Unable to launch app on android device

Steps to Reproduce
From both IDEA as CLI (Flutter/adb devices) the device is recognized correctly.
When I run it it seems to lose connection.
adb not responding is shown by the intellij-flutter output, please find below the flutter verbose output.
This may be more of a graphical issue with intellij-flutter, but for completeness:
When the adb server is manually killed No devices found with name or id matching '6127002886' is shown on run some of the times,
Error retrieving device properties for ro.product.cpu.abi:
error: closed

Launching lib/main.dart on Pixel C in debug mode...
Initializing gradle...
Resolving dependencies...
Unexpected failure from adb: Invalid argument(s): The source must not be null
Error launching application on Pixel C.

other times.
Related issues
https://github.com/flutter/flutter-intellij/issues/1097
https://github.com/flutter/flutter/issues/2167
Logs
                   BUILD SUCCESSFUL

                   Total time: 0.668 secs
[   +6 ms] /home/adamv/sdk-tools-linux-3859397/build-tools/27.0.3/aapt dump badging build/app/outputs/apk/app.apk
[   +7 ms] Exit code 0 from: /home/adamv/sdk-tools-linux-3859397/build-tools/27.0.3/aapt dump badging build/app/outputs/apk/app.apk
[        ] package: name='com.yourcompany.gapp' versionCode='1' versionName='1.0' platformBuildVersionName='7.1.1'
           sdkVersion:'16'
           targetSdkVersion:'25'
           uses-permission: name='android.permission.INTERNET'
           application-label:'g_app'
           application-icon-160:'res/mipmap-mdpi-v4/ic_launcher.png'
           application-icon-240:'res/mipmap-hdpi-v4/ic_launcher.png'
           application-icon-320:'res/mipmap-xhdpi-v4/ic_launcher.png'
           application-icon-480:'res/mipmap-xxhdpi-v4/ic_launcher.png'
           application-icon-640:'res/mipmap-xxxhdpi-v4/ic_launcher.png'
           application: label='g_app' icon='res/mipmap-mdpi-v4/ic_launcher.png'
           application-debuggable
           launchable-activity: name='com.yourcompany.gapp.MainActivity'  label='' icon=''
           feature-group: label=''
             uses-feature: name='android.hardware.faketouch'
             uses-implied-feature: name='android.hardware.faketouch' reason='default feature for all apps'
           main
           supports-screens: 'small' 'normal' 'large' 'xlarge'
           supports-any-density: 'true'
           locales: '--_--'
           densities: '160' '240' '320' '480' '640'
           native-code: 'arm64-v8a' 'x86' 'x86_64'
[   +4 ms] /home/adamv/sdk-tools-linux-3859397/platform-tools/adb -s<PHONE_NUMBER> logcat -v time -t 1
[  +73 ms] Exit code 0 from: /home/adamv/sdk-tools-linux-3859397/platform-tools/adb -s<PHONE_NUMBER> logcat -v time -t 1
[        ] --------- beginning of main
           02-09 21:24:00.005 W/android.os.Debug(  373): failed to get memory consumption info: -1
[   +2 ms] /home/adamv/sdk-tools-linux-3859397/platform-tools/adb -s<PHONE_NUMBER> logcat -v time
[ +242 ms] DependencyChecker: nothing is modified after 2018-02-09 20:55:52.772.
[   +2 ms] /home/adamv/sdk-tools-linux-3859397/platform-tools/adb version
[  +10 ms] Android Debug Bridge version 1.0.39
           Version 0.0.1-4500957
           Installed as /home/adamv/sdk-tools-linux-3859397/platform-tools/adb
[   +1 ms] /home/adamv/sdk-tools-linux-3859397/platform-tools/adb start-server
[   +6 ms] Building APK
[   +2 ms] Running 'gradlew assembleDebug'...
[   +1 ms] [android/] /home/adamv/IdeaProjects/G-mobile/android/gradlew -Ptarget=/home/adamv/IdeaProjects/G-mobile/lib/main.dart -Ptarget-platform=android-arm64 assembleDebug
[ +571 ms] NDK is missing a "platforms" directory.
[        ] If you are using NDK, verify the ndk.dir is set to a valid NDK directory.  It is currently set to /home/adamv/sdk-tools-linux-3859397/ndk-bundle.
[        ] If you are not using NDK, unset the NDK variable from ANDROID_NDK_HOME or local.properties to remove this warning.
[  +24 ms] NDK is missing a "platforms" directory.
[        ] If you are using NDK, verify the ndk.dir is set to a valid NDK directory.  It is currently set to /home/adamv/sdk-tools-linux-3859397/ndk-bundle.
[        ] If you are not using NDK, unset the NDK variable from ANDROID_NDK_HOME or local.properties to remove this warning.
[  +14 ms] Incremental java compilation is an incubating feature.
[ +106 ms] :app:flutterBuildX86Jar UP-TO-DATE
[        ] :app:preBuild UP-TO-DATE
...
[        ] :path_provider:assembleDebug UP-TO-DATE
[        ] BUILD SUCCESSFUL
[        ] Total time: 0.912 secs
[ +413 ms] calculateSha: /home/adamv/IdeaProjects/G-mobile/build/app/outputs/apk/app.apk
[ +330 ms] Built build/app/outputs/apk/app-debug.apk (23.5MB).
[        ] /home/adamv/sdk-tools-linux-3859397/build-tools/27.0.3/aapt dump badging build/app/outputs/apk/app.apk
[   +4 ms] Exit code 0 from: /home/adamv/sdk-tools-linux-3859397/build-tools/27.0.3/aapt dump badging build/app/outputs/apk/app.apk
[        ] package: name='com.yourcompany.gapp' versionCode='1' versionName='1.0' platformBuildVersionName='7.1.1'
           sdkVersion:'16'
           targetSdkVersion:'25'
           uses-permission: name='android.permission.INTERNET'
           application-label:'g_app'
           application-icon-160:'res/mipmap-mdpi-v4/ic_launcher.png'
           application-icon-240:'res/mipmap-hdpi-v4/ic_launcher.png'
           application-icon-320:'res/mipmap-xhdpi-v4/ic_launcher.png'
           application-icon-480:'res/mipmap-xxhdpi-v4/ic_launcher.png'
           application-icon-640:'res/mipmap-xxxhdpi-v4/ic_launcher.png'
           application: label='g_app' icon='res/mipmap-mdpi-v4/ic_launcher.png'
           application-debuggable
           launchable-activity: name='com.yourcompany.gapp.MainActivity'  label='' icon=''
           feature-group: label=''
             uses-feature: name='android.hardware.faketouch'
             uses-implied-feature: name='android.hardware.faketouch' reason='default feature for all apps'
           main
           supports-screens: 'small' 'normal' 'large' 'xlarge'
           supports-any-density: 'true'
           locales: '--_--'
           densities: '160' '240' '320' '480' '640'
           native-code: 'arm64-v8a' 'x86' 'x86_64'
[        ] Stopping app 'app.apk' on Pixel C.
[        ] /home/adamv/sdk-tools-linux-3859397/platform-tools/adb -s<PHONE_NUMBER> shell am force-stop com.yourcompany.gapp
[   +4 ms] error: device '6127002886' not found
[   +1 ms] /home/adamv/sdk-tools-linux-3859397/platform-tools/adb -s<PHONE_NUMBER> shell pm list packages com.yourcompany.gapp
[   +5 ms] error: device '6127002886' not found
[   +1 ms] Exit code 1 from: /home/adamv/sdk-tools-linux-3859397/platform-tools/adb -s<PHONE_NUMBER> shell pm list packages com.yourcompany.gapp:
           error: device '6127002886' not found
[        ] Installing APK.
[   +1 ms] /home/adamv/sdk-tools-linux-3859397/platform-tools/adb version
[   +3 ms] Android Debug Bridge version 1.0.39
           Version 0.0.1-4500957
           Installed as /home/adamv/sdk-tools-linux-3859397/platform-tools/adb
[        ] /home/adamv/sdk-tools-linux-3859397/platform-tools/adb start-server
[   +5 ms] Installing build/app/outputs/apk/app.apk...
[        ] /home/adamv/sdk-tools-linux-3859397/platform-tools/adb -s<PHONE_NUMBER> install -r build/app/outputs/apk/app.apk
[+313341 ms] adb: error: failed to get feature set: device '6127002886' not found

                     error: device '6127002886' not found
                     - waiting for device -
[   +2 ms] Error: ADB exited with exit code 255
[        ] adb: error: failed to get feature set: device '6127002886' not found

           error: device '6127002886' not found
           - waiting for device -
[        ] Warning: Failed to install APK.
[        ] Error launching application on Pixel C.
[  +24 ms] "flutter run" took 317,301ms.

#0      throwToolExit (package:flutter_tools/src/base/common.dart:28)
#1      RunCommand.runCommand (package:flutter_tools/src/commands/run.dart:348)
<asynchronous suspension>
#2      FlutterCommand.verifyThenRunCommand (package:flutter_tools/src/runner/flutter_command.dart:282)
<asynchronous suspension>
#3      FlutterCommand.run (package:flutter_tools/src/runner/flutter_command.dart:222)
<asynchronous suspension>
#4      CommandRunner.runCommand (package:args/command_runner.dart:194)
<asynchronous suspension>
#5      FlutterCommandRunner.runCommand (package:flutter_tools/src/runner/flutter_command_runner.dart:284)
<asynchronous suspension>
#6      CommandRunner.run.<anonymous closure> (package:args/command_runner.dart:109)
#7      new Future.sync (dart:async/future.dart:222)
#8      CommandRunner.run (package:args/command_runner.dart:109)
#9      FlutterCommandRunner.run (package:flutter_tools/src/runner/flutter_command_runner.dart:166)
#10     run.<anonymous closure> (package:flutter_tools/runner.dart:89)
<asynchronous suspension>
#11     AppContext._run (package:flutter_tools/src/base/context.dart:76)
<asynchronous suspension>
#12     AppContext.runInZone.<anonymous closure> (package:flutter_tools/src/base/context.dart:66)
#13     _rootRun (dart:async/zone.dart:1126)
#14     _CustomZone.run (dart:async/zone.dart:1023)
#15     runZoned (dart:async/zone.dart:1501)
#16     AppContext.runInZone (package:flutter_tools/src/base/context.dart:65)
#17     run (package:flutter_tools/runner.dart:61)
<asynchronous suspension>
#18     main (package:flutter_tools/executable.dart:48)
<asynchronous suspension>
#19     main (file:///home/adamv/flutter/packages/flutter_tools/bin/flutter_tools.dart:16)
#20     _startIsolate.<anonymous closure> (dart:isolate-patch/dart:isolate/isolate_patch.dart:276)
#21     _RawReceivePortImpl._handleMessage (dart:isolate-patch/dart:isolate/isolate_patch.dart:164)

[ +216 ms] ensureAnalyticsSent: 211ms
[   +2 ms] exiting with code 2

Flutter Analyze returns clean
Flutter Doctor
[✓] Flutter (on Linux, locale en_US.UTF-8, channel dev)
    • Flutter version 0.0.25-pre.5 at /home/adamv/flutter
    • Framework revision 4ae1b5f415 (2 days ago), 2018-02-07 15:18:04 -0800
    • Engine revision 9bc2efdf47
    • Tools Dart version 2.0.0-dev.19.0
    • Engine Dart version 2.0.0-edge.ea91bc9888184d5a2fc309c36656fdd325ef503c

[✓] Android toolchain - develop for Android devices (Android SDK 27.0.3)
    • Android SDK at /home/adamv/sdk-tools-linux-3859397
    • Android NDK location not configured (optional; useful for native profiling support)
    • Platform android-27, build-tools 27.0.3
    • ANDROID_HOME = /home/adamv/sdk-tools-linux-3859397
    • Java binary at: /usr/bin/java
    • Java version OpenJDK Runtime Environment (build 1.8.0_144-b01)

[✗] Android Studio (not installed)
    • Android Studio not found; download from https://developer.android.com/studio/index.html
      (or visit https://flutter.io/setup/#android-setup for detailed instructions).

[✓] IntelliJ IDEA Ultimate Edition (version 2017.3)
    • Flutter plugin version 21.2.3
    • Dart plugin version 173.4127.31

[✓] Connected devices
    • Pixel C •<PHONE_NUMBER> • android-arm64 • Android 8.1.0 (API 27)

Possibly related #14621

This crash persist through recent updates, "losing connection" to the device after building the flutter app.

I had the same issue. In my case the problem was caused from a syntax error in pubspec.yaml

Any update?

The same issue for me. Any solution?

My device is connectedm but can't run the app
Launching lib\main.dart on MTN S630 in debug mode...

Error running Gradle:
Exit code 1 from: C:\Users\Lhex\AndroidStudioProjects\flutter_gdg\android\gradlew.bat app:properties:

FAILURE: Build failed with an exception.

What went wrong:
A problem occurred configuring root project 'android'.

Could not resolve all files for configuration ':classpath'.
Could not resolve com.android.tools:annotations:26.0.1.
Required by:
project : > com.android.tools.build:gradle:3.0.1 > com.android.tools.build:gradle-core:3.0.1 > com.android.databinding:compilerCommon:3.0.1
Could not resolve com.android.tools:annotations:26.0.1.
Could not get resource 'https://dl.google.com/dl/android/maven2/com/android/tools/annotations/26.0.1/annotations-26.0.1.pom'.
Could not GET 'https://dl.google.com/dl/android/maven2/com/android/tools/annotations/26.0.1/annotations-26.0.1.pom'.
dl.google.com
Could not resolve com.android.tools:annotations:26.0.1.
Could not get resource 'https://jcenter.bintray.com/com/android/tools/annotations/26.0.1/annotations-26.0.1.pom'.
Could not GET 'https://jcenter.bintray.com/com/android/tools/annotations/26.0.1/annotations-26.0.1.pom'.
jcenter.bintray.com
Could not resolve com.android.tools:annotations:26.0.1.
Required by:
project : > com.android.tools.build:gradle:3.0.1 > com.android.tools.build:gradle-core:3.0.1 > com.android.tools.build:builder:3.0.1 > com.android.tools.build:builder-model:3.0.1
project : > com.android.tools.build:gradle:3.0.1 > com.android.tools.build:gradle-core:3.0.1 > com.android.tools.build:builder:3.0.1 > com.android.tools:common:26.0.1
project : > com.android.tools.build:gradle:3.0.1 > com.android.tools.build:gradle-core:3.0.1 > com.android.tools.build:builder:3.0.1 > com.android.tools.analytics-library:shared:26.0.1
project : > com.android.tools.build:gradle:3.0.1 > com.android.tools.build:gradle-core:3.0.1 > com.android.tools.build:builder:3.0.1 > com.android.tools.analytics-library:tracker:26.0.1
project : > com.android.tools.build:gradle:3.0.1 > com.android.tools.build:gradle-core:3.0.1 > com.android.tools.build:builder:3.0.1 > com.android.tools:sdklib:26.0.1 > com.android.tools.layoutlib:layoutlib-api:26.0.1
Could not resolve com.android.tools:annotations:26.0.1.
Could not get resource 'https://dl.google.com/dl/android/maven2/com/android/tools/annotations/26.0.1/annotations-26.0.1.pom'.
Could not GET 'https://dl.google.com/dl/android/maven2/com/android/tools/annotations/26.0.1/annotations-26.0.1.pom'.
dl.google.com
Could not resolve com.android.tools:annotations:26.0.1.
Could not get resource 'https://jcenter.bintray.com/com/android/tools/annotations/26.0.1/annotations-26.0.1.pom'.
Could not GET 'https://jcenter.bintray.com/com/android/tools/annotations/26.0.1/annotations-26.0.1.pom'.
jcenter.bintray.com
Could not resolve commons-codec:commons-codec:1.6.
Required by:
project : > com.android.tools.build:gradle:3.0.1 > com.android.tools.build:gradle-core:3.0.1 > com.android.tools.build:builder:3.0.1 > com.android.tools:sdklib:26.0.1 > org.apache.httpcomponents:httpclient:4.2.6
Could not resolve commons-codec:commons-codec:1.6.
Could not get resource 'https://jcenter.bintray.com/commons-codec/commons-codec/1.6/commons-codec-1.6.pom'.
Could not HEAD 'https://jcenter.bintray.com/commons-codec/commons-codec/1.6/commons-codec-1.6.pom'.
jcenter.bintray.com
Could not resolve commons-codec:commons-codec:1.6.
Could not get resource 'https://dl.google.com/dl/android/maven2/commons-codec/commons-codec/1.6/commons-codec-1.6.pom'.
Could not HEAD 'https://dl.google.com/dl/android/maven2/commons-codec/commons-codec/1.6/commons-codec-1.6.pom'.
dl.google.com
Could not resolve com.android.tools.external.com-intellij:intellij-core:26.0.1.
Required by:
project : > com.android.tools.build:gradle:3.0.1 > com.android.tools.build:gradle-core:3.0.1 > com.android.tools.lint:lint:26.0.1 > com.android.tools.lint:lint-checks:26.0.1 > com.android.tools.lint:lint-api:26.0.1
Could not resolve com.android.tools.external.com-intellij:intellij-core:26.0.1.
Could not get resource 'https://dl.google.com/dl/android/maven2/com/android/tools/external/com-intellij/intellij-core/26.0.1/intellij-core-26.0.1.pom'.
Could not GET 'https://dl.google.com/dl/android/maven2/com/android/tools/external/com-intellij/intellij-core/26.0.1/intellij-core-26.0.1.pom'.
dl.google.com
Could not resolve com.android.tools.external.com-intellij:intellij-core:26.0.1.
Could not get resource 'https://jcenter.bintray.com/com/android/tools/external/com-intellij/intellij-core/26.0.1/intellij-core-26.0.1.pom'.
Could not GET 'https://jcenter.bintray.com/com/android/tools/external/com-intellij/intellij-core/26.0.1/intellij-core-26.0.1.pom'.
jcenter.bintray.com
Could not resolve com.android.tools.external.lombok:lombok-ast:0.2.3.
Required by:
project : > com.android.tools.build:gradle:3.0.1 > com.android.tools.build:gradle-core:3.0.1 > com.android.tools.lint:lint:26.0.1 > com.android.tools.lint:lint-checks:26.0.1 > com.android.tools.lint:lint-api:26.0.1
Could not resolve com.android.tools.external.lombok:lombok-ast:0.2.3.
Could not get resource 'https://dl.google.com/dl/android/maven2/com/android/tools/external/lombok/lombok-ast/0.2.3/lombok-ast-0.2.3.pom'.
Could not GET 'https://dl.google.com/dl/android/maven2/com/android/tools/external/lombok/lombok-ast/0.2.3/lombok-ast-0.2.3.pom'.
dl.google.com
Could not resolve com.android.tools.external.lombok:lombok-ast:0.2.3.
Could not get resource 'https://jcenter.bintray.com/com/android/tools/external/lombok/lombok-ast/0.2.3/lombok-ast-0.2.3.pom'.
Could not GET 'https://jcenter.bintray.com/com/android/tools/external/lombok/lombok-ast/0.2.3/lombok-ast-0.2.3.pom'.
jcenter.bintray.com
Could not resolve org.jetbrains.kotlin:kotlin-reflect:1.1.3-2.
Required by:
project : > com.android.tools.build:gradle:3.0.1 > com.android.tools.build:gradle-core:3.0.1 > com.android.tools.lint:lint:26.0.1 > com.android.tools.lint:lint-checks:26.0.1 > com.android.tools.lint:lint-api:26.0.1
Could not resolve org.jetbrains.kotlin:kotlin-reflect:1.1.3-2.
Could not get resource 'https://dl.google.com/dl/android/maven2/org/jetbrains/kotlin/kotlin-reflect/1.1.3-2/kotlin-reflect-1.1.3-2.pom'.
Could not GET 'https://dl.google.com/dl/android/maven2/org/jetbrains/kotlin/kotlin-reflect/1.1.3-2/kotlin-reflect-1.1.3-2.pom'.
dl.google.com
Could not resolve org.jetbrains.kotlin:kotlin-reflect:1.1.3-2.
Could not get resource 'https://jcenter.bintray.com/org/jetbrains/kotlin/kotlin-reflect/1.1.3-2/kotlin-reflect-1.1.3-2.pom'.
Could not GET 'https://jcenter.bintray.com/org/jetbrains/kotlin/kotlin-reflect/1.1.3-2/kotlin-reflect-1.1.3-2.pom'.
jcenter.bintray.com

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

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

BUILD FAILED in 6s
Please review your Gradle project setup in the android/ folder.
Exited (sigterm)

@Lhecks that doesn't really look related to this issue.
It looks somewhat related to #23404 but it's still a bit different. I'd still suggest you check the discussion there and if this doesn't help create a new issue.

I assume this issue is stale.

@zoechi no this is not stale. My issue has not been resolved. I responded to your query and have had no response.


Update Release_Notes.md

Added a known issue per Iuliia B: https://dev.azure.com/Sitecore-PD/Products/_workitems/edit/615969

This seems to be a PR to your forked repository instead of the sitecore/developer-portal repository


provide links directly to the publication from the evidence item summary

Provide both links to sources.summary & either pubmed detail page, or directly to publication

Done.


Discussion: Database model refining

As a developer, I want to have a database model as simple as possible. This can involve the deletion of tables/columns in the database if doing so still allows us to represent the things we want to represent.
When we have less tables/columns we get 3 benefits:

A schema that is easier to understand
Less code in the project
Less execution time (a table less is a spark job less we need to execute)

Things that I think we could remove:
Diagnosis table
At the beginning of the project it seemed to be a good idea to have a table to keep the diagnosis (patient's initial diagnosis and patient sample's diagnosis). As a general rule it's recommended to extract columns, especially if they are text, into separate tables if several records in other tables can reference a single value: for example, hundreds of patients could have the same initial diagnosis so we store it once and then other tables just need to reference that single record. In this way we avoid redundancy and some potential issues.
However in our specific case, those diagnosis' values are just intermediate values in our process: they by themselves don't represent a "controlled vocabulary", they are the input for the harmonisation process and the harmonised diagnosis are the ones we want to present to the user.
Proposal
To delete the Diagnosis table and store the values as text in both patient and patient_sample tables.
Patient_snapshot

We currently have 2 tables to represent one record in the patient_sample sheet in metadata: patient_sample and patient_snapshot. That was done that way to reflect as close as possible the neo4j schema. I'd like to reevaluate this, I don't think we need the  patient_snapshot table. We could keep all the information into the patient_sample.
Proposal

To delete the patient_snapshot table move all its attributes to the patient_sample table.

To check if all fields are needed. The columns of this new table would be:

id
diagnosis
external_patient_sample_id
grade
grading_system
stage
staging_system
primary_site_id
collection_site_id
prior_treatment
tumour_type_id
model_id
patient_id
age_in_years_at_collection
collection_event
collection_date
months_since_collection_1
treatment_naive_at_collection
virology_status

Acceptance Criteria

[ ] Discussion with @zperova  about the proposed changes, either in comments in this ticket or a meeting if needed.

@zperova could you please have a look at this? We can have a meeting if needed. Thanks

moving to the next sprint

will discuss Sprint 4 May

schedule another meeting

Meeting on 20-sep-2022, changes discussed and approved. @zperova


Add https://worldcam.eu/ to cameras section

Add https://worldcam.eu/ to cameras section

Completed, thanks @patHyatt !


nnUNet_train 3d_fullres nnUNetTrainerV2 100 all

Hi, is this line still proper with the new version nnUNet V2? I have the error that "all" is illegal. THX!

In nnUNet V2, the commands for preprocessing, training, inferencing are different.
nnUNetv2_plan_and_preprocess -d DATASET_ID --verify_dataset_integrity
nnUNetv2_train DATASET_ID 3d_fullres all
nnUNetv2_predict -i INPUT -o OUTPUT -d ID -c 3d_fullres -f all


Library does not support programmatic usage

I'm not using XML for layouts in my Android project, and I simply can't use this lib at all.
You can't create a circular MaterialProgressBar, it just crashes saying determinate cirular progress bar isn't supported. But you can't set the determinate state before creating the object.

It looks like if you create a MaterialProgressBar without passing the PROGRESS_STYLE_CIRCULAR style, it actually creates an indeterminate circular progress... Weird behaviour, but it works.

Well I still don't get it. I can't create an horizontal progress bar now. Why doesn't this work?
MaterialProgressBar(context, null, R.style.Widget_MaterialProgressBar_ProgressBar_Horizontal_NoPadding)

If you want to create a Material Design ProgressBar programmatically, you can use a regular framework ProgressBar and call setProgressDrawable(new ...Drawable()) on it; or you can create a layout file and inflate it. The MaterialProgressBar widget is intended as a shortcut in layout files.


"Where Predicates" do not work as expected

Description
Export product with "Where predicate" set to

masterData(published=false)

Expected Behavior
All products which has published set to false are exported.
Current Behavior
All products which has published set to true are exported.

@VasumathiJayakumar Can you give the exact predicate you used (full predicate)? As well as context? It could well be an invalid predicate. See #171 for more details

@wizzy25 - yeah .. we found out that there are two issues

there is missing that where= prefix
and this tools is loading data from products-projection so no need for that masterData part

It is a little bit misleading that the label says "where predicate" and the attached link also leads to predicates documentation without any note how the propper query should look like.
Therefore I propose to add some better documentation to this tool or to split the query to where predicate and staged flag (so users would fill only predicate there and they would check the checkbox if they want staged true/false)

@junajan An issue will be created in impex, to update the specify where predicate line, and possibly add examples


connecting on non standard ports

doesn't seem to support  connecting on different ports
e.g I enter <IP_ADDRESS>:331 and it  returns New-SSHSession : No such host is known

It has a port option, you dont specify it in the conputername option
Sent from my iPhone

On Jan 3, 2016, at 12:55 PM, senposage<EMAIL_ADDRESS>wrote:
doesn't seem to support connecting on different ports
eg I enter 19216811:331 and it returns New-SSHSession : No such host is known
—
Reply to this email directly or view it on GitHub.

which would be where because its not mentioned in the docs

It should be in the get-help new-sshsession -full documentation
Did you ran get-help against the cmdlet and looked at the parameter information?
Sent from my iPhone

On Jan 5, 2016, at 12:10 AM, senposage<EMAIL_ADDRESS>wrote:
which would be where because its not mentioned in the docs
—
Reply to this email directly or view it on GitHub.

I do see it in the documentation if the cmdlet it self

PS C:\Users\Carlos Perez> help New-SSHSession -Parameter port

-Port []
    SSH TCP Port number to use for the SSH connection.

    Required?                    false
    Position?                    named
    Default value
    Accept pipeline input?       True (ByPropertyName)
    Accept wildcard characters?  false

PS C:\Users\Carlos Perez> help New-SSHSession

NAME
    New-SSHSession

SYNOPSIS
    Creates an SSH Session against a SSH Server

SYNTAX
    New-SSHSession [-ComputerName]  [-Credential]  [-Port []]
    [-ProxyServer []] [-ProxyPort []] [-ProxyCredential []]
    [-ProxyType []] [-ConnectionTimeOut []] [-KeepAliveInterval []]
    [-AcceptKey []] []

    New-SSHSession [-ComputerName]  [-Credential]  [-Port []]
    [-ProxyServer []] [-ProxyPort []] [-ProxyCredential []]
    [-ProxyType []] [-KeyFile []] [-ConnectionTimeOut []]
    [-KeepAliveInterval []] [-AcceptKey []] []

DESCRIPTION
    Creates an SSH Session against a remote server. The command supports creating connection
    thru a Proxy and allows for
    authentication to the server using username and password. If a key file is specified the
    command will use the password
    in the credentials parameter as the paraphrase of the key.

RELATED LINKS

REMARKS
    To see the examples, type: "get-help New-SSHSession -examples".
    For more information, type: "get-help New-SSHSession -detailed".
    For technical information, type: "get-help New-SSHSession -full".


[New Tool] OpenSCA-cli

Tool name and link (must be open source)
OpenSCA-cli, https://github.com/XmirrorSecurity/OpenSCA-cli
Supported specifications

[x] CycloneDX
[x] SPDX

Supported target

[ ] Container images
[ ] Source code repositories
[x] Packages

Environment setup (if any)
None
Recommended command to see version
(e.g. sartre-sbom --version --json)
opensca-cli -version
Recommended command(s) to build SBOM
(e.g. sartre-sbom build --cyclonedx --no-vuln ubuntu:latest)
opensca-cli -path ${project path} -out output.spdx.json
opensca-cli -path ${project path} -out output.cdx.json
Additional context
(e.g. only supports tag-value in SPDX, has external dependencies)

Thanks for raising this @SuperChen-CC , Just a preliminary note that SBOMs generated with OpenSCA seem to be missing key details, such as

creator tool details: Missing from CycloneDX, Missing version in SPDX
license details for packages
checksums for packages

These are not blockers but lead to a low sbomqs score. I am sharing examples of some scoring in case you plan to tackle these.

sbomqs score output.cdx.json
SBOM Quality Score:4.8	components:408	output.cdx.json
+-----------------------+--------------------------------+-----------+--------------------------------+
|       CATEGORY        |            FEATURE             |   SCORE   |              DESC              |
+-----------------------+--------------------------------+-----------+--------------------------------+
| NTIA-minimum-elements | comp_with_name                 | 10.0/10.0 | 407/408 have names             |

                  +--------------------------------+-----------+--------------------------------+

|                       | comp_with_supplier             | 0.0/10.0  | 0/408 have supplier names      |

                  +--------------------------------+-----------+--------------------------------+

|                       | comp_with_uniq_ids             | 10.0/10.0 | 408/408 have unique ID's       |

                  +--------------------------------+-----------+--------------------------------+

|                       | comp_with_version              | 9.9/10.0  | 402/408 have versions          |

                  +--------------------------------+-----------+--------------------------------+

|                       | sbom_authors                   | 0.0/10.0  | doc has 0 authors              |

                  +--------------------------------+-----------+--------------------------------+

|                       | sbom_creation_timestamp        | 0.0/10.0  | doc has creation timestamp     |

                  +--------------------------------+-----------+--------------------------------+

|                       | sbom_dependencies              | 10.0/10.0 | doc has 367 relationships      |
+-----------------------+--------------------------------+-----------+--------------------------------+
| Quality               | comp_valid_licenses            | 0.0/10.0  | 0/408 components with valid    |
|                       |                                |           | license                        |

                  +--------------------------------+-----------+--------------------------------+

|                       | comp_with_any_vuln_lookup_id   | 10.0/10.0 | 407/408 components have any    |
|                       |                                |           | lookup id                      |

                  +--------------------------------+-----------+--------------------------------+

|                       | comp_with_deprecated_licenses  | 0.0/10.0  | no licenses found              |

                  +--------------------------------+-----------+--------------------------------+

|                       | comp_with_multi_vuln_lookup_id | 0.0/10.0  | 0/408 components have multiple |
|                       |                                |           | lookup id                      |

                  +--------------------------------+-----------+--------------------------------+

|                       | comp_with_primary_purpose      | 10.0/10.0 | 408/408 components have        |
|                       |                                |           | primary purpose specified      |

                  +--------------------------------+-----------+--------------------------------+

|                       | comp_with_restrictive_licenses | 0.0/10.0  | no licenses found              |

                  +--------------------------------+-----------+--------------------------------+

|                       | sbom_with_creator_and_version  | 0.0/10.0  | 0/0 tools have creator and     |
|                       |                                |           | version                        |

                  +--------------------------------+-----------+--------------------------------+

|                       | sbom_with_primary_component    | 10.0/10.0 | primary component found        |
+-----------------------+--------------------------------+-----------+--------------------------------+
| Semantic              | comp_with_checksums            | 0.0/10.0  | 0/408 have checksums           |

                  +--------------------------------+-----------+--------------------------------+

|                       | comp_with_licenses             | 0.0/10.0  | 0/408 have licenses            |

                  +--------------------------------+-----------+--------------------------------+

|                       | sbom_required_fields           | 10.0/10.0 | Doc Fields:true Pkg            |
|                       |                                |           | Fields:false                   |
+-----------------------+--------------------------------+-----------+--------------------------------+
| Sharing               | sbom_sharable                  | 0.0/10.0  | doc has a sharable license     |
|                       |                                |           | free 0 :: of 0                 |
+-----------------------+--------------------------------+-----------+--------------------------------+
| Structural            | sbom_parsable                  | 10.0/10.0 | provided sbom is parsable      |

                  +--------------------------------+-----------+--------------------------------+

|                       | sbom_spec                      | 10.0/10.0 | provided sbom is in a          |
|                       |                                |           | supported sbom format of       |
|                       |                                |           | spdx,cyclonedx                 |

                  +--------------------------------+-----------+--------------------------------+

|                       | sbom_spec_file_format          | 10.0/10.0 | provided sbom should be in     |
|                       |                                |           | supported file format for      |
|                       |                                |           | spec: json and version:        |
|                       |                                |           | json,xml                       |

                  +--------------------------------+-----------+--------------------------------+

|                       | sbom_spec_version              | 0.0/10.0  | provided sbom should be        |
|                       |                                |           | in supported spec version      |
|                       |                                |           | for spec:1.5 and versions:     |
|                       |                                |           | 1.0,1.1,1.2,1.3,1.4            |
+-----------------------+--------------------------------+-----------+--------------------------------+
sbomqs score output.spdx.json
SBOM Quality Score:4.9	components:814	output.spdx.json
+-----------------------+--------------------------------+-----------+--------------------------------+
|       CATEGORY        |            FEATURE             |   SCORE   |              DESC              |
+-----------------------+--------------------------------+-----------+--------------------------------+
| NTIA-minimum-elements | comp_with_name                 | 10.0/10.0 | 814/814 have names             |

                  +--------------------------------+-----------+--------------------------------+

|                       | comp_with_supplier             | 1.6/10.0  | 132/814 have supplier names    |

                  +--------------------------------+-----------+--------------------------------+

|                       | comp_with_uniq_ids             | 10.0/10.0 | 814/814 have unique ID's       |

                  +--------------------------------+-----------+--------------------------------+

|                       | comp_with_version              | 10.0/10.0 | 814/814 have versions          |

                  +--------------------------------+-----------+--------------------------------+

|                       | sbom_authors                   | 10.0/10.0 | doc has 1 authors              |

                  +--------------------------------+-----------+--------------------------------+

|                       | sbom_creation_timestamp        | 10.0/10.0 | doc has creation timestamp     |
|                       |                                |           | 2024-01-24T16:51:47Z           |

                  +--------------------------------+-----------+--------------------------------+

|                       | sbom_dependencies              | 10.0/10.0 | doc has 367 relationships      |
+-----------------------+--------------------------------+-----------+--------------------------------+
| Quality               | comp_valid_licenses            | 0.0/10.0  | 0/814 components with valid    |
|                       |                                |           | license                        |

                  +--------------------------------+-----------+--------------------------------+

|                       | comp_with_any_vuln_lookup_id   | 10.0/10.0 | 814/814 components have any    |
|                       |                                |           | lookup id                      |

                  +--------------------------------+-----------+--------------------------------+

|                       | comp_with_deprecated_licenses  | 0.0/10.0  | no licenses found              |

                  +--------------------------------+-----------+--------------------------------+

|                       | comp_with_multi_vuln_lookup_id | 0.0/10.0  | 0/814 components have multiple |
|                       |                                |           | lookup id                      |

                  +--------------------------------+-----------+--------------------------------+

|                       | comp_with_primary_purpose      | 0.0/10.0  | 0/814 components have primary  |
|                       |                                |           | purpose specified              |

                  +--------------------------------+-----------+--------------------------------+

|                       | comp_with_restrictive_licenses | 0.0/10.0  | no licenses found              |

                  +--------------------------------+-----------+--------------------------------+

|                       | sbom_with_creator_and_version  | 0.0/10.0  | 0/1 tools have creator and     |
|                       |                                |           | version                        |

                  +--------------------------------+-----------+--------------------------------+

|                       | sbom_with_primary_component    | 0.0/10.0  | no primary component found     |
+-----------------------+--------------------------------+-----------+--------------------------------+
| Semantic              | comp_with_checksums            | 0.0/10.0  | 0/814 have checksums           |

                  +--------------------------------+-----------+--------------------------------+

|                       | comp_with_licenses             | 0.0/10.0  | 0/814 have licenses            |

                  +--------------------------------+-----------+--------------------------------+

|                       | sbom_required_fields           | 0.0/10.0  | Doc Fields:false Pkg           |
|                       |                                |           | Fields:false                   |
+-----------------------+--------------------------------+-----------+--------------------------------+
| Sharing               | sbom_sharable                  | 0.0/10.0  | doc has a sharable license     |
|                       |                                |           | free 0 :: of 0                 |
+-----------------------+--------------------------------+-----------+--------------------------------+
| Structural            | sbom_parsable                  | 10.0/10.0 | provided sbom is parsable      |

                  +--------------------------------+-----------+--------------------------------+

|                       | sbom_spec                      | 10.0/10.0 | provided sbom is in a          |
|                       |                                |           | supported sbom format of       |
|                       |                                |           | spdx,cyclonedx                 |

                  +--------------------------------+-----------+--------------------------------+

|                       | sbom_spec_file_format          | 10.0/10.0 | provided sbom should be in     |
|                       |                                |           | supported file format for      |
|                       |                                |           | spec: json and version:        |
|                       |                                |           | json,yaml,rdf,tag-value        |

                  +--------------------------------+-----------+--------------------------------+

|                       | sbom_spec_version              | 10.0/10.0 | provided sbom should be in     |
|                       |                                |           | supported spec version for     |
|                       |                                |           | spec:SPDX-2.3 and versions:    |
|                       |                                |           | SPDX-2.1,SPDX-2.2,SPDX-2.3     |
+-----------------------+--------------------------------+-----------+--------------------------------+

Thanks for your suggestions, we will start to optimize these contents.

Hi, @SuperChen-CC, sbombenchmark now has OpenSCA integrated with a handful of SBOM scanned. I understand that you are working on improving the SBOM capabilities of OpenSCA. So please let us know when they are completed, and we can -rescan all the repositories with it.
Related: I didn't see SBOM published for the OpenSCA project itself. Is this something you'd be interested in building? We can share some pointers on that.


JSON.stringify doesn't get all entity properties

const jim = alt.Ped.create({
  model: 's_m_y_cop_01',
  pos: new alt.Vector3({ x: 4476.591, y: -4493.673, z: 4.1902 }),
  heading: 0,
});

alt.log(JSON.stringify(jim));

 {"streamSyncedMeta":{},"syncedMeta":{},"meta":{},"type":2,"id":2}

Missing:

Base object

valid

WorldObject

dimension
pos

Entity

model
netOwner
rot
visible
streamed
frozen
collision
timestamp

Ped

health
maxHealth
armour
currentWeapon

Stringifying entities is something that will never work correctly due to the complexity of the classes. It shouldn't ever matter.


mitigate delayed close timeout race with connection write buffer flush - reopen

This is a follow up to a previous issue: #6392
That issue was closed due to a fix: #6437
I reopen this, because I am worried that previous issue has not been fixed.
I see approach to solving that issue changed over time and unfortunately I missed that change in PR. Sorry for not expressing my doubts earlier.
So these are my concerns / questions. Thank you in advance for answering these:
From the docs, regarding delayed_close_timeout:

To be useful in avoiding the race condition described above, this timeout must be set to at least +<100ms to account for a reasonable “worst” case processing time for a full iteration of Envoy’s event loop>.

And @alyssawilk comment from PR:

I will say that with the new plan I'm not convinced that this solves #6392 insofar as 20ms pretty short. That said I think it solves an underlying problem worth solving and #6392 may simply need longer timeouts.

I understand that short timeout will not protect against race condition described in the docs (race between closing and client processing response data). But will a race condition with write buffer flush still be possible? I mean, is there a chance, that Envoy will truncate a response when delayed_close_timeout is set to low value (20-50ms)?
Another thing from that PR that I am worried about is the information, that disabling delayed_closed_timeout can cause connection leaking. So it turns out, that it is also bad idea. It's unfortunate, because this was our workaround for this whole issue.
I see we only have the following options:

disable delayed_close_timeout

PROS:

we are immune to race between connection closing and write buffer flush
we are compatible with clients, that don't work well with delayed connection closing (e.g. Varnish healthchecks)

CONS:

we are exposed to connection leaking
we are exposed to race between client response processing and connection closing

set delayed_close_timeout to low value (< 100ms + round trip)

PROS:

we are immune to connection leaking
we are compatible with clients, that don't work well with delayed connection closing (e.g. Varnish healthchecks)

CONS:

we are exposed to race between connection connection closing and write buffer flush (is this true?)
we are exposed to race between client response processing and connection closing

set delayed_close_timeout to high or default value

PROS:

we are immune to race between connection closing and write buffer flush
we are immune to race between client response processing and connection closing

CONS:

we are NOT compatible with clients, that don't work well with delayed connection closing (e.g. Varnish healthchecks)

Fix the client, so it will work well with delayed close

Based on this table, options 1-3 are not good enough. Is the option 4. our only option?
IMHO the missing option is: wait for write buffer flush for a reasonable long time (1s for example), and then close the connection immediately, or after a short amount of time. With this option, the only CONS I see is "we are exposed to race between client response processing and connection closing" which is good enough for us. I believe this option will require introducing separate timeouts for buffer flush and delayed closing.

@AndresGuedez since you worked on https://github.com/envoyproxy/envoy/pull/6437, do you have any thoughts on this?

I understand that short timeout will not protect against race condition described in the docs (race between closing and client processing response data). But will a race condition with write buffer flush still be possible? I mean, is there a chance, that Envoy will truncate a response when delayed_close_timeout is set to low value (20-50ms)?

With PR #6437, Envoy will truncate the response only if there is backpressure to Envoy writing data to the client's socket and this causes write events to stall for an interval >= delayed_close_timeout. Prior to that PR, Envoy would close the connection early even if data was being regularly written to the client's socket.

Another thing from that PR that I am worried about is the information, that disabling delayed_closed_timeout can cause connection leaking. So it turns out, that it is also bad idea. It's unfortunate, because this was our workaround for this whole issue.

Unfortunately, connection leaks were possible prior to PR #6437 when delayed_close_timeout is disabled. For simplicity of configuration and implementation, it's desirable to have fewer timeouts so this timeout also serves as an idle timeout. My expectation with this timeout is that there are very few use cases where an end user will choose to disable the timeout or set a low value against the recommendation, so the dual purpose seemed appropriate.

I see we only have the following options:

disable delayed_close_timeout

PROS:

we are immune to race between connection closing and write buffer flush
we are compatible with clients, that don't work well with delayed connection closing (e.g. Varnish healthchecks)

Can you provide details on why delayed connection closing is an issue with Varnish healthchecks? Why is it an issue to wait 1s (by default) for those connections to terminate?

CONS:

we are exposed to connection leaking
we are exposed to race between client response processing and connection closing

set delayed_close_timeout to low value (< 100ms + round trip)

PROS:

we are immune to connection leaking
we are compatible with clients, that don't work well with delayed connection closing (e.g. Varnish healthchecks)

CONS:

we are exposed to race between connection connection closing and write buffer flush (is this true?)

It's possible if TCP ACKs from the client are not received within delayed_close_timeout window.

we are exposed to race between client response processing and connection closing

set delayed_close_timeout to high or default value

PROS:

we are immune to race between connection closing and write buffer flush
we are immune to race between client response processing and connection closing

CONS:

we are NOT compatible with clients, that don't work well with delayed connection closing (e.g. Varnish healthchecks)

Please see my question re: the incompatibility of Varnish health checks and delayed connection close.

Fix the client, so it will work well with delayed close

Based on this table, options 1-3 are not good enough. Is the option 4. our only option?
IMHO the missing option is: wait for write buffer flush for a reasonable long time (1s for example), and then close the connection immediately, or after a short amount of time. With this option, the only CONS I see is "we are exposed to race between client response processing and connection closing" which is good enough for us. I believe this option will require introducing separate timeouts for buffer flush and delayed closing.

Agreed this is another option. I was hoping to avoid this since adding more connection timeouts adds complexity for both Envoy developers and end users configuring the proxy, but it's possible your use case may be an exception to the dual purpose delayed_close_timeout.
My guess is that Varnish requires connections to be closed regardless of the HTTP response code prior to accepting a health check ack? If so, would it be possible to increase the Varnish health check timeout to be > delayed close timeout?

Can you provide details on why delayed connection closing is an issue with Varnish healthchecks? Why is it an issue to wait 1s (by default) for those connections to terminate?

@AndresGuedez Sure.

My guess is that Varnish requires connections to be closed regardless of the HTTP response code prior to accepting a health check ack?

Your guess is right. Varnish healtcheck (it is called a "probe") waits for connection closing by its backend (Envoy in this case) and adds that time to measured total time, which have to be less than the probe "timeout" parameter (otherwise heatcheck fails). Varnish doesn't close the connection by itself until the probe timeout triggers. In most recent version of Varnish this is even described in documentation https://varnish-cache.org/docs/6.2/reference/vcl.html#probes :

Note that probes require the backend to complete sending the response and close the connection within the specified timeout

If so, would it be possible to increase the Varnish health check timeout to be > delayed close timeout?

@AndresGuedez Yes, it would fix the problem. And It is possible, but very hard on our side. We have hundreds of varnish servers with thousands of healtchecks. And any of hundreds developers can create new ones. We would have to instruct them: "if your backend is Envoy, you should add +1s to varnish healtcheck timeout". Or we would have to create additional layer, which automatically modifies varnish configs. Either way it seems like over-complicated solution.
Varnish sends request request with Connection: close, but it doesn't close the connection after receiving a response. Thus I think Varnish violates rfc7230 section 6.6:

A client that sends a "close" connection option (...) MUST close the connection after reading the final response message corresponding to this request.

From this perspective it looks like this should be fixed in Varnish. But, on the other hand, we use Varnish with many http servers: various JVM servers, nodejs, nginx, apache, python/django and many others. And we never had this problem before with any of them. So it makes me think, that delayed connection closing is something very unique to Envoy.
I think it is something worth a discussion: Should Envoy behave differently than most existing http servers/proxies? Or maybe this is not true and you know other servers which behave the same as Envoy?
If you think that current state is OK and there is no need to change, we would try to fix this in Varnish.

Note that probes require the backend to complete sending the response and close the connection within the specified timeout

If so, would it be possible to increase the Varnish health check timeout to be > delayed close timeout?

@AndresGuedez Yes, it would fix the problem. And It is possible, but very hard on our side. We have hundreds of varnish servers with thousands of healtchecks. And any of hundreds developers can create new ones. We would have to instruct them: "if your backend is Envoy, you should add +1s to varnish healtcheck timeout". Or we would have to create additional layer, which automatically modifies varnish configs. Either way it seems like over-complicated solution.

Understood.

Varnish sends request with Connection: close, but it doesn't close the connection after receiving a response. Thus I think Varnish violates rfc7230 section 6.6:

A client that sends a "close" connection option (...) MUST close the connection after reading the final response message corresponding to this request.

From this perspective it looks like this should be fixed in Varnish. But, on the other hand, we use Varnish with many http servers: various JVM servers, nodejs, nginx, apache, python/django and many others. And we never had this problem before with any of them. So it makes me think, that delayed connection closing is something very unique to Envoy.

It seems most other proxies don't attempt to mitigate the connection close race condition that the delayed close timeout addresses. For your use case, it may be the case that clients and backends are well behaved in general, and your best option for now may be to simply disable this timeout. Doing so will leave open a small risk for connections to be leaked if they become inactive after the close sequence has been initiated, but this should be very rare. Prior to the delayed close timeout being introduced in 1.8, Envoy had no mechanism for addressing this type of connection leak, so if you were running Envoy prior to that version you were already exposed to this risk.
With that said, I agree this is not an ideal solution.

I think it is something worth a discussion: Should Envoy behave differently than most existing http servers/proxies? Or maybe this is not true and you know other servers which behave the same as Envoy?
If you think that current state is OK and there is no need to change, we would try to fix this in Varnish.

In my opinion, the best solution is that Varnish should become compliant with the HTTP spec and close connections after receiving the response from the backend. RFC 7230 6.6 provides a clear explanation as to why this is necessary:

If a server performs an immediate close of a TCP connection, there is
a significant risk that the client will not be able to read the last
HTTP response.  If the server receives additional data from the
client on a fully closed connection, such as another request that was
sent by the client before receiving the server's response, the
server's TCP stack will send a reset packet to the client;
unfortunately, the reset packet might erase the client's
unacknowledged input buffers before they can be read and interpreted
by the client's HTTP parser.

As you already pointed out, the other option is for Envoy to implement a separate idle timeout at the connection layer to decouple the delayed close logic from the inactivity logic. I think this would be an unfortunate increase in complexity given that this is the only use case reported so far where the coupling of this logic has caused problems.
@mattklein123 @alyssawilk What are your thoughts on this? Which side of the line are you on regarding Envoy mitigating issues caused by clients not in compliance with (important sections of) the HTTP spec?

I'd say that making Envoy more complicated to deal with non-compliant clients is not a high priority :-P
If folks are being impacted by this (yes) and have the cycles to dig into workarounds (maybe?  Marcin?) then we might allow the complexity, but I don't think it's a logical follow-on to Andres' work fixing the race for standards abiding clients.

It seems most other proxies don't attempt to mitigate the connection close race condition that the delayed close timeout addresses.

@AndresGuedez So if I understand correctly, you say that other proxies are as vulnerable as Envoy with delayed_close_timeout set to 0. If this is true, we can accept that risk, because we are accepting it for years using other proxies and nothing ever happened.
@alyssawilk Yes, maybe it will be fixed on Varnish side (I created an issue: https://github.com/varnishcache/varnish-cache/issues/2994). If not, we can probably live with delayed_closed_timeout set to 0, because as @AndresGuedez said, the risk is very low.
Thanks for clear information.


Mixing Where and OrderBy calls

Description
When I am mixing Where and OrderBy calls, I am getting exception:
Exception
Exception has occurred: CLR/System.ArgumentException
Необработанное исключение типа "System.ArgumentException" в System.Private.CoreLib.dll: 'Expression of type 'System.Linq.IOrderedQueryable`1[AspNetCoreBustronic.Models.RouteSegments]' cannot be used for return type 'System.Linq.IOrderedEnumerable`1[AspNetCoreBustronic.Models.RouteSegments]''

Code
``

var routes = context.Routes
.Where(e => e.IsReady.HasValue && e.IsReady.Value == true && !e.DeletedAt.HasValue)
.IncludeFilter(e => e.RouteSegments.Where(e => !e.DeletedAt.HasValue).OrderBy(e => e.Position))
.ToList();

``
Further technical details

EF version: 3.0 core latest
EF Plus version: latest
Database Provider: Npgsql latest

Hello @Jon,
Do you think you could provide a project sample with this issue?
It will help my developer investigate the issue more efficiently.
We now always ask for a project sample even if the issue is easy to reproduce. As a free product, we must find some way to save time to offer an overall better experience for everyone and release fixes faster.
You can send it to<EMAIL_ADDRESS>if you need to keep the source private
Best Regards,
Jonathan

Performance Libraries
context.BulkInsert(list, options => options.BatchSize = 1000);
Entity Framework Extensions • Entity Framework Classic • Bulk Operations •  Dapper Plus
Runtime Evaluation
Eval.Execute("x + y", new {x = 1, y = 2}); // return 3
C# Eval Function • SQL Eval Function

Hello @Ar4ics
Since our last conversation, we haven't heard from you.
Don't hesitate to provide a project sample with the issue.
looking forward to hearing from you,
Jon

Hello @Ar4ics
A quick reminder that we are here to assist you.
Feel free to send us a project sample with the issue, so that we can help you solve it!
Best regards,
Jon


Possible to get access to peer's name?

I'm trying to find a way to get access to the peer's name (i.e., sockaddr_in equivalent) but this information doesn't seem to get propagated past the tokio-proto and tokio-io layers. Is this by design or just a missing feature? If this is by design, is the appropriate place to implement my idea (something that needs access to peer's name but also implementing a protocol/service) directly atop tokio-core?
Really, what I want is what is described in https://tokio.rs/docs/getting-started/pipeline-server/ examples, but with the socket and/or peer name passed through to the service.

P.s., let me know if this is wrong venue to ask this type of question, I'll gladly move it somewhere else. :)

Ah yeah so currently this is difficult to do unfortunately.
The crate is generic over AsyncRead + AsyncWrite which means there's no easy access to, for example, remote_addr.
I think to handle this we'd need to add a new trait like trait RemoteAddr as well and bound by that, but that'd unfortunately leave out streams like SSL :(

Okay thanks @alexcrichton I just wanted to know if I was missing something obvious. I think that I can do what I want if I build starting at tokio-core layer, and then just duplicate some of the design that tokio-proto and tokio-io add, per the example.

I think to handle this we'd need to add a new trait like trait RemoteAddr as well and bound by that, but that'd unfortunately leave out streams like SSL :(

I don't follow and am curious... wouldn't an SSL stream still have a peer?

I don't think duplicating any of -proto and -io is necessary. You can
implement your ServerProto to take a type that knows the remote address,
specifically TcpStream. You can then grab the address in bind_transport.
On Thu, Apr 6, 2017 at 8:07 AM Stephen Holsapple<EMAIL_ADDRESS>wrote:

Okay thanks @alexcrichton https://github.com/alexcrichton I just wanted
to know if I was missing something obvious. I think that I can do what I
want if I build starting at tokio-core layer, and then just duplicate
some of the design that tokio-proto and tokio-io add, per the example.
I think to handle this we'd need to add a new trait like trait RemoteAddr
as well and bound by that, but that'd unfortunately leave out streams like
SSL :(
I don't follow and am curious... wouldn't an SSL stream still have a peer?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/tokio-rs/tokio-minihttp/issues/20#issuecomment-292204306,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAAYJISywjWAv6xMlrSJnkaT36a76Cvyks5rtP_OgaJpZM4M0l4h
.

@sholsapp oh sorry I just mean that one possible route for tokio-minihttp is to define a trait:
trait RemoteAddr {
    fn remote_addr(&self) -> SocketAddr;
}

and then require AsyncRead + AsyncWrite + RemoteAddr
Unfortunately though that trait wouldn't be easily implementable for types such as TlsStream<TcpStream>. It definitely has a possible implementation, it's just not automatic for you.


when passing masked card number "4111**********11" as values.number no card type is recognized

card.js does not recognize CC type (VISA/MasterCard/etc) when masked number is provided.

I think your issue is not clrear enough

Thanks for reporting this issue, much appreciated!
So, the values initializer isn't what this is for. Rather, it's for specifying the default values that show up on the card before users add data. The best analogy for this is the placeholder attribute on an input.
What you're looking for is the ability to pass in actual values that will Card will be initialized with. I've created a new issue for that at #184, so I'm closing this issue for now. Would appreciate any feedback there!


Add IPC to Magma

Should atleast included following features

[ ] Monitors
[ ] Keyboard
[ ] Workspaces
[ ] Windows
[ ] Layouts

we dont even have layouts yet

we will make a custom wayland protocol for it, you can look at https://github.com/HackedOS/magma for how to do it

we dont even have layouts yet

Well yes but take a look at this issue

W

we will make a custom wayland protocol for it, you can look at https://github.com/HackedOS/magma for how to do it

Why make a custom protocol for this? I think sway achieves IPC without a custom protocol.

W

we will make a custom wayland protocol for it, you can look at https://github.com/HackedOS/magma for how to do it

Why make a custom protocol for this? I think sway achieves IPC without a custom protocol.

Sway does this to achieve compatibility with i3, a custom protocol is way better bcz you can make 0 overhead scripts etc, like my workspaces script for the old magma was in rist with 0 overhead used barely any cpu cycles

Please also consider to add screensharing status for privacy purpose (or for fun)

might be a bit hard


go-e controller support

Ive tried without success to add the go-e controller to HA using the addon - my go-e charger working flawless..
Is it possible to do so with this addon or does that need further development/coding ?
https://go-e.com/en/products/go-e-controller

I think ther has to be done some coding.
Maybe one can just use the code base an "just" implement the definitions according to the go-e controller api (-> https://github.com/goecharger/go-eController-API).
Maybe I will try. But I am no "python guy" so this will be kind of a challenge (because I hate the python syntax ...)

I also just got the controller as my old meter died. Adding mqtt support parameters would be super as then they could be used elsewhere at HA. So basically reading the parameters eGo-Controller provides would be enough. No need to write anything.
If someone has to skills + energy to do this would be super.

Do you own the device and could you provide some MQTT message examples + topics?

In plaintext as code block here in the issue or as attached txt file if github accepts this file extension.

Please see attached file messages.json
It's in JSONL format but Gihub wouldn't let me use the .jsonl extension.
Every line is [{topic w/o prefix}, {dumped payload}]
Let me know if you need more!

Hi, is there any development on this topic? If some more message examples are needed I can also try to provide. I have 3phase setup if that makes any difference.....

Waiting this too. This add current sensors to my home assistant. Thanks

I've had busy days workwise but am hoping this holiday season may bring some free time.
Is it desirable to have the controller code as part of this project/repo @syssi? As this project/repo is called homeassistant-goecharger-mqtt I was wondering whether homeassistant-goe-mqtt as a shared place or another project/repo called homeassistant-goecontroller-mqtt would be preferable. I ask this humbly as I don't now what a change of name would entail.

I created POC here.
As of now only the basic power related things for the six CT sensors have been added.
Please note: there can be rough edges. I haven't tested installing through HACS as an example.

@karloskar : I tried your integration. Seems to work really well.
Now I can easily store the data from my go-e controller in my influxdb.
Great work! Many thanks!

Hey @karloskar - I am using your Controller POC and all the sensors I needed from it you got covered!
Thank you so much. It is so nice finally to have excess PV to charge my Tesla MY fully automated :)
Steffen

I'm happy about your implementation. Feel free to provide a pull request to extend the README of this project to point to your solution. We could also try to merge your device support into this project.

I've made a pull request for a README change. Feel free to edit if you think it should be positioned elsewhere.
I don't mind at all combining our projects :smile: My experience with HA development is rather limited. Would the questions I raised further up this thread be a good starting point straightening out?

Merged! :-) Let's close this issue.


Fix unsafe directory

Same as in https://github.com/roles-ansible/check-ansible-debian-latest-action/pull/10/

@DO1JLR  can you have a look?


Can't get it running with Django-Vite

I tried to set up Django with Inertia and Vue 3 by forking and cloning the Django Vite example repo and then adding the Inertia config. However, I have run into a problem - Vite fails with the following error:
failed to load config from D:\Projects\Python\django-vite-example\vite.config.js
error when starting dev server:
TypeError: vite.createFilter is not a function
    at vuePlugin (D:\Projects\Python\django-vite-example\node_modules\@vitejs\plugin-vue\dist\index.cjs:2549:23)
    at Object.<anonymous> (D:\Projects\Python\django-vite-example\vite.config.js:24:43)
    at Module._compile (node:internal/modules/cjs/loader:1105:14)
    at Object.require.extensions.<computed> [as .js] (D:\Projects\Python\django-vite-example\node_modules\vite\dist\node\chunks\dep-bc228bbb.js:70789:20)
    at Module.load (node:internal/modules/cjs/loader:981:32)
    at Function.Module._load (node:internal/modules/cjs/loader:822:12)
    at Module.require (node:internal/modules/cjs/loader:1005:19)
    at require (node:internal/modules/cjs/helpers:102:18)
    at loadConfigFromBundledFile (D:\Projects\Python\django-vite-example\node_modules\vite\dist\node\chunks\dep-bc228bbb.js:70797:17)
    at loadConfigFromFile (D:\Projects\Python\django-vite-example\node_modules\vite\dist\node\chunks\dep-bc228bbb.js:70718:32)
error Command failed with exit code 1.

I'm not sure what's going on here as googling the error message didn't lead to any relevant information.
You can check my setup here.

Thanks @mercuryseries ! I followed your tutorial and managed to set up React.
I'm now trying to setup Vue, but I've run into a major error. Not sure what's going on here but Vite's dependency pre-bundling is failing. The top-level error message reads as follows:
X [ERROR] [plugin vite:dep-pre-bundle] Failed to resolve entry for package "function-bind". The package may have incorrect main/module/exports specified in its package.json.

You can check out the code here.

Thank you so much for your help! I've got it working!


No arrows with style ggplot

If I select the ggplot style with
import matplotlib.style
matplotlib.style.use('ggplot')

I get no arrows for the boxes:

Thanks for the bug report and sorry for my delay in replying!
I've pushed a fix in cf65c681a87b97f20928366fcc67473fcfb3cf09.  In the meantime, you can work around this by specifying:
mpldatacursor.datacursor(arrowprops=dict(arrowstyle='->',
                                         connectionstyle='arc3,rad=0',
                                         edgecolor='black',
                                         facecolor='yellow'))

Thanks again for he bug report.


Inquire on the Test-Json command. Allowance to use in a product that needs to support PS v6.1-

This is a polite request on an allowance to use the Test-Json cmdlet code.
I'm doing a project named HealOps and it needs to support nodes running PowerShell versions below v6.1 (the version wherein the Test-Json cmdlet is included). Therefore, it would be wonderful if I could re-use the Test-Json code you did @iSazonov. However, can I? Am I allowed to do so? I know it is a MIT license and by reading the license text I get the impression that I can. As long as I include the license disclaimer.
So, would it be okay? Thank you very much.

@larssb Yes, you can re-use the code. See https://github.com/PowerShell/PowerShell/issues/7279#issuecomment-417146225

the recommendation is to attribute in a top level ThirdPartyNotices.txt file

Also we support side-by-side scenarios and you could redistribute latest PowerShell Core build (we have zip package) and latest Pester to target systems.

what to write in this file

Look the file in the PowerShell Core repo. (There is copies of original license texts).

E.g. by downloading the NuGet packages. Or????

Yes, you need to reference the NuGet packages to compile Test-Json.


Shipping method order isn't respected when the default shipping method isn't available

PHP Version
8.1
Shopware Version
<IP_ADDRESS>
Affected area / extension
Platform(Default)
Expected behaviour
When Shopware is unable to use the default shipping method, it should select the next best shipping method instead, based on the order that was configured in the admin panel
Actual behaviour
Shopware grabs the first valid shipping method it can find, which is based on the ID of the shipping method.
This can be seen in the getShippingMethodToChangeTo function inside storefront/Checkout/Shipping/BlockedShippingMethodSwitcher.php
How to reproduce

This was originally discovered in a project that is running Shopware <IP_ADDRESS>, but when I looked at the code in trunk, the code seemed to be unchanged and the bug is still present

Create 3 shipping methods
Determine which shipping method got a "higher" ID, and give that shipping method priority in the admin panel, we will call this "Shipping method A" to refer to this one
Make sure that the shipping method that got a "lower" ID is given less priority, we will call this "Shipping method B" to refer to this one
Make the remaining shipping method the default shipping method for the sales channel and give it a available rule that will become false when you attempt to check out.
Now add something to your cart and attempt to check out, it will now spring to "Shipping method B" instead of the expected "Shipping method A"

[public] Shopware automated response: This issue is linked to the internal issue https://shopware.atlassian.net/browse/NEXT-38034.
This link is only intended for Shopware employees and for internal use only.
[created from NEXT-38034, comment 489743]

[public]Thank you for your report. What exactly do you mean with priority of a shipping method? By default shipping methods don’t have a priority but a position and the position only determines the order in which the shipping methods should be listed on the checkout page. It does not define the order in which they are selected, if “prior” shipping methods are not available.
[created from NEXT-38034, comment 489947]

Yeah it's indeed about the position field, mixed it up with the naming of the rule builder 😅
While the name "Position" wouldn't be a perfect match anymore if this would be implemented, I think it would still make more sense than using the ID to determine the next best option.
Using the position would allow you to give specific shipping methods priority.

Another thing we noticed is that Shopware seems to execute the search with the shipping method excluded by name, not ID.
This caused it to also hide other shipping methods with the same name, even though those should have been visible.
Changing it to use it's ID instead should solve this issue.
Yes, I know it's a bit of a weird edge case, but this is something our client wanted. 😅


[Bug]: Fabric resources do not include Terraform UserAgent in API requests

Terraform Version
1
Equinix Provider Version
1
Effected Terraform Resources
equinix_fabric_*
Terraform Config Files
No response
Debug Output
No response
Panic Output
No response
Expected Behavior
API requests to the Fabric APIs include the Terraform SDK version and the fabric-go or equinix-metal-go version.
Actual Behavior
API requests report that the User-Agent is fabric-go
https://github.com/equinix/terraform-provider-equinix/blob/main/internal/config/config.go#L193-L220
Steps to Reproduce
Run Terraform on Fabric resources and check the User-Agent HTTP Header captured in API activity metrics or debug output
Related to #252

This was fixed in #606


Add support for collecting performance data for more than 1 function in the same .mlir file

Change is tested on branch: tpatel/issue-762. Need to refactor tracy-capture tool + tracy-csvexport in ttrt perf. Dependent on : https://github.com/tenstorrent/tt-mlir/pull/870


Keys

Creating new keys was erroneously removed from the app. It should be replaced.
Add KeyEditComponent <app-key-edit></app-key-edit> into the keys overview component
this area may give trouble. In that case, adapt so that you feed keys from here and delete troublesome code.
Also, this feature is needed because the site admins are thinking about adding new programs soon.

Closed by @CodyGramlich with #87.


Add embed::stub::spi

Resolves #26

Sorry, I'm not having success in getting a nice commit history.

@herculanodavi If you decide you want to pick up some other issues can you consider looking into some that are not stubs. I like to use those as intro issue for people to get started. I think a good next step would be to work on some mocks. Also consider joining our discord as well if you would like to discuss this stuff as well as attend our bi-weekly meetings. 😄

@herculanodavi try this link https://discord.gg/p5A6vzv8tm

I just submitted a change so that the discord badge is on the README now.


Add support for signet genesis block

See issue #60 and Eclair discussion/request #2382
This PR also adds check of the final genesis block hashes.

@remyers can you remove the Segnet hash in this PR as well (and in https://github.com/ACINQ/bitcoin-lib/pull/70)?

@remyers can you remove the Segnet hash in this PR as well (and in ACINQ/bitcoin-lib#70)?

It looks like I will have to recreate on testnet some tests in SegwitTestsCommon.kt that reference segnet transactions.

It looks like I will have to recreate on testnet some tests in SegwitTestsCommon.kt that reference segnet transactions.

Good point, but I think most of these tests are obsolete, and were only useful before segwit was activated. You can probably greatly simplify this test file by just verifying that p2wpkh and p2wsh work as expected, without referencing segnet transactions, this will remove some technical debt!

The tests seemed useful, so I just ported them to testnet in 2581f47 after removing segnet.


Update Documentation to 1.0.0

Preview: https://vision.sparky983.me/~/changes/XRks7UB6EWpVrg5fbkIv?r=AUPIecjgDt5tF72sfUI2

TODO
Currently the documentation references the latest SNAPSHOT (1.0.0-SNAPSHOT). After release this will need to be changed to 1.0.0.

TODO

[ ] Gui.Builder.fill(Button)
[ ] Mention #108

Completed by 12c08ea06fd3cfe02ea2624931957c719df7da23


Clarify restrictions for short codes

We seem to have the same or similar discussion about the availability of reference locations repeatedly. For example, the following three issues are currently open (and could be closed if this goes through):

#398 - a suggestion to add predefined "localities" to the end of plus codes using another separator
#461 - a request to have an "open set of anchors" that can be used world-wide
#497 - a complaint that short codes are "a black box" that need to be opened by releasing the full "dataset" Google Maps uses for their generation of short codes, or at least a "high level abstraction of an algorithm" to be implemented on a different dataset to result in the same name / code prefix relation.

I assume there might be additional closed issues along those lines, and we've had similar discussions on the mailing list. The underlying problem seems to be that the following caveats for short code generation and usage are either glossed over or not spelled out at all in the various parts of our documentation:

Short codes must be interpreted relative to some reference location. This reference location needs to be shared knowledge between all parties involved, or it needs to be transferred with the short code.
If the reference location is given as a location name (e.g. XXXX+XX CITY_NAME), which is this project's suggested way of doing things, then the recipient will have to translate this location name back into coordinates. Specifically, short codes will not work offline, unless the recipient has a lookup table available for all location names they might encounter.
Providing such lookup table is not within the scope of this project.
If a short code is generated using one provider, then there are no guarantees of being able to decode it via another provider. Specifically, short codes generated on Google Maps will probably have to be entered into Google Maps on the receiving device, or make use of Google Maps APIs.

Please comment if changes along those lines would not be welcome and merged if provided via PR. Unless that is the case, I will try to suggest doc changes along those lines in the coming days.

That seems reasonable. I've now checked the available documentation, and found that the following files do not need to be changed. They either don't talk about short codes at all, or just in technical contexts where the reference location exists as a lat/lng pair:

docs/comparison.adoc
docs/olc_definition.adoc
docs/specification.md
API.txt

This leaves the following to be updated, for which I will create a PR:

FAQ.txt
README.md

In addition to that, I suggest that the Wiki is changed as follows, so that we end up with a URL for the "global lookup table" request that we can paste into new issues asking for that:

[ ] add questions/answers added to FAQ.txt to FAQ as well

This needs to be done by the repository owner.

(Updated the FAQ)

That sounds good, thanks!
FWIW I think while dataset interoperability and offline are challenges, they're also present for numbered street addresses, which still manage to function well between mapping systems (and the real world). So it would be good not to emphasize that too much (which could also be discouraging for someone considering adoption of OLCs as an addressing system).
Re publishing an open dataset, too much of Google's data comes with licensing restrictions that preclude sharing freely, so that's a nonstarter (still plenty of other organizational and technical hurdles downstream though...).
I think Nominatim is a great option for someone looking for reasonable whole-world coverage. There's even an implementation of OLC geocoding/revgeo that uses Nominatim: https://gitlab.liu.se/davby02/olc
And many users of OLCs have requirements scaled to a particular region they support (e.g. if they're addressing with county names in a particular country, they only need a geocoder that handles those, which is pretty easy to put together from their own data or OSM).
Would be good to mention these viable alternatives.

A useful IRL application of OLCs that I've found in my line of work has been to use a 12-digit OLC as a distinct ID within a UK-based real estate database. Conventional addressing products like the Royal Mail PAF & OS Addressbase systems carry their own IDs which have widespread market adoption (UDPRNs & UPRNs) however both such systems are heavily dependent on the address-string and cannot capture 'future things'.
Real Estate businesses engaged in consultancy & transactional work often capture significant ammounts of data on a 'future development' i.e. the 100 houses that might get built on Field X in 5-10 years time, once someone has got planning permission, development finance, starting construction etc... Tying our information on 'future things' to conventional sddress systems is very inefficient & innaccurate; not least because in 99% of cases the address or 'name' will change multiple times over the lifespan of that development sites' evolution. This approach also asks colleagues to force the selection of one address as the 'master' when in reality a development opportunity/site spans multiple current addresses (all of which will then fall away & be supplanted as the development evolves).
In fact the only certain constant in these situations is the location - either defined as an input point (which if it is an existing address or feature, can be supplied by a 3rd party addressing system and refined by users as required) or as a calculated centroid of a site outline/polygon when we are dealing with Field X or Title Number Y.
In this way we have created a globally standardised set of "placeids" that act as unique serials in our database - with the added advantage that the serial itself contains spatial information. Proximate placeids can be easily identified based on truncating the serial by X characters.
To handle vertical stacking of places or co-location, we simply add an incrementing set of additional numeric characters to our OLC placeid


fix: bug 1559 when wrong bot all edit should be disabled

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

npm package (@next dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


⚠ Inventory API Endpoint has degraded performance

In 9490f26, Inventory API Endpoint (https://inventory.roblox.com/v1/users/82738847/assets/collectibles?limit=10&sortOrder=Asc) experienced degraded performance:

HTTP code: 200
Response time: 7283 ms

Resolved: Inventory API Endpoint performance has improved in 5796bb4 after 5 minutes.


Should i pass uuid into a id variable in the entity constructor?

In regular uuid we do that. with uuid-doctrine, i dont know if should i do that. Documentattion says  nothing about this, but when i try to inicialize entity in  the controller, and give a ID value of that entity in the next entity before flush, the ID isEmpty. What should i write, now?

If you're using the UUID as an ID, you can use the UuidBinaryType with @GeneratedValue - works very well.  If you are otherwise using the popular public-id, with private uuid method, then Doctrine supports only one @GeneratedValue. You'll put that on your id integer, and you can push the UUID into the constructor, or assume it within the constructor. YMMV.


BOOL Gauge Type

Is your feature request related to a problem? If so, please describe it.
I'd like to be able to monitor a boolean. This is useful for simple up/down metrics such a health checks.
Describe the solution you'd like.
The ability to create a Boolean Gauge which takes simply true/false.
Stackdriver has a specific BOOL type for this. It appears for SignalFX and Prometheus a Gauge which just accepts 1/0 would suffice.
Describe alternatives you've considered.
Using a Long Gauge as a hack but not ideal for Stackdriver.
Additional context.
Add any other context or screenshots about the feature request here.

Please file this feature request to https://github.com/open-telemetry/opentelemetry-specification. We'd like to be consistent with all language implementations when it comes to new APIs.

@dansiviter I think the new proposed idea coming from OpenMetrics is to support enums which probably can be very close to this and maybe more generic, a Boolean is just an enum with two values.

Still finding my feet with OpenTelemetry/OpenMetrics so apologies. Sounds promising so I'll take a look if it fits my use-case.

@dansiviter let me know if that fits your use-case, and if it does then I would move forward to push to that support in OpenTelemetry/OpenCensus.

See https://github.com/OpenObservability/OpenMetrics/pull/126/files#diff-d1792782ae179ab49b581de250c5def2R240


whitepaper v1

Describe your changes and provide context
Initial version of the whitepaper
Testing performed to validate your change
N/A

please publish repo.
sei_whitepaper_TR.pdf


Dust Labs + Solution #1 : Transcripts processing

Description
Adding a 'labs' component to front. This means :

New directory in pages/ - Called labs so for users it's the "Dust labs" area similar to Gmail Labs
New directory in api/
New model resource

Transcripts processing

Allows users to connect their personal Google Drive to pull meeting transcripts (transcripts pulled every 15 minutes)
When new transcript detected, send it to an assistant for summarization
Send email with summarized notes

How it works
After user connects Gdrive through Nango and picks an assistant, then can Activate the workflow
This will trigger a long running workflow (as long as the sync is active on the user end) that will trigger summarizing activities for each new transcript found
UI changes

New BETA menu
Moved extract page under labs and added feature flag
Transcript connector page

Risk

Pricing risk if a lot of meetings are transcribed, potential pressure on the temporal workers
First ever TS PR, might be 🗑. Hopefully not too much.

Deploy Plan
Add new SOLUTIONS .env vars
## SOLUTIONS
export SOLUTIONS_WORKSPACE_ID=xxx
export SOLUTIONS_API_KEY=sk-xxx

@albandum this generally looks great!
I didnt get the time to review thoroughly this weekend unfortunately (sorry). Deferring review to @flvndvd.
Eager to see this merged!!!

Was splitted into
https://github.com/dust-tt/dust/pull/4754
https://github.com/dust-tt/dust/pull/4752
https://github.com/dust-tt/dust/pull/4751


Factory girl breaks test migrations

Factory girl sometimes breaks migrations in the test environment.
I found it's necessary to avoid the default naming scheme (spec/factories.rb etc), and add a "require 'spec/xfactory.rb'"line at the end of spec_helper.rb.
Otherwise, the migrations do not take place when I run rake db:test:prepare.

@jferris  Hi can you explain a little bit why using string references here will magically make the migrations error go away?  THANKS A TON


BuildNumber and buildName are not used when building windows

Starting with flutter 3.3 we could use these parameters to produce versioned binary.

I apologize for the delay, added in commit 984f8f0. Thank you


toLowerCase() in index.html

Has happened to give error in the application when the amount of logs is very great and very fast. I have checked that the java script toLowerCase () function used to put flag images is to blame. I have adopted a simple solution here:
// var path = 'flags /' + args [i] .toLowerCase () + '.png';
Var path = 'flags /' + args [i] + '.png';
I removed toLowerCase () and used a shell script function to rename by capitalizing the acronyms of countries in the flags directory. Resolved for me.

Thanks for looking into this Diego! I'll commit the changes tonight.

hello
for file in *; do mv -- "$file" "${file^^}" ; done
for f in *.PNG; do mv -- "$f" "${f%.PNG}.png"; done
But if you have a very large log it s crash again

With me there is no crash, but the application needs adjustments to work for more than 24 hours and when there is logging through logrotate. I still need to kill the DataServer.py application, start a new instance of DataServer.py and do a reload in the browser.

Effectively logrotate make a crash of Data Server.py. I plan to debug this problem. I think you have to catch the exeception and wait for the generation of new lines in DataServer.py

I've never used Logrotate with this project myself. Tonight I will try reproducing the exception, and work on debugging it.


Hide only the picture icon

Discussed in https://github.com/mgrl/photobooth-app/discussions/99

Originally posted by laguinch October 24, 2023
Hy, is it possible to disable the collage icon on the panel like the admin icon ? Thx

implemented with #100


Hex Docs links broken

Need to remove the underscore in the github url here:
https://github.com/riverrun/notqwerty123/blob/master/mix.exs#L19

Thanks!


GH-35711: [Go] Add Value and GetValueIndex methods to some builders

Rationale for this change
See #35711
What changes are included in this PR?
Adding *BinaryDictionaryBuilder.GetValueIndex(i int) int to get the value's index in the dictionary. Then two methods to get a []byte and string results. Value(i int) []byte and ValueStr(i int) string.
Are these changes tested?
So far I have added very little testing. Mostly some sort of integration test to read back values from the BinaryDictionaryBuilder. We should definitely add some test for the *BinaryMemoTable) Value(i int) []byte.
Are there any user-facing changes?

Just additions, no breaking API changes.

cc @zeroshade

Closes: #35711

Rebased. :slightly_smiling_face:


Changed the color of the select major button on sign up page

#312

wacc

Actually can you make change membership plan and the dropdown have the same theme? Looks not so pretty with the three.

something like this?

i completely misread what you wrote, let me fix it

did you want something like this, where the drop down and the change membership button have the same color?

merge conflicts should be resolved now as well


Issues getting OKTA to work.

I seem to be getting issues when i follow https://www.bookstackapp.com/docs/admin/third-party-auth/#okta to get okta to work with instance of self hosted book stack. Can not find any documentation except this. When I click the okta link it takes me to my instance but does not login. I have removed all the sensative info. Have i missed a step to get my okta integrated?

Hi @nat-webdev,
It looks like you're editing the app/Config/services.php file. These files should not be altered unless you're intending to make deeper, non-supported changes to your instance.
Instead, revert any changes in the app/Config/services.php file (Let me know if you need guidance on that) then, all changes should made in the .env file within your install. This file might be hidden by default depending on system.
You'd add the options, shown in the documentation, to this file and customize there.

Since there's been no follow-up I'm going to close this. If the issue remains and is something you still require to be fixed please open a new issue, referencing this one.


dump  bug in converstion of authentications

Gitea Version: 1.2.0+rc1

Database
was sqlite
dump and moved to mariadb

Can you reproduce the bug:

[x ] Yes

./gitea dump -d mysql
-load the resulting sql file to mariadb
-modify app.ini to use mysql
-cannot login with external authentication any longer
-login with local admin account and see problem
original authentication before conversion
(&(groupMembership=cn=it,ou=UserGroups,ou=Unix,ou=Groups,ou=a,ou=b,o=c)(cn=%s))
after conversion
(u0026(groupMembership=cn=it,ou=UserGroups,ou=Unix,ou=Groups,ou=a,ou=b,o=c)(cn=%s))
the ampersand was changed to unicode.

I'm not sure that Gitea supports migrations between different SQL dialects :/


disable apply_boundaries and just watch the fps. Think about that

I want to apply the boundaries in calc_cells now that we iterate over every single cell

Pre calc the att_factor or not?

done in 2f3538629a490dfb50be0c3ba6eadc9ef9d9c02e


Console logging should be in ISO 8601 format.

Use New Date().toISOString() in app.js:log() method.

Updated in dev branch.


2 nested blocks breaks JSON

This will fail:
json.first do
  json.second do
    json.false true
  end
end

any resolution or hints on this?  trying to use this project (which is awesome) and running into problems because of it.


Logback version uplifted

Logback version changed 1.1.7 to 1.1.9

Version alignments for FOSSing.


fastapi return null when return value is a long integer

I am implementing a web app to print fibnocci series for any n number provided by the user.
In router part, I am able to see complete number, but when it comes to fastapi service, it fails to display larger number.
I am using ResponseModel as int and router looks like below:
@router.get("/Fibonacci", response_model = int)
 def get_fibonacci(number: int) -> int:
     fib = fibonacci(number)
     return fib
    // when I try to print fib, I could see long integer on my terminal, but on fastapi service, I see result as null.
   // where as it perfectly prints when value is upto:<PHONE_NUMBER>93079000000 (i.e.., fibnocci value of number: 102)

fibnocci() returns int

Example value that I want to print(fibnocci value of 2000):<PHONE_NUMBER>392304878706725602341482782579852840250681098010280137314308584370130707224123599639141511088446087538909603607640194711643596029271983312598737326253555802606991585915229492453904998722256795316982874482472992263901833716778060607011615497886719879858311468870876264597369086722884023654422295243347964480139515349562972087652656069529806499841977448720155612802665404554171717881930324025204312082516817125
Could someone suggest what could be the best way to display result as it is from the functionality ?
should I need to do any changes in ResponseModel ? or ?

This is probably related to OpenAPI, it should be working when you send a cURL to it.
Try it yourself.
curl http://<IP_ADDRESS>:8000/Fibonacci

This is probably related to OpenAPI, it should be working when you send a cURL to it.
Try it yourself.
curl http://<IP_ADDRESS>:8000/Fibonacci

Is there a way to fix it ?

The response message is correct。but problems start at 79。
It's the bug about OpenAPI Page(may be JS)
The frontend received<PHONE_NUMBER>4676221(fib 79) but display<PHONE_NUMBER>4676220

Is there a way to fix it ?

@mb19900210  It is not a bug, it is a limitation, fibonacci 2000 is too big that even JavaScript's BigInt can't handle it. Your code should work without an issue, you are only limited on Swagger.

Thanks for the help here @ycd and @Gascognya ! 👏  🙇
If that answers your question, then you can close this issue @mb19900210  ✔

Sorry for the long delay! 🙈  I wanted to personally address each issue/PR and they piled up through time, but now I'm checking each one in order.


Ready: Implement StyleCop

To start, I modified the And.cs file to not have any StyleCop warnings based on stock StyleCop settings.
CLIENTS-146 in JURA

@alexmoore my main concern with all of these changes are situations where _varFoo was renamed to varFoo when an existing varFoo was already being used, like in this place:
https://github.com/basho-labs/riak-dotnet-client/blob/jira/lrb/clients-146/src/RiakClient/Models/Search/GroupTerm.cs#L34-L41
https://github.com/basho-labs/riak-dotnet-client/blob/jira/lrb/clients-146/src/RiakClient/Models/Search/RiakFluentSearch.cs#L117-L124


Add windows/macos/android instructions for self-hosted

Implemented #93
Edit: Added android too

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

Hi @bcmmbaga, i think that's what i already did. I checked how it was done for the other tabs (linux, ubuntu, docker) in common.ts#L7 and common.ts#L20 and applied it here. You can see examples in lines AndroidTab.tsx#L25 and AndroidTab.tsx#L41.
If this is the wrong way could you point me to the correct implementation so i can fix it?

If this is the wrong way could you point me to the correct implementation so i can fix it

We can proceed with this at the moment


MIC-557

Codecov Report
Attention: Patch coverage is 80.00000% with 2 lines in your changes missing coverage. Please review.

Project coverage is 91.02%. Comparing base (d0c0894) to head (f7f7375).

Files with missing lines
Patch %
Lines

...rtinterventionplanapi/entity/DecisionAndActions.kt
75.00%
0 Missing and 1 partial :warning:

...lengesupportinterventionplanapi/entity/Referral.kt
66.66%
0 Missing and 1 partial :warning:

Additional details and impacted files
@@             Coverage Diff              @@
##               main     #155      +/-   ##
============================================
+ Coverage     91.01%   91.02%   +0.01%
- Complexity      752      755       +3
============================================
  Files           138      139       +1
  Lines          2158     2161       +3
  Branches        147      152       +5
============================================
+ Hits           1964     1967       +3
  Misses          130      130
  Partials         64       64

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.