sieve-connect: Init at 0.89

Motivation for this change
I use this tool to administrate the mail rules on my mail server.
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[x] Fits CONTRIBUTING.md.

Failing check is unrelated

@GrahamcOfBorg eval

@GrahamcOfBorg build sieve-connect

Success on x86_64-linux (full log)
Attempted: sieve-connect
Partial log (click to expand)
chmod +x "sieve-connect"
installing
post-installation fixup
shrinking RPATHs of ELF executables and libraries in /nix/store/hvk6v1w6zg8p5f4rpma28nhs2335w3k7-sieve-connect-0.89
gzipping man pages under /nix/store/hvk6v1w6zg8p5f4rpma28nhs2335w3k7-sieve-connect-0.89/share/man/
strip is /nix/store/a3nk8z2i7m7wa3jdckgv710n7j3yx4b5-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/hvk6v1w6zg8p5f4rpma28nhs2335w3k7-sieve-connect-0.89/bin
patching script interpreter paths in /nix/store/hvk6v1w6zg8p5f4rpma28nhs2335w3k7-sieve-connect-0.89
checking for references to /build in /nix/store/hvk6v1w6zg8p5f4rpma28nhs2335w3k7-sieve-connect-0.89...
/nix/store/hvk6v1w6zg8p5f4rpma28nhs2335w3k7-sieve-connect-0.89

Success on aarch64-linux (full log)
Attempted: sieve-connect
Partial log (click to expand)
chmod +x "sieve-connect"
installing
post-installation fixup
shrinking RPATHs of ELF executables and libraries in /nix/store/9lzimdlvh31rl6qdz0fdsz4hhxi8b7dk-sieve-connect-0.89
gzipping man pages under /nix/store/9lzimdlvh31rl6qdz0fdsz4hhxi8b7dk-sieve-connect-0.89/share/man/
strip is /nix/store/a245zacjzf3qw0davhvlfarihcy2yyrc-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/9lzimdlvh31rl6qdz0fdsz4hhxi8b7dk-sieve-connect-0.89/bin
patching script interpreter paths in /nix/store/9lzimdlvh31rl6qdz0fdsz4hhxi8b7dk-sieve-connect-0.89
checking for references to /build in /nix/store/9lzimdlvh31rl6qdz0fdsz4hhxi8b7dk-sieve-connect-0.89...
/nix/store/9lzimdlvh31rl6qdz0fdsz4hhxi8b7dk-sieve-connect-0.89

Success on x86_64-darwin (full log)
Attempted: sieve-connect
Partial log (click to expand)
build flags: SHELL=/nix/store/ryb1pmpqm7xiznq5574lifykqrr30hg6-bash-4.4-p23/bin/bash
sed <"sieve-connect.pl" >"sieve-connect" "1s:/.*:`sh ./find-perl58.sh`:"
chmod +x "sieve-connect"
installing
post-installation fixup
gzipping man pages under /nix/store/9nq7xmrvjapv8mam0zh979qmm25av0av-sieve-connect-0.89/share/man/
strip is /nix/store/sixx1lfy97125f6hxymbwn64cb8z62p3-cctools-binutils-darwin/bin/strip
stripping (with command strip and flags -S) in /nix/store/9nq7xmrvjapv8mam0zh979qmm25av0av-sieve-connect-0.89/bin
patching script interpreter paths in /nix/store/9nq7xmrvjapv8mam0zh979qmm25av0av-sieve-connect-0.89
/nix/store/9nq7xmrvjapv8mam0zh979qmm25av0av-sieve-connect-0.89

@ryantm Rebased and fixed

@GrahamcOfBorg build sieve-connect

Success on x86_64-darwin (full log)
Attempted: sieve-connect
Partial log (click to expand)
sed <"sieve-connect.pl" >"sieve-connect" "1s:/.*:`sh ./find-perl58.sh`:"
chmod +x "sieve-connect"
pod2man -n "sieve-connect" -c '' -d "`cat datefile`" -r "`cat versionfile`" "sieve-connect.pl" >"sieve-connect.1"
installing
post-installation fixup
gzipping man pages under /nix/store/jrgf9yr5l3wy20qmmnhpyq733s7gh8xv-sieve-connect-0.89/share/man/
strip is /nix/store/sixx1lfy97125f6hxymbwn64cb8z62p3-cctools-binutils-darwin/bin/strip
stripping (with command strip and flags -S) in /nix/store/jrgf9yr5l3wy20qmmnhpyq733s7gh8xv-sieve-connect-0.89/bin
patching script interpreter paths in /nix/store/jrgf9yr5l3wy20qmmnhpyq733s7gh8xv-sieve-connect-0.89
/nix/store/jrgf9yr5l3wy20qmmnhpyq733s7gh8xv-sieve-connect-0.89

Success on aarch64-linux (full log)
Attempted: sieve-connect
Partial log (click to expand)
pod2man -n "sieve-connect" -c '' -d "`cat datefile`" -r "`cat versionfile`" "sieve-connect.pl" >"sieve-connect.1"
installing
post-installation fixup
shrinking RPATHs of ELF executables and libraries in /nix/store/r3130s616gha3igf60n239mx3jiwq7q5-sieve-connect-0.89
gzipping man pages under /nix/store/r3130s616gha3igf60n239mx3jiwq7q5-sieve-connect-0.89/share/man/
strip is /nix/store/a245zacjzf3qw0davhvlfarihcy2yyrc-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/r3130s616gha3igf60n239mx3jiwq7q5-sieve-connect-0.89/bin
patching script interpreter paths in /nix/store/r3130s616gha3igf60n239mx3jiwq7q5-sieve-connect-0.89
checking for references to /build in /nix/store/r3130s616gha3igf60n239mx3jiwq7q5-sieve-connect-0.89...
/nix/store/r3130s616gha3igf60n239mx3jiwq7q5-sieve-connect-0.89

Success on x86_64-linux (full log)
Attempted: sieve-connect
Partial log (click to expand)
pod2man -n "sieve-connect" -c '' -d "`cat datefile`" -r "`cat versionfile`" "sieve-connect.pl" >"sieve-connect.1"
installing
post-installation fixup
shrinking RPATHs of ELF executables and libraries in /nix/store/d9q8j61syrlri024k3gs6nyf3yri22f3-sieve-connect-0.89
gzipping man pages under /nix/store/d9q8j61syrlri024k3gs6nyf3yri22f3-sieve-connect-0.89/share/man/
strip is /nix/store/a3nk8z2i7m7wa3jdckgv710n7j3yx4b5-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/d9q8j61syrlri024k3gs6nyf3yri22f3-sieve-connect-0.89/bin
patching script interpreter paths in /nix/store/d9q8j61syrlri024k3gs6nyf3yri22f3-sieve-connect-0.89
checking for references to /build in /nix/store/d9q8j61syrlri024k3gs6nyf3yri22f3-sieve-connect-0.89...
/nix/store/d9q8j61syrlri024k3gs6nyf3yri22f3-sieve-connect-0.89

Thanks!


protobuf version fighting?

if i pip install autotrain-advanced, it installs protobuf v 4.23.4.  This causes the complaint: ERROR: pip's dependency resolver does not currently take into account all the packages that are installed. This behaviour is the source of the following dependency conflicts. tensorflow-metadata 1.14.0 requires protobuf<4.21,>=3.20.3, but you have protobuf 4.23.4 which is incompatible.
fine. So I uninstall this version of protobuf and !pip install protobuf>=3.20.3.  Now pip is complaining: ERROR: pip's dependency resolver does not currently take into account all the packages that are installed. This behaviour is the source of the following dependency conflicts. autotrain-advanced 0.6.32 requires protobuf==4.23.4, but you have protobuf 4.24.3 which is incompatible. tensorflow-metadata 1.14.0 requires protobuf<4.21,>=3.20.3, but you have protobuf 4.24.3 which is incompatible.
I merrily go on..but this seems problematic???

it can be ignored

@abhishekkrthakur  Thank you for the quick reply.


Upgrade CentOS-based container images to CentOS Stream

I forgot to fetch recent changes. CentOS-based images have already been upgraded.


keepass: fix auto-type and clipboard features

Motivation for this change
This fixes paths to xdotool, xprop and xsel. These are required tools for auto-type to work correctly.
Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option build-use-sandbox in nix.conf on non-NixOS)
Built on platform(s)

[X] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[X] Tested execution of all binary files (usually in ./result/bin/)
[X] Fits CONTRIBUTING.md.

@GrahamcOfBorg build keepass

Failure on aarch64-linux (full log)
Partial log (click to expand)
Package ‘mono-<IP_ADDRESS>’ in /var/lib/gc-of-borg/nix-test-rs-1/repo/38dca4e3aa6bca43ea96d2fcc04e8229/builder/grahamc-aarch64-community-1/pkgs/development/compilers/mono/generic.nix:90 is not supported on ‘aarch64-linux’, refusing to evaluate.

a) For `nixos-rebuild` you can set
  { nixpkgs.config.allowBroken = true; }
in configuration.nix to override this.

b) For `nix-env`, `nix-build`, `nix-shell` or any other Nix command you can add
  { allowBroken = true; }
to ~/.config/nixpkgs/config.nix.

Success on x86_64-linux (full log)
Partial log (click to expand)
/nix/store/p8jy1cwydfcpdkpbzwhf5ih79mbdi98y-keepass-2.38 /tmp/nix-build-keepass-2.38.drv-0
/tmp/nix-build-keepass-2.38.drv-0
Created /nix/store/p8jy1cwydfcpdkpbzwhf5ih79mbdi98y-keepass-2.38/lib/pkgconfig/KeePassLib.pc
rscFileExt=ico
glibPreFixupPhase
post-installation fixup
shrinking RPATHs of ELF executables and libraries in /nix/store/p8jy1cwydfcpdkpbzwhf5ih79mbdi98y-keepass-2.38
patching script interpreter paths in /nix/store/p8jy1cwydfcpdkpbzwhf5ih79mbdi98y-keepass-2.38
checking for references to /tmp/nix-build-keepass-2.38.drv-0 in /nix/store/p8jy1cwydfcpdkpbzwhf5ih79mbdi98y-keepass-2.38...
/nix/store/p8jy1cwydfcpdkpbzwhf5ih79mbdi98y-keepass-2.38

Failure on x86_64-darwin (full log)
Partial log (click to expand)
Package ‘xdotool-3.20160805.1’ in /private/var/lib/ofborg/checkout/repo/38dca4e3aa6bca43ea96d2fcc04e8229/builder/lnl7-mac/pkgs/tools/X11/xdotool/default.nix:23 is not supported on ‘x86_64-darwin’, refusing to evaluate.

a) For `nixos-rebuild` you can set
  { nixpkgs.config.allowBroken = true; }
in configuration.nix to override this.

b) For `nix-env`, `nix-build`, `nix-shell` or any other Nix command you can add
  { allowBroken = true; }
to ~/.config/nixpkgs/config.nix.


Stylistic Updates

This should be run on top of PR #4
Various stylistic changes:

Added explicit "@Spell" dependencies
Added commas and colons to delimiters and operators, respectively
Changed "json5ObjAssign" to "json5Key"
Included string-style keys in json5Key
Changed braces to use the "Delimiter" style
Changed "null" to use the "Keyword" style
Removed the comment pragmas
Added a header comment to give credit to the original

Aaaargh, not again!

This is why I split the updates into two separate PRs -- in all likelihood this PR will be rejected because it's subjective, but I would like to get the hexadecimal numbers in (PR #4)...

Hahaha, no. Look at my username and then the body of your pull request. :-)

Hahaha, no. Look at my username and then the body of your pull request. :-)

AAAHHH -- I understand!  Must be rather frustrating...

@jpt13653903 Could you rebase it?

Done...
I originally didn't rebase because I don't, in general, like forced pushes, but this makes it much neater.


Convert CircleFrame to CircleBorder

Notes
This pull request is the result of the discussion held in #28, please read for context.
Details
All Frame inheritance that IndicatorItemView had has been replaced with inheritance of the Border element. Meaning that the most notable difference is the fact that CircleFrame has now been converted to CircleBorder.
README and docs have also been updated to reflect the conversion of Frame to Border.
Testing Performed
All samples views were tested before and after these changes on the listed platforms to ensure backwards compatibility. Test results indicate that this PR should not break anything setup with this library that is either a) out of the box or b) in-line with provided samples. Unless users directly (not through a style) access properties of the Frame element on the IndicatorItemView, then there should be no issues adopting these changes. Please read #28 for more information regarding backwards compatibility.

iOS
Android
Windows

You rock, man, as usual! <3


[FEATURE] Disable the localShuffleRead in Spark client

Code of Conduct

[X] I agree to follow this project's Code of Conduct

Search before asking

[X] I have searched in the issues and found no similar issues.

Describe the feature
The conf of spark.sql.adaptive.localShuffleReader.enabled should be false when using uniffle.
We'd better to disable it by default in RssShuffleManager
Motivation
No response
Describe the solution
No response
Additional context
No response
Are you willing to submit PR?

[X] Yes I am willing to submit a PR!

PTAL @jerqi @advancedxy

Ok for me.


Support for scanning multiple barcodes

Does this support scanning multiple barcodes without automatically popping back to the previous view? If so how? I see I can call BarcodeScanner.scan().asStream(); Am I headed in the right direction with this? thanks!

Good suggestion 🙂

Any news on this issue?

+1

This feature would be awesome!
Just a callback on scan without closing the camera view or yes, an stream.
I think this issue is related: https://github.com/mintware-de/flutter_barcode_reader/issues/259

I would like to have this feature too

I'll add my two cents here then...
I noticed that the scanner is not invoking a wakelock to keep the screen on while scanning. I don't know whether or not this deserves a separate issue/feature request. I can kind of circumvent the issue right for now, since the scanner closes every so often and re-engages the wakelock, however, if you consider adding the continuous mode you'd have to also address the wakelock issue.

That's very crucial feature for me. I really liked this package but I'm forced to use less flexible ones which provides stream mode.


feat: complete refactor, ci compilation + test, CMake configs

- What I did

completely remade packages/atclient/CMakeLists.txt
can be consumed by other CMake packages via find_package(atclient REQUIRED CONFIG) in another CMake project
tests now use CTest instead of running each binary individually through the python tool
shifting over to a pure CMake solution instead of using the python tool as different OS's require different generators and flags
CMake version minimum is now 3.19 as that is "adequate" for Apple Silicon. See #23
Encouraging  use of cmake --build build --target install instead of make install because we want to specify the generator with the -G Ninja or -G "Unix Makefiles" flags on the CMake configure step, so that we can target different generators. SEe #30
Automated tests using GitHub actions
Removed deps/ folder and git submodule tactic entirely.. use FetchContent Cmake module instead to fetch outside packages. The command also gets from releases (MbedTLS v3.4.1) so that we are not working directly from their trunk in case of any breaking changes they accidentally push. Summary: WE NOW depend on their RELEASE instead of their TRUNK branch.

- How I did it

Completely commented out your CMakeLists.txt @XavierChanth sorry...

- How to verify it

See passing unit tests

- Description for the changelog

closes #30
closes #28
closes #21
closes #23

Would like to merge @XavierChanth
Wrote up the windows atchops edge case in a ticket: #31
All is documented in the README as well

Nice work!


feat: pis stage for the platform orchestration dag

This PR adds the first stage for the Platform DAG: The one that runs PIS.
In the end it is using Compute Engine machines that are spawned with COOS. They are very fast to spin up (~10 seconds), but quite limited on what they can do.
I've implemented an Airflow Sensor/Operator that is in charge of:

Spawning a machine
Attaching disks to it
Copying config files from a bucket
Running a docker image with some arguments
Waiting for the exit code of that docker container
Repoting a success (exit code 0), or a failure for the task (>0)

Most of the logic is in the gce.py file, which contains that operator.
I also:

Added airflow-triggerer service to the docker-compose, as we need it for sensors.
Added an ignore_init setting to interrogate so we don't have to add docstrings to __init__ methods (it's annoying and rarely useful).

I'm opening the PR already although work is well underway for the ETL stage, as this way we can split the code into more manageable chunks for review. Shorter reviews find more things to fix!
I'll leave it as pending for now, until the merge of https://github.com/opentargets/orchestration/pull/13, so I can rebase onto it and fix any problems that arise.

The rationale behind remove interrogate and pydoclint is that we are already checking docstrings with Ruff by using the pydocstyle rules.
Interrogate and Pydoclint are extremely strict, I copypasted a docstring straight from google code and they complain about it. Also, --ignore-init-function and --style google are mutually exclusive and it is a pain to document all \_\_init\_\_ functions.
Let me know if you think this is too big a change.

I cannot reproduce the check error on the poetry lock pre-commit check. We should discuss on loosening those, right now it seems a bit overkill. :)

@javfg approved. Nice work!

@javfg can you drop the poetry.lock check. I had the same issue with it on my previous PR.


Packaging errors with version files

When using local paths for packaging, often we can't find the version files (e.g. lacci/version, scarpe-components/version) via local require from the gemspecs. This may need a wasify patch -- or maybe don't require, and get the version some other way?
It seems like an annoying problem.

As a temp workaround we could prepack, then figure out where to require the version files from. But I don't love that - it'd be a Scarpe-specific workaround to a more general problem. Could maybe fix somehow in wasify?
But it seems like Giovanni may not be updating Wasify any more. We may want a fork of wasify under scarpe-team where we've applied the submitted PRs (e.g. https://github.com/AlawysDelta/wasify/pull/9).

Ah, okay. Looks like these errors were cases where I wasn't specifying head-of-master in the Gemfile for the wasify gem. That's a really good reason (because I can fix that!).

Fixed.


Migrate this.value to this.modelValue

Fixes #117

Proposed Changes

Migrate this.value to this.modelValue

Thanks, probably I didn't check all during migration


Thank you!

No issue.
I just want to thank @ariutta @bumbu and all of the other contributors to this wonderful library, which has saved me and many others time and energy.
Thanks!

Thank you for your support @rendall
It actually makes a big difference to get at least some positivity from time to time.
I appreciate it a lot!

We human beings are pessimistic by nature. We often ignore what's working and focus on what's not working. It's important to stop and recognize those people who have helped you out, such as you-all.
So, thanks again!  Good luck!


Configure screenshot service

Additionall to switching the service on and of, we could also configure other things:

thumbnail size
png <-> jpg
quality
days after which screenshots get deleted
days after which thumbnails get deleted

I assume, we shouldn't present all of these options but make good defaults. Let’s not blow up the UI.
To change these, we need to adjust the cronjob and/or screenshot script.
The script is here /opt/tooloop/scripts/tooloop-screenshot

I had an instance, where the harddrive was very small and the 4K screenshots were big.
At some point there wasn't enough space on the harddrive and the system wouldn’t run properly.
Some configuration would maybe have helped.


Migrate from centos7.9 to ol8.8?

Is there a parameter I can add to the script to cause centos7.9 to migrate specifically to Oracle Linux 8.8? Our app only supports that path. Any guidance much appreciated.

I understand. However, Ciena states in their documentation: (Ciena MCP 7.x to 8.x OS Migration)
Table 1. Operating system migration supported path
From                                   To
RHEL 7.9                               RHEL 8.6/8.8
Oracle Linux 7.9                    Oracle Linux 8.6/8.8
CentOS 7.9                           RHEL/ORACLE Linux 8.6/8.8
Considerations

CentOS 7.9 can only be migrated to RHEL/Oracle Linux 8.6/8.8.

After installation any OS, or other updates ("bundles"), are supplied solely by Ciena; once they are vetted to work with their app.
I was informed by Ciena support that their 8.x app installer checks OS version at startup and will not run if OS version is other than ol8.6 or 8.8.
I previously downloaded the ol8.8 ISO. Can I not, instead, run the install, locally, and install ol8.8 over the centos7.9 now running on the servers? I plan to upgrade a test environment first to confirm operability.
Thank you again for your assistance.

Please open a support ticket with that vendor. You should consider it unacceptable that you cannot install security updates for your OS (which would make OL8 appear as "8.9" today, and "8.10" soon). Their check for exactly "8.8" is improper and Oracle does not condone using such checks to prevent you from installing updates.
If you want to install from scratch, you are free to do it, but this will not "upgrade" the system; it will install a bare system and you will need to migrate/install your applications to it.

I understand your point. Unfortunately, I have been fighting that battle for more than 2 years, with little success. I have to continue using the app to manage assets. And, now, have to migrate/upgrade in order to gain functionality. Thank you again for your time and guidance.


SASS/SCSS variant?

Any chance we could get this wonderful CSS framework in a SASS/SCSS variety? :+1:

+1

+1


polycystic liver disease refinement required : MONDO:0000447 autosomal dominant polycystic liver disease and MONDO:0008265 Polycystic liver disease 1 obsolete ExactMatches and incorrect Exact Synonym

I still seem to be on an ongoing quest to try and resolve some polycystic liver disease issues, this time caused by an Exactmatch xref and has Exactsynonym
I have made some suggestions below to try to resolve this, but you might have a better grasp of what is going on, so wanted to flag it up in the hope it can be resolved- thank you!
Mondo term (ID and Label):
MONDO:0000447 autosomal dominant polycystic liver disease http://purl.obolibrary.org/obo/MONDO_0000447
Xref that should be fixed (ID and label):
MONDO:0000447 autosomal dominant polycystic liver disease has ExactMatch to DOID:0050770 https://www.disease-ontology.org/term/DOID:0050770/
The DOI term name polycystic liver disease is represented by two xrefs
GARD:9457 https://rarediseases.info.nih.gov/diseases/9457/index  'polycystic liver disease' Other Names: 'Isolated polycystic liver disease'; 'Isolated autosomal dominant polycystic liver disease'; PCLD
OMIM:174050 https://www.omim.org/entry/174050 'Polycystic liver disease 1'
So it looks like the DOID is representing both MONDO:0000447 autosomal dominant polycystic liver disease http://purl.obolibrary.org/obo/MONDO_0000447 and  MONDO:0008265 http://purl.obolibrary.org/obo/MONDO_0008265 Polycystic liver disease 1.
I think because of this association is causing confusion with the associated Exact synonyms 'isolated polycystic liver disease' and 'isolated congenital polycystic liver disease' as they are being associated as has Exact synonym to MONDO:0008265 polycystic liver disease 1 when I think these synonyms are better placed in MONDO:0000447 autosomal dominant polycystic liver disease?
Mondo term (ID and Label):
MONDO:0008265 Polycystic liver disease 1 http://purl.obolibrary.org/obo/MONDO_0008265
Xref that should be fixed (ID and label):
Has an ExactMatch to UMLS C4255088, however this seems to be obsoleted, as it is no longer found so should be removed
Also, has ExactSynonym 'isolated polycystic liver disease', which I do not think belongs to MONDO:0008265 Polycystic liver disease 1 - rather the parent term MONDO:0000447 autosomal dominant polycystic liver disease
Xref that should be fixed (ID and label):
Remove ExactMatch to the obsoleted UMLS:C4255088 from MONDO:0008265 Polycystic liver disease 1
Remove synonym 'isolated polycystic liver disease'
Add as ExactSynonym to MONDO:0000447 autosomal dominant polycystic liver disease http://purl.obolibrary.org/obo/MONDO_0000447- see below for more info)
Also reconsider  'isolated congenital polycystic liver disease' as an ExactMatch for MONDO:0008265 Polycystic liver disease 1
Why could this isolated polycystic liver disease be added a synonym to MONDO:0000447 autosomal dominant polycystic liver ?
MONDO:0000447 autosomal dominant polycystic liver disease has ExactMatch to another UMLS C0158683: Polycystic liver disease http://linkedlifedata.com/resource/umls/id/C0158683, looking at one of the alternative labels (page 4….) it lists  ’Isolated polycystic liver disease from MeSH (no id).
MONDO:0000447 autosomal dominant polycystic liver disease has an ExactMatch https://meshb.nlm.nih.gov/record/ui?ui=C536330 this includes  'Entry Term(s) Isolated autosomal dominant polycystic liver disease; Isolated polycystic liver disease'.  Adding 'isolated polycystic liver disease'  is also supported by ORPHA:2924 Isolated polycystic liver disease being ExactMatch in MONDO:0000447 autosomal dominant polycystic liver disease
Other comments:
links to 'polycystic liver disease' DBxref #3264

Great thank you @nicolevasilevsky @sabrinatoro - I could be well off the mark with my suggestions but sometimes it is hard to find logic in a magic-merry-go-round of disease terms. I  am hoping you can help untangle  how ADPLD and PLD1 are being defined, no pressure! :)

I made  'isolated polycystic liver disease' and 'isolated congenital polycystic liver disease' broad synonyms on 'polycystic liver disease 1'
I made UMLS:C4255088 equivalentObsolete
I think that addresses everything, please let me know if not. Thanks!


More bridging tests

This PR includes tests for:

invalid connector names (ie: using / in connector name) - it works
invalid patterns in address rule in connector (ie: queue*) - it's failing added a unit test too, maybe the pattern needs to be modified ( could you check that @lulf )
Restart broker to ensure router reattached to broker and you can send/recv messages - it works
try to forward messages when the remote broker is unavailable , and check how the messages are automatically forwarded when the remote broker comes back up - it works

@enmasse-ci run tests testcase=io.enmasse.systemtest.isolated.bridging.**

:heavy_exclamation_mark: Build Failed :heavy_exclamation_mark:

@enmasse-ci run tests testcase=io.enmasse.systemtest.isolated.bridging.**

:heavy_check_mark: Test Summary :heavy_check_mark:
TEST_PROFILE: systemtests-pr
TEST_CASE: io.enmasse.systemtest.isolated.bridging.**
TOTAL: 12
PASS: 12
FAIL: 0
SKIP: 0


webchuck ACE syntax highlight

[ ] All 1.5.x.x new syntax
[ ] Hex numbers

