Mathias Fredriksson

Closing due to age, feel free to reopen if this is still an issue and the aforementioned instructions didn't give a hint for solving the problem.

Hey @lukaspj, thanks for the user experience report. You are definitely not the first! This is a very common mistake to make. There is one valid use-case for `r.Context()` after...

@spikecurtis I was thinking about the original report, but that's a good callout. We should split the second issue into a new ticket. There may be multiple issues in how...

@maggie44 certainly. In my experience, a common use-case is that the websocket is managed within the `http.Handler`, thus when `r.Context()` is used, a common misconception is that the context will...

There's nothing inherently wrong with passing the `r.Context()` other than being the source of logic bugs and misunderstanding the behavior. And you're absolutely right that a deadlock as described in...

> Interesting conversation, and I think this thread is turning in to exactly what is needed, a place for people to read through that flushes out the different scenarios. Glad...

> 1 part thinking about what the recommendation should be, 2 parts checking over my code to make sure it has been doing what I thought it had been doing...

To support multi-stage cache probes, we'll need a way to deduce the hash of dependencies between stages when operating in cache probe-mode. Some ideas off the top of my head:...

I can't reproduce this behavior with iTerm2 shell integration and Pure (without OMZ). Could you try swapping the order there at the end? ```shell source $ZSH/oh-my-zsh.sh autoload -U promptinit; promptinit...

As @denis-g mentions, modifying `fpath` is the answer. If you missed the output during installation the first time, please try to uninstall and reinstall Pure via NPM. It should output...