Contributes to #474

build(deps): bump golang.org/x/time in /internal/examples

Bumps [golang.org/x/time](https://github.com/golang/time) from 0.3.0 to 0.6.0.
- [Commits](https://github.com/golang/time/compare/v0.3.0...v0.6.0

)

---
updated-dependencies:
- dependency-name: golang.org/x/time
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

* chore: prevent ci from running twice on PRs

Now CI will only run on push to `master` and PRs to `master`. Previously, it was
running twice on each push to a PR branch, once for the PR to `master` and once 
for pushing to the PR branch.

Since we rely on the connection not being hijacked too early (i.e.
detecting the presence of http.Hijacker) to set headers, we must
manually implement the unwrapping of the http.ResponseController. By
doing so, we also retain Go 1.19 compatibility without build tags.

Closes #455

Signed-off-by: bestgopher <84328409@qq.com>

OS-specific behaviour is not necessary. This PR replaces filepath.Match
with path.Match and also updated the documentation to reflect that.

Closes #451

Sunset the dev branch

Revert "Split coverage and deploy jobs in static.yml to avoid env issue"

This reverts commit 0f14077d.

Clean out env passed to wasmbrowsertest in TestWasm

Split coverage and deploy jobs in static.yml to avoid env issue

Add setup-go to static.yml

Fix coverage

Add transfer notice to README

Update import path to github.com/coder/websocket

vulncheck was using slices which is only in
newer Go versions.

This will create easily solved breakage on updates but
I figure it's best to pull the band aid off as early as possible

Use new atomic types from Go 1.19

This is a cleaner solution for the fix in #438 thanks to the fact that Go 1.19 now is the default and the atomic.Int64 types are automatically aligned correctly on 32 bit systems.

Using this also means that xsync.Int64 can be removed. The new atomic.Int64 type solves the issue and should be quite a lot faster as it avoids the interface conversion.

fix closenow race

Context can be cancelled by parent. Doesn't indicate the CloseRead goroutine
has exited.

See #326

Far simpler now. Sorry this took a while.

Closes #427
Closes #429
Closes #434
Closes #436
Closes #437

Not ideal but whatever, I'm going to rewrite all of this anyway.