Following up on this, would we want this in the Monaco IDE editor, Ace Editor, or some variant of Prism.js? @Kizjkre

Oh yeah, I added eon and a couple other things manually to the syntax highlight list of Monaco here: https://github.com/terryzfeng/webchuck-ide/blob/871695ac1505779a9f87aae8f49e0f03e38d3e17/src/components/monaco/chuck-lang.ts#L66
Hex is handled here:
https://github.com/terryzfeng/webchuck-ide/blob/871695ac1505779a9f87aae8f49e0f03e38d3e17/src/components/monaco/chuck-lang.ts#L193-L196
I guess it's all good on the IDE then :)


How to convert a type so that it uses turbofish syntax?

I'd like to get Foo::<T> from Foo<T> given a Ty.
Is this possible at the moment and if not, is there an easy workaround?

Macros should always use <Foo<T>>::torkleyy instead of turbofish.

@dtolnay Thanks a bunch!


Issue in the #100DaysOfCode talkpython course Days 28-30 regex

Hi guys
In the recording for 'findall' section, Bob mentions in one of the exercises, '\w+' as one or more characters. Shouldn't that be one or more 'words'?
Recording time: 1:17
Cheers

You got me doubting for a sec there, but it is indeed a character class:
https://docs.python.org/3.8/library/re.html
\w
For Unicode (str) patterns:
Matches Unicode word characters; this includes most characters that can be part of a word in any language, as well as numbers and the underscore. If the ASCII flag is used, only [a-zA-Z0-9_] is matched.
Or letting the code speak:

import re
re.match(r'\w', 'a')
<_sre.SRE_Match object; span=(0, 1), match='a’>

Thanks for keeping a critical eye :)

Thank for the clarification Bob.
Cheers


chore: Update outdated LICENSE year

What kind of change does this PR introduce?
Updated the outdated copyright year to the present.

Hm I'm not a legal expert so I'm not sure how this stuff works, but my first search result seems to suggest that changing the year is not necessary. I'll wait for someone with more experience to comment

@anand2312 is right, changing the year isn't necessary, or at least not critical at least from a compliance perspective


[FIX] using snakecase on params

Hey I've took some time to rename the params following what you mentioned on the issue linked to this request, hope that this fixes are enough. i've checked and it seems to get all of the params used in all modules.
This Pull request closes #27
PR content:

renaming in all params.

Ending
Feel free to discuss ths changes with me, I'm available to make any change you feel necessary.
Hope we have a merge! :rocket:

You're welcome :smile:


Publish the runing WSL version

Is your feature request related to a problem? Please describe.
As WSL 2 has features that WSL 1 not, would be useful to know inside the running shell which version is and allow execution of code depending on it.
Describe the solution you'd like
Does not matter which solution is decided, but a reliable and official mechanism to get the WSL version runing on the current shell.
Describe alternatives you've considered
This proposed superuser answer. It works, it is reliaable, but seems not pretty elegant.
Additional context
N/A

/dupe #4555


added json-prettier

Description
Added a package for converting JSON/JS Objects to pretty JSON
The package will paste the pretty JSON automatically from your copied text on your clipboard
Checklist

[x] I read the extension guidelines
[x] I read the documentation about publishing
[x] I ran npm run build and tested this distribution build in Raycast
[x] I checked that files in the assets folder are used by the extension itself
[x] I checked that assets used by the README are placed outside of the metadata folder

The reason I was creating this because the existing one works differently I
truly believe mine would give a better DX
For 2 main reasons

No window that shows you the output, it’s automatically being pasted
where you need it
Handles also JS objects

On Wed, 11 Jan 2023 at 3:35 PM, Per Nielsen Tikær @.***>
wrote:

Hi @lacherogwu https://github.com/lacherogwu 👋
Thanks for your contribution 💯
Would it make sense to move this to one of the already existing
extensions, like this https://www.raycast.com/destiner/json-format
instead?
—
Reply to this email directly, view it on GitHub
https://github.com/raycast/extensions/pull/4198#issuecomment-1378761636,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AL4G4XSKXSDMEKZDBSSXXF3WR2ZINANCNFSM6AAAAAATVLP5GA
.
You are receiving this because you were mentioned.Message ID:
@.***>

You could still add another command to the existing extension, it might be a bit confusing for the end user to pick the "right" one since they have a lot of similarities as in they don't trying to do the same "job"

TBH I don't think the existing JSON Format doing good job, I've never seen a case where you need it the formatted value in a separate window, you always need to interact with this.
I think a better suggestion would be to remove/update the old extension because the command they provide is simply unnecessary and don't provide the ideal DX

I'm going to side with @pernielsentikaer here, adding it to an existing extension would probably be better for existing thousands of users, as they'll get your amazing update in an instant!!
However this is something you can figure out and decide for yourself.
There's one thing I wished your extension did. Instead of only "directly pasting formatted JSON to an active app", ability to store the formatted JSON to clipboard for later would be nice.
Anyways great work on the extension. The previous extension can definitely be improved upon as it was a bit annoying to work with.

Hi @lacherogwu 👋
Sorry for the long response time here 😊
We're not going to allow extensions that directly pass unsanitized input to any eval- or exec-like commands; your eval function can be very harmful if you have anything else than a JSON object in the clipboard. This is generally bad practice and can cause serious issues.

Same as there are multiple vs code extensions(on your store)
None of the vscode extensions does the same; it's 100% different purposes, whereas this one solves the same purpose.

Many extensions have a form and clipboard command, which would be the way to go - I'm sure @Destiner would be up for enhancing it too

Hi @pernielsentikaer
This is a very good point.
What is I will sanitize it first and make sure only javascript object can be passed before evaluating
or even find a more creating way instead of eval() to read a jsObject from a string and convert it to JSON
Would you approve this PR?
let me know if it is worth my effort.

What do you say @pernielsentikaer

@pernielsentikaer
#4654

I've created a rough draft update, feel free to change things and please add @lacherogwu as a contributor as well.

Hey thanks @Aayush9029
sure no worries, as long as it will be part of the tools I'm good :) not looking for any credit or something like that 😄
About the code, I saw that you removed the eval part, which is okay, but then need to find a better solution to parse js object as a json
since you mention there "Please copy a valid JSON/JS Object, but you are not handling JS Object in any way.

Did you see @lacherogwu's last message @Aayush9029 😊

@pernielsentikaer oh, yeah we can remove the JS Object.
On the error line

@pernielsentikaer feel free to quick merge https://github.com/raycast/extensions/pull/4745
This should fix the issue raised by @lacherogwu 😄

What you did is great, but the main difference here was that you can paste also a JS object, which will be a game-changer for many devs out there...
but you just removed it...

@lacherogwu Fair enough :)
We'll figure out a way to add said feature without using eval, should be simple as importing a library 😭 (surely)
And we'll get to change the error back to "JSON/JS Object" 🎉


adding map search and refactoring

This is a prototype PR for map searching functionality. It implements a new Place class that lets you give a string which will return a given map for that string. It tries to be smart about calculating zoom levels though it lets you specify this explicitly if you want.
I'll add in tests if the basics look good here. I had to do some refactoring in order to get the imports working properly. I hope that's OK! Also added an example to show off how this would work.
LMK!

This looks great, thanks! A couple of questions:

Do you think plot_map could be generalized to take inputs other than a Place object? I'm thinking the output from bounds2img. Not crucial for this PR though.
The tests are failing on geopy, can you add it to the testing suite to make sure things are back in business?
Could you add tests for the new functionality?

Thanks!

Oh yeah - the tests will definitely break because I wanted to make sure you were OK with the API change first :) I'll take a pass at fixing those and adding new tests too

(FYI, outta town for a few days but I'll get back to this when I get back)

yo @darribas - just added an example that demoes both the Place functionality as well as bounds2img along with plot_map. I also refactored a little bit and added tests. LMK!
BTW: it'd be cool if there were a little sphinx documentation with this package!

Coverage increased (+1.7%) to 93.506% when pulling af52670ed5264c5e8c18237cec2f6f5a11d7fd64 on choldgraf:map_search into ce86317f0fcf375868a91a42d5aec6e32a49b4a9 on darribas:master.

not sure what the 3.4 error is about...

Coverage increased (+0.5%) to 92.262% when pulling e1a2b2d91d2fda9cf8674dd468cb5c58191fa433 on choldgraf:map_search into ce86317f0fcf375868a91a42d5aec6e32a49b4a9 on darribas:master.

ping @darribas , any idea what the error in python 3.4 means? Seems like a dependency may not be installed properly?

Thank you very much @choldgraf this is great!!!
A couple of points:

On the Sphinx, I agree, it'd be fantastic. Do you have some experience on setting it up? My sense is, once it's going, it's not hard to maintain. Content-wise, we could start by dumping what's in the notebook tutorial. @ljwolf might have some tips on this?

On the errors, they seem to be two different ones:

The first is to do with GDAL it seems. From here, it is suggested to try conda install icu=58.*. It might be a solution?
The second one, could it be because it's an import from the tests (it does say it can't find it), so maybe something like from .. import tile_providers? I can't test right now because I don't have access to a development machine but it might be that? I'm not sure why it doesn't fail on 3.5 though...

on sphinx, I can help set that up. Will do so after this PR is finished up.
For the other stuff, I can play around with travis etc. I've found installing the geo libraries (because of their dependence on other C libraries) to be really finnicky, so maybe there's just a particular set of dependencies needed to get it working.

Sounds good @choldgraf. Let's leave Sphinx until we have the new functionality ready. On the fails, I'd say give it a go but if it passes on 2.7/3.5 we could say that's the supported version going forward? It'd be good to know why it fails though...

@choldgraf Just checking in here. Have you had a chance to look into the Python3.4 problems? I've identified a bug that precluded bounds2raster to work and the PR (#13) is showing very similar error (although it's libnetcdf rather than libgeos). Upon quick inspection, I've realised 3.5 installs) a much newer version of rasterio than 3.4. So I'm tempted to skip 3.4 as part of the supported versions, unless you'd found a better approach.
On this, I'm planning on cutting a small release for that fix but, since the release machine will be oiled, I'd be happy to try to get a new one with all of your improvements shortly after. What would be needed for that?

yo! sorry I got bogged down in the summer conference cycle. I'll spend some time on this today or tomorrow to see where we're at :-)

hmm....so, it appears that rasterio is trying to import the wrong version of libgeos only on python 3.4. At least as far as I can tell, this is not a contextily issue so much as a rasterio issue. E.g., I just tried:
conda create --name python34 python=3.4
conda install -c conda-forge cartopy rasterio
pip install -e path/to/contextily

and then doing import rasterio as rio fails with the same error...

Cool! So we're good to go on this front then? Maybe just clarifying that 3.4 is not supported. Is this PR otherwise good to merge? Keen on trying to cut a release before the start of the (UK) semester (what can go wrong?).

to my knowledge...yeah this should be good to go :-)  I think it's OK to drop 3.4 support...you can always see if this creates a bunch of issues or something but I doubt many users will really strongly want to use 3.4 over 3.5/6

Cool! One more thing, could you please add an example to the guide? That's the resource N.1 people use to check how to do things :) If pressed, we can merge and add later, but I'd rather have it from the beginning.

how does that look? (just added a little section to the guide)

Coverage increased (+0.5%) to 92.262% when pulling 7c7e99067da01a6d07734e7ecb815a3d89784fcb on choldgraf:map_search into ce86317f0fcf375868a91a42d5aec6e32a49b4a9 on darribas:master.

Coverage increased (+0.5%) to 92.262% when pulling 7c7e99067da01a6d07734e7ecb815a3d89784fcb on choldgraf:map_search into ce86317f0fcf375868a91a42d5aec6e32a49b4a9 on darribas:master.

yo - just checking to make sure there's nothing I should be working on here...

Wow, ok, seems like bundling github emails in inbox makes them real hard to track. Sorry I missed this tag.
I've stumbled through most of the sphinx I've seen before, so I wouldn't've had too much to contribute there. Sorry!
On testing, I'm not sure what the design target for contexily is, but I'd only run tests on 3.6 & latest 3. As far as I can tell, the only "long-term" python in the 3 line is 3.6. They claim it'll get bugfix support til 2021, but 3.5 and 3.4 have no planned releases.

Sorry, I don't think so. I've been snowed with the beginning of the academic year (UK time) but will try to cut a release early next week!

no problem - I'm just going through my open PRs and making sure none of them are blocking because of me!

it would be so useful to have this functionality @darribas !! one of my students is working through this and could use it right now! @wino6687 totally get busy schedules and so appreciative to have libraries like this to use. :)

@choldgraf if you do have a second, I think one thing you might want to do with this PR would be to drop line 10 from the .travis.ci file so that testing is dropped for python 3.4. In the discussion here, it seems that's the consensus, so removing it from the CI would add a marker that this is ready to go.
@darribas would have final say here, tho, but that'd at least make this a single button push to finish the issue of adding the change & having the "right" CI.

@darribas gimme the word and I'm happy to do this :-)

