Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Links often don't open the first time #182

Open
stamminator opened this issue Dec 5, 2024 · 5 comments
Open

Links often don't open the first time #182

stamminator opened this issue Dec 5, 2024 · 5 comments
Labels
bug Something isn't working
Milestone

Comments

@stamminator
Copy link
Contributor

I run into this issue fairly frequently, maybe once or twice a day, where if I haven't opened a link in a while (e.g. after a few hours of system usage without having interacted with Hurl), the first time I try to open a link is a no-op. I end up having to open the link a second time before Hurl appears.

Repro steps

I've tried closing Hurl in Task Manager and then opening a link to reproduce it, but this always works properly, so I can't reliable reproduce this, although it's happened enough times now that I'm sure it's deterministic. Just have to figure out when.

Using Hurl version 0.9.1

@U-C-S
Copy link
Owner

U-C-S commented Dec 6, 2024

Can say, I encountered this too, but not as frequently. I was thinking if I didn't click the link properly. Thanks for conforming.

Will look into this.

@U-C-S U-C-S added the bug Something isn't working label Dec 6, 2024
@U-C-S U-C-S added this to the v0.10 milestone Dec 6, 2024
@leeyaunlong
Copy link

cloud you add the log option for debug?

@bzorich
Copy link

bzorich commented Dec 29, 2024

This change fixes this issue on my win11 laptop

_pipeserver.WaitForConnectionAsync(_cancelTokenSource.Token).Wait();

added 1000 milliseconds

_pipeserver.WaitForConnectionAsync(_cancelTokenSource.Token).Wait(1000);

@kaxonomy
Copy link

This change fixes this issue on my win11 laptop

_pipeserver.WaitForConnectionAsync(_cancelTokenSource.Token).Wait();
added 1000 milliseconds

_pipeserver.WaitForConnectionAsync(_cancelTokenSource.Token).Wait(1000);

arbitrary wait times aren't a reliable practice. unfortunate if this is the only way

@bzorich
Copy link

bzorich commented Jan 27, 2025

I would agree, but it seems to work. Have not had issue since change.
Also run it on start up with -minimized flag but it showed main screen instead of just hiding in tray so I added this to MainWindow.xaml.cs ( Visibility = Visibility.Collapsed;)

    if (data.IsRunAsMin || isRuleCheckSuccess)
    {
        MinimizeWindow();
        Visibility = Visibility.Collapsed;
        Show();
    }
    else
    {

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

5 participants