using an old config file and not accepting updates throws panic error

If you have a folder that already has a ruby theme gem config file, running a command will prompt that the config file is out of date. If you say no, then there is a panic runtime error

Raw
➜  Simple git:(master) ✗ theme replace
Looks like your configuration file is out of date. Upgrading to default environment 'development'
Compare changes to configuration:
Before:
 ---
:api_key: 10c76ab9b923a8b91f77be3a85b660b7
:password: b004e796b1181996ae8cb235da73f1a0
:store: jtgrenz.myshopify.com
:theme_id:
:whitelist_files:
- directoryToUpload/
- importantFile.txt
:ignore_files:
        #- config/settings.html
- config.yml

After:
 development:
  access_token: ""
  store: ""
  bucket_size: 40
  refill_rate: 2
  concurrency: 2

Does this look correct? (y/n)
n
panic: runtime error: invalid memory address or nil pointer dereference
[signal 0xb code=0x1 addr=0x10 pc=0xe1e72]

goroutine 10 [running]:
net/http.(*Client).doFollowingRedirects(0x0, 0xc20801ec30, 0x480c10, 0x0, 0x0, 0x0)
	/usr/local/Cellar/go/1.4.2/libexec/src/net/http/client.go:304 +0x62
net/http.(*Client).Do(0x0, 0xc20801ec30, 0x0, 0x0, 0x0)
	/usr/local/Cellar/go/1.4.2/libexec/src/net/http/client.go:174 +0xa4
github.com/Shopify/themekit.ThemeClient.query(0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, ...)
	/Users/csaunders/development/golang/src/github.com/Shopify/themekit/theme_client.go:230 +0x28b
github.com/Shopify/themekit.func·020()
	/Users/csaunders/development/golang/src/github.com/Shopify/themekit/theme_client.go:95 +0x5e
created by github.com/Shopify/themekit.ThemeClient.AssetList
	/Users/csaunders/development/golang/src/github.com/Shopify/themekit/theme_client.go:112 +0x18b

goroutine 1 [chan receive]:
main.main()
	/Users/csaunders/development/golang/src/github.com/Shopify/themekit/cmd/theme/main.go:127 +0x3aa

goroutine 5 [runnable]:
github.com/Shopify/themekit.func·002()
	/Users/csaunders/development/golang/src/github.com/Shopify/themekit/error_reporter.go:50 +0x52
created by github.com/Shopify/themekit.SetErrorReporter
	/Users/csaunders/development/golang/src/github.com/Shopify/themekit/error_reporter.go:56 +0x69

goroutine 7 [chan send]:
github.com/Shopify/themekit.func·003()
	/Users/csaunders/development/golang/src/github.com/Shopify/themekit/error_reporter.go:62 +0x55
created by github.com/Shopify/themekit.func·004
	/Users/csaunders/development/golang/src/github.com/Shopify/themekit/error_reporter.go:63 +0x73

goroutine 8 [chan receive]:
github.com/Shopify/themekit.func·025()
	/Users/csaunders/development/golang/src/github.com/Shopify/themekit/theme_client.go:189 +0x9a
created by github.com/Shopify/themekit.ThemeClient.Process
	/Users/csaunders/development/golang/src/github.com/Shopify/themekit/theme_client.go:198 +0x1d8

goroutine 9 [chan receive]:
github.com/Shopify/themekit/commands.func·002()
	/Users/csaunders/development/golang/src/github.com/Shopify/themekit/commands/common.go:142 +0xbf
created by github.com/Shopify/themekit/commands.mergeEvents
	/Users/csaunders/development/golang/src/github.com/Shopify/themekit/commands/common.go:148 +0xd8

goroutine 11 [runnable]:
github.com/Shopify/themekit/commands.drainErrors(0xc20803f2c0)
	/Users/csaunders/development/golang/src/github.com/Shopify/themekit/commands/common.go:127
created by github.com/Shopify/themekit/commands.Replace
	/Users/csaunders/development/golang/src/github.com/Shopify/themekit/commands/replace.go:28 +0x20c

goroutine 12 [runnable]:
github.com/Shopify/themekit/commands.removeAndUpload(0xc20803f260, 0xc20803f140)
	/Users/csaunders/development/golang/src/github.com/Shopify/themekit/commands/replace.go:53
created by github.com/Shopify/themekit/commands.Replace
	/Users/csaunders/development/golang/src/github.com/Shopify/themekit/commands/replace.go:29 +0x236

goroutine 13 [runnable]:
main.func·001()
	/Users/csaunders/development/golang/src/github.com/Shopify/themekit/cmd/theme/main.go:110
created by main.main
	/Users/csaunders/development/golang/src/github.com/Shopify/themekit/cmd/theme/main.go:126 +0x382

@csaunders

The YAML parser I'm using isn't compatible with the way Ruby wants it to be formatted. A work around for this is to simply fix up your configuration by removing the prefixed : and it should then be able to migrate your configuration over.
I'm not sure if it's worth submitting a patch to the YAML library for this. I am pretty sure that's not part of the spec. Could it be that Ruby takes keys that :look_like_this: and translates them into symbols?

Seems to be a ruby feature for sure. Running it through http://www.yamllint.com/
---
:api_key: < API KEY >
:password: < API PASSWORD>
:store: jtgrenz.myshopify.com
:theme_id: 12403338
:whitelist_files:
- directoryToUpload/
- importantFile.txt
:ignore_files:
        #- config/settings.html
- config.yml

Becomes :
---
? !ruby/symbol api_key
: < API KEY >
? !ruby/symbol ignore_files
:
  - config.yml
? !ruby/symbol password
: < API PASSWORD>
? !ruby/symbol store
: jtgrenz.myshopify.com
? !ruby/symbol theme_id
: 12403338
? !ruby/symbol whitelist_files
:
  - directoryToUpload/
  - importantFile.txt

but passes as valid YAML. The old theme gem has this style setup as its demos https://github.com/Shopify/shopify_theme#the-configyml-file So I'm not sure how backwards compatible we want to be. If themekit is designed to try and convert an existing configuration to the new model, it should fail in most cases if it can't handle the conversion from ruby symbols. I reckon most people using the gem would have copy and pasted the sample.

As a result of https://github.com/Shopify/themekit/pull/95 this will no longer throw the error. The only thing missing is to perhaps prompt the user to update their configuration by hand.
If that is sufficient, please close the issue.


removing go-dockerclient

Took first stab at #227. Leaving as do not merge, because I need some sanity checks.

👍


Shell Elements are not readable

Hi Alex,
Pyansys currently ignores SHELL elements from the .RST file.
Regards,
Abhi

Could you please attach the result file and/or specify which shell element are being ignored?  I've been able to read in SURF154 elements with no problems.

Thanks for your response. I am trying to plot nodal stress results with a
model that contains shell181 elements. Rest of the element do get plotted
fine, while the shell elements are completely ignored. I am using Ansys
v.18.2
Do let me know if you are able to replicate the issue.
Regards,
Abhi
On 27 Feb. 2018 6:06 pm, "Alex Kaszynski"<EMAIL_ADDRESS>wrote:
Could you please attach the result file and/or specify which shell element
are being ignored? I've been able to read in SURF154 elements with no
problems.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/akaszynski/pyansys/issues/15#issuecomment-368780354,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AXa6Vw9V_mvNnSIvDppj3AsBlEjv63e6ks5tY7eegaJpZM4SQU6H
.

I've yet to program an interface for SHELL181, but as the element ordering is the same as SURF154, it shouldn't be too hard to add.  I'll update the code so that those elements are accessible to pyansys as well.

Thanks mate!
I suggest that you target the default element types used by Ansys WB (for
1D,2D,3D). This would increase the reach of pyansys.
If you could throw some light if in the future, with respect to nodal
results, you would be giving access to: the averaged, unaveraged on
material, unaveraged on real constant, top/bottom solution option for shell
elements. This would be very useful indeed.
Regards,
Abhi
On 28 Feb. 2018 8:47 pm, "Alex Kaszynski"<EMAIL_ADDRESS>wrote:

I've yet to program an interface for SHELL181, but as the element ordering
is the same as SURF154, it shouldn't be too hard to add. I'll update the
code so that those elements are accessible to pyansys as well.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/akaszynski/pyansys/issues/15#issuecomment-369201259,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AXa6VwMw8Q8srTwgEEeAZM8WsOW5qJ4pks5tZS7CgaJpZM4SQU6H
.

I'm about ready to go for SHELL181, but it would be great to have an APDL script to run and compare against.  Do you have one?

pyansys now reads SHELL181.
Could you let me know what the default elements are for workbench?  I don't usually use workbench.

Closing soon unless I hear back.

Sorry for the delay. I will send the default elements for workbench today.
-Abhi
On 7 Mar. 2018 10:12 pm, "Alex Kaszynski"<EMAIL_ADDRESS>wrote:

Closing soon unless I hear back.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/akaszynski/pyansys/issues/15#issuecomment-371119523,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AXa6V4uNygIkNpmjI62E5Hks1UuGCPhDks5tb86agaJpZM4SQU6H
.

Hi Alex,
Here is a list of common first and second order elements used by WB for
structural analysis:
1D:
BEAM188
COMBIN14
2D:
SHELL181
SHELL281
CONT174
TARG170
3D:
SOLID185
SOLID186
SOLID187
Regards,
Abhi
On 8 Mar. 2018 6:42 am, "Abhijeet Pandey"<EMAIL_ADDRESS>wrote:

Sorry for the delay. I will send the default elements for workbench today.
-Abhi
On 7 Mar. 2018 10:12 pm, "Alex Kaszynski"<EMAIL_ADDRESS>wrote:

Closing soon unless I hear back.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/akaszynski/pyansys/issues/15#issuecomment-371119523,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AXa6V4uNygIkNpmjI62E5Hks1UuGCPhDks5tb86agaJpZM4SQU6H
.

Thanks!  Let me know if you can read in shell elements now.  I tested it on:
http://pyansys.readthedocs.io/en/latest/ansys_examples.html#spotweld-shell181-example
I'd like to know if it works for you as well.

Hello Mate,
Sorry for the late response. I tried out the spot weld example with Shell elements. The results from pyansys come close to the middle layer results (using SHELL command) for the shell from Ansys results.
Also there are options(AVRES, EFACET, AVPRIN command) in Ansys (last image) for if the user wanted to average across different thicknesses and materials. I am not sure how pyansys is taking care of this as each option would result in a significantly different plot.

Regards,
Abhi


Daemonset scheduling

Description
What problem are you trying to solve?
Have enough capacity for a pod that is scheduled on a new node with other daemon-sets.
in case I have a pod that is requiring a 15vCPU, I will get a 16vCPU node, the problem is that my daemon set's in total could require 1.5 vCPU.
This scenario creates a really bad behavior which I call a "scheduling loop":

scheduler will get a request of 15vCPU allocation
karpenter will allocate me a 16vCPU node
all daemon set's will be scheduled
the 15vCPU required workload could not be scheduled on that node. setting pod priority and evicting other pods is not an option.
the new node will be terminated, the pod will continue to be in pending state, and karpenter will allocate me the same instance size.

the only way I can resolve this behavior is to ask in advance more cores on the dedicated workload to get a bigger instance size.
I would like to add a new annotation on the node-pool scheduling, which could be called "daemon-set-overhead".
so that any new node's that are being scheduled from that node-pool will take into consideration the DS requests.
for example:

workload of 15 vCPU
DS overhead of 1.5 vCPU
scheduler will be asked to get a node with at least 16.5 vCPU.

How important is this feature to you?
This feature can help me avoid scenarios where specific workload is not scheduled due to this behavior, daemon-sets are taking a critical part in my infrastructure, by taking daemons into the scheduler calculations I can avoid having unnecessary request allocation and be at peace of mind that my workload will be scheduled properly

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

