Do not report SignalExceptions in at_exit handler

Goal
The previous behaviour resulted in applications reporting errors even though they were gracefully and without any problems shut down. Example: the puma webserver relies on SIGTERM to gracefully shut down its workers and Bugsnag reported errors when it was normally shut down.
With the at_exit handler introduced in #397, Bugsnag would catch SignalExceptions on exit and report them as error, even though they are none.
This PR changes the existing behaviour to add SignalException as a special case in which the exception should not be passed to Bugsnag.notify.
Changeset
Added

Bugsnag.at_exit_handler

Changed

Bugsnag.register_at_exit

Tests
Due to the Ruby exiting when a SignalException is raised I had to refactor the code to make the actual handling of the exit-exceptions testable without the test suite quitting.
Linked issues
For more information on puma's behaviour, see here: https://github.com/puma/puma/issues/1438
Honeybadger also ignores SignalExceptions: https://github.com/honeybadger-io/honeybadger-ruby/issues/267
Review

For the submitter, initial self-review:

[x] Commented on code changes inline explain the reasoning behind the approach
[x] Reviewed the test cases added for completeness and possible points for discussion
[ ] A changelog entry was added for the goal of this pull request
[x] Check the scope of the changeset - is everything in the diff required for the pull request?
This pull request is ready for:

[x] Initial review of the intended approach, not yet feature complete
[x] Structural review of the classes, functions, and properties modified
[x] Final review

For the pull request reviewer(s), this changeset has been reviewed for:

[ ] Consistency across platforms for structures or concepts added or modified
[ ] Consistency between the changeset and the goal stated above
[ ] Internal consistency with the rest of the library - is there any overlap between existing interfaces and any which have been added?
[ ] Usage friction - is the proposed change in usage cumbersome or complicated?
[ ] Performance and complexity - are there any cases of unexpected O(n^3) when iterating, recursing, flat mapping, etc?
[ ] Concurrency concerns - if components are accessed asynchronously, what issues will arise
[ ] Thoroughness of added tests and any missing edge cases
[ ] Idiomatic use of the language

Hi @mrnugget, thanks for the PR. At a glance your description of the problem sounds reasonable and the current behaviour undesirable. I'll schedule a proper look at this PR and see where we should take it from here. Cheers!

How would we feel about signalexceptions being added to the default ignoreclasses? I'd rather have this behaviour be configurable by users with a sensible default. Right now you can achieve this by adding SignalException to the ignore classes.
Having said that we already have something like this in other integrations like https://github.com/bugsnag/bugsnag-ruby/blob/35b3ef07ef21aab09ad188e0485f1eb6310b07a6/lib/bugsnag/integrations/sidekiq.rb#L25.
I think I'd favour removing all the special cases and ignoring signal exceptions. Thoughts?

How would we feel about signalexceptions being added to the default ignoreclasses?

That's probably the cleanest of all solutions! I'd prefer it, yes.
Also didn't know that there were default ignoreclasses 🙈. A quick search got me to this PR which seems to do the same for other two exceptions in the Sidekiq integration:
https://github.com/bugsnag/bugsnag-ruby/pull/404
So, yes, I strongly agree, let's add SignalException to this set 👍

I'm going to close this PR as you can add SignalException to the list of ignore_classes in your app's configuration to achieve the desired behaviour.
I'm also going to make an internal backlog ticket to add this to the default list of ignore_classes, and to remove the specific logic in the sidekiq integration (and any others where it exists).
Thanks all!


Fix prop sidebar in modal form to be full height of the window

When the props modal was shown, the columns wouldn't stretch to 100% height of the window. That caused dropdowns not showing properly if they were in the last row:

This fix makes both columns (props and preview) scrollable independently and sets their wrapper to fit the window.

yay Anna! 🎉 thx for the fix 🙌

Awesome! :tada:


gender specification in user settings

Asking for gender specification besides only the given and last name and email seems a little bit redundant, no? This is "A framework for the publication of scientific databases" after all...

Yes, this was for demonstration purposes only. Removed in https://github.com/aipescience/django-daiquiri-app/commit/ad4f121f4bec184ed637fd892c835b379d054597.


Proposal to refactor Links

Motivation
As of today there's 4 components to make links on Open Collective:

Link (from pages) -> a wrapper for next-routes without extra markup
Link (from components) -> A <a/> tag wrapped by a next-routes Link. Also has special logic to animate scroll to anchors
StyledLink -> A <a/> tag with styled-components properties
ExternalLinkNewTab -> A <a/> tag with properties to open in a new tab

This is confusing for two reasons:

As a new contributor, should I use Link from pages, component? Or StyledLink?
You need to check the imports to see what Link you're actually using

Proposal
We have 3 types of link:

Internal (frontend routing)
External
To an anchor

We want all our internal links to use next-routes (to benefit from frontend routing), all our external and anchors links to use a <a/> tag.
I propose the following components with explicit names. All existing Link should be deprecated and migrated.
We should also change the next Link export name to NextLink to ensure we stop using it.
Link
A wrapper around next-routes Link with styled components. This one can be created easily by taking all the logic from anchors out of components/Link and by adding styled-components on it.
<InternalLink
  to="route"
  params={{x: 42}}
  textAlign="center"
>
  An internal link, the "<a/>" markup is added automatically
</InternalLink>

ExternalLink
Will add the necessary target="_blank" and ref="noopener ..." if openInNewTab is true.
<ExternalLink
  to="https://docs.opencollective.com"
  openInNewTab={true}
/>

AnchorLink
Just take the logic for anchors out of components/Link.
<AnchorLink
  to="#team"
  animate={true}
/>

Independent steps

[x] Move ExternalLinkNewTab to ExternalLink, add the boolean option openInNewTab
[ ] Move all anchors logic out of Link to a new AnchorLink
[ ] Rename Link from pages to NextLink

Closing as the specs are out-of-date. Will revisit with something simpler.


Age summary should exclude measurement level ages

Ages at the measurement level are not indicative of the age of the specimens in the data set. They should be ignored in the summary. Attached is an example text file. Should be .365 to 4.59 Ma but the summary states 0-36.012 Ma
KArAr_upload_file_2022-08-26T15_51_07.409281.txt

Peter Davidson also comment on this problem

Contributions:
karar.earthref.org/KArAr/10
karar.earthref.org/KArAr/9
have something wrong with them as they don't have a version number and when Peter Davidson publishedkarar.earthref.org/KArAr/12 it should have been version 2 of karar.earthref.org/KArAr/9


RabbitMQ high CPU usage on idle VM

Is this a request for help?: Yes

Is this a BUG REPORT or FEATURE REQUEST? (choose one): FEATURE REQUEST
Version of Helm and Kubernetes:
Helm: 2.8.0
Kubectl server: 1.7.12-gke.1 (current) (It's GCP)
Which chart:
stable/rabbitmq
What happened:
High CPU usage on idle VM with only RabbitMQ running, generated by readiness/liveness probes. Basing on Stackdriver charts I see 100% CPU usage on n1-standard-2 VM. After forking chart, replacing probes with simple tcpSocket to 15672 port, it decreased to ~0%.

What you expected to happen:
To allow customizing health checks, use tcpSocket or httpGet instead of exec probes.
How to reproduce it (as minimally and precisely as possible):
Run it on GCP with n1-standard-2 VM type, and watch

Would like to add that I'm also seeing this on GCP K8s 1.8.7-gke.1aprox 60% usage at idle.
n1-standard-1 (3.7G) free tier.
erl_child_setup and beam.smp being the consumers a around 25% each.

cool! the solution of disabling readiness and liveness worked so far! but is there any option to change the ulimit in the docker image, the chart, or the deployment itself?

@robermorales the docker image including the fix (https://github.com/bitnami/bitnami-docker-rabbitmq/pull/69) is being prepared by bitnami; then the default value should be OK, but we should still expose it in the chart values.

thanks!

The fix has been released in docker images 3.7.4-r4 and 3.6.15-r4 (and their aliases: 3.7.4, 3.7, 3.6.15 and 3.6).
Since #4591 the values.yaml became non-prod, and the default image tag is the floating tag 3.7.4 instead of 3.7.4-r1. (values-production.yaml still refers to 3.7.4-r1).
Alas, we also have by default pullPolicy: IfNotPresent so in practice the floating tag is not a great idea...
I'm not sure if values-production.yaml is a good pattern; maybe it could just overrides some values instead of redefining everything. (only uses: redis and rabbitmq).
Maybe we should remove the floating tag and use read-only tags: 3.7.4-r4.
In any case, we should bump to -r4 to get the high CPU usage fix.

I still have the exact same issue in 3.7.6-r8.

@rips-hb I also have some high CPU usage, but it's periodic, not constant. I found out it's the probes (rabbitmqctl status) which use that much CPU periodically; it's a different issue (that should be created here), and I'm not sure what to do to fix it.

@thomas-riccardi for me it is constant unfortunately and I could resolve it by disabling liveness and readiness as suggested in this thread. Since it is only a test system that is no problem but I would rather have this checks on a production system. I will investigate a bit more and if I find something else I will create a new ticket.

still an issue

The fix https://github.com/bitnami/bitnami-docker-rabbitmq/pull/63 is incomplete and does not set the ulimit for the liveness / readiness probes.

@macropin you are right.
However, I did not find a difference in execution time for rabbitmqctl status (or rabbitmqctl node_health_check) with and without ulimit -n 1024 (or ulimit -n 65536), so trying to add the ulimit -n to healtchecks will probably not help.

@macropin see also rabbitmq-ha advancements: #7378 (and #7752).

Also I concur with @thomas-riccardi's findings — I did some testing too, and it turns out that even setting ridiculously low ulimit -n 128 does not help neither to reduce the probes' CPU time nor to reduce overall Pod's CPU usage.

could it fixed at helm install? I have same problem here.

@TomaszUrugOlszewski It should be fixed by #8140 (and subsequent fixes), modulo the issue about disk or memory alarms (see #8635).

rabbitmq 3.7.8 ，Erlang 21.1 same issue,high cpu useage. qps about 200/s

But, Is this was fixed?

I'm seeing the exact same behavior on 3.7.8 (Erlang 21.1) with very high CPU usage when idle and as a workaround disabling both the readiness and liveliness checks seems to fix the issue.

Hi,
Thanks for the feedback. If this issue is constant, then maybe it makes sense to change the readiness/liveness probes to simple tcp port checking. Thoughts on that?

@javsalgar I tried again with the latest version of the chart (rabbitmq-4.0.1) with Rabbitmq 3.7.9 (Erlang 21.1) and this problem does not seem to happen anymore.

Hi everyone,
Do you still suffer High CPU usage because of readiness/liveness probes in the latest versions of the cart??
I agree with @javsalgar, we can make simpler probes (such as tcp port checking) or decrease the frequency if you're running into issues because of that.

In my case, I greatly reduced the frequency of the probes.

What values did you use @desaintmartin ?

  livenessProbe:
    timeoutSeconds: 30
    periodSeconds: 30
  readinessProbe:
    timeoutSeconds: 30
    periodSeconds: 30

So the "fix" isn't a fix, rather a workaround. This should be reopened.

Hi @macropin
Currently liveness/readiness probes use curl instead of rabbitmqctl. Why do you consider necessary to update the ulimits on the probes?

Oh that's great. I missed that change. The High cpu usage of rabbitmqctl was due to it not inheriting the entrypoint ulimit which cased a cpu usage issue with the Erlang JVM.

Hi, I've found another reason why RabbitMQ can have noticeable CPU usage when in idle or under a light load. RabbitMQ is running on Erlang and it is using its scheduling capabilities. To schedule a process Erlang is using scheduler threads and its number by default depends on a number of logical cores. And this is a problem when running in docker/kubernetes because RabbitMQ will think it has more resources than it actually has. In our case, a RabbitMQ node is running on a server with 40 cores but we are limiting it only to have 1 core in Kubernetes. Erlang will run 40 scheduler threads that are constantly context switching which generates the cpu usage. When I set the number of scheduler threads to 1 the CPU usage dropped from 23 % to 3 %.
You can check how many scheduler threads you are using with rabbitmqctl status:
$ rabbitmqctl status
...
{erlang_version,
     "Erlang/OTP 20 [erts-<IP_ADDRESS>] [source] [64-bit] [smp:40:40] [ds:40:40:10] [async-threads:640] [hipe] [kernel-poll:true]\n"},
...

numbers after smp are the number of threads. For more info see Erlang scheduler details. You can set the value using environment variable:
RABBITMQ_SERVER_ADDITIONAL_ERL_ARGS="+S 1:1"

@Artimi how did you set"RABBITMQ_SERVER_ADDITIONAL_ERL_ARGS" with rabbitmq helm?

@infa-ddeore We actually are not using helm, just custom made kubernetes deployment. I just wrote it here because I had similar problems as are in this issue.

@thomas-riccardi thanks for the pointers, for now I will update stable/rabbitmq chart locally with this variable and deploy that

@Artimi setting "RABBITMQ_SERVER_ADDITIONAL_ERL_ARGS" to "+S 1:1" doesn't seem helping me, I will try disabling liveness and readyness checks, my rmq is 3.7.8 and erlang 21

Thanks for reporting it @Artimi
I just created a PR so the user has a couple of parameters to limit the number of scheduler threads.

This was still an issue on 3.8.3 with Kubernetes.  Adding the environment variable via rabbitmq-env.conf reduced our cpu usage by 300-400%.

same issues in helm chart rabbitmq-ha-1.47.1


Set java version in tandem

When i select java 17 i would like to have subprojects be java 17 as well, or get a warning.
When i created a java17 project with only LWJGL 3  lwjgl was java 8. that combination did not work.

Right now the behavior Liftoff uses is to allow desktop and server Java versions to be different from other versions (since Android, iOS, and GWT usually are limited to language level 8, or possibly 11 in specific cases). This has been confusing in the past and I'd like to change the default, as long as there's some way to still set the language level for server and desktop modules. Server modules in particular don't often share much code with the rest of the project, and can easily use a more recent Java version.
I believe the simplest fix for your use case is to set the desktop Java version (on the advanced tab) when you set the main Java version (on the same tab), since in this case they should be the same. I probably should make the desktop Java version use the higher of its setting and the main Java version, which would set both to 17 if I implement that and reproduce this condition.


Hessian Penalty decreasing rapidly

I plug in the hessian penantly in an autoencoder
h = encoder(E)
E_ = decoder(h)
L = Lambda(lambda x:tf.reduce_mean(tf.square(x[0] - x[1]), axis=(1, 2, 3)), name='mse')([E, E_])
f = lambda x:tf.reduce_mean(tf.abs(x), axis=(1,2,3))
hessian = Lambda(lambda x:hessian_penalty(decoder, x, reduction=f, return_separately=True)[0], name='hessian')(h)

__________________________________________________________________________________________________
encoder (Model)                 (None,<PHONE_NUMBER>     net[7][2]
__________________________________________________________________________________________________
decoder (Model)                 (None, 218, 182, 2)  3462272     encoder[1][0]
__________________________________________________________________________________________________
mse (Lambda)                    (None,)              0           net[7][2]
                                                                 decoder[1][0]
__________________________________________________________________________________________________
hessian (Lambda)                (None,)              0           encoder[1][0]

And the hessian penantly is decreasing very very rapidly: in the first epoch has a value of about 4, in the second epoch has a value of 1e-08
is this normal?

Thanks for the question. I have observed that it sometimes decreases quickly when training, but not to 1e-8. Is your MSE decreasing slowly? It may be that the hessian penalty is swamping MSE, and so you need to apply a loss weighting to balance the terms.

This is what i get in terms of loss

The blue is the MSE, the orange is the Hessian Penalty x 10^6
it does make sense, i suppose, that at first it's very low, at at the beginning of the training the features are random, and therefore independent from each other? but it still stays rather low.

Also I would recommend against using tf.abs in the reduction function (sorry for any confusion about this, it was only intended to be used as a test case). This may not be related to the low loss problem but it might cause other issues. You may also find it beneficial to use the reduction we used in the paper. You can replace lines 4 and 5 in your code snippet with the following:
f = lambda x: tf.reduce_max(x, axis=(1,2,3))
hessian = Lambda(lambda x:hessian_penalty(decoder, x, reduction=f), name='hessian')(h)

ok, by using reduce_max the result gets better indeed. But it's still around 0.01 magnitude.
I noticed that if i ran the penalty on a trained autoencoder, the penalty starts at a higher value (~100) and decreases slowly, but if i start random, it will drop in less 1 epoch, and starts increasing right after

Sorry for the delay in responding. I think the behavior you're describing is more typical of what I've seen applying it to ProGAN. 0.01 magnitude can be reasonable depending on the depth of your decoder network. We found in our paper that resuming training of a pre-trained model with the HP gives good results and sometimes works better than training from scratch with the HP (possibly because an over-aggressive HP loss weighting when training from scratch can cause your model to get stuck in a local optima early in training). Ultimately I think the main thing to keep an eye on in your case is the reconstruction loss. If the HP drops too low, it's possible that it is doing something degenerate like simply scaling-down the output of the decoder. Such a degenerate solution should yield a worse reconstruction loss. But if your reconstruction loss is low (similar to what you get when you train without the HP) I think that should be a good sign that it is not doing something degenerate.


@display full address in listView

Hi,
I can't get full address in listView.
How can I get it via this package?
Thank you

@AkiraY523
Full address should be returned by default. Can you paste in a screenshot describing what you see?
You can customize list view item by providing custom renderDescription or renderRow props.

Hi myaskevich,
Thank you for your interesting for me.
As you let me know, the reason is that I used it as following code.

renderDescription={(row) => {row.terms[0].value; }}
So I rewrite like this, I solved this issue

renderDescription={(row) => row.description}
Thanks myaskevich.


Crashed app after install module on Android

This is detail of my add:
"react": "16.9.0",
"react-native": "0.61.5",
after install newest version "0.1.10" and run "npx react-native run-android" my app is crashed on start.

Sorry,
I solved this issue by cd android && ./gradlew clean


Speed optimization

The solver is now "much" faster. How much depends on the hardware. There are two new features:

MKL sparse matrix-matrix and matrix-vector calls are made for the jacobian and derivative operator. This is implemented in a new file mkl_interface.py of the solvers module:

This is hard to test on my Threadripper because matrix-matrix is extra-slow thanks to Intel. There is not even multithreading. Sparse matrix-vector for the usual jacobian calls seems much faster.
For the sparse LU one can use the PARDISO solver from MKL, it's supposed to be faster by a few factors.

CUDA GPU support for everything except the sparse LU solver. There is no implementation for sparse LU in cupy and it seems a very active topic of research. So for now that's too tedious.

That's actually a very easy implementation because almost everything can be kept the same.
Actually evaluating the entire eqn_derivative is negligible on computing time including the batch matrix multiplication. The bottleneck here is the trapz in the continuous loss_vector. Funny...
One has to be cautious with the "linear_algebra_backend" setting in the config, since bugs can occur if it is changed after initialization, so better change it in the config and then reload.
This doesn't seem to require a lot of memory ~ 500MB + overhead. But it should also run on smaller GPUs.

If you are reviewing this, please make a test on WGS37 for the MKL performance, because this is by far the fastest machine with AVX512.
I also removed some obsolete stuff from the solvers source. In particular for the BDF solver the dense jacobians are not needed anymore and these were really memory hungy. The solvers are still not super clean, but in urgent need of overhaul.
From what I see, the wall will be hit at around 6-10 seconds. Then many things will require some micro-optimizations. The examples should be updated as well to remove the numpy/scipy comments that are not required anymore. We should also increase the stepsize to 5e-3 or 1e-2. The result looked totally fine to me.

Regarding the speed on the Xeon Gold, yeah, that's what I also estimated. The advantage of MKL is quite apparent when multithreading. In case of 16 cores or so the derivative computation goes down to ~few s. So I'm happy that it works as intended. I may have a look into the iLU solvers, cuSPARSE has an ILU preconditioner that is maybe easily adaptable for GPU and mkl has dcsrilu0. The interfaces look like this may require some time.


create a photon-os version of Aegis components.

https://hub.docker.com/_/photon
This is becoming a priority and it’s not that hard to do.
Just change the base image, check if it passes tests, and if it does, then you’ll have aegis-photon dockerfiles too.

Done.


Locations: No module for.... with CollectionReference.get() in Flutter Web

I'm using cloud firestore in a Flutter web project. Whenever I call get() on an entire collection (rather than on a single document in the collection), I get the following error:
Locations: No module for https://www.gstatic.com/firebasejs/9.9.0/firebase-firestore.js
This happens on a collection with about 425 documents - if I limit the results, or call get on a smaller collection it works fine.
This is a valid operation according to the official docs: https://firebase.google.com/docs/firestore/query-data/get-data#get_all_documents_in_a_collection with no indication that it's limited by number of docs, etc. Also this same code was working fine (with the same number of docs) when I was doing the same thing on a Flutter macOS app, until recently I switched it to web.
I'm initializing Firebase in the flutter main() instead of in index.html, as now recommended by the most recent documentation. All firebase-related packages are their latest versions.
If this is indeed an issue related to too many documents then it would at least be nice if the documentation mentioned this limitation or the error message mentioned that, but that is not the case, and really it's not THAT much data, which leads me to believe there is some sort of bug or I'm doing something wrong.

@jason-downs Thanks for the report.
Can you provide flutter doctor -v, plugin version along with complete error log ?

@jason-downs
Revisiting this issue, I created 430+ documents in a sample collection. Retrieved it using below code sample which gave me correct results with all data without throwing the error you reported:
Future<void> addUser() async {

    CollectionReference add = FirebaseFirestore.instance.collection('basic-example');
    await add.get().then((event) {
      print(event.docs.length);
      for (final doc in event.docs) {
        print('${doc.id} => ${doc.data()}');

      }
    });
  }

  Flutter Web Bootstrap: Auto
The Flutter DevTools debugger and profiler on Chrome is available at: http://<IP_ADDRESS>:9100?uri=http://<IP_ADDRESS>:51418/9JK_4KByZqo=
434
05jWwqBZxC0BXXbGz2dC => {}
0CXKfUCbKI9EocGozLdA => {}
0GBytkK5IqbElwQDhpMw => {}
0NSz3nLR5Tady5UbHXcF => {}
0OzTmfyoh3TgBgObgH4A => {}
...

The browser devtools also doesn't show any error.
Can you provide more details as asked earlier ?

Sorry for the delay, for some reason my notifications weren't working - anyway here is flutter doctor -v output:
    • Flutter version 3.3.3 on channel stable at /Users/jason/flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 18a827f393 (6 days ago), 2022-09-28 10:03:14 -0700
    • Engine revision 5c984c26eb
    • Dart version 2.18.2
    • DevTools version 2.15.0

[✓] Android toolchain - develop for Android devices (Android SDK version 31.0.0)
    • Android SDK at /Users/jason/Library/Android/sdk
    • Platform android-31, build-tools 31.0.0
    • Java binary at: /Applications/Android Studio.app/Contents/jre/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 11.0.10+0-b96-7281165)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 14.0.1)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Build 14A400
    • CocoaPods version 1.11.3

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 2020.3)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 11.0.10+0-b96-7281165)

