Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

StrideCompilerServices doesnt resolve #2073

Closed
IXLLEGACYIXL opened this issue Dec 5, 2023 · 4 comments · Fixed by #2089
Closed

StrideCompilerServices doesnt resolve #2073

IXLLEGACYIXL opened this issue Dec 5, 2023 · 4 comments · Fixed by #2089
Labels
bug Something isn't working

Comments

@IXLLEGACYIXL
Copy link
Collaborator

Release Type:
Current git state
Version:
4.2

Platform(s): Does the problem occur on Windows, Android...?

Describe the bug
No project can resolve the CompilerServices even though every project should
grafik

To Reproduce
Steps to reproduce the behavior:

  1. get latest stride
  2. check analysetools if stride compilerservices is there
  3. its not there

Expected behavior
every project should have it as analyse tool and it should show the rolsyn diagnostics

@IXLLEGACYIXL IXLLEGACYIXL added the bug Something isn't working label Dec 5, 2023
@archanox
Copy link

archanox commented Dec 5, 2023

Ah, I was encountering this issue on Windows on Arm too, I thought it was a me problem. Does this need to be bisected?

@IXLLEGACYIXL
Copy link
Collaborator Author

IXLLEGACYIXL commented Dec 5, 2023

bisected

i have amd 64 bit(standard windows), sooo its on all machines

@IXLLEGACYIXL
Copy link
Collaborator Author

could it be that central package management is causing this?

@Kryptos-FR
Copy link
Member

Kryptos-FR commented Dec 30, 2023

could it be that central package management is causing this?

I don't think that's the cause.

I just checked out commit 1fc04d4 (which is where central package management was first merged) and I can see the analysers, though I can't see the rules. I will try to bisect.

edit 1: it is still good at commit ffd71ac.

edit 2: #2061 is the culprit. The fix was related to the build system, but somehow it breaks the analyser resolution. @Eideren
Now that #2055 has been merged, maybe we can revisit this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants