ModuleNotFoundError: No module named 'PerceptualSimilarity'

how could I solve this problem?

https://github.com/ManuelFritsche/real-world-sr/issues/4


Add parcels package

Ocean Parcels is an awesome tool to run lagrangian particles. It used to be on the notebook image for ocean.pangeo.io and due to the heavy list of dependencies, it is cumbersome to install on the fly.
Could we add this to the standard notebook image?

thanks @jbusecke , fine by me, but we have to tackle https://github.com/pangeo-data/pangeo-cloud-federation/issues/859 before this new environment can be used in the hub by default.
also, just a note that the pangeo-notebook image is now 3.4GB... would be great to revisit ways to make this slimmer to speed up start times https://github.com/pangeo-data/pangeo-docker-images/pull/162/checks?check_run_id=1398080473

also, just a note that the pangeo-notebook image is now 3.4GB...

Is this due to this addition? Or has it grown in general? If its the former, I am very unsure how we could slim this down. Part of my motivation to add this particular package to the main notebook is that I am having trouble manually installing all the dependencies (see here).

it's hard to tell exactly, because this addition also updates existing packages, but the size bump with this PR is ~400MB comparing to current master image:
REPOSITORY               TAG                 IMAGE ID            CREATED             SIZE
pangeo/pangeo-notebook   master              fd5c23c0d0e5        3 days ago          3.04GB

@jbusecke don't worry about addressing the size in this PR, I was just wanted to flag and we can continue the size and packages discussion here https://github.com/pangeo-data/pangeo-docker-images/issues/28

Thanks for the follow up. So this one is currently on hold until upstream issues are fixed? Is there anything else I can do to help at this point?

Yes @jbusecke , this is currently on hold, but it seems like you can use the workaround detailed here for now https://github.com/pangeo-data/pangeo/pull/792#issuecomment-727132517

I noticed that parcels is still not available on the production env. Is this still held up by the above? Or did something go wrong?

@jbusecke as of https://github.com/pangeo-data/pangeo-cloud-federation/pull/897 parcels is now on the staging hubs:
(notebook) jovyan@jupyter-scottyhq:~$ conda list | grep parcels
parcels                   2.2.1            py38h32f6830_0    conda-forge

Thanks a lot for the headsup @scottyhq


Incorrect typing (or too generic) for Subquery.c or Table.c

Describe the bug
Mypy complains about missing attribute or incompatible types in assignment.
Expected behavior
Mypy not complaining
To Reproduce
x = Table("x", metadata, Column("aaa", Integer, primary_key=True))
sq = select(x).subquery()
columns: ColumnCollection = sq.c if sq else x.c  # either add or remove typing to see one of two errors
columns.aaa

Error
Incompatible types in assignment (expression has type "object", variable has type "ColumnCollection[Any]")
"object" has no attribute "aaa"

Versions.

OS: Linux Mint 20.1
Python: 3.7.10
SQLAlchemy: 1.4.22
mypy: 0.910
SQLAlchemy2-stubs: 0.0.2a6

Additional context
Happens after upgrading from 0.0.2a4 to 0.0.2a6
Have a nice day!

This is working as expected. The issue is that you cannot do sq.c if sq else x.c, since you will get TypeError: Boolean value of this clause is not defined, you need to do sq.c if sq is not None else x.c.
Sadly mypy error is not clear in this case

Actually never got this error :stuck_out_tongue: .


How to average spinal cord segmentations across contrasts

Context
In order to generate a unique soft segmentation (related to #2), we want to average spinal cord segmentations across contrasts. However, because the images don't have the same FOV, we need to come up with a method on how to take this issue into account.
Suggestion

Put all voxels of images to 1.
Apply transformation to align with T2w contrast. --> Use linear interpolation
Add all warped images.
Add all aligned segmentations. (also use linear interpolation for alignement)
Divide the summed segmentation by the summed image (of 1).

Great! Thanks @charleygros!

So I've tested out the method!
Two problems with the method:

T1w SC segmentation and T2w don't necessarly start at the same slice, the value of the softseg can be of 0.5 at the top:

Some top and bottom slices segmentation are missing most of the time with sct_deepseg_sc on MTS data, so once again the averaging is affected.
With manual correction, it can be fixed, and if so, it will definitely help with registration too!
Or we don’t count MTS data in the mean, but the registration is not that good at the end due to missing slices.

I will need to explore with more data for MTS, but here is an example, even with manual correction, it will maybe be difficult to add the missing slices...

To resolve this, maybe instead of putting all the images to 1, we could take the registered segmentation and put all non-zero values to 1, dilate the seg (we want the coverage map to include all the segs) and add those images toghether, so it would take into account only where we have the segmentation.

I re-read this several times but I still don't understand by "dilate the seg"? How should it be dilated, by how much, and how will that solve the "missing segmented slice" problem?
However, this seg dilation gave me an idea (maybe it is what you suggested): instead of creating the coverage map by putting all-one to the native image, we could instead apply a gigantic dilation (e.g. kernel of 500) to each slice of the segmentation. If there is a segmentation at a slice, then the whole slice will be ones. If there is no segmentation, the whole slice will be all zeros.

However, this seg dilation gave me an idea (maybe it is what you suggested): instead of creating the coverage map by putting all-one to the native image, we could instead apply a gigantic dilation (e.g. kernel of 500) to each slice of the segmentation. If there is a segmentation at a slice, then the whole slice will be ones. If there is no segmentation, the whole slice will be all zeros.

Yes that was exactly the idea!!! Sorry if the explanation was not clear 🙂

Note: oopsie, msg written 2hrs ago, forgot to send

I will need to explore with more data for MTS, but here is an example, even with manual correction, it will maybe be difficult to add the missing slices...

Not sure to understand what you mean here. Can you help me.

To resolve this, maybe instead of putting all the images to 1, we could take the registered segmentation and put all non-zero values to 1, dilate the seg (we want the coverage map to include all the segs) and add those images toghether, so it would take into account only where we have the segmentation

Question: Do you fill with ones before or after the resgistration? I think it should be done before registration --> at the top slices the MTS_reg (small IS coverage) will be zeros --> it will not contribute the the division of these slices.
In other words:

slice 0: contrasts T1 and T2: division by 2
slice 10: contrasts T1, T2 MTS: division by 3
slice 58: contrasts: T1: division by one

Am I missing something here?

I will need to explore with more data for MTS, but here is an example, even with manual correction, it will maybe be difficult to add the missing slices...

Not sure to understand what you mean here. Can you help me.

I meant that the data quality is not always good for the first and last slices that we sometimes don't really see the spinal cord, so even if we wanted to manually correct those slices, it would not necessarily be acurate!

What about doing a IS_masking (based on the sct_deepseg_sc output) on the coverage file before registration?
Example: IS coverage: 0 to 100. IS coverage of seg: 10 to 98 --> put zeros to slices 0:10 and 99:100 on the coverage image

yes that could be a solution too!

I've generated the coverage map using dilated segmentations, softseg results look great 😊
This softseg was generated using T1w, T2w, T2star, T1w_MT, MTon_MTS and dwi!
(btw, the surrounding dark red are values very close to zero)


fix: footer UI misalignment

fixes #972
Fixed UI:

Please see the conflicts . Resolve the conflicts . Ensure you pull all the latest changes before pushing your feature/bug fixes to the main branch. After resolving the conflicts, please open a new PR for review.
Thank you!

@PriyaGhosal Fixed the conflicts and raised a new PR #1033. Please take a look.


Optimize LCOW snapshotter to only copy scratch vhd on the final snapshot

For LCOW currently we copy (or create) the scratch.vhd for every single snapshot so there ends up being a sandbox.vhd in every directory seemingly unnecessarily. With the default scratch size of 20GB the size on disk is about 17MB so there's a 17MB overhead per layer plus the time to copy the file with every snapshot. Only the final sandbox.vhd is actually used so this would be a nice little optimization.
Signed-off-by: Daniel Canter<EMAIL_ADDRESS>

I'd like to get feedback on this PR as assuming the key format will stay the way it is to solve this is a gross hack but I can't think of another way to handle this without bringing labels into the equation.

ping @kevpar

@dcantah - Thanks for doing this!

@jterry75 For sure :) We can benefit from this for WCOW also as the exact same thing ends up happening past the base layer. I'll likely add that also today

@cpuguy83 do you wanna review this one?

LGTM


Remove CRAN override from Connect chart value

