Update serializers.py

[gitworkflows]

User description

(Please add to the PR name the issue/s that this PR would close if merged by using a Github keyword. Example: <feature name>. Closes #999. If your PR is made by a single commit, please add that clause in the commit too. This is all required to automate the closure of related issues.)

Description

Please include a summary of the change and link to the related issue.

Type of change

Please delete options that are not relevant.

• Bug fix (non-breaking change which fixes an issue).
• New feature (non-breaking change which adds functionality).
• Breaking change (fix or feature that would cause existing functionality to not work as expected).

Checklist

• I have read and understood the rules about how to Contribute to this project
• The pull request is for the branch develop
• A new plugin (analyzer, connector, visualizer, playbook, pivot or ingestor) was added or changed, in which case:
  • I strictly followed the documentation "How to create a Plugin"
  • Usage file was updated.
  • Advanced-Usage was updated (in case the plugin provides additional optional configuration).
  • I have dumped the configuration from Django Admin using the dumpplugin command and added it in the project as a data migration. ("How to share a plugin with the community")
  • If a File analyzer was added and it supports a mimetype which is not already supported, you added a sample of that type inside the archive test_files.zip and you added the default tests for that mimetype in test_classes.py.
  • If you created a new analyzer and it is free (does not require any API key), please add it in the FREE_TO_USE_ANALYZERS playbook by following this guide.
  • Check if it could make sense to add that analyzer/connector to other freely available playbooks.
  • I have provided the resulting raw JSON of a finished analysis and a screenshot of the results.
  • If the plugin interacts with an external service, I have created an attribute called precisely url that contains this information. This is required for Health Checks.
  • If the plugin requires mocked testing, _monkeypatch() was used in its class to apply the necessary decorators.
  • I have added that raw JSON sample to the MockUpResponse of the _monkeypatch() method. This serves us to provide a valid sample for testing.
• If external libraries/packages with restrictive licenses were used, they were added in the Legal Notice section.
• Linters (Black, Flake, Isort) gave 0 errors. If you have correctly installed pre-commit, it does these checks and adjustments on your behalf.
• I have added tests for the feature/bug I solved (see tests folder). All the tests (new and old ones) gave 0 errors.
• If changes were made to an existing model/serializer/view, the docs were updated and regenerated (check CONTRIBUTE.md).
• If the GUI has been modified:
  • I have a provided a screenshot of the result in the PR.
  • I have created new frontend tests for the new component or updated existing ones.
• After you had submitted the PR, if DeepSource, Django Doctors or other third-party linters have triggered any alerts during the CI checks, I have solved those alerts.

Important Rules

• If you miss to compile the Checklist properly, your PR won't be reviewed by the maintainers.
• Everytime you make changes to the PR and you think the work is done, you should explicitly ask for a review. After being reviewed and received a "change request", you should explicitly ask for a review again once you have made the requested changes.

---

PR Type

Enhancement

---

Description

• Simplified the analyzer configuration serialization by removing the plugin_config handling and related methods
• Replaced plugin_config field with direct parameters serialization using ParameterSerializer
• Added to_representation method to include serialized parameters in the output
• Removed unnecessary PluginConfig model dependency

---

Changes walkthrough 📝

	Relevant files
Enhancement	serializers.py Refactor analyzer config serialization to use parameters  api_app/analyzers_manager/serializers.py Removed PluginConfig import and replaced with ParameterSerializer Removed plugin_config field and related create/update methods from AnalyzerConfigSerializer Added to_representation method to include parameters in serialized output +7/-36

---

💡 PR-Agent usage: Comment /help "your question" on any pull request to receive relevant information

[sourcery-ai]

Reviewer's Guide by Sourcery

This PR removes the "plugin_config" field from the "AnalyzerConfigSerializer" and adds a "to_representation" method to include the "parameters" field in the serialized output. It also removes the create and update methods from the serializer.

Sequence diagram showing updated serialization flow

sequenceDiagram
    participant C as Client
    participant S as AnalyzerConfigSerializer
    participant M as Model

    C->>S: Request serialized data
    S->>M: Get instance data
    M-->>S: Return instance data
    S->>M: Get parameters
    M-->>S: Return parameters
    Note over S: Serialize parameters
    S-->>C: Return serialized data with parameters

Loading

Class diagram showing changes to AnalyzerConfigSerializer

classDiagram
    class PythonConfigSerializer {
        +Meta
    }
    class AnalyzerConfigSerializer {
        -plugin_config: ListField [Removed]
        +python_module: SlugRelatedField
        +Meta
        -create(validated_data) [Removed]
        -update(instance, validated_data) [Removed]
        +to_representation(instance)
    }
    class AnalyzerConfigSerializerForMigration

    PythonConfigSerializer <|-- AnalyzerConfigSerializer
    PythonConfigSerializerForMigration --|> PythonConfigSerializer

    note for AnalyzerConfigSerializer "Removed plugin_config handling
Added parameters serialization"

Loading

File-Level Changes

Change	Details	Files
Removed the "plugin_config" field and associated create/update logic.	Removed the "plugin_config" field from the "AnalyzerConfigSerializer". Removed the create and update methods from the "AnalyzerConfigSerializer" which handled the creation and updating of plugin configurations.	api_app/analyzers_manager/serializers.py
Added a "to_representation" method to include parameters.	Added a "to_representation" method to the "AnalyzerConfigSerializer". The "to_representation" method now includes the serialized "parameters" data in the output.	api_app/analyzers_manager/serializers.py

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time. You can also use
  this command to specify where the summary should be inserted.

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR. (Beta)
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[gitworkflows]

⛔ Snyk checks have failed. 11 issues have been found so far.

Icon	Severity	Issues
	Critical	0
	High	11
	Medium	0
	Low	0

⛔ security/snyk check is complete. 11 issues have been found. (View Details)

[codiumai-pr-agent-free]

PR Reviewer Guide 🔍

Here are some key observations to aid the review process:

⏱️ Estimated effort to review: 2 🔵🔵⚪⚪⚪

🧪 No relevant tests

🔒 No security concerns identified

⚡ Recommended focus areas for review Data Validation The to_representation method does not handle the case where parameters might be None or empty. Consider adding validation or default empty list. def to_representation(self, instance): result = super().to_representation(instance) parameters = ParameterSerializer(instance.parameters, many=True) result["parameters"] = parameters.data return result

[deepsource-io]

Here's the code health analysis summary for commits b66de02..6191f4b. View details on DeepSource ↗.

Analysis Summary

Analyzer	Status	Summary	Link
Python	❌ Failure	❗ 49 occurences introduced 🎯 16 occurences resolved	View Check ↗
Docker	✅ Success		View Check ↗

---

💡 If you’re a repository administrator, you can configure the quality gates from the settings.

[codiumai-pr-agent-free]

PR Code Suggestions ✨

Explore these optional code suggestions:

Category	Suggestion	Score
Possible issue	Add defensive programming to handle potential None or missing attributes when serializing data Add error handling for the case when instance.parameters is None or invalid to prevent potential runtime errors in the to_representation method. api_app/analyzers_manager/serializers.py [39-43] def to_representation(self, instance): result = super().to_representation(instance) - parameters = ParameterSerializer(instance.parameters, many=True) - result["parameters"] = parameters.data + if hasattr(instance, 'parameters') and instance.parameters is not None: + parameters = ParameterSerializer(instance.parameters, many=True) + result["parameters"] = parameters.data + else: + result["parameters"] = [] return result Apply this suggestion Suggestion importance[1-10]: 8 Why: The suggestion addresses a critical defensive programming issue that could prevent runtime errors when dealing with None or missing parameters, which is essential for robust API functionality.	8
General	Validate serialized data to ensure data integrity and proper error reporting Consider validating the parameters data before serialization to ensure data integrity and prevent invalid parameter configurations. api_app/analyzers_manager/serializers.py [39-43] def to_representation(self, instance): result = super().to_representation(instance) - parameters = ParameterSerializer(instance.parameters, many=True) - result["parameters"] = parameters.data + try: + parameters = ParameterSerializer(instance.parameters, many=True) + parameters.is_valid(raise_exception=True) + result["parameters"] = parameters.data + except Exception as e: + result["parameters"] = [] + result["parameter_errors"] = str(e) return result Apply this suggestion Suggestion importance[1-10]: 4 Why: While error handling is good, calling is_valid() on already serialized data is unnecessary as ParameterSerializer would have already validated the data during instantiation. The suggestion adds unnecessary complexity.	4

[sourcery-ai]

Hey @gitworkflows - I've reviewed your changes - here's some feedback:

Overall Comments:

• Please provide a detailed description of why this change is needed and what problem it solves. The current PR title and description are too vague.
• This appears to be a breaking change since it removes plugin configuration functionality. Please explain where this functionality is being moved to and update the 'Type of change' section accordingly.

Here's what I looked at during the review

• 🟢 General issues: all looks good
• 🟢 Security: all looks good
• 🟢 Testing: all looks good
• 🟢 Complexity: all looks good
• 🟢 Documentation: all looks good

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}

[codiumai-pr-agent-free]

CI Failure Feedback 🧐

(Checks updated until commit 6191f4b)

Action: dependency-review

Failed stage: Dependency Review [❌]

Failure summary: The action failed due to two critical issues: 1. A critical security vulnerability was detected in shell-quote@1.7.2 package (Improper Neutralization of Special Elements used in a Command) 2. Multiple npm packages have OpenSSF Scorecard scores below the repository's minimum threshold of 3.0, including: - @isaacs/string-locale-compare (1.7) - hash.js (1.4) - json-parse-better-errors (1.9) - And several other packages with scores between 1.4-2.9

Relevant error logs: 1: ##[group]Operating System 2: Ubuntu ... 98: '1c365f27e80709d6dfaa60ad3e6834459dcf246c' 99: ##[group]Run actions/dependency-review-action@v4 100: with: 101: repo-token: *** 102: ##[endgroup] 103: ##[group]Vulnerabilities 104: �[1mfrontend/package-lock.json » shell-quote@1.7.2�[22m – Improper Neutralization of Special Elements used in a Command in Shell-quote �[31m(critical severity)�[39m 105: ↪ https://github.com/advisories/GHSA-g4rg-993r-mgx7 106: ##[error]Dependency review detected vulnerable packages. ... 261: npm/@types/yargs: OpenSSF Scorecard Score: 7 262: npm/@typescript-eslint/eslint-plugin: OpenSSF Scorecard Score: 5.4 263: npm/@typescript-eslint/parser: OpenSSF Scorecard Score: 5.4 264: npm/@typescript-eslint/typescript-estree: OpenSSF Scorecard Score: 5.4 265: �[31mnpm/@webassemblyjs/ast: OpenSSF Scorecard Score: 2.8�[39m 266: npm/@webassemblyjs/ast: OpenSSF Scorecard Score: 2.8 267: �[31mnpm/@webassemblyjs/floating-point-hex-parser: OpenSSF Scorecard Score: 2.8�[39m 268: npm/@webassemblyjs/floating-point-hex-parser: OpenSSF Scorecard Score: 2.8 269: �[31mnpm/@webassemblyjs/helper-api-error: OpenSSF Scorecard Score: 2.8�[39m 270: npm/@webassemblyjs/helper-api-error: OpenSSF Scorecard Score: 2.8 ... 305: �[31mnpm/acorn-dynamic-import: OpenSSF Scorecard Score: 1.9�[39m 306: npm/acorn-dynamic-import: OpenSSF Scorecard Score: 1.9 307: npm/acorn-globals: OpenSSF Scorecard Score: 4.1 308: npm/acorn-walk: OpenSSF Scorecard Score: 5.4 309: npm/address: OpenSSF Scorecard Score: 4.3 310: npm/agent-base: OpenSSF Scorecard Score: 4.4 311: �[31mnpm/agent-base: OpenSSF Scorecard Score: 2.7�[39m 312: npm/agent-base: OpenSSF Scorecard Score: 2.7 313: npm/ajv-errors: OpenSSF Scorecard Score: undefined ... 806: npm/jest-watch-typeahead: OpenSSF Scorecard Score: 4.4 807: npm/jest-watcher: OpenSSF Scorecard Score: undefined 808: npm/jest-worker: OpenSSF Scorecard Score: undefined 809: npm/js-tokens: OpenSSF Scorecard Score: 3.5 810: npm/jsbn: OpenSSF Scorecard Score: 3.1 811: npm/jsbn: OpenSSF Scorecard Score: 3.1 812: npm/jsdom: OpenSSF Scorecard Score: 6.9 813: npm/jsdom: OpenSSF Scorecard Score: 6.9 814: �[31mnpm/json-parse-better-errors: OpenSSF Scorecard Score: 1.9�[39m 815: npm/json-parse-better-errors: OpenSSF Scorecard Score: 1.9 816: npm/json-parse-even-better-errors: OpenSSF Scorecard Score: 6.1 ... 1100: npm/postcss-svgo: OpenSSF Scorecard Score: 6.3 1101: npm/postcss-unique-selectors: OpenSSF Scorecard Score: 6.3 1102: �[31mnpm/postcss-value-parser: OpenSSF Scorecard Score: 2.4�[39m 1103: npm/postcss-value-parser: OpenSSF Scorecard Score: 2.4 1104: �[31mnpm/postcss-values-parser: OpenSSF Scorecard Score: 2.3�[39m 1105: npm/postcss-values-parser: OpenSSF Scorecard Score: 2.3 1106: �[31mnpm/prelude-ls: OpenSSF Scorecard Score: 1.9�[39m 1107: npm/prelude-ls: OpenSSF Scorecard Score: 1.9 1108: npm/pretty-error: OpenSSF Scorecard Score: 3.1 ... 1337: npm/util: OpenSSF Scorecard Score: 4.3 1338: npm/util.promisify: OpenSSF Scorecard Score: 5.2 1339: npm/util.promisify: OpenSSF Scorecard Score: 5.2 1340: npm/uuid: OpenSSF Scorecard Score: 5.6 1341: npm/uuid: OpenSSF Scorecard Score: 5.6 1342: npm/validate-npm-package-license: OpenSSF Scorecard Score: 3.4 1343: npm/validate-npm-package-name: OpenSSF Scorecard Score: 6.3 1344: npm/vendors: OpenSSF Scorecard Score: 3.1 1345: npm/verror: OpenSSF Scorecard Score: undefined ... 1404: ##[warning]npm/ip has an OpenSSF Scorecard of 2.8, which is less than this repository's threshold of 3. 1405: ##[warning]npm/node-notifier has an OpenSSF Scorecard of 2.8, which is less than this repository's threshold of 3. 1406: ##[warning]npm/@babel/preset-modules has an OpenSSF Scorecard of 2.9, which is less than this repository's threshold of 3. 1407: ##[warning]npm/@bcoe/v8-coverage has an OpenSSF Scorecard of 2.4, which is less than this repository's threshold of 3. 1408: ##[warning]npm/@isaacs/string-locale-compare has an OpenSSF Scorecard of 1.7, which is less than this repository's threshold of 3. 1409: ##[warning]npm/@mrmlnc/readdir-enhanced has an OpenSSF Scorecard of 2.7, which is less than this repository's threshold of 3. 1410: ##[warning]npm/@webassemblyjs/ast has an OpenSSF Scorecard of 2.8, which is less than this repository's threshold of 3. 1411: ##[warning]npm/@webassemblyjs/floating-point-hex-parser has an OpenSSF Scorecard of 2.8, which is less than this repository's threshold of 3. 1412: ##[warning]npm/@webassemblyjs/helper-api-error has an OpenSSF Scorecard of 2.8, which is less than this repository's threshold of 3. ... 1460: ##[warning]npm/growly has an OpenSSF Scorecard of 2.7, which is less than this repository's threshold of 3. 1461: ##[warning]npm/hash.js has an OpenSSF Scorecard of 1.4, which is less than this repository's threshold of 3. 1462: ##[warning]npm/hmac-drbg has an OpenSSF Scorecard of 2.6, which is less than this repository's threshold of 3. 1463: ##[warning]npm/icss-replace-symbols has an OpenSSF Scorecard of 1.9, which is less than this repository's threshold of 3. 1464: ##[warning]npm/icss-utils has an OpenSSF Scorecard of 1.9, which is less than this repository's threshold of 3. 1465: ##[warning]npm/iferr has an OpenSSF Scorecard of 2.7, which is less than this repository's threshold of 3. 1466: ##[warning]npm/is-cidr has an OpenSSF Scorecard of 2.6, which is less than this repository's threshold of 3. 1467: ##[warning]npm/is-resolvable has an OpenSSF Scorecard of 1.7, which is less than this repository's threshold of 3. 1468: ##[warning]npm/json-parse-better-errors has an OpenSSF Scorecard of 1.9, which is less than this repository's threshold of 3. ... 1686: �[32m+ @types/stack-utils@1.0.1�[39m 1687: �[32m+ @types/stack-utils@2.0.1�[39m 1688: �[32m+ @types/yargs@13.0.12�[39m 1689: �[32m+ @typescript-eslint/eslint-plugin@1.6.0�[39m 1690: �[32m+ @typescript-eslint/parser@1.6.0�[39m 1691: �[32m+ @typescript-eslint/typescript-estree@1.6.0�[39m 1692: �[32m+ @webassemblyjs/ast@1.8.5�[39m 1693: �[32m+ @webassemblyjs/floating-point-hex-parser@1.8.5�[39m 1694: �[32m+ @webassemblyjs/helper-api-error@1.8.5�[39m ... 1712: �[32m+ acorn@6.4.2�[39m 1713: �[32m+ acorn@5.7.4�[39m 1714: �[32m+ acorn-dynamic-import@4.0.0�[39m 1715: �[32m+ acorn-globals@4.3.4�[39m 1716: �[32m+ acorn-walk@6.2.0�[39m 1717: �[32m+ address@1.1.2�[39m 1718: �[32m+ agent-base@7.1.3�[39m 1719: �[32m+ agent-base@6.0.2�[39m 1720: �[32m+ ajv-errors@1.0.1�[39m ... 2175: �[32m+ jest-watch-typeahead@0.3.0�[39m 2176: �[32m+ jest-watcher@24.9.0�[39m 2177: �[32m+ jest-worker@24.9.0�[39m 2178: �[32m+ js-tokens@3.0.2�[39m 2179: �[32m+ jsbn@1.1.0�[39m 2180: �[32m+ jsbn@0.1.1�[39m 2181: �[32m+ jsdom@11.12.0�[39m 2182: �[32m+ jsdom@14.1.0�[39m 2183: �[32m+ json-parse-better-errors@1.0.2�[39m 2184: �[32m+ json-parse-even-better-errors@4.0.0�[39m ... 2440: �[32m+ postcss-selector-parser@3.1.2�[39m 2441: �[32m+ postcss-selector-parser@5.0.0�[39m 2442: �[32m+ postcss-selector-parser@6.1.2�[39m 2443: �[32m+ postcss-svgo@4.0.3�[39m 2444: �[32m+ postcss-unique-selectors@4.0.1�[39m 2445: �[32m+ postcss-value-parser@3.3.1�[39m 2446: �[32m+ postcss-values-parser@2.0.1�[39m 2447: �[32m+ prelude-ls@1.1.2�[39m 2448: �[32m+ pretty-error@2.1.2�[39m ... 2654: �[32m+ util@0.10.4�[39m 2655: �[32m+ util.promisify@1.1.3�[39m 2656: �[32m+ util.promisify@1.0.0�[39m 2657: �[32m+ uuid@3.4.0�[39m 2658: �[32m+ uuid@8.3.2�[39m 2659: �[32m+ validate-npm-package-license@3.0.4�[39m 2660: �[32m+ validate-npm-package-name@6.0.0�[39m 2661: �[32m+ vendors@1.0.4�[39m 2662: �[32m+ verror@1.10.0�[39m ... 2710: �[32m+ y18n@5.0.8�[39m 2711: �[32m+ y18n@4.0.3�[39m 2712: �[32m+ yallist@5.0.0�[39m 2713: �[32m+ yargs@12.0.2�[39m 2714: �[32m+ yargs@13.3.2�[39m 2715: �[32m+ yargs-parser@20.2.9�[39m 2716: �[32m+ yargs-parser@13.1.2�[39m 2717: �[31m- @alloc/quick-lru@5.2.0�[39m 2718: �[31m- @apideck/better-ajv-errors@0.3.6�[39m ... 2822: �[31m- @types/connect-history-api-fallback@1.5.0�[39m 2823: �[31m- @types/eslint@8.44.1�[39m 2824: �[31m- @types/eslint-scope@3.7.4�[39m 2825: �[31m- @types/estree@1.0.1�[39m 2826: �[31m- @types/estree@0.0.39�[39m 2827: �[31m- @types/express@4.17.17�[39m 2828: �[31m- @types/express-serve-static-core@4.17.35�[39m 2829: �[31m- @types/html-minifier-terser@6.1.0�[39m 2830: �[31m- @types/http-errors@2.0.1�[39m ... 2853: �[31m- @typescript-eslint/scope-manager@5.62.0�[39m 2854: �[31m- @typescript-eslint/type-utils@5.62.0�[39m 2855: �[31m- @typescript-eslint/types@5.62.0�[39m 2856: �[31m- @typescript-eslint/typescript-estree@5.62.0�[39m 2857: �[31m- @typescript-eslint/utils@5.62.0�[39m 2858: �[31m- @typescript-eslint/visitor-keys@5.62.0�[39m 2859: �[31m- @webassemblyjs/ast@1.11.6�[39m 2860: �[31m- @webassemblyjs/floating-point-hex-parser@1.11.6�[39m 2861: �[31m- @webassemblyjs/helper-api-error@1.11.6�[39m ... 3194: �[31m- postcss-preset-env@7.8.3�[39m 3195: �[31m- postcss-pseudo-class-any-link@7.1.6�[39m 3196: �[31m- postcss-reduce-initial@5.1.2�[39m 3197: �[31m- postcss-reduce-transforms@5.1.0�[39m 3198: �[31m- postcss-replace-overflow-wrap@4.0.0�[39m 3199: �[31m- postcss-selector-not@6.0.1�[39m 3200: �[31m- postcss-svgo@5.1.0�[39m 3201: �[31m- postcss-unique-selectors@5.1.1�[39m 3202: �[31m- pretty-error@4.0.0�[39m ... 3330: �[31m- yargs@16.2.0�[39m 3331: �[31m- yargs-parser@20.2.9�[39m 3332: File: �[1mfrontend/package.json�[22m 3333: �[32m+ npm@^11.0.0�[39m 3334: �[32m+ react-scripts@^3.0.1�[39m 3335: �[31m- react-scripts@^5.0.1�[39m 3336: ##[endgroup] 3337: ##[endgroup] 3338: ##[error]$GITHUB_STEP_SUMMARY upload aborted, supports content up to a size of 1024k, got 1943k. For more information see: https://docs.github.com/actions/using-workflows/workflow-commands-for-github-actions#adding-a-markdown-summary

---

✨ CI feedback usage guide:

---

The CI feedback tool (/checks) automatically triggers when a PR has a failed check.
The tool analyzes the failed checks and provides several feedbacks:

• Failed stage
• Failed test name
• Failure summary
• Relevant error logs

In addition to being automatically triggered, the tool can also be invoked manually by commenting on a PR:

/checks "https://github.com/{repo_name}/actions/runs/{run_number}/job/{job_number}"

where {repo_name} is the name of the repository, {run_number} is the run number of the failed check, and {job_number} is the job number of the failed check.

Configuration options

• enable_auto_checks_feedback - if set to true, the tool will automatically provide feedback when a check is failed. Default is true.
• excluded_checks_list - a list of checks to exclude from the feedback, for example: ["check1", "check2"]. Default is an empty list.
• enable_help_text - if set to true, the tool will provide a help message with the feedback. Default is true.
• persistent_comment - if set to true, the tool will overwrite a previous checks comment with the new feedback. Default is true.
• final_update_message - if persistent_comment is true and updating a previous checks message, the tool will also create a new message: "Persistent checks updated to latest commit". Default is true.

See more information about the checks tool in the docs.