To Report a Bug
Due to excessive spam, ticket creation has been restricted. Once granted access you'll be able to file a new ticket here. Assistance—if required—is available in #i2p-dev on Irc2P, OFTC, or Freenode. Please enter as much information as you can when filing a new bug, including version information and relevant logs from http://127.0.0.1:7657/logs.jsp in your router console.
The Standard Trac Tickets Page
Special Tickets
- good-first-ticket (0): tickets that are a manageable size for a new contributor
- easy (6): tickets that represent some low-hanging (coding) fruit
- new (229): tickets that need to be triaged
- review-needed (2): tickets with a patch that wants to be reviewed (see PatchReviewProcess).
- reviewed (0): tickets with a patch reviewed and waiting to be committed
- news-needed (0): tickets for which a news entry is needed
- proof-needed (2): tickets that need someone to try recreating the issue, usually because there isn't enough information to identify a problem
- regression (0): regressions relative to a previous release, or previous state of the development infrastructure
- test-needed (0): tickets with a patch, but lacking sufficient tests
- unfinished-business (1): unfinished business from a previous change (but not strictly a regression)
- all open tickets, most recent first (586) or most recently changed first
- all closed tickets, most recently changed first (1860)
- open tickets owned by you (if logged in)
- research (0): things that might be good topics for a Master's Thesis or even a PhD Thesis, or at least a part of one
Keywords
Each keyword links to all of the open tickets mentioning that keyword. If you find existing tickets that are missing keywords, please feel free to add them.
- new-user (0): issues that affect users who are new to I2P
- websec (0): interaction between I2P's security model and the routerconsole
- iputil (0): having to do with automatically detecting the router's own IP address
- privacy (12): could lead to the unintended disclosure of information
- anonymity (5): relevant to the direct anonymity properties of I2P (should usually also be tagged with 'privacy')
- security (6): security issues not necessarily tagged with a more specific keyword (confidentiality, integrity, etc.)
- reliability (10): could lead to unpredictable failure of functionality
- anti-censorship (5): could help with resistance to censorship or denial of service
- scalability (4): scaling to large and/or geographically dispersed routers, or to high traffic volumes or numbers of clients
- peer-selection (5): related to the choice of tunnel peers according to topographical, geographical, bandwidth, etc. constraints
- forward-compatibility (0): relevant to forward compatibility of network protocols with future I2P versions
- transparency (2): features that help the user see and understand the inner workings, such as visualization, statistics, explorability
- unicode (0): related to Unicode
- i18n (0): related to internationalization (usually also to Unicode)
- usability (27): concerned with ease of use (interface or mental models)
- error (9): concerned with error reporting to end-users
- install (4): installation problems (not always with the installer)
- docs (16): fixing this issue involves updating documentation
- test (4): additional or better test coverage needed
- performance (22): an opportunity to improve some aspect of performance (speed, latency, bandwidth, space usage, etc.)
- memory (1): an opportunity to improve memory usage (should usually also be tagged with 'performance')
- extensibility (2): extensibility and customization mechanisms
- race (0): related to race conditions between different threads
- hang (7): could cause an operation to hang, either indefinitely or for long periods
- firewall (4): firewall and NAT traversal issues
- standards (4): compliance to standards (HTTP, HTML etc.)
- heisenbug (3): bugs that are not easily reproducible so far
- cleanup (6): code clean-up / refactoring
- time (5): having to do with time and clocks
- defaults (1): having to do with the default settings for configuration parameters
- no keywords (314): open tickets with no keywords
Platform keywords
- unix (2): all Unices
- debian (4): Debian Linux
- ubuntu (2): Ubuntu Linux
- gentoo (0): Gentoo Linux
- centos (0): CentOS Linux
- archlinux (0): Arch Linux
- nixos (0): NixOS Linux
- windows (12): Windows (native or not compiler-specific)
- win64 (1): Windows 64-bit
- cygwin (0): Windows using cygwin
- mac (2): Mac OS X
- bsd (1): all BSDs
- x86 (1): x86 processors
- x86-64 (1): x86-64 processors
- ppc (0): PowerPC processors
- arm (6): ARM processors
Functionality
- reseed (2): related to reseed code (as opposed to reseed infrastructure)
- shared-client (0): related to shared client tunnels
- participation (2): related to participating tunnels
- ntcp (8): related to NTCP
- ssu (6): related to SSU
- logging (7): related to logging
- statistics (0): related to rate stats and graphs
Plugins
Android apps
- I2P Android (35)
- Bote (0)
Development infrastructure
- mtn (1): Monotone revision control system
- trac (1): Trac bug tracker and wiki
- coverage (0): test coverage analyzer
- jenkins (0): automated builds by Jenkins
- irc (1): IRC bots for
#i2p-devchannel - build (6): related to the build scripts
- release (3): related to the release process
- metrics (2): Metrics collection
Tickets by Component
Last modified 2 years ago
Last modified on Mar 3, 2018 3:46:43 PM
