# Weird coding popups

**URL:** <https://forum.fuel.network/t/weird-coding-popups/7176>\
**Category:** General\
**Tags:** feedback\
**Created:** [December 6, 2024, 8:23am UTC](https://forum.fuel.network/t/weird-coding-popups/7176 "2024-12-06T08:23:30Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![eesheng](https://avatars.discourse-cdn.com/v4/letter/e/2bfe46/32.png) [@eesheng](https://forum.fuel.network/u/eesheng)\
**Post date:** [December 6, 2024, 8:23am UTC](https://forum.fuel.network/t/weird-coding-popups/7176/1 "2024-12-06T08:23:30Z")

</div>

Why does this keeps on happening? I’m using Visual Studio Code. Restarting extension code seems to help for 2 seconds.

 ![image](https://us1.discourse-cdn.com/flex022/uploads/fuel/original/2X/f/faf7565037df518f001147590bc271caeccf81f1.png)

---

<div class="post-metadata">

**Author:** ![Josh](https://avatars.discourse-cdn.com/v4/letter/j/45deac/32.png) [@Josh](https://forum.fuel.network/u/Josh)\
**Post date:** [December 6, 2024, 8:27am UTC](https://forum.fuel.network/t/weird-coding-popups/7176/2 "2024-12-06T08:27:32Z")

</div>

what version of forc-lsp are you using. Looks like you are using an old buggy version.

can you run

```auto
forc-lsp --version

```

---

<div class="post-metadata">

**Author:** ![eesheng](https://avatars.discourse-cdn.com/v4/letter/e/2bfe46/32.png) [@eesheng](https://forum.fuel.network/u/eesheng)\
**Post date:** [December 6, 2024, 8:31am UTC](https://forum.fuel.network/t/weird-coding-popups/7176/3 "2024-12-06T08:31:49Z")

</div>

> [@Josh](#):
>
> `forc-lsp --version`

Currently it is `forc-lsp 0.66.5`

---

<div class="post-metadata">

**Author:** ![Josh](https://avatars.discourse-cdn.com/v4/letter/j/45deac/32.png) [@Josh](https://forum.fuel.network/u/Josh)\
**Post date:** [December 6, 2024, 8:35am UTC](https://forum.fuel.network/t/weird-coding-popups/7176/4 "2024-12-06T08:35:05Z")

</div>

interesting. I’m happy to take a look at what’s going on if you want to allow me access to the code base. Or if there is a minimal reproducible example you can send over.

My github is @joshuabatty

---

<div class="post-metadata">

**Author:** ![eesheng](https://avatars.discourse-cdn.com/v4/letter/e/2bfe46/32.png) [@eesheng](https://forum.fuel.network/u/eesheng)\
**Post date:** [December 6, 2024, 12:56pm UTC](https://forum.fuel.network/t/weird-coding-popups/7176/5 "2024-12-06T12:56:41Z")

</div>

> [@Josh](#):
>
> @joshuabatty

I was testing with the multiasset vault. Not sure if it’s a Rust issue where they auto hint out such types.

> **[Sway Standards | Fuel Docs](https://docs.fuel.network/docs/sway-standards/src-6-vault/)**
>
> Official documentation for Sway Standards

---

<div class="post-metadata">

**Author:** ![eesheng](https://avatars.discourse-cdn.com/v4/letter/e/2bfe46/32.png) [@eesheng](https://forum.fuel.network/u/eesheng)\
**Post date:** [December 6, 2024, 2:28pm UTC](https://forum.fuel.network/t/weird-coding-popups/7176/6 "2024-12-06T14:28:44Z")

</div>

Hmm is it a problem linked to rust analyzer?

Similar weird popups such as:

 ![image](https://us1.discourse-cdn.com/flex022/uploads/fuel/original/2X/9/9b1e5deffc58040c9031f1c1d87d32466bcc9a07.png)

To be more explicit, you can see the grey lines `:u64` auto showing up. It gets annoying sometimes where it glitches similar to the original post.  
 ![image](https://us1.discourse-cdn.com/flex022/uploads/fuel/original/2X/b/b6a989681f1d7d58b21bb4cccf438b1493d334cd.png)

Another weird issue is underlining problems that doesn’t exists, I can compile and run test successfully:  
 ![image](https://us1.discourse-cdn.com/flex022/uploads/fuel/original/2X/f/f50b196b713aabd9d2249f90c165a504720d3da3.png)