-
-
Notifications
You must be signed in to change notification settings - Fork 45
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
fs/glob doesn't match all filenames with valid UTF-8 names (emoji) on macOS #141
Comments
It's a weird issue but on my Macbook Pro i9 Intel I see these results consistently between the JVM and babashka:
The JVM I'm using is Oracle GraalVM 24+36.1. So it could be a Oracle GraalVM issue. Let me try another Java version... |
With Java 17 Temurin I'm getting the same result. |
I managed to reproduce it in pure Java interop:
Do you see the same? |
I posted a question about this on Stackoverflow: https://stackoverflow.com/questions/79568521/glob-not-working-on-paths-with-unicode-in-java |
I noticed the |
I don't have java installed on my machine and won't be on a Mac over the weekend. Based on your tests it does seem to be more of a java/jvm issue on MacOS. I only noticed this because I moved from linux to Mac and all the sudden bb was skipping files when manipulating them. To be honest, I wasn't expected such a fast response; I have a lot of appreciation for your work, it makes me feel I chose the right tool in babashka! |
Thanks! The problem only seems to be there on macOS for me as well. I tried linux and Windows but those return true for both expressions. |
I posted a bug report to https://bugreport.java.com/ |
bb --version
babashka v1.12.197
MacOS 15.4 (apple silicon)
I use bb to help me manipulate my notes. I use emoji in filenames and file contents, after moving to MacOS from linux I realized the glob wasn't getting all files on my mac.
You can reproduce with the following (on MacOS)
Is this a graalvm problem ?
It is confusing to me how it works fine on linux but not on MacOS; the shell on mac is able to glob as I would expect it is only going thought babashka.fs/glob that gives me this issue.
The text was updated successfully, but these errors were encountered: