Add ResNet50 quantized model from EdgeCortex to the new end-to-end MLPerf submission system

Add and test ResNet50 quantized model from EdgeCortex (https://zenodo.org/record/4589637/files/resnet50_INT8bit_quantized.pt) from https://github.com/mlcommons/inference/tree/master/vision/classification_and_detection

Done: https://github.com/octoml/mlops/tree/main/program/mlperf-inference-bench-image-classification-tvm-pytorch-cpu


docs: modules dependency management

To deal with the dependency management of packages that are commonly used across all the Invenio modules, we're moving to a "centralized" approach of managing them in the following fashion:

invenio-base: flask (and werkzeug), six
invenio-celery: celery and kombu,
invenio-i18n: flask-babelex
invenio-admin: flask-admin
invenio-accounts: flask-login, flask-security, flask-kvsession

So if e.g. invenio-records depends in its install_requires currently on Flask, we should instead change that to a dependency to invenio-base.
There should be a section in the documentation, describing:

How exactly we manage these?
What is the process of addressing e.g. issues in any of the upstream libraries (e.g. Flask breaking changes)?
How do we approach the minimum/pinned versions of the 3rd-party dependencies (i.e. flask, celery, etc.), and for these "centralized" modules (invenio-base, etc.)
In extreme scenarios (e.g. when we need a hotfix), what is the way to tackle these?

Note that this is not an entirely new thing, since we've already been doing this for a while with invenio-db and invenio-search for managing SQLAlchemy and Elasticsearch dependencies.

@slint @lnielsen is this still relevant or was implemented?


[WIP] File upload component

File upload component draft. #613
Contains basic implementation on vanilla module for single file upload and multiple upload with display of selected files.
To do:

Styles. Need some sketches for that component.
Functionality.  Public API, other features like auto send files on server, errors etc.
Other stuff

Hey @toxamiz! Thanks for tackling this component, it will probably take us a week or so to go over but face value - looking good 👍

Hey @toxamiz this is a great first PR!
A few things I picked up:

Any reason why a label is being used instead of say a button for the file upload input selector? I think this does not follow a11y and even semantic html. I wouldn't think to click a label in a form to trigger the upload file popup. I'd try to do something like this:

  Attach drivers license
  <input class="au-file-upload__input" type="file" />
  <button class="au-btn au-btn--secondary">Choose file</button>

So it could look something like this in the context of the form:

It could even be worth using au-btn--tertiary for the choose file button. This is because a form page may contain a secondary button for clearing the form or going to a previous page.

I'd  hide all the custom styling when javascript is disabled, since it gets in the way of the browser default file input.

We add a .no-js class when javascript is not loaded on a page. You can use a selector that goes something like this:
.au-file-upload {

.no-js & {
//insert styles here
}

This is a good example as well: https://github.com/govau/design-system-components/blob/bb844e31a46d388316673533a9ac32d3ded05d12/packages/side-nav/src/sass/_module.scss#L72-L75

There are a couple of problems with the multiple selector:
You are using a primary button for the remove file option:

This can be confusing, especially if this is contained within a form that has a primary button that submits it.
I would probably remove that functionality to remove altogether and just stick to the default functionality for this, which replaces the previous files selected with the new files selected.
Also we make sure all of our components are supported back to IE8. I'm not sure if multiple file feature is supported in < IE10? If not, do you know of any work arounds?

I would probably even break this PR up. We could release an alpha version, that just contains a single file upload component. And possibly build on it with multiple file upload component, since it's easier to manage that way.

Let me know if this doesn't make sense.

Branch rebase on latest develop now. Added email :)
@adamzerella Do i need to resolve conflicts in auds.json? Or i can simply accept all from develop and then run npm i in package directory?

@sukhrajghuman

Any reason why a label is being used instead of say a button for the file upload input selector? I think this does not follow a11y and even semantic html. I wouldn't think to click a label in a form to trigger the upload file popup. I'd try to do something like this

I'm not sure. Using label is a native way for associating with input, so don't need to call click on input when click on button. I think for a11y it is better using label instead of button in that case. Something like this (i may be completely wrong)

	Attach drivers license
	<input class="au-file-upload__input" id="drivers-license" type="file" />

	Choose file

2

Yes, thanks, i forgot about hiding elements.

3

Primary button there only for example :)
File list functionality may be various: may be we want just see the amount of files we selected like '3 files selected', or may be we want to manage uploaded files like in my PR, or use it as you say, or add an "upload" button on each item in list with upload progress bar, or all of that and switch between options :)
Unfortunately multiple file feature, accept and drag&drop is not supported in < IE9. You can inform user to choose file one by one and add an new input after user select file. It seem like completely separate package specific for that browsers. Also i think u can't access file data because FileAPI is not supported, so cant count size and etc.

4

It depends on functionality, it can be even better to have simple and small single select component and multiple select component with different modes, file list management, upload progress bars, other cool fireworks. And some "core" module between them.
Of course we could release an alpha version just need to decide features.

Branch rebase on latest develop now. Added email :)
@adamzerella Do i need to resolve conflicts in auds.json? Or i can simply accept all from develop and then run npm i in package directory?

@toxamiz I would accept the latest develop and then do: npm run watch

@toxamiz thanks for getting back!
If you can find me an examples/research that supports using a label instead of a button for clicking to upload files, I'm happy to be proven wrong.
Yes lets split this PR up and focus on releasing a file upload component for a single file because I think that would provide good user value.

@adamzerella OK, thanks
@sukhrajghuman

If you can find me an examples/research that supports using a label instead of a button for clicking to upload files, I'd be glad to accept this approach.

I don't think there are researches "button vs label on input file". If you want add a caption on form control better use label tag than any "label like" element.
According to this label for form control actually works like button providing a click events to associated form control. Almost any articles about custom styling file input uses styles on label. Buttons uses for other features.

Yes lets split this PR up and focus on releasing a file upload component for a single file. I think that would provide good user value and is a lot more simple to build with fewer edge cases. What do you think?

OK, lets focus on single file upload. So what do we need?

Default markup
Check file type according to accept attribute
File size restriction
Error handling/messages
...

@toxamiz
Hmmm yea okay I know what you are saying, can we style the associated label look like a button then. So it doesn't look like this:

But yea sorry I probably didn't word myself properly. What I mean to say is that it's not intuitive to click on text to trigger an action. I know labels are used with a for-id relationship to focus on the form control, but you shouldn't rely on that, and you are assuming that when people fill out a form they will click the label. If something requires clicking  it needs to be designed like so.
A picture from an article on affordance to better illustrate what I'm trying to say.

I would also check out:
https://design-system.service.gov.uk/components/file-upload/
https://home-office-digital-patterns.herokuapp.com/patterns/upload-file
https://github.com/alphagov/govuk-design-system-backlog/issues/49

@sukhrajghuman
I see the reason of misunderstanding. Actually i meant that label should be look like a button, but for some reason didn't add an au-btn class. :) There is no doubt that if something requires clicking it needs to be designed like so.
I think the main accessibility issue with file upload is that native upload provide it's own button and text. I think the better way is without js it should both label and native input. Only with js it converts into button and visually hidden input + some dynamically added element showing which file uploaded. It's not enough to add some css classes for visual appearance
Something like this:

@toxamiz yes but that above example could potentially be confusing in the context of a form with a primary submit button. Hence why in my first example I used the au-btn--secondary.

It's not an easy problem. There are so many edge cases. I will have to talk with our accessibility team for more guidance.
Right now I'm thinking we just stick with the browser default file upload, and add some additional styling (fonts, spacing, errors, focus states etc.) That way we don't have to worry about javascript either.

I will have to talk with our accessibility team for more guidance.

That would be great.

Right now I'm thinking we just stick with the browser default file upload, and add some additional styling (fonts, spacing, errors, focus states etc.) That way we don't have to worry about javascript either.

Good idea. Is there any sketches?

Good idea. Is there any sketches?

Not at this stage sorry. I was basing this off the gov uk implementation of the file upload component, as mentioned in my previous post. Will keep you in the loop


Interrupted write causes corruption

At this line, we use write_all to append some bytes:
https://github.com/tikv/raft-engine/blob/ee0f6cf0d9fd5c4839463bd84edbc009402dffda/src/file_pipe_log/log_file.rs#L107
If this write is interrupted, we directly bubble its error. But some portion of the data might already be written. In this case, the self.written is inconsistent with underlying writer's internal offset. A fractured write will remain as a phantom record.

Maybe we need a new func to support a safe write here? Just like:
index 3f7628c..5f37581 100644
--- a/src/env/mod.rs
+++ b/src/env/mod.rs
@@ -55,4 +55,8 @@ pub trait WriteExt {
     fn truncate(&mut self, offset: usize) -> Result<()>;
     fn sync(&mut self) -> Result<()>;
     fn allocate(&mut self, offset: usize, size: usize) -> Result<()>;
+    fn write_all_safely(
+        &mut self,
+        buf: &mut [u8],
+    ) -> ::std::result::Result<usize, (usize, std::io::Error)>;
 }

No, simply reseek the writer if there's a failure. If that seek fails, panic.

Emm...I didn't get it.
reseek is just a op which reset the offset, and in our self-defined write, reseek and its followed operations in write is just like a redo op by continue triggered by Errno: EINTER.
https://github.com/LykxSassinator/raft-engine/blob/f3c268bb954f63f2809f84a940141db4419b2c44/src/env/default.rs#L116-L138

The purpose here is to make sure subsequent writes can correctly overwrite the failed partial write, so that LogFileWriter::written is always consistent with LogFile::offset, no phantom data is inserted.


feat: Where condition helper library using H2 in memory database

This is a really good PR! Extends Appsmith functionality in plugins with a lot of flexibility and lets us provide deeper features with very little effort in the future.


Not to fail test when tear down steps failed.

Feature Request
Can we have passed test even though there is a failure in tear down?
Why?
Let's say I have two testcases

Logout.spec

Login to app
Logout from app - (failure step)

CreateQuotation.spec

Login to app
Create quotation
_(teardown)
Logout from app

When the logout step is failed, it should fail only the Logout.spec but currently it is giving failure of both Logout.spec and CreateQuotation.spec. This lead to wrong successrate in the report.
SuccessRate
Current Behavior:
SuccessRate: 0%
Expected Behavior
SuccessRate: 50%
Suggested Approach
We shall have the environment variable TearDownFailure=true / false

Depending on the programming language you are using you can catch and ignore the failure on teardown via exception handling. If you ignore the exception the test will not fail.
You can also use the data store or context to selectively control throwing the exception depending on where the teardown step is executed.

from my above example, i use this step in normal step as well as teardown -Logout from app. If i do exceptional handling, it won't capture my main issue right? or i am not understanding the proposed solution?

This is the workaround pseudo code.
step("Logout from app") {
 if(datastore.get("ignore_logout") != true) {
    throw exception;
 }
}

You will have to set this value in the data store in some other step in that specification.
However, please note this is a workaround and not recommended. To find the right error, specifications must fail on teardown too as they can be run independently using a specification name or tags.

This feature is available in robotframework. Teardown failure can make optional. If we bring this feature to gauge, it will give correct success rate in gauge report.

Logout from app -> this step is failed in my main feature test. If i use this step as a teardown in another feature, still it shows that feature failed hence success rate is 100% instead of 50%

@sriv  do you think is it valid feature to consider?

@sriv do you think is it valid feature to consider?

No, sorry. Context and teardowns are syntactic sugar added to make the specs capable of avoiding some repetition. They do not (IMO should not) be loaded with interpretation.
The example that you gave is one where it may make sense in your context, to ignore teardown failures. But this is not the only usecase of teardown, hence cannot be generalized. Adding this as an option leads to situations where reading a step would imply something different than what it actually does in gauge's context.
Also, in your example, if logout is already tested, then the teardown can just be workflow steps without any verification.
Worth noting that gauge is framework agnostic, so it just does not understand the semantics of a user journey, it merely simulates and orchestrates it.