Motivation: If a user specifies a non-PPM version of CRAN (e.g., https://cran.r-project.org/)  when deploying to Connect, the current Helm chart overrides it with the PPM version of CRAN, which may not yet have the latest version of a package.
This change (1) removes this constraint (while still having RSPM pointing to PPM as a fall back) and (2) mirrors the workbench Helm chart (changed here)

Connect v2023.09 has some modifications to the default PackageURL behavior.

Connect has new strategies for resolving the set of R package repositories used to install packages in content environments, and controlling how configured RPackageRepository entries and content repositories are used. These are controlled with the setting R.PackageRepositoryResolution. The default behavior has changed. The new default, lax, uses a combined list of configured repositories and repositories from content. To use only configured repositories and discard content repositories, set to strict. To use the old overriding behavior, set to legacy. See the Admin Guide for more details and examples. (#23853)

Does the new default behavior make this change unnecessary?
cc @toph-allen

Brilliant! lax is exactly what I think would solve this. Much appreciated!
For more context, see https://support.posit.co/hc/en-us/requests/91166 where we'd previously discussed.


Cannot build generated ruby2.5 Hello World app

Description
A basic ruby2.5 app generated using sam init fails to build locally.
Steps to reproduce

sam init --runtime ruby2.5 -n rsam
cd rsam
sam build --use-container

Observed result
$ sam build --use-container --debug
2018-12-07 09:36:33 Using SAM Template at /Users/adrian/code/play/sam/rsam/template.yaml
2018-12-07 09:36:33 Changing event name from creating-client-class.iot-data to creating-client-class.iot-data-plane
2018-12-07 09:36:33 Changing event name from before-call.apigateway to before-call.api-gateway
2018-12-07 09:36:33 Changing event name from request-created.machinelearning.Predict to request-created.machine-learning.Predict
2018-12-07 09:36:33 Changing event name from before-parameter-build.autoscaling.CreateLaunchConfiguration to before-parameter-build.auto-scaling.CreateLaunchConfiguration
2018-12-07 09:36:33 Changing event name from before-parameter-build.route53 to before-parameter-build.route-53
2018-12-07 09:36:33 Changing event name from request-created.cloudsearchdomain.Search to request-created.cloudsearch-domain.Search
2018-12-07 09:36:33 Changing event name from docs.*.autoscaling.CreateLaunchConfiguration.complete-section to docs.*.auto-scaling.CreateLaunchConfiguration.complete-section
2018-12-07 09:36:33 Changing event name from before-parameter-build.cloudsearchdomain.Search to before-parameter-build.cloudsearch-domain.Search
2018-12-07 09:36:33 Changing event name from docs.*.cloudsearchdomain.Search.complete-section to docs.*.cloudsearch-domain.Search.complete-section
2018-12-07 09:36:33 Changing event name from before-parameter-build.logs.CreateExportTask to before-parameter-build.cloudwatch-logs.CreateExportTask
2018-12-07 09:36:33 Changing event name from docs.*.logs.CreateExportTask.complete-section to docs.*.cloudwatch-logs.CreateExportTask.complete-section
2018-12-07 09:36:33 Changing event name from creating-client-class.iot-data to creating-client-class.iot-data-plane
2018-12-07 09:36:33 Changing event name from before-call.apigateway to before-call.api-gateway
2018-12-07 09:36:33 Changing event name from request-created.machinelearning.Predict to request-created.machine-learning.Predict
2018-12-07 09:36:33 Changing event name from before-parameter-build.autoscaling.CreateLaunchConfiguration to before-parameter-build.auto-scaling.CreateLaunchConfiguration
2018-12-07 09:36:33 Changing event name from before-parameter-build.route53 to before-parameter-build.route-53
2018-12-07 09:36:33 Changing event name from request-created.cloudsearchdomain.Search to request-created.cloudsearch-domain.Search
2018-12-07 09:36:33 Changing event name from docs.*.autoscaling.CreateLaunchConfiguration.complete-section to docs.*.auto-scaling.CreateLaunchConfiguration.complete-section
2018-12-07 09:36:33 Changing event name from before-parameter-build.cloudsearchdomain.Search to before-parameter-build.cloudsearch-domain.Search
2018-12-07 09:36:33 Changing event name from docs.*.cloudsearchdomain.Search.complete-section to docs.*.cloudsearch-domain.Search.complete-section
2018-12-07 09:36:33 Changing event name from before-parameter-build.logs.CreateExportTask to before-parameter-build.cloudwatch-logs.CreateExportTask
2018-12-07 09:36:33 Changing event name from docs.*.logs.CreateExportTask.complete-section to docs.*.cloudwatch-logs.CreateExportTask.complete-section
2018-12-07 09:36:33 'build' command is called
2018-12-07 09:36:33 Starting Build inside a container
2018-12-07 09:36:33 Looking for credentials via: env
2018-12-07 09:36:33 Found credentials in environment variables.
2018-12-07 09:36:33 Loading JSON file: /Users/adrian/Library/Python/2.7/lib/python/site-packages/botocore/data/endpoints.json
2018-12-07 09:36:33 Event choose-service-name: calling handler <function handle_service_name_alias at 0x107f811b8>
2018-12-07 09:36:33 Loading JSON file: /Users/adrian/Library/Python/2.7/lib/python/site-packages/botocore/data/serverlessrepo/2017-09-08/service-2.json
2018-12-07 09:36:33 Event creating-client-class.serverlessapplicationrepository: calling handler <function add_generate_presigned_url at 0x107f31f50>
2018-12-07 09:36:33 The s3 config key is not a dictionary type, ignoring its value of: None
2018-12-07 09:36:33 Setting serverlessrepo timeout as (60, 60)
2018-12-07 09:36:33 Loading JSON file: /Users/adrian/Library/Python/2.7/lib/python/site-packages/botocore/data/_retry.json
2018-12-07 09:36:33 Registering retry handlers for service: serverlessrepo
2018-12-07 09:36:33 No Parameters detected in the template
2018-12-07 09:36:33 2 resources found in the template
2018-12-07 09:36:33 Found Serverless function with name='HelloWorldFunction' and CodeUri='hello_world/'
2018-12-07 09:36:33 Trying paths: ['/Users/adrian/.docker/config.json', '/Users/adrian/.dockercfg']
2018-12-07 09:36:33 Found file at path: /Users/adrian/.docker/config.json
2018-12-07 09:36:33 Found 'auths' section
2018-12-07 09:36:33 Auth data for https://274391695091.dkr.ecr.eu-west-1.amazonaws.com is absent. Client might be using a credentials store instead.
2018-12-07 09:36:33 Auth data for<PHONE_NUMBER>30.dkr.ecr.eu-west-1.amazonaws.com is absent. Client might be using a credentials store instead.
2018-12-07 09:36:33 Auth data for<PHONE_NUMBER>91.dkr.ecr.eu-west-1.amazonaws.com is absent. Client might be using a credentials store instead.
2018-12-07 09:36:33 Auth data for https://653789070130.dkr.ecr.eu-west-1.amazonaws.com is absent. Client might be using a credentials store instead.
2018-12-07 09:36:33 Found 'credsStore' section
2018-12-07 09:36:33 Building resource 'HelloWorldFunction'
Build Failed
Error: 'ruby2.5' runtime is not supported

Expected result
Having completed the quick start in Python, I'm attempting to replicate the example app using ruby.
I'd expect the app to build locally.
Additional environment details (Ex: Windows, Mac, Amazon Linux etc)
MacOS: 10.14.1
SAM CLI, version 0.8.1
Docker version 18.09.0, build 4d60db4

Add --debug flag to command you are running

Currently only Python is supported. You can track Ruby update in this issue: #806
Closing as duplicate

Hi, @jfuss how would you suggest I proceed?  I'm just trying to get started and the Hello World example doesn't seem to work in Ruby (or go or node - I tried them too).  That doesn't seem right to me so I must be missing something.

All examples have README.md files that you should follow. This will show you the flow that you will need to follow.

Thanks @jfuss.  That's solved things for me.
Have you considered updating the Hello World documentation to remove the build step?
My reasons for doing so would be...

It's not supported for all runtimes (hence this conversation)
As a beginner, it's not really clear to me what the benefit of building locally would be.  It seems you don't need it to work locally on an app so I'm guessing it's useful in a more advanced use case I haven't encountered
It appears to break hot reload based on my observations

It's not supported for all runtimes (hence this conversation)

Previously (before build), the Quickstart examples where specific to Python with no way to replicate the flow to any other language. This was because you needed to copy your source code into a build folder manually, which was only specific to Python. With the introduction of sam build, this allows us to formulate this workflow into a command that can span each different runtime or language. So the example is support to only work in Python. We could document this but then each release we are tied to a doc update. Instead and since the first example only ever worked for Python, we left it as is and will roll out languages. The command output is also pretty clear on why 'build' didn't work.

As a beginner, it's not really clear to me what the benefit of building locally would be. It seems you don't need it to work locally on an app so I'm guessing it's useful in a more advanced use case I haven't encountered

If you have dependencies, you absolutely need to build, install requirements/dependencies, compile your code to the right architecture and os. You need build if you meet this requirement. sam build gives us a way to make this runtime agnostic.

It appears to break hot reload based on my observations

Hot reloading still works. Previously, you needed to copy your source into a build directory (for Python) or compiling a binary before invoking the function. The way invokes work (sam local [invoke|start-api|start-lambda]) is the template is read, code location is found, and then mounted. This means you can do hot reloading but you may need to run sam build in a different terminal window or copy the edited file(s) or recompile the binary to where the CodeUri points. Invokes never hot reloaded to the affect of build previously but can be solved through sam build --watch command we are looking to add or make the invoke path also build.

Hi @jfuss,
Ok, I finally got the point of SAM build.  Thanks for clarifying.  Although everything you have said is correct, I still feel that the introductory docs could be improved as they are confusing for beginners.

We could document this but then each release we are tied to a doc update.

An alternative would be to say that support for other runtimes is being rolled and so you should check the readme generated by sam init.

The command output is also pretty clear on why 'build' didn't work.

Do you mean Error: 'ruby2.5' runtime is not supported?   Yes, that's right but it doesn't give a novice any guidance on how to resolve the issue.
Referring the me to the generated readme would have helped in this case too.

Hot reloading still works...but you may need to run sam build

Ah ok, that would explain my issue. It's obvious with hindsight but it wasn't at the time.


When enable minify,  it print error "Library class android.content.res.XmlResourceParser implements program class org.xmlpull.v1.XmlPullParser"

AGPBI: {"kind":"error","text":"Library class android.content.res.XmlResourceParser implements program class org.xmlpull.v1.XmlPullParser","sources":[{}],"tool":"R8"}

This is because this library depends on the Simple XML parser (org.simpleframework:simple-xml), which uses XmlPullParser. The library maintainer could consider replacing it. For us as consumers, we can ignore this error by configuring ProGuard.
I have the following lines in my release config, but I think only the last one is really needed: don't warn about this library using the XmlResourceParser (indirecty through Simple XML). Let me know how it goes for you.
-dontwarn org.xmlpull.v1.**
-keep class org.xmlpull.v1.** { *; }
-dontwarn android.content.res.XmlResourceParser

I ran the latest release build of my app I created with this and observed the DAV functionality working as expected.

I'm very sorry for the late reply. I'm the maintainer of the library but I don't see many alternatives to SimpleXML. Any suggestion?
Would it help if I added -dontwarn android.content.res.XmlResourceParser to the Proguard file of the library?

I'm very sorry for the late reply. I'm the maintainer of the library but I don't see many alternatives to SimpleXML. Any suggestion? Would it help if I added -dontwarn android.content.res.XmlResourceParser to the Proguard file of the library?

This is helpful.


Close menu after select (click) any child

Hi,
Thanks for this awesome component.
I'm using it to trigger some actions but I want to close the menu after the user clicks in some child element.
¿Any ideas?
Regards.

Well I found a way to do it:
Create a ref for the menu:
<Menu ... ref={(node) => this.node = node}>
Then create a helper for the onClick method of childMenu:
onClickHelper= () => {       ...       this.node.toggleMenu(event); };
Add the helper function to the onClick method of the childMenu:
<ChildButton ... onClick={onClickHelper}/>
If there is another better way to do it please share it.
Regards.

I'm not sure what the cause is, but the current version of react-mfb does not pass an event to the handleOnClick method of ChildButton. You can hack this locally by editing the child-button.js file to pass along the event.
What I ended up doing is stubbing a fakeEvent:
const fakeEvent = {preventDefault: () => {}};

Then passing this along in onClickHelper
onClickHelper = () => { ... this.node.toggleMenu(fakeEvent); };

I'm here for this too...
My solution until now is...
...
const mainMenuRef = React.createRef()
...
<MainButton ref={mainMenuRef} iconResting="fa fa-plus" iconActive="fa fa-times" className="bg-primary text-white" />
...
const handleChildBtnClick = (e) => {
        const el = ReactDOM.findDOMNode(mainMenuRef.current);
        if(el) el.click();
}

@ramyres110 I am facing the issue where the icon is not showing. Can you help me in that please


Failed to install Provider on GKE cluster - cannot establich control of object: cannot deploy a CRD with webhook conversion strategy without having a TLS bundle

What happened?

When installing the provider within a GKE cluster, it fails to install with the following error message:
Events:
  Type     Reason             Age                 From                                         Message
  ----     ------             ----                ----                                         -------
  Normal   BindClusterRole    23m (x6 over 30m)   rbac/providerrevision.pkg.crossplane.io      Bound system ClusterRole to provider ServiceAccount(s)
  Normal   ApplyClusterRoles  23m (x3 over 30m)   rbac/providerrevision.pkg.crossplane.io      Applied RBAC ClusterRoles
  Warning  SyncPackage        29s (x37 over 30m)  packages/providerrevision.pkg.crossplane.io  cannot establish control of object: cannot deploy a CRD with webhook conversion strategy without having a TLS bundle

I didn't find any documentation on how to troubleshoot it nor to fix it, as there isn't anything relevant on crossplane logs.
How can we reproduce it?

I just really installed provider in the cluster:
cat << EOF | kubectl apply -f -
apiVersion: pkg.crossplane.io/v1
kind: Provider
metadata:
  name: provider-kubernetes
spec:
  package: xpkg.upbound.io/crossplane-contrib/provider-kubernetes:v0.14.0
EOF

What environment did it happen in?
Crossplane version: v1.9.2

Cloud provider: GCP
Kubernetes version: v.28,90gke.1289000
Kubernetes distribution GKE

I just tried this scenario with crossplane v1.16.0. I see you're finding this issue with v1.9.2 which is a bit old and no longer a supported version: https://github.com/crossplane/crossplane?tab=readme-ov-file#releases
Would it be possible for you to try this scenario again with a newer version of Crossplane? 🙇♂ https://docs.crossplane.io/v1.16/software/install/

Would it be possible for you to try this scenario again with a newer version of Crossplane? 🙇♂ https://docs.crossplane.io/v1.16/software/install/

If this is a version bump away, I'm more than happy to try it!

Yup, on v1.16 it works. I feel ashamed for not trying this before opening an issue. Thanks for your time @jbw976!

Thank you very much for the initiative to report an issue you saw and the follow-up to try out the new version. That's really appreciated @gusfcarvalho! 🙇♂ 🙌


swift4

update project to swift 4

I would love this project on swift 4, thank you @ykyouhei if you do this :)

i did it actually


Add forcing variables to cache

Purpose
Adds forcing variables to cache
To-do

Content

[ ] I have read and checked the items on the review checklist.

closing in favor of simpler PR #436


Changing a username while keeping the email unchanged leads to 409 conflict

Current Behavior

Create a realm.yaml that contains a user with a name and an email address
Run keycloak-config-cli to apply the realm.yaml
Change the realm.yaml so that the user's email stays the same but the username is changed
Rerun keycloak-config-cli --> error, 409 Conflict

Expected Behavior
A new user with the new name should be created, the old user should disappear
Steps To Reproduce
No response
Environment

Keycloak Version: 16.0.1
keycloak-config-cli Version: latest
Java Version: 11

Anything else?
No response

Deleting users is currently not implemented in keycloak-config-cli, only create and update.
Thats why keycloak-config-cli will not delete the old user and the new user has a conflict with the existing user.

Is there any plan to add the remote state feature?

Hi @testuser7 (what a name ;-) ), I haven't looked into it so far!

Hi @testuser7
this also closes ticket https://github.com/adorsys/keycloak-config-cli/issues/810 since the username needs to be uniquely identified,
also setting the --import-remote-state.enable="true" should also be given a trial to see if the issue persist.

After testing, I observed that Keycloak uses the username as the unique identifier for users. This causes the following behavior:

Changing only the username during an import results in a 409 Conflict.
Changing the username along with other attributes creates a new user without deleting the old one because purging users isn’t supported
by keycloak-config-cli.

Recommendation:

Consider enabling Edit Username in the realm settings.
Explore alternative identifiers like email for user matching during imports.

This ticket is similar to ticket #810.
Reference to it for more information


RFE: Remove tokens/keys in log output

The logs should not contain authentication tokens or keys. For example:
kubewise-64db798b7f-m9chj:kubewise 2020/03/25 17:17:02 Error making request to Google Hangouts Chat Post "https://chat.googleapis.com/v1/spaces/xxxxxxxx/messages?key=(CENSORED)&token=(CENSORED)": dial tcp <IP_ADDRESS>:443: connect: connection refused

@TJM I just merged some code to take any tokens out of the logs. I also audited all the other points in the code where logging occurs to ensure this isn't a risk going forward. I'm about to release a new version with this change in it. Will let you know when that is live.

Thanks!

Fixed in version 0.6.2.
helm repo update
helm install kubewise larder/kubewise --version 0.6.2 --blah blah


New SScript version breaks scripts

Describe your bug here.
If you don't specify all parameters inside of a callback function, you will get a "Too Many Arguments" error, which didn't use to be a thing in previous SScript versions
Eg. This line of code would've worked on 0.7.X versions, but now it doesn't work anymore

Even when I do that, sometimes it doesn't work again, because flValue1 and flValue2 can be null

Command Prompt/Terminal logs (if existing)
No response
Are you modding a build from source or with Lua?
Lua
What is your build target?
Windows
Did you edit anything in this build? If so, mention or summarize your changes.
Using 1.0b

(Also the game experiences random freezes, which didn't happen in previous versions before)

(Also the game experiences random freezes, which didn't happen in previous versions before)

Potentially shader related


common.sh: Add hosts entry for jail (ref or builder)

To allow some java programs to build, add a stub hosts entry with the jail name pointing to <IP_ADDRESS>.
This fixes problem building archivers/snappy-java (at least for me).

hum can you explicit what issue you are exactly facing with those java programs? note that at quick glance the code cannot ne merged as is, as it will not fit with setup without ipv4

Yes, also ::1 is needed. I did not realize it.
The problem was that when building some packages using sbt, it tries to resolve the local host's hostname and if it can not, the build fails.

sbt -Dsbt.ivy.home=/wrkdirs/usr/ports/archivers/snappy-java/work/repository -Dsbt.offline=true -Dsbt.boot.directory=/wrkdirs/usr/ports/archivers/snapp>
copying runtime jar...
2023-08-18 20:16:45,179 main ERROR Could not determine local host name java.net.UnknownHostException: 132rx64-default-powen-job-01: 132rx64-default-po>
        at java.base/java.net.InetAddress.getLocalHost(InetAddress.java:1670)
        at org.apache.logging.log4j.core.util.NetUtils.getLocalHostname(NetUtils.java:53)
        at org.apache.logging.log4j.core.LoggerContext.setConfiguration(LoggerContext.java:541)
        at org.apache.logging.log4j.core.LoggerContext.start(LoggerContext.java:263)
        at org.apache.logging.log4j.core.async.AsyncLoggerContext.start(AsyncLoggerContext.java:87)
        at org.apache.logging.log4j.core.impl.Log4jContextFactory.getContext(Log4jContextFactory.java:207)
        at org.apache.logging.log4j.core.config.Configurator.initialize(Configurator.java:220)
        at org.apache.logging.log4j.core.config.Configurator.initialize(Configurator.java:197)
        at sbt.util.LogExchange.init(LogExchange.scala:142)
        at sbt.util.LogExchange.context$lzycompute(LogExchange.scala:18)
        at sbt.util.LogExchange.context(LogExchange.scala:18)

And this only occurs with OpenJDK17 and newer, not with OpenJDK11 and older.

ok, can you update accordingly and squash this PR?


added Bat, GiantBat, and Spider

Hi, looks good, but please remove your .project, .cproject and data.txt files


Support GRPC load balancing with SRV records

Hi,
I'm looking to set up some instances of clangd remote servers and have a load balancer arbitrate between them.
There's an example of a server-side set up for load balancing over at https://github.com/clangd/llvm-remote-index.
In my case it would be simpler if I could use the SRV mechanism optionally configurable in GRPC, per https://github.com/grpc/proposal/blob/master/A5-grpclb-in-dns.md.
This implies a minimal change in the way GRPC channels are configured in clangd, to enable GRPC_ARG_DNS_ENABLE_SRV_QUERIES. In that mode, it performs an initial _grpclb._tcp srv query to get a list of servers and runs in load balancer mode between them.
Presumably this should not break existing clients because it didn't work so there was no reason to set up dns that way.
Would you be open to upstream a change that enables this mode for the clangd remote client and monitor?

Ah, I see grpclb is considered deprecated now, in favor of xDS (Evolution of gRPCLB).
The SRV functionality is only used when the load balancing policy is set to grpclb, so it doesn't seem worthwhile to support it in clangd.
Thanks for your prompt response.


[Wallet] Use known names on CELO feed

Description
We added a short while back a mechanism to show names and pictures for known addresses on the main transaction feed. We are now reusing that on the CELO transaction feed.
Tested
Locally
Related issues

Fixes #6378

Hi @gnardini We have verified this task on Testflight build 1.8.0 & Android internal build 1.8.0 and observe the following scenarios.

User is able to see the contact user name on Activity section if user send the USD to Contact user.
User is able to see the 'Withdrawal to [User profile name] on celo activity section when user withdraw celo to Contact user.

Can you please ley us know if we need to test anything else in this task.

Hi @gnardini We have verified this task on Testflight build 1.8.0 & Android internal build 1.8.0 and observe the following scenarios.

User is able to see the contact user name on Activity section if user send the USD to Contact user.
User is able to see the 'Withdrawal to [User profile name] on celo activity section when user withdraw celo to Contact user.

Can you please ley us know if we need to test anything else in this task.


2.0 - Offset calculation for tablets

In responsive.less, when calculating the offset for a tablet column (line 163), the following code is used:
.offset(@columnOffset: 1) {
    margin-left: (@gridColumnWidth * @columnOffset) + (@gridGutterWidth * (@columnOffset - 1)) + @gridGutterWidth;
}

However, for desktop layouts, this calculation is used (line 115):
.offset(@columns: 1) {
  margin-left: (@gridColumnWidth * @columns) + (@gridGutterWidth * (@columns - 1)) + (@gridGutterWidth * 2);
}

The difference is that in the tablet layout, it appears to be missing the inclusion of an @gridGutterWidth. The result for me on a tablet (iPad) is that a row with a column of class "offset2", will not properly line up with a column jn a preceding row that is beside a "span2" column.
ex:

This is offset2

This is span2

This is span8

In the above example, the content of "offset2" is not lined up with the content of "span8" when viewed on an iPad. It is properly aligned on the desktop.
Thank you.

Resolved! Thanks, guys,


Update jcl-over-slf4j to 2.0.11

About this PR
📦 Updates org.slf4j:jcl-over-slf4j from 1.7.36 to 2.0.11 ⚠
Usage
✅ Please merge!
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 = "org.slf4j", artifactId = "jcl-over-slf4j" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "org.slf4j", artifactId = "jcl-over-slf4j" }
}]

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

we should not update  from 1.7.36 to 2.0.11 (log4cats is on 1.7.x)


empty type is treated as any

Flow version: 0.125.1
Expected behavior
empty to behave like mixed (does not cast to anything only refinements are allowed)
Actual behavior
empty is basically alias to any
code
declare var nothing: empty
declare var something: 'cotne'

declare function giveMeNumber(number): void

giveMeNumber(1)// ok
giveMeNumber('cotne')// error as expected

giveMeNumber(nothing)// should error

if (something !== 'cotne') {
  giveMeNumber(something)// should error
}

Try

In this case empty is behaving as designed, that is to say, the exact opposite way as mixed. In Flow, mixed is the top type, the supertype of all other types. This means you cannot assume anything about its contents, but can create it from any value. For example, all of the following are legal: let x : mixed = 3, let x : mixed = {} and let x : mixed = () => {}, while all of the following are errors (assuming x has type mixed): x.foo, x() and x = x + 1. Put another way, you can write anything to a mixed value, but cannot read anything from it.
empty has the opposite behavior: it is the bottom type in Flow, the subtype of all other types. It is impossible to create, but if you obtain a value of type empty, you can do anything with it. So to contrast with the examples above, all of the following are errors: let x : empty = 3, let x : empty = {} and let x : empty = () => {}, while all of the following (assuming x has type empty) are legal: x.foo, x() and x = x + 1. Reading and writing empty are dual to mixed, you can read anything from an empty value, but cannot write anything to it.
In the example above, you can call giveMeNumber inside that refinement because Flow knows that the if statement will never succeed, so the code inside is dead; dead code is one of the only sources of empty in Flow. As such, the above code won't error because that function won't even get called.
As an aside, the reason any is an unsafe type is because it combines the permissibility of writing to mixed and reading from empty: you can put anything into an any value, and do anything you want with it.


[Doc] Fix typo for wrong reference

Thanks for your contribution and we appreciate it a lot. The following instructions would make your pull request more healthy and more easily get feedback. If you do not understand some items, don't worry, just make the pull request and seek help from maintainers.
Motivation
Fix the wrong reference name in tutorial of both languages (En & Zh)
Modification
Change the reference link to correct one (the one existing in the site), not the ancient one:

BC-breaking (Optional)
Does the modification introduce changes that break the backward compatibility of the downstream repositories?
If so, please describe how it breaks the compatibility and how the downstream projects should modify their code to keep compatibility with this PR.
Use cases (Optional)
If this PR introduces a new feature, it is better to list some use cases here and update the documentation.
Checklist
Before PR:

[ ] Pre-commit or other linting tools are used to fix the potential lint issues.
[ ] Bug fixes are fully covered by unit tests, the case that causes the bug should be added in the unit tests.
[ ] The modification is covered by complete unit tests. If not, please add more unit test to ensure the correctness.
[x] The documentation has been modified accordingly, like docstring or example tutorials.

After PR:

[ ] If the modification has potential influence on downstream or other related projects, this PR should be tested with those projects, like MMDet or MMSeg.
[x] CLA has been signed and all committers have signed the CLA in this PR.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

Hi @Crescent-Saturn ！First of all, we want to express our gratitude for your significant PR in the MMCls project. Your contribution is highly appreciated, and we are grateful for your efforts in helping improve this open-source project during your personal time. We believe that many developers will benefit from your PR.
We would also like to invite you to join our Special Interest Group (SIG) private channel on Discord, where you can share your experiences, ideas, and build connections with like-minded peers. To join the SIG channel, simply message moderator— OpenMMLab on Discord or briefly share your open-source contributions in the #introductions channel and we will assist you. Look forward to seeing you there! Join us ：https://discord.gg/UjgXkPWNqA
If you have WeChat account，welcome to join our community on WeChat. You can add our assistant ：openmmlabwx. Please add "mmsig + Github ID" as a remark when adding friends：）
Thank you again for your contribution❤


package-task: Handle centos-stream-8-aarch64 yum target properly

Otherwise, the current implementation will handle wrongly for
centos-stream-8-aarch64 target case:
docker build --tag custom-fluentd-centos-stream-8-aarch64 --build-arg \
DEBUG=yes --build-arg FROM=arm64v8/centos:8 centos-stream

This can cause the following error:
docker build --tag custom-fluentd-centos-stream-8-aarch64 --build-arg DEBUG=yes --build-arg FROM=arm64v8/centos:8 centos-stream
unable to prepare context: path "centos-stream" not found
rake aborted!
Command failed with status (1): [docker build --tag calyptia-fluentd-centos...]
/media/Data2/Gitrepo/custom-fluentd-builder/lib/package-task.rb:148:in `run_docker'
/media/Data2/Gitrepo/custom-fluentd-builder/lib/package-task.rb:346:in `block (2 levels) in yum_build'
/media/Data2/Gitrepo/custom-fluentd-builder/lib/package-task.rb:342:in `each'
/media/Data2/Gitrepo/custom-fluentd-builder/lib/package-task.rb:342:in `block in yum_build'
/media/Data2/Gitrepo/custom-fluentd-builder/lib/package-task.rb:341:in `yum_build'
/media/Data2/Gitrepo/custom-fluentd-builder/lib/package-task.rb:373:in `block (2 levels) in define_yum_task'
Tasks: TOP => yum:build
(See full trace by running task with --trace)
rake aborted!
Command failed with status (1): [/home/cosmo/.rbenv/versions/2.6.3/bin/ruby...]
/media/Data2/Gitrepo/custom-fluentd-builder/Rakefile:36:in `block (3 levels) in define_bulked_task'
/media/Data2/Gitrepo/custom-fluentd-builder/Rakefile:35:in `block (2 levels) in define_bulked_task'
/media/Data2/Gitrepo/custom-fluentd-builder/Rakefile:34:in `each'
/media/Data2/Gitrepo/custom-fluentd-builder/Rakefile:34:in `block in define_bulked_task'
Tasks: TOP => yum:build
(See full trace by running task with --trace)

I found it during custom fluentd packaging tasks.
CentOS Stream 8 AArch64 is one of the special case.
Signed-off-by: Hiroshi Hatake<EMAIL_ADDRESS>

It should be more generalized but not bad for the first step.

Thanks!


[hip] driver tests status

Since we don't have CI for the HIP runtime, I am posting here the test status.

We have tests for HIP now. Closing this stale issue.


profiles-wishlist

Hello @BjarneStroustrup
First of all, thank you for your groundbreaking contributions to the development of the C++ programming language. It is truly appreciated. Based on your talk, I assume that in the future, we will have something similar to Rust with the Clippy feature for C++, but this time, these profiles will have specific target use cases in various fields of the industry. So to answer your questions:

Set of profiles – what profiles do we need? which should be part of an initial set? Which should be standardized? Which should be defined as unions of other profiles?

My proposal is
1 - CppCore:  This profile checks for adherence to the C++ Core Guidelines.
2 - Deprecated: This profile prevents the use of deprecated code and libraries.
4- Style: This profile checks for naming conventions and code style guidelines based on clang-format (e.g Google, LLVM and etc.)
4- Memory: This profile checks for:

Memory usage analysis
Compile-time allocation and deallocation tracking
Compile time Tracing object reference chains
Compile-time and run-time memory leak detection
Memory usage patterns

5- Embedded: Based on the Memory profile, this profile is customized for resource-constrained embedded systems (e.g., NO_STD_LIB).
6- Performance: this profile is tuned for performance and fearless parallelism.
7- Realtime: Based on Performance profile, this profile tuned for real time applications that require high computing capabilities from both the CPU and GPU.
8- Safety-Critical: Based on the Embedded and Realtime profiles, this profile is optimized for critical systems.

How do we specify a profile? As a set of guarantees; not, simply as a set of detailed rules. We need examples of profiles: both the set of guarantees and an initial set of detailed rules for delivering those guarantees.

We should start by establishing a set of guarantees and then provide specific details for each category. The initial set may encompass, but is not limited to, three key areas: Performance, Safety and Behavioral. Then ask what type of behavioral, safety or performance this profile aims to achieve.  (e.g sometimes, we use unsafe code for performance, and other times, we need to add many verification and assembly codes to keep things safe).

The Core Guidelines has been our initial proving ground for rules for good (and often safe C++ code). We need more rules and rules taking advantage of C++20 and C++23. Individual suggestions can be made directly on the CG GitHub, but larger sets of suggestions and suggestions directly related to profiles belong here.

Agreed, I'm pretty sure C++20 Concepts is a valuable asset!

Comments/analysis on how various compilers could accommodate profiles.

The biggest problem we currently face is the divergence of compiler strategies. Each one has taken a different approach for memory safety. In my opinion, the only way to overcome this situation is to bring the static analysis, Lifetime annotations for C++, Microsoft GSL and others as the part of the language itself.

Comments/analysis on how various static analyzers could accommodate profiles.

We encounter a similar issue in the field of static analysis. For instance, we have several static analyzers, but the majority of them are not cross-platform. The Clang Static Analyzer represents our best chance.

Names of individuals and groups working on profiles and similar projects.

I would love to collaborate in this endeavor, but apart from the ISO members I don't know of any individuals or groups at the moment.

I suggest all the community to focus on memory safe profile as the high priority works!
I think everybody knows how many circles and institutions are pressing for this feature and even suggestion changing the programming languages to memory safety ones. So I think this should the top priority. After that the community can get whatever they want without hurry.

I wrote a note about how to start for the standards committee. It will become complete and available in a couple of weeks. It points to memory safety, and the need to be precise about how we use that term.

[PooyaEimandar]: I'm working on creating a framework for collaboration.

So a profile is just a static analyzer check, like clang-tidy modules? I'm a little confused by the whole concept. I'm no expert by a long shot and respect him greatly, but I feel like Bjarne just throws this term into the room and expects everyone to know what he's talking about. Or maybe I didn't catch the part where he explains it in more detail.
I watched the talk "Delivering Safe C++ - Bjarne Stroustrup - CppCon 2023" and I feel like whatever can be done with static analysis and potentially more language features such as annotiations and library features, such as gsl::not_null (should be part of the STL, IMO), doesn't require inventing a new thing.
As for memory safety, simply flagging every naked new or delete should get rid of 90% of the problems. Range constraints are already flagged by things such as modernize-avoid-c-arrays, suggesting std::array instead. Indexing pointers is already flagged by cppcoreguidelines-pro-bounds-constant-array-index or cppcoreguidelines-pro-bounds-pointer-arithmetic.
So what is this whole profile thing about? You can never make a language 100% safe, any language, at least not a general one that can solve any problem.
Is this what profiles are about? Constructing an area of code that is guaranteed to be safe, and then allowing and explicitly flagging unsafe code in areas specially created for dangerous things, like rust does?

The item 8 above is particularly important to address for safety critical industries. Without a MISRA-like concept in C++ profiles, it will be difficult to gain broader adoption in these areas of criticality. This has been discussed by others at various conferences including cppcon, but I wanted to call it out as an important area for embedded, auto, aviation, industrial, and robotics.


feat(eip4844): include TxEip4844 in the primitive Transaction enum

Should solve #4073.

@Rjected Should be fixed, tell me if there are other stuffs or if ready to merge :)


Get Credentials from jenkins and set to AWS device farm

Description
LEARNER-7951

Get credentials from Jenkins
Send these credentials as environment variables to the AWS device farm

@farhan-arshad-dev  or @jawad-khan can anyone of you plz this PR.?


Optimism Grant 2: Attestations

Original proposal: https://app.charmverse.io/op-grants/page-31849314357430236
These are the key components of the project:

An attestation-based architecture and data model for DAO membership, member contributions, and other data (a.k.a., Attestation Standard V2)

A web platform for attestations and contributions: This platform will be capable of displaying DAOIP-3 attestations and contributions for any given Ethereum address.

Accompanying Infrastructure: This infrastructure will allow a client to deploy a new platform instance for a given Ethereum RPC-compatible network.

But the critical milestones of the project are:

Deploying the attestation schema v2 on OP Goerli/ OP mainnet using the Ethereum Attestation Service (Timeline: Q4 2023)
Attestations using the schema deployed in (1) (Timeline: Q4 2023)

Ideally, we want to complete all things promised under the key components by Q4 2023 and also try to get some adoption for it.

Call arranged for everyone here next week to go over this + make plans for the Optimism Attestations project.

We need to schedule a new call with @frm present! @frm when are you available next week / later this week?

Pinged @frm today.

Noting that Mendes is not going to be available for the next couple of weeks.

REMINDER, updated attestations standard needs to be out by end of September.

@amanwithwings We may help on one of the tasks "A web platform for attestations and contributions: This platform will be capable of displaying DAOIP-3 attestations and contributions for any given Ethereum address.", since we plan to do one for EAS as well, we plan to consolidate them and push the forward of the attestation standards. Cc@thelastjosh
We can connect next week on more details. @amanwithwings

@xiaohou77 , sounds good!

Josh is taking lead on this and we plan to have a meeting around or after the 10th of September to update on status

Josh proposed a time to meet around 10th Sept, might need to shift that slightly (sometime week of Sep 11). Need to publish V2 of attestation standard - we should be able to do that ourselves, no real blockers.
Next step: meet next week, at latest by early week of Sept 18th.
LXDAO is helping OPT build an attestation front end and list public schemas. Make existing schemas more discoverable for devs in OPT ecosystem. Second point of this issue aligns with some of LXDAO's work so might have room to collab there. DAOstar+LXDAO can explore applying for a future builders grant together.

Meeting getting scheduled for ~25th of Sep

Latest: we need to define a proper team to work on this, e.g. with Aman as PM, Rashmi + LXDAO, ideally Mendes if he's available.
Aman and I also discussed the need to have additional conversations with ecosystem actors to evaluate the need and place for the attestations standard, since this entire thing, including all the infra we are thinking of building, is really intended to support adoption of the standard, but many of the people who put effort into building in the initial standard are gone now (Avenue, Govrn, etc.). We should talk to people like Disco, DeWork, etc. to evaluate whether this standard is still useful to them. We should also talk to EAS to catch up.
We talked organizing the project management a bit more with a doc or some other tracking mechanism. For now let's just keep using this GitHub issue. Maybe Aman can just update the first post with necessary information as things evolve.
Key docs that Aman and I reviewed today
Updating the DAOIP-3 standard issue: https://github.com/metagov/daostar/discussions/39
Optimism issue: https://github.com/metagov/daostar/issues/100
PR for WIP update of v2, needs to be reviewed and merged this week: https://github.com/metagov/daostar/pull/95

Update: Milestone 1 has been completed successfully. Update added on Charmverse.

I am proposing the attestaion standard framework as below:

The key is we can set the standard to conforming EAS's format, and it can be easily adopted by devs/apps. From DAO* standpoint, we can maintain the API endpoint for non-EAS use case if we want, and we don't need to maintain any API endpoint for EAS use case.

For DAO URIs, since they are already stored in contract/IPFS thru DAO* registration contract, we don't have to store them on EAS again, at least, the value using EAS in this case is not clear and big.

In today's we reviewed part of the EAS flow and agreed it makes sense to support the integration, especially for DAOIP-3 attestations. We did not review the other uses of EAS yet (e.g. to support easier adoption of daoURI).

Asked Gonna, from the OP Builders Grant committee on how grant milestones should be updated. Their reply:
"We are working on a solution for this. Builders are subject to 1 year lock and therefore milestone reports can be done by the end of the 1 year period. If you still want to give a date-by-date update you can do it in the forum here:
https://gov.optimism.io/c/updates-and-announcements/grant-updates/56
Please use tags: "Season 4", "Builders ", "Milestones".
If you do it, please add your Charmverse proposal link."
For the time being, I am choosing to not create an additional forum post on Optimism. For now, all updates, including milestone completion details, will be periodically added to Charmverse.

Discussion today with Evin + Carl at Disco. Suggestions for update to the standard: attestationsURI -> evidence, and changing type+id to id: {type, address}.

I think we should implement DAO URI using EAS and Not the EIP 4824, it makes more sense to me
At the end of the day  DAO URI and it contents that is Attested is more relevant and more trust worthy than the DAO URI created by a registration form from our frontend. Because anyone can create a DAO URI from the reistration form, its not signed/attested
A DAO URI created with EAS attestation either onchain/offchain, someone attests it, from a wallet address/ens name/DAO address
and then they make an EIP-4824 registration contract summoner with an onchain transaction from their DAO
I believe this would make the standard more credible and also make creating the DAO URI more "decentralized" (right now, we are the only one hosting the registration form to create the DAO URI)
Next steps would be to modify the contract to listen to the DAO URI attestations and just display it on our frontend. We would NOT need our Subgraphs, nor the DAO URI API infrastucture
But we would need to implement the Framework customization ( Snapshot, DAODAO, custom, moloch, safe etc)  with an EAS attestation.
We could do this easily by  having a field on DAO URI for framework and a resolver contract which generates the Framework URI links for say Snapshot or any other framework
We need to think about "incentivising" the DAO Framework URI to be maintained by the framework maintainers themselves as it would be more in sync with any changes/updates a framework makes

Note that EAS doesn't exist on all chains.
Also, what's the difference in terms of trustworthiness between a DAO
deploying a registration contract by signing an on-chain transaction, and
them signing a EAS attestation?
You may be talking about the first part, where we first deploy a daoURI
JSON which must be "claimed" by a DAO's on-chain transaction. In which case
a signed attestation is probably more trustworthy, in some sense, than just
going through our interface.
It may, eventually, make sense for our interface to just call EAS
underneath the hood, at least for chains where EAS exists. Or, at least, to
provide that option.
Before we go through any comparisons, I would just build the EAS option and
test it, because we need to anyway.
On Mon, Nov 6, 2023 at 6:45 PM Rashmi V Abbigeri @.***>
wrote:

I think we should implement DAO URI using EAS and Not the EIP 4824, it
makes more sense to me
At the end of the day DAO URI and it contents that is Attested is more
relevant and more trust worthy than the DAO URI created by a registration
form from our frontend. Because anyone can create a DAO URI from the
reistration form, its not signed/attested
A DAO URI created with EAS attestation either onchain/offchain, someone
attests it, from a wallet address/ens name/DAO address
and then they make an EIP-4824 registration contract summoner with an
onchain transaction from their DAO
I believe this would make the standard more credible and also make
creating the DAO URI more "decentralized" (right now, we are the only one
hosting the registration form to create the DAO URI)
Next steps would be to modify the contract to listen to the DAO URI
attestations and just display it on our frontend. We would NOT need our
Subgraphs, nor the DAO URI API infrastucture
But we would need to implement the Framework customization ( Snapshot,
DAODAO, custom, moloch, safe etc) with an EAS attestation.
We could do this easily by having a field on DAO URI for framework and a
resolver contract which generates the Framework URI links for say Snapshot
or any other framework
We need to think about "incentivising" the DAO Framework URI to be
maintained by the framework maintainers themselves as it would be more in
sync with any changes/updates a framework makes
—
Reply to this email directly, view it on GitHub
https://github.com/metagov/daostar/issues/100#issuecomment-1797041885,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACHA5PF4DBQO3GHUEWBS2P3YDFZBBAVCNFSM6AAAAAA2SRCPLOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTOOJXGA2DCOBYGU
.
You are receiving this because you commented.Message ID:
@.***>

--
http://www.joshuatan.com/research/

Moving issue #179 here.
We (potentially) have Karma, Fairsharing, and Disco adopting DAOIP-3 and we need to make sure we have that indexing working. This was previously worked on for ONTOCHAIN.
From Josh:
_"From today: when we submit an attestation, it does work, but the API server that was pulling the attestations was hosted by Mendes, and that server is not returning anything, and Rashmi has no way to debug it. On the backend server though, the flow for submitting reputation attestations does currently work.
Do we need the front end? YES. The 3rd and final milestone of https://github.com/metagov/daostar/issues/100 requires having a frontend.
Next step: copy the current frontend, deploy a DAOIP-3 compliant schema(s), and add the ability to display EAS attestations. That should satisfy the milestone for https://github.com/metagov/daostar/issues/100."_

Present schemas:

Karma: https://docs.google.com/document/d/1jSAZV8mnjdyYFtH5XH6aRN9hVIbY5hdyHCdZIYlDqS4/edit#heading=h.67m9i8ttvdpu

Disco: https://github.com/discoxyz/disco-schemas/tree/main/json

Fairsharing: https://optimism.easscan.org/schema/view/0xc012dddde021c7258ff4671b1be08fe6b3b51d98bd0a89b43d020fafde24b476

Next step: suggestions to convert all 3 to being DAOIP-3 compliant.

Just will finish reviewing Aman's DAOIP proposal for EAS support ASAP

@thelastjosh, @Rashmi-278, this seems like a nice design for the attestation standard (explorer) front-end: https://tokenlists.org/
Once our schema is final, live on EAS, and projects adopt it, the front-end could display the schemas of all DAO attestations. It could look something like this:

Noting that there is an ecosystem project idea aligned with this: https://github.com/orgs/ethereum-optimism/projects/31/views/4?filterQuery=attestation+list&pane=issue&itemId=27292601
What are your thoughts? @Rashmi-278 Rashmi, how much heavy lifting does this entail?

Let's do it; @amanwithwings could you create a new issue and add it to Milestone 2.1 Attestations?

Tiny clap for @Rashmi-278 for the great technical implementation 👏  some additional BD work remains. Progress mostly tracked in #226 .

Closing this one! Great job everyone!


open a modal previewing the available filters

Fixed by https://github.com/zakodium-oss/pixelium/commit/378dc699e9276baf66730321dcbd39a03806de62


Reaping Fire: "The Walking Dead"

The fangriders enemies are still moving, even when they are already dead. This doesn't happen to everyone, only to those who were left with 0 health.

Fangriders must not have their friction set properly (or something like this), so their death velocity when they hit the ground doesn't bring them to a halt. @Zerrien wanna check this out?

Looks like the Fangrider and Griffin Rider both didn't have any rolling resistance. Bumped it up a tad and they now stop after a bit of a slide.
Let me know if you see anything strange from this change!


Apply early tx verification for p2p messages

Change summary:

Apply early tx verification for p2p messages
Use ENABLE_EARLY_TX_SIG_VERIF node param

Related issues:

https://github.com/ainblockchain/ain-blockchain/issues/1012

Thanks for the review, now merging.. @liayoo


"Publica toate joburile" button didn't work

ENVIRONMENT
URL: https://admin.peviitor.ro/
Browser: Chrome
Devices: PC, Iphone
OS: Windows 10, IOS
STEPS TO REPRODUCE
Open the URL in the browser
Write in the search field "Blackline"
Click on "Vizualizeaza joburi"
Go on production website
Delete from validator all the jobs that were published by pressing the button "sterge joburile din productie"
Verify on production if they were deleted.
Go on validator and published again all the jobs by pressing the button "Publica toate joburile"
Verify on the production if all the jobs were published.
EXPECTED RESULTS
All the jobs from validator were published on production.
ACTUAL RESULTS
The button didn't work and no job was published on production.
https://github.com/peviitor-ro/validator-ui/assets/129604131/3a753870-c339-4037-8f5e-3dbfcdfc73d4

yes i know :))


Document the release process and update the "release-it" options

Added a RELEASE_PROCESS.md file based on:

the BigchainDB Server release process
the oceanprotocol/commons release process

Updated the command-line options passed to release-it based on the same options in oceanprotol/commons, i.e. in package.json

I hope the process is mostly correct. I wasn't able to test it. Please take a look to make sure it makes sense. Once someone uses it, they might find something that should be changed or clarified.

Codecov Report

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

@@           Coverage Diff           @@
##           master     #293   +/-   ##
=======================================
  Coverage   95.14%   95.14%
=======================================
  Files          12       12
  Lines         309      309
=======================================
  Hits          294      294
  Misses         15       15

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 ba81d1b...4ea0c19. Read the comment docs.

I realized I forgot to include the signed-off-by line in the Git commit messages, so I will see if I can fix those.

I had to do a force-push of the revised commits, but it looks like it worked. Disaster averted!

Perfect. Will review asap I do have a minute
On Thu, 23 May 2019, 09:23 Troy McConaghy<EMAIL_ADDRESS>wrote:

I had to do a force-push of the revised commits, but it looks like it
worked. Disaster averted!
—
You are receiving this because your review was requested.
Reply to this email directly, view it on GitHub
https://github.com/bigchaindb/js-bigchaindb-driver/pull/293?email_source=notifications&email_token=AAM76SF4NWKM6PLYXS4OIFDPWZA5JA5CNFSM4HOUAL4KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODWBJ3WA#issuecomment-495099352,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAM76SFWHV7AXQZQHPWSPZDPWZA5JANCNFSM4HOUAL4A
.

release-it latest version is now 12.4.1 but everything should work as well with 12.2.0.
Since a lot of packages needs to be updated this can be done in another PR, therefore I will approve it.


Random ) and . under "Next steps"

From the documentation:

Next steps
Azure Key Vault security: Identity and access management
Provide Key Vault authentication with an access control policy
Secure your key vault).
Azure Key Vault developer's guide
Review Azure Key Vault best practices

What's up with the ")." after "Secure your key vault"? :P

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

ID: aa0c5bd2-62b8-f0ba-b569-d54fe97c8a68
Version Independent ID: 95da0c67-d4bd-5e33-d1cf-c6ce9a4ff2f5
Content: Use an system-assigned managed identity to access Azure Key Vault
Content Source: articles/key-vault/general/managed-identity.md
Service: key-vault
Sub-service: general
GitHub Login: @msmbaldwin
Microsoft Alias: mbaldwin

@Bosch-Eli-Black Thank you for your catching this. We agree its a typo and we will have this fixed.
Thank you.


Logarithmic scale when plotting results

Hi!
I was wondering if there was such a feature in criterion, and if not how would I go about implementing it in the library?

I don't know the answer to this question off the top of my hand. That being said, the plotting functionality in this criterion makes use of the flot JavaScript library, so if flot supports logarithmic scales, there may be a way to incorporate that functionality into criterion as well.

Thanks for the tip, @Lythenas. A next step will be figuring out what kind of interface we should offer for tweaking the axes' scales in the HTML report itself. One option is to accept extra command-line arguments for configuring this. Alternatively, we could try offering this UI in the report itself, although that would be much more work to implement.

I not sure what the best approach is. I think a general interface to write custom report exporters would be the easiest way to expand criterion. But I would keep the default exporter as is (by default) because for basic benchmarks it is fine IMO.
I wouldn't make this configurable by command line because it will likely get very complicated very fast. Maybe a list of presets would be ok as command line arguments.
I'm thinking criterion could offer something like this:
class ReportExporter where
  formatReport :: [Report] -> Text

(and maybe helpers to extend the default flot template)
And I could write my own exporter that generates HTML or custom JSON or whatever I want.
FYI: hvega looks like it has a nice DSL to generate data for Vega-Lite (which is an alternative to flot). Maybe we could build something similar for flot or replace flot with vega lite (maybe in an alternative exporter).

There should be a simple heuristic to choose between a linear scale or a log scale when the bar plot would otherwise be useless, which is most of the time in my experience

i think log scale should probably be the default ... maybe wiht the base "ofset" at the low end at pico sends?   or we shift to box and whisker plots?  on log scale https://en.wikipedia.org/wiki/Box_plot
maybe @hasufel or @bodigrim have thoughts? (theres also the issue that default rendering js last i looked doesn't just consume summary statistics, but rather all the points, last i looked? or some other insane algorithmic issue )

There should be a simple heuristic to choose between a linear scale or a log scale when the bar plot would otherwise be useless, which is most of the time in my experience

What kind of heuristic could it be? I cannot think of anything simple and one-size-fits-all.

i think log scale should probably be the default

Use cases for benchmarking are quite diverse. Like, if we benchmark different implementations of an algorithm, then log-scale usually looks very sensible, because it nicely captures differences in asymptotical growth without making plot unreadable. But if I benchmark the very same function on different inputs, I would definitely prefer a normal scale.

or we shift to box and whisker plots?

Absolutely, it would be nice to have a box-and-whisker plot. But altogether it looks to me that this is not a job for criterion. There are many ways to transform a statistical data, far more than it is sensible to configure from criterion's command line.
I remember that criterion can dump results as JSON. Isn't it enough? External tools are free to analyse and visualise it in any imaginable way.

I think the linear scale should be the default, I think it's kind of a general assumption regarding any plot

I respectfully 100% disagree and I am more than happy to have an educational resource collectiong/back and forth email/whatever with both of you to make this case.
I realize that people dont see log scale plots till relatively late in  their educations, but for the way people use criterion: namely to compare different algorithms, we care about the multiplicative difference between two algorithms on the same input (2x or 10x or whatever speed difference). Default linear scales makes the emphasis on whatever algorithm is slowest. and complicate actually visually seeing multiplicative difference in perf.
(who using criterion hasn't commented out the slowest algorithm on their machine so the visual scale "focuses" on the actual contenders?). I'm more than happy to also provide clear opinion references from statistics/applied statistics/public health where correct interpretable data plotting is part of the core decision making  loop.
I'm wiling to be convinced i'm wrong, but I ask that you give me the opportunity to convince you and address whatever grounded reasons you have in mind.

(also i'm interested in making this happen :) )

but for the way people use criterion: namely to compare different algorithms, we care about the multiplicative difference between two algorithms on the same input (2x or 10x or whatever speed difference).

If we use criterion to compare different algorithms, then yes. My argument is that this is not always the case. For instance, I often test the same function on different sizes of input (like, [100,110..200]), for which I would very much prefer a normal scale.

who using criterion hasn't commented out the slowest algorithm on their machine so the visual scale "focuses" on the actual contenders?

:D Nice!
I totally agree that having an option to switch to log-scale would be awesome. I would not make it a default however.
Maybe we can have embed a switch directly into HTML page? So that users can change between normal and log scales without rerunning benchmarks? It should not be that difficult; I am happy to revive my webdev skills if we choose this avenue.

thats an even better idea! (on page switch/toggle). In that case for log scale probably should have it start a "picoseconds" so there some margin things start with ? idk
(also last i checked years ago) : I do think that the default html template has(?) some algorithm issues (either DOM related or because the raw data set is dumped into the page instead of just order statistics + mean + variance + min + max).
@Bodigrim you, as usual, make great points!

The ability to toggle between linear and log scales via a switch on the HTML page itself sounds like a promising way forward. This avoids one of the problems that a command-line–only switch would have, since it would allow toggling the scales on a per-chart basis.

I have a (horribly hacked together) proof of concept for switching between linear and log axes by clicking the x axis. Recent versions of flot support log axes nicely, but the version in js-flot on hackage and stackage doesn't, is 7 years old, and not very forwards compatible. I'd be happy to clean this up, but the issue is mostly figuring out what we want to depend on. What do?

Please upgrAde us to a better reality ! The universe will thank you.

Thanks for picking this up, @jonascarpay! The maintainer of the js-flot library is pretty responsive, so I imagine that if you submitted a PR to the upstream js-flot repo, he'd be willing to incorporate it.

The issue there is that it would cause a ton of breaking changes in 3 fairly high-profile packages, which I don't want to take responsibility for. Major CDNs are also still on 0.8.3 for some reason, so there's a good chance Neil will decide it's not worth it just for having log axes in criterion. I'll open an issue on js-flot, but I was mostly suggesting that we think about other options, like

packaging a newer version of flot ourselves
relying on a CDN
moving to a more modern plotting library
decide it's not worth it

Unfortunately none of these sound very good..

The issue there is that it would cause a ton of breaking changes

Ah, I didn't realize that the upgrade would be that significant! Although I know nothing about flot, going from 0.8.3 to 4.2.1 does sound like a pretty sharp increase.

I'll open an issue on js-flot

Thanks. I'll keep an eye on ndmitchell/js-flot#4.

I was mostly suggesting that we think about other options, like

packaging a newer version of flot ourselves
relying on a CDN
moving to a more modern plotting library
decide it's not worth it

Judging from the interest on this issue alone, I'd say that this is worth it! So I'm going to be bold and rule out the fourth option. As far as the other options go:

packaging a newer version of flot ourselves

This is definitely within the realm of possibility. In fact, criterion uses to bundle flot itself before js-flot came along; see #72. As far as I can tell, criterion's dependency on the js-flot library is purely for the convenience of not having to bundle it itself, so there should be no loss in functionality by dropping our dependency on it. Moreover, if js-flot does decide to upgrade to 4.2.1 in the future, we could always reinstate the dependency.

relying on a CDN

I'm not sure I understand what this options entails.

moving to a more modern plotting library

I'd also be open to this idea, although it's unclear to me how much more work this would require.

Status update; the bad news is that it turns out flot 4.2.1 is kind of a mess, or at the very least, does not fit nicely into what we're trying to do. Switching to it is very frustrating, and at this point, I don't recommend we do so.
The good news is that we (@considerate and I) tried out chart.js, which was much more pleasant, doesn't require JQuery and is smaller than flot 4.2.1. You can find the latest proof of concept here. It starts out with a log axis, and clicking a bar will give you a linear scale with the clicked bar as the limits, as an example of the kind of interactivity that chart.js makes easy.
So, the question is whether we want to commit to this rewrite. If you're OK with it, I'll open a new PR and we can move the discussion there, since the log axis is only a small part of it at this point. The main questions are how to package it, plus other feature requests for the reports in general.
If you don't think a major overhaul like this is worth it, that's obviously also completely fine.

Do it! :)
I’m not the maintainer of course. But the point stands, the charting piece
of criterion is crusty and slow and wrong :)
On Thu, Nov 5, 2020 at 12:54 PM Jonas Carpay<EMAIL_ADDRESS>wrote:

Status update; the bad news is that it turns out flot 4.2.1 is kind of a
mess, or at the very least, does not fit nicely into what we're trying to
do. Switching to it is very frustrating, and at this point, I don't
recommend we do so.
The good news is that we (@considerate https://github.com/considerate
and I) tried out chart.js, which was much more pleasant, doesn't require
JQuery and is smaller than flot 4.2.1. You can find the latest proof of
concept here https://jsfiddle.net/dxcbfps5/1/. It starts out with a log
axis, and clicking a bar will give you a linear scale with the clicked bar
as the limits, as an example of the kind of interactivity that chart.js
makes easy.
So, the question is whether we want to commit to this rewrite. If you're
OK with it, I'll open a new PR and we can move the discussion there, since
the log axis is only a small part of it at this point. The main questions
are how to package it, plus other feature requests for the reports in
general.
If you don't think a major overhaul like this is worth it, that's
obviously also completely fine.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/bos/criterion/issues/213#issuecomment-722538968, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAABBQX2AOGATFHRBBPRJSDSOLRGHANCNFSM4HOHEDQQ
.

As a maintainer, I'm tentatively in support of switching to a different charting library if it will make visualizing the data easier. I do think we'll need to make sure that we can replicate the existing functionality in the current flot-based UI in chart.js (to whatever extend we can classify the functionality of the current UI), but I'm hopeful that that won't be too difficult.
In short, please continue with your rewriting efforts! I'm eager to see what this will look like when the rewrite is closer to completion.


add mediatranslation

What component of google-cloud-cpp is this feature request for?
mediatranslation
Is your feature request related to a problem? Please describe.
trying to use this library instead of custom generated
Describe the solution you'd like
mediatranslation added
Describe alternatives you've considered
continue using custom generated api with grpc instead of this library

Thanks for taking the time to file a feature request.  Please give us a few days to think about how to best support products that only have "beta" and "alpha" versions:
https://github.com/googleapis/googleapis/tree/master/google/cloud/mediatranslation
https://cloud.google.com/translate/media/docs

We do not believe we can support libraries for alpha or beta services at this time.  The team supporting google-cloud-cpp is not large and we have to prioritize where we spend our time.  If this is a big problem for you, and you already have a support contract, please open a support case at https://cloud.google.com/support/.


Can't send email to<EMAIL_ADDRESS>

Hello,
Email address<EMAIL_ADDRESS>only accepts emails from within the<EMAIL_ADDRESS>domain/organization.
Is there an alternate email address which we can use?

Thank you

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

ID: 453f416f-1e0f-a73b-6690-c4c8bf34a4e2
Version Independent ID: a8956be7-5b12-04a5-ee73-239973607dca
Content: ID Prefix Reservation
Content Source: docs/nuget-org/id-prefix-reservation.md
Product: nuget
GitHub Login: @karann-msft
Microsoft Alias: karann

Hi there! I see that the screenshot is indicating that<EMAIL_ADDRESS>cannot be emailed. Does the same error message pop up for<EMAIL_ADDRESS>

Problem has been fixed by @aortiz-msft


updated ghwf

Remove 'master' branch from GitHub workflows
Add auto-merge workflow for Dependabot PRs

@dependabot recreate


Valid ValidationResults has detail with error [when usage of const in if statement]

Nuget Package
JsonSchema.Net
Package Version
5.3.1
Operating System
Windows
.Net Target (if relevant, please specify the version in the description)
.Net (5 or after)
A clear and concise description of the bug.
Background: I wanted to provide to a user full description of what is invalid/what is inconsitent in file provided to JSON schema validation. I had to extract all errors from validation results, when validation has failed. During testing I discovered issue with usage of const in if statements. Usage of it produced an error, but it should not.
What did you expect?
If validation is successful (flag IsValid is true) then all ValidationResults should have empty error's list.
If validation failed then list of extracted error's from all details should contain only errors which caused a failure.
Please add test code or steps to reproduce the behavior.
I extended an objects and schema in DeserializationTests like this:
private class Foo
{
        [MinLength(5)]
        public string? Bar { get; set; }
        [Range(40, int.MaxValue)]
        [Required]
        public int Value { get; set; }
        [Required]
        public bool IsMultipleNewValue { get; set; }
        public string? NewValue { get; set; }
        public List<string>? NewValues { get; set; }
}

[JsonSchema(typeof(DeserializationTests), nameof(FooSchema))]
private class FooWithSchema
{
        public string? Bar { get; set; }
        public int Value { get; set; }
        public bool IsMultipleNewValue { get; set; }
        public string? NewValue { get; set; }
        public List<string>? NewValues { get; set; }
}

public static readonly JsonSchema FooSchema =
        new JsonSchemaBuilder()
	        .Type(SchemaValueType.Object)
	        .Properties(
		        (nameof(Foo.Bar), new JsonSchemaBuilder()
			        .Type(SchemaValueType.String | SchemaValueType.Null)
			        .MinLength(5)
		        ),
		        (nameof(Foo.Value), new JsonSchemaBuilder()
			        .Type(SchemaValueType.Integer)
			        .Minimum(40)
		        ),
		        (nameof(Foo.IsMultipleNewValue), new JsonSchemaBuilder()
			        .Type(SchemaValueType.Boolean)
		        ),
		        (nameof(Foo.NewValue), new JsonSchemaBuilder()
			        .Type(SchemaValueType.String, SchemaValueType.Null)
		        ),
		        (nameof(Foo.NewValues), new JsonSchemaBuilder()
			        .Type(SchemaValueType.Array, SchemaValueType.Null)
		        )
	        )
	        .Required(nameof(Foo.Value), nameof(Foo.IsMultipleNewValue))
	        .If(new JsonSchemaBuilder()
		        .Properties((nameof(Foo.IsMultipleNewValue), new JsonSchemaBuilder().Const(true))))
	        .Then(new JsonSchemaBuilder()
		        .Properties(
			        (nameof(Foo.NewValues), new JsonSchemaBuilder()
				        .Type(SchemaValueType.Array)),
			        (nameof(Foo.NewValue), new JsonSchemaBuilder()
				        .Type(SchemaValueType.Null))))
	        .Else(new JsonSchemaBuilder()
		        .Properties(
			        (nameof(Foo.NewValues), new JsonSchemaBuilder()
				        .Type(SchemaValueType.Null)),
			        (nameof(Foo.NewValue), new JsonSchemaBuilder()
				        .Type(SchemaValueType.String, SchemaValueType.Null))));

And added two test cases:
	/// <summary>
	/// validation result should not contain any detail with error when validation succeed
	/// </summary>
	[Test]
	public void WithSchema_AndIfCondition_Pass()
	{
		var jsonText = @"{
  ""Bar"": ""bartholomew"",
  ""Value"": 42,
""IsMultipleNewValue"": false,
""NewValues"": null,
""NewValue"": null
}";

		var validationResult = FooSchema.Evaluate(JsonNode.Parse(jsonText), new EvaluationOptions() { OutputFormat = OutputFormat.List, RequireFormatValidation = true });

		var errors = validationResult.Details.Where(detail => detail.HasErrors);
		Assert.IsEmpty(errors);
	}

	/// <summary>
	/// validation result should contain only one error - missing required field "Value"
	/// </summary>
	[Test]
	public void WithSchema_AndIfCondition_FailWithOneError()
	{
		var jsonText = @"{
  ""Bar"": ""bartholomew"",
""IsMultipleNewValue"": false,
""NewValues"": null,
""NewValue"": null
}";

		var validationResult = FooSchema.Evaluate(JsonNode.Parse(jsonText), new EvaluationOptions() { OutputFormat = OutputFormat.List, RequireFormatValidation = true });

		var errors = validationResult.Details.Where(detail => detail.HasErrors);
		Assert.That(errors, Has.Count.EqualTo(1));
	}

Both tests are failing because there is an error:

Is there any other information you'd like to share regarding this bug?
No response
Code of Conduct

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

Sure, here is minimum I believe.
	public void Evaluate_WithIfConditionAndConstInside_WhenJsonIsValid_ErrorsListShouldBeEmpty()
	{
		var schema = new JsonSchemaBuilder()
			.Properties(("boolProperty", new JsonSchemaBuilder()
				.Type(SchemaValueType.Boolean)))
			.If(new JsonSchemaBuilder()
				.Properties(("boolProperty", new JsonSchemaBuilder().Const(true))));

		const string jsonText = @"{""boolProperty"": false}";

		var validationResult = schema.Evaluate(JsonNode.Parse(jsonText), new EvaluationOptions { OutputFormat = OutputFormat.List});
		var errors = validationResult.Details.Where(detail => detail.HasErrors);

		Assert.IsEmpty(errors);
	}

If this behavior is the expected one then I have no idea how can I provide to user information what have failed during schema validation. This message about const will be confusing and not true.

I thought this was what you were looking for (and I suppose I'll need to write a blog post so I don't have to keep answering this question).
Relevant to this is this spec issue which discusses filtering output units to only those which impact the validation outcome.  It's... complicated.
For this example, I'm going to use the Hierarchical output format because its nested structure makes things a bit easier to visualize.
The schema you gave is effectively
{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "$id": "root",
  "type": "object",
  "properties": {
    "foo": { "type": "boolean" }
  },
  "if": {
    "properties": {
      "foo": { "const": "true" }
    }
  }
}

Now if we throw a then and else in there,
{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "$id": "root",
  "type": "object",
  "properties": {
    "foo": { "type": "boolean" }
  },
  "if": {
    "properties": {
      "foo": { "const": "true" }
    }
  },
  "then": { "required": ["bar"] },
  "else": { "required": ["baz"] }
}

we get varying behavior.  If foo is true, then we require bar; otherwise we require baz.  So both of these validate:
{ "foo": true, "bar": 1 }   // 1
{ "foo": false, "baz": 1 }  // 2

and these don't
{ "foo": false, "bar": 1 }  // 3
{ "foo": true, "baz": 1 }   // 4

Looking at (2), we may ask why this is valid.  Looking through the output,
{
  "valid": true,
  "evaluationPath": "",
  "schemaLocation": "https://json-everything.net/root#",
  "instanceLocation": "",
  "annotations": {
    "properties": [
      "foo"
    ],
    "if": false
  },
  "details": [
    {
      "valid": true,
      "evaluationPath": "/properties/foo",
      "schemaLocation": "https://json-everything.net/root#/properties/foo",
      "instanceLocation": "/foo"
    },
    {
      "valid": false,
      "evaluationPath": "/if",                                                      // 5
      "schemaLocation": "https://json-everything.net/root#/if",
      "instanceLocation": "",
      "details": [
        {
          "valid": false,
          "evaluationPath": "/if/properties/foo",                                   // 6
          "schemaLocation": "https://json-everything.net/root#/if/properties/foo",
          "instanceLocation": "/foo",
          "errors": {
            "const": "Expected \"\\\"true\\\"\""
          }
        }
      ]
    },
    {
      "valid": true,
      "evaluationPath": "/else",
      "schemaLocation": "https://json-everything.net/root#/else",
      "instanceLocation": ""
    }
  ]
}

we see an output unit (5) that indicates the subschema at /if failed validation (specifically the valid property is false).  This means that the /else subschema must pass and the /then subschema is ignored (which we can also see from other output units).  If we want to see why the /if subschema failed, then either it will contain an error itself, or it will contain an output unit somewhere in details that contains an error.  In this case, it's the latter, and shown by (6).
This illustrates that it's quite important to keep the output unit for the /if subschema, even though it failed.

I used Hierarchical output before.  Here's the same validation in List format:
{
  "valid": true,
  "details": [
    {
      "valid": true,
      "evaluationPath": "",
      "schemaLocation": "https://json-everything.net/root#",
      "instanceLocation": "",
      "annotations": {
        "properties": [
          "foo"
        ],
        "if": false
      }
    },
    {
      "valid": true,
      "evaluationPath": "/properties/foo",
      "schemaLocation": "https://json-everything.net/root#/properties/foo",
      "instanceLocation": "/foo"
    },
    {
      "valid": false,
      "evaluationPath": "/if",                                                   // 5
      "schemaLocation": "https://json-everything.net/root#/if",
      "instanceLocation": ""
    },
    {
      "valid": true,
      "evaluationPath": "/else",
      "schemaLocation": "https://json-everything.net/root#/else",
      "instanceLocation": ""
    },
    {
      "valid": false,
      "evaluationPath": "/if/properties/foo",                                    // 6
      "schemaLocation": "https://json-everything.net/root#/if/properties/foo",
      "instanceLocation": "/foo",
      "errors": {
        "const": "Expected \"\\\"true\\\"\""
      }
    }
  ]
}

You can see the (5) and (6) output units are still there, it's just reorganized.  I think this arrangement makes it a bit more difficult to analyze the output to, e.g., debug a validation.  However it's still evident in the evaluationPath property that (6) is a subvalidation of (5).

Lastly, if doesn't affect the validation result:

This validation outcome of this keyword's subschema has no direct effect on the overall validation result.

Its presence in the output is informational.

Thank you @gregsdennis for your detailed answer. I think the most important point for me was this one:

This validation outcome of this keyword's subschema has no direct effect on the overall validation result.

I see it this way: if I want to extract list of errors from whole validation and provide this list to user, then I should ignore ValidationResults which evaluationPath contains /if. Because errors in ignored results did not affect on validation result. So my first question is:
1. Are there any other keywords which also does not affect on overall validation result?
Another point is that I have to provide my own messages about validation result (like required field, expected value and so on). One of the reason is that I have to localize them and you are not supporting such languages (which is ok for me). Right now I see two options:

Take messages from library and use them as a key to get my own messages. I do not like this idea because it will fail once you update any message in a library.
Do some extraction of data from messages to get error data (like what was expected, what was required) and  create own messages based on these data and keys from errors list. But then extracting data from messages looks like some nice hacks. I am missing here property in ValidationResults.Errors which contains error data. Right now there is a key - which validation failed and value - message of failure. I would prefer some structure like: Key, Data and Message. Example:

new Error
{
        Key = "Const",
        Data = new List<string> {"true"},
        Message = "Expected {0}"
}

2. Is it possible to achieve something like this?

Another point is that I have to provide my own messages about validation result

Have you looked at the docs?  They explain how you can provide your own error messages.
Secondarily, a PR with additional translations would be most welcome!

Are there any other keywords which also does not affect on overall validation result?

The issue you're encountering isn't that if doesn't affect overall validation.  It's that it has a subschema that can fail without affecting overall validation.  Another example of this is oneOf.  By definition, it will contain subschemas that fail, but they're all still listed in the output so that you can know why they failed.

Another point is that I have to provide my own messages about validation result

Have you looked at the docs? They explain how you can provide your own error messages.
Secondarily, a PR with additional translations would be most welcome!

Ok, my bad. I see it now. Thanks!
About PR, I will think about it.

Are there any other keywords which also does not affect on overall validation result?

The issue you're encountering isn't that if doesn't affect overall validation. It's that it has a subschema that can fail without affecting overall validation. Another example of this is oneOf. By definition, it will contain subschemas that fail, but they're all still listed in the output so that you can know why they failed.

Got it, thanks.


Add getTransactionPool

Overview

Such method allows to simplify the assertions.

See: https://jira.bf.local/browse/ECR-XYZ
Definition of Done

[ ] There are no TODOs left in the code
[ ] Change is covered by automated tests
[ ] The coding guidelines are followed
[ ] Public API has Javadoc
[ ] Method preconditions are checked and documented in the Javadoc of the method
[ ] Changelog is updated if needed (in case of notable or breaking changes)
[ ] The continuous integration build passes

Coverage remained the same at 86.3% when pulling 48083e82f2da09c4e1a6d9c928f56e6ae6c2c559 on dmitry-timofeev:add-get-transaction-pool into 8e80ff0eff31f2c4cff587272a4dab042715c908 on exonum:master.


[c++] Add new constructor, factor validation helper

Issue and/or context:
The (non-static) constructor for SOMAArray contains a shared_ptr making the lifetime management from R a little trickier.  An easier alternative is to also offer a map<string,string> platform_config from which a Config and Context can be derived -- as in the two static ctors.
Changes:
This PR adds a second constructor with platform_config interface and places the validation code into a new helper function both non-static constructors call.
Notes for Reviewer:
SC-32281

Codecov Report
Patch coverage has no change and project coverage change: -11.09% :warning:

Comparison is base (0e54575) 64.66% compared to head (2962449) 53.58%.
 Consider uploading reports for the commit 92d9ae4 to get more accurate results

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
Additional details and impacted files
@@             Coverage Diff             @@
##             main    #1560       +/-   ##
===========================================
- Coverage   64.66%   53.58%   -11.09%
===========================================
  Files         104       74       -30
  Lines        8686     6134     -2552
===========================================
- Hits         5617     3287     -2330
+ Misses       3069     2847      -222

Flag
Coverage Δ

python
?

r
53.58% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.
see 31 files with indirect coverage changes

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


Import  function via Powershell Az Module or Rest API

Is there any way to perform this steps using PowerShell or the Azure REST API, instead of the User Interface? Been trying to do this so I can integrate that import into an Azure DevOps Pipeline. Unfortunately I've yet not succeeded to configure this properly, either way.

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

ID: a0b38af1-81e7-341a-d7bf-e471ea7585e5
Version Independent ID: 6d16fd43-249e-5afc-062a-2e019eade30e
Content: Import an Azure Function App as an API in Azure API Management
Content Source: articles/api-management/import-function-app-as-api.md
Service: api-management
GitHub Login: @mikebudzynski
Microsoft Alias: apimpm

@lusocoding Thanks for the Comment. We are actively investigating and will get back to you soon.

@lusocoding At this moment there is no single API call or PowerShell command that will import a Function App as an API in API Management. We're planning to improve this experience in future.
For now you can use the browser developer tools (F12) to track the ARM calls that are issued as part of the import process - including calls to Azure Functions and API Management.

Thanks for the quick reply @mikebudzynski. Will try to do exactly that then.

#please-close

do we have a way to import function app in apim via PowerShell now ?

@nuno-barreiro were you able to leverage the API calls to import the function as API?

Hi @jpl2nd ... I started but I was never able to finish that and in the meantime the project went on another direction too, so no need for that anymore.


Don't fetch config

Since we are only going to send events to our cloud function we don't need to fetch the config.
The config is used to be able to send event directly to other destinations such as GA or amplitude

LGTM


[ingest] Ensure Tesseract OCR version >= V5

Version 5 of Tesseract has improved OCR accuracy. Screen-pipe should attempt to install the latest version, which involves building from source.

Frankie, thanks for the suggestion!

@PSU3D0 are you on linux? otherwise we launch
screenpipe --ocr-engine windows-native
or
screenpipe --ocr-engine apple-native


Cluster - RegisterServices - retry forever / throw exception on failure

Due to the AWS outage the other day. there was a case where an ECS node tried to start, the RegisterService retried but failed. so the member was never registered as a member. even though the app itself started and worked fine.
Resulting in a sort of zombie cluster member.
We could make it so that nothing progresses until RegisterService has completed.
And we should do this for all cluster providers since it could theoretically happen anywhere.
Better to let cluster.StartMemberAsync just hang forever waiting for registration to complete. logging any issue.

Hey there. I was curious if you had a chance to look into this yet.

Closing for now, if we need to extend this behavior, we can do this as a separate issue


[bug] enhance match case

assert!(glob_match("**/y.txt", "y.txt"));  				// panic
assert!(glob_match("**/package.json", "package.json"));   	 // panic
assert!(glob_match("**/{package}.json", "package.json"));	 // true

Maybe this should work.

All of those seem to pass with the latest version. Do you still see an issue?

All of those seem to pass with the latest version. Do you still see an issue?

Looks good, and take my star 😆