We are about to run patch 5 from #20.
If you don't want to make this the default, can we add a drupal config to wrap the toolbar to multiple lines?
Thanks for the release!
From the bot's description:
> If this issue is left open (status of Active, Needs review, Needs work or Reviewed and tested by the community) and the "ProjectUpdateBotD10" tag is left on this issue, new patches will be posted periodically if new deprecation fixes are needed.
I think D10 is not likely to get more deprecation fixes at this point. :shrug:
But maybe something to watch for ... for like D11. Maintainers might end up merging in MRs multiple times, and keeping the bot update issue open.
Closed duplicate ✨ add Tugboat config.yml Closed: duplicate from @q0rban .
Seems like the next step here is to get a passing MR.
ps. I was familiar with this issue, from a little work I did on 💬 Umami demo content makes http reponse headers without encoding invalid characters Active
I'll copy some of the issue description to previous existing issue: https://www.drupal.org/project/drupal/issues/3280730 → . Closing this as duplicate. :)
YesCT → created an issue.
Adding template intro.
Saying thanks.
Adding default closing.
I got confused since I could see the compare but not open a PR. I needed to log in.
3 months ago, https://www.drupal.org/project/drupal/issues/2911977#comment-15309703 ✨ Add Media revision UI Fixed went into 10.2
Closer to deprecation??
Can this issue be closed? https://www.drupal.org/project/ctools → already says the current version (4.0.4) is D10 compatible.
Is there a way to have the bot re-run and see if there are still issues it can autofix??
Can this issue be closed? https://www.drupal.org/project/ctools → already says the current version (4.0.4) is D10 compatible.
I added workarounds and the upstream issue to this summary.
Like @mglaman in comment #30 https://www.drupal.org/project/drupal/issues/3405976#comment-15357388 🐛 Transaction autocommit during shutdown relies on unreliable object destruction order (xdebug 3.3+ enabled) Needs review
we were able to fix the sudden failing of our build step in behat, unit, and functional phpunit tests by updating the image CI was using in our webhead-ci/Dockerfile with this change:
- && pecl install xdebug \
+ && pecl install xdebug-3.2.2 \
Thank you folks for sharing what symptoms you were seeing and your workarounds!!
---
We are running D10. We did try a patch and it helped get our unit tests to pass, but we were still getting different errors with behat and functtional phpunit tests with the patch. Pinning xdebug got all our tests passing.
I think the lenient composer endpoint can help avoid moving the module to custom folder.
https://www.drupal.org/docs/develop/using-composer/using-drupals-lenient... →
Is this "done" since https://www.drupal.org/project/menu_breadcrumb/releases/2.0.0-alpha0 → was released?
This is listed as a blocker for a full release with D10 compatibility.
Is the next step here to help get the MR passing tests?
Is this still an issue with https://www.drupal.org/project/rename_admin_paths/releases/8.x-2.2-beta1 → ?
At Lullabot, we wrote up an Architecture Decision Record (ADR) to deal with a similar situation.
https://architecture.lullabot.com/adr/20210924-drupal-build-steps/
Depends on developers using hook_post_update_NAME() → .
Does that help?
Looks like if this issue were fixed in drupal packaging, then RenovateBot automatic updater might automatically start picking up security releases. (See the renvoatebot issue I made: "Renovate does not recognize Drupal security releases as security updates".)
@webchick You've been such a role model to me in so many ways. Thank you so much!
quietone → credited YesCT → .
This is better!
Thanks!
I talked to the group working on this issue. They are going to try and reproduce the error, and evaluate the category and priority. :)
changing to use the more common tag, so the less common one can be deleted, so it does not show up in the auto complete and confuse people.
putting the reason postponed in the issue summary.
I put the templates in the summary, but there are details I'm not sure of.
What is the motivation here?
Why is this a feature request?
Could this qualify for beta under "prioritized change"?
updating the issue summary with the 8.1.x rationale
getting a first look at if this is still relevant, put issues in the summary.
sorry fixing tag
Is there any point in rerolling (http://drupal.org/patch/reroll) #80?
could use an issue summary update. tips to do: http://drupal.org/node/1427826
#886488-94: Add stampede protection for css and js aggregation → says this issue might help that one.
(the slash in the i/o tag breaks the autocomplete from adding new tags)
#80: 1014086-80-css-imagecache.patch queued for re-testing.