How does pipenv know the virtualenv for current project ?

I have just setup a python project using pipenv. One thing I want to know is where does pipenv store the mapping of project directories to virtualenvs.
To be clear, I am running the following command:
sacjain-macOS:coursera-classification sacjain$ pipenv --venv
/Users/sachinjain/.local/share/virtualenvs/coursera-classification-iTBt6WsT

I checked Pipfile and Pipfile.lock, I assumed this information should be present in Pipfile but it was not there.
Q2. How can we install a specific version of package using pipenv ?

The virtualenv’s name is the project’s root directory name, plus the hash of the full path to the project root. This guarantees the name to be unique and predictable as long as you don’t move the project. (AFAICT this name generation logic is an implementation detail that should not be relied on.)
To install a specific version of a package, use the same syntax as you would with pip and requirements.txt, package==version (e.g. django==1.11.0).

@uranusjr This means that if I rename the directory my project's virtualenv will be lost. That's bad. It can be a common use case to rename a directory and users may fall into this and wonder how their environment stopped working.
I would suggest to fix it and make an entry into Pipfile if that's possible. Or create another .pipenv file to store such metadata in each project directory.
What do you suggest ?
Thanks for answering both the questions!

Hey @sachinjain024, we've had a few discussions on the local metadata file but the maintainer consensus has been that pipenv won't be supporting that at this time.
The directory path identifying a project was something that was implemented early on because projects with the same name, or multiple copies of the same project, were causing accidental overwriting of environment state.
In practice, we've found far fewer people have had issues with the location being part of the environment than silently having their work overwritten. Pipenv is an deployment management tool after all, so moving the directory should be a one command fix.

Thanks @nateprewitt. It makes sense to quickly jump to easy implementation. Suppose I rename a project at later stage then it means my environment does not exist.
So what should I do in this situation ?

Resetup the environment because I have Pipfile already which has the packages information so it will be easy to resetup the env.
Somehow rename the virtualenv directory too
???

What do you suggest in this case ? Just curious in case I get in this situation in future.

You can use pew cp to easily copy the existing virtualenv, but 1. would be the more “canonical” way to it I think.

@sachinjain024, whenever you need to move your project directory, you should only need to run pipenv install to get back to a working state. This will create an environment for you with the new hash and reinstall everything from the lockfile identically to the previous installation it was created with.
If you find yourself doing this often, you may want to use pew rm old_project-a3de90 to cleanup.

I wouldn't recommend using pew cp unless you're modifying the virtual environment outside of pipenv. In that case, I think we'd have to consider that a "voided warranty" scenario, because there are all sorts of changes we can't account for reliably.

Thanks @nateprewitt @uranusjr. Closing this ticket.

Set export PIPENV_VENV_IN_PROJECT=1 in your bashrc / shell configuration.
(Or change your shell scripts to create a venv at $PROJECT/.venv and then
pipenv will has that)
On Mon, Mar 19, 2018 at 6:28 AM wvxvw<EMAIL_ADDRESS>wrote:

This is one of the worst ideas that came out of pipenv so far. Here's why:
I work in a company, where Python is used for test automation of a lot of
internal projects. One tester usually works on a dozen of those. By
convention, all test code for a project lives in directory called tests.
This means, that each tester now has a bunch of virtual environments all
called something like ~/.local/share/virtualenvs/tests-hKjFddnZ -
awesome! It is a human nature to forget to switch virtual environment, so,
every few days I'm called to a different workstation because the the person
at that workstation thinks that they installed the package they need, they
ran pipenv install, but the imports in the code don't work. Not only
that, the orphan virtual environments accumulate over time, but since all
of them have nondescript names, there's no way to tell if I'm deleting
environment that's not in use, or the one that's actually been used. This
means that in CI, we create dozens, if not hundreds of virtual environments
daily. There's no way anyone can keep track of environments that have
essentially random names, and there's just too many of them, so we have to
delete all of them at least once a day. We pay a huge toll in waiting times
only because of this super smart decision made by pipenv and someone in
our company, who decided to use it...
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/pypa/pipenv/issues/796#issuecomment-374211264, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ABhjqyABdDHCB8WMm-hJwdkNptVlh8fuks5tf7KBgaJpZM4Pp3kf
.

@jtratner  Then why do I need pipenv if I'm going to create virtual environment by hand?
Virtual environment is a piece of work on its own. It's lame everywhere and is broken on Windows (it assumes that on MS Windows, of all places, the default home directory is called "~"). I was hoping that if someone was to redo PIP and virtual environment, they would, you know, fix the obvious errors of their predecessors... instead, there's this mess multiplied by a layer of incompatibility.

You’re making wrong assumptions. Pipenv does not redo either virtualenv or pip. It builds on them.

@uranusjr that's a reading comprehension problem. I know very well, what pipenv does, since I spend much more time debugging its code than I'd like to. To redo virtual environment and PIP is the project's stated goal. That, instead of fixing them it decided to use them "as is" is another huge mistake on the part of pipenv, followed by using click library, and the list goes on.

To redo virtual environment and PIP is the project's stated goal.

Where did anyone state this?

@uranusjr I read all of https://docs.pipenv.org and https://docs.pipenv.org/basics/ , and unless I missed it, it never mentions where the virtualenv directories are installed, nor does it warn anybody that renaming or moving the project directory will cause the virtualenv directory to have to be recreated.
PIPENV_VENV_IN_PROJECT is confusingly named, since pipenv does not use venv shipped in the standard library, it uses virtualenv, which is a different project.
I'm just trying to provide feedback on the things I tripped over as I'm familiarising myself with this project.

@Flimm the point is to abstract this information. If you know how other tools that manage virtualenvs work you should already know that moving folder of virtualenvs makes them un-findable. If you aren’t familiar, you probably won’t go digging for this in the first place.
As for what backend library we use to generate virtualenvs and the naming of environment variables the former isn’t that important and the latter is shorthand that is widely accepted. While details are important, this one doesn’t feel like it is causing anyone any issues, and your primary objection seems based on you being unsure which backend we use to put a python executable in a folder. If you encounter bugs please report them. We really aren’t going to change environment variables just because.
The environment variable is readily available in the docs: http://pipenv.readthedocs.io/en/latest/advanced/#configuration-with-environment-variables so you probably didn’t read all of them if you didn’t see it

@techalchemy By other tools I guess you mean something like virtualenvwrapper. To be honest, I went for years without using tools like that, and I'm guessing that there are more Python developers who are familiar with the node_modules pattern of Node than with the virtualenvwrapper pattern of hiding the environment directory. But it's a guess. If you aren't familiar with any of these tools, I think it would be confusing not to know where the installed files are ending up.

I understand this is the wrong audience, but since this discussion is going on... well, I don't think that node_modules were an inspiration for pipenv, and not for virtualenv either. My guess may be historically incorrect, but having to work with both rbenv and virtualenv, I can tell you that virtualenv feels like either a bad copy w/o understanding, or maybe an early prototype, which was improved on by rbenv.  In either case, virtualenv is a laughing stock compared to rbenv, and here's why:
It copies packages for each environment.    It's just a bad design decision, but more likely just a lack of decision: it just happened like that because someone wrote some code to put these packages into arbitrary directory.  On top of that, it doesn't work on Windows really.  To the point that it was never really tested on Windows...  One ridiculous thing about it is that it tests for OS, and once it discovers that it runs on Windows, it sets home directory to ~, this default may later be overridden by some environment variables, but if you are actually trying to run your automation in a supervised and clean environment... virtualenv will simply never install the packages in the same directory.
So... pipenv alleges to be a tool for human beings, kind of like requests... I guess? So, it ought to improve the immature efforts made by its predecessors... well, it seems like that would be the way to go, if you want to make a program that does the same thing as those before you, but better, right?  And yet, instead of throwing away the garbage of virtualenv, it uses it as is.  The wrapper is only different from the wrapped program in that it doesn't allow / makes it more difficult to use some of the functions from the wrapped program...
 But you don't live up to the promise.  In reality, you simply manipulate public opinion, without doing any real work.  And not programmers who have to do automation need to face another evil, just because someone looked to get more "likes" on GitHub...

@wvxvw Indeed you are incorrect. Virtualenv predates rbenv by something like five years, and therefore can never be inspired by it. Also they are fundamentally different things, only achieving a similar goal in the end. The thing you are looking for (runtime management tool inspired by rbenv) is pyenv.
Also regarding virtualenv being not on par with other tools—do you know it has been around for ten (10) years? Software developement requirements change a lot, and assumptions it made have been gradually going out of date, and nobody has cared to stepped up to replace it. Do you care enough to step up?
I understand everyone deserves a chance to speak, but to join a discussion without minimal understanding to the topic, and start pointing fingers right away, this is a little rude to contributors of Pipenv, virtualenv, and Python packaging systems as a whole. Please do not do this.

@wvxvw I’ve only seen you offer insults. This kind of attitude isn’t really welcome here. Please see our code of conduct before you continue posting.

I got the same problem after changing the project path and lose the original virtualenv mapping, then I read this thread. First, I appreciate the work of the pipenv team. Just got some opinions i'd like to share about this discussion:

The document indeed should point out the mapping mechanism between project path and env, at least warn users that changing project path would cause unmapping the original env.

Will it be better if you can manually set the path to the env in the Pipfile? I mean people may have some advance requirement to manually use the same env.

Just my opinions to share with you guys.

It is completely unclear how to use pipenv. Should I have many virtual environment for one project? Should I share the virtual environments between projects? How do I install a different python version for a specific project with pipenv, if the python version is only needed for that project?  When I read the praises of pipenv on the homepage, I believed that it will help me. Instead, I wasted 5 days of wrestling with it, and now I think I go back to pyenv because that was at least somewhat deterministic.

if you want to use multiple environment for one project, use tox. Use pipenv for your main development environment, and tox for testing on multiple python version.

@ashnur you clearly need something to do.  Instead of spreading negativity among an open source project run by volunteers, why don’t you try contributing something useful?

@uranusjr
this is where the hashing happens?
I am working on a project and need to calculate the hash of a path.

@devxpy Yup, exactly.

I think you guys should put a basic tutorial on how to set up a virtualenv with pipenv something very basic because the easier it is on people the more people will use it but if it causes confusion then more people may not use it and may seek other languages or methods to build there projects

@uranusjr what is the reason that Pipenv doesn't create the virtualenv by default in the project directory? The way I see it, it would solve the issue with orphaned environments when the project is renamed/moved/deleted. Besides, it would be less confusion to people who (somewhat rightfully) expect it to work like npm.
Is there any benefit to preferring this approach besides maybe tradition?

Simply create the .venv directory before the pipenv install command. A —venv or —dot-venv option to pipenv install would be welcome, actually :)

Starting with 2018.10.9 there is another way to do this. You can add a .venv file containing the path to your virtual environment. (Sneaky new feature!)
@andrewpeterprifer Because we used to do this, and needed to change it because some people rejected very strongly. We need to choose one approach or another, and I had to admit that it is a better default to not put virtual environments inside the project directory.
p.s. Would you (or anyone) be interested in writing a faq entry about this? It would likely take a few paragraphs, but I would be more than happy to explain if someone promises to take time to polish the text and submit a PR.

Starting with 2018.10.9 there is another way to do this. You can add a .venv file containing the path to your virtual environment. (Sneaky new feature!)
@andrewpeterprifer Because we used to do this, and needed to change it because some people rejected very strongly. We need to choose one approach or another, and I had to admit that it is a better default to not put virtual environments inside the project directory.
p.s. Would you (or anyone) be interested in writing a faq entry about this? It would likely take a few paragraphs, but I would be more than happy to explain if someone promises to take time to polish the text and submit a PR.

I am sorry to bump in ... I have this very same need to move projecs folders that have a virtual environments created with pipenv.
Currently I do the following and have no problem at all:

I move the project folder wherever I want
in C:\Users\user.virtualenvs I delete the folder of the venv associated to the project I just moved
I navigate the the new project folder location via cmd and run pipenv install (or pipenv sheel and then pipenv sync)

Everything works ok. Is this a bad practice?
Regarding uranusjr comment if I understand correctly with the new feature I should add the .venv file (containing the path to the desired virtual environment) into the project folder right? And this would avoid me of having to do all the steps I previously metioned? If thats the case it is great!!
If that is the case wouldn't it be better if such a file were automatically created in the project folder when the virtual enviroment is initially created?

Actually, I think @gioxc88 's idea is good, a newly created virtualenv can automatically generate .env file under project root, and contains env configs like PATH. It will make the environment more transparent to developers and a more convenient way to reconfigure.

I’ll try to answer your questions together. The approach isn’t bad (IMO; I use the same setup myself as well). It is, however, easier for an unaware user to trip on.
One way to think of it would be to consider putting a project in version control (say Git). If the environment is created in project root, it would naturally be in the repository root. People like you and I, who are used to this setup, obviously know we should add a rule in .gitignore (or the global ignore config) to prevent the .venv directory from being checked in, but an unsuspecting user would not, and could very easily checked in the environment by accident. This is not only bad for project management, but (more importantly) provides an vector to potential attacks by exposing local information. Therefore, it is a general rule for project management tools to avoid putting generated files inside project directory. It could be okay (still not optimal IMO) to do it if you’re designing an ecosystem from scratch (e.g. NPM’s node_modules), but definitely not a good idea for tools built for an ecosystem with established common practices, as the case of Pipenv.
If an environment is generated outside of project root by default, there is one less possible thing to worry about when you publish your project (e.g. push it to GitHub). It makes our (who prefer in-project environments) lives a bit more difficult, but from a risk perspective, the worst that can happen is to accidentally move the project and break the environment, or forgot to remove an environment when a project is removed. Either is much, much more easily recoverable than accidentally pushing your potentially sensitive environment information to GitHub.
The .venv file feature is still quite new (released only days ago), and we’re still exploring ways to best utilise it. It still has the same problem of a .venv directory, but hopefully not as bad. I really like the feature myself, and definitely hope we can use it to improve the user experience, but there are still a lot to consider here.

Hi. For me, the .venv directory (old feature) and .venv file (new feature) are ok, but I would be very grateful to have an option in the pipenv install command.
Something like:
pipenv install

Would install in ~/.local/
pipenv install --venv

Would install in $PWD/.venv directory
pipenv install --venv-dir /my/custom-path

Would install in /my/custom-path.

If you want a new feature, please propose it properly by making an enhancement proposal to ~/.peeps.  Please don't make enhancement proposals scattered randomly around various issues, it's not trackable.

@uranusjr thank you for the detailed answer! Just to satisfy my curiosity, what kind of local (potentially sensitive) information could be exposed by a checked in python venv? I agree that it is annoying if node_modules gets checked in, but normally that wouldn’t contain any local information.

Also, you’re right, node_modules probably does not contain sensitive information. That is another benefit when you build an ecosystem from scratch. Python virtual environments was unfortunately invented way before this is a common problem (back then you’re already a guru if you use VCS at all).

I arrived here while I was trying to understand how pipenv knows the right virtualenv : )
Thank you guys for that discussion. Probably, it could be a good idea specifying in the main page (e.g., here) that renaming the project path breaks the default mechanism of virtualenv binding.

All documentation pages are open for contribution.

I will!

@uranusjr This means that if I rename the directory my project's virtualenv will be lost. That's bad. It can be a common use case to rename a directory and users may fall into this and wonder how their environment stopped working.
I would suggest to fix it and make an entry into Pipfile if that's possible. Or create another .pipenv file to store such metadata in each project directory.
What do you suggest ?
Thanks for answering both the questions!

thanks for asking both the question. i also encounter the same problem ,

If you initialized pipenv in a wrong directory and have to utilize the virtualenv directory from the correct directory, you can get the virtualenv path by doing pipenv --venv and move the PIpfile and Pipfile.lock to the correct directory.
echo ${PATH_OBTAINED_FROM_PREVIOUS_COMMAND} > .venv in the correct directory and it should work properly.

I noticed today that if there is a pipfile in the parent directory, pipenv ignores the environmental variable export PIPENV_VENV_IN_PROJECT=1 and installs a venv in parent directory instead.  This is on release 2018.11.26.


Added support for custom antiAffinity configurations

Sample implementation for #526

[x] Chart version not bumped (the versions are all bumped and released at the same time)
[x] README.md updated with any new values or changes
[ ] Updated template tests in ${CHART}/tests/*.py
[ ] Updated integration tests in ${CHART}/examples/*/test/goss.yaml

Since this is a community submitted pull request, a Jenkins build has not been kicked off automatically. Can an Elastic organization member please verify the contents of this patch and then kick off a build manually?

jenkins test this please

Hi @cambierr, sorry for the delay. Can you merge master on your branch?

done !

jenkins test this please

When I'm trying to use a custom antiAffinity value I get the following error: coalesce.go:160: warning: skipped value for antiAffinity: Not a table. but it seems to work anyway:
➜  elasticsearch git:(features/addMoreFlexibilityToAntiAffinity) ✗ cat values.yaml
antiAffinity:
  preferredDuringSchedulingIgnoredDuringExecution:
  - weight: 100
    podAffinityTerm:
      labelSelector:
        matchExpressions:
        - key: security
          operator: In
          values:
          - S2
      topologyKey: failure-domain.beta.kubernetes.io/zone
➜  elasticsearch git:(features/addMoreFlexibilityToAntiAffinity) ✗ helm install elasticsearch . -f values.yaml
coalesce.go:160: warning: skipped value for antiAffinity: Not a table.
NAME: elasticsearch
LAST DEPLOYED: Thu Jul  9 10:53:51 2020
NAMESPACE: jmlrt-test
STATUS: deployed
REVISION: 1
NOTES:
1. Watch all cluster members come up.
  $ kubectl get pods --namespace=jmlrt-test -l app=elasticsearch-master -w
2. Test cluster health using Helm test.
  $ helm test elasticsearch --cleanup
➜  elasticsearch git:(features/addMoreFlexibilityToAntiAffinity) ✗ kg statefulsets.apps -o yaml
apiVersion: v1
items:
- apiVersion: apps/v1
  kind: StatefulSet
  metadata:
    annotations:
      esMajorVersion: "8"
      meta.helm.sh/release-name: elasticsearch
      meta.helm.sh/release-namespace: jmlrt-test
    creationTimestamp: "2020-07-09T08:53:55Z"
    generation: 1
    labels:
      app: elasticsearch-master
      app.kubernetes.io/managed-by: Helm
      chart: elasticsearch
      heritage: Helm
      release: elasticsearch
    name: elasticsearch-master
    namespace: jmlrt-test
    resourceVersion: "468258171"
    selfLink: /apis/apps/v1/namespaces/jmlrt-test/statefulsets/elasticsearch-master
    uid: b8b36bf8-c1c1-11ea-959e-42010a8000cd
  spec:
    podManagementPolicy: Parallel
    replicas: 3
    revisionHistoryLimit: 10
    selector:
      matchLabels:
        app: elasticsearch-master
    serviceName: elasticsearch-master-headless
    template:
      metadata:
        creationTimestamp: null
        labels:
          app: elasticsearch-master
          chart: elasticsearch
          heritage: Helm
          release: elasticsearch
        name: elasticsearch-master
      spec:
        affinity:
          podAntiAffinity:
            preferredDuringSchedulingIgnoredDuringExecution:
            - podAffinityTerm:
                labelSelector:
                  matchExpressions:
                  - key: security
                    operator: In
                    values:
                    - S2
                topologyKey: failure-domain.beta.kubernetes.io/zone
              weight: 100
        containers:
        - env:
          - name: node.name
            valueFrom:
              fieldRef:
                apiVersion: v1
                fieldPath: metadata.name
          - name: cluster.initial_master_nodes
            value: elasticsearch-master-0,elasticsearch-master-1,elasticsearch-master-2,
          - name: discovery.seed_hosts
            value: elasticsearch-master-headless
          - name: cluster.name
            value: elasticsearch
          - name: network.host
            value: <IP_ADDRESS>
          - name: ES_JAVA_OPTS
            value: -Xmx1g -Xms1g
          - name: node.data
            value: "true"
          - name: node.ingest
            value: "true"
          - name: node.master
            value: "true"
          image: docker.elastic.co/elasticsearch/elasticsearch:8.0.0-SNAPSHOT
          imagePullPolicy: IfNotPresent
          name: elasticsearch
          ports:
          - containerPort: 9200
            name: http
            protocol: TCP
          - containerPort: 9300
            name: transport
            protocol: TCP
          readinessProbe:
            exec:
              command:
              - sh
              - -c
              - |
                #!/usr/bin/env bash -e
                # If the node is starting up wait for the cluster to be ready (request params: "wait_for_status=green&timeout=1s" )
                # Once it has started only check that the node itself is responding
                START_FILE=/tmp/.es_start_file

                http () {
                  local path="${1}"
                  local args="${2}"
                  set -- -XGET -s

                  if [ "$args" != "" ]; then
                    set -- "$@" $args
                  fi

                  if [ -n "${ELASTIC_USERNAME}" ] && [ -n "${ELASTIC_PASSWORD}" ]; then
                    set -- "$@" -u "${ELASTIC_USERNAME}:${ELASTIC_PASSWORD}"
                  fi

                  curl --output /dev/null -k "$@" "http://<IP_ADDRESS>:9200${path}"
                }

                if [ -f "${START_FILE}" ]; then
                  echo 'Elasticsearch is already running, lets check the node is healthy'
                  HTTP_CODE=$(http "/" "-w %{http_code}")
                  RC=$?
                  if [[ ${RC} -ne 0 ]]; then
                    echo "curl --output /dev/null -k -XGET -s -w '%{http_code}' \${BASIC_AUTH} http://<IP_ADDRESS>:9200/ failed with RC ${RC}"
                    exit ${RC}
                  fi
                  # ready if HTTP code 200, 503 is tolerable if ES version is 6.x
                  if [[ ${HTTP_CODE} == "200" ]]; then
                    exit 0
                  elif [[ ${HTTP_CODE} == "503" && "8" == "6" ]]; then
                    exit 0
                  else
                    echo "curl --output /dev/null -k -XGET -s -w '%{http_code}' \${BASIC_AUTH} http://<IP_ADDRESS>:9200/ failed with HTTP code ${HTTP_CODE}"
                    exit 1
                  fi

                else
                  echo 'Waiting for elasticsearch cluster to become ready (request params: "wait_for_status=green&timeout=1s" )'
                  if http "/_cluster/health?wait_for_status=green&timeout=1s" "--fail" ; then
                    touch ${START_FILE}
                    exit 0
                  else
                    echo 'Cluster is not yet ready (request params: "wait_for_status=green&timeout=1s" )'
                    exit 1
                  fi
                fi
            failureThreshold: 3
            initialDelaySeconds: 10
            periodSeconds: 10
            successThreshold: 3
            timeoutSeconds: 5
          resources:
            limits:
              cpu: "1"
              memory: 2Gi
            requests:
              cpu: "1"
              memory: 2Gi
          securityContext:
            capabilities:
              drop:
              - ALL
            runAsNonRoot: true
            runAsUser: 1000
          terminationMessagePath: /dev/termination-log
          terminationMessagePolicy: File
          volumeMounts:
          - mountPath: /usr/share/elasticsearch/data
            name: elasticsearch-master
        dnsPolicy: ClusterFirst
        initContainers:
        - command:
          - sysctl
          - -w
          - vm.max_map_count=262144
          image: docker.elastic.co/elasticsearch/elasticsearch:8.0.0-SNAPSHOT
          imagePullPolicy: IfNotPresent
          name: configure-sysctl
          resources: {}
          securityContext:
            privileged: true
            runAsUser: 0
          terminationMessagePath: /dev/termination-log
          terminationMessagePolicy: File
        restartPolicy: Always
        schedulerName: default-scheduler
        securityContext:
          fsGroup: 1000
          runAsUser: 1000
        terminationGracePeriodSeconds: 120
    updateStrategy:
      type: RollingUpdate
    volumeClaimTemplates:
    - metadata:
        creationTimestamp: null
        name: elasticsearch-master
      spec:
        accessModes:
        - ReadWriteOnce
        resources:
          requests:
            storage: 30Gi
        volumeMode: Filesystem
      status:
        phase: Pending
  status:
    collisionCount: 0
    currentReplicas: 3
    currentRevision: elasticsearch-master-5bd45d69cb
    observedGeneration: 1
    replicas: 3
    updateRevision: elasticsearch-master-5bd45d69cb
    updatedReplicas: 3
kind: List
metadata:
  resourceVersion: ""
  selfLink: ""

Could you also update the value description and provide a commented example in https://github.com/elastic/helm-charts/blob/b375f8f28ff9c3a29c95caff7dfc68dd5c94484b/elasticsearch/values.yaml#L154-L156

When I'm trying to use a custom antiAffinity value I get the following error: coalesce.go:160: warning: skipped value for antiAffinity: Not a table.

I tried adding a test which would be really great:
def test_adding_a_custom_anti_affinity():
    config = """
antiAffinity: null
antiAffinity:
  preferredDuringSchedulingIgnoredDuringExecution:
  - weight: 100
    podAffinityTerm:
      labelSelector:
        matchExpressions:
        - key: mylabel
          operator: In
          values:
          - myvalue
"""
    r = helm_template(config)
    assert r["statefulset"][uname]["spec"]["template"]["spec"]["affinity"][
        "antiAffinity"
    ] == {
        "preferredDuringSchedulingIgnoredDuringExecution": [
            {
                "weight": 100,
                "podAffinityTerm": {
                    "labelSelector": {
                        "matchExpressions": [
                            {"key": "mylabel", "operator": "In", "values": ["myvalue"]}
                        ]
                    }
                },
            }
        ]
    }

This is failing with a more explicit error:
tests/elasticsearch_test.py::test_adding_a_custom_anti_affinity 2020/07/09 09:17:23 Warning: Merging destination map for chart 'elasticsearch'. The destination item 'antiAffinity' is a table and ignoring the source 'antiAffinity' as it has a non-table value of: hard
FAILED

It seems that Helm don't like having mixed types (string as default values and table as overrided values).
It seems that we should better create a new customAntiAffinity value in addition of the existing antiAffinity value to avoid mixing type.

antiAffinity could accept hard, soft and custom
when antiAffinity would be set to custom, the template would use the content of customAntiAffinity value instead.

WDYT?

Anything we can do to unblock that ? this improvement will be really good to have 👍


Inline query only seems to operate on first result

Whilst working on a query here: http://stackoverflow.com/a/31737571/3800244, I tried the following WHERE clause on the query.
WHERE (SELECT expand(in('Child')) from #11:3) CONTAINSALL (@rid in $current.in_Child)

This inline query only seemed to check the first result in the CONTAINSALL expression, and I was getting incorrect results. By adding a LET clause and changing the WHERE clause to the one following, all records from inline query were properly compared in the CONTAINSALL expression, and I got the expected results.
LET $parents = (SELECT expand(in('Child')) from #11:3)
WHERE $parents CONTAINSALL (@rid in $current.in_Child)

This is fixed in v 3.0 with the new SQL executor
Closing, thanks
Luigi


TypeError with HTTP Client

Laravel Version
10.42.0
PHP Version
8.3
Database Driver & Version
No response
Description
Looks like a similar issue existed before - https://github.com/laravel/framework/pull/37596.
Relevant stack trace:
TypeError: Illuminate\Http\Client\Events\ConnectionFailed::__construct(): Argument #1 ($request) must be of type Illuminate\Http\Client\Request, null given, called in /code/vendor/laravel/framework/src/Illuminate/Http/Client/PendingRequest.php on line 1424
#67 /vendor/laravel/framework/src/Illuminate/Http/Client/Events/ConnectionFailed.php(22): Illuminate\Http\Client\Events\ConnectionFailed::__construct
#66 /vendor/laravel/framework/src/Illuminate/Http/Client/PendingRequest.php(1424): Illuminate\Http\Client\PendingRequest::dispatchConnectionFailedEvent
#65 /vendor/laravel/framework/src/Illuminate/Http/Client/PendingRequest.php(924): Illuminate\Http\Client\PendingRequest::Illuminate\Http\Client\{closure}
#64 /vendor/laravel/framework/src/Illuminate/Support/helpers.php(248): retry
#63 /vendor/laravel/framework/src/Illuminate/Http/Client/PendingRequest.php(892): Illuminate\Http\Client\PendingRequest::send
#62 /vendor/laravel/framework/src/Illuminate/Http/Client/PendingRequest.php(770): Illuminate\Http\Client\PendingRequest::get

Steps To Reproduce
It happens sometimes, when calling
public function get(string $endpoint, array $query = [], int $tries = 3, int $timeout = 60): Response {
    $headers = [
        'X-Shopify-Access-Token' => 'my-token',
        'Content-Type'           => 'application/json',
    ];
    $response = Http::setClient(Http::buildClient())->withHeaders($headers)->timeout(60)->get($this->url($endpoint, $query));
}

Can you provide a full reproducible example with endpoint and query?

$endpoint = 'https://waterdrop-nl.myshopify.com/admin/api/2023-10/products/42859018911930/variants.json';
$query = []; //no query

This is the last logged url, but it happens sometimes, so I can't guarantee that this URL will reproduce it. Since ConnectionFailed is involved, I guess the server didn't respond at that moment.

How are you executing this? Within a CLI command? Or through a web request? Could you provide a complete step by step guide at what you're doing?

The service is deployed and running in the Google Cloud Platform.
A scheduled task, that is running every 5 minutes is creating jobs in the Google Cloud Tasks. We're using the stackkit/laravel-google-cloud-tasks-queue to create the jobs in Cloud Tasks. Then GCP is calling the handle-task route to execute the task.
We're logging any errors via Sentry, there are 4 of this type today.

Perfect, thank you! :sunglasses:


Remove Validation feature flag for internal use

This PR removes the feature flag for the validation service. Requirements to access this UI still lie behind Admin user authorization. This is not a public page!
Test Steps:

Remove the validation feature flag from your browser via the UI
Refresh the app and ensure the validation service is listed under Upload & Validate in the navigation bar

Changes

Flag removed from nav UI
Flag removed from AuthElement requirements
Flag removed from enumeration

Checklist
Testing

[X] Tested locally?
[ ] Ran ./prime test or ./gradlew testSmoke against local Docker ReportStream container?
[X] (For Changes to /frontend-react/...) Ran npm run lint:write?
[ ] Added tests?

Process

[ ] Are there licensing issues with any new dependencies introduced?
[ ] Includes a summary of what a code reviewer should test/verify?
[ ] Updated the release notes?
[ ] Database changes are submitted as a separate PR?
[ ] DevOps team has been notified if PR requires ops support?

Linked Issues

Fixes #issue

To Be Done
Create GitHub issues to track the work remaining, if any

#issue

Specific Security-related subjects a reviewer should pay specific attention to

Does this PR introduce new endpoints?

new endpoint A
new endpoint B

Does this PR include changes in authentication and/or authorization of existing endpoints?
Does this change introduce new dependencies that need vetting?
Does this change require changes to our infrastructure?
Does logging contain sensitive data?
Does this PR include or remove any sensitive information itself?

If you answered 'yes' to any of the questions above, conduct a detailed Review that addresses at least:

What are the potential security threats and mitigations? Please list the STRIDE threats and how they are mitigated

Spoofing (faking authenticity)

Threat T, which could be achieved by A, is mitigated by M

Tampering (influence or sabotage the integrity of information, data, or system)
Repudiation (the ability to dispute the origin or originator of an action)
Information disclosure (data made available to entities who should not have it)
Denial of service (make a resource unavailable)
Elevation of Privilege (reduce restrictions that apply or gain privileges one should not have)

Have you ensured logging does not contain sensitive data?
Have you received any additional approvals needed for this change?

Set to deploy 10/25


Ensured that only instance properties (and no static properties) are used in SimpleEffectDialog

CloudsData has a static property BlendOps, which SimpleEffectDialog tried to use and caused an error to occur because it doesn't have a getter, but again, this property is static and isn't supposed to be used. I added some more checks in the filtering part in order to make sure that only instance properties are used.
Still, I don't think this property belongs in CloudsData, so I moved it to CloudsEffect. If this is not desired, the last commit could be discarded.

I think it's fine to move it into CloudsEffect

Oh wait, I think moving the property out of CloudsData introduced an error, since the reflection for StaticList ("BlendOps") is looking for a field or property with that name, which no longer exists. Opening the clouds effect is throwing an exception from that now

I can just revert the changes from that last commit


solving problem with EMA indicator code

I'm submitting a ...
[*] bug report
[ ] question about the decisions made in the repository
Hi evearybody.
I want to use the EMA and the DEMA indicators. They run, but I cant made them make any trade on backtesting.
I tried running gekko on backtesting mode from bash, but the console log says 'undefined' on both indicators. Anyway, the console log for the candle is ok. So i think that the problem is something about the strategy code...
When i use the 'EMA' indicator on a 'TestingStrategy.js' using the tulip library, the result is undefined.
Here is the code i'm using:

var strat = {};
strat.init = function() {
this.addTulipIndicator('ema11','ema',{optInTimePeriod: 10});
this.addTulipIndicator('dema11','dema',{optInTimePeriod: 10});
}
strat.check = function(candle) {
console.log(this.TulipIndicator);
console.log(candle);
}
module.exports = strat;

and when i run node gekko --backtest --config config.js

/      \ /        |/  |  /  |/  |  /  | /
/$$$$$$  |$$$$$$$$/ $$ | /$$/ $$ | /$$/ /$$$$$$  |
$$ | $$/ $$ |_    $$ |/$$/  $$ |/$$/  $$ |  $$ |
$$ |/    |$$    |   $$  $$<   $$  $$<   $$ |  $$ |
$$ |$$$$ |$$$$$/    $$$$$  \  $$$$$  \  $$ |  $$ |
$$ _$$ |$$ |_____ $$ |$$  \ $$ |$$  \ $$ _$$ |
$$    $$/ $$       |$$ | $$  |$$ | $$  |$$    $$/
$$$$$$/  $$$$$$$$/ $$/   $$/ $$/   $$/  $$$$$$/
    Gekko v0.6.8
    I'm gonna make you rich, Bud Fox.

2019-04-30 14:22:14 (INFO):     Setting up Gekko in backtest mode
2019-04-30 14:22:14 (INFO):
2019-04-30 14:22:14 (WARN):     The plugin Candle writer does not support the mo
de backtest.

Can you please help me...? I really want to use these indicators in my strategies.
Sorry about my english...
Thanks!  :D

Hey,
This is the issue tracker for tracking bugs and new features. Your issue is not a bug report. Please ask around on the forum, stack overflow, discord or telegram next time. See here: https://gekko.wizb.it/docs/introduction/getting_help.html
As for your issue:

console.log(this.TulipIndicator);

There is no such thing as this.TulipIndicator, please check the docs for the correct way of accessing calculated indicator results.


IVGMM with user-supplied weighting matrix seems to only affect standard errors

Hello!
In my understanding, the initial_weight parameter in linearmodels.iv.model.IVGMM.fit should be the first stage weighting matrix used to get an initial parameter estimate β1 . After that, we use this β1  to generate an estimate for the covariance matrix of the moment conditions Ω , and use the inverse of this to finally estimate the β. Therefore, if we change the initial_weight parameter, it will naturally change the first stage estimate, and in turn the Ω , and finally the final estimate. It seems the winitial option in Stata gmm command works in this way.
But I just conducted a simple experiment, in which I set iter_limit=1 to directly see the estimate of the first stage:
import numpy as np
from statsmodels.api import add_constant
from linearmodels.datasets import mroz
print(mroz.DESCR)
data = mroz.load()
data = data.dropna()
data = add_constant(data, has_constant='add')

IVGMM(np.log(data.wage), data[['const']], data.educ, data.fatheduc).fit(iter_limit=1, initial_weight = np.array([[1,2], [2,2]]))

which gives me

But when I change the initial_weight:
IVGMM(np.log(data.wage), data[['const']], data.educ, data.fatheduc).fit(iter_limit=1, initial_weight = np.array([[1,2], [0.2,0.1]]))

which gives me

The two parameter estimates are the same. The initial_weight parameter does not worked quite as I expected. Can you explain a bit why this happen, and how should I do if I want to use user-supplied weighting matrix in the first stage?
Thank you!

If your model is just identified then weights don't matter since the moment conditions are exactly 0.

Definitely a bug.  Should be fixed in #315

Sorry, my example was inappropriate. But as you just mentioned, the estimates with user-supplied weighting matrices seem to be incorrect. I found this when I was trying to play with the weighting matrix using the data from Acemoglu, Johnson, and Robinson (2001) paper with an over-identified variant of their model. The results using linearmodels is different with those using Stata and my manual calculation.
Finally, thank you a lot for your package!


Not utilizing the GPU at all, but hammering away on CPU regardless of settings

My RTX 4070 TI is being utilized by 0% while my 12700K is working very hard whenever I generate anything from the program.
This is regardless of I set it to use the GPU or the CPU, and I even forced the utilization of  the GPU through windows graphics settings, by adding my browser to the list, just to make sure it wasn't a Windows issue.

I encoutered same issue, its due the pytorch version.
But first make sure u installed nvidia cuda toolkit , can be check by using
nvcc --version
if prompt command not found, u need to install from here : https://developer.nvidia.com/cuda-downloads
after installing, try to run the testing code below :
import torch
torch.zeros(1).cuda()

if it show something like : tensor([0.], device='cuda:0')
means your gpu cuda should be working now.
if prompt error, depending on the error u might need to find your own solution.
Mine is due to the pytorch installed do not compiled with cuda.
So, i uninstall the pytorch first with
pip uninstall torch torchvision
then depending on your cuda version, check using
nvidia-smi
download the respective pytorch from here: https://pytorch.org/
after installing, try to the cuda testing code again. If it dint show error, u should be able to use GPU now.

I'm getting this too. Console says device:cuda, but nvtop shows it's not being used, but CPU %100, then it usually crashes.
Loading VAE weights specified in settings: /mnt/AI/stable-diffusion-webui/models/VAE/sdxl-fp16.vae.safetensors
Applying attention optimization: Doggettx... done.
Model loaded in 3.7s (load weights from disk: 0.9s, create model: 0.4s, apply weights to model: 2.1s).
DepthMap v0.4.7 (ee54b550)
device: cuda
Loading model(s) ..
Loading model weights from  ./models/leres/res101.pth
initialize network with normal
loading the model from ./models/pix2pix/latest_net_G.pth
Computing output(s) ..
  0%|                                                              | 0/1 [00:00<?, ?it/s]wholeImage being processed in : 1568
Adjust factor is: 1.024247491638796
Selecting patches ...
Target resolution:  (3212, 2198, 3)
Resulting depthmap resolution will be : (4864, 3328)
patches to process: 19
	 processing patch 0 / 18 | [  73   73 3247 3247]
	 processing patch 1 / 18 | [  73  581 3247 3247]
	 processing patch 2 / 18 | [ 145 1163 3101 3101]
	 processing patch 3 / 18 | [ 485 2011 2423 2423]
	 processing patch 4 / 18 | [   0    0 2374 2374]
	 processing patch 5 / 18 | [   0  509 2374 2374]
	 processing patch 6 / 18 | [   0 1018 2374 2374]
	 processing patch 7 / 18 | [   0 1526 2374 2374]
	 processing patch 8 / 18 | [ 509    0 2374 2374]
	 processing patch 9 / 18 | [1090   73 2229 2229]
	 processing patch 10 / 18 | [1090  581 2229 2229]
	 processing patch 11 / 18 | [1090 1090 2229 2229]
	 processing patch 12 / 18 | [1090 1599 2229 2229]
	 processing patch 13 / 18 | [ 170 2205 2035 2035]
	 processing patch 14 / 18 | [   0  509 1357 1357]
	 processing patch 15 / 18 | [   0 2544 1357 1357]
	 processing patch 16 / 18 | [ 509    0 1357 1357]
	 processing patch 17 / 18 | [1018    0 1357 1357]
	 processing patch 18 / 18 | [1526    0 1357 1357]
100%|██████████████████████████████████████████████████████| 1/1 [00:16<00:00, 16.69s/it]
Computing output(s) done.
Running 3D Photo Inpainting ..
Loading edge model ..
Loading depth model ..
Loading rgb model ..
  0%|                                                                                | 0/1 [00:00<?, ?it/s]
Generating inpainted mesh .. (go make some coffee) ..
                                                                                ./webui.sh: line 297:  7383 Killed                  "${python_cmd}" -u "${LAUNCH_SCRIPT}" "$@"                                         | 0/7 [00:00<?, ?it/s]

PyTorch 2.3.0. Torch is working fine on my 3090 for generating images inside A1111.
Version: 2.3.0
Summary: Tensors and Dynamic neural networks in Python with strong GPU acceleration
Home-page: https://pytorch.org/
Author: PyTorch Team
Author-email<EMAIL_ADDRESS>License: BSD-3


add support for psqlextra extensions in reset_db

This attempts to suport the django-postgres-extra library wich is also a valid postgresq engine

Coverage decreased (-1.2%) to 67.941% when pulling 7ad7135f1ae6fae159cc123f67cfabcec2cefe6b on kaozdl:django-postgres-extra into 0a15ff94f704beef1e71b55a14c4a614a15434c7 on django-extensions:master.

Coverage decreased (-1.2%) to 67.941% when pulling 7ad7135f1ae6fae159cc123f67cfabcec2cefe6b on kaozdl:django-postgres-extra into 0a15ff94f704beef1e71b55a14c4a614a15434c7 on django-extensions:master.

Coverage decreased (-1.2%) to 67.941% when pulling 7ad7135f1ae6fae159cc123f67cfabcec2cefe6b on kaozdl:django-postgres-extra into 0a15ff94f704beef1e71b55a14c4a614a15434c7 on django-extensions:master.

Coverage decreased (-1.2%) to 67.941% when pulling 7ad7135f1ae6fae159cc123f67cfabcec2cefe6b on kaozdl:django-postgres-extra into 0a15ff94f704beef1e71b55a14c4a614a15434c7 on django-extensions:master.

Coverage decreased (-1.2%) to 67.941% when pulling 7ad7135f1ae6fae159cc123f67cfabcec2cefe6b on kaozdl:django-postgres-extra into 0a15ff94f704beef1e71b55a14c4a614a15434c7 on django-extensions:master.

Coverage decreased (-1.2%) to 67.941% when pulling 7ad7135f1ae6fae159cc123f67cfabcec2cefe6b on kaozdl:django-postgres-extra into 0a15ff94f704beef1e71b55a14c4a614a15434c7 on django-extensions:master.

Coverage decreased (-1.2%) to 67.941% when pulling 7ad7135f1ae6fae159cc123f67cfabcec2cefe6b on kaozdl:django-postgres-extra into 0a15ff94f704beef1e71b55a14c4a614a15434c7 on django-extensions:master.

Coverage decreased (-1.2%) to 67.941% when pulling 7ad7135f1ae6fae159cc123f67cfabcec2cefe6b on kaozdl:django-postgres-extra into 0a15ff94f704beef1e71b55a14c4a614a15434c7 on django-extensions:master.

Coverage decreased (-1.2%) to 67.941% when pulling 7ad7135f1ae6fae159cc123f67cfabcec2cefe6b on kaozdl:django-postgres-extra into 0a15ff94f704beef1e71b55a14c4a614a15434c7 on django-extensions:master.


How to run

We love your work, plz have a README on how to use the repo
Tons of thanks

There is a README.md, does it not work?


Handle high-volume terraform outputs better than Atlantis

Full commit logs is nice, but having consolidated view be good - to see relevant information

tagging @jdziat

The other idea suggested by @jdziat for "dry run / readonly mode" tracked in #237

To start with, you could just use the same output like Atlantis.
This makes it also easier for users to switch from Atlantis to digger.
E.g.


Allow terminating void elements with semicolons (;)

When Rust and HTML syntax differ, Maud tends to side with Rust syntax. This can be seen with string literals, for example, where we use backslash escapes instead of HTML entities. Using ; to terminate void
elements is consistent with this idea.
Moreover, this reduces confusion around the generated code. Maud does not insert an extra slash into the HTML output (as per the spec) but the syntax may imply otherwise.
This confusion may have been the cause of a bug I found in the wild, where the code omitted the trailing slash on an input element. I suspect that this is because the author thought that a trailing slash in the Maud template would lead to one in the HTML output. Switching to semicolons would prevent this misconception.

Merged in 1785071f1b17daff032c8a21095b23b3db6f73f8


Improved performance of decoders

Improved performance of decoders: GPT-like, bloom, etc., and Seq2seq models.
Observed a significant speedup of long sequences, e.g. Dolly-3B, 500 tokens: +30% when running on a client CPU.

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint.

I think it is ready for merge.


fix decal in aria

Brief Information
This pull request is in the type of:

[x] bug fixing
[ ] new feature
[ ] others

What does this PR do?
fix issue - https://github.com/apache/echarts/issues/18118#issue-1512698774
"series-sunburst.data.itemStyle.decal" is able to override "aria.decal. decals"
Fixed issues

Details
Before: What was the problem?

After: How does it behave after the fixing?

Document Info
One of the following should be checked.

[x] This PR doesn't relate to document changes
[ ] The document should be updated later
[ ] The document changes have been made in apache/echarts-doc#xxx

Misc
ZRender Changes

[ ] This PR depends on ZRender changes (ecomfe/zrender#xxx).

Related test cases or examples to use the new APIs
N.A.
Others
Merging options

[ ] Please squash the commits into a single one when merging.

Other information

added a test case for the issue

i did some changes and after that result is looking like this

@Ovilia did some changes and added another case

After fixing result was looking like this

mike, nancy and grandpa decal are working
do you mean their children should also have their decal ?

@Aman1919 Yes, in the above image, if two items have the same color, they should have the same decal.

@Aman1919 Yes, in the above image, if two items have the same color, they should have the same decal.

I think color is being added by value of children items . is this not correct Color shouldn't be added like  this ?

@Aman1919 By default, the color should act like this. Color relating to value is only used when visualMap is used.

I did changes after that result is looking like this

but it giving default backgroundcolor blue . I checked in pie and treemap they were also giving default blue  .  is this will be correct ?

No. This will break the original design of sunburst.

i did changes and result is looking like this . is this will be correct ?

so, lower levels node should be of lighter color than the upper level ? Could you suggest me something ?

@Aman1919 Please check this demo. The colors are correct.

@Ovilia


Rectify bug in ChangeCommand

Data file should be created at location when ChangeCommand is executed, not only after closing or adding new tasks

Bug has been rectified


Cleanup gnu test script

This fixes the last review comments from #1699

# TOTAL: 624
# PASS:  546
# SKIP:  62
# XFAIL: 0
# FAIL:  16
# XPASS: 0
# ERROR: 0

Are you sure you are really testing rust/coreutils?

# TOTAL: 624
# PASS:  546
# SKIP:  62
# XFAIL: 0
# FAIL:  16
# XPASS: 0
# ERROR: 0

Are you sure you are really testing rust/coreutils?

That sounds too good to be true

That sounds too good to be true

I can't see how anything would be going wrong, posibly the make to generate getlimits is messing things up? I did test that adding that make command wouldn't affect the binaries in the uutils build dir, but then again locally running lib/configmake.h src/getlimits was enough to get it the executable while in github there was another file that needed to be generated. So there might be remnants in my local test environment that is changing the results.
I'll run some experiments to confirm that the uutils binaries are what's being testsed.

I can't see how anything would be going wrong, posibly the make to generate getlimits is messing things up? I did test that adding that make command wouldn't affect the binaries in the uutils build dir, but then again locally running lib/configmake.h src/getlimits was enough to get it the executable while in github there was another file that needed to be generated. So there might be remnants in my local test environment that is changing the results.
I'll run some experiments to confirm that the uutils binaries are what's being testsed.

That sounds too good to be true

Yeah, something is not right. Most of the factor tests should fail, since they test numbers >  264 - 1, which uutils factor does not currently support (#1559). Only two are currently failing.

That sounds too good to be true

Yeah, something is not right. Most of the factor tests should fail, since they test numbers >  264 - 1, which uutils factor does not currently support (#1559). Only two are currently failing.

I have discovered my mistake. I was building uutils with cargo but that doesn't build all the individual binaries, so this is effectively testing the binaries that are installed on the system. After fixing this the tests just hang, a bit of digging indicates a fmt call was stuck in a read syscall which I assume is why the ulimit -t doesn't keep things moving.
I couldn't see an easy way to wrap individual tests with timeout, so I'll see if I can come up with a list of non-hanging tests.

I have discovered my mistake. I was building uutils with cargo but that doesn't build all the individual binaries, so this is effectively testing the binaries that are installed on the system. After fixing this the tests just hang, a bit of digging indicates a fmt call was stuck in a read syscall which I assume is why the ulimit -t doesn't keep things moving.
I couldn't see an easy way to wrap individual tests with timeout, so I'll see if I can come up with a list of non-hanging tests.

@jaggededgedjustice ok, thanks for digging into that :)
Don't hesitate to report a bug about the fmt issue, we could just fix the problem

@jaggededgedjustice ok, thanks for digging into that :)
Don't hesitate to report a bug about the fmt issue, we could just fix the problem

@jaggededgedjustice are you going to work on a fix to really use rust/coreutils?
Thanks

@jaggededgedjustice are you going to work on a fix to really use rust/coreutils?
Thanks

Still working on it, I hope I've found the last problem and it just needs testing. If things work out I should have a PR over the weekend.

Still working on it, I hope I've found the last problem and it just needs testing. If things work out I should have a PR over the weekend.


Does echarts support internationalization?

This issue is not created by echarts-issue-helper and will be soon closed.

ECharts 5.0 provides the i18n API https://echarts.apache.org/next/en/api.html#echarts.registerLocale

ECharts 5.0 provides the i18n API https://echarts.apache.org/next/en/api.html#echarts.registerLocale

thanks, i will learn it

thanks, i will learn it


corrected storm-hive README.md typos

+1.
Since it's about documentation, and it just fixes typos I'll merge it right now.

@randerzander Thanks for the patch. :)


Add support for Django 4.0

It would be great if django-waffle is Django 4.0 compatible.
Sadly, new version of Django dropped a lot of deprecated functions, so update required some actions in django-waffle's code.
Here are two problems:

NullBooleanField usage in migration (check out #441)
ImportError: cannot import name 'url' from 'django.conf.urls'

This one because django.conf.urls.url was removed in Django 4.0 and it's imported in waffle/urls.py.

Also

[ ] Remove default_app_config

If you need help holler!

@rh0dium a pull request is welcome!

I see that the main branch works fine with django4. Any plans on the PyPI release?

@Melevir feel free to open a pull request that adds test support.

That was my plan, but it turns out, that the only problem, that blocked me from running waffle on django4 was URLs thing, which is resolved in https://github.com/django-waffle/django-waffle/commit/c781c32de8d7e823e54486862ce5f70d2f49da33
What else blocks django-waffle from django4-compatible release? I'll be glad to help.

[ ] Add explicit test support for 4.0 at https://github.com/django-waffle/django-waffle/blob/master/tox.ini#L19
[ ] Update classifiers in https://github.com/django-waffle/django-waffle/blob/master/setup.py#L27

Fixed by #421


crash if libselinux-python is not installed.

Initial setup fails if libselinux-python is not installed:
TASK [ceph.ceph-common : apply operating system tuning] ************************
[DEPRECATION WARNING]: Using bare variables is deprecated. Update your playbooks so that the environment value uses the full variable syntax ('{{os_tuning_params}}').
This feature
will be removed in a future release. Deprecation warnings can be disabled by setting deprecation_warnings=False in ansible.cfg.
failed: [top] (item={u'name': u'kernel.pid_max', u'value': 4194303}) => {"failed": true, "item": {"name": "kernel.pid_max", "value": 4194303}, "msg": "Aborting, target uses selinux but python bindings (libselinux-python) aren't installed!"}
failed: [top] (item={u'name': u'fs.file-max', u'value': 26234859}) => {"failed": true, "item": {"name": "fs.file-max", "value": 26234859}, "msg": "Aborting, target uses selinux but python bindings (libselinux-python) aren't installed!"}
failed: [top] (item={u'name': u'vm.zone_reclaim_mode', u'value': 0}) => {"failed": true, "item": {"name": "vm.zone_reclaim_mode", "value": 0}, "msg": "Aborting, target uses selinux but python bindings (libselinux-python) aren't installed!"}
failed: [top] (item={u'name': u'vm.vfs_cache_pressure', u'value': 50}) => {"failed": true, "item": {"name": "vm.vfs_cache_pressure", "value": 50}, "msg": "Aborting, target uses selinux but python bindings (libselinux-python) aren't installed!"}
failed: [top] (item={u'name': u'vm.swappiness', u'value': 10}) => {"failed": true, "item": {"name": "vm.swappiness", "value": 10}, "msg": "Aborting, target uses selinux but python bindings (libselinux-python) aren't installed!"}
failed: [top] (item={u'name': u'vm.min_free_kbytes', u'value': 67584}) => {"failed": true, "item": {"name": "vm.min_free_kbytes", "value": 67584}, "msg": "Aborting, target uses selinux but python bindings (libselinux-python) aren't installed!"}
	to retry, use: --limit @site.yml.retry

PLAY RECAP *********************************************************************
top                        : ok=8    changed=0    unreachable=0    failed=1

I think this is normal, which is needed by ansible.

Thanks for reporting this @mmgaggle I'll update the dependancies.

This is actually a dependancy for CentOS installations. Are you trying on RHEL?

Closing this, feel free to re-open if the issue is not solved.


Add option to force docker pull

Fixes ##837.
TODO:

[x] Release a 0.22.0 version of mesos-utils.
[x] Update the mesos-utils dependency version in the Marathon build definition.
[x] Update documentation to describe the new parameter.

Blocked by #1340

Needs a rebase.

Rebased.

@drexin Ready for review.

this is related to #681 as well.

@ConnorDoyle Could you please rebase again and squash it into a single commit?

Ran into this today and glad to find this is already in progress. Thanks for efforts to everyone involved.

@drexin: rebased

:100:

@hekaldama yes, it will be in the next version (0.8.2) for which we will tag the first release candidate very soon now.


Test useRef branch on react-cytoscape-js

This PR should be tested before merging in react-cytoscapejs: https://github.com/plotly/react-cytoscapejs/pull/53
Also add the following:

https://github.com/plotly/react-cytoscapejs/pull/72
https://github.com/plotly/react-cytoscapejs/pull/70
https://github.com/plotly/react-cytoscapejs/pull/67
https://github.com/plotly/react-cytoscapejs/pull/59
https://github.com/plotly/react-cytoscapejs/pull/54
https://github.com/plotly/react-cytoscapejs/pull/50
https://github.com/plotly/react-cytoscapejs/pull/40

Tested and merged, closing.


have you tried SCNN in testing video?

i have a try,0.5s per frame. is it normal?

gpu

I haven't time the model. But the sequential operation in SCNN may take time.

@HITjialanyu  大佬，我想问下把demo_test.py 的哪里修改一下就可以检测视频，或者调用摄像头进行检测啊？

@HITjialanyu 大佬，我想问下把demo_test.py 的哪里修改一下就可以检测视频，或者调用摄像头进行检测啊？

你好，请问你解决了吗


I Want to Change CNAME of Caller

HI
I want to Change The Caller CNAME With My PhoneBook In Mine Project Database Because i want to Sho my Customize name on SoftPhones And DeskPhone
Please Help Me , With My knowledge it possible with ARI , I`m Right Or Not?

Not 100%, but no, I don't think you can use ARI to edit endpoints in your Asterisk config. The better thing to do would be to use one of the database integrations and write your own service that allows you to edit the config in the DB. ARI is more for scripting of dialplans in realtime. Not really for config editing.

Hi Seiggy, I solve this problem with ARI
sender.Channels.SetChannelVar(e.Channel.Id, "CALLERID(name)", Your String Name);
thank`s Bro


BioJS demo page doesn't work

From A. Mark Roberts:
The demos for this package on the BioJS registry aren't rendering correctly, I think.

http://biojs.io/d/biojs-pcviz

I'm seeing all blank DIVs. Maybe it's been that way for a while or maybe this package isn't maintained anymore.

To replicate this, visit either http://biojs.io/d/biojs-pcviz or http://workmen.biojs.net/demo/biojs-pcviz/simple
and this is what you get on the JavaScript Console:

Just had a chance to take another look at this and realized that this is due to our policy with pathwaycommons server. See the response and the X-Frame-Options coming from our server:

We probably need to let our sys-admins know and remove this restriction (cc: @onursumer @emekdemir )

the code changes addressed by changes 0cb90da have not resolved this issue. This requires a sysadmin work on the server side.

closed by: https://github.com/PathwayCommons/biojs-pcviz/commit/38aebb9a5d3b33e2b34aecea16d0fe39625636d1


Error while training penn mpii multimodel

Hello,
Firstly, Thank you for your work. I found the paper very interesting and just the thing I was looking for.
I want to train the model with my own dataset. But before that I tried to execute your training pipeline with python3 exp/pennaction/train_penn_multimodel.py output/train-penn
I am getting this error after 1 epoch.
Traceback (most recent call last):   File "exp/pennaction/train_penn_multimodel.py", line 160, in <module>     trainer.train(30, steps_per_epoch=steps_per_epoch, initial_epoch=2,   File "/home/ubuntu/3dexperiments/deephar/deephar/trainer.py", line 216, in train     end_of_epoch_callback(epoch)   File "exp/pennaction/train_penn_multimodel.py", line 127, in end_of_epoch_callback     mpii_callback.on_epoch_end(epoch)   File "/home/ubuntu/3dexperiments/deephar/exp/common/mpii_tools.py", line 156, in on_epoch_end     scores = eval_singleperson_pckh(model, self.fval, self.pval,   File "/home/ubuntu/3dexperiments/deephar/exp/common/mpii_tools.py", line 67, in eval_singleperson_pckh     input_shape = model.get_input_shape_at(0)   File "/home/ubuntu/anaconda3/envs/tensorflow2_p38/lib/python3.8/site-packages/keras/engine/base_layer.py", line 2057, in get_input_shape_at     return self._get_node_attribute_at_index(node_index, 'input_shapes',   File "/home/ubuntu/anaconda3/envs/tensorflow2_p38/lib/python3.8/site-packages/keras/engine/base_layer.py", line 2683, in _get_node_attribute_at_index     raise RuntimeError(f'The layer {self.name} has never been called ' RuntimeError: The layer Pose has never been called and thus has no defined {attr_name}. Exception ignored in: <generator object OrderedEnqueuer.get at 0x7f71d0663ba0> Traceback (most recent call last):   File "/home/ubuntu/anaconda3/envs/tensorflow2_p38/lib/python3.8/site-packages/keras/utils/data_utils.py", line 780, in get AttributeError: 'NoneType' object has no attribute 'Empty' Exception ignored in: <generator object OrderedEnqueuer.get at 0x7f71d0663cf0> Traceback (most recent call last):   File "/home/ubuntu/anaconda3/envs/tensorflow2_p38/lib/python3.8/site-packages/keras/utils/data_utils.py", line 780, in get AttributeError: 'NoneType' object has no attribute 'Empty'
I spent quiet a bit of time figuring out but could not. I am not familiar with keras, unfortunately. I would really appreciate any pointers.
Thank you.

Hi @imvinod , sorry for the very late reply. The error comes from https://github.com/dluvizon/deephar/blob/fbebb148a3b7153f911b86e1a7300aa32c336f31/exp/common/mpii_tools.py#L67 from Keras. Have you checked the model at this point?


[Feature]:  public access for CRD struct

Description about the feature
Wee need to allow users to operate crd resources outside xline-operator (for example, create xline cluster), which means that the struct corresponding to operator crd should be publicly accessible, currently within the crate scope.
https://github.com/xline-kv/xline-operator/blob/1a15e69438eb46becf752a4de362627890e1e26b/operator-k8s/src/crd/v1alpha1/cluster.rs#L31-L33
This is a good first issue for me,  i want to work for it and assign me please,Thanks. Remind me if i missed something.
Code of Conduct

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

Should xline-operator be used as a binary, so there is no need to provide a public CRD definition as a library?

Absolutely, xline-operator run as a binary,  At the same time, the CRD definition should also be provided as a libiary so that others can use it.
Let user can apply CR with rust code and not kubectl for integration into their platform.

Absolutely, xline-operator run as a binary, At the same time, the CRD definition should also be provided as a libiary so that others can use it.
Let user can apply CR with rust code and not kubectl for integration into their platform.

That makes sense, I suggest move these CRDs into a separated crate.

I suggest move these CRDs into a separated crate.

@iGxnon ,How about xline-operator-api, I thought this might cause some confusion given that the operator-api crate already exists.

I suggest move these CRDs into a separated crate.

@iGxnon ,How about xline-operator-api, I thought this might cause some confusion given that the operator-api crate already exists.

operator-api is used to reduce the coupling between operator and sidecar. A simple name crd-api might be sufficient

I'll handle this in #37

This is not need any more due to the xline-operator is rewriting with golang.
closing...


Error: Property Sort

Property Sort  Order throws the following error:
/Users/minamarkham/fooBar/node_modules/gulp-sass-lint/node_modules/sass-lint/lib/rules/property-sort-order.js:73
              name = prop.first('ident').content;
                                        ^
TypeError: Cannot read property 'content' of undefined
    at /Users/minamarkham/fooBar/node_modules/gulp-sass-lint/node_modules/sass-lint/lib/rules/property-sort-order.js:73:41
    at Node.forEach (/Users/minamarkham/fooBar/node_modules/gulp-sass-lint/node_modules/sass-lint/node_modules/gonzales-pe/lib/node/basic-node.js:1:2053)
    at /Users/minamarkham/fooBar/node_modules/gulp-sass-lint/node_modules/sass-lint/lib/rules/property-sort-order.js:71:15
    at RootNode.traverseByType (/Users/minamarkham/fooBar/node_modules/gulp-sass-lint/node_modules/sass-lint/node_modules/gonzales-pe/lib/node/root-node.js:1:1739)
    at Object.module.exports.detect (/Users/minamarkham/fooBar/node_modules/gulp-sass-lint/node_modules/sass-lint/lib/rules/property-sort-order.js:63:9)
    at /Users/minamarkham/fooBar/node_modules/gulp-sass-lint/node_modules/sass-lint/index.js:50:25
    at Array.forEach (native)
    at Function.sassLint.lintText (/Users/minamarkham/fooBar/node_modules/gulp-sass-lint/node_modules/sass-lint/index.js:49:9)
    at DestroyableTransform._transform (/Users/minamarkham/fooBar/node_modules/gulp-sass-lint/index.js:32:27)
    at DestroyableTransform.Transform._read (/Users/minamarkham/fooBar/node_modules/gulp-sass-lint/node_modules/through2/node_modules/readable-stream/lib/_stream_transform.js:172:10)

It seems to finish linting, but throws this error at the end.

Do you have a reduced sample of Sass where this error is occouring?

I isolated the problem to my _mixins.scss and _functions.scss files, which don't actually have any selectors in them. Could that be the problem?

Can you provide a concise example of where it's breaking?

As far as I can tell, it's caused by the assignment of a value to a variable within a function block.

@function test(foo) {
    // The line below causes the problem
    $bar: foo;
}

Here:
@mixin placeholder {
  $placeholders: ":-webkit-input" ":-moz" "-moz" "-ms-input";
  @each $placeholder in $placeholders {
    &:#{$placeholder}-placeholder {
      @content;
    }
  }
}

and here
@function em($target, $context: $base-font-size) {
  @if not unitless($target) {
    $target: strip-units($target);
  }
  @if not unitless($context) {
    $context: strip-units($context);
  }
  @if $target == 0 { @return 0 }
  @return $target / $context + 0em;
}


Support custom dimensions in GA pageviews and events

Checklist
Put an x in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code.

[x] I have added tests that prove my fix is effective or that my feature works.
[x] I have added all necessary documentation (if appropriate)

What was done
These changes adds support for custom dimensions when tracking events and page views in Google Analytics. The API adopted here was directly taken directly from the discussion in #278.
Associated Issues

Fixes #278

If you'd like to test these changes they are available in:
npm install @redux-beacon/google-analytics@next


Feature Request:  Expose sqlite3_busy_handler to Python side

Would it be possible to wire up sqlite3_busy_handler() so that Python busy handlers can be used?
https://www.sqlite.org/c3ref/busy_handler.html
The Ruby folks have done a ton of research on how to use sqlite3 on production websites and it mostly revolves around the right pragmas and replacing the default busy wait with a fast wait loop.  I'd like to be able to do that on my Flask app as well.
I'd be willing to test and contribute as best I can.

I'd be wary of anyone claiming to have a silver bullet. I'd also be wary of using a custom busy handler written in Python because it necessarily must acquire the GIL and hold it while calling your custom busy handler. For my own use, I wrote a custom "aggressive" busy handler (lol): https://github.com/coleifer/peewee/blob/master/playhouse/_sqlite_ext.pyx#L1604-L1629
The idea with the above code, as the comment indicates, is that oftentimes concurrent queries are kicked-off around the same time which can cause the connections wanting the lock to proceed in lockstep -- so instead we add some random jitter along w/more "attempts" in a given interval of time. The above code also does NOT acquire the GIL, being implemented in C only.
Here you can see the default sqlite3 busy handler to get an idea of the difference:
https://github.com/sqlite/sqlite/blob/afb879858067f0fda250ffa0a5762e62c4d16a64/src/main.c#L1688-L1729
Nonetheless, if you want a footgun because the toeless ruby guys have one, godspeed. Added:

Connection.set_busy_handler(busy_handler) -> busy handler accepts a single integer argument, which is the number of times the handler has been invoked waiting for the lock. Return 0 to trigger SQLITE_BUSY else to keep trying.
Connection.set_busy_timeout(int seconds) -> restore default busy handler w/the given timeout in seconds.

First off, thank you for the super-fast turnaround.  It's truly appreciated.
Definitely not looking for a footgun, will dig in a little further before I decide how to proceed.
Cheers!


Api changes

So this is where I am with allowing api in standalone + updating the api.
The standalone api should be working when the options --api is enabled.
There's still a lot of things missing like the gradio auto documentation is pretty bad. I would like auto docs + wiki docs eventually (wiki docs really needs to include dates). There's some clunky stuff in the api_constants.py that eventually I'd like to remove, but it doesn't seem so bad for now.
I'm going to be heading away for a couple of days. So if you did want to try to integrate the api, hopefully this is helpful. I'll format it and rigorously test when I return.
Maybe having a dedicated api branch would be helpful too?

core.py and  video_mode.py changes are because this is based on an old commit

@graemeniedermayer Thanks for the effort! API is a very good feature to expand. Great to see that standalone API can be done (Gradio-less would be even better). The code needs some changes before we can safely allow users to use it (so they are not confused and there is less breakage in the future) - I've dropped some comments on how it could be done. Please read them all before changing the code.
Btw, there has been requests to add API for other features that we provide - but this could be added after otherwise it looks good.

 Sorry, I dont know how to fix it and not break anything :sweat_smile:

@graemeniedermayer Sorry for being absent for some time. Would you still like to mainline this? There need to be some changes... Maybe extract the most important changes into a separate MR - usually mainlining small changes is easier than large changes.

@semjon00 Sorry I've gotten quite busy as well. I'll try to get to this in the next few days!


add play/pause button to device

Basic PR adding play/pause functionality to the device, following PR will hook it up into the /abort endpoint.
open to feedback for icons and language...

@imaitland & @amitschang Looking at https://github.com/ssec-jhu/evolver-ng/pull/200, I would think the UI needs a safety measure to account for someone hitting "play" when something is already running. Otherwise, it'll clobber everything (e.g., config on file) and restart.

I have no idea what I'm looking at to review the .tsx file.

Looks like you might have possible left in some dependency requirements files that shouldn't have? 🤷

I like the look of the button though from the vid-snippet you posted in the description.

I would have approved if it weren't for the package.json and package-lock.json.

Do my comments regarding changes to package.json and package-lock.json make sense? Happy to break them out into a seperate pr, tho i don't think this is necessary here.

@imaitland & @amitschang Looking at ssec-jhu/evolver-ng#200, I would think the UI needs a safety measure to account for someone hitting "play" when something is already running. Otherwise, it'll clobber everything (e.g., config on file) and restart.

@jamienoss what specifically does it clobber?
My understanding is that sending a POST request to /stop does the following:

toggle config flags:
config.enable_control = False
config.enable_commit = False
Save config to evolver.yml

so nothing should be clobbered (except those flags) by stopping and then starting the evolver?

Re: https://github.com/ssec-jhu/evolver-ui/pull/5#issuecomment-2450551893
That's correct, but only if you abort first. It would be a shame to accidentally click start whilst an experiment is already running and thus restart it.

Re: #5 (comment)
That's correct, but only if you abort first. It would be a shame to accidentally click start whilst an experiment is already running and thus restart it.

start/stop as implemented in this pr is a toggle. So from a UX pov - you can't start an already running evolver.
User can do whatever they want against the http api.
If there needs to be a guard it should be on the device's /start http endpoint, if there isn't one already - i.e. make it impossible to start an already running evovler.

start/stop as implemented in this pr is a toggle. So from a UX pov - you can't start an already running evolver.

Awesome! 👍


Align app_version struct member types to MCUBOOT image_version struct members

Would it make sense to define the app_version struct to more closely align with the  MCUBOOT image_version struct?
Specifically the sizes of patch and commit. It seems like those could grow beyond the range of a byte (potentially), unless I'm misunderstanding the workflow for versioning.
I don't think anything else should be changed, in fact its nice having the hash and build type information.

Not a bad idea. I haven't had a chance to play with a more direct Mcuboot integration. Maybe soon though!

I mentioned this in a youtube comment, but I believe setting CONFIG_MCUBOOT_EXTRA_IMGTOOL_ARGS  to "--version x.y.z+c" is the only way at the moment. Maybe the cmake script can generate and place it at the end of version.conf, unless there's a better place.

I had to add this line to my CMakeLists.txt.
file(APPEND conf/version.conf "CONFIG_MCUBOOT_IMAGE_VERSION=\"${version_major}.${version_minor}.${version_patch}+${version_commit}\"\n")

Give it a shot on your end and let me know how it goes @tdbenson

Thanks. That will work nicely. I'm surprised this option isn't defined in the official Zephyr repository.


github action refactored to test tx-gas.mjs test suites

To run test-gas properly, we need to set the number of transactions in a block to be 32 (rather than the 2 we usually use for the other tests) but I can't figure out if this is being done here.

correction done

I think this was caused by me removing the Geth-based tests.  Now that we run Geth in a separate docker project, these tests no longer work.

I think this was caused by me removing the Geth-based tests. Now that we run Geth in a separate docker project, these tests no longer work.

conflict resolved


[NEW]: Celsius CEO Cashed in After Bankrupt Crypto Lender's Token Surged

Date
2022-08-10
Description
While a group of traders has been busy pumping the bankrupt crypto lender Celsius Network’s founder cashed out some of his CEL token holdings, which have multiplied in value even as his company struggles
Links
https://finance.yahoo.com/news/dormant-wallet-linked-alex-mashinsky-193345899.html
Agreement

[X] I irrevocably agree to release my contribution under the CC-BY 3.0 License

Attribution name
Patrick Wood
Personal link
No response

https://web3isgoinggreat.com/?id=celsius-ceo-alex-mashinsky-reportedly-sells-off-some-of-his-cel


Why the apollo 3.0 can not routing through the junction?

We appreciate you go through Apollo documentations and search previous issues before creating an new one. If neither of the sources helped you with your issues, please report the issue using the following form. Please note missing info can delay the response time.
System information

Apollo version (3.0):

Steps to reproduce the issue:

The record map is as followed, I want to routing from A to B, but it failed. The reason is also followed.

Supporting materials (screenshots, command lines, code/script snippets):

I think the map you are using is virtual lane, not HD map,  junction information not contained in your virtual lane file

Closed due to inactivity. If the problem persists, pls feel free to reopen it or create a new one and refer to it.


JSON error when Series passed to get_property_labels

get_property_labels does not follow the same pattern as the rest of the API and only takes a list as input. Based on the rest of the API I would expect a Series input to output a dict. Instead I get a json error.
Steps to replicate
dc.get_property_labels(pd.Series(['geoId/sch5101950']))

Same issue for get_triples


Url hostname is no longer validated

Initial Checks

[X] I confirm that I'm using Pydantic V2

Description
Hi everyone, I am currenlty migrating yet another codebase from pydantic 1 to pydantic 2 and have an issue
with Url validation that changed a lot (was a string, and now it is not but I can handle that).
My probleme is that in any url, a hostname can't starts with a - (other rules exists, such as segment size).
Here is a sample of code in pydantic v1 that works
Python 3.11.8 (main, Feb 12 2024, 14:50:05) [GCC 13.2.1 20230801] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> from pydantic import BaseModel, AnyHttpUrl, Field, version
>>> print(version.version_info)
<cyfunction version_info at 0x7e17bc94e5a0>
>>> print(version.version_info())
             pydantic version: 1.10.13
            pydantic compiled: True
                 install path: /home/guillaume/.cache/pypoetry/virtualenvs/xxx-v1yMrRj-py3.11/lib/python3.11/site-packages/pydantic
               python version: 3.11.8 (main, Feb 12 2024, 14:50:05) [GCC 13.2.1 20230801]
                     platform: Linux-6.7.4-arch1-1-x86_64-with-glibc2.39
     optional deps. installed: ['typing-extensions']
>>> from pydantic import BaseModel, AnyHttpUrl, Field, version
>>> class M(BaseModel):
...      u: AnyHttpUrl = Field()
...
>>> M(u="http://-x/")
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "pydantic/main.py", line 341, in pydantic.main.BaseModel.__init__
pydantic.error_wrappers.ValidationError: 1 validation error for M
u
  URL host invalid (type=value_error.url.host)

while migrating a project to pydantic 2, I lost this check and let improper url enter in my database:
Example Code
from pydantic import BaseModel, AnyHttpUrl, Field
class M(BaseModel):
  u: AnyHttpUrl = Field()

M(u=Url('http://-x/'))  # should raise a ValidationError, -x is not a valid hostname

### Python, Pydantic & OS Version

```Text
pydantic version: 2.6.4
        pydantic-core version: 2.16.3
          pydantic-core build: profile=release pgo=true
                 install path: /home/guillaume/.cache/pypoetry/virtualenvs/sequoia-base3-oGZ-ftSE-py3.11/lib/python3.11/site-packages/pydantic
               python version: 3.11.8 (main, Feb 12 2024, 14:50:05) [GCC 13.2.1 20230801]
                     platform: Linux-6.7.4-arch1-1-x86_64-with-glibc2.39
             related packages: typing_extensions-4.7.1
                       commit: unknown

@mardiros,
Thanks for reporting this. Looks related to https://github.com/pydantic/pydantic/issues/7874. We use the URL Rust Crate which makes decisions based on the URL Standard.
Going to close this for now, but I'd recommend opening an issue there regarding your question about URL validity!

For the update, from rust-url and whatwg-url
They consider themself has "parser" not "validator". So there will never check hostname format here.
Pydantic is a validator (a user data validation library), so the url host invalid is a regression from pydantic 1 that I can live with.


Name clash between io.spine.protodata.Configuration and org.gradle.api.artifacts.Configuration

The first impression when I look at ProtoData code is that I deal with the type from Gradle. It's a bit misleading. Maybe the issue caused by the fact that I deal with Gradle a bit more than usually a programmer does.
Still, we in ProtoData work in close proximity to Gradle. It's better to avoid confusions.
In our API, Configuration is a sealed class. So maybe it's not a big deal. But I'd like to discuss this issue before we start publishing docs.

The class is @Internal. So, let's forget about it for now.


Added Armors

Added armours do not show up in the game.  They are there but are invisible.

Details
With the community patch installed, any armour that I add with a mod is rendered invisible.  Exile, Mark M, Banshee, and the Mjolnir armours are all invisible when the patch is installed alongside them.
Game Version
<IP_ADDRESS>
Language
English (EN)
New Game
Yes
Reproduction Steps
Install armours alongside patch.

What makes you think this is an issue with the Community Patch? There is no reason for such an interaction to happen, and in fact I run several of the armour mods you mention along the Community Patch just fine.


slow evaluation speed

Hi, I find that the training time is very fast but it seems to be stuck during the final evaluation step. Could you please tell me why? Thanks!
Evaluating Final Parameters ...
7%|██▋                                   | 139/2000 [42:48<7:12:19, 13.94s/it]

Is it getting stuck at 139 step or is it slow inference?
The evaluation is slower because we calculate LPIPS and also store images.

The inference is slow. Is the inference speed normal?

Hi, no, this speed is not normal. Generally, the final evaluation is slow since we write the final output for each eval frame to the disk. However, it shouldn't be 7 hr/sequence. This might be an issue with storage on your end?

okay, I will check it. Thank you!


1.1.0 release looks wonky

https://circleci.com/gh/quicwg/base-drafts/1500
/opt/circleci/.rvm/gems/ruby-2.2.6/bin/kramdown-rfc2629:23:in `load': /opt/circleci/.rvm/gems/ruby-2.2.6/gems/kramdown-rfc2629-1.1.0/bin/kramdown-rfc2629:210: multiple assignment in conditional (SyntaxError)
	from /opt/circleci/.rvm/gems/ruby-2.2.6/bin/kramdown-rfc2629:23:in `<main>'

Oops, I didn't test this with older rubies.  (After a laptop change, I'm not set up for this yet.). Thank god there is all this CI infrastructure around :-)

Thanks for the prompt turnaround.


[WFCORE-617] Allow embedding apps to control the server/HC's 'start t…

…ime'

Core - Full Integration Build 1094 is now running using a merge of 460b113e769ef4317b76f130a7af57bb09ae3eb8

Windows Build 1504 is now running using a merge of 460b113e769ef4317b76f130a7af57bb09ae3eb8

Linux Build 1952 is now running using a merge of 460b113e769ef4317b76f130a7af57bb09ae3eb8

Core - Full Integration Build 1094 outcome was FAILURE using a merge of 460b113e769ef4317b76f130a7af57bb09ae3eb8
Summary: Tests passed: 550, ignored: 190; exit code 1 (new) Build time: 0:04:33
Build problems:
Process exited with code 1

Windows Build 1504 outcome was SUCCESS using a merge of 460b113e769ef4317b76f130a7af57bb09ae3eb8
Summary: Tests passed: 3207, ignored: 71 Build time: 0:23:00

Linux Build 1952 outcome was SUCCESS using a merge of 460b113e769ef4317b76f130a7af57bb09ae3eb8
Summary: Tests passed: 3207, ignored: 71 Build time: 0:25:52

Linux Build 1953 is now running using a merge of ab3f7409c6f7ce67b4b950b7fd064610dc682e7d

Windows Build 1505 is now running using a merge of ab3f7409c6f7ce67b4b950b7fd064610dc682e7d

Core - Full Integration Build 1095 is now running using a merge of ab3f7409c6f7ce67b4b950b7fd064610dc682e7d

Windows Build 1505 outcome was SUCCESS using a merge of ab3f7409c6f7ce67b4b950b7fd064610dc682e7d
Summary: Tests passed: 3207, ignored: 71 Build time: 0:22:21

Linux Build 1953 outcome was SUCCESS using a merge of ab3f7409c6f7ce67b4b950b7fd064610dc682e7d
Summary: Tests passed: 3207, ignored: 71 Build time: 0:25:25

Core - Full Integration Build 1095 outcome was FAILURE using a merge of ab3f7409c6f7ce67b4b950b7fd064610dc682e7d
Summary: Tests failed: 1 (1 new), passed: 2874, ignored: 375, muted: 2 Build time: 0:48:21
Build problems:
Failed tests detected
Failed tests
org.jboss.as.test.clustering.cluster.web.GranularWebFailoverTestCase(SYNC-tcp).testGracefulUndeployFailover: <no details avaliable>

Linux Build 1987 is now running using a merge of a239b68f221fbf38a3b77de1cc0a2a51d37224a8

Core - Full Integration Build 1129 is now running using a merge of a239b68f221fbf38a3b77de1cc0a2a51d37224a8

Windows Build 1537 is now running using a merge of a239b68f221fbf38a3b77de1cc0a2a51d37224a8

Windows Build 1537 outcome was SUCCESS using a merge of a239b68f221fbf38a3b77de1cc0a2a51d37224a8
Summary: Tests passed: 3209, ignored: 71 Build time: 0:25:38

Linux Build 1987 outcome was SUCCESS using a merge of a239b68f221fbf38a3b77de1cc0a2a51d37224a8
Summary: Tests passed: 3209, ignored: 71 Build time: 0:29:21

Core - Full Integration Build 1129 outcome was FAILURE using a merge of a239b68f221fbf38a3b77de1cc0a2a51d37224a8
Summary: Tests failed: 1 (1 new), passed: 2876, ignored: 377, muted: 1 Build time: 0:55:38
Build problems:
Failed tests detected
Failed tests
org.jboss.as.test.integration.ws.wsse.signencrypt.EJBSignEncryptTestCase.encryptedAndSignedRequest: <no details avaliable>

Core - Full Integration JDK8 Build 8204 outcome was FAILURE using a merge of a239b68f221fbf38a3b77de1cc0a2a51d37224a8
Summary: Exit code 1 (Step: Build & test full (Maven)) (new) Build time: 00:02:41


Failed to download image from google source

Getting error when I try to ran this command python download.py "red car" -limit=150 -dest=folder_name -resize=250x250
Error Log:
[3244:6300:0521/114935.800:ERROR:device_event_log_impl.cc(208)] [11:49:35.800] Bluetooth: bluetooth_adapter_winrt.cc:723 GetBluetoothAdapterStaticsActivationFactory failed: Class not registered (0x80040154)
Traceback (most recent call last):
  File "download.py", line 88, in <module>
    downloader.download_images(keyword)
  File "C:\Users\Vinoth\py-image-dataset-generator\image_grabber\image_downloader.py", line 60, in download_images
    raise (NoImageFoundException("No images found on sources %s" % ",".join(list(self.sources))))
utils.utils.NoImageFoundException: No images found on sources Google

Same error for me, when running code under Manjaro Linux. My debugging turned out, that the following line from the google_grabber.py  creates an empty result - but it shouldn`t:
images = browser.find_elements_by_class_name("rg_meta")


Source code compile and build

When I compile from source code, it will meet an error when compile grpc process(grpc is on v1.27.3 branch). I done this in a nvcr.io/nvidia/pytorch:23.10-py3 docker environment, error is:
Mooncake/grpc/third_party/abseil-cpp/absl/synchronization/internal/graphcycles.cc: In member function ‘void absl::synchronization_internal::GraphCycles::RemoveNode(void*)’:
Mooncake/grpc/third_party/abseil-cpp/absl/synchronization/internal/graphcycles.cc:451:26: error: ‘numeric_limits’ is not a member of ‘std’
451 |   if (x->version == std::numeric_limits<uint32_t>::max()) {
|                          ^~~~~~~~~~~~~~
Mooncake/grpc/third_party/abseil-cpp/absl/synchronization/internal/graphcycles.cc:451:49: error: expected primary-expression before ‘>’ token
451 |   if (x->version == std::numeric_limits<uint32_t>::max()) {
|                                                 ^
Mooncake/grpc/third_party/abseil-cpp/absl/synchronization/internal/graphcycles.cc:451:52: error: ‘::max’ has not been declared; did you mean ‘std::max’?
451 |   if (x->version == std::numeric_limits<uint32_t>::max()) {
|                                                    ^~~
|                                                    std::max

You may need to use export CXXFLAGS='-include /usr/include/c++/11.2.0/limits' for your Docker env (c.f. https://github.com/gpujs/gpu.js/issues/753). In addition, we prefer to use grpc from system's repository (such as apt-get install).

You may need to use export CXXFLAGS='-include /usr/include/c++/11.2.0/limits' for your Docker env (c.f. gpujs/gpu.js#753). In addition, we prefer to use grpc from system's repository (such as apt-get install).

I resolve this error by choosing a commit_id fixed absel version problems.
But when I try to compile Mooncake, error is:

I have apt-get install libibverbs-dev, and set the LIBRARY_PATH/LD_LIBRARY_PATH for -libverbs

This error can reproduce with a simple test_verbs.c ， in which:
#include <infiniband/verbs.h>
#include <stdio.h>
int main() {
printf("libibverbs is installed and accessible.\n");
return 0;
}
gcc -o test_verbs test_verbs.c -L /usr/lib/x86_64-linux-gnu -libverbs

You may need to use export CXXFLAGS='-include /usr/include/c++/11.2.0/limits' for your Docker env (c.f. gpujs/gpu.js#753). In addition, we prefer to use grpc from system's repository (such as apt-get install).

I resolved by change grpc codebase. Thanks a lot


Multiple actions

Would it be possible to implement more than one action while dragging (the X button and something else for example)?

No, you can't.

I can't, but can You? :)

FloatingView library does not support the feature.


Made property Description on GetFirmwareVersionResponse optional

Made property Description on GetFirmwareVersionResponse optional

 You should sign our Contributor License Agreement in order to get your pull request merged.

All is well.


Use different labels for different buttons (toggle vs refresh)

As pointed out at https://github.com/commons-app/apps-android-commons/commit/784b51e29d0a07a3f343dcf1cd374bae25fc5636#r22247055 there doesn't seem to be a good reason to have "Refresh" for the toggle button.

There was a merge conflict which I have now resolved.


Start TerminalView in the working directory I'm currently in for ST 3

It would be a cool feature to have if TerminalView can be configured to start in the current working directory for the project that I'm working on currently in ST3. Does anyone know if it is possible to configure this?

See: https://github.com/Wramberg/TerminalView/issues/41

That's exactly what I was looking for. Thanks!


Refactor banner / connection implementation

self.banner is inconsistently set and handled on several view controllers. Many of these actions are spread across the interfaces, and could be cleanly implemented once in CustomNavigationController or some shared class / protocol.

Every view should dismiss banners upon viewWillDisappear and reset the status bar.
The status bar should be changed using preferredStatusBarStyle, which can be set based on a boolean indicating the status.
All banners should have the same settings (autoDismiss, dismissOnTap, etc.)

Additionally, I believe we can have one instance of Reachability that works throughout the app.

Update
If getBusLocations returns success : false, a banner does not show on RouteDetailViewController. Should make sure this error appears, and any other potential errors.

Update
Banners currently do not dismiss when internet is re-connected. Fix!


Enhancement Proposal for SEO Improvement - Adding Keywords Support

Hello, i hope this message finds you well. Firstly, i want to commend you on the exceptional work you've done with the hugo-theme-dream.
Proposal:
I've noticed that the theme has strong SEO features, which is great for improving search engine visibility. However, I believe that incorporating support for keywords further enhance the theme's SEO capabilities. Keywords are crucial for search engine optimization and could help improve the theme's effectiveness in targeting specific search queries.
Would it be possible to consider adding a feature or option to include keywords in the theme's meta tags?
If you're open to this idea, I'd be happy to provide further details or collaborate on how this feature could be integrated into the theme.
Thank you for considering this enhancement. I look forward to your thoughts and i'm eager to contribute to making the hugo-theme-dream even better.
Best regards,
MaximoVolynets

Thank you @MaximoVolynets. Yes, I'm willing to add keywords support, you've made me realize what was missing from this theme.
After my search, I think it is also very easy to complete this enhancement. Hugo provides an embedded template named schema, we can use it in the theme. I will open a PR and let you know.
Also if you have some additional suggestions, we can continue to discuss them in this issue thread.

A related PR has been opened.


Failed to create to Sample Application

IMPORTANT: Before you create an issue, please take a look at our Issue Reporting Guide.
Briefly summarize your issue:

Init failed
What is the expected behavior?

Init
What behavior are you observing?

Sample never starts. I get this failed reason.
AuthDelegate:initFailed:reason=missingConfigurationValue,key=refreshToken
Creation of AuthDelegate failed!
Provide the steps to reproduce the issue, if applicable:

sudo bash startsample.sh config.txt
Tell us about your environment:

What version of the AVS Device SDK are you using?
  Latest one downloaded

Tell us what hardware you're using:

[ ] Desktop / Laptop
[ x] Raspberry Pi
[ ] Other - tell us more:

Tell us about your OS (Type & version):

[ ] Linux
[ ] MacOS
[ x] Raspbian Stretch
[ ] Raspbian Jessy
[ ] Other - tell us more:

With SDK 1.7 we have a new authentication mechanism called CBLAuthDelegate and the configuration parameters have changed. Please use the instructions under
https://github.com/alexa/avs-device-sdk/wiki/Code-Based-Linking----Configur...
for migrating to CBL. If you already have the refresh token, you can pass it into SQLiteCBLAuthDelegateStorage::setRefreshToken(const std::string& refreshToken) to simulate authenticating via CBL.

Hi @Dusty109,
Have you been able to successfully authenticate using the new CBL method?

Closing due to inactivity. Please reopen if you have further questions.


Disable dropout in DPO Training

Helps stabilising training.
For now, I only added disable_dropout to DPO Training, but let me know if you think it should go to DPOTrainer with a config to disable
cc @kashif

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint.

LGTM! lets add it to the trainer I would say...

@kashif  Done!

thank you so much!