Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix recurrence #71

Merged
merged 1 commit into from
Oct 24, 2024
Merged

Fix recurrence #71

merged 1 commit into from
Oct 24, 2024

Conversation

Marenz
Copy link
Contributor

@Marenz Marenz commented Oct 23, 2024

Recurrence didn't properly work as we passed in the
empty list for the by-* fiedls by default
which means "No valid time-unit",
e.g bymonth=[] means no month at all. never.

Recurrence didn't properly work as we passed in the
empty list for the by-* fiedls by default
which means "No valid time-unit",
e.g bymonth=[] means no month at all. never.

Signed-off-by: Mathias L. Baumann <mathias.baumann@frequenz.com>
@Marenz Marenz requested a review from a team as a code owner October 23, 2024 11:50
@github-actions github-actions bot added part:docs Affects the documentation part:dispatcher Affects the high-level dispatcher interface labels Oct 23, 2024
@Marenz Marenz requested review from llucax and removed request for andrew-stevenson-frequenz October 23, 2024 11:51
@@ -2,4 +2,4 @@

## Summary

* `frequenz-sdk` dependency has been extended to include version `1.0.0-rc1000`.
This is a hot fix for recurrence not working
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can you describe better what the issue exactly was here too? As a user I have no idea how my code was affected before this release and what should I expect from this one.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There is really only one user and I talked to him already ;)

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You can assume that it wasn't working at all before, the chance that it was is very low.
If it was working for the user before, they must already have a detailed understanding of this problem or they couldn't have worked around it

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Well, you don't know for sure, this is a public repo. I'm sure we have plenty of external users :trollface:

But anyway, I think it is good practice to write notes that are useful, otherwise there isn't much point in writing them at all.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Well, I see all the logs and request in the API, I know for sure :P

But.. yes, I suppose it is good practice.

@Marenz Marenz added this pull request to the merge queue Oct 24, 2024
@llucax llucax changed the title Fix recurrence. Fix recurrence Oct 24, 2024
@github-merge-queue github-merge-queue bot removed this pull request from the merge queue due to failed status checks Oct 24, 2024
@Marenz Marenz added this pull request to the merge queue Oct 24, 2024
Merged via the queue into frequenz-floss:v0.x.x with commit 2f9c764 Oct 24, 2024
14 checks passed
@Marenz Marenz deleted the fixrecur branch October 24, 2024 08:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
part:dispatcher Affects the high-level dispatcher interface part:docs Affects the documentation
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants