Cloudron makes it easy to run web apps like WordPress, Nextcloud, GitLab on your server. Find out more or install now.


  • Categories
  • Recent
  • Tags
  • Popular
  • Bookmarks
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse

Cloudron Forum

Apps | Demo | Docs | Install

UX: Enable cancelling of tasks that are going to fail after a long timeout

Scheduled Pinned Locked Moved Feature Requests
userinterface
9 Posts 5 Posters 210 Views
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • robiR Offline
    robiR Offline
    robi
    wrote on last edited by girish
    #1

    Now it's something like 120seconds, which is an eternity to wait. if we can bring it down to 10s or so that would be great.

    After failure the only thing we can do is retry the tasks, but not cancel, which seems like a miss.

    It was nice to have the checkbox for the second task that was failing, which we could uncheck and get things moving again.

    Life of sky tech

    1 Reply Last reply
    1
  • nebulonN Offline
    nebulonN Offline
    nebulon Staff
    wrote on last edited by
    #2

    The long wait was intentional here. Users would cancel tasks because they take too long, like a backup or domain changes which due to long TTLs simply do take long. The result was that users end up with broken apps due to cancelling tasks prematurely.

    I wonder in your case if there are better fixes. The question might be to see why you want to cancel a task in the first place?

    d19dotcaD robiR 2 Replies Last reply
    0
  • d19dotcaD Offline
    d19dotcaD Offline
    d19dotca
    replied to nebulon on last edited by
    #3

    @nebulon One use-case I can think of is when a backup is going on and therefore nothing else can really be done (i.e. can't change memory on an app as it has to wait for the other tasks to complete), but then maybe during that time I change my mind and want to increase the memory even more than I originally did, I could cancel the change and make the correct one so it doesn't need to be restarted twice. It's really a minor issue in my mind but would be nice to cancel "waiting/pending" tasks in particular in my use-cases.

    --
    Dustin Dauncey
    www.d19.ca

    1 Reply Last reply
    0
  • robiR Offline
    robiR Offline
    robi
    replied to nebulon on last edited by
    #4

    I wonder in your case if there are better fixes. The question might be to see why you want to cancel a task in the first place?

    Task queue management might be one of those better ways.

    There will always be some who will shoot themselves in the foot, but a hammer is a tool and your responsibility in how to "apply" it.

    That way as @d19dotca mentioned, fixing the order of operations and taking out an unneeded one is much more responsive.

    I'd also like to queue up a few operations and have them keep working in the background, while I do more important things than wait for one or more to finish.

    Life of sky tech

    1 Reply Last reply
    0
  • LonkleL Offline
    LonkleL Offline
    Lonkle
    wrote on last edited by Lonkle
    #5

    As a developer, I had to uninstall, re-install a lot, and waiting forever for that little "x" to appear to cancel the starting phase, the healthcheck, etc (depends on which phase of development I was on) too forever in "I have an idea to fix this time." 😂

    Maybe hardcode Contributors with getting access to that cancellation everytime, orrrrrrr just throw it in with the buttons in the logs. Because we also usually can tell from there. I will say the first time my app worked I didn't know and I left the logs to go uninstall it for my "next test" when I saw it was "Running". 😂

    girishG 1 Reply Last reply
    0
  • nebulonN Offline
    nebulonN Offline
    nebulon Staff
    wrote on last edited by
    #6

    As a developer you could also use the CLI tool, that has a cloudron cancel command to do it immediately.

    LonkleL 1 Reply Last reply
    3
  • girishG Offline
    girishG Offline
    girish Staff
    replied to Lonkle on last edited by
    #7

    @Lonk uninstall is always available, never disabled. Unlike other actions.

    LonkleL 1 Reply Last reply
    0
  • LonkleL Offline
    LonkleL Offline
    Lonkle
    replied to nebulon on last edited by Lonkle
    #8

    @nebulon As a developer, I'm an idiot. 😂 I'll be doing that from now on; thanks!

    1 Reply Last reply
    1
  • LonkleL Offline
    LonkleL Offline
    Lonkle
    replied to girish on last edited by Lonkle
    #9

    @girish There's was a lot of times I didn't want to uninstall to re-install (just re-start with some box changes), but when "restarting" them I had to wait for them to finally "Not Respond" at certain points to restart my test of it connecting apps. Obviously because I was working in box out of necessity, my specific situation was a little weird. 😅

    1 Reply Last reply
    0

  • Login

  • Don't have an account? Register

  • Login or register to search.
  • First post
    Last post
0
  • Categories
  • Recent
  • Tags
  • Popular
  • Bookmarks
  • Login

  • Don't have an account? Register

  • Login or register to search.