libtorrent todo-list

0 urgent 2 important 35 relevant 9 feasible 134 notes
relevance 3../src/piece_picker.cpp:155we need a different type to return to the outside here
relevance 3../src/kademlia/get_item.cpp:220we don't support CAS errors here! we need a custom observer
relevance 2../src/peer_connection.cpp:2989since we throw away the queue entry once we issue the disk job, this may happen. Instead, we should keep the queue entry around, mark it as having been requested from disk and once the disk job comes back, discard it if it has been cancelled. Maybe even be able to cancel disk jobs?
relevance 2../src/peer_connection.cpp:4575use a deadline_timer for timeouts. Don't rely on second_tick()! Hook this up to connect timeout as well. This would improve performance because of less work in second_tick(), and might let use remove ticking entirely eventually
relevance 2../src/piece_picker.cpp:1966make the 2048 limit configurable
relevance 2../src/piece_picker.cpp:2575the first_block returned here is the largest free range, not the first-fit range, which would be better
relevance 2../src/piece_picker.cpp:3360it would be nice if this could be folded into lock_piece() the main distinction is that this also maintains the m_num_passed counter and the passed_hash_check member Is there ever a case where we call write filed without also locking the piece? Perhaps write_failed() should imply locking it.
relevance 2../src/session_impl.cpp:216find a better place for this function
relevance 2../src/session_impl.cpp:1813the udp socket(s) should be using the same generic mechanism and not be restricted to a single one we should open a one listen socket for each entry in the listen_interfaces list
relevance 2../src/session_impl.cpp:1915use bind_to_device in udp_socket
relevance 2../src/session_impl.cpp:1941use bind_to_device in udp_socket
relevance 2../src/session_impl.cpp:3388make a list for torrents that want to be announced on the DHT so we don't have to loop over all torrents, just to find the ones that want to announce
relevance 2../src/torrent.cpp:719post alert
relevance 2../src/torrent.cpp:4729abort lookups this torrent has made via the session host resolver interface
relevance 2../src/torrent.cpp:4873the tracker login feature should probably be deprecated
relevance 2../src/torrent.cpp:7725if peer is a really good peer, maybe we shouldn't disconnect it
relevance 2../src/tracker_manager.cpp:196some of these arguments could probably be moved to the tracker request itself. like the ip_filter and settings
relevance 2../src/udp_tracker_connection.cpp:86support authentication here. tracker_req().auth
relevance 2../src/utp_stream.cpp:348it would be nice if not everything would have to be public here
relevance 2../src/web_peer_connection.cpp:628just make this peer not have the pieces associated with the file we just requested. Only when it doesn't have any of the file do the following
relevance 2../src/web_peer_connection.cpp:687create a mapping of file-index to redirection URLs. Use that to form URLs instead. Support to reconnect to a new server without destructing this peer_connection
relevance 2../src/kademlia/node.cpp:67make this configurable in dht_settings
relevance 2../src/kademlia/node.cpp:491it would be nice to have a bias towards node-id prefixes that are missing in the bucket
relevance 2../src/kademlia/node.cpp:581use the non deprecated function instead of this one
relevance 2../src/kademlia/node.cpp:909find_node should write directly to the response entry
relevance 2../src/kademlia/routing_table.cpp:110use the non deprecated function instead of this one
relevance 2../src/kademlia/routing_table.cpp:900move the lowest priority nodes to the replacement bucket
relevance 2../include/libtorrent/enum_net.hpp:137this could be done more efficiently by just looking up the interface with the given name, maybe even with if_nametoindex()
relevance 2../include/libtorrent/piece_picker.hpp:599having 8 priority levels is probably excessive. It should probably be changed to 3 levels + dont-download
relevance 2../include/libtorrent/proxy_base.hpp:257use the resolver interface that has a built-in cache
relevance 2../include/libtorrent/session.hpp:271the ip filter should probably be saved here too
relevance 2../include/libtorrent/session_settings.hpp:55this type is only used internally now. move it to an internal header and make this type properly deprecated.
relevance 2../include/libtorrent/socks5_stream.hpp:131add async_connect() that takes a hostname and port as well
relevance 2../include/libtorrent/tracker_manager.hpp:278this class probably doesn't need to have virtual functions.
relevance 2../include/libtorrent/aux_/session_interface.hpp:130the IP voting mechanism should be factored out to its own class, not part of the session
relevance 2../include/libtorrent/aux_/session_interface.hpp:155remove this. There's already get_resolver()
relevance 2../include/libtorrent/aux_/session_interface.hpp:210factor out the thread pool for socket jobs into a separate class used to (potentially) issue socket write calls onto multiple threads
relevance 1../src/disk_io_thread.cpp:233it would be nice to have the number of threads be set dynamically
relevance 1../src/http_seed_connection.cpp:124in chunked encoding mode, this assert won't hold. the chunk headers should be subtracted from the receive_buffer_size
relevance 1../src/session_impl.cpp:5210report the proper address of the router as the source IP of this understanding of our external address, instead of the empty address
relevance 1../src/session_impl.cpp:6412we only need to do this if our global IPv4 address has changed since the DHT (currently) only supports IPv4. Since restarting the DHT is kind of expensive, it would be nice to not do it unnecessarily
relevance 1../src/torrent.cpp:1157make this depend on the error and on the filesystem the files are being downloaded to. If the error is no_space_left_on_device and the filesystem doesn't support sparse files, only zero the priorities of the pieces that are at the tails of all files, leaving everything up to the highest written piece in each file
relevance 1../src/torrent.cpp:6877save the send_stats state instead of throwing them away it may pose an issue when downgrading though
relevance 1../src/torrent.cpp:7970should disconnect all peers that have the pieces we have not just seeds. It would be pretty expensive to check all pieces for all peers though
relevance 1../include/libtorrent/ip_voter.hpp:122instead, have one instance per possible subnet, global IPv4, global IPv6, loopback, 192.168.x.x, 10.x.x.x, etc.
relevance 1../include/libtorrent/web_peer_connection.hpp:122if we make this be a disk_buffer_holder instead we would save a copy sometimes use allocate_disk_receive_buffer and release_disk_receive_buffer
relevance 0../test/test_block_cache.cpp:475test try_evict_blocks
relevance 0../test/test_block_cache.cpp:476test evicting volatile pieces, to see them be removed
relevance 0../test/test_block_cache.cpp:477test evicting dirty pieces
relevance 0../test/test_block_cache.cpp:478test free_piece
relevance 0../test/test_block_cache.cpp:479test abort_dirty
relevance 0../test/test_block_cache.cpp:480test unaligned reads
relevance 0../test/test_dht.cpp:436test obfuscated_get_peers
relevance 0../test/test_metadata_extension.cpp:91it would be nice to test reversing which session is making the connection as well
relevance 0../test/test_peer_list.cpp:581test erasing peers
relevance 0../test/test_peer_list.cpp:582test logic for which connection to keep when receiving an incoming connection to the same peer as we just made an outgoing connection to
relevance 0../test/test_peer_list.cpp:584test update_peer_port with allow_multiple_connections_per_ip and without
relevance 0../test/test_peer_list.cpp:585test add i2p peers
relevance 0../test/test_peer_list.cpp:586test allow_i2p_mixed
relevance 0../test/test_peer_list.cpp:587test insert_peer failing with all error conditions
relevance 0../test/test_peer_list.cpp:588test IPv6
relevance 0../test/test_peer_list.cpp:589test connect_to_peer() failing
relevance 0../test/test_peer_list.cpp:590test connection_closed
relevance 0../test/test_primitives.cpp:213test the case where we have > 120 samples (and have the base delay actually be updated)
relevance 0../test/test_primitives.cpp:214test the case where a sample is lower than the history entry but not lower than the base
relevance 0../test/test_resume.cpp:340test all other resume flags here too. This would require returning more than just the torrent_status from test_resume_flags. Also http seeds and trackers for instance
relevance 0../test/test_rss.cpp:135verify some key state is saved in 'state'
relevance 0../test/test_ssl.cpp:377test using a signed certificate with the wrong info-hash in DN
relevance 0../test/test_ssl.cpp:475also test using a hash that refers to a valid torrent but that differs from the SNI hash
relevance 0../test/test_torrent.cpp:133wait for an alert rather than just waiting 10 seconds. This is kind of silly
relevance 0../test/test_torrent_parse.cpp:116test remap_files
relevance 0../test/test_torrent_parse.cpp:117merkle torrents. specifically torrent_info::add_merkle_nodes and torrent with "root hash"
relevance 0../test/test_torrent_parse.cpp:118torrent with 'p' (padfile) attribute
relevance 0../test/test_torrent_parse.cpp:119torrent with 'h' (hidden) attribute
relevance 0../test/test_torrent_parse.cpp:120torrent with 'x' (executable) attribute
relevance 0../test/test_torrent_parse.cpp:121torrent with 'l' (symlink) attribute
relevance 0../test/test_torrent_parse.cpp:122creating a merkle torrent (torrent_info::build_merkle_list)
relevance 0../test/test_torrent_parse.cpp:123torrent with multiple trackers in multiple tiers, making sure we shuffle them (how do you test shuffling?, load it multiple times and make sure it's in different order at least once)
relevance 0../test/test_tracker.cpp:198test parse peers6
relevance 0../test/test_tracker.cpp:199test parse tracker-id
relevance 0../test/test_tracker.cpp:200test parse failure-reason
relevance 0../test/test_tracker.cpp:201test all failure paths, including invalid bencoding not a dictionary no files entry in scrape response no info-hash entry in scrape response malformed peers in peer list of dictionaries uneven number of bytes in peers and peers6 string responses
relevance 0../test/test_transfer.cpp:288factor out the disk-full test into its own unit test
relevance 0../test/test_upnp.cpp:100store the log and verify that some key messages are there
relevance 0../test/web_seed_suite.cpp:366file hashes don't work with the new torrent creator reading async
relevance 0../src/block_cache.cpp:884it's somewhat expensive to iterate over this linked list. Presumably because of the random access of memory. It would be nice if pieces with no evictable blocks weren't in this list
relevance 0../src/block_cache.cpp:948this should probably only be done every n:th time
relevance 0../src/block_cache.cpp:1693create a holder for refcounts that automatically decrement
relevance 0../src/bt_peer_connection.cpp:671this could be optimized using knuth morris pratt
relevance 0../src/bt_peer_connection.cpp:2212if we're finished, send upload_only message
relevance 0../src/choker.cpp:332optimize this using partial_sort or something. We don't need to sort the entire list
relevance 0../src/choker.cpp:335make the comparison function a free function and move it into this cpp file
relevance 0../src/choker.cpp:340make configurable
relevance 0../src/choker.cpp:354make configurable
relevance 0../src/disk_buffer_pool.cpp:329perhaps we should sort the buffers here?
relevance 0../src/disk_io_thread.cpp:879it would be nice to optimize this by having the cache pieces also ordered by
relevance 0../src/disk_io_thread.cpp:922instead of doing a lookup each time through the loop, save cached_piece_entry pointers with piece_refcount incremented to pin them
relevance 0../src/disk_io_thread.cpp:1133instead of doing this. pass in the settings to each storage_interface call. Each disk thread could hold its most recent understanding of the settings in a shared_ptr, and update it every time it wakes up from a job. That way each access to the settings won't require a mutex to be held.
relevance 0../src/disk_io_thread.cpp:1161a potentially more efficient solution would be to have a special queue for retry jobs, that's only ever run when a job completes, in any thread. It would only work if counters::num_running_disk_jobs > 0
relevance 0../src/disk_io_thread.cpp:1175it should clear the hash state even when there's an error, right?
relevance 0../src/disk_io_thread.cpp:1870maybe the tailqueue_iterator should contain a pointer-pointer instead and have an unlink function
relevance 0../src/disk_io_thread.cpp:2125this is potentially very expensive. One way to solve it would be to have a fence for just this one piece.
relevance 0../src/disk_io_thread.cpp:2386we should probably just hang the job on the piece and make sure the hasher gets kicked
relevance 0../src/disk_io_thread.cpp:2456introduce a holder class that automatically increments and decrements the piece_refcount
relevance 0../src/disk_io_thread.cpp:2698it would be nice to not have to lock the mutex every turn through this loop
relevance 0../src/http_tracker_connection.cpp:185support this somehow
relevance 0../src/metadata_transfer.cpp:359this is not safe. The torrent could be unloaded while we're still sending the metadata
relevance 0../src/packet_buffer.cpp:176use compare_less_wrap for this comparison as well
relevance 0../src/part_file.cpp:252what do we do if someone is currently reading from the disk from this piece? does it matter? Since we won't actively erase the data from disk, but it may be overwritten soon, it's probably not that big of a deal
relevance 0../src/part_file.cpp:344instead of rebuilding the whole file header and flushing it, update the slot entries as we go
relevance 0../src/peer_connection.cpp:1017this should be the global download rate
relevance 0../src/peer_connection.cpp:3226sort the allowed fast set in priority order
relevance 0../src/peer_connection.cpp:5870The stats checks can not be honored when authenticated encryption is in use because we may have encrypted data which we cannot authenticate yet
relevance 0../src/piece_picker.cpp:2040this could probably be optimized by incrementally calling partial_sort to sort one more element in the list. Because chances are that we'll just need a single piece, and once we've picked from it we're done. Sorting the rest of the list in that case is a waste of time.
relevance 0../src/piece_picker.cpp:2545when expanding pieces for cache stripe reasons, the !downloading condition doesn't make much sense
relevance 0../src/session_impl.cpp:512there's no rule here to make uTP connections not have the global or local rate limits apply to it. This used to be the default.
relevance 0../src/session_impl.cpp:1727instead of having a special case for this, just make the default listen interfaces be "0.0.0.0:6881,[::1]:6881" and use the generic path. That would even allow for not listening at all.
relevance 0../src/session_impl.cpp:2620should this function take a shared_ptr instead?
relevance 0../src/session_impl.cpp:2985have a separate list for these connections, instead of having to loop through all of them
relevance 0../src/session_impl.cpp:3015this should apply to all bandwidth channels
relevance 0../src/session_impl.cpp:3496these vectors could be copied from m_torrent_lists, if we would maintain them. That way the first pass over all torrents could be avoided. It would be especially efficient if most torrents are not auto-managed whenever we receive a scrape response (or anything that may change the rank of a torrent) that one torrent could re-sort itself in a list that's kept sorted at all times. That way, this pass over all torrents could be avoided alltogether.
relevance 0../src/session_impl.cpp:3573allow extensions to sort torrents for queuing
relevance 0../src/session_impl.cpp:3746use a lower limit than m_settings.connections_limit to allocate the to 10% or so of connection slots for incoming connections
relevance 0../src/session_impl.cpp:3889post a message to have this happen immediately instead of waiting for the next tick
relevance 0../src/session_impl.cpp:3936this should be called for all peers!
relevance 0../src/session_impl.cpp:4327it might be a nice feature here to limit the number of torrents to send in a single update. By just posting the first n torrents, they would nicely be round-robined because the torrent lists are always pushed back
relevance 0../src/storage.cpp:716make this more generic to not just work if files have been renamed, but also if they have been merged into a single file for instance maybe use the same format as .torrent files and reuse some code from torrent_info
relevance 0../src/storage.cpp:1012if everything moves OK, except for the partfile we currently won't update the save path, which breaks things. it would probably make more sense to give up on the partfile
relevance 0../src/torrent.cpp:508if the existing torrent doesn't have metadata, insert the metadata we just downloaded into it.
relevance 0../src/torrent.cpp:659if the existing torrent doesn't have metadata, insert the metadata we just downloaded into it.
relevance 0../src/torrent.cpp:1461is verify_peer_cert called once per certificate in the chain, and this function just tells us which depth we're at right now? If so, the comment makes sense. any certificate that isn't the leaf (i.e. the one presented by the peer) should be accepted automatically, given preverified is true. The leaf certificate need to be verified to make sure its DN matches the info-hash
relevance 0../src/torrent.cpp:1865instead of creating the picker up front here, maybe this whole section should move to need_picker()
relevance 0../src/torrent.cpp:2061there may be peer extensions relying on the torrent extension still being alive. Only do this if there are no peers. And when the last peer is disconnected, if the torrent is unloaded, clear the extensions m_extensions.clear();
relevance 0../src/torrent.cpp:2736this pattern is repeated in a few places. Factor this into a function and generalize the concept of a torrent having a dedicated listen port
relevance 0../src/torrent.cpp:3515add one peer per IP the hostname resolves to
relevance 0../src/torrent.cpp:4509update suggest_piece?
relevance 0../src/torrent.cpp:4652really, we should just keep the picker around in this case to maintain the availability counters
relevance 0../src/torrent.cpp:6625make this more generic to not just work if files have been renamed, but also if they have been merged into a single file for instance maybe use the same format as .torrent files and reuse some code from torrent_info The mapped_files needs to be read both in the network thread and in the disk thread, since they both have their own mapped files structures which are kept in sync
relevance 0../src/torrent.cpp:6743if this is a merkle torrent and we can't restore the tree, we need to wipe all the bits in the have array, but not necessarily we might want to do a full check to see if we have all the pieces. This is low priority since almost no one uses merkle torrents
relevance 0../src/torrent.cpp:6934make this more generic to not just work if files have been renamed, but also if they have been merged into a single file for instance. using file_base
relevance 0../src/torrent.cpp:8936add a flag to ignore stats, and only care about resume data for content. For unchanged files, don't trigger a load of the metadata just to save an empty resume data file
relevance 0../src/torrent.cpp:10546instead of resorting the whole list, insert the peers directly into the right place
relevance 0../src/torrent_peer.cpp:176how do we deal with our external address changing?
relevance 0../src/udp_socket.cpp:286it would be nice to detect this on posix systems also
relevance 0../src/udp_socket.cpp:777use the system resolver_interface here
relevance 0../src/upnp.cpp:71listen_interface is not used. It's meant to bind the broadcast socket
relevance 0../src/ut_metadata.cpp:316we really need to increment the refcounter on the torrent while this buffer is still in the peer's send buffer
relevance 0../src/utp_stream.cpp:1644this loop may not be very efficient
relevance 0../src/web_connection_base.cpp:73introduce a web-seed default class which has a low download priority
relevance 0../src/kademlia/dht_tracker.cpp:295ideally this function would be called when the put completes
relevance 0../include/libtorrent/bitfield.hpp:158rename to data() ?
relevance 0../include/libtorrent/block_cache.hpp:213make this 32 bits and to count seconds since the block cache was created
relevance 0../include/libtorrent/config.hpp:334Make this count Unicode characters instead of bytes on windows
relevance 0../include/libtorrent/disk_buffer_pool.hpp:134try to remove the observers, only using the async_allocate handlers
relevance 0../include/libtorrent/file.hpp:168move this into a separate header file, TU pair
relevance 0../include/libtorrent/peer_connection.hpp:205make this a raw pointer (to save size in the first cache line) and make the constructor take a raw pointer. torrent objects should always outlive their peers
relevance 0../include/libtorrent/peer_connection.hpp:1055factor this out into its own class with a virtual interface torrent and session should implement this interface
relevance 0../include/libtorrent/peer_connection_interface.hpp:45make this interface smaller!
relevance 0../include/libtorrent/performance_counters.hpp:132should keepalives be in here too? how about dont-have, share-mode, upload-only
relevance 0../include/libtorrent/performance_counters.hpp:442some space could be saved here by making gauges 32 bits
relevance 0../include/libtorrent/performance_counters.hpp:443restore these to regular integers. Instead have one copy of the counters per thread and collect them at convenient synchronization points
relevance 0../include/libtorrent/piece_picker.hpp:761should this be allocated lazily?
relevance 0../include/libtorrent/proxy_base.hpp:171it would be nice to remember the bind port and bind once we know where the proxy is m_sock.bind(endpoint, ec);
relevance 0../include/libtorrent/receive_buffer.hpp:255Detect when the start of the next crpyto packet is aligned with the start of piece data and the crpyto packet is at least as large as the piece data. With a little extra work we could receive directly into a disk buffer in that case.
relevance 0../include/libtorrent/session.hpp:861add get_peer_class_type_filter() as well
relevance 0../include/libtorrent/settings_pack.hpp:1099deprecate this ``max_rejects`` is the number of piece requests we will reject in a row while a peer is choked before the peer is considered abusive and is disconnected.
relevance 0../include/libtorrent/torrent.hpp:1265this wastes 5 bits per file
relevance 0../include/libtorrent/torrent.hpp:1324These two bitfields should probably be coalesced into one
relevance 0../include/libtorrent/torrent_info.hpp:123include the number of peers received from this tracker, at last announce
relevance 0../include/libtorrent/torrent_info.hpp:270there may be some opportunities to optimize the size if torrent_info. specifically to turn some std::string and std::vector into pointers
relevance 0../include/libtorrent/tracker_manager.hpp:382this should be unique_ptr in the future
relevance 0../include/libtorrent/upnp.hpp:108support using the windows API for UPnP operations as well
relevance 0../include/libtorrent/utp_stream.hpp:395implement blocking write. Low priority since it's not used (yet)
relevance 0../include/libtorrent/kademlia/item.hpp:61since this is a public function, it should probably be moved out of this header and into one with other public functions.
relevance 0../include/libtorrent/aux_/session_impl.hpp:836should this be renamed m_outgoing_interfaces?
relevance 0../include/libtorrent/aux_/session_impl.hpp:887replace this by a proper asio timer
relevance 0../include/libtorrent/aux_/session_impl.hpp:892replace this by a proper asio timer
relevance 0../include/libtorrent/aux_/session_impl.hpp:899replace this by a proper asio timer
relevance 0../include/libtorrent/aux_/session_interface.hpp:229it would be nice to not have this be part of session_interface
relevance 0../include/libtorrent/aux_/session_settings.hpp:78make this a bitfield