{"payload":{"feedbackUrl":"https://github.com/orgs/community/discussions/53140","repo":{"id":17420913,"defaultBranch":"master","name":"cargo","ownerLogin":"rust-lang","currentUserCanPush":false,"isFork":false,"isEmpty":false,"createdAt":"2014-03-04T23:20:42.000Z","ownerAvatar":"https://avatars.githubusercontent.com/u/5430905?v=4","public":true,"private":false,"isOrgOwned":true},"refInfo":{"name":"","listCacheKey":"v0:1714756709.0","currentOid":""},"activityList":{"items":[{"before":"3832bd9fffa922f3c2fd8ccc2f82aac908cca38c","after":"bcb6a89c5dbd6997c34bcea165b7ebaef207ffae","ref":"refs/heads/gh-pages","pushedAt":"2024-05-19T02:54:37.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"github-actions[bot]","name":null,"path":"/apps/github-actions","primaryAvatarUrl":"https://avatars.githubusercontent.com/in/15368?s=80&v=4"},"commit":{"message":"Deploy c256d7403145f1a833e06e4f4d250687e8a4342c to gh-pages","shortMessageHtmlLink":"Deploy c256d74 to gh-pages"}},{"before":"0f685f6198ed17afbbf5b8ced4c360fdf840c3ac","after":"c256d7403145f1a833e06e4f4d250687e8a4342c","ref":"refs/heads/master","pushedAt":"2024-05-19T02:54:23.000Z","pushType":"push","commitsCount":2,"pusher":{"login":"bors","name":"bors","path":"/bors","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/3372342?s=80&v=4"},"commit":{"message":"Auto merge of #13929 - ehuss:squelch-unittest-warnings, r=weihanglo\n\nSilence warnings running embedded unittests.\n\nThe `util::toml::embedded::test_expand` unittests were printing warnings directly to stderr, circumventing the libtest override. They were displaying ``warning: `package.edition` is unspecified, defaulting to `2021` ``. That warning doesn't look particularly important for those tests, so this changes it to swallow the output.\n\nWe may want to have some kind of utility function for generating a GlobalContext for testing purposes that does this, since this is a repeated pattern.","shortMessageHtmlLink":"Auto merge of #13929 - ehuss:squelch-unittest-warnings, r=weihanglo"}},{"before":"0f685f6198ed17afbbf5b8ced4c360fdf840c3ac","after":"c256d7403145f1a833e06e4f4d250687e8a4342c","ref":"refs/heads/auto-cargo","pushedAt":"2024-05-19T02:25:58.000Z","pushType":"push","commitsCount":2,"pusher":{"login":"bors","name":"bors","path":"/bors","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/3372342?s=80&v=4"},"commit":{"message":"Auto merge of #13929 - ehuss:squelch-unittest-warnings, r=weihanglo\n\nSilence warnings running embedded unittests.\n\nThe `util::toml::embedded::test_expand` unittests were printing warnings directly to stderr, circumventing the libtest override. They were displaying ``warning: `package.edition` is unspecified, defaulting to `2021` ``. That warning doesn't look particularly important for those tests, so this changes it to swallow the output.\n\nWe may want to have some kind of utility function for generating a GlobalContext for testing purposes that does this, since this is a repeated pattern.","shortMessageHtmlLink":"Auto merge of #13929 - ehuss:squelch-unittest-warnings, r=weihanglo"}},{"before":"79b9126b5668c1f18eeb4fb2cb1a095b32db8b06","after":"3832bd9fffa922f3c2fd8ccc2f82aac908cca38c","ref":"refs/heads/gh-pages","pushedAt":"2024-05-19T01:53:00.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"github-actions[bot]","name":null,"path":"/apps/github-actions","primaryAvatarUrl":"https://avatars.githubusercontent.com/in/15368?s=80&v=4"},"commit":{"message":"Deploy 0f685f6198ed17afbbf5b8ced4c360fdf840c3ac to gh-pages","shortMessageHtmlLink":"Deploy 0f685f6 to gh-pages"}},{"before":"198ba31be3ed5dfd75ebc76e38da6e0443323b95","after":"0f685f6198ed17afbbf5b8ced4c360fdf840c3ac","ref":"refs/heads/master","pushedAt":"2024-05-19T01:52:43.000Z","pushType":"push","commitsCount":2,"pusher":{"login":"bors","name":"bors","path":"/bors","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/3372342?s=80&v=4"},"commit":{"message":"Auto merge of #13930 - ehuss:squelch-git-output, r=weihanglo\n\nFix warning output in build_with_symlink_to_path_dependency_with_build_script_in_git\n\nThe test `build_with_symlink_to_path_dependency_with_build_script_in_git` was emitting a large warning block (in my case, about init.defaultBranch) because it was running `git` without filtering its output. It's not clear to me why this test was shelling out to `git` instead of using the built-in test support functions. From what I can tell, this should be exactly equivalent, and silences the warning output.","shortMessageHtmlLink":"Auto merge of #13930 - ehuss:squelch-git-output, r=weihanglo"}},{"before":"198ba31be3ed5dfd75ebc76e38da6e0443323b95","after":"0f685f6198ed17afbbf5b8ced4c360fdf840c3ac","ref":"refs/heads/auto-cargo","pushedAt":"2024-05-19T01:23:51.000Z","pushType":"push","commitsCount":2,"pusher":{"login":"bors","name":"bors","path":"/bors","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/3372342?s=80&v=4"},"commit":{"message":"Auto merge of #13930 - ehuss:squelch-git-output, r=weihanglo\n\nFix warning output in build_with_symlink_to_path_dependency_with_build_script_in_git\n\nThe test `build_with_symlink_to_path_dependency_with_build_script_in_git` was emitting a large warning block (in my case, about init.defaultBranch) because it was running `git` without filtering its output. It's not clear to me why this test was shelling out to `git` instead of using the built-in test support functions. From what I can tell, this should be exactly equivalent, and silences the warning output.","shortMessageHtmlLink":"Auto merge of #13930 - ehuss:squelch-git-output, r=weihanglo"}},{"before":"e41007f0bbe9bb30b22e0e7553e91a99f777af8d","after":"b1cd6490a4d654a7270acc387108ca11ec15c861","ref":"refs/heads/try","pushedAt":"2024-05-19T00:54:03.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"bors","name":"bors","path":"/bors","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/3372342?s=80&v=4"},"commit":{"message":"Auto merge of #13929 - ehuss:squelch-unittest-warnings, r=\n\nSilence warnings running embedded unittests.\n\nThe `util::toml::embedded::test_expand` unittests were printing warnings directly to stderr, circumventing the libtest override. They were displaying ``warning: `package.edition` is unspecified, defaulting to `2021` ``. That warning doesn't look particularly important for those tests, so this changes it to swallow the output.\n\nWe may want to have some kind of utility function for generating a GlobalContext for testing purposes that does this, since this is a repeated pattern.","shortMessageHtmlLink":"Auto merge of #13929 - ehuss:squelch-unittest-warnings, r=<try>"}},{"before":"eff37342ab02de31b5da1f204a0153dc570e7fb6","after":"e41007f0bbe9bb30b22e0e7553e91a99f777af8d","ref":"refs/heads/try","pushedAt":"2024-05-19T00:52:58.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"bors","name":"bors","path":"/bors","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/3372342?s=80&v=4"},"commit":{"message":"Auto merge of #13930 - ehuss:squelch-git-output, r=\n\nFix warning output in build_with_symlink_to_path_dependency_with_build_script_in_git\n\nThe test `build_with_symlink_to_path_dependency_with_build_script_in_git` was emitting a large warning block (in my case, about init.defaultBranch) because it was running `git` without filtering its output. It's not clear to me why this test was shelling out to `git` instead of using the built-in test support functions. From what I can tell, this should be exactly equivalent, and silences the warning output.","shortMessageHtmlLink":"Auto merge of #13930 - ehuss:squelch-git-output, r=<try>"}},{"before":"1c6293e81c58da0bcaf7062b57d884fdb83ab1c0","after":"79b9126b5668c1f18eeb4fb2cb1a095b32db8b06","ref":"refs/heads/gh-pages","pushedAt":"2024-05-18T22:41:18.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"github-actions[bot]","name":null,"path":"/apps/github-actions","primaryAvatarUrl":"https://avatars.githubusercontent.com/in/15368?s=80&v=4"},"commit":{"message":"Deploy 198ba31be3ed5dfd75ebc76e38da6e0443323b95 to gh-pages","shortMessageHtmlLink":"Deploy 198ba31 to gh-pages"}},{"before":"986dac36af2b1b8a554761426370891aa2b4dcc9","after":"198ba31be3ed5dfd75ebc76e38da6e0443323b95","ref":"refs/heads/master","pushedAt":"2024-05-18T22:41:04.000Z","pushType":"push","commitsCount":3,"pusher":{"login":"bors","name":"bors","path":"/bors","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/3372342?s=80&v=4"},"commit":{"message":"Auto merge of #13572 - linyihai:multi-dep-same-name, r=ehuss\n\nFix: Make path dependencies with the same name stays locked\n\n### What does this PR try to resolve?\nFixes: https://github.com/rust-lang/cargo/issues/13405\n\nThis is a workround based on https://github.com/rust-lang/cargo/issues/13405#issuecomment-1930496807\n\n### How should we test and review this PR?\nfirst commit will pass, second commit fixed it and update test.\n\n### Additional information","shortMessageHtmlLink":"Auto merge of #13572 - linyihai:multi-dep-same-name, r=ehuss"}},{"before":"986dac36af2b1b8a554761426370891aa2b4dcc9","after":"198ba31be3ed5dfd75ebc76e38da6e0443323b95","ref":"refs/heads/auto-cargo","pushedAt":"2024-05-18T22:12:28.000Z","pushType":"push","commitsCount":3,"pusher":{"login":"bors","name":"bors","path":"/bors","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/3372342?s=80&v=4"},"commit":{"message":"Auto merge of #13572 - linyihai:multi-dep-same-name, r=ehuss\n\nFix: Make path dependencies with the same name stays locked\n\n### What does this PR try to resolve?\nFixes: https://github.com/rust-lang/cargo/issues/13405\n\nThis is a workround based on https://github.com/rust-lang/cargo/issues/13405#issuecomment-1930496807\n\n### How should we test and review this PR?\nfirst commit will pass, second commit fixed it and update test.\n\n### Additional information","shortMessageHtmlLink":"Auto merge of #13572 - linyihai:multi-dep-same-name, r=ehuss"}},{"before":"ea558b95b4f18d4720d6ea033d4b5a6bc301eeee","after":"1c6293e81c58da0bcaf7062b57d884fdb83ab1c0","ref":"refs/heads/gh-pages","pushedAt":"2024-05-18T22:04:36.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"github-actions[bot]","name":null,"path":"/apps/github-actions","primaryAvatarUrl":"https://avatars.githubusercontent.com/in/15368?s=80&v=4"},"commit":{"message":"Deploy 986dac36af2b1b8a554761426370891aa2b4dcc9 to gh-pages","shortMessageHtmlLink":"Deploy 986dac3 to gh-pages"}},{"before":"0de7f2ec6c39d68022e6b97a39559d2f4dbf3930","after":"986dac36af2b1b8a554761426370891aa2b4dcc9","ref":"refs/heads/master","pushedAt":"2024-05-18T22:04:22.000Z","pushType":"push","commitsCount":2,"pusher":{"login":"bors","name":"bors","path":"/bors","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/3372342?s=80&v=4"},"commit":{"message":"Auto merge of #13931 - ehuss:standard_lib-no-sysroot, r=weihanglo\n\nTemporarily fix standard_lib tests on linux.\n\nThis fixes the standard_lib tests which are broken in the latest nightly. The latest nightly now requires rust-lld to be in the sysroot for x86_64-unknown-linux-gnu. This broke these tests which were trying to verify that the standard library is not required. This temporarily removes this validation, but we should have some way of enforcing it (https://github.com/rust-lang/wg-cargo-std-aware/issues/31).\n\ncc https://github.com/rust-lang/rust/issues/125246","shortMessageHtmlLink":"Auto merge of #13931 - ehuss:standard_lib-no-sysroot, r=weihanglo"}},{"before":"62f1a51a53d52591fe91eda226c203414ee35a57","after":"986dac36af2b1b8a554761426370891aa2b4dcc9","ref":"refs/heads/auto-cargo","pushedAt":"2024-05-18T21:34:39.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"bors","name":"bors","path":"/bors","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/3372342?s=80&v=4"},"commit":{"message":"Auto merge of #13931 - ehuss:standard_lib-no-sysroot, r=weihanglo\n\nTemporarily fix standard_lib tests on linux.\n\nThis fixes the standard_lib tests which are broken in the latest nightly. The latest nightly now requires rust-lld to be in the sysroot for x86_64-unknown-linux-gnu. This broke these tests which were trying to verify that the standard library is not required. This temporarily removes this validation, but we should have some way of enforcing it (https://github.com/rust-lang/wg-cargo-std-aware/issues/31).\n\ncc https://github.com/rust-lang/rust/issues/125246","shortMessageHtmlLink":"Auto merge of #13931 - ehuss:standard_lib-no-sysroot, r=weihanglo"}},{"before":"0de7f2ec6c39d68022e6b97a39559d2f4dbf3930","after":"62f1a51a53d52591fe91eda226c203414ee35a57","ref":"refs/heads/auto-cargo","pushedAt":"2024-05-18T19:50:05.000Z","pushType":"push","commitsCount":3,"pusher":{"login":"bors","name":"bors","path":"/bors","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/3372342?s=80&v=4"},"commit":{"message":"Auto merge of #13572 - linyihai:multi-dep-same-name, r=ehuss\n\nFix: Make path dependencies with the same name stays locked\n\n### What does this PR try to resolve?\nFixes: https://github.com/rust-lang/cargo/issues/13405\n\nThis is a workround based on https://github.com/rust-lang/cargo/issues/13405#issuecomment-1930496807\n\n### How should we test and review this PR?\nfirst commit will pass, second commit fixed it and update test.\n\n### Additional information","shortMessageHtmlLink":"Auto merge of #13572 - linyihai:multi-dep-same-name, r=ehuss"}},{"before":"3a6f531c76830d601574e53a0b79da70be204eba","after":"ea558b95b4f18d4720d6ea033d4b5a6bc301eeee","ref":"refs/heads/gh-pages","pushedAt":"2024-05-17T17:24:24.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"github-actions[bot]","name":null,"path":"/apps/github-actions","primaryAvatarUrl":"https://avatars.githubusercontent.com/in/15368?s=80&v=4"},"commit":{"message":"Deploy 0de7f2ec6c39d68022e6b97a39559d2f4dbf3930 to gh-pages","shortMessageHtmlLink":"Deploy 0de7f2e to gh-pages"}},{"before":"2b8804475d0be02ae311b2ebb10cf39a9974857e","after":"0de7f2ec6c39d68022e6b97a39559d2f4dbf3930","ref":"refs/heads/master","pushedAt":"2024-05-17T17:24:08.000Z","pushType":"push","commitsCount":6,"pusher":{"login":"bors","name":"bors","path":"/bors","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/3372342?s=80&v=4"},"commit":{"message":"Auto merge of #13913 - Urgau:check-cfg-lints-sub-config, r=epage\n\nAdd special `check-cfg` lint config for the `unexpected_cfgs` lint\n\n### What does this PR try to resolve?\n\nThis PR adds a special `check-cfg` lint config for the `unexpected_cfgs` lint, as it was decided by T-cargo (in today's meeting).\n\nThe goal of this lint config is to provide a simple and cost-less alternative to the build-script `cargo::rustc-check-cfg` instruction.\n\n```toml\n[lints.rust]\nunexpected_cfgs = { level = \"warn\", check-cfg = ['cfg(foo, values(\"bar\"))'] }\n```\n\n### How should we test and review this PR?\n\nI recommand reviewing commit by commit; and looking at all the new tests added in `check_cfg.rs`, I tried making them as exhaustive as I could, many of them are very similar to their non-config counterpart.\n\n### Additional information\n\nI didn't add *(actually removed from the 1st version of this PR)* the possibility to omit the `level` field if `check-cfg` is specified, https://github.com/rust-lang/cargo/pull/13913#discussion_r1600609229.\n\nRegarding the implementation, I tried making it is as straight forward as possible, nothing over-engineered or complex.\n\nr? `@epage` (or `@weihanglo` maybe)","shortMessageHtmlLink":"Auto merge of #13913 - Urgau:check-cfg-lints-sub-config, r=epage"}},{"before":"2b8804475d0be02ae311b2ebb10cf39a9974857e","after":"0de7f2ec6c39d68022e6b97a39559d2f4dbf3930","ref":"refs/heads/auto-cargo","pushedAt":"2024-05-17T16:54:55.000Z","pushType":"push","commitsCount":6,"pusher":{"login":"bors","name":"bors","path":"/bors","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/3372342?s=80&v=4"},"commit":{"message":"Auto merge of #13913 - Urgau:check-cfg-lints-sub-config, r=epage\n\nAdd special `check-cfg` lint config for the `unexpected_cfgs` lint\n\n### What does this PR try to resolve?\n\nThis PR adds a special `check-cfg` lint config for the `unexpected_cfgs` lint, as it was decided by T-cargo (in today's meeting).\n\nThe goal of this lint config is to provide a simple and cost-less alternative to the build-script `cargo::rustc-check-cfg` instruction.\n\n```toml\n[lints.rust]\nunexpected_cfgs = { level = \"warn\", check-cfg = ['cfg(foo, values(\"bar\"))'] }\n```\n\n### How should we test and review this PR?\n\nI recommand reviewing commit by commit; and looking at all the new tests added in `check_cfg.rs`, I tried making them as exhaustive as I could, many of them are very similar to their non-config counterpart.\n\n### Additional information\n\nI didn't add *(actually removed from the 1st version of this PR)* the possibility to omit the `level` field if `check-cfg` is specified, https://github.com/rust-lang/cargo/pull/13913#discussion_r1600609229.\n\nRegarding the implementation, I tried making it is as straight forward as possible, nothing over-engineered or complex.\n\nr? `@epage` (or `@weihanglo` maybe)","shortMessageHtmlLink":"Auto merge of #13913 - Urgau:check-cfg-lints-sub-config, r=epage"}},{"before":"03bb6d68f3abbae7849b6ad575695920c4441e8d","after":"3a6f531c76830d601574e53a0b79da70be204eba","ref":"refs/heads/gh-pages","pushedAt":"2024-05-17T15:36:56.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"github-actions[bot]","name":null,"path":"/apps/github-actions","primaryAvatarUrl":"https://avatars.githubusercontent.com/in/15368?s=80&v=4"},"commit":{"message":"Deploy 2b8804475d0be02ae311b2ebb10cf39a9974857e to gh-pages","shortMessageHtmlLink":"Deploy 2b88044 to gh-pages"}},{"before":"8d68ed4fb2554ae7ff2f0a3193c2651e31ee4e1e","after":"2b8804475d0be02ae311b2ebb10cf39a9974857e","ref":"refs/heads/master","pushedAt":"2024-05-17T15:36:41.000Z","pushType":"push","commitsCount":4,"pusher":{"login":"bors","name":"bors","path":"/bors","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/3372342?s=80&v=4"},"commit":{"message":"Auto merge of #13924 - weihanglo:registry, r=epage\n\nrefactor: more comments and variable rename","shortMessageHtmlLink":"Auto merge of #13924 - weihanglo:registry, r=epage"}},{"before":"8d68ed4fb2554ae7ff2f0a3193c2651e31ee4e1e","after":"2b8804475d0be02ae311b2ebb10cf39a9974857e","ref":"refs/heads/auto-cargo","pushedAt":"2024-05-17T15:05:38.000Z","pushType":"push","commitsCount":4,"pusher":{"login":"bors","name":"bors","path":"/bors","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/3372342?s=80&v=4"},"commit":{"message":"Auto merge of #13924 - weihanglo:registry, r=epage\n\nrefactor: more comments and variable rename","shortMessageHtmlLink":"Auto merge of #13924 - weihanglo:registry, r=epage"}},{"before":"ed24b23f63f4d8b8ef2b15d8b21ec51165222eeb","after":"03bb6d68f3abbae7849b6ad575695920c4441e8d","ref":"refs/heads/gh-pages","pushedAt":"2024-05-16T14:24:09.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"github-actions[bot]","name":null,"path":"/apps/github-actions","primaryAvatarUrl":"https://avatars.githubusercontent.com/in/15368?s=80&v=4"},"commit":{"message":"Deploy 8d68ed4fb2554ae7ff2f0a3193c2651e31ee4e1e to gh-pages","shortMessageHtmlLink":"Deploy 8d68ed4 to gh-pages"}},{"before":"fc13634f78023381b55452fa7f4d7a974449a5e8","after":"8d68ed4fb2554ae7ff2f0a3193c2651e31ee4e1e","ref":"refs/heads/master","pushedAt":"2024-05-16T14:23:52.000Z","pushType":"push","commitsCount":3,"pusher":{"login":"bors","name":"bors","path":"/bors","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/3372342?s=80&v=4"},"commit":{"message":"Auto merge of #13920 - weihanglo:git-safe-directory, r=ehuss\n\ntest: set safe.directory for git repo in apache container\n\n### What does this PR try to resolve?\n\nFailure in container tests due to a new version of `git` package in Alpine Linux Package repository.\n\nSee also \n\n### How should we test and review this PR?\n\nAlpine Linux Package repository 3.19 just bumped git package to 2.43.4 from 2.43.0.\nThe docker image `httpd:2.4-alpine` we use in container tests failed due to the git version bump.\nThe `httpd` log shown that\n\n```\n240.10.0.1 - - [16/May/2024:03:52:36 +0000] \"GET /repos/bar.git/info/refs?service=git-upload-pack HTTP/1.1\" 500 -\n[16/May/2024:03:52:36 +0000] 240.10.0.1 TLSv1.3 TLS_AES_256_GCM_SHA384 \"GET /repos/bar.git/info/refs?service=git-upload-pack HTTP/1.1\" -\nfatal: detected dubious ownership in repository at '/repos/bar.git'\nTo add an exception for this directory, call:\n\n git config --global --add safe.directory /repos/bar.git\n```\n\ngit/git@f4aa8c8bb11dae6e769cd930565173808cbb69c8 is likely the commit causing problems.\n\nSo I ended up adding `git config --system --add safe.directory '*'` to the Dockerfile of apache container.\nNote that we need `--system` instead of `--global` because `httpd` are running under the other user www-data, not root.","shortMessageHtmlLink":"Auto merge of #13920 - weihanglo:git-safe-directory, r=ehuss"}},{"before":"fc13634f78023381b55452fa7f4d7a974449a5e8","after":"8d68ed4fb2554ae7ff2f0a3193c2651e31ee4e1e","ref":"refs/heads/auto-cargo","pushedAt":"2024-05-16T13:54:55.000Z","pushType":"push","commitsCount":3,"pusher":{"login":"bors","name":"bors","path":"/bors","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/3372342?s=80&v=4"},"commit":{"message":"Auto merge of #13920 - weihanglo:git-safe-directory, r=ehuss\n\ntest: set safe.directory for git repo in apache container\n\n### What does this PR try to resolve?\n\nFailure in container tests due to a new version of `git` package in Alpine Linux Package repository.\n\nSee also \n\n### How should we test and review this PR?\n\nAlpine Linux Package repository 3.19 just bumped git package to 2.43.4 from 2.43.0.\nThe docker image `httpd:2.4-alpine` we use in container tests failed due to the git version bump.\nThe `httpd` log shown that\n\n```\n240.10.0.1 - - [16/May/2024:03:52:36 +0000] \"GET /repos/bar.git/info/refs?service=git-upload-pack HTTP/1.1\" 500 -\n[16/May/2024:03:52:36 +0000] 240.10.0.1 TLSv1.3 TLS_AES_256_GCM_SHA384 \"GET /repos/bar.git/info/refs?service=git-upload-pack HTTP/1.1\" -\nfatal: detected dubious ownership in repository at '/repos/bar.git'\nTo add an exception for this directory, call:\n\n git config --global --add safe.directory /repos/bar.git\n```\n\ngit/git@f4aa8c8bb11dae6e769cd930565173808cbb69c8 is likely the commit causing problems.\n\nSo I ended up adding `git config --system --add safe.directory '*'` to the Dockerfile of apache container.\nNote that we need `--system` instead of `--global` because `httpd` are running under the other user www-data, not root.","shortMessageHtmlLink":"Auto merge of #13920 - weihanglo:git-safe-directory, r=ehuss"}},{"before":"0215181b1551503cb1509c0493055b13a5a9ab87","after":"eff37342ab02de31b5da1f204a0153dc570e7fb6","ref":"refs/heads/try","pushedAt":"2024-05-15T22:15:41.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"bors","name":"bors","path":"/bors","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/3372342?s=80&v=4"},"commit":{"message":"Auto merge of #13913 - Urgau:check-cfg-lints-sub-config, r=\n\nAdd special `check-cfg` lint config for the `unexpected_cfgs` lint\n\nThis PR adds a special `check-cfg` lint config for the `unexpected_cfgs` lint, as it was decided by T-cargo (in today's meeting).\n\nThe goal of this lint config is to provide a simple and cost-less alternative to the build-script `cargo::rustc-check-cfg` instruction.\n\n```toml\n[lints.rust]\nunexpected_cfgs = { check-cfg = [\"cfg(foo, values(\\\"bar\\\"))\"] }\n```\n\nRegarding the implementation, everything is as straight forward as possible, nothing over-engineered; I added the possibility to omit the `level` field if a sub-config is specified instead, since it seems useful and was easy to implement.\n\nThere are many small-ish commit, I recommend reviewing them independently.\n\nr? `@epage` (or `@weihanglo` maybe)","shortMessageHtmlLink":"Auto merge of #13913 - Urgau:check-cfg-lints-sub-config, r=<try>"}},{"before":"083217bed69aadead9ce182fc0cca9890206e487","after":"ed24b23f63f4d8b8ef2b15d8b21ec51165222eeb","ref":"refs/heads/gh-pages","pushedAt":"2024-05-15T15:07:12.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"github-actions[bot]","name":null,"path":"/apps/github-actions","primaryAvatarUrl":"https://avatars.githubusercontent.com/in/15368?s=80&v=4"},"commit":{"message":"Deploy fc13634f78023381b55452fa7f4d7a974449a5e8 to gh-pages","shortMessageHtmlLink":"Deploy fc13634 to gh-pages"}},{"before":"0ea330d5a45536b30388f03d40b1d916ae6b4fd9","after":"fc13634f78023381b55452fa7f4d7a974449a5e8","ref":"refs/heads/master","pushedAt":"2024-05-15T15:06:58.000Z","pushType":"push","commitsCount":6,"pusher":{"login":"bors","name":"bors","path":"/bors","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/3372342?s=80&v=4"},"commit":{"message":"Auto merge of #13917 - weihanglo:resolve, r=epage\n\nrefactor: misc refactors for `ops::resolve`\n\n### What does this PR try to resolve?\n\nThis is a preparation for another `-Zpatch-files` experiment,\nso that the future PR can move things around easier without too many conflicts.\n\n### How should we test and review this PR?\n\nGenerally they shouldn't affect anything existing behavior.\na6230e348b786420e83cc8220e0d8f4c61084a12 might be a bit dubious,\nthough I believe preloading workspace members is kinda idempotent\nand registering patches/lockfile never cares about it.\n\n### Additional information","shortMessageHtmlLink":"Auto merge of #13917 - weihanglo:resolve, r=epage"}},{"before":"0ea330d5a45536b30388f03d40b1d916ae6b4fd9","after":"fc13634f78023381b55452fa7f4d7a974449a5e8","ref":"refs/heads/auto-cargo","pushedAt":"2024-05-15T14:39:19.000Z","pushType":"push","commitsCount":6,"pusher":{"login":"bors","name":"bors","path":"/bors","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/3372342?s=80&v=4"},"commit":{"message":"Auto merge of #13917 - weihanglo:resolve, r=epage\n\nrefactor: misc refactors for `ops::resolve`\n\n### What does this PR try to resolve?\n\nThis is a preparation for another `-Zpatch-files` experiment,\nso that the future PR can move things around easier without too many conflicts.\n\n### How should we test and review this PR?\n\nGenerally they shouldn't affect anything existing behavior.\na6230e348b786420e83cc8220e0d8f4c61084a12 might be a bit dubious,\nthough I believe preloading workspace members is kinda idempotent\nand registering patches/lockfile never cares about it.\n\n### Additional information","shortMessageHtmlLink":"Auto merge of #13917 - weihanglo:resolve, r=epage"}},{"before":"70d954d65cd82baead08d65dbcf2ae53a7361b37","after":"083217bed69aadead9ce182fc0cca9890206e487","ref":"refs/heads/gh-pages","pushedAt":"2024-05-15T13:13:18.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"github-actions[bot]","name":null,"path":"/apps/github-actions","primaryAvatarUrl":"https://avatars.githubusercontent.com/in/15368?s=80&v=4"},"commit":{"message":"Deploy 0ea330d5a45536b30388f03d40b1d916ae6b4fd9 to gh-pages","shortMessageHtmlLink":"Deploy 0ea330d to gh-pages"}},{"before":"2f17770a15b5e6abe3348d4fcefc08b223e05968","after":"0ea330d5a45536b30388f03d40b1d916ae6b4fd9","ref":"refs/heads/master","pushedAt":"2024-05-15T13:13:01.000Z","pushType":"push","commitsCount":3,"pusher":{"login":"bors","name":"bors","path":"/bors","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/3372342?s=80&v=4"},"commit":{"message":"Auto merge of #13898 - stevenengler:cargo-add-perms, r=weihanglo\n\nPreserve file permissions on unix during `write_atomic`\n\n### What does this PR try to resolve?\n\nFixes #13896.\n\n> When you run `cargo add`, it changes the file permissions of `Cargo.toml` to 600 (user read+write only). This is a little bit painful when you're building the code as a different user than the user writing the code, for example if you're running the code in a container. This applies to `cargo remove` as well. I tested this behaviour on Cargo 1.78.0 and nightly.\n\nI'm not entirely sure how permissions are handled on Windows, but the tempfile lib [doesn't seem to support them](https://docs.rs/tempfile/3.10.1/tempfile/struct.Builder.html#windows-and-others), so I haven't changed the behaviour on Windows.\n\nOnly the user/group/other read/write/execute permission bits are copied.\n\nThis PR sets the permissions ~twice~ once:\n~1. When creating the file. This has the umask applied, but means that we don't create a file that is more permissive than the original.~\n2. After the file has been created. This doesn't apply the umask, resulting in the file having the same u/g/o r/w/x permissions as the original file.\n\nSince this PR changes a util function, it has a wider scope than just changing the behaviour of `cargo add` and `cargo remove`. `write_atomic` is called from the following functions:\n\n- [`migrate_manifests`](https://github.com/rust-lang/cargo/blob/4de0094ac78743d2c8ff682489e35c8a7cafe8e4/src/cargo/ops/fix.rs#L340)\n- [`update_manifest_with_new_member`](https://github.com/rust-lang/cargo/blob/4de0094ac78743d2c8ff682489e35c8a7cafe8e4/src/cargo/ops/cargo_new.rs#L1008)\n- [`LocalManifest::write`](https://github.com/rust-lang/cargo/blob/4de0094ac78743d2c8ff682489e35c8a7cafe8e4/src/cargo/util/toml_mut/manifest.rs#L299)\n- [`gc_workspace`](https://github.com/rust-lang/cargo/blob/4de0094ac78743d2c8ff682489e35c8a7cafe8e4/src/bin/cargo/commands/remove.rs#L274)\n\n### How should we test and review this PR?\n\nUnit test was added (`cargo test -p cargo-util write_atomic_permissions`).","shortMessageHtmlLink":"Auto merge of #13898 - stevenengler:cargo-add-perms, r=weihanglo"}}],"hasNextPage":true,"hasPreviousPage":false,"activityType":"all","actor":null,"timePeriod":"all","sort":"DESC","perPage":30,"cursor":"djE6ks8AAAAETeF4kQA","startCursor":null,"endCursor":null}},"title":"Activity ยท rust-lang/cargo"}