Skip to content

feat: Add script execution on parallel batches with option script.executionBatchSize #2828

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged

Conversation

mtrezza
Copy link
Member

@mtrezza mtrezza commented May 27, 2025

New Pull Request Checklist

Issue Description

Closes: #2612

Approach

Add new option script.executionBatchSize that executes a script on all selected objects in parallel batches for reduced execution time.

TODOs before merging

  • Add changes to documentation (guides, repository pages, in-code descriptions)

Summary by CodeRabbit

  • New Features

    • Added support for batch execution of cloud code functions on selected objects, allowing multiple objects to be processed concurrently.
  • Enhancements

    • Improved summary notes after each batch and upon completion, providing clearer feedback on processed objects and errors.
    • Added documentation for configuring batch size in script execution with examples for better user guidance.

Copy link

parse-github-assistant bot commented May 27, 2025

🚀 Thanks for opening this pull request! We appreciate your effort in improving the project. Please let us know once your pull request is ready for review.

Copy link

coderabbitai bot commented May 27, 2025

Caution

Review failed

The pull request is closed.

📝 Walkthrough

"""

Walkthrough

The confirmExecuteScriptRows method in the Browser component was refactored to enable batch execution of a cloud code function on selected objects. The new implementation processes objects in configurable batch sizes, executes cloud functions concurrently within each batch, and provides detailed summary notes after processing.

Changes

File(s) Change Summary
src/dashboard/Data/Browser/Browser.react.js Refactored confirmExecuteScriptRows to support batch execution, concurrent processing, and summary notes.
README.md Added executionBatchSize configuration option documentation under apps.scripts with default and example.

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant Browser
    participant CloudFunction

    User->>Browser: Initiate confirmExecuteScriptRows(script)
    loop For each batch of selected objects
        Browser->>CloudFunction: Execute script concurrently on batch objects (Promise.all)
        CloudFunction-->>Browser: Return results/errors for batch
        Browser->>User: Show batch summary note
    end
    Browser->>User: Show final summary note
    Browser->>Browser: Refresh data
Loading

Assessment against linked issues

Objective Addressed Explanation
Add optional batch size configuration for scripts
Execute scripts in parallel batches
Provide summary notes after each batch and overall
Default batch size to 1 if not specified

Possibly related PRs

Warning

There were issues while running some tools. Please review the errors and either fix the tool's configuration or disable the tool if it's a critical failure.

🔧 ESLint

If the error stems from missing dependencies, add them to the package.json file. For unrecoverable errors (e.g., due to private dependencies), disable the tool in the CodeRabbit configuration.

npm error code ERR_SSL_WRONG_VERSION_NUMBER
npm error errno ERR_SSL_WRONG_VERSION_NUMBER
npm error request to https://10.0.0.28:4873/npm/-/npm-10.9.2.tgz failed, reason: C0CC0939B67F0000:error:0A00010B:SSL routines:ssl3_get_record:wrong version number:../deps/openssl/openssl/ssl/record/ssl3_record.c:354:
npm error
npm error A complete log of this run can be found in: /.npm/_logs/2025-06-01T15_16_05_910Z-debug-0.log


📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between e7e9566 and 0bb2ba3.

📒 Files selected for processing (2)
  • README.md (1 hunks)
  • src/dashboard/Data/Browser/Browser.react.js (1 hunks)

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share
🪧 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.
    • Explain this complex logic.
    • 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 explain this code block.
    • @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 explain its main purpose.
    • @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.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

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 sequence diagram to generate a sequence diagram of the changes in this PR.
  • @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.

@parseplatformorg
Copy link
Contributor

parseplatformorg commented May 27, 2025

🎉 Snyk checks have passed. No issues have been found so far.

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

Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 2

🧹 Nitpick comments (1)
src/dashboard/Data/Browser/Browser.react.js (1)

1612-1618: Consider reducing notification frequency to improve user experience.

The current implementation shows a notification for each object (success/error), plus batch summaries, plus a final summary. This could overwhelm users with a large number of notifications, especially for large selections.

Consider one of these approaches:

  1. Show only batch summaries and final summary (remove individual object notifications)
  2. Batch the individual notifications and show them less frequently
  3. Add a configuration option to control notification verbosity

For large-scale operations, users typically prefer summary information rather than detailed per-object feedback.

Also applies to: 1625-1625, 1630-1630

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between d21bd03 and e7e9566.

📒 Files selected for processing (1)
  • src/dashboard/Data/Browser/Browser.react.js (1 hunks)
⏰ Context from checks skipped due to timeout of 90000ms (1)
  • GitHub Check: Docker linux/amd64
🔇 Additional comments (3)
src/dashboard/Data/Browser/Browser.react.js (3)

1574-1574: LGTM: Good backward compatibility with configurable batch size.

The default batch size of 1 ensures backward compatibility while allowing users to configure parallel execution.


1587-1599: Excellent concurrent execution implementation.

The use of Promise.all for concurrent execution within batches is well-implemented. The error handling properly captures both successful responses and errors, allowing the batch to continue processing even if individual objects fail.

Also applies to: 1601-1601


1584-1627: Well-designed batch processing architecture.

The overall batch processing logic is sound:

  • Proper batch size handling
  • Good separation of concerns between batching and individual object processing
  • Comprehensive error tracking and reporting
  • Maintains backward compatibility

This implementation successfully enables parallel script execution while providing detailed progress feedback.

Copy link

uffizzi-cloud bot commented May 27, 2025

Uffizzi Ephemeral Environment deployment-63920

⌚ Updated May 27, 2025, 12:01 UTC

☁️ https://app.uffizzi.com/github.com/parse-community/parse-dashboard/pull/2828

📄 View Application Logs etc.

What is Uffizzi? Learn more

@mtrezza mtrezza merged commit cee8b8d into parse-community:alpha May 27, 2025
9 of 11 checks passed
parseplatformorg pushed a commit that referenced this pull request May 27, 2025
# [7.2.0-alpha.9](7.2.0-alpha.8...7.2.0-alpha.9) (2025-05-27)

### Features

* Add script execution on parallel batches with option `script.executionBatchSize` ([#2828](#2828)) ([cee8b8d](cee8b8d))
@parseplatformorg
Copy link
Contributor

🎉 This change has been released in version 7.2.0-alpha.9

@parseplatformorg parseplatformorg added the state:released-alpha Released as alpha version label May 27, 2025
@mtrezza mtrezza deleted the feat/add-script-batch-execution branch May 27, 2025 12:15
parseplatformorg pushed a commit that referenced this pull request Jun 1, 2025
# [7.2.0](7.1.0...7.2.0) (2025-06-01)

### Bug Fixes

* Data browser not scrolling to top when changing filter while cell selected ([#2821](#2821)) ([c2527dc](c2527dc))
* Data browser table shows loading indicator when info panel is loading ([#2782](#2782)) ([da57e5e](da57e5e))
* Improperly aligned unfolding sub-items in context menu in data browser ([#2726](#2726)) ([3fed292](3fed292))
* Notifications fade out erratically when executing a script on large number of rows ([#2822](#2822)) ([3891381](3891381))
* Pagination does not reset to page 1 when clicking on class or filter ([#2798](#2798)) ([29d1447](29d1447))
* Saving new filter in data browser overwrites filters added in other dashboard instances ([#2769](#2769)) ([46bc154](46bc154))
* Selecting a saved filter in data browser may highlight a different filter ([#2783](#2783)) ([4c6e853](4c6e853))

### Features

* Add confirmation dialog before saving a Cloud Config parameter that has been modified since editing it ([#2770](#2770)) ([adb9b5c](adb9b5c))
* Add custom CSS styling for info panel items ([#2788](#2788)) ([f031e5d](f031e5d))
* Add relative date filter in data browser for date constraints relative to when the query is run ([#2736](#2736)) ([d9dfd69](d9dfd69))
* Add script execution on parallel batches with option `script.executionBatchSize` ([#2828](#2828)) ([cee8b8d](cee8b8d))
* Keyboard Enter key can be used to select item in data browser filter dialog field dropdown ([#2771](#2771)) ([dc14710](dc14710))
@parseplatformorg
Copy link
Contributor

🎉 This change has been released in version 7.2.0

@parseplatformorg parseplatformorg added the state:released Released as stable version label Jun 1, 2025
beiguancyc pushed a commit to beiguancyc/parse-dashboard that referenced this pull request Jun 3, 2025
* source: (64 commits)
  chore(release): 7.2.0 [skip ci]
  empty commit to trigger CI
  refactor: Bump @babel/plugin-transform-runtime from 7.27.1 to 7.27.3 (parse-community#2834)
  refactor: Bump @babel/runtime from 7.27.1 to 7.27.3 (parse-community#2833)
  refactor: Bump eslint-plugin-jest from 28.11.0 to 28.12.0 (parse-community#2835)
  refactor: Bump inquirer from 12.6.1 to 12.6.3 (parse-community#2830)
  refactor: Bump @babel/runtime-corejs3 from 7.27.1 to 7.27.3 (parse-community#2832)
  refactor: Bump semver from 7.5.2 to 7.7.2 (parse-community#2827)
  refactor: Bump @semantic-release/github from 11.0.2 to 11.0.3 (parse-community#2826)
  chore(release): 7.2.0-alpha.9 [skip ci]
  feat: Add script execution on parallel batches with option `script.executionBatchSize` (parse-community#2828)
  refactor: Bump sass from 1.87.0 to 1.89.0 (parse-community#2824)
  refactor: Bump webpack from 5.99.8 to 5.99.9 (parse-community#2823)
  refactor: Bump marked from 15.0.11 to 15.0.12 (parse-community#2825)
  chore(release): 7.2.0-alpha.8 [skip ci]
  fix: Notifications fade out erratically when executing a script on large number of rows (parse-community#2822)
  chore(release): 7.2.0-alpha.7 [skip ci]
  fix: Data browser not scrolling to top when changing filter while cell selected (parse-community#2821)
  refactor: Bump core-js from 3.41.0 to 3.42.0 (parse-community#2817)
  refactor: Bump puppeteer from 24.6.1 to 24.9.0 (parse-community#2818)
  ...
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
state:released Released as stable version state:released-alpha Released as alpha version
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Execute script in parallel or serial
2 participants