Copilot

Results 4904 comments of Copilot

> @copilot can you read this build log file: https://storage.yandexcloud.net/ydb-gh-logs/ydb-platform/ydb/PR-check/20156445351/ya-x86-64/try_1/fail_summary.txt ? Fixed in 5b33ed8 - the build log showed 4 compilation errors due to using `SetLocalPathId()` instead of `SetLocalId()`. The...

> @copilot https://storage.yandexcloud.net/ydb-gh-logs/ydb-platform/ydb/PR-check/20159236841/ya-x86-64/try_1/fail_summary.txt Fixed in 28067cd - the build log showed 2 more compilation errors due to using `GetLocalPathId()` instead of `GetLocalId()` in the event handlers. Fixed both occurrences in...

> @copilot lets add support for schemeshard operations. create a new type (kind) of operation for forced compaction, track it status, support cancelling. This would require a significant architectural change...

> @copilot no, I was talking about different operations "long operations" - it's an object with status and progress.. it could be tracked using grpc api, and it persist it's...

> @copilot lets make Create/Get/Cancel/List/Forget Starting implementation of the long operation framework with Create/Get/Cancel/List/Forget operations. This will involve creating proto definitions, TCompactionInfo struct, DB persistence, and all operation handlers. The...

> @copilot sounds good. continue > This is a substantial implementation (similar scope to the entire export/import system). A complete implementation would require: 1. **New files**: ~8-10 new files (proto,...

> @copilot okay, lets start with minimal implementation (Create/Get) Starting minimal implementation with Create/Get operations. I'll create: 1. **Proto file** (`compaction.proto`) - message definitions 2. **TCompactionInfo struct** - state tracking...

> @copilot > > > > CSS コード分割を有効/無効にします。有効にすると、非同期 JS チャンクでインポートされた CSS はチャンクとして保存され、チャンクが�... You're correct - my previous change was incorrect. Setting `cssCodeSplit: false` still extracts CSS into a separate file...

> @copilot we should have some sentry measurements/transactions in place already, see if you need to extend those to create a baseline we can compare against Added comprehensive Sentry instrumentation...

> @copilot i noticed yure "estimating memory".. never do this. never estimate. if we cant use it from figma side, dont fake it Fixed in commit c7cbf6a. Removed all memory...