Are the Flow types completely broken in this repo?

Hey there,
I installed this project and ran flow and got a ton of errors:
Error: node_modules/react-native-keyboard-aware-scroll-view/lib/KeyboardAwareHOC.js:39
 39: function listenToKeyboardEvents(ScrollableComponent: React$Component) {
                                                          ^^^^^^^^^^^^^^^ React.Component. Application of polymorphic type needs <list of 1-2 arguments>. (Can use `*` for inferrable ones)

Error: node_modules/react-native-keyboard-aware-scroll-view/lib/KeyboardAwareHOC.js:96
                                          v--------------------
 96:         this.keyboardWillShowEvent = Keyboard.addListener(
 97:           'keyboardWillShow',
 98:           this._updateKeyboardSpace
 99:         )
             ^ EmitterSubscription. This type is incompatible with
 96:         this.keyboardWillShowEvent = Keyboard.addListener(
             ^^^^^^^^^^^^^^^^^^^^^^^^^^ function type
  Callable property is incompatible:
     45:     keyboardWillShowEvent: ?Function
                                     ^^^^^^^^ function type. Callable signature not found in
                                              v--------------------
     96:         this.keyboardWillShowEvent = Keyboard.addListener(
     97:           'keyboardWillShow',
     98:           this._updateKeyboardSpace
     99:         )
                 ^ EmitterSubscription

Error: node_modules/react-native-keyboard-aware-scroll-view/lib/KeyboardAwareHOC.js:100
                                          v--------------------
100:         this.keyboardWillHideEvent = Keyboard.addListener(
101:           'keyboardWillHide',
102:           this._resetKeyboardSpace
103:         )
             ^ EmitterSubscription. This type is incompatible with
100:         this.keyboardWillHideEvent = Keyboard.addListener(
             ^^^^^^^^^^^^^^^^^^^^^^^^^^ function type
  Callable property is incompatible:
     46:     keyboardWillHideEvent: ?Function
                                     ^^^^^^^^ function type. Callable signature not found in
                                              v--------------------
    100:         this.keyboardWillHideEvent = Keyboard.addListener(
    101:           'keyboardWillHide',
    102:           this._resetKeyboardSpace
    103:         )
                 ^ EmitterSubscription

Error: node_modules/react-native-keyboard-aware-scroll-view/lib/KeyboardAwareHOC.js:105
                                          v--------------------
105:         this.keyboardWillShowEvent = Keyboard.addListener(
106:           'keyboardDidShow',
107:           this._updateKeyboardSpace
108:         )
             ^ EmitterSubscription. This type is incompatible with
105:         this.keyboardWillShowEvent = Keyboard.addListener(
             ^^^^^^^^^^^^^^^^^^^^^^^^^^ function type
  Callable property is incompatible:
     45:     keyboardWillShowEvent: ?Function
                                     ^^^^^^^^ function type. Callable signature not found in
                                              v--------------------
    105:         this.keyboardWillShowEvent = Keyboard.addListener(
    106:           'keyboardDidShow',
    107:           this._updateKeyboardSpace
    108:         )
                 ^ EmitterSubscription

Error: node_modules/react-native-keyboard-aware-scroll-view/lib/KeyboardAwareHOC.js:109
                                          v--------------------
109:         this.keyboardWillHideEvent = Keyboard.addListener(
110:           'keyboardDidHide',
111:           this._resetKeyboardSpace
112:         )
             ^ EmitterSubscription. This type is incompatible with
109:         this.keyboardWillHideEvent = Keyboard.addListener(
             ^^^^^^^^^^^^^^^^^^^^^^^^^^ function type
  Callable property is incompatible:
     46:     keyboardWillHideEvent: ?Function
                                     ^^^^^^^^ function type. Callable signature not found in
                                              v--------------------
    109:         this.keyboardWillHideEvent = Keyboard.addListener(
    110:           'keyboardDidHide',
    111:           this._resetKeyboardSpace
    112:         )
                 ^ EmitterSubscription

Error: node_modules/react-native-keyboard-aware-scroll-view/lib/KeyboardAwareHOC.js:289
289:         reactNode,
             ^^^^^^^^^ null or undefined. This type is incompatible with the expected param type of
  9:     reactNode: Object,
                    ^^^^^^ object type. See: node_modules/react-native-keyboard-aware-scroll-view/lib/KeyboardAwareInterface.js:9

Error: node_modules/react-native-keyboard-aware-scroll-view/lib/KeyboardAwareHOC.js:289
289:         reactNode,
             ^^^^^^^^^ number. This type is incompatible with the expected param type of
  9:     reactNode: Object,
                    ^^^^^^ object type. See: node_modules/react-native-keyboard-aware-scroll-view/lib/KeyboardAwareInterface.js:9

Error: node_modules/react-native-keyboard-aware-scroll-view/lib/KeyboardAwareHOC.js:300
300:       this.position = e.nativeEvent.contentOffset
                                         ^^^^^^^^^^^^^ property `contentOffset`. Property not found in
300:       this.position = e.nativeEvent.contentOffset
                           ^^^^^^^^^^^^^ Event

I tried to just check out the repository and fix the errors, but running flow from a fresh checkout (git clone and yarn and yarn flow in that order) cough up ~1000 Flow errors.
Are the type annotations broken? Is there a Flow version issue?

Any update/solution to this problem with flow?

Hi @nojasne!
I didn't have time to address this yet, but expect updates next week, my team is currently working on this.

@alvaromb any informations about a eventual resolution? Thank you


[gardening] Remove unused variable loweredMT

@swift-ci please smoke test

@swift-ci please test

@slavapestov Good point. Fixed, squashed and pushed. Thanks!

@swift-ci please smoke test

@swift-ci please test

Build failed
Jenkins build - Swift Test Linux Platform
Git Commit - 97284b1d7e5df93643bb7d15dff5bbd83971f17f
Test requested by - @practicalswift

Build failed
Jenkins build - Swift Test OS X Platform
Git Commit - 97284b1d7e5df93643bb7d15dff5bbd83971f17f
Test requested by - @practicalswift


Class 'App\Models\TNTSearch' not found

I face to problem with the fresh installation. When I tried to create new post I got an error:
FatalErrorException in Post.php line 171: Class 'App\Models\TNTSearch' not found
after I clicked the "save" button. The same error happened with tags creation. But the post/tag was created.

@austintoddj I guess this one can also be closed since it's fixed in the latest version


Add custom script engines for donwloading/uplaod/listing

See #146.
It should also work for:  #120, #139, #116

Any word on this PR? 👍 for getting it in. We need to add caching support, but have on our on-site file store that we would like to use instead of S3.

@grioja I work on this on and off, contributions are welcome.
In the mean time, setting up minio https://www.minio.io/ might get you around the problem.

@blender @fabb What's missing to land this PR? I may try to help out a little bit with my very little knowledge of Haskell if something is needed.

@BalestraPatrick basically the path is laid out. What is missing is the implementation.
Whenever you read undefined, that is where the gap needs filling.

I have resolved the conflicts are rebased on #179

Can you elaborate a little bit on the idea for your implementation?

          1 Warning

:warning:
Big PR

  Generated by :no_entry_sign: Danger

@BalestraPatrick the idea is to invoke a script at mEnginePath and pass it a bunch on arguments:
First argument is always the command currently being executed: i.e. download, upload or list
In case of download, arguments are:

download
remote-path-to-the-file-as-constructed-by-rome
local-path-as-constructed-by-rome

In case of upload, arguments are:

upload
local-path-as-constructed-by-rome
remote-path-to-the-file-as-constructed-by-rome

In case of list, arguments are:

list
remote-path-to-the-file-as-constructed-by-rome

scripts should return exit code 0 on success and be passed stdin, stdout and stderr descriptors by rome itself. You can use Turtle to invoke the scripts.

This is to start with so that things don't get too complicated.
Alternatively the idea was to pass a description of the data structure that the commands rely upon to the script. However I don't have a concise solution for this. One idea is to use JSON to describe them but I think for a first implementation this is an overkill.


Provide category tag per item containing the sub in the 'home' RSS feed

Is your feature request related to a problem? Please describe.
I'm using the RSS feeds to get the latest posts. The user can select a specific sub, or it defaults to the home RSS feed. To determine the active sub, you can parse the URL. However, in the 'home' RSS feed all subs are visible in random order.
Describe the solution you'd like
To determine the sub per item in the 'home' RSS feed, I would like to see the <category> tag being used. This tag will contain the name of the sub per item. Optionally, a 'domain' attribute can be provided with the full URL to the sub as the attribute's contents. This tag is part of the RSS 2.0 specification.
Additional context
In lib/rss.js the generateRssFeed() function gets a list of items and separately the sub. Here the category tag could also be used for all RSS feeds but the 'home' feed to provide the sub for all items at once. The generateRssItem() function gets only the item object. Does this item object contain the sub as well (as in item.sub)? Then it can be added conditionally if it is available. The link tag off the channel part of the RSS feed should be a function so it can be reused in generateRssFeed() and in the attribute 'domain' of the category tag in generateRssItem().

Great recommendation! Thanks


JSONTest failing on Windows

Description
The JSONTest is failing on Windows.
Steps to reproduce

Build and run hedera-sdk-cpp-tests.exe
Observe failing test

Additional context
No response
Hedera network
other
Version
v0.4.0-dev
Operating system
Windows

My mistake, not reproducible on main.


Movie title search

updated index.html to display movie posters as search results.
also returns gin as liqor choice for movie results not based off genre

looks great


Sec1 SAST Security Plugin

Repository URL
https://github.com/sec0ne/secone-sast-security-scanner
New Repository Name
secone-sast-security-scanner-plugin
Description
This plugin integrates Secone SAST (Static Application Security Testing) security scanner with Jenkins, allowing you to perform security scans as part of your CI/CD pipeline.
GitHub users to have commit permission
@rahuldarekar222
@saurabhthatte007
Jenkins project users to have release permission
rahuldarekar
saurabhthatte_sec1
Issue tracker
Jira

Security audit, information and commands
The security team is auditing all the hosting requests, to ensure a better security by default.
This message informs you that a Jenkins Security Scan was triggered on your repository.
It takes ~10 minutes to complete.
Commands
The bot will parse all comments, and it will check if any line start with a command.
Security team only:

/audit-ok => the audit is complete, the hosting can continue :tada:.
/audit-skip => the audit is not necessary, the hosting can continue :tada:.
/audit-findings => the audit reveals some issues that require corrections :pencil2:.

Anyone:

/request-security-scan => the findings from the Jenkins Security Scan were corrected, this command will re-scan your repository :mag:.
/audit-review => the findings from the audit were corrected, this command will ping the security team to review the findings :eyes:.
	It's only applicable when the previous audit required changes.

Only one command can be requested per comment.

(automatically generated message, version: 1.29.12)

/hosting re-check

can anyone update on the hosting request?

This should be merged into https://github.com/jenkins-infra/repository-permissions-updater/issues/4087 or vice versa.

@NotMyFault,
We seek your guidance on the next steps for our plugin release. The initial plan was to provide users with two options: a dedicated SAST scanning plugin and another plugin offering both SAST and SCA capabilities.
Could you confirm whether we should proceed with both plugins, allowing users the flexibility to choose according to their needs, or if any adjustments are required before finalizing the release? Your input will help ensure we move forward efficiently and meet our release timeline.
Thank you for your prompt response.

Hi just one plugin would be the recommended approach in this case.

(the bot was drunk, not able to get the reaction API of the issue description :( I will put some retry mechanism in place to reduce likelihood of such behavior to occur again)

@timja
Thanks for the input! Could the team assist with the hosting request for issue 4087? Once that's taken care of, we can proceed to close this request.

4087 is completed hence closing this request


Yazi uses incorrect prefixes with the file/directory sizes.

What system are you running Yazi on?
Linux Wayland
What terminal are you running Yazi in?
foot 1.16.2
Yazi version
yazi 0.2.2 (ba0c860 2024-01-26)
Did you try the latest main branch to see if the problem has already been fixed?
Tried, but the problem is still present
Describe the bug
Yazi counts in IEC (power of two), but displays JEDEC (power of ten) prefixes (KB, MB, GB, TB).
Expected Behavior
Yazi should display the correct prefixes, which is in this case: KiB, MiB, GiB, TiB, etc.

Thanks for the reporting!
How about we use K, M, G, etc. instead of the current KB, MB, GB, which will match the behavior of ls -lah, and it's also shorter, like this:

How about we use K, M, G, etc. instead of the current KB, MB, GB, which will match the behavior of ls -lah, and it's also shorter, like this:

ls also displays prefixes incorrectly. Should be Ki, Mi there, but since we know we are counting bytes, KiB, MiB would be better. K, M would be ok with ls -lah --si

Actually, I was wrong too. ls displays SI prefixes when uses power of 10 --si, so it returns the "correct" prefixes there (the difference with JEDEC is the lowercase k for kilo). Another issue is whether they should continue to use SI prefixes.

Hmm I'm a bit confused.
If I understand correctly, kB is power of 10, KB is power of 2, and KB is equivalent to KiB. So, Yazi's units are correct right?

My apologies, I got completely messed up. Note for myself. Do not open bug reports in the middle of the night ;)

Thank you for the explanation, I understand now.
However, KiB is just too long, and it's a challenge for limited space. I really don't want to explain to users every time that I'm using the correct unit.
So I've decided to switch to K, thus I only need to tell users that it behaves the same as ls and then just enjoy life. 🤦🏻

Done by https://github.com/sxyazi/yazi/commit/c02d69590bda49babe0883ff78341d92e557f381

Once again, I apologize for the mix-up I made. I have edited the original report so it makes a little more sense.
I'm afraid https://github.com/sxyazi/yazi/commit/c02d69590bda49babe0883ff78341d92e557f381 doesn't change much. It follows the ls but not the standards for binary multiples and will continue to be a source of confusion.
Unless I overlooked something (again), the only correct solution would be to use IEC prefixes.


⚠ Bofrost.fr has degraded performance

In 101bf54, Bofrost.fr (https://www.bofrost.fr) experienced degraded performance:

HTTP code: 200
Response time: 1015 ms

Resolved: Bofrost.fr performance has improved in f51873a after 1 hour, 36 minutes.


[rt.openssl.org #3919] ssl.h uses ALL in its default cipher list

Migrated from rt.openssl.org#3919 (status was 'new')
Requestors:

<EMAIL_ADDRESS>
From<EMAIL_ADDRESS>on 2015-06-21 22:14:38:
The following is from ssl.h, around line 285:

    /*
     * The following cipher list is used by default. It also is substituted when
     * an application-defined cipher list string starts with 'DEFAULT'.
     */
    # define SSL_DEFAULT_CIPHER_LIST "ALL:!aNULL:!eNULL"

Its 2015, and its probably best to change that to something like:

    # define SSL_DEFAULT_CIPHER_LIST "HIGH:!aNULL:!eNULL"

Or:

    # define SSL_DEFAULT_CIPHER_LIST "HIGH:!aNULL:!eNULL:!RC4:!MD5"

I personally have less of a problem with MD5 in this context because
the HMAC must be broken in 2-MSL, and many/most attackers cannot do
it. But its a compliance thing....

Also, browser are now warning about outputted cryptography, that
includes the LOW and MEDIUM stuff (and RC4 and MD5). For example, see
http://security.stackexchange.com/q/83831 and
http://stackoverflow.com/q/30270788. So anything using OpenSSL with
those settings could cause problems for unsuspecting users.

The change also means the library is more secure out of the box, and
easier to use correctly and harder to use incorrectly.

For those who want Opportunistic Security
(http://tools.ietf.org/html/rfc7435), they can use different settings
that suite their taste.

_______________________________________________
openssl-bugs-mod mailing list
<EMAIL_ADDRESS>https://mta.openssl.org/mailman/listinfo/openssl-bugs-mod

No RC4 or MD5 ciphers are in DEFAULT in 1.1.0. Closing.


Suddenly status "No Response" on all broadlink switches

Hey guys,
See screenshots:

Same happens in the Home app on my iPhone
Already tried the suggested solution (here) of renaming the "user" parameter in config.json re-adding it to i Home app - but it didn't solve it..
Each attampt of the apps to refresh the statuses, results this in the logs:
0|homebridge  | [9/1/2019, 5:21:40 PM] [Broadlink RM] Volume Up getSwitchState: false
0|homebridge  | [9/1/2019, 5:21:40 PM] [Broadlink RM] Mute getSwitchState: false
0|homebridge  | [9/1/2019, 5:21:40 PM] [Roomba] Running status requested
0|homebridge  | [9/1/2019, 5:21:40 PM] [Roomba] Battery status requested
0|homebridge  | [9/1/2019, 5:21:40 PM] [Broadlink RM] Volume Down getSwitchState: false
0|homebridge  | [9/1/2019, 5:21:40 PM] [Broadlink RM] TV getSwitchState: true
0|homebridge  | [9/1/2019, 5:21:40 PM] [Broadlink RM] Air Conditioner getTargetHeatingCoolingState: 0
0|homebridge  | [9/1/2019, 5:21:40 PM] [Broadlink RM] Air Conditioner getTargetTemperature: 26
0|homebridge  | [9/1/2019, 5:21:40 PM] [Broadlink RM] Air Conditioner getCurrentTemperature (using pseudoDeviceTemperature 26 from config)
0|homebridge  | [9/1/2019, 5:21:40 PM] [Broadlink RM] Air Conditioner getCurrentHeatingCoolingState: 0
**Worth noting: commands to Siri through homepod DO WORK! and tapping few times on a swtich in the app - 'corrects' its status to normal behavior, but then leaving the screen and coming back - still fails to update status..
Anyone encountered this or know how to solve?

the problem was caused by the roomba plugin, for future reference of whoever comes here...


feat: add automatic sdk cli versioning

:warning: depends on #8061.
This is part of a piece of a more general piece of work to improve our own releasing process.
TL;DR: our releasing process (defined in https://github.com/dagger/dagger/blob/main/RELEASING.md) has steadily become more and more complex over time. Now that we're aiming for faster release cadences (at least once every couple of weeks, and often once a week), this process is starting to incur a lot of overhead. (I estimate I probably spend at least half a day per release). We can take some of this time, and use it to automate, to save time later on.

This first piece attempts to resolve the weirdness around tagging. The current process (summarized) is:

Generate engine release note and merge them
Tag the engine as vX.Y.Z
Wait for the engine to be released, auto-generating a PR with bumped cli version files (da92186 (#7690)).
Generate SDK release notes, and merge the PR
Tag the SDKs as sdk/<sdk>/vX.Y.Z
Wait for the SDKs to be released

This is weird, and this dependency introduces a slowdown in our release process. Instead, with this PR, the goal is to:

Generate engine and SDK release notes and merge them all together
Tag the engine as vX.Y.Z
Wait for the engine to be released
Tag the SDKs as sdk/<sdk>/vX.Y.Z
Wait for the SDKs to be released

There should be no extra PR steps at this stage, etc.

The main obstacle with this is that we need to bump the cli version for each SDK - this version number is used by each standalone SDK (i.e. not with modules) to perform automatic provisioning when a CLI has not been detected in the environment (i.e. when run with dagger run). This manual bump is the main reason for the PR step in the first place.
However! We can remove this step by automatically setting the version number only on publish - while in main, the version number will be unset, but when published to pypi/crates/etc, we'll set it then.

This is very easy for the python, elixir, "just upload a tarball kind of release" - we just modify it right before publishing
This is an incredible pain for go and php, "mirror to a git repository kind of release" - we need to rewrite history to automatically insert the right version numbers (while taking incredible care to make sure to avoid needlessly changing commit IDs).

TODO:

[x] Implement the insane git filter script
[x] Make version file generation simpler (by splitting them out as much as possible)
[x] Connect the generation script into CI, reworking Bump and Publish
[x] Select filler values for main
[x] Test!

Decided to rework this, and removed the version-update.py script entirely. The original intent of this was to be able to tag any commit and have it release correctly. Unfortunately, this isn't really a possible goal, due to release notes, other prep, etc.
Additionally, it introduces a significant amount more complexity, and also since it introduces more complexity to the mirroring, it becomes harder to remove it in the future - this is essentially a one-way street. Finally, it's really really unclear how this would scale nicely into a release-branch model, e.g. tagging v1.2.3 off of a v1.2 branch.
So instead, we simplify the process - instead of doing the SDK version bumps in a separate PR, we'll handle this as part of the release notes PR. This means that we'll have one commit that we can tag with all the tags, but also means we still keep some level of manual control. There is one disadvantage to this: main will temporarily have SDKs that point to versions of the engine that do not yet exist. This should be fine though - we just need to update our provisioning tests to handle this, and we can do this. Additionally, the only SDKs that are directly consumable off of main are Go and PHP - this will temporarily place the state of main for them into an invalid state, however, I think this is probably worth it for the complexity that this removes from our release.

Linting flake is https://github.com/dagger/dagger/pull/8062.

So instead, we simplify the process - instead of doing the SDK version bumps in a separate PR, we'll handle this as part of the release notes PR. This means that we'll have one commit that we can tag with all the tags, but also means we still keep some level of manual control.

I like this approach a lot. I think it's worth keeping manual checks + control in this area but agree it'd be very nice to consolidate the number of PRs involved in the overall release.

Thinking out loud: to avoid the possible issues around SDKs having engine versions that don't exist yet, I'm wondering if there's some way to actually publish engine+CLI versions in the PR itself in a safe way.
In theory, it seems possible to push an engine image and upload a CLI without that triggering the whole world to start automatically using those versions. Some way to "stage" them essentially, such that they are really uploaded but not officially published per-se and not yet considered the "latest" version.
Then the process would look something like:

Open PR for release notes + engine version bumps
CI publishes provisional engine+CLI for the new version
SDK provisioning tests run against that provisional engine+CLI
Once merged to main, we manually push the tags for the engine+CLI and all SDKs (same as today)

Tag push for engine+CLI triggers the staged publishes to be made "official" and picked up automatically when installing the "latest" version
Tag push for each SDK triggers them to be published (same as today)

One potential gotcha here is that by default it would allow anyone to open a PR and trigger publishes of these provisional engine+CLI versions.

Maybe there's some way to require manual approval from a dagger maintainer
Or maybe there's some way to structure the staging of provisional engine+CLI publishes such that even if someone did this, it wouldn't cause any actual harm. This is an obscure situation anyways, so even if it requires some manual cleanup or something I'd be okay with that.

I'm leaving the exact way you'd stage provisional engine+CLIs vague obviously, and not saying any of this is a blocker here. Just curious what others think.

In theory, it seems possible to push an engine image and upload a CLI without that triggering the whole world to start automatically using those versions. Some way to "stage" them essentially, such that they are really uploaded but not officially published per-se and not yet considered the "latest" version.

I think we kind of have this today with publishing directly off of main? Or do you mean, like a full tagged build, with versions all correctly configured?

One potential gotcha here is that by default it would allow anyone to open a PR and trigger publishes of these provisional engine+CLI versions

The problem is, I don't actually know if this is possible at all - we'd need to get secrets into a PR context, and however we do that, it's not really secure. One option instead of this would be to use manual workflow dispatch - you could trigger a staging release, since that's locked behind maintainer permissions. I'm not quite sure where the artifacts would end up though.
:thinking: I'm not 100% sure we'd want this to be part of every release process - but I can definitely see the value in doing a "staged" release for testing purposes. That said, yeah, I'm not sure we should block on this, it feels like another big piece of work on top of this.


Write tests for timeout and ignored paths

Codecov Report

Merging #25 into master will increase coverage by 5.5%.
The diff coverage is 100%.

@@            Coverage Diff            @@
##           master      #25     +/-   ##
=========================================
+ Coverage   81.96%   87.46%   +5.5%
=========================================
  Files           8        8
  Lines         316      351     +35
=========================================
+ Hits          259      307     +48
+ Misses         57       44     -13

Impacted Files
Coverage Δ

include/inotify/NotifierBuilder.h
100% <ø> (ø)
:arrow_up:

source/NotifierBuilder.cpp
100% <100%> (ø)
:arrow_up:

source/Inotify.cpp
79.83% <100%> (+9.99%)
:arrow_up:

test/unit/NotifierBuilderTests.cpp
100% <100%> (ø)
:arrow_up:

Continue to review full report at Codecov.

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


Docker image is close to 100mb

The current Docker image for the operator is close to 100MB at DockerHub. It looks like the change in #191 is the one that caused the biggest bump. Reverting it locally caused the image to go down to the initial levels.

$ docker images jaegertracing/jaeger-operator:1.10.0
REPOSITORY                      TAG                 IMAGE ID            CREATED             SIZE
jaegertracing/jaeger-operator   1.10.0              806a4530248d        7 days ago          266MB

$ docker images jpkroehling/jaeger-operator:latest
REPOSITORY                    TAG                 IMAGE ID            CREATED             SIZE
jpkroehling/jaeger-operator   latest              dcfed8ef97cc        30 seconds ago      44.9MB

I'm not sure this is a problem right now, but it's something to keep an eye on.

in #191 we switched to centos base image because we needed openssl to generate certs for ES. The whole approach is a bit nasty we run shell script to do that. I would prefer to generate the certs from go if it is possible.

So, all we need is a couple of cert files? If so, we should be able to just re-declare the base image.

By the way, looks like it's not that hard to generate from Go. I was looking at it during #473 and generating a cert is actually quite easy with go. Basically, rsa.GenerateKey() for the private key, and x509.CreateCertificateRequest() / x509.CreateCertificate() for the certificate.
I assume we would still need this code after we remove some of the duplicate code from the ES Operator, right?

I'm closing this, as it's unlikely that we'll ever generate the certs from Go in the foreseeable future.


Dev/add memo to token creation

Added a new flag to add a memo on create-token
Add a transaction instruction to write memo via Memo Program v2

The Vec<u8> address was derived from the devnet existing program address (there probably a better way to import the program id based on the network (not sure how to retrieve those values)
>>> import base58
>>> bytelist = base58.b58decode("MemoSq4gqABAXKb96qnH8TysNcWxMyWCqXgDLGmfcHr")
>>> barr = [b for b in bytelist]
>>> barr
# [5, 74, 83, 90, 153, 41, 33, 6, 77, 36, 232, 113, 96, 218, 56, 124,
# 124, 53, 181, 221, 188, 146, 187, 129, 228, 31, 168, 64, 65, 5, 68, 141]

closing in favor of newer PR https://github.com/solana-labs/solana-program-library/pull/1709


Compile the mpu::RegisterBlock struct on all targets

closes https://github.com/rust-embedded/cortex-m/issues/336

Thanks for the pull request, and welcome! The Rust team is excited to review your changes, and you should hear from @adamgreig (or someone else) soon.
If any changes to this PR are deemed necessary, please add them as extra commits. This ensures that the reviewer can see what has changed since they last reviewed the code. Due to the way GitHub handles out-of-date commits, this should also make it reasonably obvious what issues have or haven't been addressed. Large or tricky changes may require several passes of review and changes.
Please see the contribution instructions for more information.


JUnit report is not indented

JUnit report XML file is not indented. For example, see this.
That makes it hard to visually inspect the JUnit report files.
JUnit report files are generated by junit-report.xsl. Although it has xsl:output with indent="yes", the xsl:output is not used (because of unreferenced name="escaped"):
https://github.com/xspec/xspec/blob/4a9c470421c671fbb32a94d76153ff3405b41a26/src/reporter/junit-report.xsl#L28

@cirulls ,
Looks like the JUnit report was implemented in #6. Do you know these?

The reason the output XML is not indented
The purpose of the unreferenced xsl:output
How Kal Ahmed was involved. (just curious)

Yes, I implemented this back in 2016, it was one of my first contributions to XSpec. There are more technical notes in #2. Regarding your questions:

It was probably accidental or maybe for space reason as the JUnit is quite verbose. I agree that the indentation would be better for readability and debugging purposes.
I'll check the unreferenced name attribute in xsl:output, if that's the case there is certainly a contradiction. I'll get back to you.
@kal is a colleague of mine. At the time we independently wrote JUnit serializations for XSpec  and I collected our separated efforts in that pull request (this may well be the explanation for the unreferenced attribute).


updatedpodfailurepolicy doc

resolves #44952

Did you intend to include the package-lock.json file? That looks like it would be better in a separate dependency update patch if needed.

Did you intend to include the package-lock.json file? That looks like it would be better in a separate dependency update patch if needed.

I intended to but you are right, it is better for separate patch.


Update the \README.md file to describe the repo

I am finishing the week 0 tutorial, thanks!

I would like to push my portfolio. It is running at
https://mcaron-sps-summer20.uc.r.appspot.com

Make the following improvements:

Fix incorrect CSS syntax; standardize styling
Consider the benefits to avoiding tables for layout. Will implement best practices going forward
Make changes regarding class vs id to appropriately apply specificity
Create consistent style in the JavaScript file


Feat: be able to use -T and -U options

Hello!
I would like to add options to the maven commands so I can use more maven capabilities. I usually use -U and the -T to make it use multicore. This is an example of how it could look:

{
  'glaulher/maven.nvim',
  branch = 'newfeat',
  cmd = { 'Maven', 'MavenExec' },
  dependencies = 'nvim-lua/plenary.nvim',
  config = function()
    require('maven').setup {
      executable = 'mvn',
      commands = { -- add custom goals to the command list
        { cmd = { install ' }, desc = 'Install using all cores' , Options = "-T 1C "},
        { cmd = { 'install ' }, desc = 'Install using all cores update all', Options="-T 1C -U " },
      },
      maven_central_url = 'https://mvnrepository.com/repos/central',
    }
  end,
}

Is this possible as it is now and I have just not found the setting, or does this sound like a good new feature?
Thanks

the cmd paramter can accept a string list, so I think you can do something like this
{cmd={"install", "-T1C"}


#350 | adding zkEVM faucet in dev-tools page

Fixes #350
Description
A new tab was added to the dev tools page with a zkEVM faucet. Any developer can enter a valid address to receive up to 50 zTLOS daily with this faucet.
Test scenarios
https://deploy-preview-351--telos-app-native-staging.netlify.app/testnet/developers?tab=tlos-zkevm

Tested and worked against api-dev.telos.net

The token was renamed to tTLOS so we need to update the UI


Add a non-api way to load PDFs with pypdf

Hello !
It would be nice if we could load PDFs (which is for me the main reason to use the app) without the dependency on the Unstructured API.
Why not simply use something like pydf to load PDFs ?

Great idea! Thanks for the issue 👍 It's already implemented in the latest main branch and will be included in the next release. If you want to use PyPDF now, you can install Verba from source

Thanks for the resource, we'll look into also incorporating them into Verba


Feature: Open daily notes from big calendar

It would be nice if you could for example right click on a day to open the corresponding daily note for that date. That will also make it easier to change tasks

It would also be very useful if one can open/create Weekly/Monthly and other types of notes supported by the Periodic Notes plugin: https://github.com/liamcain/obsidian-periodic-notes.

@HEmile In next release, you could click and then jump to the event, in the near future, will allow you to change the event in the calendar rather than jump to the dailynote

Available in 0.1.11


Containment fields should not bounce singularity

Description
Containment fields should not bounce singularity. Until issues like #10394 are fixed, this just leads to eventual singuloose that is not fault of engineers.
Reproduction

Set up singularity
Watch it bounce violently upon collision with field

Screenshots
This is live singuloose, reported to merely suddenly clip through field:

Additional context
I am unable to reproduce clipping behavior on 60-tick localhost, yet this is definitely a danger. Does Lizard run at 30 ticks?

30 ticks?
Yes it does since it reduces load heavily for both client an dserver

They don't, well not the way you're thinking it does. It works as it normally does: it doesn't get thrown like players and such. Please give me steps to reproduce. I've tested it and was not able to reproduce this.
https://user-images.githubusercontent.com/54602815/183413634-bfaa1bea-74e0-4bce-a6f4-6bb6845e1112.mp4

This will probably be fixed by substepping or some other cd addition to physics, instead of a bandaid fix of changing the values.


allow setting log.conf values or env vars

hello!
currently one can not edit logging configuration using this chart, because it exposes values to create the server configuration block (server.conf), but not the logging one (log.conf).
besides, there is no way of supplying additional environment variables, so one can not override properties specified in log.conf either.
it would be cool to have both of these ways, though.
cheers

@Va1, just checking, is there a reason that you reopened this issue?

@sklarsa i reopened initially because 0.21.0 was not released. now that it is, i've tested the loggingConf chart value and it successfully overrides the log.conf, however QuestDB does not take it into consideration during startup:
Found /root/.questdb mount, overwriting QUESTDB_DATA_DIR
No arguments found, start with default arguments
Running as root user
QuestDB server 6.5.3
Copyright (C) 2014-2022, all rights reserved.

Log configuration loaded loaded using factory defaults.
2022-09-29T15:05:11.878599Z A server-main QuestDB server 6.5.3. Copyright (C) 2014-2022, all rights reserved.

so, still factory defaults, despite the file is in place. can it be that QuestDB expects configuration files at /var/lib/questdb/conf instead of /root/.questdb/conf according to documentation?
https://questdb.io/docs/reference/configuration/#mounting-a-volume

how does server.conf apply, which is in the same directory (/root/.questdb/conf) is unknown to me though. can you clarify?

UPD:
https://questdb.io/docs/reference/configuration/#environment-variables-2
controlling logging via environment variables does not work either:

the variables are set so the level gotta be ERROR, but it is not:
Found /root/.questdb mount, overwriting QUESTDB_DATA_DIR
No arguments found, start with default arguments
Running as root user
QuestDB server 6.5.3
Copyright (C) 2014-2022, all rights reserved.

Log configuration loaded loaded using factory defaults.
2022-09-29T16:35:46.206036Z A server-main QuestDB server 6.5.3.

Regarding the config file locations, for compatibility reasons, QuestDB supports config files at both /root/.questdb and /var/lib/questdb.  In the docker-entrypoint.sh, we check to see if there is a mounted config at /root/.questdb, which takes precedence over /var/lib/questdb.  Please take a look at that file to understand the intricacies of the config file parsing.
As for the environment variable configs not working, I can reproduce that on my end also.  I'll open up a ticket in questdb core for more visibility.

hmmm. so the entrypoint script you referenced makes sense, but it does not explain the behaviour i'm experiencing:
server configuration is in /root/.questdb/conf/server.conf as this helm chart mounts it there and it works.
with the latest changes i submitted in a PR, logging configuration lands in /root/.questdb/conf/log.conf and it does not work. /var/lib/questdb exists but is empty.
so this is not an expected behaviour either, or is it?

That seems strange.  I think that we should try to mount the configs in /var/lib/questdb instead of /root/.questdb.  I did this in a new PR and tested with the following values.yaml:
    enabled: true
    options:
      w.stdout.level: DEBUG

Then I get the following output in the pod (after applying the helm chart):
$ k logs questdb-0
No arguments found, start with default arguments
Running as questdb user
chown: changing ownership of '/var/lib/questdb/conf/log.conf': Read-only file system
chown: changing ownership of '/var/lib/questdb/conf/server.conf': Read-only file system
QuestDB server 6.5.3
Copyright (C) 2014-2022, all rights reserved.

Log configuration loaded from: conf/log.conf

Would it be possible for you to pull my PR branch and test it on your end?

i verified that your PR works in my cluster – logging configuration changes are getting applied.
however i suspect that mounting db directory into another path under non-root may break existing deployments with existing data. will this be the case?

I don't think this should be an issue because we chown all questdb-related directories and files in the docker-entrypoint.sh.
I will merge the PR and release a new minor version.  Thanks for your assistance, and let us know if you have any more issues!


Remove now-irrelevant mention of splitting

Follow-up fix to https://github.com/cockroachdb/docs/pull/4111/files.

This change is

http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/e443e673d72c1e4db125b0eab68714cd335b018e/


keyboard-map spec is missing

Spec: https://wicg.github.io/keyboard-map/
Tests: https://wpt.fyi/results/keyboard-map

Spec added to the list of specs crawled by Reffy and to the published reports.


Arr::append and array_append suggestion

I often need to append an element to an array. There is an existing helper array_prepend but no corresponding array_append at the moment.
This would behave like PHP's array_push with the difference that it returns the modified array. Just like array_prepend today is the equivalent of PHP's array_unshift except returning the modified array.
The existing array_add helper isn't a good fit for my use case because it requires a key and value.
I'm happy to submit a PR, just wanted to first ask if this would be well received or not?

Why is this insufficient?
$array = [
    1,
    2,
    3,
];

$array[] = 4;

Of course you can use built in array management. That goes for a lot of Laravel's existing helper methods.
If you wanted to add a key/value pair to your array:
$array["newelement"] = 4;

And yet Laravel provides array_add:
array_add($array, "newelement", 4);

If you want to add an element to the beginning of an array you can always do this:
array_unshift($array, 4);

And yet Laravel provides array_prepend:
array_prepend($array, 4);

The big difference? Laravel's helper methods return the modified array. That can be helpful when you need to modify and array and return it, Laravel's methods let you do that a bit cleaner.
If you want to use native PHP array management, go for it. I'm only suggesting that an append method be added, consistent with the existing prepend method because I find them useful.

Thanks, but I don't think there's much demand for this.

@jszobody Sorry, I tried.


Create Phase C WP3.6 (UKD-UKD-S16) April'24 to September'24 six month plan/review

[ ] In plan to Mar'24, consider  in terms of organisation, practices and procedures

[ ] what worked well?
[ ] what did not work well?
[ ] what can we improve?
[ ] what should we keep?
[ ] what should we drop?

[ ] Update the Apr'24 to Sep'24 Release

[ ] Create tickets for latest 6 month objectives if necessary
[x] Add Rubin IKC reporting tickets
[ ] Review previous 6 month plan
[ ] close tickets, remove duplicates as necessary
[ ] Shift any outstanding tickets from previous plan if appropriate

[ ] Identify any  task/ milestone/ deliverable dependencies with other LSST:UK WP tasks.
[ ] Review  Phase C WP Brief
[ ] Review the SRD
[ ] Review risks

Is any escalation required?
Are there risks for those tasks/ tickets/  dependencies, … on the critical path?

12/MAR/24

meeting will take place on 26/MAR/24 when all are available

Six month review meeting took place on 26/MAR/24.  Notes are on the WP wiki page.

10/APR/24

Risk Register review took place at 09/APR/24 Alder team meeting
R74 and R75 subsequently added to the RR
remaining item is to update the Zenhub tickets once the FY24 Q2 QU is submitted


ENV example

Can you please include a ENV example. Thanks

Added https://github.com/dfstio/minanft/blob/master/env.example.json


Update creating-a-file-mapping-object.md

The link of related topics seems not work without a blank line ahead.

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


ShadowCastingMode does not exist

Hi SniperFan,
Thanks for taking this project over. I just imported your newest version and am receiving this error before I even touch anything:
Assets/Plugins/OpenUnityTools/unityserializer-ng/Serialization/UnitySerializationExtensions.cs(807,38): error CS0234: The type or namespace name ShadowCastingMode' does not exist in the namespace UnityEngine.Rendering'. Are you missing an assembly reference?
I am using Unity 4.6.1
Thanks,
Mike

Unity 5 only. Check out this fork. brainz80/unityserializer-ng

Hi SniperFan,
I don't have access to Unity 5. Is the fork that you linked supposed to
work with 4.6?
Thanks,
Mike
On Mon, Jan 19, 2015 at 5:45 AM, TheSniperFan<EMAIL_ADDRESS>wrote:

Closed #10 https://github.com/TheSniperFan/unityserializer-ng/issues/10.
—
Reply to this email directly or view it on GitHub
https://github.com/TheSniperFan/unityserializer-ng/issues/10#event-220977830
.

--
Sincerely,
Mike Luyties, CEO of RenterMonsters.com
www.rentermonsters.com
http://www.rentermonsters.com

Right on top


support set currentState

Thank you for your PR. However, I'm closing it as explained in https://github.com/j-easy/easy-states/issues/10#issuecomment-727651722.


Is there any real underlying difference in platform between linux/arm64 and linux/arm64/v8?

I noticed on Docker Hub that for arm64 images have either linux/arm64 or linux/arm64/v8. Is there currently any real difference between the two or is one currently just the more explicit form of the other and a means for future proofing the platform specification when we get a newer arm64 variant than v8?

No, they are the same. Normalized form is without the variant https://github.com/containerd/containerd/blob/ab8d99cf4bec7fe4225f73162be3da338e925791/platforms/database.go#L96

Great, thank you.


YouTube Shorts Support

I end up finding a lot of good quotes in YouTube Shorts. It would be nice if these links also worked with simple embeds. The embedding works the same it's just the link's regex would be different.
https://youtube.com/shorts/VIDEOID?feature=share
It should probably have its own CSS class because most of the videos are in portrait.

Added in 1.12.0


Add environment manager installation instructions and environment

Update installation instructions to use micromamba
Add environment file

CC @MakerTobey @zoccoler @haesleinhuepf
The environment file works on Mac, would appreciate testing on Windows.

Hi @jni , thanks for setting this up! I tested on my Windows 10 and the environment works, napari opens and I can run a few napari-assistant widget 😸 however exporting notebook from the assistant fails 😿
Traceback (most recent call last):
  File "C:\Users\mazo260d\mambaforge\envs\napari-latam\Scripts\jupyter-lab-script.py", line 5, in <module>
    from jupyterlab.labapp import main
  File "C:\Users\mazo260d\mambaforge\envs\napari-latam\lib\site-packages\jupyterlab\__init__.py", line 8, in <module>
    from .handlers.announcements import (
  File "C:\Users\mazo260d\mambaforge\envs\napari-latam\lib\site-packages\jupyterlab\handlers\announcements.py", line 14, in <module>
    from jupyter_server.base.handlers import APIHandler
  File "C:\Users\mazo260d\mambaforge\envs\napari-latam\lib\site-packages\jupyter_server\base\handlers.py", line 23, in <module>
    from jupyter_events import EventLogger
  File "C:\Users\mazo260d\mambaforge\envs\napari-latam\lib\site-packages\jupyter_events\__init__.py", line 3, in <module>
    from .logger import EVENTS_METADATA_VERSION, EventLogger
  File "C:\Users\mazo260d\mambaforge\envs\napari-latam\lib\site-packages\jupyter_events\logger.py", line 18, in <module>
    from .schema import SchemaType
  File "C:\Users\mazo260d\mambaforge\envs\napari-latam\lib\site-packages\jupyter_events\schema.py", line 7, in <module>
    from referencing import Registry
ModuleNotFoundError: No module named 'referencing'

I could not figure out what this referencing package does, but it should be installable with conda: https://anaconda.org/conda-forge/referencing
I tried installing it and also adding it to the .yml file, but then the environment does not solve.
Looking for: ['python=3.10', 'pip', 'jupyterlab', 'jupytext', 'notebook', 'matplotlib', 'scikit-image=0.21.0', 'jupyter-book=0.15.1', 'pooch=1.7.0', 'scikit-learn=1.2.2', 'ipywidgets=8.0.7', 'seaborn=0.12.2', 'napari=0.4.18', 'cookiecutter', 'cellpose', 'napari-animation', 'affinder', 'devbio-napari', 'pyqt', 'pyrsistent', 'referencing', 'napari-ome-zarr']

Could not solve for environment specs
Encountered problems while solving:
  - package jupyter-book-0.15.1-pyhd8ed1ab_0 requires sphinx-external-toc >=0.3.1,<0.4.0, but none of the providers can be installed

The environment can't be solved, aborting the operation

Any ideas how to fix that? @haesleinhuepf @jni

Thanks for looking into it! Yesterday I tried again setting up the environment (using micromamba) and then starting naparia within the devbio-napari-env. I can start the environment alright but then starting the assistant the computer works long in the background and then returns the following error:

I am on Mac with the M2pro apple silicon chip in case it might play a role - and I use the zsh console.

Hi @MakerTobey !
Hey, nice that is working now. We are trying to create a .yml file so that people do not need to install individual packages, let's see if we manage.

should I install this module in base?

No! If you already did it, I guess no big harm for now, but the only package we suggested to install in the base environment was mamba, but since you have micromamba now, there is no need for that anymore (cause it is already installed).
Also, @jni , for the windows instructions, is there a reason not to just download and install mambaforge like from here?

@zoccoler maybe remove the version pin on jupyter-book?

@zoccoler maybe remove the version pin on jupyter-book?

Nope, that didn't help, led me down a terrible rabbit hole... BUT, I can install referencing with pip at the end:
  - pip:
    - referencing

This uninstalls attrs 21 and installs attrs 23. 😬 Maybe it'll be ok? 😬 Can you test? 🙏

Also, @jni , for the windows instructions, is there a reason not to just download and install mambaforge like from here?

The reason I really like micromamba is that it does not depend on or create a base environment. It is actually quite easy to bork an environment, and if you bork your base environment you're in trouble. I was actually rather shocked to find instructions to install stuff directly into base in the original instructions. By using micromamba, though, you avoid all of that. The only cost, as far as I can tell, is that you might have to do something special to put micromamba into your path. (On macOS this problem is solved quite well.)

Let me know if I need to merge this request. I think you can do so yourself when you are ready, but from this exchange I get the impression that this is not yet fully tested and ready. Should I test something? Tomorrow I could try on a windows computer.

This uninstalls attrs 21 and installs attrs 23. 😬 Maybe it'll be ok? 😬 Can you test? 🙏

I tried and there is a different error now 😭 :

Error message
---------------------------------------------------------------------------
TypeError                                 Traceback (most recent call last)
File ~\mambaforge\envs\napari-latam\lib\site-packages\napari_assistant\_gui\_Assistant.py:303, in Assistant.to_notebook(self=<napari_assistant._gui._Assistant.Assistant object>, filename='C:/Users/mazo260d/Desktop/exported_notebook.ipynb', execute=True, use_napari=False)
    300 manager = WorkflowManager.install(self._viewer)
    301 code = manager.to_python_code(notebook=True, use_napari=use_napari)
--> 303 import jupytext
    305 # jython code is created in the jupytext light format
    306 # https://jupytext.readthedocs.io/en/latest/formats.html#the-light-format
    308 jt = jupytext.reads(code, fmt="py:light")

File ~\mambaforge\envs\napari-latam\lib\site-packages\jupytext\__init__.py:9
      6 from .version import __version__
      8 try:
----> 9     from .contentsmanager import build_jupytext_contents_manager_class
     10 except ImportError as err:
     11     build_jupytext_contents_manager = reraise(err)

File ~\mambaforge\envs\napari-latam\lib\site-packages\jupytext\contentsmanager.py:612
    607     return JupytextContentsManager
    610 try:
    611     # The LargeFileManager is taken by default from jupyter_server if available
--> 612     from jupyter_server.services.contents.largefilemanager import LargeFileManager
    614     TextFileContentsManager = build_jupytext_contents_manager_class(LargeFileManager)
    615 except ImportError:
    616     # If we can't find jupyter_server then we take it from notebook

File ~\mambaforge\envs\napari-latam\lib\site-packages\jupyter_server\services\contents\largefilemanager.py:7
      4 from anyio.to_thread import run_sync
      5 from tornado import web
----> 7 from jupyter_server.services.contents.filemanager import (
      8     AsyncFileContentsManager,
      9     FileContentsManager,
     10 )
     13 class LargeFileManager(FileContentsManager):
     14     """Handle large file upload."""

File ~\mambaforge\envs\napari-latam\lib\site-packages\jupyter_server\services\contents\filemanager.py:25
     22 from traitlets import Bool, Int, TraitError, Unicode, default, validate
     24 from jupyter_server import _tz as tz
---> 25 from jupyter_server.base.handlers import AuthenticatedFileHandler
     26 from jupyter_server.transutils import _i18n
     27 from jupyter_server.utils import to_api_path

File ~\mambaforge\envs\napari-latam\lib\site-packages\jupyter_server\base\handlers.py:23
     21 from jinja2 import TemplateNotFound
     22 from jupyter_core.paths import is_hidden
---> 23 from jupyter_events import EventLogger
     24 from tornado import web
     25 from tornado.log import app_log

File ~\mambaforge\envs\napari-latam\lib\site-packages\jupyter_events\__init__.py:3
      1 # flake8: noqa
      2 from ._version import __version__
----> 3 from .logger import EVENTS_METADATA_VERSION, EventLogger
      4 from .schema import EventSchema
      6 __all__ = ["__version__", "EVENTS_METADATA_VERSION", "EventLogger", "EventSchema"]

File ~\mambaforge\envs\napari-latam\lib\site-packages\jupyter_events\logger.py:18
     15 from traitlets import Dict, Instance, Set, default
     16 from traitlets.config import Config, LoggingConfigurable
---> 18 from .schema import SchemaType
     19 from .schema_registry import SchemaRegistry
     20 from .traits import Handlers

File ~\mambaforge\envs\napari-latam\lib\site-packages\jupyter_events\schema.py:18
     15     Validator = Any  # type:ignore
     17 from . import yaml
---> 18 from .validators import draft7_format_checker, validate_schema
     21 class EventSchemaUnrecognized(Exception):  # noqa
     22     """An error for an unrecognized event schema."""

File ~\mambaforge\envs\napari-latam\lib\site-packages\jupyter_events\validators.py:41
     35 resources = [
     36     DRAFT7.create_resource(each)
     37     for each in (EVENT_METASCHEMA, PROPERTY_METASCHEMA, EVENT_CORE_SCHEMA)
     38 ]
     39 METASCHEMA_REGISTRY: Registry = resources @ Registry()
---> 41 JUPYTER_EVENTS_SCHEMA_VALIDATOR = Draft7Validator(  # type: ignore
        EVENT_METASCHEMA = {'$schema': 'http://json-schema.org/draft-07/schema', '$id': 'http://event.jupyter.org/event-metaschema', 'version': 1, 'title': 'Event Metaschema', 'description': 'A meta schema for validating that all registered Jupyter Event\nschemas are appropriately defined.\n', 'type': 'object', 'properties': {'version': {'type': 'integer'}, 'title': {'type': 'string'}, 'description': {'type': 'string'}, 'properties': {'type': 'object', 'additionalProperties': {'$ref': 'http://event.jupyter.org/property-metaschema'}, 'propertyNames': {'pattern': '^(?!__.*)'}}}, 'patternProperties': {'\\$id': {'type': 'string', 'format': 'uri'}}, 'required': ['$id', 'version', 'properties']}
        METASCHEMA_REGISTRY = <Registry (3 uncrawled resources)>
        draft7_format_checker = <FormatChecker checkers=['date', 'date-time', 'email', 'hostname', 'idn-email', 'idn-hostname', 'ipv4', 'ipv6', 'json-pointer', 'regex', 'relative-json-pointer', 'time', 'uri', 'uri-reference', 'uri-template']>
     42     schema=EVENT_METASCHEMA,
     43     registry=METASCHEMA_REGISTRY,
     44     format_checker=draft7_format_checker,
     45 )
     47 JUPYTER_EVENTS_CORE_VALIDATOR = Draft7Validator(  # type: ignore
     48     schema=EVENT_CORE_SCHEMA,
     49     registry=METASCHEMA_REGISTRY,
     50     format_checker=draft7_format_checker,
     51 )
     54 def validate_schema(schema: dict) -> None:

TypeError: create.<locals>.Validator.__init__() got an unexpected keyword argument 'registry'

What I am trying to test this is the follwoing:

Open an image
Open the Assistant
Run some functions, like Label -> voronoi_ostu_labeling (clesperanto) (up to here it works fine!)
Click on Generate code > Export jupyter notebook like in here:

The reason I really like micromamba is that it does not depend on or create a base environment. It is actually quite easy to bork an environment, and if you bork your base environment you're in trouble. I was actually rather shocked to find instructions to install stuff directly into base in the original instructions. By using micromamba, though, you avoid all of that. The only cost, as far as I can tell, is that you might have to do something special to put micromamba into your path. (On macOS this problem is solved quite well.)

I see, I need to give it a try then! I just mentioned because the installation instructions are a bit more intimidating for non-programmers 😁
Should we debug this further or make 2 environments?

I think we should try to debug, 2 envs sounds painful 😂 I guess we don't actually need jupyter-book or jupytext in their environment (only to build the book), so let me try to remove those...

(a) this env works with assistant now, at least on mac
(b) this is the first time I use this functionality and holy shit 😂
(c) hang on a sec while I add affinder LOL

wait no I already added affinder 🤣 so this should be ready to merge once we get testing confirmed on Windows!

That works now! 🎉 🎉


DNS forwarding for virtual network gateway

Type of issue
Typo
Description
[Enter feedback here]
Page URL
https://learn.microsoft.com/en-us/dotnet/API/microsoft.azure.management.network.models.virtualnetworkgateway.enablednsforwarding?view=azure-dotnet
Content source URL
https://github.com/Azure/azure-docs-sdk-dotnet/blob/master/xml/Microsoft.Azure.Management.Network.Models/VirtualNetworkGateway.xml
Document Version Independent Id
0f16c61b-2428-6bc9-0f37-4aca311d72b3
Article author
@azure-sdk
Metadata

ID: ad21f69f-ebf4-a935-dceb-1eddac64b0d4
Service: virtual-network

Hi @dklwong.  Thanks for reaching out with your feedback.   The Microsoft.Azure.Management.Network package reached end-of-life in September 2023 and is no longer published nor supported by Microsoft.   Since these docs are automatically generated from the library source a package release is required to update them.   Unfortunately, this means that we're unable to correct the typo.


Bug keyboard manager

Microsoft PowerToys version
0.76.1
Installation method
Microsoft Store
Running as admin
None
Area(s) with issue?
Keyboard Manager
Steps to reproduce
If you restart the laptop, the reassigned keys do not work until you manually press on/off the keyboard manager function.
✔ Expected Behavior
I would like the key reassignment to always work if powertoys is enabled.
❌ Actual Behavior
No response
Other Software
No response

Same as above for me. Looks like the keyboard manager settings (default.json, settings.json) are stored in the wrong place.
Re-enabling the keyboard manager reads them, fixing the issue temporarily, but on program start these can't be found.
Expected location (assumed): \Users\user_name\AppData\Local\Microsoft\PowerToys\Keyboard Manager\
Actual location: \Users\AppData\Local\Microsoft\PowerToys\Keyboard Manager\

Hi there! Thanks for reporting this bug. I'm currently aggregating all of the similar bugs to help us track this moving forward -- please continue the conversation on the parent issue! /dup #28069


Alpaca

The primary aim is to implement enough of the language to evaluate what how well an ML type of language could become a practical language for writing code to be run on the beam.

https://github.com/alpaca-lang/alpaca

Thanks. I’m well aware of alpaca. The approach is different. Alpaca is a from the ground creation. Fez taps into a mature language and tooling ecosystem. Cheers.

You like to point this out officially?

@shalomshalom? Why? And where? This is completely unrelated.

The current text is misleading.

The primary aim is to implement enough of the language to evaluate what how well an ML type of language could become a practical language for writing code to be run on the beam.
This is already implemented and through that evaluated, yes?

I personally think it's not misleading. But sure you can always interpret
things differently.
Am 25.12.2017 18:44 schrieb "MatthiasSchuster"<EMAIL_ADDRESS>
The current text is misleading.
The primary aim is to implement enough of the language to evaluate what
how well an ML type of language could become a practical language for
writing code to be run on the beam.
This is already implemented and through that evaluated, yes?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/kjnilsson/fez/issues/25#issuecomment-353882229, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AADgNFh6Iq7V7ImyZokosFHCmfbF9XLdks5tD98LgaJpZM4RL-e5
.

I think the question about how well an ML could work on the beam is still unanswered and may never be answered by this particular project. But perhaps the project mission statement needs to be refined. In as much as something that started as an extended hack needs a mission statement at all.
We'll see what comes out of the next couple of months. Thanks for your input.


Use Laravel's "config" helper to get model's config

Use Laravel's "config" helper to get model's config (to retrieve all changes that might be done to config during app runtime)

Unfortunately, this presents an obstacle to fixing #980, since heavier reliance on Laravel's config() will mean more work to avoid breaking artisan config:cache. As Laravel currently stands, it can't handle anonymous functions in the config files when caching.


Fixed 'An unexpected error occurred' for the sample

The OAuth2 "Hello World" sample did not work with current Kong versions; apparently the enable_authorization_code setting defaulted to true at some point, but does not anymore.
This resulted in Kong returning An unexpected error occurred. when posting to the /oauth2/authorize endpoint; what you saw from this was simply that app.js crashed at line 87, not being able to parse that error string as JSON.
Other things contained in this PR:

Added semicolons to make jshint happy
Removed trailing spaces from the curl which creates the access tokens; on Mac OS X, these spaces lead to bash interpreting the backslashes as "escape", and not as the intended "continue" tokens.

@DonMartin76 thanks

Np


About How to save the adata_contact

I have successfully run the following code adata_concat = STAligner.train_STAligner(adata_concat, iter_comb = None, verbose=True, device=used_device, margin=1.0).
But, due to jupyter notebook can be unstable sometimes, I want to save the adata_contact timely and I ran
adata_concat.write(f"/spatial/Visium_STAligner_{today}.h5ad")
It caused some errors, and here's the details.
`Traceback (most recent call last):
File "/home/miniconda3/envs/STAligner/lib/python3.8/site-packages/anndata/_io/utils.py", line 209, in func_wrapper
return func(elem, key, val, *args, **kwargs)
File "/home/miniconda3/envs/STAligner/lib/python3.8/site-packages/anndata/_io/h5ad.py", line 148, in write_not_implemented
raise NotImplementedError(
NotImplementedError: Failed to write value for uns/edgeList, since a writer for type <class 'tuple'> has not been implemented yet.
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "/home/workshop/visium_STAligner.py", line 118, in
adata_concat.write(f"/spatial/0.Visium_STAligner_{today}.h5ad")
File "/home/miniconda3/envs/STAligner/lib/python3.8/site-packages/anndata/_core/anndata.py", line 1912, in write_h5ad
_write_h5ad(
File "/home/miniconda3/envs/STAligner/lib/python3.8/site-packages/anndata/_io/h5ad.py", line 118, in write_h5ad
write_attribute(f, "uns", adata.uns, dataset_kwargs=dataset_kwargs)
File "/home/miniconda3/envs/STAligner/lib/python3.8/functools.py", line 875, in wrapper
return dispatch(args[0].class)(*args, **kw)
File "/home/miniconda3/envs/STAligner/lib/python3.8/site-packages/anndata/_io/h5ad.py", line 130, in write_attribute_h5ad
_write_method(type(value))(f, key, value, *args, **kwargs)
File "/home/miniconda3/envs/STAligner/lib/python3.8/site-packages/anndata/_io/h5ad.py", line 294, in write_mapping
write_attribute(f, f"{key}/{sub_key}", sub_value, dataset_kwargs=dataset_kwargs)
File "/home/miniconda3/envs/STAligner/lib/python3.8/functools.py", line 875, in wrapper
return dispatch(args[0].class)(*args, **kw)
File "/home/miniconda3/envs/STAligner/lib/python3.8/site-packages/anndata/_io/h5ad.py", line 130, in write_attribute_h5ad
_write_method(type(value))(f, key, value, *args, **kwargs)
File "/home/miniconda3/envs/STAligner/lib/python3.8/site-packages/anndata/_io/utils.py", line 212, in func_wrapper
raise type(e)(
NotImplementedError: Failed to write value for uns/edgeList, since a writer for type <class 'tuple'> has not been implemented yet.
Above error raised while writing key 'uns/edgeList' of <class 'h5py._hl.files.File'> from /.`
I'd like to ask how I should save data correctly.
Looking forward to your reply. I would appreciate it!

@Sawakotx @t-a-m-i Hi. You can delete the key 'uns/edgeList' before saving h5ad file.
del adata_concat.uns['edgeList']


scope the removal of Quartz jobs upon Grails start to default group

This change allows adding Quartz jobs to the Grails Quartz plugin managed scheduler bypassing the plugin. This change mainly prevents the plugin from deleting these jobs when Grails is started.

This change is not needed anymore. We moved TGA away from the Grails Quartz plugin.


Bundle with tsup and replace babel-jest

Bundles code and some dependencies with tsup.
Replaces babel-jest with @swc/core. With swc tests should run faster than using babel.
Adds require.resolve for jest-junit and jest-serializer-html.
Adds support for esm only projects that don't use a custom config file.
Tested locally using test-storybook:ci commands and some projects that I have with storybook and test-runner.

📦 Published PR as canary version: 1.0.0--canary.224.3c57b66.0

:sparkles: Test out this PR locally via:
npm install<EMAIL_ADDRESS># or
yarn add<EMAIL_ADDRESS>

@yannbf Can you check this?

@yannbf What do you think of these changes?

Hey @bryanjtc thanks for your contribution! Sorry, thing have been busy with SB beta. We'll take a look!

Just some finer questions/points really. Looks really good, in fact, @bryanjtc I'd love to get that @swc/jest change in the storybook monorepo some day too.
FYI: I have a chain or PRs on there removing babel: (all except for unit test 👎 ) (and code-mods 👍 )
https://github.com/storybookjs/storybook/pull/20156

@yannbf Is there no CI set up for this project?

@yannbf Is there no CI set up for this project?

There is, I guess it doesn't run on forks? I'll take a look at this tomorrow

@yannbf Is there no CI set up for this project?

There is, I guess it doesn't run on forks? I'll take a look at this tomorrow

The pr needs a label for the ci to run. Can you add it?

I don't know what labels to apply to make the right things happen 😞

@yannbf Any update on getting ci to work?

@yannbf is this supposed to work:
[SB] ERR! Module not found: Error: Can't resolve './stories/stress-test' in '/home/runner/work/test-runner/test-runner'
[SB] ERR! ModuleNotFoundError: Module not found: Error: Can't resolve './stories/stress-test' in '/home/runner/work/test-runner/test-runner'

Codecov Report
Base: 75.86% // Head: 76.13% // Increases project coverage by +0.27% :tada:

Coverage data is based on head (2b54320) compared to base (87eb771).
Patch coverage: 77.77% of modified lines in pull request are covered.

Additional details and impacted files
@@            Coverage Diff             @@
##             next     #224      +/-   ##
==========================================
+ Coverage   75.86%   76.13%   +0.27%
==========================================
  Files          11       11
  Lines         174      176       +2
  Branches       36       36
==========================================
+ Hits          132      134       +2
  Misses         42       42

Impacted Files
Coverage Δ

src/csf/transformCsf.ts
84.61% <ø> (ø)

src/util/getCliOptions.ts
60.00% <71.42%> (+4.44%)
:arrow_up:

src/playwright/transformPlaywrightJson.ts
94.28% <100.00%> (ø)

src/util/getParsedCliOptions.ts
5.88% <100.00%> (ø)

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.

I enabled some ci workflows for pull requests and modified them to run in node 16 and 18. http-server doesn't work with node 18, so I replaced it with serve. Snapshots were updated, nothing major, it just removed some empty lines.

Hey @bryanjtc thank you for all you work in this! I am currently on holidays, so I'll be checking this thoroughly once I'm back next week, I hope you don't mind!

Hey @bryanjtc I took a quick look, and to make a proper canary release I made another branch off of this one, but somehow that made this fork be able to release as well, but given this PR had "major" in it, it made a 1.0.0 version 🤦
With a canary available (and subsequent, as you make new pushes to this branch), let's test it out in our projects.
When testing, the binary did not exist anymore, so I got Command "test-storybook" not found when running yarn test-storybook in a project which was previously working.
I like what you did to the test-storybook.js file, but unfortunately it's not so easily understood when inspecting it via node_modules and easily modifiable so people could try quick fixes. But I guess that's expected if we want to support cjs/esm. Maybe if the prebundled code came from a vendors file, it would still be relatively simple to understand 🤔

Node should be able to find the bin file without extension. By default it should use test-storybook.js and for ESM only projects test-storybook.mjs. When specifying the extension, ESM projects expect test-storybook.js to be esm code. There are two solutions for this, changing the extension to .cjs or not specifying the extension. I can undo the prebundling for the dependencies of test-storybook.ts, so that it can be easier to read and modify in node_modules.

@yannbf let's discuss this Monday?

Any update on this?

Any issues trying to re-create the pr? @yannbf

This looks great!
@ndelangen will add you to the Storybook organization, and @yannbf will redo the PR to fix the CI issue.

I'll re-open this PR

done:
https://github.com/storybookjs/test-runner/pull/250


Use an existing GoogleAuth Instance

It's currently possible to instantiate a CRM client with a RefreshTokenClient (from GoogleAuth library):
const GoogleCloudResourceManager = require('@google-cloud/resource');
const crm = new GoogleCloudResourceManager({
  credentials: {
    type: 'authorized_user',
    client_id: gapiClientId,
    client_secret: gapiClientSecret,
    refresh_token: refreshToken
  }
});
crm.getProjects()

Under the hood, this will instantiate a GoogleAuth client.
In my project, I am calling multiple Google APIs and already have an instance of GoogleAuth. I want to avoid having multiple instances of GoogleAuth clients / multiple sources of truth as that would lead to redundant network requests for access tokens.
Intuitively, I tried this:
const GoogleCloudResourceManager = require('@google-cloud/resource');
const crm = new GoogleCloudResourceManager({
  credentials: {
    type: 'authorized_user',
    client_id: gapiClientId,
    client_secret: gapiClientSecret,
    refresh_token: 'dummy value'
  }
});
crm.authClient = new GoogleAuth(...);
crm.getProjects()

This does not work. getProjects() actually calls makeAuthenticatedRequest, which has in its closure the original authClient (with refresh_token: 'dummyValue') at the time the CRM client was instantiated.
My goal is to avoid having CRM's auth client make a redundant network request for an access token, given that I already have a fresh access token. I'd like to interface with the CRM library to achieve this in one of two ways:

replace the authClient used by getProjects with a existing shared instance.
Set access token on each getProjects call, and have my program own the responsibility of token management

This issue was moved to googleapis/nodejs-common#281


Custom report builder trouble

Squid3 Version: 1.10.6
Java Version: 1.8.0_361
JavaFX Version: 8.0.361-b09
OS: Windows 10 10.0
Issue details:
When creating a new report or modifying a copy of an existing one, I can create a new category, but cannot seem to populate it with any expressions.  I can drag expressions into categories that already have expressions in them, but not into empty ones.  This does not seem to be associated with any particular data file.

This bug was introduced in v1.10.2 .  Fixed soon.

@TPestaj  - this was a side-effect of drag n drop files.  Fixed in next release.


Select box should allow option to have nothing selected by default rather than the first enum in the list

When user has not chosen an item in a select box, the select box starts off with the first item selected.
If we want the form to send updates on "change" instead of "submit", and a user wishes to select the first item, the user has to change the selection twice to get a change event to fire with the choice they actually want.
The solution we propose is to have the first item in the select box be blank instead of selecting an item to start with. Once a user has made a choice the blank item could be removed from the list.
version: 0.38.0

The solution we propose is to have the first item in the select box be blank instead of selecting an item to start with.

You could indeed prepend an empty choice to the enum.

Once a user has made a choice the blank item could be removed from the list.

Not sure about that. Let's leave it among the choices so that the submitted value can be emtpy if necessary.

Once a user has made a choice the blank item could be removed from the list.

Not sure about that. Let's leave it among the choices so that the submitted value can be emtpy if necessary.

I can't see why would we want to give the user the ability to revert their choice back to an invalid option.  The value, once chosen, must be one of the enumerated choices.  To put it another way, the input begins in an unchosen state (always invalid), and then progresses to a chosen state (always valid), but never back.

The value, once chosen, must be one of the enumerated choices.

I see, this applies to field were the value is mandatory. I was thinking of optional fields sorry.
The feature makes sense, don't hesitate to draft a PR!


[BugFix] Find wrong fe when when modifying the host of a fe node.

What type of PR is this：

[x] BugFix
[ ] Feature
[ ] Enhancement
[ ] Refactor
[ ] UT
[ ] Doc
[ ] Tool

Which issues of this PR fixes ：

Fixes #14706
Problem Summary(Required) ：

Find wrong fe when when modifying the host of a fe node.
Checklist:

[ ] I have added test cases for my bug fix or my new feature
[ ] This pr will affect users' behaviors
[ ] This pr needs user documentation (for new or modified features or behaviors)

[ ] I have added documentation for my new feature or new function

Bugfix cherry-pick branch check:

[x] I have checked the version labels which the pr will be auto backported to target branch

[x] 2.5
[x] 2.4
[ ] 2.3
[ ] 2.2

run starrocks_fe_unittest

run starrocks_fe_unittest

[FE PR Coverage Check]
:heart_eyes: pass : 4 / 5 (80.00%)
file detail

path
covered_line
new_line
coverage
not_covered_line_detail

:large_blue_circle:
com/starrocks/server/NodeMgr.java
4
5
80.00%
[742]

run starrocks_admit_test

@Mergifyio backport branch-2.5

@Mergifyio backport branch-2.4

run starrocks_admit_test


As the owner, I cannot edit the Room name (as shown in the pic)   I tried 3 times and it didn't allow me to change the name. I didn't refresh. After 10 minutes, it worked.                 ![QQ20240408-210859@2x.png](https://files.boardx.us/beBT5B83vbXnsw7R5/anu9hwaYKucGwPAX3/A666sYjJvhzB4awL3/images/sm

As the owner, I cannot edit the Room name (as shown in the pic)

userAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/<IP_ADDRESS> Safari/537.36
email<EMAIL_ADDRESS>username: xiaodanzhang

Cannot reproduce this issue.
I can modify the Room Name now


Fix package restore after failed update

When updating a package, C5 first makes a backup in the trash directory and puts the backup directory's path in the package object's variable $this->backedUpFname.
Later, if updating fails, C5 attempts to restore the package from the backup.
The problem is $this->backedUpFname returns an empty value and the package is not restored breaking C5.
This fixes the restore system by returning the package after backup so we can access $this->backedUpFname

Small change, but darn useful. Thank God my updates don't fail though ;)


History back should restore scroll position (with loaded stories on chat scene)

redux is probably needed for this task

Loaded stories now supported through redux state. Need to figure out how to make the restore scroll vs. scroll top flow work properly


Fix: wrap web3Provider.eth.getCode in a try-catch

What it solves
Resolves #2675
How this PR fixes it
web3Provider.eth.getCode does checksum validation internally and can throw if the address is invalid. So I wrapped it in a try-catch.
How to test it
The particular edge case when it throws is very hard to reproduce, so let's just verify that the wallet connection still works like before. Especially with WalletConnect and a Safe as a wallet.

Thanks, will remove the test code.
Reg. the invalid address, I suspect it's coming as an empty string from this fallback: https://github.com/gnosis/safe-react/blob/dev/src/logic/wallets/getWeb3.ts#L72

Reg. the invalid address, I suspect it's coming as an empty string from this fallback:

I think we can also fall back to the zero address. Also, I just realized that on line 77 const available = account !== null will always evaluate to true because we don't return null anymore

I think we can also fall back to the zero address. Also, I just realized that on line 77 const available = account !== null will always evaluate to true because we don't return null anymore

It's better not to do a request at all if no address is set. null is still being returned as far as I can see, on line 51.

It's better not to do a request at all if no address is set

Yup, maybe an early return will help

null is still being returned as far as I can see, on line 51.

Yep, but we default it to an empty string in this function.


bump flumedb version

to bring in the fixes from flumedb/flumedb#7
(this is pre 1.0 so even with the ^, it is fixed at 0.2.x)
@dominictarr

merged into 16.3.6


Unable to run application

While running the canny edge application in live mode, i'm getting this error
Failed to remove kernel[0]=org.khronos.extra.edge_trace
Failed to remove kernel[1]=org.khronos.extra.euclidean_nonmaxsuppression_harris
Failed to remove kernel[2]=org.khronos.extras.harris_score
Failed to remove kernel[3]=org.khronos.extras.laplacian3x3
Failed to remove kernel[4]=org.khronos.extras.image_to_list
Failed to remove kernel[5]=org.khronos.extra.nonmaximasuppression
Failed to remove kernel[6]=org.khronos.extra.elementwise_norm
Failed to remove kernel[7]=org.khronos.extras.scharr3x3
Failed to remove kernel[8]=org.khronos.extras.sobelMxN

Working with Opencv 3.3.1 earlier I was having Opencv 3.2.0

sorry to open this , but i am facing this error on rpi , i am having opencv 3.4.1. How did u resolve this ?

@thrylos2307 Please refer this steps

I am facing the same error in R-pi + there is another error

It is working fine with local images , but accessing live camera is becoming the problem .

@kaki-epithesi

Is the live camera working?
Check your Opencv Version?

@kaki-epithesi

Is the live camera working?
Check your Opencv Version?

1> live camera is working
2> opencv version 3.41.

@kaki-epithesi Can you try with opencv 3.3.1?

@kaki-epithesi Can you try with opencv 3.3.1?

i will get to that .


Add tags to paths in ocpaths.proto.

This change allows paths to be tagged with arbitrary criteria that allow for grouping or other identification of a path within a list.

Pull Request Functional Test Report for #2479 / 3790fcfb4fce8be6670867bddb5f2429cf2f18a7
No tests identified for validation.
Help

We should skip the proto directory for static analysis checks in this repo, I think.


DOC: update the author name mapping

@vanpact @Sebascn @mamrehn @cel4 @chemelnucfin  Do you want to tell me your full name so that we can properly attribute your contributions in the release notes?
@person142 @drpeteb your git/github handles only have your first names. If you want to be credited with a full name, please let me know

My full name is "Sebastian Skoupý". Thanks a lot! :)

At the moment I am not really interested in revealing my true identity. As there is not really a big contribution from my side, I think it makes sense to simply drop me from the contributors list.

Hi Evgeni,
Ya, my contribution is not that significant.  Wait until I have more
significant ones.  :)
Thanks.
On Fri, Nov 13, 2015 at 12:44 PM, cel4<EMAIL_ADDRESS>wrote:

At the moment I am not really interested in revealing my true identity. As
there is not really a big contribution from my side, I think it makes sense
to simply drop me from the contributors list.
—
Reply to this email directly or view it on GitHub
https://github.com/scipy/scipy/pull/5496#issuecomment-156551293.

My first name is "Yves-Rémi" and my family name is "Van Eycke". :)
Thanks!
On Fri, Nov 13, 2015 at 11:50 PM, chemelnucfin<EMAIL_ADDRESS>wrote:

Hi Evgeni,
Ya, my contribution is not that significant. Wait until I have more
significant ones. :)
Thanks.
On Fri, Nov 13, 2015 at 12:44 PM, cel4<EMAIL_ADDRESS>wrote:

At the moment I am not really interested in revealing my true identity.
As
there is not really a big contribution from my side, I think it makes
sense
to simply drop me from the contributors list.
—
Reply to this email directly or view it on GitHub
https://github.com/scipy/scipy/pull/5496#issuecomment-156551293.

—
Reply to this email directly or view it on GitHub
https://github.com/scipy/scipy/pull/5496#issuecomment-156581283.

Josh Wilson; thanks.

Pete Bunch.
Thank you!

TravisCI failure was an unrelated VM timeout.

Merging, thanks Evgeni!


[BUG] Backup Taken With Rancher Backups Operator That Include RKE2 Downstream Clusters Should Be Able to Be Used For More Than One Migration

Rancher Server Setup

Rancher version: v2.6.11-rc9 // v2.6-head ID: ec67e31
Installation option (Docker install/Helm Chart): Helm

Information about the Cluster

Kubernetes version: v1.24.10+rke2r1
Cluster Type (Local/Downstream): Downstream

If downstream, what type of cluster? (Custom/Imported or specify provider for Hosted/Infrastructure Provider): EC2

Describe the bug
When using the backup/restore operator to restore a backup onto a new cluster (migrating to new cluster), if there's RKE2 cluster info in the backup file then upon restoration the redeploySystemAgentGeneration field is incremented. So, going from HA1 -> HA2 will set redeploySystemAgentGeneration: 1
That said, if you either change nothing before migrating or if you need to migrate again using the same backup, the RKE2 cluster will not come back into an Active status because the redeploySystemAgentGeneration field is still set to 1 when it's expected to be 2 now.
To Reproduce

HA1 -> HA2, backup file b1
HA2 -> HA3, backup file b1

HA1 -> HA2, backup file b1
HA2 -> HA3, backup file b2 (new backup from HA2)

Result

Successful restore, redeploySystemAgentGeneration: 1
Unsuccessful restore, redeploySystemAgentGeneration: 1

Successful restore, redeploySystemAgentGeneration: 1
Successful restore, redeploySystemAgentGeneration: 2

Expected Result
RKE2 cluster comes back to Active status regardless of how many times the same backup has been used for migrations
SURE-6250

As described in the original issue, we have an issue with the redeploySystemAgentGeneration value when performing multiple restores with the same backup file. For posterity, the method we use to manage the rancher-system-agent on the downstream clusters is described here: https://github.com/rancher/rancher/issues/40819#issuecomment-1463015660
There is definitely a use case where we would want to be able to use the same backup for multiple restores, thinking in the situation where we have a semi-successful restore. For now I believe we can document the expected behavior with using the same backup file on multiple clusters, but for a more comprehensive solution we could look at moving to a user-defined hash on the cluster object that would be used to invalidate the system-agent upgrade plan on the downstream cluster. The backup-restore-operator could set this hash to something random (or, maybe even a hash of the current date with a random character to really ensure uniqueness). An issue I see with this is that it would not be a method compatible with older versions of Rancher.

@Oats87 If I understand correctly, you want the redeploySystemAgentGeneration field to be incremented in the case that the same backup file is used twice on two different clusters?

Thinking about this some more, we might actually be able to fix this on the Rancher side (with versions newer than the Q2 release of v2.7.x).
We use a secret that is created in the downstream cluster to trigger system-upgrade-controller to run the manage-system-agent plan. This secret only exists if the generation is != 0.
I'm thinking that we can add an additional field to this secret if generation != 0, containing the UID of the cluster object (which will be unique for every install/restore of Rancher). This should guarantee that the plan will run every time the backup is restored into a NEW Rancher cluster.

I did a test run for this fix and I ran into some errors that fixed themselves after 20 minutes, and the RKE2 cluster came back up and seems to be running fine.
The first error is one I've been seeing for a while and takes about five minutes to clear up and move on to the next set of actions:

The second set of errors were saying that 2/3 etcd nodes are failing and inactive:

Clicking into the cluster you can see a different set of errors:

Talking with @Oats87 about it, it seems the api server was missing:
E0509 19:36:45.698400  169993 kubelet_node_status.go:92] "Unable to register node with API server" err="Post \"https://<ip-address>/api/v1/nodes\": dial tcp <ip-address>: connect: connection refused" node="nick-rke2-e-0608003e-r978w
Not sure if we wanna keep this ticket open to track these errors and the fixes or if they should be new tickets since the issue outlined in this ticket seems to be fixed once these errors self-resolve.

Pass verified in rancher 2.7-head commit ID 1eb478f

rancher rke2 local cluster
created a backup with added resources (users, roles)
deleted resources
successfully restored from backup
deleted resources
successfully restored form same backup


Enable input conversion from f8 to f16

added DataTypeA, DataTypeB to specify different type for input conversions
added conversion logic from f8 to f16
fixed incorrect type for C,D in signature
added test cases for input data conversions

Could you please reference the source of the code? Thanks.

I do not know why 90a extended test failed...
I could not reproduce it locally.
I will re-run extended test again....

I do not know why 90a extended test failed... I could not reproduce it locally. I will re-run extended test again....

All extended tests passed this time.

Closing this for now.


add uai

@Fadhilgva First stage of verification passed, official domain is uai.ac.id as far as I verified. This is just an informational note. Pull request is still in the review. I appreciate your patience while waiting for the final decision.

@Fadhilgva Thank you for your patience while waiting for a review and processing your request. Pull request merged.


Fixed Shader editor single-line comment highlight

Fixes #40798
This PR solves single-line comment highlighting by setting the CodeHighlighter::add_color_region p_line_only parameter to true for single-line comments, as well as reintroducing the solution from 3.2 where ColorRegion.line_only is automatically set to true if there is no end_key symbol.
The second piece to the fix (checking if p_end_key is empty) is redundant, but I decided to include the check anyways.

Updated PR to include visual shader comment highlighting for consistency.

Commits have been squashed.

Thanks!


Write unit tests for CorePublisher and CoreSubscriber

Now that CorePublisher and CoreSubscriber have no Android dependencies (such as Context) we can easily write unit tests for them.
The tests ideally should exercise each of the available Events that can be sent to the CorePublisher and CoreSubscriber. However, because the cores' state is kept inside them and isn't exposed anywhere, it may be a difficult task. If we won't find any good testing solution then we might consider moving the state and events processing to a separate class that will be used in cores and is easily testable.
┆Issue is synchronized with this Jira Task by Unito

After the worker queue refactoring we have replaced Events with Workers that already have unit tests written for them. But there's still untested logic in both CorePublisher and CoreSubscriber that we can test.


5.11 stable release: 5.11.47

Seems 5.11.47 moved to stable channel 6 days ago.
Thanks for the great work. 👍

5.11.48 moved to stable now ;)

New UI community "feature" strikes again... UBNT has been changing the existing sc/rc posts to stable when things are released. 5.11.47 went stable yesterday afternoon - https://community.ui.com/releases/UniFi-Network-Controller-5-11-47/bc6b27a7-ada4-4cb5-a162-c659ed755a9f#comment/66085c53-948b-43d0-8938-28a51d8ad86a
Unfortunately when they do this it doesn't trigger any release notifications, and also makes it confusing to determine when things were actually released.
Latest commit updates 5.11 / latest to v5.11.47. Builds should be complete on Docker Cloud in ~1h after this comment.


Add dockerfile for console plugin

Could we re-use the Dockerfile on the root of this git repo ?

Ya its almost same
but we add some labels and all
and also the component which is coming from hack repo alwasy points to openshift folder so

/test images

/test images

The Dockerfile is also referenced by the prow build, and this is probably why ci/prow/images fails 😅

The Dockerfile is also referenced by the prow build, and this is probably why ci/prow/images fails 😅

:thinking:
how to fix this

@savitaashture symbolic link or duplicate ?

@savitaashture symbolic link or duplicate ?

I mistakenly deleted original Dockerfile from root directory
added back now lets see

@savitaashture that works 😉
/approve
/lgtm


comment blocks

we currently handle comment lines correctly, but don't do anything with comment blocks
https://docs.asciidoctor.org/asciidoc/latest/comments/#comment-blocks

completed in 7993646 and 3fa157b


steamcmd: init at 20180104

Motivation for this change
Package the steamcmd utility for NixOS.
Curiously, steamcmd.sh and its libraries must reside in a Steam root such that it can overwrite itself at runtime. So I've adapted the debian wrapper which basically copies the system install over to the user's Steam root if it doesn't exist.
An interesting possibility could be to use this tool to install Steam games to the Nix store. It would be of limited use for packaging, however, because Steam games aren't versioned.
Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option build-use-sandbox in nix.conf on non-NixOS)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[x] Fits CONTRIBUTING.md.

No attempt on x86_64-linux (full log)
The following builds were skipped because they don't evaluate on x86_64-linux: steamcmd
Partial log (click to expand)

a) For `nixos-rebuild` you can set
  { nixpkgs.config.allowUnfree = true; }
in configuration.nix to override this.

b) For `nix-env`, `nix-build`, `nix-shell` or any other Nix command you can add
  { allowUnfree = true; }
to ~/.config/nixpkgs/config.nix.

No attempt on aarch64-linux (full log)
The following builds were skipped because they don't evaluate on aarch64-linux: steamcmd
Partial log (click to expand)

a) For `nixos-rebuild` you can set
  { nixpkgs.config.allowUnfree = true; }
in configuration.nix to override this.

b) For `nix-env`, `nix-build`, `nix-shell` or any other Nix command you can add
  { allowUnfree = true; }
to ~/.config/nixpkgs/config.nix.

I tried this branch as-is and it worked perfectly for my needs.  I was able to install and run a viable Arma 3 server.
I'd love to see this merged and I will happily test any updates to this PR.  When merged, I'd love to also have it in release-18.03 if at all possible.

@goertzenator Unfortunately, this package is likely to break once they update the steamcmd installer, since it is not versioned. I've reported an issue here: https://github.com/ValveSoftware/steam-for-linux/issues/5447

That is unfortunate, but it doesn't need to be a deal breaker. Spideroak is in the same boat and the strategy for NixOs and Arch is to just stay on top of updates.  Furthermore, the tarball from Janurary 4 worked for me on May 20, so churn seems to be low.

@matthewbauer Updated.

No attempt on aarch64-linux (full log)
The following builds were skipped because they don't evaluate on aarch64-linux: steamcmd
Partial log (click to expand)

a) For `nixos-rebuild` you can set
  { nixpkgs.config.allowUnfree = true; }
in configuration.nix to override this.

b) For `nix-env`, `nix-build`, `nix-shell` or any other Nix command you can add
  { allowUnfree = true; }
to ~/.config/nixpkgs/config.nix.

No attempt on x86_64-linux (full log)
The following builds were skipped because they don't evaluate on x86_64-linux: steamcmd
Partial log (click to expand)

a) For `nixos-rebuild` you can set
  { nixpkgs.config.allowUnfree = true; }
in configuration.nix to override this.

b) For `nix-env`, `nix-build`, `nix-shell` or any other Nix command you can add
  { allowUnfree = true; }
to ~/.config/nixpkgs/config.nix.

Cross-ref: https://discourse.nixos.org/t/nix-ifying-steam-depots-for-dedicated-game-servers/284/6?u=vcunat

@matthewbauer Anything else need to be changed at this point, or should we close this due to lack of a versioned source?

This no longer seems to work due to some dependency breakage.  Maybe a rebase on the current tree would help?
I still use this.  If the above problem is trivial I'd love to see this merged.

@goertzenator Rebased, seems to build fine.

No attempt on x86_64-linux (full log)
The following builds were skipped because they don't evaluate on x86_64-linux: steamcmd
Partial log (click to expand)

a) For `nixos-rebuild` you can set
  { nixpkgs.config.allowUnfree = true; }
in configuration.nix to override this.

b) For `nix-env`, `nix-build`, `nix-shell` or any other Nix command you can add
  { allowUnfree = true; }
to ~/.config/nixpkgs/config.nix.

No attempt on aarch64-linux (full log)
The following builds were skipped because they don't evaluate on aarch64-linux: steamcmd
Partial log (click to expand)

a) For `nixos-rebuild` you can set
  { nixpkgs.config.allowUnfree = true; }
in configuration.nix to override this.

b) For `nix-env`, `nix-build`, `nix-shell` or any other Nix command you can add
  { allowUnfree = true; }
to ~/.config/nixpkgs/config.nix.


:bug: Report actual input for when union was expected.

In case the union is empty, we will always fail. Hence, we should know what the actual input was.

:tada: This PR is included in version 1.1.1-alpha.1 :tada:
The release is available on:

npm package (@alpha dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Fork-ts-checker-webpack-plugin does not seem use the plugins in the tsconfig.json

Current behavior
webpack compiles successfully, but fails to check css module when building.
TS2307: Cannot find module './index.module.less' or its corresponding type declarations.
Expected behavior
Can successfully check the css module
Steps to reproduce the issue

Project's tsconfig.json configuration :

"plugins": [{
      "name": "typescript-plugin-css-modules",
      "options": {
        "customMatcher": "*.module.(c|le|sc)ss$"
      }
    }],

webpack configuration:

new ForkTsCheckerWebpackPlugin({
         async: false,
         typescript: {
           configFile: path.join(process.cwd(), 'tsconfig.json'),
           configOverwrite: {
             include: [options.packageDir],
           },
           diagnosticOptions: {
             semantic: true,
             syntactic: true,
           },
         },
       })

Issue reproduction repository

Environment

fork-ts-checker-webpack-plugin: 7.2.3
typescript: 4.7.3
eslint: 6.8.0
webpack: 5.70.0
os: CentOS Linux release 7.2

Unfortunately, TypeScript plugins are supported only in a language service API. I created an issue in TypeScript repo to support plugins in other APIs: https://github.com/microsoft/TypeScript/issues/38736
It seems that TypeScript team has other priorities - my proposal is 2 years old and there is no update.
This plugin supports the same features as tsc - so this behaviour is sadly expected :/