Devcentral configuration

Repository now uses main branch and is hosted here, with GitHub as mirror.

The same issue is triggered by projects_v2, again because there is no repository.

I'm planning to work on this after WindRiver migration, that should be quick, we've only one class and a more comprehensive test folder.

Where to publish those events?

Glad to hear others are having positive experiences with bruno! Great call.

For reference, here how the information was presented in Sentry:

Solved at Nasqueron by upgrading from 3.11.8 to 3.11.11.

One another occurence of this issue exists at https://ask.csdn.net/questions/7791019

Not sure at one moment the issue was solved, with opcache it's not easy to know, but just restart the server after creating the directories wasn't enough.

In T1755#24731, @dereckson wrote:

DNS configuration

notifications.notifications-test.nasqueron.org. 86400 IN CNAME www3.nasqueron.org.
orange-rabbit.notifications-test.nasqueron.org. 86400 IN CNAME www3.nasqueron.org.
vault.notifications-test.nasqueron.org. 86400 IN CNAME www3.nasqueron.org.

Code is ready both for Notifications and keruald/dockerhub, should be tested with the next build we want to promote before merging.

The nasqueron/notifications image took from D2958, so we're done:

We still use that for rNOTIF and rGROVE AFAIK, so I provisioned their secrets in Vault at apps/notifications-center/dockerhub/

So if someone needs more recent ICU, the cleaner way would be a custom Bullseye build of the icu source package. We'll include it in packages.nasqueron.org, and from there, the repository can then be used in the image both for libxml2 and PHP itself.

"Fun" fact: libxml requires libicu, and pulls the system one of course:

Debian images will lag too much, review https://icu.unicode.org/download, we're at 71, Debian Bullseye is stuck at 67.

For shellserver and devserver role, the intl extension is already installed, per bdd61c48. MediaWiki is quoted as example of application using it.

No more warning 🎉 🎊

Deployed, no more warning according Sentry.

Two warnings still exist:

First plan of action could be to ensure we've effectively and explicitly in the job configuration moved to Next Generation Warnings plugin.

In T1731#24239, @dereckson wrote:

phpDox isn't currently compatible with PHP 8.1. Deprecations are transformed into fatal errors, even if at the start an error_reporting() instruction is left.

As a workaround, here phpDox 0.12.0-27-geb943cb-dirty, with PHP 8.1 deprecation notices for signatures mismatch addressed.

Some have been reported upstream, but as the phpDox dependencies inherit PHP builtin classes to override signatures, e.g. transforming a string|bool into a string, throwing an exception instead of returning false, perhaps upstream will adopt another approach than use false signatures.

phpdox.tar.gz5 MBDownload

It has been manually deployed on WindRiver and Zateki (Jenkins agent for CI, PHP 8 flavour).

We've merged D2706 at noon. It's not yet deployed, as we've some CI issues (D2916 and T1807).

Code merged, still to deploy.

In T1798#25799, @dereckson wrote:

Jenkins PHP agent doesn't have this either.

CI relevant logs:

• https://ci.nasqueron.org/job/test-notifications-php/228/console
• https://web.archive.org/web/20230325132130/https://ci.nasqueron.org/job/test-notifications-php/228/console