OIDC with Google

I'm been trying to set up the OIDC login plugin with G Suite, and I believe I'm nearly there.
I've been able to successfully get through the login and approval flow, and been redirected back to the Stethoscope app on the following URL:
http://stethoscope:5000/<21 digit numeric value>#
However, the GET request to that URL ends in a 400 Bad Request, with nothing additional in the Docker Compose logs.
I do think I have the Google integration (with a service account) set up correctly, but it's hard to tell given the lack of feedback in the logs.
My config looks like this:
OIDC_CALLBACK_URL = 'stethoscope'
OIDC_CLIENT_ID = '' //my client id
OIDC_CLIENT_SECRET = 'secret'
OIDC_AUTHORIZATION_URL = 'https://accounts.google.com/o/oauth2/v2/auth'
OIDC_CALLBACK_SCHEME = 'http'
OIDC_CALLBACK_PORT = 5000
OIDC_TOKEN_URL = 'https://accounts.google.com/o/oauth2/token'
OIDC_USERINFO_URL = 'https://www.googleapis.com/oauth2/v3/userinfo'

PLUGINS = {
  'google': {
    'GOOGLE_API_SECRETS': '''{
  "type": "service_account",
  "project_id": "stethoscope-redacted",
  "private_key_id": "redacted",
  "private_key": "redacted",
  "client_email": "redacted.iam.gserviceaccount.com",
  "client_id": "redacted",
  "auth_uri": "https://accounts.google.com/o/oauth2/auth",
  "token_uri": "https://accounts.google.com/o/oauth2/token",
  "auth_provider_x509_cert_url": "https://www.googleapis.com/oauth2/v1/certs",
  "client_x509_cert_url": "https://www.googleapis.com/robot/v1/metadata/x509/redacted.iam.gserviceaccount.com"
}''',

    'GOOGLE_API_USERNAME': 'Stethoscope',
    'GOOGLE_API_SCOPES': [
        "https://www.googleapis.com/auth/admin.directory.device.chromeos.readonly",
        "https://www.googleapis.com/auth/admin.directory.device.mobile.readonly",
        "https://www.googleapis.com/auth/admin.directory.user.readonly",
        "https://www.googleapis.com/auth/admin.reports.audit.readonly",
        "https://www.googleapis.com/auth/admin.reports.usage.readonly",
    ]
  }
}

Any thoughts? :)

Hello,
I think you should use the email account associated with your API developpers as the identifier in URL (such as someone%40gmail.com).
Also, the triple quote before GOOGLE_API_SECRETS seems weird since a blob JSON is expected.
If the team could provide concrete examples for each plugin, it would be really appreciated.

