FITCount Brazil app camera issue

Brazil have reported the following issue, but I am unable to replicate it on android on the live app. To me it sounds like it might be related to setting permissons for the app to use the camera, which may be different on iOS vs Android. Currently waiting for confirmation from Brazil about which platform they're on.
"I tried to take a photo with the camera, but using this option the app shut down/started again at "start survey"... It only worked using a photo from the gallery."

What is the device?
If the device has less than 4GB of RAM then it can't handle the camera app and the FIT apps together in the background.

It's confirmed as android. I have no problem on my android, so will see if they're able to review the RAM on their device

Motorola G7 Play, apparently has only 2gb of RAM, so would account for the issue. However, this is a 2019 phone, so not ancient really. Which means quite a few users may experience the same issue. If it's likely to be widespread we probably need to add a warning message or information of some sort?

It's an issue that has cropped up in some other projects too but, in general, it is a rare case and we haven't done anything about it in the past. Users with such low-end devices will experience the same issue with a number of other apps too so some will know this limitation already.
Ideally, we would show a warning in the app when the device has little RAM but there isn't an easy way to check for the available memory from the app. We can exclude the app from certain devices but this would be a tedious task keeping track of each device specification. If this issue comes affects more people then maybe we could specify the minimum requirements somewhere instead, what do you think?

Adding Claire to this for her thoughts @CCarvell - I have no idea if this is likely to be a more common issue in S.America vs EU countries.
If it's a rare case then I don't think we need to go as far as the second suggestion, but adding minimum requirements text seems a simple solution and gives the opportunity to explain the workaround (eg upload photo from gallery)

I agree, most of our other apps contain a "Help" page that explains how the app works, or its limitations.

Do you have a sample you can share that we can modify to suit the FITCount?

Yeah, maybe the FAQ in this one?

I think a comprehensive FAQ/How to page for the app will be a good idea in due course. Another thing for an country coordinators working group, once we get to that point. In the more immediate term, I was just thinking about a system requirements type note just to cover off the issue of the 2gb RAM. I didn't see anything similar on the butterflies app, but suspect you were sharing an idea of where we could put that type of content?

Yes, that's right. We haven't put the minimal requirements section in any other project yet. But that might be because other projects focus on European users with more powerful phones, just a guess.

Not clear if any action still required - closing for now.


Change Rift Lens debuff from slowing down to dying if all Rift Chests not opened in a certain amount of time

Done.


Exclamation point

If any task or subtask has an exclamation point anywhere in it, display that task or subtask in RED.

Done, "!" color change is indicated in theme.ini as "taskCurrent" and "subtaskCurrent"


Docker Compose stuck on Bindings.sh error

Describe the bug
Unable to run in Docker, always running into unable to find bindings.sh as the container starts running. I was able to run locally, but no success yet with Docker.
Link to the Bolt URL that caused the error
.
Steps to reproduce

git clone https://github.com/coleam00/bolt.new-any-llm.git
cd .\bolt.new-any-llm\
modify env file
docker compose up

Goes through the steps to run
[+] Running 2/2
✔ Network boltnew-any-llm_default       Created                                                                                0.0s
✔ Container boltnew-any-llm-bolt-app-1  Created                                                                                3.3s
Attaching to bolt-app-1
bolt-app-1  |
bolt-app-1  | > bolt@ start /app
bolt-app-1  | > bindings=$(./bindings.sh) && wrangler pages dev ./build/client $bindings --ip <IP_ADDRESS> --port 3000
bolt-app-1  |
bolt-app-1  | sh: 1: ./bindings.sh: not found
bolt-app-1  |  ELIFECYCLE  Command failed.
bolt-app-1 exited with code 1
Expected behavior
Success
Screen Recording / Screenshot
PS C:\Users\Test> git clone https://github.com/coleam00/bolt.new-any-llm.git
Cloning into 'bolt.new-any-llm'...
remote: Enumerating objects: 1736, done.
remote: Counting objects: 100% (816/816), done.
remote: Compressing objects: 100% (292/292), done.
remote: Total 1736 (delta 651), reused 555 (delta 514), pack-reused 920 (from 1)
Receiving objects: 100% (1736/1736), 1.07 MiB | 8.15 MiB/s, done.
Resolving deltas: 100% (1056/1056), done.
PS C:\Users\Test> docker compose up
no configuration file provided: not found
PS C:\Users\Test> cd .\bolt.new-any-llm
PS C:\Users\Test\bolt.new-any-llm> docker compose up
[+] Building 32.0s (15/15) FINISHED                                                                                docker:desktop-linux
=> [bolt-app internal] load build definition from Dockerfile                                                                                0.0s
=> => transferring dockerfile: 676B                                                                                0.0s
=> [bolt-app internal] load metadata for docker.io/library/node:20.15.1                                                                                0.5s
=> [bolt-app auth] library/node:pull token for registry-1.docker.io                                                                                0.0s
=> [bolt-app internal] load .dockerignore                                                                                0.0s
=> => transferring context: 2B                                                                                0.0s
=> [bolt-app 1/8] FROM docker.io/library/node:20.15.1@sha256:6326b52a508f0d99ffdbfaa29a69380321b215153db6f32974835bac71b38fa4                                                                                0.0s
=> => resolve docker.io/library/node:20.15.1@sha256:6326b52a508f0d99ffdbfaa29a69380321b215153db6f32974835bac71b38fa4                                                                                0.0s
=> [bolt-app internal] load build context                                                                                0.1s
=> => transferring context: 2.57MB                                                                                0.1s
=> CACHED [bolt-app 2/8] WORKDIR /app                                                                                0.0s
=> CACHED [bolt-app 3/8] RUN npm install -g<EMAIL_ADDRESS>                                                                                0.0s
0.0s
[+] Running 1/1
✔ Container boltnew-any-llm-bolt-app-1  Created                                                                                3.1s
bolt-app-1  | > bolt@ start /app
bolt-app-1  | > bindings=$(./bindings.sh) && wrangler pages dev ./build/client $bindings --ip <IP_ADDRESS> --port 3000
bolt-app-1  |
bolt-app-1  | sh: 1: ./bindings.sh: not found
bolt-app-1  |  ELIFECYCLE  Command failed.
bolt-app-1 exited with code 1
v View in Docker Desktop   o View Codocker compose up^Chaun\bolt.new-any-llm>
PS C:\Users\Test\bolt.new-any-llm> docker compose up
[+] Running 1/0
✔ Container boltnew-any-llm-bolt-app-1  Created                                                                                0.0s
Attaching to bolt-app-1
bolt-app-1  |
bolt-app-1  | > bolt@ start /app
bolt-app-1  | > bindings=$(./bindings.sh) && wrangler pages dev ./build/client $bindings --ip <IP_ADDRESS> --port 3000
bolt-app-1  |
bolt-app-1  | sh: 1: ./bindings.sh: not found
bolt-app-1  |  ELIFECYCLE  Command failed.
bolt-app-1 exited with code 1
PS C:\Users\Test\bolt.new-any-llm> docker compose down
[+] Running 2/2r Desktop   o View Config   w Enable Watch
✔ Container boltnew-any-llm-bolt-app-1  Removed                                                                                0.0s
✔ Network boltnew-any-llm_default       Removed                                                                                0.2s
PS C:\Users\Test\bolt.new-any-llm>
PS C:\Users\Test\bolt.new-any-llm> docker-compose build --no-cache
[+] Building 59.1s (15/15) FINISHED                                                                                docker:desktop-linux
=> [bolt-app internal] load build definition from Dockerfile                                                                                0.0s
=> [bolt-app internal] load metadata for docker.io/library/node:20.15.1                                                                                0.4s
=> [bolt-app auth] library/node:pull token for registry-1.docker.io                                                                                0.0s
=> [bolt-app internal] load .dockerignore                                                                                0.0s
=> => transferring context: 2B                                                                                0.0s
=> [bolt-app 1/8] FROM docker.io/library/node:20.15.1@sha256:6326b52a508f0d99ffdbfaa29a69380321b215153db6f32974835bac71b38fa4                                                                                0.0s
=> => resolve docker.io/library/node:20.15.1@sha256:6326b52a508f0d99ffdbfaa29a69380321b215153db6f32974835bac71b38fa4                                                                                0.0s
=> [bolt-app internal] load build context                                                                                0.0s
=> => transferring context: 10.61kB                                                                                0.0s
=> CACHED [bolt-app 2/8] WORKDIR /app                                                                                0.0s
=> [bolt-app 3/8] RUN npm install -g<EMAIL_ADDRESS>                                                                                1.5s
=> [bolt-app 4/8] COPY package.json pnpm-lock.yaml* ./                                                                                0.1s
=> [bolt-app 5/8] RUN pnpm install                                                                                8.4s
=> [bolt-app 6/8] COPY . .                                                                                0.3s
=> [bolt-app 7/8] RUN pnpm run build                                                                                20.0s
=> [bolt-app 8/8] RUN chmod +x bindings.sh                                                                                0.4s
=> [bolt-app] exporting to image                                                                                27.5s
=> => exporting layers                                                                                17.7s
=> => exporting manifest sha256:3ee1663c0b4f03ec8b3c676499745c2f74751a2af8b951c698b07a8473b15ce7                                                                                0.0s
=> => exporting config sha256:7e1dd417d6d864c244285a65ccd28b687824db38d3f0cc4893b63106acb19f1c                                                                                0.0s
=> => exporting attestation manifest sha256:e4fe673785f1d6730092f63467ba0273dc3ff4cbded66e47f046a912ec9e08b9                                                                                0.0s
=> => exporting manifest list sha256:f28e14d8922e485c6a06ba93a2471a53df908a7a03fd7b6344586efa09a982dd                                                                                0.0s
=> => naming to docker.io/library/boltnew-any-llm-bolt-app:latest                                                                                0.0s
=> => unpacking to docker.io/library/boltnew-any-llm-bolt-app:latest                                                                                9.7s
=> [bolt-app] resolving provenance for metadata file                                                                                0.0s
PS C:\Users\Test\bolt.new-any-llm> docker compose up
[+] Running 2/2
✔ Network boltnew-any-llm_default       Created                                                                                0.0s
✔ Container boltnew-any-llm-bolt-app-1  Created                                                                                3.3s
Attaching to bolt-app-1
bolt-app-1  |
bolt-app-1  | > bolt@ start /app
bolt-app-1  | > bindings=$(./bindings.sh) && wrangler pages dev ./build/client $bindings --ip <IP_ADDRESS> --port 3000
bolt-app-1  |
bolt-app-1  | sh: 1: ./bindings.sh: not found
bolt-app-1  |  ELIFECYCLE  Command failed.
bolt-app-1 exited with code 1
Platform

OS: Windows 10 Pro fresh install yesterday
Browser: Chrome Canary
Version: N/A
Docker / WSL2

Additional context
General experience in figuring stuff out. Issue could be me. In this attempt, I did the bare minimum to see if it would still fail in order to take this example.

Are you working with docker on windows, had similar problems but is now working. In my case, the LF was replaced by CR LF by checkout in case of mounted directory. Try dos2unix bindings.sh and chmod +x bindings.sh ...

Are you working with docker on windows? I had a similar problems but it is working now. In my case, the LF was replaced by CR LF at checkout in case of mounted directory. Try dos2unix bindings.sh and chmod +x bindings.sh ...

Thanks for the nudge! I set up a WSL2 Ubuntu VM to run docker compose and Bindings.sh is no longer the issue!
I investigated and ran dos2unix and had no luck getting past bindings error if it was related to added CR. This still seems like a me-problem and my lack of knowledge about running docker on windows..   On to the next one!
[+] Running 2/2
✔ Network boltnew-any-llm_default       Created                                                                   0.0s
✔ Container boltnew-any-llm-bolt-app-1  Created                                                                   3.5s
Attaching to bolt-app-1
bolt-app-1  |
bolt-app-1  | > bolt@ start /app
bolt-app-1  | > bindings=$(./bindings.sh) && wrangler pages dev ./build/client $bindings --ip <IP_ADDRESS> --port 3000
bolt-app-1  |
bolt-app-1  |
bolt-app-1  |  ⛅ wrangler 3.63.2 (update available 3.83.0)
bolt-app-1  | ---------------------------------------------
bolt-app-1  |
bolt-app-1  | ✘ [ERROR] Could not resolve "../build/server"
bolt-app-1  |
bolt-app-1  |     [[path]].ts:5:29:
bolt-app-1  |       5 │ import * as serverBuild from '../build/server';
bolt-app-1  |         ╵                              ~~~~~~~~~~~~~~~~~
bolt-app-1  |
bolt-app-1  |
bolt-app-1  |
bolt-app-1  | ✘ [ERROR] Failed to build Functions at ./functions.
bolt-app-1  |
bolt-app-1  |
bolt-app-1  | 🪵  Logs were written to "/root/.config/.wrangler/logs/wrangler-2024-10-30_07-50-48_600.log"
bolt-app-1  |  ELIFECYCLE  Command failed with exit code 1.
bolt-app-1 exited with code 1

I'm having this issue with bindings.sh not found, i'm on Windows 10 and using WSL2 on Docker. This is the output:
 docker-compose --profile production up time="2024-11-14T11:59:36-03:00" level=warning msg="The \"GROQ_API_KEY\" variable is not set. Defaulting to a blank string." time="2024-11-14T11:59:36-03:00" level=warning msg="The \"OPENAI_API_KEY\" variable is not set. Defaulting to a blank string." time="2024-11-14T11:59:36-03:00" level=warning msg="The \"ANTHROPIC_API_KEY\" variable is not set. Defaulting to a blank string." time="2024-11-14T11:59:36-03:00" level=warning msg="The \"OPEN_ROUTER_API_KEY\" variable is not set. Defaulting to a blank string." time="2024-11-14T11:59:36-03:00" level=warning msg="The \"GOOGLE_GENERATIVE_AI_API_KEY\" variable is not set. Defaulting to a blank string." time="2024-11-14T11:59:36-03:00" level=warning msg="The \"OLLAMA_API_BASE_URL\" variable is not set. Defaulting to a blank string." time="2024-11-14T11:59:36-03:00" level=warning msg="The \"GROQ_API_KEY\" variable is not set. Defaulting to a blank string." time="2024-11-14T11:59:36-03:00" level=warning msg="The \"OPENAI_API_KEY\" variable is not set. Defaulting to a blank string." time="2024-11-14T11:59:36-03:00" level=warning msg="The \"ANTHROPIC_API_KEY\" variable is not set. Defaulting to a blank string." time="2024-11-14T11:59:36-03:00" level=warning msg="The \"OPEN_ROUTER_API_KEY\" variable is not set. Defaulting to a blank string." time="2024-11-14T11:59:36-03:00" level=warning msg="The \"GOOGLE_GENERATIVE_AI_API_KEY\" variable is not set. Defaulting to a blank string." time="2024-11-14T11:59:36-03:00" level=warning msg="The \"OLLAMA_API_BASE_URL\" variable is not set. Defaulting to a blank string." [+] Running 1/1  ! bolt-ai Warning pull access denied for bolt-ai, repository does not exist or may require 'docker login': denied: requested access to the resource is denied                                          2.2s  [+] Building 1.2s (16/16) FINISHED                                                                                docker:desktop-linux  => [bolt-ai internal] load build definition from Dockerfile                                                                                0.0s  => => transferring dockerfile: 2.31kB                                                                                0.0s   => [bolt-ai internal] load metadata for docker.io/library/node:20.18.0                                                                                1.2s   => [bolt-ai auth] library/node:pull token for registry-1.docker.io                                                                                0.0s   => [bolt-ai internal] load .dockerignore                                                                                0.0s  => => transferring context: 401B                                                                                0.0s   => [bolt-ai base 1/7] FROM docker.io/library/node:20.18.0@sha256:a7a3b7ec6de4b11bb2d673b31de9d28c6da09c557ee65453672c8e4f754c23fc                                                                      0.0s   => [bolt-ai internal] load build context                                                                                0.0s   => => transferring context: 7.39kB                                                                                0.0s   => CACHED [bolt-ai base 2/7] WORKDIR /app                                                                                0.0s   => CACHED [bolt-ai base 3/7] COPY package.json pnpm-lock.yaml ./                                                                                0.0s   => CACHED [bolt-ai base 4/7] RUN corepack enable pnpm && pnpm install                                                                                0.0s   => CACHED [bolt-ai base 5/7] COPY . .                                                                                0.0s   => CACHED [bolt-ai base 6/7] COPY bindings.sh ./bindings.sh                                                                                0.0s   => CACHED [bolt-ai base 7/7] RUN chmod +x ./bindings.sh                                                                                0.0s   => CACHED [bolt-ai bolt-ai-production 1/2] RUN mkdir -p /root/.config/.wrangler &&     echo '{"enabled":false}' > /root/.config/.wrangler/metrics.json                                                 0.0s   => CACHED [bolt-ai bolt-ai-production 2/2] RUN npm run build                                                                                0.0s   => [bolt-ai] exporting to image                                                                                0.0s   => => exporting layers                                                                                0.0s   => => writing image sha256:57e6a872c3770b7c913ab6e6eb3558854e9cd0c1ab7efca914c8435d2d5bd120                                                                                0.0s   => => naming to docker.io/library/bolt-ai:production                                                                                0.0s   => [bolt-ai] resolving provenance for metadata file                                                                                0.0s  [+] Running 2/1  ✔ Network boltnewanyllm_default      Created                                                                                0.0s   ✔ Container boltnewanyllm-bolt-ai-1  Created                                                                                0.0s  Attaching to bolt-ai-1 bolt-ai-1  |  bolt-ai-1  | > bolt@ dockerstart /app bolt-ai-1  | > bindings=$(./bindings.sh) && wrangler pages dev ./build/client $bindings --ip <IP_ADDRESS> --port 5173 --no-show-interactive-dev-session bolt-ai-1  |  bolt-ai-1  | sh: 1: ./bindings.sh: not found bolt-ai-1  |  ELIFECYCLE  Command failed. bolt-ai-1 exited with code 1


[SPARK-17239][ML][DOC] Update user guide for multiclass logistic regression

What changes were proposed in this pull request?
Updates user guide to reflect that LogisticRegression now supports multiclass. Also adds new examples to show multiclass training.
How was this patch tested?
Ran locally using spark-submit, run-example, and copy/paste from user guide into shells. Generated docs and verified correct output.

cc @jaceklaskowski @jkbradley @dbtsai

Test build #66332 has started for PR 15349 at commit 0144aff.

Test build #66332 has finished for PR 15349 at commit 0144aff.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/66332/
Test PASSed.

Merged build finished. Test PASSed.

LGTM. Merged into master. Thanks.

Thanks @dbtsai!


[tool_crash] RPCError

Command
flutter --no-color run --machine --track-widget-creation --device-id=chrome --start-paused --dart-define=flutter.inspector.structuredErrors=true --devtools-server-address=http://<IP_ADDRESS>:9100 lib\main.dart

Steps to Reproduce
I don't know how to reproduce this as it happened suddenly without any error in my application. I was running a flutter web application and after a hot reload this happened.
Logs
RPCError
#0      new _OutstandingRequest (package:vm_service/src/vm_service.dart:1626:45)
#1      VmService._call (package:vm_service/src/vm_service.dart:2107:21)
#2      VmService.getIsolate (package:vm_service/src/vm_service.dart:1863:7)
#3      FlutterVmService.getIsolateOrNull (package:flutter_tools/src/vmservice.dart:902:20)
#4      FlutterVmService.findExtensionIsolate (package:flutter_tools/src/vmservice.dart:868:50)
<asynchronous suspension>
#5      FlutterResidentDevtoolsHandler._waitForExtensionsForDevice (package:flutter_tools/src/resident_devtools_handler.dart:171:7)
<asynchronous suspension>
#6      Future.wait.<anonymous closure> (dart:async/future.dart)
<asynchronous suspension>
#7      FlutterResidentDevtoolsHandler._devicesWithExtensions (package:flutter_tools/src/resident_devtools_handler.dart:161:41)
<asynchronous suspension>
#8      FlutterResidentDevtoolsHandler.hotRestart (package:flutter_tools/src/resident_devtools_handler.dart:238:54)
<asynchronous suspension>

[✓] Flutter (Channel beta, 2.4.0-4.2.pre, on Microsoft Windows [Version 10.0.19043.1110], locale en-IN)
    • Flutter version 2.4.0-4.2.pre at D:\flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision f18b9281c2 (8 days ago), 2021-07-22 14:08:30 -0700
    • Engine revision 844c29f42a
    • Dart version 2.14.0 (build 2.14.0-301.2.beta)

[✓] Android toolchain - develop for Android devices (Android SDK version 30.0.3)
    • Android SDK at C:\Users\shata\AppData\Local\Android\Sdk
    • Platform android-30, build-tools 30.0.3
    • ANDROID_SDK_ROOT = C:\Users\shata\AppData\Local\Android\Sdk
    • Java binary at: D:\Android\Android Studio\jre\bin\java
    • Java version OpenJDK Runtime Environment (build 11.0.10+0-b96-7249189)
    • All Android licenses accepted.

[✓] Chrome - develop for the web
    • Chrome at C:\Program Files\Google\Chrome\Application\chrome.exe

[✓] Visual Studio - develop for Windows (Visual Studio Community 2019 16.10.0)
    • Visual Studio at C:\Program Files (x86)\Microsoft Visual Studio\2019\Community
    • Visual Studio Community 2019 version 16.10.31321.278
    • Windows 10 SDK version 10.0.19041.0

[✓] Android Studio (version 4.2.0)
    • Android Studio at D:\Android\Android Studio
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 11.0.10+0-b96-7249189)

[✓] IntelliJ IDEA Ultimate Edition (version 2020.3)
    • IntelliJ at D:\IntelliJ IDEA 2020.3.1
    • Flutter plugin version 54.0.3
    • Dart plugin version 203.7759

[✓] Connected device (2 available)
    • Chrome (web) • chrome • web-javascript • Google Chrome 92.0.4515.107
    • Edge (web)   • edge   • web-javascript • Microsoft Edge 92.0.902.55

• No issues found!

Flutter Application Metadata
Type: app
Version: 0.0.1-rc+1
Material: true
Android X: false
Module: false
Plugin: false
Android package: null
iOS bundle identifier: null
Creation channel: master
Creation framework version: be5b5c898c98699328310d7369d813cf34f6e3a9
Plugins
cloud_firestore-0.14.4
cloud_firestore_web-0.2.1+2
file_picker_web-2.0.0
firebase_auth-0.18.4+1
firebase_auth_web-0.3.2+3
firebase_core-0.5.3
firebase_core_web-0.2.1+1
firebase_storage-5.0.1
fluttertoast-7.1.8
path_provider_linux-0.0.1+2
path_provider_windows-0.0.5
searchable_dropdown-1.1.3
shared_preferences-0.5.12+4
shared_preferences_linux-0.0.2+4
shared_preferences_macos-0.0.1+11
shared_preferences_web-0.1.2+7
shared_preferences_windows-0.0.2+3
url_launcher-5.7.10
url_launcher_linux-0.0.1+4
url_launcher_macos-0.0.1+9
url_launcher_web-0.1.5+3
url_launcher_windows-0.0.1+3
video_player-2.1.6
video_player_web-2.0.1
wakelock-0.5.2
wakelock_macos-0.1.0+1
wakelock_web-0.2.0+1

Below are related RPCError tool_crashes, but they didn't have the stacktrace as listed above:
https://github.com/flutter/flutter/issues/86333
https://github.com/flutter/flutter/issues/83886
https://github.com/flutter/flutter/issues/78099
This similar issue, https://github.com/flutter/flutter/issues/73815 was fixed when it crashed throwing _flutter.listViews: (-32000) Bad state, but above issue doesn't seem to be the same case.
@shatanikmahanty
Can you switch to latest master or latest stable and try the same command again to see if you get same crash there too ?
Thanks.

If I switch to master, how do I reproduce this issue can you let me know?

@shatanikmahanty
After switching to latest master, just try to run the same command again and see if you get the same error or not, ie,:
flutter channel master
flutter upgrade
flutter --no-color run --machine --track-widget-creation --device-id=chrome --start-paused --dart-define=flutter.inspector.structuredErrors=true --devtools-server-address=http://<IP_ADDRESS>:9100 lib\main.dart

Ok. Will do it tonight and let you know. Thanks for clarifying

I switched to master and ran the command but no crashes happened upon surfing the web application

Thanks for the update. This indicates the crash doesn't occur on latest master and seem to have fixed on that version already. I am going ahead and closing this as fixed. It may not have been rolled onto beta yet, so you can be on master.


Test for missing Python modules and warn the user

See if it's possible to check for the required Python modules (pyaml and urllib3) and warn the users about it without a nasty crash :)

Done. Code will exit with a proper error message if one of the required external libraries are not present.


srb rbi gems fails on a Rails app running 6.0.0.rc2

Input
I've got my Rails app working fine with Rails 5.2.3, but upon upgrading to Rails 6.0.0.rc2 srb rbi update (specifically the srb rbi gems stage) fails.
Observed output
connorshea$ bundle exec srb rbi update

👋 Hey there!

This script will get this project ready to use with Sorbet by creating a
sorbet/ folder for your project. It will contain:

- a config file
- a bunch of 'RBI files'

RBI stands for 'Ruby Interface'; these files define classes, methods, and
constants that exist, but which Sorbet doesn't always know about.

⚠  Heads up:

To set up your project, this script will take two potentially destructive
actions:

1.  It will require every file in your project. Specifically, every script in
    your project will be run, unless that script checks if __FILE__ == $PROGRAM_NAME
    before running any code, or has the magic comment # typed: ignore in it.

2.  It will add a comment to the top of every file (like # typed: false or
    # typed: true, depending on how many errors were found in that file.)

❔ Would you like to continue? [Y/n] y
Generating: sorbet/config
Reusing existing config file: sorbet/config
Generating: sorbet/rbi/sorbet-typed/
Generating: sorbet/rbi/gems/
Traceback (most recent call last):
	10: from /Users/connorshea/.rbenv/versions/2.6.3/lib/ruby/gems/2.6.0/gems/sorbet-0.4.4524/bin/srb-rbi:234:in `<main>'
	 9: from /Users/connorshea/.rbenv/versions/2.6.3/lib/ruby/gems/2.6.0/gems/sorbet-0.4.4524/bin/srb-rbi:196:in `main'
	 8: from /Users/connorshea/.rbenv/versions/2.6.3/lib/ruby/gems/2.6.0/gems/sorbet-0.4.4524/bin/srb-rbi:118:in `init'
	 7: from /Users/connorshea/.rbenv/versions/2.6.3/lib/ruby/gems/2.6.0/gems/sorbet-0.4.4524/bin/srb-rbi:229:in `block in make_step'
	 6: from /Users/connorshea/.rbenv/versions/2.6.3/lib/ruby/gems/2.6.0/gems/sorbet-0.4.4524/lib/gem-generator-tracepoint.rb:38:in `main'
	 5: from /Users/connorshea/.rbenv/versions/2.6.3/lib/ruby/gems/2.6.0/gems/sorbet-0.4.4524/lib/gem-generator-tracepoint/tracer.rb:70:in `trace'
	 4: from /Users/connorshea/.rbenv/versions/2.6.3/lib/ruby/gems/2.6.0/gems/sorbet-0.4.4524/lib/gem-generator-tracepoint.rb:39:in `block in main'
	 3: from /Users/connorshea/.rbenv/versions/2.6.3/lib/ruby/gems/2.6.0/gems/sorbet-0.4.4524/lib/require_everything.rb:20:in `require_everything'
	 2: from /Users/connorshea/.rbenv/versions/2.6.3/lib/ruby/gems/2.6.0/gems/sorbet-0.4.4524/lib/require_everything.rb:44:in `require_all_files'
	 1: from /Users/connorshea/.rbenv/versions/2.6.3/lib/ruby/gems/2.6.0/gems/sorbet-0.4.4524/lib/require_everything.rb:114:in `excluded_rails_files'
/Users/connorshea/.rbenv/versions/2.6.3/lib/ruby/gems/2.6.0/gems/railties-6.0.0.rc2/lib/rails/engine.rb:711:in `_all_load_paths': wrong number of arguments (given 0, expected 1) (ArgumentError)

Expected behavior
It wouldn't throw an error.
Additional information
In 5.2.3, _all_load_paths was defined without a parameter: https://github.com/rails/rails/blob/v5.2.3/railties/lib/rails/engine.rb#L701
In 6.0.0.rc2, it has a parameter: https://github.com/rails/rails/blob/v6.0.0.rc2/railties/lib/rails/engine.rb#L711
The change occurred with https://github.com/rails/rails/commit/668673f7793be1ce318a32bb622ed411029d00a9
#1009 should fix this issue.

I can confirm this error.

@connorshea the PR has been merged :). 🍾

Can this issue be closed now?

Yup, this can be closed now.


We do not currently have any sles12 s390x machines tagged with "test"

At the moment we run the systemtests on sles12 as this has a suitable version of the libffi library available (https://github.com/AdoptOpenJDK/openjdk-infrastructure/issues/19). At present none of those machines has a a tag of test so I cannot use that tag to run the systemtest jobs. If I leave the tag off I end up with things potentially running on master which doesn't work well at all as it doesn't have make installed. I could use build that would stop the other platforms from using the dedicated test machines, so that's not a sensible solutionest either. For now I've set the jobs to use !hg which knocks out three machines including master and is adequate until we get a sles12/s390x box tagged with test
See also the work item about machines tags: https://github.com/AdoptOpenJDK/openjdk-infrastructure/issues/93

@gdams We just need a new box right?

@karianna getting a "new" box on s390x can be slightly difficult ;) I'm happy to look at splitting the boxes between build and test

@gdams - We can (and should) timeshare the rarer boxes but if we can source more of them that would be good in the long term as we'll be building and testing so many different versions (every 6 months a new release).

Yep obviously happy to share, but at the moment I think there's only the one zlinux box that can run the executables we produce so it could become a bottleneck

@sxa555 are the Ubuntu boxes not going to work then? I was under the impression that we were now building openjdk binaries using Ubuntu 16.04?

Doesn't work out of the box on 16.04, no - it still looks for libffi.so.4 whereas Ubuntu 16.04 has libffi.so.6.0.4. IIRC you can symlink them together and get it working but that's probably not the sensible option.

Apologies, I had not even seen this issue (prior to creating #85).  @tellison if you like, you can close 85 as a duplicate.

I have added a note on tests/309, that we are unable to run system or openjdk_regression tests against the openjdk8-openj9 release 0.8 candidate build for s390x_linux at this time as we do not have a test machine for this platform.

@smlambert you do now :) https://ci.adoptopenjdk.net/computer/test-marist-ubuntu1604-s390x-1/

Awesome! thanks @gdams

closing issue for now

The OpenJ9 are happy on there although our latest released HotSpot build does not. Somewhat worrying it would appear that the HotSpot (Or zero!) VM crashes when you try to run it on that Ubuntu machine at the moment. That'll probably need another issue raised ...


Improve stability of CMake generator selection

This change addresses item #512
This changes behavior and stability of the extension
The following changes are proposed:

Replaces the CMake generator check from callback by previously CMake generator check and provide it as variable to the driver

The purpose of this change
Issue #512 reports that the extension crashes completely if there was a generator selection problem.
The cmake generator is checked at start of the cmake client when the cmake server protocol requires the information. If there is no useable build system (generator), then there cmake-server client throws an error. But there is no way to return this error into the cmake-server-driver instance. The driver instance is broken, and cmake-tools does not know it and will not create a new instance.
The simplest solution was to move the generator selection to the cmake-tools context so that the driver does not have to select the generator. It only uses it like other build information.
This kind of error is only possible in cmake-server-api driver, legacy driver and file-api driver need the generator before executing the cmake configure step.
Additional information

This PR extracts some commits from my big PR #707 and #720  to improve stability of generator selection.

#707 is about ready to go, if you can respond to my feedback, we can get that one committed so there will be less churn to review in this PR.

Should also address #641


Fix for appsody init incubator-index/node-red none

Describe the bug
Recommended syntax fails.
To Reproduce
Steps to reproduce the behavior:

Install Docker
Install
Launch appsody init incubator-index/node-red none
See error

% appsody init incubator-index/node-red none
[Error] Repository incubator-index is not in configured list of repositories

However, appsody list does list incubator  	node-red.

REPO        	ID                       	VERSION  	TEMPLATES        	DESCRIPTION
experimental	java-spring-boot2-liberty	0.1.11   	*default         	Spring Boot on Open Liberty & OpenJ9 using Maven
experimental	nodejs-functions         	0.1.6    	*simple          	Serverless runtime for Node.js functions
experimental	quarkus                  	0.2.2    	*default         	Quarkus runtime for running Java applications
experimental	rocket                   	0.1.0    	*simple          	Rocket web framework for Rust
experimental	rust                     	0.1.4    	*simple          	Runtime for Rust applications
experimental	vertx                    	0.1.4    	*default         	Eclipse Vert.x runtime for running Java applications
*incubator  	java-microprofile        	0.2.21   	*default         	Eclipse MicroProfile on Open Liberty & OpenJ9 using Maven
*incubator  	java-spring-boot2        	0.3.20   	*default, kotlin 	Spring Boot using OpenJ9 and Maven
*incubator  	kitura                   	0.2.3    	*default         	Runtime for Kitura applications
*incubator  	node-red                 	0.1.0    	*simple          	Node-RED runtime for running flows
*incubator  	nodejs                   	0.3.0    	*simple          	Runtime for Node.js applications
*incubator  	nodejs-express           	0.2.10   	scaffold, *simple	Express web framework for Node.js
*incubator  	nodejs-loopback          	0.1.8    	*scaffold        	LoopBack 4 API Framework for Node.js
*incubator  	python-flask             	0.1.6    	*simple          	Flask web Framework for Python
*incubator  	starter                  	0.1.1    	*simple          	Runnable starter stack, copy to create a new stack
*incubator  	swift                    	0.2.3    	*simple          	Appsody runtime for Swift applications

Expected behavior
Successfully initialized Appsody project with the incubator/node-red stack and no template.
Actual behaviour
Error with

% appsody init incubator-index/node-red none
[Error] Repository incubator-index is not in configured list of repositories

Fix
Launch appsody init incubator-index/node-red none instead
Environment Details (please complete the following information):

OS: macOS 10.15.2 (19C57)
Browser: Safari 13.0.4 (156<IP_ADDRESS>.3)

If applicable please specify:

CLI version: appsody 0.5.3
Docker version 19.03.5, build 633a0ea

@rei-vilo To initialise a new project with a stack, you would run appsody init <repo>/<stack>. So in your case, you would run appsody init incubator/node-red none, as the node-red stack is under the incubator repo, rather than incubator-index

Closing as this is a non-issue.


when i set schema,it goes wrong

Take only 300 person-item data for experiments, set the meta path to person-item-person, the number of walks and length are the default values, but this will give an error
line 56 in main.py
iy = vocab [y] .index KeyError: '1006114'
I printed "all_walks" , found that it did not walk to this node '1006114'
Is there something wrong with me?Looking forward to your reply

Because this may be the case:
Some nodes in G cannot be reached when walking along the specified meta path, so this method generate_vocab in utils.py, the vocab generated according to the number of node occurrences in all_walks, does not include all the nodes in G

I had also met the same problem  as you found @yathe

may be the vacab need to be generated from all nodes?  @

My modification way is  in 'generate_vocab':
One more parameter ‘all_nodes’ was passed, and the following code was added.
for i in all_nodes:         if i not in raw_vocab.keys():             raw_vocab[i] = 0
When generating vocab, assign a value of 0 to the nodes that did not walk.
I don’t know if it is not suitable for this modification, and the effect is not very good.
@wuqianliang

My modification way is in 'generate_vocab':
One more parameter ‘all_nodes’ was passed, and the following code was added.
for i in all_nodes:
        if i not in raw_vocab.keys():
            raw_vocab[i] = 0

When generating vocab, assign a value of 0 to the nodes that did not walk.
I don’t know if it is not suitable for this modification, and the effect is not very good.
@wuqianliang

this code part used to get neighborhood of node i on edge type r  over  some walk paths. So vocab was need to generate from walks only.

thank you very much!
I still have a question, is it impossible to get the embbeding of the nodes that have not been walked?
@wuqianliang

thank you very much!
I still have a question, is it impossible to get the embbeding of the nodes that have not been walked?
@wuqianliang

according formula (6),  only "bi"  base embedding part for nodes that have not been walked

Thank you very much for your answer! @wuqianliang

thank you very much!
I still have a question, is it impossible to get the embbeding of the nodes that have not been walked?
@wuqianliang

need to modify code according to formula (13)  , if there is unobserved data in test dataset.
this pytorch code  still transductive.

maybe i want to ask how to set the number of information aggregation layers ? @wuqianliang


Place scalatest framework jar in its own classloader

Closing the ManagedClassLoader generated by test can cause nonlocal
effects because the jdk shares some JarFile resources across multiple
URLClassLoaders. As a result, if one classloader is trying to load a
resource and the classloader is closed, it might cause the resource
loading to fail (see https://github.com/sbt/sbt/issues/5262). This can
be fixed by moving the scalatest framework jar (and its dependencies)
into an additional classloader layer that sits between the scala library
loader and the rest of the test dependencies.
In addition to adding the new layer, I reworked the
ReverseLookupClassLoader to use its dependent classloader to find
resources that may below it in the classloading hierarchy rather than
constructing an entirely new classloader for resources.
After this change, I was able to run test in the repro project:
https://github.com/rjmac/sbt-5262 1000 times with no failures. Note that
the repro is sensitive to the jdk used. I could not reproduce with jdk11
but I could typically induce a failure within 20 or so runs with jdk8.
I benchmarked this change with
https://github.com/eatkins/scala-build-watch-performance and performance
was roughly the same as 1.3.4 with turbo mode and about 200-250ms faster
in non-turbo mode (which can be explained by the time to load the
scalatest classes).

Should fix #5262.

Thanks for looking into this.


As an admin, I want to include my company's branding

This issue is for a: (mark with an x)
[ ] bug report -> please search issues before submitting
[x] feature request
[ ] documentation issue or request
[ ] regression (a behavior that used to work and stopped in a new release)

Description

As an admin, I want to include my company's branding on the Splash page & the chat page so that I can make clear it's purposed specifically for my brand

Expected/desired behavior

[ ] Should be able to upload .png (or .jpg) for Splash Page
[ ] Should be able to upload .png (or .jpg) for top left corner of Chat conversation

Mention any other details that might be useful

Mostly needs better documentation on how to do it - the ability is there in the front end, just needs to be documented on how to customize, I think. And maybe slicker to include images that don't look wonky.


Add write

Are there any issues addressed by this pull-request?
Name them here as a comma-sperated list of short-hashes.
What are you doing in this pull-request in general?
Describe the general improvement and changes you propose and why you are doing so.
What are possible side-effect?
Can you already imagine side-effects that could accour in the long-run?
Did you write tests and what are you testing?
What do you test about your new code?

canceled


Fix multiple typos in claim types and values in whats-new-active-directory-federation-services-windows-server.md

All claim types and values within "How to choose extra auth providers in 2019" must start with "http://" instead of "https://".
This was requested before at https://github.com/MicrosoftDocs/windowsserverdocs/pull/6920 (closed due to possibility of being out of date - it's still an issue, though).

@microsoft-github-policy-service agree

@robinharwood, @Xelu86
Can you review the proposed changes?
#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team


noImplicitReturns does not take account of a never return

TypeScript Version:  2.5.2
Code
function foo(): never {
    throw new Error()
}

function bar(): number {
    if (Math.random() > 0.5)
        return 1;

    foo();
    // compiler should realise we can't get here.
}

Expected behavior:
Compiles without warnings when compiled with --noImplicitReturns
Actual behavior:
error TS7030: Not all code paths return a value.

If we did this, every single expression statement to a function call would need to tie into the control flow graph which would likely be prohibitively expensive, but we should discuss it anyway.

@rbuckton started looking into expanding flow control analysis to allow it to operate for throw expressions in #18798, so we're already looking into it.

@bterlson mentioned a similar issue, wanting to be able to use process.exit(), but I don't think never is the correct type for this case.

This is a duplicate of https://github.com/Microsoft/TypeScript/issues/10470. The main issue really here is how these two features are implemented. implicit return checks happen earlier in the binder. where as control flow analysis happens later on when we are checking. merging the two is not a trivial task.

Automatically closing this issue for housekeeping purposes. The issue labels indicate that it is unactionable at the moment or has already been addressed.

Is there a remaining open issue to track this? If not, should there be? I realize it's hard to implement, but maybe it's worth keeping open as a request? (#10470 has also been closed.)

@ethanresnick We'd prefer that open issues be actionable rather than serve as an infinite-scroll TODO list. Issues don't need to be open for us to be able to see activity on them


[Bug]: OSD Integration Tests: Workflow Check and OpenSearch Validation

Describe the bug
The integ test workflow for OpenSearch Dashboards requires OpenSearch to be full up and running before running tests through OpenSearch Dashboards. Without OpenSearch cluster validation the integ tests are sometimes flaky and fail on that specific OSD component
Sample Error
2023-07-12 23:20:46 INFO     Pinging http://localhost:5601/api/status

2023-07-12 23:20:46 INFO     Service not available, yet

2023-07-12 23:20:56 INFO     Sending SIGKILL to PID 219

2023-07-12 23:20:56 INFO     Process killed with exit code 1

2023-07-12 23:20:56 INFO     Sending SIGKILL to PID 240

2023-07-12 23:20:56 INFO     Process killed with exit code None

Error log: https://ci.opensearch.org/ci/dbc/integ-test-opensearch-dashboards/2.9.0/6382/linux/x64/tar/test-results/3680/integ-test/customImportMapDashboards/with-security/stdout.txt
This was shown up for customImportMapDashboards during the 2.9.0 release where customImportMapDashboards failed  and upon re-run passed the next time.
To reproduce
This is flaky but should show when running the integ test workflow for OSD components.
Sample Failed build:
https://build.ci.opensearch.org/blue/organizations/jenkins/integ-test-opensearch-dashboards/detail/integ-test-opensearch-dashboards/3682/pipeline/
Expected behavior
No response
Screenshots
If applicable, add screenshots to help explain your problem.
Host / Environment
No response
Additional context
No response
Relevant log output
No response

[Triage] This needs some deep because the OSD without security plugin is able to connect to OS cluster, which mean the OS cluster has also disabled security plugin during without-security test.
We need some logs from the failure which we can pinpoint which part of the cluster deployment is not properly setup, in order to raise 401 issues during OSD integTest for multiple plugins.

The Issue could be solved once the Build workflow is integrated with Validation Workflow. And the Integration tests are run only for the builds that pass the Validation which usually includes spinning up the OS and OSD cluster.
https://github.com/opensearch-project/opensearch-build/issues/3441

Resolved by https://github.com/opensearch-project/opensearch-build/issues/4424 . The given artifacts are now validated first, if the cluster successfully comes up for OS and OSD Integ tests are triggered.


Typescript error when using the .attr modifier of v-bind

Version
3.2.30
Reproduction link
github.com
Steps to reproduce

Clone the repo
npm i
try to build it with npm run build
remove the .attr modifier from the HelloWorld component and it will build successfully

What is expected?
I expect the build to finish successfully
What is actually happening?
Build throws an error saying "error TS1003: Identifier expected." at the start of the .attr modifier

That would have to be solved in vue-tsc (Volar). You can open an issue here: https://github.com/johnsoncodehk/volar/issues


how to use rate limit?

How to use rate limit in Reconftw?

https://github.com/six2dez/reconftw#general-options


[BUG] Missing cancelation token for MRTK.Rest

Describe the bug
While loading a Set of 12 images and then switching to another UI -> there is no possibility to cancel the load with MRTK.Rest!
To reproduce

Setup Unity Project (any version) + MRTK Foundation package ( any package even on v 2.7.3)
Add a custom class to load many images in a Task/Unitask with a cancelation token.  E.g.: Rest.Get()
await Task.WhenAll() - alternatively, use UniTask.WhenAll() for UniTasks
Cancel load with cancelation token
Observe - Task.WhenAll() is still waiting.

Expected behavior
MRTK.Rest missing cancelation token. Rest should accept cancelation token for all methods: Get, Post, Put, Delete
Your setup (please complete the following information)

Unity Version 2020.3.16f1
MRTK Version v 2.7.3.

Target platform (please complete the following information)

HoloLens
HoloLens 2
Android

@keveleigh
would you be able to add it?


feat: adding explainer guide for open source devs

PR Checklist

[ ] Addresses an existing open issue: fixes #21
[ ] That issue was marked as accepting prs
[ ] Steps in CONTRIBUTING.md were taken

Overview

This is a work in progress. I started to write an explainer. Opening a Draft WIP to reflect my progress

Thanks @CBID2! I'll take a look at your comments. I left this in draft because it was just a huge brain dump of all my thoughts. I plan to make it more consumable. Just the weird way my brain is wired...that I need to do a brain dump first and then iprove.

Thanks @CBID2! I'll take a look at your comments. I left this in the draft because it was just a huge brain dump of all my thoughts. I plan to make it more consumable. Just the weird way my brain is wired...that I need to do a brain dump first and then improve.

You're welcome @blackgirlbytes! :) I figured that out too as soon as saw the last three blank sections hehe. 😆  What I've done is write the guides in Google Docs and then add them to a markdown file. :)


Bump react-native to 0.73.1, expo to 50

Couldn't get 0.73.0 to work with Expo 49, which was expected. Some changes to Podfile config and such seems to be handled by internal Expo plugins, and we'd need to replicate that to make it work.
So I upgraded to Expo 50 beta, and upgraded all expo packages to @next tags for compat. Thankfully Expo has good npm hygiene!
Steps to get this set up on your machine:

Upgrade to Java 17 using brew or whatever you've used before
I nuked Android Studio, made sure this box was checked, and pointed Gradle at Java 17
Run yarn nuke (new script)
Then yarn && yarn prebuild

For reference:

RN upgrade guide
RN upgrade helper
Expo 50 beta announcement

Whelp, here goes nothing


Performance improvements

Primarily reducing reflection usage on things that happen per tick

Thanks for the input, this also has fixes that need to be in dev. Pushing out new build for testers in Discord soon.


Application is not available

Tested in Open shift developer sandbox.
Going the github add way, you tell in the video.
Also tested the repo with a local build in minikube,
i got an Internal Server Error from the service.
No glue why. What kind of information more do you need?

Thanks for being patient, and thanks for finding this problem.
On Sun, Aug 29, 2021 at 10:07 AM Jan @.***> wrote:

Tested in Open shift developer sandbox.
Going the github add way, you tell in the video.
Also tested the repo with a local build in minikube,
i got an Internal Server Error from the service.
No glue why. What kind of information more do you need?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/DonSchenck/qotd-python/issues/2, or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABGVCZXAUJSPC4JEQ57SORTT7I5IXANCNFSM5DAI2K7A
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

The port number is wrong, but fixing that doesn't seem to work. Something
else must be wrong.
I'll stay after this until it's working.

Thanks for being patient, and thanks for finding this problem.
On Sun, Aug 29, 2021 at 10:07 AM Jan @.***> wrote:

Tested in Open shift developer sandbox.
Going the github add way, you tell in the video.
Also tested the repo with a local build in minikube,
i got an Internal Server Error from the service.
No glue why. What kind of information more do you need?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/DonSchenck/qotd-python/issues/2, or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABGVCZXAUJSPC4JEQ57SORTT7I5IXANCNFSM5DAI2K7A
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

Jan --
Something is weird. I have it building and working fine on my local
machine, but when I build it on OpenShift it runs but doesn't serve up any
data. I'll stay on this today.
-- Don
On Sun, Aug 29, 2021 at 8:23 PM Don Schenck @.***> wrote:

The port number is wrong, but fixing that doesn't seem to work. Something
else must be wrong.
I'll stay after this until it's working.

Thanks for being patient, and thanks for finding this problem.
On Sun, Aug 29, 2021 at 10:07 AM Jan @.***> wrote:

Tested in Open shift developer sandbox.
Going the github add way, you tell in the video.
Also tested the repo with a local build in minikube,
i got an Internal Server Error from the service.
No glue why. What kind of information more do you need?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/DonSchenck/qotd-python/issues/2, or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABGVCZXAUJSPC4JEQ57SORTT7I5IXANCNFSM5DAI2K7A
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

Maybe a problem with the newest Python 3.8 image? Because i got the internal server error also on my local machine with the newest Python 3.8 image.

There is a bug in app.py; the response type should be "text/plain".
I'm making the changes now.
On Mon, Aug 30, 2021 at 9:12 AM Jan @.***> wrote:

Maybe a problem with the newest Python 3.8 image? Because i got the
internal server error also on my local machine with the newest Python 3.8
image.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/DonSchenck/qotd-python/issues/2#issuecomment-908331440,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABGVCZQF7YATLQ6I7GEL7LTT7N7U7ANCNFSM5DAI2K7A
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

Well, I fixed THAT issue, but now it won't run in OpenShift. It DOES run on
my local machine now.
On Mon, Aug 30, 2021 at 9:23 AM Don Schenck @.***> wrote:

There is a bug in app.py; the response type should be "text/plain".
I'm making the changes now.
On Mon, Aug 30, 2021 at 9:12 AM Jan @.***> wrote:

Maybe a problem with the newest Python 3.8 image? Because i got the
internal server error also on my local machine with the newest Python 3.8
image.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/DonSchenck/qotd-python/issues/2#issuecomment-908331440,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABGVCZQF7YATLQ6I7GEL7LTT7N7U7ANCNFSM5DAI2K7A
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

Jan --
Can you send me a link to the video to which you are referring? The
written instructions that I created do not use the "git add" way.
Also; If you use the "Dockerfile" way to add the app to your project, that
will work.
-- Don
On Mon, Aug 30, 2021 at 10:06 AM Don Schenck @.***> wrote:

Well, I fixed THAT issue, but now it won't run in OpenShift. It DOES run
on my local machine now.
On Mon, Aug 30, 2021 at 9:23 AM Don Schenck @.***> wrote:

There is a bug in app.py; the response type should be "text/plain".
I'm making the changes now.
On Mon, Aug 30, 2021 at 9:12 AM Jan @.***> wrote:

Maybe a problem with the newest Python 3.8 image? Because i got the
internal server error also on my local machine with the newest Python 3.8
image.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/DonSchenck/qotd-python/issues/2#issuecomment-908331440,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABGVCZQF7YATLQ6I7GEL7LTT7N7U7ANCNFSM5DAI2K7A
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

Hi Don,
now it works locally and also on openshift build with the Dockerfile. I only have to fix the service to port 10000.
Openshift seems not to use the port under routing at creation time. i edit the service after creation.
not shure but i thougt i have seen your repo url in this video https://www.youtube.com/watch?v=oPLQs-lAAYk&t=2464s
to long to it watch again ;-)
a liitle bug :-) it sends only "qotd" not the quote
greets

test once again the github way on openshift. strange. because the pod works. i got it local with curl.
I edit the service the same way like before, but i got "the service is not available"
anyway
thx a lot for fast support

Hmmmm ... Lemme watch the video and see what's going on.
Thanks for pointing out my mistakes; Now I can fix them.
On Mon, Aug 30, 2021 at 1:48 PM Jan @.***> wrote:

test once again the github way on openshift. strange. because the pod
works. i got it local with curl.
I edit the service the same way like before, but i got "the service is not
available"
anyway
thx a lot for fast support
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/DonSchenck/qotd-python/issues/2#issuecomment-908553499,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABGVCZU6WI7EDCJJKZEEGPLT7O75ZANCNFSM5DAI2K7A
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

Setting aside the video, I strongly suggest using THIS:
Learn Kubernetes using Red Hat Developer Sandbox for OpenShift | Red Hat
Developer
https://developers.redhat.com/developer-sandbox/activities/learn-kubernetes-using-red-hat-developer-sandbox-openshift
On Mon, Aug 30, 2021 at 2:00 PM Don Schenck @.***> wrote:

Hmmmm ... Lemme watch the video and see what's going on.
Thanks for pointing out my mistakes; Now I can fix them.
On Mon, Aug 30, 2021 at 1:48 PM Jan @.***> wrote:

test once again the github way on openshift. strange. because the pod
works. i got it local with curl.
I edit the service the same way like before, but i got "the service is
not available"
anyway
thx a lot for fast support
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/DonSchenck/qotd-python/issues/2#issuecomment-908553499,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABGVCZU6WI7EDCJJKZEEGPLT7O75ZANCNFSM5DAI2K7A
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.


build: Bump Python version TDE-1077

Motivation
Use a strict version string to make sure we're running with the same
version across the board.
Modification
Use Python 3.10.12.
Checklist

[ ] Tests updated (N/A)
[ ] Docs updated (N/A)
[x] Issue linked in Title

Not necessary.


Better document dependencies

Currently, building for Linux requires you link libraries.  These are undocumented which means you'll just have to compile, receive errors, install libraries and then try again.

afaict (and this comes from my luarocks package, which you can use as an example if you want) that just means having gtk 3 installed.
On ubuntu the package you'd want is libgtk-3-dev.
The cflags/ldflags can be gotten from pkg-config, like so:
pkg-config --cflags gtk+-3.0
pkg-config --libs gtk+-3.0

Thanks. This is documented in devel.


vdk-heartbeat: null datetime conversion fix

We've noticed an occasional error occurs, applying the stack trace:
File "/opt/buildenv/lib/python3.7/site-packages/vdk/internal/heartbeat/
job_controller.py", line 383, in check_job_execution_finished
self._datetime_from_iso_format(str(e["end_time"])) for e in
execution_list
TypeError: '>' not supported between instances of 'NoneType' and
'datetime.datetime'
The error seems to reproduce in case execution end_time is not yet
populated, and max() is attempting to compare datetime with NoneType.
The fix includes filtering out any empty end_times, so that we rely on
statuses and end_times populated only.
A broader Exception is added for handling during datetime conversion,
like a preventive step.
Testing done: did retrieve the Execution API response, did reproduce
same TypeError error via local code snippet, then verified the newly
introduced fix applied is operational.
Signed-off-by: ikoleva<EMAIL_ADDRESS>

Please add a unit test. It's a good idea to add a test(s) that verifies the bug is fixed (they should fail without the fix) -this way
A) we have better confidence in the fix
B) as bugs tend to resurface we have a regression check to make sure they do not.

Please add a unit test. It's a good idea to add a test(s) that verifies the bug is fixed (they should fail without the fix) -this way
A) we have better confidence in the fix
B) as bugs tend to resurface we have a regression check to make sure they do not.

We have a unit test, that failed - so I did rework and document the workflow considered,
see https://github.com/vmware/versatile-data-kit/pull/813#discussion_r854317775
Or do you have something else in mind?


Update ayatana datetime & some OTA-less Lomiri things

Description of changes
Some smaller updates not associated with any big OTA release.

ayatana-indicator-datetime: 24.1.0 was still WIP & borked when we merged this, 24.2.0 has now obsoleted the patches.
lomiri.lomiri-ui-toolkit: Translations, addressing some build warnings & failures
lomiri.lomiri-system-settings-unwrapped (and the wrapped version): Translations, a switch to enable the system dark mode (untested)

Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[x] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
24.05 Release Notes (or backporting 23.05 and 23.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

@ofborg build lomiri.lomiri-system-settings.passthru.tests nixosTests.lomiri

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

27 packages built:

ayatana-indicator-datetime
ayatana-indicator-session
deltatouch
libayatana-common
lomiri.content-hub
lomiri.content-hub.dev
lomiri.content-hub.examples
lomiri.lomiri
lomiri.lomiri-indicator-network
lomiri.lomiri-indicator-network.dev
lomiri.lomiri-indicator-network.doc
lomiri.lomiri-push-qml
lomiri.lomiri-session
lomiri.lomiri-system-settings
lomiri.lomiri-system-settings-security-privacy
lomiri.lomiri-system-settings-unwrapped
lomiri.lomiri-system-settings-unwrapped.dev
lomiri.lomiri-terminal-app
lomiri.lomiri-ui-extras
lomiri.lomiri-ui-toolkit
lomiri.lomiri-ui-toolkit.dev
lomiri.lomiri-url-dispatcher
lomiri.lomiri-url-dispatcher.dev
lomiri.morph-browser
lomiri.qtmir
lomiri.qtmir.dev
lomiri.telephony-service

New experimental dark mode switch also works.

The only affected package I don't maintain is deltatouch, so I checked it really quickly.

Seems to launch fine.


Mismatched ZFS versions cause crashes (was: coredump on predicting size when cloning from dotmesh on ubuntu 18.04)

probably because of kernel/userland mismatch

we can use modinfo -F version zfs to detect the kernel version
to get the bionic userland tools (0.7 ZoL branch) working we really need a bionic production image though...

Proposal: Have multiple ZFS toolsets in different directories, then in all zfs commands run them like this:
LD_LIBRARY_PATH=$ZFS/lib $ZFS/bin/[zpool|zfs] ...

This is needed for #519

Done!


Custom CUDA op kernel launch dimensions

Are there any kind of restrictions on the grid dimensions for custom op CUDA kernels?
Thanks

These are standard CUDA kernels, hence normal CUDA restrictions apply:
https://developer.download.nvidia.com/compute/cuda/CUDA_Occupancy_calculator.xls
And Table H.1
https://docs.nvidia.com/cuda/cuda-c-programming-guide/index.html#features-and-technical-specifications

Maximum ... of a grid of threadblocks


x/vgo: install foo/v2 as binary "foo"

If we're installing a binary with import path blah/blah/foo/v2, we should install it as foo, not v2.

What if the tool is actually called v2 (or some other vNUM)?
On a related note, how does the Go tool handle internal paths in relation to the GitHub user https://github.com/internal?
The second questions is perhaps less serious, but the first one, I currently can't see how you'd differentiate between a tool actually being called v2 from one of version 2. For say github.com/user/repo/foo/bar/v2, then bar may be a separate tool and not simply version 1 of the same tool as v2.

What if the tool is actually called v2 (or some other vNUM)?

Don't do that?
But the module path should help to disambiguate, too: perhaps a binary package in subdirectory foo/bar/v2 within a module with module path github.com/user/repo really should be named v2. The ambiguous cases occur when the module path itself ends with /v2 and the package is located at the module root.


e2e: mustgather: add missing deployer initialization

Without the deployer initialization, deployment.deployer is nil and causes the test to panic. Fix that by calling deploy.NewForPlatform().

/cherry-pick release-4.18

/retest

/close
we merged #1120
but kudos to find and fix the issue here. #1120 takes a step further and was merged only because handoff of PRs.

/close
we merged #1120
but kudos to find and fix the issue here. #1120 takes a step further and was merged only because handoff of PRs.

Thanks for handling this. much appreciated!


chore: lets automatically upgrade old stable chart repository

as its deprecated in November so move to the new URL

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To complete the pull request process, please assign jstrachan
You can assign the PR to them by writing /assign @jstrachan in a comment when ready.
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

/approve

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: jstrachan
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [jstrachan]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment


Option to disallow enabling video

I mostly use the shortcut Ctrl+D to mute & unmute.
Sometimes accidentally when muting, I press Ctrl+E, which enables my camera.
Would be great if you could add an option in the initial screen to disallow enabling video when in the call.
(This can either make the video button disabled, or hide it totally)
Thanks!

Thanks for your feedback. I'm open to ideas, but this seems a little out of scope, and I'm not sure if I'd be able to impede Google's keyboard shortcut.

Thanks for the reply @burkybang .

I'm not sure if I'd be able to impede Google's keyboard shortcut.

I was able to disable gmeet's Ctrl+E shortcut by doing the following:
function blockVideoShortcut(e) {

    if (e.ctrlKey && e.key === 'e') {
        console.log("Blocking Ctrl+E shortcut which enables camera in gmeet.");
        e.preventDefault();
        e.stopPropagation();
    }
}

document.body.addEventListener('keydown', blockVideoShortcut, true);

One simple suggestion could be that we can add a checkbox called "Disable video shortcut (Ctrl+E)" which will register the above event handler when checked. When unchecked, it can remove the event handler by:
document.body.removeEventListener('keydown', blockVideoShortcut, true);

Hii @burkybang
Would you like a PR for this?
If you think this feature called "Disable video shortcut (Ctrl+E)" is out of scope for your extension, no problem :)
I can make a fork for my use case.
Thanks again!


starting a second instance results in RPC Services not available error

Background
Attempting to run a second instance on simnet and an attempt to create a wallet for the second instance results in error as in subject
Your environment

version of lnd : 0.13.0-beta.rc5
which operating system (uname -a on *Nix) :: Ubuntu 20.04
version of btcd, bitcoind, or other backend :  btcd version 0.21.0-beta
any other relevant environment details

Steps to reproduce

Starup btcd on simnet
start first instance of lnd as below
start second instance of lnd as below
try to create a wallet for second instance as below

Expected behaviour
A wallet created for second instance just like it did for the first instance
Actual behaviour
Output of lncli --network=simnet --rpcserver localhost:10002 create
Input wallet password:
Confirm password:
Do you have an existing cipher seed mnemonic you want to use? (Enter y/n): n
Your cipher seed can optionally be encrypted.
Input your passphrase if you wish to encrypt it (or press enter to proceed without a cipher seed passphrase):
Generating fresh cipher seed...
[lncli] unable to generate seed: rpc error: code = Unknown desc = waiting to start, RPC services not available
Here is the output of ps -e  | egrep lnd
ps -ef | egrep lnd
xxxx      765316  730020  0 14:24 pts/2    00:00:00 lnd --rpclisten=localhost:10001 --listen=localhost:10011 --restlisten=localhost:8001 --configfile=/home/xxxx/.lnd/lnd.conf
xxxx      765486  730020  0 14:27 pts/2    00:00:00 lnd --rpclisten=localhost:10002 --listen=localhost:10012 --restlisten=localhost:8002 --configfile=/home/xxxx/.lnd/lnd.conf
A while later:
ps -ef | egrep lnd has only one instance running
xxxx      765316  730020  0 14:24 pts/2    00:00:00 lnd --rpclisten=localhost:10001 --listen=localhost:10011 --restlisten=localhost:8001 --configfile=/home/xxxx/.lnd/lnd.conf

Here's a bit more log of what happens after starting a second lnd instance (note: shutdown complete after a minute or so)
2021-06-16 15:38:41.683 [INF] LTND: Active chain: Bitcoin (network=simnet)
2021-06-16 15:38:41.691 [DBG] RRPC: Router RPC server successfully register with root gRPC server
2021-06-16 15:38:41.691 [DBG] VRPC: Versioner RPC server successfully registered with root gRPC server
2021-06-16 15:38:41.691 [INF] RPCS: RPC server listening on <IP_ADDRESS>:10002
2021-06-16 15:38:41.691 [DBG] RRPC: Router REST server successfully registered with root REST server
2021-06-16 15:38:41.691 [DBG] VRPC: Versioner REST server successfully registered with root REST server
2021-06-16 15:38:41.691 [INF] RPCS: gRPC proxy started at <IP_ADDRESS>:8002
2021-06-16 15:38:41.692 [INF] LTND: Opening the main database, this might take a few minutes...
2021-06-16 15:38:41.692 [INF] LTND: Opening bbolt database, sync_freelist=false, auto_compact=false
2021-06-16 15:39:41.672 [INF] LTND: Shutdown complete

operator error - closed


[Feature] Leave room

Adds the ability to leave a room from the room's overflow menu

Fixes #300

DIALOG

@ouchadam When do you plan to release this on Google Play?

https://github.com/ouchadam/small-talk/releases/tag/23%2F01%2F01.1 the release is currently rolling out!


Mobile searches not registering and Taskkill not working

browser : chromium-browser
os : linux Aarch64
device : RPi 4
config :
`
"desktop_count": 33,
"mobile_count": 23,
"load_delay": 1.5,
"search_delay": 10,
"search_url": "https://www.bing.com/search?form=QBRE&q=",
"desktop_agent": "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/<IP_ADDRESS> Safari/537.36 Edge/<IP_ADDRESS>",
"mobile_agent": "Mozilla/5.0 (Linux; Android 14; Pixel 6 Build/AP2A.240605.024) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/<IP_ADDRESS> Mobile Safari/537.36 Edge/121.0.2277.138",
"browser_path": "chromium-browser"
`
I see no difference between the pc search and mobile search windows...
Pc search works fabulously apart from lag during entering text in search bar ( need more fixes.... pls? :) )
Thnx for this wonderful piece of code!

Can you elaborate on what you mean by Taskkill not working? That might be something I can't actually fix.
As for Bing mobile not being used, I think there may not be anything to be done. You can check the pinned issues for my thoughts.
I think the simple user agent trick is not sufficient anymore.

I did a little digging and found out the os.pkill command doesn’t seem to
work… however, it seems to be resolved by replacing it with os.system and
then calling pkill in the function… since I use chromium, you might want to
add that too… so for now, I fixed it using os.system(“pkill chromium”)
Rohan K Balaji
On Wed, 20 Nov 2024 at 6:35 AM, jack-mil @.***> wrote:

Can you elaborate on what you mean by Taskkill not working? That might be
something I can't actually fix.
As for Bing mobile not being used, I think there may not be anything to be
done. You can check the pinned issues for my thoughts.
I think the simple user agent trick is not sufficient anymore.
—
Reply to this email directly, view it on GitHub
https://github.com/jack-mil/bing-rewards/issues/53#issuecomment-2487089334,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/A6CU5EE6P7H4Y4EJTPVQGDT2BPN47AVCNFSM6AAAAABROXHEUOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIOBXGA4DSMZTGQ
.
You are receiving this because you authored the thread.Message ID:
@.***>

As @Reminiscent-Fox said above, credits to him.
Copy the following in a text file and save it as Python script (.py)
import os

# Call taskkill using os.system
os.system("taskkill /F /IM msedge.exe")

Or get it here:
https://github.com/Fict513/Pkill/blob/main/Pskill.py
Instructions:

Open Edge once
Run script
Run Bing-Rewards

Or get it here:
https://github.com/Fict513/Pkill/blob/main/Pskill.py
Mobile searches now register correctly.


Scale profile picture when window is too small

I think we should set the max-width to 100% in order to scale the picture a little bit down if the view becomes to narrow.

👍


Add sync-tiers config option

Description
This PR adds a config option to the charm called "sync-tiers" which will enable the sync tiers functionality.

Merging since the integration test is expected to fail.

Just a heads up that the integration test will fail because we haven't yet promoted the latest/edge changes to the stable track.


Allow log file of job to be viewed in full-screen.

I would be nice if you could click on a button to see the raw log.  Having to view a large log file through the smaller window azkaban provides by default is sub-optimal.

I agree, or allow users to download the complete log. Are you interested in contributing a fix?

Unfortunately I don't really have the time right now.


[Enhancement] Get rid of the database readlock when updateBackendReportVersion

The update of ReportVersion has also been based on the AtomicLong. It's not necessary to have a database read lock
What type of PR is this:

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

Does this PR entail a change in behavior?

[] Yes, this PR will result in a change in behavior.
[x] No, this PR will not result in a change in behavior.

If yes, please specify the type of change:

[ ] Interface/UI changes: syntax, type conversion, expression evaluation, display information
[ ] Parameter changes: default values, similar parameters but with different default values
[ ] Policy changes: use new policy to replace old one, functionality automatically enabled
[ ] Feature removed
[ ] Miscellaneous: upgrade & downgrade compatibility, etc.

Checklist:

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

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

Bugfix cherry-pick branch check:

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

[x] 3.1
[x] 3.0
[x] 2.5
[ ] 2.4

[FE Incremental Coverage Report]
:heart_eyes: pass : 2 / 2 (100.00%)
file detail

path
covered_line
new_line
coverage
not_covered_line_detail

:large_blue_circle:
com/starrocks/system/SystemInfoService.java
2
2
100.00%
[]

[BE Incremental Coverage Report]
:heart_eyes: pass : 0 / 0 (0%)

@Mergifyio backport branch-3.1

@Mergifyio backport branch-3.0

@Mergifyio backport branch-2.5


Add jsnext build

Adds a build step for the jsnext:main which compiles all features except for modules to an es folder.  The previous compile command is now the commonjs build which ends up in the lib directory.
Fixes #103

Current coverage is 100.00%

Merging #116 into master will not affect coverage as of cec912d

@@            master    #116   diff @@
======================================
  Files            1       1
  Stmts           42      42
  Branches         0       0
  Methods          0       0
======================================
  Hit             42      42
  Partial          0       0
  Missed           0       0

Review entire Coverage Diff as of cec912d

Powered by Codecov. Updated on successful CI builds.

Coverage remained the same at 100.0% when pulling c9c0bead79198cf7067ecd2f8b36a4a820082995 on npbee:jsnext-main into 760f5014d1bb71bf052e1522e4a2ade8c65bc9a9 on reactjs:master.

@ellbee, tried my hand at the jsnext:main build.  Let me know if any troubles!

@npbee Looks good. Thanks a lot.

Thanks @npbee! If @TrySound says its good, then I'm happy to merge. I'm away from my computer for the rest of the day, but I'll publish to npm tomorrow.


Give /usr/local/share/env/ files access to baseimage functions

by changing the order of load

appears to have a bug caused by it not having cd /app 'd yet:
jq: error: Could not open file composer.lock: No such file or directory
/usr/local/share/env/45-framework: line 3: [: : integer expression expected

actually, more an issue with the other PR with a chicken and egg scenario

@andytson-inviqa would this be resolved by adding a WORKDIR /app in the PHP base image?

no, it's resolved now

Great. Then if @kierenevans is happy, I guess you can merge :)


My Vue Icon component as a Icon in UI Pro component: UDashboardSidebarLinks

Description
Hello!
Here is my example code:
import NuxtIcon from "~/components/global/NuxtIcon.vue";

<script setup lang="ts">
const links = [
  {
    id: "home",
    label: "Home",
    icon: NuxtIcon,
    to: "/",
  },
];
</script>

<template>
    ...
    <UDashboardSidebarLinks :links="links" />
    ...
</template>

I want to use my Vue icon component in the sidebar component of Vue UI Pro
How can I do that? The above option does not work.

Hi @mcandylab,
Could you possibly create a complete reproduction on Stack Blitz sharing your nuxticon.vue file?

https://stackblitz.com/edit/nuxt-icon-playground-h27odz?file=app.vue

@mcandylab, have you seen this in the documentation? https://ui.nuxt.com/getting-started/theming#custom-config - this would solve your issue of adding a custom icon. Will not work to add as component.

As a note, you don't need to add nuxt-icon to your modules, it's already installed by @nuxt/ui 😊


Detect any line ending type regardless of OS.

Mostly opening this PR to see what Travis has to say about it. I'm still getting some failing tests locally that seem unrelated to the newline issue.
But in case this is acceptable...
DCO 1.1 Signed-off-by: Joshua Clanton<EMAIL_ADDRESS>

Thanks for this, the test failures don't seem trivial so we should definitely look into having them pass, Could you also add some tests for the new helper functions please, looking for 100% coverage where we can

Just to link this to #154

@DanPurdy Sorry for the delay on this. Had a long vacation weekend. :grin:
I've pulled the latest from develop and added tests. Everything newline related passes locally (still one failure that is unrelated to these changes). And it looks like Travis approves as well.

Correction: Looks like that last failing test on my machine is newline-related after all. It's from the indentation rule, and looks a bit harder to fix than the others. Not necessarily a reason to hold this PR back. I could work on that piece separately.

@joshuacc no problem, hope you had a good time!
Thanks very much for this it's looking good to me, I think the indentation rule is heading towards a rewrite anyway due to some of the other issues that have been flagged such as #104, but by all means look into it if you'd like!
I'll have another look over this in the morning and get back to you.
Thanks again

@joshuacc this also needs develop merging into it again, we merged a few other PR's this morning.. Sorry! :smile:

Merged develop into my branch. Travis looks good.

Just run through this and tried it out, all working nicely. Thanks @joshuacc

Awesome. :+1:


[BUG] AuthorizationCodeCredential does not allow Redirect URI to be defined

Describe the bug
When utilizing AuthorizationCodeCredential to get an access token, an exception is thrown regarding the reply URL not being set.
The reply URL is set on the application registration to match the latter address. I was able to confirm that the portal is configured correctly by using a standard HTTP request on the oauth2 token endpoint - this worked correctly and I received an access token.
Expected behavior
The AuthorizationCodeCredential class should allow specification of the reply URL to use for gaining an access token. The documentation for the auth code flow here specifies that redirect_uri is a required parameter. Additionally, that documentation is referenced in the Azure SDK for .NET class documentation here.
Actual behavior (include Exception or Stack Trace)

AuthorizationCodeCredential authentication failed: A configuration issue is preventing authentication - check the error message from the server for details. You can modify the configuration in the application registration portal. See https://aka.ms/msal-net-invalid-client for details.  Original exception: AADSTS500112: The reply address 'https://replyUrlNotSet' does not match the reply address 'http://localhost:7071/api/Redirect' provided when requesting Authorization code.

   at Azure.Identity.CredentialDiagnosticScope.FailWrapAndThrow(Exception ex)
   at Azure.Identity.AuthorizationCodeCredential.<GetTokenImplAsync>d__11.MoveNext()
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd(Task task)
   at System.Threading.Tasks.ValueTask`1.get_Result()
   at System.Runtime.CompilerServices.ConfiguredValueTaskAwaitable`1.ConfiguredValueTaskAwaiter.GetResult()
   at Azure.Identity.AuthorizationCodeCredential.<GetTokenAsync>d__10.MoveNext()
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd(Task task)
   at System.Threading.Tasks.ValueTask`1.get_Result()
   at System.Runtime.CompilerServices.ValueTaskAwaiter`1.GetResult()
   at [my code]

To Reproduce
Steps to reproduce the behavior (include a code snippet, screenshot, or any additional information that might help us reproduce the issue)

Request an authorization code using the oauth2/authorize endpoint
Once the user accepts and redirects to the specified reply url, use the code to obtain an access token via AuthorizationCodeCredential

Below is the azure function used to test this scenario. The custom Authorization.GetTokenAsync function using HttpClient works while using AuthorizationCodeCredential.GetTokenAsync throws the exception. I navigate to http://localhost:7071/api/Authorize in the browser, which redirects to MSFT authorize endpoint, accept scope, and it redirects to http://localhost:7071/api/Redirect.
using System;
using System.Threading.Tasks;
using Microsoft.AspNetCore.Mvc;
using Microsoft.Azure.WebJobs;
using Microsoft.Azure.WebJobs.Extensions.Http;
using Microsoft.AspNetCore.Http;
using Microsoft.Extensions.Logging;
using System.Collections.Specialized;
using Azure.Identity;
using System.Web.Http;
using Azure.Core;
using System.Net.Http;
using System.Collections.Generic;

namespace My.Authorization.Example
{
    public static class Authorization
    {
        private static readonly string tenantId = "<my tenant id>";
        private static readonly string clientId = "<my client id>";
        private static readonly string clientSecret = "<my client secret>";
        private static readonly string redirectUri = "http://localhost:7071/api/Redirect";
        private static readonly string scope = "https://analysis.windows.net/powerbi/api/.default";

        [FunctionName("Authorize")]
        public static async Task<IActionResult> Authorize(
            [HttpTrigger(AuthorizationLevel.Anonymous, "get", Route = null)] HttpRequest req,
            ILogger log)
        {
            var queryString = System.Web.HttpUtility.ParseQueryString(string.Empty);
            queryString.Add(new NameValueCollection
            {
                { "response_type", "code" },
                { "client_id", clientId },
                { "resource", "https://analysis.windows.net/powerbi/api" },
                { "redirect_uri", redirectUri },
                { "response_mode", "query" },
                { "state", DateTime.Now.ToString("s") }
            });

            var url = $"https://login.microsoftonline.com/{tenantId}/oauth2/authorize?{queryString}";

            return new RedirectResult(url);
        }

        [FunctionName("Redirect")]
        public static async Task<IActionResult> Redirect(
            [HttpTrigger(AuthorizationLevel.Anonymous, "get", Route = null)] HttpRequest req,
            ILogger log)
        {
            try
            {
                var code = req.Query.GetString("code");
                var error = req.Query.GetString("error");
                var errorDesc = req.Query.GetString("error_description");
                var state = req.Query.GetString("state");

                //var token = await GetTokenAsync(code);
                var creds = new AuthorizationCodeCredential(tenantId, clientId, clientSecret, code);
                var token = await creds.GetTokenAsync(new TokenRequestContext(new string[]
                {
                    "https://analysis.windows.net/powerbi/api/.default"
                }));

                return new OkObjectResult("");
            }
            catch (Exception e)
            {
                log.LogError(e, "Failed to authorize with authorization code");
                return new InternalServerErrorResult();
            }
        }

        private static async Task<string> GetTokenAsync(string code)
        {
            using var client = new HttpClient();
            var url = $"https://login.microsoftonline.com/{tenantId}/oauth2/token";
            var res = await client.PostAsync(url, new FormUrlEncodedContent(new Dictionary<string, string>
            {
                { "client_id", clientId },
                { "scope", scope },
                { "code", code },
                { "redirect_uri", redirectUri },
                { "grant_type", "authorization_code" },
                { "client_secret", clientSecret }
            }));
            var content = await res.Content.ReadAsStringAsync();
            var token = System.Text.Json.JsonSerializer.Deserialize<Dictionary<string, string>>(content);
            return token["access_token"];
        }
    }

    public static class QueryCollectionExtensions
    {
        public static string GetString(this IQueryCollection collection, string key)
        {
            return collection.TryGetValue(key, out var val) ? val.ToString() : null;
        }
    }
}

Environment:

Name and version of the Library package used: Azure.Identity 1.4.0
Hosting platform or OS and .NET runtime version (dotnet --info output for .NET Core projects): Windows 10 .NET Core 3.1
IDE and version : Visual Studio 16.10.0

Thank you for your feedback.  Tagging and routing to the team members best able to assist.


Tensorflow install breaks curl on Ubuntu

Please make sure that this is a build/installation issue. As per our GitHub Policy, we only address code/doc bugs, performance issues, feature requests and build/installation issues on GitHub. tag:build_template
System information

OS Platform and Distribution (e.g., Linux Ubuntu 16.04): Ubuntu 18.04 LTS
Mobile device (e.g. iPhone 8, Pixel 2, Samsung Galaxy) if the issue happens on mobile device:
TensorFlow installed from (source or binary):
TensorFlow version: 1.15
Python version: 3.6.7
Installed using virtualenv? pip? conda?: Virtualenv/pip
Bazel version (if compiling from source):
GCC/Compiler version (if compiling from source):
CUDA/cuDNN version:
GPU model and memory: NVidia 640

Describe the problem
Rasa install of Tensorflow 1.15 causes a Ubuntu dependency error which prevents "curl" from installing, which silently breaks the iDrive backup system.
The underlying problem seems to be that Tensorflow tries to build a modified "curl" with support for some Google remote file system. See this Tensorflow mod to Curl:
https://github.com/tensorflow/tensorflow/commit/bb890ea5fa4c8a2100a295e93c5bf37b3c88b55a
That would be fine if the modified "curl" was private to the Tensorflow environment, but somehow the nonstandard version of "curl" or "libcurl" got installed in the Ubuntu system. This broke the Ubuntu package dependency system, and now a standard "curl" cannot be installed. This, in turn, broke things which depend on "curl" being present, such as iDrive backups.
Details here: https://ubuntuforums.org/showthread.php?t=2435412
Also see: https://github.com/RasaHQ/rasa/issues/5104

What do you mean by "rasa install"?
Standard tensorflow pip package installations should have no interactions with curl/libcurl.

Closing because this is an unsupported installation method/environment for TF.
This is likely due to the installer/environment.


Wrong UI behavior when presenting chat via makeScreen(.modal) using SwiftUI

y offset for input field is 2 times larger than height of the keyboard
Input field located in the middle of scroll view and falls into place without animation when typing begins
To reproduce the problem just create new template iOS project with SwiftUI selection and add pod JivoSDK
It repeats every time the keyboard appears
import SwiftUI
import JivoSDK

final class ExampleViewModel: ObservableObject {
  init() {
    Jivo.session.setup(
      widgetID: "add id here",
      clientIdentity: .anonymous
    )
  }
}

@main
struct ExampleApp: App {
  @StateObject private var viewModel = ExampleViewModel()
  var body: some Scene {
    WindowGroup {
      Jivo.display.makeScreen(.modal)
    }
  }
}

Xcode version: 15.2
Simulator iOS version: 17.2
Deployment target: iOS 15.0
JivoSDK version: 4.5.1

This is a critical bug. Please prioritize it accordingly. This decision will determine whether we continue using JivoChat.
Each time the user opens the chat, the layout shifts up by twice the size of the keyboard, breaking the layout. This leads to a poor first experience, as the chat appears broken.
This issue is reproducible 100% of the time in SwiftUI projects on iOS 15, 16, and 17

Hello, we are having the same issue. Did anybody figure out the solution?


How to get "handleAccept" method in Photoshop  on the parent component?

update vue-color to 0.0.10
<photoshop-picker :colors.sync="colors" @ok="onOk" @cancel="onCancel"></photoshop-picker>


Fix .coveragerc

This PR fixes the bug which the coverage of cupyx has not been measured.

LGTM!

@kmaehashi It seems you forgot to add a milestone. Can I add v5.0.0b1?

Thanks for the heads-up!


ComposedFixture: Add option to start/stop fixtures in parallel

The ComposedFixture currently starts and stops the added fixtures one at a time and this can be quite slow when there's a lot of fixtures (e.g. when emulating an entire service cluster).  It would be nice to have an option that lets this happen parallel.
This would combine well with the new NeonService dependencies feature that allow services to automatically detect when their dependencies are ready.

Implemented for neonLIBRARY-v2.8.0


fix: update integration dialogue instructions max width

TL;DR
Increased the maximum width of the dialogue content for larger screens.
What changed?
Modified the className prop of the DialogueContent component in the Integrate component. Specifically, the md:sc-max-w-2xl class was changed to md:sc-max-w-4xl, increasing the maximum width for medium and larger screens.
How to test?

Navigate to the page containing the Connect and Integrate component.
Trigger the dialogue to open.
Resize the browser window to a medium or larger screen size.
Verify that the dialogue content expands to a wider maximum width compared to before.

Why make this change?
This change was likely made to improve the user experience on larger screens by allowing more content to be displayed horizontally. The increased width can potentially reduce vertical scrolling and make better use of available screen space, especially for users with wider monitors or higher-resolution displays.

[!WARNING]
This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

#128  👈
#127
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @keeganpotgieter and the rest of your teammates on  Graphite

Merge activity

Sep 2, 3:54 AM EDT: @keeganpotgieter started a stack merge that includes this pull request via Graphite.


[#517] Issues running RC check against R15 branch - Pipeline Trigger 4.12

Addresses # 517
Description
This PR adds a pipeline trigger to concatenate the execution of the 02.A. Deploy skill bots and 02.B. Run skill test scenarios pipelines in main and releases branches.
Detailed Changes

Updated the runTestScenarios yaml adding configuration for a pipeline trigger.
Updated the default value for the DEPLOYBOTRESOURCESGUID variable to match the current pipeline name.

Testing
These images show the 02.B pipeline successfully triggered after the 02.A finishes its execution, both in main and in one of the releases branches.

Promoted to MS in PR# 542


Only last character is input when using (Unicode)Input Method

Describe the bug
Only last character is input when using (Unicode)Input Method.
When pressing F2 or doube-clicked into edit mode, it works without problem.
It seems only affected unicode input method.
To Reproduce
Steps to reproduce the behavior:

Issue gif
Used input methods: Sougou Pinyin and pre-installed Microsoft pinyin input method.
Edition
Which edition of ReoGrid do you using?

Windows Form (Winforms Demo Reogrid <IP_ADDRESS>)

Environment (please complete the following information):

OS: Windows 10
Language of OS: Chinese

Thanks! I have confirmed this bug, it should be fixed.