STS pods not able to be scheduled at all after deletion

Version

Karpenter Version: v0.16.1

Kubernetes Version: v1.23.10
Expected Behavior
After deleting STS pod, karpenter should schedule the new pod onto the same host node as the previous pod.
Actual Behavior
2022-10-07T19:11:07.399Z        ERROR   controller.provisioning Could not schedule pod, incompatible with provisioner "default", incompatible requirements, key kubernetes.io/hostname, kubernetes.io/hostname In [ip-172-21-3-72.us-west-2.compute.internal] not in kubernetes.io/hostname In [hostname-placeholder-0921]; incompatible with provisioner "scylla", incompatible requirements, key kubernetes.io/hostname, kubernetes.io/hostname In [ip-172-21-3-72.us-west-2.compute.internal] not in kubernetes.io/hostname In [hostname-placeholder-0922]   {"commit": "b157d45", "pod": "stage/scylla-us-west-2-2a-0"}
Steps to Reproduce the Problem
Deployed a scylla cluster via the scylla operator. It created the below statefulset.
apiVersion: apps/v1
kind: StatefulSet
metadata:
  labels:
    app: scylla
    app.kubernetes.io/managed-by: scylla-operator
    app.kubernetes.io/name: scylla
    scylla/cluster: scylla
    scylla/datacenter: us-west-2
    scylla/rack: 2a
    scylla/scylla-version: 4.5.1
  name: scylla-us-west-2-2a
  namespace: stage
  ownerReferences:
  - apiVersion: scylla.scylladb.com/v1
    blockOwnerDeletion: true
    controller: true
    kind: ScyllaCluster
    name: scylla
    uid: 24b66fe1-e16e-4bca-8d67-71b92bf579f0
  resourceVersion: "20174628"
  uid: 17b8ebe2-a446-4b65-a715-7660fe401bf6
spec:
  podManagementPolicy: OrderedReady
  replicas: 1
  revisionHistoryLimit: 10
  selector:
    matchLabels:
      app: scylla
      app.kubernetes.io/managed-by: scylla-operator
      app.kubernetes.io/name: scylla
      scylla/cluster: scylla
      scylla/datacenter: us-west-2
      scylla/rack: 2a
  serviceName: scylla-client
  template:
    metadata:
      annotations:
        prometheus.io/port: "9180"
        prometheus.io/scrape: "true"
      creationTimestamp: null
      labels:
        app: scylla
        app.kubernetes.io/managed-by: scylla-operator
        app.kubernetes.io/name: scylla
        scylla/cluster: scylla
        scylla/datacenter: us-west-2
        scylla/rack: 2a
        scylla/scylla-version: 4.5.1
    spec:
      affinity:
        nodeAffinity:
          requiredDuringSchedulingIgnoredDuringExecution:
            nodeSelectorTerms:
            - matchExpressions:
              - key: node.kubernetes.io/instance-type
                operator: In
                values:
                - i3en.xlarge
              - key: topology.kubernetes.io/zone
                operator: In
                values:
                - us-west-2a
      containers:
      - command:
        - /mnt/shared/scylla-operator
        - sidecar
        - --service-name=$(SERVICE_NAME)
        - --cpu-count=$(CPU_COUNT)
        - --loglevel=2
        env:
        - name: SERVICE_NAME
          valueFrom:
            fieldRef:
              apiVersion: v1
              fieldPath: metadata.name
        - name: CPU_COUNT
          valueFrom:
            resourceFieldRef:
              containerName: scylla
              divisor: "1"
              resource: limits.cpu
        image: scylladb/scylla:4.5.1
        imagePullPolicy: IfNotPresent
        lifecycle:
          preStop:
            exec:
              command:
              - /bin/sh
              - -c
              - PID=$(pgrep -x scylla);supervisorctl stop scylla; while kill -0 $PID;
                do sleep 1; done;
        livenessProbe:
          failureThreshold: 12
          httpGet:
            path: /healthz
            port: 8080
            scheme: HTTP
          periodSeconds: 10
          successThreshold: 1
          timeoutSeconds: 10
        name: scylla
        ports:
        - containerPort: 7000
          name: intra-node
          protocol: TCP
        - containerPort: 7001
          name: tls-intra-node
          protocol: TCP
        - containerPort: 7199
          name: jmx
          protocol: TCP
        - containerPort: 9180
          name: prometheus
          protocol: TCP
        - containerPort: 9042
          name: cql
          protocol: TCP
        - containerPort: 9142
          name: cql-ssl
          protocol: TCP
        - containerPort: 9160
          name: thrift
          protocol: TCP
        readinessProbe:
          failureThreshold: 1
          httpGet:
            path: /readyz
            port: 8080
            scheme: HTTP
          periodSeconds: 10
          successThreshold: 1
          timeoutSeconds: 30
        resources:
          limits:
            cpu: 3600m
            memory: 30Gi
          requests:
            cpu: 3600m
            memory: 30Gi
        securityContext:
          capabilities:
            add:
            - SYS_NICE
          runAsGroup: 0
          runAsUser: 0
        startupProbe:
          failureThreshold: 40
          httpGet:
            path: /healthz
            port: 8080
            scheme: HTTP
          periodSeconds: 10
          successThreshold: 1
          timeoutSeconds: 30
        terminationMessagePath: /dev/termination-log
        terminationMessagePolicy: File
        volumeMounts:
        - mountPath: /var/lib/scylla
          name: data
        - mountPath: /mnt/shared
          name: shared
          readOnly: true
        - mountPath: /mnt/scylla-config
          name: scylla-config-volume
          readOnly: true
        - mountPath: /mnt/scylla-client-config
          name: scylla-client-config-volume
          readOnly: true
      - args:
        - -c
        - /etc/scylla-manager-agent/scylla-manager-agent.yaml
        - -c
        - /mnt/scylla-agent-config/scylla-manager-agent.yaml
        - -c
        - /mnt/scylla-agent-config/auth-token.yaml
        image: scylladb/scylla-manager-agent:2.5.2
        imagePullPolicy: IfNotPresent
        name: scylla-manager-agent
        ports:
        - containerPort: 10001
          name: agent-rest-api
          protocol: TCP
        resources:
          requests:
            cpu: 50m
            memory: 10M
        terminationMessagePath: /dev/termination-log
        terminationMessagePolicy: File
        volumeMounts:
        - mountPath: /var/lib/scylla
          name: data
        - mountPath: /mnt/scylla-agent-config/scylla-manager-agent.yaml
          name: scylla-agent-config-volume
          readOnly: true
          subPath: scylla-manager-agent.yaml
        - mountPath: /mnt/scylla-agent-config/auth-token.yaml
          name: scylla-agent-auth-token-volume
          readOnly: true
          subPath: auth-token.yaml
      dnsPolicy: ClusterFirstWithHostNet
      initContainers:
      - command:
        - /bin/sh
        - -c
        - cp -a /usr/bin/scylla-operator /mnt/shared
        image: scylladb/scylla-operator:1.7.4
        imagePullPolicy: IfNotPresent
        name: sidecar-injection
        resources:
          limits:
            cpu: 10m
            memory: 50Mi
          requests:
            cpu: 10m
            memory: 50Mi
        terminationMessagePath: /dev/termination-log
        terminationMessagePolicy: File
        volumeMounts:
        - mountPath: /mnt/shared
          name: shared
      restartPolicy: Always
      schedulerName: default-scheduler
      securityContext:
        runAsGroup: 0
        runAsUser: 0
      serviceAccount: scylla-member
      serviceAccountName: scylla-member
      terminationGracePeriodSeconds: 900
      volumes:
      - emptyDir: {}
        name: shared
      - configMap:
          defaultMode: 420
          name: scylla-config
          optional: true
        name: scylla-config-volume
      - name: scylla-agent-config-volume
        secret:
          defaultMode: 420
          optional: true
          secretName: scylla-agent-config
      - name: scylla-client-config-volume
        secret:
          defaultMode: 420
          optional: true
          secretName: scylla-client-config-secret
      - name: scylla-agent-auth-token-volume
        secret:
          defaultMode: 420
          secretName: scylla-auth-token
  updateStrategy:
    rollingUpdate:
      partition: 0
    type: RollingUpdate
  volumeClaimTemplates:
  - apiVersion: v1
    kind: PersistentVolumeClaim
    metadata:
      creationTimestamp: null
      labels:
        app: scylla
        app.kubernetes.io/managed-by: scylla-operator
        app.kubernetes.io/name: scylla
        scylla/cluster: scylla
        scylla/datacenter: us-west-2
        scylla/rack: 2a
      name: data
    spec:
      accessModes:
      - ReadWriteOnce
      resources:
        requests:
          storage: 2Ti
      storageClassName: nvme-ssd
      volumeMode: Filesystem
    status:
      phase: Pending

After updating the resource limits, the pod was deleted, but a new one could not get scheduled with the above error. Upon rolling back the changes to the sts and deleting the stuck pod. The new pod that was identical to the original one also failed to schedule with the above error.
scylla provisioner
apiVersion: karpenter.sh/v1alpha5
kind: Provisioner
metadata:
  annotations:
    kubectl.kubernetes.io/last-applied-configuration: |
      {"apiVersion":"karpenter.sh/v1alpha5","kind":"Provisioner","metadata":{"annotations":{},"name":"scylla"},"spec":{"providerRef":{"name":"instance-store-mount"},"requirements":[{"key":"karpenter.sh/capacity-type","operator":"In","values":["spot","on-demand"]},{"key":"karpenter.k8s.aws/instance-family","operator":"In","values":["i3","i3en"]},{"key":"kubernetes.io/arch","operator":"In","values":["amd64"]}],"ttlSecondsAfterEmpty":30}}
  creationTimestamp: "2022-09-19T20:02:05Z"
  generation: 1
  name: scylla
  resourceVersion: "17823265"
  uid: c211edb9-ee72-43ac-a859-2d65697872c1
spec:
  providerRef:
    name: instance-store-mount
  requirements:
  - key: karpenter.sh/capacity-type
    operator: In
    values:
    - spot
    - on-demand
  - key: karpenter.k8s.aws/instance-family
    operator: In
    values:
    - i3
    - i3en
  - key: kubernetes.io/arch
    operator: In
    values:
    - amd64
  ttlSecondsAfterEmpty: 30

Resource Specs and Logs
provisioner controller logs:
2022-10-07T19:27:07.488Z        ERROR   controller.provisioning Could not schedule pod, incompatible with provisioner "default", incompatible requirements, key kubernetes.io/hostname, kubernetes.io/hostname In [ip-172-21-3-72.us-west-2.compute.internal] not in kubernetes.io/hostname In [hostname-placeholder-1305]; incompatible with provisioner "scylla", incompatible requirements, key kubernetes.io/hostname, kubernetes.io/hostname In [ip-172-21-3-72.us-west-2.compute.internal] not in kubernetes.io/hostname In [hostname-placeholder-1306]   {"commit": "b157d45", "pod": "stage/scylla-us-west-2-2a-0"}

