Update cocoapods install instructions for M1 Macs

Description
cocoapods should be installed through homebrew with node and watchman.
What is the problem?
The existing workaround published on the website is unnecessarily convoluted and often fails.
How can we address it?
In the documentation, replace the following:
sudo arch -x86_64 gem install ffi
arch -x86_64 pod install

with
brew install node
brew install watchman
brew install cocoapods

Why is it important?
The additional dependence on arch -x86_64 adds unnecessary complexity to the environment.
Who needs this?

iOS Developers
Beginners

When should this happen (use version numbers if needed)?
When setting up a development environment for the first time.

Hi @wqueree i created a PR but it still open PR #3074


Show types first rather than last while using CTRL+SPACE

Feature Request
I am currently using Flutter & when I use some class like Text() then it should show its types first but right now it shows the types at last.
Right now it looks like this, this is at start
No Types at First

Types at Last

Whereas it should show it at first then it would be more helpful
PS - Idk if this is related to Flutter Extension
VS Code version: Code 1.30.1 (dea8705087adb1b5e5ae1d9123278e178656186a, 2018-12-18T18:05:00.654Z)
OS version: Darwin x64 18.2.0

System Info

Item
Value

CPUs
Intel(R) Core(TM) i5-6360U CPU @ 2.00GHz (4 x 2000)

GPU Status
2d_canvas: enabledchecker_imaging: disabled_offflash_3d: enabledflash_stage3d: enabledflash_stage3d_baseline: enabledgpu_compositing: enabledmultiple_raster_threads: enabled_onnative_gpu_memory_buffers: enabledrasterization: enabledvideo_decode: enabledvideo_encode: enabledwebgl: enabledwebgl2: enabled

Load (avg)
2, 2, 2

Memory (System)
8.00GB (0.07GB free)

Process Argv

Screen Reader
no

VM
0%

Extensions (44)

Extension
Author (truncated)
Version

html-css-class-completion
Zig
1.17.1

alignment
ann
0.3.0

code-gnu-global
aus
0.2.2

aws-amplify-vscode
aws
0.0.4

color-info
bie
0.5.0

npm-intellisense
chr
1.3.0

path-intellisense
chr
1.4.2

bracket-pair-colorizer
Coe
1.0.61

dart-code
Dar
2.21.1

flutter
Dar
2.21.1

vscode-eslint
dba
1.7.2

githistory
don
0.4.4

EditorConfig
Edi
0.12.5

tslint
eg2
1.0.42

vsc-material-theme
Equ
2.6.2

prettier-vscode
esb
1.7.3

auto-rename-tag
for
0.0.15

code-runner
for
0.9.5

latex-workshop
Jam
5.19.0

docthis
joe
0.7.1

vscode-styled-components
jpo
0.0.25

swift
Kas
0.0.3

graphql-for-vscode
kum
1.12.1

vscode-language-babel
mgm
0.0.21

dotenv
mik
1.0.1

cpptools
ms-
0.20.1

sublime-keybindings
ms-
4.0.0

wordcount
ms-
0.1.0

debugger-for-chrome
msj
4.11.1

awesome-flutter-snippets
Nas
1.0.5

tachyons
oct
0.3.0

vscode-jest
Ort
2.9.2

advanced-new-file
pat
1.2.0

vscode-versionlens
pfl
0.22.0

material-icon-theme
PKi
3.6.2

vscode-graphql
Pri
0.1.6

code-settings-sync
Sha
3.2.4

markdown-preview-enhanced
shd
0.3.11

velocity
sod
0.1.0

ayu
tea
0.17.0

highlight-matching-tag
vin
0.8.4

vscode-jss-snippets
vis
0.2.2

vscode-svg-previewer
vit
0.3.1

vscode-wakatime
Wak
1.2.5

(6 theme extensions excluded)

"editor.snippetSuggestions": "bottom",

Thanks @usernamehw
VSCode has so many features that many don't know where to find it 😂


Consider support for models with open generics in MVC views

See UserVoice suggestion here: https://aspnet.uservoice.com/forums/41201-asp-net-mvc/suggestions/2706166-support-for-generics-in-razor-view.

Closing because we are not planning to implement this.

Is it possible to open this topic again?

@mansoor-omrani of course. Do you have an interesting scenario to share on this?

I think so.
It might be slightly long to describe the scenario and write it codes.
Should I post the whole story and its code here?

@mansoor-omrani it might make more sense to post a new issue that covers the scenario you're after. We can then decide how it is best to implement it.

Btw, I know @javiercn was asking about something similar.

@Elion The topic is the same, but ok. I post the idea/feedback as a new issue as you say.
This way the excavating the previous idea out of the dusts might make it be implemented eventually. I believe it is a useful feature. Although implementing it is a little tricky, I think it is feasible.
@pranavkm I couldn't find @javiercn's post. Could you direct me to his post?

This way the excavating the previous idea out of the dusts might make it be implemented eventually. I believe it is a useful feature. Although implementing it is a little tricky, I think it is feasible.

What would you use this for and why is it hard using the existing feature set? Can you provide an example?

Where is this? I can't believe I haven't seen what I consider to be an overwhelming Use Case for this, albeit one at which I am fully aware of the countless eyes that will roll. Send in a generic model collection, reflect on its items' property names for column headers and then iterate through the list to display those items' values in rows. Reflection, slow, I get it. But how much dev time would be saved for simple key/value lookup lists, like Country? Let the eye rolling begin.

@kramffud You can do that without having an IEnumerable as a model. In fact our default templated html helpers already do this for you.


Source code for acquiring tokens via workload identity?

Can you please provide some example source code showing how an AKS client can acquire the token needed for by AAD as workload identity? (I assume I cannot use msal since it only knows about AAD, not generic MI/OIDC issuers).

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

ID: efde8151-ca72-0ce1-271a-57a14a8c7ccd
Version Independent ID: f37efaf0-6573-6813-a3e4-3065e44666e4
Content: Tutorial - Use a workload identity with an application on Azure Kubernetes Service (AKS) - Azure Kubernetes Service
Content Source: articles/aks/learn/tutorial-kubernetes-workload-identity.md
Service: container-service
GitHub Login: @MGoedtel
Microsoft Alias: magoedte

@mrochon
Thanks for the feedback! I have assigned the issue to content author to check and update the document as appropriate.

@MGoedtel
Can you please check and add your comments on this doc update request as applicable.

#reassign:schaffererin

As we have not heard back, we will now close this GitHub issue. Thank you again! #please-close


Adding Geometric Progression Generator

I would Like to add a GP generator that is geometric progression generator which will generate the series for the given input.
It will take input first three terms and the nth term
and print the entire series respectively.
for example
input
first three terms= 2,4,8
nth terms is 1024
output is=
2,4,8,16,32,64,128,256,512,1024

@LuckySingh9897 go for it.


Popup like door_entry but for other purposes

I'm looking to find if its possible to do something similar to the door_entry popup but just for standard things?
I want to have a single button that can be pushed, that will bring up an overlay of more tiles for things like lights in the room you pressed.  If nothing is pressed for lets say 5 seconds, then the overlay disappears back to the previous screen it was on.
I know I can do pages and then do a window.openPage to load a specific page, but I'd like to reduce the number of pages to basically the 1 page.
Is this possible?

If you know JS, you can create your own tile based on the door entry one, it already includes the logic which allows you to add tiles and the inactivity timeout.

Ok, I was just checking to see if I was missing something before I went digging through the code.  I also couldn't get the door_entry option to open, but I wasn't sure if its because I removed the camera section as I don't have a live feed I can pull up, but I wanted to see about using the screen to show open doors and the lock status.

I got it working... now I'm doing some changes I need and will hopefully get them submitted to you for other people, if you like them.


Errors when opening routing service sample

 Issue by yasassri
Thursday Oct 12, 2017 at 10:07 GMT
Originally opened as https://github.com/ballerina-lang/composer/issues/3581

Following error was observed.
Oct 12, 2017 3:34:45 PM org.ballerinalang.composer.service.workspace.rest.datamodel.BLangFileRestService generateJSON
SEVERE:  [json]
Oct 12, 2017 3:34:45 PM org.ballerinalang.composer.service.workspace.rest.datamodel.BLangFileRestService generateJSON
SEVERE:  [string, TypeCastError]
Oct 12, 2017 3:34:45 PM org.ballerinalang.composer.service.workspace.rest.datamodel.BLangFileRestService generateJSON
SEVERE:  [string, TypeCastError]
Oct 12, 2017 3:34:45 PM org.ballerinalang.composer.service.workspace.rest.datamodel.BLangFileRestService generateJSON
SEVERE:  [ballerina.net.http:Response]
Oct 12, 2017 3:34:45 PM org.ballerinalang.composer.service.workspace.rest.datamodel.BLangFileRestService generateJSON
SEVERE:  [ballerina.net.http:Response]

 Comment by yasassri
Thursday Oct 12, 2017 at 10:08 GMT

Seems most of the samples are broken.

 Comment by dilinisg
Thursday Oct 12, 2017 at 10:16 GMT

Same issue observed in windows

Fixed in 0.970 we replace the samples with BBE.


Port to a different hardware platform

Hey,
the raspi is a nice piece of hardware, but there are a few points which could be better.
The two main problems are the slow cpu and the size of the ram.
There are various other board with a faster cpu and more Ram. The Cubieboard 1 (released 2 years ago) comes with a 1Ghz CPU and 1GB RAM and a SATA port. Also it does have a nand storage for the OS.
Full specs: http://docs.cubieboard.org/
This board is at the same price level as the pi and brings more power.
I think the software can benefit from this.(directly attached sata drive as storage for the audio files, maybe some speed improvements for the UI)
Are there any plans to bring the software up and running on a different hardware system?
Kai

No reply so closing. Once we get things packaged this will be supported.


Race condition between inference image and training

All things being equal, after a few clean runs of the excellent utility, it seems that there is a race condition. Between inference image build and training. As the first invocation of build inference image, fails always. Second invocation after completing the training of the model, it succeeds. Possible race issue, but don’t have proof right now. But still worth looking at.

what is the status of this?

Checking if its still there in the latest version.


no np.min() np.max() for empty array

Fix to run at KPNO.
the QA for amp was crashing. probably because we are running without a BLUE camera on the spectrograph we are testing now.

Seems to work fine. Merging to master.


Items table and modifiers

@Newobc @DanEvans485 I'd like both of you to look at this if you would be so kind :)
A copy of my DB is here (rename it to .sql, GitHub doesn't like .sql files)
opendm.txt

I don't feel the need for it. The modifiers only change character stats, and they are applied during computation of those stats.

@G-Bro If you wana have a look through the changes I've made to this PR I think I'm done.


Cody chat has no context information

When asking the chat about the code the responses are out of context.

This is the Cody commit:
459fd0cd8d5c90f450d4ea121255ea1bb6c5b44f

Since this commit the context read files are not inlcuced.

@mkondratek Some context here on how to troubleshoot the problem https://sourcegraph.slack.com/archives/C059N5FRYG3/p1702029835872099

(cc @abeatrix)

I limited the changes to this single file and change:
https://sourcegraph.com/github.com/sourcegraph/cody@18b56f527dfed147c39edf3e38c8230cd080323d/-/blob/lib/shared/src/chat/transcript/interaction.ts?L64

https://github.com/sourcegraph/cody/pull/2211

Is it worth opening another issue for this? I can't get Cody worked fine before the holidays December 15th, and for the past hour have been getting warnings about no Context messages.

Hello @adampatterson 👋
Thanks for sharing your experience with this issue. It makes me think that it's origin is somewhere deeper (probably LLM). I cannot remember for sure but I'd rather say that I have seen it even before Dec 15th. I tried to bisect the agents git history but I managed to get the same problem even months ago.
We are on it. Good point that the issue should not be closed yet. It was closed prematurely by one of the PRs that may help.

@mkondratek no problem!
I'm not sure if it's related but I noticed that the CPU usage goes way up when I open the side panel. No action needed ( for me ).  Since you mentioned the LLM it made me think that it was working at indexing the code base or something.
The Sourcegraph twitter account said that the desktop app is no longer supported. I know that it was using PostgreSQL.  If the app is no longer needed is the extension still using PostgreSQL?

@adampatterson, you are right about the history. The plugin (extension) does not use PostreSQL.

@adampatterson, we have not been seeing this issue anymore. I am closing it. 😌
We hope Cody helps you with your work 🚀  If you find something new or have some suggestions feel free to post a new issue 👋

Oh yes, the latest updates have made a huge difference!


[Impeller] Failure to render text glyph shadows.

Noticed this at wonderous near ToT.

Break on 'ImpellerValidationBreak' to inspect point of failure: Could not find glyph position in the atlas with scale:

When triaging issue https://github.com/flutter/flutter/issues/130613, the OP noticed the output log similar to the log above. I just leave my comment here if it's helpful for the investigation.

[VERBOSE-2:validation.cc(49)] Break on 'ImpellerValidationBreak' to inspect point of failure: Could not find glyph position in the atlas.

But it's only reproducible when using fast_cached_network_image package (see https://github.com/flutter/flutter/issues/130613#issuecomment-1644045875). It causes the widget to be invisible when scrolling custom 3D Cube PageView in the carousel view.
Checking flutter-wonderous-app, I also notice that log from the output console on iOS platform.
Verifying this on the master channel.

flutter doctor -v (master)
[!] Flutter (Channel master, 3.13.0-7.0.pre.57, on macOS 13.4.1 22F770820d darwin-x64, locale en-VN)
    • Flutter version 3.13.0-7.0.pre.57 on channel master at /Users/huynq/Documents/GitHub/flutter_master
    ! Warning: `flutter` on your path resolves to /Users/huynq/Documents/GitHub/flutter/bin/flutter, which is not inside your current Flutter SDK checkout at /Users/huynq/Documents/GitHub/flutter_master. Consider adding /Users/huynq/Documents/GitHub/flutter_master/bin to the front of your path.
    ! Warning: `dart` on your path resolves to /Users/huynq/Documents/GitHub/flutter/bin/dart, which is not inside your current Flutter SDK checkout at /Users/huynq/Documents/GitHub/flutter_master. Consider adding /Users/huynq/Documents/GitHub/flutter_master/bin to the front of your path.
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 83e5aca1c9 (88 minutes ago), 2023-07-20 21:26:17 -0400
    • Engine revision b5a6b1c9cb
    • Dart version 3.1.0 (build 3.1.0-332.0.dev)
    • DevTools version 2.25.0
    • If those were intentional, you can disregard the above warnings; however it is recommended to use "git" directly to perform update checks and upgrades.

[✓] Android toolchain - develop for Android devices (Android SDK version 32.0.0)
    • Android SDK at /Users/huynq/Library/Android/sdk
    • Platform android-33, build-tools 32.0.0
    • ANDROID_HOME = /Users/huynq/Library/Android/sdk
    • Java binary at: /Applications/Android Studio.app/Contents/jbr/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 17.0.6+0-17.0.6b802.4-9586694)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 14.3)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Build 14E222b
    • CocoaPods version 1.11.3

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 2022.2)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 17.0.6+0-17.0.6b802.4-9586694)

[✓] VS Code (version 1.80.1)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.68.0

[✓] Connected device (4 available)
    • RMX2001 (mobile) • EUYTFEUSQSRGDA6D                         • android-arm64  • Android 11 (API 30)
    • iPhone (mobile)  • d9a94afe2b649fef56ba0bfeb052f0f2a7dae95e • ios            • iOS 15.7.2 19H218
    • macOS (desktop)  • macos                                    • darwin-x64     • macOS 13.4.1 22F770820d darwin-x64
    • Chrome (web)     • chrome                                   • web-javascript • Google Chrome 114.0.5735.198

[✓] Network resources
    • All expected network resources are available.

! Doctor found issues in 1 category.

Hello @jonahwilliams maybe this is interesting to you
https://github.com/flutter/flutter/issues/130613#issuecomment-1644045875
@huycozy pointed me here and it looks this might be the same issue. We closed 130613 coz I thought I had no time to create a sample but then I made one.
As pointed out, fast_cached_network_image  also uses hive and dio internally, but we use those other plugins in our projects and have no issues with them.

@dnfield this is a regression from the glyph atlas changes. I'm not sure exactly why, but the compute scale for the text in the shadows is 1.0, which means its likely not computed the same as the traversal in entity pass.

Hello, just tested sample repo from 130613 after @bdero fix and that issue still persists.
https://github.com/flutter/flutter/issues/130613#issuecomment-1644045875
We will revert to 3.12.0 but are available to check things again at need.

Also noticed that after #43920 we no longer see the log: "[VERBOSE-2:validation.cc(49)] Break on 'ImpellerValidationBreak' to inspect point of failure: Could not find glyph position in the atlas."
We now see only the widgets getting unmounted.
I paste the sample link also here.
https://github.com/delfme/cube-sample
Can a plugin's bug force widgets to get unmounted after they have been rendered?

This might help narrow investigation, made time to test on more recent beta 3.13.0-0.2.pre (and 3.13.0-0.1.pre) and issue 130613 is not reproducible there.
@huycozy quick wrote this here but at this point I think the two issues might be unrelated, so please let me know if you want me to write only on
https://github.com/flutter/flutter/issues/130613

@delfme Although it looks like you were hit by the validation failure for some time, the current issue you're facing appears to be unique and not related to the validation failure. So keeping it to https://github.com/flutter/flutter/issues/130613 sounds like the right move. 👍


Static extension to protocol with PAT errors: same-type constraint is recursive

Description
With a protocol, one can write a static extension constrained to a particular Self type. SwiftUI makes extensive use of this feature:
protocol P {}

struct S: P {}

extension P where Self == S {
    static var s: Self { .init() }
}

func f(_ items: [any P]) {}

f([.s])

However, when the protocol has a primary associated type, and the constrained type is generic in that PAT, the compiler doesn't allow it:
protocol Q<A> {
    associatedtype A
}

struct T<A>: Q {}

extension Q where Self == T<A> {
    static var t: Self { .init() }
}
func g(_ items: [any Q<Int>]) {}

g([.t])

swiftc SameTypeRecursive.swift
SameTypeRecursive.swift:21:13: error: same-type constraint 'Self' == 'T<Self.A>' is recursive
extension Q where Self == T<A> {
            ^

Expected behavior
I don't understand why that's considered "recursive"; it seems to me like it should work...
Environment
swift-driver version: 1.75.2 Apple Swift version 5.8 (swiftlang-<IP_ADDRESS>.2 clang-14<IP_ADDRESS>.100)
Target: arm64-apple-macosx13.0
same behavior with Xcode 15b2:
swift-driver version: 1.82.2 Apple Swift version 5.9 (swiftlang-<IP_ADDRESS>.10 clang-15<IP_ADDRESS>)
Target: arm64-apple-macosx13.0

Actually, I do think I see why that's considered recursive.
Maybe this is a feature request for a way to introduce type parameters into extensions, like
forall<X> extension Q<X> where Self == T<X> {
    static var t: Self { .init() }
}

Shorter:
protocol P {
  associatedtype A
}

struct S<A>: P {}

extension P where Self == S<Self.A> {}

<X where Self == S<X> is still equivalent to <X where Self == S<X>, Self.A == X>, so indeed the constraint is not semantically recursive. The issue probably lies in some unwanted circularity during analysis.


Use JIRA account owners instead of usernames

@olaaun please review.

Build error

Yes, forgot the add the new class. The compiler error is completely bonkers, though!


File paths need better support on Unix

Because most project files assume that the directory path delimiter is a \, MSBuild contains a FileUtilities.FixFilePath method that is used by many tasks to ensure that paths are properly constructed when running on Unix systems.
However, some projects contain references to custom tasks that deal with file paths but do not have access to this method. (see, for example, the DownloadFile task in coreclr)
After some discussion in the coreclr chat room, it was proposed that this functionality might be best exposed as a Property Function.
Such a property function would most likely need to be a member of the MSBuild set of property functions, which are defined in IntrinsicFunctions. It would also need a name--FixFilePath might be acceptable, but I suspect that a more descriptive name would be desired.
I would be happy to submit a Pull Request if a member of the team signs off on this issue (and we agree on a name for the function)

MSBuild team triage: Sounds good. How about ToFilePath for the function name? David feel free to assign this to yourself.

I'd love to take it, but I don't have permission to assign issues in this project.


Remove automatic noise filtering

Its distorts the signal if its clean

Added filter_noise=False argument to the Sound.condition method


[stable/unifi] Add ingress for Unifi controller sevice

Signed-off-by: Stephen Liang<EMAIL_ADDRESS>
Is this a new chart

NOTE: We're experiencing a high volume of PRs to this repo and reviews will be delayed. Please host your own chart repository and submit your repository to the Helm Hub instead of this repo to make them discoverable to the community. Here is how to submit new chart repositories to the Helm Hub.

No.
What this PR does / why we need it:
Adds an ingress for the Unifi HTTP-only controller "/inform" path. Without this change, the standard controller would attempt to pass to "/inform" using TLS and since the inform path is HTTP only, will fail.
In addition, in the unified service mode specified in this helm chart, an external load balancer could be used to specify a port to the controller service, however without an external load balancer, an ingress to the controller would be needed.
Which issue this PR fixes
(optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged)

fixes #21887

Special notes for your reviewer:
@billimek @mcronce
Checklist
[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]

[x] DCO signed
[x] Chart Version bumped
[x] Variables are documented in the README.md
[x] Title of the PR starts with chart name (e.g. [stable/mychartname])

/assign @billimek

Thanks @stephenliang.  There was another merge of this chart, so can you please rebase with the master branch?  The Chart.yaml version will need to be bumped again too - I suggest using 0.10.0.

Sounds good @billimek I bumped it to 0.10.0 and rebased it.

/lgtm


[OpenAI] Async iterables to disposable and iterable readable streams

Packages impacted by this PR
@azure/core-sse, @azure/openai
Issues associated with this PR
Fixes https://github.com/Azure/azure-sdk-for-js/issues/27959
Describe the problem that is addressed by this PR
This PR updates the SSE operations to return a readable stream instead of an async iterable, which addresses the following two issues:

The issue above describes a scenario where exiting early from the loop leaves the socket not completely drained which in turn causes the application to hang until the socket timeout and closes. This PR returns streams instead which will be canceled once the loop exit early and that cancellation will prompt drainage of the socket. Moreover, the stream is disposable so the socket will be drained once the stream goes out of scope but requires declaration using await using
The output stream enables piping scenarios such as text-to-speech

What are the possible designs available to address the problem? If there are more than one possible design, why was the one in this PR chosen?
Alternatively, the linked issue could be addressed by adding the logic for draining the socket in the definition of the return method on the AsyncIterable interface.
Are there test cases added in this PR? (If not, why?)
Yes.
Provide a list of related PRs (if any)
N/A
Command used to generate this PR:**(Applicable only to SDK release request PRs)
Checklists

[x] Added impacted package name to the issue description
[ ] Does this PR needs any fixes in the SDK Generator?** (If so, create an Issue in the Autorest/typescript repository and link it here)
[x] Added a changelog (if necessary)

API change check
APIView has identified API level changes in this PR and created following API reviews.
@azure/openai


error with podman 1.9.0 and cgroup1

/kind bug
Description
podman 1.9.0 fails to run a rootless container with cgroup1, while 1.8.2 is able to run.
Steps to reproduce the issue:

Configure a fairly standard cgroup1 setup. Mount output: http://ix.io/2iuO
Invoke any run command, e.g. podman --log-level DEBUG run --rm -it docker://cameronnemo/voidlinux-interactive:latest ash

Describe the results you received:

Debug log with 1.9.0: http://ix.io/2iuM
Debug log with 1.8.2: http://ix.io/2iuN

Describe the results you expected:
A successful container run, like with 1.8.2.
Additional information you deem important (e.g. issue happens only occasionally):
Happens consistently.
Output of podman version:
1.9.0:
Version:            1.9.0
RemoteAPI Version:  1
Go Version:         go1.14.2
OS/Arch:            linux/amd64

1.8.2:
Version:            1.8.2
RemoteAPI Version:  1
Go Version:         go1.14
OS/Arch:            linux/amd64

Output of podman info --debug:
1.9.0:
debug:
  compiler: gc
  gitCommit: ""
  goVersion: go1.14.2
  podmanVersion: 1.9.0
host:
  arch: amd64
  buildahVersion: 1.14.8
  cgroupVersion: v1
  conmon:
    package: Unknown
    path: /usr/libexec/podman/conmon
    version: 'conmon version 2.0.15, commit: unknown'
  cpus: 4
  distribution:
    distribution: '"void"'
    version: unknown
  eventLogger: file
  hostname: ceci
  idMappings:
    gidmap:
    - container_id: 0
      host_id: 1000
      size: 1
    - container_id: 1
      host_id: 2000000
      size: 65536
    uidmap:
    - container_id: 0
      host_id: 1000
      size: 1
    - container_id: 1
      host_id: 2000000
      size: 65536
  kernel: 5.4.31_1
  memFree: 503386112
  memTotal:<PHONE_NUMBER>
  ociRuntime:
    name: runc
    package: Unknown
    path: /usr/bin/runc
    version: 'runc version spec: 1.0.1-dev'
  os: linux
  rootless: true
  slirp4netns:
    executable: /usr/bin/slirp4netns
    package: Unknown
    version: |-
      slirp4netns version 1.0.0
      commit: a3be729152a33e692cd28b52f664defbf2e7810a
      libslirp: 4.2.0
  swapFree:<PHONE_NUMBER>
  swapTotal:<PHONE_NUMBER>
  uptime: 176h 46m 36.14s (Approximately 7.33 days)
registries:
  search:
  - docker.io
store:
  configFile: /home/cameronnemo/.config/containers/storage.conf
  containerStore:
    number: 2
    paused: 0
    running: 0
    stopped: 2
  graphDriverName: overlay
  graphOptions:
    overlay.mount_program:
      Executable: /usr/bin/fuse-overlayfs
      Package: Unknown
      Version: |-
        fusermount3 version: 3.9.1
        fuse-overlayfs: version 0.7.8
        FUSE library version 3.9.1
        using FUSE kernel interface version 7.31
  graphRoot: /home/cameronnemo/.local/share/containers/storage
  graphStatus:
    Backing Filesystem: extfs
    Native Overlay Diff: "false"
    Supports d_type: "true"
    Using metacopy: "false"
  imageStore:
    number: 12
  runRoot: /run/user/1000
  volumePath: /home/cameronnemo/.local/share/containers/storage/volumes

1.8.2:
debug:
  compiler: gc
  git commit: ""
  go version: go1.14
  podman version: 1.8.2
host:
  BuildahVersion: 1.14.3
  CgroupVersion: v1
  Conmon:
    package: Unknown
    path: /usr/libexec/podman/conmon
    version: 'conmon version 2.0.15, commit: unknown'
  Distribution:
    distribution: '"void"'
    version: unknown
  IDMappings:
    gidmap:
    - container_id: 0
      host_id: 1000
      size: 1
    - container_id: 1
      host_id: 2000000
      size: 65536
    uidmap:
    - container_id: 0
      host_id: 1000
      size: 1
    - container_id: 1
      host_id: 2000000
      size: 65536
  MemFree: 496386048
  MemTotal:<PHONE_NUMBER>
  OCIRuntime:
    name: runc
    package: Unknown
    path: /usr/bin/runc
    version: 'runc version spec: 1.0.1-dev'
  SwapFree:<PHONE_NUMBER>
  SwapTotal:<PHONE_NUMBER>
  arch: amd64
  cpus: 4
  eventlogger: file
  hostname: ceci
  kernel: 5.4.31_1
  os: linux
  rootless: true
  slirp4netns:
    Executable: /usr/bin/slirp4netns
    Package: Unknown
    Version: |-
      slirp4netns version 1.0.0
      commit: a3be729152a33e692cd28b52f664defbf2e7810a
      libslirp: 4.2.0
  uptime: 176h 48m 16.25s (Approximately 7.33 days)
registries:
  search:
  - docker.io
store:
  ConfigFile: /home/cameronnemo/.config/containers/storage.conf
  ContainerStore:
    number: 2
  GraphDriverName: overlay
  GraphOptions:
    overlay.mount_program:
      Executable: /usr/bin/fuse-overlayfs
      Package: Unknown
      Version: |-
        fusermount3 version: 3.9.1
        fuse-overlayfs: version 0.7.8
        FUSE library version 3.9.1
        using FUSE kernel interface version 7.31
  GraphRoot: /home/cameronnemo/.local/share/containers/storage
  GraphStatus:
    Backing Filesystem: extfs
    Native Overlay Diff: "false"
    Supports d_type: "true"
    Using metacopy: "false"
  ImageStore:
    number: 12
  RunRoot: /run/user/1000
  VolumePath: /home/cameronnemo/.local/share/containers/storage/volumes

Package info (e.g. output of rpm -q podman or apt list podman):
1.9.0 (locally built and installed):
architecture: x86_64
filename-sha256: bc97aabc549fbc6451eb772dec196a1a0d5aa118a478a91e8e45eecf9d07942f
filename-size: 20MB
homepage: https://podman.io/
install-date: 2020-04-18 02:02 PDT
installed_size: 55MB
license: Apache-2.0
maintainer: Cameron Nemo<EMAIL_ADDRESS>metafile-sha256: 61a97cc0fe02eb503bd248b9bde34de6cf57602baea3ec3dc62e44fc18776397
pkgname: podman
pkgver: podman-1.9.0_1
repository: /home/cameronnemo/docs/src/vpkg/hostdir/binpkgs/podman-1.9.0
run_depends:
	runc>=0
	conmon>=0
	cni-plugins>=0
	slirp4netns>=0
	containers.image>=0
	glibc>=2.29_1
	libgpgme>=1.12.0_2
	libassuan>=2.0.1_1
	libgpg-error>=1.6_1
	libseccomp>=2.0.0_1
	device-mapper>=2.02.110_1
shlib-requires:
	libpthread.so.0
	libgpgme.so.11
	libassuan.so.0
	libgpg-error.so.0
	libseccomp.so.2
	librt.so.1
	libdevmapper.so.1.02
	libc.so.6
short_desc: Simple management tool for containers and images
state: installed

1.8.2 (built by repos:
architecture: x86_64
filename-sha256: afd84e7980ed2610e232f3d2f14e60aa210656e77b4e705c46f9d861cdbce762
filename-size: 20MB
homepage: https://podman.io/
install-date: 2020-04-18 02:05 PDT
installed_size: 54MB
license: Apache-2.0
maintainer: Cameron Nemo<EMAIL_ADDRESS>metafile-sha256: 3df90315902b0baac657941b27d7e76cfd493c9391c734fe10253eb3e2c207a8
pkgname: podman
pkgver: podman-1.8.2_2
repository: https://alpha.de.repo.voidlinux.org/current
run_depends:
	runc>=0
	conmon>=0
	cni-plugins>=0
	slirp4netns>=0
	containers.image>=0
	glibc>=2.29_1
	libgpgme>=1.12.0_2
	libassuan>=2.0.1_1
	libgpg-error>=1.6_1
	libseccomp>=2.0.0_1
	device-mapper>=2.02.110_1
shlib-requires:
	libpthread.so.0
	libgpgme.so.11
	libassuan.so.0
	libgpg-error.so.0
	libseccomp.so.2
	librt.so.1
	libdevmapper.so.1.02
	libc.so.6
short_desc: Simple management tool for containers and images
source-revisions: podman:34432dd49f
state: installed

Additional environment details (AWS, VirtualBox, physical, etc.):
Physical.

podman --log-level DEBUG run --rm -it docker://cameronnemo/voidlinux-interactive:latest ash
Works for me on cgroups V1
$ rpm -q podman
podman-1.9.0-1.fc32.x86_64
@giuseppe Ideas?

One difference may be the management method -- on Void we do not have systemd so it is using the cgroupsfs manager.

are you using exactly the same runc version for both?
Could you share the config.json file that is generated (you can get the path from the debug output: Created OCI spec for container $CTR_ID at $PATH)?

I believe I have the same issue on Gentoo without Systemd.
The following line in dmesg seems informative:
cgroup1: Unknown subsys name 'openrc'

With a hybrid cgroup setup (probably with legacy v1 as well) I have /sys/fs/cgroup/openrc, mounted as
openrc on /sys/fs/cgroup/openrc type cgroup (rw,nosuid,nodev,noexec,relatime,release_agent=/lib/rc/sh/cgroup-release-agent.sh,name=openrc)

We do not support hybrid cgroups in Podman - that's likely the issue there

We do not support hybrid cgroups in Podman

I am aware of that, but it works just fine with Podman 1.8.2. I believe it is detected as cgroup v1, and the cgroup v2 mount is ignored, right?
So, my guess is that a cgroup v1 setup (with openrc) would have the same issue. I did not test that, though.
I did test cgroup v2, but could not get Podman to run either (due to a different issue, probably #5903).

Same runc (same everything) for each version. I am not using the unified hierarchy.
1.8.2 config.json
1.9.0 config.json

Meanwhile this issue is still opened, how can we downgrade podman to 1.8.2 ?
Following the install instructions, the Kubic project seems only to provide the latest version 1.9.0.

This appears to be fixed with the 1.9.2 release.


[BEAM-9758] Use quotes in echo statements to prevent * expansion.

Also wanted to test if Jira->Github links are working again.

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).
[ ] Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.
[ ] 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.

Thanks! LGTM

@ibzib Doesn't the change in LoadTestBuilder affect what gets printed to the logs? I recently noticed that the job names weren't printed:
14:33:28 + echo '***  ***'
14:33:28 ***  ***

like here: https://builds.apache.org/job/beam_LoadTests_Java_ParDo_Dataflow_Batch/398/console

@ibzib Doesn't the change in LoadTestBuilder affect what gets printed to the logs? I recently noticed that the job names weren't printed:

Yeah, sorry about that. Fixed in #12021


Interface web

It could build on rails or other language a web interface to manage simplest Dokku.

Sorry, this is outside of the scope of dokku. If anything, we will build a daemon that users can build apis on top of, and then web interfaces for those APIs.
If you want to work on #1559 - which may lead to an official web project, though not in the core - that would be pretty pro :)

@josegonzalez  thankyou, There is a project for this?


Missing parameters for jspC - Caching, PoolingEnabled, GenStringAsCharArray and ClassDebugInfo

I need in my project access to four jspC parameters - Caching, PoolingEnabled, GenStringAsCharArray and ClassDebugInfo. Can you add access to the parameters in newer plugin version?

Can you add access to the above mentioned parameters in newer plugin version?. it would be very helpful. when can we expect new version?

@czerpak @vijayaraja would you be willing to open a pull request to add these attributes?

Hey there! :wave:
Thanks for opening an issue with jspc-maven-plugin. :+1: :bowing_man:
At the moment, the jspc maven plugin does not have an active maintainer to process your request. :no_entry:
While the Jasig jspc maven plugin is without an active maintainer, we recommend the Apache Sling jspc maven plugin and the Jetty jspc maven plugin as alternatives that are actively maintained. :white_check_mark:
If you are interested in becoming a project maintainer, there is a uPortal-dev list post where you can register your interest. :email:
Thanks again for contributing to the  jspc-maven-plugin! :sparkles:


Added documentation on calculating auto direction

Related to https://github.com/esm7/obsidian-rtl/pull/48#issuecomment-1399477009
@esm7 Let me know if some parts aren't clear or informing enough.
Also I suggest adding some screenshots in the readme if you think its a good idea to.

That's great, thanks!
And I totally agree with the need to add screenshots to the README, will probably do that soon.


Make public \yii\base\ArrayableTrait::resolveFields

It can be used for custom serializer or for my own toArrayRecursive(), since native toArray fails my needs.

Won't be implemented in 2.0.


7.3.0 instant launch crash React Native 0.74.5

Install rive-react-native 7.3.0
instant crash android on launch.

Hi @hamdij0maa can you share

the .riv file you're using
the code
the crash log

I see the same issue (crash on app start) but only on iOS in an expo project.
    "expo": "~51.0.31",
    "react-native": "0.74.5",
    "rive-react-native": "^7.3.0",

It crashes even if I remove all usages of rive-react-native in the code so I don't think it's related to a specific animation file or code.

Downgrading to 7.2.0 fixes the crash.
I tried the same version 7.3.0 of rive-react-native in a bare React Native project with the same react-native version (0.74.5) and it works well there.

Same issue as @mlazari

I guess my issue is the same as https://github.com/rive-app/rive-react-native/issues/261

I'm having the same issue here after upgrading to React Native 0.74.5. However, my Rive version is 6.2.3.
Crash Free users on the version with React Native 0.74.5 dropped to 64% (from 98%+).
I can see a SIGABRT crash on libc.so and the logs also show librive-android.so on the stack trace. We need this fixed ASAP. Could you please help us? Is there a Rive version that has been tested with React Native 0.74.5?

Hey all. 👋 I've just started working on updating the repo to support the latest couple of versions of RN. Step one is getting all of our packages upgraded to more recent versions while still using RN 0.72.x. This'll make it easier to do the next couple of upgrades. If anyone wants to give it a test on a 0.72.x project, that'd be super helpful: https://github.com/rive-app/rive-react-native/pull/267

@lancesnider @HayesGordon sorry in advance for pinging you, but do you have any visibility on when this is going to be fixed?
This issue has been opened for 3 months and makes Rive completely unusable.
It starts to get annoying as customers, as we paid to get some Rive assets that we can not use in our apps...
For tracking purpose, here are the other issues opened:
https://github.com/rive-app/rive-react-native/issues/268
https://github.com/rive-app/rive-react-native/issues/272

Hi @PierreCapo, does the latest version of Rive React Native not solve this for you?

@HayesGordon Still having the same issue with rive-react-native 8.1.0

Using s.dependency "RiveRuntime", "6.3.3" according to podspec
Related with this issue on rive-ios: https://github.com/rive-app/rive-ios/issues/345

also stuck on this issue. I have a test working with rive-react-native 8.1.0 and RN 0.76.1, but in the app with RN 0.74.5 I haven't gotten any version of rive-react-native to work. Also holding us up. Have seen some comments suggesting Firebase may be part of the problem and we are using Firebase in our project while the test project does not.

we are using Firebase in our project

we are also using https://github.com/invertase/react-native-firebase

Same, most likely an issue related with the static linking for frameworks enforced by React-Native Firebase

Any updates on that topic?
Issues still appears using version 8.1.0 released in November
Pb reproducible using React-Native 0.76 & Expo 52

cc @HayesGordon would you know if someone from Rive is aware and following the issue?
Thanks in advance 🙏

Still crashing on 0.76, no expo, also using firebase

8.2.0 also crashes, exactly the same. @HayesGordon
Thread 9 Crashed::  Dispatch queue: com.facebook.react.ShadowQueue
0   ???                           	          0x104100 ???
1   TaskHero.debug.dylib          	       0x112961134 -[RCTShadowView layoutWithMinimumSize:maximumSize:layoutDirection:layoutContext:] + 176 (RCTShadowView.m:268)
2   TaskHero.debug.dylib          	       0x1129515f4 -[RCTRootShadowView layoutWithAffectedShadowViews:] + 264 (RCTRootShadowView.m:35)
3   TaskHero.debug.dylib          	       0x112974b24 -[RCTUIManager uiBlockWithLayoutUpdateForRootView:] + 344 (RCTUIManager.m:549)
4   TaskHero.debug.dylib          	       0x11297a83c -[RCTUIManager _layoutAndMount] + 336 (RCTUIManager.m:1126)
5   TaskHero.debug.dylib          	       0x11297a6e0 -[RCTUIManager batchDidComplete] + 32 (RCTUIManager.m:1109)
6   TaskHero.debug.dylib          	       0x1128c4ac8 __32-[RCTCxxBridge batchDidComplete]_block_invoke + 56 (RCTCxxBridge.mm:1540)
7   libdispatch.dylib             	       0x1801774ec _dispatch_call_block_and_release + 24
8   libdispatch.dylib             	       0x180178de0 _dispatch_client_callout + 16
9   libdispatch.dylib             	       0x180180f60 _dispatch_lane_serial_drain + 956
10  libdispatch.dylib             	       0x180181a98 _dispatch_lane_invoke + 388
11  libdispatch.dylib             	       0x18018cf44 _dispatch_root_queue_drain_deferred_wlh + 276
12  libdispatch.dylib             	       0x18018c5a0 _dispatch_workloop_worker_thread + 440
13  libsystem_pthread.dylib       	       0x104487b74 _pthread_wqthread + 284
14  libsystem_pthread.dylib       	       0x104486934 start_wqthread + 8

Fixed in the last commit  e9fa1010a287cc87f4ffeb5a2a4166661f1fa5cb 🎉 Working on my side

Yep, this one should be working for all of you now with 8.3.0. Please let me know if you run into any issues with this. Sorry it took so long!

8.3.0 is working on my side too 🎉 Thank you for the fix!


Cannot setup BIG-IP HA Task Failed: Timed out waiting for onboarding task to finish after 1800 seconds

Environment

Declarative Onboarding Version: 1.18 (running on BIG-IQ 8.0)
BIG-IP Version: 14.1.4 (running on Velos Tenant)

Summary
@jimmccarron and I are using DO to onboard 2 BIG-IPs in HA but failing on getting the trust setup between the 2 devices. We verified the network connectivity between the self-ips and things are fine there. Wondering what is incorrect in the definition of the BIG-IP cluster in both DO declarations we are using.
We are able to add the 1s device <IP_ADDRESS> manually from the UI in the device trust of the 2nd device and complete HA config manually.
Steps To Reproduce
Steps to reproduce the behavior:

Submit the following declaration on device 1:

{
    "class": "DO",
    "declaration": {
        "schemaVersion": "1.5.0",
        "class": "Device",
        "async": true,
        "Common": {
            "class": "Tenant",
            "hostname": "tenant1.chassis2.f5demo.net",
            "myProvision": {
                "class": "Provision",
                "avr": "nominal",
                "ltm": "nominal",
                "asm": "nominal"
            },
            "myDns": {
                "class": "DNS",
                "nameServers": [
                    "<IP_ADDRESS>",
                    "<IP_ADDRESS>"
                ]
            },
            "myNtp": {
                "class": "NTP",
                "servers": [
                    "time.f5net.com"
                ],
                "timezone": "UTC"
            },
            "internal-localself": {
                "class": "SelfIp",
                "address": "<IP_ADDRESS>/24",
                "vlan": "vlan-444",
                "allowService": "all",
                "trafficGroup": "traffic-group-local-only"
            },
            "internal-self": {
                "class": "SelfIp",
                "address": "<IP_ADDRESS>/24",
                "vlan": "vlan-444",
                "allowService": "all",
                "trafficGroup": "traffic-group-1"
            },
            "external-localself": {
                "class": "SelfIp",
                "address": "<IP_ADDRESS>/24",
                "vlan": "vlan-555",
                "trafficGroup": "traffic-group-local-only",
                "allowService": "default"
            },
            "external-self": {
                "class": "SelfIp",
                "address": "<IP_ADDRESS>/24",
                "vlan": "vlan-555",
                "trafficGroup": "traffic-group-1",
                "allowService": "default"
            },
            "configsync": {
                "class": "ConfigSync",
                "configsyncIp": "/Common/internal-localself/address"
            },
            "failoverAddress": {
                "class": "FailoverUnicast",
                "address": "/Common/internal-localself/address"
            },
            "failoverGroup": {
                "class": "DeviceGroup",
                "type": "sync-failover",
                "members": [
                    "<IP_ADDRESS>",
                    "<IP_ADDRESS>"
                ],
                "owner": "<IP_ADDRESS>",
                "autoSync": true,
                "saveOnAutoSync": false,
                "networkFailover": true,
                "fullLoadOnSync": false,
                "asmSync": false
            },
            "trust": {
                "class": "DeviceTrust",
                "localUsername": "{{Tenant_Username}}",
                "localPassword": "{{Tenant_Password}}",
                "remoteHost": "/Common/failoverGroup/members/0",
                "remoteUsername": "{{Tenant_Username}}",
                "remotePassword": "{{Tenant_Password}}"
            },
            "myDbVariables": {
                "class": "DbVariables",
                "ui.advisory.enabled": "true",
                "ui.advisory.color": "red",
                "ui.advisory.text": "Configuration deployed with AS3. Do not make any change directly on the BIG-IP or those changes may be lost."
            },
            "admin": {
                "class": "User",
                "userType": "regular",
                "shell": "bash",
                "partitionAccess": {
                    "all-partitions": {
                        "role": "admin"
                    }
                },
                "password": "{{Tenant_Password}}"
            },
            "root": {
                "class": "User",
                "userType": "root",
                "newPassword": "{{Tenant_Password}}",
                "oldPassword": "{{Tenant_Password}}"
            }
        }
    },
    "targetHost": "{{Chassis2_Tenant1_IP}}",
    "targetUsername": "admin",
    "targetPassphrase": "admin",
    "bigIqSettings": {
        "failImportOnConflict": false,
        "conflictPolicy": "USE_BIGIQ",
        "deviceConflictPolicy": "USE_BIGIP",
        "versionedConflictPolicy": "KEEP_VERSION",
        "clusterName": "Tenant1-Cluster",
        "statsConfig": {
            "enabled": true,
            "zone": "default"
        },
        "snapshotWorkingConfig": false
    }
}

This was successful in BIG-IQ/BIG-IP.
Submit the following declaration on device 2:

{
    "class": "DO",
    "declaration": {
        "schemaVersion": "1.5.0",
        "class": "Device",
        "async": true,
        "Common": {
            "class": "Tenant",
            "hostname": "tenant1.chassis1.f5demo.net",
            "myProvision": {
                "class": "Provision",
                "avr": "nominal",
                "ltm": "nominal",
                "asm": "nominal"
            },
            "myDns": {
                "class": "DNS",
                "nameServers": [
                    "<IP_ADDRESS>",
                    "<IP_ADDRESS>"
                ]
            },
            "myNtp": {
                "class": "NTP",
                "servers": [
                    "time.f5net.com"
                ],
                "timezone": "UTC"
            },
            "internal-localself": {
                "class": "SelfIp",
                "address": "<IP_ADDRESS>/24",
                "vlan": "vlan-444",
                "allowService": "all",
                "trafficGroup": "traffic-group-local-only"
            },
            "internal-self": {
                "class": "SelfIp",
                "address": "<IP_ADDRESS>/24",
                "vlan": "vlan-444",
                "allowService": "all",
                "trafficGroup": "traffic-group-1"
            },
            "external-localself": {
                "class": "SelfIp",
                "address": "<IP_ADDRESS>/24",
                "vlan": "vlan-555",
                "trafficGroup": "traffic-group-local-only",
                "allowService": "default"
            },
            "external-self": {
                "class": "SelfIp",
                "address": "<IP_ADDRESS>/24",
                "vlan": "vlan-555",
                "trafficGroup": "traffic-group-1",
                "allowService": "default"
            },
            "configsync": {
                "class": "ConfigSync",
                "configsyncIp": "/Common/internal-localself/address"
            },
            "failoverAddress": {
                "class": "FailoverUnicast",
                "address": "/Common/internal-localself/address"
            },
            "failoverGroup": {
                "class": "DeviceGroup",
                "type": "sync-failover",
                "members": [
                    "<IP_ADDRESS>",
                    "<IP_ADDRESS>"
                ],
                "owner": "<IP_ADDRESS>",
                "autoSync": true,
                "saveOnAutoSync": false,
                "networkFailover": true,
                "fullLoadOnSync": false,
                "asmSync": false
            },
            "trust": {
                "class": "DeviceTrust",
                "localUsername": "{{Tenant_Username}}",
                "localPassword": "{{Tenant_Password}}",
                "remoteHost": "<IP_ADDRESS>",
                "remoteUsername": "{{Tenant_Username}}",
                "remotePassword": "{{Tenant_Password}}"
            },
            "myDbVariables": {
                "class": "DbVariables",
                "ui.advisory.enabled": "true",
                "ui.advisory.color": "red",
                "ui.advisory.text": "Configuration deployed with AS3. Do not make any change directly on the BIG-IP or those changes may be lost."
            },
            "admin": {
                "class": "User",
                "userType": "regular",
                "shell": "bash",
                "partitionAccess": {
                    "all-partitions": {
                        "role": "admin"
                    }
                },
                "password": "{{Tenant_Password}}"
            },
            "root": {
                "class": "User",
                "userType": "root",
                "newPassword": "{{Tenant_Password}}",
                "oldPassword": "{{Tenant_Password}}"
            }
        }
    },
    "targetHost": "{{Chassis1_Tenant1_IP}}",
    "targetUsername": "admin",
    "targetPassphrase": "admin",
    "bigIqSettings": {
        "failImportOnConflict": false,
        "conflictPolicy": "USE_BIGIQ",
        "deviceConflictPolicy": "USE_BIGIP",
        "versionedConflictPolicy": "KEEP_VERSION",
        "clusterName": "Tenant1-Cluster",
        "statsConfig": {
            "enabled": true,
            "zone": "default"
        },
        "snapshotWorkingConfig": false
    }
}

The 2nd BIG-IP is correctly configured except for the HA part. The DO declaration task on BIG-IQ runs until we get the following error message.

Task Failed: Timed out waiting for onboarding task to finish after 1800 seconds
or
Task Failed: Failed to get onboarding result: code: 400, message: Empty or unknown response found.
Expected Behavior
We were expecting to get the BIG-IP HA setup correctly as defined in the DO declarations.
Actual Behavior
The device trust and HA never get set up correctly.

From the documentation on Clustering (https://clouddocs.f5.com/products/extensions/f5-declarative-onboarding/latest/clustering.html#declaration-classes-for-a-cluster-of-big-ips) there is a note that mentions:

The DeviceTrust and DeviceGroup sections in both declarations should be identical. For DeviceTrust, if the remoteHost matches the management IP or one of the self IPs of the host on which it is running, that DeviceTrust section is ignored. If it does not match, then the device processing the declaration will send a request to the remote host to be added to trust. There is similar logic regarding the DeviceGroup owner. The owning device just creates the group, the other device requests to be added to the group.

I see that you have a different remoteHost in each declaration. The trust.remoteHost property of the first declaration should be "/Common/failoverGroup/members/1" or "<IP_ADDRESS>".

Thanks for the quick feedback @dstokesf5! I retried with the correct value for trust.remoteHost but getting the same failure/result.
However, looking at the logs, I noticed they were showing connectivity issues with <IP_ADDRESS> which was strange because I could ping and HTTPS <IP_ADDRESS> from <IP_ADDRESS> without any problem. Knowing in this case DO is running on BIG-IQ. I have the feeling somehow DO running on BIG-IQ is trying to connect to <IP_ADDRESS> while it should not (and also has no connectivity as the BIG-IQ does not have connectivity to the VLANs created on the BIG-IPs).
I retried the same 2 DO declarations but I used the management IP of device 1 ({{Chassis1_Tenant1_IP}}) for trust.remoteHost. The difference is BIG-IQ is able to reach the management IP of both devices and I was able to get the HA cluster and device trust setup this time.
I think there is a bug here, when DO runs on BIG-IQ regarding the trust.remoteHost when the IP used isn't the management IP or not reachable from BIG-IQ.

Device 1:
{
    "class": "DO",
    "declaration": {
        "schemaVersion": "1.5.0",
        "class": "Device",
        "async": true,
        "Common": {
            "class": "Tenant",
            "hostname": "tenant1.chassis2.f5demo.net",
            "myProvision": {
                "class": "Provision",
                "avr": "nominal",
                "ltm": "nominal",
                "asm": "nominal"
            },
            "myDns": {
                "class": "DNS",
                "nameServers": [
                    "<IP_ADDRESS>",
                    "<IP_ADDRESS>"
                ]
            },
            "myNtp": {
                "class": "NTP",
                "servers": [
                    "time.f5net.com"
                ],
                "timezone": "UTC"
            },
            "internal-localself": {
                "class": "SelfIp",
                "address": "<IP_ADDRESS>/24",
                "vlan": "vlan-444",
                "allowService": "all",
                "trafficGroup": "traffic-group-local-only"
            },
            "internal-self": {
                "class": "SelfIp",
                "address": "<IP_ADDRESS>/24",
                "vlan": "vlan-444",
                "allowService": "all",
                "trafficGroup": "traffic-group-1"
            },
            "external-localself": {
                "class": "SelfIp",
                "address": "<IP_ADDRESS>/24",
                "vlan": "vlan-555",
                "trafficGroup": "traffic-group-local-only",
                "allowService": "default"
            },
            "external-self": {
                "class": "SelfIp",
                "address": "<IP_ADDRESS>/24",
                "vlan": "vlan-555",
                "trafficGroup": "traffic-group-1",
                "allowService": "default"
            },
            "configsync": {
                "class": "ConfigSync",
                "configsyncIp": "/Common/internal-localself/address"
            },
            "failoverAddress": {
                "class": "FailoverUnicast",
                "address": "/Common/internal-localself/address"
            },
            "failoverGroup": {
                "class": "DeviceGroup",
                "type": "sync-failover",
                "members": [
                    "<IP_ADDRESS>",
                    "<IP_ADDRESS>"
                ],
                "owner": "<IP_ADDRESS>",
                "autoSync": true,
                "saveOnAutoSync": false,
                "networkFailover": true,
                "fullLoadOnSync": false,
                "asmSync": false
            },
            "trust": {
                "class": "DeviceTrust",
                "localUsername": "{{Tenant_Username}}",
                "localPassword": "{{Tenant_Password}}",
                "remoteHost": "<IP_ADDRESS>",
                "remoteUsername": "{{Tenant_Username}}",
                "remotePassword": "{{Tenant_Password}}"
            },
            "myDbVariables": {
                "class": "DbVariables",
                "ui.advisory.enabled": "true",
                "ui.advisory.color": "red",
                "ui.advisory.text": "Configuration deployed with AS3. Do not make any change directly on the BIG-IP or those changes may be lost."
            },
            "admin": {
                "class": "User",
                "userType": "regular",
                "shell": "bash",
                "partitionAccess": {
                    "all-partitions": {
                        "role": "admin"
                    }
                },
                "password": "{{Tenant_Password}}"
            },
            "root": {
                "class": "User",
                "userType": "root",
                "newPassword": "{{Tenant_Password}}",
                "oldPassword": "{{Tenant_Password}}"
            }
        }
    },
    "targetHost": "{{Chassis2_Tenant1_IP}}",
    "targetUsername": "admin",
    "targetPassphrase": "admin",
    "bigIqSettings": {
        "failImportOnConflict": false,
        "conflictPolicy": "USE_BIGIQ",
        "deviceConflictPolicy": "USE_BIGIP",
        "versionedConflictPolicy": "KEEP_VERSION",
        "clusterName": "Tenant1-Cluster",
        "statsConfig": {
            "enabled": true,
            "zone": "default"
        },
        "snapshotWorkingConfig": false
    }
}

Device 2:
{
    "class": "DO",
    "declaration": {
        "schemaVersion": "1.5.0",
        "class": "Device",
        "async": true,
        "Common": {
            "class": "Tenant",
            "hostname": "tenant1.chassis1.f5demo.net",
            "myProvision": {
                "class": "Provision",
                "avr": "nominal",
                "ltm": "nominal",
                "asm": "nominal"
            },
            "myDns": {
                "class": "DNS",
                "nameServers": [
                    "<IP_ADDRESS>",
                    "<IP_ADDRESS>"
                ]
            },
            "myNtp": {
                "class": "NTP",
                "servers": [
                    "time.f5net.com"
                ],
                "timezone": "UTC"
            },
            "internal-localself": {
                "class": "SelfIp",
                "address": "<IP_ADDRESS>/24",
                "vlan": "vlan-444",
                "allowService": "all",
                "trafficGroup": "traffic-group-local-only"
            },
            "internal-self": {
                "class": "SelfIp",
                "address": "<IP_ADDRESS>/24",
                "vlan": "vlan-444",
                "allowService": "all",
                "trafficGroup": "traffic-group-1"
            },
            "external-localself": {
                "class": "SelfIp",
                "address": "<IP_ADDRESS>/24",
                "vlan": "vlan-555",
                "trafficGroup": "traffic-group-local-only",
                "allowService": "default"
            },
            "external-self": {
                "class": "SelfIp",
                "address": "<IP_ADDRESS>/24",
                "vlan": "vlan-555",
                "trafficGroup": "traffic-group-1",
                "allowService": "default"
            },
            "configsync": {
                "class": "ConfigSync",
                "configsyncIp": "/Common/internal-localself/address"
            },
            "failoverAddress": {
                "class": "FailoverUnicast",
                "address": "/Common/internal-localself/address"
            },
            "failoverGroup": {
                "class": "DeviceGroup",
                "type": "sync-failover",
                "members": [
                    "<IP_ADDRESS>",
                    "<IP_ADDRESS>"
                ],
                "owner": "<IP_ADDRESS>",
                "autoSync": true,
                "saveOnAutoSync": false,
                "networkFailover": true,
                "fullLoadOnSync": false,
                "asmSync": false
            },
            "trust": {
                "class": "DeviceTrust",
                "localUsername": "{{Tenant_Username}}",
                "localPassword": "{{Tenant_Password}}",
                "remoteHost": "<IP_ADDRESS>",
                "remoteUsername": "{{Tenant_Username}}",
                "remotePassword": "{{Tenant_Password}}"
            },
            "myDbVariables": {
                "class": "DbVariables",
                "ui.advisory.enabled": "true",
                "ui.advisory.color": "red",
                "ui.advisory.text": "Configuration deployed with AS3. Do not make any change directly on the BIG-IP or those changes may be lost."
            },
            "admin": {
                "class": "User",
                "userType": "regular",
                "shell": "bash",
                "partitionAccess": {
                    "all-partitions": {
                        "role": "admin"
                    }
                },
                "password": "{{Tenant_Password}}"
            },
            "root": {
                "class": "User",
                "userType": "root",
                "newPassword": "{{Tenant_Password}}",
                "oldPassword": "{{Tenant_Password}}"
            }
        }
    },
    "targetHost": "{{Chassis1_Tenant1_IP}}",
    "targetUsername": "admin",
    "targetPassphrase": "admin",
    "bigIqSettings": {
        "failImportOnConflict": false,
        "conflictPolicy": "USE_BIGIQ",
        "deviceConflictPolicy": "USE_BIGIP",
        "versionedConflictPolicy": "KEEP_VERSION",
        "clusterName": "Tenant1-Cluster",
        "statsConfig": {
            "enabled": true,
            "zone": "default"
        },
        "snapshotWorkingConfig": false
    }
}

Restnoded logs on BIG-IQ:
Fri, 12 Mar 2021 02:33:25 GMT - finest: [f5-declarative-onboarding: restWorker.js] tryUntil: got error {"code":"ETIMEDOUT","errno":"ETIMEDOUT","syscall":"connect","address":"<IP_ADDRESS>","port":443}
Fri, 12 Mar 2021 02:33:25 GMT - finest: [f5-declarative-onboarding: restWorker.js] typeof err object
Fri, 12 Mar 2021 02:33:25 GMT - finer: [f5-declarative-onboarding: restWorker.js] tryUntil error: connect ETIMEDOUT <IP_ADDRESS>:443 tries left: 0
Fri, 12 Mar 2021 02:33:25 GMT - finest: [f5-declarative-onboarding: restWorker.js] tryUntil: retryOrReject: numRemaining: 0 , code: ETIMEDOUT , message: connect ETIMEDOUT <IP_ADDRESS>:443
Fri, 12 Mar 2021 02:33:25 GMT - finer: [f5-declarative-onboarding: restWorker.js] Max tries reached.
Fri, 12 Mar 2021 02:33:25 GMT - finest: [f5-declarative-onboarding: restWorker.js] tryUntil: got error {"code":"ETIMEDOUT","errno":"ETIMEDOUT","syscall":"connect","address":"<IP_ADDRESS>","port":443,"message":"tryUntil: max tries reached: connect ETIMEDOUT <IP_ADDRESS>:443","name":"Error"}
Fri, 12 Mar 2021 02:33:25 GMT - finest: [f5-declarative-onboarding: restWorker.js] typeof err object
Fri, 12 Mar 2021 02:33:25 GMT - finer: [f5-declarative-onboarding: restWorker.js] tryUntil error: tryUntil: max tries reached: connect ETIMEDOUT <IP_ADDRESS>:443 tries left: 75
Fri, 12 Mar 2021 02:33:25 GMT - finest: [f5-declarative-onboarding: restWorker.js] tryUntil: retryOrReject: numRemaining: 75 , code: ETIMEDOUT , message: tryUntil: max tries reached: connect ETIMEDOUT <IP_ADDRESS>:443
Fri, 12 Mar 2021 02:33:35 GMT - fine: [f5-declarative-onboarding: restWorker.js] list <IP_ADDRESS> /shared/echo/available
Fri, 12 Mar 2021 02:35:43 GMT - finest: [f5-declarative-onboarding: restWorker.js] tryUntil: got error {"code":"ETIMEDOUT","errno":"ETIMEDOUT","syscall":"connect","address":"<IP_ADDRESS>","port":443}
Fri, 12 Mar 2021 02:35:43 GMT - finest: [f5-declarative-onboarding: restWorker.js] typeof err object
Fri, 12 Mar 2021 02:35:43 GMT - finer: [f5-declarative-onboarding: restWorker.js] tryUntil error: connect ETIMEDOUT <IP_ADDRESS>:443 tries left: 0
Fri, 12 Mar 2021 02:35:43 GMT - finest: [f5-declarative-onboarding: restWorker.js] tryUntil: retryOrReject: numRemaining: 0 , code: ETIMEDOUT , message: connect ETIMEDOUT <IP_ADDRESS>:443
Fri, 12 Mar 2021 02:35:43 GMT - finer: [f5-declarative-onboarding: restWorker.js] Max tries reached.
Fri, 12 Mar 2021 02:35:43 GMT - finest: [f5-declarative-onboarding: restWorker.js] tryUntil: got error {"code":"ETIMEDOUT","errno":"ETIMEDOUT","syscall":"connect","address":"<IP_ADDRESS>","port":443,"message":"tryUntil: max tries reached: connect ETIMEDOUT <IP_ADDRESS>:443","name":"Error"}
Fri, 12 Mar 2021 02:35:43 GMT - finest: [f5-declarative-onboarding: restWorker.js] typeof err object
Fri, 12 Mar 2021 02:35:43 GMT - finer: [f5-declarative-onboarding: restWorker.js] tryUntil error: tryUntil: max tries reached: connect ETIMEDOUT <IP_ADDRESS>:443 tries left: 74
Fri, 12 Mar 2021 02:35:43 GMT - finest: [f5-declarative-onboarding: restWorker.js] tryUntil: retryOrReject: numRemaining: 74 , code: ETIMEDOUT , message: tryUntil: max tries reached: connect ETIMEDOUT <IP_ADDRESS>:443
Fri, 12 Mar 2021 02:35:53 GMT - fine: [f5-declarative-onboarding: restWorker.js] list <IP_ADDRESS> /shared/echo/available

Communication from device 2 to device 1:
[admin@tenant1:/S1-green-P::Active:Standalone] log # ifconfig vlan-444
vlan-444: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet <IP_ADDRESS>  netmask <IP_ADDRESS>  broadcast <IP_ADDRESS>
        inet6 fe80::294:a1ff:fe8e:d01b  prefixlen 64  scopeid 0x20<link>
        ether 00:94:a1:8e:d0:1b  txqueuelen 1000  (Ethernet)
        RX packets 93  bytes 16942 (16.5 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 30  bytes 3234 (3.1 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

[admin@tenant1:/S1-green-P::Active:Standalone] log # ping <IP_ADDRESS>
PING <IP_ADDRESS> (<IP_ADDRESS>) 56(84) bytes of data.
64 bytes from <IP_ADDRESS>: icmp_seq=1 ttl=255 time=1.08 ms
^C
--- <IP_ADDRESS> ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 1.086/1.086/1.086/0.000 ms
[admin@tenant1:/S1-green-P::Active:Standalone] log # curl -k https://<IP_ADDRESS> | tail -5
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100  3991  100  3991    0     0  42037      0 --:--:-- --:--:-- --:--:-- 42913
  </tr>

</table>
</body>
</html>

For DO, DO is not installed on the BIG-IPs. So, when DO is running on BIG-IQ, all commands are sent from BIG-IQ and BIG-IQ will need connectivity to whatever addresses are used. This is different than AS3 which actually runs on the BIG-IPs.

Thanks @seattlevine! good to know. I think this should be changed though, when setting up HA with BIG-IP self-ips, we should not require connectivity between the BIG-IQ and those self-ips which could be in a dedicated VLAN for the HA communication. As a workaround, we used the management IP which is reachable from BIG-IQ but I think some customers would like to set this up using other networks than the management network.

@dstokesf5, I worked with @jimmccarron and we confirmed we can use the management IP used to build the DeviceTrust and still use a dedicated HA VLAN for the ConfigSync and FailoverUnicast.
I think now, we would like DO to improve the error message showing to the user in case they don't use a reachable IP address from BIG-IQ in the DeviceTrust.

I have added AUTOTOOL-2349 to our internal product backlog to improve the error message when the DeviceTrust IP is unreachable.


:bug: fix: config

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Comparison is base (811995a) 2.35% compared to head (f87e4b4) 2.35%.
Report is 1 commits behind head on master.

Additional details and impacted files
@@          Coverage Diff           @@
##           master     #46   +/-   ##
======================================
  Coverage    2.35%   2.35%
======================================
  Files         127     127
  Lines        8210    8210
  Branches      156     156
======================================
  Hits          193     193
  Misses       8017    8017

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


Un-nest configuration

Currently our configuration has separate entries for each job manager.  Most of the keys within each of these entries are the same.  Should we consider lifting these common keys out to the jobqueue: namespace directly?
We would still want to support namespaced configurations for users with multiple job queuing systems on the same NFS, but this could be a special case, rather than required.

No strong feelings on this one but I am not sure how nice this plays with named configuration aka config_name. With config_name, you can copy and paste the slurm section in jobqueue.yaml, change slurm to my-config and use the my-config section like this:
cluster = SLURMCluster(config_name='my-config')

We would still want to support namespaced configurations

How would you propose to handle this ? I think we don't want to simplify the configuration at the expense of additionnal code.

Closing this for now as stale and no strong need. @mrocklin feel free to open it again if you have some suggestion on how to do this.


Run e2e/xss/init w override

Description of changes
This PR enables applying auth role overrides to new environments. Replaces https://github.com/aws-amplify/amplify-cli/pull/9677 which could not be updated due to branch protection rules.

Issue #, if available
https://github.com/aws-amplify/amplify-cli/issues/9643

Description of how you validated changes
amplify-dev init
amplify-dev override project
amplify-dev push
amplify-dev add env envb

Without this change, the result is that envb uses an auth role that does not match the override. With this change, envb uses an auth role that does match the override.
Checklist

[x] PR description included
[x] yarn test passes
[x] Tests are changed or added

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Codecov Report

Merging #9688 (2bd4172) into master (657c344) will increase coverage by 0.10%.
The diff coverage is 45.79%.

:exclamation: Current head 2bd4172 differs from pull request most recent head 3b7ebc4. Consider uploading reports for the commit 3b7ebc4 to get more accurate results

@@            Coverage Diff             @@
##           master    #9688      +/-   ##
==========================================
+ Coverage   52.90%   53.00%   +0.10%
==========================================
  Files         830      830
  Lines       45948    46012      +64
  Branches     9812     9826      +14
==========================================
+ Hits        24308    24390      +82
+ Misses      19628    19604      -24
- Partials     2012     2018       +6

Impacted Files
Coverage Δ

...service-walkthroughs/execPermissionsWalkthrough.ts
71.22% <ø> (+0.50%)
:arrow_up:

...category-geo/src/service-stacks/placeIndexStack.ts
100.00% <ø> (ø)

...mplify-category-notifications/lib/channel-Email.js
0.00% <0.00%> (ø)

...lify-category-notifications/lib/pinpoint-helper.js
0.00% <0.00%> (ø)

...ckages/amplify-cli-core/src/customPoliciesUtils.ts
87.09% <ø> (ø)

...-transformer/src/graphql-searchable-transformer.ts
93.43% <ø> (ø)

...awscloudformation/src/graphql-transformer/utils.ts
62.50% <0.00%> (-0.61%)
:arrow_down:

packages/amplify-util-mock/src/api/api.ts
0.00% <0.00%> (ø)

...es/amplify-util-mock/src/api/resolver-overrides.ts
0.00% <0.00%> (ø)

...c/extensions/amplify-helpers/auth-notifications.ts
28.18% <20.00%> (-5.97%)
:arrow_down:

... and 9 more

Continue to review full report at Codecov.

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


Support for Sparkfun Promicro RP2040

Hi,
Is there any chance you can add support for the Sparkfun Promicro RP2040
That board uses the GPIO17 for SCL and GPIO16 for SDA

I got it work on  my fork. I would be great if we can merge it back to this repo. I leave it to you:
https://github.com/ahmadexp/rp2040-i2c-interface
Thank you so much for this awesome project.


fix: Author "cgranad" -> "cgranade"

Noticed from build failures

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

articles/install-guide/command-line.md
:white_check_mark:Succeeded

articles/install-guide/vs-code.md
:white_check_mark:Succeeded

articles/libraries/chemistry/samples/end-to-end.md
:white_check_mark:Succeeded

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


Add Support for CloudEvents

CloudEvents a CNCF standard for event payloads just reached 1.0.  It'd be great to have out-of-the-box support with Spring Cloud Functions.  So we could do:
Function<CloudEvent, CloudEvent> foo()

There is an existing API for the payload, marshaling, unmarshalling, but it doesn't yet support version 1.0 of the spec
		<dependency>
			<groupId>io.cloudevents</groupId>
			<artifactId>cloudevents-api</artifactId>
			<version>0.3.1</version>
		</dependency>

Adding this will make integration with Knative Events easier.

@jamesward I knew sooner or later we'll reconnect ;)

@jamesward the lib now has 1.0 support, see: https://github.com/cloudevents/sdk-java/tree/v1.0.0

@olegz have you started this yet? Playing around with functions that accept a CloudEvent as input and would like to have something that implements a JsonMapper and gives me a CloudEvent back. I'm not using any of the SI or SCSt dependencies, maybe this should live either in SCFn along with the Jackson/Gson Mappers or somewhere else.

@trisberg No, I have not started yet, but as I said earlier it appears all that's needed is MessageConverter which is capable of converting from/to CloudEvents. @jamesward given that one of the drivers in our frameworks to pick the correct MessageConverter is content type (e.g., application/json), is there a known or widely used content type for CloudEvents? Something we can rely on?

It does look like the latest spec uses some specific Content-Type values:
https://github.com/cloudevents/spec/blob/v1.0/http-protocol-binding.md#3-http-message-mapping
Maybe @duglin can help clarify though.

Hi - yes the CE spec does define a content-type that will help you determine if the incoming message is a CE or not - at least for structured CE mode (meaning the HTTP body is wrapped in a CE structure). However, knowing whether some random message is binary CE or not is harder.  To try to address this I just created this: https://github.com/cloudevents/spec/pull/577

@jamesward @duglin I am trying, but it appears based on some of the arguments from the gate-keepers of the Cloud Event SDK that we should not even be using CloudEvent type. That it is an anti pattern to have user code to depend on CloudEvent type.
If that's the case then perhaps be we should further clarify as to what such support for us would even mean.

Should CloudEvent be instead converted to Message<T>, which is more idiomatic for Spring?

@meltsufin
Not at all. Spring Message is a central fixture of spring-messaging and will remain as such, plus Message can easily represent the cloud event (if you simply go by the spec) as it already provides a compatible structure.
So, it is really a question of CloudEvent as a type and whether it has any additional value.
In any event, I do envision simple transformation/conversion of Message to/from CloudEvent.

I guess this comes down to whether the CloudEvent SDK folks see it as a shareable construct.  Should APIs ever build on CloudEvent?  If not, then yeah we could just marshal CloudEvent payloads into Message (and out).  But if that is the case, why is there even a CloudEvent SDK?

@jamesward @duglin I am trying, but it appears based on some of the arguments from the gate-keepers of the Cloud Event SDK that we should not even be using CloudEvent type. That it is an anti pattern to have user code to depend on CloudEvent type.
If that's the case then perhaps be we should further clarify as to what such support for us would even mean.

I've asked if we can discuss this on the SDK call tomorrow (right after the normal CE call, which is from 12-1 ET unless it ends early).  Anyone is free to join.   See: https://docs.google.com/document/d/1OVF68rpuPK5shIHILK9JOqlZBbfe91RNzQ7u_P7YCDE/edit#

Thank you @duglin I will join. Perhaps @bsideup  can do as well

So it looks like maybe some progress on the cloudevents API side of things?

Indeed @jamesward we now have cleanly defined CloudEvent - https://github.com/cloudevents/sdk-java/tree/master/api/src/main/java/io/cloudevents

Fantastic! Looks much better. Thanks for working through that!

@jamesward things are finally moving. More to come, keeping it open for now

This has been addressed in spring-cloud-function-context module.
However, this work will be contributed to CNCF java SDK. Once accepted there will be minor dependency change, but given that outside of CloudEventAttributesProvider user generally  would not interact with the API, this should not be an issue. In any event, by the time 3.1.0.RELEASE is out it should be settled.
This README contains initial usage documentation and sample instructions.
This will also be donated to CNCF java SDK


new notation for Unicode code points in ES grammar

In https://github.com/tc39/ecma262/pull/3310, we are planning to refer to Unicode code points directly in the grammar using the notation <U+0000 (NULL)> (with < and > encoded as HTML entities < and > respectively). Currently, esmeta doesn't support parentheses in this position, giving us this error:

It is resolved by https://github.com/es-meta/esmeta/pull/222 and merged at https://github.com/tc39/ecma262/pull/3325. So, I close this issue.


Make tests work again

Description
This PR is intended to make the tests pass again and addresses three problems:

The mariadb image had, at least on my computer, an insane first startup time from arount 5 minutes. So when the tests started the database was not yet running and all mailserver_default tests thus failed. Fixed by using the mysql:5.7 docker image instead of mariadb.
Both mariadb and mysql docker image do not bind to <IP_ADDRESS> anymore and thus are not reachable from outside. This was fixed by adding a config file and setting bind-address to <IP_ADDRESS>
The new postfix seems not to allow emails from example.com as it is missing an MX record. I changed them to @gmail.com for now but I am not sure if that is the best choice. Maybe someone has a better idea? I chose it because it exists and it's unlikely to land on any blacklist and thus interfering with other tests.

Type of change

[x] Test (adding missing tests or correcting existing ones)

Status

[x] Ready
[ ] In development
[ ] Hold

Todo List

maybe change test sender domain to something better

How has this been tested ?

internal tests

Hmmm, I had this issue (random mailserver failing its tests) before and am not sure where it comes from. Rerunning the tests usually solves this problem (obviously not the best solution). Maybe its a timing problem?
Can you rerun the test or do I have to push another empty commit?

I took a closer look at that problem. After running the tests 7 times it occured again. This time with the mailserver_default.
This is the output from docker logs mailserver_default:
[INFO] Redis hostname found in /etc/hosts
[INFO] Traefik SSL certificates not used
[INFO] No Let's encrypt live directory found
[INFO] Using /var/mail/ssl/selfsigned/ folder
[INFO] Setting up container
[INFO] Creating DKIM keys for domain domain.tld
[INFO] Creating DKIM keys for domain domain2.tld
[INFO] Creating DKIM keys for domain domain3.tld
[INFO] Override parameter in main.cf : max_idle = 600s
[INFO] Override parameter in main.cf : readme_directory = /tmp
[INFO] Override service parameter in master.cf : submission/inet/syslog_name=postfix/submission-custom
[INFO] Custom Postfix configuration file loaded
[INFO] Debug mode is disabled
[INFO] ClamAV is enabled
[INFO] Fetchmail forwarding is disabled
[INFO] Automatic GPG encryption is disabled
[INFO] ManageSieve protocol is enabled
[INFO] DKIM/ARC signing is enabled
[INFO] Greylisting policy is enabled
[INFO] Ratelimiting policy is disabled
[INFO] POP3 protocol is disabled
[INFO] Unbound DNS resolver is enabled
[INFO] DOCKER IMAGE UNDER TESTING
[INFO] sender_access file found, sender access check enabled
[INFO] Missing SSSE3 CPU instructions, hyperscan is disabled
[INFO] clamav-unofficial-sigs is enabled (user configuration found)
[INFO] Finished container setup
[INFO] Starting services
s6-svc: fatal: unable to control /services/rsyslogd: supervisor not listening
[INFO] Checking for watchable SSL certificates
[INFO] No watchable SSL certificate mounts - disabling SSL watcher

Could this have something to do with #372 maybe?


Popup for unmatched series is broken

Description
I found a bug with a series that did not have the tvdb ID added. The popup for matching a series is missing images and the text is misplaced. I tried the same series in Overseerr and it does not have this issue.
Version
2.0.1
Steps to Reproduce

Look up any series that does not have a linked tvdb ID on tmdb
Click the request button
Observe the popup window

Screenshots
Jellyseerr

Overseerr

Logs
No response
Platform
desktop
Device
Apple MacBook Pro 14"
Operating System
macOS 14.7.1 (Sonoma)
Browser
Firefox 132.0
Additional Context
No response
Code of Conduct

[X] I agree to follow Jellyseerr's Code of Conduct

:tada: This issue has been resolved in version 2.2.0 :tada:
The release is available on:

v2.2.0
GitHub release

Your semantic-release bot :package::rocket:


Case Insensitivity and Partial Words in Search

The current global search feature only looks for exact matches. In everyday use, I'm accustomed to case-insensitivity and being able to search for partial words (if there is "SilverBullet" in any file, I'd like to find it by searching for "silver" or "bullet".

Yeah I'm not surprised. The whole full text search thing needs to be properly looked and may have to be redone. What's there now is the least effort thing to get something working, I'm sure it can use a lot of tweaking.

Regarding the search function, links have the highlight syntax and are not clickable

Do you prefer to have minimal dependencies? If not, we could think about using a dedicated library like https://github.com/krisk/Fuse


Mpreston/readme update

Added the documentation for tutorials, Readme and the migration guide the v2 of the client.

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.1 out of 2 committers have signed the CLA.:white_check_mark: splinterific:x: Mark PrestonMark Preston seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


[Feature Request] Support for DenseOres Mod

Any way to add support for DenseOres?

You can do it via the configuration file yourself.
I am not actively working on Minecraft mods anymore, so I will not make any code changes to this.


E319: Sorry, the command is not available in this version:

This is what I get when trying to run the :Search command. I have python installed. Running on OpenBSD 5.8.

Try to update with :PluginUpdate. The plugin was updated earlier today (01/05)


SKElement crash if size isnt set (Width = NaN or/and Height = NaN)

In WPF skiasharp library the SKElement is added in autogrow (width = Nan and/or Height = NaN) the project crashes when it try to create a WritableBitmap with zero dimension

Just pushed out a release that should resolve this: https://github.com/mono/SkiaSharp/releases/tag/v1.58.1


[DO NOT MERGE] Auto PR to update dependencies of pilot

This PR will be merged automatically once checks are successful.

@istio-testing: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/pilot-presubmit.sh
e387fadad704a56d6990d96f5bc3efd4b126cc3e
link
/test pilot-presubmit

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.


fix: remove clear() and update Validation component to use useEffect() instead

Updated Validation component to use useEffect() to automatically call addValidator() and removeValidator() and removed the hackier (and broken) solution of calling validator.clear() in the FormProvider.

resolves #32


Feature: support resizing and downsampling

As you all know, the native fresco library supports several image resizing options.
However, this plugin is not yet exposed the features for a long time.
I have personally extended this plugin for enabling resize and downsampling options of native fresco library, and applied to my nativescript app which manages thousands of image files including jpg,png,and gif. So far, the customized plugin handles the image resizing quite well without any noticeable problems.
How do you feel about adding support this feature to nativescript-fresco?
I am ready to contribute to this project if needed.
Thanks in advance.

Hi @mintyweazel ,
Thank you for writing to us and bringing this to our attention.
Indeed this native functionality has not been exposed in the plugin. We would love to see and welcome any contributions to this or any other nativescript plugin so do not hesitate to make your PR. If you want to make your contribution just submit your PR and we are going to review it, merge it and release a new version of the plugin as soon as possible.

Available in 3.1.0


Web Inconsistency: Sometimes horizontally centered node has incorrect left

Repro
The innermost node is being horizontally centered but it is given an incorrect left position. Here's a small repro which I extracted from my team's app:

Expected Output
{layout: {width: 52, height: 52, top: 0, left: 72}, children: [
  {layout: {width: 72, height: 52, top: 0, left: -10}, children: [
    {layout: {width: 52, height: 52, top: 0, left: 10}, },
  ]},
]},

Actual Output
The innermost node's left is 0 but it should be 10.
{layout: {width: 52, height: 52, top: 0, left: 72}, children: [
  {layout: {width: 72, height: 52, top: 0, left: -10}, children: [
    {layout: {width: 52, height: 52, top: 0, left: 0}, },
  ]},
]},

I confirmed this doesn't repro in master (bcc36cc).


refactor: add "metricbot" to groupId

rationale:
I have more than one twitter project and do not want to cause split packages.
Then, I already configured renovate...

fixed by https://github.com/bmarwell/twitter-metricbot/pull/96


Add "module" estimator spec

Import a (possibly local) module and look for a global named estimator

This was my solution to #180


[meson] Update meson for ubuntu 20.04

Update meson to work with ubuntu 20.04
Also add some missing checks
Signed-off-by: Parichay Kapoor<EMAIL_ADDRESS>

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

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


Sub-sub-commands can not have a switch with the same name in gli-2.0.0-rc2.

This code raises exception.
		command :admin do |c|
			c.command :add do |c_add|
				c_add.flag :milestone
			end
			c.command :delete do |c_delete|
				c_delete.flag :milestone
			end
			c.command :misc do |c_misc|
				c_misc.switch :verbose
			end
		end

gli/dsl.rb:171:in verify_unused_in_option': milestone has already been specified as a flag in the command admin (ArgumentError)         from gli/dsl.rb:164:in block in verify_unused'
from gli/dsl.rb:163:in each'         from gli/dsl.rb:163:in verify_unused'
from gli/dsl.rb:65:in flag'         from gli/command_support.rb:42:in flag'
from gli/command_support.rb:40:in flag'         from options.rb:97:in block (2 levels) in define_admin_commands'

Hi @davetron5000. If this issue is fixed then maybe https://github.com/davetron5000/gli/wiki/Subcommands#flags-and-switches section could be updated as well, what do you think?

It's been a long time since this issue was opened—do you want to take a stab at updating the wiki?

@davetron5000 can you please check if something like this would be fine : https://github.com/kowal/gli/wiki/Subcommands-updated.
Side question: How do we access parent-command options? I found that options[GLI::Command::PARENT] works but this isn't public API, right?

That seems ok—are you proposing changing the entire Subcommands page to that?  If not, go ahead and edit the GLI wiki directly.  I can look at the diff like that and we can tweak it as needed.
GLI::Command::PARENT is public—it's documented in the API docs, but probably not well documented elsewhere.

@davetron5000 I've updated Flags and Switches section. Also added new section 'Accessing parent command options'.

Awesome, thanks!  I tweaked it a bit, but this is much better than before

Cool, thanks!


BatchedExecutor Double Buffering

Added "double buffering" to the batched executor, this allows conversations to be prompted (adding tokens to one batch) while inference is still running on the other batch.
There's some special consideration given to errors. If an error occurs during inference the previous batch is swapped back to be the "next" batch. This allows infer to be called again (after fixing whatever caused the error).

Martin,
This is probably not the right place to mention this, but I find the batched executor examples confusing and difficult to understand. In a user point of view I would prefer something more logical and easy to understand focusing on important use cases.
Some explanation about what I mean:

BatchedExecutorFork.cs:
o I find the term 'Fork' confusing. Why don't you just use 'Clone', clone is immediately clear to anyone?
o "This demonstrates generating multiple replies to the same prompt, with a shared cache" this is clear, so you get happy that you will see something great, but then it gets ugly starting with this "// Create the root node of the tree". The whole "Node" class and the use of it is confusing. I think that in some way the Node class should not be needed in this example or should be hidden.
o then "// Occasionally fork all the active conversations" => "root.Split();". Here "fork" and then "split",... confusing and honestly I do not clearly understand what is happening.
o The example promises "generating multiple replies to the same prompt", but I do not see where those replies are.

BatchedExecutorGuidance.cs:
o here again the term "Fork" is a bit confusing. Is this equivalent to "Clone"?
o "var unguidedSampler = new GuidedSampler(null, weight);" here the use of "GuidedSampler" for "unguidedSampler" is a bit confusing.
o I would rename the "GuidedSampler" to "Sampler" and then add a method called "Sample" where I would add "guidedDecoder.Add(g);   guided.Prompt(g);   guidance.Prompt(g);" that in the example there is only one line "guidedSampler.Sample()" and thus Add and Prompt would be done once in the "Sampler" only.
o I am not sure that the separation of the decoder and sampler is logical in point of view of a user. As a user I would expect decoding and the sampling should be hidden. I think that there is just too much detail here.
o what is the meaning of the "n_len" parameter here? Is this equivalent to the number of maxtokens parameter we use to limit the generation? Is this a real world scenario here as we have to do in an application if we use the library?

BatchedExecutorRewind.cs:
o here the use of the "class Node" again... not sure what the meaning of this here again.
o not clear what the meaning of rewind is. Is this equivalent to saving the context state and then reloading it to that former state? If yes, then all of this should be hidden or not even needed and just simply use save/load context state.

So, what I mean here is that for an end user all of this will be very overwhelming and confusing. What they would want is simple, but real word scenarios that they can immediately understand and use in their work.

OK, if this is for library developers, then I would like to suggest to create a separate solution for this type of examples. The 'examples' should be helping the users of the library and not confusing them 😵. Or when you distribute the code to low level and high level parts, maybe this can then be done by moving these examples to the low level part.
I think that several names and logic should be changed even for library developers. I will not repeat the above, but just mention that you did not convince me with your explanation of 'fork' 😅. If I fork a github repository, then it is copied completely and I do not use unix, so nothing helps here. Maybe you should find a better name. It would probably be easier to understand if you would 'Clone' the context, which probably means what you mean, if I understand you well.

I will not repeat the above, but just mention that you did not convince me with your explanation of 'fork'

@zsogitbe For the current implementations in LLamaSharp, there's little semantic difference between using Fork and using Clone. However, I agree to use Fork because it's more clear when it comes to beam search. In llama.cpp, beam search is totally wrapped as an exported C API so an abstraction of SequenceGroup is not very necessary. However, since beam search is not too difficult for users to implement it themselves, we should take it into account when naming the APIs.
Beam search in LLM can be described as following steps.

Set a SequenceGroup with one sequence, which contains the prompt. Then set the size of beam search to 3.
Prefill the the first sequence (let's call it seq1), and fork seq2 and seq3 from seq1.
Sample the output of seq1 and take the 3 highest scoring tokens. The highest one will be added to seq1, the second to seq2, the third to seq3.
Compute seq1, seq2 and seq3 simultaneously, and get the top3 scoring tokens for each sequence. Now we have 9 candidate sequence.
Sort the 9 sequences by the global score, and take the highest 3 sequences as seq1, seq2 and seq3 for the next loop. The global score here refers to a score computed with all the tokens generated till now. Let's assume the global scores are [[0.2, 0.3, 0.1], [0.5, 0.2, 0.7], [0.8, 0.9, 0.2]]. Two of the highest 3 scores appears in the original seq3, and the other appears in the original seq2. Now, we need to keep the sequence with 0.9 as the next seq3 (only append the token), and make the one with 0.8 as the next seq3 (fork and append)
Loop step 4 and step 5.

After the Fork (or Clone as you preferred), the sequences are still closely related to each other in the same SequenceGroup.
Taking your analogy of repo clone&fork, please regard SequenceGroup as Github, the earliest sequence as SciSharp/LLamaSharp.  Besides, there're only at most 3 best LLamaSharp repos can exist at the same time. Then, zsogitbe/LLamaSharp, martindevans/LLamaSharp and SciSharp/LLamaSharp will both have 3 branches developed. If two of your branches have the highest scores, one of them will be merged back to SciSharp/LLamaSharp. Obviously, the semantic here is more likely to be Fork instead of Git clone.
There's also another reason: after forking the sequence, the kv-cache of it will not be copied at once. The copying happens only when  one of the sequences is used to generate the next token.

There's also another reason: after forking the sequence, the kv-cache of it will not be copied at once. The copying happens only when one of the sequences is used to generate the next token.

The copying doesn't happen then either!
If you do this:

Seq1, generate [A, B, C]
Fork into Seq2
Seq1, generate [A, B, C, D, E, F]
Seq2, generate [A, B, C, X, Y, Z]

Then you will have 9 occupied KV slots, like this: [A, B, C, D, E, F, X, Y, Z]. [A, B, C] is never copied, it is always shared between the two sequences.
This is why the save and load method for cloning a conversation, instead of forking it, is bad. As soon as you save and load the slots are no longer shared and you are taking up a lot more memory and compute.