feat(aws-lambda-stepfunctions): aws-lambda-stepfunctions implementation

Issue #271 , if available:
Description of changes:
Transitioning from aws-lambda-step-function to new construct aws-lambda-stepfunctions to adhere to consistent naming conventions.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

AWS CodeBuild CI Report

CodeBuild project: codebuildgithubautobuildPro-fkVQbXRiQi6A
Commit ID: 513cc143e1f744c67c6dbba2832b292dc0129c2c
Result: FAILED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: codebuildgithubautobuildPro-fkVQbXRiQi6A
Commit ID: 5db262609ae86d151f0657732608121a9f13af00
Result: FAILED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: codebuildgithubautobuildPro-fkVQbXRiQi6A
Commit ID: b3ab8e4cca6dc0d88dd2a0416b33547f6c50c94e
Result: FAILED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: codebuildgithubautobuildPro-fkVQbXRiQi6A
Commit ID: b87238f61cae066060db425e64b7793a8c440db8
Result: FAILED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: codebuildgithubautobuildPro-fkVQbXRiQi6A
Commit ID: ae3934c97682995977064a01f930f7f03060125f
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: codebuildgithubautobuildPro-fkVQbXRiQi6A
Commit ID: 5cee402d0419f615794a35b1f74c29926eceddda
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: codebuildgithubautobuildPro-fkVQbXRiQi6A
Commit ID: 477a86adf045160d0b5381c7c502a764723748f7
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository


add containerd http proxy configure daemonset

This daemonset allows users to configure containerd http proxy.

Can you also run shellcheck as part of presubmit?

I'm not sure how to run shellcheck as github presubmit, but I ran it locally and have fixed two small issues.

Hi @SergeyKanzhelev, could you take a look please?


modified: CMakeLists.txt and pyproject.tom

We change the version of cmake and numpy<2.

[ ] My PR includes a link to the issue that I am addressing

Code Quality

[ ] I have read the Contribution Guide
[ ] My code follows the code style of this project
[ ] My code builds (or compiles) cleanly without any errors or warnings
[ ] My code contains relevant comments and necessary documentation

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:
:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.


Evaluation dataset for GPT-3 generations

Hi, I'm woundering if you could release your evaluation dataset for GPT-3 generations, including PubMedQA, XSum, and WritingP (each 150 samples). Since the randomness in OpenAI services, a shared evaluation dataset will definitely make the followup work easier. Thanks!

Me too！thanks.


Feat/kube create cluster

Update API calls for Kubernetes and create cluster

Add cluster creation
In order to be consistent with the new cluster creation, migrate api calls and refactor code to new standards (modal with states, lazyloading ...)

A new version of ovh-api-services has been released and published :tada:!
ref: https://github.com/ovh-ux/ovh-api-services/releases/tag/v6.17.0


Missing fields in biblatex export: Archive, Loc. in Archive

Support Log ID: RD2D7YL4-refs-euc
To reproduce:

create a Manuscript item, with the Archive and Loc. in Archive fields populated, in collection "testcollection"
export the item using the http API:

wget -O archivestest.bib "http://<IP_ADDRESS>:23119/better-bibtex/export/collection?/1/test/testcollection.biblatex"

the output does not include the two fields:

@unpublished{binkleyLetterLlewellynRaney1936,
  title = {Letter to {{M}}. {{Llewellyn Raney}}},
  author = {Binkley, Robert C.},
  date = {1936-04-23},
  annotation = {RCBFWB: Doc. 12393}
}

when exporting json, however, the two fields are present:

    {
        "archive": "Joint Committee on Materials for Research Collection, Library of Congress, Washington, D.C.",
        "archive_location": "Box 23, \"Micro-Copying of Newspaper Titles\"",
        "author": [
            {
                "family": "Binkley",
                "given": "Robert C."
            }
        ],
        "citation-key": "binkleyLetterLlewellynRaney1936",
        "id": "binkleyLetterLlewellynRaney1936",
        "issued": {
            "date-parts": [
                [
                    1936,
                    4,
                    23
                ]
            ]
        },
        "note": "RCBFWB: Doc. 12393",
        "title": "Letter to M. Llewellyn Raney",
        "type": "manuscript"
    },

This is important because the Archive and Loc. in Archives fields are necessary for citing archival documents. (See https://libguides.nus.edu.sg/c.php?g=145733&p=956617 )
Support log ID:

@pbinkley I'm not yet sure where I should put this information. I'm more likely to put it in biblatex though, I hope that is all the same to you. bibtex is almost guaranteed to not have anything standardized for this.

This is important because the Archive and Loc. in Archives fields are necessary for citing archival documents. (See https://libguides.nus.edu.sg/c.php?g=145733&p=956617)

That doesn't give guidance on what biblatex fields to put this information in however.
@njbart, I see this in the biblatex manual:

number: it may contain the number of a journaltitle in an article or review entry, the number of a title in a periodical entry, the volume/number of a book (or musical recording) in a series, the (generally numerical) specifier of the type in a report entry, the archive location (or database accession number) of a dataset entry, and the number of a national or international standard in a standard entry.

(emphasis mine)
does that make number the right place for this? Where should the archive itself be put?

My interest is just in getting this working with Pandoc and csl stylesheets, and I hadn't thought about how to map it to biblatex (which I don't know much about). It looks like this has come up before with no solution other than using json, so there may not be a way around the gap in biblatex. If there were a way to warn a user like me that these fields hadn't been exported, that would save trouble, but I don't see where that could happen within Better Bibtex's workflow. Thanks for looking at this, and please don't spend time on it on my account.

I was just thinking about a structural addition to BBT, but it's easy enough to add them in a postscript:
if (Translator.BetterTeX) {
  reference.add({ name: 'archive', value: item.archive })
  reference.add({ name: 'archivelocation', value: item.archiveLocation })

}

I have thought about detecting fields that are not exported, but the few experiments I did did not pan out. But a new approach just struck me, so I'll try to add them to the quality report.

My interest is just in getting this working with Pandoc and csl stylesheets

But if that's the case, why not export to Better CSL JSON? That has both those fields.

If there were a way to warn a user like me that these fields hadn't been exported, that would save trouble, but I don't see where that could happen within Better Bibtex's workflow.

If you turn on the quality report BBT will add information on data in the zotero item that is not used in the export.

I think I'm good. I'm using the BBT json (I just changed the /better-bibtex/ url I fetch from .biblatex to .json). I'll turn on the quality report and keep an eye on it, to learn more about how BBT works. Thanks for your attention to this.


Glitch in scrolling while using it with TableView sections.

We are using APParallaxHeader at multiple places in our app so far it was working great but with a one particular table view which has various sections it's not doing great it feels a glitch in scrolling sometimes and while pulling down the header a black background shows up in the background of header bottom part.

Does the TableView use a plain or grouped style? Plain style, with floating sections, will result in glitches. I have not found any way to work around this issue and it is something I haven't seen anyone successfully solving this issue in other apps.
See issue #3

it can be fixed by changing the zPosition of the parallax layer view.
A long time searching for this fix (thanks to https://github.com/maxep/MXParallaxHeader/issues/38)
self.tableView.parallaxView.layer.zPosition = 1;


handbrake: 1.2.2 -> 1.3.0

This update is important as handbrake 1.2.2 no longer builds with
nixpkgs due to an unrelated update to pango-1.44.x as described
here.
Fixes #73399

Motivation for this change
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nix-review --run "nix-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[ ] Fits CONTRIBUTING.md.

Notify maintainers
cc @

Thanks to @jtojnar for showing the way forward with this comment.

I've done things differently to possibly better insulate our changes to the upstream build.


Update Gomega to latest sha

In recent Go releases, go test is internally calling go vet and the
version of Gomega currently used in the CLI fails vetting on gbytes.Say
matchers that contain % characters.
This is the PR that fixes it in Gomega: https://github.com/onsi/gomega/pull/300
Signed-off-by: William Martin<EMAIL_ADDRESS>Co-authored-by: William Martin<EMAIL_ADDRESS>

Is this an issue when using Go 1.10.x as well ?

No, although the vetter has been executed since 1.10.x, only in 1.11 did it become stricter: https://golang.org/doc/go1.11#vet

@AartiKriplani @williammartin Thanks! We were just looking into upgrading to Go 1.11, so this comes at the perfect time :D


fix bug check nonexist authfile

For podman command(except login), if authfile does not exist returns error.
close #4328
Signed-off-by: Qi Wang<EMAIL_ADDRESS>

@TomSweeneyRedHat @rhatdan PTAL

/approve
Change LGTM, but CI is broken

Can't we just do the shared.GetAuthFile() in the options handling, so we check if the environment variable is set and then we don't need to change all this code?

this will fail if I don't have default  /run/user/1000/containers/auth.json, should we consider this situation that ? I think CI fails for this reason
podman search alpine
ERRO[0000] error checking authfile path /run/user/1000/containers/auth.json: stat /run/user/1000/containers/auth.json: no such file or directory

I would like to remove the /run/user... stuff from defaults and allow containers/image to handle it, especially if we move to Keyrings as the default, Then we can rely on C/I to specify the default localtion.

lint is not your friend @QiWang19

LGTM

LGTM
Thanks for sticking at it on this PR @QiWang19 !

and green test buttons if someone wants to LGTM it and merge.

and green test buttons if someone wants to LGTM it and merge.

merged this PR after buildah PR https://github.com/containers/buildah/pull/1967 got merged so I can vendor in?

@QiWang19 I'm a bit confused by your last comment.  Do you want to merge this after containers/buildah#1967 gets merged?  Then you want to vendor Buildah into Podman once that's in?

@TomSweeneyRedHat yes https://github.com/containers/libpod/pull/4337#discussion_r342794897 if I should add this utility function. That function will be used both in buildah and podman.

/lgtm


Use adaptive algorithm for determining if a user speaks

This is somewhat related to issue https://github.com/fulldecent/FDSoundActivatedRecorder/issues/20.
Idea:

save the last x microphone levels (e.g. for the last 30 seconds)
identify spikes: these would indicate that a user speaks
substract spikes from other saved levels in order identify valleys: these would indicate silence
use average of valleys as the threshold value for speaking
if the current microphone level is greater than the moving average, user is probably speaking

The advantage of such an algorithm is obvious: even if the surrounding circumstances change (e.g. the user leaves a building and is exposed to traffic noise), the recognition accuracy would still be high.

This project does real-time recording. But this issue proposes an approach to analyzing pre-recorded samples. Closing as out of scope.


Function to get WFS endpoint and read data into R from SB item

User will be able to point this function at an SB item that has a WFS service attached and get the data loading into an SP dataframe.
Example of an SB item with
https://www.sciencebase.gov/catalog/item/55e372b9e4b05561fa208212
Might be able to do it with this rOpenGov package, though it is not on CRAN and it follows an object inheritance model.
Some rough code I worked out to do it using gdalUtils, which is on CRAN, but may be a pain because it relies on gdal installed externally. Worked fairly well on Windows, may have issues on other platforms.
item_get_wfs = function(sb_id){
	wfs_url = item_get_wfs(sb_id)

	layer_info = ogrinfo(paste0('WFS:', wfs_url))

	#from this layer info, we need to extract layer name
	layer_raw = str_match_all(layer_info, '[[:digit:]]+: (sb:[[:alpha:]_]+) \\([Polygon|Multi Polygon]+\\)')

	layer_names = sapply(layer_raw, function(x)x[2])

	layer_names = layer_names[!is.na(layer_names) & !layer_names %in% c('sb:boundingBox', 'sb:footprint')]
	if(length(layer_names) > 1){
		stop('SB Item WFS has > 1 layer. item_download_sp currently cannot handle more than one layer')
	}

	fname = tempfile(fileext = '.shp')

	ogr2ogr(wfs_url, fname, layer_names)

	layer_sp <- readOGR(fname, substr(basename(fname), 1, nchar(basename(fname))-4), stringsAsFactors=FALSE)
	return(layer_sp)

}

read data into R

Into what object?  a spatial object following sp classes?
When WFS is avail. for an item is there also other geospatial formats avail.? e.g., geojson would be easier to quickly visualize if that's a use case you're shooting for  - Thought i imagine most people are familiar with sp and friends

Yeah, I was thinking an object along the sp line.

When WFS is avail. for an item is there also other geospatial formats avail.?
Well, I'm fairly certain we won't know the file format that was used to create the service itself (the raw file attached to the item), but the WFS could be used to grab JSON instead of a shapefile.

Here's a quick example
https://www.sciencebase.gov/catalogMaps/mapping/ows/55e372b9e4b05561fa208212?service=wfs&request=getFeature&version=1.0.0&outputformat=application/json&typeName=sb:Iowa_DU_Living_Lakes
The hardest part is getting out the typeName to grab, which can be parsed from the getCapabilities response
https://www.sciencebase.gov/catalogMaps/mapping/ows/55e372b9e4b05561fa208212?service=wfs&request=getcapabilities&version=1.0.0
Ultimately, that's what my use of ogrinfo is doing, grabbing that name. Then we could fairly easily toss together the query ourselves to grab geojson.


the inquiry of downloading json file

Hi I'm Cheol-Ho Cho, PhD candidate at Sungkyunkwan University in Korea
I want to download the label and caption JSON file of CIRR.
However, there occur some error from the command below
mkdir data
cd data

git clone -b cirr_dataset git@github.com:Cuberick-Orion/CIRR.git cirr

How can I obtain the annotation file...?
the error message is below
root@b8d0f0e4cfd7:/project/Research/lincir/data# git clone -b cirr_dataset git@github.com:Cuberick-Orion/CIRR.git cirr
Cloning into 'cirr'...
<EMAIL_ADDRESS>Permission denied (publickey).
fatal: Could not read from remote repository.

Please make sure you have the correct access rights
and the repository exists.

Hi,
I think this is more likely a git credential issue on your end. Could you check if you are able to clone any (arbitrary) other public repository?

I solved the problem by the command below
git clone -b cirr_dataset https://github.com/Cuberick-Orion/CIRR.git cirr

This is using HTTPS instead of SSH
Thank you for kind reply 😄


The numba_dpex==0.19.0 build on conda channel dppy/label/dev is built with a commit posterior to 0.19.0

Several differences between 0.19.0 tag on the repository and the build on the conda channel dppy/label/dev:

CLK_LOCAL_MEM_FENCE has been renamed LOCAL_MEM_FENCE
the behavior of caching has changed again (seems there's no caching at all anymore - even a kernel call with a pyfunc that has the same id(func) and the same signature seems to not cache anymore ?)

Would it be possible to make it so the default numba_dpex build resolved by conda is a built from the 0.19.0 tag in the repository ?

I have the feeling that this is expected. The package found in dppy/label/dev reflect the current state of the main branch of the git repo, not the git tag 0.19.0.
The build number returned by "mamba list numba_dpex" has a _21 suffix which matches the version found in the source tree when doing:
cd numba_dpex
python
>>> import _version
>>> _version.get_versions()['version']
'0.19.0+21.ga541db59'

If you want to install the real 0.19.0 version, do not use the dppy/label/dev channel but the intel channel instead.

But to avoid any confusion, it would be best to bump the version number of main to 0.20.0 in anticipation of the next release.

I see. I'll just pin the build then. (I prefer continuing using numba-dpex from dppy/label/dev channel rather than intel since we're still all moving fast - however, it would be nice if we can start thinking of stabilizing the interfaces in the perspective of a release schedule)

Still I think it would be good practice to change the version number of the main development branch to target the next release version (with the .dev) suffix to avoid confusion.


Contributing Guide

I guess we are working on this again so I guess we need to lay out how to contribute.

Every PR must be reviewed by one other person at the least before getting merged.
Proper tags must be used for organization + communication reasons.
Travis must pass before merging (after I fix it).
If you want to tackle an issue assign yourself or if you want to suggest someone else assign them.

Anything else?
Tagging @TheMonsterFromTheDeep @Joker314 @Jonathan50

Put it in CONTRIBUTING.md, also everybody but @joker314 is watching the repo

https://github.com/ilovecode1/Pyfancy-2/pull/21

What about me?

I'm a contributor, correct?                                                                                ^^^^^^^^^^

@bjskistad Oh sorry I forgot...;P


change(tests): add acceptance test for getblocktemplate method in CI

Motivation
Needed for CI to test the getblocktemplate method with the sync to tip and contextual validation checks.
Closes #5652
Solution

Add a miner_address to the config when the getblocktemplate-rpcs feature is enabled
Sync to the tip
Call getblocktemplate RPC method and assert that the request was successful
Add new test to CI

Review
Anyone can review.
Reviewer Checklist

[x] Will the PR name make sense to users?

[ ] Does it need extra CHANGELOG info? (new features, breaking changes, large changes)

[x] Are the PR labels correct?
[x] Does the code do what the ticket and PR says?
[ ] How do you know it works? Does it have tests?

@mergifyio update


Live Trainer

I was able to get the trainer working on Aki - How can I use this on multiplayer with other players instead of solo only?

https://github.com/sailro/EscapeFromTarkov-Trainer/issues/167
Its pinned. Check next time issues list.

I was able to get the trainer working on Aki - How can I use this on multiplayer with other players instead of solo only?

How did you get the trainer working, If you dont mind me asking?

In the README.MD file:
master branch can build against EFT <IP_ADDRESS>49 (tested with spt-aki Version 2.3.1).
Again I'm waiting for the next spt-aki, before working on the upgrade (given this time it will require a bit of work, they changed a lot of stuff impacting me, like console commands).


ci: fix upload path

This fixes the following error (https://github.com/pkgjs/statusboard/actions/runs/11682497163/job/32529743694):
  tar: github-pages: Cannot open: No such file or directory
  tar: Error is not recoverable: exiting now
  Error: Process completed with exit code 2.

Also, remember to give permissions to the main branch for deployment on GitHub Pages

Can I be a maintainer for this project?, I’ve submitted the request in https://github.com/nodejs/package-maintenance/pull/617


Optional peer dependencies are incorrectly listed in package.json

Currently react-dom and react-native are listed as optional peer dependencies of react-redux, but they are only listed in peerDependenciesMeta and not in peerDependencies. Looking at the RFC for optional peer dependencies in Yarn v2, I'm pretty sure the correct way is to list them in both fields:
https://github.com/yarnpkg/rfcs/pull/105#issuecomment-438474104
Consistent with this, I'm seeing yarn v2 (with pnp) complaining that A package is trying to access another package without the second one being listed as a dependency of the first one, even when react-dom is a dep of the react-redux's direct ancestor.
Happy to provide a PR and\or a repro if you'd like!
redux: 4.0.5
react-redux: 7.2.0
react-dom: 16.12.0

Yep, I'd fully expect PnP to whine about that.
Also see these previous discussions:

#1261
#1282
#1371
#1366
#1424
#1425


fix(bashScript): download correct vault zip for arm64 processor

install_vault.sh just download and unzip binary vault for amd64, which cannot be executed
on arm64 architecture processors. Add architecture checking in bash script to support this.
Signed-off-by: maaaace<EMAIL_ADDRESS>

@maaaace Please sign the Contributor License Agreement!
Click here to manually synchronize the status of this Pull Request.
See the FAQ for frequently asked questions.

@maaaace Thank you for signing the Contributor License Agreement!

Thanks a lot. That's merged and backported, also to Spring Vault now.


make Package.Path() return platform independent package full path

@bwplotka or @aimuz can you help review?

Thx for merging!


chore: add API changes guards

Overview
Description
Help us prevent accidental API changes to core

Can't believe how simple that is 🤩


Update ansible galaxy version

I just installed the version from ansible galaxy and I wondered why it is not installing my java packages... It contains this line:
when: ansible_architecture == "armv7l"
Seems like this is an old version? I can install from git in the meantime but maybe you can release a new version?

Hi, this was a specific workaround to install on raspberry pi devices, I'm happy to apply any changes required if you can provide details on your specific use case

@teddyphreak, the version on galaxy is missing the apt-transport-https package and is failing  for me on a new Debian install. If the galaxy version was updated to what is in the repo it would work.

Exactly that, the git version works for me, no changes required. I only need an update to the galaxy version :)

Galaxy tag 2.0.1 will be published as part of https://travis-ci.org/nephelaiio/ansible-role-unifi-controller/builds/602155420


escape newlines for argo codebundle

patches up some newlines that break the markdown rendering in runwhen-local

Should fix https://github.com/runwhen-contrib/runwhen-local/issues/239


changed hml alert for alert component and added some minor errorhandling

Also the listView has the IdentitySearch Partial and the error handling should be done there as well.


odo list -o json should return json with empty list if no component present

[kind/bug]
What versions of software are you using?

Operating System: macOS
Output of odo version:

odo v0.0.20 (bd3e74a4)
Server: https://<IP_ADDRESS>:8443
Kubernetes: v1.11.0+d4cacc0

How did you run odo exactly?
odo list --app <app> --project <proj> -o json
Actual behaviour
Currently it prints the text as mentioned below:
✗  There are no components deployed.
Expected behaviour
If there are no components odo list --app <app> --project <proj> -o json should return an empty list.
{   "kind": "List",   "apiVersion": "odo.openshift.io/v1alpha1",   "metadata": {},   "items": [] }
Any logs, error output, etc?

/bug
/priority medium

I am not able to reproduce this @mohitsuman
[gramnani@girish openshift]$ odo list --app e2e-zful --project myproject -o json
{"kind":"List","apiVersion":"odo.openshift.io/v1alpha1","metadata":{},"items":[]}
[gramnani@girish openshift]$ odo version
odo v0.0.20 (a288bb99)

Server: https://<IP_ADDRESS>:8443
Kubernetes: v1.11.0+d4cacc0

can you share your steps to reproduce this?

@girishramnani Below is the mentioned steps with screenshot.

Create application from vscode UI.
Run odo command from vsode terminal

odo list --app throne --project myproject -o json

The output is string instead of json.

I can see that the odo version output for 0.0.20 has a different commit hash for me.

This is duplicate and was fixed in master https://github.com/openshift/odo/issues/1326.

@girishramnani Did you try this on macOS build ? It works on windows one for some reason.

@mohitsuman , can you test it against master again ?

Closing this since issue is resolved
$ odo list -o json
{"kind":"List","apiVersion":"odo.openshift.io/v1alpha1","metadata":{},"items":[]}