Came across this repository and was wondering if this is legit or just some random ai work: https://github.com/pronskiy/php-debugger

#Xdebug #PHP #phpcommunity

I also think this is for @derickr

🇳🇱 Home from another excellent edition of @dutchphpconference 🤘 thank you so much for the opportunity to let me speak about PIE 🥧, it is always appreciated! 🥰 #php #phpconference #dpcon2026 #dpc26 #phpc #phpcommunity

Proposal for HTTP 6XX status codes

#HTTP #PHP

A182318: List of positive integers whose prime tower factorization, as defined in comments, does not contain the prime 2
A182318 ➡️ https://oeis.org/A182318

3D graph, threejs - webGL ➡️ https://decompwlj.com/3Dgraph/A182318.html
3D graph Gen, threejs animation ➡️ https://decompwlj.com/3DgraphGen/A182318.html
2D graph, first 500 terms ➡️ https://decompwlj.com/2Dgraph500terms/A182318.html

#decompwlj #math #mathematics #maths #sequence #OEIS #JavaScript #php #graph #3D #threejs #webGL #triangular #numbers #primes #PrimeNumbers #palindromes #animation #FundamentalTheoremOfArithmetic #sequences #NumberTheory #classification #integer #decomposition #number #theory #equation #graphs #sieve #fundamental #theorem #arithmetic #research

A182175: Numbers with the property that every pair of adjacent digits sum to a prime number
A182175 ➡️ https://oeis.org/A182175

3D graph, threejs - webGL ➡️ https://decompwlj.com/3Dgraph/A182175.html
3D graph Gen, threejs animation ➡️ https://decompwlj.com/3DgraphGen/A182175.html
2D graph, first 500 terms ➡️ https://decompwlj.com/2Dgraph500terms/A182175.html

#decompwlj #math #mathematics #maths #sequence #OEIS #JavaScript #php #graph #3D #threejs #webGL #triangular #numbers #primes #PrimeNumbers #palindromes #animation #FundamentalTheoremOfArithmetic #sequences #NumberTheory #classification #integer #decomposition #number #theory #equation #graphs #sieve #fundamental #theorem #arithmetic #research

I just completed a website for teton.co.za. All hand coded.

You can view my services at duskrose.co.za

شما می‌توانید خدمات من را در duskrose.co.za مشاهده کنید.
من همین‌الان یک وب‌سایت برای teton.co.za تکمیل کردم. تماماً با دست کدنویسی شده.

#html #js #css #php #webdesign #Iran #Persia
#html #js #css #php #طراحی_وب #ایران #پارس

A181780: Numbers n which are Fermat pseudoprimes to some base b, 2 <= b <= n-2
A181780 ➡️ https://oeis.org/A181780

3D graph, threejs - webGL ➡️ https://decompwlj.com/3Dgraph/A181780.html
3D graph Gen, threejs animation ➡️ https://decompwlj.com/3DgraphGen/A181780.html
2D graph, first 500 terms ➡️ https://decompwlj.com/2Dgraph500terms/A181780.html

#decompwlj #math #mathematics #maths #sequence #OEIS #JavaScript #php #graph #3D #threejs #webGL #triangular #numbers #primes #PrimeNumbers #palindromes #animation #FundamentalTheoremOfArithmetic #sequences #NumberTheory #classification #integer #decomposition #number #theory #equation #graphs #sieve #fundamental #theorem #arithmetic #research

A179888: Starting with a(1)=2: if m is a term then also 4*m+1 and 4*m+2
A179888 ➡️ https://oeis.org/A179888

3D graph, threejs - webGL ➡️ https://decompwlj.com/3Dgraph/A179888.html
3D graph Gen, threejs animation ➡️ https://decompwlj.com/3DgraphGen/A179888.html
2D graph, first 500 terms ➡️ https://decompwlj.com/2Dgraph500terms/A179888.html

#decompwlj #math #mathematics #maths #sequence #OEIS #JavaScript #php #graph #3D #threejs #webGL #triangular #numbers #primes #PrimeNumbers #palindromes #animation #FundamentalTheoremOfArithmetic #sequences #NumberTheory #classification #integer #decomposition #number #theory #equation #graphs #sieve #fundamental #theorem #arithmetic #research

