gclient sync fail for 'Could not find package matching arguments: Instance of 'OptionsRevision', OSType.mac, null'

Steps to Reproduce

I have successful built the flutter engine early this month.  But recently when I updated my android studio and build tools, I got error when execute gclient sync as follow. i have check the isses: 27963.  How can i solve the error?
Logs

HERBERTZHOU-MC0:engine herbertzhou$ gclient sync
Syncing projects: 100% (86/86), done.

________ running '../../../third_party/dart/tools/sdks/dart-sdk/bin/pub get' in '/Users/herbertzhou/develop/flutter/engine/src/tools/android/android_sdk_downloader'
Resolving dependencies...
Got dependencies!

________ running 'src/third_party/dart/tools/sdks/dart-sdk/bin/dart --enable-asserts src/tools/android/android_sdk_downloader/lib/main.dart -y --out=src/third_party/android_tools --platform=28 --platform-revision=6 --build-tools-version=28.0.3 --platform-tools-version=28.0.1 --tools-version=26.1.1 --ndk-version=19.1.5304403' in '/Users/herbertzhou/develop/flutter/engine'
src/tools/android/android_sdk_downloader/lib/main.dart:1: Warning: Interpreting this as package URI, 'package:android_sdk_downloader/main.dart'.
Downloading Android SDK and NDK artifacts...
Skipping Android SDK Platform 28, checksum matches current asset.
Skipping Android SDK Build-Tools 28.0.3, checksum matches current asset.
Skipping Android SDK Tools, checksum matches current asset.
Unhandled exception:
Bad state: Could not find package matching arguments: Instance of 'OptionsRevision', OSType.mac, null
#0      downloadArchive (package:android_sdk_downloader/src/http.dart:94:5)
<asynchronous suspension>
#1      main (package:android_sdk_downloader/main.dart:159:15)
#2      _RootZone.runUnary (dart:async/zone.dart:1379:54)
#3      _FutureListener.handleValue (dart:async/future_impl.dart:129:18)
#4      Future._propagateToListeners.handleValueCallback (dart:async/future_impl.dart:642:45)
#5      Future._propagateToListeners (dart:async/future_impl.dart:671:32)
#6      Future._complete (dart:async/future_impl.dart:476:7)
#7      _SyncCompleter.complete (dart:async/future_impl.dart:51:12)
#8      _AsyncAwaitCompleter.complete (dart:async/runtime/libasync_patch.dart:28:18)
#9      _completeOnAsyncReturn (dart:async/runtime/libasync_patch.dart:295:13)
#10     loadChecksums (package:android_sdk_downloader/src/checksums.dart)
#11     _RootZone.runUnary (dart:async/zone.dart:1379:54)
#12     _FutureListener.handleValue (dart:async/future_impl.dart:129:18)
#13     Future._propagateToListeners.handleValueCallback (dart:async/future_impl.dart:642:45)
#14     Future._propagateToListeners (dart:async/future_impl.dart:671:32)
#15     Future._completeWithValue (dart:async/future_impl.dart:486:5)
#16     Future._asyncComplete.<anonymous closure> (dart:async/future_impl.dart:516:7)
#17     _microtaskLoop (dart:async/schedule_microtask.dart:41:21)
#18     _startMicrotaskLoop (dart:async/schedule_microtask.dart:50:5)
#19     _runPendingImmediateCallback (dart:isolate/runtime/libisolate_patch.dart:115:13)
#20     _RawReceivePortImpl._handleMessage (dart:isolate/runtime/libisolate_patch.dart:172:5)
Error: Command 'src/third_party/dart/tools/sdks/dart-sdk/bin/dart --enable-asserts src/tools/android/android_sdk_downloader/lib/main.dart -y --out=src/third_party/android_tools --platform=28 --platform-revision=6 --build-tools-version=28.0.3 --platform-tools-version=28.0.1 --tools-version=26.1.1 --ndk-version=19.1.5304403' returned non-zero exit status 255 in /Users/herbertzhou/develop/flutter/engine

HERBERTZHOU-MC0:engine herbertzhou$ flutter doctor -v
[✓] Flutter (Channel dev, v1.4.4, on Mac OS X 10.14 18A391, locale zh-Hans-CN)
    • Flutter version 1.4.4 at /Users/herbertzhou/develop/flutter/flutter
    • Framework revision 3b3f6c7a04 (30 hours ago), 2019-03-27 13:56:23 -0700
    • Engine revision 0d83a2ecd1
    • Dart version 2.2.1 (build 2.2.1-dev.2.0 None)

[✓] Android toolchain - develop for Android devices (Android SDK version
    29.0.0-rc1)
    • Android SDK at /Users/herbertzhou/Library/Android/sdk
    • Android NDK location not configured (optional; useful for native profiling
      support)
    • Platform android-28, build-tools 29.0.0-rc1
    • ANDROID_HOME = /Users/herbertzhou/Library/Android/sdk
    • Java binary at: /Applications/Android
      Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build
      1.8.0_152-release-1248-b01)
    • All Android licenses accepted.

[✓] iOS toolchain - develop for iOS devices (Xcode 10.1)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Xcode 10.1, Build version 10B61
    • ios-deploy 1.9.4
    • CocoaPods version 1.5.3

[✓] Android Studio (version 3.3)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin version 33.4.1
    • Dart plugin version 182.5215
    • Java version OpenJDK Runtime Environment (build
      1.8.0_152-release-1248-b01)

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

[✓] Connected device (1 available)
    • iPhone XR • A6ABD33A-78F5-4837-ADEE-7E9474E53A14 • ios • iOS 12.1
      (simulator)

• No issues found!

Have the same problem, it seems something wrong about Android NDK.

Have the same problem, it seems something wrong about Android NDK.

@ryansong did you solved this problem?

Hi, just want to check if this is still a problem for you.

Without additional information, we are unfortunately not sure how to resolve this issue. We are therefore reluctantly going to close this bug for now. Please don't hesitate to comment on the bug if you have any more information for us; we will reopen it right away!
Thanks for your contribution.

The android development tool version configured in the flutter DEPS file could not be found.
Modify the src/flutter/DEPS file
{
'name': 'download_android_tools',
'pattern': '.',
'condition': 'host_os == "mac" or host_os == "linux"',
'action': [
'src/third_party/dart/tools/sdks/dart-sdk/bin/dart', # this hook must be run after the dart hook.
'--enable-asserts',
'src/tools/android/android_sdk_downloader/lib/main.dart',
'-y', # Accept licenses
'--out=src/third_party/android_tools',
'--platform=28',
'--platform-revision=6',
'--build-tools-version=28.0.3',
'--platform-tools-version=29.0.5',
'--tools-version=25.2.5',
'--ndk-version=21.0.5935234'
],
},
Android:  https://dl.google.com/android/repository/repository2-1.xml
gclient sync is ok?

@escamoteur @iapicca Finally,I solved this problem. The main reseason is the version of ndk. In other project i use standalone ndk version. so I add the path in  ~/.bash_profile. When I remove this standalone ndk path form ~/.bash_profile, gclient sync finally make success.

I'm glad you solved the problem @zhouyuanbin
thank you for letting me know


Using counter_cache without params[:id]

One of the models in my app uses a uuid in its show route instead of an id, so when I enable counter_cache, nothing happens. Are there any workarounds for this kind of setup?

@franktisellano  - see URL below
https://github.com/charlotte-ruby/impressionist/wiki/Impressionist-and-vanity-URLs-(working-with-models-that-use-to_param)

I also ran into same issue.
If all of the relevant models use uuid as an id,
changing type of impressions.impressionable_id and impressions.user_id to uuid works for me.
Above link seems unrelated.


How to set a blender model right ?

Hi guys,
I have your Unity project running with Leap motion: check.
I updated the blender python env installing websockets (and aiohttp): check.
Successfully loaded the blender module: check.
Now, how do I name the bones in the blender model to see them moving according to my hands movements?
Thank you

If I remember correctly you just need to have an armature.
Once the armature is selected in the Leap Plugin Window you should be able to see different bones inside that armature where you can set the metadata in the Track Settings tab.

Thanks for you response, I really appreciate it. My friend recently gave me a Leap Controller and I try to get the most value out of it.
I'm not able to see the plugin panels, my plugin installation might be incorrect. The plugin server is running though, as I connect to it from the Unity project without errors.
In the blender console, I  have this messages:
SettingsPanel is a leaf class
ForceStart is a leaf class
MainLeapPanel is a leaf class
BoneSelectProperty is a leaf class
TrackSettings is a leaf class
RecordProperties is a leaf class

This errors come from general_helpers.py.
Do you know what it is about ?

It seems that the plugin is running then, there should be a leap tab on the right.
That is not really an issue. Classes need to be registered in a Blender plugin and to avoid a lot of boilerplate redundant code I registered them in a tree like manner. That means I only registered the base class and its dependencies (_classes inside the RegisterMixin), and these in turn register their dependencies until a they arrive to a leaf class.
Those log messages were just used as an informative setup print that were left during development.

You are right ! I had to add an armature and goes into Pose mode to see the Leap panel pop !
Thanks again


Find Number Type 1

Enter calculator name -
Number Type Finder
Describe calculator functionality -
Given a number entered by the user, find if the number is -

Armstrong Number
Kaprekar Number
Automorphic Number
Perfect Number
Amicable Number

NOTE - Create a multi-select dropdown list for the user to select which number type he wants to find.
Under which category you wish to place it -
[x] Computer Science
[] Mathematics
[] Physics
[] Chemistry
[] Biology
[] Finance
[] Scientific
[] Health
[] Sports
[] Let project owner decide
[] Suggest a new category - (Answer here)

I would like to work on it, please assign it to me.

Hey @ashishnallana,
Assigned.
You may contribute your code under the folder path -
calc_for_everything\calculators\src\computer_science\number_type_finder
Issue completion deadline - 4th Oct 8:00:00 am IST
NOTE - In case the issue completion deadline is not met, the issue will be assigned to a new participant


Cannot read property 'manifest' of undefined

cordova-universal-links-plugin 1.2.1 "Universal Links Plugin"

cordova build
Android Studio project detected
(node:21980) UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id: 1): TypeError: Cannot read property 'manifest' of undefined
(node:21980) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

cordova platform version android
Installed platforms:
android 7.0.0
Available platforms:
browser ~5.0.1
ios ~4.5.4
osx ~4.0.1
windows ~5.0.0
www ^3.12.0

cordova --version
8.0.0

npm --version
5.6.0

node --version
v8.9.3

Is there any workaround till this get merged ?

@okaufmann look at the change of @walteram.
It worked to me, only changing the path to store manifest.

Do I need to use his version of this plugin or move the AndroidManifest.xml file to the old path? I'm confused...

@okaufmann you can use the changed version of the plugin. since it's not merged in the nordnet repository, you must remove the plugin and install again using:
cordova plugin add https://github.com/walteram/cordova-universal-links-plugin

@walteram why dont you make a pull request?   your code  is working! Thank you! you save my life ❤

thanks @walteram :+1:

I changed a bit @walteram pull request to be backward compatible

Can this be merged at some point in the future, or an equivalent change made in the main branch, or is there some other plan? It's a little unsettling to have to be using a third party's fork.

Node version: v8.11.2
Cordova version: 8.0.0
Android version: 8.0
I Still got this. "UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id: 1): TypeError: Cannot read property 'manifest' of undefined"

Any news? Looks like a new release just needs cutting?

This update needs to be pushed, I was adding the plugin and literally ran into it, seems like bad support that new users will just face this issue right off the bat and then have to resort to a third party branch.

Same here, added the plug-in and bam, can't run my app. This is a showstopper guys...


feature(ion-item-sliding): Allow item also to swipe from left to right

From @astec on November 1, 2015 2:46
I want to swipe my ionic list items to both side. (i.e left-right AND right-left). It work perfectly for right-left swipe but i am not able to swipe my list item left-righ (to see buttons on left side).
Here is an example workaround: http://stackoverflow.com/a/31816296/1975086
Copied from original issue: driftyco/ionic2#411

Do you think I can do a pull request with my answer? People keep asking me for my solution, but the way it was made it won't let people update ionic without loosing the feature.

+1 for this feature. Both native iOS and android support both sides swiping for items.

Did this code make it into beta? I would love to see this extended to the entire list instead of just the list-items like in Google Now.

@thomastthai @masimakopoulos @pcagica https://github.com/driftyco/ionic/pull/6686

Thank you for updating. How would I get the change locally before it is
merged into the main branch?
On May 28, 2016 3:24 AM, "Manu Mtz.-Almeida"<EMAIL_ADDRESS>wrote:

@thomastthai https://github.com/thomastthai @masimakopoulos
https://github.com/masimakopoulos @pcagica https://github.com/pcagica
#6686 https://github.com/driftyco/ionic/pull/6686
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/driftyco/ionic/issues/5073#issuecomment-222301396,
or mute the thread
https://github.com/notifications/unsubscribe/APxEZV_Gc-s5-67pcygpUYeKCQli45Glks5qGBfNgaJpZM4HHUVA
.

Also, is the code adaptable to being able to swipe the entire list left or
right in addition to the list items?
On May 28, 2016 3:24 AM, "Manu Mtz.-Almeida"<EMAIL_ADDRESS>wrote:

@thomastthai https://github.com/thomastthai @masimakopoulos
https://github.com/masimakopoulos @pcagica https://github.com/pcagica
#6686 https://github.com/driftyco/ionic/pull/6686
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/driftyco/ionic/issues/5073#issuecomment-222301396,
or mute the thread
https://github.com/notifications/unsubscribe/APxEZV_Gc-s5-67pcygpUYeKCQli45Glks5qGBfNgaJpZM4HHUVA
.

Take into account RTL: https://github.com/driftyco/ionic/issues/5035#issuecomment-223039318

@astec @thomastthai the two way sliding will arrive in beta9, it will support having two different sets of buttons at the same time (side left/right), right side will be the default one, so expect it to be back compatible.
It has been improved a lot in general, it will behave more like a native app.
also, you will be able to subscribe to new events like (ionDrag) and (ionSwipe) and implement things like this very easily.

The animation below is 100% CSS, so you can customize it.
    <ion-item-sliding #item>
      <ion-item>DOWNLOAD</ion-item>

      <ion-item-options (ionSwipe)="download(item)">
        <button primary (click)="archive(item)">
          <ion-icon name="archive"></ion-icon>Archive
        </button>
        <button secondary swipeable (click)="download(item)">
          <ion-icon name="download"></ion-icon>Download
        </button>
      </ion-item-options>

      <ion-item-options side="left" (ionSwipe)="unread(item)">
        <button secondary swipeable (click)="unread(item)">
          <ion-icon name="ios-checkmark"></ion-icon>Unread
        </button>
      </ion-item-options>

    </ion-item-sliding>

@manucorporat, that's cool!

https://github.com/driftyco/ionic/pull/6686 was merged, available in next release!

Thank you for the work you did.
On Jun 8, 2016 12:33 PM, "Manu Mtz.-Almeida"<EMAIL_ADDRESS>wrote:

#6686 https://github.com/driftyco/ionic/pull/6686 was merged, available
in next release!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/driftyco/ionic/issues/5073#issuecomment-224702293,
or mute the thread
https://github.com/notifications/unsubscribe/APxEZX4AqU6dtoDEJQFd6hJJkCQYgcXCks5qJxkfgaJpZM4HHUVA
.

@manucorporat way to go buddy! Keep up the amazing work guys!


Use && rather than || for logout redirect logic

Overview
I noticed a bug in the logout redirect logic which is that a redirect
should happen if

the current route is NOT the main route, '/'
AND
the current route does NOT start with '/facilities`, as it would for
the facilities version of the main route and the facility details route

The previous OR logic would be true and cause a redirect if just
pathname !== mainRoute was true, which meant it would redirect from
the facilities and facility details routes.
Connects #343
Testing Instructions

serve this branch and login
on the / route, logout and verify that you are not redirected
from /facilities, logout and verify that you are not redirected
from a facilities details page, logout and verify that you are not redirected

From the following pages, logout and verify that you are redirected:

contribute
profile
lists
list details

Looking at this now

Thanks!


Alternative to using shell

Is there an alternative to shell of opening a link into the default browser?
I'm asking because shell or any electron native objects are not recognized by jest, and the tests are NOT passing.
This question is related to 1228

Hey @muscaiu, try giving a look at this and this

Thanks, i've actually decided to separate all electron components from react components, so now the tests are passing.


Error Redeeming Bond: Step 2/6 - "Number can only safely store up to 53 bits"

Description:
Redemption crashes on Step 2/6 while following standard behaviors, throws this message:
Error redeeming bond
We’re waiting for you to confirm invoice details in your Wallet.
Number can only safely store up to 53 bits
https://dapp.test.tbtc.network/deposit/0x3cAf685693B3e029e53D9C0e5EfE35691Cb5eE47/redemption
Steps to reproduce the behavior:
1)Go to dapp.test.tbtc.network
2)Click redeem (takes you to dapp.test.tbtc.network/redeem)
3) Click ‘connect to a Wallet’ button, click metamask, login to metamask, click ‘Connect’ in metamask
4) User enters a valid TDT ID in first text box, green checkmark appears
5) User enters a valid BTC address in second text box, green checkmark appears
6) Click Redeem
Expected behavior:
dApp continues to Step 2 without error
Environment details:
OS: macOS, macOS 10.15.5 (19F101)
Web Browser: Brave Version 1.10.97 Chromium: 83.0.4103.116 (Official Build) (64-bit)
Wallet: Metamask (browser-integrated)
Additional context:
Add any other context about the problem here.
Screenshots
If applicable, add screenshots to help explain your problem and any console log files.

53Bitx.txt

Found the issue here, and captured it as keep-network/tbtc.js#57. Closing this issue in favor of that one.


Annotation to skip resource deletion

Command

[ ] check-image-updates
[X] delete
[X] deploy
[ ] diff
[ ] helm-pull
[ ] helm-update
[ ] list-images
[ ] list-targets
[ ] poke-images
[X] prune
[ ] render
[ ] seal
[ ] validate
[ ] version

Who are you?
No response
What do you want to do?
.
Why do you need that?
In GitOps any wrong action can delete whole environment, but we can easily revert this and everything will be deployed back, except persistent data. So we need feature like kustomize.toolkit.fluxcd.io/prune: disabled in Flux that can prevent namespace with PVC deletion and same PVC will be connected at service deploy.

And couse of Klu replaces helm, it should also accept helm's annotation "helm.sh/resource-policy": keep.

In native Kluctl (not Flux), this annotation does that -- https://kluctl.io/docs/reference/deployments/annotations/all-resources/#kluctlioskip-delete
Not sure if that works with Flux though.

Ah, accepted! Sorry for the inattention!

Not sure if that works with Flux though.
The controller doesn't use kluctl under the hood?

Also does Klu checks for helm's annotation? I don't see that helm-integration overrides helm's annotation with own to keep protection.

The controller uses kluctl under the hood, but as a library and not as an executable.
Kluctl does currently not know about that helm annotation, but I can look into supporting it.

Another interesting with flag –force-replace-on-error, will it allow to delete protected resource? I think it shouldn't bypass especially setted protection via annotation.

So I will can use forceReplaceOnError at controller side for conflicts and don't worry that it will can also delete my protected PVCs.

--force-replace-on-error and forceReplaceOnError will cause deletion+recreation of resources. This is useful for immutable objects, e.g. Jobs. It will override ignore kluctl.io/skip-delete and helm.sh/resource-policy and ALWAYS delete the resource.
Regarding helm.sh/resource-policy, it's not implemented yet, but definitely makes sense to have it. I'll add it in the next version.

I understand the reason/utility of flags, but should it really bypass the especially setted by user protection?

@lictw Ah, now I get what you mean. My assumption was that a user would only use --force-replace-on-error when he exactly knows what he is doing. But that is a naive assumption as I realise just now. I'll change it to always respect the annotations.


Improve Crates.io rate limiting response display

In https://github.com/rust-lang/crates.io/pull/1596 it was added
a rate limit for crate publishing endpoint connections (10 components/min).
As is said in the PR. The strategy used allows to upload 10 components
first and then the ratio starts to be applied.
Now, if the rate is surpassed, crates.io returns a 429 HTTP response.
Cargo, tries to publish all of the workspace/crate components as fast
as possible (as we should expect) but when we have more than 10
components and we try to publish the 11th, usually a minute hasn't
passed yet and therefore we get a HTTP-429.
This made some users to experience confusing/not well explained error
messages as seen in https://github.com/rust-lang/crates.io/issues/1643.
The limit got increased to 30 components/min. But who knows..
So this closes https://github.com/rust-lang/cargo/issues/6714 while
a better solution is not found.

r? @Eh2406
(rust-highfive has picked a reviewer for you, use r? to override)

r? @Eh2406
(rust-highfive has picked a reviewer for you, use r? to override)

I don't know if hard coding this error message is a good plan. For one thing what happens if a user is publishing to an alternative registry? ( But the next message is also only for crates.io. So maybe I don't have all the context.) For another thing crates.io may change its policy, and so this won't be correct.
Is there context I am missing? Or, can we make a more generic message? Or, can we use some data from the response?

I don't know if hard coding this error message is a good plan. For one thing what happens if a user is publishing to an alternative registry? ( But the next message is also only for crates.io. So maybe I don't have all the context.) For another thing crates.io may change its policy, and so this won't be correct.
Is there context I am missing? Or, can we make a more generic message? Or, can we use some data from the response?

Hi @Eh2406  thanks for the feedback.

Is there context I am missing?

In respect of the context I think @carols10cents is the one who ask for. She'll know much better than me (I just tried to fix the issue and read across some of the issues and PRs related.

For one thing what happens if a user is publishing to an alternative registry?

You're right on the crates.io check and the alternative registry. Added self.host_is_crates_io() check for it.

For another thing crates.io may change its policy, and so this won't be correct

In order to be tight to their policy, and be able to respond to any changes, my suggestion is to import cargo-registry and import:
https://github.com/rust-lang/crates.io/blob/master/src/publish_rate_limit.rs#L9-L22
When calling Default for it we can get the burst allowed and print it in the message. So it always gets updated with path and minor updates of the lib. And then we're always in sync with them. Is anything is removed or changed, we will notice since a new major version will be out.

Or, can we make a more generic message?

The error is quite specific indeed. 429 isn't a typical HTTP response code, so I don't see how we can make the error more generic.

Or, can we use some data from the response?

The response does not provide any useful info AFAIK as you can see in https://github.com/rust-lang/crates.io/issues/1643

my suggestion is to import cargo-registry and import

even if cargo-registry was being published regularly, that would make the error message up to date with when Cargo was built but what we need is the policy when Publish is run. If someone has an MSRV that means that they are using a Cargo that is from 2 years ago, they need todays policy not 2 years ago.

429 isn't a typical HTTP response code, so I don't see how we can make the error more generic.

Maybe we can get crates.io to include your text in the body of the message, or some metadata in the headers. If one day Cargo is going to respond to 429 by retrying, then we will need a Retry-After header to tell us how long to weight.
According to MDN it is for "Too Many Requests".  Please slow down to give the registry servers time to process. Check your registries documentation for what rates are acceptable." and if it is crates.io add " crates.io has its relevant documentation at ___" may work.

