v1.0.0: typeError: factory is not a function (after last update)

@zhangHongEn

Pull https://github.com/smelukov/mf-vite-nx-bug
run npm start
go to http://localhost:4201/ and see that all is ok
edit packages/my-app/src/main.tsx

--- a/packages/my-app/src/main.tsx
+++ b/packages/my-app/src/main.tsx
@@ -8,6 +8,6 @@ const root = ReactDOM.createRoot(
 );
 root.render(
   <StrictMode>
-    <App />
+    123
   </StrictMode>
 );

stop npm start started on step 2
run npm start again
go to http://localhost:4201/ and see the error

Workaround to fix:

stop npm start
remove node_modules/.vite
run npm start again
go to http://localhost:4201/ and see that all is ok

vite dev --force needs to add --force option

@zhangHongEn
I have the same error event on<EMAIL_ADDRESS>

I can't reproduce it anymore

This totally works for me

@zhangHongEn I have the same error even on<EMAIL_ADDRESS>(it includes optimizeDeps.force = true in node_modules)

Is the error occurring in a more complex project, rather than in the demo?

Yep, and I don't know how to reproduce it :(

Help me check some information in the network request

Check which module chunk-MWDJXBGP.js loads
Which modules are in localShareImportMap.js

You can reopen this issue
It is best to provide me with the content of chunk-MWDJXBGP.js so that I can check if it is a special path

@smelukov Sorry to bother you, you can try again to see if this problem is fixed

You can use this version
1.0.0-alpha-31ab3f9

@zhangHongEn  Was this issue fixed? Because I just hit that very same typeError when running the package in our project.
const exportModule = await res.then((factory) => factory()); is giving the factory is not a function type error

@kalucki I haven't encountered this problem again, can you provide an example to reproduce it?

const exportModule = await res.then((factory) => factory());
Could you help check the code above this section to see which module failed to load? If the file .__mf__temp/{name}/localSharedImportMap.js is missing the corresponding module, this error will occur.


f2837xD device - downloading kernel fails

Using a F2837xD device, the program fails on the download kernel step
# serial_flash_programmer -d f2837xD -k F2837xD_sci_flash_kernels_cpu01_28_29.txt -a appimage.txt -p /dev/ttymxc2 -b 115200 -v

C2000 Serial Firmware Upgrader
Copyright (c) 2013 Texas Instruments Incorporated.  All rights reservred.

calling f021_DownloadKernel CPU1 Kernel
Downloading F2837xD_sci_flash_kernels_cpu01_28_29.txt to device...

Attempting autobaud to load kernel...Input and Output successfully flushed
Autobaud for kernel successful! Loading kernel file...
aa=0
Data does not match... Please press Ctrl-C to abort.^C

Fixed.


Test example update

because of @with_injector gone according to https://github.com/python-injector/injector/issues/146
Reported also on https://github.com/python-injector/injector/issues/220

Thanks! Fixes #220.

Codecov Report
All modified lines are covered by tests :white_check_mark:

Comparison is base (395e7e8) 95.20% compared to head (876e842) 95.20%.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@           Coverage Diff           @@
##           master     #236   +/-   ##
=======================================
  Coverage   95.20%   95.20%
=======================================
  Files           1        1
  Lines         563      563
  Branches       95       95
=======================================
  Hits          536      536
  Misses         20       20
  Partials        7        7

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Update Connatix adapter

Update Connatix adapter
🏷 Type of documentation

[ ] new bid adapter
[x] update bid adapter
[ ] new feature
[ ] text edit only (wording, typos)
[ ] bugfix (code examples)
[ ] new examples

📋 Checklist

[x] Related pull requests in prebid.js or server are linked -> https://github.com/prebid/prebid-server/pull/3916

Hello @bretg !
Just checking if everything is alright with the prebid server PR I linked here or should I do something more to get a review there, in case I missed something in the process or do we just have to wait more.
Thank you!

@patrickszeleczki - sorry for the delay. In general, you can ping the code PR after a couple of weeks. I hit the prebid slack to see if someone can take a look.

Thank you!


Brute force does not work ?

Hi,
Thank you for this tool ! :-)
I am trying to find thes best parameters of a strategy.
I modified the TOML file and launch the tool.
It computes something during one minute, creates the csv file, puts the colomn titles in it and stop the process.
I tried either:

by erasing the TOML file -> it directly tells me that it did not find the TOML file (juste to validate it searches the file)
with the start..end:step
with the start.end:step
with the specific values (value1, value2, value3, ...) I want it to compute with (12 variables with 10 values each one)

I specified the "$debug = 'yes';" option but no error/debug output.
Is this feature working ?
Thank you in advance
Xavier

Have you splited datasets? Breaks between periods? If so, do not use the scan mode, but manually enter the date for these datasets. It's a bug that can improve one day.

Hi xFFFFF
You were right.
I drastically decreased the number of configurations (from billionns to hundreds of thousands) and it works !
Thank you
Xavier


Database using up too much space

Describe the bug
Nominatim database is expected to be about 900 GB, but while still importing, the database grew to more than 1.5 TB and continues to grow.
To Reproduce
Steps to reproduce the behavior:
Container started with command:
docker run -d -e PBF_PATH=/sources/data.osm.pbf -e REPLICATION_URL=https://planet.openstreetmap.org/replication/day/ -e THREADS=16 -e NOMINATIM_PASSWORD=[redacted] -e IMPORT_STYLE=address -e POSTGRES_SHARED_BUFFERS=4GB -e POSTGRES_MAX_WAL_SIZE=16GB -e POSTGRES_CHECKPOINT_TIMEOUT=30min -v /var/lib/pgsql/geocode-replicated/osm.pbf/:/import/:Z -v /var/lib/pgsql/geocode-replicated/pgsql/:/var/lib/postgresql/14/main/:Z -v /var/lib/pgsql/geocode-replicated/nominatim:/nominatim/:Z -v /var/lib/maps/geocode-sources/:/sources/:Z --shm-size=16g --memory=32g --memory-swap=100g -p 7071:8080 -p 5440:5432 --name nominatim-replicated mediagis/nominatim:4.2

The import process is now at the Starting interpolation lines (location_property_osmline) stage.
The Postgres directory is over 1.5 TB.
Expected behavior
Database size for planet data is expected to be about 900 GB.
Server:

OS & Version: CentOS 7
Docker Version: 19.03.13
Nominatim Version: 4.2.1

Additional context
The problem is I have only allocated 2TB to the Nominatim database volume, including additional files it now only has about 300 GB of free space left.

I think you should add the flatnode file:
-e NOMINATIM_FLATNODE_FILE=/nominatim/flatnode/flatnode.file


KVM automatically adds ballooning

ISSUE TYPE

Improvement Request

SUMMARY

By default ,we cannot get the memory usage of vm through libvirt;
Through analysis, it is found that the reason is that we did not add memballoon correctly in kvm;
When the mem.overprovisioning.factor of the cluster <= 1.0, kvm will generate the following memballoon

When the mem.overprovisioning.factor  of the cluster is > 1.0, kvm will generate the following memballoon

So when memballoon.model=none, we can't get the memory usage of the vm through dommemstat (assuming they all have qga installed correctly)
I wonder if we can set memballoon to virtio under any circumstances, and configure period=10 to let it automatically count the latest memory consumption.
In this way, we can use third-party tools to monitor the resource usage of the vm, making up for the regret that cloudstack cannot view the historical consumption of vm resources!

Hi @nvazquez @div8cn ,Am intrested in contributing to solve this issue,can you please assign me this,It would be helpful.
Thank you

@ravitejasssihl get comfortable with the code base (for instance going through https://github.com/shapeblue/hackerbook) and when you feel comfortable submit a PR.

@DaanHoogland
a PR has addressed it: https://github.com/apache/cloudstack/pull/6358


Wait for NextJS to be ready before continuing

We have to wait for NextJS to be ready before launch the server.
That is, make the first build especially in dev.
Fix: https://github.com/omarkhatibco/adonis-nextjs/issues/2

Thanks for your help :)


Mux methods accept a HandlerFunc instead of Handler

I see the change that converts the mux signatures to accept an http.HandlerFunc instead of an http.Handler here: https://github.com/pressly/chi/pull/48/commits/2b1ed9c5ae2bcffa8c7da4fd4ce9e78aba8da839. There's no rationale given for the change.
In the std lib, http.Handler is the handler type and http.HandlerFunc is an adapter for functions to match the http.Handler interface. With the current mux implementation, anything that is an http.Handler type must be passed in like this:
router.Get("/", myHandler.ServeHTTP)

The ServeHTTP function is converted back into a Handler by being wrapped by the HandlerFunc type. It seems redundant and, in general I believe, breaks the expectation that a mux will accept a Handler implementation. This is also inconsistent with the Handle function of the mux and the middleware type definition of func(http.Handler) http.Handler.
Most projects in the pre-1.7 space handled this case by having two signatures for each mux function:
func (m *Mux) Get(path string, h http.Handler) {}
func (m *Mux) GetF(path string, h http.HandlerFunc) {}

I'd like to get http.Handler support back and am willing to put in a patch if we can figure out the right implementation for this project.

Dupe of https://github.com/pressly/chi/issues/79 and was also mentioned in the original PR https://github.com/pressly/chi/pull/48#r72554065

@lwc thanks for the references.
@kevinconway yea it's been talked about a few times and I've spent a lot of time thinking and iterating to try to get the cleanest design of the chi Router.
Here were the options..

For each routing method function, we have variations accepting a http.Handler or http.HandlerFunc - as described in this issue: Get(string, http.Handler) and GetF(string, http.HandlerFunc)
Single routing methods that accept handler argument of type http.Handler
Single routing methods that accept handler argument of type http.HandlerFunc

Option 1 isn't ideal because it makes the chi.Router interface huge, by adding another 9 functions to the interface. The simplicity and surface of the Router is important to me to stay as minimal as possible. Btw, I was initially thinking to support Get(string, http.HandlerFunc) and GetH(string, http.Handler).
Option 2 is what I had originally in chi v1 until I realized option 3 is a bit more elegant because it offers a cleaner API. Under option 2, you'd have to wrap endpoints such as..
func myHandler(w http.ResponseWriter, r *http.Request) {
  // ...
}

with http.HandlerFunc(myHandler), such as r.Get("/", http.HandlerFunc(myHandler)). This would be quite common and isn't ideal.
Option 3 (the current implementation) accepts func(http.ResponseWriter, *http.Request) to the routing methods as its the underlying type of http.HandlerFunc, which I believe is the most common case for passing to routing methods. The downside is for http.Handler's that are passed, they must call .ServeHTTP to make it a HandlerFunc signature. I believe if I'm foregoing option 1, then this becomes to best choice.

with http.HandlerFunc(myHandler), such as r.Get("/", http.HandlerFunc(myHandler)). This would be quite common and isn't ideal.

I believe this is consistent with the standard library. The net/http module provides a Handle method that accepts any http.Handler implementation and then a HandleFunc that accepts any http.HandlerFunc implementation. My personal inclination is to match the standard lib so this mux becomes a drop-in replacement if most cases.

it makes the chi.Router interface huge, by adding another 9 functions

For cases outside of the usual Handle and HandleFunc cases, I think another possible approach is to move the HTTP method to an input string rather than the function name which would only require two new funcs:
r.HandleM("GET", "/", myHandler)
r.HandlerFuncM("GET", "/", myHandlerFunc)

In any case, if you're pretty settled on Option 3 then you can close this issue. I'll keep passing .ServeHTTP around.

@kevinconway good point about having Handle() and HandleFunc() the same in chi as in http.ServeMux - and in fact I checked and its matches up in the current version.
Interesting idea with the http method, perhaps we do that sometime. For now, yea let's stick to open 3 and we can leave this ticket open for a bit for others to offer some feedback too.

@pkieltyka @kevinconway new to this discussion, and not sure what you mean by passing around ServeHTTP, but one way I've implemented it that may help (and not sure how it can be incorporated into chi or even that it needs to be) is by wrapping the chi.Mux.ServeHTTP method.
I define a custom Router type that wraps a chi.Mux and defines a ServeHTTP method that wraps the chi.Mux.ServeHTTP method:
type Router struct {
	Mux    *chi.Mux
}

// ServeHTTP wraps the ServeHTTP of our mux choice
// This allows us to pass it into http.ListenAndServe and http.ListenAndServeTLS
func (r Router) ServeHTTP(w http.ResponseWriter, r *http.Request) {
	r.Mux.ServeHTTP(w, r)
}

All my handlers get to keep the same standard signature:
func myHandler(w http.ResponseWriter, r *http.Request) {
   // ...
}

I create a chi.Mux and add middleware, initialize routes, etc. and then initialize the router with the mux:
mux := chi.NewRouter()
mux.Get("/", myHandler) // option 3 syntax
r := &Router{Mux: mux}

So now I can pass it into http.ListenAndServe:
http.ListenAndServe(":3000", r)

Let me know if I'm completely out in left field, but this pattern has worked for me and has been extremely nice and clean to work with.

hey @rossnanop - hmm, you can definitely wrap the chi router, and I encourage it as necessary to compose additional logic, but in the small example, you already have this out of the box:
r := chi.NewRouter()
r.Get("/", myHandler)
http.ListenAndServe(":3000", r)

Yeah I just realized that was what I was doing, and that I wasn't adding anything to the discussion. Sorry for the noise.  I guess my point was option 3 works nicely for me. 😄

I know this is an old issue (and closed), but I have to say that I am in agreement with @kevinconway and the
r.HandleM("GET", "/", myHandler) r.HandlerFuncM("GET", "/", myHandlerFunc)
seems like it would be the most elegant way to solve the problem, while still keeping in line with the project's spirit of minimalism.
The use-case is when you have complex request handlers with non-standard signatures that simply implement the http.Handler interface. For example in scenarios like this where you have a request handler that returns an error -a pretty common case.
Anyway, my 2c for future versions is to forego option 1 from above and make http.Handler a first class citizen of Chi.


Change channel id of GetTemplates operation to GUID

Contributing to the Azure SDK
Please see our CONTRIBUTING.md if you are not familiar with contributing to this repository or have questions.
For specific information about pull request etiquette and best practices, see this section.

API change check
APIView has identified API level changes in this PR and created following API reviews.
Azure.Communication.Messages


A feladatunk

Sziasztok, megérkezett a feladatunk. Holnap 9:00-kor találkozzunk. Én tudok Teams szobát indítani, ha az jó nektek, de jobb ötletet elfogadok!
A feladatunk:
Information the engineers get in real life
Summary of the meeting with the customer
The customer would like to hire external IT experts who can provide a solution to successfully migrate the company's semi-scripted tasks into a more mature automated solution. Currently there are a lot of human errors during their work because there are many manual steps in their existing processes. They would like to have a framework that helps them "automate everything". They also do not want to use complicated tools because it would be hard for their team to onboard and understand it. They also want to be able to collaborate on a shared environment/framework. The customer wants it to be ready as soon as possible. They also highlighted to following points:
The provided solution should be documented as detailed as possible. They want to be able to easily teach this framework to their colleagues
Possibility to test their code
Introduce approval workflow
They would like to have some example terraform codes
From a technical perspective they want to have an integrated system that manages code, issue tracking and automated processes.
Manager's request
Based on the meeting notes try to brake down the project into tasks
Create a sketch, diagramm or roadmap about the project. You could maybe use miro.com or draw.io
Create a technical architect diagramm about the solution
Be ready by tomorrow ;)
AFP class related information
The goal is to simulate a project work. That is why every team should utilize as much of the features that github offers as possible. Please use projects, issues, milestones to track the progress. Sometimes would be nice to create a few releases (tags). Team members can collaborate more easily by using separate branches and pull requests.
Create team workspace
Every team should have their own github repository created and the team members added.
Invite me as a collaborator to your repo: Settings / Collaborators / Add people (simark2357@gmail.com).
Copy the .gitignore file to the root of your repository and commit/push your changes to the main branch
Create the root main.tf file
Enable terraform pipeline in the repository:
In the 'Actions' tab search for the 'terraform' keyword and press configure
In the generated yaml the if statement in the terraform apply step needs to be changed from if: github.ref == 'refs/heads/"main"' && github.event_name == 'push' to if: github.ref == 'refs/heads/main' && github.event_name == 'push' otherwise the apply step will not execute in case of pushing to main branch.
You can also optionally delete the step that does the fmt check.
In case of any doubt you can use this terraform.yml for reference
commit and push your changes to the main branch. At this point you should have the following struture
.
├── .github
│   └── workflows
│       └── terraform.yml
│── .gitignore
└── main.tf
This repository will be the team's workspace and everyone should work on the tasks there
Work
Maybe you already found out that what the customer wants is basically can be covered with the github features
issues
milestones
projects
pipelines
documentation
pull requests and code reviews
approval workflows
releases (tags)
release notes
etc...
Documentation
Atleast a well structured README.md file should be created in the root of the repo. It would be a nice touch to have pictures, diagramms in the documentation. Parts of the documentation could be:
system design (for example how the github pipeline mechanism works --> uses a docker runtime that github hosts)
pull request mechanism
issues/projects
terraform code
test code
pipeline workflow
pull request approval workflow
terraform code
Create three example terraform codes that simply creates files
simply use the local_file resource
use the local_file resource but now with variables
create n number of files with the local_file resource with the help of the count meta-argument
test code
An extra step should be created in the pipeline named test or validation that would check if the files were created or not. For example a bash script could be used to check the existence of the files...

Sziasztok!
Nekem megfelelő bármilyen komm. platform, alkalmazkodok.
Reggel találkozunk!

Offtopic: Házy Attila megosztott drivejához tudja valaki a passt? Megint nem tudunk belépni, pedig valószínű ott teszi közzé a ZH feladatot ma.

Sziasztok! Nekem is jó bárhol!

Nekem is jó bárhol.

Köszi a gyors válaszokat, akkor itt a Teams link:
https://teams.microsoft.com/l/team/19%3AB-Ke_8d5egnvvDVBfmyMVl5idamEqdsls__kiHg2Xps1%40thread.tacv2/conversations?groupId=a62a6f79-6484-4492-a5f8-eb107a89c4a8&tenantId=7a75db96-b75c-4b84-9fee-af761ad9df82
Holnap 9:00!

@fattila1 Most adtam le a hozzáférési igényt az MS Teams laborgyak csoportodhoz. :)


Missing exact location for failed tests

Failing tests always refer to test.webpack.js line numbers:
PhantomJS 1.9.8 (Mac OS X 0.0.0) AbTest.js Spec should assign a random variant from a test case FAILED
Expected undefined not to be undefined.
    at /Users/dbus/Projekte/Pro7Sat1/Variants/tests.webpack.js:123

Adding sourcemaps to the preprocessors fixes this.

Fixed in PR #4.


Issue with math.clamp and -0

Fixes #43

Not 100% sure how I feel about this, as -0 does == 0 but I do agree that clamping to 0 min should remove the - So I'll leave the final decision to you!

Eh, it works.


Custom Model

How we can use your calendar with custom model?

You can extend your model:
<?php

namespace App\Models;

class YourModel extends \Czemu\NovaCalendarTool\Models\Event
{
    //
}

Then you can overwrite whatever you need.


[2.3beta] Low contrast between selected and not selected columns (ordering)

The contrast between the colour of the selected and not-selected columns is really, really subtle. Could it be made a bit more obvious?

Do you still think it's too subtile? I guess the main problem were RGBA colours which have been replaced by their HEX values.


ranking by var-complexity, complexity, sum of intervals

closed because it didn't improve pong from lab or the new quantized pong which is currently in applications


post.terms not allowing us to pass custom order settings?

Expected behavior
In a Twig partial, we should be able to order terms on a post by their ID in ascending or descending order.
This is the code we're trying to use:
post.terms({taxonomy: 'example-taxonomy', orderby: 'term_id', order: 'ASC'})

Actual behavior
The custom order values that we pass through to the method seem to have no impact on the ordering of the terms returned.
Steps to reproduce behavior
Step 1: Create a custom taxonomy for posts, create multiple new items in the taxonomy
Step 2: Assign that custom taxonomy to posts so that we can add the terms to a post
Step 3: Create a new post, add multiple taxonomy terms to the post
Step 4: Add the following code to the timber template for the post (you will need to change the taxonomy value:
{% for term_item in post.terms({taxonomy: 'example-taxonomy', orderby: 'term_id', order: 'ASC'}) %}
{{ term_item.name }}
{% endfor %}

Steo 5: View the page in a web browser, change the order value in the above code, and observe that it has no impact on the ordering of the output taxonomy terms
Could this be causing the problem?
I tried to debug this and tracked down the following line of code in lib/Post.php (line 764):
$terms = wp_get_post_terms( $this->ID, $taxonomies, $args['query'] );
(https://github.com/timber/timber/blob/master/lib/Post.php#L764)
Changing this code to the following fixes the problem:
$terms = wp_get_post_terms( $this->ID, $taxonomies, $args );
It seems like this is a bug, because the full arguements list is not being passed through to the wp_get_post_terms function, just the query which includes the taxonomy term being queried, but no other custom args (I may have missed something here, or my implementation in the twig file may be incorrect, but I don't think it is).
What version of WordPress, PHP and Timber are you using?
WordPress 5.3.2
PHP 7.2.14
Timber 1.13.0
If the code I found is actually the cause of the problem, I'm happy to fork the code and create a pull request to fix this.
Also please note that we can't order the taxonomy term in PHP because in our codebase, this code is used in a twig partial that is included in various other twig files.

Thanks for the thorough bug report @sean-dunwoody ! I'll look into this over the weekend


Implement "live" reporters + many mocha reporter counter-parts, including time measurement

I am building a new runner type that uses purescript-pipes to pipe results directly to the reporter, but also collects the results itself for final evaluation. This allows to stream results to the console, rather than running all tests first and then printing all of it.
It's still work in progress, but the goal is to eventually replace the current Runner.run implementation transparently in order to allow reporters to do more cool stuff :)
asciinema casts:

streaming console reporter
streaming spec reporter
streaming dot reporter
streaming TAP reporter

things to sort out:

[x] require a proper purescript-spec release (depends on purescript-mmorph release)
[x] should we store what is considered "slow" on the reporter or on the runner? I implemented on the reporter as it is in mocha, but thinking about it, it feels like it should be interpreted by the runner instead. @owickstrom , what do you think?
[ ] i have implemented a default summary that looks like mocha's default summary report. But in order to keep things "as they were", I have left the current console reporter's code in tact. We should decide what we want for a default summary and use it across at least all reporters currently implemented (I believe neither of them warrant a different summary look).
[x] to get timeouts into the runner itself, it requires the AVAR and TIMER effects. This means that when defining a Spec, this won't work anymore forall r. Spec r Unit, as r must be (avar :: AVAR, timer :: TIMER | r). Should we just unsafeInterleaveEff around this?

This looks really neat! :) Will look at it in more detail.

Thanks. I think my latest commit is moving in the right direction, esp around https://github.com/owickstrom/purescript-spec/pull/32/files#diff-edf85d78ba17883b458ee8575ec09337R33.
This way we can implement reporters simply by applying the reporter function to a custom step function (that receives events) and a custom summarize function (epilogue in mocha).

Alright I have ported my work from #31 to using piped reporters. I will port the console reporter also, then move to the Reporter namespace. This new system gives us everything we had before plus the ability to report dynamically as the tests are running so we don't need both implementations, I think.

I think this code is ready for review now. We won't be able to merge just yet because I am blocked on releasing a new version of purescript-pipes because of Thimoteus/purescript-mmorph#2. I am waiting for a new release of that library to depend on, then I can publish and update the dependency for this PR.
Also, it would be really helpful if you could take a look at https://github.com/felixSchl/purescript-pipes/blob/master/src/Pipes/Internal.purs#L141-L143 and https://github.com/felixSchl/purescript-pipes/blob/master/src/Pipes/ListT.purs#L67-L69 that would be much appreciated.

I've added speed reporting to the bunch of new features as well.... I updated the asciinema casts if you wanted to have a look at it from a visual perspective

I'll rebase this soon

OK, I've finally gotten around to look at this in greater detail. It looks so promising, really taking purescript-spec to the next level, Felix! Great job, so far! :+1:
About where to decide "what is slow", I agree that it should be a responsibility of the runner.
Regarding the formatting of a summary for all reporters, which one do you think is best? The legacy Console reporter was probably inspired by Hspec, but not an exact clone in formatting.
I'll look at the diffs as well, have to get a better understanding of purescript-pipes before I can make sense of it. :smile:

You are taking over this knowledge map, step by step: https://codescene.io/projects/124/jobs/346/results/social/knowledge/by-author :grin:

I implemented the TAP reporter. I will move the "what is slow" stuff into the runner next. I implemented the mocha style summary simply because I use that at work for all projects and I am used to it.

Alright, so the run function can be configured now but also provides a default config. I've added timeouts as well (borrowed in part from purescript-test-unit, not sure how to credit them).

Alright, I'll leave it at that for now, waiting for your feedback regarding the effect row stuff (I updated the todo check list in the summary).

Cool! Can't say I found any single thing to remark on. :) Looks really good!
About the effect row, the sad thing is that it will break backwards compatibility for users on 0.10.x. It's not a very big change, so maybe we could be very clear about what needs to be done. Correct me if I'm wrong, but it should only be the effect row of specs?

Yeah previously the effects caused by a spec where entirely driven by what the user wants to do with them, but now the spec runner causes some effects itself, so it will need to declare this. To keep backwards comp, we could mask it using unsafeInterleaveEff

@felixSchl yeah, but that makes me a bit uneasy as well. :disappointed: Don't really know the conventions, but could using a custom effect be a middle ground? So we can hide whatever we have behind that, like Spec (test :: TEST) Unit. Then we'd at least not have to break backwards compatibility each time we change the implementation. Or we could encourage users to use a wildcard, like in your pull request. What do you think?

Alright, I took care of it, but in the end I overshot a little: I also removed the return type for Spec since it was not used anywhere and there's not a single function that would suggest it makes sense to keep it. But I can back paddle on that if you want as it does break backwards compat to a small degree (users would have to update from mySpec :: forall e. Spec e Unit to mySpec :: forall e. Spec e.

Yes, I think we should keep the return type. People may have utility functions for providing values to a spec, say a setup function that has type Spec e MyState which they need to be monadic. Plus, as you said, keeping it would mean one less breakage point.

Good point, will back up the bus tomorrow morning

Cool, thanks!

I forced pushed the reversal, now the latest commit only contains the effect row stuff

OK, I will have look as soon as possible. :)

It seems the purescript-pipes dependency is missing from bower.json. I tried installing it manually and got a bunch of version conflicts, and the version of pipes is 0.0.0 which seemed a bit strange(?).

I am blocked on releasing an update because of this: https://github.com/Thimoteus/purescript-mmorph/pull/2. I could, of course, depend on my github fork's sha in purescript-pipes, but doesn't feel right. That said, I also send thimoteus an out of channel email w/o response.

We should get that properly released first. No updates? :/

No updates. Thimoteus appears to have gone off the radar. I wonder what's the right way to deal with this scenario.

How long have you waited? Maybe for a (temporary) fork of the dependency. Not sure how that works with Bower publishing though?

I have opened the PR to purescript-mmorph on 6th of November 2016. I have low faith it will get merged anytime soon because the owner seems to have vanished from the face of the earth. We could easily release a version of purescript-pipes that points to my fork.

I have checked with the guys on IRC, depending on the fork is the only option at this point, but @natefaubion suggested purescript-mmorph has contrib potential, where it would see active maintenance (I volunteered until the original maintainer resurfaces). But for now, as far as purescript-spec is concerned, all should be working now.

Yeah, I checked the IRC logs, and it seems reasonable. I'll try around a bit with this PR now, and then I think we should merge if nothing else comes up. brb :)

Found that the colors from the consoleReporter does not work very well with some dark color schemes (iTerm 2):

I found the Colors module, where Pass maybe should be the default text color of the terminal instead? What do you think?

Also, I found some minor warnings, all right if I fix those?

Yes, please do. Do I give write rights to my fork or what?

Yes, it seems so. :)

Should I push the changes there?

Entirely up to you, I gave you push rights on that repo if you want to finalize things before merging. If you prefer to just merge and then fix up, that's cool with me too

Yeah, I'll push so that you can have a look at my changes too. :)

Mostly unused imports and such, now fixed. If you don't have anything else, I think it's ready to be merged.
I'll update docs and tweet about it once it's on master. :)

Looked over it, looks good! I am happy for it to be merged

what about the color issue though?

Oh, right. Give me a minute, I'll try changing the Pass color to a default color.

Exact same issue discussed around Mocha here: https://github.com/mochajs/mocha/issues/802. They concluded that it was a theme issue, not a problem with using a gray color. What do you say? Leave it as is? I'm not 100% sure, but I think I agree that themes should display gray properly, and we should not have to code around Solarized issues.

Should have tried this before, but anyway... I ran this branch together with purescript-spec-discovery and found some issues regard effect rows. They're fixed now by using SpecEffects basically everywhere, also for user Aff values (Spec bodies) and Eff values (the resulting program when run).

Re mocha colors: I'd go with the verdict reached in mochajs/mocha#802. Re SpecEffects, I guess it makes sense to only introduce the effects when needed, i.e. when running the spec.

Funny you renamed it to RunnerEffects, I was thinking to suggest renaming it sth similar

Yeah, seemed like a good name. :) I had to split out PROCESS to make the Mocha runner work in the browser. We should probably split out the PROCESS-dependent runner included in purescript-spec, along with the CONSOLE-dependent reporters. We can of course do this later, and it will be a breaking change, but I've seen some confusion around what is NodeJS/Browser-specific in purescript-spec. We could have a purescript-spec-node package perhaps.


[Android Bootcamp] Project 4: MyTweets - Ready for Review

My app is complete, please review. /cc @codepathreview @codepath

:+1: Nice work. A few notes after checking out the code:

Nicely done architecting the fragments (base class and extension classes) such that you put as much code and logic as possible in the base class and then used abstract methods to define only the specific behavior where they differ!
Good to see you properly communicated the user to the user timeline fragment from the profile activity.
Nice to see you used the ViewPager to properly setup the tabs!
Good to see you played with styling
Nice job with including progress support
Amazing work on the polished UI - adding the navigation drawer, collapsible profile view

Here's a detailed Project 4 Feedback Guide here which covers the most common issues with this submitted project. Read through the feedback guide point-by-point to determine how you might be able to improve your submission.
This week (Week 5), we are going to cover the last major piece to the Android puzzle and that is using the hardware and SDK components such as the camera, photo gallery, location, maps, etc. After that, Week 6 and week 7 we will be covering a few important intermediate topics such as more about styling and animation as well as testing.
Following the bootcamp, we are going to have a public demo day to celebrate the progress you've all made with our next batch of Android students and multiple companies attending to see the group projects that you all have built. We are going to help however we can over the next few weeks to get the team project apps in shape for that.


does this plugin support saving images in a mobile broswer?

I want to saving images in a mobile broswer.

https://stackoverflow.com/questions/10673122/how-to-save-canvas-as-an-image-with-canvas-todataurl


[Firebase remote config] How to change property some fields in color.xml file or dimen.xml file

Hello all
I want to make my app dynamic color for all in app, So i want to change color.xml and dimen.xml but I dont know how to use.
Could you help me
    <color name="colorPrimary">#000</color>
    <color name="colorPrimaryDark">#000</color>
    <color name="colorAccent">#000</color>

Thank you so much

#000
#000
#000

@tvhieuit by default there is no connection between Remote Config and the theme of your app, you'd have to build that yourself.  Remote Config can only help you get the string values (#000, etc) into your code over the air.
If you need help learning how to apply themes at runtime, please ask on StackOverflow.


fix(1.32.0): scaffolder total query

Hey, I just made a Pull Request!
After upgrading to 1.32.0, the scaffolder tasks page fails to load with Postgres.
fixes scaffolder list error with postgres: error: select count("tasks"."id") as "count" from "tasks" order by "created_at" desc - column "tasks.created_at" must appear in the GROUP BY clause or be used in an aggregate function
:heavy_check_mark: Checklist

[x] A changeset describing the change and affected packages. (more info)
[ ] Added or updated documentation
[ ] Tests for new functionality and regression tests for bug fixes
[ ] Screenshots attached (for UI changes)
[x] All your commits have a Signed-off-by line in the message. (more info)

Thanks! :tada:


[Feature] system monitoring tool

New Feature
In order to operate Autoware stably for a longer period of time and to identify the cause of the error, the monitoring function of the system is indispensable.
As a monitoring target, first I want to monitor the following:
CPU, GPU, disk capacity, process, network, ntp

can we close this @yn-mrse ?
is #1943 related?


MLP layer in the models.py

Hi,
I am confused why mlp layer in the models.py doesn't change the dim of the vectors. (when pool_type=cls), so what is the function of this layer?

Hi,
You don't need "changing the dim of the vectors" for an MLP layer to work. Here the MLP layer is just for adding some transformation over the original CL representation so it might suit our need better.

I add dropout in MLP layer in chinese dataset，and result is more good.

I add dropout in MLP layer in chinese dataset，and result is more good.

Hello, I would like to add dropout to the MLP layer to improve the performance of the model, but I found that dropout is already used in the source code, so I would like to ask you how to add dropout to the MLP layer.


Report better error messages when parsing defect Kraftfiles

This issue tracks adding more helpful error messages when parsing a Kraftfile which is syntactically (or logically) in correct.  The error message should attempt to point to where the error was encountered and suggest a remedy.

Hey @nderjung I would like to work on this issue.

@bhavyastar what's your progress on this issue ? Can I start working on this ?  :)

Has this been picked up yet? If not, we were wondering where these errors is encountered, specifically where kraftfiles are being parsed. Thank you!


Add dot-env-secrets recipe

Description
What's cooking?
As discussed with @EmilRex, here is my first recipe to help loading enviroment variables from a .env file to a Prefect workspace using the Secret Block. Not sure where this should be in the repository.
Type of change

[x] New feature (non-breaking change which adds functionality)

New Recipe Checklist

[x] My PR is in the format of Add <project-name> recipe
[x] My recipe is reproducible and explains everything needed to run successfully. If my code has external dependencies, I make mention of them.
[x] My code is easily understandable and/or well-commented.
[ ] If my recipe requires a new category (e.g. creating a monitoring/ folder in devops/), I have encapsulated my project within its own subfolder so that others can add their own recipes as well.
[ ] If my recipe uses Prefect < 2.0, my code is within the prefect-v1-legacy/ folder.

Hi @zzstoatzz , I agree! I really didn't know if it had to be a flow in order to be in this repository.
I like your idea and I will make this change! Thanks for having a look at it 🙏


Story Structure validation should include a check against max number of predictable actions

Description of Problem:

I've run into issues similar to this whereby I've created stories with more than 10 actions after a given intent.  While it was easy to find during runtime, I think that data validation scripts should catch any stories that train the model to queue up more than 10 actions after any given intent.
Perhaps they could give a warning (as they do during runtime) that a certain story will not work properly?
Overview of the Solution:

Add a check in the data validator to check for stories that have more than 10 predicted actions
Examples (if relevant):

This log which only appears during runtime:
2020-09-14 02:58:26 WARNING  rasa.core.processor  - Circuit breaker tripped. Stopped predicting more actions for sender 'default'.

This issue demonstrates it's an easy pitfall for users
Additionally these forum posts have similar confusion
Something else I've noticed is that for myself I have stories that look like (I'm on Rasa 1.10.7):
## some story
* trigger_10
  - utter_something_1
  - utter_something_2
  - utter_something_3
  - utter_something_4
  - utter_something_5
  - utter_something_6
  - utter_something_7
  - utter_something_8
  - utter_something_9
  - utter_something_10
  - utter_something_11 <!-- circuit break happens here -->
  - utter_something_12

However, if I send any message (regardless of predicted intent), it will still queue up utter_something_11 and utter_something_12. This story is mostly run with the AugmentedMemoizationPolicy (with a Max history of 10) based off the logs, but after the message, the KerasPolicy will take over.
Blockers (if relevant):

Definition of Done:

[ ] Add test to Rasa Validator class for story with more than 10 actions
[ ] Add story structure warning log for any story that exceeds the MAX_NUMBER_OF_PREDICTIONS constant
[ ] story structure check is mentioned in documentation
[ ] story structure check is mentioned in the change log

Thanks for submitting this feature request 🚀 @erohmensing will get back to you about it soon! ✨

@ortsaCniveK thanks for bringing this up, it sounds like a valuable addition. Would you like to contribute it?

Sure!  I'm doing a bunch of Rasa contributions in the spirit of Hacktoberfest, so you'll see those soon :)

Awesome, I'll add it to the contributor board 🎸

Hi @ortsaCniveK, any progress with this?

Hi @ortsaCniveK, any progress with this?


Automatically add new tokens to the GH list

Description
Create a cron (a cloud function or in blockchain-api), that checks for new tokens, and if there is a new token, it submits a PR to https://github.com/valora-inc/address-metadata adding the new token.
Questions

How do we decide which tokens to add?

We could check the liquidity pools in Ubeswap, if the token is present in some liquidity pool with more than $20k of liquidity, we add it.
Other ideas?

Acceptance Criteria

[ ] Create cron

As the initial experiment will focus on only the CELO native tokens, let's tackle this task as part of a follow up


History.js on IE7 (and probably 6, but that doesn't matter to me) have problems with iframe if document.domain is set

We are using APE Project + History.js + jquery.form.js (for uploading files). APE Project sets document.domain and... breaks both History.js and jquery.form.js. On IE7 there is permission denied, when History.js tries to access iframe created for hash changes log.
Is there way to set document.domain inside that iframe?

Hey balupton, did you ever manage to fix the issue with document.domain? I'm using History.js in conjuction with a site that I need to set document.domain to a value that allows my subdomains in iframes to communicate with the parent page. But when doing so History.js spits out a whole heap of security errors in all browsers I tried.
I had a go at fixing it myself by changing the iframe history.js uses to also set document.domain but when then doing pushState I get more security errors. And I can't figure these ones out :(


[VS Code] Cannot read property 'isAnonymous' of undefined

Error:
Cannot read property 'isAnonymous' of undefined
Steps to Reproduce:

Version Data

extensionName
VSLS

extensionVersion
0.3.954

protocolVersion
2.2

applicationName
VSCode

applicationVersion
1.29.0

platformName
MacOS

platformVersion
16.7.0

cc @tavisrudd

@tslevi-unbounce @tavisrudd, thanks for reporting the issue, do you mind send me your logs?
You can run the Live Share: Export Logs comamnd in VSCode to get the zip with logs. You can attach them here or send it to<EMAIL_ADDRESS>Thanks!

May be related: https://github.com/MicrosoftDocs/live-share/issues/1269

@legomushroom I believe this is fixed - correct?

Closing due to inactivity. Please re-Open if you’re still encountering this issue. Thanks!


deb depends on libappindicator3-1 which is unavailable in Debian/11 Bullseye

Hi,
the current package 3.1.1 depends on libappindicator3-1 which is unavailable in Debian/11 Bullseye the next Stable release. So the package is uninstallable on Bullseye:
See this Bug deprecating  libappindicator3-1
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=895037
Flo

Try:
wget http://ftp.us.debian.org/debian/pool/main/libi/libindicator/libindicator3-7_0.5.0-4_amd64.deb
wget http://ftp.us.debian.org/debian/pool/main/liba/libappindicator/libappindicator3-1_0.4.92-7_amd64.deb
sudo apt install ./libindicator3-7_0.5.0-4_amd64.deb
sudo apt install ./libappindicator3-1_0.4.92-7_amd64.deb

https://github.com/Clansty/Icalingua/issues/162#issuecomment-899255738

Please test if the latest release did solve this. If not please reopen the issue or create a new one and tell us. I will be closing this one for now.
Thank you!

The deprecated libappindicator libraries are no longer provided. As a result, the related packages libappindicator1, libappindicator3-1 and libappindicator-dev are no longer available. This is expected to cause dependency errors for third-party software that still depends on libappindicator to provide system tray and indicator support.
Debian is using libayatana-appindicator as the successor of libappindicator. For technical background see this announcement.
Found here :https://www.debian.org/releases/bullseye/amd64/release-notes/ch-information.en.html#noteworthy-obsolete-packages

The deprecated libappindicator libraries are no longer provided. As a result, the related packages libappindicator1, libappindicator3-1 and libappindicator-dev are no longer available. This is expected to cause dependency errors for third-party software that still depends on libappindicator to provide system tray and indicator support.
Debian is using libayatana-appindicator as the successor of libappindicator. For technical background see this announcement.
Found here :https://www.debian.org/releases/bullseye/amd64/release-notes/ch-information.en.html#noteworthy-obsolete-packages

How can we fix this? The Electron builder that uses this library to generate the deb. Any clue?

I have also this issue, the old tauri app depends on libayatana-appindicator3-dev (https://github.com/AyatanaIndicators/libayatana-appindicator), and the newer one is depends on libayatana-appindicator3-dev.
See https://tauri.studio/v1/guides/getting-started/prerequisites/.


chore: refactor just distrobox to use libujust tooling

do not merge until #194 is merged, then this needs to be rebased first

replacing with cleaner PR


fix for flutter 1.12.13+hotfix.5

Describe the purpose of the pull request.
Fixes / Enhancements

Fixed AppLifecycleState enum changed in flutter 1.12.13+hotfix.5 - change code reference to reflect the change.

ok, saw this was already done in the beta branch


I want to know cyclist pedestrian vehicle share the same network or have own network

hello,
I want to know when after training cyclist pedestrian vehicle share the same network or have own network in both encode and decode?

We use the same model for all categories, and you can refer the config here: https://github.com/sshaoshuai/MTR/blob/master/tools/cfgs/waymo/mtr%2B100_percent_data.yaml#L3


Long wait when editing files in home directory

I recently installed Gutentags and, while it appears to work wonderfully when I open a file inside one of my projects with a .git folder, it takes EXTREMELY long (~30 seconds) for Vim to open a file in ~/ (such as my .vimrc)
I enabled the tracing and this is what I get when attempting to edit ~/.vimrc:
gutentags: Scanning buffer '/home/rslindee/.vimrc' for gutentags setup...
gutentags: Can't figure out what tag file to use... no gutentags support.
Note that the second line doesn't appear until after approximately 30 seconds of searching. I tried putting a .notags file in my ~/ directory, but it made no difference.
Any suggestions would be greatly appreciated, as I think this plugin shows a great deal of promise.
Edit - Additional info:
-The long delay doesn't seem to occur if I open Vim in the root directory. That said, the delay occurs if I attempt to open Vim inside something like /bin
-This is inside a Cygwin environment
-It seems like the algorithm for finding "project markers" in parent directories is taking way too long when there are no such project markers to be found

Interesting, I can't think of anything that would result in such a slow lookup for the project root... you could add some more traces into autoload/gutentags.vim, inside gutentags#get_project_root, where it does the while loop. This way you would maybe see exactly what directory causes problems.
Maybe there's something to do with a loop of symbolic links? Or with a parent directory that requires admin privileges and so Windows times out because of UAC? Or the terminal condition to stop navigating to parent folders is somehow not valid under Cygwin? (on Windows and *nix, Vim's fnamemodify(path, ':h') basically returns the same thing you passed in if you reached the root)

(haven't heard back)


feat: add runAsNonRoot:true to default

Signed-off-by: Batuhan Apaydın<EMAIL_ADDRESS>Related Issue(s)

Description

I noticed that we have a check for runAsNonRoot in validation rules but we don't have any mutation for that.
This PR will fix that.
kindly ping @chipzoller
Does it make sense?
Checklist

[x] I have read the policy contribution guidelines.
[x] I have added test manifests and resources covering both positive and negative tests that prove this policy works as intended.

Before approving, need to test and validate on at least the current 1.5.x release and preferably also 1.6-dev-latest.

I've tested it on locally and it worked as expected 👇
It should be a boolean btw, I got an error when I change it as string

kyverno-568449c9d6-fdptz kyverno E0131 16:19:10.359522       1 mutation.go:86] WebhookServer "msg"="mutate error" "error"="failed to validate resource mutated by policy add-default-securitycontext: ValidationError(io.k8s.api.core.v
1.Pod.spec.securityContext.runAsNonRoot): invalid type for io.k8s.api.core.v1.PodSecurityContext.runAsNonRoot: got "string", expected "boolean"" "action"="mutate" "gvk"="/v1, Kind=Pod" "operation"="CREATE" "resource"="default/Pod/"


TextInput not support Chinese input/clear() function doesn`t work in recent release of Reac-Native

It seems like a very big problem, and not all TextInput component access to have this problem. I just found if I use defaultValue props, it will happen. This problem in react-native version 0.54.0～0.55.1, but normal in 0.53.0

Problem has been solved here #18456

i fixed the bug from @mkjfeng01. thanks.

react-native version 0.55.3 has the same problem

Same in react-native: 0.55.4.

Any updates on this issue?

@SunAnle @winglleung @johnxie Follow these file changes, and modify your code manual. I think this will solve your problem.

I find a workaround for this issue.
my experience with this bug is that
(a). Chinese input goes "dissappear" and only English letters are left in the textInput
(b). prop value of textInput cause this 1
(c). If you want to use .clear(), you have to have prop value, otherwise .clear() won't clear input field in this release.
the workaround is NOT use prop value and .clear(), instead use setNativeProps.
following is my code sample.
<TextInput
        multiline={this.props.multiline}
        onChangeText={(text) => this.onChangeText(text)}
        //value={this.props.text}
        blurOnSubmit={false}
        //{...this.props.textInputProps}
        ref={component => this._textInput = component}
        onSubmitEditing={() => {
          this.clearText()
        }}
      />

and
  clearText(){
    if (Platform.OS === 'ios') {
      this._textInput.setNativeProps({ text: ' ' });
    }

    setTimeout(() => {
      this._textInput.setNativeProps({ text: '' });
    },5);
  }

Hope it helps.

@leonyhenn amazing, you save my life!


(1.0.55 pre-release) Changing network causes all WSL windows to disappear

Windows build number:
10.0.19045.3086, I was able to reproduce it on 10.0.22621.1992 as well
Your Distribution version:
22.04
Your WSL versions:
WSL version: <IP_ADDRESS>
Kernel version: <IP_ADDRESS>-1
WSLg version: 1.0.55
MSRDC version: 1.2.4419
Direct3D version: 1.608.2-61064218
DXCore version: 10.0.25880.1000-230602-1350.main
Windows version: 10.0.19045.3086
Steps to reproduce:

Install the latest WSL pre-release (1.3.14 bundling WSLg 1.0.55 at the time of writing)
Start any GUI application (in my repro, I'm running xclock -update 1 command from Windows Terminal but this seems to be reproducible with any app - I noticed it with Sublime Text 4 and kitty too; no matter if the app is set to use X11 or Wayland)
Disconnect from Wi-Fi or, if you're using Ethernet card, disable the network adapter that connects you to the Internet in Control Panel.
See that all Linux app windows disappear once the connection is stopped.

WSL logs:
WslLogs-2023-07-31_18-43-52.zip
stderr.log
wlog.log
pulseaudio.log
weston.log
WSL dumps:
No files are available in the /mnt/wslg/dumps directory.
Expected behavior:
I expect the windows of Linux apps to still be visible after I disconnect from the network.
Actual behavior:
All windows of the Linux apps disappear.

I see the same issue (i've reported this in the release discussion, see https://github.com/microsoft/WSL/discussions/10302#discussioncomment-6504163,  but i guess opening an issue is the better approach)

Welp, GitHub searched has failed me, I did look for a release discussion at some point before pinpointing what the issue is. But yeah I guess making a tracking issue for this isn't a bad idea anyway 😄
apparently I searched for "1.3" and for "1.3.10" and wrongly assumed that pre-releases probably don't have release discussions associated with them

same behavior of closing windows still happens with releases 1.3.15 and 1.3.17 ..

just noticed that after sleep my wifi interfaces were gone (blank list, smth with device probably), emacs window was available. Once it finally scanned wifi networks and reconnected to my home wifi, emacs windows disappeared.
I have simillar errors in wlog.log as issue reporter:
[13:40:43:339] [11:11] [ERROR][com.freerdp.core.transport] - BIO_read returned a system error 11: Resource temporarily unavailable
[13:40:43:343] [11:11] [ERROR][com.freerdp.core] - transport_read_layer:freerdp_set_last_error_ex ERRCONNECT_CONNECT_TRANSPORT_FAILED [0x0002000D]
[13:40:43:367] [11:11] [ERROR][com.freerdp.core.transport] - BIO_should_retry returned a system error 32: Broken pipe
[13:40:43:367] [11:11] [ERROR][com.freerdp.core.transport] - BIO_should_retry returned a system error 32: Broken pipe
[13:40:43:367] [11:11] [ERROR][com.freerdp.core.transport] - BIO_should_retry returned a system error 32: Broken pipe
[13:40:43:367] [11:11] [ERROR][com.freerdp.core.transport] - BIO_should_retry returned a system error 32: Broken pipe
[13:40:43:367] [11:11] [ERROR][com.freerdp.core.transport] - BIO_should_retry returned a system error 32: Broken pipe
[13:40:44:469] [11:11] [ERROR][com.freerdp.core.transport] - BIO_should_retry returned a system error 32: Broken pipe
[13:40:44:469] [11:11] [ERROR][com.freerdp.core.transport] - BIO_should_retry returned a system error 32: Broken pipe

any way to do rollback without losing my distro?

Restarting WSL using WSL --shutdown and then opening a new window doesn't fix it? I know that fixes issues around external drives not being available for use if they were ejected at any point during the life of WSL , so it's worth a shot

Restarting WSL using WSL --shutdown and then opening a new window doesn't fix it?

Sure, so does killing the individual GUI processes inside the running WSL instance and just opening them again but it shouldn't be happening in the first place, especially considering that this used not to be a problem.

Restarting WSL using WSL --shutdown and then opening a new window doesn't fix it? I know that fixes issues around external drives not being available for use if they were ejected at any point during the life of WSL , so it's worth a shot

it's more like if you start another window/gui application, all disappeared windows appear, but my emacs-client windows remains unresponsive though. Killing and restarting it works, but it's annoying, I'm losing my open buffers etc literally after every sleep.

Restarting WSL using WSL --shutdown and then opening a new window doesn't fix it?

Sure, so does killing the individual GUI processes inside the running WSL instance and just opening them again but it shouldn't be happening in the first place, especially considering that this used not to be a problem.

agree. It's kind of basic scenario of use (does MS perform any testing though :D )

Restarting WSL using WSL --shutdown and then opening a new window doesn't fix it?

Sure, so does killing the individual GUI processes inside the running WSL instance and just opening them again but it shouldn't be happening in the first place, especially considering that this used not to be a problem.

I am aware and at no point did I say that it was a fix for the issue or anything more than a stopgap. The question was is there any way to fix it without losing the distro, which made it sound like they were just never coming back instead of only being temporarily unavailable.

The question was is there any way to fix it without losing the distro, which made it sound like they were just never coming back instead of only being temporarily unavailable.

Ah, you were referring to the question. My belief is that the question was actually asking whether there is a way to rollback to an older (non-prerelease) version of WSL and to answer that - yes, there is. I believe wsl --update --rollback should work, that's what I did when running into this issue to confirm that it's in fact a new problem.

The question was is there any way to fix it without losing the distro, which made it sound like they were just never coming back instead of only being temporarily unavailable.

Ah, you were referring to the question. My belief is that the question was actually asking whether there is a way to rollback to an older (non-prerelease) version of WSL and to answer that - yes, there is. I believe wsl --update --rollback should work, that's what I did when running into this issue to confirm that it's in fact a new problem.

thanks! tried wsl --update --rollback before asking, there is no --rolback parameter on my instance for some reason:

it just prints help instead of rolling version back 🤔

still happens to me with
WSL: <IP_ADDRESS>
WSLg: 1.0.57

still happens with 2.0.4.  I thought the new wslinfo command might get some insights but alas it just tells me that i use nat which i knew beforehand :-)

Weird thing that I tested it with emacs client window and xfce4-terminal, emacs disappears after network change and reappears after opening another frame but unresponsive. Xfce4-terminal doesn't disappear and responsive

I primarily use (ubuntu 22.04's standard) emacs where i get the disappearing-window problem but quick experimentation shows also same behaviour with new pgtk emacs 29 or newer, xterm, gnome-text-editor and, contrary to Dmitry's experience, also with xfce4-terminal.   Also, starting a new xapp usually makes them all re-appear and being responsive. The caveat "usually" is that sometimes when the network dis/reconnects is due to a hibernation, then the xapps die (which seems due to that wslg/x-server dies and while automatically restarted obviously doesn't "inherit" the apps running at crash time ...)

Started to happen to me as well today.
WSL version: <IP_ADDRESS>
Kernel version: <IP_ADDRESS>-1
WSLg version: 1.0.59
MSRDC version: 1.2.4677
Direct3D version: 1.611.1-81528511
DXCore version: 10.0.25131.1002-220531-1700.rs-onecore-base2-hyp
Windows version: 10.0.22621.2428

Darn, did MS release WSL2 2.0 to stable channel without fixing this? :/

WOW! This is truly annoying, no way to rollback and every change in network I must reopen all my windows. Is there anyone from Microsoft on this thread?

OK, I give up, I was perfectly happy with WSL, except from two events that completely broke it:

suspend/resume regression due to Microsoft fix[1], which was resolved for Windows 11 22H2 and not for earlier versions
this one which is a regression, but I cannot find the root cause.

@Jackenmen please modify title to allow people find this issue, something like: "X applications stop responding when Windows network is modified"
I truly want to avoid installing xserver.
[1] https://github.com/microsoft/WSL/issues/6982

I can add that I don't think the issues are the same.  I get this behaviour and thought it was hibernate / standby / restore related but was on a train today and had an eclipse window disappear on me when the network dropped.  Just re-running eclipse brings the original window back fully working (it also tries to start a new eclipse which fails as it is already using the workspace).
Every now and again it also doesn't reconnect, and I have to kill it and restart it, but it is rare enough for me to not be too worried about that.
I think that this is something to do with the MSRDC connection breaking when the network changes.  I don't know then if this means that the connection is made via the wrong IP address.  I also don't know how this would be controlled...

Sorry I didn't report this earlier, but I found on Monday that when all windows are gone, I just have to start a new xterm from bash (the most simple Wslg program I can think of), and everything pops up back. Some glitches but by clicking and wait that all event handlers reconnect, everything goes back to normal in 2 or 3 seconds.
I use Jetbrains' PhpStorm with at least 3 windows open.
It was a real pain as many services attached had to be killed/restarted before I found this by accident.
Hope it works for you, while this bug is fixed. I saved my days.

yes, I am aware if that except that xfce4-terminal pops up and is
unresponsive and it is my main tool.

I have the same issue. As a workaround I run xclock  from terminal, then my disappeared windows appear again.

I agree that running an x application after the windows disappear seems to mostly bring them back.  I have also seen an application stop when the networking changes (most often on restore from hibernate); a guess is that that application does something graphical while the GUI is gone and causes a crash somehow.
It used to be possible to hibernate and resume without losing windows so something has changed.  A possible place that could have changed though is Hyper-V... maybe this has changed what happens when network cables are disconnected?
Ideally since I can do this manually something would reconnect when it disconnects, and then the problem would likely be solved...

Dear @Microsoft Representative,
Please review and merge #1108, #1092, #1098 bugs.
Please acknowledge you accept the issue and working on a solution.
Please tell us if you require any missing information from us users to make a progress.
WSL is unusable when every network change/sleep/hibernate all applications need to be reopened.
Forgive me that I am pasting this to all bugs, I do not know which if any you monitor.
Thanks,

This is a really annoying and frustrating issue.
WSL-Version: <IP_ADDRESS>
Kernelversion: <IP_ADDRESS>-1
WSLg-Version: 1.0.59
MSRDC-Version: 1.2.4677
Direct3D-Version: 1.611.1-81528511
DXCore-Version: 10.0.25131.1002-220531-1700.rs-onecore-base2-hyp
Windows-Version: 10.0.22621.2715
Changing MESA_D3D12_DEFAULT_ADAPTER_NAME has not effect on this issue.

@alonbl, @fargiolas, @burak-58 and all, thanks for keep updating us. We acknowledge the issue and are investigating the possible solutions. Basically, this occurs when remote desktop connection between Windows and WSL lost by network configuration change, but there are 2 different outcomes. When RDP connection is lost, the remote desktop client software (msrdc.exe) running on Windows terminates, and WSL auto-restart it. First issue is, the auto-restart itself is successfully done, but old windows are not restored. As @burak-58 reported, in this case, by opening another window should restore all other window. This is somewhat easy-fix, and hopefully we can address soon. The second issue more complex one, in this case the successively launched msrdc fails to establish the connection with WSLg, this ends up the log reported by @fargiolas. We have multiple reports of this symptom, including the case from sleep/hibernate, and this is most likely beyond WSLg scope and by some issue from WSL/Windows network integration layer. Unfortunately, I personally don't have local repro for this, thus it's possible some unique configuration might be required. @fargiolas, just for reference, if you perform some network operation between WSL and Windows, what would happen to them, for example, copying large file between WSL and Windows, then disconnect Windows network? Does the copy fail or keep going? Anyway, this is where we are on this issue, thanks!

Hello @hideyukn88,
Thank you so much for confirming this.
I have 100% reproducible of xfce4-terminal window lost when network change, and is restored when opening a new window (for example another xfce4-terminal), it is shown but unresponsive. In the new xfce4-terminal I can kill the previous one using kill command to get rid of the unresponsive window.
I can provide any data you need to help resolve the issue, please tell me what to collect.
Thanks,

@alonbl, I just tried xfce4-terminal and it looks working fine after window is restored. In my end, it works as wayland-native (not X11), is it to you as well? If so, how about other wayland-native app, will it be unresponsive too? thanks!

Same for me as for @alonbl, but with emacs in pgtk version. If I understand correctly, pgtk emacs runs purely on top of wayland.
It just completely unresponsive when reappears. Opening new windows doesn't make it responsive, new emacs windows are unresponsive too it doesn matter client window or standalone

Hello @hideyukn88,
Thank you for checking this out.
xterm for example is resumed correctly.
xfce4-terminal is not, if I strace the process of the window that is reappear I get poll wakeup events when focus and mouse click but the window itself is not responding.
Some information we compare:
DISTRIB_DESCRIPTION="Ubuntu 22.04.3 LTS"
xfce4-terminal 0.8.10 (Xfce 4.16)
XWAYLAND1 connected 1920x1080+0+0 (normal left inverted right x axis y axis) 0mm x 0mm

WSL version: <IP_ADDRESS>
Kernel version: <IP_ADDRESS>-1
WSLg version: 1.0.59
MSRDC version: 1.2.4677
Direct3D version: 1.611.1-81528511
DXCore version: 10.0.25131.1002-220531-1700.rs-onecore-base2-hyp
Windows version: 10.0.22621.2715

WSLg ( x86_64 ): 1.0.59+Branch.main.Sha.2bffa4a1867601b1fd0e3c7bb59ada9f6131c28e
Mariner: VERSION="2.0.20230630"
DirectX-Headers:
mesa:
pulseaudio: 6f045ff0dca233a939a2aba815f84d177e294122
FreeRDP: c4030980b29322a9cb2190711a5fadeeeb8b6a33
weston: 1c19fc5ecdd4552f36f77256e1fb53225801aff0

/mnt/wslg/stderr.log:
[22:54:56.080] <5>WSLGd: Run:108: pid 1242 exited with status 0, /init /mnt/c/Program Files/WSL/msrdc.exe msrdc.exe /v:8BA75DC0-97EE-4012-A17E-AB94CB7D55F8 /hvsocketserviceid:362A0DB8-FACB-11E6-BD58-64006A7986D3 /silent /wslg /plugin:WSLDVC_PACKAGE /wslgsharedmemorypath:WSL\8BA75DC0-97EE-4012-A17E-AB94CB7D55F8\wslg C:\Program Files\WSL\wslg.rdp
Error: debug scope named 'rdp-audio' is already registered.
Error: debug scope named 'rdp-audio-in' is already registered.
The XKEYBOARD keymap compiler (xkbcomp) reports:
> Warning:          Unsupported maximum keycode 569, clipping.
>                   X11 cannot support keycodes above 255.
> Internal error:   Could not resolve keysym XF86FullScreen
Errors from xkbcomp are not fatal to the X server

/mnt/wslg/weston.log:
[22:56:57.543] unable to checkDescriptor for 0x557c03b43210
[22:56:57.657] app_list_monitor_thread: stopRdpNotifyEvent is signalled. 1
[22:56:57.657] rdp_rail_notify_app_list(): rdp_peer 0x557c03b40df0
[22:56:57.657]     inSync: 0
[22:56:57.657]     syncStart: 0
[22:56:57.657]     syncEnd: 0
[22:56:57.657]     newAppId: 0
[22:56:57.657]     deleteAppId: 0
[22:56:57.657]     deleteAppProvider: 1
[22:56:57.657]     associateWindowId: 0
[22:56:57.657]     appId: (null)
[22:56:57.657]     appGroup: (null)
[22:56:57.657]     appExecPath: (null)
[22:56:57.657]     appWorkingDir: (null)
[22:56:57.657]     appDesc: (null)
[22:56:57.657]     appIcon: (nil)
[22:56:57.657]     appProvider: Ubuntu-22.04
[22:56:57.657]     appWindowId: 0x0
[22:56:58.620] Client: ClientStatus:0x3f5
[22:56:58.620]      - TS_RAIL_CLIENTSTATUS_ALLOWLOCALMOVESIZE
[22:56:58.620]      - TS_RAIL_CLIENTSTATUS_ZORDER_SYNC
[22:56:58.620]      - TS_RAIL_CLIENTSTATUS_WINDOW_RESIZE_MARGIN_SUPPORTED
[22:56:58.620]      - TS_RAIL_CLIENTSTATUS_HIGH_DPI_ICONS_SUPPORTED
[22:56:58.620]      - TS_RAIL_CLIENTSTATUS_APPBAR_REMOTING_SUPPORTED
[22:56:58.620]      - TS_RAIL_CLIENTSTATUS_POWER_DISPLAY_REQUEST_SUPPORTED
[22:56:58.620]      - TS_RAIL_CLIENTSTATUS_GET_APPID_RESPONSE_EX_SUPPORTED
[22:56:58.620]      - TS_RAIL_CLIENTSTATUS_BIDIRECTIONAL_CLOAK_SUPPORTED
[22:56:58.620] Client HandShake buildNumber:22621
[22:56:58.630] Server AppList caps version:4
[22:56:58.630]     appListProviderName:Ubuntu-22.04
[22:56:58.630]     appListProviderUniqueId:362A0DB8-FACB-11E6-BD58-64006A7986D3
[22:56:58.661] Client: gfxredir_caps: length:28
<snip>

If you have a specific application or configuration you want to test please write to me and I will test, I mostly use the xfce4-terminal as wslg application.
Regards,

@hideyukn88 thank you for looking into this and for the very welcome feedback! sad to hear my side of the issue is the trickiest one. It could totally be something specific with my setup, lots of factors I cannot exclude like company firewall/proxy/vpn. But it used to work pretty fine, seems it has something to do with the new WSL networking features, which I'm not using, that were introduced in 2.x.
I tried copying from windows to linux over 9p and disconnecting wifi in between. No issue, file transfer keeps going without any error.
One thing I noticed that may help you to reproduce the issue is that both native wayland (emacs compiled with pgtk in my case) and XWayland (tested with xterm) disappear. When I launch a new graphical app both come back but while I can interact with xterm the native wayland app becomes unresponsive/stops to receive input events.
Let me know if I can be of any further help, feel free to contact me by mail if you want more direct feedback.

@fargiolas, to rule out your environmental changes, if you don't mind, would you please install older version of WSL and find out which WSL version does not exhibit the issue? You can install older version of WSL from https://github.com/microsoft/WSL/releases. (you do not need to try the release marked as "pre-release"). If you can find which release works and then from which release doesn't work, then we could find some clue from the differences, and it would help us a lot. Installing/uninstalling older WSL (as long as released version) should not impact your Linux distro configuration, but just for disclaimer, there could be possibility it might cause some negative impact to your installation, if you have another backup system to try, that could be safer, thanks!

Hello, I have the same issue - unresponsive graphical app after network change/sleep. In my case, the last WSL version which works without problem is:
Verze WSL: <IP_ADDRESS>
Verze jádra: <IP_ADDRESS>-3
Verze WSLg: 1.0.54
Verze MSRDC: 1.2.4240
Verze Direct3D: 1.608.2-61064218
Verze DXCore: 10.0.25880.1000-230602-1350.main
Verze Windows: 10.0.22000.2538

@milan-melena, thanks for info, what apps do exhibit the issue? thanks!

At least emacs compiled --with-pgtk. I'm not sure if I tried something else.

Same issue(unresponsive after recover) with gnome-terminal (ubuntu 22.04 flavor), not only with pgtk emacs

@DmitryGrayscale, @milan-melena, while that apps remain unresponsive, can another wayland app be started and does that new one work correctly? thanks!

yes, another wayland app can be started and works correctly.

@milan-melena, would you please take strace log? if you can try with xfce4-terminal, then strace xfce4-terminal. If gnome-terminal, then you launch it first, then find PID of gnome-terminal-server, then strace -p <PID>, then change network configuration, then launch xclock to restore window, hopefully it shows which system call stuck it, thanks!

@hideyukn88 thanks, I'll get back with the version information as soon as I can.
Please note that while the wayland app disappears and when it gets back it's not stuck or frozen, it's still running fine. You can still it updating the window just fine if it was running something. The problem seems more that it's not receiving user input (keyboard and mouse events) anymore.

@hideyukn88, I apologize, but I currently do not have WSL with the error installed. Right now, I don't have much free time for reinstallation and experiments. Perhaps someone else with the erroneous version of WSL can retrieve a strace log.

@hideyukn88,
I wounder why you ask this from someone specific, so far I provided you with all the information so far for this specific issue, please bear with me so that you have a single vector of problem determination.
Attach is the strace log[1].
Please see marker @ALONBL: CHANGE NETWORK when  change network and @ALONBL: RESTORE when I run xterm to re-show windows, during which and until @ALONBL: UNRESPONSIVE TO USER no user response from user although there is activity, then I kill the process.
Versions were attached at [2]
Regards,
[1] xfce.log
[2] https://github.com/microsoft/wslg/issues/1092#issuecomment-1861629048

@fargiolas, this is very helpful and interesting clue, if you switch the focus to that window by ALT+TAB (not by mouse), and type in something with keyboard, is the input delivered to application? And do see you the wayland application window is moved/changed before/after disappearance? thanks!

@hideyukn88 thanks, I'll get back with the version information as soon as I can.
Please note that while the wayland app disappears and when it gets back it's not stuck or frozen, it's still running fine. You can still see it updating the window just fine if it was running something. The problem seems more that it's not receiving user input (keyboard and mouse events) anymore.

@hideyukn88, I created named pipe and sent some input while doing cat mypipe in frozen gnome-terminal instance, and even though I can't focus window, I see pipe output dynamically, so the window actually updates.
Alt +Tab does not work for me, still can't type in the window. Also cannot close the window with close button, only from windows taskbar.
If I start second gnome-terminal instance, it is unresponsive too. The same is for emacs.

@DmitryGrayscale, thanks for info.

Also cannot close the window with close button, only from windows taskbar.

So it looks mouse input are not delivered, but other non-keyboard, non-mouse inputs are working as closing from Windows's taskbar works, which Windows still send command over RDP channel to our WSLg shell inside WSL, then closing app itself are same method as clicking "x" in title bar.

If I start second gnome-terminal instance, it is unresponsive too. The same is for emacs.

This differs from what @milan-melena reported at https://github.com/microsoft/wslg/issues/1092#issuecomment-1863545241, so there might be some other factor. Does X11 app works? only wayland apps are unresponsive? If X11 app still works, then would you please try below?
1: Run wayland app.
2: Change network configuration (so wayland app to be gone from screen).
3: Run some X11 app (say xclock), and double check wayland app reappears and unresponsive.
4: Move focus to that newly launched X11 app (which is working correctly).
5: Press keyboard's "LEFT CTRL" then (while keep holding it) pressing "LEFT SHIFT", then (while keep hold both of them) press SPACE BAR. Then release all those three keys (Left Ctrl, Left Shift and Space bar) then immediately press 'w' key.
6: You will see the section of debug message starting "rdp debug binding 'W' - dump all window." inside /mnt/wslg/weston.log, please share the entire section with us.
Thanks!

dump.log
Here is the dump

@fargiolas, this is very helpful and interesting clue, if you switch the focus to that window by ALT+TAB (not by mouse), and type in something with keyboard, is the input delivered to application? And do see you the wayland application window is moved/changed before/after disappearance? thanks!

I can focus on the unresponsive window both with mouse and with ALT+TAB, it  but it seems no input event gets delivered to the app itself. I can maximise it with win+up, stick to the sides with win+left win+right. The window is updated correctly. It's just input events that are not delivered. Window is not moved when the network changes, same place same size.
I can close it from the taskbar but not from the window buttons, but that is expected as gtk on wayland uses client-side decorations so if no input event goes to the app you won't be able to click on the buttons. I cannot resize the window with side and corner handles, and I cannot drag it with the titlebar, as that all happens client-side on wayland.
Attaching a "dump all windows" weston log. Two windows were there, one xterm on XWayland and emacs on pure wayland.
dump-all-windows.log

@DmitryGrayscale, @fargiolas, thanks for log. This really puzzle me.
1: Given X11 application is working after reappearing, this indicate Windows and WSLg connection is properly working. For input-wise, windows (and RDP) don't care if it's wayland or X11 application.
2: Given below, it indicates "foreground window" is properly sync-ed with Windows and WSLg, and input message (in this case, it not keyboard or mouse message though) is delivered to correct foreground application.

I can maximise it with win+up, stick to the sides with win+left win+right. The window is updated correctly.

3: Given Wayland application can still update screen, this indicates the wayland application and compositor (and Windows) are still have valid connection for graphics output.
4: Given provided logs, compositor is aware of the wayland application surface and have proper input extents, and all other fields shows proper numbers.
At this point, I will need to build some private drop of system-distro VHD with some extensive logging. I will post such system-distro VHD after our holiday season, and hopefully anyone who has this issue can try out that to collect some more data, thanks for helping us!

@hideyukn88 thanks again, I should have some more time to better look into this too in the holidays. Will let you know if I find anything.
Meanwhile I was able to reproduce this on my win11 development evaluation vmware image with gnome-clocks (just to confirm it's something with wayland apps and not emacs specific).
Nothing exotic about network configuration, just the default image running with VMPlayer.
Started a stop watch in gnome-clocks, disconnect the network, reconnect, see it disappear, bring it back with xeyes, stop watch still running and updating. Can focus on the window, it knows it's focused because buttons grey out when unfocused and are normal again when focused, still cannot interact with it.
One thing that may add additional information: wayland and xwayland apps usually have a different mouse pointer style, before disappearing the wayland app has the usual wayland style, after reappearing it has the xwayland mouse pointer.

And do see you the wayland application window is moved/changed before/after disappearance? thanks!

@hideyukn88 I'll have to correct myself, after more testing I've seen the window move when it's restored after disappearance (easier to see after including https://github.com/microsoft/weston-mirror/pull/156).

@hideyukn88 Take this with a grain of salt as I'm not so familiar with the code base.
Looking at mouse motion it seems while I get the motion events on the rdp/rail side they never trigger a protocol motion event. As far as I can tell it is because pointer->focus_client in pointer_send_motion (libweston/input.c) is NULL. Something related to focus handling I guess, weston_pointer_set_focus calls find_pointer_client_for_surface/weston_pointer_get_pointer_client and cannot find a matching one.
Didn't investigate the keyboard focus side but I guess it's similar. No idea why that would happen though, could totally be a side effect of another problem elsewhere. Maybe some state is lost/not correctly restored when everything is restarted.
Hope this helps, I'll update you if I find anything else.

Same for me as for @alonbl, but with emacs in pgtk version. If I understand correctly, pgtk emacs runs purely on top of wayland. It just completely unresponsive when reappears. Opening new windows doesn't make it responsive, new emacs windows are unresponsive too it doesn matter client window or standalone. Complete restart of all emacs instances including server helps. It could just be emacs bug actually...

I found a way around this by recompiling emacs with lucid. Now when the window reappears it is responsive. Just starting testing this so I don't know what other consequences may there be in using lucid instead of gtk though.

Same for me as for @alonbl, but with emacs in pgtk version. If I understand correctly, pgtk emacs runs purely on top of wayland. It just completely unresponsive when reappears. Opening new windows doesn't make it responsive, new emacs windows are unresponsive too it doesn matter client window or standalone. Complete restart of all emacs instances including server helps. It could just be emacs bug actually...

I found a way around this by recompiling emacs with lucid. Now when the window reappears it is responsive. Just starting testing this so I don't know what other consequences may there be in using lucid instead of gtk though.

lucid works because it runs on X. The issue here is with running GUI apps natively on wayland. For me the main reason to run Linux apps on wayland natively in WSL is proper support for hidpi scaling (fixes issues with blurry font rendering etc..) . For now I'm sticking to running Emacs in Windows Terminal. Frankly, the GUI stuff in WSL feels like alpha software at the moment.

@fargiolas thanks for your analysis, I think I have some idea on what's going on. Would you please try below private system distro VHD with some debugging message enabled, and once unresponsiveness app is set to foreground, please run grep DEBUGDEBUG /mnt/wslg/weston.log and share output with us, thanks!
https://1drv.ms/u/s!AqQ2qEh_9iIOhqtw-_5CUhK2i33Mdw?e=q334BA
You can refer below for how to use private system-distro VHD.
https://github.com/microsoft/wslg/blob/main/CONTRIBUTING.md#installing-a-private-version-of-the-wslg-system-distro
Also if possible, can you also try with Wayland reference app, sud as weston-editor? If you are using Ubuntu, you can get it by installing weston package by sudo apt install weston, and compare how the DEBUGDEBUG  messages are differ from other nonresponsive wayland app? thanks!

@hideyukn88 tried the system distro image on my work laptop and it gives me an access denied error. Could be something about the work setup, I'll try again on a clean VM later today.
Meanwhile, weston-editor does not show the issue here, I can focus on the window after restarting the RDP client. One notable difference is that it has the same window decorations as xwayland apps, while gtk wayland clients gtk decorations.

@fargiolas, thanks for trying out, what exact error do you see? if possible, share exact message of error or screenshot?

One notable difference is that it has the same window decorations as xwayland apps, while gtk wayland clients have gtk decorations.

Yes, this is expected. Since, for Wayland application, window decoration must be rendered by app itself, weston-editor uses same window decoration as xwayland window manager, as they are built from same source code repo, thanks!

@hideyukn88 it was an access denied error when mounting the system vhd image (Wsl/Service/AttachDisk/MountVhd/E_ACCESSDENIED). I wouldn't give it too much thought, it's probably something with corporate antivirus/firewall/acls/something.
I tested the vhd image in the WinDev2311Eval VM and it fixes the problem for me! Emacs windows is restored as soon as msrdc.exe is restarted and I can finally focus on it again!
Attached a weston log produced starting up Emacs (pgtk backend), killing msrdc.exe process tree from Windows Task Manager watching it disappear and reappear and focusing on it again.
Let me know if I can be of any further help or run more tests!
weston.log

Just for completeness, here's a similar log produced with weston-editor (which didn't show the problem though).
weston-editor.log

@fargiolas and all, thanks for helping us to address this issue. We are going to address this issue in two ways.
1: At first, the remote desktop connection to WSLg/Linux VM should not be disconnected when Windows host's network configuration is changed. I already made a fix to remote desktop client software (msrdc.exe or its variant), so WSLg window will no longer disappear from desktop at network change, and this is what it ideally should be. The fix is already in pipe, but because this is external component (from WSLg's aspect), it will be for a while to be integrated to WSL release.
2: Second, in case RDP connection is dropped for whatever reasons (like @fargiolas kills msrdc process from task manager), it still should restore properly. At this point, I think this could possibly be an issue in GDK framework. From wayland perspective, when RDP connection is dropped and restored, it appears as wl_seat is gone then recreated. I think this might be an unlikely event in normal Linux desktop environment, thus there might be some missing piece, and this is why Wayland reference app, such as weston-editor, works properly, but this is just my speculation at this point, and further investigation is still required, thanks!

@hideyukn88 Unfortunately I tested the system image in another Win11 VM and it still shows the issue. So we may still be missing something. Still trying to understand how the two setups differ. Here's a similar weston log, you can see there is a "not found" line this time. Hope this helps.
weston.log

@fargiolas, thanks for trying out, the provided system distro image at https://github.com/microsoft/wslg/issues/1092#issuecomment-1875759846 is for collecting more debugging information, it is not intended to fix anything.

you can see there is a "not found" line this time. Hope this helps.

This indicate the possible issue I described at 2) in https://github.com/microsoft/wslg/issues/1092#issuecomment-1879179606, which application doesn't reinitialize wl_keyboard upon wl_seat recreation timely, at least, before the application gains the input focus, so since setting focus is failed, no keyboard and mouse inputs are sent to the application.

[11:08:21.613] DEBUGDEBUG: client:0x55f7ae5b80f0 pid:62 image:/usr/local/bin/emacs-30.0.50 is added
...
[11:08:36.880] DEBUGDEBUG: looking for client:0x55f7ae5b80f0, NOT found

@fargiolas, thanks for trying out, the provided system distro image at #1092 (comment) is for collecting more debugging information, it is not intended to fix anything.

My bad, was overly optimistic when I saw focus working again, was hoping the fix may come from the last zorder commit in weston-mirror. Not sure what's different about that setup, according to wsl.exe --version everything is the same, yet one shows the focus problem one doesn't. Even tried other gtk apps (gedit e.g.) again to rule out something emacs specific, same results. Agree it seems something gtk specific. If you need further testing let me know.

GTK bug for wl_seats handling: https://gitlab.gnome.org/GNOME/gtk/-/issues/6335

PS C:\Users\gpettey> wsl --version
WSL version: <IP_ADDRESS>
Kernel version: <IP_ADDRESS>-1
WSLg version: 1.0.59
MSRDC version: 1.2.4677
Direct3D version: 1.611.1-81528511
DXCore version: 10.0.25131.1002-220531-1700.rs-onecore-base2-hyp
Windows version: 10.0.19045.4046

Today I noticed that starting another application in WSlg (e.g. gvim) restores all my windows that disappeared after a network change.

Hi,
Yes, the new version of wsl restarts the RDP connection.
However, xfce4-terminal which is based on GTK loses input channel, and konsole whic his based on QT after several cycles looses clipboard integration. It seems like most of the wayland application did not QA the seat re-connection.
I am waiting for the RDP fix so that RDP will not drop connection when network change occurs, not sure why a network change as global causes RDP to drop connections to networks that are available.
Regards,

Hello,
Pre-release <IP_ADDRESS> seems to solve the network change event that triggers restart of RDP session, no restarts wayland applications continue to run as usual.
However, Windows sleep still triggers restart of RDP session, which means that this issue is still not fully resolved as within a valid lifetime of a valid user experience there may be network change, sleep or hibernate events.
Regards,

Hi,
Thanks for the update on this. I will try to update WSL then as this is an
improve on the situation.
Antonio COLLAZOS CARRERA
Senior Backend Engineer
@.***
C/Vivero 5, 4ªplanta, 28040 MADRID
https://maps.google.com/maps?q=C/Vivero 5, 4ªplanta, 28040 MADRID
https://barbara.tech
[image: linkedin] https://www.linkedin.com/company/barbara-edge [image:
twitter] http://www.twitter.com/barbara_edge_ai [image: youtube]
@.***>
El vie, 26 abr 2024 a las 20:02, Alon Bar-Lev @.***>)
escribió:

Hello,
Pre-release <IP_ADDRESS> seems to solve the network change event that triggers
restart of RDP session, no restarts wayland applications continue to run as
usual.
However, Windows sleep still triggers restart of RDP session, which means
that this issue is still not fully resolved as within a valid lifetime of a
valid user experience there may be network change, sleep or hibernate
events.
Regards,
—
Reply to this email directly, view it on GitHub
https://github.com/microsoft/wslg/issues/1092#issuecomment-2079846695,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/A7DNQFPR5OU4K2OINPUC6I3Y7KJDJAVCNFSM6AAAAAA26Q3LSGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDANZZHA2DMNRZGU
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

--
Barbara is certified in ISO 27001 and ISO 9001.
This email message
may contain confidential or legally protected information and is intended
solely for the use of the intended recipient(s). Any disclosure,
dissemination, distribution, copying, or taking any action based on the
information contained herein is prohibited. Emails are not secure and
cannot be guaranteed to be free of errors as they may be intercepted,
altered, or contain viruses. Barbara is not responsible for errors or
omissions in this message and denies any liability for damages arising from
the use of email. Any opinions and other statements contained in this
message and any attachments are the sole responsibility of the author and
do not necessarily represent those of the company.
https://www.barbara.tech/privacy-policy
https://www.barbara.tech/privacy-policy

but my emacs-client windows remains unresponsive

I've found resizing the window to fix this on windows 11.

I have tried resizing a chrome window and it doesn't appear possible (I tried both directly and using shortcuts).  An eclipse window using GDK_BACKEND=x11 stays available, but the Chrome window using Wayland stays visible but I can no longer interact with it after standby or hibernate followed by resume.


USHIFT-1546: Use gomplate templating engine

/test microshift-metal-tests

/cc @dhellmann

Putting on hold because to get this to 4.14, we need OCPBUGS tickets
/hold

/test ?

/test metal-periodic-test

This looks like a good change. The tool offers some options for passing inputs, so we could consider moving some values out of environment variables into a config file if that would make anything easier. There are some other types of files that use sed for replacing values (the kickstart templates are the main ones that come to mind), and we should convert those, too, but that can happen in another PR.
What does the team think about when to merge this?

This looks like a good change. The tool offers some options for passing inputs, so we could consider moving some values out of environment variables into a config file if that would make anything easier. There are some other types of files that use sed for replacing values (the kickstart templates are the main ones that come to mind), and we should convert those, too, but that can happen in another PR.
What does the team think about when to merge this?

I kept envvars so when we backport the change to 4.14, it doesn't change too much.
For 4.15 onwards, I'd definitely would try to ditch the envvars and use some explicit args instead

/unhold

/unhold
Looks great, thanks @pmtk !

/cherrypick release-4.14


Very narrow windows cause "undefined" to be printed repeatedly

Go here
http://iplayif.com/?story=http%3A%2F%2Fwww.ifarchive.org%2Fif-archive%2Fgames%2Fzcode%2Fcurses.z5
This is Graham Nelson's Curses
Now make your browser as small as possible and refresh the page
I mentioned this to you about 10 years ago
This is of little concern to me today but important to you
Once upon a time I intended to release an app...

I think this is fixed now


Adapt changes from HDM

Adapt changes regarding "production" environment from HDM https://github.com/betadots/hdm/pull/106

hdm.yaml
database.yaml
hdm.service
mv development.sqlite => production.sqlite

All fixed and implemented