Custom Query (24322 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (22 - 24 of 24322)

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18
Ticket Resolution Summary Owner Reporter
#23 Fixed Contact Info in directory entry is not compulsory nickm weasel
Description

[Moved from bugzilla] Reporter: colin@… (Colin Tuckley)

Description: Opened: 2004-01-16 22:17

The Directory server accepts node entries without a contact entry. This is a bad idea. The contact info should be compulsory, and possibly should be verified somehow? At least a syntax check for a valid email address and a domain lookup maybe.


For 0.0.7, the entry will become required, and will need to be a valid email address.


As of 0.0.7, this is compulsory for all servers running 0.0.7. Clients will not reject servers without contact information until 0.0.8 or later.

[Automatically added by flyspray2trac: Operating System: All]

#24 Fixed Tight loop in async code nickm weasel
Description

[Moved from bugzilla] Reporter: nickm@… (Nick Mathewson)

Description: Opened: 2004-01-22 06:12

There's a tight loop somewhere in the new networking code. I'm noting this here so I don't forget to fix it.

The symptom is high CPU use, and an strace that shows many successive calls to poll(2) or select(2), with no change in arguments. One possible cause is that some TLS connection thinks it wants to read/write, but that it doesn't do anything to clear the read/write state. Another possible cause is that we're getting an event other than POLLIN|POLLOUT, and not doing anything with it.

As a first step, I should add log messages accounting for all opened/closed sockets, by fd, so that the next time this happens, I can link suffering fds to suffering connections. To make sure nothing stupid is the cause, I should also

(I'd fix this now, but I -need- to finish writing e2e-traffic.)


Fixed last week: we were getting POLLERR, but never handling it.

[Automatically added by flyspray2trac: Operating System: All]

#25 Fixed Log files in UTC nickm weasel
Description

[Moved from bugzilla] Reporter: bfordham@… (Bryan L. Fordham) Description: Opened: 2004-01-23 01:38

Should we show logs in UTC format?

something like: Jan 23 00:37:53.447 UTC [DEBUG] Connection closed


Fixed in 0.0.7 cvs.

Instead of logging everything in UTC, I've kept the logs in local time, but added an indication of time zone. The new format is:

"Jan 27 00:16:57.882 -0500"

[Automatically added by flyspray2trac: Operating System: Windows]

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18
Note: See TracQuery for help on using queries.