Hernán Lucas Pereira
Hernán Lucas Pereira
https://github.com/tdwg/dwc/blob/03bc7e182fbce323ae66caedef6da3a1451ca6b8/docs/text/tdwg_dwc_text.xsd#L7 I guess XSD files were originally placed at `/xsd/`. Should them be moved back or perhaps placed under `/schema/` (possibly followed by subdirectories to classify by schema type)? Also...
We are hit somewhat often with this problem. Some possible solution: https://joshfrankel.me/blog/don-t-let-the-null-bytes-bite/ (also we should consider other types or invalid params to catch). My Google skills were not enough to...
Specs failing are those from spec/features/tasks/otus/filter_spec.rb that interact with Google Maps. As temporary fix version was locked to `~> 4.2.0`
We might need to consider prioritizing changing our loader to Zeitwerk. Besides occasionally having to patch loading (like in https://github.com/SpeciesFileGroup/taxonworks/commit/7768b7e3f11e38ef8e2dbd167f99416026f605d2), it [will be mandatory Rails 7](https://weblog.rubyonrails.org/2021/9/3/autoloading-in-rails-7-get-ready/)
I'm getting somewhat frequently today errors like `uri/common.rb:739:in 'URI': bad argument (expected URI object or URI string) (ArgumentError)` It looks the problem comes from here: https://github.com/codecov/codecov-ruby/blob/e1b4e2f85b7ac9d6b33e6af9b932a865d1c765dd/lib/codecov.rb#L413 However, I was wondering...
More info: https://github.blog/changelog/2022-09-22-github-actions-all-actions-will-begin-running-on-node16-instead-of-node12/
I've noticed that since ruby33 release invoking "bundle exec irb" or "bundle exec rails c" causes this error: ``` $ bundle exec irb Error loading RC file '/usr/local/rvm/rubies/ruby-3.3.0/.irbrc': /usr/local/rvm/rubies/ruby-3.3.0/lib/ruby/3.3.0/bundled_gems.rb:74:in `require':...
[maxent_versions](https://github.com/johnbaums/rmaxent/blob/08d11039404c78824b7daaaa7e9e2df8527efad9/R/maxent_versions.R#L22) function is not currently parsing archived releases list from GitHub properly because the page layout changed. I'm afraid I cannot spend more time on this now so I'll share...
On dataset which only have `scientificName`, the importer uses the project root as parent. In the event of two or more protonyms being matched, the importer resolves to use the...