Fixed get method of RemotePathMapper
#343
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Codecov ReportAll modified and coverable lines are covered by tests ✅
❗ Your organization needs to install the Codecov GitHub app to enable full functionality. Additional details and impacted files@@ Coverage Diff @@
## master #343 +/- ##
=======================================
Coverage 67.17% 67.18%
=======================================
Files 82 82
Lines 10277 10277
Branches 2432 2432
=======================================
+ Hits 6904 6905 +1
+ Misses 2949 2948 -1
Partials 424 424 ☔ View full report in Codecov by Sentry. |
GlassOfWhiskey
changed the title
get method of RemotePathMapper
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This commit fixes the
getmethod of theRemotePathMapperclass when trying to access a location not yet registered in the StreamFlow filesystem.In particular, this commit fixes issue #342, probably caused by a regression introduced by PR #328.