Branch: refs/heads/main
Revision: ae4afd5
Author: lydia-duncan
Link: Add futures tracking bugs with the start and end positions of channels by lydia-duncan · Pull Request #20451 · chapel-lang/chapel · GitHub
Log Message:
Merge pull request #20451 from lydia-duncan/regionBugs
Add futures tracking bugs with the start and end positions of channels
[new futures, mostly viewed by other members of the IO team]
When an end position is specified that is not the end of the file, the
file gets truncated. When a start position is specified that is not the
start of the file, the contents up to that point get turned into binary
and appear to be nonsense. Neither of these bugs are conducive to
operating on a file with multiple writing channels at once, even if the
regions are distinct enough to otherwise avoid errors.
Passed a fresh checkout
Modified Files:
A test/library/standard/IO/.gitignore
A test/library/standard/IO/openwriterEndBug.bad
A test/library/standard/IO/openwriterEndBug.catfiles
A test/library/standard/IO/openwriterEndBug.chpl
A test/library/standard/IO/openwriterEndBug.cleanfiles
A test/library/standard/IO/openwriterEndBug.future
A test/library/standard/IO/openwriterEndBug.good
A test/library/standard/IO/openwriterStartBug.bad
A test/library/standard/IO/openwriterStartBug.catfiles
A test/library/standard/IO/openwriterStartBug.chpl
A test/library/standard/IO/openwriterStartBug.cleanfiles
A test/library/standard/IO/openwriterStartBug.future
A test/library/standard/IO/openwriterStartBug.good
Compare: https://github.com/chapel-lang/chapel/compare/5f52b29d0778...ae4afd50b4bf