Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Symlink disable causing an error #7379

Closed
pursehouse opened this issue May 31, 2018 · 8 comments
Closed

Symlink disable causing an error #7379

pursehouse opened this issue May 31, 2018 · 8 comments
Labels
Milestone

Comments

@pursehouse
Copy link

pursehouse commented May 31, 2018

I'm having this issue in Windows 10 Bash.
Composer version 1.6.5 2018-05-04 11:44:59

I already tried deleting the composer.lock and deleted the links that were there before I added the option.

running composer install this gives me an error:

Loading composer repositories with package information
[ErrorException]
stream_context_create(): options should have the form ["wrappername"]["optionname"] = $value

with the config...

"repositories": {
    "vendor/package": {
        "type": "path",
        "url": "/path/to/vendor/package",
        "options" : {
            "symlink" : false
        }
    }
}

#5048 didn't seem to have the solution

any ideas? Thanks!

@pursehouse
Copy link
Author

problem solved! I had it in several repo's and accidentally added it to a VCS repo as well. Perhaps the composer error display could use an upgrade in that situation?

@Seldaek
Copy link
Member

Seldaek commented May 31, 2018

Yeah we pass-through options straight to the stream context for VCS repos. It's kinda hard to validate this as it has many possible options.

@Seldaek Seldaek closed this as completed May 31, 2018
@pursehouse
Copy link
Author

@Seldaek but it could at least output more info of what data was involved with the error, I guess just an upgrade of the generic error display system? I've not looked at the internals. But to at least show the strings/arrays involved at that moment would sure solve a lot of headaches

@Seldaek
Copy link
Member

Seldaek commented Jun 1, 2018

Sure I guess this could be done relatively easily in StreamContextFactory where I assume the error originated from.

@Seldaek Seldaek reopened this Jun 1, 2018
@Seldaek Seldaek added the Bug label Jun 1, 2018
@Seldaek Seldaek added this to the Bugs milestone Jun 1, 2018
@pursehouse
Copy link
Author

wonderful! thanks

@typoworx-de
Copy link

I also had this issue after update to latest composer release (Composer version 1.9.1 2019-11-01 17:20:17). In my previous older release I also noticed this message as "warning". Since update is was a breaking error.

I noticed I had to remove "options": { "symlink": true } from remote-repositories. For development I also use a local-vendor repository at the moment, which doesn't seem to be affected (symlink: true does not throw error at the moment).

I think composer should throw a more informative error-message being able to note where the real problem is.

@Seldaek Seldaek modified the milestones: Bugs, 2.2 May 15, 2022
@Seldaek
Copy link
Member

Seldaek commented May 24, 2022

Cannot repro anymore, so closing. If you still see this please share a composer.json that reproduces it.

@Seldaek Seldaek closed this as completed May 24, 2022
@PascalBrouwers
Copy link

adding the package with --prefer-source also seemed to be required

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants