Implements client API for export and download of artifacts

RepositoryRestService

Export and Download functions that allow for downloading of an
Exportable artefact from the server to the client

Uses ngFileSaver for converting a json blob into a saveable file that
triggers the browser SaveAs dialog

Added to vdbList for test/demo purposes

https://github.com/Teiid-Designer/komodo/pull/400 is a pre-requisite


add the Navitia API

The Navitia API is an open API built around transport data.
you can query for journeys, isochrone, schedules, realtime data, ...

Thanks!


[eas-cli] graphql codegen

what
Graphql codegen for schema types:

declared in www
queries and fragments declared in eas-cli

how
Setup is pretty much the same as what juwan configured in the website, minus the apollo plugins.
step by step
In packages/eas-cli, run yarn generate-graphql-code. This will generate agraphql/generated.tsx file, all the types from the www schema, along with the queries + fragments declared in eas-cli

@quinlanj I've just noticed this. Do we want generated.tsx to have the .tsx extension? I guess x doesn't make sense for node.

Bump. Dominik is right, trying to import the generated.tsx causes TS error:
Module '../generated' was resolved to 'packages/eas-cli/src/graphql/generated.tsx', but '--jsx' is not set.
ts(6142)


RVV: some rvv instructions' dest register is also considered as a src register.

Describe the bug
CPU: MinorCPU
ISA: RISCV (vector extension)
vlmul : 2
0x10200 | m5op (vnop)
0x10204 | vfmul.vv   v2, v0, v0
0x10208 | vfmul.vv   v2, v0, v0
0x1020c | vfmul.vv   v2, v0, v0
0x10210 | vfmul.vv   v2, v0, v0
0x10214 | vfmul.vv   v2, v0, v0
0x10218 | vfmul.vv   v2, v0, v0
0x1021c | vfmul.vv   v2, v0, v0
0x10220 | vfmul.vv   v2, v0, v0
0x10224 | vfmul.vv   v2, v0, v0
0x10228 | vfmul.vv   v2, v0, v0
0x1022c | vfmul.vv   v2, v0, v0
0x10230 | vfmul.vv   v2, v0, v0
0x10234 | vfmul.vv   v2, v0, v0
0x10238 | vfmul.vv   v2, v0, v0
0x1023c | vfmul.vv   v2, v0, v0
0x10240 | m5op   (vnop)
In this case, there should not be any src reg. dependencies, but there was some dependency problem on execute stage in RiscvMinorCPU.

But it acts like there are dependencies between each of the instructions.
As i debugged, the destination register 'v2' is also considered as a source register.
0x10200 | m5op (vnop)
0x10204 | vfmul.vv   v2, v0, v0
0x10208 | vfmul.vv   v4, v0, v0
0x1020c | vfmul.vv   v6, v0, v0
0x10210 | vfmul.vv   v8, v0, v0
0x10214 | vfmul.vv   v10, v0, v0
0x10218 | vfmul.vv   v12, v0, v0
0x1021c | vfmul.vv   v14, v0, v0
0x10220 | vfmul.vv   v16, v0, v0
0x10224 | vfmul.vv   v18, v0, v0
0x10228 | vfmul.vv   v20, v0, v0
0x1022c | vfmul.vv   v22, v0, v0
0x10230 | vfmul.vv   v24, v0, v0
0x10234 | vfmul.vv   v26, v0, v0
0x10238 | vfmul.vv   v28, v0, v0
0x1023c | vfmul.vv   v30, v0, v0
0x10240 | m5op   (vnop)
To make sure my opinion, i tried new assembly codes, that each vfmul.vv has different destination register.

I believe there should not be any difference on cycles between these two cases.
Affects version
23.1.0 (the latest release version)
gem5 Modifications
NOP
To Reproduce
Steps to reproduce the behavior. Please assume starting from a clean repository:

Compile gem5 with command ...
scons build/ALL/gem5.debug -j $(nrpoc)

Compile c++ code below with "riscv64-unknown-elf-g++"

void main() {
    asm volatile (
        "vsetvli	a4, a0, e32, m2, ta, ma\n"
        ".insn	4, 0x8000007b\n"
        "vfmul.vv v2, v0, v0\n"
        "vfmul.vv v4, v0, v0\n"
        "vfmul.vv v6, v0, v0\n"
        "vfmul.vv v8, v0, v0\n"
        "vfmul.vv v10, v0, v0\n"
        "vfmul.vv v12, v0, v0\n"
        "vfmul.vv v14, v0, v0\n"
        "vfmul.vv v16, v0, v0\n"
        "vfmul.vv v18, v0, v0\n"
        "vfmul.vv v20, v0, v0\n"
        "vfmul.vv v22, v0, v0\n"
        "vfmul.vv v24, v0, v0\n"
        "vfmul.vv v26, v0, v0\n"
        "vfmul.vv v28, v0, v0\n"
        "vfmul.vv v30, v0, v0\n"
        ".insn	4, 0x8200007b\n"
    );
}

Execute the simulation with...

`./build/ALL/gem5.debug --debug-flags=Fetch,Decode,MinorExecute script.py vfmul_vv_example_code --cpu RiscvMinorCPU
Terminal Output
With MinorExecute Debug Flags, you can find an dependency issue due to the cycles.
At Scoreboard::canInstIssue (src/cpu/minor/scoreboard.cc : 208), I could find that dest reg is also considered as a src register.
Host Operating System
Ubuntu 22.04
Host ISA
RISC-V Vector Extension

Right now many vector instructions will also use the destination register as a source to implement the tail/mask undisturbed policy. Currently it's the default even if you set agnostic behavior for both, but #997 should fix this.

Thx for your explanation.
So, there isnt any option to change that policy without modification right now, am I right?

No. The mentioned PR adds in this option, without it gem5 will always assume an undisturbed policy for both tail and mask, even if you specify otherwise with ta ma in your vset{i}vl{i} instruction.

I am transitioning this into a discussion. If I am mistaken and there is a real bug that needs to be fixed, please let me know. Thanks.


Golang example outdated.

Summary
The example https://github.com/argoproj/argo/blob/master/examples/example-golang/main.go doesn't work it throws
 Error: workflows must use workflowTemplateRef to be executed when the controller is in reference mode

Argo version is v2.11.0
I have the example modified to work where I have created WorkflowTemplate and submitted a workflow referencing the WorkflowTemplate, should we update the same example or add as a different example?

Whoever set up your Argo controller turned on a setting to only allow workflows that use workflowTemplateRef to run. This isn't an issue with the example itself, but instead your controller is not configured to work with that example.

See: https://github.com/argoproj/argo/blob/master/docs/workflow-requirements.md

Thanks @simster7


Add OpenStreetMap layer on every maps

Like for Monitor map, could you add the OSM bitmap layer too for Analysis by network, Analysis by location and Route planner ?

The OSM layer is added to all maps.


Vulnerability roundup 84: uw-imap-2007f: 1 advisory

search, files

[ ] CVE-2018-19518 CVSSv3=7.5 (nixos-20.03)

Scanned versions: nixos-20.03: 82b5f87fcc7. May contain false positives.

See also: #55393, #70130

Possible solution: https://github.com/NixOS/nixpkgs/issues/70130#issuecomment-539267399

20.03 is Frozen and EOL.
As such, issue is closed.


[BUG] Cannot play more than one video at a time

Describe the bug
Having two separate controllers for two separate youtube videos loads correctly but cannot play more than one at a time. Playing another video stops playback of the one currently playing.
To Reproduce
Create two separate controllers and click 'play' on the second when first is playing.
Expected behavior
Expected to run two separate videos at the same time
Screenshots
n/a
Technical Details:

Device: Android
OS: Android
Version 9

I guess, this cannot be fixed.


Custom representation for list command

Replace the generic array print output to improve visibility for a big amount of symlinks.

Closed by https://github.com/Serkonda/symlinker/commit/28d27da16528be49bfc71d0583ed5dc963b71514


@broskoski => Blog post about a funny bug and using Ruby OCR

Decided to write another blog post. /shrug

AMAAZINNNNNNG

:clap: :clap: :clap:

10/10 would read again.

Thanks for the read thru! Will address and make some edits.

Amazing!!  Also, to give credit where credit is due, it's our editorial
team who writes artist bios. I wouldn't necessarily mention metadata here,
since, without additional context, it's vague. The genome team just noticed
this because we regularly check the artist's page and swap out
automatically assigned artist images for curated ones for any artist who
appears on that page. I don't think you need to give that context
necessarily. A more condensed way to say it would just be that the
Artsy.net team noticed these weird images showing up on Artsy.net/artists
On Nov 12, 2015 7:49 PM, "mzikherman"<EMAIL_ADDRESS>wrote:

Thanks for the read thru! Will address and make some edits.
—
Reply to this email directly or view it on GitHub
https://github.com/artsy/artsy.github.io/pull/177#issuecomment-156282897
.

Got it @jessicabackus , cool to know thanks!

Thanks for the read-thru everybody!


”Sânzieni”, ”Cașinu Mic”, ”Petriceni”, ”Valea Seacă” are listed in the drop-down menu

Description:
When user writes ”Sânzieni”, ”Cașinu Mic”, ”Petriceni”, ”Valea Seacă” the locations appear in the drop-down menu next to the comune and the county witch is a part according to the law.
Precondition:
The website is up an running.

Step 1
Write in the search bar "Sânzieni"

Expected results
The location appears in the drop-down menu as "Sat Sânzieni, COVASNA (Sânzieni)".

Step 2
Press "x" button.

Expected results
The location was deleted from the search bar.

Step 3
Write in the search bar "Cașinu Mic"

Expected results
The location appears in the drop-down menu as "Sat Cașinu Mic, COVASNA (Sânzieni)".

Step 4
Press "x" button.

Expected results
The location was deleted from the search bar.

Step 5
Write in the search bar "Petriceni"

Expected results
The location appears in the drop-down menu as "Sat Petriceni, COVASNA (Sânzieni)".

Step 6
Press "x" button.

Expected results
The location was deleted from the search bar.

Step 7
Write in the search bar "Valea Seacă"

Expected results
The location appears in the drop-down menu as "Sat Valea Seacă, COVASNA (Sânzieni)".


[BUG] Elastic 7.10 with LTR Plugin: Excessive Increase in P95 Latency When Running Multiple A/B Test Variants

Describe the bug
When running A/B tests using Elastic 7.10 with the LTR plugin, I encounter a significant increase in P95 latency as the number of variants in the test increases. With 5 different but slightly varied queries and corresponding models that share the same feature set, executing 2 variants in interleaved calls at 100 RPS (Requests Per Second) maintains a P95 latency of around 400ms. However, when executing all 5 variants together under the same conditions, the P95 latency escalates to 2 seconds.
Related component
Plugins
To Reproduce
Set up Elastic 7.10 with the LTR plugin.
Configure 5 variants with slightly different queries and models, ensuring all models use the same feature set.
Run a test with any 2 of these variants in interleaved calls at 100 RPS. Observe the P95 latency.
Run a test with all 5 variants together at 100 RPS in interleaved calls. Observe the P95 latency.
Expected behavior
The expectation is that increasing the number of variants from 2 to 5 should not drastically increase the P95 latency, especially from 400ms to 2 seconds. A slight increase in latency might be anticipated due to the higher computational demand, but the scale of the increase observed is unexpected and indicates a potential performance issue.
Additional Details
Elastic 7.10 with LTR plugin 1.5.5-es7.10.2 https://github.com/o19s/elasticsearch-learning-to-rank

@wli-chwy Elasticsearch is https://github.com/elastic/elasticsearch, please open issues related to that product there.
OpenSearch has a fork of LTR, see https://github.com/opensearch-project/opensearch-learning-to-rank-base. This may also be of interest.


Javascript function with service bus trigger delivering byte message

Hi, we have a case when we want to process a byte array message within javascript function. The handler code though receives the message only as a string, ie. even when the message is a byte array the call to typeof message returns string.
We tried to convert that string back to byte array, but upon investigating we've discovered it contains several UTF-8 replacement characters ie. 0xEF 0xBF 0xBD rendering our data lossy. I haven't found any docs on how to switch the implementation to receive a Uint8Array or any structure supporting raw byte message.
Is there any option that I can handle my use case?

Hi if you're using model v3, you can set "dataType": "binary" in your function.json file. Here's an example:
{
  "bindings": [
    {
      "name": "mySbMsg",
      "type": "serviceBusTrigger",
      "direction": "in",
      "queueName": "myinputqueue",
      "connection": "SERVICEBUS_APPSETTING",
      "dataType": "binary"
    }
  ]
}

If you're using model v4, that's not supported yet. Tracked by https://github.com/Azure/azure-functions-nodejs-library/issues/72

Thanks, will track the other issue then.


CMake include path issue

Once again thank you for putting this together, and for reacting to the issues/PRs so quickly.
Issue
When using this library through
FetchContent_Declare(ByteTrackCpp
  GIT_REPOSITORY  https://github.com/Vertical-Beach/ByteTrack-cpp.git
  GIT_TAG         main
  GIT_SHALLOW     ON)
FetchContent_MakeAvailable(ByteTrackCpp)
# ...
target_link_libraries(my_lib bytetrack)

in my project, the include paths needed for the bytetrack library are not forwarded.
Checking a bit further,
get_target_property(bytetrack_INCLUDE_DIRS bytetrack INTERFACE_INCLUDE_DIRECTORIES)
message(STATUS "ByteTrack include dirs: ${bytetrack_INCLUDE_DIRS}")

shows that INTERFACE_INCLUDE_DIRECTORIES are not set.
I will open another small PR fixing this once the current one is merged!

Thanks! No problem, I have merged it.

I made a mistake on the issue to close.

Thank you for getting back to me =)
I think this issue is fixed with PR #10!
As mentioned in the PR, I have since made a host of other changes, if you are interested I can post PRs for those.


IA 194 gatling setup

This all looks reasonable to me, but I struggled to get it set up locally for testing. I can approve it if you like, or alternatively perhaps you could walk me through getting it set up.

@dag-yoppworks I can help walk you through setup but I first have to change things to run scylla in docker separately and somehow get containers in k8s to talk to the local container. Try walking through the steps once again once I have that part figured out


Fix Azure AD Graph API Directory Schema Extensions link reference

The current one is no longer available

@WilderPereira : Thanks for your contribution! The author, @davidmu1, has been notified to review your proposed change.

#sign-off


Charged Arrow Texture for Crossbows

Charged arrows loaded into a crossbow have the same texture as vanilla arrows. A different look, similar to how fireworks look different when loaded in a crossbow, would be a nice addition.

Probably not doable. Compare charged arrows to spectral arrows, not fireworks. Nothing in the vanilla model system is likely to let me do that.


Add a warning message when a user uses daily data and schedules intraday events during a backtest

Expected Behavior
Add a warning message when a user uses daily data and schedules intraday events during a backtest.
Actual Behavior
A scheduled intraday event during backtest results, while using daily data, does not produce a warning message, which can result in no available data for added securities at the time of the scheduled event.
Potential Solution
Add a warning message when the data resolution used for a scheduled event is higher than for user data.
Reproducing the Problem
self.UniverseSettings.Resolution = Resolution.Daily
self.spy = self.AddEquity("SPY", Resolution.Daily)
self.Schedule.On(self.DateRules.EveryDay("SPY"), self.TimeRules.AfterMarketOpen("SPY", 60), Action(self.Market))

System Information

Checklist

[x] I have completely filled out this template
[x] I have confirmed that this issue exists on the current master branch
[x] I have confirmed that this is not a duplicate issue by searching issues

[x] I have provided detailed steps to reproduce the issue

Duplicate of https://github.com/QuantConnect/Lean/issues/3687


Use Python 3.13 as the default Python version for new apps

Previously if a new app did not specify a Python version (e.g. via a .python-version file), then the buildpack would default to the latest Python 3.12 release.
Now the buildpack will use the latest Python 3.13 release.
This does not affect:

apps that specify an explicit Python version
existing apps that have already had a build using the previous default version (since that version is remembered from one build to the next, via the "version pinning" / "sticky versions" feature).

Use-cases involving new apps that aren't compatible with Python 3.13 will now need to specify Python 3.12 explicitly:
https://devcenter.heroku.com/articles/python-support#specify-a-python-version
However most apps should be compatible, since Python 3.13 was released a couple of months ago (2024-10-07), does not contain significant breaking changes over Python 3.12, and has been happily used by the python-getting-started project since 2024-10-10.
See:
https://docs.python.org/3.13/whatsnew/3.13.html
Note: When using Python 3.13, the buildpack does not install setuptools, wheel or the sqlite headers/CLI, hence those diffs to the test fixtures.
GUS-W-14846972.

Default version mentions updated at:
https://devcenter.heroku.com/articles/python-support#default-python-version-for-new-apps
https://devcenter.heroku.com/articles/python-runtimes

https://devcenter.heroku.com/changelog-items/3080


Stop preload action

Hi,
I would like to know how can I stop a preload action ?

Based on this answer, there is no standard way to abort a loading (HTML) image.
It mentions that if the src is set to empty string it will abort on some browsers.
I suggest you first try doing that, you get the HTML image element on callbacks as data.image. If it works please report and it might get added here if it works on (at least) several browsers

For me it doesn't work and I can't do what I want.
Why did you choose to preload images using <img> and not an XHR in JQuery ?
Something like this :
        $.ajax({
            url: 'http://www.exemple.com/image.jpg',
            beforeSend: function (xhr) {
                // save this XHR request
            }
        });

Cross domain support

Ok thank you, finally I generate a ID for each instance of $.preload which allow me to prevent action when it's another preloading


Add constrained scheduler benchmarks

This benchmarks scheduling with constraints, where only 1/3 of the nodes
are eligible to run the tasks.
Under the current implementation, this converges towards the worst-case
linear behavior, because the nodes that meet the constraints end up at
the end of the heap, and findMin has to scan much of the heap to find
them.

[Current coverage][cc-pull] is 53.91%

Merging [#1028][cc-pull] into [master][cc-base-branch] will increase coverage by 0.22%

@@             master      #1028   diff @@
==========================================
  Files            75         75
  Lines         11671      11642    -29
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
+ Hits           6266       6277    +11
+ Misses         4501       4474    -27
+ Partials        904        891    -13

[][cc-pull]

Powered by Codecov. Last updated by [5007feb...2482a83][cc-compare]
[cc-base-branch]: https://codecov.io/gh/docker/swarmkit/branch/master?src=pr
[cc-compare]: https://codecov.io/gh/docker/swarmkit/compare/5007febc69c4c44b3e57684902f976ddbfb3bb64...2482a83e31fa181f84ca1e58c8ae672d6eadbc5d
[cc-pull]: https://codecov.io/gh/docker/swarmkit/pull/1028?src=pr

Updated, PTAL.

LGTM


Weird type issue

While generating the schema for a query message that returns Option<cw_utils::Duration>, ts-codegen fails with:
contracts/cw-vesting/CwVesting.client.ts:25:31 - error TS2552: Cannot find name 'NullableDuration'. Did you mean 'Nullable_Duration'?

25   vestDuration: () => Promise<NullableDuration>;
                                 ~~~~~~~~~~~~~~~~

contracts/cw-vesting/CwVesting.client.ts:81:36 - error TS2552: Cannot find name 'NullableDuration'. Did you mean 'Nullable_Duration'?

81   vestDuration = async (): Promise<NullableDuration> => {
                                      ~~~~~~~~~~~~~~~~

It appears that it generates a type Nullable_Duration that is correct, and the uses a different one NullableDuration as the query return value. This CI job has a branch on which this fails. You can reproduce the issue by checking out that branch and running ts-codegen with just gen.

thanks @0xekez — can you provide the schema?


x/build: drop Go branch prefix from presubmit LUCI builders for the main Go repository

Currently the LUCI builders all have a Go branch prefix. This makes the configuration simpler, and it makes the behavior of x/ repo builders against x/ repo changes explicit in the builder name.
This distinction is also necessary for displaying the Go repository postsubmit builders in the LUCI UI in a sensible way. If we were to drop the prefix and send all builds from all branches to the same Go repo builders in postsubmit, then the LUCI dashboard would display the latest build on any branch as the top-level status for a builder. This would make the overview of each dashboard at https://ci.chromium.org/p/golang very confusing. The LUCI UI generally treats distinct builders as having distinct histories, and we need to capture that distinction.
However, there are a few downsides, specifically for LUCI builders for the main Go repository in presubmit.

When the branch prefix is present in a commit message (via Cq-Include-Trybots) and the commit is cherry-picked to a release branch, the person performing the cherry-picking needs to be careful to update the Go branch in the commit message. If they do not, they will run into a failure to start trybots.
Because the filtering of the buildbucket Gerrit plugin is not very granular (on a bucket level only), this means the "Choose Tryjobs" dialog contains lots of builders that don't make sense for a particular change. For example, a Go repo change for the main branch should never run go1.21-* builders, yet they appear in the dialog as an option.

Note that dropping the prefix for presubmit makes sense while it doesn't for postsubmit, because presubmit builders don't really have a coherent notion of a history anyway.
I spent some time outlining how we might achieve this. Here are the steps:

[x] Split out presubmit from the big config loop in main.star. (https://go.dev/cl/565420)
[ ] Split out the go project from the presubmit config loop from step (1).
[ ] Rework all the _version properties to be a map of Go branch names to versions.

Today, every builder will have exactly the same map, but builders that want to test against specific versions of some tool (node, clang, whatever) can still do so.

[ ] Allow "" and None as Go branch values throughout main.star.

Builder names simply omit the branch and properties must not depend on the branch name. (Caveat: I don't know yet how to enforce that.)

[ ] Allow "" as a valid go_branch property value in golangbuild (with an attempt to infer from the input change).

This will require some refactoring in golangbuild, because installTools will need to know the version to index into the map.

[ ] Rework the go project presubmit config loop to generate one builder per builder type, passing a None and/or "" Go branch name.

An alternative implementation would be to create the notion of a "proxy" builder whose only job consists of forwarding its invocation to a more specific build. This is doable, but the "proxy" build would likely need to stay live through the execution of the builder(s) it invokes, which burns an additional machine for no reason.
Though, this choice may have other benefits. For example, we could use it to create builders that represents sets of other builders, for greater ease-of-use during presubmit.

Thinking more about this, I think there's a slightly simpler way that is a bit closer to the alternative I mentioned, but fewer downsides:

Generate the per-branch builders as well as the not-per-branch builders.
Have golangbuild fetch the properties for the per-branch builders when the Go branch is not specified, but once it infers it.


Dependabot can not automatically create PRs for alerts generated when pnpm vulnerability support was rolled out

Is there an existing issue for this?

[X] I have searched the existing issues

Package ecosystem
npm
Package manager version
pnpm 7
Language version
Node 18.17
Manifest location and content before the Dependabot update
No response
dependabot.yml content
version: 2
registries:
  npm-github:
    type: npm-registry
    url: https://npm.pkg.github.com
    token: ${{secrets.NPM_READ_TOKEN}}
    replaces-base: true
updates:
  # root npm package.json
  - package-ecosystem: 'npm'
    directory: '/project-name'
    schedule:
      interval: 'daily'
    allow:
      - dependency-name: 'moment-timezone'
    open-pull-requests-limit: 0

Updated dependency
No response
What you expected to see, versus what you actually saw
My team's project was managed with yarn and we switched to pnpm mid-July. We lost all of our security alerts when we did this as dependabot didn't support pnpm yet. On July 31st, (I think this is when dependabot rolled out support for pnpm), the alerts were regenerated, but no PRs were opened. Since then, dependabot only automatically creates PRs for newly added dependencies, i.e. new alerts.
Is there a way to "refresh" the alerts for dependabot such that it will try to create PRs? We have around 2000 open alerts so checking each alert manually and clicking the "open PR" button is not an ideal workaround.
Native package manager behavior
No response
Images of the diff or a link to the PR, issue, or logs
No response
Smallest manifest that reproduces the issue
No response

Hei @gavacq!
I asked around internally and... this should've worked out of the box.
I assume this is happening in a private repo? If that's the case, please open a support ticket so that the proper team can have a look at the details of what happened. Feel free to link to this issue.
The logic for triggering the security updates does not live in this repo (it's internal to GitHub). Here there's only the update logic itself. So whatever actions need to be taken won't affect this repo. Hence, I'll close this.
I hope you get this sorted out!


install fails

I've tried the release and the latest commit, they both fail with the same errors:
C:\Users\scuba\Downloads\citro3d-1.3.0>make install
attribs.c
arm-none-eabi-gcc -MMD -MP -MF /c/Users/scuba/Downloads/citro3d-1.3.0/release/attribs.d -g -Wall -Werror -mword-relocations -ffunction-sections -fdata-sections -march=armv6k -mtune=mpcore -mfloat-abi=hard -mtp=soft -DNDEBUG=1 -O2 -fomit-frame-pointer -I/c/Users/scuba/Downloads/citro3d-1.3.0/include -I/c/devkitPro/libctru/include -I. -DARM11 -D_3DS -DCITRO3D_BUILD -c /c/Users/scuba/Downloads/citro3d-1.3.0/source/attribs.c -o attribs.o
In file included from c:/Users/scuba/Downloads/citro3d-1.3.0/source/internal.h:8:0,
from c:/Users/scuba/Downloads/citro3d-1.3.0/source/attribs.c:1:
c:/Users/scuba/Downloads/citro3d-1.3.0/include/c3d/fog.h:18:21: error: unknown type name 'GPU_FOGMODE'
void C3D_FogGasMode(GPU_FOGMODE fogMode, GPU_GASMODE gasMode, bool zFlip);
^~~~~~~~~~~
c:/Users/scuba/Downloads/citro3d-1.3.0/include/c3d/fog.h:18:42: error: unknown type name 'GPU_GASMODE'
void C3D_FogGasMode(GPU_FOGMODE fogMode, GPU_GASMODE gasMode, bool zFlip);
^~~~~~~~~~~
In file included from c:/Users/scuba/Downloads/citro3d-1.3.0/source/attribs.c:1:0:
c:/Users/scuba/Downloads/citro3d-1.3.0/source/internal.h:33:2: error: unknown type name 'gxCmdQueue_s'
gxCmdQueue_s gxQueue;
^~~~~~~~~~~~
make[1]: *** [attribs.o] Error 1
make: *** [lib/libcitro3d.a] Error 2

Upgrade libctru.


[UNDERTOW-2116] ServletOutputStreamImpl incorrectly sets Content-Length to 0

Issue: https://issues.redhat.com/browse/UNDERTOW-2116
Main modifications:

Now the ServletOutputStreamImpl only resets to 0 if it's not a HEAD method.
I duplicated the same behavior in the two methods that manage this (close and closeAsync).
In order to fix the HEAD too, methods sendError and sendRedirect in HttpServletResponseImpl clean any possible Content-Length header added before by the app.
Tests added.

This PR is for the maintenance branch 2.2.x.
The same PR will be submitted to master as soon as https://github.com/undertow-io/undertow/pull/1344 is merged.
@fl4via Please review this in order to fix JBEAP-23796 (blocker now) when you have time.

There was a little mistake. Adding more tests to cover that too.

since this was the first PR for this Jira, I'm merging it, even though contributors can keep in mind that now fixes are backported to 2.2.x often and there is no need for PRs for 2.2.x


Metadata.yaml SHA is a commit behind the latest template.tpl

Hi,
Thank you for submitting your template for a Community Template Gallery review. I noticed that the SHA in metadata.yaml[0] is a commit behind the latest version of template.tpl. If you want to use the latest version of template.tpl for the Template Gallery then you'll have to update that SHA[1].
Please let me know if you have any questions.
Thanks
Jon
[0] https://github.com/mbaersch/scoby-tag-server/blob/060c9e8595dc36d34a04dc1798277b7c9b17d30f/metadata.yaml#L5
[1] https://developers.google.com/tag-platform/tag-manager/templates/gallery#metadatayaml

Hi Jon,
thanks for letting me know! Just updated the SHA value.


Replace InitBenchmark with InitTest. Remove qps_test.cc

[trickle] No significant performance differences

[microbenchmarks] No significant performance differences


Fix dev deployment, compose deployment and update docs

Changes:

update readme and format according to https://commonmark.org/
build UI static files is not required to run the dev server
fix FQDN nginx image
fix docker socket mount to make it compatible with podman

@benthomasson  @ddonahue007 please review


Fix integer overflow when calculating memory allocation size

Allocating memory with a size controlled by an external user can result in integer overflow.
Also, we need to check return values of malloc/calloc for null.

There are more than 20 such patterns in the codebase. I will try to find and fix them all if this patch looks good to you.
Is there a better way to indicate memory allocation error for function GenImageColor(), other than returning an Image with the data field set to NULL?

@szsam I'm afraid I'm not applying this change for now, it will imply a big redesign of many raylib parts to validate all user inputs and allocation results.


enable interactive mode for mosaic facet

This will address https://github.com/VEuPathDB/web-eda/issues/1477. Tried to find the reason at other components such as Mosaic, facetedMosaicPlot component (at web-components), etc., but I realized it later that interactive prop was disabled for faceted cases. Thus simply removed it. Actually this happened for both Mosaic RxC as well as 2x2.
Here is an screenshot showing mouseover tooltip at full screen modal with the same example case at the ticket.

@chowington Thank you for your review and praise 😄


Assertion error and low MAP on bal/eval set

I am getting the assertion error while running your script to create hdf5 files. It occurs in float32_to_int16() conversion. Here is a simplified version.

def float32_to_int16(x):
    assert np.max(np.abs(x)) <= 1.
    return (x * 32767.).astype(np.int16)

aud, sr = librosa.core.load(wav_files[0], sr=32000, mono=True)
aud = float32_to_int16(aud)

print (np.max(np.abs(aud)))
>>> 1.0048816

Some of my audio files are out of range. If I comment out the assertion then everything works. Will it be correct to remove the assertion?

I am also getting a low MAP scores on balanced set and evaluation set by using your trained models.

The ResNet38
bal set :: 0.52
eval set :: 0.37

CNN10
bal set :: 0.48
eval set :: 0.32

Do you think the above issue has anything to do with it? I mean I prepare the data by commenting out the assertion.

Yes, you can remove the assertion. The result you got is correct. If trained on full dataset, it would be better.


Is issuer/prover relationship information appropriate within Presentation Exchange?

        // TODO: how do we say that the prover must have a certain relationship to
        // the credential subject (e.g., BE the one and only subject, but
        // also things like "be the secondary account holder" or be the
        // father on the birth certificate?

re: https://github.com/decentralized-identity/presentation-exchange/pull/18/files#diff-9308a2575ae14de31b25f4459ecfc604R100
            // TODO: we need a way to do more than specify an allow list.
            // We must also support "accredited by issuer X" and also
            // "certified by a particular governance framework" (follow the
            // 'issue-edu' example in the Sample Data Structure section of

re: https://github.com/decentralized-identity/presentation-exchange/pull/18/files#diff-9308a2575ae14de31b25f4459ecfc604R107
TODO: add examples, cc @dhh1128
Perhaps this is out of scope for now because these checks can be done downstream by the business logic with data that are further provided. But it's certainly useful for a wallet to know additional constraints around a field, even if it must piece that data together from disparate systems.

It's a big deal to me to be able to express this in a proof (presentation) request; pushing this into downstream business logic means we validate such things with something other than verifiable credential tech, which means we have to invent a new strong form of proof, do we not? Without such features, I think the spec is fatally flawed and becomes uninteresting to me.

So @dhh1128 I'd like to run a few specific use cases by you to see if I fully understand what you mean. I have some further questions and also a proposed implementation. Could you let me know if I got what you meant and if you have any of the answers? Thanks
Use cases
Ability to assert that prover has a certain relationship to the credential subject

Alice is the applicant to BigBank for a new line of credit, and wishes to present her verifiable credentials representing her state-issued identity (drivers license) and proof of address (utility bill). BigBank wants to tell Alice that her verifiable credentials must have her DID as the credentialSubject.id.
Thomas the Tank Engine wants to to cross a privately-owned bridge. The bridge tells Thomas that the verifiable credential he's presenting must have his DID as the credentialSubject.id to be properly authorized.
To get into the New York Prosecutors' Club, a Lawyer must prosecute at least one defendant in the City of New York. The Prosecturs' Club Bouncer demands evidence in the form of a verifiable credential representing a case participation, and further adds the constraint that credentialSubject.prosecutorId must match the prover's DID. However, credentialSubject.id can be for anything.

Ability to assert properties about a credential's issuer

For the New York Prosecutors' Club, the Bouncer now wants to confirm that the prover's VC was issued by an issuer who was granted the adjudicate-case privilege with respect to New York City's trust framework {"uri": "https://nyc.gov/tf/courts"}
Sarah is a patient wishes to verify her doctor's medical credentials prior to an important surgery. She wants to let the doctor's user agent know that the verifiable credential's issuer must hold the medical-license-issuer privilege with respect to the AVICENNA Directory for Medicine ({"uri": "https://www.wdoms.org/tf/medical-schools"}) or accredited-medical-school privilege in FAIMER World Directory of Medical Schools ({"uri": "www.faimer.org/tf/school-listing"}).

Questions/Issues

Can you link to or walk through some examples of how to verify properties around an issuer? Are trust frameworks and privilege the only such properties? Another one that comes to mind is DID method used. If we were to add capabilities to verify properties around an issuer, it should be able to cover most or all of the use cases we can imagine.
Presently, the Presentation Definition is only concerned with property-level extraction from whatever pile of VCs are thrown at it. If we want to verify things like issuers of a specific credential from which we derived Property X, not sure if there's a natural expression how the standard is currently. Just to confirm, this is what you want to be able to confirm, right?

Proposed Implementation
Here are aspects of an impl:

I think if we took your suggestion of splitting Presentation Definition into a static Presentation Definition and instance-based Presentation Request in #23, we could possibly include a simple way to specify property values that must be matched in the Presentation Request. For example, we could require a property to have its relative credentialSubject.id to match a specific DID, e.g. did:ethr:0xdeadbeefcafe. I feel that we should avoid using derived variables like $proverDID in the Presentation Definition for now.
We could consider syntax to add constraints to the issuer property, including those for specifying trust frameworks/privileges.

Yes, you've captured the spirit of my terse notes in far better detail. Thank you.
I would note that your first 3 examples all assume that the way to bind the credential to the prover is via a disclosed public DID value. I know this is generally assumed to be the way it works in VC circles, but it has never been the canonical way of doing the binding in ZKP circles. There, the binding has been viewed as a far more nuance-able characteristic. In a ZKP credential, you can bind a credential to a prover by exposing a public DID value (which the prover demonstrates they control). This is straightforward, but has at least two limitations: 1) it conflates the distinction between the controller and the DID subject. When someone-claiming-to-be-Alice shares a VC that contains Alice's DID and proves control of that DID, what has been proved is NOT that the party you're interacting with is Alice, but rather that the party you're interacting with controls Alice's DID. The DID spec requires these to be viewed as two different things, though in practice the distinction often collapses. This allows games to be played (e.g., Alice's legal guardian can satisfy half a proof with credentials about Alice, and half with credentials about the guardian, since the only binding property you have is the commonality of control). I have always wondered when this subtlety would bite the VC community; I intuit that there are cases where it will matter, but have not attempted to suss them all out. 2) it has privacy/correlation problems, as we all know.
In ZKP land, you can also bind a VC to a holder using proof-of-link-secret control (instead of or in addition to a public DID). Although a link secret can be shared, sharing it after issuance won't allow the sort of controller=subject conflation that DIDs do, so combining the techniques may be useful. Perhaps more interestingly, you can also bind using a biometric, a situational attribute, a password, a capability token, etc. Each of these would be a different verification method in a DID doc. So it would be good to genericize your first 3 examples slightly by requiring that a binding be proved, and leaving how it is proved as something that could have multiple concrete implementations that are not mutually exclusive.

Can you link to or walk through some examples of how to verify properties around an issuer?

The issuer is qualified by trust framework, either directly ("in our trust framework, we trust DIDs X and Y to issue college diplomas") or indirectly ("in our trust framework, an institution can issue college diplomas if it can prove it possesses an accreditation credential from DID Z"). Note that in the second case, any VC-provable characteristics are possible qualifications for the issuer, and the way you would express those qualifications is with a new presentation definition that qualifies the issuer, when satisfied. It is also conceivable that the trust framework would specify the qualifications of the issuer in ways that are not VC-provable (e.g., "the issuer must talk on a public IP address from this range or this geo" or "the issuer must possess a TLS cert from one of these CAs").

The issuer is qualified by verifier criteria. This can be expressed and evaluated exactly as if by trust framework; the difference is that the criteria are chosen by the verifier without regard to a trust framework.

Note that #1 and #2 are combinable; they are not mutually exclusive.

Presently, the Presentation Definition is only concerned with property-level extraction from whatever pile of VCs are thrown at it. If we want to verify things like issuers of a specific credential from which we derived Property X, not sure if there's a natural expression how the standard is currently. Just to confirm, this is what you want to be able to confirm, right?

Yes, this is what I want. The issuer of a cred is already a property in the VC, so it should be totally uncontroversial to be able to express requirements about the value of that property. If we can't do that much, then anybody can issue a driver's license or passport, and we have no way to express which ones we will accept. Most of the more extended characteristics I'm suggesting we support are VC-provable. They don't require new language in a spec; they just require the issuers to have VCs of their own.
Related to this is the idea of provenanced data and chained credentials (see Aries RFC 0104). If presentation definitions supported this concept, we would be able to express a requirement like this: "Prove to me the name and birthdate from your employment credential, and prove to me that the employment credential based this assertion on data that your HR department observed in your passport." Note that the latter clause in the proof is, again, NOT a new construct that requires modifications to the VC spec; instead, we're saying that the prover must disclose to the verifier not just the normal fields of a credential, but also a field called provenanceProof which is, itself, a self-contained verifiable presentation that demonstrates "HR observed this in your passport." In other words, the only thing we have to do to get this power in our presentation definitions is allow them to be recursive.

I think if we took your suggestion of splitting Presentation Definition into a static Presentation Definition and instance-based Presentation Request in #23, we could possibly include a simple way to specify property values that must be matched in the Presentation Request. For example, we could require a property to have its relative credentialSubject.id to match a specific DID, e.g. did:ethr:0xdeadbeefcafe. I feel that we should avoid using derived variables like $proverDID in the Presentation Definition for now.

I agree. I did not propose derived variables like $proverDID.

We could consider syntax to add constraints to the issuer property, including those for specifying trust frameworks/privileges.

I don't think we need this. We simply need to allow a presentation to be recursive, and to change subject at each level of recursion: "Prove with A's credentials that issuer X [did] asserted Y and Z; prove with X's credentials that W, V."

Alice is the applicant to BigBank for a new line of credit, and wishes to present her verifiable credentials representing her state-issued identity (drivers license) and proof of address (utility bill). BigBank wants to tell Alice that her verifiable credentials must have her DID as the credentialSubject.id.

First and foremost the above use case is flawed. It is not how things operate today and is not how they will operate in future. If you open a new bank account today, either online or by visiting the bank (both operate today in the UK) thenBigbank is not in the least bit interested in Alice's DID. What Bigbank is interested in is Alice's identity, not her identifier. It wants to see the details from her state-issued identity, such as name and address and DoB (but not about which vehicles she can drive) and secondary proof of address from a current utility bill. It also wants a PoP that these VCs belong to Alice, so it will want a portrait photo to match with the face of the person sitting in front of the bank clerk (on site registration) or device camera (online registration). And that's it. The DID is a red-herring that only serves to confuse the search for a working solution with VCs.

@David-Chadwick : I find myself simultaneously agreeing and disagreeing with you. The agreement is tied to "BigBank is not in the least bit interested in Alice's DID. What BigBank is interested in is Alice's identity, not her identifier." To me, this is totally correct and uncontroversial. Violent agreement.
However, I feel like it misses the point in a sense. What Wayne's framing assumes is that we have to map high-level, human interests as describable by untrained, non-technical humans into the data format of a presentation definition. And that means we have to point to something in the presentation def that gives the humans what they want. That thing is the binding between the credential and the person. It is supposed to accomplish nothing for Alice to share Bob's credentials, if she's opening an account for Alice; Alice should have to share Alice's credentials to satisfy the bank as verifier. How do we ensure that? By expressing our binding requirements. Wayne gave the canonical binding requirement (prove control of a DID that the credential asserts is controlled by Alice, so we have reason to believe the prover is (or is a controller for) Alice-the-subject.
Said another way, if a request for VC-based evidence can't say something about the prover-to-credential-subject relationship that a verifier needs to see, the evidence will be useless. Sure, a VC describing Alice has been presented, and Alice's identity has been studied/revealed/shared. But since we don't know that the parting doing that presentation is actually Alice, the bank can't open the account. (The complexity of this issue becomes more clear when we think about credentials with multiple subjects, such as a birth certificate. A government considering the issuance of a passport may ask to see a VC-formatted birth certificate to establish facts of birth. But if the holder of the birth certificate, and the applicant for the passport, is the mother rather than the child, then the birth certificate in question is irrelevant. Just because Alice's child is a French citizen doesn't mean Alice is. We MUST have a way to express this sort of requirement in our requests for evidence.)

@David-Chadwick I'm hearing you say that BigBank cares about Alice's "proofed" identity, as demonstrated by a state-issued identification card and a utility bill, and that the DID is not necessarily relevant at all. This makes sense to me.
However, there seems to be another requirement here--that Alice's identity proofing is bound to a specific authenticated session, whether established in person, over an cookie-authenticated HTTPS session, or through DID-based communications. Could it be relevant in this way? We could even imagine slotting out the DID for an OpenID Connect token that Alice got from login.gov, already proofed to an appropriate assurance level of authentication.

Let's throw in something that basically makes the DID case crystal clear: assuming acceptance, Alice wants the bank to have an identifier they know her by, which she owns/controls independently of that relationship, to do things like:

Store her monthly bank statements with her via her Hub personal datastore
Send/store any subsequent VCs they issue (ex: qualified investor proof) with her via her Hub personal datastore
Allow them to access other data/creds that they may need to periodically use for banking-related activities, which they would fetch, with DID-based permissions, from her personal datastore.

Basically, you'll need a DID to do the 99.99% of identity things that aren't directly within/about the VCs themselves.

That thing is the binding between the credential and the person.

I totally agree. This is what I referred to as PoP - proof of possession. But Binding is also an acceptable term for this. So PoP should be proven crytographically and biologically. The former only proves the binding between the device or session and the VC, the later between the VC and the person. (In fact we could dispense with the former if the latter is really strong and unbreakable, so this is why I only mentioned this in my original post).

prove control of a DID that the credential asserts is controlled by Alice,

This is not good enough because it does not prove control by Alice but control by a key or device holding a key. I can give my device holding my keys to a friend, and they can masquerade as me. This is why the portrait photo matching is also required (as it is today when registering for an online bank account).

Alice wants the bank to have an identifier they know her by, which she owns/controls independently of that relationship,

I refute that requirement. It does not matter a jot what Alice requires. It is only what the bank requires that matters. If you dont satisfy the bank's requirements you wont get a new account. So this requirement is a red-herring.

I refute that requirement. It does not matter a jot what Alice requires. It is only what the bank requires that matters. If you dont satisfy the bank's requirements you wont get a new account. So this requirement is a red-herring.

From my experience talking to countless enterprise customers (including many banks) in my work at the largest software company on the planet, I assure you enterprise customers are keenly interested in pushing personal data out of their systems to reside with users for a myriad of reasons, including: reduction of liability, GDPR compliance, and other security-related drivers. Beyond that, the enterprises that adopt DIDs + personal datastores will be able to provide new and better services that other competitors simply can't via the old model of ID/data capture within proprietary silos.

Pushing personal data out of their systems can easily be done without the need for DIDs. For example, the bank validates the user's identity from the set of VCs that the user presents, and then issues the user with one new VC. It only stores the PII it needs to store to comply with GDPR (in fact even this isnt needed because it can always ask the user to represent the identity VCs at any time). All the user needs to present from now on is the bank issued VC to be uniquely identified and authorised by the bank. No DIDs are needed.

@David-Chadwick  I am going to list a series of user stories, and I would like you to tell me how you'd accomplish them without a DPKI system + decentralized personal datastores:

As a user, I want my records (e.g. banking data) stored across secure, encrypted locations/instances of a datastore I can control, encrypt, and access, without reliance on identity providers or centralized proprietary silos, all of which sync with each each other regardless of what device or cloud they are running on.
As a user, I want to permission apps to access my data across this array of self-owned storage instances in a standard fashion, so they can provide me an app experience on top of the data I own - for example: I want to give Mint a set of permissions/keys to fetch subsets of my data to do banking related visualizations, not from centralized entities or silos, but from my self-owned array of personal storage instances.
As an app developer, I don't want to have a backend server for my app at all, I just want to transact with the user's standard data storage instances with a set of standard APIs that are not bound to providers or silos.

Please detail for me how you would create such a system without IDs that are owned and controlled by users, that aren't trivially interdictable and subject to the whims of central providers/silos (ex: email addresses, centralized app usernames, etc.), wherein the data does not reside in provider-centric services or centralized app silos.
Go!

Who owns this datastore (hardware software)? Who pays for it? If you do (solely or jointly with others) then you can do whatever you want with this resource and devise your own P2P or DLT system for it. But if others own it and require you to pay for it, then they will require you to identify yourself before they will grant you access. In this case you cannot avoid having one or more trusted identity providers in the system.  It is simply not possible for two strangers to identify themselves without a TTP.  If the system is free and publicly accessible then you dont need to identify yourself. A simple asymmetric keyID is sufficient on enrollment to ensure it is always you each time your return - but this is authentication not identification.
You can easily delegate your privileges to others by issuing the others (people, things etc) with VCs in which you are the issuer and they are the subjects. Its called DoA.
If you have a set of standard APIs available to you as a developer, then you use them and dont care how they are implemented. Its not your concern.
In general, ABAC systems only need to know the user's identity attributes, and can work out the permissions based on these attributes. Identifiers are not needed, but people implement identifiers as a simple way of uniquely identifying each user in the system, rather than using a unique set of the user's identity attributes. This false belief that identifiers are needed has led to the belief that DIDs are needed.

Who owns this datastore (hardware software)? Who pays for it?
The standard personal datastore instances would be run on the user's devices + other places where you can freely store encrypted data today (e.g. cloud storage services that offer free tiers)

If you do (solely or jointly with others) then you can do whatever you want with this resource and devise your own P2P or DLT system for it.

As a user, this would be a standard, not a one-off, random setup - the work for this is already underway in DIF's Secure Data Storage WG.

But if others own it and require you to pay for it, then they will require you to identify yourself before they will grant you access.

I can create random burner emails to get free cloud storage today, and there is no reason to believe I will have to show a driver's license to get the same exact type of free service tier.

In this case you cannot avoid having one or more trusted identity providers in the system.  It is simply not possible for two strangers to identify themselves without a TTP.

I think you are confusing use cases - for all the app-related personal datastore use cases, there is no need to identify myself for the purpose of an app storing its data with my personal datastore.

A simple asymmetric keyID is sufficient on enrollment to ensure it is always you each time your return - but this is authentication not identification.

Not being able to roll the keys and endpoints related to my ID and the datastores that it points makes the use of a raw public key a nonstarter - DIDs solve this.

You can easily delegate your privileges to others by issuing the others (people, things etc) with VCs in which you are the issuer and they are the subjects. Its called DoA.

Besides the fact that the VC would need to be associated with the common identifier that stands for you, which both the delegated party and the datastore could resolve, this is beyond a simple bearer access token: permitting access will often require a shared symmetrical key that permitted parties secure via DID-encrypted exchanges, such that the security of the system is not bound to a provider's service.

If you have a set of standard APIs available to you as a developer, then you use them and dont care how they are implemented. Its not your concern.

Of course, but for the use cases presented, I would again challenge you to accomplish the things I am talking about with a bunch of centralized, siloed services - that route conflicts with the underlying requirements presented.

In general, ABAC systems only need to know the user's identity attributes, and can work out the permissions based on these attributes. Identifiers are not needed, but people implement identifiers as a simple way of uniquely identifying each user in the system, rather than using a unique set of the user's identity attributes. This false belief that identifiers are needed has led to the belief that DIDs are needed.

Identifiers are needed, because the remote personal datastore location must be able to resolve the current PKI key/routing state without requiring in-band connection to the user.

We are getting off-topic. For purposes of moving this spec forward I propose we agree that there seems to be a need to describe relationships between the Holder, Issuer, and Subject. These could be DIDs but they don't need to be, as described in vc-data-model (see issuer, for example). Here are the outstanding items for which we can hope to reach resolution:

What relationships are important to be able to stipulate? All of Issuer-Holder, Holder-Subject, Subject-Issuer (self-issued)?
What additional constraints must we be able to express about each of Issuer, Subject, and Holder, while allowing for their manifestation as any of: public DID values, ZKP-elided DIDs, and non-DIDs (as in the issuer example above)? Our spec language should be conceivably compatible with emerging machine-readable trust frameworks while also allowing for the description of existing checks such as "in-person portrait picture on driver's license verification" or "IANA certified certificate authority issued TLS".

Any objections to that?

@wyc no objections here. What is the outcome in terms of the spec? Is there going to be a PR that changes the language we use?

None from me, thanks

Discussion from WG:

Do we need Hubs to allow practical checking of issuer/holder/subject relationships?

Several folks in this meeting echoed the realization that to do this effectively without introducing some rather intractable conditions or a cascade of downstream credential issuance/schema requirements, we really need something like a Hub. This is because no matter how one articulates the need for a chain of proofs about, or related to, the credentials being submitted (e.g. the diploma credential you submit must be from a university that itself has a credential that proves it is an accredited institution), you need a sane way to find and retrieve that proof as a Holder or Verifier (depending on who is doing the legwork). To this end, we feel it is best to look at this as something that needs a solution, but may require other specs/solutions to achieve. For now, the proposal is to mark this as something we need to solve as soon as we can, but do so in a way that doesn't encumber the spec with things it can't solve on its own.

@csuwildcat can we get a concrete proposal for a workaround in absence of "Hub"...
like serviceEndpoint URIs, etc...? I always prefer to look at some json over reading walls of text :)

To illustrate how this probably should be done, at a high level:

Alice, her university, and the verifier all have Hubs
Alice is presented with a Presentation Definition that says she needs a diploma, and the Issuer of the diploma must themselves have some other credential proving they are accredited.
Either flow happens next:

Alice resolves the Issuer's DID > get Issuer's Hub endpoints > fetches accreditation credential by schema/type query > presents it with her Presentation Submission
Alice submits just her diploma credential > Verifier resolves the Issuer's DID > gets Issuers Hub endpoints > fetches accreditation credential by schema/type query

Either way works, but you need an inferentially knowable place to get an object/cred of the type you seek - aka: Hubs

@csuwildcat can we get a concrete proposal for a workaround in absence of "Hub"...
like serviceEndpoint URIs, etc...? I always prefer to look at some json over reading walls of text :)

Personally, I will not invest a single second of my time inventing a special server/endpoint for looking up a single object type. That would be a foolish waste of effort that should be rolled into making a service/endpoint that handles the same inferentially knowable storage and lookup functionality for all types of objects. Creating a service/endpoint for a specific type of object as if they are all special snowflakes is pure insanity, and will lead to there being 100 different endpoints for fetching thousands of common objects. If this happens, I will be duty-bound to relentlessly mock everyone involved, until such time that the community capitulates and admits they should have just built the damn Hub to begin with. (none of this angst intended for you or anyone on the thread, it's just general frustration that folks have ignored what I continue to believe is the single most important component required for this to all work, besides DIDs themselves. But I digress)

Basically, this:

One way to provide this without hubs is described in Aries RFC 0104. Please note that the mechanism outlined there has no dependency on ZKPs; it will work for all types of VCs.

@dhh1128 embedding linkages to associated credentials within a credential (either by direct credential reference or to the location of associated attesters) isn't a tractable solution, imo. There are 1:Many cases where a cred can't possibly point to all the associated creds a verifier may want to check. Additionally, there are many cases where dynamic associations with upstream creds occur post-issuance, meaning you wouldn't have the references to an associated cred/issuer at the time of issuance. The dynamic nature of endpoints (along with the 1:Many association case) would also prohibit baking a series of query locations into credentials, as those could change, break, etc. after issuance. The only serious way to do this, imo, is to use DIDs for what they do best - a decentralized PKI and routing layer - to crawl for these things in a way that isn't brittle and can automatically handle just about every use case imaginable in this problem set.

Proposal: specify that requirements of credential Issuers will be exclusively in the scope of the Verifier's evaluation, not defined in the spec for v1, but we will add notes to make this clear.

I can live without a lot of the fanciness, but it is absolutely non-negotiable to be able to express a requirement like, "the DID of the issuer must be a member of the following list." While a verifier can enforce this without having support for it in the language, the verifier has no way of helping the prover know that they're looking for this requirement unless it's part of what's in the spec. "Give me an employment credential" is not very helpful without saying, "Give me an employment credential <from this DID, which is an employer I trust>". "Give me a diploma" isn't very helpful without being able to say, "The only diplomas I'm interested in are ones from these issuers." Verifiable credentials are, at their heart, far more about the question "Says who?" than they are about the question, "Says what?". It's the "who" question that confers the trust.
Do we already support this? If so, I'm cool with Daniel's proposed deferral of the rest of my requested features. But without even the ability to require a particular issuer DID from a set, the spec's dead in the water, IMO.

@dhh1128 we support this as a string matching for the issuer field or any other field, including any within credentialSubject, as such:
    "input_descriptors": [
      {
        "id": "banking_input",
        "schema": {
          "uri": ["https://bank-standards.com/customer.json"],
          "name": "Bank Account Information",
          "purpose": "We need your bank and account information."
        },
        "constraints": {
          "limit_disclosure": true,
          "fields": [
            {
              "path": ["$.issuer", "$.vc.issuer", "$.iss"],
              "purpose": "The credential must be from one of the specified issuers",
              "filter": {
                "type": "string",
                "pattern": "did:example:123|did:example:456"
              }
            }
          ]
        }
      },
    // ...
    ]

Is this okay for v1, with fancier stuff to come? Of course the downside is that referencing a large set of issuer identifiers does not scale well. Furthermore, we need to resolve this to make sure the constraint actually makes sense: https://github.com/decentralized-identity/presentation-exchange/issues/27

Okay, if we can do that much that I am okay with deferring the rest.

per the meeting 9/3/2020: The spec already provides the minimal capabilities desired.

I propose that we close this issue, as I was the source of the original question even though @wyc kindly logged the issue for me. I think we've accomplished what we needed to in terms of analyzing it.

Your terms are acceptable, @dhh1128


MongoDB Hit output support

Adds support to have hits saved to MongoDB.

Please add a wordlist editor that allows user paste wordlist directly and save. Instead of uploading files.

Please add a wordlist editor that allows user paste wordlist directly and save. Instead of uploading files.

Go into Issues and make a [Request] don't ask for features in my pull request.


Tests should verify exception messages

In test we have a few @expectedException , eg in tests/tests/install/install.php :
    /**
     * Test incorrect config provided
     * @expectedException YOURLS\Exceptions\ConfigException
     */
    public function test_incorrect_config() {
        $test = new \YOURLS\Config\Config(rand_str());
        $test->find_config();
    }

We should also be using the @expectedExceptionMessage annotation

I'd like to take this one.


Rewrite build process again (revival of #9)

(e) to launch vim, enter to skip

Resolve conflicts though

oh @TheBunnyMan123 you should make the PR checks required for merge

Ight

Spoiler alert it doesn't actually work

nvm we're hitting an I'm an idiot bug

alright turns out that I am an idiot; it's -P for Gradle properties not -D
:w

Once your ready for review fix the merge conflicts

alright! checks are successful and artifacts look good, this should be ready-to-merge for now until UnlikePaladin uploads 0.1.4+1.20.4 to maven

also please delete branches once you are done with them

Looks good, did you ask UnlikePaladin to upload them?

Yeah


Backdrop stays open after navigate using routerlink from inside mat dialog

What is the expected behavior?
When clicking an element with the routerLink directive, the navigation should close the dialog and make the backdrop disappear
What is the current behavior?
The dialog closes but the backdrop stays open.
Doesn't work even with closeOnNavigation: true or with applying mat-dialog-close to the element that has the routerLink directive
What are the steps to reproduce?
Providing a StackBlitz reproduction is the best way to share your issue.
StackBlitz starter: https://goo.gl/wwnhMV
Have an  element with a routerLink directive inside a mat dialog template and click on it to navigate.
Which versions of Angular, Material, OS, TypeScript, browsers are affected?
Angular Core: 7.2.5
Angular Material: 7.3.2
Is there anything else we should know?

Can you provide a reproduction in StackBlitz.  This will help us to investigate the issue you are seeing.

I ran into this and found that the issue was that the dialogRef wasn't triggering ngOnDestroy when it moved to the new route.
Found something that seems to work  - I wrapped the routerLink in an  tag
From within the dialog:
<button mat-button [routerLink]="'newRoute'">GO SOMEWHERE</button>
To
<a [routerLink]="'newRoute'"><button mat-button >GO SOMEWHERE</button></a>
Early finding is that it seems to trigger a cleanup of the old components and creation of a new route tree - will add more if I see anything different.

reproduce: https://angular-h4uz66.stackblitz.io

Any news on this?
My current workaround:
private _dialogRef: MatDialogRef<ModalComponent> = null;

openDialog() {
    this._dialogRef = this._dialog.open(ModalComponent);
    this._dialogRef.afterClosed().subscribe(() => this._dialogRef = null);
}

ngOnDestroy() {
    if (this._dialogRef) {
        this._dialogRef.close();
    }
}

Closing because this issue has been inactive for 2 weeks or more after follow up was requested.


[ReleasePrep][2020.08.07] RI of dev into master

Deployment work item: https://github.com/NuGet/NuGetGallery/issues/8145

I've verified @joelverhagen machine's key changes on DEV. @drewgillies has verified his changes and @scottbommarito's on DEV


CM-745: Bump Strapi from 4.10.7 to 4.11.1

Jira Ticket:
CM-745
Description:

Created this PR since Gatsby upgrade will take time
Upgrade Strapi from 4.10.7 to 4.11.1 including a security fix 4.10.8
https://github.com/strapi/strapi/releases/tag/v4.10.8
https://github.com/strapi/strapi/releases/tag/v4.11.0
https://github.com/strapi/strapi/releases/tag/v4.11.1
Remove @strapi/plugin-gatsby-preview for now as it was not supported by node <=16.x.x

npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE   package: '<EMAIL_ADDRESS>npm WARN EBADENGINE   required: { node: '>=12.x. <=16.x.x', npm: '>=6.0.0' },
npm WARN EBADENGINE   current: { node: 'v18.14.1', npm: '9.3.1' }
npm WARN EBADENGINE }

Update @babel/plugin-transform-block-scoping and eslint as they were specified when I ran npm outdated
There's a vulnerability in @strapi/plugin-graphql

dicer  *
Severity: high
Crash in HeaderParser in dicer - https://github.com/advisories/GHSA-wm7h-9275-46v2
No fix available
node_modules/dicer
  busboy  <=0.3.1
  Depends on vulnerable versions of dicer
  node_modules/busboy
    graphql-upload  <=14.0.0
    Depends on vulnerable versions of busboy
    node_modules/graphql-upload
      @strapi/plugin-graphql  *
      Depends on vulnerable versions of graphql-upload
      node_modules/@strapi/plugin-graphql

I removed @strapi/plugin-gatsby-preview once before and it didn't disapper from the Strapi admin console on all environment.  So I had to add it back again.  We'll need to keep an eye on it to make sure it uninstalls itself properly this time


Update phosphoricons to 2.1.0 release

Updates Phosphoricons to latest 2.1.0 release

Hi @noozo , what is required to push this and release?

Sry @vitalis thanks for this. I completely missed it. <3


smarthome_sdk.js:63 Uncaught ReferenceError: cast is not defined

Following the tutorial, I don't know what went wrong.

Testing must be done on a supported Home/Nest device, as the Local Home SDK binary is not available in the browser (it is only present on those devices).

测试必须在受支持的Home / Nest设备上进行，因为本地Home SDK二进制文件在浏览器中不可用（仅在那些设备上存在）。

thank you for your help


eip1559 gas estimation issue - transaction underpriced: tip needed 1, tip permitted 0

Component
Forge, Cast
Have you ensured that all of these are up to date?

[X] Foundry
[ ] Foundryup

What version of Foundry are you on?
forge 0.2.0 (26e6e57 2024-04-28T00:19:12.405804000Z)
What command(s) is the bug in?
cast send 0x97c75664c1555F958F25b84D91f01aEFaFD4Fe55 --value 0.01ether -r https://sepolia.mode.network
Operating System
macOS (Apple Silicon)
Describe the bug
on sepolia.mode.network (and other networks) it seems that gas tip calculation has some issue
tx fails with
server returned an error response: error code -32000: transaction underpriced: tip needed 1, tip permitted 0

workaround is go legacy --legacy or manual gas setting for both gas price and max gas price e.g. --gas-price 0.01gwei --priority-gas-price 0.01gwei

+1 encountered this on mode sepolia as well. Did not appear to have the issue on mainnet.

this could be due to https://github.com/ethereum/go-ethereum/releases/tag/v1.13.12

Fix enforcement of minimum miner tip

@klkvr maybe we should enforce tip of at least 1wei?

@klkvr maybe we should enforce tip of at least 1wei?

yeah, that should work, though not sure if this should be part of alloy's default estimator

This has been a thorn in my side since early April, we had a CI smoke test which did a basic cast send which worked until the nightly which contained this: https://github.com/foundry-rs/foundry/pull/7106 . We then switched to an old nightly which got yanked, and have done everything we can to not rely on foundry since.
Notably we are building our own rollups, and working with others who are. The default behavior around gas estimation seems to fail pretty wildly for local dev chains & rollups. Need to either manually set the priority fee or use a --legacy on sends. Quite annoying for deploying contracts.

Yep, running into this as well on Sepolia..

looks like https://github.com/alloy-rs/alloy/pull/808 landed, what do we need to get this into foundry? (I am unfamiliar with foundry's build/dep pipeline)

i think we just need to update the deps and eventually make some wiring
@gakonst @mds1 any guidance to make it happen?

Should be resolved after https://github.com/alloy-rs/alloy/pull/808


[Bug]: Cannot build if import package name include '@'

Version
npmPackages: @rslib/core: 0.0.14
Details
This is the examples of module federation,  i found that would be error when i build, and i just import the button from @shopify/polaris.
import { init, loadRemote } from '@module-federation/enhanced/runtime';
import { Suspense, createElement, lazy } from 'react';
import { CounterButton } from './CounterButton';
import { useCounter } from './useCounter';
import { Button } from '@shopify/polaris'; // what i change

init({
  name: 'rslib_provider',
  remotes: [
    {
      name: 'mf_remote',
      entry: 'http://localhost:3002/mf-manifest.json',
    },
  ],
});

export const Counter: React.FC = () => {
  const { count, increment, decrement } = useCounter();

  return (

      <Suspense fallback={
loading
}>
        {createElement(
          lazy(
            () =>
              loadRemote('mf_remote') as Promise<{
                default: React.FC;
              }>,
          ),
        )}
      </Suspense>
      <Button primary />

        Counter From Rslib MF Format:
        {count}

      <CounterButton id="mf-e2e-lib-decrease" onClick={decrement} label="-" />
      <CounterButton id="mf-e2e-lib-increase" onClick={increment} label="+" />

  );
};

And this is the error when building the mf-react-componet

I think it might be an invalid identifier including '@' symbol, but how to solve that, could you please help review this？
Reproduce link
n
Reproduce Steps

cd examples/module-federation/mf-react-component
yarn add<EMAIL_ADDRESS>add import {Button} from '@shopify-polaris' into the index.tsx
yarn build

Can you add this pkg into devDependencies? if you want to build this pkg into your assets you should do that because rslib will auto external pkg which is dependencies or peerDependencies.
And in mf format externalType is set to var, it means @xxx is not a standard syntax, so you get this error

Another solution is to set externalType to global, i have modify this https://github.com/web-infra-dev/rslib/pull/331

Can you add this pkg into devDependencies? if you want to build this pkg into your assets you should do that because rslib will auto external pkg which is dependencies or peerDependencies. And in mf format externalType is set to var, it means @xxx is not a standard syntax, so you get this error

Got it. But i think it must be dependencies in mf mode, and i would like to share the @shopify/polaris as common dependencies by  the shared configuration.

But i think it must be dependencies in mf mode

Rslib enables autoExteranl by default, which means even @module-federation/enhanced/runtime is in dev dep, it will be bundled into the output as well. You could refer to https://modernjs.dev/module-tools/en/api/config/build-config.html#autoexternal as the Rslib's documentation is not finished yet, but the functionality is identical.
And @shopify/polaris could be defined to be shared by shared.

But i think it must be dependencies in mf mode

Rslib enables autoExteranl by default, which means even @module-federation/enhanced/runtime is in dev dep, it will be bundled into the output as well. You could refer to https://modernjs.dev/module-tools/en/api/config/build-config.html#autoexternal as the Rslib's documentation is not finished yet, but the functionality is identical.
It should not be placed in dependencies because the output won't be bundled anymore after Rslib's build process, so it must be bundled ahead and not externalized.

and i would like to share the @shopify/polaris as common dependencies by the shared configuration.

And @shopify/polaris could be defined to be shared by shared.

Thanks. And what i understand is that there are 2 ways to avoid the error.

set the configuration autoExternal: false
move the deps to devDeps

If that is correct, for my case, i think the first one is better, because some deps should not be placed in devDeps. In mf mode, it work, but in npm mode, it doesn't work.

For npm package consumers, they should not use the mf output. And when publishing to npm, mf output won't be build at all. So putting it to dev dep makes sense for me.

Thanks. I will take another look later.


Invalid Automation file

Thanks for the addon.
Got this error in the web ui: „ERROR Internal Server error“
And this in the Addon protocol
s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service legacy-cont-init: starting
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service legacy-services: starting
s6-rc: info: service legacy-services successfully started
Python 3.9.12
INFO:     Started server process [64]
INFO:     Waiting for application startup.
INFO:     Application startup complete.
INFO:     Uvicorn running on http://<IP_ADDRESS>:8000 (Press CTRL+C to quit)
INFO:     <IP_ADDRESS>:40442 - "POST /automations/list HTTP/1.1" 500 Internal Server Error
ERROR:    Exception in ASGI application
Traceback (most recent call last):
  File "/app/./src/automations/loader.py", line 27, in load_automation
    yield ExtenededAutomationData(
  File "/usr/local/lib/python3.9/site-packages/pydantic/main.py", line 406, in __init__
    raise validation_error
pydantic.error_wrappers.ValidationError: 1 validation error for ExtenededAutomationData
trigger
  value is not a valid list (type=type_error.list)
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
  File "/usr/local/lib/python3.9/site-packages/uvicorn/protocols/http/httptools_impl.py", line 375, in run_asgi
    result = await app(self.scope, self.receive, self.send)
  File "/usr/local/lib/python3.9/site-packages/uvicorn/middleware/proxy_headers.py", line 75, in __call__
    return await self.app(scope, receive, send)
  File "/usr/local/lib/python3.9/site-packages/fastapi/applications.py", line 208, in __call__
    await super().__call__(scope, receive, send)
  File "/usr/local/lib/python3.9/site-packages/starlette/applications.py", line 112, in __call__
    await self.middleware_stack(scope, receive, send)
  File "/usr/local/lib/python3.9/site-packages/starlette/middleware/errors.py", line 181, in __call__
    raise exc
  File "/usr/local/lib/python3.9/site-packages/starlette/middleware/errors.py", line 159, in __call__
    await self.app(scope, receive, _send)
  File "/usr/local/lib/python3.9/site-packages/starlette/middleware/cors.py", line 92, in __call__
    await self.simple_response(scope, receive, send, request_headers=headers)
  File "/usr/local/lib/python3.9/site-packages/starlette/middleware/cors.py", line 147, in simple_response
    await self.app(scope, receive, send)
  File "/usr/local/lib/python3.9/site-packages/starlette/exceptions.py", line 82, in __call__
    raise exc
  File "/usr/local/lib/python3.9/site-packages/starlette/exceptions.py", line 71, in __call__
    await self.app(scope, receive, sender)
  File "/usr/local/lib/python3.9/site-packages/starlette/routing.py", line 656, in __call__
    await route.handle(scope, receive, send)
  File "/usr/local/lib/python3.9/site-packages/starlette/routing.py", line 259, in handle
    await self.app(scope, receive, send)
  File "/usr/local/lib/python3.9/site-packages/starlette/routing.py", line 61, in app
    response = await func(request)
  File "/usr/local/lib/python3.9/site-packages/fastapi/routing.py", line 226, in app
    raw_response = await run_endpoint_function(
  File "/usr/local/lib/python3.9/site-packages/fastapi/routing.py", line 161, in run_endpoint_function
    return await run_in_threadpool(dependant.call, **values)
  File "/usr/local/lib/python3.9/site-packages/starlette/concurrency.py", line 39, in run_in_threadpool
    return await anyio.to_thread.run_sync(func, *args)
  File "/usr/local/lib/python3.9/site-packages/anyio/to_thread.py", line 31, in run_sync
    return await get_asynclib().run_sync_in_worker_thread(
  File "/usr/local/lib/python3.9/site-packages/anyio/_backends/_asyncio.py", line 937, in run_sync_in_worker_thread
    return await future
  File "/usr/local/lib/python3.9/site-packages/anyio/_backends/_asyncio.py", line 867, in run
    result = context.run(func, *args)
  File "/app/./src/api/routes/automations.py", line 19, in list_autos
    return ListData(
  File "/usr/local/lib/python3.9/site-packages/pydantic/main.py", line 404, in __init__
    values, fields_set, validation_error = validate_model(__pydantic_self__.__class__, data)
  File "/usr/local/lib/python3.9/site-packages/pydantic/main.py", line 1040, in validate_model
    v_, errors_ = field.validate(value, values, loc=field.alias, cls=cls_)
  File "/usr/local/lib/python3.9/site-packages/pydantic/fields.py", line 734, in validate
    v, errors = self._validate_sequence_like(v, values, loc, cls)
  File "/usr/local/lib/python3.9/site-packages/pydantic/fields.py", line 765, in _validate_sequence_like
    for i, v_ in enumerate(v):
  File "/app/./src/automations/manager.py", line 25, in find
    yield from load_automation(auto, tags.get(i, {}))
  File "/app/./src/automations/loader.py", line 35, in load_automation
    raise InvalidAutomationFile from err
src.automations.errors.InvalidAutomationFile

Can you confirm if one of the automations you have contains a trigger that is not a list? (I was not aware this is allowed in HA). I will try to address this in an upcoming release.

Hi thanks for reply.
Sorry, I'm not sure what exactly to look for. I have a lot of automations. Everything looks fine and working correct.

So a few things,

I've updated the latest version to have some better error handling for what my addon deems as "invalid". I also corrected some issues in my implementation which didn't account for some edge cases. So try to update and see if things work

what I meant is that in yaml syntax this

Prop1: 1
Prop2:
Prop3: hello

Will give each of the props the following types:

Prop1 --> number
Prop2 --> null (or undefined, depending on parser)
Prop3 --> string

So the error you got was one where my validation failed as it was not expecting a "null" value. Hence I asked to see where in your automations you might see this pattern.
Either way, let me know if the update helped 😃

The Web UI is now loading. Thank!
It looks like this.
Many of my automations did not show any  visual graph

`- id: alarmanlage_an
alias: alarmanlage_an (Uhrzeit)
trigger:

entity_id: sensor.time
platform: state
to: '23:30'
condition:
condition: or
conditions:

condition: state
entity_id: person.simon
state: home
condition: state
entity_id: person.leni
state: home
action:

service: alarm_control_panel.alarm_arm_night
target:
entity_id:

alarm_control_panel.alarmo
data:
code: 'xxxx'

service: alarm_control_panel.alarm_arm_away
data: {}
target:
entity_id: alarm_control_panel.blink_home
mode: single`

Ok I see, I think I either misunderstood the HA docs or they've implemented it differently than I thought.
I need to make the description optional which is what's causing your error.
I will try to get an update soon for this!

thanks for the update.
But I'm still having these issues on most automations.

discription is not even in the automation

id: '1566394725941'
alias: Notify Kühltruhe wurde geöffnet
trigger:

entity_id: binary_sensor.kuehltruhe_tuer
for: 00:00:01
platform: state
to: 'on'
condition: []
action:
data:
message: Kühltruhe wurde geöffnet
service: notify.alle_ios_geraete
data:
data:
type: announce
volume_level: 2
message: Warnung Kühltruhe wurde geöffnet
service: notify.alexa_media_simons_echo_show
mode: single

@kolossboss i see, you should be able resolve it by adding a description. It's basically saying it's missing. I'll update it to be nullable.


[AIRFLOW-2330] Do not append destination prefix if not given

Addresses AIRFLOW-2330.
Description
The change introduces a check whether the destination_object parameter was given when using a wildcard (*) in the source_object parameter. If destination_object resolves to False, e.g. when not given (the default value is None) or is an empty string, the destination_object path is simply the source_object path.
It also includes some minor updates to docs and log messages.

Codecov Report

Merging #3233 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master    #3233   +/-   ##
=======================================
  Coverage   75.32%   75.32%
=======================================
  Files         196      196
  Lines       14599    14599
=======================================
  Hits        10996    10996
  Misses       3603     3603

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 3f1bfd3...809c7b7. Read the comment docs.

This will enable you to copy something from the source, to the source? Could you please elaborate, I find the logic hard to follow.

When using the wildcard, you're implicitly copying multiple files (e.g. foo/* means all files that start with foo/). The destination_object doesn't make sense in that context, so it was used to specify an extra prefix (often called a "folder" or "subfolder", although GCS, like S3, doesn't have an inherent hierarchical organisation) to be prepended to the destination paths.
Here's an example: let's assume that we have two files in a bucket called some_source_bucket: foo/file1.txt and foo/file2.txt. Now, say that we do:
copy_foo_files = GoogleCloudStorageToGoogleCloudStorageOperator(
    dag=dag,
    task_id='copy_foo_files',
    source_bucket='some_source_bucket',
    destination_bucket='some_destination_bucket',
    source_object='foo/*',
    destination_object='bar/baz'
)

This will copy files:
gs://some_source_bucket/foo/file1.txt
gs://some_source_bucket/foo/file2.txt

into:
gs://some_destination_bucket/bar/baz/foo/file1.txt
gs://some_destination_bucket/bar/baz/foo/file2.txt

Ideally, we could have a system that would allow building a complex destination path for multiple files, but that's a bigger fish to fry, and outside the scope of this ticket anyway.

Thanks @berislavlopac for the examples. It makes sense now to me. Maybe a good idea to turn one or two of these examples into an unit-test. This is some delicate code since we're possibly moving data here.

Tests added.


Keep simulating tx after submission & cancel if no longer executable

We are spending about 10% of our total gas usage on failed transactions. Failing transactions use gas up until the point that they fail. If a settlement has e.g. 5 interactions and only reverts in the last one we still pay a lot of amount of gas (cf. https://etherscan.io/tx/0x5741f69b78efce3f62764a2687653624fad3505aa917fd8370c635ab6a0f35a1).
We could save money if instead of letting the tx fail, we replaced it with a 0x noop transaction at a significantly higher gas price. This requires keeping simulation running while waiting for confirmation (similar to how we keep estimating gas).
A code pointer to the submission logic: https://github.com/gnosis/oba-services/blob/73cbfa407827a1b5a2c5e81481f219c77cc9062a/solver/src/settlement_submission/public_mempool.rs#L17

Done with the settlement submission refactor.


WIP: 4-ci-srv-03: [no-test] Update translations from Fedora Weblate

Update translations from Fedora Weblate

[ ] po-refresh

po-refresh in progress on 4-ci-srv-03.
Log: https://logs.cockpit-project.org/logs/po-refresh-1123-20201008-134141/


docs: How to roll back a deployment

Once the network is in a more stable place, it's less acceptable to cause downtime, so a failed deployment should be rolled back immediately instead of trying to debug and fix forward.
We need a section in the deployment guide for rolling back. Roughly, I think it's as straightforward as:

Before deploying, save a docker tag at the current deployed version, before setting it to the current master
When you decide to roll-back, retag the docker image back to the previously saved tag and re-run the deployment

We can't really believe a guide that hasn't been run, so do a whole deployment and roll-back cycle, following the guide, before marking this complete.

Not sure if this is a good idea or not... But at least until we enter into a "normal" release & deploy cadence, would it be helpful to simply tag a master commit as deploy-08/22/23? That way you only have to create one tag when running a deployment. It's fairly easy to look at the history and understand what tag to use for a rollback.


Cannot run GP commands in gp-workspace if geoprocessing lib is symlinked into node_modules

You should be able to run a full data prep script from within docker including publishing subdivided datasets.  This works normally but if you have npm linked over to a local geoprocessing folder, bundle-features will now fail.
The problem is that the npm link process will have created a symlink in your project folder over to the global npm folder on your host machine, which then symlinks over to your local GP install.  This global npm folder isn't mounted in Docker, and even so it would need to be mounted in a way such that the existing symlink works.
Let's look at the existing symlink from within the docker container
root@0741f5fb3dd7:/project/node_modules/@seasketch# ls -al
lrwxr-xr-x   1 root root    48 Feb 28 08:40 geoprocessing -> ../../../../geoprocessing/packages/geoprocessing

4 directories up (../../../..) doesn't exist in this container because we've mounted the project directory to /project when on the host machine it existed at /Users/myname/src/foo/bar
Possible solution might exist here:

https://properdesign.co.uk/developing-a-new-node-module-in-a-docker-container-without-using-npm-link/
use npm install which supposedly creates a file reference in package.json instead (didn't work for me), https://www.stefanjudis.com/today-i-learned/npm-install-supports-local-packages/

This issue also occurs when trying to run a gp command from a sibling package in the geoprocessing monorepo, where a symlink is made over to the main geoprocessing package.  updating title to reflect.
The alternative is to only run gp commands (like bundle-features) from outside the docker workspace.  Separating out the deploy from the prep into its own script can make this a little easier, but it's not an optimal situation.

Possible resolutions here - https://github.com/npm/npm/issues/14325

This is not currently an issue because data scripts are now run outside of the container, and gdal/ogr and related dependency calls are now isolated and run inside the container (https://github.com/seasketch/geoprocessing/issues/128)
Switching to a totally remote container work environment might avoid this issue altogether in the future.


Incorrect description - fiori using ABAP

Hello,
Scenario URL: https://developers.sap.com/tutorials/abap-environment-deploy-cf-production.html
Issue: Step 6.4: To add deploy config details enter npx fiori add deploy-config. -> Is this an ABAP Cloud System?: Y
Correct statement is: "Is this an SAP Cloud Platform System?"
please update the same.
Landscape Labels: trail1, trail2
Sprint Label: SCPTest-2009A
Scenario Label:SCPTest-fabap
priority label: high-prio

Hi @i353590 ,
thank your for your feedback. We updated this tutorial with following PR: #6017.
@MichaelCzcz can you merge?
Thank you.
Best regards,
Merve

Thank you for your feedback. The issue seems to be resolved, so I am closing the issue.
If you still have questions, feel free to reopen the issue.


Make Wood chopping use the general logs tag

Hi, I've noticed an issue with how Farmer's Delight integrates with other mods like Biomes a plenty-namely, that it doesn't(at least for wood chopping recipes,as far as I can tell). I tried to use Cherry Logs(byg:cherry_log) to get tree bark, but it doesn't work. Birch wood works fine.

Hello @wildjerry,
The logs chopping in cutting board isn't easy as you think, because it's a recipe for each logs block if I add a recipe that can take all logs present in the tag, it will produce for every logs the same stripped logs.
Isn't at me to add the compatibility for others mods, because they can name their stripped version how they want for the block, so ask for mods developer to add compatibility with cutting board.
I'm currently working on a solution that can dynamically adds recipes for all logs block in common logs tag, but this is not my priority.
Btw, it's a duplicate from another issue, use the new one to see the advancement of the feature #149.


useOverlayPosition: wrong positioning when page is zoomed

🐛 Bug Report
To reproduce this bug simply open the docs (https://react-spectrum.adobe.com/react-aria/usePopover.html#placement), click on the trigger which shows start-positioned popup and zoom the page
🤔 Expected Behavior
Popup stays at the same place where it was when page is not zoomed
😯 Current Behavior

🌍 Your Environment

Software
Version(s)

react-spectrum

Browser
Yandex Browser, based on Chromium 110.0.5481.2318 (x86_64)

Operating System
macOS Version 13.1 (Build 22C65)

I can't seem to reproduce when zooming in/out with CMD+/- on the latest version of the Yandex browser, what were your exact steps to reproduce?

Have you tried with zoom gesture using touchpad?

Ah I see, thank you. This is a duplicate of https://github.com/adobe/react-spectrum/issues/2700 then, going to close this out in favor of that one.


Where oh where has my little List Feature gone?

from the About Lists page:
Enhanced view filter for lists
You can use Table Permissions if you want to secure records, but if you want to simply provide a filter as part of the set of filter options that is relevant to the current portal user, you can use the List feature.
Where is the List feature?  What is it?
the doc goes on to show and example of some sort, how does one get to that?  these are the things that would be HELPFUL.
PLEASE BE EXPLICIT, OVERT, DIRECT
[Enter feedback here]

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

ID: 5eb3ed13-9665-518f-7cc5-eec5e279708f
Version Independent ID: 8a7aefa4-b9e0-ef52-7832-83c23cc790b1
Content: About lists - Power Apps
Content Source: powerapps-docs/maker/portals/configure/entity-lists.md
Service: powerapps
Sub-service: portals
GitHub Login: @sandhangitmsft
Microsoft Alias: sandhan

Thank you for bringing this to our attention. We have updated the doc to address this issue and hopefully it will be clearer to how the feature works and how to implement it.

Congratulations on your new job Mr Doleman!
Thanks for the update.
Sent from Yahoo Mail on Android
On Fri, Jan 7, 2022 at 9:44 AM, @.***> wrote:
Thank you for bringing this to our attention. We have updated the doc to address this issue and hopefully it will be clearer to how the feature works and how to implement it.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications on the go with GitHub Mobile for iOS or Android.
You are receiving this because you authored the thread.Message ID: @.***>


Images not loaded first time app runs

Describe the bug
When app is run for the first time, images on select theme page are not loaded
To Reproduce
Steps to reproduce the behavior:

Run app for the first time
Go to select theme page
Images are not loaded

Expected behavior
Images should load
Screenshots

Desktop (please complete the following information):

Windows

Fixed


Inject formly-form content inside a wrapper

I'm submitting a ...  (check one with "x")
[ ] bug report => search github for a similar issue or PR before submitting
[X] feature request
[X] support request

Current behavior
When I open the code (formly.form.ts), I see that the content is display below the wrapper:
    <formly-field *ngFor="let field of fields"
      [model]="fieldModel(field)" [form]="form"
      [field]="field" (modelChange)="changeModel($event)"
      [ngClass]="field.className"
      [options]="options">
    </formly-field>
    <ng-content></ng-content>

Expected behavior
I there a way to inject this content inside the wrapper ?
Minimal reproduction of the problem with instructions
To be more clear, I created a card wrapper (like tour panel wrapper in your demo) but I would like to display the submit button in the mat-card-actions:
My Wrapper:
@Component({
  selector: 'app-card-wrapper',
  template: `
    <mat-card>
      <mat-card-content>
        <ng-container #fieldComponent></ng-container>
      </mat-card-content>
      <mat-card-actions align="end">
        <!-- DISPLAY THE BUTTON HERE -->
      </mat-card-actions>
    </mat-card>
  `,
})
export class FormlyCardWrapperComponent extends FieldWrapper {
  @ViewChild('fieldComponent', { read: ViewContainerRef }) fieldComponent: ViewContainerRef;
}

My Form:
    <form class="formly" role="form" novalidate [formGroup]="form" (ngSubmit)="submit(model)">
      <formly-form [model]="model" [fields]="fields">
          <button type="submit" class="btn btn-default">Submit</button>
      </formly-form>
    </form>

Angular version: 5.0.0
Formly: 2.0.0-beta.2

see the example: https://stackblitz.com/edit/angular-y1lhbz
I used cdk portal to achieve your use-case

Thx ! I should start to learn this new cdk stuff ;)


7.x version is not working in bundlephobia

<EMAIL_ADDRESS>
MinifyError
We could not minify one of the source files in this package or its dependencies. Please verify if the contents of 0 can be minified using terser.

Stacktrace
{ "name": "SyntaxError", "message": "Unexpected token: keyword (export)", "filename": "0", "line": 1, "col": 13941, "pos": 13941 }

While previous major is working fine<EMAIL_ADDRESS>

Yeah dunno what the issue is, they don’t really give any useful feedback

Hmm sounds like they aren’t parsing the package.json bundling flags well and are assuming cjs