-
Notifications
You must be signed in to change notification settings - Fork 5k
[browser][nodejs] RequestDuration_CustomTags_Recorded - ENOENT: no such file or directory, open 'http://127.0.0.1:45051/' #88900
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
Labels
arch-wasm
WebAssembly architecture
area-System.Runtime.InteropServices.JavaScript
Known Build Error
Use this to report build issues in the .NET Helix tab
os-browser
Browser variant of arch-wasm
Milestone
Comments
Tagging subscribers to 'arch-wasm': @lewing Issue Detailsremote Loopback issue on NodeJS
|
Another log |
Probably caused by #87319 because the NodeJS CI pipeline didn't run. cc @antonfirsov |
This was referenced Jul 24, 2023
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
arch-wasm
WebAssembly architecture
area-System.Runtime.InteropServices.JavaScript
Known Build Error
Use this to report build issues in the .NET Helix tab
os-browser
Browser variant of arch-wasm
Uh oh!
There was an error while loading. Please reload this page.
remote Loopback issue on NodeJS
Log
Build Information
Build: https://dev.azure.com/dnceng-public/public/_build/results?buildId=338789&view=results
Error Message
Report
Summary
Known issue validation
Build: 🔎 https://dev.azure.com/dnceng-public/public/_build/results?buildId=338789
Error message validated:
System.Net.Http.HttpRequestException : Error: ENOENT: no such file or directory, open
Result validation: ✅ Known issue matched with the provided build.
Validation performed at: 7/14/2023 9:38:12 AM UTC
The text was updated successfully, but these errors were encountered: