fix wait-for-infrastructure-resource flag on CNO availablity prober

Need to set Command flags before container is copied to the pod spec

/lgtm


Rotation Issue

Hi Jonas
Found another issue.
I've got a "portrait-only" ViewController, which is called from a normal (portrait and landscape) ViewController. Now when I am in landscape mode and go to the portrait-only ViewController, the ProgressHUD is displayed quite wrong.. This issue also appears while changing orientation.
Thanks for your great code anyway. It's a very cool HUD :)

Any example code/project and screenshots would be useful.

No code needed. Just create a portrait-only mode and use your HUD. As soon the orientation changes while the HUD is in front, you'll see it.

Show me your code. If you want to help thats the least you can do. Or just fix it yourself open a pull request.

Hi Jonas
I found this issue too.
My code is almost same with this: http://swiftiostutorials.com/ios-orientations-landscape-orientation-one-view-controller/
The ProgressHUD is displayed quite wrong on the only one landscape  view controller.

I'm really busy right now and I don't have the time to look into this. Everyone is welcome to contribute, that's why this project is open source. You can fork the repo, fix any bugs you find and open a pull request.

I will close this ticket if it is no longer updated. If you want this to be fixed you have to show me some code instead of trying to vaguely explain your implementation.

You're free to reopen this and provide more information.


Training Code

Hello, when I run the program, an error occurred "AttributeError: Can 't pickle local object' SubPolicy. Just set the < locals >. < lambda > '", don't know if you Can help me to solve it? Thank you very much!

Sounds like an error from autoaugment.
A quick solution would be, to avoid using autoaugment in your CIFAR data loader, you can set it to False. But it may not exactly reproduce the results from README.
Or if you want to import autoaugment, can you print your full log here? I am not able to see which line cause the error. Thanks.

Hello, why is the accuracy of SNN using BN alone only about 46% on average?

Do you mean ANN trained with BN has low conversion accuracy?
We tried to analyze the difference between ANN w/ BN and ANN w/o BN, but we could not find any explicit difference. Their activation distribution looks similar. We can only say that ANN w/ BN has more activation mismatch during conversion, thus our calibration has more improvement.

Yes, the effect of Light and Advanced calibration optimization is really obvious, and the accuracy of Light and Advanced calibration by adding Usebn is similar to the effect of the paper. The ANN conversion accuracy can reach 86.111% without useBN and any calibration, so the reason for the low conversion accuracy with UseBN is not clear.

The ANN conversion accuracy can reach 86.111% without useBN and any calibration, so the reason for the low conversion accuracy with UseBN is not clear.

Yes, the reason is unclear. We tried, but we could not figure it out. We just notice that, before our paper, no one use ANN w/ BN to do the conversion, we use our calibration to solve this problem but the cause is indeed unclear. Sorry about this.
The underlying reason could be a potential research topic.

Ok, the problem I first raised was that lambda could not be serialized, but when I run the code the other day, it seems to solve the problem automatically, so I can continue to discuss the problem with you now. As for the influence of Ann-to-SNN coding on accuracy, what do you think about coding? The constant encoding used in this paper is also not very clear for encoding as pulses.

Ok, so for the talk where the time step is a little bit longer, I'm going to try to make the time step a little bit longer to see what happens.

Maybe you can try Poisson encoding with calibration, I think it can also improve plain Poisson encoding.
Personally speaking, I am not very fond of Poisson encoding. First, it is very inefficient on real hardware because you have to generate many random numbers, and second, people tend to convert it to ternary pulses (+1, -1, 0), and it drops too much performance.

请问 constant encoding是什么编码？是常数编码吗？


chore: remove unmock relay followup

This PR resolves []
Description
removes all jest.unmock\("react-relay"\) references from eigen.
Used Find and Replace regex jest.unmock\("react-relay"\)(\r?\n|\n) in vscode on find and empty replace string

PR Checklist

[ ] I tested my changes on iOS / Android.
[ ] I added screenshots or videos to illustrate my changes.
[ ] I added Tests and Stories for my changes.
[ ] I added an app state migration.
[ ] I hid my changes behind a feature flag.
[ ] I have prefixed changes that need to be tested during a release QA with [NEEDS EXTERNAL QA] on the changelog.

To the reviewers 👀

[ ] I would like at least one of the reviewers to run this PR on the simulator or device.

Changelog updates
Changelog updates

#nochangelog

Need help with something? Have a look at our docs, or get in touch with us.

feel free to merge on green

@pvinis there were some errors on the recommit hook though coming from eslint?? Did we add eslint there? had to push with --no-verify

what kind of errors? cc @damassi

  13:20  error  React Hook "useTracking" cannot be called at the top level. React Hooks must be called in a React function component or a custom React Hook function  react-hooks/rules-of-hooks
something like this coming from some tests, it wasn't complaining before

also detect-secrets failing 🤔

I had that yesterday. I think there's a new version. I can take a look in a few min 👍

You can repro like this:
➜ yarn lint eigen/src/app/Components/Artist/ArtistInsights/ArtistInsights.tests.tsx
from what I understand we added yarn lint with eslint on the pre-commit hook for the staged files and this causes this. also when I open the file in VScode I see 🔴 underlining the line.
No stress just reporting :)

tests are passing 💚

can you rebase on top of https://github.com/artsy/eigen/pull/8049 (or main once this is merged) to see the versions of detect-secrets?

also, i pushed a pr for the eslint thing. correct report.

@pvinis thanks! Although the linting issue is that this check didn't happen before and now it breaks so many files (the one that I sent was one of many examples)
Whenever a dev touches something they will have to run --no-verify due to the yarn lint eslint change 🤔 do you think we can avoid that?

going to slack


className propTypes are a mix of 'any' and 'node'.

While working on some TypeScript type definitions, I noticed the propTypes for className throughout the project are a mix of PropTypes.any and PropTypes.node.
Is there a reason to diverge from React's default string type for this? If not, I can change them to be consistent throughout the project - it'll definitely simplify the typing work.

version 3.7.0
components: all

I initially went with any to be less strict about what was sent to className prop because I imagined a consumer could make use of the classnames module within reactstrap components. This was early on, I don't think anyone uses className prop like this and should not be recommended. I would happily accept a pr that switches className props to be string. 👍
Thanks!


Don't reattach if younger than 2 minutes

Currently it can happen that a bundle is reattached almost immediately after it got sent

https://github.com/iota-pay/iota-payment-module/commit/d312c6f4f53a3620de1648ff2122de14c11c2cdc


Consolidation of Cloudant support

The following issues are still open on Cloudant and should be addressed:

[x] Inlining of recent JavaScript runtime fails due to escaping issues (#70)
[ ] There is an open bug regarding empty intermediate databases (#60)
[ ] Merging of databases has to be tested and debugged in order to support all produced M/R chains

Cloudant's gone in v2


Add service; Add helper file; Add controller test

Add service creation
Add a helper file, putting function of creating resources, creating deployments an creating services into it
Acc a controller test file, testing the controller

Change controle file's filename
Change to multi group
Add pkg folder and put apis and controllers into it


Use Python 3.9 rather than Python 3.8

We had a question why we are using Python 3.8, even though the dependencies should also resolve under Python 3.9.

It's not clear to me which component is forcing 3.8 as the lowest common denominator? Both tflite-support and PyCoral have 3.9 as a minimum version.
Using this approach means no CVE updates for this version of Python.

Short answer is Python 3.8 ships with Ubuntu 20.04 LTS, so should have some support from Canonical until 2032.
On the other had, Python 3.8 is end of life 2024-10, while Python 3.9 has one extra year of support until 2025-10: https://devguide.python.org/versions/
I've tested the image-labelling example with Python 3.9 and it works.
Let's discuss which version should we use for these examples.

A quick test of the upstream examples on a RPi 5 indicates that it is viable to change to using Python 3.9. We only need to pin different versions of the dependencies:
https://github.com/canonical/tf-lite-examples-snap/blob/31fed5b9ae044f1971094ed32e9a72341124bd67/upstream-examples/snap/snapcraft.yaml#L49-L52


Fix missing return in function not returning void

This fixes a build error:
error: control reaches end of non-void function [-Werror=return-type]

The problem has been resolved


Pad all ISIC and ISCO data to 4 digits

Addresses #157 by

[x] editing international_codes.R to include a _pad variable to all ISIC and/or ISCO data to 4 digits. This ensures that they keys come ready with the appropriate data into the main GLD code without need to edit on the fly.
[x] editing all GLD code to make sure that the code takes this _pad variable from they key instead of the original 2-digit variable.
[ ] checking the results by hand
[ ] running the GLD checks to make sure it passes the 4-digit check.

Will also address #159 by making any changes necessary to the GLD code.

Resume by re-running all code and checks

Code Completed

[ ] I2D2
[ ] GLD
[ ] I2D2 Checks
[ ] GLD Static Checks
[ ] GLD Dynamic Checks