Closed mrlerch closed 2 years ago
Hi @mrlerch. 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.
:movie_camera: You can find the recording of the previous Community Contributions Triage on the Magento Youtube Channel
:pencil2: Feel free to post questions/proposals/feedback related to the Community Contributions Triage process to the corresponding Slack Channel
Thanks for reporting this @mrlerch
For the engcom squad reviewers: note that there is a 3rd party module woopra/analytics-m2
in the stacktrace that probably is the cause of this issue and it might not immediately be reproducible in a vanilla Magento installation.
But that doesn't mean this bug isn't real.
This bug might possibly have been introduced by https://github.com/magento/magento2/pull/32002 where declare(strict_types=1);
got added to the Escaper class.
We should be more careful when adding that declaration to existing files and make sure that all calls in that class are forced to use the correct types.
@ihor-sviziev: does that make sense? Maybe collaborate with the other maintainers about this a bit if you can 🙂
The suggested change is not 100% correct as it would still allow addslashes
to fail with the same problem when $addSlashes
is set to true
@hostep this error come from same problem because declare(strict_types=1) was added: https://github.com/magento/magento2/issues/34415... its about a totally different file but just wanted to add to your comment about "We should be more careful when adding that declaration to existing files"
Here is my post on github.
Now what…
https://github.com/magento/magento2/issues/34413
Sent from my iPhone (mobile)
The information contained in this communication is potentially confidential, and intended only for the use of the addressee. If you received this communication in error, please notify us by return e-mail and delete this communication and all copies, including all attachments.
On Oct 24, 2021, at 11:22 AM, Simon Maass @.***> wrote:
@hostep this error come from same problem because declare(strict_types=1) was added: #34415
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or unsubscribe. Triage notifications on the go with GitHub Mobile for iOS or Android.
@sidolov, please set priority to P1
Hi @SergeyP18. 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:
Issue: Format is valid
will be added to the issue automatically. Please, edit issue description if needed, until label Issue: Format is valid
appears.Issue: Clear Description
label to the issue by yourself.Component: XXXXX
label(s) to the ticket, indicating the components it may be related to.2.4-develop
branch@magento give me 2.4-develop instance
to deploy test instance on Magento infrastructure. 2.4-develop
branch, please, add the label Reproduced on 2.4.x
.Error in a third-party module, check for the type of the transferred value does not pass
There is no check for value type. There is only a check if there is a value
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.
Hi @mrlerch , Thank you for reporting and collaboration. However, Woopra is a 3rd party extension and code of this extension is not part of https://github.com/magento/magento2 git repository. We are closing this issue as community is not able to provide fix for it in this repository. All questions, issue reports and fix for them should be addressed to the corresponding extension owners(support) on the Magento Market place page Thank you.
Preconditions (*)
Steps to reproduce (*)
Expected result (*)
Actual result (*)
Please provide Severity assessment for the Issue as Reporter. This information will help during Confirmation and Issue triage processes.
Looked at the function including line 417 in Escaper.php
Temporary fix: Created a module that overrides this function with this one:
Now it is working but I think that this is a bug possibly (why would there be an error if data is empty?)