Feature Req: Sql generation for Oracle

When following this tutorial https://js.langchain.com/docs/modules/chains/popular/sqlite
but for  Oracle I get an error message saying this database type has not been implemented.
I looked through the module and began trying to fix it.
The query to complete this is:
select table_name, column_name, data_type, nullable from user_tab_columns

Thank you bot.
I 've implemented the changes for Oracle and would like to see them implemented here so I don't have to maintain my own fork of langchain.
Also the documentation does mention Oracle.


GUACAMOLE-422: Forward Timezone to RDP and SSH Connections

These are the client-side changes to allow both detection of (via JSTZ) and overriding of the client timezone for remote connections (SSH and RDP).

Just a caution on this one - makes changes to guacamole-common and guacamole-ext, so backward compatibility may be an issue.

@mike-jumper: Thanks for the feedback.  I'll take another stab at putting it into the handshake and see what I can get done.
Do we want to go ahead and pull this change out of the 1.1.0 release and push it out to a future version?  Sounds like it's invasive enough that maybe we could add it to whatever release ends up with parameter prompting or something like that - 2.0.0 or whatever we decide?

@mike-jumper: Okay, rebased on staging/1.1.0 for now, though I'm still not sure if this belongs in this release or not?  Anyway, I think I managed to make the changes you were suggesting to make this part of the client handshake, and removed some of the kludgy stuff that glued it together previously.  Also opened a pull on the server-side for the libguac bits.  Need to test it still and make sure it works, but let me know if there is anything obviously wrong with the latest commits.

Regarding whether the changes belong in 1.1.0, the base timezone changes are already present on staging/1.1.0, at least for providing "timezone" parameters for RDP and SSH. That much should definitely stay, as it's compatible with 1.0.0 and I believe was included in scope as part of the initial release discussion.
As for the handshake changes ... those are incompatible protocol changes and would technically bump things to 2.0.0. However, I think we can alter things there such that the changes are compatible.
If the handling of the handshake phase is altered such that:

Order of the various handshake-specific instructions does not matter.
Presence/absence of the various handshake-specific instructions does not matter (with the exception of connect which terminates the handshake).

then things will inherently be backward compatible, and the protocol becomes a bit more forgiving of implementations going forward. This would require replacing current usage of guac_parser_expect() within the handshake with a read loop and array of instruction handler callbacks, similar to:
https://github.com/apache/guacamole-server/blob/ffe0b57faa97272ee1287bcea74c5d787e221953/src/libguac/user-handlers.c#L37-L54
and:
https://github.com/apache/guacamole-server/blob/ffe0b57faa97272ee1287bcea74c5d787e221953/src/libguac/user.c#L170-L186

Assuming the above, it would also be important that the ConfiguredGuacamoleSocket implementation continue to adhere to the 1.0.0 and older handshake except where the timezone is set, or else it would become incompatible with 1.0.0 and older guacd.
Another option could be to modify the semantics of args to include a protocol version number, allowing ConfiguredGuacamoleSocket or other implementations to change behavior depending on which version of guacd is being used.

@mike-jumper: So, I think I have backward compatibility from a guacd perspective handled - that is, the newer guacd will accept either older clients that do not provide the "timezone" handshake parameter, or newer clients that do, without any problems.
I'm struggling with backward compatibility from the other angle - that is, if I use the newer client that sends timezone with the older (1.0.0) guacd, I get protocol errors.  I am only sending the timezone parameter through the tunnel when set; however, the issue is that, as I have it implemented, today, I'm auto-detecting the timezone via JSTZ and sending that information automatically (=always).  So, not sure what other ways might be available to make this backward-compatible?  I looked at the args sent back from the server, but am not really sure the best way to implement sending back some sort of protocol version - right now it looks like the only thing that gets sent back is a list of acceptable parameters for the given protocol?

Yes, that's correct. The semantics of args would need to be modified in a backward-compatible way. For example, if a simple protocol implementation would currently produce:
4.args,8.hostname,4.port;

consider a change to args which would include the version number as one of the arguments:
4.args,<IP_ADDRESS>,8.hostname,4.port;

If the definition of args from that point forward specified that the first argument is the version number, then code that's aware of this would be able to make decisions based on that number. Code that's unaware of this would continue with the old args semantics, considering "1.1.0" to be the name of a parameter. With no value defined for such a parameter, a conforming implementation would simply include the empty string in the connect response:
7.connect,0.,9.localhost,4.1234;

whereas newer implementations would know to handle that value specifically. One possibility here would be to similarly modify connect to specify that the first argument should be the protocol version of the client (with the exception of older clients that may include an empty string):
7.connect,<IP_ADDRESS>,8.hostname,4.port;

That version information could be logged, included in guac_user, compared against the guacd version, etc.
Whether the version number should be the literal release version or some protocol-specific version number (or both?) is also worth considering.

Okay, I've taken a stab at this - I may have gone complete overkill on the client side - implementing a new enum with some supporting functions.  Let me know what needs work, here.

@mike-jumper: Okay, client-side of this I've gone back and redone a couple of things, but have confirmed client works both current and backward-compatible.  Let me know what needs attention, here.

@mike-jumper Anything else on this one before it can go in following the matching apache/guacamole-server changes?

Ah, good point. Never mind.
On Mon, May 6, 2019, 08:02 Virtually Nick<EMAIL_ADDRESS>wrote:

@necouchman commented on this pull request.
In
guacamole-common/src/main/java/org/apache/guacamole/protocol/GuacamoleProtocolVersion.java
https://github.com/apache/guacamole-client/pull/348#discussion_r281224615
:

   return patch;

}

/**

* Determines whether or not this object is greater than or equal to the

* the version passed in to the method.  Returns a boolean true if the

* version is the same as or greater than the other version, otherwise

* false.

*

* @param otherVersion

*     The version to which this object should be compared.

*

* @return

*     True if this object is greater than or equal to the other version.

*/

public boolean atLeast(GuacamoleProtocolVersion otherVersion) {

Ah, but guacamole-common is not at Java 8, it's still at Java 6. So,
we'll either have to bring it up, or do this another way...
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/apache/guacamole-client/pull/348#discussion_r281224615,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABDLCSOPPUSHWU3UJJFSKY3PUBCARANCNFSM4GMCXWBQ
.

No, I think what you already have is better defined.
On Mon, May 6, 2019, 08:54 Virtually Nick<EMAIL_ADDRESS>wrote:

@necouchman commented on this pull request.
In
guacamole-common/src/main/java/org/apache/guacamole/protocol/GuacamoleProtocolVersion.java
https://github.com/apache/guacamole-client/pull/348#discussion_r281246386
:

   return patch;

}

/**

* Determines whether or not this object is greater than or equal to the

* the version passed in to the method.  Returns a boolean true if the

* version is the same as or greater than the other version, otherwise

* false.

*

* @param otherVersion

*     The version to which this object should be compared.

*

* @return

*     True if this object is greater than or equal to the other version.

*/

public boolean atLeast(GuacamoleProtocolVersion otherVersion) {

It looks like Java enums implement the compareTo() method, though, using
the position of declaration of the enum value as the relative comparison
between them. So, I could leverage that, instead of a function like this,
but is that something we really want to rely on?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/apache/guacamole-client/pull/348#discussion_r281246386,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABDLCSKOUD5CP2G4BPTDPQDPUBIDDANCNFSM4GMCXWBQ
.

Is there a need to do that kind of search?
I was thinking it would be sufficient to parse the value as a new instance
of the class, compare to the highest supported version, and choose
whichever is less.
On Thu, May 23, 2019, 13:18 Virtually Nick<EMAIL_ADDRESS>wrote:

@necouchman commented on this pull request.
In
guacamole-common/src/main/java/org/apache/guacamole/protocol/GuacamoleProtocolVersion.java
https://github.com/apache/guacamole-client/pull/348#discussion_r287117504
:

* Parse the String format of the version provided and return the

* the enum value matching that version.  If no value is provided, return

* null.

*

* @param version

*     The String format of the version to parse.

*

* @return

*     The enum value that matches the specified version.

*/

public static GuacamoleProtocolVersion getVersion(String version) {

   if (version == null || version.isEmpty())

       return null;

   return valueOf(version);

So, I've got this implemented to the point where I can parse the provided
string for a major, minor, and patch version component, but I'm having
trouble coming up with an algorithm that finds the nearest (equal to or
less than provided) version...
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/apache/guacamole-client/pull/348?email_source=notifications&email_token=ABDLCSOU6CW2Z65RR245JVDPW33ZLA5CNFSM4GMCXWB2YY3PNVWWK3TUL52HS4DFWFIHK3DMKJSXC5LFON2FEZLWNFSXPKTDN5WW2ZLOORPWSZGOBZR6UQQ#discussion_r287117504,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABDLCSN3EMHVMNCNEIMKCGLPW33ZLANCNFSM4GMCXWBQ
.

Alrighty. At this point, I think these changes look absolutely fine. I'll try tinkering with class vs. enum for GuacamoleProtocolVersion to see if things feel better one way or the other, but I don't see any reason to hold off on these changes further. They look quite good.


Add how to solve Unsupported ESM URL Scheme Error in Cloudflare Pages deployment

Cloudflare uses Node version 12 as default, so we will get an error from some dependencies at build time.
So, it is recommended to set NODE_VERSION to 14 to the Pages production environments for consistency.

Not sure I understand this, Cloudflare doesn't run Node.js. Is this a CI thing?

Not sure I understand this, Cloudflare doesn't run Node.js. Is this a CI thing?

Yeah, it is a CI thing when Pages run npm run build.
Pages Node default version is 12.18.0. So, we need to explicitly set the environment variable NODE_VERSION to a more recent version.

I've changed the explanation to be concise. Take a look at this commit.

There is a .node-version in the pages template that takes care of this already but maybe it's good to call it out?

Oh, I added a .node-version to your branch but we already have that on main (like Jacob said). I don't think we need to call anything out, it will only break if people delete the file :)


docs: fix typo in modal.md

Changed default to defaultModal in the first example.

Thanks @jnooree. Merged!


Avoid calling warning() before Errors module initialised

Errors module is initialized during running pipeline:
https://github.com/cython/cython/blob/b462eec9899988a8d9c6637669ad8fcf1e3988ab/Cython/Compiler/Main.py#L521
There is a warning informing about deprecated name of .pxd file during the search of .pxd file:
https://github.com/cython/cython/blob/b462eec9899988a8d9c6637669ad8fcf1e3988ab/Cython/Compiler/Main.py#L694
However, the search can be run before running pipeline:
Traceback (most recent call last):
  File "/Users/matus/dev/cython/test/setup.py", line 6, in <module>
    ext_modules=cythonize("module.pyx", include_path=['bar']),
  File "/Users/matus/dev/cython/Cython/Build/Dependencies.py", line 990, in cythonize
    module_list, module_metadata = create_extension_list(
  File "/Users/matus/dev/cython/Cython/Build/Dependencies.py", line 839, in create_extension_list
    kwds = deps.distutils_info(file, aliases, base).values
  File "/Users/matus/dev/cython/Cython/Build/Dependencies.py", line 691, in distutils_info
    return (self.transitive_merge(filename, self.distutils_info0, DistutilsInfo.merge)
  File "/Users/matus/dev/cython/Cython/Build/Dependencies.py", line 700, in transitive_merge
    return self.transitive_merge_helper(
  File "/Users/matus/dev/cython/Cython/Build/Dependencies.py", line 712, in transitive_merge_helper
    for next in outgoing(node):
  File "/Users/matus/dev/cython/Cython/Utils.py", line 129, in wrapper
    res = cache[args] = f(self, *args)
  File "/Users/matus/dev/cython/Cython/Build/Dependencies.py", line 613, in cimported_files
    pxd_file = self.find_pxd(module, filename)
  File "/Users/matus/dev/cython/Cython/Utils.py", line 129, in wrapper
    res = cache[args] = f(self, *args)
  File "/Users/matus/dev/cython/Cython/Build/Dependencies.py", line 594, in find_pxd
    pxd = self.context.find_pxd_file(relative, source_file_path=filename)
  File "/Users/matus/dev/cython/Cython/Compiler/Main.py", line 270, in find_pxd_file

I have investigated the possibility to move Errors module initialisation to earlier stage but I found it rather disruptive change. Hence, I am proposing
to move the check of .pxd file name to the code called elusively within the pipeline run.
Fixes #5396

Thanks


10 times the speed change, but the real-time playback time is not reduced by 10 times

Media3 Version:
exoplayer 2.17.1
A video is 60 seconds long and is played using exoPlayer. The speed and pitch of PlaybackParameters are set to 10. The expected playback time is 6 seconds, but the actual playback time is 10 seconds or even longer.
why is that? How should I modify the parameters so that the actual playback time is 6 seconds?

I set a LivePlaybackSpeedControl for exoPlayer, and set its fallbackMaxPlaybackSpeed to 10f; at the same time, I created a thread synchronized with the playback thread to simulate the playback thread. In the simulation thread, call LivePlaybackSpeedControl.getAdjustedPlaybackSpeed(LivePlaybackSpeedControl.getTargetLiveOffsetUs(), 5000000) at intervals, I successfully changed the speed of the 60-second video to 10 times, and the playback was completed in about 6 seconds, but it is also probabilistic.
Then the following question arises, why is it necessary to call getAdjustedPlaybackSpeed after a period of time to change the speed after setting LivePlaybackSpeedControl? , also bypassing the limitation of DefaultAudioSink's maxSpeed? Why is it possible to change the speed successfully and not necessarily succeed in this way? Can I achieve my goal of 10x speed change by setting LivePlaybackSpeedControl?


Add ARP spoofing guard for host gateway port

Add ARP spoof guard flow entry after host gateway interface is created.
Fixes #200

/test-e2e

I personally feel no need to restrict the default namespace traffic. Anyway, you could not control all interfaces on the node.

@antoninbas and I have an offline discussion about it, and we thought if the ARP reply sent from gw0 is using a fake MAC, later Openflow entries might not work, especially for the traffic that needs to be forwarded by host gateway. Technically, the MAC/IP address could be changed when the packets enters OVS from gw0 interface.

You see if a Pod could send raw packets from a host interface, it could do many attacks, like it could even send VXLAN packets from a physical interface. And such containers should not be viewed as an application container, but more like a local daemon like antrea-agent.

@jianjuns I agree about your statement. However, ARP spoofing is pretty bad IMO since it can mess up the networking for other Pods and that change actually prevents that it seems. So unless there is a downside to this change I am not seeing, I suggest we merge it.

@antoninbas @wenyingd : I just do not like to add unnecessary flows and do not like to restrict host interface/traffic. But for this one I do not have a strong opinion. As you said there is no hard either (not sure if there could be cases that we want to manually bind another IP to the gateway interface though, of course for testing purposes only).


Add tests for probe/cri/registry

Hey all 👋,
First of all, thank you for making such a great project! Found it via Hacktoberfest and immediately jumped into the bandwagon for helping out. Love the current organisation/labelling of the issues. Super helpful for us newcomers.
Figured I should get this PR out sooner rather than later to start getting some feedback. While stressing the different code paths with the tests, I noticed there was one case that no matter what I do, I couldn't get an error to bubble up: The case where the scheme is "".
I'm not sure if this is some sort of 🐞 or am I missing something (?), but I ended up refactoring (to the best of my very limited Go knowledge and understanding of the project) some bits to make it so that it complies with what I think the intention was.
From what I read, the assumption was that we don't support URLs were the scheme is not specified but we're supporting them anyways when we use the fallback protocol. The branch is the more natural thing to miss, so I optimised for supporting the case (feedback is very very welcome).
The last commit is very optional, I'm not familiar with Go (in fact, this is my first PR ever). I'm happy to take it out if this is not the way we do things in Goland.
As for the tests they cover:
Unhappy path tests try to cover three scenarios

When the endpoint URL scheme is not explicitly supported e.g. HTTP
When the endpoint URL scheme is TCP which is also not supported
When we fail to parse the given URL (to extract the scheme)

The happy path covers two scenarios

When we specify the supported scheme in the URL which is an unix
socket e.g. unix///var/run/dockershim.sock
When we pass a socket address but fail to specify the scheme but our registry attempts
to use the fallback protocol e.g. var/run/dockershim.sock

Solves #3302

@bboreham gentle nudge (I completely understand if you've been or still are short on time)
As I'd like to try and add some tests for the reporter but I'd like to know whenever I'm on the right track or not.

This generally LGTM, but I'm not actively contributing to scope, but considering this change is adding a test that was previously missing, it looks like a good one to me!
But I'm not very sure why CI is failing with an error message that doesn't seem to relate to changes here in any way:
goveralls -repotoken $COVERALLS_REPO_TOKEN -coverprofile=profile.cov -service=circleci
exit status 2: warning: no packages being tested depend on github.com/weaveworks/scope/app/multitenant
warning: no packages being tested depend on github.com/weaveworks/scope/cri/runtime
warning: no packages being tested depend on github.com/weaveworks/scope/extras/copyreport
warning: no packages being tested depend on github.com/weaveworks/scope/extras/dialer/src
warning: no packages being tested depend on github.com/weaveworks/scope/extras/example/searchapp
warning: no packages being tested depend on github.com/weaveworks/scope/extras/example/shout
warning: no packages being tested depend on github.com/weaveworks/scope/extras/fixprobe
warning: no packages being tested depend on github.com/weaveworks/scope/probe/appclient
warning: no packages being tested depend on github.com/weaveworks/scope/probe/cri
warning: no packages being tested depend on github.com/weaveworks/scope/probe/plugins
warning: no packages being tested depend on github.com/weaveworks/scope/prog
warning: no packages being tested depend on github.com/weaveworks/scope/prog/externalui
warning: no packages being tested depend on github.com/weaveworks/scope/prog/staticui
warning: no packages being tested depend on github.com/weaveworks/scope/render/expected
warning: no packages being tested depend on github.com/weaveworks/scope/test
warning: no packages being tested depend on github.com/weaveworks/scope/test/fixture
warning: no packages being tested depend on github.com/weaveworks/scope/test/utils
warning: no packages being tested depend on github.com/weaveworks/scope/test/weave
warning: no packages being tested depend on github.com/weaveworks/scope/tools/cover
warning: no packages being tested depend on github.com/weaveworks/scope/tools/runner
warning: no packages being tested depend on github.com/weaveworks/scope/tools/socks
# github.com/weaveworks/scope/probe/docker
/tmp/go-build431662974/github.com/weaveworks/scope/probe/docker/_obj/container.go:328:17: undefined: namespaceIPAddresses
# github.com/weaveworks/scope/vendor/github.com/weaveworks/tcptracer-bpf/vendor/github.com/iovisor/gobpf/elf
In file included from vendor/github.com/weaveworks/tcptracer-bpf/vendor/github.com/iovisor/gobpf/elf/elf.go:52:0:
./include/bpf.h:12:30: fatal error: linux/bpf_common.h: No such file or directory
 #include <linux/bpf_common.h>
                              ^
compilation terminated.
# github.com/weaveworks/scope/vendor/github.com/google/gopacket/pcap
vendor/github.com/google/gopacket/pcap/pcap.go:22:18: fatal error: pcap.h: No such file or directory
 #include <pcap.h>
                  ^
compilation terminated.
FAIL	github.com/weaveworks/scope/app [build failed]

Exited with code 1

Could you rebase and force re-running the CI that way?

This generally LGTM, but I'm not actively contributing to scope, but considering this change is adding a test that was previously missing, it looks like a good one to me!
But I'm not very sure why CI is failing with an error message that doesn't seem to relate to changes here in any way:
goveralls -repotoken $COVERALLS_REPO_TOKEN -coverprofile=profile.cov -service=circleci
exit status 2: warning: no packages being tested depend on github.com/weaveworks/scope/app/multitenant
warning: no packages being tested depend on github.com/weaveworks/scope/cri/runtime
warning: no packages being tested depend on github.com/weaveworks/scope/extras/copyreport
warning: no packages being tested depend on github.com/weaveworks/scope/extras/dialer/src
warning: no packages being tested depend on github.com/weaveworks/scope/extras/example/searchapp
warning: no packages being tested depend on github.com/weaveworks/scope/extras/example/shout
warning: no packages being tested depend on github.com/weaveworks/scope/extras/fixprobe
warning: no packages being tested depend on github.com/weaveworks/scope/probe/appclient
warning: no packages being tested depend on github.com/weaveworks/scope/probe/cri
warning: no packages being tested depend on github.com/weaveworks/scope/probe/plugins
warning: no packages being tested depend on github.com/weaveworks/scope/prog
warning: no packages being tested depend on github.com/weaveworks/scope/prog/externalui
warning: no packages being tested depend on github.com/weaveworks/scope/prog/staticui
warning: no packages being tested depend on github.com/weaveworks/scope/render/expected
warning: no packages being tested depend on github.com/weaveworks/scope/test
warning: no packages being tested depend on github.com/weaveworks/scope/test/fixture
warning: no packages being tested depend on github.com/weaveworks/scope/test/utils
warning: no packages being tested depend on github.com/weaveworks/scope/test/weave
warning: no packages being tested depend on github.com/weaveworks/scope/tools/cover
warning: no packages being tested depend on github.com/weaveworks/scope/tools/runner
warning: no packages being tested depend on github.com/weaveworks/scope/tools/socks
# github.com/weaveworks/scope/probe/docker
/tmp/go-build431662974/github.com/weaveworks/scope/probe/docker/_obj/container.go:328:17: undefined: namespaceIPAddresses
# github.com/weaveworks/scope/vendor/github.com/weaveworks/tcptracer-bpf/vendor/github.com/iovisor/gobpf/elf
In file included from vendor/github.com/weaveworks/tcptracer-bpf/vendor/github.com/iovisor/gobpf/elf/elf.go:52:0:
./include/bpf.h:12:30: fatal error: linux/bpf_common.h: No such file or directory
 #include <linux/bpf_common.h>
                              ^
compilation terminated.
# github.com/weaveworks/scope/vendor/github.com/google/gopacket/pcap
vendor/github.com/google/gopacket/pcap/pcap.go:22:18: fatal error: pcap.h: No such file or directory
 #include <pcap.h>
                  ^
compilation terminated.
FAIL	github.com/weaveworks/scope/app [build failed]

Exited with code 1

Could you rebase and force re-running the CI that way?

@errordeveloper have rebased now but seems to be the same error.

The integration tests only run on branches in the main repo, to avoid exposing credentials to all comers.
As workaround, anyone with permission to the main repo can push the branch there to have them run.
(but take a look at the PR first)

@gotjosh The code looks ok, but clearly it is doing more than adding a test (and a refactor), so rather than have me guess what that is, could you state it?
I imagine it relates to what you are saying about protocols, but it's better all round if you change the commit message to say what you fixed.

Hey, @bboreham thanks for taking a look and the feedback! 🙌
Are there any particular lines/sections that you would like to document/state as part of the commit message? As part of the PR body, I tried to convey the intention of the first commit in detail perhaps it's just a matter of adding some bits from the description into the commit message. Another thing that occurs to me is that I could split the tests and the changes on two different commits, I'll get tha sorted straight away.
The main reasoning behind the change is:

While stressing the different code paths with the tests, I noticed there was one case that no matter what I do, I couldn't get an error to bubble up: The case where the scheme is "".

I'm not sure if this is some sort of 🐞 or am I missing something (?), but I ended up refactoring (to the best of my very limited Go knowledge and understanding of the project) some bits to make it so that it complies with what I think the intention was.

From what I read, the assumption was that we don't support URLs were the scheme is not specified but we're supporting them anyways when we use the fallback protocol. The branch is the more natural thing to miss, so I optimised for supporting the case (feedback is very very welcome).

Hi @gotjosh Changes looks good to me. I have triggered the integration tests for latest commits.
Thanks for the change.


Ling/tooling update

Updates dependencies, UI tests and lints according to newer rustc and clippy versions
bors try

bors try

bors r+

bors try

bors r+


Unformat not respecting settings

I'm brazilian, here in Brazil we use "," as decimal separator, "." as thousand separator and "R$" as currency symbol.
I have some text input with formatted input, like "R$ 123,45", then I call unformat(text) to set the (double) value and the result as expected would be (doube) 123.45, but the actual result is (double) 12345.
The accounting.settings is:
accounting.settings = {
currency: {
symbol : "R$",
format: "%s%v",
decimal : ",",
thousand: ".",
precision : 2
},
number: {
precision : 0,
thousand: ".",
decimal : ","
}
}

As a temporary fix I do: unformat(text.replace(",","."))

I'm also from Brazil and had the same issue.
I was about to try to fix the issue myself, debugging the unminified version of the library but, it turns out that the unminified version works just fine!
The dev must check the provided minified version for download, it seems to be outdated.
While this doesn't happen, we can just grab the unminified version, add to our projects and run some minification process ourselves.

We just ran into this issue and the solution @fauresco is proposing is the way to go for the time being. The unformat logic in the non-minified version of the file works as expected.
Looks like the minified and non-minified files have diverged quite a bit, I see updated 2 years ago vs 6 months ago in the commit history.

We ran into the same issue and are proposing this solution: https://github.com/openexchangerates/accounting.js/pull/183

I address this issue in #186. Documentation provides only one example of passing a second argument to unformat(), so this may be easily overlooked.
For proper usage, you may:

Pass a second argument to unformat to specify the decimal separator:

accounting.unformat("R$ 1.234,56", ","); // 1234.56

Change the settings before using unformat:

accounting.settings.number.decimal = ",";
accounting.settings.number.thousand = ".";
accounting.unformat("R$ 1.234,56"); // 1234.56


Per-paragraph comments

From #2.

We currently have integration with http://aroc.github.io/side-comments-demo/, but it needs work.


Mod Compatibility Request: Easy Shulker Boxes

Would it be possible to make the mod compatible with easy shulker boxes?
https://modrinth.com/mod/easy-shulker-boxes/version/v8.0.2-1.20.1-Fabric
it allows you to select the slot on a shulker box or bundle by scrolling up or down on the mousewheel, i think it would add a lot for the convenience of the mod, and make the experience more seamless.

I can look into adding something like this. I really like the idea too since it wouldn't interfere with any of the other controls


fix(order): bad bundle item fragments and query field

PR Checklist
Please check if your PR fulfills the following requirements:

[x] The commit message follows our guidelines: https://github.com/graycoreio/daffodil/blob/master/CONTRIBUTING.md#commit
[ ] Tests for the changes have been added (for bug fixes / features)
[ ] Docs have been added / updated (for bug fixes / features)

PR Type
What kind of change does this PR introduce?

[x] Bugfix
[ ] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] CI related changes
[ ] Documentation content changes
[ ] Other... Please describe:

What is the current behavior?

The guest orders query tries to query the orders field; the correct field is items.
Fragments on different types of item cannot be combined.

What is the new behavior?

The guest orders query tries to query items.
Fragments on different types of item define all the item fields.

Does this PR introduce a breaking change?
[ ] Yes
[x] No

Other information

@lderrickable FYI combining fragments doesn't actually work like we though because all the concrete schema types are totally distinct.

lgtm


Fixie as testing framework instead of xUnit.

Description
Please consider either adding a fork of this sample app that uses Fixie instead of xUnit, or adding a set of tests using Fixie.
Justification
As mentioned in the blog post "Integration Testing with xUnit", referring to the infrastructure built to run integration tests with xUnit:

Writing tests this manner allows me to fit inside xUnit's lifecycle configuration - but it's super ugly.

and

...while it's feasible to write tests in this way, I'd suggest avoiding it... Instead, either use a framework more suited for this style of tests (Fixie or any of the BDD-style libraries)...

No...none of my client projects use Fixie...this is intended to show what a typical project would look like.


missing sdist for 1.11.0

👋 FYI, it looks like sdist is missing on pypi for 1.11.0 release.

1.110.0 is not released yet. It should be available soon though.


a non-Jquery version of admin page showing PG history

When I need to see PG history in admin UI and used the example from doc, I got a JS error of $ is not defined error in browser when clicking Context, Data & Changes button.  Since Bootstrap is leaving JQuery, here I provide a working example of pure JS.

Also, if I don't remove user from select_related(), there will be an error of:
Invalid field name(s) given in select_related: 'user'. Choices are: pgh_context

Last, are there ways to make it support pagination? Thanks!

Hey @xjlin0, thanks for bringing this to my attention!
What version of Django are you using?
The user issue you are mentioning was an issue from when I copied the original example. In the original example, I used a custom aggregate event model so that it could be visualized in the admin. (see https://django-pghistory.readthedocs.io/en/latest/extras.html#retrieving-and-joining-aggregateevent-metadata). This included the user object. Thanks for catching it!

Following up on some PRs I forgot to close out. django-pghistory has a native admin integration now


[UWP] Change visibility of Close button to always visible

Related Issue
Fixes #3838
Description
Changes the visibility of the Close button to be always visible so it can be accessed through keyboard navigation.
Why the change?
It was deemed not possible (at this time) to access the children views for a ListView in UWP. This access was necessary as it would have allowed changing the visibility of the button with the "OnSelectionChanged" event. More changes would have been necessary to use this approach so this change be sufficient in the meantime.
How Verified
The visualizer app was executed and the behaviour can be checked as the Close button is now selectable

Microsoft Reviewers: Open in CodeFlow

/azp run


[Question] Possible to copy file to node from locally-attached disk?

Currently previewing Harvester-20221014 aka v1.1.0-rc3
I'm wanting to migrate some systems to Harvester, but uploading images from the web UI is time-consuming and unreliable.
I'd rather copy the image files via a disk connected physically to a node to a specified location on the filesystem.
Is this possible?

There is no handy solution for it now.
Technically speaking, Harvester utilizes Longhorn as the persistant storage, and when creating image in WebUI, the source file can be either an remote http link, or from local file in the client PC.  Longhorn will download this file and convert it into an image file. It does not support using a local file in the the Cluster NODE path as the source file yet.

One hack you may try:
Navigate to your file local of your local disk, start a simple http server via python3
harv31:~ # python3 -m http.server
Serving HTTP on <IP_ADDRESS> port 8000 (http://<IP_ADDRESS>:8000/) ...

suppose your Harvester cluster NODE ip is <IP_ADDRESS>, then use http://<IP_ADDRESS>:8000/....full path of your file as the URL in Harvester WebUI to create image.
It will be much faster than downloading from public network, and also re-use Harvester exsting solution to create image.

There is no handy solution for it now.
Technically speaking, Harvester utilizes Longhorn as the persistant storage, and when creating image in WebUI, the source file can be either an remote http link, or from local file in the client PC. Longhorn will download this file and convert it into an image file. It does not support using a local file in the the Cluster NODE path as the source file yet.

Thank you for the clarification,
I used the python simple http server option mentioned in https://github.com/harvester/harvester/issues/3002#issuecomment-1286852891 last night, after attempts to perform local upload resulted in a failure at 99% complete multiple times (error msg "context cancelled"). URL currently seems like the far preferable option IMO as of now.
Let's close this issue.

One hack you may try:
harv31:~ # python3 -m http.server
Serving HTTP on <IP_ADDRESS> port 8000 (http://<IP_ADDRESS>:8000/) ...
It will be much faster than downloading from public network

Yeah, I came across this solution last night after local upload failed on me right at the end (23GB file - was excruciating). If anyone who sees this issue thread is looking for more guidance, I posted a write-up on my blog: https://develmonk.com/2022/10/20/simple-http-server-for-sending-local-images-to-ranchers-harvester-hci-os/
BTW, I just used port 80 to avoid port notation.


don’t work on iPad

the obsidian shows "failed to load plugin obsidian-html-plugin" when click the enable bottom

the obsidian shows "failed to load plugin obsidian-html-plugin" when click the enable bottom

Sorry, I do not have any workable iPad/iPhone/MAC device or simulator, therefore I never testing this plugin on these platforms.
In one of closed issue of this plugin, this kind of problem is caused by using some functions or libraries only available on desktop version. Did you ever enable this plugin on any other iPad/iPhone device? (In my Android devices, this plugin can be enabled without error)
I searched the Obsidian forum, it seems that there is no usable debugging console on these platforms.

Access the Obsidian console on iOS app

If someone is interesting in contributing and testing with their iPad devices, I’d be glad to accept contributions.

Thank you for your reply. It's strange that when this plugin is enabled on the repository of the Mac that is synced to the cloud, the repository on the iPad can also work properly. Although I'm not sure why, the plugin can be used now anyway. Thank you for developing this plugin.

Trying to help you guys 😀
@nuthrash  you can emulate Obsidian Mobile on desktop by executing this command on Console

@nuthrash there is a plugin called Obsidian Mobile Logging that copy the console log to a note.
→  This way you can identify what is the error that the plugin is getting on Mobile and send to the developer

I hope it helps 🙏


No search results for common classes

Problem:
I cannot find many classes that used to be commonly searchable and easily found via google.
I went to the document search here: https://docs.microsoft.com/en-us/dotnet/api/?term=ActionFilter&view=netframework-4.7.2
Because I need help with WebAPI ActionFilter (I'm not using .net core)
The documentation simply doesn't exist:  No Results, unless I search under core, but I'm not using core.

I like the new format of the doc browser, but it used to be that one of the coolest things about .net documentation was that if I just put the class name into google, the first or second hit would be the documentation for it.
Nowadays, I have to search all over for the api docs.

Pressing F-1 within Visual Studio leads me to the image below.
Note:   the "no longer updated" message
Note: It's dos for VS 2013 (I'm using 2017)
Note: there is no version switcher option
Note: clicking "return to main site", just returns me to the home page for docs, where I do a search, and get the results that I posted into the description of the issue above.

Thanks for the feedback, @jsmarsch - we are currently working on onboarding ASP.NET APIs to docs (see #90 for details).


WIP: Attempt to fix indexing for Dask

[x] Closes #2511
[ ] Tests added
[ ] Passes pre-commit run --all-files
[ ] User visible changes (including notable bug fixes) are documented in whats-new.rst
[ ] New functions/methods are listed in api.rst

This is a naive attempt to make isel work with Dask.
Known limitation: it triggers the computation.
WIP
The code presented here is mainly to support the discussion on #2511.
It has not been unit tested and should probably not be merged as is.

Hello @bzah! Thanks for opening this PR. We checked the lines you've touched for PEP 8 issues, and found:

In the file xarray/core/indexing.py:

Line 310:61: F821 undefined name 'dask'
Line 323:34: F821 undefined name 'dask'
Line 324:25: F821 undefined name 'dask'


[iOS][TextInput] Fix #18272 TextInput.setNativeProps({text: ''}) to work

Motivation
Fix #18272. Calling textInputRef.setNativeProps({text: ''}) or textInputRef.clear() should clear the text input.
Test Plan

All tests of yarn run test are passed
Test with the sample app.

TextInput.clear() and TextInput.setNativeProps({ text: '***' }) worked
When clear() or setNativeProps() called, onChange/onChangeText wasn't called

Same behavior as react 0.53.0

When non-string values are given to setNativeProps({text: ___}), its behavior is the same as react 0.53.0.

Value Type
Result

null
same as empty string ''

undefined
nothing changes

number
throw error

function
throw error

object
throw error

When clear() or setNativeProps() called, attributed text keeps the attributes
When value prop is set, the text can't be changed

react 0.54.0 (with the bug)

clear() doesn't work from the second time
setNativeProps({text '***'}) doesn't work from the second time
Even when value prop is set, you can change the text

with bugfix

clear() works every time
setNativeProps({text '****'}) works every time

Attributed text with bugfix

The text keeps the attributes (font family, size, color, text align)

value prop with bugfix

If value prop is set, the text should not be changed

Release Notes
[IOS] [BUGFIX] [TextInput] - Fix TextInput.clear() and TextInput.setNativeProps({text: ''}) to work

What is the status of this? The regression fixed by this PR is holding us back from publishing our app so I'm keen to help out in any way I can!

Thank you! I was testing my changes.
I'm going to update this PR and remove "WIP" soon!

I added Test Plan and removed "WIP" from the title.
How can I solve the CI error? It seems to have nothing to do with this change.

I added an attributed text test. (Thank you @reyalpsirc!)
And it seems that CI errors are fixed.

@shergin Thank you for your review!
I looked into the code again, and I guess the problem is that the value of ShadowView is not sync with user input.
If input events are handled correctly, text property doesn't need to be added to UIView instance.
Let me think how to fix it.

I removed text property from RCTBaseTextInputView and added text accessor to RCTBaseTextInputShadowView.
When text native property (or value prop of TextInput component) is explicitly set, text should be compared with the current local text (_localAttributedText) to check if it needs to update.
This change will also fix #18389 (TextInput value not binding on IOS).

News?

This pull request is ready for review.
@shergin Could you please check it?

Any news? When can someone merge this (maybe also cherry pick it for 0.54.5 or 0.55?)

Updates? this fixes my issued and should be merged.

This regression fix has been open for 20 days... It's not that big of a PR either, why is no one merging?

The same is happening for Android on very few devices.

Simple test case with snack expo - https://github.com/HandlebarLabs/code-and-coffee/issues/15#issuecomment-379606414

A more advanced test case with snack expo - https://github.com/HandlebarLabs/code-and-coffee/issues/15#issue-302470239

this bug has been around since 0.54, is this fix going to be merged in 0.56 (April) ?
I find it hard to believe a bug like this makes it to React Native and stays longer than 2 versions around, with a PR submitted almost 2 months ago. For us this bug is a total stopper, thanks.

Created an issue for Android - https://github.com/facebook/react-native/issues/19085 - it's similar but not the same.

https://github.com/pualxiao/React-Native-TextInput-Bug-Fix

Thank you @pualxiao for sharing that copy paste fix!! Was very much needed until this PR gets merged.

@maraujop I know it can be frustrating, but if you look at the history of this PR, you can see it was reviewed by @shergin several times. He asked for changes back in April 11 but @magicien has not responded yet.

It would be nice if it can be group effort. Lots of times the changes requested are harder for the submitter. Ideally the person requesting the changes can help out, they know what they want done.  @magicien already did an extremely amazing job, finding there was a bug, creating a videos to show others before and after, and a possible fix.

@Noitidart I agree with the sentiment, and hopefully it's something we can do more often once we have fewer PRs waiting for review.

@shergin,
any updates?

 Thank you so much.

Is this pull request merged in 0.56??
Or, Is there any workaround??

@Noitidart I agree with the sentiment, and hopefully it's something we can do more often once we have fewer PRs waiting for review.

Understand that, but I suppose this bug should deserve a very high priority.

@sasayahiromu this PR is open and has not been merged to master, so it's not in any release.

@kevinresol feel free to open your own PR. It does not look like the author of this PR, @magicien, is actively working on it, as they have not responded to @shergin's feedback.

as they have not responded to @shergin's feedback.

But I did

Can anyone pick up the work, please? Validation on input texts are basically useless on iOS.
Thanks

Simply unfocusing the textInput solves the problem
<View style={styles.textInputStyle}>

    <TextInput onChangeText={(text) => this.setState({searchText: text}, () => {
                   this.state.searchText.length > 1 ? this._getSearchedData() : null
               })}
               value={this.state.searchText}
               placeholder='Search restaurant or cuisine'
    />

    <TouchableOpacity  onPress={() => {
                    this.setState({searchText: ''}),
                    Keyboard.dismiss()
                }}>
    <Icon name="md-close-circle" style={{color: 'gray', fontSize: 15,}}/>
</TouchableOpacity>

</View>

Hello! If the original author of a PR does not return to answer feedback, is there anything the community can do to help get that PR merged? It's sort of silly to leave huge regressions like this alive in the wild just because a contributor ghosted on five lines of code.

This PR also fixes my issue #20224.
I'm new to React Native and already surprised by the number of very simple bugs 😬

@shergin Could you please check my comment on your review?

@kevboh you can always submit your own PR, making sure to incorporate the feedback brought up here.

@kevboh you can always submit your own PR, making sure to incorporate the feedback brought up here.

The original author has already returned and commented.  @hramos @shengmin Please review

This PR has languished for far too long.  Binding the TextInput value to state is critical for form validation.  Please prioritize merging this into a stable release.

I've already left my thoughts on the status of this PR. No need to @-mention me any more.

@hramos

@shergin please follow up

@shergin please follow up

I updated the diff and added the comment.
It seems that there is something wrong with the test environment.

any updates?

@hramos - See: https://github.com/facebook/react-native/pull/18278#discussion_r210798429 . The requested changes by @shergin 15 days ago was made by original author 12 days ago. Can we get this regression merged now? If @shergin is still MIA on the other project this may sit around indefinitely
Thanks!

@shergin please follow up, thank you very much.

@rowinbot it's imported. Once the reviewer accepts the changes, it will land internally and eventually sync out to github.

I've turned off these types of notifications from the bot for now.
We check the thread for an existing comment from the bot before adding a new comment. I'll need to look into why this failed on this commit.


Update README.md

I propose this change to point out that UIA2 consists of managed library but the underlying automation API is native. I also removed the information about maintainability because in .Net 4.8 there are actually some improvements related to automation.

Thanks. I like the rephrasing and will merge the change.


[MGDOBR-968] - Create Logger action for development

https://issues.redhat.com/browse/MGDOBR-968
PR owner checklist
Please make sure that your PR meets the following requirements:

[ ] Your code is properly formatted according to this configuration.
Run mvn clean verify -DskipTests so that imports are correctly set.
[ ] Your commit messages are clear and reference the JIRA issue e.g: "[MGDOBR-1] - $clear_explanation_of_what_you_did"
[ ] The layers in the kustomize folder have been updated accordingly.
[ ] All new functionality is tested
[ ] Pull Request title is properly formatted: MGDOBR-XYZ Subject
[ ] Pull Request contains link to the JIRA issue
[ ] Pull Request contains link to any dependent or related Pull Request
[ ] Pull Request contains description of the issue
[ ] Pull Request does not include fixes for issues other than the main ticket

PR reviewer(s) checklist

[ ] Check if code and Github action workflows have been modified and if the modification is safe
[ ] If the modification is safe, add the safe to test label

How to trigger pipelines and use the bots:

Run the end to end pipeline
Annotate the pull request with the label: safe to test. If you want to run the pipeline again, remove and add it again.

Rebase the pull request
Comment with: /rebase.

Deploy BOT
Comment with `/deploy <dev,stable> when the PR has been merged to deploy to a target environment.

You cannot add a development Action the way you have.
The whole mechanism of catalogue, lookup and validation needs to be changed to support this.

sorry.. I didn't get you. What need to be change?
It you are looking for test parameter then it because current implementation enforce it. It a bug in current implementation that need to be fixed.


Create BBE for Resource API

Description:
Need to create ballerina guide(BBE) for Resource API.

Resource API feature is on hold for the moment. BBE for Resource AP will be added later once this feature is resumed and finalized.


Index Creation

Hi Daan,
I have a few questions I was hoping you could answer.  For context, I have a repository of training documents containing 12 folders with 2-3 subfolders each.  Within each folder is a markdown file that contains graphics links, text and often a GIF file link.

Is your action capable of crawling through these documents to create topic indexes?
Or is it creating basically a table of contents based on the folder structure?

Thank you in advance for your time.

Hi James.
It's doing a bit of both. it crawls through all your folder as far down as possible looking for markdown files.
if it found any it will create a list of markdown files and store them under "categories".
if it has created an index page, it will be added to the index of files in the folder above it under the header "Documents".

I updated the example picture

Thank you for the clarification Daan.  We will check it out.


purescript-arraybuffer-types#2.0.0

 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.


$window.localMediaStream.stop(); not available on Chrome

This don't work anymore in Google Chrome
https://developers.google.com/web/updates/2015/07/mediastream-deprecations?hl=en#stop-ended-and-active
$window.localMediaStream.stop();
and needs to be replaced by this : (which works one Firefox & Chrome)
$window.localMediaStream.getTracks()[0].stop();

:+1:

I also replaced localMediaStream with MediaStreamTrack. See https://developers.google.com/web/updates/2015/07/mediastream-deprecations?hl=en


cupy Build fails in fedora 27

I was trying to install cupy for chainer in fedora 27, while building, its not able to find stdlib.h. this occurs 4 times in the log. Is this due to gcc version being 7.x?
error pip log portions:
#first time

In file included from /usr/include/c++/7/ext/string_conversions.h:41:0,
                   from /usr/include/c++/7/bits/basic_string.h:6349,
                   from /usr/include/c++/7/string:52,
                   from /usr/include/c++/7/bits/locale_classes.h:40,
                   from /usr/include/c++/7/bits/ios_base.h:41,
                   from /usr/include/c++/7/ios:42,
                   from /usr/include/c++/7/ostream:38,
                   from /usr/include/c++/7/iterator:64,
                   from /usr/include/cuda/thrust/iterator/iterator_traits.h:34,
                   from /usr/include/cuda/thrust/detail/type_traits/pointer_traits.h:23,
                   from /usr/include/cuda/thrust/memory.h:23,
                   from /usr/include/cuda/thrust/device_ptr.h:25,
                   from /tmp/tmpqneyyuui/a.cpp:1:
  /usr/include/c++/7/cstdlib:75:15: fatal error: stdlib.h: No such file or directory
   #include_next <stdlib.h>
                 ^~~~~~~~~~
  compilation terminated.
  command 'gcc' failed with exit status 1

#second time
gcc -pthread -DDYNAMIC_ANNOTATIONS_ENABLED=1 -DNDEBUG -O2 -g -pipe -Wall -Werror=format-security -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector-strong --param=ssp-buffer-size=4 -grecord-gcc-switches -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -m64 -mtune=generic -fasynchronous-unwind-tables -D_GNU_SOURCE -fPIC -fwrapv -I /usr/include/cuda -fPIC -D_GLIBCXX_USE_CXX11_ABI=0 -D_FORCE_INLINES=1 -I/usr/include -I/usr/include/python3.6m -c cupy/core/core.cpp -o build/temp.linux-x86_64-3.6/cupy/core/core.o
  In file included from /usr/include/c++/7/ext/string_conversions.h:41:0,
                   from /usr/include/c++/7/bits/basic_string.h:6349,
                   from /usr/include/c++/7/string:52,
                   from /usr/include/c++/7/bits/locale_classes.h:40,
                   from /usr/include/c++/7/bits/ios_base.h:41,
                   from /usr/include/c++/7/ios:42,
                   from cupy/core/core.cpp:615:
  /usr/include/c++/7/cstdlib:75:15: fatal error: stdlib.h: No such file or directory
   #include_next <stdlib.h>
                 ^~~~~~~~~~
  compilation terminated.
  error: command 'gcc' failed with exit status 1

#third time

In file included from /usr/include/c++/7/ext/string_conversions.h:41:0,
                     from /usr/include/c++/7/bits/basic_string.h:6349,
                     from /usr/include/c++/7/string:52,
                     from /usr/include/c++/7/bits/locale_classes.h:40,
                     from /usr/include/c++/7/bits/ios_base.h:41,
                     from /usr/include/c++/7/ios:42,
                     from /usr/include/c++/7/ostream:38,
                     from /usr/include/c++/7/iterator:64,
                     from /usr/include/cuda/thrust/iterator/iterator_traits.h:34,
                     from /usr/include/cuda/thrust/detail/type_traits/pointer_traits.h:23,
                     from /usr/include/cuda/thrust/memory.h:23,
                     from /usr/include/cuda/thrust/device_ptr.h:25,
                     from /tmp/tmp8_peajaj/a.cpp:1:
    /usr/include/c++/7/cstdlib:75:15: fatal error: stdlib.h: No such file or directory
     #include_next <stdlib.h>
                   ^~~~~~~~~~
    compilation terminated.
    command 'gcc' failed with exit status 1

#last time

gcc -pthread -DDYNAMIC_ANNOTATIONS_ENABLED=1 -DNDEBUG -O2 -g -pipe -Wall -Werror=format-security -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector-strong --param=ssp-buffer-size=4 -grecord-gcc-switches -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -m64 -mtune=generic -fasynchronous-unwind-tables -D_GNU_SOURCE -fPIC -fwrapv -I /usr/include/cuda -fPIC -D_GLIBCXX_USE_CXX11_ABI=0 -D_FORCE_INLINES=1 -I/usr/include -I/usr/include/python3.6m -c cupy/core/core.cpp -o build/temp.linux-x86_64-3.6/cupy/core/core.o
    In file included from /usr/include/c++/7/ext/string_conversions.h:41:0,
                     from /usr/include/c++/7/bits/basic_string.h:6349,
                     from /usr/include/c++/7/string:52,
                     from /usr/include/c++/7/bits/locale_classes.h:40,
                     from /usr/include/c++/7/bits/ios_base.h:41,
                     from /usr/include/c++/7/ios:42,
                     from cupy/core/core.cpp:615:
    /usr/include/c++/7/cstdlib:75:15: fatal error: stdlib.h: No such file or directory
     #include_next <stdlib.h>
                   ^~~~~~~~~~
    compilation terminated.
    error: command 'gcc' failed with exit status 1

Could you please try using wheels to install CuPy? https://docs-cupy.chainer.org/en/latest/install.html#install-cupy-using-wheel

Thanks it Worked!


[BUG] No stable connection when changing networks (LTE -> Wi-Fi -> LTE...)

Your Rocket.Chat.Android version: Rocket.Chat+ 1.0.18
Server: 0.58.2
We cant provide a stable connection between Rocket.Chat+ on different Android Devices and the Rocket.Chat-Sever. We switch a lot between different WLAN-Hotspots and LTE and have a huge problem with the Android-App. The App often says "Authenticating" and nothing happens after a while in the background. You have to restart the App to get a connection to the server. Sometimes when you are connected a message cant get send and you get a "Failed to sync" error. The same behavior is reproducable on different Android devices (in our case: OnePlus 3T with Android 7.1.1, Moto G5 with Android 7.0)
The Server runs via SNAP Installation on a virtual Ubuntu Server. From the Internet an Apache Reverse Proxy handles the connection.
The iOS Rocket.Chat+ App doesn´t have this issues.
Is there a know problem or can i provide further informations to get a fix for this problem?

@ArchimedesFM Thanks for opening the issue! We're working hard to fix those issues with our brand new SDK (http://github.com/RocketChat/Rocket.Chat.Java.SDK) in Android. I'll ask you a bit o patience and wait for new updates in the next months.

@rafaelks Thank you for your answer, but i want to go a bit further. Is this a widely known Problem or a new one? Are you already working on this or is a fix far far away in 2018? We want to roll out Rocket.Chat in our Company on PCs, iPhones and Android devices, but we can not do this with an unstable Android App. Is there any alternative or Workaround in your oppinion?

@ArchimedesFM This is a known issue (and old) in our Android app. I'm really sorry for that, I can assure you we're working really hard to get this fixed.

The problems are still present in Android App 1.0.21.

@ArchimedesFM Yes, we're doing a rewrite in our network layer that is going to fix this problems.

any updates on this? :)

@ccfiel We have a new version available at Google Play on Beta channel. It has many improvements on network issues. It's still not bulletproof but it's a checkpoint for us. Any help on testing it will be appreciated.

@leonardoaramaki  how can I apply for beta test? :) I love to help

@ccfiel It's open to everyone.
Just go to the Rocket.Chat+ app on Google Play and scroll to the bottom to apply :)

Ok got it! 😀
On Nov 12, 2017 6:52 AM, "Leonardo Aramaki"<EMAIL_ADDRESS>wrote:

@ccfiel https://github.com/ccfiel It's open to everyone.
Just go to the Rocket.Chat+ app on Google Play and scroll to the bottom to
apply :)
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/RocketChat/Rocket.Chat.Android/issues/469#issuecomment-343699816,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABtJyFjZG3EiTEUQOGKHgqZdcPRS65F2ks5s1iVAgaJpZM4Pb9k6
.

Using beta version now. So far so good :) I test some more. Hopefully, its now solved. @ArchimedesFM  Try the beta

The connection in beta 1.0.33 is much more stable then in the old release 1.0.18.
I dont know how much of the refactoring is done, but you are on a good way.

@ArchimedesFM Thanks for the feedback! @leonardoaramaki is working hard to fix it! 🎉


[BUG] Missing westus3 in Azure.Core.AzureLocation

Library name and version
Azure.ResourceManager 1.3.2
Describe the bug
westus3 is missing from the Azure.Core.AzureLocation struct.
Expected behavior
/// <summary>
/// Public cloud location for West US 3.
/// </summary>
public static AzureLocation WestUS3 { get; } = CreateStaticReference("westus3", "West US 3");

Actual behavior
The AzureLocation is missing.
Reproduction Steps
No steps.
Environment
No response

Label prediction was below confidence level 0.6 for Model:ServiceLabels: 'Azure.Core:0.09276507,Search:0.088337556,Azure.Identity:0.06268648'

Thank you for your feedback.  Tagging and routing to the team member best able to assist.

@AlexanderSher can you add this new location?

+1 on this issue. SwedenCentral is missing as well. @AlexanderSher @ArthurMa1978
We are trying to migrate off of Fluent SDK, which has been deprecated: https://www.nuget.org/packages/Microsoft.Azure.Management.ResourceManager.Fluent. Fluent supports WestUS3 and SwedenCentral https://learn.microsoft.com/en-us/dotnet/api/microsoft.azure.management.resourcemanager.fluent.core.region?view=azure-dotnet

This has been confirmed to have been added since this issue was last updated.  Resolving.


Gut images

The CL edits in this branch appear to revert accepted edits in merged PRs e.g. see https://github.com/obophenotype/cell-ontology/pull/2711/files
Please recreate edits (image folder, uploaded images, README.md in this PR https://github.com/obophenotype/cell-ontology/pull/2794/files.


lie algebra

Need to map out the definition of a lie algebra
bilinearity: [v1+v2,2] = [v1,w]+[v2,w] and [cv,w] = c[v,w]
skew symmetry: [v,w] = -[w,v] or [v,v] = 0
jacobi: [u,[v,w]] + [u,[w,u]] + [w,[u,v]] = 0
the 6x6 matrix has a determinant path of 0
differential geometry means that there exists a path

An Introduction to Lie Groups and Lie Algebras
Alexander Krillov, Jr.

Solvable

exp of x times exp of y = exp of x + y + 1/2[x,y]
Ex. Commutator


Create a new pull request by comparing changes across two branches

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

2 of 2 (100.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.2%) to 95.78%

Totals

Change from base Build<PHONE_NUMBER>:
0.2%

Covered Lines:
2030

Relevant Lines:
2081

💛  - Coveralls


Monospace check 079 is incorrectly triggered by propotional font in v 0.6.11

Observed behaviour
Currently, in Fontbakery 0.6.11, check 79 tells me that Encode Sans seems to be a monospace, with a self-contradicting message:
⚠ WARN: Monospace font has hhea.advanceWidthMax equal to each glyph's advanceWidth?
⚠ WARN This seems to be a monospaced font, so advanceWidth value should be the same across all glyphs, but 99.67% of them have a different value

This happens with both Condensed and Expanded versions of Encode.
I suspect that we may have set the math slightly wrong in the monospace check. If 99.67% of glyphs have a different width value, a font is almost certainly not intended to be monospace.
Expected behaviour
Guestimates
I expect that a font with anything above maybe 20% or so of glyphs with variable width is not at all trying to be monospace. A font is probably monospace if 95%+ of glyphs have the same width.
If the check were even smarter, it could also detect the amount of variation in metrics. That is, if a bunch of glyphs are within a small range of widths (say, ±5% or so), it may be a sloppy monospace font.
One example of real metrics that should fail
Roboto Mono, which is on the more-variable side of monospace fonts, has about 3.25% of its glyphs with a width other than 1229 units (out 2048 UPM) in the upright Medium instance. In the Medium Italic instance, there are also 3.25% of its glyphs with widths different from the rest of the glyphs, but the main width here is 1202, which is different from the upright glyphs.
See https://github.com/google/fonts/issues/1832 for more details.
Taken together, these fonts should certainly fail this check. Matching widths between styles is one thing (and I've filed a separate issue specifically for this at https://github.com/googlefonts/fontbakery/issues/2365). However, even these internal consistencies should fail check 079.
However, Encode Sans is very much a proportional design, and should not trigger this warning.
Resources and exact process needed to replicate
I am specifically seeing this warning while I build split-width variable fonts in https://github.com/thundernixon/Encode-Sans.
It was not the case in Fontbakery 0.6.10 (example checks), but it is now an issue with v 0.6.11 (example checks).

In #2349 I refactored check 033 so only the ascii glyphs are used to determine whether a font is monospace. I did this so CJK fonts which contain proportional Latin glyphs are not marked as monospace.
I will need to update this check as well.

Interestingly, the shared condition glyph_metrics_stats is never used in the check. this feels like a pointless check but I'll see what I can do next week.

To me, this (or something like it) seems like a really important check.
That makes sense to need a way to avoid flagging CJK fonts as monospace, and shows that we can't rely on a percentage of all glyphs. Limiting check to just ASCII characters seems a bit limited, though, and would (I think) miss most of the issues in Roboto Mono.

Fixed in #2368.


Refactor custom middlewares out of server

As server.tsx has grown I've found it harder to navigate around as a lot of functionality is defined inline, some of which we don't have to touch very often.
This is a first step to refactor some functionality out into separate modules.

Thanks @nicl!


Behavior of 'end' key is incorrect if 'show spaces' is not enabled

With show spaces on, the 'end' key jumps to the end of the line, after any whitespace.
With show spaces off, it jumps to the end of the line, but before any trailing whitespace.
The behavior should be consistent between the two settings. Also, I think the first behavior is more useful -- trailing whitespace usually is unintentional, and one should be able to find it by pressing 'end'. Notepad++ also jumps to the end of line after trailing whitespace.

It might be worth noting that the cause of the inconsistency was textLine.TrailingWhitespaceLength... the value of this property always seems to be 1 when 'show spaces' is on, no matter how many spaces there actually are.

I would like to lobby to have this fixed, or at least overridable. User has reported the issue in https://github.com/mike-ward/Markdown-Edit/issues/105

I believe the first line of GetEndOfLineCaretPosition() should use
textLine.NewlineLength
instead of
textLine.TrailingWhitespaceLength
See
https://github.com/Microsoft/Windows-classic-samples/blob/cded84bed49cb8ef2095e6470ac83ee3264c4113/Samples/Win7Samples/multimedia/DirectWrite/PadWrite/TextEditor.cpp#L1382

PR #140


refactor(executor): swap the ptr and size in u64 return value

why this change?

Just make it complied with the convention that substrate does


[UIFlow 2.0] [JP] Unit-Fader (additional)

Additional translation the "Fader" unit in UIFlow 2.0 under the Unit category into Japanese.

Translation is finished.


feat: 🎸 add useGetSetState

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Bug: Fast Tagging uses incorrect mouse position

when u move mouse and click on histogram it will use wrong position
solution: save mouse coordinate when user press ctrl d

Hi, thanks for creating an issue. This is actually the current implementation. Are you using any zoom factors at windows? Or the actual overlay? Could you maybe provide a short gif. Thanks!

Hi,
I think I'm also hitting this issue. Very often, when I try to fast tag an item, it will fail and instead trigger an ability/open chat. I'm in windowed full screen 1680x1050. vSync enabled, no zoom.
I noticed that when I used windows step recorder that it has not failed once out of over 20 tries (usually fails well before that). Race condition maybe?
Gif of the bug in action!  https://gfycat.com/revolvingnearbrahmanbull

I just started using this program today. I have noticed that it works for a specific portion of the stash tab and other portions of it will cause the chat dialog to open and not set the price. Kinda weird, I think it is not recording the position of the cursor correctly. I am enjoying the program otherwise.
Win 10
1920x1080
Vsync enabled
no zoom
desktop
steam


Simplify regex and test on Turkish locale

I remove RegexOptions.IgnoreCase since somehow this break the whole recognition on Turkish locale and I don't see any point have it. We already define both uppercase and lower case letters in the regex. Alternative for A-Za-z is to use \w and for 0-9 use \d, so maybe this will lead to more reliable version recognizer. If strict fragment rules needed they should be placed to RegexOptionalFragment, but I was unable to make this work reliable so far.
See #253

Great job figuring this out! The docs do actually call out the ignoreCase can cause issues on Turkish locale (see https://msdn.microsoft.com/en-us/library/yd1hzczs.aspx#Invariant ). Using \w or \d would include non-ASCII characters in a .NET RegEx unless ECMAScript mode is enabled, so using the character ranges explicitly is still the best way to go here I think. Other comments on the code.

Nice job tracking this down! In addition to Bill's comments... let's go ahead and catch this exception during GetCatalog (and print to the output window) so that people aren't left empty handed if parsing fails (as we do with ArgumentException)
https://github.com/Microsoft/nodejstools/blob/master/Nodejs/Product/Npm/SPI/NpmGetCatalogCommand.cs#L143-L148

Probably was too late to debug this issue, now patch is much more clean. I just have to remove RegexOptions.IgnoreCase
@mousetraps and @billti please review.

minor comment, but lgtm other than that!

@kant2002 I presume you mistakenly closed this since it looks like you restored your branch too, so I went ahead ad re-opened it :smile:

True. I just add reporting of the message in case of invalid package semversion


Check disabled dates whithin the range.

it's is normal? It's not suppose to enable only the next disable day after start date?
Currently it's enable all day so I can range hover a complete booking...

@sonia360 can you elaborate a more detail example?

Exemple:
disable date : june 3, june 5, june 10
If I choose june 2 it's suppose to enable checkout on june 3 only right?. but I can pass over all date it's enable checkout on all date. So a user can book on already booked date

That's right, but check for disabled dates in between of a range is not a feature of the datepicker right now. Could be added but is not a bug, it's a missing feature if you like.
I am afraid that you are going to check this issues externally, but if you want you can provide a PR with the solution and I will tested and incorporate in the 2.x branch.
Can you do it?

I encounter the same issue just now and working to see what I can do to resolve this now.

Check v4.0.0-beta.2


manifest.json support

Is possible to have this also for manifest.json ?

Currently using transformIndexHtml hook, not support manifest.json.

Currently using transformIndexHtml hook, not support manifest.json.

Is there another way to do manifest.json then?

You can try to read dist/manifest.json, use buildEnd or closeBundle hook.

You can try to read dist/manifest.json, use buildEnd or closeBundle hook.

idk if I will be able to, this is why I choosed this


Bug: changing the interval doesn't take effect

Hi,
I changed the interval to 30 minutes but it took no effect and the auto-shelve keeps on shelving each 5 minutes.

Same here.

Does the interval change if you restart Visual Studio?

Yes.
On 9 Mar 2018 2:46 pm, "Jason Vercellone" <notifications<EMAIL_ADDRESS>wrote:
Does the interval change if you restart Visual Studio?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHubhttps://github.com/vercellone/tfsautoshelve/issues/20#issuecomment-371816102, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AALNd-T3mx0cPSNUEosEweh5z1m_Rjn6ks5tcoekgaJpZM4OpICJ.

OK.  That is the workaround.
As for the root cause...There is an event handler which is supposed to trigger reloading the configuration based on the options form entry.  It may have been a glitch where the event didn't fire for reasons unknown, or it might be that the event is not wired up correctly.  Can you tell me which version of Visual Studio, so that I can inspect the code in the appropriate branch?

Community 2017 Version 15.5.6, framework 4.7.02556.  TFS Autoshelve 6.2
installed via Visual Studio.
Personally I'm happy with the workaround.
But there is another problem.  The output pane shows that lots of files are
being shelved but when I look at the shelve set I don't see all of them.
Not sure if this is a bug or a misunderstanding on my part.
Kevin
On 9 Mar 2018 11:17 pm, "Jason Vercellone"<EMAIL_ADDRESS>wrote:

OK. That is the workaround.
As for the root cause...There is an event handler which is supposed to
trigger reloading the configuration based on the options form entry. It may
have been a glitch where the event didn't fire for reasons unknown, or it
might be that the event is not wired up correctly. Can you tell me which
version of Visual Studio, so that I can inspect the code in the appropriate
branch?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/vercellone/tfsautoshelve/issues/20#issuecomment-371961033,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AALNd10B8Olaq33e7EBEj_SCcaf_9Q3Nks5tcv9rgaJpZM4OpICJ
.

Thanks.  That'd be the current master branch.  I'll take a look at the event registration code.
Do you have multiple workspaces? If so, make sure your shelveset name includes {0} as a placeholder for the workspace name, else you'll end up with 1 shelveset with changes from the last workspace to get shelved.

Just for completion's sake; I think i must have misunderstood how it works becuse now that I have added the date to the shelveset name I can see more files in the shelvesets.
Anyway, thanks for a useful tool.


[Feature]: IMPROVE SEO SCORE BY ADDING IMPORTANT META ELEMENTS 🚀

Description

I want to add important Meta elements because in HTML they play a crucial role in providing information about the webpage to browsers and search engines.
Meta elements in HTML serve various purposes, including defining document encoding, improving search engine visibility, enhancing social media sharing, optimizing for mobile devices, and influencing browser behavior.
Utilizing appropriate meta elements can significantly impact how webpages are perceived, indexed, and shared on the internet.

Checklist

[X] I have checked the existing issues
[X] I have read the [Contributing Guidelines]
[X] I am willing to work on this issue (optional)
[X] I am a GSSoC'23 contributor

Please assign this issue to me @ShwetKhatri2001.

Hi @0xabdulkhalid! There is already issue #84  present covering these points.
Tell me what kind of changes you will make, I'd like to know whether it's different from that issue or not.

Hey there @ShwetKhatri2001, he is only mentioning meta tags for description and keywords.
But the description is already present, and keyword is isn't enough.
There are crucial other Meta elements like "og:title," "og:description," and "og:image" are part of Open Graph protocol and are used for social media sharing. When a webpage is shared on platforms like Facebook or Twitter, these meta elements provide specific information such as the title, description, and image to be displayed, enhancing the visual appeal and context of the shared content
I want to add every important meta elements to this site to boost site's vital score and performance.

Okay, Go ahead and implement this. You're assigned.


SSIM Loss

HI, you mentioned that SSIM loss is used to encourage the original image structure in your paper. And it's reasonable. Recently, I want to add ssim loss to image segmentation to increase the building extraction performance. In my experiment, the ssim training loss is convergence well while the SSIM result between pred segmentation result and GT is lower than before.
I'm really confused. Any answer or suggestion will be thankful!

"In my experiment, the ssim training loss is convergence well while the
SSIM result between pred segmentation result and GT is lower than before."
I am not sure about the details of your experiments. SSIM Loss =  1 - SSIM.
If your SSIM Loss is decraseing, the SSIM should be increasing. Of course,
you need to test on a relatively big image set and get the average SSIM,
individual image may not reflect the correct trend.
On Mon, Aug 12, 2019 at 8:36 PM xuyingxiao<EMAIL_ADDRESS>wrote:

HI, you mentioned that SSIM loss is used to encourage the original image
structure in your paper. And it's reasonable. Recently, I want to add ssim
loss to image segmentation to increase the building extraction performance.
In my experiment, the ssim training loss is convergence well while the SSIM
result between pred segmentation result and GT is lower than before.
I'm really confused. Any answer or suggestion will be thankful!
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/NathanUA/BASNet/issues/9?email_source=notifications&email_token=ADSGORIRLPOCOM2YJN33DYTQEIM4TA5CNFSM4ILGRKPKYY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4HE3FSRA,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ADSGORKFDOGFSSCDVC6L62DQEIM4TANCNFSM4ILGRKPA
.

--
Xuebin Qin
PhD Candidate
Department of Computing Science
University of Alberta, Edmonton, AB, Canada
Homepage:https://webdocs.cs.ualberta.ca/~xuebin/


Why is generateStaticParams not used for generating the different product pages?

Why wouldn't it be used for product/[handle]?

You totally can! Could be a future addition to this demo 👍


the new pom.xml content for kafka 0.7.2 sink

if you do package under the original pom.xml, you could get some issues, just like too many license, etc.
now I supply a new dependence pom.xml for this cleared kafka07 sink project to my friend - Frank. thanks.
ps: just remember package command is "mvn assembly:assembly -DskipTests=true"
=======================Gorgeous split line===========================

================================================================

hello, can you share the jar package with us?

@hzruandd this project has been merged into flume release branch. Kafka source/sink is available in flume now. What you need to do is download flume and enjoy it:)


Upgrade to cdk v2

Fixes #

Upgrade cdk version to use CDK 2.2.0
Tests have also been upgraded to use aws-cdk-lib/assertions
Can read more about cdk by visiting the AWS CDK Reference Document
Some formatting changes by using prettier

removing formatting changes


MarkdownExporter.Default.ExportToLog fails with NRE for Summary with Critical Validation Errors

Bench.Net 0.9.5, summary obtained from run with critical errors (e.g. run with Validators.JitOptimizationsValidator.FailOnError on debug build).
Call to the MarkdownExporter.Default.ExportToLog() fails at MarkdownExporter.PrintTable(), as the SummaryTable passed is null.

Honestly I am not sure if it was a bug, because BenchmarkRunner would not call any export if summary has some critical validation errors but I have fixed it anyway ;)


Misc fixes

The changes made fixed the error, thank you so much! Btw, does the lib directory serve any purpose?

No problem, happy I could help!
No, the lib folder isn't special, it's just a common pattern for storing "library" or "utility" files. You can rename this if you'd like.
Also, would you mind marking this comment as the accepted answer on our discussion? Thanks 😄

The changes made fixed the error, thank you so much! Btw, does the lib directory serve any purpose?

No problem, happy I could help!
No, the lib folder isn't special, it's just a common pattern for storing "library" or "utility" files. You can rename this if you'd like.
Also, would you mind marking this comment as the accepted answer on our discussion? Thanks 😄

The changes made fixed the error, thank you so much! Btw, does the lib directory serve any purpose?

No problem, happy I could help!
No, the lib folder isn't special, it's just a common pattern for storing "library" or "utility" files. You can rename this if you'd like.
Also, would you mind marking this comment as the accepted answer on our discussion? Thanks 😄

Sure, i'll gladly do that, i'll also give you a follow here and i'll love to connect with you if you don't mind that haha.

Sure, i'll gladly do that, i'll also give you a follow here and i'll love to connect with you if you don't mind that haha.

Sure thing! I'm most active on Twitter and here on GitHub.


Can't go backwards after reaching the last slide

When 'infinite' is set to false, if you reach the last slide and keep clicking on "Next", the slider keeps incorrectly updating the states of the previous slides. So, if you then want to go backwards, you'll have to click on "Previous" as many times (more or less) as you clicked on "Next".
====================================================================
https://jsfiddle.net/ignaciodeele/ojp9ktot/5/
====================================================================
Steps to reproduce the problem

Click on "Next" until you reach the last slide ("Nine").
Click on "Next" six more times.
Click on "Previous" five to seven times, until it works.

====================================================================
What is the expected behaviour?
After reaching the right end of the slider, if you keep clicking "Next" you should be able to go back just by clicking only once on "Previous". This is indeed how the left end works (if you are seeing the first slide and click on "Previous" many times, it only takes a single click on "Next" to move forwards).
By the way, it would be a nice feature to set the button as 'disabled' when there are no more slides to show.
====================================================================
What is observed behaviour?
You have to click on "Previous" many times, instead of just one, to see the previous slides.
====================================================================
More Details

Which browsers/versions does it happen on?
Firefox 45.0.2, Chrome 49, IE 11
Which jQuery/Slick version are you using?
jQuery 2.2.3, Slick 1.5.9

Hey @ignaciodeele Check this issue out: #2146
Definitely a little confusing. Hope that helps.


Trying to import a dependency using an ESM import() statement fails

Describe the bug
I am trying to dynamically import a dependency from node modules, based on a condition. In this case I want to use the package https://www.npmjs.com/package/@gtm-support/vue-gtm for google tag manager. This package is a Vue plugin but I don't want to import it and register the plugin based on some condition I receive from my infra during startup.
The code looks roughly like this
if (optionalTracking) {
  const { createGtm } = await import('@gtm-support/vue-gtm');
  app.use(createGtm({ id: 'GTM-1234567', defer: true }));
}

This works during dev, but not during build. I debugged the unminified prod build output and it seems like the __vitePreload function has a promise that silently fails, cannot be caught and simply halts execution. Then then clause is never executed, and neither is code that follows the import statement.

I've looked around multiple issues and the only one that seems to ring a bell is this closed one
https://github.com/vitejs/vite/issues/2009
where it's mentioned that this __vitePreload function could fail and never resolve. Though still could be unrelated, I'm not sure.
Is what I'm trying to achieve not possible/currently supported? Or am I missing something that might be in the docs?
Reproduction
https://stackblitz.com/edit/vitejs-vite-tdaeem?file=src%2Fmain.js
Steps to reproduce
You'll notice the app will start just fine for dev mode. I've added the serve package which allow you to run the prod build. So if you execute:
> npm run build
> serve -l 5173 dist/

You'll see that the app is no longer mounted.
System Info
System:
    OS: Linux 6.6 Manjaro Linux
    CPU: (16) x64 AMD Ryzen 7 PRO 4750U with Radeon Graphics
    Memory: 3.09 GB / 30.58 GB
    Container: Yes
    Shell: 5.9 - /usr/bin/zsh
  Binaries:
    Node: 20.11.0 - ~/.volta/tools/image/node/20.11.0/bin/node
    npm: 10.2.4 - ~/.volta/tools/image/node/20.11.0/bin/npm
    pnpm: 9.1.4 - ~/.local/share/pnpm/pnpm
  npmPackages:
    @vitejs/plugin-vue: ^5.0.4 => 5.1.2
    vite: ^5.1.6 => 5.4.2

Used Package Manager
npm
Logs
No response
Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Make sure this is a Vite issue and not a framework-specific issue. For example, if it's a Vue SFC related bug, it should likely be reported to vuejs/core instead.
[X] Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
[X] The provided reproduction is a minimal reproducible example of the bug.

It look like this is a top-level-await dead lock as @gtm-support/vue-gtm chunk is importing nextTick from vue in the entry chunk. This is a duplicate of https://github.com/vitejs/vite/issues/16520#issuecomment-2076268800. See linked comment for the workaround.

It look like this is a top-level-await dead lock as @gtm-support/vue-gtm chunk is importing nextTick from vue in the entry chunk. This is a duplicate of #16520 (comment). See linked comment for the workaround.

hm, Interesting.... I have other top-level awaits on my main file though and those have been working fine so far. Only this new change seems to be causing it. Nevertheless I will test it out