Karpenter should already calculate the DaemonSets that should be assigned to the node when the node spins up and add that to the pod requests for your applications. If you aren't seeing that behavior, it means there's potentially a bug with how Karpenter is doing the calculation. Could you provide a little more detail into the behavior that you are seeing with Karpenter and how that's different from what you are expecting?

Hi @jonathan-innis
I am running karpenter 0.35 on EKS
I have an application that is requiring 15vCPU, so karpenter will schedule me a 16 vCPU machine, once the machine is scheduled an running, my daemon-sets will start to schedule before the application will be scheduled. the problem is that after the daemon-sets are ready it appears there in not enough room for my application to be scheduled because of the daemon-sets workload, after this is happening, the node is being terminated and new scheduling is happening with exactly the same node capacity.

The main workload is using this EC2NC and node pool
Ec2NodeClass:
Name:         arm64-specific-al2
Namespace:
Labels:       <none>
Annotations:  karpenter.k8s.aws/ec2nodeclass-hash: XXXXXXXX
API Version:  karpenter.k8s.aws/v1beta1
Kind:         EC2NodeClass
Metadata:
  Creation Timestamp:  2024-03-13T11:01:13Z
  Finalizers:
    karpenter.k8s.aws/termination
  Generation:  1
  Managed Fields:
    API Version:  karpenter.k8s.aws/v1beta1
    Fields Type:  FieldsV1
    fieldsV1:
      f:spec:
        f:amiFamily:
        f:blockDeviceMappings:
        f:role:
        f:securityGroupSelectorTerms:
        f:subnetSelectorTerms:
    Manager:      XXXXXXXX
    Operation:    Apply
    Time:         2024-03-13T11:01:13Z
    API Version:  karpenter.k8s.aws/v1beta1
    Fields Type:  FieldsV1
    fieldsV1:
      f:metadata:
        f:annotations:
          .:
          f:karpenter.k8s.aws/ec2nodeclass-hash:
        f:finalizers:
          .:
          v:"karpenter.k8s.aws/termination":
    Manager:      karpenter
    Operation:    Update
    Time:         2024-03-13T11:01:14Z
    API Version:  karpenter.k8s.aws/v1beta1
    Fields Type:  FieldsV1
    fieldsV1:
      f:status:
        .:
        f:amis:
        f:instanceProfile:
        f:securityGroups:
        f:subnets:
    Manager:         karpenter
    Operation:       Update
    Subresource:     status
    Time:            2024-04-18T06:15:27Z
  Resource Version:  570114648
  UID:               64ff56f1-1f4d-41c7-a879-c89ce49b6b76
Spec:
  Ami Family:  AL2
  Block Device Mappings:
    Device Name:  /dev/xvda
    Ebs:
      Encrypted:    true
      Volume Size:  50Gi
      Volume Type:  gp3
    Device Name:    /dev/xvdb
    Ebs:
      Encrypted:    true
      Volume Size:  10Gi
      Volume Type:  gp3
  Metadata Options:
    Http Endpoint:                enabled
    httpProtocolIPv6:             disabled
    Http Put Response Hop Limit:  2
    Http Tokens:                  required
  Role:                           XXXXXXXXXX
  Security Group Selector Terms:
    Tags:
      XXXXXXX:  XXXXXXX
  Subnet Selector Terms:
    Tags:
      XXXXXXX:  XXXXXXX
      XXXXXXX:  XXXXXXX
  Tags:
    XXXXXXX:  XXXXXXX
Status:
  Amis:
    Id:    ami-01af8560b504eb3db
    Name:  amazon-eks-arm64-node-1.28-v20240415
    Requirements:
      Key:       kubernetes.io/arch
      Operator:  In
      Values:
        arm64
      Key:       karpenter.k8s.aws/instance-gpu-count
      Operator:  DoesNotExist
      Key:       karpenter.k8s.aws/instance-accelerator-count
      Operator:  DoesNotExist
    Id:          ami-0f6bdc3ce0ee191e9
    Name:        amazon-eks-gpu-node-1.28-v20240415
    Requirements:
      Key:       kubernetes.io/arch
      Operator:  In
      Values:
        amd64
      Key:       karpenter.k8s.aws/instance-gpu-count
      Operator:  Exists
    Id:          ami-0f6bdc3ce0ee191e9
    Name:        amazon-eks-gpu-node-1.28-v20240415
    Requirements:
      Key:       kubernetes.io/arch
      Operator:  In
      Values:
        amd64
      Key:       karpenter.k8s.aws/instance-accelerator-count
      Operator:  Exists
    Id:          ami-01520c51b1b0e680b
    Name:        amazon-eks-node-1.28-v20240415
    Requirements:
      Key:       kubernetes.io/arch
      Operator:  In
      Values:
        amd64
      Key:           karpenter.k8s.aws/instance-gpu-count
      Operator:      DoesNotExist
      Key:           karpenter.k8s.aws/instance-accelerator-count
      Operator:      DoesNotExist
  Instance Profile:  XXXXXXXXXX
  Security Groups:
    Id:    XXXXXXXX
    Name:  XXXXXXXX
  Subnets:
    Id:    XXXXXXXX
    Zone:  us-east-1f
    Id:    XXXXXXXX
    Zone:  us-east-1d
    Id:    XXXXXXXX
    Zone:  us-east-1b
    Id:    XXXXXXXX
    Zone:  us-east-1c
Events:    <none>

node pool
Name:         arm64-specific-al2
Namespace:
Labels:       <none>
Annotations:  karpenter.sh/nodepool-hash:<PHONE_NUMBER>0938391933
API Version:  karpenter.sh/v1beta1
Kind:         NodePool
Metadata:
  Creation Timestamp:  2024-03-13T11:01:13Z
  Generation:          1
  Managed Fields:
    API Version:  karpenter.sh/v1beta1
    Fields Type:  FieldsV1
    fieldsV1:
      f:spec:
        f:disruption:
          f:consolidationPolicy:
          f:expireAfter:
        f:limits:
          f:cpu:
          f:memory:
        f:template:
          f:spec:
            f:nodeClassRef:
              f:apiVersion:
              f:kind:
              f:name:
            f:requirements:
        f:weight:
    Operation:    Apply
    Time:         2024-03-13T11:01:13Z
    API Version:  karpenter.sh/v1beta1
    Fields Type:  FieldsV1
    fieldsV1:
      f:metadata:
        f:annotations:
          .:
          f:karpenter.sh/nodepool-hash:
    Manager:      karpenter
    Operation:    Update
    Time:         2024-03-13T11:01:13Z
    API Version:  karpenter.sh/v1beta1
    Fields Type:  FieldsV1
    fieldsV1:
      f:status:
        .:
        f:resources:
          .:
          f:cpu:
          f:ephemeral-storage:
          f:memory:
          f:pods:
    Manager:         karpenter
    Operation:       Update
    Subresource:     status
    Time:            2024-04-18T06:16:17Z
  Resource Version:  570115420
  UID:               570b6186-f65f-4895-8b4d-2cb7845e7924
Spec:
  Disruption:
    Budgets:
      Nodes:               10%
    Consolidation Policy:  WhenUnderutilized
    Expire After:          720h
  Limits:
    Cpu:     10000
    Memory:  1000000Gi
  Template:
    Spec:
      Node Class Ref:
        API Version:  karpenter.k8s.aws/v1beta1
        Kind:         EC2NodeClass
        Name:         arm64-specific-al2
      Requirements:
        Key:       karpenter.k8s.aws/instance-size
        Operator:  NotIn
        Values:
          metal
        Key:       kubernetes.io/arch
        Operator:  In
        Values:
          amd64
          arm64
        Key:       topology.kubernetes.io/zone
        Operator:  In
        Values:
          us-east-1c
          us-east-1f
          us-east-1b
          us-east-1d
        Key:       type
        Operator:  NotIn
        Values:
          private
        Key:       type
        Operator:  In
        Values:
          public
        Key:       karpenter.sh/capacity-type
        Operator:  In
        Values:
          on-demand
          spot
        Key:       karpenter.k8s.aws/instance-cpu
        Operator:  Gt
        Values:
          4
  Weight:  50
Status:
  Resources:
    Cpu:                  2544
    Ephemeral - Storage:<PHONE_NUMBER>Ki
    Memory:<PHONE_NUMBER>Ki
    Pods:                 20028
Events:                   <none>

DaemonSet is being scheduled on each karpenter node, this is affinity:
    spec:
      affinity:
        nodeAffinity:
          requiredDuringSchedulingIgnoredDuringExecution:
            nodeSelectorTerms:
            - matchExpressions:
              - key: karpenter.sh/registered
                operator: In
                values:
                - "true"

this is the affinity for the main workload
      affinity:
        nodeAffinity:
          requiredDuringSchedulingIgnoredDuringExecution:
            nodeSelectorTerms:
            - matchExpressions:
              - key: karpenter.sh/capacity-type
                operator: In
                values:
                - spot
                - on-demand
              - key: kubernetes.io/arch
                operator: In
                values:
                - arm64
              - key: type
                operator: In
                values:
                - public
              - key: type
                operator: NotIn
                values:
                - private

Do you have Karpenter controller logs that you can share from these launches as well? These should give us some detail on how much Karpenter is calculating for the requests that the node needs and how much available space that Karpenter thinks that the node will have.

Also, looking at the DaemonSets, there is an open issue in the kubernetes-sigs/karpenter repo around specifying DaemonSets with karpenter.sh/registered or karpenter.sh/initialized in their affinity: https://github.com/kubernetes-sigs/karpenter/issues/919.
Basically, Karpenter doesn't realize that this label is going to be present on the node when it is going through scheduling, so that causes it to think that the DaemonSet will never schedule to nodes provisioned by that NodePool. When the node actually spins-up, that label obviously gets added so the pods do schedule, but this is going to create the continual spin behavior that you are seeing.
You should be able to fix this issue by specifying karpenter.sh/nodepool instead of karpenter.sh/registered in the affinity.

I haven't seen any response on this one, but I think this should cover the problem that you are hitting. Feel free to add additional comments on this if you don't think that this should have been closed. Closing for now...


Account for dropcap when calculating paragraph size, fix duplicate last char when using dropcap with autowrap off.

Account for dropcap when calculating paragraph size.
Fix duplicate last char when using dropcap with autowrap off.

Fixes https://github.com/godotengine/godot/issues/96255
Note: dropcap is still not convenient to use with autowrap off, since only one paragraph will flow around it (and a normal new line will start a new paragraph), but you can force breaks within a paragraph with other line breaking characters, e.g, [char=0B].

Fix duplicate last char when using dropcap with autowrap off.

Does this also fix #94819? As in, fixing the duplicate last char when autowrap is set to any value other than off

Does this also fix https://github.com/godotengine/godot/issues/94819? As in, fixing the duplicate last char when autowrap is set to any value other than off

Yes, should fix it as well.

Thanks!


[core] Do not generate utility classes

Duplicates

[X] I have searched the existing issues

Latest version

[X] I have tested the latest version

Summary 💡
Without default MUI class.
I want no show any class that contain default class like  class="Typography-root Container-root Container-maxWidthLg"  in the DOM.
I am prefer it all like random class.  css-1ujsas3  css-f156aff css-fdfdv54
Examples 🌈

Test

to

Test

Motivation 🔦
No response

@TpTTT-T what is the reason for this? We discussed this briefly with @michaldudak too, but I am curious to know why do you think this will be an improvement.

@TpTTT-T what is the reason for this? We discussed this briefly with @michaldudak too, but I am curious to know why do you think this will be an improvement.

The Real DOM element that use MUI component className is too long.
Random css is prettier than default long classname.
I prefer to use random css in real website, default className in developer

I believe we can track it in #30820 as it's more broad (it about customization, not just removal of generated class names).


Clean up Tech Spec

Oed and Christian need to have a conversation about lpld

https://github.com/uport-project/3box/blob/master/ARCHITECTURE.md
Needs to be updated. Most of the stuff is already in the data schema file in the 3box-js library.

https://github.com/uport-project/3box/blob/master/ABOUT.md
Can be removed?

Yes, seems like we can remove the DATA-SCHEMA file. I still think that the ARCHITECTURE file should live in the 3box repo though, since it also includes information about the server side components. We can have a link to it from the 3box-js repo.


⚠ GG2RDF Service has degraded performance

In dc237ac, GG2RDF Service (https://gg2rdf.ld.plazi.org/status) experienced degraded performance:

HTTP code: 200
Response time: 658 ms

Resolved: GG2RDF Service performance has improved in a2c048b after 44 minutes.


Convert OOXML to CiceroMark (JSON)

I hope this is the last time :crossed_fingers:

Coverage increased (+0.2%) to 91.868% when pulling f71eaa9944bc237a80f2bb8e4485052cd4d5ca60 on algomaster99:pointer-to-ooxml into 6d0f4401a7aee7151ec4425de1ed1c7c381d7e75 on accordproject:algoo-ooxml.


add heuristic for excluding auto-generated containers/identities

Adds support for #7.
The implementation is on the conservative side to insure that it

works with any configuration of Temporary Containers (any prefix, any color, any symbol, even with randomization)
works with different configurations of Temporary Containers on different machines - e.g. it does not use a fixed prefix
it only triggers when it finds at least two containers matching ^([a-zA-Z-_]+)\d$ with the same stem (prefix)
it filters both backup and restore => excludes single auto-generated identities

What's left?
The pull request is shippable. A later version could add preferences (including UI) for manual configuration of exclusion criteria.

Sorry for the late reply.
Thanks a lot for your contribution. I'll ship this with the UI in the next release


Test failure due to Chalice's breaking change

$ travis_retry pytest tests/adapter_tests/
============================= test session starts ==============================
platform linux -- Python 3.6.7, pytest-5.4.3, py-1.7.0, pluggy-0.12.0
rootdir: /home/travis/build/slackapi/bolt-python, inifile: pytest.ini
plugins: cov-2.10.1
collected 53 items
tests/adapter_tests/test_aws_chalice.py ....F.                           [ 11%]
tests/adapter_tests/test_aws_lambda.py ........                          [ 26%]
tests/adapter_tests/test_bottle.py ...                                   [ 32%]
tests/adapter_tests/test_bottle_oauth.py .                               [ 33%]
tests/adapter_tests/test_cherrypy.py ....                                [ 41%]
tests/adapter_tests/test_cherrypy_oauth.py ..                            [ 45%]
tests/adapter_tests/test_django.py ....                                  [ 52%]
tests/adapter_tests/test_falcon.py ....                                  [ 60%]
tests/adapter_tests/test_fastapi.py ....                                 [ 67%]
tests/adapter_tests/test_flask.py ....                                   [ 75%]
tests/adapter_tests/test_lambda_s3_oauth_flow.py .                       [ 77%]
tests/adapter_tests/test_pyramid.py ....                                 [ 84%]
tests/adapter_tests/test_starlette.py ....                               [ 92%]
tests/adapter_tests/test_tornado.py ...                                  [ 98%]
tests/adapter_tests/test_tornado_oauth.py .                              [100%]
=================================== FAILURES ===================================
______________________ TestAwsChalice.test_lazy_listeners ______________________
self = <tests.adapter_tests.test_aws_chalice.TestAwsChalice object at 0x7fcdd5cbcfd0>
    def test_lazy_listeners(self):
        app = App(client=self.web_client, signing_secret=self.signing_secret,)

        def command_handler(ack):
            ack()

        def say_it(say):
            say("Done!")

        app.command("/hello-world")(ack=command_handler, lazy=[say_it])

        input = (
            "token=verification_token"
            "&team_id=T111"
            "&team_domain=test-domain"
            "&channel_id=C111"
            "&channel_name=random"
            "&user_id=W111"
            "&user_name=primary-owner"
            "&command=%2Fhello-world"
            "&text=Hi"
            "&enterprise_id=E111"
            "&enterprise_name=Org+Name"
            "&response_url=https%3A%2F%2Fhooks.slack.com%2Fcommands%2FT111%2F111%2Fxxxxx"
            "&trigger_id=111.111.xxx"
        )
        timestamp, body = str(int(time())), input

        chalice_app = Chalice(app_name="bolt-python-chalice")
        slack_handler = ChaliceSlackRequestHandler(app=app, chalice=chalice_app)

        headers = self.build_headers(timestamp, body)
        headers["x-slack-bolt-lazy-only"] = "1"
        headers["x-slack-bolt-lazy-function-name"] = "say_it"

        request: Request = Request(
            method="NONE",
            query_params={},
            uri_params={},
            context={},
            stage_vars=None,
            is_base64_encoded=False,
            body=body,
>           headers=headers,
        )
E       TypeError: __init__() got an unexpected keyword argument 'method'
tests/adapter_tests/test_aws_chalice.py:242: TypeError
=============================== warnings summary ===============================

Category (place an x in each of the [ ])
tests
Requirements
Please read the Contributing guidelines and Code of Conduct before creating this issue or pull request. By submitting, you are agreeing to those rules.

Fixed by https://github.com/slackapi/bolt-python/commit/d1dc479d656e2a5fdf2479ff811f225f32484c8a


the tutorial page is now largely empty

Until today link
https://docs.microsoft.com/en-us/azure/app-service/tutorial-custom-container?pivots=container-linux
 used to contain an excellent tutorial on using Azure Container Apps to
  deploy a container image ... now today this page is largely EMPTY

     What happened to its contents ?

     It used to detail steps including below :

 Build and test the image locally

docker build --tag appsvc-tutorial-custom-image .

docker run -it -p 8000:8000 appsvc-tutorial-custom-image

Create a resource group

az group create --name myResourceGroup --location westeurope

Push the image to Azure Container Registry

Run the az acr show command to retrieve credentials for the registry:

Use the docker login command to sign in to the container registry:

Use the docker push command to push the image to the registry:

docker push <registry-name>.azurecr.io/appsvc-tutorial-custom-image:latest

complete the steps in the next section to configure App Service to deploy from the registry.

az acr repository list -n <registry-name>

Configure App Service to deploy the image from the registry

 An App Service plan corresponds to the virtual machine that hosts the web app. By default, the previous command uses an inexpensive B1 pricing tier that is free for the first month. You can control the tier with the --sku parameter.

az webapp create --resource-group myResourceGroup --plan myAppServicePlan --name <app-name> --deployment-container-image-name <registry-name>.azurecr.io/appsvc-tutorial-custom-image:latest

Enable the system-assigned managed identity for the web app by using the az webapp identity assign command:

az webapp identity assign --resource-group myResourceGroup --name <app-name> --query principalId --output tsv

Managed identity allows you to grant permissions to the web app to access other Azure resources without needing any specific credentials.

Retrieve your subscription ID with the az account show command, which you need in the next step:

az account show --query id --output tsv

Deploy the image and test the app

 Use the az webapp config container set command to specify the container registry and the image to deploy for the web app:

az webapp config container set --name <app-name> --resource-group myResourceGroup --docker-custom-image-name <registry-name>.azurecr.io/appsvc-tutorial-custom-image:latest --docker-registry-server-url https://<registry-name>.azurecr.io

Access diagnostic logs

Turn on container logging:

az webapp log config --name <app-name> --resource-group myResourceGroup --docker-container-logging filesystem

            NOW all of above content is missing from this link ... Please fix by putting back its content

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

ID: 36d6ead7-4a59-ee55-327a-6cc1a909b6b8
Version Independent ID: d529825d-8e4e-1174-14ff-b404791ef304
Content: Tutorial: Build and run a custom image in Azure App Service - Azure App Service
Content Source: articles/app-service/tutorial-custom-container.md
Service: app-service
GitHub Login: @cephalin
Microsoft Alias: msangapu

Hi @sekhemrekhutawysobekhotep, Thanks for the feedback! I believe the content got moved to a different page. Is this the same content you were referring to https://docs.microsoft.com/en-us/azure/container-apps/get-started-existing-container-image-portal?pivots=container-apps-private-registry

#re-assign: msangapu-msft

@sekhemrekhutawysobekhotep Are you still seeing the issue?

#please-close


Support the direct passing of dictionary literals.

Fix: https://github.com/sqlalchemy/mako/issues/400 and https://github.com/sqlalchemy/mako/issues/401
Support the direct passing of dictionary literals when calling functions and fix the errors caused by unexpected nested braces.

New Gerrit review created for change a08ff83a16f7821b59f06ccb448d702aecbe6b99: https://gerrit.sqlalchemy.org/c/sqlalchemy/mako/+/5558

Sorry for the late reply. Now all the tests have passed.

Patchset c6aa6bef1926f16ff3bb9afca00cf58c1b572a39 added to existing Gerrit review https://gerrit.sqlalchemy.org/c/sqlalchemy/mako/+/5558

Gerrit review https://gerrit.sqlalchemy.org/c/sqlalchemy/mako/+/5558 has been merged. Congratulations! :)

im going to release mako 1.3.7 now with these two changes you did, leaving enough room in the week to revert if we have more reports of issues, thanks!


Building EVP_PKEY_CTX for Verification from raw parameters in OpenSSL 3.0

Hi,
We are currently trying to migrate our code base to the OpenSSL 3.0 API alpha 13 and we have difficulty understanding how to build an EVP_PKEY_CTX to verify a signature.
Until now we took all the parameters of an EC curve (a, b, p, generator, order and cofactor), built an EC_GROUP, an EC_KEY, an EVP_PKEY and used that for the EVP_PKEY_CTX:
EC_GROUP* group = EC_GROUP_new_curve_GFp(bn_p, bn_a, bn_b, 0);
EC_POINT* base_point = EC_POINT_new(group);
EC_POINT_oct2point(group, base_point, generator, sizeof(generator), 0);
EC_GROUP_set_generator(group, base_point, bn_order, bn_cofactor);
EC_KEY* ecKey = EC_KEY_new();
EC_KEY_set_group(ecKey, group);
EC_POINT* public_point = EC_POINT_new(group);
EC_POINT_oct2point(group, public_point, pub, sizeof(pub), 0);
EC_KEY_set_public_key(ecKey, public_point);

EVP_PKEY* evpPkey = EVP_PKEY_new();
EVP_PKEY_set1_EC_KEY(evpPkey, ecKey);
EVP_PKEY_CTX* ctx = EVP_PKEY_CTX_new(evpPkey, 0);
EVP_PKEY_verify_init(ctx);
EVP_PKEY_verify(ctx, signature, sizeof(signature), data, sizeof(data));

Working with EC_KEY directly is deprecated in OpenSSL 3.0 (EC_KEY_new, EC_KEY_set_group, EC_KEY_set_public_key, EVP_PKEY_set1_EC_KEY). We therefor tried to use the parameter interface:
EVP_PKEY_CTX* gctx = EVP_PKEY_CTX_new_from_name(0, "EC", 0);

EVP_PKEY_verify_init(gctx);

OSSL_PARAM_BLD* bld = OSSL_PARAM_BLD_new();
OSSL_PARAM* params = 0;

if (bld == NULL
        || !OSSL_PARAM_BLD_push_BN(bld, "p", bn_p)
        || !OSSL_PARAM_BLD_push_BN(bld, "a", bn_a)
        || !OSSL_PARAM_BLD_push_BN(bld, "b", bn_b)
        || !OSSL_PARAM_BLD_push_BN(bld, "order", bn_order)
        || !OSSL_PARAM_BLD_push_BN(bld, "cofactor", bn_cofactor)
        || !OSSL_PARAM_BLD_push_octet_string(bld, "pub", pub, sizeof(pub))
        || !OSSL_PARAM_BLD_push_octet_string(bld, "generator", generator, sizeof(generator))
        || !OSSL_PARAM_BLD_push_utf8_string(bld, "field-type", fieldtype, sizeof(fieldtype))
        || (params = OSSL_PARAM_BLD_to_param(bld)) == 0)
{
    printf("Param builder failed\n");
    exit(1);
}

EVP_PKEY_CTX_set_params(gctx, params);

EVP_PKEY_verify(gctx, signature, sizeof(signature), data, sizeof(data));

The first way works, but is deprecated, the second is not, using the same parameters. What are we missing here? Are we missing a parameter, do we use the wrong name for the EVP_PKEY_CTX or are we simply not using the API as intended?
Another question: In https://www.openssl.org/docs/manmaster/man7/EVP_KEYMGMT-EC.html some parameters use unsigned int (a, b, p, order), but shouldn't it be BIGNUM?
A simple example is attached. ossl_example.zip

Another question: In https://www.openssl.org/docs/manmaster/man7/EVP_KEYMGMT-EC.html some parameters use unsigned int (a, b, p, order), but shouldn't it be BIGNUM?

Unsigned integer in this context doesn't specify a length.  A BIGNUM is allowed as would a byte.

You cannot set the key parameters on the EVP_PKEY_CTX. You need to use EVP_PKEY_fromdata() to create an EVP_PKEY from the data and then use that EVP_PKEY. Basically you'll keep the last three lines of your legacy code but you'll replace the rest with appropriately adjusted code from the example from the EVP_PKEY_fromdata(3) manpage.

Thanks, this worked for us!
We are still unsure on how to use the static OSSL_PARAMs without a BIGNUM.
This works for us.
BIGNUM* p;
BN_bin2bn(mPrimeModulus->data, mPrimeModulus->length, p);
OSSL_PARAM_BLD_push_BN(bld, "p", p)

How to avoid a BIGNUM and use mPrimeModulus directly? Is that possible? What format is expected here? Our call to EVP_PKEY_fromdata fails.
params[0] = OSSL_PARAM_construct_BN("p", mPrimeModulus->data, mPrimeModulus->length);
...
params[n] = OSSL_PARAM_construct_end();

Unfortunately there is basically no nice and clean way how to use the static OSSL_PARAMs without a BIGNUM because the params must be in arch native byte order. So if you have regular big endian static data as what the bin2bn expects, you'd need to first convert it to little endian on little endian architectures before using the construct_BN call.

From the documentation:
=item B<OSSL_PARAM_UNSIGNED_INTEGER>

The parameter data is an integer (signed or unsigned) of arbitrary
length, organized in native form, i.e. most significant byte first on
Big-Endian systems, and least significant byte first on Little-Endian
systems.

Thanks!
Is it possible to fetch the parameters later? Just need for unit tests here.
It works for the "group".
EVP_PKEY_get_utf8_string_param(key.data(), "group", name, sizeof(name), &len);

But I cannot get a BN here.
EVP_PKEY_get_bn_param(key.data(), "a", &a)
EVP_PKEY_get_bn_param(key.data(), "b", &b)
EVP_PKEY_get_bn_param(key.data(), "p", &p)

But I cannot get a BN here.

Hmmm...assuming you are using a key type that recognises those parameter names (i.e. ec), that should be ok. We do this in our own tests here:
https://github.com/openssl/openssl/blob/6511f686c2c56d3ed68477981c1a3821bdc2e565/test/ectest.c#L2443-L2450
What happens when you try to do this?

It does not work for named groups - if the curve matches a named group it is automatically converted to a named group and the curve parameters are not retrievable for the named groups. I'd say it is a bug. I do not see a reason why you shouldn't be able to retrieve the parameters even for the named groups.

I'd say it is a bug.

Sounds like a bug to me. You really should be able to do this.

@misery Would you please open a new issue for the ec parameters problem?

Thanks for answer! I created a new issue: https://github.com/openssl/openssl/issues/14662


libnetty_resolver_dns_native_macos_x86_64 crash when upgrading from 4.1.87 to 4.1.88

OS 11.4
Darwin Kernel Version 20.5.0
dyld: lazy symbol binding failed: Symbol not found: _netty_jni_util_JNI_OnLoad
  Referenced from: /private/var/folders/9y/1ld4xhrs4q9g3dt33dt9t53c0000gn/T/libnetty_resolver_dns_native_macos_x86_642861775474910762688.dylib
  Expected in: flat namespace

dyld: Symbol not found: _netty_jni_util_JNI_OnLoad
  Referenced from: /private/var/folders/9y/1ld4xhrs4q9g3dt33dt9t53c0000gn/T/libnetty_resolver_dns_native_macos_x86_642861775474910762688.dylib
  Expected in: flat namespace

Ha ha, duplicate of #13214


Fix the numbers in test_network based on feedback-driven analysis

These numbers seem arbitrary. We need to have a clear idea on how to set them, and how to measure the timeouts for the types of deployment. Perhaps they should even be extracted into configuration files.
Originally posted by @appetrosyan in https://github.com/hyperledger/iroha/pull/2969#discussion_r1032066730

not so relevant


value-updates only after 30-40 sec. in Venus OS or VRM-Portal

Hello and many thanks for the nice driver.
I have 3 packs with 16x280Ah and JkBMS with RasPi and Venus OS.
The driver works an every battery, also the virtual aggregate-battery is shown in the Venus OS.
After a while, the values are updated only after 30-40 seconds.
Thats a little problem to find the correct gridpoint near zero.
Is it possible to fix that by my own?
Thanks and greetings
Kristian

Hello, I know about it and work on it. @smurfix supports me with his knowledge. It is a ressource issue. For now you can restart the program, it usually helps.

Dbusmonitor used instead VeDbusItemImport. Solution discussed under isuue #5.


config problems

these two are easy to understand.
name tutorial           # name of network
subnet <IP_ADDRESS>/24     # private subnetwork

what is the random string ? and how to generate ??
and I guess bootstrap.wirehub.io is the hostname of my "bootstrap node" ??
Do I have to open any ports in firewall ?
# one DHT bootstrap node
boot P17zMwXJFbBdJEn05RFIMADw9TX5_m2xgf31OgNKX3w bootstrap.wirehub.io

👋

what is the random string ?

P17zMwXJFbBdJEn05RFIMADw9TX5_m2xgf31OgNKX3w is the public key of the bootstrap node.

and how to generate ??

You can generate a pair of private and public key with wh genkey and wh pubkey.
wh genkey | tee node_a.sk | wh pubkey | tee node_a.k

and I guess bootstrap.wirehub.io is the hostname of my "bootstrap node" ??

Indeed. This is a domain name or IP to contact the bootstap node.

Do I have to open any ports in firewall ?

No.
Note that my bootstrap node is offline. This project is unmaintained.


Add scaling for playback speed (Then automatically make it slower on shorter clips)

Wait for users to use site before fully implementing feature


Chromedriver version check and Nuget package documentation update

Chromedriver version check update from '96.0.4664.45' to '97.0.4692.71'
Nuget package creation - v1.0.3

Codecov Report

Merging #17 (cf54bdc) into main (9c3aaf8) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##              main       #17   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files            1         1
  Lines          108       108
  Branches        10        10
=========================================
  Hits           108       108

Continue to review full report at Codecov.

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


can't initialize iptables table `filter': Table does not exist

INFO[0000]main.go:85 starting wireguard server on <IP_ADDRESS>:51820
INFO[0000]main.go:99 wireguard VPN network is <IP_ADDRESS>/24
FATA[0000]main.go:102 failed to set ip tables rule: running [/sbin/iptables -t filter -C WG_ACCESS_SERVER_FORWARD -s <IP_ADDRESS>/24 -d <IP_ADDRESS>/0 -j ACCEPT --wait]: exit status 3: modprobe: can't change directory to '/lib/modules': No such file or directory
iptables v1.8.3 (legacy): can't initialize iptables table `filter': Table does not exist (do you need to insmod?)
Perhaps iptables or your kernel needs to be upgraded.
[root@localhost ~]# docker run   -it   --rm   --cap-add NET_ADMIN   --device /dev/net/tun:/dev/net/tun   -v wg-access-server-data:/data   -e "WG_ADMIN_PASSWORD=$WG_ADMIN_PASSWORD"   -e "WG_WIREGUARD_PRIVATE_KEY=$WG_WIREGUARD_PRIVATE_KEY"   -p 8601:8000/tcp   -p 8600:51820/udp   place1/wg-access-server
INFO[0000]main.go:85 starting wireguard server on <IP_ADDRESS>:51820
INFO[0000]main.go:99 wireguard VPN network is <IP_ADDRESS>/24
FATA[0000]main.go:102 failed to set ip tables rule: running [/sbin/iptables -t filter -C WG_ACCESS_SERVER_FORWARD -s <IP_ADDRESS>/24 -d <IP_ADDRESS>/0 -j ACCEPT --wait]: exit status 3: modprobe: can't change directory to '/lib/modules': No such file or directory
iptables v1.8.3 (legacy): can't initialize iptables table `filter': Table does not exist (do you need to insmod?)
Perhaps iptables or your kernel needs to be upgraded.

You may want to try out the fork over at https://github.com/freifunkMUC/wg-access-server.
If there still are any problems, feel free to open an issue over there.


Abnormal Container Termination

This is hard to explain, but example better than 1000 words:
On Terminal 1 (run)
host$ sudo docker run --name="test" -i -t ubuntu /bin/bash

On Terminal 2 (exec)
host$ sudo docker exec -it test /bin/bash

On Terminal 1 (human type: "exit")
root@194c15a91851:/# exit
(hang)

On Terminal 2
root@194c15a91851:/#
(exit)
host$

On Terminal 3 (show state)
host$ sudo docker ps -a
CONTAINER ID        IMAGE               COMMAND             CREATED              STATUS                         PORTS               NAMES
194c15a91851        ubuntu:latest       "/bin/bash"         About a minute ago   Up About a minute                                  test
host$ sudo docker kill 194c15a91851
Error response from daemon: Cannot kill container 194c15a91851: no such process
FATA[0000] Error: failed to kill one or more containers

On Terminal 2 (restart docker)
host$ sudo restart docker
docker start/running, process 5929
host$ sudo docker ps -a
CONTAINER ID        IMAGE               COMMAND             CREATED             STATUS                         PORTS               NAMES
194c15a91851        ubuntu:latest       "/bin/bash"         6 minutes ago       Exited (-127) 5 minutes ago                        test

On Terminal 1
(exit)
FATA[0063] Get http:///var/run/docker.sock/v1.16/containers/194c15a91851bef7887110b45ddb7963ce88599cb3e7fc6d66450aaff766d7d3/json: write unix /var/run/docker.sock: broken pipe.


CPI client with return values

The CPI client should transparently use "retbuf" accounts to allow returning values from CPI.

The one advantage of using CPI instead of reading accounts directly is that the program can perform access control that the caller doesn't need to worry about.

Another advantage is that sometimes you want to make a call to an opaque address that implements some interface. So you need to make a CPI instead of reading accounts.

The "Ephemeral Accounts" proposed here will allow this to be implemented without retbuf accounts, which is the last thing blocking the implementation of this https://github.com/solana-labs/solana/blob/1b81a6323ff1c0c2a9510804f71f07bbde3719a7/docs/src/proposals/interest-bearing-tokens.md#ephemeral-accounts.

New proposal for return data here https://github.com/solana-labs/solana/pull/19318.

FYI: heres the proposal https://github.com/solana-labs/solana/blob/master/docs/src/proposals/return-data.md

usage examples:
caller:
https://github.com/solana-labs/solana/blob/527f62c744b3bc664dcfe1d2bf75cb2f9055faf8/programs/bpf/rust/invoke/src/processor.rs#L369
callee:
https://github.com/solana-labs/solana/blob/527f62c744b3bc664dcfe1d2bf75cb2f9055faf8/programs/bpf/rust/invoked/src/processor.rs#L292

To clarify the desired behavior here.
One should be able to define an instruction handler with a return value, e.g.
#[program]
mod program {
  fn my_instruction(ctx: Context<MyInstruction) -> Result<u64> {
    Ok(2)
  }
}

Such that the cpi client in crate::cpi::my_program can be invoked, returning Result<u64>.

We're using it like this:
https://github.com/smartcontractkit/chainlink-solana/blob/196e46631c299bf62b5583ff09830935539302af/contracts/programs/store/src/lib.rs#L280-L286
Then decoding the data after CPI:
https://github.com/smartcontractkit/chainlink-solana/blob/196e46631c299bf62b5583ff09830935539302af/contracts/programs/store/src/lib.rs#L385-L395
I also have a function that decodes the return in tests: https://github.com/smartcontractkit/chainlink-solana/blob/196e46631c299bf62b5583ff09830935539302af/contracts/tests/ocr2.spec.ts#L90-L113

We should consider an initial explicit approach instead of a Result<T> return value imo.
I can imagine that devs want to toggle return data via ix input to save compute for callers that dont need it.
And we could write wrappers around the syscall with T: Anchor(De)Serialize that would make them pleasant to use.
Explicit functions also feel like a reasonable stepping stone from which we could see whether we should add cpi return values as handler return values

Explicit functions also feel like a reasonable stepping stone from which we could see whether we should add cpi return values as handler return values

Explicit functions sound good as an additional feature, though I still think we should add the return functions as described above so that we can have a more intuitive programming model that favors composability. This feature should be used for pluggable components that typically don't store state and just return a value. Programs that care about compute can simply not return a value.

I agree that it would be more intuitive although I dont see how it's more composable. its the same functionality, just a different api.
That said, I like it with functions that only compute and return values and do nothing else although Im not sure those are really necessary to be called via cpi. you can save one context switch in compute by not cpi'ing. It seems to me that return values are most useful when something else is done in the cpi anyway.
In a world where compute doesnt matter this is fine to do via cpi but I dont think that world is real. We might not have to do eth like optimizations but compute-intensive tx are hurting the network and may cost more in the future.
And I think that all programs should care about compute because theyre not independent of other programs (and also compute will probably cost more in the future). there will be a tx wide compute budget. this means that program optimization becomes more important cause badly optimized programs take away compute from other ix.

The feature is opt in. So there's no downside of adding it since programs that don't need it can opt out.

I'll tackle this if no one is working on it.


Parser urdf

In its current version, the urdf parser is not able to understand url starting by "package://"
Moreover, it seems that srdf files are not parsed.

@florent-lamiraux Do you think there's a solution for the package:// issue without adding a dependency to ROS?
+1 for srdf.
+1 as well for sdf, the official format for Gazebo simulator. It offers slightly more options than urdf, such as adding parallel spring-dampers on the joints. Although outside the current scope of pinocchio, the model does not need to be a kinematics tree, it can also be a DAG for parallel robots.

I think the best solution is to parse ROS_PACKAGE_PATH environment variable in C++ and to search in the corresponding directories for the files. The way ROS proceeds is not very clear and fails sometimes to find new directories because the right setup.sh has not been resourced after installation.

The final idea is then:

Add method to directly read a SRDF file to activate collision pairs.
Add function to locate model and its data (URDF, SRDF, meshes, etc) by only the robot name and seek in $ROS_PACKAGE_PATH

Have you other requests?

Solved by #110.


METRON-670 Monit Incorrectly Reports Status

In a constrained environment, like 'Quick Dev', Monit will often incorrectly report the status of a Metron topology. This occurs when the environment is under load and a query of topology status exceeds the default timeout of 30 seconds.
Added a parameter so that the timeout for a status check can be extended under these conditions. This was previously done for starting and stopping a topology, but not for a status checks.
This was tested in 'Quick Dev' and made starting, stopping and reporting status of the topologies using Monit work much better.  Previously Monit would erroneously report some of the topologies as not running when they were.  This would also interfere with your ability to start/stop the same topologies.
For example, starting all of the services required to consume Bro telemetry works much better with this change.
monit -g bro start

There are also problems with shutting down topologies, since we don't pass in the wait to storm ( at least we didn't.   I need to find the pr/jira for that.  All external calls from monit need to have clear timeout accounting from both monit's pov and the external agent

+1, spun this up in quick dev, and it seems to work well and the UI reports the timeout on status is 60 seconds.  Thanks for grabbing this.

All of these files will go away as a result of PR-436. Would you guys be willing to hold off until I can get it completed and through the process?

@dlyle65535 I'm fine with holding off on it. I wasn't sure of the timing on that, and I have been annoyed by this issue in my own testing in the interim.
@nickwallen You okay with holding off on this?

I found myself having to manually do this all the time.  I thought it might be worthwhile to put the fix in, so that at least we have a record of it working at some point in time.  Then after @dlyle65535 gets his PR done, he can remove it.
I don't have a strong opinion either way though.  Meh.

It creates a bunch of rebase conflicts for me when I bring it in. Fwiw, I've got one more hard problem + a review until I'm done.

No longer needed.


modify OUT_IN_data.f90 not to make access outside bounds of arrays.

This PR does not affect the normal use of SALMON.
In the GCEED part, the access outside bounds of arrays occurs when users read checkpoint files in scf calculations with k points parallelization or orbital parallelization. This PR fix the bug for the access.

I approve this PR.

Thank you for merging, @tt-ims san.


add a GFF3 parser

We need a parser that supports the GFF3 format.
Get the sample fasta and gff3 format from here. (These two files will be used for testing the annotate_from_gff method works, but for this ticket just add the gff file.)
add the parser as cogent3.parse.gff.gff3_parser, and hook it into the gff_parser function, with the check for version number.
and of course, tests (correct parser is chosen, correct number of records processed)!

Write a docstring for the gff_parser function. In changing returned object to dict, important to state that in the doctsring.


Specify custom command syntax using vorpal?

This is somewhat related to vorpal, but I posted it here in case there's a way to do a parsing work around to leave the vorpal stuff untouched.
Is there a way to specify a custom syntax using vorpal? The syntax I'm interested in is something like <id>=[value] (this is what variable reassignment looks like).
If it's possible to write something to recognize that form and preparse it to the form _assign <id> [value], that's probably a good enough work around, since that would let assign be treated like a regular command.

I was thinking about just adding <id>=[value] as alternate parsing to all commands in Vorpal, as, yeah, its coming up in Cash a lot, and is a very familiar method.
Since I'm about to jump under the arg-parsing hood anyways, I'll just do it in Vorpal.

SGTM. Let me know when it's resolved, and I can probably write up regular variable assignments fairly quickly.

:+1:

What I did is normalize key=value pairs in Vorpal, for now. So it will always return key='value', no matter how the user does it, like:
foo=bar => foo='bar'
or
'foo="bar food cat"' => foo='bar food cat'
Then its pretty simple for you to arg parse from there.
Couldn't really think of a better way to do it API-wise. Closing this for now, but if you have an API suggestion post it here and I'll re-open.


[BUG] Installing Winget packages will no longer work after release of Winget 1.9 due to catastrophic failure with --disable-interactivity

Please confirm these before moving forward

[X] I have searched for my issue and have not found a work-in-progress/duplicate/resolved issue.
[X] I have tested that this issue has not been fixed in the latest (beta or stable) release.
[X] I have checked the FAQ section for solutions.
[X] This issue is about a bug (if it is not, please use the correct template).

UniGetUI Version
3.1.0-beta2
Windows version, edition and architecture
Windows 11 Pro 26040.1000 AMD64
Describe your issue
Due to https://github.com/microsoft/winget-cli/issues/4584, installing with the --disable-interactivity flag will always result in "catastrophic failure" under the 1.9 preview.
Steps to reproduce the issue

Install Winget 1.9 preview
Make the app use system Winget
Install a package from the Winget sources using the app

UniGetUI Log
Too long; see [the last section](#Screenshots and videos)

Package Managers Logs
Manager Winget with version:
Naive WinGet CLI Version: v1.9.1792-preview
Microsoft.WinGet.Client PSModule version:
Using Native WinGet helper (COM Api)

——————————————————————————————————————————

Logged native task on manager Winget. Task type is ListSources
Process start time: 2024/7/3 1:00:38
Process end time:   2024/7/3 1:00:38

-- Task information
 ...

The task reported success

——————————————————————————————————————————

Logged subprocess-based task on manager Winget. Task type is RefreshIndexes
Subprocess executable: "C:\Users\aaron\AppData\Local\Microsoft\WindowsApps\winget.exe"
Command-line arguments: " source update --disable-interactivity"
Process start time: 2024/7/3 1:00:40
Process end time:   2024/7/3 1:00:42

-- Process STDOUT
 ...

Return code: SUCCESS (0)

——————————————————————————————————————————

Logged subprocess-based task on manager Winget. Task type is ListPackages
Subprocess executable: "C:\WINDOWS\system32\windowspowershell\v1.0\powershell.exe"
Command-line arguments: "-ExecutionPolicy Bypass -NoLogo -NoProfile"
Process start time: 2024/7/3 1:00:40
Process end time:   2024/7/3 1:00:43

-- Process STDIN
 ...

-- Process STDOUT
 ...

-- Process STDERR
  Write-Output : The term 'Write-Output' is not recognized as the name of a cmdlet, function, script file, or
  operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try
  again.
  At line:1 char:1
  + Write-Output (Get-Module -Name Microsoft.WinGet.Client).Version
  + ~~~~~~~~~~~~~~~
      + CategoryInfo          : ObjectNotFound: (Write-Output:String) [], CommandNotFoundException
      + FullyQualifiedErrorId : CommandNotFoundException

  Import-Module : The specified module 'Microsoft.WinGet.Client' was not loaded because no valid module file was found
  in any module directory.
  At line:1 char:1
  + Import-Module Microsoft.WinGet.Client
  + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
      + CategoryInfo          : ResourceUnavailable: (Microsoft.WinGet.Client:String) [Import-Module], FileNotFoundExcep
     tion
      + FullyQualifiedErrorId : Modules_ModuleNotFound,Microsoft.PowerShell.Commands.ImportModuleCommand

  Get-WinGetPackage : The term 'Get-WinGetPackage' is not recognized as the name of a cmdlet, function, script file, or
  operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try
  again.
  At line:1 char:1
  + Get-WinGetPackage | Print-WinGetPackage
  + ~~~~~~~~~~~~~~~~~
      + CategoryInfo          : ObjectNotFound: (Get-WinGetPackage:String) [], CommandNotFoundException
      + FullyQualifiedErrorId : CommandNotFoundException

Return code: SUCCESS (0)

——————————————————————————————————————————

Logged native task on manager Winget. Task type is ListSources
Process start time: 2024/7/3 1:00:41
Process end time:   2024/7/3 1:00:41

-- Task information
 ...

The task reported success

——————————————————————————————————————————

Logged subprocess-based task on manager Winget. Task type is ListUpdates
Subprocess executable: "C:\WINDOWS\system32\windowspowershell\v1.0\powershell.exe"
Command-line arguments: "-ExecutionPolicy Bypass -NoLogo -NoProfile"
Process start time: 2024/7/3 1:00:42
Process end time:   2024/7/3 1:00:44

-- Process STDIN
 ...

-- Process STDOUT
 ...

-- Process STDERR
  Write-Output : The term 'Write-Output' is not recognized as the name of a cmdlet, function, script file, or
  operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try
  again.
  At line:1 char:1
  + Write-Output (Get-Module -Name Microsoft.WinGet.Client).Version
  + ~~~~~~~~~~~~~~~
      + CategoryInfo          : ObjectNotFound: (Write-Output:String) [], CommandNotFoundException
      + FullyQualifiedErrorId : CommandNotFoundException

  Import-Module : The specified module 'Microsoft.WinGet.Client' was not loaded because no valid module file was found
  in any module directory.
  At line:1 char:1
  + Import-Module Microsoft.WinGet.Client
  + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
      + CategoryInfo          : ResourceUnavailable: (Microsoft.WinGet.Client:String) [Import-Module], FileNotFoundExcep
     tion
      + FullyQualifiedErrorId : Modules_ModuleNotFound,Microsoft.PowerShell.Commands.ImportModuleCommand

  Get-WinGetPackage : The term 'Get-WinGetPackage' is not recognized as the name of a cmdlet, function, script file, or
  operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try
  again.
  At line:1 char:1
  + Get-WinGetPackage | Print-WinGetPackage
  + ~~~~~~~~~~~~~~~~~
      + CategoryInfo          : ObjectNotFound: (Get-WinGetPackage:String) [], CommandNotFoundException
      + FullyQualifiedErrorId : CommandNotFoundException

Return code: SUCCESS (0)

——————————————————————————————————————————

Logged native task on manager Winget. Task type is FindPackages
Process start time: 2024/7/3 1:00:48
Process end time:   2024/7/3 1:00:49

-- Task information
 ...

The task reported success

——————————————————————————————————————————

Relevant information
No response
Screenshots and videos
UniGetUI Log.txt

I am afraid this is on WinGet, and I can't do anything about it


Rebase v1.5.0

several fixes and releases, including fixes for AzureStack Hub:
https://github.com/kubernetes-sigs/azuredisk-csi-driver/compare/v1.5.0...tjungblu:master
CC @openshift/storage

/retest e2e-azure-csi-migration

/test e2e-azure-csi-migration

BTW, the test failure seems unrelated to this PR.

A good side effect of that is that the link you provided in the description will not stop working once you overwrite your master branch. :)

is there a more sustainable solution for this? I intend to completely remove my forked repo after my time on the storage team.
As for the test failure, I already reached out to Mustafa to have a look (I believe he was working on that).

As for the test failure, I already reached out to Mustafa to have a look (I believe he was working on that).

@tjungblu these failing tests are not related to your changes as @bertinatto said. Once we rebase upstream v1.21, all of prometheus WAL problems will be resolved, I hope :)

A good side effect of that is that the link you provided in the description will not stop working once you overwrite your master branch. :)

is there a more sustainable solution for this? I intend to completely remove my forked repo after my time on the storage team.
As for the test failure, I already reached out to Mustafa to have a look (I believe he was working on that).

I'm not sure if there's a better solution for this, but since you intend to remove your fork, I believe we can merge the PR as is. Thanks for working on this.
/lgtm
/approve


Create a React "Hello, world!" project

I believe this should be built on React as opposed to Angular, as it would better suit both our programming preferences (pure functional components!) and performance.

Umm, seems like my Markdown autoformatter went to town on the contributing instructions. I'll fix that in a minute. Do not merge yet.

PINGING @ztaylor54


The forwarder package is not pip installable

The presence of a pyproject.toml file would appear to indicated that a Python module could be installed from this repository, either
git clone https://github.com/ess-dmsc/forwarder.git
python -m pip install ./forwarder

or
python -m pip install git+https://github.com/ess-dmsc/forwarder.git

but either method fails due to misconfiguration of the project for setuptools.
Is it envisioned that this project should not be installable? Or can the pyproject.toml be updated to produce an installable project?

It isn't meant to be pip installable - it is meant to be cloned.
The pyproject.toml is used to avoid having separate .ini files for black, isort, flake8, mypy, etc.

We can make it installable if needs be though.

Thanks for merging #251 🥳
Installing via python -m pip install git+https://github.com/ess-dmsc/forwarder.git now works as I in intially expected


[alembic] update to 1.7.10

Tested on windows and it compiles and works with my downstream project as usual.

👍 Nice update, thanks!


Show ScopeNote in nwbib.ttl notations 102000, 102060

All notations show ScopeNote accordingly except the ones 102000 Landesbeschreibungen and 102060 Reiseberichte.

Adding some context: This issue is about the NWBib subject classification which uses hash URIs. A build can be viewed at https://test.skohub.io/hbz/lobid-vocabs/heads/master/purl.org/lobid/rpb.de.html.
I have added links to the mentioned concepts in the original comment. By now everything seems fine as the scopeNote is shown. So it must have been some problem in the vocabulary that is fixed by now. Right, @HMetzner ? Please close the issue if you agree.


chore!: Remove offical support for python 3.13

Fixes:
What was the problem/requirement? (What/Why)
Dependencies required for the library do not exist for python 3.13
What was the solution? (How)
put in version cap into pyproject.toml file to prevent pip installing on python 3.13
What is the impact of this change?
Users will no longer be able to pip install the library if python version is >=3.13
How was this change tested?
hatch build

Was this change documented?

