nodejs-express stack cannot be built anymore

Describe the bug
Something changed in the RPM database referenced during the application build and the build never completes. The symptoms affect local appsody build calls, as well as tekton pipeline runs.
To Reproduce
Steps to reproduce the behavior:

Initialize an application directory with the nodejs-express stack:

appsody init kabanero/nodejs-express
appsody build --docker-options="--no-cache"

Expected behavior
Build should complete without errors and create a container image.
Actual behaviour
Build fails with the following log:
Yeager2:service-a nastacio$ appsody build --docker-options="--no-cache"
Extracting project from development environment
Pulling docker image docker.io/kabanero/nodejs-express:0.2
Running command: docker pull docker.io/kabanero/nodejs-express:0.2
0.2: Pulling from kabanero/nodejs-express
Digest: sha256:2d0bb6bfbbd6d4e24803d18b85edab2ae3083ab716b9a26f833300715a8caa5c
Status: Image is up to date for kabanero/nodejs-express:0.2
docker.io/kabanero/nodejs-express:0.2
[Warning] The stack image does not contain APPSODY_PROJECT_DIR. Using /project
Running command: docker create --name service-a-extract -v /Users/nastacio/workspace/cp4a-labs/service-a/:/project/user-app docker.io/kabanero/nodejs-express:0.2
Running command: docker cp service-a-extract:/project /Users/nastacio/.appsody/extract/service-a
Project extracted to /Users/nastacio/.appsody/extract/service-a
Running command: docker rm service-a-extract -f
Running command: docker build -t dev.local/service-a --no-cache --label "dev.appsody.stack.commit.date=Fri Apr 3 09:22:57 2020 +0100" --label "dev.appsody.stack.title=Node.js Express" --label "dev.appsody.stack.description=Express web framework for Node.js" --label "dev.appsody.stack.commit.committer=GitHub<EMAIL_ADDRESS>--label "name=kabanero/nodejs-express" --label "release=66" --label "org.opencontainers.image.title=service-a" --label "dev.appsody.image.commit.committer=GitHub<EMAIL_ADDRESS>--label "maintainer=SoftwareCollections.org<EMAIL_ADDRESS>--label "vendor=Kabanero" --label "io.openshift.expose-services=8080:http" --label "architecture=x86_64" --label "usage=s2i build <SOURCE-REPOSITORY> ubi8/nodejs-10:latest <APP-NAME>" --label "org.opencontainers.image.documentation=https://github.com/think-2020-cp4a/service-a" --label "org.opencontainers.image.revision=1a7f990fc71a6e949f19f77a55628e52adc2dd63-modified" --label "authoritative-source-url=registry.access.redhat.com" --label "dev.appsody.stack.licenses=Apache-2.0" --label "io.k8s.display-name=Node.js 10" --label "summary=Image for Kabanero Node.js Express development" --label "io.s2i.scripts-url=image:///usr/libexec/s2i" --label "dev.appsody.stack.revision=27a3254c80e6c5367a76e6099c2e18b393d15841" --label "url=https://access.redhat.com/containers/#/registry.access.redhat.com/ubi8/nodejs-10/images/1-66" --label "vcs-type=git" --label "dev.appsody.image.commit.message=Update .appsody-config.yaml" --label "dev.appsody.stack.url=https://github.com/kabanero-io/collections/tree/master/incubator/nodejs-express" --label "dev.appsody.stack.source=https://github.com/kabanero-io/collections/tree/master/incubator/nodejs-express/image" --label "dev.appsody.stack.commit.author=kilnerm<EMAIL_ADDRESS>--label "com.redhat.deployments-dir=/opt/app-root/src" --label "dev.appsody.image.commit.author=Denilson Nastacio<EMAIL_ADDRESS>--label "dev.appsody.image.commit.date=Mon Apr 27 17:21:10 2020 -0400" --label "build-date=2020-01-30T08:16:17.662981" --label "description=This image contains the Kabanero development stack for the Nodejs Express collection" --label "com.redhat.build-host=cpt-1008.osbs.prod.upshift.rdu2.redhat.com" --label "io.openshift.s2i.scripts-url=image:///usr/libexec/s2i" --label "io.k8s.description=Node.js 10 available as container is a base platform for building and running various Node.js 10 applications and frameworks. Node.js is a platform built on Chrome's JavaScript runtime for easily building fast, scalable network applications. Node.js uses an event-driven, non-blocking I/O model that makes it lightweight and efficient, perfect for data-intensive real-time applications that run across distributed devices." --label "vcs-ref=6bc1753cc6499a5573f9fac87a839bc3fa7798d2" --label "dev.appsody.stack.id=nodejs-express" --label "dev.appsody.stack.commit.contextDir=/incubator/nodejs-express" --label "dev.appsody.stack.documentation=https://github.com/kabanero-io/collections/tree/master/incubator/nodejs-express/README.md" --label "com.redhat.dev-mode.port=DEBUG_PORT:5858" --label "dev.appsody.stack.tag=docker.io/kabanero/nodejs-express:0.2.10" --label "com.redhat.component=nodejs-10-container" --label "org.opencontainers.image.url=https://github.com/think-2020-cp4a/service-a" --label "distribution-scope=public" --label "help=For more information visit https://github.com/sclorg/s2i-nodejs-container" --label "com.redhat.dev-mode=DEV_MODE:false" --label "org.opencontainers.image.created=2020-04-29T15:56:49-04:00" --label "version=0.2.10" --label "dev.appsody.stack.created=2020-04-21T06:50:55Z" --label "dev.appsody.stack.configured=docker.io/kabanero/nodejs-express:0.2" --label "com.redhat.license_terms=https://www.redhat.com/en/about/red-hat-end-user-license-agreements#UBI" --label "org.opencontainers.image.source=https://github.com/think-2020-cp4a/service-a/tree/v1" --label "dev.appsody.stack.authors=Chris Bailey<EMAIL_ADDRESS>Neeraj Laad<EMAIL_ADDRESS>--label "io.openshift.tags=builder,nodejs,nodejs10" --label "dev.appsody.stack.version=0.2.10" --label "dev.appsody.stack.commit.message=Merge pull request #316 from groeges/release-0.6" -f /Users/nastacio/.appsody/extract/service-a/Dockerfile /Users/nastacio/.appsody/extract/service-a
[Docker] Sending build context to Docker daemon    194kB
[Docker] Step 1/80 : FROM registry.access.redhat.com/ubi8/nodejs-10:1-66
[Docker]  ---> 83e13db75f5f
[Docker] Step 2/80 : USER root
[Docker]  ---> Running in 4c88e71aa1fa
[Docker] Removing intermediate container 4c88e71aa1fa
[Docker]  ---> 4571777cc0e6
[Docker] Step 3/80 : RUN yum upgrade --disableplugin=subscription-manager -y  && yum install --disableplugin=subscription-manager python2 -y  && yum clean --disableplugin=subscription-manager packages  && ln -s /usr/bin/python2 /usr/bin/python  && useradd --uid 1000 --gid 0 --shell /bin/bash --create-home node
[Docker]  ---> Running in be940cb71fd0
[Docker] Red Hat Universal Base Image 8 (RPMs) - BaseOS  1.8 MB/s | 762 kB     00:00
[Docker] Red Hat Universal Base Image 8 (RPMs) - AppStre 7.5 MB/s | 3.7 MB     00:00
[Docker] Red Hat Universal Base Image 8 (RPMs) - CodeRea  43 kB/s | 9.1 kB     00:00
[Docker] Error:
[Docker]  Problem 1: cannot install the best update candidate for package python3-rpm-4.14.2-25.el8.x86_64
[Docker]   - nothing provides libzstd.so.1()(64bit) needed by python3-rpm-4.14.2-37.el8.x86_64
[Docker]  Problem 2: cannot install the best update candidate for package rpm-4.14.2-25.el8.x86_64
[Docker]   - nothing provides libzstd.so.1()(64bit) needed by rpm-4.14.2-37.el8.x86_64
[Docker]  Problem 3: cannot install the best update candidate for package rpm-build-libs-4.14.2-25.el8.x86_64
[Docker]   - nothing provides libzstd.so.1()(64bit) needed by rpm-build-libs-4.14.2-37.el8.x86_64
[Docker]  Problem 4: cannot install the best update candidate for package rpm-libs-4.14.2-25.el8.x86_64
[Docker]   - nothing provides libzstd.so.1()(64bit) needed by rpm-libs-4.14.2-37.el8.x86_64
[Docker]  Problem 5: package python3-dnf-4.2.17-6.el8.noarch requires python3-rpm >= 4.14.2-35, but none of the providers can be installed
[Docker]   - cannot install the best update candidate for package python3-dnf-4.2.7-7.el8_1.noarch
[Docker]   - nothing provides libzstd.so.1()(64bit) needed by python3-rpm-4.14.2-37.el8.x86_64
[Docker]  Problem 6: package dnf-4.2.17-6.el8.noarch requires python3-dnf = 4.2.17-6.el8, but none of the providers can be installed
[Docker]   - package python3-dnf-4.2.17-6.el8.noarch requires python3-rpm >= 4.14.2-35, but none of the providers can be installed
[Docker]   - cannot install the best update candidate for package dnf-4.2.7-7.el8_1.noarch
[Docker]   - nothing provides libzstd.so.1()(64bit) needed by python3-rpm-4.14.2-37.el8.x86_64
[Docker]  Problem 7: package python3-dnf-plugins-core-4.0.12-3.el8.noarch requires python3-dnf >= 4.2.17, but none of the providers can be installed
[Docker]   - package python3-dnf-4.2.17-6.el8.noarch requires python3-rpm >= 4.14.2-35, but none of the providers can be installed
[Docker]   - cannot install the best update candidate for package python3-dnf-plugins-core-4.0.8-3.el8.noarch
[Docker]   - nothing provides libzstd.so.1()(64bit) needed by python3-rpm-4.14.2-37.el8.x86_64
[Docker]  Problem 8: package python3-dnf-plugins-core-4.0.12-3.el8.noarch requires python3-dnf >= 4.2.17, but none of the providers can be installed
[Docker]   - package dnf-plugins-core-4.0.12-3.el8.noarch requires python3-dnf-plugins-core = 4.0.12-3.el8, but none of the providers can be installed
[Docker]   - package python3-dnf-4.2.17-6.el8.noarch requires python3-rpm >= 4.14.2-35, but none of the providers can be installed
[Docker]   - cannot install the best update candidate for package dnf-plugins-core-4.0.8-3.el8.noarch
[Docker]   - nothing provides libzstd.so.1()(64bit) needed by python3-rpm-4.14.2-37.el8.x86_64
[Docker]  Problem 9: package dnf-4.2.17-6.el8.noarch requires python3-dnf = 4.2.17-6.el8, but none of the providers can be installed
[Docker]   - package yum-4.2.17-6.el8.noarch requires dnf = 4.2.17-6.el8, but none of the providers can be installed
[Docker]   - package python3-dnf-4.2.17-6.el8.noarch requires python3-rpm >= 4.14.2-35, but none of the providers can be installed
[Docker]   - cannot install the best update candidate for package yum-4.2.7-7.el8_1.noarch
[Docker]   - nothing provides libzstd.so.1()(64bit) needed by python3-rpm-4.14.2-37.el8.x86_64
[Docker]  Problem 10: problem with installed package python3-dnf-4.2.7-7.el8_1.noarch
[Docker]   - package python3-hawkey-0.39.1-5.el8.x86_64 conflicts with python3-dnf < 4.2.13 provided by python3-dnf-4.2.7-7.el8_1.noarch
[Docker]   - package python3-dnf-4.2.17-6.el8.noarch requires python3-rpm >= 4.14.2-35, but none of the providers can be installed
[Docker]   - cannot install the best update candidate for package python3-hawkey-0.35.1-9.el8_1.x86_64
[Docker]   - nothing provides libzstd.so.1()(64bit) needed by python3-rpm-4.14.2-37.el8.x86_64
[Docker]  Problem 11: package python3-dnf-plugins-core-4.0.8-3.el8.noarch requires python3-dnf >= 4.2.7-3, but none of the providers can be installed
[Docker]   - package dnf-plugin-subscription-manager-1.26.16-1.el8.x86_64 requires python3-dnf-plugins-core, but none of the providers can be installed
[Docker]   - package python3-dnf-4.2.7-7.el8_1.noarch requires dnf-data = 4.2.7-7.el8_1, but none of the providers can be installed
[Docker]   - package python3-dnf-plugins-core-4.0.12-3.el8.noarch requires python3-dnf >= 4.2.17, but none of the providers can be installed
[Docker]   - cannot install both dnf-data-4.2.17-6.el8.noarch and dnf-data-4.2.7-7.el8_1.noarch
[Docker]   - package python3-dnf-4.2.17-6.el8.noarch requires python3-rpm >= 4.14.2-35, but none of the providers can be installed
[Docker]   - cannot install the best update candidate for package dnf-plugin-subscription-manager-1.25.17-1.el8.x86_64
[Docker]   - cannot install the best update candidate for package dnf-data-4.2.7-7.el8_1.noarch
[Docker]   - nothing provides libzstd.so.1()(64bit) needed by python3-rpm-4.14.2-37.el8.x86_64
[Docker]  Problem 12: package python3-hawkey-0.39.1-5.el8.x86_64 conflicts with python3-dnf < 4.2.13 provided by python3-dnf-4.2.7-7.el8_1.noarch
[Docker]   - package python3-dnf-plugins-core-4.0.8-3.el8.noarch requires python3-dnf >= 4.2.7-3, but none of the providers can be installed
[Docker]   - problem with installed package python3-hawkey-0.35.1-9.el8_1.x86_64
[Docker]   - package dnf-plugin-subscription-manager-1.26.16-1.el8.x86_64 requires python3-dnf-plugins-core, but none of the providers can be installed
[Docker]   - package python3-hawkey-0.35.1-9.el8_1.x86_64 requires libdnf(x86-64) = 0.35.1-9.el8_1, but none of the providers can be installed
[Docker]   - package python3-dnf-plugins-core-4.0.12-3.el8.noarch requires python3-dnf >= 4.2.17, but none of the providers can be installed
[Docker]   - package subscription-manager-1.26.16-1.el8.x86_64 requires dnf-plugin-subscription-manager = 1.26.16, but none of the providers can be installed
[Docker]   - cannot install both libdnf-0.39.1-5.el8.x86_64 and libdnf-0.35.1-9.el8_1.x86_64
[Docker]   - package python3-dnf-4.2.17-6.el8.noarch requires python3-rpm >= 4.14.2-35, but none of the providers can be installed
[Docker]   - cannot install the best update candidate for package subscription-manager-1.25.17-1.el8.x86_64
[Docker]   - cannot install the best update candidate for package libdnf-0.35.1-9.el8_1.x86_64
[Docker]   - nothing provides libzstd.so.1()(64bit) needed by python3-rpm-4.14.2-37.el8.x86_64
[Docker]  Problem 13: package python3-hawkey-0.39.1-5.el8.x86_64 conflicts with python3-dnf < 4.2.13 provided by python3-dnf-4.2.7-7.el8_1.noarch
[Docker]   - package python3-dnf-plugins-core-4.0.8-3.el8.noarch requires python3-hawkey >= 0.34.0, but none of the providers can be installed
[Docker]   - package python3-dnf-plugins-core-4.0.8-3.el8.noarch requires python3-dnf >= 4.2.7-3, but none of the providers can be installed
[Docker]   - problem with installed package python3-dnf-plugins-core-4.0.8-3.el8.noarch
[Docker]   - package python3-hawkey-0.35.1-9.el8_1.x86_64 requires python3-libdnf = 0.35.1-9.el8_1, but none of the providers can be installed
[Docker]   - package python3-dnf-plugins-core-4.0.12-3.el8.noarch requires python3-dnf >= 4.2.17, but none of the providers can be installed
[Docker]   - cannot install both python3-libdnf-0.39.1-5.el8.x86_64 and python3-libdnf-0.35.1-9.el8_1.x86_64
[Docker]   - package python3-dnf-4.2.17-6.el8.noarch requires python3-rpm >= 4.14.2-35, but none of the providers can be installed
[Docker]   - cannot install the best update candidate for package python3-libdnf-0.35.1-9.el8_1.x86_64
[Docker]   - nothing provides libzstd.so.1()(64bit) needed by python3-rpm-4.14.2-37.el8.x86_64
[Docker] (try to add '--allowerasing' to command line to replace conflicting packages or '--skip-broken' to skip uninstallable packages or '--nobest' to use not only best candidate packages)
[Docker] The command '/bin/sh -c yum upgrade --disableplugin=subscription-manager -y  && yum install --disableplugin=subscription-manager python2 -y  && yum clean --disableplugin=subscription-manager packages  && ln -s /usr/bin/python2 /usr/bin/python  && useradd --uid 1000 --gid 0 --shell /bin/bash --create-home node' returned a non-zero code: 1
[Error] exit status 1

Environment Details (please complete the following information):

OS: [e.g. iOS] N/A
Browser [e.g. chrome, safari] N/A
Version [e.g. 22] N/A

If applicable please specify:

CLI version: appsody 0.5.8
Collection you are using:
kabanero/nodejs-express

Screenshots
None
Additional context
This problem started happening today, 4/29. I think it is related to the yum upgrade call at the beginning of the build, which may have bumped into some change to the RPM database.

cc @groeges

This is sometimes an issue with the package manager / package repository and normally sorts itself out.
Anyway, in order to keep the builds using the same packages that are available on the base images, we should not be doing a yum upgrade within the Dockerfile.
The following PR: https://github.com/kabanero-io/collections/pull/327 has removed the yum upgrade.


It can deploy the illegal code via VSCode without validation error.

Describe the Bug with repro steps
It isn't efficient.
For example, we can deploy the code unexpectedly like below including terminate action within ForEach.

Only after the opening from AzurePortal, we can find the validation error of the code.

What type of Logic App Is this happening in?
Standard (VSCode)
Which operating system are you using?
Windows
Are you using new designer or old designer
New Designer
Did you refer to the TSG before filing this issue? https://aka.ms/lauxtsg
Yes
Workflow JSON
{
    "definition": {
        "$schema": "https://schema.management.azure.com/providers/Microsoft.Logic/schemas/2016-06-01/workflowdefinition.json#",
        "actions": {
            "For_each": {
                "type": "Foreach",
                "foreach": "@range(0,3)",
                "actions": {
                    "Terminate": {
                        "type": "Terminate",
                        "inputs": {
                            "runStatus": "Failed",
                            "runError": {
                                "code": "9",
                                "message": "error"
                            }
                        }
                    }
                },
                "runAfter": {}
            }
        },
        "triggers": {
            "When_a_HTTP_request_is_received": {
                "type": "Request",
                "kind": "Http"
            }
        },
        "contentVersion": "<IP_ADDRESS>",
        "outputs": {},
        "parameters": {}
    },
    "kind": "Stateful"
}

Screenshots or Videos
No response
Browser
via VSCode.
Additional context
No response

We can refer:
Do not allow to save if there are illegal steps on a workflow. · Issue #984 · Azure/logicapps (github.com)

Hi @nobuko-yamada thanks for raising this isssue. I will take a look on how we can validate the workflow.json before deploying it

Hi @nobuko-yamada I will make the update to validate the workflow definition while saving it when using the Designer locally and prior deploying it. I am working with the BE team right now to make the right changes for it. I will update the issue as soon as I have the fix

[heart]         Nobuko Yamada reacted to your message:

From: Carlos Emiliano Castro Trejo @.>
Sent: Tuesday, September 24, 2024 11:00:13 PM
To: Azure/LogicAppsUX @.>
Cc: Mention @.>; Author @.>; Comment @.***>
Subject: Re: [Azure/LogicAppsUX] It can deploy the illegal code via VSCode without validation error. (Issue #5666)
Hi @nobuko-yamadahttps://github.com/nobuko-yamada I will make the update to validate the workflow definition while saving it when using the Designer locally and prior deploying it. I am working with the BE team right now to make the right changes for it. I will update the issue as soon as I have the fix
—
Reply to this email directly, view it on GitHubhttps://github.com/Azure/LogicAppsUX/issues/5666#issuecomment-2372534105 or unsubscribehttps://github.com/notifications/unsubscribe-auth/A3NXCBFSI574NO5OOHXWHULZYHVH3BFKMF2HI4TJMJ2XIZLTSSBKK5TBNR2WLJDUOJ2WLJDOMFWWLO3UNBZGKYLEL5YGC4TUNFRWS4DBNZ2F6YLDORUXM2LUPGBKK5TBNR2WLJDUOJ2WLJDOMFWWLLTXMF2GG2C7MFRXI2LWNF2HTAVFOZQWY5LFUVUXG43VMWSG4YLNMWVXI2DSMVQWIX3UPFYGLAVFOZQWY5LFVI2TGMBXGQ4TIMRVGKSG4YLNMWUWQYLTL5WGCYTFNSWHG5LCNJSWG5C7OR4XAZNMJFZXG5LFINXW23LFNZ2KM5DPOBUWG44TQKSHI6LQMWVHEZLQN5ZWS5DPOJ42K5TBNR2WLKJTHE4TMMJYHE4TTAVEOR4XAZNFNFZXG5LFUV3GC3DVMWVDENJSGM4TKMBQGQ3YFJDUPFYGLJLMMFRGK3FFOZQWY5LFVI2TGMBXGQ4TIMRVGKTXI4TJM5TWK4VGMNZGKYLUMU.
You are receiving this email because you were mentioned.
Triage notifications on the go with GitHub Mobile for iOShttps://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Androidhttps://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.


Can we have more examples?

I cannot wrap my head around how this is possible, when and where we deserialized the BackwardPaginationArgsor ForwardPaginationArgs?
I think it is a good idea to jot down somewhere in the doc that you're gonna do it probably in a middleware. Or at least that's my best guess right now. Why I think it is this way? Because here you're directly using ForwardPaginationArgs type and ForwardPaginationArgs won't accept string as its generic value for the cursor.
All in all the doc can be improved by a lot if you ask me.

After a close inspection of the codebase I understood what is happening beneath the surface :sweat_smile:. We have defined a new scalar types:
https://github.com/johnsonjo4531/typegraphql-relay-connections/blob/a832f566a1fe4e7a2fb33511afe5607b70d73a73/src/index.ts#L9-L18
And then in that scalar type we are deserializing and serializing the cursor.
https://github.com/johnsonjo4531/typegraphql-relay-connections/blob/a832f566a1fe4e7a2fb33511afe5607b70d73a73/src/cursor.ts#L107-L112
Now I think I must have missed something in the docs about this part.

Hey sorry I'm on vacation at the moment so my reply will be short, but I'll try and reply now and I can more replies possibly before I get back to work in January.
First I would look at how to overwrite the default cursor which is also described here
Second you can always pass in the type of the cursor but its shape is an object with string keys (and as you noticed it must not be other things such as a sting itself.)
Also the cursor isn't really passed in it is taken from the node itself. So if all your nodes/objects have (as part of their fields) and are identifiable by an id with a string type you may want to just overwrite the default cursor like so in a typescript definition module:
declare module 'typegraphql-relay-connections' {
export interface Cursor {
id: string;
}
}


Handling connection error

How to handle connection error with nestjs-redis?
For example I turn off my redis container and it should throw an error that it can't connect to redis

Reference documentation: https://github.com/luin/ioredis#connection-events


Using Word RNN for word prediction

I am a undergraduate research assistant at Purdue University. I am attempting to use the Word RNN you have hosted on github to improve automated monkey testing (by supplying context relevant input instead of random input that the monkey uses). In a few words, I would like to give the RNN a word or phrase (the context) and would like the output of the RNN (for the monkey to use as input) to be the next predicted word. However, right now, the Word RNN implementation looks like it does only a sampling and cannot take input (a phrase or word) and output the next predicted word. Any suggestions on how to go about changing the implementation for my needs?
Example:
In a movie app, we record the following sequence:
⟨Movie,Search,Star Trek\n⟩.
And we train the RNN on similar datasets with these kind of sequences.
Later,
If I give the RNN "Movie, Search" as input, I am looking for the predicted next word, which should be relevant input for the app.

Are you looking for the --prime option?
parser.add_argument('--prime', type=str, default=' ',
                       help='prime text')

Possibly. The description of prime from the "char rnn" github repo is "Priming. It's also possible to prime the model with some starting text using -primetext. This starts out the RNN with some hardcoded characters to warm it up with some context before it starts generating text. E.g. a fun primetext might be -primetext "the meaning of life is ". I was not sure if this is the feature I was looking for. I will train the rnn on my data set and see if the prime feature is what I am looking for and reach back out to you. Thanks for the help!

@mahmoodn1 Did you try our head version? I think it is fixed. Please let us know if it is not the case.


version update and regarding web

Hi,
I wanted to use this library with react native web, I have forked this library. Now I wanted to add some packages and update the version of react native and react using diff-purge so that react-native-web which uses react version 17.0.2  will become compatible.
Problem while updating react version:
I am not able to find certain files, that need to be updated i.e -
-AppDelegate.mm
-AppDelegate.h
And many others based on this diff purge version update : https://github.com/react-native-community/rn-diff-purge/compare/release/0.61.5..release/0.69.0

A lot of files have moved or deleted. The entire iOS code has been rewritten. The only suggestion I have is to do a diff against the version of master you forked off, and then manually apply all your local changes to current master.


Allow usage via API

Thanks for your great tool! It would be great if it was possible to use it in more automated way thanks to some simple API, the most basic idea would be receiving the feed name and returning the generated id, though returning an object containing mail address and feed address may be preferred. I may even implement this if you are willing to accept such a feature

Thanks for the idea. I actually like it. I’ll take it on myself as part of some changes I already want to make. I’ll let you know when it’s read.

Thank you, I'll be looking forward to it!

Hi @zakius,
I implemented this and it’ll be out on the next version of Kill the Newsletter!
The only routes that I found made sense as an API are the create feed and delete feed routes.
The delete feed route already acts like an API, you can just ignore the HTML that it returns.
For the create feed route I added a way for you to send a request header of Accept: application/json and the server responds with JSON instead of the usual HTML, for example:
$ curl --request POST --header "CSRF-Protection: true" --header "Accept: application/json" --data "title=Example of a feed" https://localhost/
{"feedId":"r4n7siivh4iiho0gtv59","email":"r4n7siivh4iiho0gtv59@localhost","feed":"https://localhost/feeds/r4n7siivh4iiho0gtv59.xml"}

I’m curious to know what you end up creating with this.
Best.

Thanks! If you don't mind I'd like to use it in a browser extension that simplifies feed detection and subscription, I'm not entirely sure whether I'll submit it to extension repositories as it's meant mainly to integrate with my self hosted aggregating service but it will surely end up on GitHub some day

Sounds great!


Allow retry on invalid amount

If the client is out of sync with the server and receives payment headers with Rdn-Invalid-Amount set, it should retry the request with an updated balance.

Looks fine. I'll leave #244 open though, for the test. We should definitely have one that goes through this kind of client/server exchange.


Plugins: Add Plugin hexo-cdn-jsdelivr

Check List
Please read and check followings before submitting a PR.

[ ] I want to publish my theme on Hexo official website.

[ ] I have read the theme publishing doc.
[ ] name is unique.
[ ] link URL is correct.
[ ] preview URL is correct.
[ ] preview URL web site is rendered correctly.
[ ] Add a screenshot to source/themes/screenshots.
[ ] Screenshot filename is same as value of name.
[ ] Screenshot size is 800 * 500.
[ ] Screenshot file format is png.

[x] I want to publish my plugin on Hexo official website.

[x] I have read the plugin publishing doc.
[x] name is unique.
[x] link URL is correct.

[ ] Others (Update, fix, translation, etc...)

Languages:
[ ] en English
[ ] ko Korean
[ ] pt-br Brazilian Portuguese
[ ] ru Russian
[ ] th Thai
[ ] zh-cn simplified Chinese
[ ] zh-tw traditional Chinese

Hello, does anyone have time to review this pull request?

@renzibei I am not sure whether the plugin violates the ToS of jsDelivr or not.
@MartinKolarik Would you mind having a look at this?

@renzibei I am not sure whether the plugin violates the ToS of jsDelivr or not.
@MartinKolarik Would you mind having a look at this?

@SukkaW  You may want to look at this issue, More explicit terms of use are needed. Though there are no explicit terms of use for jsDelivr yet, one of its developers does not seem to oppose using jsDelivr as a CDN for small sites.

Please wait with this for a few days until we discuss it and provide better guidelines.

The use policy of jsdelivr has been created #18247.
I think this plugin itself is just a tool for the convenience of website developers. It's up to the user whether it will violate the user policy of jsdelivr.
@MartinKolarik

Any updates on this thread?


change name to match with existing resources

Short description:
Name of this file ocp_resources/console_quick_starts.py does not match with existing naming convention
More details:
This naming mismatch is causing issues with automation that relies on names to follow a convention.
What this PR does / why we need it:
Changing the name would help with automation of https://issues.redhat.com/browse/CNV-12118
Which issue(s) this PR fixes:
Ability to automate https://issues.redhat.com/browse/CNV-12118
Special notes for reviewer:
Bug:

/verified

/approve


Add syntax highlighting

Closes #13

Thanks for working on this 🙏! I'm going to make a few other additions to improve the usability of this feature within the inputs (namely multi-line)and then we can release it.


Corrected typo and formatting

Changed M8ps in Table header to MBps

@rishabv90
Can you review the proposed changes?
When the changes are ready for publication, add a #sign-off comment to signal that the PR is ready for the review team to merge.
#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

#sign-off

Had a discussion with @rishabv90, and according to him, these PRs/issues are duplicates of what they have already addressed through ICMs. Closing this issue. Should this issue be still existing, request to file new issue to work on. Thanks!
#please-close


[bug] Running two instances of hyprlock disables it

I use hypridle to run hyprlock after 60s of inactivity. If I manually start hyprlock, then after 60s, due to hypridle running hyprlock, the first hyprlock completely shuts down and unlocks the computer. Notably, the hyprlock process still stays on and doesn't allow locking the computer again until it is killed first.
Steps to Reproduce

Open a terminal and run sleep 10 && hyprlock
Open another terminal and run hyprlock
The computer will get unlocked after 10s.

Version Information

Hyprlock v0.3.0-1 from the extra repo.
Idk what other information to provide, please let me know if you need any.

this is fixed in hyprland git and unrelated to hyprlock

Does the related hyprland commit also fix fullscreen windows appearing over hyprlock?

different iirc but its also fixed in git


Allow setting legend title in scale_xxx_biolizard functions

The classic scale_xxx functions allow setting the title as the first argument, e.g. scale_color_discrete("Treatment"), this does not work for the scale_xxx_biolizard functions:

Now, you need to set the name parameter explicitly, e.g. scale_color_biolizard(name = "Treatment")


Consider removing add() and addMultiple()

add() and addMultiple() work like set() and setMultiple() except they store cache only if there is no existing value.
Personally, I've never used it. Need opinions about removing these.

I've never used them either but maybe some random library that requires providing a PSR-16 adapter (like does florianv/swap) would expect them?

No, these are not part of PSR-16. These are added on top of it.

https://forum.yiiframework.com/t/cache-is-nearly-final/126716

Oh! Then it is your call. I've personally never seen or heard of a developper complaining about a bonus feature :)

I've never seen or heard about a developper complaining about a bonus feature

Yes, it's mainly maintainers complaining internally :)


Simplify the logic of LUI execution

data_out is reg as well. so it is fine. I run through the test cases:
====> Test PASSED, Total of 55 cases

Thanks for your contribution!


Godot doesn't notify user of potentially sizable loss of data when "editable children" is checked off.

Godot version:

Godot 3.0.2 Stable
OS/device including version:

i7 3770 CPU; AMD 7700 GPU; 24 gigs RAM; Win10 64 bit (Fall Creators update)
Issue description:

When the editable children checkbox is disabled while information within has been edited or overriden, there will be no notification if the user saves the scene and exits the project. The user then loses the edited data (changed values, groups, everything). I for instance use editable children to modify Blender scene files brought in as a child scene of a larger scene (for avoiding loss of work if a re-import is needed).  This can sneak up on you for instance since the editable children checkbox will instantly revert to 'off' if the name of its top node is changed.
The thing though, you can lose more than assignments if you turn the checkbox off and forget to turn it back on. Material files that only existed inside of overridden material slots can get corrupted and become an invalid file, forcing the user to recreate it.
I do make backups fortunately, so I lost a very small amount of work at most. I don't think the scene has to be a Collada file even, but any scene that is a child and has overridden values. I think it is possible that forgetting data like this is by design, but the user gets no warning that it will be the case (and as I mentioned before, there is one case where it can sneak up and not get caught).

I agree that it should check for modifications and issue a warning.

This can sneak up on you for instance since the editable children checkbox will instantly revert to 'off' if the name of its top node is changed.

That's a bug in its own right though, it should be fixed independently of the addition of a warning when checking off.


log viewer in the gui

[x] make an endpoint that returns the log file
[x] make a log tab in the GUI
[x] load the log continuously with updates

still some design left to resolve but it's more or less done


Booting issue

Had a power outage and trying to boot back up my system. Seems to hang on this screen. Do I just need to wait longer or do I have an issue?

Thanks!

A power outage has always the danger of data corruption & loss. If you are lucky just your sd card with the OS eneded up ins some inconsistent sate. So first try should be to flash a new sd card with the latest RaspiBlitz image and see if you can get thru the recovery process. https://github.com/rootzoll/raspiblitz#downloading-the-software

Ok I will try it. Thanks for the response!

please close if resolved or abandoned


Crash when using cranelift

I'm using bevy, and after switching to cranelift, I get this error (and crash) when running my game, but only certain parts of the game.
Compute Task Pool (3)' has overflowed its stack

Can you try setting the RUST_MIN_STACK env var to 67108864? This should increase the stack size of all threads spawned by rust to 64MiB. If this works, that means you are simply using quite a bit of stack already and rustc_codegen_cranelift is simply a bit less efficient in the stack usage, pushing it over the edge into a stack overflow. It it works with a 64MiB stack, you can also try 16777216 for a 16MiB stack, which is a fair bit bigger than the default, but would waste less memory if it works.

Right, will try when I get home, it must be that..I use a lot of recursion.

Like this, in cargo/config.tom?
[target.x86_64-unknown-linux-gnu]
linker = "clang"
rustflags = ["-C", "link-arg=-fuse-ld=/usr/bin/mold", "RUST_MIN_STACK=67108864"]

No, run export RUST_MIN_STACK=67108864 once before you run the program. If you close your shell again and re-open it you will have to run this again.

Got it thanks

That worked, thanks


Publish 10/24/2022 3:30 PM PT

Learn Build status updates of commit 35ab402:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

exchange/exchange-ps/exchange/New-Label.md
:white_check_mark:Succeeded
View (exchange-ps)

exchange/exchange-ps/exchange/Set-ComplianceSecurityFilter.md
:white_check_mark:Succeeded
View (exchange-ps)

exchange/exchange-ps/exchange/Set-Label.md
:white_check_mark:Succeeded
View (exchange-ps)

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the learn.microsoft.com contributor guidesPost your question in the Learn support channel


3D export fixes and tests

Checkpointing my work in case I don't get to finish it.

added tests for at least 4 different configurations of fo3d data layout + relative vs. absolute + flatten vs. rel_dir.
Fixed a few bugs caught by tests

.mtl file in ObjMesh wasn't getting rewritten (it was only checking first asset path for each node)
use input to output asset path map to determine when we need to rewrite asset path in the fo3d file. fixes the case when flattening (no rel_dir) causes a file to be renamed from, say, pcd.pcd to pcd-2.pcd

The tests are absolutely horrendous on the eyes, I'm so sorry!! They could be refactored to something nicer but didn't have time right now.
What I would like to do if I have time:

allow asset_dir
make changes work with Teams which includes fos.resolve() and a cloud friendly os.path.relpath() if it doesn't already exist. Actually the latter probably just works but we would want to double check.
make a batch media exporter that does this in bulk instead of one at a time. Then re-use that for fos.upload_media() and download_media() in Teams so we don't have the same fragile code implemented twice. With the side benefit that export should be faster.

make a batch media exporter that does this in bulk instead of one at a time. Then re-use that for fos.upload_media() and download_media() in Teams so we don't have the same fragile code implemented twice. With the side benefit that export should be faster.

Ok I am seeing that this exists, sort of, in Teams when a cloud path is involved. I am unable to take this refactor on right now so perhaps I'll have to leave it alone for now.

@coderabbitai review


Re-enable partial replication testing (distributed queries)

After merging the DQ branch, master testing in circle continually timed-out. Instead of simply increasing the timeout (which may mask a real issue) I have disabled the "partial replication" test, which exercises actual DQ functionality. This must be re-enabled once the underlying issue is addressed.
https://github.com/influxdb/influxdb/commit/7dd61dcf147ce3f547e34ff1041d3e4b43ce7294

No longer applicable in new design.


Server

Server loading problem

I know the problem, and easy to fix. But this is not the right way to report the issue.
At least give detail info about the issue.
closing...

My issue is. Same as #95

Just try to change the source server that work for you. There is 6 different source


[SQL Migration] Premium series memory optimized SQL MI SKUs not included during SKU recommendation

Azure Data Studio Version: 1.40.2
OS Version: Windows 11 21H2

Steps to Reproduce:

Run SKU recommendation using the SQL Migration extension
Observe that premium series memory optimized SQL MI SKUs are not being recommended without the preview flag turned on, which is incorrect behavior as these SKUs were recently GAed

Does this issue occur when all extensions are disabled?: Yes/No

Fixed in the latest RC build. Closing the issue


The js-search doesn't  compatibility with Persian language

I have a site that it is Persian language but the js-search doesn't compatibility with Persian language and doesn't result when i have search any string

The default implementation of Tokenizer used by js-search is SimpleTokenizer which targets Germanic languages.
However, you can provide an alternate tokenizer implementation and js-search should work fine for you. For example:
var REGEX = /\s+/; // Split on spaces
const tokenizer = {
  tokenize(text) {
    return text
      .split(REGEX)
      .filter(
        (text) => text // Filter empty tokens
      );
  }
}
const A = {id: 'A', text: ' ایرانیان در آمریکا · خواهان یک ایران آزاد'}
const B = {id: 'B', text: 'حامی تمامی اقلیت ها · جدائی دین از دولت · جوامع'}

var search = new JsSearch.Search('id');
search.tokenizer = tokenizer;
search.addIndex('text');

search.addDocuments([A, B]);

search.search('دین'); // Should match B

If you'd be interested in contributing a Persian-friendly tokenizer as a PR I'd love to merge it into js-search so others can use it by default!
Note that this example tokenizer is super simplistic and presumably would have problems with punctuation. I'm not a native speaker so I'm not really qualified to create a tokenizer for it. However I wanted to provide a starting point for you in case you would be interested in contributing!


CentOS 8 Life cycle

It's been quite a while since the announcement of CentOS 8 EOL (Table) scheduled by December 2021.
Will Cortx stick to CentOS 7 (according to LocalVMSetup) for now while looking at other Linux distro or would go for CentOS Stream?
Consideration for Rocky Linux?

@shailesh-vaidya, can you address Harrison query as I see CentOS 8 in the roadmap but do we have any plan defined? I hope this might be a ARC call ?

Thanks @harrison-seow-seagate I agree we should probably support the latest CentOS but what are the benefits of supporting Rocky Linux over CentOS.
Thanks for suggesting this!

Hi @justinzw, the latest CentOS 8 will have no updates/maintenance by Dec 2021 (unless further migrate to CentOS Steam).
CentOS is famous for being a reliable Linux distribution (downstream of RHEL), but CentOS Stream is a development (upstream) branch of RHEL.
I would say it's generally a bad idea to use development branch for production use, also advised by Red Hat, to go for the paid RHEL if stability is needed.
Rocky Linux is intended to be 100% bug-to-bug compatible with Enterprise Linux, effectively replacing the gap left by CentOS 8 after its EOL. (Though I can't say much about it in the current state as it's still new, but it's initiated by the founder of CentOS)
I'm sure there are other people with better insights, but I would personally think CentOS Stream is probably not the best option.

I'm not sure if this is categorized as an issue, perhaps this can be moved to discussion?
However, I think it would be an issue if migration to CentOS 8 has started.

I'm not sure if this is categorized as an issue, perhaps this can be moved to discussion?
However, I think it would be an issue if migration to CentOS 8 has started.

It will be a discussion as the migration to CentOS 8 yet not started


New release?

Seems like there have been a lot of improvements lately, but the last release is from Aug 12, over 3 months ago.
Are there any plans to make a new release soon?
(no pressure, I'll work off master if necessary, but I prefer to wait for a release if it's coming soon)

Yeah I'll cut another release today. I am probably going to continue more intensive work for a while, but I can always make another release.

Cool, thanks!

https://pypi.org/project/pyanalyze/0.4.0/#description

Just a quick note, it isn't mentioned in the notes but pyanalyze.value.UnresolvedValue is no longer available. fwiw I replaced it in my code with AnyValue and it works for my purposes.

Oh yes, I didn't mention that as explicitly because there was only meant to be one instance of the class. Added it in #274.


Add footer

Add the footer and style it.

Good job @TimmyChan99, you can go ahead and merge it to development.


Update vegas.js

TypeError: Cannot read property 'remove' of null.

Thanks a lot Fausto! :)
Could you please edit some changes :

No need to comment the patch in the code
Follow the code convention and use the long form of condition with brackets { }
Add a space after the condition block

Also could you add a better commit message with "Fix ...".
Thanks ago for your contribution.

Thanks for the tips, it was my first pull request and I was not sure what to write on it.
What I thought was that the code speaks by himself.
For the next time I will do better.

For sure I can do it!


Image overlay improvements

Change image
Load image from file
Resize image with screen size

Configuration for size and position

Configuration per failure type
Break threading up to avoid long uninterruptable periods
Enable and disable per trigger

Also address #101


modifed the driver name to be same as definition in code

What this PR does / why we need it:

modifed the driver name to be same as definition in code

Which issue this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged): fixes #
Special notes for your reviewer:
Release note:

Coverage remained the same at 37.948% when pulling de0a1c3b44b53cae3c49e820c6f12ccfed3acd51 on xxwjj:driver_name into 921f728cd976c3204d75ef0013f0aa4a035edd31 on opensds:development.


Add block detector

Fixes #3

I don't think this is necessary any more because of https://github.com/square/gradle-dependencies-sorter


[suggestion] any workaround for GamePass version?

Basically title. Can’t edit hex of GamePass version .exe.

I don't have the GamePass version sadly, but I will try to update it as soon as possible for your version, I will let you know here.

Instead of editing the exe, it is possible to just override it with the StarfieldCustom.ini.
It was recommended to make the ini read only after editing.
So maybe create an ini generator instead of a patcher.
Found here:
reddit
But Hex editing isn't necessary, infact the value you edit by hex editing is the default value which is applied by the following setting:

Documents\My Games\Starfield\StarfieldCustom.ini

[Display]
fWideAspectLimit=3.55556

Should work for all Game editions.

And more settings for FOV etc...
found here:
reddit
 FOV fix, create a StarfieldCustom.ini in Document/My Games/Starfield of game directory and add

[Display]
fDefault1stPersonFOV=100
fDefaultFOV=100
fDefaultWorldFOV=100
fFPWorldFOV=100.0000
fTPWorldFOV=100.0000

[Camera] fDefault1st
PersonFOV=100
fDefaultFOV=100
fDefaultWorldFOV=100
fFPWorldFOV=100.0000
fTPWorldFOV=100.0000

Make sure to change the value from 100 to your desired FOV.

hello, yes I am aware of this, since few days ago, I will edit this tool to use this method


Investigate Proof of Burn Consensus

https://en.bitcoin.it/wiki/Proof_of_burn

I don't like this for SushiChain


WebRtc detection in Bowser doesn't work

I read in the doc that webrtc detection will not before owr.js will be injected.
So I have following function for detecting the webrtc features in bowser
var isWebRTCSupported;
var detectWebRTCBowser = function()
{
 isWebRTCSupported = (!!window.webkitRTCPeerConnection || !!window.mozRTCPeerConnection)
if (isWebRTCSupported)
 {
    return;
 }
else
 {
   setTimeout(detectWebRTCBowser , 1000);
 }
}
$(window).load(function () {
 detectWebRTCBowser();
});

It doesn't work. If it can't detect webrtc from the first time it'll never detect it. And if it's detectabe it'll detected from the first time.
Also what is important I think is that: when you launch bowser for the first time and load the page it never detects webrtc. If to refresh the page it'll detect it. And all ongoing sessions it'll work, untill you realunch the bowser.
How to correctly implement webrtc detection in bowser?

What I just discovered is that owr.js is not injected sometimes. Especially looks like this is happens after bowser crashes and you launch it again. Can I just inject http://localhost:10717/owr.js to my html myself? Or how to deal with this?

I would recommend having a look at this PR https://github.com/EricssonResearch/bowser/pull/61
We are moving to WKWebView which makes the JavaScript injection of owr.js robust (there is a proper API for injection).

With this PR webrtc detection works fine. I merged it locally with current master branch. But now video sending and receiving doesn't work. I see alot of HTTP GETs to <IP_ADDRESS>:21428/__JAflv/{alotofsymbols} when sending video from bowser. Is it ok?
Also When I try to send video from safari wirth plugin and latest daemon from openwebrtc I got:
ERROR: owr_transport_agent.c:1522:prepare_transport_bin_send_elements: assertion failed: (scream_queue)
Abort trap: 6

That has been fixed in a newer version of OpenWebRTC. Could you please update and re-build?

The Issue specified in the title is fixed. If you have other problems please open a new Issue. Closing, thanks.


your shell /bin/bash can't handle traditional UNIX syntax for redirection

Hello,
I'm on FreeBSD trying to get syntastic to work, it works great on other systems I use, but FreeBSD is being stubborn.
.vimrc set shell=/bin/csh
root@mb ~# echo $SHELL /bin/csh
I've done some searching on this and found a previous issue here
But I've tried this and still no luck... Any suggestions?
Thanks, and thanks again for syntastic!

Please read :h syntastic-csh.

Thank you @lcd047
I'm a silent lurker to your many, many, responses to these issues and you're brilliant!
I'll go read now.

I set
let g:syntastic_shell = "/bin/sh"
and
.vimrc set shell=/bin/sh
But still,

your shell /bin/bash can't handle traditional UNIX...

I'm just kind of puzzled here because it almost seems like this has nothing to do with Syntastic and more like vim is ignoring my shell settings

Please open your test file, set g:syntastic_debug to 1, run the checker, run :mes, and post the output.

Okay it's fixed, I had duplicate conflicting shell settings
let g:syntastic_shell = "/bin/sh"
let g:syntastic_shell = "/bin/bash"
blushing
Thank you for helping me get that sorted it out. I'll close this issue now. Have a wonderful weekend and thank you again for syntastic!


[Feature] Support mmcls with NPU backend.

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
Added ascending device support in mmcv.
Modification

The main modification points are as follows:

In mmcls/apis/train.py, We added an NPU device in the DDP scenario, and the mixing accuracy is enabled by default when using the NPU
In ``mmcls/utils/distribution.py```, We have added DP and DDP classes for NPU
In ``mmcls/datasets/samplers/distributed_sampler.py```, We added device judgment to make the broadcast within the sync_random_seed function execute correctly on the npu

BC-breaking (Optional)
A new mmcv containing the NPU background needed.
Use cases (Optional)
We tested config/resnet/resnet50_8x32_in1k.py with Acc@1: 76.4
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.
[ ] 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.
[ ] 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.王姜奔 seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


add commented reviewers, remove global variables

This consists of two commits, please look at each individual commit for summaries.

@brendanashworth merge pending conflict resolution.

@deekoder PTAL, rebased, fixed conflicts and fixed a little new error.

Thanks!


Add support for OS version in Appetize options

Checklist

[x] I've run bundle exec rspec from the root directory to see all new and existing tests pass
[x] I've followed the fastlane code style and run bundle exec rubocop -a to ensure the code style is valid
[x] I've read the Contribution Guidelines
[x] I've updated the documentation if necessary.

Motivation and Context
By default, Appetize launches with the iOS version set to iOS 8.0. Creating an Appetize URL via Fastlane for an app that targets a more recent iOS version requires the user to manually select the iOS version in the Appetize webpage for the app to work.
For apps that target more recent iOS versions, the osVersion parameter allows an Appetize URL to be created with the correct iOS version. This PR allows this parameter to be specified from Fastlane.
Description
Adds an os_version parameter to appetize_viewing_url_generator.rb.

CLA signed

CI seems to be failing.
Could you fix this offense? @solon
$ bundle exec rubocop -a

Offenses:

fastlane/lib/fastlane/actions/appetize_viewing_url_generator.rb:30:1: C: Style/TrailingWhitespace: Trailing whitespace detected.

905 files inspected, 1 offense detected

@giginet fixed 🔧


Date formats on Dashboard aren't consistently honoring regional config

My setup:
Dates: dd-Mmm-YYYY
Time: HH:mm
Resources view (correct):

Structured Logs/Traces timestamp:

Metrics:

Likely because of this US-centric hard-code format: https://github.com/dotnet/aspire/blob/1cbea342b307da55f83aa001ef6bce7a6fbaf9d6/src/Aspire.Dashboard/Otlp/Model/OtlpHelpers.cs#L47

Consider adding time format options in the future.  Honor the date format

The challenge here is wanting the user's preferred time format, but to also show milliseconds on the time span.
From https://learn.microsoft.com/en-us/dotnet/standard/base-types/how-to-display-milliseconds-in-date-and-time-values:

A problem with defining a complete custom format specifier that includes the millisecond component of a date and time is that it defines a hard-coded format that might not correspond to the arrangement of time elements in the application's current culture. A better alternative is to retrieve one of the date and time display patterns defined by the current culture's DateTimeFormatInfo object and modify it to include milliseconds. The example also illustrates this approach. It retrieves the current culture's full date and time pattern from the DateTimeFormatInfo.FullDateTimePattern property and then inserts the custom pattern fff along with the current culture's millisecond separator. The example uses a regular expression to do this operation in a single method call.

Fix in review with https://github.com/dotnet/aspire/pull/2135


[Contrib] Add MKL DNN option

Thanks for contributing to TVM!   Please refer to guideline https://docs.tvm.ai/contribute/ for useful information and tips. After the pull request is submitted, please request code reviews from Reviewers by @ them in the pull request thread.

@soiferj No. If the USE_BLAS is OFF, we won't compile MKLDNN ops. See here in the cmake
https://github.com/apache/incubator-tvm/pull/4323/files#diff-9e0c77365976363b16f3bdc58f95fb38R59
One proposal is that I remove (NOT USE_BLAS STREQUAL "none") in the condition but I won't add ${CBLAS_CONTRIB_SRC} into src list if USE_BLAS is OFF. So if we have conv2d contrib using MKLDNN in the future, we can still include that file in the src list.
How does this sound?

I see, I think I was looking at an old version. I think that solution sounds good.

Thanks @icemelon9 @TaoLv @soiferj !


Update the documentation regarding Let's Encrypt

With the additions from Islandora-Devops/isle-dc#228 requesting
certificates via ACME / Let's Encrypt has changed, and should be easier
for users to utilize.
Purpose / why
Updated the documentation relating to requesting SSL Certificates through Let's Encrypt and Traefik.
https://islandora.github.io/documentation/installation/docker-custom/#using-lets-encrypt-instead-of-certificate-files
What changes were made?
Updated text to reflect only having to change environment variables in the .env file.
Verification
If Islandora-Devops/isle-dc#228 gets merged, ACME Certificate generation is controlled by a few simple variables. Also debugging Traefik would be also controlled by a variable.
Interested Parties
@Islandora/documentation
@Islandora/8-x-committers_

Checklist

Pull-request reviewer should ensure the following

[ ] Does this PR link to related issues?
[ ] Does the proposed documentation align with the Islandora Documentation Style Guide?
[ ] Are the changes accurate, useful, free of typos, etc?

Person merging should ensure the following

[ ] Does mkdocs still build successfully? (This is indicated by TravisCI passing. To test locally, and see warnings, see How To Build Documentation.)
[ ] If pages are renamed or removed, have all internal links to those pages been fixed?
[ ] If pages are added, have they been linked to or placed in the menu?
[ ] Did the PR receive at least one approval from a committer, and all issues raised have been addressed?

With https://github.com/Islandora-Devops/isle-dc/pull/228 being merged I suspect that these documentation change can be merged now.
@misilot I assume that are no changes needed to your docs and they can go in as is since the https://github.com/Islandora-Devops/isle-dc/pull/228 merge ?

@ysuarez, yes I believe it is good to go. The PR was merged as is without any changes.

Let me rebase it, so it's a clean merge

No, thank you @misilot


Bayesian RSA needs example and a new version dealing with spatial noise correlation

Working on them now.
Other issues that I need to work on later: add read_spm to utils.ReadDesign

@lcnature Please add an example as soon as possible.
I should have delayed the PR, but I did not realize it. I am sorry.

Actually it works better this way. Because I changed the code so much, I also need to modify my previous code which calls brsa. With brsa in the package, it is easy to see what needs to be changed.

That is good to hear. However, we should not have code without examples.


Improve visibility of error messages

Is your proposal related to a problem?

When ever I have validation errors when trying to save a page (or other model) in the Wagtail admin, I find it hard to identify the field with the error.
I believe this is particularly hard for me as I have a form of "deuteranomalia" which causes "red" for me to be less saturated than for other people. As a result, the small red error text appears basically grey to me and is hard to distinguish from the rest of the page content.
On simple field like text inputs this is less annoying since the entire field changes its styling. But, especially on chooser fields there is no indication apart from the small text.
Describe the solution you'd like

I could imagine the style to be updated in the following order of usefulness (most to least):

Add a icon at the beginning of the error text (something like this maybe ❌)
Use a bold font.
Increase the font size.
Use a brighter red.

I understand that might be ugly from a design perspective, but this is only visible when something is amiss and important information needs to be transported to the user.
Describe alternatives you've considered

Not much I can do but slowly scroll the pages.
Additional context

Here is an example comparison:

Here is the changed .error-message class I have used:
.error-message {
    color: #d93030;
    font-weight: bold;
    font-size: small;
}

Thank you for the very solid initial report @tbrlpld, and thank you to @Wicked7000 for making the PR. This will be released in v2.16, due in a few weeks.


Fix to use UTF-8 instead of US_ASCII

Description
Fix to use Charsets.UTF-8 instead of Charsets.US_ASCII.
If there is no charset in the Content-Type header value, Charsets.US_ASCII is used and the multibyte character sets is garbled.
https://github.com/kittinunf/fuel/blob/823df71af8d9d70ed477d5d22eb0548045b95fad/fuel/src/main/kotlin/com/github/kittinunf/fuel/core/BodyRepresentation.kt#L29
I think it would be better to use Charsets.UTF-8. because the documentation says:

https://fuel.gitbook.io/documentation/core/fuel#blocking-responses
The default charset is UTF-8.

Fixes #815
Type of change
Check all that apply

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

How Has This Been Tested?
I added a test case with multibyte character sets.
Checklist:

[x]  I have performed a self-review of my own code
[ ]  I have commented my code, particularly in hard-to-understand areas
[ ]  I have made corresponding changes to the documentation, if necessary
[ ]  My changes generate no new compiler warnings
[x]  I have added tests that prove my fix is effective or that my feature works
[ ]  New and existing unit tests pass locally with my changes
[ ]  Inspect the bytecode viewer, including reasoning why

I'm getting this error in Travis CI.
Could not authorize build request for...

Is there anything I should do on my side?

Thank you for the detailed explanation to me. I understand now that it is not a bug.
Unfortunately, UTF-7 is not supported by the JDK and cannot be specified.
https://docs.oracle.com/en/java/javase/11/docs/api/java.base/java/nio/charset/Charset.html
So, the best I can do at this point is to remember to set the Content-Type header value with charset=UTF-8.
I hope RFC 6657 will be approved.
I'm going to close this PR for useless fixes. Thank you.

@aytdm You'll want US-ASCII. It's "equivalent" to the proposed UTF-7 (that didn't make it), but implemented before the UTF standard proliferated with a similar charset, but different positions.
But yes, setting charset=UTF-8 is your best bet! :D

Thank you again :)


Switch cache action to use the cache node package

Biggest change is in setCacheState. We are now only saving cache key not the entire artifact cache object since cacheKey what we get back from saveCache.

Let's add a note in the README pointing to the package in the toolkit

Well, will Zstd support be removed?

@imbsky See https://github.com/actions/toolkit/pull/469 for the zstd fixes.

(I just checked the PR 🙂)


Custom sorter issue

Hello,
First of all, thank you for this amazing grid, I use it all the time.
I'm implementing multi column sort and looks like there is an issue with jsGrid("option", "data") when using custom sorter.
There is fiddle to reproduce the issue: https://jsfiddle.net/yleshchuk/cbv88kya/
Reproducible only in Chrome, Firefox works fine.
As you can see when I use $("#jsGrid").jsGrid("option", "data"), it returns invalid list of items with duplicated item instead some valid item.
I know, this can be fixed by using external array with items, but I'm filing grid dynamically and one more place to sync items does not sound as good solution.

That looks bizarre indeed. Actually $("#jsGrid").jsGrid("option", "data") just returns the reference to the arrays passed from loadData.
In this fiddle we see, that this happens even w/o jsgrid:
https://jsfiddle.net/tabalinas/08sy8z5q/
Any thoughts?

No answer.


Int 2399 maint

JIRA: https://jira.springsource.org/browse/INT-2399.
Refactor ReplyRequiredException to MessageHandlingException.

Looks like these changes were handled by the previous cherry-pick commit from the associated PR for master.

reopened in order to merge this after all... turns out the exception type was a 2.1 addition


chore: remove include/omit porting notes

See this Zulip discussion.

maintainer merge

cf leanprover/lean4#2452

Thanks! Once it clears CI, please summon the bot.
bors delegate+

bors r+


Task: Open a PR here from your notebook branch

It is easier to review if you open a pull request in this repo from your other the-first-notebook branch. Having a PR open also serves as a reminder for us.

Done


Use stable nixpkgs version (23.11)

Problem: some old unstable nixpkgs is used in flake.nix, which is potentially insecure.
Solution: bump the version of nixpkgs, and a few more flakes.
Explain how you tested your changes:

[ ] Test build on MacOS
[ ] Test build on Linux

Checklist:

[x] Dependency versions are unchanged

Notify Velocity team if dependencies must change in CI

[x] Modified the current draft of release notes with details on what is completed or incomplete within this project
[x] Document code purpose, how to use it

Mention expected invariants, implicit constraints

[x] Tests were added for the new behavior

Document test purpose, significance of failures
Test names should reflect their purpose

[x] All tests pass (CI will check this if you didn't)
[x] Serialized types are in stable-versioned modules
[x] Does this close issues? None

!ci-build-me

!ci-build-me

!ci-build-me

!ci-build-me

!ci-build-me

Why not use unstable?

!ci-build-me

!ci-build-me

!ci-build-me

Can confirm it works on NixOS as is. Have some issues on MacOS. Waiting for others with Apple Silicon to chime in to see if it's local or more global.

!ci-build-me

!ci-toolchain-me

!ci-build-me

!ci-build-me

Working well for me too!

!approved-for-mainnet


docs: add getting started guide

:books: Documentation preview :books:: https://meltano-edk--33.org.readthedocs.build/en/33/

pre-commit fix

pre-commit.ci fix

pre-commit.ci autofix


Update stalebot.yml

updating the user message based on feedback. end users to this repo cannot remove a label.

what was the feedback?

what was the feedback?

users in the repo cannot remove a label, like the stalebot message suggested to do. i updated the message to remove that statement


dartdevc usage errors scroll off the screen

From @devoncarew on July 1, 2016 16:17
When I have an error in my cli invocation, the usage text printed by dartdevc scrolls the useful bit of the error off the screen. Perhaps show a very truncated version of the usage in some instances?
Imported file "package:usage/usage.dart" was not found as a summary or source file. Please pass in either the summary or the source file for this import.

Usage: dartdevc compile [arguments]
-h, --help                             Print this usage information.
-o, --out                              Output file (required)
    --module-root                      Root module directory. Generated module paths are relative to this root.
    --build-root                       Root of source files. Generated library names are relative to this root.
    --[no-]summarize                   emit an API summary file
                                       (defaults to on)

    --[no-]source-map                  emit source mapping
                                       (defaults to on)

    --[no-]source-map-comment          adds a sourceMappingURL comment to the end of the JS,
                                       disable if using X-SourceMap header
                                       (defaults to on)

    --modules                          module pattern to emit

          [es6]                        es6 modules
          [legacy]                     a custom format used by dartdevc, similar to AMD
          [node]                       node.js modules (https://nodejs.org/api/modules.html)

    --[no-]emit-metadata               emit metadata annotations queriable via mirrors
    --[no-]closure-experimental        emit Closure Compiler-friendly code (experimental)
    --[no-]destructure-named-params    Destructure named parameters
    --[no-]unsafe-force-compile        Compile code even if it has errors. ಠ_ಠ
                                       This has undefined behavior!

    --[no-]hoist-instance-creation     Hoist the class type from generic instance creations
                                       (defaults to on)

    --[no-]hoist-signature-types       Hoist types from class signatures
    --[no-]name-type-tests             Name types used in type tests
                                       (defaults to on)

    --[no-]hoist-type-tests            Hoist types used in type tests
                                       (defaults to on)

-s, --summary                          summary file(s) to include
    --dart-sdk                         Dart SDK Path
    --dart-sdk-summary                 Dart SDK Summary Path
-p, --package-root                     Package root to resolve "package:" imports
                                       (defaults to "packages/")

    --url-mapping                      --url-mapping=libraryUri,/path/to/library.dart uses
                                       library.dart as the source for an import of of "libraryUri".

    --package-paths                    use a list of directories to resolve "package:" imports

Run "dartdevc help" to see global options.

Copied from original issue: dart-lang/dev_compiler#598

So the high level point about DDC now: it's meant to be called by a build tool. It's not going to be super friendly to use directly, because of modular compilation. It would be sort of like calling "clang" directly for each .o file you're building. Works for a simple hello world, but doesn't really scale :).  (See clang --help for a big list! It's 376 lines on my version.)
That said, there's a lot we can do to improve command line UX:

we need actual manual style documentation hosted somewhere. That takes pressure off --help to document things. Some *nix tools simply print flags, and leave documentation to "man".
the flag names are uniformly terrible, almost no flags have a user-friendly name
probably most of those flags should be hidden (especially experimental ones)
the "compile command" stuff needs to go (it's supported only for backwards compat)

At the stage we're at in development, the reality is folks want to add flags. I haven't had any luck encouraging folks to be thoughtful about the flag UX in code reviews. So I've kind of made peace with it for now. What we could do is review them when we get closer to 1.0, and take a coherent design view at whatever is left. Then combine that with a user-facing documentation effort for DDC.

if it fails during compilation [...] printing usage as part of the error tends to drown out the actual error.

eeeeep, yeah, good catch. we can make that better. Probably because we're (ab)using UsageException from the args package

From @devoncarew on July 1, 2016 20:19

it's meant to be called by a build tool

Cool, I totally get that. What I was doing yesterday was trying to get the cli args together (https://github.com/flutter/atom-flutter/blob/master/tool/grind.dart#L108) that I would then roll back into a build system of some sort. But even puzzling out the args I think could use a little bit better feedback. Specifically:

if the tool fails parsing the args, printing the usage makes sense
if it fails during compilation (Imported file "package:usage/usage.dart" was not found as a summary or source file...), printing usage as part of the error tends to drown out the actual error.

we need actual manual style documentation hosted somewhere

+100 :) a walk-though of compiling a hello-world app would be very useful.

should be fixed in https://dart-review.googlesource.com/c/42881/


fix: remove requestAsBrowser in favor of got-scraping

Fixes #34

[x] remove compatibility layer in requestAsBrowser
[ ] remove got export in got-scraping or replace it with gotScraping

[ ] use that in the docs

[ ] adjust all the examples and jsdocs
[ ] write down small migration guide about the differences between requestAsBrowser and using got-scraping directly

The code is still quite messy. Needs a refactoring (should be a separate PR) - the context.response is expected to be IncomingMessage, however that isn't right with Got ideology. Got wraps parts of ClientRequest and IncomingMessage into Got's Request. For example, in order to access the original IncomingMessage, you need request.response. So, in order to get the headers, request.response.headers.
To solve this, there has been added addResponsePropertiesToStream which turns Got's Request instance to look like IncomingMessage, overwriting some properties along the way. Oh, and it gets casted from Request to IncomingMessage.


chatterino2: 2.3.4 -> 2.3.5

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://repology.org/metapackage/chatterino2/versions.
meta.description for chatterino2 is: "A chat client for Twitch chat"
meta.homepage for chatterino2 is: "https://github.com/Chatterino/chatterino2"
meta.changelog for chatterino2 is: "https://github.com/Chatterino/chatterino2/blob/master/CHANGELOG.md"
Updates performed

Version update

To inspect upstream changes
Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
Warning: no invocation of /nix/store/grgmgcqjpwizdm6b61svca4dkilpp1z2-chatterino2-2.3.5/bin/chatterino had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/grgmgcqjpwizdm6b61svca4dkilpp1z2-chatterino2-2.3.5/bin/.chatterino-wrapped had a zero exit code or showed the expected version
0 of 2 passed binary check by having a zero exit code.
0 of 2 passed binary check by having the new version present in output.
found 2.3.5 with grep in /nix/store/grgmgcqjpwizdm6b61svca4dkilpp1z2-chatterino2-2.3.5
found 2.3.5 in filename of file in /nix/store/grgmgcqjpwizdm6b61svca4dkilpp1z2-chatterino2-2.3.5

Rebuild report (if merged into master) (click to expand)

2 total rebuild path(s)

1 package rebuild(s)

1 x86_64-linux rebuild(s)
1 x86_64-darwin rebuild(s)

First fifty rebuilds by attrpath
chatterino2

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/grgmgcqjpwizdm6b61svca4dkilpp1z2-chatterino2-2.3.5 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A chatterino2 https://github.com/r-ryantm/nixpkgs/archive/d78bf7598ac0da8d58a55b11e6f3d25f05786217.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/grgmgcqjpwizdm6b61svca4dkilpp1z2-chatterino2-2.3.5
ls -la /nix/store/grgmgcqjpwizdm6b61svca4dkilpp1z2-chatterino2-2.3.5/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

chatterino2

Maintainer pings
cc @rexim for testing.

Result of nixpkgs-review pr 168126 run on x86_64-linux 1

1 package built:

chatterino2

Builds and runs fine for me.


⚠ SolarOscp has degraded performance

In 35b843a, SolarOscp ($SOLAROSCP_URL) experienced degraded performance:

HTTP code: 200
Response time: 401 ms

Resolved: SolarOscp performance has improved in c0e0a7f after 9 minutes.


Add Jersey Bean Validation Support

See https://jersey.java.net/documentation/latest/bean-validation.html for details
about the Bean Validation support in Jersey. It enables the use of Java validation annotations like @NotNull, @Min, or @Email in the context of JAX-RS and Jersey.
Merging this could probably fix #625 and #633 (as both, the issue and the PR, are now outdated anyway).

Coverage increased (+0.01%) when pulling aaa240ee08d399a583f4f228a4be750503399675 on joschi:bean-validation into 8a1d9ca293e4d5d5f1c37802d5c7cf43e7f0ef05 on dropwizard:master.

I'm OK with this, are we comfortable with adding a new dependency? @carlo-rtr @ryankennedy if one of you 2 +1s let's put it in

I assume the exclusion of hibernate-validator is because we're pulling it in as part of dropwizard-validation and don't want Jersey's bean validation bits to stomp the version we're pulling? Is that going to be safe to do going forward? Is there any way to move these bits to dropwizard-validation instead so all the validation-related bits stay in one place? I assume removing hibernage-validator from dropwizard-validation would suddenly cause some awkward runtime and, maybe, test missing class failures way over in dropwizard-jersey. Maven exclusions make me nervous for long-term maintenance.
I'm a little confused as to why people are POSTing empty bodies, having their resources take an argument, and complaining when it says foo = null is not a valid foo. It's triggering my smell test. Like…why would you do that? Especially the one talking about an empty POST for a login request being a valid request. I'm not sure how opinionated to be about that one. But I'm not sure that's a problem I'd aim to solve.
Out of curiosity, why aren't these validations just working right now? Is this for validation annotations in the resource method parameter list (i.e. Foo getFoo(@NotNull FooRequest req))? I assume validation annotations in the representation class (i.e. class FooRequest { @NotNull String id; }) are already working since we advertise that in the docs.
I'm fine with the new dependency if we don't see a way we'd deeply regret adding this feature down the road.

@joschi did you want to respond to @ryankennedy before someone merges this in?

I think the validations are useful if you aren't using a bean. There are many annotations, that make more sense than NotNull. http://docs.oracle.com/javaee/7/api/javax/validation/constraints/package-summary.html
I suspect the exclusion in org.hibernate.hibernate-validator is to avoid dependency divergence. I doubt trying to use jersey module without providing org.hibernate.hibernate-validator would work. Perhaps we should also explicitly add a dependency on org.hibernate.hibernate-validator in dropwizard-jersey. This way both dropwizard-jersey & dropwizard-validation have the right deps. We can ensure version consistency by moving the version to a property field defined in the parent pom

@joschi did you want to address @carlo-rtr 's comment and we'll add this into 0.9.0?

Ah, sorry for not responding. Completely overlooked the replies on this PR.

I assume the exclusion of hibernate-validator is because we're pulling it in as part of dropwizard-validation and don't want Jersey's bean validation bits to stomp the version we're pulling?

Yes, exactly. In the end it's excluded to make the Maven Enforcer plugin happy. The alternative would be to add Hibernate Validator to the dependencyManagement section of the parent POM to enforce a certain version of it. We should probably do that anyway.
This being said, it's rather unlikely that we remove Hibernate Validator in the foreseeable future because it's quite deeply embedded in dropwizard-validation.

Is there any way to move these bits to dropwizard-validation instead so all the validation-related bits stay in one place?

dropwizard-jersey pulls in dropwizard-validation (see pom.xml) and this feature is tightly coupled with Jersey. It's completely useless without dropwizard-jersey, so I assumed putting it in there is the right place™.

Out of curiosity, why aren't these validations just working right now? Is this for validation annotations in the resource method parameter list (i.e. Foo getFoo(@NotNull FooRequest req))?

Yes, exactly. Some annotations (namely @Valid and @Validated) can already be used in Resource classes, others are currently limited to value classes.
If the addition of this feature doesn't impose a large performance overhead (which we should test), I don't see a reason not to add it by default.

Cool, thanks for the explanation Jochen. I'm a +1.
Ryan
On Wed, Apr 15, 2015 at 6:45 AM, Jochen Schalanda<EMAIL_ADDRESS>wrote:

Ah, sorry for not responding. Completely overlooked the replies on this PR.
I assume the exclusion of hibernate-validator is because we're pulling it
in as part of dropwizard-validation and don't want Jersey's bean validation
bits to stomp the version we're pulling?
Yes, exactly. In the end it's excluded to make the Maven Enforcer plugin
happy. The alternative would be to add Hibernate Validator to the
dependencyManagement section of the parent POM to enforce a certain version
of it. We should probably do that anyway.
This being said, it's rather unlikely that we remove Hibernate Validator
in the foreseeable future because it's quite deeply embedded in
dropwizard-validation.
Is there any way to move these bits to dropwizard-validation instead so
all the validation-related bits stay in one place?
dropwizard-jersey pulls in dropwizard-validation (see pom.xml
https://github.com/dropwizard/dropwizard/blob/58c4d52ce212d05b691e80e5ff687c92a24d510f/dropwizard-jersey/pom.xml#L20-24)
and this feature is tightly coupled with Jersey. It's completely useless
without dropwizard-jersey, so I assumed putting it in there is the right
place™.
Out of curiosity, why aren't these validations just working right now? Is
this for validation annotations in the resource method parameter list (i.e.
Foo getFoo(@NotNull https://github.com/NotNull FooRequest req))?
Yes, exactly. Some annotations (namely @Valid and @Validated) can already
be used in Resource classes, others are currently limited to value classes.
If the addition of this feature doesn't impose a large performance
overhead (which we should test), I don't see a reason not to add it by
default.
—
Reply to this email directly or view it on GitHub
https://github.com/dropwizard/dropwizard/pull/842#issuecomment-93406630.


Support for blockquote element

I love this lightweight editor. We are using it in multiple projects. I was wondering if there is a way to add blockquote element in the editor.

You can’t. But you can fake it → https://jsbin.com/tovubih/edit?output
The method above will wrap your selected text with .

@tovic Thanks you for your response. It's certainly helpful.
I just love this simple library. Are you still maintaining this project? Any feature coming up?
I also tried searching to you on Twitter in order to get in touch for help.
One more help needed - Can you please point me to a place where you took the SVG path of other icons of RTE? They seemed to be fit for viewbox 0 0 16 16. I am having hard time finding the SVG suitable for this viewbox.

Are you still maintaining this project?

Only to fix the bugs. I don’t think will add more features on this small project.

I also tried searching to you on Twitter in order to get in touch for help.

I don’t tweet a lot. It’s just too short and looks spammy to me. You can contact me from everywhere else. Just try it.

Can you please point me to a place where you took the SVG path of other icons of RTE?

They are from Material Design Icons → https://materialdesignicons.com

Thanks a lot for clarifying.
You've been awesome.


Compatibility with .Net 4.6.1?

Hi,
Am having an issues with conflicts between StringInterpolationBridge and the actual available classes in .Net framework 4.6.1
Error CS0433: The type 'FormattableString' exists in both 'StringInterpolationBridge, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=null' and 'mscorlib, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=b77a5c561934e089' (174, 27)
Given that Dapper.FastCrud is dependant on StringInterpolationBridge I cant remove it.
Any idea what I can do? I would prefer not to downgrade to 4.5.2 unless absolutely required.
Regards,

Actually, I just had a look at the NuSpec. The dependency should be  only on Dapper.
<group targetFramework=".NETFramework4.6">
        <dependency id="Dapper" version="[1.50.2, )" />
</group>

Hmm, l think I have to figure this one out.  Will close this issue once I document what I did so that it can help anyone else  who might face this :)

Easy fix.

Shutdown VS
Delete all packages within  the packages folder
Type in Package Manager Console  Update-Package –reinstall

Hope it helps.
Am closing this ticket now.


[FLOC-3520] change docs nav to be inline with current website

Fixes FLOC-3520

Looks good, thanks @msh100
Tested all links work, and matches the rest of the website. Please merge.


hwinfo: 21.72 -> 21.73

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://repology.org/metapackage/hwinfo/versions.
meta.description for hwinfo is: "Hardware detection tool from openSUSE"
meta.homepage for hwinfo is: "https://github.com/openSUSE/hwinfo"
meta.changelog for hwinfo is: ""
Updates performed

Version update

To inspect upstream changes

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS

The tests defined in passthru.tests, if any, passed

/nix/store/5560p350gwc6xa2idjlfa4j90laj7s36-hwinfo-21.73/bin/hwinfo passed the binary check.

/nix/store/5560p350gwc6xa2idjlfa4j90laj7s36-hwinfo-21.73/bin/check_hd passed the binary check.

/nix/store/5560p350gwc6xa2idjlfa4j90laj7s36-hwinfo-21.73/bin/convert_hd passed the binary check.

/nix/store/5560p350gwc6xa2idjlfa4j90laj7s36-hwinfo-21.73/bin/getsysinfo passed the binary check.

Warning: no invocation of /nix/store/5560p350gwc6xa2idjlfa4j90laj7s36-hwinfo-21.73/bin/mk_isdnhwdb had a zero exit code or showed the expected version

3 of 5 passed binary check by having a zero exit code.

3 of 5 passed binary check by having the new version present in output.

found 21.73 with grep in /nix/store/5560p350gwc6xa2idjlfa4j90laj7s36-hwinfo-21.73

found 21.73 in filename of file in /nix/store/5560p350gwc6xa2idjlfa4j90laj7s36-hwinfo-21.73

directory tree listing: https://gist.github.com/80920ed9fbc8a670f6b8c8e0bf2ddfb8

du listing: https://gist.github.com/bf0966ac34c02ae035aaa46d3c4906de

Rebuild report (if merged into master) (click to expand)

3 total rebuild path(s)

1 package rebuild(s)

1 x86_64-linux rebuild(s)
1 i686-linux rebuild(s)
0 x86_64-darwin rebuild(s)
1 aarch64-linux rebuild(s)

First fifty rebuilds by attrpath
hwinfo

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/5560p350gwc6xa2idjlfa4j90laj7s36-hwinfo-21.73 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A hwinfo https://github.com/r-ryantm/nixpkgs/archive/d67443c742b3a20a17916af2365f23209621fb03.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/5560p350gwc6xa2idjlfa4j90laj7s36-hwinfo-21.73
ls -la /nix/store/5560p350gwc6xa2idjlfa4j90laj7s36-hwinfo-21.73/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

hwinfo

Maintainer pings
cc @bobvanderlinden for testing.

Result of nixpkgs-review pr 121024 at d67443c7 run on x86_64-linux 1

1 package built successfully:

hwinfo

2 suggestions:

warning: unclear-gpl
gpl2 is a deprecated license, please check if project uses gpl2Plus or gpl2Only and change meta.license accordingly.
Near pkgs/tools/system/hwinfo/default.nix:35:5:
   |
35 |     license = licenses.gpl2;
   |     ^

warning: patch-phase
patchPhase should not be overridden, use postPatch instead.
Near pkgs/tools/system/hwinfo/default.nix:14:3:
   |
14 |   patchPhase = ''
   |   ^


Different usernames can see the same stored files if same mnemonic

This situation should probably not exist, so will label as bug.
Restoring account with same mnemonic but under different usernames, the same data is seen under Fairdrive app.
E.g., users:
fairos-demouser2
fairos-demouser3
Can see the same folder, created under demouser2

this is bad, should not happen

ok, now i understand, this is by design, same key for all users, same derivation from them. The key is important. Even if you provide different username, mnemonic will be the same, address will be the same and all derived keys are same. This is a feature. @asabya mentioned this a while ago. Closing.


Static Class Mapping

Hi,
I was just wondering the  reason behind not having static class mapping over dynamic responses, which is far more error prone than classes. Also, the library can have API links as constant pushed to somewhere in other class and utilized RestSharp like libraries for making the calls...

@sarthak-k Can you explain what you meant by "static class mapping"?
Using classes as enums for API links will be a cleaner way to do it. We will consider it for the next release.
Also, when we started this project the idea was to keep it as easy as possible to port to other platforms like .Net core, Xamarin etc. So we didn't use any external dependencies in this project. Everything including the WebSockets uses the classes from .Net framework.

Static class mapping is nothing but POCO objects for JSON Mapping. The problem with current implementation is returning dynamic<string, object> I believe, it does not make sense to have a dynamic object and make programs error prone unecessarily.
Using static class for mapping API endpoints reduces the burden of refactoring each time there is change on the Zerodha end. As far as I understand, any library which targets .NET Standard 2.0 can be utilized and will work across all the platforms. Let me know if I can be of any help.

I believe we are already doing it in this project. Take a look at Structures.cs.
We do not use any external library for the serialization. Instead, the parsed JSON is loaded into the corresponding POCO field by field. So even if there is an API change from the backend, the library remains almost the same.
Til now, the only time users had to refactor was after KiteConnect 3.0 release, which had major breaking changes and bunch of feature additions. Because of that, we had given ~6 months to users to migrate to this new API. We had also sent reminder emails regarding the same.
Also, we targeted .Net 4.5 instead of previous versions because of multiple reasons. First, previous versions don't have built in WebSocket support. And the one shipped with framework is standard compliant, stable and light compared to external libraries. Second, new versions of Windows don't ship with .Net 2.0 and 3.5 where as 4.5 or above is built in. And since these APIs are dealing with serious data, we encourage our users to be in the latest versions because of the improvements in security and stability they offer.

.NET 4.5 and .NET Standard are two different things. It not necessarily required that any application written for .NET 4.5 will work across all the platforms, while any application written over .NET Standard, specifically 2.0 ensures it to run across the .NET ecosystem. With .NET Standard 2.0 implementation you will ensure that user is on the lastest platform both in .NET and .NET Core.
Also, placing an order or modifying an order is still using a dynamic object for returning any data from the API. Also, at the same time, the API can be written in Fluent fashion (which is much robust and enforce users to use correctly as per the guidelines and required business requirements) and can utilize many helpful libraries for maintaining validation states like FluentValidator, Mapper and etc.

I was planning to write a port for .Net core. But like you said .Net Standard 2.0 will be a better target since it can work with both .Net framework and .Net core.
Also, I will check out the "Flutent" system for the API. Will consider both of them for the next major release.


Client list in WavefrontClientFactory is global, rather than stored on the instance

WavefrontClientFactory has clients as a class member:
class WavefrontClientFactory:
    """Wavefront client factory.

    Create wavefront direct/proxy data ingestion client.
    """

    PROXY_SCHEME = "proxy"
    HTTP_PROXY_SCHEME = "http"
    DIRECT_DATA_INGESTION_SCHEME = "https"
    clients = []

This means that the list of clients is shared among different WavefrontClientFactory instances:
>>> from wavefront_sdk.client_factory import WavefrontClientFactory
>>> client_factory = WavefrontClientFactory()
>>> client_factory.add_client(url="http://example.com/")
>>> client_factory_two = WavefrontClientFactory()
>>> client_factory.clients
[<wavefront_sdk.client.WavefrontClient object at 0x100d10f40>]
>>> client_factory_two.clients
[<wavefront_sdk.client.WavefrontClient object at 0x100d10f40>]

This is surprising for users that may instantiate separate WavefrontClientFactory's and expect them not to share data.
I'd like to propose to change this list to be an instance member.

PR: https://github.com/wavefrontHQ/wavefront-sdk-python/pull/109


Helpers for box-sizing

Hey,
while working on my project, I found that helpers for box-sizing are missing.
If this is considered useful I'd try to contribute them :)

You might already be aware of this, but you can create your own utilities in Tailwind. I know they're probably not intending to get 100% coverage of CSS properties because the default stylesheet would be gargantuan. However, they've done an incredible job making it simple to customize and extend the framework.

Here's one way you could make your own box-sizing utility classes. You would just add something like this at the end of your main stylesheet. By wrapping the classes in the @responsive directive, Tailwind will automatically generate the responsive classes (i.e. md:border-box, lg:border-box).
@responsive {
  .border-box {
    box-sizing: border-box;
  }
  .content-box {
    box-sizing: content-box;
  }
}

Hey @skollro! I would recommend creating those utilities as needed for your own project right now as we don't have plans to add them by default. Thanks!

@adamwathan any plans on revisiting this? I have a few sites where I've needed to add this manually and I feel like it should be a part of core just like userSelect or appearance are.


Test and update the GraphQL API tutorial

Description:
Test the GraphQL API tutorial as there are discrepancies in the actual product UI and the doc [1].
[1] https://apim.docs.wso2.com/en/4.1.0/tutorials/create-and-publish-a-graphql-api/
Related Issues:

https://github.com/wso2/docs-apim/pull/5041

Reported a product issue in [2]. Also removed the section in the docs that mentions this capability as currently it is not possible.

[2] https://github.com/wso2/product-apim/issues/12072
[3

]


Support application crash logging

I have so many app crashes. After select DTC after start live data with enabled GPS..
Can we include https://github.com/ACRA/acra to have device log?
and this: https://github.com/d-a-n/acra-mailer

I have implemented something similar but in native android development. It creates a log file and asks the user if the log should be mailed.

@Pho3niX90 I am in favor of that solution instead of #138. Anyway, #138 is not ready for testing/merge.

ACRA support sending report by email too
https://github.com/ACRA/acra/wiki/AdvancedUsage#sending-reports-by-email
You can put this preference in settings. But the main advantage that https://github.com/pires/android-obd-reader/pull/138 have its that its not need to have Email account (or SMTP) on Android device or Emulator. This is debugging feature (its only for the programmers and @pires can I know what is not ready for you ?) if you not like to debug application with my solution feels free to close PR and write new ACRA project for example ;)

True. But acra is another library that needs to be taken into consideration when compiling. I agree that only developers needs logs, that's why you might as well use android native code and send a complete logcat to the developer.
See here -> https://github.com/pires/android-obd-reader/pull/144

@pires you can think about debugging plugins for every kind of developer ;)

@sytolk my comments on why PR #138 is not ready for merge are detailed there.