test Non3GPP fails

Describe the bug
A clear and concise description of what the bug is.
TestNon3GPP fails on a fresh installation on ubuntu 20.04
It always stuck at:
time="2022-04-04T10:01:42Z" level=error msg="Set XFRM rules failed: invalid argument" category=IKE component=N3IWF
time="2022-04-04T10:01:42Z" level=error msg="Applying XFRM rules failed: Set XFRM state rule failed" category=IKE component=N3IWF
claiming for an invalid argument ,and need to be killed
the XFRM rule that fails should be, but i can be wrong...
time="2022-04-04T10:01:42Z" level=info msg="Dst: <IP_ADDRESS>, Src: <IP_ADDRESS>, Proto: esp, Mode: tunnel, SPI: 0xab581b91, ReqID: 0x0, ReplayWindow: 0, Mark: (0x5,0x0), OutputMark: 0, Ifid: 0, Auth: {Name: hmac(sha1), Key: 0x8ca113cdca4313050a8b5fd6e24324fd29cfb35f}, Crypt: {Name: cbc(aes), Key: 0xb99369e69c0116a6fc35124db975a619f10c54870b7db52130766d18ebc3592e}, Aead: , Encap: , ESN: false\n" category=IKE component=N3IWF
what i'm missing ?
To Reproduce
Steps to reproduce the behavior:

Change config '...' no changes to default cfg files

Code patch '...' (You can fork the project and give us the patch diff you have modified)
I just added a print in n3iwf.log of xfrmState to the code in file NFs/n3iwf/pkg/ike/handler/xfrm.go, just to see what is passed to FrmStateAdd when the code stuck

Run command '...' ./test.sh TestNon3GPP

Dump packet '...'

Expected behavior
A clear and concise description of what you expected to happen.
TestNon3GPP completes correctly
Environment (please complete the following information):

free5GC Version: [e.g. v3.1.0]
OS: e.g. Ubuntu 20.04 Server (running in an lxd container, but same behaviour on the host)
Kernel version: 5.4.0-107-generic
go version: go version go1.14.4 linux/amd64
c compiler version (Option): gcc version 9.4.0 (Ubuntu 9.4.0-1ubuntu1~20.04.1)

Log File
Provide the program log file here.
n3iwf.log attached
n3iwf.log

Did you pass the TestNon3GPP without adding any code?

No, test didn't pass with a fresh installation.
I added the print statement in the code to try to understand what happens, but my go and xrfm knowledge are not enough at the moment to understand where the problem is...

In my opinion , this is kernel version problem.
You can try to downgrade the kernel version to before 100, such as 5.4.0-91-generic.

Hi
you opinion is right!
TestNon3GPP completes correctly with kernel version <IP_ADDRESS>
so, question for developers is...
the issue could be fixed or i am forced to use a specifica kernel version ?
thanks

https://github.com/vishvananda/netlink/issues/750#issuecomment-1109391763

Hi, thanks for the reference
So, i understood this is a kernel issue, and that with next kernel versions the test will pass successfuly again
Am I right ?
Last available kernel right now is 5.4.0-109-generic, i will verify if problem is still present here
thanks

my current machine configuration is:
OS:- ubuntu 20.04
kernel version:- 5.13.0-44-generic
when i am downgrading kernel below 100 some of the modules of kernel stops working properly.
So I think downgrading the kerenel is not an good option.
Is there any other solution.
the issue is same for:
OS:- ubuntu 18.04
kernel version:- 5.4.0-110-generic
any help will be appriciated.

Actually using the version v3.2.0 / v3.2.1 (following the official installation), it is impossible to complete the TestNon3GPP. It seems the N3IWF can't contact the UPF, in the following the log:
[...]
2022-09-05T15:18:56Z [INFO][SMF][PduSess] Sending PFCP Session Establishment Request
2022-09-05T15:18:56Z [INFO][UPF][Pfcp][<IP_ADDRESS>:8805] handleSessionEstablishmentRequest
2022-09-05T15:18:56Z [INFO][UPF][Pfcp][<IP_ADDRESS>:8805][rNodeID:<IP_ADDRESS>][SEID:L(0x1),R(0x1)] New session
2022-09-05T15:18:56Z [INFO][LIB][PFCP] Remove Request Transaction [2]
2022-09-05T15:18:56Z [INFO][SMF][PduSess] Received PFCP Session Establishment Accepted Response
2022-09-05T15:18:56Z [INFO][SMF][GIN] | 201 |       <IP_ADDRESS> | POST    | /nsmf-pdusession/v1/sm-contexts |
2022-09-05T15:18:56Z [INFO][AMF][GMM][SUPI:imsi-2089300007487] create smContext[pduSessionID: 1] Success
2022-09-05T15:18:56Z [INFO][AMF][Producer] Handle N1N2 Message Transfer Request
2022-09-05T15:18:56Z [INFO][AMF][NGAP][<IP_ADDRESS>/<IP_ADDRESS>/<IP_ADDRESS>/<IP_ADDRESS>/<IP_ADDRESS>/<IP_ADDRESS>/<IP_ADDRESS>:34435][AMF_UE_NGAP_ID:1] Send PDU Session Resource Setup Request
2022-09-05T15:18:56Z [INFO][N3IWF][NGAP] [N3IWF] Handle PDU Session Resource Setup Request
2022-09-05T15:18:56Z [INFO][AMF][GIN] | 200 |       <IP_ADDRESS> | POST    | /namf-comm/v1/ue-contexts/imsi-2089300007487/n1-n2-messages |
|
|
2022-09-05T15:19:01Z [ERRO][N3IWF][GTP] Dial to UPF failed: read udp <IP_ADDRESS>:2152: i/o timeout
2022-09-05T15:19:01Z [ERRO][N3IWF][NGAP] Setup GTP connection with UPF failed: Dial failed
|
|
2022-09-05T15:19:01Z [INFO][N3IWF][NGAP] [N3IWF] Send PDU Session Resource Setup Response
2022-09-05T15:19:01Z [INFO][AMF][NGAP][<IP_ADDRESS>/<IP_ADDRESS>/<IP_ADDRESS>/<IP_ADDRESS>/<IP_ADDRESS>/<IP_ADDRESS>/<IP_ADDRESS>:34435][AMF_UE_NGAP_ID:1] Handle PDU Session Resource Setup Response
2022-09-05T15:19:01Z [INFO][SMF][PduSess] Receive Update SM Context Request
2022-09-05T15:19:01Z [INFO][SMF][PduSess] In HandlePDUSessionSMContextUpdate
2022-09-05T15:19:01Z [ERRO][SMF][PduSess] Handle PDUSessionResourceSetupResponseTransfer failed: sequence truncated
2022-09-05T15:19:01Z [WARN][SMF][PduSess] SM Context State [Active] shouldn't be here
2022-09-05T15:19:01Z [INFO][SMF][GIN] | 200 |       <IP_ADDRESS> | POST    | /nsmf-pdusession/v1/sm-contexts/urn:uuid:728fef01-6b1c-4abb-8f2c-a81679032970/modify |
[stuck]

@neel-shail
Hi, please check the recommand environment in free5GC wiki, since the project is developed based on the environment.
Please let me know if it works.


feat: [FW-13] add home page

Add hero section
Add how it works section
Add animations using framer-motion

Could we have separate PRs for the 3 points in the description. So reviewing is much simpler and changes are smaller 😄


Error while processing the html

Hi. I'm getting the error while parsing some kinds of html markdown. Here is simple example:
link

That snippet can be copied to https://caja.appspot.com/ after pressing Cajole getting the error:
Uncaught TypeError: Cannot read property 'hasScheme' of null

at
ses-single-frame.js?debug=1:32638

The reason of that error is \n after href parameter. As quick workaround I can single lined that html and it works fine, but there is side effect with other htmls (for example with
 tag)

That's not valid HTML, so Caja doesn't support it.  You can say
link

but you can't have line breaks inside the quotes.

Actually, newlines in attribute values are permitted (and sometimes used purposefully in title/alt attributes). I'm not sure whether it's okay by the specs to have whitespace around a URI value, but in any case Caja shouldn't be “crashing” on this input whether or not it is conformant.


Console pod in crashloopbackoff on a baremetal deployment

I have deployed a cluster with 3 control and 2 worker nodes with RHCOS 4.4.3 OS. The issue with the deployment is that all the pods are coming up successfully but only the console pod fails and throws the below errors.
[root@ocp-svc ~]# oc describe pod console-56c9b69c8b-jvhhr -n openshift-console
Name:                 console-56c9b69c8b-jvhhr
Namespace:            openshift-console
Priority:<PHONE_NUMBER>
Priority Class Name:  system-cluster-critical
Node:                 ocp-cp-3.lab.ocp.lan/<IP_ADDRESS>
Start Time:           Wed, 28 Oct 2020 12:29:06 +0530
Labels:               app=console
                      component=ui
                      pod-template-hash=56c9b69c8b
Annotations:          cni.projectcalico.org/podIP: <IP_ADDRESS>/32
                      cni.projectcalico.org/podIPs: <IP_ADDRESS>/32
                      console.openshift.io/console-config-version: 18040
                      console.openshift.io/default-ingress-cert-config-version: 13038
                      console.openshift.io/image:
                        quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:c26b6c699b2095eb44387b84504557f3b635938671fe0af5eb7ab2b4c65cfd4f
                      console.openshift.io/oauth-secret-version: 13071
                      console.openshift.io/proxy-config-version: 571
                      console.openshift.io/service-ca-config-version: 10343
                      console.openshift.io/trusted-ca-config-version: 10346
                      k8s.v1.cni.cncf.io/network-status:
                        [{
                            "name": "k8s-pod-network",
                            "ips": [
                                "<IP_ADDRESS>"
                            ],
                            "default": true,
                            "dns": {}
                        }]
                      k8s.v1.cni.cncf.io/networks-status:
                        [{
                            "name": "k8s-pod-network",
                            "ips": [
                                "<IP_ADDRESS>"
                            ],
                            "default": true,
                            "dns": {}
                        }]
                      openshift.io/scc: restricted
Status:               Running
IP:                   <IP_ADDRESS>
IPs:
  IP:           <IP_ADDRESS>
Controlled By:  ReplicaSet/console-56c9b69c8b
Containers:
  console:
    Container ID:  cri-o://912597a682f0de6603f579d21dc15c5578875298fec01cd72e3ead62fcfeab2a
    Image:         quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:c26b6c699b2095eb44387b84504557f3b635938671fe0af5eb7ab2b4c65cfd4f
    Image ID:      quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:c26b6c699b2095eb44387b84504557f3b635938671fe0af5eb7ab2b4c65cfd4f
    Port:          8443/TCP
    Host Port:     0/TCP
    Command:
      /opt/bridge/bin/bridge
      --public-dir=/opt/bridge/static
      --config=/var/console-config/console-config.yaml
      --service-ca-file=/var/service-ca/service-ca.crt
    State:       Waiting
      Reason:    CrashLoopBackOff
    Last State:  Terminated
      Reason:    Error
      Message:   08:17:37Z auth: error contacting auth provider (retrying in 10s): request to OAuth issuer endpoint https://oauth-openshift.apps.lab.ocp.lan/oauth/token failed: Head https://oauth-openshift.apps.lab.ocp.lan: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)
2020-10-29T08:17:52Z auth: error contacting auth provider (retrying in 10s): request to OAuth issuer endpoint https://oauth-openshift.apps.lab.ocp.lan/oauth/token failed: Head https://oauth-openshift.apps.lab.ocp.lan: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)
2020-10-29T08:18:07Z auth: error contacting auth provider (retrying in 10s): request to OAuth issuer endpoint https://oauth-openshift.apps.lab.ocp.lan/oauth/token failed: Head https://oauth-openshift.apps.lab.ocp.lan: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)
2020-10-29T08:18:17Z auth: error contacting auth provider (retrying in 10s): request to OAuth issuer endpoint https://oauth-openshift.apps.lab.ocp.lan/oauth/token failed: Head https://oauth-openshift.apps.lab.ocp.lan: EOF
2020-10-29T08:18:32Z auth: error contacting auth provider (retrying in 10s): request to OAuth issuer endpoint https://oauth-openshift.apps.lab.ocp.lan/oauth/token failed: Head https://oauth-openshift.apps.lab.ocp.lan: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)
2020-10-29T08:18:47Z auth: error contacting auth provider (retrying in 10s): request to OAuth issuer endpoint https://oauth-openshift.apps.lab.ocp.lan/oauth/token failed: Head https://oauth-openshift.apps.lab.ocp.lan: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)
2020-10-29T08:18:57Z auth: error contacting auth provider (retrying in 10s): request to OAuth issuer endpoint https://oauth-openshift.apps.lab.ocp.lan/oauth/token failed: Head https://oauth-openshift.apps.lab.ocp.lan: EOF

      Exit Code:    2
      Started:      Thu, 29 Oct 2020 13:45:42 +0530
      Finished:     Thu, 29 Oct 2020 13:49:02 +0530
    Ready:          False
    Restart Count:  261
    Requests:
      cpu:        10m
      memory:     100Mi
    Liveness:     http-get https://:8443/health delay=150s timeout=1s period=10s #success=1 #failure=3
    Readiness:    http-get https://:8443/health delay=0s timeout=1s period=10s #success=1 #failure=3
    Environment:  <none>
    Mounts:
      /etc/pki/ca-trust/extracted/pem from trusted-ca-bundle (ro)
      /var/console-config from console-config (ro)
      /var/default-ingress-cert from default-ingress-cert (ro)
      /var/oauth-config from console-oauth-config (ro)
      /var/run/secrets/kubernetes.io/serviceaccount from console-token-9qn58 (ro)
      /var/service-ca from service-ca (ro)
      /var/serving-cert from console-serving-cert (ro)
Conditions:
  Type              Status
  Initialized       True
  Ready             False
  ContainersReady   False
  PodScheduled      True
Volumes:
  console-serving-cert:
    Type:        Secret (a volume populated by a Secret)
    SecretName:  console-serving-cert
    Optional:    false
  console-oauth-config:
    Type:        Secret (a volume populated by a Secret)
    SecretName:  console-oauth-config
    Optional:    false
  console-config:
    Type:      ConfigMap (a volume populated by a ConfigMap)
    Name:      console-config
    Optional:  false
  service-ca:
    Type:      ConfigMap (a volume populated by a ConfigMap)
    Name:      service-ca
    Optional:  false
  default-ingress-cert:
    Type:      ConfigMap (a volume populated by a ConfigMap)
    Name:      default-ingress-cert
    Optional:  false
  trusted-ca-bundle:
    Type:      ConfigMap (a volume populated by a ConfigMap)
    Name:      trusted-ca-bundle
    Optional:  false
  console-token-9qn58:
    Type:        Secret (a volume populated by a Secret)
    SecretName:  console-token-9qn58
    Optional:    false
QoS Class:       Burstable
Node-Selectors:  node-role.kubernetes.io/master=
Tolerations:     node-role.kubernetes.io/master:NoSchedule
                 node.kubernetes.io/memory-pressure:NoSchedule
                 node.kubernetes.io/not-reachable:NoExecute for 120s
                 node.kubernetes.io/not-ready:NoExecute for 300s
                 node.kubernetes.io/unreachable:NoExecute for 120s
Events:
  Type     Reason     Age                  From     Message
  ----     ------     ----                 ----     -------
  Warning  Unhealthy  10h (x718 over 33h)  kubelet  Liveness probe failed: Get https://<IP_ADDRESS>:8443/health: dial tcp <IP_ADDRESS>:8443: connect: connection refused
  Warning  Unhealthy  8h (x5232 over 33h)  kubelet  Readiness probe failed: Get https://<IP_ADDRESS>:8443/health: dial tcp <IP_ADDRESS>:8443: connect: connection refused
  Warning  BackOff    8h (x3125 over 32h)  kubelet  Back-off restarting failed container

I did further debugging and found out that oauth-openshift.apps.lab.ocp.lan is not reachable from the inside pod but from the node its reachable here are the nslookup outputs from the nodes and from inside the pods:
[core@ocp-cp-2 ~]$ nslookup oauth-openshift.apps.lab.ocp.lan
Server:         <IP_ADDRESS>
Address:        <IP_ADDRESS>#53

Name:   oauth-openshift.apps.lab.ocp.lan
Address: <IP_ADDRESS>

[core@ocp-cp-3 ~]$ nslookup oauth-openshift.apps.lab.ocp.lan
Server:         <IP_ADDRESS>
Address:        <IP_ADDRESS>#53

Name:   oauth-openshift.apps.lab.ocp.lan
Address: <IP_ADDRESS>

[root@ocp-svc ~]# oc get pods -n openshift-console
NAME                         READY   STATUS    RESTARTS   AGE
console-56c9b69c8b-jvhhr     0/1     Running   263        25h
console-56c9b69c8b-mr5g7     1/1     Running   0          25h
downloads-7588464d99-46t54   1/1     Running   0          6d4h
downloads-7588464d99-xsj72   1/1     Running   0          6d4h

[root@ocp-svc ~]# oc rsh console-56c9b69c8b-mr5g7
sh-4.2$ nslookup oauth-openshift.apps.lab.ocp.lan
;; connection timed out; no servers could be reached

sh-4.2$ exit
exit
command terminated with exit code 1

[root@ocp-svc ~]# oc rsh console-56c9b69c8b-jvhhr
sh-4.2$ nslookup oauth-openshift.apps.lab.ocp.lan
;; connection timed out; no servers could be reached

Looks like the issue is within the pod not able to reach that domain. But the nodes are able to resolve the domain.
Let me know if there can be a workaround or a fix to this issue.
Im using calico as my CNI and I can say that calico works fine as all other pods are working fine. But it seems that only for console pod its not working and as its on the calico setup network I suspect its happening due to the CNI. Can you please tell me if anything is wrong?
Expected Behavior

I expect the console pod to come up as I need to access the console
Current Behavior

Console pod fails to come up
Possible Solution

Steps to Reproduce (for bugs)

Setup the calico from the official page of calico and setup the openshift cluster using their official documentation.
Context

We are trying to setup a cluster to deploy VMs
Your Environment

Calico version - latest
Orchestrator version (e.g. kubernetes, mesos, rkt): Openshift 4.4.3
Operating System and version: RHCOS 4.4.3
Link to your project (optional):

Hi @AvRajath . Thanks for bringing this to our attention. It is definitely unexpected that only the console will fail during your install since I would have expected other components to also have trouble as well in cases where there are some large malfunctions with the CNI. Based on what you have provided, it does seem that the issue could be DNS but Calico should not be the one setting up your DNS entries in the pods.
How are you installing OpenShift? Is it using openshift-install or are you provisioning your own nodes?

@AvRajath any update on this?


Update Lab_15_ConfigureAAD_MultiFactorAuthRegPolicy.md

Task 2 is repetitive, cleaned up,
Module: 00
Lab/Demo: 00
Fixes # .
Changes proposed in this pull request:

Thanks for submitting this item.  I am going to not make this change at this time.  I do realize that this step really does not do anything.  It is actually meant to be a quick experience to show that MFA can be configured in several different place.  Most people are very aware of the Conditional Access way of setting it up.  But this per-user version is often missed.  There are some cases where the per-user might be valuable.  It is not super common, so I did not make a more in-depth version; I may reconsider later.  Thanks for submitting the update and please continue to share feedback that you see.


Could not parse your date

This is my code.
s=gn.search('energy digital transformation',helper=True,from_ =date1.strftime("%Y-%m-%d"), to_ =date2.strftime("%Y-%m-%d"))
The following result is obtained.
#Exception: Could not parse your date
Why can't it recognize the date?

I did some research and apparently, it could be the issue with the parsedata module and regex, so I just went into the actual script and removed the part where it needed to parse any data in the first place; so if I already put it in the 'YYYY-MM-DD' format then this alteration would not affect the program whatsoever.

I did some research and apparently, it could be the issue with the parsedata module and regex, so I just went into the actual script and removed the part where it needed to parse any data in the first place; so if I already put it in the 'YYYY-MM-DD' format then this alteration would not affect the program whatsoever.

This "fix" doesn't work for me. Putting a string in 'YYYY-MM-DD' will still yield "error: bad escape \d at position 7" and throw the exception "Could not parse your date."


added border-radious css variable

Pull request checklist
Please check if your PR fulfills the following requirements:

[ ] Tests for the changes have been added (for bug fixes / features)
[ ] Docs have been reviewed and added / updated if needed (for bug fixes / features)
[ ] Build (npm run build) was run locally and any changes were pushed
[ ] Lint (npm run lint) has passed locally and any fixes were made for failures

Pull request type

Please check the type of change your PR introduces:

[ ] Bugfix
[ ] Feature
[ ] Code style update (formatting, renaming)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] Documentation content changes
[ ] Other (please describe):

What is the current behavior?

Issue Number: N/A
What is the new behavior?

Does this introduce a breaking change?

[ ] Yes
[ ] No

Other information

Thanks for the PR. I am going to close this as ion-popover is not a shadow DOM component, so you can just style it directly. Please see my response to your original GitHub issue for more information: https://github.com/ionic-team/ionic/issues/20000. Thanks!


Minor fix projection in IconLayer and TextLayer

Coverage remained the same at 60.86% when pulling d8efb2fe8a5115c3bf2b3aaac672fa115662af8c on xx/billboard into 51ea4fbc04867929b5ee6c841303b402fdbea086 on master.


Use internal links in README to quickstart and other docs

GitHub supports internal links in markdown-files. Why not use it? Also because there is still a link to the published documentation, there is the risk of this documentation is not up-to-date with the current state of the repo.

I was doing some changes and then reverting them back in another commit so I guess it's better to just close this PR and solve the problem elsewhere.
It's just that it is a bit inconsistent to both link to documents internally and link to documentation to the published site. Why does everyone have to have the documentation locally in own repo? (+) would be that the documentation is up-to-date with the version of the template but (-) is possible inconsistencies between template-versions.
Maybe the documentation should just be a different repo all together? (Separate from the template-repo?)
Anyway feel free to close in stead of merge.

@hansvb addressing your concerns.

there is the risk of this documentation is not up-to-date with the current state of the repo.

Firstly, the link to the published docs is provided in the event you are unable to see your published site as it provides the same info. That section (in the README) is also meant to be deleted in favour of your repo's README on initial setup.
The template repo changes along with the docs are all meant to be reviewed and periodically added to your repo. There are no template repo specific docs, they are relevant to your repo to aid you to get familiar with the CI configuration.

GitHub supports internal links in markdown-files. Why not use it?

As explained above, the intention is not to refer to the template repo links but to your own repo's Github pages site.

Why does everyone have to have the documentation locally in own repo?

The purpose of this is to keep your docs closer to the code and in version control. The closer it is to you, to your codebase, the more likely you are to update it and have access to it locally.

(+) would be that the documentation is up-to-date with the version of the template but

As previously stated the docs you get from the template repo is relevant information for you to understand and manage your CI configuration.

(-) is possible inconsistencies between template-versions.

It will only be inconsistent if you fetch changes from the template repo and omit the docs. For instance, when you use the template repo to create your repo, it is a point in time snapshot. You can optionally synchronise with the template repo which will provide you with the next complete set of changes unless you explicitly don't include it.
Hope that clears it up. I'll close this for now.


ID is not necessarily an abbreviation / Freudian code

The linter currently requires variables like GatewayId to be named GatewayID because of this.
The thing is, "Id" in cases like the above is not an initialism/abbreviation/acronym. It is just a shortening from "identifier" or "identification" — not "identity document" or any other two-word term.
I therefore suggest removing ID from that map, because requiring to rename GatewayId to GatewayID does not make any sense.

Duplicate of #89.

I disagree with this issue being truly closed.


patch: API enhancements

Add List filters: secret_types, match_all_labels
Add Expiration date field to iam_credentials and service_credentials API responses

:tada: This PR is included in version 2.0.11 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


feat: Add multiple methods of new services

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


Getting different error when running same cypher using goroutine

Facing different errors while running a cypher to get an array of values from a collection of nodes
running the same cypher in goroutine from s2s API channel, and calling from UI

calling X endpoint of ServiceOne to get an array of interests
calling Y endpoint of ServiceTwo to get some values and calling X endpoint of ServiceOne via S2S channel as goroutine for some other operations

Neo4j version: Enterprise 4.1.3
Neo4j Mode: Single instance
Driver version: v1.8.3
Operating system: macOS BigSur
Steps to reproduce
using this neo4j-go-driver to query a collection of node value as an array with go channels

I used go channels to query the same cipher in multiple golang services, used security rules per service, and created separate user per service

Code Snippet
`
result, err := repository.db.Run("match (person:Person{userId: $userId})-[follows:FOLLOWS]->(interest:Interest) return COLLECT(interest.name) as interests", map[string]interface{}{
"userId": userId,
})
if err != nil {
	return nil, err
}

_, err = result.Summary()

if err != nil {
	return nil, err
}

`

Expected behavior

having this repo call as route called /interests and calling this directly from UI, another API call to XYZ service which internally making an s2s channel call to /interests as a goroutine and facing this error at random intervals. suspecting this is some kind of race condition, the expected behavior is to get data regardless of any race condition

Actual behavior

getting one of the errors listed below

Invalid struct size: 146
Invalid Handle
Map key is not string type: int64
Invalid struct size: 201
Unconsumed data

the error returned by neo4j go driver

Tried solutions as of now:

I'm new to neo4j, I tried increasing the memory configuration in the conf file, but that doesn't work, initially encountered this error in the neo4j docker container, to verify this tried in the neo4j desktop version but ended up in the same error
tried removing the goroutine and tested, this time the frequency of error is reduced somehow but still facing the same issue though
working fine in v4.2.3, facing this issue on 1.x

Hi @hsivakum
This looks like you are accessing the same session/result/transaction instance from multiple Go routines. Only the driver "object" is safe to use from multiple Go routines. This applies to both 1.8 and 4.x branches and is by design. You should only keep instances of the driver object, all other type of objects should be kept local to the current thread.
Please use the 4.2.3 version of the driver instead of the 1.8 one, there is no reason to use the older one in terms of database server compatibility.
If you still have problems with the 4.2.3 version please open another issue with more example of how you use the driver.


A new LinuxSyslog table is not created every 10 days for syslogEvents

Please update this article, it's showing that a new LinuxSyslog table is created every 10 days:
"When you specify syslogEvents, LAD always writes data to a table in Azure storage. You can have the same data written to JSON blobs and/or Event Hubs, but you cannot disable storing data to a table. The partitioning behavior for this table is the same as described for performanceCounters. The table name is the concatenation of these strings:
LinuxSyslog
A date, in the form "YYYYMMDD", which changes every 10 days
Examples include LinuxSyslog20170410 and LinuxSyslog20170609."
The truth is only one table named LinuxSyslogVer2v0 is created

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

ID: 13249027-1524-dd0c-9d83-15a9733a3d19
Version Independent ID: bf8a2d1a-8d9b-228a-6919-16127f315d40
Content: Azure Compute - Linux Diagnostic Extension
Content Source: articles/virtual-machines/extensions/diagnostics-linux.md
Service: virtual-machines-linux
GitHub Login: @abhijeetgaiha
Microsoft Alias: gwallace

@c4rlosmarin I was also on the thread you had offline. You are welcome to submit the PR yourself as well.

Closing as we can work on this offline.


Example of using WinAppDriver within Azure DevOps for a WPF application

I would like to see an example of using WinAppDriver within Azure Devops for a WPF application. I am more wondering where to can I point for it to be able to run the tests.

Do you have WinAppDriver tests running locally with the desired WPF app? The process  for getting it working inside DevOps shouldn't be too different than using any other modern app.


hub create ORGANIZATION/NAME cannot set team_id

$ hub create ORGANIZATION/NAME
Error creating repository: Unprocessable Entity (HTTP 422)
Invalid value for "team_id": ""

I know the team_id which should be assigned to the new repo, but I cannot set it using hub create.

+1, would be amazing to specify team_id and better yet set a default team @mislav it looked from the readme that you guys have the go impl going?

it looked from the readme that you guys have the go impl going?

@scamden Yes, hub is now entirely in Go (except for some test setup which still runs on Ruby)

@mislav you mentioned you would revisit this after go release, any thoughts yet?

@scamden Yes we need to revisit this. It's in our 2.3 milestone, and we'll get to it eventually.

awesome good to hear
On 29 June 2015 at 15:11, Mislav Marohnić<EMAIL_ADDRESS>wrote:

@scamden https://github.com/scamden Yes we need to revisit this. It's
in our 2.3 milestone, and we'll get to it eventually.
—
Reply to this email directly or view it on GitHub
https://github.com/github/hub/issues/431#issuecomment-116861539.

--
Sterling Camden
Software Engineer
502 Emerson Street | Palo Alto, CA 94301
303.520.2968 |<EMAIL_ADDRESS>

@mislav Sounds like a good solution. Any news? :)

@joaosa No code yet to solve this issue, sorry. I accept contributions. Although, I'm not sure in a scenario where you belong to multiple teams, which team should be picked as a default team to create the repo in?

@mislav at least being able to set a team would be huge regardless of the default, but maybe for default team you could ask and store it in a config file or something?

@scamden Agreed. I think being able to set a team explicitly is more important feature than configuring a default team.

@mislav What do you think of my earlier comment?

@mislav Sorry to bother, but any news on this one? Should something be changed in hub or this should be taken care of in the GitHub API? Thanks!

I think this still stands. You don't need to choose a team when creating an organisation repo on GitHub.com. Why should we do this in hub through the API then?

@hkdobrev From what I can see while inspecting our API validation, it looks like a user can only create a repository without a team if they have adminable rights on the org. Any other users will have to supply team_id.
Does this make sense?

@mislav Fair enough. But I can do that on the web for my organisations as well as any other core dev in the team. Why not be able to do it via hub?

Have you tried it recently? The API has changed since you reported this in 2013.

@mislav You are indeed correct! This is now possible in an organisation where you have admin rights. Great!


Unable to use Collection suffix for table name

I couldn't find this limitation documented anywhere, apologies if I've overlooked something obvious.
I have a Book table and a BookCollection table, with an FK from BookCollection.ID <-> Book.CollectionId.
When getting a list of books ($bookCollection->getBooks()) , propel attempts to load my BookCollection class, assuming it's the class for a "collection of Books". This breaks with an error Uncaught Propel\Runtime\Exception\BadMethodCallException: Call to undefined method: "setModel" since my collection class doesn't implement setModel().
I added a check to explicitly not consider classes that implement ActiveRecordInterface as "collection of object" classes.
Originally I was going to check if the $collectionClass is a subclass of \Propel\Runtime\Collection, but I suppose someone could implement a collection class that isn't a subclass of \Propel\Runtime\Collection. It seemed less likely that someone would implement a collection class that also implements ActiveRecordInterface.

Looks good to me.

Can you please rebase so the tests are green? Then we can merge.

Can you please rebase so the tests are green? Then we can merge.


Push built image as docker v2s2

CLOUDBLD-8136
By default, the podman build command uses the oci format. The podman
push command defaults to the format of the built image.
Explicitly specify v2s2, because some parts of the RH container pipeline
do not support oci yet.
Signed-off-by: Adam Cmiel<EMAIL_ADDRESS>Maintainers will complete the following section

[x] Commit messages are descriptive enough
[x] Code coverage from testing does not decrease and new code is covered
n/a Python type annotations added to new code
n/a JSON/YAML configuration changes are updated in the relevant schema
n/a Changes to metadata also update the documentation for the metadata
n/a Pull request has a link to an osbs-docs PR for user documentation updates
n/a New feature can be disabled from a configuration file

should we document this somewhere that images are built as oci and pushed as v2s2?

should we document this somewhere that images are built as oci and pushed as v2s2?

Added to docstrings at least, I don't think there is a good place for this info in osbs.readthedocs yet
@rcerven I also updated the commands to follow the "options-first" format. It gets a bit awkward when adding options dynamically (insert(-1, option)), LMK what you think

should we document this somewhere that images are built as oci and pushed as v2s2?

Added to docstrings at least, I don't think there is a good place for this info in osbs.readthedocs yet
@rcerven I also updated the commands to follow the "options-first" format. It gets a bit awkward when adding options dynamically (insert(-1, option)), LMK what you think

well that podman pushes default oci image is podman implementation, for our users nothing changes, we always create v2s2


Write a guide on deploying to Digital Ocean

Unless someone else steps up we're likely not going to do this in the near term. Happy to re-open if it comes up again or someone from the community wants to contribute.


Add support for VMware hardware version 11.

VMware vSphere 6 introduces a new virtual hardware version - 11.

@gmcculloug Please review.

:+1:


Bypass for deleting an in-use cloud credential not working

When trying to delete an old credential that is used by an existing node template, I'm blocked from doing so, but when I want to use the bypass, it does not work. I hold the command key when clicking delete, but the same error is returned. I also tried closing the dialog box and holding command when deleting from the credentials list and this does indeed bypass the error, however nothing happens and the credential is not deleted.
It would make sense to block the deletion of the credential because it is indeed still in use. However, I am given a tip on how to bypass the error, which then does not work. I'd expect it to just block the action or have a bypass that does work. It is also a bit confusing how the bypass works. Can I hold the command button while in the error's dialog box or when deleting from the list?
Rancher Server Setup

Rancher version: 2.6 RC2
Installation option: Helm chart, on a single node k3s cluster
Proxy/Cert Details: LetsEncrypt

@Sheldonwl , thank you for reporting this issue.
There may be some misunderstanding what "bypass" is referring to. The intention here is not to bypass actual error and force deletion, but to bypass the confirmation to allow for more streamlined UI if the user wants to avoid confirmations when deleting objects.
Now, I see that if I Cmd + click "Delete" on a cloud credential that is in use, seemingly nothing is happening in the UI. However in Console I see it actually calls backend to delete cloud credential and it returns the same error - it's just there is nothing in the UI that handles this error.

So, this looks like UI bug/enhancement and I'm going to transfer this issue to rancher/dashboard for UI team to look into.


revert index tree twistie changes

This reverts commits a8dd7f60a6204353e8d6969c8bc39f0476d46e2a and 5dab5012d8e1cada5f1c9fffdc6e2525e44745ff

Had to revert this back since it completely broke the Explorer's rename: https://github.com/microsoft/vscode/pull/201889


Project that runs in VS Mac doesn't run in VS Code on macOS

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

VS Code Version: Version: 1.84.2
Commit: 1a5daa3a0231a0fbba4f14db7ec463cf99d7768e
Date: 2023-11-09T10:52:57.054Z
Electron: 25.9.2
ElectronBuildId: 24603566
Chromium: 114.0.5735.289
Node.js: 18.15.0
V8: <IP_ADDRESS>-electron.0
OS: Darwin arm64 22.6.0
OS Version: macOS 13.6 (22G120)

I develop on macOS and deploy to Windows as a Windows service. I'm using the C# Dev Kit.
Steps to Reproduce:

Add this to .csproj on macOS: <DefaultAppHostRuntimeIdentifier>win-x64</DefaultAppHostRuntimeIdentifier>
Debug project and notice that it doesn't start and presents this error:

The target process exited without raising a CoreCLR started event. Ensure that the target process is configured to use .NET Core. This may be expected if the target process did not run on .NET Core.
The program '[29491] AlumniAdmissionsReport.exe' has exited with code 1 (0x1).

Please file this against the C# dev kit


Update time to launch EKS clusters

Issue #, if available: None
Description of changes:
As per https://aws.amazon.com/about-aws/whats-new/2021/03/amazon-eks-reduces-cluster-creation-time-40-percent/

Posted On: Mar 19, 2021
Amazon Elastic Kubernetes Service (EKS) has reduced control plane creation time by 40%, enabling you to create a new EKS cluster control plane in 9 minutes or less, on average.

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Actually this doesn't seem to work, in my test in Ireland it still took more than 15min
Admin:~/environment $ eksctl create cluster -f eksworkshop.yaml
2021-04-20 10:38:48 [ℹ]  eksctl version 0.44.0
2021-04-20 10:38:48 [ℹ]  using region eu-west-1
2021-04-20 10:38:48 [ℹ]  subnets for eu-west-1a - public:<IP_ADDRESS>/19 private:<IP_ADDRESS>/19
2021-04-20 10:38:48 [ℹ]  subnets for eu-west-1b - public:<IP_ADDRESS>/19 private:<IP_ADDRESS>/19
2021-04-20 10:38:48 [ℹ]  subnets for eu-west-1c - public:<IP_ADDRESS>/19 private:<IP_ADDRESS>/19
2021-04-20 10:38:48 [ℹ]  using Kubernetes version 1.17
2021-04-20 10:38:48 [ℹ]  creating EKS cluster "eksworkshop-eksctl" in "eu-west-1" region with managed nodes
2021-04-20 10:38:48 [ℹ]  1 nodegroup (nodegroup) was included (based on the include/exclude rules)
2021-04-20 10:38:48 [ℹ]  will create a CloudFormation stack for cluster itself and 0 nodegroup stack(s)
2021-04-20 10:38:48 [ℹ]  will create a CloudFormation stack for cluster itself and 1 managed nodegroup stack(s)
2021-04-20 10:38:48 [ℹ]  if you encounter any issues, check CloudFormation console or try 'eksctl utils describe-stacks --region=eu-west-1 --cluster=eksworkshop-eksctl'
2021-04-20 10:38:48 [ℹ]  CloudWatch logging will not be enabled for cluster "eksworkshop-eksctl" in "eu-west-1"
2021-04-20 10:38:48 [ℹ]  you can enable it with 'eksctl utils update-cluster-logging --enable-types={SPECIFY-YOUR-LOG-TYPES-HERE (e.g. all)} --region=eu-west-1 --cluster=eksworkshop-eksctl'
2021-04-20 10:38:48 [ℹ]  Kubernetes API endpoint access will use default of {publicAccess=true, privateAccess=false} for cluster "eksworkshop-eksctl" in "eu-west-1"
2021-04-20 10:38:48 [ℹ]  2 sequential tasks: { create cluster control plane "eksworkshop-eksctl", 2 sequential sub-tasks: { wait for control plane to become ready, create managed nodegroup "nodegroup" } }
2021-04-20 10:38:48 [ℹ]  building cluster stack "eksctl-eksworkshop-eksctl-cluster"
2021-04-20 10:38:49 [ℹ]  deploying stack "eksctl-eksworkshop-eksctl-cluster"
2021-04-20 10:39:19 [ℹ]  waiting for CloudFormation stack "eksctl-eksworkshop-eksctl-cluster"
2021-04-20 10:39:49 [ℹ]  waiting for CloudFormation stack "eksctl-eksworkshop-eksctl-cluster"
2021-04-20 10:40:49 [ℹ]  waiting for CloudFormation stack "eksctl-eksworkshop-eksctl-cluster"
2021-04-20 10:41:49 [ℹ]  waiting for CloudFormation stack "eksctl-eksworkshop-eksctl-cluster"
2021-04-20 10:42:49 [ℹ]  waiting for CloudFormation stack "eksctl-eksworkshop-eksctl-cluster"
2021-04-20 10:43:49 [ℹ]  waiting for CloudFormation stack "eksctl-eksworkshop-eksctl-cluster"
2021-04-20 10:44:49 [ℹ]  waiting for CloudFormation stack "eksctl-eksworkshop-eksctl-cluster"
2021-04-20 10:45:49 [ℹ]  waiting for CloudFormation stack "eksctl-eksworkshop-eksctl-cluster"
2021-04-20 10:46:49 [ℹ]  waiting for CloudFormation stack "eksctl-eksworkshop-eksctl-cluster"
2021-04-20 10:47:49 [ℹ]  waiting for CloudFormation stack "eksctl-eksworkshop-eksctl-cluster"
2021-04-20 10:48:49 [ℹ]  waiting for CloudFormation stack "eksctl-eksworkshop-eksctl-cluster"
2021-04-20 10:49:49 [ℹ]  waiting for CloudFormation stack "eksctl-eksworkshop-eksctl-cluster"
2021-04-20 10:50:49 [ℹ]  waiting for CloudFormation stack "eksctl-eksworkshop-eksctl-cluster"
2021-04-20 10:51:49 [ℹ]  waiting for CloudFormation stack "eksctl-eksworkshop-eksctl-cluster"
2021-04-20 10:51:50 [ℹ]  building managed nodegroup stack "eksctl-eksworkshop-eksctl-nodegroup-nodegroup"
2021-04-20 10:51:50 [ℹ]  deploying stack "eksctl-eksworkshop-eksctl-nodegroup-nodegroup"
2021-04-20 10:51:50 [ℹ]  waiting for CloudFormation stack "eksctl-eksworkshop-eksctl-nodegroup-nodegroup"
2021-04-20 10:52:06 [ℹ]  waiting for CloudFormation stack "eksctl-eksworkshop-eksctl-nodegroup-nodegroup"
2021-04-20 10:52:23 [ℹ]  waiting for CloudFormation stack "eksctl-eksworkshop-eksctl-nodegroup-nodegroup"
2021-04-20 10:52:43 [ℹ]  waiting for CloudFormation stack "eksctl-eksworkshop-eksctl-nodegroup-nodegroup"
2021-04-20 10:53:00 [ℹ]  waiting for CloudFormation stack "eksctl-eksworkshop-eksctl-nodegroup-nodegroup"
2021-04-20 10:53:20 [ℹ]  waiting for CloudFormation stack "eksctl-eksworkshop-eksctl-nodegroup-nodegroup"
2021-04-20 10:53:39 [ℹ]  waiting for CloudFormation stack "eksctl-eksworkshop-eksctl-nodegroup-nodegroup"
2021-04-20 10:53:58 [ℹ]  waiting for CloudFormation stack "eksctl-eksworkshop-eksctl-nodegroup-nodegroup"
2021-04-20 10:54:14 [ℹ]  waiting for CloudFormation stack "eksctl-eksworkshop-eksctl-nodegroup-nodegroup"
2021-04-20 10:54:32 [ℹ]  waiting for CloudFormation stack "eksctl-eksworkshop-eksctl-nodegroup-nodegroup"
2021-04-20 10:54:49 [ℹ]  waiting for CloudFormation stack "eksctl-eksworkshop-eksctl-nodegroup-nodegroup"
2021-04-20 10:55:05 [ℹ]  waiting for CloudFormation stack "eksctl-eksworkshop-eksctl-nodegroup-nodegroup"
2021-04-20 10:55:23 [ℹ]  waiting for CloudFormation stack "eksctl-eksworkshop-eksctl-nodegroup-nodegroup"
2021-04-20 10:55:39 [ℹ]  waiting for CloudFormation stack "eksctl-eksworkshop-eksctl-nodegroup-nodegroup"
2021-04-20 10:55:55 [ℹ]  waiting for CloudFormation stack "eksctl-eksworkshop-eksctl-nodegroup-nodegroup"
2021-04-20 10:56:13 [ℹ]  waiting for CloudFormation stack "eksctl-eksworkshop-eksctl-nodegroup-nodegroup"
2021-04-20 10:56:13 [ℹ]  waiting for the control plane availability...
2021-04-20 10:56:13 [✔]  saved kubeconfig as "/home/ec2-user/.kube/config"
2021-04-20 10:56:13 [ℹ]  no tasks
2021-04-20 10:56:13 [✔]  all EKS cluster resources for "eksworkshop-eksctl" have been created
2021-04-20 10:56:13 [ℹ]  nodegroup "nodegroup" has 3 node(s)
2021-04-20 10:56:13 [ℹ]  node "ip-192-168-41-94.eu-west-1.compute.internal" is ready
2021-04-20 10:56:13 [ℹ]  node "ip-192-168-5-183.eu-west-1.compute.internal" is ready
2021-04-20 10:56:13 [ℹ]  node "ip-192-168-91-25.eu-west-1.compute.internal" is ready
2021-04-20 10:56:13 [ℹ]  waiting for at least 3 node(s) to become ready in "nodegroup"
2021-04-20 10:56:13 [ℹ]  nodegroup "nodegroup" has 3 node(s)
2021-04-20 10:56:13 [ℹ]  node "ip-192-168-41-94.eu-west-1.compute.internal" is ready
2021-04-20 10:56:13 [ℹ]  node "ip-192-168-5-183.eu-west-1.compute.internal" is ready
2021-04-20 10:56:13 [ℹ]  node "ip-192-168-91-25.eu-west-1.compute.internal" is ready
2021-04-20 10:56:14 [ℹ]  kubectl command should work with "/home/ec2-user/.kube/config", try 'kubectl get nodes'
2021-04-20 10:56:14 [✔]  EKS cluster "eksworkshop-eksctl" in "eu-west-1" region is ready


Make toolbar responsive for Explorer

Improve the behavior of the Explorer toolbar when the viewport width is narrow. Currently, the entire right toolbar moves below the left toolbar if there isn't enough space.
Figma

Keeping this ticket open to re-implement post launch

Will be addressed as part of #1034


Add Ironforged V1 by NQJ

Project name: Ironforged V1
Project URL: https://nqjasmine.itch.io/ironforged-v1

Why it's awesome

First page describes overall changes to make when converting Ironsworn assets & situations to Starforged rules
Additional pages are printable Ironsworn asset cards with the given tweaks.  I haven't checked recently, but I think it only contains the assets with changes, and blank spots where unchanged assets were in the original Cards PDF.

I've seen two reddit posts this week asking about using Ironsworn assets with Starforged.

https://www.reddit.com/r/Ironsworn/comments/1h41e72/more_assets/
https://www.reddit.com/r/Ironsworn/comments/1h4uiit/can_i_use_ironsworn_assetswithout_changes_for/

Thanks!


feat(otelx): add API key attribute keys

Adds attribute keys for both ProjectAPIKeys and WorkspaceAPIKeys.

Turns out, it is not as easy everywhere to know what type an API key is of.

Is this putting actual secrets in attributes?


PEAR-1732 - Repository and Projects app: clear local filters on exit/reentry

Description
Checklist

[x] Added proper unit tests
[x] Left proper TODO messages for any remaining tasks
[x] Scanned for web accessibility with aXe, and mitigated or documented
flagged issues

Screenshots/Screen Recordings (if Appropriate)

works as expected 👍


backoff: Make duration bounds customizable

This will let us have some backoff loops that back off more patiently than others, e.g. because their work is happening in the background and isn't expected to be something the user is already waiting for.
In particular I plan to use this for backing off the fetch of server emoji data, for #669.

Ah I reviewed this before I noticed it was assigned to @PIG208. LGTM, but I'd be happy to wait for @PIG208's review if that's desired or @PIG208 if you've started yours already. :)

Sorry for the delay! Posted a comment. This LGTM overall.

Thanks for the reviews! Merging, with that tweak.


feat: added update-status handler

https://github.com/canonical/kfp-operators/issues/188

Summary of changes:
- Added update-status handler.

Needs conflict resolution. Closing.


Fix static_assert (C++17 -> C++11) in net.cc

Based on this documentation the following static_assert implementation:
static_assert ( bool_constexpr , message ) 		(since C++11)

should be used in Pistache to be compatible with C++11/14.

Codecov Report

Merging #729 into master will increase coverage by 0.01%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master     #729      +/-   ##
==========================================
+ Coverage    67.6%   67.62%   +0.01%
==========================================
  Files          51       51
  Lines        6665     6665
==========================================
+ Hits         4506     4507       +1
+ Misses       2159     2158       -1

Impacted Files
Coverage Δ

src/common/net.cc
89.9% <ø> (ø)
:arrow_up:

include/pistache/async.h
89.25% <0%> (+0.25%)
:arrow_up:

Continue to review full report at Codecov.

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


Convert to mediapipe.framework.formats.landmark_pb2.NormalizedLandmark

I would liket to use mediapipe coordinates as labels for some other task,
how can i convert array or list or dict storing these coordinates to mediapipe.framework.formats.landmark_pb2.NormalizedLandmark, so that i could use the native draw function ?

Hi @nisarnabeel, Store the iterated values in a list. Then use this snippet below,
from mediapipe.framework.formats import landmark_pb2
reconstructed = landmark_pb2.NormalizedLandmarkList(extracted_points_list)

Attaching relevant threads for your reference. Thank you!

Hi @kuaashish , quite new on mediapipe,
thanks for the swift response
in the end i used (reconstructed.landmark.add in a loop) to store values which were not of the type landmark_pb2.NormalizedLandmark.
i tried the above method as well, it works fine :)
thank you

Hi @nisarnabeel,
Thanks for the confirmation! Could we move this issue to the close status as it has been resolved.
Thank you!

sure thanks :)


How can I upgrade my Config from V1 to V2 ?

Describe the issue:
I have already run python3 -m pip install --upgrade nni, upgrade nni from 2.4 to 2.5 .
However, though It shows that my version is 2.5 when I run nnictl --version, it seems that my Config version is only V1 because when I use
trainingService:
  platform: local
  useActiveGpu: false

and run nnictl create --config search.yml -p 8080, it says ERROR: Config V1 validation failed: SchemaWrongKeyError("Wrong key 'trainingService' in .......
Environment:

NNI version: 2.5
Training service (local|remote|pai|aml|etc): local
Client OS: Ubuntu
Server OS (for remote mode only):
Python version: 3.8.11
PyTorch version: 1.7.1
Is conda/virtualenv/venv used?: conda
Is running in Docker?: no

my search.yml is as follows:
authorName: test
experimentName: test_search
trialConcurrency: 6
maxExecDuration: 24h
maxTrialNum: 100
trainingServicePlatform: local
searchSpacePath: search_space.json
useAnnotation: false

localConfig:
  useActiveGpu: true
  gpuIndices: 0,1
tuner:
  builtinTunerName: TPE
  classArgs:
    optimize_mode: maximize

trial:
  command: python test_nni.py
  codeDir: .
  gpuNum: 1

trainingService:
  platform: local
  useActiveGpu: false

I wanna know how can I upgrade Config to V2, or how can I run multiple trials on one GPU in Config V1?
Thanks a lot!

You are mixing two schemas. The reference of latest format is here.
 The reference of latest format is here.
Your config should look like this in v2:
experimentName: test_search
trialConcurrency: 6
maxExperimentDuration: 24h
maxTrialNumber: 100
searchSpaceFile: search_space.json

tuner:
  name: TPE
  classArgs:
    optimize_mode: maximize

trialCommand: python test_nni.py
trialGpuNumber: 1

trainingService:
  platform: local
  useActiveGpu: false
  gpuIndices: 0,1

Now I'm more clear of the concept Config. The version depends on the code !
Thanks a lot :) :+1:


swapped cstor and jiva in bootstrapper

What this PR does / why we need it:
-> swapped cstor and jiva in bootstrapper

Ci.yaml
- include: setup-kubernetes.yml
- include: setup-stern.yml
- include: setup-openebs.yml
- include: setup-disks.yml
- include: create-cStorPool.yml
- include: cstor-run-tests.yml
- include: jiva-run-tests.yml
- include: delete-cStorPool.yml
- include: playbooks/deprovision-cvr/deprovision-cvr.yml
- include: delete-disks.yml
- include: cleanup-openebs.yml


Block Mix

What website(s) would this filter apply to?
Youtube
What content should be blocked?
 I have a filter for that, but it doesn't quite work as it should. He leaves blank (screenshot 2) spaces for mixes. It works only in English and Polish.

Screen 1

Screen 2

What options should be offered?
No response
Did you write a custom uBlock filter already?
www.youtube.com##:xpath(//ytd-two-column-browse-results-renderer[starts-with(@page-subtype,"home")]//a[starts-with(@title,"Mix - ")]):nth-ancestor(7)
www.youtube.com##:xpath(//ytd-two-column-browse-results-renderer[starts-with(@page-subtype,"home")]//a[starts-with(@title,"YouTube Mix")]):nth-ancestor(7)
www.youtube.com##:xpath(//ytd-two-column-browse-results-renderer[starts-with(@page-subtype,"home")]//a[starts-with(@title,"Mój YouTube Mix")]):nth-ancestor(7)
www.youtube.com##:xpath(//ytd-two-column-browse-results-renderer[starts-with(@page-subtype,"home")]//a[starts-with(@title,"Mój Mix")]):nth-ancestor(7)
www.youtube.com##:xpath(//ytd-two-column-browse-results-renderer[starts-with(@page-subtype,"home")]//a[starts-with(@title,"My Mix")]):nth-ancestor(7)
youtube.com###dismissable[class*="video-renderer"]:has([id^="video-title"]:has-text(/Mix/i))
youtube.com##ytd-playlist-renderer:has-text(/^Mix/)
youtube.com##ytd-compact-radio-renderer:has-text(/^Mix/)
youtube.com###dismissable:has-text(/^Mix/)
youtube.com###dismissable.style-scope ytd-compact-radio-renderer:has-text(/^Mix/)

Additional notes
No response

Could you please try the following filters:
www.youtube.com##ytd-browse ytd-rich-item-renderer:has(#video-title-link[href*="&start_radio=1"])
www.youtube.com##ytd-search ytd-radio-renderer
www.youtube.com##ytd-watch-next-secondary-results-renderer ytd-compact-radio-renderer
www.youtube.com##ytd-player div.videowall-endscreen a[data-is-list=true]

They block mixes, respectively in:

the homepage
the search results
the player sidebar recommendations
the player endscreen

As for the layout issue, I'm afraid there is not much we can do here, and it happens with my other youtube filters. While the subscription page is a simple item list that the browser wraps into rows, the homepage code inserts ytd-rich-grid-row elements wrapping a set number of items. Someone decided not to trust the browser to do such a simple job but, because they are so well-paid, we can only assume they had good reasons, right?


Username/Password Authentication: support to configure default users

Configure default username/password:
    %% Authentication and Authorization
    {access, [
        %% Authetication. Anonymous Default
        {auth, [
            %% Authentication with username, password
            {username, [{user1, "pass1"}, {user2, "pass2"}]},
            ...

Fixed in 0.15.0 release


Is the bold command patch really necessary?

So, currently, the bold command patch prevents a user from running the bold command inside of a heading tag. A comment in that patch seems to be referencing this example.
The problematic bit in this patch happens when a user first makes text bold, and then decides to make it a heading. In this case, you end up with
Some bolded heading
, and then the user isn't able to "de-bold" the heading.
As an experiment, I made a branch that removed this command patch and...everything seemed to function properly. While I still wasn't able to bold text inside a heading, I was able to remove the bold tag from a heading like this:
Some bolded heading
. Also, I didn't see any bad markup in Chrome, Safari or Firefox.
Any guidance on this would be greatly appreciated. Is there something that I'm missing here?

@csinchok Does the changes in 1.2.0 allow you to override the behaviour now?

I'm closing this because I think we've resolved the issue


Switched index in loading dataset?

Hello, I noticed that within your implementation of pix2pix, Datasets will return image in form of like this
https://github.com/eriklindernoren/PyTorch-GAN/blob/fd9f0713eadd03b09e4fa0e828d5b7b6375e76bb/implementations/pix2pix/datasets.py#L33
But when reading it again in training loop, it was written like
https://github.com/eriklindernoren/PyTorch-GAN/blob/fd9f0713eadd03b09e4fa0e828d5b7b6375e76bb/implementations/pix2pix/pix2pix.py#L127-L128
This happened multiple times within pix2pix.py when loading the image. Is this switching intentional?

it is normal as the facades datasets is transfering B to A. Or You can say that imgB = input , and imgA = output


Use console_engine for terminal control

I discovered console_engine today, which always a rich control of the terminal and how text / graphics are displayed:
https://crates.io/crates/console_engine
This would allow us to create complex images by using absolute / relative positions instead of printing spacers. Here is an example gif of what is possible (runs on macOS, Windows, Linux, haven't tried netBSD but should work on all UNIX terminals):

We'll use tui-rs


Improve class structure for Labels type

The current implementation of labels has no implementation of GitLabel defined in the abstract classes, which would be consistent with what is done for GitUser, GitProject etc. This is leading to inconsistent typing in the library where we have the following function signatures within the codebase:
abstract.py
def get_issue_labels(self, issue_id: int) -> List[Any]
github/project.py
def get_issue_labels(self, issue_id: int) -> List[GithubLabel]
gitlab/project.py
def get_issue_labels(self, issue_id: int) -> List[str]
Would be good to make this consistent and inherit from a base class of GitLabel.
@lachmanfrantisek

We need to look at it.
@mfocko You may probably now if this was fixed by your cllas restracture?

@mfocko You may probably now if this was fixed by your cllas restracture?

nope, it wasn't
what do we expect? just name and colour properties? or also methods and/or setters?

The following properties would be nice:

name
colour
description for GitHub/GitLab

what about getting issues/PRs by label? and setters?
looking at API, Pagure has "labels" just as strings that don't seem to be organized like github/gitlab does

what about getting issues/PRs by label? and setters?

:+1:

looking at API, Pagure has "labels" just as strings that don't seem to be organized like github/gitlab does

OK, let's have an abstract label class with the name and Git* label classes with the other two properties.


Bad encoding for credentials with SQL Server connector since Steeltoe 2.5.0

Describe the bug
Deploying an app using Cloud Foundry and MASB as service broker for Azure SQL database, the connection will not be established when the password contains special characters like + character.
Steps to reproduce
Steps to reproduce the behavior:

Deploy an app on Cloud Foundry using an Azure SQL database (provided by MASB).
Unbind / bind the app on Azure SQL database until you get a password with a + in it.
Observe that app can't connect to Azure SQL database in your app log.

Expected behavior
The connection should work properly even if there is a special character in the password.
Environment :

Steeltoe Version: reproduced on 2.5.x and 3.x.x
Platform: Cloud Foundry using MASB
.NET Version: .NET Core 3.1

Additional context or links
Here what the VCAP_SERVICES looks like:
System-Provided:
{
 "VCAP_SERVICES": {
  "azure-sqldb": [
   {
    "binding_name": null,
    "credentials": {
     "databaseLogin": "fakeUsername",
     "databaseLoginPassword": "fakePasswordWith+",
     "hostname": "custom-server.database.windows.net",
     "jdbcUrl": "jdbc:sqlserver://custom-server.database.windows.net:1433;database=fakeDbName;user=fakeUsername;password=fakePasswordWith+;Encrypt=true;TrustServerCertificate=false;HostNameInCertificate=*.database.windows.net;loginTimeout=30;",
     "jdbcUrlForAuditingEnabled": "jdbc:sqlserver://custom-server.database.secure.windows.net:1433;database=fakeDbName;user=fakeUsername;password=fakePasswordWith+;Encrypt=true;TrustServerCertificate=false;HostNameInCertificate=*.database.secure.windows.net;loginTimeout=30;",
     "name": "fakeDbName",
     "password": "fakePasswordWith+",
     "port": 1433,
     "sqlServerFullyQualifiedDomainName": "custom-server.database.windows.net",
     "sqlServerName": "custom-server",
     "sqldbName": "fakeDbName",
     "uri": "mssql://fakeUsername:fakePasswordWith%2B@custom-server.database.windows.net:1433/fakeDbName?encrypt=true\u0026TrustServerCertificate=false\u0026HostNameInCertificate=%2A.database.windows.net",
     "username": "fakeUsername"
    },
    "instance_name": "fakeServiceInstanceName",
    "label": "azure-sqldb",
    "name": "fakeServiceInstanceName",
    "plan": "StandardS0",
    "provider": null,
    "syslog_drain_url": null,
    "tags": [],
    "volume_mounts": []
   }
  ]
 }
}

I think that #367 introduced that bug.
I don't know what is the best solution. Maybe it makes sense that username/password should be always return using WebUtility.UrlDecode in UriServiceInfo and that change shouldn't be reverted.
In the SqlServerServiceInfoFactory, if there is a username and password (like the MASB provides), it doesn't use the uri parameter. Maybe it should use the uri parameter first (SqlServerServiceInfo constructor with only url parameter) instead of username/password parameters.


Blockquotes appear cut on mobile

Formerly this post was shown on mobile like this:

I've then removed the negative margin setting, which looks fine on desktop, but not on mobile.

Hi @oblitum, it may need a little bit more positive left margin if that is what you wanted to achieve for quick fix. Another solution is to put left and right margins on the .post to have more space for the entire post. Apology for I didn't do enough for mobile.


pip install ./gridencoder build fails

I was able to build all requirements in install_ext.sh except ./gridencoder
I am using a docker image 'ngc-pytorch-kernel:22.04-py3-202207261342'
I reinstalled torch with pip install torch torchvision torchaudio --extra-index-url https://download.pytorch.org/whl/cu116
But it seems that this is not the problem
Did anyone have a similar issue?
Looking in indexes: https://pypi.org/simple, https://pypi.ngc.nvidia.com
Processing ./gridencoder
  Preparing metadata (setup.py) ... done
Building wheels for collected packages: gridencoder
  Building wheel for gridencoder (setup.py) ... error
  error: subprocess-exited-with-error

  × python setup.py bdist_wheel did not run successfully.
  │ exit code: 1
  ╰─> [495 lines of output]
      running bdist_wheel
      running build
      running build_ext
      building '_gridencoder' extension
      Emitting ninja build file /source/sihun/stable-dreamfusion/gridencoder/build/temp.linux-x86_64-3.8/build.ninja...
      Compiling objects...

      Traceback (most recent call last):
        File "/opt/conda/lib/python3.8/site-packages/torch/utils/cpp_extension.py", line 1900, in _run_ninja_build
          subprocess.run(
        File "/opt/conda/lib/python3.8/subprocess.py", line 516, in run
          raise CalledProcessError(retcode, process.args,
      subprocess.CalledProcessError: Command '['ninja', '-v']' returned non-zero exit status 1.

      The above exception was the direct cause of the following exception:

      Traceback (most recent call last):
        File "<string>", line 2, in <module>
        File "<pip-setuptools-caller>", line 34, in <module>
        File "/source/sihun/stable-dreamfusion/gridencoder/setup.py", line 32, in <module>
          setup(
        File "/opt/conda/lib/python3.8/site-packages/setuptools/__init__.py", line 153, in setup
          return distutils.core.setup(**attrs)
        File "/opt/conda/lib/python3.8/distutils/core.py", line 148, in setup
          dist.run_commands()
        File "/opt/conda/lib/python3.8/distutils/dist.py", line 966, in run_commands
          self.run_command(cmd)
        File "/opt/conda/lib/python3.8/distutils/dist.py", line 985, in run_command
          cmd_obj.run()
        File "/opt/conda/lib/python3.8/site-packages/wheel/bdist_wheel.py", line 299, in run
          self.run_command('build')
        File "/opt/conda/lib/python3.8/distutils/cmd.py", line 313, in run_command
          self.distribution.run_command(command)
        File "/opt/conda/lib/python3.8/distutils/dist.py", line 985, in run_command
          cmd_obj.run()
        File "/opt/conda/lib/python3.8/distutils/command/build.py", line 135, in run
          self.run_command(cmd_name)
        File "/opt/conda/lib/python3.8/distutils/cmd.py", line 313, in run_command
          self.distribution.run_command(command)
        File "/opt/conda/lib/python3.8/distutils/dist.py", line 985, in run_command
          cmd_obj.run()
        File "/opt/conda/lib/python3.8/site-packages/setuptools/command/build_ext.py", line 79, in run
          _build_ext.run(self)
        File "/opt/conda/lib/python3.8/site-packages/Cython/Distutils/old_build_ext.py", line 186, in run
          _build_ext.build_ext.run(self)
        File "/opt/conda/lib/python3.8/distutils/command/build_ext.py", line 340, in run
          self.build_extensions()
        File "/opt/conda/lib/python3.8/site-packages/torch/utils/cpp_extension.py", line 843, in build_extensions
          build_ext.build_extensions(self)
        File "/opt/conda/lib/python3.8/site-packages/Cython/Distutils/old_build_ext.py", line 195, in build_extensions
          _build_ext.build_ext.build_extensions(self)
        File "/opt/conda/lib/python3.8/distutils/command/build_ext.py", line 449, in build_extensions
          self._build_extensions_serial()
        File "/opt/conda/lib/python3.8/distutils/command/build_ext.py", line 474, in _build_extensions_serial
          self.build_extension(ext)
        File "/opt/conda/lib/python3.8/site-packages/setuptools/command/build_ext.py", line 202, in build_extension
          _build_ext.build_extension(self, ext)
        File "/opt/conda/lib/python3.8/distutils/command/build_ext.py", line 528, in build_extension
          objects = self.compiler.compile(sources,
        File "/opt/conda/lib/python3.8/site-packages/torch/utils/cpp_extension.py", line 658, in unix_wrap_ninja_compile
          _write_ninja_file_and_compile_objects(
        File "/opt/conda/lib/python3.8/site-packages/torch/utils/cpp_extension.py", line 1573, in _write_ninja_file_and_compile_objects
          _run_ninja_build(
        File "/opt/conda/lib/python3.8/site-packages/torch/utils/cpp_extension.py", line 1916, in _run_ninja_build
          raise RuntimeError(message) from e
      RuntimeError: Error compiling objects for extension
      [end of output]

  note: This error originates from a subprocess, and is likely not a problem with pip.
  ERROR: Failed building wheel for gridencoder
  Running setup.py clean for gridencoder
Failed to build gridencoder
Installing collected packages: gridencoder
  Running setup.py install for gridencoder ... error
  error: subprocess-exited-with-error

  × Running setup.py install for gridencoder did not run successfully.
  │ exit code: 1
  ╰─> [507 lines of output]
      running install
      /opt/conda/lib/python3.8/site-packages/setuptools/command/install.py:34: SetuptoolsDeprecationWarning: setup.py install is deprecated. Use build and pip and other standards-based tools.
        warnings.warn(
      running build
      running build_ext
      building '_gridencoder' extension
      creating /source/sihun/stable-dreamfusion/gridencoder/build
      creating /source/sihun/stable-dreamfusion/gridencoder/build/temp.linux-x86_64-3.8
      creating /source/sihun/stable-dreamfusion/gridencoder/build/temp.linux-x86_64-3.8/source
      creating /source/sihun/stable-dreamfusion/gridencoder/build/temp.linux-x86_64-3.8/source/sihun
      creating /source/sihun/stable-dreamfusion/gridencoder/build/temp.linux-x86_64-3.8/source/sihun/stable-dreamfusion
      creating /source/sihun/stable-dreamfusion/gridencoder/build/temp.linux-x86_64-3.8/source/sihun/stable-dreamfusion/gridencoder
      creating /source/sihun/stable-dreamfusion/gridencoder/build/temp.linux-x86_64-3.8/source/sihun/stable-dreamfusion/gridencoder/src
      Emitting ninja build file /source/sihun/stable-dreamfusion/gridencoder/build/temp.linux-x86_64-3.8/build.ninja...
      Compiling objects...

      Traceback (most recent call last):
        File "/opt/conda/lib/python3.8/site-packages/torch/utils/cpp_extension.py", line 1900, in _run_ninja_build
          subprocess.run(
        File "/opt/conda/lib/python3.8/subprocess.py", line 516, in run
          raise CalledProcessError(retcode, process.args,
      subprocess.CalledProcessError: Command '['ninja', '-v']' returned non-zero exit status 1.

      The above exception was the direct cause of the following exception:

      Traceback (most recent call last):
        File "<string>", line 2, in <module>
        File "<pip-setuptools-caller>", line 34, in <module>
        File "/source/sihun/stable-dreamfusion/gridencoder/setup.py", line 32, in <module>
          setup(
        File "/opt/conda/lib/python3.8/site-packages/setuptools/__init__.py", line 153, in setup
          return distutils.core.setup(**attrs)
        File "/opt/conda/lib/python3.8/distutils/core.py", line 148, in setup
          dist.run_commands()
        File "/opt/conda/lib/python3.8/distutils/dist.py", line 966, in run_commands
          self.run_command(cmd)
        File "/opt/conda/lib/python3.8/distutils/dist.py", line 985, in run_command
          cmd_obj.run()
        File "/opt/conda/lib/python3.8/site-packages/setuptools/command/install.py", line 68, in run
          return orig.install.run(self)
        File "/opt/conda/lib/python3.8/distutils/command/install.py", line 545, in run
          self.run_command('build')
        File "/opt/conda/lib/python3.8/distutils/cmd.py", line 313, in run_command
          self.distribution.run_command(command)
        File "/opt/conda/lib/python3.8/distutils/dist.py", line 985, in run_command
          cmd_obj.run()
        File "/opt/conda/lib/python3.8/distutils/command/build.py", line 135, in run
          self.run_command(cmd_name)
        File "/opt/conda/lib/python3.8/distutils/cmd.py", line 313, in run_command
          self.distribution.run_command(command)
        File "/opt/conda/lib/python3.8/distutils/dist.py", line 985, in run_command
          cmd_obj.run()
        File "/opt/conda/lib/python3.8/site-packages/setuptools/command/build_ext.py", line 79, in run
          _build_ext.run(self)
        File "/opt/conda/lib/python3.8/site-packages/Cython/Distutils/old_build_ext.py", line 186, in run
          _build_ext.build_ext.run(self)
        File "/opt/conda/lib/python3.8/distutils/command/build_ext.py", line 340, in run
          self.build_extensions()
        File "/opt/conda/lib/python3.8/site-packages/torch/utils/cpp_extension.py", line 843, in build_extensions
          build_ext.build_extensions(self)
        File "/opt/conda/lib/python3.8/site-packages/Cython/Distutils/old_build_ext.py", line 195, in build_extensions
          _build_ext.build_ext.build_extensions(self)
        File "/opt/conda/lib/python3.8/distutils/command/build_ext.py", line 449, in build_extensions
          self._build_extensions_serial()
        File "/opt/conda/lib/python3.8/distutils/command/build_ext.py", line 474, in _build_extensions_serial
          self.build_extension(ext)
        File "/opt/conda/lib/python3.8/site-packages/setuptools/command/build_ext.py", line 202, in build_extension
          _build_ext.build_extension(self, ext)
        File "/opt/conda/lib/python3.8/distutils/command/build_ext.py", line 528, in build_extension
          objects = self.compiler.compile(sources,
        File "/opt/conda/lib/python3.8/site-packages/torch/utils/cpp_extension.py", line 658, in unix_wrap_ninja_compile
          _write_ninja_file_and_compile_objects(
        File "/opt/conda/lib/python3.8/site-packages/torch/utils/cpp_extension.py", line 1573, in _write_ninja_file_and_compile_objects
          _run_ninja_build(
        File "/opt/conda/lib/python3.8/site-packages/torch/utils/cpp_extension.py", line 1916, in _run_ninja_build
          raise RuntimeError(message) from e
      RuntimeError: Error compiling objects for extension
      [end of output]

  note: This error originates from a subprocess, and is likely not a problem with pip.
error: legacy-install-failure

× Encountered error while trying to install package.
╰─> gridencoder

note: This is an issue with the package mentioned above, not pip.
hint: See above for output from the failure.

Same bug for me

I  can not use the pip install./raymarching build to get the module , I thought it maybe the same kind of issue like yours, can you tell me how to overcome it?
These are my output when I use the "pip install ./raymarching"
 RuntimeError: Error compiling objects for extension
    Error in atexit._run_exitfuncs:
    Traceback (most recent call last):
      File "D:\anaconda\lib\site-packages\colorama\ansitowin32.py", line 59, in closed
        return stream.closed
    ValueError: underlying buffer has been detached
    ----------------------------------------
ERROR: Command errored out with exit status 1: 'D:\anaconda\python.exe' -u -c 'import sys, setuptools, tokenize; sys.argv[0] = '"'"'C:\\Users\\86178\\AppData\\Local\\Temp\\pip-req-build-nttvjyg_\\setup.py'"'"'; __file__='"'"'C:\\Users\\86178\\AppData\\Local\\Temp\\pip-req-build-nttvjyg_\\setup.py'"'"';f=getattr(tokenize, '"'"'open'"'"', open)(__file__);code=f.read().replace('"'"'\r\n'"'"', '"'"'\n'"'"');f.close();exec(compile(code, __file__, '"'"'exec'"'"'))' install --record 'C:\Users\86178\AppData\Local\Temp\pip-record-lqdmeh1z\install-record.txt' --single-version-externally-managed --compile --install-headers 'D:\anaconda\Include\raymarching' Check the logs for full command output.

Okay, I got something that worked for me.
When installing gridencoder, add TORCH_CUDA_ARCH_LIST=6.0 in front.
TORCH_CUDA_ARCH_LIST=6.0 pip install ./gridencoder

I got 6.0 by looking at cuda's arch list, which you can get by running
python3 -c "import torch; print(torch.cuda.get_arch_list())"

which gave me
['sm_37', 'sm_50', 'sm_60', 'sm_70', 'sm_75', 'sm_80', 'sm_86']
                                 ^--- what I used

Same bug for me. I followed the instructions upstairs and tried all available arch list, but unfortunately none of them works. Any help would be appreciated!

Preparing metadata (setup.py) ... done
Building wheels for collected packages: gridencoder
Building wheel for gridencoder (setup.py) ... error
error: subprocess-exited-with-error
× python setup.py bdist_wheel did not run successfully.
│ exit code: 1
╰─> [42 lines of output]
No CUDA runtime is found, using CUDA_HOME='C:/Program Files/NVIDIA GPU Computing Toolkit/CUDA\v12.0'
running bdist_wheel
running build
running build_ext
Traceback (most recent call last):
File "", line 2, in
File "", line 34, in
File "D:\AIGC_Dreamfusion\stable-dreamfusion\gridencoder\setup.py", line 32, in
setup(
File "D:\Program Files\python39\lib\site-packages\setuptools_init_.py", line 153, in setup
return distutils.core.setup(**attrs)
File "D:\Program Files\python39\lib\distutils\core.py", line 148, in setup
dist.run_commands()
File "D:\Program Files\python39\lib\distutils\dist.py", line 966, in run_commands
self.run_command(cmd)
File "D:\Program Files\python39\lib\distutils\dist.py", line 985, in run_command
cmd_obj.run()
File "D:\Program Files\python39\lib\site-packages\wheel\bdist_wheel.py", line 325, in run
self.run_command("build")
File "D:\Program Files\python39\lib\distutils\cmd.py", line 313, in run_command
self.distribution.run_command(command)
File "D:\Program Files\python39\lib\distutils\dist.py", line 985, in run_command
cmd_obj.run()
File "D:\Program Files\python39\lib\distutils\command\build.py", line 135, in run
self.run_command(cmd_name)
File "D:\Program Files\python39\lib\distutils\cmd.py", line 313, in run_command
self.distribution.run_command(command)
File "D:\Program Files\python39\lib\distutils\dist.py", line 985, in run_command
cmd_obj.run()
File "D:\Program Files\python39\lib\site-packages\setuptools\command\build_ext.py", line 79, in run
_build_ext.run(self)
File "D:\Program Files\python39\lib\distutils\command\build_ext.py", line 340, in run
self.build_extensions()
File "D:\Program Files\python39\lib\site-packages\torch\utils\cpp_extension.py", line 499, in build_extensions
_check_cuda_version(compiler_name, compiler_version)
File "D:\Program Files\python39\lib\site-packages\torch\utils\cpp_extension.py", line 382, in _check_cuda_version
torch_cuda_version = packaging.version.parse(torch.version.cuda)
File "D:\Program Files\python39\lib\site-packages\pkg_resources_vendor\packaging\version.py", line 56, in parse
return Version(version)
File "D:\Program Files\python39\lib\site-packages\pkg_resources_vendor\packaging\version.py", line 275, in init
match = self._regex.search(version)
TypeError: expected string or bytes-like object
[end of output]
note: This error originates from a subprocess, and is likely not a problem with pip.
ERROR: Failed building wheel for gridencoder
Running setup.py clean for gridencoder
Failed to build gridencoder
Installing collected packages: gridencoder
Running setup.py install for gridencoder ... error
error: subprocess-exited-with-error
× Running setup.py install for gridencoder did not run successfully.
│ exit code: 1
╰─> [44 lines of output]
No CUDA runtime is found, using CUDA_HOME='C:/Program Files/NVIDIA GPU Computing Toolkit/CUDA\v12.0'
running install
running build
running build_ext
Traceback (most recent call last):
File "", line 2, in
File "", line 34, in
File "D:\AIGC_Dreamfusion\stable-dreamfusion\gridencoder\setup.py", line 32, in
setup(
File "D:\Program Files\python39\lib\site-packages\setuptools_init_.py", line 153, in setup
return distutils.core.setup(**attrs)
File "D:\Program Files\python39\lib\distutils\core.py", line 148, in setup
dist.run_commands()
File "D:\Program Files\python39\lib\distutils\dist.py", line 966, in run_commands
self.run_command(cmd)
File "D:\Program Files\python39\lib\distutils\dist.py", line 985, in run_command
cmd_obj.run()
File "D:\Program Files\python39\lib\site-packages\setuptools\command\install.py", line 61, in run
return orig.install.run(self)
File "D:\Program Files\python39\lib\distutils\command\install.py", line 546, in run
self.run_command('build')
File "D:\Program Files\python39\lib\distutils\cmd.py", line 313, in run_command
self.distribution.run_command(command)
File "D:\Program Files\python39\lib\distutils\dist.py", line 985, in run_command
cmd_obj.run()
File "D:\Program Files\python39\lib\distutils\command\build.py", line 135, in run
self.run_command(cmd_name)
File "D:\Program Files\python39\lib\distutils\cmd.py", line 313, in run_command
self.distribution.run_command(command)
File "D:\Program Files\python39\lib\distutils\dist.py", line 985, in run_command
cmd_obj.run()
File "D:\Program Files\python39\lib\site-packages\setuptools\command\build_ext.py", line 79, in run
_build_ext.run(self)
File "D:\Program Files\python39\lib\distutils\command\build_ext.py", line 340, in run
self.build_extensions()
File "D:\Program Files\python39\lib\site-packages\torch\utils\cpp_extension.py", line 499, in build_extensions
_check_cuda_version(compiler_name, compiler_version)
File "D:\Program Files\python39\lib\site-packages\torch\utils\cpp_extension.py", line 382, in _check_cuda_version
torch_cuda_version = packaging.version.parse(torch.version.cuda)
File "D:\Program Files\python39\lib\site-packages\pkg_resources_vendor\packaging\version.py", line 56, in parse
return Version(version)
File "D:\Program Files\python39\lib\site-packages\pkg_resources_vendor\packaging\version.py", line 275, in init
match = self._regex.search(version)
TypeError: expected string or bytes-like object
[end of output]
note: This error originates from a subprocess, and is likely not a problem with pip.
error: legacy-install-failure
× Encountered error while trying to install package.
╰─> gridencoder
note: This is an issue with the package mentioned above, not pip.
error occurred when building gridencode on windows 10, python 3.9.
Anyone solved it? Thanks for help.

Okay, I got something that worked for me.
When installing gridencoder, add TORCH_CUDA_ARCH_LIST=6.0 in front.
TORCH_CUDA_ARCH_LIST=6.0 pip install ./gridencoder

I got 6.0 by looking at cuda's arch list, which you can get by running
python3 -c "import torch; print(torch.cuda.get_arch_list())"

which gave me
['sm_37', 'sm_50', 'sm_60', 'sm_70', 'sm_75', 'sm_80', 'sm_86']
                     ^--- what I used

Following your comment, I was able to install gridencoder without any error!
Thank you so much!!!

(stable-dreamfusion) C:\Stablediff\stable-dreamfusion\stable-dreamfusion>TORCH_CUDA_ARCH_LIST=3.7 pip install ./gridencoder
'TORCH_CUDA_ARCH_LIST' is not recognized as an internal or external command,
Guessing you're on linux?

Okay, I got something that worked for me.
When installing gridencoder, add TORCH_CUDA_ARCH_LIST=6.0 in front.
TORCH_CUDA_ARCH_LIST=6.0 pip install ./gridencoder

I got 6.0 by looking at cuda's arch list, which you can get by running
python3 -c "import torch; print(torch.cuda.get_arch_list())"

which gave me
['sm_37', 'sm_50', 'sm_60', 'sm_70', 'sm_75', 'sm_80', 'sm_86']
                     ^--- what I used

Following your comment, I was able to install gridencoder without any error! Thank you so much!!!

(stable-dreamfusion) C:\Stablediff\stable-dreamfusion\stable-dreamfusion>TORCH_CUDA_ARCH_LIST=3.7 pip install ./gridencoder
'TORCH_CUDA_ARCH_LIST' is not recognized as an internal or external command,
Guessing you're on linux? As on windows, the command doesn't work. Using anaconda

@DuckersMcQuack if you're on windows, you need to set environment variables in a different way

@DuckersMcQuack @569363087 if you're on windows, you need to set environment variables in a different way

Sadly that page was way too confusing for me.
And I have managed to get it to work, but now it says "_gridencoder was not found" googled my butt off, but found nothing relevant to my issue.

@DuckersMcQuack @569363087 if you're on windows, you need to set environment variables in a different way

Sadly that page was way too confusing for me.
And I have managed to get it to work, but now it says "_gridencoder was not found" googled my butt off, but found nothing relevant to my issue.

Is the problem solved? How did you solve it?


msbuild /t:<anyTask> foo.sln fails if solution file has comment inside projectSection

NuGet team broke our solution file, so msbuild was no longer able to successfully parse it.
It turned out that a comment in the wrong place of the solution file, worked fine in VS, but broke msbuild parsing of that solution.
Not a critical bug to fix...but nice to have eventually.
Our Issue: https://github.com/NuGet/Home/issues/8239
Our fix: https://github.com/NuGet/NuGet.Client/commit/686dd6b060639a0fb401eceb4c3a4029c1482023
Steps to reproduce
Project("{FAE04EC0-301F-11D3-BF4B-00C04F79EFBC}") = "NuGetConsole.Host.PowerShell", "src\NuGet.Clients\NuGetConsole.Host.PowerShell\NuGetConsole.Host.PowerShell.csproj", "{5A79EEF3-51C0-4A14-8D37-50EF38AD835D}"
# This comment is ok.
ProjectSection(ProjectDependencies) = postProject
# This comment will cause problems.
{26DC17AC-A390-4515-A2C0-07A0950036C5} = {26DC17AC-A390-4515-A2C0-07A0950036C5}
EndProjectSection
EndProject
Expected  behavior
msbuild /t:restore nuget.sln works
Actual behavior
Output:
error: Parent project GUID not found in "NuGetConsole.Host.PowerShell" project dependency section. C:\repos\nc-dotnetlist\NuGet.sln
Environment data
reproduced this in msbuild 15.9 and msbuild 16.1
I think it also reproed with dotnet msbuild

Thanks for the report. I believe this was reported earlier, let me see if I can find the original.

Duplicate of #4328


bugfix/SPEECH-795: Fixing bug when splitting on strings with 'and' and multipliers

Coverage:
Name                      Stmts   Miss  Cover
---------------------------------------------
words2num/__init__.py         4      0   100%
words2num/base.py            10      0   100%
words2num/core.py             9      0   100%
words2num/lang_EN_US.py     102      4    96%


PostgreSQL - schema and table autocompletion does not work

Hi,
PostgreSQL 9.5
DBeaver 3.7.5 (Linux 64 .deb version)
When I try to perform a completion of a schema / table name with ctrl + space, if the table is in another schema than the "active" schema, nothing is displayed, since the table exists.
Only tables in "active" schema are displayed if I type the table name (without the schema name).
Schema names autocompletion does not work either.
This features worked well in previous versions.
No message in the error logs.
Thanks for your help.
Regards,
Cedric

Thanks for report

Fix will be in the next version.
Till then as a workaround you can add database name ("postgres" by default) before schema name. So full table name will look like "postgres.public.table". Not convenient but works.

Thanks.
If the schema is active, it also works. So there are two workarounds.

Having the same issue with DBeaver 4.0.7 and latest JDBC driver at the moment (42.1.1)
when the schema is active the autocompletion is working (but not adding the schema which I think it should). I have the option to use short object-names disabled.
When the schema is not active it CTRL+space gives 'no proposals'.

Auto-completion for non-active (and non-system) schema works only if you specify schema name before table.
So it works as expected.

For those who want autocompletion over multiple schema's. Version 3.6.10 does this the old way.
Example : select * from dat
When you hit CTRL-SPACE all schema's containing all tables with dat in the name will be shown. Just letting you know.
Regards,
Jeroen