pod events:
  Warning  FailedProvisioning  17m                   karpenter          Failed to provision new node, incompatible with provisioner "default", incompatible requirements, key kubernetes.io/hostname, kubernetes.io/hostname In [ip-172-21-3-72.us-west-2.compute.internal] not in kubernetes.io/hostname In [hostname-placeholder-0901]; incompatible with provisioner "scylla", incompatible requirements, key kubernetes.io/hostname, kubernetes.io/hostname In [ip-172-21-3-72.us-west-2.compute.internal] not in kubernetes.io/hostname In [hostname-placeholder-0902]
  Warning  FailedProvisioning  3m4s (x172 over 17m)  karpenter          (combined from similar events): Failed to provision new node, incompatible with provisioner "default", incompatible requirements, key kubernetes.io/hostname, kubernetes.io/hostname In [ip-172-21-3-72.us-west-2.compute.internal] not in kubernetes.io/hostname In [hostname-placeholder-1245]; incompatible with provisioner "scylla", incompatible requirements, key kubernetes.io/hostname, kubernetes.io/hostname In [ip-172-21-3-72.us-west-2.compute.internal] not in kubernetes.io/hostname In [hostname-placeholder-1246]
  Warning  FailedScheduling    47s (x17 over 18m)    default-scheduler  0/8 nodes are available: 1 Insufficient cpu, 1 Insufficient memory, 1 node(s) had taint {eks.amazonaws.com/compute-type: fargate}, that the pod didn't tolerate, 6 node(s) didn't match Pod's node affinity/selector.

Community Note

Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
If you are interested in working on this issue or have submitted a pull request, please leave a comment

In case it wasn't clear the pvc for that pod already exists and is tied to a specific instance (it's a local pv).

Karpenter doesn't schedule pods to nodes, it just launches new nodes so that kube-scheduler can schedule the pods.The pod in your error log appears to have a label selector of:
kubernetes.io/hostname: ip-172-21-3-72.us-west-2.compute.internal
Karpenter isn't launching a node as it wouldn't help in that case.  The node that we launched wouldn't have that hostname when it came up so the pod wouldn't schedule anyway.


chore: Updated Dynatrace JMeter extension to 1.8.0

This PR
Updates the Dynatrace JMeter Extension that is installed into the jmeter-service from 1.3 to 1.8 (latest)
Related Issues
Fixes #6877
How to test
No additional tests needed as this is just an update of a dependency

hey @grabnerandi !
thanks for the PR, could you please fix the missing signoff on your commit? :)

Hey @mowies - just did the DOC. sorry for missing this

@grabnerandi could you please pull, then run git rebase HEAD~2 --signoff and the force push on this PR? then the DCO should be fixed for good


[feature] added dependency management

Added golang/dep dependency management

I appreciate the effort but seeing as this is supposed to be a library I'm against including the vendor directory in the repo.

@knarz having the vendor folder into the repository is commonly advised as good practice in the Golang ecosystem, however not strictly, here some pro/cons from https://github.com/golang/dep/blob/master/docs/FAQ.md#should-i-commit-my-vendor-directory
Pros

It's the only way to get truly reproducible builds, as it guards against upstream renames, deletes and commit history overwrites.
You don't need an extra dep ensure step to sync vendor/ with Gopkg.lock after most operations, such as go get, cloning, getting latest, merging, etc.

Cons

Your repo will be bigger, potentially a lot bigger, though prune can help minimize this problem.
PR diffs will include changes for files under vendor/ when Gopkg.lock is modified, however files in vendor/ are hidden by default on Github.

What do you think?

I am aware of the pros and cons and agree that for applications that best practice should be followed but I think that libraries should let their users decide.

I am not sure what is your point, but I won't hang more on this, I've removed the vendor folder. It's not a big deal at the end. Thanks

what do you think @knarz

should I expect a response anytime soon @knarz ?


Fix Summon Validation

Fix summon form date field validation/required state

needs to recognize default value and display it

needs to prevent submission if end is before start or if not filled out

requires an SDK update for some of this


Increase unit test coverage of at_client package to > 40%

Describe the bug
Unit test coverage of the at_client package is currently very low (< 10%)
Additional context
https://stackoverflow.com/a/34698711 is a good summary of why this matters. Excerpt:

[Code coverage] has a clear relationship to how well-tested the code is, which in turn is our best way to
increase confidence in its correctness. Code coverage is a measurable approximation of immeasurable
qualities we care about.

Previously we just had #352 but this is too big for a single issue

Adjusting target to reduce the size of this issue.

https://github.com/atsign-foundation/at_client_sdk/pull/378
coverage improved from 4.6 to 8.6%

Remaining: Once #350 and #373 have been merged then @gkc will resolve merge conflicts in their unit tests branch and merge in. Effort for #350 and #373 is included in those tickets; remaining effort here is 2SP approx


Conduits dont place

Issue Description:
Problem with conduits
What happens:
When placing Conduits they never actually place, and or leave my inventory
What you expected to happen:
The conduits to place
Steps to reproduce:
1.Place conduit
2.Breaking will result in a invisible block
3.It never left your inventory in the beginning
...

Affected Versions (Do not use "latest"):

EnderIO: .32
EnderCore: .21
Minecraft: 1.9,4
Forge:  1.9.4-<IP_ADDRESS>2

Your most recent log file where the issue was present:
Forge Log: http://pastebin.com/G7C3W5LF

Someone close this didnt know forge had a new version

gah, I nearly clicked on "reopen issue" to close it for you ;)


Userscript should work at Imgur and SoundCloud too

:goat:

Imgur implemented in https://github.com/lidel/yt-looper/commit/81fc8b3d841f43ceaa1cae3e5a03db7e9fc8f3e8


replica's binlog would be reset, once pod is reconstructed.

https://github.com/presslabs/mysql-operator/blob/47436cc5edd3d974239e45c994ccf7e22afa65e0/pkg/sidecar/appconf.go#L196

The logic of FirstPodInSet should be removed. @AMecea

Hi @jianhaiqing, can you explain a little more? Thanks!

Hi @jianhaiqing, can you explain a little more? Thanks!

// the slave pod doesn't need to back up sys_operator.status, Xtrabackup might have some bugs that
// cause the table to be unclean. We can do this cleanup before the slave pod starts to avoid accidents.
if !cfg.IsFirstPodInSet() {
queries = append(queries, fmt.Sprintf("DROP TABLE IF EXISTS %s.%s",
	constants.OperatorDbName, constants.OperatorStatusTableName))
}

The logic is used, replica is created, and xtrabackup's "--tables-exclude=sys_operator.status" can't work properly.
But, once the replica is running for a while,  and there's a rolling update for each pod. Then the status would be dropped. again, and reset master; set global gtid_purged='' would be executed again. master-replica io_thread or sql_thread might be stopped due to 'binlog is purged or binlog is replayed already.

// the slave pod doesn't need to back up sys_operator.status, Xtrabackup might have some bugs that
// cause the table to be unclean. We can do this cleanup before the slave pod starts to avoid accidents.
if !cfg.IsFirstPodInSet() {
queries = append(queries, fmt.Sprintf("DROP TABLE IF EXISTS %s.%s",
	constants.OperatorDbName, constants.OperatorStatusTableName))
}

The logic is used, replica is created, and xtrabackup's "--tables-exclude=sys_operator.status" can't work properly.
But, once the replica is running for a while,  and there's a rolling update for each pod. Then the status would be dropped. again, and reset master; set global gtid_purged='' would be executed again. master-replica io_thread or sql_thread might be stopped due to 'binlog is purged or binlog is replayed already.

how to rename xtrabackup_binlog_info after set global gtid_purged='@gtid' is run ?
remove --tables-exclude from xtrabackup ?

how to rename xtrabackup_binlog_info after set global gtid_purged='@gtid' is run ?
remove --tables-exclude from xtrabackup ?

It really confuse me, could you explain the logical more detailed for me. In my option, it's fatal issue, replicas' binlog might be reset again once it's reconstructed again.

It really confuse me, could you explain the logical more detailed for me. In my option, it's fatal issue, replicas' binlog might be reset again once it's reconstructed again.

this problem is sloved ?  i still has this issues


Standalone ABAP doc reader

Ref #72
Feel free to continue to work on this PR

[ ] Replace RSWSOURCET data type, compare a1486a0

last error is a false positive by abaplint, will try fixing it in abaplint first

also started some implementation of SCAN = https://github.com/open-abap/open-abap/pull/315

