Opened 8 years ago
Closed 7 years ago
#902 closed defect (fixed)
Describe "Rejecting Tunnels" better
| Reported by: | DISABLED | Owned by: | |
|---|---|---|---|
| Priority: | minor | Milestone: | 0.9.8 |
| Component: | apps/console | Version: | 0.9.4 |
| Keywords: | Cc: | ||
| Parent Tickets: | Sensitive: | no |
Description
If we are rejecting tunnels, tell the user why for each case. "Rejecting tunnels" in itself can be extremely vague & confusing.
Subtickets
Change History (3)
comment:1 Changed 8 years ago by
| Component: | unspecified → apps/console |
|---|---|
| Milestone: | 0.9.5 → 0.9.6 |
comment:2 Changed 7 years ago by
| Milestone: | 0.9.6 → 0.9.8 |
|---|
or have an intelligent default at 20 minutes - set based on maxParticpatingTunnels and bandwidth class. Yeah, let's do that.
comment:3 Changed 7 years ago by
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
Fixed in 0.9.7.1-22 2afd1422d5ea92a758ec5932edd23af31b58c4fe
Note: See
TracTickets for help on using
tickets.
We actually do have several different messages, after each rejection the message is replaced with the reason. There is a no-reason default 'rejecting tunnels' that's shown about 20 minutes after startup, replacing the 'rejecting tunnels - starting up' that's shown at startup. That should only last until the next request comes in. Perhaps the default replacement should be 'accepting tunnels', which is less scary.