When building 2.0.0-1.0, version *-TDP-0.1.0-SNAPSHOT is needed

When building ranger in branch ranger-2.0-TDP I have this error:
[INFO] ---------------< org.apache.ranger:ranger-plugins-cred >----------------
[INFO] Building Credential Support 2.0.0-1.0                             [3/57]
[INFO] --------------------------------[ jar ]---------------------------------
Downloading from apache.snapshots: https://repository.apache.org/snapshots/org/apache/hadoop/hadoop-common/3.1.1-TDP-0.1.0-SNAPSHOT/maven-metadata.xml
Downloading from apache.snapshots.https: https://repository.apache.org/content/repositories/snapshots/org/apache/hadoop/hadoop-common/3.1.1-TDP-0.1.0-SNAPSHOT/maven-metadata.xml
Downloading from apache.snapshots.https: https://repository.apache.org/content/repositories/snapshots/org/apache/hadoop/hadoop-common/3.1.1-TDP-0.1.0-SNAPSHOT/hadoop-common-3.1.1-TDP-0.1.0-SNAPSHOT.pom
Downloading from apache.snapshots: https://repository.apache.org/snapshots/org/apache/hadoop/hadoop-common/3.1.1-TDP-0.1.0-SNAPSHOT/hadoop-common-3.1.1-TDP-0.1.0-SNAPSHOT.pom
[WARNING] The POM for org.apache.hadoop:hadoop-common:jar:3.1.1-TDP-0.1.0-SNAPSHOT is missing, no dependency information available
Downloading from apache.snapshots.https: https://repository.apache.org/content/repositories/snapshots/org/apache/hadoop/hadoop-common/3.1.1-TDP-0.1.0-SNAPSHOT/hadoop-common-3.1.1-TDP-0.1.0-SNAPSHOT.jar
Downloading from apache.snapshots: https://repository.apache.org/snapshots/org/apache/hadoop/hadoop-common/3.1.1-TDP-0.1.0-SNAPSHOT/hadoop-common-3.1.1-TDP-0.1.0-SNAPSHOT.jar
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary for ranger 2.0.0-1.0:
[INFO]
[INFO] ranger ............................................. SUCCESS [  2.707 s]
[INFO] Jdbc SQL Connector ................................. SUCCESS [  1.160 s]
[INFO] Credential Support ................................. FAILURE [  0.815 s]
[INFO] Audit Component .................................... SKIPPED
[INFO] Common library for Plugins ......................... SKIPPED
[INFO] Installer Support Component ........................ SKIPPED
[INFO] Credential Builder ................................. SKIPPED
[INFO] Embedded Web Server Invoker ........................ SKIPPED
[INFO] Key Management Service ............................. SKIPPED
[INFO] ranger-plugin-classloader .......................... SKIPPED
[INFO] HBase Security Plugin Shim ......................... SKIPPED
[INFO] HBase Security Plugin .............................. SKIPPED
[INFO] Hdfs Security Plugin ............................... SKIPPED
[INFO] Hive Security Plugin ............................... SKIPPED
[INFO] Knox Security Plugin Shim .......................... SKIPPED
[INFO] Knox Security Plugin ............................... SKIPPED
[INFO] Storm Security Plugin .............................. SKIPPED
[INFO] YARN Security Plugin ............................... SKIPPED
[INFO] Ozone Security Plugin .............................. SKIPPED
[INFO] Ranger Util ........................................ SKIPPED
[INFO] Unix Authentication Client ......................... SKIPPED
[INFO] Security Admin Web Application ..................... SKIPPED
[INFO] KAFKA Security Plugin .............................. SKIPPED
[INFO] SOLR Security Plugin ............................... SKIPPED
[INFO] NiFi Security Plugin ............................... SKIPPED
[INFO] NiFi Registry Security Plugin ...................... SKIPPED
[INFO] Unix User Group Synchronizer ....................... SKIPPED
[INFO] Ldap Config Check Tool ............................. SKIPPED
[INFO] Unix Authentication Service ........................ SKIPPED
[INFO] Unix Native Authenticator .......................... SKIPPED
[INFO] KMS Security Plugin ................................ SKIPPED
[INFO] Tag Synchronizer ................................... SKIPPED
[INFO] Hdfs Security Plugin Shim .......................... SKIPPED
[INFO] Hive Security Plugin Shim .......................... SKIPPED
[INFO] YARN Security Plugin Shim .......................... SKIPPED
[INFO] OZONE Security Plugin Shim ......................... SKIPPED
[INFO] Storm Security Plugin shim ......................... SKIPPED
[INFO] KAFKA Security Plugin Shim ......................... SKIPPED
[INFO] SOLR Security Plugin Shim .......................... SKIPPED
[INFO] Atlas Security Plugin Shim ......................... SKIPPED
[INFO] KMS Security Plugin Shim ........................... SKIPPED
[INFO] ranger-examples .................................... SKIPPED
[INFO] Ranger Examples - Conditions and ContextEnrichers .. SKIPPED
[INFO] Ranger Examples - SampleApp ........................ SKIPPED
[INFO] Ranger Examples - Ranger Plugin for SampleApp ...... SKIPPED
[INFO] Apache Ranger Examples Distribution ................ SKIPPED
[INFO] Ranger Tools ....................................... SKIPPED
[INFO] Atlas Security Plugin .............................. SKIPPED
[INFO] Sqoop Security Plugin .............................. SKIPPED
[INFO] Sqoop Security Plugin Shim ......................... SKIPPED
[INFO] Kylin Security Plugin .............................. SKIPPED
[INFO] Kylin Security Plugin Shim ......................... SKIPPED
[INFO] Presto Security Plugin ............................. SKIPPED
[INFO] Presto Security Plugin Shim ........................ SKIPPED
[INFO] Elasticsearch Security Plugin Shim ................. SKIPPED
[INFO] Elasticsearch Security Plugin ...................... SKIPPED
[INFO] Apache Ranger Distribution ......................... SKIPPED
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time:  5.009 s
[INFO] Finished at: 2023-05-31T08:51:17Z
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal on project ranger-plugins-cred: Could not resolve dependencies for project org.apache.ranger:ranger-plugins-cred:jar:2.0.0-1.0: Could not find artifact org.apache.hadoop:hadoop-common:jar:3.1.1-TDP-0.1.0-SNAPSHOT in apache.snapshots.https (https://repository.apache.org/content/repositories/snapshots) -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/DependencyResolutionException
[ERROR]
[ERROR] After correcting the problems, you can resume the build with the command
[ERROR]   mvn <goals> -rf :ranger-plugins-cred

Fix with #3


fix: change hasura health check url to make auth server work in gcp

Google cloud doesnt support "z" urls - https://stackoverflow.com/questions/43380939/where-does-the-convention-of-using-healthz-for-application-health-checks-come-f
And hasura provides an alternate end point for this https://hasura.io/docs/2.0/api-reference/health/ .
Checklist

[ ] No breaking changes
[X] Tests pass
[X] New features have new tests
[ ] Documentation is updated

Google cloud doesnt support "z" urls - https://stackoverflow.com/questions/43380939/where-does-the-convention-of-using-healthz-for-application-health-checks-come-f

Where does it say that? I couldn't find any reference to it. Do you have any documentation we can reference?
Regarding the change, unfortunately, it isn't good (and doesn't work) for two main reasons:

It is done on the javascript side, which isn't used (we are transitioning to go) so this change basically has no impact.
It is a breaking change as changing the healthz path will break every single deployment

To properly perform this change you will have to:

Add a second healthz endpoint here. Do not change the existing one as any PR modififying it will not be accepted. Adding a second one should be fine.
After you have edited the openapi.yaml you can run go generate ./... to generate some stubs and boilerplate.
You will have to implement the new method added to the server interface (which can just be an alias to this.

Also, don't call the endpoint /hasura/healthz. If the issue is that the endpoint is called healthz we can just add a second one called /health (without the z)

Where does it say that? I couldn't find any reference to it. Do you have any documentation we can reference?

Workloads in Google Cloud cannot have URL paths with /healthz . here is are some references from stackoverflow
here is the proof (hasrua hosted in google Cloud Run)

When hasura-auth container starts, it use this code to check if hasura is UP and healthy. without this check pass, hasura-auth in GCP will not start at all.
I think there is some misunderstanding  here:
@itsmurugappan is asking to use  Hasura's second health endpoint /hasura/healthz instead of /healthz

[!IMPORTANT]
Hasura include both health-check endpoints in all deployment environments. we don't have to do anything for hasura.

I think this change will not have any side-effect

hasura docs

yes, you are completely right. I totally misinterpreted the change. Thanks for the clarification.
However, if you need this change because you are hosting hasura in GCP, wouldn't you also need an alternative /health endpoint for hasura-auth?

since hasura auth health check end point is not called through the loadbalancer by any client we dint need it.

yes, you are completely right. I totally misinterpreted the change. Thanks for the clarification.
However, if you need this change because you are hosting hasura in GCP, wouldn't you also need an alternative /health endpoint for hasura-auth?

Would be nice to have alternative health-check endpoints for all nhost services that won't conflict with GCP.
But as minimum viable solution,  this PR is good enough making it work in GCP.


Typescript Types not available in npm package

Looks like some types were included in v0.9.0 but when I install via npm install @rollbar/react then the correct version is installed but types are still missing.
I think the index.d.ts is not included in the package:

So the types are not available in the code:
error TS7016: Could not find a declaration file for module '@rollbar/react'. <EMAIL_ADDRESS>implicitly has an 'any' type.
  Try `npm i --save-dev @types/rollbar__react` if it exists or add a new declaration (.d.ts) file containing `declare module '@rollbar/react';`

8 import { Provider as RollbarProvider, ErrorBoundary as RollbarErrorBoundary } from '@rollbar/react';

Thanks for fixing this @waltjones , will there be another release soon as latest version is still 0.9.0?

This is now published in v0.10.0. https://github.com/rollbar/rollbar-react/releases/tag/v0.10.0


Add solo scenarios for base game

Created JSON files for all solo scenarios for base game (except Cthulhu), using ids 116-131. These should be changed and ordered once we can move them to their final place.
(Note that this PR does not include the diviner solo scenario.)
I also changed the valid range of scenario numbers, so the added ones could be selected. That should be changed to 1-115 once the scenarios are moved.

Thanks again for this @luksan47 ! :-) I'm now in a position to merge this into dev - still a quite a bit of styling to go on the selector, and the Diviner scenario of course; but this has helped loads :-)

Thanks again for this @luksan47 ! :-) I'm now in a position to merge this into dev - still a quite a bit of styling to go on the selector, and the Diviner scenario of course; but this has helped loads :-)

Happy to help! :)
I'll probably have a look at some other issues as well when I'll have the time :)

Happy to help! :)
I'll probably have a look at some other issues as well when I'll have the time :)


Annotation processor in IntelliJ

I use immutables in a small project: full source code is here GitLab encoding
when I setup my build.gradle as explained in the readme file:
dependencies {
  compileOnly "org.immutables:value:2.2.10:annotations"
  apt         "org.immutables:value:2.2.10"
}

the gradle command line build works.
When I apply the IntelliJ settings for annotation processors as explained in my comment of issue#35, IntelliJ will still not run the annotation processors.
I must also add immutables:values to the compile configuration, like this:
dependencies {
  compileOnly "org.immutables:value:2.2.10:annotations"
  compile         "org.immutables:value:2.2.10"
  apt         "org.immutables:value:2.2.10"
}

Can someone please explain why this is needed?

I'll have a look, but FYI IntelliJ IDEA 2016.3 has an option to delegate build to Gradle; maybe you could try that?
https://www.jetbrains.com/idea/whatsnew/#v2016-3-gradle
(FWIW, I for one manually run a compilation through Gradle whenever I need to rerun annotation processors, I don't let IntelliJ IDEA do it for me)

OK, so ./gradlew idea works as expected (adds org.immutables:value:2.2.10 as a dependency), but the IntelliJ↔Gradle integration does not…
…unless you uncheck Create separate module per source set when importing the project.
I'd love to get better integration with IntelliJ IDEA but that would probably require changes to IntelliJ and/or Gradle. Ideally, annotation processors will eventually be first-class citizens in Gradle so this plugin will no longer be necessary and integration with IntelliJ could be much better. In the mean time, I don't have the bandwidth to even start reverse-engineering and debugging what IntelliJ does, and understand what could make it happy.
As stated in the README, IDE integration is provided as a best-effort, and IntelliJ has too many options and obscure behaviors (not to mention the recent changes to gradle idea in Gradle 3.4).

thanks for the quick reply & the info about the "option to delegate build to Gradle". I didn't know about that, but it sounds great and I'll give it a try.


Show strategies details in about page

Hey @bonustrack, is it about the space about page? :thinking:


Unity console: [error] ~200 errors with GoogleVr/scripts/Controller/Internal/Emulator/phoneEvent.cs

Solved: re-downloaded GoogleVRForUnity.unitypackage in assets folder and imported it again unity


1.7

i have a zip copy of csvfix 1.7 : neilb-csvfix-93804d497be6.zip. let me know if you want to check it out. might be some worthwhile improvements in here. it builds in WSL last time i checked in 2018.

[...]/src/neilb-csvfix-93804d497be6/csvfix/bin$ ./csvfix

CSVfix 1.7 (Dec  5 2018)
Copyright (C) 2014 Neil Butterworth
This is free software; see the source for copying conditions. There is NO
warranty, not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

Configuration file: none

csvfix is a CSV stream editor
use 'csvfix help' to see a list of commands
use 'csvfix help command' to see help on a specific command

Hey, it would be nice if you could share the copy, though I cannot promise that I find the time to include it soon.

i put it on my dropbox here; let me know once you grab it and i'll take it down.

also, someone forked your repo and fixed a bug, calling it 1.6.1 ... hehe. might be worth a PR?

Thanks, got it.
Hope I will find the time.
Regards,
Michael

Am 29.04.2022 um 21:00 schrieb Ron Wilson @.***>:
i put it on my dropbox here https://www.dropbox.com/s/xpz0lwh84cjgo43/neilb-csvfix-93804d497be6.zip?dl=0; let me know once you grab it and i'll take it down.
—
Reply to this email directly, view it on GitHub https://github.com/wlbr/csvfix/issues/1#issuecomment-1113631510, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAFU6M5LH6LCVN2JITCUGC3VHQWVLANCNFSM5UUTSOQQ.
You are receiving this because you commented.

yw!


Complex analysis

Lofty goal: state Cauchy's integral formula. Even loftier -- let's prove it!
Note: this might be really really hard.

@VeraXZheng has been looking at M2PM3 problem sheets. These are hard, not least because they're constantly mentioning pi, which we don't have! TODO NEED sin and cos.


1.3.3 Doesn't include any javascript files

Describe the bug
When upgrading to remix-auth-auth0 1.3.3
Your Example Website or App
https://github.com/lavabear/remix-auth-auth0-example
Steps to Reproduce the Bug or Issue

Create new project
Depend on remix-auth-auth0
npm install

Expected behavior
As a user I expect there to be javascript files in this library release
Screenshots or Videos
no javascript -
Platform

OS: Linux, Mac
Version: 1.3.3

Additional context
No response

Hi @magicfoodhand! Thank you for the report, a fix has been uploaded on the v1.3.4

Thanks for the quick response!


Livewire 3 closeModal closing issue

The closeModal even works perfectly however if I spawn a child modal then close that then spawn it, then close it, rinse and repeat a few times then the main modal takes multiple clicks on the close button to close the original modal

          Teams

          <button
              class="font-bold hover:bg-gray-100 dark:bg-gray-800 hover:dark:bg-gray-900 dark:text-white px-3 py-1.5 rounded"
              title="Close"
              tabindex="0"
              onclick="Livewire.dispatch('closeModal')"
          >
              X
          </button>

Laravel 10
Livewire 3

Can you try and see if this is still in issue with the latest release? Thanks!

Can you try and see if this is still in issue with the latest release? Thanks!

Just update to version 2.0.8 and it seems to have resolved it.
I'll let you know if any further issue(s).


[Improve] Fix the typo of "Metrics", and fix the npe when jobStatus is null.

Purpose of this pull request

Fix the typo of "Metrics", and fix the npe when jobStatus is null.
Check list

[ ] Code changed are covered with tests, or it does not need tests for reason:
[ ] If any new Jar binary package adding in your PR, please add License Notice according
New License Guide
[ ] If necessary, please update the documentation to describe the new feature. https://github.com/apache/seatunnel/tree/dev/docs

LGTM


Make ConfigListeners aware of Test Methods

Closes #2328
Fixes #2328  .
Did you remember to?

[X] Add test case(s)
[X] Update CHANGES.txt

We encourage pull requests that:

Add new features to TestNG (or)
Fix bugs in TestNG

If your pull request involves fixing SonarQube issues then we would suggest that you please discuss this with the
TestNG-dev before you spend time working on it.

@juherr - Please review.


Liverpool ARU corpus

https://www.liverpool.ac.uk/architecture/research/acoustics-research-unit/speech-corpus/

13ce9c6701e7fc393bcd7bdc1397df41d0b2ad2d


ERROR 403: Forbidden https://developer.salesforce.com/media/salesforce-cli/sfdx-linux-amd64.tar.xz

@mshanemc @WillieRuemmele @shetzel @cristiand391
could you tell us why this url is no longer working?
I'm working with a customer that is downloading sfdx from this place on every ci run. I'm going to change it, but first I would like to know why I'm seeing 403 - Forbidden
From my computer:

From Github:

Hi @AllanOricil
yes, this was deleted on purpose. I remember we deleted this one last year and got a lot reports from customers still using it so we restored it and mentioned it will be deleted in the future.
For context: that tarball had a very old version of the CLI, back then customer mentioned they found that tarball via our docs (which are versioned, google was showing an old frozen version that we couldn't update).
Install the CLI with a TAR File:
https://developer.salesforce.com/docs/atlas.en-us.sfdx_setup.meta/sfdx_setup/sfdx_setup_install_cli.htm#sfdx_setup_install_cli_linux

@Shahul9891NL yep, that's a node error and you might be on an old linux distro:
https://github.com/forcedotcom/cli/issues/1788

yeah, you can install the CLI via npm as mentioned in the linked issue.

weird that almost nobody use docker images in their ci builds


Drop is not returing path on MacOS to Sequoia

let filePath = await drop()

dev(filePath)

after I drop files from finder:

Looks like I missed a breaking change note: https://www.electronjs.org/docs/latest/breaking-changes#removed-filepath
I'll get it fixed ASAP and post another release.

@achtan Can you test drop with this build?
https://github.com/script-kit/app/releases/tag/v3.1.13

@johnlindquist it's working! thanks


Update Composer dependencies (2021-04-07-00-08)

Visual regression test passed!
View the visual regression test report


✨ add the browser package

Pull out the browser package from web
https://github.com/Shopify/web/tree/master/packages/%40shopify/browser

[x] Add more test
[x] Add Docs

@michenly I updated this branch with some docs and more tests, could you take a look? :)

Closing this PR for now as we can replicate the koa middleware's functionality by just passing the user-agent and letting consumers use their own parsing logic.


Mapwriter's minimap render broken

@fewizz code is here: https://github.com/Vectron/mapwriter

what would be the best place to get the max blockid that you changed without being dependant on your mod?
i still have a hardcoded reference in the mod to 4096 for max blocks that i use to build some arrays.

I'm changing final var "MAX_BLOCK_ID" in GameData class(in fml). [P.S.] (https://github.com/fewizz/mapwriter/releases)

unfortunatly that field is private.
as for the changes if i understand it right it will break if your mod is not installed right? (not counting the refference to your mod)

yep...


asorted changes

includes #44 so that should be merged first and then this one rebased
This PR includes small usability improvements (logging) and fixes a corner case when patch files are empty.
It also adds more e2e cases to prove conversion works for those packages.

rebased

@csomh thanks for the rebase!


⚠ Bofrost.de has degraded performance

In cf1101f, Bofrost.de (https://www.bofrost.de) experienced degraded performance:

HTTP code: 200
Response time: 1241 ms

Resolved: Bofrost.de performance has improved in 69872a7 after 52 minutes.


Signet Support

We need to be able to reliably test the wallets on signet. Show and use supported wallets for signet.

Show which wallets support signet
Handle connection to a wallet when switching to signet

i think this is a must as well. our only issue is that most of the ordinal friendly wallets are missing signet support atm, but now that i think about, lets put this on the front burner.

just to keep track. which wallets support signet:

[ ] unisat
[ ] xverse
[ ] oyl
[ ] magic eden
[ ] wizz
[ ] phantom
[ ] okx

Looks like signet PubKey is one in the same as a testnet PubKey so we'll need to look into how we'll broadcast (Sandshrew???) and the necessary flags in all of the methods to fill in the gaps created by wallet insufficiencies.

added here: #40


Show plugins folder button text changed

As for Insomnia-core version 2020.4.0 (Linux Manjaro, at least), the button to open Plugins Folder is now labeled "Reveal Plugins Folder" instead of former "Show plugins folder". Besides that, the opened folder is the parent folder to the plugins folder itself.

Thanks for this issue, we have updated our install instructions on #4!


Update glam requirement from 0.24 to 0.25

Updates the requirements on glam to permit the latest version.

Changelog
Commits

updated-dependencies:

dependency-name: glam dependency-type: direct:production ...

Sorry for this, was trying to merge this to fork, but selected wrong branch.


[Storage] Fix #29929: az storage copy: Fix when wildcard * is in --source-file-path

Related command

Description

Fix when wildcard * is in --source-file-path
Fix #29929
Testing Guide

History Notes

[Storage] Fix #29929: az storage copy: Fix when wildcard * is in --source-file-path

This checklist is used to make sure that common guidelines for a pull request are followed.

[ ] The PR title and description has followed the guideline in Submitting Pull Requests.

[ ] I adhere to the Command Guidelines.

[ ] I adhere to the Error Handling Guidelines.

Thank you for your contribution! We will review the pull request and get back to you soon.


Building freestyle IoT application

Tutorial URL: https://developers.sap.com/tutorials/iotae-comp-buildappmc0.html
In the tutorial mentioned above.
On step number 4, While going through the wizard to create a Freestyle IOT application template, it is mentioned that the data Freestyle-IOTAS-ADVANCEDLIST-THING-ODATA  should be selected. I do not have this in my drop down.
From the research that I've done this can be brought in by using the Update IOT destination option in webide but this requires me to enter some details, I understand that some of these details I already have e.g. the Username and password  and URL for the thing modeller etc.. but I'm not able to get the remaining details. Searching for this only leads me posts of where others are asking the same question or to more content where this is already set up and no information on how this is set up.
Any help here would be greatly appreciated.
Amarpreet.

nothing?

Hi, sorry, for the late reply. Please refer to the getting started section of the leonardo iot page at help.sap.com. It will walk you through all the steps including the retrieval of the service key needed for (re-)creatign the destinations. Regards, Marcus

Thank you for your feedback. We haven't heard from you in a while, so we are closing the issue.
If you still have questions, feel free to reopen the issue.


WSL2 cannot connect to localhost when the service is running on Windows

Please fill out the below information:

Your Windows build number:  (Type ver at a Windows Command Prompt)
Microsoft Windows [Version 10.0.19041.264]

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. Include screenshots if that helps demonstrate the problem.)
I am using an HTTP proxy (ShadowSocks) on windows which is listening on localhost port 1080. Then, I want the command in WSL2 to go through that proxy.

What's wrong / what should be happening instead:
curl: (7) Failed to connect to <IP_ADDRESS> port 1080: Connection refused

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).

For WSL launch issues, please collect detailed logs.

In WSL1, all things are fine. In WSL2 I could connect to the HTTP proxy through my Windows IP. I believe it is caused by WSL2 running in a separate VM.

To simplify the issue, I will show the telnet result, <IP_ADDRESS> is the Windows IP on WSL switch.

hi,
the issue here is that while Windows can see the localhost ports of WSL, the inverse in not true by default.
The ports forwarding are from WSL to Windows. If you do a netstat -an | grep 1080 on WSL, it should return nothing.
However, when you pass it trough the Gateway (WSL switch), it will reach it.
Going forward, you can create a tunnel from Windows to WSL if you need/want to use localhost in your proxy (see: netsh interface portproxy command)
Hope this helps.
WSL Corsair

See also #5131
@nunix do you see this as default behavior with the portproxy on WSL?

Thanks for the reply. I notice that many related issues are all about the network between the two systems. I can create a tunnel or proxy for this. But may I know if the WSL team has a specific plan or eta for the network improvement? Thanks.

let's wait for Build (and here I really am like you, I'm waiting on news) and see if something will done.
@bplasmeijer I remember the SSH, actually right now, netsh is what I use for many of my demos.
still, I do agree with you that the "reverse forwarding" from Windows to WSL2 would be a great improvement

let's wait for Build (and here I really am like you, I'm waiting on news) and see if something will done.
@bplasmeijer I remember the SSH, actually right now, netsh is what I use for many of my demos.
still, I do agree with you that the "reverse forwarding" from Windows to WSL2 would be a great improvement

cc: @craigloewen-msft @benhillis @sirredbeard

hi,
the issue here is that while Windows can see the localhost ports of WSL, the inverse in not true by default.
The ports forwarding are from WSL to Windows. If you do a netstat -an | grep 1080 on WSL, it should return nothing.
However, when you pass it trough the Gateway (WSL switch), it will reach it.
Going forward, you can create a tunnel from Windows to WSL if you need/want to use localhost in your proxy (see: netsh interface portproxy command)
Hope this helps.
WSL Corsair

@nunix can you give us an example? For example; I am trying to access 10134 port from WSL. 10134 port is on Windows assigned by Logitech Options application. I would like to access this port from inside WSL.
Is it possible with the portproxy? Currently my WSL IP is:  <IP_ADDRESS>

