BufferCollection can be indexed by using Proxy

It is possible to provide indexing like Buffer has by using Proxy. Here's an example.
For more information, see Proxy and Reflect on MDN.
class BufferCollection {
  // Declare the index operator.
  [offset: number]: number

  // ...

  static from(
    values: BufferFromTypes | Buffer | BufferCollection,
    byteOffset?: number,
    length?: number,
  ): BufferCollection {
    const buf = new BufferCollection()
    if (values instanceof BufferCollection) {
      buf.push(values.toBuffer())
    } else if (values instanceof Buffer) {
      buf.push(values)
    } else if (
      values instanceof ArrayBuffer ||
      values instanceof SharedArrayBuffer
    ) {
      buf.push(Buffer.from(values, byteOffset, length))
    } else {
      buf.push(Buffer.from(values as any))
    }

    // Return a Proxy that traps the get and set index operators.
    return new Proxy(buf, {
      get(target, key) {
        // Ensure the key is a number.
        const offset = Number(key)
        if (!isNaN(offset)) {
          return target.get(offset)
        }

        // If key is not a number, default to the normal getter.
        return Reflect.get(target, key) as number
      },
      set(target, key, value): boolean {
        // Ensure the key is a number.
        const offset = Number(key)
        if (!isNaN(offset)) {
          target.set(offset, value)
          // Return true to indicate success.
          return true
        }

        // If key is not a number, default to the normal setter.
        return Reflect.set(target, key, value)
      },
    })
  }

  // ...
}

Yeah, of course it's possible now. When I was working on this library, it didn't have proper browser / node.js support. I will have add it when I will have time.

Sounds good. I built my own prototype with this feature for one of my projects. Let me know if you would like me to submit a PR.
One other minor thing is that Buffer returns undefined when you access bytes outside of the expected range whereas BufferCollection throws an error.

PRs are always welcome 👍


Multisession feature w/ configured display to show project description as names

We'd like to add a switch_project API so when in multisession mode, the user is able to switch projects under the Setup page.
Features

New_project button on Setup page prompts User to enter project description
Switch_project header on Setup page shows list of projects available to switch to
Configuration to display project descriptions as the project name on UI is available

@makseq Could you assist with how to read these build failures and how to go about it? It seemed to happen after I committed merge f2b8251 this morning.

@ktl014 Can you merge release/0.7.5 branch here?

Hmmm I did the merge, but seems to be failing around the same issue with the project initialization?


CNAME record for eurobioc2022.bioconductor.org

Currently, the website lives at https://nifty-austin-83f763.netlify.app/. Changing the domain name at Netlify's side results in error, the domain is taken. What can we do to link Netlify to the EuroBioC2022 domain name? @lshep, can you help?

I just created the CNAME record on AWS for eurobioc2022.bioconductor.org that points to the above url.  let me know if it does not resolve in the next 24 hours


github.com/golang/lint now imports golang.org/x/lint

What this PR does / why we need it:
github.com/golang/lint now imports golang.org/x/lint
Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #
Special notes for your reviewer:
Release note:

/lgtm
/approve


[BUG] Microsoft.Security/locations/jitNetworkAccessPolicies@2020-01-01 returns undefined property "location"

API Spec link
https://github.com/Azure/azure-rest-api-specs/blob/b3d5c34b3447f71ca8474aa9d32449aafe3996a2/specification/security/resource-manager/Microsoft.Security/stable/2020-01-01/jitNetworkAccessPolicies.json#L434
API Spec version
2020-01-01
Describe the bug
In the GET response, the location field is returned but not defined in the swagger.
Expected behavior
In the GET response, the location should not be returned, or should be defined in the swagger.
Actual behavior
In the GET response, the location field is returned but not defined in the swagger.
Reproduction Steps

Create the resource.
Call GET API and check the response.

Environment
No response

Related to #30259 and #29198.

@ronf11 Please help take a look, thanks.


under maintenence also suggestion

it says under maintenence when will it come back up? and would this be the best visual ray tracing mod pack? if there are any other mopd packs can you tell me please

Either Aldrnari or this I guess.


i can't add more than 2 keys

how can i add more than 2 binds ? i put one more line and key 3 but the program crashes

Hey, use the latest release here, we have long abandoned that version and format.

oh ok so Ty so much!


rfc: Network Chaos on Kubernetes Service

rendered markdown

Hi @dengruilong, I noticed that the "detailed design" part is not enough properly described.  I think we could help you to enrich this part.
Would you mind us editing this RFC directly in the future?

Glad to hear that. It will be great if you can help enriching the detailed design.

CHAOS-MESH is an excellent K8S failure injection tool than other products, but under the trend of cloudy and mixed clouds, the fault injection tool in the K8S cluster can not meet the business disaster tolerance needs. The failure injection ability must surpass the competition and become a great fault injection product.
This is an excellent proposal and opened my mind.

We need this feat very much.

这是来自QQ邮箱的假期自动回复邮件。

您好，我最近正在休假中，无法亲自回复您的邮件。我将在假期结束后，尽快给您回复。

不错不错

@STRRL Another (rough) thought. Will ingress network chaos works like a charm in this situation :thinking:  ? If the NetworkChaos could be bidirectional, the traffic through service will also be matched during ingress.
(Though, I agree supporting service as the target is much more straightforward and intuitive.)

这是来自QQ邮箱的假期自动回复邮件。

您好，我最近正在休假中，无法亲自回复您的邮件。我将在假期结束后，尽快给您回复。


bug: cannot deploy with next.js

Try to fix:

allow to deploy Next.js examples;
or if not possible - remove next.js examples from the repo;

Now it can be deployed just fine.
Next step is to fix the flush-notes example - https://github.com/waku-org/lab.waku.org/issues/78


v0.8.1_47: Population value at "1800" year is not consistent with values at others year

SEVERITY: Minor
MODULE:  Mountain chart
Platform:

Android Nexus-5 (5.1.1) / Chrome 44.0
Windows 7 / Chrome 45.0
Windows 7 / Firefox 42.0

RELEASE: v0.8.1
STEPS TO REPRODUCE:

Navigate URL: http://static.gapminderdev.org/vizabi/release/v0.8.1/preview/mountainchart.html
Mountain chart is loaded
Click Play
Note that At year 1800 the population is shown in full form while at other years it is shown in short form like 3.2 M.

ACTUAL RESULTS:
At year 1800 the population is shown in full form while at other years it is shown in short form like 3.2 M.
EXPECTED RESULTS:
Population value at "1800" year should be consistent with values at others year.
SCREENSHOT:

done


Mark container within pod as "do not respawn"

I have a container in a pod whose only job is to populate some configuration values within the pod-local etcd on startup. This works fine except that after it exits successfully Kubernetes continually respawns it over and over again.
My current hack is to append && tail -f /dev/null to the container command to allow it to "run" indefinitely.
It would be great if Kubernetes allowed one to specify certain containers as non-respawning in the pod spec.

Is it possible for you to use a container lifecycle hook? http://godoc.org/github.com/GoogleCloudPlatform/kubernetes/pkg/api/v1#Lifecycle
RestartPolicy is almost what you want but it is applied over all the containers in a pod. http://godoc.org/github.com/GoogleCloudPlatform/kubernetes/pkg/api/v1#RestartPolicy

@mikedanese RestartPolicy would be perfect if only it were per-container rather than pod.
I wouldn't mind trying to implement this if there's interest.

cc @bgrant0607 for api changes.

The corner cases around mixed-restart-policy pods is not worth the energy.
This is what lifecycle hooks should do, and if they aren't sufficient, we
should make them sufficient.
On Mon, Jun 15, 2015 at 8:26 PM, Mike Danese<EMAIL_ADDRESS>wrote:

cc @bgrant0607 https://github.com/bgrant0607 for api changes.
—
Reply to this email directly or view it on GitHub
https://github.com/GoogleCloudPlatform/kubernetes/issues/9836#issuecomment-112271587
.

It's true that the most common use cases of sidecar containers, for example data loader and log saver, will run forever. However, IIRC we've occasionally told people to use sidecar containers for various kinds of initial configuration, and in those cases it seems that having the sidecar run once to completion and the other pod restart would be desirable.
I guess the lifecycle hook proposal would be that you merge the configuration container logic into the main container's logic, so that you have just one container, and have the PreStart hook invoke the former?
Anyway, I don't have a strong opinion.

We've thrown out the idea of having two stages in a pod - stage 1 only
completes when stage 0 is done.  E.g. all the containers in stage 1 have
completed successfully.  Like so many other things, it is a matter of
priority and making time for it among the ocean of other things going on :)
On Mon, Jun 15, 2015 at 10:47 PM, David Oppenheimer <
<EMAIL_ADDRESS>wrote:

It's true that the most common use cases of sidecar containers, for
example data loader and log saver, will run forever. However, IIRC we've
occasionally told people to use sidecar containers for various kinds of
initial configuration, and in those cases it seems that having the sidecar
run once to completion and the other pod restart would be desirable.
I guess the lifecycle hook proposal would be that you merge the
configuration container logic into the main container's logic, so that you
have just one container, and have the PreStart hook invoke the former?
Anyway, I don't have a strong opinion.
—
Reply to this email directly or view it on GitHub
https://github.com/GoogleCloudPlatform/kubernetes/issues/9836#issuecomment-112302926
.

Yeah, I was assuming the user would be responsible for orchestrating the dependency between the two containers (e.g. the application in the main container would wait until the configuration data was populated by the other container before finishing its startup).

Pod-level hook or container volume #831 would be the right solution.
Original discussion re. restart policy was #127.

Closing as a dupe of #4282


Download enumerator refactor

Pretty roughly based off the upload enumerator refactor. There's only a couple of places that really needed altering.

Looking good! Now we are really seeing the advantage of the modular design:

Please consider adding the changelog entry now, to explain the change in behavior for download, to avoid forgetting the details at release time

Squash and merge, squash and merge!


Add a launch screen

https://developer.apple.com/library/ios/recipes/xcode_help-image_catalog-1.0/chapters/AddingLaunchImagestoanAssetCatalog.html

I think would be better to use storyboard as launch screen instead of static images. Reference: http://oleb.net/blog/2014/08/replacing-launch-images-with-storyboards/


Add UT for superduper.base.datalayer

Description

Related Issues

Checklist

[ ] Is this code covered by new or existing unit tests or integration tests?
[ ] Did you run make test successfully?
[ ] Do new classes, functions, methods and parameters all have docstrings?
[ ] Were existing docstrings updated, if necessary?
[ ] Was external documentation updated, if necessary?

Additional Notes or Comments

Codecov Report
Attention: 48 lines in your changes are missing coverage. Please review.

Comparison is base (34830a7) 80.33% compared to head (3985b98) 80.49%.
Report is 13 commits behind head on main.

:exclamation: Current head 3985b98 differs from pull request most recent head 6643531. Consider uploading reports for the commit 6643531 to get more accurate results

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #1244      +/-   ##
==========================================
+ Coverage   80.33%   80.49%   +0.15%
==========================================
  Files          95       97       +2
  Lines        6602     6685      +83
==========================================
+ Hits         5304     5381      +77
- Misses       1298     1304       +6

Files
Coverage Δ

superduperdb/base/config.py
100.00% <ø> (ø)

superduperdb/base/datalayer.py
68.61% <100.00%> (+0.45%)
:arrow_up:

superduperdb/components/model.py
93.66% <100.00%> (+11.00%)
:arrow_up:

superduperdb/ext/openai/model.py
96.09% <ø> (+0.64%)
:arrow_up:

superduperdb/ext/torch/model.py
76.80% <ø> (ø)

superduperdb/misc/superduper.py
76.25% <ø> (ø)

superduperdb/base/build.py
65.85% <66.66%> (-1.65%)
:arrow_down:

superduperdb/base/logger.py
86.95% <80.00%> (-3.05%)
:arrow_down:

superduperdb/cli/serve.py
39.28% <50.00%> (+4.28%)
:arrow_up:

superduperdb/cli/stack.py
55.55% <55.55%> (ø)

... and 1 more

... and 2 files with indirect coverage changes

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


Cannot find namespace 'grapesjs.Plugin' in grapejs-mjml index.d.ts

When npm install grapesjs 0.21.1 with grapesjs-mjml 1.0.4 in angular get the following error:
Error: node_modules/grapesjs-mjml/dist/index.d.ts:99:23 - error TS2503: Cannot find namespace 'grapesjs'.

99 declare const plugin: grapesjs.Plugin<PluginOptions>;
                         ~~~~~~~~

To reproduce the issue, you check out the following repository:
https://github.com/zeskysee/angular-grapejs-mjml-issue

Fixed here https://github.com/GrapesJS/mjml/releases/tag/v1.0.5


Adds Wordpress example

Adds the Wordpress example to resolve #57. Also includes a new version of replicatedservice.py that accepts three new properties:
cluster_ip: to set the ip of a service
privileged: to create privileged containers
volumes: to mount volumes

@bmelville This should work.

Good catch, thanks.


Lazy resolution in ternaries

What is the purpose of the ifElse alternative to a simple ternary?
const execIfFunc = x => (typeof x === 'function' ? x() : x);

/**
 * This is a higher order function that accepts a boolean condition and will
 * return a function allowing you to provide if/else values that should be
 * resolved based on the boolean condition.
 *
 * @param  {Boolean|() => Boolean} condition:
 *   The condition to test against. This can be a function for lazy resolution.
 *
 * @return {(X|() => X, Y|() => Y) => X|Y}
 *   A function where the first paramater is the "if" and the second paramater
 *   is the "else".  Each of these allows lazy resolving by providing a function.
 *
 * @example
 *   const ifDev = ifElse(process.env.NODE_ENV === 'development');
 *   ifDev('foo', () => 'lazy resolved');  // => 'foo'
 */
export default function ifElse(condition) {
  return (then, or) => (execIfFunc(condition) ? execIfFunc(then) : execIfFunc(or));
}

Aren't ternaries already resolved lazily in JavaScript?

Yeah, you are correct, however a ternary isn't as composable as used within the webpack config generation.  TBH I have started moving away from this implementation in some of my more recent work, into a much simpler form.

Great! Makes sense, just wanted to make sure I understood the things.
Thanks for the clarification! 💃


Importing astro-purgecss in astro.config.ts could not be resolved by TypeScript.

Describe the bug
When importing astro-purgecss in astro.config.ts, a TypeScript error is reported.
error TS7016: Could not find a declaration file for module 'astro-purgecss'. '<PROJECT_PATH>/node_modules/.pnpm/astro-purgecss<EMAIL_ADDRESS>implicitly has an 'any' type.

There are types at '<PROJECT_PATH>/node_modules/astro-purgecss/dist/index.d.ts', but this result could not be resolved when respecting package.json "exports". The 'astro-purgecss' library may need to update its package.json or typings.

To Reproduce

Add import purgecss from "astro-purgecss"; at top of astro.config.ts
If editor don't have inline hint, run pnpm tsc --noEmit (or npx, etc.)

Screenshots

Additional context
As mentioned by TypeScript docs, the "types" field in package.json is no longer used if there is an exports field:
https://github.com/codiume/orbit/blob/main/packages/astro-purgecss/package.json#L12
https://github.com/codiume/orbit/blob/main/packages/astro-purgecss/package.json#L33-L35

Thanks for reporting this @Jisu-Woniu

I don't seem to be able to reproduce this issue, I have installed a plain new Astro project and added astro-purgecss without any issues, I also have configured my typescript rules to strict.

You have to use astro.config.ts instead of .mjs, since typescript won't check .mjs files.

@Jisu-Woniu hmm, by default astro generates the config file as mjs I wonder what are the use cases for that file to be in TS ? I'm gonna look more into this, as you see per typescript docs

These are fallbacks for older versions of typescript.

After reading this https://github.com/microsoft/TypeScript/issues/52363
I think I understand why it's not working properly, basically typescript is looking at exports' and ignoring main', types' etc.. and when it looks for types for index.mjs' it expects to find an index.d.mts' file instead of an index.d.ts' file which is supposed to be for common js files. thus throwing the error:
There are types at 'astro-purgecss/dist/index.d.ts', but this result could not be resolved when respecting package.json "exports"
first time hearing about this index.d.mts file extension but I guess I need to specify now in exports the types key.

I use astro.config.ts because Astro claims TypeScript config is supported, and it can help me identify error in my configuration sometimes.
https://docs.astro.build/en/guides/typescript/


[Docs] read/write_resource when no add_resource - behaviour?

The documentation says that World::read_resource and World::write_resource panic if "it's already borrowed". But it is unclear what happens if the resource is not added with add_resource beforehand. Does it panic in this case?

Yes, I'd expect it to throw an "resource not found" error


🐛 [BUG]:  class 'nodrag' in NodeToolbar does not work

Is there an existing issue for this?

[X] I have searched the existing issues and this is a new bug.

Current Behavior
Using the class 'nodrag' in NodeToolbar does not work.
`

input:

            <input type="number" class="nodrag" value="10"></input>

            <NodeToolbar position={Position.Right} isVisible={data.toolbarVisible}>
                <input type="number" class="nodrag"></input>
            </NodeToolbar>

`
Expected Behavior
Work like you're in custom Node
Steps To Reproduce
No response
Relevant log output
No response
Anything else?
https://github.com/bcakmakoglu/vue-flow/assets/38812759/85035fb6-0766-45cf-9f91-2fcc22486d24

What would you expect nodrag to do here?🤔
Nodrag is supposed to prevent a node from being dragged if a specific element is targeted but a Toolbar doesn’t trigger drag anyway so this “bug” report doesn’t really make sense to me here.

@284668461 ping - can you respond to me previous question? :)

Closing due to a lack of information here, please re-open if necessary.


Update prepare-for-upload-vhd-image.md

The PowerShell code for BCDEdit hangs somewhere near the "exit" statement.  I changed and tested all the commands for BCDEdit.

@sandude-ms : Thanks for your contribution! The author(s) have been notified to review your proposed change. @glimoli

@sandude-ms Hi Robert, sorry but what exactly the change you are proposing here? Within a powershell session, we are invoking a CMD session and then running the BCDedit commands and once we are done, we are exit the embedded CMD session so what is the ask/change you are proposing?

Hello Gabriela,
I have been configuring VMs for uploading to Azure all week.  I follow that article, which is very helpful by the way.  Another change I would propose is whether or not it applies to Windows 10 Multi-Session (EVD).
The change was brought about, because twice when I tried copying, pasting, then running that code, it would hang at some point and I had to forcefully end it.  I had some help from a peer, because I wanted to set up a loop to apply all the settings from an array.  But he mentioned it would be much simpler to just put the "& " in front of each command.  I did that, I tested it multiple times, and it works perfect.
Oh, another idea I had.  We should put all the code into a single script, perhaps at the end of the article.   Here is an example that includes all except Diskpart:
& SFC /scannow
Set-ItemProperty -Path HKLM:\SYSTEM\CurrentControlSet\Control\TimeZoneInformation -Name RealTimeIsUniversal -Value 1 -Type DWord -Force
Set-Service -Name w32time -StartupType Automatic
Set-ItemProperty -Path 'HKLM:\SYSTEM\CurrentControlSet\Control\Session Manager\Environment' -Name TEMP -Value "%SystemRoot%\TEMP" -Type ExpandString -Force
Set-ItemProperty -Path 'HKLM:\SYSTEM\CurrentControlSet\Control\Session Manager\Environment' -Name TMP -Value "%SystemRoot%\TEMP" -Type ExpandString -Force
Get-Service -Name BFE, Dhcp, Dnscache, IKEEXT, iphlpsvc, nsi, mpssvc, RemoteRegistry |
Where-Object StartType -ne Automatic |
Set-Service -StartupType Automatic
Get-Service -Name Netlogon, Netman, TermService |
Where-Object StartType -ne Manual |
Set-Service -StartupType Manual
Set-ItemProperty -Path 'HKLM:\SYSTEM\CurrentControlSet\Control\Terminal Server' -Name fDenyTSConnections -Value 0 -Type DWord -Force
Set-ItemProperty -Path 'HKLM:\SOFTWARE\Policies\Microsoft\Windows NT\Terminal Services' -Name fDenyTSConnections -Value 0 -Type DWord -Force
Set-ItemProperty -Path 'HKLM:\SYSTEM\CurrentControlSet\Control\Terminal Server\Winstations\RDP-Tcp' -Name PortNumber -Value 3389 -Type DWord -Force
Set-ItemProperty -Path 'HKLM:\SYSTEM\CurrentControlSet\Control\Terminal Server\Winstations\RDP-Tcp' -Name LanAdapter -Value 0 -Type DWord -Force
Set-ItemProperty -Path 'HKLM:\SYSTEM\CurrentControlSet\Control\Terminal Server\WinStations\RDP-Tcp' -Name UserAuthentication -Value 1 -Type DWord -Force
Set-ItemProperty -Path 'HKLM:\SYSTEM\CurrentControlSet\Control\Terminal Server\WinStations\RDP-Tcp' -Name SecurityLayer -Value 1 -Type DWord -Force
Set-ItemProperty -Path 'HKLM:\SYSTEM\CurrentControlSet\Control\Terminal Server\WinStations\RDP-Tcp' -Name fAllowSecProtocolNegotiation -Value 1 -Type DWord -Force
Set-ItemProperty -Path 'HKLM:\SOFTWARE\Policies\Microsoft\Windows NT\Terminal Services' -Name KeepAliveEnable -Value 1  -Type DWord -Force
Set-ItemProperty -Path 'HKLM:\SOFTWARE\Policies\Microsoft\Windows NT\Terminal Services' -Name KeepAliveInterval -Value 1  -Type DWord -Force
Set-ItemProperty -Path 'HKLM:\SYSTEM\CurrentControlSet\Control\Terminal Server\Winstations\RDP-Tcp' -Name KeepAliveTimeout -Value 1 -Type DWord -Force
Set-ItemProperty -Path 'HKLM:\SOFTWARE\Policies\Microsoft\Windows NT\Terminal Services' -Name fDisableAutoReconnect -Value 0 -Type DWord -Force
Set-ItemProperty -Path 'HKLM:\SYSTEM\CurrentControlSet\Control\Terminal Server\Winstations\RDP-Tcp' -Name fInheritReconnectSame -Value 1 -Type DWord -Force
Set-ItemProperty -Path 'HKLM:\SYSTEM\CurrentControlSet\Control\Terminal Server\Winstations\RDP-Tcp' -Name fReconnectSame -Value 0 -Type DWord -Force
Set-ItemProperty -Path 'HKLM:\SYSTEM\CurrentControlSet\Control\Terminal Server\Winstations\RDP-Tcp' -Name MaxInstanceCount -Value<PHONE_NUMBER> -Type DWord -Force
if ((Get-Item -Path 'HKLM:\SYSTEM\CurrentControlSet\Control\Terminal Server\WinStations\RDP-Tcp').Property -contains 'SSLCertificateSHA1Hash')
{
Remove-ItemProperty -Path 'HKLM:\SYSTEM\CurrentControlSet\Control\Terminal Server\WinStations\RDP-Tcp' -Name SSLCertificateSHA1Hash -Force
}
Set-NetFirewallProfile -Profile Domain, Public, Private -Enabled True
Enable-PSRemoting -Force
Set-NetFirewallRule -Name WINRM-HTTP-In-TCP, WINRM-HTTP-In-TCP-PUBLIC -Enabled True
Set-NetFirewallRule -Group '@FirewallAPI.dll,-28752' -Enabled True
Set-NetFirewallRule -Name FPS-ICMP4-ERQ-In -Enabled True
New-NetFirewallRule -DisplayName AzurePlatform -Direction Inbound -RemoteAddress <IP_ADDRESS> -Profile Any -Action Allow -EdgeTraversalPolicy Allow
New-NetFirewallRule -DisplayName AzurePlatform -Direction Outbound -RemoteAddress <IP_ADDRESS> -Profile Any -Action Allow
& bcdedit.exe /set "{bootmgr}" integrityservices enable
& bcdedit.exe /set "{default}" device partition=C:
& bcdedit.exe /set "{default}" integrityservices enable
& bcdedit.exe /set "{default}" recoveryenabled Off
& bcdedit.exe /set "{default}" osdevice partition=C:
& bcdedit.exe /set "{default}" bootstatuspolicy IgnoreAllFailures
#Enable Serial Console Feature
& bcdedit.exe /set "{bootmgr}" displaybootmenu yes
& bcdedit.exe /set "{bootmgr}" timeout 5
& bcdedit.exe /set "{bootmgr}" bootems yes
& bcdedit.exe /ems "{current}" ON
& bcdedit.exe /emssettings EMSPORT:1 EMSBAUDRATE:115200
exit
Set up the guest OS to collect a kernel dump on an OS crash event
Set-ItemProperty -Path 'HKLM:\SYSTEM\CurrentControlSet\Control\CrashControl' -Name CrashDumpEnabled -Type DWord -Force -Value 2
Set-ItemProperty -Path 'HKLM:\SYSTEM\CurrentControlSet\Control\CrashControl' -Name DumpFile -Type ExpandString -Force -Value "%SystemRoot%\MEMORY.DMP"
Set-ItemProperty -Path 'HKLM:\SYSTEM\CurrentControlSet\Control\CrashControl' -Name NMICrashDump -Type DWord -Force -Value 1
Set up the guest OS to collect user mode dumps on a service crash event
$key = 'HKLM:\SOFTWARE\Microsoft\Windows\Windows Error Reporting\LocalDumps'
if ((Test-Path -Path $key) -eq $false) {(New-Item -Path 'HKLM:\SOFTWARE\Microsoft\Windows\Windows Error Reporting' -Name LocalDumps)}
New-ItemProperty -Path $key -Name DumpFolder -Type ExpandString -Force -Value 'C:\CrashDumps'
New-ItemProperty -Path $key -Name CrashCount -Type DWord -Force -Value 10
New-ItemProperty -Path $key -Name DumpType -Type DWord -Force -Value 2
Set-Service -Name WerSvc -StartupType Manual
& echo y | chkdsk /f
I can figure out and send you code for Diskpart if you're interested.
Thanks,
Robert M. Smith

From: Gabriela Limoli @.>
Sent: Thursday, June 3, 2021 3:56 PM
To: MicrosoftDocs/azure-docs @.>
Cc: Robert Smith @.>; Mention @.>
Subject: Re: [MicrosoftDocs/azure-docs] Update prepare-for-upload-vhd-image.md (#76373)
@sandude-mshttps://github.com/sandude-ms Hi Robert, sorry but what exactly the change you are proposing here? Within a powershell session, we are invoking a CMD session and then running the BCDedit commands and once we are done, we are exit the embedded CMD session so what is the ask/change you are proposing?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/MicrosoftDocs/azure-docs/pull/76373#issuecomment-854137774, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ALHP7JU457CZAZUZACWH4B3TQ7NABANCNFSM46BMGGMQ.

Here is the Diskpart code.  I tested and it works perfect.
$DiskpartText = @'
san policy=onlineall
'@
Add-Content -Path "$env:TEMP\DiskPartText.txt" -Value $DiskpartText
& Diskpart /s "$env:TEMP\DiskPartText.txt"
If (Test-Path "$env:TEMP\DiskPartText.txt"){
Remove-Item -Path "$env:TEMP\DiskPartText.txt"
}

From: Robert Smith @.>
Sent: Friday, June 4, 2021 2:39 PM
To: MicrosoftDocs/azure-docs @.>; MicrosoftDocs/azure-docs @.>
Cc: Mention @.>
Subject: Re: [MicrosoftDocs/azure-docs] Update prepare-for-upload-vhd-image.md (#76373)
Hello Gabriela,
I have been configuring VMs for uploading to Azure all week.  I follow that article, which is very helpful by the way.  Another change I would propose is whether or not it applies to Windows 10 Multi-Session (EVD).
The change was brought about, because twice when I tried copying, pasting, then running that code, it would hang at some point and I had to forcefully end it.  I had some help from a peer, because I wanted to set up a loop to apply all the settings from an array.  But he mentioned it would be much simpler to just put the "& " in front of each command.  I did that, I tested it multiple times, and it works perfect.
Oh, another idea I had.  We should put all the code into a single script, perhaps at the end of the article.   Here is an example that includes all except Diskpart:
& SFC /scannow
Set-ItemProperty -Path HKLM:\SYSTEM\CurrentControlSet\Control\TimeZoneInformation -Name RealTimeIsUniversal -Value 1 -Type DWord -Force
Set-Service -Name w32time -StartupType Automatic
Set-ItemProperty -Path 'HKLM:\SYSTEM\CurrentControlSet\Control\Session Manager\Environment' -Name TEMP -Value "%SystemRoot%\TEMP" -Type ExpandString -Force
Set-ItemProperty -Path 'HKLM:\SYSTEM\CurrentControlSet\Control\Session Manager\Environment' -Name TMP -Value "%SystemRoot%\TEMP" -Type ExpandString -Force
Get-Service -Name BFE, Dhcp, Dnscache, IKEEXT, iphlpsvc, nsi, mpssvc, RemoteRegistry |
Where-Object StartType -ne Automatic |
Set-Service -StartupType Automatic
Get-Service -Name Netlogon, Netman, TermService |
Where-Object StartType -ne Manual |
Set-Service -StartupType Manual
Set-ItemProperty -Path 'HKLM:\SYSTEM\CurrentControlSet\Control\Terminal Server' -Name fDenyTSConnections -Value 0 -Type DWord -Force
Set-ItemProperty -Path 'HKLM:\SOFTWARE\Policies\Microsoft\Windows NT\Terminal Services' -Name fDenyTSConnections -Value 0 -Type DWord -Force
Set-ItemProperty -Path 'HKLM:\SYSTEM\CurrentControlSet\Control\Terminal Server\Winstations\RDP-Tcp' -Name PortNumber -Value 3389 -Type DWord -Force
Set-ItemProperty -Path 'HKLM:\SYSTEM\CurrentControlSet\Control\Terminal Server\Winstations\RDP-Tcp' -Name LanAdapter -Value 0 -Type DWord -Force
Set-ItemProperty -Path 'HKLM:\SYSTEM\CurrentControlSet\Control\Terminal Server\WinStations\RDP-Tcp' -Name UserAuthentication -Value 1 -Type DWord -Force
Set-ItemProperty -Path 'HKLM:\SYSTEM\CurrentControlSet\Control\Terminal Server\WinStations\RDP-Tcp' -Name SecurityLayer -Value 1 -Type DWord -Force
Set-ItemProperty -Path 'HKLM:\SYSTEM\CurrentControlSet\Control\Terminal Server\WinStations\RDP-Tcp' -Name fAllowSecProtocolNegotiation -Value 1 -Type DWord -Force
Set-ItemProperty -Path 'HKLM:\SOFTWARE\Policies\Microsoft\Windows NT\Terminal Services' -Name KeepAliveEnable -Value 1  -Type DWord -Force
Set-ItemProperty -Path 'HKLM:\SOFTWARE\Policies\Microsoft\Windows NT\Terminal Services' -Name KeepAliveInterval -Value 1  -Type DWord -Force
Set-ItemProperty -Path 'HKLM:\SYSTEM\CurrentControlSet\Control\Terminal Server\Winstations\RDP-Tcp' -Name KeepAliveTimeout -Value 1 -Type DWord -Force
Set-ItemProperty -Path 'HKLM:\SOFTWARE\Policies\Microsoft\Windows NT\Terminal Services' -Name fDisableAutoReconnect -Value 0 -Type DWord -Force
Set-ItemProperty -Path 'HKLM:\SYSTEM\CurrentControlSet\Control\Terminal Server\Winstations\RDP-Tcp' -Name fInheritReconnectSame -Value 1 -Type DWord -Force
Set-ItemProperty -Path 'HKLM:\SYSTEM\CurrentControlSet\Control\Terminal Server\Winstations\RDP-Tcp' -Name fReconnectSame -Value 0 -Type DWord -Force
Set-ItemProperty -Path 'HKLM:\SYSTEM\CurrentControlSet\Control\Terminal Server\Winstations\RDP-Tcp' -Name MaxInstanceCount -Value<PHONE_NUMBER> -Type DWord -Force
if ((Get-Item -Path 'HKLM:\SYSTEM\CurrentControlSet\Control\Terminal Server\WinStations\RDP-Tcp').Property -contains 'SSLCertificateSHA1Hash')
{
Remove-ItemProperty -Path 'HKLM:\SYSTEM\CurrentControlSet\Control\Terminal Server\WinStations\RDP-Tcp' -Name SSLCertificateSHA1Hash -Force
}
Set-NetFirewallProfile -Profile Domain, Public, Private -Enabled True
Enable-PSRemoting -Force
Set-NetFirewallRule -Name WINRM-HTTP-In-TCP, WINRM-HTTP-In-TCP-PUBLIC -Enabled True
Set-NetFirewallRule -Group '@FirewallAPI.dll,-28752' -Enabled True
Set-NetFirewallRule -Name FPS-ICMP4-ERQ-In -Enabled True
New-NetFirewallRule -DisplayName AzurePlatform -Direction Inbound -RemoteAddress <IP_ADDRESS> -Profile Any -Action Allow -EdgeTraversalPolicy Allow
New-NetFirewallRule -DisplayName AzurePlatform -Direction Outbound -RemoteAddress <IP_ADDRESS> -Profile Any -Action Allow
& bcdedit.exe /set "{bootmgr}" integrityservices enable
& bcdedit.exe /set "{default}" device partition=C:
& bcdedit.exe /set "{default}" integrityservices enable
& bcdedit.exe /set "{default}" recoveryenabled Off
& bcdedit.exe /set "{default}" osdevice partition=C:
& bcdedit.exe /set "{default}" bootstatuspolicy IgnoreAllFailures
#Enable Serial Console Feature
& bcdedit.exe /set "{bootmgr}" displaybootmenu yes
& bcdedit.exe /set "{bootmgr}" timeout 5
& bcdedit.exe /set "{bootmgr}" bootems yes
& bcdedit.exe /ems "{current}" ON
& bcdedit.exe /emssettings EMSPORT:1 EMSBAUDRATE:115200
exit
Set up the guest OS to collect a kernel dump on an OS crash event
Set-ItemProperty -Path 'HKLM:\SYSTEM\CurrentControlSet\Control\CrashControl' -Name CrashDumpEnabled -Type DWord -Force -Value 2
Set-ItemProperty -Path 'HKLM:\SYSTEM\CurrentControlSet\Control\CrashControl' -Name DumpFile -Type ExpandString -Force -Value "%SystemRoot%\MEMORY.DMP"
Set-ItemProperty -Path 'HKLM:\SYSTEM\CurrentControlSet\Control\CrashControl' -Name NMICrashDump -Type DWord -Force -Value 1
Set up the guest OS to collect user mode dumps on a service crash event
$key = 'HKLM:\SOFTWARE\Microsoft\Windows\Windows Error Reporting\LocalDumps'
if ((Test-Path -Path $key) -eq $false) {(New-Item -Path 'HKLM:\SOFTWARE\Microsoft\Windows\Windows Error Reporting' -Name LocalDumps)}
New-ItemProperty -Path $key -Name DumpFolder -Type ExpandString -Force -Value 'C:\CrashDumps'
New-ItemProperty -Path $key -Name CrashCount -Type DWord -Force -Value 10
New-ItemProperty -Path $key -Name DumpType -Type DWord -Force -Value 2
Set-Service -Name WerSvc -StartupType Manual
& echo y | chkdsk /f
I can figure out and send you code for Diskpart if you're interested.
Thanks,
Robert M. Smith

From: Gabriela Limoli @.>
Sent: Thursday, June 3, 2021 3:56 PM
To: MicrosoftDocs/azure-docs @.>
Cc: Robert Smith @.>; Mention @.>
Subject: Re: [MicrosoftDocs/azure-docs] Update prepare-for-upload-vhd-image.md (#76373)
@sandude-mshttps://github.com/sandude-ms Hi Robert, sorry but what exactly the change you are proposing here? Within a powershell session, we are invoking a CMD session and then running the BCDedit commands and once we are done, we are exit the embedded CMD session so what is the ask/change you are proposing?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/MicrosoftDocs/azure-docs/pull/76373#issuecomment-854137774, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ALHP7JU457CZAZUZACWH4B3TQ7NABANCNFSM46BMGGMQ.

Hi @sandude-ms - We aren't able to add a script at this time, so we'll close this PR. Thanks for your interest in contributing to the documentation.
cc @glimoli


Removed most sprintf and ignore sprintf warnings in bind code

When compiling on the mac I am getting a bunch of compiler errors for sprintf.  I converted all of them to snprintf, except for the bind code that we copied over.  For that I am ignoring the errors.
@bneradt I changed the way I am filling the resize()  in TransactionData::initialize_default_sensitive_field.  Hopefully this won't cause any issues. My worry is that we are writing 9 bytes including the null into data.  From my understanding it is not guaranteed to have space for that.

[approve ci clang-format]

@bneradt I changed the way I am filling the resize() in TransactionData::initialize_default_sensitive_field. Hopefully this won't cause any issues. My worry is that we are writing 9 bytes including the null into data. From my understanding it is not guaranteed to have space for that.

In case it's helpful or interesting, the original was safe. Since C++11, std::string is guaranteed to have a null terminator. To demonstrate this, let's think of the default string being a size of 8 characters instead of 128k to make it easier to think through. Then the function becomes:
  // 128 KB is the maximum size supported for all headers, so this size should
  // be plenty large for our needs.
  //constexpr size_t default_field_size = 128 * 1024;
  constexpr size_t default_field_size = 8;  // <--- Changed to 8.
  default_sensitive_field_value.resize(default_field_size);

  char *field_buffer = default_sensitive_field_value.data();
  for (auto i = 0u; i < default_field_size; i += 8) {
    sprintf(field_buffer, "%07x ", i / 8);
    field_buffer += 8;
  }

Thus the internal buffer size has to be at least 9 (8 for the resize value for the number of characters, and then one more value for the null terminator). The for loop will execute exactly once and write 8 characters (7 0 values and a space " " character) and then sprintf will null terminate the string at default_sensitive_field_value[8] which is already guaranteed to be null. Thus there is no buffer overrun in the original and its behavior should be correct.
That said, I prefer the ostringstream version I suggest in my comment over the sprintf.
Again, thank you for the PR. I'm happier with the update to the function.

[approve ci]

[approve ci]

A lot of nice changes.  Thanks!


Fix duplicate RCTBridge.h in IOS, RN 0.40+

sorry for being perfectionist, but there are more imports that should be replaced (they're not causing issues, but ... for completeness).
Basically all imports referenced in this commit:
https://github.com/mauron85/react-native-background-geolocation/commit/9d83368039aed26f88d812247b43c10af3ea0904
should be changed that <> imports are before "".

Should be fixed in alpha.7.


Validate docs dir before writing custom js

If the user puts an invalid docs dir, we fail with a generic error, we should raise a more specific one.
https://github.com/rtfd/readthedocs.org/blob/44951fbf8fe1fe12fa9f99f3075f87bd77188525/readthedocs/doc_builder/backends/mkdocs.py#L175-L176

@stsewd Should the validation be here?
https://github.com/rtfd/readthedocs.org/blob/44951fbf8fe1fe12fa9f99f3075f87bd77188525/readthedocs/doc_builder/base.py#L84
or should we put it be before
https://github.com/rtfd/readthedocs.org/blob/44951fbf8fe1fe12fa9f99f3075f87bd77188525/readthedocs/doc_builder/backends/mkdocs.py#L175-L176


Choose the unlifting mode based on the protocol version

Default will change in V6.

Needs a test, actually.

Not benchmarked? You're being overly confident in both GHC's optimization abilities and my prediction abilities!

 If it's a recent one I think it should be fine.

I didn't know there was a difference.

The scripts that get run come from the branch that is being benchmarked, which can make that matter.


Styling Help for MoneyRequestHeader

Thanks @grgia!

Making this PR as a record of what you added so I can learn a bit.

@techievivek Please copy/paste the Reviewer Checklist from here into a new comment on this PR and complete it. If you have the K2 extension, you can simply click: [this button]

🚀 Deployed to staging by https://github.com/yuwenmemon in version: 1.3.11-0 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅

🚀 Deployed to production by https://github.com/roryabraham in version: 1.3.12-0 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅


Buzz phone not connecting calls completely

Buzz does incomplete first ring and the call is dropped. Resulting in a missed call in our company logs. This issue will happen several times in a row.

If you enable developer mode in Chrome Extension section then you'll get an Inspect views option and if you share the logs from the offscreen.html maybe I can assist...
I would assume it has something to do with the connectivity between the client browser and Asterisk - are they on the same LAN or going over the Internet?

closting due to no response


is there's a way to implement mongodb "DBrefs" with this library?

hey there, is there's a way to implement mongodb "DBrefs" with this library? thanks a lot :)

i have the same question.

You need to import
use MongoDB\BSON\ObjectId;
After all you, need to create DBRef struct, like mongodb doc
public function store(Request $request)     {         $data = $request->all();         if($data['id_role']){             $role = [                 '$ref' => 'role',                 '$id' => new ObjectId($dados['id_role'])             ];             unset($data['id_role']);             $data['role'] = $role;         }         return User::create($data);     }
Example of my controller, but you will need to load the DBRefs manually on show.
`public function show($id)
{
$user = User::find($id);
if($user){
$user->role = Role::find($user->role['$id']);
return $user;
}
    return response('{"message":"NOT FOUND"}', 404);
}`


Trigger order status is not Correct in V2

In this Function: https://www.bitget.com/api-doc/contract/plan/orders-plan-history
Trigger order status
If not specified, all states will be queried
executed: the order triggered
fail_trigger: Failed to trigger
cancelled: Cancelled
But your api: Bitget.Net.Enums.V2.TriggerOrderStatus in Status including: Live, Executing, Executed

I've added the status filter with correct values in the latest version

How about Response Parameters:
Order status
live: new order
executed: the order triggered
fail_execute: Failed to trigger
cancelled: Cancelled
In this Function: https://www.bitget.com/api-doc/contract/plan/orders-plan-history
Trigger order status
If not specified, all states will be queried
executed: the order triggered
fail_trigger: Failed to trigger
cancelled: Cancelled
But your api: Bitget.Net.Enums.V2.TriggerOrderStatus returrn Status (Response) including: Live, Executing, Executed

Ah yeah I missed that, these values are valid but the fail_execute and cancelled values were missing. I've added them in latest version

I just sent a donation. Thank you. Hopefully we will win big this Uptrend season. I will continue to donate to you to the best of my ability


Updates the package to etcd 2.2.0

etcd 2.2.0 docs apparently don't have png files to copy, so I also removed that line from the Makefile

Thanks! You are now a contributor!


SD TTNN: TtUpsampleNearest2d

Implement subgraph TtUpsampleNearest2d and make two tests: one for 256x256 image size and one for 512x512 image size.
Have one test file named something like test_upsample_nearest_2d.py and inside it two tests test_upsample_nearest_2d_256x256 and test_upsample_nearest_2d_512x512. Tests should be parametrized with following input shapes:

[x] Shape 1:  256x256

[x] input case 1: [2, 1280, 4, 4]
[x] input case 2: [2, 1280, 8, 8]
[x] input case 3: [2, 640, 16, 16]

[x] Shape 2:  512x512

[x] input case 1: [2, 1280, 8, 8]
[x] input case 2: [2, 1280, 16, 16]
[x] input case 3: [2, 640, 32, 32]

While utilizing the repeat_interleave operation from the ttnn library, I observed that the scaling is limited to dimension 0, irrespective of the specified dim parameter in the function call.
The problem can be replicated using the following code:
def test_repeat_interleave(device):
    tensor_tensor_2d = torch.rand(32,64)
    torch_result = torch.repeat_interleave(tensor_tensor_2d, 2, dim=1)
    input_tensor = ttnn.to_layout(ttnn.to_device(ttnn.from_torch(tensor_tensor_2d, dtype=ttnn.bfloat16), device=device), layout=ttnn.TILE_LAYOUT)
    output = ttnn.repeat_interleave(input_tensor, 2, dim=1)
    output = ttnn.to_torch(ttnn.from_device(ttnn.to_layout(output, layout=ttnn.ROW_MAJOR_LAYOUT)))
    assert_with_pcc(torch_result, output, 0.9999)

@boris-drazic while utilizing the repeat_interleave operation from ttnn library, I observed that the upsampling is limited to dimension 0, irrespective of the specified dim parameter in the function call.
The problem can be replicated using the following code:
def test_repeat_interleave(device):
    tensor_tensor_2d = torch.rand(32,64)
    torch_result = torch.repeat_interleave(tensor_tensor_2d, 2, dim=1)
    input_tensor = ttnn.to_layout(ttnn.to_device(ttnn.from_torch(tensor_tensor_2d, dtype=ttnn.bfloat16), device=device), layout=ttnn.TILE_LAYOUT)
    output = ttnn.repeat_interleave(input_tensor, 2, dim=1)
    output = ttnn.to_torch(ttnn.from_device(ttnn.to_layout(output, layout=ttnn.ROW_MAJOR_LAYOUT)))
    assert_with_pcc(torch_result, output, 0.9999)

This issue has been resolved in the latest main,
All 6 tests are passing , commit link

PR for upsample_nearest2d implementation in function_stable_diffusion model - #4870

PR merged. Hence Closing the ticket.


Fix documentation source code issues

Just some typos
Btw, is the develop branch the right one? The contributing guidelines say yes but looking at the commits this doesn't seem as true...

Thanks for the fix :+1:

The contributing guidelines say yes but looking at the commits this doesn't seem as true...

develop is currently behind master because I had to make some quick fixes after releasing moor 3.0 and sqlparser 0.8.0. In general it's the right branch.


Make the bookmarklet location permanent

Why don't you just fix the links on index html, this works:
javascript:(function(){ cb = function(){ create_spritz(); }; var script=document.createElement('SCRIPT');script.src='https://raw.githubusercontent.com/Miserlou/Glance-Bookmarklet/master/spritz.js?callback=cb'; script.onload=cb; document.body.appendChild(script);})();

If only that were true @Miserlou . If only that were true.


JS files broken links

There are two JavaScript files in _layouts/default.html with broken links.

Fixed in #354


Timed out while waiting for the machine to boot.

How to reproduce the error:
> cd ~/geerlingguy-drupal-vm-ac56269/ (straight out of the zip file)
> vagrant up
Bringing machine 'drupalvm' up with 'virtualbox' provider...
==> drupalvm: Cloning VM...
==> drupalvm: Matching MAC address for NAT networking...
==> drupalvm: Checking if box 'geerlingguy/ubuntu1604' is up to date...
==> drupalvm: Setting the name of the VM: drupalvm.dev
==> drupalvm: Clearing any previously set network interfaces...
==> drupalvm: Preparing network interfaces based on configuration...
    drupalvm: Adapter 1: nat
    drupalvm: Adapter 2: hostonly
==> drupalvm: Forwarding ports...
    drupalvm: 22 (guest) => 2222 (host) (adapter 1)
==> drupalvm: Running 'pre-boot' VM customizations...
==> drupalvm: Booting VM...
==> drupalvm: Waiting for machine to boot. This may take a few minutes...
    drupalvm: SSH address: <IP_ADDRESS>:2222
    drupalvm: SSH username: vagrant
    drupalvm: SSH auth method: private key

after a few minutes of intense suspence
Timed out while waiting for the machine to boot. This means that
Vagrant was unable to communicate with the guest machine within
the configured ("config.vm.boot_timeout" value) time period.

If you look above, you should be able to see the error(s) that
Vagrant had when attempting to connect to the machine. These errors
are usually good hints as to what may be wrong.

If you're using a custom box, make sure that networking is properly
working and you're able to connect to the machine. It is a common
problem that networking isn't setup properly in these boxes.
Verify that authentication configurations are also setup properly,
as well.

If the box appears to be booting properly, you may want to increase
the timeout ("config.vm.boot_timeout") value.

I showed the GUI of the guest OS via Virtualbox and it is stuck on a black screen stating:
[    6.569034] piix:smbus 0000:00:0
7.0: SMbus base address uninitialized - upgrade bios or use force_addr=0xaddr mac os virtualbox
[      6.878323] intel_rapl: no valid rapl domains found in package 0

If I press ESC to display the detailed boot log I can see a new process starting:
A start job is running for Raise network interfaces. (screenshot)
It lasts about 5 minutes and I'm guessing that's longer than vagrant's login timeout. If I start the VM manually from within VirtualBox and wait, after about 5 minutes I'm asked username and password.
I tried unchecking Enable Nested Paging and changing the virtual chipset in VirtualBox's settings, as suggested somewhere else, but none of that helped.
The problem doesn't show up when using a recent xenial64 box:
> vagrant init ubuntu/xenial64
geerlingguy/ubuntu1204, geerlingguy/ubuntu1404 and geerlingguy/centos7 don't rise this error, but they all get stuck on the login screen waiting for username and password. Go figure.
Here it is the output of vagrant up --debug.
My setup:

Mac OS X Sierra  10.12.1
Vagrant 1.8.6
Ansible <IP_ADDRESS>
VirtualBox 5.0.28

@dimatteomaurizio - Thank you SO much for the detailed error report. You have no idea how many times I have to help someone starting from an issue summary of "something doesn't work" (and that's literally it).
In this case, I'm 99% sure the issue is VirtualBox 5.0.28—I just updated the boxes to use 5.1.8 guest additions, so they will likely not work correctly with 5.0.x anymore. If you aren't able to upgrade VirtualBox to the latest version, you can install the previous Vagrant box version of geerlingguy/ubuntu1604 and it should hopefully work correctly.

I also experienced this issue while running VirtualBox 5.0.26 after doing a vagrant box update from geerlingguy/ubuntu1604 1.0.4 to 1.0.5.
I've updated VirtualBox to 5.1.8 which has fixed the initial SMbus error above, but I'm still getting the second error regarding intel_rapl:
[    7.259594] intel_rapl: no valid rapl domains found in package 0
As per above, if you press escape it removes the error, displays the detailed boot log and starts the
A start job is running for Raise network interfaces process which runs for about 5 minutes.
I tried removing 1.0.5 (vagrant destroy then vagrant box remove geerlingguy/ubuntu1604 --box-version 1.0.5) and 1.0.4 works fine.
My setup:

Mac OS X 10.11.6 El Capitan
Ansible <IP_ADDRESS>
Vagrant 1.8.6
VirtualBox 5.1.8

In this case, I'm 99% sure the issue is VirtualBox 5.0.28—I just updated the boxes to use 5.1.8 guest additions, so they will likely not work correctly with 5.0.x anymore. If you aren't able to upgrade VirtualBox to the latest version, you can install the previous Vagrant box version of geerlingguy/ubuntu1604 and it should hopefully work correctly.

I guess I put too much faith in auto-updates, I thought 5.0.28 was the latest.
Indeed updating to 5.1.8, deleting and re-downloading the latest box (just in case) solved the issue.
Thanks a lot :)

Hmm... @keithcrooks due to caching/cloning, it could have still been using the same instance that was broken after you upgraded VirtualBox—can you try redownloading the box again like @dimatteomaurizio did?

@geerlingguy You're right. My bad. I've tried updating the box to 1.0.5 again after updating VB to 5.1.8 and removing the cached versions of 1.0.5 and it works!
Thanks 👍

Awesome! I'm going to close out this issue then. I can specify a required Vagrant and Ansible version, but I can't seem to do the same (forcibly) for VirtualBox... so it looks like I'll be seeing a bunch of these issues posted over the next month or two :D

Thank you!  This was so helpful.  Exactly my problem.  Worked right away, once I upgraded VirtualBox.

Hi all,
I am new to vagrant.
I create a new machine using vagrant ini hashicorp/precise64.
When making vagrant up command i got timeout error. Is there other thing i must do please?
I am using the last 1.9.5 version on windows with oracle virtual box.

@koolstens - That sounds like a Vagrant issue, not something that would be relevant to the Drupal VM issue queue. That issue can happen because of a large number of different issues. I'd suggest searching the Vagrant issue queue for your error and filing an issue there if you find it to be a bug: https://github.com/mitchellh/vagrant

My OS is Windows Ubuntu 16.04 and I have installed Oracle VM VirtualBox Manager 5.1.26 and vagrant 1.8.5
Even I am getting this with 'vagrant up':
Timed out while waiting for the machine to boot. This means that Vagrant was unable to communicate with the guest machine within the configured ("config.vm.boot_timeout" value) time period.
If you look above, you should be able to see the error(s) that Vagrant had when attempting to connect to the machine. These errors are usually good hints as to what may be wrong.
If you're using a custom box, make sure that networking is properly working and you're able to connect to the machine. It is a common problem that networking isn't setup properly in these boxes. Verify that authentication configurations are also setup properly, as well.
If the box appears to be booting properly, you may want to increase the timeout ("config.vm.boot_timeout") value.
I even tried adding the following to the Vagrantfile
config.vm.boot_timeout = 600
But still getting the same timeout error. Please suggest.

Hi guys, I have exactly the same issue,  I am using the latest version for Ubuntu 16.04 64bits:
"Version 5.2.8 r121009)
"Timed out while waiting for the machine to boot".

I figured the best solution is starting the Oracle VM from the GUI interface and then when you use 'vagrant ssh' on the terminal, it will directly login to the VM.

Hi guys, I have the same issue. I am using Windows 7, VirtualBox 5.2.8, Git-2.16.2, Vagrant 2.0.3.
This error could be reproduced following these steps:
1.- git clone https://github.com/adafruit/esp8266-micropython-vagrant.git
2.- cd esp8266-micropython-vagrant
3.- vagrant up
** message **
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Box 'ubuntu/trusty64' could not be found. Attempting to find and in              stall...
default: Box Provider: virtualbox
default: Box Version: >= 0
==> default: Loading metadata for box 'ubuntu/trusty64'
default: URL: https://vagrantcloud.com/ubuntu/trusty64
==> default: Adding box 'ubuntu/trusty64' (v20180308.0.0) for provider: virtualb              ox
default: Downloading: https://vagrantcloud.com/ubuntu/boxes/trusty64/version              s/20180308.0.0/providers/virtualbox.box
default: Download redirected to host: cloud-images.ubuntu.com
default:
==> default: Successfully added box 'ubuntu/trusty64' (v20180308.0.0) for 'virtu              albox'!
==> default: Importing base box 'ubuntu/trusty64'...
==> default: Matching MAC address for NAT networking...
==> default: Checking if box 'ubuntu/trusty64' is up to date...
==> default: Setting the name of the VM: esp8266-micropython-vagrant_default_152<PHONE_NUMBER>_81314
==> default: Clearing any previously set forwarded ports...
Vagrant is currently configured to create VirtualBox synced folders with
the SharedFoldersEnableSymlinksCreate option enabled. If the Vagrant
guest is not trusted, you may want to disable this option. For more
information on this option, please refer to the VirtualBox manual:
https://www.virtualbox.org/manual/ch04.html#sharedfolders
This option can be disabled globally with an environment variable:
VAGRANT_DISABLE_VBOXSYMLINKCREATE=1
or on a per folder basis within the Vagrantfile:
config.vm.synced_folder '/host/path', '/guest/path', SharedFoldersEnableSymlin              ksCreate: false
==> default: Clearing any previously set network interfaces...
==> default: Preparing network interfaces based on configuration...
default: Adapter 1: nat
==> default: Forwarding ports...
default: 22 (guest) => 2222 (host) (adapter 1)
==> default: Running 'pre-boot' VM customizations...
==> default: Booting VM...
==> default: Waiting for machine to boot. This may take a few minutes...
default: SSH address: <IP_ADDRESS>:2222
default: SSH username: vagrant
default: SSH auth method: private key
Timed out while waiting for the machine to boot. This means that
Vagrant was unable to communicate with the guest machine within
the configured ("config.vm.boot_timeout" value) time period.
If you look above, you should be able to see the error(s) that
Vagrant had when attempting to connect to the machine. These errors
are usually good hints as to what may be wrong.
If you're using a custom box, make sure that networking is properly
working and you're able to connect to the machine. It is a common
problem that networking isn't setup properly in these boxes.
Verify that authentication configurations are also setup properly,
as well.
If the box appears to be booting properly, you may want to increase
the timeout ("config.vm.boot_timeout") value.
** end of message **
Would you please give me a hand?
Thanks.

I had a similar issue on Windows 8.1 64bits. I installed virtualbox version 5.1,  vagrant version 2.1.2 with ubuntu/ precise64. What solved my problem was "vagrant destroy" command after I had done a lot of things ranging from going into BIOS ---
to enable VIRTUALIZATION TECHNOLOGY ---- to tweaking vagrantfile. I don't know how that could solve the problem but it sure did.

Facing the same issue in my Ubuntu-16.04.4 Environment.

Just Check does your base environment VM/Machine even supporting virtualization...
I installed the GUI version on Centos and when tried opening the console of the VM through VirtualBox, I could see the unsupported virtualization message.
Fixing the virtualization in my environment fixed the issue. Maybe it can help someone, hence posting here.

I have similar issue.  I just downloaded new vagrant version (from 2.1.2 to 2.2.6 and upgraded virtualbox (from 5.2 to 6.0)
I run into Timed out while waiting for the machine to boot at SSH author method: private key...etc...
Any help would really appreciate it.+


[CI] Various CI improvements

Adjust ci to use new webhook project label method

I believe this fixes: https://github.com/rancher/helm-project-operator/issues/62

Add dapper back to improve local mac dev (can be removed fully later)
Add support for simultaneous cross-arch cross-os bin builds
Uses goreleaser for binary releases on tags
removes use of unauthorized GHA
Adds the helm-project-operator chart as a tag release artifact.

For a preview of how this improvs tags/releases see:

Current: https://github.com/rancher/helm-project-operator/releases/tag/v0.3.0
After: https://github.com/mallardduck/helm-project-operator/releases/tag/v0.3.1-rc.1

Created a new release from this: https://github.com/rancher/helm-project-operator/releases/tag/v0.3.1


Fix some ie8 issues

The homepage buttons have lost their protuding-button styling that they inherited from the browser (see below). I thought that probably didn't matter enough to reintroduce?

Thanks - no the styling is not a problem.

Thanks for spotting this!


Add helm resource-policy annotation on PVC

Following up on #385
We could argue it is expected of Helm to purge objects based on a change of values, we could ensure that a PersistentVolumeClaim would never be removed automatically.

Right, #266, not #355 ... Tells about:

This happened after I upgraded my release to the latest version and set existingClaim to my existing claim "traefik"

AFAIU, there was an existing deployment managed by Helm, with persistence enabled. PV was lost by adding an existingClaim to the values file, updating that deployment.
The helm update command then compared existing objects, created by the previous helm install, to those that should be applied, resulting in the existing PVC destruction, since no longer managed by Helm.
I don't think any documentation would suggest to do this. It's most likely a misunderstanding.
Could have happened with pretty much any chart, definitely not a bug.
Annotating the PVC could serve as a safety net against pebkac.


fix(cd): helm pvc clean up after pr close

currently when PR is closed the pvc are not removed.

Thanks for the PR!
Deployments, as required, will be available below:

Frontend
Backend

Please create PRs in draft mode.  Mark as ready to enable:

Analysis Workflow

After merge, new images are deployed in:

Merge Workflow

@DerekRoberts we need a release after this is merged, lot of PVC are hanging around due to this bug .

@mishraomp Thanks and go for it! :)


feat: support bytes[] as the contract call args

Motivation

This PR adds logic to handle bytes[] contract call args
Test on Base Sepolia
https://sepolia.basescan.org/tx/0x61bca9ade0522b70524ebe3e9b3064572cd22e05cdd67d650ad8657dc0f8a1f4
Solution

Open questions

🟡 Heimdall Review Status

Requirement
Status
More Info

Reviews

🟡
0/1

Denominator calculation

Show calculation

1 if user is bot
0

1 if user is external
0

From .codeflow.yml

1

Additional review requirements

Show calculation

Max
0

0

From CODEOWNERS

0

Global minimum
0

Max

1

1

1 if commit is unverified
0

Sum
1

Review Error for GeekArthur @ 2024-09-27 14:42:02 UTC
User failed mfa authentication, see go/mfa-help


Small improvements

I added a missing option: "responsive", and some minor improvements (generics wildcards, to make it easier to extend panels for ICharts). Also, some small fixes were made to the pom file fo the project (missing version tags).

Thanks a lot for your support :+1: , i'll create a new release and push it into maven central within the next few days.

Thanks for merging, I would highly recommend you to change the current versioning scheme for the lib, I believe it is following wicket's release versions but in cases like this (e.g. hotfixes) versions won't match, I recommend using a separate version scheme for the lib (but it is only a recommendation :)

Thanks for your suggestion and sorry for answering so late. You're right. The only advantage of the current versioning scheme is, that you can simply use some ${wicket.version} property in your pom.xml to have the lib in sync with your version of wicket core. I'll discuss that and post conclusion here.


Can you please bring back the backup button for the config(s)?

Hi,
after the update to v4 I discovered that there is no longer a backup button (save as) for the config.
Could you please bring this button back?
regards,

Done in 4.2.0

i've installed 4.3.0 and backup button is not present (do not come back in 4.2.0 for me)

Maybe you need to clear the  browsercache?
Which browser on which system? SSL enabled?

Yes, you are right!
Thanks and sorry..
Inviato da iPhone

Il giorno 5 mag 2019, alle ore 22:11, palasinio<EMAIL_ADDRESS>ha scritto:
Maybe you need to clear the browsercache?
Which browser on which system? SSL enabled?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.


Missing CONTRIBUTING.md File in Repository

The repository currently lacks a CONTRIBUTING.md file, which is an important resource for guiding potential contributors on how to engage with the project effectively. A CONTRIBUTING.md file outlines the contribution guidelines, coding standards, and procedures for submitting pull requests, thus streamlining the contribution process and ensuring consistency across contributions.
I'm a GSSOC'24 contributor
@Dev-tanay   Please give it a gssoc'24 label and assign this work to me .

I would like to work on this issue. Please assign it to me.


[BUG] Fields limited to 500 characters

Describe the bug
Importing an XLSX file with greater than 500 characters in a fields produces an error -- I have some large boards that have Reference field with MANY locations.
EDIT:
I tried editing the contents of this reference field after import, and realized that it's not the import API function, but just that the field itself is limited to 500 characters.
---end-of-edit---
Steps to Reproduce
Steps to reproduce the behavior:

Create a BOM data file with a >500 characters in any field (I ran into this on "Reference" column)
Go to part/<id>/bom-upload
Click on 'Upload BOM File'
Browse to file, Open
Submit, match fields
Submit
See error "Ensure this field has no more than 500 characters."

Screenshots

Deployment Method

[X ] Docker
[ ] Bare Metal

Version Information
0.6.3

Not a bug, this is a known (and as seen in the screenshot validated) limitation to keep imports reasonably fast.
We are always open for PRs that enable longer imports while keeping response times under 30secs per API call.

Agreed, this field is simply limited to 500 characters

@4jag this is a separate issue to the "500 character limit" issue.
If you are importing a BOM file with 1500 parts, that is a lot of data for the backend to process and serve back to the client via the API.
Can you please share some information on the error you are seeing now? Is the system reporting a timeout to the server?

I was just responding to @matmair 's comment that it's a "known limitation to keep imports reasonably fast. ... while keeping response times under 30secs per API call." I find when the import takes longer than 30 seconds, I get a "Bad gateway" error from NGINX, and I wasn't sure if that's an artificial timeout or something that could be lengthened to accommodate larger data imports.
So it sounded to me like maybe you want to limit the import data size in order to avoid the timeout from NGINX. If that's the case, and if it's possible to increase the timeout above 30 seconds, then ...  On the other hand, allowing larger field sizes but having to break up imports into several files would be preferred over limiting the fields sizes, because limiting the field size can forces bad data (such as in my case).

@4jag the 30 seconds comes from nginx which used the default of apache2. Setting any higher value will lead to security warnings with a lot of enterprise cmdbs or outright alerts by monitoring tools.
This is why django and most libraries come with settings to be well under this limit. That is where the 500 characters come from - it is a battle-tested default.
I strongly suggest to not make users change their webserver settings and instead fix the performance issue at hand - If possible.

Hi, I have this exact same issue.
I generated a BOM where I split long list of references:

However, when I have two lines with the same IPN, the second line is ignored and is not imported:

What would be the workaround ? Generate multiple csv files and import them one by one ?

Hi, I have this exact same issue.

@fjullien can you clarify the issue you are having? This discussion has covered a few different topics already

As you can see on the screenshots, I have 123 capacitor PRT00020.
Because the reference "C53, C56..., C258" is too long, I split this in two lines in my csv file.
When I import this csv file, I can see only 80 PRT00020 (the ones from the first line).
It should be 123 because there is 80 + 43 PRT00020.
I may have miss something above....

The reference field is limited to 500 characters. Splitting the row in the CSV into 2 rows will not change that. Also there is currently no way for InvenTree to detect that you did the split so you will lose everything in the second line/it will not be imported.

Agreed, this field is simply limited to 500 characters

@4jag have you found a workaround for this limitation ?
I think I'll have to move to another solution to generate my BOM.


Home Screen Rebranding

@maxkpower which UI will be applied
there many examples in the UI
https://www.figma.com/file/3oGLWzSH0oJljo4RETZtur/Superhero-Wallet-UI-(✔Updated)?type=design&node-id=28812-168359&mode=design&t=cdHzXTrqta1yc4jD-0


properly handle passthrough and non passthrough on same gateway port

fixes https://github.com/istio/istio/issues/11786 where a gateway with some passthrough and some non passthrough
servers on same 443 port was failing. The logic for building the gateway listeners was very old (before the full filter
chain matching stuff was introduced in Envoy). The old logic (predating Istio 1.0) assumed that a listener could either
have a terminating HTTPS server or a sni passthrough server, but not both, causing the bug described in
https://github.com/istio/istio/issues/11786 .
This code fixes that logic. Along the way, I spotted several related issues - listeners can have filter chains,
where one chain could be using HTTP connection manager with TLS termination, while the other chain could
be doing a simple SNI passthrough using tcp proxy filter. Pilot's plugin code relies on the listener level
protocol to determine what to do (insert JWT filter, or mixer http filter), without looking at individual filter
chains. This will turn out to be incorrect in a scenario where the above said gateway has both HTTPS termination
and passthrough. I have fixed this logic in mixer filter, authN and the envoy filter CRD logic accordingly.
Signed-off-by: Shriram Rajagopalan<EMAIL_ADDRESS>

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: rshriram
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

pilot/pkg/networking/OWNERS [rshriram]
tests/e2e/tests/pilot/OWNERS [rshriram]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

cc @duderino .. this is a latent bug since 1.0 or earlier..

@rshriram: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/e2e-dashboard.sh
c89fa740965c11beab5858497b86b782e6448720
link
/test e2e-dashboard

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@rshriram: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/e2e-dashboard.sh
c89fa740965c11beab5858497b86b782e6448720
link
/test e2e-dashboard

prow/e2e-simpleTests-cni.sh
c89fa740965c11beab5858497b86b782e6448720
link
/test e2e-simpleTests-cni

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

cc @kyessenov / @yangminzhu / @diemtvu for their respective plugins
cc @hzxuzhonghu (supersedes #12060 )

@rshriram: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/e2e-dashboard.sh
c89fa740965c11beab5858497b86b782e6448720
link
/test e2e-dashboard

prow/e2e-simpleTests-cni.sh
c89fa740965c11beab5858497b86b782e6448720
link
/test e2e-simpleTests-cni

prow/istio-unit-tests.sh
c89fa740965c11beab5858497b86b782e6448720
link
/test istio-unit-tests

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@rshriram: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/e2e-dashboard.sh
c89fa740965c11beab5858497b86b782e6448720
link
/test e2e-dashboard

prow/e2e-simpleTests-cni.sh
c89fa740965c11beab5858497b86b782e6448720
link
/test e2e-simpleTests-cni

prow/istio-unit-tests.sh
c89fa740965c11beab5858497b86b782e6448720
link
/test istio-unit-tests

prow/istio-integ-k8s-tests.sh
c89fa740965c11beab5858497b86b782e6448720
link
/test istio-integ-k8s-tests

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@rshriram: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/e2e-dashboard.sh
c89fa740965c11beab5858497b86b782e6448720
link
/test e2e-dashboard

prow/e2e-simpleTests-cni.sh
c89fa740965c11beab5858497b86b782e6448720
link
/test e2e-simpleTests-cni

prow/istio-unit-tests.sh
c89fa740965c11beab5858497b86b782e6448720
link
/test istio-unit-tests

prow/istio-integ-k8s-tests.sh
c89fa740965c11beab5858497b86b782e6448720
link
/test istio-integ-k8s-tests

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
c89fa740965c11beab5858497b86b782e6448720
link
/test istio-pilot-e2e-envoyv2-v1alpha3

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@rshriram: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/e2e-dashboard.sh
c89fa740965c11beab5858497b86b782e6448720
link
/test e2e-dashboard

prow/e2e-simpleTests-cni.sh
c89fa740965c11beab5858497b86b782e6448720
link
/test e2e-simpleTests-cni

prow/istio-unit-tests.sh
c89fa740965c11beab5858497b86b782e6448720
link
/test istio-unit-tests

prow/istio-integ-k8s-tests.sh
c89fa740965c11beab5858497b86b782e6448720
link
/test istio-integ-k8s-tests

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
c89fa740965c11beab5858497b86b782e6448720
link
/test istio-pilot-e2e-envoyv2-v1alpha3

prow/e2e-mixer-no_auth.sh
c89fa740965c11beab5858497b86b782e6448720
link
/test e2e-mixer-no_auth

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@rshriram: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/e2e-dashboard.sh
c89fa740965c11beab5858497b86b782e6448720
link
/test e2e-dashboard

prow/e2e-simpleTests-cni.sh
c89fa740965c11beab5858497b86b782e6448720
link
/test e2e-simpleTests-cni

prow/istio-unit-tests.sh
c89fa740965c11beab5858497b86b782e6448720
link
/test istio-unit-tests

prow/istio-integ-k8s-tests.sh
c89fa740965c11beab5858497b86b782e6448720
link
/test istio-integ-k8s-tests

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
c89fa740965c11beab5858497b86b782e6448720
link
/test istio-pilot-e2e-envoyv2-v1alpha3

prow/e2e-mixer-no_auth.sh
c89fa740965c11beab5858497b86b782e6448720
link
/test e2e-mixer-no_auth

prow/istio-pilot-multicluster-e2e.sh
c89fa740965c11beab5858497b86b782e6448720
link
/test istio-pilot-multicluster-e2e

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@rshriram: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/e2e-dashboard.sh
c89fa740965c11beab5858497b86b782e6448720
link
/test e2e-dashboard

prow/e2e-simpleTests-cni.sh
c89fa740965c11beab5858497b86b782e6448720
link
/test e2e-simpleTests-cni

prow/istio-unit-tests.sh
c89fa740965c11beab5858497b86b782e6448720
link
/test istio-unit-tests

prow/istio-integ-k8s-tests.sh
c89fa740965c11beab5858497b86b782e6448720
link
/test istio-integ-k8s-tests

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
c89fa740965c11beab5858497b86b782e6448720
link
/test istio-pilot-e2e-envoyv2-v1alpha3

prow/e2e-mixer-no_auth.sh
c89fa740965c11beab5858497b86b782e6448720
link
/test e2e-mixer-no_auth

prow/istio-pilot-multicluster-e2e.sh
c89fa740965c11beab5858497b86b782e6448720
link
/test istio-pilot-multicluster-e2e

prow/e2e_pilotv2_auth_sds.sh
c89fa740965c11beab5858497b86b782e6448720
link
/test istio_auth_sds_e2e

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@rshriram: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-integ-k8s-tests.sh
c89fa740965c11beab5858497b86b782e6448720
link
/test istio-integ-k8s-tests

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
c89fa740965c11beab5858497b86b782e6448720
link
/test istio-pilot-e2e-envoyv2-v1alpha3

prow/e2e-mixer-no_auth.sh
c89fa740965c11beab5858497b86b782e6448720
link
/test e2e-mixer-no_auth

prow/istio-pilot-multicluster-e2e.sh
c89fa740965c11beab5858497b86b782e6448720
link
/test istio-pilot-multicluster-e2e

prow/e2e_pilotv2_auth_sds.sh
c89fa740965c11beab5858497b86b782e6448720
link
/test istio_auth_sds_e2e

prow/e2e-simpleTests-cni.sh
696fdcdb1dc0bb3f4c7b0561346cb3aea2c0bd6d
link
/test e2e-simpleTests-cni

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@rshriram: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
c89fa740965c11beab5858497b86b782e6448720
link
/test istio-pilot-e2e-envoyv2-v1alpha3

prow/e2e-mixer-no_auth.sh
c89fa740965c11beab5858497b86b782e6448720
link
/test e2e-mixer-no_auth

prow/istio-pilot-multicluster-e2e.sh
c89fa740965c11beab5858497b86b782e6448720
link
/test istio-pilot-multicluster-e2e

prow/e2e_pilotv2_auth_sds.sh
c89fa740965c11beab5858497b86b782e6448720
link
/test istio_auth_sds_e2e

prow/e2e-simpleTests-cni.sh
696fdcdb1dc0bb3f4c7b0561346cb3aea2c0bd6d
link
/test e2e-simpleTests-cni

prow/istio-integ-k8s-tests.sh
696fdcdb1dc0bb3f4c7b0561346cb3aea2c0bd6d
link
/test istio-integ-k8s-tests

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@rshriram: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/e2e-mixer-no_auth.sh
c89fa740965c11beab5858497b86b782e6448720
link
/test e2e-mixer-no_auth

prow/istio-pilot-multicluster-e2e.sh
c89fa740965c11beab5858497b86b782e6448720
link
/test istio-pilot-multicluster-e2e

prow/e2e_pilotv2_auth_sds.sh
c89fa740965c11beab5858497b86b782e6448720
link
/test istio_auth_sds_e2e

prow/e2e-simpleTests-cni.sh
696fdcdb1dc0bb3f4c7b0561346cb3aea2c0bd6d
link
/test e2e-simpleTests-cni

prow/istio-integ-k8s-tests.sh
696fdcdb1dc0bb3f4c7b0561346cb3aea2c0bd6d
link
/test istio-integ-k8s-tests

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
696fdcdb1dc0bb3f4c7b0561346cb3aea2c0bd6d
link
/test istio-pilot-e2e-envoyv2-v1alpha3

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@rshriram: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/e2e-mixer-no_auth.sh
c89fa740965c11beab5858497b86b782e6448720
link
/test e2e-mixer-no_auth

prow/istio-pilot-multicluster-e2e.sh
c89fa740965c11beab5858497b86b782e6448720
link
/test istio-pilot-multicluster-e2e

prow/e2e-simpleTests-cni.sh
696fdcdb1dc0bb3f4c7b0561346cb3aea2c0bd6d
link
/test e2e-simpleTests-cni

prow/istio-integ-k8s-tests.sh
696fdcdb1dc0bb3f4c7b0561346cb3aea2c0bd6d
link
/test istio-integ-k8s-tests

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
696fdcdb1dc0bb3f4c7b0561346cb3aea2c0bd6d
link
/test istio-pilot-e2e-envoyv2-v1alpha3

prow/e2e_pilotv2_auth_sds.sh
696fdcdb1dc0bb3f4c7b0561346cb3aea2c0bd6d
link
/test istio_auth_sds_e2e

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@rshriram: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/e2e-simpleTests-cni.sh
696fdcdb1dc0bb3f4c7b0561346cb3aea2c0bd6d
link
/test e2e-simpleTests-cni

prow/istio-integ-k8s-tests.sh
696fdcdb1dc0bb3f4c7b0561346cb3aea2c0bd6d
link
/test istio-integ-k8s-tests

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
696fdcdb1dc0bb3f4c7b0561346cb3aea2c0bd6d
link
/test istio-pilot-e2e-envoyv2-v1alpha3

prow/e2e_pilotv2_auth_sds.sh
696fdcdb1dc0bb3f4c7b0561346cb3aea2c0bd6d
link
/test istio_auth_sds_e2e

prow/istio-pilot-multicluster-e2e.sh
696fdcdb1dc0bb3f4c7b0561346cb3aea2c0bd6d
link
/test istio-pilot-multicluster-e2e

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: rshriram
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

pilot/OWNERS [rshriram]
pkg/OWNERS [rshriram]
tests/OWNERS [rshriram]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@rshriram: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-integ-k8s-tests.sh
696fdcdb1dc0bb3f4c7b0561346cb3aea2c0bd6d
link
/test istio-integ-k8s-tests

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
696fdcdb1dc0bb3f4c7b0561346cb3aea2c0bd6d
link
/test istio-pilot-e2e-envoyv2-v1alpha3

prow/e2e_pilotv2_auth_sds.sh
696fdcdb1dc0bb3f4c7b0561346cb3aea2c0bd6d
link
/test istio_auth_sds_e2e

prow/istio-pilot-multicluster-e2e.sh
696fdcdb1dc0bb3f4c7b0561346cb3aea2c0bd6d
link
/test istio-pilot-multicluster-e2e

prow/e2e-simpleTests-cni.sh
342a4f5ef0cedc3d8c30260089070e3740790102
link
/test e2e-simpleTests-cni

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@rshriram: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
696fdcdb1dc0bb3f4c7b0561346cb3aea2c0bd6d
link
/test istio-pilot-e2e-envoyv2-v1alpha3

prow/e2e_pilotv2_auth_sds.sh
696fdcdb1dc0bb3f4c7b0561346cb3aea2c0bd6d
link
/test istio_auth_sds_e2e

prow/istio-pilot-multicluster-e2e.sh
696fdcdb1dc0bb3f4c7b0561346cb3aea2c0bd6d
link
/test istio-pilot-multicluster-e2e

prow/e2e-simpleTests-cni.sh
342a4f5ef0cedc3d8c30260089070e3740790102
link
/test e2e-simpleTests-cni

prow/istio-integ-k8s-tests.sh
342a4f5ef0cedc3d8c30260089070e3740790102
link
/test istio-integ-k8s-tests

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@rshriram: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/e2e_pilotv2_auth_sds.sh
696fdcdb1dc0bb3f4c7b0561346cb3aea2c0bd6d
link
/test istio_auth_sds_e2e

prow/istio-pilot-multicluster-e2e.sh
696fdcdb1dc0bb3f4c7b0561346cb3aea2c0bd6d
link
/test istio-pilot-multicluster-e2e

prow/e2e-simpleTests-cni.sh
342a4f5ef0cedc3d8c30260089070e3740790102
link
/test e2e-simpleTests-cni

prow/istio-integ-k8s-tests.sh
342a4f5ef0cedc3d8c30260089070e3740790102
link
/test istio-integ-k8s-tests

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
342a4f5ef0cedc3d8c30260089070e3740790102
link
/test istio-pilot-e2e-envoyv2-v1alpha3

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@rshriram: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-multicluster-e2e.sh
696fdcdb1dc0bb3f4c7b0561346cb3aea2c0bd6d
link
/test istio-pilot-multicluster-e2e

prow/e2e-simpleTests-cni.sh
342a4f5ef0cedc3d8c30260089070e3740790102
link
/test e2e-simpleTests-cni

prow/istio-integ-k8s-tests.sh
342a4f5ef0cedc3d8c30260089070e3740790102
link
/test istio-integ-k8s-tests

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
342a4f5ef0cedc3d8c30260089070e3740790102
link
/test istio-pilot-e2e-envoyv2-v1alpha3

prow/e2e_pilotv2_auth_sds.sh
342a4f5ef0cedc3d8c30260089070e3740790102
link
/test istio_auth_sds_e2e

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@rshriram: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/e2e-simpleTests-cni.sh
342a4f5ef0cedc3d8c30260089070e3740790102
link
/test e2e-simpleTests-cni

prow/istio-integ-k8s-tests.sh
342a4f5ef0cedc3d8c30260089070e3740790102
link
/test istio-integ-k8s-tests

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
342a4f5ef0cedc3d8c30260089070e3740790102
link
/test istio-pilot-e2e-envoyv2-v1alpha3

prow/e2e_pilotv2_auth_sds.sh
342a4f5ef0cedc3d8c30260089070e3740790102
link
/test istio_auth_sds_e2e

prow/istio-pilot-multicluster-e2e.sh
342a4f5ef0cedc3d8c30260089070e3740790102
link
/test istio-pilot-multicluster-e2e

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@rshriram: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-integ-k8s-tests.sh
342a4f5ef0cedc3d8c30260089070e3740790102
link
/test istio-integ-k8s-tests

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
342a4f5ef0cedc3d8c30260089070e3740790102
link
/test istio-pilot-e2e-envoyv2-v1alpha3

prow/e2e_pilotv2_auth_sds.sh
342a4f5ef0cedc3d8c30260089070e3740790102
link
/test istio_auth_sds_e2e

prow/istio-pilot-multicluster-e2e.sh
342a4f5ef0cedc3d8c30260089070e3740790102
link
/test istio-pilot-multicluster-e2e

prow/e2e-simpleTests-cni.sh
8f94e3e73162e6b93f6909e7724c78948138735f
link
/test e2e-simpleTests-cni

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@rshriram: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-integ-k8s-tests.sh
342a4f5ef0cedc3d8c30260089070e3740790102
link
/test istio-integ-k8s-tests

prow/e2e_pilotv2_auth_sds.sh
342a4f5ef0cedc3d8c30260089070e3740790102
link
/test istio_auth_sds_e2e

prow/istio-pilot-multicluster-e2e.sh
342a4f5ef0cedc3d8c30260089070e3740790102
link
/test istio-pilot-multicluster-e2e

prow/e2e-simpleTests-cni.sh
8f94e3e73162e6b93f6909e7724c78948138735f
link
/test e2e-simpleTests-cni

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
8f94e3e73162e6b93f6909e7724c78948138735f
link
/test istio-pilot-e2e-envoyv2-v1alpha3

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@rshriram: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-integ-k8s-tests.sh
342a4f5ef0cedc3d8c30260089070e3740790102
link
/test istio-integ-k8s-tests

prow/e2e_pilotv2_auth_sds.sh
342a4f5ef0cedc3d8c30260089070e3740790102
link
/test istio_auth_sds_e2e

prow/istio-pilot-multicluster-e2e.sh
342a4f5ef0cedc3d8c30260089070e3740790102
link
/test istio-pilot-multicluster-e2e

prow/e2e-simpleTests-cni.sh
8f94e3e73162e6b93f6909e7724c78948138735f
link
/test e2e-simpleTests-cni

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
8f94e3e73162e6b93f6909e7724c78948138735f
link
/test istio-pilot-e2e-envoyv2-v1alpha3

prow/istio-unit-tests.sh
6e7be813d3752de3f15d255997062970e9e57053
link
/test istio-unit-tests

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@rshriram: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-integ-k8s-tests.sh
342a4f5ef0cedc3d8c30260089070e3740790102
link
/test istio-integ-k8s-tests

prow/e2e_pilotv2_auth_sds.sh
342a4f5ef0cedc3d8c30260089070e3740790102
link
/test istio_auth_sds_e2e

prow/istio-pilot-multicluster-e2e.sh
342a4f5ef0cedc3d8c30260089070e3740790102
link
/test istio-pilot-multicluster-e2e

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
8f94e3e73162e6b93f6909e7724c78948138735f
link
/test istio-pilot-e2e-envoyv2-v1alpha3

prow/istio-unit-tests.sh
6e7be813d3752de3f15d255997062970e9e57053
link
/test istio-unit-tests

prow/e2e-simpleTests-cni.sh
6e7be813d3752de3f15d255997062970e9e57053
link
/test e2e-simpleTests-cni

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@rshriram: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/e2e_pilotv2_auth_sds.sh
342a4f5ef0cedc3d8c30260089070e3740790102
link
/test istio_auth_sds_e2e

prow/istio-pilot-multicluster-e2e.sh
342a4f5ef0cedc3d8c30260089070e3740790102
link
/test istio-pilot-multicluster-e2e

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
8f94e3e73162e6b93f6909e7724c78948138735f
link
/test istio-pilot-e2e-envoyv2-v1alpha3

prow/istio-unit-tests.sh
6e7be813d3752de3f15d255997062970e9e57053
link
/test istio-unit-tests

prow/e2e-simpleTests-cni.sh
6e7be813d3752de3f15d255997062970e9e57053
link
/test e2e-simpleTests-cni

prow/istio-integ-k8s-tests.sh
6e7be813d3752de3f15d255997062970e9e57053
link
/test istio-integ-k8s-tests

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@rshriram: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-multicluster-e2e.sh
342a4f5ef0cedc3d8c30260089070e3740790102
link
/test istio-pilot-multicluster-e2e

prow/istio-unit-tests.sh
6e7be813d3752de3f15d255997062970e9e57053
link
/test istio-unit-tests

prow/e2e-simpleTests-cni.sh
6e7be813d3752de3f15d255997062970e9e57053
link
/test e2e-simpleTests-cni

prow/istio-integ-k8s-tests.sh
6e7be813d3752de3f15d255997062970e9e57053
link
/test istio-integ-k8s-tests

prow/e2e_pilotv2_auth_sds.sh
6e7be813d3752de3f15d255997062970e9e57053
link
/test istio_auth_sds_e2e

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@rshriram: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-unit-tests.sh
6e7be813d3752de3f15d255997062970e9e57053
link
/test istio-unit-tests

prow/e2e-simpleTests-cni.sh
6e7be813d3752de3f15d255997062970e9e57053
link
/test e2e-simpleTests-cni

prow/istio-integ-k8s-tests.sh
6e7be813d3752de3f15d255997062970e9e57053
link
/test istio-integ-k8s-tests

prow/e2e_pilotv2_auth_sds.sh
6e7be813d3752de3f15d255997062970e9e57053
link
/test istio_auth_sds_e2e

prow/istio-pilot-multicluster-e2e.sh
6e7be813d3752de3f15d255997062970e9e57053
link
/test istio-pilot-multicluster-e2e

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/test istio-unit-tests

@rshriram: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-integ-k8s-tests.sh
6e7be813d3752de3f15d255997062970e9e57053
link
/test istio-integ-k8s-tests

prow/e2e_pilotv2_auth_sds.sh
6e7be813d3752de3f15d255997062970e9e57053
link
/test istio_auth_sds_e2e

prow/istio-pilot-multicluster-e2e.sh
6e7be813d3752de3f15d255997062970e9e57053
link
/test istio-pilot-multicluster-e2e

prow/e2e-simpleTests-cni.sh
ae3ac69b07866a235b6f1673b756c5ade375e562
link
/test e2e-simpleTests-cni

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@rshriram: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/e2e_pilotv2_auth_sds.sh
6e7be813d3752de3f15d255997062970e9e57053
link
/test istio_auth_sds_e2e

prow/istio-pilot-multicluster-e2e.sh
6e7be813d3752de3f15d255997062970e9e57053
link
/test istio-pilot-multicluster-e2e

prow/e2e-simpleTests-cni.sh
ae3ac69b07866a235b6f1673b756c5ade375e562
link
/test e2e-simpleTests-cni

prow/istio-integ-k8s-tests.sh
ae3ac69b07866a235b6f1673b756c5ade375e562
link
/test istio-integ-k8s-tests

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/lgtm
/approve

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: GregHanson, rshriram
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

pilot/OWNERS [GregHanson,rshriram]
pkg/OWNERS [rshriram]
tests/OWNERS [rshriram]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

Why was this merged without answering reviewer questions?
@duderino
On Wed, Feb 27, 2019, 10:25 AM Shriram Rajagopalan<EMAIL_ADDRESS>wrote:

Merged #12071 https://github.com/istio/istio/pull/12071 into
release-1.1.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/istio/istio/pull/12071#event-2168844269, or mute the
thread
https://github.com/notifications/unsubscribe-auth/AJGIxuqFTEgChqvRUR8WJKBbJkDA-K_Jks5vRs2bgaJpZM4bSy7T
.

@rshriram what's the burning urgency with this one?
Why can't @kyessenov 's and @hzxuzhonghu 's comments be addressed?


Ubuntu 24.04 LTS failed to install

NGINX of Ubuntu 24.04 and open-appsec:
The installation failed:
open-appsec for NGINX, Kong and APISIX Installer v1.2245.1
For release notes and known limitations check:
https://docs.openappsec.io/release-notes
Searching local NGINX…
nginx version found: 1.24.0-2ubuntu7
Unsupported nginx version: 1.24.0-2ubuntu7. Please see docs.openappsec.io

I have switched to nginx-mainline repository.


Jupyter-multi_outputs can't work at without internet access

I want to use Jupyter-multi_outputs and my environment is no internet access.
I read main.js and I think require.config use "cdnjs.cloudflare.com" directly is reason of that.
But I don't how to fix it.
Would you like to tell how to fix it ?

I fixed it. Please check.


PR: Add support for type linting with MyPy

Description of Changes

[ ] Wrote at least one-line docstrings (for any new functions)
[ ] Added unit test(s) covering the changes (if testable)

[x] Included a screenshot or animation (if affecting the UI, see Licecap)

Add the extension of the PyLS to support type linting

Issue(s) Resolved

Fixes #3045
Affirmation
By submitting this Pull Request or typing my (user)name below,
I affirm the Developer Certificate of Origin
with respect to all commits and content included in this PR,
and understand I am releasing the same under Spyder's MIT (Expat) license.

I certify the above statement is true and correct: Steff456

Nice! I have been thinking about adding type hinting to some of the stuff at work, and this will certainly help.

Is this feature still being worked on? Would really love to see it in my favourite IDE, but it got very quiet around here unfortunately..

This turned out to be harder than we thought. We'll try to resume work on it by the end of the year or probably next year.