Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

PostInverse matches more than one declaration in GradedModules #510

Open
TKuh opened this issue Aug 31, 2022 · 3 comments
Open

PostInverse matches more than one declaration in GradedModules #510

TKuh opened this issue Aug 31, 2022 · 3 comments

Comments

@TKuh
Copy link

TKuh commented Aug 31, 2022

Setting

SetUserPreference( "PackagesToLoad", [ "CAP", "homalg" ] );

inside gap.ini and then executing make test inside HigherHomologicalAlgebra/BBGG yields:

testing: /home/tom/.gap/pkg/HigherHomologicalAlgebra/BBGG/tst/100_LoadPackage.tst
########> Diff in /home/tom/.gap/pkg/HigherHomologicalAlgebra/BBGG/tst/100_LoadPackage.tst:8
# Input is:
LoadPackage( "BBGG", false );
# Expected output:
true
# But found:
#I  method installed for PostInverse matches more than one declaration in /home/tom/.gap/pkg/homalg_proj\
ect/GradedModules/gap/UnderlyingMap.gi:265
#I  method installed for PreInverse matches more than one declaration in /home/tom/.gap/pkg/homalg_project/GradedM\
odules/gap/UnderlyingMap.gi:296
true
########

@mohamed-barakat remarked, that this might point to a bug related to the order of package loading.

These errors disappear, when

SetUserPreference( "PackagesToLoad", [ "CAP", "homalg" ] );

is removed from gap.ini.

@zickgraf
Copy link
Member

zickgraf commented Sep 2, 2022

This is this issue again: homalg-project/CAP_project#586 (comment)

Minimal example:

LoadPackage( "CategoryConstructor" );
LoadPackage( "GradedModules" );

Is this relevant (=important) for you? If not, we probably won't do anything about it :D

@TKuh
Copy link
Author

TKuh commented Sep 2, 2022

Ah, I see.

Is this relevant (=important) for you? If not, we probably won't do anything about it :D

Haha, no, it's not. :) Should I close the issue, since this is known, or shall I leave it open? (Is this even the correct place here?)

@zickgraf
Copy link
Member

zickgraf commented Sep 2, 2022

I would say we keep the issue open to make it easier to find in case someone else comes across this. And just to make sure: My rather direct question was not meant to deter you from opening such issues in the future: It's good if we are aware of such things, even if they are of minor practical relevance right now, because they might get relevant any time. So thanks for the report! :-)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants