You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@texera.apache.org by "juliethecao (via GitHub)" <gi...@apache.org> on 2026/06/03 07:13:21 UTC

[PR] feat(comment-commands): auto-assign reviewer on request-review no args command [texera]

juliethecao opened a new pull request, #5359:
URL: https://github.com/apache/texera/pull/5359

   <!--
   Thanks for sending a pull request (PR)! Here are some tips for you:
     1. If this is your first time, please read our contributor guidelines: 
        [Contributing to Texera](https://github.com/apache/texera/blob/main/CONTRIBUTING.md)
     2. Ensure you have added or run the appropriate tests for your PR
     3. If the PR is work in progress, mark it a draft on GitHub.
     4. Please write your PR title to summarize what this PR proposes, we 
       are following Conventional Commits style for PR titles as well.
     5. Be sure to keep the PR description updated to reflect all changes.
   -->
   
   ### What changes were proposed in this PR?
   <!--
   Please clarify what changes you are proposing. The purpose of this section 
   is to outline the changes. Here are some tips for you:
     1. If you propose a new API, clarify the use case for a new API.
     2. If you fix a bug, you can clarify why it is a bug.
     3. If it is a refactoring, clarify what has been changed.
     3. It would be helpful to include a before-and-after comparison using 
        screenshots or GIFs.
     4. Please consider writing useful notes for better and faster reviews.
   -->
   Extends the `/request-review` comment command in `.github/workflows/comment-commands.yml`
   so that when called with **no `@mention` arguments**, it automatically identifies reviewers
   via `git blame` on the PR's changed files, rather than requiring the author to name someone
   explicitly.
   
   `/request-review` with no arguments runs `git blame -p <base-sha>` on each
   changed file, finds the most recent commit author per file, resolves their GitHub login,
   and calls `requestReviewers` — filtering out the PR author, bots, and accounts with no
   linked GitHub login.
   
   This makes `/request-review` a zero-configuration entry point for contributors unfamiliar
   with who owns a given area of the codebase.
   
   ### Any related issues, documentation, discussions?
   <!--
   Please use this section to link other resources if not mentioned already.
     1. If this PR fixes an issue, please include `Fixes #1234`, `Resolves #1234`
        or `Closes #1234`. If it is only related, simply mention the issue number.
     2. If there is design documentation, please add the link.
     3. If there is a discussion in the mailing list, please add the link.
   -->
   Closes #5244
   
   
   ### How was this PR tested?
   <!--
   If tests were added, say they were added here. Or simply mention that if the PR 
   is tested with existing test cases.  Make sure to include/update test cases that
   check the changes thoroughly including negative and positive cases if possible.
   If it was tested in a way different from regular unit tests, please clarify how
   you tested step by step, ideally copy and paste-able, so that other reviewers can
   test and check, and descendants can verify in the future. If tests were not added, 
   please describe why they were not added and/or why it was difficult to add. 
   -->
   Unit tests for the blame-parsing and reviewer-selection logic were written and run locally.
   The test file covers:
   
   - **Basic blame parsing**: `latestBlameCommit` picks the commit with the highest
     `author-time` across multiple blamed blocks
   - **Missing `author-time`**: returns `null` when the field is absent; file is skipped
   - **All files produce reviewers**: three files with distinct authors and a non-overlapping
     PR author returns all three logins
   - **PR author filtered**: a file whose blame points to the PR author is excluded
   - **Case-insensitive author filter**: `Alice` vs `alice` is treated as the same person
   - **Bot commits filtered**: accounts with `type: 'Bot'` are excluded
   - **Blame throws (new file at base)**: a file absent at the base SHA is skipped; other
     files still contribute reviewers
   - **All candidates filtered**: when every blame candidate is the PR author, returns `[]`
   
   End-to-end verification was done by opening a test PR on the fork and commenting
   `/request-review` with no arguments; the workflow run successfully called
   `requestReviewers` with the blame-detected login.
   
   Test file and run results via test PR: [`test-request-review-no-args`](https://github.com/juliethecao/texera/pull/3)
   
   
   ### Was this PR authored or co-authored using generative AI tooling?
   <!--
   If generative AI tooling has been used in the process of authoring this PR, 
   please include the phrase: 'Generated-by: ' followed by the name of the tool 
   and its version. If no, write 'No'. 
   Please refer to the [ASF Generative Tooling Guidance](https://www.apache.org/legal/generative-tooling.html) for details.
   -->
   Co-authored with Claude Sonnet 4.6 in compliance with ASF guidelines


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscribe@texera.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Re: [PR] feat(comment-commands): auto-assign reviewer on request-review no args command [texera]

Posted by "Ma77Ball (via GitHub)" <gi...@apache.org>.
Ma77Ball commented on PR #5359:
URL: https://github.com/apache/texera/pull/5359#issuecomment-4634109475

   /request-review @Yicong-Huang 


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscribe@texera.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Re: [PR] feat(comment-commands): auto-assign reviewer on request-review no args command [texera]

Posted by "juliethecao (via GitHub)" <gi...@apache.org>.
juliethecao commented on PR #5359:
URL: https://github.com/apache/texera/pull/5359#issuecomment-4609973987

   /request-review @Ma77Ball


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscribe@texera.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Re: [PR] feat(comment-commands): auto-assign reviewer on request-review no args command [texera]

Posted by "juliethecao (via GitHub)" <gi...@apache.org>.
juliethecao closed pull request #5359: feat(comment-commands): auto-assign reviewer on request-review no args command
URL: https://github.com/apache/texera/pull/5359


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscribe@texera.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Re: [PR] feat(comment-commands): auto-assign reviewer on request-review no args command [texera]

Posted by "codecov-commenter (via GitHub)" <gi...@apache.org>.
codecov-commenter commented on PR #5359:
URL: https://github.com/apache/texera/pull/5359#issuecomment-4610021365

   ## [Codecov](https://app.codecov.io/gh/apache/texera/pull/5359?dropdown=coverage&src=pr&el=h1&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=apache) Report
   :white_check_mark: All modified and coverable lines are covered by tests.
   :white_check_mark: Project coverage is 51.32%. Comparing base ([`23c5fd2`](https://app.codecov.io/gh/apache/texera/commit/23c5fd2c13936e43c5094c041650c7c041fe9b22?dropdown=coverage&el=desc&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=apache)) to head ([`a46579c`](https://app.codecov.io/gh/apache/texera/commit/a46579c167cf6ff0c89716b46443f9a4909eea23?dropdown=coverage&el=desc&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=apache)).
   
   <details><summary>Additional details and impacted files</summary>
   
   
   
   ```diff
   @@            Coverage Diff            @@
   ##               main    #5359   +/-   ##
   =========================================
     Coverage     51.32%   51.32%           
     Complexity     2416     2416           
   =========================================
     Files          1054     1054           
     Lines         40918    40918           
     Branches       4381     4381           
   =========================================
     Hits          21002    21002           
     Misses        18695    18695           
     Partials       1221     1221           
   ```
   
   | [Flag](https://app.codecov.io/gh/apache/texera/pull/5359/flags?src=pr&el=flags&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=apache) | Coverage Δ | | *Carryforward flag |
   |---|---|---|---|
   | [access-control-service](https://app.codecov.io/gh/apache/texera/pull/5359/flags?src=pr&el=flag&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=apache) | `41.89% <ø> (ø)` | | Carriedforward from [23c5fd2](https://app.codecov.io/gh/apache/texera/commit/23c5fd2c13936e43c5094c041650c7c041fe9b22?utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=apache) |
   | [agent-service](https://app.codecov.io/gh/apache/texera/pull/5359/flags?src=pr&el=flag&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=apache) | `33.76% <ø> (ø)` | | Carriedforward from [23c5fd2](https://app.codecov.io/gh/apache/texera/commit/23c5fd2c13936e43c5094c041650c7c041fe9b22?utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=apache) |
   | [amber](https://app.codecov.io/gh/apache/texera/pull/5359/flags?src=pr&el=flag&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=apache) | `51.98% <ø> (ø)` | | Carriedforward from [23c5fd2](https://app.codecov.io/gh/apache/texera/commit/23c5fd2c13936e43c5094c041650c7c041fe9b22?utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=apache) |
   | [computing-unit-managing-service](https://app.codecov.io/gh/apache/texera/pull/5359/flags?src=pr&el=flag&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=apache) | `1.38% <ø> (ø)` | | Carriedforward from [23c5fd2](https://app.codecov.io/gh/apache/texera/commit/23c5fd2c13936e43c5094c041650c7c041fe9b22?utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=apache) |
   | [config-service](https://app.codecov.io/gh/apache/texera/pull/5359/flags?src=pr&el=flag&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=apache) | `54.68% <ø> (ø)` | | |
   | [file-service](https://app.codecov.io/gh/apache/texera/pull/5359/flags?src=pr&el=flag&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=apache) | `38.42% <ø> (ø)` | | Carriedforward from [23c5fd2](https://app.codecov.io/gh/apache/texera/commit/23c5fd2c13936e43c5094c041650c7c041fe9b22?utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=apache) |
   | [frontend](https://app.codecov.io/gh/apache/texera/pull/5359/flags?src=pr&el=flag&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=apache) | `45.82% <ø> (ø)` | | Carriedforward from [23c5fd2](https://app.codecov.io/gh/apache/texera/commit/23c5fd2c13936e43c5094c041650c7c041fe9b22?utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=apache) |
   | [pyamber](https://app.codecov.io/gh/apache/texera/pull/5359/flags?src=pr&el=flag&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=apache) | `90.80% <ø> (ø)` | | Carriedforward from [23c5fd2](https://app.codecov.io/gh/apache/texera/commit/23c5fd2c13936e43c5094c041650c7c041fe9b22?utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=apache) |
   | [python](https://app.codecov.io/gh/apache/texera/pull/5359/flags?src=pr&el=flag&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=apache) | `90.80% <ø> (ø)` | | Carriedforward from [23c5fd2](https://app.codecov.io/gh/apache/texera/commit/23c5fd2c13936e43c5094c041650c7c041fe9b22?utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=apache) |
   | [workflow-compiling-service](https://app.codecov.io/gh/apache/texera/pull/5359/flags?src=pr&el=flag&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=apache) | `58.39% <ø> (ø)` | | Carriedforward from [23c5fd2](https://app.codecov.io/gh/apache/texera/commit/23c5fd2c13936e43c5094c041650c7c041fe9b22?utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=apache) |
   
   *This pull request uses carry forward flags. [Click here](https://docs.codecov.io/docs/carryforward-flags?utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=apache) to find out more.
   </details>
   
   [:umbrella: View full report in Codecov by Sentry](https://app.codecov.io/gh/apache/texera/pull/5359?dropdown=coverage&src=pr&el=continue&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=apache).   
   :loudspeaker: Have feedback on the report? [Share it here](https://about.codecov.io/codecov-pr-comment-feedback/?utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=apache).
   <details><summary> :rocket: New features to boost your workflow: </summary>
   
   - :package: [JS Bundle Analysis](https://docs.codecov.com/docs/javascript-bundle-analysis): Save yourself from yourself by tracking and limiting bundle sizes in JS merges.
   </details>


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscribe@texera.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Re: [PR] feat(comment-commands): auto-assign reviewer on request-review no args command [texera]

Posted by "juliethecao (via GitHub)" <gi...@apache.org>.
juliethecao commented on code in PR #5359:
URL: https://github.com/apache/texera/pull/5359#discussion_r3354227680


##########
.github/workflows/comment-commands.yml:
##########
@@ -111,10 +113,16 @@ jobs:
           || startsWith(github.event.comment.body, '/unrequest-review'))
     runs-on: ubuntu-latest
     steps:
+      - uses: actions/checkout@v5

Review Comment:
   - Added an explicit git fetch origin <pull.base.ref> inside getReviewersFromBlame, right after the github.rest.pulls.get API call that gives us pull.base.ref.
   - This ensures pull.base.sha is always reachable in the runner regardless of which branch the PR targets, not just main.
   - The fetch can't be done at the actions/checkout step level because pull.base.ref is only known after the API call, which happens later in the script step.



-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscribe@texera.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Re: [PR] feat(comment-commands): auto-assign reviewer on request-review no args command [texera]

Posted by "juliethecao (via GitHub)" <gi...@apache.org>.
juliethecao commented on PR #5359:
URL: https://github.com/apache/texera/pull/5359#issuecomment-4620470362

   It has been fixed through a git reset. What caused it was I synced fork and pushed those unrelated changes with mine in a previous commit.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscribe@texera.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Re: [PR] feat(comment-commands): auto-assign reviewer on request-review no args command [texera]

Posted by "Ma77Ball (via GitHub)" <gi...@apache.org>.
Ma77Ball commented on code in PR #5359:
URL: https://github.com/apache/texera/pull/5359#discussion_r3362393929


##########
.github/workflows/comment-commands.yml:
##########
@@ -137,6 +145,150 @@ jobs:
               return;
             }
 
+            // Find a reviewer for the PR by running `git blame` on each
+            // changed file, picking the most recent commit author for
+            // that file, and turning that commit into a GitHub login.
+            // Returns an array of unique logins.
+            async function getReviewersFromBlame() {
+              const { data: pull } = await github.rest.pulls.get({
+                owner, repo, pull_number,
+              });
+
+              // The default checkout targets the repo's default branch, so
+              // pull.base.sha may not be reachable when the PR targets a
+              // release or divergent branch. Fetch the base ref explicitly
+              // so git blame <base.sha> always works.
+              try {
+                execFileSync('git', ['fetch', 'origin', pull.base.ref], { encoding: 'utf8' });
+              } catch (e) {
+                core.warning(`git fetch for base ref ${pull.base.ref} failed: ${e.message}`);
+              }
+
+              // List files changed in the pull request (paginated).
+              const files = await github.paginate(github.rest.pulls.listFiles, {
+                owner, repo, pull_number, per_page: 100,
+              });
+
+              // Parse the `git blame -p` output to find, for each file,
+              // the commit (SHA) that was the most recent author-time.
+              function latestBlameCommit(blameOutput) {
+                let latest = null; // { sha, authorTime }
+                let current = null;
+
+                function finalizeCurrent() {
+                  if (!current || current.authorTime == null) return;
+                  if (!latest || current.authorTime > latest.authorTime) {
+                    latest = current;
+                  }
+                }
+
+                for (const line of blameOutput.split(/\r?\n/)) {
+                  // A header line marks a new blamed commit block.
+                  const header = line.match(/^([0-9a-f^]+)\s+\d+\s+\d+\s+\d+$/);
+                  if (header) {
+                    finalizeCurrent();
+                    current = { sha: header[1].replace(/^\^/, ''), authorTime: null };
+                    continue;
+                  }
+
+                  // `author-time` lines give a UNIX timestamp we can use.
+                  const authorTime = line.match(/^author-time\s+(\d+)$/);
+                  if (authorTime && current) {
+                    current.authorTime = Number(authorTime[1]);
+                  }
+                }
+
+                finalizeCurrent();
+                return latest;
+              }
+
+              // Fetch collaborators once as a fallback pool for files whose
+              // blamed commit has no linked GitHub login.
+              let collaboratorPool = [];
+              try {
+                const collabs = await github.paginate(github.rest.repos.listCollaborators, {
+                  owner, repo, per_page: 100,
+                });
+                collaboratorPool = collabs
+                  .filter(u => u.type !== 'Bot' && u.login.toLowerCase() !== author.toLowerCase())
+                  .map(u => u.login);
+              } catch (e) {
+                core.warning(`Could not fetch collaborators for fallback: ${e.message}`);
+              }
+
+              // Count how many changed files each candidate most recently
+              // touched. Top MAX_REVIEWERS avoids the GitHub 422 that
+              // rejects >15 reviewers and keeps noise low.
+              const MAX_REVIEWERS = 2;
+              const reviewerCounts = new Map(); // login -> file count
+              for (const { filename } of files) {
+                let blameOutput;
+                try {
+                  // Run blame at the PR base commit so we attribute
+                  // existing lines correctly (not the PR tip).
+                  blameOutput = execFileSync('git', ['blame', '-p', pull.base.sha, '--', filename], { encoding: 'utf8' });
+                } catch (e) {
+                  core.warning(`git blame on ${filename} at ${pull.base.sha} failed: ${e.message}`);
+                  continue;
+                }
+
+                const latest = latestBlameCommit(blameOutput);
+                if (!latest) {
+                  core.warning(`Could not determine a blamed commit for ${filename}; skipping.`);
+                  continue;
+                }
+
+                let commit;
+                try {
+                  ({ data: commit } = await github.rest.repos.getCommit({ owner, repo, ref: latest.sha }));
+                } catch (e) {
+                  core.warning(`Commit lookup for ${latest.sha} from ${filename} failed: ${e.message}`);
+                  continue;
+                }
+
+                // Prefer the GitHub-linked author/committer; fall back to a
+                // random collaborator if the commit has no linked GitHub login
+                // (e.g., authored by email only).
+                let login = commit.author?.login ?? commit.committer?.login;
+                if (!login) {
+                  if (!collaboratorPool.length) {
+                    core.warning(`Commit ${latest.sha} from ${filename} has no GitHub user and no collaborator fallback; skipping.`);
+                    continue;
+                  }
+                  login = collaboratorPool[Math.floor(Math.random() * collaboratorPool.length)];
+                  core.info(`Commit ${latest.sha} from ${filename} has no GitHub user; falling back to random collaborator ${login}.`);
+                }

Review Comment:
   The random fallback pick gets counted in `reviewerCounts`, so it can outrank a real blame author from another file. Don't count random picks: use real committers whenever any file has one, and fall back to a single random collaborator only when no file produced a real committer.



-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscribe@texera.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Re: [PR] feat(comment-commands): auto-assign reviewer on request-review no args command [texera]

Posted by "juliethecao (via GitHub)" <gi...@apache.org>.
juliethecao commented on code in PR #5359:
URL: https://github.com/apache/texera/pull/5359#discussion_r3354239286


##########
.github/workflows/comment-commands.yml:
##########
@@ -137,6 +145,97 @@ jobs:
               return;
             }
 
+            // Find a reviewer for the PR by running `git blame` on each
+            // changed file, picking the most recent commit author for
+            // that file, and turning that commit into a GitHub login.
+            // Returns an array of unique logins.
+            async function getReviewersFromBlame() {
+              const { data: pull } = await github.rest.pulls.get({
+                owner, repo, pull_number,
+              });
+
+              // List files changed in the pull request (paginated).
+              const files = await github.paginate(github.rest.pulls.listFiles, {
+                owner, repo, pull_number, per_page: 100,
+              });
+
+              // Parse the `git blame -p` output to find, for each file,
+              // the commit (SHA) that was the most recent author-time.
+              function latestBlameCommit(blameOutput) {
+                let latest = null; // { sha, authorTime }
+                let current = null;
+
+                function finalizeCurrent() {
+                  if (!current || current.authorTime == null) return;
+                  if (!latest || current.authorTime > latest.authorTime) {
+                    latest = current;
+                  }
+                }
+
+                for (const line of blameOutput.split(/\r?\n/)) {
+                  // A header line marks a new blamed commit block.
+                  const header = line.match(/^([0-9a-f^]+)\s+\d+\s+\d+\s+\d+$/);
+                  if (header) {
+                    finalizeCurrent();
+                    current = { sha: header[1].replace(/^\^/, ''), authorTime: null };
+                    continue;
+                  }
+
+                  // `author-time` lines give a UNIX timestamp we can use.
+                  const authorTime = line.match(/^author-time\s+(\d+)$/);
+                  if (authorTime && current) {
+                    current.authorTime = Number(authorTime[1]);
+                  }
+                }
+
+                finalizeCurrent();
+                return latest;
+              }
+
+              const reviewers = new Set();
+              for (const { filename } of files) {
+                let blameOutput;
+                try {
+                  // Run blame at the PR base commit so we attribute
+                  // existing lines correctly (not the PR tip).
+                  blameOutput = execFileSync('git', ['blame', '-p', pull.base.sha, '--', filename], { encoding: 'utf8' });
+                } catch (e) {
+                  core.warning(`git blame on ${filename} at ${pull.base.sha} failed: ${e.message}`);
+                  continue;
+                }
+
+                const latest = latestBlameCommit(blameOutput);
+                if (!latest) {
+                  core.warning(`Could not determine a blamed commit for ${filename}; skipping.`);
+                  continue;
+                }
+
+                let commit;
+                try {
+                  ({ data: commit } = await github.rest.repos.getCommit({ owner, repo, ref: latest.sha }));
+                } catch (e) {
+                  core.warning(`Commit lookup for ${latest.sha} from ${filename} failed: ${e.message}`);
+                  continue;
+                }
+
+                // Prefer the GitHub-linked author/committer; skip if
+                // there is no linked login (e.g., authored by email only).
+                const login = commit.author?.login ?? commit.committer?.login;
+                if (!login) {
+                  core.warning(`Commit ${latest.sha} from ${filename} has no GitHub user; skipping.`);
+                  continue;
+                }
+
+                // Don't request the PR author or bot accounts.
+                if (login.toLowerCase() === author.toLowerCase()) continue;
+                if (commit.author?.type === 'Bot' || commit.committer?.type === 'Bot') continue;
+
+                reviewers.add(login);
+              }
+
+              return [...reviewers].sort();

Review Comment:
   - Replaced the Set (which collected one unique login per file) with a Map that counts how many changed files each candidate most recently touched.
   - After the loop, candidates are sorted by count descending and capped at MAX_REVIEWERS = 2, so a wide PR with many changed files will only request the top 2 most frequent authors, not every distinct one.
   - This avoids the GitHub 422 rejection for >15 reviewers and keeps the review request focused on whoever owns the most relevant parts of the diff.



-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscribe@texera.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Re: [PR] feat(comment-commands): auto-assign reviewer on request-review no args command [texera]

Posted by "Yicong-Huang (via GitHub)" <gi...@apache.org>.
Yicong-Huang commented on PR #5359:
URL: https://github.com/apache/texera/pull/5359#issuecomment-4644814845

   if no objection, I suggest we go with that proposal. In this case, let's close the current Pr and issue and create a new issue to move forward. WDYT?


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscribe@texera.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Re: [PR] feat(comment-commands): auto-assign reviewer on request-review no args command [texera]

Posted by "juliethecao (via GitHub)" <gi...@apache.org>.
juliethecao commented on PR #5359:
URL: https://github.com/apache/texera/pull/5359#issuecomment-4644282520

   I think your proposal is very reasonable. It keeps the author in control of who actually gets requested, avoids spamming past contributors like Alice, and the distinction between requestable committers and contextual cc's maps directly onto GitHub's own limitations. I'm happy to implement these suggestions unless there are other points to consider.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscribe@texera.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Re: [PR] feat(comment-commands): auto-assign reviewer on request-review no args command [texera]

Posted by "juliethecao (via GitHub)" <gi...@apache.org>.
juliethecao commented on code in PR #5359:
URL: https://github.com/apache/texera/pull/5359#discussion_r3354233358


##########
.github/workflows/comment-commands.yml:
##########
@@ -137,6 +145,97 @@ jobs:
               return;
             }
 
+            // Find a reviewer for the PR by running `git blame` on each
+            // changed file, picking the most recent commit author for
+            // that file, and turning that commit into a GitHub login.
+            // Returns an array of unique logins.
+            async function getReviewersFromBlame() {
+              const { data: pull } = await github.rest.pulls.get({
+                owner, repo, pull_number,
+              });
+
+              // List files changed in the pull request (paginated).
+              const files = await github.paginate(github.rest.pulls.listFiles, {
+                owner, repo, pull_number, per_page: 100,
+              });
+
+              // Parse the `git blame -p` output to find, for each file,
+              // the commit (SHA) that was the most recent author-time.
+              function latestBlameCommit(blameOutput) {
+                let latest = null; // { sha, authorTime }
+                let current = null;
+
+                function finalizeCurrent() {
+                  if (!current || current.authorTime == null) return;
+                  if (!latest || current.authorTime > latest.authorTime) {
+                    latest = current;
+                  }
+                }
+
+                for (const line of blameOutput.split(/\r?\n/)) {
+                  // A header line marks a new blamed commit block.
+                  const header = line.match(/^([0-9a-f^]+)\s+\d+\s+\d+\s+\d+$/);
+                  if (header) {
+                    finalizeCurrent();
+                    current = { sha: header[1].replace(/^\^/, ''), authorTime: null };
+                    continue;
+                  }
+
+                  // `author-time` lines give a UNIX timestamp we can use.
+                  const authorTime = line.match(/^author-time\s+(\d+)$/);
+                  if (authorTime && current) {
+                    current.authorTime = Number(authorTime[1]);
+                  }
+                }
+
+                finalizeCurrent();
+                return latest;
+              }
+
+              const reviewers = new Set();
+              for (const { filename } of files) {
+                let blameOutput;
+                try {
+                  // Run blame at the PR base commit so we attribute
+                  // existing lines correctly (not the PR tip).
+                  blameOutput = execFileSync('git', ['blame', '-p', pull.base.sha, '--', filename], { encoding: 'utf8' });
+                } catch (e) {
+                  core.warning(`git blame on ${filename} at ${pull.base.sha} failed: ${e.message}`);
+                  continue;
+                }
+
+                const latest = latestBlameCommit(blameOutput);
+                if (!latest) {
+                  core.warning(`Could not determine a blamed commit for ${filename}; skipping.`);
+                  continue;
+                }
+
+                let commit;
+                try {
+                  ({ data: commit } = await github.rest.repos.getCommit({ owner, repo, ref: latest.sha }));
+                } catch (e) {
+                  core.warning(`Commit lookup for ${latest.sha} from ${filename} failed: ${e.message}`);
+                  continue;
+                }
+
+                // Prefer the GitHub-linked author/committer; skip if
+                // there is no linked login (e.g., authored by email only).
+                const login = commit.author?.login ?? commit.committer?.login;
+                if (!login) {
+                  core.warning(`Commit ${latest.sha} from ${filename} has no GitHub user; skipping.`);
+                  continue;
+                }
+
+                // Don't request the PR author or bot accounts.
+                if (login.toLowerCase() === author.toLowerCase()) continue;
+                if (commit.author?.type === 'Bot' || commit.committer?.type === 'Bot') continue;

Review Comment:
   - The original check rejected a commit if either author or committer was a Bot, which would wrongly exclude a human-authored commit that was applied by a bot committer (e.g. a patch-applying bot).
   - Fixed by introducing loginSource, a variable that holds whichever identity actually supplied the login (commit.author if commit.author?.login exists, otherwise commit.committer).
   - The bot check now gates on loginSource?.type === 'Bot' instead, so only the identity whose login is being used is checked.



-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscribe@texera.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Re: [PR] feat(comment-commands): auto-assign reviewer on request-review no args command [texera]

Posted by "Ma77Ball (via GitHub)" <gi...@apache.org>.
Ma77Ball commented on code in PR #5359:
URL: https://github.com/apache/texera/pull/5359#discussion_r3346755461


##########
.github/workflows/comment-commands.yml:
##########
@@ -111,10 +113,16 @@ jobs:
           || startsWith(github.event.comment.body, '/unrequest-review'))
     runs-on: ubuntu-latest
     steps:
+      - uses: actions/checkout@v5

Review Comment:
   `actions/checkout@v5` on an `issue_comment` event checks out the repo's **default branch**, not this PR's base ref. With `fetch-depth: 0` that's fine when the PR targets `main` (base.sha is an ancestor), but for a PR targeting a release/divergent branch, `pull.base.sha` may not be reachable from the checked-out tree — `git blame <base.sha>` would then fail for *every* file and the command silently produces no reviewers. Consider fetching/checking out `pull.base.ref` (or `base.sha`) explicitly.



##########
.github/workflows/comment-commands.yml:
##########
@@ -137,6 +145,97 @@ jobs:
               return;
             }
 
+            // Find a reviewer for the PR by running `git blame` on each
+            // changed file, picking the most recent commit author for
+            // that file, and turning that commit into a GitHub login.
+            // Returns an array of unique logins.
+            async function getReviewersFromBlame() {
+              const { data: pull } = await github.rest.pulls.get({
+                owner, repo, pull_number,
+              });
+
+              // List files changed in the pull request (paginated).
+              const files = await github.paginate(github.rest.pulls.listFiles, {
+                owner, repo, pull_number, per_page: 100,
+              });
+
+              // Parse the `git blame -p` output to find, for each file,
+              // the commit (SHA) that was the most recent author-time.
+              function latestBlameCommit(blameOutput) {
+                let latest = null; // { sha, authorTime }
+                let current = null;
+
+                function finalizeCurrent() {
+                  if (!current || current.authorTime == null) return;
+                  if (!latest || current.authorTime > latest.authorTime) {
+                    latest = current;
+                  }
+                }
+
+                for (const line of blameOutput.split(/\r?\n/)) {
+                  // A header line marks a new blamed commit block.
+                  const header = line.match(/^([0-9a-f^]+)\s+\d+\s+\d+\s+\d+$/);
+                  if (header) {
+                    finalizeCurrent();
+                    current = { sha: header[1].replace(/^\^/, ''), authorTime: null };
+                    continue;
+                  }
+
+                  // `author-time` lines give a UNIX timestamp we can use.
+                  const authorTime = line.match(/^author-time\s+(\d+)$/);
+                  if (authorTime && current) {
+                    current.authorTime = Number(authorTime[1]);
+                  }
+                }
+
+                finalizeCurrent();
+                return latest;
+              }
+
+              const reviewers = new Set();
+              for (const { filename } of files) {
+                let blameOutput;
+                try {
+                  // Run blame at the PR base commit so we attribute
+                  // existing lines correctly (not the PR tip).
+                  blameOutput = execFileSync('git', ['blame', '-p', pull.base.sha, '--', filename], { encoding: 'utf8' });
+                } catch (e) {
+                  core.warning(`git blame on ${filename} at ${pull.base.sha} failed: ${e.message}`);
+                  continue;
+                }
+
+                const latest = latestBlameCommit(blameOutput);
+                if (!latest) {
+                  core.warning(`Could not determine a blamed commit for ${filename}; skipping.`);
+                  continue;
+                }
+
+                let commit;
+                try {
+                  ({ data: commit } = await github.rest.repos.getCommit({ owner, repo, ref: latest.sha }));
+                } catch (e) {
+                  core.warning(`Commit lookup for ${latest.sha} from ${filename} failed: ${e.message}`);
+                  continue;
+                }
+
+                // Prefer the GitHub-linked author/committer; skip if
+                // there is no linked login (e.g., authored by email only).
+                const login = commit.author?.login ?? commit.committer?.login;
+                if (!login) {
+                  core.warning(`Commit ${latest.sha} from ${filename} has no GitHub user; skipping.`);
+                  continue;
+                }
+
+                // Don't request the PR author or bot accounts.
+                if (login.toLowerCase() === author.toLowerCase()) continue;
+                if (commit.author?.type === 'Bot' || commit.committer?.type === 'Bot') continue;
+
+                reviewers.add(login);
+              }
+
+              return [...reviewers].sort();

Review Comment:
   This returns the latest author of *every* changed file, so a wide PR can request many reviewers. Two issues: (1) `requestReviewers` rejects >15 reviewers with a 422, and (2) it's noisy. Limit to like 2 reviewers.



##########
.github/workflows/comment-commands.yml:
##########
@@ -111,10 +113,16 @@ jobs:
           || startsWith(github.event.comment.body, '/unrequest-review'))
     runs-on: ubuntu-latest
     steps:
+      - uses: actions/checkout@v5
+        with:
+          fetch-depth: 0
       - uses: actions/github-script@v8
         with:
           github-token: ${{ secrets.GITHUB_TOKEN }}
           script: |
+            // `git blame` needs to runlocally in the runner. Use

Review Comment:
   ```suggestion
               // `git blame` needs to run locally in the runner. Use
   ```
   Nit: typo — "runlocally" should be "run locally".
   



##########
.github/workflows/comment-commands.yml:
##########
@@ -153,8 +252,18 @@ jobs:
                 reviewers.push(h);
             }
             if (!reviewers.length && !team_reviewers.length) {
-              core.warning(`No valid @mentions in '${action}'; skipping.`);
-              return;
+              if (action !== 'request-review') {
+                core.warning(`No valid @mentions in '${action}'; skipping.`);
+                return;
+              }
+
+              reviewers.push(...await getReviewersFromBlame());

Review Comment:
   **Main concern:** `requestReviewers` only accepts **collaborators**; any other login returns `422. Reviews may only be requested from collaborators."` In a public repo, `git blame` frequently surfaces past contributors who aren't current collaborators. Since the REST call is atomic, a single failed login fails the *entire* request, and zero reviewers get added. The path mentioned above already guards against the analogous "one bad name" case; blame logins enter here, unvalidated. Consider validating each login (e.g., `repos.checkCollaborator`) before adding it.



##########
.github/workflows/comment-commands.yml:
##########
@@ -137,6 +145,97 @@ jobs:
               return;
             }
 
+            // Find a reviewer for the PR by running `git blame` on each
+            // changed file, picking the most recent commit author for
+            // that file, and turning that commit into a GitHub login.
+            // Returns an array of unique logins.
+            async function getReviewersFromBlame() {
+              const { data: pull } = await github.rest.pulls.get({
+                owner, repo, pull_number,
+              });
+
+              // List files changed in the pull request (paginated).
+              const files = await github.paginate(github.rest.pulls.listFiles, {
+                owner, repo, pull_number, per_page: 100,
+              });
+
+              // Parse the `git blame -p` output to find, for each file,
+              // the commit (SHA) that was the most recent author-time.
+              function latestBlameCommit(blameOutput) {
+                let latest = null; // { sha, authorTime }
+                let current = null;
+
+                function finalizeCurrent() {
+                  if (!current || current.authorTime == null) return;
+                  if (!latest || current.authorTime > latest.authorTime) {
+                    latest = current;
+                  }
+                }
+
+                for (const line of blameOutput.split(/\r?\n/)) {
+                  // A header line marks a new blamed commit block.
+                  const header = line.match(/^([0-9a-f^]+)\s+\d+\s+\d+\s+\d+$/);
+                  if (header) {
+                    finalizeCurrent();
+                    current = { sha: header[1].replace(/^\^/, ''), authorTime: null };
+                    continue;
+                  }
+
+                  // `author-time` lines give a UNIX timestamp we can use.
+                  const authorTime = line.match(/^author-time\s+(\d+)$/);
+                  if (authorTime && current) {
+                    current.authorTime = Number(authorTime[1]);
+                  }
+                }
+
+                finalizeCurrent();
+                return latest;
+              }
+
+              const reviewers = new Set();
+              for (const { filename } of files) {
+                let blameOutput;
+                try {
+                  // Run blame at the PR base commit so we attribute
+                  // existing lines correctly (not the PR tip).
+                  blameOutput = execFileSync('git', ['blame', '-p', pull.base.sha, '--', filename], { encoding: 'utf8' });
+                } catch (e) {
+                  core.warning(`git blame on ${filename} at ${pull.base.sha} failed: ${e.message}`);
+                  continue;
+                }
+
+                const latest = latestBlameCommit(blameOutput);
+                if (!latest) {
+                  core.warning(`Could not determine a blamed commit for ${filename}; skipping.`);
+                  continue;
+                }
+
+                let commit;
+                try {
+                  ({ data: commit } = await github.rest.repos.getCommit({ owner, repo, ref: latest.sha }));
+                } catch (e) {
+                  core.warning(`Commit lookup for ${latest.sha} from ${filename} failed: ${e.message}`);
+                  continue;
+                }
+
+                // Prefer the GitHub-linked author/committer; skip if
+                // there is no linked login (e.g., authored by email only).
+                const login = commit.author?.login ?? commit.committer?.login;
+                if (!login) {
+                  core.warning(`Commit ${latest.sha} from ${filename} has no GitHub user; skipping.`);
+                  continue;
+                }
+
+                // Don't request the PR author or bot accounts.
+                if (login.toLowerCase() === author.toLowerCase()) continue;
+                if (commit.author?.type === 'Bot' || commit.committer?.type === 'Bot') continue;

Review Comment:
   `login` is taken from `commit.author?.login ?? commit.committer?.login`, but this rejects the commit if *either* author or committer is a Bot. A human-authored commit applied by a bot committer (e.g. a patch-applying bot) would be wrongly excluded. Consider gating on the bot-ness of whichever identity actually supplied `login`.



-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscribe@texera.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Re: [PR] feat(comment-commands): auto-assign reviewer on request-review no args command [texera]

Posted by "Yicong-Huang (via GitHub)" <gi...@apache.org>.
Yicong-Huang commented on PR #5359:
URL: https://github.com/apache/texera/pull/5359#issuecomment-4635229167

   I do have one concern which is this `request-review` will automatically send out the review request to a real user, without confirming with PR author, and this may bother ppl and we don't have ways to precent it. 
   
   For instance, suppose a contributor Alice committed to a file 5 years ago and no longer wish to work on texera. whenever someone uses this feature on a PR touched the file, Alice will get a request. She may not want to receive such a request. 
   
   So I think there are two ways to go:
   1. We could add a confirming phase, after CI kicks in, it will reply as a github comment about "Suggested reviewers: A, B, C". Then author use the command again explicitly `/request-review A B C` to actually send out the review request. This way, the author is in control of sending such a request. This can make the problem smaller, but from time to time, new contributors would still blindly send the request to Alice anyway if she is suggested by the CI.
   2. We should make only committers to be the request target. This implicitly means we have higher requirement on committer: committers are expected to receive review requests, even if they don't wish to receive. 
   
   This also reminds me of github limitation (to be verified though):
   I think github only allows the request target to be committers + anyone reviewed this PR before. So even if your suggestion contains A, B and C three contributors, only the committers (say B) in the suggestion list will receive the request (this may already satisfy the 2nd way above). But I feel it will still be benefitial to let author know A and C also have context.
   
   Based on all those thinking, here is a proposal, up for discussion:
   1. Maybe we can run a CI when PR gets opened or updated, which sends a comment of "suggested reviewer: A, B (committer), C. You can use /request-review <committer> or @ others to ping them for review".
   2. The author still needs to explicitly use `/request-review B` to  request a committer for review. 
   3. The author can optionally add a comment `cc @A, @C, you may want to have a pass" to notify non-committers.  


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscribe@texera.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Re: [PR] feat(comment-commands): auto-assign reviewer on request-review no args command [texera]

Posted by "Ma77Ball (via GitHub)" <gi...@apache.org>.
Ma77Ball commented on code in PR #5359:
URL: https://github.com/apache/texera/pull/5359#discussion_r3346917067


##########
.github/workflows/comment-commands.yml:
##########
@@ -137,6 +145,97 @@ jobs:
               return;
             }
 
+            // Find a reviewer for the PR by running `git blame` on each
+            // changed file, picking the most recent commit author for
+            // that file, and turning that commit into a GitHub login.
+            // Returns an array of unique logins.
+            async function getReviewersFromBlame() {
+              const { data: pull } = await github.rest.pulls.get({
+                owner, repo, pull_number,
+              });
+
+              // List files changed in the pull request (paginated).
+              const files = await github.paginate(github.rest.pulls.listFiles, {
+                owner, repo, pull_number, per_page: 100,
+              });
+
+              // Parse the `git blame -p` output to find, for each file,
+              // the commit (SHA) that was the most recent author-time.
+              function latestBlameCommit(blameOutput) {
+                let latest = null; // { sha, authorTime }
+                let current = null;
+
+                function finalizeCurrent() {
+                  if (!current || current.authorTime == null) return;
+                  if (!latest || current.authorTime > latest.authorTime) {
+                    latest = current;
+                  }
+                }
+
+                for (const line of blameOutput.split(/\r?\n/)) {
+                  // A header line marks a new blamed commit block.
+                  const header = line.match(/^([0-9a-f^]+)\s+\d+\s+\d+\s+\d+$/);
+                  if (header) {
+                    finalizeCurrent();
+                    current = { sha: header[1].replace(/^\^/, ''), authorTime: null };
+                    continue;
+                  }
+
+                  // `author-time` lines give a UNIX timestamp we can use.
+                  const authorTime = line.match(/^author-time\s+(\d+)$/);
+                  if (authorTime && current) {
+                    current.authorTime = Number(authorTime[1]);
+                  }
+                }
+
+                finalizeCurrent();
+                return latest;
+              }
+
+              const reviewers = new Set();
+              for (const { filename } of files) {
+                let blameOutput;
+                try {
+                  // Run blame at the PR base commit so we attribute
+                  // existing lines correctly (not the PR tip).
+                  blameOutput = execFileSync('git', ['blame', '-p', pull.base.sha, '--', filename], { encoding: 'utf8' });
+                } catch (e) {
+                  core.warning(`git blame on ${filename} at ${pull.base.sha} failed: ${e.message}`);
+                  continue;
+                }
+
+                const latest = latestBlameCommit(blameOutput);
+                if (!latest) {
+                  core.warning(`Could not determine a blamed commit for ${filename}; skipping.`);
+                  continue;
+                }
+
+                let commit;
+                try {
+                  ({ data: commit } = await github.rest.repos.getCommit({ owner, repo, ref: latest.sha }));
+                } catch (e) {
+                  core.warning(`Commit lookup for ${latest.sha} from ${filename} failed: ${e.message}`);
+                  continue;
+                }
+
+                // Prefer the GitHub-linked author/committer; skip if
+                // there is no linked login (e.g., authored by email only).
+                const login = commit.author?.login ?? commit.committer?.login;
+                if (!login) {
+                  core.warning(`Commit ${latest.sha} from ${filename} has no GitHub user; skipping.`);
+                  continue;
+                }
+
+                // Don't request the PR author or bot accounts.
+                if (login.toLowerCase() === author.toLowerCase()) continue;
+                if (commit.author?.type === 'Bot' || commit.committer?.type === 'Bot') continue;
+
+                reviewers.add(login);
+              }
+
+              return [...reviewers].sort();

Review Comment:
   Possibly do a polling strategy based on the most common collaborator that shows up



-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscribe@texera.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Re: [PR] feat(comment-commands): auto-assign reviewer on request-review no args command [texera]

Posted by "juliethecao (via GitHub)" <gi...@apache.org>.
juliethecao commented on code in PR #5359:
URL: https://github.com/apache/texera/pull/5359#discussion_r3354246838


##########
.github/workflows/comment-commands.yml:
##########
@@ -153,8 +252,18 @@ jobs:
                 reviewers.push(h);
             }
             if (!reviewers.length && !team_reviewers.length) {
-              core.warning(`No valid @mentions in '${action}'; skipping.`);
-              return;
+              if (action !== 'request-review') {
+                core.warning(`No valid @mentions in '${action}'; skipping.`);
+                return;
+              }
+
+              reviewers.push(...await getReviewersFromBlame());

Review Comment:
   - Added a repos.checkCollaborator call for each candidate login before adding them to reviewerCounts.
   - If the login is not a collaborator, it is skipped with a warning and never enters the count, so only validated collaborators are passed to requestReviewers.
   - This prevents the atomic requestReviewers call from failing with a 422 due to a single non-collaborator login (which would otherwise cause zero reviewers to be added).
   - The validation happens during the per-file blame loop, so non-collaborators are filtered out before the frequency ranking and MAX_REVIEWERS cap are applied.



-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscribe@texera.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org