Add __slots__ to classes for performance improvements

See https://stackoverflow.com/questions/472000/usage-of-slots for benefits of slots.
Additionally, I ran the code through a code formatter, Ruff. I'll also create a separate PR introducing some lint rules (reduces chances of bugs)
Code is UNTESTED.

My understanding of slots was that they could help improve performance when many instances of a class are made, but when there's just one, I thought it didn't really matter.
Do you think it is necessary for the IMU, Servo, Logger, and AirbrakesContext? I would argue that it adds complexity for little/no performance gain.
That being said, it is definitely a great idea for the IMUDataPacket class. Those are created every loop, so I think it would help performance for sure.
Also, I like using a linter, I was meaning to get us on one.

Okay I read more into the thread you posted, and this was what they I said:
Do not "only use __slots__ when instantiating lots of objects"
I quote:

"You would want to use __slots__ if you are going to instantiate a lot (hundreds, thousands) of objects of the same class."

Abstract Base Classes, for example, from the collections module, are not instantiated, yet __slots__ are declared for them.

Why?

If a user wishes to deny __dict__ or __weakref__ creation, those things must not be available in the parent classes.

__slots__ contributes to reusability when creating interfaces or mixins.

It is true that many Python users aren't writing for reusability, but when you are, having the option to deny unnecessary space usage is valuable.

I don't really find these reasons compelling enough. I think it makes the code a little less readable (especially for those unfamiliar with slots) and I don't think saving minute amounts of space really matters here. Additionally, the intended use of slots seems to be when you have a lot of objects, so idk if I like going against that.
All of that being said, I'm curious what you think. Did I misinterpret any of this? Also, if you think it would produce a measurable  performance increase then I'm all for it.

Do you think it is necessary for the IMU, Servo, Logger, and AirbrakesContext? I would argue that it adds complexity for little/no performance gain.

imo there is basically no added complexity when slots are added for a small codebase like ours. Personally, when I implemented slots for a big library (~50k+ LoC), while it did initially require some refactoring, but in the end it actually helped promote good coding practices, such as not adding attributes (accidently) to classes, e.g. MyClass().some_random_attr = 1, and users reported tremendous memory savings and slight performance increases, despite not having "thousands" of classes being initialized.

Abstract Base Classes, for example, from the collections module, are not instantiated, yet slots are declared for them.

I would also like to add that most built in classes in the standard library now have __slots__ defined for them, and it's really an easy optimization trick.

I think it makes the code a little less readable (especially for those unfamiliar with slots)

While I would agree that it's not understood at first glance, it's not really a reason to ignore a feature of the language. A short comment about slots linking to any of the articles would suffice imo.
Additionally, we could "automate" the creation of slots through dataclasses, but that is actually some added complexity which I think we should avoid, since it doesn't actually provide any further benefits, other than less lines of code.
The little performance gain for our use case is comparable to upgrading from py 3.9 to py 3.12 (without build time optimizations) 😉


Move MD5 mesh + animation into class library

OOP-ify it!

Creating separate issue for feature request.


Compliance Report B | Units Column |1|

Task:
This card is to create the functionality needed for the Units column for each fuel reported under Schedule B - Part 3 Fuel Supply.
Non-editable:
The fuel supplier user should not be able to edit this column
Units:
This column should be auto-populated based on the fuel selected within the Fuel Type column, created in Card 1386.
Units for the different fuel types:

Show 'L': Ethanol, Biodiesel, HDRD, Petroleum-based gasoline, Petroleum-based diesel, Propane, Renewable diesel, Natural gas-based gasoline, Renewable gasoline
Show 'kg': Hydrogen, LNG
Show 'kWh': Electricity
Show 'm3' (the 3 should be superscript as m3 is cubic metres) for: CNG

Schedule C:

Schedule C has a units column with identical functionality, see Card 1298 for more information about the functionality of this column.

https://trello.com/c/dtVAUz7K/1391-compliance-report-b-units-column-1

 Compliance Report B | Units Column |1|


Introduction of sub-parts.

When designing a part, it may include multiple subparts. It would be ideal to create sub-parts independently, but refer to a group of sub-parts as a part. Sub-parts would share a part's transformations and affect its cumulative properties.

The three sub-parts make up the whole of the ball bearing part.
Each sub-part can have a material and weight, affecting the overall properties of the ball bearing; or the part can be given properties, ignore the properties of its constituents.

In Blender, this may be  parenting objects.
In Onshape, this may be creating composite parts: https://premiercb.onshape.com/help/Content/composite_part.htm?Highlight=composite or it might be a managed attribute.

Closing, duplicate of #194

I don't know if CodeToCAD will have the concept of an Assembly. At this time I think it will be implied. If you Joint two or more parts, that in itself is an Assembly. We MAY have an Assembly class to do automation on software that have an Assembly tab or window.
Also, to select multiple entities belonging to the same group, just add their references to an array. E.g. ball_bearing = [inner_ring, outer_ring, spherical_balls], or create a dataclass to reference them.


Name change

If I write a function called
public bool VBFileCountLines() the AI converts it as
public bool CSharpFileCountLines()

Thank you for reporting. We will add an instruction about not changing any method/variable names whenever it's possible.
Best Regards,
Jon


fix: add secondary IPs for enrichment

Description
Please provide a brief description of the changes made in this pull request.
Related Issue
Fixes #224
Checklist

[x] I have read the contributing documentation.
[x] I signed and signed-off the commits (git commit -S -s ...). See this documentation on signing commits.
[x] I have correctly attributed the author(s) of the code.
[x] I have tested the changes locally.
[x] I have followed the project's style guidelines.
[x] I have updated the documentation, if necessary.
[x] I have added tests, if applicable.

Screenshots (if applicable) or Testing Completed

Additional Notes
Both the previous implementation and this PR don't clear stale IP-endpoint bindings immediately from the ipToEpKey Map.
E.g. When endpoint A changes from IP address "<IP_ADDRESS>" to "<IP_ADDRESS>", the stale binding between the IP address "<IP_ADDRESS>" and endpoint A is still in the ipToEpKey map until the IP address "<IP_ADDRESS>" gets reassigned to another pod.
However, this shouldn't be a problem. The DNS is supposed to provide up-to-date IP addresses for the sender and receiver so that any flow event will always contain the latest IP addresses.

@rbtr Hi Evan, Could you give me another approval for running the CI tests? Thanks!

hey @FZhg it looks like your branch has conflicts, can you rebase it and resolve them? Please update it against latest main also, your diff is showing other changes than just yours and I think a rebase would resolve this.

hey @FZhg it looks like your branch has conflicts, can you resolve them? Please update it against latest main also, your diff is showing other changes than just yours and I think a rebase (git fetch --all && git rebase upstream/main or equivalent based on your repository config) would resolve this.

Thanks for your help! Problem solved.

lgmt, thank you for your contribution


Version 7 -> 8 Roadmap

This issue is outlining what needs to be done in version 7 before we can move to version 8 in earnest.

Once ALL items in version 7 are complete, we can consider moving the 8.x branch to master, and create a 7.x` branch.
Once ALL items in version 8 are finalized and implemented, we can move from 8.x.x-alpha to 8.x.x-beta.

In Version 7

[x] groupBy config (#5679)
[x] share observable resets (#6169)
[x] splitBy (#3807)
[x] Add all exports to top level
[x] More configurable retry (#6421)
[x] More configurable repeat (#6640)
[x] Deprecate MapTo variants (#6399, PR: #6860)
[x] Deprecate retryWhen/repeatWhen? (#6859)
[x] Deprecate onErrorResumeNext operator in favor of onErrorResumeNextWith (#6755)
[x] Various selectors/arguments should support ObservableInput

[x] delayWhen's notifier (#7049),
[x] buffer's closingNotifier (#7073),
[x] distinct's flushes (#7081),
[x] repeatWhen's notifier (#7103),
[x] sample's notifier (#7104),
[x] retryWhen's notifier (#7105),
[x] sequenceEqual's compareTo (#7102),
[x] ShareConfig's resetOnError, resetOnComplete and resetOnRefCountZero (#7093),
[x] skipUntil's notifier (#7091) and
[x] window's windowBoundaries (#7088)

Before Version 8 is released

[ ] Remove all deprecated APIs marked to be removed in v8 or marked deprecated ages ago.
[ ] Remove source parameters from predicates. (Deprecating these via the type system effects problems - see #6361.)
[x] Ensure we're publishing only ES2021 or later and CJS. Drop tslib. (#6321)
[x] Drop all Internet Explorer support into a pit of flames! 🔥 IE 🔥 🥳
[x] Idempotent subscription add (#6401)
[ ] Replace all external uses of any with unknown. (This could likely be non-breaking, FWIW.)
[ ] productize our internals for creating operators (#6803)
[ ] Implement [Symbol.asyncIterator]() on Observable (TBD. We should try this out in an alpha, at least. Issue: #6857)
[x] Convert repo to monorepo (#6786)

[ ] Docs app can be a separate project under monorepo
[ ] Operator Decision Tree can also likely be its own project under monorepo
[ ] Keep rxjs as "whole package". (It's not going away, ever, really)
[ ] Publish @rxjs/observable with just Observable.
[ ] Publish @rxjs/ajax
[ ] Publish @rxjs/fetch
[ ] Publish @rxjs/testing
[ ] Decide on how we'll do other packages: Current thoughts are that we could publish a package for each operator, even. Subjects and multicasting might be trickier, but maybe not. Maybe individual packages is right for all. Needs discussion.

[ ] ??? TBD

During Version 8

[ ] Create new schedulers and deprecate old schedulers.
[ ] Implement Symbol.asyncIterator on observable. (https://github.com/ReactiveX/rxjs/discussions/6779)

🔥 IE 🔥 🥳 - every time I see that statement in some repo it makes my day better

Since "??? TBD" seems to imply we can suggest anything, what about https://github.com/ReactiveX/rxjs/issues/2686?
It seems to be a recurring "issue" people are having to configure headers for every request (most popular seem to be Bearer, CorrelationId and Content-Type).
While it's not "hard" to make your own ajax, I feel it's a bit sad everyone has to write that piece of code and it might be helpful for everyone to have an helper provided by rxjs.

Wouldn't publishing multiple packages for what is essentially the same code actually increase risk of non tree shakable use-case and thus increase bundle size ?
As seen with lodash, if one of my dependency decides to depends on the future @rxjs/observable, but my app depends on the current rxjs, then all the code from @rxjs/observable will essentially be bundled twice, won't it ?
And of course it would be much worse if we actually publish a package for each operator. Then a single operator could be bundled three times if my deps happened to depend on rxjs, @rxjs/operators and say @rxjs/operators-map.
I could also imagine compatibility issues if one of my dependency depends on an old version of  @rxjs/observable and my app pass one of those object to a new, incompatible version of an operator coming from the latest version of rxjs. This kind of issue already happened with the graphql package where they had to add manual check in their code to throw error if it happens.
That seems a lot of tricky tradeoffs to attempt to solve the issue of bundle size that is already properly solved by tree shaking.
Is that really worth it ? :thinking:

It looks like the items for version 7 are all done except one. Is there any progress? Feels a bit stagnated ):

Do you honestly think this signature change on the subscribe, etc. methods is critical enough to cause billions of lines of code change across the internet?

You seem to have "Publish @rxjs/fetch" twice. I'm sure it will be an awesome package but it probably only needs to be done once 😋

@benlesh, it seems development toward v8 is picking up lately. However I am not aware that the concerns expressed in https://github.com/ReactiveX/rxjs/issues/6367#issuecomment-1122351023 and https://github.com/ReactiveX/rxjs/issues/6786#issuecomment-1172953044 have been addressed. And it seems a few persons are sharing those concerns.
Is the plan still to split in multiple, possibly redundant, packages ? What's the team opinion about the pitfalls of such a strategy, as experienced by lodash and graphql (for example) ?

have you considered 8.x being your first esm-only version of rxjs? seems to me it is the ideal opportunity to do that.
we're now at a point where most consumers are on a version of node which is capable of importing ESM packages, and all popular bundlers are too.
anyone who can only use CJS must be on a fairly old node version, so are likely going to be fine sticking to rxjs 7.x.
there's a few hazards and disadvantages with dual packages (esm + cjs), and the complexity of the build scripts for contributors/maintainers etc.
you mentioned you considered publishing CJS and ESM packages separately, but i wouldn't bother to be honest. many other packages have already moved to pure ESM and consumers managed fine, imo we could do the same her.e

Just tested latest alpha release and these errors appear, is that on purpose? If yes, I would go and open issues on GH for these.

Wouldn't publishing multiple packages for what is essentially the same code actually increase risk of non tree shakable use-case and thus increase bundle size ?

It shouldn't... rxjs itself will re-export @rxjs/observable, @rxjs/fetch, et al. So there's only really one copy of those dependencies. The only real risk is the same risk we've always had, where a dependency can depend on rxjs, and then you can depend on rxjs and you end up with two different versions in your codebase... if your bundler/repo isn't set up properly, you're doomed in that scenario even WITHOUT this change.

Do you honestly think this signature change on the subscribe, etc. methods is critical enough to cause billions of lines of code change across the internet?

Yes. In order to align with native observables, the change to subscribe is required to move forward. However, you're wrong that it will "cause billions of lines of code change". Whatever version of RxJS that code is using will still exist. There's very, very little chance of any security issues or reasons to change those old versions, and if there were, we'd just fix it and publish a new 7.x or whatever.

have you considered 8.x being your first esm-only version of rxjs?

We can't really do this yet. There are way too many people using RxJS with CJS still. Myself included.

For those of you wondering about the path of different packages for each thing... the primary motivator is around how many libraries choose to use some other, untested, and or cobbled-together observable implementation because they "don't want all of RxJS". This causes us to end up shipping our observables alongside other people's observables in the same bundles, and then it causes developers to need to deal with interop, etc.
Ideally, we can convince developers that want observables to use the most battle tested and common implementation, at least until native observables land.

What is the status of this?

@benlesh Is the idea then that version 8 will eventually be released using a polyfilled version of the Web Platform observable?

There will be an optional polyfill, or an identical observable to directly import. The RxJS observable will pass all web platform tests as well, and there will be some backwards compat solution.


occur error when generate client key

Dear Sir
I'me the new beginner and start to learn ubuntu
I got error when use this script, same error as post here https://github.com/OpenVPN/easy-rsa/issues/261
"Can't load /etc/openvpn/server/easy-rsa/pki/.rnd into RNG"
not sure how to solve this error due to my poor english, could you please help check that?
Thanks
System: ubuntu 18.04
`root@ubuntu:~# wget https://git.io/vpn -O openvpn-install.sh && bash openvpn-install.sh
--2020-03-22 22:53:29--  https://git.io/vpn
Resolving git.io (git.io)... <IP_ADDRESS>, <IP_ADDRESS>, <IP_ADDRESS>, ...
Connecting to git.io (git.io)|<IP_ADDRESS>|:443... connected.
HTTP request sent, awaiting response... 302 Found
Location: https://raw.github.com/Nyr/openvpn-install/master/openvpn-install.sh [following]
--2020-03-22 22:53:31--  https://raw.github.com/Nyr/openvpn-install/master/openvpn-install.sh
Resolving raw.github.com (raw.github.com)... <IP_ADDRESS>, <IP_ADDRESS>, <IP_ADDRESS>, ...
Connecting to raw.github.com (raw.github.com)|<IP_ADDRESS>|:443... connected.
HTTP request sent, awaiting response... 301 Moved Permanently
Location: https://raw.githubusercontent.com/Nyr/openvpn-install/master/openvpn-install.sh [following]
--2020-03-22 22:53:33--  https://raw.githubusercontent.com/Nyr/openvpn-install/master/openvpn-install.sh
Resolving raw.githubusercontent.com (raw.githubusercontent.com)... <IP_ADDRESS>, <IP_ADDRESS>, <IP_ADDRESS>, ...
Connecting to raw.githubusercontent.com (raw.githubusercontent.com)|<IP_ADDRESS>|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 17623 (17K) [text/plain]
Saving to: ‘openvpn-install.sh’
openvpn-install.sh                          100%[===========================================================================================>]  17.21K  --.-KB/s    in 0.04s
Welcome to this OpenVPN road warrior installer!
I need to ask you a few questions before starting setup.
You can use the default options and just press enter if you are ok with them.
This server is behind NAT. What is the public IPv4 address or hostname?
Public IPv4 address / hostname [<IP_ADDRESS>]: <IP_ADDRESS>
Which protocol do you want for OpenVPN connections?

UDP (recommended)
TCP
Protocol [1]: 1

What port do you want OpenVPN listening to?
Port [1194]: 11194
Which DNS do you want to use with the VPN?

Current system resolvers
<IP_ADDRESS>
Google
OpenDNS
Verisign
DNS [1]: 1

Finally, tell me a name for the client certificate.
Client name [client]: jian
Okay, that was all I needed. We are ready to set up your OpenVPN server now.
Press any key to continue...
Hit:1 http://mirrors.aliyun.com/ubuntu bionic InRelease
Hit:2 http://mirrors.aliyun.com/ubuntu bionic-updates InRelease
Hit:3 http://mirrors.aliyun.com/ubuntu bionic-backports InRelease
Hit:4 http://mirrors.aliyun.com/ubuntu bionic-security InRelease
Hit:5 http://ppa.launchpad.net/hollywood/ppa/ubuntu bionic InRelease
Reading package lists... Done
Reading package lists... Done
Building dependency tree
Reading state information... Done
ca-certificates is already the newest version (20180409).
iptables is already the newest version (1.6.1-2ubuntu2).
openssl is already the newest version (1.1.1-1ubuntu2.1~18.04.5).
Suggested packages:
easy-rsa resolvconf
The following NEW packages will be installed:
openvpn
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 0 B/470 kB of archives.
After this operation, 1,136 kB of additional disk space will be used.
Preconfiguring packages ...
Selecting previously unselected package openvpn.
(Reading database ... 157401 files and directories currently installed.)
Preparing to unpack .../openvpn_2.4.4-2ubuntu1.3_amd64.deb ...
Unpacking openvpn (2.4.4-2ubuntu1.3) ...
Setting up openvpn (2.4.4-2ubuntu1.3) ...

Restarting virtual private network daemon.                                                                                [ OK ]
Created symlink /etc/systemd/system/multi-user.target.wants/openvpn.service → /lib/systemd/system/openvpn.service.
Processing triggers for man-db (2.8.3-2ubuntu0.1) ...
Processing triggers for ureadahead (0.100.0-21) ...
Processing triggers for systemd (237-3ubuntu10.39) ...

Using SSL: openssl OpenSSL 1.1.1  11 Sep 2018
init-pki complete; you may now create a CA or requests.
Your newly created PKI dir is: /etc/openvpn/server/easy-rsa/pki
Generating RSA private key, 2048 bit long modulus (2 primes)
....................................+++++
............+++++
e is 65537 (0x010001)
Can't load /etc/openvpn/server/easy-rsa/pki/.rnd into RNG
140105300844992:error:2406F079:random number generator:RAND_load_file:Cannot open file:../crypto/rand/randfile.c:88:Filename=/etc/openvpn/server/easy-rsa/pki/.rnd
Using SSL: openssl OpenSSL 1.1.1  11 Sep 2018
Can't load /etc/openvpn/server/easy-rsa/pki/.rnd into RNG
140700857864640:error:2406F079:random number generator:RAND_load_file:Cannot open file:../crypto/rand/randfile.c:88:Filename=/etc/openvpn/server/easy-rsa/pki/.rnd
Generating a RSA private key
............+++++
............................................................................................+++++
writing new private key to '/etc/openvpn/server/easy-rsa/pki/private/server.key.czoY25m7Sf'
Using configuration from ./safessl-easyrsa.cnf
Can't load /etc/openvpn/server/easy-rsa/pki/.rnd into RNG
140238996201920:error:2406F079:random number generator:RAND_load_file:Cannot open file:../crypto/rand/randfile.c:88:Filename=/etc/openvpn/server/easy-rsa/pki/.rnd
Can't open /etc/openvpn/server/easy-rsa/pki/index.txt.attr for reading, No such file or directory
140238996201920:error:02001002:system library:fopen:No such file or directory:../crypto/bio/bss_file.c:72:fopen('/etc/openvpn/server/easy-rsa/pki/index.txt.attr','r')
140238996201920:error:2006D080:BIO routines:BIO_new_file:no such file:../crypto/bio/bss_file.c:79:
Check that the request matches the signature
Signature ok
The Subject's Distinguished Name is as follows
commonName            :ASN.1 12:'server'
Certificate is to be certified until Mar 20 14:35:46 2030 GMT (3650 days)
Write out database with 1 new entries
Data Base Updated
Using SSL: openssl OpenSSL 1.1.1  11 Sep 2018
Can't load /etc/openvpn/server/easy-rsa/pki/.rnd into RNG
139700686315968:error:2406F079:random number generator:RAND_load_file:Cannot open file:../crypto/rand/randfile.c:88:Filename=/etc/openvpn/server/easy-rsa/pki/.rnd
Generating a RSA private key
..........................+++++
..........+++++
writing new private key to '/etc/openvpn/server/easy-rsa/pki/private/jian.key.h5szVJ44C6'
Using configuration from ./safessl-easyrsa.cnf
Can't load /etc/openvpn/server/easy-rsa/pki/.rnd into RNG
140429172212160:error:2406F079:random number generator:RAND_load_file:Cannot open file:../crypto/rand/randfile.c:88:Filename=/etc/openvpn/server/easy-rsa/pki/.rnd
Check that the request matches the signature
Signature ok
The Subject's Distinguished Name is as follows
commonName            :ASN.1 12:'jian'
Certificate is to be certified until Mar 20 14:35:46 2030 GMT (3650 days)
Write out database with 1 new entries
Data Base Updated
Using SSL: openssl OpenSSL 1.1.1  11 Sep 2018
Using configuration from ./safessl-easyrsa.cnf
Can't load /etc/openvpn/server/easy-rsa/pki/.rnd into RNG
140606435611072:error:2406F079:random number generator:RAND_load_file:Cannot open file:../crypto/rand/randfile.c:88:Filename=/etc/openvpn/server/easy-rsa/pki/.rnd
An updated CRL has been created.
CRL file: /etc/openvpn/server/easy-rsa/pki/crl.pem
Created symlink /etc/systemd/system/multi-user.target.wants/openvpn-iptables.service → /etc/systemd/system/openvpn-iptables.service.
Created symlink<EMAIL_ADDRESS>→<EMAIL_ADDRESS>Finished!
Your client configuration is available at: /root/jian.ovpn
If you want to add more clients, just run this script again!
`

You can safely ignore that message.


AMBARI-25243. Tez/MR service check fails with ClassNotFoundException LzoCodec during host ordered upgrade (amagyar)

What changes were proposed in this pull request?
After host upgrade Tez/MR service checks fail because of a classpath issue.
The classpath used by on the client side is:
/usr/hdp/<NEW.HDP.VERSION>/hadoop/lib/hadoop-lzo-0.6.0.<NEW.HDP.VERSION>.jar

LzoPackage is installed lazily therefore it's not available at the server side. This patch ensures that LZO is installed before the upgrade.
How was this patch tested?

Performed host ordered upgrade with TEZ service check enabled

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/Ambari-Github-PullRequest-Builder/5135/
Test FAILed.
Test FAILured.

retest this please

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/Ambari-Github-PullRequest-Builder/5136/
Test PASSed.


How do I disable http and enable https?

Currently I am accessing the controller page using http.
How could I enable https and disable http?

Documentation on this subject would be greatly appreciated! Also, doing so with private certificates would also be a great topic.

In lieu of this, I've taken the route of setting up a SSL reverse proxy with nginx. Having documentation on the subject would still be helpful.

Using the reverse proxy how do you disable http?  Can't a user "go around" the reverse proxy and use http unless you have a firewall or something else in place to stop that traffic?

If you're concerned about this, you can modify the docker containers to listen on localhost instead. There's sufficient documentation on the subject.   Agreed on the need for docs, I think this should be in the roadmap for the next release.


Added client_max_body_size 0

While in apicast there is this settings this should be here too to permit upload of file of any size

👍 but wildcard router is going away in the next release and there are no patch releases planned for the existing releases. I'm happy to merge it, but it won't get released :-/

DOH! 🤦🏻♂


⚠ Jenkins Plugins Artifactory has degraded performance

In 13b67ac, Jenkins Plugins Artifactory (https://get.jenkins.io/plugins/artifactory/) experienced degraded performance:

HTTP code: 200
Response time: 1374 ms

Resolved: Jenkins Plugins Artifactory performance has improved in 8653add after 13 minutes.


Event Subprocess v7 Migration

{placeholder}

https://github.com/apache/incubator-kie-kogito-runtimes/pull/3552


Issue #1063 - add test for using takeLatest on an actionChannel

Oh, I see what u meant! I think buffers.sliding(1) is exactly what you need. :)

Oh, I see what u meant! I think buffers.sliding(1) is exactly what you need. :)

after looking in to it some more that, buffers.dropping(1) looks like what I want (I just need to know if there was a new action buffered), but now when I use it, my tests fail when I compare:
assert.deepEqual(gen.next().value, actionChannel(TYPE, buffers.dropping(1)));

When I log the two values I get this:
{ '@@redux-saga/IO': true,
  ACTION_CHANNEL:
   { pattern: 'TYPE',
     buffer:
      { isEmpty: [Function: isEmpty],
        put: [Function: put],
        take: [Function: take],
        flush: [Function: flush] } } }
{ '@@redux-saga/IO': true,
  ACTION_CHANNEL:
   { pattern: 'TYPE',
     buffer:
      { isEmpty: [Function: isEmpty],
        put: [Function: put],
        take: [Function: take],
        flush: [Function: flush] } } }

So I guess that the functions are being compared and they are not equal.

@Andarist I recreated my test in #1085 to show what is failing.

Going to close this one as it seems not relevant anymore, please ping me here if you feel it needs reopening though.


Finding loci via a distance based clumping

When given a set of single point associations, lead snps are identified using windows of a given size, where the distance between leads cannot be smaller than the window size.

The algorithm orders positions by p-value,
Then finds the most significant association
Excludes all further associations from testing where the position is less than the window size from the found lead.
Repeats until no variants left.

The function returns with a study-locus object

Codecov Report

Merging #97 (338ed5c) into main (d3f2e1b) will decrease coverage by 0.38%.
The diff coverage is 62.96%.

@@            Coverage Diff             @@
##             main      #97      +/-   ##
==========================================
- Coverage   80.39%   80.01%   -0.38%
==========================================
  Files          43       44       +1
  Lines        1214     1241      +27
==========================================
+ Hits          976      993      +17
- Misses        238      248      +10

Impacted Files
Coverage Δ

src/otg/method/window_based_clumping.py
62.96% <62.96%> (ø)

I added some updates:

Minor bugfix from 465306d
Testing increased to 100% coverage of the new method (semantic testing of the clump function is not implemented)
Window-based clumping added to the documentation
SummaryStatistics now has a function to clump using the new method. Tests for the new function were also added.

The result is that the tests are failing because the output of the clump function doesn't yet look like a StudyLocus. If I'm not missing anything this is the only thing pending.


Simple arraylist

Hello,
is there a simple ArrayList like we know it from Java?
I could only find a LinkedList in this library :/

you are probably looking for native [], or new Array()

Closing this because of old age. If the issue persists, discuss it here and/or open a Pull Request please.


Help me fix my markdown emojis on collections_resources page

My :arrow_upper_right: emojis aren't working :sob:

I took them out!


Clean up the repo and initial build up files

The initial 0.1.0 contains some redundancies, so this merge  request attempts to offer the following fix:

[x] Remove Webpack which is the current bundler and use Rollup.js instead

[x] Add build config for commonJs, es modules environment as well as umd builds

[x] Add prettier configuration as default repo formatter

[ ] Add test for store , responseHandler files using Jest

[ ] Remove all dependencies except axios

Also check this https://github.com/kunyora/kunyora/pull/1/commits/471f905af48d14d47028698224a2583b0885667d . I feel its quite basic enough for a deep copying function for the store @kayslay


[Python] Replace global linting excludes with local line-level excludes ("noqa")

What's in this pull request?
Replace the project global linting rule excludes (as defined in .pep8) with fine-grained # noqa annotations.
By using noqa annotations the excludes are made on a per line basis instead of globally.
These annotations are used where we make deliberate deviations from the standard linting rules.
To lint the Python code in the project:
  $ flake8

To install flake8:
  $ pip install flake8

See https://flake8.readthedocs.org/en/latest/ for details.
To enable checking of the PEP-8 naming conventions, install the optional extension pep8-naming:
  $ pip install pep8-naming

To enable checking of blind except: statements, install the optional extension flake8-blind-except:
  $ pip install flake8-blind-except

To enable checking of import statement order, install the optional extension flake8-import-order:
  $ pip install flake8-import-order

Resolved bug number: –

Before merging this pull request to apple/swift repository:

[ ] Test pull request on Swift continuous integration.

Triggering Swift CI
The swift-ci is triggered by writing a comment on this PR addressed to the GitHub user @swift-ci. Different tests will run depending on the specific comment that you use. The currently available comments are:
Smoke Testing
    Platform     | Comment
    ------------ | -------------
    All supported platforms     | @swift-ci Please smoke test
    OS X platform               | @swift-ci Please smoke test OS X platform
    Linux platform              | @swift-ci Please smoke test Linux platform

Validation Testing
    Platform     | Comment
    ------------ | -------------
    All supported platforms     | @swift-ci Please test
    OS X platform               | @swift-ci Please test OS X platform
    Linux platform              | @swift-ci Please test Linux platform

Note: Only members of the Apple organization can trigger swift-ci.

@swift-ci Please test

@swift-ci Please test again - I think the build failures were unrelated to this PR :-)

@swift-ci Please test

@swift-ci Please test again - I think the build failures were unrelated to this PR :-)

@swift-ci Please test


Feathers doesn't exit when generating a Generic Service

This is a low priority issue. After creating a generic service (no database) the CLI tool won't release the command prompt.
Steps to reproduce:

Generate a new service using feathers generate service
When prompted, enter the name you want to give it, then select generic and, finally, select wether or not you need auth.
You'll see that Feathers generates the corresponding files and then the command prompt stays as local@mbp~$ (or whatever your hostname is). Trying to run ls results in an Invalid command error and displays all available commands.

Workaround:
Just hit Ctrl+c to exit manually.

Fixed with version 2.0 that is coming. You can use the workaround for now.

To dig this up, I'm using the latest version of the cli but when I try to generate a new service I get the error as follows:
events.js:141
      throw er; // Unhandled 'error' event
      ^

Error: No function expression found after module.exports
    at Object.exports.addLastInFunction (C:\Users\Steven.Lambe\AppData\Roaming\npm\node_modules\feathers-cli\node_modules\generator-feathers\lib\transform.js:81:11)
    at importService (C:\Users\Steven.Lambe\AppData\Roaming\npm\node_modules\feathers-cli\node_modules\generator-feathers\generators\service\index.js:16:15)
    at module.exports.generators.Base.extend.writing (C:\Users\Steven.Lambe\AppData\Roaming\npm\node_modules\feathers-cli\node_modules\generator-feathers\generators\service\index.js:171:5)
    at Object.<anonymous> (C:\Users\Steven.Lambe\AppData\Roaming\npm\node_modules\feathers-cli\node_modules\yeoman-generator\lib\base.js:439:23)
    at C:\Users\Steven.Lambe\AppData\Roaming\npm\node_modules\feathers-cli\node_modules\run-async\index.js:26:25
    at new Promise (C:\Users\Steven.Lambe\AppData\Roaming\npm\node_modules\feathers-cli\node_modules\core-js\modules\es6.promise.js:191:7)
    at C:\Users\Steven.Lambe\AppData\Roaming\npm\node_modules\feathers-cli\node_modules\run-async\index.js:25:19
    at C:\Users\Steven.Lambe\AppData\Roaming\npm\node_modules\feathers-cli\node_modules\yeoman-generator\lib\base.js:440:9
    at processImmediate [as _immediateCallback] (timers.js:383:17)


How to connect to ipv6 server?

I'm connecting ipv4 server with
var net = require('react-native-tcp');
var client = new net.Socket();
client.connect('port', 'ipv4-address', function() {});
// client = net.createConnection('port', 'address')

However, it's not work when I try to connect to ipv6 server.
What's the proper way to connect the socket server? thanks!

thanks for the PR!

Hi,
any update on this issue?
#Thanks


[SPARK-10613] [SQL] Reduce LocalNode tests dependency on SQLContext

This is WIP. The remaining tasks include:

Fix TakeOrderedAndProjectSuite, where tests are currently ignored
Do HashJoinNodeSuite
Actually remove SharedSQLContext from LocalNodeTest

@zsxwing please have a look in the mean time. Thanks.

Merged build triggered.

Merged build started.

Test build #42479 has started for   PR 8764 at commit 0030ba0.

Test build #42479 has finished for   PR 8764 at commit 0030ba0.

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

Merged build finished. Test PASSed.

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

Fix TakeOrderedAndProjectSuite, where tests are currently ignored

I didn't notice java.util.PriorityQueue.iterator doesn't guarantee the order. Could you fix this line: https://github.com/apache/spark/blob/e626ac5f5c27dcc74113070f2fec03682bcd12bd/sql/core/src/main/scala/org/apache/spark/sql/execution/local/TakeOrderedAndProjectNode.scala#L53 ?
It should be queue.toArray.sorted(ord).iterator.

Merged build triggered.

Merged build started.

Alright, as of the latest commit I believe this patch is finished on my side. @zsxwing I fixed the take ordered issue we discussed, filed a new JIRA SPARK-10624 for it, and included the fix in this patch.

Merged build triggered.

Merged build started.

Test build #42510 has started for   PR 8764 at commit 3bd5ac7.

Merged build finished. Test FAILed.

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

Test build #1762 has started for   PR 8764 at commit 3bd5ac7.

Test build #1763 has started for   PR 8764 at commit 3bd5ac7.

Test build #1761 has started for   PR 8764 at commit 3bd5ac7.

Looks like the relevant tests have already passed. Merging into master.

Thanks @andrewor14 I will update #8769 as per your changes.

Test build #42510 has finished for   PR 8764 at commit 3bd5ac7.

This patch passes all tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
abstract class LocalNode(conf: SQLConf) extends QueryPlan[LocalNode] with Logging

Merged build finished. Test PASSed.

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

Test build #1761 has finished for   PR 8764 at commit 3bd5ac7.

This patch passes all tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
abstract class LocalNode(conf: SQLConf) extends QueryPlan[LocalNode] with Logging

Test build #1763 has finished for   PR 8764 at commit 3bd5ac7.

This patch passes all tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
abstract class LocalNode(conf: SQLConf) extends QueryPlan[LocalNode] with Logging

Test build #1762 has finished for   PR 8764 at commit 3bd5ac7.

This patch passes all tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
abstract class LocalNode(conf: SQLConf) extends QueryPlan[LocalNode] with Logging


Add private 'pic_path' parameter

Need a new pic_path parameter to be used in mod_rewrite.  Will replace cur_url and pic params which are user visible.
Later want to deprecate the old params.

pic_path is fully functional now, however internal links need to be updated to remove deprecated params pic and cur_url.

pic_path is fully functional now.  See #21 for cleanup.


Update yourdfpy now that the NumPy issue is fixed

See https://github.com/clemense/yourdfpy/pull/46

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 97.895%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
651

Relevant Lines:
665

💛  - Coveralls


packages are missing.

I'm able to configure the relation between projects. but for project "waltz-schema" the below package is missing.
"com.khartec.waltz.schema.tables".

for project "waltz-model" the Immutable_* classes are missing.

The classes you mention are generated during the build process.
They are the output from the Immutables library and from jOOQ

Hello David Watkins
Thank you very much for the reply,
I have checked the doc and try to build the application via Travis.
As my understanding I need database structure for JOOQ, the JOOQ will
generate java class from the database structure. generate where we mention
the packages for java class.
kindly request please mention the database exported script location.
below links are not mentioning the database architecture.
https://github.com/davidwatkins73/waltz-dev/blob/master/docs/features/entity_notes/entity_notes_schema.txt
https://github.com/davidwatkins73/waltz-dev/blob/master/docs/features/flow_diagrams/flow_diagram_schema.txt
https://github.com/davidwatkins73/waltz-dev/blob/master/docs/features/logical_flows/logical_flows_schema.png
kindly request please suggest.
Regards,
Rajesh Gupta
On Sat, Nov 4, 2017 at 5:16 PM, David Watkins<EMAIL_ADDRESS>wrote:

The classes you mention are generated during the build
https://github.com/khartec/waltz/blob/master/docs/build.md process.
They are the output from the Immutables https://immutables.github.io/
library and from jOOQ https://www.jooq.org/
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/khartec/waltz/issues/2782#issuecomment-341890650, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AfyzAxLyTh3-5DFY26wJAWsyPxGcTuzHks5szE6tgaJpZM4QQnu2
.

The build process ensures the database has the correct version of the schema - it uses liquibase to apply the DDL.

Hello David Watkins,
Really thank you for the guidance.
I was able to setup the project.
but while doing changes, the changes are not reflected.
when i did the changes and try to run waltz-ng project's "dev-server.sh"
file. the old data are reflected.
please suggest how to check the changes.
Regards,
Rajesh Gupta
On Mon, Nov 6, 2017 at 12:28 PM, David Watkins<EMAIL_ADDRESS>wrote:

The build process ensures the database has the correct version of the
schema - it uses liquibase to apply the DDL.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/khartec/waltz/issues/2782#issuecomment-342062165, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AfyzA_9_hwBccclLAOi7p8crJGRhhGj6ks5szq4PgaJpZM4QQnu2
.

Could you raise a more specific issue detailing what you are trying to achieve and what issues you are encountering ? Thanks.


Replace deprecated kube controller-manager port

Description

Replace deprecated kube controller manager port. Used the wrong port in https://github.com/gravitational/gravity/pull/2562.
Type of change

Internal change (not necessarily a bug fix or a new feature)

Linked tickets and PRs

Requires https://github.com/gravitational/planet/pull/854

TODOs

[ ] Self-review the change
[ ] Perform manual testing
[ ] Address review feedback

Testing done

Looks like @a-palchikov addressed this in https://github.com/gravitational/gravity/pull/2568


Attribute value missing warning in Blazor Server template

In _Host.cshtml:
<a href class="reload">Reload</a>

Which results in an "Attribute value missing" warning for new Blazor Server projects.

Dup of https://github.com/aspnet/AspNetCore-ManualTests/issues/39. This is being fixed by https://github.com/aspnet/AspNetCore/pull/16719


Upgrade Kubernetes to version 1.26.2

This PR upgrades Kubernetes dependencies to v1.26.2.
This also upgrades Go to version 1.19, as it's required by Kubernetes v1.26.
Fixes #524.

@astefanutti we need to upgrade the kind images to match the k8s version. The version to use would be:
kindest/node:v1.25.11@sha256:227fa11ce74ea76a0474eeefb84cb75d8dad1b08638371ecf0e86259b35be0c8

The configuration file is in: hack/e2e-kind-config.yaml.
It is LGTM otherwise.

Thanks @astefanutti , will this upgrade break InstaScale integration?

Thanks @astefanutti , will this upgrade break InstaScale integration?

@asm582 I don't think so as this PR does not touch the AppWrapper API.

/hold
There is a CodeFlare release going on. This PR should be merged once the release is done.

/LGTM

/unhold


Bug: Chrome Extension: Unable to copy transcribed text to clipboard in active tab

" navigator.clipboard.writeTextToCursor is not a function "
Happens whenever i end a transcript. i get the content in the small text output window but automatic pasting isnt working.
Chrome
Version 127.0.6533.89

Pushing a hotfix asap. This bug was addressed in a previous commit but somehow wasn't merged. Sorry for the inconvenience!


Parliament should monitor queues and drops

Basically what it tells in the title, it would be cool if parliament would alert if queues or/and drops get too big on capture nodes.
Could be that it is already monitored, in that case would like to be able to set thresholds :)

We already have packet drops.


Array keypaths

It'd be nice to skip the string.split('.') and just allow array keypaths:
put(obj, ['user', 'name'], 'tjmenha')

What do you think?

All the keypath stuff is powered by keypather. It would be fine adding the functionality there, but adding this functionality in 101 complicates partial method arg checking..
Will have to think about this. I've seen this request before w/ keypather, but I always thought it was trivial to just use join('.').. put(obj, ['user', 'name'].join('.'), 'tjmehta')


Taggin new release

Hi, do you plan to tag a release anytime soon? There are plenty of changes after Jul 4. Can we consider that they are stable enough for tagging?

Yes tagged

Thanks!


" Sânmartin" are villages in " Macea" common, "ARAD" county

Precondition
Empty the search bar after every step

Steps 1
Acces to the link https://peviitor-ro.github.io/ui.orase/
Expected result
The page opens

Steps 2
Write "Sânmartin"
Expected result
In the drop down menu you find "Sânmartin, ARAD( Macea)"
Test Data
Sânmartin


Add support for besselroots(::BigFloat, ::Int)

I assume this is easy via Newton iteration with besselroots(::Float64, ::Int) initial guesses? Can add a PR
@marcofasondini

Is this issue still active? The function besselroots was renamed to approx_besselroots in https://github.com/JuliaApproximation/FastGaussQuadrature.jl/pull/96.


Contribution: Redo icon

Is your feature request related to a problem? Please describe.
The usage of "restart" icon seems a little bit inappropriate for a text toolbar.
Describe the solution you'd like
I have designed this icon for a new component, Text toolbar #361
It can be used to erase the text you have just typed.
All files here: https://ibm.box.com/s/z6ebqcilwvi40dahzyihmhcpvwing2rl
Screenshot details:

Hi @m-battelli! 👋 Thanks so much for taking the time to make this issue 😄
We do currently have an icon that could satisfy this use case here: https://carbon-elements.netlify.com/icons/examples/preview/#32%2Frestart, is that matching what you're looking for?
cc @chrisconnors-ibm

closed by #373


Npm audit report

5 vulnerabilities showed up when I ran npm audit. This was the report
npm audit report
cookie  <0.7.0
cookie accepts cookie name, path, and domain with out of bounds characters - https://github.com/advisories/GHSA-pxg6-pf52-xh8x
fix available via npm audit fix --force
Will install<EMAIL_ADDRESS>which is a breaking change
node_modules/engine.io/node_modules/cookie
node_modules/next-auth/node_modules/cookie
engine.io  1.8.0 - 6.6.1
Depends on vulnerable versions of cookie
node_modules/engine.io
socket.io  1.6.0 - 4.7.5
Depends on vulnerable versions of engine.io
node_modules/socket.io
react-email  1.10.1-canary.0 - 1.10.1-canary.18 || >=1.10.2-canary.0
Depends on vulnerable versions of socket.io
node_modules/react-email
next-auth  <=0.0.0-pr.11562.ed0fce23 || 4.0.0-beta.1 - 4.0.0-beta.7 || 4.0.1 - 4.24.8
Depends on vulnerable versions of cookie
node_modules/next-auth
5 low severity vulnerabilities

Waiting for next-auth (which we can override to bump up cookie) and react-email (engine.io + socket.io + cookie) to update their libs.

We'll check if we can override react-email as well in the meantime.


Factor large 1D dispatches into 2D and 3D

Description of the related problem
Old AMD and mobile GPUs love to make our lives difficulr by limiting the dispatch shape with constraint that the number of workgroups in the X-axis be <=64k.
Solution proposal
A new utility function in nbl::core that can split a T (either uint32_t or uint64_t) into 3 factors which when multiplied are either greater than or equal to the input.
For example a 64M input would be factored into (64k,1024,1).
The approximate 3-factor algorithm would have to do the following:

produce 3 natural (integer greater than 0) numbers less than or equal to the Maximum
start at each number equal to ceil(pow(input_size,1.f/3.f))
explore each candidate triple in the surface wdh = input_size (iterate in 2D over w,h in the range [1,MAX])

Furthermore all compute extensions and samples (included but not limited to FFT, Scan, RadixSort) will have to be adjusted to this (wg_count in the computed dispatch parameters and the use of gl_GlobalInvocationIndex,gl_WorkgroupID, etc.).
Additional context
https://github.com/Devsh-Graphics-Programming/Nabla/pull/75#discussion_r608113556

@Przemog1 do this on the new API

Not needed anymore.
Its less trouble and hassle to run 1D dispatches as persistent workgroups.


Document conditional updates for PATCH operations

This is a Feature Request

What would you like to be added
As mentioned in https://github.com/kubernetes/website/pull/31261#discussion_r942896591 (by @apelisse)

You can have conditions in your json-patch to validate some things are consistent when the patch is applied (or applying will fail with a 40x bad request)
You can also enforce a specific resource version in the patch, which will give you the PUT guarantees without having to send the entire object.

Why is this needed
Conditional patch operations are useful to avoid lost updates. Readers have an interest in knowing:

that these are possible
how to do it

Comments
/wg api-expression
/language en
/kind feature

I'd like to see if we can get this triaged.
/reopen
/remove-lifecycle rotten

I imagine that we add these details into https://kubernetes.io/docs/reference/using-api/ - probably, a new page within that section.
We already have a page about server-side apply. We could also have a page about client-driven updates.

deleting objects, probably outside the reference section

Yes, we could have with that: specify uid to make sure you delete the right resource, and the risk of running things like "create or update"

— @apelisse in a message on Slack

/triage accepted


Newsletters: add 286 (2024-01-24)

Lede, releases/RCs, topic entries @harding
PR summaries @harding
Client/Services @bitschmidty

Should this perhaps inlcude the btcd disclosure? Since it's a consensus bug I think it should be included in the earliest possible newsletter.

Should this perhaps inlcude the btcd disclosure? Since it's a consensus bug I think it should be included in the earliest possible newsletter.

Good idea, I added a section to the top of the newsletter (our usual policy is that significant security disclosure go first).

Made edits for all feedback (thanks @vostrnad @jirijakes @murchandamus @bitschmidty @LarryRuane !), reviewed @bitschmidty's section (thanks!), added remaining content, and added topic entries.  Thanks everyone!


Scene Editor, rename node, selecting next/prev node, requires arrow key twice

Godot version
v3.4.1.stable.official [aa1b95889]
System information
Windows 10 21H1
Issue description
In the Scene Editor,
after renaming a node, by pressing Space
and confirming enter or canceling esc.
Now, an arrow key has to be pressed twice, to select the node above or below.
Steps to reproduce
In a new project or scene.

Add two nodes, for example:

Node2D
  Node2D

select the bottom node
press space to make the name editable
press enter to confirm (or esc to cancel)
press arrow up

Observed
Nothing happens.

press arrow up again

Now the top node become selected.
Expected
The top node should have been selected after the first arrow up press.
It works as expected with these renaming methods
Only one arrow key press is required, to select the node above or below.
After renaming a node with:

F2
Enter
Mouse left clicking on the selected node

It does also work as expected when renaming with:

ctrl space
alt space

But shift space causes the same issue as space without a modifier.
Project Settings > Input Map
The same issue is also observed in:
Project > Project Settings
on the tab: Input Map
when renaming a user created action.
Reproduction steps

open: Project > Project Settings
select the tab: Input Map
in the Action input box at the top,
type a new action name: jump
press enter to add the new action
left click to select the new action (at the bottom of the list),
this makes the action name editable
press enter to confirm
press space to make the action name editable
press arrow up

Observed
Nothing happens

press arrow up again

Now the defined key for the action above, becomes selected.
Expected
The selection should move up, on the first arrow key press.
Notes
The selection moves up on the first key press,
when renaming a user action with:

enter
left mouse clicking

f2 doesn't do anything when a input map action is selected.
It's also mentioned in this comment: https://github.com/godotengine/godot/issues/33206#issuecomment-548620945
A proposal to add f2 has been opened:
Add F2 to rename a user action in the Input Map https://github.com/godotengine/godot-proposals/issues/3700
Minimal reproduction project
No response

Confirmed.
It affects the Tree node itself (not only SceneTree) and happens with master branch too.


Training Time

Hi, do you only include 'main_training part' in the '30 hours' here?
Please ask the total number of frames in your training data set, as well as your total number of training iterations is 125000 and batch_size is 16? (followed your train_config.yaml)

It is for the entire training process.
I don't have the total number of training frames off the top of my head, but you can just count from the training dataset.
The default configuration in the code is correct.

Thanks!
I currently face a problem:  the training time is too long when I run train.py on our custom dataset (two 3090 GPUs).
My custom dataset: 19544 frames in total, and I set the 'iteration=125000', and 'batch_size=14'.
The following figures are my training record and GPU. Is this reasonable?

The first printed "time" is not reliable as it includes warm-up and initialization.
In general, we want a high GPU utilization (see https://github.com/hkchengrex/Cutie/issues/58#issuecomment-2053740579) -- your GPUs are sitting at 18C and 29C so I don't think they are working hard enough unless you have really good cooling. This usually indicates a bottleneck in CPU/disk IO.

At the later 'time', the 'avg_time' is still 12-13.

Your CPUs and GPUs are not being used as much as they should be. Potentially related: https://github.com/pytorch/pytorch/issues/99625

Please feel free to re-open if there are any updates.


Apache htaccess file upload

Is your feature request related to a problem? Please describe.
Currently addon supports the JSP, Html based Scan Rules, so now we need to add the Apache htaccess file upload based scan rule. This Feature/Enhancement is for that.
Definition of Done
Definition of Done for this scan rule is 1. Adding various scan rules for Apache htaccess file upload. Along with that adding a VulnerableApplication which supports the https://github.com/SasanLabs/VulnerableApp-facade so that we can do TDD type of implementation where Vulnerable applications are written first and then Scan rules are written over them.

https://github.com/SasanLabs/owasp-zap-fileupload-addon/pull/10 closes this one.

https://github.com/SasanLabs/owasp-zap-fileupload-addon/releases/tag/1.1.0


Is there some kind of portable without --standalone that uses existing Python installation

currently, if no --standalone is used, the created EXE file reads python libraries from the lib sub-directory where python.exe is located.
In other word

if I rename c:\python36 to c:\python3, then the EXE fails to run
if I installed python 3.6 on other PC but under d:\python, then the EXE fails to run
and also it seems that it is not necessary to copy python36.dll to the directory where the created EXE file lives since it should be the parent directory where the EXE try to find python libraries

is it possible to add an options --find-pythondll for nuitka, then
nuikta --find-pythondll=.. main.py
creates main.exe which will try to load python36.dll from the parent directory, and find python libraries from ..\lib.
so I can put it under a sub-directory of python.exe
thanks

Yes, I have found the following in the document
but my advice is for user not for coder
Dynamic sys.path

If your script modifies sys.path to e.g. insert directories with source code relative to it, Nuitka will currently not be able to see those. However, if you set the PYTHONPATH to the resulting value, you will be able to compile it.

Your best way of distribution to use in an existing Python installation is to make an extension module, which will be portable to that specific Python version used to compile, and then a batch file to do the scanning, and a minimal executable that loads the DLL from there.
In fact, I bet this could be done relatively easily, with the new Windows bootstrap even as a single file to the user. But I would do it only if paid for, as it's work and not needed really. I estimate this would be take 4 days to create. Until such time this will remain unimplemented.
Yours,
Kay

Your best way of distribution to use in an existing Python installation is to make an extension module, which will be portable to that specific Python version used to compile, and then a batch file to do the scanning, and a minimal executable that loads the DLL from there.
In fact, I bet this could be done relatively easily, with the new Windows bootstrap even as a single file to the user. But I would do it only if paid for, as it's work and not needed really. I estimate this would be take 4 days to create. Until such time this will remain unimplemented.
Yours,
Kay


Add support for user provided context in handlers

Add support for user provided context in handlers. With this change handlers can depend on user provided values in the context. Related issues: #818, #586, #550 and #708
Example:
Create a context key with a default value:
export interface User {
  id: string;
}
import { createContextKey } from "@connectrpc/connect";
export const kUser = createContextKey<User | undefined>(
  undefined // The default value.
);

Use the contextValues option to provide the context values for each request:
import { fastify } from "fastify";
import routes from "./connect";
import { fastifyConnectPlugin } from "@connectrpc/connect-fastify";
import { authenticate } from "./authenticate.js";
import { kUser } from "./user-ctx.js";

const server = fastify();

await server.register(fastifyConnectPlugin, {
 routes,
 contextValues: (req) => createContextValues().set(kUser, authenticate(req)),
});

await server.listen({
  host: "localhost",
  port: 8080,
});

Use the context value in the handler:
import { ConnectRouter } from "@connectrpc/connect";
import { ElizaService } from "./gen/eliza_connect";

export default (router: ConnectRouter) => {
  // using const say
  router.service(ElizaService, {
    say: (req, { values }) => {
      const currentUser = values.get(kUser);
      if (currentUser === undefined) {
        throw new ConnectError("Unauthenticated", Code.Unauthenticated);
      }
      // ...
    },
  });
};

I love the way this keeps the type information associated to the context id, very cool. One question I have is if we want to expose the context values to interceptors as well?

I love the way this keeps the type information associated to the context id, very cool. One question I have is if we want to expose the context values to interceptors as well?

We don't have server side interceptors yet, but if we finalize this API I will send a follow up to add this to the clients. The server side interceptors should include them when implemented.

This may be a contrived example, but what if the user wants to add something to context that doesn't involve the request object? I suppose they could do:
await server.register(fastifyConnectPlugin, {
 routes,
 contextValues: () => createContextValues().set(kUser, {"name": "Krishna"}),
});

Does it make sense then to make the req optional in the contextValues function property?

@smaye81 Your example will work without any changes, req is something we pass to the function and can be omitted if they don't need it.

Would it be helpful to consider a solution that introduces typesafe constraints between the route handlers and the context builder?
Here is a rough example of the types I'm talking about:
// context now has typesafety
type Context<V={}> = { values: V };

// example of how a route handler can assert that it needs some data out of context
type RouterHandler<I, O, V={}> =  (input: I, context?: Context<V>) => O;

// then we can force the injection of some data in context
class Server<C extends Context> {
  addContextValue<K extends LiteralString, T>(lambda: (req: Request) => T): Server<Context<C["values"] & { K: T}>>;
}

Thank you for the suggestion @jeffsu!
Could you give us a simple e2e example of how this will work? I am unable to see how this can guarantee the presence of a value. In the current design, users have to pass a default value.
One other thing to note is that we want to add context values to interceptors on both the client and server side (not implemented yet). Values can be added via the interceptors as well which means the values are not always available at the request start.

Hey @jeffsu to illustrate what I meant by adding them to interceptors I just opened #841 please take a look and let me know what you think.
One thing I noticed with the current implementation is that ContextValues is mutable. Should we make it immutable?
Current behavior:
const interceptor = (next) => {
     return (req) => {
          const user = req.values(kUser);
          const res = next(req); // This can modify req.values
          // req.values(kUser) !== user
     }
}

cc @timostamm @paul-sachs @smaye81

This level of mutability doesn't really bother me. If we made a version of context that could be deep cloned, you could do something like:
const interceptor = (next) => {
     return (req) => {
          const user = req.values(kUser);
          const res = next({ ...req, values: req.values.clone() }); // This can modify req.values
          // req.values(kUser) === user
     }
}

Is there an example of how to use this new system to get the logger inside the connect service?
E.g
fastify.get('/', options, function (request, reply) {
  request.log.info('Some info about the current request')
  reply.send({ hello: 'world' })
})

router.service(Health, {
  check(request, context) {
    // log here
    console.log(context)
  }
}

Is there an example of how to use this new system to get the logger inside the connect service?

It is the same as the example in the PR description, instead of
contextValues: (req) => createContextValues().set(kUser, authenticate(req)),
you can just use a different key for the log type:
 contextValues: (req) => createContextValues().set(kLog, req.log),
And then can get the value and use it:
router.service(Health, {
  check(request, context) {
    context.values.get(kLog).log.info(...);
    console.log(context)
  }
}

Why was the implementation shipped this way? We have no async support and we can't pass a global type for contextValues. Our use case is to check authentication in this handler. Do you accept a PR?

@StarpTech Typically if you're using something like Fastify/Express you will have an auth library that does the authentication checks and adds the subject info to the incoming request, and you can add the that to the context.

we can't pass a global type for contextValues.

This is actually error prone and could have conflicts. Using a unique key lookup helps us guarantee type safety and always provide a default value.

I see your points but why should we limit the implementation to only synchronous work? I don't see the value in it.

This is actually error prone and could have conflicts. Using a unique key lookup helps us guarantee type safety and always provide a default value.

I'm quite on the opposite side. We have to specify a shared ContextKey Type and use the right type everywhere we access it instead of maintaining the relation once
This would be more conenvient
(router: ConnectRouter) => {
    router.service<MyContextValuesType>(MyService, MyServiceServiceImpl(opts), handlerOptions);
  };

Access
 ctx.values.get(Symbol('foo)) // return the correct type

Another thing we find odd is, why is it necessary to specify the the default value when retrieving a value?
// Error: Property defaultValue is missing in type { id: symbol; } but required in type ContextKey<unknown>
ctx.values.get({
  id: Symbol('subgraph'),
});

Access
 ctx.values.get(Symbol('foo')) // return the correct type, typesafe access out of the box

This is how it can be used today, instead of creating a Symbol the key is nothing but a type-safe proxy to a static symbol.

Another thing we find odd is, why is it necessary to specify the the default value when retrieving a value? If the value can be undefined, it is the dev responsibility to deal with it.

Default is not needed when retrieving a value, it is only needed when creating the key. If undefined is needed, then the type can be set to do that: T | undefined.
We just updated the docs with an example. Hopefully that helps clarify the usage a little bit. This is fairly a common pattern in the JS ecosystem, a popular mechanic that works like this is the React Context.

This is how it can be used today, instead of creating a Symbol the key is nothing but a type-safe proxy to a static symbol.

Was the API updated? This is not possible in 1.1.3.

Default is not needed when retrieving a value,

This doesn't work for me.
Property defaultValue is missing in type { id: symbol; } but required in type ContextKey<string | undefined>
 ctx.values.get<string | undefined>({
        id: Symbol('test'),
      });

We just updated the docs with an example.

There you made an example to authenticate within contextValues. Based on your previous suggestions, I think this should be removed.

The API is the same, you have to create a unique key using createContextKey and use that. Symbol constructor creates a unique symbol and cannot be used like this:
console.log(Symbol('foo') === Symbol('foo'));
// Expected output: false

Ah, ok createContextKey is just a utility function. I think I know now where my confusion comes from. The API is just not very common in the Node.js space. Thanks again.


export circular progress props

Description
Export circular progress props
Verification

[ ] Your code builds clean without any errors or warnings
[ ] Manual testing done (required)
[ ] Relevant automated test added (if you find this hard, leave it and we'll help out)
[ ] All tests run green

Documentation

[ ] User documentation is updated with a separate linked PR in altinn-studio-docs. (if applicable)

Codecov Report
Patch and project coverage have no change.

Comparison is base (839a3dd) 95.51% compared to head (729f2a5) 95.51%.
Report is 9 commits behind head on main.

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #333   +/-   ##
=======================================
  Coverage   95.51%   95.51%
=======================================
  Files          29       29
  Lines         357      357
  Branches       95       95
=======================================
  Hits          341      341
  Misses         14       14
  Partials        2        2

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Mitsubishi Electric AC MSZ-HJ25VA

MSZ-HJ25VA.zip
Attached you will find the json for MSZ-HJ25VA
this is my first contribution, hope it will be usefull.

Thanks!


[FEATURE] Datasource ID should be able to be configured inside config.ex/dev.ex/ etc.

Is your feature request related to a problem? Please describe.
I have a problem where we have different prometheus datasource names, so I need to be able to change the datasource_id in dashboard_assings depending on my env.
I can always create a new config env variable and write code inside dashboard_assigns/0 call but it would be nice if prom_ex handles this.
Describe the solution you would like to see
It would be nice if we can have the following
releases.exs

config :app_node, AppNode.PromEx,
  grafana: [
    host: System.fetch_env!("GRAFANA_URL"),
    auth_token: System.fetch_env!("GRAFANA_TOKEN")
  ],
  datasource_id: System.fetch_env!("PROMETHEUS_DATASOURCE")

Would know if datasource_id should be outside or inside grafana Keyword list.

Thanks for opening up the issue! The funny thing is that this is how I had this configured when PromEx was in Alpha. The reason that I decided to switch it to the way that it is now is that it is more explicit as to what is going on now (the datasource id is passed as an assign to the dashboard template). In addition, given that the dashboard_assigns/0 function is is completely under your control, you can store this value in a config and read it yourself and pass it via the keyword list. Lastly, I want to keep the amount of application configuration to a minimum so that the library is easier to use and follows Elixir best practices (https://hexdocs.pm/elixir/master/library-guidelines.html#avoid-application-configuration).
Hopefully that all makes sense, and you can see where I am coming from on this one :). Let me know if you have any other questions, or feel free to close the issue.

Hey, makes total sense. Thanks for taking your time.


Create user service

A micro-service in the core/services directory that will facilitate user related workflows through http endpoints. Example workflows include:

Mobile number OTP and email login
SSO related workflows for login: google, facebook, whatsapp
receive roles based on which permissible actions across the system can be determined
get relevant user information, including settings, role

Covered in stories under epic-1 #62


Please delete this repository immediately

Why?

Why doesn't anybody open useful and insightful issues like these on my repositories?

👆true story, bro! High five!
пт, 6 апр. 2018 г. в 8:45, Patrick Meade<EMAIL_ADDRESS>
Why doesn't anybody open useful and insightful issues like these on my
repositories?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/NodeOS/NodeOS/issues/402#issuecomment-379154574, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AC3NvxwNfcb3092URQ6Aksa84sgKpbkPks5tlwD-gaJpZM4TJbUh
.

I admit first time I found something similar to this I got it really personal, but now I'm taking a more Zen-like mindset: ignore it, don't feed the troll, and report abuse to Github administrators to take the correct action and close its account :-) That's funny to be sometimes a BOFH... :smiling_imp:


Soften the experimental warning for the repo in the 3.0 release

Description
Make the experimental warning softer and allow for some use in production (at users own risk).
Definition of Done

[ ] Users should be able to use the documentation to complete a task

Contributions
Do you plan to raise a PR to address this issue? YES
See the contributing guide for more information about what's expected for contributions.

Is there an estimate/guesstimate as to when the provider will be GA?


Update README.ZH_CN.md

fix spell

[] Do only one thing
[] Non breaking API changes
[] Tested

What did this pull request do?

User Case Description

顺手把README.md也改了吧？


What to do with Terminal?

Summary
Hmmmmmm. The Terminal team has announced some significant changes to Terminal that I need to take some time to understand.  I need to perform a few small experiments and then think about the best path forward for my current packages.
 On top of that, there are now two kits and differences between Windows 11 and 10 Terminal installations. Previously there was a single kit and it just came with the msixbundle.
Recently I have made lots of changes to make these packages Windows 11 first, but that does not mean ripping support for Windows 10. Some of these packages are literally only built to be used on Windows 10.
What I am thinking...
I have much more thinking to do, but so far I am considering a few options listed from most likely to least likely

Use the Windows 10/11 bundle for all packages, and then Windows 11 installations will just have to convert the W11 version automatically during the user step with store update. (One bundle to rule them all)
Use the Windows 10 bundle in the Windows 10/11 general packages, and then move certain packages to exclusively Windows 11 and use the Windows 11 bundle for those. (Two bundles)
Move all packages to Windows 11 exclusively. (This really isn't even an option atm, just brainstorming.)

Experiments & Questions
Here are some experiments & questions I have to explore.

[ ] What are the differences between Win10 and Win11 kits?

[ ] Different msixbundle?
[ ] Different dependencies?

[ ] What are all these dependencies?

[ ] What dependencies did Terminal 1.11 have?
[ ] What dependencies are needed for Windows 10, Windows 11?
[ ] What dependencies does the store install?

[ ] What is the difference between installing Win10 kit and Win11 kit on Windows 11?

[ ] How acceptable is it to install Win10 kit on W11?

[ ] How does the Win10 Terminal version get upgraded to the Win11 Terminal?

I would now consider removing Terminal altogether from this package. W11 comes with Windows Terminal. Every major release of W11 further integrates Terminal. W11 22H2 should come with Terminal as the default terminal.


fix: update default path for git submodule

PR Checklist

[x] Added label to the Pull Request for easier discoverability and search
[x] Commit Message meets guidelines as indicated in the URL https://github.com/intel-retail/performance-tools/blob/main/CONTRIBUTING.md
[x] Every commit is a single defect fix and does not mix feature addition or changes
[ ] Unit Tests have been added for new changes
[ ] Updated Documentation as relevant to the changes
[ ] All commented code has been removed
[ ] If you've added a dependency, you've ensured license is compatible with repository license and clearly outlined the added dependency.
[ ] PR change contains code related to security
[ ] PR introduces changes that breaks compatibility with other modules (If YES, please provide details below)

What are you changing?

Issue this PR will close
close: #issue_number
Anything the reviewer should know when reviewing this PR?
Test Instructions if applicable

set up performance tools submodule
ensure benchmark container is built using 'make build-benchmark-docker' from performance tools
run the followingcd benchmark-scripts
python benchmark.py --compose_file ../../use-cases/gst_capi/add_camera-simulator.yml --compose_file ../../use-cases/gst_capi/add_gst_capi_yolov5_ensemble.yml

If the there are associated PRs in other repositories, please link them here (i.e. intel-retail/performance-tools )

I needed to change the path from your instructions to: ../../retail-use-cases/use-cases/gst_capi/add_camera-simulator.yml
is this supposed to be the correct path for the compose-files?

For this - you need to set up performance-tools as a submodule of retail-use-cases. In the retail-use-cases root, run make update-submodules to set up the submodule. Then for me, I edited the git config for the submodule which should be in retail-use-cases/.git/modules/performance-tools/config so that you have your remotes set up properly.
Then the path should be correct.

I needed to change the path from your instructions to: ../../retail-use-cases/use-cases/gst_capi/add_camera-simulator.yml
is this supposed to be the correct path for the compose-files?

For this - you need to set up performance-tools as a submodule of retail-use-cases. In the retail-use-cases root, run make update-submodules to set up the submodule. Then for me, I edited the git config for the submodule which should be in retail-use-cases/.git/modules/performance-tools/config so that you have your remotes set up properly.
Then the path should be correct.

Okay makes sense, I had performance-tools as its own repo.


Add PropertyString pointer to some LiteralStrings

There are some types of strings which we convert into LiteralString (e.g. ConcatStrings). However, they generally have a number of fields so there is extra space that is unused after conversion. This change utilizes that space with a PropertyString pointer (which we populate if you use the string as an index for a StElem).
This is about a 2% improvement in Speedometer.

:shipit:


chore(release): 29.1.1

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.04%) to 95.991%

Totals

Change from base Build<PHONE_NUMBER>:
0.04%

Covered Lines:
4055

Relevant Lines:
4154

💛  - Coveralls

ping @kulshekhar


Google Geocoder ignoring postal_code component when country is not null

Found an issue in the GoogleGeocoder when the country is null.
https://github.com/nchaulet/node-geocoder/blob/master/lib/geocoder/googlegeocoder.js#L43
Components is initialised as a null, so if the country is not provided the end result of the components section looks like:
components=nullpostal_code:{postalCode}
This is causing Google to ignore the postal code and returning inaccurate results.
This is fixed by initialising the components as an empty string.
Please let me know if you agree with the change and I'll submit a PR.
Thanks,
leo

Fixed in v3.21.1 Thanks for the PR.


✨ Add manifest linting script

What this PR does / why we need it:
Add a script for validation of the k8s core objects within the repo. This is the first step to have a mandatory CI job on every future pull request. The second step will be to configure the prow to run the script.
There are some files such as kustomization patches - for which we need to skip the validation because their deployment definitions are not complete. As such, kubeval will through an error for them. However, we can give a pattern of the files in the same directory that need to be skipped from the check. That's why we add the word patch in all the kustomization patches so that we can filter them out with a single pattern, which in this case is patch.

/assign @maelk
/cc @kashifest
/cc @furkatgofurov7

/test-integration

Looks good to me. Are you planning to add this to the Makefile target, in this repo as well?

Yes, added.
/test-integration

/lgtm


MINOR: Add compatibility tests for 2.3.0

So I'm trying to upload the https://s3-us-west-2.amazonaws.com/kafka-packages/kafka_2.12-2.3.0.tgz file for the 2.3.0 release that we just created
I successfully uploaded it to s3, but now I can't access it through the web URL? (edited)
<?xml version="1.0" encoding="UTF-8"?>
<Error>AccessDenied<Message>Access Denied</Message><RequestId>02E376BABEAD7065</RequestId><HostId>Lz7fKeOhKYcr7ylU85bzBN7OGB/Fr7+Uelb3v2Qfej8Szt3lW7EpvAo4BOt0JoPNsaeUOap39/c=</HostId></Error>[cmccabe@zeratul t]$```

Is there something else I have to do to make this visible?


Replace Gatsby with Nextjs

As proposed in https://github.com/cdk-dev/base/pull/7 this replaces Gatsby with Nextjs and fixes the sticky footer issue.

No issue here.  I don’t see the discussion in #7 though.  That’s about mindmaps.

No issue here. I don’t see the discussion in #7 though. That’s about mindmaps.

Yeah, the discussions are about mindmaps, the actual PR is about changing this. See diff
I wanted to demonstrate, that it's not a huge change in terms of code. But it'll enable more dynamic use-cases in a straightforward way.

I have little experience with either Gatsby or Next but I've had success with one and pain with the other, so I'm a little defensive to moving to Next.
What are some of the use-cases it'll be better at? We had talk about building something similar to Gatsby recipes. Would it be useful to keep this project around as a sandbox/dog-fooding Gatsby Recipes and know what to mimic in our CDK recipes?

I have little experience with either Gatsby or Next but I've had success with one and pain with the other, so I'm a little defensive to moving to Next.

Which pain points did you have with Next?

What are some of the use-cases it'll be better at?

I think as soon as we get some concept of a user involved, something like Next with SSR will be dramatically easier (for recipes, notes and similar things) . From my understanding, Nextjs is pretty much capable of doing what Gatsby can in terms of static content, is less configuration, doesn't force a GraphQL schema on everything and can do dynamic SSR on top of that. As you can see in the Pull Request diff, the transition is pretty straight forward for the static part.
I think what's mostly missing are the starter templates and plugins. However, I don't think we'd use many plugins anyway since we're not really going down the "low code" route here.

We had talk about building something similar to Gatsby recipes. Would it be useful to keep this project around as a sandbox/dog-fooding Gatsby Recipes and know what to mimic in our CDK recipes?

Not sure what you mean by that, could you elaborate?

I have little experience with either Gatsby or Next but I've had success with one and pain with the other, so I'm a little defensive to moving to Next.

Which pain points did you have with Next?

Mostly that getting things setup and built required multiple steps. However, upon review it seems like that isn't an issue here so I'm guessing it was just the way the previous developer had setup that project.

What are some of the use-cases it'll be better at?

I think as soon as we get some concept of a user involved, something like Next with SSR will be dramatically easier (for recipes, notes and similar things) . From my understanding, Nextjs is pretty much capable of doing what Gatsby can in terms of static content, is less configuration, doesn't force a GraphQL schema on everything and can do dynamic SSR on top of that. As you can see in the Pull Request diff, the transition is pretty straight forward for the static part.
I think what's mostly missing are the starter templates and plugins. However, I don't think we'd use many plugins anyway since we're not really going down the "low code" route here.

:+1:

We had talk about building something similar to Gatsby recipes. Would it be useful to keep this project around as a sandbox/dog-fooding Gatsby Recipes and know what to mimic in our CDK recipes?

Not sure what you mean by that, could you elaborate?

We had talked about doing Gatsby-like recipes for the CDK. I'm not too familiar with Gatsby recipes so I thought it'd be good to use the website as a place to get familiar with how they work and learn what is good and bad to use with our CDK recipes.

We had talked about doing Gatsby-like recipes for the CDK. I'm not too familiar with Gatsby recipes so I thought it'd be good to use the website as a place to get familiar with how they work and learn what is good and bad to use with our CDK recipes.

I think it's fairly easy to play with Gatsby Recipes on its own and therefore shouldn't be factored as pro / con for this PR.

Are there other concerns? If not, I'd work in the recent changes from master in this PR and then we'll get it merged?

let's do it.

let's do it.

Ok - added the Discord link. Please have a look at the netlify preview and approve :)

while we're here can you generate a new link so we get a better name on the invite?

while we're here can you generate a new link so we get a better name on the invite?

👍


make site multilingual

title says it all, would be nice to be able to have interchangeable languages, english and greek for now (and potentially more if we feel like it :) )
also, a good thing would be to have a simple procedure for translating text. i dont know exactly how, but let's make it easy for translators.

I'll take it ;)


[Suggestion] Different particle

Hi (sorry for my english),
That's sould be great if we can put more than one particle and not necessary an image.
Example :
$('h1').clickSpark({
    particle: ['

', '', 'foo'],
    // other stuff
});

With this you can make differents scale of an image. Or you can put div whatever you want.
So you can make an AMAZING PARTICLES RAINBOW§§§

Hi hotgeart,
thx for your proposal :+1:
Particles are based on an canvas image obj. so I will only work with images or paths. The given particles are scalable by configuration, additionally they are scaled randomly in the code a bit. Also you can put the particle source wherever you want with
clickSpark.fireParticles($('.someDiv'));

If you want different colored particles, you can put them into one image file. But I will keep the idea to configure multiple images, thx for that :-)


Port InfluxQL docs into 2.x and Cloud

With InfluxQL support in both 2.x and Cloud, we need to port the Enterprise 1.9 InfluxQL documentation (the most recent InfluxQL docs) into 2.x and Cloud. Certain InfluxQL operations are not possible (such as administrative tasks) and we need to call those out.
Relevant URLs

https://docs.influxdata.com/enterprise_influxdb/v1.9/query_language
https://docs.influxdata.com/influxdb/v2.1/query-data/influxql/
https://docs.influxdata.com/influxdb/v2.1/reference/syntax/flux/flux-vs-influxql/

For now, InfluxQL is only supported in API. @sanderson @lwandzura and @kelseiv met today to discuss plan for porting InfluxQL doc 1.x content to 2.x and Cloud:

[ ] Create an InfluxQL branch and copy and paste the enterprise_influxdb/v1.9/query_language/ file into v2.0, v2.1, and Cloud.
[ ] Move the following docs to an InfluxQL section under Reference:
- Functions
- Mathematical operators
- InfluxQL reference (and rename to InfluxQL specification)
[ ] Drop Continuous queries doc (figure out where/if it makes sense to refer to "tasks" in the InfluxQL context)
[ ] Remove unsupported commands throughout (much of Manage your database using InfluxQL doc goes away--do we want to keep this doc now/retitle?)
[ ] Remove CQ content throughout and retention policies. Do we support create a database? how does this translate to bucket?
[ ] Remove cli examples.
[ ] Drop Sample data doc, and update other docs where appropriate to use 2.x/Cloud sample data, and create a DBRP mapping.
[ ] Reorganize and rewrite Explore data using InfluxQL to be more procedural and step-by-step instruction; verb phrase headers. Update intro and remove table format, update all examples to reflect API calls and new sample data. Break out into new docs if it makes sense to do so.
[ ] Remove (or identify) unsupported InfluxQL queries in 2.x/Cloud in context. Do we want to remove associated content altogether, or note that the content is "only supported in 1.x"?
[ ] Editorial sweeps.
[ ] Review keywords; test search.

ensure the following is added:
SHOW MEASUREMENTS grouping/filtering by RP


Added auto-updater

Description
This PR adds an updater to the addon so it can update from within the editor.
Tests are yet to be written for the new features.
Any feedback is appreciated
Addressed issues

Fixes #126

Screenshots
Update Button

Updater Window

Good job!


Extend the user-defined rules language

Depends on #11.
Features:

[ ] several patterns in conditions to match
[ ] combine objects, resolve naming conflicts
[ ] access attributes after renaming

Several patterns in conditions to match
Example:
TODO

Several patterns in conditions to match
Example:
TODO

Access attributes after renaming
Example:
TODO

Superseded by https://github.com/objectionary/normalizer/issues/51


sdrangel: 6.8.0 -> 6.16.2

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/f4exb/sdrangel/releases.
meta.description for sdrangel is: "Software defined radio (SDR) software"
meta.homepage for sdrangel is: "https://github.com/f4exb/sdrangel"
meta.changelog for sdrangel is: ""
Updates performed

Version update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS

The tests defined in passthru.tests, if any, passed

/nix/store/l7i71571rwfjvg7yrgnk4gld1brcgk3w-sdrangel-6.16.2/bin/sdrangelbench passed the binary check.

Warning: no invocation of /nix/store/l7i71571rwfjvg7yrgnk4gld1brcgk3w-sdrangel-6.16.2/bin/sdrangel had a zero exit code or showed the expected version

/nix/store/l7i71571rwfjvg7yrgnk4gld1brcgk3w-sdrangel-6.16.2/bin/sdrangelsrv passed the binary check.

/nix/store/l7i71571rwfjvg7yrgnk4gld1brcgk3w-sdrangel-6.16.2/bin/ldpctool passed the binary check.

/nix/store/l7i71571rwfjvg7yrgnk4gld1brcgk3w-sdrangel-6.16.2/bin/.sdrangelbench-wrapped passed the binary check.

Warning: no invocation of /nix/store/l7i71571rwfjvg7yrgnk4gld1brcgk3w-sdrangel-6.16.2/bin/.sdrangel-wrapped had a zero exit code or showed the expected version

/nix/store/l7i71571rwfjvg7yrgnk4gld1brcgk3w-sdrangel-6.16.2/bin/.sdrangelsrv-wrapped passed the binary check.

/nix/store/l7i71571rwfjvg7yrgnk4gld1brcgk3w-sdrangel-6.16.2/bin/.ldpctool-wrapped passed the binary check.

6 of 8 passed binary check by having a zero exit code.

6 of 8 passed binary check by having the new version present in output.

found 6.16.2 with grep in /nix/store/l7i71571rwfjvg7yrgnk4gld1brcgk3w-sdrangel-6.16.2

found 6.16.2 in filename of file in /nix/store/l7i71571rwfjvg7yrgnk4gld1brcgk3w-sdrangel-6.16.2

directory tree listing: https://gist.github.com/4624d2d95f9398c0c74838d638a91080

du listing: https://gist.github.com/b77cdecc63ecb55dba60afedead73b5e

Rebuild report (if merged into master) (click to expand)

3 total rebuild path(s)

1 package rebuild(s)

1 x86_64-linux rebuild(s)
1 i686-linux rebuild(s)
0 x86_64-darwin rebuild(s)
1 aarch64-linux rebuild(s)

First fifty rebuilds by attrpath
sdrangel

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/l7i71571rwfjvg7yrgnk4gld1brcgk3w-sdrangel-6.16.2 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A sdrangel https://github.com/r-ryantm/nixpkgs/archive/b6d9b4bd22a3822910308cd18455de0cfcc26051.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/l7i71571rwfjvg7yrgnk4gld1brcgk3w-sdrangel-6.16.2
ls -la /nix/store/l7i71571rwfjvg7yrgnk4gld1brcgk3w-sdrangel-6.16.2/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

sdrangel

Maintainer pings
cc @Alkeryn for testing.

Result of nixpkgs-review pr 134558 run on x86_64-linux 1

1 package built:

sdrangel


Rerender recipe

Checklist

[x] Used a personal fork of the feedstock to propose changes
[x] Bumped the build number (if the version is unchanged) NA: first time rendering
[x] Reset the build number to 0 (if the version changed)
[x] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[x] Ensured the license file is being packaged.

@conda-forge-admin, please rerender

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.


validateRequest does not throw an error when stringified (JSON.stringify) version of the request body is provided

I was testing validateRequest() to see if it correctly throws an error in the following scenarios

if a property of the body parameter is set to null and the swagger spec says that it should be of type string.
if a property of the body parameter is of type integer and the user provides a string instead

Initially validateRequest output was { errors: [], warnings: [] }. I was amazed to see this. I was not expecting this.
Then I found that while constructing the request object, I was doing
this.body = JSON.stringify(options.body) , where options is the parameter to my request wrapper.
As soon as I removed that and passed the body as-is validateRequest worked as expected.
Hence, I think this is a bug.

Either validateRequest should somehow find out that the provided body is a stringified version and do  JSON.parse() and validate correctly.
OR it should do type validation. In most cases where the request body is usually an object, typeof check should fail and vlidateRequest should throw correct error. (This will absorb the error when body is of type string but it will do the correct thing for other scenarios, which will be better than what is happening today).

Can you provide the pertinent portion of your Swagger document (the parameter definition and any referenced definitions) and an example that reproduces the issue?

I'm closing this until you provide more information.


Case insensitivity of the import statement

The import statement allowed import of files without checking for cases in file names.
This branch should fix the issue (by aborting translation when the name of the import file is unequal to the file name of the imported module itself) and introduce an according test scenario.

@edding4500 the CI test fails on unix systems since there it (apparently) already has the desired semantics.
It is a bit fragile, but you could change the error message to 'Cannot find source for examples/pos/liStS" to match the behavior on unix.

Superseded by #158


[DO NOT MERGE] finatra: Fix Test Logging dependencies

DO NOT MERGE

 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.


TypeError: Not an Operation or Iterable: <class 'cirq.ops.global_phase_op.GlobalPhaseGate'> (-0.2272020946930871+0.9738476308781951j)

Greetings,
Hope all are well. I am trying to add a Global Phase Gate to the circuit definition, however I am receiving the error below.
TypeError: Not an Operation or Iterable: <class 'cirq.ops.global_phase_op.GlobalPhaseGate'> (-0.2272020946930871+0.9738476308781951j)

Here is my code :
# Create a Global Phase gate
phase = np.exp(1j*angle) # angle = 1.8 in this instance
global_phase = cirq.GlobalPhaseGate(phase)

# Apply the Global Phase gate to the circuit
circuit.append(global_phase)

Thanks in advance!

Shouldn't global phase not depend on a specific qubit? It's an attribute of the circuit, not specific qubits no?

Shouldn't global phase not depend on a specific qubit? It's an attribute of the circuit, not specific qubits no?

That is correct, sorry about misspeaking.  The circuit needs Operation-type objects and does not accept Gate instances.
For GlobalPhaseGate there are indeed no specific qubits as you correctly pointed out.
The gate thus needs to be called without arguments so it is expressed as an Operation.
Either of cirq.GlobalPhaseGate(phase)() or cirq.GlobalPhaseGate(phase).on() will do in your example.

No worries at all. Thank you so much for the help. Quick question, I am trying to write a tester for this, and was wondering how I can check the global phase of a circuit.

@pavoljuhas ?

... Quick question, I am trying to write a tester for this, and was wondering how I can check the global phase of a circuit.

Apologies about a delay in response.  cirq does not have tracking of global phase for circuits because the global phase can also change with gate operations - for example a gate sequence XZXZ is equivalent to a global phase shift by PI (multiplication by -1).  One option to check the effects of global phase is to evaluate the unitary matrix cirq.unitary(circuit) and verify the complex phase of its elements changes by equal amount as the global phase coefficient.  Hope this works.
BTW, w/r to the initial question, cirq has also a convenience function cirq.global_phase_operation(phase) to construct the phase operation without explicitly using the GlobalPhaseGate.

I see. So, how would I let's say check if the global phase gate of e^i1.8 is correctly applied to the circuit in a tester function?

@ACE07-Sev
np.testing.assert_allclose(cirq.unitary(circuit_with_global_phase), cirq.unitary(circuit_without_global_phase) * global_phase)

although I don't see why you need to test that. testing that global phase is applied is equivalent to testing cirq itself, I don't think your goal is that -unless you are contribution to cirq- instead you should be testing the logic of your method/class in which case that would be checking that your method constructs a circuit with a global phase object that has the correct phase e.g.
global_phase = cirq.global_phase_operation(desired_global_phase)
circuit = my_method()
assert any(op == global_phase for op in circuit.all_operations())

but if you expect that their might be multiple global phase operations in your circuit, then you can do
total_phase = 1
for op in circuit.all_operations():
  if isinstance(op.gate, cirq.GlobalPhaseGate):
     total_phase *= op.gate.coefficient
assert total_phase == pytest.approx(desired_global_phase)

Thank you so much!