same problem , we need to use proxy host on windows

In my case, I am unable to connect to a service running on windows on ANY IP. Always the response is:
~/tcc/network-info$ telnet  <IP_ADDRESS> 5432 Trying <IP_ADDRESS>... telnet: Unable to connect to remote host: Connection refused

@fatichar  turn off your firewall , it cost me serveral hours to get it out . This is difinitely another big problem

Actually, what I am looking for is something even more about proxy between WSL2 and Windows. I am expecting similar experiences like WSL1, where WSL and Windows are using the same address (at least users should be bothered if services on WSL and Windows are listening on different addresses) and follow the same FireWall rules.
If the network is not unified, why not use VM directly and using Samba to share the filesystem? WSL1 provide grate convenience compared with VM. 🤔

hi,
the issue here is that while Windows can see the localhost ports of WSL, the inverse in not true by default.
The ports forwarding are from WSL to Windows. If you do a netstat -an | grep 1080 on WSL, it should return nothing.
However, when you pass it trough the Gateway (WSL switch), it will reach it.
Going forward, you can create a tunnel from Windows to WSL if you need/want to use localhost in your proxy (see: netsh interface portproxy command)
Hope this helps.
WSL Corsair

@nunix can you give us an example? For example; I am trying to access 10134 port from WSL. 10134 port is on Windows assigned by Logitech Options application. I would like to access this port from inside WSL.
Is it possible to do with the portproxy? Currently my WSL IP is: <IP_ADDRESS>

hi @gencer I would suppose it's possible indeed, but on powershell if you do a netstat -an, on which interface is port 10134 mapped?
if it's localhost, then WSL2 cannot reach it indeed, if it's bound to <IP_ADDRESS> then from WSL2 distro, try connecting to the :10134
Let me know the output of netstat and I will provide you the command

@nunix, Unfortunately it binds on localhost as follow:
  TCP    <IP_ADDRESS>:10134        <IP_ADDRESS>:0              LISTENING
  TCP    <IP_ADDRESS>:10134        <IP_ADDRESS>:50456        ESTABLISHED
  TCP    <IP_ADDRESS>:10134        <IP_ADDRESS>:50833        ESTABLISHED
  TCP    <IP_ADDRESS>:10134        <IP_ADDRESS>:56123        ESTABLISHED

However, we make it work on SSH/WSL by making vscode extension runing on UI side. This makes us to access localhost port and data.

you can access Windows port from WSL2 using your local IP like <IP_ADDRESS> instead of localhost, though is not elegant

I also have experienced this issue when accessing my Windows' Redis instance from my project running in WSL2. End up mapping Nameserver to localhost in /etc/hosts.
You can find Nameserver from /etc/resolv.conf, it looks like: nameserver <IP_ADDRESS>
Then you can add line in /etc/hosts like: <IP_ADDRESS> localhost
Created a shell script to make life simpler: https://gist.github.com/toryano0820/6ee3bff2474cdf13e70d972da710996a
Not sure yet if there's a downside with this method. But it works!

This is a complete duplicate of #4619, and all details there are applicable here.  For those not wanting to scroll through everything there, there doesn't seem to be any indication that WSL2 will go back to handling networking in a similar manner to WSL1.  Your two options are 1: Put together some hacks and maybe it'll work, or 2: Revert to WSL1 and hope WSL2 maybe someday changes its approach back to that of WSL1.

I was having similar issues. For me it's a hit or miss scenario. Sometimes it works sometimes it doesn't. I started webpack dev server (<IP_ADDRESS>:500) and accessed it through <IP_ADDRESS>:500, usually browser will wait for bundles to load but today it loaded html page then just disconnected. Reloading no longer loads the page.
I had to disable my vpn before starting local server. After that turning on VPN seems to have no impact on server. I tried shutting down wsl instance (VPN still connected) and starting it again and everything seems to work fine. 🤔

I can confirm that I can connect to the WSL2's localhost using VPN but are unable to do so when I am disconnected.

I personally ended up running containers with the WSL2 integration for services that can run on Docker (Mongo for example)

This is so frustrating

When I upgraded my distro I started having all sorts of DNS problems (even with McAfee firewall turned off) and then today hit this issue of not being able to connect to a port of a process running in Windows from my Ubuntu command line.
I've reverted the distro to WSL 1:    wsl.exe --set-version Ubuntu 1    and things seem to be back to normal now.

When I upgraded my distro I started having all sorts of DNS problems (even with McAfee firewall turned off) and then today hit this issue of not being able to connect to a port of a process running in Windows from my Ubuntu command line.
I've reverted the distro to WSL 1:    wsl.exe --set-version Ubuntu 1    and things seem to be back to normal now.

@fatichar turn off your firewall , it cost me serveral hours to get it out . This is difinitely another big problem

It works . But I want to know why . I have added advanced rule in firewall , But It doesn't work .

So you can't run SSH or any daemons (https://github.com/microsoft/WSL/issues/994#issuecomment-242918148) and you can't connect to servers run as Windows services (SSH e.g. #3173). 😢

This is just a nightmare. Was expecting to work this just out of the box. Can't believe it doesn't.

How is this still not resolved after all these people complaining of this issue for over a year? This is such a problem, my Linux coworkers keep telling me to drop WSL and just dual boot.

I switched to WSL1. WSL1 even performs better under Windows file system. If you choose to use Linux, you still cannot visit Windows ports through localhost.

May 2021 - we're still here! Unexpected behavior of WSL2 networking after each restart of my PC. Everytime I have NEW network issues.
That's terrible to pretend WSL2 is stable and recommend it as default! Without stable networking all the fancy features of WSL2 is totally useless!!! Microsoft, please put efforts on this. First things - first!

I finally got a custom wsl2 kernel with NBD support only to find out I can't connect to the NBD server running under windows.
(I'm trying to mount my ext4 partition in wsl2)

Hey! I was having the same issue and I finally fixed it.
Opening a PowerShell and wsl --shutdown worked for me like a charm! (Make sure to have closed all your wsl terminals first)
Hope it helps!

Hey! J'avais le même problème et je l'ai finalement résolu.
wsl --shutdownsur le PowerShell a fonctionné pour moi comme un charme ! (Assurez-vous d'avoir fermé tous vos terminaux wsl au préalable)
J'espère que cela aide!

That works, but you need  a shutdown/restart WSL2 after each launching Windows ?
Someone knows why ?

Microsoft never changes

What's bizarre is that my desktop does not have this issue but my laptop has this issue at least once a week.
It's incredibly frustrating to get everything setup and run npm start just to realize you have to shut the entire wsl environment down and start all over again.

What's bizarre is that my desktop does not have this issue but my laptop has this issue at least once a week.
It's incredibly frustrating to get everything setup and run npm start just to realize you have to shut the entire wsl environment down and start all over again.

Is there a reason why this hasn't received more attention? This is really, really annoying.

This behavior is insane and has one killer side effect: random and unpredictable service ports conflicts.
Let's assume you have a windows process listening on <IP_ADDRESS> and for example port 9000
Port is visible from Windows
❯❯❯ NETSTAT.EXE -an | grep LISTEN | grep 9000
  TCP    <IP_ADDRESS>:9000           <IP_ADDRESS>:0              LISTENING
  TCP    <IP_ADDRESS>:9000         <IP_ADDRESS>:0              LISTENING
❯❯❯

but from WSL2 you are NOT seeing it:
❯❯❯ netstat -an | grep LISTEN | grep 9000
❯❯❯

Because you are not seeing it, then a wsl2 process can legitimately open the same port for listen, thinking that no other process is using it, like for example (note the absence of reuseaddr and reuseport)
❯❯❯ socat TCP4-LISTEN:9000,bind=<IP_ADDRESS>,fork exec:'/usr/bin/echo'

But this is now visible from both WSL2 and windows ! Two listeners on <IP_ADDRESS>:9000
❯❯❯ NETSTAT.EXE -an | grep LISTEN | grep 9000
  TCP    <IP_ADDRESS>:9000           <IP_ADDRESS>:0              LISTENING
  TCP    <IP_ADDRESS>:9000         <IP_ADDRESS>:0              LISTENING
  TCP    <IP_ADDRESS>:9000         <IP_ADDRESS>:0              LISTENING
❯❯❯

And the WSL2 port can be randomly hit instead of the Windows one causing unpredictable behavior.
From my experience the Windows port seems to be 'winning' most of the time, but if the port is under heavy use it sometimes happen that the connection is accepted by the WSL2 listener.

From my experience the Windows port seems to be 'winning' most of the time, but if the port is under heavy use it sometimes happen that the connection is accepted by the WSL2 listener.

Exactly. Even Windows is not listening on port 9000, connecting to port 9000 on Windows will not always hit port 9000 in WSL2. It sometimes says connection refused. This situation happens where sshd is running in WSL2, and I want to ssh localhost in Windows.

I also saw similar behavior. We are running Docker Desktop with WSL2 feature enabled. We created a container with 443 port exposed. And for some reason after 2 days of stable work the port become inaccessible. One more strange thing for me is that this port is inaccessible when I try to reach it from another host from the same network (https://host) or even from the same host via its IP (https://192.168.x.x), but it is accessible when I using localhost (https://localhost). Does anyone has any ideas what is happening?)

@AlexZablotsky450501 Probably, when Windows is forwarding the listening port from WSL2 to Windows, the listening address is changed to localhost.
Runthis command in WSL2: socat TCP4-LISTEN:2333,bind=<IP_ADDRESS>,fork exec:'/usr/bin/echo'. Then, I opened another terminal and run lsof -i | awk "NR==1 || /LISTEN/", I get,
COMMAND PID  USER   FD   TYPE DEVICE SIZE/OFF NODE NAME
socat   277 david    5u  IPv4  17568      0t0  TCP *:2333 (LISTEN)

It looks fine. But running NETSTAT.EXE -an | grep LISTEN | grep 2333, I only get
  TCP    <IP_ADDRESS>:2333         <IP_ADDRESS>:0              LISTENING

It seems that on Windows, it is listening on localhost:2333 not <IP_ADDRESS>:2333. This is why you cannot connect from another host. I also double checked that it indeed cannot be connected from another host.

It happens from randomly. Usually wsl --shutdown and restart fix the issue. Very annoying, hope there can be a patch for this issue.

It may be useful for you :
I had the same issue when i use VPN on windows to connect to Postgresql (port 5432) server using podman in wsl2/ubuntu. This issue not append with VPN turned off.
It failed on localhost or local ip connection.
BUT
running NETSTAT.EXE -an | grep LISTEN | grep 5432 show me that listening port is on ::1 (ipv6) and not <IP_ADDRESS>.
Then this issue not append anymore when i used ::1 instead of localhost

Es muy molesto , pero al reiniciar wsl2 nuevamente puedo acceder a localhost : https://snippets.khromov.se/how-to-restart-wsl2-windows-subsystem-linux-on-windows-10/

I have checked I have exactly the same issue when connecting through the VPN. I have tried restarting wsl2 and changing the IP address to ::1 as commented above, but nothing works. I will write back if I find a solution.

Workaround for those looking to just run a bash command against your service such as curl you can access localhost through git bash

FYI for folks following this thread: after the latest Windows update, this was no longer broken for me. I don't see this issue mentioned anywhere in the update notes, but it may be worth your time to see if this is now fixed for you, as well.

Can confirm that WSL2 does NOT connect to Windows 10 services via 'localhost' hostname or IP addresses for the following version:
Microsoft Windows [Version 10.0.19042.1237]
(c) Microsoft Corporation. All rights reserved.

C:\Users\Joe Gorse>ver

Microsoft Windows [Version 10.0.19042.1237]

I can confirm that migrating to WSL1 resolves the issue entirely. For a comparison of features, see https://docs.microsoft.com/en-us/windows/wsl/compare-versions
Notably, WSL1 outperforms WSL2 for Windows File access performance. While WSL2 has the "full Linux kernel", it lacks serial device support that works for WSL1. See the link for full details.
Cheers,
Joe

None of the tricks shown here worked for me and I can't switch the listening IP since it's not my code.
Rolling back to WSL1 worked, though. I just followed @jhgorse 's comment and ran on a powershell:
wsl.exe --set-version Ubuntu-20.04 1

This happens very often on my end too (Windows 11 w/ WSL2). Running wsl --shutdown helps, but only for 15 minutes, until I get a new ERR_CONNECTION_REFUSED for localhost.
Any fix yet, other than reverting to WSL1?

My laptop has ip <IP_ADDRESS> in local net. And access the internet from a wsl2. So, I can use ip <IP_ADDRESS> as an external ip address for a laptop on my LAN. I have web server on 8080 port. And into wsl2 I can run:
curl http://<IP_ADDRESS>:8080
It works!
Difficulties:

I have to to open port (8080 for example and other used) in Windows 10. This reduces security.
I have to have a static ip for my laptop on the network or I have to change the dynamic ip and keep this in mind.

Connect from wsl2 to VirtualBox use ssh may be with port mapping use in VirtualBox. For example port mapping tcp <IP_ADDRESS>:2222 to 22. Dont forget open 2222 port on Windows. Then in wsl2 run: ssh @<IP_ADDRESS> -p 2222`
Inconvenient but it works!
I would like a simple solution to appear.

In Powershell, use ipconfig command to find the IPV4 address in  vEthernet (WSL).
Add the normal proxy setting command in ~/.bashrc (e.g. export http_proxy="http://<IP_ADDRESS>:1080") for http & https using the address you found in the above step.
source ~/.bashrc
Close the current wsl terminal and open it again. curl www.google.com should work.

In the ssr software, use Socks5(support UDP) & Allow connections from LAN.

What about setting up SSH Tunneling for this? i tried to solve this last year. i had to recompile the wsl distro, because i read it pulls down network settings for apt functionality

No one here seems to have brought this up... so I will:
In ChromeOS's version of WSL2 called Crostini, all listening ports are automatically forwarded to the host machine and accessible at localhost:1234 or example.localhost:1234. The Android VM doesn't support that, but it has a stable IP address.
P.S.
If I don't figure this out in the next 5 minutes I'm shifting my resources to dual booting Manjaro Gnome... for context I've used ChromeOS for development primarily on my Laptop and Ubuntu on desktop. My new laptop is too fancy for stock Manjaro linux... but I found the Kernel driver that I needed to use and OLED damage will be someone else's problem. The value proposition of Windows has been so negative, I might just erase it and dual boot SteamOS/Manjaro Gnome.

I can confirm that migrating to WSL1 resolves the issue entirely. For a comparison of features, see https://docs.microsoft.com/en-us/windows/wsl/compare-versions
Notably, WSL1 outperforms WSL2 for Windows File access performance. While WSL2 has the "full Linux kernel", it lacks serial device support that works for WSL1. See the link for full details.
The conversion command where "Ubuntu-20.04" may be any from the list wsl.exe -l -v:
wsl.exe --set-version Ubuntu-20.04 1

Not wanting to switch to WSL1, I put my server in a docker container. It works for me.

The application running on WSL2 was unable to access API running on windows host at localhost:5001
This worked for me.

Run ipconfig on windows host
Get the IPV4 Address from Ethernet adapter vEthernet (WSL)  - Eg - <IP_ADDRESS>
Replace localhost:5001  with <IP_ADDRESS>:5001

Why is this taking so long, this can't be that hard to fix, can it? It's just annoying having to deal with stuff like this.

On my end this happened because I was using the WSL Insider Preview from the store. Uninstalling it fixed the issue.

@gpotter2 I just installed that here as well. Did uninstalling it remove any of the files you had saved in your linux subsystem?

@helgatheviking It did not !

I found an old article about localhost and bind <IP_ADDRESS>. I'm posting it in case it can lead anyone who's troubleshooting to something new. https://www.bleepingcomputer.com/news/security/wsl2-now-supports-localhost-connections-from-windows-10-apps/

I found an old article about localhost and bind <IP_ADDRESS>. I'm posting it in case it can lead anyone who's troubleshooting to something new. https://www.bleepingcomputer.com/news/security/wsl2-now-supports-localhost-connections-from-windows-10-apps/

Thanks for the input. However, being able to access a listener/server started in WSL is not the problem, it's the other way around. You can't access servers started in Windows with WSL.
This here is what the issue is about:

This Microsoft page helped solve the problem on my end
https://docs.microsoft.com/en-us/windows/wsl/networking
Check in the "Accessing Windows networking apps from Linux (host IP)" section
Works pretty fine👌

This Microsoft page helped solve the problem on my end
https://docs.microsoft.com/en-us/windows/wsl/networking
Check in the "Accessing Windows networking apps from Linux (host IP)" section
Works pretty fine👌

Yes, this was already mentioned in this thread a few times (e.g. https://github.com/microsoft/WSL/issues/5211#issuecomment-706652801)
Not a fix for the problem though, the issue is that one should be able to access it through localhost, not the IP.

Did anyone got around "connection refused" issue even when using the nameserver ip?
I tried: disabled firewall, fast startup, allowed localhostForwarding, rebooted everything...
Still can't reach windows from WSL2 :(
cat /etc/resolv.conf
> nameserver <IP_ADDRESS>

curl -XGET http://<IP_ADDRESS>:4040/inspect/http -I -v
*   Trying <IP_ADDRESS>:4040...
* TCP_NODELAY set
* connect to <IP_ADDRESS> port 4040 failed: Connection refused
* Failed to connect to <IP_ADDRESS> port 4040: Connection refused
* Closing connection 0
curl: (7) Failed to connect to <IP_ADDRESS> port 4040: Connection refused

@bodinsamuel does your windows host use a proxy lan setting or .pac script? if so, any recent changes?

I also need some kind of localhost proxy from WSL2 to Windows host - in case I want to execute Windows binaries (that´s why WSL to Windows Interop exists), I cannot use IP Address. For example, if I Packer starts VirtualBox VM with port forwarding, it works until the moment when starts waiting for localhost:port. Boom! It ends in a never-ending loop...

I basically avoided this issue by using WSL1 for the past years, but I found a solution that works for me; If you don't encounter this issue often just use $(hostname).local 😒
TLDR; This changes localhost to point to your Windows IP, <IP_ADDRESS> is still available for wsl. In windows you can access WSL via localhost as usual, because windows listens for exposed ports on WSL. Exposes your set windows port(s) via portproxies.

Add this to your /etc/wsl.conf,

[boot]
command="sed -i \"s/<IP_ADDRESS>$(printf '\t')localhost/$(tail -1 /etc/resolv.conf | cut -d' ' -f2)$(printf '\t')localhost/g\" /etc/hosts 2>&1"

This command replaces the default localhost in /etc/hosts to point to your Windows IP, <IP_ADDRESS> is still available for wsl. This might require setting the host in your code to <IP_ADDRESS> for example in vite add server: { host: "<IP_ADDRESS>" } . Services running on Windows might need to be bind to <IP_ADDRESS> or it's local ip for a service to be accessible in WSL.

a. And use this powershell script to configure portproxies fix-wsl2-port-forwading-to-windows-localhost. The firewall rules, might not be necessary but can be helpful if you encounter issues.
b. While the above script also helps you set the firewall rules. You can also execute the following command to set the portproxies manually in (admin) Powershell. In this example ports 8080,27017. (credits above)

$addr='<IP_ADDRESS>'; $ports=@(8080,27017); # set ports according to your use case, what ports from windows should be exposed.
$remoteport = (wsl hostname -I).Trim(); for( $i = 0; $i -lt $ports.length; $i++ ){ $port = $ports[$i]; echo "added portproxy ${addr}:${port} to ${remoteport}:${port}"; iex "netsh interface portproxy delete v4tov4 listenport=$port listenaddress=$addr"; iex "netsh interface portproxy add    v4tov4 listenport=$port listenaddress=$addr connectport=$port connectaddress=$remoteport"; }

You can reset these proxies anytime using netsh interface portproxy reset
This for me solves many of the main issues why I didn't switch, it's not the same as using WSL1. But does the job since you don't have to change localhost host configurations for any of your projects. Which is frustrating when using WSL2. Bonus you can enjoy the latest features such as WSLg and better performance 😀.

As a workaround, I added the following to my .zshenv file to set the IP address of the Windows host to an environment variable:
if [[ -n "$IS_WSL" || -n "$WSL_DISTRO_NAME" ]]; then
  if [[ -z "$WINDOWS_HOST_IP_ADDRESS" ]]; then
    export WINDOWS_HOST_IP_ADDRESS="$(powershell.exe -Command '(Get-NetIPConfiguration | Where-Object { $_.IPv4DefaultGateway -ne $null -and $_.NetAdapter.Status -ne "Disconnected"}).IPv4Address.IPAddress' | tr -d '\r')"
  fi
fi

This way I can use the WINDOWS_HOST_IP_ADDRESS environment variable to proxy requests from WSL2 to the Windows host. For example, I run the Vite development server and proxy API requests to a .NET web application running on the Windows host.

Had the same issue, mentioned workarounds relying only on IPs from /etc/resolv.conf or /etc/hosts are close but not enough, at least for me. Anyone who have this problem should try finding correct IP, for me it was one of those printed by nslookup $(hostname).

Posting my solution to a similar problem.
I was trying to find a way to access RStudio Server (running on WSL2 Ubuntu) from another computer on my local network. RStudio Server is accessible on the Windows Host at localhost:8787. I needed to do both of these:

Create an inbound rule on Windows Defender Firewall for port 8787

Create a forwarding rule for incoming connections to port 8787 to be directed to localhost
Adapted from here. The guide suggests forwarding to the local windows address for the WSL2 VM (wsl hostname -i), which may be the right thing for other people, but in my case RStudio Server is already forwarded to localhost:8787, so that didn't work. I used <IP_ADDRESS> instead and now it works.

This is a frustrating topic.  Exposing all the interfaces from windows via <IP_ADDRESS> is INSECURE.  it would be great and makes most sense to just keep it behave the same as a loopback interface in WSL..

That moment when you scroll the whole thread since 2020 hoping at this point someone would have a good fix but nope 😂😕

That moment when you scroll the whole thread since 2020 hoping at this point someone would have a good fix but nope 😂😕

No joke. I've been following this thread since it was opened, hoping someone far more intelligent than me would have solved this by now. Yet here we are lol

This was fixed in #4619

@obedm503 Thanks for pointing it out. Would have never known it was actually being addressed all this time.
Had to take a few steps to get it working on my local environment. Just thought I'd share. The changes are on a pre-release of WSL so it won't be available through regular update paths.

Update Windows to at least the October 10th build. See more info here: https://github.com/microsoft/WSL/issues/4619#issuecomment-1778054020
Update your WSL to the latest pre-release by running this in CMD or Powershell wsl --update; wsl --update --pre-release. You can view the changes of the pre-release versions here: https://github.com/microsoft/WSL/releases
Update (or create) your .wslconfig file which is located at %USERPROFILE% in explorer. Add the following:[wsl2]
networkingMode=mirrored # add this line if file already exists

(Optional) Shutdown and restart your WSL (after a few seconds) so that the config changes apply.

Since getting it enabled, I haven't had a single issue with my localhost being inaccessible. I could safely enable IPV6 again too.
Side note, pre-release v2.0.5 https://github.com/microsoft/WSL/releases/tag/2.0.5 moved the networkingMode setting from [experimental] to [wsl2].

@dons20 thank you so much, it works fine for me. I have spent a lot of time trying to resolve this problem

Awesome to hear! The release mentions it's a window 11 fix. Anyone on Windows 10 to confirm it works for them as well?

@obedm503 Thanks for pointing it out. Would have never known it was actually being addressed all this time.
Had to take a few steps to get it working on my local environment. Just thought I'd share. The changes are on a pre-release of WSL so it won't be available through regular update paths.
1. Update Windows to at least the October 10th build. See more info here: [[WSL 2] WSL 2 cannot access windows service via localhost:port #4619 (comment)](https://github.com/microsoft/WSL/issues/4619#issuecomment-1778054020)

2. Update your WSL to the latest pre-release by running this in CMD or Powershell `wsl --update; wsl --update --pre-release`. You can view the changes of the pre-release versions here: https://github.com/microsoft/WSL/releases

3. Update (or create) your `.wslconfig` file which is located at `%USERPROFILE%` in explorer. Add the following:
   ```
   [wsl2]
   networkingMode=mirrored # add this line if file already exists
   ```

4. (Optional) Shutdown and restart your WSL (after a few seconds) so that the config changes apply.

Since getting it enabled, I haven't had a single issue with my localhost being inaccessible. I could safely enable IPV6 again too.
Side note, pre-release v2.0.5 https://github.com/microsoft/WSL/releases/tag/2.0.5 moved the networkingMode setting from [experimental] to [wsl2].

This worked for me!

@dons20
This worked for me too on Windows 11. Thank you!

Wow! I just did the steps and finally I can connect to local host services again while in Public LAN or Wifi.
I always had to set the public LAN/Wifi to private (but that did not feed ok exposing the services to everyone in the LAN), I tried playing around with the Firewall, or I switched to private-hotspot (when I had enough connectivity) .
Thanks!! :-)
Finally I can set most LANs/Wifis to public again :-)

@dons20  Thanks! Works for me on W11.
This issue, WSL cannot connect to remote localhost, on my side had to do when the connected WiFi or LAN was set to "public network". On "private network" everything was fine.
With this fix  WSL also connects to localhost while in public network.  :-)

@dons20 cheers mate!
For real, over a year of struggle

Update since Major Version 2.0.9
For step 2, you can just do wsl --update only, no need to do the pre-release anymore.
Original
@obedm503 Thanks for pointing it out. Would have never known it was actually being addressed all this time.
Had to take a few steps to get it working on my local environment. Just thought I'd share. The changes are on a pre-release of WSL so it won't be available through regular update paths.

Update Windows to at least the October 10th build. See more info here: [WSL 2] WSL 2 cannot access windows service via localhost:port #4619 (comment)
Update your WSL to the latest pre-release by running this in CMD or Powershell wsl --update; wsl --update --pre-release. You can view the changes of the pre-release versions here: https://github.com/microsoft/WSL/releases
Update (or create) your .wslconfig file which is located at %USERPROFILE% in explorer. Add the following:[wsl2]
networkingMode=mirrored # add this line if file already exists

(Optional) Shutdown and restart your WSL (after a few seconds) so that the config changes apply.

Since getting it enabled, I haven't had a single issue with my localhost being inaccessible. I could safely enable IPV6 again too.
Side note, pre-release v2.0.5 https://github.com/microsoft/WSL/releases/tag/2.0.5 moved the networkingMode setting from [experimental] to [wsl2].

Works! thank you so much!

As mentioned by this comment: https://github.com/microsoft/WSL/issues/5211#issuecomment-1783883702 fixed by mirrored mode.


Reduce object allocations when using parents

I noticed that every time you call parents, it creates a new Parents instance creating unnecessary object allocations.  This PR lazily loads and stores the Parents object.

@mje113 are you still working on this gem ?


rlImGuiShutdown() causes SEGMENTATION FAULT

System

Pop! Os 22.04 LTS
CLion 2023.3.2
CMake 3.27.8
C++ 17
Raylib 5.0 with internal GLFW and OpenGL 3.3 (compiled as a static library)
Latest rlImGui version

Issue
When closing the application the terminal reads:

INFO: Window closed successfully
Process finished with exit code 139 (interrupted by signal 11:SIGSEGV)

The app runs just fine apart from this.
More information
Debugging I discovered that the error is thrown at line 475 of rlImGui.cpp: ImGui::DestroyContext();, so ImGui_ImplRaylib_Shutdown(); executes without problems

Does this happen in one of the examples or your own code. There is an order dependence when you shutdown rlImGui and raylib. You must shutdown rlImGui before you shutdown raylib, since rlImGui is going to unload a texture from the GPU using raylib.
I can't duplicate this in current code, so I'll need to know more about how you are calling rlImGui and raylib.

Order is correct, code is public (all the rlImGui code is in main.cpp) GdC2024.
Can't really check with the exaples now, Ill'update as soon as I can

I can not duplicate the issue with your code, unless rlImGuiShutdown is somehow called twice..
the high level rlImGui API maintains a context as GlobalContext and that should be valid. You will need to debug into the rlImGui and ImGui code and see if that context is bad.
I am adding a null set and check to that code to help prevent double calls, but I see nothing that would cause the error.

I see the problem now. fixing.

fixed in commit 165a715


Warn user if persistence is disabled

With https://helm.sh/docs/topics/charts/#schema-files, we need to warn user if they deploy hlf-k8s without persistence over peer, orderer, ca, couchdb !

It seems to be complicated to do so with json schema.
We can alternatively switch persistence true by default like bitnami charts like https://github.com/bitnami/charts/tree/master/bitnami/rabbitmq. What do you think ?

It seems to be complicated to do so with json schema.
We can alternatively switch persistence true by default like bitnami charts like https://github.com/bitnami/charts/tree/master/bitnami/rabbitmq. What do you think ?

@Kelvin-M I think it's more safe to enable it by default. So 👍 for me.

@Kelvin-M I think it's more safe to enable it by default. So 👍 for me.


regression: dropped Support of CUDA® architecture 5.0?

I'm using trying to use tensorflow 2.4 with nvidia 960m (compute compatibility 5.0)
According to the following change: https://github.com/tensorflow/docs/commit/cb886cfdd16d66ff7f8d1430676ff395b02910e6
Support of my card and many others have been dropped (My card at least definitely worked fine with tensorflow 2.2)
This is a major regression for many who are trying to upgrade, and currently, it is not even clear to me if it's intended and what is the rational behind it. If it is intended, please document it prominently in the 2.4 release. (and please consider not dropping the support of this architecture)

Hi, @amahendrakarI are you sure this is not a regression? AFAIKT, a year ago tensorflow supported all cuda architectures greater than 3.5

I think this was intentional change. See https://github.com/tensorflow/tensorflow/issues/41892#issuecomment-667452483

It's bad for tensorflow maintainers among others, I'm sure many issues could just be resolved when considering they are running an unsupported compute version, but even not all maintainers seem to be familier with this new limitation.
Also, got do admit I don't follow why/how 3.5, 3.7, 5.2, 6.0, and 6.1 are supported but specifically 5.0 is skipped (https://www.tensorflow.org/install/gpu) when in the 2.3 release notes we have: "PTX is not compiled before version 7.0".

Side note for docker users landing here - because they are not able to use their gpus anymore:
The problems you may have when trying to run with gpus from the docker image tensorflow/tensorflow:gpu-latest appear not to be related to this issue: Using tensorflow/tensorflow:gpu-nightly works.

TF 2.4 should support CC 5.0, please see announcement here.
The list of compute capabilities on https://www.tensorflow.org/install/gpu is stale, we will fix it soon.

The gpu docs have been updated commit b5c78b0.
See https://www.tensorflow.org/install/gpu#hardware_requirements
Thanks!

The gpu docs have been updated commit b5c78b0.
See https://www.tensorflow.org/install/gpu#hardware_requirements
Thanks!


Fix diff around default and known settings

What does this PR do?
We need to mimic the behavior from viper around default and known settings.

Fix the case where the user would BindEnv after setting a default and would override the default with nil:

config.SetDefault("a", 1234)
config.BindEnv("a")

Fix intermediate key not being known: SetKnown("a.b.c") should set a, a.b and a.b.c as known.
Fix AllSettings returning settings without values from BindEnv. This is done by adding a proper schema to differentiate settings with and without values. This answer the core difference betweenBindEnv add  SetDefault. Once we enforce a default for all settings we will be able to remove this difference. but for now we must mimic Viper default.
Fix the config not using search paths to look for datadog.yaml
Fix IsSet returning false when given an inner node setting path
Fix proxy setting initialization: this settings was initialize as a leaf but use as an inner node by viper.
Reproduce behavior from Viper where the Get method would infer the return var type from the defaults.

Describe how you validated your changes
Functionality is currently guarded behind a env var, so there should be no functional change. To test the behavior, use the DD_CONF_NODETREEMODEL env var, but be warned that there are likely bugs.

/merge


Update to rogue

What's this PR do?

If Rogue feature flag is enabled, send reportback item's updated status to Rogue when reviewed.

How should this be reviewed?

Choose a campaign to review reportbacks.
In Sequel Pro in the dosomething_rogue_reportbacks table, add the fid (or more if you want!) to the table and a rogue_reportback_id that exists as the id in Rogue's reportback_items table (make sure the status of this reportback item is pending).
Approve all reportbacks.
In Rogue database, the reportback item's status should be changed to approved.

Relevant tickets
Fixes #6972
Checklist

[ ] Documentation added for new features/changed endpoints.
[ ] Tested on staging.
[ ] Pinged a PM if this is a larger PR that would benefit from some additional testing love.

Overall looks ok to me. I think i have like two comments but I don't necessarily think they are needed to merge.

ok cool, thanks @sbsmith86 ! Is it ok to merge?

👍


table-input details-menu is always open

Description
You probably already noticed this since it's hard to miss, but the table input button's grid popup is always open. I think it's just a CSS issue
:root .rgh-table-input {
  width: auto;
  padding: 3px;
  z-index: 99;
  display: grid !important;
  grid-template: repeat(5, 20px) / repeat(5, 20px);
}

has higher priority than
details:not([open]) > :not(summary) {
  display: none !important;
}

How to replicate the issue
See the comment box input at the bottom of this page
Extension version
22.9.21
Browser(s) used
Firefox 107.0a1 (Nightly 2022-09-20)

Thanks for the report! I'll look into this soon. Can you include a screenshot?

Sure, here's a screenshot on Firefox. And yes, this is on github.com. I tried disabling other add-ons btw. The rule being overridden is in here, which I guess is generated from this. Could be color scheme dependent, I have the "Dark default" theme enabled in https://github.com/settings/appearance

You're on a nightly version. It works correctly on Firefox 103 and Firefox 105 on Mac, even with the black default theme.

Even if the final display value is grid, the browser still hides the element because that's how details work. I think you should report it to Mozilla before it reaches the stable version.

For a quick fix, you might want to add something like this to the CSS field in the options:
:root details:not([open]) > .rgh-table-input:not(summary) {
  display: none !important;
}

Ah, you're right. Thanks for your patience, it was actually my fault lol. The presence of the author sheet rule hiding the details content confused me, figured that it was intended to override the UA styles, but now (at least in Firefox) they're not overridable at all.


Add code check for if a method is invoked

We have a code check that looks if a method was invoked inside a test. We need another one that looks for method invocations anywhere.

Hello, me and Kiril would also like to work on this one as well.

@sandemiroren1 great! What's Kiril's github id?

Hello, I am Kiril!

Sir, shall we open a new branch ourselves, or should we wait for a branch that is tied to this issue? Thanks!


Make Event Log longer (and scrollable)

It would be nice have the ability to open the full event log and scroll through the full history

Sent a pull request to fix this: https://github.com/Cheneth/coup-online/pull/14
Hopefully it will be merged soon :)

Merged and deployed :)

Merged and deployed :)


Molecule idempotence test is not working during standalone execution via Docker

Issue Type

Bug report

Molecule and Ansible details
ansible 2.7.9
molecule 2.20.0

Molecule installation method (one of):

Using Molecule from Docker image: quay.io/ansible/molecule:2.20

Ansible installation method (one of):

Using Ansible from Docker image: quay.io/ansible/molecule:2.20

Detail any linters or test runners used:
Desired Behavior
I'm executing molecule tests by leveraging dind as from docs example.
Idempotence scenario cannot find converged instances if I run it as standalone step.
Is there are kind of limitation for this for dind execution?
Debug also shows not so much information.
If I run converge+idempotence scenarious at the same run, all is working OK.
Actual Behaviour
~/test-role$ docker run --rm -it \
>     -v "$(pwd)":/tmp/$(basename "${PWD}"):ro \
>     -v /var/run/docker.sock:/var/run/docker.sock \
>     -w /tmp/$(basename "${PWD}") \
>     quay.io/ansible/molecule:2.20 \
>     molecule create
--> Validating schema /tmp/test-role/molecule/default/molecule.yml.
Validation completed successfully.
--> Test matrix

└── default
    └── create

--> Scenario: 'default'
--> Action: 'create'

    PLAY [Create] ******************************************************************

    TASK [Log into a Docker registry] **********************************************
    skipping: [localhost] => (item=None)

    TASK [Create Dockerfiles from image names] *************************************
    changed: [localhost] => (item=None)
    changed: [localhost]

    TASK [Discover local Docker images] ********************************************
    ok: [localhost] => (item=None)
    ok: [localhost]

    TASK [Build an Ansible compatible image] ***************************************
    changed: [localhost] => (item=None)
    changed: [localhost]

    TASK [Create docker network(s)] ************************************************

    TASK [Determine the CMD directives] ********************************************
    ok: [localhost] => (item=None)
    ok: [localhost]

    TASK [Create molecule instance(s)] *********************************************
    changed: [localhost] => (item=None)
    changed: [localhost]

    TASK [Wait for instance(s) creation to complete] *******************************
    changed: [localhost] => (item=None)
    changed: [localhost]

    PLAY RECAP *********************************************************************
    localhost                  : ok=6    changed=4    unreachable=0    failed=0

~/test-role$ docker run --rm -it \
>     -v "$(pwd)":/tmp/$(basename "${PWD}"):ro \
>     -v /var/run/docker.sock:/var/run/docker.sock \
>     -w /tmp/$(basename "${PWD}") \
>     quay.io/ansible/molecule:2.20 \
>     molecule converge
--> Validating schema /tmp/test-role/molecule/default/molecule.yml.
Validation completed successfully.
--> Test matrix

└── default
    └── converge

--> Scenario: 'default'
--> Action: 'converge'

    PLAY [Converge] ****************************************************************

    TASK [Gathering Facts] *********************************************************
    ok: [molecule-host-]

    TASK [test-role : Ensure test user exists] *************************************
    changed: [molecule-host-]

    PLAY RECAP *********************************************************************
    molecule-host-             : ok=2    changed=1    unreachable=0    failed=0

~/test-role$ docker run --rm -it \
>     -v "$(pwd)":/tmp/$(basename "${PWD}"):ro \
>     -v /var/run/docker.sock:/var/run/docker.sock \
>     -w /tmp/$(basename "${PWD}") \
>     quay.io/ansible/molecule:2.20 \
>     molecule --debug idempotence
--> Validating schema /tmp/test-role/molecule/default/molecule.yml.
Validation completed successfully.
--> Test matrix

└── default
    └── idempotence

--> Scenario: 'default'
--> Action: 'idempotence'
ERROR: Instances not converged.  Please converge instances first.

~/test-role$ docker ps
CONTAINER ID        IMAGE                                                           COMMAND                  CREATED             STATUS              PORTS               NAMES
381ba0afe7e9        molecule_local/centos:latest                                    "/sbin/init"             2 minutes ago       Up 2 minutes                            molecule-host-

have you tried to use last prerelease or master?

Yes, I also tried different prereleases including 2.22rc6 one, but the same behavior.

Reproduce steps with 2.22rc6
$ docker run --rm -it \
>     -v "$(pwd)":/tmp/$(basename "${PWD}"):ro \
>     -v /var/run/docker.sock:/var/run/docker.sock \
>     -w /tmp/$(basename "${PWD}") \
>     quay.io/ansible/molecule:2.22rc6 \
>     molecule create
--> Validating schema /tmp/test-role/molecule/default/molecule.yml.
Validation completed successfully.
--> Test matrix

└── default
    └── create

--> Scenario: 'default'
--> Action: 'create'
--> Sanity checks: 'docker'

    PLAY [Create] ******************************************************************

    TASK [Log into a Docker registry] **********************************************
    skipping: [localhost] => (item=None)

    TASK [Create Dockerfiles from image names] *************************************
    changed: [localhost] => (item=None)
    changed: [localhost]

    TASK [Determine which docker image info module to use] *************************
    ok: [localhost]

    TASK [Discover local Docker images] ********************************************
    ok: [localhost] => (item=None)
    ok: [localhost]

    TASK [Build an Ansible compatible image (new)] *********************************
    ok: [localhost] => (item=molecule_local/centos:latest)

    TASK [Build an Ansible compatible image (old)] *********************************
    skipping: [localhost] => (item=molecule_local/centos:latest)

    TASK [Create docker network(s)] ************************************************

    TASK [Determine the CMD directives] ********************************************
    ok: [localhost] => (item=None)
    ok: [localhost]

    TASK [Create molecule instance(s)] *********************************************
    changed: [localhost] => (item=molecule-host-)

    TASK [Wait for instance(s) creation to complete] *******************************
    FAILED - RETRYING: Wait for instance(s) creation to complete (300 retries left).
    changed: [localhost] => (item=None)
    changed: [localhost]

    PLAY RECAP *********************************************************************
    localhost                  : ok=7    changed=3    unreachable=0    failed=0    skipped=3    rescued=0    ignored=0

$ docker run --rm -it \
>     -v "$(pwd)":/tmp/$(basename "${PWD}"):ro \
>     -v /var/run/docker.sock:/var/run/docker.sock \
>     -w /tmp/$(basename "${PWD}") \
>     quay.io/ansible/molecule:2.22rc6 \
>     molecule converge
--> Validating schema /tmp/test-role/molecule/default/molecule.yml.
Validation completed successfully.
--> Test matrix

└── default
    └── converge

--> Scenario: 'default'
--> Action: 'converge'
--> Sanity checks: 'docker'

    PLAY [Converge] ****************************************************************

    TASK [Gathering Facts] *********************************************************
    ok: [molecule-host-]

    TASK [test-role : Ensure test user exists] *************************************
    changed: [molecule-host-]

    PLAY RECAP *********************************************************************
    molecule-host-             : ok=2    changed=1    unreachable=0    failed=0    skipped=0    rescued=0    ignored=0

$ docker run --rm -it \
>     -v "$(pwd)":/tmp/$(basename "${PWD}"):ro \
>     -v /var/run/docker.sock:/var/run/docker.sock \
>     -w /tmp/$(basename "${PWD}") \
>     quay.io/ansible/molecule:2.22rc6 \
>     molecule --debug idempotence
--> Validating schema /tmp/test-role/molecule/default/molecule.yml.
Validation completed successfully.
--> Test matrix

└── default
    └── idempotence

--> Scenario: 'default'
--> Action: 'idempotence'
ERROR: Instances not converged.  Please converge instances first.

I guess to check idempotence locally you can execute molecule converge twice coz If I am not wrong molecule idempotence works as running molecule converge two times.

If role has not idempotent tasks, molecule will just show us changed tasks in output of molecule converge second time execution. It should not automatically detect any idempotency test failure.

@prashant0085 is right, that is by design. You either disable idempotence or assure that second run does not report any changed tasks.