Are relevant docstrings in the code base updated?
Has the README.md been updated? If you modified CLI arguments, for instance.

Does this PR introduce new dependencies?
This library is designed to be integrated into third-party applications that have bespoke and customized deployment environments. Adding dependencies will increase the chance of library version conflicts and incompatabilities. Please evaluate the addition of new dependencies. See the Dependencies section of DEVELOPMENT.md for more details.

[ ] This PR adds one or more new dependency Python packages. I acknowledge I have reviewed the considerations for adding dependencies in DEVELOPMENT.md.
[X] This PR does not add any new dependencies.

Is this a breaking change?
yes this removes pip support for python 3.13
Does this change impact security?
no
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

closing this PR as a breaking change needs to be merged into deadline-cloud


HandHeldLightComponent is spamming state updates

They get marked as dirty every tick under the update so they're churning data. https://github.com/space-wizards/space-station-14/blob/172b964de4368224820be72625732d06e9c8e7b7/Content.Server/GameObjects/Components/Interactable/HandheldLightComponent.cs#L193
This should be guarded so it only gets called when something changes.

Also ideally it only gets marked as dirty when the panel needs to update rather than every tick when it's on which will lead to significant bandwidth savings if someone ever turned on a flashlight.


Cannot assign a device for operation

Hi
Try to run simple code from example but get exception instantly after start 'Hallucinating...' process. Tensorflow can't find GPU?
Notebook with UHD Graphics 630 and GeForce RTX 2060
Cuda 11.3
Tensorflow 1.15.0
Windows 10
Console:
Hallucinating...
0%|                                                                                | 0/2600 [00:00<?, ?it/s]
Traceback (most recent call last):
File "C:\Users\1\AppData\Local\Programs\Python\Python37\lib\site-packages\tensorflow_core\python\client\session.py", line 1365, in _do_call
return fn(*args)
File "C:\Users\1\AppData\Local\Programs\Python\Python37\lib\site-packages\tensorflow_core\python\client\session.py", line 1350, in _run_fn
target_list, run_metadata)
File "C:\Users\1\AppData\Local\Programs\Python\Python37\lib\site-packages\tensorflow_core\python\client\session.py", line 1443, in _call_tf_sessionrun
run_metadata)
tensorflow.python.framework.errors_impl.InvalidArgumentError: Cannot assign a device for operation G_mapping_1/_Run/G_mapping/latents_in: {{node G_mapping_1/_Run/G_mapping/latents_in}} was explicitly assigned to /device:GPU:0 but available devices are [ /job:localhost/replica:0/task:0/device:CPU:0 ]. Make sure the device specification refers to a valid device.
[[G_mapping_1/_Run/G_mapping/latents_in]]
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "test1.py", line 6, in
L.hallucinate(file_name = 'C:\Proj\Self\NeuralNetworks\Ojo de Dios.mp4')
File "C:\Users\1\AppData\Local\Programs\Python\Python37\lib\site-packages\lucidsonicdreams\main.py", line 680, in hallucinate
self.generate_frames()
File "C:\Users\1\AppData\Local\Programs\Python\Python37\lib\site-packages\lucidsonicdreams\main.py", line 525, in generate_frames
np.tile(class_batch, (batch_size, 1)))
File "C:\Users\1\AppData\Local\Programs\Python\Python37\lib\site-packages\dnnlib\tflib\network.py", line 443, in run
mb_out = tf.get_default_session().run(out_expr, dict(zip(in_expr, mb_in)))
File "C:\Users\1\AppData\Local\Programs\Python\Python37\lib\site-packages\tensorflow_core\python\client\session.py", line 956, in run
run_metadata_ptr)
File "C:\Users\1\AppData\Local\Programs\Python\Python37\lib\site-packages\tensorflow_core\python\client\session.py", line 1180, in _run
feed_dict_tensor, options, run_metadata)
File "C:\Users\1\AppData\Local\Programs\Python\Python37\lib\site-packages\tensorflow_core\python\client\session.py", line 1359, in _do_run
run_metadata)
File "C:\Users\1\AppData\Local\Programs\Python\Python37\lib\site-packages\tensorflow_core\python\client\session.py", line 1384, in _do_call
raise type(e)(node_def, op, message)
tensorflow.python.framework.errors_impl.InvalidArgumentError: Cannot assign a device for operation G_mapping_1/_Run/G_mapping/latents_in: node G_mapping_1/_Run/G_mapping/latents_in (defined at C:\Users\1\AppData\Local\Programs\Python\Python37\lib\site-packages\tensorflow_core\python\framework\ops.py:1748)  was explicitly assigned to /device:GPU:0 but available devices are [ /job:localhost/replica:0/task:0/device:CPU:0 ]. Make sure the device specification refers to a valid device.
[[G_mapping_1/_Run/G_mapping/latents_in]]

I think you should install CUDA 10.0 version instead.
source : https://www.tensorflow.org/install/source#gpu

Unfortunately, I am running into the same issue and have CUDA 10.0 installed.

I have the same issue and have CUDA 11.4. Tensorflow 1.15.4,rtx3080,ubuntu.


katacoda runner: group tutorials into topics

Katacoda offers the possibility to group tutorials into courses (https://www.katacoda.community/git-repository-structure.html#courses).
If we have several tutorials on the same topic (e.g. devon4g), we could group them. This way the katacoda account would be clearer.
Probably we need to pass this topic through the playbook and the parser needs to be adapted for this.

Let's not focus on this right now but possibly we can already share some thoughts on it. There seems to even another notion of scenarios, am I right? So scenarios could be something like what @SchettlerKoehler finally plans to do? We currently are implementing trainings? And what about courses? In any case let's align together what we would expect from each of the different things and what's the difference between them from a katacoda technical standpoint.

@maybeec At the moment we are creating single tutorials (scenarios in katacoda language). Courses are a way to group multiple scenarios together. For example, we have a course about devon4j and we group all tutorials related to devon4j in this course. In Katacoda itself, it's just a way to display them. In the main page, we have a course and when we open it, we can see all the tutorials that belong to it. But we need to change the structure of the tutorials on Github.
If we implement the restoreWorkspace command, maybe we could implement a tutorial series where each tutorial could start with the state of the last tutorial.

It should group the tutorials based on a course_[name].json file. Add a prebuild to group them automatically


Set default TTS settings and add build script for Windows

This PR sets the default TTS language to en-US and the default TTS voice to en-us-x-tpc-network for personal use. The network voice provides better quality than the offline voice. It also adds a new script for building the release on Windows.
Changes made:

Set default TTS language to en-US
Set default TTS voice to en-us-x-tpc-network
Add buildReleaseWin script for Windows users

The changes to the TTS settings were made for personal use, as the network voice provides better quality than the offline voice. The new buildReleaseWin script allows Windows users to easily build the release version of the app.

But... there're users who dont read LN in English (included me)

of course I'm aware of that, in fact, I can read Arabic and French my self
but as I mentioned in the PR, I made these changes for my own selfish
personal needs. 😄
In all seriousness, I had never developed anything for mobile or Android
before. It took me two days just to figure out how to build the project.
But it was worth it for me because the neural network voices are much
better. In fact, the offline voice was so irritating that I couldn't stand
to listen to it.
I decided to share this in case someone else needed it. And if there's
anyone who can add a setting to choose the language and voices, that would
be great.
I also tried to highlight the sentence being read and make the scroll
follow the current sentence, but I wasn't able to do that.
On Tue, Apr 25, 2023, 11:42 AM nyagami @.***> wrote:

But... there're users who dont read LN in English (included me)
—
Reply to this email directly, view it on GitHub
https://github.com/LNReader/lnreader/pull/607#issuecomment-1521569567,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAJ6K7YUOA25M6LSAMOD7XTXC6TBTANCNFSM6AAAAAAXJJWTSY
.
You are receiving this because you authored the thread.Message ID:
@.***>

Hai,
thanks for the this PR. i total agree, offline voice is terrible.
im really looking forward for this.

Everything you want is available in latest code

Closing this as the features are now available in the master branch.


WGPUShaderModuleDescriptor initialized incorrectly

The GPUShaderModule initializes members code and codeSize that do not exist.
Fix coming shortly.

This appears to have already been fixed in master.


500 - Please report this

Issue
Error 500 - message states to please report this.
https://havelund.org/~lhavelund/owcomp/Dant%C3%A9-2105.json

Uh what endpoint does that translate to? The new /heroes endpoint?

2016-11-23 12:40:48,975 - [ERROR] Kyoukai -> Unhandled exception in route `<Route 'get_blob' in blueprint <Blueprint 'api_v3' with 8 routes>>`:
...
  File "/srv/OWAPI/owapi/v3/v3_util.py", line 116, in _rl_inner2
    return await func(ctx, *args, **kwargs)
  File "/srv/OWAPI/owapi/v3/__init__.py", line 63, in get_blob
    d["heroes"]["stats"]["quickplay"] = parsing.bl_parse_hero_data(result)
  File "/srv/OWAPI/owapi/v3/parsing.py", line 298, in bl_parse_hero_data
    role = parsed.xpath(".//h4[@class='h2 hero-detail-role-name']")[0].text
IndexError: list index out of range

test in production

Uh what endpoint does that translate to? The new /heroes endpoint?

It was, yes -- apologies.

test in production

Confirmed, many thanks.


Retina U-Net Segmentation Loss Not Decreasing

Hi, thank your for this great repository!
I encountered some problems during training Retina U-Net, similar to a previous issue. When Instance/Batch-norm is activated, the segmentation loss does not decrease and the segmentation does not work properly. This problem does not occur when no normalisation is used. After some digging into the code, I found a normalisation layer after the final convolution of the segmentation layer of Retina U-Net.
https://github.com/pfjaeger/medicaldetectiontoolkit/blob/2b343ba974a6936d10bc7ba2d571db28f0760df5/models/retina_unet.py#L378
I think there should be no normalisation of the segmentation logits (because it implicitly limits the output prediction) or did I miss something?

Hi thanks for your feedback. Good catch! Although there are no hard rules on where to apply norm, I would intuitively agree that your logits should enter the softmax unscaled. Please set norm to None here until I fix this in the next commit.
Do you get better results with the "fixed norm" as opposed to no norm? Thing is even with other models where the norm was applied correctly I did not see an improvement. I did not test this extensively though, recent neurips papers suggest the actual benefit of norm is to enable larger learning rates so I guess one would have to run some experiments on that. What data set are you working on?

I did some testing with Mask R-CNN, where I compared Instance Norm to no normalisation. The results were slightly worse when I removed the normalisation, but due to time constraints I was not able to do an exhaustive hyerparameter search. I guess the impact is somewhat small, but faster convergence speed and potentially higher learning rates are a nice thing to have :)
I'm working on an in-house dataset which is not public.


Rem function

Add rem conversion function with tests and KSS, documentation.

This is pretty cool! I like the idea of having all these unit tests :+1:


Update README.md

I have add the some additional informaion about hactober-fest and how to start with hacktober-fest.
What the program do ?

In what programming language it is written?

This pull request do not contains files in specific folders. Please fix it and reopen


Split schema for source_types

We need to come up with a new system for schemas stored in DB, because in application_types, there are supported_authentication_types which cannot be used to use the right authentication type, because there isn't anything like authentication_type.
I propose something like:
# application_types.rb

...
supported_authentication_types: {
  "ansible_tower" => ["username_password"],
}
...

# source_types.rb

ansible_tower_json_schema = {
  :authentication => {
    :title => "Configure AnsibleTower Authentication"
    :username_password => {
      :fields => {
        {:component => "text-field", :name => "authentication.authtype", :type => "hidden", :initialValue => "username_password"},
        {:component => "text-field", :name => "authentication.username", :label => "User name"},
        {:component => "text-field", :name => "authentication.password", :label => "Secret Key", :type => "password"}
      }
    }
  },
  :endpoint => {
    :title => "Configure AnsibleTower Endpoint",
    :fields => {
      {:component => "text-field", :name => "endpoint.role", :type => "hidden", :initialValue => "ansible"}, # FIXME: Find the correct value.
      {:component => "text-field", :name => "url", :label => "URL", :validate => [{:type => "url-validator"}]},
      {:component => "checkbox", :name => "endpoint.verify_ssl", :label => "Verify SSL"},
      {:component => "text-field", :name => "endpoint.certificate_authority", :label => "Certificate Authority", :condition => {:when => "endpoint.verify_ssl", :is => true}},
    }
  }
}

update_or_create(:name => "ansible_tower", :product_name => "Ansible Tower", :vendor => "Red Hat", :schema => ansible_tower_json_schema)

There are several possible questions/modifications I have:

Default authentication types (i.e. :default => ... ) Would be something like this required or would every application have always the supported_auth type provided?

Custom titles for each type (add :title to each type hash), do we need to have different titles for each type Configure Amazon ARN, Configure Secret Key?

For better usability I divided endpoints/authentications to two steps. I am not sure if we want this (UX reasons, backend reasons...) but it would be much better for building of the final form.

Will be there different types of endpoints?

I18n - We should start to think how we will provide localized texts.
a) On API side - I have no idea
b) On frontend - instead of hardcoded labels (i.e.: :label => "URL") send ID (:label_id => 'sources.url') (or both to support applications without a I18n solution) and the frontend will pre-process schemas and inject the right labels there.

@agrare @gtanzillo

@rvsia makes sense that the authentication type should be more formalized.  I like your example above but we should probably have a title for the authentication type so that e.g. "Username/Password" or "ARN" could be shown on the UI to the user.
Could you also show an example of a Cost Management case where there are two types of authentications supported?

@agrare
Ad Title) As I stated in my question 2, we could add title for each authentication type
Ad Cost Management )
# source_types.rb

amazon_json_schema = {
  :authentication => {
    :title => "Configure AWS", # Fallback
    :access_key_secret_key => {
      :title => "Configure AWS secret identity", # custom title
      :fields => [
        {:component => "text-field", :name => "authentication.authtype", :type => "hidden", :initialValue => "access_key_secret_key"},
        {:component => "text-field", :name => "authentication.username", :label => "Access Key"},
        {:component => "text-field", :name => "authentication.password", :label => "Secret Key", :type => "password"}
      ]
    }
    :arn => {
      :title => "Configure AWS ARN credentials",
      :fields => [
        {:component => "text-field", :name => "authentication.authtype", :type => "hidden", :initialValue => "arn"},
        {:component => "text-field", :name => "authentication.arn", :label => "ARN"},
      ]
    }
  }
  :endpoint => {
    # no title needed, this step would not be shown in UI, as it is only hidden field
    :hidden => true, # simple flag would make it easier for UI, but is not required
    :fields => [
          {:component => "text-field", :name => "endpoint.role", :type => "hidden", :initialValue => "aws"},
    ]
  }
}

:+1: go ahead and update it for what you need @rvsia


PettingZoo

Hey, I just wanted to mention that we used your code as the base logic of the Backgammon environment PettingZoo, a library that we just released (https://github.com/PettingZoo-Team/PettingZoo / https://www.pettingzoo.ml/). I credited you in the code, and we really appreciate your work.

@jkterry1 Hi Jordan, is the backgammon environment available in PettingZoo?

We eventually removed it because it was being so rarely used (and I believe may have had bugs). It's available in older versions if you look back through the release notes if you'd like to try it out though, and if you want to maintain your own version of it for pettingzoo, we'd be happy to link to the github repo in the third party repos list in the pettingzoo documentation website


Skip HTML comments parsing

This should fix the issue #23

:+1:
Encountered the problem for this library: http://lib.haxe.org/p/suncalc (assuming that this lib is used to render the HTML for it).

Thanks for the patch!


Fix typo in the podspec file

Because of typo in the podspec file, I couldn't install using Cocoapods by specifying repository and tag. I fixed this typo.
Podfile description
pod 'APIKit', :git => 'https://github.com/ishkawa/APIKit.git', :tag => '3.2.0'

Installation Error
$ pod install
Analyzing dependencies
Pre-downloading: `APIKit` from `https://github.com/ishkawa/APIKit.git`, tag `3.2.0`
[!] Failed to load 'APIKit' podspec:
[!] Invalid `APIKit.podspec` file: undefined method `pod_target_xcconfigs=' for #<Pod::Specification name="APIKit">.

 #  from /var/folders/sd/v8vlggpj7k5cq94ckr7b1n680000gn/T/d20180122-1220-28wdgc/APIKit.podspec:26
 #  -------------------------------------------
 #
 >    s.pod_target_xcconfigs = { "SWIFT_VERSION" => "4.0" }
 #
 #  -------------------------------------------

@ishkawa Could you review this pull request.

Thank you for the help 👍

Just pushed 3.2.1 podspec that contains changes in this PR!


Update validate to check for missing components

Note: This is completely untested
Developer's Certificate of Origin 1.1
   By making a contribution to this project, I certify that:

   (a) The contribution was created in whole or in part by me and I
       have the right to submit it under the Apache License 2.0; or

   (b) The contribution is based upon previous work that, to the best
       of my knowledge, is covered under an appropriate open source
       license and I have the right under that license to submit that
       work with modifications, whether created in whole or in part
       by me, under the same open source license (unless I am
       permitted to submit under a different license), as indicated
       in the file; or

   (c) The contribution was provided directly to me by some other
       person who certified (a), (b) or (c) and I have not modified
       it.

   (d) I understand and agree that this project and the contribution
       are public and that a record of the contribution (including all
       personal information I submit with it, including my sign-off) is
       maintained indefinitely and may be redistributed consistent with
       this project or the open source license(s) involved.

Ran this locally and it does render the error outline, but I also noticed that for this use case the tooltip doesn't render either (also on master). So the user won't know why it failed

Ran this locally and it does render the error outline, but I also noticed that for this use case the tooltip doesn't render either (also on master). So the user won't know why it failed

Oh yea we need to set the error message on the node

Oh yea we need to set the error message on the node

do you want ti fix that here or merge this and fix it later?


capture to firefox content is encrypted

Describe the bug
capture to firefox content is encrypted
To Reproduce
Steps to reproduce the behavior:

sudo ./ecapture tls --nspr /usr/lib/firefox/libnspr4.so
request https://www.baidu.com/robots.txt by firefox

Screenshots
ecapture output content(show a little part):

Linux Server/Desktop (please complete the following information):

OS: Linux Desktop VM
Kernel Version 5.13.0-37-generic
Version 20.04.1-Ubuntu
Architecture x86_64 x86_64 x86_64 GNU/Linux

Content-Encoding: gzip

eh... just compressed by gzip .   and you can read text context as http request and http response header.
It is encoded, not encrypt.  and will fix it with #5

sorry，this is misjudgement！！！
thank you for your reply.


Modify the file_url to become invalid when a plurality of comment is in the one file

fix
Operation check
If one comment is in the touch file: OK
If few comment is in the touch file: OK
If one comment is in the touch line: OK
If few comment is in the touch line: OK

LGTM


Light Mode: dark backgrounds in the user profile page

Related to: #2081
In light mode,

the "badge" on the user profile is still showing a dark background:

the honor breakdown too (not sure this one is an actual problem, but that still fills a bit weird when looking at the whole page):

Yeah, the badge is an image. Will need to add an option to generate a light version, then include both in the HTML, then load one based on the theme.
For the honor breakdown, any suggestions for better colors? You can play with it and post screenshots here.

("meh", about the red text on dark bars)
"the simpler the better" (?) reusing the colors of the page:

Tho, I'd like better a lighter red for better readability, but that will "break" the unity of the colors theme. Like:

Deployed the fix


Unable to mock application/x-www-form-urlencoded requests with netty

We are unable to mock the application/x-www-form-urlencoded requests we use for oauth with netty.
The error returned is:
java.lang.RuntimeException: javascript evaluation failed: client_secret=MySecret&grant_type=MyGrantType&client_id=MyClientId, :1:45 Invalid left hand side for assignment
client_secret=MySecret&grant_type=MyGrantType&client_id=MyClientId
at com.intuit.karate.ScriptBindings.eval(ScriptBindings.java:144)
at com.intuit.karate.ScriptBindings.updateBindingsAndEval(ScriptBindings.java:134)
at com.intuit.karate.ScriptBindings.evalInNashorn(ScriptBindings.java:119)
at com.intuit.karate.Script.evalJsExpression(Script.java:371)
at com.intuit.karate.Script.evalKarateExpression(Script.java:285)
at com.intuit.karate.Script.evalKarateExpression(Script.java:171)
at com.intuit.karate.Script.assign(Script.java:601)
at com.intuit.karate.Script.assign(Script.java:527)
at com.intuit.karate.Match.def(Match.java:98)
Attached is a project that shows the issue.
netty-form-issue.zip

this was actually fixed in this commit, but now we have a bug to link to: 14727be
@brianheazlewood 0.9.0.RC4 has this fix - can you confirm ? and thanks for taking the time to create an example project.

@ptrthomas I can confirm the issue is fixed in 0.9.0.RC4. Thanks for your efforts.

@brianheazlewood thanks ! I'll just keep this open until 0.9.0 final is released.

When will this be released?

@TumagoleNed we just released 0.9.0.RC5 - the sooner you confirm it is working fine :)


Make compatible with Java 11/17

Java 8 is supported longer than 11, so it should at least run with 17, otherwise it makes no sense.

It no longer needs to run with Java 8.

https://github.com/bravecollective/brave-bucks/pull/7

Java 8 is supported longer than 11, so it should at least run with 17, otherwise it makes no sense.

Perhaps it is better to rewrite it completely.

Perhaps it is better to rewrite it completely.

…said every software developer ever. 🤣

The app is being rewritten.

URL of new repository?


Update MD file on new branch 2017-38-15_01-12-14

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

split/updateTestCon.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


'visual example' for step 7 of the schematic ('validate the model')

Hi,
The example notebook does a great job of showing the capabilities of the package.
One important thing may be to show a new user a visual example (e.g. overlay of body key-points on a previously unseen video) of what comes out from the trained model in the example notebook.
This is more likely to convince a first-time user who's not yet fully invested.
I see that there are already ROC curves etc. once the model is trained, but it might be useful to show the first-time casual user what the final outputs can actually look like?
Something optional, and completely left to you of course.
This is in relation to the JOSS review process (https://github.com/openjournals/joss-reviews/issues/6392)

Thanks, I'll give it some thought and follow up

I'm going to defer on this for now in the interest of time. If reviewers feel strongly happy to re=approach. Thanks


Dockerfile ARG default values not utilised for Windows containers

The ARG command in a Dockerfile is being ignored when using Windows containers
Linux Containers - Working as expected
Dockerfile:
FROM ubuntu

ARG ENV_NAME=production

RUN echo $ENV_NAME

Build command:
docker build -t argtest .
Build output:
Sending build context to Docker daemon 2.048 kB
Step 1/3 : FROM ubuntu
 ---> 0ef2e08ed3fa
Step 2/3 : ARG ENV_NAME=production
 ---> Running in fb368b080832
 ---> 1dcfb40dfddc
Removing intermediate container fb368b080832
Step 3/3 : RUN echo $ENV_NAME
 ---> Running in c67bef8961d6
production
 ---> 67dc30529c10
Removing intermediate container c67bef8961d6
Successfully built 67dc30529c10

As you can see in Step 3/3, the default ARG value is echoed as expected.
Windows Containers - Not working as expected
Dockerfile:
FROM microsoft/nanoserver

ARG ENV_NAME=production

RUN echo $ENV_NAME

Build command:
docker build -t argtest .
Build output:
Sending build context to Docker daemon 2.048 kB
Step 1/3 : FROM microsoft/nanoserver
 ---> 18a0d32a4b98
Step 2/3 : ARG ENV_NAME=production
 ---> Running in 344b3a61ee3d
 ---> 0167a3895668
Removing intermediate container 344b3a61ee3d
Step 3/3 : RUN echo $ENV_NAME
 ---> Running in 43d9ac3847ec
$ENV_NAME
 ---> 8cdaf3c07ed8
Removing intermediate container 43d9ac3847ec
Successfully built 8cdaf3c07ed8

With Windows containers, the ARG name is being echoed instead of the value.
Output of docker version:
Client:
 Version:      17.03.1-ce
 API version:  1.27
 Go version:   go1.7.5
 Git commit:   c6d412e
 Built:        Tue Mar 28 00:40:02 2017
 OS/Arch:      windows/amd64

Server:
 Version:      17.03.1-ce
 API version:  1.27 (minimum version 1.24)
 Go version:   go1.7.5
 Git commit:   c6d412e
 Built:        Tue Mar 28 00:40:02 2017
 OS/Arch:      windows/amd64
 Experimental: true

Output of docker info:
Containers: 11
 Running: 0
 Paused: 0
 Stopped: 11
Images: 93
Server Version: 17.03.1-ce
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.953.amd64fre.rs1_release_inmarket.170303-1614)
Operating System: Windows 10 Pro
OSType: windows
Architecture: x86_64
CPUs: 8
Total Memory: 15.94 GiB
Name: DT_AT
ID: P5CL:JS6N:WOLG:ERRU:A44J:5Q5O:7PQE:25QZ:UBFU:AXEF:SYDG:AZTS
Docker Root Dir: C:\ProgramData\Docker
Debug Mode (client): false
Debug Mode (server): true
 File Descriptors: -1
 Goroutines: 20
 System Time: 2017-04-03T12:15:26.8548571+01:00
 EventsListeners: 0
Registry: https://index.docker.io/v1/
Experimental: true
Insecure Registries:
 <IP_ADDRESS>/8
Live Restore Enabled: false

Does it work if you echo % ENV_NAME% ?

@thaJeztah That does fix this. Is the special character ($ or % %) specified by docker or by something else?

It's the way you print environment variables on Windows :smile:


Inline SCSS styles truncated

OS:
OSX
Versions:
angular-cli: 1.0.0-beta.22-1
node: 6.3.1
os: darwin x64
Repro steps:

Convert repo to scss
Import bootstrap into styles.scss with @import "../node_modules/bootstrap/scss/bootstrap-flex";
Button styles get applied but column styles are not being applied.  Looking at the inline import it appears cutoff. Maybe there is a line limit on the imported styles?

Note:
When importing the .scss file in the angular-cli.json file via the styles attribute the issue still persists. However switching to the compiled css file in ../node_modules/bootstrap/css/bootstrap-flex.min.css "fixes it"
Here is the demo repo: https://github.com/zackarychapple/bootstrap-ng2

Looks to be the same / similar issue as #3500

Dupe of #3500

@hansl while this is similar it is broken behavior, can we possibly bump the priority for https://github.com/angular/angular-cli/issues/3500 to not be nice to have


data does not seem to be checked in

https://github.com/ActivitySim/activitysim-estimation-example/tree/main/data_sf/survey_data

Yes, the data isn't checked in for this repo.  The reason why this repo exists is to migrate away from large binary data files checked in to Git, and instead just attach the data as asset on a "release".


Make Configuration use IOptions

The code currently assumes that all configuration sources are applied prior to adding KeycloakAuthentication/Authorization/...
This is not always the case and goes against the way other .NET components work.
By using services.AddOptions<...>() and things like the following, the code can be rewritten in a way that supports any order of configuration, by sacrificing minimal performance due to serviceProvider.GetRequiredService<IOptions<..>>()-Lookups.
// we can make use of DI for configuring JwtBearerOptions
// by registering it with the same name as the scheme itself
services.AddOptions<JwtBearerOptions>(JwtBearerDefaults.AuthenticationScheme)
    .Configure((JwtBearerOptions opts, IOptions<KeycloakAuthenticationOptions> keycloakOption)
        => { /* ... */})
// ...
services.AddAuthentication(JwtBearerDefaults.AuthenticationScheme)
    .AddJwtBearer(/* JwtBearerDefaults.AuthenticationScheme */);

Also current IConfiguration overloads force Keycloak or any other named Key as the location for the values, as such the following appsettings could not be used with the current way:
{
  "AuthServerUrl": "..."
}

i propose any IConfiguration-Overload assumes that it's already at the correct location (e.g. by configuration.GetSection("here:is:keycloak")) and a new overload that takes in the IConfiguration and a section name, which may be set to null to use default Keycloak section name, though this reduces the visibility of configuration sources by a bit.

The way the ASP.NET Core pipeline works, we can't really make use of IOptionsSnapshot or IOptionsMonitor, as the AuthenticationOptions only get applied once.

The a good point, added to 2.0.0 scope

Could you please provide an example of overload that you are talking about?

ref: https://github.com/NikiforovAll/keycloak-authorization-services-dotnet/issues/53

Added since 2.0.0-pre2


WIP [Depends on ManageIQ/manageiq#1584] Openstack fix metrics saving mechanism

For the BZ link, can you put it on its own line in the commit message?  The auto-bz-comment bot right now only detects when the link is on its own line.  I'll add an issue on the bot to support the line starting with words like "Fixes"

@blomquisg Please review.

WIP: need to write tests for metrics processing first

https://github.com/ManageIQ/manageiq/pull/1584 is merged.  If this is ready for review/merge, please remove the WIP from the title of this PR.

it's ready for review

One small nitpick.  Otherwise :+1: