timeperiods is a required property
See original GitHub issueFirefox addon on Linux is giving me:

Looked at the console, and this is the error for all requests:
{
"errors": {
"timeperiods": "'timeperiods' is a required property"
},
"message": "Input payload validation failed"
}
I’m running from source, here are the steps:
cd ~/.apps/activitywatch
git pull
git submodule update --recursive
rm -rf venv
python3 -m venv venv
source venv/bin/activate
make build DEV=true
Issue Analytics
- State:
- Created 5 years ago
- Comments:8 (4 by maintainers)
Top Results From Across the Web
Real Estate Dates and Time Periods Flashcards - Quizlet
Time Period which the pre-License will expired. Two Years. Experience requirements for brokers applicant obtained within preceding five-year-period.
Read more >Frequently Asked Questions (FAQs) About 1031 Exchanges
How long does a property need to be held prior to doing an exchange? The tax code does not provide a specific time...
Read more >1031 Exchange Holding Period Requirements - Accruit
Most exchange expert commentators take the position that a holding of two years or more is so significant an amount of time that...
Read more >Property Types and Abandonment Periods - Texas Comptroller
Abandonment Periods Quick Reference. Type of Property, Property Code, Abandonment Period. Wages, Payroll or Salary, MS01, 1 year.
Read more >adverse possession | Wex | LII / Legal Information Institute
The common law requirements have evolved over time and they vary between ... an adverse possessor to obtain title, their possession of the...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found

@ErikBjare Not necessarily. Either the git submodule update command failed or the make build command failed somehow, but we don’t know which one so we can’t know for sure. But it would at least help simplifying things since there’s one less potential issue.
Yeap, that fixed it.