-
Notifications
You must be signed in to change notification settings - Fork 42
Open
Labels
A-ClientArea: Parsec desktop applicationArea: Parsec desktop applicationB-TriageBlocker: The issue is awaiting triageBlocker: The issue is awaiting triageI-BindingsImpact: libparsec bindings (generator, electron, web, ...)Impact: libparsec bindings (generator, electron, web, ...)I-RustImpact: Rust-related stuffImpact: Rust-related stuff
Description
Parsec version
3.7
Which platform(s) you have observed the problem
- Any
- macOS
- Linux
- Windows
- Web
Bug description
When calling libparsec.pathJoin('/', '/'), an exception occurs inside the worker, and the function never returns.
The function returns a string and we don't really want to make it return a result (it would add a lot of complexity). It could be argued that / could be a valid return value in this case. In any case, the function should return, not block.
How should the application behave
No response
Reproduction steps
1.
2.
3.
...Relevant output:
No response
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
A-ClientArea: Parsec desktop applicationArea: Parsec desktop applicationB-TriageBlocker: The issue is awaiting triageBlocker: The issue is awaiting triageI-BindingsImpact: libparsec bindings (generator, electron, web, ...)Impact: libparsec bindings (generator, electron, web, ...)I-RustImpact: Rust-related stuffImpact: Rust-related stuff