Upgrading from 2.4.6-p5 to 2.4.7 not compiling about magento2 HOT 10 CLOSED

@FadedOut: in your case it's most likely related to: Upgrading colinmollenhour/php-redis-session-abstract (v1.5.5 => v1.6.0), see #38728 (and see #38728 (comment) for a workaround)

But it's definitely not related to the issue here.

from magento2.

@hostep @FadedOut @raviverma18th
After downgrading colinmollenhour/php-redis-session-abstract, everything is working again.

composer require colinmollenhour/php-redis-session-abstract:1.5.5

from magento2.

Hi @will-wright1. Thank you for your report.
To speed up processing of this issue, 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.
⚠️ According to the Magento Contribution requirements, all issues must go through the Community Contributions Triage process. Community Contributions Triage is a public meeting.
🕙 You can find the schedule on the Magento Community Calendar page.
📞 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.

from magento2.

Hi @engcom-Dash. 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: 👇

• 1. Verify that issue has all the required information. (Preconditions, Steps to reproduce, Expected result, Actual result).
• 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue.
• 3. Add Area: XXXXX label to the ticket, indicating the functional areas it may be related to.
• 4. Verify that the issue is reproducible on 2.4-develop branch
     Details

     - 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!

• Join Magento Community Engineering Slack and ask your questions in #github channel.

from magento2.

This issue can probably be closed, it turns out it was because composer wasn't on the latest version. I'm not sure why it only fails at the compile stage but ensuring composer was on version 2.7.0 fixed it

from magento2.

I updated composer to the latest version : Composer version 2.7.6 2024-05-04 23:03:15
and the issue is still there

from magento2.

I am getting the same issue in debug.log file,
Composer version 2.7.2 2024-03-11 17:12:18

[2024-05-16T13:41:45.437723+00:00] report.DEBUG: Source class "\Magento\ServiceProxy\Model" for "Magento\ServiceProxy\Model\Logger" generation does not exist. {"exception":"[object] (RuntimeException(code: 0): Source class "\Magento\ServiceProxy\Model" for "Magento\ServiceProxy\Model\Logger" generation does not exist. at /vendor/magento/framework/Code/Generator.php:223)"} []

from magento2.

After doing composer update in Magento 2.4.7 with PHP 8.3 I have the same issue
[2024-05-16T17:13:10.241272+00:00] main.DEBUG: Source class "\Magento\ServiceProxy\Model" for "Magento\ServiceProxy\Model\Logger" generation does not exist. {"exception":"[object] (RuntimeException(code: 0): Source class "\Magento\ServiceProxy\Model" for "Magento\ServiceProxy\Model\Logger" generation does not exist. at /data/web/magento2/vendor/magento/framework/Code/Generator.php:223)"} []

from magento2.

@raviverma18th @LotsofPixels

You're both saying you've done composer update and have this error in the log file? I'm on 2.4.6-p5 and have ran composer update just a little while ago and found the same error in my debug.log file.

I am having a 500 error on my front page now. Trying to revert to backups. No idea if this error is in relation to the site not working. But it was working before I did this composer update and it updated (also added) a few dependencies. I also can't get past 3/9 (Application code generation) on di:compile. It just stops the process with no errors.

Did either of you see these when it updated (hopefully you keep a log of every update?):
Upgrading paragonie/constant_time_encoding (v2.6.3 => v2.7.0)

• Upgrading composer/xdebug-handler (3.0.4 => 3.0.5)
• Upgrading laminas/laminas-validator (2.53.0 => 2.54.0)
• Upgrading psr/http-factory (1.0.2 => 1.1.0)
• Upgrading colinmollenhour/php-redis-session-abstract (v1.5.5 => v1.6.0)
• Installing react/event-loop (v1.5.0)
• Installing evenement/evenement (v3.0.2)
• Installing react/stream (v1.3.0)
• Installing react/cache (v1.2.0)
• Installing react/dns (v1.12.0)
• Installing react/socket (v1.15.0)
• Installing react/child-process (v0.6.5)
• Installing fidry/cpu-core-counter (1.1.0)
• Installing clue/ndjson-react (v1.3.0)
• Upgrading friendsofphp/php-cs-fixer (v3.54.0 => v3.57.1)
• Upgrading phpstan/phpstan (1.10.67 => 1.11.1)
• Upgrading aws/aws-sdk-php (3.305.9 => 3.306.7)

I think the culprit is in here somewhere...arg!!

from magento2.

@FadedOut: in your case it's most likely related to: Upgrading colinmollenhour/php-redis-session-abstract (v1.5.5 => v1.6.0), see #38728 (and see #38728 (comment) for a workaround)

But it's definitely not related to the issue here.

You are a lifesaver! This was exactly my problem. So glad you were able to respond quickly like that, that's much appreciated 👍😀.

@LotsofPixels
This also worked for me as well. I'll just make a sticky note to remove that hard line in like a month, it should hopefully be okay by then.

from magento2.