fileshelter    | Caught std::exception: filesystem error: cannot create directories: Permission denied [/var/fileshelter/files]

Every time I run:
docker-compose up
I receive the following error:
fileshelter    | Caught std::exception: filesystem error: cannot create directories: Permission denied [/var/fileshelter/files]
Any ideas?
Mk...

Thanks for pointing this out. Sorry, I didn't adjust that after my recent refactoring.
This is due to the fact, that the fileshelter container now runs as read-only. So when the application starts up, it tries to create an uploads directory at /var/fileshelter which fails. To get around this, you can mount a host folder / volume to this container director.
Example: Add the following to your volumes: section in your compose file:
- ./application/uploads/:/var/fileshelter/
I should probably refactor the default compose file. Hope this is of help.

I'm using the current master where the docker-compose.production.yml already includes that volume mount. I still see that same error. Plus does caddy need an update maybe?
docker-compose -f docker-compose.yml -f docker-compose.production.yml up
Starting fileshelter ...
Starting fileshelter ... done
Starting caddy ...
Starting caddy ... done
Attaching to fileshelter, caddy
fileshelter    | Caught std::exception: filesystem error: cannot create directories: Permission denied [/var/fileshelter/files]
caddy          | Activating privacy features...2020/04/24 07:49:50 registration error: acme: Error 403 - urn:acme:error:unauthorized - Account creation on ACMEv1 is disabled. Please upgrade your ACME client to a version that supports ACMEv2 / RFC 8555. See https://community.letsencrypt.org/t/end-of-life-plan-for-acmev1/88430 for details.

Thanks for reporting this issue. I have just updated the Compose workflow with a new Caddy image. Also moved the volume mount to the regular docker-compose.yml.
I tested this setup running a local testing environment with docker-compose up on macOS 10.15.4 and Docker Desktop for Mac v<IP_ADDRESS>.
Hope this fixes your problems.

Thank you for the update! I still got the error afterwards, so I looked more into it. For me the problem appears to have triggered if the applications/uploads subdir did not exist before starting the services the first time. The container actually creates the dir in the volume mount then, but still errors out. I've proposed a solution to prevent this in #3

Thanks for your suggestions. Funny enough, I have been looking into the issue more over the weekend and have come to the same realisation. I think this will solve this issue for most situations.
Additionally I have tried to make the workflow more resilient should anyone decide to bind mount a different folder other than the initial uploads folder. I went with a docker-entrypoint.sh script to take care of potential issues with folder permissions before handing over execution of the fileshelter process to an unprivileged user.

Hi,
I am too facing this problem with this simple docker compose:
version: "3"

services:
  fileshelter:
    image: paulgalow/fileshelter
    read_only: true # I have tried omitting this part
    container_name: fileshelter
    volumes:
      - ./config/fileshelter.conf:/etc/fileshelter.conf:ro # I have tried omitting ":ro"
      - ./data:/var/fileshelter
    restart: unless-stopped
    labels:
    # Labels for Traefik reverse proxy, do not worry about these
      - "traefik.enable=true"
      - "traefik.http.routers.fileshelter.service=fileshelter"
      - "traefik.http.routers.fileshelter.tls=true"
      - "traefik.http.routers.fileshelter.tls.certresolver=dns-cloudflare"
      - "traefik.http.routers.fileshelter.entrypoints=websecure"
      - "traefik.http.services.fileshelter.loadbalancer.server.port=5091"
    networks:
      - web_proxy
    # I have also tried omitting the following cap_drop
    cap_drop:
      - ALL
    cap_add:
      - CHOWN
      - SETUID
      - SETGID

networks:
  web_proxy:
    external:
      name: web_proxy

I get the same exact error message.
I have tried creating the ./data folder manually and I have chowned every folder with the user running the container but it still does not work.

Hi @paolobasso99,
it seems like you are using the FileShelter image that has been published to Docker Hub previously. I should probably remove that at some point. I have later changed the workflow to build the Docker image locally mainly for maintenance reasons. What happens if you clone this repo and build the Docker image yourself, i.e. replacing …
   image: paulgalow/fileshelter

… with …
    image: fileshelter
    build:
      context: ./application
      dockerfile: Dockerfile

?

I've just tried and the same error persist.

Sounds like a permissions issue with your local filesystem. Perhaps it might be worth trying to persist data using a Docker volume instead of a bind mount?


Minecraft does not load ready

https://1drv.ms/v/s!AtINsyYPsa0rg6IsUt7oQ44UFQSA-g?e=fJwMgU

sorry for the late response.
the problem should be fixed, and the upload with the bug has been removed
thanks for the issue


shell script highligh does not properly

Issue Type: Bug
sql=sqlplus -s user/pwd@tns << EOFSQL set serveroutput on; EOFSQL
adding this in a shell script is not properly highlighted things
VS Code version: Code 1.50.0 (93c2f0fbf16c5a4b10e4d5f89737d9c2c25488a3, 2020-10-07T06:10:52.432Z)
OS version: Windows_NT x64 10.0.18363
Extensions (1)

Extension
Author (truncated)
Version

gitlens
eam
11.2.1

We get our shell script grammar from https://github.com/atom/language-shellscript/. This issue looks like a duplicate of https://github.com/atom/language-shellscript/issues/158.


License

You put together a terrific resource!
I am currently writing a book on backend development (https://zero2prod.com) and I'd be interested in featuring (and linking) to your diagram on Hexagonal architecture. While I was checking the repository though I didn't manage to find a license covering the material - can you clarify what can and cannot be done with what is inside this repository?

Hello, thanks for your interest.
I added a license (MIT), you can use everything you need. Looking forward to read your book when it's finished ;)

Thanks a lot 🙇♂


Device Trust Management

As a user, I want to know if my account is logged in from unknown device.

Resolved by #145


Add Gateway API webhook validation functions to egctl translate

Description:
Run the upstream Gateway API validation functions such as https://github.com/kubernetes-sigs/gateway-api/blob/a78e09220feec7947eb1a08b658b45f3b4182d7f/apis/v1beta1/validation/gateway.go#L54 on the inputted resources in egctl translate https://github.com/envoyproxy/gateway/blob/5019d8b598e54fddeece07bbf6de666ec0875780/internal/cmd/egctl/translate.go#L221 to catch client side validation errors and mimic the same experience the user would have had if they were applying these resources using kubectl apply

Can we have a hgctl validate cmd for validating resources ?

Can we have a hgctl validate cmd for validating resources ?

we currently solve above case using egctl translate --from gateway-api --to gateway-api but we could also create a validate alias

/assign

Thanks @liangyuanpeng !

@liangyuanpeng hi, what is the status?

This would be very helpful if we bring validations into translate, which will also help the validations in file-resources provider.
For now, some validations are implemented via CEL, maybe what we need to do here is to find a way convert all the CEL rules into validations code.

For now, some validations are implemented via CEL, maybe what we need to do here is to find a way convert all the CEL rules into validations code.

can we run CEL validation locally like what we did in cel validation tests?

For now, some validations are implemented via CEL, maybe what we need to do here is to find a way convert all the CEL rules into validations code.

can we run CEL validation locally like what we did in cel validation tests?

Have a discussion about this today in the meeting, it seems we cannot run CEL validation tests locally without kube-api-server support, so may need more investigation.

It seems we can take https://github.com/google/cel-go as a example, and input our CEL validation rules like:
ast, issues := env.Compile(`OUR-CEL-RULE`)

and then validate the input object like:
out, details, err := prg.Eval(XXX)

So the only thing left unresolved now is how we retrieve our current CEL rules from comments.

oh nice @shawnh2 !
we can look into kube-builder converts CEL into x-kubernetes-validations fields
https://github.com/envoyproxy/gateway/blob/cc8a86e0961e9dec5f5c56422127a8950931efb3/charts/gateway-helm/crds/generated/gateway.envoyproxy.io_backendtrafficpolicies.yaml#L218

oh nice @shawnh2 ! we can look into kube-builder converts CEL into x-kubernetes-validations fields
https://github.com/envoyproxy/gateway/blob/cc8a86e0961e9dec5f5c56422127a8950931efb3/charts/gateway-helm/crds/generated/gateway.envoyproxy.io_backendtrafficpolicies.yaml#L218

sure we can read CEL rules from x-kubernetes-validations fields in all these CRD yaml file. but if we do so, does it mean we need to include all these yaml file ?
maybe we can introduce a knob like --crd-path to indicate all the path for these files.

we'll need to codify this, if we need access to the YAML file we can use embed to make it part of the binary

find a more suitable way to validate k8s CRD object using cel-lib provided by apiserver.
code will like:

import (
	"context"
	"math"
	"testing"

	apiextensions "k8s.io/apiextensions-apiserver/pkg/apis/apiextensions/v1"
	"k8s.io/apiextensions-apiserver/pkg/apiserver/schema"
	celschema "k8s.io/apiextensions-apiserver/pkg/apiserver/schema/cel"
	"k8s.io/apiextensions-apiserver/pkg/apiserver/schema/cel/model"
	"k8s.io/apimachinery/pkg/util/validation/field"
	"k8s.io/apimachinery/pkg/util/version"
	celconfig "k8s.io/apiserver/pkg/apis/cel"
	"k8s.io/apiserver/pkg/cel/environment"
)

func TestExprEval(t *testing.T) {
        // Here is going to be our CEL validation schema for each CRD
	objectSchema := schema.Structural{
		Generic: schema.Generic{
			Type: "object",
		},
		Properties: map[string]schema.Structural{
			"nestedObj": {
				Generic: schema.Generic{
					Type: "object",
				},
				Properties: map[string]schema.Structural{
					"val": {
						Generic: schema.Generic{
							Type: "integer",
						},
					},
				},
			},
		},
		Extensions: schema.Extensions{
			XValidations: apiextensions.ValidationRules{
				{
					Rule:    "self.nestedObj.val == 10",
					Message: "val should be equal to 10",
				},
			},
		},
	}

	env, err := environment.MustBaseEnvSet(environment.DefaultCompatibilityVersion()).Extend(
		environment.VersionedOptions{
			IntroducedVersion: version.MajorMinor(1, 999),
		})
	if err != nil {
		t.Fatal(err)
	}
	loader := celschema.NewExpressionsEnvLoader()

	compilationResults, err := celschema.Compile(&objectSchema, model.SchemaDeclType(&objectSchema, false), celconfig.PerCallLimit, env, loader)
	if err != nil {
		t.Fatalf("Expected no error, but got: %v", err)
	}
	t.Log("compile ret", compilationResults)

	if len(compilationResults) != len(objectSchema.XValidations) {
		t.Fatalf("complie ret must equal xvalidations size")
	}

	celValidator := celschema.NewValidator(&objectSchema, true, celconfig.PerCallLimit)
	if celValidator == nil {
		t.Fatalf("unexpected nil cel validator")
	}

        // Here is going to be the object resource that we'd like to perform validations on
	validateObj := map[string]interface{}{
		"nestedObj": map[string]interface{}{
			"val": 10,
		},
	}

	errs, _ := celValidator.Validate(context.Background(), field.NewPath("root"), &objectSchema, validateObj, nil, math.MaxInt)
	t.Log(errs)
}

// The test pass.

// changing validateObj 'val' to 6, the test fail with reason: "val should be equal to 10" (which is exactly our CEL rule msg)

note:

the validateObj must be in type map[string]interface{}, so we need convert resource into this type
we need to visit each CRD to build schema.Structural

Find a more suitable way to validate k8s CRD object using cel lib provided by apiextensions-apiserver. Here is an example code that works:

import (

	"context"

	"math"

	"testing"

	apiextensions "k8s.io/apiextensions-apiserver/pkg/apis/apiextensions/v1"

	"k8s.io/apiextensions-apiserver/pkg/apiserver/schema"

	celschema "k8s.io/apiextensions-apiserver/pkg/apiserver/schema/cel"

	"k8s.io/apiextensions-apiserver/pkg/apiserver/schema/cel/model"

	"k8s.io/apimachinery/pkg/util/validation/field"

	"k8s.io/apimachinery/pkg/util/version"

	celconfig "k8s.io/apiserver/pkg/apis/cel"

	"k8s.io/apiserver/pkg/cel/environment"

)

func TestExprEval(t *testing.T) {

        // Here is going to be our CEL validation schema for each CRD

	objectSchema := schema.Structural{

		Generic: schema.Generic{

			Type: "object",

		},

		Properties: map[string]schema.Structural{

			"nestedObj": {

				Generic: schema.Generic{

					Type: "object",

				},

				Properties: map[string]schema.Structural{

					"val": {

						Generic: schema.Generic{

							Type: "integer",

						},

					},

				},

			},

		},

		Extensions: schema.Extensions{

			XValidations: apiextensions.ValidationRules{

				{

					Rule:    "self.nestedObj.val == 10",

					Message: "val should be equal to 10",

				},

			},

		},

	}

	env, err := environment.MustBaseEnvSet(environment.DefaultCompatibilityVersion()).Extend(

		environment.VersionedOptions{

			IntroducedVersion: version.MajorMinor(1, 999),

		})

	if err != nil {

		t.Fatal(err)

	}

	loader := celschema.NewExpressionsEnvLoader()

	compilationResults, err := celschema.Compile(&objectSchema, model.SchemaDeclType(&objectSchema, false), celconfig.PerCallLimit, env, loader)

	if err != nil {

		t.Fatalf("Expected no error, but got: %v", err)

	}

	t.Log("compile ret", compilationResults)

	if len(compilationResults) != len(objectSchema.XValidations) {

		t.Fatalf("complie ret must equal xvalidations size")

	}

	celValidator := celschema.NewValidator(&objectSchema, true, celconfig.PerCallLimit)

	if celValidator == nil {

		t.Fatalf("unexpected nil cel validator")

	}

        // Here is going to be the object resource that we'd like to perform validations on

	validateObj := map[string]interface{}{

		"nestedObj": map[string]interface{}{

			"val": 10,

		},

	}

	errs, _ := celValidator.Validate(context.Background(), field.NewPath("root"), &objectSchema, validateObj, nil, math.MaxInt)

	t.Log(errs)

}

// The test pass.

// Changing the 'val' of validateObj to 6, the test fail with reason: "val should be equal to 10" (which is exactly our CEL rule msg)

BTW:

The validateObj must be in type map[string]interface{}, so we need convert resource into this type. The easiest approach is to first encode the struct into a JSON string using encoding/json, and then decode the JSON string into a map

We need to visit each CRD to build schema.Structural, like objectSchema in this example

FYI: The whole implementation work will based on the idea above, post here first just for better understanding.

Refs:

https://github.com/kubernetes/apiextensions-apiserver/blob/v0.30.1/pkg/apiserver/schema/cel/compilation_test.go

https://github.com/kubernetes/apiextensions-apiserver/blob/v0.30.1/pkg/apiserver/schema/cel/validation_test.go

found a even better approach, will post here by tomorrow

Hi @arkodg @shawnh2 I was looking forward for help points on this discussion about adding API validation for the functions in egctl translate implementation , under internal/cmd/egctl/translate.go.
I have made some changes in this direction here #3960 , the added resources to the kubernetesYAMLToResources need to have a validity API webhook . Can you guide me more about achieving the same?


AVRC without a2dp?

is it possible to use your library as a stand alone AVRC controller?
Without hijacking the audio feed from the player?

What's wrong with you people: Why are you asking questions that have been answered  several times and that are documented in the Readme!: stand alone AVRCP without A2DP are not supported!

I think the most promising approch would be if you use the ESP32 API directly: https://docs.espressif.com/projects/esp-idf/en/latest/esp32/api-reference/bluetooth/esp_avrc.html

I'll look into it! thanks :)


Not Found import com.pluto.plugin.Plugin in Release

**Plugin Class not found in release variant **
I create a custom pluto plugin for some purpose but in release variant i can;t find class.
Screenshots
Click here to see image.
Additional context
I added i custom plugin and its work in debug variant but when i run in release mode, it give error for not finding plugin class.
Can't import these files
import com.pluto.plugin.Plugin import com.pluto.plugin.PluginConfiguration

@rohitjakhar can you share screenshot for your dependencies code snippet?


Inlay failed on the newest rust-analyzer

It seems that the newest rust-analyzer is not using experimental/inlayHints , and using the stable api..But I change to Document/inlayHint the inlay hasn't show. I want to help but..

https://rust-analyzer.github.io/thisweek/2022/04/18/changelog-125.html
As shown in the document
https://github.com/rust-analyzer/rust-analyzer/pull/12006
https://github.com/rust-analyzer/rust-analyzer/pull/11935
They have switch to LSP inlay hints.


Sort Of 2D Array

Have you read the Contributing Guidelines on Pull Requests?
yes
Description
(Write your answer here.)
Checklist

[y ] I've read the contribution guidelines.
[y ] I've checked the issue list before deciding what to submit.
[ y] I've edited the README.md and link to my code.

Related Issues or Pull Requests
Sort Of 2D Array #1924

@iamrajiv

@iamrajiv


Proxy mode

Hello, does the project leader support the proxy mode to use this project to implement penetration testing, and if so, where do you need to change the request address of the interface?

Yes. The easiest way would be modifying api_base in module_import.py, such as the one for GPT-4. You shall find all those related to OpenAI.
You'll need to pull the project to local env, modify the api base as your desired proxy, and install the project with pip install ./

Okay, thank you project leader


list filter forces a space before its second_delimiter

Expected behavior
The list filter shouldn't impose users to have spaces around the second_delimiter. This would allow us to have all strings separated by a single comma or support formatting like the Oxford comma and such. Right now it's too opinionated without any option to opt-out of this behavior.
Actual behavior
The list filter forces one space before the second_delimiter: https://github.com/lggorman/timber/blob/master/lib/Twig.php#L315
Steps to reproduce behavior
Try using the list filter passing a comma (,) as the second argument.
What version of WordPress, PHP and Timber are you using?
Latest everything. Unrelated to the issue.
How did you install Timber? (for example, from GitHub, Composer/Packagist, WP.org?)
WordPress.org. Unrelated to the issue.

Totally agree! This seems like a quick fix if you're interested (or someone else watching this thread) is interested in submitting a PR!


Default output dir for integration tests causes issues with pre-commit checks

The default output directory for integration tests is output/ directory, which can cause issues when these tests are run locally.
As part of integration tests we clone Git repository under output/. Now if we run make check without removing output/, pre-commit picks up files in these cloned repositories (even though output is part of Macaron's .gitignore) based on their individual .gitignore files.
I can think of two solutions:

Use a path outside the current workspace for integration test output directory, but picking a path that would also work on GitHub Actions Runner might not be straightforward.
Clean up and remove the integration tests output directory after tests finish (which will make tests slower as we won't cache the cloned repositories anymore).

I think we should close this issue because now we create the output directory within the test case directory itself, and not on the root path (of the cloned Macaron repo) any more.

#764


Bot not working

I'm getting this error
Cannot read property \'intent\' of undefined
here  let intentDisplayName = req.body.queryResult.intent.displayName;  in fulfillment.js
seems like queryresults is undefined, I'm new to dialog flow
what am I doing wrong?

Hi ChinnaRajS,
Did you follow the instructions and create the Dialogflow project and import the intents from the file included in this sample?


How do I get the element that the mouse is over?

For instance

1
2

If I drag 1 over 2 how do I get the 2 element while the mouse is over it?
sort of like an over element function or something?
I am trying to implement something like http://www.jqueryscript.net/demo/jQuery-Plugin-To-Sort-Nested-Lists-Using-Drag-Drop-nestedSortable/.
So I would need to get the element that the item is over and append a new sortable list to it. Not sure how to implement it yet.
I think adding this functionality would help a lot with creating nested sortable lists.

you can get the Id of the element you are over while dragging by using the onMove event. evt.related.id will contain the Id of the item you are currently over. this will work with multiple lists as well.


meta does not list transformers modules under 'modules'

I have noticed that if I get the meta data from weaviate (v1.2.0) with a transformer module, it does not display it under the 'module'.
>>> client.get_meta()
{'hostname': 'http://[::]:8080', 'modules': {}, 'version': '1.2.0'}

Weaviate with a transformer model has the same META as weaviate without any module.
I would suggest to have something different for transformers , so we can know what kind of module we have without checking the docker-compose/helm-chart.
My suggestions are the following:

'modules' : ['text2vec-transformers']
'modules' : 'text2vec-transformers'
'modules' : {'text2vec-transformers': {} }

As we discussed the 3rd option is the best since it preserves the same format as for text2vec-contextionary.
If anyone has another suggestion, please feel free to comment it in this issue.

PR #1506 fixed that issue, we went with option 3


UI for resources in statefulset does not match UI for resources in deployments -> if limit is lower than request, user should not be able to create

How to reproduce:

create a statefulSet

add a resource request and limit request, where the request is higher then the limit

Result:

kubernetes throws an error

Resource UI in other create/edit fields (i.e. deployments) throws an error in the UI. This is what should happen for any resource request done through the UI

This is (lack of) server-side k8s validation, not UI or even Rancher.

Closing this since this outside what can be done in the product. If you think something like this is needed, then file a new ticket against the rancher/rancher repo if the backend can pass along something to the UI.


Shell completion fails for option values that start with symbols

Running into the same case as #1929, except specific to option values that may start with symbols such as '+', '~', and '!'. Shell completion treats these values as the start of new options, so doesn't complete them.
Reproduction script with the cli command referenced by setuptools:
@command()
@option("-c", type=Choice(["+1", "+2", "!1", "!2"]))
def cli(c):
    echo(f"Value is {c}")

With shell completion enabled:
$ click-bug -c <TAB><TAB>
+1 +2  !1 !2
$ click-bug -c +<TAB><TAB>
# Nothing happens

I was looking at the discussion on #1930, and it makes sense that '+' may be considered the start of an option. I'm wondering if it would be valid for completion to prioritize option values over new option names. As in, within shell_completion.py's _resolve_incomplete function, moving the _is_incomplete_option check above the if "--" not in args and _start_of_option(incomplete) call allows the tab completion in this example to work as expected:
$ click-bug -c +<TAB><TAB>
+1 +2

I can look into putting up a PR to do that if it seems valid.
Environment:

Python version: 3.6.9
Click version: 8.0.1

Importantly, this affects the completion of paths that start with a period. These are very common, e.g., ../file to refer to a file in the parent directory, or .bashrc for hidden files. The current shell completion system cannot cope with these paths.

I can confirm that our CLI tab-completion also broke when moving to click 8.0 specifically with relative paths starting with . or ~ no longer being completed.


Fix typo in FormScrollToInvalidFieldPlugin import

1. Why is this change necessary?
Add more consistency between all plugins imports and fix a typo
2. What does this change do, exactly?
Changed the import syntax of the plugin, FormScrollToInvalidFieldPlugin was imported as "FromScrollToInvalidFieldPlugin" with a typo
3. Describe each step to reproduce the issue or behaviour.
no real issue just malformed syntax
5. Checklist

[x] I have written tests and verified that they fail without my change
[x] I have created a changelog file with all necessary information about my changes
[x] I have written or adjusted the documentation according to my changes
[x] This change has comments for package types, values, functions, and non-obvious lines of code
[x] I have read the contribution requirements and fulfil them.

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

Thanks for your contribution @iNem0o ! 💙


Use etag for better caching

https://docs.github.com/en/rest/using-the-rest-api/best-practices-for-using-the-rest-api?apiVersion=2022-11-28#do-not-manually-parse-urls

Done in #89


Naming of containers depends on environment

Expected Behaviour
The implicit naming for the testcontainers is the same for ci environment and local environment.
Actual Behaviour
Local Environment:
When the docker compose environment starts, the container names cosist of the service names in the docker-compose.yml and an additional "-1". Everything works fine.
Ci Environment:
Im using azure pipelines.  I get this error:
Error: Cannot get container "frontend-1" as it is not running. After testing i recognized that the container in the ci-environment
is named with  an additional "_1" instead of "-1".
Because of the different naming behaviuor certain steps like the wait strategies are not working because they depend on the  container name.
Steps to Reproduce

This is the setup of the docker-compose environment:`

 test.beforeEach(async ({ page }) => {
       environment = await new DockerComposeEnvironment('playwrightTests', 'docker-compose.yml')
           .withBuild()
           .withWaitStrategy('postgres-1', Wait.forListeningPorts(),)
           .withWaitStrategy('frontend-1',
               Wait.forAll([
                   Wait.forListeningPorts(), Wait.forLogMessage(/start worker processes/)]))
           .withWaitStrategy('api-1', Wait.forListeningPorts())
           .up();
       const frontendPort = environment.getContainer("frontend-1").getMappedPort(8080);
       await page.goto(`http://localhost:${frontendPort}`);
   })`

Docker compose yml:

version: '3'
services:
    frontend:
        image: my-frontend
        environment:
            DEBUG: testcontainers*
        ports:
            - '8080'
    api:
        image: my-api
        environment:
            ASPNETCORE_ENVIRONMENT: 'Development'
            CONNECTIONSTRINGS__POSTGRES: 'Host=postgres;Username=admin;Password=admin;Database=my-db'
            DEBUG: testcontainers*
        ports:
            - '1234:80'

    postgres:
        image: postgres:14.6
        environment:
            POSTGRES_USER: admin
            POSTGRES_PASSWORD: admin
            POSTGRES_DB: my-db
            DEBUG: testcontainers*
        ports:
            - '5432'

The docker compose environment starts when running npx playwright test, The test.beforeEach hook is defined at the top of a playwright testfile

Environment Information

Operating System: Windows 10.0.19045 Build 19045
Docker Version: 24.0.5, build ced0996
Node version: 19.9.0
Testcontainers version: 9.9.1

In general, the actual container name should be considered an internal implementation detail and you should not rely on it in other parts of your code. However, you are right that the methods provided byDockerComposeEnvironment should abstract this way 👍
So in your case it means, locally you are using Docker Compose v2, while CI is using Docker Compose v1, correct? As a workaround, I'd strongly suggest to use the same Docker Compose version across environments (either by using v1 locally, or trying to upgrade to v2 on CI).


Update "Using Atam4j" section in readme

The public interface has changed with https://github.com/atam4j/atam4j/pull/23 and the readme should be updated to reflect this.

I will do this once the latest release has been pushed to maven central - then I can update the sample app.

Addressed in https://github.com/atam4j/atam4j/pull/30

This is now complete. README associated with v0.4.0 reflects the new and improved public interface and usage code snippet.


ES comments need checked for consistency

Lots of copy/paste type errors in ES. For example, after CFE_ES_IncrementTaskCounter() the comment says  /* End of CFE_ES_ExitChildTask() */

Trac comment by jhageman on 2019-07-03 12:48:08:
Moved unfinished 6.6.1 issues to next minor release

Imported from trac issue 244.  Created by sseeger on 2018-08-14T19:37:54, last modified: 2019-07-03T12:48:08

Just piling on, /* end of file */ in the middle of the file and a handful of others.

Comments and format cleanup planned once this round of PRs are closed

Most or all of the typos/mistakes that were originally noticed when this issue was opened have probably been cleared up by now.
I would suggest that this can be closed as completed by recent commits.


yquake2: Add suggestion for yquake2-ref-vk

This adds the suggestion to install the Vulkan renderer specifically made for Yamagi Quake II.
It's been ported from vkQuake2 by the Yamagi team.
What package release type is this?

[x] stable
[ ] beta
[ ] dev/nightly/canary

I followed the bucket's manifest standards?

[x] I have read the Contributing Guide.
[x] properly named and capitalized shortcuts?
[x] autoupdate and checkver entry
[x] persist defined with config/data/user/portable/textures/saves folder(s) specific for the app?
[x] a pre_install script to auto-enable portable mode (if needed)?

[x] a pre_install script creates runtime created files specified in persist (ensures symlinks properly get created)

[x] license identifier and url
[x] a short terse description matching existing style.
[x] url to the release along with its sha256 hash
[x] bin entry for main binary

[x] if beta, dev, etc: does bin shim have variant appended to the name? (e.g appname-dev)

[x] passes bin/checkver.ps1 and bin/checkurls.ps1
[x] tested install, checked persist, no errors.
[x] manifest is sorted to spec
[x] manifest follows spec: appname or appname-variant (e.g citra-canary or dolphin-dev)
[x] I tested the package and it runs in portable mode. I have verified the symlinks are correct in the persist folder and working.
[x] I will maintain this manifest and promptly fix it in the event it breaks.

Hold on, let me troubleshoot.

Just a note that the latest commit fixed the error that was encountered.


When I want to download/clone the code of this project, the GitHub remind me that Page not found. Could you please upload the proper version for this doc? thx

[Enter feedback here]

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

ID: df55b676-8ff7-1470-3525-d0edfd406af6
Version Independent ID: ac264c26-7196-870b-760f-94a97ae437e8
Content: Deploy an ASP.NET Core and Azure SQL Database app to Azure App Service - Azure App Service
Content Source: articles/app-service/tutorial-dotnetcore-sqldb-app.md
Service: app-service
GitHub Login: @alexwolfmsft
Microsoft Alias: alexwolf

Thanks for the feedback! I have assigned the issue to the content author to investigate further and update the document as appropriate.

This has been fixed with this PR:
https://github.com/MicrosoftDocs/azure-docs-pr/pull/188102


Feature request: scss-lint doesn't like unabbreviated hex colors

If I use color picker to choose a color such as #333333, scss-lint complains about it and wants #333. It would be cool if there were an option in the Color Picker package that would dump out abbreviated hexes.

Abbreviation will be included as an option in the upcoming v2.0.0.


Remove assignment to variable as the value is never used

Breaking change

Proposed change

Type of change

[ ] Dependency upgrade
[ ] Bugfix (non-breaking change which fixes an issue)
[ ] New integration (thank you!)
[ ] New feature (which adds functionality to an existing integration)
[ ] Deprecation (breaking change to happen in the future)
[ ] Breaking change (fix/feature causing existing functionality to break)
[ ] Code quality improvements to existing code or addition of tests

Additional information

This PR fixes or closes issue: fixes #
This PR is related to issue:
Link to documentation pull request:

Checklist

[ ] The code change is tested and works locally.
[ ] Local tests pass. Your PR cannot be merged unless tests pass
[ ] There is no commented out code in this PR.
[ ] I have followed the development checklist
[ ] I have followed the perfect PR recommendations
[ ] The code has been formatted using Black (black --fast homeassistant tests)
[ ] Tests have been added to verify that the new code works.

If user exposed functionality or configuration variables are added/changed:

[ ] Documentation added/updated for www.home-assistant.io

If the code communicates with devices, web services, or third-party tools:

[ ] The manifest file has all fields filled out correctly.
Updated and included derived files by running: python3 -m script.hassfest.
[ ] New or updated dependencies have been added to requirements_all.txt.
Updated by running python3 -m script.gen_requirements_all.
[ ] For the updated dependencies - a link to the changelog, or at minimum a diff between library versions is added to the PR description.
[ ] Untested files have been added to .coveragerc.

To help with the load of incoming pull requests:

[ ] I have reviewed two other open pull requests in this repository.

Description:
Code Smell:Remove assignment to variable as the value is never used
Motivation:Code with unused variables creates confusion and difficult to maintain. They serve no use and may cause confusion in other readers of our code. We should remove these unused local variables in order to simplify your code and reduce errors.The platform local variable assigned twice and not used in first occurence and second occurence is used in for loop.I removed unused local variable platform(first occurence) in the code and it makes easy to read and maintain the code.

looks good


Linechart zoom shows wrong preview

Version
4.2.1-rc1
Reproduction link
https://jsfiddle.net/tmtron/0beLxwh2/21/
Steps to reproduce

add a null datapoint at 1995
add some data between 1997 and 2000
add a final null datapoint at 2005

What is expected?
the zoom slider background data should show the real data in the middle of the slider
What is actually happening?
The data in the zoom slider is stretched. I think this is a bug, unless I am missing some settings (but I could not find any switches on the zoom-slider to make this work)

The following screenshot shows the issue. The area outside of the yellow highlighted rectangle in the zoom range (1) should not be visible.

see also: related Stackoverflow question

Hello, any updates on this? This is a very important feature

Hello, any updates on this? This is a very important feature

The issue was open in 2019 and it's still present in 5.0.0.
The problem is: the preview doesn't correspond to actual chart data, even approximately.
Here's a bright example: https://echarts.apache.org/examples/en/editor.html?c=line-draggable
See the previews for X and Y and compare it to actual curve on the graph.  There is no obvious logic behind it.
Let me repeat that this feature seems to be very important for various common cases.
Thank you!

The issue was open in 2019 and it's still present in 5.0.0.
The problem is: the preview doesn't correspond to actual chart data, even approximately.
Here's a bright example: https://echarts.apache.org/examples/en/editor.html?c=line-draggable
See the previews for X and Y and compare it to actual curve on the graph.  There is no obvious logic behind it.
Let me repeat that this feature seems to be very important for various common cases.
Thank you!

@pissang - Is there any update on this issue? It is not in the v5.2 release. What are other people using to replace this?

Any updates on this? I'm facing the same issue in v5.4.3


请问下MVParms AndroidX的版本是哪个? 谢谢

Look at here

→ Did you conform to the Rules?
→ Did you read the Wiki Carefully?
→ Did you search in Google?
→ Did you search in openned&closed Issues?
→ Receive only bugs and suggestions

Environment

[x] MVPArms Version:
[x] AndroidStudio Version:
[x] Gradle Plugin Version:
[x] Target Android Version:
[x] Device Model:

Bug Description:

Related Code:

Bug Log:

Others:

master 分支就是 AndroidX


Try enabling Windows tests

Checklist

[ ] Used a personal fork of the feedstock to propose changes
[ ] Bumped the build number (if the version is unchanged)
[ ] Reset the build number to 0 (if the version changed)
[ ] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[ ] Ensured the license file is being packaged.

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

Fix #2 - let's see whether this works by now.

This is ready to go @conda-forge/libignition-gui

Thanks!


adjust log format in LogTradesAnalysis Analyze

use local time make more readability
add orderside string for trades analysis. because EntranceOrder may not be bought, but sold.

thanks, I'll double check it again


Issue running demo package locally

Hey amazing repo... I think there is a great demand coming for tools like this that allow you to move away from SPA applications to more of a hybrid approach.
Im having trouble running the demo app locally
steps to reproduce:
npm i from root
cd demo
npm i
resulting error
➜  demo git:(main) ✗ npm i
npm ERR! code EUNSUPPORTEDPROTOCOL
npm ERR! Unsupported URL Type "workspace:": workspace:*

npm ERR!      /Users/../.npm/_logs/2022-03-28T17_17_11_106Z-debug.log

Hey @dperrymorrow! I'm using pnpm to manage this repo, so running pnpm i from the root should work.
I still need to work on a better demo, the one included here isn't the most useful at the moment.

Actually, I remembered that I do have a live demo you can check out!
The category tabs on https://astro.build/integrations/ are powered by micromorph/spa 👍🏻


Nitrokey 3C NFC not found in Nitropy in Bootloader mode

Hi, I guess this is more of a pynitrokey issue rather than a firmware Issue, else I could add an Issue to the Firmware Repo.
I wanted to update my Nitrokey from v1.6.0 to 1.7.0.
I tried this in the Nitrokey App.
After I need to touch the Nitrokey, the Stick reboots in Bootloader mode and is not recognised anymore.
Then I tried the same with nitropy and ensured it is listed (nitropy nk3 list).
This also works.
An nitropy nk3 reboot --bootloader works as intended.
The Nitrokey is visible in Windows with e.g. usbipd, Zadig etc.
And I can see the ID 20a0:42dd clearly.
An nitropy list throws an error afterwards.
Log is attached.
nitropy.log.i158qdq9.txt
Also I think this is not related to the timing issues of the former problems with updating, since the device is not found, even after a while.
Everything is running on Windows 11.
Tried it with python 3.10 and 3.11

Can you confirm that you also tried running it as administrator?
Do you maybe have some usb-guard software running ? bitdefender or something which doesn't have the bootloader whitelisted?

Closing as we need more information to diagnose the problem.  Please re-open and provide more details if you are still running into this issue.


(docs) Add PowerShell cmdlet reference

This adds a new PowerShell cmdlet reference page that is similar in
structure to the shell command reference page.
!no-release-note

CLA signed by all contributors.


support for private dockerhub

is there any way we can docker pull from private dockerhub repos while defining Image.from_registry?

Not yet. You can use private AWS ECR and GCP artifact registry though, see docs.


Added external data computation logics

... to avoid re-computing for external products with prices

I've been thinking about a better term to replace "external", because in this context an "external" prices is something we can't re-compute, correct?
I'd like to call it something more verbose for the given context, keep in mind this is a generic lib that can have more situations where we don't want re-computations.
Immutable, maybe?


0.20 backports

Once this passes, I'll get out a round of bugfix releases for gtk-rs-core later. gtk4-rs tomorrow, gstreamer-rs Wednesday, gst-plugins-rs Thursday.

Is the part where we ignore the clippy warning still needed with the latest gir changes?

Yes

In 0.20 only, in main it should be fine


HBASE-28890 RefCnt Leak error when caching index blocks at write time

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 40s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  1s

codespell was not available.

+0 :ok:
detsecrets
0m  1s

detect-secrets was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

+1 :green_heart:
hbaseanti
0m  0s

Patch does not have any anti-patterns.

_ master Compile Tests _

+0 :ok:
mvndep
0m 10s

Maven dependency ordering for branch

+1 :green_heart:
mvninstall
4m 15s

master passed

+1 :green_heart:
compile
5m 36s

master passed

+1 :green_heart:
checkstyle
1m 28s

master passed

+1 :green_heart:
spotbugs
2m 47s

master passed

+1 :green_heart:
spotless
0m 54s

branch has no errors when running spotless:check.

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 10s

Maven dependency ordering for patch

+1 :green_heart:
mvninstall
3m 59s

the patch passed

+1 :green_heart:
compile
7m  0s

the patch passed

+1 :green_heart:
javac
7m  0s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
checkstyle
1m 44s

the patch passed

+1 :green_heart:
spotbugs
2m 48s

the patch passed

+1 :green_heart:
hadoopcheck
16m 35s

Patch does not cause any errors with Hadoop 3.3.6 3.4.0.

+1 :green_heart:
spotless
1m 15s

patch has no errors when running spotless:check.

_ Other Tests _

+1 :green_heart:
asflicense
0m 41s

The patch does not generate ASF License warnings.

60m 41s

Subsystem
Report/Notes

Docker
ClientAPI=1.47 ServerAPI=1.47 base: https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-6317/1/artifact/yetus-general-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/6317

Optional Tests
dupname asflicense javac spotbugs checkstyle codespell detsecrets compile hadoopcheck hbaseanti spotless

uname
Linux bc459442020e 5.4.0-192-generic #212-Ubuntu SMP Fri Jul 5 09:47:39 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
master / 7752139ea93e031a82d023be94c5dc5e4b807954

Default Java
Eclipse Adoptium-17.0.11+9

Max. process+thread count
84 (vs. ulimit of 30000)

modules
C: hbase-common hbase-server U: .

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 13s

Maven dependency ordering for patch

+1 :green_heart:
mvninstall
4m 36s

the patch passed

+1 :green_heart:
compile
2m  1s

the patch passed

+1 :green_heart:
javac
2m  1s

the patch passed

+1 :green_heart:
javadoc
1m 12s

the patch passed

+1 :green_heart:
shadedjars
8m  8s

patch has no errors when building our shaded downstream artifacts.

_ Other Tests _

+1 :green_heart:
unit
3m 29s

hbase-common in the patch passed.

-1 :x:
unit
383m  0s
/patch-unit-hbase-server.txt
hbase-server in the patch failed.

436m 20s

Subsystem
Report/Notes

Docker
ClientAPI=1.43 ServerAPI=1.43 base: https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-6317/1/artifact/yetus-jdk17-hadoop3-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/6317

Optional Tests
javac javadoc unit compile shadedjars

uname
Linux 7332b6ca5d07 5.4.0-1103-aws #111~18.04.1-Ubuntu SMP Tue May 23 20:04:10 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
master / 7752139ea93e031a82d023be94c5dc5e4b807954

Default Java
Eclipse Adoptium-17.0.11+9

Test Results
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-6317/1/testReport/

Max. process+thread count
4428 (vs. ulimit of 30000)

modules
C: hbase-common hbase-server U: .

Console output
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-6317/1/console

versions
git=2.34.1 maven=3.9.8

Powered by
Apache Yetus 0.15.0 https://yetus.apache.org

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 43s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  1s

codespell was not available.

+0 :ok:
detsecrets
0m  1s

detect-secrets was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

+1 :green_heart:
hbaseanti
0m  0s

Patch does not have any anti-patterns.

_ master Compile Tests _

+0 :ok:
mvndep
0m  8s

Maven dependency ordering for branch

+1 :green_heart:
mvninstall
3m 31s

master passed

+1 :green_heart:
compile
5m  4s

master passed

+1 :green_heart:
checkstyle
1m  7s

master passed

+1 :green_heart:
spotbugs
2m 45s

master passed

+1 :green_heart:
spotless
0m 52s

branch has no errors when running spotless:check.

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 11s

Maven dependency ordering for patch

+1 :green_heart:
mvninstall
3m 50s

the patch passed

+1 :green_heart:
compile
5m  7s

the patch passed

+1 :green_heart:
javac
5m  7s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
checkstyle
1m 12s

the patch passed

+1 :green_heart:
spotbugs
3m 17s

the patch passed

+1 :green_heart:
hadoopcheck
13m 14s

Patch does not cause any errors with Hadoop 3.3.6 3.4.0.

+1 :green_heart:
spotless
0m 50s

patch has no errors when running spotless:check.

_ Other Tests _

+1 :green_heart:
asflicense
0m 19s

The patch does not generate ASF License warnings.

50m 31s

Subsystem
Report/Notes

Docker
ClientAPI=1.47 ServerAPI=1.47 base: https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-6317/2/artifact/yetus-general-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/6317

Optional Tests
dupname asflicense javac spotbugs checkstyle codespell detsecrets compile hadoopcheck hbaseanti spotless

uname
Linux 7b4f14a28554 5.4.0-195-generic #215-Ubuntu SMP Fri Aug 2 18:28:05 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
master / 7752139ea93e031a82d023be94c5dc5e4b807954

Default Java
Eclipse Adoptium-17.0.11+9

Max. process+thread count
85 (vs. ulimit of 30000)

modules
C: hbase-common hbase-server U: .

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 13s

Maven dependency ordering for patch

+1 :green_heart:
mvninstall
3m 43s

the patch passed

+1 :green_heart:
compile
1m 45s

the patch passed

+1 :green_heart:
javac
1m 45s

the patch passed

+1 :green_heart:
javadoc
0m 59s

the patch passed

+1 :green_heart:
shadedjars
6m 49s

patch has no errors when building our shaded downstream artifacts.

_ Other Tests _

+1 :green_heart:
unit
2m 59s

hbase-common in the patch passed.

+1 :green_heart:
unit
271m 37s

hbase-server in the patch passed.

307m 17s

Subsystem
Report/Notes

Docker
ClientAPI=1.47 ServerAPI=1.47 base: https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-6317/2/artifact/yetus-jdk17-hadoop3-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/6317

Optional Tests
javac javadoc unit compile shadedjars

uname
Linux 3b792adb8f91 5.4.0-195-generic #215-Ubuntu SMP Fri Aug 2 18:28:05 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
master / 7752139ea93e031a82d023be94c5dc5e4b807954

Default Java
Eclipse Adoptium-17.0.11+9

Test Results
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-6317/2/testReport/

Max. process+thread count
4697 (vs. ulimit of 30000)

modules
C: hbase-common hbase-server U: .

Console output
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-6317/2/console

versions
git=2.34.1 maven=3.9.8

Powered by
Apache Yetus 0.15.0 https://yetus.apache.org

This message was automatically generated.


Create robot bounding mesh

Hello,
I would like to recreate the robot bounding mesh like described in the paper.
http://www6.in.tum.de/Main/Publications/Gaschler2015d.pdf (Fig. 4)
Where can I find the robot file? What are the settings in boundingmesh-gui.exe?
I appreciate your help.
-Martin

Hello Martin,
to answer your first question how to obtain meshes of robots, most manufacturers offer *.step files for download. As an example, the Mitsubishi RV-6SL robot is available as a file rv-6sl_top.stp. Then, you triangulate with FreeCAD and export as *.wrl file wih good quality settings (such that you start with similar vertex counts).
For bounding mesh simplification, always start with the simplest method (metric: average, initialization: midpoint) and make sure the algorithm works on that type of mesh. After that, try potentially finer methods such as (metric: average, initialization: DistancePrimitives).
When evaluating the results, note that the "error" or "mesh error" in boundingmesh-gui is not a distance but a cost function of the respective metric. Computing the exact distance is not part of boundingmesh, other software like meshlab could do it.


Wish option to view 'multiple-dependency-versions' as a warning instead of an error.

I want to include Sherif in CI, but it's difficult to match versions right away in the project we are transferring. So, I wish there was an option to change items that appear as errors to warnings.

Sherif is very opinionated and we don't really want to add a configuration step, even if not mandatory.
While you're updating your dependencies, you can use the --ignore-rule multiple-dependency-versions option to ignore entirely the rule, or --ignore-dependency @dependency/name to ignore a specific dependency. That should help integrating Sherif in your CI immediately, and enable the rule later when you've fixed all dependencies errors.
Let me know if that would work for you.

Rather than ignoring it, I just wanted it to be checked every time in CI with warning option.
Thanks for the reply. We decided to use this for monthly checking rather than putting it in CI.

Thanks, I'll close the issue unless more folks are interested in the same feature.


added gps part numbers and built the interfaces for the OutputMixing and SendToActuators modules

I'll change the name of the sendToActuators module before this gets merged.

Name has been changed.

Looks good, builds 👍

@heyitslu I think you might need to re-approve


AAD token refresh

AAD token is properly refreshed using a callback that corrects the prefix.

API change check
API changes are not detected in this pull request.

@jay-most can you please point me to the fix of AAD Token refresh functionality in this PR?
I only see code changes which are not related to AAD Token refresh.


Develop functionality to check for new acquisitions

Implement acquisition checks for both Sentinel2 and Landsat8

Scrap support for landsat8

The geocore lite package contained runtimes for this functionality but has since moved to the goecore library within the acquisition-builder service


Test name detection fails when we use a function to construct the test

I'm using
it("script-empty", assertSchema("script-empty", "MyType", `No root type "MyType" found`));

Which runs
node '/Users/domoritz/Developer/UW/ts-json-schema-generator/node_modules/.bin/jest' '/Users/domoritz/Developer/UW/ts-json-schema-generator/test/invalid-data.test.ts' -t 'it("script-empty", assertSchema("script-empty", "MyType", `No root type "MyType" found`));'

But instead it should run
node '/Users/domoritz/Developer/UW/ts-json-schema-generator/node_modules/.bin/jest' '/Users/domoritz/Developer/UW/ts-json-schema-generator/test/invalid-data.test.ts' -t 'script-empty'

And you right-click somwhere in "script-empty" ?

Yes. My workaround is to highlight the whole word. Is this expected behavior?

Both ways should work.

this is the regex which is used
https://github.com/firsttris/vscode-jest-runner/blob/master/src/util.ts#L19

I can reproduce your issue.
╰─>$ nnode '/home/firsttris/Projects/someproject/packages/app/test/snapshot/formElements/FormInput.test.tsx' -t 'script-┬─[firsttris@e480:~/Projects/]─[15:27:41]root type "MyType" found'
The issue is the Regex i postet to you.
I verified on regex101.com

We need to update the Regex

@domoritz motiviated to contribute the correct regex?

Motivated yes, but won't have the headspace for the foreseeable future, sorry.

same issue here :dancer:

Regexes are fundamentally not powerful enough to cover all cases but I took a stab at a slightly more robust matcher: https://github.com/firsttris/vscode-jest-runner/pull/18.


STIX v2.1 does not handle lang granular markings

If you use the last example from STIX v2.1 § <IP_ADDRESS> (attached as test_granlang.json), and try to extract the markings for it, you get the following error:
Traceback (most recent call last):
  File "examp.py", line 5, in <module>
    print `obj.get_markings('description')`
  File "/Users/jmg/work/cti-i18n/p/lib/python2.7/site-packages/stix2/markings/__init__.py", line 53, in get_markings
    descendants,
  File "/Users/jmg/work/cti-i18n/p/lib/python2.7/site-packages/stix2/markings/granular_markings.py", line 47, in get_markings
    results.update([refs])
TypeError: unhashable type: 'list'

Attached are both examp.py and test_granlang.json both with a .txt extension.
examp.txt
test_granlang.txt

@jmgnc thanks for catching this bug. Essentially the markings API portion was outdated and did not include support for lang markings.
With these changes, calls like get_markings() by default will include BOTH markings to lang and marking-definition identifiers. If you are only interested in one you can toggle them like so: get_markings(marking_ref=False) or get_markings(lang=False) and that will exclude marking-definition markings or lang respectively.
This should be available on the next release.

Thanks, I'll test out the code shortly.


Support scrolling with page up and page down.

Not deleteToEndOfParagraph: yet ;)
This change implements scrolling via the page up and page down keys. The behavior is the same like in standard text views on macOS: it only scrolls the contents, but doesn't move the cursor.

@simonbs Sorry, my bad. I was kind of expecting this, but when I tested it, I only tested with edited files and did not catch it.
I updated the implementation and it should work now. There's one thing which is rather inelegant: https://github.com/simonbs/Runestone/blob/ea047f3e53397ddc98a394f40d7c115bb706b217/Sources/Runestone/TextView/Core/Mac/TextView_Mac.swift#L787-L788
I'm reading the scrollview's content size instead of using the ContentSizeService. But the scroll view is updated based on the contents, so it works for now.

@Lukas-Stuehrk Thanks for revisiting these changes.
I'm afraid that there are still some issues though. See the attached video. From seconds 7 to 8, I attempt to scroll a page down but it only scrolls 2/3 of a page down or so.
I'm afraid that the changes needed are quite elaborate, however, I have an idea as to how it can be implemented. I'll be happy to have a look at this a bit further down the road when a few more of the basics in the Mac app are in place 😊


Draft Objects should be notified

Description

There should be a notification of the amount of draft versions of each object.
DoD (Definition of Done)

Have number (for e.g. 1) next to the title of an object (According to the design) to notify that there is a draft version of an object

Testing

Peer review

Dependent on #67

we will need to follow up this with #116 in order to see how to use those drafts


MANGO-424. Feature: updated message DTO.

Codecov Report

Merging #178 (64a3faf) into develop (008920b) will not change coverage.
The diff coverage is 70.00%.

@@           Coverage Diff            @@
##           develop     #178   +/-   ##
========================================
  Coverage    59.69%   59.69%
========================================
  Files          202      202
  Lines         2970     2970
  Branches       110      110
========================================
  Hits          1773     1773
  Misses        1176     1176
  Partials        21       21

Flag
Coverage Δ

web
59.69% <70.00%> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

...piCommands/Messages/DeleteMessageCommandHandler.cs
71.42% <0.00%> (ø)

....BusinessLogic/Models/MessageDeleteNotification.cs
20.00% <0.00%> (ø)

...iQueries/Messages/SearchChatMessageQueryHandler.cs
58.44% <50.00%> (ø)

.../ApiCommands/Messages/EditMessageCommandHandler.cs
88.67% <66.66%> (ø)

.../ApiCommands/Messages/SendMessageCommandHandler.cs
100.00% <100.00%> (ø)

...gic/ApiQueries/Messages/GetMessagesQueryHandler.cs
100.00% <100.00%> (ø)

MangoAPI.BusinessLogic/Models/Chat.cs
83.87% <100.00%> (ø)

MangoAPI.BusinessLogic/Models/Message.cs
97.22% <100.00%> (ø)

...PI.BusinessLogic/Models/MessageEditNotification.cs
100.00% <100.00%> (ø)

MangoAPI.Domain/Entities/ChatEntity.cs
92.85% <100.00%> (ø)

Continue to review full report at Codecov.

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


Bump tree-sitter-kotlin

https://github.com/cursorless-dev/cursorless/issues/2642

cc @pokey (I can't assign)

Released in 0.31.3


Lite version of InternVL Chat

Hello,
Do you have any plan or guideline to create the internVL Chat with more lightweight version so we would have in total ~10B parameter? This might be good for the GPU poor user could run on their hardware.

Close as it might be similar for #138. I am interested in the OCR task.


refactor(rust): implement custom get_env

Current behavior
Environment variables are used everywhere and being parsed in different manners. This requires boilerplate code to handle them.

Proposed changes
Implement convinient custom get_env and get_env_with_default which are going to parse env variables and give the results right away.
fixes https://github.com/build-trust/ockam/issues/4549

Checks

[x] All commits in this Pull Request are signed and Verified by Github.
[x] All commits in this Pull Request follow the Ockam commit message convention.
[x] I accept the Ockam Community Code of Conduct.
[x] I have accepted the Ockam Contributor License Agreement by adding my Git/Github details in a row at the end of the CONTRIBUTORS.csv file in a separate pull request to the build-trust/ockam-contributors repository. The easiest way to do this is to edit the CONTRIBUTORS.csv file in the github web UI and create a PR, this will mark the commit as verified.

Thanks for the review! I don't really know how to fix
use of undeclared crate or module `std`

It doesn't really give me a hint about std::env :(

Right we need a bunch of config flags to do some conditional compilation. I have pushed a commit which should work.

Thanks Dan for your contribution, it really makes the library better!


dependency johnpbloch/wordpress moved to a new configuration causing issues

Description of your issue
When following along with the custom deployment steps everything works fine, the site deploys to Heroku with no issues. However upon updating WordPress' version, or simply installing a new plugin, the site will to fail to deploy. The issue arises once you have to update your composer.json / composer.lock files.
From my investigation this is due to changes made to the johnpbloch/wordpress dependency, which you can also read about here:
https://discourse.roots.io/t/johnpbloch-wordpress-moved-to-a-new-configuration-and-wp-goes-missing/9124
I've followed along with the recommendation made in the thread to

remove johnpbloch/wordpress from composer.json, run composer update, push to server
add johnpbloch/wordpress back, run composer update, push to server

However I am seeing this error in Heroku's logs:
2017-06-03T16:26:04.495459+00:00 app[web.1]: [03-Jun-2017 16:26:04 UTC] PHP Fatal error:  Uncaught Error: Call to undefined function WP_CLI\Dispatcher\get_path() in /app/vendor/wp-cli/wp-cli/php/WP_CLI/Runner.php:49
2017-06-03T16:26:04.495475+00:00 app[web.1]: Stack trace:
2017-06-03T16:26:04.495584+00:00 app[web.1]: #0 /app/vendor/wp-cli/wp-cli/php/WP_CLI/Dispatcher/CompositeCommand.php(37): WP_CLI\Runner->register_early_invoke('before_wp_load', Object(WP_CLI\Dispatcher\Subcommand))
2017-06-03T16:26:04.495723+00:00 app[web.1]: #1 /app/vendor/wp-cli/wp-cli/php/WP_CLI/Dispatcher/Subcommand.php(20): WP_CLI\Dispatcher\CompositeCommand->__construct(Object(WP_CLI\Dispatcher\RootCommand), 'server', Object(WP_CLI\DocParser))
2017-06-03T16:26:04.495842+00:00 app[web.1]: #2 /app/vendor/wp-cli/wp-cli/php/WP_CLI/Dispatcher/CommandFactory.php(73): WP_CLI\Dispatcher\Subcommand->__construct(Object(WP_CLI\Dispatcher\RootCommand), 'server', Object(WP_CLI\DocParser), Object(Closure))
2017-06-03T16:26:04.495950+00:00 app[web.1]: #3 /app/vendor/wp-cli/wp-cli/php/WP_CLI/Dispatcher/CommandFactory.php(34): WP_CLI\Dispatcher\CommandFactory::create_subcommand(Object(WP_CLI\Dispatcher\RootCommand), 'server', Array, Object(ReflectionMethod))
2017-06-03T16:26:04.496047+00:00 app[web.1]: #4 /app/vendor/wp-cli/wp-cli/php/class-wp-cli.php(466): WP_CLI\Dispatcher\CommandFactory::create('serve in /app/vendor/wp-cli/wp-cli/php/WP_CLI/Runner.php on line 49

Steps to Reproduce

follow the steps from https://github.com/PhilippHeuer/wordpress-heroku/wiki/Deployment
you can probably skip the heroku config & addons
deploy and verify that the installation is working
now run composer update (you don't need to change composer.json / add any new dependencies)
deploy again
the site should be failing now

Other Information
Git Commit/Version:
Running off of the latest which at this time is: https://github.com/PhilippHeuer/wordpress-heroku/commit/e8ed1d355397f57b55fe4cf90ed94f56d4e9e332
Thanks for putting this template together, I'm looking forward to getting everything work.

Hey, thanks for your report.
I could reproduce your error, i didn't specifiy the exact version in the dependencies - so it updated to WP CLI from 1.1.0 to 1.2.0 which broke it.
I still need to look at what changed to get it working with the new version, but for now i set the dependency version to 1.1.0 so that it works again.
I specified exact versions for all dependencies to prevent sth. like this from happening again.

Sweet, thanks mate.


Added CSS Loader

Added CSS loader
#hacktoberfest

Added CSS loader #hacktoberfest

I think you didn't add the right(accroding to the rules) CSS Loader.
Update the code according to current numbering of the css loader then make another PR.

Dear Rohit Sir,
First of all thank you for looking into my pull request and noting the
minute details. But I am unable to understand, could you be more specific
about the issues.
Thanks
Regards
Satwik Rai
On Tue, Oct 4, 2022 at 12:05 PM Rohit Gangwar @.***>
wrote:

Added CSS loader #hacktoberfest
I think you didn't add the right(accroding to the rules
https://github.com/rohit8020/css-loaders/blob/main/README.md) CSS
Loader.
Update the code according to current numbering of the css loader then make
another PR.
—
Reply to this email directly, view it on GitHub
https://github.com/rohit8020/css-loaders/pull/22#issuecomment-1267459590,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/A3BWLBQWSNIN2MAG3AUWE33WBR5YHANCNFSM6AAAAAAQ42F4D4
.
You are receiving this because you authored the thread.Message ID:
@.***>


Unit tests for modules.ts

Related Issues

closes #5052
Short Description and Why It's Useful

This is the unit tests for modules.ts as the issue #5052 requires
Screenshots of Visual Changes before/after (if There Are Any)

Which Environment This Relates To
Check your case. In case of any doubts please read about Release Cycle

[x] Test version (https://test.storefrontcloud.io) - this is a new feature or improvement for Vue Storefront. I've created branch from develop branch and want to merge it back to develop
[ ] RC version (https://next.storefrontcloud.io) - this is a stabilisation fix for Release Candidate of Vue Storefront. I've created branch from release branch and want to merge it back to release
[ ] Stable version (https://demo.storefrontcloud.io) - this is an important fix for current stable version. I've created branch from hotfix or master branch and want to merge it back to hotfix

Upgrade Notes and Changelog

[x] No upgrade steps required (100% backward compatibility and no breaking changes)
[x] I've updated the Upgrade notes and Changelog on how to port existing Vue Storefront sites with this new feature

IMPORTANT NOTICE - Remember to update CHANGELOG.md with description of your change
Contribution and Currently Important Rules Acceptance

[x] I read and followed contribution rules

Hi @Fifciu, Thanks for your response. I have updated the changelog.

Please resolve conflict @TamTran72111

Great, thanks a lot!


Npm package not found.

https://www.npmjs.com/@reason-react-native/paper is not available.

Still not available, is anybody still maintaining this repo ?

yarn add https://github.com/reason-react-native/paper should help until this lands on npm.

Add this in README

Now it is!


More info at: https://travis-ci.com/Qiskit/qiskit-terra/jobs/323896854

Captured traceback:
~~~~~~~~~~~~~~~~~~~
    Traceback (most recent call last):
      File "/home/travis/virtualenv/python3.6.10/lib/python3.6/site-packages/qiskit/providers/ibmq/api/session.py", line 230, in request
    response.raise_for_status()
      File "/home/travis/virtualenv/python3.6.10/lib/python3.6/site-packages/requests/models.py", line 941, in raise_for_status
    raise HTTPError(http_error_msg, response=self)
    requests.exceptions.HTTPError: 400 Client Error: Bad Request for url: https://api-qcon.quantum-computing.ibm.com/api/Network/ibm-q/Groups/open/Projects/main/devices/ibmq_16_melbourne/queue/status

This can be closed it's being caused by an ibm cloud outage right now which is causing unreliable connections to the ibmq api. Moving forward this will be addressed by removing any dependency on the ibmq api from the unittests in: https://github.com/Qiskit/qiskit-terra/pull/4296


win: CREATE_NO_WINDOW when stdio is not inherited

Resolves #1625

To clarify:
CREATE_NO_WINDOW does not appear compatible with inherited console handles (no console, and hence console handles, get created). MoarVM showed a regression post v1.15.0 because it uses inherited stdio handles by default, and -always- sets UV_PROCESS_WINDOWS_HIDE. The problem was not immediately obvious on nodejs because it defaults to stdio pipes, but indeed a deadlock can be shown with the right parameters:
node -e "const cp = require('child_process'); { const bat = cp.spawn('cmd.exe', ['/k', 'dir'], { stdio: 'inherit', detached: false, windowsHide: true }); }"

In the case of MoarVM this PR fixes the regression introduced in https://github.com/libuv/libuv/commit/b21c1f900c55572917d64c5e208c3eb8850ffd18
In the case of nodejs this PR should bring back the console 'blip' but only if stdio: 'inherit' is used, with the possible caveat (bonus) that it no longer deadlocks.

Sorry, forgot about this. I'll land this tomorrow.
CI: https://ci.nodejs.org/view/libuv/job/libuv-test-commit/709/

Landed in https://github.com/libuv/libuv/commit/48ba92c93ecdb3719436f44fe26c81a5d2da642f

@bzoz, yeah will do that

Landed in https://github.com/libuv/libuv/commit/491848a0ad20031fa26bfb4a934b82293e0f7732 with the correct author.

Thanks!


[suggestion] Add --output=json support for 'cr namespace-list'

It would be nice to have a computer readable format for ibmcloud cr namespace-list.
Say, --output=json?  It's used elsewhere...
See #139 for a reason for why it might be nice.

Thanks for the suggestion here. We have an enhancement request open to add --output=json to some more of the cr commands. I can't guarantee a timeframe, but it is on the radar.

Thanks for the suggestion here. We have an enhancement request open to add --output=json to some more of the cr commands. I can't guarantee a timeframe, but it is on the radar.

Link to the enhancement request?

Link to the enhancement request?


Fix asteroids demo input and visuals

Fixed background, added input mapping (why is it gone though?), added basic controls help

I might've deleted input mappings while trying it fix project


Convert almost all classes to dataclasses

It makes the code a little bit more efficient in some places, but it also provides us with a PR to release on.

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

Comparison is base (7743581) 64.49% compared to head (cf9f502) 63.39%.

Additional details and impacted files
@@            Coverage Diff             @@
##           master     #184      +/-   ##
==========================================
- Coverage   64.49%   63.39%   -1.10%
==========================================
  Files           1        1
  Lines        1611     1620       +9
  Branches      374      347      -27
==========================================
- Hits         1039     1027      -12
- Misses        470      486      +16
- Partials      102      107       +5

Files
Coverage Δ

src/datalad_installer.py
63.39% <100.00%> (-1.10%)
:arrow_down:

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

@yarikoptic Ping.


Questions/Comments/Feedback thread

A place for generic feedback and questions, anything goes. For bug-reports, site requests and feature requests, please open a new issue.

I'm having some problems getting achewood to work. The little dialog to say I was new to using the script triggered, and I went through the settings (half-understanding most of them) but I can't get any of the features to work on achewood itself.
As an aside, does the script have a way to display alt-texts on comics?

It should display the alt-text automatically by default. I have updated the code for the site now, so it should work if you update the script.
But yes, the settings are a bit over-complicated. I should probably add a simplified version and hide the other options by default.

Ah works perfectly now, cheers.

Can we make this multilanguage?

@Tmp341 Make what multilanguage? Do you want to translate the script to some other language? I so, I can add some framework to simplify the process.

Script i mean. Like, we can use "russian word for next" other than "english next".

@Tmp341 If you want to translate the script to your language, I can start working on adding a localization framework to simplifying the process. It will be some work, but it shouldn't be too bad.
It might force some restructuring though, since we'll probably want the translations in separate files so that changing the translations won't cause a conflict with changing the main script. I probably want to split the script to put the site implementations in a separate file as well, and then use a script to build the whole project together. In other words, this change might take some time.

On the other hand, if we want to go with the lazy solution (at least for me ;-) ), you can just fork the repository and just translate all (displayed) strings in the copy. That will of course cause more work in the long term, since you will have to merge all upstream changes to keep the translated copy updated.
If so, we could create a shared repository so I can handle most of the merges. There shouldn't be too much  merge conflicts.

We might also go with a compromise between these paths. For example, you can start translating in a fork and then later, when we have the framework I can extract the translations and put them in a separate translation-file so we'll avoid the merge conflicts.
Feel free to ask if any of that was unclear or if you have other questions (or if I completely misinterpreted you).

Nope. No problem here. But here is a problem, i'll be in military service for 1 year, until November 2017. Before that, i can't do anything. I'll join my team next week. But you can keep the idea.


Copy button not consistently visible on Edge browser when window size is reduce

Prerequisites

[X] I have searched for duplicate or closed issues
[X] I have validated any HTML to avoid common problems
[X] I have read the contributing guidelines

Describe the issue
I've noticed that when reducing the size of the browser window in the Edge browser, the copy button for code snippets in Bootstrap does not always appear. Sometimes it's visible, but other times it's hidden and requires scrolling to become visible.

The copy button should always be visible on the page, regardless of the window size or device used to access the page.

The copy button is not consistently visible on the page when reducing the size of the Edge browser window, making it difficult for users to copy code snippets.
Reduced test cases
The addition of a media query that particularly targets Edge and makes sure the button is always displayed at all window widths is one potential fix. Another option would be to change the button's CSS to increase its adaptability to various screen widths.
What operating system(s) are you seeing the problem on?
Windows
What browser(s) are you seeing the problem on?
Microsoft Edge
What version of Bootstrap are you using?
v5.3(alpha)

Confirmed issue. Can see the same thing on Firefox (macOS). Thanks for reporting this issue @mootezaloui.

We hide the button on small screens IIRC. It's unrelated to the browser but was decided at some point to be this way.

Hi @julien-deramond , @XhmikosR ,
can I take this issue ?
I have found its root cause.
as mentioned by @XhmikosR, we just need to remove that display: none for small view and set display:block property for all view
Please do let me know
Thanks

This was done by design by mdo, unsure what his take is now.
On Sat, Apr 8, 2023, 16:53 surajgjadhav @.***> wrote:

Hi @julien-deramond https://github.com/julien-deramond , @XhmikosR
https://github.com/XhmikosR ,
can I take this issue ?
I have found its root cause.
as mentioned by @XhmikosR https://github.com/XhmikosR, we just need to
remove that display: none for small view and set display:block property
for all view
Please do let me know
Thanks
—
Reply to this email directly, view it on GitHub
https://github.com/twbs/bootstrap/issues/38382#issuecomment-1500896747,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AACVLNIJCK33WPYTC4A2RH3XAFUWZANCNFSM6AAAAAAWNB4VHQ
.
You are receiving this because you were mentioned.Message ID:
@.***>


Nrfx 6088 extend can api test

tests: drivers: can: api: Set default CAN state before each test
Tests assume that CAN is started.
When previous test stops CAN and fails on assertion then remaining tests may fail.
Start CAN before every tests. Ignore error code returned when starting CAN that is already started.
tests: drivers: can: api: Add negative test for can_send()
Check error codes when sending invalid frames:

too big data payload;
wrong set of flags.

tests: drivers: can: api: Check value returned by can_get_bitrate_max()
Function can_get_bitrate_max() shall return maximum supported bitrate for the CAN controller/transceiver combination.
Check if that bitrate can be set with can_set_bitrate_data().
tests: drivers: can: api: Check value returned by can_get_bitrate_min()
Function can_get_bitrate_min() shall return minimum supported bitrate for the CAN controller/transceiver combination.
Check if that bitrate can be set with can_set_bitrate().
tests: drivers: can: api: Add negative test for can_set_bitrate_data()
There is negative test for too high data bitrate.
Add test that checks too low data bitrate.
tests: drivers: can: api: Add negative test for can_set_bitrate()
There is negative test for too high bitrate.
Add test that checks too low bitrate.
tests: drivers: can: api: Add negative test for can_add_rx_filter()
Check that error is reported when CAN filter is added without callback function.

This PR relates to https://github.com/zephyrproject-rtos/zephyr/pull/76298

What does "Nrfx 6088" mean?

What does "Nrfx 6088" mean?

"NRFX-6088" is a task number in our JIRA.

What does bitrate of 0 bit/s mean?
I see, vale of 0 is returned by can_get_bitrate_min()
"Get the minimum supported bitrate for the CAN controller/transceiver combination."
https://docs.zephyrproject.org/latest/doxygen/html/group__can__interface.html#ga343456749eec6144a91bacae0d94b114
However, when I try to set such bitrate, I get -EINVAL.

What does bitrate of 0 bit/s mean?

It means the CAN controller has no documented lower bitrate limit.

I see, vale of 0 is returned by can_get_bitrate_min()
"Get the minimum supported bitrate for the CAN controller/transceiver combination."
https://docs.zephyrproject.org/latest/doxygen/html/group__can__interface.html#ga343456749eec6144a91bacae0d94b114
However, when I try to set such bitrate, I get -EINVAL.

Questions like this make uncomfortable accepting any CAN related code changes from you. How would you expect a bitrate of 0 bits/second to be acceptable?

What does bitrate of 0 bit/s mean?

It means the CAN controller has no documented lower bitrate limit.

It is undocumented feature.

I see, vale of 0 is returned by can_get_bitrate_min()
"Get the minimum supported bitrate for the CAN controller/transceiver combination."
https://docs.zephyrproject.org/latest/doxygen/html/group__can__interface.html#ga343456749eec6144a91bacae0d94b114
However, when I try to set such bitrate, I get -EINVAL.

Questions like this make uncomfortable accepting any CAN related code changes from you. How would you expect a bitrate of 0 bits/second to be acceptable?

I consider this a personal attack. I will consult my supervisor on how to proceed.

Fallout from misunderstanding the CAN_FRAME_ESI flag fixed here: https://github.com/zephyrproject-rtos/zephyr/pull/80380

Fallout from misunderstanding the CAN_FRAME_ESI flag fixed here: #80380

"Fix the test for sending frames with the CAN_FRAME_ESI flag set. Sending frames with this flag set in software is never allowed."
"The test introduced in https://github.com/zephyrproject-rtos/zephyr/commit/8023a58c2a463cfcda1ffeaf41b0ea853bba0178 is wrong and holding back both local pre-v4.0.0-rc1 testing and PRs targeting v4.0.0-rc1."
That proves what You stated - I don't have sufficient knowledge to work on task "NRFX-6088: Extend testing for CAN".
I asked to assign that task to somebody else.
I apologise for the inconvenience.

From the other side:
API states that can_send() shall return
"-ENOTSUP	if an unsupported parameter was passed to the function. "
https://docs.zephyrproject.org/apidoc/latest/group__can__interface.html#ga446ee31913699de3c80be05d837b5fd5
You wrote "Sending frames with this flag set in software is never allowed."
IMHO, there should be more tests:
Scenario 1:
What I proposed, CONFIG_CAN_FD_MODE=y, and can_set_mode(CAN_MODE_FD) and .flags = CAN_FRAME_ESI (as this caused failure in https://github.com/zephyrproject-rtos/zephyr/pull/76134 -> driver was not detecting invalid use)
Scenario 2:
What You proposed, CONFIG_CAN_FD_MODE=y, and can_set_mode(CAN_MODE_FD) and .flags = CAN_FRAME_FDF | CAN_FRAME_ESI (as this would cause failure in fix for fail in scenario 1 in https://github.com/zephyrproject-rtos/zephyr/pull/76134 -> still, invalid use)
Correct check for scenarios 1 and 2 is implemented here: https://github.com/zephyrproject-rtos/zephyr/blob/main/drivers/can/can_mcan.c#L936
Scenario 3 in "classic can":
CONFIG_CAN_FD_MODE=n, and .flags = CAN_FRAME_ESI
Scenario 4 in "classic can":
CONFIG_CAN_FD_MODE=n, and .flags = CAN_FRAME_FDF | CAN_FRAME_ESI
Correct check for scenarios 3 and 4 is implemented here: https://github.com/zephyrproject-rtos/zephyr/blob/main/drivers/can/can_mcan.c#L948


Add download, share, citation and follow icons for buttons

I have coded the buttons like this but there maybe a better way of doing this. @will-byrne or @scottaubrey ?


Dynamic single selection dropdown reset other dropdown

After selecting a dropdown value (using ngmodel as array) other dropdown values are set by last selected item. we are using dynamic form with dynamic dropdown.

Please refer https://cuppalabs.github.io/angular2-multiselect-dropdown/#/usingInList or write to me on my email for implementation help.


mat: VecDense.CopyVec panics when copying another VecDense of diffrent length

What are you trying to do?
Use CopyVec to copy a smaller vector into a bigger vector
What did you do?

https://play.golang.org/p/BWgtRJx9vDC
What did you expect to happen?
Copy the smaller VecDense into the head of the bigger one should be allowed according to documentation of CopyVec.
What actually happened?
Code panics
What version of Go and Gonum are you using?

go version go1.12.6 windows/amd64
gonum.org/v1/gonum v0.0.0-20190628223043-536a303fd62f
Does this issue reproduce with the current master?
yes

Thanks. This is a result of a new check in blas64.Copy. I'll send a PR soon.


New release 0.4.0

https://github.com/toml-lang/toml/blob/v0.4.0/README.md

Fixed this back in February but I forgot to push. See c54810e


Field level validation & warning

Summary
Since v7.0.0 the behaviour of Field level validation changed/was fixed, but had a significant side effect. It has caused a lot of ongoing confusion, and this was/is at least a documentation issue. This ticket is for centralizing any further discussion around this issue. Everything in this ticket applies to field level warnings as well. FieldArray lags a little, see #4081.
What is the history?
In v6.8.0 and prior component field level validation used the initial value of the validate prop provided only. After a Field mounted its validation behaviour could not be changed.
Issue #3012 and subsequent pull request #3094 addressed this in v7.0.0.
#3094 was a fix, which happened to use re-registering as it's mechanism. From v7.0.0 onwards a change to the validate prop would apply during subsequent sync validations. From v7.4.2 this was updated to run a sync validation immediately upon the detection of a new validate.
A broken pattern
If you never needed to change the validate prop after first render then before #3012 you could usefully use a higher-order-function inline to generate the validate function. After this change, unless memoized, the use of a higher order function to generate the validation function inside the render will cause the Field to re-register / re-run validations. Example:
<Field
   component="input"
   name={props.name}
   validate={getMax(props.max)} // never do this in v7.0.0 and above (unless getMax is memoized)
>

How to field level validate your Field:
The golden rule is don't change (according to ===) the validate prop unless you intend to between renders.
All of the following equally applies for passing an array e.g. [maxAge, isRequired]
# 1. If you have a fixed validation function for the whole lifecycle of your Field (trivial case):
Just make sure that your validation function is not created inside the render. E.g.
// static definition outside the Field.
const minAge =  value => (value < 18) ? 'Too young' : undefined

const Age = ({ name }) => {
    // do not create minAge here.
   return (
     <Field
       component="input"
       type="number"
       name={name}
       validate={minAge}
     />
  )
}

# 2. If you have a validation function that changes while your Field is mounted:
Since v7.0.0 this is now possible. Just like above, but with e.g.
validate={this.state.applyValidator ? minAge : undefined}

# 3. If you need to generate a validation function based on props when rendering your Field component that will change as your component receives new props:
class MyFieldCreator extends Component {
   validate = (...args) => {
      return getMax(this.props.max)(...args)
   }
   render() {
     <Field
        component="input"
        name={this.props.name}
        validate={this.validate}
      >
   }
}

Memoization can often be used instead of any of the above options. If you are doing more complex memoization involving closures, be sure to create a new memoizer per usage to ensure that no stale closure values are passed between components. The same applies if you're using e.g. memoize-one a new memoized validator needs to be created per component.

Other issues
Disagreement
The react docs accept the use of the inline approach when it comes to simple cases like buttons. In saying that it was a pretty big change in 6.8.0 that affected a lot of developers (possible semvar mixup, though it was fixing a bug of how it was supposed to behave). It's been expressed that using higher order functions inline is extremely desirable. The answer to this is sorry but the need to fix #3012 is more important/meaningful.
Looking forwards (a hoped for enhancement):
Feature request to those interested [Edit: as per #3724,#2881] is that this whole business would be a lot easier if the inline validation provided fieldProps as another param (value, allValues, formProps, name, fieldProps), even if it this is getting a tad overcrowded. This would allow you to skip all the constructor & componentWillReceiveProps aspects and just:
const minAge = (value, allValues, formProps, name, fieldProps) => {
  const { min } = fieldProps
  if (value < min) {
    return 'Too young'
  }
}

<Field
  component="input"
  type="number"
  name={name}
  min={min}
  validate={minAge}
>

The "above the Field" approaches noted above would still apply in some cases, e.g. building different arrays of validators depending on a prop like field type (i.e. the component is not known in advance).

After reading this, I am as, or more, lost than before. It would be helpful to show exactly how it should be done and not, as in some situations above, how it should not be done. I, for one, already know the latter. So, the education actions alluded above needs to be worked on more emphatically  and certainly more didactically.

@BernardA Thank you for your feedback. I've added:

The golden rule is don't change (according to ===) the validate prop unless you intend to between renders.

I've also added "don't do this" comments next to the two snippets above that represent bad code.
Everything besides those are suggested practice.
It is certainly my intention to clarify, and not declarify the situation, but in this ticket I am also trying to address a variety of concerns / people - from @erikras to newbies, and provide context to the current state of the library.

I have the same issues after trying to follow above. The behavior continues that, if the first form field does not generate error, the remaining won't either.
Form field example:
const EmailField = ({name}) => {     return (         <Field              name="fos_user_registration_form[email]"             type="e-mail"             id="fos_user_registration_form_email"             placeholder='e-mail'             component={renderField}              validate={[required, isEmail]}     />     ) }
Then on the component:
`const RegisterForm = (props) =>{
const { handleSubmit, pristine, reset, submitting } = props;
if(props.error){
    return (

{ props.error.messageKey}

    )
}else {
    return (
        <form
            name="fos_user_registration_form"
            onSubmit={handleSubmit(props.submitRegister)}
        >

                <EmailField />

.......
export default reduxForm({
form: 'RegisterForm'
})(RegisterForm);
`

@BernardA please make a sandbox / stackblitz reproduction of your issue.

@danielrob . I had already done a sandbox with my original question.
https://codesandbox.io/s/m3nqpqommp Here it is.
I updated one of the components as per above. I also left the old version.
The other forms I left with the original setup.
The component is:
/pages/common/register/containers/register.js  (The old version, marked as OLD is in the same folder ).
To reproduce the issue:
1 -
On the sandbox browser click on the "register" button.
Fill in the form with no errors, except that input a password confirm that does not match
You should receive no error.
2-
Refresh the page
Fill in the form again and this time input an invalid email.
You should now receive an error and also errors in any subsequent invalid field.
You will also observe that the submit button will not be disabled in most cases, particularly when going back and forth with invalid/valid fields.

@BernardA you cannot do maxLength(180) as i clearly updated above:

validate={getMax(props.max)} // never do this in v7.0.0 and above

thanks @danielrob, You are right, of course. My bad.
This is better, but still it does not work as it should.
On the password confirm field, once the error is triggered it won't go away even after the fields are made to match.
I updated the sandbox.

@BernardA I moved assisting your question to back to your original issue at #4013.

@danielrob Can you please explain a bit more on how can i have conditional validate methods passed to  Basically i want to have a custom maxLength and minLength validation checks done based on the CardType. I tried using the approach mentioned in the section "If you need to generate a validation function based on props when rendering your Field component that will change as your component receives new props:"
but that doesn't work.

@siddhant91 . Please take a look at this sandbox. There's a working setup there.
https://codesandbox.io/s/m3nqpqommp

@siddhant91 there's definitely a bug in here, #3909 should (help) fix this, awaiting the 7.4.0 release.

@siddhant91 in the meantime I've updated the example with a far better approach, apologies for misguiding you there.

@danielrob  Thanks for the Update , if there any expected date for 7.4.0 release ?
Also in the example i see that we have validation methods set as
const maxLength180 = maxLength(180);
const minLength8 = minLength(8);
and then this gets passed to the validate prop.
But these never change , and what i need to do is based on the condition on every render i need to either send minLength8 or some other validate method.
Hope that we have the release soon , so that this can be fixed.

@siddhant91 yep, so the new updated last option should deal to this case for you:
class FieldFactory extends Component {
   maxLength = (...args) => {
      return maxLength(this.props.max)(...args)
   }
   minLength = (...args) => {
      return minLength(this.props.max)(...args)
   }
   render() {
     <Field
        component="input"
        name={this.props.name}
        validate={[this.maxLength, this.minLength]}
      >
   }
}

Let me know how you get on.

@danielrob How exactly are you setting the character length in your example?

e.g. <FieldFactory max={10} min={12} />. If you're in this scenario it is probably a factory scenario (you are creating fields from some set of field schema), so perhaps it would instead be this.props.schema.max and  but you get the idea.

@danierob , i am able to pass custom validation method now to the Field Component with the new release of 7.4.2 . However if i set some initialValues to my Form and also set enableReinitialize: true , there seems to be an infinite loop of register and unregister Field which happens
is there any more configuration or prop that i have to pass on ?
My Code is something like this
`const validate = [
this.required()),
this.minLength(validCardLength || 13),
this.maxLength(validCardLength || 19),
];
<Field
component={FormFieldInput}
{...InputProps}
validate={validate}
/>`
i have around two to 3 fields with an form which need the validation to be updated on the fly.

@danielrob Thanks for this. I believe this is the issue I was having.
Could you take a look at the sandbox and show me how to fix this?
I'm not sure if any of the approach you mentioned is applicable in my case.
https://github.com/erikras/redux-form/issues/4102
Thanks!

@danielrob after the unexpected and confusing bugs I uncovered due to memoization, I'd personally prefer if instead of saying

Memoization can often be used instead of any of the above options

You only mention memoization in a warning section.  This language needs some work to make it easy to understand, but then again, we're not dealing with a simple and easy-to-understand pitfall to begin with.

Warning: if you are trying to memoize your validator creators
And your validator creator accepts a function option to customize it's behavior (for example, a function that skips validation in certain cases), you should be aware that there will be problems if the customization function is a closure.  This is because only the first customization function's closure makes it into the cache, and other component instances will get the memoized validator which uses the closure from another component.

@danielrob I hope you'll consider leaving # 3 out of the docs as well.  I feel uneasy about components that only do something based upon their initial props, and ignore later changes to those props, because I believe it would often be surprising to people using the component unless it is very loudly documented.  I don't want to see examples that encourage such a pattern, and I think # 4 will solve most cases that # 3 is trying to.

Here's an easier-to-understand example for # 4:
class CommentField extends Component {
  validateComment = (value) => {
    const {minCommentLength} = this.props
    if (!value || value.length < minCommentLength) {
      return `${minCommentLength - value.length} to go...`
    }
  }
  render() {
    return (
      <Field
        component="input"
        name={this.props.name}
        validate={this.validateComment}
      >
    )
  }
}

@danielrob the idea of passing additional props from Field to the validators is great!  It will reduce the need for validator creators and the temptation to memoize them, since it will be possible for libraries to export a single validation function instance that can be customized by properties passed to the Field.
I think maybe supporting a specific validateOptions prop on Field instead of arbitrary extra props will increase flexibility and reduce interference with existing props needed by the Field and especially its component, and enable more reusable validators (shallow-equal changes to validateOptions would be ignored):
function range(value, allValues, formProps, name, validateOptions) {
  const num = parseFloat(value)
  if (!Number.isFinite(num)) return 'must be a number'
  if (num > validateOptions['<=']) return `must be <= ${validateOptions['<=']}`
  if (num < validateOptions['>=']) return `must be >= ${validateOptions['>=']}`
}
<Field
  name="someValue"
  validate={range}
  validateOptions={{
    '>=': 0,
    '<=': 10,
  }}
/>

Also I hope to see all arguments to validators after value get collapsed into a hash in the next breaking change.

@jedwards1211 sorry for the late reply. Thanks for those suggestions. I agree, I've removed the prior option #3. Regarding memoization - I can see you hit a pain point there, and I agree it's nice to have a reminder that memoization has it's quirks.

@danielrob thanks!
You might want to clarify that you mean per component instance rather than component class.
Also, just so you know...it is even possible to screw up the closure if doing one memoizer per component instance.  Not as likely, but the most sound advice is, make sure you are not memoizing any functions that use variables from the containing scope.  It's pretty pointless to create a memoizer per component instance anyway since at that point you can just create the validators directly when the component instance is constructed.

Possible to add this to the doc? It will be a really really good tips and for best practice to avoid certain situation.

This might be an edge case. Looking for clarification on how to do this with a connected form that already has validation.  Returning undefined in the validate prop still runs the top level validation for the form. If this is per field level, I would imagine that the field level validation should override the validate object. The reasoning behind this is partly due to how we are managing disabled fields, if the condition is true, then I want to negate the validation for those fields.
Is it better to unregister the field at that point?

It might be worth adding that you can use the new React.useMemo to memorize the validator closure as a work around.
import React, { useMemo } from 'react';

const Form = ({ externalValue }) => {
 const memorizedValidator = useMemo(
        () => (value) => ( value > externalValue ? undefined : "validation error"),
        [externalValue]
    );

  return (
    ...
    <Field ... validators={[memorizedValidator]} />
   ...
  )
};

Related #4724

how to validate for select field in redux form

I shouldn't say this in public because it's very shameful, but hear this. I was having this insecurity mindset due to my wife sudden strange behavior, I tried to figure it but it wasn't possible, I decided to investigate her phone, luckily my big bro referred to contacted (hack4net8@gmail .com) to help me in hacking my wife phone, when the results came out i saw that my wife has been communicating with someone, I viewed their whatsapp conversations, facebook, email hangout, and more. To be honest I couldn't believe because I thought it was just dream. However am here to review and thank (hack4net8@gmail .com)


Remove jQuery dependencies from gi_load.js

gi_load.js used some jQuery utilities, but only in a shallow way.
I have a project which can profitable use gi_load.js but is React rather than jQuery. So I went in and removed all the jQuery dependencies.

jQuery.ajax() → XMLHttpRequest()
jQuery.extend() → Object.assign()
jQuery.type() → (typeof val === 'string' || val instanceof String)
$('<script>') → document.createElement('script')

Took some fiddling to figure out the ajax() arguments I was using, but it turned out to be simple enough.

This is all done. I only created this issue to have somewhere to track problems if problems occur which, hopefully, they won't.