starred/panel-pelican-dev
1
0
Fork 0
mirror of https://github.com/pelican-dev/panel.git synced 2026-05-04 18:00:48 +03:00
Code Issues 41 Packages Projects Releases 10 Wiki Activity

Time Offset "missing" when editing the first task in list of schedule #462

New Issue
Closed
opened 2026-02-05 17:38:02 +03:00 by OVERLORD · 8 comments
OVERLORD commented 2026-02-05 17:38:02 +03:00
Owner
Copy Link

Originally created by @xBlueCellx on GitHub (Oct 2, 2025).

Current Behavior

When i create a schedule to perform a task, i can set a Time Offset.
When editing the first task in line, it´s Time Offset is not editable.

Expected Behavior

The Time Offset of the first entry should be editable, like the rest of the tasks below.

Steps to Reproduce

Just create some task in a schedule, on the first line you will not be able to edit the Time Offset.

Panel Version

canary

Wings Version

1.0.0-beta17

Games and/or Eggs Affected

No response

Docker Image

No response

Error Logs

Is there an existing issue for this?

  • I have searched the existing issues before opening this issue.
  • I have provided all relevant details, including the specific game and Docker images I am using if this issue is related to running a server.
  • I have checked in the Discord server and believe this is a bug with the software, and not a configuration issue with my specific system.
Originally created by @xBlueCellx on GitHub (Oct 2, 2025). ### Current Behavior When i create a schedule to perform a task, i can set a Time Offset. When editing the first task in line, it´s Time Offset is not editable. ### Expected Behavior The Time Offset of the first entry should be editable, like the rest of the tasks below. ### Steps to Reproduce Just create some task in a schedule, on the first line you will not be able to edit the Time Offset. ### Panel Version canary ### Wings Version 1.0.0-beta17 ### Games and/or Eggs Affected _No response_ ### Docker Image _No response_ ### Error Logs ```bash ``` ### Is there an existing issue for this? - [x] I have searched the existing issues before opening this issue. - [x] I have provided all relevant details, including the specific game and Docker images I am using if this issue is related to running a server. - [x] I have checked in the Discord server and believe this is a bug with the software, and not a configuration issue with my specific system.
OVERLORD added the not confirmed label 2026-02-05 17:38:02 +03:00
OVERLORD commented 2026-02-05 17:38:06 +03:00
Author
Owner
Copy Link

@JoanFo1456 commented on GitHub (Oct 2, 2025):

It's not a bug, it's made on purpose, first task shouldn't have offset.

@JoanFo1456 commented on GitHub (Oct 2, 2025): It's not a bug, it's made on purpose, first task shouldn't have offset.
OVERLORD commented 2026-02-05 17:38:10 +03:00
Author
Owner
Copy Link

@tuAntonioo commented on GitHub (Oct 2, 2025):

From what I remember thats not a bug. Why would you want to set offset on the first task?

@tuAntonioo commented on GitHub (Oct 2, 2025): From what I remember thats not a bug. Why would you want to set offset on the first task?
OVERLORD commented 2026-02-05 17:38:11 +03:00
Author
Owner
Copy Link

@xBlueCellx commented on GitHub (Oct 2, 2025):

From what I remember thats not a bug. Why would you want to set offset on the first task?

Alright, i get your point. Was just thinking it might be a bug, since you are still able to set a Time Offset on first generation of a task.

@xBlueCellx commented on GitHub (Oct 2, 2025): > From what I remember thats not a bug. Why would you want to set offset on the first task? Alright, i get your point. Was just thinking it might be a bug, since you are still able to set a Time Offset on first generation of a task.
OVERLORD commented 2026-02-05 17:38:13 +03:00
Author
Owner
Copy Link

@JoanFo1456 commented on GitHub (Oct 2, 2025):

From what I remember thats not a bug. Why would you want to set offset on the first task?

Alright, i get your point. Was just thinking it might be a bug, since you are still able to set a Time Offset on first generation of a task.

I see, on creation it shows, I'll take a look.

@JoanFo1456 commented on GitHub (Oct 2, 2025): > > From what I remember thats not a bug. Why would you want to set offset on the first task? > > Alright, i get your point. Was just thinking it might be a bug, since you are still able to set a Time Offset on first generation of a task. I see, on creation it shows, I'll take a look.
OVERLORD commented 2026-02-05 17:38:16 +03:00
Author
Owner
Copy Link

@xBlueCellx commented on GitHub (Oct 2, 2025):

It's not a bug, it's made on purpose, first task shouldn't have offset.

So one question then still remains for me. Tasks get processed in the order they are in the list?
If yes, then the workflow for inserting one task at start or in between would be deleting and recreating. Totally doable but not quite intuitive.

That´s how i encountered my "issue". I wanted to insert a notificaton before the server does a restart/backup. So i tried to set the Time Offset of the first task (Restart/Backup) to 10 seconds and see if the order changes.

@xBlueCellx commented on GitHub (Oct 2, 2025): > It's not a bug, it's made on purpose, first task shouldn't have offset. So one question then still remains for me. Tasks get processed in the order they are in the list? If yes, then the workflow for inserting one task at start or in between would be deleting and recreating. Totally doable but not quite intuitive. That´s how i encountered my "issue". I wanted to insert a notificaton before the server does a restart/backup. So i tried to set the Time Offset of the first task (Restart/Backup) to 10 seconds and see if the order changes.
OVERLORD commented 2026-02-05 17:38:17 +03:00
Author
Owner
Copy Link

@JoanFo1456 commented on GitHub (Oct 2, 2025):

It's not a bug, it's made on purpose, first task shouldn't have offset.

So one question then still remains for me. Tasks get processed in the order they are in the list? If yes, then the workflow for inserting one task at start or in between would be deleting and recreating. Totally doable but not quite intuitive.

That´s how i encountered my "issue". I wanted to insert a notificaton before the server does a restart/backup. So i tried to set the Time Offset of the first task (Restart/Backup) to 10 seconds and see if the order changes.

Not really, you can reorder, below Tasks you see two arrows? That allows you to reorder by dragging.

@JoanFo1456 commented on GitHub (Oct 2, 2025): > > It's not a bug, it's made on purpose, first task shouldn't have offset. > > So one question then still remains for me. Tasks get processed in the order they are in the list? If yes, then the workflow for inserting one task at start or in between would be deleting and recreating. Totally doable but not quite intuitive. > > That´s how i encountered my "issue". I wanted to insert a notificaton before the server does a restart/backup. So i tried to set the Time Offset of the first task (Restart/Backup) to 10 seconds and see if the order changes. Not really, you can reorder, below Tasks you see two arrows? That allows you to reorder by dragging.
OVERLORD commented 2026-02-05 17:38:20 +03:00
Author
Owner
Copy Link

@xBlueCellx commented on GitHub (Oct 2, 2025):

It's not a bug, it's made on purpose, first task shouldn't have offset.

So one question then still remains for me. Tasks get processed in the order they are in the list? If yes, then the workflow for inserting one task at start or in between would be deleting and recreating. Totally doable but not quite intuitive.
That´s how i encountered my "issue". I wanted to insert a notificaton before the server does a restart/backup. So i tried to set the Time Offset of the first task (Restart/Backup) to 10 seconds and see if the order changes.

Not really, you can reorder, below Tasks you see two arrows? That allows you to reorder by dragging.

Thanks for pointing that out, nice feature 🚀
I'll close this "issue" then.

Sorry for bothering btw, i'm totally a newbie with pelican and just want to provide some feedback and maybe someday even some commits/PRs. It's a quite versatile project for homelab owners and even more usecases.

@xBlueCellx commented on GitHub (Oct 2, 2025): > > > It's not a bug, it's made on purpose, first task shouldn't have offset. > > > > > > So one question then still remains for me. Tasks get processed in the order they are in the list? If yes, then the workflow for inserting one task at start or in between would be deleting and recreating. Totally doable but not quite intuitive. > > That´s how i encountered my "issue". I wanted to insert a notificaton before the server does a restart/backup. So i tried to set the Time Offset of the first task (Restart/Backup) to 10 seconds and see if the order changes. > > Not really, you can reorder, below Tasks you see two arrows? That allows you to reorder by dragging. Thanks for pointing that out, nice feature 🚀 I'll close this "issue" then. Sorry for bothering btw, i'm totally a newbie with pelican and just want to provide some feedback and maybe someday even some commits/PRs. It's a quite versatile project for homelab owners and even more usecases.
OVERLORD commented 2026-02-05 17:38:23 +03:00
Author
Owner
Copy Link

@JoanFo1456 commented on GitHub (Oct 2, 2025):

It's not a bug, it's made on purpose, first task shouldn't have offset.

So one question then still remains for me. Tasks get processed in the order they are in the list? If yes, then the workflow for inserting one task at start or in between would be deleting and recreating. Totally doable but not quite intuitive.
That´s how i encountered my "issue". I wanted to insert a notificaton before the server does a restart/backup. So i tried to set the Time Offset of the first task (Restart/Backup) to 10 seconds and see if the order changes.

Not really, you can reorder, below Tasks you see two arrows? That allows you to reorder by dragging.

Thanks for pointing that out, nice feature 🚀 I'll close this "issue" then.

Sorry for bothering btw, i'm totally a newbie with pelican and just want to provide some feedback and maybe someday even some commits/PRs. It's a quite versatile project for homelab owners and even more usecases.

It indeed has a bug, I'll fix it and send a pr, hope they see it, thanks.

@JoanFo1456 commented on GitHub (Oct 2, 2025): > > > > It's not a bug, it's made on purpose, first task shouldn't have offset. > > > > > > > > > So one question then still remains for me. Tasks get processed in the order they are in the list? If yes, then the workflow for inserting one task at start or in between would be deleting and recreating. Totally doable but not quite intuitive. > > > That´s how i encountered my "issue". I wanted to insert a notificaton before the server does a restart/backup. So i tried to set the Time Offset of the first task (Restart/Backup) to 10 seconds and see if the order changes. > > > > > > Not really, you can reorder, below Tasks you see two arrows? That allows you to reorder by dragging. > > Thanks for pointing that out, nice feature 🚀 I'll close this "issue" then. > > Sorry for bothering btw, i'm totally a newbie with pelican and just want to provide some feedback and maybe someday even some commits/PRs. It's a quite versatile project for homelab owners and even more usecases. It indeed has a bug, I'll fix it and send a pr, hope they see it, thanks.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
not confirmed
pull-request
Mirrored from GitHub Pull Request
 👑 sponsor
💰 fund
🔴 hard
🟡 medium
🟡 medium
🟡 medium
🟢 easy
🟢 easy
🟢 easy
No Label not confirmed
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
OVERLORD
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/panel-pelican-dev#462
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?