These are chat archives for composer/composer

27th
Oct 2016
Ben Johnson
@cbj4074
Oct 27 2016 14:46
Anybody know why Composer will gladly use tags that are pushed while in "detached HEAD state" (and therefore not to any specific branch)?
We had a situation in which a developer accidentally created a tag while in detached HEAD state and pushed to a remote (origin) and Composer used that tag during update.
(instead of the latest tag on master)
Just curious what the reason is for that behavior. It seems less than ideal.
Rob
@alcohol
Oct 27 2016 14:55
because the tag will still reference a commit
and we simply checkout that commit
not our fault someone made a bad tag
nothing we can do about detecting that
cause from a git perspective it is perfectly valid
@cbj4074 does that answer your question?
Ben Johnson
@cbj4074
Oct 27 2016 15:17
@alcohol It does! Thanks, Rob!

While I have your ear, any idea on that other issue I'm seeing frequently, and seemingly all of a sudden?

Failed to decode response: zlib_decode(): data error

When it happens, Composer says

Retrying with degraded mode, check https://getcomposer.org/doc/articles/troubleshooting.md#degraded-mode for more info

and it seems to move ahead successfully, for whatever that's worth.

Rob
@alcohol
Oct 27 2016 15:24
are you using vagrant/virtualbox?
Ben Johnson
@cbj4074
Oct 27 2016 15:25
Yes, with a network-mounted filesystem
Rob
@alcohol
Oct 27 2016 15:25
well there you go
Ben Johnson
@cbj4074
Oct 27 2016 15:25
Why now? I've had this setup for 2 years.
And haven't self-updated Composer for a month or so.
it's not a composer issue
so updating composer wont help fix it
Ben Johnson
@cbj4074
Oct 27 2016 15:27
I was asking more because I wondered if it was always an issue but Composer didn't squawk about it until recently.
Rob
@alcohol
Oct 27 2016 15:27
like i said, it is not a composer issue
Ben Johnson
@cbj4074
Oct 27 2016 15:27
I believe you.
Rob
@alcohol
Oct 27 2016 15:28
and there can be various causes
Ben Johnson
@cbj4074
Oct 27 2016 15:28
I'm reading through this massive Issue in an effort to determine the actual cause(s).
This is helpful, though, thank you.
Ben Johnson
@cbj4074
Oct 27 2016 16:03

So, it seems that recent updates to VirtualBox had some effect on IPv6 routing, despite not changing any other networking settings in VirtualBox. Accordingly, this tip, straight form the docs at https://getcomposer.org/doc/articles/troubleshooting.md#degraded-mode , fixed it (Ubutu 16.04 guest OS):

sudo sh -c "echo 'precedence ::ffff:0:0/96 100' >> /etc/gai.conf"