Bundling and PivotMDS layouts

I came across your paper "Graph Layouts by t-SNE” from 2017 and found it most interesting! I was also happy to see that you had shared your code on GitHub. I’ve played around with the code a little bit and have a couple of questions that I hope you can answer:

How did you achieve the edge bundling discussed in Sect. 4.7 and shown in some of the figures? Some post-processing of the saved graphs?
I’m not sure how one could construct a PivotMDS layout for a new graph.

Göran Falkman

Hi Göran, thanks for you interest! I hope the following helps.
For the edge bundling, I've used CUBu[1], but I'm not sure if the source code/application is public. I encourage you to contact the original authors listed below, they might be able to help.
I manually used Gephi to contruct and export the PivotMDS layouts from the graphs. Unfortunately, the PivotMDS phase of tsNET* is not incorperated into the graph layout pipeline of this repository, as it relies on the PivotMDS layouts.
[1]: Van der Zwan, Matthew, Valeriu Codreanu, and Alexandru Telea. "CUBu: Universal real-time bundling for large graphs." IEEE transactions on visualization and computer graphics 22.12 (2016): 2550-2563.

Hi Han,
Thank you for your prompt reply!
Regarding the PivotMDS layouts, I cannot find any Gephi plugin for PivotMDS. Could you please elaborate on how exactly you constructed these layouts using Gephi? Any help on how to do this would be most appreciated.
Best regards,
Göran
27 apr. 2018 kl. 10:46 skrev Han Kruiger <notifications<EMAIL_ADDRESS>Hi Göran, thanks for you interest! I hope the following helps.
For the edge bundling, I've used CUBu[1], but I'm not sure if the source code/application is public. I encourage you to contact the original authors listed below, they might be able to help.
I manually used Gephihttps://gephi.org/ to contruct and export the PivotMDS layouts from the graphs. Unfortunately, the PivotMDS phase of tsNET* is not incorperated into the graph layout pipeline of this repository, as it relies on the PivotMDS layouts.
[1]: Van der Zwan, Matthew, Valeriu Codreanu, and Alexandru Telea. "CUBu: Universal real-time bundling for large graphs." IEEE transactions on visualization and computer graphics 22.12 (2016): 2550-2563.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/HanKruiger/tsNET/issues/4#issuecomment-384907165, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AZIKid9jMnpouzBvHPGgCF8fyD5Wbbkfks5tstrogaJpZM4Tp9OI.

Hi Göran,
Apologies, I may have been remembering incorrectly. During the time of writing I used both Gephi and Tulip for making the various layouts. If there's no PivotMDS in Gephi, I'm pretty sure™ it's in Tulip.
Best,
Han


Using Linuxbrew with ARM processor

Hello there,
I got Linuxbrew installed, but brew install <formula> gives me:
Sorry, Homebrew does not support your computer's CPU architecture. For PPC support, see https://github.com/mistydemeo/tigerbrew.

uname -a gives me:
Linux Jolla <IP_ADDRESS>40612.1 #1 SMP PREEMPT Mon Jun 16 17:24:16 UTC 2014 armv71 armv71 armv71 GNU/Linux.

And cat /proc/cpuinfo:
Processor			ARMv7 Processor rev 4 (v71)
Processor			0

Is there anything I can do to get Linuxbrew working on my system? Thank you for your time.

Are there any news for support for armv7? Raspberry Pi 2 is available (armv7, 4 cores) and I thing this feature is a must

Being unaware of this issue, I opened https://github.com/Homebrew/linuxbrew/issues/260 24 days ago which was closed 19 days ago and it seems to be duplicate of this one.

I won't be adding ARM support myself, because I have no ARM hardware on which to test it. I will merge a pull request to add support for ARM to Linuxbrew provided that a couple people can vouch that it works.

Just out of interest, what changes would be needed to support ARM?

Homebrew (not Linuxbrew) supports PPC and Intel. Search Library/Homebrew for ppc and you'll probably find most of the locations that need to be changed. It's probably doable with some effort.

I've add ARM support to Linuxbrew for the Raspberry Pi. Happy hacking! I have a Raspberry Pi myself now.
See 2077229dfdcc32559c80349080d8baf345ef42b9


[SPARK-46906][SS] Add a check for stateful operator change for streaming

What changes were proposed in this pull request?

Currently user will get a misleading error as org.apache.spark.sql.execution.streaming.state.StateSchemaNotCompatible if restarting query in the same checkpoint location and changing their stateful operator. This PR catches such errors and throws a new error with informative message.
After physical planning, before execution phase, we will read from state metadata with the current operator id to fetch operator name of committed batch with the same operator id. If operator name does not match, throws the error.
Why are the changes needed?

The current error message is misleading to users. We should provide users with message that can guide them to the real root cause of error.
Does this PR introduce any user-facing change?

No
How was this patch tested?

Unit tests.
Was this patch authored or co-authored using generative AI tooling?

No

Thanks Jungtaek for your thorough code review!

@jingz-db Mind retriggering GA? You can either manually do this in your fork or simply push an empty commit to do this automatically. Thanks!


400: Bad Request

My HA is throwing "400: Bad Request" when connecting from a none Tailscale equipped device. Connecting from a device with Tailscale works fine using http
Some comments.

I have two HA in my network, both configured with tailscale, but only this one configured with Funnel.
This device is also configured for DuckDNS/NGINX, but I guess this has nothing to do with this setup
My Config file has this http entry:

http:
  use_x_forwarded_for: true
  trusted_proxies:
    - <IP_ADDRESS>/24

Something I noticed in the log file is "http://<IP_ADDRESS>:5000/Public_UPNP_gatedesc.xml". That is an very old Netgear router configured only as an access point and my HA is not routed through this device. As this is the only device on my network (except for my HA at <IP_ADDRESS>) I think it's worth noticing.

Log file below:
2023/08/09 00:38:32 portmapper: UPnP meta changed: {Location:http://<IP_ADDRESS>:5000/Public_UPNP_gatedesc.xml Server:Linux/2.6.12, UPnP/1.0, NETGEAR-UPNP/1.0 USN:uuid:c08bed9f-ca63-872c-35eb-849431d8e49a::urn:schemas-upnp-org:device:InternetGatewayDevice:1}
s6-rc: info: service init-nginx successfully started
s6-rc: info: service nginx: starting
2023/08/09 00:38:32 control: NetInfo: NetInfo{varies=false hairpin=true ipv6=false ipv6os=true udp=true icmpv4=false derp=#4 portmap=active-UM link=""}
2023/08/09 00:38:32 magicsock: endpoints changed: <IP_ADDRESS>:46062 (portmap), <IP_ADDRESS>:46062 (local), <IP_ADDRESS>:46062 (local), <IP_ADDRESS>:46062 (local)
2023/08/09 00:38:32 Switching ipn state NoState -> Starting (WantRunning=true, nm=true)
2023/08/09 00:38:32 magicsock: SetPrivateKey called (init)
2023/08/09 00:38:32 magicsock: private key changed, reconnecting to home derp-4
2023/08/09 00:38:32 wgengine: Reconfig: configuring userspace WireGuard config (with 1/2 peers)
2023/08/09 00:38:32 magicsock: adding connection to derp-4 for home-keep-alive
2023/08/09 00:38:32 magicsock: 1 active derp conns: derp-4=cr0s,wr0s
2023/08/09 00:38:32 wgengine: Reconfig: configuring router
2023/08/09 00:38:32 wgengine: Reconfig: configuring DNS
2023/08/09 00:38:32 dns: Set: {DefaultResolvers:[] Routes:{tailYYYY.ts.net.:[] ts.net.:[<IP_ADDRESS> 2620:111:8007::53]}+65arpa SearchDomains:[tailYYYY.ts.net.] Hosts:3}
2023/08/09 00:38:32 derphttp.Client.Connect: connecting to derp-4 (fra)
2023/08/09 00:38:32 peerapi: serving on http://<IP_ADDRESS>:43486
2023/08/09 00:38:32 health("dns"): error: getting OS base config is not supported
2023/08/09 00:38:32 health("dns-os"): error: getting OS base config is not supported
2023/08/09 00:38:32 peerapi: serving on http://[fd7a:115c:a1e0:ab12:4843:cd96:626f:fe63]:43486
2023/08/09 00:38:32 Switching ipn state Starting -> Running (WantRunning=true, nm=true)
[00:38:32] INFO: Starting NGinx...
2023/08/09 00:38:33 magicsock: derp-4 connected; connGen=1
s6-rc: info: service nginx successfully started
2023/08/09 00:38:34 wgengine: Reconfig: configuring userspace WireGuard config (with 1/10 peers)
[00:38:40] DEBUG: Requested API resource: http://supervisor/network/info
[00:38:40] DEBUG: Request method: GET
[00:38:40] DEBUG: Request data: {}
[00:38:40] DEBUG: API HTTP Response code: 200
[00:38:40] DEBUG: API Response: {"result": "ok", "data": {"interfaces": [{"interface": "wlan0", "type": "wireless", "enabled": false, "connected": false, "primary": false, "mac": "B8:27:EB:EF:40:97", "ipv4": {"method": "disabled", "address": [], "nameservers": [], "gateway": null, "ready": false}, "ipv6": {"method": "disabled", "address": [], "nameservers": [], "gateway": null, "ready": false}, "wifi": null, "vlan": null}, {"interface": "eth0", "type": "ethernet", "enabled": true, "connected": true, "primary": true, "mac": "B8:27:EB:BA:15:C2", "ipv4": {"method": "auto", "address": ["<IP_ADDRESS>/24"], "nameservers": ["<IP_ADDRESS>"], "gateway": "<IP_ADDRESS>", "ready": true}, "ipv6": {"method": "disabled", "address": ["fe80::4276:11cb:6a16:4a27/64"], "nameservers": [], "gateway": null, "ready": true}, "wifi": null, "vlan": null}], "docker": {"interface": "hassio", "address": "<IP_ADDRESS>/23", "gateway": "<IP_ADDRESS>", "dns": "<IP_ADDRESS>"}, "host_internet": true, "supervisor_internet": true}}
2023/08/09 00:38:40 wgengine: idle peer [wsJSV] now active, reconfiguring WireGuard
2023/08/09 00:38:40 wgengine: Reconfig: configuring userspace WireGuard config (with 2/10 peers)
2023/08/09 00:38:40 magicsock: disco: node [wsJSV] d:a4f4b648194b869e now using <IP_ADDRESS>:32466
2023/08/09 00:38:40 Accept: TCP{<IP_ADDRESS>:53384 > <IP_ADDRESS>:8123} 65 tcp non-syn
2023/08/09 00:38:40 Accept: TCP{<IP_ADDRESS>:53409 > <IP_ADDRESS>:8123} 64 tcp ok
2023/08/09 00:38:40 [unexpected] localbackend: got TCP conn without TCP config for port 8123; from <IP_ADDRESS>:53409
2023/08/09 00:38:41 Accept: TCP{<IP_ADDRESS>:53409 > <IP_ADDRESS>:8123} 52 tcp non-syn
[00:38:41] DEBUG: Requested API resource: http://supervisor/network/interface/wlan0/info
[00:38:41] DEBUG: Request method: GET
[00:38:41] DEBUG: Request data: {}
[00:38:41] DEBUG: API HTTP Response code: 200
[00:38:42] DEBUG: API Response: {"result": "ok", "data": {"interface": "wlan0", "type": "wireless", "enabled": false, "connected": false, "primary": false, "mac": "B8:27:EB:EF:40:97", "ipv4": {"method": "disabled", "address": [], "nameservers": [], "gateway": null, "ready": false}, "ipv6": {"method": "disabled", "address": [], "nameservers": [], "gateway": null, "ready": false}, "wifi": null, "vlan": null}}
[00:38:43] DEBUG: Requested API resource: http://supervisor/network/interface/eth0/info
[00:38:43] DEBUG: Request method: GET
[00:38:43] DEBUG: Request data: {}
[00:38:43] DEBUG: API HTTP Response code: 200
[00:38:44] DEBUG: API Response: {"result": "ok", "data": {"interface": "eth0", "type": "ethernet", "enabled": true, "connected": true, "primary": true, "mac": "B8:27:EB:BA:15:C2", "ipv4": {"method": "auto", "address": ["<IP_ADDRESS>/24"], "nameservers": ["<IP_ADDRESS>"], "gateway": "<IP_ADDRESS>", "ready": true}, "ipv6": {"method": "disabled", "address": ["fe80::4276:11cb:6a16:4a27/64"], "nameservers": [], "gateway": null, "ready": true}, "wifi": null, "vlan": null}}
[00:38:46] INFO: Tailscale is running
[00:38:47] WARNING: Currently the following subnets are both present as local subnets
[00:38:47] WARNING: and are also routed within your tailnet to other nodes!
[00:38:47] WARNING: Please reconfigure your subnet routing within your tailnet
[00:38:47] WARNING: to prevent current or future collisions.
[00:38:47] WARNING:   <IP_ADDRESS>/24
s6-rc: info: service post-tailscaled successfully started
s6-rc: info: service proxy: starting
s6-rc: info: service taildrop: starting
s6-rc: info: service taildrop successfully started
[00:38:49] DEBUG: Requested API resource: http://supervisor/core/info
[00:38:49] DEBUG: Request method: GET
[00:38:49] DEBUG: Request data: {}
[00:38:49] DEBUG: API HTTP Response code: 200
[00:38:49] DEBUG: API Response: {"result": "ok", "data": {"version": "2023.8.1", "version_latest": "2023.8.1", "update_available": false, "machine": "raspberrypi3-64", "ip_address": "<IP_ADDRESS>", "arch": "aarch64", "image": "ghcr.io/home-assistant/raspberrypi3-64-homeassistant", "boot": true, "port": 8123, "ssl": false, "watchdog": true, "audio_input": null, "audio_output": null}}
2023/08/09 00:38:50 serve: closing idle connections to http://<IP_ADDRESS>:8123
2023/08/09 00:38:50 Hostinfo.WireIngress changed to false
2023/08/09 00:38:51 serve: creating a new proxy handler for http://<IP_ADDRESS>:8123
2023/08/09 00:38:51 wgengine: Reconfig: configuring userspace WireGuard config (with 2/2 peers)
[00:38:51] INFO: Tailscale Proxy is enabled:
[00:38:51] INFO:   Your Home Assistant instance is available within your Tailnet VPN at
[00:38:51] INFO:   https://XXXX.tailYYYY.ts.net
s6-rc: info: service proxy successfully started
s6-rc: info: service funnel: starting
2023/08/09 00:38:53 Hostinfo.WireIngress changed to true
[00:38:53] INFO: Tailscale Funnel is enabled:
[00:38:53] INFO:   Your Home Assistant instance is publicly available on the internet at
[00:38:53] INFO:   https://XXXX.tailYYYY.ts.net
s6-rc: info: service funnel successfully started
s6-rc: info: service legacy-services: starting
s6-rc: info: service legacy-services successfully started
2023/08/09 00:38:53 wgengine: Reconfig: configuring userspace WireGuard config (with 2/10 peers)
2023/08/09 00:39:37 Accept: TCP{<IP_ADDRESS>:53409 > <IP_ADDRESS>:8123} 52 tcp non-syn
2023/08/09 00:39:37 Accept: TCP{<IP_ADDRESS>:53409 > <IP_ADDRESS>:8123} 58 tcp non-syn
2023/08/09 00:39:50 Accept: TCP{<IP_ADDRESS>:53409 > <IP_ADDRESS>:8123} 52 tcp non-syn
2023/08/09 00:39:50 Accept: TCP{<IP_ADDRESS>:53409 > <IP_ADDRESS>:8123} 66 tcp non-syn
2023/08/09 00:39:56 [unexpected] localbackend: got TCP conn without TCP config for port 8123; from <IP_ADDRESS>:53411
2023/08/09 00:39:56 [unexpected] localbackend: got TCP conn without TCP config for port 8123; from <IP_ADDRESS>:53412
2023/08/09 00:39:56 [unexpected] localbackend: got TCP conn without TCP config for port 8123; from <IP_ADDRESS>:53413
2023/08/09 00:39:58 Accept: TCP{<IP_ADDRESS>:53411 > <IP_ADDRESS>:8123} 52 tcp non-syn
2023/08/09 00:40:41 wgengine: idle peer [8EeRI] now active, reconfiguring WireGuard
2023/08/09 00:40:41 wgengine: Reconfig: configuring userspace WireGuard config (with 3/10 peers)
2023/08/09 00:40:41 magicsock: disco: node [8EeRI] d:770110597853e96d now using <IP_ADDRESS>:41651
2023/08/09 00:40:41 Drop: TCP{[fd7a:115c:a1e0:ab12:4843:cd96:6249:ba61]:49386 > [fd7a:115c:a1e0:ab12:4843:cd96:626f:fe63]:43486} 80 no rules matched
2023/08/09 00:40:41 Drop: TCP{[fd7a:115c:a1e0:ab12:4843:cd96:6249:ba61]:49402 > [fd7a:115c:a1e0:ab12:4843:cd96:626f:fe63]:43486} 80 no rules matched
2023/08/09 00:40:41 Accept: TCP{[fd7a:115c:a1e0:ab12:4843:cd96:6249:ba61]:49386 > [fd7a:115c:a1e0:ab12:4843:cd96:626f:fe63]:43486} 72 tcp non-syn
2023/08/09 00:40:41 Accept: TCP{[fd7a:115c:a1e0:ab12:4843:cd96:6249:ba61]:49402 > [fd7a:115c:a1e0:ab12:4843:cd96:626f:fe63]:43486} 72 tcp non-syn
2023/08/09 00:40:41 Accept: TCP{[fd7a:115c:a1e0:ab12:4843:cd96:6249:ba61]:49402 > [fd7a:115c:a1e0:ab12:4843:cd96:626f:fe63]:43486} 315 tcp non-syn
2023/08/09 00:40:41 [RATELIMIT] format("%s: %s %d %s\n%s")
2023/08/09 00:40:57 Accept: TCP{[fd7a:115c:a1e0:ab12:4843:cd96:6249:ba61]:49386 > [fd7a:115c:a1e0:ab12:4843:cd96:626f:fe63]:43486} 72 tcp non-syn

Please add <IP_ADDRESS> to trusted proxies (as noted in the Documentation), because Tailscale is running on the host network, not like NGINX on the docker network.
Note: This is an intentional Tailscale limitation that it uses <IP_ADDRESS>, "Note that only http://<IP_ADDRESS> is currently supported for proxies." https://tailscale.com/kb/1242/tailscale-serve/
  trusted_proxies:
    - <IP_ADDRESS>/24
    - <IP_ADDRESS>

On the Netgear issue: I think Tailscale tries to find any route toward the internet with any means.

Important:
[00:38:47] WARNING: Currently the following subnets are both present as local subnets
[00:38:47] WARNING: and are also routed within your tailnet to other nodes!
[00:38:47] WARNING: Please reconfigure your subnet routing within your tailnet
[00:38:47] WARNING: to prevent current or future collisions.
[00:38:47] WARNING: <IP_ADDRESS>/24

There is a protection in this add-on to prevent this collision, but without this, when you enable the subnet routing on the other site, this site would route all the traffic toward the other site and your local HA would lose ALL network access, would get soft bricked! Yes, it is typical to use <IP_ADDRESS>/24 or <IP_ADDRESS>/24 on multiple LAN-s, but Tailscale assumes they are on the same LAN and this is usually not true, and a simple click (enabling subnet routing on the Tailscale admin page) can mess up your networking completely.

Thanks, now works like a charm.
I tried to understand the "Important:" above but didn't totally grab it. I only have one network that should be known by tailscale and that is <IP_ADDRESS>/24
I did see that there was another issue related to the same "400: Bad Request" with the solution to set <IP_ADDRESS> as the trusted proxy but as I didn't find it in the documentation I thought it was not relevant. Are you sure this is in the documentation for HA. I looked at the latest documentation where there was some updates for Funnel but I didn't find the information about the trusted proxy but I might have miseed something
I could see that this is on the way to be released in the official repro, that would be great
Thanks for the help and all the work you are doing, this will be a great improvement to HA when finally released. Now my Internet Provider can NAT and hide my router anyway they want, I will still be able to give access to my family members without them to install the Tailscale app and register an account

Ah, I see, this <IP_ADDRESS> thing is in the proxy documentation, but funnel uses the proxy. I will add a note to the funnel docs to read the proxy docs also. It was trivial for me, but not trivial for a first time reader, thank you for the reply! And I will try to add some detection for this misconfiguration.

On the "Important" thing: there are at least 2 Tailscale devices (add-on or real Tailscale installation) in your tailnet network that uses the same local <IP_ADDRESS>/24 LAN network, and the add-on automatically advertises these as possible subnet routes. Subnet: you can access non-tailscale-installed devices on the advertised subnet through the tailscale-installed device routing the traffic. Advertising doesn't automatically enable the routing, but it seems you have enabled on at least one of the other devices (not this add-on that we are talking about now) this routing (see https://login.tailscale.com/admin/machines), so you can access that subnet's devices from any tailscale-installed device (like this add-on's device) easily with a ping 192.168.0.x. But this add-on's local LAN also uses a <IP_ADDRESS>/24 network, so all the traffic, even your local HA's traffic on 192.168.0.x will go to the other devices LAN, a total mess. Tailscale assumes they are load-balancing or failsafe nodes on the same physical LAN, but they are usually just misconfiguration.
Enter this into a cli (do not copy-paste the output here, just see it):
docker exec -it addon_09716aab_tailscale /bin/bash
/opt/tailscale status --json --peers=true --self=false | jq '.Peer[] | select(has("PrimaryRoutes"))'

You will get at least one result, a device that is not this add-on's LAN, but has an enabled <IP_ADDRESS>/24 subnet routing.
Enter this:
{ ip -4 rule list; ip -6 rule list; }

There will be lines starting with "5000" like:
5000:   from all to <IP_ADDRESS>/24 lookup main

These lines prevent tailscale to route this add-on's devices's ALL network trafic to the other device's network, making it de facto unreacable.

Yeah, my forked docs contain an extra "check logs again" step, now I made a PR for the official add-on also: https://github.com/hassio-addons/addon-tailscale/pull/242 I don't want to mention proxy explicitly, if somebody is a fresh new Tailscale user, HTTPS won't be set, and if it is already set, there will be warning in the log about the situation. Other services are also starting after the login, so better to be not too specific, core developers don't like that in my experience.
And I made a reference from the funnel docs to the proxy doc also.
And I've tried to add some proxy config check to the scripts, but a simple curl fails on userspace-networking devices, after I figure out this problem, there will be a warning about this trusted proxies issue also.

And the proxy config check is released also, closing this issue now.

Thanks for this great addon supercharge! Definitely add this to your DOC.md (Something like "Note: <IP_ADDRESS> must be one of your trusted_proxies in your home assistant config file for https/proxy to work, otherwise you will see a 400:Bad Request error when trying to access home assistant").
Just to understand are their any serious security risks of adding this to the trusted proxy list?

Oh, and the security issue: I'm really not an expert, as I understand, this will make accessible the unencrypted plain HTTP web UI of HA for proxies not only on the <IP_ADDRESS>/24 internal docker add-on network (used by eg. the NGINX proxy) but on the localhost also. I think this is at least not much worst than without this extra config line. And this is a Tailscale requirement, so we can't do anything about it. :/

That should help.
Been using the proxy/https features and they work great.

And finally even myself run into this 400: Bad Request error... :D
I fixed reverse proxy config detection: diff
New release is out.


Fix form fields ax-load issue on spa-mode

[x] Changes have been thoroughly tested to not break existing functionality.
[ ] New functionality has been documented or existing documentation has been updated to reflect changes.
[x] Visual changes are explained in the PR description using a screenshot/recording of before and after.

As per #9151 fixes the table ax-load issue on spa mode, the same issue also happened in some form fields.
This PR will fix it.
https://github.com/filamentphp/filament/assets/46495960/acc6b039-3aaa-47a2-8e50-4abf1cf7f671

DateTimePicker still has the issue with the displayText etc. I'm working on it

Thanks for working on this, @akunbeben!
Could you mark this PR as ready for review when you've implemented all pending changes?

Thanks for working on this, @akunbeben! Could you mark this PR as ready for review when you've implemented all pending changes?

Yes, I will.
I'll continue to work on it later today

Any news here?

DateTimePicker still has the issue with the displayText etc. I'm working on it

Sorry for the delay. After a while, I finally recognized that the problem was when we async load the component, it is not really asynchronous because the livewire.js expects the props in the first place.
Simply "wire:ignore" along with ax-load="visible" solves the problem.
Manually tested.

Please revert all unnecessary changes where you are moving large code blocks like this
New imports can be added at the top of the existing code blocks, they don't need to be split

Changing it, Sorry

The problems of Date and Time pickers have not been fixed.

wire:ignore would break dynamic min/max dates and disabled dates


merge package from arlac77/npm-package-template

package.json

chore(package<EMAIL_ADDRESS>chore(scripts): cover@#overwrite c8 --temp-directory build/coverage ava && c8 report -r lcov --temp-directory build/coverage
chore(package): add nyc from template
chore(package): set $.ava.require='esm' as in template
chore(package): set $.ava.files='tests/-test.js,tests/-test.mjs' as in template
chore(package): set $.ava.extensions='js,mjs' as in template

Coverage decreased (-6.1%) to 39.604% when pulling ad94fb9588ac54ecf1a90b6b316d9a9b501f1265 on template-sync-1 into fb22398b6e123e0bd348f387ea855d7174c48071 on master.

:tada: This PR is included in version 8.1.29 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


update iot end of property result

@ahsonkhan

Sweet, docs validation in action!

D:/a/1/s/sdk/inc/azure/iot/az_iot_common.h:166: warning: explicit link request to 'AZ_ERROR_IOT_END_OF_PROPERTIES' could not be resolved
D:\a_temp\725da464-726f-40ef-9994-85bc47c64317.ps1 : Warnings from the doxygen docs generation step are treated as error.

https://dev.azure.com/azure-sdk/public/_build/results?buildId=514538&view=logs&j=a129effc-2dd1-54d1-fb5a-ad7bdc0e851d&t=22be136e-4813-5a04-5aa2-6a647ac29f4d


Hw1

Did I jsut made a pull request to push my code in to the main branch of the class?  I think I made a mistake, I mean to push it on my branch.  Please ignore the pull request

Made by mistake. Closing.


Teslafi import PARTIALLY succeeds... How to debug remainder?

I have Teslafi data that starts in 06-2017.  I've downloaded the teslafi csv files, and started into import process.  It sorta worked.  It did process everything UP UNTIL 03-07-2018.  The next information appears to be 11-17-2019 when I first started logged with Teslamate.  None of the files appear to add any information to the teslamate database - They say starting to import, then complete, but no drives/charging/etc added.
I'd love to get the remainder of the data in.  There are trips I'd like to have recorded in the visits dashboard, and I'd LOVE to see if my projected range has declined steadily or if there is a drop-off somewhere... (see attached)
Any suggestions on how I can debug this further and hopefully get the remainder of the data imported?
Is there an Environment variable to increase the logging detail?
Ubuntu host machine, using the simple internal docker-compose.yaml to bring the system online.
Thanks!

Any suggestions on how I can debug this further and hopefully get the remainder of the data imported?

Have you checked the relevant CSV files? It is possible that something went wrong with the export.
Try to import the files into a fresh TeslaMate installation to see if this behavior is reproducible and to get the logs of that import.
Alternatively, you can send me the relevant files so I can debug this locally.

Fresh install, Bombs out in March 2018 as per the original install.  Logs attached.
Sending the March 2018 teslafi file via email.
log.txt.gz

Thanks. With the error message, fixing it was fairly straightforward. I'll release a new version with the fix soon.

Thank YOU!  Hope that takes care of the issue!

Continuing on this - That does fix this issue in a blank database.  Unfortunately, I've got several months of data that is exclusive to Teslamate.  Trying to start the import again, from the problematic 3/19 teslafi file doesn't allow me to pick it up and go.
Can we drop data from the Postgres database that is older than a specific date and allow me to import again?  I've got plenty of backups, but the original import was when the feature debuted, and I've got data after that backup, obviously.
Thank you!

Yes, I would also suggest dropping the imported data. Delete everything before a certain date from the following tables and then import again:

charging_processes
drives
positions
states
updates

That worked.  Documenting in case someone has the same or similar issue.  It would also be good in case an Import failed for whatever reason, so you can start over.
delete from charging_processes where start_date < '2019-01-01';
delete from drives where start_date < '2019-01-01';
delete from states where start_date < '2019-01-01';
delete from updates where start_date < '2019-01-01';
delete from positions where date < '2019-01-01';
I had a position and charging_process foreign key issue, but it was obviously from the failed import.  Removed the locked rows in both tables and everything imported in without an issue.
Thanks very much for your help.

Just wanted to add to this, that when running the delete from charging_process query, matching on end_date instead of start_date will purge all rows used by the following queries without getting foreign key issues:
delete from charging_processes where end_date < '2020-04-01';
delete from drives where start_date < '2020-04-01';
delete from states where start_date < '2020-04-01';
delete from updates where start_date < '2020-04-01';
delete from positions where date < '2020-04-01';

Sorry to reopen this but I appear to have the same issue.  I have imported a couple of years of TeslaFi data but have a gap in February, March, April and May 2020.
I had some failed imports and retried a few times.
Can anyone give idiot-proof instructions on how to clear old data from the db?  I am OK with Docker but not very knowledgeable on db admin commands.  I still have TeslaFi running and have done all the time so I can happily trash all of the data in TeslaMate db and re-import if that's easier.
I tried opening the console for the postgres container and then entering "delete from charging_processes where end_date < '2020-01-06';" but go the following error:  "bash: 2020-01-06: No such file or directory".
I am fairly sure it's me doing it all wrong.  Perhaps I should be entering the commands at a normal console connected to my Ubuntu host...?
Any help before I trash TeslaMate and all associated containers and start again?

You're just missing the part where you connect to pgsql before executing the queries,
see the below copypasta from my teslamate notes: :)
##########################################################################################
enter pgsql shell:
docker-compose exec database psql teslamate teslamate
##########################################################################################
Delete teslamate data before a given date:
delete from charging_processes where start_date < '2020-04-01';
delete from charging_processes where end_date < '2020-04-01';
delete from drives where start_date < '2020-04-01';
delete from states where start_date < '2020-04-01';
delete from updates where start_date < '2020-04-01';
delete from positions where date < '2020-04-01';
delete from charging_processes where start_date < '2020-04-19';
delete from charging_processes where end_date < '2020-04-19';
delete from drives where start_date < '2020-04-19';
delete from states where start_date < '2020-04-19';
delete from updates where start_date < '2020-04-19';
delete from positions where date < '2020-04-19';
##########################################################################################
list all charging processes, inc position id:
select start_date,end_date,position_id from charging_processes;
##########################################################################################

Thanks for the pointers but I am still completely lost.
I think it may be time to just scrap this and try again.

Yep, I ran out of skill so baled and dumped all containers, volumes etc and pulled everything anew.
I imported all the same csv files and this time is worked perfectly with no gaps in the history.
I am still confused about why I hit this bug because it appeared to be fixed long before I installed TeslaMate but nevermind.   All's well that ends well:


Revert "Changing #warning to #pragma message. (#89)"

We've had a couple releases as a message. It's time for this to become a warning.
Reverts RadeonOpenCompute/rocm-cmake#89.

I created a ticket to track the unrelated test failures. Since this is just a reversion to a previous state, I'm going to go ahead and merge. We don't want to leave this change until the last minute.


Update package.json

Hi why did you close this.

@paladox npm automatically will install that version.
http://semver.npmjs.com/


How can I generate a new CDS file after writing adding a few more smart contracts?

I added a few more functions into the pre-existing chaincode (in go). Now I want to test them, so how should I package my chaincode into a CDS package. What STEPS should I follow?
I am working on a project and my submission is due in 1 day, can you help as soon as possible

Hi @yashverma9
I'm also looking for the same. Please let me know if you got to know how to package and instantiate the chaincode.

Hey, it's pretty easy. Just install the IBM Blockchain platform extension in VS Code. In the command pallete (open from view tab in vs code) use the package open project command. This will create a new cds file. More details here:
https://github.com/IBM-Blockchain/blockchain-vscode-extension#package-open-project


Fixed #33464 -- Resolved output_field for combined numeric expressions with MOD operator.

ticket-33464
I'm unsure about the second commit, if it makes sense to define as default FloatField + DecimalField => DecimalField.
I'd say that one wants to keep the decimal precision by default, like when doing plain Python arithmetic with a Decimal.

@David-Wobrock Thanks :+1: I think we should drop the second commit as we will lose precision anyway and users should be aware of that, e.g:
SQL> SELECT MOD(4.6, TO_BINARY_FLOAT(2.5)) FROM DUAL;

MOD(4.6,TO_BINARY_FLOAT(2.5))
-----------------------------
		     2.1E+000

SQL> SELECT CAST(MOD(4.6, TO_BINARY_FLOAT(2.5)) AS NUMBER) FROM DUAL;

CAST(MOD(4.6,TO_BINARY_FLOAT(2.5))ASNUMBER)
-------------------------------------------
				  2.0999999

SQL> SELECT MOD(4.6, 2.5) FROM DUAL;

MOD(4.6,2.5)
------------
	 2.1

Ah yes @felixxm , that's the caveat I missed. I removed the second commit, thanks 🙏

@David-Wobrock Thanks :+1:


Use vector drawables instead of PNGs

There are a lot of PNGs being used in the code. Replace them with equivalent xml drawable files
Reference
https://sendeyo.com/onlineconverter/en/image-png/xml

@Swati4star  I'd like to work on this.

Few pngs are still there...

I'm working on this tomorrow

Hi Rita, you can start working on issues 1 March 2019 as coding phase for GSSoC starts from 1 March 2019.

Alright thank you for the information

Hey! Can I start working on this issue?

sure @lifeLessCoder

okay

I'm not able to convert pngs to XML using the website mentioned above. Can I use
Icons from flaticon to do so?
Reference
https://www.flaticon.com

if you see the code, we now dont have flags images in the drawable folder.
You can convert other images to vector drawables

okay!

Done! @Swati4star

Trackign in #711


RFE: better support for patching setup.cfg files

commonly when openstack python packages are tagged upstream the setup.cfg file is re-written and whitespace normalization is done for the version of the setup.cfg that is in the tarball vs what is in the branch.
this causes most attempts to patch setup.cfg to fail when trying to build with that patch in the %prep section
It would be nice if rdopkg could at a minimum detect failure to apply patch to tarball downloaded.
for bonus points gracefully handling the simple tabs vs spaces and trailing space at end of line after an = cleanly.

This is related to #110


ProjectReference to interop project causes build error

I have a C# app which has a project reference to an interop project. This causes the following build error:
3>C:\Program Files\dotnet\sdk\5.0.100\Sdks\Microsoft.NET.Sdk\targets\Microsoft.NET.Sdk.targets(934,5): error NETSDK1130: Referencing a Windows Metadata component directly when targeting .NETCoreApp,Version=v5.0 is not supported. Use the C#/WinRT projection tool (https://aka.ms/cswinrt) or a provided projection for this target.
3>Done building project "WinUIClassLibrary.csproj" -- FAILED.
Adding nuget references to Microsoft.Windows.CsWinRT fixes the issue, but I wouldn't expect that I need to do that, since I'm just referencing a .NET5 project.
Repro project: CS-Desktop2.zip
/cc @angelazhangmsft

And since pictures are worth a 1000 words, here is the project configuration:

The issue is with the RuntimeComponent1.Interop project publishing out its winmd file to the referencing project.  We have an issue tracking that somewhere for nugetized components (props and targets sensing the referencing target and publishing out either native dll/winmd OR managed interop dll).  But in a direct project reference scenario, you'd need to take care of that yourself.  Adding the cswinrt nuget reference provides the convenience of disabling all winmd references (itself a workaround to prevent NETSDK1130 errors)

This is yet another example of why the current implementation of NETSDK1130 enforcement (via _BlockWinMDsOnUnsupportedTFMs) should be reconsidered - too many false positives.
See also:
New winmd reference enforcement takes down unit test host

New winmd reference enforcement targets wrong items
Compilation fails with NETSDK1130 error, WITHOUT directly referencing a winmd

closing, as not a cswinrt issue


The connection count on Azure Portal is Incorrect

I just use 2 clients locally for testing, started and stopped them multiple times, but the portal logged the connection number as around 55 which is definitely incorrect.

Since the count number is incorrect, it will cause issues with the costing

Where did you see the connection count number, in overall page or in metrics(preview) page. If in metrics page, you need to make sure Time granularity = 1 minute. It's just a bug of showing metrics and the background statistics is accurate.

I saw that on the overall page.

Also, it's having issues on the metrics page, if I chose the default granularity, it goes above 1k+, even if I chose granularity as 1 minute, it still shows around 55.

Synced with your team offline, I think this issue can be closed now


Doesn't wait for OSK to finish

The On-Screen Keyboard (OSK.EXE) is launched, but the "Process Finished" message appears immediately. It seems that the proc.hProcess value is incorrect. I checked the process ID value of proc.dwProcessID against the PID listed for OSK in Task Manager, and they don't match. Indeed, proc.dwProcessID isn't listed for any process (even in Process Explorer)., so it seems that the PROCESS_INFORMATION structure is not receiving correct outputs. Everything works fine for NOTEPAD and CALC though. Equivilent code compiled in VB.NET  behaves properly with OSK! What's different about VBA that causes CreateProcessA to work incorrectly with OSK?

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: d106b8c8-ffc7-3212-3b72-5a25881a318c
Version Independent ID: 68f75ed0-8f51-2989-3261-0a3b36f7b030
Content: Determine when a shelled process ends
Content Source: access/Concepts/Windows-API/determine-when-a-shelled-process-ends.md
Product: access
GitHub Login: @o365devx
Microsoft Alias: o365devx

@JAH72 Thanks for your feedback. We use Github issues for documentation bugs, not for developer support. Please try the VBA developer community on Stack Overflow (https://stackoverflow.com/questions/tagged/vba) where you can get help from actual developers. If you find a bug in our documentation, please let us know. Thanks!


cannot import name 'Conf' from partially initialized module 'neural_compressor.conf.config'

When I try to import the installed optimum.intel I am getting this error:
import optimum.intel.neural_compressor

Error:
---------------------------------------------------------------------------
ImportError                               Traceback (most recent call last)
Input In [7], in <cell line: 1>()
----> 1 import optimum.intel.neural_compressor

File /usr/local/lib/python3.8/dist-packages/optimum/intel/__init__.py:15, in <module>
      1 #  Copyright 2022 The HuggingFace Team. All rights reserved.
      2 #
      3 #  Licensed under the Apache License, Version 2.0 (the "License");
   (...)
     12 #  See the License for the specific language governing permissions and
     13 #  limitations under the License.
---> 15 from .neural_compressor.configuration import IncConfig, IncPruningConfig, IncQuantizationConfig
     16 from .neural_compressor.optimization import IncOptimizer
     17 from .neural_compressor.pruning import IncPruner, IncPruningMode

File /usr/local/lib/python3.8/dist-packages/optimum/intel/neural_compressor/__init__.py:15, in <module>
      1 #  Copyright 2022 The HuggingFace Team. All rights reserved.
      2 #
      3 #  Licensed under the Apache License, Version 2.0 (the "License");
   (...)
     12 #  See the License for the specific language governing permissions and
     13 #  limitations under the License.
---> 15 from .configuration import IncConfig, IncDistillationConfig, IncPruningConfig, IncQuantizationConfig
     16 from .distillation import IncDistiller
     17 from .optimization import IncOptimizer

File /usr/local/lib/python3.8/dist-packages/optimum/intel/neural_compressor/configuration.py:23, in <module>
     20 from transformers.file_utils import cached_path, hf_bucket_url
     22 import yaml
---> 23 from neural_compressor.conf.config import Conf, Distillation_Conf, Pruning_Conf, Quantization_Conf
     24 from optimum.intel.neural_compressor.utils import CONFIG_NAME
     27 logger = logging.getLogger(__name__)

File /usr/local/lib/python3.8/dist-packages/neural_compressor/conf/config.py:20, in <module>
     18 import yaml
     19 from schema import Schema, And, Use, Optional, Or, Hook
---> 20 from ..adaptor import FRAMEWORKS
     21 from ..strategy import STRATEGIES
     22 from ..objective import OBJECTIVES

File /usr/local/lib/python3.8/dist-packages/neural_compressor/__init__.py:18, in <module>
      1 #!/usr/bin/env python
      2 # -*- coding: utf-8 -*-
      3 #
   (...)
     15 # See the License for the specific language governing permissions and
     16 # limitations under the License.
---> 18 from .quantization import Quantization
     19 from .pruning import Pruning
     20 from .benchmark import Benchmark

File /usr/local/lib/python3.8/dist-packages/neural_compressor/quantization.py:20, in <module>
     18 import os
     19 from .utils import logger
---> 20 from .data import DATALOADERS, DATASETS
     21 from .experimental import Quantization as ExpQuantization
     23 class Quantization(object):

File /usr/local/lib/python3.8/dist-packages/neural_compressor/data/__init__.py:19, in <module>
      1 #!/usr/bin/env python
      2 # -*- coding: utf-8 -*-
      3 #
   (...)
     15 # See the License for the specific language governing permissions and
     16 # limitations under the License.
---> 19 from .dataloaders import DataLoader
     20 import neural_compressor.data.datasets
     21 import neural_compressor.data.transforms

File /usr/local/lib/python3.8/dist-packages/neural_compressor/data/dataloaders/__init__.py:18, in <module>
      1 #!/usr/bin/env python
      2 # -*- coding: utf-8 -*-
      3 #
   (...)
     15 # See the License for the specific language governing permissions and
     16 # limitations under the License.
---> 18 from .dataloader import DataLoader
     20 __all__ = [
     21     "DataLoader",
     22 ]

File /usr/local/lib/python3.8/dist-packages/neural_compressor/data/dataloaders/dataloader.py:18, in <module>
      1 #!/usr/bin/env python
      2 # -*- coding: utf-8 -*-
      3 #
   (...)
     15 # See the License for the specific language governing permissions and
     16 # limitations under the License.
---> 18 from neural_compressor.experimental.data.dataloaders import DATALOADERS
     20 # THIS API IS TO BE DEPRECATED!
     21 class DataLoader(object):

File /usr/local/lib/python3.8/dist-packages/neural_compressor/experimental/__init__.py:18, in <module>
      1 #!/usr/bin/env python
      2 # -*- coding: utf-8 -*-
      3 #
   (...)
     15 # See the License for the specific language governing permissions and
     16 # limitations under the License.
---> 18 from .component import Component
     19 from .quantization import Quantization
     20 from .pruning import Pruning

File /usr/local/lib/python3.8/dist-packages/neural_compressor/experimental/component.py:17, in <module>
      1 #!/usr/bin/env python
      2 # -*- coding: utf-8 -*-
      3 #
   (...)
     15 # See the License for the specific language governing permissions and
     16 # limitations under the License.
---> 17 from ..conf.config import Conf
     18 from ..utils import logger
     19 from ..utils.utility import set_backend

ImportError: cannot import name 'Conf' from partially initialized module 'neural_compressor.conf.config' (most likely due to a circular import) (/usr/local/lib/python3.8/dist-packages/neural_compressor/conf/config.py)

I would appreciate any help here.

I can success import it, here is my env.
(optimum) [changwa1@mlt2-clx011 ~]$ python
Python 3.8.13 (default, Mar 28 2022, 11:38:47)
[GCC 7.5.0] :: Anaconda, Inc. on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import optimum.intel.neural_compressor
>>>
[2]+  Stopped                 python
(optimum) [changwa1@mlt2-clx011 ~]$ pip list|grep torch
torch                1.12.1+cpu
torchaudio           0.12.1+cpu
torchvision          0.13.1+cpu
(optimum) [changwa1@mlt2-clx011 ~]$ pip list|grep neural
neural-compressor    1.13.1
(optimum) [changwa1@mlt2-clx011 ~]$ pip list|grep optimum
optimum              1.3.0
optimum-intel        1.3.0.dev0   /home/changwa1/optimum-intel


Upgrade to Spring Cloud Finchley M9

Coverage decreased (-0.06%) to 88.792% when pulling 34ad20ba0722c3c807ee1fbeff7a22772340c3a9 on tgianos:finchleyM9 into ce35302bc31ac1e5d0ed61d09f09b5725065e46b on Netflix:master.


xrdp: constify input event type

+1
On Fri, Sep 29, 2017 at 12:22 PM metalefty<EMAIL_ADDRESS>wrote:

You can view, comment on, or merge this pull request online at:
https://github.com/neutrinolabs/xrdp/pull/896
Commit Summary

xrdp: constify input event type

File Changes

M common/xrdp_constants.h
https://github.com/neutrinolabs/xrdp/pull/896/files#diff-0 (1)
M xrdp/xrdp_wm.c
https://github.com/neutrinolabs/xrdp/pull/896/files#diff-1 (10)

Patch Links:

https://github.com/neutrinolabs/xrdp/pull/896.patch
https://github.com/neutrinolabs/xrdp/pull/896.diff

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/neutrinolabs/xrdp/pull/896, or mute the thread
https://github.com/notifications/unsubscribe-auth/ADTH1HR3vZUFy9dHJf7LGrfUiD1NPidAks5snH6GgaJpZM4PoNbD
.

--
Idan Freiberg
PGP FP: 8108 7EC9 806E 4980 75F2  72B3 8AD3 2D04 337B 1F18


Use retries when building docker image

Summary

Failing to download kubectl was causing CI failures.
This adds a retry mechanism when building docker image

Test Plan
Ran build script

@bors-libra r+
Looks good.

:pushpin: Commit c8e46b8 has been approved by sausagee

@bors-libra r=sausagee

:bulb: This pull request was already approved, no need to approve it again.

:pushpin: Commit c8e46b8 has been approved by sausagee

:hourglass: Testing commit c8e46b8514a66b5c54e744ca96e0ebc172dbf32b with merge<PHONE_NUMBER>0cb24d5554998434b39e4e9be0e035...

:broken_heart: Test failed - checks-actions_land_blocking_test

@bors-libra r=sausagee

:pushpin: Commit 92be561 has been approved by sausagee

:hourglass: Testing commit 92be56178c558864347623b2c7b74c08686ef282 with merge b58e50e892489603d4e1a44de01c1725ea2a7082...

@ankushagarwal heads up, there is git linter issue in https://circleci.com/gh/libra/libra/63708 (same in https://circleci.com/gh/libra/libra/63705)
Run ./scripts/changed-files.sh to repro locally.

:broken_heart: Test failed - checks-circle_commit_workflow

@bors-libra r=sausagee

:pushpin: Commit 65d5ab9 has been approved by sausagee

:hourglass: Testing commit 65d5ab96ef6380e27c5a8522774fd4795608e581 with merge 6c7f7999ae553b7717829ad0bc98d599be2cd2f8...

:broken_heart: Test failed - checks-circle_commit_workflow

@bors-libra r=sausagee

:pushpin: Commit 78d38b4 has been approved by sausagee

:hourglass: Testing commit 78d38b4ab8474fc434c52cea33d9598a596183b2 with merge 7ea0db0984e97c34c9ff3b55bc5b746923d9897c...

:sunny: Test successful - checks-actions_land_blocking_test, checks-circle_commit_workflow
Approved by: sausagee
Pushing 7ea0db0984e97c34c9ff3b55bc5b746923d9897c to master...


[mle] handle received Advertisements from RxOnlyNeighbor on FED

This commit updates Mle class such that on an FED (FTD child) when an MLE Advertisement is received, we use FindRxOnlyNeighborRouter() in addition to FindNeighbor() which only checks the parent and parent candidate on an FED. This ensures that the key sequence and frame counters are validated for Advertisement messages from a neighbor router with which the FED has established a RxOnly link.
This commit also adds a new flavor of FindRxOnlyNeighborRouter() that accepts an Mac::ExtAddress as its input parameter.

Closing this PR in favor of https://github.com/openthread/openthread/pull/9484.


Power Toys run with mica effects and smooth open and close animations for windows 11

Mica effect for power toys run with new open and close animation
it will be very beautiful and cool to update power toys run design to mica effect and open , close animation with smooth one for windows 11.
Scenario when this would be used?
It will be used while using the search tool, so that it gives a more aesthetic appearance and greater compatibility with Windows 11 .. and its consistent, compatible, more attractive, and more suitable with Windows 11
like this

Supporting information
No response

Any response??

/dup #4794

hey it's from 2020 without any updates we are now in the end of 2022 without any change in appearance so please change it


Disable SA1000: Keywords should be spaced correctly

@iSazonov Please merge ASAP.

I'm seeing warnings on the following pattern in live analysis, I'm surprised CI did not fail:
SA1000: The keyword 'new' should be followed by a space.
https://github.com/PowerShell/PowerShell/blob/db94377b3a69511280d329e64375475f6d7513b8/src/Microsoft.Management.Infrastructure.CimCmdlets/RemoveCimInstanceCommand.cs#L288
This issue was fixed in DotNetAnalyzers/StyleCopAnalyzers#3187, and is in the v1.2.0-beta.261 release.

Originally posted by @xtqqczze in https://github.com/PowerShell/PowerShell/issues/13973#issuecomment-735933117

@iSazonov @adityapatwardhan SA1000 is now causing failures in CI:
https://dev.azure.com/powershell/PowerShell/_build/results?buildId=69096&view=results


After hook and Before hooks are not running if a failure occrurs

Current behavior
The Before and After hooks will only run when tests pass.
Desired behavior
We want to be able to use the cucumber style After hook to run some test cleanup, even when tests fail. But currently the After hook will only run when the test passes.
Using the cypress afterEach hook is an option but it would be nice to use the cucumber After hook as it supports @tags
Test code to reproduce
Here is a link to an older test feature file from the cypress repo which illustrates the issue. The scenarios that illustrate this problem are commented out as they cause steps to fail, (Scenario: With Untagged After having test errors in steps part 1 & 2). The steps file only needed a minor tweak to pull { Given, Then, After, Before } from the right place.
https://github.com/badeball/cypress-cucumber-preprocessor/blob/77dbacb65741d559ae0eedd461f02970249f75d8/cypress/integration/BeforeAndAfterSteps.feature
Versions

Cypress version<EMAIL_ADDRESS>Preprocessor version<EMAIL_ADDRESS>** esbuild version**<EMAIL_ADDRESS>Node version: v16.14.0

Checklist

[x] I've read the FAQ.
[x] I've read Instructions for logging issues.
[x] I'm not using<EMAIL_ADDRESS>(package name has changed and it is no longer the most recent version, see #689).

Related issue:
https://github.com/badeball/cypress-cucumber-preprocessor/pull/538

The Before and After hooks will only run when tests pass.

This is by design and matches behavior found in Cucumber.
If you want afterEach behavior then use afterEach.  You can use doesFeatureMatch(..) for conditions, as seen here.

Okay, thanks for the quick reply.

Hello, I believe we need to reopen this. The behavior of an After hook is to run post-scenario, regardless of whether the scenario passed or failed.
See here:

After hooks run after the last step of each scenario, even when the step result is failed, undefined, pending, or skipped.

While that above is for Cucumber-Java, the same behavior works for Cucumber-JS where a tagged hook will still run post-scenario. I can reproduce this behavior if needed.

Re-opening, as this does in fact seem to the behavior exhibited by Cucumber, despite what I was thinking earlier.
This is likely a pretty substantial change and I don't have the ability to look into it right now. Anyone feeling particularly compelled can take a shot at it meanwhile.

As per now, the plugin will register a single afterEach hook. If a step fails, this hook will ensure that appropriate messages are  sent to the backend (example).
In order to ensure that After hooks are run despite step failure, they would have to be part of an afterEach block. This is just due to how Cypress works - there isn't any try-catch here.
However, errors ocurring in afterEach blocks are "uncatchable", as in they will cause the spec to finish early. In other words, you only have one opportunity to handle failures in Cypress and this is used by the plugin to create appropriate messages / reports.
Thus, if After hooks were to run as part of the internal afterEach, then failures in such hooks could not be handled properly and failures here would finish the spec early.
For this reason, I believe it is unlikely that this issue will be fixed.

The following tests, test output in case of failures in After hooks:

https://github.com/badeball/cypress-cucumber-preprocessor/blob/master/features/reporters/messages.feature#L263-L280
https://github.com/badeball/cypress-cucumber-preprocessor/blob/master/features/reporters/json.feature#L262-L279

This is the behavior I believe you will have some trouble retaining when moving After hook execution inside the internal afterEach hook. I also believe this would be much more probable had one had test:after:run hooks.
In any case, the code you want to look into resides in

https://github.com/badeball/cypress-cucumber-preprocessor/blob/master/lib/browser-runtime.ts
https://github.com/badeball/cypress-cucumber-preprocessor/blob/master/lib/plugin-event-handlers.ts

The former is run in the browser and it's there you will find the internal afterEach hook. The latter is run within setupNodeEvents() { .. } through addCucumberPreprocessorPlugin().

For Cucumber, the After hook is necessarily the same as a Mocha afterEach hook since they both run immediately after a test. Also, a Cucumber After hook can be skipped or included based on tag patterns, unlike an afterEach hook.

FYI, you can use doesFeatureMatch(..) in afterEach hooks to run code conditionally based on tags.

The problem with proxying After to afterEach, is that failures in such hooks would cause the rest of the spec (test file) to be skipped, including other After hooks. In other words, you still wouldn't be able to provide the guarantee that cucumber-js offers, where all After hooks are tried, despite their status.

That would skip the rest of the spec (test file), yes. This is simply just how Cypress works, I have no control nor influence over this.


ios 18 version get error

khanarif@Khans-MacBook-Pro gpspro % flutter build ios
Building com.gomax.gpspro for device (ios-release)...
Automatically signing iOS for device deployment using specified development team in Xcode project: Y59JP677FD
Running pod install...                                             21.0s
Running Xcode build...
Xcode build done.                                           51.2s
Failed to build iOS app
Swift Compiler Error (Xcode): Method does not override any method from its superclass
/Users/khanarif/.pub-cache/hosted/pub.dev/flutter_inappwebview_ios-1.0.13/ios/Classes/InAppWebView/InAppWebView.
swift:1431:25
Swift Compiler Error (Xcode): Ambiguous use of 'evaluateJavaScript(_:completionHandler:)'
/Users/khanarif/.pub-cache/hosted/pub.dev/flutter_inappwebview_ios-1.0.13/ios/Classes/InAppWebView/InAppWebView.
swift:1035:20
Swift Compiler Error (Xcode): Ambiguous use of 'evaluateJavaScript(_:completionHandler:)'
/Users/khanarif/.pub-cache/hosted/pub.dev/flutter_inappwebview_ios-1.0.13/ios/Classes/InAppWebView/InAppWebView.
swift:1038:16
Swift Compiler Error (Xcode): Ambiguous use of 'evaluateJavaScript(_:completionHandler:)'
/Users/khanarif/.pub-cache/hosted/pub.dev/flutter_inappwebview_ios-1.0.13/ios/Classes/InAppWebView/InAppWebView.
swift:1047:20
Swift Compiler Error (Xcode): Ambiguous use of 'evaluateJavaScript(_:completionHandler:)'
/Users/khanarif/.pub-cache/hosted/pub.dev/flutter_inappwebview_ios-1.0.13/ios/Classes/InAppWebView/InAppWebView.
swift:1050:16
Swift Compiler Error (Xcode): Ambiguous use of 'evaluateJavaScript(_:completionHandler:)'
/Users/khanarif/.pub-cache/hosted/pub.dev/flutter_inappwebview_ios-1.0.13/ios/Classes/InAppWebView/InAppWebView.
swift:1327:25
Swift Compiler Error (Xcode): Ambiguous use of 'evaluateJavaScript(_:completionHandler:)'
/Users/khanarif/.pub-cache/hosted/pub.dev/flutter_inappwebview_ios-1.0.13/ios/Classes/InAppWebView/InAppWebView.
swift:1912:8
Swift Compiler Error (Xcode): Ambiguous use of 'evaluateJavaScript(_:completionHandler:)'
/Users/khanarif/.pub-cache/hosted/pub.dev/flutter_inappwebview_ios-1.0.13/ios/Classes/InAppWebView/InAppWebView.
swift:2859:22
Swift Compiler Error (Xcode): Ambiguous use of 'evaluateJavaScript(_:completionHandler:)'
/Users/khanarif/.pub-cache/hosted/pub.dev/flutter_inappwebview_ios-1.0.13/ios/Classes/InAppWebView/InAppWebView.
swift:2870:22
Swift Compiler Error (Xcode): Ambiguous use of 'evaluateJavaScript(_:completionHandler:)'
/Users/khanarif/.pub-cache/hosted/pub.dev/flutter_inappwebview_ios-1.0.13/ios/Classes/InAppWebView/InAppWebView.
swift:2964:17
Encountered error while building for device.
khanarif@Khans-MacBook-Pro gpspro %

i've been facing same issue after upgrading to MacOS sequoia and upgrading Xcode.  Please if anyone knows the solution please let me know.

Experiencing the same issue after upgrading to MacOS sequoia and upgrading Xcode 16.0.

I have same error
Could not build the precompiled application for the device.
Swift Compiler Error (Xcode): Method does not override any method from its superclass
/Users/docaohuynh/.pub-cache/hosted/pub.dev/flutter_inappwebview_ios-1.0.13/ios/Classes/InAppWebView/InAppWebView.swift:1431:25

Swift Compiler Error (Xcode): Ambiguous use of 'evaluateJavaScript(_:completionHandler:)'
/Users/docaohuynh/.pub-cache/hosted/pub.dev/flutter_inappwebview_ios-1.0.13/ios/Classes/InAppWebView/InAppWebView.swift:2859:22

Swift Compiler Error (Xcode): Ambiguous use of 'evaluateJavaScript(_:completionHandler:)'
/Users/docaohuynh/.pub-cache/hosted/pub.dev/flutter_inappwebview_ios-1.0.13/ios/Classes/InAppWebView/InAppWebView.swift:2870:22

Same here

Same here

Xcode16.0 has error，when debug running

For fast fix you can replace in 1432 line InAppWebView (flutter_inappwebview_ios-1.0.13/ios/Classes/InAppWebView/InAppWebView.swift)
from
    public override func evaluateJavaScript(_ javaScriptString: String, completionHandler: ((Any?, Error?) -> Void)? = nil) {

to
    public override func evaluateJavaScript(_ javaScriptString: String, completionHandler: (@MainActor @Sendable (Any?, (any Error)?) -> Void)? = nil) {

I put this modified method, written a simple script, you can try to solve this problem   https://github.com/ke112/fixios18

    public override func evaluateJavaScript(_ javaScriptString: String, completionHandler: (@MainActor @Sendable (Any?, (any Error)?) -> Void)? = nil) {

Yes this is working, Thank you

For fast fix you can replace in 1432 line InAppWebView (flutter_inappwebview_ios-1.0.13/ios/Classes/InAppWebView/InAppWebView.swift) from
    public override func evaluateJavaScript(_ javaScriptString: String, completionHandler: ((Any?, Error?) -> Void)? = nil) {

to
    public override func evaluateJavaScript(_ javaScriptString: String, completionHandler: (@MainActor @Sendable (Any?, (any Error)?) -> Void)? = nil) {

This working, Thanks you.

Duplicate of #2278

For fast fix you can replace in 1432 line InAppWebView (flutter_inappwebview_ios-1.0.13/ios/Classes/InAppWebView/InAppWebView.swift) from
    public override func evaluateJavaScript(_ javaScriptString: String, completionHandler: ((Any?, Error?) -> Void)? = nil) {

to
    public override func evaluateJavaScript(_ javaScriptString: String, completionHandler: (@MainActor @Sendable (Any?, (any Error)?) -> Void)? = nil) {

love you. thank you.

I have the same eror, any finala solution?
the proposal solution is very dangerous, becous we are editing thje labray insie in .pubcache  and this is alwasy rewrite with pub get o whn you do a flutter clean

I have the same error, any final solution?
the proposal solution is very dangerous, because we are editing the library inside in .pubcache and this is always rewrite with pub get o when you do a flutter clean

For temporary solution you can use my form with fix this problem.
Add
dependency_overrides:
  # TODO: Recheck once flutter_inappwebview version >6.0.0 is released
  flutter_inappwebview_ios:
    git:
      url: https://github.com/IncM/flutter_inappwebview
      path: flutter_inappwebview_ios
      ref: cbc214c7b2cf5fd7996ff2e9e25d203946b74bc3

in your pubspec.yaml

Same issue. Updated XCode and game over :D

i've been facing same issue after upgrading to MacOS sequoia and upgrading Xcode. Please if anyone knows the solution please let me know.

Yesterday I upgraded my Mac and Xcode, same issue appeared...

You can use my new package zikzak_inappwebview fork of this package that I will keep maintaining. Thanks @pichillilorenzo for developing/maintaining this package for a long time. I guess he is busy or on vacataion. I am the builder of Flutter Vendure (open source headless commerce framework) package. Vendure Please open your PRs here and I am happy to check them and merge them by Monday.

public override func evaluateJavaScript(_ javaScriptString: String, completionHandler: (@MainActor @Sendable (Any?, (any Error)?) -> Void)? = nil) {

It worked for me. Thank you!

I encountered the same error after updating Xcode.
Swift Compiler Error (Xcode): Method does not override any method from its superclass
/Users/khanarif/.pub-cache/hosted/pub.dev/flutter_inappwebview_ios-1.0.13/ios/Classes/InAppWebView/InAppWebView.
swift:1431:25
Swift Compiler Error (Xcode): Ambiguous use of 'evaluateJavaScript(_:completionHandler:)'
/Users/khanarif/.pub-cache/hosted/pub.dev/flutter_inappwebview_ios-1.0.13/ios/Classes/InAppWebView/InAppWebView.
swift:1035:20
Swift Compiler Error (Xcode): Ambiguous use of 'evaluateJavaScript(_:completionHandler:)'
/Users/khanarif/.pub-cache/hosted/pub.dev/flutter_inappwebview_ios-1.0.13/ios/Classes/InAppWebView/InAppWebView.
swift:1038:16
Please Let me know if you find any solution.

So it looks like this package has been forked with a fix, with on-going maintenance. It has fixed the issue for me.
https://pub.dev/packages/zikzak_inappwebview

Perhaps easier solution is to install previous version of xcode 15.4 using xcodes.
After installing, you just setup command line tools version in xcode locations settings to 15.4 instead of 16 and voila, everything is back to working 😄

I encountered the same error after updating Xcode.
Swift Compiler Error (Xcode): Method does not override any method from its superclass /Users/khanarif/.pub-cache/hosted/pub.dev/flutter_inappwebview_ios-1.0.13/ios/Classes/InAppWebView/InAppWebView. swift:1431:25
Swift Compiler Error (Xcode): Ambiguous use of 'evaluateJavaScript(_:completionHandler:)' /Users/khanarif/.pub-cache/hosted/pub.dev/flutter_inappwebview_ios-1.0.13/ios/Classes/InAppWebView/InAppWebView. swift:1035:20
Swift Compiler Error (Xcode): Ambiguous use of 'evaluateJavaScript(_:completionHandler:)' /Users/khanarif/.pub-cache/hosted/pub.dev/flutter_inappwebview_ios-1.0.13/ios/Classes/InAppWebView/InAppWebView. swift:1038:16

If you encounter the same error, you can find your solution by visiting this link.
https://github.com/pichillilorenzo/flutter_inappwebview/issues/2283#issuecomment-2367389122

Released new version 6.1.0 with the fix, thanks.

Hello everyone! I opened an issue #2327 related to a new problem like this. I ask that you consider upvoting or interacting so that the maintainers can see this as soon as possible. Remember that these problems can happen to you - as is happening to me. :)


make condvar wait use absolute time

This was a tricky one to track down! We started seeing reports of issues using WiFi on the new esp rust board (which uses usb-serial-jtag, importantly). I initially started looking at WiFi initialization differences as the esp-idf examples worked fine. Eventually though, I tracked the issue down to the wait for connect condvar timing out instantly.
Using the rust-std-demo example, here was what was happening:
The rust code calls wait with a time-out duration (20 seconds) on the pthread condvar, the condvar being the wifi status. However, when resetting with USB serial jtag this timeout triggers immediately.
I tracked the down to the failure point being this piece of code in esp-idf:
if (timercmp(&abs_time, &cur_time, <)) {
    /* As per the pthread spec, if the time has already
     * passed, no sleep is required.
     */
    timeout_msec = 0;
}

The USB-SERIAL-JTAG leaves a timer running through reset or something? This alone is not enough to cause the bug. There is actually something else going on and it's to do with pthread_cond_timedwait semantics, as per the posix the wait time is absolute not relative, however, the current time coming from esp-idf-svc (rust) is the relative time!
How did this work in the first place you ask? This was due the rather large timeout of 20 seconds, the chip can usually boot and connect to WiFi in 20 seconds. Reducing the timeout to 5 seconds and adding a delay at the start of main can trigger this issue even when flashing with the dedicated usb serial chip (not usb-serial-jtag).
This fix gets the current time and adds the duration to that to form the absolute time the condvar should timeout.

Sorry for causing so much trouble!


Monster: Githyanki Star Seer

(I based icon choices purely off similar abilities with icons already on other monsters)
Astral Bolt:
     Item Details:
          Image Path: icons/magic/light/projectile-beam-yellow.webp  (Missing one)
          Equipped: True(It wasn't, popular modules prefer weapons equipped)
          Magical: True
          Auto Effects:
               MidiQOL flags:(At the bottom of the item)
                    Magic Effect: True
                    Magic Damage: True
Astral Step:
     Item Details:
          Image Path: icons/magic/control/debuff-energy-snare-blue.webp  (Missing one)

Thanks, in next release.


Build errors: export xx was not found in monaco-editor/esm/vs/platform/files/common/files.js

I'm struggling to build after upgrading to v7.0.2 etc.
I get several export xx was not found in xxx errors:
./node_modules/vscode/vscode/src/vs/workbench/services/workingCopy/common/workingCopyFileService.js:226:48-60 - Error: export 'IFileService' (imported as 'IFileService') was not found in 'monaco-editor/esm/vs/platform/files/common/files.js' (possible exports: FileKind)

./node_modules/vscode/vscode/src/vs/workbench/services/workspaces/common/workspaceTrust.js:187:45-61 - Error: export 'isSavedWorkspace' (imported as 'isSavedWorkspace') was not found in 'monaco-editor/esm/vs/platform/workspace/common/workspace.js' (possible exports: EXTENSION_DEVELOPMENT_EMPTY_WINDOW_WORKSPACE, IWorkspaceContextService, STANDALONE_EDITOR_WORKSPACE_ID, UNKNOWN_EMPTY_WINDOW_WORKSPACE, WORKSPACE_EXTENSION, WORKSPACE_FILTER, Workspace, WorkspaceFolder, isEmptyWorkspaceIdentifier, isSingleFolderWorkspaceIdentifier, isStandaloneEditorWorkspace, isWorkspaceIdentifier, toWorkspaceIdentifier)

./node_modules/vscode/vscode/src/vs/workbench/services/workspaces/common/workspaceTrust.js:229:34-50 - Error: export 'isSavedWorkspace' (imported as 'isSavedWorkspace') was not found in 'monaco-editor/esm/vs/platform/workspace/common/workspace.js' (possible exports: EXTENSION_DEVELOPMENT_EMPTY_WINDOW_WORKSPACE, IWorkspaceContextService, STANDALONE_EDITOR_WORKSPACE_ID, UNKNOWN_EMPTY_WINDOW_WORKSPACE, WORKSPACE_EXTENSION, WORKSPACE_FILTER, Workspace, WorkspaceFolder, isEmptyWorkspaceIdentifier, isSingleFolderWorkspaceIdentifier, isStandaloneEditorWorkspace, isWorkspaceIdentifier, toWorkspaceIdentifier)

./node_modules/vscode/vscode/src/vs/workbench/services/workspaces/common/workspaceTrust.js:362:13-33 - Error: export 'isTemporaryWorkspace' (imported as 'isTemporaryWorkspace') was not found in 'monaco-editor/esm/vs/platform/workspace/common/workspace.js' (possible exports: EXTENSION_DEVELOPMENT_EMPTY_WINDOW_WORKSPACE, IWorkspaceContextService, STANDALONE_EDITOR_WORKSPACE_ID, UNKNOWN_EMPTY_WINDOW_WORKSPACE, WORKSPACE_EXTENSION, WORKSPACE_FILTER, Workspace, WorkspaceFolder, isEmptyWorkspaceIdentifier, isSingleFolderWorkspaceIdentifier, isStandaloneEditorWorkspace, isWorkspaceIdentifier, toWorkspaceIdentifier)

./node_modules/vscode/vscode/src/vs/workbench/services/workspaces/common/workspaceTrust.js:537:279-311 - Error: export 'IWorkspaceTrustEnablementService' (imported as 'IWorkspaceTrustEnablementService') was not found in 'monaco-editor/esm/vs/platform/workspace/common/workspaceTrust.js' (possible exports: IWorkspaceTrustManagementService)

./node_modules/vscode/vscode/src/vs/workbench/services/workspaces/common/workspaceTrust.js:537:325-337 - Error: export 'IFileService' (imported as 'IFileService') was not found in 'monaco-editor/esm/vs/platform/files/common/files.js' (possible exports: FileKind)

I'm using the following :
{
  "name": "vyne-app",
  "dependencies": {
// only showing the relevant ones...
    "monaco-editor": "npm<EMAIL_ADDRESS><1.84.0",
    "monaco-languageclient": "^7.0.2",
    "vscode-languageclient": "~9.0.1",
    "vscode": "npm<EMAIL_ADDRESS><1.84.0",
    "vscode-ws-jsonrpc": "^3.1.0",
  },
  "overrides": {
    "monaco-editor": "$monaco-editor"
    "vscode": "$vscode"
  },
  "resolutions": {
    "monaco-editor": "npm<EMAIL_ADDRESS><1.84.0"
    "vscode": "npm<EMAIL_ADDRESS><1.84.0"
  },

For reference, my package.json is available here
I saw this error mentioned on this comment, but it's not clear how this was fixed.
Any help greatly appreciated!

After digging, this line seems to be (one of the) culprits:
  startLanguageClient() {
    this.monacoLanguageClient.start()
    .then(() => {
      // Adding in this line causes the errors
      this.monacoLanguageClient.sendNotification(DidOpenTextDocumentNotification.type, {
        textDocument: {
          uri: 'inmemory://query.taxi',
          languageId: TAXI_LANGUAGE_ID,
          version: 0,
          text: this.content
        }
      })
    });
  }

This causes lots of the following error:
./node_modules/vscode/vscode/src/vs/workbench/contrib/debug/common/debug.js:218:45-65 - Error: export 'localizeWithPath' (imported as 'nls') was not found in 'monaco-editor/esm/vs/nls.js' (possible exports: create, getConfiguredDefaultLocale, load, localize, setPseudoTranslation)

It seems you use the non-treemended version of monaco-editor
I think the convention now is to use @codingame/monaco-editor-treemended instead of monaco-editor, @kaisalmen am I right?

The package.json committed right now is using the non-treemended version.
However, I just switched back (have been trying many many configurations to try to get this to work).
Here's my package.json deps:
    "monaco-editor": "npm<EMAIL_ADDRESS><1.84.0",
    "monaco-editor-workers": "~0.44.0",
    "monaco-languageclient": "^7.0.2",
    "vscode-languageclient": "~9.0.1",
    "@codingame/monaco-vscode-configuration-service-override": "~1.83.7",
    "@codingame/monaco-vscode-editor-service-override": "~1.83.7",
    "@codingame/monaco-vscode-files-service-override": "~1.83.7",
    "@codingame/monaco-vscode-json-default-extension": "~1.83.7",
    "@codingame/monaco-vscode-keybindings-service-override": "~1.83.7",
    "@codingame/monaco-vscode-python-default-extension": "~1.83.7",
    "@codingame/monaco-vscode-textmate-service-override": "~1.83.7",
    "@codingame/monaco-vscode-theme-defaults-default-extension": "~1.83.7",
    "@codingame/monaco-vscode-theme-service-override": "~1.83.7",
    "vscode": "npm<EMAIL_ADDRESS><1.84.0",

At build time, gives the following errors:
./src/app/json-viewer/json-viewer.component.ts:10:0-122 - Error: Module not found: Error: Can't resolve 'monaco-editor/esm/vs/editor/standalone/browser/quickAccess/standaloneHelpQuickAccess.js' in '/home/martypitt/dev/vyne/vyne-query-service/src/main/web/src/app/json-viewer'

./src/app/json-viewer/json-viewer.component.ts:11:0-126 - Error: Module not found: Error: Can't resolve 'monaco-editor/esm/vs/editor/standalone/browser/quickAccess/standaloneGotoLineQuickAccess.js' in '/home/martypitt/dev/vyne/vyne-query-service/src/main/web/src/app/json-viewer'

./src/app/json-viewer/json-viewer.component.ts:12:0-128 - Error: Module not found: Error: Can't resolve 'monaco-editor/esm/vs/editor/standalone/browser/quickAccess/standaloneGotoSymbolQuickAccess.js' in '/home/martypitt/dev/vyne/vyne-query-service/src/main/web/src/app/json-viewer'

./src/app/json-viewer/json-viewer.component.ts:13:0-126 - Error: Module not found: Error: Can't resolve 'monaco-editor/esm/vs/editor/standalone/browser/quickAccess/standaloneCommandsQuickAccess.js' in '/home/martypitt/dev/vyne/vyne-query-service/src/main/web/src/app/json-viewer'

Those files don't exist anymore with the treemended version, what is trying to import them?

You're right, and my apologies for the confusing messages. I've been back-and-forth on this so long, that I've stopped reading meaningful messages.
I tidied up the messages above, but I'm back to:
./node_modules/vscode/api.js:111:12-26 - Error: export 'FileType' (imported as 'files') was not found in 'monaco-editor/esm/vs/platform/files/common/files.js' (possible exports: FileKind)

./node_modules/vscode/api.js:112:18-38 - Error: export 'FilePermission' (imported as 'files') was not found in 'monaco-editor/esm/vs/platform/files/common/files.js' (possible exports: FileKind)

./node_modules/vscode/vscode/src/vs/platform/telemetry/common/telemetryUtils.js:42:50-70 - Error: export 'TELEMETRY_SETTING_ID' (imported as 'TELEMETRY_SETTING_ID') was not found in 'monaco-editor/esm/vs/platform/telemetry/common/telemetry.js' (possible exports: ITelemetryService)

./node_modules/vscode/vscode/src/vs/platform/telemetry/common/telemetryUtils.js:43:60-95 - Error: export 'TELEMETRY_CRASH_REPORTER_SETTING_ID' (imported as 'TELEMETRY_CRASH_REPORTER_SETTING_ID') was not found in 'monaco-editor/esm/vs/platform/telemetry/common/telemetry.js' (possible exports: ITelemetryService)

./node_modules/vscode/vscode/src/vs/platform/telemetry/common/telemetryUtils.js:44:50-74 - Error: export 'TELEMETRY_OLD_SETTING_ID' (imported as 'TELEMETRY_OLD_SETTING_ID') was not found in 'monaco-editor/esm/vs/platform/telemetry/common/telemetry.js' (possible exports: ITelemetryService)

./node_modules/vscode/vscode/src/vs/workbench/api/common/extHostTypes.js:2299:47-85 - Error: export 'FileSystemProviderErrorCode' (imported as 'FileSystemProviderErrorCode') was not found in 'monaco-editor/esm/vs/platform/files/common/files.js' (possible exports: FileKind)

./node_modules/vscode/vscode/src/vs/workbench/api/common/extHostTypes.js:2302:47-87 - Error: export 'FileSystemProviderErrorCode' (imported as 'FileSystemProviderErrorCode') was not found in 'monaco-editor/esm/vs/platform/files/common/files.js' (possible exports: FileKind)

./node_modules/vscode/vscode/src/vs/workbench/api/common/extHostTypes.js:2305:47-92 - Error: export 'FileSystemProviderErrorCode' (imported as 'FileSystemProviderErrorCode') was not found in 'monaco-editor/esm/vs/platform/files/common/files.js' (possible exports: FileKind)

./node_modules/vscode/vscode/src/vs/workbench/api/common/extHostTypes.js:2308:47-91 - Error: export 'FileSystemProviderErrorCode' (imported as 'FileSystemProviderErrorCode') was not found in 'monaco-editor/esm/vs/platform/files/common/files.js' (possible exports: FileKind)

./node_modules/vscode/vscode/src/vs/workbench/api/common/extHostTypes.js:2311:47-88 - Error: export 'FileSystemProviderErrorCode' (imported as 'FileSystemProviderErrorCode') was not found in 'monaco-editor/esm/vs/platform/files/common/files.js' (possible exports: FileKind)

./node_modules/vscode/vscode/src/vs/workbench/api/common/extHostTypes.js:2314:47-86 - Error: export 'FileSystemProviderErrorCode' (imported as 'FileSystemProviderErrorCode') was not found in 'monaco-editor/esm/vs/platform/files/common/files.js' (possible exports: FileKind)

./node_modules/vscode/vscode/src/vs/workbench/api/common/extHostTypes.js:2316:35-70 - Error: export 'FileSystemProviderErrorCode' (imported as 'FileSystemProviderErrorCode') was not found in 'monaco-editor/esm/vs/platform/files/common/files.js' (possible exports: FileKind)

./node_modules/vscode/vscode/src/vs/workbench/api/common/extHostTypes.js:2319:4-33 - Error: export 'markAsFileSystemProviderError' (imported as 'markAsFileSystemProviderError') was not found in 'monaco-editor/esm/vs/platform/files/common/files.js' (possible exports: FileKind)

./node_modules/vscode/vscode/src/vs/workbench/api/common/extHostTypes.js:2368:39-52 - Error: export 'isStringArray' (imported as 'isStringArray') was not found in 'monaco-editor/esm/vs/base/common/types.js' (possible exports: assertIsDefined, assertType, isBoolean, isDefined, isFunction, isIterable, isNumber, isObject, isString, isTypedArray, isUndefined, isUndefinedOrNull, validateConstraint, validateConstraints)

./node_modules/vscode/vscode/src/vs/workbench/api/common/extHostTypes.js:2719:27-44 - Error: export 'normalizeMimeType' (imported as 'normalizeMimeType') was not found in 'monaco-editor/esm/vs/base/common/mime.js' (possible exports: Mimes)

./node_modules/vscode/vscode/src/vs/workbench/api/common/extHostTypes.js:2741:25-42 - Error: export 'normalizeMimeType' (imported as 'normalizeMimeType') was not found in 'monaco-editor/esm/vs/base/common/mime.js' (possible exports: Mimes)

./node_modules/vscode/vscode/src/vs/workbench/contrib/debug/common/debug.js:15:15-35 - Error: export 'localizeWithPath' (imported as 'nls') was not found in 'monaco-editor/esm/vs/nls.js' (possible exports: create, getConfiguredDefaultLocale, load, localize, setPseudoTranslation)

./node_modules/vscode/vscode/src/vs/workbench/contrib/debug/common/debug.js:19:15-35 - Error: export 'localizeWithPath' (imported as 'nls') was not found in 'monaco-editor/esm/vs/nls.js' (possible exports: create, getConfiguredDefaultLocale, load, localize, setPseudoTranslation)

./node_modules/vscode/vscode/src/vs/workbench/contrib/debug/common/debug.js:23:15-35 - Error: export 'localizeWithPath' (imported as 'nls') was not found in 'monaco-editor/esm/vs/nls.js' (possible exports: create, getConfiguredDefaultLocale, load, localize, setPseudoTranslation)

./node_modules/vscode/vscode/src/vs/workbench/contrib/debug/common/debug.js:28:15-35 - Error: export 'localizeWithPath' (imported as 'nls') was not found in 'monaco-editor/esm/vs/nls.js' (possible exports: create, getConfiguredDefaultLocale, load, localize, setPseudoTranslation)

./node_modules/vscode/vscode/src/vs/workbench/contrib/debug/common/debug.js:32:15-35 - Error: export 'localizeWithPath' (imported as 'nls') was not found in 'monaco-editor/esm/vs/nls.js' (possible exports: create, getConfiguredDefaultLocale, load, localize, setPseudoTranslation)

./node_modules/vscode/vscode/src/vs/workbench/contrib/debug/common/debug.js:36:15-35 - Error: export 'localizeWithPath' (imported as 'nls') was not found in 'monaco-editor/esm/vs/nls.js' (possible exports: create, getConfiguredDefaultLocale, load, localize, setPseudoTranslation)

./node_modules/vscode/vscode/src/vs/workbench/contrib/debug/common/debug.js:40:15-35 - Error: export 'localizeWithPath' (imported as 'nls') was not found in 'monaco-editor/esm/vs/nls.js' (possible exports: create, getConfiguredDefaultLocale, load, localize, setPseudoTranslation)

./node_modules/vscode/vscode/src/vs/workbench/contrib/debug/common/debug.js:44:15-35 - Error: export 'localizeWithPath' (imported as 'nls') was not found in 'monaco-editor/esm/vs/nls.js' (possible exports: create, getConfiguredDefaultLocale, load, localize, setPseudoTranslation)

./node_modules/vscode/vscode/src/vs/workbench/contrib/debug/common/debug.js:48:15-35 - Error: export 'localizeWithPath' (imported as 'nls') was not found in 'monaco-editor/esm/vs/nls.js' (possible exports: create, getConfiguredDefaultLocale, load, localize, setPseudoTranslation)

./node_modules/vscode/vscode/src/vs/workbench/contrib/debug/common/debug.js:52:15-35 - Error: export 'localizeWithPath' (imported as 'nls') was not found in 'monaco-editor/esm/vs/nls.js' (possible exports: create, getConfiguredDefaultLocale, load, localize, setPseudoTranslation)

./node_modules/vscode/vscode/src/vs/workbench/contrib/debug/common/debug.js:56:15-35 - Error: export 'localizeWithPath' (imported as 'nls') was not found in 'monaco-editor/esm/vs/nls.js' (possible exports: create, getConfiguredDefaultLocale, load, localize, setPseudoTranslation)

./node_modules/vscode/vscode/src/vs/workbench/contrib/debug/common/debug.js:60:15-35 - Error: export 'localizeWithPath' (imported as 'nls') was not found in 'monaco-editor/esm/vs/nls.js' (possible exports: create, getConfiguredDefaultLocale, load, localize, setPseudoTranslation)

./node_modules/vscode/vscode/src/vs/workbench/contrib/debug/common/debug.js:64:15-35 - Error: export 'localizeWithPath' (imported as 'nls') was not found in 'monaco-editor/esm/vs/nls.js' (possible exports: create, getConfiguredDefaultLocale, load, localize, setPseudoTranslation)

./node_modules/vscode/vscode/src/vs/workbench/contrib/debug/common/debug.js:68:15-35 - Error: export 'localizeWithPath' (imported as 'nls') was not found in 'monaco-editor/esm/vs/nls.js' (possible exports: create, getConfiguredDefaultLocale, load, localize, setPseudoTranslation)

./node_modules/vscode/vscode/src/vs/workbench/contrib/debug/common/debug.js:72:15-35 - Error: export 'localizeWithPath' (imported as 'nls') was not found in 'monaco-editor/esm/vs/nls.js' (possible exports: create, getConfiguredDefaultLocale, load, localize, setPseudoTranslation)

./node_modules/vscode/vscode/src/vs/workbench/contrib/debug/common/debug.js:76:15-35 - Error: export 'localizeWithPath' (imported as 'nls') was not found in 'monaco-editor/esm/vs/nls.js' (possible exports: create, getConfiguredDefaultLocale, load, localize, setPseudoTranslation)

./node_modules/vscode/vscode/src/vs/workbench/contrib/debug/common/debug.js:80:15-35 - Error: export 'localizeWithPath' (imported as 'nls') was not found in 'monaco-editor/esm/vs/nls.js' (possible exports: create, getConfiguredDefaultLocale, load, localize, setPseudoTranslation)

./node_modules/vscode/vscode/src/vs/workbench/contrib/debug/common/debug.js:84:15-35 - Error: export 'localizeWithPath' (imported as 'nls') was not found in 'monaco-editor/esm/vs/nls.js' (possible exports: create, getConfiguredDefaultLocale, load, localize, setPseudoTranslation)

./node_modules/vscode/vscode/src/vs/workbench/contrib/debug/common/debug.js:88:15-35 - Error: export 'localizeWithPath' (imported as 'nls') was not found in 'monaco-editor/esm/vs/nls.js' (possible exports: create, getConfiguredDefaultLocale, load, localize, setPseudoTranslation)

./node_modules/vscode/vscode/src/vs/workbench/contrib/debug/common/debug.js:92:15-35 - Error: export 'localizeWithPath' (imported as 'nls') was not found in 'monaco-editor/esm/vs/nls.js' (possible exports: create, getConfiguredDefaultLocale, load, localize, setPseudoTranslation)

./node_modules/vscode/vscode/src/vs/workbench/contrib/debug/common/debug.js:96:15-35 - Error: export 'localizeWithPath' (imported as 'nls') was not found in 'monaco-editor/esm/vs/nls.js' (possible exports: create, getConfiguredDefaultLocale, load, localize, setPseudoTranslation)

./node_modules/vscode/vscode/src/vs/workbench/contrib/debug/common/debug.js:100:15-35 - Error: export 'localizeWithPath' (imported as 'nls') was not found in 'monaco-editor/esm/vs/nls.js' (possible exports: create, getConfiguredDefaultLocale, load, localize, setPseudoTranslation)

./node_modules/vscode/vscode/src/vs/workbench/contrib/debug/common/debug.js:104:15-35 - Error: export 'localizeWithPath' (imported as 'nls') was not found in 'monaco-editor/esm/vs/nls.js' (possible exports: create, getConfiguredDefaultLocale, load, localize, setPseudoTranslation)

./node_modules/vscode/vscode/src/vs/workbench/contrib/debug/common/debug.js:108:15-35 - Error: export 'localizeWithPath' (imported as 'nls') was not found in 'monaco-editor/esm/vs/nls.js' (possible exports: create, getConfiguredDefaultLocale, load, localize, setPseudoTranslation)

./node_modules/vscode/vscode/src/vs/workbench/contrib/debug/common/debug.js:112:15-35 - Error: export 'localizeWithPath' (imported as 'nls') was not found in 'monaco-editor/esm/vs/nls.js' (possible exports: create, getConfiguredDefaultLocale, load, localize, setPseudoTranslation)

./node_modules/vscode/vscode/src/vs/workbench/contrib/debug/common/debug.js:116:15-35 - Error: export 'localizeWithPath' (imported as 'nls') was not found in 'monaco-editor/esm/vs/nls.js' (possible exports: create, getConfiguredDefaultLocale, load, localize, setPseudoTranslation)

./node_modules/vscode/vscode/src/vs/workbench/contrib/debug/common/debug.js:120:15-35 - Error: export 'localizeWithPath' (imported as 'nls') was not found in 'monaco-editor/esm/vs/nls.js' (possible exports: create, getConfiguredDefaultLocale, load, localize, setPseudoTranslation)

./node_modules/vscode/vscode/src/vs/workbench/contrib/debug/common/debug.js:124:15-35 - Error: export 'localizeWithPath' (imported as 'nls') was not found in 'monaco-editor/esm/vs/nls.js' (possible exports: create, getConfiguredDefaultLocale, load, localize, setPseudoTranslation)

./node_modules/vscode/vscode/src/vs/workbench/contrib/debug/common/debug.js:128:15-35 - Error: export 'localizeWithPath' (imported as 'nls') was not found in 'monaco-editor/esm/vs/nls.js' (possible exports: create, getConfiguredDefaultLocale, load, localize, setPseudoTranslation)

./node_modules/vscode/vscode/src/vs/workbench/contrib/debug/common/debug.js:132:15-35 - Error: export 'localizeWithPath' (imported as 'nls') was not found in 'monaco-editor/esm/vs/nls.js' (possible exports: create, getConfiguredDefaultLocale, load, localize, setPseudoTranslation)

./node_modules/vscode/vscode/src/vs/workbench/contrib/debug/common/debug.js:136:15-35 - Error: export 'localizeWithPath' (imported as 'nls') was not found in 'monaco-editor/esm/vs/nls.js' (possible exports: create, getConfiguredDefaultLocale, load, localize, setPseudoTranslation)

./node_modules/vscode/vscode/src/vs/workbench/contrib/debug/common/debug.js:140:15-35 - Error: export 'localizeWithPath' (imported as 'nls') was not found in 'monaco-editor/esm/vs/nls.js' (possible exports: create, getConfiguredDefaultLocale, load, localize, setPseudoTranslation)

./node_modules/vscode/vscode/src/vs/workbench/contrib/debug/common/debug.js:144:15-35 - Error: export 'localizeWithPath' (imported as 'nls') was not found in 'monaco-editor/esm/vs/nls.js' (possible exports: create, getConfiguredDefaultLocale, load, localize, setPseudoTranslation)

./node_modules/vscode/vscode/src/vs/workbench/contrib/debug/common/debug.js:148:15-35 - Error: export 'localizeWithPath' (imported as 'nls') was not found in 'monaco-editor/esm/vs/nls.js' (possible exports: create, getConfiguredDefaultLocale, load, localize, setPseudoTranslation)

./node_modules/vscode/vscode/src/vs/workbench/contrib/debug/common/debug.js:152:15-35 - Error: export 'localizeWithPath' (imported as 'nls') was not found in 'monaco-editor/esm/vs/nls.js' (possible exports: create, getConfiguredDefaultLocale, load, localize, setPseudoTranslation)

./node_modules/vscode/vscode/src/vs/workbench/contrib/debug/common/debug.js:156:15-35 - Error: export 'localizeWithPath' (imported as 'nls') was not found in 'monaco-editor/esm/vs/nls.js' (possible exports: create, getConfiguredDefaultLocale, load, localize, setPseudoTranslation)

./node_modules/vscode/vscode/src/vs/workbench/contrib/debug/common/debug.js:160:15-35 - Error: export 'localizeWithPath' (imported as 'nls') was not found in 'monaco-editor/esm/vs/nls.js' (possible exports: create, getConfiguredDefaultLocale, load, localize, setPseudoTranslation)

./node_modules/vscode/vscode/src/vs/workbench/contrib/debug/common/debug.js:164:15-35 - Error: export 'localizeWithPath' (imported as 'nls') was not found in 'monaco-editor/esm/vs/nls.js' (possible exports: create, getConfiguredDefaultLocale, load, localize, setPseudoTranslation)

./node_modules/vscode/vscode/src/vs/workbench/contrib/debug/common/debug.js:168:15-35 - Error: export 'localizeWithPath' (imported as 'nls') was not found in 'monaco-editor/esm/vs/nls.js' (possible exports: create, getConfiguredDefaultLocale, load, localize, setPseudoTranslation)

./node_modules/vscode/vscode/src/vs/workbench/contrib/debug/common/debug.js:172:15-35 - Error: export 'localizeWithPath' (imported as 'nls') was not found in 'monaco-editor/esm/vs/nls.js' (possible exports: create, getConfiguredDefaultLocale, load, localize, setPseudoTranslation)

./node_modules/vscode/vscode/src/vs/workbench/contrib/debug/common/debug.js:176:15-35 - Error: export 'localizeWithPath' (imported as 'nls') was not found in 'monaco-editor/esm/vs/nls.js' (possible exports: create, getConfiguredDefaultLocale, load, localize, setPseudoTranslation)

./node_modules/vscode/vscode/src/vs/workbench/contrib/debug/common/debug.js:180:15-35 - Error: export 'localizeWithPath' (imported as 'nls') was not found in 'monaco-editor/esm/vs/nls.js' (possible exports: create, getConfiguredDefaultLocale, load, localize, setPseudoTranslation)

./node_modules/vscode/vscode/src/vs/workbench/contrib/debug/common/debug.js:184:15-35 - Error: export 'localizeWithPath' (imported as 'nls') was not found in 'monaco-editor/esm/vs/nls.js' (possible exports: create, getConfiguredDefaultLocale, load, localize, setPseudoTranslation)

./node_modules/vscode/vscode/src/vs/workbench/contrib/debug/common/debug.js:188:15-35 - Error: export 'localizeWithPath' (imported as 'nls') was not found in 'monaco-editor/esm/vs/nls.js' (possible exports: create, getConfiguredDefaultLocale, load, localize, setPseudoTranslation)

./node_modules/vscode/vscode/src/vs/workbench/contrib/debug/common/debug.js:192:15-35 - Error: export 'localizeWithPath' (imported as 'nls') was not found in 'monaco-editor/esm/vs/nls.js' (possible exports: create, getConfiguredDefaultLocale, load, localize, setPseudoTranslation)

./node_modules/vscode/vscode/src/vs/workbench/contrib/debug/common/debug.js:196:15-35 - Error: export 'localizeWithPath' (imported as 'nls') was not found in 'monaco-editor/esm/vs/nls.js' (possible exports: create, getConfiguredDefaultLocale, load, localize, setPseudoTranslation)

./node_modules/vscode/vscode/src/vs/workbench/contrib/debug/common/debug.js:200:15-35 - Error: export 'localizeWithPath' (imported as 'nls') was not found in 'monaco-editor/esm/vs/nls.js' (possible exports: create, getConfiguredDefaultLocale, load, localize, setPseudoTranslation)

./node_modules/vscode/vscode/src/vs/workbench/contrib/debug/common/debug.js:204:15-35 - Error: export 'localizeWithPath' (imported as 'nls') was not found in 'monaco-editor/esm/vs/nls.js' (possible exports: create, getConfiguredDefaultLocale, load, localize, setPseudoTranslation)

./node_modules/vscode/vscode/src/vs/workbench/contrib/debug/common/debug.js:208:15-35 - Error: export 'localizeWithPath' (imported as 'nls') was not found in 'monaco-editor/esm/vs/nls.js' (possible exports: create, getConfiguredDefaultLocale, load, localize, setPseudoTranslation)

./node_modules/vscode/vscode/src/vs/workbench/contrib/debug/common/debug.js:212:15-35 - Error: export 'localizeWithPath' (imported as 'nls') was not found in 'monaco-editor/esm/vs/nls.js' (possible exports: create, getConfiguredDefaultLocale, load, localize, setPseudoTranslation)

./node_modules/vscode/vscode/src/vs/workbench/contrib/debug/common/debug.js:216:15-35 - Error: export 'localizeWithPath' (imported as 'nls') was not found in 'monaco-editor/esm/vs/nls.js' (possible exports: create, getConfiguredDefaultLocale, load, localize, setPseudoTranslation)

./node_modules/vscode/vscode/src/vs/workbench/contrib/debug/common/debug.js:218:45-65 - Error: export 'localizeWithPath' (imported as 'nls') was not found in 'monaco-editor/esm/vs/nls.js' (possible exports: create, getConfiguredDefaultLocale, load, localize, setPseudoTranslation)

./node_modules/vscode/vscode/src/vs/workbench/contrib/debug/common/debug.js:225:15-35 - Error: export 'localizeWithPath' (imported as 'nls') was not found in 'monaco-editor/esm/vs/nls.js' (possible exports: create, getConfiguredDefaultLocale, load, localize, setPseudoTranslation)

./node_modules/vscode/vscode/src/vs/workbench/contrib/notebook/common/notebookCommon.js:44:33-45 - Error: export 'encodeBase64' (imported as 'encodeBase64') was not found in 'monaco-editor/esm/vs/base/common/buffer.js' (possible exports: VSBuffer, readUInt16LE, readUInt32BE, readUInt8, writeUInt16LE, writeUInt32BE, writeUInt8)

./node_modules/vscode/vscode/src/vs/workbench/contrib/notebook/common/notebookCommon.js:60:20-32 - Error: export 'decodeBase64' (imported as 'decodeBase64') was not found in 'monaco-editor/esm/vs/base/common/buffer.js' (possible exports: VSBuffer, readUInt16LE, readUInt32BE, readUInt8, writeUInt16LE, writeUInt32BE, writeUInt8)

For reference, this is the line of code that causes the error to appear - specifically, the reference to DidOpenTextDocumentNotification  Commented out, the build works (but we obviously need the notification):
    this.monacoLanguageClient.start()
    .then(() => {
         this.monacoLanguageClient.sendNotification(DidOpenTextDocumentNotification.type, null)
    });

you probably have a duplicated dependency, monaco-editor non treemended is used somewhere

Fantastic - thanks for your help -- fixing the invalid deps resolved the issue.
Turned out to be caused by a left over devDependency on "monaco-editor-webpack-plugin": "^7.0.1",.
One final question -
Would you mind verifying what the correct configuration should be?
The example has the following:
  "overrides": {
    "monaco-editor": "$monaco-editor",
    "vscode": "$vscode"
  },

I'm not familiar with the $monaco-editor syntax used there.
However, the README shows the following:
  "overrides": {
    "monaco-editor": "npm<EMAIL_ADDRESS><1.84.0",
    "vscode": "npm<EMAIL_ADDRESS><1.84.0"
  },

Can you please clarify the difference, and which is correct?

It seems that $monaco-editor just references the version in the dependencies, see https://docs.npmjs.com/cli/v9/configuring-npm/package-json#overrides

@martypitt sorry you had to traverse this muddy road. I updated the troubleshooting section here. The CHANGELOG and the README already carried a lot of helpful information, but this should help even more.

It seems that $monaco-editor just references the version in the dependencies, see https://docs.npmjs.com/cli/v9/configuring-npm/package-json#overrides

This is a helpful short-cut in case you have the dependencies already defined locally, but you still need to enforce the specific override throughout your dependency tree with overrides. You can always write it down fully

Yup I didn't know about that syntax, it's cool!

No problem. I think, in retrospect, the docs were pretty clear.  I was a
little thrown by the examples not matching the docs, but that could equally
be down to my own lack of experience with package.json format.
Appreciate the speedy responses!
Thanks again
On Tue, 21 Nov 2023, 12:56 Kai Salmen, @.***> wrote:

@martypitt https://github.com/martypitt sorry you had to traverse this
muddy road. I updated the troubleshooting section here
https://github.com/TypeFox/monaco-languageclient#dependency-issues-monaco-editor--codingamemonaco-editor-treemended.
The CHANGELOG and the README already carried a lot of helpful information,
but this should help even more.
—
Reply to this email directly, view it on GitHub
https://github.com/TypeFox/monaco-languageclient/issues/573#issuecomment-1820875094,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AACVFNFPHK2EGZIXANBOGWDYFSQGTAVCNFSM6AAAAAA7TVSAHCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMRQHA3TKMBZGQ
.
You are receiving this because you were mentioned.Message ID:
@.***>


Disable Animations in FancyZones

Description of the new feature / enhancement
I would like for FancyZones to honor the system animation preferences (as set in SystemPropertiesPerformance.exe) and not show any animations like fading the grid/zones into view, when the user has chosen not to see animations.
Scenario when this would be used?
While it's smooth and a great experience locally, when I access my PC via RDP, the fade-in of the zones causes hard jitty and lag.
Supporting information
No response

Tracked via #1911

Confirming this is not fixed in the latest version 0.62.1.
I have Windows Animations turned off and am watching the overlay paint in like a slide show.

@keyboardg, it is tracked via #1911


⚠ MineVN Maven & Resource Pack has degraded performance

In 7136f79, MineVN Maven & Resource Pack (http://app.minevn.net/pack) experienced degraded performance:

HTTP code: 520
Response time: 14172 ms

Resolved: MineVN Maven & Resource Pack performance has improved in 9948b97.


i create a code for ternary search in c

Great work please give this repo a star and follow me for follow back 😊✨