-
-
Notifications
You must be signed in to change notification settings - Fork 42
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
jsp: properties.jsp fails, missing #1014
Comments
|
We have the IndexUnicodeProperties data precalculated, but probably not the ToolUnicodeProperties data which lurks in the darker and more ancient corners of this code base. |
@eggrobin i'm not sure what either of those are… |
There are two main implementations of UCD parsing and data structures for accessing the UCD in here:
Someday, and that day may never come, we will retire org.unicode.text.UCD… See #639. But to the issue at hand, we should have write permissions to Generated. |
maybe when it does the copy it has more restrictive permissions. But again, shouldn't we pre-create the content in Generated rather than have it created on the fly in each Cloud Run instantiation? |
In principle, sure, in practice, it’s not that costly (compared to, e.g., just loading the much larger precomputed IUP data), and making sure that we have generated everything we need is tricky (especially since we shouldn’t need too much, as this is the legacy part: like the new IUP, the old TUP is also capable of handling old versions of the UCD, albeit with questionable correctness, but I don’t know how much of that can actually be hit from the JSPs). And investing too much energy into the twenty-nine year old part of the infrastructure rather than the fourteen year old part seems unwise. |
@iwsfutcmd found this when using the docker image of a recent build:
properties.jsp failed as below.
Indeed,
/var/lib/jetty/data/unicodetools/Generated/BIN/UCD_Data16.0.0.bin
doesn't exist.Did something change in the build process? assign this back to me if you have comments
The text was updated successfully, but these errors were encountered: