Patch 7.0 Destroyed Cooldown API

I noticed that attribute and items .Cooldown doesnt work with patch 7.0 .
Anyone having this issue ?

Will look into it in the next few days. Anything else get broken with 7.0?

On Dec 16, 2016, at 10:13, gentmat<EMAIL_ADDRESS>wrote:
I noticed that attribute and items .Cooldown doesnt work with patch 7.0 .
Anyone having this issue ?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

I looked into this. The cooldowns aren't being sent to the library properly. It's always sending 0. It's an issue with Dota 2 and should be reported to Valve if possible.
I also looked into Talents. GSI does send talent information over, however, they are all labeled "attributes" and so due to a limitation in Newtonsoft, it does not allow multiple parameters to have the same name. And so it parses just one talent. I will see if I can find a workaround later for this.

"It's always sending 0" It was always working prior patch 7 .
Maybe they will fix it then i ll update the issue when they do . About the
talent tree (yeah that would be nice)
good job and hope you the best .
On Mon, Dec 19, 2016 at 1:11 AM, Anton Pupkov<EMAIL_ADDRESS>wrote:

I looked into this. The cooldowns aren't being sent to the library
properly. It's always sending 0. It's an issue with Dota 2 and should be
reported to Valve if possible.
I also looked into Talents. GSI does send talent information over,
however, they are all labeled "attributes" and so due to a limitation in
Newtonsoft, it does not allow multiple parameters to have the same name.
And so it parses just one talent. I will see if I can find a workaround
later for this.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/antonpup/Dota2GSI/issues/11#issuecomment-267846950,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AE9in4uBJ-TmxeRM8Iznub6KbZ_8vetlks5rJaGcgaJpZM4LPVuC
.

Looks like now the game is sending cooldowns properly.
"ability0": {
                        "name": "meepo_earthbind",
                        "level": 1,
                        "can_cast": false,
                        "passive": false,
                        "ability_active": true,
                        "cooldown": 8,
                        "ultimate": false
                },

Is the cooldown part of the issue resolved then?

I m not playing from 2 weeks ! hospital :(
I ll check it when i come back into game for sure.
Ty for the update
On Wed, Jan 25, 2017 at 1:59 PM, Artyom Desyatnikov <
<EMAIL_ADDRESS>wrote:

Looks like now the game is sending cooldowns properly.
"ability0": {
"name": "meepo_earthbind",
"level": 1,
"can_cast": false,
"passive": false,
"ability_active": true,
"cooldown": 8,
"ultimate": false
},
Is the cooldown part of the issue resolved then?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/antonpup/Dota2GSI/issues/11#issuecomment-275066274,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AE9in4s5uGee8roI3Z2N3Ge7tAj0UKeuks5rVx0NgaJpZM4LPVuC
.


CASMMON-127:port Prometheus Alerts and Notifications to alarta

Description
As part of SMH integration with SMF integration Port Prometheus Alerts and Notifications.
https://jira-pro.its.hpecorp.net:8443/browse/CASMMON-127
CASMMON-127 : port Prometheus Alerts and Notifications to alerta
EPIC: CASM-1606 : https://jira-pro.its.hpecorp.net:8443/browse/CASM-1606

I did some linting.

I also pulled in linting of the email alert page that the new Alerta page used as a template, in order to keep them consistent.

I reverted the changes that Rusty objected to, so we can hopefully merge this guy. The author was asking me about it.

Note that the automatic linter does apparently object to multiple top level headers, so we're either going to have to make an exception to our policy and merge this despite the failure, or I will need to add those linting changes into this PR.


⚠ Orpheus has degraded performance

In 343c439, Orpheus ($OPS) experienced degraded performance:

HTTP code: 200
Response time: 12316 ms

Resolved: Orpheus performance has improved in e96b115 after 5 minutes.


ENH: Added overwrite parameter to epochs.save

Reference issue
Fixes #5627
What does this implement/fix?
I added an overwrite parameter to epochs.save, similar to that in raw.save.
Additional information
I set the default to be overwrite=False, for consistency with raw.save. This changes the behavior of epochs.save. Is this correct or should I add a deprecation warning?
I had to add overwrite=True as an argument to epochs.save in a number of unit tests, so that the behavior would be consistent with previous versions of epochs.save. Please also let me know if this is appropriate.

@katarinaslama you'll need to update what's new too

@katarinaslama see why CIs are complaining. Thx

Great - all green. Ready for reviews @katarinaslama ?

Thanks!

Thank you!

This introduced a couple of warnings in examples, which we treat as errors:
https://circleci.com/gh/mne-tools/mne-python/12115
By default CircleCI only builds changed examples until they get merged into master, so this is not uncommon. @katarinaslama can you open a tiny PR to fix these? (Then CircleCI will build the failed examples in the PR, because they are changed, so the green CIs should indicate master will be green after merge.)

 Otherwise I will do it.


Cleanup Bibdata and Bibcollection

Looking at the BibData and Bib collection seems like they are doing a lot and lots of functionality/responsibilities are packed in this single class which also makes this class harder to reuse.
This commit takes the first step to clean up these classes, and initially, it adds a simple parser that will extract out the attributes from any valid XML file.

Nicely done. Thank you @abunashir !


independent versioning compose compiler

Now that Android Team introduce independent versioning that starts with the Compose Compiler version, i think we could separate the compiler version so we can update Kotlin version indepently.

Wow thank you for the fast feedback! Looks good to me 👍


Add support for UnreachableException in .NET code

.NET 7 added the UnreachableException class, which is meant to be thrown when executing a branch that isn't isn't expected to execute, due to the developer believing it to be unreachable. The Microsoft code coverage tools should analyze code that throws UnreachableException and reduce the number of coverable lines and branches accordingly.
Consider the following example:
using System.Diagnostics;

enum E
{
    A,
    B,
    C,
}

static partial class C
{
    public static void M()
    {
        E value = GetValue();

        switch (value) // line 16
        {
            case E.A:
                PerformActionA();
                break;

            case E.B:
                PerformActionB();
                break;

            case E.C:
                PerformActionC();
                break;

            default:
                throw new UnreachableException(); // line 31
        }
    }
}

Currently, this will yield coverage data for M() like so:
<method line-rate="0.9090909090909091" branch-rate="0.75" complexity="4" name="M" signature="()">
  <lines>
    <line number="13" hits="1" branch="False" />
    <line number="14" hits="1" branch="False" />
    <line number="16" hits="1" branch="True" condition-coverage="75% (3/4)">
      <conditions>
        <condition number="0" type="switch" coverage="75%" />
      </conditions>
    </line>
    <line number="19" hits="1" branch="False" />
    <line number="20" hits="1" branch="False" />
    <line number="23" hits="1" branch="False" />
    <line number="24" hits="1" branch="False" />
    <line number="27" hits="1" branch="False" />
    <line number="28" hits="1" branch="False" />
    <line number="31" hits="0" branch="False" />
    <line number="33" hits="1" branch="False" />
  </lines>
</method>

We see that the condition on line 16 shows four branches (one of which is the default case and is uncovered) and that line 31 shows no hits. If the developer has otherwise guaranteed that GetValue() will return a valid value of E—one of the known enum cases—and they handle the remaining case in the above sample by throwing UnreachableException, the code coverage findings should reflect that. Given the above example, if the code coverage tools were aware of UnreachableException, I would instead expect to see the following coverage data:
<method line-rate="1" branch-rate="1" complexity="4" name="M" signature="()">
  <lines>
    <line number="13" hits="1" branch="False" />
    <line number="14" hits="1" branch="False" />
    <line number="16" hits="1" branch="True" condition-coverage="100% (3/3)">
      <conditions>
        <condition number="0" type="switch" coverage="100%" />
      </conditions>
    </line>
    <line number="19" hits="1" branch="False" />
    <line number="20" hits="1" branch="False" />
    <line number="23" hits="1" branch="False" />
    <line number="24" hits="1" branch="False" />
    <line number="27" hits="1" branch="False" />
    <line number="28" hits="1" branch="False" />
    <line number="33" hits="1" branch="False" />
  </lines>
</method>

Recognizing the developer's intent with regards to intentionally unreachable code will provide for more accurate code coverage results, and will make the tooling more usable for teams who want to enforce 100% code coverage in their test suites.
References:

UnreachableException class
API Proposal: UnreachableException
Add UnreachableException

Thanks for the suggestion. We have added it to our backlog and will work on it once it gets prioritized.


Trouble to win the block!!

My farm is just over a petabyte. I am using windows 10 and GUI. All hardware class Interprays. The program indicates the time interval between winning blocks is 44 minutes, but in reality, about two blocks are won in 24 hours. I invested 10 coins for staking - I did not feel the increase in profit. At the moment there is a similar problem with chia 1.6.1 and not only for me. What to do?

Please update to the latest version


 show "real" URL in generated ?

Hi
I noticed that by using <localized-link> the generated URL in the <a> tag is the "global" one and not the one with the language. This maybe could give SEO/Crawling problems with Google?
For example I have and /about page.
If I'm on / and have a <localized-link>  to /about, it is fine.
If I'm on /fr/ and have a <localized-link> to /about, the generated link in the anchor tag will be /about and not /fr/about, even if by clicking it correctly go to the fr page.
It's there a workout to generated the "correct" url?
Edit:
Just saw the example and it works like I wanted, but it's using <localized-link to="..."> while I'm using
<localized-link :to="{name: 'product', params: { id: id }}">

so I guess I need to pass it in the params?

Hi @GregoryWullimann, yes, this is known issue, I haven't gotten around to fixing it yet, sorry 🙁
Duplicate of #9.


docs: Add Code of Conduct

Changes

Add official CODE_OF_CONDUCT.md (provided by GitHub)

Due to that we are also missing out on some checks on the community guidelines checklist

Also, Please provide an Email to include that in the Code of Conduct

Contribution towards GSsoc`22, Thank you

Hey,I want to work upon this issue under GSSOC 2022.


Standard Surface to glTF PBR Translation Graph

This PR introduces a simple nodegraph for mapping standard_surface.mtlx material documents to gltf_pbr.mtlx material documents. It was implemented as part of my Summer '22 internship with Autodesk as part of a larger Standard Surface => glTF export workflow.
The parameters supported by this translation are simply passed through, or multiplied in the case of weighted colors.

Translation
We map properties as follows - items in the glTF PBR column are outputs, items in the Standard Surface column are inputs.

glTF PBR
Standard Surface

base_color
multiply(base_color, base)

metallic
dot(metallic)

roughness
dot(specular_roughness)

transmission
dot(transmission)

specular
dot(specular)

specular_color
dot(specular_color)

ior
dot(specular_ior)

sheen_color
multiply(sheen_color, sheen)

sheen_roughness
dot(sheen_roughness)

clearcoat
dot(coat)

clearcoat_roughness
dot(coat_roughness)

emissive
dot(emission_color)

emissive_strength
dot(emission)

Further work
Transmission
Our mapping of transmission (Standard Surface specular transmission) to transmission (glTF KHR_materials_transmission) covers only the transmission weight. Better approximation of Standard Surface's transmission behavior should be possible via the KHR_materials_volume properties which are supported by the gltf_pbr.mtlx node definition.
Coat
We map Standard Surface's coating to KHR_materials_clearcoat. KHR clearcoat does not support coat color; this behavior can be approximated by mixing incoming base color and coat color, but was not sufficiently explored in the course of this work and is omitted on this PR.
Thin film
Standard Surface's specular transmission supports a thin film behavior that may be mappable to KHR_materials_iridescence, but this extension is not supported by the current implementation of the gltf_pbr node definition.
Other behaviors
Any behaviors not listed on this PR were not explored and are not supported by this implementation of the translation nodegraph.
Other work
Other work implemented for this workflow includes pipelines for translating test materials to native *.gltf and rendering test scenes, there is some discussion on ASWF slack in materialx-gltf about where it may live.

This proposal looks promising, thanks @roblesch and @ashwinbhat.
My sense is that we'd want this translation pathway to reach the same level of visual parity as the existing graph from Standard Surface to UsdPreviewSurface before moving forward.  Running a few local tests with materials such as standard_surface_plastic.mtlx and standard_surface_copper.mtlx, it doesn't look like we're quite hitting that level of parity yet.
As one example, there isn't yet any handling for coat attenuation in the new translation graph, so the copper material loses all of its metal coloration when translated to gltf_pbr.  Additionally, there seems to be an issue with the handling of dielectric specular that shows up as a loss of highlights when translating the plastic material to gltf_pbr.

Hi @jstone-lucasfilm, thank you for the feedback and for your suggestions on further improvements! Here's the current results with the most recent push - Standard surface on the left, glTF pbr on the right.

This looks excellent, thanks @roblesch!
One additional change that I would recommend is to add default values for each input in the new standard_surface_to_gltf_pbr node.  This will guarantee that Standard Surface materials without bindings for these inputs will correctly inherit their correct defaults during shader translation.
A good example to test this with is standard_surface_brick_procedural.mtlx, which only binds three of the Standard Surface inputs, leaving all others at their default values.

I've added default input values. Thank you for the continued input @jstone-lucasfilm!


Azure Account signin failing silently if account has no Azure tenants

Trying to log in with an account that doesn't have any Azure tenants, nothing happens after logging in and no indication an error occurred. Console has this :

We should ideally surface that to the user so they know why it didn't add.

@Charles-Gagnon or @aaomidi  do we know if this is a regression from 1.14.1?

Merged into 1.15 branch https://github.com/microsoft/azuredatastudio/commit/fb4ab6b5016e06460407bbd6beed29eff66ea3b4


environment error

Hello, thanks for the great work!
But when I create an environment following https://github.com/open-mmlab/mmdetection/blob/v2.18.0/docs/get_started.md for training, the import error has came.

OS: Linux
CUDA: 11.7
pytorch: 1.13

I hava  meet the same problem too, and I have tride changed the version but failed, because it will raise other error, can you tell me the version of  mmcv, mmcv-full, and mmdet?

I have solved the problem. the environment as follow:
mmcv-full           1.3.14
mmdet               2.18.0
numpy               1.23.5
Don't install the mmcv >=2.0.0 and the numpy <1.24.0 is better.

I have solved the problem. the environment as follow: mmcv-full 1.3.14 mmdet 2.18.0 numpy 1.23.5 Don't install the mmcv >=2.0.0 and the numpy <1.24.0 is better.
May I ask if you encountered 'FasterRCNN: 'CLIPResNet is not in the models registry' while running 'bash tools/dist_train.sh configs/singledataset/clip_end2end_faster_rcnn_r50_c4_1x_coco.py 8 --cfg-options load_from=regionclip_pretrained-cc_rn50_mmdet.pth' in this environment?"

you can  pip unistall mmdet and try python setup.py develop


Globalnet doesn't work:  pod cannot communicate across clusters

What happened:
Hi teams!  I have a two clusters with the overlaps cidr:
cluster1:
pod: <IP_ADDRESS>/16 service: <IP_ADDRESS>/18
globalCIDR: <IP_ADDRESS>/24

cluster2:
pod: <IP_ADDRESS>/16 service: <IP_ADDRESS>/18
globalCIDR: <IP_ADDRESS>/24

subctl show all for cluster1
[root@master1 ~]# subctl show all
Cluster "cluster.local"
 ✓ Detecting broker(s)
 ✓ No brokers found

 ✓ Showing Connections
GATEWAY           CLUSTER    REMOTE IP     NAT   CABLE DRIVER   SUBNETS         STATUS      RTT avg.
cluster2master1   cluster2   <IP_ADDRESS>   no    libreswan      <IP_ADDRESS>/24   connected   1.796365ms

 ✓ Showing Endpoints
CLUSTER    ENDPOINT IP   PUBLIC IP      CABLE DRIVER   TYPE
cluster1   <IP_ADDRESS>   <IP_ADDRESS>   libreswan      local
cluster2   <IP_ADDRESS>   <IP_ADDRESS>   libreswan      remote

 ✓ Showing Gateways
NODE      HA STATUS   SUMMARY
master1   active      All connections (1) are established

 ✓ Showing Network details
    Discovered network details via Submariner:
        Network plugin:  calico
        Service CIDRs:   [<IP_ADDRESS>/18]
        Cluster CIDRs:   [<IP_ADDRESS>/16]
        Global CIDR:     <IP_ADDRESS>/24

 ✓ Showing versions
COMPONENT                       REPOSITORY                      VERSION
submariner-gateway              quay.m.daocloud.io/submariner   0.14.0
submariner-routeagent           quay.m.daocloud.io/submariner   0.14.0
submariner-globalnet            quay.m.daocloud.io/submariner   0.14.0
submariner-operator             quay.m.daocloud.io/submariner   0.14.0
submariner-lighthouse-agent     quay.m.daocloud.io/submariner   0.14.0
submariner-lighthouse-coredns   quay.m.daocloud.io/submariner   0.14.0

# subctl diagnose all
[root@master1 ~]# subctl diagnose all
Cluster "cluster.local"
 ✓ Checking Submariner support for the Kubernetes version
 ✓ Kubernetes version "v1.23.7" is supported

 ✓ Checking Submariner support for the CNI network plugin
 ✓ The detected CNI network plugin ("calico") is supported
 ✓ Trying to detect the Calico ConfigMap
 ✓ Calico CNI detected, checking if the Submariner IPPool pre-requisites are configured
 ✓ Checking gateway connections
 ✓ All connections are established
 ✓ Globalnet deployment detected - checking if globalnet CIDRs overlap
 ✓ Clusters do not have overlapping globalnet CIDRs
 ✓ Checking Submariner pods
 ✓ All Submariner pods are up and running
 ⚠ Starting with Kubernetes 1.23, the Pod Security admission controller expects namespaces to have security labels. Without these, you will see warnings in subctl's output. subctl should work fine, but you can avoid the warnings and ensure correct behavior by adding at least one of these labels to the namespace "submariner-operator":
  pod-security.kubernetes.io/enforce=privileged
  pod-security.kubernetes.io/audit=privileged
  pod-security.kubernetes.io/warn=privileged

 ✓ Checking if gateway metrics are accessible from non-gateway nodes
 ✓ The gateway metrics are accessible
 ⚠ Starting with Kubernetes 1.23, the Pod Security admission controller expects namespaces to have security labels. Without these, you will see warnings in subctl's output. subctl should work fine, but you can avoid the warnings and ensure correct behavior by adding at least one of these labels to the namespace "submariner-operator":
  pod-security.kubernetes.io/enforce=privileged
  pod-security.kubernetes.io/audit=privileged
  pod-security.kubernetes.io/warn=privileged

 ✓ Checking if globalnet metrics are accessible from non-gateway nodes
 ✓ The globalnet metrics are accessible
 ⚠ Starting with Kubernetes 1.23, the Pod Security admission controller expects namespaces to have security labels. Without these, you will see warnings in subctl's output. subctl should work fine, but you can avoid the warnings and ensure correct behavior by adding at least one of these labels to the namespace "submariner-operator":
  pod-security.kubernetes.io/enforce=privileged
  pod-security.kubernetes.io/audit=privileged
  pod-security.kubernetes.io/warn=privileged

 ✓ Checking Submariner support for the kube-proxy mode
 ✓ The kube-proxy mode is supported
 ⚠ Starting with Kubernetes 1.23, the Pod Security admission controller expects namespaces to have security labels. Without these, you will see warnings in subctl's output. subctl should work fine, but you can avoid the warnings and ensure correct behavior by adding at least one of these labels to the namespace "submariner-operator":
  pod-security.kubernetes.io/enforce=privileged
  pod-security.kubernetes.io/audit=privileged
  pod-security.kubernetes.io/warn=privileged

⢀⡱ Checking the firewall configuration to determine if intra-cluster VXLAN traffic is allowed  ⚠ Starting with Kubernetes 1.23, the Pod Security admission controller expects namespaces to have security labels. Without these, you will see warnings in subctl's output. subctl should work fine, but you can avoid the warnings and ensure correct behavior by adding at least one of these labels to the namespace "submariner-operator":
  pod-security.kubernetes.io/enforce=privileged
  pod-security.kubernetes.io/audit=privileged
  pod-security.kubernetes.io/warn=privileged

 ✓ Checking the firewall configuration to determine if intra-cluster VXLAN traffic is allowed
 ✓ The firewall configuration allows intra-cluster VXLAN traffic
 ✓ Checking Globalnet configuration
 ✓ Globalnet is properly configured and functioning

 ✓ Checking if services have been exported properly
 ✓ All services have been exported properly

Skipping inter-cluster firewall check as it requires two kubeconfigs. Please run "subctl diagnose firewall inter-cluster" command manually.

subctl show all for cluster2:
[root@cluster2master1 ~]# subctl show all
Cluster "cluster.local"
 ✓ Detecting broker(s)
 ✓ No brokers found

 ✓ Showing Connections
GATEWAY   CLUSTER    REMOTE IP     NAT   CABLE DRIVER   SUBNETS         STATUS      RTT avg.
master1   cluster1   <IP_ADDRESS>   no    libreswan      <IP_ADDRESS>/24   connected   1.962336ms

 ✓ Showing Endpoints
CLUSTER    ENDPOINT IP   PUBLIC IP      CABLE DRIVER   TYPE
cluster2   <IP_ADDRESS>   <IP_ADDRESS>   libreswan      local
cluster1   <IP_ADDRESS>   <IP_ADDRESS>   libreswan      remote

 ✓ Showing Gateways
NODE              HA STATUS   SUMMARY
cluster2master1   active      All connections (1) are established

 ✓ Showing Network details
    Discovered network details via Submariner:
        Network plugin:  calico
        Service CIDRs:   [<IP_ADDRESS>/18]
        Cluster CIDRs:   [<IP_ADDRESS>/16]
        Global CIDR:     <IP_ADDRESS>/24

 ✓ Showing versions
COMPONENT                       REPOSITORY                      VERSION
submariner-gateway              quay.m.daocloud.io/submariner   0.14.0
submariner-routeagent           quay.m.daocloud.io/submariner   0.14.0
submariner-globalnet            quay.m.daocloud.io/submariner   0.14.0
submariner-operator             quay.m.daocloud.io/submariner   0.14.0
submariner-lighthouse-agent     quay.m.daocloud.io/submariner   0.14.0
submariner-lighthouse-coredns   quay.m.daocloud.io/submariner   0.14.0
# subctl diagnose all
[root@cluster2master1 ~]# subctl diagnose all
Cluster "cluster.local"
 ✓ Checking Submariner support for the Kubernetes version
 ✓ Kubernetes version "v1.23.7" is supported

 ✓ Checking Submariner support for the CNI network plugin
 ✓ The detected CNI network plugin ("calico") is supported
 ✓ Trying to detect the Calico ConfigMap
 ✓ Calico CNI detected, checking if the Submariner IPPool pre-requisites are configured
 ✓ Checking gateway connections
 ✓ All connections are established
 ✓ Globalnet deployment detected - checking if globalnet CIDRs overlap
 ✓ Clusters do not have overlapping globalnet CIDRs
 ✓ Checking Submariner pods
 ✓ All Submariner pods are up and running
 ⚠ Starting with Kubernetes 1.23, the Pod Security admission controller expects namespaces to have security labels. Without these, you will see warnings in subctl's output. subctl should work fine, but you can avoid the warnings and ensure correct behavior by adding at least one of these labels to the namespace "submariner-operator":
  pod-security.kubernetes.io/warn=privileged
  pod-security.kubernetes.io/enforce=privileged
  pod-security.kubernetes.io/audit=privileged

 ✓ Checking if gateway metrics are accessible from non-gateway nodes
 ✓ The gateway metrics are accessible
 ⚠ Starting with Kubernetes 1.23, the Pod Security admission controller expects namespaces to have security labels. Without these, you will see warnings in subctl's output. subctl should work fine, but you can avoid the warnings and ensure correct behavior by adding at least one of these labels to the namespace "submariner-operator":
  pod-security.kubernetes.io/enforce=privileged
  pod-security.kubernetes.io/audit=privileged
  pod-security.kubernetes.io/warn=privileged

 ✓ Checking if globalnet metrics are accessible from non-gateway nodes
 ✓ The globalnet metrics are accessible
 ⚠ Starting with Kubernetes 1.23, the Pod Security admission controller expects namespaces to have security labels. Without these, you will see warnings in subctl's output. subctl should work fine, but you can avoid the warnings and ensure correct behavior by adding at least one of these labels to the namespace "submariner-operator":
  pod-security.kubernetes.io/audit=privileged
  pod-security.kubernetes.io/warn=privileged
  pod-security.kubernetes.io/enforce=privileged

 ✓ Checking Submariner support for the kube-proxy mode
 ✓ The kube-proxy mode is supported
 ⚠ Starting with Kubernetes 1.23, the Pod Security admission controller expects namespaces to have security labels. Without these, you will see warnings in subctl's output. subctl should work fine, but you can avoid the warnings and ensure correct behavior by adding at least one of these labels to the namespace "submariner-operator":
  pod-security.kubernetes.io/enforce=privileged
  pod-security.kubernetes.io/audit=privileged
  pod-security.kubernetes.io/warn=privileged

⢀⡱ Checking the firewall configuration to determine if intra-cluster VXLAN traffic is allowed  ⚠ Starting with Kubernetes 1.23, the Pod Security admission controller expects namespaces to have security labels. Without these, you will see warnings in subctl's output. subctl should work fine, but you can avoid the warnings and ensure correct behavior by adding at least one of these labels to the namespace "submariner-operator":
  pod-security.kubernetes.io/enforce=privileged
  pod-security.kubernetes.io/audit=privileged
  pod-security.kubernetes.io/warn=privileged

 ✓ Checking the firewall configuration to determine if intra-cluster VXLAN traffic is allowed
 ✓ The firewall configuration allows intra-cluster VXLAN traffic
 ✓ Checking Globalnet configuration
 ✓ Globalnet is properly configured and functioning

 ✓ Checking if services have been exported properly
 ✓ All services have been exported properly

Skipping inter-cluster firewall check as it requires two kubeconfigs. Please run "subctl diagnose firewall inter-cluster" command manually.

pod cannot communicate across clusters:
# cluster1
[root@master1 ~]# kubectl get po -o wide
NAME                                READY   STATUS    RESTARTS   AGE   IP              NODE      NOMINATED NODE   READINESS GATES
dao2048-dao-2048-7994b8fc96-7trqc   1/1     Running   0          15h   <IP_ADDRESS>   master1   <none>           <none>
dao2048-dao-2048-7994b8fc96-9qb5d   1/1     Running   0          16h   <IP_ADDRESS>   worker4   <none>           <none>

# cluster2
[root@cluster2master1 ~]# kubectl get po -o wide
NAME                        READY   STATUS    RESTARTS   AGE   IP              NODE              NOMINATED NODE   READINESS GATES
dao-2048-6d6c45bbf9-d4smw   1/1     Running   0          18h   <IP_ADDRESS>    cluster2master1   <none>           <none>
dao-2048-6d6c45bbf9-rvgfm   1/1     Running   0          18h   <IP_ADDRESS>   cluster2worker1   <none>           <none>
[root@cluster2master1 ~]# kubectl exec -it dao-2048-6d6c45bbf9-d4smw sh
kubectl exec [POD] [COMMAND] is DEPRECATED and will be removed in a future version. Use kubectl exec [POD] -- [COMMAND] instead.
/ # ping <IP_ADDRESS>
PING <IP_ADDRESS> (<IP_ADDRESS>): 56 data bytes
^C
--- <IP_ADDRESS> ping statistics ---
6 packets transmitted, 0 packets received, 100% packet loss

What you expected to happen:
pod can be communicate across clusters
How to reproduce it (as minimally and precisely as possible):
Anything else we need to know?:
calico ippools:
# cluster1
[root@master1 ~]# calicoctl get ippools -o wide
NAME                  CIDR            NAT     IPIPMODE   VXLANMODE   DISABLED   DISABLEBGPEXPORT   SELECTOR
cluster2-globalcidr   <IP_ADDRESS>/24   false   Never      Never       true       false              all()
default-pool          <IP_ADDRESS>/16   true    Never      Always      false      false              all()
default-pool-ipv6     fc01::/112      false   Never      Always      false      false              all()

# cluster2
[root@cluster2master1 ~]# calicoctl get ippools -o wide
NAME                  CIDR            NAT     IPIPMODE   VXLANMODE   DISABLED   DISABLEBGPEXPORT   SELECTOR
cluster1-gloablcidr   <IP_ADDRESS>/24   false   Never      Never       true       false              all()
default-pool          <IP_ADDRESS>/16   true    Never      Always      false      false              all()
default-pool-ipv6     fc01::/112      false   Never      Always      false      false              all()

cluster1.tgz
cluster2.tgz
Environment:

Diagnose information (use subctl diagnose all):
Gather information (use subctl gather):
Cloud provider or hardware configuration:
Install tools:
Others:

Hi teams! I would be very grateful if someone helped me, Thanks!

Hi @cyclinder , thanks for reaching out.
In GlobalNet environment you should ping the globalIP of the remote pod/service and not the original IP address (<IP_ADDRESS> in your case).
You can verify inter-cluster connectivity using service as explained here
If you want to test pod 2 pod connectivity, you should first create GlobalEgressIP (you can find more details here ) resource for the remote pod, you can find the assigned global IP address under status section, and then ping this globalIP.
Let us know if you run into any more issues

Thanks for the help! @yboaron
Yes, In GlobalNet environment, We can't ping the Pod's original IP address, I followed your steps, and I created and exported a remote svc. I verify the service's connectivity, it works well.
And I try to test pod to pod connectivity, I created a GlobalEgressIP with podSelector for remote pod：
root@controller-node-1:~# kubectl get globalegressips.submariner.io dao-pods -o yaml
apiVersion: submariner.io/v1
kind: GlobalEgressIP
metadata:
  annotations:
    kubectl.kubernetes.io/last-applied-configuration: |
      {"apiVersion":"submariner.io/v1","kind":"GlobalEgressIP","metadata":{"annotations":{},"name":"dao-pods","namespace":"default"},"spec":{"numberOfIPs":1,"podSelector":{"matchLabels":{"app":"dao2048"}}}}
  creationTimestamp: "2023-03-01T02:41:17Z"
  generation: 2
  name: dao-pods
  namespace: default
  resourceVersion: "5315702"
  uid: 546dd040-907c-429c-9001-c36829a4702e
spec:
  numberOfIPs: 1
  podSelector:
    matchLabels:
      app: dao2048
status:
  allocatedIPs:
  - <IP_ADDRESS>
  conditions:
  - lastTransitionTime: "2023-03-01T02:41:17Z"
    message: Allocated 1 global IP(s)
    reason: Success
    status: "True"
    type: Allocated

But I can't ping or curl this IP,  Is this the expected behavior？

And I try to test pod to pod connectivity, I created a GlobalEgressIP with podSelector for remote pod：

GlobalEgressIP as the name suggests is only for Egress traffic (i.e., the associated globalIP will be used as SNAT IP for any outbound traffic that matches the GlobalEgressIP. This globalIP cannot be used as an ingressIP. If you are interested to connect to a Pod directly instead of a service, you can create an Headless Service or a statefulSet where each backend pod will get its unique globalIP which can be used as IngressIP to talk to the pod. You can refer to the following examples.
https://submariner.io/getting-started/quickstart/openshift/globalnet/#deploy-headless-service
https://submariner.io/getting-started/quickstart/openshift/globalnet/#verify-statefulsets

@sridhargaddam Thanks for the explanation! I see, I verified this through some tests.
Now I close this issue, thanks all!

Ack, got it,
I thought that GlobalEgressIP allocated for specific pod will be used also for inbound traffic.
Thanks @sridhargaddam !


fix(unikraft): Hardcode language libraries before libcs

Prerequisite checklist

[x] Read the contribution guidelines regarding submitting new changes to the project;
[x] Tested your changes against relevant architectures and platforms;
[x] Ran make fmt on your commit series before opening this PR;
[ ] Updated relevant documentation.

Description of changes

This commit hardcodes all known language libraries that need to sit before musl/newlib.
This is a temporary fix as mentioned in the comment above them.
Before that is fixed, all libraries known to cause problems should be added here.

Should we also add libgo to the list (it's also put before the libc)?

sure thing

added


Repository

My Introduction
Name
Asa Marjew
Class
202
About me

Skill level
Intermediate
GitHub username
https://github.com/AsaMarjew
GitHub repository
https://github.com/AsaMarjew/js-bootcamp-19-20/tree/master/template-repo

👋 Asa
Good start! Your repo does feel a bit 'scanty', you might want to add more notes while you continue working on front-end.


Feature Request: Make it possible to remotely control mouse/keyboard input

I don't know how feasible it would be to implement, but it seems fun for trolling purposes.

The goal of this project is to be troll-y, but not in a way that could be to do anything malicious. Full control of someone's computer can definitely be used maliciously, which is why this doesn't allow that.

TrollRAT is not made for data stealing, full control or other bad things.

If the RAT shouldn't be used maliciously, then why is there a process killer, with a Crash Windows option? That seems like something that could at the very least corrupt data, right?

"Some of this tool can be used maliciously, so why not make it more malicious?"
Because being malicious is not the goal.
It's for trolling. Trolling can be malicious but that's still not the goal of the program.


.NET 6.0 breaking change for signing emitted assembly

Interface interceptor code generator fails when setting sign key of emitted assembly.

dotnet/runtime#69311


Error in beir/beir/retrieval/search/sparse/sparse_search.py

https://github.com/UKPLab/beir/blob/568f4c34fa0be1901e2aaa8479978c9e54a1e377/beir/retrieval/search/sparse/sparse_search.py#L28-L34
Hello,
I think there is an error in sparse_search.py; only the first query in each batch is evaluated.
Thank you!

Indeed! An easy fix would be to remove the step size self.batch_size?


[BRD-166-167] - Help Button and Hide Burger Icon

implemented the help button with redirection to the doc page and burger icon is not rendered when plugin list is empty

Pull Request Test Coverage Report for Build 767587130

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 100.0%

Totals

Change from base Build 767494548:
0.0%

Covered Lines:
77

Relevant Lines:
77

💛  - Coveralls


Support the ability to create workshop on self provisioned EC2 instance

Is your feature request related to a problem? Please describe.
i'm setting up an internal sandbox so we can test, modify, integrate with ITSI for developing lantern material.  This will be used for a team of 4, so i don't want to use multipass on laptop
Describe the solution you'd like
Ability to spin up instance ready for workshop.
Describe alternatives you've considered
Multipass - This worked, but i want the instance.

When creating your instance you can upload the cloud-init script directly

https://raw.githubusercontent.com/signalfx/observability-workshop/master/workshop/cloud-init/k3s.yaml

i tried to do that, but i couldn't get it to work.   I even tried running it manually on the instance.
Wish it was that easy.
I ran everything manually.
i did find out that i needed an export
export KUBECONFIG-e=/etc/rancher/k3s/k3s.yaml


VScode style snippets can't be load properly.

My neovim can load friendly-snippets, but my custom snippet can't be load.
I use :lua print(vim.inspect(require('luasnip.loaders._caches'))) to check the cache, and can find my custom snippets in the second part oflazy_load_paths like this.
lazy_load_paths = {{
    ...,
    python = { "/home/hakuya/.local/share/nvim/site/pack/packer/start/friendly-snippets/./snippets/python/base.json"},
    ...
  }, {
    ...,
    python = {"/home/hakuya/.local/share/nvim/site/pack/packer/start/friendly-snippets/./snippets/python/base.json", "/home/hakuya/.config/nvim/snippets/./python.json"},
    ...
  }
}

but when writing a python program, only friendly-snippets works

I tried only load my custom snippet, but it still not work.
the output of :lua print(vim.inspect(require('luasnip.loaders._caches').vscode))in a python file is above.
{
  ft_paths = {
    lua = { "/home/hakuya/.config/nvim/snippets/lua.json" },
    python = { "/home/hakuya/.config/nvim/snippets/python.json" }
  },
  lazy_load_paths = { {
      add_opts = {},
      lua = { "/home/hakuya/.config/nvim/snippets/lua.json" },
      python = { "/home/hakuya/.config/nvim/snippets/python.json" }
    } },
  lazy_loaded_ft = {
    [""] = true,
    all = true,
    python = true
  },
  path_snippets = {},
  <metatable> = {
    __index = {
      clean = <function 1>
    }
  }
}

package.json
{
    "name": "nvim-snippets",
    "contributes": {
        "snippets": [
            {
                "language": [
                    "lua"
                ],
                "path": "lua.json"
            },
            {
                "language": [
                    "python"
                ],
                "path": "python.json"
            }
        ]
    }
}

python.json
{
    "PWNInit": {
        "prefix": "pwn_init",
        "body": [
            "from pwn import *",
            "import sys",
            "",
            "context.log_level = \"debug\"",
            "context.arch = \"amd64\"",
            "",
            "binary_name = \"${1:binary_name}\"",
            "libc_name   = \"${2:libc_name}\"",
            "remote_addr = \"\"",
            "remote_port = 0",
            "",
            "elf  = ELF(binary_name)",
            "libc = ELF(libc_name)",
            "",
            "local = 1",
            "",
            "if local:",
            "\tp = process(\"./\"+binary_name)",
            "\t# p = process(\"./\"+binary_name,env={\"LD_PRELOAD\":\"./\"+libc_name})",
            "\t# p = process([\"qemu-arm\", \"-L\", \"/usr/arm-linux-gnueabihf\", \"./\"+binary_name])",
            "\t# p = process(argv=[\"./qemu-arm\", \"-L\", \"/usr/arm-linux-gnueabihf\", \"-g\", \"1234\", \"./\"+binary_name])",
            "else:",
            "\tp = remote(remote_addr,remote_port)",
            "",
            "def z(a = ''):",
            "\tif local:",
            "\t\tgdb.attach(p, a)",
            "\telse:",
            "\t\tpass",
            "\t",
            "def leak_address():",
            "\tif(context.arch == 'i386'):",
            "\t\treturn u32(p.recv(4))",
            "\telse :",
            "\t\treturn u64(p.recv(6).ljust(8, b'\\x00'))",
            "",
            "ru  =lambda x    : p.recvuntil(x)",
            "sl  =lambda x    : p.sendline(x)",
            "sd  =lambda x    : p.send(x)",
            "sa  =lambda a, b : p.sendafter(a,b)",
            "sla =lambda a, b : p.sendlineafter(a,b)",
            "ia  =lambda      : p.interactive()",
        ],
        "description": "Init pwn exp",
    }
}

First of all, thanks for the detailed report :+1:
I think the issue here is just the trailing comma after "description" :facepalm:
(I've also been bit by that some times)
As you correctly asserted, the file is recognized without issue, its just that vim.json.decode fails (I'm assuming) (I'll look into adding logs to report such errors, luasnip just silently aborts, which, as you can probably attest, sucks)

Yes, it is caused by comma! And I find the two decode function (vim.fn.json_decode and vim.json.decode)will report different error:
E5108: Error executing lua Vim:E474: Trailing comma: ],"description":"Init pwn exp",}}
E5108: Error executing lua [string ":lua"]:1: Expected value but found T_ARR_END at character 1147

Right, I think the former is an older implementation, best use vim.json.decode when available.

hey @L3MON4D3 i dont think the logs are sufficient. it's taken me over a month to figure out that there is a trailing comma in my json. Since invalid json is invalid, it should be an error.

Hi, AFAICT we  have an error-message in the log for this, malformed json should be easier to discover with that.


hello, foundation new ProjectName

report !
.
/|     ,
, /|/  /| /|       Slow down there, friend!
/|/       |/ |       ------------------------
||            ||   Running this installer as an administrator can cause problems.
_|  ^^   ^^   |/   Try running this command again without "sudo" or administrator rights.
| -[O]--[O]- |
|    ,    |
|    ...     |
______/
I can only use common user login, to create a project?

current root user

Yes, you can't use sudo or admin rights. The commands the CLI runs must be run as a normal user, to avoid permissions issues with the files.


test: fix flaky tests + Add clean up for git repos

Description

Added clean up for git repos

Fixed below flaky tests

Scrolling_spec.js
PgAdmin_spec.js
BasicLint_spec.ts
Logs_spec.ts
GraphQL_spec.ts

Type of change

Flaky test fix

How Has This Been Tested?

Cypress test runs

Checklist:
QA activity:

[ ] Test plan has been approved by relevant developers
[ ] Test plan has been peer reviewed by QA
[ ] Cypress test cases have been added and approved by either SDET or manual QA
[ ] Organized project review call with relevant stakeholders after Round 1/2 of QA
[ ] Added Test Plan Approved label after reveiwing all Cypress test

/ok-to-test sha=bcb9de1

/ok-to-test sha=a6a4514

/ok-to-test sha=191301d

/ok-to-test sha=4adfec0

/ok-to-test sha=15b11df

/ok-to-test sha=2d17a38

/ok-to-test sha=26b282e

/ok-to-test sha=49c8c56

/ok-to-test sha=f64a29b

/ok-to-test sha=b1b2431

/ok-to-test sha=90a4d16

/ok-to-test sha=ff361d1

/ok-to-test sha=ffd2be2

/ok-to-test sha=96f7f91

/ok-to-test sha=9d450db

/ok-to-test sha=4233357

/ok-to-test sha=b6a0686

/ok-to-test sha=2d1814c

/ok-to-test sha=2d1814c

/ok-to-test sha=4a4cd0a


How to pass the sqlalchemyconnection string for oracle modin read_sql

Comes from https://stackoverflow.com/questions/68999218/how-to-pass-the-sqlalchemyconnection-string-for-oracle-modin-read-sql.

cc @amyskov

Currently modin read_sql doesn't support SQLAlchemy or another object connectables, so con parameter should be passed as string. Connection string looks correct, so, i think, we need more details about this case (can reproducer be provided or does it work on pandas.read_sql?).

I'm having the same issue as the poster. In my case, pandas.read_sql works and when I try using modin.pandas with pd.read_sql, I get the following message:
"UserWarning: To use parallel implementation of read_sql, pass the sqlalchemyconnection string instead of <class 'sqlalchemy.engine.base.Connection'>.
UserWarning: Parameters provided defaulting to pandas implementation."
Can I have an example of how to pass the sqlalchemyconnection string to pd.read_sql?

I'm reopening this issue so I can respond to @YarShev  comments on #3629.


Missing uncommitted changes

Testing #172042
Version: 1.75.0-insider
Commit: 0a6c277e4faa44a6b6eb82ddca8bfeccf7fecef6
Date: 2023-01-24T05:22:29.430Z
Electron: 19.1.9
Chromium: 102.0.5005.194
Node.js: 16.14.2
V8: <IP_ADDRESS>-electron.0
OS: Darwin arm64 21.6.0
Sandboxed: Yes

window with locally cloned private repo with uncommitted changes
Cloud changes turned on
Continue On: Open on vscode.dev

-> repo opens on insiders.vscode.dev and I need to sign in to GH
-> cloud changes are showing as turned on
-> no uncommitted changes show up
Local log:
2023-01-24 17:39:39.391 [info] Storing edit session...
2023-01-24 17:39:39.984 [info] Stored edit session with ref aeef5fac-5e56-4090-bf4f-7d4dcb429d95.
2023-01-24 17:39:39.990 [info] Opening https://insiders.vscode.dev/github/kieferrm/myrepo/blob/main/file.md?editSessionId%3Daeef5fac-5e56-4090-bf4f-7d4dcb429d95%26continueOn%3D1#L27

Cloud changes log in the web:
2023-01-24 17:39:47.615 [info] Resuming cloud changes, reason: found editSessionId aeef5fac-5e56-4090-bf4f-7d4dcb429d95 in environment service...
2023-01-24 17:39:47.826 [info] Resuming changes from cloud with ref aeef5fac-5e56-4090-bf4f-7d4dcb429d95...
2023-01-24 17:40:00.574 [info] Matching identity {"remote":"https://github.com/kieferrm/myrepo","ref":"master","sha":"612327c69855342d20100b73bcd0a61631f7c9c7"} against edit session folder identity {"remote":"git@github.com:kieferrm/myrepo.git","ref":"master","sha":"612327c69855342d20100b73bcd0a61631f7c9c7"}...
2023-01-24 17:40:00.678 [info] Skipping applying 3 changes from edit session with ref aeef5fac-5e56-4090-bf4f-7d4dcb429d95 as no matching workspace folder was found.

This is because the local git repo has a GitHub SSH remote and the remote repo reports GitHub HTTPS remotes. There's no generic way to translate a SSH remote to an HTTPS one, but we can add that logic in the providers in RemoteHub to mitigate this.
We can't introduce a RemoteHub setting to control which remote type gets used because by default Codespaces uses HTTPS remotes, so enabling such a setting would break Continue On to a codespace.

API proposal for this: https://github.com/microsoft/vscode/issues/180582


[v2] discovering if user is actually using code-server (for idle check - can do in v1)

Environment:  A docker swarm running code-server development environments for multiple users simultaneously (teaching course).
Previously
code-server v1, will log to files in  ".cache/code-server/logs" added
a line every time the users browser contacts the running code-server.
This happens at least every 5 minutes (on the dot), while the user has
a open browser pointing to "code-server".
This let me implement a check looking at when these log files last
updated to determine when the user last had a browser open to
code-server.  This check could then shutdown the docker container
for users that have not used there code-server for some time.
That is we have implemented idle timeout for the docker instances.
This is vital for the system to keep things running smoothly for
the multi-user docker swarm.
So far I have found no equivalent to implement idle timeout in
code-server v2.
Suggestion.
Provide a 'heartbeat' option/file, that is 'touched' (does not have to
write anything but it could, just have the file timestamp updated),
whenever "code-server" is contacted by the users browser.
This will make idle checking a lot easier too as it not need to search
for the latest log file, just the one heartbeat file.
However a log file file (as in v1) will be fine too.
Or prehaps you have some other suggestion.
PS:  Code-server v2 does generate logs whenever the user opens a file.  The log is for it attempting to find a 'git' repository for the file, and failing.
But it is not really a good idle/in-use indicator.

@antofthy So you're using this specific log file to audit user access if I'm correct?

We are currently still using v1, for a software development environment for 150 separate users (students).  We are looking for updates to the latest file matching...
$HOME/.cache/code-server/logs/[0-9]*/sharedprocess.log

The timestamp being used to determine when the user last had there browser connected to code-server. This file gets updated by code-server v1 every 5 minutes while the user has there browser connected.  With an entry like...
[2019-09-01 18:41:48.630] [sharedprocess] [info] Scanned user extensions: 0

It made for great way to determine when the user was no longer using their container.
I actually did not care what was logged, only that some file was being updated while code-server was in use, so that a 'idle time' could be determined.    I have not found anything similar in version 2
The alternative was to constantly scan a large volume of web logs to determine when browsers actually successfully contacted code-server, which would be hugely time consuming and process intensive.
It would be a very minor addition to code-server to have it touch (or log) to some user file, but one that would be immensely valuable when running multiple user environments.

We'll see what we can do.
CC @code-asher

A touch, or update of code-server v2 log file...
$HOME/.local/share/code-server/logs/*/remoteagent.log
would be ideal.  Just something every 5 to 10 minutes, whenever the web browser contacts server looking for directory/file updates.  Basically saying, user is still has it open in the browser.
File does update for some conditions, just not on any use activity.

@antofthy I use code-server@v1 behind a proxy and count the number of websocket connections. Maybe you can try this on v2.

@jeasonstudio How are you getting that information?  Is your proxy a docker service?
Anything would be better than trying to parse web logs!

The Scanned user extensions line every five minutes actually sounds like a bug haha. We could certainly log periodically to a file while there is at least one active connection to code-server.
One thing we wanted to do is have the ability to open a new file from the command line in the running browser instance. The way to do that would be to have a socket that code-server listens on to get file open requests.
So I'm just thinking out loud but another idea would be to use that same socket to emit events like "connect" and "disconnect" and something could then sit on that and listen. Or maybe we add a command like code-server --status which uses the socket to query the number of open connections or maybe a JSON blob which would contain the number of connections.

And the time since last connection. This would just be if the browser is actively connected or not though, but we could probably send actual idle info from the browser as well.

They are some nice ideas, though not as versatile or even as simple as logging, or even just touching, a file.  I don't even mind if the file is overwritten, or even deleted or re-created.
While code-server is running inside a docker container. The idle test that is being run is actually testing files, outside the docker container, and checking code-servers running in multiple containers (one per user development environment).  That way it can then shutdown the container if it has been idle for some time.  In fact the idle test of the files may not even be on the same docker node (machine) the docker container is running on!   EG: the container is on a 'worker' node, while the idle check on the code-server log file is being done on the 'master' node of a larger docker swarm.  The files being on a network file system (SAN) across all the workers, and mounted as appropriate into the docker containers.
This is why a file update (even if it is just a touch) is a good idea, as the status (idleness) of the code-server is then available to all systems that has access to the file.

Makes sense.

That would be perfect.  Look forward to seeing this on the next code-server release.


SAK-30080 Activate create button when using mouse.

If you tab through the fields on a new account page on the !gateway site then the create user button correctly appears, but if you click with the mouse it always thinks the email address is invalid because it’s validator never gets called. Here we pre-check if we need to validate the email.

+1, nice catch


npm install not working

Hello. I am on linux ubuntu server and i set up config.json
When i try to npm install like instructions says at first looks fine but then some errors show.
errors in console: https://pastebin.com/z6Rp9u2c
npm-debug.log : https://store11.gofile.io/download/6eb1c9d8-1b1e-4e5c-b1ff-430da4939390/npm-debug.log
Hope this logs help resolve issue.

Please join the support server I am no longer assisting with issues here on github. When you join please create a new ticket and I can assist you there https://discord.gg/pAKE2YK .


Change ChEBI name of cicloheximide to cycloheximide

Hi,
Currently the CHEBI:27641 entry is listed with the name cicloheximide and has cycloheximide listed as a synonym. We had talked internally about this being confusing based on usage in the scientific community and this morning one of our users (SGD) wrote in suggesting this was an error. When I checked some other sites I find that they have this chemical listed as cycloheximide:
https://www.ebi.ac.uk/chembl/compound/inspect/CHEMBL123292
http://chem.sis.nlm.nih.gov/chemidplus/rn/66-81-9
http://www.genome.jp/dbget-bin/www_bget?cpd:C06685
Would it be possible to change the name based on usage?
Cheers,
Rob

Hi Rob,
Where they exist, we tend to use the International Nonproprietary Name for drugs, as these tend to be the most widely used - hence our use of cicloheximide, rather than cycloheximide (the US adopted name) .
A problem with the latter is that is looks like a sensible 'structural' name for a chemical - possibly a synonym for piperidine 2,6-dione; possibly a synonym for azepine-2,7-dione based (see http://www.chemspider.com/Chemical-Structure.9599288.html for a "cyclohexamide" derivative), whereas there is no way of generating the structure of cicloheximide/cycloheximide from its name - a "look-up list" is required.
However, a Google search reveals that in this case, usage of the USAN is vastly greater than that of the INN (>600,000 hits compared with 5,000, respectively). Accordingly, I have changed the display name of ChEBI:27641 to cycloheximide, while retaining cicloheximide as a synonym.
Best wishes for Christmas and the New Year.
Gareth


R-CNN FG Accuracy=0.000000

Hello! I try a detection model and I get R-CNN FG Accuracy=0.000000. Is it ok if I just keep running it?
I search about this and it is said that I have to adjust the base_lr for gpu numbers. I do that but still get this issue.
Any suggestions?
Thank you!

maybe you can try reduce learning rate

@SingL3 hello, have you solved this problem? Please let me know, Thanks adavance

@maozezhong I do as what he suggests, reduce the learning rate to adjust the number of gpus you are using. Originally, for coco dataset, it sets to 0.01 for 8 gpus. I use 4 gpus so I set to 0.005.

R-CNN FG Accuracy=0.000000
This will still occur for hundreds of batches or thousands of batches, but after that it will increase.

OK. thank you for your reply. After 3000 batches, it increase to 0.000055, still so small...
I will continue training and see what it will increase to.
I have another question, what acturally does this 'FG' means ?

@maozezhong When it is not 0.0000000, I will increase constantly. I think FG means foreground. However, I found that this metric is kind of useless. I test my model at epoch 2 when it is ~0.5 and epoch 7 when it is ~0.82, but the performance of epoch 2 is better than 7.

OK, I got it, Thanks!

All the above answers are wrong. Accuracy = 0 is not due to lr.That's caused by batch_rois=-1, which is in the experiments/fpn/cfgs/resnet_v1_101_coco_trainval_fpn_dcn_end2end_ohem.yaml file.
Change batch_rois=-1 to batch_rios=512.

All the above answers are wrong. Accuracy = 0.000000 is not due to lr.That's caused by batch_rois=-1, which is in the experiments/fpn/cfgs/resnet_v1_101_coco_trainval_fpn_dcn_end2end_ohem.yaml file.
Change batch_rois=-1 to batch_rios=512.

This hyper-parameter is set for using ohem, but actually I didn't use ohem and I still get this issue at that time.

Is wrong.This hyper-parameter is not set for using ohem,It is used to select rios. After I modified this parameter, the problem of Accuracy = 0.0000 was solved. After testing, the AP value returned to normal.

Epoch[1] Batch [1200]	Speed: 1.70 samples/sec	Train-RPNAcc=0.974165,	RPNLogLoss=0.069415,	RPNL1Loss=0.067423,	Proposal FG Fraction=0.137024,	R-CNN FG Accuracy=0.370897,	RCNNAcc=0.889737,	RCNNLogLoss=0.334114.
you can result for output of training.

Epoch[1] Batch [1200] Speed: 1.70 samples/sec Train-RPNAcc=0.974165, RPNLogLoss=0.069415, RPNL1Loss=0.067423, Proposal FG Fraction=0.137024, R-CNN FG Accuracy=0.370897, RCNNAcc=0.889737, RCNNLogLoss=0.334114.
you can result for output of training,it is obvious that 'accuracy' already is normal value.

Epoch[1] Batch [1200] Speed: 1.70 samples/sec Train-RPNAcc=0.974165, RPNLogLoss=0.069415, RPNL1Loss=0.067423, Proposal FG Fraction=0.137024, R-CNN FG Accuracy=0.370897, RCNNAcc=0.889737, RCNNLogLoss=0.334114.you can see result for output of my  training,it is obvious that 'accuracy' already is normal value.


[#2] Specify operators type

Closes #2

This change is

@jandudulski, thanks for a prompt PR, this LGTM
ticket #2  can be closed


flesh out spinelia

Three corners of the town are vacant of people or things, despite their descriptions referring to such.

All corners have NPCs now, and they'll be fleshed out in a future update.

All the NPCs in Spinelia now have some content, including the shifty_woman who has a quest. All is in the latest version, 0.11.1.


widen Legend patches in thinned theme

The thinned theme changes the size of patches in Legends.  This means that the :solid, :dash and :dot lifestyles are hard to distinguish.
Widen patchsize from (8, 8)to(20, 8)`.
There may be some reason I'm unaware of for not doing this.

Running this script:
using CairoMakie, TuePlots, Random

data = cumsum(randn(Xoshiro(2), 4, 201), dims = 2)

for (p,) in [8, 16, 20]

    theme = merge(
        Makie.Theme(Legend = (patchsize = (p, 8),)),
        Theme(
            TuePlots.SETTINGS[:AISTATS];
            thinned = true
        )
    )

    with_theme(theme) do
        series(
            data,
            labels = ["label $i" for i in 1:4],
            linestyle=[:solid, :dash, :dot, :dashdot],
            axis=(title="patchsize = ($p, 8)",),
        )
        axislegend()

        display(current_figure())
    end
end

I got this output

In my opinion 16 is a little too narrow --- the :dash output doesn't quite have a full second dash to distinguish it from :dashdot.  It might be sufficient for most cases though.

Looks convincing! I'll go ahead and merge. Thanks again for the PR!


added a counting mechanism for SNPs after forging

This is an implementation of a simple non-missing SNP count in forge to solve #83.
Might be useful as an independent module as well - or as part of one of the inspection modules we already have in trident.
Playing around with some packages in the published_data repo yielded small, but still curious deviations between this count and the numbers reported in the respective .janno files.

Codecov Report

Merging #112 (073f1d8) into master (a15da88) will increase coverage by 0.26%.
The diff coverage is 91.30%.

@@            Coverage Diff             @@
##           master     #112      +/-   ##
==========================================
+ Coverage   64.56%   64.82%   +0.26%
==========================================
  Files          18       18
  Lines        1916     1936      +20
  Branches      126      128       +2
==========================================
+ Hits         1237     1255      +18
  Misses        553      553
- Partials      126      128       +2

Impacted Files
Coverage Δ

src/Poseidon/CLI/Forge.hs
78.70% <91.30%> (+1.67%)
:arrow_up:

Continue to review full report at Codecov.

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

OK, thanks for doing my homework :-) I'll go through this ASAP.

Hmm. So if I understand correctly, your strategy here is to make a second pass through the joint genotype data after forging just to determine the number of non-missing SNPs? Isn't that exacerbating the performance problem? I mean... in principle it should be possible do to the forging and the SNP counting in one pass right?

In principle your code is definitely right. A pipe-fold is exactly what's needed for this. But I think it can be done within the main forge stream. I'll take a closer look and make a suggestion

I think we need to use the Pipes.Prelude.tee function (https://hackage.haskell.org/package/pipes-4.3.16/docs/Pipes-Prelude.html) for this. It can convert the final consumer in the forge loop into a pipe by forwarding everything. Then we can wrap all this in a fold. Needs a bit of thinking, but I think it's possible...

Right - I considered this as well, but then decided against it. I thought the SNP counting might be interesting also outside of forge, so I didn't want to entangle it too much with it. But I have no strong opinions here and certainly prefer a faster solution.

OK, I will take a stab at that when I'm done with the forge optimisation. I think we can keep it modular as a pipe component, but still run it inside a single pass.

Alright. I've managed to put the SNP counting into the main forge pipe (or rather, the other way around as it looks in the code). It's beautifully elegant to work with P.tee and P.fold, but I haven't really tested it yet.

Could you perhaps merge master into this branch once we have merged #118? We can then directly check whether the SNP counting results in a performance issue, by comparing with our tests on real data.

OK, it's actually what I thought: This new version has a space leak (visible through top). We need to work on the fold.

Here is a possibly related space leak that I found some time ago with pipes and resource acquisition
https://github.com/Gabriel439/Haskell-Pipes-Library/issues/159
It's a bit different, but runManaged and runSafeT are tangentially related, I think.

I managed to reduce the memory leak by orders of magnitudes by using unboxed vectors for the counting. As a general rule, Unboxed Vectors should always be used if we're dealing with Ints or Doubles and the likes.
But I think the memory footprint still continuously increases now in the forge loop, even though it's now on the order to a megabyte or so every few seconds, so likely tolerable in the end. But it's still bugging me, of course.
I'll make one more attempt with IOVector, which might fix it.

If we can construct a minimal example with Pipes.Safe and readFile from Pipes.Safe.Prelude and then a fold which reproduces this leak, it would be awesome to put it on stack overflow or GitHub issue on the Pipes library...

OK, so I've now implemented this with IOVector, which is mutable and in this case the more reasonable choice. Unfortunately, there still is a mild memory leak... I observe 1Mb every two seconds in a large forge, starting with around 25Mb. This is not terrible, and I think in practice it won't affect runs much.
I think I would propose to wait for #118 and then merge master back into here to have the more optimal forging algorithm and then check again.
I will try to construct a more minimal example with a fold inside SafeT IO and will ask the pipes author how to avoid leaking there.

OK. I've merged master, and low and behold... the memory seems to max out at 33Mb right now. I can't observe an actual leak anymore. Could you perhaps replicate this, @nevrome? It's possible that the former leak was related to the former forge algorithm.

Ah, and I should say that I have not actually tested the SNP counting yet. That would also be awesome if you could somehow actually try it, @nevrome, perhaps you had a test case from your original implementation?

Alright - it seems to work well and a test with and without --intersect yields an expected result. But as already pointed out above, in all my tests the count after forge deviated from the numbers in the .janno file by a few thousand SNPs.
Where is this coming from? I think our counts here are reliable, right? It's stupidly simple, so I don't think there is an error in our code. But the values in the janno files should already be correct?

With
trident forge -f "*2012_PattersonGenetics*,*2021_Wang_EastAsia*,*2021_GnecchiRuscone_KazakhSteppe*,*2020_Bergstrom_HGDP*,*2019_Flegontov_PalaeoEskimo*,*2019_Olalde_Iberia*,*2019_Narasimhan_centralSouthAsia*" -d . -o huhu -n huhu

I don't observe meaningful memory leaking. How could I reproduce your observation?

OK - nevermind. I went to f0e17001f33c9fbf9e520686bccd13381bc9a67d and saw it. Amazing! Seems to be fixed in the current version.

Ugh, @nevrome, help... can you please resolve that conflict? I'm not comfortable enough (yet) to mess with the Golden test files. Thanks!

Done

Excellent. Thanks. I'll merge this then.


Manual install

Hi, I'm currently using windows, and my company will not allow the use of downloading from github, so I can't download the packages through a package manager...also, pathogen.vim doesn't work on my machine...is there a way to manually install nerdtree?

fixed it...problem with pathogen...had to change name of directory from .vim to .vimrc and had to change the vim runtime directory like so:
let vimDir = $HOME.'\\.vimfiles'
let &runtimepath.=','.vimDir


Viewer not working correctly

Please see the screenshot below for what is happening to our mails in the MailHog UI. Note that when I download the EML and open it in e.g. Outlook, the mail looks fine.

The same happens for non-HTML mails by the way.

thanks @Venorcis, it was only looking for Content-Transfer-Encoding values in lowercase, should be fixed now


fix: Correct FAB size and position (#708)

Fixes #708
Changes: FABs positioned correctly so as to have 16dp of space from the edges. Margin added to the layout for 'Code of Conduct', so that FAB doesn't block its veiw.
Screenshots for the change:

It looks a little bit out of place in Create Ticket Fragment

@iamareebjamal So what do you suggest?

Align the create ticket text. Or actually, just remove the Bottom Sheet Fragment and make it a proper fragment

I think the content is pretty short for it to be a proper fragment. Besides that, I think the Bottom Sheet Fragment looks and feels good :sweat_smile: .
Can I just align the text for now?

Alright, also show how the layout looks when creating ticket, i.e. with progress bar

It looks like this:

Try adding the progress bar above fab as this does not look good

Adding progress bar above, didn't seem to work. However, increasing the size seemed to be a better solution to make it look the same as it was before. Looks like this:

Adding progress bar above seemed to not work. Instead, I increased the size of ProgressBar.
Looks like this:


Step 7: added tags info

The service now allows tags. I edited the example in Step 7 and added the necessary description.

Closed due to technical problems


Consider shipping multiple go modules.

Proposal
Ship multiple go modules in this repository. For example, github.com/prometheus/prometheus/promql (or simply github.com/prometheus/promql) could be a module, as could github.com/prometheus/discovery. Many sub-directories in the project don't have direct dependencies on each other, but depend on github.com/prometheus/prometheus/common and github.com/prometheus/prometheus/util.
Use case. Why is this important?
My primary issue is that the whole prometheus module lists a requirement for k8s.io/client-go v0.20.0, but this is only needed by the discovery/ path. I needn't use the kubernetes discovery in my existing project, but I would like to use a recent version of the promql package. I do use the kubernetes API in other parts of my project, and I need it pinned to an earlier version of the code than prometheus requires. MVS always picks the version required by the prometheus module. I therefore can't build my project in a way that's compatible with my runtime while including the prometheus/prometheus module.
I can work around this by copying the part of the source tree that I need into its own directory, or shadowing the repo, deleting all the code I don't want and updating the go.mod file, but it's not an ideal long-term solution.

Thank you for your interest. While having multiple modules would slow down prometheus development and raise the barrier to entry, this is something that will be discussed in our developer summit, in the coming months.
For your specific dependency conflict, it should be fixed in the coming release of go (go 1.17): https://github.com/golang/go/issues/36460
Can you hold a few month more with your current workflow? Thanks.

(note: we also experimented with https://github.com/modularise but it seems not to work anymore)

Thanks - I think a discussion at the developer summit sounds like a great way to consider the issue. It's certainly not a slam-dunk do-it-now proposal. I think our workaround will be sufficient for my team for now.
I'm finding this design document a little hard to follow: https://go.googlesource.com/proposal/+/master/design/36460-lazy-module-loading.md
But I do believe that as long as we don't import the discovery package, we won't have the prometheus transitive dependency on k8s and it won't contribute to the k8s version selected by us.

Yes that is correct.

Last week's dev summit didn't get far enough through the agenda to cover this, but I expect it to be handled soon at one of the upcoming summits (happen monthly at the moment).
Relevant previous discussions:
https://groups.google.com/g/prometheus-developers/c/F1Vp0rLk3TQ/m/TyF2WxlkBgAJ
https://groups.google.com/g/prometheus-developers/c/DY88o6yOg28/m/Bzc7E0x9BgAJ

Hello from the bug-scrub!
The discussion around a modularize tool linked above didn't get traction.
Historically, TSDB was extracted as a separate repo, and then moved back in to Prometheus as maintenance was a pain.
It would be quite a high bar to motivate additional friction for Prometheus maintainers, but if the benefits are there we could do it.
Next step for this issue would be a concrete proposal of which modules, who benefits from creating them, and how much work it is to get there.


Debootstrap error: ar: error while loading shared libraries: libbfd-2.36.1.so

Please describe your issue:
Every time I try and install any distro I get the same error:
I: Retrieving ubuntu-minimal 1.361
I: Validating ubuntu-minimal 1.361
I: Retrieving ucf 3.0036
I: Validating ucf 3.0036
I: Retrieving udev 229-4ubuntu4
I: Validating udev 229-4ubuntu4
I: Retrieving ureadahead 0.100.0-19
I: Validating ureadahead 0.100.0-19
I: Retrieving util-linux 2.27.1-6ubuntu3
I: Validating util-linux 2.27.1-6ubuntu3
I: Retrieving vim-common 2:7.4.1689-3ubuntu1
I: Validating vim-common 2:7.4.1689-3ubuntu1
I: Retrieving vim-tiny 2:7.4.1689-3ubuntu1
I: Validating vim-tiny 2:7.4.1689-3ubuntu1
I: Retrieving whiptail 0.52.18-1ubuntu2
I: Validating whiptail 0.52.18-1ubuntu2
I: Retrieving xkb-data 2.16-1ubuntu1
I: Validating xkb-data 2.16-1ubuntu1
I: Retrieving zlib1g 1:1.2.8.dfsg-2ubuntu4
I: Validating zlib1g 1:1.2.8.dfsg-2ubuntu4
I: Chosen extractor for .deb packages: ar
I: Extracting adduser...
debootstrap error log:

ar: error while loading shared libraries: libbfd-2.36.1.so: cannot open shared object file: No such file or directory
Failed to run debootstrap.

Using a Pixelbook on 91.0.4472.147.

It's the original 2017 Pixelbook.

Does it say anything about libbfd-2.36.1.so before this log?

Nope, only in the error itself. Full log is here.

Do you have chromebrew installed? If you do, the problem is likely chromebrew's version of libbfd. I uninstalled chromebrew and got it to work, but if you don't want to install chromebrew you can unset LD_LIBRARY_PATH and see if that works.

@saltedcoffii Crouton works via chroots, so I wouldn't think that is the case, feel free to correct me if I am wrong though.

Thanks. I did have chromebrew installed, uninstalled and now it works.

Thanks. I did have chromebrew installed, uninstalled and now it works.
I stand corrected... I didn't think that Chromebrew effected it.

@saltedcoffii Crouton works via chroots, so I wouldn't think that is the case, feel free to correct me if I am wrong though.

In the early stages of the chroot setup, debootstrap is used to create a basic rootfs for chroot (running outside of chroot), then take over by apt in chroot to complete the setup


Testing on Linux

Tests are not executed on linux caused by swifts lack of dynamic test evaluation.
Generating the tests could be a solution. (https://oleb.net/blog/2017/03/keeping-xctest-in-sync/)

When this is done, Linux build success should be required.


BLD: require latest s2geometry 0.11 / s2geography 0.1.1 + use cmake config to find libraries

If we require the latest release of both s2geometry and s2geography, that simplifies our CMake set-up a bit.
(this relies on having a conda-forge release)

s2geography last release is available on conda-forge (or should be in a few hours).


Migrate manager identifier/displayName (solve static identifier -> pure virtual)

What
Add identifier and displayName methods to the C++ ManagerInterface and inherit their default implementations in Python.
Why
This is a necessary step toward a C++ manager plugin and a C++->Python bridge.
Questions
identifier is currently a static method in the Python source, so that ManagerPlugin can retrieve the identifier without first creating a ManagerInterface instance. We may need to rethink this?

We'll need to revert https://github.com/TheFoundryVisionmongers/OpenAssetIO/pull/125 for ManagerInterface. Lol.