Update to 3.3.0
This update has been submitted for testing by svashisht.
This update's test gating status has been changed to 'ignored'.
This update's test gating status has been changed to 'waiting'.
This update has been pushed to testing.
Dies after space is pressed on the prompt with:
error: ../src/reader.cpp:3837: failed assertion: should have been handled by inputter_t:readch
fish-3.2.1-2 works fine.
Bodhi is disabling automatic push to stable due to negative karma. The maintainer may push manually if they determine that the issue is not severe.
This update has been obsoleted by fish-3.3.1-1.fc34.
Dies after space is pressed on the prompt with: error: ../src/reader.cpp:3837: failed assertion: should have been handled by inputter_t:readch fish-3.2.1-2 works fine.
Possibly fixed here.
I have updated to 3.3.1 and above fix is included there. See https://bodhi.fedoraproject.org/updates/FEDORA-2021-96c5f8e1a2
I have updated to 3.3.1 and above fix is included there. See FEDORA-2021-96c5f8e1a2
However mentioned patch is in 3.3.0 too. If you can still reproduce this issue, it would be better to follow up on this issue in upstream.
Please login to add feedback.
Confirm request to re-trigger tests.
This update has been submitted for testing by svashisht.
This update's test gating status has been changed to 'ignored'.
This update's test gating status has been changed to 'waiting'.
This update's test gating status has been changed to 'ignored'.
This update has been pushed to testing.
Dies after space is pressed on the prompt with:
error: ../src/reader.cpp:3837: failed assertion: should have been handled by inputter_t:readch
fish-3.2.1-2 works fine.
Bodhi is disabling automatic push to stable due to negative karma. The maintainer may push manually if they determine that the issue is not severe.
This update has been obsoleted by fish-3.3.1-1.fc34.
Possibly fixed here.
I have updated to 3.3.1 and above fix is included there. See https://bodhi.fedoraproject.org/updates/FEDORA-2021-96c5f8e1a2
However mentioned patch is in 3.3.0 too. If you can still reproduce this issue, it would be better to follow up on this issue in upstream.