We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
The core and std library merger (#6729) has introduced a few failing tests that seem to be bugs within the lsp itself.
Failing tests: sway-lsp::lib completion sway-lsp::lib publish_diagnostics_dead_code_warning sway-lsp lsp_syncs_with_workspace_edits Failed projects: - Project: match_expressions_or Path: /home/runner/actions-runner/_work/sway/sway/test/src/e2e_vm_tests/test_programs/should_pass/language/match_expressions_or/src/main.sw Error: Exit code: exit status: 1 - Project: match_expressions_unreachable_or Path: /home/runner/actions-runner/_work/sway/sway/test/src/e2e_vm_tests/test_programs/should_pass/language/match_expressions_unreachable_or/src/main.sw Error: Exit code: exit status: 1 - Project: fix_opcode_bug Path: /home/runner/actions-runner/_work/sway/sway/test/src/e2e_vm_tests/test_programs/should_pass/language/fix_opcode_bug/src/main.sw Error: Exit code: signal: 9 (SIGKILL)
The text was updated successfully, but these errors were encountered:
No branches or pull requests
The core and std library merger (#6729) has introduced a few failing tests that seem to be bugs within the lsp itself.
The text was updated successfully, but these errors were encountered: