Open magentix opened 2 years ago
Hi @magentix. Thank you for your report. To speed up processing of this issue, make sure that you provided the following information:
Make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce. To deploy vanilla Magento instance on our environment, Add a comment to the issue:
@magento give me 2.4-develop instance
- upcoming 2.4.x release
For more details, review the Magento Contributor Assistant documentation.
Add a comment to assign the issue: @magento I am working on this
To learn more about issue processing workflow, refer to the Code Contributions.
Join Magento Community Engineering Slack and ask your questions in #github channel.
:warning: According to the Magento Contribution requirements, all issues must go through the Community Contributions Triage process. Community Contributions Triage is a public meeting.
:clock10: You can find the schedule on the Magento Community Calendar page.
:telephone_receiver: The triage of issues happens in the queue order. If you want to speed up the delivery of your contribution, join the Community Contributions Triage session to discuss the appropriate ticket.
:pencil2: Feel free to post questions/proposals/feedback related to the Community Contributions Triage process to the corresponding Slack Channel
Hi @engcom-November. Thank you for working on this issue. In order to make sure that issue has enough information and ready for development, please read and check the following instruction: :point_down:
[ ] 1. Verify that issue has all the required information. (Preconditions, Steps to reproduce, Expected result, Actual result).Details
If the issue has a valid description, the label Issue: Format is valid
will be added to the issue automatically. Please, edit issue description if needed, until label Issue: Format is valid
appears.
[ ] 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue. If the report is valid, add Issue: Clear Description
label to the issue by yourself.
[ ] 3. Add Component: XXXXX
label(s) to the ticket, indicating the components it may be related to.
[ ] 4. Verify that the issue is reproducible on 2.4-develop
branchDetails
- Add the comment @magento give me 2.4-develop instance
to deploy test instance on Magento infrastructure.
- If the issue is reproducible on 2.4-develop
branch, please, add the label Reproduced on 2.4.x
.
- If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and stop verification process here!
[ ] 5. Add label Issue: Confirmed
once verification is complete.
[ ] 6. Make sure that automatic system confirms that report has been added to the backlog.
@magento give me 2.4-develop instance
Hi @engcom-November. Thank you for your request. I'm working on Magento instance for you.
Hi @engcom-November, unfortunately there is no ability to deploy Magento instance at the moment. Please try again later.
Verified the issues on Magento 2.4-develop branch and 2.4.4 versions and the issue is reproducible on 2.4.4 instance but not on 2.4-develop branch. Steps performed:
:white_check_mark: Jira issue https://jira.corp.magento.com/browse/AC-2892 is successfully created for this GitHub issue.
:white_check_mark: Confirmed by @engcom-November. Thank you for verifying the issue.
Issue Available: @engcom-November, You will be automatically unassigned. Contributors/Maintainers can claim this issue to continue. To reclaim and continue work, reassign the ticket to yourself.
Facing the same issue. If this is a known issue then does any patch available to fix this issue?
@Vishrootways: try updating magento/zendframework1
to version 1.15.1, see https://github.com/magento/zf1/pull/46#issuecomment-1165267804
@hostep Updating magento/zendframework1 to version 1.15.1 works. Thank you
This is issue is only partially fixed in 1.15.1.
I still got error, but in different file :
PHP Fatal error: During inheritance of ArrayAccess: Uncaught Exception: Deprecated Functionality: Return type of Zend_Memory_Value::offsetExists($offset) should either be compatible with ArrayAccess::offsetExists(mixed $offset): bool, or the #[\\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /var/www/html/vendor/magento/zendframework1/library/Zend/Memory/Value.php
=> magento/zendframework1/library/Zend/Memory/Value.php
Here's a patch :
--- a/library/Zend/Memory/Value.php
+++ b/library/Zend/Memory/Value.php
@@ -86,7 +86,7 @@
* @param integer $offset
* @return boolean
*/
- public function offsetExists($offset)
+ public function offsetExists(mixed $offset): bool
{
return $offset >= 0 && $offset < strlen($this->_value);
}
@@ -98,7 +98,7 @@
* @param integer $offset
* @return string
*/
- public function offsetGet($offset)
+ public function offsetGet(mixed $offset): mixed
{
return $this->_value[$offset];
}
@@ -110,7 +110,7 @@
* @param integer $offset
* @param string $char
*/
- public function offsetSet($offset, $char)
+ public function offsetSet(mixed $offset, mixed $value): void
{
$this->_value[$offset] = $char;
@@ -126,7 +126,7 @@
*
* @param integer $offset
*/
- public function offsetUnset($offset)
+ public function offsetUnset(mixed $offset): void
{
unset($this->_value[$offset]);
@Nuranto: could you report this as a new issue on https://github.com/magento/zf1/issues? I think it will get picked up sooner that way, thanks! 🙂
Done 👍
Hi!
Fixed for me after zendframework1 1.15.1 upgrade:
Updating magento/zendframework1 (1.15.0 => 1.15.1): Downloading (connecting.Downloading (100%)
@magento give me 2.4.5-p1 instance
Hi @SPbryan007. Thank you for your request. I'm working on Magento instance for you.
Hi @SPbryan007, here is your Magento Instance: https://72f6bd7b7d0063653c526ba435e0f2f8.instances.magento-community.engineering Admin access: https://72f6bd7b7d0063653c526ba435e0f2f8.instances.magento-community.engineering/admin_9959 Login: 0a17b5ea Password: 8ca9eca47982
Preconditions (*)
Steps to reproduce (*)
Expected result (*)
Actual result (*)
The error happens with the Magento\Shipping\Model\Shipping\LabelGenerator::combineLabelsPdf method.
Additional Information: Please refer below comment:
https://github.com/magento/magento2/issues/35335#issuecomment-1103902652
Please provide Severity assessment for the Issue as Reporter. This information will help during Confirmation and Issue triage processes.