github-germ
github-germ
2.4.114 could the same root cause be causing `ExpandedPyMisp.update_tag` connected with an authkey of a user with a role which has `Tag Editor Granted` be causing this error? ``` 20190913-18:16:55...
Also, when using `PyMISP.edit_tag` with the same code and authkey as above, the tag revision succeeded without error. Am I doing something wrong with the newer `ExpandedPyMisp.update_tag` method or perhaps...
Anybody have a chance to look at this? Thanks...
Might this have been fixed in 2.4.159? If not, we'd appreciate any help to resolve. Thanks.
Still seeing this with 2.4.162. Any insight is appreciated to help find root cause. Thanks,
The second attempt via the WebUI click to build with the new engine failed this time * after 18 hours * with progress=2 * 2.6M `default_correlations` rows * 950k `correlation_values`...
Hmmm, I thought we could still enable the legacy correlation engine with 2.4.160; however, perhaps I'm missing the HOWTO or it isn't possible. Don't see it in the WebUI nor...
Thanks. I will build from `develop`, try again, and report back.
I'm likely missing something. I built from `develop` and launched. I do not see a newly auto started `job_type: generate correlation` in the db `jobs` table; nor do I see...
Aha, the endpoint `/servers/serverSettings/correlations` works; however, the new `Correlations` top menu entry that was seen in the `v2.4.160` tagged branch is not there in `develop`. OK... rebuilding with the new...