Closed (fixed)
Project:
Drupal core
Version:
8.8.x-dev
Component:
update.module
Priority:
Normal
Category:
Task
Assigned:
Unassigned
Reporter:
Created:
19 Mar 2020 at 18:37 UTC
Updated:
16 May 2020 at 17:34 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #2
tedbowComment #3
tedbowComment #4
dwwBig +1 to this. However, I don't understand point 2 in the proposed resolution:
Huh? All the tests involve testing contrib having version numbers. ;) What does this mean?
Thanks,
-Derek
Comment #5
dww3120961-5.8_x.patch applies cleanly to both 8.9.x and 8.8.x branches.
Tests are still running locally, but so far so good. Let's see what the d.o bot thinks...
Comment #6
naresh_bavaskarComment #7
naresh_bavaskarabove patch LGTM
Comment #9
neslee canil pinto@naresh_bavaskar, can you please do a dry run test.
Comment #10
dww@Neslee Canil Pinto re: #9: There's nothing to screenshot here. It's an internal change to test-only modules. The testbot shows that all the tests still pass with this change applied. I don't think there's anything to gain from a "dry run test" nor attaching screenshots of anything.
There was random failure weirdness on the 9.0.x branch -- I requeued that since the 75 failures along these lines obviously have nothing to do with this patch:
Back to RTBC.
Thanks,
-Derek
Comment #11
xjmComment #12
tedbowSorry yeah I am not sure I remember what I was thinking in 2) in the issue summary.
Plus 1 to RTBC
I couple of thoughts but both are existing issue and don't affect this issue
versionthat is set in the info.yml file. We always rely on the alter so we don't really have test coverage for it being picked up from the info.yml file. But that is existing issue and is not affected by this issue\Drupal\Core\Extension\InfoParserDynamic::parse()we haveThis seems weird that we don't check if this is core file. Is there any way a contrib module could have
version: 'VERSION'No, right? because drupal.org packaging sets this? Always? If they could then you would start to get weird situations where the update module would think the module version is \Drupal::VERSION. Would that cause any problems now that contrib can have semantic versioning?
Comment #13
xjmI guess #12.2 is followup material?
Comment #14
xjmNR for that followup to be filed.
Comment #15
dww*sigh* #12.2 has nothing to do with this issue. It's not improved or harmed. We've never had that test coverage, and that concern is entirely about the .info.yml parsing system, not the update.module. But whatever. I'll open the follow-up.
Comment #16
dww#3132978: Add test coverage of version: VERSION handling in info parser system
Comment #17
dwwRemoving point 2 from the proposed resolution, per #12.
Comment #22
xjmCommitted to 9.1.x, 9.0.x, 8.9.x, and 8.8.x. Thanks!