Intellisence not working for Metals 1.2.0 for scala 2.12.15

[vikas-saxena02]

Hi guys, we are palnning to use Metals in VSCode for developing spark jobs but run into issue where IntelliSence is not working as the version of spark that we use EMR 6.10.0 is built using Scala 2.12.15 which metals takes as an old version as highlighted in the screenshot below. The issue is that IntelliSense seems not to be working which is a must have feature for us. Also, the Doctor is taking the project type as java while its an scala project
Unfortunately we cannot change scala versions as we need to have the same that AWS has used to create spark binaries. Any pointers to solve this will really be appreciated!!

[tgodzik]

Thanks for reporting! Do you indeed have problems with hover, completions etc. ? We actually still publish for that version. Does it say something in the metals log about failing to download mtags?

[vikas-saxena02]

Hi Tomer, It is indeed a problem with hover, autocomplete and referencing functions and variables (control + left click). We have the requisite scala mtags for sure and there are no missing jars issues in metals.log file. Also for some reason doctor shows that the project to be java as shown in snapshot attached before but same code works fine for scala 2.13.12 and doctor reports it to be a scala project. Thanks, Vikas

…

On Mon, 18 Mar 2024, 9:38 pm Tomasz Godzik, ***@***.***> wrote: Thanks for reporting! Do you indeed have problems with hover, completions etc. ? We actually still publish for that version. Does it say something in the metals log about failing to download mtags? — Reply to this email directly, view it on GitHub <#6231 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AVSEDXRAL22BIAXA2NHWFO3YY27ZPAVCNFSM6AAAAABE222II2VHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM4DQMRWGA3TS> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[tgodzik]

Och right, that might be an actual issue. Looks like we don't get scala information about those modules. This might be related to out Bloop maven plugin, it might not work in your case.

If you look into .bloop files and jsons there they will probably be missing any scala information.

Would be great to get a reproduction to try an fix that, but the plugin is located in https://github.com/scalacenter/bloop-maven-plugin and is not that complex, so you might be able to see what is going on.

[vikas-saxena02]

@tgodzik sorry I forgot to ypdate you in this. On my personal laptop, upgrading to Metals. 1.29 fixes the issue. I will try this in the airgap setup in my organisation.

[vikas-saxena02]

@tgodzik just letting you know that upgrading metals did work out for me.