Closed arsalanworld closed 1 month ago
Hi @arsalanworld. Thank you for your report. To help us process this issue please make sure that you provided the following information:
Please make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce. To deploy vanilla Magento instance on our environment, please, add a comment to the issue:
@magento give me 2.4-develop instance
- upcoming 2.4.x release
For more details, please, review the Magento Contributor Assistant documentation.
Please, add a comment to assign the issue: @magento I am working on this
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, please 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
@magento I am working on this
Hi @arsalanworld! :wave:
Thank you for collaboration. Only members of Community Contributors Team are allowed to be assigned to the issue. Please use @magento add to contributors team
command to join Contributors team.
@magento add to contributors team
Hi @arsalanworld! :wave: Thank you for joining. Please accept team invitation :point_right: here :point_left: and add your comment one more time.
@magento/klarna could someone look on it?
Hi @engcom-Delta. 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 @engcom-Hotel. 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.
Hello @arsalanworld,
Thanks for reporting the issue. We have tried to reproduce the issue with the above-mentioned steps and are able to reproduce it by making the object of Klarna\Core\Cron\CleanLogs
and call the execute
method.
Please find below the screenshot for reference:
Thanks
:white_check_mark: Jira issue https://jira.corp.magento.com/browse/AC-1374 is successfully created for this GitHub issue.
:white_check_mark: Confirmed by @engcom-Hotel. Thank you for verifying the issue.
Issue Available: @engcom-Hotel, You will be automatically unassigned. Contributors/Maintainers can claim this issue to continue. To reclaim and continue work, reassign the ticket to yourself.
I have a brand new Adobe commerce cloud project version 2.4.3 that shows the exact same errors. When I review the structure of the table klarna_logs
it is missing the column store_id.
MariaDB [main]> DESCRIBE klarna_logs;
+--------------+--------------+------+-----+---------------------+----------------+
| Field | Type | Null | Key | Default | Extra |
+--------------+--------------+------+-----+---------------------+----------------+
| log_id | smallint(6) | NO | PRI | NULL | auto_increment |
| status | varchar(255) | NO | | NULL | |
| action | varchar(255) | YES | MUL | NULL | |
| klarna_id | varchar(255) | YES | MUL | NULL | |
| increment_id | varchar(255) | YES | | NULL | |
| url | varchar(255) | NO | | NULL | |
| method | varchar(255) | NO | | NULL | |
| service | varchar(255) | NO | | NULL | |
| request | text | YES | | NULL | |
| response | text | YES | | NULL | |
| created_at | datetime | NO | | current_timestamp() | |
+--------------+--------------+------+-----+---------------------+----------------+
11 rows in set (0.00 sec)
Hello @arsalanworld,
As Klarna is not part of the bundled extension now, we are marking this issue as 3rd party extension. Hence closing this issue.
Thanks
Preconditions (*)
Steps to reproduce (*)
var/log/debug.log
log fileExpected result (*)
Actual result (*)
klarna_logs
ASmain_table
WHERE (store_id
= '1') AND (created_at
<= '2021-07-06') Exception (PDOException): SQLSTATE[42S22]: Column not found: 1054 Unknown column 'store_id' in 'where clause'Please provide Severity assessment for the Issue as Reporter. This information will help during Confirmation and Issue triage processes.