| Q | A |-------------- | ------ | Documentation | no | Bugfix | no | BC Break | no | New Feature | yes | RFC | no | QA | no

Description

No code change needed, all tests passed locally. My understanding is that CI will automatically run tests for all versions in composer.json.

Furthermore my understanding of the last TSC meeting is that “security only” is redefined to “passive maintenance”, this change should qualify for that.

Whenever you submit a form using "PHP session-upload-progress", and you are also using the ZF session-container object, the session becomes corrupted. It looks like the upload-progress data is being injected into the ZF session data. I can confirm this happens with all releases of the framework. Output of error below:

Stack trace:

#0 /sites/shepherdpups/public_html/vendor/zendframework/library/Zend/Stdlib/ArrayObject.php(412): Zend\Stdlib\ArrayObject->setIteratorClass(NULL)
#1 [internal function]: Zend\Stdlib\ArrayObject->unserialize('a:4:{s:7:"stora...')
#2 /sites/shepherdpups/public_html/vendor/zendframework/library/Zend/Session/SessionManager.php(112): session_start()
#3 /sites/shepherdpups/public_html/module/Application/Module.php(195): Zend\Session\SessionManager->start()
#4 /sites/shepherdpups/public_html/module/Application/Module.php(53): Application\Module->bootstrapSession(Object(Zend\Mvc\MvcEvent))
#5 [internal function]: Application\Module->onBootstrap(Object(Zend\Mvc\MvcEvent))
#6 /sites/shepherdpups/public_html/vendor/zendframework/library/Zend/EventManager/EventManager.php(444): call_user_func(Array, in /sites/shepherdpups/public_html/vendor/zendframework/library/Zend/Stdlib/ArrayObject.php on line 370

Note: just submitting the form corrupts the session container.

Originally posted by @headbutt at https://github.com/zendframework/zend-progressbar/issues/3

| Q | A |-------------- | ------ | Documentation | no | Bugfix | yes | BC Break | no | New Feature | no | RFC | no | QA | no

Description

The $text parameter is documented to take a string, not a ?string and in fact the Console adapter unconditionally calls a variant of substr() on the given $text to shorten it to the configured display width.

With PHP 8.1 this fails, because native functions no longer accept null for a string parameter:

TypeError: grapheme_substr(): Argument #1 ($string) must be of type string, null given in […]

| Q | A |-------------- | ------ | Documentation | no | Bugfix | no | BC Break | no | New Feature | no | RFC | no | QA | yes

Description

Spun out of #17 to unbreak the CI in the 2.11.x base branch and to not mix unrelated changes.

| Q | A |-------------- | ------ | Documentation | no | Bugfix | no | BC Break | no | New Feature | no | RFC | no | QA | yes

Description

Two little housekeeping changes:

1. The README.md change fixes this: https://github.com/laminas/laminas-progressbar/runs/7557088552?check_suite_focus=true
2. The .gitattributes change correctly strips phpcs.xml.dist from the distribution.

Welcome to Renovate! This is an onboarding PR to help you understand and configure settings before regular Pull Requests begin.

🚦 To activate Renovate, merge this Pull Request. To disable Renovate, simply close this Pull Request unmerged.

Detected Package Files

• composer.json (composer)
• .github/workflows/auto-close.yml (github-actions)
• .github/workflows/continuous-integration.yml (github-actions)
• .github/workflows/docs-build.yml (github-actions)
• .github/workflows/release-on-milestone-closed.yml (github-actions)

Configuration Summary

Based on the default config's presets, Renovate will:

• Start dependency updates only once this onboarding PR is merged
• Enable Renovate Dependency Dashboard creation.
• Ignore node_modules, bower_components, vendor and various test/tests directories.
• Automerge patch and minor upgrades if they pass tests.
• If automerging, push the new commit directly to the base branch (no PR).
• Wait for branch tests to pass or fail before creating the PR.
• Rebase existing PRs any time the base branch has been updated.
• Separate major versions of dependencies into individual branches/PRs.
• Do not separate patch and minor upgrades into separate PRs for the same dependency.
• Raise PR when vulnerability alerts are detected.
• Evaluate schedules according to timezone UTC.
• Append Signed-off-by: to signoff Git commits.
• Apply label renovate to PRs.
• Group all minor and patch updates together.
• Default configuration for repositories in the Laminas organisation

🔡 Would you like to change the way Renovate is upgrading your dependencies? Simply edit the renovate.json in this branch with your custom config and the list of Pull Requests in the "What to Expect" section below will be updated the next time Renovate runs.

What to Expect

With your current configuration, Renovate will create 3 Pull Requests:

❓ Got questions? Check out Renovate's Docs, particularly the Getting Started section. If you need any further assistance then you can also request help here.

Read more information about the use of Renovate Bot within Laminas.

| Q | A |-------------- | ------ | QA | yes

Description

Adding Renovate to Laminas, Mezzio repositories. https://gist.github.com/weierophinney/49ca8ae2b916d898dd3d4162b26ff41b

• Configure minimum supported PHP version
• Update composer dependencies
• Update to reusable Continuous Integration workflow
• Update to reusable Automatic Releases workflow

| Q | A |-------------- | ------ | Documentation | no | Bugfix | no | BC Break | no | New Feature | yes | RFC | no | QA | no

Description

This PR adds support for PHP 8.1 and laminas-form ^3 (which was necessary for that) This PR is also necessary to add PHP 8.1 support to laminas-file.

Only some minor code changes were required because of a deprecation warning for fopen.

Feature Request

| Q | A |------------ | ------ | QA | yes

Summary

As decided during the Technical-Steering-Committee Meeting on August 3rd, 2020, Laminas wants to implement vimeo/psalm in all packages.

Implementing psalm is quite easy.

Required

• [ ] Create a .psalm.xml.dist in the project root
• [ ] Copy and paste the contents from this psalm.xml.dist
• [ ] Run $ composer require vimeo/psalm
• [ ] Run $ vendor/bin/psalm --set-baseline=psalm-baseline.xml
• [ ] Add a composer script static-analysis with the command psalm --shepherd --stats
• [ ] Add a new line to script: in .travis.yml: - if [[ $TEST_COVERAGE == 'true' ]]; then composer static-analysis ; fi
• [ ] Remove phpstan from the project (phpstan.neon.dist, .travis.yml entry, composer.json require-dev and scripts)

Optional

• [ ] Fix as many psalm errors as possible.

This is not a real issue or bug, just putting it here for further reference (as it does not come up anywhere yet in relation to zend-progressbar when searching for it)

Running a cli script, which uses zend-progressbar as a cronjob leads to an exit status != 0 displaying the following message:

stty: standard input: Inappropriate ioctl for device

Obviously a cli command being run through cron does not need a progress bar ;) Although one might use the same command in different contexts.. I am not sure wether this even can be "fixed" or wether its worth it. Feel free to close this issue!

I am grateful for this great component/framework and everyone contributing to it. cheers

Originally posted by @lenada at https://github.com/zendframework/zend-progressbar/issues/23

• [x] I was not able to find an open or closed issue matching what I'm seeing.
• [ ] This is not a question. (Questions should be asked on chat (Signup here) or our forums.)

Provide a narrative description of what you are trying to accomplish. I just wanted to play around with the examples to realize a progressbar with a JsPush-adapter.

Code to reproduce the issue

See the examples in the documentation and my question in stackoverflow, too: https://stackoverflow.com/questions/50396543/zend-framework-3-how-to-use-and-push-update-progressbar

Expected results

The update-function should have been called and the progressbar should have been updated.....

Actual results

Nothing happened.

After renaming the update function to "ZendProgressBarUpdate" and adding the line

$this->adapter->setUpdateMethodName("ZendProgressBarUpdate");

everything worked as expected.

So I suggest to update the manual.

Originally posted by @kolbius at https://github.com/zendframework/zend-progressbar/issues/26