calico - Getting the dependencies from go list failed

Running license_finder report on calico fails.
License Finder Version: 7.0.1
Error:
LicenseFinder::GoModules: is active
GO111MODULE=on go list -mod=readonly -deps -f '{{ if and (.DepOnly) (.Module) (not .Standard) }}{{ $mod := (or .Module.Replace .Module) }}{{ $mod.Path }},{{ $mod.Version }},{{ or $mod.Dir .Dir }}{{ end }}' ./...: did not succeed.
GO111MODULE=on go list -mod=readonly -deps -f '{{ if and (.DepOnly) (.Module) (not .Standard) }}{{ $mod := (or .Module.Replace .Module) }}{{ $mod.Path }},{{ $mod.Version }},{{ or $mod.Dir .Dir }}{{ end }}' ./...: Getting the dependencies from go list failed
	package github.com/projectcalico/calico/cni-plugin/internal/pkg/utils/winpol
	imports github.com/projectcalico/calico/cni-plugin/internal/pkg/utils/hcn: build constraints exclude all Go files in /Users/carlo.wahlstedt/temp-chg/calico/cni-plugin/internal/pkg/utils/hcn
package github.com/projectcalico/calico/felix/dataplane/windows
	imports github.com/projectcalico/calico/felix/dataplane/windows/hcn: build constraints exclude all Go files in /Users/carlo.wahlstedt/temp-chg/calico/felix/dataplane/windows/hcn
package github.com/projectcalico/calico/felix/dataplane/windows
	imports github.com/projectcalico/calico/felix/dataplane/windows/hns: build constraints exclude all Go files in /Users/carlo.wahlstedt/temp-chg/calico/felix/dataplane/windows/hns
package github.com/projectcalico/calico/node/cmd/calico-node
	imports github.com/projectcalico/calico/node/cmd/calico-node/bpf: build constraints exclude all Go files in /Users/carlo.wahlstedt/temp-chg/calico/node/cmd/calico-node/bpf
package github.com/projectcalico/calico/node/cmd/calico-node
	imports github.com/projectcalico/calico/node/pkg/lifecycle/startup
	imports github.com/projectcalico/calico/node/pkg/lifecycle/startup/autodetection/ipv4: build constraints exclude all Go files in /Users/carlo.wahlstedt/temp-chg/calico/node/pkg/lifecycle/startup/autodetection/ipv4
package github.com/projectcalico/calico/node/cmd/calico-node
	imports github.com/projectcalico/calico/node/pkg/nodeinit: build constraints exclude all Go files in /Users/carlo.wahlstedt/temp-chg/calico/node/pkg/nodeinit

/usr/local/Cellar/licensefinder/7.0.1/libexec/gems/license_finder-7.0.1/lib/license_finder/package_managers/go_modules.rb:63:in `block in packages_info': Command 'GO111MODULE=on go list -mod=readonly -deps -f '{{ if and (.DepOnly) (.Module) (not .Standard) }}{{ $mod := (or .Module.Replace .Module) }}{{ $mod.Path }},{{ $mod.Version }},{{ or $mod.Dir .Dir }}{{ end }}' ./...' failed to execute (RuntimeError)
	from /usr/local/Cellar/licensefinder/7.0.1/libexec/gems/license_finder-7.0.1/lib/license_finder/package_managers/go_modules.rb:32:in `chdir'
	from /usr/local/Cellar/licensefinder/7.0.1/libexec/gems/license_finder-7.0.1/lib/license_finder/package_managers/go_modules.rb:32:in `packages_info'
	from /usr/local/Cellar/licensefinder/7.0.1/libexec/gems/license_finder-7.0.1/lib/license_finder/package_managers/go_modules.rb:20:in `current_packages'
	from /usr/local/Cellar/licensefinder/7.0.1/libexec/gems/license_finder-7.0.1/lib/license_finder/package_manager.rb:105:in `current_packages_with_relations'
	from /usr/local/Cellar/licensefinder/7.0.1/libexec/gems/license_finder-7.0.1/lib/license_finder/scanner.rb:42:in `each'
	from /usr/local/Cellar/licensefinder/7.0.1/libexec/gems/license_finder-7.0.1/lib/license_finder/scanner.rb:42:in `flat_map'
	from /usr/local/Cellar/licensefinder/7.0.1/libexec/gems/license_finder-7.0.1/lib/license_finder/scanner.rb:42:in `active_packages'
	from /usr/local/Cellar/licensefinder/7.0.1/libexec/gems/license_finder-7.0.1/lib/license_finder/core.rb:84:in `current_packages'
	from /usr/local/Cellar/licensefinder/7.0.1/libexec/gems/license_finder-7.0.1/lib/license_finder/core.rb:79:in `decision_applier'
	from /System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/lib/ruby/2.6.0/forwardable.rb:224:in `acknowledged'
	from /usr/local/Cellar/licensefinder/7.0.1/libexec/gems/license_finder-7.0.1/lib/license_finder/license_aggregator.rb:51:in `block in aggregate_packages'
	from /usr/local/Cellar/licensefinder/7.0.1/libexec/gems/license_finder-7.0.1/lib/license_finder/license_aggregator.rb:49:in `each'
	from /usr/local/Cellar/licensefinder/7.0.1/libexec/gems/license_finder-7.0.1/lib/license_finder/license_aggregator.rb:49:in `flat_map'
	from /usr/local/Cellar/licensefinder/7.0.1/libexec/gems/license_finder-7.0.1/lib/license_finder/license_aggregator.rb:49:in `aggregate_packages'
	from /usr/local/Cellar/licensefinder/7.0.1/libexec/gems/license_finder-7.0.1/lib/license_finder/license_aggregator.rb:11:in `dependencies'
	from /usr/local/Cellar/licensefinder/7.0.1/libexec/gems/license_finder-7.0.1/lib/license_finder/cli/main.rb:159:in `report'
	from /usr/local/Cellar/licensefinder/7.0.1/libexec/gems/thor-1.2.1/lib/thor/command.rb:27:in `run'
	from /usr/local/Cellar/licensefinder/7.0.1/libexec/gems/thor-1.2.1/lib/thor/invocation.rb:127:in `invoke_command'
	from /usr/local/Cellar/licensefinder/7.0.1/libexec/gems/thor-1.2.1/lib/thor.rb:392:in `dispatch'
	from /usr/local/Cellar/licensefinder/7.0.1/libexec/gems/thor-1.2.1/lib/thor/base.rb:485:in `start'
	from /usr/local/Cellar/licensefinder/7.0.1/libexec/gems/license_finder-7.0.1/bin/license_finder:6:in `<top (required)>'
	from /usr/local/Cellar/licensefinder/7.0.1/libexec/bin/license_finder:23:in `load'
	from /usr/local/Cellar/licensefinder/7.0.1/libexec/bin/license_finder:23:in `<main>'

Steps to reproduce:

Run: git clone https://github.com/projectcalico/calico
Inside the calico dir run: license_finder report

Hey @carlowahlstedt ! It looks liek there is a go version mismatch. The docker image actually uses 1.14.3 which is quite old! We should probably upgrade that but in the mean time you can run something like wget https://dl.google.com/go/go1.18.linux-amd64.tar.gz && tar -xvf go1.18.linux-amd64.tar.gz && rm -rf /go && mv go / && rm go1.18.linux-amd64.tar.gz to get this working!

Just tried it and latest version of go does indeed work for me! Thanks for looking into it!


[FlexFields] Rule set does not seem to work correctly

Hello, I'm testing out your app in an test environment and I can't seem to get it to function correctly at all.
Describe the bug
Adding rules does not show and hide the correct fields when changing "layout".
To Reproduce
I've attached a video file of our screen recording of the issue.
Expected behavior
When rules are added the correct fields show/hide when switching between "layout" field values.
https://github.com/contentful/marketplace-partner-apps/assets/55763151/2e6b1c33-e5be-4e36-a01f-1341ba6e9a7a

Hi @houtaiwong-toast, thank you for raising this issue! Currently a constraint with the app framework is that you must refresh the Contentful web app once a change to the app configuration has been made. Do you mind trying to refresh the web app after setting the rules on the configuration page, and letting me know if this resolves the issue? If not, we will certainly look into it.

@houtaiwong-toast It looks like not all fields are showing up in the FlexFields editor. Can you share how the content type is set up and also how this looks in the default Contentful editor so that we can reproduce and debug this further. Thanks.

Not sure if it's the same issue but it at least looks similar to this one here.
I created 5 simple rules that check if a short text field contains a specific value and if so, hide another field. But these rules only work partly. When I look into the browsers dev tools I can see that https://api.contentful.com blocks some calls with HTTP 429 Too many requests. Could this be the reason and if so, what can I do about it?

@lilbitner @vipulchadda Do you think that @houtaiwong-toast's problem is also because of the contentful rate limiting?

@sizzle168 I don't think there should be any issues with rate limiting. Would you be able to share more details about the fields you are using and the rules that are set. This will allow us to reproduce this issue and dig into this further.

This is how the content type looks:

These are the configured rules:

I tested it again today and it still failed. So I checked the rules again and recognized that the non-working rules were lacking this "(Same Entry)" appendage. So I removed and recreated these rules and now it works perfectly. I also can't find any 429 responses anymore in the dev tools' network tab.
Any idea?

Ok I found out how to break it again!
I added new fields to the content type as below:

Then I changed a rule to also hide these new fields. After saving the rule configuration, the "(Same Entry)" appendage disappeared and the rule didn't work anymore.

Does that help you?

Oh, I guess that might be the issue. I think there was a change to allow for any reference to the same content type. So the rules without (Same Entry) would be invalid as you dont have any reference fields. Can you try to recreate/update that rule to make sure it uses (Same Entry) value

Yes, recreating the rule works, updating the rule unfortunately not. And recreating the rule everytime a newly added field needs to be considered by the rule, is not an option for us.

You should not have to recreate rules again all the time. This was due to 1 fix that was made to make sure this scenario works. Once you have fixed/recreated all existing rules (it should now say (SameEntry)), you will not need to recreate the rules. Just editing them should work properly

That's not possible. Please, see my video. When editing a rule (even without changing anything), the rule will be broken after saving. Rules that no longer work can be recognized by the missing entry (Same Entry)
https://github.com/contentful/marketplace-partner-apps/assets/19364321/4138e254-b05b-41ef-a85d-3045521071e6

Oh, ok. Thanks for clarifying. Will work on fixing this and let you know once it is fixed.

Thank you!

@lilbitner would you be able to help with the PR raised to fix this issue (https://github.com/contentful/marketplace-partner-apps/pull/919)

@vipulchadda I'll be taking a look at your PRs today

@houtaiwong-toast @sizzle168 I merged in @vipulchadda's fix and it is now deployed to production. Can you please verify that this issue is now resolved? Thank you!

It's resolved! Thank's!

It's resolved! Thank's!

Great, thanks for confirming! I'll close this issue now.


Fix Issue #320 Fix transparent object ordering in 3d

Solves https://github.com/djeedai/bevy_hanabi/issues/320

Tested with cargo run --example ordering --features="bevy/bevy_winit bevy/bevy_pbr bevy/png 3d examples_world_inspector"

I've changed the example a bit to make sure we can see the blue rectangle being rendered on top and partially (but not completely) affecting the particles:

Great, thanks!


Update template-specialization-cpp.md

Adds the delete statement for showcasing good practice.

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

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


Apply duckdb's patches

Main question is where this makes sense to merge / if you want to have a v1.0.0 branch + a main branch, or what other strategy. Idea is having a git ref so that within duckdb it can be retargeted to this branch + removing the patches.

Thanks!


CSS build delay

When saving changes on CSS files with custom builder, I have to refresh it twice. It needs to know that the build is done before refreshing the page.

Fixed.


Use joi to validate and set defaults

joi is a library to validate objects against a schema. This branch switches to joi for validating the config to try to work around configuration errors.
For this pull request, I'm just going to try to get validation in place. I'll open a separate PR opens an issue in the repository to report errors with the configuration.
cc #81, #62
closes #86

This is in production now. If stale.yml has an invalid config, then the default values will be used, and warnings will be reported to Sentry.
In a future, this should report the errors to the end-user and refuse to run until the configuration is valid.

9 hours later, there have been ~350 warnings from the schema check, and zero GitHub API errors due to malformed schema. Calling this a success! 🎉
Next up will be implementing a probot/report-errors package that will open an issue on the target repository when a configuration error occurs.

My only comment is that there is a lot more code going on; as cool as Joi is, it's pretty bulky. I'm not saying we shouldn't use it, just something I've noticed.

Yeah, I agree. It'd be nice if there was a concise schema definition format. Before we recommend this for all apps I want to experiment with a few different approaches.


Add implementation for the remaining hints on Uint256.cairo

Add implementation for the remaining hints on Uint256.cairo
https://github.com/starkware-libs/cairo-lang/blob/167b28bcd940fd25ea3816204fa882a0b0a49603/src/starkware/cairo/common/uint256.cairo
Description

Add hint implementations:

fn uint256_sqrt

%{
    from starkware.python.math_utils import isqrt
    n = (ids.n.high << 128) + ids.n.low
    root = isqrt(n)
    assert 0 <= root < 2 ** 128
    ids.root.low = root
    ids.root.high = 0
%}

fn uint256_signed_nn

%{ memory[ap] = 1 if 0 <= (ids.a.high % PRIME) < 2 ** 127 else 0 %}

fn uint256_unsigned_div_rem

%{
    a = (ids.a.high << 128) + ids.a.low
    div = (ids.div.high << 128) + ids.div.low
    quotient, remainder = divmod(a, div)

    ids.quotient.low = quotient & ((1 << 128) - 1)
    ids.quotient.high = quotient >> 128
    ids.remainder.low = remainder & ((1 << 128) - 1)
    ids.remainder.high = remainder >> 128
%}

Update cairo_programs/uint256.cairo integration test
add bigint_i128! macro

Description of the pull request changes and motivation.
Checklist

[ ] Linked to Github Issue
[x] Unit tests added
[x] Integration tests added.
[ ] This change requires new documentation.

[ ] Documentation has been added/updated.

Codecov Report

Merging #316 (eb81872) into main (27408f8) will increase coverage by 0.09%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##             main     #316      +/-   ##
==========================================
+ Coverage   96.62%   96.71%   +0.09%
==========================================
  Files          32       32
  Lines       11578    11890     +312
==========================================
+ Hits        11187    11500     +313
+ Misses        391      390       -1

Impacted Files
Coverage Δ

src/utils.rs
100.00% <ø> (ø)

src/vm/hints/execute_hint.rs
100.00% <100.00%> (ø)

src/vm/hints/uint256_utils.rs
100.00% <100.00%> (+0.54%)
:arrow_up:

Help us with your feedback. Take ten seconds to tell us how you rate us.

@Oppen you can check thew review corrections here


delay is not being honored

I apologize in advance for adding this issue here but I could not find a way to create this issue under here
https://github.com/lopelex/node-red-contrib-harmony
The sendCommandsWithDelay does not seem to be implemented. Please advise.
Thanks, Stephan

I do not know exactly what you mean.
In HWS command sendCommandsWithDelay is addressed as soon as you set the delay bigger 0.
See https://github.com/lopelex/node-red-contrib-harmony/blob/master/harmony/hub.js#L236.

I have tried many values in the 10's , 100's and 1000's and there is no perceivable delay to the command.

The delay time indicates how long the command is held.
So how long the IR signal is sent. The delay is not a pause between the commands.
https://github.com/lopelex/harmony-websocket/blob/master/lib/harmony-websocket.js#L313

Ahh so it's the equivalent to holding down the volume button for x seconds, correct?
If so, can I make a feature request to insert a delay (before or after..doesn't matter) to the command being sent?

Of course I'm ready for it.
But please read this through:
https://github.com/lopelex/harmony-websocket/pull/2

https://github.com/lopelex/node-red-contrib-harmony/commit/d95a491382a94031025c4b57054de1d2663c3784

ready for testing


flutter run hangs on "Resolving dependencies..."

From @martinkbrown on August 30, 2017 20:59
Steps to Reproduce
Run flutter run.
Version info from Flutter Doctor
PS C:\Users\nz962\git\flutter-hello-world\myapp> flutter doctor
[√] Flutter (on Microsoft Windows [Version 6.3.9600], locale en-US, channel alpha)
    • Flutter at C:\Users\nz962\git\flutter
    • Framework revision b156a0f054 (3 weeks ago), 2017-08-11 22:01:40 -0700
    • Engine revision fef7d827d6
    • Tools Dart version 1.25.0-dev.9.0

[√] Android toolchain - develop for Android devices (Android SDK 26.0.0)
    • Android SDK at C:\Users\nz962\AppData\Local\Android\sdk
    • Platform android-26, build-tools 26.0.0
    • ANDROID_HOME = C:\Users\nz962\AppData\Local\Android\sdk
    • Java binary at: C:\Users\nz962\Downloads\Software\Android3.0\android-studio\jre\bin\java
    • Java version OpenJDK Runtime Environment (build 1.8.0_152-release-884-b01)

[√] Android Studio (version 2.3)
    • Android Studio at C:\Program Files\Android\Android Studio
    • Java version OpenJDK Runtime Environment (build 1.8.0_112-release-b06)

[√] Android Studio (version 3.0)
    • Android Studio at C:\Users\nz962\Downloads\Software\Android3.0\android-studio
    • Java version OpenJDK Runtime Environment (build 1.8.0_152-release-884-b01)

[√] Connected devices
    • Nexus 6P • 8XV7N16516000352 • android-arm • Android 6.0.1 (API 23)

Logs
After running flutter run -v, I get this:
PS C:\Users\nz962\git\flutter-hello-world\myapp> flutter run -v
[  +23 ms] [C:\Users\nz962\git\flutter\] git rev-parse --abbrev-ref --symbolic @{u}
[ +118 ms] Exit code 0 from: git rev-parse --abbrev-ref --symbolic @{u}
[        ] origin/alpha
[   +2 ms] [C:\Users\nz962\git\flutter\] git ls-remote --get-url origin
[  +70 ms] Exit code 0 from: git ls-remote --get-url origin
[        ] https://github.com/flutter/flutter.git
[   +2 ms] [C:\Users\nz962\git\flutter\] git log -n 1 --pretty=format:%H
[  +66 ms] Exit code 0 from: git log -n 1 --pretty=format:%H
[        ] b156a0f0549a3ad3e1134638f26f472427c379be
[   +2 ms] [C:\Users\nz962\git\flutter\] git log -n 1 --pretty=format:%ar
[  +70 ms] Exit code 0 from: git log -n 1 --pretty=format:%ar
[        ] 3 weeks ago
[ +603 ms] Listing devices using C:\Users\nz962\AppData\Local\Android\sdk\platform-tools\adb
[        ] C:\Users\nz962\AppData\Local\Android\sdk\platform-tools\adb devices -l
[  +43 ms] Exit code 0 from: C:\Users\nz962\AppData\Local\Android\sdk\platform-tools\adb devices -l
[        ] List of devices attached
           8XV7N16516000352       device product:angler model:Nexus_6P device:angler
[  +22 ms] C:\Users\nz962\AppData\Local\Android\sdk\platform-tools\adb -s 8XV7N16516000352 shell getprop
[ +142 ms] ro.hardware = angler
[        ] ro.build.characteristics = nosdcard
[ +626 ms] Launching lib/main.dart on Nexus 6P in debug mode...
[   +6 ms] Initializing gradle...
[        ] Using gradle from C:\Users\nz962\git\flutter-hello-world\myapp\android\gradlew.bat.
[ +258 ms] C:\Users\nz962\git\flutter-hello-world\myapp\android\gradlew.bat -v
[ +732 ms]
           ------------------------------------------------------------
           Gradle 3.3
           ------------------------------------------------------------

           Build time:   2017-01-03 15:31:04 UTC
           Revision:     075893a3d0798c0c1f322899b41ceca82e4e134b

           Groovy:       2.4.7
           Ant:          Apache Ant(TM) version 1.9.6 compiled on June 29 2015
           JVM:          1.8.0_152-release (JetBrains s.r.o 25.152-b01)
           OS:           Windows 8.1 6.3 amd64

           Picked up _JAVA_OPTIONS: -Djava.net.preferIPv4Stack=true
[   +2 ms] Resolving dependencies...
[   +2 ms] [android\] C:\Users\nz962\git\flutter-hello-world\myapp\android\gradlew.bat app:properties

Copied from original issue: flutter/flutter-intellij#1311

Thanks for the detailed info! It looks like flutter run is hung up on the gradle build step. I don't know enough about what can commonly go wrong here. I'll cc people who know a bit more (and bump this issue over to the main flutter repo).

/cc @jason-simmons @jakobr-google

/cc @mravn-google

The issue is with my network at work. I tried it while connected to an external network and it was successful!
I can usually get around the proxies at work, but even Chrome has been having some trouble with DNS lookups lately, giving DNS lookup errors and certificate errors. But I thought that since flutter doctor worked, that the issue was not with my network, but I was wrong.
Solution: Use a different network.

I encounted above-mentioned behaviour while running a project. I was able to fix it by disabling antivirus for a while (Avast Antivirus on Windows 10 version 1709 build 16299.2)

Same issue with F-Secure on  Windows 10 Enterprise, Version10.0.15063 Build 15063.

same issue but not running any antivirus so not sure

i am running the same cammand on Linux ,still receiving the problem .. i am sure its not a networking or Antivirus problem .

@Cyan101 @MalwareNinja do you get the exact same behavior - as in, flutter run -v seems to hang just after printing out the line about running gradlew app:properties, or does it hang on another line?

This worked for me:
./flutter_project_name/android/gradlew

After successful build.
Try run the project again.

I just had this on Windows... I ran the gradlew file maually as suggested above and saw:
PS M:\Coding\Applications\Dart-Code\test\test_projects\flutter_hello_world> .\android\gradlew
Starting a Gradle Daemon, 2 incompatible Daemons could not be reused, use --status for details

And after that it was fine.

Same problem when running on Mac. Running .\android\gradlew didn't solve the issue.

Sometimes it helps to delete the android/.gradle folder and retry.

@Nykollas Thanks man it worked

As mentioned by @Nykollas, I used the command gradlew under the folder structure, during the command run it downloaded various zip files and extracted it. I traced out errors each time and again ran the gradlew command until it prompted Build Successful. It may require to use the command several times to finally remove the issue by solving them manually or with the help of search.
Thank you...

Is it a must for android studio to run for long the first time i run hello world,because i used gradlew command and after successful build i tried to run but still takes ages

On my machine it doesn't exactly hang, just takes about 3 hours... glad we have hot reload, just avoid cold start ;) Turning network off makes it start reasonably fast.

I had it twice, and I ran gradlew --debug manually. It also stuck on resolving dependencies.
If you are in China, the reason  maybe that flutter proxy setting does not work for gradle.
You have to set it in gradle.properties.
I finally solved it by with this line
org.gradle.jvmargs=-DsocksProxyHost=<IP_ADDRESS> -DsocksProxyPort=6444

It fixed with me by changing the SDK location in local.properties file.

Same problem...
stuck at
[        ] executing: [/home/sanket143/Desktop/Verts/Android/hello/android/] /home/sanket143/Desktop/Verts/Android/hello/android/gradlew app:properties

flutter doctor is fine.
$ ./android/gradlew
$ # BUILD SUCCESSFUL
$ # didn't worked, same problem

Does this requires Internet ?

Same issue with MacOS(10.14.1).
Inspired by @gliheng , since I use shadowsocks, so I add this line to change the gradle proxy:
org.gradle.jvmargs=-DhttpProxyHost=<IP_ADDRESS> -DhttpProxyPort=1080

Hope it helps!

for me, the below works

rm -rf ~/.gradle
cd flutter_your_project/android <- go android directory
./gradlew
./gradlew app:properties

executing ./gradelw fixed the issue in linux

This worked for me:
./flutter_project_name/android/gradlew

After successful build.
Try run the project again.

This work for me, thanks!

Has someone solved this issue? In my gitlab CI/CD it gets stuck on
executing: [/builds/flutter/[project_name]/android/] /builds/flutter/[project_name]/android/gradlew app:properties
And this is a very strange behavior since it's occurring with this project only, with other projects it's working flawlessly straight.
I've tried setting up a worker timeout of 3 hours but seems not to be sufficient, it gets stuck and the build fails. Tried also changing the gradlew script and the gradle wrapper version downgrading it from 5.22 to 4.10 without any result.
Any suggestions would be appreciated, thank you!

@AngeloAvv make sure your android/gradlew is executable

I had the same issue lately,  I got it fixed it by setting my JAVA_HOME environment variable in /etc/environment to /usr/lib/jvm/java-12-openjdk

for me, the below works (macOS 10.14)

rm -rf ~/.gradle
cd flutter_your_project/android <- go android directory
add org.gradle.jvmargs=-DhttpProxyHost=<IP_ADDRESS> -DhttpProxyPort=1080 on ./gradle.properties
./gradlew
./gradlew app:properties
cd ../
flutter run

4 & 5 works for me. It was upgraded gradle version to 5.6.2, then fixed that resolving dependencies issue.

I had this issue too with version 1.9.8.hotfix.4. A reasonable workaround could be to switch back to 1.7.8.hotfix.4.

i just deleted the .gradle in android directory and then everything went fine

1- Set the connection to internet off
2- run flutter un (THIS  MAY TAKE 13 sec)
3- you will see error about resource because it's need internet
4- set internet on
5- run flutter run
this should be work , good lucky

Hi @devoncarew is this issue still meant to be open?

This is likely obsolete now.

this work for me
run this in your project file
brew install gradle

I'm also having this issue in bitrise CI.
brew install gradle didn't work for me.

I solved with the suggested answer at https://stackoverflow.com/a/45782695/2164891
Apparently gradle can get stuck if you didn't approve all the android licenses required by the SDK.
Everything worked fine after executing the following command:
yes | sdkmanager --licenses

如果你试了以上的方法都没有解决，而你又刚好在中国国内的网络环境，建议你试下下面的方法，它对我有效果：
修改 ./flutter_project_name/android/build.gradle里的repositories（有两处），使用国内代理。
repositories {
    // google()
    // jcenter()
    maven { url 'https://maven.aliyun.com/repository/google' }
    maven { url 'https://maven.aliyun.com/repository/jcenter' }
    maven { url 'http://maven.aliyun.com/nexus/content/groups/public' }
}


Make xDS retry backoff configurable

Title: Add configuration parameters for xDS retry backoff strategy
Description:
The gRPC xDS implementation uses hardcoded retry durations for re-establishing the gRPC channel. I'm planning to address the TODO to make the backoff configurable, and I'm opening an issue so that I can get feedback on the configuration options I add.
Relevant Links:
https://github.com/envoyproxy/envoy/blob/v1.12.1/source/common/config/grpc_stream.h#L39

@baojr @snowp is it possible to reopen this issue? Configurable retry backoff is would be very beneficial for our use case.

@michaelbor I'm no longer involved with this project so I unfortunately cannot help.

Thanks, @baojr. I will open a new issue then since I don't see an option to reopen this one. BTW, please let me know if you have by chance any drafts for the code you planned to add for this feature.


ignore bottomLayoutGuide when hidesBottomBarWhenPushed == true

... otherwise I found that even when pushing from a navigation controller embedded in a UITabbarViewController with hidesBottomBarWhenPushed == true, bottomLayGuide.length would be set to 49. Elsewhere in the code hidesBottomBarWhenPushed is used to ignore bottomLayGuide.length, see: viewDidLayoutSubviews()

Codecov Report

Merging #299 into master will increase coverage by 0.01%.
The diff coverage is 100%.

@@            Coverage Diff            @@
##           master    #299      +/-   ##
=========================================
+ Coverage   64.39%   64.4%   +0.01%
=========================================
  Files          63      63
  Lines        3522    3523       +1
=========================================
+ Hits         2268    2269       +1
  Misses       1254    1254

Impacted Files
Coverage Δ

...Source/ChatController/BaseChatViewController.swift
81.14% <100%> (+0.1%)
:white_check_mark:

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 dcbb676...0041c16. Read the comment docs.


Require max size for shared memory

So sorry, I completely forgot to address this issue from @ncruces
https://github.com/tetratelabs/wazero/pull/1460#discussion_r1193557372

I've been seeing the windows tests fail with OOM sometimes but not often - just checking if that's been seen before. If not, it must be because of my PR and I'll look into it

opened https://github.com/tetratelabs/wazero/issues/1476 on the flake. thanks for reporting


update dependencies

Coverage remained the same at 86.053% when pulling fe8efb345102faf42da3ac0fb9f65d9ca227593b on sbp_5a_update_dependencies into 1a358ad6c45d710193bd7b24fb0d36a8a8f02eb2 on master.


toggle returns an empty string instead of false when off

need to return false instead of "" when toggle is switched off

fixed in 0.0.20


Encryption causes: pyo3_runtime.PanicException: called Option::unwrap() on a None value

I did the following to setup pysequoia:
I exported a secret key to a file called sender.asc like this:
gpg --armor --export-secret-key <fingerprint> > sender.asc

And a public key like this:
gpg --armor --export <other fingerprint> > recipient.asc

Then I did the following setup steps.
Download files from https://pypi.org/project/pysequoia/#files
tar -xvzf pysequoia-0.1.11.tar.gz
python3 -m venv .env
source .env/bin/activate
pip install maturin[patchelf]
cd pysequoia-0.1.11/
maturin develop  # finishes without error

I copy-pasted the demo code in a file named minimal_test_case.py like this:
from pysequoia import Cert, Context

s = Cert.from_file("sender.asc")
r = Cert.from_bytes(open("recipient.asc", "rb").read())
encrypted = Context.standard().encrypt(s, r, "content to encrypt")
print(f"Encrypted data: {encrypted}")

And ran it like this, but it fails:
% RUST_BACKTRACE=full python minimal_test_case.py
thread '<unnamed>' panicked at 'called `Option::unwrap()` on a `None` value', src/lib.rs:422:10
stack backtrace:
   0:     0x7fbaf6b8191d - std::backtrace_rs::backtrace::libunwind::trace::h8217d0a8f3fd2f41
                               at /rustc/4b91a6ea7258a947e59c6522cd5898e7c0a6a88f/library/std/src/../../backtrace/src/backtrace/libunwind.rs:93:5
   1:     0x7fbaf6b8191d - std::backtrace_rs::backtrace::trace_unsynchronized::h308103876b3af410
                               at /rustc/4b91a6ea7258a947e59c6522cd5898e7c0a6a88f/library/std/src/../../backtrace/src/backtrace/mod.rs:66:5
   2:     0x7fbaf6b8191d - std::sys_common::backtrace::_print_fmt::hc208018c6153605e
                               at /rustc/4b91a6ea7258a947e59c6522cd5898e7c0a6a88f/library/std/src/sys_common/backtrace.rs:66:5
   3:     0x7fbaf6b8191d - <std::sys_common::backtrace::_print::DisplayBacktrace as core::fmt::Display>::fmt::hf89a7ed694dfb585
                               at /rustc/4b91a6ea7258a947e59c6522cd5898e7c0a6a88f/library/std/src/sys_common/backtrace.rs:45:22
   4:     0x7fbaf6ba1d8c - core::fmt::write::h21038c1382fe4264
                               at /rustc/4b91a6ea7258a947e59c6522cd5898e7c0a6a88f/library/core/src/fmt/mod.rs:1197:17
   5:     0x7fbaf6b7cbe1 - std::io::Write::write_fmt::h7dbb1c9a3c254aef
                               at /rustc/4b91a6ea7258a947e59c6522cd5898e7c0a6a88f/library/std/src/io/mod.rs:1672:15
   6:     0x7fbaf6b83095 - std::sys_common::backtrace::_print::h4e8889719c9ddeb8
                               at /rustc/4b91a6ea7258a947e59c6522cd5898e7c0a6a88f/library/std/src/sys_common/backtrace.rs:48:5
   7:     0x7fbaf6b83095 - std::sys_common::backtrace::print::h1506fe2cb3022667
                               at /rustc/4b91a6ea7258a947e59c6522cd5898e7c0a6a88f/library/std/src/sys_common/backtrace.rs:35:9
   8:     0x7fbaf6b83095 - std::panicking::default_hook::{{closure}}::hd9d7ce2a8a782440
                               at /rustc/4b91a6ea7258a947e59c6522cd5898e7c0a6a88f/library/std/src/panicking.rs:295:22
   9:     0x7fbaf6b82db6 - std::panicking::default_hook::h5b16ec25444b1b5d
                               at /rustc/4b91a6ea7258a947e59c6522cd5898e7c0a6a88f/library/std/src/panicking.rs:314:9
  10:     0x7fbaf6b83626 - std::panicking::rust_panic_with_hook::hb0138cb6e6fea3e4
                               at /rustc/4b91a6ea7258a947e59c6522cd5898e7c0a6a88f/library/std/src/panicking.rs:698:17
  11:     0x7fbaf6b834d9 - std::panicking::begin_panic_handler::{{closure}}::h4cb67095557cd1aa
                               at /rustc/4b91a6ea7258a947e59c6522cd5898e7c0a6a88f/library/std/src/panicking.rs:586:13
  12:     0x7fbaf6b81dd4 - std::sys_common::backtrace::__rust_end_short_backtrace::h2bfcac279dcdc911
                               at /rustc/4b91a6ea7258a947e59c6522cd5898e7c0a6a88f/library/std/src/sys_common/backtrace.rs:138:18
  13:     0x7fbaf6b83249 - rust_begin_unwind
                               at /rustc/4b91a6ea7258a947e59c6522cd5898e7c0a6a88f/library/std/src/panicking.rs:584:5
  14:     0x7fbaf5fc6ed3 - core::panicking::panic_fmt::h1de71520faaa17d3
                               at /rustc/4b91a6ea7258a947e59c6522cd5898e7c0a6a88f/library/core/src/panicking.rs:142:14
  15:     0x7fbaf5fc6d9d - core::panicking::panic::h467ee1bf554babeb
                               at /rustc/4b91a6ea7258a947e59c6522cd5898e7c0a6a88f/library/core/src/panicking.rs:48:5
  16:     0x7fbaf6064295 - core::option::Option<T>::unwrap::h77fc95d20dc76962
                               at /rustc/4b91a6ea7258a947e59c6522cd5898e7c0a6a88f/library/core/src/option.rs:775:21
  17:     0x7fbaf602e895 - pysequoia::encrypt_for::h2a260e67e6f38090
                               at /home/jan/Projekte/pysequoia/pysequoia-0.1.11/src/lib.rs:413:24
  18:     0x7fbaf5fce8d7 - pysequoia::Context::encrypt::hfcdbeb07f8e4c2c8
                               at /home/jan/Projekte/pysequoia/pysequoia-0.1.11/src/lib.rs:183:9
  19:     0x7fbaf6032f54 - pysequoia::_::<impl pysequoia::Context>::__pymethod_encrypt__::{{closure}}::h9a0754f163b3f3d4
                               at /home/jan/Projekte/pysequoia/pysequoia-0.1.11/src/lib.rs:168:1
  20:     0x7fbaf5ff5bb0 - std::panicking::try::do_call::h13d762b9bcaf9d8d
                               at /rustc/4b91a6ea7258a947e59c6522cd5898e7c0a6a88f/library/std/src/panicking.rs:492:40
  21:     0x7fbaf5ffa74b - __rust_try
  22:     0x7fbaf5ff3c06 - std::panicking::try::ha055326381e54c20
                               at /rustc/4b91a6ea7258a947e59c6522cd5898e7c0a6a88f/library/std/src/panicking.rs:456:19
  23:     0x7fbaf5ffe758 - std::panic::catch_unwind::h99c32f221df2de43
                               at /rustc/4b91a6ea7258a947e59c6522cd5898e7c0a6a88f/library/std/src/panic.rs:137:14
  24:     0x7fbaf5fceb4c - pysequoia::_::<impl pysequoia::Context>::__pymethod_encrypt__::h208e3e5d91acac13
                               at /home/jan/Projekte/pysequoia/pysequoia-0.1.11/src/lib.rs:168:1
  25:     0x557b6be97f7e - <unknown>
  26:     0x557b6be6014a - _PyEval_EvalFrameDefault
  27:     0x557b6be5c766 - <unknown>
  28:     0x557b6bf54456 - PyEval_EvalCode
  29:     0x557b6bf80f08 - <unknown>
  30:     0x557b6bf79d5b - <unknown>
  31:     0x557b6bf80c55 - <unknown>
  32:     0x557b6bf80138 - _PyRun_SimpleFileObject
  33:     0x557b6bf7fe33 - _PyRun_AnyFileObject
  34:     0x557b6bf710ae - Py_RunMain
  35:     0x557b6bf4734d - Py_BytesMain
  36:     0x7fbaf788ad90 - __libc_start_call_main
                               at ./csu/../sysdeps/nptl/libc_start_call_main.h:58:16
  37:     0x7fbaf788ae40 - __libc_start_main_impl
                               at ./csu/../csu/libc-start.c:392:3
  38:     0x557b6bf47245 - _start
  39:                0x0 - <unknown>
Traceback (most recent call last):
  File "/home/jan/Projekte/pysequoia/minimal_test_case.py", line 5, in <module>
    encrypted = Context.standard().encrypt(s, r, "content to encrypt")
pyo3_runtime.PanicException: called `Option::unwrap()` on a `None` value

The error is the same when I install pysequoia via pip.
Am I doing something wrong?
Or is this a bug?

Sounds very much like a bug. Thanks for the instructions I'll replicate it locally and fix it.
Just for the record: I hope you are aware that the API is in flux and may change at any time? :)

Thanks for looking into it. Yes, I am aware this is a very early stage, but I've been waiting since about the inception of sequoia for Python Bindings and am willing to rewrite my code a few times. Regard me as an early adopter, who'll happily help you with testing your project and sending bug reports etc. along the way.

Great to hear that!
Just out of curiosity do you already have a use case in mind? We've got a couple of features in the pipeline but are always happy to look at what real users would need...

I want to use it for the mailer part of a membership management application we use in the Chaos Computer Club. We have quite a few members who use PGP and would like to receive encrypted mails. I could use a project like Kuverto, but I want better integration for managing keys of members. I want the software to fetch, store, and read keys and send custom error messages, when a key does not work for some reason. Also, I want the code to be very efficient, because we may be sending thousands of mails in a single day. So I am looking into multiprocessing and async programming.
So far I believe most of my use cases are covered with the current API described at https://pypi.org/project/pysequoia/

Read a (private) key from disk
Fetch a key by fingerprint or long ID from a keyserver
Fetch a key via WKD
Encrypt and sign
Store a key on disk

What I am not yet sure how to do is how to check the validity of a key. What if a key is revoked, expired, or unusable in any other way? How can I find that out (and send a error message to the recipient)?

Hi @wiktor-k, I tested version 0.1.12 from PyPI, but the problem is still the same:
RUST_BACKTRACE=full python minimal_test_case.py
thread '<unnamed>' panicked at 'called `Option::unwrap()` on a `None` value', src/lib.rs:422:10
stack backtrace:
   0:     0x7fe6201ca22d - std::backtrace_rs::backtrace::libunwind::trace::h8217d0a8f3fd2f41
                               at /rustc/4b91a6ea7258a947e59c6522cd5898e7c0a6a88f/library/std/src/../../backtrace/src/backtrace/libunwind.rs:93:5
   1:     0x7fe6201ca22d - std::backtrace_rs::backtrace::trace_unsynchronized::h308103876b3af410
                               at /rustc/4b91a6ea7258a947e59c6522cd5898e7c0a6a88f/library/std/src/../../backtrace/src/backtrace/mod.rs:66:5
   2:     0x7fe6201ca22d - std::sys_common::backtrace::_print_fmt::hc208018c6153605e
                               at /rustc/4b91a6ea7258a947e59c6522cd5898e7c0a6a88f/library/std/src/sys_common/backtrace.rs:66:5
   3:     0x7fe6201ca22d - <std::sys_common::backtrace::_print::DisplayBacktrace as core::fmt::Display>::fmt::hf89a7ed694dfb585
                               at /rustc/4b91a6ea7258a947e59c6522cd5898e7c0a6a88f/library/std/src/sys_common/backtrace.rs:45:22
   4:     0x7fe6201ea66c - core::fmt::write::h21038c1382fe4264
                               at /rustc/4b91a6ea7258a947e59c6522cd5898e7c0a6a88f/library/core/src/fmt/mod.rs:1197:17
   5:     0x7fe6201c54f1 - std::io::Write::write_fmt::h7dbb1c9a3c254aef
                               at /rustc/4b91a6ea7258a947e59c6522cd5898e7c0a6a88f/library/std/src/io/mod.rs:1672:15
   6:     0x7fe6201cb9a5 - std::sys_common::backtrace::_print::h4e8889719c9ddeb8
                               at /rustc/4b91a6ea7258a947e59c6522cd5898e7c0a6a88f/library/std/src/sys_common/backtrace.rs:48:5
   7:     0x7fe6201cb9a5 - std::sys_common::backtrace::print::h1506fe2cb3022667
                               at /rustc/4b91a6ea7258a947e59c6522cd5898e7c0a6a88f/library/std/src/sys_common/backtrace.rs:35:9
   8:     0x7fe6201cb9a5 - std::panicking::default_hook::{{closure}}::hd9d7ce2a8a782440
                               at /rustc/4b91a6ea7258a947e59c6522cd5898e7c0a6a88f/library/std/src/panicking.rs:295:22
   9:     0x7fe6201cb6c6 - std::panicking::default_hook::h5b16ec25444b1b5d
                               at /rustc/4b91a6ea7258a947e59c6522cd5898e7c0a6a88f/library/std/src/panicking.rs:314:9
  10:     0x7fe6201cbf36 - std::panicking::rust_panic_with_hook::hb0138cb6e6fea3e4
                               at /rustc/4b91a6ea7258a947e59c6522cd5898e7c0a6a88f/library/std/src/panicking.rs:698:17
  11:     0x7fe6201cbde9 - std::panicking::begin_panic_handler::{{closure}}::h4cb67095557cd1aa
                               at /rustc/4b91a6ea7258a947e59c6522cd5898e7c0a6a88f/library/std/src/panicking.rs:586:13
  12:     0x7fe6201ca6e4 - std::sys_common::backtrace::__rust_end_short_backtrace::h2bfcac279dcdc911
                               at /rustc/4b91a6ea7258a947e59c6522cd5898e7c0a6a88f/library/std/src/sys_common/backtrace.rs:138:18
  13:     0x7fe6201cbb59 - rust_begin_unwind
                               at /rustc/4b91a6ea7258a947e59c6522cd5898e7c0a6a88f/library/std/src/panicking.rs:584:5
  14:     0x7fe61f4f8ea3 - core::panicking::panic_fmt::h1de71520faaa17d3
                               at /rustc/4b91a6ea7258a947e59c6522cd5898e7c0a6a88f/library/core/src/panicking.rs:142:14
  15:     0x7fe61f4f8d6d - core::panicking::panic::h467ee1bf554babeb
                               at /rustc/4b91a6ea7258a947e59c6522cd5898e7c0a6a88f/library/core/src/panicking.rs:48:5
  16:     0x7fe61f594445 - core::option::Option<T>::unwrap::h3b1a3a66b47b87e8
                               at /rustc/4b91a6ea7258a947e59c6522cd5898e7c0a6a88f/library/core/src/option.rs:775:21
  17:     0x7fe61f54f105 - pysequoia::encrypt_for::h7531509fd4750f41
                               at /home/jan/Projekte/pysequoia/pysequoia-0.1.12/src/lib.rs:413:24
  18:     0x7fe61f55eb97 - pysequoia::Context::encrypt::hf4f313356aa7a21e
                               at /home/jan/Projekte/pysequoia/pysequoia-0.1.12/src/lib.rs:183:9
  19:     0x7fe61f5537c4 - pysequoia::_::<impl pysequoia::Context>::__pymethod_encrypt__::{{closure}}::h10a8e2cd46e49d51
                               at /home/jan/Projekte/pysequoia/pysequoia-0.1.12/src/lib.rs:168:1
  20:     0x7fe61f52ec20 - std::panicking::try::do_call::hcf6ede9284f014af
                               at /rustc/4b91a6ea7258a947e59c6522cd5898e7c0a6a88f/library/std/src/panicking.rs:492:40
  21:     0x7fe61f531ecb - __rust_try
  22:     0x7fe61f528a56 - std::panicking::try::h16dde3ad569341e8
                               at /rustc/4b91a6ea7258a947e59c6522cd5898e7c0a6a88f/library/std/src/panicking.rs:456:19
  23:     0x7fe61f54aaa8 - std::panic::catch_unwind::h7047c3700816f519
                               at /rustc/4b91a6ea7258a947e59c6522cd5898e7c0a6a88f/library/std/src/panic.rs:137:14
  24:     0x7fe61f55ee0c - pysequoia::_::<impl pysequoia::Context>::__pymethod_encrypt__::h7a5aa14f5be61582
                               at /home/jan/Projekte/pysequoia/pysequoia-0.1.12/src/lib.rs:168:1
  25:     0x55a0151bbf7e - <unknown>
  26:     0x55a01518414a - _PyEval_EvalFrameDefault
  27:     0x55a015180766 - <unknown>
  28:     0x55a015278456 - PyEval_EvalCode
  29:     0x55a0152a4f08 - <unknown>
  30:     0x55a01529dd5b - <unknown>
  31:     0x55a0152a4c55 - <unknown>
  32:     0x55a0152a4138 - _PyRun_SimpleFileObject
  33:     0x55a0152a3e33 - _PyRun_AnyFileObject
  34:     0x55a0152950ae - Py_RunMain
  35:     0x55a01526b34d - Py_BytesMain
  36:     0x7fe620f21d90 - __libc_start_call_main
                               at ./csu/../sysdeps/nptl/libc_start_call_main.h:58:16
  37:     0x7fe620f21e40 - __libc_start_main_impl
                               at ./csu/../csu/libc-start.c:392:3
  38:     0x55a01526b245 - _start
  39:                0x0 - <unknown>
Traceback (most recent call last):
  File "/home/jan/Projekte/pysequoia/minimal_test_case.py", line 5, in <module>
    encrypted = Context.standard().encrypt(s, r, "content to encrypt")
pyo3_runtime.PanicException: called `Option::unwrap()` on a `None` value

I think I figured out the problem. I checked the source at src/lib.rs:422:10:
    let signing_cert = signing_cert
        .cert
        .keys()
        .unencrypted_secret()
        .with_policy(policy, None)
        .alive()
        .revoked(false)
        .for_signing()
        .next()
        .unwrap()
        .key()
        .clone()
        .into_keypair()?;

.unencrypted_secret() reads to me as if only keys whitouth a password are supported right now. So I generated a test key without a password and this worked.

Great to hear! BTW I think my edit didn't reach you as I suggested just that: https://github.com/wiktor-k/pysequoia/issues/2#issuecomment-1425435485

Ah, indeed. I neither noticed the edit nor got a notification.


[Question]: Embedding error

I try to Embed a markdown file , it works before , but since yesterday I got these error , I try run in demo.ragflow.io or my docker .
Embed Model : Fast Embed - BAAI/bge-large-en-v1.5
Start to parse.
Finish parsing.
Finished slicing files(10). Start to embedding the content.
[ERROR]Embedding error:Error code: 500 - {'code': 50500, 'message': 'Request processing has failed due to some unknown error.', 'data': None}
Finished embedding(4.29)! Start to build index!
Embed Model :  SiliconFlow - BAAI/bge-large-en-v1.5
Start to parse.
Finish parsing.
Finished slicing files(10). Start to embedding the content.
[ERROR]Embedding error:Error code: 400 - {'code': 20012, 'message': 'Model does not exist. Please check it carefully.', 'data': None}
Finished embedding(0.96)! Start to build index!

Demo site did not support Fast Embed anymore.

hi @lionkingc  Thank you for bringing this up. It seems there was an unknown error when calling SILICONFLOW using the OpenAI API-compatible paradigm. After switching to a native HTTP request, the error disappeared. You can pull the latest image after the code update to resolve this issue. If the problem persists, please feel free to let me know

解决了,原来是md文件中含有一些表格代码,转换成以下格式后顺利embedding.

Pros
Cons

Range of low-prep and no-prep options
Some sub-par ingredients


Replace custom logging with built-in version.

Rather than write to stdout via click.echo, use Python's built-in logging
mechanism. This is a bit more conventional and could allow users to configure
logs more thoroughly. It should also resolve #362.
To match the ANSI colors, this now imports the coloredlogs module.
Contributor checklist

[ ] ~Provided the tests for the changes~ (N/A, refactor)
[x] Added the changes to CHANGELOG.md
[ ] Requested (or received) a review from another contributor

I like the idea of moving away from click and towards using the stdlib for logging. In doing so, can we avoid introducing a new dependency, coloredlogs? It seems as pip-tools is a very low level tool used to build projects instead of consumed directly by projects it should strive for a minimal number of dependencies.

While I'm generally in favor of reducing dependencies, the coloredlogs library is tailor-fit to this situation. Python's logging system isn't aware of ANSI colors (they don't make sense when outputting to a file, constructing JSON for logstash, etc.). coloredlogs allows us to add that back when writing to the console (while avoiding it for other outputs) to match the existing functionality.
I think that leaves us with a few possibilities:

Continue to write everything to stdout and skip Python's logging system. This is not a great solution as it mixes different types of messages and doesn't allow the logs to be configured.
Use Python's logging system, but don't attempt to colorize the stdout/stderr logs. This is a regression in terms of functionality.
Use Python's logging system and coloredlogs. This solves the problems of 1 and 2, but adds a new dependency.
Use Python's logging system and re-implement coloredlogs in pip-tools. This is also a less-than-optimal solution as it requires new tests and maintenance for the pip-tools team. It's also trading a custom logging system for a custom coloring system, which isn't as significant a step forward.

Thanks for the analysis and reasoning. I agree that 1 & 4 are definitely not wanted. Your considerations of the trade offs are very fair.

I'm like the idea. The only thing bugging me is the effect of a pip-sync for an app also using coloredlogs.
I did a simple test with your branch on Windows:
requirements.in:
coloredlogs<6.0

then
$ pip-compile
$ pip-sync

and it went well, no problem with modifying coloredlogs while pip-sync used it itself.
(If only it could go that well all the time... sigh).
That was a really simple test, it would probably be a good idea to do test the behaviour a bit more.
Note, I actually managed to "break" pip-sync doing this:
requirements.in:
coloredlogs<1.0

then
$ pip-compile
$ pip-sync

ending up with coloredlogs==0.8 installed, which broke pip-sync.
So to be nice, we should set a lower bound on coloredlogs, so that running pip check will tell that something is wrong in that case.
I'll make a more complete review after the branch is rebased with the latest changes.

Maybe it would be acceptable to just not have colored logging? What are your thoughts?

Thinking about this over again, this is the same situation with any of of pip-tools dependencies (click or anything else). I did have to go out of my way a bit to break it. I think a reasonable idea here is to use coloredlogs, and put a version specifier, like we should, in install_requires. Let's try to put that lower bound as low as possible to minimize the conflict zone. I don't feel like this is lib with a high risk of conflict though.
Sorry for taking so long on this. Its a bit hard to get motivation when you know you're somewhat blocked ahead by being unable to make releases and give value to the time spent. /rant.

Too old to be salvageable.


v4 with cordova runs very slow compared to v3 (on iOS device)

switching between tabs is very sluggish compared to v3 which is almost instant, built with cordova using  the instructions in readme, this is on an iOS device

ok so enabling fast click definitely fixes the sluggishness, my remaining issue is on tab 2, the entire screen scrolls and the tabs don't stay fixed


migrate k8s-event-exporter to imagetest

As part of a Chainguard effort to reduce code duplication and provide higher quality images, we have stopped accepting pull requests for changes to images in this repository. Due to this, we are closing all pull requests today in order to start fresh.
If you think this pull request was closed in error, please feel free to re-open this pull request or open an issue and we will try to help you out. Thank you!


Child handler doesn't stopPropagation since 1.1.4 release

Hello,
First thank you for your package.
Since the 1.1.4 release, and especially this Pull Request (https://github.com/greena13/react-hotkeys/pull/101/files), there is a breaking change regarding event propagation to parent's handler.
Before this release, a hotkey defined in a child component AND in a root component was only triggered once (by the most nested component). But now, they are always both triggered (nested component AND root component).
I guess this happens because we create a new handler on each render() (and so hasChanged(handlers, prevHandlers) is always true) (see: https://github.com/greena13/react-hotkeys/pull/101/files#diff-5f147d6760a1bc2314f409768a38984fR247).
It means that your example in the README won't stop propagation to parent because a new handler is created on each render:
const MyNode = React.createClass({
  render() {
    const handlers = {
      'deleteNode': this.deleteNode
    };

    return (
      <HotKeys handlers={handlers}>
        Node contents
      </HotKeys>
    );
  }
});

Is it a (new) expected behavior ? If its is, shouldn't we mark this PR as a breaking change ?
We had to rollback to previous release to fix this issue, and I guess we're not the only one to create a new handler on each render (bad idea though, but a breaking change nevertheless)

Hello Colmea, thank you for your patience on this.
Can you please confirm the latest version of the package that still works for you? The hasChanged() logic appears to have been in since v1.1.1.

I'm seeing this as well, anyone have a workaround? I can submit a PR, is this still maintained? I love the API but afraid this has been open so long it's a dead project.

Hey @greena13 , sorry for the delay.
Indeed, the  1.0.6 is the last working release for us.


Update office-integration-troubleshooting.md

Providing correct Centralized Deployment App ID

Change made in response to a large thread with the support team and the office team.


? Cannot resolve symbol 'javafx' - I'm trying to run the demos locally but cannot due to JavaFX missing

Environment:

JDK 11
OS: Windows 10 Home - 20H2
RichTextFX: cloned from master branch
Gradle Version: 5.2.1
IDE: IntelliJ IDEA 2020.2.4

My aim: I want to be able to run the demos locally and debug through them to help me understand the code.
The problem: JavaFX seems to be missing so when I run the "gradlew RichTextDemo" command the compilation fails. Looking through the source code I can see any reference to javafx highlighted in red and upon hovering my mouse over said references I see "Cannot resolve symbol 'javafx'"
Context: I've cloned the source code from the master branch on GitHub and the initial build was successful, although I did notice the following message: "Deprecated Gradle features were used in this build, making it incompatible with Gradle 6.0.
Use '--warning-mode all' to show the individual deprecation warnings."
What I've tried:

I have javafx-sdk-15.0.1 installed and I've tried adding the lib folder as a library manually via Project Structure > Libraries > Plus Button > Java > Select javafx-sdk-15.0.1 lib folder. This changes the error to be "Cannot resolve symbol 'Path'" for example, instead of the previous error in which it could not find javafx.
I've also tried changing the project SDK under Project Structure > Project SDK > Add SDK > Select javafx-sdk-15.0.1 folder - but Intellij throws this error: "The selected directory is not a valid home for JDK"

I know this problem is trivial and most likely a result of my ignorance however I'm on a tight deadline and would appreciate any help massively.

Hi, so currently gradle is setup to compile RichTextFX against Java 8 or 9, where JavaFX is part of the JDK.
You have two options I think:

Download a JDK that includes JavaFX, like Azul, or
Change gradle to include JavaFX dependencies.

Unfortunately I cannot help with option 2 as my gradle foo is weak, but if you do get it right I'd really appreciate feedback.

Went with option 1 for speed's sake and it worked - much appreciated @Jugen

The syntax highlighting looks all normal after I switched to JDK 8 however the compile/build still fails:
FAILURE: Build failed with an exception.

What went wrong:
Execution failed for task ':richtextfx:compileJava'

Other errros:
error: cannot find symbol
@Override public final BooleanProperty editableProperty() { return editable; }
It seems to not be recognising the JavaFX package although the IDE does as I can CTRL+click into the JavaFX classes. Any ideas?

I tried adding the Gradle configs specified here: https://openjfx.io/openjfx-docs/#gradle
But it still didn't work.
I've now tried switching to JDK 9 and still no luck when I run "gradlew RichTextDemo"

Update: had to manually change the JAVA_HOME environment variable and restart IntelliJ
Now works, thanks @Jugen!


使用@SPI的wrapper方式报空指针异常bug #7176

Related issue #7176

Close for long time no response.
Please feel free to reopen if you have any question.
If you think these changes still useful in the latest master branch, please submit a new pull request.


Syntax highlighting for state/local variables

I was wondering if it would be possible to distinguish state variables (or local variables) and highlight them with other colors?
One drawback of using solidity (rather than viper) is there is no grammatical difference between accessing state variables and local variables. My current workaround is to prepend "_" to local variables and add a TextMate rule to highlight underscore-prepended variables to other colors. I was wondering if there're better solutions?

@dkenw it might be possible using the https://code.visualstudio.com/api/language-extensions/semantic-highlight-guide as opposed to the textmate one, as local and state variables are already identified by the parser using the code walker. Now that might be a big piece of work, this will have a dependency on first on other work to combine autocomplete and goto definitions using the same code walker service.
Now one thing, this may break due to normal syntax errors.

@juanfranblanco  It does look like a big piece of work. Just asking, will that be in your roadmap of this repo?

@dkenw yes, slowly we will get there


Update deps

It would be nice to push this, since the current gulp-pug-lint gaks on es6.

Oh, this is more than a year old.  :(


Add package comments

Some (all?) packages miss top level comment.
To be consistent, I propose using a separate file for that, say, doc.go.
#53

Package vmm (branches multi_backend and ir_unstable) has package comment inside doc.go.


Issue #1199: Fix synced folder examples in docs

While reading through the synced folder docs I also tested out one of the examples that seemed incorrect. NFS does not support dmode or fmode, and produces an invalid mount command. Also owner/group doesn't affect NFS.

Thanks!


Proposal: require ps -a to show swarm containers

If you do the swarm join in a container, you will end up with one line per node in docker ps on swarm join per node.
In this PR I propose to hide the swarm containers in docker ps.
They will be visible with docker ps --all

ping @ehazlett and @aluzzardi  what do you think ?

+1. I think it's confusing if you see it from a normal "ps". However, being able to restart, check logs etc is absolutely necessary.

Is it possible to log that it's explicitly hiding all swarm images, and tell the user if they want to see it please use -a?

@tnachen on the daemon you mean ?

+1

I think this needs to wait until we get a proper official image so we can filter that one exactly (instead of everything named "somethingsomething/swarm".

@aluzzardi +1 for official image :)

ok I updated the code, this should match only the official image. let's wait

@aluzzardi it's good to merge

LGTM


Little problem with the type hint

sqlalchemy does not exporse orm as a clear attr, so the type hint there is not working.
now we change that to this with full path.

And it works out with the type hint.
The main problem with that might be the use of some thing like db.session, which I use a lot in project to do CRUD operations. Previously we have that. It will stock since sa don't have orm attr. It's a module.
https://github.com/pallets-eco/flask-sqlalchemy/blob/d137db10e733daf1fd2ad24dd59aedc3072d48e5/src/flask_sqlalchemy/extension.py#L325

And I think we should make this little change to provide more type hint info.
Environment:

Python version: 3.9.16
Flask-SQLAlchemy version: 3.0.3
SQLAlchemy version: 2.0.0 and above

It's a bug with pyright: https://github.com/microsoft/pyright/issues/3884. I'm willing to take the suggested fix of import sqlalchemy.orm as sa_orm.

It't not only sa.orm, but also sa.exc and sa.event. But they can adopt the rule to be like sa_exc and sa_event. OK?

Yes, that's what I meant.

Fixed in 3.0.4 which is now released. Thanks for the PR!


corrected exit tranisition animation with zoom

Hi,
I'm committing what we discussed in #176,
I've fixed the sample app, divided in two activities, and fixed the exit out animation while zoomed in the second activity.
We can delay the exit animation using finishAfterTransition() and un-zooming with some controls that I added to BIV.
Check it out, and let me know if it's good to commit. I want to try this in my app.
PS: I see some distorsion on Fresco, I see it has it's own animations method, we should try that,
I think, this lib should not fix the weirdness of Fresco, we integrated well with transition animation, that should be the end of it.

Hi @KirkBushman , thanks for your contribution!
The code looks fine to me, but I did some test, the result seems depend on the image, please test with this setting:
    companion object {
        private const val THUMB_URL =
                "http://img1.imgtn.bdimg.com/it/u=1520386803,778399414&fm=21&gp=0.jpg"
        private const val SOURCE_URL =
                "https://youimg1.c-ctrip.com/target/tg/773/732/734/7ca19416b8cd423f8f6ef2d08366b7dc.jpg"
    }

It happens because the height of the image is greater than the height of the view, so it tries to fit it using scale type, but the thumbnail scaleType and the mainView scaleType are not the same.
For a better result we should use ScaleType fixXY on both, but since SSIV extends View and not ImageView, our hands are tied.
it happens differently with this:
private const val THUMB_URL =
"https://preview.redd.it/k18ckrkhrzt31.jpg?width=640&crop=smart&auto=webp&s=32ee988aaf9dd0af480cc2df104e38fd8ce73b03"
private const val SOURCE_URL =
"https://i.redd.it/k18ckrkhrzt31.jpg"
We should find a way to handle the scale type in SSIV, but the project is dead, no commits since may of last year, ignored all issues. We should evaluate using a fork that handles scale type the standard way. What do you think.

Forking SSIV sounds not bad, you can try that :)

Wait, I can't tell if you're joking, I already have a fork of that, will you switch to a fork?

Ok, this is a more broad and complicated task, I'll do it as soon as I have time free

Hi @Piasy, long time no see, I was very busy during this month...
I started getting back to solve this problem once and for all, reworking SSIV, but I'm encountering difficulties: since SSIV is extending View directly and not ImageView, it's very different, and I always end up with some problem at the end.
I'll keep trying, and if desperate I'll move all the subsampling code in an external class that is working with ImageView like https://github.com/chrisbanes/PhotoView
But if anyone wants a quick fix for this type of problem, that works with both tall and wide images, you can watch my fork.
Since SSIV, by default uses a scale implementation very similar to fit center, and only works well with that, if you set both thumbnail to android:scaleType="fitCenter" you should see it working.

Hey it's me again.
I'm having some troubles with custom ImageViewFactory at the moment, can you read #187 and tell me what you think?
Maybe merge this till we can figure something out.


Move to Java 17

I have started to test the jberet project against Java 17 and Java 21: https://github.com/jberet/jsr352/blob/main/.github/workflows/jberet-main.yml#L24


pnpm build: "Type error: Expected 0 arguments, but got 1. "

Describe the bug
When trying to build the next.js app (pnpm build command), the process throws this error with exit status = 1.
To Reproduce
Steps to reproduce the behavior:

go to console
run "pnpm build"
wait for compilation
build fails due to the "type error"

Expected behavior
After checking the type declaration on your plugin, this error shouldn't happen since clearly the function allows arguments.
Screenshots

About (please complete the following information):

next-international version 1.0.1
Next.js version 13.4

Could you send your complete middleware.ts file or a reproduction link? I'm not able to reproduce the error in any project using next-international nor in the example: https://github.com/QuiiBz/next-international/tree/main/examples/next-app

Thanks for your prompt reply!
By the end, I've end up changing the format from .ts -> .js and it worked out.
I've basically copied your middleware.ts from the documentation:
`// middleware.ts
import { createI18nMiddleware } from 'next-international/middleware'
import { NextRequest } from 'next/server'
const I18nMiddleware = createI18nMiddleware({
locales: ['en', 'de'],
defaultLocale: 'de'
})
export function middleware(request: NextRequest) {
return I18nMiddleware(request)
}
export const config = {
matcher: ['/((?!api|static|.\..|_next|favicon.ico|robots.txt).*)']
}`

This seems to be an issue with your TypeScript config, as we have the same middleware.ts file in this example and it's working fine: https://codesandbox.io/p/sandbox/jovial-paper-skkprk?file=%2Fmiddleware.ts
I'll close the issue but feel free to send a reproduction that can showcase the same error!

Hello here!
Hope you're doing well!
I have the same error and switching the middlware file to js worked for me as well (thank you!) but it doesnt feel like the right way to do so .

Ok, I could make the build work using the same next config you use. But it still doesnt feel right to ignorebuilderrors and ignoreDuringBuilds:
 /** @type {import('next').NextConfig} */
const nextConfig = {
  transpilePackages: ['next-international', 'international-types'],
  eslint: {
    ignoreDuringBuilds: true,
  },
  typescript: {
    ignoreBuildErrors: true,
  },
  // Uncomment to set base path
  // basePath: '/base',
  // Uncomment to use Static Export
  // output: 'export',
};

module.exports = nextConfig;

Ok, I could make the build work using the same next config you use. But it still doesnt feel right to ignorebuilderrors and ignoreDuringBuilds:

We don't recommend at all to use eslint.ignoreDuringBuilds / typescript.ignoreBuildErrors, that depends on your project setup (in our case, we already run eslint & typescript in all the monorepo at once, so it's not needed to run it there too)


fix: Allow docker driver to properly use cache

This fix involves creating a new function for the BuildDriver trait called build_tag_push. In order to get the proper logic in place to make use of docker buildx, I had to create a separate function that would construct the build command to include all of the tags necessary for pushing. A default implementation of build_tag_push will be used for podman and buildah which was originally from the build command's functions. Now that we have custom logic for docker builds, we can take advantage of using the GitHub cache features without having the --load arg which had a big negative effect on build times. We can now also use docker for creating local oci-archive tarballs for local rebasing. Making use of the oci-archive will require the user to create a docker-container builder as it is not supported on the standard docker builder.
https://docs.docker.com/build/exporters/oci-docker/

Ok I think this is ready to be looked at


Embed watcher to monitor sass partials

Codecov Report

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

@@          Coverage Diff          @@
##           master     #7   +/-   ##
=====================================
  Coverage     100%   100%
=====================================
  Files           1      1
  Lines          25     65   +40
=====================================
+ Hits           25     65   +40

Impacted Files
Coverage Δ

src/index.js
100% <100%> (ø)
:arrow_up:

Continue to review full report at Codecov.

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


[Search] Question: Do Solr fields used in search need to be stored?

Hi,
I am currently investigating how we can break our quite big monolithic Solr index&stored Core into multiple smaller cores maintained by individual microservices.
The idea is that we will have index core, which would contain all the fields across the domain, but would have everything set stored=false. This will be maintained by our "Search team".
And then we will have multiple smaller services (possibly even not backed by solr) holding the data. These will be maintained by some other teams.
Would it be possible to still use the Search indexed only Core in Hue? Or will there be any limitations caused by the fact that data for the documents will not be available?
Thanks!

Shen stored=false, the content is not in the index, so you would need to build a link to the document as a field if you want to open it back. If you are doing just analytics and use facets mostly it should be less of a problem.

I am interested just in the widgets - Timeline, piecharts, barcharts, couter and drilldown analytics. I am quite ok that I will have just a very limited info in result/html result grid.


feat: removeAgent method

:tada: This PR is included in version 5.0.0-beta.19 :tada:
The release is available on:

npm package (@beta dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This PR is included in version 5.0.0-alpha.15 :tada:
The release is available on:

npm package (@alpha dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This PR is included in version 5.0.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


fix: heroku sections levels

This PR fixes an issue with the Heroku deploy sections levels where Heroku related sections are not located under Heroku.

yay! thanks ❤


Branch Protection Pattern

In GitHub UI i can create an Branch Protection with an Pattern.
So the branches not exists in this moment in the repo and will be protected after it created.
i studied your api but found only the protection of real existing branches.
i am right, and if is it possible to enhance the api ? Mayby with an String contructor in GHBranchProtectionBuilder ?
thanks
andreas

It might be possible.  It would depend on it being available as part of the Branch Protection API.  See if you can find it here: https://developer.github.com/v3/repos/branches/#update-branch-protection .


Calendar Graph

⚠ Please verify that this feature request has NOT been suggested before.

[x] I checked and didn't find similar feature request

🏷 Feature Request Type
UI Feature
🔖 Feature description
Current graph isn't optimized to show a lot of days (for example one year).
If it can show one year's data, It isn't so clear for user to understand it.
✔ Solution
Use this Calendar Graph library in JS to show a large period of time Uptime:
https://www.npmjs.com/package/calendar-graph
For each day, you should specify a count number, which is the number of heartbeats / max_heartbeats_in_day * 100 (this is my proposal).
❓ Alternatives
No response
📝 Additional Context
No response

hello,
i'd like to see the Overall Uptime, like UptimeRobot is doing in their status page :

And the calendar view :

Has this gotten anywhere?

Until now, nobody has provided a PR

Bump! This is super useful to have as a tab on status dashboards like BetterUptime.

@AlivaTH
Please refrain from posting +1 / requests for updates things on issues, as this makes issue-management harder.
Issues are for discussing what needs to be done how by whom.
We use 👍🏻 on issues to prioritise work, as always: Pull Requests welcome.

That graph looks like Github Activity chart Lol. I don't think this make sense to change the whole Chart UI for which the Uptime Kuma is famous.

uptime kuma is not famous for it. I think there is a misperception of reality here. Everyone single person that saw this graph of uptime kuma just scratched their head and the questions are always the same:

Why the hell is there only 40 minutes history on the graph
Where is the long term history (calendar)

@wzrdtales
I don't think your assumption is entirely true.
I assume Some people would like to not be as transparent with the public status of their system and would thus not like the last year of production outages to be displayed.
=> making the display option configurable is a better choice
@Zaid-maker
As long as this is configurable, such an alternate display mode is fine by me (https://github.com/louislam/uptime-kuma/pull/4419#pullrequestreview-1842405524)

I assume Some people would like to not be as transparent with the public status of their system and would thus not like the last year of production outages to be displayed.

Those some people probably have a lot of downtimes and lie to their customers. Customers want transparency, and honest providers that actually do the invest for the uptime want to give them the transparency. That is the default.


Accessibility testing of Masthead and Footer

User Story

As a [user role below]:
ibm.com user with visual impairments

I need to:
effectively navigate through ibm.com's header and footer

so that I can:
find my way through ibm.com

Additional information

Use tools like Chromevox for testing keyboard navigation and voice announcements
Any automated accessibility tests
Should report any issues as separate issues in Github

Acceptance criteria

[ ] Masthead and footer passes WCAG AA compliance

Plan to do this testing during sprint 21 code freeze.


fortune: 3.18.0 -> 3.20.0

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://repology.org/project/fortune-mod/versions.
meta.description for fortune is: A program that displays a pseudorandom message from a database of quotations
Updates performed

Version update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 3.20.0 with grep in /nix/store/777d3lnf4dm09g17r1954ahs1db66ykl-fortune-mod-3.20.0
found 3.20.0 in filename of file in /nix/store/777d3lnf4dm09g17r1954ahs1db66ykl-fortune-mod-3.20.0

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

5 total rebuild path(s)

5 package rebuild(s)

First fifty rebuilds by attrpath
ding
fancy-motd
fortune
gtypist
xcowsay

Instructions to test this update (click to expand)

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

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

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/777d3lnf4dm09g17r1954ahs1db66ykl-fortune-mod-3.20.0
ls -la /nix/store/777d3lnf4dm09g17r1954ahs1db66ykl-fortune-mod-3.20.0/bin

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

5 packages built:

ding
fancy-motd
fortune
gtypist
xcowsay

Maintainer pings
cc @Vonfry for testing.

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

5 packages built:

ding
fancy-motd
fortune
gtypist
xcowsay


GitHub Provider

Adds support for GitHub.
Merge blocked by: https://github.com/google/go-github/pull/1896#issuecomment-867236851
When auto merge is added to the github sdk, I'll add it to this PR as well and remove the fake auto merge in the e2e test.

@phillebaba @NissesSenap @bittrance ready for review

@NissesSenap thanks! :1st_place_medal:  I've responded/closed them. No changes made, but I agree with your thoughts on most of the comments.

@NissesSenap @phillebaba the auto_merge PR has been merged and released, but it only exposes information about AutoMerge in the response - not possible to set it. Seems like the API doesn't support it either.. Except through GraphQL: https://github.community/t/enabling-auto-merge-on-a-pr-using-the-api/150797/3
Any suggestions? Should I add a GraphQL client and try to build a mutation to do this? Haven't worked that much with GraphQL before.

If that's the case and we feel that we have to have the automerge feature in the initial support of github I would say yes.
I have done some small amounts of GraphQL and it's not so bad when you are on the client side.


luarocks install lua-resty-jwt fails

Luarocks installation fails.
In my ubuntu desktop machine:
$sudo luarocks install lua-resty-jwt
Warning: falling back to curl - install luasec to get native HTTPS support
Installing https://luarocks.org/lua-resty-jwt-0.1.10-0.src.rock
Error: Couldn't extract archive .: unrecognized filename extension
And in my Dockerfile (based on CentOS):
Step 6/11 : RUN luarocks install lua-resty-jwt
---> Running in dd206fdf553c
Warning: falling back to curl - install luasec to get native HTTPS support
Error: Unrecognized filename extension .
Installing https://luarocks.org/lua-resty-jwt-0.1.10-0.src.rock...
Using https://luarocks.org/lua-resty-jwt-0.1.10-0.src.rock... switching to 'build' mode
The command '/bin/sh -c luarocks install lua-resty-jwt' returned a non-zero code: 1

It appears that the rockspec is broken: https://luarocks.org/manifests/skylothar/lua-resty-jwt-0.1.10-0.rockspec
The source URL is set to 'file://.', whereas 0.1.9 is a repo URL: https://luarocks.org/manifests/skylothar/lua-resty-jwt-0.1.9-0.rockspec

I've been using 0.1.10-0 for about a yr with no problem.  Even rebuilt it about a week ago with no problem.
Needed to rebuild today and now having the same issue as stated above.
The manifest was changed in last ~week?  Can it be rolled back?

@gimbel0893 That seems unlikely, since 0.1.10-0 was released yesterday.
As a temporary workaround, I have pinned my version of lua-resty-jwt to >= 0.1.8, < 0.1.10.

Oops thanks for correction.  I wasn't specifying version so started grabbing latest from yesterday then.  Thanks much

😿 Sorry for the trouble.
Just released 0.1.10-1 to fix this problem.
I'll add some tests for installation check after a new version is released.

Thanks, it works.
$sudo luarocks install lua-resty-jwt
Warning: falling back to curl - install luasec to get native HTTPS support
Installing https://luarocks.org/lua-resty-jwt-0.1.10-1.src.rock
lua-resty-jwt 0.1.10-1 is now installed in /usr/local (license: Apache License Version 2)

Thanks! Works for me as well.


How to update data file from v2.0.0-rc to v 3.1

First of all thank you for this project, I think it currently the best embedded document db for .net.
I am currently using v2.0.0-rc in desktop application and want to upgrade to the last version.
But as it turned out v2.0.0-rc is not supported for automatic upgrade -  it just throws exception that db version 5 is unknown.
So I was wondering is there any other way to upgrade data file on application start (as application uses autoupdate - it downloads its last version from web).
I think about serializing collection to json and then load them to new data file,
but I am not sure how to reference and use v2.0.0-rc and v3.1 in the same application so that serialize data in v2.0.0-rc and then recreate db and load this data.
Could you please point me to direction how to do this update.
Thank you

This is possible to do. Check this StackOverflow Entry on the topic.
https://stackoverflow.com/questions/42715564/using-2-different-versions-of-the-same-dll

could you add the upgrade from 5 to 7 in the upgradecode?

Hi! With the objective of organizing our issues, we are closing old unsolved issues. Please check the latest version of LiteDB and open a new issue if your problem/question/suggestion still applies. Thanks!


Add support for suppressing members

Fixes https://github.com/microsoft/typespec/issues/4446

API change check
APIView has identified API level changes in this PR and created following API reviews.
Microsoft.Generator.CSharp


logging refactor

Current coverage is 91.85% (diff: 95.89%)

Merging #65 into master will increase coverage by 0.27%

@@             master        #65   diff @@
==========================================
  Files            22         23     +1
  Lines          2483       2480     -3
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
+ Hits           2274       2278     +4
+ Misses          155        148     -7
  Partials         54         54

Powered by Codecov. Last update 5c4a009...3f953e0


Docs: Add LoadBalancerClass to L2 Announcements

Now that https://github.com/cilium/cilium/pull/27976 merged, update the l2-announcements docs for LoadBalancerClass support

/assign


chore: added resource for tailwindCSS in UI generators

Fixes Issue : #1122

Changes proposed

Added Tailwind Awesome to Frontend -> UI Generators

Screenshots

Note to reviewers
This PR is a part of GSSoC'23

Hey @CBID2, I have written the description based on the information provided on the Tailwind Awesome website itself!
you can checkout the website's description here Tailwind Awesome

hey @CBID2, I have made the required changes kindly review it!

Hey @CBID2, I have written the description based on the information provided on the Tailwind Awesome website itself!
you can check out the website's description here Tailwind Awesome

Hey @kirtiraj22. I saw the link you provided. I still recommend making the change. More often than not, a website’s content doesn't always present things correctly whether it’s grammar or information about a topic, so it's crucial to critically evaluate it before accepting it. 😄

Collaborator
Apologies, I will ensure to be more cautious and evaluate the content thoroughly next time. 😄


[docs] broken link "security policy" in README.md

In the README.md file, the "security policy" link is broken:
For security issues, please first check our security policy

Find an open MR to fix this issue: https://github.com/rancher/rancher/pull/44770

Thanks @able8.
The broken link was fixed!


Adds additional file saving and plots results on a common axis

Not sure if this will be desired. Just adds a use of localfilesystem to create the images directory, such that it will get created if it doesn't exist. Saves more of the output figures to there, and plots some of the results on a common y-axis to make viewing on the same scale a bit simpler.
I had originally opened it here, https://github.com/twiecki/covid19/pull/4 but closed that to make one that utilized a common function for the plotting, rather than duplicating the code.

Why is it desirable to save figures by default?

Hi @twiecki you're right.  It's likely not desirable to save the figures by default.  I added a variable to save the additional figures, in the base python notebook.  Additionally in the bayes notebook, I added a parameter to the individual functions to provide control over whether the figures are saved or not.


Containerization chronicles 01

first blog post of the containerisation chronicles

the tests results are gonna come back negative because its already set for containers, so Im just gonna merge.


The 1Password CLI executable (op.exe) was not found in folder

System Details:
Windows 11
.Net 8.0.
Package Version 2.4.2
Error:
The 1Password CLI executable (op.exe) was not found in folder "C:\Users**USER\source\repos**SOLUTIONFOLDER**PROJECTFOLDER\bin\Debug\net8.0"
My Code:
var onePasswordManagerOptions = new OnePasswordManagerOptions(); var onePassword = new OnePasswordManager(onePasswordManagerOptions);
When the One Password Manager is instantiated I am getting that the CLI executable isn't present in the build directory. I moved the op.exe file into the folder just to try it out and it is found but the password prompt comes up instead of using the account that was added with all of the account information later.
Do you have to have the One Password CLI installed for this to work? Also should I expect the login prompt to pop up?

Sorry I misunderstood a few things. I didn't realize that I could put the path to the executable in the options. I did that and that part works. I also I didn't realize that using a Service Account token would negate the login. I was able to work with my 1Password admin and I now have a token and that part is working as well.

Glad you worked it out! :)


misspelling?

genetic.py
line 252
               child = Organism.getChild(parent1, parent1, self.mutationRate)
which should be
               child = Organism.getChild(parent1, # parent2, self.mutationRate)

Thanks for pointing that out...surprised it worked as written, but it definitely seems like an error!

Should be fixed now, sorry for the late response.


Netlify dev tries to resolve to a page when returning 404 from a function

Describe the bug
I have a FaunaDB CRUD API that I updated to pass on the exact HTTP status code from the database request so that I could catch 404 errors on the client. When my function returns 404, something (not my client code, probably netlify middleware - I checked the Network log in Chrome) initiates another function request that tacks on '.html' to my API route. Snippet of the output:
Request from ::1: GET /.netlify/functions/cart/279578027748229641
.
.
.
Response with status 404 in 204 ms. // This is the 404 that is correctly returned
Request from ::1: GET /.netlify/functions/cart/279578027748229641.html // A request to the same route plus '.html' follows immediately

This causes errors in code which is expecting numeric input for the id. It also forces me to return a non-404 error.
To Reproduce
Steps to reproduce the behavior:

Create a function that returns a 404 error
Execute the function in netlify dev
Observe the above behavior

Configuration
Here's my actual function code:
/* Import faunaDB sdk */
const faunadb = require('faunadb');

const q = faunadb.query;
const client = new faunadb.Client({
    secret: process.env.FAUNA_DB_SECRET,
    timeout: 30
});

exports.handler = async event => {
    const id = event.id;
    console.log(`Function 'read' invoked. Read id: ${id}`)
    return client
        .query(q.Get(q.Ref(q.Collection('carts'), id)))
        .then(response => {
            console.log('success', response)
            return {
                statusCode: 200,
                body: JSON.stringify(response),
            }
        })
        .catch(error => {
            console.log('error', error)
            return {
                statusCode: error.requestResult.statusCode,
                body: JSON.stringify(error),
            }
        });
}

Expected behavior
The 404 error gets returned to the client.
CLI Output
See problem description.

Reported also in https://github.com/netlify/cli/issues/695#issuecomment-725626061

Still affected by this bug via builders!
Seems like returning anything other than HTTP status code 200 from my builder results in receiving a JSON request body with the text: "Function is not an on-demand builder. See https://ntl.fyi/create-builder for how to convert a function to a builder."

@digitpain Do you have any public repository that can be shared so I can reproduce the issue?

Yes this is the repo I was referencing in the original issue: https://github.com/ercgrat/creator.urbanbasic.de

@ercgrat Thank you for providing the repo.
I tried this out locally with netlify-cli/10.15.0 & this issue doesn't seem to be happening anymore. There aren't any additional requests to the same route with .html

Note: I edited the code  here a bit to always return the error status as 404.
.catch((error) => {
    console.log('error', error);
    return {
        statusCode: 404,
        body: JSON.stringify(error),
    };
});

@danez I think this issue can be closed.


adding hooks in multiple router setup

hi! Thanks for the minimalist router, I love it. This might be a bit of a newbie question, but I'm unsure how to add the hooks if I setup the code with multiple routes. Also I wonder if it's possible to overrule specific hooks per route in this setup. For example I want to add a showLoader function for all the routes except 404.

Hello @flowen,
actually the hooks are added per route. For example:
router.on(
  '/user/edit',
  function () {
    // show user edit page
  },
  {
    before: function (done) {
      // doing some async operation
      done();
    },
    after: function () {
      console.log('Data saved.');
    }
  }
);

And because they are just functions you may extract them to a function definition:
var beforeHook = function (done) { ... };
var afterHook = function () { ... };

router.on(
  '/something',
  function () { ... },
  { before: beforeHook, after: afterHook }
);

router.on(
  '/else',
  function () { ... },
  { before: beforeHook, after: afterHook }
);

That way you may create single hook for all your routes and define a specific one for 404 pages.

alright, thank you for the answer!


added my folder

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

[ x]  🚀 Added Details
[ ]  🌟 stared the repo
[ ]  🐛 Grammatical Error
[ ]  📝 Documentation Update
[ ]  🚩 Other

Description
Add Link of GitHub Profile


Do you think you might be able to make it compatible with windows xp in the new update 32 bit

Note: for support questions, please use one of the following channels.
Reddit: /r/gbstudio
Discord: Join Chat
This repository's issues are reserved for feature requests and bug reports.

I'm submitting a ...

[ ] bug report
[ ] feature request
[ ] support request => Please do not submit support request here, see note at the top of this template.

Do you want to request a feature or report a bug?

What is the current behavior?

If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem

What is the expected behavior?

What is the motivation / use case for changing the behavior?

Please tell us about your environment:

Version: 1.0.0
Platform: [all | Windows | macOS | Linux | Other ]

Other information (e.g. detailed explanation, stacktraces, related issues, suggestions how to fix, links for us to have context, eg. stackoverflow, gitter, etc)

do you think you might be able to make it compatible im having a hard enough time trying to get this to work on my 2008 hp with vista and I can't upgrade to Windows 10 plus this project is for something old why don't you release for multiple versions of windows so more people can enjoy your project I love what your doing otherwise

@thomas-alrek

That unfortunately is not possible. Windows XP is no longer supported by Microsoft, and XP does not support the libraries and software needed to run GB Studio. You'll need to upgrade your machine if you want to use GB Studio.

@snes666 Windows XP is an 18 year old system that haven't been supported for years.
The project is built with electron, which also doesn't support Windows XP.


Issue43

Fix #43
Test URLs:

Before: https://v2--helix-sportsmagazine--headwirecom.hlx.page/
After: https://issue43--helix-sportsmagazine--headwirecom.hlx.page/

@icaraps
I am not sure why https://issue43--helix-sportsmagazine--headwirecom.hlx.page/blocks/header/leaderboard.js returns 404. The file exists in this branch https://github.com/headwirecom/helix-sportsmagazine/tree/issue43/blocks/header

There was probably a sync issue on hlx side. I updated the code bus manually with https://www.hlx.live/docs/admin.html#tag/code/operation/updateCode and it's in sync now.

Looks cool ! How should the navigation behave for the root page ?
Currently it looks like this one the official site:

Looks cool ! How should the navigation behave for the root page ? Currently it looks like this one the official site:

I added the horizontal subnav on the home page. I think other visual changes we should handle as a separate issue when we address the homepage and landing pages. We might want to discuss that with Erin and William as well.

I think other visual changes we should handle as a separate issue when we address the homepage and landing pages

Sounds good to me


Terminate called after throwing an instance of 'nlohmann::json_abi_v3_11_2::detail::parse_error'

Hello, I am trying to get this working on a Raspberry Pi 4B and have had some troubles. I get an error
terminate called after throwing an instance of 'nlohmann::json_abi_v3_11_2::detail::parse_error'
  what():  [json.exception.parse_error.101] parse error at line 1, column 1: syntax error while parsing value - invalid literal; last read: '<'
Aborted

I am using the 1.2.0 ARM64 on the latest Raspberry Pi OS lite [64 bit] but have also tried the ARMv7 file and the 32 Bit OS but got the same issues and am using the en_GB-northern_english_male-medium voice model. Using the --debug flag doesn't produce any useful information. I am using SSH but I don't see how that should effect it.

Running into the same error on x86_64.
The voice I'm using is: en_US-libritts_r-medium.onnx
Thank you in advance.

Hello,
I'm getting the same effect on:
RPI CM4 (64bit kernel, and 32-bit userland)
Intel x86_64
Both having the same error. No matter if I compiled from source, or used precombiled latest binaries. Tried using: pl_PL-gosia-medium.onnx

I was able to fix it by following the Running in Python section to download my model file. @pjarmuzek  @undrwater If you follow those steps does it work?

@BlackBatA8T
I've got both model and json files downloaded in the same dir where piper is located:
root@xxxxxx:/mnt/nand-user/temp/source/piper # ls
espeak-ng-data   libespeak-ng.so.1       libonnxruntime.so         libpiper_phonemize.so    libpiper_phonemize.so.1.1.0  piper                    pl_PL-gosia-medium.onnx.json
libespeak-ng.so  libespeak-ng.so.1.1.51  libonnxruntime.so.1.14.1  libpiper_phonemize.so.1  libtashkeel_model.ort        pl_PL-gosia-medium.onnx
root@xxxxxx:/mnt/nand-user/temp/source/piper # echo "test" | ./piper -m pl_PL-gosia-medium.onnx -c pl_PL-gosia-medium.onnx.json -f output.wav
terminate called after throwing an instance of 'nlohmann::json_abi_v3_11_2::detail::parse_error'
  what():  [json.exception.parse_error.101] parse error at line 1, column 1: syntax error while parsing value - invalid literal; last read: '<'
Aborted

@BlackBatA8T
Downloaded from: https://huggingface.co/rhasspy/piper-voices/tree/v1.0.0
It looks like that I got the wrong files downloaded.. Now after your message checked repo again, re-downloaded and it's fine. Piper correctly outputs the wav file :)

I was able to fix it by following the Running in Python section to download my model file then using it in the c++ binary. @pjarmuzek @undrwater If you follow those steps does it work?

Kind of. For some reason it doesn't find some of the voices to download. Example:
echo 'Welcome to the world of speech synthesis!' | piper   --model en_US-libritts_r-medium --output_file welcome.wav Traceback (most recent call last):   File "/srv/piper/bin/piper", line 8, in <module>     sys.exit(main())              ^^^^^^   File "/srv/piper/lib/python3.11/site-packages/piper/__main__.py", line 104, in main     ensure_voice_exists(args.model, args.data_dir, args.download_dir, voices_info)   File "/srv/piper/lib/python3.11/site-packages/piper/download.py", line 56, in ensure_voice_exists     raise VoiceNotFoundError(name) piper.download.VoiceNotFoundError: en_US-libritts_r-medium
That file is at the same hugging face URL from above, and follows the same convention for the 'lessac' voice. Some other voices such as 'joe' work, and others do not. I suspect it's a parsing error.

Actually, I downloaded the en_US-libritts_r-medium.onnx file and it is quite a bit smaller than the others. 40k vs ~61M for the ones that work. Perhaps some of the files were not correctly built?
Would that be better as a new issue?

is there any udate to this i am still getting this issue, i tried the solution about following the running in pythin and that led to a sepearte issue

THe same here too on a Jetson nano, arm64 binary. Tried several voices without any luck. Help would be really appreciated.

If your file is only 40K, you are probably downloading the huggingface web page about the file, and not the file itself.
URL for the page: https://huggingface.co/rhasspy/piper-voices/blob/main/en/en_US/libritts_r/medium/en_US-libritts_r-medium.onnx
URL for the file: https://huggingface.co/rhasspy/piper-voices/resolve/main/en/en_US/libritts_r/medium/en_US-libritts_r-medium.onnx
Notice the blob vs resolve difference.


Revert #528 as CI tool is not a sufficient reason to drop a PHP version

Then Travis supports PHP 5.3 on Precise/Trusty distributions

As Travis actually supports PHP 5.3 We have to see if we have a real reason to drop PHP 5.3, else we should revert #528 and keep the compatibility range of 2.6.1 for 2.7.0.

I've checked the code fro short array usage, found none in the src directory.
When I checked for PHP language level errors through PhpStorm, it showed me this:

All cases are OK, though (Website builder script uses deliberately PHP 7.x) and the test files aren't executed. If the test don't fail, it should be OK.


Disk Encryption Support

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

With security being critical within datacenter infrastructure having encrypted volumes adds an additional layer of protection of data loss in the case of theft or pre-boot attacks.
Describe the solution you'd like

I would be nice to have the option to enable LUKS encryption of the root volume during installation.

Any update on this?

This is a blocker for us to use Harvester on some projects as well.

Duplicated. Let's track https://github.com/harvester/harvester/issues/3129 instead.

@innobead my read of this issue is that it's for encryption of the host disk(s), whereas #3129 is for encryption of VM volumes

@tserong this is also my understanding. Due to policy reasons, I am unable to install Harvester on a bare metal node without full-disk encryption.
@innobead If this isn't something Harvester can/want to support, that's 100% fine. I want to make sure we're not closing something as a duplicate when it's not.
Can you either reopen this issue or remove the duplicate tag and be explicit that full-disk encryption on bare metal isn't considered?

Thanks for clarifying the context, as this was mistakenly regarded as the volume encryption feature.

It's somewhat straight forward to add a an optional LUKS envelope at install time. However, any thoughts on which key providers to support at boot time then? Anyone?
The initial implementation could be just "interactive passphrase on the console". But... In that case, it doesn't become usable for me before I also have network+ssh in initrd - since Hetzner don't provide console access by default.

For us, we'd be looking at having a hardware TPM handle key managment otherwise it doesn't scale.


Design and stub out identity service

Come up with high-level identity requests and responses.
Needs to be able to handle at least three use cases:

Proxy service for publicly auditable proofs
Third-party attestation server
Origin attestation server (really a subset of the above)

Attestation server is done by https://github.com/OriginProtocol/bridge-server/pull/28. We chose to move away from publicly-auditable proofs for now.