andidate function has type mismatch at 2nd parameter

Hi, while building n4.1.4 as shown in example, I get the following error
/22.1.7171670/toolchains/llvm/prebuilt/darwin-x86_64/sysroot/usr/include/bits/ioctl.h:60:5: note: candidate function has type mismatch at 2nd parameter (expected 'unsigned long' but has 'unsigned int')
My ndk version is 22.1.7171670. If I understand correctly, it has got something to do with the fact that gcc isn't supported by ndk anymore.
Hence, I downloaded an older version of ndk (r13b) and tried to run the script.
Then I got the following error
Library/Android/sdk/ndk/android-ndk-r13b/toolchains/llvm/prebuilt/darwin-x86_64/bin/aarch64-linux-android21-clang is unable to create an executable file

Hello.
I feel a bit nostalgic about this issue. Grab a drink and hear a story.
ioctl.h problem
When I first tried to make the FFmpeg compilable, even before I decided to make it public, I tried using FFmpeg 4.1. I finally made it compilable, however some problems (like in your message) were eliminated by disabling certain modules of FFmpeg from being compiled at all. Even now the what-the-codec branch still has such modules disabled and the brief check of FFmpeg 4.1.4 with it works fine. Check this file to see what is actually disabled.
Now the master branch has all standard modules enabled.
Specifically your problem was fixed by this commit, but it was merged only into FFmpeg 4.2.
This means that if you want all modules of FFmpeg being compiled, please use the FFmpeg 4.2+. If you are ok with certain modules not included to the final binary, try disable them. I don't really remember which modules give this error.
NDK issue
The Android NDK is an evolving beast and it is very important to use its proper version for this scrip to work. Supported versions are r19 - r21.
Starting with NDK r19 it has unified directory for header files, which simplifes a lot of things. Previously the easiest way for compilation was to create a standalone toolchain for each of the ABI you are targeting. All NDK versions up until r21e are checked and work well with the script. But the r22 isn't supported yet. It is planned for the future. This information is in the README.md file.
I suggest using r21e as the LTS version of NDK.

First of all, man the reply was extremely swift. Truly appreciate that. I can make out that this project is really close to your heart.
Now to other extremely important topic, I doubt you will be travelling to India anytime soon. But I would still like to buy you a beer! Can you please share a link somewhere through which I could :)
I am checking the resources you mentioned here, and will be playing around a lot. this is a great starting point.

Thanks for the kind words and let's better stay sober :)
Is your issue resolved now?

haha, sure thing. So yes, its kinda resolved. I am going to close this one, will post another query if needed


[FLOC-2946] Docker plugin acceptance tests for volume movement

Demonstrate that volumes can be moved to different containers on the same node and on different nodes.
This also includes a fix to the way the plugin API work which is necessary for the tests to pass: the /VolumeDriver.Path call needs to return a result immediately even if it doesn't know the path yet.
Finally, the acceptance test remote log capture also captures the flocker-docker-plugin logs since that was helpful when debugging.

Thanks @itamarst
This looks great. I left one or two comments above. Please answer or address those and then merge.

Added a bunch of explanations to the code to address the above.


Update credential-guard-manage.md

The Microsoft Virtual Academy site is being retired, removed references to the training video.

Any particular reason for closing this PR?
(it would be nice to have a closing comment)

Found your new PR here: #3349

I closed this pull request because it had been 2 days since the conversation had been resolved and thought that I misunderstood the process.  Sorry for the inconvenience

Fair enough. Sooner or later, we all need to learn how the process works anyway.


redefining a variable causes SPAWN to fail (memory leak?)

Reported by Andrew Wittenberg on 28 Aug 2006 16:10 UTC
Found this while running my old "LET" benchmark of 06nov2003.  Here the first
line runs smoothly, while the 2nd begins thrashing my hard disk and then fails
to complete the command (omitting the last "SPAWN date").  After that, SPAWN
always fails, and trying to capture the results of SPAWN to a variable causes a
segfault.
I tried this in two different sessions, one with "ferret -memsize 128" and the
other "ferret -memsize 16", and both failed after the same number of iterations
(somewhere between 450,000 and 500,000 executions of "LET A=0").
   NOAA/PMEL TMAP
    FERRET v6
    Linux(g77) 2.4.21-32 - 08/23/06
    28-Aug-06 11:53

yes? can mode verif; sp date; rep/i=1:50 rep/j=1:5000 let a=0; sp date
Mon Aug 28 11:53:36 EDT 2006
Mon Aug 28 11:54:26 EDT 2006
yes? can mode verif; sp date; rep/i=1:50 rep/j=1:5000 let a=0; sp date
Mon Aug 28 11:54:30 EDT 2006
yes? sp date
yes? sp ls
yes? sp pwd
yes? let pwdtxt = {spawn:"pwd"}
Segmentation fault
Migrated-From: http://dunkel.pmel.noaa.gov/trac/ferret/ticket/1437

Comment by<EMAIL_ADDRESS>on 7 Jun 2007 15:33 UTC
I no longer reproduce this in v6.03 for Linux 32bit.  Waiting to check v6.03 for
Altix.

Comment by<EMAIL_ADDRESS>on 7 Jun 2007 15:35 UTC
I spoke too soon.  After 3 more iterations of the test, I do get the same bomb
in v6.03 for Linux.

Comment by<EMAIL_ADDRESS>on 30 Jul 2007 18:04 UTC
In v6.05 (& 6.04?) this leak is worse -- my system can't get through even one
iteration of
ferret -memsize 16
yes? can mode verif; sp date; rep/i=1:50 rep/j=1:5000 let a=0; sp date
As the loop progresses, I watch my system's memory usage go from 171MB (83%
free) to 958MB (5% free), at which point it starts swapping to disk like crazy
and my system slows way down.  When my 2GB of swap space fills up, Ferret then
simply stops and gives a "yes?" prompt.  But at that point the memory and swap
space are completely full, and Ferret will accept no more commands.  (Note that
this is despite my limiting the Ferret memsize to 16MB.)  Can you reproduce this
on systems at PMEL?

Comment by<EMAIL_ADDRESS>on 15 Oct 2007 19:10 UTC
Fixed by Remik Ziemlinski; routine ncf_free_attrib in NCF_Util.c


replce deep-extend with lodash.merge

Doesn't look like deep-extend was doing anything that lodash.merge
couldn't do. Requiring one less dep is nice.

:+1:


DO-49 default buckets minio

References
DO-49
Summary
This PR provisions two initial buckets for minio in the dev environment. One for temporary weights from participants, and one for storage of aggregated models
Are there any open tasks/blockers for the ticket?
No

Reviewer checklist
Reviewer agreement:

Reviewers assign themselves at the start of the review.
Reviewers do not commit or merge the merge request.
Reviewers have to check and mark items in the checklist.

Merge request checklist

[ ] Conforms to the merge request title naming XP-XXX <a description in imperative form>.
[ ] Each commit conforms to the naming convention XP-XXX <a description in imperative form>.
[ ] Linked the ticket in the merge request title or the references section.
[ ] Added an informative merge request summary.

Code checklist

[ ] Conforms to the branch naming XP-XXX-<a_small_stub>.
[ ] Passed scope checks.
[ ] Added or updated tests if needed.
[ ] Added or updated code documentation if needed.
[ ] Conforms to Google docstring style.
[ ] Conforms to XAIN structlog style.

I have an issue with this:
Recreating xain-fl_minio-dev_1 ... done
Recreating xain-fl_initial-buckets_1 ... done
Attaching to xain-fl_minio-dev_1, xain-fl_initial-buckets_1
minio-dev_1        | ‘ln’ is not a minio sub-command. See ‘minio --help’.
xain-fl_minio-dev_1 exited with code 1
initial-buckets_1  | Waiting for minio service to start...
initial-buckets_1  | nc: bad address 'minio-dev'
initial-buckets_1  | nc: bad address 'minio-dev'
initial-buckets_1  | nc: bad address 'minio-dev'
initial-buckets_1  | nc: bad address 'minio-dev'
initial-buckets_1  | nc: bad address 'minio-dev'
initial-buckets_1  | nc: bad address 'minio-dev'
initial-buckets_1  | nc: bad address 'minio-dev'


Setting- Avatar is updated after refresh/re -login when delete it in OldDot

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Issue found when executing PR https://github.com/Expensify/App/pull/13216
Action Performed:

Log in with the same account in OldDot and NewDot
Go to NewDot and upload a new custom avatar
Back to OldDot - Setting - Account
Delete avatar in OldDot
Go back in NewDot and check avatar

Expected Result:
Avatar is updated immediately when delete it in OldDot
Actual Result:
Avatar is updated after refresh/re login in app when delete it in OldDot
Workaround:
Unknown
Platforms:

Which of our officially supported platforms is this issue occurring on?

[x] Android / native
[x] Android / Chrome
[x] iOS / native
[x] iOS / Safari
[x] MacOS / Chrome / Safari
[x] MacOS / Desktop

Version Number: <IP_ADDRESS>
Reproducible in staging?: Yes
Reproducible in production?: Yes
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation
https://user-images.githubusercontent.com/93399543/216669355-01f4d5ea-8556-4a04-958d-65fd3761514d.mp4
Expensify/Expensify Issue URL:
Issue reported by: Applause - Internal Team
Slack conversation:
View all open jobs on GitHub

I'll jump on this on Monday, but @grgia putting it on your radar in the meantime wrt default avatars.

Triggered auto assignment to @tgolen (Engineering), see https://stackoverflow.com/c/expensify/questions/4319 for more details.

I don't think this is a bug, it should be classified as a new feature. I think this brings up a much wider discussion of potential features... I think before we do this GH, we need to figure out:

How much should we try to keep OldDot in sync with NewDot (without requiring a refresh) in light of wanting to completely get rid of OldDot someday?

There are THOUSANDS of actions you can take in OldDot that would impact NewDot (eg. changing your name, creating policies, submitting reports, yada yada). I do not think that we want to put any effort into keeping the two in sync, since we are going to completely replace OldDot someday.


Heuristics to get a positive / negative explanation for an image model

Hi,
We are trying to arrive at positive and negative image explanation with a fixed heuristic that works for all kinds of image resolutions. In the sense, once the explanation is generated by LIME, in order to get two images which display the areas which have contributed positively towards the prediction and the features which have negatively contributed, we need to be sending the number of features (super-pixels) to include in the explanation. Is there a good heuristic that you suggest to arrive at a value of num_features (arg to get_image_and_mask) based on the image and the explanation output?
Thanks
Venkat

If you are generating explanations for multiple images, and want to meaningfully compare them, I would actually suggest setting min_weight to something you consider significant and letting num_features be 1000000 (infinite), so that you only get superpixels that contribute by at least min_weight to the prediction. Otherwise, the positive superpixels in an image are not really comparable to another, as they may have very low weight while the other has very high weight.


Bump Ansible and Packer on builder-base

Bump Ansible and Packer on builder-base to the versions required by kubernetes-sigs/image-builder v0.1.22.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

/lgtm

/approve


Revert breaking changes in casper-test-support and tidy up casper-execution-engine

Fixes #3072 #3074
This PR reverts the breaking changes in casper-test-support since the v1.4.6 release.
The changes in casper-execution-engine cannot be reverted in a backwards compatible way, so this PR adds non-exhaustive to enums and restores write_scratch_to_db in a deprecated state.
Changes were found using the cargo-public-api tool.

bors merge


Is the exclude syntax for the REPL documented?

If you want Ammonite to exclude multiple transitive dependencies, separate them with commas, like this:
import $exclude.`maven-group1:maven-id1`, $ivy.`maven-group2:maven-id2:optionalVersion`, $ivy.`maven-group3:maven-id3`

Notice that the first transitive dependency was prefaced with $exclude, while the remainder were prefaced with $ivy. I have not found documentation on this syntax; this is merely what seems to work. Is there documentation on this? Have I correctly phrased the explanation?

@mslinn It's something you must have seen in jupyter-scala or its underlying modified Ammonite. It's specific to them for now.
The implem in them depends on coursier, which is not used by Ammonite, although @lihaoyi expressed some interest for it (after its 1.0 release). It might be possible to have an implementation with Ivy that Ammonite currently used though.

@alexarchambault Thank you for your quick reply. The $exclude syntax is undocumented and I think perhaps inconsistent. To be consistent, the first excluded transitive dependency should mention $ivy, or is $ivy a default?
import $exclude.$ivy.`maven-group1:maven-id1`, $ivy.`maven-group2:maven-id2:optionalVersion`, $ivy.`maven-group3:maven-id3`

Ammonium has no documentation regarding how it differs from Ammonite. Some documentation on this syntax, and any other user-visible changes would be helpful.


Mark this repo as a template repo

https://help.github.com/en/articles/creating-a-template-repository

Thank you! That's a new feature I missed. :)


Add service manager

This PR introduces the service manager which handles all the plumbing of services between cilium-agent and the BPF maps.
Previously, the manager functionality was spread among pkg/loadbalancer/loadbalancer.go, daemon/loadbalancer.go and pkg/lbmap/bpfservice.go. Now, it resides in a single module - pkg/service/service.go.
I didn't add any test (yet), as this PR is big enough, and I didn't want to introduce more changes by adding the lbmap interface. Going to do in a subsequent PR. For now, I'm relying on the integration tests.
Next steps:

Unit tests for the service manager.
TODO(brb) items.
Cleanup types mess in pkg/loadbalancer.
Get rid of some methods in pkg/lbmap.

Reviewable per commit.

This change is

test-me-please

Coverage increased (+0.3%) to 45.139% when pulling 0421e8fa1b0c15b880670376425e9009691b592a on pr/brb/refactor-lb-next-v5 into 1316dcaff9f1539dc60a4200e22fe8bbc0364780 on master.

test-me-please

test-me-please


Script '/home/tisu/snap/flutter/common/flutter/packages/flutter_tools/gradle/flutter.gradle' line: 896 while debuging

When I'm trying to degug the app
FAILURE: Build failed with an exception.

* Where:
Script '/home/tisu/snap/flutter/common/flutter/packages/flutter_tools/gradle/flutter.gradle' line: 896

* What went wrong:
Execution failed for task ':app:compileFlutterBuildDebug'.
> Process 'command '/home/tisu/snap/flutter/common/flutter/bin/flutter'' finished with non-zero exit value 1

* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.

* Get more help at https://help.gradle.org

BUILD FAILED in 3m 34s
Exited (sigterm)
Exception: Gradle task assembleDebug failed with exit code 1

project.exec {
            logging.captureStandardError LogLevel.ERROR
            executable flutterExecutable.absolutePath
            workingDir sourceDir
            if (localEngine != null) {
                args "--local-engine", localEngine
                args "--local-engine-src-path", localEngineSrcPath
            }
            if (verbose) {
                args "--verbose"
            } else {
                args "--quiet"
            }
            args "assemble"
            args "--depfile", "${intermediateDir}/flutter_build.d"
            args "--output", "${intermediateDir}"
            if (performanceMeasurementFile != null) {
                args "--performance-measurement-file=${performanceMeasurementFile}"
            }
            if (!fastStart || buildMode != "debug") {
                args "-dTargetFile=${targetPath}"
            } else {
                args "-dTargetFile=${Paths.get(flutterRoot.absolutePath, "examples", "splash", "lib", "main.dart")}"
            }
            args "-dTargetPlatform=android"
            args "-dBuildMode=${buildMode}"
            if (trackWidgetCreation != null) {
                args "-dTrackWidgetCreation=${trackWidgetCreation}"
            }
            if (splitDebugInfo != null) {
                args "-dSplitDebugInfo=${splitDebugInfo}"
            }
            if (treeShakeIcons == true) {
                args "-dTreeShakeIcons=true"
            }
            if (dartObfuscation == true) {
                args "-dDartObfuscation=true"
            }
            if (dartDefines != null) {
                args "--DartDefines=${dartDefines}"
            }
            if (bundleSkSLPath != null) {
                args "-iBundleSkSLPath=${bundleSkSLPath}"
            }
            if (extraGenSnapshotOptions != null) {
                args "--ExtraGenSnapshotOptions=${extraGenSnapshotOptions}"
            }
            if (extraFrontEndOptions != null) {
                args "--ExtraFrontEndOptions=${extraFrontEndOptions}"
            }
            args ruleNames
        }

[✓] Flutter (Channel stable, 1.22.4, on Linux, locale en_US.UTF-8)
• Flutter version 1.22.4 at /home/tisu/development/flutter
• Framework revision 1aafb3a8b9 (6 days ago), 2020-11-13 09:59:28 -0800
• Engine revision 2c956a31c0
• Dart version 2.10.4
[✓] Android toolchain - develop for Android devices (Android SDK version 29.0.3)
• Android SDK at /home/tisu/Android/Sdk
• Platform android-30, build-tools 29.0.3
• Java binary at: /home/tisu/android-studio/jre/bin/java
• Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b3-6222593)
• All Android licenses accepted.
[✓] Android Studio (version 4.0)
• Android Studio at /home/tisu/android-studio
• Flutter plugin installed
• Dart plugin version 193.7547
• Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b3-6222593)
[✓] Connected device (1 available)
• SM A515F (mobile) • R58N23DVJ5Z • android-arm64 • Android 10 (API 29)
• No issues found!

@Tisanthan
I see 2 different installation path in your logs
> Process 'command '/home/tisu/snap/flutter/common/flutter/bin/flutter'' finished with non-zero exit value 1
• Flutter version 1.22.4 at /home/tisu/development/flutter
I guess you installed flutter both via snapcraft and manually
can you show the relevant part of  ~/bashrc and the output of which flutter

@Tisanthan
I see 2 different installation path in your logs
> Process 'command '/home/tisu/snap/flutter/common/flutter/bin/flutter'' finished with non-zero exit value 1
• Flutter version 1.22.4 at /home/tisu/development/flutter
I guess you installed flutter both via snapcraft and manually
can you show the relevant part of ~/bashrc and the output of which flutter

export PATH="$PATH:/home/tisu/development/flutter/bin"
which flutter
/home/tisu/development/flutter/bin/flutter

@Tisanthan
your setup looks fine
I wonder why in the logs flutter seems to run from the snap installation,
did you run flutter from terminal or IDE?
If the latter, could you try from terminal

Hi @Tisanthan
Can you please provide on your script does, do you also experience the issue without the script and please try from the terminal as mentioned above
Can you please provide your flutter run --verbose logs, and a minimal complete reproducible code sample?
Thank you

@Tisanthan
your setup looks fine
I wonder why in the logs flutter seems to run from the snap installation,
did you run flutter from terminal or IDE?
If the latter, could you try from terminal
thank you @iapicca
I have done debug in Vs code.
it was working properly until the last flutter update
it has worked in the terminal.

it is also an output line in the debug console
../../development/flutter/packages/flutter/lib/material.dart:1:1: Error: The specified language version is too high. The highest supported language version is 2.9.
// Copyright 2014 The Flutter Authors. All rights reserved.
^
../../development/flutter/.pub-cache/hosted/pub.dartlang.org/meta-1.3.0-nullsafety.3/lib/meta.dart:1:1: Error: The specified language version is too high. The highest supported language version is 2.9.
// Copyright (c) 2016, the Dart project authors. Please see the AUTHORS file
^
../../development/flutter/packages/flutter/lib/src/material/about.dart:1:1: Error: The specified language version is too high. The highest supported language version is 2.9.
// Copyright 2014 The Flutter Authors. All rights reserved.
^
../../development/flutter/packages/flutter/lib/src/material/animated_icons.dart:1:1: Error: The specified language version is too high. The highest supported language version is 2.9.
// Copyright 2014 The Flutter Authors. All rights reserved.

Hi @Tisanthan
Can you please provide on your script does, do you also experience the issue without the script and please try from the terminal as mentioned above
Can you please provide your flutter run --verbose logs, and a minimal complete reproducible code sample?
Thank you

thank you @TahaTesser
...........
[  +99 ms] > Task :app:mergeDebugNativeLibs UP-TO-DATE
[ +900 ms] > Task :app:stripDebugDebugSymbols UP-TO-DATE
[        ] Compatible side by side NDK version was not found.
[        ] > Task :app:packageDebug UP-TO-DATE
............

[  +14 ms] executing: /home/tisu/Android/Sdk/platform-tools/adb -s emulator-5554 shell -x logcat -v time -t 1
[  +16 ms] Exit code 0 from: /home/tisu/Android/Sdk/platform-tools/adb -s emulator-5554 shell -x logcat -v time -t 1
[        ] --------- beginning of main
           11-21 08:59:00.006 D/KeyguardClockSwitch( 2310): Updating clock: 859
[   +1 ms] executing: /home/tisu/Android/Sdk/platform-tools/adb -s emulator-5554 shell -x logcat -v time -t 1
[  +19 ms] Exit code 0 from: /home/tisu/Android/Sdk/platform-tools/adb -s emulator-5554 shell -x logcat -v time -t 1
[        ] --------- beginning of main
           11-21 08:59:00.006 D/KeyguardClockSwitch( 2310): Updating clock: 859
[  +15 ms] <- compile package:social_sign/main.dart
[  +11 ms] executing: /home/tisu/Android/Sdk/platform-tools/adb version
[   +6 ms] Android Debug Bridge version 1.0.41
           Version 30.0.4-6686687
           Installed as /home/tisu/Android/Sdk/platform-tools/adb
[   +2 ms] executing: /home/tisu/Android/Sdk/platform-tools/adb start-server
[   +6 ms] Building APK
[  +18 ms] Running Gradle task 'assembleDebug'...
[   +1 ms] gradle.properties already sets `android.enableR8`
[   +2 ms] Using gradle from /home/tisu/flutter/social_sign/android/gradlew.
[        ] /home/tisu/flutter/social_sign/android/gradlew mode: 33261 rwxr-xr-x.
[   +9 ms] executing: /home/tisu/android-studio/jre/bin/java -version
[ +135 ms] Exit code 0 from: /home/tisu/android-studio/jre/bin/java -version
[        ] openjdk version "1.8.0_242-release"
           OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b3-6222593)
           OpenJDK 64-Bit Server VM (build 25.242-b3-6222593, mixed mode)
[   +6 ms] executing: [/home/tisu/flutter/social_sign/android/] /home/tisu/flutter/social_sign/android/gradlew -Pverbose=true -Ptarget-platform=android-x86
-Ptarget=/home/tisu/flutter/social_sign/lib/main.dart -Ptrack-widget-creation=true -Pfilesystem-scheme=org-dartlang-root assembleDebug
[+1160 ms] > Configure project :app

......

Hi @Tisanthan
The above flutter run --verbose log you provided doesn't seem to be complete. Can you provide entire log that has prominent failure / exception messages ?

flutter run --verbose
[ +136 ms] executing: [/home/tisu/development/flutter/] git -c log.showSignature=false log -n 1 --pretty=format:%H
[ +213 ms] Exit code 0 from: git -c log.showSignature=false log -n 1 --pretty=format:%H
[   +1 ms] 1aafb3a8b9b0c36241c5f5b34ee914770f015818
[   +2 ms] executing: [/home/tisu/development/flutter/] git tag --points-at HEAD
[+1455 ms] Exit code 0 from: git tag --points-at HEAD
[        ] 1.22.4
[  +35 ms] executing: [/home/tisu/development/flutter/] git rev-parse --abbrev-ref --symbolic @{u}
[  +85 ms] Exit code 0 from: git rev-parse --abbrev-ref --symbolic @{u}
[        ] origin/stable
[        ] executing: [/home/tisu/development/flutter/] git ls-remote --get-url origin
[   +9 ms] Exit code 0 from: git ls-remote --get-url origin
[        ] https://github.com/flutter/flutter.git
[  +97 ms] executing: [/home/tisu/development/flutter/] git rev-parse --abbrev-ref HEAD
[   +2 ms] Exit code 0 from: git rev-parse --abbrev-ref HEAD
[        ] stable
[ +303 ms] Artifact Instance of 'AndroidMavenArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'AndroidGenSnapshotArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'AndroidInternalBuildArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'IOSEngineArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'FlutterWebSdk' is not required, skipping update.
[  +53 ms] Artifact Instance of 'WindowsEngineArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'MacOSEngineArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'LinuxEngineArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'LinuxFuchsiaSDKArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'MacOSFuchsiaSDKArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'FlutterRunnerSDKArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'FlutterRunnerDebugSymbols' is not required, skipping update.
[ +210 ms] executing: /home/tisu/Android/Sdk/platform-tools/adb devices -l
[  +49 ms] List of devices attached
           R58N23DVJ5Z            device usb:1-3 product:a51nsxx model:SM_A515F device:a51 transport_id:6
[   +6 ms] /home/tisu/Android/Sdk/platform-tools/adb -s R58N23DVJ5Z shell getprop
[ +141 ms] Artifact Instance of 'AndroidMavenArtifacts' is not required, skipping update.
[ +163 ms] Artifact Instance of 'AndroidInternalBuildArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'IOSEngineArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'FlutterWebSdk' is not required, skipping update.
[   +4 ms] Artifact Instance of 'WindowsEngineArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'MacOSEngineArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'LinuxEngineArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'LinuxFuchsiaSDKArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'MacOSFuchsiaSDKArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'FlutterRunnerSDKArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'FlutterRunnerDebugSymbols' is not required, skipping update.
[ +224 ms] Generating /home/tisu/Flutter_2.0/vadamar/android/app/src/main/java/io/flutter/plugins/GeneratedPluginRegistrant.java
[  +19 ms] ro.hardware = exynos9611
[        ] ro.build.characteristics = phone
[  +39 ms] Starting incremental build...
[   +2 ms] Initializing file store
[   +7 ms] Skipping target: gen_localizations
[   +6 ms] complete
[   +5 ms] Launching lib/main.dart on SM A515F in debug mode...
[   +4 ms] /home/tisu/development/flutter/bin/cache/dart-sdk/bin/dart --disable-dart-dev
/home/tisu/development/flutter/bin/cache/artifacts/engine/linux-x64/frontend_server.dart.snapshot --sdk-root
/home/tisu/development/flutter/bin/cache/artifacts/engine/common/flutter_patched_sdk/ --incremental --target=flutter --debugger-module-names
--experimental-emit-debug-metadata -Ddart.developer.causal_async_stacks=true --output-dill /tmp/flutter_tools.UMQSUO/flutter_tool.JXZMZG/app.dill
--packages .packages -Ddart.vm.profile=false -Ddart.vm.product=false
--bytecode-options=source-positions,local-var-info,debugger-stops,instance-field-initializers,keep-unreachable-code,avoid-closure-call-instructions
--enable-asserts --track-widget-creation --filesystem-scheme org-dartlang-root --initialize-from-dill build/cache.dill.track.dill
[  +17 ms] executing: /home/tisu/Android/Sdk/platform-tools/adb -s R58N23DVJ5Z shell -x logcat -v time -t 1
[ +155 ms] Exit code 0 from: /home/tisu/Android/Sdk/platform-tools/adb -s R58N23DVJ5Z shell -x logcat -v time -t 1
[        ] --------- beginning of main
           11-28 08:05:43.262 D/ISG_Wakeup_Verify_Algo(31133): kwd_score: 0.0938, kwd_score-OOV: 0.0938, flag(0), peakCount(0), TimeElapsed(47375)
[        ] executing: /home/tisu/Android/Sdk/platform-tools/adb -s R58N23DVJ5Z shell -x logcat -v time -t 1
[ +156 ms] Exit code 0 from: /home/tisu/Android/Sdk/platform-tools/adb -s R58N23DVJ5Z shell -x logcat -v time -t 1
[        ] --------- beginning of main
           11-28 08:05:43.461 D/ISG_Wakeup_Verify_Algo(31133): kwd_score: 0.0415, kwd_score-OOV: 0.0415, flag(0), peakCount(0), TimeElapsed(47395)
[   +4 ms] <- compile package:vadamar/main.dart
[  +14 ms] executing: /home/tisu/Android/Sdk/platform-tools/adb version
[   +3 ms] Android Debug Bridge version 1.0.41
           Version 30.0.4-6686687
           Installed as /home/tisu/Android/Sdk/platform-tools/adb
[   +1 ms] executing: /home/tisu/Android/Sdk/platform-tools/adb start-server
[   +3 ms] Building APK
[  +14 ms] Running Gradle task 'assembleDebug'...
[   +1 ms] gradle.properties already sets `android.enableR8`
[   +1 ms] Using gradle from /home/tisu/Flutter_2.0/vadamar/android/gradlew.
[        ] /home/tisu/Flutter_2.0/vadamar/android/gradlew mode: 33261 rwxr-xr-x.
[   +7 ms] executing: /home/tisu/android-studio/jre/bin/java -version
[  +47 ms] Exit code 0 from: /home/tisu/android-studio/jre/bin/java -version
[        ] openjdk version "1.8.0_242-release"
           OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b3-6222593)
           OpenJDK 64-Bit Server VM (build 25.242-b3-6222593, mixed mode)
[   +3 ms] executing: [/home/tisu/Flutter_2.0/vadamar/android/] /home/tisu/Flutter_2.0/vadamar/android/gradlew -Pverbose=true
-Ptarget-platform=android-arm64 -Ptarget=/home/tisu/Flutter_2.0/vadamar/lib/main.dart -Ptrack-widget-creation=true -Pfilesystem-scheme=org-dartlang-root
assembleDebug
[+5407 ms] > Task :app:compileFlutterBuildDebug
[        ] [ +106 ms] executing: [/home/tisu/development/flutter/] git -c log.showSignature=false log -n 1 --pretty=format:%H
[        ] [  +28 ms] Exit code 0 from: git -c log.showSignature=false log -n 1 --pretty=format:%H
[        ] [        ] 1aafb3a8b9b0c36241c5f5b34ee914770f015818
[        ] [        ] executing: [/home/tisu/development/flutter/] git tag --points-at HEAD
[        ] [  +12 ms] Exit code 0 from: git tag --points-at HEAD
[        ] [        ] 1.22.4
[        ] [   +7 ms] executing: [/home/tisu/development/flutter/] git rev-parse --abbrev-ref --symbolic @{u}
[        ] [   +2 ms] Exit code 0 from: git rev-parse --abbrev-ref --symbolic @{u}
[        ] [        ] origin/stable
[        ] [        ] executing: [/home/tisu/development/flutter/] git ls-remote --get-url origin
[        ] [   +3 ms] Exit code 0 from: git ls-remote --get-url origin
[        ] [        ] https://github.com/flutter/flutter.git
[        ] [  +41 ms] executing: [/home/tisu/development/flutter/] git rev-parse --abbrev-ref HEAD
[        ] [   +2 ms] Exit code 0 from: git rev-parse --abbrev-ref HEAD
[        ] [        ] stable
[        ] [  +35 ms] Artifact Instance of 'AndroidMavenArtifacts' is not required, skipping update.
[        ] [        ] Artifact Instance of 'AndroidGenSnapshotArtifacts' is not required, skipping update.
[        ] [        ] Artifact Instance of 'AndroidInternalBuildArtifacts' is not required, skipping update.
[        ] [        ] Artifact Instance of 'IOSEngineArtifacts' is not required, skipping update.
[        ] [        ] Artifact Instance of 'FlutterWebSdk' is not required, skipping update.
[        ] [   +1 ms] Artifact Instance of 'WindowsEngineArtifacts' is not required, skipping update.
[        ] [        ] Artifact Instance of 'MacOSEngineArtifacts' is not required, skipping update.
[        ] [        ] Artifact Instance of 'LinuxEngineArtifacts' is not required, skipping update.
[        ] [        ] Artifact Instance of 'LinuxFuchsiaSDKArtifacts' is not required, skipping update.
[        ] [        ] Artifact Instance of 'MacOSFuchsiaSDKArtifacts' is not required, skipping update.
[        ] [        ] Artifact Instance of 'FlutterRunnerSDKArtifacts' is not required, skipping update.
[        ] [        ] Artifact Instance of 'FlutterRunnerDebugSymbols' is not required, skipping update.
[        ] [   +8 ms] Artifact Instance of 'MaterialFonts' is not required, skipping update.
[        ] [        ] Artifact Instance of 'GradleWrapper' is not required, skipping update.
[        ] [        ] Artifact Instance of 'AndroidMavenArtifacts' is not required, skipping update.
[        ] [        ] Artifact Instance of 'AndroidGenSnapshotArtifacts' is not required, skipping update.
[        ] [        ] Artifact Instance of 'AndroidInternalBuildArtifacts' is not required, skipping update.
[        ] [        ] Artifact Instance of 'IOSEngineArtifacts' is not required, skipping update.
[        ] [        ] Artifact Instance of 'FlutterWebSdk' is not required, skipping update.
[        ] [        ] Artifact Instance of 'FlutterSdk' is not required, skipping update.
[        ] [        ] Artifact Instance of 'WindowsEngineArtifacts' is not required, skipping update.
[        ] [        ] Artifact Instance of 'MacOSEngineArtifacts' is not required, skipping update.
[        ] [        ] Artifact Instance of 'LinuxEngineArtifacts' is not required, skipping update.
[        ] [        ] Artifact Instance of 'LinuxFuchsiaSDKArtifacts' is not required, skipping update.
[        ] [        ] Artifact Instance of 'MacOSFuchsiaSDKArtifacts' is not required, skipping update.
[        ] [        ] Artifact Instance of 'FlutterRunnerSDKArtifacts' is not required, skipping update.
[        ] [        ] Artifact Instance of 'FlutterRunnerDebugSymbols' is not required, skipping update.
[        ] [        ] Artifact Instance of 'IosUsbArtifacts' is not required, skipping update.
[        ] [        ] Artifact Instance of 'IosUsbArtifacts' is not required, skipping update.
[        ] [        ] Artifact Instance of 'IosUsbArtifacts' is not required, skipping update.
[        ] [        ] Artifact Instance of 'IosUsbArtifacts' is not required, skipping update.
[        ] [        ] Artifact Instance of 'IosUsbArtifacts' is not required, skipping update.
[        ] [        ] Artifact Instance of 'FontSubsetArtifacts' is not required, skipping update.
[        ] [  +72 ms] Initializing file store
[        ] [  +15 ms] Skipping target: gen_localizations
[        ] [   +7 ms] kernel_snapshot: Starting due to {}
[        ] [  +24 ms] /home/tisu/development/flutter/bin/cache/dart-sdk/bin/dart --disable-dart-dev
/home/tisu/development/flutter/bin/cache/artifacts/engine/linux-x64/frontend_server.dart.snapshot --sdk-root
/home/tisu/development/flutter/bin/cache/artifacts/engine/common/flutter_patched_sdk/ --target=flutter -Ddart.developer.causal_async_stacks=true
-Ddart.vm.profile=false -Ddart.vm.product=false
--bytecode-options=source-positions,local-var-info,debugger-stops,instance-field-initializers,keep-unreachable-code,avoid-closure-call-instructions
--enable-asserts --track-widget-creation --no-link-platform --packages /home/tisu/Flutter_2.0/vadamar/.packages --output-dill
/home/tisu/Flutter_2.0/vadamar/.dart_tool/flutter_build/3622b39ecc2a811af4c3c799c83acf59/app.dill --depfile
/home/tisu/Flutter_2.0/vadamar/.dart_tool/flutter_build/3622b39ecc2a811af4c3c799c83acf59/kernel_snapshot.d package:vadamar/main.dart
[+6681 ms] [+8110 ms] kernel_snapshot: Complete
[+1100 ms] [+1053 ms] debug_android_application: Starting due to {}
[+1300 ms] [+1349 ms] debug_android_application: Complete
[ +799 ms] [ +767 ms] Persisting file store
[        ] [  +11 ms] Done persisting file store
[        ] [   +6 ms] build succeeded.
[        ] [   +8 ms] "flutter assemble" took 11,448ms.
[        ] [   +3 ms] ensureAnalyticsSent: 0ms
[        ] [   +1 ms] Running shutdown hooks
[        ] [        ] Shutdown hooks complete
[        ] [        ] exiting with code 0
[ +799 ms] > Task :app:packLibsflutterBuildDebug
[        ] > Task :app:preBuild UP-TO-DATE
[        ] > Task :app:preDebugBuild UP-TO-DATE
[        ] > Task :app:compileDebugAidl NO-SOURCE
[ +699 ms] > Task :app:checkDebugManifest
[ +500 ms] > Task :app:generateDebugBuildConfig
[   +1 ms] > Task :app:compileDebugRenderscript NO-SOURCE
[  +98 ms] > Task :app:cleanMergeDebugAssets UP-TO-DATE
[ +199 ms] > Task :app:mergeDebugShaders
[        ] > Task :app:compileDebugShaders
[        ] > Task :app:generateDebugAssets
[        ] > Task :app:mergeDebugAssets
[ +199 ms] > Task :app:copyFlutterAssetsDebug
[        ] > Task :app:mainApkListPersistenceDebug
[ +200 ms] > Task :app:generateDebugResValues
[        ] > Task :app:generateDebugResources
[ +898 ms] > Task :app:createDebugCompatibleScreenManifests
[ +400 ms] > Task :app:processDebugManifest
[        ] > Task :app:processDebugJavaRes NO-SOURCE
[ +199 ms] > Task :app:mergeDebugResources
[ +699 ms] > Task :app:processDebugResources
[+6800 ms] > Task :app:compileDebugKotlin
[ +100 ms] > Task :app:checkDebugDuplicateClasses
[        ] > Task :app:javaPreCompileDebug
[+2699 ms] > Task :app:compileDebugJavaWithJavac
[        ] > Task :app:compileDebugSources
[+1699 ms] > Task :app:transformClassesWithDexBuilderForDebug
[        ] > Task :app:validateSigningDebug
[  +99 ms] > Task :app:signingConfigWriterDebug
[ +100 ms] > Task :app:mergeDebugJavaResource
[        ] > Task :app:desugarDebugFileDependencies
[  +99 ms] > Task :app:mergeDebugJniLibFolders
[+1099 ms] > Task :app:mergeExtDexDebug
[ +599 ms] > Task :app:mergeDebugNativeLibs
[ +700 ms] Unable to strip library '/home/tisu/Flutter_2.0/vadamar/build/app/intermediates/merged_native_libs/debug/out/lib/x86_64/libflutter.so' due to
missing strip tool for ABI 'X86_64'. Packaging it as is.
[        ] Unable to strip library '/home/tisu/Flutter_2.0/vadamar/build/app/intermediates/merged_native_libs/debug/out/lib/arm64-v8a/libflutter.so' due to
missing strip tool for ABI 'ARM64_V8A'. Packaging it as is.
[ +300 ms] > Task :app:stripDebugDebugSymbols
[        ] Compatible side by side NDK version was not found.
[        ] Unable to strip library '/home/tisu/Flutter_2.0/vadamar/build/app/intermediates/merged_native_libs/debug/out/lib/x86/libflutter.so' due to
missing strip tool for ABI 'X86'. Packaging it as is.
[   +1 ms] > Task :app:mergeDexDebug
[+4596 ms] > Task :app:packageDebug
[  +99 ms] > Task :app:assembleDebug
[        ] BUILD SUCCESSFUL in 39s
[        ] 31 actionable tasks: 30 executed, 1 up-to-date
[ +361 ms] Running Gradle task 'assembleDebug'... (completed in 39.6s)
[  +42 ms] calculateSha: LocalDirectory: '/home/tisu/Flutter_2.0/vadamar/build/app/outputs/flutter-apk'/app.apk
[  +13 ms] calculateSha: reading file took 12us
[ +662 ms] calculateSha: computing sha took 662us
[   +4 ms] ✓ Built build/app/outputs/flutter-apk/app-debug.apk.
[   +2 ms] executing: /home/tisu/Android/Sdk/build-tools/29.0.3/aapt dump xmltree /home/tisu/Flutter_2.0/vadamar/build/app/outputs/flutter-apk/app.apk
AndroidManifest.xml
[ +700 ms] Exit code 0 from: /home/tisu/Android/Sdk/build-tools/29.0.3/aapt dump xmltree
/home/tisu/Flutter_2.0/vadamar/build/app/outputs/flutter-apk/app.apk AndroidManifest.xml
[   +2 ms] N: android=http://schemas.android.com/apk/res/android
             E: manifest (line=2)
               A: android:versionCode(0x0101021b)=(type 0x10)0x1
               A: android:versionName(0x0101021c)="1.0.0" (Raw: "1.0.0")
               A: android:compileSdkVersion(0x01010572)=(type 0x10)0x1d
               A: android:compileSdkVersionCodename(0x01010573)="10" (Raw: "10")
               A: package="com.example.vadamar" (Raw: "com.example.vadamar")
               A: platformBuildVersionCode=(type 0x10)0x1d
               A: platformBuildVersionName=(type 0x10)0xa
               E: uses-sdk (line=7)
                 A: android:minSdkVersion(0x0101020c)=(type 0x10)0x10
                 A: android:targetSdkVersion(0x01010270)=(type 0x10)0x1d
               E: uses-permission (line=14)
                 A: android:name(0x01010003)="android.permission.INTERNET" (Raw: "android.permission.INTERNET")
               E: application (line=22)
                 A: android:label(0x01010001)="vadamar" (Raw: "vadamar")
                 A: android:icon(0x01010002)=@0x7f080000
                 A: android:name(0x01010003)="io.flutter.app.FlutterApplication" (Raw: "io.flutter.app.FlutterApplication")
                 A: android:debuggable(0x0101000f)=(type 0x12)0xffffffff
                 A: android:appComponentFactory(0x0101057a)="androidx.core.app.CoreComponentFactory" (Raw: "androidx.core.app.CoreComponentFactory")
                 E: activity (line=28)
                   A: android:theme(0x01010000)=@0x7f0a0000
                   A: android:name(0x01010003)="com.example.vadamar.MainActivity" (Raw: "com.example.vadamar.MainActivity")
                   A: android:launchMode(0x0101001d)=(type 0x10)0x1
                   A: android:configChanges(0x0101001f)=(type 0x11)0x40003fb4
                   A: android:windowSoftInputMode(0x0101022b)=(type 0x11)0x10
                   A: android:hardwareAccelerated(0x010102d3)=(type 0x12)0xffffffff
                   E: meta-data (line=42)
                     A: android:name(0x01010003)="io.flutter.embedding.android.NormalTheme" (Raw: "io.flutter.embedding.android.NormalTheme")
                     A: android:resource(0x01010025)=@0x7f0a0001
                   E: meta-data (line=52)
                     A: android:name(0x01010003)="io.flutter.embedding.android.SplashScreenDrawable" (Raw:
                     "io.flutter.embedding.android.SplashScreenDrawable")
                     A: android:resource(0x01010025)=@0x7f040000
                   E: intent-filter (line=56)
                     E: action (line=57)
                       A: android:name(0x01010003)="android.intent.action.MAIN" (Raw: "android.intent.action.MAIN")
                     E: category (line=59)
                       A: android:name(0x01010003)="android.intent.category.LAUNCHER" (Raw: "android.intent.category.LAUNCHER")
                 E: meta-data (line=66)
                   A: android:name(0x01010003)="flutterEmbedding" (Raw: "flutterEmbedding")
                   A: android:value(0x01010024)=(type 0x10)0x2
[  +15 ms] Stopping app 'app.apk' on SM A515F.
[   +2 ms] executing: /home/tisu/Android/Sdk/platform-tools/adb -s R58N23DVJ5Z shell am force-stop com.example.vadamar
[ +196 ms] executing: /home/tisu/Android/Sdk/platform-tools/adb -s R58N23DVJ5Z shell pm list packages com.example.vadamar
[ +168 ms] package:com.example.vadamar
[   +6 ms] executing: /home/tisu/Android/Sdk/platform-tools/adb -s R58N23DVJ5Z shell cat /data/local/tmp/sky.com.example.vadamar.sha1
[  +67 ms] cat: /data/local/tmp/sky.com.example.vadamar.sha1: No such file or directory
[        ] Installing APK.
[   +1 ms] executing: /home/tisu/Android/Sdk/platform-tools/adb version
[   +3 ms] Android Debug Bridge version 1.0.41
           Version 30.0.4-6686687
           Installed as /home/tisu/Android/Sdk/platform-tools/adb
[        ] executing: /home/tisu/Android/Sdk/platform-tools/adb start-server
[   +4 ms] Installing build/app/outputs/flutter-apk/app.apk...
[        ] executing: /home/tisu/Android/Sdk/platform-tools/adb -s R58N23DVJ5Z install -t -r
/home/tisu/Flutter_2.0/vadamar/build/app/outputs/flutter-apk/app.apk
[+21090 ms] Performing Streamed Install
                     Success
[        ] Installing build/app/outputs/flutter-apk/app.apk... (completed in 21.1s)
[   +1 ms] executing: /home/tisu/Android/Sdk/platform-tools/adb -s R58N23DVJ5Z shell echo -n 89114d2b8149117cb88a6e7bc6ce7b86f738af91 >
/data/local/tmp/sky.com.example.vadamar.sha1
[  +41 ms] SM A515F startApp
[   +2 ms] executing: /home/tisu/Android/Sdk/platform-tools/adb -s R58N23DVJ5Z shell am start -a android.intent.action.RUN -f 0x20000000 --ez
enable-background-compilation true --ez enable-dart-profiling true --ez enable-checked-mode true --ez verify-entry-points true
com.example.vadamar/com.example.vadamar.MainActivity
[ +276 ms] Starting: Intent { act=android.intent.action.RUN flg=0x20000000 cmp=com.example.vadamar/.MainActivity (has extras) }
[   +1 ms] Waiting for observatory port to be available...

Tagging @TahaTesser for visibility.

Hi @Tisanthan
Sorry, I mistook your issue earlier for something else, this seems to be related to packages
From https://github.com/flutter/flutter/issues/70852#issuecomment-731503633
You need to update your flutter packages, execute flutter update-packages  and make sure you flutter SDK in pubspec.yaml i updated as well
So when you run the app from the snap, it fails? but form terminal, it is using non-snap flutter
[   +2 ms] executing: [/home/tisu/development/flutter/] git tag --points-at HEAD
build is successful based on the logs, are you able the run the app from the terminal?
Can you please more details and provide reproducible steps?

Hi @Tisanthan
Sorry, I mistook your issue earlier for something else, this seems to be related to packages
From #70852 (comment)
You need to update your flutter packages, execute flutter update-packages and make sure you flutter SDK in pubspec.yaml i updated as well
So when you run the app from the snap, it fails? but form terminal, it is using non-snap flutter
[ +2 ms] executing: [/home/tisu/development/flutter/] git tag --points-at HEAD
build is successful based on the logs, are you able the run the app from the terminal?
Can you please more details and provide reproducible steps?

I have removed the flutter that I had installed by snap
then after I had upgraded flutter Now VScode debugging working well
Thank you for your valuable help
@iapicca @TahaTesser @darshankawar


Live producer threads and dynamic-destination-cache-size property

We have detected a problem in the increase of resources when there are configured in an application more bindings out (producers) which value has the property spring.cloud.stream.dynamic-destination-cache-size (default 10).
The problem is that the created threads grow without control and are not released, and in some cases consuming memory and even occupying all the descriptors of the system causing the application to fail.
Is this an expected behavior? the only solution is to increase the value of the spring.cloud.stream.dynamic-destination-cache-size property?
Attached is an application that reproduces the case we explained and we add a screenshot with the threads created are only 2 binding and spring.cloud.stream.dynamic-destination-cache-size=1:

demoDynamicDestinationCache.zip

@ferblaca Good to hear that the issue has been resolved once you upgraded. We will see if we can update the release notes. In the meantime, can we close this issue? Is there anything more to be done on this?


select columns doesnt support raw select

example:
sql, args := query.ToSQL(&pop.Model{Value: models.Activity{}}, "distinct on (activities.weight,activities.name) activities.*",
		"fieldother", "fieldother2")

expected
select distinct on (activities.weight,activities.name) activities.*, fieldother, fieldother2 from activities

i can see that it tries to prepend table name when 1 field contains read/writable flag.
can we add in support for raw sql by adding suffix ::raw as last charactor?
thanks
func (c *Columns) Add(names ...string) []*Column {
	ret := []*Column{}
	c.lock.Lock()
	for _, name := range names {
		xs := strings.Split(name, ",")
		col := c.Cols[xs[0]]
		if col == nil {
			ss := xs[0]
			if c.TableName != "" {
				ss = fmt.Sprintf("%s.%s", c.TableName, ss)
			}
			col = &Column{
				Name:      xs[0],
				SelectSQL: ss,
				Readable:  true,
				Writeable: true,
			}

			if len(xs) > 1 {
				if xs[1] == "r" {
					col.Writeable = false
				}
				if xs[1] == "w" {
					col.Readable = false
				}
			} else if col.Name == "id" {
				col.Writeable = false
			}

			c.Cols[col.Name] = col
		}
		ret = append(ret, col)
	}
	c.lock.Unlock()
	return ret
}

i will do a pull request to support distinct select column


Improve RTL Tests

WHAT
WHY
HOW
Checklist :clipboard:

[ ] Add explicit visibility modifier and explicit return types for public declarations
[ ] Run spotless check
[ ] Run tests
[ ] Update metalava's signature text files

@garanj tests only, will land


Error when trying to unrar archive with subfolders

Here is an example of the file:
test.zip
/testfolder/
file1.jpg
file2.jpg
When using archive.Unzip, it behaves as expected -- creates the subfolders as they are in the zip archive:
err := archiver.Unzip("c:\\tmp\\test.zip", "c:\\tmp\\test\\")
However when running the same command to unrar, it appears as though it's not able to Mkdir the subfolders.
err := archiver.Unrar("c:\\tmp\\test.rar", "c:\\tmp\\test\\")
Error:

c:\tmp\test\testfolder\file1.jpg: creating new file: open c:\tmp\test\testfolder\file1.jpg: The system cannot find the path specified.

If it helps, line 41 of rar.go is checking
if header.IsDir but it seems to evaluate as false, since technically the path includes both the folder and the filename (I'm assuming).

Thanks for the report! So are file1.jpg and file2.jpg inside testfolder?

correct, those files are within the subfolder (inside the archive).

Thanks. Can you send me the .rar file? I don't have a way to make them (and I'd rather not install one on my Mac... heh) :smile: My email address is at https://matt.chat.

No problem, sent you the file I've been testing against.

Got it, thanks. Will check it out soon!

Quick and dirty string comparison workaround here:
https://github.com/mholt/archiver/pull/7
I'm sure there are better ways of approaching this, but this seemed simple enough to be a viable solution.

Fixed in #7. Thank you!

I've published a new release with this and another fix: https://github.com/mholt/archiver/releases/tag/v1.1.1


Support of old GNU df

How about supporting old df commands? Without option output but P.

I added the --output usage to fix MSYS2/Cygwin, which otherwise prints the full windows path to the Cygwin installation as the "filesystem", this breaks things if there are any spaces in the path, since the read command splits on spaces.  I could make a check that only does the workaround on MSYS and Cygwin.


support last version pytorch

https://github.com/Nuitka/Nuitka/issues/1891
@[kayhayen] Actually kind of all are supported, but every PyPI release can invalidate that information. Right now we do not have automatic regression testing of all of PyPI, but we hope to get there.
@[kayhayen] This is part of the hotfix release 1.2.2 that I just made.
Updated, but did not help. Still the same error:
Nuitka-Plugins:WARNING: torch: This plugin has been deprecated, do not enable it anymore.
version of pytorch 1.3.0 as said cannot be installed, it is not in official source. only from version 1.11.0

That 1.3.0 was probably a typo of 1.13.0


Deploying on GKE using the helm chart not working

My actions before raising this issue

Following the official documentation for using the official Helm Chart documentation
Deployment of cvat works for all deployments except workers both the low and default
Checking Deployment logs using GKE console

Multi-Attach error for volume "pvc-856156a9-8f5e-4ac1-9b5e-e39a490f26c1" Volume is already used by pod(s) mc-backend-worker-default-75bdfc7d9f-4l2w2, mcit-backend-utils-845b68fb99-8wls9, mc-backend-server-74fb85b6c7-pk6kq

Expected Behaviour
Deployment of chart should work on GKE
suggesting a change/improvement, tell us how it should work -->
Current Behaviour
Deployment of utils, default and low worker stuck, which one is stuck is based on competition on the created shared volume
Possible Solution
Avoid using shared folder
or, using affinity to ensure deployment on single node
Steps to Reproduce (for bugs)

Change configuration following instructions
run helm upgrade -n cvat mcit -i --create-namespace ./helm-chart -f ./helm-chart/values.yaml -f ./helm-chart/values.override.yaml

Context
GKE supports Read/Write shared volumes for pods attached to the same node, cross node attachment for Read/Write is not allowed
Your Environment

GKE cluster version: 1.22.12-gke.2300
cvat release: 2.2

@ahmedrshdy , do you still have the issue in the latest release?

I'm still seeing this on 0.7.2 (on-prem RKE, not GKE).

I'm stuck having the same issue as described in the original post (I'm trying to deploy helm-chart that is currently available (for CVAT v2.4.1)

I still have this exact same issue when trying to deploy in cloud (We dont have ReadWriteMany volumes, i cannot set affinity to make pods run on single node (permissions)

Unfortunately I gave up k8s deployment

Sadly cvat right now is designed to use RWX volume, so you could not proceed without one AFAIK.
Also I believe, that GKE supports them:
https://cloud.google.com/filestore/docs/optimize-multishares

I have a deployment that uses ReadWriteOnce via helm and it works fine, you do have to use podaffinity rules to schedule all the pods on the same node though. Example for every backend service:
affinity:     podAffinity:       requiredDuringSchedulingIgnoredDuringExecution:         - labelSelector:             matchExpressions:             - key: tier               operator: In               values:               - backend           topologyKey: "kubernetes.io/hostname"

fixed in #6137


New version: ossia.score version 3.2.3

Pull request has been created with komac v2.3.0 :rocket:
Microsoft Reviewers: Open in CodeFlow

/azp run

This package installs and launches normally on a Windows 10 VM.


Fixed doc link

@joel-hamill the #downgrade part isn't working for me...

@tamarrow Can you try again? Worked for me just now: http://cl.ly/2E2C0X3Y3w1a.

works for me now, weird. will merge once tests pass


Add ICCV deadline

Added deadline for International Conference on Computer Vision (ICCV) 2019 based on their website.

Thanks!

My pleasure. Thanks for building this amazing tool! Keep up the good work.


Crash when rendering items in Creative inventory

Issue description:
When I view some items in the Creative inventory or through JEI (namely anything built on ItemNetworkItem), my game crashes.
What happens:
Crash.
What you expected to happen:
Actually be able to use the mod.
Steps to reproduce:

Open the Creative inventory
Click the Refined Storage tab
Watch as your hopes and dreams come crashing down around you (pun intended)

Version (Make sure you are on the latest version before reporting):

Minecraft: 1.10.2
Forge: <IP_ADDRESS>5
Refined Storage: 1.2.4

Does this issue occur on a server? [yes/no]
Probably, though I'm finding it in singleplayer.
If a (crash)log is relevant for this issue, link it here:
https://gist.github.com/tripl3dogdare/ebc7c697548cdd72b9e8e24e24b44077

You have a bad RF api in some mod. Check if you have some old jar just sitting in there or try swapping out some mods. You could always install enderio, since they report the loaded RF api when something like this happens.

After following your advice and digging around for a while, it turns out I was using Extra Utilities and not Extra Utilities 2. No idea how a 1.8 mod even loaded at all on 1.10, but apparently it did. Thank you!

np, yeah the mod that provides the api doesn't even have to be loaded. Glad it worked out!


do_join/anti_join ignore na_action

Describe the bug, including details regarding any error messages, version, and platform.
library(dplyr)
library(arrow)

dat1 <- data.frame(a=1:5, b=c(11:14, NA))
dat2 <- dat1[-3,]
dat1arr <- arrow_table(dat1)
dat2arr <- arrow_table(dat2)

anti_join(dat1, dat2, by = names(dat1), na_matches = "na")
#   a  b
# 1 3 13
anti_join(dat1arr, dat2arr, by = names(dat1), na_matches = "na") |>
  collect()
# # A tibble: 2 × 2
#       a     b
#   <int> <int>
# 1     3    13
# 2     5    NA

I see https://github.com/apache/arrow/blob/main/r/R/dplyr-join.R#L31 from commit https://github.com/apache/arrow/commit/c273ea72097a0ca4d45eef4ce10db29a813bda66 in Sep 2021, is there a timeline for implementation?
Component(s)
R

dupe of https://github.com/apache/arrow/issues/37902


Rename norwegian language translations folder

The norwegian translations folder was wrongly named in previous commit
after a copy and merge.

Thanks!


sc-11339 Refactor Certificate inventory feature

Scope of changes
sc-11339 Refactor Certificate inventory feature
Type of change

[ ] bug fix
[ ] new feature
[ ] documentation
[x] refact

Acceptance criteria
https://app.shortcut.com/rotational/story/11339/refactor-certificate-inventory-feature
Author checklist

[x] I have manually tested the change and/or added automation in the form of unit tests or integration tests
[ ]  I have updated the dependencies list
[ ]  I have recompiled and included new protocol buffers to reflect changes I made
[ ]  I have added new test fixtures as needed to support added tests
[x]   Check this box if a reviewer can merge this pull request after approval (leave it unchecked if you want to do it yourself)
[x]  I have moved the associated Shortcut story to "Ready for Review"

Reviewer(s) checklist

[ ] Any new user-facing content that has been added for this PR has been QA'ed to ensure correct grammar, spelling, and understandability.

Codecov Report
Base: 44.49% // Head: 44.58% // Increases project coverage by +0.09% :tada:

Coverage data is based on head (945bfa9) compared to base (c614d85).
 Consider uploading reports for the commit 6895676 to get more accurate results

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #901      +/-   ##
==========================================
+ Coverage   44.49%   44.58%   +0.09%
==========================================
  Files         678      667      -11
  Lines       24439    24167     -272
  Branches     1531     1517      -14
==========================================
- Hits        10875    10776      -99
+ Misses      12175    12019     -156
+ Partials     1389     1372      -17

Flag
Coverage Δ

unittests
44.58% <ø> (+0.09%)
:arrow_up:

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

Impacted Files
Coverage Δ

web/gds-user-ui/src/application/routes/routes.ts
80.00% <ø> (ø)

...rtificateManagement/MainnetTestnetCertificates.tsx
100.00% <ø> (ø)

web/gds-user-ui/src/utils/menu.tsx
100.00% <ø> (ø)

...rc/components/CertificateManagement/Statistics.tsx
0.00% <0.00%> (-100.00%)
:arrow_down:

...components/CertificateManagement/StatisticCard.tsx
0.00% <0.00%> (-100.00%)
:arrow_down:

web/gds-user-ui/src/utils/date.ts
0.00% <0.00%> (-50.00%)
:arrow_down:

...ds-user-ui/src/modules/dashboard/profile/index.tsx
0.00% <0.00%> (-33.34%)
:arrow_down:

...crypto/directory/pkg/bff/models/v1/organization.go
74.57% <0.00%> (-4.74%)
:arrow_down:

web/gds-user-ui/src/utils/utils.ts
40.32% <0.00%> (-2.54%)
:arrow_down:

.../github.com/trisacrypto/directory/pkg/bff/users.go
54.50% <0.00%> (-2.30%)
:arrow_down:

... and 41 more

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

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


order parameter binding before pass to execute

fixed an issue that occur if parameters are passed in a different order
than in the sql statement specified.

ack


Code refractor for read query in metering

ok to test

retest this please

Retest this please

retest this please

Build finished.

Build finished.

Combine flyway schema in one single file, and include other tables for AAA, CAT, etc. @gopal-mahajan please help @ankitmashu with table schema for other servers.

Solved

Build finished.

Build finished.

Build finished.

Build finished.

retest this please

Build finished.


ignore the build directory

The commit adds the build/ directory to gitignore and CDNs within the HTML examples, as discussed here: https://github.com/unconed/mathbox/issues/21.
Additionally, I added rm -rf build to the build script because when Typescript rebuilds, it does NOT remove old files. This has caused me problems in other projects, and I'd like to avert those problems here.

@sritchie Let me know if you have thoughts about this... See also comments in #21

I am really happy these are gone. PRs will be much simpler now.


Setting bucket based on ID

There were old functions commented out that normalized the ID to an integer. I uncommented those and sent the userId to the generate bucket function.
I also uncommented the tests for normalizeId, though I never could get any of the tests to run even before adding these back in.
This will fix the bucket to the userId, which is sent in through in woodruff and snow's experiments middleware. When userId is null or is the wrong type, the old way is used as the fallback.

@redbugz: the fix might be easier than originally thought if this is alright.

I've fixed the tests by upgrading vows and merged that into master. You can now test this pull request locally by checking out master and then running
$ hub am -3 https://github.com/fs-webdev/experiment/pull/11
$ npm test

Notice that all the tests run.  Still, I'm not sure if we should accept the pull request just yet. I don't recall why we abandoned this hashing function in the first place. Was it only because people would change buckets once they logged in? If so, I think we need to merge this.  If there is some other reason then we need to identify it.

I couldn't find any reason why these were commented out. However, it happened in this commit: https://github.com/fs-webdev/experiment/commit/d2902bfce1efffebebde7abf8e9f0437bef18bec

Actually, looking at the commit before the one where it was commented out provides more insight. It looks like they just weren't using it anymore: https://github.com/fs-webdev/experiment/commit/29d187dde9836c8da43eb85dacf7af990e406f8c

+1

I'm going to take a look at this today.

I was told this morning that there was some uncertainty still about why they originally abandoned the hashing function. If you look at https://github.com/fs-webdev/experiment/commit/29d187dde9836c8da43eb85dacf7af990e406f8c, you can see that the normalize function stopped being used in favor of using session ids to calculate percentage buckets. They no longer needed to hash the userId in other places (adding users to groups) to keep things consistent, so they didn't. The functions got commented out in the next commit because nobody was using them anymore.

I spoke with Stephen Lynn. His vague recollection is that they disabled experiments that keyed off the user id because that was causing experiments to toggle on and off when you logged in and out, which was a problem for apps like search, home, and photos that have both authenticated and unauthenticated views. The replacement algorithm was supposed to preserve your bucket ID across recalculations of the cookie. My guess is that algorithm is now broken, so it is not preserved.
However, this fix will make percentages difficult to use for partially unauthenticated apps like home and search.
So a permanent solution to this problem will need to be designed that addresses the needs of both authenticated and unauthenticated experiments, but that is beyond the scope of this PR at this time.
So we either can take this PR at the expense of unauthenticated apps temporarily until the permanent solution is developed with their approval, or we will need to defer this until the permanent fix is established. We will work with the other teams to see if they are okay with the limitation imposed by this PR in the interim.

I have tested this the best I know how and the only issue I found, after consulting with Logan (@redbugz), is that logged out users are always put into bucket 7 because their username is always '-anon-'.  So I am going to fix this by forcing the '-anon-' user to be randomly assigned a bucket.

Excellent @jasonallen68 ! Thank you.

It turns out that the best way to fix the unauthenticated users issue is to fix it in Frontier (woodruff, snow).  So for this PR, I'm going to update the Experiment version and merge it and create a release.  Then I will fix woodruff and snow and pin to the new Experiment release.

@rosemariesadler @redbugz It has been 2.5 years for this PR...should we just close it? It doesn't sound like a huge issue if we've been fine living with it for this long.

I thought this did get merged. Hm. Well when the issue of turning on percentage based experiments comes up again, the issue that this was trying to solve will come up again. But I don't know if another solution is going to be better.

Closing for now. If was was super important, then it should have been merged 2.5 years ago, or we'd still be talking about it, but we aren't to my knowledge.


Rename NEAR chain -> Aurora

Coverage decreased (-0.4%) to 90.941% when pulling b8f66ace4a919e4823b17219ea39903e3d2af1c9 on rename-aurora into 76c4d943fd6b8857990c206f07ad26d75ab51754 on master.


Handling many-to-many relations with *gorm.DB.Create

I'm currently trying two insert two 'pictures' in table Picture. These pictures have tags, and so share a many-to-many relation with table Tag.
See here the structs:
//Picture is a default DB structure for GORM
type Picture struct {
	ID        int
	Title     string
	URL       string
	CreatedAt time.Time
	UpdatedAt time.Time

	Tags []Tag `gorm:"many2many:picture_tags;"`
}

//Tag is a default DB structure for GORM
type Tag struct {
	ID        int
	Name      string
	CreatedAt time.Time
	UpdatedAt time.Time

	Pictures []Picture `gorm:"many2many:picture_tags;"`
}

With the function MockData i'm putting test data in the Database:
//MockData creates two instants of pictures with 4 tags
func MockData(db *gorm.DB) {
	baby := Tag{
		Name: "Baby",
	}

	cat := Tag{
		Name: "Cat",
	}

	gif := Tag{
		Name: "Gif",
	}

	shit := Tag{
		Name: "Shit",
	}

	picture := Picture{
		Title: "Dancing Baby Gif",
		URL:   "https://45.media.tumblr.com/07106512835c07d2a237a4d12479c7f8/tumblr_mpg5arui7E1s1clzao1_250.gif",
		Tags:  []Tag{baby, gif, shit},
	}

	picture2 := Picture{
		Title: "Dancing Cat Gif",
		URL:   "http://rs143.pbsrc.com/albums/r146/sconti1369/Funny_Pictures_Animated_Dancing_Cat.gif~c200",
		Tags:  []Tag{cat, gif, shit},
	}

	db.Create(&picture)
	db.Create(&picture2)
}

The result should be two pictures in table Picture, and four tags in table Tag, as two tags are shared between the pictures and 2 are unique.
This is not the case. Table Picture is OK:
[
   {
      "ID":1,
      "Title":"Dancing Baby Gif",
      "URL":"https://45.media.tumblr.com/07106512835c07d2a237a4d12479c7f8/tumblr_mpg5arui7E1s1clzao1_250.gif",
      "CreatedAt":"2015-12-08T19:58:55.631519+01:00",
      "UpdatedAt":"2015-12-08T19:58:55.631519+01:00",
      "Tags":null
   },
   {
      "ID":2,
      "Title":"Dancing Cat Gif",
      "URL":"http://rs143.pbsrc.com/albums/r146/sconti1369/Funny_Pictures_Animated_Dancing_Cat.gif~c200",
      "CreatedAt":"2015-12-08T19:58:55.639515+01:00",
      "UpdatedAt":"2015-12-08T19:58:55.639515+01:00",
      "Tags":null
   }
]

(Don't look at the "Tags":null part. I'm not doing a query for them, but it works when requesting only a single ID)
The Tags table is problematic:
[
   {
      "ID":1,
      "Name":"Baby",
      "CreatedAt":"2015-12-08T19:58:55.633513+01:00",
      "UpdatedAt":"2015-12-08T19:58:55.633513+01:00",
      "Pictures":null
   },
   {
      "ID":2,
      "Name":"Gif",
      "CreatedAt":"2015-12-08T19:58:55.636512+01:00",
      "UpdatedAt":"2015-12-08T19:58:55.636512+01:00",
      "Pictures":null
   },
   {
      "ID":3,
      "Name":"Shit",
      "CreatedAt":"2015-12-08T19:58:55.638514+01:00",
      "UpdatedAt":"2015-12-08T19:58:55.638514+01:00",
      "Pictures":null
   },
   {
      "ID":4,
      "Name":"Cat",
      "CreatedAt":"2015-12-08T19:58:55.640522+01:00",
      "UpdatedAt":"2015-12-08T19:58:55.640522+01:00",
      "Pictures":null
   },
   {
      "ID":5,
      "Name":"Gif",
      "CreatedAt":"2015-12-08T19:58:55.642518+01:00",
      "UpdatedAt":"2015-12-08T19:58:55.642518+01:00",
      "Pictures":null
   },
   {
      "ID":6,
      "Name":"Shit",
      "CreatedAt":"2015-12-08T19:58:55.643519+01:00",
      "UpdatedAt":"2015-12-08T19:58:55.643519+01:00",
      "Pictures":null
   }
]

Tag 'Gif' and 'Shit' are being duplicated which they should not be. Searching for tag Gif should return 1 row, and when requesting for this ID should show two linked pictures instead of one.
Removing the 	```Pictures []Picture `gorm:"many2many:picture_tags;"```` line from Tag doesn't solve the problem, but makes it more of a hassle to search corresponding pictures from tags. The tags are still being duplicated.
Hope someone can help!
Rivalo

Fixed this by just creating the Pictures, then the Tags, and then using the .append method (as given in the Many2Many examples) to append the Tag to the Picture.

I've just run into this issue. I feel db.Create should have a way of using existing records in relationships such as this, provided there is a unique/unique_index field specified on (in this example) Tag.


Updated "File Upload with Progress Callback" code snippet in README.md.

Resolved a mismatch between variable names imageData and data.
Updated to the current appendPartWithFileData:name:fileName:mimeType: method signature.
Updated to the current upload progress block signature ^(NSInteger bytesWritten, NSInteger totalBytesWritten, NSInteger totalBytesExpectedToWrite) {...}
Added two lines that create an ad-hoc AFHTTPClient instance, instead of referencing a hypothetical [AFHTTPClient sharedClient] singleton, which new users might be confused by when they're trying to get the example working.

Geez, I thought the README was still pretty up-to-date. How wrong I was. Thanks for sending those fixes in, Larry.


Fixed typo and duplicate word on string 08

@timotheeguerin what about this one? :slightly_smiling_face:

Missed that one


Update endpoint URL to the log server

Coverage remained the same at 97.526% when pulling 68ef8b82606a07eece68efee8c5d81d90f0f9f95 on roman/new-endpoint into 36fe7388f61975a919927e984cbf049076f9d759 on devel.


reinstantiate item to prior position in list when item is returned from Last Recently Used

When an item is "resurrected" from "Last Recently Used" it would be nice if it remembered its prior order in the list.

@bnfinet I like the idea, but I'm unsure what "prior order" even means in this situation, because the list can change after an item is removed from the list (by moving, removing, or adding items).
It could be -

the same position counted from the top
before the same item as before
after the same item as before
a mixture of the possibilities above

What do you think about this?

I'm not sure either.
If I think of the use case for consistency, it's familiarity over time for
quick marking of done or resurrection from LRU or perhaps convenience while
shopping.  Perhaps I put flour, cheese, milk in that order because it
mimics the shopping aisles and location of the items in the store.  But
also it's being able to quickly locate bread from either the list (to mark
off) or LRU.
But regardless of the aisles in the store, the point that I want
convenience most is ressurect from a long LRU. m uncertain of what's best.
Maybe
LRU should just always be alpha numeric sorted.
Some of our lists are 15 items but most are 10 (though I think they're
gonna grow).
Perhaps each item's ordinal is to the combined set of LRU and current
items.  When an item is moved or created, set it's ordinal in the combined
list to the item above +1 or to first if it's moved to the top of the
list.  And adjust all other item ordinals accordingly.
That feels about right to me.
On Wed, Apr 24, 2019, 5:17 AM Joe Reuter<EMAIL_ADDRESS>wrote:

@bnfinet https://github.com/bnfinet I like the idea, but I'm unsure
what "prior order" even means in this situation, because the list can
change after an item is removed from the list (by moving, removing, or
adding items).
It could be -

the same position counted from the top
before the same item as before
after the same item as before
a mixture of the possibilities above

What do you think about this?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/flash1293/ekofe/issues/158#issuecomment-486203816,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAJUV26HHHV2AXH3TWEZVXLPSBFXBANCNFSM4HFQCRAQ
.


[FLINK-30119] Breaking change: Flink Kubernetes Operator should store…

… last savepoint in the SavepointInfo.lastSavepoint field whether it is completed or pending
What is the purpose of the change
End user experience proposal:
User can see the properties of last savepoint pending or completed and can get status in one of three states for the status: PENDING, SUCCEEDED and ABANDONED. If there is never savepoint taken or attempted, it is empty. Completed savepoints (manual, periodic and upgrade) are included Savepoint history, merged with savepoints form Flink job.
User can manually trigger a savepoint. If there is another savepoint pending, triggering is disabled. User can see this savepoint with PENDING status. Once completed, user can see last savepoint status changed to SUCCEEDED and included in savepoint history or ABANDONED and not in savepoint history. If there is other savepoint triggered after completion before user checks, user cannot see the status of the one they triggered but they can check if the savepoint is in the history.
Currently lastSavepoint only stores the last completed one, duplicate with savepoint history.
To expose the properties of the currently pending savepoint or last savepoint that failed, we need to expose those info in separate fields in SavepointInfo. The internal logic of Operator uses those fields for triggering and retries and creates compatibility issues with client.
Code change proposal:
Use lastSavepoint to store the last completed/attempted one and remove SavepointInfo.triggerTimstamp, SavepointInfo.triggerType and SavepointInfo.formatType.
Add SavepointInfo::retrieveLastSavepoint method to return the last succeeded one.
Update getLastSavepointStatus to simplify the logic and change SavepointStatus.ABANDONED state to FAILED.
This is a breaking change:

Existing application using lastSavepoint or trigger related fields in Savepoint info except triggerId may be broken.
For triggerId dependence, better use SavepointUtils.savepointInProgress which is guaranteed to work.
savepointHistory is not changed and still keeps the completed savepoints only. Unit tests for savepoint history also cover a few scenarios.

Brief change log

Use Savepoint.lastSavepoint to store last savepoint, completed or attempted .
Added SavepointInfo::retrieveLastCompletedSavepoint() method to find the last completed one.
Updated related logic.
Added migration logic to handle lingering trigger information on old CR

Verifying this change
This change added tests and can be verified as follows:
(example:)

Updated existing tests to check for regression.
Added tests for migration and backward compatibility with old CR
Updated e2e testes to remove tests that are no longer needed

Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): no
The public API, i.e., is any changes to the CustomResourceDescriptors: no
Core observer or reconciler logic that is regularly executed: yes

Documentation

Does this pull request introduce a new feature? yes
If yes, how is the feature documented?  JavaDocs and will roll into public doc

After discussing it with Clara, I'm colsing this for the time being.


Update to google protobuf v23.4

google/protobuf/descriptor.proto and google/protobuf/compiler/plugin.proto have changed for editions.
Some unittest proto files have been updated with editions. Since our plugin does not support them yet, we skip generating them. These proto files are only used to test code generation. We will include them again once we have sufficient support for editions.

nit: PR name should be 24.4


deps: tools: up esbuild to v0.15.10

Details are here https://github.com/evanw/esbuild/releases/tag/v0.15.10.

fixed by #435


Correction for raw affiliation Cemagref, UMR TETIS, Montpellier, France

Correction needed for raw affiliation Cemagref, UMR TETIS, Montpellier, France
raw_affiliation_name: Cemagref, UMR TETIS, Montpellier, France
new_rors: ;0458hw939
previous_rors:
works_examples: W2166204808;W2119345669
contact: db6d7de0cdc38383d79237ba35946061:362b2394f3afbbc06e31e8124919d2244fa7 @ inrae.fr

This issue was accepted and ingested by the OpenAlex team on 2024-12-19. The new affiliations should be visible within the next 7 days.


Cant reach container's in other hosts in virtualbox

Hi,
Im making some tests locally using virtual-box, and i create a stack that run some containers in diff hosts.
im having some issues and i found container's communication between  host's are not working.
Example:
Im running a docker container in host A that are linked to a redis container in host B with link-name redis-link . So inside container in Host A i ping the link name and getting no response.
this is stack im using to test

this is infrastructure

and this is ping and dig result.

version

The host in the UI with IP (<IP_ADDRESS>) is most likely the the docker internal IP and will not work. You will need to re-register your host with the correct IP.
After that, your containers should be able to communicate. If you get Please re-register this agent in the agent logs, then you might be hitting https://github.com/rancher/rancher/issues/1528. The workaround is in the second comment.

@fernandoneto Please let me know if you have corrected the IP of your host to see if your containers on different hosts can communicate.

@deniseschannon yes i correct the host ip but the problem persist.
using something like this to start the agent docker run -d -e CATTLE_AGENT_IP=<IP_ADDRESS> -v /var/run/docker....  and in host UI the correct IP is show, but when starting containers in diff host's they don't communicate .

@fernandoneto Can you look at the troubleshooting FAQs to make sure the expected networking is set up correctly?
http://docs.rancher.com/rancher/faqs/troubleshooting/

@deniseschannon ok thanks

running with this version's seems to resolve the problem.
i also run the the agent that is at rancher-server host with variable -e CATTLE_AGENT_IP=
thanks


Update MapStorageMixin from core:invalid

Located in: core:invalid
Part of: storage
This is part of the upgrade process for Sponge and is likely involving some work and investigation.
Advice and tips include:

Sometimes things are just a simple method name change
Might be a new class or field
Understanding what the original intention of the target code had
Analyzing whether the functionality achieved by the target class/mixin still exists
Understanding the new functionality in the new Minecraft version that requires rewriting for the functionality
The SpongeAPI usage could very well have gone missing out the window if functionality was deemed unnecessary for release

MapStorage no longer exists in 1.16. Instead its purpose is served via DimensionDataStorage, and getting map data is done from here.
Code snippets of changes
@Nullable
public MapItemSavedData getMapData(String var1) {
    return (MapItemSavedData)this.getServer().overworld().getDataStorage().get(() -> {
        return new MapItemSavedData(var1);
    }, var1);
}
public void setMapData(MapItemSavedData var1) {
    this.getServer().overworld().getDataStorage().set(var1);
}

The MapStorage I added in the Map Api was purely a sponge concept, that sorted everything maps into one place.
This purely seems to be checking for async thread access, so if anything these injects should be put onto DimensionDataStorage to check for async access there.


Internal Pressure on Beluga LCD

There is a typical adafruit pressure sensor that you can get data from with the help of I2C buss. This pressure data should be implemented on the LCD screen to display pressure visually.

Website for the pressure sensor in use: https://www.adafruit.com/product/3965

Try using this library: https://docs.circuitpython.org/projects/mprls/en/latest/index.html

Done, Tested and it works :D
Wiki page about it: https://vortex.a2hosted.com/index.php/MPRLS


Need to check shiny when there's no international and no charm

https://github.com/Quandra/SMHatchingRNGTool/blob/master/SMHatchingRNGTool/EggRNGSearch.cs#L143
I think you may need to check PSV and TSV before this line?
In your code, if there's no international hatching and no charm, it's not possible to hatch a shiny egg.
I guess that the "暗号化定数 -- Encryption Constant" is not encryption constant, it's for checking whether the egg is shiny or not in the first time.
I'm not professional, so I'm not sure whether I'm wrong. But the shiny egg should happen even when you have no international and no charm. :)

The PID is generated differently if you are not using Masuda and/or Charm. That is why at least one is required.

I meant, you didn't check shiny if you are "not" using Masuda and/or Charm.  But in this cause, it still have shiny (1/4096)

Yes you can still get shiny Pokemon without either Masuda or Charm. This program is just unable to predict it due to the PID being generated from a different source and not derived from the same seed.


Active Tab Accent Colour or Bold Text on Active Tab

Is your feature request related to a problem? Please describe.
[FEAT Request]
This is based on the App Theme using "Dark" Mode or even "Windows Default" when system is set to Dark mode.
It is much more difficult to see which tab is currently Active when compared to Light Mode.
Describe the solution you'd like
When using Dark Mode, either the Active tab has a noticeable lighter accent/shade compared to the inactive tab.
Describe alternatives you've considered
Give the active tab text a different colour e.g. standard white for inactive and Light Blue for active (or a settings choice).
Additional context
See attached example of how light mode tabs are so much easier to see compared to dark.

Thanks for this report, this is something we're looking to improve. Merging with #3384


Headship Stats CSS

On macOS Safari the head ship stats don't render properly. I understand this is not a data issue. You can see in the screenshot that the data is present but not rendered legibly. The problem is related to light/dark mode - it does work in dark mode.

Good spot. Some quirk to do with mixing numbers and percentages for the background gradient colours. I've pushed a fix.

It works for me now. Suggest to close this.


Promise doesn't provide variants of catch and either where the rejection function returns another Promise

According to the spec, Promise.catch(f) is sugar for Promise.then(id, f), which allows f : exn -> U2<'T, Promise<'T>>, whereas the Fable.PowerPack's current implementations only allow f : exn -> 'T.
To avoid breaking changes, I propose not to change the signatures of catch and either, but add two new functions, catchBind and eitherBind respectively:
[<Emit("$1.catch($0)")>]
let catchBind (a: Exception->Promise<'T>) (pr: JS.Promise<'T>): JS.Promise<'T> = jsNative

[<Emit("$2.then($0,$1)")>]
let eitherBind (success: 'T->'R) (fail: Exception->Promise<'R>) (pr: JS.Promise<'T>): JS.Promise<'R> = jsNative

(I'm not completely sure about the names - not a native English speaker myself - so if anyone has better ideas...)

I think that's a good idea! Though maybe the signature of eitherBind should be the following? (So success also returns a Promise.)
let eitherBind (success: 'T->Promise<'R>) (fail: Exception->Promise<'R>) (pr: JS.Promise<'T>): JS.Promise<'R> = jsNative

I know this reduces flexibility, maybe we could do something like this, although it may not be very pretty:
let eitherBind (success: 'T->U2<'R,Promise<'R>>) (fail: Exception->Promise<'R>) (pr: JS.Promise<'T>): JS.Promise<'R> = jsNative

We could use the !^ operator for combination (for example, return a non-promise in success and a promise in fail):
myPromise
|> Promise.eitherBind (fun x -> !^(string x)) (fun ex -> !^(Promise.lift ex.Message))

Hum, I am asking myself if it's a good idea to add "custom" methods in the libs instead of fixing it. If I understand correctly, we are less permissive than the official API.
The compiler should, generate an error when the user update it's deps and so help him identified and fix the errors.

@MangelMaxime In principle you're right, but we must be careful with this, because it's always annoying to find that your code is not compiling anymore after updating a dependency and sometimes it's difficult to figure out how to fix the error right away.
In any case, we need to decide if we do need to fix this and how. It's true the JS API (.then) is more flexible than the F# one, but I think it's OK to have two methods (map and bind) because they're standard in most functional languages. For catch, I'd say it's also OK to have both catch and catchBind for the same reasons.
The trickiest part is either as it allows four combinations (non-promise/non-promise, promise/promise, non-promise/promise, promise/non-promise). If we decided to go for the ('T->U2<'R,Promise<'R>>) -> (Exception->U2<'R,Promise<'R>>) -> JS.Promise<'T> -> JS.Promise<'T> signature, it may make sense to directly modify either, yes (though it's a breaking change).

Ok, I understand :)
Seems fine to me. Just either type signature which looks complex :)

I was not aware of the existence of the "erased cast" operator, and my chief concern was with the awkwardness of inserting U2.Case1 everywhere, but now I that I know that the operator exists, I think that we should fix the signature of either instead of adding eitherBind. The justification is that either probably represents am "advanced" usage, and therefore it is both more rare in existing code and practiced by more experienced developers, who wouldn't be confused by the changed signature as much.
By the reverse reasoning, and agreeing with @alfonsogarciacaro, I agree with adding catchBind.

It seems we reached an agreement ;) @fsoikin Would you mind sending a PR to modify the signature of Promise.either? Ideally adding an explanation in the help comment on how to use the !^ operator. Cheers!


Expired schedule job is re-triggerred after restarting support-cron-scheduler

🐞 Bug Report
Affected Services [REQUIRED]

 The issue is located in: support-cron-scheduler
Is this a regression?

 No
Description and Minimal Reproduction [REQUIRED]

Create a scheduler job
Wait the job started and stopped
Restart support-cron-scheduler

🔥 Exception or Error
The expired schedule job is re-triggered

....
level=DEBUG ts=2024-09-06T07:05:40.016031163Z app=support-cron-scheduler source=manager.go:261 msg="A new schedule action record with type: REST and status: SUCCEEDED was added for job: test_job_1, record ID: ab088a56-7573-4dcb-a9a8-6b747afb3656, Correlation-ID: 7c78aa45-43b1-4d78-b499-d9ca9c569261"
level=DEBUG ts=2024-09-06T07:05:50.010199607Z app=support-cron-scheduler source=rest.go:40 msg="Successfully send the rest request with address http://<IP_ADDRESS>:59880/api/v3/ping"
level=DEBUG ts=2024-09-06T07:05:50.010430808Z app=support-cron-scheduler source=gocron.go:105 msg="REST action was executed successfully, response: {\"apiVersion\":\"v3\",\"timestamp\":\"Fri Sep  6 15:05:50 CST 2024\",\"serviceName\":\"core-data\"}"
level=DEBUG ts=2024-09-06T07:05:50.016112465Z app=support-cron-scheduler source=manager.go:261 msg="A new schedule action record with type: REST and status: SUCCEEDED was added for job: test_job_1, record ID: 9d6c9de5-f616-49cf-b7cf-6523901941f2, Correlation-ID: 7c78aa45-43b1-4d78-b499-d9ca9c569261"
level=DEBUG ts=2024-09-06T07:06:00.002032216Z app=support-cron-scheduler source=manager.go:128 msg="The scheduled job test_job_1 was stopped in the scheduler manager. Correlation-ID: d9a2c4ff-ae22-420f-a83b-887952905381"
level=DEBUG ts=2024-09-06T07:06:06.357628579Z app=support-cron-scheduler source=reporter.go:195 msg="Publish 0 metrics to the 'edgex/telemetry/support-cron-scheduler' base topic"
level=DEBUG ts=2024-09-06T07:06:06.35786978Z app=support-cron-scheduler source=manager.go:123 msg="Reported metrics..."
level=DEBUG ts=2024-09-06T07:06:36.357201871Z app=support-cron-scheduler source=reporter.go:195 msg="Publish 0 metrics to the 'edgex/telemetry/support-cron-scheduler' base topic"
level=DEBUG ts=2024-09-06T07:06:36.357357616Z app=support-cron-scheduler source=manager.go:123 msg="Reported metrics..."
level=INFO ts=2024-09-06T07:06:51.430338396Z app=support-cron-scheduler source=config.go:853 msg="Watching for 'Writable' configuration changes has stopped"
level=INFO ts=2024-09-06T07:06:51.430592639Z app=support-cron-scheduler source=httpserver.go:262 msg="Web server stopped"
...
## restarting logs
...
level=INFO ts=2024-09-06T07:06:51.720858287Z app=support-cron-scheduler source=manager.go:60 msg="New scheduled job test_job_1 was added into the scheduler manager. ScheduleJob ID: feccf895-2718-4613-ac2a-a0ecb0f71065, Correlation-ID: 6110eb2f-829f-416c-8529-c2db3b3eed16"
level=DEBUG ts=2024-09-06T07:06:51.720881369Z app=support-cron-scheduler source=schedulejob.go:227 msg="The startTimestamp is expired for the scheduled job: test_job_1, which will be started immediately. Correlation-ID: 6110eb2f-829f-416c-8529-c2db3b3eed16"
level=DEBUG ts=2024-09-06T07:06:51.720890577Z app=support-cron-scheduler source=schedulejob.go:243 msg="The endTimestamp is expired for the scheduled job: test_job_1, which will be stopped immediately. Correlation-ID: 6110eb2f-829f-416c-8529-c2db3b3eed16"
level=DEBUG ts=2024-09-06T07:06:51.721025657Z app=support-cron-scheduler source=manager.go:128 msg="The scheduled job test_job_1 was stopped in the scheduler manager. Correlation-ID: 6110eb2f-829f-416c-8529-c2db3b3eed16"
level=DEBUG ts=2024-09-06T07:06:51.721037782Z app=support-cron-scheduler source=manager.go:113 msg="The scheduled job test_job_1 was started. Correlation-ID: 6110eb2f-829f-416c-8529-c2db3b3eed16"
level=DEBUG ts=2024-09-06T07:06:51.725540698Z app=support-cron-scheduler source=scheduleactionrecord.go:162 msg="Missed schedule action records with action id: b15ac040-30bb-4028-875d-57f255697755 of job: test_job_1 have been created successfully. Correlation-ID: 6110eb2f-829f-416c-8529-c2db3b3eed16"
level=DEBUG ts=2024-09-06T07:06:51.725570697Z app=support-cron-scheduler source=schedulejob.go:205 msg="Successfully loaded the existing scheduled job: test_job_1. Correlation-ID: 6110eb2f-829f-416c-8529-c2db3b3eed16"
level=INFO ts=2024-09-06T07:06:51.72558378Z app=support-cron-scheduler source=httpserver.go:167 msg="Web server starting (edgex-support-cron-scheduler:59863)"
level=INFO ts=2024-09-06T07:06:51.725589322Z app=support-cron-scheduler source=message.go:50 msg="Service dependencies resolved..."
level=INFO ts=2024-09-06T07:06:51.725592072Z app=support-cron-scheduler source=message.go:51 msg="Starting support-cron-scheduler 3.2.0-dev.61 "
level=INFO ts=2024-09-06T07:06:51.725593863Z app=support-cron-scheduler source=message.go:55 msg="This is the Support Cron Scheduler Microservice"
level=INFO ts=2024-09-06T07:06:51.725596572Z app=support-cron-scheduler source=message.go:58 msg="Service started in: 51.797728ms"
level=INFO ts=2024-09-06T07:06:51.725604238Z app=support-cron-scheduler source=bootstrap.go:254 msg="SecuritySecretsRequested metric registered and will be reported (if enabled)"
level=INFO ts=2024-09-06T07:06:51.725607446Z app=support-cron-scheduler source=bootstrap.go:254 msg="SecuritySecretsStored metric registered and will be reported (if enabled)"
level=INFO ts=2024-09-06T07:06:51.725617196Z app=support-cron-scheduler source=httpserver.go:239 msg="listening on underlay network. ListenMode '' at edgex-support-cron-scheduler:59863"
level=DEBUG ts=2024-09-06T07:07:01.727049355Z app=support-cron-scheduler source=rest.go:40 msg="Successfully send the rest request with address http://<IP_ADDRESS>:59880/api/v3/ping"
level=DEBUG ts=2024-09-06T07:07:01.727157477Z app=support-cron-scheduler source=gocron.go:105 msg="REST action was executed successfully, response: {\"apiVersion\":\"v3\",\"timestamp\":\"Fri Sep  6 15:07:01 CST 2024\",\"serviceName\":\"core-data\"}"
level=DEBUG ts=2024-09-06T07:07:01.732117759Z app=support-cron-scheduler source=manager.go:261 msg="A new schedule action record with type: REST and status: SUCCEEDED was added for job: test_job_1, record ID: c967fc18-8dce-445b-9c66-6b55c0ec4575, Correlation-ID: 83891720-aaff-4eda-be42-f773f4f3b0eb"
level=DEBUG ts=2024-09-06T07:07:11.728406614Z app=support-cron-scheduler source=rest.go:40 msg="Successfully send the rest request with address http://<IP_ADDRESS>:59880/api/v3/ping"
level=DEBUG ts=2024-09-06T07:07:11.72892335Z app=support-cron-scheduler source=gocron.go:105 msg="REST action was executed successfully, response: {\"apiVersion\":\"v3\",\"timestamp\":\"Fri Sep  6 15:07:11 CST 2024\",\"serviceName\":\"core-data\"}"

🌍  Your Environment
Deployment Environment: Ubuntu 2204/arm64
EdgeX Version [REQUIRED]: Main
Anything else relevant?

Verified this issue has been fixed but I caught another bug that the missed records still been generated.
Will fix it in the PR for this issue.


Breadcrumbs links are broken

In the last release (3.2.2), the template on the breadcrumbs was changed to check for the attribute has_view_permission (link).
However, the template tag still populates the attribute has_change_permission.
As a result, breadcrumbs are rendered without links:

A quickfix for users is to downgrade the package to version 3.2.1.

Thanks for catching this. I had and off feeling about the last PR, but it was just before vacation and I wanted to get it out the door, before I left. New release is being published as I type.


Operator: armada helm chart 'executor-cluster-monitoring' not in Operator

This is a service monitor outside of the executor chart -- maybe we can roll it up with executor CR.
┆Issue is synchronized with this Jira Task by Unito

Per James Murkin we do not need to implement


Failed assert when using precision and orderedComparison

The issue found regards the use of precision and orderedComparison = false
When orderedComparison is false, the library automatically orders the dataframe by taking the columns in alphabetical order. It may happen (like in the example below) that the first column in the order is the one that uses the "precision". Therefore, it can happen that by ordering the columns, the result is not the expected one.
You can see an example of what I'm talking about here:
it should "test" in {
    val ds1 = Seq(
      ("1", "10/01/2019", 26.762499999999996),
      ("1", "11/01/2019", 26.762499999999996)
    ).toDF("col_B", "col_C", "col_A")

    val ds2 = Seq(
      ("1", "10/01/2019", 26.762499999999946),
      ("1", "11/01/2019", 26.76249999999991)
    ).toDF("col_B", "col_C", "col_A")

    assertApproximateDataFrameEquality(ds1, ds2, precision = 7, orderedComparison = false)
  }

As you can see, the test should pass, because only the precision decimals > 7 are different, the rest of columns are the same. However, since "col_A" will go first in the "orderedComparison = false", the test will fail.
Some possible fixes could be:

Apply precision before ordering columns
Avoid using in the order columns that will be affected by precision (double columns)

A workaround for this issue is to order yourself the dataframes and set "orderedComparison = true"

@adrixgc - Here's a fix: https://github.com/MrPowers/spark-fast-tests/pull/92
Looks like we can avoid the column ordering.  Let me know if this fix looks alright to you!
Thanks for reporting this edge case!

@MrPowers I checked the PR and that solves the current problem. Could you run this test and check if it passes too?
"can work with precision and unordered comparison 2" in {
      import spark.implicits._
      val ds1 = Seq(
        ("1", "10/01/2019", 26.762499999999996, "A"),
        ("1", "10/01/2019", 26.762499999999996, "B")
      ).toDF("col_B", "col_C", "col_A", "col_D")

      val ds2 = Seq(
        ("1", "10/01/2019", 26.762499999999946, "A"),
        ("1", "10/01/2019", 26.76249999999991, "B")
      ).toDF("col_B", "col_C", "col_A", "col_D")

      assertApproximateDataFrameEquality(ds1, ds2, precision = 0.0000001, orderedComparison = false)
    }

@adrixgc - you're right, thanks for the additional test case to illustrate the issue.
Pushed up another commit that only sorts the precise columns (not the float, decimal, or double) columns which should fix the issue.
Can you please take a look and let me know if this fix looks alright to you?  Thanks!

Looks good to me! PR approved. Thanks for the quick response!

Closed as fixed