Why do non-cacheable blobs fail?

Hi,
I'm part of the CF Bits-Service team. We're implementing a local blobstore that replaces the one in CC. We noticed that blob responses must contain either an ETag or Last-Modified header, otherwise the Executor won't accept it, because the CachedDownloader treats it as NotCacheable and Executor treats that as non-recoverable error.
Is there a specific reason why non-cacheable blobs fail? If so, could you please explain?
We can add this header, but it came with a big surprise and was also very hard to track down, because from the error message
{"timestamp":"1524044759.316318274","source":"rep","message":"rep.executing-container-operation.task-processor.run-container.containerstore-create.node-create.failed-fetching-cache-dependency","log_level":2,"data":{"cache-key":"91fd...2288","container-guid":"b95....59","container-state":"reserved","download-url":"https://bits-service.service.cf.internal/buildpacks/91f....b46e2288","error":"Not cacheable directory","guid":"b9516b72-5b31-460d-bc34-2d9af6437759","session":"<IP_ADDRESS>.1"}}
it's not obvious what's wrong.
Any thoughts are appreciated.
Thanks,
Peter and the Bits team
/cc @suhlig @idev4u @smoser-ibm @eric-cartman

For context, this change/feature was introduced in #108774976 and the acceptance criteria is very explicit about the behavior. The ETag is required in order to invalidate the cached data (based on the story description). Note this is only the case when the FetchAsDirectory is called. That said, we could do something similar to Fetch to allow users of the cacheddownloader to download a directory temporarily. I'll let @emalm comment on this idea and the original acceptance criteria of the story mentioned above.
@petergtz what exactly is the use case for this ? ETag and Last-Modified are critical to the operation of the cacheddownloader. It allows multiple containers to share those assets while making it possible to invalidate the data when it change. As I mentioned before, we could modify FetchAsDirectory to allow this use case, but I would be interested in justifying that change.

@jvshahid Thanks for getting back to me on this and sharing your thougths and the context of this feature.
First, please note that we did implement caching in our implementation since I asked my questions above, and hence made it compatible with the cacheddownloader. All of the below is for me to better understand why things are the way they are.

ETag and Last-Modified are critical to the operation of the cacheddownloader.

This is clear. My question about it is not so much how, but rather why must artifacts used by the Executor be cacheable? While this is a very much desirable feature, it seems to be a performance optimization. But why is it required then? The executor could accept non-cacheable blobs and spit out a warning or info in the log.
My other comment was about the error reporting around this cacheability. "Not cacheable directory" is not very instructive in telling me that an ETag or Last-Modified header is missing. An error message like "Not cacheable directory. ETag and Last-Modified header missing in HTTP response" would have helped a lot in tracking down what's wrong.

@jvshahid

...
That said, I don't see an argument to change this behavior.

Sure. Make sense.

would changing the error message be sufficient to address this github issue ?

That would be awesome, yes (in the interest of anyone stumbling up on this in the future).
I could imagine that the error in the log should say something similar to the following, instead of just Not cacheable directory:

Not cacheable directory (no ETag and no Last-Modified header was found in response)
Not cacheable directory (cache key is missing)

Separating those 2 error conditions and describing them in that detail would point immediately to the issue.
Thanks


Update zio-sbt-website to 0.2.6

Updates dev.zio:zio-sbt-website from 0.2.0 to 0.2.6.
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "dev.zio", artifactId = "zio-sbt-website" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "@monthly" },
  dependency = { groupId = "dev.zio", artifactId = "zio-sbt-website" }
}]

labels: sbt-plugin-update, early-semver-minor, semver-spec-patch, commit-count:1

Superseded by #297.


Pending status hides payment details

Once I click on "payment" on my personal profile page, the payment details are shown to me.
If I close the browser window and then open the page again, I see the status "pending" but can't see the payment details anymore.

Done!


Ability to run a Reproducible Build comparison Jenkins job to Verify two builds are identical

This is the top epic which should include works for different OS:

Linux: https://github.com/adoptium/ci-jenkins-pipelines/issues/301
Windows: https://github.com/adoptium/ci-jenkins-pipelines/issues/398
MacOs: https://github.com/adoptium/ci-jenkins-pipelines/issues/399

Description for this epic:
To create Jenkins job which does comparision work for the compressed file we create after build.
read https://github.com/adoptium/ci-jenkins-pipelines/issues/301 for more discussion

@andrew-m-leonard
job https://ci.adoptopenjdk.net/view/ReproducibleBuild/job/reproducible_comparision is result from #301
from run result https://ci.adoptopenjdk.net/view/ReproducibleBuild/job/reproducible_comparision/2/console , expect it shows these two tar file of linux x64 are identical (same scm_ref from jdk17, same build_ref from temurin-build, can check detail sbom.json from GH release artifacts), but it says files are not the same.
Offline download these 2 tar files into folder first and second, and did a comparison on each's jdk-17.0.5+7/bin/jar
used different tools to verify result
>cmp first/jdk-17.0.5+7/bin/jar second/jdk-17.0.5+7/bin/jar
first/jdk-17.0.5+7/bin/jar second/jdk-17.0.5+7/bin/jar differ: byte 8295, line 4

>xxd second/jdk-17.0.5+7/bin/jar > second.txt
>xxd first/jdk-17.0.5+7/bin/jar > first.txt
>diff second.txt first.txt
519c519
< 00002060: 3032 3231 3030 3432 3330 3500 2d4a 2d6d<PHONE_NUMBER>5.-J-m
---
> 00002060: 3032 3231 3030 3530 3732 3900 2d4a 2d6d<PHONE_NUMBER>9.-J-m

ah, I might know the reason. the build has --with-source-data=updated.

https://ci.adoptopenjdk.net/view/ReproducibleBuild/job/reproducible_comparision/5/console is from two tar files both from weekly-build and same scm_ref
diff -q -r url1Dir1 url1Dir2
Files url1Dir1/jdk-17.0.5+7/lib/server/classes.jsa and url1Dir2/jdk-17.0.5+7/lib/server/classes.jsa differ
Files url1Dir1/jdk-17.0.5+7/lib/server/classes_nocoops.jsa and url1Dir2/jdk-17.0.5+7/lib/server/classes_nocoops.jsa differ
Files url1Dir1/jdk-17.0.5+7/release and url1Dir2/jdk-17.0.5+7/release differ

Think  we need to exclude release file in comparison and check why the other two are different

@zdtsw classes_nocoops.jsa is a known non-deterministic issue at the moment.

@zdtsw classes_nocoops.jsa is a known non-deterministic issue at the moment.

:+1: then it should be in the exclude list as the "release" one

@zdtsw classes_nocoops.jsa is a known non-deterministic issue at the moment.

should be classes.jsa be the same case as classes_nocoops.jsa?

So classes.jsa should be determinstic, so it's probably different because of some other difference, what are all your differences?

what is difference in release file?

@zdtsw so the JAVA_VERSION_DATE is always set to the release date, so that's fine
The above was built with different temurin-build SHAs, try with same

@zdtsw so the JAVA_VERSION_DATE is always set to the release date, so that's fine The above was built with different temurin-build SHAs, try with same

Ok I see. the "future date" is pre-set for the next CPU release date. that makes sense.
not really sure how could these two ended with 8 and 7 bits of SHA1
first: https://ci.adoptopenjdk.net/job/build-scripts/job/jobs/job/jdk17u/job/jdk17u-linux-x64-temurin/153/consoleFull
"buildRef": "https://github.com/adoptium/temurin-build/commit/8e043e36",
second: https://ci.adoptopenjdk.net/job/build-scripts/job/jobs/job/jdk17u/job/jdk17u-linux-x64-temurin/161/consoleFull
 "buildRef": "https://github.com/adoptium/temurin-build/commit/8e043e3",
Update:
think i know the reason......
Set the length object names are abbreviated to. If unspecified or set to "auto", an appropriate value is computed based on the approximate number of packed objects in your repository, which hopefully is enough for abbreviated object names to stay unique for some time. The minimum length is 4.
we do not specific set core.abbrev so it can be a different on each run.
good if we  can lock the number of return
https://github.com/zdtsw/temurin-build/blob/master/sbin/build.sh#L1621
https://github.com/zdtsw/temurin-build/blob/master/sbin/build.sh#L1750
https://github.com/zdtsw/temurin-build/blob/master/sbin/build.sh#L1760
to something like git rev-parse --short=10 --verify HEAD so we can be sure we always get 10 digits

One problem is, we only produce reproducible build from

weekly build
official release.

And we only keep 2 batches of artifacts from weekly and we do not publish weekly build result to binary repo for longer time.
So the chance to get two URL’s that I can download and get a positive result is, e.g I build release on 18th Oct, then I wait till 23/24th Oct to get one from weekly (assume nobody pushed any new code into upstream repo, so the gitsha is the same)
Today, it is 9th Nov, the build from 23/24 Oct is gone, the new ones generated from 05/06 Nov and 29/30 Oct,
either with different gitsha (diff from RELEASE)
or something failed and not get archived in weekly
or already create a new version, e.g: jdk-20+21 vs jdk-20+22
=> hard to get test objects (jdk tarballs)  even we have the test tool (job) ready


State is tightly coupled with CSS class names

I spent a bit of time trying to get this to work for my use case, but everything is so tightly coupled that it's very difficult to comprehend what influences what.
    targetClassName = e.target.className,
    direction = targetClassName.match(/(\w+)Number/)[1],
    otherDirection = this.getOtherDirection(direction),
// [...]
    var otherNumber = otherDirection + "Number";
    stateObject[otherNumber] = this.state[otherNumber];

The above only works if the events are triggered by DOM elements with the right class, and wouldn't have passed code review where I work.

That is indeed terrible code.

@vcarl Would you be interested in providing a PR to unsuss the CSS class names?

I started to, but it would really be a fundamental rewrite. And I disagree with a lot of the prop names, so it'd be a completely different component if I made the changes I felt necessary for me to use it in my code. I'm going with mpowaga/react-slider instead because I really just need a functional slider to implement a feature at work.

Alright then, closing this. Feel free to revisit in the future if you have time.


Update metadata.textproto for drained_configuration_convergence

Added these deviations after modifications to the internal/setup.go files that apply to both full_configuration_replace and drained_configuration_convergence.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 46.627%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
1341

Relevant Lines:
2876

💛  - Coveralls


[BUG] errors in sample templates

What is the bug?
I've found the sample samples in file https://github.com/opensearch-project/flow-framework/blob/main/sample-templates/alert-summary-agent-claude-tested.json is wrong.
How can one reproduce the bug?
Provision resources with this template. Then, I call predict on the created claude model. I will then meet with the following error:
{
  "error": {
    "root_cause": [
      {
        "type": "status_exception",
        "reason": "Error from remote service: {\"message\":\"prompt must start with \\\"\\n\\nHuman:\\\" turn after an optional system prompt\"}"
      }
    ],
    "type": "status_exception",
    "reason": "Error from remote service: {\"message\":\"prompt must start with \\\"\\n\\nHuman:\\\" turn after an optional system prompt\"}"
  },
  "status": 400
}

What is the expected behavior?
Both the created agent and claude model should work
What is your host/environment?
Linux. OpenSearch 2.18.
Do you have any screenshots?

Do you have any additional context?
Need to check other templates to see whether there are any errors.

May also need to check other dashboard assistant agents.

https://github.com/opensearch-project/flow-framework/pull/873
@qianheng-aws can you please investigate?

#873
@qianheng-aws can you please investigate?

We need to add \n\nHuman: at the beginning of the prompt for model claude v1. Fixed by this PR: https://github.com/opensearch-project/flow-framework/pull/958

Find out that anomaly-detector-suggestion-agent-claude.json also has the same error. @gaobinlong can you update the prompt like https://github.com/opensearch-project/flow-framework/blob/b32f98bedfbab1c19c225845737c72489789f956/sample-templates/alert-summary-log-pattern-agent.json#L29?

Also needs these 2 PRs:

https://github.com/opensearch-project/flow-framework/pull/959
https://github.com/opensearch-project/flow-framework/pull/936


[HOLD for after Agent Freeze] Support e2e testing for SNMP Network Devices Metadata

What does this PR do?
Support e2e testing for SNMP - Network Devices Metadata
Motivation

Useful for testing SNMP Devices metadata
Useful for testing profile based metadata https://github.com/DataDog/datadog-agent/pull/9679

Additional Notes
Review checklist (to be filled by reviewers)

[ ] Feature or bugfix MUST have appropriate tests (unit, integration, e2e)
[ ] PR title must be written as a CHANGELOG entry (see why)
[ ] Files changes must correspond to the primary purpose of the PR as described in the title (small unrelated changes should have their own PR)
[ ] PR must have changelog/ and integration/ labels attached

Superseded by https://github.com/DataDog/integrations-core/pull/10663 and https://github.com/DataDog/integrations-core/pull/10664


docs(releasing): Document release steps for admins

@johnjbarton Something is wrong with commit message, would be nice if you investigate

I guess that github + travis have some problem about the meaning of the SHA for the commit that gets tested.


Swan Song - Add Recommended items

Please add these to the recommended item list:

1 x Draynor Village teleport (Amulet of Glory)
2 x Piscatoris teleport
1 x Yanille teleport (Nightmare Zone minigame teleport or Watchtower teleport)
1 x Crafting guild teleport (Skills Necklace)
1 x Cooking gauntlets (to reduce the chance of burning the 5 Monkfish caught during the quest)

Used in these sections:
Starting off

1 x Piscatoris teleport
1 x Draynor Village teleport (Amulet of Glory)

Entering the colony

1 x Piscatoris teleport

Helping Arnold

1 x Cooking gauntlets (to reduce the chance of burning the 5 Monkfish caught during the quest)

Making an army

1 x Yanille teleport (Nightmare Zone minigame teleport or Watchtower teleport)
1 x Crafting guild teleport (Skills Necklace)

I also noticed I need a brown apron to enter the crafting guild, so that should probably be in the requirements as well. (in the "Making an Army" step)

Thanks for the breakdown, made it a lot easier to implement 😄


new wrap: chipmunk

I've created a warp and meson.build for https://github.com/slembcke/Chipmunk2D. While it's named Chipmunk2D there, I think the name should be chipmunk, as Fedora calls its package chipmunk-devel for example. I couldn't find a pkg-config file.

They call the project chipmunk https://github.com/slembcke/Chipmunk2D/blob/master/CMakeLists.txt#L3
So this looks reasonable for me.
https://github.com/mesonbuild/chipmunk/tree/7.0.2 is up

Can you create the branch 6.2.2? Version 7 still hasn't implemented some features I need.

Done.


Replace TCPConnect with a custom channel

Is your feature request related to a problem? Please describe.
I have a P2P channel (It has the functionality of TCP)  and want to replace TCPConnect with it.
Describe the solution you'd like
typedef int (*pTCPConnect)(rdpContext* context, rdpSettings* settings, const char* hostname,
	                           int port, DWORD timeout);
typedef BOOL (*pTransportAttach)(rdpTransport* transport, int sockfd);

This function binds sockfd, which does not represent a custom channel.
I want to replace int sockfd with void* pTcpChannel:
typedef void* (*pTCPConnect)(rdpContext* context, rdpSettings* settings, const char* hostname,
	                           int port, DWORD timeout);
typedef BOOL (*pTransportAttach)(rdpTransport* transport, pTcpChannel);

Already available, just write your own transport.
If you do not use sockets of any kind you can also pass in and cast any data that fits the int.
if that is not good enough, there is fmemopen, fileno and dup to have a in memory file that can pass any data you want.

Fmemopen, Fileno and DUP are not available on all systems.

but sockets are, this was just (one) example of how to use that.


Installation instructions (binary/mac) incomplete

I tried installing CockroachDB on a clean mac, and the installation broke because of a missing /usr/local/bin/ directory.
Environment

Macbook Air (Retina, 13-inch, 2018)
MacOS 10.14.6 (Mojave)

Steps to reproduce

Wipe the mac & started from scratch.
Go to our installation page for installing the binary.
Perform the curl command to get the binary (for me it was curl https://binaries.cockroachdb.com/cockroach-v20.2.2.darwin-10.9-amd64.tgz | tar -xJ).
Attempt to copy the binary to usr/local/bin/ with the provided command (for me it was cp -i cockroach-v20.2.2.darwin-10.9-amd64/cockroach /usr/local/bin/).

Expected result
Binary gets copied there, or maybe it gives me a permission error & it copies with sudo
Actual result
$ cp -i cockroach-v20.2.2.darwin-10.9-amd64/cockroach /usr/local/bin/
cp: directory /usr/local/bin does not exist
$

Possible solution
Add a step for sudo mkdir /usr/local/bin in the instructions, and change the cp command to sudo cp.

@taroface, @piyush-singh, this feels like something we should prioritize, given it concerns the installation workflow.

From @bdarnell:

between this and the geo libraries our "simple single binary" isn't so simple anymore. i think we should steer mac users to brew and leave the tarball as an advanced use case
personally i wouldn't install from the tarball into /usr/local; i'd put it somewhere else and add that directory to my $PATH
and for users for whom that is sufficient instruction, it works great. but if you want to provide more hand-holding, it gets complicated fast because of all the shell init files and the fact that macos switched from bash to zsh by default recently


Add SwissDLT

Website
https://explorer.swissdlt.ch
https://bcts.ch
ChainId
94
RPC
https://rpc.swissdlt.ch

I cannot find your network in https://chainlist.org/

The PR is already merged: https://github.com/ethereum-lists/chains/pull/2842
I don't know how often it Chainlist gets updated.

Ok, done! https://github.com/safe-global/safe-singleton-factory/pull/164

Thanks! Deployed: https://explorer.swissdlt.ch/tx/0xce02dafae2b15ba0e005a973d5ecaee82605815ddbdd31ace392ebbc54008219


PIP package missing Cython dependency

The package doesn't list Cython as a dependency. This breaks and prevents installation on a bare virtualenv, which fails with the error:
ModuleNotFoundError: No module named 'Cython'

The solution is to simply first run:
pip install Cython

but ideally the package should list Cython as a dependency so this will be done automatically.

The pyproject.toml lists Cython as a dependency https://github.com/ethanhs/pynanosvg/blob/master/pyproject.toml#L2
So I believe if you have a new enough pip, it should work.
The problem is declaring Cython as a dependency isn't enough, because the setup script needs to import Cython https://github.com/ethanhs/pynanosvg/blob/master/setup.py#L2
Also, fair warning: I don't plan on spending much more time on this project, especially since nanosvg is no longer actively maintained. I will review PRs if this project, but don't expect work from me on it, I have decided to focus on other projects.
I would be happy to take a PR that warns people should upgrade pip if the Cython import fails.

That's interesting. I get this error in a Docker build that uses an ubuntu:18.04 image, but now that you mention it, I can't reproduce it on my normal Ubuntu 18.04 dev system. Even if I completely purge the global Cython package, pip is still able to install pynanosvg correctly in a virtualenv. It might just be isolated to Docker.

The pip that ships with Python 3 in Ubuntu 18.04 is too old. My guess is that your dev system has an upgraded pip, which supports installing the pyproject.toml specified dependencies. Also out of curiosity, what project is this for (if its open source).

Yeah, but I always install Python 3.7 or 3.8 in my Docker builds for just that reason. The build it failed for was using Python 3.7.7, and that should be recent enough.


Check if we should implement Pages & Attributes for OutputBuiltinRunner

The cairo-lang implementation of OutputBuiltinRunner contains the pages and attributes fields, which are created via the add_page & add_attribute methods. These methods are not used during normal execution and are only used by os hints. While running os hints is outside the scope of the vm these methods would be needed for an OsSyscallHintProcessor to implement those hints. The data on these fields is also used when creating a cairo pie.
Adding this behaviour would entail:

Creating the pages and attributes fields in the OutputBuiltinRunner
Implementing the methods add_page & add_attribute for OutputBuiltinRunner
Implementing OutputBuiltinRunner.finalize_segments (This would add the logic of pages and attributes on top of the common builtin segment finalization)

I would suggest converting the BuiltinRunner back into a trait. It was my mistake to think converting to enum was the only way to make it Sync + Send at the time due to lack of knowledge at the time.
If we make it a trait, I think we can simply handle it as a different builtin in SiR with its own extra methods/fields that the OsSyscallHintProcessor will know about and use.
Does this make sense to you?

I don't think adding an alternative output builtin is a good solution. These fields are part of the original `OutputBuiltinRunner', we just didn't implement them because they weren't used. This would be a small extension of the builtin's functionality, not a breaking change in the builtin's behaviour, so it doesn't really merit possibly braking changes in how the runner interprets builtins (as this is currently a closed behaviour, not something extensible).

Implemented by #1580


Bump Pixelmon 8.3.8

Add Pokemon Wyrdeer to Species
Add husuian form for Pokemon Growlithe and Braviary

Bump Pixelmon 8.3.8

Add hisuian form for additional Pokemon Arcanine, Voltorb, and Electrode


Linux (And AMD CPU) measurement

On a Debian-based GNU Linux Distribution, rework the energy tool used in measurer.py to use something that functions with linux and AMD hardware. Ideally, output data in the same normalized way so that data analysis scripts do not need to be changed.

not doing this ☠


[BUG] Output folder is empty

API-Mgr. CLI version

Please make sure to use the latest available version before reporting a bug.

API-Manager and Service-Pack Version
7.6.2, SP3
Expected behavior
Should be able to export the api;s.
Actual behavior
target folder is empty,
Log-Output in Debug
target folder is empty,
Test case sample

Please describe the steps you have done to replicate the issue
I am able to see the exported API's on the terminal, but the target folder is empty after running this command : apim api get -s dev --output json -t C:/axway/apis

Hi @kunwardhwaj, Do you see any log output?
What happens if you try to export just on the console by using no output option at all?

Looks like it doesn’t realize the output format. Can you please try with -o json?
When the output format is detected successfully, it doesn’t print the console table anymore. Hence, in your case the output format is not detected.

Hi @cwiechmann ,
I tried apim api get -s dev -o json -t C:/axway/apis, but it's still empty.
I prints the details on the terminal though.

And you are using version 1.1.0?
In version 1.0.0 and 1.0.1 the parameter was named -f or —format, which I have changed to -o or —output be aligned with the AMPLIFY CLI.

yes, I am using version 1.0.1 Below is the output from my local dev API Manager:
**λ apim api get -s local -o json -t C:/axway/apis
API-Manager CLI: 1.0.1
To report issues or get help, please visit:
https://github.com/Axway-API-Management-Plus/apim-cli
Module: API - E X P O R T / U T I L S (1.0.1)
1426   INFO     APIManagerAdapter| Successfully connected to API-Manager (7.6.2 SP3) on: https://localhost:8075
1771   INFO          APIExportApp| 2 API(s) selected.
+--------------------------------------+-----------------------+-----------------------------+---------+
| API-Id                               | Path                  | Name                        | Version |
+--------------------------------------+-----------------------+-----------------------------+---------+
| 4d226e01-5444-420f-8f27-120efc1f8b8c | /api                  | Wisercare_Inbound_API       |     1.0 |
| 287e2508-a24f-4e92-9a6a-7d30c236cbd8 | /v2                   | petstore swagger.json       |   1.0.5 |
+--------------------------------------+-----------------------+-----------------------------+---------+**

That is the problem. Please download the latest version 1.1.0 and then use the parameter: -o or —output

Perhaps a good idea to watch the repository and select the option to get notified for new releases.

Thanks! That fixed the issue!


[MINOR] Fixing CTAS configuration not propagated properly

Change Logs
This change addresses issue of CTAS erroneously performing de-duplication, due to the fact that

It reuses InsenrtIntoHoodieTableCommand infrastructure to insert the data
It provides an extra-options overriding default configs (tuned for Insert Into statement) specifically for CTAS
Extra options not being merged into the final config (at some point after 0.12.2), resulted into it by default doing de-duplication

Impact
Disables de-duplication for CTAS by default, makes sure CTAS specific properties are properly propagated.
Risk level (write none, low medium or high below)
Low
Documentation Update
N/A
Contributor's checklist

[ ] Read through contributor's guide
[ ] Change Logs and Impact were stated clearly
[ ] Adequate tests were added if applicable
[ ] CI passed

TestHoodieDeltaStreamer.testHoodieAsyncClusteringJobWithScheduleAndExecute is extremely flaky.
Tried to run it locally, and it passes but also occasionally flakes out.
https://dev.azure.com/apache-hudi-ci-org/apache-hudi-ci/_build/results?buildId=14883&view=logs&j=0f02b992-1348-53f9-d191-b680ba8cdc58&t=b1b72248-7c8f-502f-b211-fbf8269f9ee6


#165 - Duplicate operationId in swagger doc

Assign unique operationIds for get summary result and get detailed obfuscated result endpoints

Very minor change in documentation. Merging without review by anyone else.


Analysis and Design document for CRUD Bucket operation

Issue/Feature Description:
Prepare Analysis and Design document for Create , Update , Delete Operation of buckets for AWS , Azure, GCP Clouds .
Why this issue to fixed / feature is needed(give scenarios or use cases):
Needed to support YJP use-cases of bucket creation and tiering placement of bucket.
How to reproduce, in case of a bug:
N/A
Other Notes /  Environment Information: (Please give the env information, log link or any useful information for this issue)

Completed in I Release


Need to manually install numpydoc -- version 0.2.1

🐛 Bug
Not sure if you are aware but after updating napari to version 0.2.1, I had to manually install numpydoc, which I didn't need before.
To Reproduce
Not have numpydoc installed

@bioimage-analysis do you mean nothing works at all without numpydoc installed? Could you post the full traceback? Thanks!

Well, I just tried it on a different env, I upgraded napari from 0.2.0 to 0.2.1 on that environment and here is the error message I get when I tried to import napari:
import napari Traceback (most recent call last):   File "<stdin>", line 1, in <module>   File "/Applications/anaconda3/envs/chloe/lib/python3.7/site-packages/napari/__init__.py", line 29, in <module>     from .viewer import Viewer   File "/Applications/anaconda3/envs/chloe/lib/python3.7/site-packages/napari/viewer.py", line 1, in <module>     from ._qt.qt_viewer import QtViewer   File "/Applications/anaconda3/envs/chloe/lib/python3.7/site-packages/napari/_qt/qt_viewer.py", line 24, in <module>     from .qt_dims import QtDims   File "/Applications/anaconda3/envs/chloe/lib/python3.7/site-packages/napari/_qt/qt_dims.py", line 5, in <module>     from ..components.dims import Dims   File "/Applications/anaconda3/envs/chloe/lib/python3.7/site-packages/napari/components/__init__.py", line 16, in <module>     from .dims import Dims   File "/Applications/anaconda3/envs/chloe/lib/python3.7/site-packages/napari/components/dims.py", line 6, in <module>     from ..util.event import EmitterGroup   File "/Applications/anaconda3/envs/chloe/lib/python3.7/site-packages/napari/util/__init__.py", line 1, in <module>     from .misc import is_rgb, segment_normal   File "/Applications/anaconda3/envs/chloe/lib/python3.7/site-packages/napari/util/misc.py", line 8, in <module>     from numpydoc.docscrape import FunctionDoc ModuleNotFoundError: No module named 'numpydoc'

experienced same with conda env py3.7 on mac osx mojave

Ah, got it. This was added in #583, but we missed it because numpydoc was in our test dependencies rather than default! Fix in #598.


[Gally]: master <- dev

Automatically created by Git-Ally

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Lazy does not instantiate type parameters

From my testing, Lazy does not work if more than a single type parameter is involved. I have only tested two myself.
import shapeless._

object LazyTest {

  new FindSimpleFooer[Int].find
  new FindLazySimpleFooer[Int].find
  new FindFooer[Int].find
  new FindLazyFooer[Int].find
}

class FindSimpleFooer[Tpe] {
  def find(implicit fooer: SimpleFooer[Tpe]) = fooer
}

class FindLazySimpleFooer[Tpe] {
  def find(implicit fooer: Lazy[SimpleFooer[Tpe]]) = fooer
}

class FindFooer[Tpe] {
  def find[F <: Foo](implicit fooer: Fooer[Tpe, F]) = fooer
}

class FindLazyFooer[Tpe] {
  def find[F <: Foo](implicit fooer: Lazy[Fooer[Tpe, F]]) = fooer
}

trait Foo
case class BarFoo(i: Int) extends Foo

trait SimpleFooer[Tpe] {
  def makeFoo(obj: Tpe): Foo
}
object SimpleFooer {
  implicit val barFooer: SimpleFooer[Int] = (obj: Int) => BarFoo(obj)
}

trait Fooer[Tpe, FooTpe <: Foo] {
  def makeFoo(obj: Tpe): FooTpe
}
object Fooer {
  implicit val barFooer: Fooer[Int, BarFoo] = (obj: Int) => BarFoo(obj)
}

Lazy can't know what is F - it's probably Nothing

It works fine when Lazy is not present though. Only the last one of the four above fails.

I meant that the problem is F <: Foo and not that there are two type parameters.

That bound is clearly needed as that's the bound of Fooer. Even if you remove that bound though, it still fails.

Yeah the reason is that Lazy is using a macro and inside we explicitly ask the compiler to infer an implicit with that type, but that doesn't correspond exactly to what the compiler is doing. So we ask to infer Fooer[Tpe, F] where F is the type parameter and instead we should try to substitute it with a wildcard and ask for Fooer[Tpe, ? <: Foo]. I have a WIP for a fix, let's see if we can make it work.

We had to revert the fix, because it breaks kittens


Error during loading of pretrained model

Guys. I am trying to load following pretrained model "icefall-asr-librispeech-pruned-transducer-stateless8-2022-12-02"
For some reason during loading of bpe.model I get following error. Could you help please:
(base) root@ca3678a00d7e:/fsx_new/Alex/tmp2/s8/icefall-asr-librispeech-pruned-transducer-stateless3-2022-05-13/data/lang_bpe_500# python
Python 3.8.15 (default, Nov 24 2022, 15:19:38)
[GCC 11.2.0] :: Anaconda, Inc. on linux
Type "help", "copyright", "credits" or "license" for more information.

import sentencepiece as spm
sp = spm.SentencePieceProcessor()
sp.load("bpe.model")
Traceback (most recent call last):
File "", line 1, in
File "/opt/conda/lib/python3.8/site-packages/sentencepiece/init.py", line 905, in Load
return self.LoadFromFile(model_file)
File "/opt/conda/lib/python3.8/site-packages/sentencepiece/init.py", line 310, in LoadFromFile
return _sentencepiece.SentencePieceProcessor_LoadFromFile(self, arg)
RuntimeError: Internal: src/sentencepiece_processor.cc(1101) [model_proto->ParseFromArray(serialized.data(), serialized.size())]

cd icefall-asr-librispeech-pruned-transducer-stateless8-2022-12-02

git lfs pull --include "data/lang_bpe_500/bpe.model"

git lfs pull --include "exp/pretrained.pt"

We don't use bpe.model and pretrained.pt in sherpa, that is why the doc in sherpa does not mention the downloading of bpe.model and pretrained.pt.
Before using git lfs pull, please run
cd icefall-asr-librispeech-pruned-transducer-stateless8-2022-12-02

ls -lh data/lang_bpe_500
ls -lh exp

You will find that the file size of bpe.model and pretrained.pt is several hundred **bytes``, which
indicates you have not used git lfs to download them.

You can also just "right click -> copy link address" on the "download" link on the model's HF page, e.g.,

and then use wget to download it.


Update README.md

Add unzip package for compose step, otherwise PHP Compose gives warning missing Unzip application into the system.
P.S.: Thanks for the great work on K8s-101!

Thanks for finding that! It's technically okay without it I think, but does make it a little faster.

Thanks for finding that! It's technically okay without it I think, but does make it a little faster.


[Awaiting Payment 29th April] [Wave Collect][QBO] Disabled toggle for Categories, Tags, and  Taxes accordingly depending on the accounting software connected

When the user connects to accounting software:

optimistically clear all existing categories, tags and taxes
prevent the user from turning off categories, tags and taxes features
prevent the user from deleting categories, tags and taxes imported from connecting accounting software
prevent the user from adding new categories, tags and taxes

I'll work on this during this week

Several PRs are needed to implement this. Removed the Reviewing and Daily labels.

Both PRs linked to this issue are deployed! 🎉

Added the bug label to get a BZ assigned.

Who needs paying here? Just @shubham1206agra for https://github.com/Expensify/App/pull/39874?

Yep!

@shubham1206agra offer is here: https://www.upwork.com/nx/wm/offer/102114555
Ping me on this issue once you've accepted.

Ah cool, thanks for letting me know. I went ahead and paid out $500. Thanks everyone!


Upgrade OS on self-hosted runners

Our GitHub runner runs Debian 10.

GCC 8.3.0's old linker blocks https://github.com/hermitcore/uhyve/pull/193.

Ubuntu 20.04's GCC 9.3.0 seems to work fine.

We'll discuss this in two weeks. We might have new hardware soon, making a software upgrade unnecessary.

Using lld on linux is not supported yet: https://github.com/rust-lang/rust/issues/39915#issuecomment-618726211

We are about to get new HW for the CI, then we can upgrade to Debian 11 for the runners. I don't think it is worth the effort to update the runners before.


avoid clashing with local babel config file

Seeing as you're calling transformAsync() with all the config that you want it's probably a good idea to pass configFile: false to prevent any interactions with local babel configs 👍

Hey 👋 any chance we could get this looked at and merged? Ember uses this as part of the blueprint infrastructure and we are working on a new blueprint that includes a babel config so a lot of people are going to be hit with this 🙈 If we could get this out in a patch release that would be super awesome


Refactor cut and copy event handlers

The cut event handler currently dispatches a copy and cut event. The copy is fired by reuse of the copy event handler and the data is removed from the grid before the cut event is dispatched. This is not in line with the W3C Clipboard API which reads:

In an editable context, if the event is not canceled the action will place the currently selected data on the system clipboard and remove the selection from the document. The cut event fires before the selected data is removed. When the cut operation is completed, the selection is collapsed.

This PR refactors the cut event handler to:

Move selected-cell-copy-logic to a utility function so it can be used in both cut and copy event handler.
Copy selected data to the clipboard but not dispatch a copy event.
(Re)-Dispatch  cut event before anything happens.
Clear selected data and then dispatch a customaftercut event with an array of affected cells (usable in calling application).
Add/enable tests for neat and untidy copy actions.

In #383 I added affectedCells to the cut event, this PR breaks this by introducing an aftercut event with those cells. I would think impact of this is very limited.
Here's a demo: https://3nvso.csb.app/

Very nice, thank you!


fix compile error on darwin

What this PR does / why we need it:
Special notes for your reviewer:
Does this PR introduce a user-facing change?

NONE

Codecov Report

Merging #1101 (80b34ec) into main (2aa97a9) will decrease coverage by 0.05%.
Report is 76 commits behind head on main.
The diff coverage is n/a.

:exclamation: Current head 80b34ec differs from pull request most recent head 62b61f9. Consider uploading reports for the commit 62b61f9 to get more accurate results

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
@@            Coverage Diff             @@
##             main    #1101      +/-   ##
==========================================
- Coverage   40.80%   40.75%   -0.05%
==========================================
  Files          24       24
  Lines        1642     1644       +2
==========================================
  Hits          670      670
- Misses        900      902       +2
  Partials       72       72

see 1 file with indirect coverage changes
:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


remove nlls from PeakStats

fixes issue #1263
Description
The nlls attribute in PeakStats is for a planned, undocumented, and unimplemented feature.  Since it has not been implemented, its presence invites questions from new users as to why nlls is defined in the results but always None.

The merged PR will not close the corresponding issue. Should be corrected such as fixes #1263. Otherwise looks good, thanks @prjemian!

Good catch!


Reduction of package size published on npm

Currently the published package size is 164M in disk:

I'm not sure what can be cleaned up right now, but it would be ideal to reduce that large size.

Using an online tool:
https://pkg-size.dev/@carbon%2Fweb-components


Error with Django 1.8.6

django.db.migrations.loader.BadMigrationError: Migrated app 'django_extensions' contains South migrations. Make sure all numbered South migrations are deleted prior to creating Django migrations.

please make sure you are running django-extensions version 1.5.9 or higher


noPropertyAccessFromIndexSignature=true causes compilation errors on  tags.

If tsconfig.json contains
{
  "compilerOptions": {
    "noPropertyAccessFromIndexSignature": true,
  }
}

Then any <slot/> tag anywhere in the <template> section causes typescript compilation errors:
test.vue:17:6 - error TS4111: Property 'slot' comes from an index signature, so it must be accessed with ['slot'].
17     <slot />
Reproducible in both vscode UI and via "vue-tsc --noEmit".

You are the God! Please live forever.


FireDb.hent_observationer_fra_opstillingspunkt udsteder SAWarning

Fx ved udtræk af observationer:
>fire niv udtræk-observationer regn --db=test K-01-09287 K-01-09288 K-01-07454 K-01-07780 K-01-07425
Klargør identer
Søg i databasen efter punkter til hver ident
Søg med punkterne som opstillingspunkt
c:\dev\fire\fire\api\firedb\hent.py:241: SAWarning: SELECT statement has a cartesian product between FROM element(s) "observation", "observationstype_1" and FROM element "koordinat_1".  Apply join condition(s) between each element to resolve.
  return query.all()
c:\dev\fire\fire\api\firedb\hent.py:241: SAWarning: SELECT statement has a cartesian product between FROM element(s) "koordinat_1" and FROM element "observation".  Apply join condition(s) between each element to resolve.
  return query.all()
Filtrér observationer
Indsaml opstillingspunkter fra observationer
Gem observationer og punkter i projekt-regnearket
K-01-09287
K-01-09288
K-01-07454
Check: Punktoversigt har alle punkter i Observationer[Fra]: Ja
Skriver til C:\dev\fire\sandkasse\regn.xlsx...
Gem punkter som .geojson-fil...
Skriver punkter til regn-2022-02-22T125842.geojson ...

Lader til at opstå som konsekvens af brugen af joinedload i opsætningen af observationsklassen (?): https://stackoverflow.com/questions/39277957/sqlalchemy-emitting-cross-join-for-no-reason

FireDb.hent_observationer_fra_opstillingspunkt() bygger en SQL forespørgsel op der ser ud som følger:
SELECT
    observation.value1 AS observation_value1,
    observation.value2 AS observation_value2,
    observation.value3 AS observation_value3,
    observation.value4 AS observation_value4,
    observation.value5 AS observation_value5,
    observation.value6 AS observation_value6,
    observation.value7 AS observation_value7,
    observation.registreringfra AS observation_registreringfra,
    observation.registreringtil AS observation_registreringtil,
    observation.objektid AS observation_objektid,
    observation.id AS observation_id,
    observation.value8 AS observation_value8,
    observation.value9 AS observation_value9,
    observation.value10 AS observation_value10,
    observation.value11 AS observation_value11,
    observation.value12 AS observation_value12,
    observation.value13 AS observation_value13,
    observation.value14 AS observation_value14,
    observation.value15 AS observation_value15,
    observation.sagseventfraid AS observation_sagseventfraid,
    observation.sagseventtilid AS observation_sagseventtilid,
    observation.observationstidspunkt AS observation_observationstidspunkt,
    observation.antal AS observation_antal,
    observation.gruppe AS observation_gruppe,
    observation.observationstypeid AS observation_observationstypeid,
    observation.sigtepunktid AS observation_sigtepunktid,
    observation.opstillingspunktid AS observation_opstillingspunktid,
    observationstype_1.observationstype AS observationstype_1_observationstype,
    observationstype_1.objektid AS observationstype_1_objektid,
    observationstype_1.observationstypeid AS observationstype_1_observationstypeid,
    observationstype_1.beskrivelse AS observationstype_1_beskrivelse,
    observationstype_1.value1 AS observationstype_1_value1,
    observationstype_1.value2 AS observationstype_1_value2,
    observationstype_1.value3 AS observationstype_1_value3,
    observationstype_1.value4 AS observationstype_1_value4,
    observationstype_1.value5 AS observationstype_1_value5,
    observationstype_1.value6 AS observationstype_1_value6,
    observationstype_1.value7 AS observationstype_1_value7,
    observationstype_1.value8 AS observationstype_1_value8,
    observationstype_1.value9 AS observationstype_1_value9,
    observationstype_1.value10 AS observationstype_1_value10,
    observationstype_1.value11 AS observationstype_1_value11,
    observationstype_1.value12 AS observationstype_1_value12,
    observationstype_1.value13 AS observationstype_1_value13,
    observationstype_1.value14 AS observationstype_1_value14,
    observationstype_1.value15 AS observationstype_1_value15,
    observationstype_1.sigtepunkt AS observationstype_1_sigtepunkt
FROM koordinat koordinat_1, observation
LEFT OUTER JOIN observationstype observationstype_1
    ON observationstype_1.observationstypeid = observation.observationstypeid
WHERE observation.opstillingspunktid = :opstillingspunktid_1
    AND observation.registreringtil IS NULL
    AND koordinat_1.sridid = :sridid_1
    AND observation.observationstypeid
    IN (__[POSTCOMPILE_observationstypeid_1])

Jeg gætter på at problemet er at der selectes fra to tabeller i samme ombæring: SELECT ... FROM koordinat koordinat_1, observationer .... Det bør måske nærmere være et join?


[W5][W10-3]Sun Yiqun

Adding a field company to person.

Good idea to give Persons more details like the company name.


[GSSoC'23] Recipe Finder Website

Describe the project you want to add with tech stack
Tech using - HTML, CSS and JS
Expected behavior

By fetch data from the Recipe API.
Show so many recipes of a single product
Also showcase the preparing methods on click

Screenshots (optional)

Additional context (optional )

@MohitGupta121 @pranjay-poddar @Saurabh-kumar09 sir, please assign this project to me


Inconsistence in material3 between Android vs Desktop (and iOS)

Describe the bug
There are inconsistence between platforms.
Affected platforms
Select one of the platforms below:

Desktop
iOS

Versions

Kotlin version*: 1.9.0
Compose Multiplatform version*: 1.4.3, 1.5.0-beta01
OS version(s)* (required for Desktop and iOS issues): MacOS 13.4.1, iOS 16 (But it's doesn't matter)
OS architecture (x86 or arm64): Arm64
JDK (for desktop issues): 17

To Reproduce
Minimal reproducible sample: https://github.com/dima-avdeev-jb/ios-android-inconsistent
Expected behavior
Android and Desktop (and iOS) should looks the same
Screenshots
Android

Desktop and iOS

Probably related: https://github.com/JetBrains/compose-multiplatform/issues/2383

@igordmn @dima-avdeev-jb
It's not related directly to m3. You can reproduce it with an m2 text if you set lineHeight to 24.sp (default m3 bodyLarge). m2 default text style just don't care about line height.
Look like there is a bug in skiko paragraph implementation.
Here is an example of weird behavior of skiko paragraph on desktop and android with Roboto font (m3 or m2 text, doesn't matter). Looks like android always trying to align text to the top, when line height is greater that text size. But skiko justifies it in a strange way: if lineHeight/fontSize < 2 it aligns to the top, otherwice to the bottom.
I guess the issue is somewhere on this line

textSize = 10.sp

lineHeight = 16.sp

textSize = 10.sp

lineHeight = 20.sp

textSize= 10.sp

lineHeight = 24.sp

Desktop

Android

Probably related: #1082

Worth to try Roboto (the default Android font) on Desktop/iOS. If it will look the same as in Android, then it is not a bug, but font-dependent behavior.

Yep, different font is one of the reasons. The second one is an assumption that
modifier = Modifier.fillMaxSize()
textAlign = TextAlign.Center,

will align the text vertically, but it's not (and should not). The proper way to do this is to add wrapContentHeight modifier:
.wrapContentHeight(
    align = Alignment.CenterVertically, // Default value
    unbounded = true // Makes sense if the size less then text
),

The initial sample with this modifier:

On Android Jetpack Compose before 1.6.0, there was a need to disable extra padding via includeFontPadding flag for proper centering. Now it's false by default. But that's android-only known "feature"
So, I'm closing this as not a bug. cc @dima-avdeev-jb

If line height is greater than font size, android trims first and last line

That's a different issue, it happens only with custom lineHeight. Fixed in https://github.com/JetBrains/compose-multiplatform-core/pull/897

Looks like there the bug is in skiko paragraph implementation.

It's a bug, we just didn't support that parameter at all 😅

Please check the following ticket on YouTrack for follow-ups to this issue. GitHub issues will be closed in the coming weeks.


I am not able to load a js file in locale that contains other attached json files.

Environment

Operating System: Linux
Node Version:     v20.2.0
Nuxt Version:     3.11.2
CLI Version:      3.11.1
Nitro Version:    2.9.6
Package Manager<EMAIL_ADDRESS>Builder:          -
User Config:      devtools, modules, i18n
Runtime Modules<EMAIL_ADDRESS>Build Modules:    -

Reproduction
.
Describe the bug
I'm trying to config a locale whose file is a javascript file that return a object. if the dictionary is simple like {‘title’: ‘about’, ‘data’: ‘the data’} everything works correctly and I can access those values via $t(title) without problems. However, if the dictionary includes other elements imported from other js files, I am not able to access them.
The configuration of my environment is as follows:
NUXT.CONFIG.TS:
export default defineNuxtConfig({
devtools: { enabled: true },
modules: ["@nuxtjs/i18n"],
i18n: {
lazy: true,
langDir: "./locales",
strategy: 'prefix_and_default',
locales: [
{
code: "en",
name: "English(US)",
file: "en/index.js",
},
{
code: "es",
name: "Español",
file: "es/index.js",
},
],
defaultLocale: "es",
}
})
INDEX.JS
import portfolioMain from './pages/portfolioMain'
import blogMain from './pages/blogMain'
export default {
portfolioMain,
blogMain,
"section-name": "about me"
}
PORTFOLIOMAIN.JS
export default {
title: 'the house'
}
In this configuration, I can access to section-name without problems. Could I help me, please?  My intention is to have the files as tidy as possible within the directory
Additional context
No response
Logs
WARN  [intlify] Not found 'portfolioMain.title' key in 'es' locale messages.

Hi @joaquinCaceres I've had the same issue. Try using defineI18nLocale function in your translation file.
So instead of this:
export default {
portfolioMain,
blogMain,
"section-name": "about me"
}

do this:
export default defineI18nLocale(() => {
  portfolioMain,
  blogMain,
  "section-name": "about me"

});

You can read more about that here -> https://i18n.nuxtjs.org/docs/guide/lazy-load-translations

Closing due to inactivity.
Please open a new issue with a reference to this one if you can follow up with more information.
Thanks!


Feature: Multi-Root Workspaces

Sublimetext and vscode implements Workspace / Project
documentation here: http://docs.sublimetext.info/en/latest/file_management/projects.html
https://code.visualstudio.com/docs/editor/multi-root-workspaces
This feature allow to work with many folders at the same time and hold special config for it.
For example you can have back-end, front-end and worker as independent applications but feature might require to make changes in all of them
This feature might too ambitious for Pre-Alpha.
Minimal implementation might be to allow add multiple folder to file three

Related to #640 #639 and #440

I'll use this to track implementing multi-root workspaces / integrating with the Code extension host.


[Event Request] Application Tests-Misc Codeunit 138400 "RS Pack Content - Evaluation"

[Event Request] Application “Tests-Misc”, Codeunit 138400 "RS Pack Content - Evaluation"
Could you please insert the OnTestInitialize Event at the beginning of the procedure PostSalesInvoices?

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. We will update this issue with information about availability.


Unable to find an implementation for interface acscommons.io.jsonwebtoken.io.Serializer using java.util.ServiceLoader

Required Information

[x] AEM Version, including Service Packs, Cumulative Fix Packs, etc: AEM Cloud Quickstart 2021.1.4830.20210128T075814Z
[x] ACS AEM Commons Version: 4.11.2
[x] Reproducible on Latest? yes/no

Expected Behavior
When configuring an Adobe IO endpoint, there should be no error when running the according healthcheck.
Actual Behavior
The following error can be observed
15.02.2021 19:33:49.845 *ERROR* [sling-default-1-health-com.adobe.acs.commons.adobeio.service.impl.AdobeioHealthcheck] com.adobe.acs.commons.adobeio.service.impl.IntegrationServiceImpl Unable to find an implementation for interface acscommons.io.jsonwebtoken.io.Serializer using java.util.ServiceLoader. Ensure you include a backing implementation .jar in the classpath, for example jjwt-impl.jar, or your own .jar for custom implementations.

Steps to Reproduce
Just configure an Adobe IO endpoint as outlined in https://adobe-consulting-services.github.io/acs-aem-commons/features/adobe-io-apis/index.html and wait for the health check to be automatically triggered.
Links
A similar issue was reported in https://github.com/jwtk/jjwt/issues/563. And indeed the acs-aem-commons-bundle does not include META-INF/services/acscommons.io.jsonwebtoken.io.Serializer

The Serializer is necessary when calling compact (https://github.com/jwtk/jjwt/blob/71ed1b67aafacb3a7383ee8de659023292a89135/impl/src/main/java/io/jsonwebtoken/impl/DefaultJwtBuilder.java#L296) in https://github.com/Adobe-Consulting-Services/acs-aem-commons/blob/309a84ee7dd2e51da844a3f48a65d105f4ba0a48/bundle/src/main/java/com/adobe/acs/commons/adobeio/service/impl/IntegrationServiceImpl.java#L158.


Aspect differs for Images in Layouts

If I have an Image with a non-square bounds, it is plotted as a square when its embedded in a Layout, but as a rectangle when it's on its own:
import numpy as np
from holoviews import Image

x,y = np.mgrid[-50:51, -50:51] * 0.1
bounds=(-1,0,1,1)

ims = (Image(np.sin(x**2+y**2),   bounds=bounds)
       + Image(np.sin(x**2+y**2), bounds=bounds)[-0.5:0.5, -0.5:0.5])

ims

ims.Image.I

Is that deliberate?  It was very surprising.

No, I think Layouts still set Elements to be square by default, will have to remove that.


Hotfix highwatermark

Made changes to resolve https://github.com/r9y-dev/r9y-map/issues/35

Couldn't get a suitable zero shot so went section by section clearing context when needed, technically prompt engineering but not very re-usable


Do not place windows off screen

Before submitting, please confirm you've

[x] read and understood our Contributing Guidelines
[x] completed Mattermost Contributor Agreement
[x] executed npm run lint:js for proper code formatting

This fixes an issue where a window could be placed off screen which happend when the display it was previously on has been disconnected before launching the application.

The application will always be placed on an existing screen.

https://github.com/mattermost/desktop/issues/378
Test Cases

Have 2 monitors
Place the app on one of them
Close the app
Start the app -> It should be exactly were it was when you closed it
Close the app
Disable the monitor
Start the app -> It should be on your main screen

Additional Notes
I do not check if the window fits onto the screen , so if you plug in another monitor with a smaller resolution the window might not fit the screen (which I actually didn't test, might as well be covered by electron).

Thanks @jnugh!!
I don't have two monitors to test..so wondering if someone in the community would like to help with testing?
You can find the test builds here, and test cases have been included above.
If you have two monitors with different sizes, please help test the corner case provided by @jnugh above.

I could not reproduce the issue on Ubuntu 16.04 hosted on VirtualBox. However this feature looks like working well.

Let me see if I can find someone who can help test  this PR on Mac/Windows.

@yuya-oc would you be able to test this on Windows, just to confirm it's working as expected?
I have a couple of people I can ask to try as well, but it would be good to try ourselves first (I would, but again only have one monitor).

As I had written in https://github.com/mattermost/desktop/issues/378#issuecomment-267035909, the original issue didn't reproduced on my MacBook. But this feature works well if I launched the app from CLI.
For Windows, I need to bring another monitor to test this, so I will check this in weekend.

Tested on Windows 10. In the case of that the secondary monitor is located at left of main monitor, x has a negative value. So the feature doesn't work.

You are absolutely right, could you please check the updated version.

Tested on Windows 10 by editing <userData>/bound-info.json. The feature works well.


ctool: --dry-run

Requirements

Rename --test-mode to --dry-run
Do not modify cluster.json

When executing a command with the --dry-run option, a folder named dry-run is created in the working folder. The log and the modified cluster.json are saved to the dry-run folder. The cluster.json file is in the working folder is not modified in this case.


So this is dead right?

40+ eager PRs, and nothing doing. This done?

Ruh roh

@nikolasleblanc We fork it and continue working on it or see how to add it to react-native-community

460+ eager PRs, and nothing doing. This done?

That would be fantastic if we could fork this can continue it, it's a great library.
I'd be glad to help but I'm a bit new to all this...

I just lost almost 2 days of work on this :O

react-native-snap-carousel is used to implement tinder carousel effects, but not appropriate if you want to build an app similar to snapchat, where the user use gesture to move between different screens.
Currently I don't have any replacement for this library.

If you don't want the warning in your debugger's console log.
Install https://github.com/react-native-community/react-native-viewpager with yarn as mentionned in the Readme
link library as mentionned in the doc
go to .\node_modules\react-native-swiper\src\index.js and change the ViewPagerAndroid component with "ViewPager" (don't forget to import it with : import ViewPager from "@react-native-community/viewpager";)
4 It works for me.
Hope it helps.

go to .\node_modules\react-native-swiper\src\index.js and change the ViewPagerAndroid component with "ViewPager" (don't forget to import it with : import ViewPager from "@react-native-community/viewpager";

Hello，
Is there any other way?

I have replaced this (having same features) with good and maintained  - https://github.com/Jacse/react-native-app-intro-slider


Update to Latest domino-nsf Implementation

...maybe wait for the capi-rewrite branch to be merged and released.

This is more permanently on my back-burner than I intended from 2 years ago, although the api package appears to be coming along nicely. I recommend using >= version 0.3.1 as of this writing.


Siesta and HATEOAS pattern

Is possible use the HATEOAS (Hypermedia As The Engine Of Application State) pattern in Siesta?

Of course. Resource.relative(_:) and optionalRelative(_:) are there for exactly this purpose.
If you run into trouble working HATEOASly, Stack Overflow with a siesta-swift tag is a good place to ask “how to” questions — and of course feel free to file a Github issue if you find a bug or a gap in functionality.


Action to quick open member

Is your feature request related to a problem? Please describe.
In our environment, we do not load a full copy of all sources to each developer.  We only get copies of sources that we work on. I often need to open a member from production code, either to recall how the program was coded before my changes or to duplicate something I have seen in another program.
Describe the solution you'd like
It would be nice to have a simple dialog or something that we type to quickly open a member from the IBM i server without the need to create a filter every time.  It does not need to have a short cut but that would be very nice.
Describe alternatives you've considered
Creating a filter that I constantly modify to find the member I want to open or creating a filter over all production sources to get to the one I want (this last item is slow to download a list of all production members).
Thanks, Matt

There are two ways to open files:

Open File: allows you to enter in the entire path to source member or streamfile.

Go to file: lets you quickly filter files you've browsed before to open them again.

@m-tyler I am going to close this for the time being, but do let me know if you need something more specific.

Thanks for the info.
I cannot seem to get Ctrl+Alt+O (IBM i: Open File) to work for me.  It tells me each time its unable to open that member.
The Go to file (Ctrl+Alt+P) option works great if I have opened the filter containing that member once.

@m-tyler Please let me know what you're trying and I will check the format is correct (or fix a bug!)

I tried all of these patterns, FYI we use an IASP but I have yet to be required to add that to anything so far.
/wfisrc/qrpgsrc/prp10vrg.sqlrpgle
/wfisrc.lib/qrpgsrc.file/prp10vrg.sqlrpgle
/wiasp/wfisrc.lib/qrpgsrc.file/prp10vrg.sqlrpgle
/WFISRC/QRPGSRC/PRP10VRG.SQLRPGLE
/WFISRC.LIB/QRPGSRC.FILE/PRP10VRG.SQLRPGLE
/WIASP/WFISRC.LIB/QRPGSRC.FILE/PRP10VRG.SQLRPGLE
Also, I could not find a log entry for the attempt to see if I was messing up the open string.   Is there such a thing for this?
Thanks, Matt

For source members, remove the leading / you have.

Instead of: /wfisrc/qrpgsrc/prp10vrg.sqlrpgle
try: wfisrc/qrpgsrc/prp10vrg.sqlrpgle

Leading / is used for the IFS.

Sorry about that.  I know I had that pattern typed in one time but I did not have it saved in that list I sent along.  I must have used the wrong extension.
Any way to keep that little dialog open if it fails to find the member to open it, for instance, I mistyped the source file name, QRPGSRC as QPRGSRC?

@m-tyler No way to keep it open, but perhaps I could make the value retain for the next time you try to open it. Likely another issue required for that.

Anything would help to prevent having to retype even though it's not a long string I would imagine IFS strings could be an issue.

No hurry on this one its a low PTY for me.  Since I know the string pattern, I'll watch out for my poor typing.

So I would like to have an addition for the quick open, I don't think the member type (extension) needs to be specified.  The IBM i will not allow you to have the same-named member of different types exist in the same source file.   Allowing me to forgo supplying the member type, would mean that your tool would need to figure that part out for me to set the VS Code language.
Thanks, Matt


Update<EMAIL_ADDRESS><EMAIL_ADDRESS>possibly promotions@, marketing@ as well.

Currently all of these emails go to Chris Wilcox. These should go to the 2nd VP, possibly others as well if the job is shared.

This has been resolved for quite some time. If I/We hear otherwise, I'll reopen.


Trying to use flask_jwt_extended.set_access_cookies giving error

I retrieve the the access token by running:
auth_response = client.admin_initiate_auth(
    UserPoolId=USER_POOL_ID,
    ClientId=APP_CLIENT_ID,
    AuthFlow='ADMIN_NO_SRP_AUTH',
    AuthParameters={
        'USERNAME': request.form['username'],
        'PASSWORD': request.form['password']
    }
)

access_token = cognitojwt.decode(
    auth_response['AuthenticationResult']['AccessToken'],
    REGION,
    USER_POOL_ID,
    app_client_id=APP_CLIENT_ID,  # Optional
    # testmode=True  # Disable token expiration check for testing purposes
)

response = jsonify({'jwt': auth_response['AuthenticationResult']['AccessToken']})
set_access_cookies(response, auth_response['AuthenticationResult']['AccessToken'], max_age=60)

I get an error on the last line saying
jwt.exceptions.InvalidAlgorithmError: The specified alg value is not allowed

There's no option to set the algorithm within the package and I don't see anywhere to set it on the management console either. Do you have any recommendations?

workable example


Improved Error handling

Improves error handling code in PL/Rust.
Includes:

thiserror
eyre/tracing wired up to not interfere with pgx
Spantraces and error sections supported
Most unwraps turned into errors, this is just a first pass.
tracing_level GUC for customizing the log level of PL/Rust itself
#[pg_extern] functions now wrap functions which return errors, and handle them.
Updates flake for CI

Ok this is ready for review now. 😅


NL: Fixes minor crashes and add dates for maps

Fix a couple of crashes I found on GCP console.
Fix a regression to [floods in the world]
Add dates for map charts (https://github.com/datacommonsorg/website/issues/2392)

Thanks for the review!


Chore: add arrows to dropdowns

Chore
Describe the chore
Add arrows to dropdown overlay panels

https://radix-ui.com/primitives/docs/components/dropdown-menu#arrow

Hey, @MildTomato Would like to contribute. Is there some place I can refer to for setting up the project
Right now I am doing the following

Forked the repo and run npm build
npm link inside the repo
add link in a test folder using npm link @supabase/ui

But I seem to be getting an error

@ankitjena sorry for the late reply!
Yep, I've had the same problem as you're having.
To be honest, I've mainly been testing and playing around with components inside storybook, but we should really get into the habit soon of making components and road testing them in react apps on the fly - but this problem you mentioned keeps happening and I'm not super familiar with it.
I wrote up a fix that (sometimes) works for this. I think this tends to work as long as your using the same version of react and react-dom in both the ui library and also the target app your testing it in.
https://github.com/supabase/ui/blob/develop/development.md#common-issues
If you're struggling with that though, I'd suggest just using storybook to preview the components.
You can run storybook with npm run storybook and it should be served on localhost:6006

@MildTomato Sorry for the late response on my end as well, busy week! Thanks for instructions. I went the easier route with storybook and made a PR, do review it if possible.

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Update example configs

Hi, I'm trying out the current main branch and found that basically all included config JSONs are broken. It would definitely help new users get up and running quickly if there were one complete and working example for each catalogue type. Edit: found https://github.com/TerriaJS/saas-catalogs-public/ with working examples.
The docs are helpful once a working example exists, but it's hard to create a working config from scratch purely from the docs.
e.g. based on a working config found through a Github code search here's a working CKAN config:
/* Docs: https://docs.terria.io/guide/connecting-to-data/catalog-type-details/ckan-group/ */
{
    "corsDomains" : [
        "corsproxy.com",
        "catalogue.data.wa.gov.au"
    ],
    "homeCamera": {
        "west": 105,
        "south": -45,
        "east": 155,
        "north": -5
    },
    "services": [],
    "catalog": [
        {
            "name": "WA Government Data Catalogue",
            "description": "WA public sector data.",
            "type": "ckan-group",
            "url": "https://catalogue.data.wa.gov.au/",
            "groupBy": "organization"
        }
    ]
}

@florianm Thanks for letting us know. I've removed all of the old init files and expanded simple.json, which is written for v8.

Thanks, much appreciated! Happy to close this issue.


Tweaked const declaration style

More in the style of https://golang.org/doc/effective_go.html#constants
And more consistant accross the file

This change doesn't apply.
I think I'd prefer you tried to avoid really long lines.  The comments at the end of fairly long lines could be placed above.

Fine.
Will you merge it if I move the comments back to top line?

I'd prefer that.  The patch doesn't apply currently, though.
On Tue, Mar 24, 2015 at 11:17 PM Julien Vermillard<EMAIL_ADDRESS>wrote:

Fine.
Will you merge it if I move the comments back to top line?
—
Reply to this email directly or view it on GitHub
https://github.com/dustin/go-coap/pull/18#issuecomment-85868405.

OK fixed long line comments.
merge with current master, but maybe it's not for you because you didn't pushed #17 patch to master ? (an unrelated line was modified by go fmt)

Yeah, I did fail to push.  Sorry about that.  I've fixed this up and pushed it.


docs: Add link to Cypress

What:
Add link to Cypress in README.
Why:
Might be helpful for people that :

don't know what Cypress is.
are familiar with kcd-testing-libraries testing style but not Cypress.
are looking for quick link to Cypress to browse docs.

Checklist:

[x] Documentation
[ ] Tests N/A
[x] Ready to be merged
[ ] Added myself to contributors table N/A Too small a change to consider myself a contributor 😄

Please feel free to ignore this PR for any reason !
Cheers !

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


numGroups / numVarDataFields support

The 1.0 specification mentions that the following attributes are part of message headers

Number of repeating groups
A count of repeating groups at the root level of the message. The count does not include nested repeating groups.
Number of variable-length fields
A count of the variable-length fields at the root level of the message. The count does not include variable-length fields within repeating groups.

When generating Java encoder/decoder for this schema using 1.33, numGroups and numVarDataFields do not seem to have any special significance.
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<sbe:messageSchema xmlns:sbe="http://fixprotocol.io/2016/sbe"
                   package="uk.co.real_logic.sbe.benchmarks"
                   id="1"
                   version="1"
                   semanticVersion="5.2"
                   description="Example schema"
                   byteOrder="littleEndian">
    <types>
        <composite name="messageHeader" description="Message identifiers and length of message root">
            <type name="blockLength" primitiveType="uint16"/>
            <type name="templateId" primitiveType="uint16"/>
            <type name="schemaId" primitiveType="uint16"/>
            <type name="version" primitiveType="uint16"/>
            <type name="numGroups" primitiveType="uint16" />
            <type name="numVarDataFields" primitiveType="uint16" />
        </composite>
    </types>

    <sbe:message name="Car" id="1" description="Description of a basic Car">
        <field name="serialNumber" id="1" type="uint32"/>
    </sbe:message>
</sbe:messageSchema>

Generated Java code:
    public CarEncoder wrapAndApplyHeader(
        final MutableDirectBuffer buffer, final int offset, final MessageHeaderEncoder headerEncoder)
    {
        headerEncoder
            .wrap(buffer, offset)
            .blockLength(BLOCK_LENGTH)
            .templateId(TEMPLATE_ID)
            .schemaId(SCHEMA_ID)
            .version(SCHEMA_VERSION);

        return wrap(buffer, offset + MessageHeaderEncoder.ENCODED_LENGTH);
    }

Are numGroups / numVarDataFields not supported ?

I believe the specification repository was modified after version 1 was "cut".  The modifying commit refers to changes since v1. It is a bit confusing.
AFAIK, the specification for SBE v2 is still in the release candidate phase. It would be useful to adopt these header fields, and adjust our implementation, as it allows less restricted schema extension (w.r.t. groups and variable length data). However, adopting these changes is not currently on our roadmap.

Actually, I was more correct before the edit, i.e., it is part of the v2 specification. Please see this issue: https://github.com/FIXTradingCommunity/fix-simple-binary-encoding/issues/157


Pgsearch(search on projects)

Fixes #21
Implemented full text search with pg_search.Removed sql specific code with minor changes in UI.

Looks good to me, will merge once @tachyons approves.


New environment variable "userManagementEnabled" (true/false)

This variable enables/disables the user management in the BSS

test this please


Can set nvidia as primary gpu in dual monitor env on laptop.

Description
According to the official setting recommendation, I use intel as the main graphics card, but the system doesn't run smoothly, however I can't turn off the built-in graphics card in the bios.
I used to use gnome,add /usr/lib/udev/rules.d/61-mutter-primary-gpu.rules in gnome and set the following:
ENV{DEVNAME}=="/dev/dri/card1", TAG+="mutter-device-preferred-primary"
so that all the rendering work is done by nvidia, and intel is only used as a display device, and then you get a very smooth running environment.
I don't know if there is such a setting in hyprland.

so that all the rendering work is done by nvidia, and intel is only used as a display device, and then you get a very smooth running environment.

That is physically not possible.


NullPointerException in NativeMap.updateCameraPosition

Since tangram 0.16.0, I am getting a lot of error reports like these
java.lang.NullPointerException: Attempt to invoke virtual method 'void com.mapzen.tangram.NativeMap.updateCameraPosition(int, double, double, float, float, float, float, float, float, double, double, double, double, android.graphics.Rect, float, int)' on a null object reference
at com.mapzen.tangram.MapController.updateCameraPosition(MapController.java:408)
at com.mapzen.tangram.MapController.updateCameraPosition(MapController.java:360)
at de.westnordost.streetcomplete.map.tangram.CameraManager.pushCameraPositionToController(CameraManager.kt:169)
at de.westnordost.streetcomplete.map.tangram.CameraManager.animate(CameraManager.kt:174)
at de.westnordost.streetcomplete.map.tangram.CameraManager.access$animate(CameraManager.kt:35)
at de.westnordost.streetcomplete.map.tangram.CameraManager$animateCameraUpdate$6.invoke(CameraManager.kt:157)
at de.westnordost.streetcomplete.map.tangram.CameraManager$animateCameraUpdate$6.invoke(CameraManager.kt:35)
at de.westnordost.streetcomplete.map.tangram.CameraManagerKt$sam$android_animation_ValueAnimator_AnimatorUpdateListener$0.onAnimationUpdate(Unknown Source:2)
at android.animation.ValueAnimator.animateValue(ValueAnimator.java:1547)
at android.animation.ObjectAnimator.animateValue(ObjectAnimator.java:987)
at android.animation.ValueAnimator.animateBasedOnTime(ValueAnimator.java:1339)
at android.animation.ValueAnimator.doAnimationFrame(ValueAnimator.java:1471)
at android.animation.AnimationHandler.doAnimationFrame(AnimationHandler.java:146)
at android.animation.AnimationHandler.access$100(AnimationHandler.java:37)
at android.animation.AnimationHandler$1.doFrame(AnimationHandler.java:54)
at android.view.Choreographer$CallbackRecord.run(Choreographer.java:1002)
at android.view.Choreographer.doCallbacks(Choreographer.java:816)
at android.view.Choreographer.doFrame(Choreographer.java:748)
at android.view.Choreographer$FrameDisplayEventReceiver.run(Choreographer.java:990)
at android.os.Handler.handleCallback(Handler.java:873)
at android.os.Handler.dispatchMessage(Handler.java:99)
at android.os.Looper.loop(Looper.java:280)
at android.app.ActivityThread.main(ActivityThread.java:6706)
at java.lang.reflect.Method.invoke(Native Method)
at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:493)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:858)

So, some field in MapController is already null but it is still being accessed.
Maybe this has something to do with the following: The app uses the Android animation system to animate which repeatedly calls updateCameraPosition on the MapController during its course. On onDestroy however, all animations are cancelled, so after the Fragment/Activity has been destroyed, there should not be any calls anymore.
When does it occur? Not sure, it never occured to myself, I only get the crash reports. But I am pretty sure this happens when the view is being destroyed / recreated by app switch or something else.

The order in which onDestroy is called on fragments, activities and their lifecycle observers is nothing the individual app developer can influence. The order is given by the Android system.
Am 12. Mai 2021 01:45:30 MESZ schrieb Matt Blair @.***>:

My first guess was that these animation callbacks might be on a
background thread, but the stacktrace here looks like it's running on
the main thread - so that rules out race conditions.
The NativeMap instance is disposed in the call to
MapView.onDestroy, so these callbacks must be occurring after that
point. Maybe you need to change the order in which objects get
destroyed?
--
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub:
https://github.com/tangrams/tangram-es/issues/2263#issuecomment-839291153

--
Diese Nachricht wurde von meinem Android-Gerät mit K-9 Mail gesendet.

I looked at the StreetComplete code that seems to control these camera animations and I have a theory, so tell me if this makes sense:

When OnDestroy is called on the MapFragment (and MapView) KtMapController calls cameraManager.cancelAllCameraAnimations() https://github.com/streetcomplete/StreetComplete/blob/master/app/src/main/java/de/westnordost/streetcomplete/map/tangram/KtMapController.kt#L133-L136
In cancelAllCameraAnimations() a call to animator.cancel() is posted to the main thread Handler and not executed immediately https://github.com/streetcomplete/StreetComplete/blob/master/app/src/main/java/de/westnordost/streetcomplete/map/tangram/CameraManager.kt#L85-L94
MapView.onDestroy finishes and the NativeMap instance is destroyed
On the next main thread loop, the animators run their next step because cancel() has not been called yet, and the animation triggers the null pointer exception.

Does that seem plausible? If this is the case, you could test/fix it by making the animator.cancel() call directly on the main thread in the onDestroy callback.

Wow, that's very cool that you did that!

Correct
Oh hmm, I think you are right. This might be the problem!
Yes
Right, yes this could be the source of this

I'll prepare a fix for this that. Since I could never reproduce this issue myself, I think I will just deploy the fix "into the blue" and then I'll see if I still get those crash reports or not. Shall we close this issue then until after I can report whether this was the issue or not?

The StreetComplete code was pretty easy to navigate 👍
I think it's better to close this issue, since there isn't any action to be taken in this repo. If the problem turns out to be something different, we can re-open the issue in the future.


Update benefits.md

Add missing reference to 'Mainstream adoption' from Official Guide, per Issue #4.

This duplicates the "Mainstream adoption" text that was already inserted in the "Adoption" section... I actually moved some parts around, for clarity sake I felt it was better to have "Adoption" as a main section.
How about we just remove this "Benefits" section then ? Maybe it's not that useful after all, what do you think ?


Possible package that can be included

I have developed a Go package that may be included in the tooling resources:
github.com/kelvins/chronobiology - Provide an easy way to access some chronobiology functions that can perform data analysis in time series using GoLang. (I think this is related to bioinformatics)
I don't know if this package is 'robust' as the packages shared in the tooling resources. If you think it should be added feel free to add or let me know.
Thanks

Yes, we should definitely add.  Please PR with a relevant description to the tooling README.  Thanks!

Ok, I will do that. Thank you so much.

Added.  Closing.  Thanks!


Info List Item Info line 'wrap' prop

Describe the desired behavior
Add wrap prop to InfoListItem so I can wrap info line items
Describe the current behavior
No wrapping on info line, only subtitle & title.
Is this request related to a current issue?
No
Additional Context

Log an issue on the React one too


Updated Red Hat Universal Base Images link

The link previous published was not showing information about the Red Hat UBI images, the new link shows the current OpenSSL version and the date of image publication.
Thank you for your contribution! Some pointers to get it merged quickly:
For contributions in software/:

[ x] PR Title: Please use "Add <vendor/product name>" (instead of "Update README.md")
[x ] Status: please select a value from the status table at the top
[x ] Version: Status Vulnerable / Workaround? -> List vulnerable versions.
Status Fix?                     -> List fixed versions.
[x ] Links: make sure you link to a public statement by the developer.
Alternatively, include and link a file in the software/vendor-statements/ directory
[x ] Please mind the sorting

The url at this moment is more clear what is impacted and on what version.
Also there is a status, which is not visible in your new url.

@pbeij I can go with you in this, I'll close the PR.


add windows support for root CA cert stores

Summary
Move the get/create of a root CA cert store into OS dependent functions
Fixes https://github.com/rancher/system-agent/issues/83
Unblocks https://github.com/rancher/windows/issues/161
Occurred changes and/or fixed issues
Windows does not support x509.SystemCertPool() in <go1.18. This PR implements a workaround to load the System Cert Store on Windows nodes.
Technical notes summary
This is adapted from the following workaround: https://github.com/golang/go/issues/16736#issuecomment-540373689
Error seen on Windows machines:
Message : error loading system cert pool for probe (kubelet): crypto/x509: system root pool is not available on Windows
Since <go1.18 on Windows cannot load the root CA cert store, this PR leverages syscalls to load the certificate context from the Root CA cert store and then create a new x509 cert pool that contains the Root CAs. This will likely cause a performance drop on Windows as each probe that requires a CACert will need to build it's own x509 cert pool with the root CAs.
Once system-agent is upgraded to go1.18+ the differing code paths should no longer be required.
Areas or cases that should be tested
This PR cannot be tested before it is merged as far as I am aware.
Areas which could experience regressions
These changes should only impact system agent functionality on Windows. The existing functionality for linux hosts has been shuffled into a new function but the underlying code is still the same. For windows, given that loading the CA certs from the root store is currently broken I do not see any potential for regression.
Screenshot/Video
N/A

@snasovich If @Oats87 is not able to review this by EOD today as he is out of office, can I get your approval to merge once I have another round of approvals from @brandond and @thedadams ?


hocon object merging (inheritance) behavior not expected

Copy of https://github.com/akkadotnet/akka.net/issues/2700

 Feature: HOCON Configuration
  Scenario: new objects can support inheritence via object merging
  Given I have hocon
  ###
  data-center-generic = { cluster-size = 6 }
  data-center-east = ${data-center-generic} { name = "east" }
  ###
  When I parse hocon
  Then I should have the following values
      | path                             | value |
      | data-center-generic.cluster-size | 6     |
      | data-center-east.cluster-size    | 6     |
      | data-center-east.name            | east  |

data-center-east.cluster-size returns null

closed by #55


Corrected all Swagger documents found in the Accounting module by ad…

Description
Describe the changes made and why they were made. Ignore if these details are present on the associated Jira ticket
Checklist
Please make sure these boxes are checked before submitting your pull request - thanks!

[x] Commit message starts with the issue number from https://issues.apache.org/jira/projects/FINERACT/. Ex: FINERACT-646 Pockets API.

[x] Coding conventions at https://cwiki.apache.org/confluence/display/FINERACT/Coding+Conventions have been followed.

[x] API documentation at https://github.com/apache/fineract/blob/develop/api-docs/apiLive.htm has been updated with details of any API changes.

[x] Integration tests have been created/updated for verifying the changes made.

[x] All Integrations tests are passing with the new commits.

[x] Submission is not a "code dump".  (Large changes can be made "in repository" via a branch.  Ask on the list.)

Our guidelines for code reviews is at https://cwiki.apache.org/confluence/display/FINERACT/Code+Review+Guide

@Sanyam96 : Can you please review this change ?

@kangbreder
Changes seems to be perfect on first glance.
I'll review your changes and we'll merge your PR with complete GSoC project as a single PR on fineract.

changes look fine at first glance.
We'll merge this as a single PR for GSoC project 2019 into fineract.

@Sanyam96 I'm doing a quick round of review of open PRs to help clean up the list of pending PRs (any help with that is very very welcome BTW!)... were you planning to merge this (when?), or should this be closed, perhaps superceded by another one of @kangbreder PRs? BTW, generally speaking, I personally would encourage to gradually merge GSoC contributions, and not wait for one single "big bang".


uaa-cli 0.8.0

It looks like the uaa-cli just cut a release of 0.8.0
Apologies for not submitting a PR to bump the version myself, but could the uaa.rb formula be bumped to take the latest CLI release?
I dream of a day when homebrew taps & apt-get & snap repos are so easily integrated into all project's CI/CD that they're hosted & maintained by the code authors, but until that day comes... could I freeload off your brew taps? 😉
EDIT: for the time being I'm goofing with uaa-cli 0.8.0 in my own brew tap but it's just for goofing. When/if the version bump happens here I'd like to switch back to the starkandwayne tap

Sorry, I missed this issue. Will investigate.

Resolved. Sorry I never switched over the pipeline when they started cutting their own releases + binaries.
$ brew install starkandwayne/cf/uaa-cli
Updating Homebrew...
==> Installing uaa-cli from starkandwayne/cf
==> Downloading https://github.com/cloudfoundry-incubator/uaa-cli/releases/download/0.8.0/uaa-darwin-amd64-0.8.0
...

$ uaa version
0.8.0 2f8631f


libsolv 0.7.24

Changelog: https://github.com/openSUSE/libsolv/blob/0.7.24/NEWS
License: https://github.com/openSUSE/libsolv/blob/0.7.24/LICENSE.BSD
Requirements: https://github.com/openSUSE/libsolv/blob/0.7.24/CMakeLists.txt
Actions:
1.

Linter check found the following problems:
The following problems have been found:
ERROR: clone/recipe/meta.yaml:35: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: clone/recipe/meta.yaml:50: host_section_needs_exact_pinnings: output "libsolv": Packages in host must have exact version pinnings, except python build tools.
ERROR: clone/recipe/meta.yaml:80: host_section_needs_exact_pinnings: output "libsolv-static": Packages in host must have exact version pinnings, except python build tools.
Errors were found

Linter check found the following problems:
The following problems have been found:
ERROR: clone/recipe/meta.yaml:33: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
WARNING: clone/recipe/meta.yaml:33: build_tools_must_be_in_build: The build tool pkg-config is not in the build section.
ERROR: clone/recipe/meta.yaml:35: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: clone/recipe/meta.yaml:48: host_section_needs_exact_pinnings: output "libsolv": Packages in host must have exact version pinnings, except python build tools.
WARNING: clone/recipe/meta.yaml:48: build_tools_must_be_in_build: output "libsolv": The build tool pkg-config is not in the build section.
ERROR: clone/recipe/meta.yaml:50: host_section_needs_exact_pinnings: output "libsolv": Packages in host must have exact version pinnings, except python build tools.
ERROR: clone/recipe/meta.yaml:78: host_section_needs_exact_pinnings: output "libsolv-static": Packages in host must have exact version pinnings, except python build tools.
WARNING: clone/recipe/meta.yaml:78: build_tools_must_be_in_build: output "libsolv-static": The build tool pkg-config is not in the build section.
ERROR: clone/recipe/meta.yaml:80: host_section_needs_exact_pinnings: output "libsolv-static": Packages in host must have exact version pinnings, except python build tools.
Errors were found

Linter check found the following problems:
The following problems have been found:
WARNING: clone/recipe/meta.yaml:34: build_tools_must_be_in_build: The build tool pkg-config is not in the build section.
ERROR: clone/recipe/meta.yaml:34: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: clone/recipe/meta.yaml:36: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: clone/recipe/meta.yaml:50: host_section_needs_exact_pinnings: output "libsolv": Packages in host must have exact version pinnings, except python build tools.
WARNING: clone/recipe/meta.yaml:50: build_tools_must_be_in_build: output "libsolv": The build tool pkg-config is not in the build section.
ERROR: clone/recipe/meta.yaml:52: host_section_needs_exact_pinnings: output "libsolv": Packages in host must have exact version pinnings, except python build tools.
WARNING: clone/recipe/meta.yaml:80: build_tools_must_be_in_build: output "libsolv-static": The build tool pkg-config is not in the build section.
ERROR: clone/recipe/meta.yaml:80: host_section_needs_exact_pinnings: output "libsolv-static": Packages in host must have exact version pinnings, except python build tools.
ERROR: clone/recipe/meta.yaml:82: host_section_needs_exact_pinnings: output "libsolv-static": Packages in host must have exact version pinnings, except python build tools.
Errors were found

Linter check found the following problems:
The following problems have been found:
ERROR: clone/recipe/meta.yaml:34: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
WARNING: clone/recipe/meta.yaml:34: build_tools_must_be_in_build: The build tool pkg-config is not in the build section.
ERROR: clone/recipe/meta.yaml:36: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: clone/recipe/meta.yaml:50: host_section_needs_exact_pinnings: output "libsolv": Packages in host must have exact version pinnings, except python build tools.
WARNING: clone/recipe/meta.yaml:50: build_tools_must_be_in_build: output "libsolv": The build tool pkg-config is not in the build section.
ERROR: clone/recipe/meta.yaml:52: host_section_needs_exact_pinnings: output "libsolv": Packages in host must have exact version pinnings, except python build tools.
WARNING: clone/recipe/meta.yaml:80: build_tools_must_be_in_build: output "libsolv-static": The build tool pkg-config is not in the build section.
ERROR: clone/recipe/meta.yaml:80: host_section_needs_exact_pinnings: output "libsolv-static": Packages in host must have exact version pinnings, except python build tools.
ERROR: clone/recipe/meta.yaml:82: host_section_needs_exact_pinnings: output "libsolv-static": Packages in host must have exact version pinnings, except python build tools.
Errors were found


chore: run pipeline commands in src directory

run pipeline commands in the src directory
add net6.0 as Target Framework for run tests

The Github Actions CI failed on delivery nuget because can not know the secret api-key to use

I will merge anyway. For delivery nuget from master branch


Sync DIS2012.xml and DIS7.xml

The file in this repo, xmlpg/DIS2012.xml and the one over in DISDescription/DIS7.xml differ slightly. They should be the same.
https://github.com/open-dis/xmlpg/blob/master/DIS2012.xml
https://github.com/open-dis/DISDescription/blob/master/DIS7.xml
It looks to me like different fixes have gone into both so a careful merge of the two should be considered.

To avoid this, there should be only one source for these files.

Is it possible to make xmlpg generate some kind of time stamp with the git commit for the file used to generate the code?

Is it possible to make xmlpg generate some kind of time stamp with the git commit for the file used to generate the code?

@kurtsansom it probably could, that would help identify what was used to generate the code. If this would be useful to you feel free to submit a pull request.

@kurtsansom it probably could, that would help identify what was used to generate the code. If this would be useful to you feel free to submit a pull request.

I would be happy to make some changes. I am not sure where to start. I was able to build, and generate c++, but beyond that my java skills are mediocre.

@kurtsansom ok, I'd recommend installing Apache Netbeans for your IDE, file open the root folder with the pom.xml.
Accessing the Git sha1 in Java looks like it could be done by adding the maven git commit id plugin to the project and then reading in the properties file it generates.


[auto-bump] [no-release-notes] dependency by fulghum

:coffee: An Automated Dependency Version Bump PR :crown:
Initial Changes
The initial changes contained in this PR were produced by `go get`ing the dependency.
```
$ go get github.com/dolthub//go@
```
Before Merging
This PR must have passing CI and a review before merging.

This PR has been superseded by https://github.com/dolthub/go-mysql-server/pull/2127

This PR has been superseded by https://github.com/dolthub/go-mysql-server/pull/2128


Where is Swift_Validate in 6.*?

The file swiftmailer/swiftmailer/lib/classes/Swift/Validate.php and its class Swift_Validatehas disappeared from v6.* but still mentionned in https://github.com/swiftmailer/swiftmailer/blob/master/doc/messages.rst and NOT appearing has deleted in https://github.com/swiftmailer/swiftmailer/blob/master/CHANGES.
So, is it a mistake? If not what is the new way to validate?

So... If I want to validate, I must stick to 5.4.8?

@fabpot sorry to ping you, but it seems to me that having lost Validation is A problem. So if you have any answer...

@Laurent3170 Stop crying, use the search then you will find the composer file or the according commit https://github.com/swiftmailer/swiftmailer/commit/6776d293954416a9ee7df4d76f24cea6eb3370a9 and then you see that it has been replaced by an external library.
Then make a pull request which adds this change to the changes.txt and update the doc, that helps fabpot and all other user. Thanks.

@Rotzbua am I crying? No I don't think so... But if so, thanks for having drying my tears...
Maybe you're a geek in Github and Symfony and maybe I'm not.
I have used the searched and just found that the file was not there anymore, with no explanation, looking like it was just a mistake.  First question was

So, is it a mistake?

Not having this answer gives no possibility to know. I can't re-do all the way that has lead to this decision if I was not implied in these discussions.
Second question was

If not what is the new way to validate?

You gave me an answer with the commit url and I'll look at it, and I thank you for this part of your answer.
And then I will be able to do a commit, if still needed, as you have mentioned and as I did in other parts of other bundles.

@Rotzbua I followed your link and created two PR's #951 and #952 (yes I don't know how to do only one directly from Github, but ready to learn).

@Laurent3170 You did great! Thank you.


cytoscape: bump 3.6.1 -> 3.7.1

Needed to update URL, because wget "http://chianti.ucsd.edu/cytoscape-3.7.1/cytoscape-3.7.1.tar.gz" returns 404.
Motivation for this change
Update to latest version, bumping from 3.6.1 -> 3.7.1.
Things done

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

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

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

Please use fetchFromGitHub instead of fetchurl when fetching from GH.

@peterhoeg, I would normally use fetchFromGitHub, but this is a special case. The current Nix package doesn't compile from source. Rather, it just downloads a gzipped tarball from this URL:
http://chianti.ucsd.edu/${name}/${name}.tar.gz
That URL works for version 3.6.1, but it doesn't work for version 3.7.1. The equivalent working URL is this:
https://github.com/cytoscape/cytoscape/releases/download/${version}/${name}.tar.gz
My update is very conservative, containing the minimal changes required to bump from 3.6.1 to 3.7.1.
If someone has time, it would definitely be better to get the code like this:
  src = fetchFromGitHub {
    owner = "cytoscape";
    repo = "cytoscape";
    rev = "${version}";
    sha256 = "0jqg3mxvgh9w4h9npbzql78ki03ypa5b3pjgwhivlqwwa60sxnn2";
  };

And then build from source. But I can't guarantee when I'll be able to make that happen, because it'll mean completely rewriting the package.

Makes sense.


Request for training logs

Hi,
I've checked other issues to find training logs and I was able to get training log of 'deit_small_distilled_patch16_224' model
thanks to (https://github.com/facebookresearch/deit/issues/18).
Could you also share the training logs of other distilled versions like 'deit_tiny_distilled_patch16_224' and 'deit_base_distilled_patch16_224' and 'deit_base_distilled_patch16_384'?

Hi @HeegonJin ,
Thanks for your question.
We have no plans to share additional training logs in the near future. I will keep you informed.
There are more logs here.
Best,
Hugo