No Syntax/Type Solver

Bug Reports Studio Bugs
,
1

When I use the new beta feature it randomly occurred today with “New Luau Type Solver” all syntax and type solving is gone.

I have 94gb ram, 3090 ti rtx, 9700x 8-core amd cpu

Expected behavior

I expect the syntaxing and type solving to work.

2

Hello! Sorry to hear you’re running into issues with the New Type Solver, but we could use a little more information:

  1. Does this occur on all places?
  2. Does the script analysis widget say anything?
  3. Are you able to disable the new type solver?

If you are comfortable, sharing a place file, such as in a private message, is the best way for us to help figure out the root cause here.

3

Thank you for the response.

It occurs on all places, any script. I see no output when editing scripts, absolutely nothing.

I can disable this beta feature, in doing so everything returns back to normal, pointing to the beta feature.

4

Hum, that’s quite odd. I’d like to help: can you do the following:

  1. Create a new place with the new solver on, confirm that you see the issue;
  2. Publish the place (it can be private);
  3. Open the place again and confirm the above issue occurs;
  4. Paste a link to this place in this thread.
5

After creating a NEW place it works fine, but any existing one prior is buggy.

6

… but any existing one prior is buggy

Are any of the existing ones published places? Even if they’re private.

7

Yes they are, they’re published but private.

8

Here is one of the places:

This has the bug occuring.

9

Is there one you’d be willing to share in a private message?

If you are getting no output, I realize you might be encountering the same issue as this post. There is a fix on the way for that but it will take a bit of time to make it to users.

10

Yes, I would be willing to share in a private message.

11

I’ve been working on converting my framework to be strictly type-checked and have also ran into this issue when using the new type solver. In my case it doesn’t appear to be place specific, but code specific.

I’ve narrowed down the specific cause to be the ModuleScripts that contain all the types I use, which are pretty large (one on the server and one on the client). Type solving and debugging return to normal once I delete these modules and reload Studio, though of course the code won’t properly work without these files. The old solver handles the type modules without issue, but I’d much rather use the new one since it has more accurate type-checking logic I need for my purposes.

@MercuryBromine0 Would you like me to share the place I described above in a private message, or should I wait for the fix that was mentioned in the quote below?

12

@DairyProductsz: feel free to share the place in a private message, in fact opening another DevForum ticket would be best (there should be a dialog of some kind for sharing private info with staff). At worst I’ll confirm it’s the same fix and send you on your way, at best we’ll find out it was a different issue and be able to track it separately.

1 Like
13

Hello! Sorry for the late response, but we’ve released a couple performance improvements for the new solver. The place you provided does take a bit to type check initially, but on my machine (admittedly a beefy MacBook Pro M3 MAX) it’s maybe six seconds?

Please let me know if you’re able to give the new solver a shot again, and if you’re encountering more issues!

14

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.