[✓] VS Code (version 1.71.2)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.48.0

[✓] Connected device (2 available)
    • macOS (desktop) • macos  • darwin-arm64   • macOS 12.6 21G115 darwin-arm
    • Chrome (web)    • chrome • web-javascript • Google Chrome 106.0.5249.91

[✓] HTTP Host Availability
    • All required HTTP hosts are available

• No issues found!```

Will post more diagnostic info in a moment.

@jason-downs
Thanks for coming back. Can you provide snapshot of the type of document data you have in that collection ? That way, I'll try to recreate the data and see if it is replicable at our end or not.

Moreover, please also try the same on latest master and see if you get same error log or not.

Please, i have the same error

Please dont close

@alvarogabrielgomez
I suggest you to go through https://github.com/flutter/flutter/issues/111136 and see if underlying comments / solutions mentioned in it, helps in your case too or not.


equiv between '2p21 microdeletion syndrome' and 3 other classes

'2p21 microdeletion syndrome' is inferred to be equivalent to three other classes:
'hypotonia-cystinuria syndrome type 1'
'homozygous 2p21 microdeletion syndrome'
'hypotonia-cystinuria syndrome'
I think this may be caused by the new axioms using monochrome - this isn't right though, is it? I'm surprised the qc checks didn't catch this.

how did you find these? robot does not..

Hm, that link doesn't work, here is a screenshot:

this is from a check that ensures all subClassOfs are proper subClassOfs https://douroucouli.wordpress.com/2018/09/04/debugging-ontologies-using-owl-reasoning-part-2-unintentional-entailed-equivalence/

related to: https://github.com/monarch-initiative/mondo/issues/3664

Per @cmungall's guidance, I ran the check for unsatisfiable classes and this was in Protege:

Note - in the 3rd explanation, Chris spotted this:

He noted there is a comment in the mondo-edit file:
id: MONDO:0011669
name: hypotonia-cystinuria syndrome
def: “Hypotonia-Cystinuria syndrome (HCS) is a rare syndrome including neonatal and infantile hypotonia and failure to thrive, cystinuria type 1 and nephrolithiasis, growth retardation due to growth hormone deficiency, and minor facial dysmorphism.” [Orphanet:163690]
comment: Editor note: check this. ORDO has type 1 as a superclass. Also check wether is_a: MONDO:0016538 is appropriate.
This comes from Orphanet:

It is incorrect for a generic class to be a child of a type 1 class. Action item: fix this in Mondo.

OK there may be more work to do than a simple merge. The axiomatization is revealing all kinds of other issues
e.g. I was suspicious of this:

here is the explanation:


Capture other unrecognized fields

#[derive(Serialize, Deserialize)]
struct S {
    a: u32,
    b: String,
    #[serde(other)]
    other: Map<String, Value>,
}

{"a":0,"b":"","c":true}

This would deserialize into other containing "c" => true.

I like this idea and might be able to submit a PR for it, but I have a few questions:

What are the type constraints on other? I'm guessing it works with any type that supports entries (so that it can report an error on duplicate fields and insert non-duplicate values).
Does the K type parameter of the map have to be String, or can it also be &'de str?
Does the V type parameter of the map have to be Value, or can it be any type? The latter seems more powerful, and I think it would work as long as local type inference can figure out what type to deserialize into.
Where is serde(other) valid?

Named-field structs
Named-field enum variants
Anywhere else?

Should using serde(other) with serde(deny_unknown_fields) on a struct produce a warning?
What other attributes are valid with serde(other)?

skip, skip_serializing, skip_serializing_if, and skip_deserializing
rename_all
borrow? (This is a new feature I'm not familiar with yet)

During serialization, should an error be generated if a key occurs on a named field and in other? Is name collision allowed if the named field's skip_serializing_if resolves to true?

It should support any type that implements visit_map (for deserialization) and uses serialize_map (for serialization). The handling of duplicate fields is baked into the Deserialize impl so doesn't need to be handled as part of this feature.

This would be handled by the Deserialize impl in visit_map.

This would be handled by the Deserialize impl in visit_map.

Just those two I think.

Yes, good idea.

For now I would just reject any other attributes. We can follow up later if anybody makes a strong case for a particular one.

Serde allows duplicate keys during serialization.

I personally would prefer naming this something more verbose like other_fields. The extra typing will make the attribute more understandable in the long run, and right now, I wouldn't know what other means without having it explained.

@dtolnay Right now, I only see errors in serde_derive_internals::Ctxt; is there a way to surface warnings?

No there is not. I guess make it an error.

This is starting to feel suspiciously similar to #119, in that it will allow reading and writing of keys from a nested object into a flat namespace in the serialized object. If we had #[serde(flatten)], I feel like we could allow that attribute on a generic map type and avoid needing this separate attribute at all.
Assuming this is still desirable, I'm starting to wonder if this should be a container-level attribute rather than a field-level attribute.
#[derive(Serialize, Deserialize)]
#[serde(unknown_fields_in="other")]
pub struct Sample {
    hello: String,
    other: HashMap<String, Value>
}

The user experience is similar: The duplicated identifier is unfortunate, but semantically I think it's a little clearer. From an implementation perspective, a container-level approach would be marginally simpler:

Two fields can't both claim to be the recipient of unknown fields
Validation errors about deny_unknown_fields and unknown_fields_in are easier to surface and explain
Code generation in serde_derive::de::deserialize_map doesn't have to scan the fields to determine how to handle unknown values.

I'm interested in developing this feature, but I haven't dug into the serde codebase at all up until this point. Is it a "beginner" issue? If so and with a little guidance I'd like to take this one up.

Yes, go for it!

@dtolnay can you give me some pointers - like if the field or container level attribute is preferred

I would recommend handwriting some Deserialize impls for this and testing them against some JSON inputs to make sure they capture unrecognized fields the way you expected. I would recommend doing this before diving into attributes and proc macro stuff.

@dtolnay okay thanks I'll see how far I get with this and if I make progress I'll share it here.

I added a somewhat working PR for this now: https://github.com/serde-rs/serde/pull/1178
I went with @TedDriggs's suggestion of a container attribute. However I do think that flattening and this feature cannot be merged for now. The reason for this is that in order to serialize unknown fields one needs to go through the map serialization system because of lifetime issues. As a result of that I decided to add a special mode to structs where structs are serialized into maps all the time and if that mode is on, deserialization into an Extends contained is possible.
For JSON it does not make a difference currently as the only thing you lose from this is the type name on the way to the serializer but JSON never used this anyways.

I think this issue is subset of https://github.com/serde-rs/serde/issues/119 ? Probably worth considering forwards compatibility with solution for that issue.

@Marwes i do not believe that with the current traits flattening can be combined with capturing leftover data for the reasons outlined above. At least the repr=map would have to stick around.

@mitsuhiko  I were thinking about that but it might be possible to have a other/flatten/collect_into  field in a struct if that is struct itself.
#[serde(unknown_fields_into="other")]
struct S {
   field: String,

   other: T,
}

struct T {
   field1: i32,
   field2: i32,
}

Failing that, the traits could be extended with alternative methods without the 'static lifetimes. These methods would only be called if the collect_into attribute is specified. To preserve backwards compatibility these added methods would need to return an error (or panic) in their default implementation and users would need to make sure that they use a format which has been updated to implemented these methods.

@Marwes i don't think forwarding unknown fields into anything other than a container that can eat anything makes sense. That would be a full overlap to a potential future flatten feature.

I would prefer to combine this with #119.
Sketch of a solution

@dtolnay would all flatten downgrade into map serialization or only if flatten is used on a non struct?

Flatten would always downgrade your struct into a map. In practice people only care about JSON anyway.

@dtolnay doesn't your solution require that data in inner can always be converted from the data in other?

Yes. I think that should be okay because in the case where there is more than one flatten field it will pretty much always be 0 or more structs/enums within which we ignore unrecognized fields by default, followed by 0 or 1 final catch-all map. The DeserializeMapAdapter will need to remove entries from the input vec that are deserialized at each step, and keep only the ones that are deserialized with deserialize_ignored_any. That way the final catch-all only sees fields that have not been claimed by any previous flattened field.

That means though if other is u32 it will no longer work or am I misunderstanding this?

Like this?
#[derive(Serialize, Deserialize)]
struct S {
    s: String,
    #[serde(flatten)]
    other: u32,
}

I would expect that to not work.

More like HashMap<String, u32>
On Wed, Mar 14, 2018 at 8:30 PM David Tolnay<EMAIL_ADDRESS>wrote:

Like this?
#[derive(Serialize, Deserialize)]struct S {
s: String,
#[serde(flatten)]
other: u32,
}
I would expect that to not work.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/serde-rs/serde/issues/941#issuecomment-373147016, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAAc5G83WfPNR42ga2XUz--048VD3KzEks5teW_ugaJpZM4Nhtqo
.

HashMap<String, u32> will work just like HashMap<String, Value> -- its existing Deserialize impl will take care of deserializing from the input deserializer (DeserializeMapAdapter) and coming up with error messages as necessary if things are the wrong type.

I see what I missed: that your sketch deserializes into the internal Content type. I somehow read the type inference as deserializing to serde json's Value. I will play around with this a bit. Not a huge fan that this means you potentially buffer up a huge amount of data because obviously this also means that efficiently ignoring items no longer works.

Implemented in #1179, released in Serde 1.0.34.
#[macro_use]
extern crate serde_derive;

extern crate serde;
extern crate serde_json;

use std::collections::BTreeMap as Map;
use serde_json::Value;

#[derive(Serialize, Deserialize)]
struct S {
    a: u32,
    b: String,
    #[serde(flatten)]
    other: Map<String, Value>,
}

fn main() {
    let s = S {
        a: 0,
        b: "".to_owned(),
        other: {
            let mut map = Map::new();
            map.insert("c".to_owned(), Value::Bool(true));
            map
        },
    };

    println!("{}", serde_json::to_string(&s).unwrap());
}

Slightly simpler, but same idea working well for me as a debug with no other use or other statements required :wink:
    #[serde(flatten)]
    other: serde_json::Value,

On a tangent; this confirmed for me the way that serde parsing consumes as it flattens. I'm kinda curious if there's a way to control that somewhat. For example I have another place with two structs I would like nested, who each both get a copy of the parent id, for example. If the parser consumes the id for the first flatten structure then it can't give it to the second.

Is there any other way to achieve this without using serde_json?

If you only concerned about serde_json, then use serde_value.

If you only concerned about serde_json, then use serde_value.

Yes, because I'm not currently using JSON for anything, it was more s debugging tool, so serde value will probably suffice if it allows me to inspect the captured values


Support ECS TaskRole in S3 storage driver

Instead of constructing the list of credential providers manually, if we use the default list we can take advantage of the AWS SDK checking the environment and returning either the EC2RoleProvider or the generic HTTP credentials provider, configured to use the ECS credentials endpoint.
Also, use the defaults.Config() function instead of aws.NewConfig(), as this results in an initialised HTTP client which prevents a fatal error when retrieving credentials from the ECS credentials endpoint.
Fixes #2960
Signed-off-by: Andrew Bulford<EMAIL_ADDRESS>

Hi @abulford and thanks for the fix which would be a big help to me. The build is failing on the execution script/validate/vendor, let me know if you're too busy to fix and I'll gladly get it done.

Ok @abulford looks like the failing vendor modules check is nothing to do with your change but related to some kind of inconsistency in go mod vendor behaviour, possibly https://github.com/golang/go/issues/28102. Would you be able to help @caervs ?

@btisdall sorry for missing your comments before - yes, I seem to remember when I submitted this I looked around and saw this test was failing elsewhere as well so assumed it was a known issue and hopefully wouldn't affect the review.  I would have investigated further but was rushing something out at the time.  Thanks for looking into this!

Is there anything I can do to move this forward? We have a project that's suffering from this exact problem and it's pretty much the last piece.

How is this still waiting? This is a critical patch... lets get this in!

LGTM
It looks like the build is failing on the vendor changes.
Are there any tests?

I've come back to a project that was relying on this and could do with it being merged so I can revert to the official release rather than my fork.  Is there anything I can do to move this along?  Or is this just awaiting the review from @manishtomar?

Would love to see this merged and released. We're using our own generic HTTP credentials provider throughout our environment and the registry is the only outlier we have.

Could you rebase this with latest master to fix the CI?

@manishtomar rebase done, CI is passing now! :)

So, what's remaining to merge this?

This needs to be tested in AWS before merging. I was hoping to do that but have been busy.

@manishtomar Tested this works in Fargate and locally with env variables.

Thanks @manishtomar!

Any chance of getting a new release that encompasses this?

It looks like #3245 undid the fix for this issue.  The comments in the follow-on PR say that it's fixing auth' for EKS while maintaining auth' for static credentials and EC2.  But it undoes the fix for ECS.  Can we have a fix that supports ECS (as well as EKS and other integrations)?


Loading and Testing

The model was imported perfectly. But the LabelEncoder did not work as:
#added in cell 496
from sklearn.preprocessing import LabelEncoder
lb = LabelEncoder()
livepredictions = (lb.inverse_transform((liveabc)))
livepredictions
throws the error:

This LabelEncoder instance is not fitted yet. Call 'fit' with appropriate arguments....

If you could help with this, it will be of great help.
PS: I started by importing all files in cell 1,2,3.
Then added
'opt = keras.optimizers.rmsprop(lr=0.00001, decay=1e-6)'
to cell 137, since opt was not defined
then executed all the blocks in Demo section.

Nevermind, I wrote a rough workaround for it.
Turns out, that it occurred because when model is imported, all the parameters are encoded with it except for the LabelEncoder.
It worked for you because you used notebook and all the variables were reused. but when it comes to standalone execution error occurs.
Hence, to reuse the variable "lb"(instance of LableEncoder) we pickle dump it in a file and load it again in the same variable name. Hence the inverse_transform method of the lb object can be reused without fit or fit_transform, but one time execution is mandatory to initialize the variable and fit it.
the code for dumping is as follows:
import pickle
file=open('lbsave.txt','wb')
pickle.dump(lb,file)
file.close()
loading the file is through:
import pickle
file=open('lbsave.txt','rb')
lb=pickle.load(file)

Hey @HarshitSoni1903, sorry I couldn't get back as I was consumed in other tasks. Glad that you found the solution to the problem.
Best wishes.

Is it possible to share the lbsave.txt file with me? my email id<EMAIL_ADDRESS>Because I didn't download the audio files and trained the model. But I having the same issue when I run the system. Or are there any other solutions available?

Hi, i have uploaded the file.
Kindly download the file and tweak your code to load the variable from the pickle.
Link:https://gofile.io/?c=bXRZ6n

Moreover, other way( the actual way) is to train the model on colab or some other repo. Because thanks to Mitesh, the code is colab compatible. Hence
train the model,
pickle the variable in some file,
use the same file to load the variable.
Because the pickle file I created uses only half of dataset, so if you want higher accuracy, it won't help.

Thank you very much. That's very helpful :1st_place_medal:

Hi, i have uploaded the file. Kindly download the file and tweak your code to load the variable from the pickle. Link:https://gofile.io/?c=bXRZ6n

Hi, could you share the saved pickle file one more time?
There's no file in the link you provided here.
I'd really appreciate it if you can send a file to<EMAIL_ADDRESS>Thanks!

Hi, i have uploaded the file. Kindly download the file and tweak your code to load the variable from the pickle. Link:https://gofile.io/?c=bXRZ6n

Hi, could you share the saved pickle file one more time? There's no file in the link you provided here. I'd really appreciate it if you can send a file to<EMAIL_ADDRESS>Thanks!

can you mail me if you have it
<EMAIL_ADDRESS>

can you mail me if you have it
<EMAIL_ADDRESS>
can you mail me if you have it
<EMAIL_ADDRESS>

Hi, i have uploaded the file. Kindly download the file and tweak your code to load the variable from the pickle. Link:https://gofile.io/?c=bXRZ6n

can you mail me if you have it
<EMAIL_ADDRESS>

Hey,
apologies for the delay. I have uploaded the file (use link)
to download. Instructions to use the code are already given above. However, I would like to caution you. I have used only half of the dataset to train so my accuracy was lower. If you wish to utilize the full capabilities of Mitesh's code, train it again, pickle the variable, and then reuse it.

Thanks a lot.
On Mon, 5 Feb 2024 at 17:48, HarshitSoni @.***> wrote:

Hey,
apologies for the delay. I have uploaded the file (use link
https://drive.google.com/file/d/1_qlnNvwtYjHdcgsMsjQRK5rS3FgdOq4I/view?usp=sharing
)
to download. Instructions to use the code are already given above.
However, I would like to caution you. I have used only half of the dataset
to train so my accuracy was lower. If you wish to utilize the full
capabilities of Mitesh's code, train it again, pickle the variable, and
then reuse it.
—
Reply to this email directly, view it on GitHub
https://github.com/MiteshPuthran/Speech-Emotion-Analyzer/issues/20#issuecomment-1926866533,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AQ4X6PVQPHAJ3HDWM2Q22CDYSDEYRAVCNFSM4G43YSTKU5DIOJSWCZC7NNSXTN2JONZXKZKDN5WW2ZLOOQ5TCOJSGY4DMNRVGMZQ
.
You are receiving this because you commented.Message ID:
@.***>

do u know any other code repo related to this task
On Mon, 5 Feb 2024 at 17:49, Anas Khan @.***> wrote:

Thanks a lot.
On Mon, 5 Feb 2024 at 17:48, HarshitSoni @.***> wrote:

Hey,
apologies for the delay. I have uploaded the file (use link
https://drive.google.com/file/d/1_qlnNvwtYjHdcgsMsjQRK5rS3FgdOq4I/view?usp=sharing
)
to download. Instructions to use the code are already given above.
However, I would like to caution you. I have used only half of the dataset
to train so my accuracy was lower. If you wish to utilize the full
capabilities of Mitesh's code, train it again, pickle the variable, and
then reuse it.
—
Reply to this email directly, view it on GitHub
https://github.com/MiteshPuthran/Speech-Emotion-Analyzer/issues/20#issuecomment-1926866533,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AQ4X6PVQPHAJ3HDWM2Q22CDYSDEYRAVCNFSM4G43YSTKU5DIOJSWCZC7NNSXTN2JONZXKZKDN5WW2ZLOOQ5TCOJSGY4DMNRVGMZQ
.
You are receiving this because you commented.Message ID:
@.***>

Thanks for the tip!
On Mon, 5 Feb 2024 at 17:52, HarshitSoni @.***> wrote:

Unfortunately no. I used this repo about 4 years ago, for my major
project. I'm afraid you'll have to research it on your own.
—
Reply to this email directly, view it on GitHub
https://github.com/MiteshPuthran/Speech-Emotion-Analyzer/issues/20#issuecomment-1926874735,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AQ4X6PTZRUJ75QFJ7JAEVZTYSDFKDAVCNFSM4G43YSTKU5DIOJSWCZC7NNSXTN2JONZXKZKDN5WW2ZLOOQ5TCOJSGY4DONBXGM2Q
.
You are receiving this because you commented.Message ID:
@.***>


Question: Can ALVR be used with a SteamVR installation but without a Steam installation?

Hi,
as per the title, I'm interested in running OpenXR apps with the SteamVR runtime but in an environment that doesn't allow full Steam installations. We can, however, have a portable installation of SteamVR (the contents of steamapps\common\SteamVR) something like the procedure described in this Valve article. I gave ALVR a try since it seemed like a possible solution, but I noticed that it needs to launch Steam in its entirety at some points. Is this how it is or have I missed something around some advanced parameterizing?
Thanks in advance!

It is how it is, however it shouldn't be too hard to just rewrite those sections of the code. Beware that you'll lack steam's process reaper in that case and that steamvr likes to not close all it's processes nicely if something even slightly goes wrong. Also if you only need openxr, integration with the open source monado runtime is in the works for alvr (see https://github.com/alvr-org/Monado-ALVR), but there's no ETA when it will be in a actually usable state.

It is possible. I know that my company uses offline-mode SteamVR packages, what have no Steam or cloud dependencies. These packages are distributed by HTC and are few and far apart. I think they don't have a SteamVR 2.0 package yet. Also unfortunately these packages are only for businesses, so you would have to contact HTC directly.

It is how it is, however it shouldn't be too hard to just rewrite those sections of the code. Beware that you'll lack steam's process reaper in that case and that steamvr likes to not close all it's processes nicely if something even slightly goes wrong (this is the main blocker to adding a feature to optionally just launch a steamvr executable directly) (actually not sure about that, there exists some process reaping code in alvr).

We would happily welcome such a feature, even as experimental with its potential stability risks. Also ALVR with Monado sounds like a very attractive combo choice so I'll definitely keep an eye on that for the future.

It is possible. I know that my company uses offline-mode SteamVR packages, what have no Steam or cloud dependencies. These packages are distributed by HTC and are few and far apart. I think they don't have a SteamVR 2.0 package yet. Also unfortunately these packages are only for businesses, so you would have to contact HTC directly.

Interesting info and we'll have to explore to that direction as well, sounds good.
@The-personified-devil and @zarik5 , great help and information, thank you so much both!

Actually, bringing back the subject, after some more searching I noticed that if I manually "Register the ALVR driver" in the installation tab of the Dashboard, and then run manually the standalone SteamVR (via vrstartup.exe), the dashboard seems to be detecting it and connecting to it successfully. Same steps as in https://github.com/alvr-org/ALVR/issues/2080 .
Then I was able to run the ALVR app in the headset (Quest3) and it seems to be working. One difference I noticed is that the SteamVR main menu looked different than what I've used to when running through Steam (looked older and was rendering different controllers than the Quest3's). Finally I was also able to run my app which, except from this error at the start

seemed to be running ok afterwards? I don't know if I'm neglecting something important from the registration process, but it looks encouraging nonetheless.


Fixed: Pass proper error when returning

Hit this panic today. We were not passing the correct error during one of the returns from netRetrieveState
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x0 pc=0x827caf]

goroutine 109 [running]:
github.com/aporeto-inc/enforcerd/vendor/github.com/aporeto-inc/trireme/enforcer.(*Datapath).processNetworkTCPPackets(0xc42033ef00, 0xc42688cf70, 0x0, 0x0)
	/tmp/build/80754af9/go/src/github.com/aporeto-inc/enforcerd/vendor/github.com/aporeto-inc/trireme/enforcer/datapath_tcp.go:71 +0x54f
github.com/aporeto-inc/enforcerd/vendor/github.com/aporeto-inc/trireme/enforcer.(*Datapath).processNetworkPacketsFromNFQ(0xc42033ef00, 0xc424ecb810)
	/tmp/build/80754af9/go/src/github.com/aporeto-inc/enforcerd/vendor/github.com/aporeto-inc/trireme/enforcer/nfq_linux.go:93 +0xdd
github.com/aporeto-inc/enforcerd/vendor/github.com/aporeto-inc/trireme/enforcer.networkCallback(0xc424ecb810, 0xab9120, 0xc42033ef00)
	/tmp/build/80754af9/go/src/github.com/aporeto-inc/enforcerd/vendor/github.com/aporeto-inc/trireme/enforcer/nfq_linux.go:19 +0x46
github.com/aporeto-inc/enforcerd/vendor/github.com/aporeto-inc/nfqueue-go.(*NfQueue).ProcessPackets(0xc422652b40)
	/tmp/build/80754af9/go/src/github.com/aporeto-inc/enforcerd/vendor/github.com/aporeto-inc/nfqueue-go/nfqueue.go:465 +0x313
created by github.com/aporeto-inc/enforcerd/vendor/github.com/aporeto-inc/nfqueue-go.CreateAndStartNfQueue
	/tmp/build/80754af9/go/src/github.com/aporeto-inc/enforcerd/vendor/github.com/aporeto-inc/nfqueue-go/nfqueue.go:117 +0x6ba
Initializing remote with fq &{QueueSeparation:false MarkValue:1000 NetworkQueue:4 NumberOfApplicationQueues:4 NumberOfNetworkQueues:4 ApplicationQueue:0 ApplicationQueueSize:500 NetworkQueueSize:500 NetworkQueuesSynStr:4:7 NetworkQueuesAckStr:4:7 NetworkQueuesSynAckStr:4:7 NetworkQueuesSvcStr:4:7 ApplicationQueuesSynStr:0:3 ApplicationQueuesAckStr:0:3 ApplicationQueuesSvcStr:0:3 ApplicationQueuesSynAckStr:0:3}

Codecov Report

Merging #300 into master will not change coverage.
The diff coverage is 0%.

@@           Coverage Diff           @@
##           master     #300   +/-   ##
=======================================
  Coverage   52.75%   52.75%
=======================================
  Files          40       40
  Lines        4428     4428
=======================================
  Hits         2336     2336
  Misses       1897     1897
  Partials      195      195

Impacted Files
Coverage Δ

enforcer/datapath_tcp.go
62.8% <0%> (ø)
:arrow_up:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update b525365...2e62ad9. Read the comment docs.


deps: Bump pytooling publishing deps

improved multi-tar extraction handling
added zst de/compression support
cleanup/simplification of signing util

Commit Message:
Additional Description:
Risk Level:
Testing:
Docs Changes:
Release Notes:
Platform Specific Features:
[Optional Runtime guard:]
[Optional Fixes #Issue]
[Optional Fixes commit #PR or SHA]
[Optional Deprecated:]
[Optional API Considerations:]

most of these updates have gone through already, the remaining one requires the fix included here


[stable/airflow] Optionally mount requirements.txt for entrypoint.sh consumption

Is this a request for help?: Maybe

Is this a BUG REPORT or FEATURE REQUEST? (choose one):
FEATURE REQUEST

Version of Helm and Kubernetes:
not relevant
Which chart:
stable/airflow
What happened:
There is no way -- except from modifying the chart -- to mount a requirements.txt in the default Docker image (puckel/docker-airflow).
What you expected to happen:
Maybe it would be valuable to modify the chart and add an option in values.yaml to mount requirements.txt in the default Docker image so that the entrypoint.sh would run pip install --user -r /requirements.txt. If that was available, users who choose to deploy DAGs via a shared persistent volume would still be able to install any Python dependencies needed by their DAGs (for example kubernetes for the KubernetesPodOperator to work).
How to reproduce it (as minimally and precisely as possible):
Just install Airflow on a Kubernetes cluster with any DAGs needing some Python dependency which is not installed (for example a DAG using a KubernetesPodOperator without the kubernetes lib). The DAG will fail and you'll have to modify the chart to run pip install or switch from the default image to another one with Python dependencies pre-installed.
Anything else we need to know:
Of course there are workarounds to this problem, but I don't think any of them are as nice as having that capability native to the chart. If I'm missing anything and there is indeed a native way of doing that without modifying the chart, then please let me know :)

Well, in fact, as I found today -  it's sufficient to put a requirements.txt at the root of your dags directory and the init container will run it.

Are you saying that placing a requirements.txt at the root of the dags directory works even for a shared persistent volume strategy, i.e. not only for a git-init strategy?

Hi. Have you found a solution, can we close this ticket?

Sure @gsemet! Thanks to you and @antweiss for the help 👍

Placing requirements.txt to DAGs root doesn't work with Shared Persistance Volume because /usr/local/scripts/install-requirements.sh && appends to deployment only if .Values.dags.initContainer.enabled is enabled. I think it is bug.


Need a Prototek member to open up for OKC-Sharp May 2nd

Could we please get someone with a Prototek membership to open the doors for us on Monday May 2nd at 11:20?
Thanks!

I'll let y'all in today :-)

Pizza for 32 ordered. Posted a screenshot in slack too


same channel hadler in many go routiens

I am having single channel handler to publish message and this handler is passed to multiple go routine at same time.
Are channel handlers thread safe?

Yes.


Incorrect version number displayed when installing

If this is a question about how to use NVM4W, please use stackoverflow instead.
If this is an issue regarding antivirus, make sure you search the existing issues first.
My Environment

[x] Windows 10

I have already...

[x] read the README to be aware of npm gotchas & antivirus issues.
[x] reviewed the wiki to make sure my issue hasn't already been resolved.
[x] verified I'm using an account with administrative privileges.
[x] searched the issues (open and closed) to make sure this isn't a duplicate.
[x] made sure this isn't a question about how to use NVM for Windows, since gitter is used for questions and comments.

My issue is related to (check only those which apply):

[ ] settings.txt
[ ] proxy support
[ ] 32 or 64 bit support

Expected Behavior
NVM should say 'installing version X.Y.X' when installing X.Y.Z, no matter what version it is.
Actual Behavior
NVM incorrectly identifies the version number when installing. This may be related to installing a version that isn't in the list (ls available only lists up to 6.9.5, but I'm installing 7.5.0).
Note: NVM installs properly, and node --version checks out correctly--the only issue here is that nvm states that it's installing the incorrect version.
Steps to reproduce the problem:
nvm install 7.5.0
Screenshot

nvm install 7.5.0
Downloading node.js version 7.5.0 (64-bit)... Complete

Where is it displaying the wrong version?
(Remember 4.1.2 is the latest version of npm)

Closing since I don't see an issue.

I seem to have been looking at the NPM version. Apparently I'm dumb...

It's easy enough to miss. If I had time, I'd add color coding or reformat in some way to make this clearer.


Feature: background shadow when clap is active

Hi,
Would you accept a PR for a background-shadow when Clap is active?
I already have a proof-of-concept branch ready, visible below.

With preview:

Yes, looks cool, I like this 👍


Support delayed values in array top

This allows using dask.delayed values in dask.array top operations.  In particular this helps to deduplicate literal numpy arrays in task graphs.
x = da.ones((10, 10), chunks=(5, 5))
y = np.ones((5, 5))

yy = delayed(y)
zz = x.map_blocks(add, yy, dtype=x.dtype)

cc @jcrist

In [1]: import dask.array as da

In [2]: import numpy as np

In [3]: from dask import delayed

In [4]: from operator import add

In [5]: x = da.random.normal(10, 1, size=(10000, 10000), chunks=(10, 10000))

In [6]: y = np.random.random((10, 10000))

In [7]: z = x.map_blocks(add, y, dtype=x.dtype)

In [8]:

In [8]: from cloudpickle import dumps

In [9]: %time sum(len(dumps(v)) for v in z.dask.values())
CPU times: user 4.34 s, sys: 1.38 s, total: 5.72 s
Wall time: 5.72 s
Out[9]:<PHONE_NUMBER>

In [10]:

In [10]: y = delayed(y)

In [11]: z = x.map_blocks(add, y, dtype=x.dtype)

In [12]: %time sum(len(dumps(v)) for v in z.dask.values())
CPU times: user 352 ms, sys: 0 ns, total: 352 ms
Wall time: 351 ms
Out[12]: 5531638

This looks good to me.


Psmisc fall back to stat, when statx is missing

Description of changes
on older kernels statx() was added to Linux in kernel 4.11; fuser -km /path fails due to statx failing, this upstream patch
https://gitlab.com/psmisc/psmisc/-/commit/c22d1e4edbfec6e24346cd8d89b822cb07cd6f5c falls back to stat when this happens
mark heroic unwrapped broken to pass nixpkgs-review, it's already broken due to unrelated issues
https://hydra.nixos.org/job/nixos/release-23.11/nixpkgs.heroic-unwrapped.aarch64-linux
Things done

Built on platform(s)

[ ] x86_64-linux
[x] 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

[x] 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.05 Release Notes (or backporting 23.05 and 23.11 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

[ ] Fits CONTRIBUTING.md.

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

I found this pr does not fix the issue everywhere, it seems in some places statx returns (via errno) EINVAL, when kernel return ENOSYS I'll investigate this more.

Is the Heroic change at all related to the Psmisc change?

The heroic change is there exclusively to make nixpkgs-review pass

Still some changes are needed, but I should probably upstream them, otherwise this is probably no-go, it's funny that strace only sees ENOSYS, so I guess glibc is silly
          postPatch = ''
            sed -i 's/else if (errno==ENOSYS)/else if (errno==ENOSYS || errno==EINVAL)/' src/statx.c
          '';

Heroic now builds on master, does not build on stable, but maybe doesn't matter.
Second psmisc patch now upstreamed and included in this pr.

Superseded by #293130


Remove standalone comment lines with only slashes

Separators with comments are generally not very useful with modern code editors and IDEs, which provide better navigation tools.
See https://github.com/godotengine/godot/issues/33027#issuecomment-1110387546.

I disagree with this change. In fact, many of the lines it removes I just added. I find that the breaks provided by comment lines help distinguish between conceptually unique parts of classes. It helps tremendously when trying to navigate large classes like the Rasterizer classes in the GLES3 code.

I'm neutral about the change, but I do take issue with the justification

Separators with comments are generally not very useful with modern code editors and IDEs, which provide better navigation tools.

Mostly because not everyone uses a full featured IDE and almost nobody does so during code review. Perhaps if github were to improve their code review tool significantly I would support this.

Why? Having separators between different classes makes it easier to differentiate between classes within the same file quickly.

Separators with comments are generally not very useful with modern code editors and IDEs, which provide better navigation tools.

Which code editors do this? I'm using Visual Studio Code, and I haven't seen any setting to automatically add separators between C++ classes, although I might just not have the right extensions or settings enabled.

I like @bruvzg's separation comment style, it's very clear, ensures consistency and has the right size to be easily noticed in the minimap some editors/IDEs provide. (I agree, ideally we should strive for one class per file, but I can see that this could be problematic in some cases like in visual_shader_nodes.cpp for example, where we have many small classes)

In PR review meeting several of us were against the idea to remove those comments. Whenever a file has multiple class implementations, it's really useful to be able to separate visually which part is which. We could discuss splitting more of the classes in separate files but that's for a different discussion and should anyway be done gradually, so we can keep/change the comment style in the meantime.
We agreed that we could harmonize how we make these separation lines though, and that include the class name would be useful. Maybe not with a full description like @bruvzg's style (or that could go in the header), but at least the name.


Move password management out of UserManager into its own injectable class

In ASP.NET Identity, I want to use LDAP (or Active Directory) for password management while storing user data using EntityFrameworkCore.  Changing the password authentication should be as simple as injecting a custom IUserPasswordStore, but the interface only provides GetPasswordHash and SetPasswordHash methods, which are not possible to use for LDAP.
I'd like to propose alternatives to a IUserPasswordStore that will move the authentication of the password out of the IUserStore implementations (which are implementing IUserPasswordStore) into a separate class/interface.
I'm thinking of something like a PasswordManager implementation of an IPasswordManager interface.
public interface IPasswordManager<TUser>
{
    bool SupportsUserPassword { get; }
    Task<PasswordManagerResult> SetPasswordAsync(TUser user, string password);
    Task<PasswordManagerResult> RemovePasswordAsync(TUser user);
    Task<bool> HasPasswordAsync(TUser user);
    Task<bool> CheckPasswordAsync(TUser user, string password);
}

Usage in the UserManager would take an IPasswordManager in the constructor, then have code changes similar to
public UserManager(IUserStore<TUser> store,
    // <truncated>
    IPasswordManager<TUser> passwordManager)
{
    // <truncated>
    PasswordManager = passwordManager;
    // <truncated>
}

public IPasswordManager PasswordManager;

protected virtual async Task<PasswordVerificationResult> VerifyPasswordAsync(PasswordManager manager, TUser user, string password)
{
    return await manager.CheckPasswordAsync(user, CancellationToken);
}

private IUserPasswordStore<TUser> GetPasswordStore()
{
    if (!PasswordManager.SupportsUserPassword)
    {
        throw new NotSupportedException(Resources.PasswordManagerDoesNotSupportPasswords);
    }
    return PasswordManager;
}

This would allow users to inject their own PasswordManager in the Startup.cs file:
services.AddDefaultIdentity<ApplicationUser>()
    .AddPasswordManager<LdapPasswordManager>() // <--- Extension method off IdentityBuilder
    .AddEntityFrameworkStores<ApplicationDbContext>();

At this point the extensibility point is UserManager and UserStore. We don't want to implement another layer of abstraction.
Why doesn't implementing your own UserManager work for your scenario? Password stores are expecting you to store the password, not call elsewhere to validate.

Closing as by design.


Diagnostic settings shared among subscription

Hi,
When I create a diagnostic setting for Activity Logs of a particular resource under a Subscription, I can see that diagnostic setting in other resources Diagnostic Settings and under the Subscription Activity Log Diagnostic Settings. Is a platform diagnostic setting shared among Subscription?
Thanks,
Canan
How to reproduce:

Create a diagnostic setting for a resource under a subscription
List diagnostic settings for other resources in that subscription
The diagnostic setting created is seen under every resource

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

ID: 9de91305-0620-591b-a706-9e748905c869
Version Independent ID: 7c3e480b-0a32-6a2f-35af-589f49318500
Content: Collect Azure resource logs in Log Analytics workspace - Azure Monitor
Content Source: articles/azure-monitor/platform/resource-logs-collect-workspace.md
Service: azure-monitor
Sub-service: logs
GitHub Login: @bwren
Microsoft Alias: bwren

@cananac Thanks for your comment! We will review and provide an update as appropriate.

@cananac Thanks for reaching out!! I have tried to reproduce the issue from my end and I couldn't find any issue. Can you please share the screenshots of the steps you have taken to notice the issue at<EMAIL_ADDRESS>along with your subscription Id and also a link to this thread (for business context).

Thanks @SwathiDhanwada-MSFT I cannot share as they are confidential  but will raise a support ticket instead. We can close the issue for now, thanks.

Thank you @cananac. We will close the issue for now. If there are further questions , please revert and we will be glad to assist you.


Size and position of edge label not changed on update

I'm writing a React application using this great library, where the user can change nearly every aspect of the graph, as well as the text of the labels. But when updating it, the size of the label background and the position of the label (centering) is not adjusted. I prepared a Codesandbox showing my approach and the problem here. Would be great to know, if this is an real issue or i missed something here.
Version: current 9.0.2

Thanks for the report :) Can you check v9.0.4?

The fix seems to work. Thank you!


Add tests to StdLibSpec checking comparison between Date & Timestamp …

When comparing Timestamp and Date returned value should always be Data.NA
Closes https://github.com/quasar-analytics/quasar/issues/1778

This test fails for most of the connectors.
@sellout @drostron @wemrysi can you check this on your side?

See, this is the kind of case where we really want universals (and type classes) in our type system. Rather than having ~ val LT(a: Comparable, b: Comparable), we should have val LT[A: Comparable](a: A, b: A). Which would allow the typechecker to 1. check the constraint and 2. check that the types match. But currently it just checks that each argument independently satisfies the constraint. So, ideally, a connector should never execute a case where the types don’t line up correctly (because the type check would prevent it).

@sellout that would be nice indeed. But for now, we should fix connectors right?

Yes, absolutely. I was just tying it back to your new book 😄

@sellout I know :)

@rabbitonweb Can you assign this PR to someone?

@djspiewak I'm happy to assign but shouldn't I wait till every connector will fix its errors?

I have a branch with the potential fix for CB here. Some attention is still due to address a few integration test failures that cropped up due to the change. I've been pulled away by a few other issues but will try and get back to this before too long.

Can we make these tests pending for the connectors the tests are failing under? Then we could get this merged.

@alissapajer @djspiewak I can make those tests pending, np

@rabbitonweb I'm working on StdLibSpec for mimir now, so since I'm already in this code, I'd be happy to make the failing tests pending so we can get this merged. Then as I mentioned in #1778 we can open individual tickets for each backend. It will be easier to track the remaining work that way, and then we don't have to have PRs open like this for a long time.

I;ve discussed with @wemrysi possible ways to make it pending for particular connector, will have it done tomorror

@alissapajer ready for review

@rabbitonweb no idea why but the travis build didn't even run for this one. Will merge when we see a green build. I'll look into it as well.

I'm pretty sure I've seen it green on Travis. But sure, re-run it, np.
Im afk
I will be back in 30min.

@rabbitonweb in the most recent build for this PR https://travis-ci.org/quasar-analytics/quasar/builds/253134766 some time-related specs are failing inquasar.std.SimplifyStdLibSpec` for all mongo backends, so they probably just need to be make pending too.

since @rabbitonweb is off on holiday starting tomorrow, I'm going to take charge of fixing the remaining compile errors so we can get this PR merged. I'll assign another reviewer before merge so I'm not merging my own work :)

Taking notes here, newly added tests are still failing in:
quasar.physical.mongodb.MongoDbJsStdLibSpec
quasar.physical.mongodb.MongoDbExprStdLibSpec
quasar.physical.sparkcore.fs.CoreMapStdLibSpec


[HUDI-2573] Fixing double locking with multi-writers

What is the purpose of the pull request

With recent refactoring for synchronous metadata patch, there was 2 code paths where double locking is happening. This patch fixes this issue.
While adding tests, also found a bug related to multi-writer and upgrade and fixed the same as well.

Brief change log

There are two code paths where deadlock happens.
a. When a table is being upgraded, and if multi-writer is enabled, we rollback all partial commits. This upgrade step itself happens within a lock, but the rollback also tries to acquire lock when committing the rollback
b. When auto commit is enabled with inline cleaning, auto clean is triggered as part of post commit which happens within a lock. But cleaning at the end when trying to commit again tries to acquire lock.
Fix: Added optionality to both rollback and clean to skip locking. These two code paths will set true for skipLocking. Also, fixed to add guards to take locks only if metadata is enabled. Prior to this patch, we take locks and then check if metadata writer is available. Some minor optimization.
While testing, came across a bug with upgrade and rollback relating to multi-writer. When a table needs an upgrade, and if multi-writer is enabled, we rollback all partial commits. This also rollsback the current transaction in flight. Added a filtering to ensure we don't rollback the current transaction that just got started and is triggering the upgrade.

Verify this pull request
This change added tests and can be verified as follows:

Added tests to TestHoodieBackedMetadata
a. testMultiWriterForDoubleLocking
b. testRollbackDuringUpgradeForDoubleLocking

Points to discuss:

I checked code paths for inline compaction and clustering and it happens just outside of transactional lock in AbstractHoodieWriteClient. But cleaning happens within transactional lock meant for inflight commit. Is that intentional or should we also move clean outside of the lock.
Two different code paths for auto commit enabled and disabled is slowly becoming a pain point. Should we look into unifying the same.

Committer checklist

[ ] Has a corresponding JIRA in PR title & commit

[ ] Commit message is descriptive of the change

[ ] CI is green

[ ] Necessary doc changes done or have another open PR

[ ] For large changes, please consider breaking it into sub-tasks under an umbrella JIRA.

LGTM!


Improve and distribute AutoResize types

Codecov Report

Merging #930 into master will not change coverage.
The diff coverage is 100%.

@@           Coverage Diff           @@
##           master     #930   +/-   ##
=======================================
  Coverage   89.87%   89.87%
=======================================
  Files          57       57
  Lines        1630     1630
=======================================
  Hits         1465     1465
  Misses        165      165

Impacted Files
Coverage Δ

source/AutoSizer/index.js
0% <ø> (ø)
:arrow_up:

source/AutoSizer/AutoSizer.js
100% <100%> (ø)
:arrow_up:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 8849d0b...4053ae2. Read the comment docs.


SSH auth

Was thinking about doing auth, and eyeing TLS, Kerberos, etc. But then I thought, wait, how do I login on my home servers? And that SSH. So I think it makes sense to default to SSH and a Go pkg exists for it.
It may be possible to shoehorn the REST stuff into SSH or rewrite that bit as well, so the whole proto becomes SSH. Added benefit IMHO is no TLS certs (and validity of those), IP only hosts and piggybacking on a well understood proto for sysadmins.
I.e. you auth with ssh, then we check if you're in the "special" group and if so you can manipulate gitopper.
Catch-22: how to setup the ssh infra to get all this  going? As said in design doc - think a custom image should solve this by having some sane default that make sense for you org

https://pkg.go.dev/golang.org/x/crypto/ssh#example-Client.Listen
but unsure how you would hook into there was our own code....

does it make sense to include all auth by ourselves, i.e. public key auth and carry the keys in the config (that we pull down anyway) - that means we don't depend on system files at all

This Go program allows me to ssh into it. I can intercept various things and then call the json creation methods that are now listed in routes.go
package main

import (
	"fmt"
	"io"
	"io/ioutil"
	"log"

	"github.com/gliderlabs/ssh"
)

func main() {
	// generate persistent key
	ssh.Handle(func(s ssh.Session) {
		io.WriteString(s, fmt.Sprintf("Hello %s %v\n", s.User(), s.Command()))
	})

	log.Println("starting ssh server on port 2222...")
	ssh.ListenAndServe(":2222", nil,
		ssh.PublicKeyAuth(func(ctx ssh.Context, key ssh.PublicKey) bool {
			data, _ := ioutil.ReadFile("/home/miek/.ssh/id_ed25519.pub")
			allowed, _, _, _, _ := ssh.ParseAuthorizedKey(data)
			return ssh.KeysEqual(key, allowed)
		}),
	)
}

We need to store the host key somewhere however - or make the client not care when it connects. I'm inclined to go for the latter, because once you store state it becomes convenient to store more of it.
Also if we pursue this we need to extend this config with pub keys of admins(?)
[[keys]]
user = "miek"
path = "keys/id_ed25519.pub"

where those keys also live in the config repo of gitopper.

closed via #17


Multiple pocketBase instances in one app

Is it possible to use multiple pocketBase instances in one app? E.g. 1 pb instance for user management and authentication. Another one for storing data and both instances sharing the same auth collection. If this is impossible, how can I use SSO using JSON Web Token (JWT)?  If both options impossible, what's your suggestion?

No, a single PocketBase instance can work only with 1 database.

If both options impossible, what's your suggestion?

I'm sorry, I don't understand your use case and why do you need 2 separate instances for auth and data to recommend a solution.

@ganigeorgiev  Thank you for the quick reply.
Let me explain my use case. I have about 40 departments and each has different application form. They only share some common entities like users, locations, departments, ..etc.  If I use 1 instance for all departments I will run out of resources quickly and PocketBase doesn't allow horizontal scaling. That's why I want use multiple instances to store formApplications data of each departments on separate instances.

I understand, but this is not possible at the moment because there is no easy mechanism out of the box to sync and share the different states and data across the multiple instances.
If a single server and a single PocketBase instance is not enough to handle your expected traffic, you can look at some other open source options that are designed with scaling from the beginning like Supabase, Nhost, SurrealDB, EdgeDB, etc.

Thank you!


FancyZones suddenly doesn't work well with my custom layout.

ℹ Computer information

PowerToys version:
PowerToy Utility:
Running PowerToys as Admin:
Windows build number: [run "winver"]

📝 Provide detailed reproduction steps (if any)

…
…
…

✔ Expected result
What is the expected result of the above steps?
❌ Actual result
What is the actual result of the above steps?
📷 Screenshots
Are there any useful screenshots? WinKey+Shift+S and then just paste them directly into the form

@ItsReizka
can you please provide some information?

I'm so sorry for not having been able to reply immediately...So my problem is that whenever I use a custom FancyZones Setup, It doesn't work properly. Like it wouldn't follow my custom window setup...And just now I checked if it's the same for the templates, and it is...it doesn't work quite well. And so are the FancyZones Settings...

@ItsReizka
can you please be more specific and explain what doesn't work?
Can you list the repro steps and explain what it exactly happening?

@ItsReizka
have you already updated to 0.23? https://github.com/microsoft/PowerToys/releases/download/v0.23.0/PowerToysSetup-0.23.0-x64.exe
Can you also be more specific in the repro steps?
The attached screen capture is not helping, it's not clear what are the action. Can you please use the Windows built in Steps Recorder?

Ah, I didn't know that there was a new version. Since when I clicked "Check for Updates" under the Updates area...It said that I had the latest version...maybe it was a bug or something??? But anyways....instead, what I did was uninstall it (the v.0.22.0) and installed the link you gave me. It now works perfectly :DD Thank you so much for your prompt replies! 👍 :)

@ItsReizka
0.22 didn't notify of 0.23 because 0.22 contains the VideoConferenceMute module that is still experimental and not present in 0.23.
If you need the VideoConferenceMute module, next week we will release 0.24 that will be based on 0.23 plus some bug fixes for the VideoConferenceMute module.


Increases assert error message coverage in parser.js

This makes it easier to identify the most valuable targets for feature addition to compiler/parser by categorizing logs from insuccessful compilations based on assert message information

Ah nice, thanks!


Add support for ufunc methods

Goal: Support the following ufunc methods in CuPy.
https://numpy.org/doc/stable/reference/ufuncs.html#methods

ufunc.outer
ufunc.at (https://github.com/cupy/cupy/pull/7062)
ufunc.reduce
ufunc.accumulate
ufunc.reduceat

v12 Goals
We've briefly investigated use-cases of these methods and targetted the following as v12 goal. Comments welcomed!

[x] ufunc.outer: support all ufuncs

https://github.com/cupy/cupy/pull/7049

[x] ufunc.at: support add, maximum, minimum, and, or, xor

https://github.com/cupy/cupy/pull/7077
https://github.com/cupy/cupy/pull/7099

[x] ufunc.reduce: support add, multiply

https://github.com/cupy/cupy/pull/7105

[x] ufunc.accumulate: support add

https://github.com/cupy/cupy/pull/7105

[x] ufunc.reduceat: support add

https://github.com/cupy/cupy/pull/7115

Updated the priority label and removed the assignee, as we have completed everything we planned for v12. Feel free to comment on this issue if you need at / reduce / accumulate / reduceat support for ufuncs other than currently supported.


Frontend: Profile Page Code !

Is your feature request related to a problem? Please describe.

A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]

Describe the solution you'd like
i would like to to code for the profile page  , can you assign this to me

A clear and concise description of what you want to happen.

@bhubesh757 okk

Below are the designs

@codewithvk @purnima143 i would like to work on this.

@bhubesh757 Any update?

@codewithvk please assign to others, i got strucked with ma exams


Play nice with others using the ios appdelegate

Hi,
I was using this very nice sample as a base for an app and wanted to add the 3D Touch plugin to add home shortcut icons.
The idea of those shortcut icons is you can redirect to different pages in your app according to the shortcut triggered.
To pull that off the dev needs to pass in a callback function, but this callback was never fired because it needs to be triggered by a function on the iOS appdelegate which turned out to be overridden by code in the statusbar util in this repo.
Since this sample is rather popular (and rightfully so) I'd like it to play nice with other code relying on adding handlers to the appdelegate, so I propose this change. It seems to work equally well, without touching the appdelegate at all.

It’s also waaaaay simpler 😄
Merged in 92e2308669bb6219cbaa6cfae8701c1a9f01cdba. Thanks!


GH-1 GH-2 Limit title and description length

[x] I understand that contributing to this repository will require me to agree with the CLA

Description
Adds a placeholder in the experience template.
Checks the description and title lengths after experience is submitted. If limits are exceeded, label "changes_requested" and comment about the problem are added. Once a user updates the body, the restrictions are automatically rechecked.

What type of PR is this? (check all applicable)

[x] 🍕 Feature
[ ] 🐛 Bug Fix
[ ] 📝 Documentation Update
[ ] 🎨 Style
[x] 🧑💻 Code Refactor
[ ] 🔥 Performance Improvements
[ ] ✅ Test
[ ] 🤖 Build
[x] 🔁 CI

Related Tickets & Documents
https://linear.app/anytype/issue/GH-1/limit-experience-description-length
Mobile & Desktop Screenshots/Recordings

Added tests?

[ ] 👍 yes
[ ] 🙅 no, because they aren't needed
[ ] 🙋 no, because I need help

Added to documentation?

[ ] 📜 README.md
[ ] 📓 tech-docs
[ ] 🙅 no documentation needed

[optional] Are there any post-deployment tasks we need to perform?

@any contributor @jmetrikat tooling


Translate fundamental SOLID documents to other languages

I know this takes a lot of time and energy but I am just putting out there. If we have translations at least in Chinese, Russian, Arabic, Vietnamese, French, German we can include more people.

Perhaps we could pair tech people with translators.  That way someone with fewer tech skills could still participate.
Also - every app developer should keep localization in mind so that their apps can eventually be translated.  We should provide guidelines and help to developers in how to do that.


HAWQ-134. Fixed 2 transaction drop table concurrently report successf…

…ully

looks good to me. +1

+1


Refactor Plausible Adapter

Bring plausible adapter over to the refactored version of the analytics library

One generic feedback about the AnalyticsException
Let's use the convention we follow in utopia-php/framework
https://github.com/utopia-php/framework/blob/master/src/Exception.php
Let's change the class and file names of AnalyticsException

Please check the failing tests as well

Please check the failing tests as well

The tests will always fail since we don't have a testing account up and ready and I don't want to run our CI against the main plausible account.


Depend on x-is-array directly.

Requiring x-is-array fron inside virtual-dom’s depnencies breaks on an npm 3.x install, since npm 3 moves x-is-array to the top level when installing. virtual-dom itself depends on the x-is-array module as published on npm, so the code should be identical.

The test fails for some npm error: failed to fetch from registry: https://registry.npmjs.org/vargs

Thanks for this PR.
I think it fails because of this
$ node --version

v0.12.7

$ npm --version

2.11.3

$ nvm --version

0.23.3

Should probably be npm v3. Can you specify the npm version in .travis.yml?

This also happens on my machine (I believed it was an issue with my local environment) so it should not be npm 3 vs 2. https://registry.npmjs.org/vargs returns an empty document instead of a package.json so I believe the problem is on npm’s end.

I’ve looked into this a bit. https://github.com/cloudhead/vargs is a really old package without a pacakge.json. It’s introduced as dependency by zuul via the wd package. Somehow I managed to run the tests on my machine by running npm test and installing packages one by one until mocha does not complain about missing module, so it looks like vargs is not strictly required, maybe just because the tests do not happen to touch the zuul codepath that uses vargs.

Probably this npm issue: https://github.com/npm/npm/issues/9178
You can try running the tests again when they solve it.

Alright, thanks for investigating. Let's see

I can confirm this. require('virtual-dom/node_modules/x-is-array') will not work with npm@3.

This is already done in Cycle DOM v5: https://github.com/cyclejs/cycle-dom/blob/master/src/virtual-hyperscript.js#L2


Fixed font-family redundancies on style.css

I changed all font: Xpx lato, sans-serif to font-size: Xpx

Looks good to me, apart the comment I just made! 👏 When you fix that, please also reword your commit message to reflect the changes, something like Remove duplicate font declarations. Just so we know just from the commit message what each commit does without having to check the changes. This makes it quicker to trace back bugs by just checking the history :)
For reference, this fixes #138. If you fix other issues in the future please say something like Fixes #XXX in the description of the PR so we don't have to search which issue (thankfully I remembered seeing it this morning so I managed). This also makes it so GitHub closes the issue automatically on merge.

I'm new to this tool (just started today) so I have a rudimentary questions.
Since I linked it to a fork and I commit a change to the font property will the pull request update automatically?

Yep, the PR always track your fork's branch. Welcome to the world of git/github and our project! If you need assistance with anything feel absolutely free to ping me on IRC or email me!
Moving to this PR, you will have to squash those two commits together so when we merge the PR we don't push all those intermediate commits to master. To do that, you will want to rewrite the history with the git rebase command. We recommend to always rebase to our latest master, so:

Add add our repo to your local git clone, alongside of your origin: git remote add lounge https://github.com/thelounge/lounge.git
Download that repo: git fetch lounge
Now you are ready to rebase: git rebase -i lounge/master

The last command should open your text editor, with your two commits and a few instructions. You will want to edit your first commit, and squash the second one. Save and exit. Git will then revert to your first commit, from which you can git commit --amend to change the commit message as I asked. Then you can git rebase --continue and git ahould squash the second commit in the first one as we told it to. And finally, you can force push those changes back to your github with git push -f origin <your-branch>. Note that rewriting history is only recommended on topic branches like that. It's heavily recommended to avoid doing that on branches other people are working on at the same time.
If you need more information, GitHub has some great documentation on that topic. Hopefully this gets you going, if not feel free to ask for more information :)

Good stuff. Could you do the the same in themes?

I'm on it as soon as I get home from work at 9pm.

That's great stuff indeed, @wesleyParriott! 👍

Could you follow @maxpoulin64's instructions (https://github.com/thelounge/lounge/pull/377#issuecomment-223739908) to squash all your commits into one before we can ship this please? Thanks!

Hey @wesleyParriott, any update on this? Also, GitHub will not let us merge until you fix the conflicts (lots have changed in 2 months as you can expect 😅), so if you could rebase on master and fix them, that'd be awesome.
Thanks!

Closing in favor of #562.


Running in a Web Worker

Since this module supports WAL mode and concurrent writes, it makes sense to wrap it in a Web Worker.

I wrote a lib a while ago to make it run in a Web Worker, might help you<EMAIL_ADDRESS>

There was another comment here that the author deleted for some reason.
But I wanted to add that I got this working in a web worker and Kysely: https://gitlab.com/soapbox-pub/ditto/-/blob/main/src/workers/sqlite.worker.ts?ref_type=heads

@alexgleason that's awesome! Just like in your repo, I think this is better done in user land, specific to the way application needs it.
I am not sure what other comment you're talking about. I'm the original author of this module and I didn't delete anything. Even if someone else from the organization deleted, it would show up. Read more here: https://docs.github.com/en/communities/moderating-comments-and-conversations/managing-disruptive-comments#deleting-a-comment

Guys it was my comment, sorry :sweat_smile: I'd written a lib to do it but forgotten that I'd deprecated it because of some issue. This issue caught my eye so I posted a comment with a link to it, but then realised the lib was deprecated and deleted my comment.

Just like in your repo, I think this is better done in user land, specific to the way application needs it.

I agree, I'll close this. Thanks for making this library, it's super helpful! The performance of x/sqlite didn't cut it, so this one is a necessity for me.

@alexgleason Thanks for posting the link to your solution! I was banging my head against the wall for a day, but you solved the problem! For reference, use Comlink! BTW your code is GREAT.
@DjDeveloperr I have a minimal example extracted from @alexgleason ' s code that I can add to the the doc.md file if you want. Might help some other folks like me.

@dustinboston that would be a welcome addition!


Update Migrating Configuration doc to RTM

This PR addresses issue https://github.com/aspnet/Docs/issues/1856 by updating the "Migrating Configuration" doc to RTM.

Thank you Scott.


Drop http2 request in two cases

Drop request on router requests to drop a request.
Drop request on writeAndFlush exceeds threshold.
Adjusted Netty High and Low WaterMark for isWriteable() tracking.

Codecov Report

Merging #1589 into master will decrease coverage by 0.06%.
The diff coverage is 79.81%.

@@             Coverage Diff              @@
##             master    #1589      +/-   ##
============================================
- Coverage     73.77%   73.70%   -0.07%
+ Complexity     8441     8413      -28
============================================
  Files           588      588
  Lines         45808    45849      +41
  Branches       5806     5810       +4
============================================
  Hits          33795    33795
- Misses        10281    10321      +40
- Partials       1732     1733       +1

Impacted Files
Coverage Δ
Complexity Δ

...i/src/main/java/com/github/ambry/network/Send.java
0.00% <ø> (-50.00%)
0.00 <0.00> (-1.00)

.../github/ambry/messageformat/MessageFormatSend.java
89.77% <0.00%> (-1.04%)
24.00 <0.00> (ø)

...in/java/com/github/ambry/network/Transmission.java
92.59% <ø> (-0.27%)
20.00 <0.00> (-1.00)

...bry/network/http2/Http2MultiplexedChannelPool.java
63.26% <ø> (ø)
27.00 <0.00> (ø)

.../java/com/github/ambry/protocol/AdminResponse.java
57.14% <ø> (-5.83%)
2.00 <0.00> (-7.00)

...github/ambry/network/http2/Http2NetworkClient.java
67.74% <26.92%> (-11.26%)
13.00 <0.00> (ø)

...om/github/ambry/network/BoundedByteBufferSend.java
33.33% <50.00%> (+1.75%)
7.00 <1.00> (+1.00)

.../java/com/github/ambry/protocol/CompositeSend.java
57.69% <50.00%> (-0.65%)
8.00 <1.00> (+1.00)
:arrow_down:

...java/com/github/ambry/network/BlockingChannel.java
82.35% <60.00%> (+0.21%)
16.00 <2.00> (ø)

.../com/github/ambry/network/SocketNetworkClient.java
93.78% <64.28%> (-0.55%)
37.00 <2.00> (-3.00)

... and 47 more

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 486d708...2702660. Read the comment docs.


Documentation Site for EKS CDK Blueprints Patterns.

Is your feature request related to a problem? Please describe.
Documentation Site for EKS CDK Blueprints Patterns.
Describe the solution you'd like
Documentation Site for EKS CDK Blueprints Patterns. We might need mkdocs in blueprints patterns site as a GTM for our patterns.
Describe alternatives you've considered
Mkdocs in blueprints cdk repo is aligned to that repo for addons.
Additional context
Add any other context or screenshots about the feature request here.

This is completed


feature: 提供主动触发异步任务机制(closed #1473)

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


chore(main): release xcm-analyser 1.2.1

:robot: I have created a release beep boop
1.2.1 (2024-04-30)
Miscellaneous Chores

xcm-analyser: Add readme (62edfc5)
xcm-analyser: Update readme (9fd5725)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/paraspell/xcm-tools/releases/tag/xcm-analyser-v1.2.1 :sunflower:


Bugfixes for PetscSolvers

PetscLinearSolver::SetOperator behaves exactly as for other iterative solvers, see https://github.com/mfem/mfem/issues/1180
Fix Jacobian callbacks to circumvent an issue with blocked operators and command line specification of the PC type as -pc_ytpe fieldsplit
For a proper fix of all the PCFIELDSPLIT cases, we also need this to be merged into PETSc maint branch https://gitlab.com/petsc/petsc/merge_requests/2364/

PR
Author
Editor
Reviewers
Assignment
Approval
Merge

https://github.com/mfem/mfem/pull/1186
@stefanozampini
@tzanio
@jandrej + @psocratis
12/09/19
12/12/19
⌛due 12/19/20

Merged in next for testing...


VS Live Unit Testing

Hello,
Firs thanks for the job.
I have some problem when running tests with Live Unit Testing as it's not using CscCommandLineArgs. So the project has no document and no reference.
I m going to investigate a bit further on this. So I can compare Items from a run with CscCommandLineArgs and without.

I just published Buildalyzer 2.0 which runs MSBuild out-of-process (as opposed to the old way of running it via MSBuild APIs). In general, if you can build it Buildalyzer should now be able to build it. Given how drastically different this new technique is, I'm closing all existing bug reports.
Please try the new version and if you're still having problems, please open a new issue.