Segmentation fault when using stub created from SSL channel credentials

What version of gRPC and what language are you using?
C++, error found in gRPC 1.45.0 and 1.46.3.
What operating system (Linux, Windows,...) and version?
Ubuntu 18.04
What runtime / compiler are you using (e.g. python version or version of gcc)
gcc/g++ version 11.1.0 (Ubuntu 11.1.0-1ubuntu1~18.04.1)
What did you do?
I created a channel as follows, according to the tutorial:
auto channel = grpc::CreateChannel(
  "localhost:50053", grpc::SslCredentials(grpc::SslCredentialsOptions()));

The server address did not matter, the segfault occured regardless of that value and before any connection was attempted. Using a client stub that was instantiated with this channel resulted in a segfault. I was able to reproduce with a variety of different credentials, each resulting in the same issue:
// Create SSL channel credentials
grpc::SslCredentialsOptions ssl_opts = {read_file(root_ca_location), "", ""};
auto channel_creds = grpc::SslCredentials(ssl_opts);

auto channel = grpc::CreateChannel("localhost:50053", channel_creds);

// Create TLS channel credentials
grpc::experimental::TlsChannelCredentialsOptions options;
auto channel_creds = grpc::experimental::TlsCredentials(options);

auto channel = grpc::CreateChannel("localhost:50053", channel_creds);

What did you expect to see?
An attempt at a connection to a secure server located on port 50053 of the same machine, written in Golang.
What did you see instead?
I observed a segfault.
Stack trace:
stack-trace.txt
gRPC Debugging logs:
grpc-debug.txt
Anything else we should know about your project / environment?
When I switched from BoringSSL to a system installed version of OpenSSL (1.1.1-1ubuntu2.1~18.04.17) using set(gRPC_SSL_PROVIDER package) in CMake, this error went away. Previously, I added BoringSSL to the CMake using set(gRPC_deps third_party/boringssl-with-bazel ...).

@ZhenLian can you take a look at this? There appears to be a crash in loading the certificates.

I suspect this might due to different string interpretations of OpenSSL/BoringSSL versions. Try adding a terminating NULL("\0") to your root certificate string?
It seems the error comes from the function PEM_ASN1_read_bio(https://man.openbsd.org/PEM_ASN1_read.3). You can also try loading your root certs into a string and read that string with this function, to see if that would cause a crash.

This appears to affect the python package too. Traceback when code encounters a seg fault:
Environment
python version - 3.8.7, grpc version - 1.45.0, os - Debian GNU/Linux 10 (buster)
File "/usr/local/lib/python3.8/threading.py", line 890 in _bootstrap
File "/usr/local/lib/python3.8/threading.py", line 932 in _bootstrap_inner
File "/usr/local/lib/python3.8/site-packages/sentry_sdk/integrations/threading.py", line 67 in run
File "/usr/local/lib/python3.8/threading.py", line 870 in run
File "/usr/local/lib/python3.8/site-packages/grpc/_plugin_wrapping.py", line 89 in call
File "/usr/local/lib/python3.8/site-packages/google/auth/transport/grpc.py", line 101 in call
File "/usr/local/lib/python3.8/site-packages/grpc/_plugin_wrapping.py", line 61 in call

@ZhenLian

I suspect this might due to different string interpretations of OpenSSL/BoringSSL versions. Try adding a terminating NULL("\0") to your root certificate string?

The string is null terminated. Confirmed that by printing and inspecting the last byte as well

Adding @erm-g in case there is any further investigation that's needed.

I'm having the same issue on gRPC v1.56.0 and 1.58.0. I've tried using the test certificates shipped with the source but the result is identical. All cert strings are null-terinated as double-checked with gdb. Here is the relevant part of the backtrace:
#0  0x00007ffff7b089b9 in BIO_gets () from /lib/x86_64-linux-gnu/libcrypto.so.3
#1  0x00007ffff7c528a8 in PEM_read_bio_ex () from /lib/x86_64-linux-gnu/libcrypto.so.3
#2  0x00007ffff7c5353f in ?? () from /lib/x86_64-linux-gnu/libcrypto.so.3
#3  0x00007ffff7c53a1f in PEM_bytes_read_bio () from /lib/x86_64-linux-gnu/libcrypto.so.3
#4  0x00007ffff7c53ac0 in PEM_ASN1_read_bio () from /lib/x86_64-linux-gnu/libcrypto.so.3
#5  0x0000555555b66722 in ssl_ctx_use_certificate_chain(ssl_ctx_st*, char const*, unsigned long) ()
#6  0x0000555555b66c94 in populate_ssl_context(ssl_ctx_st*, tsi_ssl_pem_key_cert_pair const*, char const*) ()
#7  0x0000555555b6a284 in tsi_create_ssl_server_handshaker_factory_with_options(tsi_ssl_server_handshaker_options const*, tsi_ssl_server_handshaker_factory**) ()
#8  0x0000555555ac0487 in (anonymous namespace)::grpc_ssl_server_security_connector::InitializeHandshakerFactory() ()
#9  0x0000555555ac0ca6 in grpc_ssl_server_security_connector_create(grpc_core::RefCountedPtr<grpc_server_credentials>) ()
#10 0x0000555555ab8c2b in grpc_ssl_server_credentials::create_security_connector(grpc_core::ChannelArgs const&) ()
#11 0x000055555597e50b in grpc_server_add_http2_port ()
#12 0x00005555556410cc in grpc::SecureServerCredentials::AddPortToServer(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&, grpc_server*) ()
#13 0x00005555556540b1 in grpc::Server::AddListeningPort(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&, grpc::ServerCredentials*) ()
#14 0x0000555555646ece in grpc::ServerBuilder::BuildAndStart() ()

Relevant bits of the code:
auto read_file(std::string path) -> std::string
{
    std::ifstream ifs(path);
    if (!ifs) {
        exit(1);
    }

    std::string content((std::istreambuf_iterator<char>(ifs)),
                        (std::istreambuf_iterator<char>()));

    ifs.close();

    /* remove trailing newline */
    if (content.at(content.length() - 1) == '\n') {
        content.pop_back();
    }
    /* ensure null-termination */
    if (content.at(content.length()-1 != '\0')) {
        content.push_back('\0');
    }

    return content;
}

int runGrpcServer(...) {
    [...]

    const std::string key_path("grpc/src/core/tsi/test_creds/server0.key");
    const std::string cert_path("grpc/src/core/tsi/test_creds/server0.pem");
    const std::string root_path("grpc/src/core/tsi/test_creds/ca.pem");

    auto ssl_server_cred_opts = grpc::SslServerCredentialsOptions();
    auto ssl_root_cert_pair = grpc::SslServerCredentialsOptions::PemKeyCertPair();
    ssl_root_cert_pair.private_key = read_file(key_path);
    ssl_root_cert_pair.cert_chain = read_file(cert_path);
    ssl_server_cred_opts.pem_key_cert_pairs.push_back(ssl_root_cert_pair);
    ssl_server_cred_opts.pem_root_certs = read_file(root_path);
    ssl_server_cred_opts.client_certificate_request = GRPC_SSL_DONT_REQUEST_CLIENT_CERTIFICATE;
    auto channel_creds = grpc::SslServerCredentials(ssl_server_cred_opts);
    ServerBuilder builder;
    builder.AddListeningPort(server_address, channel_creds);
    builder.RegisterService(&service);
    server = builder.BuildAndStart();

I created a standalone test case with just the gRPC code above and it works normally, so the problem appears to be when gRPC is built using boringSSL and the application it is being used from is linking against openSSL for its own functionality, like in our case.

Closing based on the most recent comment.


gossip registry

I'm experiment with gossip registry and may be found some specific issue. When i'm start first service1 with
specify gossip.Address("<IP_ADDRESS>:4223") and on other server service2 with registry.Addrs("<IP_ADDRESS>:4223") and gossip.Address("<IP_ADDRESS>:0")
i see that members equal 2 on both sides, but the second service does not registered in registry.
But  if i stop service1 and start it with registry.Addrs("<IP_ADDRESS>:4223") and gossip.Address("<IP_ADDRESS>:xxx") where xxx is port provided by service2 all works fine.
So issue appears only on first service1 when it start first without other members.

yes, txt records can be concatenated, but this is also limits to udp packet size

If you have a good solution please propose or PR it. Otherwise you can disable adding endpoints when you register handlers https://godoc.org/github.com/micro/go-micro/server#InternalHandler


docs(contributing): update contributing doc

:tada: This PR is included in version 2.16.0-alpha.1 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:

:tada: This PR is included in version 2.16.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


space checks created for microk8s subpaths

Checks are created for microk8s subpath volume, e.g.:
stg-bootstack-managed-k8s-lma-microk8s-0-check_space_var_snap_microk8s_common_var_lib_kubelet_pods_c43afd69-49d1-4b7f-b7a7-dd01b548511f_volume-subpaths_charm-data_charm-init_2
The charm only checks if the paths starts with:
/var/lib/kubelet/pods"
on our microk8s install, the path is:
/var/snap/microk8s/common/var/lib/kubelet/pods/
See
https://git.launchpad.net/charm-nrpe/tree/hooks/nrpe_helpers.py#n818
It might also affect other types of volumes, but so far I've only seen it for the subpath, since it does a bind mount.

(by marcusboden)
Alternatively, or additionally, we may want to detect and ignore bind mounts anyway. Having separate space checks for each bind mount seems unnecessary.


Context menu loses focus due to positioning.

Version
2.9.2
Test Case

Steps to reproduce
When we right click on the edges or furthermost right or bottom, context menu goes outside the area and the control over the context menu is affecting due to that.
Expected Behavior
Adjust according to the position.
Actual Behavior
Context menu control loses when clicking on the edges of furthermost right or bottom.

Issue resolved when applied z-index to the context-menu.


feature(backend) Status-IR: add MLMD client to persistence agent and support for Status-IR

Original Issue: https://github.com/kubeflow/pipelines/issues/8964
This issue looks like it's gone stale, reach out to kfp community and see if we can help contribute to this effort.
Note:
This is a reference issue for internal tracking purposes, please forward all discussion to the actual upstream issue.
When assigning this, please confirm this is already not in progress upstream.

Migrated to Jira: https://issues.redhat.com/browse/RHOAIENG-1618


Handle different board sizes

We need to work on this to make it compatible with the computer player. (We should add computer player's board matrix for larger boards)


Updated classic Makefiles for Oracle Express 11.2.

This pull request brings the classic Makefils up-to-date with the Oracle Express 11.2 (in fact, it should be version-agnostic) edition and fixes some missing bits that accumulated during the recent evolution of SOCI and that were not taken into account in the Makefiles.

Do we still use these makefiles at all? I had no idea they had to be maintained to be honest...

On 28 May 2015 23:52, "VZ"<EMAIL_ADDRESS>wrote:

Do we still use these makefiles at all? I had no idea they had to be
maintained to be honest...

Maciej created those makefiles as he prefers to use them. So, he was taking
care of the maintenance.

+1 feel free to merge

Please note that this patch contains the include/private/soci_backends_config.h file - this file is #included from sources, but does not exist in the repository. My understanding is that it is generated by CMake, but it should be confirmed - and that this generation is not obscured by the presence of this file.
As for the need for these Makefiles - please note that they provide the shortest and at the same time the most exact (and verifiable by execution) documentation of (external) dependencies. CMake is great in that it automates some things, but at the same time it hides them, making it more difficult for others to integrate the whole source tree with other build systems. You might not need them, but I prefer to keep them for reference.

[https://github.com/SOCI/soci/blob/48a8bfab0e4a735bcd623a4d03071bd7536aa822/src/core/CMakeLists.txt#L19-L21 src/core/CMakeLists.txt generates] uses [https://github.com/SOCI/soci/blob/cf76df6c404314df2986130ac1de28bf97090fcb/src/core/soci_backends_config.h.in src/core/soci_backends_config.h.in] as input to generate this header.
CMake will still generate the header, but in build directory. So, there will be two versions of the headers and order of includes might matter. I can't check it myself, but I'd worry about it after merge..

The patch was corrected - the file in question is now regenerated by src/core/Makefile.basic, which means that it is not needed in the patch. Now the only files that are modified by the patch are 3 Makefiles, which should be safe with regard to the remaining part of the repository.

I'll take the liberty of merging it then, it doesn't seem useful to just keep it sitting here.


#9739 Set proxy setting from environment variables, falling back to p…

Implements #9739 allowing the proxy target to be set using environment variables and falling back to package.json if none exists.
Tested by running a project with the change applied.

Ran with no proxy environment variable, but with proxy in package.json. Result: Used proxy from package.json
Ran with proxy environment variable and package.json. Result: Used proxy from environment variable
Ran with proxy environment variable and none in package.json. Result: Used proxy from environment variable

CLA completed

Still needed.


Initial Commit - Mike Gowland

Category

[x] New Sample

What's in this Pull Request?
Power Apps Calendar Component

Awesome work @sgtsnacks-64 !


 I'll do that this weekend before merging if you feel appropriate to change your vote.

I opened https://github.com/Azure/azure-sdk-for-rust/issues/294 to track moving (exposing) request methods from the pipeline itself, like with our other SDKs, to abstract away the requests from the wire protocol.

I opened #300 to further the discussion on how we want the guidelines to end up in this regard.


Travis CI warnings / issues

Our firmware build is using Travis and the CLI to do test builds, but it looks like maybe something is off about the two combined.  Any chance we can fix this part of the build?  Is it just a matter of not using the deprecated module, and using the new one?
https://travis-ci.org/spark/firmware/builds/64131560
Thanks! :)
edit: reviewed this some more, looks like the CLI is adapting and skipping modules it can't find dependencies for.  Looks like the thing failing the build is:
!!! Install it now by running npm install -g particle-cli
12580
spark variable did not return an integer. Network connectivity problems?

I would recommend trying particle-cli. We haven't updated spark-cli in quite awhile.

The error came from here - https://github.com/spark/firmware/blob/e28f4256ba132f788d07eb39af4e511745568e88/ci/test_memory_available_with_real_core.sh#L99
There needs to be an actual CI core setup for the test and the output means there's probably not one online


#1551 read.csv behind Data Import dialog should appear in REPL

Make temp file less 'temporary' so re-invoking command from history would work
Reuse file name rather than generating it every time
Don't delete converted file so command from history won't fail
Add asserts to workflow operations that require UI thread calls

:+1:


FID scores in README.

I read the code fid.py and found that it calculates intra FID rather than FID.
Thus I doubt whether the FID scores reported in README is actually intra FID.
Hope you can reply at your convenience. Thx!

I think it is the mean of intra FIDs.

I think it is the mean of intra FIDs.

Thx!
However, I check the original results of intra FID in the paper, finding 83.7 reported which is much higher than one GPU version Res-SAGAN in README (64.8).
I am fairly confused. Guess it could be FID rather than intra FID?
It has been 2 years since this repo got released. Thx for your reply!

This implementation is quite different from official implementation as I made this before official implementation came out, and I didn't experimented on full imagenet. (only on 10 classes)

This implementation is quite different from official implementation as I made this before official implementation came out, and I didn't experimented on full imagenet. (only on 10 classes)
Also, using pytorch inception model for calculating FIDs is not very appropriate - it will report FIDs lower than when using tensorflow inception. You will need to use like this https://github.com/mseitzer/pytorch-fid if you want to calculate FID in pytorch.

Thx!
I think the implementation of self attention itself is right though the entire net is different. At least it is OK for a light, fast and fair experiment with only one GPU : ).
Thus I conduct a simple comparison using DC-SAGAN in this repo's model.py as a baseline. FID of  DC-SAGAN is approximately 85 while intra FID is 222 (All 1000 classes in ImageNet 128*128, 1500K & ~3 weeks, TTUR 1:5, batch size 64).  It is enough for a simple comparison since simple baseline may enlarge the performance gap to make more significant differences.
FID & intra FID reported above has been rewrited to ensure it is comparable with other results using original InceptionV3 in pytorch. You may add this result to README if it is helpful.
I will futher conduct formal comparisons in tf, which might be much heavier : ). Thx for your help.


Check the top-level render call using

<EMAIL_ADDRESS>dev

next dev

ready - started server on <IP_ADDRESS>:3000, url: http://localhost:3000
info  - Loaded env from /content/.env
event - compiled client and server successfully in 1594 ms (173 modules)
wait  - compiling...
event - compiled successfully in 228 ms (139 modules)
wait  - compiling / (client and server)...
event - compiled client and server successfully in 2.1s (1321 modules)
Warning: Each child in a list should have a unique "key" prop.
Check the top-level render call using . See https://reactjs.org/link/warning-keys for more information.
at Home (webpack-internal:///./pages/index.tsx:29:78)
at main
at MyApp (webpack-internal:///./pages/_app.tsx:14:18)
at StyleRegistry (/content/node_modules/styled-jsx/dist/index/index.js:449:36)
at PathnameContextProviderAdapter (/content/node_modules/next/dist/shared/lib/router/adapters.js:60:11)
at AppContainer (/content/node_modules/next/dist/server/render.js:291:29)
at AppContainerWithIsomorphicFiberStructure (/content/node_modules/next/dist/server/render.js:327:57)
at div
at Body (/content/node_modules/next/dist/server/render.js:614:21)
At the same time, when i send message, An error occurred while fetching the data. Please try again.
I found that the author has previously addressed this issue and I am using the latest version of the code. I don't know why the problem still occurs.

That 'Warning: Each child in a list should have a unique "key" prop.' does not prevent one from using the app. The real issue here is with the fact that you got an error while fetching the data. Can you share more details on that?

If the server responded iwth status code 500, it means that either your pinecone or openai api configuration is not set up correctly.


Defer TransformFlags Calculation

Background
Today, TypeScript aggregates TransformFlags on every node upon construction. This makes it possible to keep track of specific language features that must be transformed later on in our emit pipeline. If a node does not contain specific transform flags, certain passes can avoid walking over a region of the tree (or avoid walking over a tree entirely).
However, this incurs an overhead on every single node in our syntax trees, regardless of whether TypeScript is being used for emit. If a developer uses TypeScript strictly for type-checking, then these transform flags may not be justified. Even if TypeScript is being used for emit, this information may never be requested in editor scenarios.
Furthermore, TransformFlags may become less relevant over time. Back when we introduced the emit pipeline, we had a lot of different transformations that might need to be performed based on every language target. We wanted to do as few walks of a given tree as possible, but I would like to revisit some of the core assumptions we had back then. In the last few years, we've seen that:

users are more likely to be targeting recent ECMAScript targets (or not even using our emit pipeline!), and therefore request fewer transforms in the first place.
with the exception of decorators, the amount of work in every language transform since ES2017 has been much much smaller.

In this issue, I'd like to explore the possibility of deferring the calculation of transformFlags on nodes, or removing them entirely.
Proposal
The chief idea is to remove the transformFlags property from every node in the tree. Instead of using a property, we could store this information in a Map during the emit pipeline on a given SourceFile, or global WeakMap as soon as node hits the emit pipeline. Depending on which, this could mean that re-emitting a SourceFile might require recalculating this information; but it could also mean that less information would have to be stored between building different files.
One upside to this is that with this strategy, TransformFlags don't need to be stored unless the target is low enough in the first place; so this would become more of a pay-for-play feature.
The downside is that this would require a walk of the tree to calculate the transformFlags for a given node. More on that below.
Challenges and Possible Solutions
Requiring Extra Walks
As mentioned above, when you do need to emit, you would need to walk the tree to calculate the TransformFlags for each node. Doing this at bind-time is tempting, but that would mean all that information needs to sit around regardless of when it is used. In general, and especially for incremental build scenarios, it would be more ideal to only hold on to this information when needed.
We could do a walk per a file. That's not ideal, but it is more pay-for-play.
Another thing to note is that most nodes go through at least one transform anyway: the TypeScript transform. We could modify that transform to act more like a full tre walk, but could then calculate the TransformFlags for subsequent transforms.
Reducing Passes
While doing this could relieve us of memory pressure in non-emit scenarios, it's very likely that Maps and WeakMaps have a higher memory overhead and lookup cost. One way to offset this might be to fold a few of the existing transform steps into a single step. For example, can the ES2020, ES2021, and ES2022 transforms be combined into a single transform? These transforms tend to be relatively simple, and this would reduce some of our code size, along with the number of top-down walks to transform, say ??=.
Non-Transform Uses of TransformFlags
One challenge is that TransformFlags are used in a few places in the compiler - not just in the emit pipeline. We use this information to avoid deeper walks of our trees in the type-checker, and in the language service. We would need to ensure that we don't regress performance in these areas.
Forgetting to Propagate TransformFlags
One of the nice parts of how our node factories work is that they by-default always aggregate the transformFlags of their children, and introducing a new node makes it easier to notice that you need to call aggregateTransformFlags. One of the counter-arguments to moving aggregation into an existing non-dedicated pass is that historically when we did that, we often ended up with bugs from miscalculation. Still, it's possible for these flags to be miscalculated in the current node factory system.

A relatively easyish experiment to start out with would be to

Drop the tranformFlags field from every node
Drop all usage of TransformFlags from outside the emit pipeline and make those walks unconditional
Make every transformer unconditional

Or possibly just make transformFlags a getter that returns all possible TransformFlags as set. Then we could see what this does for memory and speed.

I tried the above suggestion as it wasn't too hard to do. There's more here in the "non-transform" case, unfortunately; a lot of stuff depends on these flags past just for performance, e.g. we use it to know when we need to reparse for await, to avoid transforming code when it would behave the same without transform, detecting if JSX was ever used within a specific subtree, and seemingly to make decisions about how to transform generators and such.
I pushed my attempt to https://github.com/jakebailey/TypeScript/tree/transform-flag-hack-test, but it's also possible that I just did it wrong.


bug fix and removed unwanted code for image slider

Fix #114
Test URLs:

Before: https://main--aldevron--hlxsites.hlx.page
After: https://feature-imageslider--aldevron--hlxsites.hlx.page/test/imageslider

why not just remove the code vs commenting it out?

Removed the commented code and added changes for bug #135

@dkuntze  - thank you for the review.  This has now been amended, can you please review again?  Thanks.


Add Object.is polyfill

Fixes #2718.

Changelog Entry
Fixed

Fixes #2718. Add Object.is polyfill for IE11, by @compulim in PR #2719

Description
Usage of Object.is was added in #2710 but the polyfill for ES5 browsers was not added.
Specific Changes

Add corejs/features/object/is to ES5 bundle

[x] Testing Added

Manual test steps

Load ES5 bundle in IE11, the UI should show up

Coverage remained the same at 61.108% when pulling 89f814e80b8cba7d838e1f7aaafa65ace994a451 on compulim:fix-2718 into 9e43da0b413efc369f823e4278e2444e3fb0b5b3 on microsoft:master.


File doesn't open after "Successfully read remote file"

I can view my remote directory fine in the remote-edit file browser. When I select a file to open, I get the usual display messages--including "success"--but the file isn't opened after that. I've tried with multiple remote servers, directories, and files. I see no error messages. Is there a log or something I can paste to help someone dig into this? Is anyone else having this problem?

Same here.  (Same problem as #143, by the way.)  Installed Atom just this morning to use exactly this package, and it's broken.  ::great sadness::

Thanks for the link @theclapp and sorry for the repost!


mvm broken

also what's about recompile textures for mvm, but with NO LEVEL OF DETAIL?!

Is this broken for you on the latest version of the hud? I don't have any issues on a resolution that is near to yours:

@rbjaxter , OwO you returned!
that problem exist in lobby, in left top corner you can see, i not alone

sorry for the delays, I haven't been working on my hud in a long time.
I've since tested this with/without someone in the party and can't replicate this unfortunately.


Update API examples

I updated the list examples once again, because some entries were still wrong.
Another thing I found is the proxy function for URLs:
The description for the parameter shortURL is
short url ID, without the domain, eg. if your short URL is `m3o.one/u/someshorturlid` then pass in `someshorturlid`

But the example request is
-d '{
  "shortURL": "https://m3o.one/u/ck6SGVkYp"
}'

I mean it works but you don't use only the ID as described in the parameter description, should we change it?

Added new ID types to examples

@asim NanoID is implemented through one of the last pull requests, but it is not added as a type.
Therefore you can not use it. Am I right?
https://github.com/a0v0/services/blob/da7b9eee7c58d9eba3d4c18580c18f1d3a85241d/id/handler/id.go#L51-L58

@asim NanoID is implemented through one of the last pull requests, but it is not added as a type. Therefore you can not use it. Am I right?
https://github.com/micro/services/blob/813a9ed4edb07fab062a5cd932ddbbc925510515/id/handler/id.go#L51-L58

Yea that's right

I will fix this in a seperate PR to keep everything organized

What about the URL thing I mentioned in the PR description above?
Should we change something there?

What about the URL thing I mentioned in the PR description above? Should we change something there?

Leave the URL for now. I'll look later.

Alright, then you can approve the changes and merge it.


hasMany() + where() returns where conditions in opposite order

Using the following:
return $this->hasMany(Text::class, 'item_id')->where('item_type', 'product');

Will make a query like this:
select * from texts where item_type = 'product' and texts.item_id in ('1', '2', '3', '4', '5', '6', '7', '8', '9', '10')

When it should be like this:
select * from texts where texts.item_id in ('1', '2', '3', '4', '5', '6', '7', '8', '9', '10') and item_type = 'product'

The functions are called in the following order: hasMany() + where() but the where conditions are in the following order: where() + hasMany().

Thanks for the report. Please can you provide the exact Laravel version you are using?

@GrahamCampbell
Laravel Framework version 5.2.37

The hasMany() will always be the last where condition regardless how many where()s is following it.

@unskaa does the order matter?

I'm not sure. It might with partial composite indexes.
Even if it didnt matter its illogical.
On Jun 18, 2016 1:54 AM, "Mohamed Said"<EMAIL_ADDRESS>wrote:

@unskaa https://github.com/unskaa does the order matter?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/laravel/framework/issues/13994#issuecomment-226899986,
or mute the thread
https://github.com/notifications/unsubscribe/AHxZExkwAG_JmXWCzhvMBsLQwvFdbyBXks5qMyW7gaJpZM4I2EF7
.

I don't think the order of where clauses matters.

I think if it's indexed, it does matter? https://dev.mysql.com/doc/refman/5.7/en/multiple-column-indexes.html

@unskaa @bbashy This is not a actually a bug but just the way Eloquent works. User defined conditions will always be applied first, eager load constraints second and relation conditions third.That's because relation conditions are not even known until the parent query has already executed.
Anyway, there is no way to change this since it's a design decision, so I suggest closing this issue.


Update mkdirp and fix build issues

Previous upgrade of mkdirp package failed to run styleguidist build process. According to their changelog, this version switches from using callbacks to promises - which makes wrapping usage inside promisify fail.  Does not appear to fail anywhere else.

Coverage remained the same at 84.878% when pulling db7b6dcca17c7e2c980675cdea46e6a4990aa777 on snyk-fix-2f51adebebe6ff1b56fd60e119ad0f60 into ad9c4e5a8b6a2fdca957cdf2bfa2e35152393cfd on develop.


Add tar errors output

Unpack procedure failures output is unuseful:
Unpack firmware package ...               [FAIL]
exited with status 1. Output:

This adds output error messages from tar command and improves UI.
It will now look like:
Unpack firmware package ...               [FAIL]
exited with status 1. Output:
tar: write error: No space left on device

Signed-off-by: Alexander Filippov<EMAIL_ADDRESS>

Just rebased


Unable to build--maturin failed, the module name must not contain a minus '-'

Following the instructions from https://medium.com/inside-in-sight/high-performance-python-sort-tracker-225c2b507562 resulted in a build failure, with the message maturin failed, the module name must not contain a minus '-' .  I edited the pyproject.toml file to change the project name back to similari (no -trackers-rs) and the build worked.

Hello, @bwmcin. I need to check because, recently, CI was able to build everything with a new naming scheme which enabled uploading to PyPi.

@bwmcin the problem is fixed.

I was able to successfully build Similari with the new updates.  Thank you for the quick response.
bwmcin
From: Bitworks LLC @.>
Sent: Friday, June 02, 2023 10:55 PM
To: insight-platform/Similari @.>
Cc: bwmcin @.>; Mention @.>
Subject: Re: [insight-platform/Similari] Unable to build--maturin failed, the module name must not contain a minus '-' (Issue #102)
Hello, @bwmcin https://github.com/bwmcin . I need to check because, recently, CI was able to build everything with a new naming scheme which enabled uploading to PyPi.
—
Reply to this email directly,  https://github.com/insight-platform/Similari/issues/102#issuecomment-1574689493 view it on GitHub, or  https://github.com/notifications/unsubscribe-auth/AC3OYU5J25I6XBZZRSEDD4TXJLGTJANCNFSM6AAAAAAYY66WEU unsubscribe.
You are receiving this because you were mentioned.  https://github.com/notifications/beacon/AC3OYU2FCMY5CFZAMUMWV4DXJLGTJA5CNFSM6AAAAAAYY66WEWWGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTS53PNNK.gif Message ID: < @.> @.>


Warning: Encountered two children with the same key,     in App. Keys should be unique so that components maintain their identity across updates. Non-unique keys may cause children to be duplicated and/or omitted — the behavior is unsupported and could change in a future version.

when i run > npx gltfjsx models/gltf/xbot.glb --root public/ --verbose`
i get this error
arning: Encountered two children with the same key, `    in App`. Keys should be unique so that components maintain their identity across updates. Non-unique keys may cause children to be duplicated and/or omitted — the behavior is unsupported and could change in a future version.
    in ink-box (created by Box)
    in Box (created by ErrorOverview)
    in ink-box (created by Box)
    in Box (created by ErrorOverview)
    in ErrorOverview (created by InternalApp)
    in InternalApp

  ERROR  Objects are not valid as a React child (found: Error: Invalid hook call. Hooks can only be called inside of the body of a function component. This could happen for one of the following reasons:
        1. You might have mismatching versions of React and the renderer (such as React DOM)
        2. You might be breaking the Rules of Hooks
        3. You might have more than one copy of React in the same app
        See https://fb.me/react-invalid-hook-call for tips about how to debug and fix this problem.). If you meant to render a collection of children, use an array instead.
            in ink-text (created by Text)
            in Text
            in ink-box (created by Box)
            in Box
            in App
            in App
            in InternalApp

 - 1. You might have mismatching versions of React and the renderer (such as React DOM)
 - 2. You might be breaking the Rules of Hooks
 - 3. You might have more than one copy of React in the same app
 - See https://fb.me/react-invalid-hook-call for tips about how to debug and fix this problem.). If you meant to render a collection of children, use an array instead.
 -     in ink-text (created by Text)
 -     in Text
 -     in ink-box (created by Box)
 -     in Box
 -     in App
 -     in App
 -     in InternalApp
 - throwOnInvalidObjectType (node_modules/ink/node_modules/react-reconciler/cjs/react-reconciler.development.js:4524:15)
 - createChild (node_modules/ink/node_modules/react-reconciler/cjs/react-reconciler.development.js:4757:7)
 - reconcileChildrenArray (node_modules/ink/node_modules/react-reconciler/cjs/react-reconciler.development.js:5008:25)
 - reconcileChildFibers (node_modules/ink/node_modules/react-reconciler/cjs/react-reconciler.development.js:5374:14)
 - reconcileChildren (node_modules/ink/node_modules/react-reconciler/cjs/react-reconciler.development.js:7865:28)
 - updateHostComponent (node_modules/ink/node_modules/react-reconciler/cjs/react-reconciler.development.js:8387:3)
 - beginWork$1 (node_modules/ink/node_modules/react-reconciler/cjs/react-reconciler.development.js:9969:14)
 - Object.invokeGuardedCallbackImpl (node_modules/ink/node_modules/react-reconciler/cjs/react-reconciler.development.js:11563:10)
 - invokeGuardedCallback (node_modules/ink/node_modules/react-reconciler/cjs/react-reconciler.development.js:11740:31)
 - beginWork$$1 (node_modules/ink/node_modules/react-reconciler/cjs/react-reconciler.development.js:15778:7)

could you append the glb?

https://github.com/mrdoob/three.js/blob/dev/examples/models/gltf/Xbot.glb its this one, just one of the standard threejs gltf models

cant reproduce unfortunately, runs through here :-(

I am also encountering the same problem when executing the same command with the model in this codesandbox public/stacy.glb.

I am also encountering the same problem when executing the same command with the model in this codesandbox public/stacy.glb.

@drcmda i will do some work and put together a PR to try and make the error message less cryptic. let me know if you can provide any context / pointers otherwise ill get started on it later tonight. thank you :)

@drcmda i will do some work and put together a PR to try and make the error message less cryptic. let me know if you can provide any context / pointers otherwise ill get started on it later tonight. thank you :)

awesome! good luck also, i still can't reproduce :-(

awesome! good luck also, i still can't reproduce :-(

After a few tests, I found out that the error I was encountering was because I installed the package locally. Everything is working well when I install it globally.

After a few tests, I found out that the error I was encountering was because I installed the package locally. Everything is working well when I install it globally.

I can confirm. Got the same error when running locally, where installing globally fixed it.


nice ci

Return the alarm type for Alarmist.current_alarms/0
fixup! Return the alarm type for Alarmist.current_alarms/0
Give CircleCi a little more time

Sigh. Apparently that's not enough time.


I need to create user password and project and api secrets

I'm using the helm chart version is  registry: ghcr.io/langfuse
repository: langfuse
tag: "1.31"
I need to create these on deployment time
langfuse_secrets:
LANGFUSE_INIT_PROJECT_NAME: "My Project"
LANGFUSE_INIT_PROJECT_PUBLIC_KEY: "lf_pk_1234567890"
LANGFUSE_INIT_PROJECT_SECRET_KEY: "lf_sk_1234567890"
LANGFUSE_INIT_USER_NAME: "john doe"
LANGFUSE_INIT_USER_EMAIL<EMAIL_ADDRESS>LANGFUSE_INIT_USER_PASSWORD: "password123"
NODE_ENV: production
langfuse-dev db url deployed through terraform
DATABASE_URL: postgresql://:@<endpoint_url>/test
generate using openssl rand -base64 32
NEXTAUTH_SECRET:
generate using openssl rand -base64 32
SALT:
NEXTAUTH_URL:
TELEMETRY_ENABLED: "true"
FOR THE FIRST TIME MAKE IT "false" AND THEN "true" AFTER YOU HAVE GOTTEN PUBLIC and SECRET KEY
NEXT_PUBLIC_SIGN_UP_DISABLED: "false"
LANGFUSE_ENABLE_EXPERIMENTAL_FEATURES: "false"
This is my values.yaml file I can sign in invalid users

@umar-rayn Could you add a couple more sentences on the behaviour that you observe vs. the behaviour that you would expect to see? To me, it is not entirely clear what you're requesting.

I'm trying to create user project and API keys during deployment in Helm.I passed the variables as an env but the user project and API are not created successfully I can't see any error in the logs

@marcklingen Could you take a look here as you may have a better idea on why the init feature may not work as expected.

Happy to help. Do you get any logs from the Langfuse instance at startup?

@umar-rayn Happy to help. Do you get any logs from the Langfuse instance at startup?

The logs have only migration logs, not any error or init think in logs could you please first verify the values.yaml I'm passing variables INIT-* is it the right way?

Thanks for pointing me to the variables again. The issue here is that you do not initialize an organization. From the docs:

The different resources depend on each other in the following way. You can e.g. intialize an organization and a user wihtout having to also initialize a project and API keys, but you cannot initialize a project without also initializing an organization.
Organization
├── Project      (part of organization)
│   └── API Keys (set for project)
└── User         (owner of organization)

Adding this again as a troubleshooting step to the docs.

@umar-rayn
Thanks for pointing me to the variables again. The issue here is that you do not initialize an organization. From the docs:

The different resources depend on each other in the following way. You can e.g. intialize an organization and a user wihtout having to also initialize a project and API keys, but you cannot initialize a project without also initializing an organization.
Organization
├── Project      (part of organization)
│   └── API Keys (set for project)
└── User         (owner of organization)

Adding this again as a troubleshooting step to the docs.

Sure, I need help automating the signup process, project creation, and API key generation. I can't find the APIs for signing up, creating projects, and generating keys in the API documentation. Can you assist me in setting up a form in Terraform to automate these processes?

@umar-rayn this is not supported yet, headless initialization configures a single project/org/user/api-key-pair
See docs: https://langfuse.com/docs/deployment/self-host#initialization
If you are interested in an admin-api, please upvote this thread: https://github.com/orgs/langfuse/discussions/1007

Closing this issue, please share if adding the org as mentioned above does not resolve the problem here


Error when starting weffe for the second time

Hi ! I've got an error when I restart weffe (great job btw).
Example:
weffe -a
weffe -r

works perfectly fine
But when I close the terminal and re-open an other and redo this:
weffe -a
weffe -r

I've got an error
...
Press [q] to stop, [?] for help
[video4linux2,v4l2 @ 0x55fd0908e440] ioctl(VIDIOC_G_FMT): Invalid argument
Could not write header for output file #0 (incorrect codec parameters ?): Invalid argument
Error initializing output stream 0:0 --
Conversion failed!

Is the first process still running? e.g. if you run ps aux | grep weffe does it show a task running?
Alternatively, this may be because the input webcam stream is already being used by another application.

if you run ps aux | grep weffe does it show a task running?

Unfortunately no :disappointed:
I think there is an error when re-creating a blank virtual webcam. If I retry weffe -a, it doesn't print any errors but I can't see/select the virtual webcam in chrome (for example)

Same problem.. :(

weffe -a is supposed to create the virtual webcam by loading v4l2loopback, a kernel module. Right now there's no wrapper command to remove this kernel module although running sudo modprobe -r v4l2loopback would undo that (I can add this soon). Can you tell me if that works? If so, I may make weffe -a automatically remove an existing v4l2loopback module before reactivating it.
As a side note, was Chrome opened before weffe -a was run? Sometimes the kernel module has to be activated and the virtual webcam has to be streaming when a program is opened for that software to recognize it.

Can you tell me if that works? If so, I may make weffe -a automatically remove an existing v4l2loopback module before reactivating it.

I can confirm that running sudo modprobe -r v4l2loopback before weffe -a definitively works ! :tada:

I've just merged this change so you can rerun weffe -a without the modprobe commnad. Hope this helps!


depends_on :formula should take install flags

Refs https://github.com/donmelton/video-transcoding-scripts/issues/8#issuecomment-69292480.
There is currently at least one case where it’d be useful (the referenced issue). Homebrew does it; could we perhaps leverage that?
Looking now at the relevant code. From what I gather, we’d need to both add the option to supply install flags and a way to check if the relevant formula was compiled with the relevant flags (since it currently only checks if it was installed at all).

Checking whether it was compiled with the relevant flags is simple enough; we'd just need to parse the output of brew info formula or brew info --json=v1 formula.
A trickier question, I think, is how to support this in the DSL. At the moment, depends_on :formula can be given a string or an array. From here, there are a couple of ways we could incorporate install flags.
We could permit only one formula per depends_on clause, with an optional :options key that takes an array of strings. This would open the floor to further extension, such as minimum version requirements. For example:
depends_on :formula => 'mkvtoolnix'
depends_on :formula => 'ffmpeg',
           :version => '>= 2.5.2',
           :options => %w{ --with-faac --with-fdk-aac }

This method seems the most straightforward and readable to me. It is also the most consistent with Homebrew's depends_on syntax.
Alternatively, we could allow :formula to be an array of strings and/or hashes...
depends_on :formula => [
  { :name => 'mkvtoolnix' }, # or just 'mkvtoolnix'
  { :name => 'ffmpeg', :version => '>= 2.5.2', :options => %w{ --with-faac --with-fdk-aac } }
]

...or a hash of hashes...
depends_on :formula => {
  'mkvtoolnix' => {},
  'ffmpeg'     => { :version => '>= 2.5.2', :options => %w{ --with-faac --with-fdk-aac } }
}

I find the latter two options pretty clunky and unattractive. Are there any other alternatives you guys can think of? This was just a quick brainstorm.

I agree the first one looks better. We’ve never been shy about repeating stanzas (app, binary, name), and most dependencies should be easy enough to declare (just the name — extra options being the exception). I’m definitely for it.

Alright, so how about a stricter requirement, then? Each depends_on stanza may only contain one of:

:formula with optional :options (and any future args such as :version)
:cask with optional :options (and any future args such as :version)
:macos
:arch
:x11
:java

This reduces complexity by allowing us to assume exactly one dependency per depends_on stanza.

I also see no problem with that. Most casks have only one depends_on anyway.

@jawshooah the purpose of defining DSL 1.0 (#4688) is to have a standard from which we will not remove anything.  New functionality should be added in ways that add to the existing DSL, or leave the existing DSL unchanged.
Also, please note that this issue has already been assigned.  We use assignments as a way to avoid duplicating efforts.

@rolandwalker Right, but I can't find anything in the roadmap or docs specifying that a depends_on stanza should be allowed to contain multiple dependencies. Restricting it to one dependency per stanza would simplify the backend and better mirror Homebrew functionality. It also helps that only a few casks (<10 in the main repo, by my count) would need to change as a result.
And sorry about that, I didn't notice that @ndr-qef had already self-assigned this.

We appreciate contributions. My self-assignment was largely meant as a warning not to start an implementation before I had the chance to comment, in the interest of avoiding preventable mistakes.
First, as @rolandwalker noted, it is unadvisable to break forms defined in the DSL v1; any change should be incremental. There is room for argument, partly because depends_on is recent and fairly unused, but backward compatibility is a better baseline for discussion.
With regard to syntax, we should avoid nested forms. @rolandwalker in particular expressed concern over “creeping braces”, as exemplified by uninstall :script. That means that adding key-value pairs, as in your first proposal, is preferrable to more contrived alternatives.
More relevantly to the issue at hand, we cannot be cavalier about preexisting installations. Aborting is the most we can do if we detect a formula which fails to meet our version and option requirements. Given that Homebrew formulae are latest-only, I would focus on adding options and postpone version

Closing in favour of https://github.com/caskroom/homebrew-cask/issues/22825.


All fixes wrapped up

This wraps up #150, #152, and #153. This should ensure that the travis build passes.

Thanks for both the fixes and pulling them all together. I'm aiming to block out some time this weekend to poke around the individual CRs.
I admit I'm a little confused about the build comments, latest build I see on master shows green: https://travis-ci.org/striglia/pyramid_swagger?branch=master. Maybe you're just referring to adding back in the pyramid 1.6 support?

@striglia thanks for building pyramid_swagger in the first place!
The travis build report doesn't say which version of pyramid it's installing, and I imagine that the virtualenv was created a long time ago, which means it's using an old version of pyramid. The bug caused by pyramid 1.6 is also caused by pyramid>1.5.4. If you add the -r flag to tox, I believe the bug will be recreated on master.

@striglia: @sontek cleaned up his fix for pyramid 1.5.4+ support, looks much cleaner!

Ah good eye. I had assumed Travis was blowing away environments between runs, but your explanation matches the symptoms here :) If @sontek doesn't mind, I'll probably just collect any comments in this PR for ease of reading.

Sounds good to me!

merged, pushed, tagged as v2.2.3, and published to https://pypi.python.org/pypi/pyramid_swagger/. Thanks for the help and patience :smile:  If you have any larger issues or feedback, feel free to open up further issues on the project!


chore: add untracked logo

This PR Adds a logo for untracked tokens

Let's add this logo to the unknown token here -> https://github.com/InjectiveLabs/injective-ts/blob/74fbca6f3da5c82d824568eee564c25bbfe80167/packages/token-metadata/src/utils.ts#L270


[SPARK-20450] [SQL] Unexpected first-query schema inference cost with 2.1.1

What changes were proposed in this pull request?
https://issues.apache.org/jira/browse/SPARK-19611 fixes a regression from 2.0 where Spark silently fails to read case-sensitive fields missing a case-sensitive schema in the table properties. The fix is to detect this situation, infer the schema, and write the case-sensitive schema into the metastore.
However this can incur an unexpected performance hit the first time such a problematic table is queried (and there is a high false-positive rate here since most tables don't actually have case-sensitive fields).
This PR changes the default to NEVER_INFER (same behavior as 2.1.0). In 2.2, we can consider leaving the default to INFER_AND_SAVE.
How was this patch tested?
Unit tests.

Test build #76116 has started for PR 17749 at commit 4c0ff63.

LGTM

Test build #76116 has finished for PR 17749 at commit 4c0ff63.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/76116/
Test PASSed.

LGTM - merging to 2.1. Thanks!

can you close?


SAK-43131 clean the internal id consistently (lowercase)

 Here is an overview of what got changed by this pull request:

Issues
======
- Added 1

See the complete overview on Codacy


Unable to make example work for arducam shield v2

I purchased this arducam:  and am trying to use the example ArduCAM_Shield_V2_Camera_Playback to learn how it works. My issue is that the sketch uploads but nothing occurs on the screen or with button presses. The serial monitor has outputted 3 different things:

"SPI interface Error!" which I believe is caused by
temp = myCAM.read_reg(ARDUCHIP_TEST1); if (temp != 0x55) {  Serial.println(F("SPI interface Error!"));  delay(1000); continue;     } else{  Serial.println(F("SPI interface OK"));break; } 	   (98-105) but I don't know what it requires me to do to fix it. I can't find documented anywhere regarding this issue.

"⸮⸮⸮⸮⸮⸮\⸮ܸ⸮\⸮⸮񦸇\⸮ܸ⸮⸮⸮⸮⸮\⸮⸮⸮⸮⸮⸮ ... etc". I haven't been able to find the source of this print but it occurs after the interface error

At one point I was able to make it output "background(69, 70, 70)" once about every second or so (the parameter values change frequently as well). I don't know how I managed it but the touchscreen and camera still remained unresponsive

I haven't been able to find anything that explains to me how to use the arducam or how to make the examples work. I followed all the instructions (like uncommenting proper devices in memorysaver.h) so I don't get why it doesn't work.
I'm hoping someone knows why this is happening as I've been researching this for hours to no avail. I appreciate any and all help. Thanks!

@Stryker69669
Hi,
Please refer to this link to get morehelp:
http://www.arducam.com/knowledge-base/arducam-shield-v2-tutorial/

I've done all that properly. That's not where my issue is coming from.

@Stryker69669
Hi,
Don't worry and we will try our best to help you.Have you test other demos for Shield V2 ?
You can attach us some pictures for your problems.


struggling with nd4j-jcublas initialization

Hi,
I'm getting the following error ..
Exception in thread "main" java.lang.ExceptionInInitializerError
at com.newikov.neuralnetworks.arquitecture.TestNd4JCuda.main(TestNd4JCuda.java:11)
Caused by: java.lang.RuntimeException: org.nd4j.linalg.factory.Nd4jBackend$NoAvailableBackendException
at org.nd4j.linalg.factory.Nd4j.initContext(Nd4j.java:4525)
at org.nd4j.linalg.factory.Nd4j.(Nd4j.java:141)
... 1 more
Caused by: org.nd4j.linalg.factory.Nd4jBackend$NoAvailableBackendException
at org.nd4j.linalg.factory.Nd4jBackend.load(Nd4jBackend.java:148)
at org.nd4j.linalg.factory.Nd4j.initContext(Nd4j.java:4522)
... 2 more
Can you help me with this? I have been trying to get it running for about a week. I followed absolutely all instructions i have on nd4j manuals. Fixed some other errors on the way. I'm using the latest nd4j version 0.4-rc3.8.
I completed the following steps:

Added path to cl.exe C:\Program Files (x86)\Microsoft Visual Studio 12.0\VC\bin to the PATH

Added to the PATH the folder with: libblas3.dll, libgcc_s_seh-1.dll, libgfortran-3.dll,
liblapack3.dll, libopenblas.dll, libquadmath-0.dll, netlib-native_system-win-x86_64-1.1.dll

I have NVIDIA GTX 980 TI. It's working ok. I checked with Theano/Lasange, Caffe and Aparapi for Java.

in pom.xml i have the following
<properties>
	<nd4j.version>0.4-rc3.8</nd4j.version>
</properties>

<dependencies>

	<!-- <dependency> <groupId>org.nd4j</groupId> <artifactId>nd4j-x86</artifactId>
		<version>${nd4j.version}</version> </dependency> -->

	<dependency>
		<groupId>org.nd4j</groupId>
		<artifactId>nd4j-jcublas-7.0</artifactId>
		<version>${nd4j.version}</version>
	</dependency>

	<!-- <dependency> <groupId>org.nd4j</groupId> <artifactId>nd4j-jblas</artifactId>
		<version>0.4-rc3.6</version> </dependency> -->

	<dependency>
		<groupId>org.nd4j</groupId>
		<artifactId>nd4j-api</artifactId>
		<version>${nd4j.version} </version>
	</dependency>

	<dependency>
		<groupId>com.googlecode.combinatoricslib</groupId>
		<artifactId>combinatoricslib</artifactId>
		<version>2.1</version>
	</dependency>

</dependencies>

What could be the reason?
I would really appreciate any help.
Thank you for your time!

Please come in to gitter for these kinds of questions. We put it on every page of the site for a reason. Thanks!
https://gitter.im/deeplearning4j/deeplearning4j


Error provisioning node silents the error.

Stacktrace:
WARNING	c.g.j.p.c.ComputeEngineCloud#provision: Error provisioning node
com.google.api.client.googleapis.json.GoogleJsonResponseException: 400 Bad Request
{
  "code" : 400,
  "errors" : [ {
    "domain" : "global",
    "message" : "Invalid value for field 'resource.disks[0].initializeParams.sourceImage': 'projects/***-images-prod/global/images/****-ubuntu-1804-lts-20210427131914'. The referenced image resource cannot be found.",
    "reason" : "invalid"
  } ],
  "message" : "Invalid value for field 'resource.disks[0].initializeParams.sourceImage': 'projects/***-images-prod/global/images/***-ubuntu-1804-lts-20210427131914'. The referenced image resource cannot be found."
}

As far as I see the https://github.com/jenkinsci/google-compute-engine-plugin/blob/bb7dcc6ffdd7b5f21a01817c76fbafc5a4765ea4/src/main/java/com/google/jenkins/plugins/computeengine/ComputeEngineCloud.java#L272-L274 does not through an error that can be captured with the https://github.com/jenkinsci/jenkins/blob/677fbb2a81fa8e9a0bc37ad5eca56565612e1f2e/core/src/main/java/hudson/slaves/CloudProvisioningListener.java#L110-L132
See https://github.com/jenkinsci/jenkins/blob/95e85495ca6b26ba61ff4a1bf18d181d5e218bc9/core/src/main/java/hudson/slaves/NodeProvisioner.java#L856-L868

I cannot reproduce this error in 2.189.1 with the latest version of this plugin, so I'll close this issue now


Non-static method Gears\String\Str::contains() should not be called statically

i have "gears/string": "*", in my composer.json file
In the Pdf.php file i changed use Gears\String as Str to use Gears\String\Str and now it is giving me the error:
Non-static method Gears\String\Str::contains() should not be called statically
Somebody tell me what am doing wrong. Thank you

this error was being brought about by the wrong document paths


Display Bug in SelectCar, City page

Display bug in SelectCar, City etc.
Here is a screenshot

Bug page1
Bug page2

I didn't understand what you meant. What are the specific issues? Can they be more detailed? @jacks808

done


Transparent proxy injection into existing K8s clusters

@andraxylia commented on Wed Mar 15 2017

Initial initializer deployment and configuration is merged into istio/pilot. Additional enhancements are pending review (https://github.com/istio/pilot/pull/1104).
The feature is disabled by default in in e2e presubmit tests but can be enabled with -use-initializer flag to bin/e2e.sh. The feature will by enabled by default in istio/pilot after https://github.com/istio/pilot/pull/1104 is merged. The initializer is cluster scoped so any bugs could affect the entire test cluster. We should be prepared to revert to default-off and manually delete the initializer configuration. ClusterPool testing feature will help here (cc @sebastienvas). The feature can be enabled in istio/istio after istio/pilot switch over is complete.

TODO

[x] Merge enhancement PR https://github.com/istio/pilot/issues/1104
[x] Update istio/istio template files for initializer deployment/configuration
[x] Document injection method for istio.io https://github.com/istio/pilot/issues/1046

Automated sidecar injection
By leveraging the alpha initializer feature provided by Kubernetes 1.7, envoy sidecars can now be automatically injected into application deployments when your cluster has the initializer enabled. This enables you to deploy microservices using kubectl, the exact same command that you normally use for deploying the microservices without Istio.

@kyessenov commented on Wed Mar 15 2017
Please reference the upstream issue from Kubernetes. We might get it for 1.7.

@andraxylia commented on Wed Mar 15 2017
Depends on kubernetes/community#132

@andraxylia commented on Thu Mar 30 2017
I opened this issue, hopefully we can enhance PodPreset and re-use functionality:
kubernetes/kubernetes#43874

@ldemailly commented on Fri Jul 28 2017
doc is https://docs.google.com/document/d/1-5rLhv6MbB27lL8l2CWD6kR-eMa13_PPwOScVVZq8bo/

@kyessenov commented on Fri Jul 28 2017
There are two aspects of proxy injection: inserting a sidecar and programming iptables. Rephrased the title to be about the first item.

@ldemailly commented on Fri Jul 28 2017
this is an epic so maybe it should cover both ?

@andraxylia commented on Fri Jul 28 2017
Yes, it's an epic and covers everything. You can open issues and group them under this epic.

@andraxylia commented on Fri Jul 28 2017
The title matches the roadmap item, let's leave it as it is.

@ldemailly commented on Fri Aug 18 2017
epic should not be closed yet

@andraxylia commented on Fri Sep 29 2017
This is done. P1 enhancements are possible, but they will need to be prioritized.

@Promaethius commented on Wed Nov 01 2017
What's the status on this? Istios documentation says it's not ready but all the pull requests and issues are merged and closed respectively.

@ldemailly commented on Wed Nov 01 2017
@Promaethius can you provide a link to where it says it's not ready ?

@Promaethius commented on Wed Nov 01 2017
https://github.com/istio/pilot/blob/master/doc/proxy-injection.md
https://istio.io/docs/reference/commands/istioctl.html#istioctl-kube-inject

Automatic sidecar injection is available on k8s >= 1.9 (see https://istio.io/docs/setup/kubernetes/sidecar-injection.html).


Unable to build Python gRPC service with Bazel

What version of gRPC and what language are you using?
gRPC 1.63.1
python 3.12.1
What operating system (Linux, Windows,...) and version?
macOS Sonoma 14.5
What runtime / compiler are you using (e.g. python version or version of gcc)
python 3.12.1
rgenter@RGENTER-M-040N ~ % gcc --version
Apple clang version 15.0.0 (clang-15<IP_ADDRESS>)
Target: arm64-apple-darwin23.5.0
Thread model: posix
InstalledDir: /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin
rgenter@RGENTER-M-040N ~ %

What did you do?
I have a test that demonstrates that with Bazel 7.2.0, protobuf 27.1 and gRPC 1.63.1, a gRPC service written in Python fails to build on a MacBook Pro with an Apple M3 Pro chip.
My MODULE.bazel file:
"""Test demonstrating failure between Bazel, gRPC and Python."""
module(name = "test", version = "1.0")

bazel_dep(name = "grpc", version = "1.63.1", repo_name = "com_github_grpc_grpc")
bazel_dep(name = "protobuf", version = "27.1")

use_repo_rule("@@com_github_grpc_grpc//bazel:grpc_deps.bzl", "grpc_deps")
use_repo_rule("@@com_github_grpc_grpc//bazel:grpc_extra_deps.bzl", "grpc_extra_deps")
use_repo_rule("@@com_github_grpc_grpc//baze::grpc_python_deps.bzl", "grpc_python_deps")

My BUILD.bazel file:
package(default_visibility = ["//visibility:public"])

load("@com_github_grpc_grpc//bazel:cc_grpc_library.bzl", "cc_grpc_library")
load("@com_github_grpc_grpc//bazel:python_rules.bzl", "py_grpc_library", "py_proto_library")

proto_library(
    name = "service_proto",
    srcs = ["service.proto"],
)

cc_proto_library(
    name = "service_cc_proto",
    deps = [":service_proto"],
)

cc_grpc_library(
    name = "service_cc_grpc",
    srcs = [":service_proto"],
    grpc_only = True,
    deps = [":service_cc_proto"],
)

py_proto_library(
    name = "service_py_proto",
    deps = [":service_proto"],
)

py_grpc_library(
    name = "service_py_grpc",
    srcs = [":service_proto"],
    deps = [":service_py_proto"],
)

My service.proto file:
syntax = "proto3";

package test;

service MyService {
    rpc MyMethod(MyRequest) returns (MyResponse);
}

message MyRequest {
    optional string request = 1;
}

message MyResponse {
    optional string response = 1;
}

When I do:
$ bazel clean --expunge
$ bazel build //:service_py_grpc

I get:
ERROR: /private/var/tmp/_bazel_rgenter/a1a8280059cd89e552f80330d54f1415/external/grpc~/src/python/grpcio/grpc/_cython/BUILD.bazel:25:12: Linking external/grpc~/src/python/grpcio/grpc/_cython/cygrpc.so failed: (Exit 1): cc_wrapper.sh failed: error executing CppLink command (from target @@grpc~//src/python/grpcio/grpc/_cython:cygrpc.so) external/bazel_tools~cc_configure_extension~local_config_cc/cc_wrapper.sh @bazel-out/darwin_arm64-fastbuild/bin/external/grpc~/src/python/grpcio/grpc/_cython/cygrpc.so-2.params

Use --sandbox_debug to see verbose messages from the sandbox and retain the sandbox build root for debugging
Undefined symbols for architecture arm64:
  "_PyArg_UnpackTuple", referenced from:
      __Pyx_Coroutine_Throw(_object*, _object*) in cygrpc.o
      __Pyx_async_gen_athrow_send(__pyx_PyAsyncGenAThrow*, _object*) in cygrpc.o
  "_PyAsyncGen_Type", referenced from:
      __Pyx_PyGen_Send(PyGenObject*, _object*) in cygrpc.o
  "_PyBaseObject_Type", referenced from:
      __Pyx_InBases(_typeobject*, _typeobject*) in cygrpc.o
      __Pyx_setup_reduce(_object*) in cygrpc.o
      __pyx_tp_new_7_cython_6cygrpc__ChannelArg(_typeobject*, _object*, _object*) in cygrpc.o
      __pyx_tp_new_7_cython_6cygrpc__ChannelArgs(_typeobject*, _object*, _object*) in cygrpc.o
      __pyx_tp_new_7_cython_6cygrpc_Call(_typeobject*, _object*, _object*) in cygrpc.o
      __pyx_tp_new_7_cython_6cygrpc__CallState(_typeobject*, _object*, _object*) in cygrpc.o
      __pyx_tp_new_7_cython_6cygrpc__ChannelState(_typeobject*, _object*, _object*) in cygrpc.o
      ...

followed by several thousand more lines complaining about undefined symbols, all of which start with _Py or __Py. This seems to come from Cython, which gRPC apparently depends upon for Python.
If I try to build a C++ service using:
$ bazel clean --expunge
$ bazel build //:service_cc_grpc

The build succeeds.
What did you expect to see?
A successful build.
What did you see instead?
See above.
Anything else we should know about your project / environment?
Nothing that I can think of. I'm happy to answer questions.
NOTE: This is also filed as https://github.com/grpc/grpc.io/issues/1307

Reproduced issue above with Bazel 7.1.2, note that this seems to be Mac M1 specific as all our py targets work fine on linux builds.

Running into the same issue with Bazel 6.5.0 on a M1 Mac with Sonoma 14.6

@q0dr  We don't claim support of MODULE.bazel . We'll welcome any contribution to add support for this.

I was able to reproduce this in a gist, Reproduction of grpc/grpc#37251, and to fix it in https://github.com/bazelbuild/bazel-central-registry/pull/2685. Though by the looks of the presubmit checks, this may necessitate releasing an updated module version instead.

https://github.com/bazelbuild/bazel-central-registry/pull/2685 is in. @q0dr can you update your grpc module to version 1.66.0.bcr.1 and see if it fixes your build?

FYI: I added the additional dependency in cython_library.bzl in #35666.


Does this work for statamic v3?

Nope, Statamic v2 only. For Events, check out my events addon: https://statamic.com/addons/transform/events


Adds preconnect links to essencial external domains

This PR adds preconnect links to optimize performance by establishing early connections to the following third-party origins: bsky.app, bsky.social, and bsky.network. Potential saving of 280ms according to Lighthouse.

Would you mind doing these as well? Thanks!
https://github.com/bluesky-social/social-app/tree/4a158104017e23d876efae8cadf017b9a2c4c77a/bskyweb/templates

wouldn't adding bsky.app be unnecessary since the app is hosted on that very same domain?

Done, @gaearon ;)
@mary-ext, makes all sense. Thanks ;)

I think you got a formatting change in there — mind omitting that?

wonderful, thank you.


Grammar

yes I know there’s a conflict but I can’t fix it as I don’t have a command line to use

I'll take a look after lunch.

Too many conflicts, I'll go through and fix the grammar manually

I'll use this as a reference though, you an English major or something? haha


Wont work with mask

Please describe the issue in as much detail as possible, including any errors and traces.
If your issue is a camera issue, be sure to also post the image generated by running sudo howdy snapshot.
When I try to add a face with my mask on it doesn't work

I've searched for similar issues already, and my issue has not been reported yet.
Linux distribution (if applicable):
Ubuntu
Howdy version (sudo howdy version):
2.6.1

This is intended behavior; your face isn't visible


Add circom info to readme

Adding a link to circom as i couldn't find how to install it before.

Great, thanks!


GPT2-XL in  run_convsent_llama2.py

python examples/run_convsent_llama2.py --hparams_dir /home/jiangkailin/project/EasyEdit-main/hparams/FT/gpt2-xl.yaml --editing_method FT --data_dir /home/jiangkailin/project/EasyEdit-main/knowedit/convsent
0%|                                                                                | 0/800 [00:01<?, ?it/s]
Traceback (most recent call last):
File "/home/jiangkailin/project/EasyEdit-main/examples/run_convsent_llama2.py", line 153, in
metrics, edited_model, _ = editor.edit(
File "/home/jiangkailin/project/EasyEdit-main/../EasyEdit-main/easyeditor/editors/editor.py", line 156, in edit
return self.edit_requests(requests, sequential_edit, verbose, **kwargs)
File "/home/jiangkailin/project/EasyEdit-main/../EasyEdit-main/easyeditor/editors/editor.py", line 332, in edit_requests
edit_evaluation(all_metrics, request, edited_model, i, eval_metric, test_generation, icl_examples, **kwargs)
File "/home/jiangkailin/project/EasyEdit-main/../EasyEdit-main/easyeditor/editors/editor.py", line 310, in edit_evaluation
all_metrics[idx].update(compute_sent_metric(self.model, edited_model, self.model_name, self.hparams, self.tok,metric_kwargs=kwargs["metric_kwargs"][idx], device=self.hparams.device))
File "/home/jiangkailin/project/EasyEdit-main/../EasyEdit-main/easyeditor/evaluate/personality_evaluate.py", line 40, in compute_sent_metric
raise NotImplementedError("currently only support for llama")
NotImplementedError: currently only support for llama

This code only supports llama.
We may support GPT2-XL in the future.

Do you have any further questions?


Build(deps): Bump node-forge from 1.2.1 to 1.3.0 (#3165)

Pull request opened by the merge tool on behalf of #3165

Merged in 758ac6b75657d2482c9f8bbb8f2fc52ca595ba14


Feature/min max improvements

Description:
Related issue (if applicable): fixes 	Fix #6783
Related issue (if applicable): fixes 	Fix #6784
Checklist:
If the code does not interact with devices:

[x] Local tests with tox run successfully. Your PR cannot be merged unless tests pass
[x] Tests have been modified to verify that the new code works.

@stu-gott Thanks for your super fast feedback - can you double check this still works with your CoffeeMachine?

The changes look all fine to me. Good improvements.

This would also require a documentation update.

If you basically agree with my changes (althought it's breaking), I will commit a PR to the docs as well.
Since we already have a breaking change, I would also switch the property "entitiy_ids" to "entities" to align it with "groups" component.

@fabaff Could your please proceed with this PR?

@fabaff Do you think we can go with the changes I made? I's leave entity_ids as it is.

@fabaff Hope it's fine now?


Create new browser extension developer accounts

[ ] Chrome
[ ] Firefox
[ ] Edge
[ ] Opera

@zackkrida, since we are retiring the browser extension, should we close this issue?


chore(npm-script): refactored to reuse commands

Please see inline notes.

Also, makes the build a little bit faster; by 4s
➜  glamor git:(master) date; npm run build > /dev/null; date
Wed Oct 26 18:27:03 PDT 2016
Wed Oct 26 18:27:15 PDT 2016
➜  glamor git:(chore/npm-script) date; npm run build > /dev/null; date
Wed Oct 26 18:27:32 PDT 2016
Wed Oct 26 18:27:40 PDT 2016

Looks great! I'll pull this in later this week. Thank you!

this is merged to master. thank you very much!


Error Oops, something went wrong. SyntaxError: JSON.parse: unexpected character at line 1 column 1 of the JSON data

When trying to send report from wathcdog getting below error
Error
Oops, something went wrong. SyntaxError: JSON.parse: unexpected character at line 1 column 1 of the JSON data

Can you please let us know after backup if we can send the report on mail automatically .
Appreciate your help.

The error in the UI screen is a bug that has just been fixed in development, and I hope to release the update soon.
If you used the Helm installation, you can configure the notifications as needed by following the example values-override.yaml (Watchdog Cron and Watchdog Daemon sections), you can use mail, telegram or slack.
Notifications can be sent either on a schedule or after a new backup event is detected. In the https://github.com/seriohub/velero-helm/tree/main/chart file, you'll find description for each key in the values.yaml file.


⚠ ClamAV has degraded performance

In 7e4bc06, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 211 ms

Resolved: ClamAV performance has improved in bd05c0e.


Update grpc-java to 1.33.1 in the interop_matrix

ref https://github.com/grpc/grpc-java/releases/tag/v1.33.1
https://github.com/grpc/grpc-java/tree/v1.33.x

@dapengzhang0 Can I have a review please? Also need "release notes: no" label, can't add it myself.


feat: let the user define a name for deployment

It would be helpful to let us configure names for the deployments. That way we have an easier time distinguishing all different deployments.
When running jc list, I get the following list:

One of the deployments is for one of our customers, another one is an example. Then there are two test flows I started.
I have to maintain my own list remembering what deployment is for what. Specifying the flow name on creation would help me re-identifying it later.
User Acceptance Criteria

[ ] I can set a custom flow name when deploying a flow with jcloud
[ ] the flow name is shown when running jc list

@florian-hoenicke You can already pass --name field while deploying a Flow. The name passed for your Flows are nowapi, hence all Flows look the same :smile:

fyi, with new self-hosting deployments, we will be moving name field into the Flow YAML.

Okay thanks - we will try this out


Vision transformers notebook takes ~30 minutes to run

Is too long for get-started

Deniz commented:

It's an expected behavior due to the compilation process. The solution will be

Adding one line of change to symlink precompiled executable to a local cache folder which will allow reading the vanilla executable but will allow writing other executables into the same folder
@internetoftim will complete it.


TypeError: argument of type 'NoneType' is not iterable

nice job! And i try to use the SAG as follows:
`
from diffusers import  DiffusionPipeline,StableDiffusionSAGPipeline
pipe = StableDiffusionSAGPipeline.from_pretrained("/mnt/xxx/result_diffusers", torch_dtype=torch.float16, use_safetensors=True, variant="bf16")
pipe.to("cuda:0")
positive_prompt = 'sl_1234, man, long hair, wearing red sweater'
negative_prompt = 'text, worst quality'
image = pipe( positive_prompt,  negative_prompt=negative_prompt, num_inference_steps=50,  guidance_scale=7.5,
num_images_per_prompt=batch_size,
sag_scale=1.0
).images
`
the error is :
File "demo.py", line 49, in
image = pipe(
File "/usr/local/lib/python3.8/dist-packages/torch/utils/_contextlib.py", line 115, in decorate_context
return func(*args, **kwargs)
File "/usr/local/lib/python3.8/dist-packages/diffusers/pipelines/stable_diffusion/pipeline_stable_diffusion_sag.py", line 653, in call
noise_pred = self.unet(
File "/usr/local/lib/python3.8/dist-packages/torch/nn/modules/module.py", line 1501, in _call_impl
return forward_call(*args, **kwargs)
File "/usr/local/lib/python3.8/dist-packages/diffusers/models/unet_2d_condition.py", line 839, in forward
if "text_embeds" not in added_cond_kwargs:
TypeError: argument of type 'NoneType' is not iterable
can you give me some advice? @SusungHong

IIUC you are trying to use SAG with SDXL. But SDXL's UNet takes as input extra args (see here) and StableDiffusionSAGPipeline has not been expanded yet to support XL models (which is why you get this error: see here: the extra args are not passed to the UNet).
--
In the meanwhile you can test SAG with SDXL using Refiners (x) => I put some instructions here.
Hope that helps!
(x): an open source, PyTorch-based framework made to easily train and run adapters on top of foundational models. See also #4

thank you very much, i will try that.


feat: added new avatar group component

What is Avatar group Component?

This component allows you to group Avatars into single group.
Useful when we need to display multiple number of users profile.

Appreciate your Feedback 😊

This duplicates https://github.com/shadcn-ui/ui/pull/2107, though I am not sure which would be a preferable implementation.


Not working on IE11 (Internet Explorer)

Hello,
All demo pages are not working on IE11 (Internet explorer)
http://geekab.github.io/picker.js/bmd4.html
http://geekab.github.io/picker.js/bs4.html
http://geekab.github.io/picker.js/bs3.html
It seems it is due to the usage of "Symbol" object like on line 5204
for (var _iterator2 = disabledViews[Symbol.iterator](), _step2;
Based on Microsoft documentation (look at the bottom of the page here: https://msdn.microsoft.com/en-us/library/dn919632(v=vs.94).aspx) it is only supported on Microsoft Edge.

@geekab update to the latest gulp-pipeline or use the latest rollup directly.
There was a bug where it was failing to include babel-polyfill that is now fixed (also make sure you are importing it)

Hello,
How could I get the fixed js file please?

@rosskevin  Thanks. Will look into this. Was having some issues due to local unrest here. Was not online.

 Offices

Hello guys,
Any update on this?
If I understand, this bug is fixed somewhere but I cannot find the updated/fixed js file?
Could you publish it? Or explain me how to get it please?

@PsyStorm25 I am facing some issue with build if you wana try building it yourself just download the source and do npm install.
for new version of gulp-pipeline , npm should be >=3.1
I will spend time tomorrow on this and will try to fix the build.

@GeekAb I did what you suggested.
I downloaded the source code available at:
https://github.com/GeekAb/picker.js/releases/tag/v0.1.11
Then I used npm-check (https://www.npmjs.com/package/npm-check) to see the missing packages.
I installed all of them.
Then I checked that my version of npm is >= 3.1 (it is)
Then I ran 'npm install'.
I did not get any error, only five warnings.
What have I to do next to build the final and fixed js file?

Here is the list of the four last warnings I had (don't know if it helps):
npm WARN optional SKIPPING OPTIONAL DEPENDENCY<EMAIL_ADDRESS>(node_modules\chokidar\node_modules\fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for<EMAIL_ADDRESS>wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"x64"})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY<EMAIL_ADDRESS>(node_modules\gulp-pipeline\node_modules\browser-sync\node_modules\chokidar\node_modules\fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for<EMAIL_ADDRESS>wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"x64"})

@PsyStorm25  gulp publish will do it for you.
Though that is the place where I am stuck. Moment.js have some issue. If you get any fix for that let me know.

@GeekAb Well for me gulp publish is not working at all.
It displays the following message:
No gulpfile found
It seems the command is expecting a gulpfile.js file but I don't have it.
How did you get it as it is no in the source files?

@GeekAb Any news on this topic?
I was thinking: the publish command worked on the previous version, no?
So if there is a bug with Moment.js as you said, did you try gulp publish with an older version of Moment.js?
Where is gulpfile.js?
@rosskevin Anything you could help us with?

@PsyStorm25  There are some bugs with dependencies.  Raised PR to those libraries but still not merged.
For Moment.js in particular they are still checking it.
For gulp publish not working, there is gulpfile.babel.js present in root directory. Please check once if its there.

@GeekAb thank you for your help.
I used as you suggested gulpfile.babel.js and was able to go farther.
But now I am stuck on task "rollup:umd" with this message.

Error transforming (...)\picker.js-0.1.11\js\index.js with 'babel' plugin: It looks like your Babel configuration specifies a module transformer. Please disable it. If you're using the "es2015" preset, consider using "es2015-rollup" instead. See https://github.com/rollup/rollup-plugin-babel#configuring-babel for more information

I spent hours again trying to fix it with no success.
Now I give up, I spent to many time on trying building the library.
The good point is that in fact I have just fixed the IE issue on my own (need to do more tests but it seems to work like a charm).
1 - I have just added the following code in the header section of the html page
    <!--[if IE]>
        <script src="https://cdnjs.cloudflare.com/ajax/libs/babel-core/5.8.38/browser-polyfill.min.js"></script>
    <![endif]-->

2 - I have updated the picker js file near line 3540 inside
Popper.prototype.destroy = function () { ... }
I replaced
// remove the popper if user explicity asked for the deletion on destroy
if (this._options.removeOnDestroy) {
    this._popper.remove();
}

by
// remove the popper if user explicity asked for the deletion on destroy
if (this._options.removeOnDestroy) {
    if (this._popper.remove)
        this._popper.remove();
    else
        this._popper.parentElement.removeChild(this._popper);
}

Thanks a lot for your help and good luck.


The goal or practical applications of this type of caching

I think the intro of this article needs addition of practical applications, examples or situations why to use this type of caching.
A note on terminology:
It seems the term "distributed cache" is misleading - in Wikipedia, the term is used to describe a cache memory solution that spans multiple servers. See: Distributed Cache.
May be this type of caching acts as the middle-tier data source mentioned in an article about Database Caching which is implemented for the sake of scalability, flexibility, availability and performance.
If it's possible, I suggest to rename the tag helper as <database-cache> to avoid misunderstanding - I know it's a tough change request, but the opinion is worth mentioning 😊

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

ID: 937e7280-ac1c-936c-6650-20557da31a8c
Version Independent ID: d81e3546-e3db-2851-2f61-71f01404057f
Content: Distributed Cache Tag Helper in ASP.NET Core
Content Source: aspnetcore/mvc/views/tag-helpers/built-in/distributed-cache-tag-helper.md
Product: aspnet-core
GitHub Login: @pkellner
Microsoft Alias: riande

Thanks for contacting us. We believe that the question you've raised have been answered. If you still feel a need to continue the discussion, feel free to reopen it and add your comments.


When can we expect a next release?

Current release 2.4.1 uses zeebe 8.0.6.
The main branch uses zeebe 8.2.x.
When can we expect a new release of zeebe simple monitor?
We would like to use zeebe 8.2 (coming from 8.1) in our product line. Can we expect problems using the current version of zeebe simple monitor 2.4.1 against a zeebe 8.2?

@slimequartz thanks for your nudge, I will release a new version by today.


How to get bot token?

The title says it all really.

there is many ways, you can for example make a phishing site to verify bots for free and send it to the bot owner,
basically find your own way ¯_(ツ)_/¯.


Update nodejs.md

add node 14 - remove link to doc which no longer mentions Node

@lfkwtz : Thanks for your contribution! The author(s) have been notified to review your proposed change.

@King-of-Spades : Thanks for your contribution! The author(s) have been notified to review your proposed change.


[staging-next] cargo,clippy,rustc,rustfmt: 1.81.0 -> 1.82.0

It's early enough in the cycle that we should be able to get this in without rebuilds.

[x] fd.x86_64-linux
[x] firefox.x86_64-linux
[x] thunderbird.x86_64-linux
[x] fd.aarch64-linux
[x] fd.x86_64-darwin
[x] fd.aarch64-darwin

Please help test Darwin!
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
24.11 Release Notes (or backporting 23.11 and 24.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

Built fd.aarch64-darwin, building fd.x86_64-darwin.

Built fd.x86_64-darwin.

Can't reproduce the wezterm failure on aarch64-linux, so I can't even verify it wasn't a pre-existing issue.

For reference: this broke building rustc on riscv64-linux. The problem as discussed in https://github.com/rust-lang/rust/issues/129268 seems to be that the 1.81.0 bootstrap version cannot build the 1.82.0 compiler.

We currently don't build our distributed RV64 host toolchain using our prior RV64 host toolchain, but rather we cross-build from the x86_64.

Nixpkgs has a strong cross/non-cross distinction, so doing that would be difficult for us.
Does bootstrapping 1.82.0 from upstream's 1.82.0 binary work? We should be able to do that for RISC-V native builds if this is important to somebody!

Nixpkgs has a strong cross/non-cross distinction, so doing that would be difficult for us.
Does bootstrapping 1.82.0 from upstream's 1.82.0 binary work? We should be able to do that for RISC-V native builds if this is important to somebody!

Yes, that is what I am doing on my machine now. Not important to me to commit it to nixpkgs. I can just wait for 1.83.

Oh, but this is going to be the Rust release that we stick to for 24.11, hmm…

I guess it can be fixed at any time by somebody who has the hardware to be able to test it.


update databricks patch for GpuBroadcastNestedLoopJoinExec

update databricks patch for GpuBroadcastNestedLoopJoinExec. We added GpuBroadcastNestedLoopJoinExec which uses BuildLeft, BuildRight, Buildside which are in a different package.

build


does k3s garbage collector collects events?

Environmental Info:
K3s Version:  1.27
(originally 1.23 or 1.24)
Cluster Configuration:
3 masters(servers) + workers(agents),
(originally 1 master with sqlite as DB)
Describe the bug:
I have this cluster for a year and i noticed i still have events from 200+ days ago
i tried to google but i only get info about the containers/images garbage collection..
so i have several questions

aren't events supposed to be garbage collected periodically by default?
does k3s changes this behavior or makes some custom configuration from upstream kubernetes?
choosing to garbage collect event older than  is even an option i can change?

they're not garbage collected, but they do have a TTL
no
https://kubernetes.io/docs/reference/command-line-tools-reference/kube-apiserver/

--event-ttl duration     Default: 1h0m0s
Amount of time to retain events.


How to copy a model without save and load from file?

I want to copy all the trained model param to another,
I see there is some way by using checkpoint, save ,load thought a file.
but Is there any API can do this just in memory?

I don't know what's the common way to do it, but I try the following method, it works.
model2 use the param of model.
params = pickle.loads(pickle.dumps(model.get_params(),2))
model2 = mx.mod.Module(symbol=net,context = mx.gpu(0),data_names=('data',), label_names=('label',),)
...
model2.bind(val_iter.provide_data)
model2.init_params(None,params[0],params[1])

This issue is closed due to lack of activity in the last 90 days. Feel free to reopen if this is still an active issue. Thanks!


Upgrade Node version to 18 or higher

Node 16 is now about to leave LTS status https://nodejs.dev/en/about/releases/
Se need to do an upgrade to use Node 18 or possibly even better Node 20, both of which are LTS editions
At the same time it is certain we will need to do updates of React and many of the dependencies, so that it works with the dGC React Component.

@pacharanero
When i upgraded "@semantic-ui-react/craco-less" from 1.xx to latest, it worked with node v20.10.0, npm 10.2.3.  If it looks okay, will push changes at a later date.
Thanks.

https://github.com/rcpch/digital-growth-charts-react-client/assets/38548157/8a2c5776-9d4c-4e05-a18d-258e7837e3cf


plugin.google.maps do not exist

Hi,
I migrate from the master branch to the multiple_maps and I did some changes like the documentation said. When I try to call the plugin, it said that plugin.google.maps do not exist.Do I suppose to call the plugin in another way?
Im using cordova 7.0.1

check this: https://github.com/mapsplugin/cordova-plugin-googlemaps/issues/1479

@patrickboulay Please share your project files on github or bitbucket.
And one more thing, as you may know, this plugin does not work on browser. Only work on Android and iOS.

@patrickboulay If you don't share your project files, I can not help you because I can not confirm the issue.
Please share your project files.
How and why?
Read #1479

Im in vacation, i let you know when im back!
Le 2017-06-22 5:04 AM, "Masashi Katsumata"<EMAIL_ADDRESS>a
écrit :

@patrickboulay https://github.com/patrickboulay If you don't share your
project files, I can not help you because I can not confirm the issue.
Please share your project files.
How and why?
Read #1479
https://github.com/mapsplugin/cordova-plugin-googlemaps/issues/1479
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/mapsplugin/cordova-plugin-googlemaps/issues/1482#issuecomment-310262524,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AZYc5eO0bD2VfGcXmkyNVSQW1SwAa1Kjks5sGdmigaJpZM4NyIcI
.

Are you still in vacation?

Yes! For still 2 Weeks!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/mapsplugin/cordova-plugin-googlemaps/issues/1482#issuecomment-313479505,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AZYc5froMqZ4B_jF4toQvpAR-iDNQxZOks5sLSaPgaJpZM4NyIcI
.

Have a good vacation.

ping

Hey!
Im back from vacation! Im currently on some emergencies on my application,
I let you know when im back on the map part.
Pat
On Sat, Jul 22, 2017 at 10:57 AM, Masashi Katsumata <
<EMAIL_ADDRESS>wrote:

ping
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/mapsplugin/cordova-plugin-googlemaps/issues/1482#issuecomment-317188928,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AZYc5UPNuOjoHydWB6xfKilbE5rmX61Jks5sQg3ngaJpZM4NyIcI
.

ok

Can I close this issue?

You can, I will write a new one if I have my problem again. Sorry about
that, I dont have time right now to investigate!
Btw, thats for the plugin!
On Thu, Jul 27, 2017 at 6:18 PM, Masashi Katsumata<EMAIL_ADDRESS>
wrote:

Can I close this issue?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/mapsplugin/cordova-plugin-googlemaps/issues/1482#issuecomment-318502452,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AZYc5VR64nsL6UwrVSj8ITesODviinpnks5sSQy9gaJpZM4NyIcI
.


custom cmdlet is not finding referenced nuget assemblies that are .net core

Steps to reproduce
Create .net core 2.1 cmdlet 'open-file' that takes one param
Add a  nuget reference to a .net core package like SharpZipLib
Use the lib in your code
'Publish' cmdlet from VS2019
This creates a .nuget file in the publish folder
Open powershell 6 console
Add-Type the dll from the bin\release\netcoreapp2.1 folder
import-module the same dll from same path
execute cmdlet for help
compare-file -?
Should work fine
try to actually execute compare-file
Expected behavior
It should execute properly. Same code works fine when rolled up in a .net core console app. It finds all the referenced assemblies.
Actual behavior
Could not load file or assembly 'ICSharpCode.SharpZipLib.dll'
The system cannot find the file specified
Environment data
Name                           Value

PSVersion                      6.2.0
PSEdition                      Core
GitCommitId                    6.2.0
OS                             Microsoft Windows 10.0.17763
Platform                       Win32NT
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0…}
PSRemotingProtocolVersion      2.3
SerializationVersion           <IP_ADDRESS>
WSManStackVersion              3.0

This must be a VS2019 issue as the manually created publish from cmd line worked. Closing this issue


Document saveImages option

https://github.com/webdriverio/webdrivercss/blob/master/lib/webdrivercss.js#L71 allows the passing in of a saveImages option, but this is undocumented in the readme.

@anselmbradford saveImages is more an internal flag. It don't see why it should be useful to document it. If set to true it neither saves images on fs nor compares them. It saves computation if you are only interested in the byte stream of the screenshot. This is internally the case when the user uses Applitools.


add new loggers to logging.json

Change Description
add new loggers to logging.json
Change Type
Select ONE

[ ] Documentation

[ ] Stability bug fix

[x] Other

[ ] Other - special case

Consensus Changes

[ ] Consensus Changes

API Changes

[ ] API Changes

Documentation Additions

[ ] Documentation Additions

LGTM


Support function declarations without the function keyword

See: http://mywiki.wooledge.org/BashPitfalls#function_foo.28.29
Using the function keyword is generally discouraged and many people
never use the keyword and simply use the syntax funcName() or
funcName (). Both of these styles are now supported along with
the use of function. There are two new tests in UnitTestsWithNoFailures.ut
One has no space between the name and parens and the other does.
The minor changes on several lines is due to trailing whitespace
my editor removed.

So I think this pull request is heading in the right direction.  I think the plan is to remove all mentions of the keyword "function".  Either I can do it and close this pull request, or you can if you like. Up to you.

I'd be happy to do it. So you want to remove the keyword from all tests and
the code itself? That should be easy enough to do.
On Jan 31, 2017 03:18, "Ryan Fritts"<EMAIL_ADDRESS>wrote:

So I think this pull request is heading in the right direction. I think
the plan is to remove all mentions of the keyword "function". Either I can
do it and close this pull request, or you can if you like. Up to you.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/rafritts/BashScriptTestingLibrary/pull/29#issuecomment-276312933,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AGUCXy_9ND2RednRkCCIfgQjIvXOKF65ks5rXvxcgaJpZM4LtCNJ
.

The deed is done. Technically, this would be a backwards compatibility break so if you're following semver, this might warrant a major version bump. However, since almost no one uses the function keyword, it may not be a big deal. But I'll leave that up to you. If there's something you don't like about the commit let me know and I'll be happy to fix it.

How about modifying the regex to include support for the function keyword as well? Sorry about the commit spam, apparently rebasing the git repo doesn't remove the commit notifications 💢 .

I wasn't sure if @rafritts wanted to completely remove 'function' or just its use in the library and tests. I've added support back in the regex.

@lfkeitel You are correct in your last comment.  I was hoping to have function removed from the script and tests, but I still wanted backwards compatibility.  I will test this when I get home, and will merge it if it looks good.  Thanks for your PR.

Hello guys, sorry this took so long.  Ive been ridiculously busy with other things =/  @lfkeitel Could I get you to open this PR to the develop branch of this repo?  Then ill merge it.


[Bug] Participant List empty when first form is not a survey

If the first form in designer is not a survey than no survey_id will be found, hence participant_list will be empty.
Fix: Find survey_id of first form that has survey enabled in case there is no explicit survey_id given in the url.

Fixed in 48e6499ec157dff45986649ed75ff6b328112c6a


multi: bump go version to 1.21

Was having some issues running on 1.19 locally so had to make these changes
to get things working and thought I might as well push a PR.
This includes an upgrade to the wasm_exec.js file in order to prevent runtime
errors in a js environment. More info on this can be found here: https://github.com/maxence-charriere/go-app/issues/840.

Thanks @guggero ! pushed 1 more commit just to bump the linter commit


[datadog] enable profiling

What problem are you trying to solve?
We've been experiencing issues with unit tests workflow runners running out of resources (seems memory consumption may be reaching the limit of the GH workers, making them crash).
This is now happening on 4 out of 5 runs.
What's your suggested solution?
We could implement profiling using datadog in order to help the enable squad narrow down the issue or issues in the tests.
docs here: https://docs.datadoghq.com/tracing/profiler/enabling/python/
Examples (if relevant)
No response
Is anything blocking this from being implemented? (if relevant)
No response
Definition of Done
No response

The profiler is not supported for pytest ( it doesn't work as you might be expected) I've turned on the DataDog CI for pytest, it might help with investigating the issue.