Update buckifier to use folly/coro instead of folly/experimental/coro (#14685)#14685
Update buckifier to use folly/coro instead of folly/experimental/coro (#14685)#14685pdillinger wants to merge 1 commit into
Conversation
|
@pdillinger has exported this pull request. If you are a Meta employee, you can view the originating Diff in D103096688. |
✅ clang-tidy: No findings on changed linesCompleted in 0.0s. |
✅ Claude Code ReviewAuto-triggered after CI passed — reviewing commit c8e8a7a Code Review: Update buckifier to use folly/coro instead of folly/experimental/coroPR: Update buckifier to use folly/coro instead of folly/experimental/coro SummaryThis PR fixes a consistency gap between the generated BUCK file and the buckifier script that generates it. A prior change (D102823090) migrated the BUCK file from Verification
FindingsNo issues found. This is a correct, minimal, and low-risk change.
RecommendationApprove. The change is correct, complete, and necessary to prevent the next buckifier run from reverting the folly coro migration. ℹ️ About this responseGenerated by Claude Code. Limitations:
Commands:
|
…facebook#14685) Summary: D102823090 migrated the generated RocksDB BUCK file from `//folly/experimental/coro:*` to `//folly/coro:*`, but did not update the buckifier script that generates it. This leaves the BUCK file and buckifier out of sync — the next buckifier run would revert the BUCK change. Update buckify_rocksdb.py to match, so the generated BUCK file stays consistent with the folly coro migration. Reviewed By: nmk70 Differential Revision: D103096688
c8e8a7a to
1a07528
Compare
…facebook#14685) Summary: D102823090 migrated the generated RocksDB BUCK file from `//folly/experimental/coro:*` to `//folly/coro:*`, but did not update the buckifier script that generates it. This leaves the BUCK file and buckifier out of sync — the next buckifier run would revert the BUCK change. Update buckify_rocksdb.py to match, so the generated BUCK file stays consistent with the folly coro migration. Reviewed By: nmk70 Differential Revision: D103096688
1a07528 to
b4c1c59
Compare
|
This pull request has been merged in fa8f4f1. |
…#14685) Summary: Pull Request resolved: #14685 D100235293 and D102823090 migrated the generated RocksDB BUCK file from `//folly/experimental/coro:*` to `//folly/coro:*`, but did not update the buckifier script that generates it in internal_repo_rocksdb. The next release would revert the change. Update buckify_rocksdb.py to match, so the generated BUCK file stays consistent with the folly coro migration. Reviewed By: nmk70 Differential Revision: D103096688 fbshipit-source-id: 9055769ed5e9893397c7504ada22e21980f59dd2
…facebook#14685) Summary: Pull Request resolved: facebook#14685 D100235293 and D102823090 migrated the generated RocksDB BUCK file from `//folly/experimental/coro:*` to `//folly/coro:*`, but did not update the buckifier script that generates it in internal_repo_rocksdb. The next release would revert the change. Update buckify_rocksdb.py to match, so the generated BUCK file stays consistent with the folly coro migration. Reviewed By: nmk70 Differential Revision: D103096688 fbshipit-source-id: 9055769ed5e9893397c7504ada22e21980f59dd2
Summary:
D102823090 migrated the generated RocksDB BUCK file from
//folly/experimental/coro:*to//folly/coro:*, but did not updatethe buckifier script that generates it. This leaves the BUCK file and
buckifier out of sync — the next buckifier run would revert the BUCK
change.
Update buckify_rocksdb.py to match, so the generated BUCK file stays
consistent with the folly coro migration.
Reviewed By: nmk70
Differential Revision: D103096688