Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

[Lock][Messenger] Fix precedence of DSN options for 5.1#37269

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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.

Already on GitHub?Sign in to your account

Merged
nicolas-grekas merged 1 commit intosymfony:5.1fromjderusse:fix-precedence-51
Jun 18, 2020

Conversation

@jderusse
Copy link
Member

@jderussejderusse commentedJun 13, 2020
edited by nicolas-grekas
Loading

QA
Branch?5.1
Bug fix?yes
New feature?no
Deprecations?no
Tickets#37218 (comment)
LicenseMIT
Doc PRN/A

This PR fix précédence of DSN options over constructor options in all component on branch 5.1

@nicolas-grekas
Copy link
Member

There are some failures to take care of.

@jderussejderusseforce-pushed thefix-precedence-51 branch 2 times, most recently fromb409d15 toc4942b8CompareJune 14, 2020 19:11
parse_str($parsedUrl['query'],$query);
}
$this->options['collection'] =$this->options['collection'] ??$query['collection'] ??null;
$this->options['collection'] =$query['collection'] ??$this->options['collection'] ??null;
Copy link

@kraloskralosJun 15, 2020
edited
Loading

Choose a reason for hiding this comment

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

Isn't this a BC Break? someone's application could start writing to the wrong collection if they are specifying both for some reason and they differ. Also there's the path in the uri which should take precedence over$options['database']

Choose a reason for hiding this comment

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

I would rather we deal withLock\Store\MongoDbStore in#37218

Choose a reason for hiding this comment

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

see#37218 (comment) about BC vs bugfix

Choose a reason for hiding this comment

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

there's the path in the uri which should take precedence over $options['database']

@jderusse can you have a look at this, also in the other PR?

Copy link
MemberAuthor

Choose a reason for hiding this comment

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

good catch. Also fix precedenceof credentials in that PR

Copy link
MemberAuthor

Choose a reason for hiding this comment

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

did not found precendence in#37268@nicolas-grekas . Did you have a specific thing in mind?

@nicolas-grekas
Copy link
Member

Thank you@jderusse.

@nicolas-grekasnicolas-grekas merged commitab24fb9 intosymfony:5.1Jun 18, 2020
@fabpotfabpot mentioned this pull requestJul 24, 2020
fabpot added a commit that referenced this pull requestJul 31, 2020
… (jderusse)This PR was merged into the 5.1 branch.Discussion----------[Messenger] Fix invalid option sslmode in AmazonSqs bridge| Q             | A| ------------- | ---| Branch?       | 5.1| Bug fix?      | yes| New feature?  | no| Deprecations? | no| Tickets       | />| License       | MIT| Doc PR        | /The sslmode option allows people to use AmazonSqs with non-offical endpoint like the [asyncaws/testing-sqs](https://hub.docker.com/r/asyncaws/testing-sqs) docker imageBy fixing precedence of DNS options in#37269 I introduced a bug that trigger an exception `Unknown option found: [sslmode]`. I apologize for thisThis PR adds `sslmode` in list of allowed optionsCommits-------afbd51b Fix invalid option sslmode
@jderussejderusse deleted the fix-precedence-51 branchOctober 15, 2020 10:01
Sign up for freeto join this conversation on GitHub. Already have an account?Sign in to comment

Reviewers

@nicolas-grekasnicolas-grekasnicolas-grekas approved these changes

@srozesrozeAwaiting requested review from sroze

+1 more reviewer

@kraloskraloskralos left review comments

Reviewers whose approvals may not affect merge requirements

Assignees

No one assigned

Projects

None yet

Milestone

5.1

Development

Successfully merging this pull request may close these issues.

4 participants

@jderusse@nicolas-grekas@kralos@carsonbot

[8]ページ先頭

©2009-2025 Movatter.jp