Sorry again for the delay! Thanks @ljwolf for chipping in and @lwasser for the kind words. Yeah, let's go ahead and remove 3.4 from the CI. I'm going to merge and remove it myself and it's a very minor thing and I'm on it at the minute :-)

OK, so with e600b9f we're not supporting 3.4 anymore and tests are back on green light!


[MOB-845] Test EmptyInAppManager

+1.
Although I don't think this class needs any tests.

Yeah, we aren't expecting to change it from as is, but it's good to have the coverage on the reporting side.


Request logged out

Who is this for?
Library members who are logged out
What is it doing for them?
Giving them UI to indicate they need to log in in order to request items on a work page
This is currently behind the showLogin toggle, and not yet aware of a user's logged-in state (since that is being dealt with in a separate piece of work).

@davidpmccormick is it possible to use the colour background from the design rather than grey?

@DominiqueMarshall I don't think that colour is part of our palette – I picked the closest thing (to my eyes). I know our palette is limiting as it is, but I don't think we can add new things in ad hoc. Hopefully the work @GarethOrmerod has been doing around the palette will make life easier all round.

@davidpmccormick Circling back around to this - the colour is actually a tint from the turquoise in our palette. As a means of trying out some colour exploration as part of improving the works page long term, it would be ideal to use the tint in the design rather than the grey. It might feel a bit like a special snowflake at the moment, but it would be good to try and iterate on this while we have the opportunity to!

We've got a system in place for base, light and dark versions of each colour in the palette, but we've not really made use of it so far. I'll put this in as the light tint of turquoise for now then.

That's perfect - we were just talking about a concrete starting point for expanding the colour palette being ~3 tints of the existing colours, possibly using the opportunity to group some of the blacks/greys/beiges.


Security: EJBCA's private key persistence

For this issue, we will create a doc and a script to help the system administrator export/import the keys/certificate file (.p12 file) related with the ROOT CA. For now, this issue and the feature related will be 'on hold'.

This issue is related with dojot/dojot#1305

When EJBCA create the tables in postgres db, he automatically inserts his keys (private and public) and his certificates in the database, persisting all his data.


Favicon not served in new project?

I'm running a new leptos project built with cargo leptos new --git https://github.com/leptos-rs/start-axum, but when I run cargo leptos watch it doesn't load the favicon on the site. Inspecting in chrome web tools "sources" tab it's not vended, though the pkg directory is.
The contents of the site appear to be built correctly.
❯ tree target/site
target/site
├── favicon.ico
└── pkg
    ├── example.css
    ├── example.js
    └── example.wasm

Any ideas what I'm doing wrong?

No idea. If you load localhost:3000/favicon.ico (or whatever port you're at), does it serve the favicon? The default starter does server the file from public/favicon.ico, so not sure what you changed that stopped that from happening.

Closing as stale, please open a new issue if you're still experiencing htis

I know this issue is closed... but I had the same problem with the same leptos init and site root directory.
I discovered that it was due to a browser compatibility issue (I was using Brave initially), and switching to Chrome proper resolved. In Brave, the browser wasn't calling the favicon endpoint on page load, but if you called the route manually the icon was fetched/rendered. Chrome does make the call to fetch the favicon, though.


Restricted users only see repos in orgs which their team was assigned to

Sponsored by Kithara Software GmbH

I was unable to create a backport for 1.20. @6543, please send one manually. :tea:
go run ./contrib/backport 28025
...  // fix git conflicts if any
go run ./contrib/backport --continue

I was unable to create a backport for 1.21. @6543, please send one manually. :tea:
go run ./contrib/backport 28025
...  // fix git conflicts if any
go run ./contrib/backport --continue


[PE-D][Tester D] User Guide: Different Heading Formats for Method 1 and Method 2

Minor cosmetic bug found - "Method 1" and "Method 2" in Section 2.17 of User Guide are of different heading formats. See the top and bottom of the screenshot below.

Labels: type.DocumentationBug severity.VeryLow
original: lutfir-cpu/ped#1

Resolved


Don't save fp8 q/k/v/out tensors when using bf16 bprop

Description
When using FP8_DPA=1 NVTE_FP8_DPA_BWD=0, the backprop uses BF16 q/k/v/out tensors and the fp8 q/k/v/o are not used. So we should avoid saving them for backprop, which reduces the peak memory footprint.
Fixes # (issue)
Type of change

[ ] Documentation change (change only to the documentation, either a fix or a new content)
[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Infra/Build change
[ ] Code refractor

Changes
Please list the changes introduced in this PR:

Change A
Change B

Checklist:

[ ] I have read and followed the contributing guidelines
[ ] The functionality is complete
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes

/te-ci pytorch


signal: custom exit code status for interceptor

fixes #5625

Outline and Challenge
This issue was required lnd to exit with status code 1 where there was an request to shutdownRequestChannel
https://github.com/lightningnetwork/lnd/blob/52767a7567afe1a96e275a8659f77467ac0fe72f/signal/signal.go#L100-L102
The challenge was that we had to do an os.exit(1) after an graceful shutdown.
An graceful shutdown occurs when all the deferred go function in the Main() function clean up, but there is no way that we can pass the data or tell the function that cleans up last to exit with a particular status code.
Approach
I pulled the defer function of Main() outside from lnd package and put it under cmd/lnd.go where the Main() get's called (giving us parental access to shutdownInterceptor) and added an additional parameter to Interceptor struct so that we can pass data when an graceful shutdown has occurred.
I am passing a pointer reference in-order to retain the modifications (setting exit code) in the Intercept struct in goroutines.

Before
After

Steps to test this PR

run bitcoind server
run the following ./lnd-debug --rpclisten=localhost:10001 --listen=localhost:10011 --restlisten=localhost:8001 --debuglevel=debug --healthcheck.chainbackend.backoff=1s --healthcheck.chainbackend.interval=1m0s --healthcheck.chainbackend.timeout=3s
create a wallet  ./lncli-debug --rpcserver=localhost:10001 --macaroonpath=data/chain/bitcoin/simnet/admin.macaroon unlock
Press ctrl+c and shutdown your bitcoind server
Wait for 1 min, lnd will exit gracefully with an exit status code 1

Pull Request Checklist

[x] All changes are Go version 1.15 compliant
[x] Your PR passes all CI checks. If a check cannot be passed for a justifiable reason, that reason must be stated in the commit message and PR description.
[ ] If this is your first time contributing, we recommend you read the Code Contribution Guidelines

[ ] The code being submitted is commented according to Code Documentation and Commenting
[ ] Commits have a logical structure according to Ideal Git Commit Structure

[ ] For new code: Code is accompanied by tests which exercise both the positive and negative (error paths) conditions (if applicable)
[ ] For bug fixes: If possible, code is accompanied by new tests which trigger the bug being fixed to prevent regressions
[ ] Any new logging statements use an appropriate subsystem and logging level
[x] For code and documentation: lines are wrapped at 80 characters (the tab character should be counted as 8 characters, not 4, as some IDEs do per default)
[x] A description of your changes should be added to running the release notes for the milestone your change will land in.

Hi @carlaKC ! I have solved the issue, ensure the CI checks pass with a PR on personal fork :smiley:

Hey @carlaKC Implemented and amended the suggested changes!

Force pushed from  1057f6d to 1764854 to fix a lint issue reported by Travis.

Hey @carlaKC , I have implemented the recommended changes and have resolved the conversations :smile:

@DarthBenro008 any updates here?

@darthbenro008, remember to re-request review from reviewers for your latest update

@darthbenro008, remember to re-request review from reviewers for your latest update

@darthbenro008, remember to re-request review from reviewers when ready

@darthbenro008, remember to re-request review from reviewers when ready

Closing due to inactivity.

Replaced by #8659


Support for opening eLife's reference articles

This issue is the result of a pivot during sprint 7, where I realised I could for now simple reuse some of substance's bundling code to bundle our reference manuscripts as a 'vfs' file, which for now allows them to be opened without making any substantial changes to Texture.
The pro of this approach is that I can defer the full integration with the storage-manager until later in the project and for now focus on the goal of getting our reference articles to display correctly.
DoD:

[x] Reference manuscripts can be opened using the 'archive=' query string option and displayed.
[x] Staging version of Libero Editor updated to support opening reference manuscripts.

Fixed under commits:
libero/editor: 0c0977c4b0e3dd9d6c14a478d19ccba4d64e7732
libero/texture: f00ae012ed6cced7cc6907557c741b596af5aacc
I also raised the following new issues, which cover refactoring some workarounds that I put in to get things working.
libero/texture#2
libero/texture#3


F9 doesn't work on Ubuntu 16.04

On the settings page when I push any key I see undefined in keyboard shortcut field

Ubuntu 16.04
Google Chrome 54.0.2840.59 (64-bit)

Can confirm. Dectection of Ctrl, Shift and Alt works

I believe this is probably related to #16 , which was fixed a while ago. I think the extension is outdated in the Chrome App Store, or else you would have received the update by now.
@auchenberg can you resubmit this to the Chrome store?

Version 1.1.5 has been pushed to the Chrome store. Sorry for the delay.

No effect.

removed old version from Chrome
reboot the system
install new version from Chrome store

Still "undefined"

It works now!
Thanks a lot!

Welcome @4selin ! How did you receive the update? Did you clone this repo and add to Chrome? I think we need @auchenberg to push yet another update to the Chrome store.

I have reinstalled it from chromes webstore and had no problems anymore.


Add RAM used for Bundles that use CacheDataset

Some of the bundles use CacheDataset, but do not provide any information on how many RAM are required. For a large dataset, caching all data need large RAM otherwise error will be raised. It would be hard to debug when meeting this kind of error because the error message is not informative, for example:
8.72s/it]WARNING:torch.distributed.elastic.multiprocessing.api:Sending process 1332 closing signal SIGTERM
ERROR:torch.distributed.elastic.multiprocessing.api:failed (exitcode: -9) local_rank: 0 (pid: 1331) of binary: /usr/bin/python

Therefore, I think we should add related information in README, and provide some suggestions for users that do not have enough RAM.

Related bundles include:

pathology_nuclei_classification @KumoLiu
pathology_nuclei_segmentation_classification @KumoLiu
endoscopic_tool_segmentation @binliunls
spleen_ct_segmentation @heyufan1995
spleen_deepedit_annotation @tangy5
swin_unetr_btcv_segmentation @tangy5
pathology_nuclick_annotation @tangy5
wholeBody_ct_segmentation @tangy5
pancreas_ct_dints_segmentation @dongyang0122

May need your help to supplement the information of how many RAM is required to run the bundle training with default settings (cache rate) , and you can post the data within this ticket, and I will submit a PR to address it, thanks in advance!
For bundles that use different cache rate in multi_gpu_train.json and train.json, I think we should unify the settings to avoid complex explanations.

To sum up according to discussions as well as @zephyrie 's comments in PR: #406 #399 , I think we need to add two sections into README:
1. (optional)  The template is like:
Memory Consumption

Dataset Manager: CacheDataset
Data Size:
Cache Rate:
Single GPU - System RAM Usage:
Multi GPU (GPUs) - System RAM Usage:

2. (necessary on bundles use CacheDataset) The template is like:
Memory Consumption Warning
If you face memory issues with CacheDataset, you can either switch to a regular Dataset class or lower the caching rate cache_rate in the configurations within range $(0, 1)$ to minimize the System RAM requirements.
Hi @zephyrie @Nic-Ma @daguangxu @dongyang0122 @tangy5 what do you think?

That looks good! My only suggestion is to have the number of GPUs in the parenthesis.  E.g. "Multi GPU (8 GPUs)".
Also, I'll also update our best template to include this section.

The template is well-structured and suitable.


test: Add Schema checks to Table tests

Closes #124.
Summary of Changes
Add Schema checks to Table tests

🦙 MegaLinter status: ✅ SUCCESS

Descriptor
Linter
Files
Fixed
Errors
Elapsed time

✅ PYTHON
black
32
0
0
1.14s

✅ PYTHON
mypy
32

0
2.15s

✅ PYTHON
ruff
32
5
0
0.07s

✅ REPOSITORY
git_diff
yes

no
0.03s

See detailed report in MegaLinter reports
Set VALIDATE_ALL_CODEBASE: true in mega-linter.yml to validate all sources, not only the diff
MegaLinter is graciously provided by

tests/safeds/data/tabular/containers/_table/test_rename.py:
This test should also check that the old column name is not included in the schema anymore.
Currently, such a test would fail, see (issue is being created right now).

tests/safeds/data/tabular/containers/_table/test_rename.py:
This test should also check that the table's schema is not changed by sorting.

This test should also check that the old column name is not included in the schema anymore.

In this case renaming a column with the same name (which we know is not that useful, but should still be possible) would give an error

This test should also check that the old column name is not included in the schema anymore.

In this case renaming a column with the same name (which we know is not that useful, but should still be possible) would give an error

Since it's just a test, we can simply choose the test case so that this doesn't happen.
Alternatively, the test could check whether either the old name is not included in the schema anymore or name_from == name_to.

This test should also check that the old column name is not included in the schema anymore.

In this case renaming a column with the same name (which we know is not that useful, but should still be possible) would give an error

Since it's just a test, we can simply choose the test case so that this doesn't happen. Alternatively, the test could check whether either the old name is not included in the schema anymore or name_from == name_to.

When applying this requested change codecov isn't 100% anymore, because the line 862 in Stdlib/src/safeds/data/tabular/containers/_table.py isn't tested.

This test should also check that the old column name is not included in the schema anymore.

In this case renaming a column with the same name (which we know is not that useful, but should still be possible) would give an error

Since it's just a test, we can simply choose the test case so that this doesn't happen. Alternatively, the test could check whether either the old name is not included in the schema anymore or name_from == name_to.

When applying this requested change codecov isn't 100% anymore, because the line 862 in Stdlib/src/safeds/data/tabular/containers/_table.py isn't tested.

I see.
Thinking more about this, I think the cleanest would be to replace all assertions in test_should_rename_colunm with these two lines:
assert renamed_table.schema.column_names == [column_one, column_two]
assert renamed_table.column_names == [column_one, column_two]


EC2 default for Security Group is going to Custom instead of Standard

v0.22.0-rc2
Steps:
Build an EC2 machine
Results:
When I get to Security Group it is automatically selecting Custom instead of Standard radio button
Expected:
Should default to Standard

build from master - June 11th (morning)
Verified fixed


How to build and run the beginning project?

I want to validate the throughput in the beginning project and the following are my steps:

git pull futurewei-cloud master:master
git reset --hard febe03f (Initial commit (May 21 2020) )
follow the readme to install dependencies and build the project but it failed due to some errors. Here are them:

error: ‘seastar::shard_id seastar::reactor::cpu_id() const’ is deprecated: Use this_shard_id
when i fix the first error, then come another error: ‘compat’ in namespace ‘seastar’ does not name a type

I wonder if it is because of the verison of seastar-rd. If so, which version(commit id) should I choose?

Hi,
You should use a version of seastar-rd as of the same time as the commit you have in the platform. I'd try https://github.com/futurewei-cloud/chogori-seastar-rd/commit/671999e557606adb60703e0db332f951b5f51179


Feat: Decrease the Navbar Content

Describe the feature
It looks very bad because the navbar has many options i would like to decrease the navbar contents
Add ScreenShots

Record

[X] I agree to follow this project's Code of Conduct
[X] I'm a GSSOC'24 contributor
[X] I want to work on this issue

Describe the feature
It looks very bad because the navbar has many options i would like to decrease the navbar contents
Add ScreenShots

Record

[X] I agree to follow this project's Code of Conduct
[X] I'm a GSSOC'24 contributor
[X] I want to work on this issue

yes do it! use some expanding list type of elements!

Hi. Under GSSOC'24, I would like to work on this issue.
Please Assign me this task.
I am looking forward to do this in min. time with max. efficient.


Installation micro-sam for macOS M1

The troubleshooting didn't work for me, but I have some adaptions for the installation on the M1 that worked:
git clone https://github.com/computational-cell-analytics/micro-sam
mamba create -c conda-forge python=3.10 pip -n sam
conda activate sam
mamba install icu=70.1
mamba install qt-main=5.15.4
mamba install pyqt=5.15.4
mamba install pytorch::pytorch torchvision torchaudio -c pytorch
mamba install -c conda-forge python-elf tqdm
mamba install -c conda-forge napari
cd micro-sam
pip install git+https://github.com/facebookresearch/segment-anything.git
pip install -e .

I needed to install icu, qt-main and pyqt before installing everything else.
SAM-yml.zip

Thanks for reporting this @GesineMueller! I hope that we will have a more stable way of installing micro_sam on mac soon.
In the meantime I will leave this issue open and have linked it in the troubleshooting section of the (new!) installation documentation: https://computational-cell-analytics.github.io/micro-sam/micro_sam.html#from-source

These issues are fixed now, PyTorch can be installed normally for Mac M1 etc. now.


fix: bad link of dfget example

Signed-off-by: lowzj<EMAIL_ADDRESS>
Ⅰ. Describe what this PR did
Ⅱ. Does this pull request fix one issue?

Ⅲ. Why don't you add test cases (unit test/integration test)? (你真的觉得不需要加测试吗？)
Ⅳ. Describe how to verify it
Ⅴ. Special notes for reviews

Codecov Report

Merging #253 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #253   +/-   ##
=======================================
  Coverage   65.26%   65.26%
=======================================
  Files          30       30
  Lines        1592     1592
=======================================
  Hits         1039     1039
  Misses        522      522
  Partials       31       31

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update d3a87f8...ec470fe. Read the comment docs.


Add Lammers2021

Pull Request
This PR is for a

[x] New Publication(s)
[ ] Correction

For the following list(s):

[ ] ancientmetagenome-anthropogenic (README)
[x] ancientmetagenome-environmental (README, ask @thedir-team-dirt for advice)
[ ] ancientmetagenome-hostassociated (README, ask @thedir-team-bugparty for advice)
[ ] ancientsinglegenome-hostassociated (README, ask @thedir-team-pathopeeps for advice)

New Publication
Publication Information
This pull request is to add samples from the following publication(s): 10.1038/s42003-021-01710-4
This is to close #372
Checklist

[x] Publication is published (preprints currently not accepted)?
[x] Checked the publication is not already in the database?
[x] Checked samples in this publication are not previously published data (newly re-sequenced metagenomes are OK!)?
[x] Samples are shotgun metagenomes (hostassociated-singlegenome may also contain whole-genome enriched data)?
[x] Checked the list follows conventions as described in the corresponding sample type's README file (e.g. using ERS/SRS accession codes for ENA/SRA)?
[x] Changelog is updated to include the publication under 'Added'?
[x] Pull request has passed validation checks (see automated comment from github-bot)?
[x] Review requested from corresponding team (see list of lists above for each team)?
[ ] (If applicable) Made a separate PR to add new categories to controlled lists (stored under /assets/enums, e.g. material or archive)? If so the corresponding PR is here:

If you do not know how to check errors in failed validation checks, expand here

Correction
This PR is for

[ ] ancientmetagenome-hostassociated
[ ] ancientsinglegenome-hostassociated
[ ] ancientmetagenome-environmental
[ ] ancientmetagenome-anthropogenic

Reference
This pull request is to correct samples from the following publication(s):
This is to close
Description
The issue is:

Checklist

[ ] Checked the corrected entries follow conventions as described in the corresponding sample type's README file (e.g. using ERS/SRS accession codes for ENA/SRA)
[ ] Changelog is updated to include the publication under 'Changed'?
[ ] Pull request has passed validation checks (see automated comment from github-bot)?
[ ] Review requested from corresponding team (see list of lists above for each team)?

Note that there is no lookup file for the ERS codes to samples, but these are correct based on my lab-book records.

Feel free to merge @pheintzman !

Note that there is no lookup file for the ERS codes to samples, but these are correct based on my lab-book records.

Actually, there is on the ENA! https://www.ebi.ac.uk/ena/browser/view/PRJEB38213 make sure show column selection has secondary_sample_accession, sample_alias and sample_title. If anythign this is my preferred way of metadata sharing ;)


Do you support Bluetooth 4.0 LE devices?

I wanted to know if you support Bluetooth 4.0 LE devices?

I do not believe the library does.

Can you share the code about "setup an input stream on the read characteristic, and an output stream on the write characteristic"

My last comment was more than 2 years ago, and back then I did not investigate this library further.
Maybe they even implemented BLE support in the meantime.
If not, have a look at LTSupportAutomotive's LTBLESerialTransporter class. It's Objective-C, but should not be too hard to translate to Swift.

Thank you for the reply , okay please explain me little more about the third point "setup an input stream on the read characteristic, and an output stream on the write characteristic" if possible

As I've said, have a look at the LTBLESerialTransporter class.
A very rough overview is like this:
Create subclasses from NSInputStream and NSOutputStream.
Whenever the "read characteristic" is updated, take the value and update your input stream's internal buffer, and call the appropriate NSInputStream delegate methods (at least stream:handleEvent: with the NSStreamEventHasBytesAvailable event).
Whenever your output stream has data available, write it to the "write characteristic" (you might need to split it, because Bluetooth LE has a maximum limit for each write).
If the write was successful, call the appropriate NSOutputStream delegate methods (at least stream:handleEvent: with the NSStreamEventHasSpaceAvailable event).


in the mxnet0.9.4 has a bug in python35 win10, but in python27 is normal

fix into https://github.com/dmlc/mxnet/pull/5268
wait merge

thanks!


Variable name, IP and port obfuscation

This adds automatic variable name obfuscation to all payloads and encoder stubs, as well as IP and port obfuscation as an option. To deal with the added size obfuscation can bring, a obfuscate-small option is also added to allow for much smaller obfuscated payloads.
A new 'lang' class member has been added for the Shell, BindShell, and ReverseShell classes. This is necessary because certain languages require certain rules to be met when it comes to variable naming or expression expansion that most languages do not. This could also be helpful in the future if we need to mutate the payload based off of what language it is.
All variables in bind shells, reverse shells, and encoder stubs have been replaced with VAR#, with VAR1 being the first variable in the payload, VAR2 being the second, and so on. Similarly, 'magic numbers' for loops (ie while(1)) have been replaced with with NUM# to add a tiny bit more randomness to some payloads. This allows obfuscation.randomize_vars() to correctly identify, and randomly name all variables in the selected payload.
If you read my commit messages, or look closely, you'll notice I haven't updated the stager payloads to take advantage of variable randomization. This intentional, I realized partway in to do so would require a bit of a refactoring of the stagers' code, and I believe that is outside the scope of this PR. I have some other ideas for stagers I would like to incorporate along with variable randomization, if this PR gets submitted we can talk stagers then.
I have tested each bind, and reverse shell in all forms of encoding, with and without the --ipfuscation option applied before submitting this PR, so everything should work correctly. In doing such rigorous testing, I have come across a handful of connection issues with a few shells I have since fixed. These problems didn't allow the problematic shells to be used at all, and because they were extremely trite fixes, I didn't bother to open any issues or PRs for them.
Let me know if there's any mistakes I made or anything you'd like me to change. Thanks for this great project!

Hey @capnspacehook, I had the time to test your changes and from what I have tested, this is my review:
The changes are amazing, I liked how --ipfuscate and --obfuscate-small behave.
Linux payloads worked very smoothly, I had no problems with any payload, but Windows ones are broken. I hadn't  success establishing reverse shells using powershell payloads.
Have you tested them? I think it might be a powershell issue or something. I still haven't figured it out why it failed.
What I tried was:
shellpop --payload windows/reverse/tcp/powershell -H eth0 -P 8080 with or without --ipfuscate
I  think it must be something with powershell and variables.

I think I know that caused that... just fixed the reverse powershell payloads. Before I push the commit though, did the powershell bind shell work or was that broken as well?

Sorry for taking too long, I was full.
Well, I just tested bind shell and the phenomenom still ocurrs. It is like powershell only interpreted as simple text. I think it might be something with -Command handle.

That commit should fix the Powershell reverse shells, but as for the bind shell, I  couldn't figure out what the problem was. I tested the bind shell on the master branch and it was giving me the same problem... can you verify?

Hey @capnspacehook ! I have just fixed bind shell with your changes in a separate branch.
You can check it in this repo. Please push the changes to this PR so we can proceed into merging, everything looks fine now!


v0.67.2: An error occurred while Rails/ActiveRecordOverride cop was inspecting

Expected behavior
Works without error.
Actual behavior
When run rubocop in this model:
# app/models/group.rb

class Group
  def self.create(attributes)
  end

  def update(attributes)
  end
end

Throw this error:
An error occurred while Rails/ActiveRecordOverride cop was inspecting /home/rjurado/.../app/models/group.rb:8:2.
undefined method `const_name' for nil:NilClass
/home/rjurado/.asdf/installs/ruby/2.5.3/lib/ruby/gems/2.5.0/gems/rubocop-0.67.2/lib/rubocop/cop/rails/active_record_override.rb:42:in `on_def'
/home/rjurado/.asdf/installs/ruby/2.5.3/lib/ruby/gems/2.5.0/gems/rubocop-0.67.2/lib/rubocop/cop/commissioner.rb:58:in `block (2 levels) in trigger_responding_cops'
/home/rjurado/.asdf/installs/ruby/2.5.3/lib/ruby/gems/2.5.0/gems/rubocop-0.67.2/lib/rubocop/cop/commissioner.rb:106:in `with_cop_error_handling'
/home/rjurado/.asdf/installs/ruby/2.5.3/lib/ruby/gems/2.5.0/gems/rubocop-0.67.2/lib/rubocop/cop/commissioner.rb:57:in `block in trigger_responding_cops'
/home/rjurado/.asdf/installs/ruby/2.5.3/lib/ruby/gems/2.5.0/gems/rubocop-0.67.2/lib/rubocop/cop/commissioner.rb:56:in `each'
/home/rjurado/.asdf/installs/ruby/2.5.3/lib/ruby/gems/2.5.0/gems/rubocop-0.67.2/lib/rubocop/cop/commissioner.rb:56:in `trigger_responding_cops'
/home/rjurado/.asdf/installs/ruby/2.5.3/lib/ruby/gems/2.5.0/gems/rubocop-0.67.2/lib/rubocop/cop/commissioner.rb:34:in `block (2 levels) in <class:Commissioner>'
/home/rjurado/.asdf/installs/ruby/2.5.3/lib/ruby/gems/2.5.0/gems/rubocop-0.67.2/lib/rubocop/ast/traversal.rb:50:in `block in on_begin'
/home/rjurado/.asdf/installs/ruby/2.5.3/lib/ruby/gems/2.5.0/gems/rubocop-0.67.2/lib/rubocop/ast/traversal.rb:50:in `each'
/home/rjurado/.asdf/installs/ruby/2.5.3/lib/ruby/gems/2.5.0/gems/rubocop-0.67.2/lib/rubocop/ast/traversal.rb:50:in `on_begin'
/home/rjurado/.asdf/installs/ruby/2.5.3/lib/ruby/gems/2.5.0/gems/rubocop-0.67.2/lib/rubocop/cop/commissioner.rb:35:in `block (2 levels) in <class:Commissioner>'
/home/rjurado/.asdf/installs/ruby/2.5.3/lib/ruby/gems/2.5.0/gems/rubocop-0.67.2/lib/rubocop/ast/traversal.rb:92:in `on_class'
/home/rjurado/.asdf/installs/ruby/2.5.3/lib/ruby/gems/2.5.0/gems/rubocop-0.67.2/lib/rubocop/cop/commissioner.rb:35:in `block (2 levels) in <class:Commissioner>'
/home/rjurado/.asdf/installs/ruby/2.5.3/lib/ruby/gems/2.5.0/gems/rubocop-0.67.2/lib/rubocop/ast/traversal.rb:13:in `walk'
/home/rjurado/.asdf/installs/ruby/2.5.3/lib/ruby/gems/2.5.0/gems/rubocop-0.67.2/lib/rubocop/cop/commissioner.rb:46:in `investigate'
/home/rjurado/.asdf/installs/ruby/2.5.3/lib/ruby/gems/2.5.0/gems/rubocop-0.67.2/lib/rubocop/cop/team.rb:116:in `investigate'
/home/rjurado/.asdf/installs/ruby/2.5.3/lib/ruby/gems/2.5.0/gems/rubocop-0.67.2/lib/rubocop/cop/team.rb:104:in `offenses'
/home/rjurado/.asdf/installs/ruby/2.5.3/lib/ruby/gems/2.5.0/gems/rubocop-0.67.2/lib/rubocop/cop/team.rb:44:in `inspect_file'
/home/rjurado/.asdf/installs/ruby/2.5.3/lib/ruby/gems/2.5.0/gems/rubocop-0.67.2/lib/rubocop/runner.rb:273:in `inspect_file'
/home/rjurado/.asdf/installs/ruby/2.5.3/lib/ruby/gems/2.5.0/gems/rubocop-0.67.2/lib/rubocop/runner.rb:220:in `block in do_inspection_loop'
/home/rjurado/.asdf/installs/ruby/2.5.3/lib/ruby/gems/2.5.0/gems/rubocop-0.67.2/lib/rubocop/runner.rb:252:in `block in iterate_until_no_changes'
/home/rjurado/.asdf/installs/ruby/2.5.3/lib/ruby/gems/2.5.0/gems/rubocop-0.67.2/lib/rubocop/runner.rb:245:in `loop'
/home/rjurado/.asdf/installs/ruby/2.5.3/lib/ruby/gems/2.5.0/gems/rubocop-0.67.2/lib/rubocop/runner.rb:245:in `iterate_until_no_changes'
/home/rjurado/.asdf/installs/ruby/2.5.3/lib/ruby/gems/2.5.0/gems/rubocop-0.67.2/lib/rubocop/runner.rb:216:in `do_inspection_loop'
/home/rjurado/.asdf/installs/ruby/2.5.3/lib/ruby/gems/2.5.0/gems/rubocop-0.67.2/lib/rubocop/runner.rb:119:in `block in file_offenses'
/home/rjurado/.asdf/installs/ruby/2.5.3/lib/ruby/gems/2.5.0/gems/rubocop-0.67.2/lib/rubocop/runner.rb:137:in `file_offense_cache'
/home/rjurado/.asdf/installs/ruby/2.5.3/lib/ruby/gems/2.5.0/gems/rubocop-0.67.2/lib/rubocop/runner.rb:117:in `file_offenses'
/home/rjurado/.asdf/installs/ruby/2.5.3/lib/ruby/gems/2.5.0/gems/rubocop-0.67.2/lib/rubocop/runner.rb:105:in `process_file'
/home/rjurado/.asdf/installs/ruby/2.5.3/lib/ruby/gems/2.5.0/gems/rubocop-0.67.2/lib/rubocop/runner.rb:82:in `block in each_inspected_file'
/home/rjurado/.asdf/installs/ruby/2.5.3/lib/ruby/gems/2.5.0/gems/rubocop-0.67.2/lib/rubocop/runner.rb:81:in `each'
/home/rjurado/.asdf/installs/ruby/2.5.3/lib/ruby/gems/2.5.0/gems/rubocop-0.67.2/lib/rubocop/runner.rb:81:in `reduce'
/home/rjurado/.asdf/installs/ruby/2.5.3/lib/ruby/gems/2.5.0/gems/rubocop-0.67.2/lib/rubocop/runner.rb:81:in `each_inspected_file'
/home/rjurado/.asdf/installs/ruby/2.5.3/lib/ruby/gems/2.5.0/gems/rubocop-0.67.2/lib/rubocop/runner.rb:73:in `inspect_files'
/home/rjurado/.asdf/installs/ruby/2.5.3/lib/ruby/gems/2.5.0/gems/rubocop-0.67.2/lib/rubocop/runner.rb:39:in `run'
/home/rjurado/.asdf/installs/ruby/2.5.3/lib/ruby/gems/2.5.0/gems/rubocop-0.67.2/lib/rubocop/cli.rb:174:in `execute_runner'
/home/rjurado/.asdf/installs/ruby/2.5.3/lib/ruby/gems/2.5.0/gems/rubocop-0.67.2/lib/rubocop/cli.rb:75:in `execute_runners'
/home/rjurado/.asdf/installs/ruby/2.5.3/lib/ruby/gems/2.5.0/gems/rubocop-0.67.2/lib/rubocop/cli.rb:47:in `run'
/home/rjurado/.asdf/installs/ruby/2.5.3/lib/ruby/gems/2.5.0/gems/rubocop-0.67.2/exe/rubocop:25:in `block in <top (required)>'
/home/rjurado/.asdf/installs/ruby/2.5.3/lib/ruby/2.5.0/benchmark.rb:308:in `realtime'
/home/rjurado/.asdf/installs/ruby/2.5.3/lib/ruby/gems/2.5.0/gems/rubocop-0.67.2/exe/rubocop:24:in `<top (required)>'
/home/rjurado/.asdf/installs/ruby/2.5.3/bin/rubocop:23:in `load'
/home/rjurado/.asdf/installs/ruby/2.5.3/bin/rubocop:23:in `<main>'

Steps to reproduce the problem
Just running rubocop in app/models folder of my Rails project.
RuboCop version
0.67.2 (using Parser <IP_ADDRESS>, running on ruby 2.5.3 x86_64-linux)

I ran into this same issue. It looks like the fix will solve this one too, but wanted to point out that I saw a similar error on a class that uses module_function:
Create a PORO class with a save method below the module_function macro.
Saved in Rails app at: app/models/app/console.rb
# frozen_string_literal: true

module App
  module Console
    module_function  # Must exist

    def save
    end
  end
end

Failure details:
$ rubocop app/models/app/console.rb -d
For /Users/pauld/dev/badger: configuration from /Users/pauld/dev/badger/.rubocop.yml
Inheriting configuration from /Users/pauld/dev/badger/.rubocop_todo.yml
Default configuration from /Users/pauld/.gem/ruby/2.5.3/gems/rubocop-0.67.2/config/default.yml
Inspecting 1 file
Scanning /Users/pauld/dev/badger/app/models/app/console.rb
An error occurred while Rails/ActiveRecordOverride cop was inspecting /Users/pauld/dev/badger/app/models/app/console.rb:7:4.
undefined method `const_name' for nil:NilClass
/Users/pauld/.gem/ruby/2.5.3/gems/rubocop-0.67.2/lib/rubocop/cop/rails/active_record_override.rb:42:in `on_def'
/Users/pauld/.gem/ruby/2.5.3/gems/rubocop-0.67.2/lib/rubocop/cop/commissioner.rb:58:in `block (2 levels) in trigger_responding_cops'
/Users/pauld/.gem/ruby/2.5.3/gems/rubocop-0.67.2/lib/rubocop/cop/commissioner.rb:106:in `with_cop_error_handling'
/Users/pauld/.gem/ruby/2.5.3/gems/rubocop-0.67.2/lib/rubocop/cop/commissioner.rb:57:in `block in trigger_responding_cops'
/Users/pauld/.gem/ruby/2.5.3/gems/rubocop-0.67.2/lib/rubocop/cop/commissioner.rb:56:in `each'
/Users/pauld/.gem/ruby/2.5.3/gems/rubocop-0.67.2/lib/rubocop/cop/commissioner.rb:56:in `trigger_responding_cops'
/Users/pauld/.gem/ruby/2.5.3/gems/rubocop-0.67.2/lib/rubocop/cop/commissioner.rb:34:in `block (2 levels) in <class:Commissioner>'
/Users/pauld/.gem/ruby/2.5.3/gems/rubocop-0.67.2/lib/rubocop/ast/traversal.rb:50:in `block in on_begin'
/Users/pauld/.gem/ruby/2.5.3/gems/rubocop-0.67.2/lib/rubocop/ast/traversal.rb:50:in `each'
/Users/pauld/.gem/ruby/2.5.3/gems/rubocop-0.67.2/lib/rubocop/ast/traversal.rb:50:in `on_begin'
/Users/pauld/.gem/ruby/2.5.3/gems/rubocop-0.67.2/lib/rubocop/cop/commissioner.rb:35:in `block (2 levels) in <class:Commissioner>'
/Users/pauld/.gem/ruby/2.5.3/gems/rubocop-0.67.2/lib/rubocop/ast/traversal.rb:150:in `on_while'
/Users/pauld/.gem/ruby/2.5.3/gems/rubocop-0.67.2/lib/rubocop/cop/commissioner.rb:35:in `block (2 levels) in <class:Commissioner>'
/Users/pauld/.gem/ruby/2.5.3/gems/rubocop-0.67.2/lib/rubocop/ast/traversal.rb:150:in `on_while'
/Users/pauld/.gem/ruby/2.5.3/gems/rubocop-0.67.2/lib/rubocop/cop/commissioner.rb:35:in `block (2 levels) in <class:Commissioner>'
/Users/pauld/.gem/ruby/2.5.3/gems/rubocop-0.67.2/lib/rubocop/ast/traversal.rb:13:in `walk'
/Users/pauld/.gem/ruby/2.5.3/gems/rubocop-0.67.2/lib/rubocop/cop/commissioner.rb:46:in `investigate'
/Users/pauld/.gem/ruby/2.5.3/gems/rubocop-0.67.2/lib/rubocop/cop/team.rb:116:in `investigate'
/Users/pauld/.gem/ruby/2.5.3/gems/rubocop-0.67.2/lib/rubocop/cop/team.rb:104:in `offenses'
/Users/pauld/.gem/ruby/2.5.3/gems/rubocop-0.67.2/lib/rubocop/cop/team.rb:44:in `inspect_file'
/Users/pauld/.gem/ruby/2.5.3/gems/rubocop-0.67.2/lib/rubocop/runner.rb:273:in `inspect_file'
/Users/pauld/.gem/ruby/2.5.3/gems/rubocop-0.67.2/lib/rubocop/runner.rb:220:in `block in do_inspection_loop'
/Users/pauld/.gem/ruby/2.5.3/gems/rubocop-0.67.2/lib/rubocop/runner.rb:252:in `block in iterate_until_no_changes'
/Users/pauld/.gem/ruby/2.5.3/gems/rubocop-0.67.2/lib/rubocop/runner.rb:245:in `loop'
/Users/pauld/.gem/ruby/2.5.3/gems/rubocop-0.67.2/lib/rubocop/runner.rb:245:in `iterate_until_no_changes'
/Users/pauld/.gem/ruby/2.5.3/gems/rubocop-0.67.2/lib/rubocop/runner.rb:216:in `do_inspection_loop'
/Users/pauld/.gem/ruby/2.5.3/gems/rubocop-0.67.2/lib/rubocop/runner.rb:119:in `block in file_offenses'
/Users/pauld/.gem/ruby/2.5.3/gems/rubocop-0.67.2/lib/rubocop/runner.rb:137:in `file_offense_cache'
/Users/pauld/.gem/ruby/2.5.3/gems/rubocop-0.67.2/lib/rubocop/runner.rb:117:in `file_offenses'
/Users/pauld/.gem/ruby/2.5.3/gems/rubocop-0.67.2/lib/rubocop/runner.rb:105:in `process_file'
/Users/pauld/.gem/ruby/2.5.3/gems/rubocop-0.67.2/lib/rubocop/runner.rb:82:in `block in each_inspected_file'
/Users/pauld/.gem/ruby/2.5.3/gems/rubocop-0.67.2/lib/rubocop/runner.rb:81:in `each'
/Users/pauld/.gem/ruby/2.5.3/gems/rubocop-0.67.2/lib/rubocop/runner.rb:81:in `reduce'
/Users/pauld/.gem/ruby/2.5.3/gems/rubocop-0.67.2/lib/rubocop/runner.rb:81:in `each_inspected_file'
/Users/pauld/.gem/ruby/2.5.3/gems/rubocop-0.67.2/lib/rubocop/runner.rb:73:in `inspect_files'
/Users/pauld/.gem/ruby/2.5.3/gems/rubocop-0.67.2/lib/rubocop/runner.rb:39:in `run'
/Users/pauld/.gem/ruby/2.5.3/gems/rubocop-0.67.2/lib/rubocop/cli.rb:174:in `execute_runner'
/Users/pauld/.gem/ruby/2.5.3/gems/rubocop-0.67.2/lib/rubocop/cli.rb:75:in `execute_runners'
/Users/pauld/.gem/ruby/2.5.3/gems/rubocop-0.67.2/lib/rubocop/cli.rb:47:in `run'
/Users/pauld/.gem/ruby/2.5.3/gems/rubocop-0.67.2/exe/rubocop:25:in `block in <top (required)>'
/Users/pauld/.rubies/ruby-2.5.3/lib/ruby/2.5.0/benchmark.rb:308:in `realtime'
/Users/pauld/.gem/ruby/2.5.3/gems/rubocop-0.67.2/exe/rubocop:24:in `<top (required)>'
/Users/pauld/.gem/ruby/2.5.3/bin/rubocop:23:in `load'
/Users/pauld/.gem/ruby/2.5.3/bin/rubocop:23:in `<main>'
C

Offenses:

app/models/app/console.rb:4:3: C: Style/Documentation: Missing top-level module documentation comment.
  module Console
  ^^^^^^

1 file inspected, 1 offense detected

1 error occurred:
An error occurred while Rails/ActiveRecordOverride cop was inspecting /Users/pauld/dev/badger/app/models/app/console.rb:7:4.
Errors are usually caused by RuboCop bugs.
Please, report your problems to RuboCop's issue tracker.
https://github.com/rubocop-hq/rubocop/issues

RuboCop version
Mention the following information in the issue report:
0.67.2 (using Parser <IP_ADDRESS>, running on ruby 2.5.3 x86_64-darwin18)

Similar issue here when running Rubocop against the following code:
# app/models/transaction.rb
class Transaction
  def destroy
  end

  private
end

Note: issue won't happen when private isn't present.
Error:
An error occurred while Rails/ActiveRecordOverride cop was inspecting app/models/transaction.rb:2:2.
undefined method `const_name' for nil:NilClass

Same problem for us too.
https://github.com/crimethinc/website/pull/1099
https://travis-ci.org/crimethinc/website/builds/518080309
File in question:
https://github.com/crimethinc/website/blob/master/app/models/advanced_search.rb
crimethinc/website/app/models/advanced_search.rb
An error occurred while Rails/ActiveRecordOverride cop was inspecting /crimethinc/website/app/models/advanced_search.rb:8:2.
undefined method `const_name' for nil:NilClass

1 error occurred:
An error occurred while Rails/ActiveRecordOverride cop was inspecting /crimethinc/website/app/models/advanced_search.rb:8:2.
Errors are usually caused by RuboCop bugs.
Please, report your problems to RuboCop's issue tracker.
https://github.com/rubocop-hq/rubocop/issues

Mention the following information in the issue report:
0.67.2 (using Parser <IP_ADDRESS>, running on ruby 2.6.2 x86_64-darwin18)

We've also run into this error.
Here's a simplified version of what can reproduce it:
# app/models/some_model.rb
class SomeModel < ApplicationRecord
  alias a_method another_method

  def destroy
    # Some code here.
  end
end

The presence of the alias is enough to cause the failure. Interestingly, this only happens if the file is in the app/models folder. If the file is at the root level of the project, this doesn't happen.
Here's the output:
$ rubocop -a -d app/models/some_model.rb
For <removed>: configuration from <removed>/.rubocop.yml
configuration from <removed>/.rbenv/versions/2.6.2/lib/ruby/gems/2.6.0/gems/rubocop-performance-1.0.0/config/default.yml
configuration from <removed>/.rbenv/versions/2.6.2/lib/ruby/gems/2.6.0/gems/rubocop-performance-1.0.0/config/default.yml
Default configuration from <removed>/.rbenv/versions/2.6.2/lib/ruby/gems/2.6.0/gems/rubocop-0.67.2/config/default.yml
Inspecting 1 file
Scanning <removed>/app/models/some_model.rb
An error occurred while Rails/ActiveRecordOverride cop was inspecting <removed>/app/models/some_model.rb:6:2.
undefined method `const_name' for nil:NilClass
<removed>/.rbenv/versions/2.6.2/lib/ruby/gems/2.6.0/gems/rubocop-0.67.2/lib/rubocop/cop/rails/active_record_override.rb:42:in `on_def'
<removed>/.rbenv/versions/2.6.2/lib/ruby/gems/2.6.0/gems/rubocop-0.67.2/lib/rubocop/cop/commissioner.rb:58:in `block (2 levels) in trigger_responding_cops'
<removed>/.rbenv/versions/2.6.2/lib/ruby/gems/2.6.0/gems/rubocop-0.67.2/lib/rubocop/cop/commissioner.rb:106:in `with_cop_error_handling'
<removed>/.rbenv/versions/2.6.2/lib/ruby/gems/2.6.0/gems/rubocop-0.67.2/lib/rubocop/cop/commissioner.rb:57:in `block in trigger_responding_cops'
<removed>/.rbenv/versions/2.6.2/lib/ruby/gems/2.6.0/gems/rubocop-0.67.2/lib/rubocop/cop/commissioner.rb:56:in `each'
<removed>/.rbenv/versions/2.6.2/lib/ruby/gems/2.6.0/gems/rubocop-0.67.2/lib/rubocop/cop/commissioner.rb:56:in `trigger_responding_cops'
<removed>/.rbenv/versions/2.6.2/lib/ruby/gems/2.6.0/gems/rubocop-0.67.2/lib/rubocop/cop/commissioner.rb:34:in `block (2 levels) in <class:Commissioner>'
<removed>/.rbenv/versions/2.6.2/lib/ruby/gems/2.6.0/gems/rubocop-0.67.2/lib/rubocop/ast/traversal.rb:50:in `block in on_begin'
<removed>/.rbenv/versions/2.6.2/lib/ruby/gems/2.6.0/gems/rubocop-0.67.2/lib/rubocop/ast/traversal.rb:50:in `each'
<removed>/.rbenv/versions/2.6.2/lib/ruby/gems/2.6.0/gems/rubocop-0.67.2/lib/rubocop/ast/traversal.rb:50:in `on_begin'
<removed>/.rbenv/versions/2.6.2/lib/ruby/gems/2.6.0/gems/rubocop-0.67.2/lib/rubocop/cop/commissioner.rb:35:in `block (2 levels) in <class:Commissioner>'
<removed>/.rbenv/versions/2.6.2/lib/ruby/gems/2.6.0/gems/rubocop-0.67.2/lib/rubocop/ast/traversal.rb:92:in `on_class'
<removed>/.rbenv/versions/2.6.2/lib/ruby/gems/2.6.0/gems/rubocop-0.67.2/lib/rubocop/cop/commissioner.rb:35:in `block (2 levels) in <class:Commissioner>'
<removed>/.rbenv/versions/2.6.2/lib/ruby/gems/2.6.0/gems/rubocop-0.67.2/lib/rubocop/ast/traversal.rb:13:in `walk'
<removed>/.rbenv/versions/2.6.2/lib/ruby/gems/2.6.0/gems/rubocop-0.67.2/lib/rubocop/cop/commissioner.rb:46:in `investigate'
<removed>/.rbenv/versions/2.6.2/lib/ruby/gems/2.6.0/gems/rubocop-0.67.2/lib/rubocop/cop/team.rb:116:in `investigate'
<removed>/.rbenv/versions/2.6.2/lib/ruby/gems/2.6.0/gems/rubocop-0.67.2/lib/rubocop/cop/team.rb:104:in `offenses'
<removed>/.rbenv/versions/2.6.2/lib/ruby/gems/2.6.0/gems/rubocop-0.67.2/lib/rubocop/cop/team.rb:44:in `inspect_file'
<removed>/.rbenv/versions/2.6.2/lib/ruby/gems/2.6.0/gems/rubocop-0.67.2/lib/rubocop/runner.rb:273:in `inspect_file'
<removed>/.rbenv/versions/2.6.2/lib/ruby/gems/2.6.0/gems/rubocop-0.67.2/lib/rubocop/runner.rb:220:in `block in do_inspection_loop'
<removed>/.rbenv/versions/2.6.2/lib/ruby/gems/2.6.0/gems/rubocop-0.67.2/lib/rubocop/runner.rb:252:in `block in iterate_until_no_changes'
<removed>/.rbenv/versions/2.6.2/lib/ruby/gems/2.6.0/gems/rubocop-0.67.2/lib/rubocop/runner.rb:245:in `loop'
<removed>/.rbenv/versions/2.6.2/lib/ruby/gems/2.6.0/gems/rubocop-0.67.2/lib/rubocop/runner.rb:245:in `iterate_until_no_changes'
<removed>/.rbenv/versions/2.6.2/lib/ruby/gems/2.6.0/gems/rubocop-0.67.2/lib/rubocop/runner.rb:216:in `do_inspection_loop'
<removed>/.rbenv/versions/2.6.2/lib/ruby/gems/2.6.0/gems/rubocop-0.67.2/lib/rubocop/runner.rb:119:in `block in file_offenses'
<removed>/.rbenv/versions/2.6.2/lib/ruby/gems/2.6.0/gems/rubocop-0.67.2/lib/rubocop/runner.rb:137:in `file_offense_cache'
<removed>/.rbenv/versions/2.6.2/lib/ruby/gems/2.6.0/gems/rubocop-0.67.2/lib/rubocop/runner.rb:117:in `file_offenses'
<removed>/.rbenv/versions/2.6.2/lib/ruby/gems/2.6.0/gems/rubocop-0.67.2/lib/rubocop/runner.rb:105:in `process_file'
<removed>/.rbenv/versions/2.6.2/lib/ruby/gems/2.6.0/gems/rubocop-0.67.2/lib/rubocop/runner.rb:82:in `block in each_inspected_file'
<removed>/.rbenv/versions/2.6.2/lib/ruby/gems/2.6.0/gems/rubocop-0.67.2/lib/rubocop/runner.rb:81:in `each'
<removed>/.rbenv/versions/2.6.2/lib/ruby/gems/2.6.0/gems/rubocop-0.67.2/lib/rubocop/runner.rb:81:in `reduce'
<removed>/.rbenv/versions/2.6.2/lib/ruby/gems/2.6.0/gems/rubocop-0.67.2/lib/rubocop/runner.rb:81:in `each_inspected_file'
<removed>/.rbenv/versions/2.6.2/lib/ruby/gems/2.6.0/gems/rubocop-0.67.2/lib/rubocop/runner.rb:73:in `inspect_files'
<removed>/.rbenv/versions/2.6.2/lib/ruby/gems/2.6.0/gems/rubocop-0.67.2/lib/rubocop/runner.rb:39:in `run'
<removed>/.rbenv/versions/2.6.2/lib/ruby/gems/2.6.0/gems/rubocop-0.67.2/lib/rubocop/cli.rb:174:in `execute_runner'
<removed>/.rbenv/versions/2.6.2/lib/ruby/gems/2.6.0/gems/rubocop-0.67.2/lib/rubocop/cli.rb:75:in `execute_runners'
<removed>/.rbenv/versions/2.6.2/lib/ruby/gems/2.6.0/gems/rubocop-0.67.2/lib/rubocop/cli.rb:47:in `run'
<removed>/.rbenv/versions/2.6.2/lib/ruby/gems/2.6.0/gems/rubocop-0.67.2/exe/rubocop:25:in `block in <top (required)>'
<removed>/.rbenv/versions/2.6.2/lib/ruby/2.6.0/benchmark.rb:308:in `realtime'
<removed>/.rbenv/versions/2.6.2/lib/ruby/gems/2.6.0/gems/rubocop-0.67.2/exe/rubocop:24:in `<top (required)>'
<removed>/.rbenv/versions/2.6.2/bin/rubocop:23:in `load'
<removed>/.rbenv/versions/2.6.2/bin/rubocop:23:in `<main>'
.

1 file inspected, no offenses detected

1 error occurred:
An error occurred while Rails/ActiveRecordOverride cop was inspecting <removed>/app/models/some_model.rb:6:2.
Errors are usually caused by RuboCop bugs.
Please, report your problems to RuboCop's issue tracker.
https://github.com/rubocop-hq/rubocop/issues

Mention the following information in the issue report:
0.67.2 (using Parser <IP_ADDRESS>, running on ruby 2.6.2 x86_64-darwin18)

We've also run into this error.
Here's a simplified version of what can reproduce it:
# app/models/some_model.rb
class SomeModel < ApplicationRecord
  alias a_method another_method

  def destroy
    # Some code here.
  end
end

The presence of the alias is enough to cause the failure. Interestingly, this only happens if the file is in the app/models folder. If the file is at the root level of the project, this doesn't happen.
Here's the output:
$ rubocop -a -d app/models/some_model.rb
For <removed>: configuration from <removed>/.rubocop.yml
configuration from <removed>/.rbenv/versions/2.6.2/lib/ruby/gems/2.6.0/gems/rubocop-performance-1.0.0/config/default.yml
configuration from <removed>/.rbenv/versions/2.6.2/lib/ruby/gems/2.6.0/gems/rubocop-performance-1.0.0/config/default.yml
Default configuration from <removed>/.rbenv/versions/2.6.2/lib/ruby/gems/2.6.0/gems/rubocop-0.67.2/config/default.yml
Inspecting 1 file
Scanning <removed>/app/models/some_model.rb
An error occurred while Rails/ActiveRecordOverride cop was inspecting <removed>/app/models/some_model.rb:6:2.
undefined method `const_name' for nil:NilClass
<removed>/.rbenv/versions/2.6.2/lib/ruby/gems/2.6.0/gems/rubocop-0.67.2/lib/rubocop/cop/rails/active_record_override.rb:42:in `on_def'
<removed>/.rbenv/versions/2.6.2/lib/ruby/gems/2.6.0/gems/rubocop-0.67.2/lib/rubocop/cop/commissioner.rb:58:in `block (2 levels) in trigger_responding_cops'
<removed>/.rbenv/versions/2.6.2/lib/ruby/gems/2.6.0/gems/rubocop-0.67.2/lib/rubocop/cop/commissioner.rb:106:in `with_cop_error_handling'
<removed>/.rbenv/versions/2.6.2/lib/ruby/gems/2.6.0/gems/rubocop-0.67.2/lib/rubocop/cop/commissioner.rb:57:in `block in trigger_responding_cops'
<removed>/.rbenv/versions/2.6.2/lib/ruby/gems/2.6.0/gems/rubocop-0.67.2/lib/rubocop/cop/commissioner.rb:56:in `each'
<removed>/.rbenv/versions/2.6.2/lib/ruby/gems/2.6.0/gems/rubocop-0.67.2/lib/rubocop/cop/commissioner.rb:56:in `trigger_responding_cops'
<removed>/.rbenv/versions/2.6.2/lib/ruby/gems/2.6.0/gems/rubocop-0.67.2/lib/rubocop/cop/commissioner.rb:34:in `block (2 levels) in <class:Commissioner>'
<removed>/.rbenv/versions/2.6.2/lib/ruby/gems/2.6.0/gems/rubocop-0.67.2/lib/rubocop/ast/traversal.rb:50:in `block in on_begin'
<removed>/.rbenv/versions/2.6.2/lib/ruby/gems/2.6.0/gems/rubocop-0.67.2/lib/rubocop/ast/traversal.rb:50:in `each'
<removed>/.rbenv/versions/2.6.2/lib/ruby/gems/2.6.0/gems/rubocop-0.67.2/lib/rubocop/ast/traversal.rb:50:in `on_begin'
<removed>/.rbenv/versions/2.6.2/lib/ruby/gems/2.6.0/gems/rubocop-0.67.2/lib/rubocop/cop/commissioner.rb:35:in `block (2 levels) in <class:Commissioner>'
<removed>/.rbenv/versions/2.6.2/lib/ruby/gems/2.6.0/gems/rubocop-0.67.2/lib/rubocop/ast/traversal.rb:92:in `on_class'
<removed>/.rbenv/versions/2.6.2/lib/ruby/gems/2.6.0/gems/rubocop-0.67.2/lib/rubocop/cop/commissioner.rb:35:in `block (2 levels) in <class:Commissioner>'
<removed>/.rbenv/versions/2.6.2/lib/ruby/gems/2.6.0/gems/rubocop-0.67.2/lib/rubocop/ast/traversal.rb:13:in `walk'
<removed>/.rbenv/versions/2.6.2/lib/ruby/gems/2.6.0/gems/rubocop-0.67.2/lib/rubocop/cop/commissioner.rb:46:in `investigate'
<removed>/.rbenv/versions/2.6.2/lib/ruby/gems/2.6.0/gems/rubocop-0.67.2/lib/rubocop/cop/team.rb:116:in `investigate'
<removed>/.rbenv/versions/2.6.2/lib/ruby/gems/2.6.0/gems/rubocop-0.67.2/lib/rubocop/cop/team.rb:104:in `offenses'
<removed>/.rbenv/versions/2.6.2/lib/ruby/gems/2.6.0/gems/rubocop-0.67.2/lib/rubocop/cop/team.rb:44:in `inspect_file'
<removed>/.rbenv/versions/2.6.2/lib/ruby/gems/2.6.0/gems/rubocop-0.67.2/lib/rubocop/runner.rb:273:in `inspect_file'
<removed>/.rbenv/versions/2.6.2/lib/ruby/gems/2.6.0/gems/rubocop-0.67.2/lib/rubocop/runner.rb:220:in `block in do_inspection_loop'
<removed>/.rbenv/versions/2.6.2/lib/ruby/gems/2.6.0/gems/rubocop-0.67.2/lib/rubocop/runner.rb:252:in `block in iterate_until_no_changes'
<removed>/.rbenv/versions/2.6.2/lib/ruby/gems/2.6.0/gems/rubocop-0.67.2/lib/rubocop/runner.rb:245:in `loop'
<removed>/.rbenv/versions/2.6.2/lib/ruby/gems/2.6.0/gems/rubocop-0.67.2/lib/rubocop/runner.rb:245:in `iterate_until_no_changes'
<removed>/.rbenv/versions/2.6.2/lib/ruby/gems/2.6.0/gems/rubocop-0.67.2/lib/rubocop/runner.rb:216:in `do_inspection_loop'
<removed>/.rbenv/versions/2.6.2/lib/ruby/gems/2.6.0/gems/rubocop-0.67.2/lib/rubocop/runner.rb:119:in `block in file_offenses'
<removed>/.rbenv/versions/2.6.2/lib/ruby/gems/2.6.0/gems/rubocop-0.67.2/lib/rubocop/runner.rb:137:in `file_offense_cache'
<removed>/.rbenv/versions/2.6.2/lib/ruby/gems/2.6.0/gems/rubocop-0.67.2/lib/rubocop/runner.rb:117:in `file_offenses'
<removed>/.rbenv/versions/2.6.2/lib/ruby/gems/2.6.0/gems/rubocop-0.67.2/lib/rubocop/runner.rb:105:in `process_file'
<removed>/.rbenv/versions/2.6.2/lib/ruby/gems/2.6.0/gems/rubocop-0.67.2/lib/rubocop/runner.rb:82:in `block in each_inspected_file'
<removed>/.rbenv/versions/2.6.2/lib/ruby/gems/2.6.0/gems/rubocop-0.67.2/lib/rubocop/runner.rb:81:in `each'
<removed>/.rbenv/versions/2.6.2/lib/ruby/gems/2.6.0/gems/rubocop-0.67.2/lib/rubocop/runner.rb:81:in `reduce'
<removed>/.rbenv/versions/2.6.2/lib/ruby/gems/2.6.0/gems/rubocop-0.67.2/lib/rubocop/runner.rb:81:in `each_inspected_file'
<removed>/.rbenv/versions/2.6.2/lib/ruby/gems/2.6.0/gems/rubocop-0.67.2/lib/rubocop/runner.rb:73:in `inspect_files'
<removed>/.rbenv/versions/2.6.2/lib/ruby/gems/2.6.0/gems/rubocop-0.67.2/lib/rubocop/runner.rb:39:in `run'
<removed>/.rbenv/versions/2.6.2/lib/ruby/gems/2.6.0/gems/rubocop-0.67.2/lib/rubocop/cli.rb:174:in `execute_runner'
<removed>/.rbenv/versions/2.6.2/lib/ruby/gems/2.6.0/gems/rubocop-0.67.2/lib/rubocop/cli.rb:75:in `execute_runners'
<removed>/.rbenv/versions/2.6.2/lib/ruby/gems/2.6.0/gems/rubocop-0.67.2/lib/rubocop/cli.rb:47:in `run'
<removed>/.rbenv/versions/2.6.2/lib/ruby/gems/2.6.0/gems/rubocop-0.67.2/exe/rubocop:25:in `block in <top (required)>'
<removed>/.rbenv/versions/2.6.2/lib/ruby/2.6.0/benchmark.rb:308:in `realtime'
<removed>/.rbenv/versions/2.6.2/lib/ruby/gems/2.6.0/gems/rubocop-0.67.2/exe/rubocop:24:in `<top (required)>'
<removed>/.rbenv/versions/2.6.2/bin/rubocop:23:in `load'
<removed>/.rbenv/versions/2.6.2/bin/rubocop:23:in `<main>'
.

1 file inspected, no offenses detected

1 error occurred:
An error occurred while Rails/ActiveRecordOverride cop was inspecting <removed>/app/models/some_model.rb:6:2.
Errors are usually caused by RuboCop bugs.
Please, report your problems to RuboCop's issue tracker.
https://github.com/rubocop-hq/rubocop/issues

Mention the following information in the issue report:
0.67.2 (using Parser <IP_ADDRESS>, running on ruby 2.6.2 x86_64-darwin18)

Yet another case when this happens
class Test
  def save
  end

  private
end

in app/models directory

The error was introduced in v0.67.2. Had to downgrade to v0.65.0 for now

You could have also just disabled the problematic check. I guess we should suggest this workaround in the error message or something like this.


Add clear for export parameters at beginning of method

Export parameters should always be cleared at the first executable line of a method to avoid old, obsolete data to be exported by this very method. Sometimes a developer forgot to add such a statement.
It would be cool, if there was a rule which enabled ABAP Cleaner to check whether such a statement is already existent for all export parameters and add a clear for missing ones.

Hi Marius,
unfortunately, the possibility to check this is a bit limited, because ABAP cleaner does not do additional backend calls, which might be needed to retrieve the method signature if it is "out of sight" (e.g. because the method is defined on an interface or in a parent class).
Whenever the method signature is found in the same code document, the cleanup rule "Report unused parameters" indeed reports missing CLEAR:

I'd be hesitant, though, to automatically introduce CLEAR if it is missing, because ABAP cleaner should not change the behavior of a method. And funny things can happen, esp. if the caller passes the same variable into both EXPORTING and IMPORTING parameters. Try this with and without the CLEAR:
    METHODS any_method.

    METHODS get_next_date
      importing iv_date type dats
      exporting ev_next_date type dats.

...

  METHOD any_method.
    DATA lv_date TYPE dats VALUE '20240220'.
    get_next_date( EXPORTING iv_date      = lv_date
                   IMPORTING ev_next_date = lv_date ).
    WRITE lv_date.
  ENDMETHOD.

  METHOD get_next_date.
    " CLEAR ev_next_date.
    ev_next_date = iv_date + 1.
  ENDMETHOD.

Kind regards,
Jörg-Michael


[IMPROVEMENT] Prevent RMI from doing System.gc every hour

Suspicious! GC every hour with JMX activated... I'll shoot down the usual suspect.

:exploding_head:

Not surprised that's a big classic in Devoxx JVM talks. I listen to that when washing dishes....

i do sometimes too but clearly not enough. I would be very curious to understand the rationale that drove to scheduling a gc every hour ...

Likely some long living connections  with some churns.
Long living connections cause the old gen to fill up.
And the churn turns those old gen objects into garbadges.
I bet the intent is to try to achieve reasonnable pause time by forcing periodic GCs rather than let a huge GC pause build up. THough debatable this 'could' make sense for JMX intensive apps.
Now in james context we only use JMX for the CLI and in the heap dump I worked with I never even come to read 'rmi' or 'jmx' thus I believe that for James this GC pause is highly irrelevant.
Also I came across some comments in Cassandra source code explicitly disabling this : https://github.com/apache/cassandra/blob/39e89fd636ee4343eb2201820da87881cbc749e2/src/java/org/apache/cassandra/utils/JMXServerUtils.java#L110

THough debatable this 'could' make sense for JMX intensive apps
sounds like premature optimization built-in right into the JDK :p