-
-
Notifications
You must be signed in to change notification settings - Fork 194
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
undo icontentish interface #3836
Conversation
@Akshat2Jain thanks for creating this Pull Request and helping to improve Plone! TL;DR: Finish pushing changes, pass all other checks, then paste a comment:
To ensure that these changes do not break other parts of Plone, the Plone test suite matrix needs to pass, but it takes 30-60 min. Other CI checks are usually much faster and the Plone Jenkins resources are limited, so when done pushing changes and all other checks pass either start all Jenkins PR jobs yourself, or simply add the comment above in this PR to start all the jobs automatically. Happy hacking! |
@jenkins-plone-org please run jobs |
The tests are failing with the error:
in this line of this subscriber: The error occurs when creating a Plone Site. It looks like the subscriber wants to use the if anno_tool is not None and uidtool is not None: |
@wesleybl what do I have to do in this? |
@Akshat2Jain have already signed the Plone contributor agreement. Could you add it to zopefoundation, so I can fix this error? |
any progress? |
I'm not too sure what my role here is. For historical reasons, we need a (separate) contributor agreement for the Zopefoundation repos; that can be signed here: https://sign.plone.org/d/FTU6XN6qrGtoni Is the question if @icemac should put that in there for him? Or if @Akshat2Jain does it there himself? I'm not at all familiar with the Zope codebase, testing infrastructure, and customs, although @jaroel is I think so maybe he knows. |
@Akshat2Jain please sign the Zopefoundation contributor agreement. This way you can make a PR for Products.CMFUid |
Done |
@wesleybl I have been added to the Zope Foundation. Please guide what I have to do next. |
@Akshat2Jain you need to make a PR on Products.CMFUid, with what was explained in: #3836 (comment) |
@wesleybl can you run jobs again? |
@Akshat2Jain It's no use running the jobs again. We need a new release of |
@Akshat2Jain a new |
@jenkins-plone-org please run jobs |
@davisagli @jaroel @Akshat2Jain the errors with We now have two tests failing in These tests count the number of objects returned by searching the catalog through the @Akshat2Jain , can you make a PR on |
@Akshat2Jain can you please make a PR like this in branch 6.0.x? |
this pr would be on the master branch? @wesleybl |
and this pr would be on 6.0x branch? @wesleybl |
in master of https://github.com/plone/plone.api
in branch 6.0.x of https://github.com/plone/Products.CMFPlone |
@Akshat2Jain the "like this" is the PR we are in now #3836, but in branch 6.0.x. |
@jaroel did you manage to make this test fail locally? What did you do? |
@jenkins-plone-org please run jobs |
@wesleybl Sorry, I had a left over change. My buildout.coredev only checks out Products.CMFPlone branch=undo_icontentish and the test passes. I fetched origin and then merged origin/master in. That should correctly disable that thingy I do in Products.CMFPlone/Products/CMFPlone/__init__.py Lines 12 to 21 in 621edb0
|
I'm setting SKIP_PTA in https://github.com/plone/plone.rest/blob/5f9898970f871008e84b254bf73ff13f48218bbc/src/plone/rest/tests/test_explicitacquisition.py#L67-L118, which then leaks into our I can reproduce with |
@jaroel so you need to test the environment variable at the end of these tests and set the SKIP_PTA variable again, to restore the default behavior. Can you take care of it? |
@wesleybl please look here: plone/plone.rest#168 |
@jaroel anyway, it would be good to create a test similar to |
@wesleybl No, there should be no difference. |
But if someone uses
Was it this bug that caused the test to fail? Is there already an issue about this? Can you point? |
@jenkins-plone-org please run jobs note to self: This is gonna be useless because the plone.rest stuff isn't merge yet, isn't it? |
|
@jenkins-plone-org please run jobs @jaroel I think the tests will pass now. But I don't know if we should merge this before fix plone/plone.rest#169. If someone uses |
@wesleybl No worries, nobody uses that. It's just there so we don't ship it as enabled by default. |
@jenkins-plone-org please run jobs |
@davisagli how do you feel about landing this IContentish branch? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me. I also looked through the zopefoundation and plone github organizations for references to IContentish, just to see if there was anything that might be surprising, and I think it should be okay (as also indicated by the state of the tests).
I think I would keep it for 6.1 (master) only though and not make this change for 6.0 at this point.
Special thanks to @Akshat2Jain and @wesleybl for your persistence and patience with this one!
We will keep it at bugfix instead of feature.
If we don't have this in Plone 6.0, it won't be possible to fix plone/plone.restapi#1674 in an easy way, since we don't have a version of restapi just for Plone 6.1 |
I think it would be good to have an upgrade step to reindex the Plone Site, since we have indexes that have interfaces. |
fixes #3833
also related to plone/plone.restapi#1674