Skip to content

Conversation

@levon80999
Copy link
Contributor

@levon80999 levon80999 commented Sep 8, 2022

@levon80999 levon80999 changed the title PHPC-2101: Default Binary constructor parameter to TYPE_GENERIC !DRAFT! PHPC-2101: Default Binary constructor parameter to TYPE_GENERIC Sep 8, 2022
@levon80999 levon80999 changed the title !DRAFT! PHPC-2101: Default Binary constructor parameter to TYPE_GENERIC PHPC-2101: Default Binary constructor parameter to TYPE_GENERIC Sep 8, 2022
@levon80999 levon80999 requested a review from jmikola September 8, 2022 16:46
Copy link
Member

@jmikola jmikola left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please check the CI failures for this PR. There looks to be another test that requires changes.

In the future, please make a point to come back to PRs on your own and check for failures. Anything that isn't already being tracked in JIRA (e.g. failing-on-waterfall label) should either be fixed or result in a new ticket (if the failure is truly unrelated to the PR).

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This include is not necessary and can be removed. It was only included in bson-binary-001.phpt for some helper functions used within the test (e.g. fromPHP()).

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done

@levon80999
Copy link
Contributor Author

Seems I accidentally closed this PR when tried to solve conflict in phpstorm editor. new PR link is this #1362

@jmikola
Copy link
Member

jmikola commented Sep 13, 2022

Seems I accidentally closed this PR when tried to solve conflict in phpstorm editor.

In the future, you should just be able to re-open the pull request. If you don't have perms to do so, please reach out to @tom-selander.

@alcaeus
Copy link
Member

alcaeus commented Sep 13, 2022

@jmikola that's usually possible, but when force-pushing to a branch that's part of a closed pull request GotHub prevents one from re-opening said PR. I suspect that's what happened here.

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants