Latest release of VSCode (1.76.0) breaks first party extensions including "WAVE for Windows"

looks related to "I cannot build my VSCode extension project in VSCode after update to 1.76"  Issue #175833
•	Our first party Extensions such as "WAVE", which is required by Windows developers to write and compile their code, have been broken for developers on the latest VSCode release (1.76.0), starting with c4a609f94329b17d91cd13a4fd113d1abfe5ec1f
Typically, when a dev opens a folder in the OS repo, the Wave extension is activated and begins to initialize and 'restore dependencies', by running a few scripts, setting up the build environment.  in >= 1.76.0, we briefly see "Activating extensions..." in the status bar then it abruptly stops.
•	Windows developers on release 1.76.0 have been unable to do their work in VSCode since the release
•	When users revert to version 1.75, the issues don't happen anymore; the extension is activated, scripts run, and the environment is properly prepared.
What we know so far:
•	Our WAVE extension is loaded, at least momentarily and initialization begins, but fails and exits fairly early on
o	Per the comment from the GitHub issue above, we listened for error messages in devtools (Help > Toggle Developer Tools)
o	VSCode output has very few details in the log, and not very helpful to debug
o	Our wave extension architect tried debugging and noticed that the build does not complete. VSCode attempts to launch WAVE but then sharply exits the process with no indication in the debugger for what is happening under the hood.
No log info in debugger that indicates why the “Activating extensions” process quits.
Results of npx vscode-bisect:
√ Is c4a609f94329b17d91cd13a4fd113d1abfe5ec1f good or bad? » Bad
...
√ Is 9a1ee564ee63315b690670ed68b9d3fe37e3b291 good or bad? » Good
**c4a609f94329b17d91cd13a4fd113d1abfe5ec1f** is the first bad commit after
9a1ee564ee63315b690670ed68b9d3fe37e3b291.

Comparing 9a1ee564ee63315b690670ed68b9d3fe37e3b291...c4a609f94329b17d91cd13a4fd113d1abfe5ec1f · microsoft/vscode · GitHub

I built and ran git bisect which narrowed it down to this commit:
Bisecting: 0 revisions left to test after this (roughly 0 steps)
[1108c31f0d0b4852786db42904a135acb56209a5] Adopt activationEventsGenerator for onTaskType (#173192)

Just wanted to say 👏 for doing the bisecting even down to the committ.

Looks related to #175821

I can confirm that if I remove the task definitions from our extension, that I am able to load our WAVE extension and hit breakpoints in the debugger (obviously with limited functionality). Our Mocha tests also start whereas they did not start before with 1.76.

The commit https://github.com/microsoft/vscode/commit/1108c31f0d0b4852786db42904a135acb56209a5 will add the onTaskType:X activation event to the activation event array for extensions contributing a specific task type X.
The only way I can imagine this could backfire:

the extension contributes a task of type X
the extension did not have onTaskType:X as an activation event so far
the extension has a bug where its activate() method returns a promise which never completes
we will now wait with launching debugging and tasks on activateByEvent(onTaskType:X). That means to wait on all extensions that want to activate on this event to activate. If the extension never activates (its returned promise never completes), things will stall indefinitely.

Could you please check that the promise you return from the activate() function resolves?

Can you clarify:
The extension did not have "onTaskType:X" as an activation event ?
I can confirm that we do not have "onTaskType:X" in our package.json, but we also never have.
In the meantime, I'll step through our activate() promise and see if it completes.

I've added onTaskType: to our package.json activation events, and that had no affect. But, yes, our activate() promise is never completing because it is performing:
``ts
const tasks = await vscode.tasks.fetchTasks();

during the activation and it **never completes**.

I'm going to change this to not "await" and report back.

Is it possible that because our extension is activating AND provides tasks AND is calling fetch tasks during its activation that it causes some sort of "hang" inside VSCode?

Yes! It looks like a dead-lock. Most likely:

the extension activate() waits on vscode.tasks.fetchTasks()
vscode.tasks.fetchTasks() waits on activateByEvent(onTaskType:X)
activateByEvent(onTaskType:X) waits on the extension activate()

I'm using const tasks = await vscode.tasks.fetchTasks(); in my extension and this does not resolve only when I have some other extensions, that maybe provide tasks, crashing during the activation. If I uninstall the "crashing" extension this resolves and fix the issue. This behavior started with v1.76.0

@alexr00 any chance we can diagnose and fix soon?

Typed that last comment from my phone :) Let me clarify my concern. While we can work around this in our extension because we understand the issue, it appears that if any other extension has similar code that it may block extension startup. Thank you @microhobby for looking into this.

I can reproduce this issue even when I revert the change that was made last iteration, so I believe this has been a bug for some time. Was there a change made in the wave extension within the past month @GabeDeBacker ?

I cannot reproduce in 1.75 though, which makes me wonder if something else changed in VS Code that could explain this

Since an extension can literally break tasks this probably should be a candidate, even though the root cause is an (easy to cause) extension bug.

Yes I agree, though this is reproducible in earlier versions. @Tyriar

/closedWith https://github.com/microsoft/vscode/pull/176440

Repro was an extension contributes tasks or uses onTaskType:X as an activationEvent and has await vscode.fetchTasks() in its activate method.
Try to run a task of type X. 🐛  the progress bar loads forever and extension activation status bar item spins forever.

Hmmm, using the new 1.76.1 but the await vscode.fetchTasks() continues not returning ...
Is needed some changes on the extension level?


URL Encode State Hash

You'll notice a mild asymmetry in how hash was
saved vs retrieved.
The retrieval was:
JSON.parse(decodeUrlComponent(hash))
The save was:
JSON.stringify(hash)
I modified it to:
JSON.stringify(encodeUrlComponent(hash))
The reason I noticed this is in one of my apps,
I wanted to be able to copy/share a stateful filter URL.
However without the url encoding, those auto-parsers
of URLs were missing the full filter.
TESTING CONDUCTED:

Updated the Hash unit tests to both parse the
encoded string, as well as generate it.

Ran "grunt", which has built/tested/jslinted
the code.

Thanks a lot for pointing this out. Can you please bump the version in package.json to 0.2.57, run grunt, commit and push again?
Then it's good to go,
Cheers

Tx for having updated the unit tests too 👍

Done! You can tell I don't write a lot of node.js. :-) Keep forgetting the package version.

👌


Remove DatabaseAdmin::autoBuild

Fixes #5843
It doesn't even work due to the missing getClassFile which was removed in 3.0.

:+1:

Merged as:

Easy enough for devs to implement if they want it
It won’t actually do a build if you just add a new file
It doesn’t work anyway 😛


spec for File::TMPFILE fails on Amazon Linux

spec for File::TMPFILE fails on Amazon Linux:
http://rubyci.org/logs/rubyci.s3.amazonaws.com/amazon/ruby-trunk/log/20161207T063002Z.fail.html.gz
O_TMPFILE is defined in glibc 2.19 or later:
https://github.com/bminor/glibc/commit/ffdd31816a67f48697ea4d6b852e58d2886d42ca
It may be better to test the behavior if File::TMPFILE is defined, instead of testing
the existence of the constant.

glibc version can be checked by Etc.confstr(Etc::CS_GNU_LIBC_VERSION).

Thanks for the report, bdb599c should solve it.
I looked for a test in MRI for inspiration but did not find any, so I made an example based on the manpage.

Great idea to test the behavior if defined BTW, since presence of this feature is so hard to test otherwise

Thanks for the fix.
But it failed on armv7l-linux-eabihf:
http://rubyci.org/logs/rubyci.s3.amazonaws.com/scw-9d6766/ruby-trunk/log/20161207T211705Z.fail.html.gz
It may be better to skip the test if Errno::EINVAL is raised.
And It seems that Errno:EOPNOTSUPP is raised if the filesystem doesn't
support O_TMPFILE.

I agree for EOPNOTSUPP, but it seems EINVAL is a bug on that platform:
EINVAL The filesystem does not support the O_DIRECT flag.  See NOTES for more information.
EINVAL Invalid value in flags.
EINVAL O_TMPFILE was specified in flags, but neither O_WRONLY nor O_RDWR was specified.

None of these should apply. O_DIRECT is not provided, flags are valid AFAIK and O_TMPFILE is specified with O_RDWR. Do you have any idea why it raises EINVAL?

None of these should apply. O_DIRECT is not provided, flags are valid AFAIK and O_TMPFILE is specified with O_RDWR. Do you have any idea why it raises EINVAL?

Besides these cases, EINVAL occurs if O_CREAT is specified with O_TMPFILE, but O_CREAT
is not specified in bdb599ca....
glibc 2.19 seems to have the following bug, but I'm not sure it's related.
https://lists.debian.org/debian-glibc/2016/09/msg00037.html
http://permalink.gmane.org/gmane.comp.lib.glibc.alpha/46271

Besides these cases, EINVAL occurs if O_CREAT is specified with O_TMPFILE, but O_CREAT
is not specified in bdb599c....

Indeed, I noticed that as well when trying with IO.sysopen.

5254fba allows both errors.


Parameter is not saved to json file for elementwise-binary-scalar-op

Parameter of _***Scalr ops are not saved to json file and gives error during loading. Reproducing:
import mxnet as mx

x = mx.sym.Variable('x')
y = 100*x
y.save('test.json')
y2 = mx.sym.load('test.json')

Error:
Traceback (most recent call last):
File "test.py", line 6, in
y2 = mx.sym.load('test.json')
File "/scratch/mxnet/python/mxnet/symbol.py", line 768, in load
check_call(_LIB.MXSymbolCreateFromFile(c_str(fname), ctypes.byref(handle)))
File "/scratch/mxnet/python/mxnet/base.py", line 76, in check_call
raise MXNetError(py_str(_LIB.MXGetLastError()))
mxnet.base.MXNetError: Parameter scalar is not presented

change https://github.com/dmlc/mxnet/blob/master/src/operator/elementwise_binary_scalar_op-inl.h#L255 to return param_.DICT();

@piiswrong can you submit a fix?

I have a lot of local changes. It's going to take a while to sort them out
and push
On Tue, Dec 22, 2015 at 3:01 AM, Tianqi Chen<EMAIL_ADDRESS>wrote:

@piiswrong https://github.com/piiswrong can you submit a fix?
—
Reply to this email directly or view it on GitHub
https://github.com/dmlc/mxnet/issues/995#issuecomment-166581620.

It is better to open a new branch and push changes in small PR, so they can be stagged and reviewed easily. You can always use git rebase workflow to merge the master branch back

I have got the same problem

@tqchen why is this problem still open, I got the same problem in the Release windows binary build 20151228, please fix it, thanks

Fix PR by #1215


File: samples/rails.md

looks like this was addressed in https://github.com/docker/docker.github.io/pull/13007, but these samples are quite outdated, and definitely need a cleanup overall


feat(#1472): add excluding specific mutations

fixes #1472

for now only
stryker:on
stryker:off
stryker:on MutatorName...
stryker:off MutatorName...

are working
stryker:next-on
stryker:next-off

are not implemented yet, since there were several problems with it

next-on and next-off are working now!
Next thing is to do the same for typescript mutator :)

Help needed. I can't extract a comment from TS file :/ any help would be nice

@kmdrGroch https://github.com/Microsoft/TypeScript/issues/21049#issuecomment-355756511

@Djaler I saw it, but it didn't really help me :/

@Djaler so with help of that comment, I somehow managed to get these comments.
But now I need some help with tests. Some of them aren't passing. @nicojs, @simondel, @Djaler any idea? :<

I would be happy to accept a merge request that only implements the babel-side of things. We will need to make clear remarks in the readme's

I'd like https://github.com/stryker-mutator/stryker/pull/1718 this PR to be accepted, so I can start this over again.


Fix refresh config

List of Changes

fix refresh configuration
fix channels

Motivation and Context

How Has This Been Tested?

Screenshots (if appropriate):
Types of changes

[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)

Checklist:

[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.

update_code


Pacing: Pacing of egress QUIC packets

Currently pacing is enabled for Cubic and Reno, since BBR is under development.

Please add some test for pacing.

Added some tests for pacing.

@ghedo @LPardue Can you guys review!

@ghedo @LPardue can you guys review this!

I've been using this branch since March and it's been working excellently for me. The only comment I have would be that paced congestion controllers like BBR may have "send quantum" as an output control signal and future work may want to allow congestion controllers to set a quantum value as well, which would cap the size of generated QUIC datagrams at that size.

FTR, I renamed the SendInfo field to at, to be somewhat more consistent. Also, the conversion from Instant to timespec in FFI is now only implemented when OS != macOS, iOS, Windows, in the other cases the field is just set to 0. In the future we can implement more OS-specific conversion functions.


materialize css slider within a parallax doesn't work!

when trying slider with parallax it doesn't work ,it suppose to be work like this :-
`

This is our big Tagline!

Here's our small slogan.

This is our big Tagline!

Here's our small slogan.

`
i turn arround this issue by doing so ;
[link]
(https://stackoverflow.com/questions/33459124/how-can-i-nest-materializecss-slider-within-a-parallax/46580003#46580003)

It works this is how I did it.

One Of Dubai's Most Trusted Brokers

                Property List
                Property for Sale
                Property for Rent

you can check how i turn arround the issue from here
slides code + one css line of code -not using parallax class at all
but i think it should be fixed in the core of materialize to work with class name


Changing pane with TAB doesn't refresh status bar

StatusBarExtended refreshes only upon on_path_changed(). Should refresh when changing pane with TAB button

This is most probably an issue with the on_path_changed() not being fired by fman core itself. Should probably report the issue there.

But the tab button shouldn't trigger on_path_changed() because it doesn't actually change path, it just moves the cursor to the other pane, so there's nothing wrong with on_path_changed() per se.
I just need a method to hook into (like I did on toggle_selection()), I looked through the core plugin but I couldn't find any methods for changing  cursor pane, only "MoveCursorDown/Up" etc (and I guess it would be overkill to refresh statusbar on every cursor movement in the same pane).
I'll tag @mherrmann and maybe he can give us a hint

I agree, makes sense. Would be nice if a on_pane_changed() was there.

I can see the need for this. What would be most logical to me would be an on_pane_activated event. What do you guys think?

on_pane_activated requires to either subscribe to both panes (guessing by the API naming). Or did you mean to fire with the activated pane ID in the args and is the API name a bit confusing.
I can think of two situations:

You want to know when a specific pane is activated; this would suggest on_pane_actived.
You just want to refresh something when a pane is switched. In this case it might be easier to have something like on_active_pane_changed(id).

Of course on_pane_activated(id) could be your intention but I was misinterpreting the API.

Actually, on_activated would be a better name for what I mean. Maybe that already clarifies what you now asked @bastijnv.
I would make on_activated similar to on_path_changed. Say you have:
class Foo(DirectoryPaneListener):
    def on_path_changed(self):
        pass
    def on_activated(self):
        pass

When there are two panes (the default), there would be two instances of Foo. When one pane's path changes, on_path_changed is called on that instance. When the user presses TAB so the other pane becomes active, that other Foo instance's on_activated method is called.
Does that make sense?

on_pane_activated or on_activated or whatever is perfect. Once that is fired we can simply do self.pane.id to get the current pane :)

What do you think of on_activated @bastijnv ?

That would work. Generic so it could also be reused for other elements in the future.
Thanks @m_herrmann.

@mherrmann so it ends up in your notifications (previous autocorrected to your twitter).

Okay, that's the way I'll implement it then. I've created a card so I don't forget.


Add basic compatibility check to ROM

ROM should add a simple check to verify it is running on an RTL version that it is compatible with. If not, a clear error should be reported to aid in debug.

Similar issues filed for ROM, FMC, RT:

Component
Issue Link

ROM
https://github.com/chipsalliance/caliptra-sw/issues/1423

FMC
https://github.com/chipsalliance/caliptra-sw/issues/1424

RT
https://github.com/chipsalliance/caliptra-sw/issues/1425


README claims minimum target of 7.0+ but podspec lists 8.0

This prevents anyone whose app runs on 7.0-7.1 from using Cocoapods to install this library. Has the minimum target actually changed to 8.0 or will it still run on 7.0+?

Hi @mad102190. Unfortunately it is not possible using CocoaPods. Please check https://github.com/CocoaPods/swift/issues/22. It will run on 7.0+, but you should install project manually, not using CocoaPods.


fix logic in when for job : generate a Self Signed OpenSSL certificat…

…e for dashboard

Hello Guillaume!  I added to commit sign-off. Thats all ?
Thx !

Closing in flavor of #4517


Improved error handling, styling updates

-Improved exception handling (invalid API keys caused the app not to load)
-Fixed Configuration styling
-More intuitive starting UI message (upon first time load/install)

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


Zigbee2MQTT is not sending the transition time in MQTT message

Description of the issue
Hi, I'm trying to set a transition time as I used to have in the Philips Hue Hub. Reading the documentation, I stumbled upon many ways to add this configuration, but none of them seem to work.
I added transition: 4 in every way possible:

In devices.yaml as a default value:

device_options:
  transition: 4

In devices.yaml as a single light option:

'0x0017880103fd3b4f':
    friendly_name: Roof 2
    transition: 4

And in configuration.yaml:
  "device_options": {"transition": 4},

Yet when I examine the message through MQTT Explorer, there is no transition argument:
{"state": "ON", "brightness": 254}
The light in question is a hue bulb that supports transition, as when I manually send {"state": "ON", "brightness": 254,"transition":5} the bulb transitions to the new brightness. It also transitioned correctly with the hue hub I previously used
Zigbee2MQTT is missing the transition argument when sending the message.
I would appreciate any help and can provide logs if needed, thank you!
Addon version
1.18.1-1
Platform
Core: core-2022.6.7
Supervisor: supervisor-2022.05.3
Operating System: Linux Mint 20.2
Logs of the issue (if applicable)
No response

You are using a very old z2m version
If you are still on 1.18.1 check first point of https://github.com/Koenkk/zigbee2mqtt/releases/tag/1.19.0
When transition is specified in the config, it will not be send over MQTT but will directly be applied (so internally it will convert {"state": "ON", "brightness": 254} to {"state": "ON", "brightness": 254, "transition": 5}

@Koenkk I totally missed the repo change! I switched the repo, reinstalled the addon and configured using device_options in zigbee2mqtt configuration.yaml and everything is working great.
Sorry for the issue and thank you very much!

Sorry to re-open this issue.
I still can't get transition settings to work using zigbee groups. Please advice!
It works when adding a transition value in the ui on device specific pages, but there is no such option for zigbee groups in the zigbee2mqtt webinterface and setting the device_option, option does not seem to be respected.

Setup details:
Using Zigbee2MQTT stable, version: 1.30.1-1 from the official home assistant repo: https://github.com/zigbee2mqtt/hassio-zigbee2mqtt/
/config/zigbee2mqtt/configuration.yaml
homeassistant: true
device_options:
transition: 0.4

Home Assistant 2023.2.5
Supervisor 2023.01.1
Operating System 9.5
Frontend 20230202.0 - latest


[add] unit test

Hi! @whatyouhide
I adopt unit test in this repo.
It can syntax check about Vim script by vint.
Could you check this Pull Request?
PS: If you merge this patch, github actions may work.
Reference
reviewdog : > https://github.com/reviewdog/action-vint
vint : > https://github.com/Vimjas/vint

If you don't need this pull request, feel free to close it. 🙇

Thank you.


[bug] Empty window, Failed to create GBM device for render device: /dev/dri/renderD128

Describe the bug
I was trying to compile and run mdSilo-app, but kept giving me this error. I though it might be mdSilo-specific so I created a new tauri project using create-tauri-app, but it still gives me this same error:
    Building [=======================> ] 358/359: tauri-app(bin)
    Finished dev [unoptimized + debuginfo] target(s) in 1m 22s
Gtk-Message: 15:21:25.493: Failed to load module "appmenu-gtk-module"
Could not determine the accessibility bus address
DRI driver not from this Mesa build ('23.0.3' vs '23.1.9')
failed to bind extensions
DRI driver not from this Mesa build ('23.0.3' vs '23.1.9')
failed to bind extensions
DRI driver not from this Mesa build ('23.0.3' vs '23.1.9')
failed to bind extensions
DRI driver not from this Mesa build ('23.0.3' vs '23.1.9')
failed to bind extensions
Failed to create GBM device for render device: /dev/dri/renderD128: No such file or directory
Gtk-Message: 15:21:27.416: Failed to load module "appmenu-gtk-module"
DRI driver not from this Mesa build ('23.0.3' vs '23.1.9')
failed to bind extensions
DRI driver not from this Mesa build ('23.0.3' vs '23.1.9')
failed to bind extensions
DRI driver not from this Mesa build ('23.0.3' vs '23.1.9')
failed to bind extensions
DRI driver not from this Mesa build ('23.0.3' vs '23.1.9')
failed to bind extensions
Failed to create GBM device for render device: /dev/dri/renderD128: No such file or directory
Failed to get GBM device

It doens't crash, just stays there and will continue to print "Failed to get GBM device" whenever I interact (resize) the window:

Reproduction
Repro repo: https://github.com/zyansheep/tauri-app-render-bug
Instructions (on NixOS w/ nix flakes)
nix develop
yarn
yarn tauri dev

Expected behavior
Expected the app to show the default Hello World window.
Platform and versions
yarn run v1.22.19
$ tauri info

[⚠] Environment
    - OS: NixOS 23.5.0 X64
    ✔ webkit2gtk-4.0: 2.42.2
    ✔ rsvg2: 2.56.3
    ✔ rustc: 1.76.0-nightly (dd430bc8c 2023-11-14)
    ✔ cargo: 1.76.0-nightly (6790a5127 2023-11-10)
    ⚠ rustup: not installed!
      If you have rust installed some other way, we recommend uninstalling it
      then use rustup instead. Visit https://rustup.rs/
    ⚠ Rust toolchain: couldn't be detected!
      Maybe you don't have rustup installed? if so, Visit https://rustup.rs/
    - node: 18.18.2
    - yarn: 1.22.19
    - npm: 9.8.1

[-] Packages
    - tauri [RUST]: 1.5.2
    - tauri-build [RUST]: 1.5.0
    - wry [RUST]: 0.24.4
    - tao [RUST]: 0.16.5
    - tauri-cli [RUST]: 1.5.3
    - @tauri-apps/api [NPM]: 1.5.1
    - @tauri-apps/cli [NPM]: 1.5.6

[-] App
    - build-type: bundle
    - CSP: unset
    - distDir: ../dist
    - devPath: http://localhost:1420/
    - framework: React
    - bundler: Vite
Done in 7.78s.

Stack trace
No response
Additional context
> doas inxi -GS
System:    Kernel: 6.1.62 x86_64 bits: 64 Desktop: KDE Plasma 5.27.9 Distro: NixOS 23.05 (Stoat)
Graphics:  Device-1: Intel UHD Graphics 620 driver: i915 v: kernel
           Device-2: Sunplus Innovation USB Camera type: USB driver: uvcvideo
           Display: wayland server: X.org <IP_ADDRESS> driver: loaded: modesetting resolution: <missing: xdpyinfo>
           OpenGL: renderer: Mesa Intel UHD Graphics 620 (KBL GT2) v: 4.6 Mesa 23.0.3

Edit: I figured I should probably test some tauri apps already in nixpkgs, so I installed pot and it seems to work perfectly, despite receiving nearly the same driver and render device messages as mdSilo and the blank tauri app.
Edit 2: I cloned the pot repository and build it from scratch and I'm getting the same error, so I'm wondering if it has something to do with the way it was packaged in nixpkgs :thinking:

I have a similar issue, also on NixOs. The logs are :
Could not determine the accessibility bus address
DRI driver not from this Mesa build ('23.1.7' vs '23.0.3')
failed to bind extensions
DRI driver not from this Mesa build ('23.1.7' vs '23.0.3')
failed to bind extensions
DRI driver not from this Mesa build ('23.1.7' vs '23.0.3')
failed to bind extensions
DRI driver not from this Mesa build ('23.1.7' vs '23.0.3')
failed to bind extensions
Failed to create GBM device for render device: /dev/dri/renderD129: No such file or directory
Failed to create EGL image from DMABufs with file descriptors 23, 26 and 27

I'm getting a similar issue for cinny-desktop (a Tauri-based matrix client) from the NixOS repos. pot does not seem to work for me.
Same basic errors in both, in both cases only seeing a blank or totally transparent window.
Note that this is only happening on my laptop, not on my desktop (which has a different graphics card and CPU, and thus different drivers)

Note that this is only happening on my laptop, not on my desktop (which has a different graphics card and CPU, and thus different drivers)

@alevy what drivers are you using for your laptop and desktop? I'm using intel integrated graphics on my laptop and AMD Ryzen 6600 GPU on desktop (mesa drivers I think).
I recently tried messing around with my laptop graphics and for some reason now the app page opens up (and is visible) in firefox, (but I can't actually do anything like open a folder).

I updated to 23.11 and that seemed to have fixed the issue! I'm not sure exactly what the bug here was, but I think its safe to close this for now.

Hmm, I'm happy to re-open this issue, but It might be a different error, i.e. the "Illegal Seek" part seems suspicious.
Also, if you open a new issue it might get more attention :)

Can also repro. Am also on 23.11, but am also using flakes.

I have the same problem. Using NixOS 24.05 and cargo-tauri nixpkgs.
Could not determine the accessibility bus address
DRI driver not from this Mesa build ('23.1.9' vs '23.3.5')
failed to bind extensions
DRI driver not from this Mesa build ('23.1.9' vs '23.3.5')
failed to bind extensions
DRI driver not from this Mesa build ('23.1.9' vs '23.3.5')
failed to bind extensions
Failed to create GBM device for render device: /dev/dri/renderD128: Illegal seek
DRI driver not from this Mesa build ('23.1.9' vs '23.3.5')
failed to bind extensions
DRI driver not from this Mesa build ('23.1.9' vs '23.3.5')
failed to bind extensions
DRI driver not from this Mesa build ('23.1.9' vs '23.3.5')
failed to bind extensions
Failed to create GBM device for render device: /dev/dri/renderD128: No such file or directory
Failed to get GBM device

Alright looks like this is still a reoccuring issue. I will reopen.

I am also having this issue, using a Nix flake on NixOS (nixpkgs-unstable).  My GPU is an Intel integrated.
Output:
❯ yarn tauri dev
yarn run v1.22.19
$ /home/jordan/scm/streambrah-desktop/node_modules/.bin/tauri dev
     Running BeforeDevCommand (`npm run dev`)

><EMAIL_ADDRESS>dev
> next dev

   ▲ Next.js 14.1.0
   - Local:        http://localhost:3000

 ✓ Ready in 1506ms
        Info Watching /home/jordan/scm/my-app/src-tauri for changes...
    Finished dev [unoptimized + debuginfo] target(s) in 0.22s
DRI driver not from this Mesa build ('24.0.1' vs '24.0.2')
failed to bind extensions
DRI driver not from this Mesa build ('24.0.1' vs '24.0.2')
failed to bind extensions
DRI driver not from this Mesa build ('24.0.1' vs '24.0.2')
failed to bind extensions
Failed to create GBM device for render device: /dev/dri/renderD128: Illegal seek

It seems like this issue is related to flakes. Is anyone here not using flakes?

Did a nix channel update and I have started seeing this error again. So I stumbled on this issue but then played around and found the following worked for me:
It went away these are the only steps I took:
1) Re-build flake.lock
I don't know if this had anything to do with it but this is the only lock file I turfed.
rm flake.lock

And then enter and exit the folder so the flake gets picked up by direnv and gets rebuilt
This wasn't enough as development was still giving me the same error. Maybe it did something though I am not sure
2) Nuke all things in the repo
I am using git so I figured I would nuke all the caches:
Making sure I am in my repo (this leaves my .git folder intact):
rm -rf *
git reset --hard HEAD
pnpm install
pnpm tauri build
pnpm tauri dev

My flake:
# From https://tauri.app/v1/guides/getting-started/prerequisites
{
  inputs = {
    nixpkgs.url = "github:NixOS/nixpkgs/nixos-unstable";
    flake-utils.url = "github:numtide/flake-utils";
    rust-overlay.url = "github:oxalica/rust-overlay";
  };

  outputs = { self, nixpkgs, flake-utils, rust-overlay }:
    flake-utils.lib.eachDefaultSystem (system:
      let
        overlays = [ (import rust-overlay) ];

        pkgs = import nixpkgs {
          inherit system overlays;
        };

        libraries = with pkgs;[
          webkitgtk
          gtk3
          cairo
          gdk-pixbuf
          glib
          libayatana-appindicator
          dbus
          openssl_3
          librsvg
        ];

        packages = with pkgs; [
          curl
          sqlite
          wget
          pkg-config
          dbus
          openssl_3
          glib
          gtk3
          libsoup
          webkitgtk
          librsvg
          tor
          libappindicator-gtk3
          rust-bin.stable."1.76.0".default
          rust-analyzer
          sea-orm-cli
          sqlx-cli
          jq
        ];
      in
      {
        devShell = pkgs.mkShell {
          buildInputs = packages;

          shellHook =
            ''
              export LD_LIBRARY_PATH=${pkgs.lib.makeLibraryPath libraries}:$LD_LIBRARY_PATH
            '';
        };
      });
}

Tried the same steps (except that I'm using vanilla js) but I got the same error.

Also tried the same steps.
Interestingly, I'm getting this error with plain rust, libadwaita, and libgtk4. I think this might be an upstream issue.

Same issue for me using NixOs 23.11 and with a flake that is very similar to the one that ryardley presented.
I was looking to just learn about Tauri for the first time... Is there perhaps an older version that works with NixOs 23.11?

It also happens on Fedora 39 with KDE. It works when running through tauri dev but once I build  it with tauri build , the app image  behaves the same as shown above.
[✔] Environment
    - OS: Fedora 39 X64
    ✔ webkit2gtk-4.0: 2.44.0
    ✔ rsvg2: 2.57.1
    ✔ rustc: 1.73.0 (cc66ad468 2023-10-03)
    ✔ cargo: 1.73.0 (9c4383fb5 2023-08-26)
    ✔ rustup: 1.26.0 (5af9b9484 2023-04-05)
    ✔ Rust toolchain: stable-x86_64-unknown-linux-gnu (default)
    - node: 21.0.0
    - npm: 10.2.0

[-] Packages
    - tauri [RUST]: 1.6.1
    - tauri-build [RUST]: 1.5.1
    - wry [RUST]: 0.24.7
    - tao [RUST]: 0.16.7
    - @tauri-apps/api [NPM]: 1.5.3
    - @tauri-apps/cli [NPM]: 1.5.11

[-] App
    - build-type: bundle
    - CSP: unset
    - distDir: ../dist
    - devPath: http://localhost:1420/
    - framework: React
    - bundler: Vite

I have the same issue and WEBKIT_DISABLE_COMPOSITING_MODE=1 fixed it for me (without any other actions).

I got the same problems and fixed them when using this flake.nix
I also set WEBKIT_DISABLE_COMPOSITING_MODE=1, but I don't know if that was necessary.
There are most likely some unnecessary parts in this flake.nix, so feel free to cut some things out.
inputs = {
    nixpkgs.url = "nixpkgs";
    flake-utils.url = "github:numtide/flake-utils";
    rust-overlay.url = "github:oxalica/rust-overlay";
  };

  outputs = { self, nixpkgs, rust-overlay, flake-utils }:
    flake-utils.lib.eachDefaultSystem (system:
      let
        overlays = [ (import rust-overlay) ];
        pkgs = import nixpkgs {
          inherit system overlays;
        };

        libraries = with pkgs;[
          webkitgtk
          webkitgtk_4_1
          gtk3
          cairo
          gdk-pixbuf
          glib
          dbus
          openssl_3
          librsvg
          libsoup
          xdo
          xdotool
        ];

        packages = with pkgs; [
          (rust-bin.selectLatestNightlyWith (toolchain: toolchain.default.override {
            extensions = [ "rust-src" "rust-analyzer" ];
            targets = [ "wasm32-unknown-unknown" ];
          }))
          curl
          wget
          pkg-config
          dbus
          openssl_3
          glib
          gtk3
          libsoup
          webkitgtk
          webkitgtk_4_1
          librsvg
          xdo
          xdotool
        ];
      in
      {
        devShell = pkgs.mkShell {
          buildInputs = packages;

          shellHook =
            ''
              export LD_LIBRARY_PATH=${pkgs.lib.makeLibraryPath libraries}:$LD_LIBRARY_PATH
              export XDG_DATA_DIRS=${pkgs.gsettings-desktop-schemas}/share/gsettings-schemas/${pkgs.gsettings-desktop-schemas.name}:${pkgs.gtk3}/share/gsettings-schemas/${pkgs.gtk3.name}:$XDG_DATA_DIRS
            '';
        };
      });
}

Setting WEBKIT_DISABLE_COMPOSITING_MODE=1 also fixed it for me. Here is a short snippet to create a wrapped output binary:
wrapProgram $out/bin/${name} --prefix PATH : ${pkgs.glib}/bin --set WEBKIT_DISABLE_COMPOSITING_MODE 1

same issue here.
i'm not 100pct sure but it seems like a nix issue. nix link tauri product to a different version of some library with the system, maybe compositor or X compositing library, the protocol may vary and thus built app cannot render web page on screen.
i set nixpkgs reference by

nix-channel --remove nixpkgs # and any other channels
nixos configuration:

environment.etc."channels/nixpkgs".source = nixpkgs.outPath;
environment.etc."channels/nixpkgs-unstable" = lib.mkIf (nixpkgs-unstable != null) { source = nixpkgs-unstable.outPath; };

nix.nixPath = [ "nixos=/etc/channels/nixpkgs" "nixpkgs=/etc/channels/nixpkgs" "nixpkgs-unstable=/etc/channels/nixpkgs-unstable" ];

it replaced nix channel used before. and force nixpkgs to be synced with nixos flake
then i build tauri by use default.nix, without flake which is previously hard to keep sync with system. if you set nix.nixPath like above, use /etc/channels/nixpkgs as flake inputs
# mostly copied from https://github.com/NixOS/nixpkgs/blob/ab3fc0538d2012d5da74fb6a28c78f2c37831998/pkgs/by-name/po/pot/package.nix

# first line changed to build default.nix out of nixpkgs tree
# you can also nix-build --expr '(import <nixpkgs> {}).callPackage ./default.nix {}'
{ pkgs ? import <nixpkgs> {}, ... }: pkgs.callPackage ({ lib
, stdenv
, stdenvNoCC
, rustPlatform
, fetchFromGitHub
, wrapGAppsHook
, cargo
, rustc
, cargo-tauri
, pkg-config
, nodePackages
, esbuild
, buildGoModule
, jq
, moreutils
, libayatana-appindicator
, gtk3
, webkitgtk
, libsoup
, openssl
, xdotool
, cacert
}:

stdenv.mkDerivation rec {
  pname = "my-brand-new-tauri-app";
  version = "0.0.0";

  # this ensures that source files lines in /nix/store/[HASH]-source directory, which makes unpackPhase copy source files to source sub directory, and let you use sourceRoot = "source/src-tauri"
  src = lib.cleanSourceWith {
    src = ./.;
  };

  sourceRoot = "source/src-tauri";

  postPatch = ''
    substituteInPlace $cargoDepsCopy/libappindicator-sys-*/src/lib.rs \
      --replace "libayatana-appindicator3.so.1" "${libayatana-appindicator}/lib/libayatana-appindicator3.so.1"
  '';

  pnpm-deps = stdenvNoCC.mkDerivation {
    pname = "${pname}-pnpm-deps";
    inherit src version;

    nativeBuildInputs = [
      jq
      moreutils
      nodePackages.pnpm
      cacert
    ];

    installPhase = ''
      export HOME=$(mktemp -d)
      pnpm config set store-dir $out
      # use --ignore-script and --no-optional to avoid downloading binaries
      # use --frozen-lockfile to avoid checking git deps
      pnpm install --frozen-lockfile --no-optional --ignore-script

      # Remove timestamp and sort the json files
      rm -rf $out/v3/tmp
      for f in $(find $out -name "*.json"); do
        sed -i -E -e 's/"checkedAt":[0-9]+,//g' $f
        jq --sort-keys . $f | sponge $f
      done
    '';

    dontFixup = true;
    outputHashMode = "recursive";
    outputHash = "sha256-6CxFm4m3WphdRgU+O8qUHgb+ntdmLrP3zMdJvEnFZcg=";
  };

  # pot uses a seperate Cargo.lock file, i changed it to the one in the source tree
  cargoDeps = rustPlatform.importCargoLock {
    lockFile = ./src-tauri/Cargo.lock;
    outputHashes = {
      # All other crates in the same workspace reuse this hash.
      #"tauri-plugin-autostart-0.0.0" = "sha256-/uxaSBp+N1VjjSiwf6NwNnSH02Vk6gQZ/CzO+AyEI7o=";
    };
  };

  nativeBuildInputs = [
    rustPlatform.cargoSetupHook
    cargo
    rustc
    cargo-tauri
    wrapGAppsHook
    nodePackages.pnpm
    pkg-config
  ];

  buildInputs = [
    gtk3
    libsoup
    libayatana-appindicator
    openssl
    webkitgtk
    xdotool
  ];

  # no idea why this does not work
  #ESBUILD_BINARY_PATH = "${esbuild}/bin/esbuild";
  ESBUILD_BINARY_PATH = "${lib.getExe (esbuild.override {
    buildGoModule = args: buildGoModule (args // rec {
      version = "0.18.20";
      src = fetchFromGitHub {
        owner = "evanw";
        repo = "esbuild";
        rev = "v${version}";
        hash = "sha256-mED3h+mY+4H465m02ewFK/BgA1i/PQ+ksUNxBlgpUoI=";
      };
      vendorHash = "sha256-+BfxCyg0KkDQpHt/wycy/8CTG6YBA/VJvJFhhzUnSiQ=";
    });
  })}";

  preBuild = ''
    export HOME=$(mktemp -d)
    pnpm config set store-dir ${pnpm-deps}
    chmod +w ..
    pnpm install --offline --frozen-lockfile --no-optional --ignore-script
    chmod -R +w ../node_modules
    pnpm rebuild
    # Use cargo-tauri from nixpkgs instead of pnpm tauri from npm
    cargo tauri build -b deb
  '';

  preInstall = ''
    mv target/release/bundle/deb/*/data/usr/ $out
  '';
}) {}

i guess that's why most system freeze the package versions.

For everybody using flakes:

Make sure that the version of nixpkgs being used in the flake.lock matches the one being used by the system.
If you are using oxalica/rust-overlay, make sure that inputs.nixpkgs.follows is set correctly!

inputs = {
    ...
    rust-overlay = {
      url = "github:oxalica/rust-overlay";
      inputs.nixpkgs.follows = "nixpkgs";
    };
};

Error produced on Fedora 41, Kde plasma 6.1(beta), wayland on nvidia.
logs:
DRM kernel driver 'nvidia-drm' in use. NVK requires nouveau. ```

followed by:

``` ** (test_package:12569): WARNING **: 12:16:07.668: webkit_settings_set_enable_offline_web_application_cache is deprecated and does nothing.
Failed to get GBM device ```

``` Failed to get GBM devide ``` occurs every time you do something on the window (cursor move, click etc).
How ever, if you go to your web browser view on http://localhost:1420/ , you won't see any errors.
So, its most likely a rendering issue on the frontend application.

Have you tried to install the nvidia nouveau driver?

This comes up for me when I bump the nix mesa.drivers in my opengl settings.
My hypothesis is that it literally is just a version mismatch between the system mesa and one that (a) tauri is using or (b) tauri is expecting the APIs for/from.
I'm pretty sure that WEBKIT_DISABLE_COMPOSITING_MODE env var would disable hardware acceleration which would also support this hypothesis.
So long story short, if we knew where this mesa info inside tauri was coming from, we could override the derivation, no? :thinking:

Okay so after letting webkitgtk compile for what felt like foreverrrr that did seem to pay off :sweat_smile:
My devshell for the tauri app now forces webkitgtk to use the same unstable.mesa version as my system and I no longer get the version mismatch or any other of the errors mentioned above.
(webkitgtk.overrideAttrs (old: {
  buildInputs = [ unstablePkgs.mesa ] ++ old.buildInputs;
}))

Is there any official fix from tauri devs ? or workaround ? @martinfrances107 @tweidinger @chippers
Should we report upstream this issue to Mesa devs ?
I understand that @ndom91 fix works well on NixOS and that's pretty cool to have that possible but an official fix should be made for all Linux users at some point.
I believe this issue is not Nix/NixOS specific but happens on all Linux distros.

I'm running into this same issue on Arch Linux, and manually setting WEBKIT_DISABLE_COMPOSITING_MODE fixed it for me, although I still see the following errors when I run the AppImage build artifact that cargo tauri build emits:
 WARNING **: 20:47:45.121: webkit_settings_set_enable_offline_web_application_cache is deprecated and does nothing.
DRI driver not from this Mesa build ('24.1.2' vs '24.1.2-arch1.1')
failed to bind extensions
DRI driver not from this Mesa build ('24.1.2' vs '24.1.2-arch1.1')
failed to bind extensions
DRI driver not from this Mesa build ('24.1.2' vs '24.1.2-arch1.1')
failed to bind extensions
Failed to create GBM device for render device: /dev/dri/renderD128: Illegal seek

Just FYI @neunenak by disabling compositing mode I believe you're just going back to software rendering. Which does work apparently, right, but you're missing out on a lot of performance..


Vite SSG build error in the new update

[vite-ssg] An internal error occurred.
[vite-ssg] Please report an issue, if none already exists: https://github.com/antfu/vite-ssg/issues
(node:108607) UnhandledPromiseRejectionWarning: SyntaxError: Unexpected token '?'
at Loader.moduleStrategy (internal/modules/esm/translators.js:133:18)
(node:108607) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag --unhandled-rejections=strict (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 2)
(node:108607) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

What's your Node version?

v12.22.5

see https://github.com/antfu/vite-ssg#install, required node 14+

see https://github.com/antfu/vite-ssg#install, required node 14+

Thanks that worked completely fine...


Tor Browser Not Working

Not much else to say really.
Acer c720 chromebook.

Not much else to say really.

Yes there is a lot more to say ,-)
Output of croutonversion, where are you downloading tor browser from, how are you starting it...


Tabs vs spacing in eslint causing compiler errors

Running npm start in main causes these errors
Failed to compile.

[eslint]
src/App.jsx
  Line 7:1:   Expected indentation of 1 tab but found 2 spaces   indent
  Line 7:28:  Unexpected trailing comma                          comma-dangle
  Line 11:1:  Expected indentation of 1 tab but found 2 spaces   indent
  Line 12:1:  Expected indentation of 2 tabs but found 4 spaces  indent
  Line 13:1:  Expected indentation of 3 tabs but found 6 spaces  indent
  Line 14:1:  Expected indentation of 4 tabs but found 8 spaces  indent
  Line 15:1:  Expected indentation of 3 tabs but found 6 spaces  indent
  Line 16:1:  Expected indentation of 3 tabs but found 6 spaces  indent
  Line 17:1:  Expected indentation of 4 tabs but found 8 spaces  indent
  Line 18:1:  Expected indentation of 4 tabs but found 8 spaces  indent
  Line 19:1:  Expected indentation of 4 tabs but found 8 spaces  indent
  Line 20:1:  Expected indentation of 3 tabs but found 6 spaces  indent
[...]

I don't think we should allow tabs and spaces simultaneously, and should not allow tab characters at all.
It is generally preferred to insert space characters, since they are more consistent across editors than tab characters, among other reasons. I personally have VSCode set to insert spaces to indent with the tab key.

Fixed.


Added bootstrap templates for CentOS. They still need vetting. Fixed …

…replaced use of sed for envsubst which is safer and designed as a templating method. Functionalized the generate script for better readability. Added functionality for machine.yaml to actually be processed so that OS_TYPE and KUBELET_VERSION are injected. Fixes some bugs. Created common_functions.template which will allow easier editing of templates vs having to potentially fix code in several templates.

There are a few things to note about this commit:

Though there is now a common functions template which gets injected in the new centos templates, it is not yet used in the other templates, yet.
The node bootstrap aws template is nothing more than a copy of the master template for now.
The steps currently scripted for the AWS centos implementation are not 100% correct yet. It's close, but not quite there yet.

https://samsung-cnct.atlassian.net/browse/CMS-391


Adding the modified yara-python to pip

The yara-python clone and compile steps here are temporarily necessary because we must point directly to our modified version of a Yara branch which includes our DEX Yara module. This step is nessecary until (if?) the original maintainers of Yara merge our module into the master branch.

How about adding it to pip as a separate module?

This is definitely an option - however, I do not think it is the correct way to handle this. I believe getting this merged into the actual master branch is the correct way to solve this.
Otherwise, we need to create and maintain our own pip module - where compiling it from source is just as acceptable.


fix chart deploy failure if rbac disabled.

PR: https://github.com/istio/istio/pull/6139 doesn't fix: https://github.com/istio/old_issues_repo/issues/386 rbac issues completely, still the get error from
clean old ca hook job:
  Warning  FailedCreate  15s (x8 over 2m)  job-controller  Error creating: pods "istio-cleanup-old-ca-" is forbidden: error looking up service account istio-system/istio-cleanup-old-ca-service-account: serviceaccount "istio-cleanup-old-ca-service-account" not found

and mixer post install hook job:
Error from server (Forbidden): error when retrieving current configuration of:
&{0xc42020dc80 0xc4210fb420 istio-system istio-telemetry /tmp/mixer/custom-resources.yaml 0xc4210fe290 0xc4210fe290  false}
from server for: "/tmp/mixer/custom-resources.yaml": destinationrules.networking.istio.io "istio-telemetry" is forbidden: User "system:serviceaccount:istio-system:istio-mixer-post-install-account" cannot get destinationrules.networking.istio.io in the namespace "istio-system"

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: morvencao
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approver: ostromart
Assign the PR to them by writing /assign @ostromart in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

install/OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@morvencao: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-e2e.sh
764a5cab31b317016978c1b684f7ddcb1c19e15a
link
/test istio-pilot-e2e

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@morvencao: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-e2e.sh
764a5cab31b317016978c1b684f7ddcb1c19e15a
link
/test istio-pilot-e2e

prow/e2e-bookInfoTests.sh
764a5cab31b317016978c1b684f7ddcb1c19e15a
link
/test e2e-bookInfo

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: gyliu513, morvencao
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

install/OWNERS [gyliu513]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

/retest


Error on load

[Error  : Unity Log] NullReferenceException: Object reference not set to an instance of an object
Stack trace:
MonoMod.Utils.ReflectionHelper.GetRuntimeHashedFullName (Mono.Cecil.AssemblyNameReference asm) (at <6733e342b5b549bba815373898724469>:IL_0017)
MonoMod.Utils.ReflectionHelper._ResolveReflection (Mono.Cecil.MemberReference mref, System.Reflection.Module[] modules) (at <6733e342b5b549bba815373898724469>:IL_00AF)
MonoMod.Utils.ReflectionHelper.ResolveReflection (Mono.Cecil.TypeReference mref) (at <6733e342b5b549bba815373898724469>:IL_0000)
MonoMod.Utils._DMDEmit+<>c__DisplayClass5_0.<Generate>b__0 (Mono.Cecil.Cil.VariableDefinition var) (at <6733e342b5b549bba815373898724469>:IL_000C)
System.Linq.Enumerable+SelectIListIterator`2[TSource,TResult].ToArray () (at <dab7f68612224ba3ae40f651d44f9d4c>:IL_0034)
System.Linq.Enumerable.ToArray[TSource] (System.Collections.Generic.IEnumerable`1[T] source) (at <dab7f68612224ba3ae40f651d44f9d4c>:IL_001F)
MonoMod.Utils._DMDEmit.Generate (MonoMod.Utils.DynamicMethodDefinition dmd, System.Reflection.MethodBase _mb, System.Reflection.Emit.ILGenerator il) (at <6733e342b5b549bba815373898724469>:IL_015C)
MonoMod.Utils.DMDEmitDynamicMethodGenerator._Generate (MonoMod.Utils.DynamicMethodDefinition dmd, System.Object context) (at <6733e342b5b549bba815373898724469>:IL_0332)
MonoMod.Utils.DMDGenerator`1[TSelf].Generate (MonoMod.Utils.DynamicMethodDefinition dmd, System.Object context) (at <6733e342b5b549bba815373898724469>:IL_0013)
MonoMod.Utils.DynamicMethodDefinition.Generate (System.Object context) (at <6733e342b5b549bba815373898724469>:IL_013A)
MonoMod.Utils.DynamicMethodDefinition.Generate () (at <6733e342b5b549bba815373898724469>:IL_0000)
(wrapper dynamic-method) MonoMod.RuntimeDetour.ILHook+Context.DMD<MonoMod.RuntimeDetour.ILHook+Context::Refresh>(MonoMod.RuntimeDetour.ILHook/Context)
(wrapper dynamic-method) MonoMod.Utils.DynamicMethodDefinition.Trampoline<MonoMod.RuntimeDetour.ILHook+Context::Refresh>?-693053586(object)
HarmonyLib.Internal.RuntimeFixes.StackTraceFixes.OnILChainRefresh (System.Object self) (at <474744d65d8e460fa08cd5fd82b5d65f>:IL_0000)
MonoMod.RuntimeDetour.ILHook.Apply () (at <4e2760c7517c4ea79c633d67e84b319f>:IL_0059)
HarmonyLib.PatchFunctions.ReversePatch (HarmonyLib.HarmonyMethod standin, System.Reflection.MethodBase original, System.Reflection.MethodInfo postTranspiler, System.Reflection.MethodInfo postManipulator) (at <474744d65d8e460fa08cd5fd82b5d65f>:IL_015D)
Rethrow as HarmonyException: IL Compile Error (unknown location)
HarmonyLib.PatchClassProcessor.ReportException (System.Exception exception, System.Reflection.MethodBase original) (at <474744d65d8e460fa08cd5fd82b5d65f>:IL_0045)
HarmonyLib.PatchClassProcessor.Patch () (at <474744d65d8e460fa08cd5fd82b5d65f>:IL_0095)
HarmonyLib.Harmony.PatchAll (System.Type type) (at <474744d65d8e460fa08cd5fd82b5d65f>:IL_0008)
HarmonyLib.Harmony.CreateAndPatchAll (System.Type type, System.String harmonyInstanceId) (at <474744d65d8e460fa08cd5fd82b5d65f>:IL_001E)
Loadstone.Loadstone.Awake () (at <445e04fe67d044aca995cc82fa9519d6>:IL_0091)
UnityEngine.GameObject:AddComponent(Type)
BepInEx.Bootstrap.Chainloader:Start()
UnityEngine.Rendering.HighDefinition.HDRenderPipelineAsset:OnEnable()

Mod list:
BepInEx-BepInExPack-5.4.2100
Hardy-LCMaxSoundsFix-1.1.0
Evaisa-HookGenPatcher-0.0.5
Evaisa-LethalLib-0.14.2
zealsprince-Locker-0.13.1
IntegrityChaos-GraphicsAPI-1.0.0
IntegrityChaos-LCCutscene-1.0.0
IntegrityChaos-Diversity-2.0.3
x753-Peepers-0.9.6
jaspercreations-Scopophobia-1.1.1
NomnomAB-RollingGiant-2.5.2
x753-Mimics-2.4.1
Ozone-Runtime_Netcode_Patcher-0.2.5
readthisifbad-SnatchinBracken-1.4.3
SillySquad-Arachnophilia-1.6.1
Rolevote-The_Fiend-1.0.5
Ccode_lang-SirenHead-1.0.1
SolidStone-ShockwaveDroneEnemy-0.3.0
ShaosilGaming-GeneralImprovements-1.1.11
ShaosilGaming-FlashlightFix-1.1.2
Lordfirespeed-OdinSerializer-2022.11.9
IAmBatby-LethalLevelLoader-1.1.6
xilophor-LethalNetworkAPI-2.1.6
zealsprince-Malfunctions-1.8.2
FlipMods-ReservedItemSlotCore-1.8.17
FlipMods-ReservedFlashlightSlot-1.6.3
FlipMods-ReservedWalkieSlot-1.6.2
Piggy-LC_Office-1.1.5
skidz-PoolRooms-0.1.18
Dantor-Dantors_Mental_Hospital-1.1.1
Alice-ScarletDevilMansion-1.3.2
Badham_Mods-SCPFoundationDungeon-3.0.0
Major_And_Skiz-MoreInteriors-2.5.0
scoopy-Scoopys_Variety_Mod-1.2.0
mrgrm7-LethalCasino-0.4.2
Monkeytype-HideChat-1.0.0
Zduniusz-LBtoKG-1.0.0
x753-More_Suits-1.4.1
qwbarch-BarchLib-1.0.0
Bobbie-NAudio-2.2.2
Bobbie-UniTask-2.5.0
qwbarch-Mirage-1.1.0
xCeezy-LethalEscape-0.8.5
Swaggies-BetterEXP-1.2.2
dopadream-Some_Buyable_Suits_Fix-1.0.3
malco-Lategame_Upgrades-3.3.0
notnotnotswipez-MoreCompany-1.8.1
HGG-JigglePhysicsPlugin-1.1.2
Mhz-MoreHead-1.2.6
LethalAPI-LethalAPI_Terminal-1.0.1
mattymatty-LobbyControl-2.2.6
Rune580-LethalCompany_InputUtils-0.6.3
KlutzyBubbles-BetterEmotes-1.4.5
PotatoCoders-MinimumQuotaFinder-1.1.3
Suskitech-AlwaysHearActiveWalkies-1.4.4
TanmanG-Forest_Giant_Motionsense-1.0.2
Woecust-Immersive_Visor-0.2.1
mrov-WeatherTweaks-0.4.6
Fredolx-MeteoMultiplier-1.1.3
Sigurd-CSync-3.1.1
Evaisa-LethalThings-0.9.4
Scintesto-Monster_Plushies-1.1.2
bigmcnugget-VanillaContentExpansion-0.1.8
Refract-LethalLevelLoaderFixed-1.1.0
Zaggy1024-PathfindingLagFix-1.2.1
NutNutty-SellTracker-1.2.1
veri-ShipWindows-1.3.6
CatsArmy-SpaceSunShine-1.2.1
KawaiiBone-Remnants-1.1.7
mrov-TerminalFormatter-0.0.8
AdiBTW-Loadstone-0.0.1

I'm currently looking into this issue, and it appears that the way the development profile I set up works is behaving differently from a fresh profile. Even with no other mods installed, the same error is happening. I'll try to get a fix out as soon as possible

I've figured out why my dev environment works differently, and you might be able to use the same change as a temporary fix until I can resolve the issue fully. By changing BepInEx.cfg's HarmonyBackend option from auto to cecil, it should work. I'm currently try to make it work on the default backend, but it could take a bit

well i set it to cecil and i am now watching advanced company do something called 'added DMDASM.XXXXXXX.Cecil' thousands and thousands of times and it looks like ill never reach the load screen

but it did do something to the load times even without setting it to cecil..

interesting
I'm guessing that that particular mod just doesn't work with the cecil backend
I'll keep poking around and see if I can figure it out on my end. Also, while level loading might work for the most part, the particular function that's erroring is responsible for spawning in the doors between rooms, so there will likely not be any doors spawning between rooms until I can find a fix

looks like something is defaulting it to generate properly as i've not noticed anything as of yet

perhaps that section of patches isn't being applied? Or maybe Lethal Company handles doors separately from the map generator, although I don't think that it does if my memory serves correctly

Ok! I think I've finally located the root of the issue. It seems to be a potential bug in MonoMod, which lies underneath of BepInEx, and was causing files to not be loaded when they should be. I've created a workaround that seems to resolve the error. I'm uploading the new version the thunderstore now, and the update should go live within 30 minutes to an hour (thunderstore takes a while to actually display updates for some reason)

nice. cheers for the mod. working good so far


Add support proxyprotocol v2

What does this PR do?
This PR adds support for proxyprotocol v2 headers.
The package provides support for proxy protocol v1 (https://github.com/armon/go-proxyproto) is replaced by the package (https://github.com/c0va23/go-proxyprotocol) supporting the analysis of both proxy protocol versions at the same time.
Motivation
Support for proxy protocol v2 need that traefik can be run using AWS NLB.
More

[x] Added/updated tests
[x] Updated documentation

Additional Notes
Package github.com/c0va23/go-proxyprotocol tested manually with HA Proxy (v1 and v2) and on production with AWS NLB.
It PR #4561 migrated on branch v2.0

I updated the package after reviewing and typos. Added more documentation on how to enable proxyprotocol. And made a rebase on the fresh code in the 2.0 branches.

Any chance this PR will be merged?


Default in memory config

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

8 of 9 (88.89%)  changed or added relevant lines in 2 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.5%) to 96.75%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

src/Stock/DataStorage/CsvFileStorage.php
0
1
0.0%

Totals

Change from base Build<PHONE_NUMBER>:
0.5%

Covered Lines:
387

Relevant Lines:
400

💛  - Coveralls


Create literals for assemble models representing primitive wrappers

Description
Fixes # (2217)
Also corrects classId in methods of some assemble models obtained from concrete execution.
How to test
Automated tests
utbot-samples pipeline as a set of regression checks
Manual tests
Scenario from the issue
Self-check list
Check off the item if the statement is true. Hint: [x] is a marked item.
Please do not delete the list or its items.

[x] I've set the proper labels for my PR (at least, for category and component).
[x] PR title and description are clear and intelligible.
[x] I've added enough comments to my code, particularly in hard-to-understand areas.
[x] The functionality I've repaired, changed or added is covered with automated tests.
[] Manual tests have been provided optionally.
[x] The documentation for the functionality I've been working on is up-to-date.

Unfortunately, one two tests for current method fails after these changes:
public class ObjectWithFinalStatic {
    public final static Integer keyValue = 420;

    public int parameterEqualsFinalStatic(Integer key, int value) {
        if (key == keyValue) {
            return value;
        }
        return -420;
    }
}

The reason is that we need the value 420 two times.
When the variable is created, it is ok. When literals are used, standard boxing leads to different wrappers for one constant that are not equal.


[webview_flutter_web] Migration to package:web needed for wasm

Use case
Currently webview_flutter_web uses dart:html, and requires to be updated to be using package:web.
For WASM support, attempting to build to web with webview_flutter would cause it to not build.
Proposal
Finish the migrations for webview_flutter_web to package:web, and the tests for it.
There was already a PR for it a few months ago: https://github.com/flutter/packages/pull/5694 .
And before i found the pr, here is the things that i recently done from the latest commit.
https://github.com/ThomasAunvik/flutter-packages/commit/a799099ab2a0a4ef1436332ef42615080b1036c3
And, it would help if someone knew how to fix the tests, as i don't really know that.
Note: Flutter version 3.22.0 when trying to run the changes causes the app to hang and crash giving a memory out of bounds error, using flutter version (master branch) works: 3.22.0-43.0.pre.6

found duplicate issue https://github.com/flutter/flutter/issues/139749


Pass existing server_side_parameters to session connection wrapper and use to configure SparkSession.

resolves #690
Description
Pass existing server_side_parameters to session connection wrapper and use to configure SparkSession.
Checklist

[x] I have read the contributing guide and understand what's expected of me
[x] I have signed the CLA
[x] I have run this code in development and it appears to resolve the stated issue
[x] This PR includes tests, or tests are not required/relevant for this PR
[x] I have opened an issue to add/update docs, or docs changes are not required/relevant for this PR
[ ] I have run changie new to create a changelog entry

Prefer PR #823 823


Minimum supported node version?

Problem
Mylas 1.1.x minimum supported node version is node >=12
StatusAPI supports node >=10
Because of this we can't update to<EMAIL_ADDRESS>Solutions
Solution 1
Node 10 will reach End-of-life on 2021-04-30
Bump StatusAPI minimum version to >=12
Solution 2
Keep using Mylas version 1.0.7

Current dependabot PR for this dependency #89

Solution 1 is the best longterm solution, adding node engine to package.json


[BUG] Material-UI createTheme does not expose MuiDataGrid

Describe the bug
If one wants to customize the DataGrid via the main theme, Typescript throws an error because MuiDataGrid is not present in the components object of the Theme object. The @mui/x-data-grid docs recommend adding a type augmentation, but since the createTheme that we get is from the refine library and not mui directly, we can't use the augmentation.
As a workaround, setting the object passed to createTheme as any allows us to style the DataGrid, but we lose Typescript for it.
Steps To Reproduce

Create a theme via the @pankod/refine-mui-exposed createTheme
Use the following structure:

components: {
 MuiDataGrid: {
   styleOverrides: {
     cell: {
       borderBottom: "1px solid black !important"
     }
   }
 }
}

Expected behavior
To get Typescript autocomplete for the MuiDataGrid object
Screenshot
No response
Desktop
No response
Mobile
No response
Additional Context
No response

Hi @derTuca, Thanks for the issue. we will look into it immediately 🙏

Removing the ol' node_modules, yarn.lock and removing/readding the type augmentation seems to do the trick, sorry for the noise!
Still, I am left wondering, considering the fact that x-data-grid is part of refine-mui anyways, would it not be a better idea to include this type augmentation from refine's DataGrid export?
I am leaving the issue open just in case the question above is of any interest but you can close it anytime. Thank you for your time!

I'm glad to hear that 🥳
You are right but we couldn't figure out how we can export typeAugmentation from the refine package. We would be very pleased if you would like to open PR 🙏


Separate config into a separate file

Rasa Core's config is stored in a separate "config.json" and not intertwined with the unrelated "package.json". This means we can use volumes in Docker to overwrite the config file with the appropriate values without needing the rest of the package properties.
My current approach has involved building and pushing a straight copy of RASA UI to Docker Hub, and creating a new Dockerfile in a separate repo to setup the configuration for the UI. I've included these lines for setting the config values. This would be unnecessary if the config was in its own file.
FROM recombix/paschmann-rasa-ui:0.2.0

# Add our configuration to the package file.
RUN npm install -g<EMAIL_ADDRESS>RUN json -I -f ./package.json -e 'this.config.rasaserver="http://rasa-core:7000"; this.config.jwtsecret="XXX"; this.config.postgresConnectionString="XXX"'

@saikojosh  With the latest release, rasa-ui supports environment variables for core, nlu and postgres db. Hope this helps.


[TO DISCUSS] Hide the backend.run vs Qiskit Runtime comparison

From @javabster

We should remove /compare
It's not useful enough to warrant it's own page, and I'm still trying to figure out if theres another page we could integrate it into
for now, can you give it the __ treatment? so the file is still there but it's not deployed?

I agree it doesn't belong in Migration guides, but why do you want to hide it before finding a new home? Since the information is still useful and will be lost this way.

See https://github.com/Qiskit/documentation/pull/177 for my proposal for now before this Wednesday deadline, since it sounds like we need to move Migration Guides to the API dropdown by then. Then we can find a better home for this file after the release.

We decided to instead consolidate compare into the Runtime migration guides. @beckykd is working on that in a separate PR.


mapviz: 2.2.0-1 in 'humble/distribution.yaml' [bloom]

Increasing version of package(s) in repository mapviz to 2.2.0-1:

upstream repository: https://github.com/swri-robotics/mapviz.git
release repository: https://github.com/ros2-gbp/mapviz-release.git
distro file: humble/distribution.yaml
bloom version: 0.11.2
previous version for package: null

Holding for the upcoming Humble sync.


Allow sync of local paths

Allow sync of local paths …This patch removes the requirement for a REMOTE_HOST argument. If the host isn't specified, then two paths on the local system are implied. This is assumed to work very well since this is how the test (rake) system works.
Partially implements #40

This has been merged into the master branch and released in https://github.com/sickill/bitpocket/releases/tag/v0.2


az ad group: Group names with '&' in them get split at the point where the '&' appears

Describe the bug
Command Name
az ad group show --group "Hello_&_World" --query id --output tsv
Errors:
No group matches the name of 'Hello_'

To Reproduce:
Steps to reproduce the behavior. Note that argument values have been redacted, as they may contain sensitive information.

Have an AAD group with an '&' in the name
az ad group show --group {} --query id --output tsv

Expected Behavior
az ad command can handle group names that have "&" in them. Previously had to use a workaround with --% though with 2.40 this is apparently no longer needed https://github.com/Azure/azure-cli/blob/dev/doc/quoting-issues-with-powershell.md and was working fine until 2.41
Environment Summary
Windows-10-10.0.19042-SP0
Python 3.10.5
Installer: MSI

azure-cli 2.41.0

Extensions:
azure-devops 0.17.0

Dependencies:
msal 1.20.0b1
azure-mgmt-resource 21.1.0b1

Additional Context

@jiasli for awareness

Have put the --% workaround back into our scripts which seems to have solved it on 2.41
az --% ad group show --group "Hello_&_World" --query id --output tsv

We reverted #23514 in #24015. az is now still az.cmd.


Upgraded paho library to 1.2.0

Upgraded paho library to 1.2.0.
I have tested AWS SDK with new version of paho and it seems to be working: messages are getting published via WebSockets and TCP connections, Shadows are getting updated etc etc.
Signed-off-by: Rehan Shaukat<EMAIL_ADDRESS>

Thank you for your submission. A change like this will have to go through our internal testing cycle before it can be released. It may take a while before we're able to take action on this.
Is there a particular fix / feature of Paho 1.2 you require?

I'm waiting for Paho 1.1.1 which includes a fix to NullPointerException in receiveHandshakeResponse issue.
The fix is in Pull request Adding connection checks to WebSocket Tests which is included in version 1.1.1 (https://github.com/eclipse/paho.mqtt.java/compare/v1.1.0...v1.1.1).

Is it OK to change the Paho version to 1.1.1? are there any known issues with using this version with aws-iot-device-sdk-java?
What is the schedule for releasing a new version of aws-iot-device-sdk-java? The last version was released a year ago...

Is there a particular fix / feature of Paho 1.2 you require?
This fixed an issue for when connecting to IoT over websockets. We had issues with IoT connection dying and not able to recover.

Is this of any concern... https://github.com/eclipse/paho.mqtt.java/issues/402
I am hitting this issue with 1.2.0

This issue might be also of concern if you consider upgrading to 1.2.0
eclipse/paho.mqtt.java#345

This upgrade caused issue https://github.com/aws/aws-iot-device-sdk-java/issues/116


don't specify fixed, too old Vespa version

I confirm that this contribution is made under the terms of the license found in the root directory of this repository's source tree and that I have the authority necessary to make this contribution on behalf of its copyright owner.

We should ensure this example is tested in CI too


Make "Compiling" section easier to execute

There is a section in the Makefile to do that instead of execute manually a script.

Yes, it could make sense!
But, in my opinion, embedded scripts have the inconvenient that if the scripts is updated, sometimes people don't remember to update documentation too...
There are cases where there is no other option that embedded an script, but in this case as exists a Makefile, it encapsulates it and if it is modified the user does not care :)
Despite this,I can adapt it to what you decide!

The main point of all of this work, is that this should not be executed from this repository anymore, but instead from your own internal infrastructure repository. That's why intentionally the script is done extremely simple.
I'd prefer if the script stays in the foreground and make generate-raw is just a helper in a hint.

Great! I have changed that @brancz :)

Yeah! I agree with you @mxinden! I have already changed that

@luarx sorry to bother you once more here. Could you rebase your changes onto current master. Our CI system doesn't do this before testing, thereby it fails with diffs in the generation step.

Yes! There is no problem, I have already done it :)

Thanks @luarx.


Document any implicit filtering

Add new rule 226 "Document any implicit filtering" (#428).

:+1:

:+1:

:+1:


passing arrays as function arguments

The obvious translation of
void f(int x[10]);

(array 10 int) @-> returning void

fails with an Unsupported exception.  I can kind of see why - a pointer is really passed, not an array as described.  Is this something that is fixable in Ctypes?

It would be useful to be able to pass arrays.  I think it's probably possible to fix (and similarly for bigarrays).


body-parser errors are not handled as HttpErrors

Steps to reproduce:

use createServer with default server.jsonParser to start the server
send request with invalid JSON. e.g.:

curl --location 'http://localhost:{{port}}/whatever-path' \
--header 'Content-Type: application/json' \
--data '{
    a: "b"
}'

Actual behaviour:
The server responds with a 500 error
Expected behaviour
The server responds with a 400 error

One possible workaround is to pass a custom jsonParser:
import { isHttpError } from "http-errors";

...
const rawJsonParser = express.json();
const jsonParser: typeof rawJsonParser = (request, response, next) => {
  rawJsonParser(request, response, (error) => {
    if (error instanceof Error) {
      response.statusCode = isHttpError(error)
        ? error.status
        : getStatusCodeFromError(error);
      response.end(getMessageFromError(error));
    } else {
      next(error);
    }
  });
};
...
createServer(createConfig({
...
server: {
  jsonParser,
  ...
}
}), routing)

Note that code above will not work without the isHttpError check, because there is no such check inside getStatusCodeFromError. @RobinTail, Is it intentional?

Hello @McMerph

@RobinTail, Is it intentional?

Let me check... I'm sure that I actually have a test for this case...

I found that test. Now I need to recall why it's 500.
Please stand by :)
https://github.com/RobinTail/express-zod-api/blob/d7bf42feecfd50f58af798bbfd66a6e014c89cfe/tests/system/system.spec.ts#L350

The test is 2 years old and is from the version 0.1.2.
I believe it's a bug.

@McMerph ,
this is a very long-living issue.
Thank you very much for finding it.
🏅

🚀 The fix released in v10.1.2


cmd/compile: "cannot use _ as value" compile error for blank identifier variable declaration with non-empty composite literal

What version of Go are you using (go version)?
$ go version
go version go1.8.3 darwin/amd64

What operating system and processor architecture are you using (go env)?

$ go env
GOARCH="amd64"
GOBIN=""
GOEXE=""
GOHOSTARCH="amd64"
GOHOSTOS="darwin"
GOOS="darwin"
GOPATH="/Users/Dmitri/Dropbox/Work/2013/GoLanding:/Users/Dmitri/Dropbox/Work/2013/GoLand"
GORACE=""
GOROOT="/usr/local/go"
GOTOOLDIR="/usr/local/go/pkg/tool/darwin_amd64"
GCCGO="gccgo"
CC="clang"
GOGCCFLAGS="-fPIC -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=/var/folders/tw/kgz4v2kn4n7d7ryg5k_z3dk40000gn/T/go-build536199591=/tmp/go-build -gno-record-gcc-switches -fno-common"
CXX="clang++"
CGO_ENABLED="1"
PKG_CONFIG="pkg-config"
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"

What did you do?
I was writing some new Go code, and wanted to assign an unused struct to the blank identifier to prevent a compiler error.
package main

func main() {
	_ = int(5)               // ok
	_ = struct{ int }{}      // ok
	_ = struct{ int }{5}     // ok
	var _ = int(5)           // ok
	var _ = struct{ int }{}  // ok
	var _ = struct{ int }{5} // cannot use _ as value
}

https://play.golang.org/p/KZlFqfhE1z
What did you expect to see?
No compile errors. (Probably? I'm not sure if this is intended behavior or not, but it doesn't seem to be.)
What did you see instead?
I got "cannot use _ as value" compile error.
Additional Notes
I tried gc compiler from Go 1.4.3, and got the same error.
go/types doesn't seem to give an error for that code.

Looks like a duplicate of https://github.com/golang/go/issues/15481 and in particular this permutation https://github.com/golang/go/issues/15481#issuecomment-262472312.

Thanks, that does look the same. Closing as duplicate.
I'll copy my snippet to that issue, since I don't see a case of struct literals mentioned there.


Please keep the HTML option

I see in the latest release that the html option is deprecated.
Please do not remove the html option. HTML and text are different data types, and being able to specify the data types used can make for more robust and explicit code. I only use the hyphenate library with text.
Thank you.

Same here. I already notified @ytiurin about this. He is currently figuring out a solution.

Hi guys,
I was planning to make text processor skip all html tags by default and deprecate all html-related configuration
I added the Migration section to the readme file, please check
If you really need to hyphenate html tags (when <blockquote> results to <block-quote> ), I can leave the html option available in further versions, just tell me if you use hyphenateHTML and hyphenateHTMLSync functions - those are still available, it's just that hyphenate function now have the exact same behavior

@ytiurin, we do not use hyphenateHTML or hyphenateHTMLSync. I'm fine with using createHyphenate(patterns, { html: false }) as an alternative to hyphenate, since hyphenate now behaves the same as hyphenateHTML.
As you describe it, I guess you would say that we do need to hyphenate HTML tags. I would instead describe it that text and HTML are different data types: if I'm processing text, then < and > have no special meaning, and <blockquote> should be hyphenated the same as "blockquote" or [blockquote], so having code that mixes up data types by treating text as HTML invites bugs.

I would instead describe it that text and HTML are different data types: if I'm processing text, then < and > have no special meaning, and <blockquote> should be hyphenated the same as "blockquote" or [blockquote].

:point_up: This is how I see it too. I find it odd that this library is skipping anything as I feel that should not be part of its functionality. If somebody wants to skip HTML or whatever one has to do it oneself somehow. But I guess if it is a scenario that a lot of users need then maybe it does make sense to skip HTML tags out of convenience.
@ytiurin we use hyphenateSync in our application.


apps: migrate to SPDX identifier

Summary
Most tools used for compliance and SBOM generation use SPDX identifiers This change brings us a step closer to an easy SBOM generation.
Impact
SBOM
Testing
CI

[Experimental Bot, please feedback here]
No, this PR description does not meet the NuttX requirements.  While it attempts to follow the structure, it lacks crucial details.  Here's why:

Summary:  While it states the why, it's vague. What tools? What kind of SPDX identifiers?  It completely omits what is changing, how the change works, and any related issue references.  Example: "This change adds SPDX license identifiers to the source files within the core OS directory (e.g., sched/, drivers/). This will allow tools like [tool name] to generate a compliant SBOM.  This addresses issue #[issue number]."

Impact: Simply stating "SBOM" isn't helpful.  You need to address all impact points with "YES/NO" and descriptions where necessary.  For example,  "Impact on documentation: YES - The README will be updated to explain how to generate an SBOM."  Even if the answer is "NO", state it explicitly.

Testing:  "CI" isn't sufficient. List the specific build hosts and targets tested.  Provide actual log snippets demonstrating the change's effect, not just "your testing logs here".  Show the absence of SPDX identifiers before and their presence after the change.  Example:

Build Host(s): Linux (Ubuntu 22.04), x86_64, GCC 11.2
Target(s): qemu-sim:default

Testing logs before change (excerpt from sched/sched.c):
/* No SPDX identifier present */

Testing logs after change (excerpt from sched/sched.c):
// SPDX-License-Identifier: Apache-2.0

In short, the PR description needs to be significantly more detailed and explicit to meet the NuttX requirements.  It should provide specific information about the changes, their impact, and clear evidence of testing.

@xiaoxiang781216 please ignore can nxerrors

build errors come from previously merged pr? o_O

@xiaoxiang781216 ready to go


Caching shortcodes

Is it possible to cache shortcodes?
Some shortcodes are loading 150ms

@vedmant I didn't add universal cache for shortcodes as they can be too different, can be nested and depend on many things. If you need to cache some specific shortcode you just use Cache::remember function:
<?php
use Vedmant\LaravelShortcodes\Shortcode;
use Cache;

class MyShortcode extends Shortcode
{
    /**
     * @var string Shortcode description
     */
    public $description = 'Some my shortcode';

    /**
     * @var array Shortcode attributes with default values
     */
    public $attributes = [
        'class' => [
            'default'     => '',
            'description' => 'Class name',
            'sample'      => 'some-class',
        ],
    ];

    /**
     * Render shortcode
     *
     * @param string $content
     * @return string
     */
    public function render($content)
    {
        $atts = $this->atts();

        $seconds = 3600;
        return Cache::remember('my-shortcode-cache-key', $seconds, function ()  use ($atts) {
            // Some database code if needed here

            return $this->view('shortcodes.my-shortcode', compact('atts'));
        });
    }
}


Refactor of Language Middleware and implemented https redirect middleware on prod.

I've refactored the current Language middleware and extracted the Https redirection to its own middleware.
Both middlewares have passing tests included.
The existing tests are renamed in StudlyCaps specified in (PSR-1)[https://github.com/php-fig/fig-standards/blob/master/accepted/PSR-1-basic-coding-standard.md#1-overview]

Class names MUST be declared in StudlyCaps.

Thanks! I'll let @Tjoosten give his blessing before merging this :)

I will look at this tonight. I've no spare time now @pietercolpaert.
@SaschaDens Thx for the refactoring. I appreciate your effort.

Quick update: @pietercolpaert This looks awesome to me. So my word is. merge === 'yes' :p


[imgui] Update to 1.89.7

Update imgui port from 1.89.6 to 1.89.7 : https://github.com/ocornut/imgui/releases/tag/v1.89.7
I tested the following features and platforms with success :
imgui[docking-experimental,dx9-binding,dx10-binding,dx11-binding,freetype,glfw-binding,glut-binding,libigl-imgui,opengl2-binding,opengl3-binding,sdl2-binding,vulkan-binding,wchar32,win32-binding]:x86-windows
imgui[docking-experimental,dx9-binding,dx10-binding,dx11-binding,dx12-binding,freetype,glfw-binding,glut-binding,libigl-imgui,opengl2-binding,opengl3-binding,sdl2-binding,vulkan-binding,wchar32,win32-binding]:x64-windows
imgui[docking-experimental,dx9-binding,dx10-binding,dx11-binding,dx12-binding,freetype,glfw-binding,libigl-imgui,opengl2-binding,opengl3-binding,sdl2-binding,vulkan-binding,wchar32,win32-binding]:x64-windows-static
imgui[docking-experimental,freetype,libigl-imgui,vulkan-binding,wchar32]:x64-uwp

[x] Changes comply with the maintainer guide
[x] SHA512s are updated for each updated download
[ ] The "supports" clause reflects platforms that may be fixed by this new version
[ ] Any fixed CI baseline entries are removed from that file.
[ ] Any patches that are no longer applied are deleted from the port's directory.
[x] The version database is fixed by rerunning ./vcpkg x-add-version --all and committing the result.
[x] Only one version is added to each modified port's versions file.

Please fix the CI error, you can find all failure logs from https://dev.azure.com/vcpkg/public/_build/results?buildId=91490&view=artifacts&pathAsName=false&type=publishedArtifacts.
FAILED: CMakeFiles/implot.dir/implot.cpp.obj
C:\PROGRA~1\MICROS~1\2022\ENTERP~1\VC\Tools\MSVC\1436~1.325\bin\Hostx64\x64\cl.exe   /TP  -ID:\buildtrees\implot\src\v0.14-fd7f3e910d.clean -ID:\installed\x64-windows\include /nologo /DWIN32 /D_WINDOWS /W3 /utf-8 /GR /EHsc /MP  /D_DEBUG /MDd /Z7 /Ob0 /Od /RTC1 /showIncludes /FoCMakeFiles\implot.dir\implot.cpp.obj /FdCMakeFiles\implot.dir\implot.pdb /FS -c D:\buildtrees\implot\src\v0.14-fd7f3e910d.clean\implot.cpp
D:\buildtrees\implot\src\v0.14-fd7f3e910d.clean\implot.cpp(1805): error C2065: 'ImGuiButtonFlags_AllowItemOverlap': undeclared identifier
D:\buildtrees\implot\src\v0.14-fd7f3e910d.clean\implot.cpp(1805): error C2737: 'plot_button_flags': const object must be initialized
D:\buildtrees\implot\src\v0.14-fd7f3e910d.clean\implot.cpp(3381): error C2065: 'ImGuiButtonFlags_AllowItemOverlap': undeclared identifier
D:\buildtrees\implot\src\v0.14-fd7f3e910d.clean\implot.cpp(3411): error C2065: 'ImGuiButtonFlags_AllowItemOverlap': undeclared identifier


Add support for pyarrow 10

Thank you for your contribution to the Graph Data Science Client project.

Before submitting this PR, please read Contributing to the Neo4j Ecosystem.
Make sure:

[x] You signed the Neo4j CLA (Contributor License Agreement) so that we are allowed to ship your code in our library
[x] Your contribution is covered by tests

Hope we can drop pyarrow 4 in the near future

me too...


NTR: decreased protein localization to division site, with protein mislocalized to cytoplasm

standard def
PMID:26132084

decreased protein localization to cell division site, with protein mislocalized to cytoplasm FYPO:0006221
edit file: a16a9a024893b3b63a7b4ebe0d51f1fc415fa21d
release: ff262e82c8f3b9d1f2af188e2d0fb6462ee50e65


Use Draft.js + Draftail to handle rich text fields

What I'm trying to achieve
We currently use Medium Editor for basic rich text features. We'd love to have something easier to style (not storing HTML in the database).
Describe a proposed solution
I propose that we use Draft.js to handle the editing and rendering aspect in React apps (dashboard and the new storefront). For Django views we can use Draftail to render things server-side.
Other solutions I've tried and won't work
We've evaluated most existing WYSIWYG/WYSIWYM editors.

Sorry for my late response. I was busy for the last few days.
I'll be working on it from now on.
So we want to use Draftail for React side editor, and possibly draft.js exporter for converting the Draft.js schema (that Draftail uses) to HTML for showing Draft.js data correctly in Django views?
cause I checked and Draftail is a client side editor built on Draft.js.
and as a result we want to save new data as JSON?
Am I correct?

Yes, sorry if there was any confusion.


anonymous structures support

Gopium supports only named structs as targets for all transformations.
Originally this was done by design, as supposedly all "important" structs, performance of which matters, should be named anyhow and originally it simplified internal implementation.
But there are some counterexample, for example take for consideration:
type Bank struct {
	// anonymous structure that won't be targeted by Gopium
	Departments []struct{
		ID string
		Open bool
		Workers int64
	}
	Assets float64
}

I still have doubts wherether it's important feature for Gopium or not.
As implementation will definitely require recurrent strategies. So generally for each struct we need to build structure tree and postorder traverse it, to support generic cases like this properly:
type a struct {
	b struct{
		c struct {
			d struct {
				e int32
			}
		}
	}
	f struct {
		g struct {
			h string
		}
		i struct {
			k string
		}
	}
}

So I'm opening this issue to gather feedback and ideas whether Gopium needs this feature or not.

Closing this as non priority issue.

Closing this as non priority issue.


min SDK issue to use library

Hi,
I need to use this library for minSDK 16.
Is it possible?
If yes, then how can I acheive this?
Thanks.

Hi
Sorry but min SDK version is 21.


Add GitHub Actions CI and Codecov badges to README.md

This pull request adds GitHub Actions CI and Codecov badges to the README.md file.

The badges seem to appear in different sections instead of appearing in a single line. Could you take a look at that?

i changed the alignment


Best way to access map services (E.g. PlacesService)?

I'm trying to make use of the PlaceService nearbySearch method.  Currently I'm making use of $window as I can't figure out from the documentation how else to do this.  This seems to work fine, but I'm guessing there's a better way?
NgMap.getMap().then((map) => {
  var placeService = new $window.google.maps.places.PlacesService(map);
  placesService.searchNearby({...}, (results, status) => {...});
});

You can have your own `PlaseService, but I don't see a way to avoid window.
There is similiar service GeoCode. https://github.com/allenhwkim/angularjs-google-maps/blob/master/services/geo-coder.js
You may take a look at that to see how it is coded.


Refactor the code

Refactor the code

Which code do you want to be refactored?

js/jquery.cccheck.js

Can I have it? @RuanAragao
But I'm pretty new to this open-source things.

Go ahead, don't worry. :wink:

Hello @RuanAragao
I have finished refactoring your code please review my pull request on #13


Rename "Project Type" to "Emissions Reduction Pathway"

Describe the task
This was a feature request raised by Eric S. during the CIF (Internal) App Demo on Apr 13, 2023. May require further validation.
Acceptance Criteria

[ ] first
[ ] second
[ ] third

Additional context

Add any other context about the task here.
Or here

@nanyangpro  I'm tagging this 'UX research', but this card is probably not needed, granted the proper training is given to the team

This hasn't been brought up again, and was the opinion of one person surveyed. Closing.


Remove direct usage of fork(2) in most tests, use trampolined execution instead

What does this PR do?
This addresses long standing issue with fork being inherently unsafe and unreliable way to run tests - and sidecar itself on production environments.
To enable running tests directly on linux - a new LD_PRELOAD based trampoline was added. It will automatically kick off when the spawn_worker crate is used from a linked executable.
However 1 caveat exists that enables this. The tests need to be compiled with "-rdynamic" flag which will export symbols so that they are available for LD_PRELOAD to look up and execute
Motivation
Evils of fork
Additional Notes
Fork is evil
How to test the change?

Thanks @paullegranddc and @r1viollet for the reviews :bow:


lodash treeshaking support

we should optimize our imports of lodash to allow treeshaking, as this results in lower bundle size.
their are multiple bundle tools supporting this. e.g. https://www.npmjs.com/package/@optimize-lodash/rollup-plugin
we should not do this:
import _ from "lodash;
_.join(values, ",")

instead we should do this:
import { join } from "lodash;
join(values, ",")

maybe also something like this should be fine
import join from "lodash/join;
join(values, ",")

should be fixed by https://samhammer.atlassian.net/browse/MET-2558


minItems, maxItems, pattern, variable fix

Implemented minItems from Schema
Implemented maxItems from Schema
Implemented pattern from Schema
Implemented available Architecture's from Schema
Implemented available InstallerType's from Schema
Added $script: to some variables which needs to stay throughout the script

Only tested with one manifest as of now
I do not understand the PromptInstallerManifestValue/Read-WinGet-InstallerManifest part so i worked around it

@quhxl can you take this for a run since you keep finding stuff that needs a update? 😁 (recommend to replace the YamlCreate in a new branch which have updated files)

I will try this. Thanks for the constant improvement of the script!

Well since a few actually want to use the PowerShell script instead of wingetcreate there is a reason to update it 😁
Now that multiple people can add features and we have YamlParsing it should be pretty simple to add the 2 last features we miss 😁


Visual bug

Chrome Version 79.0.3945.117 (Official Build) (64-bit)
image

Also sidebar menu vertical line overlapping to the parent menu

@AdeSupriyadi that one was fixed with 5a27b56 hasn't been pushed to live site thought


Implement interleave()

For parity with itertools, interleave() should alternately produce
elements from two given iterators. Once one of the iterators run out,
elements should just be drawn from the other until both are exhausted.
This is from #384

I'm not sure why this fails, some of the errors are that the ? operator is not stable. Is there something I need to do?

It's not you, but futures update -- see #412.
At a glance, the PR looks great.  I'll try to give it a proper review soon!

Ok, thank you :-) Let me know if there's anything I can do...

Can you now please rebase, to see how CI fares?

Sure thing

Sorry about the noise, I rebased on a different machine, and forgot to set core.name and core.email - should be fixed now.

@cuviper It should build now, I installed a rust 1.12.0 locally. The commitment to backwards compatibility is pretty cool, I think. :crossed_fingers: for tests passing

Looks like the order is getting mixed up:
---- iter::test::check_interleave_eq stdout ----
	thread 'iter::test::check_interleave_eq' panicked at 'assertion failed: `(left == right)`
  left: `[0, 10, 1, 2, 11, 12, 3, 13, 4, 14, 5, 15, 6, 7, 16, 17, 8, 18, 9, 19]`,
 right: `[0, 10, 1, 11, 2, 12, 3, 13, 4, 14, 5, 15, 6, 16, 7, 17, 8, 18, 9, 19]`', src/iter/test.rs:1735:4

Yeah, I'm not sure why though - I can't get it to fail locally, and it seems to be only on nightly that it fails :-/

it seems to be only on nightly that it fails

nightly is the only one that runs tests, if only because the dev-dependency compiletest_rs requires it (and dev-deps can't be conditional).

Hmm, that makes sense - am I doing something wrong then? I run cargo +nightly test, and I tried setting RUSTFLAGS='--cfg=rayon_unstable' as well, but so far no dice.

I think Travis runs with 2-cpus, so setting RAYON_NUM_THREADS=2 locally may get you closer.  I suggest adding a temporary debug-print with all your index, i_idx, j_idx, i_split, j_split, flag, even etc. so you have a trace of how things go awry.

Oh, that did it, thanks! I'll do some debugging now :-)

Thanks for the help @cuviper! I had forgotten to carry the flag through to InterleaveSeq's constructor.

Let's merge -- thanks!

Thanks! It should be relatively easy to implement interleave_shortest, I think, so I could give that a shot if you're interested.

Yeah, I think interleave_shortest will be a simple wrapper, much like zip_eq and zip.  Go for it!

Hmm, it may not be as trivial as I thought - the zip_eq is simple, because it is just zip with an added assertion in front. interleave_shortest should terminate once one of the iterators runs out (interleave exhausts them both).
But by their example, it is not simply take()ing the first n elements where n = cmp::min(i.len(), j.len()):
let it = (1..7).interleave_shortest(vec![-1, -2]);
itertools::assert_equal(it, vec![1, -1, 2, -2, 3]);

(source)
Observe that the last element is drawn from the first iterator, ie three elements are drawn from that one while the second only provides two elements.
I can see how I'd change with_producer for Interleave to select the right lengths for creating the producers, but I'd like to avoid copying too much code if possible. Maybe I'll try to pull that code out in interleave.rs and implement InterleaveShortest in interleave.rs? But I'm for better suggestions on how to implement this :-)

Something like this?
if i.len() <= j.len() {
    // take equal lengths from both iterators
    let n = i.len();
    i.take(n).interleave(j.take(n))
} else {
    // take one extra item from the first iterator
    let n = j.len();
    i.take(n + 1).interleave(j.take(n))
}

(using take even when it's redundant, to get consistent types)

Thanks for the suggestion! I was trying something similar, but run into:
error[E0308]: mismatched types
  --> src/iter/interleave.rs:49:9
   |
42 | pub fn new_shortest<I, J>(i: I, j: J) -> Interleave<I, J>
   |                                          ---------------- expected `iter::interleave::Interleave<I, J>` because of return type
...
49 |         i.take(n).interleave(j.take(n))
   |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ expected type parameter, found struct `iter::take::Take`
   |
   = note: expected type `iter::interleave::Interleave<I, J>`
              found type `iter::interleave::Interleave<iter::take::Take<I>, iter::take::Take<J>>`

error[E0308]: mismatched types
  --> src/iter/interleave.rs:53:9
   |
42 | pub fn new_shortest<I, J>(i: I, j: J) -> Interleave<I, J>
   |                                          ---------------- expected `iter::interleave::Interleave<I, J>` because of return type
...
53 |         i.take(n + 1).interleave(j.take(n))
   |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ expected type parameter, found struct `iter::take::Take`
   |
   = note: expected type `iter::interleave::Interleave<I, J>`
              found type `iter::interleave::Interleave<iter::take::Take<I>, iter::take::Take<J>>`

pub fn new_shortest<I, J>(i: I, j: J) -> Interleave<I, J>

I think we'll want this to return a distinct InterleaveShortest<I, J> type, so we're not bound to any particular implementation details.  This custom type can contain an Interleave<Take<I>, Take<J>>, and forward all methods to that.  (as ZipEq does)


STUB_PROPERTY and STUB_METHOD

Is everything that is flagged as STUB* deprecated ? or  some might be implemented later?
The warning often says "deprecated: property not yet implemented".
This is not useful in telling me if it will be coming later and I should wait for it, or it is deprecated and I should 'implement or workaround'..  Is there a way to tell the difference?

STUB_* are entities that are not yet implemented (/to be implemented in the future)
I can see that for STUB_* properties and methods in UIKit project, it's indicating it's deprecated, @asimonov-msft  could shed more light into why we are getting deprecated tags for the warning.

https://github.com/Microsoft/WinObjC/wiki/FAQ#whats-the-deal-with-all-of-these-stubs has the details about stubs.  The warning says deprecated because we use deprecated() attribute (we needed a reliable attribute) to tag them.
We have stubs to enable most apps to compile easily.  The idea here is that the app will be functional for key scenarios with just the stubs.
Stub doesnt mean we will implement something in the future.  If you need some stubbed method, please do open an issue for what you need.  Alternatively, we would appreciate pull requests as well.  Hope that helps.

@jaimerodriguez closing this issue for now, please let us know if you have any other questions on this.


Suggestion: add version verification to checkrr output

I cannot find a way to verify the version of checkrr that is currently installed. I would suggest adding the version number to the output and/or supporting a runtime argument like --version.

Resolved with 980f616265711e084350151832ba66020a73191b


Update MigrateToRewrite8 referenced recipes

What's changed?
The package of referenced recipes in MigrateToRewrite8.
What's your motivation?
I tried to run the MigrateToRewrite8 recipe introduced in #3241, but saw these messages:
> Task :rewriteDryRun
Validating active recipes
Recipe validation error in org.openrewrite.java.upgrade.MigrateToRewrite8.recipeList[0] (in jar:file:/home/sghill/.gradle/caches/modules-2/files-2.1/org.openrewrite/rewrite-java/8.0.0/5846c136ff8dc89b163dbff7445633bd6bb4c9c2/rewrite-java-8.0.0.jar!/META-INF/rewrite/migrate-rewrite.yml):
recipe 'org.openrewrite.java.upgrade.MigrateRecipeToRewrite8' does not exist.
Recipe validation error in org.openrewrite.java.upgrade.MigrateToRewrite8.recipeList[1] (in jar:file:/home/sghill/.gradle/caches/modules-2/files-2.1/org.openrewrite/rewrite-java/8.0.0/5846c136ff8dc89b163dbff7445633bd6bb4c9c2/rewrite-java-8.0.0.jar!/META-INF/rewrite/migrate-rewrite.yml):
recipe 'org.openrewrite.java.upgrade.MigrateTestToRewrite8' does not exist.
Recipe validation error in org.openrewrite.java.upgrade.MigrateToRewrite8.recipeList[2] (in jar:file:/home/sghill/.gradle/caches/modules-2/files-2.1/org.openrewrite/rewrite-java/8.0.0/5846c136ff8dc89b163dbff7445633bd6bb4c9c2/rewrite-java-8.0.0.jar!/META-INF/rewrite/migrate-rewrite.yml):
recipe 'org.openrewrite.java.upgrade.MigrateMarkersSearchResult' does not exist.

The classes were relocated in #3118.
Have you considered any alternatives or workarounds?
I'm using the gradle plugin, so I copied this version with the package change into my local rewrite.yml and saw it succeed :tada:

Thanks a lot!