Uri scheme isn't normalized
See original GitHub issueIssue Type: Bug
Open URL <URL: FILE:///proc/sys/fs/inotify/max_user_instances >! Note: <URL: file:///proc/sys/fs/inotify/max_user_instances > opens all right.
VS Code version: Code 1.62.3 (ccbaa2d27e38e5afa3e5c21c1c7bef4657064247, 2021-11-17T08:00:36.721Z) OS version: Linux x64 5.15.5-1-default Restricted Mode: No
System Info
Item | Value |
---|---|
CPUs | Intel® Core™2 Quad CPU Q6600 @ 2.40GHz (4 x 2393) |
GPU Status | 2d_canvas: enabled gpu_compositing: enabled multiple_raster_threads: enabled_on oop_rasterization: disabled_off opengl: enabled_on rasterization: disabled_software skia_renderer: enabled_on video_decode: disabled_software vulkan: disabled_off webgl: enabled webgl2: enabled |
Load (avg) | 3, 2, 5 |
Memory (System) | 5.66GB (0.14GB free) |
Process Argv | –unity-launch --crash-reporter-id 2a03cb52-9f4b-48bf-93d3-5c0537d534ee |
Screen Reader | no |
VM | 0% |
DESKTOP_SESSION | /usr/share/xsessions/plasma5 |
XDG_CURRENT_DESKTOP | KDE |
XDG_SESSION_DESKTOP | KDE |
XDG_SESSION_TYPE | x11 |
Extensions (24)
Extension | Author (truncated) | Version |
---|---|---|
doxdocgen | csc | 1.3.2 |
vscode-pull-request-github | Git | 0.32.0 |
Ionide-fsharp | Ion | 5.10.2 |
better-cpp-syntax | jef | 1.15.10 |
vscode-language-pack-pl | MS- | 1.62.4 |
csharp | ms- | 1.23.16 |
dotnet-interactive-vscode | ms- | 1.0.2602010 |
vscode-dotnet-pack | ms- | 1.0.4 |
python | ms- | 2021.11.1422169775 |
vscode-pylance | ms- | 2021.11.2 |
jupyter | ms- | 2021.10.1101450599 |
jupyter-keymap | ms- | 1.0.0 |
jupyter-renderers | ms- | 1.0.4 |
remote-containers | ms- | 0.205.2 |
remote-ssh | ms- | 0.66.1 |
remote-ssh-edit | ms- | 0.66.1 |
remote-wsl | ms- | 0.58.5 |
cmake-tools | ms- | 1.9.2 |
cpptools | ms- | 1.7.1 |
cpptools-extension-pack | ms- | 1.1.0 |
vscode-markdown-notebook | ms- | 0.0.26 |
vsliveshare | ms- | 1.0.5090 |
vsliveshare-audio | ms- | 0.1.91 |
cmake | twx | 0.0.17 |
(1 theme extensions excluded)
A/B Experiments
vsliv368:30146709
vsreu685:30147344
python383:30185418
vspor879:30202332
vspor708:30202333
vspor363:30204092
pythontb:30283811
pythonvspyt551cf:30345471
pythonptprofiler:30281270
vshan820:30294714
vstes263:30335439
pythondataviewer:30285071
vscod805:30301674
pythonvspyt200:30340761
binariesv615:30325510
bridge0708:30335490
bridge0723:30353136
pythonrunftest32:30373476
pythonf5test824:30373475
javagetstartedt:30391933
pythonvspyt187:30373474
vsaa593cf:30376535
vscop804cf:30404767
vscop940:30404999
vsrem710:30405998
Issue Analytics
- State:
- Created 2 years ago
- Comments:9 (8 by maintainers)
Top Results From Across the Web
URI normalization - Wikipedia
URI normalization is the process by which URIs are modified and standardized in a consistent manner. The goal of the normalization process is...
Read more >Normalizing Link not possible when uri is null - Drupal
When an entity has a 'link' field that isn't filled, the link field will still be normalized. This results in an InvalidArgumentException.
Read more >c# - The provided URI scheme 'https' is invalid; expected 'http ...
I finally narrowed it down to being an issue in WCFStorm after creating a service reference in a test project in Visual Studio...
Read more >java.net.URI.normalize java code examples - Tabnine
private static String normalizeURI(String uri) { return URI.create(uri).normalize().toString();
Read more >URI schemes - UWP applications | Microsoft Learn
All of the schemes described in this topic follow typical URI scheme rules for normalization and resource retrieval.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
There is no problem as long as externalized uris go though
URI.parse(...).toString()
again. Tho every place where a scheme is “left alone” or were an externalized URI is concatenated with another string we can see issuesYeah, this is a known bug. What’s unknown is if we can still fix it. Many 3rd parties and extensions have started to “depend” on uri-bugs and in the past good changes/fixes had really bad consequences. This needs careful consideration first