PHP 8.5.4 released: https://github.com/php/php-src/releases/tag/php-8.5.4

PHP 8.4.19 released: https://github.com/php/php-src/releases/tag/php-8.4.19

Changelog: https://www.php.net/ChangeLog-8.php

Thanks to @adoy, @php development team, and all contributors.

(P.S. We need Release Managers for #PHP 8.6, https://news-web.php.net/php.internals/130240 )

How to Capture Variables in Closures

use ($var) brings outer scope in. Read. Modify with use (&$var).

#php #closure #use #howto

https://www.youtube.com/watch?v=9KqC_XBx608

Is anyone of my followers using the lightweight #Kirby CMS as a #blog? Are the core functions enough for you? How much pain do you have with its version updates? Retoots welcome.
#php

Es un hecho señoras y señores: se la nueva plataforma de aprendizaje online de #juncotic se va gestando 😃

A jugar con configuraciones web, de BBDD, optimización, hardening, y demás cositas interesantes! o/

Nuestra nueva casa, un laboratorio donde podamos jugar con el conocimiento, y crecer como comunidad aprendiendo juntos.

Estén atentos/as! Esperamos pronto tenerlo online 🙂

#moodle #gnu #linux #nginx #lemp #mariadb #php #learning #aprendizaje

We're switching to cURL everyone, cURL I say! What's cURL? cURL is better!

#rss #curl #php #development #testing

We released 1.18.0 of hydrator! See here for the changelog: https://github.com/patchlevel/hydrator/releases/tag/1.18.0
#PHP #Hydrator

How to Replace switch With match in PHP 8

match is strict. No fall-through. Returns a value. One expression.

#php #match #php8 #switch #howto

https://www.youtube.com/watch?v=BFaQXqsGYS4

Array Slicing: Python's [::-1] vs PHP Functions!

Python's magical slice syntax vs PHP's functions! arr[::-1] to reverse?! Which is cleaner? MIND BLOWN!

#python #php #pythonvsphp #arrayslicing #slicesyntax #arrayoperations #codecomparison #syntaxcomparison #pythontricks #phptricks #programmingdebate #codingtips #pythonmagic #arrayfunctions

https://www.youtube.com/watch?v=N2t3ureX7QQ

Explore our free trial to discover the platform, develop features, transfer projects, or hack together weekend experiments. #php #hosting but different.
https://docs.fortrabbit.com/platform/get-started/free-trial

#Fedora changes of this week

All #PHP extensions, coming from PECL and also available in packagist (PIE), have been cleaned of pecl stuff (25 packages for now).

So "php-pear" is no longer required at build or runtime.

Example: https://src.fedoraproject.org/rpms/php-pecl-mongodb2/c/1a4935c4ea1c5973106e74602286becddc22a307?branch=rawhide

In today's video, I show you how PHPStorm's PR review tools give you better file tracking than GitHub's own interface. #php #laravel https://masteringlaravel.io/daily/2026-03-13-video-another-nice-feature-for-local-pull-request-review

Code-Coverage with PCOV in a mono-repo

Today I finally managed to find and fix an issue that we had for some time with Code-Coverage generation with PCOV in github actions.

To give you a bit of background, imagine a project that uses 2 separate folders where one contains the business-logic and one contains the framework-related code. The framework-related part contains a lot of integration and end-to-end test that – of course – also use and therefore test the business-logic.

Every PullRequest runs the tests both from the bunsiness-logic part as well as from the framework-related part. And to give the developers feedback how well the changed code is covered with tests we collect coverage data and generate a patch-coverage report. I wrote about that some time back. So we now get a comment each in the PR that contains the untested lines in the business-logic related part and the framework-related part respectively.

That worked flawlessly for the business-logic related part as those were mostly unit-tests that do not rely upon the framework-related code.

The framework-related part though didn’t work that great. It always showed the business-logic related parts as untested even though I knew they were tested.

So… Why?

After some digging I realized that there is a difference in how the coverage is created between Xdebug and pcov – yes! There is obviously a difference as those are different tools. But there is also a difference in what is included in the reports.

And today I figured out what it was and why it broke our proces in our specific setup in GitHub actions.

For a start: We have our code in two folders: business and framework.

We also have a framework/phpunit.xml file that contains this code:

<?xml version="1.0" encoding="UTF-8"?><phpunit
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xsi:noNamespaceSchemaLocation="https://schema.phpunit.de/12.1/phpunit.xsd"
    processIsolation="false"
    stopOnFailure="false"
>
  <coverage/>
  <source>
    <include>
      <directory>src</directory>
      <directory>../business/src</directory>
    </include>
  </source>
</phpunit>

So coverage shall be collected from the current src folder as well as from the business/src folder.

This works as expected when you run phpunit with Xdebug as coverage-generator.

With pcov as coverage-generator it worked locally as expected.

But not in our GitHub Actions…

Enter pcov.directory

After a bit of digging I learned that there is the pcov.directory ini-setting that determines which code is considered for coverage. So I tested my GitHub Actions by adding some test-code like this:

jobs:
  tests:
    steps:
      - name: "Checkout"
        uses: actions/checkout@de0fac2e4500dabe0009e67214ff5f5447ce83dd # v6
        with:
          ref: ${{ github.event.pull_request.head.ref }}

      - name: "Install PHP"
        uses: shivammathur/setup-php@44454db4f0199b8b9685a5d763dc37cbf79108e1 # v2
        with:
          extensions: "intl, pdo_mysql, zip, imap, xml, soap, apcu, redis"
          php-version: "8.4"
          coverage: "pcov"
      - name: "check pcov.directory"
        run: |
          php -i | grep pcov

Running this in GitHub Actions provided me with output similar to this:

Run php -i | grep pcov
/etc/php/8.4/cli/conf.d/20-pcov.ini,
pcov
pcov.directory => /home/runner/work/<org-name>/<repo-name>
pcov.exclude => none
pcov.initial.memory => 65336 bytes
pcov.initial.files => 64

/home/runner/work/<org-name>/<repo-name> was exactly what i expected! So why the heck does it seemingly not work?

After some more testing I realized that I was at one point doing a cd framework before running PHPUnit.

- name: "Run tests"
  run: |
    cd framework
    vendor/phpunit/phpunit/phpunit --coverage-php /tmp/${{ github.sha }}_coverage.cov

Should that cause some issues?

So I added the php -i | grep pcov after the PHPUnit run like this:

- name: "Run tests"
  run: |
    cd framework
    vendor/phpunit/phpunit/phpunit --coverage-php /tmp/${{ github.sha }}_coverage.cov
    php -i | grep pcov

And what was that? Suddenly I got

pcov.directory => /home/runner/work/<org-name>/<repo-name>/framework/src

🤯

Suddenly the pcov directory was set to something totally different. And with that setting it was clear that I couldn’t get what I expected as now only content from framework/src/ would be considered as covered. And everything from the business folder was not considered for coverage.

So the only question left was whether that was something happening deep in PHPUnits logic or just based on changing the directory.

Long story short: It’s just based on the change directory. In essence setup-php sets up pcov so that the current folder is considered as pcov.directory. As pcov itself adds src when that folder is available that explains the changed folder.

But is there a way to change that? To use a fixed folder despite the current working directory being changed?

Yes! There is.

I added ini-values: "pcov.directory=$GITHUB_WORKSPACE" to the setup-php directive like this:

      - name: "Install PHP"
        uses: shivammathur/setup-php@44454db4f0199b8b9685a5d763dc37cbf79108e1 # v2
        with:
          extensions: "intl, pdo_mysql, zip, imap, xml, soap, apcu, redis"
          ini-values: "pcov.directory=$GITHUB_WORKSPACE"
          php-version: "8.4"
          coverage: "pcov"

And all of a sudden the pcov.directory stayed regardless of where I changed the working directory to.

And so with this little change I was again able to get the coverage-data from the business folder whenever i run tests in the framework folder.

Helpful links:

• https://github.com/shivammathur/setup-php#pcov
• https://github.com/krakjoe/pcov/issues/86