Well, only present on development. I don't see it in any asset on production
Do not attempt to change cacheability of webpack-managed assets unless you are absolutely certain of what you are doing. It is supposed that referenced assets have a SHA1 hash in their name, so a single change produces a new file that is impossible that browsers could use a cached previous version.
Opened Console in Safari: got this:
Trying in Forefox
*Firefox
same issue there, waiting for log
No extensions, no browser plug-ins
I'm also noticing super long load times for georeferencing RE this collecting event.
Ah, same patch code.
Now I'm getting longer load times on the new CE
the more objects I add the longer it gets
Up to seventeen seconds on this one - started at 1 second.
Not yet, but I can
THis sikely impact us in the long run: https://developer.squareup.com/blog/the-state-of-ruby-3-typing/
Can you check the CE autocomplete bug that got fired?
got a million emails
I've lost count of how many times I've attempted to determine what's wrong with it (including last week when the tsunami of notifications arrived)... Never managed to reproduce locally. The error started somewhere else, then shifted to the autocomplete. Always the problem was in UNH Insects project but the very last errors also happened in INHS. The earliest exception notification I have (which was
contains? on String when receiver should have been geo-related class), is of the same date that https://github.com/SpeciesFileGroup/taxonworks/releases/tag/v0.12.5 was released. Nothing there looks it should cause it. Do anyone have exceptions of that kind that are even earlier than this? I'm not fully convinced this problem started that date, specially given that https://github.com/SpeciesFileGroup/taxonworks/blob/development/app/views/exception_notifier/_full_backtrace.text.erb was added very few days later in 0.12.6.
The only next action I have left would be to plant code to watch for this error and get as much information as possible (starting with a full output of
inspect on that alleged String that should have been some RGeo class)
@LocoDelAssembly I almost have new sqed pattern ready- but I don't want to rush it, so maybe we do a quick release after. No reason not to deploy. We need to tease out the semantic versioning a little more explicitly in the future perhaps. I.e. if we have "Added" things in changelog then likely its a minor bump, but changed and fixed are patch.
@/all Version 0.12.13 live 📢
Changes on this release: https://github.com/SpeciesFileGroup/taxonworks/releases/tag/v0.12.13 📝
Changes on this release: https://github.com/SpeciesFileGroup/taxonworks/releases/tag/v0.12.13 📝
It's slowing down productivity for me pretty heavily using comprehensive to digitize lots of specimens - so I'm up for doing anything I can to help isolate the issue.