by

Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • 00:32

    jlpereira on development

    Fix (compare)

  • Aug 14 22:17
    adrik29 commented #1651
  • Aug 14 21:03
    mjy commented on c79c421
  • Aug 14 21:02
    mjy commented #1651
  • Aug 14 20:47
    adrik29 opened #1651
  • Aug 14 19:04

    jlpereira on development

    Changed input size (compare)

  • Aug 14 19:00

    proceps on development

    date recognition regex update (compare)

  • Aug 14 18:40

    jlpereira on development

    misspelling (compare)

  • Aug 14 17:18

    LocoDelAssembly on development

    Fixed bug in repository facet. (compare)

  • Aug 14 15:52

    jlpereira on development

    Update CHANGELOG.md [skip ci] (compare)

  • Aug 14 15:46
    jlpereira closed #1650
  • Aug 14 15:46

    jlpereira on development

    Fix #1650 (compare)

  • Aug 14 15:16
    proceps labeled #1650
  • Aug 14 15:16
    proceps assigned #1650
  • Aug 14 15:16
    proceps opened #1650
  • Aug 14 13:07

    jlpereira on development

    Improvements on pinboard naviga… (compare)

  • Aug 13 22:39

    jlpereira on development

    Update CHANGELOG.md [skip ci] (compare)

  • Aug 13 22:37

    jlpereira on development

    Tweak (compare)

  • Aug 13 22:30
    jlpereira closed #1647
  • Aug 13 22:30

    jlpereira on development

    Fix #1647 (compare)

Matt
@mjy
Do we have expiriy on webpacker builds?
José Luis Pereira
@jlpereira
Mmmmmm, i dont see it on the headers, only for rails assets: Cache-Control: public, max-age=31536000
Well, only present on development. I don't see it in any asset on production
Hernán Lucas Pereira
@LocoDelAssembly
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.
Matt
@mjy
Thanks.
Tommy McElrath
@tmcelrath
Okay: RE yesterday - I opened same page in private browser window in Safari, not Chrome, so totally different browser, got same problem.
Opened Console in Safari: got this:
Matt
@mjy
Safari is not a good test as not offiically supported, if you can replicate in FF
Tommy McElrath
@tmcelrath
image.png
Trying in Forefox
*Firefox
same issue there, waiting for log
image.png
No extensions, no browser plug-ins
I'm also noticing super long load times for georeferencing RE this collecting event.
Ah, same patch code.
Tommy McElrath
@tmcelrath
Console for clicking on Georeference:
image.png
Tommy McElrath
@tmcelrath
Okay I got through that collecting event's specimens and now everything is fine. Definitely something wrong with that collecting event.
Matt
@mjy
How many collection objects on the CE?
Tommy McElrath
@tmcelrath
32
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.
Matt
@mjy
@tmcelrath did you/can you add an issue?
Tommy McElrath
@tmcelrath
Had no COs added, as I add them, time gets longer.
Not yet, but I can
Matt
@mjy
Thanks.
Tommy McElrath
@tmcelrath
Was hoping was a quick fix, but apparently not
Matt
@mjy
@LocoDelAssembly maybe we have a triggering loop- likely need a test where do some timing to see if we can replicate
Tommy McElrath
@tmcelrath
Matt
@mjy
Thanks.
Matt
@mjy
Hernán Lucas Pereira
@LocoDelAssembly
@mjy @proceps @jlpereira is this a good moment to make a new release?
Matt
@mjy
oops
Can you check the CE autocomplete bug that got fired?
got a million emails
Hernán Lucas Pereira
@LocoDelAssembly
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)
Dmitry Dmitriev
@proceps
@LocoDelAssembly It would be good time to push recent changes to the production. Numberous small thing added to development during last few weeks.
Hernán Lucas Pereira
@LocoDelAssembly
Will begin preparing. Please @mjy @jlpereira if there is any reason to not proceed let me know.
José Luis Pereira
@jlpereira
@LocoDelAssembly give me a couple of minutes to get back and push a little fix
Hernán Lucas Pereira
@LocoDelAssembly
@jlpereira OK. The CHANGELOG was already set for release, so make sure you add entries in 0.12.13 section instead of unreleased.
José Luis Pereira
@jlpereira
@LocoDelAssembly ready
Matt
@mjy
@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.
Hernán Lucas Pereira
@LocoDelAssembly
@/all Production is being updated to version 0.12.13 📢
Hernán Lucas Pereira
@LocoDelAssembly
@/all Version 0.12.13 live 📢
Changes on this release: https://github.com/SpeciesFileGroup/taxonworks/releases/tag/v0.12.13 📝
Matt
@mjy
Thanks @LocoDelAssembly
Tommy McElrath
@tmcelrath
Getting #1630 right now - happy to zoom to show any network tabs.
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.