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

New release for providing Symfony 4 support #757

Open
adiq opened this issue Jan 24, 2018 · 31 comments

Comments

@adiq
Copy link

commented Jan 24, 2018

It would be great to release new version of Mink to provide Symfony 4 support.

@pamil

This comment has been minimized.

Copy link

commented Feb 14, 2018

Is there anything that needs to be done to tag a new release?

@adiq

This comment has been minimized.

Copy link
Author

commented Feb 14, 2018

I think there is nothing to do, as 808702d fixes the dependencies problem. I'll try to test it on real project and will let you know.

@stof

This comment has been minimized.

Copy link
Member

commented Feb 14, 2018

Well, before making new releases for Mink packages, I would like to make CI green for the different drivers (IIRC, the Selenium2Driver CI has issues currently)

@kochen

This comment has been minimized.

Copy link

commented Apr 21, 2018

@adiq did you manage to get Sessions to work?

I'm getting:

Specify session name to get

See: Behat/MinkExtension#321

and is $sessions (https://github.com/minkphp/Mink/blob/master/src/Mink.php#L36) is actually empty... :/

@bartonhammond

This comment has been minimized.

Copy link

commented May 8, 2018

I'm getting same error Specify session name to get (InvalidArgumentException) . Any update?

@adiq

This comment has been minimized.

Copy link
Author

commented May 8, 2018

I will look into this when I will have some spare time. Did you try to revert mentioned commit and see if the issue persists?

@bartonhammond

This comment has been minimized.

Copy link

commented May 8, 2018

I got past that error by adding the line below

default:
  suites:
    default:
      paths: ["%paths.base%/features/temp/home.feature"]
      local_screenshots: false      
      contexts: [ThinkWellContext]

  extensions:
    Behat\MinkExtension:
      browser_name: 'chrome'
      base_url: https://twlw.wpengine.com      
      default_session: cross_browser_testing  #### Added this line
      cross_browser_testing:
@DonCallisto

This comment has been minimized.

Copy link

commented May 25, 2018

Isn't the CI green? I can't see any error.

@aik099

This comment has been minimized.

Copy link
Member

commented May 25, 2018

@DonCallisto , in the #757 (comment) @stof meant driver repos. Almost all of them are red currently.

@DonCallisto

This comment has been minimized.

Copy link

commented May 25, 2018

Got it, so we should try to fix them IIUC

@tristanbes

This comment has been minimized.

Copy link

commented Jun 29, 2018

Any release planned yet ? It hurts me to require a package as dev-master

@aik099

This comment has been minimized.

Copy link
Member

commented Jun 29, 2018

Nothing has changed since #757 (comment). I could really use some help on getting those driver tests green again.

@kochen

This comment has been minimized.

Copy link

commented Oct 18, 2018

I got past that error by adding the line below

default:
  suites:
    default:
      paths: ["%paths.base%/features/temp/home.feature"]
      local_screenshots: false      
      contexts: [ThinkWellContext]

  extensions:
    Behat\MinkExtension:
      browser_name: 'chrome'
      base_url: https://twlw.wpengine.com      
      default_session: cross_browser_testing  #### Added this line
      cross_browser_testing:

That line doesn't seem to do the trick.
I've created a repo that demonstrates the issue: https://github.com/kochen/behat-mink-session (with travis-ci).

@juliendufresne

This comment has been minimized.

Copy link

commented Dec 23, 2018

This is blocking every projects using symfony/flex with the composer extra config symfony.require: "4.2.*"

@juliendufresne

This comment has been minimized.

Copy link

commented Dec 23, 2018

According to what @stof stated here #757 (comment), this requires the following issues to be fixed:

@Einenlum

This comment has been minimized.

Copy link

commented May 14, 2019

Not sure I get why it needs to wait for issues in selenium driver and zombie driver to be fixed…
I think a lot of people now use Mink with the chrome headless driver.

Also, I think that making mink not installable on sf4 is quite like dooming Mink (and so Behat) for the Symfony community :/

@BigZ

This comment has been minimized.

Copy link

commented Jun 7, 2019

definitely. drivers are suggestions, not dependencies. nothing ties the drivers and the release together as i see it. It really is bad for both mink, behat and symfony that sf4 and mink aren't compatible.
Software going to production cannot possibly set minimum stability to something else than stable

@pamil

This comment has been minimized.

Copy link

commented Jun 7, 2019

@BigZ I agree with the meaning of your comment though Mink should be a development dependency so there's no effect on production environment whatsoever.

@phoefnagel

This comment has been minimized.

Copy link

commented Jun 18, 2019

Dear friends,

We are encountering this error when using Symfony 4.3 when using the flex configuration "4.3.*". Similar to what julien described above.

  • behat/mink v1.7.1 requires symfony/css-selector ~2.1|~3.0 -> no matching package found.
  • behat/mink v1.7.0 requires symfony/css-selector ~2.1 -> no matching package found.
  • Installation request for behat/mink ^1.7 -> satisfiable by behat/mink[v1.7.0, v1.7.1].

Could this be picked up as part of this ticket? Thanks!

@grudda

This comment has been minimized.

Copy link

commented Aug 19, 2019

Is there any progress expected soon? Those incompatibilities are really blocking ci pipelines, if you rely on those tests before deploying to prod!

@BigZ

This comment has been minimized.

Copy link

commented Aug 27, 2019

i'm using my own fork on the meantime, but it's quite alarming to see no answer from the maintainers. Any input @stof @everzet @aik099 ?

@DonCallisto

This comment has been minimized.

Copy link

commented Aug 27, 2019

@BigZ as you can easily see by yourself, @stof is the only one that's quite still active in open source.
My guess is, as I already saw Stof taking a step back from some projects he was following (like Prophecy for instance), he's focusing only on some kind of projects (maybe the ones with more download, more active contributors overall, more ... whatever; it's only a guess).
The only alarming thing is that if current owners can't follow anymore their projects - that's quite an understendable matter from my standpoint - should try to find someone else who can take the projects back to life.
But, maybe, I'm missing the bigger picture so is just a speculation of mine.

@kochen

This comment has been minimized.

Copy link

commented Aug 27, 2019

@BigZ @adiq @aik099 are you all directly requiring behat/mink: "1.7" in your projects?

@aik099

This comment has been minimized.

Copy link
Member

commented Aug 28, 2019

@DonCallisto , @kochen , @BigZ : As a maintainer I review PRs, but IMO for PR to be merged it needs to be reviewed by 2 maintainers at least.

If I'm not mistaken, then:

  • Selenium2 driver - has PR to make tests green (in review), that also changes min PHP version to 7.x for that driver
  • Zombie driver - build is failing

Other non-deprecated drivers have successful builds.

@kochen

This comment has been minimized.

Copy link

commented Aug 28, 2019

@aik099 my question was more related to the actual usage and to better understand the requiement for this version bump (cause in the general sense it works with Symfony 4 just fine).

The interesting question to you would be:
are there 2 active maintainers in this project?

@DonCallisto

This comment has been minimized.

Copy link

commented Aug 28, 2019

As a maintainer I review PRs, but IMO for PR to be merged it needs to be reviewed by 2 maintainers at least.

I totally agree with this but if no other mantainers are active, that basically means that the project is already died.

Moreover I agree with this comment #757 (comment) but I'm still not sure to have the complete picture so I can possibly miss something.

@grudda

This comment has been minimized.

Copy link

commented Aug 28, 2019

So what does this discussion basically mean. Shall we move away from behat tests in symfony context, because there is no one who like to maintain this project? Or do I oversee other options to make behat tests run? Any opinions?

@aik099

This comment has been minimized.

Copy link
Member

commented Aug 28, 2019

Actually we can make all people happy here.

Instead of using approach, where driver releases must be in sync with Mink releases itself (suggested in #757 (comment)) we can use different approach: drivers and Mink itself are released independently as long as no BC breaks in driver API happen.

If that sounds good enough we need to:

  1. inspect all commits made since last release to create change log and look for BC breaks
  2. depending on BC break presence we decide to make new release as 1.7.2 (no BC breaks) or 2.0.0 (has BC breaks)

P.S.
That would make people in this discussion happy even with 1 semi-active maintainer.

@kochen

This comment has been minimized.

Copy link

commented Aug 28, 2019

@aik099 or we tag it has 2.0.0 even without BC breaks and we sail to a fresh (re)start.

@stof

This comment has been minimized.

Copy link
Member

commented Aug 29, 2019

if we have no BC breaks, we should not tag it as 2.0. That would make it painful for users, as any library depending on Mink would have to be updated first to allow the new major version, without any need for a major version.

@BigZ

This comment has been minimized.

Copy link

commented Sep 11, 2019

@BigZ @adiq @aik099 are you all directly requiring behat/mink: "1.7" in your projects?

i use dev-master

we can use different approach: drivers and Mink itself are released independently as long as no BC breaks in driver API happen

yes please. it's in the composer "suggest section" and mink is not tied to a specific version of them.

if we have no BC breaks, we should not tag it as 2.0. That would make it painful for users, as any library depending on Mink would have to be updated first to allow the new major version, without any need for a major version.

Definitely. but we have what looks like a BC break there v1.7.1...masterdiff-b5d0ee8c97c7abd7e3fa29b9a27d1780R19

It's the only one i found, tho. and it might be easy to fix.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
You can’t perform that action at this time.