Add initial portuguese translation to runtime class

Add initial translation to runtime class + necessary glossary

/label tide/merge-method-squash
@jailton @devlware thanks for the suggestion. I've commited them, and added the label to squash all the commits until the PR is accepted :)

/lgtm
/approve


Fixed the footer linked pages to scroll to top

What does this pull request aim to achieve? 💯
_Please be concise and link any related issue(s):_This PR Resolves #1790

[x] I have checked that no one else is working on similar changes.
[x] I have read the latest README and understand the development workflow.
[x] The name of this branch is: feature/<branch_name>, or hotfix/<branch_name> if this is a hotfix, where <branch_name> briefly describes the issue(s) resolved and is prefixed with the issue number(s) (e.g. 1127-1130-update-git-branching-model). The branch is created in a cloned version of this repo, not a forked repo.
[x] This branch is rebased/merged with the latest staging (or the latest production if it is a hotfix).
[x] There are no merge conflicts.
[x] There are no console warnings and errors.
[x] On the right hand side of this PR, I have linked the appropriate issue(s) under "Issues" and added a project progress under "Projects".
[x] The title describes the issue(s) being addressed using format: <issue_numbers> - <brief_issue_description> (e.g. #1127/#1130 - Update Git Branching Model)

Feels like this somehow already fixed in staging? maybe it was fixed with https://github.com/FightPandemics/FightPandemics/pull/1709
@rabbi08 can you please confirm this.
@sujatha-m Thank you! your solution works, but another PR has already fixed the same issue I guess. waiting for rabbi08's confirmation before closing this

Feels like this somehow already fixed in staging? maybe it was fixed with #1709
@rabbi08 can you please confirm this.
@sujatha-m Thank you! your solution works, but another PR has already fixed the same issue I guess. waiting for rabbi08's confirmation before closing this

Yes, retested and verified in STG, this is already working. We can close this.
Thanks @sujatha-m


Postgres connection error - "SCRAM authentication requires libpq version 10 or above"

Bug happend in

Version: 0.3.2 -> 0.5.2

Description
This error happend if i try to connect to my supabase postgres database: "SCRAM authentication requires libpq version 10 or above".
Is there an option to solve this error?

Same problem here, if you have any solution I'll take it !

Same problem here.

up, same problem

Linked to:

https://github.com/scram-sasl/info/issues/1

Hi folks! I am not sure if there is any way to upgrade libpq to newer version, because lambdas are using Amazon Linux 2 under the hood. But, I will try to take a look deeper.

Will this fix work? https://stackoverflow.com/a/72703748
I've been using Planetscale instead as my database temporarily and that works for now but would love to get Postgres working.

is there an update?

I have an update:
Found time to work my way into the platform and found a fix for it.
The problem needs to be fixed in libphp. I will put a PR there and hope that @f3l1x will release a new package version for everyone in time :)

@SchramlTim: Where is the PR?
Maybe good to specify ;)

Ofcouse
https://github.com/juicyfx/libphp/pull/376

Same problem too @SchramlTim  i tried to connect using PDO method with php-vercel function: https://github.com/vercel-community/php
how do i use libphp in my project ?
i need create this architecture in my project  just ?
├── dist
// │   └── *.js
└── native
//     ├── lib
//     │   └── * (shared libs)
//     └── php
//         ├── modules
//         │   └── *.so (php modules)
//         ├── composer
//         ├── php.ini
//         ├── php
//         ├── php-cgi
//         ├── php-fpm
//         └── php-fpm.ini

I am working on it. I need to release new version.

Hi, can you folks try new versions?
<EMAIL_ADDRESS>- PHP 8.2.x (https://example-php-8-2.vercel.app/)
<EMAIL_ADDRESS>- PHP 8.1.x (https://example-php-8-1.vercel.app/)
<EMAIL_ADDRESS>- PHP 8.0.x (https://example-php-8-0.vercel.app/)
<EMAIL_ADDRESS>- PHP 7.4.x (https://example-php-7-4.vercel.app/)

@SchramlTim, @MaksOuw, @snuggneighborhood, @irfanhkm, @tao, @HugoBarjot: Can you try the new versions specified by @f3l1x?

Connection work for me with this 0.6.0 version

Tested it too. PHP 8.2 works for me fine.

Awesome. Thank you guys for waiting and @SchramlTim for code updates.

Awesome. Thank you guys for waiting and @SchramlTim for code updates.


[Tracking Issue] Database layer performance and stability

Low Priority

[ ] https://github.com/osmosis-labs/iavl/issues/32

[ ] #1044

nice to have before transitioning to rocks db

[ ] #695

[ ] https://github.com/osmosis-labs/cosmos-sdk/issues/148

Tech Debt

[ ] https://github.com/osmosis-labs/iavl/issues/25
[ ] https://github.com/osmosis-labs/iavl/issues/14

How is this different from the epic?
Is it for low-priority items to be backlogged for the future?

Sorry for the late reply, yeah thats exactly it! Wanted to get peoples thoughts on keeping epics just to the components we want to get done in a certain frame, and then keeping indexes on backlog items in these tracking issues


adding type definitions.

Porting over from https://github.com/typed-contrib/node-amqp10 which has lot of good stuff.
With this PR we will have type definitions shipped with the package itself.
This will make it easy to consume and make changes as and when required.

This change is

I would love this to be merged, as the "typings" client was deprecated in favour of @types npm packages, we no longer have a mechanism to automatically update typedefs.
Merging this PR would help greatly.
I would only exclude/revert the following files:

examples/simple_servicebus_queues.js
-- The newline at the end should be there.
package-lock.json
-- The package-lock is not currently included in the project, and shouldnt be included for libraries.
package.json
-- Revert everything except the ""types": "./typings/lib/index.d.ts"," line; especially requireing typings for node 9.4 in the dependencies or higher is pretty bad.

If a (second) maintainer for this feature is required, then I would be glad to help out.

I would love to see types! But should we maybe create a PR over at https://github.com/DefinitelyTyped/DefinitelyTyped ? That's the official / most used repo to store types

no, it's recommended that libs carry their own typings with them, so they are kept up-to-date with the lib's functionality.  DefinitelyTyped is for community contributions for packages they don't own.

@ps2goat do you have a source on that? Because I only heard / read that it should be published to DefinitelyTyped...

https://github.com/DefinitelyTyped/DefinitelyTyped

If you are the library author and your package is written in TypeScript, bundle the autogenerated declaration files in your package instead of publishing to DefinitelyTyped.

Reviewed 28 of 32 files at r1, 9 of 9 files at r2.
Review status: all files reviewed, 2 unresolved discussions (waiting on @amarzavery)

typings/lib/policies/policy.d.ts, line 36 at r2 (raw file):

declare namespace Policy {
    /** Policy Configuration. */
    export interface Overrides {

This is where I had to pass in sasl configuration, but I don't see a property added in later commits. Would this be a good place for saslMechanism property? Or do you have it somewhere else?  https://stackoverflow.com/a/43913433/2084315

typings/lib/policies/service_bus_policy.d.ts, line 4 at r2 (raw file):

// Project: https://github.com/noodlefrenzy/node-amqp10
// Definitions by: Maxime LUCE <https://github.com/SomaticIT/>
// Definitions: https://github.com/typed-contrib/node-amqp10

It's nice to give credit, but since this will evolve, and is in every file, should the credits be moved to the readme file?  Somewhere visible and in a single place.

Comments from Reviewable

@BorntraegerMarc - that comment got lost in the reviewable.io publish lol.
I guess that this lib isn't written in TypeScript, so technically it could go on DT.  But they call it out on the readme:
https://github.com/DefinitelyTyped/DefinitelyTyped

If you are the library author and your package is written in TypeScript, bundle the autogenerated declaration files in your package instead of publishing to DefinitelyTyped.


any pretrained models for mxnet?

any pretrained models for mxnet?
i try to convert the caffe model to mxnet model
but there is a new layer,do you have any pretrain model for mxent

We do not have pretrained models for MXNet. You can convert the Caffe model to MXNet model easily as the new layer is a combination of Scale layer and Element-wise Layer which have no parameters. Maybe you can refer to the definition of SENets of third-party re-implementation for MXNet.


Online doc shows roles of x-ibm-guard.admin and x-ibm-guard.user, it should be x_ibmrt_gdpva.admin and x_ibmrt_gdpva.user

Describe the bug
Online doc shows roles of x-ibm-guard.admin and x-ibm-guard.user, it should be x_ibmrt_gdpva.admin and x_ibmrt_gdpva.user
Steps to Reproduce
See online documentation

Fixed


403 forbidden, or filters having issues....info, updated filters/profile view

So the team at grindr have been getting cranky.  They have now changed code on their server so that if you are using a free account and try to use the filters, only the free ones will work.  This would be the age, tribes and looking for filters.
The current version on fuckr.me does not have those, but does have the online and photo only, and both of those will not work on free accounts.  On tom's version the app will not throw errors, on the older releases I made, you could get a 403 forbidden error.  Right now the app defaults to photo only being on, so if you run the app and see nothing and that is checked, that is why, it will not allow that xtra feature.
Last week I updated my fork from @tomlandia current release to add the 6 drop down filters back in, and also updated the profile view to show more info when viewing profiles.  This way the releases will be more consistent as this version works fine under windows 10 now.
I believe grindr thinks this will get more people to sign up for xtra, but for me it has the exact opposite effect.  Personally I'm liking this app less and less as time goes on, and their service has gone down hill
I can say, that this somewhat locks things down in some ways, not in others. And that their server itself is not exactly "secure", but that isn't anything I am going to disclose here.

This is most likely an overly noob question but where do I find your version with the 6 filters? If I access Fuckr via your profile, it shows the latest release as 1.81, rather than 2.0.0

What you (all, together) have accomplished is really impressive. When the panic of apiv3 first appeared, i was hoping i'd have time to help, but i had a few personal issues soak up all available time and then some. So all i can do is express thanks and respect from the outside. I'm finally able to look at this once again, and I have a question or two as i set things up:
1, i saw your advice just to clone tomlandia's master and then zip-overwrite your files on top. But I'm confused that github asserts the following three facts:
A. you're 14 committs ahead and 19 behind Tomland
B. Tomlandia last committed code to his tree in February
C. You last updated from the current release 3 weeks ago.
I think this implies that the current release branch is older by at least 15 commits from the current master. I cloned the current master a few days ago. Any idea if it's dangerous/dumb/painful or not a problem if I now zip-overwrite your code on top of the current master? If this merge would be useful to you, i'm happy to give it a try. (Just to spell it out, i used to write code for a living, but haven't for some time and never node.  I'd like to make the effort to get some skills back, just trying to estimate if this is a good way to do that, or a bad one. )
2. One of the things that pushed me to you guys in the first place is that grindr seems to explicitly prevent its own app from running on an intel or mac hardware, as well as on any virtual device. This isn't an API question -- as far as I can tell the code actually checks a few things and shuts down if it doesn't like the neighborhood it just came alive in. It's not a question of not wanting to run on emulation either, It wont start on any version of android-x86 running native either, and that's really android on metal, no emulation. I was just wondering if fuckr does anything to make grindr think it's actually real bona fide grindr code. Given how nasty they've been, actually including client code to make the client committ suicide rather than live on intel hardware, i was just wondering if you think you'll need to spend time at some point pretending to be running in an iOS or android phone.
i'll prob just try to brute-force add your code on top of the master branch right now, to see what happens.
Thanks again for this amazing work. I only hope that grindr doesn't prove to be a service that wasn't worthy of the attention from devs as talented as you all.....

I was actually about to close this as an issue, but I'll leave it a bit longer.  I'm not greatly familiar with github's functionality in detail.  When I forked this from the main branch, we were still on v2 of the api, which was version 1.8.0 or 1.8.1 of fuckr and we had to fix that for a bit back in October.  When I made adjustments, I simply uploaded files that I worked with directly to my github account.
When Thom fixed this version, he made some code changes and which were different from what I had worked with, and then he released his code for the different OSs Linux, Mac, and Windows.  Windows 10 did not like his code at first but was ok with mine, I so had left mine as the old version for a while.  Then with an update Win10 started to behave a little better.  I then updated my code from downloading the app from his site, and updating to add filters back in
The code from both accounts is in sync now, except that I've added back filters and updated the profile views.  Just to be clear, Thom is the author of this, and this version is still considered in alpha stage and has some issues.
As for grindr, they've become quite pissy about things, and now when you run the app, you need to remove the check marks from the online and photo only boxes, as those are paid filters, and grindr updated their code on their server to make sure those won't work unless you have grindr xtra (which isn't worth it imho).
Yes this is a great way to learn some things.  As for grindr, they have code that checks to see if this is runing in an android emulator, and it will close the app on most of them if (which has pissed quite a few potential customers off).  They believe they can protect their code by doing so, they've even gone as far as to obfuscate things with Dexguard.  In my opinion, that can only slow people down a little bit, there is no real security in the app.  They also keep bloating it up on Android and not telling people what they put in there.
  They can tell how long you are in any spot, where you put your finger on your screen, how long you spend on any part, the times you interact in any way with the app, then they take all their analytics and sell that data to companies.    I've totally quit using grindr on android, and barely use it on the computer any more.
There is an unofficial API document on the main page here, if you want to dig through that, there is info in there that would answer some of the questions you've asked.


Bugfix: returns String w/o filters

fix for:
with no filters set the method returns a string (Model::class)

Thanks for the PR!


Anybody succeeded running alphafold on AMD GPU?

Discussing challenges

I have tried alphafold on MI250X but it was much slower than that on Nivida gpu.

HI @saruarlive and @YumengYan, have you managed to use the host memory together with the GPU memory to work on larger models? on AMD GPUs I cannot go past the memory capacity of a single GPU whereas it is possible on NVIDIA GPUs..


feat: implement String for platform for convenience

Added this to make a change in rattler-build easier.

I dont think this implementation makes a lotnof sense. Since Platform inplements display, cant you just call to_string directly on Platform where you need to use this?

I dont think this implementation makes a lotnof sense. Since Platform inplements display, cant you just call to_string directly on Platform where you need to use this?

your right that also works. for some reason, it didn't work at first so I started looking for a solution and this was what that resulted in.


update README.md and .gitignore

Added instructions on how to build
added third_party/cryptopp-cmake to .gitignore

third_party/cryptopp-cmake should already be ignored, as it is a submodule...

it kept appearing as a changed folder somehow


[CustomShortcut] Update docs and model

Changes proposed in this PR:

Update model to use 10 data
Update readme.md

Self evaluation:

Build test: [X]Passed [ ]Failed [ ]Skipped
Run test: [X]Passed [ ]Failed [ ]Skipped

Signed-off-by: Jihoon Lee<EMAIL_ADDRESS>

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

:octocat: cibot: @zhoonit, A builder checker could not be completed because one of the checkers is not completed. In order to find out a reason, please go to http://nnsuite.mooo.com/nntrainer/ci/repo-workers/pr-checker/570-202009221405080.075184106826782-cd6a926031077f92e6d59c4020ee11828def6cca/.

:octocat: cibot: @zhoonit, A builder checker could not be completed because one of the checkers is not completed. In order to find out a reason, please go to http://nnsuite.mooo.com/nntrainer/ci/repo-workers/pr-checker/570-202009221418230.68343997001648-cf132f6001a101f82b336c5b8bb0332f9b320b91/.


chore(docker): Dockerize backend and update docs to include how to run app's docker image

Description
Description
This pull request updates the backend's Docker containerization setup and adds a documentation guildeline on how to get the development server running on your localhost.
The following changes were made

Added a .dockerignore file to exclude unnecessary files from the Docker image.
Updated the Dockerfile to install dependencies and match the new project directory structure.
Improved the README.md documentation to provide clear instructions for building and running the Docker image.

These updates simplify the process of building and running the backend code in a Docker container, reducing setup time and improving developer workflow.

Type of Change

[x] ✨ New feature (non-breaking change which adds functionality)
[ ] 🛠 Bug fix (non-breaking change which fixes an issue)
[x] ❌ Breaking change (fix or feature that would cause existing functionality to change)
[ ] 🧹 Code refactor
[x] ✅ Build configuration change
[x] 📝 Documentation
[x] 🗑 Chore

Changes

Please which part of the project your changes affect ?

[ ] Frontend (Templates, CSS, JS)
[x] Backend (Dancer2, api-docs, Dockerfile)

Hello @manwar 👋
This is ready for review.

Impressive work, keep it up. @baimamboukar

Impressive work, keep it up. @baimamboukar

Thanks very much @manwar ✨
It is a pleasure 🫡✨


local runtime for binance

For fills, can I switch to sendin sending the correct full accumulated quantity instead of new recorded delta

Use curl to debug receiving fills on an order

Scratch sending filled to hub - we send straight to positions from local exchange runtimes


Translation of Navcoin.org Into Arabic

Description
Translation of the NavCoin main site into Arabic would provide access to greater markets.
Motivation
I work for a law firm in a predominately Middle-Eastern community. I am not very familiar with GitHub, but the guide to adding a translation is pretty comprehensive. I am in Pre-Law at the moment, but with what spare time I do have, I will spend translating.
Acceptance Criteria

[ ] Description is satisfied.
[ ] Changes display correctly on desktop / mobile.
[ ] Translations have been added or ammended as necessary.

I would like to claim.


Option to mark filtered tags by colour

Hi, I think the ability to mark the 'severity' of tags we've hidden would be great. I always find myself reading through the list of filtered tags of the works that have been hidden, to see if it's just ones that are more on the mild side that I may not mind in that combination, or if there's something among them I wouldn't touch with a mile-long pole...
A simple way might be marking them red/orange/yellow for severe/moderate/mild, You could have an additional column in the tags table on the options screen with a coloured box beside each tag, which you can then leave blank or click and choose between the r/o/y.
Then, when you open AO3 and you come across a hidden work, it would colour the tags you've marked, letting you easily see if there's a red among them or it's just a bunch of yellow ones that you might want to give a second look.
It's pretty simplistic but I imagine it could be quite effective, reducing the amount of time it takes to find a work we enjoy by a little

Just remembered inverted tag filters, and I think it might work quite well with them. Having the tag automatically be marked green may be an idea, since you can then clearly see by the tag colours which inverted tag(s) overrode which hidden tag(s)


Account Button replaced with User's GitHub Profile Picture

Fixes Issue #9691

Changes proposed

Check List (Check all the applicable boxes)

[x] My code follows the code style of this project.
[x] My change requires changes to the documentation.
[x] I have updated the documentation accordingly.
[x] All new and existing tests passed.
[x] This PR does not contain plagiarized content.
[x] The title of my pull request is a short description of the requested changes.

Screenshots
Before

After

Note to reviewers

Tested on: Environment: Local Development OS: Ubuntu Browser: Firefox works well but the image is too big and while hovering the borders are making it weird as well. After changes:

Then we can remove the borders or we can make them rounded, circle around the image.
I'll try different designs and let you know 👍

Check this out, changed the size to 40, border is now rounded, and also the alt text is more relatable

Check this out, changed the size to 40, border is now rounded, and also the alt text is more relatable

This does look better than the previous hover effect.

Please update the PR description with the latest screenshots

Done

Thank you 👍  please include the response before/after also

I'm not sure why the manage profile navigation link size is bigger than other links?

It's my suggestion, I think for consistent design we should use same size for all navigation links, ensuring they look visually related and don't create confusion for users.

Thank you 👍 please include the mobile responsive before/after also

Surely, I'll include that

I'm not sure why the manage profile navigation link size is bigger than other links?
It's my suggestion, I think for consistent design we should use same size for all navigation links, ensuring they look visually related and don't create confusion for users.

but shrinking user's photo to that size won't look good according to me

Working on the navbar closing issue


fix(oidcprovider): remove semicolon from error output

A picture tells a thousand words

Before this PR
Semicolon would occur after login errors in output.
After this PR
Semicolon will not occur after login errors in output.

Thank you very much @DASPRiD :)


exception class/object expected on /lib/cypress/js_ecqm_calc.rb:44:in `raise' version cypress 4.0.2

Could you provide more information about how you have installed Cypress and what you did to see this error?

Hello robert, I have installed the cypress using VM. I downloaded the VM from github and uploaded to my AWS S3 and from there I imported as AMI using VM-Import and hosted it in AWS.

Could you verify the instance type that the imported VM has on AWS? Also please note that we have an AWS VM that we provide for Cypress v4.0.1. If you install the Cypress v4.0.1 VM you can then upgrade it using the upgrade instructions provided on our wiki which may provide you with an easier experience for getting cypress up and running in AWS.

Its t2-small. While we are using the AMI of cypress we encountered with error. So thats why we used this method to do so.

Just to clarify, did you receive the same error when using the provided AMI or a different error?

We are not able to host from the ami. Actually the guy who hosted this is no more with us. So at present we are having this issue.

Can you try upgrading the type to a t2-large, reboot and see if that works? I believe this is a case of the VM not having enough resources to handle running all of cypress.

sure I will try.
On Thu, Mar 7, 2019 at 10:26 AM Robert Clark<EMAIL_ADDRESS>wrote:

Can you try upgrading the type to a t2-large, reboot and see if that
works? I believe this is a case of the VM not having enough resources to
handle running all of cypress.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/projectcypress/cypress/issues/1115#issuecomment-470569963,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AuA2f8lwsud-zKS56MOOfjP66fVTbiILks5vUS-9gaJpZM4belCB
.

--
Thanks & Regards,
Basaveswar Rao Ramu,
AWS Administrator,
<EMAIL_ADDRESS><EMAIL_ADDRESS>.

@Basaveswarr just wanted to check in and see if this worked for you?

No robert, It doesn't work.
On Tue, Mar 19, 2019 at 9:02 AM Robert Clark<EMAIL_ADDRESS>wrote:

@Basaveswarr https://github.com/Basaveswarr just wanted to check in and
see if this worked for you?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/projectcypress/cypress/issues/1115#issuecomment-474354466,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AuA2fx9j6w68FGKjJaJQpcWm5bxKE2Nbks5vYN_agaJpZM4belCB
.

--
Thanks & Regards,
Basaveswar Rao Ramu,
AWS Administrator,
<EMAIL_ADDRESS><EMAIL_ADDRESS>.

Could you elaborate on the error that was encountered previously from trying to use the AMI? Our AMI build is a supported method that should work, converting an AMI to a VM is completely untested by us and also might open you up to other issues. For example the VM is built with a default username and password login over SSH, meaning there is a chance anyone can SSH into your VM -> AMI conversion. This is not the case with the public AMI.


[Bug] Two binlog task running at the same time may have data loss

What happened
[Bug] Two binlog task running at the same time may have data loss
What you expected to happen
[Bug] Two binlog task running at the same time may have data loss
How to reproduce
[Bug] Two binlog task running at the same time may have data loss
Environment
No response
InLong version
0.12.0
InLong Component
InLong Agent
Are you willing to submit PR?

[X] Yes, I am willing to submit a PR!

Code of Conduct

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

solved in https://github.com/apache/incubator-inlong/pull/3200

solved in https://github.com/apache/incubator-inlong/pull/3200


[Need help] Command for buildkite annotate is being given as an input to docker-compose plugin

I am trying to execute the buildkite annotate command to display the artifacts created by the build as an annotation. I am also using the docker-compose plugin to execute my code through Docker. The issue is that the command is been given to the docker-compose as input and hence the build is failing with the following error:
Running /bin/sh -e -c 'buildkite-agent annotate --style “info” Read the  uploaded test report | 2s
  $ docker-compose -f docker-compose.yml -p buildkitec0a9070575a14d1dbb08c0a600932556 run --name buildkitec0a9070575a14d1dbb08c0a600932556_web-test_build_74 --rm web-test /bin/sh -e -c 'buildkite-agent annotate --style “info” Read the  uploaded test report
Creating buildkitec0a9070575a14d1dbb08c0a600932556_web-test_run ... done
/bin/sh: 2: Syntax error: newline unexpected
⚠ Failed to run command, exited with 2 | 0s
🚨 Error: The command exited with status 2
user command error: The plugin docker-compose command hook exited with status 2

Here are the pipeline steps that I am using:
steps:
  - label: ':chrome: Testing web'
    artifact_paths:
    - "reports/**/*"
    - "screenshots/**/*"
    - "videos/**/*"
    agents:
      queue: <agent_name>
    command: |
      buildkite-agent annotate --style “info” Read the  uploaded test report
    plugins:
      - 'docker-compose#v3.2.0':
          run: web-test
          config: docker-compose.yml

I want to run the buildkite annotate command after Docker has completed the execution.

@AkashD-Developer I was having running into the same issue. So I've created a buildkite plugin to help,
https://github.com/phcyso/annotate-from-file-buildkite-plugin
There is a example in the readme of using it with the docker-compose plugin.

The issue is that this plugin completely takes over the command portion of a step. That means that whatever your use as command (either in the step or as an option to this plugin) will be the one thing run inside of the application container and not after it. The suggestion by @phcyso is one of the ways to achieve what you want, the other would be to setup a more complicated script to be run in the step that does include the annotation.
That said, it is weird to see that error, as if there was a newline or strange character not being shown in the pipeline. If you are still experiencing the issue, let us know to further troubleshoot and track down the root cause


cleanup(rules): graduate 'Disallowed SSH Connection Non Standard Port' to maturity_stable

What type of PR is this?

Uncomment one (or more) /kind <> lines:

/kind feature

/kind bug

/kind cleanup

/kind design

/kind documentation

/kind failing-test

Any specific area of the project related to this PR?

Uncomment one (or more) /area <> lines:

/area rules

/area registry

/area build

/area documentation

Proposed rule maturity level

Uncomment one (or more) /area <> lines (only for PRs that add or modify rules):

/area maturity-stable

/area maturity-incubating

/area maturity-sandbox

/area maturity-deprecated

What this PR does / why we need it:
Graduating rule "Disallowed SSH Connection Non Standard Port" according to our assessment here https://github.com/falcosecurity/rules/pull/147#pullrequestreview-1616742956
@darryk10 @Andreagit97
Which issue(s) this PR fixes:

Fixes #
Special notes for your reviewer:

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: incertum
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [incertum]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

LGTM label has been added.  Git tree hash: 3ec84b35a6f639192a697f06adc69dd444c6f6e3

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: darryk10, incertum
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [incertum]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: darryk10, incertum, LucaGuerra
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [LucaGuerra,incertum]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment


Different properties for primary key and clustered index

Currently, if you define a key as Clustered = true it will become the primary key of the table. And it seems to work well the way it is in 90% of use cases, especially with natural keys.
However it would be even better if you could define the primary key as a separate property PrimaryKey = true.
This would enable us to accomplish some more efficient table designs when using sequential primary keys.
As far as backward compatibility is concerned, you could default the PrimaryKey attribute on the key that has the Clustered attribute and no separate PrimaryKey defined.

Seems like a good idea

This is a great idea! I hope it will be accepted.
Many of my surrogate key tables I've created for my customers performed very poor on list pages. That could really improve them.

Good idea, indeed.

Hi! Thank you for your suggestion. We are working on focusing the activity in this repository on addressing issues related to the AL development tools.
As this issue appears to require changes across multiple areas of our product, we recommend that you post this on our Ideas forum at aka.ms/BCIdeas, or vote up the idea if its already there.
We are constantly monitoring top ideas and will consider them for a future release.


Remove sound label after test completion

What improvement are you suggesting?
Remove sound html after test completion or add sound after testing
Why should make this improvement?
I observed the sound is not coming after completing test. So I will try to add sound. If it is not possible, I will remove the sound html
How can we make these improvements?
I will just remove this html code after button is submitted or add sound.
Additional Context

Hey @hindu-muppala, I think this is an unnecessary addition, the volume slider is at the bottom and doesn't spoil the UI/UX. If you have anymore suggestions or points please share them.
Happy Contributing


New version: PETLION v0.1.3

Registering package: PETLION
Repository: https://github.com/MarcBerliner/PETLION.jl
Created by: @MarcBerliner
Version: v0.1.3
Commit: 7f11555682f954103fa41c3c7d4ccf042d2f39d1
Reviewed by: @MarcBerliner
Reference: https://github.com/MarcBerliner/PETLION.jl/commit/7f11555682f954103fa41c3c7d4ccf042d2f39d1#commitcomment-56681914

block

block


Reject internal pull requests using pull_request_target

This will prevent duplicate runs when both triggers are enabled.
Change-type: patch

I self-certify!


chore: consolidate investor constants

Description
Consolidate redundant constants across the investor domain.
Pull Request Type

[ ] :bug: Bug fix (Non-breaking Change: Fixes an issue)
[x] :hammer_and_wrench: Chore (Non-breaking Change: Doc updates, pkg upgrades, typos, etc..)
[ ] :nail_care: New Feature (Breaking/Non-breaking Change)

Issue (if applicable)
N/A
Risk
Small.
Testing
Regression test the investor/earn app functionality.
Engineering
☝
Operations
☝
Screenshots (if applicable)
N/A

Current dependencies on/for this PR:

develop

PR #4505

PR #4506

PR #4507

PR #4508

PR #4509

PR #4510   👈

This comment was auto-generated by Graphite.

@0xApotheosis queued this pull request to merge with Graphite.

Graphite couldn't merge this pull request because a downstack PR #4507 failed to merge.


Closes #311 | Add dataloader for indonesian_madurese_bible_translation

Closes #311.
Checkbox

[x] Confirm that this PR is linked to the dataset issue.
[x] Create the dataloader script seacrowd/sea_datasets/my_dataset/my_dataset.py (please use only lowercase and underscore for dataset naming).
[x] Provide values for the _CITATION, _DATASETNAME, _DESCRIPTION, _HOMEPAGE, _LICENSE, _URLs, _SUPPORTED_TASKS, _SOURCE_VERSION, and _SEACROWD_VERSION variables.
[x] Implement _info(), _split_generators() and _generate_examples() in dataloader script.
[x] Make sure that the BUILDER_CONFIGS class attribute is a list with at least one SEACrowdConfig for the source schema and one for a seacrowd schema.
[x] Confirm dataloader script works with datasets.load_dataset function.
[x] Confirm that your dataloader script passes the test suite run with python -m tests.test_seacrowd seacrowd/sea_datasets/<my_dataset>/<my_dataset>.py.
[x] If my dataset is local, I have provided an output of the unit-tests in the PR (please copy paste). This is OPTIONAL for public datasets, as we can test these without access to the data files.

Use new packages other than the template:
import jsonlines

Replacing @danjohnvelasco with @ljvmiranda921.

Hi @TysonYu, pls don't forget to change the default message of "Closes ..." into the corresponding dataloader issue number (refer to my updated message on the top of the PR). The data loader PR has been marked as stale since the issue, and this PR isn't connected, and @holylovenia mistakenly removed you from the data loader assignment.

Hi @TysonYu, pls don't forget to change the default message of "Closes ..." into the corresponding dataloader issue number (refer to my updated message on the top of the PR). The data loader PR has been marked as stale since the issue, and this PR isn't connected, and @holylovenia mistakenly removed you from the data loader assignment.

Sorry, my bad. 😂 Added the "Closes #311".


doc: update docs for new features

Docs:

added plugin-configuration.md to explain arguments and permission management
update ca-signed certificate getting started doc

Signed-off-by: Junjie Gao<EMAIL_ADDRESS>

@Two-Hearts Your comment will be resolved in this PR.


Webview get html content

Hello everyone, I know that this's not a Issue, but is there a way of getting the html content of the rendered view in the Webview?
I posted here because I can't find anything on google or stackoverflow

@facebook-github-bot stack-overflow

If you want the html from the url, you could fetch it without a webview.
If it's really the rendered html from the webview you want, I suppose you could inject a javascript function that fires on load end, and posts the DOM content.

@alexsotocx  i want the same thing , have you got any solution ? can you please paste your solution ?

+1 same thing.

+1


Remove unused and deprecated template provider

what

Remove any references to the template provider

why

The template provider is deprecated and no binaries exist for darwin/arm64
The provider is not used in the module or any submodules

references

Provider documentation

/test all


Using mmap instead of allocating large buffer in memory

https://github.com/influxdata/influxdb/blob/df6a5e68e0e61a638b24a0779dc54c51667d52fa/tsdb/series_partition.go#L582
Hello, I am using InfluxDB 1.x and I find when series cardinality is to high, we need allocate too much memory here to compact series. Why don't we use mmap here to avoid large memory allocation?

when series cardinality is too high, compaction will result in out-of-memory and terminate influxd progress.


Update grpc-netty-shaded to 1.48.1

Updates io.grpc:grpc-netty-shaded from 1.47.0 to 1.48.1.
GitHub Release Notes - Version Diff
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "io.grpc", artifactId = "grpc-netty-shaded" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "@monthly" },
  dependency = { groupId = "io.grpc", artifactId = "grpc-netty-shaded" }
}]

labels: test-library-update, early-semver-minor, semver-spec-minor, commit-count:1

Codecov Report

Merging #272 (65595ac) into main (d430b83) will increase coverage by 0.15%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             main     #272      +/-   ##
==========================================
+ Coverage   59.90%   60.06%   +0.15%
==========================================
  Files         153      153
  Lines        3245     3245
  Branches      104      104
==========================================
+ Hits         1944     1949       +5
+ Misses       1301     1296       -5

Impacted Files
Coverage Δ

.../surge/kafka/streams/KafkaStreamManagerActor.scala
55.69% <0.00%> (-1.27%)
:arrow_down:

.../surge/internal/kafka/KafkaProducerActorImpl.scala
77.32% <0.00%> (+0.62%)
:arrow_up:

...a/surge/kafka/KafkaPartitionShardRouterActor.scala
59.06% <0.00%> (+0.67%)
:arrow_up:

...main/scala/surge/internal/akka/cluster/Shard.scala
86.25% <0.00%> (+3.75%)
:arrow_up:

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 514e7db...65595ac. Read the comment docs.


fix typo of translate

What type of PR is this?
/kind documentation
What this PR does / why we need it:
明明空间 -> 命名空间
Which issue(s) this PR fixes:
Fixes #none
Special notes for your reviewer:

Nice finding!
/lgtm

/approve

Thanks @sunbinnnnn , and welcome to Karmada~


Auth example without updating ID state for issued credentials

The current "handle auth request" example updates the issuer's state to include the age credential, then publishes it to RHS and blockchain.
In the attached standalone example, it bumps the issuer state by adding an empty list of creds, then publishes that to both RHS and blockchain, th issues the age credential against that ID state. It runs ok, though I had to give an empty transaction ID (rather than null or undefined) to satisfy the type checking (how is the tx ID used anyway?):
  const credsWithIden3MTPProof = await identityWallet.generateIden3SparseMerkleTreeProof(
    issuerDID,
    res2.credentials,
    ""  // we have no transaction ID since we did not update ID state after issuing credential
  );

I understand that even publishing the genesis state should not be necessary, however I'm unable to adapt this example to demonstrate that. If I comment out the publishing to RHS and/or blockchain, it fails with Error: can't fetch revocation status.
e.g.
============== user handles auth request ==============
ERROR: Error: can't fetch revocation status
    at CredentialWallet.getRevocationStatus (/Users/nedgar/src/open-harbour/polygon-id-js-sdk-tutorial/node_modules/@0xpolygonid/js-sdk/src/credentials/credential-wallet.ts:295:15)
    at processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async CredentialWallet.getRevocationStatusFromCredential (/Users/nedgar/src/open-harbour/polygon-id-js-sdk-tutorial/node_modules/@0xpolygonid/js-sdk/src/credentials/credential-wallet.ts:254:12)
    at async CredentialWallet.findNonRevokedCredential (/Users/nedgar/src/open-harbour/polygon-id-js-sdk-tutorial/node_modules/@0xpolygonid/js-sdk/src/credentials/credential-wallet.ts:415:25)
    at async ProofService.getPreparedCredential (/Users/nedgar/src/open-harbour/polygon-id-js-sdk-tutorial/node_modules/@0xpolygonid/js-sdk/src/proof/proof-service.ts:249:7)
    at async ProofService.generateProof (/Users/nedgar/src/open-harbour/polygon-id-js-sdk-tutorial/node_modules/@0xpolygonid/js-sdk/src/proof/proof-service.ts:187:52)
    at async AuthHandler.handleAuthorizationRequestForGenesisDID (/Users/nedgar/src/open-harbour/polygon-id-js-sdk-tutorial/node_modules/@0xpolygonid/js-sdk/src/iden3comm/handlers/auth.ts:172:25)
    at async handleAuthRequest (/Users/nedgar/src/open-harbour/polygon-id-js-sdk-tutorial/src/handle-auth-no-publish-cred.ts:383:30)

It would be helpful for the examples to show:

publishing only the issuer's ID state and issuing credentials against that, using signature-based proofs to verify creds, even if publishing isn't necessary (like in the attached example)
same but with no publishing

Alternatively, could you update the attached example to show the no publishing scenario?

With config.ts included:
handle-auth-no-publish-cred.zip

@Kolezhniuk please have a look and provide an example of auth handler requesting signature proof, without transitioning the issuer's state.

meanwhile  @nedgar  you can check https://github.com/iden3/polygonid-js-sdk-examples/pull/2
it works fine.

@nedgar Hello!
The example that you've provided works for me. I don't have any issues.
Also, I've checked the token validation here https://jwz.polygonid.me/ and the token is valid also.
One thing I noticed is that you have missed calling await for the next lines of code
   await dataStorage.credential.saveCredential(credential);
and
   await credentialWallet.saveAll(credsWithIden3MTPProof);

Please see the console output below from your example
=============== handle auth request ===============

=============== user did and auth credential===============
DID did:iden3:polygon:mumbai:wxNALoZxnWexpJKDvsb3grVCpU8QWgJfj9w78WiAA
W3CCredential {
  "id": "http://wallet.com/38e44b76-9f55-42d1-98e8-10179bdbf0cc",
  "@context": [
    "https://www.w3.org/2018/credentials/v1",
    "https://raw.githubusercontent.com/iden3/claim-schema-vocab/main/schemas/json-ld/iden3credential-v2.json-ld",
    "https://raw.githubusercontent.com/iden3/claim-schema-vocab/main/schemas/json-ld/auth-v2.json-ld"
  ],
  "type": [
    "VerifiableCredential",
    "AuthBJJCredential"
  ],
  "issuanceDate": "2023-03-08T12:33:51.665Z",
  "credentialSubject": {
    "x": "10571746397287825748586785298116645295039918874040573668743229997189960831142",
    "y": "14685730841763434345582146127929774020407158434763740953500585061238653248826",
    "type": "AuthBJJCredential"
  },
  "issuer": "did:iden3:polygon:mumbai:wxNALoZxnWexpJKDvsb3grVCpU8QWgJfj9w78WiAA",
  "credentialSchema": {
    "id": "https://raw.githubusercontent.com/iden3/claim-schema-vocab/main/schemas/json/auth-v1.json",
    "type": "JsonSchemaValidator2018"
  },
  "credentialStatus": {
    "id": "https://rhs-staging.polygonid.me",
    "revocationNonce": 0,
    "type": "Iden3ReverseSparseMerkleTreeProof"
  },
  "proof": [
    {
      "type": "Iden3SparseMerkleTreeProof",
      "mtp": {
        "existence": true,
        "siblings": []
      },
      "issuerData": {
        "id": "did:iden3:polygon:mumbai:wxNALoZxnWexpJKDvsb3grVCpU8QWgJfj9w78WiAA",
        "state": {
          "rootOfRoots": "0000000000000000000000000000000000000000000000000000000000000000",
          "revocationTreeRoot": "0000000000000000000000000000000000000000000000000000000000000000",
          "claimsTreeRoot": "683ce0b99386c5e2444539435c45fcdca43f0a1b51ea466fb9e6916854662918",
          "value": "69530a630042e4af1de7ea3c72e4fb2dd3e5e5fb87a7bdaa11eb6788bc37101d"
        },
        "authCoreClaim": "cca3371a6cb1b715004407e325bd993c000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000a610b0a0e51e3466572afdb6c181015c30481012c07b6622464a709a7b655f173ae5b6d2be0235525aa99e25f599bd6a9e015d5eea009822b071f5a73fd477200000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000",
        "credentialStatus": {
          "id": "https://rhs-staging.polygonid.me",
          "revocationNonce": 0,
          "type": "Iden3ReverseSparseMerkleTreeProof"
        },
        "mtp": {
          "existence": true,
          "siblings": []
        }
      },
      "coreClaim": "cca3371a6cb1b715004407e325bd993c000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000a610b0a0e51e3466572afdb6c181015c30481012c07b6622464a709a7b655f173ae5b6d2be0235525aa99e25f599bd6a9e015d5eea009822b071f5a73fd477200000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000"
    }
  ]
}

=============== issuer did and auth credential ===============
DID did:iden3:polygon:mumbai:x3rEyMPHv5ERRcxYdCjJm69u49n5r9pVFuxhrQoYi
W3CCredential {
  "id": "http://wallet.com/d41bb014-3ac4-496f-a1db-66d6c7033fad",
  "@context": [
    "https://www.w3.org/2018/credentials/v1",
    "https://raw.githubusercontent.com/iden3/claim-schema-vocab/main/schemas/json-ld/iden3credential-v2.json-ld",
    "https://raw.githubusercontent.com/iden3/claim-schema-vocab/main/schemas/json-ld/auth-v2.json-ld"
  ],
  "type": [
    "VerifiableCredential",
    "AuthBJJCredential"
  ],
  "issuanceDate": "2023-03-08T12:38:43.369Z",
  "credentialSubject": {
    "x": "13090682478546178437121398969741476665836063439244429284879630725052336506556",
    "y": "5631416302020247018723620940442665326311747037756866770815320849584297175560",
    "type": "AuthBJJCredential"
  },
  "issuer": "did:iden3:polygon:mumbai:x3rEyMPHv5ERRcxYdCjJm69u49n5r9pVFuxhrQoYi",
  "credentialSchema": {
    "id": "https://raw.githubusercontent.com/iden3/claim-schema-vocab/main/schemas/json/auth-v1.json",
    "type": "JsonSchemaValidator2018"
  },
  "credentialStatus": {
    "id": "https://rhs-staging.polygonid.me",
    "revocationNonce": 0,
    "type": "Iden3ReverseSparseMerkleTreeProof"
  },
  "proof": [
    {
      "type": "Iden3SparseMerkleTreeProof",
      "mtp": {
        "existence": true,
        "siblings": []
      },
      "issuerData": {
        "id": "did:iden3:polygon:mumbai:x3rEyMPHv5ERRcxYdCjJm69u49n5r9pVFuxhrQoYi",
        "state": {
          "rootOfRoots": "0000000000000000000000000000000000000000000000000000000000000000",
          "revocationTreeRoot": "0000000000000000000000000000000000000000000000000000000000000000",
          "claimsTreeRoot": "d57df7392a4e1432a97db15ffb383d9d398f887fb55bf518a668d01ba4c5b120",
          "value": "9413502dacbbb279b9d6208676bbd44f69605b8bffe62ec5ed4c96b9a76dd90c"
        },
        "authCoreClaim": "cca3371a6cb1b715004407e325bd993c000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000bc06514ea41ef99460ded139f5b5531b77e01d6d7bd95307951a44a94f10f11c086af9c04916ddf173d8ef60de29a2af0c32f9946c86c6950fcd68d8c744730c0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000",
        "credentialStatus": {
          "id": "https://rhs-staging.polygonid.me",
          "revocationNonce": 0,
          "type": "Iden3ReverseSparseMerkleTreeProof"
        },
        "mtp": {
          "existence": true,
          "siblings": []
        }
      },
      "coreClaim": "cca3371a6cb1b715004407e325bd993c000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000bc06514ea41ef99460ded139f5b5531b77e01d6d7bd95307951a44a94f10f11c086af9c04916ddf173d8ef60de29a2af0c32f9946c86c6950fcd68d8c744730c0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000"
    }
  ]
}
================= transition for issuer genesis state =======================
old tree state (hashes): {
  claimsRoot: 'd57df7392a4e1432a97db15ffb383d9d398f887fb55bf518a668d01ba4c5b120',
  revocationRoot: '0000000000000000000000000000000000000000000000000000000000000000',
  rootOfRoots: '0000000000000000000000000000000000000000000000000000000000000000',
  state: '9413502dacbbb279b9d6208676bbd44f69605b8bffe62ec5ed4c96b9a76dd90c'
}
new tree state (hashes): {
  claimsRoot: 'd57df7392a4e1432a97db15ffb383d9d398f887fb55bf518a668d01ba4c5b120',
  revocationRoot: '0000000000000000000000000000000000000000000000000000000000000000',
  rootOfRoots: '648952a44830157fc18e023b6e61f1516529d3498a5338767d272cd2662fb02f',
  state: 'd1309ff3c13a26004f0adc76e85e6c6fd4b5a90334dec69d759f5cfa841a081c'
}
================= push updated issuer state to RHS (Reverse Hash Service) ===================
================= publish issuer state to blockchain, with state transition proof ===================
transaction ID: 0x51755ea15c088f17e8f12b273f53fa393a34f8d8de211a3e4538f2152b0ba081

=============== credential request for issuer to sign ===============
{
  "credentialSchema": "https://raw.githubusercontent.com/iden3/claim-schema-vocab/main/schemas/json/KYCAgeCredential-v3.json",
  "type": "KYCAgeCredential",
  "credentialSubject": {
    "id": "did:iden3:polygon:mumbai:wxNALoZxnWexpJKDvsb3grVCpU8QWgJfj9w78WiAA",
    "birthday": 19960424,
    "documentType": 99
  },
  "expiration":<PHONE_NUMBER>8
}

=============== issued credential, signed ===============
W3CCredential {
  "id": "http://wallet.com/b868a9ca-a4b0-49ea-994f-d4b04b78ae10",
  "@context": [
    "https://www.w3.org/2018/credentials/v1",
    "https://raw.githubusercontent.com/iden3/claim-schema-vocab/main/schemas/json-ld/iden3credential-v2.json-ld",
    "https://raw.githubusercontent.com/iden3/claim-schema-vocab/main/schemas/json-ld/kyc-v3.json-ld"
  ],
  "type": [
    "VerifiableCredential",
    "KYCAgeCredential"
  ],
  "expirationDate": "2361-03-21T19:14:48.000Z",
  "issuanceDate": "2023-03-08T12:46:44.562Z",
  "credentialSubject": {
    "id": "did:iden3:polygon:mumbai:wxNALoZxnWexpJKDvsb3grVCpU8QWgJfj9w78WiAA",
    "birthday": 19960424,
    "documentType": 99,
    "type": "KYCAgeCredential"
  },
  "issuer": "did:iden3:polygon:mumbai:x3rEyMPHv5ERRcxYdCjJm69u49n5r9pVFuxhrQoYi",
  "credentialSchema": {
    "id": "https://raw.githubusercontent.com/iden3/claim-schema-vocab/main/schemas/json/KYCAgeCredential-v3.json",
    "type": "JsonSchemaValidator2018"
  },
  "credentialStatus": {
    "id": "https://rhs-staging.polygonid.me",
    "revocationNonce": 9610,
    "type": "Iden3ReverseSparseMerkleTreeProof"
  },
  "proof": [
    {
      "type": "BJJSignature2021",
      "issuerData": {
        "id": "did:iden3:polygon:mumbai:x3rEyMPHv5ERRcxYdCjJm69u49n5r9pVFuxhrQoYi",
        "state": {
          "rootOfRoots": "0000000000000000000000000000000000000000000000000000000000000000",
          "revocationTreeRoot": "0000000000000000000000000000000000000000000000000000000000000000",
          "claimsTreeRoot": "d57df7392a4e1432a97db15ffb383d9d398f887fb55bf518a668d01ba4c5b120",
          "value": "9413502dacbbb279b9d6208676bbd44f69605b8bffe62ec5ed4c96b9a76dd90c"
        },
        "authCoreClaim": "cca3371a6cb1b715004407e325bd993c000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000bc06514ea41ef99460ded139f5b5531b77e01d6d7bd95307951a44a94f10f11c086af9c04916ddf173d8ef60de29a2af0c32f9946c86c6950fcd68d8c744730c0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000",
        "mtp": {
          "existence": true,
          "siblings": []
        },
        "credentialStatus": {
          "id": "https://rhs-staging.polygonid.me",
          "revocationNonce": 0,
          "type": "Iden3ReverseSparseMerkleTreeProof"
        }
      },
      "coreClaim": "c9b2370371b7fa8b3dab2a5ba81b68382a000000000000000000000000000000011242e4af1de7ea3c72e4fb2dd3e5e5fb87a7bdaa11eb6788bc37101dc80f00c3074857ade4a8ab289ce7aef1f847a7f8ba31738cf87c94f7b936bc92e2351900000000000000000000000000000000000000000000000000000000000000008a25000000000000281cdcdf0200000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000",
      "signature": "106ec5927fe4df4ee9fde1433e2d959db8e00919c26b34912c5c66f4b4219e2771dcb26d993c6766eb4d7decda05ffd9de6e8ae0bef64dc6bd2ade6088332101"
    }
  ]
}
================= add credential to issuer ID wallet claims tree =======================
old tree state (hashes): {
  claimsRoot: 'd57df7392a4e1432a97db15ffb383d9d398f887fb55bf518a668d01ba4c5b120',
  revocationRoot: '0000000000000000000000000000000000000000000000000000000000000000',
  rootOfRoots: '648952a44830157fc18e023b6e61f1516529d3498a5338767d272cd2662fb02f',
  state: 'd1309ff3c13a26004f0adc76e85e6c6fd4b5a90334dec69d759f5cfa841a081c'
}
new tree state (hashes): {
  claimsRoot: '8aad02c548e397a4b6816238463739c357272ba6d93ba973605b263306f51711',
  revocationRoot: '0000000000000000000000000000000000000000000000000000000000000000',
  rootOfRoots: '1518af1b643741d918858df88bec549d07848c52b28228491e046842825c3318',
  state: 'bad8b48cee6a59c49ff214685edf46481f1efc60f53ee67039100ffbe9534924'
}
================= generate Iden3SparseMerkleTreeProof =======================
W3CCredential {
  "id": "http://wallet.com/b868a9ca-a4b0-49ea-994f-d4b04b78ae10",
  "@context": [
    "https://www.w3.org/2018/credentials/v1",
    "https://raw.githubusercontent.com/iden3/claim-schema-vocab/main/schemas/json-ld/iden3credential-v2.json-ld",
    "https://raw.githubusercontent.com/iden3/claim-schema-vocab/main/schemas/json-ld/kyc-v3.json-ld"
  ],
  "type": [
    "VerifiableCredential",
    "KYCAgeCredential"
  ],
  "expirationDate": "2361-03-21T19:14:48.000Z",
  "issuanceDate": "2023-03-08T12:46:44.562Z",
  "credentialSubject": {
    "id": "did:iden3:polygon:mumbai:wxNALoZxnWexpJKDvsb3grVCpU8QWgJfj9w78WiAA",
    "birthday": 19960424,
    "documentType": 99,
    "type": "KYCAgeCredential"
  },
  "issuer": "did:iden3:polygon:mumbai:x3rEyMPHv5ERRcxYdCjJm69u49n5r9pVFuxhrQoYi",
  "credentialSchema": {
    "id": "https://raw.githubusercontent.com/iden3/claim-schema-vocab/main/schemas/json/KYCAgeCredential-v3.json",
    "type": "JsonSchemaValidator2018"
  },
  "credentialStatus": {
    "id": "https://rhs-staging.polygonid.me",
    "revocationNonce": 9610,
    "type": "Iden3ReverseSparseMerkleTreeProof"
  },
  "proof": [
    {
      "type": "BJJSignature2021",
      "issuerData": {
        "id": "did:iden3:polygon:mumbai:x3rEyMPHv5ERRcxYdCjJm69u49n5r9pVFuxhrQoYi",
        "state": {
          "rootOfRoots": "0000000000000000000000000000000000000000000000000000000000000000",
          "revocationTreeRoot": "0000000000000000000000000000000000000000000000000000000000000000",
          "claimsTreeRoot": "d57df7392a4e1432a97db15ffb383d9d398f887fb55bf518a668d01ba4c5b120",
          "value": "9413502dacbbb279b9d6208676bbd44f69605b8bffe62ec5ed4c96b9a76dd90c"
        },
        "authCoreClaim": "cca3371a6cb1b715004407e325bd993c000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000bc06514ea41ef99460ded139f5b5531b77e01d6d7bd95307951a44a94f10f11c086af9c04916ddf173d8ef60de29a2af0c32f9946c86c6950fcd68d8c744730c0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000",
        "mtp": {
          "existence": true,
          "siblings": []
        },
        "credentialStatus": {
          "id": "https://rhs-staging.polygonid.me",
          "revocationNonce": 0,
          "type": "Iden3ReverseSparseMerkleTreeProof"
        }
      },
      "coreClaim": "c9b2370371b7fa8b3dab2a5ba81b68382a000000000000000000000000000000011242e4af1de7ea3c72e4fb2dd3e5e5fb87a7bdaa11eb6788bc37101dc80f00c3074857ade4a8ab289ce7aef1f847a7f8ba31738cf87c94f7b936bc92e2351900000000000000000000000000000000000000000000000000000000000000008a25000000000000281cdcdf0200000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000",
      "signature": "106ec5927fe4df4ee9fde1433e2d959db8e00919c26b34912c5c66f4b4219e2771dcb26d993c6766eb4d7decda05ffd9de6e8ae0bef64dc6bd2ade6088332101"
    },
    {
      "type": "Iden3SparseMerkleTreeProof",
      "mtp": {
        "existence": true,
        "siblings": [
          {
            "bytes": {
              "0": 213,
              "1": 125,
              "2": 247,
              "3": 57,
              "4": 42,
              "5": 78,
              "6": 20,
              "7": 50,
              "8": 169,
              "9": 125,
              "10": 177,
              "11": 95,
              "12": 251,
              "13": 56,
              "14": 61,
              "15": 157,
              "16": 57,
              "17": 143,
              "18": 136,
              "19": 127,
              "20": 181,
              "21": 91,
              "22": 245,
              "23": 24,
              "24": 166,
              "25": 104,
              "26": 208,
              "27": 27,
              "28": 164,
              "29": 197,
              "30": 177,
              "31": 32
            }
          }
        ]
      },
      "issuerData": {
        "id": "did:iden3:polygon:mumbai:x3rEyMPHv5ERRcxYdCjJm69u49n5r9pVFuxhrQoYi",
        "state": {
          "claimsTreeRoot": "8aad02c548e397a4b6816238463739c357272ba6d93ba973605b263306f51711",
          "revocationTreeRoot": "0000000000000000000000000000000000000000000000000000000000000000",
          "rootOfRoots": "1518af1b643741d918858df88bec549d07848c52b28228491e046842825c3318",
          "value": "bad8b48cee6a59c49ff214685edf46481f1efc60f53ee67039100ffbe9534924",
          "txId": ""
        },
        "mtp": {
          "existence": true,
          "siblings": [
            {
              "bytes": {
                "0": 213,
                "1": 125,
                "2": 247,
                "3": 57,
                "4": 42,
                "5": 78,
                "6": 20,
                "7": 50,
                "8": 169,
                "9": 125,
                "10": 177,
                "11": 95,
                "12": 251,
                "13": 56,
                "14": 61,
                "15": 157,
                "16": 57,
                "17": 143,
                "18": 136,
                "19": 127,
                "20": 181,
                "21": 91,
                "22": 245,
                "23": 24,
                "24": 166,
                "25": 104,
                "26": 208,
                "27": 27,
                "28": 164,
                "29": 197,
                "30": 177,
                "31": 32
              }
            }
          ]
        }
      },
      "coreClaim": "c9b2370371b7fa8b3dab2a5ba81b68382a000000000000000000000000000000011242e4af1de7ea3c72e4fb2dd3e5e5fb87a7bdaa11eb6788bc37101dc80f00c3074857ade4a8ab289ce7aef1f847a7f8ba31738cf87c94f7b936bc92e2351900000000000000000000000000000000000000000000000000000000000000008a25000000000000281cdcdf0200000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000"
    }
  ]
}
================= generate credentialAtomicSigV2 proof request ===================
=================  credential auth request message ===================
{
  "id": "fe6354fe-3db2-48c2-a779-e39c2dda8d90",
  "thid": "fe6354fe-3db2-48c2-a779-e39c2dda8d90",
  "typ": "application/iden3comm-plain-json",
  "from": "did:iden3:polygon:mumbai:x3rEyMPHv5ERRcxYdCjJm69u49n5r9pVFuxhrQoYi",
  "type": "https://iden3-communication.io/authorization/1.0/request",
  "body": {
    "callbackUrl": "http://testcallback.com",
    "message": "message to sign",
    "scope": [
      {
        "id": 1,
        "circuitId": "credentialAtomicQuerySigV2",
        "optional": false,
        "query": {
          "allowedIssuers": [
            "*"
          ],
          "type": "KYCAgeCredential",
          "context": "https://raw.githubusercontent.com/iden3/claim-schema-vocab/main/schemas/json-ld/kyc-v3.json-ld",
          "credentialSubject": {
            "birthday": {
              "$lt": 20020101
            }
          }
        }
      }
    ],
    "reason": "verify age"
  }
}

============== user handles auth request ==============
{
  "authRequest": {
    "id": "fe6354fe-3db2-48c2-a779-e39c2dda8d90",
    "thid": "fe6354fe-3db2-48c2-a779-e39c2dda8d90",
    "typ": "application/iden3comm-plain-json",
    "from": "did:iden3:polygon:mumbai:x3rEyMPHv5ERRcxYdCjJm69u49n5r9pVFuxhrQoYi",
    "type": "https://iden3-communication.io/authorization/1.0/request",
    "body": {
      "callbackUrl": "http://testcallback.com",
      "message": "message to sign",
      "scope": [
        {
          "id": 1,
          "circuitId": "credentialAtomicQuerySigV2",
          "optional": false,
          "query": {
            "allowedIssuers": [
              "*"
            ],
            "type": "KYCAgeCredential",
            "context": "https://raw.githubusercontent.com/iden3/claim-schema-vocab/main/schemas/json-ld/kyc-v3.json-ld",
            "credentialSubject": {
              "birthday": {
                "$lt": 20020101
              }
            }
          }
        }
      ],
      "reason": "verify age"
    }
  },
  "authResponse": {
    "id": "018481f3-be42-4643-9c79-4bd8effaba45",
    "typ": "application/iden3-zkp-json",
    "type": "https://iden3-communication.io/authorization/1.0/response",
    "thid": "fe6354fe-3db2-48c2-a779-e39c2dda8d90",
    "body": {
      "message": "message to sign",
      "scope": [
        {
          "id": 1,
          "circuitId": "credentialAtomicQuerySigV2",
          "proof": {
            "pi_a": [
              "17871135223869671998984571254500499965902748590641326266880431426878060616074",
              "11514596717418678124863498017764982140465828305016585011909725125216810983631",
              "1"
            ],
            "pi_b": [
              [
                "9586337403457328519755251660428950990006366341885539386978217151064853867695",
                "19560081597114892129179099483667613552322948213522216428691624508233207574114"
              ],
              [
                "19907112272087332203590182394363584182027028780733221623589025856715556656196",
                "2475349532142251317639943206618745535945853547673019532751607191646931868955"
              ],
              [
                "1",
                "0"
              ]
            ],
            "pi_c": [
              "12055341381747379902908506327985270976050164873581384897042957721336946312908",
              "21792124219223380091504684182761772871718364871519359353110220706414283194913",
              "1"
            ],
            "protocol": "groth16",
            "curve": "bn128"
          },
          "pub_signals": [
            "1",
            "27883838787412540016096521630333663670416136030843855254384674996018614785",
            "5811916808263603644991159609508077569165425645854138777323988284530282730388",
            "1",
            "27455493384769683420575283141384721131198237206075430982574200223193305601",
            "1",
            "12679077567333838331028970265227503467470205999759801691171391734616403423441",
            "1678280248",
            "74977327600848231385663280181476307657",
            "0",
            "20376033832371109177683048456014525905119173674985843915445634726167450989630",
            "2",
            "2",
            "20020101",
            "0",
            "0",
            "0",
            "0",
            "0",
            "0",
            "0",
            "0",
            "0",
            "0",
            "0",
            "0",
            "0",
            "0",
            "0",
            "0",
            "0",
            "0",
            "0",
            "0",
            "0",
            "0",
            "0",
            "0",
            "0",
            "0",
            "0",
            "0",
            "0",
            "0",
            "0",
            "0",
            "0",
            "0",
            "0",
            "0",
            "0",
            "0",
            "0",
            "0",
            "0",
            "0",
            "0",
            "0",
            "0",
            "0",
            "0",
            "0",
            "0",
            "0",
            "0",
            "0",
            "0",
            "0",
            "0",
            "0",
            "0",
            "0",
            "0",
            "0",
            "0",
            "0",
            "0"
          ]
        }
      ]
    },
    "from": "did:iden3:polygon:mumbai:wxNALoZxnWexpJKDvsb3grVCpU8QWgJfj9w78WiAA",
    "to": "did:iden3:polygon:mumbai:x3rEyMPHv5ERRcxYdCjJm69u49n5r9pVFuxhrQoYi"
  },
  "token": "eyJhbGciOiJncm90aDE2IiwiY2lyY3VpdElkIjoiYXV0aFYyIiwiY3JpdCI6WyJjaXJjdWl0SWQiXSwidHlwIjoiYXBwbGljYXRpb24vaWRlbjMtemtwLWpzb24ifQ.eyJpZCI6IjAxODQ4MWYzLWJlNDItNDY0My05Yzc5LTRiZDhlZmZhYmE0NSIsInR5cCI6ImFwcGxpY2F0aW9uL2lkZW4zLXprcC1qc29uIiwidHlwZSI6Imh0dHBzOi8vaWRlbjMtY29tbXVuaWNhdGlvbi5pby9hdXRob3JpemF0aW9uLzEuMC9yZXNwb25zZSIsInRoaWQiOiJmZTYzNTRmZS0zZGIyLTQ4YzItYTc3OS1lMzljMmRkYThkOTAiLCJib2R5Ijp7Im1lc3NhZ2UiOiJtZXNzYWdlIHRvIHNpZ24iLCJzY29wZSI6W3siaWQiOjEsImNpcmN1aXRJZCI6ImNyZWRlbnRpYWxBdG9taWNRdWVyeVNpZ1YyIiwicHJvb2YiOnsicGlfYSI6WyIxNzg3MTEzNTIyMzg2OTY3MTk5ODk4NDU3MTI1NDUwMDQ5OTk2NTkwMjc0ODU5MDY0MTMyNjI2Njg4MDQzMTQyNjg3ODA2MDYxNjA3NCIsIjExNTE0NTk2NzE3NDE4Njc4MTI0ODYzNDk4MDE3NzY0OTgyMTQwNDY1ODI4MzA1MDE2NTg1MDExOTA5NzI1MTI1MjE2ODEwOTgzNjMxIiwiMSJdLCJwaV9iIjpbWyI5NTg2MzM3NDAzNDU3MzI4NTE5NzU1MjUxNjYwNDI4OTUwOTkwMDA2MzY2MzQxODg1NTM5Mzg2OTc4MjE3MTUxMDY0ODUzODY3Njk1IiwiMTk1NjAwODE1OTcxMTQ4OTIxMjkxNzkwOTk0ODM2Njc2MTM1NTIzMjI5NDgyMTM1MjIyMTY0Mjg2OTE2MjQ1MDgyMzMyMDc1NzQxMTQiXSxbIjE5OTA3MTEyMjcyMDg3MzMyMjAzNTkwMTgyMzk0MzYzNTg0MTgyMDI3MDI4NzgwNzMzMjIxNjIzNTg5MDI1ODU2NzE1NTU2NjU2MTk2IiwiMjQ3NTM0OTUzMjE0MjI1MTMxNzYzOTk0MzIwNjYxODc0NTUzNTk0NTg1MzU0NzY3MzAxOTUzMjc1MTYwNzE5MTY0NjkzMTg2ODk1NSJdLFsiMSIsIjAiXV0sInBpX2MiOlsiMTIwNTUzNDEzODE3NDczNzk5MDI5MDg1MDYzMjc5ODUyNzA5NzYwNTAxNjQ4NzM1ODEzODQ4OTcwNDI5NTc3MjEzMzY5NDYzMTI5MDgiLCIyMTc5MjEyNDIxOTIyMzM4MDA5MTUwNDY4NDE4Mjc2MTc3Mjg3MTcxODM2NDg3MTUxOTM1OTM1MzExMDIyMDcwNjQxNDI4MzE5NDkxMyIsIjEiXSwicHJvdG9jb2wiOiJncm90aDE2IiwiY3VydmUiOiJibjEyOCJ9LCJwdWJfc2lnbmFscyI6WyIxIiwiMjc4ODM4Mzg3ODc0MTI1NDAwMTYwOTY1MjE2MzAzMzM2NjM2NzA0MTYxMzYwMzA4NDM4NTUyNTQzODQ2NzQ5OTYwMTg2MTQ3ODUiLCI1ODExOTE2ODA4MjYzNjAzNjQ0OTkxMTU5NjA5NTA4MDc3NTY5MTY1NDI1NjQ1ODU0MTM4Nzc3MzIzOTg4Mjg0NTMwMjgyNzMwMzg4IiwiMSIsIjI3NDU1NDkzMzg0NzY5NjgzNDIwNTc1MjgzMTQxMzg0NzIxMTMxMTk4MjM3MjA2MDc1NDMwOTgyNTc0MjAwMjIzMTkzMzA1NjAxIiwiMSIsIjEyNjc5MDc3NTY3MzMzODM4MzMxMDI4OTcwMjY1MjI3NTAzNDY3NDcwMjA1OTk5NzU5ODAxNjkxMTcxMzkxNzM0NjE2NDAzNDIzNDQxIiwiMTY3ODI4MDI0OCIsIjc0OTc3MzI3NjAwODQ4MjMxMzg1NjYzMjgwMTgxNDc2MzA3NjU3IiwiMCIsIjIwMzc2MDMzODMyMzcxMTA5MTc3NjgzMDQ4NDU2MDE0NTI1OTA1MTE5MTczNjc0OTg1ODQzOTE1NDQ1NjM0NzI2MTY3NDUwOTg5NjMwIiwiMiIsIjIiLCIyMDAyMDEwMSIsIjAiLCIwIiwiMCIsIjAiLCIwIiwiMCIsIjAiLCIwIiwiMCIsIjAiLCIwIiwiMCIsIjAiLCIwIiwiMCIsIjAiLCIwIiwiMCIsIjAiLCIwIiwiMCIsIjAiLCIwIiwiMCIsIjAiLCIwIiwiMCIsIjAiLCIwIiwiMCIsIjAiLCIwIiwiMCIsIjAiLCIwIiwiMCIsIjAiLCIwIiwiMCIsIjAiLCIwIiwiMCIsIjAiLCIwIiwiMCIsIjAiLCIwIiwiMCIsIjAiLCIwIiwiMCIsIjAiLCIwIiwiMCIsIjAiLCIwIiwiMCIsIjAiLCIwIiwiMCIsIjAiLCIwIiwiMCJdfV19LCJmcm9tIjoiZGlkOmlkZW4zOnBvbHlnb246bXVtYmFpOnd4TkFMb1p4bldleHBKS0R2c2IzZ3JWQ3BVOFFXZ0pmajl3NzhXaUFBIiwidG8iOiJkaWQ6aWRlbjM6cG9seWdvbjptdW1iYWk6eDNyRXlNUEh2NUVSUmN4WWRDakptNjl1NDluNXI5cFZGdXhoclFvWWkifQ.eyJwcm9vZiI6eyJwaV9hIjpbIjIxNzM3NTQ1NzAyMzYyODkyMjQ4OTY4OTkyOTQyNTI0MTU5ODExODU3ODA2MTQ3NzIzNzcxMTI4ODAyOTM5OTg0NzEzNTc5NjIxNTE4IiwiMjA0ODU0MTc0OTA0ODg2MTIwNDE2ODE3Mzg1NDc0MjIwNTA2MjM0MTUwNDMxMzQwNzUxNzY3OTAwNjU0MDg0MjA2ODY2OTk1MDYwMyIsIjEiXSwicGlfYiI6W1siMTgxOTIxNTgxMjA4ODQ0MjY2MjQ2NzEyNDEzMjAyMTk2ODkxOTEzOTU3NjIwMDY3OTE5NTI2NDc2NTgxNjczNjU4NzQyNTQxNTQ2MTAiLCIxNjE1Mjc2Mzc2MDU0NzMwOTc5MDE0NjQzMTcwNTk2NTMzMzU1OTU5MDYxOTY1MzI2ODcyNzYxNTcyNDUxOTY3MDU2ODkwMzgwNDIwNyJdLFsiMTk1NjQ4OTM0MTY5MzU3NTYzNDc4MTY4ODM2MjQ1OTkzOTg2MjExMDM1ODIwNjU2ODY3ODMzODEwNDc5MjkyMTM3ODg1MDY0OTI4MjAiLCIxODYzODcyNDM2MTEyNzY2MTcxOTExNzE0MzMwOTIwNDYyMjg0NDY1MzUzODkzNTQ2MDczMDYyNjk4ODc5NTc1MjIxNjc4NDg2MDg4OCJdLFsiMSIsIjAiXV0sInBpX2MiOlsiNDkzOTY5NjA4MDgxODc5NzA5ODYxNDUyNzAxNzkwMjE0NDY3NDU1MzAwODM4NTUwMDUxNTU0MTI3MzI3MjQzNzQ0NTE3Njk5MzYyMCIsIjQ3NDE1MzgxNjc0MDgyOTc4MDQxMDIwNTc1OTU0MjExNzcwMzI0NDg2Nzk5NjE2MDEwNjE2MTAwNTI0NjA2NTAwODY3ODQ3OTAwNTIiLCIxIl0sInByb3RvY29sIjoiZ3JvdGgxNiIsImN1cnZlIjoiYm4xMjgifSwicHViX3NpZ25hbHMiOlsiMjc4ODM4Mzg3ODc0MTI1NDAwMTYwOTY1MjE2MzAzMzM2NjM2NzA0MTYxMzYwMzA4NDM4NTUyNTQzODQ2NzQ5OTYwMTg2MTQ3ODUiLCIxMDM1NDgzNDc2NDk4NjU4Nzc1MDQwNDQ4OTA2NzEwMzM2MDAzMzQ0NjM0Nzg4MTQxODg1NTIyMTI4NjU1MTkzNTY5OTQ1NDI0NjA4NyIsIjIwMTYwNTAwNjUzNzIxMTM0NDExMDU2NjkzNjE0Mzc3MzY2Mzg2OTMzMjk0MzU0MDI1MTM3NDgzMTcyMjgwMjIzOTc1NjMxNzIwOTQyIl19"
}```

I suppose we need to make txId parameter optional and most probably will do that in the next version of SDK
cc @vmidyllic

Thanks @vmidyllic and @Kolezhniuk, #2 answers my questions above. I guess the null transition (no new credentials) I have in example here still bumps the issuer ID out of genesis state, so publishing it is still necessary.

One thing I noticed is that you have missed calling await for the next lines of code

This was copied from the original example. I've commented in #2 to add the missing await there.

Also, I've checked the token validation here https://jwz.polygonid.me/ and the token is valid also.

Nice tool! I was confused for a while about the JWZ token format because I tried deserializing its segments using the shell's base64 -d, but since the input is not padded it drops the last character (}).
e.g. for a JWZ token generated from running #2 just now: eyJhbGciOiJncm90aDE2IiwiY2lyY3VpdElkIjoiYXV0aFYyIiwiY3JpdCI6WyJjaXJjdWl0SWQiXSwidHlwIjoiYXBwbGljYXRpb24vaWRlbjMtemtwLWpzb24ifQ. ..., in shell:
echo -n eyJhbGciOiJncm90aDE2IiwiY2lyY3VpdElkIjoiYXV0aFYyIiwiY3JpdCI6WyJjaXJjdWl0SWQiXSwidHlwIjoiYXBwbGljYXRpb24vaWRlbjMtemtwLWpzb24ifQ | base64 -d yields: {"alg":"groth16","circuitId":"authV2","crit":["circuitId"],"typ":"application/iden3-zkp-json" (missing closing brace). But I think that's just a limitation of the base64 command line expecting padded input. It decodes OK in @iden3/js-jwz's Token.parse.

Given the example in #2, I'll close this. To accomodate various examples, I suggest splitting the index.ts into separate files for each example, even if there's some duplication. I found the progression in the tutorial to be quite clear, and (before learning about this repo), I used separate files -- starting simple and adding code as needed.


Set up issue

I have some problems setting up and I do not know how to solve them.
I am setting up with docker-compose on Windows. The first thing that makes me confused is whether I should type wsl first or not. In this case, I did not do it but the program still seems to work.

After installation, there is an error from the daemon path and it seems like none of the UI in the container works. Or am I missing a way to open other programs?

Another error I received while installing is this error

I haven't used WSL and Docker on Windows for a while now, but I highly recommend sticking with WSL for local development on Windows. It's more Linux-native and will make your developer journey much easier. As I recall, I installed Docker Desktop normally, and then there's a setting to integrate Docker into WSL.
From your first screenshot, it seems like Docker is working fine on your WSL. Sometimes the setup can go wrong or even freeze because the system is resource-consuming and your computer might be struggling to manage the required resources. In my experience, simply rerunning the command or waiting a bit longer (even if the status shows 'unhealthy') often resolves the issue, and Kafka and Ray start up correctly.
To investigate this further, try starting the system without Airflow first. This will make the setup faster and less resource-consuming.  Afterward, examine the logs of all services for any warnings or errors.
For reference, during development, I allocated 11GB of RAM and 6 CPU cores to Docker. It worked fine most of the time, but occasionally I encountered startup errors like yours. Simply rerunning the command usually solved the issue.

I see, ok I will try running the command in wsl and see how it works
Nicha
On Thu, 2 May 2024, 13:52 Ariya Sontrapornpol, @.***>
wrote:

I haven't used WSL and Docker on Windows for a while now, but I highly
recommend sticking with WSL for local development on Windows. It's more
Linux-native and will make your developer journey much easier. As I recall,
I installed Docker Desktop normally, and then there's a setting to
integrate Docker into WSL.
From your first screenshot, it seems like Docker is working fine on your
WSL. Sometimes the setup can go wrong or even freeze because the system is
resource-consuming and your computer might be struggling to manage the
required resources. In my experience, simply rerunning the command or
waiting a bit longer (even if the status shows 'unhealthy') often resolves
the issue, and Kafka and Ray start up correctly.
To investigate this further, try starting the system without Airflow
first. This will make the setup faster and less resource-consuming.  Afterward,
examine the logs of all services for any warnings or errors.
For reference, during development, I allocated 11GB of RAM and 6 CPU cores
to Docker. It worked fine most of the time, but occasionally I encountered
startup errors like yours. Simply rerunning the command usually solved the
issue.
—
Reply to this email directly, view it on GitHub
https://github.com/jomariya23156/sales-forecast-mlops-at-scale/issues/3#issuecomment-2089576200,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AQCK6ENG4EANI5GPBOH3W3LZAHBATAVCNFSM6AAAAABHC5LFJGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAOBZGU3TMMRQGA
.
You are receiving this because you authored the thread.Message ID:
@.***
com>

I'm closing the issue since it seems inactive now. Please feel free to reopen again or open a new one if you have more problems.


Question: Internal http access not working

Hi,
very nice implementation! I have a question how can I use an internal connection without https. I dont want to make the homeassistant instance accessible from the internet. The clock only needs the internal connection via http. At the moment that does not seem to work. This is true for the api as well as the Menu.json file.
Cheers Jan

Hi @janlang,
Due to limitations of the ConnectIQ SDK, we cannot offer support for HTTP in the app.
Documentation

It is important to note that your Home Assistant instance will need to be accessible via HTTPS with public SSL or all requests from the Garmin will not work. This cannot be a self-signed certificate, it must be a public certificate. You can get one for free from Let's Encrypt or you can pay for Home Assistant cloud. (You can install a local Nginx proxy server to manage Let's Encrypt certificates.)

.. Joseph

You can do (almost) the same as we have done in our Trouble Shooting guide. Create a proxy that forwards HTTPS to Home Assistant HTTP. If you use Nginx as the web server you can then use Let's Encrypt for free certificates. Next you need to make sure that the hostname in the certificate can be resolved locally. E.g. adding ther hostname to your local DNS.
I am aware that another user has done something similar and got it working. See the end of this conversation trail.

Ah, I was not aware of the ConnectIQ SDK limitation. The trouble shooting thing I have seen. I hoped that there is an easier solution. Thanks for the answers!


Feature: BPN authorisation validation

Description
The MIW currently hosts a method called getBPNFromToken which is hidden away in a controller base class. For the purposes of Catena-X, the BPN number will always be present in the JWT provided for authorisation, which means we can use the spring-security facilities to ensure that we don't even go near the business logic, unless a BPN claim is provided.
The task is to remove the base controller and add a validator to the security filter chain which will intercept the validated JWT and validate it has a BPN claim.
This is also a great opportunity to fix the injection of Principal into various methods. The correct way would be to use the spring class Authentication (sub-class of the java Principal).
The relevant information is provided in the spring-security resource server JWT docs: https://docs.spring.io/spring-security/reference/servlet/oauth2/resource-server/jwt.html
One way which would work is to provide a custom @Bean jwtDecoder and inject our validator there.
Sidenote: This will guarantee that developers can use the Authentication injection and directly read the BPN claim, without doing any extra checks, which will, in turn, clean up the code quite a lot.
Acceptance Criteria

[ ] Authorisation checks for a BPN claim and rejects tokens which do not include it
[ ] BaseController removed
[ ] Injection of Principal changed to Authentication

Maybe we can unitise  exiting CustomAuthenticationConverter and return a subclass of JwtAuthenticationToken (which takes BPN as a constructor) and we can directly inject this in the controller when needed

Hi @nitin-vavdiya,
this isn't needed, as the Authentication object is already a rich JWT object, which means there's no need to do extra work in the converter.


TagBot trigger issue

This issue is used to trigger TagBot; feel free to unsubscribe.
If you haven't already, you should update your TagBot.yml to include issue comment triggers.
Please see this post on Discourse for instructions and more details.
If you'd like for me to do this for you, comment TagBot fix on this issue.
I'll open a PR within a few hours, please be patient!

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/43943

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/44200

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/44202

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/44227


"Unknown Cipher: aes256-ctr" when using SSH slaves in LTS container

I was getting this error when using SSH slaves in jenkins/jenkins:lts
SSHLauncher{host='ne1-mgmt-mac1', port=22, credentialsId='ssh-key for jenkins@ne1-mgmt-mac1', jvmOptions='', javaPath='', prefixStartSlaveCmd='', suffixStartSlaveCmd='', launchTimeoutSeconds=210, maxNumRetries=10, retryWaitTime=15, sshHostKeyVerificationStrategy=hudson.plugins.sshslaves.verifiers.ManuallyTrustedKeyVerificationStrategy, tcpNoDelay=true, trackCredentials=true}
[03/08/19 01:58:27] [SSH] Opening SSH connection to ne1-mgmt-mac1:22.
[03/08/19 01:58:27] [SSH] SSH host key matches key seen previously for this host. Connection will be allowed.
ERROR: SSH authentication failed
java.lang.IllegalArgumentException: Unknown Cipher: aes256-ctr
    at com.trilead.ssh2.signature.OpenSshCertificateDecoder$SshCipher.getInstance(OpenSshCertificateDecoder.java:207)

I switched containers to jenkins/jenkins and the issue fixed without having to make any configuration changes.
Maybe this issue is fixed already but I just wanted to make sure that it gets reported and that people googling the error might see this :)

Sounds like fixed in weekly along time ago


[DEP-267] Release 2.8.1

Description
SDK Release 2.8.1

Upgrade SDK libraries version to 2.8.1
Update CHANGELOG to include main features included in this release.
Update README.md with references to the latest version
Update project set up (gradle version, target SDK, etc...)

References
DEP-267
Testing

[ ] Complete 3 steps flow with Zoom liveness.
[ ] Complete 3 steps flow with face capture.

Checklist

[X] I have added documentation for new/changed functionality in this PR or in auth0.com/docs
[X] All active GitHub checks for tests, formatting, and security are passing
[X] The correct base branch is being used, if not master

QA approved.