Possible bug in nick_chars validation
Bug #258175 reported by
Toast
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| DSHub |
Confirmed
|
High
|
Pietry | ||
Bug Description
- [15:03:02] *** Connecting to x
- [15:03:02] *** Connected
- [15:03:02] <x> Running Iota Version of DSHub.
- [15:03:02] <x> Hub is up since Fri Aug 15 14:58:21 CEST 2008
- [15:03:02] <x> Nick not valid, please choose another
- [15:03:02] *** Connection closed
[08-08-
[08-08-
.* means anything
still ended up with the same result
[08-08-
[08-08-
changed back still the same
then tried to restart hub crashed ask spookie for more details of the crash cause it didn't get back online
seems to have dropped reglist after crash
| description: | updated |
Revision history for this message
| Toast (swetoast-deactivatedaccount) wrote | #1 |
Revision history for this message
| Toast (swetoast-deactivatedaccount) wrote | #2 |
| Changed in dshub: | |
| importance: | Undecided → High |
| status: | New → Confirmed |
| Changed in dshub: | |
| assignee: | nobody → pietry |
To post a comment you must log in.
updated to a certain regexp that i know works tested and everything
([\w\W]+)*
[17:02:43] *** Connecting to x...
[17:02:43] *** Connected
[17:02:44] <x> Running Iota Version of DSHub.
[17:02:44] <x> Hub is up since Fri Aug 15 17:00:56 CEST 2008
[17:02:44] <x> Nick not valid, please choose another
used nick: mupp
and the hub refused to let that nick in even thou the regexp matched and everthing was okey so im taking the liberty to updating the status of this to confirmed