-
-
Notifications
You must be signed in to change notification settings - Fork 517
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
Some Homset are not unique parents #13184
Comments
comment:1
Attachment: trac_13184_homset_unique_parent.gz I've attached a small patch fixing the problem. |
comment:4
Please fill in your real name as Author. |
Author: Xavier Caruso |
Attachment: trac_13184.patch.gz added .patch to the existing patch so the patchbot picks it up |
This comment has been minimized.
This comment has been minimized.
comment:7
Sage does not run with the patch applied:
|
This comment has been minimized.
This comment has been minimized.
comment:8
I don't understand exactly why you got this error. Nevertheless, I noticed that ticket #11521 was merged in sage-5.5.beta0 resulting in some important modifications in |
This comment has been minimized.
This comment has been minimized.
comment:9
Attachment: trac_13184_sage_5.5.0.beta.patch.gz |
Work Issues: sage fails to run |
comment:10
Same error. I'm running Thanks, Travis PS - it's generally not a good idea to have periods in your filenames since they are used for extension types; typically people replace them with underscores. For patchbot: Apply only: trac_13184_sage_5.5.0.beta.patch |
This comment has been minimized.
This comment has been minimized.
comment:11
here is a rebased and slightly modified patch for the bot: apply trac_13184_sage_5.9.beta.patch |
comment:12
ok, just one little failing doctest, needs to be investigated |
Changed work issues from sage fails to run to one doctest |
comment:13
ok, this new patch should pass all tests. Let us wait and see |
comment:14
for the bot: apply trac_13184_sage_5.9.beta.patch |
comment:15
ok, the bot is green. There now remains the question whether or not this is the right thing to do. Any opinion, somebody ? |
Reviewer: Travis Scrimshaw |
comment:16
I'm cc-ing Simon to see if he can find a memory leak that I couldn't. However it looks good to me. |
Changed author from Xavier Caruso to Xavier Caruso, Frédéric Chapoton |
comment:18
I believe so, however because of the file rename done in #14214, there will be a dependency one way or the other. I'm cc-ing Nils to let him know about this ticket. Enjoy your holiday Simon. Nils, what is the review status of #14214 and it's dependency #14159, and perhaps you can find a memory leak that I didn't? Thanks, Travis |
comment:19
Replying to @tscrim:
If Simon's away you should probably slide this ticket under there. #14214 doesn't fix a bug, it's an enhancement. And I think it needs a little work. |
Dependencies: #14159 |
comment:21
Attachment: trac_13184_sage_5.9.beta.patch.gz here is a patch applying above #14159, where I have made the required change for the bot : apply trac_13184_sage_5.9.beta.patch |
comment:22
Thank you. |
Changed work issues from one doctest to none |
Merged: sage-5.10.beta0 |
I guess it is a bug:
I don't know what is the correct way to fix this problem.
More precisely, in sage.categories.homset (l. 223-227), one can read:
However, in this particular case, k.Hom is apparently not cached. IMHO, caching should be the job of sage.categories.homset.Hom is all cases, but I might be wrong.
Apply
Depends on #14159
CC: @xcaruso @simon-king-jena @nbruin
Component: categories
Keywords: homset unique parent
Author: Xavier Caruso, Frédéric Chapoton
Reviewer: Travis Scrimshaw
Merged: sage-5.10.beta0
Issue created by migration from https://trac.sagemath.org/ticket/13184
The text was updated successfully, but these errors were encountered: