~/.config/github-copilot/apps.json not created/saved even though authentication succeeds
- 主要語言
- Vim Script
- 星號
- 11.7k
- 分支
- 810
- PR 合併指標
- 30 天內沒有已合併 PR
描述
I've been successfully using copilot.vim 1.59.0 in Neovim 0.12.2 on Ubuntu 22.04.5 with a corporate Github Copilot subscription; I can verify that authentication succeeds and that completions are successfully processed when I edit code (and if I examine the copilot.vim log). Recently, however, it seems that the plugin isn't saving the authentication token into apps.json. This poses issues with another vim plugin that relies upon copilot.vim for authentication (https://github.com/olimorris/codecompanion.nvim). Any thoughts as to what could be preventing the apps.json file from being created/saved? The ~/.config/github-copilot/ folder appears to be writable, i.e., I can manually save files there. Tried deleting the whole directory before starting Neovim and authenticating; after authentication, the directory was recreated; it contains auth.db, auth.db-shm, auth.db-wal, versions.json, but not apps.json
貢獻指南
研究方向
在 Neovim 中使用 copilot.vim 重現驗證流程,並檢查 copilot.vim 記錄以及 ~/.config/github-copilot/。比較驗證後建立的檔案,尤其是 auth.db、versions.json 和缺少的 apps.json。完成的標準是找出 apps.json 未被儲存的原因,並確認它會為依賴它的驗證整合而建立。
由索引模型根據 Issue 內容生成。
評估
- 技術堆疊
- vim
- 領域
- authentication, devtools
- Issue 類型
- 缺陷
- 難度
- 3/5
- 預估耗時
- 1-2 天
- 活躍度
- 冷清
- 描述清晰度
- 需要釐清
- 新手友好度
- 48/100