Skip to content

Conversation

@LetMeFly666
Copy link
Owner

By newSolution.py using GH on MacOS | close: #1062

cpp - AC,44.38%,64.27%
cpp(no max) - AC,46.19%,67.47%
py(no max - AC,61.42%,81.68%
.pem泄露无所谓 反正为了指标的HTTPS只是一个笑话
研二这个点加班的就我一个 - 这绝对有问题
完成一个需求就会有下一个需求
毁灭吧 世界
by hand ofcoursely
看吧 我就说还有
commit f7aa8bc (origin/master, master)
PS F:\OtherApps\Program\Git\Store\Store20_LeetCode> git push
Enumerating objects: 10, done.
Counting objects: 100% (10/10), done.
Delta compression using up to 8 threads
Compressing objects: 100% (6/6), done.
Writing objects: 100% (6/6), 6.12 KiB | 2.04 MiB/s, done.
Total 6 (delta 4), reused 0 (delta 0), pack-reused 0
remote: Resolving deltas: 100% (4/4), completed with 4 local objects.
To ssh.github.com:LetMeFly666/LeetCode
   9aae0e4..1ebb7ee  dev -> dev
PS F:\OtherApps\Program\Git\Store\Store20_LeetCode> git push
Enumerating objects: 7, done.
Counting objects: 100% (7/7), done.
Delta compression using up to 8 threads
Compressing objects: 100% (4/4), done.
Writing objects: 100% (4/4), 4.82 KiB | 2.41 MiB/s, done.
Total 4 (delta 3), reused 0 (delta 0), pack-reused 0
remote: Resolving deltas: 100% (3/3), completed with 3 local objects.
To ssh.github.com:LetMeFly666/LeetCode
   1ebb7ee..1e64402  dev -> dev
PS F:\OtherApps\Program\Git\Store\Store20_LeetCode>
 *  还原的历史记录

remote: Counting objects: 100% (15/15), done.
remote: Compressing objects: 100% (11/11), done.
remote: Total 15 (delta 4), reused 6 (delta 4), pack-reused 0 (from 0)
Unpacking objects: 100% (15/15), 157.69 KiB | 180.00 KiB/s, done.
From ssh.github.com:LetMeFly666/LeetCode
 * branch                    master     -> FETCH_HEAD
   f7aa8bc..34ff65e  master     -> origin/master
Auto-merging Solutions/Other-English-LearningNotes-SomeWords.md
CONFLICT (content): Merge conflict in Solutions/Other-English-LearningNotes-SomeWords.md
Automatic merge failed; fix conflicts and then commit the result.
PS F:\OtherApps\Program\Git\Store\Store20_LeetCode> git branch
* dev
  master
  website
  website_Static
PS F:\OtherApps\Program\Git\Store\Store20_LeetCode> git checkout dev
PS F:\OtherApps\Program\Git\Store\Store20_LeetCode> git status
On branch dev
Your branch is up to date with 'origin/dev'.

You have unmerged paths.
  (fix conflicts and run "git commit")

Changes to be committed:
        new file:   .gitlog
        modified:   .vscode/launch.json
        new file:   Codes/1695-maximum-erasure-value.go
        new file:   Codes/1695-maximum-erasure-value.java
        new file:   Codes/1695-maximum-erasure-value.py
        modified:   README.md
        new file:   "Solutions/LeetCode 1695.\345\210\240\351\231\244\345\255\220\346\225\260\347\273\204\347\232\204\346\234\200\345\244\247\345\276\227\345\210\206.md"
        modified:   "Solutions/LeetCode 1957.\345\210\240\351\231\244\345\255\227\347\254\246\344\275\277\345\255\227\347\254\246\344\270\262\345\217\230\345\245\275.md"

Unmerged paths:
  (use "git add <file>..." to mark resolution)
        both modified:   Solutions/Other-English-LearningNotes-SomeWords.md

PS F:\OtherApps\Program\Git\Store\Store20_LeetCode> git branch
* dev
  master
  website
  website_Static
PS F:\OtherApps\Program\Git\Store\Store20_LeetCode> git status
On branch dev
Your branch is up to date with 'origin/dev'.

You have unmerged paths.
  (fix conflicts and run "git commit")

Changes to be committed:
        new file:   .gitlog
        modified:   .vscode/launch.json
        new file:   Codes/1695-maximum-erasure-value.cpp
        new file:   Codes/1695-maximum-erasure-value.go
        new file:   Codes/1695-maximum-erasure-value.java
        new file:   Codes/1695-maximum-erasure-value.py
        modified:   README.md
        new file:   "Solutions/LeetCode 1695.\345\210\240\351\231\244\345\255\220\346\225\260\347\273\204\347\232\204\346\234\200\345\244\247\345\276\227\345\210\206.md"
        modified:   "Solutions/LeetCode 1957.\345\210\240\351\231\244\345\255\227\347\254\246\344\275\277\345\255\227\347\254\246\344\270\262\345\217\230\345\245\275.md"

Unmerged paths:
  (use "git add <file>..." to mark resolution)
        both modified:   Solutions/Other-English-LearningNotes-SomeWords.md

PS F:\OtherApps\Program\Git\Store\Store20_LeetCode> git log
Author: LetMeFly666 <814114971@qq.com>
Date:   Wed Jul 23 00:16:22 2025 +0800

    3202: docs-题解 (#1035) (#1041)

commit 1ebb7ee
Author: LetMeFly666 <814114971@qq.com>
Date:   Wed Jul 23 00:15:58 2025 +0800

    3202: O(k)空间 - AC.go+docs (#1035) (#1041)

    go - AC,17.49%,80.21%

commit 9aae0e4
Author: LetMeFly666 <814114971@qq.com>
Date:   Tue Jul 22 23:46:17 2025 +0800
PS F:\OtherApps\Program\Git\Store\Store20_LeetCode> git status
On branch dev
Your branch is up to date with 'origin/dev'.

You have unmerged paths.
  (fix conflicts and run "git commit")

Changes to be committed:
        new file:   .gitlog
        modified:   .vscode/launch.json
        new file:   Codes/1695-maximum-erasure-value.cpp
        new file:   Codes/1695-maximum-erasure-value.go
        new file:   Codes/1695-maximum-erasure-value.java
        new file:   Codes/1695-maximum-erasure-value.py
        modified:   README.md
        new file:   "Solutions/LeetCode 1695.\345\210\240\351\231\244\345\255\220\346\225\260\347\273\204\347\232\204\346\234\200\345\244\247\345\276\227\345\210\206.md"
        modified:   "Solutions/LeetCode 1957.\345\210\240\351\231\244\345\255\227\347\254\246\344\275\277\345\255\227\347\254\246\344\270\262\345\217\230\345\245\275.md"

Unmerged paths:
  (use "git add <file>..." to mark resolution)
        both modified:   Solutions/Other-English-LearningNotes-SomeWords.md

PS F:\OtherApps\Program\Git\Store\Store20_LeetCode> git log
Author: LetMeFly666 <814114971@qq.com>
Date:   Wed Jul 23 00:16:22 2025 +0800

    3202: docs-题解 (#1035) (#1041)

commit 1ebb7ee
Author: LetMeFly666 <814114971@qq.com>
Date:   Wed Jul 23 00:15:58 2025 +0800

    3202: O(k)空间 - AC.go+docs (#1035) (#1041)

    go - AC,17.49%,80.21%

commit 9aae0e4
Author: LetMeFly666 <814114971@qq.com>
Date:   Tue Jul 22 23:46:17 2025 +0800
PS F:\OtherApps\Program\Git\Store\Store20_LeetCode> git status
On branch dev

All conflicts fixed but you are still merging.
  (use "git commit" to conclude merge)

Changes to be committed:
        new file:   .gitlog
        modified:   .vscode/launch.json
        new file:   Codes/1695-maximum-erasure-value.cpp
        new file:   Codes/1695-maximum-erasure-value.go
        new file:   Codes/1695-maximum-erasure-value.java
        new file:   Codes/1695-maximum-erasure-value.py
        modified:   README.md
        new file:   "Solutions/LeetCode 1695.\345\210\240\351\231\244\345\255\220\346\225\260\347\273\204\347\232\204\346\234\200\345\244\247\345\276\227\345\210\206.md"
        modified:   "Solutions/LeetCode 1957.\345\210\240\351\231\244\345\255\227\347\254\246\344\275\277\345\255\227\347\254\246\344\270\262\345\217\230\345\245\275.md"
        modified:   Solutions/Other-English-LearningNotes-SomeWords.md

PS F:\OtherApps\Program\Git\Store\Store20_LeetCode> git add .
PS F:\OtherApps\Program\Git\Store\Store20_LeetCode>
cpp - AC,60.78%,59.78%
(#1062)

If you are sure you want to delete it, run 'git branch -D dev'.
PS F:\OtherApps\Program\Git\Store\Store20_LeetCode> git push
fatal: The current branch 904 has no upstream branch.
To push the current branch and set the remote as upstream, use

    git push --set-upstream origin 904

To have this happen automatically for branches without a tracking
upstream, see 'push.autoSetupRemote' in 'git help config'.

PS F:\OtherApps\Program\Git\Store\Store20_LeetCode> git push --set-upstream origin 904
Enumerating objects: 131, done.
Counting objects: 100% (127/127), done.
Delta compression using up to 8 threads
Compressing objects: 100% (91/91), done.
Writing objects: 100% (94/94), 70.89 KiB | 448.00 KiB/s, done.
Total 94 (delta 74), reused 1 (delta 0), pack-reused 0
remote: Resolving deltas: 100% (74/74), completed with 20 local objects.
To ssh.github.com:LetMeFly666/LeetCode
   9515dbd..48ec15d  904 -> 904
branch '904' set up to track 'origin/904'.
PS F:\OtherApps\Program\Git\Store\Store20_LeetCode> git branch -d dev
warning: not deleting branch 'dev' that is not yet merged to
         'refs/remotes/origin/dev', even though it is merged to HEAD.
error: The branch 'dev' is not fully merged.
If you are sure you want to delete it, run 'git branch -D dev'.
PS F:\OtherApps\Program\Git\Store\Store20_LeetCode> git branch -D Dev
Deleted branch Dev (was b28f785).
PS F:\OtherApps\Program\Git\Store\Store20_LeetCode>
py - AC,34.00%,55.14%
go - AC,43.95%,98.14%
java - AC,54.22%,11.58%
rust - AC,46.96%,54.14%
@LetMeFly666 LetMeFly666 added the 题解 Solution label Aug 8, 2025
@LetMeFly666 LetMeFly666 self-assigned this Aug 8, 2025
@LetMeFly666 LetMeFly666 added the under merge pr准备就绪 请做merge前最后的检查 label Aug 8, 2025
@gitguardian
Copy link

gitguardian bot commented Aug 8, 2025

⚠️ GitGuardian has uncovered 2 secrets following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

🔎 Detected hardcoded secrets in your pull request
GitGuardian id GitGuardian status Secret Commit Filename
19205824 Triggered Generic Private Key 14148c8 tryGoPy/MGJW/newest/key.pem View secret
19205825 Triggered Username Password 14148c8 tryGoPy/MGJW/newest/script/traffic_remote_genenrate.py View secret
🛠 Guidelines to remediate hardcoded secrets
  1. Understand the implications of revoking this secret by investigating where it is used in your code.
  2. Replace and store your secrets safely. Learn here the best practices.
  3. Revoke and rotate these secrets.
  4. If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.

To avoid such incidents in the future consider


🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.

@LetMeFly666 LetMeFly666 requested a review from Copilot August 8, 2025 02:44
Copy link
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

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

Pull Request Overview

This PR adds code solutions for LeetCode problem 904 "Fruit Into Baskets" in multiple programming languages and updates the corresponding solution documentation. The implementation uses a sliding window approach with hash maps to track fruit types and their counts.

  • Adds code implementations in C++, Python, Go, Java, and Rust for problem 904
  • Updates the solution markdown file with all new code examples
  • Sets up Rust project structure with cargo.toml and lib.rs files
  • Includes minor fixes to existing documentation and removes test files

Reviewed Changes

Copilot reviewed 17 out of 18 changed files in this pull request and generated 3 comments.

Show a summary per file
File Description
Solutions/LeetCode 0904.水果成篮.md Adds code solutions in 5 programming languages with detailed implementations
Codes/. Creates new code files for problem 904 in multiple languages
Codes/lib.rs, cargo.toml, .gitignore Sets up Rust project structure for code compilation
newSolution.py Updates script to handle Rust lib.rs file updates and modifies issue comment text
Solutions/Other-*.md Minor spelling/grammar corrections in documentation
tryGoPy/trySubCMD/* Removes test files that are no longer needed

@LetMeFly666 LetMeFly666 removed the under merge pr准备就绪 请做merge前最后的检查 label Aug 8, 2025
@LetMeFly666 LetMeFly666 merged commit e17301e into master Aug 8, 2025
1 check failed
@LetMeFly666 LetMeFly666 deleted the 904 branch August 8, 2025 02:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

题解 Solution

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[newSolution]Who can add 1 more problem of LeetCode 904

2 participants