ArchiSteamFarm: ASF's docker "latest" containers have broken ASF-ui and localization
See upstream issue: https://github.com/dotnet/runtime/issues/37208
The fix is actually not so obvious, as I’d need to disable the single file publish in linux-* OS-specific packages that latest containers actually update to, and that would kill the properly working functionality on barebones Linux machines. Not the cleanest solution.
If there is no good solution to this issue, I’ll do that in a few days. The optimal solution would be finding out what causes this issue in docker and working it around for time being.
About this issue
- Original URL
- State: closed
- Created 4 years ago
- Comments: 20 (10 by maintainers)
Commits related to this issue
- Add awful workaround for #1812 — committed to JustArchiNET/ArchiSteamFarm by JustArchi 4 years ago
- Address possible .NET Core tmp path change in #1812 — committed to JustArchiNET/ArchiSteamFarm by JustArchi 4 years ago
- Remove workaround for #1812 — committed to JustArchiNET/ArchiSteamFarm by JustArchi 4 years ago
- .NET 5.0 (#1999) * Initial work * Fix CIs * Fix warnings * Update .travis.yml * Update dockerfiles * Update libraries to .NET 5.0 * Misc * Remove workaround for #1812 * Update... — committed to JustArchiNET/ArchiSteamFarm by JustArchi 4 years ago
If you’d like to test if .NET 5.0 solves this issue, I’ve set up my docker CI to build
experimental-net5.0tag, together with-armand-arm64release. This should be available later today.Check #1999 for more details.
This issue is supposed to be fixed with https://github.com/dotnet/sdk/pull/12814 - if we’re lucky, it’ll make it to .NET 5.0 release.
(Please avoid spamming this issue with problems unrelated to the one discussed here, especially if it has nothing to do with ASF development, thank you)
Hello, I have the
latestcontainer (4.2.3.4) and I have the same problem as @iceCodeNew but I’m using the english locale. I’ve also tried with thereleasedcontainer as you mentioned but still the same errorProbably, I’m not sure, fact is that everything we do in this issue is a workaround for .NET Core bug which shouldn’t (and actually is impossible to) be solved by us.
You can give it a try with other docker images, such as
releasedwhich do not suffer from this problem. If you find out that addinglibicuto it fixes localization, you can submit a PR to our dockerfiles adding it.Localization has nothing to do with ASF being capable (or not) of handling chinese characters, ASF is UTF8 (actually Unicode) compatible and aware. You can use russian localization with chinese names for bots for example.
And yes, minutes come from humanizer, this is why they were translated.