[BUG]  Unknown command: catalyst

Describe the bug
My cocoapods install with brew, in use cocoapods-catalyst-support,
when input: pod catalyst run, error:
pod catalyst run
[!] Unknown command: catalyst
Did you mean: list?
Podfile
Please provide your Podfile here.
Environment

cocoapods-catalyst-support => <run gem list | grep cocoapods-catalyst-support>
✅ cocoapods-catalyst-support (0.2.1)
Ruby version [e.g 2.6.0] => <run ruby --version>
✅ ruby 3.1.1p18 (2022-02-18 revision 53f5fc4236) [arm64-darwin21]
Cocoapods version [e.g 1.10.0] => <run pod --version>
✅ 1.11.3
Xcode version [e.g 12.2] => <run xcodebuild -version>
✅ Xcode 13.3.1 Build version 13E500a

Additional context
Add any other context about the problem here.

@Howard-Wang-Hao have you followed the Installation guide? I’d recommend you use Bundle and a Gemfile in your project. Home brew is not currently supported, see request here

Hello, I have followed your Installation & Usage guide.
But there are still errors,
Libraries that don't support Macs don't seem to be ruled out
pod catalyst run
Analyzing dependencies
Downloading dependencies
Generating Pods project
Configuring macos dependencies
Unsupported Libraries
[]
Unsupported dependencies
[]
Frameworks not to be included in the Archive
[]
Resources not to be included in the Archive
[]
Flagging unsupported libraries
Target: Alamofire
	Scheme: Dev_Debug
		Nothing to flag
	Scheme: Rel_Debug
		Nothing to flag
	Scheme: Qa_Debug
		Nothing to flag
	Scheme: Rel_Release
		Nothing to flag
	Scheme: Dev_Release
		Nothing to flag
	Scheme: Qa_Release
		Nothing to flag
Target: AliHACore
	Scheme: Dev_Debug
		Nothing to flag
	Scheme: Rel_Debug
		Nothing to flag
	Scheme: Qa_Debug
		Nothing to flag
	Scheme: Rel_Release
		Nothing to flag
	Scheme: Dev_Release
		Nothing to flag
	Scheme: Qa_Release
		Nothing to flag
Target: AliHALogEngine
	Scheme: Dev_Debug
		Nothing to flag
	Scheme: Rel_Debug
		Nothing to flag
	Scheme: Qa_Debug
		Nothing to flag
	Scheme: Rel_Release
		Nothing to flag
	Scheme: Dev_Release
		Nothing to flag
	Scheme: Qa_Release
		Nothing to flag
Target: AliHAMethodTrace
	Scheme: Dev_Debug
		Nothing to flag
	Scheme: Rel_Debug
		Nothing to flag
	Scheme: Qa_Debug
		Nothing to flag
	Scheme: Rel_Release
		Nothing to flag
	Scheme: Dev_Release
		Nothing to flag
	Scheme: Qa_Release
		Nothing to flag
Target: AliHAProtocol
	Scheme: Dev_Debug
		Nothing to flag
	Scheme: Rel_Debug
		Nothing to flag
	Scheme: Qa_Debug
		Nothing to flag
	Scheme: Rel_Release
		Nothing to flag
	Scheme: Dev_Release
		Nothing to flag
	Scheme: Qa_Release
		Nothing to flag
Target: AliHASecurity
	Scheme: Dev_Debug
		Nothing to flag
	Scheme: Rel_Debug
		Nothing to flag
	Scheme: Qa_Debug
		Nothing to flag
	Scheme: Rel_Release
		Nothing to flag
	Scheme: Dev_Release
		Nothing to flag
	Scheme: Qa_Release
		Nothing to flag
Target: AliRemoteDebugInterface
	Scheme: Dev_Debug
		Nothing to flag
	Scheme: Rel_Debug
		Nothing to flag
	Scheme: Qa_Debug
		Nothing to flag
	Scheme: Rel_Release
		Nothing to flag
	Scheme: Dev_Release
		Nothing to flag
	Scheme: Qa_Release
		Nothing to flag
Target: AlicloudHAUtil
	Scheme: Dev_Debug
		Nothing to flag
	Scheme: Rel_Debug
		Nothing to flag
	Scheme: Qa_Debug
		Nothing to flag
	Scheme: Rel_Release
		Nothing to flag
	Scheme: Dev_Release
		Nothing to flag
	Scheme: Qa_Release
		Nothing to flag
Target: AlicloudSettingService
	Scheme: Dev_Debug
		Nothing to flag
	Scheme: Rel_Debug
		Nothing to flag
	Scheme: Qa_Debug
		Nothing to flag
	Scheme: Rel_Release
		Nothing to flag
	Scheme: Dev_Release
		Nothing to flag
	Scheme: Qa_Release
		Nothing to flag
Target: AlicloudTLog
	Scheme: Dev_Debug
		Nothing to flag
	Scheme: Rel_Debug
		Nothing to flag
	Scheme: Qa_Debug
		Nothing to flag
	Scheme: Rel_Release
		Nothing to flag
	Scheme: Dev_Release
		Nothing to flag
	Scheme: Qa_Release
		Nothing to flag
Target: AlicloudUTDID
	Scheme: Dev_Debug
		Nothing to flag
	Scheme: Rel_Debug
		Nothing to flag
	Scheme: Qa_Debug
		Nothing to flag
	Scheme: Rel_Release
		Nothing to flag
	Scheme: Dev_Release
		Nothing to flag
	Scheme: Qa_Release
		Nothing to flag
Target: AlicloudUtils
	Scheme: Dev_Debug
		Nothing to flag
	Scheme: Rel_Debug
		Nothing to flag
	Scheme: Qa_Debug
		Nothing to flag
	Scheme: Rel_Release
		Nothing to flag
	Scheme: Dev_Release
		Nothing to flag
	Scheme: Qa_Release
		Nothing to flag
Target: AliyunOSSiOS
	Scheme: Dev_Debug
		Nothing to flag
	Scheme: Rel_Debug
		Nothing to flag
	Scheme: Qa_Debug
		Nothing to flag
	Scheme: Rel_Release
		Nothing to flag
	Scheme: Dev_Release
		Nothing to flag
	Scheme: Qa_Release
		Nothing to flag
Target: CryptoSwift
	Scheme: Dev_Debug
		Nothing to flag
	Scheme: Rel_Debug
		Nothing to flag
	Scheme: Qa_Debug
		Nothing to flag
	Scheme: Rel_Release
		Nothing to flag
	Scheme: Dev_Release
		Nothing to flag
	Scheme: Qa_Release
		Nothing to flag
Target: DeviceKit
	Scheme: Dev_Debug
		Nothing to flag
	Scheme: Rel_Debug
		Nothing to flag
	Scheme: Qa_Debug
		Nothing to flag
	Scheme: Rel_Release
		Nothing to flag
	Scheme: Dev_Release
		Nothing to flag
	Scheme: Qa_Release
		Nothing to flag
Target: EMASRest
	Scheme: Dev_Debug
		Nothing to flag
	Scheme: Rel_Debug
		Nothing to flag
	Scheme: Qa_Debug
		Nothing to flag
	Scheme: Rel_Release
		Nothing to flag
	Scheme: Dev_Release
		Nothing to flag
	Scheme: Qa_Release
		Nothing to flag
Target: FileKit
	Scheme: Dev_Debug
		Nothing to flag
	Scheme: Rel_Debug
		Nothing to flag
	Scheme: Qa_Debug
		Nothing to flag
	Scheme: Rel_Release
		Nothing to flag
	Scheme: Dev_Release
		Nothing to flag
	Scheme: Qa_Release
		Nothing to flag
Target: HiPosPrinter
	Scheme: Dev_Debug
		Nothing to flag
	Scheme: Rel_Debug
		Nothing to flag
	Scheme: Qa_Debug
		Nothing to flag
	Scheme: Rel_Release
		Nothing to flag
	Scheme: Dev_Release
		Nothing to flag
	Scheme: Qa_Release
		Nothing to flag
Target: IQKeyboardManagerSwift
	Scheme: Dev_Debug
		Nothing to flag
	Scheme: Rel_Debug
		Nothing to flag
	Scheme: Qa_Debug
		Nothing to flag
	Scheme: Rel_Release
		Nothing to flag
	Scheme: Dev_Release
		Nothing to flag
	Scheme: Qa_Release
		Nothing to flag
Target: Kingfisher
	Scheme: Dev_Debug
		Nothing to flag
	Scheme: Rel_Debug
		Nothing to flag
	Scheme: Qa_Debug
		Nothing to flag
	Scheme: Rel_Release
		Nothing to flag
	Scheme: Dev_Release
		Nothing to flag
	Scheme: Qa_Release
		Nothing to flag
Target: MJRefresh
	Scheme: Dev_Debug
		Nothing to flag
	Scheme: Rel_Debug
		Nothing to flag
	Scheme: Qa_Debug
		Nothing to flag
	Scheme: Rel_Release
		Nothing to flag
	Scheme: Dev_Release
		Nothing to flag
	Scheme: Qa_Release
		Nothing to flag
Target: MKProgress
	Scheme: Dev_Debug
		Nothing to flag
	Scheme: Rel_Debug
		Nothing to flag
	Scheme: Qa_Debug
		Nothing to flag
	Scheme: Rel_Release
		Nothing to flag
	Scheme: Dev_Release
		Nothing to flag
	Scheme: Qa_Release
		Nothing to flag
Target: MagicalRecord
	Scheme: Dev_Debug
		Nothing to flag
	Scheme: Rel_Debug
		Nothing to flag
	Scheme: Qa_Debug
		Nothing to flag
	Scheme: Rel_Release
		Nothing to flag
	Scheme: Dev_Release
		Nothing to flag
	Scheme: Qa_Release
		Nothing to flag
Target: Moya
	Scheme: Dev_Debug
		Nothing to flag
	Scheme: Rel_Debug
		Nothing to flag
	Scheme: Qa_Debug
		Nothing to flag
	Scheme: Rel_Release
		Nothing to flag
	Scheme: Dev_Release
		Nothing to flag
	Scheme: Qa_Release
		Nothing to flag
Target: ObjcExceptionBridging
	Scheme: Dev_Debug
		Nothing to flag
	Scheme: Rel_Debug
		Nothing to flag
	Scheme: Qa_Debug
		Nothing to flag
	Scheme: Rel_Release
		Nothing to flag
	Scheme: Dev_Release
		Nothing to flag
	Scheme: Qa_Release
		Nothing to flag
Target: ProgressHUD
	Scheme: Dev_Debug
		Nothing to flag
	Scheme: Rel_Debug
		Nothing to flag
	Scheme: Qa_Debug
		Nothing to flag
	Scheme: Rel_Release
		Nothing to flag
	Scheme: Dev_Release
		Nothing to flag
	Scheme: Qa_Release
		Nothing to flag
Target: RemoteDebugChannel
	Scheme: Dev_Debug
		Nothing to flag
	Scheme: Rel_Debug
		Nothing to flag
	Scheme: Qa_Debug
		Nothing to flag
	Scheme: Rel_Release
		Nothing to flag
	Scheme: Dev_Release
		Nothing to flag
	Scheme: Qa_Release
		Nothing to flag
Target: SPPermissions
	Scheme: Dev_Debug
		Nothing to flag
	Scheme: Rel_Debug
		Nothing to flag
	Scheme: Qa_Debug
		Nothing to flag
	Scheme: Rel_Release
		Nothing to flag
	Scheme: Dev_Release
		Nothing to flag
	Scheme: Qa_Release
		Nothing to flag
Target: SSZipArchive
	Scheme: Dev_Debug
		Nothing to flag
	Scheme: Rel_Debug
		Nothing to flag
	Scheme: Qa_Debug
		Nothing to flag
	Scheme: Rel_Release
		Nothing to flag
	Scheme: Dev_Release
		Nothing to flag
	Scheme: Qa_Release
		Nothing to flag
Target: SnapKit
	Scheme: Dev_Debug
		Nothing to flag
	Scheme: Rel_Debug
		Nothing to flag
	Scheme: Qa_Debug
		Nothing to flag
	Scheme: Rel_Release
		Nothing to flag
	Scheme: Dev_Release
		Nothing to flag
	Scheme: Qa_Release
		Nothing to flag
Target: Starscream
	Scheme: Dev_Debug
		Nothing to flag
	Scheme: Rel_Debug
		Nothing to flag
	Scheme: Qa_Debug
		Nothing to flag
	Scheme: Rel_Release
		Nothing to flag
	Scheme: Dev_Release
		Nothing to flag
	Scheme: Qa_Release
		Nothing to flag
Target: SwiftProtobuf
	Scheme: Dev_Debug
		Nothing to flag
	Scheme: Rel_Debug
		Nothing to flag
	Scheme: Qa_Debug
		Nothing to flag
	Scheme: Rel_Release
		Nothing to flag
	Scheme: Dev_Release
		Nothing to flag
	Scheme: Qa_Release
		Nothing to flag
Target: SwiftyGif
	Scheme: Dev_Debug
		Nothing to flag
	Scheme: Rel_Debug
		Nothing to flag
	Scheme: Qa_Debug
		Nothing to flag
	Scheme: Rel_Release
		Nothing to flag
	Scheme: Dev_Release
		Nothing to flag
	Scheme: Qa_Release
		Nothing to flag
Target: SwiftyJSON
	Scheme: Dev_Debug
		Nothing to flag
	Scheme: Rel_Debug
		Nothing to flag
	Scheme: Qa_Debug
		Nothing to flag
	Scheme: Rel_Release
		Nothing to flag
	Scheme: Dev_Release
		Nothing to flag
	Scheme: Qa_Release
		Nothing to flag
Target: TBJSONModel
	Scheme: Dev_Debug
		Nothing to flag
	Scheme: Rel_Debug
		Nothing to flag
	Scheme: Qa_Debug
		Nothing to flag
	Scheme: Rel_Release
		Nothing to flag
	Scheme: Dev_Release
		Nothing to flag
	Scheme: Qa_Release
		Nothing to flag
Target: TBRest
	Scheme: Dev_Debug
		Nothing to flag
	Scheme: Rel_Debug
		Nothing to flag
	Scheme: Qa_Debug
		Nothing to flag
	Scheme: Rel_Release
		Nothing to flag
	Scheme: Dev_Release
		Nothing to flag
	Scheme: Qa_Release
		Nothing to flag
Target: TRemoteDebugger
	Scheme: Dev_Debug
		Nothing to flag
	Scheme: Rel_Debug
		Nothing to flag
	Scheme: Qa_Debug
		Nothing to flag
	Scheme: Rel_Release
		Nothing to flag
	Scheme: Dev_Release
		Nothing to flag
	Scheme: Qa_Release
		Nothing to flag
Target: UMAPM
	Scheme: Dev_Debug
		Nothing to flag
	Scheme: Rel_Debug
		Nothing to flag
	Scheme: Qa_Debug
		Nothing to flag
	Scheme: Rel_Release
		Nothing to flag
	Scheme: Dev_Release
		Nothing to flag
	Scheme: Qa_Release
		Nothing to flag
Target: UMCCommonLog
	Scheme: Dev_Debug
		Nothing to flag
	Scheme: Rel_Debug
		Nothing to flag
	Scheme: Qa_Debug
		Nothing to flag
	Scheme: Rel_Release
		Nothing to flag
	Scheme: Dev_Release
		Nothing to flag
	Scheme: Qa_Release
		Nothing to flag
Target: UMCommon
	Scheme: Dev_Debug
		Nothing to flag
	Scheme: Rel_Debug
		Nothing to flag
	Scheme: Qa_Debug
		Nothing to flag
	Scheme: Rel_Release
		Nothing to flag
	Scheme: Dev_Release
		Nothing to flag
	Scheme: Qa_Release
		Nothing to flag
Target: UMDevice
	Scheme: Dev_Debug
		Nothing to flag
	Scheme: Rel_Debug
		Nothing to flag
	Scheme: Qa_Debug
		Nothing to flag
	Scheme: Rel_Release
		Nothing to flag
	Scheme: Dev_Release
		Nothing to flag
	Scheme: Qa_Release
		Nothing to flag
Target: UMPush
	Scheme: Dev_Debug
		Nothing to flag
	Scheme: Rel_Debug
		Nothing to flag
	Scheme: Qa_Debug
		Nothing to flag
	Scheme: Rel_Release
		Nothing to flag
	Scheme: Dev_Release
		Nothing to flag
	Scheme: Qa_Release
		Nothing to flag
Target: XCGLogger
	Scheme: Dev_Debug
		Nothing to flag
	Scheme: Rel_Debug
		Nothing to flag
	Scheme: Qa_Debug
		Nothing to flag
	Scheme: Rel_Release
		Nothing to flag
	Scheme: Dev_Release
		Nothing to flag
	Scheme: Qa_Release
		Nothing to flag
Target: ZipArchive
	Scheme: Dev_Debug
		Nothing to flag
	Scheme: Rel_Debug
		Nothing to flag
	Scheme: Qa_Debug
		Nothing to flag
	Scheme: Rel_Release
		Nothing to flag
	Scheme: Dev_Release
		Nothing to flag
	Scheme: Qa_Release
		Nothing to flag
Target: Pods-HiPOSHD_iPad
	Scheme: Dev_Debug
		Nothing to flag
	Scheme: Rel_Debug
		Nothing to flag
	Scheme: Qa_Debug
		Nothing to flag
	Scheme: Rel_Release
		Nothing to flag
	Scheme: Dev_Release
		Nothing to flag
	Scheme: Qa_Release
		Nothing to flag
Target: Pods-HiPOSHD_iPad-HiPOSHD_iPadUITests
	Scheme: Dev_Debug
		Nothing to flag
	Scheme: Rel_Debug
		Nothing to flag
	Scheme: Qa_Debug
		Nothing to flag
	Scheme: Rel_Release
		Nothing to flag
	Scheme: Dev_Release
		Nothing to flag
	Scheme: Qa_Release
		Nothing to flag
Target: Pods-HiPOSHD_iPadTests
	Scheme: Dev_Debug
		Nothing to flag
	Scheme: Rel_Debug
		Nothing to flag
	Scheme: Qa_Debug
		Nothing to flag
	Scheme: Rel_Release
		Nothing to flag
	Scheme: Dev_Release
		Nothing to flag
	Scheme: Qa_Release
		Nothing to flag

Filtering build phases
Filtering dependencies
Changing frameworks and resources script
Target: Pods-HiPOSHD_iPad
	-Uninstalling frameworks
		Uninstalling for configurations: ["Release", "Debug", "Dev_Debug", "Rel_Debug", "Qa_Debug", "Rel_Release", "Dev_Release", "Qa_Release"]
		Nothing to uninstall
	-Uninstalling resources
		Uninstalling for configurations: ["Release", "Debug", "Dev_Debug", "Rel_Debug", "Qa_Debug", "Rel_Release", "Dev_Release", "Qa_Release"]
		Nothing to uninstall
Target: Pods-HiPOSHD_iPad-HiPOSHD_iPadUITests
	-Uninstalling frameworks
		Uninstalling for configurations: ["Release", "Debug", "Dev_Debug", "Rel_Debug", "Qa_Debug", "Rel_Release", "Dev_Release", "Qa_Release"]
		Nothing to uninstall
	-Uninstalling resources
		Uninstalling for configurations: ["Release", "Debug", "Dev_Debug", "Rel_Debug", "Qa_Debug", "Rel_Release", "Dev_Release", "Qa_Release"]
		Nothing to uninstall
Target: Pods-HiPOSHD_iPadTests
	-Uninstalling frameworks
		Uninstalling for configurations: ["Release", "Debug", "Dev_Debug", "Rel_Debug", "Qa_Debug", "Rel_Release", "Dev_Release", "Qa_Release"]
		Nothing to uninstall
	-Uninstalling resources
		Uninstalling for configurations: ["Release", "Debug", "Dev_Debug", "Rel_Debug", "Qa_Debug", "Rel_Release", "Dev_Release", "Qa_Release"]
		Nothing to uninstall

Catalyst => Done! Your Catalyst dependencies are ready to go
Integrating client project
Pod installation complete! There are 29 dependencies from the Podfile and 44 total pods installed.

@fermoya Very confused, it seems that every step before compiling is not reported by mistake

@Howard-Wang-Hao i need your Podfile to make take a look at your dependency structure and how the way you're using the framework

Hi, it is:
require 'cocoapods-catalyst-support'
source "https://github.com/aliyun/aliyun-specs.git"
source 'https://cdn.cocoapods.org/'
Uncomment the next line to define a global platform for your project
platform :ios, '13.0'
Comment the next line if you don't want to use dynamic frameworks
use_frameworks!
target 'HiPOSHD_iPad' do
Pods for HiPOSHD_iPad
pod 'Moya'
pod 'SnapKit'
pod 'XCGLogger' #, '~> 7.0.1'
pod 'FileKit'   #, '~> 5.0.0'
pod 'SSZipArchive'
pod 'ProgressHUD'
pod 'MKProgress'
pod 'Kingfisher'
pod 'MagicalRecord'
pod 'SwiftyJSON', '~> 4.0'
pod 'Starscream'
pod 'IQKeyboardManagerSwift'
pod 'SwiftyGif'
pod 'MJRefresh'
pod 'SwiftProtobuf', '~> 1.0'
pod 'SPPermissions/Bluetooth'
pod 'SPPermissions/Location'
pod 'SPPermissions/Camera'
pod 'SPPermissions/Notification'
pod 'SPPermissions/Calendar'
pod 'UMCommon'
pod 'UMDevice'
pod 'UMPush'
pod 'UMAPM'
pod 'UMCCommonLog'
pod 'DeviceKit'
pod 'CryptoSwift'
pod 'AlicloudTLog'
target 'HiPOSHD_iPadTests' do
inherit! :search_paths
# Pods for testing
end
target 'HiPOSHD_iPadUITests' do
# Pods for testing
end
end
Configure your macCatalyst dependencies
catalyst_configuration do
# Uncomment the next line for a verbose output
verbose!
This dependency will only be available for iOS
ios ['UMCommon', 'UMDevice', 'UMPush', 'UMAPM', 'UMCCommonLog', 'AlicloudTLog']
This dependency will only be available for macOS
macos []
end
Configure your macCatalyst dependencies
post_install do |installer|
installer.configure_catalyst
end

@fermoya it is here

@fermoya Is there any problem？

Since it's not supported on Homebrew yet #21,  you should use gem.

In Gemfile
Add gem 'cocoapods-catalyst-support'


Doubt with pivx/miota

First of all I love your initiave and thanks for your work!
I'm interested on the new pivx feature but sadly I'm not really into this subject. Until now, I saved my shares until the moment I thought it was a good xmr/miota conversion and then I withdraw it. This was easy to me thanks to your info on the header. But now if I want to stack  my shares into pivx I'm not able to check it or at least to understand when is the best moment to do it.
Can you explain me how to do it? Or maybe add to the table the pvix/miota rate conversion too?
Thanks!

