You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hmm, maybe you've found a bug. Could you put a print statement in the
Beeminder API wrapper class to see exactly what's being sent, and see if
that makes sense / try sending that to the Beeminder API manually?
On Tue, Mar 10, 2020, 4:34 AM Tom Dörr ***@***.***> wrote:
When I run
dummy3.stage_rate_change(1, 1586815200, 1586820000)
dummy3.commit_road()
I get the following output:
Exception: API request failed with code 422: {"errors":{"message":"Error parsing params (roadall)"}}
Am I using stage_rate_change correctly? Is it correct to input the start
and end timestamps as Unix timestamps?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#6?email_source=notifications&email_token=ABDQSPTS6JYHBDFJR3AKNSLRGX3RFA5CNFSM4LEZUDCKYY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4ITZ5UBA>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABDQSPV4GYL5PGWOKYPOQ53RGX3RFANCNFSM4LEZUDCA>
.
The Unix timestamp 1576429200 is neither the start nor the end timestamp I set, but the timestamp of the first datapoint for the goal.
I guess the error occurs because the timestamp corresponds to Sun Dec 15 18:00:00 CET 2019.
After that I looked into self._dense_path and noticed that the rate is not changed there since the steps are bigger than the timestamp range that I set for stage_rate_change.
After increasing the range to 1586815200(Tue Apr 14 00:00:00 CEST 2020) - 1587820000 (Sat Apr 25 15:06:40 CEST 2020), pyminder transmits the following:
When I run
I get the following output:
Am I using
stage_rate_change
correctly? Is it correct to input the start and end timestamps as Unix timestamps?The text was updated successfully, but these errors were encountered: