-
Notifications
You must be signed in to change notification settings - Fork 619
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
Remove unnecessary platform specific workaround in iso9660util #3149
base: master
Are you sure you want to change the base?
Conversation
Signed-off-by: Arthur Sengileyev <[email protected]>
If it works now, it was probably fixed in either the go-diskfs or in go. Back then, it didn't like when mixing them. |
But from what I can tell, it still seems to be using https://github.com/diskfs/go-diskfs/tree/master/filesystem/iso9660 fullPath := path.Join(fsm.workspace, p) |
I'll rebuild from unaltered to double check and post stack trace here later. |
It is definitely using Same in the master HEAD. |
And here is stack trace showing filepath being used, where it panics
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Reproduced the crash, cidata.iso creation now works without converting the path (so it is not needed).
I've been experimenting using latest Lima with QEMU on Windows and during my initial tests writing
.iso
file would always result in app panicking inside the third party library (I don't have stack trace preserved unfortunately). By removing this transformation of path I did manage to get a running setup. Probably the native Windows path handling was added in upstream, but I didn't try to bisect there no evidence when it was last working.cc: @afbjorklund tagging you, because you added this part some time ago f264c90