Hello,
I think you should use the email account associated with your API developpers as the identifier in URL (such as someone%40gmail.com).
If the team could provide concrete examples for each plugin, it would be really appreciated.
In my case I have :
PLUGINS = {
'google': {
'GOOGLE_API_SECRETS':
'''{
"type": "service_account",
"project_id": "stethoscope-160318",
"private_key_id": "e267075d310ec2e1e60e3f8af6f186663b27ee75",
"private_key": "-----BEGIN PRIVATE KEY-----BLABLABLA-----END PRIVATE KEY-----",
"client_email"<EMAIL_ADDRESS>"client_id": "101104793176291395999",
"auth_uri": "https://accounts.google.com/o/oauth2/auth",
"token_uri": "https://accounts.google.com/o/oauth2/token",
"auth_provider_x509_cert_url": "https://www.googleapis.com/oauth2/v1/certs",
"client_x509_cert_url": "https://www.googleapis.com/robot/v1/metadata/x509/713615339037-compute%40developer.gserviceaccount.com"
}''',
'GOOGLE_API_USERNAME': 'Stethoscope',
'GOOGLE_API_SCOPES': [
"https://www.googleapis.com/auth/admin.directory.device.chromeos.readonly",
"https://www.googleapis.com/auth/admin.directory.device.mobile.readonly",
"https://www.googleapis.com/auth/admin.directory.user.readonly",
"https://www.googleapis.com/auth/admin.reports.audit.readonly",
"https://www.googleapis.com/auth/admin.reports.usage.readonly"
]
}
}
In the log I only see :
api_1           | 2017-03-02T19:42:41+0000 [stderr#error] [Failure instance: Traceback: <type 'exceptions.RuntimeError'>: Unable to get credentials for Google API access: []
api_1           | 2017-03-02T19:42:41+0000 [stderr#error] /usr/local/lib/python2.7/threading.py:801:__bootstrap_inner
api_1           | 2017-03-02T19:42:41+0000 [stderr#error] /usr/local/lib/python2.7/threading.py:754:run
api_1           | 2017-03-02T19:42:41+0000 [stderr#error] /usr/local/lib/python2.7/site-packages/twisted/_threads/_threadworker.py:46:work
api_1           | 2017-03-02T19:42:41+0000 [stderr#error] /usr/local/lib/python2.7/site-packages/twisted/_threads/_team.py:190:doWork
Any thoughts?

Google appears to be sending the user back to the wrong local endpoint (not clear from our docs, but this should be /auth/oidc; Google is sending the user just to the root URI). I've replicated this behavior on my personal G Suite domain and am now trying to figure out why Google is not respecting the full redirect URI.

Please let me know if that commit doesn't fix your issue. Thanks for the bug report!

That did indeed fix the login issue, thank you! Now I can start debugging why I'm not getting data from my Google service account... :)
As @elenoir mentioned, config samples for each plugin would be greatly appreciated.

Glad that fixed your issue.
I'm working on the docs and will include config samples for each plugin.
On Sat, Mar 4, 2017 at 3:01 AM Vegard Vaage<EMAIL_ADDRESS>wrote:

That did indeed fix the login issue, thank you! Now I can start debugging
why I'm not getting data from my Google service account... :)
As @elenoir https://github.com/elenoir mentioned, config samples for
each plugin would be greatly appreciated.
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/Netflix/stethoscope/issues/13#issuecomment-284144429,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABQuds_TtN_oUOoV1m_3Rs-t6dK9jmN-ks5riUSWgaJpZM4MRC5-
.

Hello,
The fix didn't fix my issue with my previous example.
I have another error now :
2017-03-06T12:22:40+0000 [stderr#error] [Failure instance: Traceback: <type 'exceptions.RuntimeError'>: Unable to get credentials for Google API access: 'str' object has no attribute 'get'

@elenoir Your issue is different from @vegardvaage's -- theirs was with respect to using Google for authentication via OpenIDConnect. Yours is, I believe, in configuring the Google data source plugin.
You need to configure your PLUGINS dictionary like so:
PLUGINS = {
  'google': {
    'GOOGLE_API_SECRETS': {
       "client_id": "<redacted>",
       "private_key": "-----BEGIN PRIVATE KEY-----<redacted>-----END PRIVATE KEY-----\n",
       "token_uri": "https://accounts.google.com/o/oauth2/token",
       "client_email": "<redacted>",
       "client_x509_cert_url": "<redacted>",
       "private_key_id": "<redacted>",
       "type": "service_account",
       "auth_uri": "https://accounts.google.com/o/oauth2/auth",
       "auth_provider_x509_cert_url": "https://www.googleapis.com/oauth2/v1/certs",
       "project_id": "<redacted>"
    },
    'GOOGLE_API_USERNAME': '<redacted>',
    'GOOGLE_API_SCOPES': [
      "https://www.googleapis.com/auth/admin.directory.device.chromeos.readonly",
      "https://www.googleapis.com/auth/admin.directory.device.mobile.readonly",
      "https://www.googleapis.com/auth/admin.directory.user.readonly",
      "https://www.googleapis.com/auth/admin.reports.audit.readonly",
      "https://www.googleapis.com/auth/admin.reports.usage.readonly",
    ],
  }
}


Includes k3s upgrade images when uses image export script in dev, master, or non semver tag that is equal to kd.RancherVersionDev

What kind of request is this (question/bug/enhancement/feature request):
bug
Steps to reproduce (least amount of steps as possible):
Use export script with TAG set to dev, master, or a value equal to kd.RancherVersionDev.
Result:
Using export script with TAG set to dev, master, or a value equal to kd.RancherVersionDev will result in no k3s
upgrade or related images being added to the images text.
Other details that may be helpful:
Nothing should be observably different when rancher-images texts are produced for tagged releases. QA can verify that an rc tag has a rancher-images text that includes k3s-upgrade images for compatible k3s versions in https://raw.githubusercontent.com/rancher/kontainer-driver-metadata/dev-v2.5/data/data.json. Each compatible version will cause some supporting images to be added as well. Can confirm by making sure klipper-helm images are add to images-text.

Aiming for 2.5.6 on this one as I am assuming it will merge before then, but it can slip to 2.5.7 without a problem.

This is validated on rancher:v2.5.6-rc4
Steps:

get the compatible k3s versions from the here
get the rancher-images.txt from rancher:v2.5.6-rc4's release page

Results:

there are four compatible k3s versions for rancher:v2.5.6

v1.17.17+k3s1
v1.18.15+k3s1
v1.19.7+k3s1
v1.20.2+k3s1

the klipper-helm images are in the rancher-images.txt file

rancher/klipper-helm:v0.2.3
rancher/klipper-helm:v0.2.7
rancher/klipper-helm:v0.3.0
rancher/klipper-helm:v0.4.3

the k3s-upgrade images are in the rancher-images.txt file

rancher/k3s-upgrade:v1.17.17-k3s1
rancher/k3s-upgrade:v1.18.15-k3s1
rancher/k3s-upgrade:v1.19.7-k3s1
rancher/k3s-upgrade:v1.20.2-k3s1

Since we will not get RCs from the master branch soon, I created a forward port issue for tracking it on the master branch https://github.com/rancher/rancher/issues/31121

Re-opening because this was reverted as secondary parallel fix was implemented.

Should just test that rancher-images.txt looks how it normally does on release.

This is re-validated on v2.5.6-rc6

All k3s-related images are in the rancher-images.txt file
All regular tests for air-gap installation are passed


Unknown custom element:

Does installing nuxt-validate requires to import ValidationProvider components or am I doing something wrong?
Here is my nuxt.config.js
modules: [ 'nuxt-validate'],
nuxtValidate: {
lang: 'en',
},

@fmcdigital do you solved this? If I have to import manually ValidationProvider in my pages, what's the point of using this module and not vee-validate directly?


Target es2022

We afaik support node 18+
https://github.com/microsoft/TypeScript/wiki/Node-Target-Mapping#node-18
The @tsconfig/node18 package is even targetting es2023. But I think this is because node 18.0.0 was supporting es2022 and later updated v8 and supports later es2023.
Also @tsconfig/node uses differnt module and moduleResolution (in both cases node16) which should be actually the better option, but I did not touch that.
Imho semver-major.

Can you please split this, the 2 changes aren't related.

We afaik support node 18+
https://github.com/microsoft/TypeScript/wiki/Node-Target-Mapping#node-18
The @tsconfig/node18 package is even targetting es2023. But I think this is because node 18.0.0 was supporting es2022 and later updated v8 and supports later es2023.

We don't want to use a version that is too new in order to support the most versions possible.
I don't think this has much of an effect, since we use esbuild and typescript only for types. It would probably only effect the tests.

Also @tsconfig/node uses differnt module and moduleResolution (in both cases node16) which should be actually the better option, but I did not touch that.

Using node16 module resolution is tricky... It introduces many errors. It would be nice to do so, it would probably require removing CJS builds which is a to-do for the next major versions of Octokit.

Imho we already use fetch and stuff in alot of octokit/packages, which is only usable in node 18+. So this should be semver-major release and then used in the plugins.
So this should be the lowest common denominator for node 18 and above.

I made #22
It's made with Node 18+ compat and ESM in mind

I am totally fine with it ;)


feat: support gRPC endpoints in core

This is an implementation of a streaming API for blocks in core.
Helps close https://github.com/celestiaorg/celestia-app/issues/3421 but not sure it entirely closes it.
It can easily be used:
package main

import (
	"context"
	"fmt"
	coregrpc "github.com/tendermint/tendermint/rpc/grpc"
)

func main() {
	client := coregrpc.StartBlockAPIGRPCClient("tcp://localhost:9090")

	// get a streamed block
	blockStreamer, err := client.BlockByHeight(context.Background(), &coregrpc.BlockByHeightRequest{Height: 10})
	if err != nil {
		panic(err)
	}
	resp, err := blockStreamer.Recv()
	if err != nil {
		panic(err)
	}
	fmt.Println(resp)

	// get a commit
	commit, err := client.Commit(context.Background(), &coregrpc.CommitRequest{Height: 10})
	if err != nil {
		panic(err)
	}
	fmt.Println(commit)

	// listen for new heights
	streamer, err := client.SubscribeNewHeights(context.Background(), &coregrpc.SubscribeNewHeightsRequest{})
	if err != nil {
		panic(err)
	}
	for {
		resp, err := streamer.Recv()
		if err != nil {
			panic(err)
		}
		fmt.Println(resp)
	}
}

Ps: I didn't add the tests because I didn't find a direct way of mocking the environment without polluting the rest of the repo (exporting some methods, adding new helpers, etc). And I think since the implementation is simple, just querying the block/state stores for results, it's fine to leave it untested.

Just found out that once we enable the app grpc, these endpoints get overridden, I'll be looking into it

We register these endpoints in cosmos-sdk which allow using the same endpoints and not 2
celestiaorg/cosmos-sdk#416

Ah great! Can we register it just in celestia-app?

the grpc gets sealed in cosmos-sdk... and there is no way to change it app if I understand correctly

Hmm but I recently added a new grpc server to celestia-app for the TxStatus endpoint. I did it here:
https://github.com/celestiaorg/celestia-app/blob/a742bd3245dde76898a4514ac116792025fb9f57/app/app.go#L737
Can you not do the same?
Why I'm asking this is that if we want to unfork ourselves from the SDK we should be trying to reduce the changes we need to make there

Interesting, I like that. I'll give it a go. Thanks for pointing that

@cmwaters re on registering these endpoints in app:
I tried moving all the endpoints definitions to app. However, I couldn't import the tendermint proto from there due to dependency conflict in buf.
Then, I tried to generate the protobuf grpc gateway to register the endpoints similar to what was done with TxStatus but that requires the endpoints to be in a cosmos-sdk repository for them to be generated.
So, unless I am missing something, we can only have the endpoints in here and have those couple lines added in cosmos-sdk. Otherwise, we will need to have the endpoints served under a different port.
Please let me know if there is another way that I am missing.

per sync, we will run this change with a Celestia-node bridge node to see if all works fine

This branch is now ready to be merged:

Tests added
TLS support added to utility as per @vgonkivs request
latest version tested in node against an app running this version and all seems to be in place


Default ios8BrowserCrash workaround to "off/false"

See https://twitter.com/fineuploader/status/576084483268558848.

completed in 5.2.0-20


I believe there is a bug in webpack-plugin

const outputFolder =  this.opts.writeToDisk.filename || this.compiler.options.output.path
shouldn't it be
const outputFolder =  this.opts.filename || this.compiler.options.output.path
filename prop shouldn't be under writeToDisk

anyone?

It's working exactly as written in the documentation https://loadable-components.com/docs/api-loadable-webpack-plugin/

Yes no problem here.


set version of spotify's docker-maven-plugin in order to be able to comp...

set docker-maven-plugin version in order to be able to compile the project

Coverage remained the same at 26.88% when pulling f3a17ba060f214e83a833805a3876b8a67a1d048 on feature/set-spotify-docker-maven-plugin-version into 0c9f0d6b7209465a5ca63e0e5f030a38573ef267 on master.


Is Forseti still under active development?

Is Forseti still a going concern in 2023? Or is the same functionality wrapped into SCC now?

Hello, Forseti is not in development and will be archived by June 2023. Visit SCC and the new Policy Intelligence suite from GCP for equivalent functionnality.


ImportError: DLL load failed while importing _process: The specified module could not be found.

Hello Max,
Greetings for the day!
While I was trying to import process and utils module from rapidfuzz, I have encountered with the below error.
ImportError: DLL load failed while importing _process: The specified module could not be found.
I have C++ 2019 redistributable  installed on my laptop.
I also can see the process.py in my anaconda package folder.
I have installed both "0.11.1" and "0.10.0" versions but no luck in both cases.
Please help me in fixing this issue, Thanking you!

Hm thats strange, since process is implemented in python, so there is no _process, that should be imported :confused:
(For me it works fine on Windows)
_process did exist until something around version 0.7/0.8 (I do not remember when exactly it was removed), so when working with a new version this should not occur. Are you really sure your actually using these version? (I guess I should add a version for future versions ...)

Hello Max,
I have attached the snip of my error for your reference, please have a look
I tried in 2/3 different machines, same error pops up

I could not reproduce this myself. For me this error only occurs when the C++ redistributable is missing.
Does this error occur with other software thats using C/C++ aswell like for example python-Levenshtein?

closed because the error could not be reproduced and there was no update from the the issue creator.


Seems to get confused by the v1 and v2  branches.

Package manager/ecosystem
Go

👋 Hey there! Sorry for the glacially slow response... we've been a bit buried the past few years, and only just now starting to dig through some of our backlog.
I'm a big fan of Hugo, thanks for your hard work there!
This issue is pretty old, and we've pushed a lot of bugfixes since then... is this still a valid issue?
Also, often with metadata issues like this, we use whatever the package maintainers give us, so while I haven't dug into the code, there's a 50/50 chance that this is an upstream issue with github.com/nicksnyder/go-i18n and not dependabot-core.
But if you're still seeing it in recent Dependabot PRs (I see you just recently merged a Dependabot PR two days ago) then please let me know... otherwise I'll close this.

@jeffwidman I have no idea if this is still an issue, I haven't reacted negatively to it lately, so I suspect it's fixed. Closing.

Thanks for the quick followup @bep.


cannot compile current kivy master

this commit breaks it: 0e46e3d6b302c94e82843fb08000b0ba12e67bda
I get the same error as described in the comment

@ecdsa can you give some more details about what you are trying to do? Compile on what system and for what architecture?

I was initially trying to build an APK with buildozer.
However, I also get the same error when trying to build kivy on ubuntu (without buildozer).
I do "sudo python setup.py install"
and I get
cythoning kivy/graphics/instructions.pyx to kivy/graphics/instructions.c

 Error compiling Cython file:
 ------------------------------------------------------------
 ...
             if do_parent == 1 and self.parent is not None:
                 instrs.append(self)
                 self.parent.flag_update(do_parent=1, _instrs=instrs)
             self.flags |= GI_NEEDS_UPDATE
     ELSE:
         cpdef void flag_update(self, int do_parent=1):
              ^
 ------------------------------------------------------------

 kivy/graphics/instructions.pyx:75:14: Return with value in void function

 Error compiling Cython file:
 ------------------------------------------------------------
 ...
             if do_parent == 1 and self.parent is not None:
                 instrs.append(self)
                 self.parent.flag_update(do_parent=1, _instrs=instrs)
             self.flags |= GI_NEEDS_UPDATE
     ELSE:
         cpdef void flag_update(self, int do_parent=1):
              ^
 ------------------------------------------------------------

 kivy/graphics/instructions.pyx:75:14: Cannot convert 'void' to Python object

I get this warning at that same point, but no error. Make sure you have the correct cython(0.23) version, can't think of anything else that would cause such an issue.
cythoning kivy/graphics/instructions.pyx to kivy/graphics/instructions.c
building 'kivy.graphics.instructions' extension
x86_64-linux-gnu-gcc -pthread -DNDEBUG -g -fwrapv -O2 -Wall -Wstrict-prototypes -g -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -I/usr/include/python3.5m -I/home/udiboy/.apps/venvs/kivy3/include/python3.5m -c kivy/graphics/instructions.c -o build/temp.linux-x86_64-3.5/kivy/graphics/instructions.o
kivy/graphics/instructions.c: In function ‘__pyx_pf_4kivy_8graphics_12instructions_11Instruction_4flag_update’:
kivy/graphics/instructions.c:192:53: warning: left-hand operand of comma expression has no effect [-Wunused-value]
 #define __Pyx_void_to_None(void_result) (void_result, Py_INCREF(Py_None), Py_None)
                                                     ^
kivy/graphics/instructions.c:3278:15: note: in expansion of macro ‘__Pyx_void_to_None’
   __pyx_t_2 = __Pyx_void_to_None(NULL); if (unlikely(!__pyx_t_2)) {__pyx_filename = __pyx_f[0]; __pyx_lineno = 75; __pyx_clineno = __LINE__; goto __pyx_L1_error;}

I have Cython version 0.20.1post0

ok, it compiles after I installed cython 0.23
this is still a bug:  setup.py should abort if the correct version of cython is not detected

We could surely add that as a dependency check! Would you open another issue about that, closing this one.


Add images to compound and reaction pages

Hello James,
My main concern is in bandwidth restricted circumstances, some user experience issues may be incurred, as I understand you are planning to embed images directly on the page, for example in the compounds page:
<img id="compound-image" ng-src="{{getImagePath(cpd.id)}}"

            height="325" data-toggle="modal" data-target="#modal"

            tooltip-trigger tooltip="Click to expand.">

Also I don't follow some of the code, like the code in the stoichiometryToImgs directive... why do you need to call $compile?
Suggest reconsider the underlying design, and address fundamental questions.  I think perhaps adding hyperlinks only (to the images), to the Compound/Reactions pages, rather than the images themselves.  I am also concerned about Chris's yesterday  comment on slack:
"I don’t think structures should appear in the reaction tables. It is too busy, and there will always be other data we would rather show (pathways, roles, subsystems, aliases). I think we should have the structure view in the reaction roll out that appears when ever you click on a reaction in modelseed."
Let's talk about all this in the next scrum?
Thanks you,

arman


[BEAM-5355] GroupByKey Load IT

Detailed description in the JIRA ticket.
@pabloem could you take a look?

Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

It will help us expedite review of your Pull Request if you tag someone (e.g. @username) to look at it.
Post-Commit Tests Status (on master branch)

Lang
SDK
Apex
Dataflow
Flink
Gearpump
Samza
Spark

Go

---
---
---
---
---
---

Java

Python

---

---
---
---
---

CC: @echauchot

This looks good to me. I'd just add one or a couple distribution metrics to count time spent blocked, waiting to load the iterable with the values (e.g. time of first iteration, time of all iterations). WDYT?

Closing this PR. An alternate solution (more runners supported out of the box, runs without perfkit) is proposed here: https://github.com/apache/beam/pull/6571


Update README.md

Updated level of support description based on text from @MattF-NSIDC.

📚 Documentation preview 📚: https://earthaccess--434.org.readthedocs.build/en/434/

Should we merge?


Should we archive old code in the KG2 repository?

The KG2 repository is getting a little bit large. The root folder for the repository has 128 files (including folders). It is unruly to look through. I propose organizing it and archiving files that are no longer needed (such as outdated documentation). This could be tricky, because of the dependencies that are involved. However, I think it would solve some confusion during development, especially if files that are not remotely up to date are not side by side with our core files.

Solved in KG2.9.3


Add exception logging

Fixes #1959.

Pull Request Test Coverage Report for Build 6909

1 of 10 (10.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.02%) to 71.785%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

sharding-proxy/sharding-proxy-backend/src/main/java/org/apache/shardingsphere/shardingproxy/backend/schema/LogicSchemas.java
1
10
10.0%

Totals

Change from base Build 6908:
-0.02%

Covered Lines:
10851

Relevant Lines:
15116

💛  - Coveralls


add french translation of the README file

Simply adds french translation for the README file.
Will try to translate CODE_OF_CONDUCT.md and CONTRIBUTING.md when I will have more time ^^

@all-contributors please add @yafkari for translation language :)

@yafkari You need to link in the original README english file:

Like this :)

Hey, you have git conflicts. Please solve them :)

Hey we're changing from MIT to GPLv3 because some of our projects are licensed with that, do you approve? If you do not approve we will be forced to delete your code and rewrite it 😢
By approving of this change, you are agreeing to re-license the code you wrote under GPLv3.


[UBS Tariffs page_Create pricing card] The description of the validation of the "Створити" button in AC2 of US #4202 contradicts AC4.

Environment: Mac OS Ventura 13.2.1, browser Version 112.0.5615.137, it's version 06.05.2023.
Reproducible: always.
Steps to reproduce

Go to #US4202;
Compare AC2 with AC4.

Actual result
According to the description of the validation of the "Створити" button in AC2: "...When the user selects any points - the button will be active....". But according to the AC4: "To create and save a new pricing cart the user should fill all fields. Otherwise the button “Створити” should be disabled."
Expected result
AC2 should be clarified for the validation of the "Створити" button: "...When the user selects all mandatory points - the button will be active....".
User story and test case links
E.g.: "User story #4202

Resolved as a change to the US


Support for stdin for 'az storage blob upload' command

Is your feature request related to a problem? Please describe.
After running the following command:
$ echo foo bar buzz | az storage blob upload --container-name mycontainer -n test.txt -f /dev/stdin
{
  "etag": "\"0x8D...\"",
  "lastModified": "2022-01-13T21:50:19+00:00"
}

the blob content is empty.
Describe the solution you'd like
Correct content of the file should be uploaded.
Describe alternatives you've considered
Using a temporary file.

storage

Can you install storage-blob-preview extension with az extension add -n storage-blob-preview and try az storage blob upload --data? --data can take input string as blob content directly.

Can you install storage-blob-preview extension with az extension add -n storage-blob-preview and try az storage blob upload --data? --data can take input string as blob content directly.

% az storage blob upload -c mycontainer --data "Foo Bar" -n test.txt
...
The command failed with an unexpected error. Here is the traceback:
'>' not supported between instances of 'NoneType' and 'int'
Traceback (most recent call last):
  File "/usr/local/Cellar/azure-cli/2.25.0/libexec/lib/python3.8/site-packages/knack/cli.py", line 231, in invoke
    cmd_result = self.invocation.execute(args)
  File "/usr/local/Cellar/azure-cli/2.25.0/libexec/lib/python3.8/site-packages/azure/cli/core/commands/__init__.py", line 657, in execute
    raise ex
...
  File "/usr/local/Cellar/azure-cli/2.25.0/libexec/lib/python3.8/site-packages/azure/cli/core/commands/command_operation.py", line 121, in handler
    return op(**command_args)
  File "/Users/user/.azure/cliextensions/storage-blob-preview/azext_storage_blob_preview/operations/blob.py", line 666, in upload_blob
    _adjust_block_blob_size(client, blob_type, length)
  File "/Users/user/.azure/cliextensions/storage-blob-preview/azext_storage_blob_preview/operations/blob.py", line 613, in _adjust_block_blob_size
    if length > 50000 * 4 * 1024 * 1024:
TypeError: '>' not supported between instances of 'NoneType' and 'int'
To open an issue, please run: 'az feedback'

Hi @kenorb, Can you explicitly specify --length:
az storage blob upload -c mycontainer --data "Foo Bar" --length 7 -n test.txt

We will fix the extension bug in next vesion, sorry for the inconvenience.

Hi @glanchow, we have supported --data in main CLI now, you don't have to install extension any more. Here's an example using stdin input with pipe:
echo $data | az storage blob upload --data @- -c mycontainer -n myblob --account-name $accountName

Why is passing the length necessary? When working with streams, you might not know the size of the blob in advance.

@chribsen If you use the command directly from main CLI, --length is not needed any more. The bug has been fixed in main CLI.

This feature technically uploads something but it doesn't seem to be uploading my files correctly. Not sure if we should close this one and then open a new issue but when I do something to the effect of:
cat my-textfile.txt | xz | az storage blob upload -c my-channel --data @- --content-type application/x-xz

and then re-download the file, the file has:
7zXZִF!t/G]&J

For the first line and the xz program does not recognize the file. I have tried this with zst and other binary files and I can't seem to get it to upload the file in the correct format. I suspect it has something to do with the handling of binary data since text files appear to work, but I have no way of confirming that.
What should I do?

@WattsInABox when pipe is not used, but you use --data @/path/to/file data end up in the storage as base64 encoded. I haven't figured out how to get un-mangled data using pipes, but there seems to be similar issue https://github.com/Azure/azure-cli/issues/22810 with az rest.

I have the same issue like
https://github.com/Azure/azure-cli/issues/20980#issuecomment-1267449510
It seems that binary stdin does not correctly work with az storage account.
very need to xz and az as a pipe


Implement account restoration

I started this in PR #92, but decided it was out of scope. Here are some things that I had started or planned on doing:

Users::RestorationsController would be implemented like Devise::PasswordsController and is responsible for initiating and completing an account restoration (initiating means sending an email with a token link in it)
We'll need to create a module, sayRestorable, that is the equivalent of Devise's Recoverable. It will be responsible for handling the token and undoing the soft delete, just like Recoverable is responsible for token handling and password resetting.

Here are some pending specs for this issue (feel free to change them):
# spec/features/user_soft_delete_spec.rb
...
scenario 'User cannot login after deleting their account' do
  ...
  # expect(flash).to have_link 'restore your account' # TODO: implement this
  ...
end
...
scenario 'Soft-deleted user tries to re-register with same email' do
  ...
  # expect(flash).to have_link 'restore account' # TODO: implement this
  ...
end
...

# spec/features/users/restoration_spec.rb
require 'rails_helper'

RSpec.feature 'User account restoration', type: :feature do
  scenario 'User initiates account restoration', :js do
    skip 'not implemented yet'
    user = create :user, :soft_deleted
    visit welcome_index_path

    click_on 'Restore account'
    fill_in 'Email', with: user.email
    click_on 'Restore'

    expect(page).to have_content 'Glad to have you back! We\'ve sent account '\
                                 'restoration instructions to your email.'
    expect(emails).to have(1).email
  end

  scenario 'User completes account restoration' do
    skip 'not implemented yet'
    user = create :user, :soft_deleted
    post user_restore_path, email: user.email

    email = ActionMailer::Base.deliveries.last
    visit email.body.find('.create_restoration')

    expect(page).to flash_message 'Your account has been successfully restored'
    expect(user).to be_signed_in
  end
end

Actually, it might be easier to do it the way Facebook does and just un-delete the account if the user logs back in. If we do it this way, we should find a way to allow soft-deleted users to use the forgot password feature.


Remove changed flag from expanded folders in explorer to reduce the noise

Hi and thank you guys for the awesome job you have done so far.
I'm not sure if there's already an option to config this, so I'm requesting this as a new feature.
Look at this picture

When you add a file or change something in the project, there comes a U, A, M, etc flag into the explorer which helps you find the changes since last commit (which is great by the way).
But there also come quite a few dot flags on the containing folders up to the root. This part is a bit noisy I think and could be better. for example I have now changed only one file and there are 5 flags (beside that badge on the Git tab) showing me that.
I believe those dots are only helpful if the folder is collapsed and therefor we are unable to track inside changes. But if the folder and sub-folders are expanded, it's not necessary to flag all the folders in the path.
Thank you

Just in case this won't be implemented you can try the path of hacks with extension Custom CSS and JS Loader
.explorer-folders-view .monaco-tree-row.expanded .explorer-item::after {
	opacity: 0 !important;
}

"git.decorations.enabled": false


[Question] --no-download-archive --no-mark-watched when printing video information

Checklist

[x] I'm asking a question
[x] I've looked through the README and FAQ for similar questions
[x] I've searched the bugtracker for similar questions including closed ones

Question

I can't print information about the video if it is in the archive. For example:
yt-dlp --print id --playlist-end 1 https://www.youtube.com/playlist?list=WL prints an empty line if the first video is in the archive
I have to add the parameter "--no-download-archive".
I also need to add the "--no-mark-watched " parameter so that the video is not marked as viewed if the parameter is in the configuration file. Can you fix it?

The point of using a download archive is that the video is not processed if it is the archive. So this is intended behavior

The point of using a download archive is that the video is not processed if it is the archive. So this is intended behavior

Then it is not possible to print information about the playlist. There is also a problem with --mark-watched.

It is possible. Just don't use --download-archive. Or use --no-download-archive or --no-config to override the setting in configuration. You can't pass an option to yt-dlp and expect it to ignore it. There are usecases where --print and the archive are used together intentionally

It is possible. Just don't use --download-archive. Or use --no-download-archive or --no-config to override the setting in configuration. You can't pass an option to yt-dlp and expect it to ignore it. There are usecases where --print and the archive are used together intentionally

OK. When I used the "-J" (dump single json) parameter, the entire playlist was marked as viewed. Is this intentional behavior?

Marked as watched? yes, that is intended.
If it got written to archive, there is some issue (unless you used some other option to force it). If that is the case, show me the verbose log

Marked as watched? yes, that is intended.
If it got written to archive, there is some issue (unless you used some other option to force it). If that is the case, show me the verbose log

I just don't understand why the video is marked as watched if I'm just "--print" information.

Marking as watched is part of the extraction process. It doesn't matter if you downloaded it or not. It could be argued that it should work like download-archive, but this is how youtube-dl handles this, and the hassle of changing this is not worth it since you can just use --no-mark-watched when simulating

I will update the docs to make this clearer


[Bug] Dispatcher will be closing and reopening when Key_shared consumers have different policies (AUTO_SPLIT/STICKY, allowOutOfOrderDelivery true/false)

Search before asking

[X] I searched in the issues and found nothing similar.

Read release policy

[X] I understand that unsupported versions don't get bug fixes. I will attempt to reproduce the issue on a supported version of Pulsar client and Pulsar broker.

Version
all released versions including master branch
Minimal reproduce step
The conclusion is currently based on the source code:
https://github.com/apache/pulsar/blob/766d2a407196533832184447c25498c6a82f7a86/pulsar-broker/src/main/java/org/apache/pulsar/broker/service/persistent/PersistentSubscription.java#L287-L309
What did you expect to see?
When multiple consumers are using different policies, this should be properly handled.
One possibility is to keep the policy of the connected consumers and reject any other consumers and return a proper error message.
What did you see instead?
Based on the source code, it looks like the solution cannot work:

a new dispatcher is created while the existing dispatcher is active
the existing dispatcher is closed asynchronously
no proper errors messages are logged or logged that could help resolving the situation

Anything else?
No response
Are you willing to submit a PR?

[ ] I'm willing to submit a PR!

@lhotari I tried to implement this: https://github.com/phil-cd/pulsar/commit/e241cff3aa6f0273138b05eb61bac14e0153a7d6
When the policy of a new consumer is incompatible with the existing consumers of the subscription it is rejected.
I also wrote a test but it works only when disabling the transaction coordinator in the setup() method. I could not find out how to make the test work with the transaction coordinator being enabled. When calling addConsumer() on the subscription the pendingAckHandleFuture seems to block.

@lhotari I tried to implement this: pdolif@e241cff When the policy of a new consumer is incompatible with the existing consumers of the subscription it is rejected.
I also wrote a test but it works only when disabling the transaction coordinator in the setup() method. I could not find out how to make the test work with the transaction coordinator being enabled. When calling addConsumer() on the subscription the pendingAckHandleFuture seems to block.

makes sense. good work, @pdolif! Thanks for the contribution.


Fixed Catkin_make Issue and Gazebo Blacking problem

A couple of people raised an issue saying their catkin_make failed due to some dependencies and also some people faced problem while running gazebo simulation that the screen became completely black. I've fixed both those problems and everything is tested on multiple PCs. Hope you merge this fix @XRobots so that no one else face this problem through your existing branch

Thanks


Migrate token and collection module from link

Summary
Migrate token and collection module from line/link.
token module is an implementation of ERC-20 and collection module is an implementation of ERC-1155.

For Admin Use

[ ] Not duplicate issue
[ ] Appropriate labels applied
[ ] Appropriate contributors tagged
[ ] Contributor assigned/self-assigned

Collection module not ready.


Bump blockifier to rc7

This change is

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

Comparison is base (65eccfa) 67.18% compared to head (63a3c1b) 67.18%.

Additional details and impacted files
@@              Coverage Diff              @@
##           main-v0.13.0    #1150   +/-   ##
=============================================
  Coverage         67.18%   67.18%
=============================================
  Files                52       52
  Lines              6734     6734
  Branches           6734     6734
=============================================
  Hits               4524     4524
  Misses             1798     1798
  Partials            412      412

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


BE/API support for comments

Need
Some tasks will need comment threads associated with them when information needs to be exchanged to complete them. A single comment can accompany a status change or act as a note about the task or other entity as required.
Approach
We want to be able to add comment threads to the different entities, Atlas, Source Study etc. but do not want to have to drag the comment lists around when listing or processing the entities. To separate the comments from the entities we will have a comments table, and then let the entity hold one or more ids to the a thread.
Model  - add a "comments" table
On the comment object list

id (uuid)
threadId (uuid)
createdAt
updatedAt
created by (user id)
updated by (user id)
text ( string )

APIs
Create a comment Thread
POST /comments
Reply to a thread
POST /commennts/threadId/comment
Edit a comment
PUT /commennts/threadId/comment/commentId
Delete a comment
DELETE /commennts/threadId/comment/commentId
We wont implement delete thread.
Authorization
Any logged in user can comment on anything (for now)
Anyone can edit/delete thier own comment.
Content Admins can edit/delete all comments

Complete!


Remove Japplis Website Optimizer version 4.1

[x] Have you signed the Contributor License Agreement?
[x] Have you checked that there aren't other open pull requests for the same manifest update/change?
[x] This PR only modifies one (1) manifest

Note: <path> is the name of the directory containing the manifest you're submitting.

Removed 4.1 as latest version is 4.2.
Microsoft Reviewers: Open in CodeFlow

URL: https://www.japplis.com/website-optimizer/versions/WebsiteOptimizer-4.1.exe
Status Code: 200
(Automated message - build 861)


Colors clashing with vim solarized dark theme

Looks like updating lightBlack to #002b36 does the trick!
Before:

After:

Since the author haven't answered back I forked this repo, fixed this issue and created a new plugin for hyper calles hyper-solarized-dark2 in https://github.com/estebanrao/hyper-solarized-dark


story: P1-90

deleting 'description' field from request body when registering a user
modifying Category Schema to have enum values
adding a Tag Schema and adding it as a key for Recipe Schema
adding a Ingredient Schema
modifying the data type to be 'Ingredient' for  the key Ingredient in Recipe Schema
CreateRecipe backend function done
'Write' icon and 'User' icon on Landingpage now navigates to the corresponding pages
in PrivateRoute file, token from the local /session storage is used to check authentication instead of getting the token from use selector because of a delay in grabbing the token data from the redux
recipe creation and safe action functions in userSlice and recipeSlice
saved recipe gets stored in local storage
clicking on the 'write' icon on LandingPage triggers to check if there's a saved recipe. If there is, then CreateRecipePage gets loaded with that recipe that is saved in local storage
trying to get out of CreateRecipePage while having something written will show the user prompt alerting them to save their recipe before they leave the page

UserId 없음요

_id 저게 userId 임 @younghoonyou


Sanity check-quality-grades/diagnostic

Hi Team,
I have noticed the below-given page is without content. Please look into this and do the needful.
quality-grades/diagnostic

As per the pardeep update, the content is received yet so the page is blank


Test C# driver with CockroachDB

Re: Install Client Drivers
Issue Description
Where is C# driver?
Suggested Resolution

@talley We haven't tested or vetted Npgsql. If you want to test it out for us, we'd be excited to have the contribution!

@talley, a quick update: We're close to publishing C# code samples and tutorials. Should be within the next week or two. You can take an earlier look at the code samples here: #1991

cc: @BramGruneir, @awoods187

@talley, we just added a tutorial on building a C# app with CockroachDB. Please take a look and let us know if you have any questions.


Dato

display "Dato" from NGU togeter with data_shape from IMR

The enchancement is working well in test. There is a solution for both single layers end multiple layers-call. The issue of updating the WFS-call is discussed and approved. If there isn't any other concerns, the enchancement can be implemented on main Mareano-maps.
NB! We must remember that Dato shows the creation date of the newest feature in a data set, not the latest update of the data.

Saken er lukket.


Fixed wrong default tax rate

Line: 964
Changed: $tax = 119;
To: $tax = 19;
Like it's done in line 369 and line 863 before.

Hi @haruka, thanks for your PR.
Please rebase your PR and update the target branch to 5.1 or 5.2. I'll schedule your PR afterwards.

Hello,
thank you for creating this pull request.
I have opened an issue on our Issue Tracker for you. See the issue link: https://issues.shopware.com/#/issues/SW-17220.
Please use this issue to track the state of your pull request.


How to click to detail Activity Wallpaper ?

Thanks for template :) i hope add feature detail Activity Wallpaper

I feel like there is no extra information to show on that activity
So i didn't added that
Any suggestions what should i add in detailed wallpaper activity?

Add button save image and favorite :) and i hope add menu favorite in navigation drawer,
thanks architjn for template


Improve internal handling of SSL certificates

New PR to replace https://github.com/confluentinc/cp-ansible/pull/751 because of issues with CI-pipelines.
Description
Use Ansible module community.crypto.certificate_complete_chain to make SSL cert handling more robust. Targeting the 7.0.x branch, since older branches might have users with older Ansible versions - that do not support using the community.crypto collection.
Fixes #737 #738
Type of change

[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update

How Has This Been Tested?
I do not currently have an environment available to run CP 7.x, so I trust the CI to catch any problems.
Test Configuration:
Checklist:

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] Any dependent changes have been merged and published in downstream modules
[ ] Any variable changes have been validated to be backwards compatible

New PR rebased on top of 7.0.x branch gives:
[2022-02-28T10:08:59.323Z] TASK [Install OpenSSL Rsync and Java] ******************************************
[2022-02-28T10:09:38.009Z] fatal: [zookeeper11]: FAILED! => {"changed": false, "msg": "Failure talking to yum: Cannot find a valid baseurl for repo: base/7/x86_64"}

base/7/x86_64

Thats a repo from the base image geerlingguy/docker-centos7-ansible - Their hosting infra may have had issues when the test was ran - Checking the image myself, it doesn't seem to be having an issue:
aegelhofer@MWR542RXK7 ~ % docker run -it geerlingguy/docker-centos7-ansible yum --disablerepo='*' --enablerepo=base makecache
WARNING: The requested image's platform (linux/amd64) does not match the detected host platform (linux/arm64/v8) and no specific platform was requested
Loaded plugins: fastestmirror, ovl
Determining fastest mirrors
 * base: mirror.arizona.edu
base                                                                                | 3.6 kB  00:00:00
(1/4): base/7/x86_64/group_gz                                                                                | 153 kB  00:00:00
(2/4): base/7/x86_64/filelists_db                                                                                | 7.2 MB  00:00:01
(3/4): base/7/x86_64/primary_db                                                                                | 6.1 MB  00:00:05
(4/4): base/7/x86_64/other_db                                                                                | 2.6 MB  00:00:05
Metadata Cache Created

So I would re-run your test.

So I would re-run the CI check.

@andrewegel How do I trigger a re-run?

So I would re-run the CI check.

@andrewegel How do I trigger a re-run?

I can't seem to trigger one myself in this Jenkins CI runner - But you can push an empty commit with git commit -m "Empty commit to trigger CI" --allow-empty to get one started.

Thanks @andrewegel! A rebase and force push seems to get the build further.

Thanks @andrewegel for having a look. Going forward pushing an empty commit would be the only way to re-trigger the run for community or can we request for re-build privilege. At times, I do need some rights on these jobs to start/stop.


Iron support

couple it with new gazebo while announcing. Gazebo classic will not be supported from here onwards.


Use older libraries and exclude some

See #334.

There is the issue to test OAIPMH still open, I find it not so easy to test this without doing an actual httpUrlConnection which we agreed on to not do in the library. I updated #325 to point to the encoding issue to test that also.

Got the branch built by using proper version of xalan library. Requesting your review again @fsteeg.