Hi,
thank you for support.
Yeah it is good point, I can make it more clear.
Conversion is very simple PIVX to BTC and BTC to IOTA.
Math: (pivxBtcPrice*userPivxBalance)/(miotaToBtcPrice/1000000)
So pivxBtcPrice = 0.00017050 PIVX/BTC
userPivxBalance = 0.5 PIVX
miotaToBtcPrice = 0.00007825 MillionIOTA/BTC
(0.00017050 * 0,5)/(0.00007825/1000000)
0,00008525/0,00000000007828
result = 1089039,34593766
So you get for 0,5PIVX 1089039 IOTA a.k. 1,089039 Miota
There is no fee, so you can verify calculation on your own.
I add this formula to Wiki. Thank you for tip.


chore: bump bb version to 0.54.0

Description
Problem*
Resolves
Summary*
This PR bumps bb so we can take advantage of some improvements to circuit generation.
Additional Context
Documentation*
Check one:

[x] No documentation needed.
[ ] Documentation included in this PR.
[ ] [For Experimental Features] Documentation to be submitted in a separate PR.

PR Checklist*

[x] I have tested the changes locally.
[x] I have formatted the changes with Prettier and/or cargo fmt on default settings.

Blocked by https://github.com/AztecProtocol/aztec-packages/pull/8486 and needing to do another release.


Yooooo! Don't commit your API Key :)

Lol i thought about this but i got it for free so i don’t care haha
Best,
Jacob McKenney
On May 13, 2022, 11:14 AM -0700, Spencer McKenney @.***>, wrote:

—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.Message ID: @.***>

This is what you use your secrets.json file for?
Best,
Jacob McKenney
On May 13, 2022, 11:27 AM -0700, Jacob Mckenney @.***>, wrote:

Lol i thought about this but i got it for free so i don’t care haha
Best,
Jacob McKenney
On May 13, 2022, 11:14 AM -0700, Spencer McKenney @.***>, wrote:

—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.Message ID: @.***>


Make vault clients export metrics with default values if no data is available

Context
When a vault client is running for a liquidated vault, some data is not exported anymore. This makes it difficult for the monitoring services to work properly as 'no data' would generally be considered a bug or faulty. To facilitate the monitoring and alerting of our vault clients we should change this to rather return a default value of instead.
TODO
We want to change the vault clients to keep exporting data for the following metrics, even if the vault is liquidated:

Locked collateral
Required collateral
Issue count
Stellar Balance
Redeem count
Collateralization

For the metrics that are not applicable for liquidated vaults, namely locked and required collateral as well as collateralization, we should return 0 instead. For the others, we can keep exporting the correct values.

@pendulum-chain/product this ticket helps improve our automated alerts as it allows to monitor vaults even when they are liquidated.

Hey team! Please add your planning poker estimate with Zenhub @b-yap @bogdanS98 @ebma @gianfra-t @TorstenStueber

@ebma all the listed fields show no data right now? For instance, even the redeem count for a liquidated vault.


⚠ Jenkins Plugins Artifactory has degraded performance

In 16cf62f, Jenkins Plugins Artifactory (https://get.jenkins.io/plugins/artifactory/) experienced degraded performance:

HTTP code: 200
Response time: 1225 ms

Resolved: Jenkins Plugins Artifactory performance has improved in 73d663d after 28 minutes.


Can't download from Tumblr, Error:null

Ripme version: 1.5.1
Java version (output of java -version): 1.8.0_91
Operating system: MacOS 10.12.5
Exact URL you were trying to rip when the problem occurred: http://ask-human-octavia.tumblr.com/post/152562762965/my-roommate-is-a-vampire-jerk-i-sometimes-forget
Please include any additional information about how to reproduce the problem:

Expected Behavior
Expected software to download all 3 pictures.
Actual Behavior
It looks like the download is starting and then it stops with the message: Error:null
Log:
Downloading http://api.tumblr.com/v2/blog/ask-human-octavia.tumblr.com/posts?id=159080635200&api_key=JFNLu3CbINQjRdUvZibXW9VpSEVYYtiPJ86o8YmvgLZIoKyuNX
Rip complete, saved to /Users/user/Desktop/RipMe/rips/tumblr_ask-human-octavia.tumblr.com_post_159080635200
null

I can't repo this
Tried on Ubuntu 16.04 using openJDK 1.8.0_131

Why are you on an old Java ?

@rautamiekka windows 10, java version "1.8.0_131" - same problem

Can confirm. I have the same problem.
Ripme v1.5.2
Java: 1.8.0_131
Windows 10

Expected Behavior
Expected software to download all 3 pictures.

Wait, you're trying just this single post?
Not sure, normally Ripme is used like this <user>.tumblr.com, i.e. the whole tumblr log.
Did it ever work on single post? Wasn't really taken into consideration, I think, because if all you want is some images from a single post, you can download them manually.

Problem was with api-key. It worked after its updating.

Please do this!!

Error while loading http://api.tumblr.com/v2/blog/ask-human-octavia.tumblr.com/posts?id=152562762965&api_key=JFNLu3CbINQjRdUvZibXW9VpSEVYYtiPJ86o8YmvgLZIoKyuNX
org.jsoup.HttpStatusException: HTTP error fetching URL. Status=429, URL=http://api.tumblr.com/v2/blog/ask-human-octavia.tumblr.com/posts?id=152562762965&api_key=JFNLu3CbINQjRdUvZibXW9VpSEVYYtiPJ86o8YmvgLZIoKyuNX
at org.jsoup.helper.HttpConnection$Response.execute(HttpConnection.java:459)
at org.jsoup.helper.HttpConnection$Response.execute(HttpConnection.java:434)
at org.jsoup.helper.HttpConnection.execute(HttpConnection.java:181)
at com.rarchives.ripme.utils.Http.response(Http.java:130)
at com.rarchives.ripme.utils.Http.getJSON(Http.java:120)
at com.rarchives.ripme.ripper.rippers.TumblrRipper.rip(TumblrRipper.java:122)
at com.rarchives.ripme.ripper.AbstractRipper.run(AbstractRipper.java:353)
at java.lang.Thread.run(Thread.java:745)
Got exception while running ripper:
java.lang.NullPointerException
at com.rarchives.ripme.ripper.rippers.TumblrRipper.handleJSON(TumblrRipper.java:182)
at com.rarchives.ripme.ripper.rippers.TumblrRipper.rip(TumblrRipper.java:159)
at com.rarchives.ripme.ripper.AbstractRipper.run(AbstractRipper.java:353)
at java.lang.Thread.run(Thread.java:745)
Waiting for threads to finish
Rip completed!
Getting 429(API limit reached) in logs.

I get the same issues. I get a HTTP 429 back.
{"meta":{"status":429,"msg":"Limit Exceeded"},"response":[],"errors":[{"title":"Limit Exceeded","detail":"It did not work"}]}

I think the solution is to allow the user to provide their own API key.
Cheers,
Indy

You can set your own API key within rip.properties


WIP [DUOS-1551][risk=no] DAR Collection Summary View - Application Information

First attempt at DUOS-1551

Extended ApplicationInformation to pull additional items from darInfo to populate items under the "Application Details" section.
Extended the AtAGlance component by adding a header for the table and started to write a function to handle pulling the data.
Added AtAGlanceCellData.js to store properties for the different "At A Glance" fields.
Need to complete the At A Glance table, and need to figure out how to get signing official email and IT director email for the Application Details
Need to add IRB protocol link?
Redo the page header to match the mock?

Have you read Terra's Contributing Guide lately? If not, do that first.

Label PR with a Jira ticket number and include a link to the ticket
Label PR with a security risk modifier [no, low, medium, high]
PR describes scope of changes
Get a minimum of one thumbs worth of review, preferably two if enough team members are available
Get PO sign-off for all non-trivial UI or workflow changes
Verify all tests go green
Test this change deployed correctly and works on dev environment after deployment

@quazi-broad - Pending Justin's feedback, 👍🏽. I don't see any additional commits after his comments. Please re-request a review if you do merge those in.


update nanovg,nanort,fix memory leaks

Thank! I will review changes at some point, but not so soon since it takes some time to review it.


[BUG] Can't build on NextJS 14 with typescript and app router

I tried to build two different projects with spline but I have the same error message each time :
TypeError: Super constructor null of anonymous class is not a constructor
    at new <anonymous> (/.next/server/app/page.js:6312:50455)

...

Error occurred prerendering page "/". Read more: https://nextjs.org/docs/messages/prerender-error

TypeError: Super constructor null of anonymous class is not a constructor
    at new <anonymous> (/.next/server/app/page.js:6312:50455)

I tried different thing with SSR on, SSR off, Suspense, Lazy loading etc ... but nothing change.
Package.json :
"dependencies": {
    "@gsap/react": "^2.1.0",
    "@hookform/resolvers": "^3.3.4",
    "@radix-ui/react-dropdown-menu": "^2.0.6",
    "@radix-ui/react-icons": "^1.3.0",
    "@radix-ui/react-label": "^2.0.2",
    "@radix-ui/react-slot": "^1.0.2",
    "@react-email/button": "^0.0.13",
    "@react-email/components": "^0.0.12",
    "@react-email/html": "^0.0.7",
    "@splinetool/react-spline": "^2.2.6",
    "@splinetool/runtime": "^1.6.8",
    "class-variance-authority": "^0.7.0",
    "clsx": "^2.0.0",
    "gsap": "^3.12.5",
    "lucide-react": "^0.323.0",
    "next": "14.1.1",
    "next-themes": "^0.2.1",
    "nodemailer": "^6.9.7",
    "react": "^18.2.0",
    "react-dom": "^18.2.0",
    "react-email": "^1.10.0",
    "react-hook-form": "^7.49.2",
    "react-icons": "^4.12.0",
    "resend": "^2.1.0",
    "sharp": "^0.33.1",
    "sonner": "^1.3.1",
    "tailwind-merge": "^2.2.1",
    "tailwindcss-animate": "^1.0.7",
    "zod": "^3.22.4"
  },
  "devDependencies": {
    "@testing-library/jest-dom": "^6.4.5",
    "@testing-library/react": "^16.0.0",
    "@types/node": "^20.8.8",
    "@types/react": "^18.2.31",
    "@types/react-dom": "^18.2.14",
    "autoprefixer": "^10.4.16",
    "eslint": "^8.56.0",
    "eslint-config-next": "14.1.0",
    "jest": "^29.7.0",
    "jest-environment-jsdom": "^29.7.0",
    "postcss": "^8.4.31",
    "prettier": "3.2.5",
    "prettier-plugin-tailwindcss": "^0.5.11",
    "tailwindcss": "^3.3.3",
    "ts-node": "^10.9.2",
    "typescript": "^5.2.2"
  }

Any updates on this?

Same issue on my end. Working locally is fine with pnpm dev, but as soon as do pnpm build and then pnpm start it throws the error, as well as on production.

Bumping Next to "next": "14.2.4" solved the issue for me!

Bumping Next to "next": "14.2.4" solved the issue for me!

Worked for me too! Thanks 😊

Upgrading to latest version of next i.e. 15.0.3 for now, worked for me✌


Support of the native builds without Docker.

Would be nice if you will reconsider the support of the "native" builds without Docker usage. There are many projects that own their servers, thus the using Docker just wastes the performance which can be used for building itself. Currently we are using Jenkins but it would be awesome to finally ditch it in favor of more lightweight solution (and less control complexity).

native builds remains out of scope. If something changes we will re-open https://github.com/drone/drone/issues/135


how to execute the given  swagger api

Library name and version
swagger
Query/Question
how to execute the given  swagger api
Environment
No response

Hi @SatyaRvnkr.  Thank you for reaching out and we regret that you're experiencing difficulties.  Unfortunately, this repository is focused on the Azure SDK for .NET - we're unable to assist with other issues.  Since what you're describing appears to be related to OpenAPI (swagger) and not one of the Azure SDKs, it is not something that we can help with.
I'm going to close this out; if I've misunderstood what you're describing, please let us know in a comment and we'd be happy to assist as we're able.

Thank you for your response
On Wed, Dec 21, 2022 at 7:40 PM Jesse Squire @.***>
wrote:

Closed #33138 https://github.com/Azure/azure-sdk-for-net/issues/33138
as completed.
—
Reply to this email directly, view it on GitHub
https://github.com/Azure/azure-sdk-for-net/issues/33138#event-8087626266,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/A44K6VLIUTGQXKIJRY5FDATWOMFV7ANCNFSM6AAAAAATFKFJJU
.
You are receiving this because you were mentioned.Message ID:
@.***>


Add OpenAPI based validation to LitmusChaos CRDs

As the Chaos CRD schema evolves (point-in-case: the configmap and secret support for experiments), there is an need to enforce schema validation at the CRD level to ensure:

That the right values are provided by users
To avoid a significant chunk on code to validate the data provided in the custom resources

The OpenAPI Spec based validation is now supported across different Kubernetes versions (1.8 onwards) and should be used against the chaos CRDs.

Started making the changes into the LitmusChaos CRDs. Ref the WIP PR: https://github.com/litmuschaos/chaos-operator/pull/104

Skipping docs as this is an internal/non-user facing change.

Fixed by https://github.com/litmuschaos/chaos-operator/pull/104


Inconsistent gdr read latency

I have a memory allocator based on gdr which initially allocates a large chunk of gdr memory (e.g. 16 MB) and then allocates pieces of this chunk to the subsequent memory requests. During performance benchmarking, I noticed that the read latency of the same memory size fluctuates quite significantly and I can't understand why. For example, if I allocate 3KB memory read 100 times and do the same thing again and again, the average read time fluctuates between 4.5 us and 70 us (i.e. 4.5 -> 70 -> 4.5 -> 70 ...) even though the same piece of memory is allocated for every 100 reads.
Here are some details regarding my settings:

I have set CU_POINTER_ATTRIBUTE_SYNC_MEMOPS to 1 for the entire chunk using cuPointerSetAttribute.
The api reports "using SSE4_1 implementation of gdr_copy_from_bar" for read operation.
The data is read into page-locked host memory allocated using cudaMallocHost.
Both the gdr-mapped source pointer and the destination pointer are 128-bit aligned.
The write latency is quite consistent.

Hi @anaanimous,
CPU and GPU clocks are usually the main cause (but not always) of performance fluctuation. Can you try the items below and rerun your test again?

Fix the CPU clock or at least set your power governance to "performance" sudo cpupower frequency-set -g performance.
Please also set the GPU clocks to max.

# To view the max clock values of GPU 0
$ nvidia-smi -i 0 -q
...
    Max Clocks
        Graphics                          : 1410 MHz
        SM                                : 1410 MHz
        Memory                            : 1593 MHz
        Video                             : 1290 MHz
...

# To set the clocks of GPU 0 to max
$ sudo nvidia-smi -i 0 -ac 1539,1410

Thank you for the quick response.
I have been running the benchmark on an AWS instance. However, today after running the same program on a local server, the performance has been stable. I don't know what's causing the fluctuation on AWS. It may be due to frequency scaling but I doubt it. Here is why:
I have a benchmark program where I measure the read latency for different sizes (1, 2, 4, ..., 1MB), similar to the copylat program, except that I use my allocator and its APIs to allocate memory and perform the reading. If I run this program on a local server the performance nicely matches that of the copylat. But on AWS the read latency for sizes above 512 bytes suddenly increases significantly (e.g. the latency of reading 512 bytes goes from 1.5 us to 12 us). But strangely enough, if I only skip the one-byte read (i.e. if I perform the test for 2, 4, ..., 1MB instead of 1, 2,... 1MB) the numbers match the copylat output.

Let's split into two topics here. The first one is the performance fluctuation, which seems to be resolved now. Depending on how your instance is allocated, I guess that you might share the host with other instances. I cannot say much about the performance predictability if you are not in full control of the entire system. There are so many external factors that can affect the performance.
The second topic is about the reading latency jumps to 12 us when reading 512 bytes. Can you share the code? I will try to reproduce this behavior on our system.


missing files？

├── modelnet40_half1_rm_rotate.txt
├── modelnet40_half2_rm_rotate.txt
Where can I get these two files？thanks

Hi,
Sorry for the late reply. These two files contain the names of the training and test categories (ModelNet40 dataset). The axisymmetrical categories are removed from the original ModelNet40 dataset, and you can download these two files here.


External markup renderer [$15]

See gogits/gogs#211 and gogits/gogs#2097.
Most Python-related projects use reStructuredText .rst instead of markdown files, for README.rst and documentation.  Sometimes other markup languages are used, or markdown with extensions currently not supported by Gitea.  GitHub supports the following markups: https://github.com/github/markup/.
I propose the following feature:
[markup]
; List of file extensions that should be rendered by an external command
FILE_EXTENSIONS = .rst,.rest,.restx
; External command to render all matching extensions
RENDER_COMMAND = "rst2html.py --no-raw"

If, for example, the file README.rst exists, its first 1024 bytes will be passed into stdin of rst2html.py --no-raw and stdout will be displayed as html for the file preview.
An optional %s will be replaced by the matched file extension (so that one can write a script that handles both .rst and .asciidoc).
As such a feature would be important to me, I am willing to implement this proposal, assuming there is a good chance it will be merged into master.  Let me know if I can start working on it.

There is a $15 open bounty on this issue. Add to the bounty at Bountysource.

Depending on external tools for rendering content is not really our goal

The default can be empty, then it's not a dependency and more like plugin interface.

We could find a go lib to do that

It seems there isn't any mature Golang library to do that. So maybe give a config like @plemp said, but default is closed currently.

IMO adding external renderers isn't a bad idea, could be made with a simple list.
Have a simple schema to identify arguments, basically injecting .InFile and .OutFile
Example:
EXTERNAL_RENDER = .rst:/usr/bin/rst2html5 {{ .InFile }} > {{ .OutFile }}

given
renderParam := struct {
  InFile  string
  OutFile string
}{"foo.rst", "/tmp/gitea-1337/foo.html"}

would generate /usr/bin/rst2html5 foo.rst > /tmp/gitea-1337/foo.html

I would prefer to integrate a real plugin system instead of increasing the current config more and more

Well I guess I'm just here to vote for .asciidoc the rich format and feature is offers have make it a defacto tools in our product chain.

@tboerger maybe external renderer is better choice, because asciidoc is an extensible format. the renderer itself should have a plugin system.

I recently did a quick-and-dirty hack on Gogs to add some basic .rst support for our own use, but maybe you will also find it useful:
https://github.com/AlphaGriffin/gogs

@lannocc great! I will try to merge it on v1.3

After #2525 merged, I will try to add reStructuredText support based on github.com/hhatto/gorst and https://github.com/AlphaGriffin/gogs. And I think that should be easy since that a new document type only implementation markup.Parser.

And for asciidoc, since github.com/VonC/asciidocgo could be imported.

@plemp, It seems there is no golang lib to handle asciidoc well. don't know how to use github.com/VonC/asciidocgo.

Any update on this one?
@lunny https://godoc.org/github.com/VonC/asciidocgo documentation looks good to me

@lenisko #2570 will support external render commands.

@lunny: Bountysource keeps telling me "Your application has been suspended" and throws various {"error":"Internal server error."} responses, keeping me from releasing the bounty. The mails I got from them uniquely say that if I "don't respond" you will get the bounty paid out at 2017-11-21. Sorry for that delay!
Could you check back at that date and - please - get in touch with me[1], should Bountysource fail to pay the bounty.
Thank you - and all contributors - for your continuous work on Gitea!

[1] via GitHub or<EMAIL_ADDRESS>

@tantegerda1 OK. Thanks for your bounty.

Getting this working was as simple as

Installing docutils (didn't even need root for that!)
Ensuring PATH contains $HOME/.local/bin
Appending a small snippet to app.ini:

[markup.restructuredtext]
ENABLED = true
FILE_EXTENSIONS = .rst
RENDER_COMMAND = rst2html.py
IS_INPUT_FILE = false

Restart the server 👍…and DONE! Readme.rst renders just as prettily on my selfhost as on GitHub! 🎉

However, what I am wondering is: isn't this a security nightmare? How quick+easy would it be for some sufficiently clever person to monkey into existence a Readme.rst that, when uploaded, would allow doing things not otherwise doable on the server?

Although, a small P.S. to the previous comment:

Installing…
Ensuring…
Adding a small snippet…
Restart…!

Is the above explicitly documented anywhere beyond the associated thread for 62d0a4d8829f214af4f9c00ecf8a81907d86ef06, #2750 in GitHub's walled-garden forum?

@JamesTheAwesomeDude it is definitely a security problem in that situation. I wouldn't say it is a complete nightmare, however, because you can write a wrapper for your external renderer that takes one or more steps to isolate it from your server environment, e.g.:

Run it in a firejail
Run it in an ephemeral KVM VM
Run it on another computer entirely

You're still left with the problem of the returned html being untrusted, but you can at least prevent attacks on the external renderer(s) from being able to perform arbitrary actions on the server.

@Shados Just to expand on that a bit,
since rst2html.py is seemingly only having stdio used, I guess it'd pretty simple to set up something like the way FastCGI servers work, just assign the wrapper/offloader script to RENDER_COMMAND.
But I really am concerned at the scarcity of documentation on this; as I mentioned before, you've got to manually hunt down the information yourself to make this work..I might have to stick something in the Wiki, maybe...

Although, re:"the problem of the returned html being untrusted",
It does look like Gitea (and Github itself, for that matter) actually sanitizes it pretty violently...for instance,
.. note:: HTML is sanitized

renders to the browser merely to:

Note

HTML is sanitized

with absolutely no styling at all, not even an indication that the word "Note" is a header for the following content, no indent for the note itself....anything
(same with warning, etc)


Push Notification Not Working On iOS with cordova-plugin-fcm-with-dependency-updated .

Hello @andrehtissot & all i am facing problem with push notification with iOS application but its completely working fine with android (i have build an ionic cordova hybrid application).
I think the push notification was working fine before i updating iOS 16.1 SDK (xcode 14.3).
Issues i m facing while building: (ionic cordova build ios --configuration production --release)

but when i do edit the pod file with a specific version ~> 7.4.0 (Firebase/Messaging version) and do pod install  and then build it again then it got build successfully without any error and all functionality is working perfectly in the application but the push notification is not working.
Note: if i m putting any other versions except 7.4.0 the pod install is getting succeeded but the build is getting failed.
Pod File:

to

pod install:

node version:
v14.17.3
npm version
6.14.13
cordova version
11.1.0
ionic version
5.4.16
Pod version(cocoapods)
1.11.2
System:
macOS Ventura (13.2.1)
Xcode 14.3
Thank you!

I am also working on a Ionic (hybrid) APP and this plugin is working fine on Android.
On IOS it is compiled successfully, but the notifications no more arrive on  Apple devices.
It was working fine until mid August 2023. Is it anything changed on Firebase side?

Hello @carlo318 its the same case with me also. I tired finding on firebase side but didn't get anything there.Please let me know if you get any solution to this issue, It will be a great help.
Thank you !

Hi @vivekkumarbiswal finally I solved with these 2 actions:

reinstalling the plugin with ALL the parameters suggested in the ReadMe:

ionic cordova plugin add cordova-plugin-fcm-with-dependecy-updated   --variable ANDROID_DEFAULT_NOTIFICATION_ICON="@mipmap/ic_launcher"   --variable ANDROID_FIREBASE_BOM_VERSION="26.0.0"    --variable ANDROID_GOOGLE_SERVICES_VERSION="4.3.4"   --variable ANDROID_GRADLE_TOOLS_VERSION="4.1.0"    --variable IOS_FIREBASE_MESSAGING_VERSION="~> 7.4.0"

Inserting the explicit request for the Permission to receive the Push Notifications:

const wasPermissionGiven = await FCM.requestPushPermission({  });
If still not working, try removing the platform IOS, remove the plugin, reinstall the plugin, then reinstall the platform IOS.

Hi @vivekkumarbiswal finally I solved with these 2 actions:

reinstalling the plugin with ALL the parameters suggested in the ReadMe:

ionic cordova plugin add cordova-plugin-fcm-with-dependecy-updated --variable ANDROID_DEFAULT_NOTIFICATION_ICON="@mipmap/ic_launcher" --variable ANDROID_FIREBASE_BOM_VERSION="26.0.0" --variable ANDROID_GOOGLE_SERVICES_VERSION="4.3.4" --variable ANDROID_GRADLE_TOOLS_VERSION="4.1.0" --variable IOS_FIREBASE_MESSAGING_VERSION="~> 7.4.0"

Inserting the explicit request for the Permission to receive the Push Notifications:

const wasPermissionGiven = await FCM.requestPushPermission({ });
If still not working, try removing the platform IOS, remove the plugin, reinstall the plugin, then reinstall the platform IOS.

Hello @carlo318 i tried reinstalling the plugin its failing and i tried removing platform(ios) and plugin, i m able to install the plugin but while adding platform its giving the same error :
Installing "cordova-plugin-fcm-with-dependecy-updated" for ios
Running command: pod install --verbose
Failed to install 'cordova-plugin-fcm-with-dependecy-updated': Error: pod: Command failed with exit code 1
at ChildProcess.whenDone (/Users/vivekbiswal/Documents/IOS/Push Notification/website/FSPortal/node_modules/cordova-common/src/superspawn.js:135:23)
at ChildProcess.emit (events.js:375:28)
at maybeClose (internal/child_process.js:1055:16)
at Process.ChildProcess._handle.onexit (internal/child_process.js:288:5)
pod: Command failed with exit code 1
[ERROR] An error occurred while running subprocess cordova.
cordova platform add ios exited with exit code 1.
Re-running this command with the --verbose flag may provide more information.
do you know how to resolve this ?

I am sorry I don't know how to help you, I don't get that error.

It got resolved as the issue is not with the plugin its because my app was not using the FCM request push permission, after putting the FCM request push permission its working now.

It got resolved as the issue is not with the plugin its because my app was not using the FCM request push permission, after putting the FCM request push permission its working now.

Is it working on the Android 13 & the latest iOS? Are you able to receive the Push notification successfully?


Export ServiceToken for cross-stack references

Now that CF has cross-stack references, would it make sense to export the Lambda ARN so that stacks can retrieve it using ImportValue?
Note that the exported names are global to the account and region, so you might want to qualify it with the stack name of the creating stack, e.g. {StackName}:APIGatewayCloudFormation:ServiceToken
Or perhaps there's another simple way to do this that I'm not aware of.

That's not a bad idea since it would be a backwards compatible change unlike naming the function.

I'd really like this functionality, would you accept a PR?

Sure!
On Thu, Apr 27, 2017, 12:12 Stefano Vozza<EMAIL_ADDRESS>wrote:

I'd really like this functionality, would you accept a PR?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/carlnordenfelt/aws-api-gateway-for-cloudformation/issues/51#issuecomment-297672796,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AEzRoXcFkuEoXmhovKDY1SpiPY419zY7ks5r0GoOgaJpZM4Kvx9C
.

Great! Do you mind if I convert the template to yaml?

I would prefer if you didn't do that :)
On Thu, Apr 27, 2017, 16:28 Stefano Vozza<EMAIL_ADDRESS>wrote:

Great! Do you mind if I convert the template to yaml?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/carlnordenfelt/aws-api-gateway-for-cloudformation/issues/51#issuecomment-297729852,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AEzRoQGNp2hjaA0_lnTQra_vS8FFVoLlks5r0KX6gaJpZM4Kvx9C
.

No probs, that's why I thought I'd ask first!


Crash - [FPRClient logTrace:]_block_invoke

Description
Hi, we have an issue with the Firebase sdk. This issue already asked and mark as fixed on the version 8.6.0 in this issue:
https://github.com/firebase/firebase-ios-sdk/issues/8545
But we're using version 8.15.0 and this crash still happen, could you help me to check this?
Here is my crash log:
Reproducing the issue
No response
Firebase SDK Version
8.15.0
Xcode Version
14.1
Installation Method
Swift Package Manager
Firebase Product(s)
Analytics, Crashlytics, Performance
Targeted Platforms
iOS
Relevant Log Output
Crashed: com.google.perf.sessionIds.trace

0  libobjc.A.dylib                0x2e5c objc_retain_x0 + 16
1  libobjc.A.dylib                0x2e5c objc_retain + 16
2  CoreFoundation                 0x71ffc __NSSingleObjectArrayI_new + 88
3  CoreFoundation                 0x5238 -[NSArray initWithArray:range:copyItems:] + 368
4  MyApp                       0x15753f0 __20-[FIRTrace sessions]_block_invoke + 239 (FIRTrace.m:239)
5  libdispatch.dylib              0x3fdc _dispatch_client_callout + 20
6  libdispatch.dylib              0x13574 _dispatch_lane_barrier_sync_invoke_and_complete + 56
7  MyApp                       0x1575344 -[FIRTrace sessions] + 238 (FIRTrace.m:238)
8  MyApp                       0x1563ae8 FPRGetTraceMetric + 286 (FPRNanoPbUtils.m:286)
9  MyApp                       0x1561250 __22-[FPRClient logTrace:]_block_invoke + 174 (FPRClient.m:174)
10 libdispatch.dylib              0x24b4 _dispatch_call_block_and_release + 32
11 libdispatch.dylib              0x3fdc _dispatch_client_callout + 20
12 libdispatch.dylib              0xb774 _dispatch_lane_serial_drain + 896
13 libdispatch.dylib              0xc1e0 _dispatch_lane_invoke + 384
14 libdispatch.dylib              0x16e10 _dispatch_workloop_worker_thread + 652
15 libsystem_pthread.dylib        0xdf8 _pthread_wqthread + 288
16 libsystem_pthread.dylib        0xb98 start_wqthread + 8

If using Swift Package Manager, the project's Package.resolved

Expand Package.resolved snippet

Replace this line with the contents of your Package.resolved.

If using CocoaPods, the project's Podfile.lock

Expand Podfile.lock snippet

Replace this line with the contents of your Podfile.lock!

Thanks for reporting, @tamv-ika. Is the issue reproducible using the latest SDK version?

Hi @rizafran, as I mentioned on the #10522, both issues are reported from firebase Crashlytics and run on version 8.15.0. And I havent update to the lastest SDK version. So I don't know does this issues exist in the lastest one.

Thanks @tamv-ika for sharing the stack trace. Looking at the crashed line, Firebase performance does a copy of an object. It is hard to see a reason why this could lead to a crash (Probably copy of items could lead to a crash, but chances are really low I'm hoping).

Similar to the other issue, can you provide the full stack trace of what other threads were doing at the time of the crash?
Can you also provide some details about the iOS version where this issue happens more often?

@visumickey, thanks for sharing the information. I don't have full snapshot of the application stack trace at the time of crash.
I also look at the crashed line you found, and I did some investigation based on your theory of race condition. I did a little search and I saw that all the modifications of the activeSessions was made in a serial queue sessionIdSerialQueue except the creation is made in the callee thread. In the crashed line the result is also got from the sessionIdSerialQueue => difficult to have race condition here. But I've notice a thing, dispatch_queue is use in sync which mean it will put a task into the sessionIdSerialQueue and do a wait in the current callee queue => become a deadlock if these two queues are in the same runloop. But in the crash log above this deadlock didn't happen. So the problem is caused by the copy function. I can't go further :(.

Since this issue hasn't had any updates recently and I am not able to reproduce it, I am closing this issue. If this issue occurs again, please file a new issue with information about your current environment. Thank you


Installation Instructions for pysatCDF in Windows OS.

Coverage remained the same at 86.523% when pulling a89a09231c59d5759f3014a6354843454dbaf1d1 on Gayatri012:WindowsInstallation into 642fceae46c07444a4e1fbe08312750cc86b8339 on rstoneback:master.


[WIP] Flughafen München facelift

München is Munich.

[ ] Update STARs
[ ] Revise traffic

If someone could assist with terrain, it'd be highly appreciated - my PC cannot handle the natural neighbour process.

@indianbhaji Unfortunately, I tried creating the terrain for München in the past, but due to some of the limitations of the current method for generating terrain, a lot of errors come up. I'll try again, but I don't think I'll be able to get it to work.

@Fechulo Alright, tell me the result, if it doesn't work, we'll just leave it. Thanks!

Is this still being held?

@erikquinn @indianbhaji To be honest, I haven't tried adding terrain since the last time, but I don't think I'll be able to make it work. The method we're using to generate the terrain works fine, but it's not perfect. Unfortunately, all of the imperfections of this method come up when trying to generate the terrain for EDDM.

This is actually held because I haven't finished all the SIDs due to my poor prioritisation.

Relocated to openscope/openscope#98, closing!


Change ctrl s to download .scn file instead of json

Describe your changes
Saves a .scn when user presses ctrl s, which can be easily re-uploaded. Requested by creators to speed up development workflow and use the app as an editor.
What are the steps for a QA tester to test this pull request?
Press ctrl s
Scene should be saved
Verify that scene works by dragging back into window to load
Issue ticket number and link
https://github.com/webaverse/app/issues/3652
Checklist before requesting a review

[x] I have performed a self-review of my code
[x] I am not adding any irrelevant code or assets
[x] I am only including the changes needed to implement the change
[x] I have playtested and intentionally tried to find error cases but couldn't

Closed in favor of Upstreet PR


Supported?

Is this library supported anymore?  Any chance some of the PRs or issues will be dealt with?
For my use cases, it would be great to have better support for optional fields.

Hi! All of my personal GitHub notifications were flooded with work stuff for the past couple years so I never saw this, my apologies.
I don't really write front end stuff too much anymore, or TypeScript/JavaScript at all for that matter, so I don't imagine myself spending too much time on maintenance here. It's kind of a lot of work to load all this context up into my brain when issues come up. That said, I'll try to go through all of the open issues and PRs this week.
Do you have any specific features in mind for optional fields that you'd like to see?

Similar to you, I don't have as much time for the project I was using which uses this anymore either. I remember having to do a bit of extra work to get the field supported the way I needed, but I don't remember what, specifically.  So no worries if you don't get around to it.


Fix typo in launch instructions

The command to launch JupyterLab is jupyter lab, not jupyter-lab.

I think it is jupyter-lab on certain Windows distributions, unless it has recently changed. But yes on UNIX it is with space.

jupyter-lab also does work on macOS, but I'm so used to jupyter lab that it looked like a typo to me.


CUDA error: out of memory

Hello,
I'm currently in the process of attempting to replicate the remarkable work you've shared. However, I've encountered a hurdle along the way. Following the training pipeline outlined in the repository and adhering to the provided requirements, I attempted to train the DHE-VPR using 4090 with 24GB graphics memory, same size with the 3090 . Unfortunately, after training for 1 epoch, the program crashed and reported the following issue:

Traceback (most recent call last):
File "/home/xx/Documents/codespace/DHE-VPR/train_dhe.py", line 151, in
REIloss = homography_project.reprojection_error_ofinliers(model, queries_fw, positives_fw, weights=random_weights)
File "/home/xx/Documents/codespace/DHE-VPR/homography_project.py", line 102, in reprojection_error_ofinliers
reproject_error[i] = match_batch_tensor(query, pred, theta, trainflag=True, img_size=(384,384))
File "/home/xx/Documents/codespace/DHE-VPR/homography_project.py", line 31, in match_batch_tensor
max1 = torch.argmax(M, dim=1) #(N,l)
RuntimeError: CUDA error: out of memory

I believe this issue is related to memory allocation on the CUDA device. Your expertise and guidance in resolving this problem would be immensely valuable to me
Thank you for your time

Hello, thanks for your interest in our work. Run train_dhe.py will take up about 12G memory on GPU. Is it possible that other programs are already taking up some memory while you are running this program? You can also reduce the batch_size and try again.


[docs] Missing documentation dependency 'autodocsumm' on docs/README.txt

When testing a new tutorial I'm writing about TVMC, I noticed that the guidance to generate docs is missing one plugin: autodocsumm.
If this is not present you'll see an error like this:
$ ./tests/scripts/task_sphinx_precheck.sh
cd python; python3 setup.py build_ext --inplace
WARNING: Cython is not installed, will compile without cython module
running build_ext
PreCheck sphinx doc generation WARNINGS..
rm -rf _build/*
rm -rf gen_modules
rm -rf tutorials
rm -rf vta/tutorials
python3 -m sphinx -b html -d _build/doctrees   . _build/html
Running Sphinx v3.2.1

Extension error:
Could not import extension autodocsumm (exception: No module named 'autodocsumm')
Makefile:70: recipe for target 'html' failed
make: *** [html] Error 2

cc @tqchen

Thanks @leandron !


Config option "connectionTimeout" is not honored

Attempting to change the configuration to include connectionTimeout: 30000 has made no difference in both the latest and a previous version of the mssql module.
Error code is as follows, reflecting default 15,000ms limit:
{ [RequestError: Timeout: Request failed to complete in 15000ms]
  name: 'RequestError',
  message: 'Timeout: Request failed to complete in 15000ms',
  code: 'ETIMEOUT',
  number: 'ETIMEOUT',
  lineNumber: undefined,
  state: undefined,
  class: undefined,
  serverName: undefined,
  procName: undefined,
  precedingErrors: [] }

try setting requestTimeout since you are able to connect, it's the request that is timing out...
see: http://pekim.github.io/tedious/api-connection.html

Must have missed that in the configuration options.
Thank you, this has fixed the problem.


Unable to use aspect="equal" in plot.imshow() whereas option is given in the doc

What is your issue?
I'm using the version 2023.12.0.
In the doc of imshow (https://docs.xarray.dev/en/stable/generated/xarray.DataArray.plot.imshow.html) it is written for the aspect parameter:

aspect ("auto", "equal", scalar or None, optional) – Aspect ratio of plot, so that aspect * size gives the width in inches. Only used if a size is provided.

But if I try this simple code:
import xarray as xr
import numpy as np
import matplotlib.pyplot as plt

data_array = np.random.randint(0, 255, size=(3, 2), dtype=np.uint8)
xarray_data = xr.DataArray(data_array, dims=('dim1', 'dim2'))
xarray_data.plot.imshow(size=5, aspect="equal")
plt.show()

I get the following error:
...
  File "...\lib\site-packages\xarray\plot\dataarray_plot.py", line 1598, in newplotfunc
    raise ValueError("plt.imshow's `aspect` kwarg is not available in xarray")
ValueError: plt.imshow's `aspect` kwarg is not available in xarray

Indeed in the code here there is:
        if "imshow" == plotfunc.__name__ and isinstance(aspect, str):
            # forbid usage of mpl strings
            raise ValueError("plt.imshow's `aspect` kwarg is not available in xarray")

which seems quite clear.
So is there something I'm doing wrong or is it an issue between doc and code ? Thanks !

@aspyk Thanks for raising this. I've followed the code to the PR, where this was introduced: https://github.com/pydata/xarray/pull/1168. It looks like there's a reason to not have aspect forwarded to imshow, so I'm assuming that there is a slight inconsistency with the docstring.
You could still provide the aspect as scalar value (eg. 1.0). I've no detailed knowledge of xarray's plotting, so appreciate comments of others here.

Thanks for your quick answer. I just tried the aspect as scalar value but it doesn't seem to "lock" the aspect ratio, when I resize dynamically the window the aspect ratio follow the resizing and does not keep its initial value :/

@aspyk Let's wait for some more informed opinions here.
You might use plt.gca().axes.set_aspect('equal', 'box') before show to work around this (no resizing tested). See https://stackoverflow.com/questions/2934878/matplotlib-pyplot-preserve-aspect-ratio-of-the-plot

Thank, it works nice!
In my case I have several axis, so I'm ended with this:
ax = xarray_data.plot.imshow()
ax.axes.set_aspect("equal")
plt.show()

Indeed the trick was to apply set_aspect to ax.axes and not only ax...


binary streamed :in ?

ruby: 3.2.2
TTY::Command:  0.10.1
I am trying to stream a Down::ChunkedIO object from down to a TTY::Command.
Where the content could be arbitrary binary content.  But binary content streamed in: raises a Encoding::UndefinedConversionError
A simple reproduction:
require 'down'
require 'tty/command'

down_io = Down.open("https://upload.wikimedia.org/wikipedia/en/a/a9/Example.jpg")

runner = TTY::Command.new

runner.run("cat > out.jpg", in: down_io)

But this raises Encoding::UndefinedConversionError
/Users/jrochkind/.rubies/ruby-3.2.2/lib/ruby/3.2.0/delegate.rb:349:in `write': "\xFF" from ASCII-8BIT to UTF-8 (Encoding::UndefinedConversionError)
	from /Users/jrochkind/.rubies/ruby-3.2.2/lib/ruby/3.2.0/delegate.rb:349:in `block in delegating_block'
	from /Users/jrochkind/.gem/ruby/3.2.2/gems/tty-command-0.10.1/lib/tty/command/child_process.rb:200:in `convert_to_fd'
	from /Users/jrochkind/.gem/ruby/3.2.2/gems/tty-command-0.10.1/lib/tty/command/child_process.rb:136:in `convert'
	from /Users/jrochkind/.gem/ruby/3.2.2/gems/tty-command-0.10.1/lib/tty/command/child_process.rb:115:in `block in normalize_redirect_options'
	from /Users/jrochkind/.gem/ruby/3.2.2/gems/tty-command-0.10.1/lib/tty/command/child_process.rb:113:in `each'
	from /Users/jrochkind/.gem/ruby/3.2.2/gems/tty-command-0.10.1/lib/tty/command/child_process.rb:113:in `reduce'
	from /Users/jrochkind/.gem/ruby/3.2.2/gems/tty-command-0.10.1/lib/tty/command/child_process.rb:113:in `normalize_redirect_options'
	from /Users/jrochkind/.gem/ruby/3.2.2/gems/tty-command-0.10.1/lib/tty/command/child_process.rb:24:in `spawn'
	from /Users/jrochkind/.gem/ruby/3.2.2/gems/tty-command-0.10.1/lib/tty/command/process_runner.rb:44:in `run!'
	from /Users/jrochkind/.gem/ruby/3.2.2/gems/tty-command-0.10.1/lib/tty/command.rb:185:in `execute_command'
	from /Users/jrochkind/.gem/ruby/3.2.2/gems/tty-command-0.10.1/lib/tty/command.rb:104:in `run'

I expect this to instead properly stream to process, in this case (for reproduction purposes only) resulting in writing output to out.jpg.
I think I can fix the problem by changing this line:
https://github.com/piotrmurach/tty-command/blob/6aeb499dc323aebca7450f95f3fc8360a0d1ee83/lib/tty/command/child_process.rb#L198
To:
tmp = ::Tempfile.new(::SecureRandom.uuid.split("-")[0], :encoding => 'ascii-8bit')

If I make that change, the reproduction script no longer raises, and has the outcome I expect -- writing the bytes to local out.jpg.
I'm not sure if that change might break anything else, or if this is simply a bug that can be fixed?

However, looking at that code and seeing it's writing the stream to a tempfile on disk.... may defeat the purpose of what I'm trying to do anyway.  I was trying to improve performance by avoiding the write to disk, and streaming the bytes from network directly to the process. (Which is not cat in my real use case of course, that was just a simple reproduction).
But if TTY::Command is going to write whatever in: stream I give it to disk in a temporary file anyway, I'm not going to get the performance increase I was hoping for. So this may still be a bug that should be fixed, but maybe won't actually help me out.
Is is not feasible to stream the bytes directly to the process without creating the intermediate temp file? In my real use case, these are very large files from the network, and I was hoping to stream them directly to a spawned process stdin without first buffering them all on disk and taking the performance hit of the write-to-disk then read-from-disk.

Hi Jonathan,
Thanks for submitting this issue.

However, looking at that code and seeing it's writing the stream to a tempfile on disk.... may defeat the purpose of what I'm trying to do anyway. I was trying to improve performance by avoiding the write to disk, and streaming the bytes from network directly to the process. (Which is not cat in my real use case of course, that was just a simple reproduction).

But if TTY::Command is going to write whatever in: stream I give it to disk in a temporary file anyway, I'm not going to get the performance increase I was hoping for. So this may still be a bug that should be fixed, but maybe won't actually help me out.

That's not how tty-command works. I believe you have jumped to the wrong conclusion based on spurious understanding.
The tty-command is a wrapper around Process.spawn. It doesn't aim to reinvent the wheel and instead piggybacks on the spawn method and its options. This is key. The spawn method provides the following redirection options and allowed values:
redirection:
    key:
      FD              : single file descriptor in child process
      [FD, FD, ...]   : multiple file descriptor in child process
    value:
      FD                        : redirect to the file descriptor in parent process
      string                    : redirect to file with open(string, "r" or "w")
      [string]                  : redirect to file with open(string, File::RDONLY)
      [string, open_mode]       : redirect to file with open(string, open_mode, 0644)
      [string, open_mode, perm] : redirect to file with open(string, open_mode, perm)
      [:child, FD]              : redirect to the redirected file descriptor
      :close                    : close the file descriptor in child process

Further, the file descriptor can be given as:
      :in     : the file descriptor 0 which is the standard input
      :out    : the file descriptor 1 which is the standard output
      :err    : the file descriptor 2 which is the standard error
      integer : the file descriptor of specified the integer
      io      : the file descriptor specified as io.fileno

The tty-command examines these redirect options. In almost all cases, the TTY::Command passes these through to spawn unchanged which is the first line in the convert_to_fd method:
return object if fd?(object)

However, when the object provided is a string it intercepts it and first checks if it is a file, and if so lets it through:
  if object.is_a?(::String) && ::File.exist?(object)
    return object
  end

Finally, in an exceptional circumstance when the redirect is a string that doesn't reference a file, it converts it to a Tempfile so that it can conform to the spawn interface. It then can be passed to spawn, for example, as a value for :in option. Why have I made this exception? I wanted to be able to pass a keyboard input as a string like "input\ninput\ninput\n" for the benefits of tools like tty-prompt.
Now back to your original issue of providing Down::ChunkedIO object as a value for :in option. As shown above, the spawn method can accept FD(:in, :out, :err, integer, IO),string and :close as values for :in option.  However, your expectation is for :in to accept what is essentially a random object called IO but not an IO for all intents and purposes and stream the content down to process. Trying this out with spawn:
down_io = Down.open("https://upload.wikimedia.org/wikipedia/en/a/a9/Example.jpg")
Process.spawn("cat > out.jpg", in: down_io)

You get an error:
 `spawn': wrong exec redirect action (ArgumentError)

Therefore, I don't believe this to be a bug. If anything, the TTY::Command should raise an error for any value that doesn't conform to the spawn interface. The Down::ChunkedIO object certainly doesn't conform to any of the expected values.
As for the encoding change in the Tempfile, this will be useful in cases when the input string contains ASCII 8-bit characters. However, the file should probably be written as binary to avoid any encoding issues.
Not sure what the best solution for your case is. Ideally, TTY::Command instance would expose the child process streams and make them available to down_io to write in chunks. However, this is not a feature that this gem offers yet.

Thank you that was very helpful!

However, your expectation is for :in to accept what is essentially a random object called IO but not an IO for all intents and purposes and stream the content down to process

The basic problem is that ruby provides no actual specification of what an "IO" is!  Down::ChunkedIO is trying it's best to provide something that is an IO for all intents and purposes -- and it does succesfully serve as an IO in many contexts -- but ruby just doesn't make it easy (or possibly even feasible at all) for anything other than the stdlib objects to be IO "for all intents and purposes".  :(


Missing erlang native interface

Describe the bug
All erlang packages (except erlangR22 and erlangR21) are missing erl_interface.h which is crucial for building native dependencies for erlang
Expected behavior
erlang, erlangR23, erlangR24 should have erl_interface.h
Notify maintainers
@ankhers @Br1ght0ne @DianaOlympos @gleber @happysalada @yurrriq

the arch package doesn't contain it and neither does our erlang.src
https://archlinux.org/packages/community/x86_64/erlang/files/

I am not an erlang expert by any stretch.
Looking at this hacker news thread it says that erl_interface was deprecated with otp 23
https://news.ycombinator.com/item?id=23166554
it says that things have moved to a newer ei_ interface.
On the nixpkgs side of things, we are not doing anything different for compilation of 21 to 24. So if it is missing it is probably a deprecation upstream.
@dlesl sorry to bother you with this, but you might know more about this issue.

Oh goddess not erl_interface. I can have a look later too, it is a bit complex because it is a header that we need to provide for the dependencies to build. So may need to think a bit on how we could do it.

I found this:
http://erlang.org/doc/apps/erl_interface/notes.html#erl_interface-<IP_ADDRESS>

The old legacy erl_interface library (functions with prefix erl_) is deprecated as of OTP 22, and will be removed in OTP 23. This does not apply to the ei library. Reasonably new gcc compilers will issue deprecation warnings. In order to disable these warnings, define the macro EI_NO_DEPR_WARN.

As @happysalada mentioned it has been removed so I think the only solution is to update these dependencies. I'll close this since it doesn't seem to be a nixpkgs issue.

@dlesl , oh, I see
Thanks!


Spark 3.3 support

We would like to use RedShift connector with Spark 3.3 and Scala 2.13.
Could you share a road map to understand your plans for such support?
Thanks!

This project is basically inactive per the note
To ensure the best experience for our customers, we have decided to inline this connector directly in Databricks Runtime. The latest version of Databricks Runtime (3.0+) includes an advanced version of the RedShift connector for Spark that features both performance improvements (full query pushdown) as well as security improvements (automatic encryption). For more information, refer to the Databricks documentation. As a result, we will no longer be making releases separately from Databricks Runtime.
You may want to check out a community support version like https://github.com/spark-redshift-community/spark-redshift


kpt live commands should provide output in json/yaml format

When using kpt live as part of a CI/CD pipeline, it is useful to have an output format that can be easily parsed.

This would be very interesting to us. We're using the output as part of CI/CD pipelines, and while --output=table gives a nice summary of the state after a kpt live apply, it assumes the output is a terminal.

@fsommar My first thought here is that printing in json format will be similar to the default event format of kpt live, but with each line of the output as a json object. So something like:
{"namespace": "default", "name": "foo", "apiVersion": "apps/v1", "kind": "Deployment", "action": "created"}
{"namespace": "default", "name": "foo", "apiVersion": "apps/v1", "kind": "Deployment", "status": "InProgress", "message": ".."}

The output will still be streaming from kpt as it happens. I still need to spend some time deciding on the exact fields we should use, but does the direction match what you are looking for?

@fsommar I have a WIP on this at: https://github.com/kubernetes-sigs/cli-utils/pull/231
I have added a description of what the output would look like as godoc at https://github.com/kubernetes-sigs/cli-utils/pull/231/files#diff-f0e3e33ec6b4df91f7a7e1b0b65e2675R4. Take a look and let me know if there is anything you need that are missing or if something doesn't look right.

@mortent Thank you, LGTM!


Update Dataflow fnapi_container_version

Updates the Dataflow fnapi_container_version for the dataflow runner to a more recent build.

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Choose reviewer(s) and mention them in a comment (R: @username).
[ ] Mention the appropriate issue in your description (for example: addresses #123), if applicable. This will automatically add a link to the pull request in the issue. If you would like the issue to automatically close on merging the pull request, comment fixes #<ISSUE NUMBER> instead.
[ ] Update CHANGES.md with noteworthy changes.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.
To check the build health, please visit https://github.com/apache/beam/blob/master/.test-infra/BUILD_STATUS.md
GitHub Actions Tests Status (on master branch)

See CI.md for more information about GitHub Actions CI.

R: @kennknowles @johnjcasey

LGTM

The MacOS unit test run seems to be tied to not being able to find a gradle plugin?

Run Java PreCommit


user login

We should consider supporting google, facebook, twitter, weibo accounts authorization.

Actually, it is important that this site not be linked to any external sites or social media because of COPPA and also the privacy rules that will be in place.  Users will not be able to share personal information.

Do you mean a user should not be allowed to login with their google/facebook account and has to create an account at athanasea?

Yes.  The user must have an independent account just like on Chicken Smoothie or Eldemore.

That's why the phpBB forum framework is commonly used for these sites, because it already has that type of system built in.

I see. How is the current login we have on http://athanasea.meteor.com ?

I think that's fine, but I would still prefer to have the site be phpBB-based, since that works so well for all of the other adoptable games (and other virtual pet sites) that I've seen.

Also, any login will have to be COPPA compliant, so we will need to verify the user's age (as best as we can) and have a way for them to submit parental approval if they are under 13 years of age.  In case you're not familiar with COPPA: http://www.coppa.org


add init_options for domain_id , the code can't reconnect again !

Issue template

Hardware description: stm32f407  board
RTOS:  freertos
Installation type:   micro_ros_setup docker
Version or commit hash: galatic

Steps to reproduce the issue
this is good code , not init_option
// create init_options
RCCHECK(rclc_support_init(&support, 0, NULL, &allocator));

// create node
const char * node_name = "ailibot2";
RCCHECK(rclc_node_init_default(&node, node_name, "", &support));

this is bad code  with init_options .  it will cause can't reconnect again .
init_options = rcl_get_zero_initialized_init_options();

RCCHECK(rcl_init_options_init(&init_options, allocator));

size_t domain_id = 1;
RCCHECK(rcl_init_options_set_domain_id(&init_options, domain_id));

rmw_init_options_t* rmw_options = rcl_init_options_get_rmw_init_options(&init_options);

// create init_options
RCCHECK(rclc_support_init_with_options(&support, 0, NULL, &init_options, &allocator));

// create init_options
// RCCHECK(rclc_support_init(&support, 0, NULL, &allocator));

// create node
const char * node_name = "ailibot2";
RCCHECK(rclc_node_init_default(&node, node_name, "", &support));

Expected behavior
When I disconnect the micro-ros-agent, it can automatically connect when I use the micro-ros-agent again.
Actual behavior
Good code can achieve reconnection, but bad code cannot reconnect. However, for the actual data output by dubug, the development board is connected to the agent, but cannot output data.

Hello, Galactic is not a supported version of micro-ROS, could you confirm that this is replicable in humble or iron?

Currently we do not have a humble environment for testing.  Maybe we will also build a humble environment later.

Could you share the micro-ROS Agent log with the flag -v6?

docker run -it --net=host -v /dev:/dev --privileged microros/micro-ros-agent:galactic serial --dev /dev/ailibot -v6

[1695030014.669471] info     | TermiosAgentLinux.cpp | init                     | running...             | fd: 3
[1695030014.669762] info     | Root.cpp           | set_verbose_level        | logger setup           | verbose_level: 6

Only these contents, when I disconnect and reconnect

My debug infomation show like ：
[17:44:04:766] APP  State is AGENT_CONNECTED Continue!␍␊
[17:44:04:780] APP  State is AGENT_CONNECTED!␍␊
[17:44:04:782] APP  State is AGENT_CONNECTED Continue!␍␊
[17:44:04:795] APP  State is AGENT_CONNECTED!␍␊
[17:44:04:798] APP  State is AGENT_CONNECTED Continue!␍␊
[17:44:04:811] APP  State is AGENT_CONNECTED!␍␊
[17:44:04:815] APP  State is AGENT_CONNECTED Continue!␍␊
[17:44:04:827] APP  State is AGENT_CONNECTED!␍␊
[17:44:04:830] APP  State is AGENT_CONNECTED Continue!␍␊
[17:44:04:843] APP  State is AGENT_CONNECTED!␍␊

this is a normal information ， if i disconnected ， it will be ：
[17:45:42:614] APP  State is WAITING_AGENT!␍␊
[17:45:42:882] APP  State is WAITING_AGENT!␍␊
[17:45:42:885] APP  State is WAITING_AGENT!␍␊
[17:45:42:893] APP  State is WAITING_AGENT!␍␊
[17:45:42:893] APP  State is WAITING_AGENT!␍␊
[17:45:42:901] APP  State is WAITING_AGENT!␍␊
[17:45:42:901] APP  State is WAITING_AGENT!␍␊
[17:45:42:901] APP  State is WAITING_AGENT!␍␊
[17:45:42:914] APP  State is WAITING_AGENT!␍␊
[17:45:42:914] APP  State is WAITING_AGENT!␍␊
[17:45:42:914] APP  State is WAITING_AGENT!␍␊
[17:45:42:914] APP  State is WAITING_AGENT!␍␊

Does it work if you use rclc_support_init instead of rclc_support_init_with_options ?

Yes, reconnect is correct if I use rclc_support_init

I would recommend using a newer version of micro-ROS in order to ensure that this is not a old resolved issue

Okay, I will set up a humble environment to test it.

@pablogs9  I tested the code on humble today and found that this problem still exists, but this one can reconnect one more time than the galactic version. I replugged the USB, then the micro-ros-agent connected, disconnected, reconnected, disconnected again, and then couldn't connect again. The feedback is the same as galactic's problem.

@pablogs9  On Galactic, there is no limit on reconnection. It is normal for me to disconnect and reconnect more than 5 or 6 times. Judging from the content printed by debug on the code, the code on the MCU is running normally, but the agent cannot obtain it normally. Unable to reconnect, all that appear are stuck in the connected state:
docker run -it --net=host -v /dev:/dev --privileged microros/micro-ros-agent:humble serial --dev /dev/ailibot -v6

[1695030014.669471] info | TermiosAgentLinux.cpp | init | running... | fd: 3
[1695030014.669762] info | Root.cpp | set_verbose_level | logger setup | verbose_level: 6

@pablogs9  I may have found the answer to the problem. Without the rcl_init_options_fini(&init_options); line of code, after adding this, the current behavior on humble is normal. Can successfully reconnect multiple times in a row

Are you taking into account to set RMW_UXRCE_ENTITY_CREATION_DESTROY_TIMEOUT to 0 and UCLIENT_MAX_SESSION_CONNECTION_ATTEMPTS to a low value as stated here:
https://github.com/micro-ROS/micro_ros_arduino/blob/6f004dc1c88b3a0cdfa86b60b52bf0c335b69dc0/examples/micro-ros_reconnection_example/micro-ros_reconnection_example.ino#L44-L48

I didn't set these two values. I don't know where I can set them :( After I added rcl_init_options_fini, it became normal. The galactic and humble codes are all normal.

So can we close as solved?


Inventory status field should be passed through validation for boolean in its backend controller.

https://github.com/bagisto/bagisto/blob/cce548f2cd674db7f4973e7738a48bd5667b6e92/packages/Webkul/Admin/src/Resources/views/settings/inventory_sources/create.blade.php#L72
https://github.com/bagisto/bagisto/blob/cce548f2cd674db7f4973e7738a48bd5667b6e92/packages/Webkul/Inventory/src/Http/Controllers/InventorySourceController.php#L79
No validation in controller done for status its validation should be passed as boolean.

Hi @dejavuejs
We don't need validation for this one, simply, if we get this field from view at controller then it is active otherwise not.


Make RetainedHandlingPolicy enum public

Motivation:
Impossible to specify retained messages handling policy because the corresponding enum
isn't public (https://github.com/netty/netty/issues/10562)
Modification:
Made RetainedHandlingPolicy public
Result:
Fixes #10562.

@netty-bot test this please

@paul-lysak thanks a lot


support custom user data on nodes

This makes it easier to know which items were matched, e.g. tree.add(descriptor, 'abc'); assert tree.search(descriptor, 1)[0].user_data == 'abc'

What's the use case here?  Isn't the value of the node sufficient to determine what value you matched?

Maybe you're thinking about a situation where the identifier is the descriptor, but a) that's not guaranteed to be unique so it's common to use a different identifier, b) it's a bad index as it's ~pseudorandom bitstring which results in not being a good field to be indexed. After a tree.search the only way to find the information about the nodes that matched would be to iterate over all the dataset and find the ones with the descriptors returned, it's very inefficient.

With respect to a), my thinking was that nodes with the same value are indistinguishable.  Sure, they're not unique, but why would you want them to be?  A 5 is a 5, in what scenario does it matter which 5 you got back?
I don't quite follow you on b) either - what are you indexing?  You have to look at the results at least once, so I'm not sure what improvement that would buy you.

When you run tree.search(something, threshold) you're not returning only nodes with the same value, otherwise there would be no point in using this data structure. You're returning information about nodes that are within the threshold, they are not necessarily exact duplicates.
Maybe you could tell me how you're using this package, I'm not seeing an useful way to use it without having at least some indicator that is able to relate the descriptor (a bit string) to an identifier. If you think this is not a good idea for your package, by all means don't do it and close this issue.
Let's say you have one million items, item 1, item 2, item 3, .... Each of these have an associated bit string, bitstring 1, bitstring 2, bitstring 3, .... Zero or more of these bitstrings are within a distance of 2 of another 10 bitstrings.  How do you find out which items are related to those bitstrings? Currently, you have to iterate over your 1 million items to find it out. The proposal is that tree.search would return a node which contains some information to indicate that you got back items 99999, 812381, ....

How do you find out which items are related to those bitstrings? Currently, you have to iterate over your 1 million items to find it out

A dict seems like a pretty good built-in way to do this.  Like this:
>>> hashed_entries = {bitstring 1: [item 1, item 4, item 24601, ...],
                      bitstring 2: [item 99999, item 812381, ...],
                      etc, etc
                     }

>>> tree.search(somebitstring, 2)
[bitstring 2, bitstring 406, bitstring 10000, ...]

>>> hashes[bitstring 2]
[item 99999, item 812381, ...]

You had to iterate over your million items to get the bitstrings in the first place, so I think precomputing a dict of them is not likely a major performance hit.

That's fine if you want keep it this way. But do you think it's better, or even a good idea, to use bitstring as keys (which are pseudorandom) instead of simple integers? At least in my case, I have initial data sitting in a typical database which gets updated while the bktree is live. Items have a very simple and efficient index, an integer. The bitstrings are not used as an index because it's slower to index and search through pseudorandom indexes. I also don't want to keep a bitstring index outside of the bktree (in addition to the data already sitting in the database), as that increases the memory usage. But that's just me, I guess I'll close this, thanks for your time.

I got it now.  This is what I meant when I initially asked what your use case is.

I have initial data sitting in a typical database which gets updated while the bktree is live. Items have a very simple and efficient index, an integer. The bitstrings are not used as an index because it's slower to index and search through pseudorandom indexes. I also don't want to keep a bitstring index outside of the bktree (in addition to the data already sitting in the database), as that increases the memory usage

I think we're using different terminology - a bitstring (as I've been using the term) is an integer.  They're different representations of the same value.  For example, 0xe == 0b1110 == 14.  Does that not satisfy your requirements?

Sorry, yes it can be represented as an integer. It just happens that '0000000001000000000000000010000000000000000000000000000000000000' and '0000000000000000000000000010000000000000000000000000000000000000', which differ by 1 bit and can be represented as<PHONE_NUMBER>8435456 and<PHONE_NUMBER>72 is a poorer way to index the data related to it (e.g. 1 and 2). This library seems to consider the descriptors in a vacuum, while in practice I can't see it being used as something that can absolutely only store the descriptors themselves and not an indicator of what those descriptors refer to (which you have to build yourself externally, and duplicate/triplicate memory usage).

I compared the two versions of tagging a node and measured the memory used and time to build the data structures in question (windows 10, python 3.4):
# Node class as currently in master
from collections import defaultdict
import datetime

import bktree

start = datetime.datetime.now()
tree = bktree.Tree()
cache = defaultdict(list)

for i in range(1000000):
	tree.add(i)
	cache[i].append(str(i))

stop = datetime.datetime.now()
input('finished in {} ms.  Hit enter to proceed'.format((start - stop).microseconds / 1000))

# 699.0MB, 50ms

# Node class as in the PR
from collections import defaultdict
import datetime

import bktree

start = datetime.datetime.now()
tree = bktree.Tree()
cache = defaultdict(list)

for i in range(1000000):
	tree.add(i, str(i))

stop = datetime.datetime.now()
input('finished in {} ms.  Hit enter to proceed'.format((start - stop).microseconds / 1000))

# 726.3MB, 500ms

It appears using the Python builtins is an order of magnitude faster to build, and actually uses less memory.  Thanks for the feedback, but I'm going to keep Node as-is for now.

Uh.. that's a poor way to compare those for a few different reasons, but are you sure (start - stop).microseconds is not completely incorrect to measure the time taken?
>>> import time
>>> import datetime
>>>
>>> for i in range(10):
...     a = datetime.datetime.now()
...     time.sleep(0.003)
...     b = datetime.datetime.now()
...     print((a - b).microseconds / 1000)
...
988.991
989.617
988.307
987.697
988.017
989.91
987.83
989.248
989.448
987.467

I think you meant just (b - a):
>>> import time
>>> import datetime
>>>
>>> for i in range(10):
...     a = datetime.datetime.now()
...     time.sleep(0.003)
...     b = datetime.datetime.now()
...     print(b - a)
...
0:00:00.003842
0:00:00.003663
0:00:00.003396
0:00:00.003122
0:00:00.003809
0:00:00.003086
0:00:00.003850
0:00:00.003049
0:00:00.003858
0:00:00.003790

Then on my machine both take around 13 seconds to insert those 1e6 entries between 0 and 999,999. This comparison doesn't take into account that an insertion happens only once for a given entry, and then many searches (followed by many lookups in your code) occurs.

You're right about the time difference.  I was thinking total microseconds, it's just the fraction apparently.  Time between the two looks like a wash, 9.8-9.9 vs 9.9-10.0 seconds on my machine.
Lookups, though - I didn't time it, but Python set lookups are O(1).  It also appears to use less memory.  I'm hesitant to add something when the standard library performs at least as well on both time and space.

That's fine, no worries. btw, if you want to reduce the memory usage you could use slots for the nodes you have now.


OmniSharp - "latest" is being downloaded on every restart

The install test path ends with mono.linux-x86 which is not present in the latest OmniSharp versions, hence the package is being downloaded on every restart of the server when the omnisharp path is set to "latest".
@TheRealPiotrP @DustinCampbell @rchande @colombod

We determined in email that this is likely due a change in the OmniSharp packaging for OSX, Linux-x86 and Linux-x64 where the Mono runtime has moved to a "bin" folder. I suspect that an appropriate fix would be to just test the presence of the "run" script, since that's the thing that should be launched.

This will be fixed once the release (specifically this commit - https://github.com/OmniSharp/omnisharp-vscode/commit/81df57cff148edcf4f53819ee19ceec4cbdd5966) will be merged into master

@akshita31: I built a VSIX from the release branch and it still tries to download the latest every restart.


Add Jakarta Mail

This may be best handled by forking the source and changing the com.sun.* classes to a different package, as the Jakarta implementations share the same names as the old ones, which is trouble on Domino.

This may ALSO require forking the API as well: the next problem is jakarta.mail.Session's use of ServiceLoader.load(StreamProvider.class), which will look for services using the thread-context classloader. A fork could change that to use Session.class's ClassLoader instead.


Support for 3rd party diffs in insta review?

git can be configured to use different tools for generating code diffs. One of such tools is delta.
Is it possible to plug in some other engine into CLI's insta review?

Would be happy to accept changes here. This again is another issue that #282 would be good to have, but for now it could be configured by an envvar.


Add unpause buckets when unhealthy backends become online

Description of your changes
We introduced Auto pause function. Currently paused buckets are not monitored.
However, Provider should detect backend status changes (unhealthy -> healthy) and reconcile buckets again even if buckets are paused.
This PR introduces these steps:

Once a backend comes online again, the provider detects it (healthcheck_controller.Reconcile) and Unpause buckets which use the backend as their backend store.
bucket.Observe function detects that paused bucket are unpaused
bucket.Update function updates these buckets (catchup current status of the backend store, and be paused again)

In addition, this PR also introduces tests:

Whole unit test for bucket.Update
New test case for bucket.Observe

I have:

[x] Read and followed Crossplane's [contribution process].
[x] Run make reviewable to ensure this PR is ready for review.
[x] Added backport release-x.y labels to auto-backport this PR if necessary.

How has this code been tested
Unit test
[contribution process]: https://git.io/fj2m9

Thanks!


Avoid cache miss and dependency stall when have virtual small objects…

… for checksum aggregation.
Instead compute checksum inline with a simple switch.
@toregge and @vekterli PR

Yes, we can switch to XXH3 without any implications. I will do that in a separate PR


False positive for ComposeContentEmitterReturningValues?

The following code triggers a false positive warning for ComposeContentEmitterReturningValues.
The code doesn't emit any content into the composition. It just returns a value.
@Composable
fun rememberInsetsController(): WindowInsetsControllerCompat? {
    val view = LocalView.current
    val window = remember { view.context.findActivity()?.window } ?: return null
    return remember { WindowCompat.getInsetsController(window, view) }
}

Also I think the XML configuration of the related documentation has a typo. Shouldn't it be content-emitters instead of allowed-composition-locals?
Version: 1.4.0

This also happens with Circuit Presenter<UiState> composable functions.

hm, does it go away if you don't use LocalView? I wonder if the composition local is what's triggering this

Found the issue


It appears twice pagination

When in javascript write load ($("#content").load("ok.php?Page=" + num);),
and click on pagination, it appears twice pagination, and should be only one.

You are loading same page recursively


Site: fix REPL by loading prop-types.

REPL was broken otherwise.

Coverage remained the same at 97.507% when pulling 4de21bb782e83f57b3d901e474d490f4bc73bea4 on site-repl-fix into 78f3e1a0616686a075f13f164e2f6f2018858ca4 on master.