Fix: debug.logging not work in retry provider #1098
Merged
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.
When using
RetryProvider
, we want to identify the specificProvider
being used (according to #1094 requirements).According to the source code, I noticed that
g4f.logging
is likely intended for this purpose, facilitating better debugging for developers (please correct me if I'm wrong).However, the
logging
attribute inretry_provider.py
does not change along withg4f.logging = True
. (always beFalse
)gpt4free/g4f/Provider/retry_provider.py
Lines 43 to 44 in cb3677a
Therefore, in this case, I have defined
logging
as a class variable inRetryProvider
.Example
Results
Noted: I'm not sure if this modification is the optimal solution. If there is a better way, I welcome assistance.