@larshp Thanks for taking over. I had no time during the last two weeks :(


Add taxa endpoints

New endpoints
This PR adds the /taxa endpoints from the iNaturalist Node API:

/taxa
/taxa/{id}
/taxa/autocomplete

Rank ranges
In addition to the parameters exposed by  /taxa, this also adds support for searching taxa by a range of ranks, via min_rank and/or max_rank. This is intended to match the search features in the web UI:

Minor documentation, dependency, and config updates

Add development packages to [dev] setuptools extra
(e.g., for local testing, generating docs, etc. outside of tox environments)
Add a couple more example commands to docs
Bump pinned version of requests-mock to 1.7.0 for recent feature additions
Bump pinned version of pytest to 4.6.9
(the last release that still works under python3.4)
Add Sphinx and sphinx-autodoc-typehints to requirements.txt

Note on unit tests
requests_mock now provides a pytest fixture, which plays more nicely with pytest than the decorator. See:

https://github.com/pytest-dev/pytest/issues/2749
https://bugs.launchpad.net/requests-mock/+bug/1714756
https://github.com/jamielennox/requests-mock/pull/51

Checklist

[x] Issue: #12
[x] Docstrings (that render correctly in Sphinx)
[x] Unit tests
[x] Sample data
[x] Type annotations
[x] Black formatting

Please let me know if there is anything you'd like me to change in this PR, or if you have additional contribution guidelines to follow that I missed.

Wow, thanks a lot for the contribution @JWCook!
Sorry for my lack of responsiveness, I've been quite busy recently but I'll have a lok very soon and will let you know!

@niconoe No worries, take your time!
It looks like I have a couple compatibility issues to fix for the older interpreters. I'll get those sorted out, but would you consider dropping support for Python <= 3.5 at some point in the future? Python 3.4 reached EOL in March 2019, and 3.5 will reach EOL this September.

@JWCook: about Python compatibility: I don't have a very strong opinion on this, I'd say supporting 3.4 (the most recent deprecated one) is nice for now, but not forever...
If we keep this logic, it could make sense to only support 3.5+ after September (once 3.5 is itself unsupported). Do you think that would be reasonable?

@niconoe Sure, sounds reasonable.
Also, I rebased onto master once more. I'm done messing with this PR now; I'll likely have another one for you to review soon, though.


Collection, folder, and request variables scope

I have checked the following:

[X] I've searched existing issues and found nothing related to my issue.

Describe the feature you want to add
Collection, folder, and request variables currently do not scope properly. They are all treated as runtime variables.
i.e., A variable set in a folder should not be accessible to any requests outside of that folder.
This feature will allow users to create better integration tests by sharing variables within a folder and not worry about naming conflicts.
Side question: What was the original intent for variables at collection, folder, and request level if they all are considered runtime variables?
Mockups or Images of the feature
No mock up. This is an functionality change.

UP please.
Being able to only set variable via scripts in the Environment is so painful... The Scripting Doc just allow us to get the collection and folder variable, but not to set it.


ERROR  Invariant Violation: new NativeEventEmitter() requires a non-null argument.

Trying to get this working in Tamagui.
I'm setting it up in the kitchen-sink there, I've run expo doctor and fixed all versions. React Native 0.71.7.
It runs fine, but once I import react-native-ios-modal I get:
ERROR  Invariant Violation: `new NativeEventEmitter()` requires a non-null argument.

Any idea?

Had to re-install pods for a fourth time or something odd...


Add resolver data on lookup items

This change is

Current dependencies on/for this PR:

main

PR #2885

PR #2886   👈

This comment was auto-generated by Graphite.


chore: NO-JIRA update playwright

chore: NO-JIRA update playwright
:hammer_and_wrench: Type Of Change

[x] Other (chore)

:book: Description
Update playwright to latest version
:bulb: Context
We were having an issue with accessibility tests failing on CI because playwright version is too old. Testing to see if this will fix it.
:pencil: Checklist

For all PRs:

[x] I have ensured no private Dialpad links or info are in the code or pull request description (Dialtone is a public repo!).
[x] I have reviewed my changes.
[x] I have added all relevant documentation.
[x] I have considered the performance impact of my change.

Making a change to vue component to trigger a11y tests

Seems to have fixed it.


Completely forgets about chat context, and generally feels dumber than ChatGPT4

Version: 1.79.0-insider (system setup)
Commit: f6be5461f8bc69013a605f5baea834651c6589fb
Date: 2023-05-20T01:18:53.811Z
Electron: 22.5.2
Chromium: 108.0.5359.215
Node.js: 16.17.1
V8: <IP_ADDRESS>-electron.0
OS: Windows_NT x64 10.0.22623
Github Copilot Nightly: v1.86.118
Steps to Reproduce:

Ask a general question, in this case about whether some events used with event-driven architecture (EDA) could be improved
It lists some general suggestions but doesn't feel like it's even looking at the 3 (simple) interfaces I have open in VS Code, but it does list 5 points, in numbered points.
Ask follow-up questions about how to do points 3,4,5 it suggested
It starts talking about something completely irrelevant, in this case about code folding?!?

Was really excited about this new Copilot, but it really feels 10x dumber than even ChatGPT 3.5, not sure if it's because you are not feeding it enough context of the open files, or if you just have way too aggressive GPT parameters running.
Meanwhile, if you ask ChatGPT4, the same question, it answers clearly, and as intended, a similar question is asked in ChatGPT4 here: https://chat.openai.com/share/c30f92f3-461f-4441-9de3-f9affa239404, it understands you are talking about the previous points.
Not sure what has happed to GPT4 in Microsoft, it's the same problem on bing, it always feels more like GPT3.5 than GPT4 for coding related things, while it's extremely rare, that ChatGPT4 gets things wrong, or doesn't understand the context, even after 20+ Q/A's down the line in a conversation.
This is not the first time I have seen it being completely lost:

And when you actually do get it to write unit tests in xUnit, they often don't even compile, meanwhile ChatGPT4 even with less knowledge/context, is able to generate them without issues.
I'm fully aware this is an early preview, but I just don't get how the Microsoft "GPT4" implementation, is so much worse compared to ChatGPT, if it's a cost issue just let us pay for it.

skill issue

I am at the point of needing to give it nearly everything, where I might aswell just code it myself.
Too add to that I am getting a lot of "Your Response Got Filtered"
I feel like you have to Tablespoon feed Github Copilot, while GPT 4 API you only need a Teaspoon.

it appears to be using gpt 3.

Here's an alternative which lets you use GPT4 with your own API key

Here's an alternative which lets you use GPT4 with your own API key

looks nice, but this doesn't work with vscode, so not really an alternative ?

Update from #6: All responses in panel/quick chat are served by GPT-4 since Copilot Chat 0.10 (part of VS Code's October release). 3.5 is still used for other messages.
Please give it a try and file new issues for any follow-up feedback!

@digitarald Still seeing GPT-3 in v0.10.0:

@digitarald Can confirm the answers are still GPT-3 level too. They aren't anywhere near as good as the GPT-4 model in ChatGPT


[CGD2D] CGContextClearRect crashes if used under CGContextPushBegin/PopEndDraw

This is because it's using the raw ->BeginDraw() and ->EndDraw().
I must've missed this during #1750.

Oops right I forgot that the 'Fixes' in the commit message doesn't actually close if I merge to a non-develop branch.


Multiple cookbooks

What does this PR do?
Contains cookbook for the following:

AWS photo rekognition
AWS polly
Stripe payment and
Web scraping.

Codecov Report

Merging #231 into master will decrease coverage by <.01%.
The diff coverage is n/a.

@@            Coverage Diff            @@
##           master    #231      +/-   ##
=========================================
- Coverage    34.1%   34.1%   -0.01%
=========================================
  Files         119     121       +2
  Lines        4647    4650       +3
  Branches        5       5
=========================================
+ Hits         1585    1586       +1
- Misses       3062    3064       +2

@jonny22094 can you take over this thing?


Relief from "warning: already initialized constant" in supermarket release?

/var/.../cookbooks/firewall/libraries/provider_firewall_rule_firewalld.rb:60: warning: already initialized constant Chef::Provider::FirewallRuleFirewalld::CHAIN
/var/.../cookbooks/firewall/libraries/provider_firewall_rule_firewalld.rb:60: warning: previous definition of CHAIN was here

ad infinitum
This seems fixed in c9240b8006cb8d0cebd5d01a24875103bb5c18d9 but with the most recent supermarket version, all the warnings are still making my test output useless.
It looks like there are a lot of balls in the air right now and it may be inappropriate for a new release at this time, but any tips on avoiding this problem?  Would it be reasonable to "depend" a previous version?

Hi there -- I went ahead and did a maintenance release. The only thing in it is #57. Hope that helps!

Excellent!   Yes thanks, that was quite helpful.


Update README.md

Add Framer Motion implementation.
Let me know if anything needs to change!

Thank you for this PR. However i'm thinking that this example should use lenis/react.

Agree with @clementroche, as most people using lenis with react will use lenis/react. React lenis will setup a rAF for itself so it has to be explicitly disabled with the autoRaf prop on the Provider. This is currently a discrepancy between lenis core and lenis react.

I'll probably wait until we find a proper solution about rAFs

Thank you @meesrutten I added this example to lenis/react documentation:
https://github.com/darkroomengineering/lenis/blob/main/packages/react/README.md#framer-motion-integration


When gateway peer starts or restarts it could be unusable

As of driver downloaded today 22nd Oct 2021 (built 3 days ago)
hyperledger-fabric.jfrog.io/fabric-peer    cd4ffa294471        3 days ago          54.7MB
While testing bringing the gateway peer down and up I've found it to be unreliable when it comes back up, ie unable to submit transactions with 1 of 2 errors
14 UNAVAILABLE: failed to select a set of endorsers that satisfy the endorsement policy

and
14 UNAVAILABLE: no combination of peers can be derived which satisfy the endorsement policy: no peer combination can satisfy the endorsement policy

The gateway peer remains in this state (stopping and starting the client makes no difference). It requires another restart
One thing that appears to affect recovery is how much pressure the client is putting on the gateway peer during the time it comes up. If I reduce the pressure the gateway peer seems to restart more reliably .

Closing as resolved


graphicsmagick: add heif support

Description of changes
AVIF format support requires libheif, otherwise GraphicsMagick does not support decoding/encoding AVIF images. After testing, adding this build dependency, gm can support AVIF decoding (but still does not support encoding, which may require some investigation).
Similarly, the imagemagick package currently includes libheif by default: https://github.com/NixOS/nixpkgs/blob/48c01ad1c8ce68e30de4056f63f36aa34b736bc8/pkgs/applications/graphics/ImageMagick/default.nix#L26
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[x] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
24.11 Release Notes (or backporting 23.11 and 24.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

I'm cutting my nixpkgs-review short at 104 successful builds


Add the ability to tag test files when using the exports interface.

This is something we implemented in my current shop and it has been very useful. Our applications and their services have grown. This makes being able to test particular functionality out of context very useful (or in context if you so choose). To make this accessible to all, I've added a change to the exports ui that looks for an array of tags in options.
Example:
// test/foo.js

var Taggable = require('mocha').Taggable;

module.exports = Taggable(['foo', 'bar'], {
  Foo: {
    '#new Foo()': {
      'foo should be of Foo': function() {
        var foo = foo();
        foo.should.be.instanceOf(Foo);
      }
    }
}

In your task runner you would do something like:
// test/run

var args = process.argv.slice(2);
// some other things like get filenames
var opts = { tags: args };
var mocha = new Mocha(opts).ui('exports');
filenames.forEach(function(file) {
  mocha.addFile(path.join('test',file)).run(failureHandler);
});

And to run your tests:
test/run foo bar other thing which would result in all files tagged with foo, bar, other, or thing to be run. This doesn't affect tests when being run by npm test or mocha directly unless they call on your test runner test/run.

Thanks for the PR! I don't think we'd want to introduce the functionality for a single interface. It'd be great to expand on https://github.com/mochajs/mocha/pull/1830 to include exports as well.

Woah, I should have searched for comments on tags. Really cool to see other people have had the same use case and thoughts on the subject. I plan on digging into #1830 and #1445 in a bit. Thanks for the heads up!


I can't install Wraith on Mac OS/X

My setup Mac OS/X 10.13.5, ruby 2.3.3p222 (2016-11-21 revision 56859) [universal.x86_64-darwin17]. I get an error during compiling stage…
Running 'compile' for libxml2 2.9.8... ERROR, review '/Library/Ruby/Gems/2.3.0/gems/nokogiri-1.8.4/ext/nokogiri/tmp/x86_64-apple-darwin17/ports/libxml2/2.9.8/compile.log' to see what happened. Last lines are:
========================================================================
  CCLD     libxml2.la
  CC       testdso.lo
  CCLD     testdso.la
  CC       xmllint.o
  CCLD     xmllint
ld: warning: ignoring file /usr/local/Cellar/xz/5.2.4/lib/liblzma.dylib, file was built for x86_64 which is not the architecture being linked (i386): /usr/local/Cellar/xz/5.2.4/lib/liblzma.dylib
Undefined symbols for architecture i386:
  "_lzma_auto_decoder", referenced from:
      _xz_head in libxml2.a(xzlib.o)
  "_lzma_code", referenced from:
      _xz_decomp in libxml2.a(xzlib.o)
  "_lzma_end", referenced from:
      ___libxml2_xzclose in libxml2.a(xzlib.o)
  "_lzma_properties_decode", referenced from:
      _is_format_lzma in libxml2.a(xzlib.o)
ld: symbol(s) not found for architecture i386
clang: error: linker command failed with exit code 1 (use -v to see invocation)
make[2]: *** [xmllint] Error 1
make[1]: *** [all-recursive] Error 1
make: *** [all] Error 2
========================================================================
*** extconf.rb failed ***

brew unlink xz; gem install nokogiri; brew link xz

Thank you, that helped!


How do podman containers make connections and port issues?

I can't access http://irc.freenode.net/, so I'd like to ask some questions

Question 1: not root user cannot create a nginx application with a port number of 80?

Podman can not create containers that bind to ports < 1024.
Non priv users are not allowed to bind to ports < 1024, so this requires root.

So I can only create nginx under root? And I also need PHP and mariadb to support my site, I've tried to reference PHP in nginx's configuration file:
location ~ \.php(.*)$ {
    fastcgi_pass   php:9000;
    ...
}

Check with nginx -t and report an error: nginx: [emerg] host not found in upstream "php" in ...
But docker works that way
Question 2: How do I create two 80-port containers in the same pod?
like this：
podman pod create --name zf_site_network -p 80:80 -p 443:443 -p 3306:3306 -p 8888:80

// port 80:80
podman run -d --name nginx --pod zf_site_network nginx
// port 8888:80, need mariadb
podman run -d --name nextcloud --pod zf_site_network nextcloud
// port 3306:3306
podman run -d --name mariadb --pod zf_site_network mariadb
// port 9000:9000, need mariadb
podman run -d --name php --pod zf_site_network php

Thanks!

Podman, when run without root, has no privileges the user running it does not have. Binding ports under 1024 on Linux is a privileged operation, requiring root (though there is a sysctl to change this - see here). This is a disadvantage of rootless Podman, which needs to trade off some functionality like this for security benefits. if you want things to work exactly as Docker does, please use Podman as root.

Pods share a single network stack - everything within a pod will have the same IP address, same localhost, etc. This lets applications talk to each other over localhost, but also means that two applications cannot bind to the same port within a pod. If you have multiple webapps, you can try binding them to different ports on localhost in the pod, then running a single HTTP server that proxies them all that runs on the primary port.

@mheon Thank you for your reply. In addition, if pod is not used, how can containers contact each other?
I see podman support for creating a network, but after I add a container (like Nginx) to the network, the browser can't access the container?
sudo podman network create zf_site_network
podman run -d --name nginx -p 80:80 --network zf_site_network nginx

Networks created as root can only be used by root Podman - we should probably improve documentation about this. I would also expect that podman run would error when you tried the command; does it?

@mheon  Okay, I'm already running podman as root, but how do I communicate between containers? If I can't do that, I'll have to go back to docker. At least, it's easy. Finally, let me say thank you.

Inter container communication is done via <IP_ADDRESS> if they are in a pod. Inter pod communication is done via <IP_ADDRESS> (rootless, in root mode should be found via ip a, conmon interface).
You can also use host networking, especially suitable for ingress reverse proxy. That way, the reverse proxy can find other pods via <IP_ADDRESS>.
Besides, you should stick with root or rootless mode rather than hybrid. To use 443 port in rootless mode you can refer to the documentation.

@ZeronoFreya Assuming the dnsname plugin for CNI is installed (it should be a dependency on most distributions) you can look up other containers via their names, as Docker does. From there, communications works exactly as it does between any two hosts; each container has an IP address, and you can connect between them without issue. You could also assign them static IPs to avoid name lookup.

@ZeronoFreya @mheon Is this a solved problem, and we can close the issue.

I'm going to close this due to a lack of activity; feel free to open a new issue if more questions arise.


CI/CT/CD

@ilkerhalil Did a bot just merge in upstream, or was that you?

@ilkerhalil Did a bot just merge in upstream, or was that you?

@Rjvs I was looking at this too. I did not merge.

Might have to convince the bot to stop hijacking other people's PRs :)

@ilkerhalil created a new PR #4 to get rid of the weirdness.  Closing this one.


TDLib fatal error

TDLib fatal error: [SqliteDb.cpp:79][#1][!Td]	Database was deleted during execution and can't be recreated: [WindowsError : 系统找不到指定的文件。 :"db.sqlite" can't be opened for reading for stat]

Someone deleted the db.sqlite file, required by TDLib. You should be able to start TDLib without issues after that, but some data is lost.

Yeah,i got it,thanks！


[bug 1129102] ditch ditchchart flag

Ditch ditchchart waffle flag from the checks. Remove the flag from
the database using the provided reversible migration.

Other than the missing docstring, this looks good to me.

I have added the docstring to the migration file

Awesome! Thank you!

d44faf3 [bug 1129102] ditch ditchchart flag


Use of language tag ja-Hrkt is inconsistent

As the name suggests, and according to ISO standards, records associated with the language tag ja-Hrkt should include only hiragana and katakana. All records consisting of kanji or a mix of kanji and hiragana and/or katakana should instead be associated with the language tag ja, or internal language ID 11. We are instead associating many records with internal language ID 1, even when they contain kanji. Examples of this can be found in version_names.csv, region_names.csv, pokemon_color_names.csv, and several other files.
It would be good to refactor this by adding records associated with language ID 11 for all tables that have language ID 1 records but no language ID 11 records. I can't think of a scenario where it makes sense to have a ja-Hrkt record but no ja record. The ja record should contain the most standard way to write the data, and the ja-Hrkt record should contain the all hiragana/katakana form of this. This would make the Japanese data much more standardized and easier to use.
Here's an example of how a refactored version of one of these files would look:
pokemon_color_id,local_language_id,name
1,1,くろい
1,5,Noir
1,6,Schwarz
1,8,Nero
1,9,Black
1,11,黒い
2,1,あおい
2,5,Bleu
2,6,Blau
2,8,Blu
2,9,Blue
2,11,青い
3,1,ちゃいろ
3,5,Brun
3,6,Braun
3,8,Marrone
3,9,Brown
3,11,茶色
4,1,はいいろ
4,5,Gris
4,6,Grau
4,8,Grigio
4,9,Gray
4,11,灰色
5,1,みどり
5,5,Vert
5,6,Grün
5,8,Verde
5,9,Green
5,11,緑
6,1,ピンク
6,5,Rose
6,6,Rosa
6,8,Rosa
6,9,Pink
6,11,ピンク
7,1,パーパル
7,5,Violet
7,6,Violett
7,8,Viola
7,9,Purple
7,11,パーパル
8,1,あかい
8,5,Rouge
8,6,Rot
8,8,Rosso
8,9,Red
8,11,赤い
9,1,しろい
9,5,Blanc
9,6,Weiß
9,8,Bianco
9,9,White
9,11,白い
10,1,きいろ
10,5,Jaune
10,6,Gelb
10,8,Giallo
10,9,Yellow
10,11,黄色
As you can see, there's some redundancy between some of the records, and I'm not sure if that's acceptable, but especially in a small table like this, it seems a small price to pay for consistency.

Don't quote me on this, but I believe the language options are parsed from the actual game data, meaning this is how Game Freak use these language options. The iso codes may have been added for convenience sake. I'm not sure why some fields don't have every language, or even every permutation of the same language though.

There was originally no distinction in between ja and ja-Hrkt. Language ID 1 was ja. When the games added the option to switch between kana and kanji text (Gen 6?), we added a new language ID for kanji and changed the old one to ja-Hrkt, on the grounds that the games had mostly stuck to kana up until that point. I guess some tables with translations not ripped from the games (like the colors) were using kanji though. They should be updated with the new language ID.
Here's a complete list of ja-Hrkt text containing kanji characters: https://gist.github.com/magical/2c47e9605de7f1b22981cefd2b812ea8. I'm not sure what's going on with location_names, but other than that they should be easy to fix up.


[REFACTOR] Initialize Unified IR Type Data Structures

Depends on #4615
This PR moves a few base types from relay to the ir sub-folder.
These types will serve as a common type system across the stack.
Notably, we want to be able to use the same FuncType for all function signatures.
I tried to make a minimum move to bring the necessary dependencies for a FuncType.
We can discuss what additional things we want to move as a follow-up.
Notably, because the TensorType will have a dependency on low-level Expr,
we will need to break the type.h into two files and introduce a
tensor_type.h(or leave them in relay for now).

cc @icemelon9 @jroesch @zhiics @wweic @yzhliu

I like the unification of the types for low-level IR and relay. I have one question on the tensor type. Since TE also has Tensor, will it have the TensorType?

To simplify the treatment, most of the low-level expression won't has a tensor type, although by definition it is possible to allow a var to have a tensor type and Pass them over to a function, you cannot do anything other than pass it through calls.

Thanks @icemelon9 @zhiics @MarisaKirisame


JS error: container is null in resetDuration

Issue description:
Getting this error every now and again. We're doing a lot of screwing around right before/after initializing and destroying tiny-slider so it isn't a common use case, but might indicate some other issues:
Uncaught TypeError: Cannot read property 'style' of null
    at Hn (tiny-slider.js:2190)
    at tiny-slider.js:2226

I think what's going on here is that
setTimeout(function() { resetDuration(container, ''); }, 10); is getting set in doContainerTransformSilent, but the container doesn't exist when it gets calls 10ms later. Maybe a sanity check in resetDuration to check that el actually exists would be a quick fix? Alternatively maybe the container needs to be set aside?
var currentContainer = container;
setTimeout(function() { resetDuration(currentContainer, ''); }, 10);

Tiny-slider version:   2.8.2
Browser name && version:  Chrome
OS name && version:   OSX

Do you think you can make a demo?
If it's not good for you do make it public, you can try to replace doContainerTransformSilent with doContainerTransform to see if the issue still happens.
BTW, I don't think it's a good idea to check container's existence only for this specific case.

No problem I can appreciate that, we'll work off a fork for this. Unfortunately it's tied up in a complicated system so isn't easy to extract a small demo, if I get some time I'll see what I can do.

Ok, thanks for your understanding.


Error running Hydrogen

Description:
[Error while running hydrogen on python 3.4]
Steps to Reproduce:

[Install python 3.4]
[Install atom and hydrogen]
[open a .py file]
[run the code via hydrogen]

Versions:
Which OS and which version of Hydrogen and Atom are you running?
You can get this information from copy and pasting the output of atom --version  from the command line.
Atom    : 1.26.0
Electron: 1.7.11
Chrome  : 58.0.3029.110
Node    : 7.9.0
OS : Windows 10 64-bit with 32-bit python 3.4
Logs:
Traceback (most recent call last): File "C:\Python34\lib\site-packages\tornado\ioloop.py", line 288, in current return IOLoop._ioloop_for_asyncio[loop] KeyError: <asyncio.windows_events._WindowsSelectorEventLoop object at 0x06A296F0>

During handling of the above exception, another exception occurred:

Traceback (most recent call last): File "C:\Python34\lib\runpy.py", line 171, in _run_module_as_main "main", mod_spec) File "C:\Python34\lib\runpy.py", line 86, in _run_code exec(code, run_globals) File "C:\Python34\lib\site-packages\ipykernel_launcher.py", line 16, in app.launch_new_instance() File "C:\Python34\lib\site-packages\traitlets\config\application.py", line 657, in launch_instance app.initialize(argv) File "", line 2, in initialize File "C:\Python34\lib\site-packages\traitlets\config\application.py", line 87, in catch_config_error return method(app, args, **kwargs) File "C:\Python34\lib\site-packages\ipykernel\kernelapp.py", line 465, in initialize self.init_kernel() File "C:\Python34\lib\site-packages\ipykernel\kernelapp.py", line 364, in init_kernel shell_stream = ZMQStream(self.shell_socket) File "C:\Python34\lib\site-packages\zmq\eventloop\zmqstream.py", line 108, in init self.io_loop = io_loop or IOLoop.instance() File "C:\Python34\lib\site-packages\zmq\eventloop\ioloop.py", line 105, in instance loop = ioloop.IOLoop.instance(args, kwargs) File "C:\Python34\lib\site-packages\tornado\ioloop.py", line 221, in instance return IOLoop.current() File "C:\Python34\lib\site-packages\tornado\ioloop.py", line 292, in current current = AsyncIOMainLoop(make_current=True) File "C:\Python34\lib\site-packages\tornado\util.py", line 312, in new instance.initialize(*args, init_kwargs) File "C:\Python34\lib\site-packages\tornado\platform\asyncio.py", line 182, in initialize super(AsyncIOMainLoop, self).initialize(asyncio.get_event_loop(), **kwargs) File "C:\Python34\lib\site-packages\tornado\platform\asyncio.py", line 53, in initialize if loop.is_closed(): AttributeError: '_WindowsSelectorEventLoop' object has no attribute 'is_closed'

Please post any error logs and the output of the developer tools as described in our Debugging Guide.

This is a bug on the Python/IPython side.
I don't know your requirements and don't use Windows, but my recommendations are:

Upgrade to a newer version of Python (version 3.6, if possible)
Make sure IPython/Jupyter installation is up-to-date
Anaconda tends to be a more reliable way of installing Python on Windows than the official downloads from python.org


Release announcement generation / publishing

Context
The release pipeline creates and publishes the release announcement discussion. However, the text of the announcement needs to be customized which can prevent us from using the automation to publish it. It would be preferential if the pipeline did it (it will be authored by the bot, etc.).
Proposed solution

The release pipeline will have a new parameter - an announcement gist URL
We will create an empty gist and run the pipeline, supplying the URL to it
The pipeline would print the suggested announcement content during the Pre-Release stage
We can take this and populate the gist where we would final-fit it
The pipeline would take the body of the announcement from there during the Release stage

@MichaelSimons what do you think of this proposal? It should be very easy to implement using the GitHub CLI

I like this approach but I would want the URL to be optional.  For normal servicing releases, I don't recall a time that we posted a custom message, it certainly is an edge case.


Fixed- UnicodeDecodeError: 'charmap' codec can't decode byte 0x9d in position 430: character maps to

To summarize the issue, python defaults to cp1252 encoding, but Windows defaults to UTF-8. This isn't always an issue, but if there are characters within the UTF-8 file that cp1252 cannot convert, it throws an error. So we use chardet to detect the encoding and use the appropriate one to handle the file. This should prevent an issue with Linux users, someone else will need to confirm.

GitHub was annoying and made it so that it was hard to bring your branch up to date w/ some of the more recent changes, so I went and I manually oncorporated the character encoding detection changes into Augmentoolkit. Really appreciate the contribution, and all the things you're bringing up in the issues, BovineOverlord!


release.nix:  attempt to get cardano-node-profiled into Hydra builds

An attempt to get cardano-node-profiled into Hydra builds.

bors r+


Implement `parallel' (just alias of run_after)

I've added the `parallel' config keyword to execute commands parallel. This is the implementation of #107 .
In this implementation, parallel is just an alias of run_after . But I think parallel is more understandable.
I've tested this code with this pipeline.yml.
pipeline:
  - name: command 1
    command: sleep 3
  - name: parallel commands
    parallel:
      - name: parallel command 1
        command: sleep 5
      - name: parallel command 2
        command: sleep 5
  - name: command 2
    command: sleep 3

Please check it.

LGTM


Support NodePort and LoadBalancer Service Types for GatewayStatus Addresses field

Set the GatewayStatus addresses field based on the type of Service that exposes NKG.
The initial issue for supporting GatewayStatus addresses is limited in scope and will set the GatewayStatus address field to the ClusterIP of the Service, regardless of the Service type.
This issue covers the work to support addresses for LoadBalancer and NodePort Services.

Note: this is a blocker for external-dns integration (we need the address from the fronting LoadBalancer Service).

Another note: we set the GatewayStatus to the Pod IP, not the Service's ClusterIP. Should we also support ClusterIP as part of this story? (or maybe not since we'll always use the NodePort or LoadBalancer IP?)

Service ClusterIP is not appropriate.  Since the Gateway is always fronting the service.  You got there.

Do we want to support setting the address to Hostname if available? (https://github.com/kubernetes-sigs/gateway-api/blob/main/apis/v1beta1/shared_types.go#L719)
Or do we only support IP addresses right now?

Do we want to support setting the address to Hostname if available? (https://github.com/kubernetes-sigs/gateway-api/blob/main/apis/v1beta1/shared_types.go#L719)
Or do we only support IP addresses right now?

I think we also want to support Hostname since some LoadBalancers (like AWS NLB) will be exposed with a dns name instead of an IP address.


UI glitches on windows

v7.2.313 (latest stable)
Windows 8.1 x64
Nvidia GeForce 9800 GT
When I continue/stop timer via global shortcut I see UI glitches (which are changing after mouse hover):

It differs time to time: doesn't show description or doesn't change "Start" button to "Stop", etc.
I have latest graphical drivers. Don't see it in other software.

I too see a similar issue.
My working environment is a local Windows 8.1 install and a Virtual Windows 8.1 in the cloud.
I often work between these two machines on the local and then Remote Desktop into the Virtual Machine in full screen mode.
I run Toggl Desktop on both so I can easily change tasks no matter if I am using the Local Machine or the Remote machine.
There are slight UI Sync issues between the too.
For example when I change or stop/start tasks on one machine the UI of toggle is not updated on the other.
Here is a screenshot example of a task already running on my local machine and then I start toggle on the remote machine.
You can see that the title bar of the window correctly state Emails and Admin task but the task description box says "What are you doing?"
Resizing the window usually fixes the display issue.

Got this kind of UI glitches too. Sometimes the UI is freezing.

Thanks for reporting the problem!
We have been busy rewriting the Toggl Desktop user interface on Windows the last few weeks. We just released a new beta version today, that exclusively uses the new framework we are switching to, and we believe that this should solve these glitches you noticed.
Could you try and see if the beta version works better for you?
You can switch to the beta in the "about" window of the app.
After you do, please give the program 5-10 minutes to download the update in the background, and then restart it. It will then install the update automatically.
If the update was successful, it will show the new version number in the about window: 7.2.348
Sorry for the inconvenience!

@amulware I've updated to 7.2.348 and don't see this glitches now. Thanks!
But there is a new issue - when I use global shortcut to continue timer it starts a new empty task (not continue old).

@egoroof Thank you for reporting this I've created another issue for this bug #1531

Just to let you know that I had switched to the dev channel a few days ago. It seems that there is no more glitches as the ones reported here, but there is still some freezes of the UI. A few seconds everytime and it happens often. Should you/I creat a new issue for this ?

@leup Could you please send us a screencast to<EMAIL_ADDRESS>of the issue, so we can see how exactly the the glitches appear. Mention Paul in your email so it's redirected to us straight away.

@leup Actually it would be good if you could just send feedback from the app, that way we get the log files and can investigate the source of the issue.

Closing since original issue was resolved. We are continuing to collect data about performance issues, and hope to get the app buttery smooth for everyone in due time.

The app is a lot more smooth now. Seeing no more UI glitches and no more freezes. Last thing remaining is that sometimes when focusing an input field like the task name nothing happen. It gives the feeling that something is wrong. But start typing anything and the focus appears on the field. It is just the lack of visual feedback that the focus has indeed been given to the field.

@leup Thanks for reporting back!
I can reproduce the focus thing you mention. At least sometimes. No idea what is causing it, but we will definitely take a closer look.


show clinvar version in version API

Currently clinvar version is not shown:
https://www.genomenexus.org/version

@inodb I willing to work on this. Could you please guide me if the clinvar version will be coming from database or its to be specified in properties file?

This is solved in the latest release


Cannot create transparent network on Windows 10: hnsCall failed in Win32: The remote procedure call failed. (0x6be)

Description
I'm trying to create a transparent network on my Surface Pro 3 with Windows 10 (all updates applied). This worked with Docker 1.12 but after upgrading to 1.13 I had to recreate the networks which fails. I've removed all virtual networks from the Hyper-V management console and re-installed Docker. The DockerNAT vnet is created automatically, but after switching to Windows containers creating a transparent network fails.
Steps to reproduce the issue:
Run: docker network create -d transparent wlan
Describe the results you received:
Whether I specify the interface name or not (via the com.docker.network.windowsshim.interface option or not), I receive the following error:

Error response from daemon: hnsCall failed in Win32: The remote procedure call failed. (0x6be)

Describe the results you expected:
The transparent network is created.
Additional information you deem important (e.g. issue happens only occasionally):
This works fine on my Lenovo X1 Carbon, on which I've been beta testing 1.13 for many months.
Output of docker version:
Client:
 Version:      1.13.0
 API version:  1.25
 Go version:   go1.7.3
 Git commit:   49bf474
 Built:        Wed Jan 18 16:20:26 2017
 OS/Arch:      windows/amd64

Server:
 Version:      1.13.0
 API version:  1.25 (minimum version 1.24)
 Go version:   go1.7.3
 Git commit:   49bf474
 Built:        Wed Jan 18 16:20:26 2017
 OS/Arch:      windows/amd64
 Experimental: true

Output of docker info:
Containers: 3
 Running: 0
 Paused: 0
 Stopped: 3
Images: 3
Server Version: 1.13.0
Storage Driver: windowsfilter
 Windows:
Logging Driver: json-file
Plugins:
 Volume: local
 Network: l2bridge l2tunnel nat null overlay transparent
Swarm: inactive
Default Isolation: hyperv
Kernel Version: 10.0 14393 (14393.693.amd64fre.rs1_release.161220-1747)
Operating System: Windows 10 Pro
OSType: windows
Architecture: x86_64
CPUs: 4
Total Memory: 7.907 GiB
Name: SurfacePro3
ID: DTAI:B4FU:CVX6:LU7C:AYOM:CW6B:HDTQ:E4P7:B2LQ:5O4Y:7FKM:X56H
Docker Root Dir: C:\ProgramData\Docker
Debug Mode (client): false
Debug Mode (server): true
 File Descriptors: -1
 Goroutines: 16
 System Time: 2017-01-21T08:52:13.5464519-08:00
 EventsListeners: 0
Registry: https://index.docker.io/v1/
Experimental: true
Insecure Registries:
 <IP_ADDRESS>/8
Live Restore Enabled: false

I should also note that if I run the same failed command again, a "Layered Wi-Fi" (my adapter name was "Wi-Fi" and if I rename it, says "Layered ") vnet is created and I get an hnsCall error that an "Object already exists".

ping @msabansal ptal

@heaths -- can you please share the output of the following on your system?
get-vmswitch
get-netnat
get-containernetwork

I appear to be having the same or similar issue.  Here are the requested results before and after the error:
PS C:\Windows\system32> Get-ContainerNetwork

Name Id                                   Subnets           Mode SourceMac DNSServers DNSSuffix
---- --                                   -------           ---- --------- ---------- ---------
nat  27f1006d-1586-4152-9f45-e2b02feaef7f {<IP_ADDRESS>/20} NAT

PS C:\Windows\system32> get-netnat

Name                             : H27f1006d-1586-4152-9f45-e2b02feaef7f
ExternalIPInterfaceAddressPrefix :
InternalIPInterfaceAddressPrefix : <IP_ADDRESS>/20
IcmpQueryTimeout                 : 30
TcpEstablishedConnectionTimeout  : 1800
TcpTransientConnectionTimeout    : 120
TcpFilteringBehavior             : AddressDependentFiltering
UdpFilteringBehavior             : AddressDependentFiltering
UdpIdleSessionTimeout            : 120
UdpInboundRefresh                : False
Store                            : Local
Active                           : True

PS C:\Windows\system32> get-vmswitch

Name SwitchType NetAdapterInterfaceDescription
---- ---------- ------------------------------
nat  Internal

PS C:\Windows\system32> docker network create -d transparent -o com.docker.network.windowsshim.networkname=TransparentNetwork TransparentNetwork
docker : Error response from daemon: hnsCall failed in Win32: The remote procedure call failed. (0x6be)
At line:1 char:1
+ docker network create -d transparent -o com.docker.network.windowsshi ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : NotSpecified: (Error response ...failed. (0x6be):String) [], RemoteException
    + FullyQualifiedErrorId : NativeCommandError

PS C:\Windows\system32> Get-ContainerNetwork

Name          Id                                   Subnets           Mode        SourceMac DNSServers DNSSuffix
----          --                                   -------           ----        --------- ---------- ---------
Layered Wi-Fi 3bd2f366-c1d1-43e2-80fb-145b7fe6e1ae                   Transparent
nat           27f1006d-1586-4152-9f45-e2b02feaef7f {<IP_ADDRESS>/20} NAT

PS C:\Windows\system32> get-netnat

Name                             : H27f1006d-1586-4152-9f45-e2b02feaef7f
ExternalIPInterfaceAddressPrefix :
InternalIPInterfaceAddressPrefix : <IP_ADDRESS>/20
IcmpQueryTimeout                 : 30
TcpEstablishedConnectionTimeout  : 1800
TcpTransientConnectionTimeout    : 120
TcpFilteringBehavior             : AddressDependentFiltering
UdpFilteringBehavior             : AddressDependentFiltering
UdpIdleSessionTimeout            : 120
UdpInboundRefresh                : False
Store                            : Local
Active                           : True

PS C:\Windows\system32> get-vmswitch

Name          SwitchType NetAdapterInterfaceDescription
----          ---------- ------------------------------
nat           Internal
Layered Wi-Fi Private

PS C:\Windows\system32> docker network create -d transparent -o com.docker.network.windowsshim.networkname=TransparentNetwork TransparentNetwork
docker : Error response from daemon: HNS failed with error : {Object Exists} An attempt was made to create an object and the object name already existed.
At line:1 char:1
+ docker network create -d transparent -o com.docker.network.windowsshi ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : NotSpecified: (Error response ...lready existed.:String) [], RemoteException
    + FullyQualifiedErrorId : NativeCommandError

PS C:\Windows\system32>

ping @kallie-b ptal :-)

There is a fix for this in the next windows update

@msabansal you mean the Creator's update, or the next Patch Tuesday? Either way, you could probably close this issue then unless you wanted me to confirm and close after it ships.

The fix will be included in the next Patch Tuesday. And the fix addresses an issue related to the wifi adapter. It's probably fine to close this issue, but I'll remain subscribed to the thread just in case anyone has follow up questions after the fix is released.

Fix is in the pipeline, Understood.
If this is a WiFi related issue, until April 11, 2017 I should be able to set up transparent on machines that also have Ethernet adapters?  or machines that ONLY have Ethernet adapters? or have I made a poor assumption here and I should just wait for next month's patch cycle?

Thanks all! Let me close this issue for housekeeping, but feel free to continue the discussion, and let us know once it's resolved 👍

This is only a Wi-Fi Issue. Ethernet Adapter will work. Please let us know if you face any issue with Ethernet.
thanks

And, just in case you need it, here's the syntax to bind to a specific network interface:
C:> docker network create -d transparent -o com.docker.network.windowsshim.interface="Ethernet 2" TransparentNet2
(https://docs.microsoft.com/en-us/virtualization/windowscontainers/manage-containers/container-networking)

@kallie-b the 1703 update did a number on my machine, network dead, studio, and docker unusable with truly bizarre failures.  I had to do a system restore and reinstall most of my tools.
docker on my machine is now 17.05.0-ce-rc1
I can start from VS17 in the nat and debug, that is as far as I had gotten on this machine before.
I can add a network with -d transparent without error and I can launch (but not connect to) a docker started on that network.  When I docker network inspect the network it looks like the machine is there, but didn't get an address from DHCP.
Possibly what I had read originally was out of date, so I attempted to follow the process in your link above but there does not appear to be any get-containernetwork powershell anymore and there is not any additional instruction on adding mac spoofing when running on a physical host.  This command definitely existed at the point I first commented here, so something has changed, or something is still broken from the windows updates.
I am probably doing something incorrectly here, but with the variety of changes I am uncertain what.
Sorry for being a noob, but with the amount of things that went wrong here I am no longer certain if I am doing something wrong, the instructions are wrong, or the machine is still wrong.  Could someone point me in a useful direction?

Looking like I am dumb here, inside the container there is an IP and in "docker network inspect " there is no IP.  In hind sight I am guessing because that is only showing me configuration not current state and it treats DHCP as current state?  If this is normal then my only outstanding question is if "get-containernetwork" is supposed to have been removed or not.

@dirething -- So let me make sure I understand your machine state/issue here.

You're using Windows 10, with Docker CE (Docker CE install instructions are here), and all of the latest Windows updates
After installing Docker CE on your machine, you switched to Windows Containers
Now you're able to start Docker, but your containers do not have network connectivity.

A question:

Are you seeing network for all containers (i.e. containers created on the default 'nat' network), or just for containers connected to a transparent network?

@kallie-b
yes, yes, & they have connectivity now
In the first attempts after updating from patch Tuesday neither nat or transparent worked, I started to notice a lot of other things amiss outside docker, eventually after doing a system restore and reinstalling to 17.05.0-ce-rc1, hyper-v and containers, nat worked, but transparent showed no address, or so I thought.
"docker network inspect TransparentNetwork" says there isn't an address on my transparent network container, but there is if you run an ipconfig /all from inside docker exec, at least after a minute or two it would seem.  if this is normal, so be it, but I was unsuccessful at finding an example to compare to when using DHCP.
In trying to follow your instructions in your earlier reply (https://docs.microsoft.com/en-us/virtualization/windowscontainers/manage-containers/container-networking) I noticed I no longer had the"get-containernetwork" powershell.  This was definitely there before as I had to use it several times to clean up when I was first trying to create the transparent network.
If that is supposed to be gone in this version and inspect is not supposed to show you DHCP addresses then possibly I have it all working correctly at this point and I would thank you for your time and apologize for not catching on faster on my own.  If these outcomes are not expected any suggestion on how to proceed in correcting the issue would be appreciated.
Hopefully at this point it is just my misunderstanding

@dirething -- apologies for the delayed reply. I don't believe the behavior you're describing is normal. If you have a transparent network on your host, "TransparentNetwork", and you create a container to be attached to that transparent network, you should see the container listed as an endpoint when you do "docker network inspect TransparentNetwork."
Specifically, if you follow these commands:
C:\> docker network create -d transparent TransparentNetwork
C:\> docker run --network TransparentNetwork microsoft/nanoserver
C:\> docker network inspect TransparentNetwork

You should see the ID of the container listed as an endpoint in the output of "docker network inspect TransparentNetwork."
Is that not the case for you?

@kallie-b  No worries, thanks for putting up with my confusion.
Running your commands (but with a different network name since I already had that name)
It shows in the inspect, but without an address:
PS C:\WINDOWS\system32> docker network inspect TransparentNetwork1
[
    {
        "Name": "TransparentNetwork1",
        "Id": "6f5b3db1ed1df2eb6f2d780c3f5335c2249dc31a6cd43abec4d13f7bad4e944d",
        "Created": "2017-04-28T14:16:10.355859-04:00",
        "Scope": "local",
        "Driver": "transparent",
        "EnableIPv6": false,
        "IPAM": {
            "Driver": "windows",
            "Options": {},
            "Config": [
                {
                    "Subnet": "<IP_ADDRESS>/0",
                    "Gateway": "<IP_ADDRESS>"
                }
            ]
        },
        "Internal": false,
        "Attachable": false,
        "Ingress": false,
        "Containers": {
            "71662d5871b5c4605290aedd3a352a5d659afc6c39dc9427ef86d5de3951103b": {
                "Name": "sharp_jackson",
                "EndpointID": "9b99ae870b72a667c5e76e0dbf9c6e08a7ec7f7edc8a5c4dd61607bf03b1d535",
                "MacAddress": "00:15:5d:50:d8:a1",
                "IPv4Address": "",
                "IPv6Address": ""
            }
        },
        "Options": {
            "com.docker.network.windowsshim.hnsid": "fb13d025-b41e-4d72-a8ad-00e0a7887e1a"
        },
        "Labels": {}
    }
]

but if I connect to it interactively and check the ip from the container's point of view it has one:
Microsoft Windows [Version 10.0.14393]
(c) 2016 Microsoft Corporation. All rights reserved.

      : Yes
   Autoconfiguration Enabled . . . .    : Disabled

C:\>

this is the part I am guessing might possibly be normal and I have just misunderstood
the disappearance of the containernetwork powershell commands still confuses me, but I now see others having this problem like: https://github.com/docker/for-win/issues/679 so if the inspect result is as expected I can probably leave you alone.

Hello Everyone,
      I am very new to docker on WIndows, I have tried everything i can think of and searched google till I am blue in the face.

Here is how I tried to add a network to my docker for windows:
PS C:\Users\Administrator> docker network create -d transparent -o com.docker.network.windowsshim.interface="Ethernet 3"
tlan1
Error response from daemon: plugin "transparent" not found
PS C:\Users\Administrator> get-vmswitch
Name               SwitchType NetAdapterInterfaceDescription

nat                Internal
DockerNAT          Internal
Layered_Ethernet 2 External   Intel(R) Ethernet Connection (2) I219-LM
PS C:\Users\Administrator> get-netnat
Name                             : Hec9ffadc-03ab-46ca-b0c2-e8977d093b52
ExternalIPInterfaceAddressPrefix :
InternalIPInterfaceAddressPrefix : <IP_ADDRESS>/20
IcmpQueryTimeout                 : 30
TcpEstablishedConnectionTimeout  : 1800
TcpTransientConnectionTimeout    : 120
TcpFilteringBehavior             : AddressDependentFiltering
UdpFilteringBehavior             : AddressDependentFiltering
UdpIdleSessionTimeout            : 120
UdpInboundRefresh                : False
Store                            : Local
Active                           : True
Name                                                             Id                                   Subnets

nat                                                              ec9ffadc-03ab-46ca-b0c2-e8977d093b52 {<IP_ADDRESS>/20}
DockerNAT (1)                                                    0590a357-1ac2-4d0e-901c-e1abb2f3f01a {<IP_ADDRESS>/20}
e6b08d31c3e77fa8b64ce15dd543ac972a6aa9d98b62d2ea43f67baa55bf36c0 5806fad2-95b5-42db-a0db-4407dc52b74e {}
I am confused and lost not sure what to do from here. Any help would be greatly appreciated.
Thanks,
Michael

@nexusguy59 Try updating docker. Works fine on latest docker:
PS C:\Windows\system32> docker version
Client:
Version:      18.03.1-ce
API version:  1.37
Go version:   go1.9.5
Git commit:   9ee9f40
Built:        Thu Apr 26 07:12:48 2018
OS/Arch:      windows/amd64
Experimental: false
Orchestrator: swarm
Server:
Engine:
Version:      18.03.1-ce
API version:  1.37 (minimum version 1.24)
Go version:   go1.9.5
Git commit:   9ee9f40
Built:        Thu Apr 26 07:21:42 2018
OS/Arch:      windows/amd64
Experimental: false
PS C:\Windows\system32> docker network create -d transparent -o com.docker.network.windowsshim.interface="Ethernet" tlan1
9d63589cf0df37351f04ec4a0d5f8fa46afa9952c647a60a53a5cfeeaab8dc63

Similar Issue Cannot create Transparent Network

docker version:
C:\Users\Administrator\Desktop>docker info
Containers: 0
Running: 0
Paused: 0
Stopped: 0
Images: 0
Server Version: 18.09.2
Storage Driver: overlay2
Backing Filesystem: extfs
Supports d_type: true
Native Overlay Diff: true
Logging Driver: json-file
Cgroup Driver: cgroupfs
Plugins:
Volume: local
Network: bridge host macvlan null overlay
Log: awslogs fluentd gcplogs gelf journald json-file local logentries splunk syslog
Swarm: inactive
Runtimes: runc
Default Runtime: runc
Init Binary: docker-init
containerd version:<PHONE_NUMBER>f7fe2f4e74d43e2fc7ccd237edcbce
runc version: 09c8266bf2fcf9519a651b04ae54c967b9ab86ec
init version: fec3683
Security Options:
seccomp
Profile: default
Kernel Version: 4.9.125-linuxkit
Operating System: Docker for Windows
OSType: linux
Architecture: x86_64
CPUs: 8
Total Memory: 22.99GiB
Name: linuxkit-00155d010224
ID: KTFL:YSU3:VMIN:SYCT:74JV:6LUM:UCRH:DYD7:H6IF:PPVO:WO4S:HDI4
Docker Root Dir: /var/lib/docker
Debug Mode (client): false
Debug Mode (server): true
File Descriptors: 22
Goroutines: 46
System Time: 2019-06-20T22:01:07.3925473Z
EventsListeners: 1
Registry: https://index.docker.io/v1/
Labels:
Experimental: false
Insecure Registries:
<IP_ADDRESS>/8
Live Restore Enabled: false
Product License: Community Engine
support   macvlan commd


Policy Server local

While exploring both master branch and UMA branch I found it really hard to understand the schema for client policy but once I got the hang of it, was really impressed. If you intend to make UMA version main branch some day, please provide documentation on explaining schema.
What I liked about PolicyServer.Local was the simple version of policy schema. However it was intended to keep authorization in application itself. What's great about Policy Server1 is that it allows for centralizing authorization.
Is it possible to have version of Policy Server1 which extend the policy Server local version of schema?

If you intend to make UMA version main branch some day, please provide documentation on explaining schema.

Yes and Yes

Is it possible to have version of Policy Server1 which extend the policy Server local version of schema?

i'm really not sure to understand what you ask.

see #4

Never mind on the last part of my quesiton. I think the UMA version should cover my ask.


WSS method blockSubscribe throws "Invalid/Unspported params for blockSubscribe."

I am following the example given here about the WSS method of blockSubscribe, to get data about the news blocks and the transactions in them.
Below is my implementation in JS -
socket.addEventListener("open", () => {
  const subscribeMessage = {
    jsonrpc: "2.0",
    id: "1",
    method: "blockSubscribe",
    params: [{ filter: "all" }],
  };

  console.log("WSS stream started");
  const messageString = JSON.stringify(subscribeMessage);
  socket.send(messageString);
});

Response I get -
  [Symbol(kType)]: 'message',
  [Symbol(kData)]: '{"id":"1","jsonrpc":"2.0","error":{"code":-32602,"message":"Invalid/Unspported params for blockSubscribe."}}'

I am using the alchemy mainnet RPC for creating this WSS connection.

  const subscribeMessage = {
    jsonrpc: "2.0",
    id: "1",
    method: "blockSubscribe",
    params: ["all"],
  };


Add a new CustomIsotope class.

class CustomIsotope:
   symbol: str
   spin: int
   natural_abundance: float
   gyromagnetic_ratio: float
   quadrupole_moment: float
   atomic_number: int

[ ] Check serialization and reading custom isotopes.

Completed by PR #257


su inside tmux window: pam_authenticate: Error in service module

Open tmux or screen, then su, and I get: Error in service module. Does it happen to you as well? This is my su pam module:
# Account management.
account sufficient pam_unix.so

# Authentication management.
auth sufficient pam_rootok.so
auth required pam_wheel.so
auth required pam_tally.so
auth sufficient pam_unix.so  likeauth
auth required   pam_deny.so

# Password management.
password requisite pam_unix.so nullok sha512

# Session management.
session required pam_unix.so
session optional pam_xauth.so xauthpath=/nix/store/d6qd7hdifbkl1a2ga5z8xhlkr3qfnbnh-xauth-1.0.9/bin/xauth systemuser=99

Closing as I couldn't find any solution and any other distro uses use_uid.


Fix staging and preview deployments

VPN connection is required for stating playground

Created an SRE ticket for removing the VPN requirement.


Kotlin 1.9.10 causes Kover regression

Describe the bug
When Kover encounters a serializable data class containing a list property, it mistakenly indicates instructions are not covered.  The same source code compiled with 1.8.10 does not report any missing instructions.
Errors
See attached Kover report below for 1.9.10

Expected behavior
The report should indicate 100% coverage result.
Reproducer
See https:gitlab.com/pmr/kover-serialization-issue1
Reports
See above.
Environment

Kover Gradle Plugin version: 0.7.3
Gradle version: 8.2
Kotlin project type: Kotlin/JVM
Coverage Toolset (if customized in build script): Kover
Other context important for this bug: Kotlin 1.9.10

I cannot say definitively that this is a Kover bug.  Could very easily be a Serialization bug, which I believe that it is but I'm loathe to complain to the Serialization team without some evidence supplied by the Kover team. But Kover is where the failure occurs so I must start here.

+1

@shanshin , hi! Could you tell about approximate time for bug fix?


Generate filename for formula from packager config

Fixes #973
Context
Generate filename for formula from packager config

Checklist

[ ] Review Contribution Guidelines.
[ ] Make sure all contributed code can be distributed under the terms of the
Apache License 2.0, e.g. the code was written by
you or the original code is licensed under a license compatible to Apache License 2.0.
[ ] Update documentation when applicable.

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

Hi, @aalmiray I have made the necessary changes.

Thank you! 😁

Thanks @aalmiray

Released in v1.3.0 -> https://github.com/jreleaser/jreleaser/releases/tag/v1.3.0


GeoJson file type for obsSegmentations

User story
Should be able to load segmentations from geoJSON.

See https://github.com/vitessce/vitessce/blob/df0c5cea1d4fa156697849aa5abcbdf6242aeaf0/src/loaders/CellsGeoJsonLoader.js (from https://github.com/vitessce/vitessce/pull/1150) and https://github.com/vitessce/vitessce/pull/946


Adapter Development Walkthrough is not updated for the new repo structure

The instructions of the Mixer Adapter Development Walkthrough are not updated to match the new location of the Mixer within the Istio repo.
E.g. BUILD file for mysampleadapter (in step 1) should have:
"//mixer/pkg/adapter:go_default_library",
"//mixer/template/metric:go_default_library",

Instead of:
"//pkg/adapter:go_default_library",
"//template/metric:go_default_library",

Hi Yossi and Etai,
Any of you guys working on this issue ? Let me know if that is the case, I am also working on similar PR to update the guide and walk-though doc.

Hi, I began updating the walkthrough while going through the steps there. If you already did it feel free to close this issue as resolved by your PR.
Which PR is it?

https://github.com/istio/istio/pull/1576
On Mon, Nov 6, 2017 at 9:38 PM, Yossi Mesika<EMAIL_ADDRESS>wrote:

Hi, I began updating the walkthrough while going through the steps there.
If you already did it feel free to close this issue as resolved by your PR.
Which PR is it?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/istio/istio/issues/1545#issuecomment-342380923, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AK6xE00TAqECWxPnledGCwXEelfpPvtNks5sz-zGgaJpZM4QTNU0
.

--
Thanks,
-SG

I have not tested it, I too have to go through the steps and see if things will work with mono repo.

Resolved by #1576


Please add a screen shot

I'd like to add this to awesome-zsh-plugins, but I prefer to add themes with screen shots so that users can see what they look like without having to install them.

Will do it when is ready 👍 I'll keep you posted

Cool, thanks!

Added #2ea8f7d


Using different icons for different powertoy wake status

Description of the new feature / enhancement
Is it possible to use different icons to indicate different status of powertoy wake? It's an useful feature but it's easy to forget if you are still indefinitely waking the computer or not.
Scenario when this would be used?
When forget to turn indefinite waking off. I cannot tell if the feature is on by looking at the icon, always have to right click which is annoying.
Supporting information
No response

Duplicate of #11996

Thanks for your suggestion! This issue is a duplicate.
I'm linking this issue to #11996 to centralize the discussion thread, please go to that thread for discussion.
Thanks for your help to make PowerToys a better piece of software!


types not working

Hi
I'm building a table with dynamically added headers, widths and column types. Generated headers, widths and relevant types are pushing into arrays (headers, widths, cols) and passed to jexcel:
$('#mytable').jexcel({ 	minDimensions:[ncols,10],     	colHeaders: headers,     	colWidths: widths, 	columns : cols 	});
while headers and widths are displayed correctly, the types do not seem to be working. Some of the fields are dropdowns and checkboxes, but they are not being rendered.
Any ideas as to what I'm doing wrong?
thanks in advance.

issue solved, was not a jexcel issue

Great ;)


DOC: add a "big picture" roadmap

Follow-up to gh-9489, it splits things into a big picture roadmap (idea: 5-10 of our top prios) and a detailed roadmap (which is what we had before).
From the seven ideas currently listed on the "big picture" roadmap, only Support for distributed arrays and GPU arrays is new. The other ones are all present on the detailed roadmap or issues.  Additions, criticism, questions etc. all very welcome of course, I'm sure we can improve on this.

I really like the idea of having a detailed roadmap. Would this also be supposed to help potential contributors who are interested in adding features but who don't know where to start?I think it would be nice to discuss some ideas for the different modules to get a better picture of the priorities (not sure if here or in separate issues per module?).
A couple of questions / ideas came to my mind for scipy.stats:

If we want to add general ideas for contributors: implementing (well-kown) distributions is always welcome I guess.
What about issues that are considered high priority? (Maybe issues related to mannwithneyu?. This would imply regular maintenance of the roadmap toegther with a new release)
what about mstats (in particular, documentation / consistency with stats). Warren's comment in #9395 just reminded me about this.

I agree with @chrisb83 's comments on detailed roadmaps for sub-modules. Having a good idea of priorities and more specific guidance on where to start would be helpful for those who haven't contributed before and for those (like me) who've done a couple commits but lack the knowledge and experience of the members.

I really like the idea of having a detailed roadmap. Would this also be supposed to help potential contributors who are interested in adding features but who don't know where to start?I think it would be nice to discuss some ideas for the different modules to get a better picture of the priorities (not sure if here or in separate issues per module?).

Yes, that was indeed one of the main ideas for the roadmap that we've had for a while. As long as we don't make it significantly more detailed than what's there now (we can use issues labelled enhancement for that) then having a clear list of prios per submodule would be great.

If we want to add general ideas for contributors: implementing (well-kown) distributions is always welcome I guess.

+1

What about issues that are considered high priority? (Maybe issues related to mannwithneyu?. This would imply regular maintenance of the roadmap toegther with a new release)

I would suggest only if they're structural, not single issues for one function. Or if we do that, maybe super short: "high prio issues are for mannwhitneyu (gh-xxxx), ... and ...

What about mstats (in particular, documentation / consistency with stats). Warren's comment in #9395 just reminded me about this.

That got a lot better over time, but indeed there's still quite some work to do. That fits well on the roadmap I'd say.

If there are more comments on the "big picture" part, by tomorrow would be very useful. Reason: @scopatz is hosting a webinar and he invited me to talk about the SciPy roadmap this Friday (details, register). By then we hope to get a brochure out as well, similar to the ones for other projects on  https://www.quansight.com/projects.
To recap, the 7 listed ideas in order of prio are:

Evolve BLAS and LAPACK support
Sparse arrays
Fourier transforms
Support for distributed arrays and GPU arrays
Improve benchmark system for optimize
Linear programming enhancements
Improve source builds on Windows

Thanks for putting this in @rgommers!

Any other comments? I'm thinking of merging this at the start of the new year.

One more suggestion for stats: improve statistical tests (p-value calculation / alternative hypothesis). Here R often has better functionality.
Examples:

exact two-sided KS test (Marsaglia et al)
two-sided vs one-sided tests (Wilcoxon)

One more suggestion for stats: improve statistical tests (p-value calculation / alternative hypothesis). Here R often has better functionality.

Thanks Christoph, added.

Any other comments? I'm thinking of merging this at the start of the new year.

Okay, in it goes. We can open new issues/PR or discuss on the mailing list for the rest. Except the ndimage interpolation modes discussion, let's continue that here. Needs @stefanv's input, we're tweaking his text (what there now is certainly an improvement over the old text though).


The sample throws an exception after upgrading all CoreWCF packages to the latest versions.

Which sample is the bug for
I use the NetCoreServer sample.
Describe the bug
The sample throws an exception after upgrading all CoreWCF packages to the latest versions.
To Reproduce
Steps to reproduce the behavior:

Get clean code from GitHub
Upgrade all CoreWCF packages to the latest version

Run the sample
Error:

Error message: System.InvalidOperationException: 'Unable to resolve service for type 'Microsoft.AspNetCore.Authentication.IAuthenticationSchemeProvider' while attempting to activate 'Microsoft.AspNetCore.Authentication.AuthenticationMiddleware'.'
Stack trace:
   at Microsoft.Extensions.Internal.ActivatorUtilities.ConstructorMatcher.CreateInstance(IServiceProvider provider) in /_1/microsoft.extensions.activatorutilities.sources/3.1.23-servicing.22123.2/contentFiles/cs/netstandard1.0/ActivatorUtilities.cs:line 391
   at Microsoft.Extensions.Internal.ActivatorUtilities.CreateInstance(IServiceProvider provider, Type instanceType, Object[] parameters) in /_1/microsoft.extensions.activatorutilities.sources/3.1.23-servicing.22123.2/contentFiles/cs/netstandard1.0/ActivatorUtilities.cs:line 90
   at Microsoft.AspNetCore.Builder.UseMiddlewareExtensions.<>c__DisplayClass4_0.<UseMiddleware>b__0(RequestDelegate next) in /_/src/Http/Http.Abstractions/src/Extensions/UseMiddlewareExtensions.cs:line 92
   at Microsoft.AspNetCore.Builder.ApplicationBuilder.Build() in /_/src/Http/Http/src/Builder/ApplicationBuilder.cs:line 103
   at Microsoft.AspNetCore.Builder.MapWhenExtensions.MapWhen(IApplicationBuilder app, Func`2 predicate, Action`1 configuration) in /_/src/Http/Http.Abstractions/src/Extensions/MapWhenExtensions.cs:line 45
   at CoreWCF.Channels.ServiceModelHttpMiddleware.BuildBranch() in /_/src/CoreWCF.Http/src/CoreWCF/Channels/ServiceModelHttpMiddleware.cs:line 170
   at CoreWCF.Channels.ServiceModelHttpMiddleware.EnsureBranchBuilt() in /_/src/CoreWCF.Http/src/CoreWCF/Channels/ServiceModelHttpMiddleware.cs:line 64
   at CoreWCF.Channels.ServiceModelHttpMiddleware.ServiceBuilderOpenedCallback(Object sender, EventArgs e) in /_/src/CoreWCF.Http/src/CoreWCF/Channels/ServiceModelHttpMiddleware.cs:line 73
   at CoreWCF.Channels.CommunicationObject.OnOpened() in /_/src/CoreWCF.Primitives/src/CoreWCF/Channels/CommunicationObject.cs:line 503
--- End of stack trace from previous location ---
   at CoreWCF.Configuration.WrappingIServer.<StartAsync>d__9`1.MoveNext() in /_/src/CoreWCF.Primitives/src/CoreWCF/Configuration/WrappingIServer.cs:line 45
   at Microsoft.AspNetCore.Hosting.WebHost.<StartAsync>d__27.MoveNext() in /_/src/Hosting/Hosting/src/Internal/WebHost.cs:line 160
   at Microsoft.AspNetCore.Hosting.WebHostExtensions.<RunAsync>d__5.MoveNext() in /_/src/Hosting/Hosting/src/WebHostExtensions.cs:line 111
   at Microsoft.AspNetCore.Hosting.WebHostExtensions.<RunAsync>d__5.MoveNext() in /_/src/Hosting/Hosting/src/WebHostExtensions.cs:line 145
   at Microsoft.AspNetCore.Hosting.WebHostExtensions.<RunAsync>d__4.MoveNext() in /_/src/Hosting/Hosting/src/WebHostExtensions.cs:line 95
   at Microsoft.AspNetCore.Hosting.WebHostExtensions.Run(IWebHost host) in /_/src/Hosting/Hosting/src/WebHostExtensions.cs:line 69
   at NetCoreServer.Program.Main(String[] args) in D:\code\CoreWCF-samples\Scenarios\Getting-Started-with-CoreWCF\NetCoreServer\Program.cs:line 15

Expected behavior
The sample should work with the latest CoreWCF versions, or could anyone please give me some ideas about how to get it work? I can then contribute a PR to fix the sample.
Repo environment:

OS: Windows
Architecture: x64
.NET Version: 3.1 and 6.0
Run from VS 2022

In https://github.com/CoreWCF/samples/blob/main/Scenarios/Getting-Started-with-CoreWCF/NetCoreServer/Startup.cs, the exception will go away if I add two more lines to the ConfigureServices:
 public void ConfigureServices(IServiceCollection services)
    {
        services.AddAuthentication(); // add this
        services.AddAuthorization(); // and this

        // Enable CoreWCF Services, enable metadata
        // Use the Url used to fetch WSDL as that service endpoint address in generated WSDL
        services.AddServiceModelServices()
                .AddServiceModelMetadata()
                .AddSingleton<IServiceBehavior, UseRequestHeadersForMetadataAddressBehavior>();
    }

I don't know if adding them will break anything. Will do more testing.


Fix a typo

get_output_metadate_impl -> get_output_metadata_impl

Thanks @caffeinism! Have you maybe filed the CLA required for contributing to Model Navigator? Here is relevant section in documentation: https://github.com/triton-inference-server/model_navigator/blob/main/CONTRIBUTING.md#contributor-license-agreement-cla


Support decorators for @action

Target components
action_server, actions
Description
i.e.: As something as:
@my_decorator
@action
def any_action(value: str) -> str:
    ...

is the same as:
def any_action(value: str) -> str:
    ...

any_action = action(any_action) # at this point we save the reference to the function, so, it doesn't work.
any_action = my_decorator(any_action)

and if it was inverted it'd be:
def any_action(value: str) -> str:
    ...

any_action = my_decorator(any_action)
any_action = action(any_action) # The signature of the my_decorator won't be correct for introspecting.

Describe the solution you'd like to see
We could maybe make it work by not storing the reference and just storing the module/function name to get for calling but still introspecting on the given one (but it does have some caveats too).
Describe alternatives you've considered
No response

Note: investigate if functools.wraps adds info on the wrapper so that the original one can be gotten for introspection.

This issue has been moved here, under Sema4AI/actions repository.


[improvement](column reader) lazy load indices

Proposed changes
Issue Number: close #xxx
Currently when reading column data, all types of indice are read even if they are not actually used, this PR implements lazy load of indices.
Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

run buildall

run buildall

run buildall


Add snk file to System.IO.Packaging,DocumentFormat.OpenXml and PowerTools .Strong-name signed assemblies must specify a public key in their InternalsVisibleTo declarations.

Hi,
I have add latest OpenXml SDK (2.6) and PowerTools 4.0 in my project.I have added snk file to my project.I got Unable to emit assembly error.So i try to add snk file for System.IO.Packaging,DocumentFormat.OpenXml and PowerTools . For System.IO.Packaging there is no problem.But For DocumentFormat.OpenXml,After adding snk file i got below error.
Friend assembly reference 'SdbBuilder' is invalid. Strong-name signed assemblies must specify a public key in their InternalsVisibleTo declarations.
Friend assembly reference 'ofapiTest' is invalid. Strong-name signed assemblies must specify a public key in their InternalsVisibleTo declarations.
File name is (ofapi.cs)
How to solve above error.
How to add snk file to all 3 projects.I need dll with stong named type project.
Please help me to resolve the issue.

@Ganesan-Chandran Rather than try to add the DLLs to your project where you need strong-named type project, can you simply add links to the source modules, and compile all modules as though they are part of your project directly?

@EricWhiteDev I'm running into the same issue.  I'm willing to try the solution you suggested, but could you briefly describe how that's done?  I know how to add other projects into my VS solution, but as far as I know that still compiles into separate DLLs.  How can I link in the way you describe (so that all the OpenXML stuff ends up in my main DLL)?


Support listening on Unix sockets

Currently we only support listening on IPs, but not on Unix sockets. Might be interesting if Aerys is deployed behind Nginx or another reverse proxy.

I generally like the idea.
I am wondering though how this will work with multiple binding. SO_REUSEPORT won't work here.
So only option is to force usage of socket transfer then.
Additionally, how will the signature on Host::expose() look like then? Host::expose(string $address, int $port = 0) and require the port being non-zero for anything not being a path (and zero for paths)?
That way it should be pretty trivial, except that we have to special case it within CommandClient::importServerSockets (in order to use so_reuseport when available on tcp sockets, but not on unix sockets - ultimately so_reuseport is the fastest way to use).

Either 0 or null for the port, yes.

https://github.com/amphp/uri/issues/9
Please don't forget about this

@umbri That's a separate issue.


Removes the non-gitea options

We've consolidated to using Gitea across the board. This codifies that
and removes the number of variations we need to test & validate. It also
simplifies the experience for the instructor, since they're not
presented with unclear configuration options.
This also adds a spec for puppetize, since its configuration is slightly
different from the other virtuals.
TRAINTECH-1445 #resolved #time 2h

@binford2k It makes sense to me.

I did, but I'd forgotten somehow to commit the change adding Gitea to the plugin list! Thanks for reminding me.


text-embedding-ada-002 for embeddings

openai says to use "text-embedding-ada-002" for all text embeddings. It's very cheap. gpt3.5/4 are 1000x more expensive  tokenizer_model: str = "text-embedding-ada-002"

no. We always use the text-embedding-ada-002 model for embedding. See the OpenAIEembeddings class. You can see that model: str = "text-embedding-ada-002".
        embeddings: Embeddings = OpenAIEmbeddings(
            client=openai.Embedding,
            openai_api_key=openai_api_key,
        )

Okay. Don't want to use ada-002 as tokenizer?


Automate Testing Infrastructure

The goal here is to automate the following using docker-compose:

Start Keycloak and Kong's db, wait till it's ready, run the db migration (uncomment the command in docker-compose.yml, start Kong and run setup.py. The source code in mounted into the container, so you need only to restart Kong's container to test your changes.

This way the tests and infrastructure they run on can be executed using a single command.

Got the build working with one command. How are the tests run once the services are running and setup.py has been run?

As far as I could tell, there are no tests to run (yet) after setup.py has been run.
For unit tests, I created a docker image that can run the unit tests. That way, all developers can run them in exactly the same environment (these were crashing on my Mac, previously). PR should be in by the end of the day.