stage contains artifacts and is not visible on AMD gpu solved

Describe the bug
Stage (place where the 3d object should be rendered) is not being shown properly, instead, artifacts are being rendered.
Top controls are also not being displayed, white color is shown. But, left panel and bottom 'Text commands' are shown properly.
To Reproduce
Steps to reproduce the behavior:

Open 'Fusion 360'
Finish!

Expected behavior
Was expecting to see 3d grid with the top controls.
Screenshots

Desktop (please complete the following information):

Fusion 360 2.0.11415
AMD RX 5700 XT, driver: amdgpu-pro - 20.45-1188099
Ubuntu 20.04.3 LTS (kernel 5.4.0-54-generic)
Gnome 3.36.8
OpenGL-Mode
used 'stable-branch/fusion360-setup-wizard.sh'
wine-6.21 (Staging) and WINEARCH=win64

Relevant info:
$ glxinfo -B

name of display: :1
display: :1  screen: 0
direct rendering: Yes
Memory info (GL_ATI_meminfo):
    VBO free memory - total: 3972 MB, largest block: 6049 MB
    VBO free aux. memory - total: 7162 MB, largest block: 6125 MB
    Texture free memory - total: 3972 MB, largest block: 6049 MB
    Texture free aux. memory - total: 7162 MB, largest block: 6125 MB
    Renderbuffer free memory - total: 3972 MB, largest block: 6049 MB
    Renderbuffer free aux. memory - total: 7162 MB, largest block: 6125 MB
OpenGL vendor string: Advanced Micro Devices, Inc.
OpenGL renderer string: AMD Radeon RX 5700 XT
OpenGL core profile version string: 4.6.14756 Core Profile Context
OpenGL core profile shading language version string: 4.60
OpenGL core profile context flags: (none)
OpenGL core profile profile mask: core profile

OpenGL version string: 4.6.14756 Compatibility Profile Context
OpenGL shading language version string: 4.60
OpenGL context flags: (none)
OpenGL profile mask: compatibility profile

OpenGL ES profile version string: 4.6.14756 Compatibility Profile Context
OpenGL ES profile shading language version string: 4.60

$ sudo lshw -C display

  *-display
       description: VGA compatible controller
       product: Navi 10 [Radeon RX 5600 OEM/5600 XT / 5700/5700 XT]
       vendor: Advanced Micro Devices, Inc. [AMD/ATI]
       physical id: 0
       bus info: pci@0000:2f:00.0
       version: c1
       width: 64 bits
       clock: 33MHz
       capabilities: pm pciexpress msi vga_controller bus_master cap_list rom
       configuration: driver=amdgpu latency=0
       resources: irq:160 memory:d0000000-dfffffff memory:e0000000-e01fffff ioport:f000(size=256) memory:fcd00000-fcd7ffff memory:c0000-dffff

$ dpkg -l amdgpu-pro
||/ Name           Version       Architecture Description
+++-==============-=============-============-==============================================
ii  amdgpu-pro     20.45-1188099 amd64        Meta package to install amdgpu Pro components.

Kindly thank you for this installer and for the work that went into this.

Hey @Andreii 🙂,
I see a couple of similarities to this post here:

https://github.com/cryinkfly/Autodesk-Fusion-360-for-Linux/issues/73

Please check these issues here:

https://github.com/cryinkfly/Autodesk-Fusion-360-for-Linux/issues/17
https://github.com/cryinkfly/Autodesk-Fusion-360-for-Linux/issues/116
https://github.com/cryinkfly/Autodesk-Fusion-360-for-Linux/issues/124

Hello @cryinkfly, thank you for the prompt feedback!
I uninstalled amdgpu-pro driver, restarted and... it works. Seems the kernel driver works better.
The artifacts are gone, stage is rendered.
Works with:

OpenGL
DirectX 9
Not working:
DirectX 11

Any update on this? I'm suffering the same issue with gtx 1080 on pop os 21.10 wine 7.0. Its borderline usable by quickly zooming in or out to update the selection set, but still not ideal and hard to deal with small selections/highlights.


Upgrade to Babel 6 and JSPM 0.17

Follow these steps and pray

Not particularly urgent, and this may not be stable enough yet to warrant the churn.


[gnav] The gnav disappear in some circonstances

Open https://main--blog--adobe.hlx3.page/en/publish/2021/04/01/36-days-of-type-2021#gs.fjtoin in Incognito window: gnav is missing.

This seems to be some css priority that is applied differently depending on the loading sequence.

This is the consequence of the banner in the page being loaded with .html.plain.html. This is now fixed with #94. (browser cache reload)


WindiCSS Docs search not working properly.

I am using WindiCSS a lot,, and I always go to WindiCSS docs and use search to find utilities I like to use.. just today it seems like the search not working properly
I am looking for hover but does not work properly.

Doesn't work at all now. It seems it's a problem with algolia.
Operations quota exceeded. Change plan to get more Operations.

This question how to fix?

This question how to fix?

I'm having the same issue. From what I can tell in the browser console and a quick Google search, it seems like WindiCSS has exceeded their search quota with the Algolia service used for browsing the docs. Since it seems like this issue appeared for me almost a month later, I'm assuming this happens sometimes at the end of their monthly quota period. I'm sure it will be fixed soon!
In the meantime, you can still use the navigation menus at the top of the screen to find what you're looking for. I stumbled upon some cool features by circumventing the quick search utility, such as the WindiCSS Intellisense extension for VS Code, which I didn't know existed until now.

it seems its now working on my end so I will be closing this issue.


Update README.md - fixed missing newline and indents

Honestly, this is just a test - I just haven't committed code to someone else's GitHub repo in a while, and I'm wondering if I need to start a PR or a fork in order to do that

Nice catch! Thanks for contributing. Your contribution will be featured on episode 87 of the Nerd Dice YouTube series.

Nice catch! Thanks for contributing. Your contribution will be featured on episode 87 of the Nerd Dice YouTube series.

It was a pretty big honor being featured in that episode.
I'm not gonna lie Mike, I tried to make a more impressive contribution by adding a Dockerfile to spin up the site in a container or two or few, but I ran into too many issues.  Sometimes I can do that sort of thing quickly - other times, not so much.  Familiarity with the Ruby ecosystem might have helped.


app cannotstartanymore with small interval

since api 24 cant set the periodic less than 15m that's for sure, but when i set a amall interval foe api 23, the vever started, is  amdroid-jkb not allow to set a small interval time?

No, the idea is to provide a job library which works the same on all platforms.


Add kickout hook

Environment

VerneMQ Version: 1.4.0
OS: centos7
Erlang/OTP version (if building from source):

Expected behavior
Actual behaviour
we use vernemq be a IM server
when set allow_multiple_sessions = off
client A and client B use the same client_id
client A connected,
client B connected and kickout  client A ,  client A disconnected without any info ,  reconnect start, and will kickout client B ...
maybe we can add a hook , when client A will be kickout,  publish a msg to client A (qos 0) ,

Hi,
It would be interesting to know what use case this would solve? Maybe there's another way to achieve what you want to do?
In MQTTv5 this problem is solved as there the broker can send the client a specific MQTT disconnect packet with the reason code 'disconnected due to session take over'. We expect to merge MQTT v5 support to the master branch in one of the following days, see #814 .

Good!


AxisLine: Text should respect Label alignment

issue originated from an email from "Kyle"

namespace Sandbox.WinForms;

public partial class Form1 : Form
{
    public Form1()
    {
        InitializeComponent();

        var f = formsPlot1.Plot.Add.VerticalLine(42);
        f.Text = "Hi Kyle";
        f.Label.Rotation = -45;
        f.Label.Alignment = ScottPlot.Alignment.LowerLeft;
    }
}

The call to render seems right...
https://github.com/ScottPlot/ScottPlot/blob/b01ad7e732f78ed8d04bda6a5aff24f7a06ddf4a/src/ScottPlot5/ScottPlot5/Plottables/VerticalLine.cs#L74
so maybe the bug is inside the label class itself?

The bug is here... the user-defined alignment is overwritten in the render method
https://github.com/ScottPlot/ScottPlot/blob/b01ad7e732f78ed8d04bda6a5aff24f7a06ddf4a/src/ScottPlot5/ScottPlot5/Plottables/VerticalLine.cs#L66-L68


After opening/closing a dx-popup widget, Angular2 routing is broken

Using devextreme-angular for angular2, I have a main page (a list with a dx-button that opens a dx-popup widget:
Project list:

Project-popup-new:

After closing the dx-popup, routing stops working, when trying to navigate to other row items. If I don't open the dx-popup, routing is Ok.
Any clues on this issue?
Thank you.
To help us process your issue more efficiently, please provide the following information:

Specify the version of the devextreme-angular package. If you replaced the default version of the devextreme package, please specify it as well.
If you consider the issue to be a bug, provide detailed steps to reproduce it. If possible, create a demo illustrating the problem using https://plnkr.co or a similar service. Feel free to use the template for version 16.2 or template for version 16.1.

This issue is known to us. Please provide me with a sample project to reproduce it. At the moment, I don't see any reason why our popup may break routing in Angular applications.

What files (or configurations) do you need to replicate this behavior ?
Thank you.

Hello,
This was caused by other problem not related to Devextreme but to Angular2.

I am facing the similar issue. Can you specify how was the issue solved?


Allow custom tags

For parsing dynamic begin/end blocks in Antlr4: https://stackoverflow.com/a/27321119/3447117

Single-tag custom tags (i.e. ones without a block) are now implemented. The exact user-facing API for implementing a custom tag complete with type checking on tag arguments is not well thought out yet though.


kubeconfig content string in kubernetes provider is not working with operator

What happened?
I declared a k8s provider in the Pulumi YAML as below.
   k8sProvider:
        type: pulumi:providers:kubernetes
        properties:
          cluster: kubernetes
          context: aws
          kubeconfig: |
            apiVersion: v1
            clusters:
            - cluster:
                server: <server-url>
                certificate-authority-data: <cert-data>
              name: kubernetes
            contexts:
            - context:
                cluster: kubernetes
                user: aws
              name: aws
            current-context: aws
            kind: Config
            preferences: {}
            users:
            - name: aws
              user:
                exec:
                  apiVersion: client.authentication.k8s.io/v1beta1
                  command: aws-iam-authenticator
                  args:
                    - "token"
                    - "-i"
                    - "pl-native"

It works fine with Pulumi CLI.
But the same did not work with pulumi-kubernetes-operator.
I included the same provider in a program/stack pair.
Here is the error i am getting.
pulumi:providers:kubernetes k8sProvider  error: rpc error: code = Unknown desc = failed to parse kubeconfig: json: cannot unmarshal string into Go struct field ExecConfig.users.user.exec.args of type []string
Example
Extract from the the program/stack
  apiVersion: pulumi.com/v1
  kind: Program
  metadata:
    name: pl-program-eks
  program:
    variables:
      providers:
        - ${k8sProvider}
    resources:
      k8sProvider:
      type: pulumi:providers:kubernetes
      properties:
        cluster: kubernetes
        context: aws
        kubeconfig: |
          apiVersion: v1
          clusters:
          - cluster:
              server: <server-url>
              certificate-authority-data: <cert-data>
            name: kubernetes
          contexts:
          - context:
              cluster: kubernetes
              user: aws
            name: aws
          current-context: aws
          kind: Config
          preferences: {}
          users:
          - name: aws
            user:
              exec:
                apiVersion: client.authentication.k8s.io/v1beta1
                command: aws-iam-authenticator
                args:
                  - "token"
                  - "-i"
                  - "pl-native"

Output of pulumi about
CLI
Version      3.107.0
Go Version   go1.22.0
Go Compiler  gc
Plugins
NAME        VERSION
kubernetes  4.9.0
yaml        unknown
Host
OS       amazon
Version  2
Arch     x86_64
This project is written in yaml
No dependencies found
Pulumi locates its logs in /tmp by default
warning: Failed to get information about the current stack: No current stack
Additional context
No response
Contributing
Vote on this issue by adding a 👍 reaction.
To contribute a fix for this issue, leave a comment (and link to your pull request, if you've opened one already).

thanks for the issue report @geowalrus4gh; it migyht be helpful to compare the version of the pulumi-yaml plugin that's being used locally vs in the operator.

Similar: https://github.com/pulumi/pulumi-kubernetes-operator/issues/525


[Glitch] In Chrome rendering make black lines

Chrome Version 120.0.6099.227 (Official Build) (64-bit) make glitching black frames when scrolling trough long lists.
I heard it is not in firefox but did not checked (because I don't use firefox) yet.
Can someone confirm this bug?

This happens to me in Chrome pretty frequently as well


Storybook links in zeroheight not working

Design and code pages:
https://eds.equinor.com/0b0c666ab/p/392109-table/b/398446
Code page in:
https://eds.equinor.com/0b0c666ab/p/50d3be-tabs/b/94939a

https://eds.equinor.com/0b0c666ab/p/392109-table/b/398446 is broken

I fixed the links in zeroheight, but not published it yet. Can you check in zeroheight that it looks up in the latest version there?


Update Request - GSD-2022-31289

Automated Edit Request
For: "GSD-2022-31289"
{
  "GSD": {
    "alias": "CVE-2022-31289",
    "summary": "GSD UPDATE: There doesn't appear to be a vulnerability, the Sonatype Nexus Repository Manager OSS is a single page web app, so when passed a \"200\" response the page displays that login was successful when it fact it was not. A CVE was erroneously assigned to the original security researchers report.",
    "description": "GSD UPDATE: There doesn't appear to be a vulnerability, the Sonatype Nexus Repository Manager OSS is a single page web app, so when passed a \"200\" response the page displays that login was successful when it fact it was not. A CVE was erroneously assigned to the original security researchers report. \n\n https://ossindex.sonatype.org/ Sonatype Nexus Repository Manager OSS 3.37.3-02 is affected by: Incorrect Access Control. The impact is: Authentication Bypass (remote). The component is: Admin Panel. The attack vector is: With the help of response manipulation Attacker can bypass the login panel and view the dashboard menus, No user interaction is required. ¶¶ 1. Go to https://nexus.e-goi.com 2. Click on the Sign In button. 3. Enter the password as admin:admin. 4. Intercept the request in Burp Suite. 5. Capture the Response of the Request. 6. Change the Status Code from 403 Forbidden to 200 OK. 7. You will see the dashboard which provides the admin access.",
    "id": "GSD-2022-31289",
    "references": [
      {
        "type": "WEB",
        "url": "https://blog.sonatype.com/nexus-repo-issue-neither-bug-nor-vulnerability"
      },
      {
        "type": "TWITTER",
        "url": "https://twitter.com/brian_fox/status/1537468660377440270"
      }
    ]
  },
  "namespaces": {
    "cve.org": {
      "CVE_data_meta": {
        "ASSIGNER"<EMAIL_ADDRESS>        "ID": "CVE-2022-31289",
        "STATE": "PUBLIC"
      },
      "affects": {
        "vendor": {
          "vendor_data": [
            {
              "product": {
                "product_data": [
                  {
                    "product_name": "n/a",
                    "version": {
                      "version_data": [
                        {
                          "version_value": "n/a"
                        }
                      ]
                    }
                  }
                ]
              },
              "vendor_name": "n/a"
            }
          ]
        }
      },
      "data_format": "MITRE",
      "data_type": "CVE",
      "data_version": "4.0",
      "description": {
        "description_data": [
          {
            "lang": "eng",
            "value": "https://ossindex.sonatype.org/ Sonatype Nexus Repository Manager OSS 3.37.3-02 is affected by: Incorrect Access Control. The impact is: Authentication Bypass (remote). The component is: Admin Panel. The attack vector is: With the help of response manipulation Attacker can bypass the login panel and view the dashboard menus, No user interaction is required. ¶¶ 1. Go to https://nexus.e-goi.com 2. Click on the Sign In button. 3. Enter the password as admin:admin. 4. Intercept the request in Burp Suite. 5. Capture the Response of the Request. 6. Change the Status Code from 403 Forbidden to 200 OK. 7. You will see the dashboard which provides the admin access."
          }
        ]
      },
      "problemtype": {
        "problemtype_data": [
          {
            "description": [
              {
                "lang": "eng",
                "value": "n/a"
              }
            ]
          }
        ]
      },
      "references": {
        "reference_data": [
          {
            "name": "https://www.acunetix.com/vulnerabilities/web/tag/authentication-bypass/",
            "refsource": "MISC",
            "url": "https://www.acunetix.com/vulnerabilities/web/tag/authentication-bypass/"
          },
          {
            "name": "https://medium.com/@pmmali/my-first-cve-2022-31289-4081c57e90fb",
            "refsource": "MISC",
            "url": "https://medium.com/@pmmali/my-first-cve-2022-31289-4081c57e90fb"
          }
        ]
      }
    },
    "nvd.nist.gov": {
      "configurations": {
        "CVE_data_version": "4.0",
        "nodes": []
      },
      "cve": {
        "CVE_data_meta": {
          "ASSIGNER"<EMAIL_ADDRESS>          "ID": "CVE-2022-31289"
        },
        "data_format": "MITRE",
        "data_type": "CVE",
        "data_version": "4.0",
        "description": {
          "description_data": [
            {
              "lang": "en",
              "value": "https://ossindex.sonatype.org/ Sonatype Nexus Repository Manager OSS 3.37.3-02 is affected by: Incorrect Access Control. The impact is: Authentication Bypass (remote). The component is: Admin Panel. The attack vector is: With the help of response manipulation Attacker can bypass the login panel and view the dashboard menus, No user interaction is required. ¶¶ 1. Go to https://nexus.e-goi.com 2. Click on the Sign In button. 3. Enter the password as admin:admin. 4. Intercept the request in Burp Suite. 5. Capture the Response of the Request. 6. Change the Status Code from 403 Forbidden to 200 OK. 7. You will see the dashboard which provides the admin access."
            }
          ]
        },
        "problemtype": {
          "problemtype_data": [
            {
              "description": []
            }
          ]
        },
        "references": {
          "reference_data": [
            {
              "name": "https://medium.com/@pmmali/my-first-cve-2022-31289-4081c57e90fb",
              "refsource": "MISC",
              "tags": [],
              "url": "https://medium.com/@pmmali/my-first-cve-2022-31289-4081c57e90fb"
            },
            {
              "name": "https://www.acunetix.com/vulnerabilities/web/tag/authentication-bypass/",
              "refsource": "MISC",
              "tags": [],
              "url": "https://www.acunetix.com/vulnerabilities/web/tag/authentication-bypass/"
            }
          ]
        }
      },
      "impact": {},
      "lastModifiedDate": "2022-06-15T12:53Z",
      "publishedDate": "2022-06-14T17:15Z"
    }
  }
}

Added manually


Change colour on inline code

Hi,
I would like to change the color of the inline code. I know that the template is using highlight.js for the code chunks. But what changes should a make to change the color of the inline code?
Thanks!

Hi, I’m afraid I don’t know how to help. You should check with highlight.js to see if they support this.


compress.js handling 'accept-encoding' header according to W3C standards?

Hi Connect Creators,
Right now, compress.js doesn't seem to adhere to W3C standards when it comes to reading the 'accept-encoding' header (unless I'm completely mistaken). For example, if a request has an accept-encoding heading of "gzip;q=0", the browser would be telling the server that it does not want any gzipped files, while this server would return a gzip file.
Is compress.js being planned on being made W3C compliant at some point, or will we need to modify it/write our own zlib-using-connect-middleware in order to make this happen?
Best,
Sami

I guess I don't know too much about how browsers that don't deal with gzip. I'm just trying to cover all my fronts - essentially if the app I'm working on becomes popular and a browser specifically requests non-gzip files because it can't gunzip them, then I wouldn't want that user to be unable to view the page.
I realize that it isn't that large of an issue anymore, but apparently 10% or so of the internet's users still use real shitty browsers... do you think it's something that's necessary?

not that it's not a concern, but I've never seen a client send q=0, they just dont set it at all

ah ok. i'll trust that you know more about this than i do. if my site picks up traffic and i end up noticing issues of these sorts, i'd be happy to write a patch for connect that addresses the problem.

a spec is a spec, but in practice i dont think you'll run into that much, but certainly let me know if you do come across any


qtstyleplugin-kvantum-qt4: 0.16.0 -> 0.18.0

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/tsujan/Kvantum/releases.
meta.description for qtstyleplugin-kvantum-qt4 is: "SVG-based Qt4 theme engine"
meta.homepage for qtstyleplugin-kvantum-qt4 is: "https://github.com/tsujan/Kvantum"
meta.changelog for qtstyleplugin-kvantum-qt4 is: ""
Updates performed

Version update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS

The tests defined in passthru.tests, if any, passed

0 of 0 passed binary check by having a zero exit code.

0 of 0 passed binary check by having the new version present in output.

directory tree listing: https://gist.github.com/6504f6c270d818671871856ae60a3479

du listing: https://gist.github.com/751a4396dc0bddceb5edea0d3c672990

Rebuild report (if merged into master) (click to expand)

3 total rebuild path(s)

1 package rebuild(s)

1 x86_64-linux rebuild(s)
1 i686-linux rebuild(s)
0 x86_64-darwin rebuild(s)
1 aarch64-linux rebuild(s)

First fifty rebuilds by attrpath
qtstyleplugin-kvantum-qt4

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/15v35970qymdv6k5q01vyfv8hyiw4536-qtstyleplugin-kvantum-qt4-0.18.0 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A qtstyleplugin-kvantum-qt4 https://github.com/r-ryantm/nixpkgs/archive/b3377862458444e582994c7ce26c94b11d2fbaf7.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/15v35970qymdv6k5q01vyfv8hyiw4536-qtstyleplugin-kvantum-qt4-0.18.0
ls -la /nix/store/15v35970qymdv6k5q01vyfv8hyiw4536-qtstyleplugin-kvantum-qt4-0.18.0/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

qtstyleplugin-kvantum-qt4

Maintainer pings
cc @bugworm for testing.

a new version has been released


Tonic example

Added example notebook that shows how to download data, ready to feed to network. Tonic does support batching for tensor representations, if you want to do that please let me know and I'll add it.

Thanks a lot man, this looks great.
Batching would be good to include, though I think I figured it out.
All you need is tonic.utils.pad_tensors to get all tensors of equal duration, right?

Indeed! As mentioned in an example here https://tonic.readthedocs.io/en/latest/utils.html#pad-events-for-batching
Le 7 septembre 2021 22:20:40 GMT+01:00, Jason Eshraghian @.***> a écrit :

Thanks a lot man, this looks great.
Batching would be good to include, though I think I figured it out.
All you need is tonic.utils.pad_tensors to get all tensors of equal duration, right?
--
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub:
https://github.com/jeshraghian/snntorch/pull/65#issuecomment-914637334
--
Envoyé de mon appareil Android avec Courriel K-9 Mail. Veuillez excuser ma brièveté.

Perfect! I'll expand this tutorial and shoot it through to you in the next few days.


.get_endpoints.kind == "Endpoint" vs .get_endpoint(...).kind == "Endpoints"

When getting a single entity, we return .kind as-is:
pry(main)> kclient.get_endpoint('docker-registry', 'default', as: :raw)[0..39]
=> "{\"kind\":\"Endpoints\",\"apiVersion\":\"v1\",\"m"
pry(main)> kclient.get_endpoint('docker-registry', 'default').kind
=> "Endpoints"
pry(main)> kclient.get_security_context_constraint('nonroot').kind
=> "SecurityContextConstraints"

For collections, k8s does not return individual .kind in each item, only a global list kind.
We do some magic to convert that to a singular .kind, without the List.
Somewhat confusingly, we do this on the EntityList pseudo-array, no .kind on individual item:
pry(main)> kclient.get_endpoints(as: :raw)[0..39]
=> "{\"kind\":\"EndpointsList\",\"apiVersion\":\"v1"
pry(main)> kclient.get_endpoints.kind
=> "Endpoint"
pry(main)> kclient.get_endpoints.first.kind
=> nil
pry(main)> kclient.get_security_context_constraints.kind
=> "SecurityContextConstraint"

The immediate bug here is "Endpoints" vs "Endpoint" and  "SecurityContextConstraints" vs "SecurityContextConstraint" mismatch, because the single is already plural in k8s (see https://github.com/kubernetes/kubernetes/issues/8115#issuecomment-101319887, https://github.com/kubernetes/kubernetes/issues/18622, #81, #261 for background).
I'm not 100% sure which way to fix it, but I think the reason we "fixed" the double plural is merely we needed distinct get_foo / get_foos method names — which is a kubeclient concern that should not leak into .kind, it should always be a valid k8s API kind.

The wider question I want to discuss (not necessarily here) is what's the purpose of this magic?

The best use I envision is making it easy to feed the kind back to the API, which is not yet applicable much in kubeclient but is discussed on #208 etc.
Towards that, I'd like us to provide the non-List .kind (and apiVersion?) inside every entity of the array, such that you don't have to care whether you obtained one from via List or Get operation.  (And then potentially restore get_foos.kind to be "FooList".)

Besides kind, neither the collection nor the individual items expose .api_version.  It's simply lost.


Allow Connection Limit when running Direct Mode

When running in Gateway Mode there is a connection limit setting to limit the number of open connections to CosmosDB.  This is useful when running an Azure Function that connects to CosmosDB as it keeps the function from exceeding the 300 connection limit enforced on functions running in Azure.
However, this connection limit setting is ignored in Direct Mode.  As a result I have found that if I run Function with Direct Mode I see Connect Limit errors when large spikes occur on my Function (which is an HTTP Trigger). This has forced me to run Gateway mode rather than Direct mode.  I would much rather run Direct mode and eliminate the extra latency of Gateway mode.
Please consider enforcing the Connection Limit in  Direct Mode.  BTW, I am running the DocumentClient as a singleton.

@edwarder86 You mention that you are using the DocumentClient as a singleton, is that implemented as a static instance?

Yes, it is a static instance.

Thanks! Just making sure. Aren't you connecting to any other service in the Function? Any other HTTP request that could be raising the connection limit?
As far as I know, using a static / singleton instance should not raise the amount of connections.

Additional info regarding the Connection Limit in Functions: https://github.com/Azure/azure-functions-host/wiki/Managing-Connections

CosmosDB is the only thing it connects to.  The problem is that I'm calling the function millions of times a day and sometimes in very large spikes.  Using Gateway Mode and setting a limit of 200 works fine for me.  If Direct Mode would support the same Conneciton Limit as Gateway Mode does I am confident that it work work just fine as well.

Makes sense, will leave the comments to the SDK experts, I'm not familiar on how Direct Mode works with connections as a Singleton, just wanted to rule out any common issue on Functions environment,

We are working on adding this feature. Please stay tuned.

Thank you for the update.

Any update on this? We are having to resort to the same strategy (but would rather use Direct Mode for performance when possible).


💡[FEATURE]: Vehicle Insurance Claim Fraud Detection

Vehicle insurance fraud involves conspiring to make false or exaggerated claims involving property damage or personal injuries following an accident so, It will Detect fraud claims and will help Insurance Firms to verify them properly again.

@Akshat111111 sir please merge it


Error: no valid ID found for GFF record

Hello, I don't know what went wrong, could you tell me? thank you

see https://github.com/gpertea/gffread/issues/84
you are likely using a gtf2.2 reference, of which the omission of transcript_id is allowed causing legacy gtf readers to complain
try using an older assembly / annotation pair
alternatively try using a gff file from that assembly and converting it to gff format

If it is that GTF2.2 issue indeed, as I wrote in gpertea/gffread#84, I do not want to encourage such terrible ideas (empty string identifiers in a file format), so I recommended one of the following solutions instead:

use the GFF3 version of that same annotation, if available
..or if that's not an option:
use a grep filter to weed out the badly formatted lines from that GTF2.2 file, e.g. something like this:

grep -P '\btranscript_id\s+"[^"]+"'  ann_gtf22.gtf >  ann_fixed.gtf


Popup not triggered by custom component

I recently bumped into this problem after I decide to turn some code into their own sub-component.
Steps
Create a basic React component
class Foo extends Component {
  render() {
    return (
      sdafsd
    );
  }
}

The popup doesn't appear
<Popup
  trigger={<Foo />}
  content='Comments are coming soon!'
  inverted
  />

but it shows up fine with this
<Popup
  trigger={sdafsd}
  content='Comments are coming soon!'
  inverted
  />

Expected Result
Popup should appear
Actual Result
Nothing happens
Version
I'm using<EMAIL_ADDRESS>and<EMAIL_ADDRESS>Test case
I'm not sure how to make one as I'm not really sure what's the underlying issue :\

Duplicate #1187. There is a simple fix, your component should spread unhandled props:
class Foo extends Component {
  render() {
    const { children, ...rest } = this.props
    return (
      {children}
    );
  }
}


Make ReactionRemoveEmoji::emoji a ReactionType

Turns out, we store a ReactionType in the cache, so this change actually
simplifies the cache code.
This has been tested with both Unicode and Custom ReactionTypes.
Fixes #850.

Marked as a breaking change.


improve Flatten errors section's (issues guide) example

The example under the Flatten errors section uses a nested key to define the object schema. This might confuse the readers, as the result returned by the flatten function might also use nested as a key to indicate nested issues.
Before:

After:

Another option would be to rename the keys to nested1 and nested2. What do you think?

I am not sure if I understand. We can't rename the key returned by the flatten method.

What we can do is rename the key of the example input object used (nested -> nestedObject or something else) to make it easier to understand the relation between the input and output. So we have the flexibility to change one object key. That means nested1 and nested2 won't make sense.
To provide more context: While reading the section, initially I was confused.
Input:

Output:

Why is key inside nested? In the input the outer key is not inside nested but in the output it is. But after a while I figured it was one of the standard keys returned by the flatten method.
I think we can improve this using a different name that is not one of the standard keys returned by the flatten method. What do you think?

Renaming all of the keys is even better! Will update this PR shortly.


Error updating theme list

If I click on "Update Theme List" in "ControlPanel/BobSettings/ManageThemes" the following error message is displayed in the console window I used to launch Bob:
Error getting theme info { Error: Directory 'C:**\BobEXE\themes' was not included into executable at compilation stage. Please recompile adding it as asset or script.
at error_ENOENT (pkg/prelude/bootstrap.js:422:17)
at readdirFromSnapshot (pkg/prelude/bootstrap.js:766:29)
at Object.fs.readdirSync (pkg/prelude/bootstrap.js:786:12)
at Object.exports.getThemeInfo ($:/plugins/OokTech/Bob/theme-info.js:29:24)
at Object.$tw.nodeMessageHandlers.getThemeList ($:/plugins/OokTech/Bob/NodeMessageHandlers.js:1381:34)
at WebSocket.$tw.Bob.handleMessage ($:/plugins/OokTech/Bob/NodeWebSocketsSetup.js:151:52)
at WebSocket.emit (events.js:182:13)
at Receiver.receiverOnMessage ($:/plugins/OokTech/Bob/External/WS/lib/websocket.js:720:20)
at Receiver.emit (events.js:182:13)
at Receiver.dataMessage ($:/plugins/OokTech/Bob/External/WS/lib/receiver.js:415:14)
errno: -4058,
code: 'ENOENT',
path: 'C:\snapshot\BobEXE\themes',
pkg: true }
BobExe 1.2.2rc5

I am running (check any that apply, put an x inside the [ ] to check a box, like this: [x]):

[x] Windows
[ ] OSX
[ ] Linux
[ ] Other

and using

[ ] The nodejs version
[x] The single file executable

Before posting I read issue guidelines and:

[x] I am using the newest version
[x] The answer to my question isn't listed in the documentation or this isn't
a question
[x] This is not a duplicate issue
[x] I have not done anything that required me to set acceptance to
I Will Not Get Tech Support For This

I see where that error is coming from, I will fix it. Did it actually prevent themes from being listed? It shouldn't have broken anything.

Themes that are included in the BobExe binary are correctly listed. I do not have additional themes in my Themes folder, so I cannot tell if it works too for this case.

I believe that this is fixed, I will re-open the issue if it persists.


started to add the possibility to keep a model on hold

Pull Request Description
What issue does this change request address? (Use "#" before the issue to link it, i.e., #42.)
What are the significant changes in functionality due to this change request?

For Change Control Board: Change Request Review
The following review must be completed by an authorized member of the Change Control Board.

[ ] 1. Review all computer code.
[ ] 2. If any changes occur to the input syntax, there must be an accompanying change to the user manual and xsd schema. If the input syntax change deprecates existing input files, a conversion script needs to be added (see Conversion Scripts).
[ ] 3. Make sure the Python code and commenting standards are respected (camelBack, etc.) - See on the wiki for details.
[ ] 4. Automated Tests should pass, including run_tests, pylint, manual building and xsd tests. If there are changes to Simulation.py or JobHandler.py the qsub tests must pass.
[ ] 5. If significant functionality is added, there must  be tests added to check this. Tests should cover all possible options.  Multiple short tests are preferred over one large test. If new development on the internal JobHandler parallel system is performed, a cluster test must be added setting, in  XML block, the node <internalParallel> to True.
[ ] 6. If the change modifies or adds a requirement or a requirement based test case, the Change Control Board's Chair or designee also needs to approve the change.  The requirements and the requirements test shall be in sync.
[ ] 7. The merge request must reference an issue.  If the issue is closed, the issue close checklist shall be done.
[ ] 8. If an analytic test is changed/added is the the analytic documentation updated/added?

I still don't quite understand what "holding" part of the outspace means, and why it's useful.  Could you help me understand it a little?

@AaronEpiney

I added an issue

Addressed @PaulTalbot-INL 's comments

Did the changes get pushed? I don't see the commit.

Sorry @PaulTalbot-INL... I forgot to push.
Now you should see the modifications.


Jupyter Notebooks support

I just tried using pipreqs, but it seems useless for my workflow heavily relying on Jupyter notebooks.
Will Jupyter notebooks be supported in the future?

I'm sorry but, Jupyter will not be supported any time soon, I will leave this Issue open for future reference, if someday I find time to look into this.

Any updates here? I would love to use it.

Seems to be possible, someone wrote a wrapper: https://github.com/ivanlen/pipreqsnb

implemented in #414


Small buttons inside d-flex no longer small

Prerequisites

[X] I have searched for duplicate or closed issues
[X] I have validated any HTML to avoid common problems
[X] I have read the contributing guidelines

Describe the issue
After updating to 5.3.0, buttons with class btn-sm are no longer small if inside a d-flex (or d-sm-flex).
The issue was marked as fixed in 2021: https://github.com/twbs/bootstrap/pull/34834
Reduced test cases

What operating system(s) are you seeing the problem on?
macOS
What browser(s) are you seeing the problem on?
Chrome, Safari, Firefox
What version of Bootstrap are you using?
v5.3.0

Hi, please assign me this issue

@GopalDeyDev As mentioned in our contributing guidelines, we don't assign issues. Moreover, in this case, this issue doesn't have any live demo yet and hasn't been analyzed.


Unnecessary files layer1, layer2, layer3, scratch in service/gcs/core/gcs

Are these files used?

Based off the names + size. I'm guessing these are files that are mounted on loopback for gcs tests. @beweedon Do you need these files or could you generate these with a script?

Yeah, these are files which can be generated using a script. If we want, I could write a script and have the storage tests generate and then clean up these files on every run.

Ideally, we should avoid binary assets in repo. I also have some test tar file that I will remove when I get the chance to create a script that generates it.

Cool cool! I've been meaning to add a script for these for a while but haven't gotten around to it. Turns out adding an issue is a very good way to get me to fix a problem :)


updating documentation and version

Please check if the PR fulfills these requirements

[x] Followed the Contributing guidelines.
[x] Tests for the changes have been added (for bug fixes/features) with 100% code coverage.
[ ] Docs have been added / updated (for bug fixes / features)

What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
updating documentation and version

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 100.00%. Comparing base (b03c2ad) to head (cef1949).

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@            Coverage Diff            @@
##              main      #654   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files            5         5
  Lines          387       388    +1
  Branches        96        96
=========================================
+ Hits           387       388    +1

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Merges Kubernetes features into GCT plugin

What this PR does
Merges google-container-tools-intellij into google-cloud-intellij, preserving Git history.
Status
The Kubernetes features are merged into the GCT plugin. All features currently run side by side:

Remaining TODOs

[x] merge code with history preserved
[x] get functionality from both plugins working together in the same plugin
[x] Get all tests to pass
[x] Get build to fully pass with static analytics
[x] bump supported IDE version to minimum supported by the container-tools plugin (2018.2)
[x] set IDEA dev target version to 2018.3
[x] delete old Kokoro project configs
[x] update CI to build correct versions
[x] rename the container-tools module to kubernetes
TODOs in next PRs
[ ] (subsequent PR) rename 'com.google.container..' package naming to 'com.google.kubernetes..'; Note: do not do this until all outstanding PRs in the other branch have been closed and synced with this repo
[ ] (subsequent PR) factor out the container tools core and common-test-lib modules to be shared plugin-wide
[ ] (subsequent PR) refactor documentation (currently all container tools documentation lives in the sub-module)
[ ] (subsequent PR) GCS panel hidden by default
[ ] (subsequent PR) disable/feature-flag container-tools feature
[ ] (subsequent PR) refactor the action tools menu
[ ] (subsequent PR) refactor telemetry according to container-tools strategy

IMPORTANT: Prior to merging to master, GitHub commit squashing needs to be temporarily disabled to preserve history of the container-tools repo

@ivanporty ready for review.
This performs the bulk of the work required to merge the container-tools plugin into GCT.
Apologies for the large PR, but this was one of those rare instances where it would have not been worth it to try and split it up. Regardless most of the changes are just bringing the files over from the other repo here with no changes.

+patflynn just as fyi

LGTM in general, just one small comment, otherwise pretty straightforward merge of modules. Build time though :) this is what I got for my first run - BUILD SUCCESSFUL in 7m 55s. Need to refactor those heavy tests.
BTW, let me take the package name refactoring thing (next PR) if you don't mind - wanted to get a feel for the new structure and make sure I know where all the code went.

sounds good. I did notice an issue manually testing that I'm trying to resolve (an exception during new project creation wizard).
wrt to the package name refactoring, I was thinking we could wait until all open PRs on container tools are merged into this repo (currently there is 1 outstanding). Keeping the package names the same makes it easier to do this (via a patch, or cherry picking).

Sure, let's do it after that one is merged.


FlutterError.reportError is not printed in the logcat when installing the APK manually

Steps to Reproduce
With the hello flutter app:
import 'package:flutter/material.dart';

void main() {
  // Initializing the binding overrides FlutterError.presentError.
  // See https://github.com/flutter/flutter/blob/f6f0d608bac344c113481e59219f69879b208e48/packages/flutter/lib/src/widgets/widget_inspector.dart#L991-L993
  WidgetsFlutterBinding.ensureInitialized();

  FlutterError.reportError(
    FlutterErrorDetails(exception: AssertionError('foo')),
  );
  runApp(const MyApp());
}

// ...

The error is printed with flutter run on an Android emulator:
$ flutter run
Using hardware rendering with device sdk gphone x86 arm. If you notice graphics artifacts, consider enabling software rendering with "--enable-software-rendering".
Launching lib/main.dart on sdk gphone x86 arm in debug mode...
Running Gradle task 'assembleDebug'...                              7.7s
✓  Built build/app/outputs/flutter-apk/app-debug.apk.
Installing build/app/outputs/flutter-apk/app.apk...                 4.8s
Syncing files to device sdk gphone x86 arm...                      142ms

Flutter run key commands.
r Hot reload. 🔥🔥🔥
R Hot restart.
h List all available interactive commands.
d Detach (terminate "flutter run" but leave application running).
c Clear the screen
q Quit (terminate the application on the device).

💪 Running with sound null safety 💪

An Observatory debugger and profiler on sdk gphone x86 arm is available at: http://<IP_ADDRESS>:60824/HmQHeq1fxVY=/

══╡ EXCEPTION CAUGHT BY FLUTTER FRAMEWORK ╞═════════════════════════════════════════════════════════
The following assertion was thrown:
Assertion failed: "foo"
════════════════════════════════════════════════════════════════════════════════════════════════════
The Flutter DevTools debugger and profiler on sdk gphone x86 arm is available at: http://<IP_ADDRESS>:9100?uri=http://<IP_ADDRESS>:60824/HmQHeq1fxVY=/

But when I manually install the APK and run it, the error does not appear in the logcat:
$ adb uninstall com.example.hello_flutter_no_report_error
Success

$ adb install build/app/outputs/flutter-apk/app-debug.apk
Performing Streamed Install
Success

# Start the app
$ adb shell am start com.example.hello_flutter_no_report_error/com.example.hello_flutter_no_report_error.MainActivity
Starting: Intent { act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] cmp=com.example.hello_flutter_no_report_error/.MainActivity }

The assertion error does not show up in adb logcat.
Possible Cause
This is likely happening because of isStructuredErrorsEnabled:
https://github.com/flutter/flutter/blob/f6f0d608bac344c113481e59219f69879b208e48/packages/flutter/lib/src/widgets/widget_inspector.dart#L969-L979
The flutter.inspector.structuredErrors constant flag is likely not set when using flutter build apk --debug and defaults to true on Android.
This results in FlutterError.presentError being overriden with _reportStructuredError
https://github.com/flutter/flutter/blob/f6f0d608bac344c113481e59219f69879b208e48/packages/flutter/lib/src/widgets/widget_inspector.dart#L991-L993
_reportStructuredError sends errors to developer.postEvent:
https://github.com/flutter/flutter/blob/f6f0d608bac344c113481e59219f69879b208e48/packages/flutter/lib/src/widgets/widget_inspector.dart#L953
But I don't think developer.postEvent is wired up to stdout of the app.
I'm missing some context behind the functionality here, perhaps flutter.inspector.structuredErrors should default to false instead and only be enabled by supporting tools so the APK can work on its own. Internally, there are use cases where the APK is built separately and executed without the Flutter tool. (See also http://shortn/_fVpZ7QSo3P)

cc @kenzieschmoll, any thoughts on the above?

I can reproduce this on stable and master. No logs for the assertion error visible when using adb logcat.
flutter run
══╡ EXCEPTION CAUGHT BY FLUTTER FRAMEWORK ╞═════════════════════════════════════════════════════════
The following assertion was thrown:
Assertion failed: "foo"
════════════════════════════════════════════════════════════════════════════════════════════════════

flutter doctor -v (Stable)
[✓] Flutter (Channel stable, 3.0.2, on macOS 12.4 21F79 darwin-arm, locale en-US)
    • Flutter version 3.0.2 at /Users/nabeelparkar/fvm/versions/stable
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision cd41fdd495 (13 days ago), 2022-06-08 09:52:13 -0700
    • Engine revision f15f824b57
    • Dart version 2.17.3
    • DevTools version 2.12.2

[✓] Android toolchain - develop for Android devices (Android SDK version 33.0.0-rc4)
    • Android SDK at /Users/nabeelparkar/Library/Android/sdk/
    • Platform android-33, build-tools 33.0.0-rc4
    • ANDROID_SDK_ROOT = /Users/nabeelparkar/Library/Android/sdk/
    • Java binary at: /Applications/Android Studio.app/Contents/jre/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 11.0.12+0-b1504.28-7817840)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 13.4.1)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • CocoaPods version 1.11.3

[✓] Chrome - develop for the web
    • CHROME_EXECUTABLE = /Applications/Brave Browser.app/Contents/MacOS/Brave Browser

[✓] Android Studio (version 2021.2)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 11.0.12+0-b1504.28-7817840)

[✓] IntelliJ IDEA Ultimate Edition (version 2022.1.2)
    • IntelliJ at /Applications/IntelliJ IDEA.app
    • Flutter plugin version 68.1.4
    • Dart plugin version 221.5787.37

[✓] VS Code (version 1.68.1)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.42.0

[✓] Connected device (2 available)
    • macOS (desktop) • macos  • darwin-arm64   • macOS 12.4 21F79 darwin-arm
    • Chrome (web)    • chrome • web-javascript • Brave Browser <IP_ADDRESS>

[✓] HTTP Host Availability
    • All required HTTP hosts are available

• No issues found!

flutter doctor -v (Master)
[✓] Flutter (Channel master, 3.1.0-0.0.pre.1317, on macOS 12.4 21F79 darwin-arm, locale en-US)
    • Flutter version 3.1.0-0.0.pre.1317 on channel master at /Users/nabeelparkar/fvm/versions/master
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision d4929bc828 (6 hours ago), 2022-06-20 20:09:05 -0400
    • Engine revision ceac23d7a9
    • Dart version 2.18.0 (build 2.18.0-190.0.dev)
    • DevTools version 2.14.0

[✓] Android toolchain - develop for Android devices (Android SDK version 33.0.0-rc4)
    • Android SDK at /Users/nabeelparkar/Library/Android/sdk/
    • Platform android-33, build-tools 33.0.0-rc4
    • ANDROID_SDK_ROOT = /Users/nabeelparkar/Library/Android/sdk/
    • Java binary at: /Applications/Android Studio.app/Contents/jre/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 11.0.12+0-b1504.28-7817840)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 13.4.1)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Build 13F100
    • CocoaPods version 1.11.3

[✓] Chrome - develop for the web
    • CHROME_EXECUTABLE = /Applications/Brave Browser.app/Contents/MacOS/Brave Browser

[✓] Android Studio (version 2021.2)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 11.0.12+0-b1504.28-7817840)

[✓] IntelliJ IDEA Ultimate Edition (version 2022.1.2)
    • IntelliJ at /Applications/IntelliJ IDEA.app
    • Flutter plugin version 68.1.4
    • Dart plugin version 221.5787.37

[✓] VS Code (version 1.68.1)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.42.0

[✓] Connected device (2 available)
    • macOS (desktop) • macos  • darwin-arm64   • macOS 12.4 21F79 darwin-arm
    • Chrome (web)    • chrome • web-javascript • Brave Browser <IP_ADDRESS>

[✓] HTTP Host Availability
    • All required HTTP hosts are available

• No issues found!

It is currently probably a hack that we are enabling by default for all non-web apps. The right solution here would be to add support from dds / the vm service to allow specifying some extensions values we want to set on the first vm service connection (https://github.com/dart-lang/sdk/issues/44611 CC @bkonyi). That way we can enable the structured errors when a vm service connection is present and not otherwise.
Another option would be to make sure that we show the errors in log cat but that these logs aren't duplicated in the flutter tools output. We could use some invisible character at the beginning of the line and flutter tools can be smart enough to not show these (because they'd be duplicates).


Wrong enhanced packet size when it has a comment

Hi, based on what I see in PcapNgWriteEnhancedPacket function, sizeof(EndOption) is added twice if a comment is provided.
Regards.

https://github.com/microsoft/etl2pcapng/pull/34
We just found this bug today and it will get fixed in this PR.


License and CLA text

Added Apache 2.0 license text file, and brief CLA language in README.md

👍

👍


Migrate all tests to expect

Currently, the most important part of tests are written with 'yeoman-assert'.
'expect' looks great from the code readability point of view, helping with the code maintenance.
New tests for #1 and #3 have been written using 'expect'. We need to migrate all tests left to 'expect'.

Migration completed in Commit 928387744ec3e5476b7b946ee1af999bc752d346


[FLOC-4004] Add forgotten GCE unit tests.

Found these sitting in one of my git trees. Thought they would have more use if they were checked in.

:heavy_check_mark: Thanks, these looks good.
Merge when green.

Yea, these were actually how I was addressing the 'URL parsing is terrible comment'. I was sort of embarrassed when I realized I didn't even check in the proof that it was better now.


refactor(ci): Switch to Jenkins

Stop using CircleCI for the build pipeline. This change
switches to using a Dockerfile to build and test the
provider plugin.
Semver: patch

I did play with a matrix build here which works nicely. That said, given how these tests work sequential runs might be better. That's still doable with a loop over GO_VERSIONS but the explicitness isn't bad either.

Thanks for experimenting.  For me, the matrix is better.  We're used to it and it's less code.  Will switch.


minikube default memory is not enough for kube-registry

My kube-registry job is hanging there forever and kubectl describe indicates it's unable to run due to lack of memory available. This is solved by running minikube start with larger --memory 8192 in setup_host.sh. Although I don't know what's the minimum memory requirement for e2e test.
Version
minikube version: v0.25.0

@JimmyCYJ

minikube start --help | grep mem
      --memory int                      Amount of RAM allocated to the minikube VM in MB (default 2048)

Default one is 2048 MB.

Thanks @incfly for reporting.. I am playing around with more memory and cpu's and will update the script. I am also testing with 8192...

I think I encountered similar memory issue when running e2e tests some time ago, so I set the default memory to 5000: minikube config set memory 5000.


Report metrics from custom-plugin-monitor

Add a new field metricsReporting (true by default) in the custom-plugin-monitor config file.
By setting the metricsReporting field to true, custom-plugin-monitor will report metrics when temporary/permanent problems happen.
The behavior was specified in the NPD metrics design doc here.
For example, when I make the custom plugin script to report problem (by manually editing the script to force it return error), I will see:
$ curl http://localhost:20257/metrics
# HELP problem_counter Number of times a specific type of problem have occurred.
# TYPE problem_counter counter
problem_counter{reason="NTPIsDown"} 5
# HELP problem_gauge Whether a specific type of problem is affecting the node or not.
# TYPE problem_gauge gauge
problem_gauge{reason="NTPIsDown",type="NTPProblem"} 1

This PR maintains backward compatibility on existing custom-plugin-monitor configs.
This PR is part of #284:

[ x ] Implement feature in System Log Monitor and Custom Plugin Monitor, to allow them to report metrics.

Most of the heavy lifting has been done in #300 .
I tried to update the README for custom-plugin-monitor, but seems that's not necessary:

The README for custom-plugin-monitor simply points to its design doc.
In the design doc, all common configuration flags (e.g. rules, conditions) were omitted.

Since the metricsReporting flag is now a common config flag used by both system-log-monitor and custom-plugin-monitor, I don't think it's necessary to add it to the custom-plugin-monitor design doc.

/assign @wangzhen127
/cc @Random-Liu

/cc @andyxning
Hi Ning, could you also help take a look of this PR? Thanks! Since you are the original author of this plugin, I want to hear your opinion.

/ok-to-test

My bad. I'll fix the test.
Also, since Lantao is back now:
/assign @Random-Liu

@Random-Liu Hi Lantao, sorry for the delay. I just fixed the tests. Could you help take a look? Thanks!

/lgtm


Disable logging completely

I try to use Javalin for a Spigot plugin and want to disable all the logging Javalin does. So far I was able to disable all the Javalin-logging with JavalinLogger.enabled = false but I still get all the logging from jetty. I tried to disable that with many different providers, but none worked. (log4j, slf4j-simple. or even slf4j-nop). The only method that disabled the jetty-logging was to not include any slf4j implementation at all but this throws the warning in Javalin, that no slf4j providers were found.
Is there any solution to disable ALL the logging from Javalin and jetty?

but I still get all the logging from jetty

Yeah, Jetty does its own logging, and they don't have any option to disable it programmatically anymore: https://stackoverflow.com/questions/72673433/adjusting-logging-programmatically-in-jetty-11. Seems you can disable it completely though.


Exception: Call to Node module failed with error: ReferenceError: window is not defined

first request works fine on on refresh throws error
Exception: Call to Node module failed with error: ReferenceError: window is not defined
at Ng2Webstorage.initStorageListener (/Users/roman_petrenko/git/source/elixir/node_modules/ng2-webstorage/bundles/core.umd.js:354:13)
at new Ng2Webstorage (/Users/roman_petrenko/git/source/elixir/node_modules/ng2-webstorage/bundles/core.umd.js:332:14)
at NgModuleInjector.AppServerModuleInjector.createInternal (/AppServerModule/module.ngfactory.js:576:28)
at NgModuleInjector.create (/Users/roman_petrenko/git/source/elixir/node_modules/@angular/core/bundles/core.umd.js:8979:80)
at NgModuleFactory.create (/Users/roman_petrenko/git/source/elixir/node_modules/@angular/core/bundles/core.umd.js:8953:22)
at /Users/roman_petrenko/git/source/elixir/node_modules/@angular/core/bundles/core.umd.js:8523:65
at ZoneDelegate.invoke (/Users/roman_petrenko/git/source/elixir/node_modules/zone.js/dist/zone-node.js:229:26)
at Object.onInvoke (/Users/roman_petrenko/git/source/elixir/node_modules/@angular/core/bundles/core.umd.js:4427:41)
at ZoneDelegate.invoke (/Users/roman_petrenko/git/source/elixir/node_modules/zone.js/dist/zone-node.js:228:32)
at Zone.run (/Users/roman_petrenko/git/source/elixir/node_modules/zone.js/dist/zone-node.js:113:43)
at NgZone.run (/Users/roman_petrenko/git/source/elixir/node_modules/@angular/core/bundles/core.umd.js:4296:66)
at PlatformRef_.bootstrapModuleFactoryWithZone (/Users/roman_petrenko/git/source/elixir/node_modules/@angular/core/bundles/core.umd.js:8521:27)
at PlatformRef.bootstrapModuleFactory (/Users/roman_petrenko/git/source/elixir/node_modules/@angular/core/bundles/core.umd.js:8504:25)
at NodePlatform.bootstrapModule (/Users/roman_petrenko/git/modules/platform-node/node-platform.ts:505:31)
at NodePlatform.serializeModule (/Users/roman_petrenko/git/modules/platform-node/node-platform.ts:153:12)

So it's a problem with that library you're using Ng2Webstorage. I believe that library wasn't built with webworkers/universal in mind, they're just accessing the window without testing to see if it's undefined first. Maybe you can create an issue with that repo so they can try and fix those issues?
On the bright side, there's actually a nice StorageService built into the project, that handles localStorage in a platform-specific way you can use :)
It uses Dependency injection, so on the server it's just getting/setting a local variable (you could connect this to something like Redis/etc if you'd want to), and on the browser it's using localStorage
You can see an example of it in use on the platform-examples page here
constructor (private storage: StorageService) {}

ngOnInit() {
  this.storage.setItem('test', 'This came from Storage within each Platform !!');
  let storedItem = this.storage.getItem('test');
}

Hope that helps!

Thanks a lot for advice!!!!!!!!!!! You rocks!


Combine socketplane/libovsdb and ebay/libovsdb

Background
:wave: I'm one of the original authors of libovsdb and the only active maintainer left of socketplane/libovsdb.
I note in your README that your motivation for forking the repository was as follows:
This fork has been created to encourage changes and patches to ensure this version of the library works with go-ovn.

This sounds like a practical difference, not a philosophical one. You had changes to make, there hadn't been any activity on the upstream repository for a while, and you had a job to do.
Motivation
Thanks to libovsdbs usage in go-ovn, and for my involvement with ovn-kubernetes I've been able to find time to work on libovsdb again.
Aside from the changes I made in socketplane/libovsdb I've contributed #35, and I have plans with @amorenoz to get #31 merged soon so we can generate code for clients. Once we've tested this with go-ovn, I'd like to help pull together a v1.0 release. After which, I have a Server implementation that I'm planning to contribute in the coming months which can be used to try out various data storage formats, or for testing the client.
I can't maintain socketplane/libvosdb on my own and it's unclear how this fork is being managed.
The MAINTAINERS file still has my name in it :wink:
Proposal
I would like to propose that we work together and merge these two repos in to one.

We merge the ebay fork in to socketplane
We add myself, @hzhou8 and whomever else is interested as maintainers to the repository, updating the MAINTAINERS file in the process.
We donate the repository from the socketplane repository over to either ovs or ovn-org. This will provide the project with some governance too

/cc @trozet as a representative from ovn-org
Code Impact
I've taken the liberty of merging the two repos here for what this would look like.
The main differences are:

It uses Github Actions for CI vs. Travis
A lot of linting issues, picked up by golangci-lint have been fixed

Impact on users
I don't anticipate there being any negative impact on users. Only positives.

👋 @dave-tucker welcome back to libovsdb!
First of all I agree with your proposal. As you have seen in the README, this eBay fork of libovsdb was merely because of no response for my PR (small but critical) in the original socketplane repo. We initially forked it and fix internally in eBay so that go-ovn can work internally. Later since we (eBay) decided to open-source go-ovn, which depends on libovsdb and the fixes on top of it, we had to make sure the eBay modified version of libovsdb is open-sourced as well, hence this forked repo existed publicly. Now that you are back and socketplane repo is back to life, it makes sense to "upstream" back.
In fact, just a week before you came back, while I am trying my best to maintain these repos, I also started discussing internally in eBay about donating go-ovn and libovsdb to ovn-org/ovs, partly because it is getting more and more popular in upstream ovn-k8s community, and partly because of my personal changes. It is very similar to your proposal. However, there will be more management discussions in eBay, and I am not sure about legal processes, which could be slow (I guess there is no legal issue given the Apache license, but I am not an expert on that). It is kind of a coincidence that you came back and proposed this at the right time!
I also briefly mentioned your proposal in today's OVN meeting. People are positive on this potential move (to either openvswitch or ovn-org).
I'll check with eBay management again and get back ASAP.

thanks @hzhou8

@hzhou8 I've completed the merge with your LGTM over in socketplane/libovsdb#71 and I've also sent you an invite to the socketplane org which will add you to the libovsdb-maintainers group and grant you merge access. Should eBay management want to make any changes to the NOTICE file etc... I'm more than happy to accommodate them.


Add riprap microservice

https://github.com/mjordan/riprap

Step one get it setup as a stand alone service, handling alpaca integration will be a separate issue, likely against the alpaca repo

Reference implementation from roblib: https://github.com/roblib/Islandora-Devops.riprap

@nigelgbanks FYI I did build a docker image a while ago to use it with the Ansible playboook at https://gitlab.com/nikathone/riprap_docker for demonstration purposes. Not sure if you might something to reuse.

@nikathone thanks for letting me know I'll have a read through and see what I can use!

Merged in here: https://github.com/Islandora-Devops/isle-buildkit/pull/113


command not found: node-prune

$ go get github.com/tj/node-prune/cmd/node-prune
$ node-prune
// command not found: node-prune

go version go1.9.2 darwin/amd64

ah I forgot that $GOPATH/bin should be in your $PATH, that's one thing you have to set up after you install Go if you want to install binaries this way

nice~~ It's really helpful！


Edits for 'tips' documentation.

Fixed 'inherent' typo and made a few other small edits for readability.

Thank you for the improvements!


fixing two special character encoding issues when testing on other locales

Hi,
we have 2 minor issues when building bc-java on a German windows system. Both come from some strings in test cases, containing special characters  (ä and π), which we encode as \u????. Afterwards all tests work fine on our systems.
I hope there is no problem with this pull request.
thanks & regards,
daniel

Thanks for the update. These are now merged.


Add restricted methods

Prevent Grift from mocking anything internal, or any internal dependencies.
This includes all Grift, Grift:: and Minitest classes/modules.
Also String :to_sym or Array :map :push :count :empty?  or Hash :[] Class :singleton_class :instance_methods :remove_method :define_method :alias_method :send

Also prevent a method from being mocked twice or at least prevent the true cached method from being overwritten.


How to set ambient pressure

I am trying to set the ambient pressure via the set_ambient_pressure method. From the datasheet I took that the value needs to be in hectopascal if I am not mistaken. So I am trying the following:
from scd4x import SCD4X

pres = pressure_data_from_some_sensor_in_hectopascal

scd41 = SCD4X(quiet=False)
scd41.start_periodic_measurement()

scd41.set_ambient_pressure(pres)

But it doesn't seem to be working. I have tried giving it an int and a float but both throw errors:
pres is an int:
Traceback (most recent call last):
   File "/home/pi/homelab/smarthome/breakout_garden/src/breakout.py", line 170, in <module>
     process_request()
   File "<decorator-gen-1>", line 2, in process_request
   File "/home/pi/.local/lib/python3.7/site-packages/prometheus_client/context_managers.py", line 66, in wrapped
     return func(*args, **kwargs)
   File "/home/pi/homelab/smarthome/breakout_garden/src/breakout.py", line 159, in process_request
     scd41.set_ambient_pressure(int(pres))
   File "/home/pi/.local/lib/python3.7/site-packages/scd4x/__init__.py", line 132, in set_ambient_pressure
     self.rdwr(SET_PRESSURE, value=ambient_pressure)
   File "/home/pi/.local/lib/python3.7/site-packages/scd4x/__init__.py", line 52, in rdwr
     msg_w = i2c_msg.write(self.address, struct.pack(">HHb", command, value, self.crc8(value)))
 struct.error: byte format requires -128 <= number <= 127

pres is a float:
Traceback (most recent call last):
   File "/home/pi/homelab/smarthome/breakout_garden/src/breakout.py", line 170, in <module>
     process_request()
   File "<decorator-gen-1>", line 2, in process_request
   File "/home/pi/.local/lib/python3.7/site-packages/prometheus_client/context_managers.py", line 66, in wrapped
     return func(*args, **kwargs)
   File "/home/pi/homelab/smarthome/breakout_garden/src/breakout.py", line 159, in process_request
     scd41.set_ambient_pressure(float(pres))
  File "/home/pi/.local/lib/python3.7/site-packages/scd4x/__init__.py", line 132, in set_ambient_pressure
     self.rdwr(SET_PRESSURE, value=ambient_pressure)
   File "/home/pi/.local/lib/python3.7/site-packages/scd4x/__init__.py", line 52, in rdwr
     msg_w = i2c_msg.write(self.address, struct.pack(">HHb", command, value, self.crc8(value)))
   File "/home/pi/.local/lib/python3.7/site-packages/scd4x/__init__.py", line 157, in crc8
     for byte in data:
 TypeError: 'float' object is not iterable

In what form does the pressure value have to be provided to the set_ambient_pressure method?

This is an error in the Pimoroni library and occurs with several functions for sending settings to the SCD4X, like setting the pressure or altitude.
If you change the format of the struct from ">HHb" to ">HHB" the command works. The original format string interprets the checksum as a signed byte instead of an unsinged byte.
     msg_w = i2c_msg.write(self.address, struct.pack(">HHb", command, value, self.crc8(value)))

So simply edit line 52 of the file:
/home/pi/.local/lib/python3.7/site-packages/scd4x/scd4x/__init__.py
(note that the .local folder is hidden)

O, and another important thing:
The SCD4X has to be idle for changing settings, so don't start the measurement BEFORE changing the settings. You can find that in the Sensiron datasheet (link)
If you change your code (and the init.py in the library, as I mentioned earlier) it should work fine. So:

from scd4x import SCD4X
import time
pres = pressure_data_from_some_sensor_in_hectopascal
scd41 = SCD4X(quiet=False)
scd41.set_ambient_pressure(pres)
time.sleep(3)
scd41.start_periodic_measurement()

Thanks for the solution.
But if I read the data sheet correctly the set_ambient_pressure can actually be sent during periodic measurements.
From the data sheet:
3.6.5 set_ambient_pressure
Description: The set_ambient_pressure command can be sent during periodic measurements to enable continuous pressure
compensation.

But the other functions like set_sensor_altitude must be set while the sensor is idle as you have described.

But if I read the data sheet correctly the set_ambient_pressure can actually be sent during periodic measurements.

Yes, you are right about that, I see now. Strange, it is one of the few things allowed during execution. I did not check the data sheet when I reacted yesterday. I found your issue and I ran into the same problem while trying to set the altitude earlier, but I had a workaround for that. So it had no priority for me 😉.


Chrome Window Occasionally Freezes on Regolith with Sway

Sway Version: 1.8
Description:
I am experiencing an issue where a Chrome window sporadically freezes while I'm using the Regolith Linux desktop environment, which is built on top of Sway. This problem occurs without a clear pattern, but it tends to happen after prolonged use of Chrome. When the freeze occurs, the Chrome window becomes unresponsive to both keyboard and mouse input, although other applications and system functions seem to operate normally.
Steps to Reproduce:

Start the system and log into the Regolith desktop environment.
Open Chrome and navigate to various websites.
Continue normal use of Chrome, including opening new tabs, watching videos, etc.
After an unspecified amount of time, one of the Chrome window remains frozen on the image it reproduces. You can see that when changing tabs the title of the window changes but you do not see those changes reflected graphically.

This is solved with sway 1.9.


A question about metrics on ddp

Thanks for the nice work! 🥳🥳🥳
Backgroud
The new metrics package is released with build-in ddp support.
DistributedSampler is used by dataloaders to work with ddp.
It adds extra samples to make the samples evenly divisible.
This means during evaluation and testing, the added extra samples affect the eval result.
Question
Does the metrics package remove the extra redundant samples to make sure the eval result is not affected?
I have looked into the code and find the answer is NO.
Did I miss something or it's just not been resolved for now?

Hi @haichao592 , AFAIK the DistributedSampler simply does not behave like this. It only divides the dataset into disjunct subsets and does not add any extra samples. This is also the reason, we haven't implemented this.

@justusschock, the DistributedSampler actually adds samples from the start of the dataset to make the number of examples evenly divisible:
        # add extra samples to make it evenly divisible
        indices += indices[:(self.total_size - len(indices))]

Reference: https://github.com/pytorch/pytorch/blob/master/torch/utils/data/distributed.py#L79

Okay, thanks @zerogerc learned something new :)
But to answer the question here: No we don't over that and I also think we can't do that so easily. Because we don't know which samples that are (there may also be shuffling) and we also don't know which batch you currently feed in your metric. So far this is only a module that calculates and syncs with some sanity checks. The more advanced features are yet to come, but I'm not sure, if this is possible :)
@SkafteNicki do you think, we can add this feature?

Hi @justusschock, just my thoughts on this matter.
I believe that even divisibility is only critical for backward propagation and gradient calculation. I think that writing a distributed sampler which does not add additional samples would solve the problem for the metrics calculation.

I was neither aware of this, and cannot really understand why this is default behavior of pytorch (at least without any kind of warning).
I guess that the only way to prevent this would be to write a custom DistributedSampler that corrects this.

@SkafteNicki @zerogerc  when you think about it, this makes sense (and can not be changed that easily without dropping the last batches), since you cannot sync/reduce something that is not available on some of the processes (which would be the case if you have a not evenly divisible number of batches/samples.

@justusschock for something like that to work, a torch.distributed.barrier would be needed before any reduction?

@justusschock, @SkafteNicki
One more concern.
I think that custom sampler would break the MEAN reduce operation for metrics. For example, accuracy cannot be correctly reduced if each process handled the different number of examples. For correct reduction, each process should calculate the number of handled examples. Another approach is to return tps and sups and always use SUM operation to reduce ddp.

@zerogerc we are aware of that problem, and I have an upcoming PR that will fix that issue by using SUM to sync metric states (for accuracy tps and sups) which afterwards gets divided

This problem was also discussed in pytorch (https://github.com/pytorch/pytorch/issues/22584) with the solution that the only way to do this would be to keep track of the sample ids and then filter the computations based on that.
Interestingly enough this is the very reason the official imagenet example only adds distributed sampler to their train dataloader and not their validation dataloader (https://github.com/pytorch/examples/blob/49ec0bd72b85be55579ae8ceb278c66145f593e1/imagenet/main.py#L216-L233)

I think that tracking of sample ids and filtering would add significant overhead to validation step.

Judging from the implementation of DistributedDataParallel the computation only hangs if the gradient computation is required, so the uneven distribution should work. Needs testing, though.

Judging from the implementation of DistributedDataParallel the computation only hangs if the gradient computation is required, so the uneven distribution should work. Needs testing, though.

@zerogerc did you test it?

This issue should be solved by this PR https://github.com/PyTorchLightning/pytorch-lightning/pull/5141 which enables support for even input in LightningDDP


[docs/enhancement] - commaai/openpilot/README.md - tweaking a few things in comma ai open pilot README.md file (layout, ToC - Table of Contents, Grammar, etc.)

[docs/enhancement] - commaai/openpilot/README.md - tweaking a few things in comma ai open pilot readme file (layout, ToC - Table of Contents, Grammar, etc.)
this PR does basically consist of minor tweaks within:

improving overall document grammar
improving overall document layout
improving overall document style
adding in a table of content to the document
adding in logos of license and company to the document

the overall motivation behind such lies within:

improving overall document quality
improving overall document accessibility
making the document easier to be read
making the document more accessible to be read

Furthermore:

helping to strike a better first impact whenever opening the document which can potentially
lead to more views of the repository
lead to more forks of the repository
lead to more commits to the repository
lead to more stars to the repository

Cheers

done. fixed

dear gentleman, please feel free to spot in any further feedback. cheers

it had conflicts with our internal version, so we cherry picked the changes and it will be in next release. Thansk.


Assistance on how to configure the go-elasticsearch client to not use cached IPs while using Opensearch service.

What version of Go are you using (go version)?
go version go1.16.14 darwin/amd64
What version of go-elasticsearch are you using (go-elasticsearch version)?
Client version : github.com/elastic/go-elasticsearch/v8
What did you do?
We see that the go-elasticsearch client was not able to reach the aws elasticsearch at the end of cluster upgrade when old nodes were getting deleted. Client(go-elasticsearch) was not able to reach aws ES for at least 10 minutes with connection timeout error before connection getting reset and it started working fine.
Did check with the AWS Elasticsearch team, They mentioned that

Issue exists with go-elasticsearch client, when a configuration change is made to elasticsearch, A new fleet of nodes is launched to match the desired configuration. These new nodes are joined to the cluster with new IP addresses. Data is then moved from the old nodes to these new nodes and once this is complete then the new nodes take over completely and the old nodes with their old IP addresses are terminated.
If a client is configured to use persistent http/https connections then in the client itself the old node IPs are still being used and hence the connection will fail until the endpoint is updated with new node IPs depending on how long the persistent connection is set up to last.

By default, This is how our client looks like
func (esClient *ESClient) Init(esUrl string) {

	var err error
	esClient.client, err = es.NewClient(es.Config{
		Addresses: []string{
			esUrl,
		},
	})
	...
	...

}

We tried the following things to fix the issue, Unfortunately, None of them worked.

Disabling persistent connections by Setting the DisableKeepAlives:true.

func (esClient *ESClient) Init(esUrl string) {

    var err error
    esClient.client, err = es.NewClient(es.Config{
        Addresses: []string{
            esUrl,
        },
        Transport: &http.Transport{
            // Disable long-lived connection
            DisableKeepAlives: true,
            TLSClientConfig: &tls.Config{InsecureSkipVerify: true},
        },
    })
    ...
    ...
}

Closing the idle connection every 3 seconds.

func (esClient *ESClient) Init(esUrl string) {

    var err error

    Transport := &http.Transport{
        // Disable long-lived connection
        DisableKeepAlives: true,
        TLSClientConfig: &tls.Config{InsecureSkipVerify: true},
    }

    go func(transport *http.Transport) {
        for {
            time.Sleep(3 * time.Second)
            transport.CloseIdleConnections()
        }
    }(Transport)

    esClient.client, err = es.NewClient(
        es.Config{
        Addresses: []string{
            esUrl,
        },
        Transport: Transport,
    })
    ...
    ...
}

Tried Setting DiscoverNodesOnStart and DiscoverNodesInterval for initial and periodic sniffing,
But the client didn't start, Started seeing the below error. "msg":"Error getting response","error":"dial tcp :443: connect: connection refused"

func (esClient *ESClient) Init(esUrl string) {

    var err error

    Transport := &http.Transport{
        // Disable long-lived connection
        DisableKeepAlives: true,
        TLSClientConfig: &tls.Config{InsecureSkipVerify: true},
    }

    go func(transport *http.Transport) {
        for {
            time.Sleep(3 * time.Second)
            transport.CloseIdleConnections()
        }
    }(Transport)

    esClient.client, err = es.NewClient(
        es.Config{
        Addresses: []string{
            esUrl,
        },
        Transport: Transport,
        DiscoverNodesOnStart: true,
        DiscoverNodesInterval: 60 * time.Second,
    })
    ...
    ...
}

What did you expect to see?
I expect all requests to pass without any failures throughout the cluster upgrade
What did you see instead?
Connection timeout from go-elasticsearch client at the end of cluster upgrade.

While I cannot give you specific support on your infrastructure, here is some general advice.
The DiscoverNodesOnStart and DiscoverNodesInterval is definitely the right way to do that at the client level. I would recommend you lower the interval, 60 seconds seems a lot if node are coming and going from the cluster. Furthermore, the discovery if enabled is triggered on start and relies on the transport to make a call to /_nodes/http. I don't know the specifics for OpenSearch, but for Elasticsearch, the user would need the monitor or manage permission to access the nodes list. Of course, the first node you target should still be live and part of the cluster to have relevant informations.
I find odd the AWS support states there's an issue with the client while they could have provided the idea of adding a Load Balancer in front of the cluster which would have taken care of the no downtime scenario.
Elastic Cloud does that for you, you are provided with a simple endpoint and we take care of routing, updates and upgrades for you. You can even reach us via the AWS Marketplace!

Thanks for your suggestion.
As mentioned we tried DiscoverNodesOnStart and DiscoverNodesInterval (5 sec), I see client is coming up, But calls to elasticsearch is not happening.  I see the following error :
"dial tcp :443: connect: connection refused"
I don't see any issue with the permission as we invoke /_nodes/http,
Below is the snippet of the response from /_nodes/http :
{
  "_nodes": {
    "total": 17,
    "successful": 17,
    "failed": 0
  },
  "cluster_name": "10xxxxxx98:xxx-xxxx-elasticsearch",
  "nodes": {
    "Xysv2xxxxxxxU_lFOUdUQ": {
      "name": "e9dd66340f69xxxxxxxxxb9000bab3",
      "version": "7.10.2",
      "build_flavor": "oss",
      "build_type": "tar",
      "build_hash": "unknown",
      "roles": [
        "master",
        "remote_cluster_client"
      ]
    },
    "ZHAdCWexxxxxxxQljIY2A": {
      "name": "77c9a4a828b700xxxxxxxxx3298c615e4",
      "version": "7.10.2",
      "build_flavor": "oss",
      "build_type": "tar",
      "build_hash": "unknown",
      "roles": [
        "data",
        "ingest",
        "remote_cluster_client"
      ]
    },
    "obbtysuOQFuaWkbkpWe98g": {
      "name": "e39a13412b50ab86074babe5dc06c215",
      "version": "7.10.2",
      "build_flavor": "oss",
      "build_type": "tar",
      "build_hash": "unknown",
      "roles": [
        "data",
        "ingest",
        "remote_cluster_client"
      ]
    },
    ...
    ...

Is the above fetched information from the elasticsearch cluster is enough for the DiscoverNodesOnStart to work ? Or does it require any other more data ?

Using the makefile at the root of this repo, I ran:
make cluster nodes=3
curl http://<IP_ADDRESS>:9200/_nodes/http | jq
From there you get a payload that is roughly similar to this:
{
  "_nodes": {
    "total": 3,
    "successful": 3,
    "failed": 0
  },
  "cluster_name": "go-elasticsearch",
  "nodes": {
    "u0r1m6NhQW6Gg7sdIiNaDg": {
      "name": "es3",
      "transport_address": "<IP_ADDRESS>:9300",
      "host": "<IP_ADDRESS>",
      "ip": "<IP_ADDRESS>",
      "version": "8.5.0",
      "build_flavor": "default",
      "build_type": "docker",
      "build_hash": "5d6af5890f70cfdb234240f7a1d8c65c6339315d",
      "roles": [
        "data",
        "data_cold",
        "data_content",
        "data_frozen",
        "data_hot",
        "data_warm",
        "ingest",
        "master",
        "ml",
        "remote_cluster_client",
        "transform"
      ],
      "attributes": {
        "testattr": "test",
        "ml.machine_memory": "33563676672",
        "ml.max_jvm_size": "1073741824",
        "xpack.installed": "true",
        "ml.allocated_processors": "24"
      },
      "http": {
        "bound_address": [
          "<IP_ADDRESS>:9200"
        ],
        "publish_address": "<IP_ADDRESS>:9200",
        "max_content_length_in_bytes": 104857600
      }
    },
    "CL0JM2OnSjWqtKVZxBTZIw": {
      "name": "es1",
      "transport_address": "<IP_ADDRESS>:9300",
      "host": "<IP_ADDRESS>",
      "ip": "<IP_ADDRESS>",
      "version": "8.5.0",
      "build_flavor": "default",
      "build_type": "docker",
      "build_hash": "5d6af5890f70cfdb234240f7a1d8c65c6339315d",
      "roles": [
        "data",
        "data_cold",
        "data_content",
        "data_frozen",
        "data_hot",
        "data_warm",
        "ingest",
        "master",
        "ml",
        "remote_cluster_client",
        "transform"
      ],
      "attributes": {
        "ml.machine_memory": "33563676672",
        "ml.allocated_processors": "24",
        "ml.max_jvm_size": "1073741824",
        "xpack.installed": "true",
        "testattr": "test"
      },
      "http": {
        "bound_address": [
          "<IP_ADDRESS>:9200"
        ],
        "publish_address": "<IP_ADDRESS>:9200",
        "max_content_length_in_bytes": 104857600
      }
    },
    "9170hztBRqqdnzXMEF8GTg": {
      "name": "es2",
      "transport_address": "<IP_ADDRESS>:9300",
      "host": "<IP_ADDRESS>",
      "ip": "<IP_ADDRESS>",
      "version": "8.5.0",
      "build_flavor": "default",
      "build_type": "docker",
      "build_hash": "5d6af5890f70cfdb234240f7a1d8c65c6339315d",
      "roles": [
        "data",
        "data_cold",
        "data_content",
        "data_frozen",
        "data_hot",
        "data_warm",
        "ingest",
        "master",
        "ml",
        "remote_cluster_client",
        "transform"
      ],
      "attributes": {
        "testattr": "test",
        "ml.machine_memory": "33563676672",
        "ml.max_jvm_size": "1073741824",
        "xpack.installed": "true",
        "ml.allocated_processors": "24"
      },
      "http": {
        "bound_address": [
          "<IP_ADDRESS>:9200"
        ],
        "publish_address": "<IP_ADDRESS>:9200",
        "max_content_length_in_bytes": 104857600
      }
    }
  }
}

Notice how your payload differs and lacks the publish_address field which the transport seeks to register nodes addresses.


satisfies keyword causes fatal error

Is there a way to use the satisfies keyword? because when I try to do it, it causes a fatal error
const defaults = {
    type: 'page',
    robots: { index: true, follow: true },
} satisfies {
    type: Types
    robots: Robots
}

X [ERROR] Expected ";" but found "satisfies"
      15 │ } satisfies {

What deno version are you running (deno --version)?

Just looked into this. Looks like the reason this works in routes but fails on islands is because fresh's version of esbuild is out of date.

Esbuild added support for satisfies in v0.15.13
Fresh currently uses v0.14.51

I'm opening a PR to bump the dependency. Thanks for reporting @JacobWeisenburger!

great, thanks

When do you think this will be in a release?

When https://github.com/lucacasonato/esbuild_deno_loader/pull/22 lands but I don't know if anyone other than @lucacasonato can merge that PR.

For curious observers who have not been following this super stringently, upstream landed the update that we needed and https://github.com/denoland/fresh/pull/986 is now in the green so hopefully that gets reviewed soon!

This should be fixed in a new tagged release. @kt3k when do you think the next tag will happen?

Probably in the next week. cc @hashrock

Any news on this?


null is not an object

Hello guys!
Today im try create project width react native (for iOS). When i using react-native-html-to-pdf then get error

null is not an object (evaluating '_reactNativeHtmlToPdf.default.convert').

I did follow issue #80, but can't resolve.
Who can help me how to fix this?
"dependencies": {
    "react": "16.8.3",
    "react-native": "0.59.8",
    "react-native-html-to-pdf": "^0.7.0"
  },

Thank you so much!

Are you sure you've linked the files properly?
If you are using Expo and haven't ejected this library will not work.

I got this error on fresh installation react native projects.
   "dependencies": {     "react": "16.8.6",     "react-native": "0.60.5",     "react-native-html-to-pdf": "^0.8.0"   },
either automatic link with react-native link and manual link provided in documentation doesn't work.
Does this package support react native auto link?

I solved this issue by re-install my apps after install this package. Thank you.

how do i make the manual link on Expo?

I faced the same and I re-install the app as u say @khanisak

I solved this issue by re-install my apps after install this package. Thank you.
I put it in import { RNHTMLtoPDF }  and reinstalled the app and finally did not work :(

Solved the issue for android by reinstall the app
For ios pod install in ios folder helped

I have the same problem but reinstall did not solve my problem. Any ideas ?

I am also stuck in this problem. Can any one guide how to link expo with react native modules  and how to solve this problem.

I'm facing the same error, using this with Expo. Could the maintainers help me out?

I was with the same issue and in my case to resolve this I installed a library after that I applied react-native link and solved! I also deleted node_modules and reinstalled them.

you need to restart your metro server after installing the package.


Decide if DockerHub should still be supported

Related to #1.
As of yesterday, May 1st 2021, it's been six months since the new DockerHub retention policy was introduced. That means they will start deleting stale images (6 months or older without push/pull activity) from now on.
All the images were still present today. Not sure if they gave a grace period, since I doubt all versions have been pulled in the last six months. They'll be present for at least another six months because I pulled them all today.
Decide if it's worth the maintenance hassle to continue using DockerHub in addition to GitHub Container Registry.
One benefit is that a lot of tooling defaults to DockerHub for images.
Also consider creating a GitHub action that runs very infrequently (like once every six months) to reset the counter.
Need to do docker pull --all-tags dideler/fish-shell more or less.

Also keep an eye on GitHub Billing: https://github.com/settings/billing
Their docs weren't super clear on how pricing works for GHCR.


Negate var using not

Describe the bug
Negating a var using not v does not work.
To Reproduce
For example, creating a var in State is_false: bool = False and then using rx.cond(not State.is_false, rx.text("negated"), rx.text("not negated")). It always shows the text not negated.
Expected behavior
I expected the var to be correctly negated.
Specifics:

Python Version: 3.11.5
Reflex Version: 0.2.6
OS: macOS 13.5.1 (22G90)
Browser (Optional): Arc; version 1.6.0 (41215)

Additional context
It works using ~State.is_false but it would me more user-friendly if it works using not.

According to what @pickelo said, Python will not let us override the not so we can't do anything about that.

To negate the var, you can use the ~ operator:
rx.cond(~State.is_false, rx.text("negated"), rx.text("not negated"))

Yeah unfortunately we will have to close this, since it's not currently possible without AST manipulation, which we're not getting into at this point.
I implemented #1750 which will raise a TypeError when trying to use a Var with if, and, or or not and suggest the use of our alternative operations. That will have to be enough for now.


Transform op - database is not picked from metadata

Description
closes: #1034
Add table param in create_database function so that can access and use table metadata while creating a hook
What is the current behavior?
Currently, we don't use Table metadata param schema and database while creating so if these values is not set in the airflow connection we are getting an error in the case of snowflake
What is the new behavior?
change
def create_database(conn_id: str) -> BaseDatabase:
    ...

to
def create_database(
    conn_id: str,
    table: object | None = None,
) -> BaseDatabase:
    ...

and use table metadata if available while creating snowflake hook
Does this introduce a breaking change?
No
Checklist

[ ] Created tests which fail without the change (if possible)
[ ] Extended the README / documentation, if necessary

I have posted some findings on https://github.com/astronomer/astro-sdk/issues/1034 also posting here for better visibility

@pankajastro I think we should also define a priority when picking up values for metadata.
P0 - Table object
P1 - Connection id
P2 - Settings(Airflow config ex - schema postgres_default_schema)
P3 - Database defaults

Postgres-related tests are failing because database_table_fixture create below object which has schema astroflow_ci but in our test env it does not exist.
database_table_fixture = (PostgresDatabase(conn_id="postgres_conn), TempTable(_name='', conn_id='postgres_conn', metadata=Metadata(schema='astroflow_ci', database=None), columns=[], temp=True))

@pankajastro I think we should also define a priority when picking up values for metadata. P0 - Table object P1 - Connection id P2 - Settings(Airflow config ex - schema postgres_default_schema) P3 - Database defaults

currently, since this depends on airflow hook too and that is not consistent so not sure how can control this


Added show tree as an alternative command.

Fixes #117.
git gud show tree has been added as a valid command. I should note that there are two parsers which are doing work here: one that is made visible to the user when git gud help is run, (_show_parser_visible), and one which does the actual processing (show_parser).
It's a bit hackish of a solution, so do you have any ideas on how to improve this, @benthayer ?

I agree that this is a bit of a hacky solution. I think that's because it isn't meant to be done. I updated it to reflect how I think it should be, but I'm going to have to think about this before I actually merge.
Looking at #152 , do you think we could somehow detect when someone enters git gud show tree and fail by telling them to use "git gud show-tree"? Feel free to overwrite my code, we can always go back to it.

After thinking about this, I think we can just replace show-tree with show tree.
Would you mind making those updates?

show-tree has been fully replaced.
I also modified the code a bit so that putting additional commands like git gud show solution should be easier.

Merged


Multi Bot

Is there an easier way to do multi bots?
I did screen and python pokecli.py --config ./configs/config1.json then i start another terminal and did the same thing but with config2.json. This method works but it's kinder confusing because when i'm back from afking i won't know which is which.
Other Information
OS: Ubuntu 14.04 LTS

maybe set name for each screen? screen -S name

I use docker to do that. Much more scalable.

My current solution:
screen -S bots -c screenscript
screenscript
layout save default
screen bot1.sh
split -v
focus
screen bot2.sh
split
focus
screen bot3.sh
each bot.sh executes "python pokecli.py -cf configs/config.json -u ... -p ... "
i use a global config and overwrite it iside the bot.sh with bot specific settings.
later you can detach ctrl+a d, and retatch always using screen -r bots

Can someone please explain the docker part?


[UI/DATA BUG]: Dupplicated project after it has been approved by the SR

Problem description
Context: ACM0002
Step to reproduce
Steps to reproduce the behavior:
When a PP create a project, it must be approved by the SR.
After the SR approves it, then the projects are dupplicated in the UI of the PP.
Expected behavior
We can expect the project don't be duplicated
Screenshots

I have the same issue on my local guardian instance and in MGS.
Plus, a colleague of mine met the same issue.

@MarcAntoineLebourgeois Thank you so much for raising this ticket. We are looking at it and will fix the policy asap. Will keep it posted.

Hello @prernaadev01
We've met the same issue in Verra VM0047 policy when working via API. VVB validates a project and sees several copies of it with different statuses. But it's not reproducible through UI

@ilyozzz Thank you so much for the information. Only one ticket should work. We are working on it. Will keep you posted on it.

@ilyozzz We tried it reproducing but we are unable to do it. So, can you please send us API requests and responses, which you are trying to execute the policy. That would be really helpful for us. Thanks.


Form creation

Description
As an administrator, I would like the application to have a built-in form that allows analyzing user preferences.
Acceptance criteria

The form must contain questions that allow selecting a type of learning for the user
The form must save the answers and then deliver a type of learning that will be stored in the user's account

for this story the user should be able to answer the questions in the form

For this we create new responses and a better UX
the user can now answer the question and then recive a type of learning that its stored in the users column