A commit has broken creation of v3 onion services with Stem 1.7

added component::archived/stem hs owner::atagar priority::high regression reporter::maqp resolution::duplicate severity::normal status::closed type::defect labels

Trac:
Component: - Select a component to Core Tor/Tor
Milestone: N/A to Tor: 0.4.0.x-final
Keywords: N/A deleted, regression hs added

This bug affects both OnionShare and TFC that are no longer able to use v3 Onion Services. For TFC it makes releasing the next version quite impossible as it will be v3 only.

Does Tor 0.4.0.x-final milestone mean the projects will have to wait until April? Everything has been working great for five months: ever since #25552 (that was considered to be 0.3.5 must) was fixed.

I understand you're busy but if it's at all possible, could you please take a look what's going on.

Atagar: can you please check if this is something Stem could fix?

Trac:
Username: maqp

Oh; I hadn't seen that this bug is in 0.3.5.

I don't see how it can be caused by the commit that you mention, though: that commit only changes log messages.

Trac:
Milestone: Tor: 0.4.0.x-final to Tor: 0.3.5.x-final

Oh, I get it! This is the stem bug related to the changed log messages. It should be fixed in stem soon.

Trac:
Component: Core Tor/Tor to Core Tor/Stem
Owner: N/A to atagar
Cc: N/A to atagar
Milestone: Tor: 0.3.5.x-final to N/A

nickm: Thank you! I'm not sure to what bug you are referring to. Is there a ticket number?

Trac:
Username: maqp

Replying to maqp:

nickm: Thank you! I'm not sure to what bug you are referring to. Is there a ticket number?

#28844 (closed)

Hi Nick. To be clear this was not a stem bug. Stem was working as intended.

Tor changed its bootstrap log messages with the upfront understanding that it would break things like this. Please see #28731 (moved) for the discussion.

Trac:
Status: new to closed
Resolution: N/A to duplicate

closed

A commit has broken creation of v3 onion services with Stem 1.7

Child items ...

Activity