setup:di:compile - directory not empty

[Eddcapone]

Summary

The setup:di:compile command often fails because the directory is not empty.

Examples

Proposed solution

Delete the folder and make sure it is empty, before firing the command that triggers the compilation.

Release note

No response

Triage and priority

• Severity: S0 - Affects critical data or functionality and leaves users without workaround.
• Severity: S1 - Affects critical data or functionality and forces users to employ a workaround.
• Severity: S2 - Affects non-critical data or functionality and forces users to employ a workaround.
• Severity: S3 - Affects non-critical data or functionality and does not force users to employ a workaround.
• Severity: S4 - Affects aesthetics, professional look and feel, “quality” or “usability”.

[m2-assistant]

Hi @Eddcapone. 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.

• 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.

[m2-assistant]

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: 👇

• 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

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

[engcom-November]

Hello @Eddcapone ,

Thank you for your report and collaboration.

We attempted to replicate the issue on our end but were unable to reproduce it. Could you please provide a more detailed description of the problem, including clear steps to reproduce it? Additionally, it would be helpful if you could share the expected versus actual results, and, if possible, include screencasts demonstrating the issue.

Note: Could you please mention which Folder your deleting?

Until then, we are marking this issue as “Needs Update.”

Thank you for your understanding and support!

[hostep]

@Eddcapone, if I have to guess, you're probably running this command in an environment that receives traffic the moment you run the command? Or maybe a Magento cronjob is running at the same time?
A way around this, would be to enable maintenance mode first, then run setup:di:compile and then disable maintenance mode again. Maybe give that a try?
If that doesn't solve it, you'll have to figure out if there is any other process that bootstraps your Magento instance somehow which then probably tries to generate code in that directory at runtime.

[engcom-November]

Hello @Eddcapone ,

Thank you for your report and collaboration.

Could you please respond to the [comments](#40059 (comment) , #40059 (comment) ) above and let us know whether the issue has been resolved?

Thank You!

[engcom-November]

Hello @Eddcapone ,

Follow Up on the above Comment.

Thank You!