Hi,
When pushing to a non-existing repository on hg.sr.ht it is failing
instead of creating the repository:
$ hg push ssh://hg@hg.sr.ht/~fcresende/new_repo
pushing to ssh://hg@hg.sr.ht/~fcresende/new_repo
remote: Traceback (most recent call last):
remote: File "/usr/bin/hgsrht-shell", line 269, in <module>
remote: r = check_ssh_access(path, user_id, username)
remote: ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
remote: File "/usr/bin/hgsrht-shell", line 122, in check_ssh_access_sql
remote: r = _do_get_or_create_repo(path, user_id, username, con)
remote: ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
remote: File "/usr/bin/hgsrht-shell", line 162, in _do_get_or_create_repo
remote: row = query.one()._mapping
remote: ^^^^^^^^^^^
remote: File
"/usr/lib/python3.11/site-packages/sqlalchemy/engine/result.py", line
1520, in one
remote: return self._only_one_row(
remote: ^^^^^^^^^^^^^^^^^^^
remote: File
"/usr/lib/python3.11/site-packages/sqlalchemy/engine/result.py", line
752, in _only_one_row
remote: raise exc.NoResultFound(
remote: sqlalchemy.exc.NoResultFound: No row was found when one was required
Best regards,
Felipe
> When pushing to a non-existing repository on hg.sr.ht it is failing
> instead of creating the repository:
Ah yes, I think that's a fallout of the recent breaking changes in
sqlalchemy.
It should be fixed soon, once it's done deploying the new version.
Thanks for reporting the problem!
On 3/30/24 17:11, Ludovic Chabant wrote:
> Scratch that, the ongoing issue with python package versions somehow
> also happened on a tagged release, and prevented deploying the fix...
> I'm not sure why yet...
>
> https://builds.sr.ht/~sircmpwn/job/1182935#task-package
no hurry, thanks.