As discussed in the standup, I tried keeping the Xalan dependency at 2.7.1, keeping the exclusions. This got me a NoClassDefFoundError org.apache.xml.serializer.TreeWalker. Searching that, I found a solution of setting a system property: System.setProperty("javax.xml.transform.TransformerFactory", "com.sun.org.apache.xalan.internal.xsltc.trax.TransformerFactoryImpl"). This fixes that TreeWalker error, but also, when removing the exclusions, the original error. I then moved the dependency up to 2.7.2, all still looks good for me. Pushing that here.

Seems to work.
Pro: it uses the newest xalan version.
Con: we have more dependencies. Also, your solution is somwhere commented as a "workaround" (I don't know what's the implication).
What way is the better one?

Con: we have more dependencies.

Why more dependencies? You mean setting the property?

Also, your solution is somwhere commented as a "workaround"

As far as I understand, it's a workaround to set it yourself as a user of their project, and their solution was to do it in their own code: https://github.com/wmz7year/Openfire/commit/3d88aaf (in that sense, it would be a workaround if a metafacture user had to set it in their own code).

What way is the better one?

I think it's better to use the newer Xalan lib, which should avoid other issues.

Why more dependencies? You mean setting the property?

I mean now there are no exclusions of libraries. So there are more dependencies. Or does it not work in this way? Do exclusions none-the-less load dependencies and set them into the classpath? If that's the case, dump my idea. Otherwise, I so often experienced problems with libraries on the classpath having the same name but coming in different versions that it's sometimes real hard to find the problem. So, avoiding unnecessary dependencies is better in my experience.
Re workaround:
yes I think you are right.

I mean now there are no exclusions of libraries. So there are more dependencies. Or does it not work in this way?

I think the problem is always a conflict of transitive dependencies. So by excluding them, we actually say: don't use the ones pulled in by Xalan itself here. They are still dependencies of Xalan, so they need to come from some other place. Where is actually undefined at this point, so while often a good solution to fix a problem, I think exclusions actually increase the intransparency. Without exclusions, it's clear the library uses the dependencies as it declares them itself (in its pom etc.).

come from some other place. Where is actually undefined at this point,

It comes with Java Class Library.
The dependencies in the metafacture-biblio module have impact on other modules, like e.g. org.metafacture.metamorph.test.MetamorphTestCaseTest, so I still think using as less dependencies makes the whole  more stable. Also transparency.
For the complex of XML handling in java see also https://stackoverflow.com/questions/11952289/serializing-supplementary-unicode-characters-into-xml-documents-with-java. It's quite baffling or say: complex to see what uses when.

It comes with Java Class Library.

The xml-apis sound like that, but xalan.serializer and xercesImpl too?
In general however, I don't think it's less dependencies, it's just a question who pulls them. Xalan has these three dependencies that are excluded, it needs to get them somewhere, right? But I don't really see where. Running ./gradlew :metafacture-runner:dependencies only shows them as the Xalan dependencies. So I don't know. Both ways are a little weird, running with 2.7.0 + exclusions instead of 2.7.2 or setting an internal implementation class in a system property. Since both contain weirdness (exclusions, property) I'd favor the higher version.

The package java.xml as part of the Java Class Library comes with copies of xalan and xerces, see e.g. in  https://stackoverflow.com/questions/11952289/serializing-supplementary-unicode-characters-into-xml-documents-with-java. :

With the default JDK (1.6 and 1.7), TransformerFactory returns a com.sun.org.apache.xalan.internal.xsltc.trax.TransformerImpl, which uses com.sun.org.apache.xml.internal.serializer.ToXMLStream ...

It's worthwhile to read that section.

The package java.xml as part of the Java Class Library comes with copies of xalan and xerces

Right, now I understand. Then how about this: we add back the exclusions, but use 2.7.2 + property.
So we have both the latest version and reduced XML dependency copies (pushed in https://github.com/metafacture/metafacture-core/pull/335/commits/3ecdb4783f3a7693c87e1ec8c4f4ef4457cd364e).

but use 2.7.2 + property

would love to, but then tests in other modules fail (see note here https://github.com/metafacture/metafacture-core/pull/335#issuecomment-717110460)

would love to, but then tests in other modules fail (see note here #335 (comment))

Right, sorry, only ran the Flux test. We could set the property in the build for metamorph-test: https://github.com/metafacture/metafacture-core/pull/335/commits/ee0e624b2bfc724166e30765cff0fe1e076915c8

We could set the property in the build for metamorph-test

Hm, but you then change a test which was supposed to work as it is. Probably then one would have to set this property in all the productive apps to also work, and this would be a "break of the api".

Hm, but you then change a test which was supposed to work as it is. Probably then one would have to set this property in all the productive apps to also work, and this would be a "break of the api".

Hm, yes, that is true. So 2.7.2 + exclusions is no option. I'd still prefer 2.7.2 + property, since that keeps the workaround very local, to OaiPmhOpener only, while the rest of the biblio package and the rest of metafacture can use the newer 2.7.2. But if you prefer 2.7.0 + exclusion, that's fine with me too.

Disucussed offline:
Both approaches have their weiredness. As Xalan 2.7.x somehow interferes with other modules I tend to not use it atm. But we should keep this in the back of our minds and may come back to the "System-Property-solution" if the need arise.


White box around popups

When you click in the Multi-Target NAME field the surrounding modal turns grey and the moment you try to enter text (or even backspace) a single key press will cause the white box to appear and take focus out of the text box.
Entering in the ORDER boxes or MULTIPLIER boxes don't cause this. It's only the NAME box.
Doesn't matter if it's the first multi-target created, or an old one edited.

Updated description and changed status to Fix ASAP since I now know how to re-create it.

Fixed by 8.19.2 https://github.com/frzyc/genshin-optimizer/commit/9d5046fc79e06b5ec0640a6125e0f61d31e318cc


Dependency updates for Angular 8 and TS 3.3.3333

We need to wait, until the framework supports Ts 3.3
PR for this https://github.com/angular/angular/pull/28497

@filipesilva updating to TS3, would also fix this issue https://github.com/angular/angular-cli/issues/13842

@filipesilva what you mind having a look at this? I cannot add you as a reviewers since you authored this.


Can not install appcenter cli

Description
Can not install appcenter cli with this command: npm install -g appcenter-cli
Repro Steps
Please list the steps used to reproduce your issue.

Open Terminal on Macos
Type npm install -g appcenter-cli and enter

Expected behavior
Use appcenter command with Terminal
Details

Is there a particular beacon/command that you are having trouble with?

npm install -g appcenter-cli

Which version of the App Center CLI are you using?

2.10.10

Which OS version did you experience the issue on?

MacOS 12.3

What command line/shell are you using?

Terminal

What version of Node.js and NPM/Yarn are you using?

node v18.0.0, npm v8.6.0

Additionally, you can provide verbose logs of a CLI command by using DEBUG="appcenter-cli:*" before the command, for example, DEBUG="appcenter-cli:*" appcenter apps list. Include the logs here, don't forget to omit any personal/sensitive data.
INSTALL LOG

npm WARN deprecated<EMAIL_ADDRESS>this library is no longer supported
npm WARN deprecated<EMAIL_ADDRESS>Please upgrade to latest, formidable@v2 or formidable@v3! Check these notes: https://bit.ly/2ZEqIau
npm WARN deprecated<EMAIL_ADDRESS>Please upgrade  to version 7 or higher.  Older versions may use Math.random() in certain circumstances, which is known to be problematic.  See https://v8.dev/blog/math-random for details.
npm WARN deprecated<EMAIL_ADDRESS>Please upgrade  to version 7 or higher.  Older versions may use Math.random() in certain circumstances, which is known to be problematic.  See https://v8.dev/blog/math-random for details.
npm WARN deprecated<EMAIL_ADDRESS>Please upgrade  to version 7 or higher.  Older versions may use Math.random() in certain circumstances, which is known to be problematic.  See https://v8.dev/blog/math-random for details.
npm WARN deprecated<EMAIL_ADDRESS>request has been deprecated, see https://github.com/request/request/issues/3142
npm WARN deprecated<EMAIL_ADDRESS>Please upgrade to v7.0.2+ of superagent.  We have fixed numerous issues with streams, form-data, attach(), filesystem errors not bubbling up (ENOENT on attach()), and all tests are now passing.  See the releases tab for more information at <https://github.com/visionmedia/superagent/releases>.
npm WARN deprecated<EMAIL_ADDRESS>Please note: newer packages @azure/storage-blob, @azure/storage-queue and @azure/storage-file are available as of November 2019 and @azure/data-tables is available as of June 2021. While the legacy azure-storage package will continue to receive critical bug fixes, we strongly encourage you to upgrade. Migration guide can be found: https://github.com/Azure/azure-sdk-for-js/blob/main/sdk/storage/MigrationGuide.md

changed 490 packages, and audited 491 packages in 15s

Hello @dunno7 !
Unfortunately I'm unable to reproduce your issue.
anatoly@MacBook-Pro-anatoly-2 ~ % npm install -g appcenter-cli
added 489 packages, and changed 1 package in 54s
53 packages are looking for funding run npm fund for details
anatoly@MacBook-Pro-anatoly-2 ~ % appcenter -v
appcenter version 2.10.10
anatoly@MacBook-Pro-anatoly-2 ~ % node -v
v18.0.0

I'm using the same environment as you, and all works as expected.
Also I didn't see any errors in provided log.
Could you please describe actual behaviour more detailed?

This is full log:
Last login: Wed Apr 27 20:37:53 on console

The default interactive shell is now zsh.
To update your account to use zsh, please run `chsh -s /bin/zsh`.
For more details, please visit https://support.apple.com/kb/HT208050.
MacBook-Pro:~ dungnart$ npm install -g appcenter-cli
npm WARN deprecated<EMAIL_ADDRESS>this library is no longer supported
npm WARN deprecated<EMAIL_ADDRESS>Please upgrade to latest, formidable@v2 or formidable@v3! Check these notes: https://bit.ly/2ZEqIau
npm WARN deprecated<EMAIL_ADDRESS>Please upgrade  to version 7 or higher.  Older versions may use Math.random() in certain circumstances, which is known to be problematic.  See https://v8.dev/blog/math-random for details.
npm WARN deprecated<EMAIL_ADDRESS>Please upgrade  to version 7 or higher.  Older versions may use Math.random() in certain circumstances, which is known to be problematic.  See https://v8.dev/blog/math-random for details.
npm WARN deprecated<EMAIL_ADDRESS>Please upgrade  to version 7 or higher.  Older versions may use Math.random() in certain circumstances, which is known to be problematic.  See https://v8.dev/blog/math-random for details.
npm WARN deprecated<EMAIL_ADDRESS>request has been deprecated, see https://github.com/request/request/issues/3142
npm WARN deprecated<EMAIL_ADDRESS>Please upgrade to v7.0.2+ of superagent.  We have fixed numerous issues with streams, form-data, attach(), filesystem errors not bubbling up (ENOENT on attach()), and all tests are now passing.  See the releases tab for more information at <https://github.com/visionmedia/superagent/releases>.
npm WARN deprecated<EMAIL_ADDRESS>Please note: newer packages @azure/storage-blob, @azure/storage-queue and @azure/storage-file are available as of November 2019 and @azure/data-tables is available as of June 2021. While the legacy azure-storage package will continue to receive critical bug fixes, we strongly encourage you to upgrade. Migration guide can be found: https://github.com/Azure/azure-sdk-for-js/blob/main/sdk/storage/MigrationGuide.md
(#######(##################) ⠏ reify:appcenter-cli: timing reifyNode:node_modules/appcenter-c
changed 490 packages, and audited 491 packages in 28s

found 0 vulnerabilities
MacBook-Pro:~ dungnart$ appcenter -v
-bash: appcenter: command not found
MacBook-Pro:~ dungnart$ node -v
v18.0.0
MacBook-Pro:~ dungnart$ npm -v
8.6.0
MacBook-Pro:~ dungnart$

Do I miss any configuration? node & npm is installed. :(

@Dunno7 looks like that something goes wrong with your local environment.
You can find more information in issue https://github.com/microsoft/appcenter-cli/issues/460.
Closing as a duplicate of https://github.com/microsoft/appcenter-cli/issues/460.

Could you please send me your package.json file. I think there is something wrong with it. Thank in advance!

@dunno7 appcenter-cli is an open-source project.
You can found package.json file here https://github.com/microsoft/appcenter-cli/blob/master/package.json

Solution was founded from here: https://stackoverflow.com/questions/15054388/global-node-modules-not-installing-correctly-command-not-found

This may mean your node install prefix isn't what you expect.
You can set it like so:
npm config set prefix /usr/local
then try running npm install -g again, and it should work out.

Solution was founded from here: https://stackoverflow.com/questions/15054388/global-node-modules-not-installing-correctly-command-not-found. Thanks @AnatolyPristensky for helping!

May I know what you did to resolve the issue?


When service is running and you open the notification, it fails to check if the service is running

Hi,
I've noticed that when you start the service, the notification is created and the service is actually running, when you click on the notification to return to the main activity, it fails to check if the service is actually running even though it is running.
So if (service != null && service.isRunning()) always returns a false even though it is still running in the background but the main activity thinks it's not and behaves that way, resulting in no communication between the service and activity anymore.

@phamels thanks for reporting. Care to open a PR that fixes this?

@jbits want to check this one out? ;-)

I can't reproduce it. From what I understand after I go back to the app by clicking on notification (service != null && service.isRunning()) evaluates to false. I don't see it happening. Maybe somebody could explain more clearly what is the issue. I'm fairly new to android.


The "Debug a remote Service Fabric application" does not work as advertised

I tried this the other day.  Below is how it worked for me:

attaching to the application worked only on like every 5h attempt.
once the breakpoint was hit, it took the debugger forever to evaluate the local variables.  It never went through to completion.

The feature sounds to be amazingly good "on paper", a total waste of time to try to use it.

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

ID: e8adfa1c-0bb9-c112-3463-0d655a3e7cd1
Version Independent ID: ef09b17d-cebf-56ca-7f59-71dba2dc3123
Content: Debug your application in Visual Studio
Content Source: articles/service-fabric/service-fabric-debugging-your-application.md
Service: service-fabric
GitHub Login: @vturecek
Microsoft Alias: vturecek

@eugen-nw thanks for bringing this up. The performance might vary based on your computer specs as well. Can you tell me what specs you are running VS on?

@eugen-nw thanks for that! You are running a similar machine to mine so I will try to repro and see if I get similar behavior. Just FYI I am out of office tomorrow so I will run some tests first thing next week and provide an update. If you notice anything else you believe might be worth noting just let me know :)

Thanks again Micah!  I'll be on vacation next week, so I won't follow up on this before Sept. 10.
There's another inconvenience I just recalled: Visual Studio was not able to load the .PDB symbols that were placed next to the running binaries in Service Fabric, so I needed to download them onto my laptop and load them from there.  This is merely an inconvenience that needs to be 1). documented 2). hopefully, be  addressed.

Thanks for letting me know :) I will be sure to provide updates but not expect a response till you are back so no worries. Enjoy the vacation!
And thanks for that extra information. I will make sure to note that as well and we can see if we can note that in the doc or find a way to make the debugger better so that doesn't happen.

@eugen-nw I ran through this doc and although I did not see the exact same issues as you did the entire process itself was not super fluent. I am assuming this is because the doc was published in 2017 and since then their have been mulitple updates in the SDKs.
I was able to get the debugger to work but not very smoothly.
@vturecek would you be able to run through this doc and see if we can add some updates where needed? If anything we should make sure it is updated to work with the latest SDK versions.

Even I am facing the same issue as eugen-nw trying to debug a SF Application deployed in Azure.
VS 2017 doesn't download the application code symbols at all even from the local location. Do we have any fix for this in place?

It’d be interesting to learn if the feature works for anyone

@MicahMcKittrick-MSFT Do you guys have a fix in place for this? I enabled remote debugging using VS and it completed all tasks. However, after that, I could not attach to debugger - as other people have mentioned, it says: "Failure to launch Remote Debugger" - this is very frustrating, as it always happens wth MS product that it does not work as advertised when it is most needed.


chore(release): revert unexpected downgrade of backstage-plugin-orchestrator-form-react by MSR

The MSR release job seems to have failed after merging #2223 :
https://github.com/janus-idp/backstage-plugins/actions/runs/11159096004/job/31016793572
This reverts commit 5cf6602004c09b037d31aade078b45b3e02f0608, and should allow releasing the packages that have been updated recently (like bulk-import-backend and bulk-import-common).

/cc @AndrienkoAleksandr


Fixed \ ; KP_,

Description
According to console, ; and KP_. are not valid. Have to use SEMICOLON and KP_DEL respectively.
TL;DR: Fixed \ ; KP_.
Changes
Fixed ; and KP_. in default layout.
Fixed \ ; and KP_. in razer layout.
Added Fn/Menu (just visual) in razer layout.
Comments
I am completely not sure how having \ will affect in other places.

Thanks, I think this should fix it. I also don't think there will be any issues because of the /, but it's a weird character, you never know.
Will update the version running on my server in the next 10 minutes.

It's live, if you notice any issues let me know, I can only verify the visual side of it and the layout seem to work.


UCF101 future prediction with resolution 128

On Table D1 in the paper, it says 16-frame unconditional video synthesis on UCF-101 was done in resolution 128x128.
However, I found that released checkpoints are for 256x256 resolution instead of 128x128 - so the resolution does not match.
Could you release checkpoints and scripts for reproducing this table?

Hi ! We follow the experimental protocol from MoCoGANHD [1] where video are synthesized at 256x256 and resized to 128x128 during evaluation for fair comparisons with prior works (see Section 4.3 of [1]: "We resize frames for all methods to 128x128 when calculating IS and FVD").
[1] A good image generator is what you need for high-resolution video synthesis, ICLR'21

Thank you for your prompt response!


schema: slight clarification for oci-layout file

https://github.com/opencontainers/image-spec/pull/579#issuecomment-285132348
Signed-off-by: Vincent Batts<EMAIL_ADDRESS>

LGTM
Maybe needs to rebase after merging the PR that fixes the build.

rebased

LGTM

@jbouzane Pull approve does recognize the approvals system. You need to say "LGTM".

The schema/fs.go might had better to be updated accordingly.

@xiekeyang the schema/fs.go is now a PHONY target in the Makefile. It ought to be regenerated as needed for make targets. I wish we could delete the fs.go completely, and only generate it, but that would break go get or vendoring of this spec.

Yeah, you are right. I mistook it.

LGTM

:+1:


Add support for ForeignKey to_field

This PR adds support for ManyToOneRel where a custom join field is used by setting ForeignKey.to_field.
This is achieved by removing the hardcoded outer_ref='pk' and retrieve the field name by join_field.get_related_field().name. The caveat is that GenericRel does not have a get_related_field defined and will fallback on pk in this case.
I also added a test case for this.
FYI I found your project through this Django ticket https://code.djangoproject.com/ticket/28296. Maybe you're interested in bringing this into Django? :)

Thanks for finding and fixing this, looks good.

Maybe you're interested in bringing this into Django?

Ultimately, yes, this should be in Django with the API that ticket settles on. In the short term, I think it's good as a third party app where we can quickly fix bugs like you did here. Hopefully we can get all the bugs out, making the implementation in Django easy.

Thanks for the review and merge! :)


Path eq string comparison is not working

When comparing a string, in the response inside a path, the script throws an error
 jq: invalid JSON text passed to --argjson
Use jq --help for help with command-line options,
or see the jq manpage, or online docs  at https://stedolan.github.io/jq

Example:
[
    {
        "key": "value",
        "foo": "bar",
        "status": "ASTATUS"
    }
]

example test case:
 ...
    "testCases": {
        "get_status": {
            "path": "/programs/",
            "method": "GET",
            "description": "GET /programs",
            "expect": {
                "body": {
                    "path_eq": {
                        "[0].status": "MYSTATUS"
                    }
                }
            }
        }
    }

The reason the error arises is, an invalid string is passed to jq argson (without quotes) failing it to parse. https://github.com/subeshb1/api-test/blob/v0.3.2/api-test.sh#L389
Thanks, @badevos for reporting this!

Fixed by #26


Chromebook: white bar remains after closing app

Expected behavior
On Chromebook, when exiting (fullscreen) K-9 mail, all windows and popups close.
Actual behavior
A white bar with a (non-functioning) close "×" symbol is opened by K-9 and left behind on the top of the screen. This behavior started after last K-9 update. I suspect K-9 is trying to open an alert and mysteriously failing.

Steps to reproduce

Start K-9
Exit
White bar remains at top of screen, the only way to get rid of it is to log out.

Environment
K-9 Mail version:
5.600
Android version:
Google Chrome OS Version 69.0.3497.120 (Official Build) (32-bit)
Account type (IMAP, POP3, WebDAV/Exchange):
IMAP

That sounds like a Chrome OS bug rather than a K-9 Mail bug.


 Can you please attach a sample project that reproduces the issue?

Nevermind, I set an exception breakpoint and was able to see it happen. Looks like geos uses C++ exceptions internally. If you turn off the exception breakpoint, you'll see that l?.intersection(p!) actually completes successfully.

C++ exception, does it affect my normal use? I am worried that this exception will crash the normal APP.

Nope, it won’t impact the app. GEOSwift uses the geos C API which catches all exceptions from the C++ layer.


update-report: unlink rather than uninstall --force formula when migrating a formula to a cask

[x] Have you followed the guidelines in our Contributing document?
[x] Have you checked to ensure there aren't other open Pull Requests for the same change?
[ ] Have you added an explanation of what your changes do and why you'd like us to include them?
[ ] Have you written new tests for your changes? Here's an example.
[ ] Have you successfully run brew tests with your changes locally?

Discussion in #2025.

Thanks again @zmwangx!


Create an option to skip/disable upload to code scanning

Fixes #701

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

Comparison is base (dd26cdc) 78.86% compared to head (a831edb) 78.34%.

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #702      +/-   ##
==========================================
- Coverage   78.86%   78.34%   -0.53%
==========================================
  Files          84       84
  Lines        5943     5943
==========================================
- Hits         4687     4656      -31
- Misses       1054     1084      +30
- Partials      202      203       +1

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


feat: squash nft tokens on resize

What does this PR do and why?
Provide a description of what this PR does. Link to any relevant GitHub issues, Notion tasks or Discord discussions.
Screenshots or screen recordings
If applicable, provide screenshots or screen recordings to demonstrate the changes.
Acceptance checklist

[ ] I have evaluated the Approval Guidelines for this PR.
[ ] (if relevant) I have tested this PR in all supported browsers.
[ ] (if relevant) I have tested this PR in dark mode and light mode (if applicable).

Current dependencies on/for this PR:

main

PR #3756

PR #3757

PR #3758   👈

This comment was auto-generated by Graphite.

@wraeth-eth started a stack merge that includes this pull request via Graphite.

Graphite rebased this pull request as part of a merge.

@wraeth-eth merged this pull request with Graphite.


esnext option - where? how?

I'm new to jsbin.  Thanks for building this tool.  i'm trying to test some rxjs, but I'm getting this error:

arrow function syntax (=>)' is available in ES6 (use esnext option) or Mozilla JS extensions (use moz).

The help makes no mention of where this esnext option lives?  Am I supposed to select ES6/babel?
I can't find "moz" either.
It would be nicer to have a more verbose message to direct the user.
Thanks,

Your errors have nothing to do with jsbin, they're coming from what ever library you're using. If you want to use Babel, select it from the JavaScript panel. Otherwise you may want to raise this issue again the library you're using if you're having trouble with it.

For me, I choose ES6/Babel, go to account settings -> preferences -> linting -> jshint, and add the following rules:
{
  "esnext": true
}

and it works for me.

Eh. I can see no rules above...

Using jsbin without logging in, add a comment at the top of the JavaScript panel //jshint esnext:true

Relevant parts of jshint documentation:

Newer esversion syntax doesn't seem to work in jsbin. Old esnext option does, but it's a bit buggy for me (I get weird "missing semicolon" errors).

Agreed, especially if the editor is set to Babel/ES6.

Common, it's definitely a UX issue if you open this tool for the first time. Just put this piece of information or link to the tooltip or make it even smarter by asking the user to automatically change its jsHint config on changing script type.

Add the following line in the beginning of JS Bin JavaScript editor:
/* jshint esnext: true */

Please recheck if you are using the console or the output window for the result.

For me, I choose ES6/Babel, go to account settings -> preferences -> linting -> jshint, and add the following rules:
{
  "esnext": true
}

and it works for me.

Thank you

Add the following line in the beginning of JS Bin JavaScript editor:
/* jshint esversion: 6 */
These configurations come from JShint

Thank you !!!

Thank You.

only esnext style works for me.

Not even with /* jshint esnext: true */ line added
I click in Run on console window, nothing happens.


Update grpc minimum version to 1.30

This rebases @jjardon's patch against bst-1, replacing pull request #1489

Some tests are still spuriously failing, partly due to using pytest-xdist, unrelated to this patch, merging this regardless.


Adding missing specs and docs to Registrar#register

Just to be consistent across all the Registrar methods.

:+1:


remove twitter from my profile, will be deleted soon

Signed-off-by: Felix Kronlage-Dammers<EMAIL_ADDRESS>

LGTM! Would you be interested in a button for the Mastodon network?

yes.


add links to nvm and rvm

in our readme we suggest people use nvm and rvm, however we do not provide them with any links. After much thought I don't want to provide the entire documentation for nvm and rvm on our readme since it will inherently become outdated.

fixed in bbe785f4c7d1c24ec1941a04be54cdd92ce7c393


uv pip install fails to install llama-cpp-python

Thank you very much for this package. I'm encountering the following issue. In an emptly virtual environment, when I run
uv pip install llama-cpp-python --verbose

I obtain
DEBUG uv 0.2.35
DEBUG Searching for Python interpreter in system path
DEBUG Found `cpython-3.10.12-linux-x86_64-gnu` at `/home/asilva/test-llama-cpp/.venv/bin/python3` (active virtual environment)
DEBUG Using Python 3.10.12 environment at test-llama-cpp/.venv/bin/python3
DEBUG Acquired lock for `test-llama-cpp/.venv`
DEBUG At least one requirement is not satisfied: llama-cpp-python
DEBUG Using request timeout of 30s
DEBUG Solving with installed Python version: 3.10.12
DEBUG Adding direct dependency: llama-cpp-python*
DEBUG Found fresh response for: https://pypi.org/simple/llama-cpp-python/
DEBUG Searching for a compatible version of llama-cpp-python (*)
DEBUG Selecting: llama-cpp-python==0.2.87 [compatible] (llama_cpp_python-0.2.87.tar.gz)
DEBUG Acquired lock for `/home/asilva/.cache/uv/built-wheels-v3/pypi/llama-cpp-python/0.2.87`
DEBUG No cache entry for: https://files.pythonhosted.org/packages/a2/63/7b9fe4c6b9d52e1ed2c2689711cdbb60314cf13474c626accd4213cf937c/llama_cpp_python-0.2.87.tar.gz
DEBUG Downloading source distribution: llama-cpp-python==0.2.87
error: Failed to download and build `llama-cpp-python==0.2.87`
  Caused by: Failed to extract archive
  Caused by: failed to unpack `/home/asilva/.cache/uv/built-wheels-v3/.tmpvYPWA5/llama_cpp_python-0.2.87/vendor/llama.cpp/spm-headers/ggml-alloc.h`
  Caused by: File exists (os error 17) when symlinking ../ggml/include/ggml-alloc.h to /home/asilva/.cache/uv/built-wheels-v3/.tmpvYPWA5/llama_cpp_python-0.2.87/vendor/llama.cpp/spm-headers/ggml-alloc.h

Current uv version: uv 0.2.35
Current platform:
PRETTY_NAME="Ubuntu 22.04.4 LTS"
NAME="Ubuntu"
VERSION_ID="22.04"
VERSION="22.04.4 LTS (Jammy Jellyfish)"
VERSION_CODENAME=jammy
ID=ubuntu
ID_LIKE=debian
HOME_URL="https://www.ubuntu.com/"
SUPPORT_URL="https://help.ubuntu.com/"
BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"
UBUNTU_CODENAME=jammy

Uhm, I cannot decipher the last line:
Caused by: File exists (os error 17) when symlinking ../ggml/include/ggml-alloc.h to /home/asilva/.cache/uv/built-wheels-v3/.tmpvYPWA5/llama_cpp_python-0.2.87/vendor/llama.cpp/spm-headers/ggml-alloc.h

There might be another version of ggml-alloc somewhere in the machine?

Uhm, I cannot decipher the last line:
Caused by: File exists (os error 17) when symlinking ../ggml/include/ggml-alloc.h to /home/asilva/.cache/uv/built-wheels-v3/.tmpvYPWA5/llama_cpp_python-0.2.87/vendor/llama.cpp/spm-headers/ggml-alloc.h

There might be another version of ggml-alloc somewhere in the machine?

Thank you very much for your answer @baggiponte
Any pointers on how to check if that is the case and how to remove it?

I tested other versions of llama-cpp-python. Up to version llama-cpp-python=0.2.85 it works without any problem. The last two versions llama-cpp-python=0.2.86 and llama-cpp-python=0.2.87 do not work with uv anymore.

I can take a look. My guess is we're refusing to overwrite a file with a symlink, or something like that.

I think there might be something wrong with this source distribution. If you untar it, every entry is duplicated: tar -tf llama_cpp_python-0.2.87.tar.gz:
...
llama_cpp_python-0.2.87/vendor/llama.cpp/tests/test-tokenizer-1-bpe.cpp
llama_cpp_python-0.2.87/vendor/llama.cpp/tests/test-tokenizer-1-bpe.cpp
llama_cpp_python-0.2.87/vendor/llama.cpp/tests/test-tokenizer-1-spm.cpp
llama_cpp_python-0.2.87/vendor/llama.cpp/tests/test-tokenizer-1-spm.cpp
llama_cpp_python-0.2.87/vendor/llama.cpp/tests/test-tokenizer-random.py
llama_cpp_python-0.2.87/vendor/llama.cpp/tests/test-tokenizer-random.py
...

I don't see the same issue with the prior release. Do you mind reporting this on the library itself?

Nevermind, I commented on https://github.com/abetlen/llama-cpp-python/issues/1670.

scikit-build-core 0.10.2 should fix this (thanks to @abetlen)!

Great. Thank you very much. Should I close it then or leave it open until fixed in case other people are having the same issue?

Best to close it so we know we don't need to do anything here. Thanks!

For others looking at this issue, this has been solved in llama-cpp-python==0.2.88


Support custom openapi url

I think it might be better if we just changed the setup of the SwaggerUIBundle to support external openapi files:
<script>
  window.ui = SwaggerUIBundle({
     url: '{{ filter_var(config('swagger-ui.file'), FILTER_VALIDATE_URL) ? config('swagger-ui.file') : route('swagger-openapi-json', [], false) }}',
     dom_id: '#swagger-ui',
     deepLinking: true,
     presets: [
         SwaggerUIBundle.presets.apis,
     ],
     layout: 'BaseLayout',
  });
</script>

If the swagger-ui.file config value is an url, then that config value will be directly provided as url to swagger-ui, instead of this package's route.
What do you think?

Or maybe, if the file is located somewhere else, then it still needs to go through the swagger-openapi-json route of the package, so it can update the server url and the oauth urls in the file before the openapi file is shown in swagger-ui 🤔


Don't count failed signature matches as autocast matches

Consider the following:
def foo(x : Int8, y : Char); end
def foo(x : UInt8, y : String); end

foo(1, 'a')       # Error: ambiguous call, implicit cast of 1 matches all of Int8, UInt8
foo(y: 'a', x: 1) # okay

def bar(x : Char, y : Int8); end
def bar(x : String, y : UInt8); end

bar('a', 1)       # okay
bar(y: 1, x: 'a') # Error: ambiguous call, implicit cast of 1 matches all of Int8, UInt8

Each overload set is checked in that order, because neither overload is more restricted than the other. What happens here is:

Neither overload matches when autocasting is disabled.
Method lookup is repeated with autocasting enabled, and proceeds to check argument compatibility following argument order.
1 successfully matches Int8 because 1 is within Int8's range. The compiler adds this to a list of autocast matches.
'a' successfully matches Char, so there is a successful signature match. But the compiler must also check other defs to detect ambiguous autocasts.
1 successfully matches UInt8 because 1 is within UInt8's range. The autocast match list now contains both integer types.
'a' does not match String, so this signature match fails, but the compiler does not reset the autocast matches. Thus 1 is considered to be ambiguous even though the UInt8 autocast match is useless.

This PR refactors the literal restriction logic so that autocast matches are added only after a signature match succeeds (with LiteralType#add_literal_matches), making both error calls above unambiguous. The method LiteralType#restrict_literal is also added to perform literal restriction without relying on the autocast match state (@match and exact_match?).
Does not fix https://github.com/crystal-lang/crystal/pull/8600#pullrequestreview-334682026, since in that case all signature matches succeed.

I don't know if you are going to present in the next Crystal Conference, but here's a topic suggestion: "How I fixed Crystal" 😄


improve display for listAccounts

Codecov Report

Merging #38 into release-rc2 will decrease coverage by 0.04%.
The diff coverage is 0.00%.

@@               Coverage Diff                @@
##             release-rc2     #38      +/-   ##
================================================
- Coverage           6.27%   6.23%   -0.05%
  Complexity            17      17
================================================
  Files                 16      16
  Lines                908     914       +6
  Branches             121     122       +1
================================================
  Hits                  57      57
- Misses               838     844       +6
  Partials              13      13

Impacted Files
Coverage Δ
Complexity Δ

...a/com/webank/wecross/console/routine/HTLCImpl.java
0.00% <0.00%> (ø)
0.00 <0.00> (ø)

...n/java/com/webank/wecross/console/rpc/RPCImpl.java
0.00% <0.00%> (ø)
0.00 <0.00> (ø)

Continue to review full report at Codecov.

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


Can we convert images to video like ffmpeg library in ffmpeg wasm?

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
Describe the solution you'd like
A clear and concise description of what you want to happen.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.

Yes, we can 🦾
With help of ffmpeg command: --pattern_type glob
Pass array of images with num pattern like: -i frame_*.jpg. Remember that your frames should have correct number relative to video that you want to get. Ex:
const num = `00${index}`.slice(-3);
await this.ffmpeg.writeFile(`frame_${num}.jpg`, new Uint8Array(buffer));

check ffmpeg docs: https://ffmpeg.org/

Yes, we can 🦾 With help of ffmpeg command: --pattern_type glob Pass array of images with num pattern like: -i frame_*.jpg. Remember that your frames should have correct number relative to video that you want to get. Ex:
const num = `00${index}`.slice(-3);
await this.ffmpeg.writeFile(`frame_${num}.jpg`, new Uint8Array(buffer));

Hi @tini2n,
Thanks for your response. I am trying to record the stream getting from navigator.mediaDevices.getUserMedia by painting the video into a canvas and then storing the imageData using ffmpeg.writeFile method and then trying to convert the images into video using ffmpeg.exe method but it is not working for me. I am sharing the code I used here. Kindly please assist me if I did anything wrong.
const ffmpegRef = useRef(new FFmpeg());
const canvasRef = useRef<HTMLCanvasElement | null>(null);
const videoRef = useRef<HTMLVideoElement | null>(null);
const fps = 30;
let uuid = crypto.randomUUID();
let images: Record<string, string[]> = {
[uuid]: [],
};
useEffect(() => {
initFFmpeg();
}, []);
const initFFmpeg = async () => {
const baseURL = "https://unpkg.com/<EMAIL_ADDRESS>const ffmpeg = ffmpegRef.current;
ffmpeg.on("log", ({ message }) => {
  console.log(message);
});

ffmpeg.on("progress", ({ progress, time }) => {
  console.log(time, progress);
});
// toBlobURL is used to bypass CORS issue, urls with the same
// domain can be used directly.
await ffmpeg.load({
  coreURL: await toBlobURL(`${baseURL}/ffmpeg-core.js`, "text/javascript"),
  wasmURL: await toBlobURL(
    `${baseURL}/ffmpeg-core.wasm`,
    "application/wasm"
  ),
  workerURL: await toBlobURL(
    `${baseURL}/ffmpeg-core.worker.js`,
    "text/javascript"
  ),
});

getVideoStream();

};
const getVideoStream = async () => {
if (!videoRef.current) return;
try {
  let stream = await navigator.mediaDevices.getUserMedia({
    audio: false,
    video: true,
  });
  videoRef.current.srcObject = stream;
  await videoRef.current.play();
  console.log(ffmpegRef.current);
  setInterval(renderCanvas, 1000 / fps);
} catch (error) {
  console.log(error);
}

};
const renderCanvas = async () => {
if (!videoRef.current || !canvasRef.current || !ffmpegRef.current) return;
let ctx = canvasRef.current.getContext("2d");

if (!ctx) return;

let canvasWidth = canvasRef.current.width;
let canvasHeight = canvasRef.current.height;

ctx.clearRect(0, 0, canvasWidth, canvasHeight);

ctx.drawImage(
  videoRef.current,
  0,
  0,
  canvasRef.current.width,
  canvasRef.current.height
);

let fileName = `image-${uuid}-${images[uuid].length + 1}.png`;
let base64 = canvasRef.current.toDataURL("image/png");
let unit8Array = await fetchFile(base64);
await ffmpegRef.current.writeFile(fileName, unit8Array);
images[uuid].push(fileName);
if (images[uuid].length === 125) convertImagesToVideo(uuid);

};
const convertImagesToVideo = async (id: string) => {
try {
uuid = crypto.randomUUID();
images[uuid] = [];
let ffmpeg = ffmpegRef.current;
const input = image-${id}-%d.png;
const output = "output.mp4";
const args = -start_number 1 -i ${input} -c:v libx264 ${output};
await ffmpeg.exec(args.split(" "));
let data = await ffmpeg.readFile(output);
console.log(data);
} catch (error) {
console.log(error);
}
};
Thanks

Hi @vkaswin, you can have a look here, this stop motion app seems to be doing the same thing you'd like to do:
https://github.com/kitsteam/stop-motion-app/blob/main/src/app/services/video/video.service.ts
https://github.com/kitsteam/stop-motion-app/blob/main/src/app/models/animator.ts#L148

Hi @nwittstruck ,
Thanks for your response will check the stop motion github repository.

Yes, we can 🦾 With help of ffmpeg command: --pattern_type glob Pass array of images with num pattern like: -i frame_*.jpg. Remember that your frames should have correct number relative to video that you want to get. Ex:
const num = `00${index}`.slice(-3);
await this.ffmpeg.writeFile(`frame_${num}.jpg`, new Uint8Array(buffer));

Lets say I've like 500 images in an array that I want to convert in a video, so do I run this in a loop and writeFile 500 times?

Lets say I've like 500 images in an array that I want to convert in a video, so do I run this in a loop and writeFile 500 times?

Yes, exactly. Just be aware of memory limits, especially on mobile devices.


Optimize recursive directories?

Hi there,
great tool!
How does it optimize directories recursive?
Cheers Ralf

Thanks @Horttcore,
Whenever a directory is passed into ImageOptim-CLI it optimises every image within it using this find command, so directories within directories get included that way.
Is that what you were asking about?

Not exactly, here is an example if I try to optimize a WordPress upload folder.
Folder structure is
…
uploads/2015/11
uploads/2015/12
uploads/2016/01
…
➜  wp-content git:(master) imageoptim --directory uploads sort: string comparison failed: Illegal byte sequence sort: Set LC_ALL='C' to work around the problem. sort: The strings compared were UPLOADS/2015/04/MOTIV\302\200\223MINIQEE-480X195.JPG' and UPLOADS/2015/04/MOTIV\302\200\223MINIQEE.JPG'. Running ImageOptim... Runtime error (func=(main), adr=9): Divide by zero (standard_in) 2: parse error TOTAL was: 0kb now: 0kb saving: 0kb (%) quality: %
No image is optimized, if I try imageoptim --directory uploads/2016/01 it works as expected.
Maybe its my enviroment?

Could you tell me some more about the block starting with ➜ please?

Ah thats just because I use ohmyzsh

I've not used ohmyzsh before, I couldn't say whether ImageOptim-CLI supports that.
The directory structure UPLOADS/2015/04/MOTIV\302\200\223MINIQEE.JPG which mixes /s and \ isn't something I've ever seen before, is that valid? That could be the cause.


Rel/2.0.0

@mikeharder,
Thanks for having already signed the Contribution License Agreement. Your agreement was validated by .NET Foundation. We will now review your pull request.
Thanks,
.NET Foundation Pull Request Bot


Don't you want to apply for Korean server 6.2?

I want to use it on the Korean server.

It's currently not trivial to support multiple versions, unfortunately. Your best bet is rolling back to whatever version was current when 6.2 was on EU, then finding network opcodes for KR client, updating that and rebuilding.


#2: Identify and extract more code that can be shared as packages

Once the concept is proven and tested here https://github.com/leather-wallet/extension/issues/4268 we can identify more things that would benefit from moving and being shared via packages.
A rough list could be:

TS config
Core CSS theme
Panda configuration setup
Design system - typography, colours etc.

Eslint config, too.
RE design tokens, how about the structure of @leather/tokens → @leather/panda-config ?

@kyranjamie to outline Bitcoin and Ordinals code to migrate for sharing

I've been working on this and have setup new monorepo packages for:

eslint
tsconfig

I've also implemented developer tools which:

enforce conventional commits with commitlint
use husky to run lint and commit checks on commit

Now I am working on setting up github actions to run checks and to auto-publish to npm. Once that's done we will be in a good spot to add the remaining packages

Another package to add here is dependancy-cruiser

Here's a stab at how I reckon we should organise our packages.
Please excuse this very basic, crude diagram but hope it can explain a few thoughts. For some reason I couldn't embed mermaid directly.

Package granularity
The thinking here is really to highlight what level of granularity our packages should take. For example, do we have a general bitcoin package, break it down further into an ordinals package, a Native Segwit and Taproot package etc. I suggest the former, creating a chain-level abstraction (so not very granular).
Isolating side effects/network requests
Anything that involves side effects, e.g. network requests, we should isolate in separate packages. They should also allow some level of configurability. Consider the use case that we need to add a custom header to requests on each platform, how might we configure the internal http client?
Dependency rules
We'll likely need a core package for general utils and logic shared between the @leather/{bitcoin,stacks} packages. I think we can just have a single crypto package for this, but open to other ideas if anyone thinks we should abstract further. @leather/crypto must not depend on any chain-specific packages, and depcruiser should enforce this, and also prevent any circular deps.
@leather/crypto
Encapsulates common crypto logic shared between chains. Keychain derivation, extracting details from a derivation path, for example. Must not know of chain-specific details. Much of the logic in src/shared/crypto of extension.
@leather/stacks
Lower priority for now as mobile won't support Stacks on first release, also much logic is already abstracted in @stacks/*
@leather/bitcoin
Highest priority package. Should depend on as few packages as possible, ideally only those of @scure/* and internal leather tooling. Stateless. Package should expose flat, pure functions. Should:

Derive the correct bitcoin-specific keychains
Contain logic to generate bitcoin payment types
Sign transactions
Message signing

Questions

Should chain packages be allowed to contain React-specific implementations? Hooks etc?
Should hardware wallet specific logic live alongside software in single package?

Please share any other idea & feedback

This looks great to me @kyranjamie , thanks for the efforts on this.
Regarding the questions:

I think it's OK to keep React-specific implementations in chains but in an organised manner. It would be cleaner not to but in reality all of our APPs will use React for now at least so it's useful to also share that logic
Similar to the above it could be easier to keep hardware + software specific logic alongside it's chain. I don't know much about the nuances of that though. If there are more generic things like setup / key creation it could be better to have in it's own package

Another thing for consideration on this path are to add more headless unit tests for packages to ensure core logic is well tested.
Yesterday we discussed starting to move some of these items for sharing with mobile but I find that a tricky thing to do without a clear roadmap and defined feature list for mobile. That will help us prioritise what to move and when

@kyranjamie is this issue still relevant?

Repurposing this issue for the refactor