The 'eject' script results in an error.

When I tried to run yarn run eject, I'm got the following:
error An unexpected error occurred: "ENOENT: no such file or directory, open<EMAIL_ADDRESS>

Thanks for the report, investigating now.

huh, don't seem to be able to reproduce this, do you have a yarn-error.log?

Here's what I got from trying it again, getting a similar error for @types/node:
https://gist.github.com/DanielRosenwasser/a0a6be895c8549bad5f7109524bffe4c

Hopefully this is fixed in Yarn 18.x.x

Jeez, sorry about that - that did it! Though I still get the following at the very end.
The batch file cannot be found.
error Command failed with exit code 1.

There is no yarn-error.log, so it's probably fine. If you want to close this out, go for it.

@DanielRosenwasser no worries at all! Yarn is moving so quickly little things seem to be being patched all the time. I don't have much experience with yarn, and especially yarn on Windows, so don't think I can be much help for the issue above. I did just push a fix for yarn run test afer ejecting in 1.0.1, so make sure you update for that!


[AutoRelease] t2-redhatopenshift-2023-08-07-11407(can only be merged by SDK owner)

https://github.com/Azure/sdk-release-request/issues/4382
Recording test success
https://dev.azure.com/azure-sdk/internal/_build?definitionId=1638

issue link:https://github.com/Azure/sdk-release-request/issues/4382


EnumProperty suddenly being marked as incorrect

Type: Bug
I'm not sure if this is reproducible for others but in my VSCode which used to work now suddenly is bugged. Create test.py file and just paste this code. Same problem even after updating to latest version 1.86.1
import bpy

class StupidClass(bpy.types.PropertyGroup):
    export_format: bpy.props.EnumProperty(
        name="asdf",
        description="asdf",
        default="ASDF",
    )

And now all of a sudden VSCode underlines everything starting at name="asdf" as being incorrect "Call expression not allowed in type expression". This used to work and all of a sudden VSCode is bugged.

 It looks like you may be using an old version of VS Code, the latest stable release is 1.86.1. Please try upgrading to the latest version and checking whether this issue remains.
Happy Coding!

still the same problem after i updated to
Version: 1.86.1 (system setup)
Commit: 31c37ee8f63491495ac49e43b8544550fbae4533
Date: 2024-02-07T09:08:20.941Z
Electron: 27.2.3
ElectronBuildId: 26495564
Chromium: 118.0.5993.159
Node.js: 18.17.1
V8: <IP_ADDRESS>-electron.0
OS: Windows_NT x64 10.0.22621

Hi thank you for writing about this issue. You can see in your screenshot that the error is thrown by Pylance, so I assume this is likely not a problem with VS Code, but due to an upgrade in the Python extensions you have installed that now throw errors on the lines you mention. If you are not happy with how the error is displayed, you may file an issue directly to the Python extension you are using. This issue will be closed.

oh ok thank you very much for the clarification. sorry i'm still new to VSCode.


Update google drive extractor

Checklist:

[x] Updated extVersionCode value in build.gradle for individual extensions
[x] Updated overrideVersionCode or baseVersionCode as needed for all multisrc extensions
[x] Referenced all related issues in the PR body (e.g. "Closes #xyz")
[x] Added the isNsfw = true flag in build.gradle when appropriate
[x] Have not changed source names
[x] Have explicitly kept the id if a source's name or language were changed
[x] Have tested the modifications by compiling and running the extension through Android Studio

3 source names modified, 0 (zero) IDs explicitly kept, 10/10


"OPEN SOURCE NOTE BLOCK EDITOR"

open source note block editor huh? this is not open source. if it is "open source" you provide a dmg and exe file. if its just a .exe file, its windows only and windows only is not open source

i guess its not "open source" if you cant install it on mac

Sorry, but that doesn't seem correct! Note Block Studio is open-source. The entire source code is available here: https://github.com/OpenNBS/OpenNoteBlockStudio
There's nothing in the OSI's Definition of Open Source that requires the software in question to be available to any specific platform. There's a variety of open-source programs that are Windows-only — in fact, there's a whole Wikipedia entry dedicated to them. The platform a program is distributed to has nothing to do with it being open-source. :)
Finally, the reason why Mac distributions aren't available is that there are numerous dependencies which are Windows-only. A lot of work is being made to allow that to happen! Please follow this discussion for updates, or use this unofficial fork which has partially-working builds for a variety of platforms.

I think I took brain damage reading what smidgeondutchrabbit  wrote.. lol


吾有一術。名之曰「JS转文言」。现已支持大部分 JS 语法转换。

@LingDong- Could this be counted as a contributed tool? 😄
Project url: https://github.com/zxch3n/wenyanizer
进展

Name
Status

JS Code Compiled From Wenyan
✔

Closure
✔

Control: While/For/If/Else
✔

Object var a = {a: 0, b: 1, c: 2}
✔

Array [[[0 ,2], [2, []]]]
✔

+-*/
✔

--, ++, +=, -=, /=
✔

Distinguish a++ and ++a
✔

Wraping global object when necessary, such as Math, JSON
✔

console.log
✔

a.b = 3
✔

NewExpression
✔

Function
✔

this keyword
✔

a[b] = 3
✔

ForOfStatement
✔

Wenyan Lib
WIP

Wenyan Nested Function Call
❌

Optimize Curried Function
❌

RegExp
❌

switch
❌

bit op
❌

null undefined
❌

DebugExpression
❌

WithStatement
❌

continue
❌

debug exp
❌

ForInStatement
❌

throw try...catch...finally
❌

Modules (import, export, require)
❌

=== (will be compiled to ==)
❌

It supports medium difficulty compilation now.
The screenshot is how it compile a program that solves sudoku

@zxch3n This is so awesome. I just added it to the README. 👍

Thanks! :D

Amazing job!

wow~ ⊙o⊙，👍

fabulous!


[Bug]: Error when using SSH key to deploy from Gitea Private Repo

Error Message and Logs
I'm having the an issue when using Gitea and trying to deploy from a private repo. Works fine with Github.
-Generate SSH key pair in Coolify's Key & Token management.
-Copy public key to Gitea repository's Deploy Keys.
-Create new project in Coolify, entering Git repository URL and required details.
-Deploy
-Attempt to clone repository, resulting in SSH authentication failure.
Error message.
Starting deployment of git@gitea-fhghghf88g.<IP_ADDRESS>.sslip.io:fhhg/hhgf.git:main to localhost.
Preparing container with helper image: ghcr.io/coollabsio/coolify-helper:1.0.2.
Oops something is not okay, are you okay? 😢
Permission denied, please try again.
Permission denied, please try again.
git@gitea-fhghghf88g.<IP_ADDRESS>.sslip.io:Permission denied (publickey,password).
fatal: Could not read from remote repository.
Please make sure you have the correct access rights
and the repository exists.
Deployment failed. Removing the new version of your application.

Steps to Reproduce

Generate SSH key pair in Coolify's Key & Token management.
Copy public key to Gitea repository's Deploy Keys.
Create new project in Coolify, entering Git repository URL and required details.
Deploy
Attempt to clone repository, resulting in SSH authentication failure.

Example Repository URL
No response
Coolify Version
v4.0.0-beta.355
Are you using Coolify Cloud?
No (self-hosted)
Operating System and Version (self-hosted)
Debian GNU/Linux 12 (bookworm)
Additional Information
No response

that looks like it failed to pull teh helper from ghcr
can u first try docker logout ghcr.io

Thanks, I think i just fixed it. The port Gitea was using was missing from the ssh url.
What I did.
Under "Service Stack," click "Edit Compose File" and see what port Gitea is listening on. Mine is 22222.
You'll need to add that port to your Gitea SSH URL. Something like this:
git@gitea-gccgasdds4sdsd.3.444.232.32.sslip.io:22222/user/repo


[wait for #1394] [layer] LayerV1 cleanup from LayerNode

Remove LayerNode dependence on LayerV1.
Further, NetworkGraph dependence on LayerV1 is also removed.
Some More bugfixes in the patch:

Add initialization for the missing variables for LayerImpl class
Add missing initialization in constructor for the weight class

:memo: TAOS-CI Version: 1.5.20200925. Thank you for submitting PR #1410. Please a submit 1commit/1PR (one commit per one PR) policy to get comments quickly from reviewers. Your PR must pass all verificiation processes of cibot before starting a review process from reviewers. If you are new member to join this project, please read manuals in documentation folder and wiki page. In order to monitor a progress status of your PR in more detail, visit http://nnstreamer.mooo.com/.


Change annotation names in grid editor

Based on top of #177, merge after #177 has been merged in to develop.
Pull request checklist
Please check if your PR fulfills the following requirements:

[ ] Tests for the changes have been added (for bug fixes / features)
[ ] Docs have been reviewed and added / updated if needed (for bug fixes / features)
[ ] The Unreleased section in CHANGELOG.md has been amended to reflect the changes in this PR
[ ] Build (mvn verify) was run locally and any changes were pushed
[x] The pull request is against the correct branch (master for bug fixes, develop for new functionality)

Pull request type

Please check the type of change your PR introduces:

[ ] Bugfix
[x] Feature
[ ] Code style update (formatting, renaming)
[ ] Refactoring (no functional changes, no API changes)
[ ] Build related changes
[ ] Documentation content changes
[ ] Other (please describe):

What is the current behavior?

Annotation names (Salt namespace/Salt name) cannot be changed for existing annotations.
Issue Number: #97
What is the new behavior?

Fixes #97

Does this introduce a breaking change?

[ ] Yes
[x] No

Does this introduce new dependencies?

[ ] Yes
[ ] No

If this introduces new dependencies:

[ ] Dependencies and citation templates have been updated where necessary

Other information

Checklist for maintainers
Releases

[ ] Do NOT push the green merge button on GitHub.
Follow the latest version of the developer/maintainer docs for making releases.
[ ] License and citation information for dependencies are complete (each dependency has a folder in /THIRD-PARTY/).

Closing, as superseded by #229.


TD is appended even after paris

Describe the feature
After Paris hardfork Total difficulty is not used and it is always zero
Should move insertion to else? https://github.com/paradigmxyz/reth/blob/main/crates/stages/src/stages/total_difficulty.rs#L100
Additional context
No response

Total difficulty is used in the RPC. See https://ethereum.org/en/developers/docs/apis/json-rpc/#eth_getblockbyhash

Total difficulty is used in the RPC. See https://ethereum.org/en/developers/docs/apis/json-rpc/#eth_getblockbyhash

If this is the only place, we can check if block number is >Paris block and return zero. In general, a small thing

If this is the only place, we can check if block number is >Paris block and return zero. In general, a small thing

Yes. Let's move the append to an else block, and let's also ensure that any RPC response has #[serde(default)] / is initialized with difficulty 0

Is this still relevant? cc @rakita


Handle displaying various status conditions on providers

The status column in the providers table will currently only display the first condition in the list, and hasn't been tested with error or warning conditions. We need to double check that stuff, and possibly look at the rest of the conditions array to identify the most serious condition or display multiple conditions.
See: https://github.com/konveyor/virt-ui/blob/2bf0b914669a79553bad324759b1985bd62a8e29/src/app/Providers/components/ProvidersTable/VMware/VMwareProvidersTable.tsx#L43

+1 This will be a common theme across all of the API resources. With CAM, we have functions that short circuit & return a status when a condition is met. The critical/severe error state statuses are at the top of the function block. We should think about the best way to do this across the app.

Yep. I imagine the status condition API structure will be common across multiple API objects, so we could make a common component to consume/display that.

We effectively need to deal with categories before displaying a status type:
Condition categories:
Advisory - An advisory condition provides information that does not impact a resource’s Ready condition.
Warn - A warning condition alerts users to concerns that do not impact a resource’s Ready condition.
Error - An error condition indicates a problem that is serious enough to prevent a resource from having a Ready condition but does not indicate that the resource itself is unhealthy.
Critical - A critical condition indicates a serious problem and that the resource is not healthy.  This blocks the Ready condition.
Required - A required condition represents something that is needed to have occurred or be true in order for the resource to have a Ready condition.


Add searchbar to header

closes #558
LiveURL: https://smartfaq-search-in-header.surge.sh

It breaks search input for mobile:

For iPad I think the search input should stay in the right part, becoming progressively smaller.

as @jalbertsr says, it breaks the input field on mobile. However, only if you are logged in. When you are not logged in, it's fine:

This also closes https://github.com/kiwicom/smart-faq/issues/396 👍 I've checked and we're using <UserStatus.LoggedIn> everywhere we can.

thanks all for shipping this

It breaks search input for mobile

let's add cypress test for search on mobile, so we have covered our back here.

let's add cypress test for search on mobile, so we have cover our back here.

@jaroslav-kubicek sure, I've added #640

Search in mobile still broken

@kantord the fix is on it's way 🚂

@jalbertsr I have asked @mjancik about the specific cases, for now I would leave the layout as it is.

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Add macro_use? and update gem dependency "dry-validation", "~> 1.3"

Add support for checking that the macro is used through the method macro_use?
Updated gem dependency "dry-validation", "~> 1.3"

Thank you!

Just released 1.2.0


Updated findAllWhere(). Params sent was misused.

findAllWhere($where, $value) uses where($where) which does not work cause it expects it to be where("$where = ?")

Checking the result from Scrutinizer, I see now how it it supposed to work. Documentation somewhat misleading on usage of this function.
$this->findAllWhere("idQuestion = ?", 4);
What is the main reason why " = ?" has to be defined outside the function?

From the testsuite, two examples on usage.
Argument as single value:
https://github.com/canax/database/blob/v1.1.5/test/Database/ActiveRecordUsageTest.php#L119-L123
Argument as array and changed = to IN:
https://github.com/canax/database/blob/v1.1.5/test/Database/ActiveRecordUsageTest.php#L131-L135
Its correct this works in another manner than find(). So its not christal clear, but at the time of implementation it seemed to be the best solution.


Sam model throw a Error "cannot find tensor image_encoder.patch_embed.proj.weight" when using facebook/sam-vit-base

this is 0.6.0 example command:
$ cargo run --example segment-anything --release -- --image candle-examples/examples/yolo-v8/assets/bike.jpg --point 0.6,0.6 --point 0.6,0.55
   Compiling candle-examples v0.6.0 (/media/dev/fork/candle/candle-examples)
    Finished `release` profile [optimized] target(s) in 2.13s
     Running `target/release/examples/segment-anything --image candle-examples/examples/yolo-v8/assets/bike.jpg --point 0.6,0.6 --point 0.6,0.55`
loaded image Tensor[dims 3, 711, 1024; u8, cuda:0]
Error: cannot find tensor image_encoder.patch_embed.proj.weight
[foliage@foliage candle]$

model link: https://huggingface.co/facebook/sam-vit-base

Could you try with the current github tip? For me the command line you've put worked out of the box, or maybe you had some specific arguments to use the model from the link that you've pasted?
     Running `target/release/examples/segment-anything --image candle-examples/examples/yolo-v8/assets/bike.jpg --point 0.6,0.6 --point 0.6,0.55`
Running on CPU, to run on GPU(metal), build this example with `--features metal`
loaded image Tensor[dims 3, 711, 1024; u8]
sam_vit_b_01ec64.safetensors [00:00:41] 357.61 MiB/357.61 MiB 8.61 MiB/s (0s)mask generated in 9.02s
mask:
[[[-10.5055, -10.5055, -10.5055, ...,  -9.8610,  -9.8610,  -9.8610],
  [-10.5055, -10.5055, -10.5055, ...,  -9.8610,  -9.8610,  -9.8610],
  [-10.5055, -10.5055, -10.5055, ...,  -9.8610,  -9.8610,  -9.8610],
  ...
  [ -9.4169,  -9.4169,  -9.4169, ...,  -9.8145,  -9.8145,  -9.8145],
  [ -9.4169,  -9.4169,  -9.4169, ...,  -9.8145,  -9.8145,  -9.8145],
  [ -9.4169,  -9.4169,  -9.4169, ...,  -9.8145,  -9.8145,  -9.8145]]]
Tensor[[1, 711, 1024], f32]
iou_predictions: [[0.6909]]
Tensor[[1, 1], f32]

@LaurentMazare
sam_vit_b_01ec64.safetensors

You used the file provided by lmz/candle-sam and it worked fine, but I wanted to use the official file from facebook/sam-vit-base and it had problems, as I reported, and I didn't find any guidance on how to convert the model.
BTW:
You are using lmz/candle-sam/sam_vit_b_01ec64.safetensors, which works fine in point mode, but not in generate_masks mode.
cargo run --example segment-anything --release -- --image candle-examples/examples/yolo-v8/assets/bike.jpg --generate-masks

I have already reported this issue here.https://github.com/huggingface/candle/issues/2373

I found the relevant source code here and the problem has been solved.
https://huggingface.co/spaces/safetensors/convert/blob/main/convert.py


SDK 44 - unable to build even a basic 'expo init' project via EAS (for iOS)

Build/Submit details page URL
https://expo.dev/accounts/seetickets/projects/sdk44-test/builds/7bffc2b8-ee3a-4873-8524-44a5a5979574
Summary
Since upgrading to Expo SDK 44 every build for iOS via EAS fails during 'Run fastlane' with the following error:
** ARCHIVE FAILED **
▸ The following build commands failed:
▸ 	CompileSwiftSources normal arm64 com.apple.xcode.tools.swift.compiler (in target 'ExpoModulesCore' from project 'Pods')
▸ 	PhaseScriptExecution [CP-User]\ Generate\ Specs /Users/expo/Library/Developer/Xcode/DerivedData/sdk44test-cdacpoevfgnhvgcmpjwaipkewvah/Build/Intermediates.noindex/ArchiveIntermediates/sdk44test/IntermediateBuildFilesPath/Pods.build/Release-iphoneos/FBReactNativeSpec.build/Script-AEB7E4B2C2A6262E00C82D25FB34E8C3.sh (in target 'FBReactNativeSpec' from project 'Pods')

^ this error even occurs when trying to build basic, boiler plate app created via 'expo init'
Managed or bare?
Managed
Environment
expo-env-info 1.0.2 environment info:
System:
OS: Windows 10 10.0.19044
Binaries:
Node: 16.14.2 - C:\Program Files\nodejs\node.EXE
npm: 8.5.0 - C:\Program Files\nodejs\npm.CMD
npmPackages:
expo: ~44.0.0 => 44.0.6
react: 17.0.1 => 17.0.1
react-dom: 17.0.1 => 17.0.1
react-native: 0.64.3 => 0.64.3
react-native-web: 0.17.1 => 0.17.1
Expo Workflow: managed
Error output
From the 'Run fastlane' step:
Creating Gymfile
Gymfile created
Successfully loaded '/Users/expo/workingdir/build/Mobile Apps/React/sdk44-test/ios/Gymfile' 📄
+-----------------------+---------------------------------------------------------------------------------------------------------------------------------------------+
|                                                                  Detected Values from './Gymfile'                                                                   |
+-----------------------+---------------------------------------------------------------------------------------------------------------------------------------------+
| suppress_xcode_output | true                                                                                |
| clean                 | false                                                                                |
| scheme                | sdk44test                                                                                |
| configuration         | Release                                                                                |
| export_options        |                                                                                |
| export_xcargs         | OTHER_CODE_SIGN_FLAGS="--keychain /var/folders/97/73j93h690g9gdn54bh_zskm40000gn/T/turtle-v2-a2a245ed-453a-43b4-b8a5-ea526667b41d.keychain" |
| disable_xcpretty      | true                                                                                |
| buildlog_path         | /Users/expo/workingdir/logs                                                                                |
| output_directory      | ./build                                                                                |
+-----------------------+---------------------------------------------------------------------------------------------------------------------------------------------+
Resolving Swift Package Manager dependencies...
$ xcodebuild -resolvePackageDependencies -workspace ./sdk44test.xcworkspace -scheme sdk44test -configuration Release
▸ Command line invocation:
▸     /Applications/Xcode.app/Contents/Developer/usr/bin/xcodebuild -resolvePackageDependencies -workspace ./sdk44test.xcworkspace -scheme sdk44test -configuration Release
▸ User defaults from command line:
▸     IDEPackageSupportUseBuiltinSCM = YES
▸ --- xcodebuild: WARNING: Using the first of multiple matching destinations:
▸ { platform:iOS, id:dvtdevice-DVTiPhonePlaceholder-iphoneos:placeholder, name:Any iOS Device }
▸ { platform:iOS Simulator, id:dvtdevice-DVTiOSDeviceSimulatorPlaceholder-iphonesimulator:placeholder, name:Any iOS Simulator Device }
▸ { platform:iOS Simulator, id:1CB33FBC-3FAA-4F3E-BB0F-A9EDCAAD1259, OS:15.0, name:iPad (9th generation) }
▸ { platform:iOS Simulator, id:AFC5A58F-7FBC-4DF5-AE5A-0974346DF7B6, OS:15.0, name:iPad Air (4th generation) }
▸ { platform:iOS Simulator, id:95E4DD21-70F0-4B6F-AC94-EA4476055EEF, OS:15.0, name:iPad Pro (9.7-inch) }
▸ { platform:iOS Simulator, id:EEB18B5C-E97E-454D-A183-84ED100F8196, OS:15.0, name:iPad Pro (11-inch) (3rd generation) }
▸ { platform:iOS Simulator, id:2A156826-CB37-46EA-8ECC-8DAD52EF0F1F, OS:15.0, name:iPad Pro (12.9-inch) (5th generation) }
▸ { platform:iOS Simulator, id:CCA2D32E-96E5-44C0-8A63-13814504BDA0, OS:15.0, name:iPad mini (6th generation) }
▸ { platform:iOS Simulator, id:AE115BC2-463C-49D5-B498-8741EE92F069, OS:15.0, name:iPhone 8 }
▸ { platform:iOS Simulator, id:718EB7E9-0A7D-4F2D-8334-9FAEB4D2D7D6, OS:15.0, name:iPhone 8 Plus }
▸ { platform:iOS Simulator, id:0B5CA4B0-23A2-4D9B-ACB5-0697F287717C, OS:15.0, name:iPhone 11 }
▸ { platform:iOS Simulator, id:03B4BB90-B5D0-4877-9D66-4E5B63B5A3C5, OS:15.0, name:iPhone 11 Pro }
▸ { platform:iOS Simulator, id:95F5C092-940F-4853-850B-B1B36E8E0590, OS:15.0, name:iPhone 11 Pro Max }
▸ { platform:iOS Simulator, id:FEA2C8C1-E52B-4540-9BCD-3BBC2EDEBFF4, OS:15.0, name:iPhone 12 }
▸ { platform:iOS Simulator, id:AFEA8245-61C0-43CB-BAEA-97F1196BAF6E, OS:15.0, name:iPhone 12 Pro }
▸ { platform:iOS Simulator, id:CB92FB5B-DF81-4D07-A8F6-18224862D513, OS:15.0, name:iPhone 12 Pro Max }
▸ { platform:iOS Simulator, id:AE9F8D77-BE11-4FDB-AD3B-CA9CF749BF34, OS:15.0, name:iPhone 12 mini }
▸ { platform:iOS Simulator, id:ECE956C8-39E0-492B-9E37-0C28627D599D, OS:15.0, name:iPhone 13 }
▸ { platform:iOS Simulator, id:BC6F1D15-3ED9-40F2-BBDA-D082D5DFB738, OS:15.0, name:iPhone 13 Pro }
▸ { platform:iOS Simulator, id:B26270AC-4D5B-4F8B-AF53-15B9BE5F6A3B, OS:15.0, name:iPhone 13 Pro Max }
▸ { platform:iOS Simulator, id:AF3558D2-7ED7-4BD9-93BE-9F2C242BE18E, OS:15.0, name:iPhone 13 mini }
▸ { platform:iOS Simulator, id:0A569D77-37C2-405B-A551-23EFA0D267DB, OS:15.0, name:iPhone SE (2nd generation) }
▸ { platform:iOS Simulator, id:3F3F8FB5-2DED-483F-8134-855C1784EFC5, OS:15.0, name:iPod touch (7th generation) }
▸ resolved source packages:
$ xcodebuild -showBuildSettings -workspace ./sdk44test.xcworkspace -scheme sdk44test -configuration Release
[stderr] --- xcodebuild: WARNING: Using the first of multiple matching destinations:
[stderr] { platform:iOS, id:dvtdevice-DVTiPhonePlaceholder-iphoneos:placeholder, name:Any iOS Device }
[stderr] { platform:iOS Simulator, id:dvtdevice-DVTiOSDeviceSimulatorPlaceholder-iphonesimulator:placeholder, name:Any iOS Simulator Device }
[stderr] { platform:iOS Simulator, id:1CB33FBC-3FAA-4F3E-BB0F-A9EDCAAD1259, OS:15.0, name:iPad (9th generation) }
[stderr] { platform:iOS Simulator, id:AFC5A58F-7FBC-4DF5-AE5A-0974346DF7B6, OS:15.0, name:iPad Air (4th generation) }
[stderr] { platform:iOS Simulator, id:95E4DD21-70F0-4B6F-AC94-EA4476055EEF, OS:15.0, name:iPad Pro (9.7-inch) }
[stderr] { platform:iOS Simulator, id:EEB18B5C-E97E-454D-A183-84ED100F8196, OS:15.0, name:iPad Pro (11-inch) (3rd generation) }
[stderr] { platform:iOS Simulator, id:2A156826-CB37-46EA-8ECC-8DAD52EF0F1F, OS:15.0, name:iPad Pro (12.9-inch) (5th generation) }
[stderr] { platform:iOS Simulator, id:CCA2D32E-96E5-44C0-8A63-13814504BDA0, OS:15.0, name:iPad mini (6th generation) }
[stderr] { platform:iOS Simulator, id:AE115BC2-463C-49D5-B498-8741EE92F069, OS:15.0, name:iPhone 8 }
[stderr] { platform:iOS Simulator, id:718EB7E9-0A7D-4F2D-8334-9FAEB4D2D7D6, OS:15.0, name:iPhone 8 Plus }
[stderr] { platform:iOS Simulator, id:0B5CA4B0-23A2-4D9B-ACB5-0697F287717C, OS:15.0, name:iPhone 11 }
[stderr] { platform:iOS Simulator, id:03B4BB90-B5D0-4877-9D66-4E5B63B5A3C5, OS:15.0, name:iPhone 11 Pro }
[stderr] { platform:iOS Simulator, id:95F5C092-940F-4853-850B-B1B36E8E0590, OS:15.0, name:iPhone 11 Pro Max }
[stderr] { platform:iOS Simulator, id:FEA2C8C1-E52B-4540-9BCD-3BBC2EDEBFF4, OS:15.0, name:iPhone 12 }
[stderr] { platform:iOS Simulator, id:AFEA8245-61C0-43CB-BAEA-97F1196BAF6E, OS:15.0, name:iPhone 12 Pro }
[stderr] { platform:iOS Simulator, id:CB92FB5B-DF81-4D07-A8F6-18224862D513, OS:15.0, name:iPhone 12 Pro Max }
[stderr] { platform:iOS Simulator, id:AE9F8D77-BE11-4FDB-AD3B-CA9CF749BF34, OS:15.0, name:iPhone 12 mini }
[stderr] { platform:iOS Simulator, id:ECE956C8-39E0-492B-9E37-0C28627D599D, OS:15.0, name:iPhone 13 }
[stderr] { platform:iOS Simulator, id:BC6F1D15-3ED9-40F2-BBDA-D082D5DFB738, OS:15.0, name:iPhone 13 Pro }
[stderr] { platform:iOS Simulator, id:B26270AC-4D5B-4F8B-AF53-15B9BE5F6A3B, OS:15.0, name:iPhone 13 Pro Max }
[stderr] { platform:iOS Simulator, id:AF3558D2-7ED7-4BD9-93BE-9F2C242BE18E, OS:15.0, name:iPhone 13 mini }
[stderr] { platform:iOS Simulator, id:0A569D77-37C2-405B-A551-23EFA0D267DB, OS:15.0, name:iPhone SE (2nd generation) }
[stderr] { platform:iOS Simulator, id:3F3F8FB5-2DED-483F-8134-855C1784EFC5, OS:15.0, name:iPod touch (7th generation) }
Command timed out after 3 seconds on try 1 of 4, trying again with a 6 second timeout...
[stderr] --- xcodebuild: WARNING: Using the first of multiple matching destinations:
[stderr] { platform:iOS, id:dvtdevice-DVTiPhonePlaceholder-iphoneos:placeholder, name:Any iOS Device }
[stderr] { platform:iOS Simulator, id:dvtdevice-DVTiOSDeviceSimulatorPlaceholder-iphonesimulator:placeholder, name:Any iOS Simulator Device }
[stderr] { platform:iOS Simulator, id:1CB33FBC-3FAA-4F3E-BB0F-A9EDCAAD1259, OS:15.0, name:iPad (9th generation) }
[stderr] { platform:iOS Simulator, id:AFC5A58F-7FBC-4DF5-AE5A-0974346DF7B6, OS:15.0, name:iPad Air (4th generation) }
[stderr] { platform:iOS Simulator, id:95E4DD21-70F0-4B6F-AC94-EA4476055EEF, OS:15.0, name:iPad Pro (9.7-inch) }
[stderr] { platform:iOS Simulator, id:EEB18B5C-E97E-454D-A183-84ED100F8196, OS:15.0, name:iPad Pro (11-inch) (3rd generation) }
[stderr] { platform:iOS Simulator, id:2A156826-CB37-46EA-8ECC-8DAD52EF0F1F, OS:15.0, name:iPad Pro (12.9-inch) (5th generation) }
[stderr] { platform:iOS Simulator, id:CCA2D32E-96E5-44C0-8A63-13814504BDA0, OS:15.0, name:iPad mini (6th generation) }
[stderr] { platform:iOS Simulator, id:AE115BC2-463C-49D5-B498-8741EE92F069, OS:15.0, name:iPhone 8 }
[stderr] { platform:iOS Simulator, id:718EB7E9-0A7D-4F2D-8334-9FAEB4D2D7D6, OS:15.0, name:iPhone 8 Plus }
[stderr] { platform:iOS Simulator, id:0B5CA4B0-23A2-4D9B-ACB5-0697F287717C, OS:15.0, name:iPhone 11 }
[stderr] { platform:iOS Simulator, id:03B4BB90-B5D0-4877-9D66-4E5B63B5A3C5, OS:15.0, name:iPhone 11 Pro }
[stderr] { platform:iOS Simulator, id:95F5C092-940F-4853-850B-B1B36E8E0590, OS:15.0, name:iPhone 11 Pro Max }
[stderr] { platform:iOS Simulator, id:FEA2C8C1-E52B-4540-9BCD-3BBC2EDEBFF4, OS:15.0, name:iPhone 12 }
[stderr] { platform:iOS Simulator, id:AFEA8245-61C0-43CB-BAEA-97F1196BAF6E, OS:15.0, name:iPhone 12 Pro }
[stderr] { platform:iOS Simulator, id:CB92FB5B-DF81-4D07-A8F6-18224862D513, OS:15.0, name:iPhone 12 Pro Max }
[stderr] { platform:iOS Simulator, id:AE9F8D77-BE11-4FDB-AD3B-CA9CF749BF34, OS:15.0, name:iPhone 12 mini }
[stderr] { platform:iOS Simulator, id:B26270AC-4D5B-4F8B-AF53-15B9BE5F6A3B, OS:15.0, name:iPhone 13 Pro Max }
[stderr] { platform:iOS Simulator, id:AF3558D2-7ED7-4BD9-93BE-9F2C242BE18E, OS:15.0, name:iPhone 13 mini }
[stderr] { platform:iOS Simulator, id:ECE956C8-39E0-492B-9E37-0C28627D599D, OS:15.0, name:iPhone 13 }
[stderr] { platform:iOS Simulator, id:BC6F1D15-3ED9-40F2-BBDA-D082D5DFB738, OS:15.0, name:iPhone 13 Pro }
[stderr] { platform:iOS Simulator, id:0A569D77-37C2-405B-A551-23EFA0D267DB, OS:15.0, name:iPhone SE (2nd generation) }
[stderr] { platform:iOS Simulator, id:3F3F8FB5-2DED-483F-8134-855C1784EFC5, OS:15.0, name:iPod touch (7th generation) }
Detected provisioning profile mapping: {:"com.seetickets.sdk44test"=>"6caf0a76-df0d-4df6-a010-a07ef930a38b"}
+--------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------+
|                                                                                Summary for gym 2.185.1                                                                                |
+--------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------+
| workspace                                                    | ./sdk44test.xcworkspace                                                                                |
| scheme                                                       | sdk44test                                                                                |
| clean                                                        | false                                                                                |
| output_directory                                             | ./build                                                                                |
| output_name                                                  | sdk44test                                                                                |
| configuration                                                | Release                                                                                |
| silent                                                       | false                                                                                |
| skip_package_ipa                                             | false                                                                                |
| skip_package_pkg                                             | false                                                                                |
| export_options.method                                        | app-store                                                                                |
| export_options.provisioningProfiles.com.seetickets.sdk44test | 6caf0a76-df0d-4df6-a010-a07ef930a38b                                                                                |
| export_xcargs                                                | OTHER_CODE_SIGN_FLAGS="--keychain /var/folders/97/73j93h690g9gdn54bh_zskm40000gn/T/turtle-v2-a2a245ed-453a-43b4-b8a5-ea526667b41d.keychain" |
| build_path                                                   | /Users/expo/Library/Developer/Xcode/Archives/2022-03-22                                                                                |
| result_bundle                                                | false                                                                                |
| buildlog_path                                                | /Users/expo/workingdir/logs                                                                                |
| destination                                                  | generic/platform=iOS                                                                                |
| suppress_xcode_output                                        | true                                                                                |
| disable_xcpretty                                             | true                                                                                |
| skip_profile_detection                                       | false                                                                                |
| skip_package_dependencies_resolution                         | false                                                                                |
| disable_package_automatic_updates                            | false                                                                                |
| use_system_scm                                               | false                                                                                |
| xcode_path                                                   | /Applications/Xcode.app                                                                                |
+--------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------+
$ set -o pipefail && xcodebuild -workspace ./sdk44test.xcworkspace -scheme sdk44test -configuration Release -destination 'generic/platform=iOS' -archivePath /Users/expo/Library/Developer/Xcode/Archives/2022-03-22/sdk44test\ 2022-03-22\ 11.49.18.xcarchive archive | tee /Users/expo/workingdir/logs/sdk44test-sdk44test.log > /dev/null
› Compiling react-native Pods/glog » vlog_is_on.cc
› Compiling react-native Pods/glog » utilities.cc
› Compiling react-native Pods/glog » symbolize.cc
› Compiling react-native Pods/glog » signalhandler.cc
› Compiling react-native Pods/glog » raw_logging.cc
› Compiling react-native Pods/glog » logging.cc
› Compiling react-native Pods/glog » glog-dummy.m
› Compiling react-native Pods/glog » demangle.cc
› Compiling react-native Pods/Yoga » log.cpp
› Compiling react-native Pods/Yoga » experiments.cpp
› Compiling react-native Pods/Yoga » event.cpp
› Compiling react-native Pods/Yoga » Yoga-dummy.m
› Compiling react-native Pods/Yoga » YGValue.cpp
› Compiling react-native Pods/Yoga » YGStyle.cpp
› Compiling react-native Pods/Yoga » YGNodePrint.cpp
› Packaging react-native Pods/glog » libglog.a
› Compiling react-native Pods/Yoga » YGLayout.cpp
› Compiling react-native Pods/Yoga » YGEnums.cpp
› Compiling react-native Pods/Yoga » YGConfig.cpp
› Compiling react-native Pods/Yoga » Utils.cpp
› Compiling react-native Pods/React-perflogger » React-perflogger-dummy.m
› Compiling react-native Pods/React-perflogger » BridgeNativeModulePerfLogger.cpp
› Compiling react-native Pods/React-jsinspector » React-jsinspector-dummy.m
› Compiling react-native Pods/React-jsinspector » InspectorInterfaces.cpp
› Packaging react-native Pods/Yoga » libYoga.a
› Packaging react-native Pods/React-perflogger » libReact-perflogger.a
› Preparing react-native Pods/React-Core-AccessibilityResources » ResourceBundle-AccessibilityResources-React-Core-Info.plist
› Copying   react-native ../../../Users/expo/workingdir/build/Mobile/ Apps/React/sdk44-test/node_modules/react-native/React/AccessibilityResources/en.lproj ➜ ../../../Users/expo/Library/Developer/Xcode/DerivedData/sdk44test-cdacpoevfgnhvgcmpjwaipkewvah/Build/Intermediates.noindex/ArchiveIntermediates/sdk44test/IntermediateBuildFilesPath/UninstalledProducts/iphoneos/AccessibilityResources.bundle/en.lproj
› Compiling react-native Pods/DoubleConversion » strtod.cc
› Compiling react-native Pods/DoubleConversion » fixed-dtoa.cc
› Compiling react-native Pods/DoubleConversion » fast-dtoa.cc
› Compiling react-native Pods/DoubleConversion » double-conversion.cc
› Compiling react-native Pods/DoubleConversion » diy-fp.cc
› Compiling react-native Pods/DoubleConversion » cached-powers.cc
› Compiling react-native Pods/DoubleConversion » bignum.cc
› Compiling react-native Pods/DoubleConversion » DoubleConversion-dummy.m
› Creating  react-native Pods/React-Core-AccessibilityResources » AccessibilityResources.bundle
› Creating  expo-constants Pods/EXConstants-EXConstants » EXConstants.bundle
› Packaging react-native Pods/DoubleConversion » libDoubleConversion.a
› Compiling react-native Pods/RCT-Folly » json_pointer.cpp
› Compiling react-native Pods/RCT-Folly » json.cpp
› Compiling react-native Pods/RCT-Folly » dynamic.cpp
› Packaging react-native Pods/React-jsinspector » libReact-jsinspector.a
› Compiling react-native Pods/RCT-Folly » UniqueInstance.cpp
› Compiling react-native Pods/RCT-Folly » Unicode.cpp
› Compiling react-native Pods/RCT-Folly » SysUio.cpp
› Compiling react-native Pods/RCT-Folly » SpookyHashV2.cpp
› Compiling react-native Pods/RCT-Folly » ScopeGuard.cpp
› Compiling react-native Pods/RCT-Folly » SafeAssert.cpp
› Compiling react-native Pods/RCT-Folly » RCT-Folly-dummy.m
› Compiling react-native Pods/RCT-Folly » NetOps.cpp
› Compiling react-native Pods/RCT-Folly » FileUtil.cpp
› Compiling react-native Pods/RCT-Folly » MallocImpl.cpp
› Compiling react-native Pods/RCT-Folly » Format.cpp
› Compiling react-native Pods/RCT-Folly » F14Table.cpp
› Compiling react-native Pods/RCT-Folly » Demangle.cpp
› Compiling react-native Pods/RCT-Folly » Conv.cpp
› Compiling react-native Pods/RCT-Folly » CString.cpp
› Compiling react-native Pods/RCT-Folly » Assume.cpp
› Packaging react-native Pods/RCT-Folly » libRCT-Folly.a
› Compiling react-native Pods/React-jsi » jsilib-windows.cpp
› Compiling react-native Pods/React-jsi » jsilib-posix.cpp
› Compiling react-native Pods/React-jsi » jsi.cpp
› Compiling react-native Pods/React-jsi » React-jsi-dummy.m
› Compiling react-native Pods/React-jsi » JSIDynamic.cpp
› Compiling react-native Pods/React-jsi » JSCRuntime.cpp
› Packaging react-native Pods/React-jsi » libReact-jsi.a
› Compiling react-native Pods/React-cxxreact » ReactMarker.cpp
› Compiling react-native Pods/React-cxxreact » React-cxxreact-dummy.m
› Compiling react-native RAMBundleRegistry.cpp
› Compiling react-native Pods/React-cxxreact » NativeToJsBridge.cpp
› Compiling react-native Pods/React-cxxreact » ModuleRegistry.cpp
› Compiling react-native Pods/React-cxxreact » MethodCall.cpp
› Compiling react-native Pods/React-cxxreact » JSIndexedRAMBundle.cpp
› Compiling react-native Pods/React-cxxreact » JSExecutor.cpp
› Compiling react-native Pods/React-cxxreact » JSBundleType.cpp
› Compiling react-native Pods/React-cxxreact » JSBigString.cpp
› Compiling react-native Pods/React-cxxreact » Instance.cpp
› Compiling react-native Pods/React-cxxreact » CxxNativeModule.cpp
› Packaging react-native Pods/React-cxxreact » libReact-cxxreact.a
› Compiling react-native Pods/React-jsiexecutor » JSINativeModules.cpp
› Compiling react-native Pods/React-jsiexecutor » React-jsiexecutor-dummy.m
› Compiling react-native Pods/React-jsiexecutor » JSIExecutor.cpp
› Packaging react-native Pods/React-jsiexecutor » libReact-jsiexecutor.a
› Compiling react-native Pods/React-Core » React-Core-dummy.m
› Compiling react-native Pods/React-Core » UIView+React.m
› Compiling react-native Pods/React-Core » RCTWrapperViewController.m
› Compiling react-native Pods/React-Core » RCTWeakProxy.m
› Compiling react-native Pods/React-Core » RCTViewManager.m
› Compiling react-native Pods/React-Core » RCTView.m
› Compiling react-native Pods/React-Core » RCTVersion.m
› Compiling react-native Pods/React-Core » RCTUIUtils.m
› Compiling react-native Pods/React-Core » RCTUIManager.m
› Compiling react-native Pods/React-Core » RCTTouchHandler.m
› Compiling react-native Pods/React-Core » RCTSurfaceStage.m
› Compiling react-native Pods/React-Core » RCTSurfaceSizeMeasureMode.mm
› Compiling react-native Pods/React-Core » RCTSurfaceRootView.mm
› Compiling react-native Pods/React-Core » RCTSurfaceRootShadowView.m
› Compiling react-native Pods/React-Core » RCTSurfacePresenterStub.m
› Compiling react-native Pods/React-Core » RCTSurfaceHostingView.mm
› Compiling react-native Pods/React-Core » RCTSurfaceHostingProxyRootView.mm
› Compiling react-native Pods/React-Core » RCTSurface.mm
› Compiling react-native Pods/React-Core » RCTSliderManager.m
› Compiling react-native Pods/React-Core » RCTSlider.m
› Compiling react-native Pods/React-Core » RCTShadowView+Layout.m
› Compiling react-native Pods/React-Core » RCTShadowView+Internal.m
› Compiling react-native Pods/React-Core » RCTSegmentedControlManager.m
› Compiling react-native Pods/React-Core » RCTSegmentedControl.m
› Compiling react-native Pods/React-Core » RCTScrollViewManager.m
› Compiling react-native Pods/React-Core » RCTScrollView.m
› Compiling react-native Pods/React-Core » RCTScrollEvent.m
› Compiling react-native Pods/React-Core » RCTScrollContentViewManager.m
› Compiling react-native Pods/React-Core » RCTScrollContentView.m
› Compiling react-native Pods/React-Core » RCTScrollContentShadowView.m
› Compiling react-native Pods/React-Core » RCTSafeAreaViewManager.m
› Compiling react-native Pods/React-Core » RCTSafeAreaViewLocalData.m
› Compiling react-native Pods/React-Core » RCTSafeAreaView.m
› Compiling react-native Pods/React-Core » RCTSafeAreaShadowView.m
› Compiling react-native Pods/React-Core » RCTSRWebSocket.m
› Compiling react-native Pods/React-Core » RCTRootView.m
› Compiling react-native Pods/React-Core » RCTRefreshControl.m
› Compiling react-native Pods/React-Core » RCTRedBoxSetEnabled.m
› Compiling react-native Pods/React-Core » RCTRedBoxExtraDataViewController.m
› Compiling react-native Pods/React-Core » RCTReconnectingWebSocket.m
› Compiling react-native Pods/React-Core » RCTProgressViewManager.m
› Compiling react-native Pods/React-Core » RCTProfile.m
› Compiling react-native Pods/React-Core » RCTPickerManager.m
› Compiling react-native Pods/React-Core » RCTPicker.m
› Compiling react-native Pods/React-Core » RCTPerformanceLogger.m
› Compiling react-native Pods/React-Core » RCTParserUtils.m
› Compiling react-native Pods/React-Core » RCTPackagerConnection.mm
› Compiling react-native Pods/React-Core » RCTPackagerClient.m
› Compiling react-native Pods/React-Core » RCTObjcExecutor.mm
› Compiling react-native Pods/React-Core » RCTNativeModule.mm
› Compiling react-native Pods/React-Core » RCTMultipartStreamReader.m
› Compiling react-native Pods/React-Core » RCTMultipartDataTask.m
› Compiling react-native Pods/React-Core » RCTModuleMethod.mm
› Compiling react-native Pods/React-Core » RCTModuleData.mm
› Compiling react-native Pods/React-Core » RCTModalManager.m
› Compiling react-native Pods/React-Core » RCTModalHostViewController.m
› Compiling react-native Pods/React-Core » RCTModalHostView.m
› Compiling react-native Pods/React-Core » RCTMessageThread.mm
› Compiling react-native Pods/React-Core » RCTMaskedViewManager.m
› Compiling react-native Pods/React-Core » RCTMaskedView.m
› Compiling react-native Pods/React-Core » RCTManagedPointer.mm
› Compiling react-native Pods/React-Core » RCTLog.mm
› Compiling react-native Pods/React-Core » RCTLayoutAnimationGroup.m
› Compiling react-native Pods/React-Core » RCTLayoutAnimation.m
› Compiling react-native Pods/React-Core » RCTLayout.m
› Compiling react-native Pods/React-Core » RCTKeyCommands.m
› Compiling react-native Pods/React-Core » RCTJavaScriptLoader.mm
› Compiling react-native Pods/React-Core » RCTJSStackFrame.m
› Compiling react-native Pods/React-Core » RCTInspectorPackagerConnection.m
› Compiling react-native Pods/React-Core » RCTInspectorDevServerHelper.mm
› Compiling react-native Pods/React-Core » RCTInspector.mm
› Compiling react-native Pods/React-Core » RCTImageSource.m
› Compiling react-native Pods/React-Core » RCTI18nUtil.m
› Compiling react-native Pods/React-Core » RCTFrameUpdate.m
› Compiling react-native Pods/React-Core » RCTFont.mm
› Compiling react-native Pods/React-Core » RCTFollyConvert.mm
› Compiling react-native Pods/React-Core » RCTEventEmitter.m
› Compiling react-native Pods/React-Core » RCTEventDispatcher.m
› Compiling react-native Pods/React-Core » RCTErrorInfo.m
› Compiling react-native Pods/React-Core » RCTDatePickerManager.m
› Compiling react-native Pods/React-Core » RCTDatePicker.m
› Compiling react-native Pods/React-Core » RCTCxxUtils.mm
› Compiling react-native Pods/React-Core » RCTCxxModule.mm
› Compiling react-native Pods/React-Core » RCTCxxMethod.mm
› Compiling react-native Pods/React-Core » RCTCxxConvert.m
› Compiling react-native Pods/React-Core » RCTConvert.m
› Compiling react-native Pods/React-Core » RCTConstants.m
› Compiling react-native Pods/React-Core » RCTComponentEvent.m
› Compiling react-native Pods/React-Core » RCTComponentData.m
› Compiling react-native Pods/React-Core » RCTBundleURLProvider.mm
› Compiling react-native Pods/React-Core » RCTBridge.m
› Compiling react-native Pods/React-Core » RCTBorderDrawing.m
› Compiling react-native Pods/React-Core » RCTAssert.m
› Compiling react-native Pods/React-Core » RCTActivityIndicatorViewManager.m
› Compiling react-native Pods/React-Core » RCTActivityIndicatorView.m
› Compiling react-native Pods/React-Core » NSDataBigString.mm
› Compiling react-native Pods/React-Core » JSCExecutorFactory.mm
› Packaging react-native Pods/React-Core » libReact-Core.a
› Compiling react-native Pods/React-RCTText » RCTVirtualTextViewManager.m
› Compiling react-native Pods/React-RCTText » React-RCTText-dummy.m
› Compiling react-native Pods/ReactCommon » TurboModuleUtils.cpp
› Compiling react-native Pods/ReactCommon » TurboModulePerfLogger.cpp
› Compiling react-native Pods/ReactCommon » TurboModuleBinding.cpp
› Compiling react-native Pods/ReactCommon » TurboModule.cpp
› Compiling react-native Pods/ReactCommon » TurboCxxModule.cpp
› Compiling react-native Pods/ReactCommon » ReactCommon-dummy.m
› Compiling react-native Pods/ReactCommon » RCTTurboModuleManager.mm
› Compiling react-native Pods/ReactCommon » RCTTurboModule.mm
› Compiling react-native Pods/ReactCommon » LongLivedObject.cpp
› Compiling react-native Pods/React-RCTText » RCTVirtualTextShadowView.m
› Compiling react-native Pods/React-RCTText » RCTTextViewManager.m
› Compiling react-native Pods/React-RCTText » RCTTextView.m
› Packaging react-native Pods/ReactCommon » libReactCommon.a
› Compiling react-native Pods/React-RCTText » RCTTextShadowView.m
› Compiling react-native Pods/React-RCTText » RCTTextSelection.m
› Compiling react-native Pods/React-RCTText » RCTTextAttributes.m
› Compiling react-native Pods/React-RCTText » RCTSinglelineTextInputViewManager.m
› Compiling react-native Pods/React-RCTText » RCTRawTextViewManager.m
› Compiling react-native Pods/React-RCTText » RCTRawTextShadowView.m
› Compiling react-native Pods/React-RCTText » RCTMultilineTextInputViewManager.m
› Compiling react-native Pods/React-RCTText » RCTMultilineTextInputView.m
› Compiling react-native Pods/React-RCTText » RCTInputAccessoryViewManager.m
› Compiling react-native Pods/React-RCTText » RCTInputAccessoryViewContent.m
› Compiling react-native Pods/React-RCTText » RCTInputAccessoryView.m
› Compiling react-native Pods/React-RCTText » RCTInputAccessoryShadowView.m
› Compiling react-native Pods/React-RCTText » RCTConvert+Text.m
› Compiling react-native Pods/React-RCTText » RCTBaseTextViewManager.m
› Compiling react-native Pods/React-RCTText » RCTBaseTextShadowView.m
› Compiling react-native Pods/React-RCTText » RCTBaseTextInputViewManager.m
› Compiling react-native Pods/React-RCTText » RCTBaseTextInputView.m
› Compiling react-native Pods/React-RCTText » RCTBaseTextInputShadowView.m
› Compiling react-native Pods/RCTTypeSafety » RCTTypedModuleConstants.mm
› Compiling react-native Pods/RCTTypeSafety » RCTTypeSafety-dummy.m
› Compiling react-native Pods/RCTTypeSafety » RCTConvertHelpers.mm
› Packaging react-native Pods/React-RCTText » libReact-RCTText.a
› Packaging react-native Pods/RCTTypeSafety » libRCTTypeSafety.a
› Executing react-native Pods/FBReactNativeSpec » [CP-User] Generate Specs
⚠  Skipping duplicate file: node_modules/react-native/React/FBReactNativeSpec/FBReactNativeSpec/FBReactNativeSpec.h
   Remove: Xcode » Pods/FBReactNativeSpec » Build Phases » Copy Headers » FBReactNativeSpec.h
⚠  Skipping duplicate file: node_modules/react-native/React/FBReactNativeSpec/FBReactNativeSpec/FBReactNativeSpec-generated.mm
   Remove: Xcode » Pods/FBReactNativeSpec » Build Phases » Compile Sources » FBReactNativeSpec-generated.mm
▸ ** ARCHIVE FAILED **
▸ The following build commands failed:
▸ 	CompileSwiftSources normal arm64 com.apple.xcode.tools.swift.compiler (in target 'ExpoModulesCore' from project 'Pods')
▸ 	PhaseScriptExecution [CP-User]\ Generate\ Specs /Users/expo/Library/Developer/Xcode/DerivedData/sdk44test-cdacpoevfgnhvgcmpjwaipkewvah/Build/Intermediates.noindex/ArchiveIntermediates/sdk44test/IntermediateBuildFilesPath/Pods.build/Release-iphoneos/FBReactNativeSpec.build/Script-AEB7E4B2C2A6262E00C82D25FB34E8C3.sh (in target 'FBReactNativeSpec' from project 'Pods')
▸ (2 failures)
** ARCHIVE FAILED **
The following build commands failed:
	CompileSwiftSources normal arm64 com.apple.xcode.tools.swift.compiler (in target 'ExpoModulesCore' from project 'Pods')
	PhaseScriptExecution [CP-User]\ Generate\ Specs /Users/expo/Library/Developer/Xcode/DerivedData/sdk44test-cdacpoevfgnhvgcmpjwaipkewvah/Build/Intermediates.noindex/ArchiveIntermediates/sdk44test/IntermediateBuildFilesPath/Pods.build/Release-iphoneos/FBReactNativeSpec.build/Script-AEB7E4B2C2A6262E00C82D25FB34E8C3.sh (in target 'FBReactNativeSpec' from project 'Pods')
(2 failures)
Exit status: 65
+-------------+-------------------------+
|           Build environment           |
+-------------+-------------------------+
| xcode_path  | /Applications/Xcode.app |
| gym_version | 2.185.1                 |
| sdk         | iPhoneOS15.0.sdk        |
+-------------+-------------------------+
Looks like fastlane ran into a build/archive error with your project
It's hard to tell what's causing the error, so we wrote some guides on how
to troubleshoot build and signing issues: https://docs.fastlane.tools/codesigning/getting-started/
Before submitting an issue on GitHub, please follow the guide above and make
sure your project is set up correctly.
fastlane uses `xcodebuild` commands to generate your binary, you can see the
the full commands printed out in yellow in the above log.
Make sure to inspect the output above, as usually you'll find more error information there
[stderr] [!] Error building the application - see the log above
Error: Fastlane build failed with unknown error. Please refer to the "Run fastlane" and "Xcode Logs" phases.
Fastlane errors in most cases are not printed at the end of the output, so you may not find any useful information in the last lines of output when looking for an error message.

Reproducible demo or steps to reproduce from a blank project

Create a new folder
Run 'expo init' in command line (follow basic instructions)
Run 'eas build --platform ios --profile production' to configure/trigger a build in EAS.

This was resolved by some help from Expo support directly.
The error is because our build directory path had a subfolder with a space in the name e.g. '/Mobile Apps/ourapp'. Remove the spaces in folder names in the build directory structure and it all works.
Hope this helps someone


local-gpu docker-compose version incompatibility

When I try to estimator.fit() with a local_gpu instance type, I get the following error:

The Compose file '/tmp/tmpemtqjw1x/docker-compose.yaml' is invalid because:
Unsupported config option for services.algo-1-x260e: 'deploy'

The generated YAML is:
networks:
  sagemaker-local:
    name: sagemaker-local
services:
  algo-1-lrlsg:
    command: train
    container_name: anj25ec7e5-algo-1-lrlsg
    deploy:
      resources:
        reservations:
          devices:
          - capabilities:
            - gpu
    environment:
    - AWS_REGION=eu-central-1
    - TRAINING_JOB_NAME=my_ecr-2023-07-03-21-51-01-644
    image: xxxxxxxxxxxx.dkr.ecr.eu-central-1.amazonaws.com/my_ecr:latest
    networks:
      sagemaker-local:
        aliases:
        - algo-1-lrlsg
    stdin_open: true
    tty: true
    volumes:
    - /tmp/tmp56de_vqt/algo-1-lrlsg/output:/opt/ml/output
    - /tmp/tmp56de_vqt/algo-1-lrlsg/output/data:/opt/ml/output/data
    - /tmp/tmp56de_vqt/algo-1-lrlsg/input:/opt/ml/input
    - /tmp/tmp56de_vqt/model:/opt/ml/model
    - /home/ubuntu/work/feuerkrieg_division:/opt/ml/input/data/instance
version: '2.3'

I am new to docker compose, but after reading a bit I think the problem is that deploy was introduced in v3, but that the YAML version is 2.3
Also I dont know how this interacts with the fact that I had to install v1 (docker-compose rather than docker compose) for the execution to reach this failure.
I saw no ENV_VAR I could set to change either:

The docker-compose command https://github.com/aws/sagemaker-python-sdk/blob/052d7e00f236b19260b584ee7d63e2141e5053fb/src/sagemaker/local/image.py#L718C15-L718C15
The YAML version: https://github.com/aws/sagemaker-python-sdk/blob/052d7e00f236b19260b584ee7d63e2141e5053fb/src/sagemaker/local/image.py#L686

P.S.
Here is where the deploy command comes from https://github.com/aws/sagemaker-python-sdk/blob/052d7e00f236b19260b584ee7d63e2141e5053fb/src/sagemaker/local/image.py#L769-L772

Some things I forgot to mention:
I am using a BYOC.
docker engine version 24.0.2
docker-compose version 1.25.0

Hi @shakedel , which sample in this GitHub repo are you trying to run?

@eitansela  now that you ask I realize it is not from this repo but from another one owned by AWS. Here is the notebook I copied: https://github.com/aws/amazon-sagemaker-examples/blob/09f6fad6de75a4520f6f71d661f4b7a8139ce736/advanced_functionality/pytorch_extending_our_containers/pytorch_extending_our_containers.ipynb
You can scroll down to the section named "SageMaker Python SDK Local Training"
But I don't think it matters much as my code is fairly simple and straightforward:
Estimator(
    role='my_role',
    instance_count=1,
    instance_type="local_gpu",
    image_uri="xxxxxxxxxxxx.dkr.ecr.eu-central-1.amazonaws.com/my_ecr:latest",
).fit({
    'channel1': "file:///path/to/channel1/data",
    'channel2': "file:///path/to/channel2/data"
})

The contents of the docker image are irrelevant since the failure occurs when validating the generated docker-compose.yaml does not reach that stage

Hi @shakedel , please open an issue in the amazon-sagemaker-examples repo. Closing the issue here.

Hi @shakedel , please open an issue in the amazon-sagemaker-examples repo. Closing the issue here.


release v0.22.3 post-relese actions

Update documentation
snapshot documentation
snapshot k8s
create next k8s manifests and helm charts

Done.


molecule: init at 5.1.0, python310Packages.molecule-plugins: init at 23.4.1

Description of changes

This PR is a successor to https://github.com/NixOS/nixpkgs/pull/156612.
Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] 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
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
23.11 Release Notes (or backporting 23.05 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.

@ofborg build molecule

I don't think ofborg understand this commit syntax. Can you split in two commit or use pkg1,pkg2: init at v1,v2 (ofborg understand this).
i will test molecule soon. Can we test molecules plugin without molecules ? I know how to test molecule plugin but wanted to test them separately.
Why are you reversing the deps ?

molecule-plugins depends on molecule in upstream repo. I'm not sure if plugins can be tested separately.
Maybe I'm not knowledgeable enough but it seemed easier to implement reversing the dependencies in nixpkgs. Actually I don't know how it would work (if it would work at all) when someone wanted to get molecule with plugins installed. I know one can install python with some packages (like requests) but I have no idea if it is possible to do something like: nix profile install nixpkgs#molecule nixpkgs#python3.pkgs.molecule-plugins. Would that get one molecule with plugins? Maybe my understanding is limited.

What can be done is naming the top level attribute molecule and have it reference molecule-plugins so when someone install molecule it get a working molecule. Something like we have with cc-unwrapped

Neither python3Packages.molecule,python3Packages.molecule-plugins: init at 5.1.0,23.4.1 nor python3Packages.molecule: init at 5.1.0, python3Packages.molecule-plugins: init at 23.4.1 worked for ofborg to find changed paths :thinking:

molecule reset
Traceback (most recent call last):
  File "/nix/store/qrdxj46nz3s5f7wgzl6n4y124iy47lvk-python3.10-molecule-5.1.0/bin/.molecule-wrapped", line 9, in <module>
    sys.exit(main())
  File "/nix/store/f0sfxf4yjc0xsylxxn0syrpmkb5wlq01-python3.10-click-8.1.3/lib/python3.10/site-packages/click/core.py", line 1130, in __call__
    return self.main(*args, **kwargs)
  File "/nix/store/f0sfxf4yjc0xsylxxn0syrpmkb5wlq01-python3.10-click-8.1.3/lib/python3.10/site-packages/click/core.py", line 1055, in main
    rv = self.invoke(ctx)
  File "/nix/store/f0sfxf4yjc0xsylxxn0syrpmkb5wlq01-python3.10-click-8.1.3/lib/python3.10/site-packages/click/core.py", line 1657, in invoke
    return _process_result(sub_ctx.command.invoke(sub_ctx))
  File "/nix/store/f0sfxf4yjc0xsylxxn0syrpmkb5wlq01-python3.10-click-8.1.3/lib/python3.10/site-packages/click/core.py", line 1404, in invoke
    return ctx.invoke(self.callback, **ctx.params)
  File "/nix/store/f0sfxf4yjc0xsylxxn0syrpmkb5wlq01-python3.10-click-8.1.3/lib/python3.10/site-packages/click/core.py", line 760, in invoke
    return __callback(*args, **kwargs)
  File "/nix/store/f0sfxf4yjc0xsylxxn0syrpmkb5wlq01-python3.10-click-8.1.3/lib/python3.10/site-packages/click/decorators.py", line 26, in new_func
    return f(get_current_context(), *args, **kwargs)
  File "/nix/store/qrdxj46nz3s5f7wgzl6n4y124iy47lvk-python3.10-molecule-5.1.0/lib/python3.10/site-packages/molecule/command/reset.py", line 48, in reset
    driver.reset()
  File "/nix/store/wy6k5cyyc1iqrgggpqx8ibkxrl3iv420-python3.10-molecule-plugins-23.4.1/lib/python3.10/site-packages/molecule_plugins/docker/driver.py", line 256, in reset
    import docker
ModuleNotFoundError: No module named 'docker'

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/prs-ready-for-review/3032/2558


User @bzxys tried to open a 3x position with 0.95 BTC. Instead of reject the transaction due lack of liquidity, a weird position was opened

User @bzxys tried to open a 3x position with this transaction:
https://blockscout.com/rsk/mainnet/tx/0x82d6fda2ddd639d4d2d013a569aacfd29b19c15065795f8debd67255c09fd819/token-transfers
There was a lack of sufficient liquidity in lending pool, but instead of reject the openeing of the position, a lend for around 4.700 satoshis was opened.

i looked into his position on the contract:
{'loanId': 0xb974a64f70f5a1179f8fded6b689ae31daee910f84d025c424784a70034a9838, 'loanToken': '0xef213441A85dF4d7ACbDaE0Cf78004e1E486bB96', 'collateralToken': '0x542fDA317318eBF1d3DEAf76E0b632741A7e677d', 'principal':<PHONE_NUMBER>849381404, 'collateral':<PHONE_NUMBER>90903415, 'interestOwedPerDay':<PHONE_NUMBER>86700, 'interestDepositRemaining':<PHONE_NUMBER>673550, 'startRate':<PHONE_NUMBER>5435514311290, 'startMargin':<PHONE_NUMBER>0000000000, 'maintenanceMargin':<PHONE_NUMBER>0000000000, 'currentMargin':<PHONE_NUMBER>669145119161903, 'maxLoanTerm': 2419200, 'endTimestamp':<PHONE_NUMBER>, 'maxLiquidatable': 0, 'maxSeizable': 0}

he's got a loan of 1.9 USD
and collateral of 0.95 BTC
i have no idea how this could happen. this will take some time to investigate.
is he able to close the position on the UI?

Not able / held off closing the position on the UI (see pic). Awaiting directions from devs. Have been working closely with @jjmr007 and last direction provided -->Wait till next UI update (target 2/4) and trading enabled to unwind position ...so I wait.

Not sure if this could be related to the reason why loan of $1.9 USD occurred. Posting here so that can track down / understand this #issue2 of mine:
wallet: https://explorer.rsk.co/address/0x9642f4781e1e6673b1ad2dec31bc727993bf76ad

I had transferred ~0.05 BTC a few days before above .95 BTC trade.
I did a leverage trade with this and made ~$65 USD profit.
I then performed the .95 3x Margin trade
For some reason, my wallet balance started showing remaining balance of 0.03 RBC ... not sure what happened to 0.02 BTC?
Will need that investigated as well ... first want to recover 0.95 BTC vs 0.02 BTC :)

this should qualify for bug finding bounty no!? ;p

i have now closed my position and recovered .95 btc. thx @jjmr007

This issue has a new incident, with the user CEK#6313 who opened this Short position:
loanId = 0x1fed14703b3e846ce8c791039e84b323a4fb6334a0f4a7b58f0be65d32e7f2b7
with the intention to be 5x, but the loan was only of 400.000 satoshis (around $150) while his collateral was of $191
Also he opened this long position:
loanId = 0x347280f5c62d5cfffa12984d170709f23a6d53f416c9949cf33ee4adbd5246c7
also with the intention to be 5x, but the loan obtained was of $3,9 while his collateral was of 600.000 satoshis (more than $220)

There is a couple of other users with this same incident:
I.- User CEK#6313 opened two positions from address 0x15ee3a6e32864d4247ec41f399cb4ead55cf412f
1.-Short position, with loanId: 0x1fed14703b3e846ce8c791039e84b323a4fb6334a0f4a7b58f0be65d32e7f2b7
intended to be 5x, but the loan obtained was 400.000 satoshis (around $154) while the collateral was $190
2.- Long position, with loanId: 0x347280f5c62d5cfffa12984d170709f23a6d53f416c9949cf33ee4adbd5246c7
intended to be 5x, but the loan obtained was of $3,9 while the collateral was 600.000 satoshis (more than $220)
II.- User lactarius#9543 opened one positions from address 0x1996A1c4597721EDAFA2ffe433B0C26B25494ec9
3.- Long position, with loanId: 0x00b46a6052de2b15fdf91b32643393d342ba6903c5d2add5f94f9bc4d0db9556
intended to be 5x, but the loan obtained was of $3,9 while the collateral was 1.000.000 satoshis (around $400)
I think a warning should be publishet to the community

@creed-victor and @powerhousefrank are going to look into this.

check the params which were sent to the smart contract to find out if the frontend was sending the wrong params (in that case the issue lies on the frontend and i victor's repsonsibility)
if the params are correct, the issue is on the smart contract and it's franklin's responsibiliy to look into it (contact me for an explanation of our trading process)

Was able to reproduce it on testnet too when sending BTC/USDT long using BTC as collateral and BPRO/USDT long using BPRO as collateral (the ones with amount in collateralTokenSent instead of loanTokenSent).
For 0.01 BTC with 2x leverage opened position size is 0.01 BTC while it should be 0.002 BTC (tried this will all leverage choices with same outcome).
Checked on params from frontend side and it looks good, so unless contract ABI changed and it's not updated on frontend it shouldn't be issue within frontend.

Update about the Bug: The user CEK#6313 who opened a long 5x position loanId :
0x347280f5c62d5cfffa12984d170709f23a6d53f416c9949cf33ee4adbd5246c7
his vcollateral was of 600.000 satoshis (around $220), but the loan he got was of $3,9 (instead a loan of 4x$220)
This position is opened at a startRate of 38,884.292195869885465932 USD/BTC
Today he closed his position at a price close to $44.000... AND HE GOT A LOSS of around 13.500 satoshis (while the cost of the closing transaction is around 5.000 satoshis)

please don't mix different user cases in the same issue. it can become confusing. regarding the second user: it's mostly likely an issue due to price misconceptions. we had the oracle rate stored on the loan object, which was shown to the user as start price, although that was not the case. also user were expecting the wrong price when closing a trade.
the price update is the main improvement of our recent update.
However, the wrong opening sizes are a huge problem if they are still present.

@powerhousefrank i think the problem lies in _totalDeposit

This issue was solved.


tour: No math.pi

Context: https://tour.golang.org/basics/3
./prog.go:9:14: cannot refer to unexported name math.pi
./prog.go:9:14: undefined: math.pi

Please read the text on the left before opening issues. It says:

Run the code. Notice the error message.

Closing here.


Call to undefined method Carbon\Carbon::timespan()

I'm trying to implement this package in my project but after installation via composer and adding the provider, i get Call to undefined method Carbon\Carbon::timespan()
Can I know what I did wrong

Are you calling Carbon::timespandirectly? Carbon doens't have the timespan method, you need to call it on the Date class.


Update the game over message.

Update the game over message so people know how to play again!

Interesting stuff


Hex values without # are missed

The CSS Style declaration looks for only a # followed by 6 characters for Hex values, browsers treat the # as optional and will resolve any value 0-ffffff as hex.  The change seems pretty simple, change the regex in parse.js .

A quick check in Chrome shows that this is not the case, at least not for all browsers:
> element.style.backgroundColor = 'fff'
"fff"

> element.style.backgroundColor
"initial"

> element.style.backgroundColor = '#fff'
"#fff"

> element.style.backgroundColor
"rgb(255, 255, 255)"

Could you provide an example of a browser that works without #?

Closing because of no activity.


Change texts to stipulate TAN hotline for PCR tests only (EXPOSUREAPP-6585)

Description
Changed TAN-related UI texts to specify that they refer to PCR tests only (as opposed to Rapid Tests) - see also EXPOSUREAPP-6585.

@harambasicluka Why has this been merged into the release/2.0.x branch?

@Ein-Tim Early morning mistake, thanks for the heads up :heart:

@Ein-Tim thanks for pointing this out. This was my mistake.

@janetback @d4rken
No problem, always happy to help. This isn't live in the Android app now, or?


Module not fount dns, dgram, ,,,

I get this error when doing follow the guide
const fetch = require('@zeit/fetch-cached-dns')(require('node-fetch'))
Module not found: Can't resolve 'dns' in 'C:\Sony\work\saostar\saostar-fe-pc\node_modules\native-dns-cache'

Is there already an solution for this issue? I got the same error.

dns and dgram are standard library https://nodejs.org/api/dgram.html https://nodejs.org/api/dns.html
Which node, npm/yarn versions  are you using? And which OS? in node console, does require('dgram') and require('dns') work?


Replace nil ternaries with #try

Closes #11955

LGTM 👍  Not sure why there are test failures. Will restart.

Closing this for now. I don't have the time right now to figure out why this is failing.


[cloud_firestore] Add MetadataChanges to documentReference.snapshot()

I want to use MetadataChanges like in Android

I believe that this is a duplicate of flutter/flutter#16432 and it was fixed in https://github.com/flutter/plugins/pull/1918. Please let me know if I'm mistaken

@basketball-ico
This issue has been moved to https://github.com/FirebaseExtended/flutterfire/issues/1210. Any further collaboration will be done there.


Add option to delete account, edit account information, add profile picture

API covers the functions, we just need to use them in the app


Submission checker : Time difference checker needs to be modified

The time difference checker method that checks perf delta between ranging and testing phase has conflicting requirements to Inference WG.  An issue was raised in last round where one of the submissions had a difference of  > 5% which was the acceptable threshold.  It turned out that the testing (measure) phase was slower .  If the submitter (NVIDIA) had rerun, then their results could have come within threshold.  However the inference WG requires that any updated submission be no more than a fraction of a % off.  So these two objectives are in conflict. If the goal is to check that the flow was carried out as expected , then we could relax this check or find another way that allows to meet both the  Inference WG objectives and Power WG objectives.
[x] Check client sources checksum
[x] Check server sources checksum
[x ] Check PTD commands and replies
[x] Check UUID
[x] Check session name
[x] Check time difference
[x] Check client server messages
[x] Check results checksum
[x] Check errors and warnings from PTD logs
[x] Check PTD configuration
[x] Check debug is disabled on server-side

Hi Tejus - I do not know if we have any resolution for this , as yet.  But clearly we need to modify this as a warning and not a check to re-submit to make these within the acceptable time range, because it may conflict with Inference policy of resubmit needing to be within a very small delta perf  (< 1%) from original submission.
Another option could be that an issue to resubmit be filed optionally,  if the "performance" phase is faster than "ranging" phase by the given  tolerance bound we have in v1.0.  Need to check if that is acceptable by Inference policies.

Power WG Discussions:
If Ranging result > Testing result, then power could be higher (likely), then after ranging if the limits are set, then the limits are going to hold. This case is good. No need for resubmissions. The other case will need more scrutiny (resubmissions, etc.). More folks asked to comment here.

I think this is agreed given discussions in Power WG , no need to change code.


Update MD file on new branch 2017-27-21_23-11-22

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

split/updateTestCon.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Bigbluebutton playback video is 3 hours, but bbb-video-download result is 1.07!

Bigbluebutton playback video is 3 hours, but bbb-video-download result is 1.07 hour!

Please provide some detail. Best: The presentation files. Minimum: shapes.svg and metadata.xml

Should I upload the files or just screenshots for the files

please provide the files (not screenshots)


Filtering variantmatrix data by MAF range and max missing

Can the proposed /search/variantmatrix endpoint has basic filtering fields (e.g., minmaf, maxmaf, and missingData) just like the GA4GH /variants/search endpoint?
I can see the great advantage of this new "variantmatrix" endpoint, saving time and bandwidth when retrieving genotyping data. But we will lose a significant part of that advantage by forcing the clients to request the whole data set and do that filtering at their end!
I believe it will be wise to enable the requester to apply that kind of filtering before packing and sending the requested data back via API. It will serve the primary goal of having this "variantmatrix" endpoint in the first place, isn't it?

Actually, the plain GA4GH specs do not support these filtering parameters: https://rest.ensembl.org/documentation/info/gavariants. They were added as an enrichment to the Gigwa V2 implementation because we wanted to make it API-driven without losing any of V1's functionalities. But of course I can only agree that these are pretty useful filters. Although applying them can take a long time on large datasets.

Hello,
this issue is somewhat related to #551 as calculated metrics/statistics like MAF, heterozygosity etc. can also be seen as variant-level metadata like the INFO column metadata of VCF. So we can discuss both topics in context in the meetings of the Genotyping Call Enhancement Working Group.

@GuilhemSempere I would like to see GIGWA supporting all these (optional/extra) minMaf, maxMaf, minMissingData, maxMissingData, minHeZ, and maxHeZ filtering parameters in the allele matrix search call. Just like what they did for the GA4GH /variants/search call.
@BrapiCoordinatorSelby If we agree on their usefulness from the application point of view, why not suggest having them in the BrAPI /search/allelematrix parameters?
@patrick-koenig I understand the service provider's argument that such parameters can put a huge computational load on the server side. Well, what will be the alternative option, the client application has nothing but extract the whole dataset, and then do the filtering at their side. This scenario implies more transfer data cost and fewer requests the server can manage because of the transfer time required for each!
@BrapiCoordinatorSelby I believe adding these filtering parameters can be a win-win situation for both server and client implementation in most production environments.

I don't see major problems implemnting this in Gigwa's allelematrix call, but indeed we'd rather have this functionality well defined and made official before starting something. I think @patrick-koenig you are referring to pre-computed annotation fields based on the overall list of callSets, whereas @khaled-alshamaa is mentioning realtime calculation based on a selected list of material.


error : "LONG_BIT definition appears wrong for platform (bad gcc/glibc config?)

Hi,
my program is using a python module to download some video from google drive, it's work very well but I couldn't cross compile it for raspberry. I am new in QT Cross Compile for raspberry and I couldn't find a solution for this error in any place :

define _POSIX_C_SOURCE 200809L
^
In file included from lib/python2.7/Include/Python.h:8:0,
from DigitalSignal.cpp:15:
lib/python2.7/Include/pyconfig.h:1242:0: warning: « _XOPEN_SOURCE » redéfini [enabled by default]
define _XOPEN_SOURCE 600
^
In file included from /opt/qtrpi/raspi/tools/arm-bcm2708/gcc-linaro-arm-linux-gnueabihf-raspbian-x64/arm-linux-gnueabihf/include/c++/4.8.3/arm-linux-gnueabihf/bits/os_defines.h:39:0,
from /opt/qtrpi/raspi/tools/arm-bcm2708/gcc-linaro-arm-linux-gnueabihf-raspbian-x64/arm-linux-gnueabihf/include/c++/4.8.3/arm-linux-gnueabihf/bits/c++config.h:426,
from /opt/qtrpi/raspi/tools/arm-bcm2708/gcc-linaro-arm-linux-gnueabihf-raspbian-x64/arm-linux-gnueabihf/include/c++/4.8.3/cstddef:41,
from /opt/qtrpi/raspi/qt5pi/include/QtCore/qglobal.h:45,
from /opt/qtrpi/raspi/qt5pi/include/QtCore/qtimer.h:43,
from /opt/qtrpi/raspi/qt5pi/include/QtCore/QTimer:1,
from DigitalSignal.h:5,
from DigitalSignal.cpp:1:
/opt/qtrpi/raspbian/sysroot/usr/include/./features.h:162:0: note: ceci est l'emplacement d’une précédente définition
define _XOPEN_SOURCE 700
^
In file included from lib/python2.7/Include/Python.h:61:0,
from DigitalSignal.cpp:15:
lib/python2.7/Include/pyport.h:895:2: error: #error "LONG_BIT definition appears wrong for platform (bad gcc/glibc config?)."
error "LONG_BIT definition appears wrong for platform (bad gcc/glibc config?)."
^
Makefile:1145: recipe for target 'DigitalSignal.o' failed
make: *** [DigitalSignal.o] Error 1

If anyone already seen this error , please help :)
thank you in advance :)

@REKIKWael
Try using python3 instead. If that doesn't work, make sure you have the correct bit variation of python.


[Symfony60] Fix added return type for Router::getRouteCollection

Fixes rectorphp/rector#7308

Looks very good, thank you for the test verification :clap:


Direct peer between VNETs - Troubleshoot SMB or dual-protocol volumes

In section "Troubleshoot SMB or dual-protocol volumes" (https://docs.microsoft.com/en-gb/azure/azure-netapp-files/troubleshoot-dual-protocol-volumes#errors-for-dual-protocol-volumes), the resolution of "Dual-protocol volume creation fails with the error Could not query DNS server. Verify that the network configuration is correct and that DNS servers are available.", could have some additional details. After stating that peering between two VNETs for AD connection is allowed, the following or something similar could be added: "Make sure that the two VNETs are directly peered, with no middle VNETs connecting the volumes and the domain controller".

Document details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 7afcf612-fe74-b152-cdd0-3afbb919f2fb
Version Independent ID: 1067f927-b15a-7fbe-d3d0-ad2fdf598e25
Content: Troubleshoot SMB or dual-protocol volumes for Azure NetApp Files
Content Source: articles/azure-netapp-files/troubleshoot-dual-protocol-volumes.md
Service: azure-netapp-files
GitHub Login: @b-juche
Microsoft Alias: b-juche

@beagam - Thanks for the comment. I'll consult the technical team about your input.  Meanwhile, if you are a NetApp or Microsoft team member, feel free to reach out through email at<EMAIL_ADDRESS>or<EMAIL_ADDRESS>so that I can loop you in for the discussion.  Thanks.

Per input from product team, we'd add reference instead of additional explanation.
We've added:
"See Guidelines for Azure NetApp Files network planning (https://docs.microsoft.com/en-us/azure/azure-netapp-files/azure-netapp-files-network-topologies#azure-native-environments) for details."
This change is addressed in PR#16803
https://github.com/MicrosoftDocs/azure-docs-pr/pull/168030

#please-close


Zooming Stretches the Image

When you use zoom feature, game stretches the image vertically.
https://i.imgur.com/26qtT36.jpg

Thanks for reporting. I did not use that feature, so I did not notice the bug when I was testing the FOV fix. I will see what I can do.

I also don't use it often but since SH3 is very visceral in detail, It's nice to have a close look at the obscure Valtiel sequences and other models like ceremonial robes and hanged models far away in nightmare worlds. I sincerely thank you for your work to make Silent Hill more modern. Cheers!

Fixed in the upcoming release.


how come () => void is a subtype of () => a if void isn't a subtype of a and a isn't subtype of void?

declare var a: () => void;
declare var b: () => PromiseLike<void>;

a = b; // <-- why!!!
b = a;

declare var c: void;
declare var d: PromiseLike<void>;

c = d;
d = c;

tl;dr; the assumption is that it is save to assign something that returns some value to something that returns void so result is ignored, however the opposite is not true.
see 3.11.3 Subtypes and Supertypes

S is an object type, an intersection type, an enum type, or the Number, Boolean, or String primitive type, T is an object type, and for each member M in T, one of the following is true:

M is a property and S has an apparent property N where

M and N have the same name,
the type of N is a subtype of that of M,
if M is a required property, N is also a required property, and
M and N are both public, M and N are both private and originate in the same declaration, M and N are both protected and originate in the same declaration, or M is protected and N is declared in a class derived from the class in which M is declared.

M is a non-specialized call or construct signature and S has an apparent call or construct signature N where, when M and N are instantiated using type Any as the type argument for all type parameters declared by M and N (if any),

the signatures are of the same kind (call or construct),
M has a rest parameter or the number of non-optional parameters in N is less than or equal to the total number of parameters in M,
for parameter positions that are present in both signatures, each parameter type in N is a subtype or supertype of the corresponding parameter type in M, and
the result type of M is Void, or the result type of N is a subtype of that of M.

it's not a safe assumption at all, ugh....

I have a function that returns a promise: () => Promise<void>, it is passed around a callback, after refactoring unintentionally it end up being an argument of a parameter of type () => void. Right here I need the compiler's help to notice it and tell me that I can't use it there, because Promisejust can't be treated the same way asvoid`, and what does compiler do? nothing, exactly

anything that has to be serialized can't be passed round safely because there is a chance it will get swallowed by () => void and then end up being passed to the standard JSON.stringify which will then crash

The alternative is much worse -- imagine not being able to write this code:
let arr = [1, 2];
// Error, can't convert 'number' return type to 'void'
[1, 2, 3].forEach(x => arr.push(x));

much worse, I agree, you sound more convincing than never
let arr = [1, 2];
// Error, can't convert 'number' return type to 'void'
[1, 2, 3].forEach(x => { arr.push(x); });

If that's sarcasm I'm missing it :stuck_out_tongue:

not much sarcasm in 3 extra characters


Validate remaining API with IBM OpenAPI Validator

[x] Date annotator
[x] Person name annotator
[x] Physical address annotator
[x] Deidentifier

Done in #81


dart fix applies the wrong fix for always-specify-types in const collection literals.

Dart SDK Version:  Dart SDK version: 3.1.0-46.0.dev (dev) (Tue Apr 25 23:35:50 2023 -0700) on "windows_x64"
Windows 11

So the issue is, when applying fixes for the rule always-specify-types as stated above, the result can be seen in this snippet of code:
/// Before applying the fix
Matrix<E> removed({Set<int> x = const {}, Set<int> y = const {}}) { ... }
/// After applying the fix
Matrix<E> removed({Set<int> x = <int>const {}, Set<int> y = <int>const {}}) { ... }
/// Expected behavior
Matrix<E> removed({Set<int> x = const <int>{}, Set<int> y = const <int>{}}) { ... }

/cc @pq @scheglov

https://dart-review.googlesource.com/c/sdk/+/300162


Desyncing

Product and Version [VS/VSCode]: VSCode
OS Version [macOS/Windows/Linux]: macOS
Live Share Extension Version: 1.0.2104
Target Platform or Language [e.g. Node.js]: Python
What were you doing when you encountered the desync?
Writing python code
How often have you encountered desyncs?
2 times in a period of 3 hours

So you were in a session for >1 hour before encountering the first desync? And then encountered another shortly after?

Yes @daytonellwanger . In the >1 period it wasn't idle, we were actively working on the collaboration.

Thanks for reporting this! I'm closing this as a duplicate of #2086, so we can focus the conversation in a single place.


[BUG] Editor sometimes crashes on Shift+Tab

Describe the bug
Sometimes, when pressing Shift+Tab the editor crashes when trying to delete the tab character before the cursor. Note that the crash doesn't happen with atto, possibly with older versions of femto as well.
To Reproduce
Steps to reproduce the behavior:

Open up editor
Go to some line with indentation
Move the cursor to a character just after the whitespace at the beginning of the line, like here:

Press Shift+Tab at least 2 times
See, that the editor crashes

Expected behavior
The editor shouldn't crash, obviously.
Desktop (please complete the following information):

OS: Windows 10 21H2
Version: 2.1

The last version not to have this issue is Release 2.1 RC4, anything higher than that has this issue with certainty.


Dev

uodate

Codecov Report

Merging #30 into master will increase coverage by 0.16%.
The diff coverage is 33.33%.

@@            Coverage Diff             @@
##           master      #30      +/-   ##
==========================================
+ Coverage   80.87%   81.03%   +0.16%
==========================================
  Files          16       16
  Lines        2039     2041       +2
==========================================
+ Hits         1649     1654       +5
+ Misses        390      387       -3

Impacted Files
Coverage Δ

src/show.jl
69.91% <ø> (+2.96%)
:arrow_up:

src/pk.jl
75.73% <ø> (+1.36%)
:arrow_up:

src/ci.jl
82.36% <0%> (-1.27%)
:arrow_down:

src/descriptives.jl
90.38% <55.55%> (-1.66%)
:arrow_down:

Continue to review full report at Codecov.

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


Fetch data on click event

Hi,
The way your plugin works is that data should be available when user click on the button. Is there any way to call web api service first, when user clicks on a button?
Thanks,
Igor

@korolei thank you for feedback. I will review it

yes. This will be a nice addition. I am also trying to modify the code and see if I can do it.

@abhimishra18 , great if have the help of you

u can pass a function(call server with data callback) to data and change click event code like this:

element.bind('click', function() {
scope.data(function (dt) {
var bodyData = _bodyData(dt);
var strData = _convertToExcel(bodyData);
var blob = new Blob([strData], {type: "text/plain;charset=utf-8"});
return saveAs(blob, [scope.filename + '.csv']);
});
});

@romeo-nxp callback function would not work, as it is asynchronous call and by the time data get back, _convertToExcel function will be called already. I solved this issue with using two buttons: 'Fetch Data' & ' Export Data'. Only one button visible at a time and user has to click twice to get data into Excel.

I achieved this my adding ng-mouseover="fetchResults()"
This is just a work around which can help if someone stuck at this point.


IPv6 addresses in AWS are only failed over if IPv4 addresses exist too

Do you already have an issue opened with F5 support?
No.
Description
CFE failover is working when I have IPv4 and IPv6 VIPs and they are both in Traffic Group 1. However CFE fails if:
a) I have no IPv4 addresses, only IPv6 VIPs, or
b) If my IPv4 addresses are in traffic group None and my IPv6 address is in Traffic Group 1.
CFE appears to ignore the IPv6 addresses unless it finds IPv4 addresses to move also.
Environment information
For bugs, enter the following information:

Cloud Failover Extension Version: 1.8
BIG-IP version: <IP_ADDRESS>
Cloud provider: AWS

Severity Level
For bugs, enter the bug severity level. Do not set any labels.
Severity: 4

This issue is being tracked internally with ID AUTOSDK-558.

Closing.
This issue was addressed with Release 1.10.


Improve eww get-active-workspace for multimonitor setup

The active workspace reacts to monitor focus as well using this script

Are you sure jq doesn't need -r to print without quotes? Or does it not affect the script?

Are you sure jq doesn't need -r to print without quotes? Or does it not affect the script?

Since the id is a number there is no quotes printed in the output. I can re-check in 2h if needed.

It's alright, I'll merge it as is.


Question: How would I define multiple services on one shared port?

Hi,
first of all thank you for this awesome project.
I would like to know how I can use a pub/sub and a req/rep via a websocket endpoint and binding both services on the same port.
my intention is to have one common socket to make all my communications (different patterns) with.
any example are appreciated.
thanks

To do this you need to create an HTTP server and use multiple sockets with it, using different paths on the server to identify the namespaces for different sockets (e.g. prefix/PUB  or prefix/SURVEYOR or some other string -- could be anything really).
Basically, what you do is use the OptionWebSocketMux on the listener, and then register that with a normal Http ServeMux.   This way you can use mangos even with lots of other middlewares.
I'll write an example.

You can use that example code.  Note that you must also have the fix for #258 -- which I integrated just prior to this example, in order for the example code to function.

this is awesome. thank you very much. I just tried it out. you must not specify the loopback address though. since you hardcoded tcp://<IP_ADDRESS> already. so in main.go url=tcp://<IP_ADDRESS>:40899 should be just url=40899 for easy copy pasting.


Lights for the robot

Descrition
The lights should correspond to something that's happening
Subsystem
Lights
Useful Knowledge
https://docs.wpilib.org/en/stable/docs/software/hardware-apis/misc/addressable-leds.html
Last Check

[X] I have labelled this issue with the priority and correct subsystem.

[ ] Wire power directly to PDH, not to rio so we don't fry the rio.


Issue #18 - NPE with Array generator

@djodjoni
Hi,
First of all, thanks for this project. Its really useful for my project.
I have fixed the NPE when minItems, maxItems is not set in the json schema when the type is 'array'.
Detailed issue description: https://github.com/apptik/JustJson/pull/17
I request you to do the code review and inform me if any changes are required.
Thanks,
Mohammed Rizwan

@djodjoni - Any idea when this fix can be merged?

Hey @Malligarjunan ! Thank you for the input! I will make a new release in the next days !

@djodjoni Latest jar available in maven doesnt have fix for NPE for arraygenerator as per issue #18. can you please share latest jar for NPE with ArrayGenerator


Implement MultiFrameImageStreamCompleter - handles scheduling for animated image frames

This CL requires https://github.com/flutter/engine/commit/2920d61a5c1a64e87be424d7dd4bd7a6c4cb3acc so expect Travis to be complaining until we successfully roll the engine.
https://github.com/flutter/flutter/issues/204

It's hard for me to 100% see if this is correct without also seeing the corresponding ImageProvider changes that use this, but LGTM so far.


Body from tokio::fs::File

Was it something like this you had in mind @seanmonstar ? In the comment you wrote here: https://github.com/seanmonstar/reqwest/pull/1357#pullrequestreview-782333115

Or should this be under the stream-feature?


Skip test test_del_model_attr_error to run on PyPy < 3.9

Fixes CI failure on pypy3.8

please review


Schedule

Ability to fill in...what?...to create a schedule. Not sure what users would find least painful. YML, possibly, with a template provided?

Yes YAML. Will implement.

Possibly have that day's schedule on the front page


Fix performance problem in rename implementation

Currently DataColumn object is used as a key for associateBy in rename implementation. It leads to computation of rolling hash function and scanning through all column data. This problem can be seen in stack trace for https://github.com/Kotlin/dataframe/issues/526
Instead, a column path should be used as column id.

Thanks! Could you rebase on the master so that the TeamCity tests pass (includes https://github.com/Kotlin/dataframe/pull/535) and assemble the project to make sure the doc processor is run and the generated-sources are updated? Then I can merge it :)

Done


chore: add nil checks and tweaks to gRPC handlers

Closes: #1224
Description

For contributor use:

[ ] Targeted PR against correct branch (see CONTRIBUTING.md)
[ ] Updated relevant documentation (docs/) or specification (x/<module>/spec/)
[ ] Added a relevant changelog entry to the Unreleased section in CHANGELOG.md
[ ] Re-reviewed Files changed in the Github PR explorer

Codecov Report

Merging #1238 (3492f3b) into main (20cfa05) will decrease coverage by 0.07%.
The diff coverage is 16.66%.

@@            Coverage Diff             @@
##             main    #1238      +/-   ##
==========================================
- Coverage   20.96%   20.89%   -0.08%
==========================================
  Files         196      196
  Lines       25337    25422      +85
==========================================
- Hits         5312     5311       -1
- Misses      19066    19119      +53
- Partials      959      992      +33

Impacted Files
Coverage Δ

x/epochs/keeper/grpc_query.go
35.71% <0.00%> (-5.96%)
:arrow_down:

x/gamm/keeper/grpc_query.go
42.95% <ø> (+0.74%)
:arrow_up:

x/incentives/keeper/grpc_query.go
48.00% <0.00%> (-7.82%)
:arrow_down:

x/pool-incentives/keeper/grpc_query.go
65.95% <0.00%> (-2.94%)
:arrow_down:

x/superfluid/keeper/grpc_query.go
46.84% <0.00%> (-9.68%)
:arrow_down:

x/txfees/keeper/grpc_query.go
20.00% <0.00%> (-5.00%)
:arrow_down:

x/lockup/keeper/grpc_query.go
54.86% <34.48%> (-18.08%)
:arrow_down:

Continue to review full report at Codecov.

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

LGTM!

@ValarDragon I'm not 100% sure. These methods come from the gRPC service generator. But something tells me the answer is no lol.


Create new teams css

The teams page doesn't have a link to the new teams CSS, so it isn't using it


Latest dev build crashes the backend server

🐛 Bug Report

[x] 📁 I've Included a ZIP file containing my librephotos log files
[x] ❌ I have looked for similar issues (including closed ones)
[ ] 🎬 (If applicable) I've provided pictures or links to videos that clearly demonstrate the issue

📝 Description of issue:
log.txt with the attached logs

Thanks for the report! Should be fixed now, as the demo server also works again.
I upgraded to Django 4.2, a new database driver and a new python version. That was probably too much to do all at once 😅


enhancement for datarangepicker  - reset values method

added a javascript method for datarangepicker that allows to reset velue.

Thanks for contribution!


use numpy array instead of tuple for indexing collections

starts #214

merging for now, will continue optimizing later


lisa.trace: Avoid forking multiprocessing.Pool

FIX
Since they can cause deadlocks in multithreaded applications, use the
"spawn" method even though it is slower.

Closing as the project has moved to https://gitlab.arm.com/tooling/lisa/


Update Futures and Tokio

With v0.5.0 I updated all dependencies except for the futures crate, since v0.2.x has been yanked, and tokio since I'm slightly afraid to touch that, for now. But eventually it must get done.
This is issue is a reminder to do so, eventually.

Not relevant anymore


Add more Algorithms under the Algorithms Directory.

What is the Issue in brief?
The Algorithm section requires more algorithms and a bit of organization.

Hey, Can you label it as Hacktoberfest2020 and Hacktoberfest-accepted?

Hey @DeepanshuGOYAL05 you can check your progress at https://hacktoberfest.digitalocean.com/profile

Hi, I can check that but please add label too in this!!


Question: Looking for examples

Hi, I'm looking at the Ontologies in this repo and trying to figure out how to use them. I wonder if some example RDF snippets exemplify how data looks like when using these ontologies.
I would be grateful if you could provide me with a pointer to examples or presentations about the concrete data.
Cristian.

Hi @cristianvasquez it depends on which ontologies you are interested in. Some of them provide examples (e.g., Indicator).  Which one are you looking at?

Hi!, thanks for the response
I was looking at them in general, I remember looking for RDF examples for point of Interest, time, prices, social media... An example can make the ontologies easier to understand and use...
Where can I see the example of Indicator?

Hi @cristianvasquez, for instance you can look at example-indicator files here https://github.com/italia/daf-ontologie-vocabolari-controllati/tree/master/Ontologie/Indicator/latest

@cristianvasquez I will close the issue if it is fine for you :)

Sure no problem!


Pagination Issues: Duplicated Maven Packages in GET API Responses

Description
When querying Maven packages from the Gitea using the endpoint {base_url}/packages/{owner}?page={page}&limit={PAGE_SIZE}&type=maven, duplicate entries appear across different pages, especially when the total number of packages is very large (like 20,000). Sometimes, if you request the same page again, the duplicate packages won't appear, showing that the way pages are filled with packages can be unpredictable. Additionally, if you make the same request multiple times, you might get different packages each time.
Gitea Version: a36636357
Deployment: The Gitea instance is running within a Kubernetes pod managed by Rancher.
Database Used: PostgreSQL 12.17-bullseye
Additional Context: This issue might be related to how pagination is implemented in the backend storage or indexing system used by Gitea for package management.
Steps to Reproduce

Send a GET request to {base_url}/packages/{owner}?page=1&limit=20&type=maven with a high total package count ( in our case more then 20000)
Note the packages returned and repeat the request for the same page.
Compare the results from both requests and note any duplicates.
Optionally, continue to the next page and check for overlap with previous pages.

Expected Behavior
Each page requested should return a unique set of packages without overlap, regardless of the number of times the same page is queried.
Actual Behavior
Some package entries are duplicated across multiple page results, and the same page request can yield different packages on subsequent queries.
Gitea Version
a36636357
Can you reproduce the bug on the Gitea demo site?
No
Log Gist
No response
Screenshots
No response
Git Version
No response
Operating System
Linux
How are you running Gitea?
The Gitea instance is running within a Kubernetes pod managed by Rancher.
Database
PostgreSQL

Do you know it that's a new problem? Then #30520 could be the reason.


Different result every time app re-load

I tried your package and I haven't found a solution to deal with different results each time my application reloads with one call

Trusted results can only be obtained by repeating as you write in the example folder. Are there other solutions to guarantee the results are correct without repeating by timer?

@young-altair I have added stream getter where you can use this without coding a timer in your source code. Code example here. trust_location

Thanks a lot !

I am facing a new problem with the latest version.
I want to use a stream in another class but the following error appears
[ERROR:flutter/lib/ui/ui_dart_state.cc(157)] Unhandled Exception: Bad state: Stream has already been listened to.

I changed the code as below
from
static var changeController = new StreamController<LatLongPosition>();

to
static var changeController = new StreamController<LatLongPosition>.broadcast();

Is this correct?

@young-altair Correct. Thank you for suggestion. I will update it with next release.