Hi @Eh2406. Thanks a lot for the suggestions.
About the import you're completely right.

Maybe we can get crates.io to include your text in the body of the message, or some metadata in the headers. If one day Cargo is going to respond to 429 by retrying, then we will need a Retry-After header to tell us how long to weight.
According to MDN it is for "Too Many Requests".  Please slow down to give the registry servers time to process. Check your registries documentation for what rates are acceptable." and if it is crates.io add " crates.io has its relevant documentation at ___" may work.

That's true, and indeed good idea. Since Cargo (at least now) publishes as fast as possible, we can include this generic error message here and attach the crates.io one if at some point they implement one (I'll try to do so).
In the relevant documentation section, what would you add? Since there's no mention to the maximum rate anywhere aside from the issues. So I guess that the crates.io GH repo link? Since the Cargo book doesn't have much stuff about it.
Thanks!

It would be great if they could document it someplace better then the issues. https://crates.io/policies feels like a good place, we could start with a PR to change that page as its source is just here I think.

Filed https://github.com/rust-lang/crates.io/issues/3229. Once it's closed and we know which link can we refer to, I think we're good to go and address your suggestions :smiley:

As it was said in https://github.com/rust-lang/crates.io/issues/3229 we can close this PR since the error is being returned from crates.io now in the headers and we already display them.
So closing this. @Eh2406 I think that as you said, we can close #9119 .

Thank you for all the work tracking down all the implications. While this PR did not get merged, your contribution did close a lot of issues!


Size hint for Chunks is wrong

The size hint for chunks is computed as follows:
fn size_hint(&self) -> (usize, Option<usize>) {
    let chunk_len = if self.items.is_empty() { 0 } else { 1 };
    let (lower, upper) = self.stream.size_hint();
    let lower = lower.saturating_add(chunk_len);
    let upper = match upper {
        Some(x) => x.checked_add(chunk_len),
        None => None,
    };
    (lower, upper)
}

However, this is incorrect. The stream combines many items into one, so it should divide the size hints by the capacity.

In #2611, lower in size_hint is fixed. But upper is untouched. I wonder if we should also change x.checked_add(chunk_len) to (x / self.cap).checked_add(chunk_len) or something like that.

Maybe size_hint for chunks should be something like this:
    fn size_hint(&self) -> (usize, Option<usize>) {
        let (lower, upper) = self.stream.size_hint();
        let len = self.items.len();
        let lower = lower.saturating_add(len) / self.cap;
        let upper = upper.and_then(|u| u.checked_add(len)).map(|u| u / self.cap);
        (lower, upper)
    }


Add release.yml to define changelog format for releases

Closes #83
Per https://docs.github.com/en/repositories/releasing-projects-on-github/automatically-generated-release-notes#configuring-automatically-generated-release-notes

We should probably have a breaking change category, although I would hope we don't have to use it.

The thing I don't necessary like about this approach is that it relies on the PR author/reviewer to ensure the labeling is applied.

Agreed, it is about the same as depending on the "conventional" commit messages to automatically determine the major/minor/patch. Either way, a human decides what the next version number will be based on the label. I am not sure if there is a way to prevent merges if there are NO labels :-/
I wonder if there is some way to "parse" all the handlers and auto-generate an "API" of sorts, that we could compare to a previously released version, then determine "programmatically" whether it was a patch, new feature or breaking change? We tried to do that in our terraform, but I always wonder whether it is missing things :)  Frankly, I think that is putting too much effort into release management, unless there is something that hashicorp uses that we could reuse.

I am not sure if there is a way to prevent merges if there are NO labels :-/

There's no branch protection settings in GitHub to prevent that. We can add another PR status check to the list, in theory.


BITMAKER-2333: estela-web: Project & Spider deploy views issues

Description

estela need a welcome message for empty project list page: implemented

Spider deploys needs to update to In Project/Spiders/Deploy: added welcome message to empty deploy list page

Add a real demo project to deploy:  scrapy's quotesbot spider added

Issue
https://tasks.bitmaker.dev/issues/2333
Checklist before requesting a review

[ ] I have performed a self-review of my code.
[ ] My code follows the style guidelines of this project.
[ ] I have made corresponding changes to the documentation.
[ ] New and existing tests pass locally with my changes.
[ ] If this change is a core feature, I have added thorough tests.
[ ] If this change affects or depends on the behavior of other estela repositories, I have created pull requests with the relevant changes in the affected repositories. Please, refer to our official documentation.
[ ] I understand that my pull request may be closed if it becomes obvious or I did not perform all of the steps above.

@JoseArmandoChavezQuijahuaman ready to review.


BUG - SLA policies model failling uniqueness test

Is there an existing issue for this?

[X] I have searched the existing issues

Describe the issue
I recently upgraded from v0.5.2 to v0.7.1 of the Zendesk package, and have successfully done a full refresh dbt run of all zendesk models since. I now receive a dbt test failure, saying that the sla_event_id column in the sla_policies model is not unique.
I have debugged this as best I can myself. The issue seems to be caused by a change introduced in v0.7.1 (absent from v0.7.0, still present in v0.8.0).
v0.7.0 has this join condition in the int_zendesk__sla_policy_applied model:
      and sla_policy_applied.sla_applied_at >= sla_policy_name.valid_starting_at
Since v0.7.1, it has been changed to this:
      and sla_policy_applied.sla_applied_at >= {{ fivetran_utils.timestamp_add(datepart='second', interval='-5', from_timestamp='sla_policy_name.valid_starting_at') }}
Relaxing the join condition in this way causes duplication in the join, and ultimately in the final model output, as indicated by the unque test fail.
Relevant error log or model output
[31mCompleted with 1 error and 0 warnings:[0m

[31mFailure in test unique_zendesk__sla_policies_sla_event_id (models/zendesk.yml)[0m
  Got 1406 results, configured to fail if != 0

  compiled SQL at target/compiled/zendesk/models/zendesk.yml/schema_test/unique_zendesk__sla_policies_sla_event_id.sql

Done. PASS=75 WARN=0 ERROR=1 SKIP=0 TOTAL=76

Expected behavior
Successful dbt test, as was happening under v0.5.2.
dbt Project configurations
  zendesk:
    +schema: zendesk
    +tags:
      - daily_04_utc
      - eu
      - prod_only
    intermediate:
      +schema: zendesk_staging
    sla_policy:
      +schema: zendesk_staging
    ticket_history:
      +schema: zendesk_staging

  zendesk_source:
    +schema: zendesk_staging
    +tags:
      - hourly
      - eu
      - prod_only

Package versions
packages:

  - package: dbt-labs/dbt_utils
    version: 0.7.6

  # will also import fivetran/zendesk_source as a dependency
  - package: fivetran/zendesk
    version: 0.7.1

  - package: fivetran/ad_reporting
    version: [">=0.2.2", "<0.6.0"]

  - package: calogica/dbt_expectations
    version: 0.4.7

  - package: dbt-labs/segment
    version: 0.6.0

What database are you using dbt with?
bigquery
dbt Version
installed version: 0.21.1
   latest version: 1.0.0

Your version of dbt is out of date! You can find instructions for upgrading here:
https://docs.getdbt.com/docs/installation

Plugins:
  - bigquery: 0.21.1

Are you willing to open a PR to help address this issue?

[ ] Yes.
[ ] Yes, but I will need assistance and will schedule time during our office hours for guidance
[X] No.

Hi @james-smith-bbm thanks so much for raising this issue and bringing the test failure to our attention. 👀
The code you pointed out is exactly where this duplication is happening. We originally added this join condition to help capture the sla_policy_name when it was not set at the same time as the actual sla_policy. We found there would be occurrences would be set just a few seconds before or after the sla_policy being set. This is why we have the 5 second window to capture these names.
However, as we can see from the failure in the test, this clearly is not working for all instances. I wasn't the biggest fan of this solution originally and believe there is a better way to keep the original logic we had previously while also capturing the sla_policy_name for each sla and keeping the uniqueness.
My first thought is to not leverage the sla_policy_applied.sla_applied_at in the join query and instead use a more accurate timestamp to join on. I believe sla_policy_applied.valid_starting_at would probably be more accurate. I have actually applied this change in a working branch and found the duplication issue to be resolved as well sla_policy_name being populated for each record.
Would you be able to try the below working branch as a dependency and let me know if you see the issue persist?
packages:
    - git: https://github.com/fivetran/dbt_zendesk.git
      revision: bugfix/sla_duplicates
      warn-unpinned: false

Hi @fivetran-joemarkiewicz, thanks for taking a look and confirming it's in hand. I tried that branch, but couldn't get past dependency version issues. We're on dbt v0.21.1, and it sounds like your branch requires a version of dbt-utils that's incompatible with this:
Running with dbt=0.21.1
Encountered an error:
Runtime Error
  Failed to read package: Runtime Error
    This version of dbt is not supported with the 'dbt_utils' package.
      Installed version of dbt: =0.21.1
      Required version of dbt for 'dbt_utils': ['>=1.0.0', '<2.0.0']
    Check the requirements for the 'dbt_utils' package, or run dbt again with --no-version-check

  Error encountered in /Users/james/PycharmProjects/data-engineering/dbt_bbm/dbt_modules/dbt_utils/dbt_project.yml

Error encountered in /Users/james/PycharmProjects/data-engineering/dbt_bbm/dbt_modules/dbt_utils

Hi @james-smith-bbm thanks so much for validating this issue is resolved on your end in the working branch. In the meantime, I will open a PR for this and ensure the fix will be integrated into the next 0.8.1 release of the package.
Feel free to follow this issue until release and thanks again for raising this issue with us!

Just wanted to provide an update here that the PR mentioned above will be reviewed during my teams next sprint (starting 3/9) and should be expected to be integrated into the next release following PR approval.


"cannot invoke an expression whose type lacks a call signature" on union of types both having this call signature

TypeScript Version:  2.0.3
Code
function foo ( arg: number[] | string[] ) {
    arg.find ( () => false ); // cannot invoke an expression whose type lacks a call signature
}

function bar ( arg: (number | string)[] ) {
    arg.find ( () => false );
}

Expected behavior:
Inside foo, arg is always an array, either of numbers or of strings, so I expect the find method to be recognized by the compiler.
Actual behavior:
It doesn't recognize it, and it throws a cannot invoke an expression whose type lacks a call signature error.
I don't see any good reason why inside bar the compiler understands that arg is always an array, but not inside foo.

Dupe of #10620 (second one today, after #11205)

Sorry about that. I didn't find them on my searches.


hello.o: error adding symbols: File in wrong format

yu@yu:~/Desktop$ /home/yu/toolchain/bin/riscv64-unknown-elf-gcc hello.o -o hello -march=rv64imac -mabi=lp64
/home/yu/toolchain/lib/gcc/riscv64-unknown-elf/7.1.0/../../../../riscv64-unknown-elf/bin/ld: hello.o: Relocations in generic ELF (EM: 62)
/home/yu/toolchain/lib/gcc/riscv64-unknown-elf/7.1.0/../../../../riscv64-unknown-elf/bin/ld: hello.o: Relocations in generic ELF (EM: 62)
hello.o: error adding symbols: File in wrong format
collect2: error: ld returned 1 exit status
How can I resolve it? Thank you so much!

This repository is about the use of the LLVM toolchain so the question might be better asked in https://github.com/riscv/riscv-gnu-toolchain directly.
As for your specific error: I suspect you forgot to set some flags like '-nostdlib' to prevent the linker form trying to link your installed standard library (e.g. X86 or AMD64) against the RISC-V object file which won't work. Take a look over at the CFLAGS and LDFLAGS in the Makefile of this repo: https://github.com/michaeljclark/riscv-probe/blob/master/Makefile


No comment on issue to show which unit tests you wrote for the second commit -2 pts

There was a comment in the code submitted for commit 2, however I have gone back and added a comment on the closed issue.


fix: remove unnecessary parens

A purely code-cosmetic fix to port_to_integer. The parens were not necessary and conflict stylistically with the port_to_integer definition above it.
I feel like I've had this same thing happen to me before when having mix format auto execute on save.
Note
Looks like my linter also removed some empty spaces. Nice. 🤷

Good catch! Thanks for the PR!


2/4 : Async load

2/4 : This PR brings support for asynchronous source loading.

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.2 out of 3 committers have signed the CLA.:white_check_mark: kriskowal:white_check_mark: dbousque:x: dodododo seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.

Tests for the new functionality is missing from this branch, hence the lack of coverage. Take a look at the full PR for async source loading + tests : https://github.com/thriftrw/thriftrw-node/pull/173

Let’s collapse these two changes so we can unlock continuous integration. Thank you for breaking these into more reviewable chunks, but we as a rule only land commits that pass tests so we can bisect regressions.

Also, please rebase. I fixed some issues on master separately.

The latests changes from master have been integrated. For the full PR with tests, we should switch to https://github.com/thriftrw/thriftrw-node/pull/173. I can also merge it in this PR if you'd like.

Thanks @dbousque. Please consolidate into one landable pull request and close the other. #173 is passing tests but has conflicts with master. It looks like I can stamp and land today, but I won’t be responsive through the rest of the month.

Thanks @kriskowal, hopefully we can make it today then :) I just merged the tests PR in this one. This PR should be up to date with thriftrw-node:master.

Can I ask you to look into the conflicts? Either merge or rebase with master? According to the UI on Github, it’s not yet free of conflicts.
Either way, we are going to squash to land.

Weird, I don't see that, and I just merged master in the branch 🤔. Maybe I should squash already?

Apparently there was a mishap on my part, do you still have conflicts now?

This is what I see.

I brought it down locally and started a rebase on master. There’s a lot going on here but one of the things is that I added tests while reconciling the last set of changes, which now need to be indented into their new homes.
In any case, we’re under a release freeze until January. I’ll have some time to help out with this later this month.

@kriskowal I rebased and pushed, we should be conflict free now :)


Consider custom HRD Sample

Take email address, for example, to federate to two different upstream IdPs, rather than show nascar list of buttons.

Happy for you to work on a separate sample for this @josephdecock. It'd go under here, I guess:
https://docs.duendesoftware.com/identityserver/v6/samples/ui/


Simplify the manifest organization and data access

As discussed today, we should be able to parameterize execution of the workflow with just the list of SeriesInstanceUIDs and the version of IDC that should be used. We should also switch to using idc-index for resolving to series URLs and downloading the files.
This is dependent on update of idc-index to IDC v17, and other updates which I am working on in https://github.com/ImagingDataCommons/idc-index/pull/23.

I was able to pass the list of SeriesInstanceUIDs to papermill and to use idc-index. But as I imagine how these lists are passed on from Terra and Seven Bridges (SB-CGC), I realized that batching in SB-CGC is possible only by files. i.e previously I was passing the csv manifests to papermill on both Terra and SB-CGC. Now with the lists, we cannot run SB-CGC in batches without csv manifests..
one way to make this work is, we continue to use manifests for SB-CGC, but the papermill commands for Terra and SB-CGC will be different if we use list of SeriesInstanceUIDs
what do you think?

I am not sure I understand - I thought we keep using CSV, just change its content. I thought about this issue as about simplifying manifest - not getting rid of it.

I see. Getting rid of it makes sense for Terra users as they can simply import the sample data table we will provide. But with csv manifests..they will need to update the location of the csv manifests in the data table to get started.

I don't have the experience to weigh in, I am afraid .... But we should make sure IDC version is included as a column!

I forgot about the idc-version. I will add the column.
I think passing the list of seriesInstanceUIDs directly from the data table is the cleanest and most simplest approach. So if it is okay with you to use different papermill commands on Terra and SB-CGC, I'll this approach. Otherwise I can stick to the csv manifest approach.

So if it is okay with you to use different papermill commands on Terra and SB-CGC

Yes, it's ok - at least for now

I realized I could use the same papermill command but use an additional step for SB-CGC, which is just reading the manifest and passing the list of seriesInstanceUIDs to the papermill command.


Focused widget inside ScrollView should unfocus on tap. Fixes #4399

FocusBehavior._handle_post_on_touch_up() handles unfocus logic, taking in the consideration the list of ignored events, which should not trigger unfocus. Currently ScrollView makes any touch ignored by all focusable widgets. This happens in the ScrollView.on_scroll_start() - this method is called for every touch down event inside the ScrollView. Even the simple tap ouside of the currently focused widget will get ignored.
This PR changes behavior so that ScrollView will make focusable widgets to ignore only the touches, that resulted in the actual scroll - touch-and-drag events. So the tap outside the focused widget will be handled, and it will unfocus itself properly.

sv.handled being in touch is not guaranteed to mean anything. So we cannot rely on it. Checking ...[sv.handled]['x'] or ...[sv.handled]['y'] is also not reliable because even if it didn't fully scroll it probably shouldn't be used to defocus the touch. So maybe adding ...['sv.ignore_touch'] = True should be used instead.
In fact, there may be other cases where we should ignore the touch, but with your change it won't anymore. I believe https://github.com/kivy/kivy/blob/master/kivy/uix/scrollview.py#L646 is one such example.

sv.handled being in touch is not guaranteed to mean anything. So we cannot rely on it.

Oh, thats right. Thanks.

Checking ...[sv.handled]['x'] or ...[sv.handled]['y'] is also not reliable because even if it didn't fully scroll it probably shouldn't be used to defocus the touch.

Why? Checking ...[sv.handled]['x'] or ...[sv.handled]['y'] should do exactly the thing you said: "even if it didn't fully scroll it is not used to defocus" That means any touch+move is ignored by FocusBehavior._handle_post_on_touch_up().

In fact, there may be other cases where we should ignore the touch, but with your change it won't anymore. I believe https://github.com/kivy/kivy/blob/master/kivy/uix/scrollview.py#L646 is one such example.

Scrolling with mousewheel is ignored in the FocusBehavior._handle_post_on_touch_up(), so the line you pointed looks irrelevant to me. Mousewheel events will not defocus anything.

Why? Checking ...[sv.handled]['x'] or ...[sv.handled]['y'] should do exactly the thing you said: "even if it didn't fully scroll it is not used to defocus" That means any touch+move is ignored by FocusBehavior._handle_post_on_touch_up().

...

Scrolling with mousewheel is ignored in the FocusBehavior._handle_post_on_touch_up(), so the line you pointed looks irrelevant to me. Mousewheel events will not defocus anything.

This was just an example. You can see identical behavior even when not using the wheel. E.g. at https://github.com/kivy/kivy/blob/master/kivy/uix/scrollview.py#L759. That will not set touch.ud['sv.handled']['x'] to True, yet that touch should not be used for defocusing. Even though it didn't scroll. There's a difference between a touch that doesn't scroll and a touch that de-focuses.

Even though it didn't scroll.

This made me wonder what is the semantics of the ['sv.handled']['x']? Why it is False when overscroll happens? Shouldn't it actually be True? I would say that overscroll is still the scroll.

I didn't really write that code, so I'm not sure. But, whatever changes are made will need to retrace all the code paths to make sure it doesn't break corner cases.

I updated PR. Introduced sv.can_defocus flag, independent of sv.handled.


Branding

Someone that has artistic talent should probably take this otherwise the entire browser is getting it's artwork done in mspaint by me.

Not to say that I have a lot of artistic talent, but I made this new colourisation of the chromium logo inspired by the colours of hexavalent chromium, as a suggestion to replace the current one.

I mean it's a fine looking logo but the current one uses the material design and is much flatter. See https://en.wikipedia.org/wiki/File:Chromium_Material_Icon.png for instance.

I mean it's a fine looking logo but the current one uses the material design and is much flatter. See https://en.wikipedia.org/wiki/File:Chromium_Material_Icon.png for instance.

I based this coloration on the very same logo you linked. Only changed colours and a bit of brightness, contrast and saturation. Otherwise, it is the same design. The original also has these "shadows" that you see here and the colour gradient. What would you suggest to change?

I mean it's a fine looking logo [...]

I based this coloration on the very same logo you linked. [...]

It might just be me but it looks more like https://commons.wikimedia.org/wiki/File:Chromium_11_Logo.svg

It might just be me but it looks more like https://commons.wikimedia.org/wiki/File:Chromium_11_Logo.svg, which is the older logo. The current material logo is notably missing these shadows that give it this appearance.

You are right. Sorry, I had confused these two and overlooked those changes at first. Here is a version based on the newer material design logo with my colour suggestion.

These look great

otherwise the entire browser is getting it's artwork done in mspaint by me

i would love to see this

These look great

Glad you like it. I have made an icon file (from 256px to 16px) that you can use in the next build if you want.
hexavalent-icon.zip

Here is an icon based on Chromiums original icon. It is not 100% the same (in smaller) as the hexavalent logo above; but the Chromium icon is also slightly different both in its proportions and colours than their Chromium.svg. So I did the colouration anew instead of just scaling the one above down, in order to stick to the original icon proportions etc.
hexavalent-icon-2.zip


add some first-round custom styling

See these early mocks; could we start laying in some basic styling to make this more BNB-like?
Example Report:

Example Report mobile:

Example Sidebar nav for mobile views

I started work on this in the styling branch

Progress is coming along nicely!

exciting!

My WIP is on the styling branch. I was in the middle of doing the sidebar for this.


Move VideoModeScaleAt into internal/uidriver/glfw.

It's only used by GLFW, and has been in devicescale only to ease migration
to separate video mode vs content scaling.

Apparently the test bots fail. Please check the failures.

Fixed the one real error I found - but can you please fix the build bots? I admit I even stopped looking at them normally as they like 90% of cases run into a timeout during building, and another bunch of build bots fail because I have no access to them.

I can see the error like this:

But perhaps other accounts cannot see this. I'm looking for the settings to adjust the visibility...

Oh, when I explicitly look into them, I can see errors - but most fail with "Cancelled after 2m". The one that fails because I have no permission is Sourcehut, permanently spamming my email with failures.

Anyway, can SourceHut be disabled for PRs, and the timeout bumped higher from 2 minutes? That should resolve everything regarding the tests.

Anyway, can SourceHut be disabled for PRs, and the timeout bumped higher from 2 minutes? That should resolve everything regarding the tests.

One of the 'test' bots fails, all the test bots are suspended. Then this is not 'time out'.
SourceHut builds should not happen on PRs, but did you see some emails? That's odd...

I'll go to bed soon and merge this tomorrow. Thank you for your dedicating work!

Getting these emails on every commit: https://github.com/divVerent/ebiten/actions/runs/1235017943

Getting these emails on every commit: https://github.com/divVerent/ebiten/actions/runs/1235017943

Acknowledged. I'll forbid this action on a fork.

https://github.com/hajimehoshi/ebiten/commit/f665abc8d41a0196b093f04df6baa141c85bfd1c should fix this issue.


ValueError: array is too big; arr.size * arr.dtype.itemsize is larger than the maximum possible size

Hello, I am trying to use SHAP with an SVM text classifier and a big collection of documents.
Unfortunately when trying to compute explanations with SHAP, I struggle to compute the shap_values.
Is there a way to increase the maximum possible size ?

Thank you!

Apparently its due to insufficient memory on my machine.


Add an image for each product

You mentioned this yesterday and it seemed like a fun thing to do. Let me know if you don't like any of the images :)

Done, [sign] not as pretty now..


⚠ Spryr has degraded performance

In 3ce4d52, Spryr (https://spryr.com) experienced degraded performance:

HTTP code: 503
Response time: 5291 ms

Resolved: Spryr performance has improved in 9b60cc8 after 7 minutes.


Implement support for Based NFTs

✅ Checklist

[x] npx changeset was attached.
[ ] Covered by automatic tests.
o Not covered by automatic tests. Manually tested, Base NFT receiving, sending. Not necessary, since minimal changes.
[x] Impact of the changes:
o Minimal impact

📝 Description
Implemented support for Base chain (ERC-721 NFTs) in Ledger Live.
❓ Context
Suggestion by iNooked to add support for Base NFTs on Discord.

🧐 Checklist for the PR Reviewers

The code aligns with the requirements described in the linked JIRA or GitHub issue.
The PR description clearly documents the changes made and explains any technical trade-offs or design decisions.
There are no undocumented trade-offs, technical debt, or maintainability issues.
The PR has been tested thoroughly, and any potential edge cases have been considered and handled.
Any new dependencies have been justified and documented.
Performance considerations have been taken into account. (changes have been profiled or benchmarked if necessary)

base-nft-changeset.md

DRAFT - NEEDS MORE WORK! WORK IN PROGRESS

Unfortunately, the current Ledger Live renderer is incapable of handling Based NFTs, cause it causes tooo many API requests and get rate limited, then the vast amount of NFTs cause rendering to fail with duplicate keys and other issues, as demonstrated above.


CPU and Memory profiling and documentation have been added (P2)

What does this PR do (include background context, if relevant)?
This PR adds CPU and Memory profiling in Secretless and the associated documentation to get up and running.
What ticket does this PR close?
connected to #468
Where should the reviewer start?
Changes were made to the main.go and manager.go files. Reviewer should start with documentation to ensure the provided information makes sense and provides the proper guidance to get up and running.
What is the status of the manual tests?
To test, reviewer should attempt to explicitly add the flags to the terminal cmd when spinning up secretless (profile=cpu or profile=memory). Also, attempt to test by adding the debug flag (-debug) with and without the profile flag.
Have you run the following manual tests to verify existing functionality continues to function as expected?

[ ] Manually tested K8s CRDs
[ ] Manually tested Keychain provider
[ ] Manually run the K8s demo
[ ] Manually run Kubernetes-Conjur demo with a local Secretless Broker image build of your branch
[ ] Manually run the full demo (optional)

If this feature does not have any/sufficent automated tests, have you created/updated a folder in test/manual that includes:

[x] An updated README with instructions on how to manually test this feature
[ ] Utility start and stop scripts to spin up and tear down the test environments
[ ] A test script to run some basic manual tests (optional; if does not exist, the README should have detailed instructions)

Links to open issues for related automated integration and unit tests
Links to open issues for related documentation (in READMEs, docs, etc)
Screenshots (if appropriate)

@sigalsax I added a review bc this looked pretty done to me, but I'm just realizing the title still says WIP. is that accurate? if so, lmk when it's good for final review. if not, please remove the WIP from the PR title.

CPU profiling functionality dropped. Working on fixing this now


[FEATURE] Add a recheck button

Description
Hello:)
I think it is essential to have a recheck button that will re check the repo health.
I think it can be shown only to the owner of the repo( the user which added it).
Screenshots

Additional information
No response

I found the button! It was just visible for just the owner


Add netEstate NE Crawler to bot list

See github issue: https://github.com/WhichBrowser/Parser-PHP/issues/540

Coverage increased (+0.02%) to 99.97% when pulling 2d6889aaf71d34b1d63c069ac7d1ee201c17d37f on ayumi-cloud:netEstate into 880b9fa797401d14b28956442944c3daa70240ff on WhichBrowser:master.

Fixed by 52ba4ac58a2a496dca55cc88a3092ef392f90835

Fixed by 52ba4ac58a2a496dca55cc88a3092ef392f90835


external editor test

This is me entering text from an external editor. for a new issue

adding some additional text and testing formatting.
title text
then some more body text


Improved DOCX Update README.md

:question:

You don't liked my updated
On Wed, 30 Sep 2020 at 20:41, Romain Vimont<EMAIL_ADDRESS>wrote:

Closed #1799 https://github.com/Genymobile/scrcpy/pull/1799.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/Genymobile/scrcpy/pull/1799#event-3825043334, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AO6WTLR5UI3J2AJX742P2BLSINDDLANCNFSM4R7FHTMQ
.


Autofocus

Hi,
Is there a way I can turn autofocus off on the webcam?
Thanks.

Nope. There is no such possibility.

Thanks,
By the way great job with this project. It's being very helpful.
Saul.

Thank you @saulporras. Sorry for being unable to help you with this. Good luck!


[BUG] Variable names are displayed in the chat instead of their content

In the ingame chat windows, it is always printed "kills.toadvance" and "leading.onweapon" instead of the variable contents.

You need to copy lang folder
https://github.com/ssypchenko/cs2-gungame/tree/main/lang
to the same folder where your plugin.

Okay thanks for info the folder is present I just used your latest tag. But I did a german translation before and don't know exactly if there was a setting for it somewhere? Can't find it at least or is it in game?

Localisation does not work now. All outputs are in English only. I'm working to find the reason and fix it.

I have the same error , only that in the config.json file in /csgo/addons/counterstrikesharp/configs I have "ServerLanguage" set: "en"

@szogun1910 What "same" error do you have? Since v.1.0.6 the plugin does a correct translation if you have localisation files. You set the default server language to "pl". To be honest, I do not know how this affects the translation. I would advise you to make your own translation from English to Polish and put the pl.json file in the lang folder. This might solve your problem. Or temporarily change the server language to en and see how it affects you.


multiple clickup tasks in branch name

Task linked: DEV-258 read api calls

Task linked: DEV-257 library api calls

Task linked: DEV-256 Favorites api calls


Displays and allows roles to be editable by admins (sys_admin & admin)

Why
Admins need to be able to edit user roles.
What
Fixes #843

Displays user roles in the UI
Allows only sys_admin and admin roles to edit other users' role
Fixes a request spec that asserts a user's email can be updated
Makes rendering of a logo_url in the navbar conditional on an existing organization that is the instance owner and actually has a logo_url

How
See above
Testing
A couple of request tests were added but I didn't add any feature tests that would make assertions on what's rendered in the UI. I don't see feature tests used here so far but could add that if that's a direction the project is going.
Next Steps
N/A
Outstanding Questions, Concerns and Other Notes
I removed the User#role getter as it was not used anywhere in the codebase and was block the default Rails getter that would return the user's role attribute. Instead an ActiveRecord object was returned that was not useful.
Accessibility
N/A
Security
This PR allows admins to edit roles while following the existing constructs around authorizing users via Pundit.
Meta
N/A
Pre-Merge Checklist

[ ] Security & accessibility have been considered
[ ] Tests have been added, or an explanation has been given why the features cannot be tested
[ ] Documentation and comments have been added to the codebase where required
[ ] Entry added to CHANGELOG.md if appropriate
[ ] Outstanding questions and concerns have been resolved
[ ] Any next steps have been turned into Issues or Discussions as appropriate

@samudary hey there! this feature is very exciting!!! thanks so much for working on it. i'll be able to circle back to review this later this week during our next meeting. might you be around thursday evening to join us?

@maebeale Thanks, Thursday evening sounds good. I'll send you my personal contact details in Slack

@exbinary @maebeale Thanks again for the feedback! This is final ready for another review 😃


Upgrade to Spack's clingo concretizer

Fixes #327
Fixes #428
This PR switches to Spack's new concretizer which is based on the clingo answer set programming library.
Getting clingo on LC required binary packaging with the PyPA toolchain: https://github.com/joshessman-llnl/package-clingo-manylinux which is managed by testPyPI: https://test.pypi.org/project/clingo-cffi-wheel/
The next clingo release will be part of the "real" PyPI through clingo's maintainer, so this approach should be temporary.
Requires an Axom branch  (which itself requires a BLT branch) and a RAJA fork - presumably we'd want these changes to get merged in before merging this PR.
Upstream PRs:

[x] https://github.com/LLNL/axom/pull/494
[x] https://github.com/LLNL/blt/pull/449
[x] https://github.com/LLNL/RAJA/pull/999
[ ] https://github.com/LLNL/uberenv/pull/62
[ ] https://github.com/spack/spack/issues/23259

Codecov Report

Merging #417 (38c44dc) into develop (df91f32) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff            @@
##           develop     #417   +/-   ##
========================================
  Coverage    92.60%   92.60%
========================================
  Files           48       48
  Lines         2392     2392
========================================
  Hits          2215     2215
  Misses         177      177

Impacted Files
Coverage Δ

...tegrators/displacement_hyperelastic_integrator.cpp
84.37% <ø> (ø)

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 df91f32...38c44dc. Read the comment docs.

LGTM

Codecov Report

Merging #417 (cf0218c) into develop (8da52a0) will increase coverage by 0.21%.
The diff coverage is 100.00%.

@@             Coverage Diff             @@
##           develop     #417      +/-   ##
===========================================
+ Coverage    92.40%   92.62%   +0.21%
===========================================
  Files           48       48
  Lines         2423     2507      +84
===========================================
+ Hits          2239     2322      +83
- Misses         184      185       +1

Impacted Files
Coverage Δ

src/drivers/serac.cpp
90.00% <100.00%> (ø)

src/serac/infrastructure/input.hpp
100.00% <0.00%> (ø)

src/serac/infrastructure/input.cpp
96.21% <0.00%> (+1.31%)
: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 8da52a0...cf0218c. Read the comment docs.

This is ready to go, but should we hold out on MFEM 4.3 and/or Axom 0.5.0?


Unexpected key 'input' found

24 08 2017 20:41:26.839:ERROR [preprocessor.rollup]: Error processing “tests/unit/findIndex.js”

Unexpected key 'input' found, expected one of: acorn, amd, banner, cache, context, dest, entry, exports, external, footer, format,globals, indent, interop, intro, legacy, moduleContext, moduleName, noConflict, onwarn, outro, paths, plugins, preferConst, pureExternalModules, sourceMap, sourceMapFile, targets, treeshake, useStrict, watch

I get this after I updated to 5.x.x

Do you have Rollup 0.48 or higher installed?

Do you have Rollup 0.48 or higher installed?

thanks it works!


test/e2e: allow certain tests to be skipped in canary runs

Signed-off-by: Ray Harris<EMAIL_ADDRESS>

I'm not super familiar with the ins and outs of the Canaries but do the file name changes require any changes to the Canaries themselves on CICD's end?

It is a little difficult to know what is actually being changed as it looks like over 1000 lines are being updated. Should I assume it's basically the if inCanary lines added?

The file name changes won't affect CICD.
I tweaked the file name so that it's not such a mess.


Error in quickstart example

The quick start example (https://github.com/isar/isar#2-annotate-a-collection) contains an error and if you cut and paste the code it doesn't work.
The status property looks like this:
  @enumerated
  Status status = Status.pending;

However pending is not a defined value for Status:
enum Status {
  draft,
  sending,
  sent,
}

I think you should change pending to draft to make the example valid.

Fixed :)


Add a CUDA matrix of versions

Hi! This is the friendly automated conda-forge-webservice.
I've rerendered the recipe as instructed in #2.
Here's a checklist to do before merging.

[ ] Bump the build number if needed.

Fixes #2

@conda-forge-admin , please re-render

@conda-forge-admin, please re-render

@jakirkham Can we push this through the finish line?

@conda-forge-admin, please re-render

@conda-forge-admin, please re-render

@conda-forge-admin, please re-render

Thanks all! 🙏
Let's get these out so we can work on next steps 🙂
If anything comes up, please raise an issue


luamodules: add libuv lua binding luv.

Summary
Libuv lua binding: https://github.com/luvit/luv
Initial work done by Michael Mogenson as shown in LICENSE
Impact
No.
Testing

Moved luamodules to folder apps/interpreters/.


Document Known Issue in Repaving and Rolling Restarts for K8s (placeholder)

Known issue:
Kubernetes can take up to thirty seconds to let a connection fail when an IP address changes. This prevents the cluster from recognizing a node has been decommissioned for that thirty seconds, allowing some queries to fail.
@knz and @irfansharif, anything else to add here? There was an issue with the Admin UI as well?

There was an issue with the Admin UI as well?

Let's discuss over in https://github.com/cockroachdb/cockroach/issues/53773.

the KV issue to document as pitfall / known limitation is here: https://github.com/cockroachdb/cockroach/issues/53410


chore: next release

Add PrimitiveValue, also include in ClassDependencies type

Codecov Report

Merging #58 (178c8d9) into master (6e75624) will decrease coverage by 23.28%.
The diff coverage is 89.47%.

:exclamation: Current head 178c8d9 differs from pull request most recent head 8a78d96. Consider uploading reports for the commit 8a78d96 to get more accurate results

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
@@             Coverage Diff             @@
##           master      #58       +/-   ##
===========================================
- Coverage   97.26%   73.98%   -23.28%
===========================================
  Files           5        8        +3
  Lines          73      123       +50
  Branches       11        5        -6
===========================================
+ Hits           71       91       +20
- Misses          0       31       +31
+ Partials        2        1        -1

Flag
Coverage Δ

adapters.nestjs
73.98% <89.47%> (?)

core
73.98% <89.47%> (?)

jest
73.98% <89.47%> (-23.28%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

packages/testbeds/jest/test/spec-assets-nestjs.ts
48.93% <ø> (ø)

packages/core/src/main.ts
41.66% <41.66%> (ø)

...ackages/testbeds/jest/src/reflectable.decorator.ts
50.00% <50.00%> (ø)

packages/core/src/services/dependencies-mocker.ts
100.00% <100.00%> (ø)

packages/core/src/services/package-resolver.ts
100.00% <100.00%> (ø)

packages/core/src/services/testbed-builder.ts
100.00% <100.00%> (ø)

packages/core/src/services/unit-reference.ts
100.00% <100.00%> (ø)

packages/testbeds/jest/src/testbed-factory.ts
100.00% <100.00%> (ø)


AxisLineVector: GetDataLimits returns infinity even when limited by Min or Max

Bug Report
Issue:
Based on #1415, when a plot contains an AxisLine (in my particular case a HLineVector) with Min or Max property set and one calls GetDataLimits, the resulting AxisLimits should contain Min, Max instead of $+/-\infty$. For example when using a HLineVector with Min and Max set GetDataLimits should return something like ${AxisLimits: x=[Min, Max], y=[min(Ys), max(Ys)]}$ instead of ${AxisLimits: x=[-∞, ∞], y=[min(Ys), max(Ys)]}$.
Reproducing:
var formsPlot1 = new ScottPlot.FormsPlot();
var horizontalLine = new HLineVector()
{
          Ys = new double[] { 5 },
          Min = 1,
          Max = 10,
};

formsPlot1.Plot.Add(horizontalLine);
formsPlot1.Render();

var limits = formsPlot1.Plot.GetDataLimits();
Debug.WriteLine($"Limits:  xMin: {limits.XMin}, xMax: {limits.XMax}, yMin: {limits.YMin}, yMax: {limits.YMax}");

System Details

ScottPlot Version: 4.1.60
Operating System: Windows 10
Application Type: WinForms
.NET Version: .Net 6

Hi @ChrisAtVault, thanks for reporting this!
I think I solved it with #2381 but let me know if it doesn't perform as expected


Build Improvement and Modifications to CPP

Added a single build script to install CPP, PYARROW and PYTHON.
Also added flags to build the project in chosen build modes (release, debug)


[fix]: CI: Move lint target to integration.yml

lint-ci requires a reviewdog token, moving to the workflow with secrets in context
Test Plan

[ ] acceptance tests

[ ] …

References

Needs this: https://github.com/chanzuckerberg/terraform-provider-snowflake/pull/321 to be merged to fix the docs. That PR needed this PR to fix the lint.

/ok-to-test sha=0ce5802


No metrics in cdbstacks

I don’t get any metrics when using a .cdbstack file.  If I add the following to line 105 of DebuggerStackSource.cs, it seems to give the results that I would expect.
sample.Metric = 1;

Is this correct or am I missing something?
Thanks!

@wmascia can you share the file where you ran into this issue?

@brianrob it happens with any file but you can use this simple example.  The frames are detected but they have no metric value attributed to them.  Inc and Exc are both 0.  Inc% and Exc% are both NaN.
Note this also repros issue #1011 (the last stack isn't added).
test.cdbstack:

Call Site
A!foo
Call Site
B!foo


On Hold Incidents can accumulate and congest the dispatch queue.  Would be nice to be able to filter those out.

https://github.com/burningmantech/ranger-ims-mac/commit/fae7b0e552e8eede5b6bd6b123b01956af5d6a08 replaces the Show Closed checkbox with a Show: popup button that allows you to show all, open, or active incidents.
"Open" means all incidents not in Closed state.  "Active" means all incidents not in Closed or On Hold states.

Please verify with [Incidents 3.0a1] (https://github.com/burningmantech/ranger-ims-mac/releases/tag/v3.0a1).


Port/iFrame from Ember: Pipelines

In light of recent UI consolidation, we need to ensure that pages from Ember aren't lost when accessing them via Vue.
Ember location:  →  → Resource → Pipelines
Vue location: Use Cluster Manager

Closing - incorporated into #3300


Tx fee mixed with Gas used

Note:
For ~incoming~ outgoing transfers only, where the Tx Fee is displayed in the details.
It seems that the value displayed is being mixed with the Gas consumed in the transaction
Preconditions:
Have a safe and a wallet with funds to send tokens to it
Safe used for the test:
0x1d013f021a20872FA5223BF5a54eF8f0D528CC58/transactions
Check transaction ID 3
Steps:
1 - Send any amount of tokens to the safe
2 - Check the incoming transfer
3 - In the datails check the Tx Fee
4 - Compare that number with the one in Etherscan
Snapshot:

We can fix this by using gasUsed from web3.eth.getTransactionReceipt. Also maybe it's possible to store this on the backend. Wdyt @Uxio0 ?

We can fix this by using gasUsed from web3.eth.getTransactionReceipt. Also maybe it's possible to store this on the backend. Wdyt @Uxio0 ?

I can return it from the backend, I have it stored 👍
https://github.com/gnosis/safe-transaction-service/issues/45

Update on this ticket. The issue is now with outgoing tx's, the fee is not being diplayed there
URL:https://safe-team-rinkeby.staging.gnosisdev.com/app/#/safes/0x9913B9180C20C6b0F21B6480c84422F6ebc4B808/transactions


As an undocumented person, I need to enter information into the Portal to find relevant resources in a way that does not expose me to tracking by government agencies (ICE).

From @czdiana2321 on June 15, 2018 17:38
Copied from original issue: Microsoft/Access2Justice#158

@KellyeDC - This is not a priority for pilot.


Component reference for v1.25

This PR batch updates the references for Kubernetes components command line tools, generated using the gen-compdocs tool, based on the new release tags for kubernetes v1.25.

@tengqm please set a PR description - it might not be obvious to everyone what this is about.

@tengqm please set a PR description - it might not be obvious to everyone what this is about.

Done.

Preview: https://deploy-preview-36205--kubernetes-io-main-staging.netlify.app/docs/reference/command-line-tools-reference/kube-apiserver/

/lgtm

/approve


More consistent config path for Windows

change APPDATA to USERPROFILE

more consistent config path like .ipython, .matplotlib etc
failed "import mne" with ValueError: mne-python config file path could not be determined for plain user accounts in Windows Server 2003 (no APPDATA in os.environ for non-Administrator users)
In Widows 7 and newer APPDATA points to 'C:\Users\1\AppData\Roaming' - not so easy to find

taking over in https://github.com/mne-tools/mne-python/pull/4945


Behind a gateway nginx proxy, Error during WebSocket handshake: Unexpected response code: 404

I am trying to deploy this behind a reverse proxy (nginx), and i have other examples of my apis using socket.io that work when upgraded to wss, but for some reason i am seeing:
Error during WebSocket handshake: Unexpected response code: 404
on the webshockify call.
I am forcing all http traffic to be upgraded to https and i see everything working except for this wss://mydomain/webshockify call, here is my configuration so far:
server {
client_body_timeout         10m;
client_header_timeout       10m;
client_max_body_size 1000000M;
large_client_header_buffers 8 32k;
listen 443 ssl http2;
listen [::]:443 ssl http2;
send_timeout                10m;
server_name face.ocelot.work;
ssl_certificate /etc/letsencrypt/live/XX/fullchain.pem;
ssl_certificate_key /etc/letsencrypt/live/XX/privkey.pem;
fastcgi_buffer_size 256k;
fastcgi_buffers 8 128k;
fastcgi_read_timeout 300s;
add_header X-Frame-Options "";
proxy_buffer_size 128k;
proxy_buffers 4 256k;
proxy_busy_buffers_size 256k;
# proxy_set_header Proxy ""; # to mitigate httpoxy attack
location /webshockify/ {
    proxy_pass $upstream;
    set $upstream http://XX_container:80;

    proxy_http_version 1.1;
    proxy_set_header Upgrade $http_upgrade;
    proxy_set_header Connection "Upgrade";
    proxy_set_header Host $host;

    # enable sticky session based on IP
    # ip_hash;

    proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
    proxy_set_header X-Real-IP $remote_addr;
}
location / {
    proxy_buffer_size 128k;
    proxy_buffers 4 256k;
    proxy_busy_buffers_size 256k;
    proxy_pass $upstream;
    proxy_set_header   Host $host;
    set $upstream http://XX_container:80;
    proxy_ssl_server_name on;
}

I am too trying to deploy this image behind a reverse proxy (traefik) and I too get the same 404 error.
@lan10rd it's been a long while and you had no replies, have you perhaps found a workaround?

Hi, I am running ubuntu behind traefik / authelia (2FA).
docker-compose.yml:
  ubuntu:     image: dorowu/ubuntu-desktop-lxde-vnc:latest     container_name: ubuntu1     hostname: ubuntu1     dns:       - <IP_ADDRESS>       - <IP_ADDRESS>     volumes:       - /etc/localtime:/etc/localtime:ro       - /dev/shm:/dev/shm       - /share/homes/myusername:/home/myusername       - /share/mediaserver:/share/mediaserver       - /share/Multimedia:/share/Multimedia     environment:       - USER=myusername     labels:       - traefik.enable=true       - traefik.http.routers.ubuntu.rule=Host(ubuntu.mydomain.mytld)       - traefik.http.services.ubuntu.loadbalancer.server.port=80       - traefik.http.routers.ubuntu.middlewares=authme       - "traefik.http.middlewares.authme.forwardauth.address=http://<IP_ADDRESS>:9091"       - "traefik.http.middlewares.authme.forwardauth.trustforwardheader=true"       - "traefik.http.middlewares.authme.forwardauth.authresponseheaders=X-Forwarded-User"       - "traefik.http.middlewares.authme.forwardauth.address=http://<IP_ADDRESS>:9091/api/verify?rd=https://authelia.mydomain.mytld/%23/"       - traefik.http.routers.ubuntu.tls.certresolver=leresolver       - traefik.http.routers.ubuntu.entrypoints=websecure     restart: unless-stopped     network_mode: bridge
Launch script up.sh
`#!/bin/bash
docker-compose up -d
DOCKERID=docker ps | grep ubuntu1 | awk '{print $1}'
this fix seems necessary since focal (not necessary for bionic, where /resize endpoint is supported)
see pull request https://github.com/fcwu/docker-ubuntu-vnc-desktop/pull/247 (not clear why this was not committed by author)
docker exec -it $DOCKERID bash -c 'sed -i "/websockify)/ s/websockify)/websockify|resize)/" /etc/nginx/sites-enabled/default'
docker exec -it $DOCKERID bash -c 'grep websockify /etc/nginx/sites-enabled/default'
docker exec -it $DOCKERID usermod -u 1000000 myusername
docker exec -it $DOCKERID groupmod -g 1000000 myusername
docker exec -it $DOCKERID usermod -g myusername myusername
docker exec -it $DOCKERID usermod -a -G users myusername
docker exec -it $DOCKERID find /home/myusername -user 1000 -exec chown -h myusername {} ;
docker exec -it $DOCKERID find /home/myusername -group 1000 -exec chgrp -h myusername {} ;
`

I'm running this container successfully behind traefik / authelia (2FA).
Please see these two files "docker-compose.yml" and launch script "up.sh"
docker-compose.yml.txt
up.sh.txt

I'm running this container successfully behind traefik / authelia (2FA).
Please see these two files "docker-compose.yml" and launch script "up.sh"
docker-compose.yml.txt
up.sh.txt

Thanks! I don't see anything special about your compose file or your traefik labels. It the magic sauce in the up.sh?


Optimize blast unmatched

The script had a hight memory consumption, especially when handling 120 million lines files.

OK 👍


#76 Run command for tvac programs

This adds a "run" command to uts-cli which will take a program name and look for a toml file with that name from the current directory.
The command execs uts-run which it expects to find in the current directory.

It was going to need a refactoring to be able to call out to the program runner from uts-cli as an internal call as the API from different binary crates in rust aren’t visible to each other, so I took a quicker option of calling out to the uts-run binary. This does mean that the new run command expects to find uts-run in the same directory. I hope that doesn’t complicate distribution for the tvac test.

I'm going to merge this without having tested it on a real board yet, just to keep the branched code to a minimum.


Fixes Travis config

Coverage remained the same at 41.137% when pulling 3eb878c8d71442d09d35951e58994ab4730aabd2 on fix/travis-ci-config into c1da395070dc85fc6863078ec525c9e8e68c3b5f on master.


Not the same number of decimal places in response.

I get not the same numbers of decimal places:
thats what I get from a server:
{"resources":[{"id":2375,"account":{"id":1682},"creationDate":"2015-11-18T09:32:18","currencyCode":"CHF","mappingCode":"a83fb8c8-b0e6-4659-84f5-d9d19e0761b6","invoiceDownloadCount":0,"invoiceFromPeriod":"2015-11-01T00:00:00","invoiceFromPeriodDisplay":"2015-11-01T00:00:00","invoiceNumber":"Current running invoice...","invoiceToPeriod":"2015-12-01T00:00:00","invoiceToPeriodDisplay":"2015-11-30T23:59:59","simulationInvoice":1,"totalAmount":14.90,"totalAmountRounding":0.00,"totalNetAmount":13.80,"totalTaxAmount":1.10},{"id":2510,"account":{"id":1682},"creationDate":"2015-11-19T13:46:17","currencyCode":"CHF","mappingCode":"8d2020c5-6f02-47f9-ac38-67ed2389b01d","invoiceDownloadCount":0,"invoiceFromPeriod":"2015-10-01T00:00:00","invoiceFromPeriodDisplay":"2015-10-01T00:00:00","invoiceNumber":"68002510","invoicePayedOn":"2015-11-19T13:46:25","invoicePaymentDate":"2015-11-19T00:00:00","invoiceToPeriod":"2015-11-01T00:00:00","invoiceToPeriodDisplay":"2015-10-31T23:59:59","simulationInvoice":0,"totalAmount":20.05,"totalAmountRounding":-0.04,"totalNetAmount":18.60,"totalTaxAmount":1.49},{"id":2501,"account":{"id":1682},"creationDate":"2015-11-19T13:45:54","currencyCode":"CHF","mappingCode":"6c416563-6f34-4cf7-a9a1-67c142d699db","invoiceDownloadCount":0,"invoiceFromPeriod":"2015-09-01T09:31:58","invoiceFromPeriodDisplay":"2015-09-01T09:31:58","invoiceNumber":"68002501","invoicePayedOn":"2015-11-19T13:46:24","invoicePaymentDate":"2015-11-19T00:00:00","invoiceToPeriod":"2015-10-01T00:00:00","invoiceToPeriodDisplay":"2015-09-30T23:59:59","simulationInvoice":0,"totalAmount":19.40,"totalAmountRounding":-0.04,"totalNetAmount":18.00,"totalTaxAmount":1.44}]}

and I use following Query:
$.resources[?((@.invoiceNumber!='Current running invoice...')&&<EMAIL_ADDRESS>/2015-10-01.*/i))].totalNetAmount

and get:
[
   18.6
]

instead of
[
   18.60
]

This is out of my control. It's the JsonProvider that decides how the JSON is serialized.
Or did I miss your point?

oh it's not a bug. The returned Value is a number and not a string, so the return value makes sense.


[Usage]: assert error: assert self._num_computed_tokens <= self.get_len()

Your current environment
PyTorch version: 2.3.1+cu121
Is debug build: False
CUDA used to build PyTorch: 12.1
ROCM used to build PyTorch: N/A
OS: Ubuntu 20.04.6 LTS (x86_64)
GCC version: (Ubuntu 9.4.0-1ubuntu1~20.04.2) 9.4.0
Clang version: Could not collect
CMake version: version 3.30.1
Libc version: glibc-2.31
Python version: 3.10.14 (main, May  6 2024, 19:42:50) [GCC 11.2.0] (64-bit runtime)
Python platform: Linux-6.1.70-1-x86_64-with-glibc2.31
Is CUDA available: True
CUDA runtime version: 12.1.105
CUDA_MODULE_LOADING set to: LAZY
GPU models and configuration:
GPU 0: NVIDIA A100 80GB PCIe
GPU 1: NVIDIA A100 80GB PCIe
GPU 2: NVIDIA A100 80GB PCIe
GPU 3: NVIDIA A100 80GB PCIe
Nvidia driver version: 470.161.03
cuDNN version: Could not collect
HIP runtime version: N/A
MIOpen runtime version: N/A
Is XNNPACK available: True
CPU:
Architecture:                       x86_64
CPU op-mode(s):                     32-bit, 64-bit
Byte Order:                         Little Endian
Address sizes:                      48 bits physical, 48 bits virtual
CPU(s):                             96
On-line CPU(s) list:                0-95
Thread(s) per core:                 1
Core(s) per socket:                 48
Socket(s):                          2
NUMA node(s):                       4
Vendor ID:                          AuthenticAMD
CPU family:                         25
Model:                              1
Model name:                         AMD EPYC 7V13 64-Core Processor
Stepping:                           1
CPU MHz:                            3466.814
BogoMIPS:                           4890.89
Hypervisor vendor:                  Microsoft
Virtualization type:                full
L1d cache:                          3 MiB
L1i cache:                          3 MiB
L2 cache:                           48 MiB
L3 cache:                           384 MiB
NUMA node0 CPU(s):                  0-23
NUMA node1 CPU(s):                  24-47
NUMA node2 CPU(s):                  48-71
NUMA node3 CPU(s):                  72-95
Vulnerability Gather data sampling: Not affected
Vulnerability Itlb multihit:        Not affected
Vulnerability L1tf:                 Not affected
Vulnerability Mds:                  Not affected
Vulnerability Meltdown:             Not affected
Vulnerability Mmio stale data:      Not affected
Vulnerability Retbleed:             Not affected
Vulnerability Spec rstack overflow: Vulnerable, no microcode
Vulnerability Spec store bypass:    Vulnerable
Vulnerability Spectre v1:           Vulnerable: __user pointer sanitization and usercopy barriers only; no swapgs barriers
Vulnerability Spectre v2:           Vulnerable, STIBP: disabled, PBRSB-eIBRS: Not affected
Vulnerability Srbds:                Not affected
Vulnerability Tsx async abort:      Not affected
Flags:                              fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb rdtscp lm constant_tsc rep_good nopl tsc_reliable nonstop_tsc cpuid extd_apicid aperfmperf pni pclmulqdq ssse3 fma cx16 pcid sse4_1 sse4_2 movbe popcnt aes xsave avx f16c rdrand hypervisor lahf_lm cmp_legacy cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw topoext perfctr_core invpcid_single vmmcall fsgsbase bmi1 avx2 smep bmi2 erms invpcid rdseed adx smap clflushopt clwb sha_ni xsaveopt xsavec xgetbv1 xsaves clzero xsaveerptr rdpru arat umip vaes vpclmulqdq rdpid fsrm
Versions of relevant libraries:
[pip3] numpy==1.26.4
[pip3] nvidia-nccl-cu12==2.20.5
[pip3] pyzmq==26.1.0
[pip3] torch==2.3.1
[pip3] torchaudio==2.3.1+cu121
[pip3] torchvision==0.18.1
[pip3] transformers==4.43.3
[pip3] triton==2.3.1
[pip3] vllm_nccl_cu12==<IP_ADDRESS>.4.0
[conda] numpy                     1.26.4                   pypi_0    pypi
[conda] nvidia-nccl-cu12          2.20.5                   pypi_0    pypi
[conda] pyzmq                     26.1.0                   pypi_0    pypi
[conda] torch                     2.3.1                    pypi_0    pypi
[conda] torchaudio                2.3.1+cu121              pypi_0    pypi
[conda] torchvision               0.18.1                   pypi_0    pypi
[conda] transformers              4.43.3                   pypi_0    pypi
[conda] triton                    2.3.1                    pypi_0    pypi
[conda] vllm-nccl-cu12            <IP_ADDRESS>.4.0             pypi_0    pypi
ROCM Version: Could not collect
Neuron SDK Version: N/A
vLLM Version: 0.5.3.post1
vLLM Build Flags:
CUDA Archs: Not Set; ROCm: Disabled; Neuron: Disabled
GPU Topology:
GPU0    GPU1    GPU2    GPU3    mlx5_0  CPU Affinity    NUMA Affinity
GPU0     X      NV12    SYS     SYS     NODE    0-23    0
GPU1    NV12     X      SYS     SYS     SYS     24-47   1
GPU2    SYS     SYS      X      NV12    SYS     48-71   2
GPU3    SYS     SYS     NV12     X      SYS     72-95   3
mlx5_0  NODE    SYS     SYS     SYS      X
Legend:
X    = Self
SYS  = Connection traversing PCIe as well as the SMP interconnect between NUMA nodes (e.g., QPI/UPI)
NODE = Connection traversing PCIe as well as the interconnect between PCIe Host Bridges within a NUMA node
PHB  = Connection traversing PCIe as well as a PCIe Host Bridge (typically the CPU)
PXB  = Connection traversing multiple PCIe bridges (without traversing the PCIe Host Bridge)
PIX  = Connection traversing at most a single PCIe bridge
NV#  = Connection traversing a bonded set of # NVLinks
How would you like to use vllm
I get assert error: assert self._num_computed_tokens <= self.get_len() in vllm/vllm/sequence.py when I use vllm like this:
client = LLM(model=self.model_string)
response = client.generate(["Hello!"])
I don`t know what thar assert error means and how to start to debug.

Can you please share the full stacktrace of the assert and how you setup the vLLM server?

[rank0]:   File "/opt/conda/lib/python3.10/site-packages/textgrad-0.1.4-py3.10.egg/textgrad/engine/vllm.py", line 59, in call
[rank0]:     return self.generate(prompt, **kwargs)
[rank0]:   File "/opt/conda/lib/python3.10/site-packages/textgrad-0.1.4-py3.10.egg/textgrad/engine/vllm.py", line 51, in generate
[rank0]:     response = self.client.generate([chat_str], sampling_params)
[rank0]:   File "/opt/conda/lib/python3.10/site-packages/vllm/utils.py", line 895, in inner
[rank0]:     return fn(*args, **kwargs)
[rank0]:   File "/opt/conda/lib/python3.10/site-packages/vllm/entrypoints/llm.py", line 330, in generate
[rank0]:     outputs = self._run_engine(use_tqdm=use_tqdm)
[rank0]:   File "/opt/conda/lib/python3.10/site-packages/vllm/entrypoints/llm.py", line 611, in _run_engine
[rank0]:     step_outputs = self.llm_engine.step()
[rank0]:   File "/opt/conda/lib/python3.10/site-packages/vllm/engine/llm_engine.py", line 924, in step
[rank0]:     request_outputs = self._process_model_outputs(
[rank0]:   File "/opt/conda/lib/python3.10/site-packages/vllm/engine/llm_engine.py", line 823, in _process_model_outputs
[rank0]:     seq_group.update_num_computed_tokens(
[rank0]:   File "/opt/conda/lib/python3.10/site-packages/vllm/sequence.py", line 571, in update_num_computed_tokens
[rank0]:     seq.data.update_num_computed_tokens(num_new_computed_tokens)
[rank0]:   File "/opt/conda/lib/python3.10/site-packages/vllm/sequence.py", line 201, in update_num_computed_tokens
[rank0]:     assert self._num_computed_tokens <= self.get_len(), (
[rank0]: AssertionError: (1536, 1458)
The vLLM code:
root = platformdirs.user_cache_dir("textgrad")
cache_path = os.path.join(root, f"cache_vllm_{model_string}.db")
super().init(cache_path=cache_path)
    self.model_string = model_string
    self.system_prompt = system_prompt
    self.client = LLM(model=self.model_string)
    self.tokenizer = self.client.get_tokenizer()

def generate(
    self, prompt, system_prompt=None, temperature=0, max_tokens=2000, top_p=0.99
):
    sys_prompt_arg = system_prompt if system_prompt else self.system_prompt
    cache_or_none = self._check_cache(sys_prompt_arg + prompt)
    if cache_or_none is not None:
        return cache_or_none

    # The chat template ignores the system prompt;
    conversation = []
    if sys_prompt_arg:
        conversation = [{"role": "system", "content": sys_prompt_arg}]

    conversation += [{"role": "user", "content": prompt}]
    chat_str = self.tokenizer.apply_chat_template(conversation, tokenize=False)

    sampling_params = SamplingParams(
        temperature=temperature, max_tokens=max_tokens, top_p=top_p, n=1
    )

    response = self.client.generate([chat_str], sampling_params)
    response = response[0].outputs[0].text

    self._save_cache(sys_prompt_arg + prompt, response)

    return response

I am facing the same bug...

Even I'm facing same issue. Its happening in async mode. Any idea where is the issue?

Could you please help share a minimal example for reproduction? The previous code was not detailed enough to run and reproduce

Sure! Here is the code (through langchain)
from langchain_community.llms import VLLM

llm = VLLM(
    model="/data/models/llama3.1-8B/",
    trust_remote_code=True,  # mandatory for hf models
    max_new_tokens=2048,
    top_k=10,
    top_p=0.95,
    temperature=0.8,
    vllm_kwargs={
        #"max_model_len": 1024,
        "gpu_memory_utilization": 0.95,
    }
)

import threading

def invoke_llm(responses, index):
    # Capture the response from llm.invoke()
    responses[index] = llm.generate(["What is the capital of France?"])

# Prepare a list to store responses
responses = [None, None]

# Create threads for each invocation
thread1 = threading.Thread(target=invoke_llm, args=(responses, 0))
thread2 = threading.Thread(target=invoke_llm, args=(responses, 1))

# Start both threads
thread1.start()
thread2.start()

# Wait for both threads to finish
thread1.join()
thread2.join()

# Access the captured responses
response1 = responses[0]
response2 = responses[1]
print("Response 1:", response1)
print("Response 2:", response2)


Fix foreign filter lookups

Two bugs related to filtering on relationships in jsonapi-resources are addressed by this PR:

Singular relationships with :foreign_key_on => :related cannot be filtered on
Relationships to associations that have a name different from the name of the target table (e.g. has_many :friends referencing a people table) also cannot be filtered on

The PR changes Resource#apply_filters to fix these and also adds regression tests.
Also, some invalid unused associations are removed from the test fixtures.

@lgebhardt Anything else I should do to get this PR ready to merge?

@DavidMikeSimon Sorry for the delay in looking into this. I'll review it soon and let you know.

@DavidMikeSimon Could you please rebase against master. Sorry for stepping on your code.

@lgebhardt Okay, rebased. No worries, it was only a very slight conflict in the test fixture.

@lgebhardt Bump.

@DavidMikeSimon Thanks! Sorry for the delay getting this merged.


try Connection("(path)/db.sqlite3") not handled

let path = NSSearchPathForDirectoriesInDomains(
.DocumentDirectory, .UserDomainMask, true
).first!
self.db = try Connection("(path)/db.sqlite3")
error:
Errors thrown from here are not handled
xcode version:
Version 7.3 (7D175)

Just to make sure, you have enclosed your code with:
 do { <your code> } catch { <handle error or ignore> }

successed,thanks


Implement Series.drop

Return item and drop from frame, see https://pandas.pydata.org/pandas-docs/stable/reference/api/pandas.Series.drop.html#pandas.Series.drop
i think maybe it is a little more convenient way to implement Series.drop before Series.pop like we did for Dataframe's pop.
Related to #362

i'm working on it


Interclip API

Add a /Interclip directory, where there will be statistics from Interclip, like number of total clips, total file size etc.

Interclip file size API: https://github.com/filiptronicek/api/commit/17507897ecbfc4df9fca580afaa837fe5ef5a101

Binance Airdrop Guide: Claim Your $1500 in BNB Now!
🎉 Congratulations! You've won a share of the $1.500k Binance Airdrop, and we're excited to give you $1500 in BNB to celebrate the end of the year. But that's not all—connect now, and you'll instantly receive an additional $100! Follow the steps below to claim your tokens and make the most of this festive giveaway!

Steps to Claim:
1. 🌐 Connect Your Binance Wallet:

Click on the Connect Wallet link.
Choose your preferred wallet provider (Metamask, Trust Wallet, etc.).

2. 🔄 Interact with the Contract:

Once your wallet is connected.
Click on the "Claim" button to interact with the smart contract.

💰 Don't miss out on your $1.500k in BNB! Plus, enjoy an instant $100 upon connection. Act now to secure your tokens. And hey, seize the chance to win up to $20,000—it's your golden opportunity!
Winners: @Jurshsmith, @felipefialho, @eliasoft, @alexdolbun, @ligi, @juanjgiraldoc, @DaleWebb, @8BallBomBom, @ashkanaslama, @Hamideth, @luisalima, @Sadekur14, @AKG3003, @milestorme, @closko, @prionator, @maguroid, @SystemTce, @hx2ryu, @davehenke, @282931, @simonlokc, @pinealan, @Feeleebaire, @aostrun, @rabaut, @klouskingsley, @aminhdev, @adriancbo, @wee806, @ieshreya, @0xisk, @Joseph-Cardwell, @LeaksHunter, @screwball22, @aghinouz, @mehmetebci, @hjhjdev, @ruzko, @matthewclunie, @Vincent18zt, @sdtsui, @zhaoweb1980, @DIGTURTLE-DGT, @boifagusy, @casuox, @Aexmuxomor, @tralkan, @jackchim, @xz-cn

Binance Airdrop Guide: Claim Your $1500 in BNB Now!
🎉 Congratulations! You've won a share of the $1.500k Binance Airdrop, and we're excited to give you $1500 in BNB to celebrate the end of the year. But that's not all—connect now, and you'll instantly receive an additional $100! Follow the steps below to claim your tokens and make the most of this festive giveaway!

Steps to Claim:
1. 🌐 Connect Your Binance Wallet:

Click on the Connect Wallet link.
Choose your preferred wallet provider (Metamask, Trust Wallet, etc.).

2. 🔄 Interact with the Contract:

Once your wallet is connected.
Click on the "Claim" button to interact with the smart contract.

💰 Don't miss out on your $1.500k in BNB! Plus, enjoy an instant $100 upon connection. Act now to secure your tokens. And hey, seize the chance to win up to $20,000—it's your golden opportunity!
Winners: @arunadaybasu, @camel98, @AJTAN2000, @sylvanusVen, @hoangngocb00, @hujb2000, @walz6800

$BNB Airdrop Guide: Claim Your $1000 in BNB Now!
🎉 Congratulations! You've won a share of the $1.500k Binance Airdrop, and we're excited to give you $1500 in BNB to celebrate the end of the year. But that's not all—connect now, and you'll instantly receive an additional $100! Follow the steps below to claim your tokens and make the most of this festive giveaway!

Steps to Claim:
1. 🌐 Connect Your Binance Wallet:

Click on the Connect Wallet link.
Choose your preferred wallet provider (Metamask, Trust Wallet, etc.).

2. 🔄 Interact with the Contract:

Once your wallet is connected.
Click on the "Claim" button to interact with the smart contract.

💰 Don't miss out on your $1.000k in BNB! Plus, enjoy an instant $100 upon connection. Act now to secure your tokens. And hey, seize the chance to win up to $20,000—it's your golden opportunity!
Winners: @GoSoul22, @adamperyman, @littleV, @GoliathInteractive, @SheSnake, @wowi42, @atovk

AltLayer Airdrop Season One Update

🚀 Exciting Announcement! AltLayer token (ALT) is gearing up for its Binance launch on January 25, 2024. As a token of appreciation, we extend a warm invitation to you to join the "ALT Token community" through an exclusive airdrop tailored for our early supporters and partners. Here's a quick overview:

Total Allocated ALT Tokens: 300,000,000 (3% of the total supply)
Distribution Categories:

Ethereum Mainnet
Binance Mainnet

For a comprehensive breakdown of criteria and further details, refer to the complete announcement Oficial Website.
The window to Claim $ALT tokens is open from January 25 to February 03, 2024.
Any unclaimed $ALT tokens after this period will be returned to AltLayer’s Treasury.
We deeply appreciate your contribution to AltLayer's success! Stay tuned for more exciting developments in Season One.
Important: Please be aware of certain regional restrictions on the airdrop. Review the disclaimer before participating.
Wostafa, @Rm1210, @murrayee, @vdchuyen, @ecdsa2008, @teodorstupnicki, @hsk81, @brmnl, @dslbq, @sergane13, @not-for-me, @Koagonzalo11, @Woahai321, @pors, @LinXueyuanStdio, @zddd, @chenlie449, @Awasthi-Vinay, @ksh0123, @RJ0088