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

Bump minimum version to PHP 7.1 for Symfony 4 #22733

Merged
merged 3 commits into from May 18, 2017

Conversation

@fabpot
Member

fabpot commented May 17, 2017

Q A
Branch? master
Bug fix? no
New feature? yes-ish?
BC breaks? yes-ish?
Deprecations? no
Tests pass? yes
Fixed tickets n/a
License MIT
Doc PR n/a
Show outdated Hide outdated .travis.yml
- php: 5.5
- php: 5.6
- php: 7.0
- php: 7.1.0

This comment has been minimized.

@stof

stof May 17, 2017

Member

we should have a test running the fullstack testsuite on latest 7.1 too IMO

@stof

stof May 17, 2017

Member

we should have a test running the fullstack testsuite on latest 7.1 too IMO

This comment has been minimized.

@nicolas-grekas

nicolas-grekas May 17, 2017

Member

We have one, like in the previous branches: the deps=low line does it

@nicolas-grekas

nicolas-grekas May 17, 2017

Member

We have one, like in the previous branches: the deps=low line does it

This comment has been minimized.

@stof

stof May 18, 2017

Member

deps=low is a per-component build, not a fullstack build. It does not test the requirements of the fullstack

@stof

stof May 18, 2017

Member

deps=low is a per-component build, not a fullstack build. It does not test the requirements of the fullstack

This comment has been minimized.

@nicolas-grekas

nicolas-grekas May 18, 2017

Member

Unless I misunderstood what you meant, the line you're​ asking for doesn't exist on the SF3 lines. Thus we should not add it since it has never been required.

@nicolas-grekas

nicolas-grekas May 18, 2017

Member

Unless I misunderstood what you meant, the line you're​ asking for doesn't exist on the SF3 lines. Thus we should not add it since it has never been required.

Show outdated Hide outdated appveyor.yml
@@ -59,8 +57,6 @@ test_script:
- cd c:\php && 7z x php-7.1.3-Win32-VC14-x64.zip -y >nul && copy /Y php.ini-min php.ini
- cd c:\projects\symfony
- php phpunit src\Symfony --exclude-group benchmark,intl-data || SET X=!errorlevel!
- cd c:\php && 7z x php-5.5.9-nts-Win32-VC11-x86.zip -y >nul && copy /Y php.ini-min php.ini
- cd c:\projects\symfony
- SET SYMFONY_PHPUNIT_SKIPPED_TESTS=phpunit.skipped
- php phpunit src\Symfony --exclude-group benchmark,intl-data || SET X=!errorlevel!

This comment has been minimized.

@stof

stof May 17, 2017

Member

this line should be removed, as it was the one running tests on 5.5.9. there is no need to run tests a second time on 7.1.3 without changing the php.ini (skipped tests will stay the same)

@stof

stof May 17, 2017

Member

this line should be removed, as it was the one running tests on 5.5.9. there is no need to run tests a second time on 7.1.3 without changing the php.ini (skipped tests will stay the same)

@stof

This comment has been minimized.

Show comment
Hide comment
@stof

stof May 17, 2017

Member

@fabpot when bumping the version to 4.0, you forgot to update all inter-component requirements to allow them to use the 4.0 version of other components in their own 4.0 versions

Member

stof commented May 17, 2017

@fabpot when bumping the version to 4.0, you forgot to update all inter-component requirements to allow them to use the 4.0 version of other components in their own 4.0 versions

@nicolas-grekas

This comment has been minimized.

Show comment
Hide comment
@nicolas-grekas

nicolas-grekas May 17, 2017

Member

Looks like this requires us to drop HHVM, impossible to make it run on the CI. I'm fine with that personally.

Member

nicolas-grekas commented May 17, 2017

Looks like this requires us to drop HHVM, impossible to make it run on the CI. I'm fine with that personally.

@fabpot

This comment has been minimized.

Show comment
Hide comment
@javiereguiluz

This comment has been minimized.

Show comment
Hide comment
@javiereguiluz

javiereguiluz May 18, 2017

Member

In addition to the poll, according to the latest global PHP stats, HHVM is used by 0.36% of PHP developers. The number is practically zero ... but maybe there are some high-profile clients there (Facebook is using it, Slack was thinking about using it, ...)

Member

javiereguiluz commented May 18, 2017

In addition to the poll, according to the latest global PHP stats, HHVM is used by 0.36% of PHP developers. The number is practically zero ... but maybe there are some high-profile clients there (Facebook is using it, Slack was thinking about using it, ...)

@Seldaek

This comment has been minimized.

Show comment
Hide comment
@Seldaek

Seldaek May 18, 2017

Member

@javiereguiluz please don't forget that the stats are about number of composer installs.. That doesn't translate 1:1 to users, as some may do more installs than others. I think it's mostly interesting to see trends over time as exact point-in-time numbers can't be fully trusted.

Member

Seldaek commented May 18, 2017

@javiereguiluz please don't forget that the stats are about number of composer installs.. That doesn't translate 1:1 to users, as some may do more installs than others. I think it's mostly interesting to see trends over time as exact point-in-time numbers can't be fully trusted.

@stof

This comment has been minimized.

Show comment
Hide comment
@stof

stof May 18, 2017

Member

@nicolas-grekas HHVM has 2 modes: PHP 5 mode and PHP 7 mode. IIRC, it runs in PHP 5 mode by default. We should add hhvm.php7.all = 1 in the HHVM INI file.

Member

stof commented May 18, 2017

@nicolas-grekas HHVM has 2 modes: PHP 5 mode and PHP 7 mode. IIRC, it runs in PHP 5 mode by default. We should add hhvm.php7.all = 1 in the HHVM INI file.

@nicolas-grekas

This comment has been minimized.

Show comment
Hide comment
@nicolas-grekas

nicolas-grekas May 18, 2017

Member

I just tried again this mode, same failure. We'd need a php 7.1 mode. There is just no way currently to make hhvm run on a 7.1 code base. HHVM advertises itself as 70099 so even Composer cant.
Just dropping for now.

Member

nicolas-grekas commented May 18, 2017

I just tried again this mode, same failure. We'd need a php 7.1 mode. There is just no way currently to make hhvm run on a 7.1 code base. HHVM advertises itself as 70099 so even Composer cant.
Just dropping for now.

@stof

This comment has been minimized.

Show comment
Hide comment
@stof

stof May 18, 2017

Member

Have you tried using the latest HHVM rather than 3.18 ? they may have updated their PHP 7 mode to expose it as 7.1 later

Member

stof commented May 18, 2017

Have you tried using the latest HHVM rather than 3.18 ? they may have updated their PHP 7 mode to expose it as 7.1 later

@nicolas-grekas

This comment has been minimized.

Show comment
Hide comment
@nicolas-grekas

nicolas-grekas May 18, 2017

Member

Yep, 3.19 locally, same result

Member

nicolas-grekas commented May 18, 2017

Yep, 3.19 locally, same result

Show outdated Hide outdated .travis.yml
# Load fixtures
if [[ ! $skip ]]; then
sleep 5

This comment has been minimized.

@stof

stof May 18, 2017

Member

why sleeping ?

@stof

stof May 18, 2017

Member

why sleeping ?

This comment has been minimized.

@nicolas-grekas

nicolas-grekas May 18, 2017

Member

Previously we did not require it because we had some extensions to compile, which gave some time for the ldap sever to start in the background. But now we have to sleep a bit to let it start.

@nicolas-grekas

nicolas-grekas May 18, 2017

Member

Previously we did not require it because we had some extensions to compile, which gave some time for the ldap sever to start in the background. But now we have to sleep a bit to let it start.

Show outdated Hide outdated composer.json
@@ -16,7 +16,7 @@
}
],
"require": {
"php": ">=5.5.9",
"php": "^7.1.0",

This comment has been minimized.

@nicolas-grekas

nicolas-grekas May 18, 2017

Member

shouldn't we keep the ">=" operator?

@nicolas-grekas

nicolas-grekas May 18, 2017

Member

shouldn't we keep the ">=" operator?

This comment has been minimized.

@stof

stof May 18, 2017

Member

Well, this constraint forbids using the existing version with PHP 8. I think it is fine. I'm almost sure that the current code will not work with PHP 8 (PHP major versions will break BC for sure if we look at the existing releases where even minor versions have a hard time preserving BC fully). This way, when PHP 8 starts to come out, we can update our requirements once we start testing it with PHP 7

@stof

stof May 18, 2017

Member

Well, this constraint forbids using the existing version with PHP 8. I think it is fine. I'm almost sure that the current code will not work with PHP 8 (PHP major versions will break BC for sure if we look at the existing releases where even minor versions have a hard time preserving BC fully). This way, when PHP 8 starts to come out, we can update our requirements once we start testing it with PHP 7

This comment has been minimized.

@Th3Mouk

Th3Mouk May 18, 2017

Contributor

This way exclude PHP8, IMO it's a good thing and avoid future PR to exclude it and then re-enable PHP8 after BC breaks corrected.

@Th3Mouk

Th3Mouk May 18, 2017

Contributor

This way exclude PHP8, IMO it's a good thing and avoid future PR to exclude it and then re-enable PHP8 after BC breaks corrected.

@@ -83,11 +77,11 @@ before_install:
echo extension = ldap.so >> $INI
echo extension = redis.so >> $INI
echo extension = memcached.so >> $INI
[[ $PHP = 5.* ]] && echo extension = mongo.so >> $INI
[[ $PHP = 5.* ]] && echo extension = memcache.so >> $INI
#echo extension = mongodb.so >> $INI

This comment has been minimized.

@nicolas-grekas

nicolas-grekas May 18, 2017

Member

the test suite does not pass yet with mongodb - but this is not master specific so should be handled on a lower branch

@nicolas-grekas

nicolas-grekas May 18, 2017

Member

the test suite does not pass yet with mongodb - but this is not master specific so should be handled on a lower branch

@nicolas-grekas

👍
thanks to Doctrine guys who quickly merged the PR allowing ~4.0 on their side
min PHP version is 7.1.3, which fixes a segfault that we were hitting

@nicolas-grekas nicolas-grekas added this to the 4.0 milestone May 18, 2017

@nicolas-grekas

This comment has been minimized.

Show comment
Hide comment
@nicolas-grekas

nicolas-grekas May 18, 2017

Member

Now with all lowest deps updated to ~3.4, same process we did for 3.0

Member

nicolas-grekas commented May 18, 2017

Now with all lowest deps updated to ~3.4, same process we did for 3.0

@dunglas

This comment has been minimized.

Show comment
Hide comment
@dunglas

dunglas May 18, 2017

Member

👍 even if I would be to use >=7.1.3 instead of ^7.1.3 because:

  • It will prevent people to upgrade to PHP 8 because of old Symfony apps
  • PHP is almost always backward compatible
  • PHP doesn't respect strictly semver
  • Laravel and most other projects use this notation
Member

dunglas commented May 18, 2017

👍 even if I would be to use >=7.1.3 instead of ^7.1.3 because:

  • It will prevent people to upgrade to PHP 8 because of old Symfony apps
  • PHP is almost always backward compatible
  • PHP doesn't respect strictly semver
  • Laravel and most other projects use this notation
Show outdated Hide outdated src/Symfony/Bridge/Twig/composer.json
"symfony/translation": "~3.4|~4.0",
"symfony/yaml": "~3.4|~4.0",
"symfony/security": "~3.4|~4.0",
"symfony/security-acl": "~3.4|~4.0",

This comment has been minimized.

@dunglas

dunglas May 18, 2017

Member

"symfony/security-acl": "~3.4", (4.0 doesn't exist)

@dunglas

dunglas May 18, 2017

Member

"symfony/security-acl": "~3.4", (4.0 doesn't exist)

Show outdated Hide outdated src/Symfony/Bundle/SecurityBundle/composer.json
"symfony/form": "~3.4|~4.0",
"symfony/framework-bundle": "~3.4|~4.0",
"symfony/http-foundation": "~3.4|~4.0",
"symfony/security-acl": "~3.4|~4.0",

This comment has been minimized.

@dunglas

dunglas May 18, 2017

Member

"symfony/security-acl": "~3.4", (4.0 doesn't exist)

@dunglas

dunglas May 18, 2017

Member

"symfony/security-acl": "~3.4", (4.0 doesn't exist)

"symfony/http-foundation": "~3.3|~4.0.0",
"symfony/http-kernel": "~3.3|~4.0.0",
"symfony/cache": "~3.4|~4.0",
"symfony/class-loader": "~3.4|~4.0",

This comment has been minimized.

@xabbuh

xabbuh May 18, 2017

Member

The ClassLoader component won't have a 4.0 release.

@xabbuh

xabbuh May 18, 2017

Member

The ClassLoader component won't have a 4.0 release.

This comment has been minimized.

@stof

stof May 18, 2017

Member

yeah, but the requirement will be dropped entirely when removing deprecated code anyway (only the BC layer requires it), so it is fine for now

@stof

stof May 18, 2017

Member

yeah, but the requirement will be dropped entirely when removing deprecated code anyway (only the BC layer requires it), so it is fine for now

"symfony/translation": "~2.8|~3.0|~4.0.0",
"symfony/var-dumper": "~3.3|~4.0.0",
"symfony/browser-kit": "~3.4|~4.0",
"symfony/class-loader": "~3.4|~4.0",

This comment has been minimized.

@xabbuh

xabbuh May 18, 2017

Member

The ClassLoader component won't have a 4.0 release.

@xabbuh

xabbuh May 18, 2017

Member

The ClassLoader component won't have a 4.0 release.

This comment has been minimized.

@nicolas-grekas

nicolas-grekas May 18, 2017

Member

let's do that in the next PR removing class loader, here it's a batch change

@nicolas-grekas

nicolas-grekas May 18, 2017

Member

let's do that in the next PR removing class loader, here it's a batch change

This comment has been minimized.

@xabbuh

xabbuh May 18, 2017

Member

fair enough

@xabbuh

xabbuh May 18, 2017

Member

fair enough

Show outdated Hide outdated src/Symfony/Component/HttpKernel/composer.json
},
"suggest": {
"symfony/browser-kit": "",
"symfony/class-loader": "",

This comment has been minimized.

@xabbuh

xabbuh May 18, 2017

Member

should be removed

@xabbuh

xabbuh May 18, 2017

Member

should be removed

This comment has been minimized.

@nicolas-grekas

nicolas-grekas May 18, 2017

Member

removed

@nicolas-grekas
@xabbuh

xabbuh approved these changes May 18, 2017

@stof

stof approved these changes May 18, 2017

@nicolas-grekas

This comment has been minimized.

Show comment
Hide comment
@nicolas-grekas

nicolas-grekas May 18, 2017

Member

Thank you @fabpot.

Member

nicolas-grekas commented May 18, 2017

Thank you @fabpot.

@nicolas-grekas

This comment has been minimized.

Show comment
Hide comment
@nicolas-grekas
Member

nicolas-grekas commented May 18, 2017

;)

@nicolas-grekas nicolas-grekas merged commit 4758c2c into symfony:master May 18, 2017

2 of 3 checks passed

continuous-integration/appveyor/pr Waiting for AppVeyor build to complete
Details
continuous-integration/travis-ci/pr The Travis CI build passed
Details
fabbot.io Your code looks good.
Details

nicolas-grekas added a commit that referenced this pull request May 18, 2017

feature #22733 Bump minimum version to PHP 7.1 for Symfony 4 (fabpot,…
… dunglas, nicolas-grekas)

This PR was merged into the 4.0-dev branch.

Discussion
----------

Bump minimum version to PHP 7.1 for Symfony 4

| Q             | A
| ------------- | ---
| Branch?       | master
| Bug fix?      | no
| New feature?  | yes-ish?
| BC breaks?    | yes-ish?
| Deprecations? | no
| Tests pass?   | yes
| Fixed tickets | n/a
| License       | MIT
| Doc PR        | n/a

Commits
-------

4758c2c Tweak travis and appveyor for Symfony 4
6633c8b Allow individual bridges, bundles and components to be used with 4.0
c850733 bumped minimum version to PHP 7.1
@mofarrell

This comment has been minimized.

Show comment
Hide comment
@mofarrell

mofarrell May 18, 2017

Is this just a version number issue? HHVM can change what version number it gives back. Are there some PHP7 features we haven't implemented yet that are making it burdensome for Symfony to support HHVM?

mofarrell commented May 18, 2017

Is this just a version number issue? HHVM can change what version number it gives back. Are there some PHP7 features we haven't implemented yet that are making it burdensome for Symfony to support HHVM?

@nicolas-grekas

This comment has been minimized.

Show comment
Hide comment
@nicolas-grekas

nicolas-grekas May 18, 2017

Member

That's not the only issue because even with the branches that support php5.5 thus hhvm, once you enable the php7 mode the test suite fails to just run, with strange type issues being reported.
It's quite easy to reproduce: just try running the ./phpunit script in this mode on e.g. 3.2.

Member

nicolas-grekas commented May 18, 2017

That's not the only issue because even with the branches that support php5.5 thus hhvm, once you enable the php7 mode the test suite fails to just run, with strange type issues being reported.
It's quite easy to reproduce: just try running the ./phpunit script in this mode on e.g. 3.2.

@mofarrell

This comment has been minimized.

Show comment
Hide comment
@mofarrell

mofarrell May 18, 2017

We have an suboption to PHP7 that can disable the strict type checks. The strict type checks are broken in some cases, and we have that on our radar. It happens to not be trivial to fix, and also currently not at the top of our priority list.
The option is hhvm.php7.scalar_types=0

mofarrell commented May 18, 2017

We have an suboption to PHP7 that can disable the strict type checks. The strict type checks are broken in some cases, and we have that on our radar. It happens to not be trivial to fix, and also currently not at the top of our priority list.
The option is hhvm.php7.scalar_types=0

@robfrawley

This comment has been minimized.

Show comment
Hide comment
@robfrawley

robfrawley May 20, 2017

Contributor

@fabpot Was this intentional or should this have been set to 4? This breaks some libraries ability to version detect (using their current mechanisms) and support spanning releases from 2.3 to 4.x.

@fabpot Was this intentional or should this have been set to 4? This breaks some libraries ability to version detect (using their current mechanisms) and support spanning releases from 2.3 to 4.x.

This comment has been minimized.

Show comment
Hide comment
@nicolas-grekas

nicolas-grekas May 20, 2017

Member

That's already fixed, isn't it?

Member

nicolas-grekas replied May 20, 2017

That's already fixed, isn't it?

This comment has been minimized.

Show comment
Hide comment
Contributor

robfrawley replied May 20, 2017

This comment has been minimized.

Show comment
Hide comment
@fabpot

fabpot May 21, 2017

Member

fixed now

Member

fabpot replied May 21, 2017

fixed now

nicolas-grekas added a commit that referenced this pull request May 22, 2017

feature #22820 Remove PHP < 7.1.3 code (ogizanagi)
This PR was squashed before being merged into the 4.0-dev branch (closes #22820).

Discussion
----------

Remove PHP < 7.1.3 code

| Q             | A
| ------------- | ---
| Branch?       | master
| Bug fix?      | no
| New feature?  | no
| BC breaks?    | yes
| Deprecations? | no <!-- don't forget updating UPGRADE-*.md files -->
| Tests pass?   | yes
| Fixed tickets | #22733
| License       | MIT
| Doc PR        | N/A

Commits
-------

7091fb4 Remove PHP < 7.1.3 code
@SenseException

This comment has been minimized.

Show comment
Hide comment
@SenseException

SenseException May 22, 2017

Contributor

Will Symfony 4 use scalar type hints and return types? This would be a break to the 3.x versions, but with a major release the best time to introduce them.

Contributor

SenseException commented May 22, 2017

Will Symfony 4 use scalar type hints and return types? This would be a break to the 3.x versions, but with a major release the best time to introduce them.

@stof

This comment has been minimized.

Show comment
Hide comment
@stof

stof May 22, 2017

Member

@SenseException we will use them in new APIs. But we won't add them in existing interfaces, as this would be a BC break without a progressive upgrade path, and so the drawbacks are much bigger than the benefits for the community.

Btw, the master branch already contains a scalar typehint in at least one place (the last argument in

public function registerListener($key, $logoutPath, $csrfTokenId, $csrfParameter, CsrfTokenManagerInterface $csrfTokenManager = null, string $context = null)
)

Member

stof commented May 22, 2017

@SenseException we will use them in new APIs. But we won't add them in existing interfaces, as this would be a BC break without a progressive upgrade path, and so the drawbacks are much bigger than the benefits for the community.

Btw, the master branch already contains a scalar typehint in at least one place (the last argument in

public function registerListener($key, $logoutPath, $csrfTokenId, $csrfParameter, CsrfTokenManagerInterface $csrfTokenManager = null, string $context = null)
)

@SenseException

This comment has been minimized.

Show comment
Hide comment
@SenseException

SenseException May 22, 2017

Contributor

@stof I'm aware that this would be a bold move, but your argument also fits to a future Symfony 5, 6, 7 and so on. Implementing an old Symfony 4 interface forces a user to omit type hints even when it is a new project that never was on version 3 before.

But it seems that a return type can be added to the class implementing an interface that misses that type: https://3v4l.org/BHlVW.

Contributor

SenseException commented May 22, 2017

@stof I'm aware that this would be a bold move, but your argument also fits to a future Symfony 5, 6, 7 and so on. Implementing an old Symfony 4 interface forces a user to omit type hints even when it is a new project that never was on version 3 before.

But it seems that a return type can be added to the class implementing an interface that misses that type: https://3v4l.org/BHlVW.

@sstok

This comment has been minimized.

Show comment
Hide comment
@sstok

sstok May 28, 2017

Contributor

@SenseException yes you can add return types to implementations, even when the interface doesn't require them. But doing this would be something for Symfony 5 so developers can first upgrade to Symfony 4, add the return-types, and then when Symfony 5 is released they can safely upgrade.

Contributor

sstok commented May 28, 2017

@SenseException yes you can add return types to implementations, even when the interface doesn't require them. But doing this would be something for Symfony 5 so developers can first upgrade to Symfony 4, add the return-types, and then when Symfony 5 is released they can safely upgrade.

@SenseException

This comment has been minimized.

Show comment
Hide comment
@SenseException

SenseException May 29, 2017

Contributor

So Symfony 5 is going to have the type hints and return types? I just want to read when Symfony and its components arr going to use modern (2017) PHP.

Contributor

SenseException commented May 29, 2017

So Symfony 5 is going to have the type hints and return types? I just want to read when Symfony and its components arr going to use modern (2017) PHP.

@dunglas

This comment has been minimized.

Show comment
Hide comment
@dunglas

dunglas May 29, 2017

Member

We'll use type hints and return types for the new code. It's not possible without a BC break for the old one (and it has very little interest because, as pointed out by other people, you can use type hints in your code and our code base is well tested).

Member

dunglas commented May 29, 2017

We'll use type hints and return types for the new code. It's not possible without a BC break for the old one (and it has very little interest because, as pointed out by other people, you can use type hints in your code and our code base is well tested).

@javiereguiluz

This comment has been minimized.

Show comment
Hide comment
@javiereguiluz

javiereguiluz May 29, 2017

Member

@SenseException in addition to what Kévin told you, we can only use PHP 7 features for new code added to Symfony. For the existing code, we can't use PHP 7 until November 2021 (as explained in this comment: #22862 (comment))

Member

javiereguiluz commented May 29, 2017

@SenseException in addition to what Kévin told you, we can only use PHP 7 features for new code added to Symfony. For the existing code, we can't use PHP 7 until November 2021 (as explained in this comment: #22862 (comment))

@SenseException

This comment has been minimized.

Show comment
Hide comment
@SenseException

SenseException Jun 8, 2017

Contributor

@javiereguiluz Thank you for pointing me to the comment and the answer to my question.

Contributor

SenseException commented Jun 8, 2017

@javiereguiluz Thank you for pointing me to the comment and the answer to my question.

@fabpot fabpot referenced this pull request Oct 19, 2017

Merged

Release v4.0.0-BETA1 #24612

@@ -63,7 +63,7 @@
const VERSION = '4.0.0-DEV';
const VERSION_ID = 40000;
const MAJOR_VERSION = 4;
const MAJOR_VERSION = 0;

This comment has been minimized.

@Aliance

Aliance Oct 19, 2017

Contributor

Why did you change this?

@Aliance

Aliance Oct 19, 2017

Contributor

Why did you change this?

This comment has been minimized.

@sstok

sstok Oct 19, 2017

Contributor

That seems like a bug in the release script 😛

@sstok

sstok Oct 19, 2017

Contributor

That seems like a bug in the release script 😛

This comment has been minimized.

@ogizanagi

ogizanagi Oct 19, 2017

Member

It was already fixed in ce519b6

@ogizanagi

ogizanagi Oct 19, 2017

Member

It was already fixed in ce519b6

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment