The newly introduced category feature in version 0.8.1 has a bug when creating a new category with no Rules (Type: None).
Steps to reproduce the behavior:
The pregiven categories (e.g. Media or Comms) don't have these issues. I would expect this category to behave like them, just an organizing category.
Problem can be solved by either deleting the whole category (obviously), setting a Rule that doesn't match anything (e.g. some big Hex-Number: "4BAB231F049AEA1D9") or setting a Regex Rule that also won't match anything but is a bit cleverer (e.g. ".^")
Red Banner on 'Activities' Tab:
Error: Request failed with status code 400. See dev console (F12) and/or server logs for more info.
Web Console:
Error: Request failed with status code 400
at t.exports (createError.js:16)
at t.exports (settle.js:17)
at XMLHttpRequest.h.onreadystatechange (xhr.js:59)
vue.runtime.esm.js:1888
Query options: {timeperiod: {鈥, host: "myPC", force: undefined, filterAFK: true}
activity_daily.ts:85
POST http://localhost:5600/api/0/query/ 400 (BAD REQUEST)
xhr.js:172
Linux Server Log:
Traceback (most recent call last):
File "aw_server/rest.py", line 244, in post
File "aw_server/api.py", line 245, in query2
File "site-packages/aw_query/query2.py", line 393, in query
File "site-packages/aw_query/query2.py", line 371, in interpret
File "site-packages/aw_query/query2.py", line 123, in interpret
File "site-packages/aw_query/query2.py", line 269, in interpret
File "site-packages/aw_query/query2.py", line 269, in interpret
File "site-packages/aw_query/query2.py", line 204, in interpret
File "site-packages/aw_query/query2.py", line 56, in interpret
aw_query.exceptions.QueryInterpretException: Tried to reference variable 'null' which is not defined
2019-11-18 19:06:19 [INFO ]: 400 (127.0.0.1): POST /api/0/query/ HTTP/1.1 (flask:25)
Thanks for reporting!
We noticed this ourselves a couple of days ago, and will be fixing it shortly. It might take a couple of weeks until there is a new release with the fix included, but we're on it :)
Great to hear!
As I've noted I have a temporary solution for the meantime.
Most helpful comment
Thanks for reporting!
We noticed this ourselves a couple of days ago, and will be fixing it shortly. It might take a couple of weeks until there is a new release with the fix included, but we're on it :)