Wsl -shutdown not working for me (WSL2 / Win 21H2).Īs said. See our contributing instructions for assistance. Strace of the failing command, if applicable: (If some_command is failing, then run strace -o some_command.strace -f some_command some_args, and link the contents of some_command.strace in a gist here).įor WSL launch issues, please collect detailed logs. I also added a rule to my firewall rules to allow connections to any port for my WSL 2 ip address. However, I am still not able to connect to my server. Therefore, I followed the instructions as shown in this Microsoft blog post. I understand that localhost can not be reached from windows for wsl 2 server yet. I am unable to connect to my node server (started with firebase serve in my WSL 2 Ubuntu distro). What's wrong / what should be happening instead: Include screen shots if that helps demonstrate the problem.) What you're doing and what's happening: (Copy&paste the full set of specific command-line steps necessary to reproduce the behavior, and their output. Your Windows build number: (Type ver at a Windows Command Prompt) Please direct all Windows crashes and security issues to Ideally, please configure your machine to capture minidumps, repro the issue, and send the minidump from "C:\Windows\minidump". Important: Do not open GitHub issues for Windows crashes (BSODs) or security issues. If this is a console issue (a problem with layout, rendering, colors, etc.), please post to the console issue tracker. If you have a feature request, please post to the UserVoice. Please fill out all the fields! Issues with missing or incomplete issue templates will be closed. bin/ysqlsh -d example -U joe -h 192.168.86.Please use the following bug reporting template to help produce issues which are actionable and reproducible, including all command-line steps necessary to induce the failure condition. Nikhils-MacBook-Pro:yugabyte-2.17.0.0 nikhil$. Please consult deprecation warnings for more details. You can use '-warning-mode all' to show the individual deprecation warnings and determine if they come from your own scripts or plugins.Įxecution optimizations have been disabled for 1 invalid unit(s) of work during this build to ensure correctness. > Run with -info or -debug option to get more log output.ĭeprecated Gradle features were used in this build, making it incompatible with Gradle 8.0. > Run with -stacktrace option to get the stack trace. > Could not resolve org.projectlombok:lombok:1.18.22. > Could not resolve all files for configuration ':lombok'. Please refer to for more details about this problem.Įxecution failed for task ':generateEffectiveLombokConfig'. Reason: An input file collection couldn't be resolved, making it impossible to determine task inputs. In plugin 'io.LombokBasePlugin' type 'io.tasks.LombokConfig' property 'lombokClasspath' cannot be resolved: Failed to resolve imported Maven boms: : nodename nor servname provided, or not known. > Task :generateEffectiveLombokConfig FAILEDĮxecution optimizations have been disabled for task ':generateEffectiveLombokConfig' to ensure correctness due to the following reasons: See the error trace below - Nikhils-MacBook-Pro:yugabytedb-example nikhil$. can you please let me know how I can resolve this Lombok error in Gradle. Getting some build errors with the sample app, and I’m not familiar with how to resolve them.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |