The Vitess 7.0 DocumentationRemotes Since you should have cloned the repository from your fork, the origin remote should look like this: $ git remote -v origin git@github.com:/vitess.git (fetch) origin git@github.com: remote: $ git remote add upstream git@github.com:vitessio/vitess.git $ git remote -v origin git@github.com: /vitess.git (fetch) origin $ git config remote.pushdefault origin $ git config push.default current The first setting saves you from typing origin every time. And with the second setting, Git assumes that the remote branch on the 0 码力 | 254 页 | 949.63 KB | 1 年前3- The Vitess 8.0 DocumentationRemotes Since you should have cloned the repository from your fork, the origin remote should look like this: $ git remote -v origin git@github.com:
/vitess.git (fetch) origin git@github.com: remote: 37 $ git remote add upstream git@github.com:vitessio/vitess.git $ git remote -v origin git@github.com: /vitess.git (fetch) git config remote.pushdefault origin $ git config push.default current 38 The first setting saves you from typing origin every time. And with the second setting, Git assumes that the remote branch on 0 码力 | 331 页 | 1.35 MB | 1 年前3 - The Vitess 6.0 Documentation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160 Unmanaged or remote MySQL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Remotes Since you should have cloned the repository from your fork, the origin remote should look like this: $ git remote -v origin git@github.com:
/vitess.git (fetch) origin git@github.com: remote: $ git remote add upstream git@github.com:vitessio/vitess.git $ git remote -v origin git@github.com: /vitess.git (fetch) origin 0 码力 | 210 页 | 846.79 KB | 1 年前3 - The Vitess 5.0 Documentation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169 Unmanaged or remote MySQL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Remotes Since you should have cloned the repository from your fork, the origin remote should look like this: $ git remote -v origin git@github.com:
/vitess.git (fetch) origin git@github.com: remote: $ git remote add upstream git@github.com:vitessio/vitess.git $ git remote -v origin git@github.com: /vitess.git (fetch) origin 0 码力 | 206 页 | 875.06 KB | 1 年前3 - The Vitess 11.0 DocumentationRemotes Since you should have cloned the repository from your fork, the origin remote should look like this: $ git remote -v origin git@github.com:
/vitess.git (fetch) origin git@github.com: remote: $ git remote add upstream git@github.com:vitessio/vitess.git $ git remote -v origin git@github.com: /vitess.git (fetch) origin $ git config remote.pushdefault origin $ git config push.default current The first setting saves you from typing origin every time. And with the second setting, Git assumes that the remote branch on the 0 码力 | 481 页 | 3.14 MB | 1 年前3 - The Vitess 10.0 Documentation
Remotes Since you should have cloned the repository from your fork, the origin remote should look like this: $ git remote -v origin git@github.com:
/vitess.git (fetch) origin git@github.com: remote: $ git remote add upstream git@github.com:vitessio/vitess.git $ git remote -v origin git@github.com: /vitess.git (fetch) origin $ git config remote.pushdefault origin $ git config push.default current The first setting saves you from typing origin every time. And with the second setting, Git assumes that the remote branch on the 0 码力 | 455 页 | 3.07 MB | 1 年前3 - The Vitess 9.0 DocumentationRemotes Since you should have cloned the repository from your fork, the origin remote should look like this: $ git remote -v origin git@github.com:
/vitess.git (fetch) origin git@github.com: remote: $ git remote add upstream git@github.com:vitessio/vitess.git $ git remote -v origin git@github.com: /vitess.git (fetch) origin $ git config remote.pushdefault origin $ git config push.default current The first setting saves you from typing origin every time. And with the second setting, Git assumes that the remote branch on the 0 码力 | 417 页 | 2.96 MB | 1 年前3 - The Vitess 12.0 DocumentationRemotes Since you should have cloned the repository from your fork, the origin remote should look like this: $ git remote -v origin git@github.com:
/vitess.git (fetch) origin git@github.com: remote: $ git remote add upstream git@github.com:vitessio/vitess.git $ git remote -v origin git@github.com: /vitess.git (fetch) origin $ git config remote.pushdefault origin $ git config push.default current The first setting saves you from typing origin every time. And with the second setting, Git assumes that the remote branch on the 0 码力 | 534 页 | 3.32 MB | 1 年前3 - Vitess security audit*mysqlCallInfoImpl) HTML() template.HTML { return template.HTML("MySQL User: " + mci.user + " Remote Addr: " + 34 Vitess Security Audit, 2023 mci.remoteAddr) } https://github.com/vitessio/vi *gRPCCallInfoImpl) HTML() template.HTML { return template.HTML("Method: " + gci.method + " Remote Addr: " + gci.remoteAddr) } The Vitess maintainers triaged these cases extensively to assess0 码力 | 41 页 | 1.10 MB | 1 年前3
- Pentest-Report Vitess 02.2019Additional testing for filter circumvention did not uncover any methods to successfully achieve Remote Code Execution. All enumerated endpoints were investigated for bypasses of the described protections0 码力 | 9 页 | 155.02 KB | 1 年前3
共 10 条
- 1