We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
tide::listener::tcp_listener
This only occurs while running on one of my machines, every other machine I've tried it on works fine.
When the server sent event endpoint fires to send an event to the page Tide logs the following error:
ERROR tide::listener::tcp_listener > async-h1 error
and in Chrome the debug log shows the following:
[0831/095258.342960:WARNING:process_memory_mac.cc(93)] mach_vm_read(0x7ffeeaa6b000, 0x2000): (os/kern) invalid address (1)
Similar behavior happens in Firefox.
Here is the endpoint in question: https://github.com/gregcline/rs-readme/blob/ce845f98be469ac15e47e1a2c30e48932b93b4fb/src/web_server.rs#L227
The project is still very much work in progress. 😣
On all other environments the server sent event periodically fires with the potentially updated file and its content hash.
Here is what chrome displays:
The text was updated successfully, but these errors were encountered:
Similar issue: #608
Sorry, something went wrong.
No branches or pull requests
Bug Report
Current Behavior
This only occurs while running on one of my machines, every other machine I've tried it on works fine.
When the server sent event endpoint fires to send an event to the page Tide logs the following error:
and in Chrome the debug log shows the following:
Similar behavior happens in Firefox.
Code/Gist
Here is the endpoint in question: https://github.com/gregcline/rs-readme/blob/ce845f98be469ac15e47e1a2c30e48932b93b4fb/src/web_server.rs#L227
The project is still very much work in progress. 😣
Expected behavior/code
On all other environments the server sent event periodically fires with the potentially updated file and its content hash.
Environment
Additional context/Screenshots
Here is what chrome displays:
The text was updated successfully, but these errors were encountered: