Closed
Conversation
* Migrate from RabbitMQ/Celery to Django Q2 * Replace RabbitMQ/Celery with Django Q2 in deployment scripts and Docker configs * Make createcachetable idempotent in entrypoint script * test: add tests for setup_schedules management command - Add comprehensive tests for EXTRACTION_INTERVAL handling - Fix setup_schedules to read settings at runtime for testability - Add minute clamping to prevent invalid cron values * fix: improve test robustness and cache table creation - Use name-based assertion instead of positional indexing in tests - Fix misleading docstring about minute clamping - Explicitly create greedybear_cache table in entrypoint to match settings * refactor: Improve Django-Q schedule management and deployment - Separated schedule setup logic into greedybear/cronjobs/schedules.py - Added automatic cleanup of orphaned schedules from database - Simplified cache table creation (removed || true, uses Django idempotent command) - Fixed qcluster Docker health check to wait for uwsgi - Added validation: EXTRACTION_INTERVAL must be divisor of 60 - Fixed django-q2 version pinning (== instead of ~=) - Code cleanup: removed extra blank lines in tasks.py * chore: update django-q2 version to 1.9.0 in project requirements * fix: update service condition for uwsgi and enhance test mocks in setup_schedules tests * feat: add healthcheck for uwsgi service and adjust worker count in Q_CLUSTER * fix: disable RabbitMQ usage and enhance schedule management in setup_schedules * refactor: replace custom uWSGI healthcheck script with a simpler network check and increase healthcheck retries. * fix: remove unused healthcheck script for uwsgi service * chore: Add `__init__.py` to `tests/greedybear/management` to enable test discovery. * Fix log file ownership * Add exec before qcluster command to allow qcluster to shut down gracefully --------- Co-authored-by: tim <46972822+regulartim@users.noreply.github.com>
* feat(frontend): migrate from Create React App to Vite * fix: correct localStorage.getItem() argument order in Register.jsx * chore: update to v3.1.0 and align env vars with Vite migration * chore: clean up config per review - remove CRA proxy field, no-op rewrite function, and meta description tag * test: add Jest mock for environment.js to fix import.meta.env compatibility * fix(auth): confirmPassword is undefined error * final cleanup * revert some of the renaming as suggested
* chore(migration): migrate frontend tests from Jest to Vitest * fix(test): mock zustand to resolve version conflict with certego-ui * refactor(test): remove jest polyfill and use vi natively * fix(ci): remove duplicate input definition * fix(test): add missing coverage dependency * implemented maintainer feedback * fix(ci): remove undefined input use_jest * fix coverage report in CI --------- Co-authored-by: tim <46972822+regulartim@users.noreply.github.com>
) Bumps [slack-sdk](https://github.com/slackapi/python-slack-sdk) from 3.39.0 to 3.40.0. - [Release notes](https://github.com/slackapi/python-slack-sdk/releases) - [Commits](slackapi/python-slack-sdk@v3.39.0...v3.40.0) --- updated-dependencies: - dependency-name: slack-sdk dependency-version: 3.40.0 dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
* Add Enrichment Lookup component * run prettier * fix wrong field name for ioc Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com> * handle null values in expected_interactions Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com> * firehol_category -> firehol_categories Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com> * Fix enrichment error handling to use DRF error format * linter * test: add tests for Enrichment Lookup functionality * fix: changes requested in review; handle null values; fix typos; remove redundant loding state from button; * disable user input when not authenticated --------- Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Hey Matteo,
as new contributors always seem to fall into the same traps, I was thinking that maybe a more clearly structured PR template would help (them and us). Here it is. What do you think?
Description
Please include a short summary of the change. Don't just paste LLM output here.
Related issues
Please add related issues: the issues you are trying to solve as well as other issues that are important in the context of this pull request.
Type of change
Checklist
Please complete this checklist carefully. It helps guide your contribution and lets maintainers verify that all requirements are met.
Formalities
<feature name>. Closes #999develop.develop.Docs and tests
Ruff) gave 0 errors. If you have correctly installed pre-commit, it does these checks and adjustments on your behalf.GUI changes
Ignore this section if you did not make any changes to the GUI.
Review process