Skip to content

DOCSP-46711 MongoClientOptions 404 #960

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
merged 1 commit into from
Feb 3, 2025

Conversation

lindseymoore
Copy link
Collaborator

@lindseymoore lindseymoore commented Feb 3, 2025

Pull Request Info

PR Reviewing Guidelines

JIRA - https://jira.mongodb.org/browse/DOCSP-46711
Staging - https://deploy-preview-960--docs-node.netlify.app/fundamentals/connection/network-compression/#specify-compression-algorithms

Self-Review Checklist

  • Is this free of any warnings or errors in the RST?
  • Did you run a spell-check?
  • Did you run a grammar-check?
  • Are all the links working?
  • Are the facets and meta keywords accurate?

Copy link

netlify bot commented Feb 3, 2025

Deploy Preview for docs-node ready!

Name Link
🔨 Latest commit c58a648
🔍 Latest deploy log https://app.netlify.com/sites/docs-node/deploys/67a12f40b3ee8e0008380917
😎 Deploy Preview https://deploy-preview-960--docs-node.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site configuration.

@lindseymoore lindseymoore merged commit a9aa853 into mongodb:master Feb 3, 2025
19 checks passed
github-actions bot pushed a commit that referenced this pull request Feb 3, 2025
github-actions bot pushed a commit that referenced this pull request Feb 3, 2025
github-actions bot pushed a commit that referenced this pull request Feb 3, 2025
github-actions bot pushed a commit that referenced this pull request Feb 3, 2025
github-actions bot pushed a commit that referenced this pull request Feb 3, 2025
github-actions bot pushed a commit that referenced this pull request Feb 3, 2025
github-actions bot pushed a commit that referenced this pull request Feb 3, 2025
Copy link

github-actions bot commented Feb 3, 2025

The backport to v6.3 failed:

The process '/usr/bin/git' failed with exit code 1

To backport manually, run these commands in your terminal:

# Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add .worktrees/backport-v6.3 v6.3
# Navigate to the new working tree
cd .worktrees/backport-v6.3
# Create a new branch
git switch --create backport-960-to-v6.3
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 a9aa8532e6a61e412bc722ee45b1e7fe56348275
# Push it to GitHub
git push --set-upstream origin backport-960-to-v6.3
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-v6.3

Then, create a pull request where the base branch is v6.3 and the compare/head branch is backport-960-to-v6.3.

Copy link

github-actions bot commented Feb 3, 2025

The backport to v6.2 failed:

The process '/usr/bin/git' failed with exit code 1

To backport manually, run these commands in your terminal:

# Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add .worktrees/backport-v6.2 v6.2
# Navigate to the new working tree
cd .worktrees/backport-v6.2
# Create a new branch
git switch --create backport-960-to-v6.2
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 a9aa8532e6a61e412bc722ee45b1e7fe56348275
# Push it to GitHub
git push --set-upstream origin backport-960-to-v6.2
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-v6.2

Then, create a pull request where the base branch is v6.2 and the compare/head branch is backport-960-to-v6.2.

Copy link

github-actions bot commented Feb 3, 2025

The backport to v6.1 failed:

The process '/usr/bin/git' failed with exit code 1

To backport manually, run these commands in your terminal:

# Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add .worktrees/backport-v6.1 v6.1
# Navigate to the new working tree
cd .worktrees/backport-v6.1
# Create a new branch
git switch --create backport-960-to-v6.1
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 a9aa8532e6a61e412bc722ee45b1e7fe56348275
# Push it to GitHub
git push --set-upstream origin backport-960-to-v6.1
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-v6.1

Then, create a pull request where the base branch is v6.1 and the compare/head branch is backport-960-to-v6.1.

Copy link

github-actions bot commented Feb 3, 2025

The backport to v6.0 failed:

The process '/usr/bin/git' failed with exit code 1

To backport manually, run these commands in your terminal:

# Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add .worktrees/backport-v6.0 v6.0
# Navigate to the new working tree
cd .worktrees/backport-v6.0
# Create a new branch
git switch --create backport-960-to-v6.0
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 a9aa8532e6a61e412bc722ee45b1e7fe56348275
# Push it to GitHub
git push --set-upstream origin backport-960-to-v6.0
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-v6.0

Then, create a pull request where the base branch is v6.0 and the compare/head branch is backport-960-to-v6.0.

github-actions bot pushed a commit that referenced this pull request Feb 3, 2025
github-actions bot pushed a commit that referenced this pull request Feb 3, 2025
github-actions bot pushed a commit that referenced this pull request Feb 3, 2025
lindseymoore added a commit that referenced this pull request Feb 3, 2025
(cherry picked from commit a9aa853)

Co-authored-by: lindseymoore <[email protected]>
lindseymoore added a commit that referenced this pull request Feb 3, 2025
(cherry picked from commit a9aa853)

Co-authored-by: lindseymoore <[email protected]>
lindseymoore added a commit that referenced this pull request Feb 3, 2025
(cherry picked from commit a9aa853)

Co-authored-by: lindseymoore <[email protected]>
lindseymoore added a commit that referenced this pull request Feb 3, 2025
(cherry picked from commit a9aa853)

Co-authored-by: lindseymoore <[email protected]>
lindseymoore added a commit that referenced this pull request Feb 3, 2025
(cherry picked from commit a9aa853)

Co-authored-by: lindseymoore <[email protected]>
lindseymoore added a commit that referenced this pull request Feb 3, 2025
(cherry picked from commit a9aa853)

Co-authored-by: lindseymoore <[email protected]>
lindseymoore added a commit that referenced this pull request Feb 3, 2025
(cherry picked from commit a9aa853)

Co-authored-by: lindseymoore <[email protected]>
lindseymoore added a commit that referenced this pull request Feb 3, 2025
(cherry picked from commit a9aa853)

Co-authored-by: lindseymoore <[email protected]>
lindseymoore added a commit that referenced this pull request Feb 3, 2025
(cherry picked from commit a9aa853)

Co-authored-by: lindseymoore <[email protected]>
lindseymoore added a commit that referenced this pull request Feb 3, 2025
(cherry picked from commit a9aa853)

Co-authored-by: lindseymoore <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants