Message7578
Hi Bern:
There appears to be a misunderstanding.
In message <1654757054.12.0.23438825126.issue2551209@roundup.psfhosted.org>,
Bernhard Reiter writes:
>so far we cannot reproduce the problem.
This is true for my test instance.
However the problem Marcus' describes is on the
https://issues.roundup-tracker.org tracker when he submitted the
attached message. It's not one of Marcus' trackers.
I was able to reproduce the problem on the issues.roundup-tracker.org
tracker. My "fix" to the logging.getLogger() calls to eliminate the
error seems to have fixed it on issues.roundup-tracker.org. Howvwer I
can't explain why that made the error go away.
Also I can't reproduce that failure in my test code to understand why
that failure caused the behavior Marcus described.
>There must be something different [...] (Could be some different in
>Python version or version settings inherited from the general
>operating system or something done by a set of reactors or other
>modules.)
That's what I am assuming. However I am using the tracker from
mercurial that should be the same as what is deployed on
issues.roundup-tracker.org. Work continues to verify that assumption.
-- rouilj |
|
Date |
User |
Action |
Args |
2022-06-09 13:31:49 | rouilj | set | recipients:
+ rouilj, schlatterbeck, ber, marcus.priesch |
2022-06-09 13:31:49 | rouilj | link | issue2551209 messages |
2022-06-09 13:31:49 | rouilj | create | |
|