-
Notifications
You must be signed in to change notification settings - Fork 5
[QA] data_exporter fails with setIgnoredAttributes() call to undefined method. #232
Comments
I have deja-vu about this. I am sure that I have done something like this in some other app or test - looking... |
https://github.com/owncloud/files_classifier/pull/755/files From memory, Symfony4 supports both So we can change to using (2) and it will work for both Symfony releases. I will code something, and also try to see why we do not have any failing tests in CI. |
The tarball of https://github.com/owncloud/data_exporter/releases/tag/v0.3.0-rc.1 has
But Thinking... |
I was using: I have updated to: @jnweiger what version of |
https://drone.owncloud.com/owncloud/data_exporter/2584/20/4 https://drone.owncloud.com/owncloud/data_exporter/2584/20/11 I unzipped the 0.3.0 RC tarball into a local core master, and export commands work fine for me. I will need to locally install a 10.12.2 (rather than my development core master) and see if I can reproduce the bad behavior. |
🤔 so, is this composer 2.1.6 too old? |
I have a feeling that composer 2.2 had new features to support "new stuff" - I would have to investigate. I think that somehow the Anyway, I think that we want to generate the latest autoloader code, using the the latest composer version. So try making a tarball that has I could update my composer on Ubuntu with |
Second RC built with composer 2.5.8 after @GeraldLeikam Is this any better? |
Unfortunately, it didn't help. The same problem with the "ObjectNormalizer" still persists.
|
@phil-davis I'd say, composer is innocent in this case. |
I will try again to reproduce later today. |
I did:
It works fine.
I also tried putting it in the Maybe you have some other app(s) enabled? Or??? - it will be good to find out what is the cause. |
I think I found the mistake. Encryption is enabled on my and Jürgen's machine. Could that be causing the error? |
Tested on 10.12.2 + https://github.com/owncloud/data_exporter/releases/tag/v0.3.0-rc.2 with and without master-key encryption: issue is not reproducible. |
No, it is not encryption. it is files_classifier. We disable this app, and get a clean export. we enable this app, and get Gerald's crash.
|
cannot confirm:
|
yep. files_classifier-1.3.2 is harmless. The new 1.4.0-rc.1 or 1.4.0-rc.2 cause the explosion. |
confirmed 💥 |
Happens with current core master in my development environment:
I suppose that there is some "magic" in how the composer autoload sequence tries to find the referenced class, and it must have loaded a class definition that comes from I will play around and see if there is some way to help composer autoload to be smarter. |
@phil-davis yes, it seems the symfony/serializer from files_classifier is loaded and there See 5.0.0 changelog in https://github.com/owncloud/files_classifier/pull/583, which was superseded by https://github.com/owncloud/files_classifier/pull/763 (merged). |
Yes, Symfony5 does not have
(1) might be quite tricky to ensure that we get it right. (2) is easy and will work. If we decide to do (2), then the new data_exporter release should still work fine with oC10 core releases that have Symfony4 (lots of 10.* releases, including 10.11 10.12 and the upcoming 10.13). Before doing that, we should check for any unreleased little bits of code in data_exporter master, and release that as 0.2.2. Then 0.2.2 can be used with lots of old core like 9.* and 10.* right up to 10.12. I can see #221 and #227 that in in master but not released yet - first releasing those as 0.2.2 might be good. |
PR #221 is fine - we should have always returned an |
IMO we can release the current |
Understood. So this should do the trick: https://github.com/owncloud/data_exporter/releases/download/v0.2.2-rc.1/data_exporter-0.2.2-rc.1.tar.gz |
Compatibility:
|
Confirmed fixed with 0.3.0 and 10.13.0-beta.1 |
Seen with owncloud core 10.12.2 and data-exporter-0.3.0-rc.1
seems the setIgnoredAttributes() call is deprecated.
Some google showed me code like this:
do we need to do something similar?
The text was updated successfully, but these errors were encountered: