Answers.Body: <p>It sounds like you're running into this recent Composer autoloading bug: <a href="https://github.com/composer/composer/issues/6977" rel="nofollow noreferrer">https://github.com/composer/composer/issues/6977</a></p>
  
  <p>Chances are if you <code>composer self-update</code>, the issue will go away.</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2018-01-11T19:20:13.437Z
Answers.Text: Excellent, ok we'll give this a shot and I'll report back. Thanks!
Answers.UserDisplayName: jkilp
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2018-01-11T20:09:58.763Z
Answers.Text: So, our other developer ran that code, but he is saying that he gets exactly the same error. Is there any other information or screenshots that I can attached that would be helpful in possibly diagnosing what the issue could be?
Answers.UserDisplayName: jkilp
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2018-01-11T21:09:32.690Z
Answers.Text: If they run `composer -V`, what version are they on?
Answers.UserDisplayName: Brad Bell
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2018-01-11T21:17:36.383Z
Answers.Text: `version 1.6.2 2018-01-05 15:28:41`
Answers.UserDisplayName: jkilp
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2018-01-11T21:18:32.253Z
Answers.Text: Well, now I'm out of ideas. :)
Answers.UserDisplayName: Brad Bell
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2018-01-12T14:05:00.943Z
Answers.Text: Rats! That is not ideal. Ok, thank you for your help, I'm going to try to do some more investigating on this.
Answers.UserDisplayName: jkilp
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2018-01-11T19:08:54.077Z
Answers.LastActivityDate: 2018-01-11T19:20:42.433Z
Answers.LastEditDate: 2018-01-11T19:20:42.433Z
Answers.UserDisplayName: Brad Bell
Body: <p>We have multiple people working on a craft site using Vagrant and Virtual Box for our local server.</p>
  
  <p>I am running MacOS Sierra, and everything works as expected. A couple of our other developers have updated to run High Sierra, and when they would pull down the git repo for the project this error shows up:</p>
  
  <blockquote>
    <p>include(/vagrant/app/craft/app/vendor/composer/../twig/twig/lib/Twig/Source.php): failed to open stream: No such file or directory</p>
  </blockquote>
  
  <p>This happens when Vagrant is up and running successfully, gulp is watching, and all the user is trying to do is connect to localhost:3000 through their browser. These computers had successfully worked on the project in the past before updating their OS.</p>
  
  <p>We tried doing a fresh pull down of the repo on a computer that had never worked on the project (but also using High Sierra) and we get the same exact error. So the only thing we know that is different between my computer (which works as expected) and the others is that mine is running Sierra and the others are running High Sierra.</p>
  
  <p>We've tried searching online for this issue, but haven't found anybody posting similar enough problems. Also, I am posting this here since it is a Craft CMS project, so if I should switch this to a different stack exchange, let me know. Thank you!</p>
  
  <p>SETUP INFO:</p>
  
  <pre><code>config.vm.box = "ubuntu/trusty32"
  config.vm.box_url = "https://vagrantcloud.com/ubuntu/boxes/trusty32"
  </code></pre>
  
  <p>Tools:
  Vagrant, Virtual Box, Gulp, rsync installed through homebrew</p>
  
  <p>Let me know if there is anything specific about our setup that you'll need to see to be more helpful.</p>
  
Tags: <error-message><php><composer>
Title: PHP warning with composer on MacOS High Sierra: Failed to open stream
ThreadText: # PHP warning with composer on MacOS High Sierra: Failed to open stream
  
  (Asked by: username_0 on 2018-01-11)
  
  We have multiple people working on a craft site using Vagrant and Virtual Box for our local server.
  
  I am running MacOS Sierra, and everything works as expected. A couple of our other developers have updated to run High Sierra, and when they would pull down the git repo for the project this error shows up:
  
  > include(/vagrant/app/craft/app/vendor/composer/../twig/twig/lib/Twig/Source.php): failed to open stream: No such file or directory
  
  This happens when Vagrant is up and running successfully, gulp is watching, and all the user is trying to do is connect to localhost:3000 through their browser. These computers had successfully worked on the project in the past before updating their OS.
  
  We tried doing a fresh pull down of the repo on a computer that had never worked on the project (but also using High Sierra) and we get the same exact error. So the only thing we know that is different between my computer (which works as expected) and the others is that mine is running Sierra and the others are running High Sierra.
  
  We've tried searching online for this issue, but haven't found anybody posting similar enough problems. Also, I am posting this here since it is a Craft CMS project, so if I should switch this to a different stack exchange, let me know. Thank you!
  
  SETUP INFO:
  
  ```
  config.vm.box = "ubuntu/trusty32"
  config.vm.box_url = "https://vagrantcloud.com/ubuntu/boxes/trusty32"
  
  ```
  
  Tools:
  Vagrant, Virtual Box, Gulp, rsync installed through homebrew
  
  Let me know if there is anything specific about our setup that you'll need to see to be more helpful.
  
  **Tags:** error-message, php, composer
  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_1 on 2018-01-11. Score: 1
  
  It sounds like you're running into this recent Composer autoloading bug: <https://github.com/composer/composer/issues/6977>
  
  Chances are if you `composer self-update`, the issue will go away.
  
  > **Comments:**
  > **username_0**: Excellent, ok we'll give this a shot and I'll report back. Thanks!  
  > **username_0**: So, our other developer ran that code, but he is saying that he gets exactly the same error. Is there any other information or screenshots that I can attached that would be helpful in possibly diagnosing what the issue could be?  
  > **username_1**: If they run `composer -V`, what version are they on?  
  > **username_0**: `version 1.6.2 2018-01-05 15:28:41`  
  > **username_1**: Well, now I'm out of ideas. :)  
  > **username_0**: Rats! That is not ideal. Ok, thank you for your help, I'm going to try to do some more investigating on this.  
  
  ---
  
  