~dr|z3d
@RN
@RN_
@StormyCloud
@T3s|4
@T3s|4_
@eyedeekay
@orignal
@postman
@zzz
%Liorar
%cumlord
+FreefallHeavens
+Xeha
+ardu
+hk
+mareki2p
+profetikla
+qend-irc2p
+r00tobo_BNC
+segfault
Arch
BubbRubb
Danny
DeltaOreo
Irc2PGuest21579
Irc2PGuest34419
Irc2PGuest49450
Meow
Onn4l7h
Onn4|7h
SigSegv
acetone_
boonst
carried6590
duck
maylay
not_bob_afk
pisslord
poriori_
shiver_
simprelay
solidx66
thetia
u5657
weko_
woodwose
zer0bitz_
qend-irc2p
Hello! I'd like to report a bug in the i2psnark standalone(https://gitlab.com/i2pplus/I2P.Plus/-/jobs/artifacts/master/raw/i2psnark-standalone.zip?job=Java8) web interface. When two different torrents (with different data_directory paths) have the same name, the interface generates the same link for both, such as: x.x.x.x:8002/i2psnark/torrent_name. This leads to undefined behavior — only one of the
qend-irc2p
torrents can be accessed through the web UI, while the other becomes unreachable. If someone here is maintaining this part of the code, would it be possible to make the link unique, for example using the infohash instead: x.x.x.x:8002/i2psnark/INFOHASH
dr|z3d
that's a new one.
dr|z3d
I don't think we've seen that before, zzz?
dr|z3d
also, hello, qend-irc2p, welcome to #saltr!
dr|z3d
I'm not even sure that should be possible, there should be a naming conflict when the second torrent's data is written.
zzz
pretty sure we have checks in there, but maybe they got bypassed or broken
dr|z3d
I'm scratching my head.. if the torrents have different data dirs, and presumably different names, how can we get a conflict?
dr|z3d
Unless the torrents themselves are being stored in different locations, but then they should be copied back to the data dir, so I'm a bit confused.
dr|z3d
anyways, thanks for the report, qend-irc2p
qend-irc2p
~dr|z3d, look — if we start downloading two torrents and specify two different directories for them, but both torrents internally have a folder named, say, "New_Folder", then in the Snark web interface we'll have a single link like x.x.x.x:8002/i2psnark/New_Folder, and undefined behavior occurs when we try to view that torrent in the web interface.
qend-irc2p
Yes, the downloading goes into separate directories, so there's no naming conflict, but still — the issue shows up in the web UI.
dr|z3d
qend-irc2p: ok, that's fairly atypical, but we'll look into it.