[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Error 500 when querying binary/by_metadata/Go-Import-Path



On Fri, Sep 23, 2022 at 07:16:42PM +0200, Mattia Rizzolo wrote:
> On Fri, Sep 23, 2022 at 05:19:39PM +0200, Andrea Pappacoda wrote:
> > I then discovered that the tool queries dak's API, specifically the
> > <https://api.ftp-master.debian.org/binary/by_metadata/Go-Import-Path>
> > endpoint, and currently it seems that querying that URL leads to an HTTP 500
> > error.
> > 
> > Does somebody know what is going on?
> 
> Probably:
> 
> Traceback (most recent call last):
>   File "/usr/lib/python3/dist-packages/bottle.py", line 869, in _handle
>     return route.call(**args)
>   File "/usr/lib/python3/dist-packages/bottle.py", line 1749, in wrapper
>     rv = callback(*a, **ka)
>   File "/srv/ftp-master.debian.org/dak/dakweb/queries/binary.py", line 63, in binary_by_metadata
>     q = q.join(DBSource).join(SourceMetadata).join(MetadataKey)
>   File "/usr/lib/python3/dist-packages/sqlalchemy/orm/query.py", line 2391, in join
>     return self._join(
>   File "<string>", line 2, in _join
>   File "/usr/lib/python3/dist-packages/sqlalchemy/orm/base.py", line 227, in generate
>     fn(self, *args[1:], **kw)
>   File "/usr/lib/python3/dist-packages/sqlalchemy/orm/query.py", line 2587, in _join
>     self._join_left_to_right(
>   File "/usr/lib/python3/dist-packages/sqlalchemy/orm/query.py", line 2611, in _join_left_to_right
>     ) = self._join_determine_implicit_left_side(left, right, onclause)
>   File "/usr/lib/python3/dist-packages/sqlalchemy/orm/query.py", line 2747, in _join_determine_implicit_left_side
>     raise sa_exc.InvalidRequestError(
> sqlalchemy.exc.InvalidRequestError: Can't determine which FROM clause to join from, there are multiple FROMS which can join to this entity. Please use the .select_from() method to establish an explicit left side, as well as providing an explcit ON clause if not present already to help resolve the ambiguity.
> 
> 
> (or at least, apache'2 errors.log is full of that, so at the very least
> that's one error...)
> 
This should now be fixed.

Cheers,
Julien


Reply to: