Skip to content

Conversation

@jrfnl
Copy link
Member

@jrfnl jrfnl commented Jun 18, 2021

Note: this is a recreation of PR #110, which was closed due to the branch rename and the remote no longer existing.
Please see PR #110 for the original discussion on the PR.

Currently it consumes a lot of CPU, it's a no-brainer i think.

/cc @diegode

@jrfnl
Copy link
Member Author

jrfnl commented Aug 13, 2021

@diegode Hiya!

We're currently planning two triage sessions for Requests 2.0 and would like to invite you to join us in one or both of these sessions to talk us through the PR and discuss it.

The triage sessions are currently planned for:

  • Friday August 20, 07:00 - 11:00 UTC
  • Friday September 3, 07:00 - 11:00 UTC

Would you be available to join us during those times on one of those days ?

@jrfnl
Copy link
Member Author

jrfnl commented Aug 13, 2021

Possible duplicate of #284 to fix #283

Currently it consumes a lot of CPU, it's a no-brainer i think.

Co-authored-by: Diego de Estrada
@jrfnl jrfnl force-pushed the feature/110-curl_multi-select branch from 0d89faa to 13f15af Compare October 4, 2021 23:02
@schlessera schlessera added this to the 2.1.0 milestone Nov 5, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants