-
Notifications
You must be signed in to change notification settings - Fork 725
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
Add PROMPT_TOOLKIT_NO_CPR=1 environment variable to disable CPR requests (master) #898
Merged
jonathanslenders
merged 1 commit into
prompt-toolkit:master
from
asmeurer:no-cpr-env-var-master
May 14, 2019
Merged
Add PROMPT_TOOLKIT_NO_CPR=1 environment variable to disable CPR requests (master) #898
jonathanslenders
merged 1 commit into
prompt-toolkit:master
from
asmeurer:no-cpr-env-var-master
May 14, 2019
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
asmeurer
changed the title
Add PROMPT_TOOLKIT_NO_CPR=1 environment variable to disable CPR requests
Add PROMPT_TOOLKIT_NO_CPR=1 environment variable to disable CPR requests (master)
May 14, 2019
I assume it works on master too, I'll test later. The change looks obvious. |
Thanks! |
usingtechnology
added a commit
to usingtechnology/aries-cloudagent-python
that referenced
this pull request
May 26, 2023
Bug with prompt_toolkit and trace logging. Could only bump up the prompt_toolkit library so much since demos run on Python 3.6. However, I did attempt on 3.9 with the latest version of prompt_toolkit and setting an env var (see prompt-toolkit/python-prompt-toolkit#898). This still did not correct the issue, so reverted to existing code and just handled the exception(s). The output of the trace log is being written to the console, my limited understanding of this would be that the trace log works, but also triggers the prompt_toolkit to do the same work and gets into conflict. Signed-off-by: Jason Sherman <[email protected]>
Zzocker
pushed a commit
to trential/aries-cloudagent-python
that referenced
this pull request
Jul 4, 2023
Bug with prompt_toolkit and trace logging. Could only bump up the prompt_toolkit library so much since demos run on Python 3.6. However, I did attempt on 3.9 with the latest version of prompt_toolkit and setting an env var (see prompt-toolkit/python-prompt-toolkit#898). This still did not correct the issue, so reverted to existing code and just handled the exception(s). The output of the trace log is being written to the console, my limited understanding of this would be that the trace log works, but also triggers the prompt_toolkit to do the same work and gets into conflict. Signed-off-by: Jason Sherman <[email protected]>
Zzocker
pushed a commit
to trential/aries-cloudagent-python
that referenced
this pull request
Jul 4, 2023
Bug with prompt_toolkit and trace logging. Could only bump up the prompt_toolkit library so much since demos run on Python 3.6. However, I did attempt on 3.9 with the latest version of prompt_toolkit and setting an env var (see prompt-toolkit/python-prompt-toolkit#898). This still did not correct the issue, so reverted to existing code and just handled the exception(s). The output of the trace log is being written to the console, my limited understanding of this would be that the trace log works, but also triggers the prompt_toolkit to do the same work and gets into conflict. Signed-off-by: Jason Sherman <[email protected]>
mukulverm4
pushed a commit
to trential/aries-cloudagent-python
that referenced
this pull request
Jul 4, 2023
Bug with prompt_toolkit and trace logging. Could only bump up the prompt_toolkit library so much since demos run on Python 3.6. However, I did attempt on 3.9 with the latest version of prompt_toolkit and setting an env var (see prompt-toolkit/python-prompt-toolkit#898). This still did not correct the issue, so reverted to existing code and just handled the exception(s). The output of the trace log is being written to the console, my limited understanding of this would be that the trace log works, but also triggers the prompt_toolkit to do the same work and gets into conflict. Signed-off-by: Jason Sherman <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Same as #897 execpt against master.
I've tested #897 and can confirm it works, but I have not tested the master version (this branch).