POST et. all timeout ceilings need to be quadrupled

Open
#336 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
35/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
ruby
Domain
cli, networking

Research direction

Start at the t update command path and locate the timeout ceilings applied to POST requests. Compare the current values and update each relevant ceiling to four times its present value. Verify that the update path completes over a slow or unstable connection, such as the Tor scenario described in the issue.

Written by the indexing model from the issue text.

Description

feature

Some people tether or use saturated wifi channels that yield unstable internet connections.

Only way off the top of my head I could reproduce (via Tor):

vxbinaca@lappy/~$ torsocks t update "eating lunch"
/usr/local/bin/t: execution expired
Dominant language
Ruby
Stars
5.6k
Forks
402
Avg merge
13h 50m
Merged PRs (30d)
5

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from sferik/x-cli

All issues in sferik/x-cli

Similar issues

More Ruby issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.