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

Adds dynamic Settings for session connection timeout #85

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

pengchengyin
Copy link

Adds dynamic Settings for whether sessions are reused or not

Many thanks for your contribution, we truly appreciate it. We will appreciate it even more, if you make sure that you can say "YES" to each point in this short checklist:

  • You made a small amount of changes (less than 100 lines, less than 10 files)
  • You made changes related to only one bug (create separate PRs for separate problems)
  • You are ready to defend your changes (there will be a code review)
  • You don't touch what you don't understand
  • You ran the build locally and it passed

This article will help you understand what we are looking for: http:https://www.yegor256.com/2015/02/09/serious-code-reviewer.html

Thank you for your contribution!

Adds dynamic Settings for whether sessions are reused or not
@0crat
Copy link

0crat commented Jul 15, 2019

@yegor256/z please, pay attention to this pull request

@0crat 0crat added the scope label Jul 15, 2019
@0crat
Copy link

0crat commented Jul 15, 2019

Job #85 is now in scope, role is REV

@0crat
Copy link

0crat commented Jul 15, 2019

@yegor256/z everybody who has role REV is banned at #85; I won't be able to assign anyone automatically; consider assigning someone manually (as in §19), or invite more people (as in §51), or remove the job from the scope (as in §14)

@0crat
Copy link

0crat commented Jul 20, 2019

@yegor256/z everybody who has role REV is banned at #85; I won't be able to assign anyone automatically; consider assigning someone manually (as in §19), or invite more people (as in §51), or remove the job from the scope (as in §14)

@0crat
Copy link

0crat commented Jul 25, 2019

@yegor256/z everybody who has role REV is banned at #85; I won't be able to assign anyone automatically; consider assigning someone manually (as in §19), or invite more people (as in §51), or remove the job from the scope (as in §14)

@0crat
Copy link

0crat commented Jul 30, 2019

@yegor256/z everybody who has role REV is banned at #85; I won't be able to assign anyone automatically; consider assigning someone manually (as in §19), or invite more people (as in §51), or remove the job from the scope (as in §14)

@0crat
Copy link

0crat commented Aug 4, 2019

@yegor256/z everybody who has role REV is banned at #85; I won't be able to assign anyone automatically; consider assigning someone manually (as in §19), or invite more people (as in §51), or remove the job from the scope (as in §14)

@0crat
Copy link

0crat commented Aug 14, 2019

@yegor256/z everybody who has role REV is banned at #85; I won't be able to assign anyone automatically; consider assigning someone manually (as in §19), or invite more people (as in §51), or remove the job from the scope (as in §14)

@0crat
Copy link

0crat commented Aug 19, 2019

@yegor256/z everybody who has role REV is banned at #85; I won't be able to assign anyone automatically; consider assigning someone manually (as in §19), or invite more people (as in §51), or remove the job from the scope (as in §14)

@0crat
Copy link

0crat commented Aug 24, 2019

@yegor256/z everybody who has role REV is banned at #85; I won't be able to assign anyone automatically; consider assigning someone manually (as in §19), or invite more people (as in §51), or remove the job from the scope (as in §14)

@0crat
Copy link

0crat commented Aug 29, 2019

@yegor256/z everybody who has role REV is banned at #85; I won't be able to assign anyone automatically; consider assigning someone manually (as in §19), or invite more people (as in §51), or remove the job from the scope (as in §14)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants