Stefano299
commented
2 months ago I have the same problem on PopOS using AMD radeon graphics
Open HarshNarayanJha opened 2 months ago
Stefano299
commented
2 months ago I have the same problem on PopOS using AMD radeon graphics
ConradIrwin
commented
2 months ago Interesting that it seems to block on the system. Could you please try again with strace -ftT and see if we can see which calls are blocking for a while.
We had a similar bug on X11 where we'd block waiting to query for settings for multiple seconds, so hopefully we can identify the problem and remove it from the critical path.
Stefano299
commented
2 months ago I get something like this: log.txt
HarshNarayanJha
commented
2 months ago UPDATE: these are the timings just after a fresh reboot
________________________________________________________
Executed in 1.25 secs fish external
usr time 0.52 millis 521.00 micros 0.00 millis
sys time 3.48 millis 145.00 micros 3.33 millisRunning with strace produces a 18MB logfile! Do you only need certain lines of it?
Stefano299
commented
2 months ago It opens in about 15-20 seconds for me
ConradIrwin
commented
2 months ago @Stefano299 How did you generate that strace? it seems to be missing the first ~13 seconds of events (based on pid 5298). I think (after you've made sure there are no other instances of zed running) that running strace -ftT zed --foreground should work, but I'm not an expert. (It may as @HarshNarayanJha says be quite a large file!).
That said, there's still some odd looking stuff in here:
/sys/bus/pci tree. We open each device 4-5 times, and some of your PCI devices are very slow to respond (e.g. reading /sys/bus/pci/devices/0000:00:01.1/config takes ~450ms and we do it 4 times!).Not sure exactly why yet, but it seems like at the least we should only do this once, and ideally we should not do it at all during app boot.
@HarshNarayanJha I'm looking for things that take time, or just seem off. If you don't want to upload the whole log try:
zed-editor process (probably the one with the most stuff going on).<[1-9]. for things that take >1s, or <0.[1-9] for 100ms or more (etc.)Stefano299
commented
2 months ago Thanks, I did it wrong. I found the problem, while starting it I get like infinite lines like this: [pid 7193] 07:09:16 openat(AT_FDCWD, "/sys/bus/pci/devices/0000:00:18.3/config", O_RDONLY) = 78 <0.000013> [pid 7193] 07:09:16 read(78, "\"\20|\26\0\0\0\0\0\0\0\6\0\0\200\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 48) = 48 <0.000011> [pid 7193] 07:09:16 close(78) = 0 <0.000007> [pid 7193] 07:09:16 openat(AT_FDCWD, "/sys/bus/pci/devices/0000:04:00.5/config", O_RDONLY) = 78 <0.000014> [pid 7193] 07:09:16 read(78, "\"\20\342\25\6\0\20\0`\0\200\4\20\0\200\0\0\0h\201\0\0\0\0\0\0\0\0\0\0\0\0"..., 48) = 48 <0.012762> [pid 7193] 07:09:16 close(78) = 0 <0.000062> [pid 7193] 07:09:16 openat(AT_FDCWD, "/sys/bus/pci/devices/0000:00:18.1/config", O_RDONLY) = 78 <0.000106> [pid 7193] 07:09:16 read(78, "\"\20z\26\0\0\0\0\0\0\0\6\0\0\200\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 48) = 48 <0.000096> [pid 7193] 07:09:16 close(78) = 0 <0.000050> [pid 7193] 07:09:16 openat(AT_FDCWD, "/sys/bus/pci/devices/0000:02:00.0/config", O_RDONLY) = 78 <0.000037> [pid 7193] 07:09:16 read(78, "\303\24\26\6\6\4\20\0\0\0\200\2\20\0\0\0\f\0\0\2\177\0\0\0\4\0\200\201\0\0\0\0"..., 48) = 48 <0.001217> [pid 7193] 07:09:16 close(78) = 0 <0.000008> [pid 7193] 07:09:16 openat(AT_FDCWD, "/sys/bus/pci/devices/0000:00:01.0/config", O_RDONLY) = 78 <0.000014> [pid 7193] 07:09:16 read(78, "\"\20\267\24\0\0\0\0\1\0\0\6\0\0\200\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 48) = 48 <0.000015> [pid 7193] 07:09:16 close(78) = 0 <0.000007> [pid 7193] 07:09:16 openat(AT_FDCWD, "/sys/bus/pci/devices/0000:04:00.3/config", O_RDONLY) = 78 <0.000014> [pid 7193] 07:09:16 read(78, "\"\20\35\26\7\4\20\0\0000\3\f\20\0\200\0\4\0000\201\0\0\0\0\0\0\0\0\0\0\0\0"..., 48) = 48 <0.140692> [pid 7193] 07:09:16 close(78) = 0 <0.000030> [pid 7193] 07:09:16 openat(AT_FDCWD, "/sys/bus/pci/devices/0000:00:02.3/config", O_RDONLY) = 78 <0.000065> [pid 7193] 07:09:16 read(78, "\"\20\272\24\7\4\20\0\0\0\4\6\20\0\201\0\0\0\0\0\0\0\0\0\0\2\2\0\361\1\0 "..., 48) = 48 <0.000041> [pid 7193] 07:09:16 close(78) = 0 <0.000014> [pid 7193] 07:09:16 openat(AT_FDCWD, "/sys/bus/pci/devices/0000:00:04.0/config", O_RDONLY) = 78 <0.000026> [pid 7193] 07:09:16 read(78, "\"\20\267\24\0\0\0\0\1\0\0\6\0\0\200\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 48) = 48 <0.000030> [pid 7193] 07:09:16 close(78) = 0 <0.000017> [pid 7193] 07:09:16 openat(AT_FDCWD, "/sys/bus/pci/devices/0000:00:14.3/config", O_RDONLY) = 78 <0.000021> [pid 7193] 07:09:16 read(78, "\"\20\16y\17\0 \2Q\0\1\6\0\0\200\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 48) = 48 <0.000034> [pid 7193] 07:09:16 close(78) = 0 <0.000017> [pid 7193] 07:09:16 openat(AT_FDCWD, "/sys/bus/pci/devices/0000:04:00.1/config", O_RDONLY) = 78 <0.000023> [pid 7193] 07:09:16 read(78, "\2\20@\26\6\4\20\0\0\0\3\4\20\0\200\0\0\200l\201\0\0\0\0\0\0\0\0\0\0\0\0"..., 48) = 48 <0.015009> [pid 7193] 07:09:16 close(78) = 0 <0.000089> [pid 7193] 07:09:16 openat(AT_FDCWD, "/sys/bus/pci/devices/0000:01:00.0/config", O_RDONLY) = 78 <0.000166> [pid 7193] 07:09:16 read(78, "\336\20\342%\0\0\20\0\241\0\0\3\20\0\0\0\0\0\0\200\f\0\0\0~\0\0\0\f\0\0\0"..., 48) = 48 <0.346766> [pid 7193] 07:09:16 close(78) = 0 <0.000059> [pid 7193] 07:09:16 openat(AT_FDCWD, "/sys/bus/pci/devices/0000:00:00.2/config", O_RDONLY) = 78 <0.000071>
This is what is making zed start so slow on my machine.
ConradIrwin
commented
2 months ago Does seem that way. So now the question is why :D. My suspicion is that this is coming from vulkan, but it does seem like we're probably doing this work more often than we need.
Is there any pattern of what happens before this in the logs? In the trace that you sent it looked like we were also connecting to the X server three times, though enumerating the PCI bus 4-5 times.
Feel free to just upload the log here if it's easier.
HarshNarayanJha
commented
2 months ago It's not that I don't want to upload that big file, but I though it may be useless for you, but in that case, I found things that take
But this output doesn't seem very informative to me 😅. So here is the full log
After the laptop is running for 1 hr or so, running zeditor launch time averages at 6-7 seconds.
One interesting behavior I caught when running zeditor with strace strace -ftT zeditor --foreground &> /tmp/zed_strace.log launches it much slower (maybe because of too much logging), but the theme I have in settings applies after a delay, as it launches with some light mode theme.
Here is the clip demonstrating that:
https://github.com/user-attachments/assets/88f3465b-dc43-4c4e-9be9-4a375d63be90
This is not the case with normal launches.
Stefano299
commented
2 months ago Does seem that way. So now the question is why :D. My suspicion is that this is coming from vulkan, but it does seem like we're probably doing this work more often than we need.
Is there any pattern of what happens before this in the logs? In the trace that you sent it looked like we were also connecting to the X server three times, though enumerating the PCI bus 4-5 times.
Feel free to just upload the log here if it's easier.
I'm sorry, I don't know how to send you the whole log.... I tried doing " > output.txt" but it didn't work. The output is too big and the beginning gets erased in the terminal window...
HarshNarayanJha
commented
2 months ago Does seem that way. So now the question is why :D. My suspicion is that this is coming from vulkan, but it does seem like we're probably doing this work more often than we need. Is there any pattern of what happens before this in the logs? In the trace that you sent it looked like we were also connecting to the X server three times, though enumerating the PCI bus 4-5 times. Feel free to just upload the log here if it's easier.
I'm sorry, I don't know how to send you the whole log.... I tried doing " > output.txt" but it didn't work. The output is too big and the beginning gets erased in the terminal window...
Actually, the whole output just gets logged to stdout and stderr, so you can't really redirect it to a file. You have to redirect both stdout and stderr using &> output.txt, just as I did
strace -ftT zeditor --foreground &> /tmp/zed_strace.logThanks, this is the log: zed_strace.log
claytonwramsey
commented
2 months ago It looks like I had the same issue as well. Notably, this only occurred when I disabled the dedicated GPU on my hybrid-graphics laptop. Boot times are fine with the dedicated NVIDIA GPU enabled.
First, I disabled the dGPU with envycontrol:
sudo envycontrol -s integratedThen, when running Zed, I saw the same startup issues. Here's an strace from running Zed:
Also, here's Zed.log.
Environment:
## Hardware Information:
- **Hardware Model:** Dell Inc. XPS 15 9530
- **Memory:** 32.0 GiB
- **Processor:** 13th Gen Intel® Core™ i9-13900H × 20
- **Graphics:** Intel® Graphics (RPL-P)
- **Disk Capacity:** (null)
## Software Information:
- **Firmware Version:** 1.13.0
- **OS Name:** Fedora Linux 40 (Workstation Edition)
- **OS Build:** (null)
- **OS Type:** 64-bit
- **GNOME Version:** 46
- **Windowing System:** Wayland
- **Kernel Version:** Linux 6.9.8-200.fc40.x86_64Any updates?
lsrrd
commented
1 month ago It looks like I had the same issue as well. Notably, this only occurred when I disabled the dedicated GPU on my hybrid-graphics laptop. Boot times are fine with the dedicated NVIDIA GPU enabled.
To add to this in short: running my system on the iGPU (Intel) with my dGPU disabled with nvidia-utils installed (edit 1: from the arch repos) caused Zed to open in 15-20 seconds. Removing it, and Zed opens like normal. Installed the package again to double check I wasn't hallucinating and can reproduce it.
edit 2: As this is really not my area of expertise, I'm speculating and inferring somewhat. It seems to me the issue, in my instance at least, was the presence of multiple vulkan implementations (provided by vulkan-intel and nvidia-utils) where the GPU it wants to use (??) is not actually available. The Zed logs suggested it always ran on the iGPU.
Stefano299
commented
1 month ago Can you please tell me how to uninstall nvidia utils?
HarshNarayanJha
commented
1 month ago @Stefano299 apt remove nvidia-utils I believe... you need to have the exact package name
pcrock-thmdo
commented
1 month ago To add to this in short: running my system on the iGPU (Intel) with my dGPU disabled with nvidia-utils installed (edit 1: from the arch repos) caused Zed to open in 15-20 seconds. Removing it, and Zed opens like normal. Installed the package again to double check I wasn't hallucinating and can reproduce it.
I can confirm this was the issue for me on Pop!_OS. I had a disabled NVIDIA GPU, was running on integrated graphics. However a boatload of NVIDIA packages were still installed on my machine. After purging them all (according to official instructions), zed launches instantly.
More specifically, a long time ago I ran this command to switch to integrated graphics:
sudo system76-power graphics integratedand today I ran this to resolve the zed startup issue:
sudo apt purge ~nvidia
sudo apt autoremove
systemctl reboot
Check for existing issues
Describe the bug / provide steps to reproduce it
Just installed the latest Zed
v0.143.6-1from arch repos. It is considerably slow to start, taking around 10–15 seconds to launch.This behavior is the same regardless of whether I open an empty workspace or a folder.
Environment
Zed: v0.143.6 (Zed) OS: Linux Wayland garuda unknown Memory: 7.1 GiB Architecture: x86_64
Don't know why unknown is there, but I am on Arch Linux using Hyprland WM. GPU: AMD Integrated
If applicable, add mockups / screenshots to help explain present your vision of the feature
No response
If applicable, attach your Zed.log file to this issue.
Zed.log
2024-07-11T21:03:07+05:30 [INFO] ========== starting zed ========== 2024-07-11T21:03:17+05:30 [INFO] perform; 2024-07-11T21:03:17+05:30 [INFO] read_command; 2024-07-11T21:03:17+05:30 [INFO] read_command; 2024-07-11T21:03:17+05:30 [INFO] socket reader; 2024-07-11T21:03:17+05:30 [INFO] new; 2024-07-11T21:03:17+05:30 [INFO] Opening main db 2024-07-11T21:03:17+05:30 [INFO] Using git binary path: None 2024-07-11T21:03:17+05:30 [INFO] updating SHELL environment variable to value from passwd entry: "/bin/bash" 2024-07-11T21:03:17+05:30 [ERROR] theme not found: Xcode Default Dark 2024-07-11T21:03:17+05:30 [INFO] extensions updated. loading 6, reloading 0, unloading 0 2024-07-11T21:03:17+05:30 [INFO] activate is not implemented on Linux, ignoring the call 2024-07-11T21:03:17+05:30 [INFO] Opening main db 2024-07-11T21:03:17+05:30 [WARN] Theme "macOS Classic Light" is using a deprecated style property: scrollbar_thumb.background. Use `scrollbar.thumb.background` instead. 2024-07-11T21:03:17+05:30 [WARN] Theme "macOS Classic Dark" is using a deprecated style property: scrollbar_thumb.background. Use `scrollbar.thumb.background` instead. 2024-07-11T21:03:17+05:30 [WARN] Theme "macOS Classic Dark2" is using a deprecated style property: scrollbar_thumb.background. Use `scrollbar.thumb.background` instead. 2024-07-11T21:03:17+05:30 [INFO] perform; 2024-07-11T21:03:17+05:30 [INFO] read_command; 2024-07-11T21:03:17+05:30 [INFO] read_command; 2024-07-11T21:03:17+05:30 [INFO] socket reader; 2024-07-11T21:03:17+05:30 [INFO] set environment variables from shell:/bin/bash, path:/usr/local/i386elfgcc/bin:/run/media/harshnj/E_Drive/flutter-sdk/flutter/bin:/run/media/harshnj/E_Drive/flutter-sdk/flutter/bin:/opt/devkitpro/tools/bin:/home/harshnj/.bun/bin:/home/harshnj/.local/share/pnpm:/home/harshnj/.pyenv/shims:/usr/local/i386elfgcc/bin:/run/media/harshnj/E_Drive/flutter-sdk/flutter/bin:/home/harshnj/.local/bin:/home/harshnj/.local/share/nvm/v22.1.0/bin:/home/harshnj/.pyenv/bin:/opt/devkitpro/tools/bin:/usr/local/sbin:/usr/local/bin:/usr/bin:/usr/lib/jvm/default/bin:/usr/bin/site_perl:/usr/bin/vendor_perl:/usr/bin/core_perl:/opt/rocm/bin 2024-07-11T21:03:17+05:30 [INFO] building git repository, `.git` path in the worktree: ".git" 2024-07-11T21:03:17+05:30 [WARN] Theme "Xcode Bare" is using a deprecated style property: scrollbar_thumb.background. Use `scrollbar.thumb.background` instead. 2024-07-11T21:03:17+05:30 [WARN] Theme "Xcode Basic" is using a deprecated style property: scrollbar_thumb.background. Use `scrollbar.thumb.background` instead. 2024-07-11T21:03:17+05:30 [WARN] Theme "Xcode Classic Dark" is using a deprecated style property: scrollbar_thumb.background. Use `scrollbar.thumb.background` instead. 2024-07-11T21:03:17+05:30 [WARN] Theme "Xcode Classic Light" is using a deprecated style property: scrollbar_thumb.background. Use `scrollbar.thumb.background` instead. 2024-07-11T21:03:17+05:30 [WARN] Theme "Xcode Default Dark" is using a deprecated style property: scrollbar_thumb.background. Use `scrollbar.thumb.background` instead. 2024-07-11T21:03:17+05:30 [WARN] Theme "Xcode Default Light" is using a deprecated style property: scrollbar_thumb.background. Use `scrollbar.thumb.background` instead. 2024-07-11T21:03:17+05:30 [WARN] Theme "Xcode High Contrast Dark" is using a deprecated style property: scrollbar_thumb.background. Use `scrollbar.thumb.background` instead. 2024-07-11T21:03:17+05:30 [WARN] Theme "Xcode High Contrast Light" is using a deprecated style property: scrollbar_thumb.background. Use `scrollbar.thumb.background` instead. 2024-07-11T21:03:17+05:30 [WARN] Theme "Xcode Low Key" is using a deprecated style property: scrollbar_thumb.background. Use `scrollbar.thumb.background` instead. 2024-07-11T21:03:17+05:30 [WARN] Theme "Xcode Midnight" is using a deprecated style property: scrollbar_thumb.background. Use `scrollbar.thumb.background` instead. 2024-07-11T21:03:17+05:30 [WARN] Theme "Xcode Presentation Dark" is using a deprecated style property: scrollbar_thumb.background. Use `scrollbar.thumb.background` instead. 2024-07-11T21:03:17+05:30 [WARN] Theme "Xcode Presentation Light" is using a deprecated style property: scrollbar_thumb.background. Use `scrollbar.thumb.background` instead. 2024-07-11T21:03:17+05:30 [WARN] Theme "Xcode Spartan" is using a deprecated style property: scrollbar_thumb.background. Use `scrollbar.thumb.background` instead. 2024-07-11T21:03:17+05:30 [WARN] Theme "Xcode Sunset" is using a deprecated style property: scrollbar_thumb.background. Use `scrollbar.thumb.background` instead. 2024-07-11T21:03:18+05:30 [INFO] Enabling Vulkan Portability 2024-07-11T21:03:18+05:30 [INFO] Enabling color space support 2024-07-11T21:03:18+05:30 [INFO] Adapter "AMD Radeon Graphics (RADV RENOIR)" 2024-07-11T21:03:18+05:30 [INFO] No ray tracing extensions are supported 2024-07-11T21:03:18+05:30 [INFO] Using surface present mode MAILBOX 2024-07-11T21:03:18+05:30 [WARN] Unable to forbid exclusive full screen 2024-07-11T21:03:18+05:30 [INFO] Creating a descriptor pool for at most 16 sets 2024-07-11T21:03:18+05:30 [INFO] Creating a descriptor pool for at most 16 sets 2024-07-11T21:03:18+05:30 [INFO] Initializing Blade pipelines for surface SurfaceInfo { format: Bgra8UnormSrgb, alpha: PreMultiplied } 2024-07-11T21:03:18+05:30 [INFO] Using surface present mode MAILBOX 2024-07-11T21:03:18+05:30 [WARN] Unable to forbid exclusive full screen 2024-07-11T21:03:18+05:30 [INFO] Initializing Blade pipelines for surface SurfaceInfo { format: Bgra8UnormSrgb, alpha: Ignored } 2024-07-11T21:03:18+05:30 [INFO] Opening main db 2024-07-11T21:03:18+05:30 [INFO] Using surface present mode MAILBOX 2024-07-11T21:03:18+05:30 [WARN] Unable to forbid exclusive full screen 2024-07-11T21:03:18+05:30 [INFO] Initializing default prettier with plugins {} 2024-07-11T21:03:18+05:30 [INFO] starting language servers for JavaScript: vtsls, tailwindcss-language-server, eslint 2024-07-11T21:03:18+05:30 [INFO] starting language server "vtsls", path: "/home/harshnj/Documents/NodeJS/fullstackopen", id: 1 2024-07-11T21:03:18+05:30 [INFO] starting language server "tailwindcss-language-server", path: "/home/harshnj/Documents/NodeJS/fullstackopen", id: 2 2024-07-11T21:03:18+05:30 [INFO] starting language server "eslint", path: "/home/harshnj/Documents/NodeJS/fullstackopen", id: 3 2024-07-11T21:03:18+05:30 [INFO] Initializing default prettier with plugins {} 2024-07-11T21:03:18+05:30 [INFO] starting language servers for JavaScript: vtsls, tailwindcss-language-server, eslint 2024-07-11T21:03:18+05:30 [INFO] fetching latest version of language server "vtsls" 2024-07-11T21:03:18+05:30 [INFO] Node runtime install_if_needed 2024-07-11T21:03:18+05:30 [INFO] fetching latest version of language server "tailwindcss-language-server" 2024-07-11T21:03:18+05:30 [INFO] fetching latest version of language server "eslint" 2024-07-11T21:03:18+05:30 [INFO] downloading language server "eslint" 2024-07-11T21:03:19+05:30 [INFO] Initializing default prettier with plugins {} 2024-07-11T21:03:19+05:30 [INFO] starting language servers for JavaScript: vtsls, tailwindcss-language-server, eslint 2024-07-11T21:03:19+05:30 [INFO] Node runtime install_if_needed 2024-07-11T21:03:20+05:30 [INFO] Node runtime install_if_needed 2024-07-11T21:03:20+05:30 [INFO] starting language server. binary path: "/home/harshnj/.local/share/zed/node/node-v18.15.0-linux-x64/bin/node", working directory: "/home/harshnj/Documents/NodeJS/fullstackopen", args: ["/home/harshnj/.local/share/zed/languages/eslint/vscode-eslint-release/2.4.4/vscode-eslint/server/out/eslintServer.js", "--stdio"] 2024-07-11T21:03:21+05:30 [INFO] Language server with id 3 sent unhandled notification window/logMessage: { "type": 3, "message": "ESLint server running in node v18.15.0" } 2024-07-11T21:03:21+05:30 [INFO] Node runtime install_if_needed 2024-07-11T21:03:22+05:30 [INFO] Language server with id 3 sent unhandled notification eslint/status: { "uri": "file:///home/harshnj/Documents/NodeJS/fullstackopen/part2/phonebook/src/App.jsx", "state": 1, "validationTime": 1002 } 2024-07-11T21:03:23+05:30 [INFO] downloading language server "tailwindcss-language-server" 2024-07-11T21:03:23+05:30 [INFO] Node runtime install_if_needed 2024-07-11T21:03:23+05:30 [INFO] starting language server. binary path: "/home/harshnj/.local/share/zed/node/node-v18.15.0-linux-x64/bin/node", working directory: "/home/harshnj/Documents/NodeJS/fullstackopen", args: ["/home/harshnj/.local/share/zed/languages/tailwindcss-language-server/node_modules/.bin/tailwindcss-language-server", "--stdio"] 2024-07-11T21:03:23+05:30 [INFO] Language server with id 2 sent unhandled notification window/logMessage: { "type": 4, "message": "Setting up server…" } 2024-07-11T21:03:23+05:30 [INFO] Language server with id 2 sent unhandled notification window/logMessage: { "type": 4, "message": "Listening for messages…" } 2024-07-11T21:03:24+05:30 [INFO] downloading language server "vtsls" 2024-07-11T21:03:24+05:30 [INFO] Node runtime install_if_needed 2024-07-11T21:03:25+05:30 [INFO] starting language server. binary path: "/home/harshnj/.local/share/zed/node/node-v18.15.0-linux-x64/bin/node", working directory: "/home/harshnj/Documents/NodeJS/fullstackopen", args: ["/home/harshnj/.local/share/zed/languages/vtsls/node_modules/@vtsls/language-server/bin/vtsls.js", "--stdio"] 2024-07-11T21:03:52+05:30 [INFO] Creating a descriptor pool for at most 16 sets 2024-07-11T21:03:52+05:30 [INFO] Creating a descriptor pool for at most 16 sets 2024-07-11T21:03:52+05:30 [INFO] Creating a descriptor pool for at most 256 sets 2024-07-11T21:03:52+05:30 [INFO] Creating a descriptor pool for at most 256 sets 2024-07-11T21:03:52+05:30 [INFO] Initializing default prettier with plugins {} 2024-07-11T21:03:52+05:30 [INFO] starting language servers for TypeScript: vtsls, eslint 2024-07-11T21:03:52+05:30 [INFO] Initializing default prettier with plugins {} 2024-07-11T21:03:52+05:30 [INFO] starting language servers for TypeScript: vtsls, eslint 2024-07-11T21:03:52+05:30 [INFO] starting language servers for JavaScript: vtsls, tailwindcss-language-server, eslint 2024-07-11T21:03:52+05:30 [INFO] Initializing default prettier with plugins {} 2024-07-11T21:03:52+05:30 [INFO] starting language servers for TypeScript: vtsls, eslint 2024-07-11T21:03:52+05:30 [INFO] starting language servers for JavaScript: vtsls, tailwindcss-language-server, eslint 2024-07-11T21:03:52+05:30 [INFO] Language server with id 3 sent unhandled notification eslint/noLibrary: { "source": { "uri": "file:///home/harshnj/Documents/NodeJS/fullstackopen/part2/phonebook/node_modules/.pnpm/@types+react@18.3.3/node_modules/@types/react/index.d.ts" } } 2024-07-11T21:03:52+05:30 [INFO] Language server with id 3 sent unhandled notification eslint/status: { "uri": "file:///home/harshnj/Documents/NodeJS/fullstackopen/part2/phonebook/src/App.jsx", "state": 1, "validationTime": 75 } 2024-07-11T21:03:52+05:30 [INFO] Language server with id 3 sent unhandled notification eslint/noLibrary: { "source": { "uri": "file:///home/harshnj/Documents/NodeJS/fullstackopen/part2/phonebook/node_modules/.pnpm/@types+react@18.3.3/node_modules/@types/react/index.d.ts" } } 2024-07-11T21:03:52+05:30 [INFO] Language server with id 3 sent unhandled notification eslint/status: { "uri": "file:///home/harshnj/Documents/NodeJS/fullstackopen/part2/phonebook/src/App.jsx", "state": 1, "validationTime": 56 } 2024-07-11T21:03:52+05:30 [INFO] Language server with id 3 sent unhandled notification eslint/noLibrary: { "source": { "uri": "file:///home/harshnj/Documents/NodeJS/fullstackopen/part2/phonebook/node_modules/.pnpm/@types+react@18.3.3/node_modules/@types/react/index.d.ts" } } 2024-07-11T21:03:54+05:30 [INFO] new; 2024-07-11T21:03:54+05:30 [INFO] keep_updated; 2024-07-11T21:03:54+05:30 [INFO] new; 2024-07-11T21:20:34+05:30 [INFO] open paths ["/home/harshnj/.local/share/zed/logs/Zed.log"] 2024-07-11T21:20:36+05:30 [INFO] Using surface present mode MAILBOX 2024-07-11T21:20:36+05:30 [WARN] Unable to forbid exclusive full screen 2024-07-11T21:20:58+05:30 [INFO] Using surface present mode MAILBOX 2024-07-11T21:20:58+05:30 [WARN] Unable to forbid exclusive full screen 2024-07-11T21:21:00+05:30 [INFO] Using surface present mode MAILBOX 2024-07-11T21:21:00+05:30 [WARN] Unable to forbid exclusive full screen 2024-07-11T21:21:15+05:30 [INFO] Using surface present mode MAILBOX 2024-07-11T21:21:15+05:30 [WARN] Unable to forbid exclusive full screen 2024-07-11T21:21:16+05:30 [INFO] Using surface present mode MAILBOX 2024-07-11T21:21:16+05:30 [WARN] Unable to forbid exclusive full screen