pimutils / pimutils/khal

Setting the start and end timedate in a new event sometimes fails ("end date before start date" error)

Open
#1,394 1 comment 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Python
Stars
3.1k
Forks
233
Avg merge
1h 44m
Merged PRs (30d)
1

Description

  1. Start khal interactively
  2. make a new event
  3. set the start time and the end time (I set it normally with 1 hour difference)
  4. Sometimes (like in 50%) the khal denies creating event saying "end date before start date"
  5. Return to set the times normally solves the issue

OS, version, khal version and how you installed it:

  • khal 0.11.3
  • installation method: pip
  • python 3.8.10
  • Linux Mint
  • Your khal config file
    `
    [locale]
    timeformat = %H:%M
    dateformat = %d.%m.%Y
    longdateformat = %d.%m.%Y
    datetimeformat = %d.%m.%Y %H:%M
    longdatetimeformat = %a %d.%m.%Y %H:%M
    unicode_symbols = true

[default]
highlight_event_days=True
show_all_days=False
default_calendar=mycal

[highlight_days]
color = dark cyan
`

Additional context

Sometimes even if the error is not shown the actual time interval is far from 1 h, but 8 hours or more.
For example, I set from 10:30 till 11:15, but when I save it, I got from 10:30 till 21:00

Image

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start khal interactively and reproduce the new-event flow by entering a one-hour start and end interval, then compare the saved event’s times with the entered values. Trace the handling of start and end times around event creation, including the reported “end date before start date” validation. Done means repeated entries save the intended interval without intermittent errors or large time shifts.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
cli
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.