Typing has gotten very slow, probably due to large files

Issue Type: Performance Issue
There is a folder with many mp3 audio files. This is probably what is causing the slow down.  But the files are not being changed, not loaded into any editor. They are just sitting there. I can't think why
It's normal (fast) when disabling extensions. It is definitely some extension, but we need some way to quickly identify which one it is. Some performance analysis mode like Atom timecop but for runtime analysis.
VS Code version: Code 1.25.0 (0f080e5267e829de46638128001aeb7ca2d6d50e, 2018-07-05T13:02:28.333Z)
OS version: Darwin x64 17.4.0

System Info

Item
Value

CPUs
Intel(R) Core(TM) i7-7820HQ CPU @ 2.90GHz (8 x 2900)

GPU Status
2d_canvas: enabledflash_3d: enabledflash_stage3d: enabledflash_stage3d_baseline: enabledgpu_compositing: enabledmultiple_raster_threads: enabled_onnative_gpu_memory_buffers: enabledrasterization: enabledvideo_decode: enabledvideo_encode: enabledvpx_decode: enabledwebgl: enabledwebgl2: enabled

Load (avg)
2, 2, 2

Memory (System)
16.00GB (0.71GB free)

Process Argv
/Applications/Visual Studio Code.app/Contents/MacOS/Electron ./

Screen Reader
no

VM
0%

Process Info
CPU %	Mem MB	   PID	Process
   27	   131	  3255	code main
    5	   197	  3260	   gpu-process
    0	   229	  3261	   window (48.csv — textin)
    0	   147	  3262	     extensionHost
    0	    82	  3274	       electron_node htmlServerMain.js
    0	    49	  3278	       electron_node jsonServerMain.js
    0	    49	  3265	     watcherService
    0	    49	  3270	     searchService
    4	    98	  3266	   shared-process
   12	   639	  3419	   window (sites/crucial-systems/templates/Artist.js — matterminds)
    0	   262	  3420	     extensionHost
    0	   131	  3435	       electron_node jsonServerMain.js
    0	    82	  3475	       electron_node eslintServer.js
    0	   246	  3479	       electron_node electronForkStart.js tsserver.js
    0	    66	  3489	         electron_node typingsInstaller.js tsserver.js typesMap.js
    0	    49	  3480	       electron_node tslintServer.js
    0	    49	  3421	     watcherService
    0	    49	  3425	     searchService
    0	    33	  3705	     terminal
    0	     0	  3706	       /bin/zsh -l
   79	    98	  4436	   window (Issue Reporter)
    0	     0	  4437	   /bin/ps -ax -o pid=,ppid=,pcpu=,pmem=,command=

Workspace Info
|  Window (sites/crucial-systems/templates/Artist.js — matterminds)
|  Window (48.csv — textin)
|    Folder (textin): 1 files
|      File types: csv(1)
|      Conf files:
|    Folder (matterminds): 5698 files
|      File types: md(1585) yaml(1268) mp3(642) json(597) jpg(587) js(374)
|                  JPG(222) scss(168) DS_Store(140) png(43)
|      Conf files: package.json(1) tsconfig.json(1) settings.json(1);

Extensions (50)

Extension
Author (truncated)
Version

clipboard-history
Anj
1.0.7

template-generator-vscode
Den
0.4.1

EditorConfig
Edi
0.12.4

vscode-docker
Pet
0.0.27

lorem-ipsum
Tyr
1.2.0

project-manager
ale
8.0.0

vscode-color
ans
0.4.5

django-html
bib
1.2.0

django-snippets
bib
1.1.0

vscode-opennewinstance
chr
0.0.4

npm-intellisense
chr
1.3.0

path-intellisense
chr
1.4.2

bracket-pair-colorizer
Coe
1.0.59

transformer
dak
1.6.0

vscode-eslint
dba
1.4.12

jupyter
don
1.1.4

python-extension-pack
don
1.0.1

xml
Dot
2.3.1

gitlens
eam
8.4.1

tslint
eg2
1.0.33

vscode-npm-script
eg2
0.3.5

prettier-vscode
esb
1.5.0

vscode-open-in-npm
fab
1.0.1

simple-new-file
fay
0.1.0

gc-excelviewer
Gra
2.1.24

vscode-react-typescript
inf
1.0.17

hungry-delete
jas
1.5.0

nbpreviewer
jit
1.0.0

auto-comment-blocks
kev
1.0.1

graphql-for-vscode
kum
1.12.0

node-module-intellisense
lei
1.5.0

restructuredtext
lex
65.0.0

MagicPython
mag
1.0.12

markdown-shortcuts
mdi
0.8.1

rainbow-csv
mec
0.4.2

dotenv
mik
1.0.1

vscode-todo-parser
min
1.9.1

python
ms-
2018.6.0

autodocstring
njp
0.2.1

typescript-hero
rbb
2.3.2

vscode-yaml
red
0.0.13

preview-vscode
sea
1.4.2

git-merger
sha
0.4.1

bash-beautify
sha
0.1.1

vscode-fileutils
sle
2.10.3

vs-code-node-require
tgr
1.2.7

vim
vsc
0.14.2

jinja
who
0.0.8

markdown-pdf
yza
1.2.0

markdown-all-in-one
yzh
1.5.1

(7 theme extensions excluded)

Please use this guide to provide more information: https://github.com/Microsoft/vscode/wiki/Performance-Issues. Thanks.

Thanks that was exactly the type of profiling I was looking for. Will use that the next time.
I did use developer tools for a bit and I did isolate it:
  "vim.statusBarColorControl": false,

Closing, see https://github.com/VSCodeVim/Vim/issues/2166 and https://github.com/VSCodeVim/Vim/issues/2124


Links in diagrams are absolute, but should be relative

In #80, diagram elements were made into links, to make site navigation more smooth and intuitive. However, the links in the diagrams were made absolute. The site generator is set up to make all links on the generated site relative, so it works, regardless of the "context path" it's hosted under.
The diagram links must be made relative, to retain this behaviour.

This issue has been fixed with #86.


Missing releaseConnection?

As described over here: https://github.com/sidorares/node-mysql2
// For pool initialization, see above
pool.getConnection(function(conn) {
   // Do something with the connection
   conn.query(/* ... */);
   // Don't forget to release the connection when finished!
   pool.releaseConnection(conn);
})

It should be possible to also call pool.releaseConnection. Currently it says: 'Property 'releaseConnection' does not exist on type 'Pool'.
I don't know if conn.release() is also fine, or should this example be updated on their page (sidorares)?
Correct me if I'm wrong.
Regards,
Melroy

I had to remove it, several methods are not yet available in this type. I found "releaseConnection" and "prepare" to be missing

You had to remove this? So you'll add them again or :S?

It would be good to update the Docs.

Is it updated yet?


Grammar correction

a => an

[x] I have read freeCodeCamp's contribution guidelines.
[x] My pull request has a descriptive title (not a vague title like Update index.md)
[x] My pull request targets the master branch of freeCodeCamp.
[x] None of my changes are plagiarized from another source without proper attribution.
[x] My article does not contain shortened URLs or affiliate links.

If your pull request closes a GitHub issue, replace the XXXXX below with the issue number.
Closes #XXXXX

Closed and Reopened this PR to attempt to resolve a specific Travis build failure.

Being fixed in #30899


Blocks highlighting in Edge

Repro: Click on a toolbox category, move mouse over flyout blocks - all of them get highlighted

This is a bug in Blockly. @riknoll looking into a possible fix.


commands.NewResourceCommand should retry when k8s api is unavailable

Summary
Resource executions are not retried for tcp timeouts when the K8s API becomes busy from too many workflows running in parallel. I think we can use retry.OnError from k8s.io/client-go/util/retry to avoid the issue.
return retry.OnError(retry.DefaultBackoff, net.IsTimeout, func() (err error) {
   // argo code here
})

https://pkg.go.dev/k8s.io/client-go/util/retry#OnError
https://pkg.go.dev/k8s.io/apimachinery/pkg/util/net#IsTimeout

Diagnostics
👀 Yes! We need all of your diagnostics, please make sure you add it all, otherwise we'll go around in circles asking you for it:
What Kubernetes provider are you using?
EKS 1.19
What version of Argo Workflows are you running?
3.1.2
What executor are you running? Docker/K8SAPI/Kubelet/PNS/Emissary
n/a
Did this work in a previous version? I.e. is it a regression?
No
Logs
task-ssh-config-create-update-5lwhb-1844661117: time="2021-08-02T15:28:39.528Z" level=error msg="executor error: Unable to connect to the server: dial tcp <IP_ADDRESS>:443: i/o timeout
github.com/argoproj/argo-workflows/v3/errors.New
/go/src/github.com/argoproj/argo-workflows/errors/errors.go:49
github.com/argoproj/argo-workflows/v3/workflow/executor.(*WorkflowExecutor).ExecResource
/go/src/github.com/argoproj/argo-workflows/workflow/executor/resource.go:44
github.com/argoproj/argo-workflows/v3/cmd/argoexec/commands.execResource
/go/src/github.com/argoproj/argo-workflows/cmd/argoexec/commands/resource.go:48
github.com/argoproj/argo-workflows/v3/cmd/argoexec/commands.NewResourceCommand.func1
/go/src/github.com/argoproj/argo-workflows/cmd/argoexec/commands/resource.go:25
github.com/spf13/cobra.(*Command).execute
/go/pkg/mod/github.com/spf13/cobra@v1.0.0/command.go:846
github.com/spf13/cobra.(*Command).ExecuteC
/go/pkg/mod/github.com/spf13/cobra@v1.0.0/command.go:950
github.com/spf13/cobra.(*Command).Execute
/go/pkg/mod/github.com/spf13/cobra@v1.0.0/command.go:887
main.main\n\t/go/src/github.com/argoproj/argo-workflows/cmd/argoexec/main.go:15\nruntime.main\n\t/usr/local/go/src/runtime/proc.go:204
runtime.goexit
/usr/local/go/src/runtime/asm_amd64.s:1374"

The workflow template that timed out is creating a simple config map that stores ssh keys
    resource:
      action: apply
      manifest: |
        apiVersion: v1
        kind: ConfigMap
        metadata:
          name: ssh-authorized-keys
          namespace: {{inputs.parameters.envNamespace}}
          labels:
            ssh-user: {{workflow.parameters.sshUserName}}
        data:
          keys: "{{workflow.parameters.sshKeys}}"

Message from the maintainers:
Impacted by this bug? Give it a 👍. We prioritise the issues with the most 👍.

@blkperl yes, the Current code is not retried if it is a transient error.  Would you like to fix this issue? here the code reference
https://github.com/argoproj/argo-workflows/blob/5fde8fa72f2e5b0bcd7cfb048fd1eb9e24b6a950/workflow/executor/resource.go#L34-L45

@sarabala1979 I'm not sure how to convert the exec error from kubectl into a real error that can be interpreted by isTransientNetworkErr

@sarabala1979 I opened a PR but I'm not sure how to test it.


Mcgillby conversion issue

There was a problem in the master branch with some of mcgillby's converted macros. They needed to be assigned --in-x and --in-y values (which is common with MEmu macros). Output looks pretty good now, but needs to be tested.

Just tested NOX TMFarming720. Its better but it is still inverted. Its in the correct area but is mirrored and the inputs are on the left side instead of the right if you understand that? like before it was sideways, now its not sideways and the touchpoints are correct except its hitting unit 4/6 instead of 1/3 and its going for the refresh click on the left instead of the right.. hope that is enough info.. if not ill make a video.

Im getting the hang of navigating this site. Ill test the other versions and see if there are any faults. The speed of the MEmu to NOX conversion TMRefill720 is incredible. It will be a huge improvement from my original NOX script. The Y Values seem correct. The X values are backwards/mirrored.

If I remember correctly I had similar issues with HiroMacro scripts running on a rooted phone.

Got it. I'll take a look when I wake up. Can you make sure you haven't changed any resolution settings on your Memu machine from default?

@curunoir, think this is the issue that you were having a few weeks ago? I think there is an error in my screen flip handling, but the only reason I think this is happening here is because I think @Mcgillby has non-standard Memu resolution settings in some of these macros and since Memu doesn't record the resolution settings inside the file itself it's impossible to differentiate except when the y-axis isn't inverse and shit just breaks all the time.
The better thing to do right now for everyone is to leave resolution at default settings so that macros can be standardized as they've been for months now. Even when I fix this bug in the convertMacros code, it's impossible to know if someone has changed the resolution in their Memu settings without them explicitly saying so, and it fucks everything up.

I agree that a standard resolution should be the base of devs/fixes. His issue reminds me of mine with HiroMacro which was setting origin point on top right corner of my device, so I fixed my issue by converting standard pwnology nox scripts with a little math (720 minus the original x value).
The thing is I'm not sure if this issue is related to speficially HiroMacro on my device. Luckily my device has in theory same resolution as standard Nox and Memu. I don't know if I should open another issue, maybe the question is also if you target mainly emulators script or more wisely every device with macro abilities. (sorry for my english btw)

We should probably open an issue on the convertMacros Github page. I have a
couple ideas of where the issue may be coming from, actually, but if you
could give me a sample line to test with and it's expected output I could
probably accelerate a fix on my end.
On Apr 5, 2017 5:43 AM, "curunoir"<EMAIL_ADDRESS>wrote:

I agree that a standard resolution should be the base of devs/fixes. His
issue reminds me of mine with HiroMacro which was setting origin point on
top right corner of my device, so I fixed my issue by converting standard
pwnology nox scripts with a little math (720 minus the original x value).
The thing is I'm not sure if this issue is related to speficially
HiroMacro on my device. Luckily my device has in theory same resolution as
standard Nox and Memu. I don't know if I should open another issue, maybe
the question is also if you target mainly emulators script or more wisely
every device with macro abilities. (sorry for my english btw)
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
https://github.com/kastyr1984/FFBE-Macros/issues/6#issuecomment-291810063,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ARPJh9-HiAqxPlZJkoavOBI1Pd6x0uiwks5rs2JTgaJpZM4Mzwps
.

I went ahead and set --flip-x to see if that fixes it.

Appears to have been fixed with incorporation of --flip-y into the conversion script command line. Will continue to monitor issue but closing ticket for now.

how do i know when you message. can i get a phone app?

ill go test now, thanks

There should be a notification button on the panel on the right side of the github issue or pull request page that you can use to subscribe to notifications for ones you want to follow.


Generic export model

Make generic import/export registered models.

I believe the model importing is failing due thread safety.
The model registry is resolved just for the first model or fails for the first model and just works for next models:
mlflow.tracking.registry.UnsupportedModelRegistryStoreURIException:  Model registry functionality is unavailable; got unsupported URI 'custom://profile' for model registry data storage. Supported URI schemes are: ['databricks', 'http', 'https', 'postgresql', 'mysql', 'sqlite', 'mssql', '', 'file']

When using --use-threads false everything works well, all models are imported.
I did comment set_experiment (global variable) without affecting results...
But the import is still failing - maybe the model registry LRU cache is not working well with threads.


[CLI] - Add Tailwind option to templates

We added Tailwind support to Static Shock in #145. But this support still requires project setup, which involves downloading the Tailwind binary tool, and creating a few config files.
Update the templates to optionally include as much of the Tailwind configuration as possible.
Can we automatically include the Tailwind CLI tool? Or is it better to force the user to download it? If the user needs to download the Tailwind tool then add an explicit check to the plugin and give the user a helpful error message with instructions where to get it.

Feel free to use my working blog (uses static shock with tailwind) for inspiration:
https://github.com/xdega/liamhockley_blog.github.io/
I always try to keep things as minimal as possible. But there are some customisations here. Alternatively, I would happily volunteer to create a more barebones tailwind project, based on my current setup.

Can we automatically include the Tailwind CLI tool?

@matthew-carroll Given my recent experience, it should be noted that the binary is platform dependent. As such, I think that automatically supplying it should be avoided (or done in such a way that binaries are platform-aware, when executed, and included for Mac, Windows, and Linux)

I went ahead and pumped out a template repo this evening, where I attempt to solve some of the problems mentioned above, and provide a sample TailwindCSS template with everything hooked up (cross-platform supported, pending verification/testing on windows/linux).
https://github.com/xdega/static_shock_tailwind
I adapted the index.html from the most "official" boilerplate I could find: https://github.com/tailwindlabs/tailwindcss-playground
Let me know what you think.
I if this is something you would be interested in implementing, I can prepare a PR (or you can just snag it, whatever works)

One thing I'm wondering, with regard to to downloading the binary, is what the likelihood is that Tailwind will relocate those binaries. If they do, all Static Shock templates that use Tailwind would be broken...

One thing I'm wondering, with regard to to downloading the binary, is what the likelihood is that Tailwind will relocate those binaries. If they do, all Static Shock templates that use Tailwind would be broken...

Yeah. It probably makes sense to deliver a copy of the binaries. In my theme that I threw together, I baked binaries into the project (for each platform). Granted, Git is not the most ideal place to host such files.
That being said, there is probably a reasonable likelihood that the binaries will be rewritten at some point, in Rust.
At which point the binaries that are included should be updated.

Al alternative approach, could be like what Jaspr is doing, where they ask users to install the tailwindcss cli globally, and then the project accesses it with the assumption that it exists in the users PATH.
https://pub.dev/documentation/jaspr_tailwind/latest/

I think both options sound reasonable (per-project binary and global binary). Maybe supporting both makes sense? Can you think of any situations where someone might have a good reason to not want to globally activate Tailwind?
One possibility is Tailwind versioning. If they make a breaking change, and a developer has multiple projects, some of which are their own custom websites with Tailwind, then there could be an issue where activating a version for Website 1 breaks Website 2. I have no idea how likely that might be.
If we still want to provide binaries, we could add a static_shock_tailwind package to the mono-repo whose job is simply to aggregate Tailwind binaries, and then provide a root level file like tailwind_download.yaml, which then lists Tailwind versions and a URL to that binary within our own repo. In that case, resolution would be fully in our control.

I think both options sound reasonable (per-project binary and global binary). Maybe supporting both makes sense? Can you think of any situations where someone might have a good reason to not want to globally activate Tailwind?
One possibility is Tailwind versioning. If they make a breaking change, and a developer has multiple projects, some of which are their own custom websites with Tailwind, then there could be an issue where activating a version for Website 1 breaks Website 2. I have no idea how likely that might be.
If we still want to provide binaries, we could add a static_shock_tailwind package to the mono-repo whose job is simply to aggregate Tailwind binaries, and then provide a root level file like tailwind_download.yaml, which then lists Tailwind versions and a URL to that binary within our own repo. In that case, resolution would be fully in our control.

From my experience with Tailwind so far, they seem to be quite rigorous. As such I would think that breaking changes to their CLI would be relatively unlikely. This is also enhanced by the fact that TW has seen significant adoption, including with non-js projects that depend on their CLI binary being consistent.
I think the biggest reason someone might not want to install a global version of the CLI, would be the implications of having to spend CI/CD minutes on installing it for build runners. But there are always workarounds for that, and nothing to stop users from adding the binaries to their template (as I have done in my template).
The benefits of globally installed Tailwind, probably outweigh the negatives, IMHO.
If someone is working with multiple versions (I think somewhat unlikely), giving users the flexibility of BYOT (Bring Your Own Tailwind) allows them to use a binary, or any global node package version (managed by their package manager of choice).
With that in mind, we could simply let the tailwind plugin be nothing more than an automatic "runner" for whatever tailwind version you have installed globally by default, with the optional tailwindPath param being used to point to specific binaries if needed.


Cannot scroll to top programatically when header is sticked.

My Pod Version: 3.0.1
I have a use case when one tab have scroll disabled and other one enabled.
So consider the following case:
Tab A -> Scroll Disabled
Tab B -> Scroll Enabled
Now I am in Tab B and scrolled half way and tabs are not sticked to top. Then I switch to Tab A following code works:
scrollView.setContentOffset(.zero, animated: true)
But When the header is sticked to top and I move to Tab A then I won't scroll to top.
Any fix or solution for this @Jiar
Thanks

Thanks for the feedback, but this should be a special scenario. The framework does not consider the Scroll Disabled scenario in its design.
I can't immediately tell what the problem is, but the framework listens to the scroll with the scrollView‘s observe() method. I'm not sure if using setContentOffset for A's scrollView can trigger the callback to the observe method. You can debug by setting a breakpoint at the callback of the Observe method.
I hope the information I've provided will help you.


Transition is not smooth after customizing.

I customized the accordion, and its transition animation is not smooth.
Here is my code with TailWind CSS.     Please let me know how I can fix it.
.item {
border: 1px solid gray;
border-radius: 5px;
margin-bottom: 25px;
}
.itemBtn {
cursor: pointer;
display: flex;
align-items: center;
width: 100%;
margin: 0;
padding-top: 8px;
padding-bottom: 8px;
padding-left: 14px;
padding-right: 14px;
font-size: 1.275em;
font-family: HelveticaRoman;
text-align: left;
color: #393939;
background-color: transparent;
border: none;
}
.itemBtn:hover {
background-color: #f3f3f3;
}
.itemBtnExpanded {
color: var(--defautColor);
border-bottom: 1px solid var(--defautColor);
}
.itemContent {
transition: height 0.1s linear;
font-size: 1.1em;
font-family: HelveticaRoman;
color: gray;
padding-top: 8px;
padding-bottom: 8px;
padding-left: 14px;
padding-right: 14px;
}
.chevron {
margin-left: auto;
transition: transform 0.2s ease-in-out;
}
.itemBtnExpanded .chevron {
transform: rotate(180deg);
}
.szh-accordion__item--expanded {
border: 1px solid var(--defautColor) !important;
}
Looking forward to your help!

It's most likely there is vertical margin on item children as explained in this page.

To ensure a smooth height animation on accordion items, do not add outer vertical margin to the children of an accordion item. Instead, use padding on the parent DOM element which contains the children. This is the element with class selector szh-accordion__item-panel.

Looks like your example uses css module so that in the jsx add className to the panel element:
<AccordionItem panelProps={{ className: styles.itemPanel }} />

In css file add a padding:
.itemPanel {
  padding: 1rem;
}

If you don't actually need the padding this also works:
.itemPanel {
  padding: 0.1px 0;
}

I didn't give margin to children of an accordion item but it is not smooth.
Please check my above code and let me know.
Thank you.

Ok, i may see the problem. Could you try to move the paddings from .itemContent  into .itemPanel?

Yes, it helped me.  Seems like it is fixed.
But when content is big (12 lines in my case), it is not smooth.

It might not get as smooth as 60fps.
Unlike the CSS transform property, CSS transition on the height property uses CPU rather than GPU. The accordion animation cannot use transform as it can skew the contents. But it should be fine on most devices even with the old ones I have tested.
Another factor is when you're inspecting the page in Chrome with the "Element" tab open, it can slow down the DOM updates and make the transition not smooth. Try to close the inspection window and see if the transition gets more smooth.

Thank you for your reply.
I just changed transition duration from 0.3s to 0.1s, and it is smooth enough
Thank you for your help.


Authentication using OAuth in the MPS IDE

As part of the discussion on authentication/authorization I start creating this PR. The goal is to make possible to authenticate within the MPS IDE and pass the token to the MMS (or any proxy in front of it).
For this:

We have a mechanism to specify the configuration. The idea is to support all the different OAuth flows possible. We have so far tested it with two different ones (we used Google and an instance of Identity Server)
We store the configuration in an XML file under the .mps directory. In this way this file could be committed and shared with new users without having them inserting this advanced configuration
We make the user login in a browser window we open from MPS
We use routes in the internal HTTP server as redirection URIs to capture the token and intermediate values
We have a small documentation file (doc/oauth_configuration.md)

Thank you for the revision!


Fix exception on windows for failing tests

Tests

testStartNewAgentOnUsedPort in sovrin-client
testStartAgentChecksForPortAvailability  in sovrin-client

Yes, you are right. I have taken note of it and will check the same in our daytime.


Add setting form

screen

Server URL
Room
Font properties
Message speed

comment

Server URL
Room

https://github.com/ihiroky/live-comment/pull/27

Font properties can't be set by design. Zoom setting is introduced instead. https://github.com/ihiroky/live-comment/pull/53


Site Page Loading New Design

The purpose of this PR is to close https://github.com/aqualinkorg/aqualink-app/issues/692.
TODOs

[x] Add skeletons for charts & surveys timeline
[x] Tweak loading condition and props passing

Design

desktop
iPad Air
iPhone 12 Pro

Great job @tleraj, I love the feel!
What do you think about using a skeleton for the featured site on the map page?

Looks great! Is there a deploy link?

Deployed on programize @Ry-DS  https://aqualink-app-programize.web.app/sites/1630

@ericboucher I did some work in https://github.com/aqualinkorg/aqualink-app/pull/694/commits/247cd1cca4a145c54060a01e6d90a3a82d1fd045, and made the featured site card on the map page look like this:

Let's also fix the text skeleton size change. Is there another way to set the size maybe so that it is less random and therefore less subject to reloads?

Let's also fix the text skeleton size change. Is there another way to set the size maybe so that it is less random and therefore less subject to reloads?

I think this is what we do on ovio for the text variant. We use a random length.

For the image logo, maybe we could find a reef symbol instead? Something that looks a bit like that

Looks good!! Let me know if you want to use this image, or you have something else looking like it in mind :slightly_smiling_face:

@tleraj

Let's also fix the text skeleton size change. Is there another way to set the size maybe so that it is less random and therefore less subject to reloads?

I think this is what we do on ovio for the text variant. We use a random length.

Yup this is a shortcoming on Ovio too. When I made it I didn't think it was a big deal since it's just skeleton loading, but would be nice to keep it consistent. One solution is to store the random values in some state and relying on those. Or even better, use a seed generated at the beginning:
const seed=useState(genSeed())
and use that to generate the lines. So each component will have a different seed but the line width won't change when the component is reloaded.

ially seed text skeleton line widths

@Ry-DS What do you think about https://github.com/aqualinkorg/aqualink-app/pull/694/commits/c39d468f6b5cf4ce6af819acfb7c8a53020fb8b9?

ially seed text skeleton line widths

@Ry-DS What do you think about c39d468?

Looks great :+1:

Looking good! Some commments might be enforcing a more Ovio-style structure, let me know if it'd be better if we stuck with what you have here.
Also a little unneccessary but could consider adding a play icon where the video goes in the skeleton animation eyes

@Ry-DS I updated the screenshots :wink:

@tleraj I noticed that if the FEATURED_REEF_ID is not set or the reef is not available, the skeleton stays on forever, which is not ideal:

@tleraj I noticed that if the FEATURED_REEF_ID is not set or the reef is not available, the skeleton stays on forever, which is not ideal:

I think that this contradicts with what @Ry-DS, i.e. considering the !site as a loading state.

@tleraj I noticed that if the FEATURED_REEF_ID is not set or the reef is not available, the skeleton stays on forever, which is not ideal:

I think that this contradicts with what @Ry-DS, i.e. considering the !site as a loading state.

See https://github.com/aqualinkorg/aqualink-app/pull/694#discussion_r842222497 :eyes: tbh free for you to do anything to solve this, what I mentioned is more for cleaniness so not too important

@ericboucher @Ry-DS I added an error handling functionality for the featured site, which looks like this


added ErG decoder for drug

I tested the encoder, and it works for KIBA, DAVIS, BindingDB(Kd).

Looks great! Thanks!

Looks great! Thanks!


(PUP-10351) Puppet Agent fails to self-restart

Before this change, puppet agent could get in a repeatedly restart_requested state.
This happens due to two agent runs taking place at about the same time where the second one needs to reload the puppet service(or simply receives a HUP signal) and can't restart because the first run is still in progress.

CLA signed by all contributors.

jenkins please test this


add autoenchant pls

big grin asked for auto enchant you shoulld add it

You should describe what AutoEnchant does.

WHY TF DO U NEED THAT


DPPTSBGTC-2838 Use setup(extras_require...) instead of requirements.txt.

See DPPTSBGTC-2838.
setup.py#read_requirements() fails while parsing the first line of "requirements-dev.txt", because it does not correctly handle the content "-r requirements.txt".
This PR implements the second suggested fix in the sub-task description:

Alternatively, instead of fixing read_requirements(), we can eschew the requirements.txt files entirely by leveraging extras_require.

This is the other proposed solution is:
$ python -c "\
> def read_requirements(file_path):
>     lines = pkg_resources.resource_string(__name__, file_path).splitlines()
>     return clean_requirements(lines)
>
> def clean_requirements(lines):
>     lines = (line.strip() for line in lines)
>     lines = (line for line in lines if line)
>     lines = (line.split()[0].strip() for line in lines)
>     return [line for line in lines if line[0] not in ('-', '#')]
>
> if __name__ == '__main__':
>     sample = (
>         '-r requirements.txt',
>         '--index-url',
>         ' good ',
>         'great #bad',
>         '# bad',
>         '',
>         ' ',
>     )
>     assert clean_requirements(sample) == ['good', 'great']
>     print('OK')"
OK

Looks good, thank you for finding a fix that improves dev workflow and maintainability as well!

LGTM

cool

Looks good. Could you also update the README to reflect the new dev setup workflow?

It would be nice if we could use this with the projects that depend on private libraries too, but the last time I played with setup.py stuff you couldn't specify alternate sources. It always pulled form pypi. Do you know if there's a way to make that work, or are we stuck using requirements files for those projects?

Awesome! :+1:  Feel free to merge!

@greatestape

Could you also update the README to reflect the new dev setup workflow?

Done in cbba783

Do you know if there's a way to make that work, or are we stuck using requirements files for those projects?

This is possible using dependency_links and setup_requires arguments to setuptools.setup().
local_pypi='<REDACTED NAME>'
local_dependency='<REDACTED URL>'
pushd $(mktemp -d) >/dev/null
virtualenv -q venv
source venv/bin/activate
pip install -Uq pip
pip install -q --no-cache-dir ${local_dependency} 2>/dev/null \
    || echo -e "\033[1;31m✖ Cannot install ${local_dependency} from pypi.python.org\033[0m";
echo "\
import setuptools
setuptools.setup(
    name='example',
    setup_requires=['${local_dependency}'],
    install_requires=['${local_dependency}'],
    dependency_links=['${local_pypi}/${local_dependency}'])
" > setup.py
pip install -q --process-dependency-links .
popd >/dev/null
pip freeze | grep -q ${local_dependency} && echo -e "\033[1;32m✔ ${local_dependency} is installed\033[0m"

This outputs:
✖ Cannot install <REDACTED NAME> from pypi.python.org
✔ <REDACTED NAME> installed from <REDACTED URL>

I do not believe that this approach is ideal, though. There is some related discussion on the pypa-dev mailing list.
IMO, this should not be the responsibility of the packaging metadata, instead the user's environment should define the package indexes that are consulted via: ~/.pip/pip.conf, ~/.pydistutils.cfg, and ~/.pypirc.


Remove c99 requirements

This allows to compile on less advanced compilers (more portable).

First, may I ask what compiler is torturing you into doing this?
Thanks for taking the time to make this patch. However, I'm not sure if
I really want to restrict the code to C90. I really like C99 and
strict C90 conformance is a real pain. The C99 standard is now 16 years
old and incorporated even older established language extensions. That's
plenty of time for compiler vendors to catch up.
I do know there's one major vendor in particular (cough Microsoft
cough) that's still two decades behind on these sorts of things.
However, the usual way to deal with them is to make the code compilable
as C++, which Optparse (mostly) is. If this is your situation, just
compile it as if it was C++.
As-is, your patch is currently an incomplete transformation. There are
still some double-slash comments, calls to snprintf (though now
removed), and, more importantly, a variable-length array in
optparse_fallback --- which also technically makes it invalid as C++,
but it hasn't caused problems yet. I just made my own "c90" branch as a
complete transformation to C90, with the help of GCC's "-pedantic" to
route out every last bit of C99. The transformation is mostly
mechanical, so, with Optparse being an embedded library, I'd rather just
let whoever needs it do it themselves (or they can use your or my
patch).

I will try your c90 branch thanks


Implement Read for i2c peripherals

Implement embedded_hal::blocking::i2c::Read for i2c peripherals

Any progress here? I have a couple device drivers waiting on this.


Question about internal users in the cross-region adfs deployment.

I understand the value of this architecture regarding external users that will use the traffic manager. My concern is about internal users. Internal users are supposed to be redirected to an adfs server when trying to access the sts right ? So how do you deal with dns resolution of the sts for internal users in such a deployment ? Are you supposed to use some kind of HLB on-prem? a DNS policy ? or do you consider that all users (external and internal) will go through the traffic manager ?
Thanks

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

ID: 2427554b-3bca-1b79-c037-97bdce61e093
Version Independent ID: 56f5a1ef-9c76-ca18-dbe4-d285bc36d967
Content: High availability cross-geographic AD FS deployment in Azure with Azure Traffic Manager
Content Source: WindowsServerDocs/identity/ad-fs/deployment/active-directory-adfs-in-azure-with-azure-traffic-manager.md
Product: windows-server
Technology: ad-fs
GitHub Login: @anandyadavMSFT
Microsoft Alias: billmath

Hello @DufferFromParis. GitHub issues are for letting us know that are there are problems with the documentation. For questions about your implementation, please contact support or post a question at MS Q & A.


Heap corruption

Steps to Reproduce

Don't know

Target Platform: iOS
Target OS version/browser: 13.2.0
Devices: iPhone 7
Logs

Crashed: com.apple.main-thread
EXC_BAD_ACCESS KERN_INVALID_ADDRESS 0x0000000000000130

Crashed: com.apple.main-thread
0  libobjc.A.dylib                0x19deb8140 objc_release + 16
1  libsystem_blocks.dylib         0x19dd69a48 _Block_release + 152
2  libsystem_blocks.dylib         0x19dd69a48 _Block_release + 152
3  UIKitCore                      0x1a17f08d4 __destroy_helper_block_e8_32s40s + 24
4  libsystem_blocks.dylib         0x19dd69a48 _Block_release + 152
5  libsystem_blocks.dylib         0x19dd69a48 _Block_release + 152
6  CoreFoundation                 0x19e0bf054 __RELEASE_OBJECTS_IN_THE_ARRAY__ + 112
7  CoreFoundation                 0x19e04ca4c -[__NSArrayM dealloc] + 268
8  UIKitCore                      0x1a1bed21c -[_UIViewControllerTransitionContext _runAlongsideCompletions] + 140
9  UIKitCore                      0x1a1becf58 -[_UIViewControllerTransitionContext completeTransition:] + 116
10 UIKitCore                      0x1a2631438 -[UITransitionView notifyDidCompleteTransition:] + 240
11 UIKitCore                      0x1a26310e4 -[UITransitionView _didCompleteTransition:] + 1132
12 UIKitCore                      0x1a2667218 -[UIViewAnimationBlockDelegate _didEndBlockAnimation:finished:context:] + 588
13 UIKitCore                      0x1a263b0c8 -[UIViewAnimationState sendDelegateAnimationDidStop:finished:] + 244
14 UIKitCore                      0x1a263b5d0 -[UIViewAnimationState animationDidStop:finished:] + 240
15 UIKitCore                      0x1a263b720 -[UIViewAnimationState animationDidStop:finished:] + 576
16 QuartzCore                     0x1a4bd3194 CA::Layer::run_animation_callbacks(void*) + 276
17 libdispatch.dylib              0x19de43184 _dispatch_client_callout + 16
18 libdispatch.dylib              0x19ddf5190 _dispatch_main_queue_callback_4CF$VARIANT$mp + 1044
19 CoreFoundation                 0x19e0f33a8 __CFRUNLOOP_IS_SERVICING_THE_MAIN_DISPATCH_QUEUE__ + 12
20 CoreFoundation                 0x19e0ee39c __CFRunLoopRun + 2004
21 CoreFoundation                 0x19e0ed8a0 CFRunLoopRunSpecific + 464
22 GraphicsServices               0x1a8045328 GSEventRunModal + 104
23 UIKitCore                      0x1a21de768 UIApplicationMain + 1936
24 Runner                         0x10284c4c8 main + 5 (AppDelegate.swift:5)
25 libdyld.dylib                  0x19df78360 start + 4

[√] Flutter (Channel stable, v1.12.13+hotfix.5, on Microsoft Windows [Version 10.0.18362.535], locale pt-BR)
    • Flutter version 1.12.13+hotfix.5 at C:\flutter
    • Framework revision 27321ebbad (13 days ago), 2019-12-10 18:15:01 -0800
    • Engine revision 2994f7e1e6
    • Dart version 2.7.0

[√] Android toolchain - develop for Android devices (Android SDK version 29.0.2)
    • Android SDK at C:\Users\jckod\AppData\Local\Android\Sdk
    • Android NDK location not configured (optional; useful for native profiling support)
    • Platform android-29, build-tools 29.0.2
    • ANDROID_HOME = C:\Users\jckod\AppData\Local\Android\Sdk
    • ANDROID_SDK_ROOT = C:\Users\jckod\AppData\Local\Android\Sdk
    • Java binary at: C:\Program Files\Android\Android Studio\jre\bin\java
    • Java version OpenJDK Runtime Environment (build 1.8.0_202-release-1483-b03)
    • All Android licenses accepted.

[√] Android Studio (version 3.5)
    • Android Studio at C:\Program Files\Android\Android Studio
    • Flutter plugin version 42.1.1
    • Dart plugin version 191.8593
    • Java version OpenJDK Runtime Environment (build 1.8.0_202-release-1483-b03)

[√] VS Code, 64-bit edition (version 1.41.1)
    • VS Code at C:\Program Files\Microsoft VS Code
    • Flutter extension version 3.7.1

[√] Connected device (2 available)
    • XT1033   •<PHONE_NUMBER> • android-arm • Android 5.0.2 (API 21)
    • SM J415G • 785dd05b   • android-arm • Android 9 (API 28)

• No issues found!

Insights:
The stack trace indicates that heap corruption may have caused your app to crash. Memory corruption can occur pretty easily from freeing a dangling pointer, a thread race, or bad pointer arithmetic. The important thing to keep in mind is that the resulting crash may happen long after the initial corruption. As a result, the stack trace for this crash might not provide any clues to the location of the bug in your code. However, you can still fix memory issues with tools from Apple. For speedy resolution of memory corruption issues, we recommend regularly auditing your app with Xcode’s memory debugging facilities: Visual Memory Debugger, Zombies Instrument, Address Sanitizer, Thread Sanitizer and malloc diagnostics.
External resources

iOS Debugging Magic
macOS Debugging Magic
Apple Memory Usage Performance Guidelines
Zombies Instrument Guide
WWDC 2015: Advanced Debugging and the Address Sanitizer
WWDC 2016: Thread Sanitizer and Static Analysis
Apple Secure Coding Guide: Avoiding Buffer Overflows and Underflows

Hi @JCKodel
can you please provide your flutter run --verbose
and  a minimal code sample
or the steps to reproduce the problem.
Thank you


server down will send repetitive message

The master and worker will listen to other master or worker services down from zk, and will send message notifications, but this message  will send one for each monitored service, so repeat.
For example, I have 3 masters and 3 workers, and one of the masters is down. The remaining five services will insert an alert data
in the database.
I haven't a good plan to fix this issue ,shoule we  consider the influence of normal version iterations?

@wangxj3 Yeal, I also noticed this problem, this caused by each instance will listen the node path in zookeeper.
One possible solution is to get the lock on zookeeper when insert the instance crash alert.

@wangxj3 Yeal, I also noticed this problem, this caused by each instance will listen the node path in zookeeper.
~One possible solution is to get the lock on zookeeper when insert the instance crash alert.~
Can we think each instance should save at most one unsent instance alert in database?
---Can we think each instance should save at most one unsent instance alert in database?
Yes,this we will do something in alert .Do you have a dateil plan?
---And
The solution with lock on zookeeper can resove this issue.How ablut that,if we can get the time of server down ,insert this time to t_ds_alert ,this time is the PRIMARY KEY,so other server will fail to insert database.

@wangxj3 I think it is hard to get the exact time when the server down, the time that each instance gets this event may be different.
Use lock on zookeeper does not seem to be a good solution for this issue, because some instances may get this event late.
The best solution may be when we insert to the t_ds_alert table, check whether there is the same content in the database for sending, the SQL like below
INSERT INTO t_ds_alert(instance, user, item)
    SELECT xx, xxx, xxxx FROM t_ds_alert
        WHERE NOT EXISTS (SELECT * FROM t_ds_alert WHERE content ='' AND alert_status = WAIT_EXECUTION)

I didn't test this SQL, but this should be work.
In this way, there will be only one unsent alert for each instance in the database. But I think this is reasonable.

This is indeed a question that can be improved. Can anyone submit a PR for this?


Decide on code formatting

I'm not a big fan of the formatting changes, especially the if statements (for example in the method create()). Ideally keep formatting as was and then agree on some code style and formatting standard - this applies just to the changes made in GUI.py
Originally posted by @miskfi in https://github.com/stepva/chatalysis/pull/11#pullrequestreview-1048652168

@miskfi try to use black, I like it and vote for it hehe

I really don't like some of the formatting choices in Black - makes the code unnecessarily long and confusing to read. What about autopep8? I think having a PEP8 compliant code is alright, even if the formatting differs a little bit somewhere. But I respect your preferences, so if you want, Black it is.
Also maybe we could formalize other code aspects as well like docstrings (maybe use some linter like pydocstyle) and type annotations?

Settled on Black.


base .travis.yml on travis env vars

This bases Travis CI operation on various necessary travis env vars. Use of docker-compose to create specific docker machines is now in a script

merged as improves travis CI and tests pass. No impact on node app or db


Data Table Filter

Is there a way to filter the table rows like with TanStack Tables?

Data Tables are currently not actively supported.
There's a post that points you to some well maintained alternatives like datatables

We're referring all data table discussion here: https://github.com/skeletonlabs/skeleton/issues/538


examples/imdb_cnn.py not working

Hi,
I'm running the examples/imdb_cnn.py script with current master branch of keras and 0.8.2. Theano version.
However, the code is not learning anything. The loss does not go down and the accuracy stays at 50%.
The other example, for example imdb_lstm.py or imdb_festtext.py work as expected and achieve around 90% accuracy.
I suspect that something with the convolution or the max-over-time is broken in the imdb_cnn.py script.
Has anyone else the same problem?

Nevermind, just cleaned all cache files and updated Theano once more and now it is running and it is learning as expected.
Sorry for the spam.

Hello,
I have the following error with the script, could you help me with that?
Thank you!
File "/usr/lib64/python3.4/urllib/request.py", line 1183, in do_open
h.request(req.get_method(), req.selector, req.data, headers)
File "/usr/lib64/python3.4/http/client.py", line 1137, in request
self._send_request(method, url, body, headers)
File "/usr/lib64/python3.4/http/client.py", line 1182, in _send_request
self.endheaders(body)
File "/usr/lib64/python3.4/http/client.py", line 1133, in endheaders
self._send_output(message_body)
File "/usr/lib64/python3.4/http/client.py", line 963, in _send_output
self.send(msg)
File "/usr/lib64/python3.4/http/client.py", line 898, in send
self.connect()
File "/usr/lib64/python3.4/http/client.py", line 1287, in connect
server_hostname=server_hostname)
File "/usr/lib64/python3.4/ssl.py", line 362, in wrap_socket
_context=self)
File "/usr/lib64/python3.4/ssl.py", line 580, in init
self.do_handshake()
File "/usr/lib64/python3.4/ssl.py", line 807, in do_handshake
self._sslobj.do_handshake()
ssl.SSLError: [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:600)
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/lib64/python3.4/site-packages/keras/utils/data_utils.py", line 220, in get_file
urlretrieve(origin, fpath, dl_progress)
File "/usr/lib64/python3.4/urllib/request.py", line 186, in urlretrieve
with contextlib.closing(urlopen(url, data)) as fp:
File "/usr/lib64/python3.4/urllib/request.py", line 161, in urlopen
return opener.open(url, data, timeout)
File "/usr/lib64/python3.4/urllib/request.py", line 464, in open
response = self._open(req, data)
File "/usr/lib64/python3.4/urllib/request.py", line 482, in _open
'_open', req)
File "/usr/lib64/python3.4/urllib/request.py", line 442, in _call_chain
result = func(*args)
File "/usr/lib64/python3.4/urllib/request.py", line 1226, in https_open
context=self._context, check_hostname=self._check_hostname)
File "/usr/lib64/python3.4/urllib/request.py", line 1185, in do_open
raise URLError(err)
urllib.error.URLError: <urlopen error [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:600)>
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "imdb_cnn.py", line 29, in
(x_train, y_train), (x_test, y_test) = imdb.load_data(num_words=max_features)
File "/usr/lib64/python3.4/site-packages/keras/datasets/imdb.py", line 51, in load_data
path = get_file(path, origin='https://s3.amazonaws.com/text-datasets/imdb.npz')
File "/usr/lib64/python3.4/site-packages/keras/utils/data_utils.py", line 222, in get_file
raise Exception(error_msg.format(origin, e.errno, e.reason))
Exception: URL fetch failure on https://s3.amazonaws.com/text-datasets/imdb.npz: None -- [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:600)


v10.1 release

Background
We should probably cut a v10.1 soon, we've already accumulated a notable number of changes on v10.x. We are also planning to backport many of the accumulated main changes to v10.x, and would be good to incrementally test commits to date first.

[x] Refactors
[x] TokenFactory InitGenesis fixes
[x] Update v10.x SDK import

Which has the store hash logging update, to reduce log spam

Suggested Design
Once the minor test commit workflow is merged & we have updated v10.x SDK import:

[x] Run the commit workflow on v10.x
[x] See if we can extend workflows, to make binaries from a manually created releas

Also we need to cleanup the changelog prior to release
Acceptance Criteria

[x] v10.1 tag and release exists
[x] Has an automated test for state machine compatability
[x] Binaries exist on release

I think we can close this issue.

State compatibility check was added in https://github.com/osmosis-labs/osmosis/pull/2178
Release workflow can be triggered via osmosis-ci repository. It was used to create: https://github.com/osmosis-labs/osmosis/releases/tag/v10.1.0


decode.rs: Mark functions safe and document unsafe operations

Mark decode_b, decode_sb, rav1d_decode_tile_sbrow, and rav1d_decode_frame_main as safe, putting any unsafe operations in unsafe blocks and documenting their safety invariants. For the bd_fn calls those should be safe since they're pure Rust calls and just haven't been marked safe. Once they're made safe we can clean up the unnecessary unsafe blocks. I also marked load_tmvs and save_tmvs safe since those wrap the unsafe asm call and handle converting the safe Rust args to the raw pointers that asm needs.
Part of #843.

I was discussing this a bit with @rinon; I think we should make index_mut safe like we did index.  All of the safety comments are essentially the same and we're not really saying anything meaningful.


Code cleanup

What I purpose with this PR:

Code simplification, it is little messed in IDE when you see all methods twice
PEP8 cleanup
Switch to mixin type of inheritance

I hope it will help to maintain and develop code in the future.

@xen Will you fix the issues with the super class? Your pull request is awesome but there are several bugs that should be fixed!

@xen Waiting for your fixes.


IE11 rendering of contributors on events

IE11 seems to be struggling with contributors. You can see here the image overlays the bio text:
https://wellcomecollection.org/events/W498dB4AACEAph-V

FWIW it doesn't seem to be an issue on new articles or even events with schedules:
https://wellcomecollection.org/events/W5fKOiYAACYAMt8T
https://content.wellcomecollection.org/articles/W6zJhRAAAB8Ae6NL

Same problem on IE11 on Windows, but no problem on Edge on Windows.


resource_control: take global resource consumption into consideration

What is changed and how it works?

Issue Number: Close #14604
What's Changed:

resource control takes global resource consumption into consideration

Check List
Tests

Manual test (add detailed scripts or steps below)

Under an unbalanced leader distribution, this patch can control the QPS quota of two resource groups nearly 1:1

Release note
resource control takes global resource consumption into consideration to improve scheduling effect

/merge

/merge


Custom variables in settings.json for easier profile configuration

Description of the new feature/enhancement
Let one define custom variables in settings.json for use with profiles.
E.g. define myCustomVariable for later use within commandline to avoid adding same long path to SSH key file for every profile name.
Would also be great to reuse current profile parameters such as "name" to connect to this hostname by stating $profile.name with SSH as shown in example.

Proposed technical implementation details (optional)
"profiles":
{
    "defaults":
    {
        "myCustomVariable": "C:\\Users\\USERNAME\\SSH_KEY_FILE_PATH.key"
    },
    "list":
    [
        {
            "name": "HOSTNAME",
            "commandline": "ssh -i $myCustomVariable $profile.name",
        },

This isn't a terrible idea, but I'm guessing that this would not play well with the Settings UI.  So this would end up being a feature that would work well if you exclusively used the json settings. I'm gonna stick this in the freezer for now. It's a reasonable request, but not one we're likely to get to anytime soon.


improve validation for CeleryExecutor (ensure redis is enabled)

Currently, we validate that the user has disabled workers.enabled, flower.enabled, and redis.enabled if airflow.executor=KubernetesExecutor.
We should also validate the reverse for CeleryExecutor and CeleryKubernetesExecutor, that is we should ensure that:

Either embedded or external Redis is enabled
NOTE: we shouldn't force flower to be enabled, as not all users will want flower

Bumping for bot.

Bumping for bot.


Incorrect info in the "Groups for Architects" document

@officedocsbot assign @mypil

@zendack - May we know which Microsoft document link you used in reference to this issue?
Please share it with us so we can investigate further. Thank you.

Please delete.  Posted in another area.


Radix Card size attribute not working

Describe the bug
Exactly what is in the title, the size attribute in reflex.components.radix.themes does not work, as it does not appear in the HTML.
The issue comes from the fact that the size python attribute is converted in js as size={4} where it should be size="4"
To Reproduce
Just adding reflex.components.radix.themes.card in a blank reflex page
Expected behavior
n.a.
Screenshots
n.a.
Specifics (please complete the following information):
n.a.
Additional context
n.a.

May be addressed by https://github.com/reflex-dev/reflex/pull/2316/files#diff-ddebfec818cd67f4680ada31d1a99a197df36a3ac23d933fc79876ab468dff1b
The radix components should still be considered experimental, we will look into this as we finalize the components and fix the documentation.

This is resolved now.


Clean up from PR #286

PR #286 has two incomplete to-dos that need to be cleaned up. A PR addressing this issue should address the following:

[ ] Remove developers.time_zone and developers.utc_offset
[ ] Remove conditional validation for locations.latitude and locations.longitude

@joemasilotti Can I work on this issue?

Yes please! If you see any other unused columns feel free to open a PR to get rid of those, too. Thank you.

@joemasilotti Added PR https://github.com/joemasilotti/railsdevs.com/pull/315. Please review.

Yes please! If you see any other unused columns feel free to open a PR to get rid of those, too. Thank you.

I will look into it and let you know.

Done via #315.


Atlantic Explorer v4 Cozytouch bridge away mode don't work

Did you read the instructions?

[X] I have read the README, including the advanced debugging section.

The problem
I've got 2 entities to control the explorer v4.
Boost mode & away mode.
Boost mode works fine, but the away mode does nothing. With the cold weather I want to control the pump with boost mode and away mode. Set is to away 'always' and let HA set it to boost to heat the water to a target level and set it back to away again after the temp is reached.

The slider don't work and I see no error or something in the logs.
If i set it to 1 it goes automatic back to 0

What version of this integration (ha-tahoma) has the issue?
2.14.0
What version of Home Assistant Core has the issue?
2022.11.2
Which gateway / hub do you use?
Cozytouch
Device model
AtlanticDomesticHotWaterProductionV2_CV4E_IOComponent
Home Assistant log
Logs
Copy/paste any log here, between the starting and ending backticks. The first log line must start with "Added device (Device...".

Additional information
No response

@Step-han could you try the Overkiz integration from core? If you face the same issue, you can create an issue there and include your diagnostics information. This integration does not receive many updates anymore, we mainly focus on the core integration at the moment.

@iMicknl thanks for your reply
I have deleted the intergration from /config/custom_componens, rebooted HA and installed the cozytouch core intergration (via Overkiz). Same behavior.
Where do I need to make a new issue?

Here https://github.com/home-assistant/core/issues


zen-browser: init at 1.0.2-b.4

https://zen-browser.app/
Closes https://github.com/NixOS/nixpkgs/issues/327982
NOTE: This package takes quite a lot of resources to build. It took me an hour maybe two on my machine (3200g), This is not a package you want to compile yourself if you can avoid it.
If anyone wants to be added as a maintainer to this package, please leave a comment and I will add you.
Followup from PR https://github.com/NixOS/nixpkgs/pull/347222 that got reverted because of this comment: https://github.com/NixOS/nixpkgs/pull/347222#issuecomment-2508814428 I want to make sure this pr is okay to go on nixpkgs the right way instead of reverting.
I will add myself as a maintainer once I have my darwin stuff sorted.
Things done

Built on platform(s)

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

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

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

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

[x] Fits CONTRIBUTING.md.

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

I will add myself as a maintainer once I have my darwin stuff sorted.

I will need to fix the update script to update surfer and firefox.

I want to make sure this pr is okay to go on nixpkgs the right way instead of reverting.

The PR had not only had technical issues, but project management issues inherent to upstream as well. As such, drafting until a consensus across committees/security/buildMozillaMach folks can be reached.

@ofberg build zen-browser

@ofborg build zen-browser

I want to make sure this pr is okay to go on nixpkgs the right way instead of reverting.

The PR had not only had technical issues, but project management issues inherent to upstream as well. As such, drafting until a consensus across committees/security/buildMozillaMach folks can be reached.

I mean it's in beta so there will be only small big changes but the Firefox version was rolled back because of half of the browser broke due to new apis in FF 133.

@ofborg build zen-browser

This was the reason because It took two hours for a single build and my machine and I need to sleep.

I will keep this in draft until it's fully stable.

Working on darwin support, but a lot of libraries used that are linux based.

You would need to provide an example of a library in question, and why you think it's (a) needed, and (b) an issue on Darwin.

Working on darwin support, but a lot of libraries used that are linux based, is there an easier route of finding out what is using a linux thing directly.

You could run readelf -d </path/to/binary>

Working on darwin support, but a lot of libraries used that are linux based, is there an easier route of finding out what is using a linux thing directly.

You could run readelf -d </path/to/binary>

But I can't build on my linux but I can with my darwin so I don't know what is using what.

And I keep getting these errors

You could try nix eval .#zen-browser -vvv to find where this error happens

Zen ended up shipping a known‐vulnerable version for 12 days

Where are you getting this from? It was literally released on the same day

I think this is about the a.20 that got rolled back in a.21. The FF version only got updated for the beta release ~two weeks after.

Hm, there wasn't any major security issues while in 21

There were multiple known security vulnerabilities in Firefox 133 at the point Zen rolled back to 132 and remained there for almost two weeks, one of which was high severity. As discussed in https://github.com/NixOS/nixpkgs/pull/347222, that just falls below the standards we consider acceptable for browser forks, and which the ones we ship like LibreWolf have managed to keep up with so far. I can understand if Zen doesn’t have the resources to keep up with new upstream versions in a timely fashion, but downstream forks that can’t get releases out within ~3 days of upstream security fixes are not something we can ship to users in good conscience.
The question is not so much which security vulnerabilities were being shipped to end users in practice – although clearly there was at least one that Mozilla considered to be serious – but the fact that even if there had been extremely serious issues it doesn’t seem like Zen would have been equipped to protect their users in that period. At a minimum I think the version that rolled back to the Firefox version with known vulnerabilities should have contained a prominent notice in the release notes that it was known to be insecure and linked to the upstream advisories. That way users and downstream distributors would at least be aware of that (and we could have e.g. marked it with knownVulnerabilities on our end to warn our own users).

Just to note I am note I am keeping this I no draft until stable or they improve their security.

This is substantially based on the work in zen-browser: init at 1.0.1-a.22 #347222, but the commit metadata contains no credit to @matthewpi. Either the Git commit author should be restored or a Co-authored-by: trailer should be added to give appropriate credit and avoid a licence violation.

@matthewpi is now credited .

This duplicates code from buildMozillaMach, some of it incorrect as a result (e.g. the LTO stuff looks wrong). It would be best for us to apply their patchset on top of the pristine Firefox source ourselves and then use the standard buildMozillaMach rather than relying on their own build tool.

I mean that could work but the problem I run into is using an update script to update the browser in less than 72hrs.
But also another problem is fetching where the patches are could get complex and if paths change then yeah it could break.

The LLVM closure stuff should of course be addressed.

I haven't found the root cause because I am working on getting darwin builds working.

However, I want to be clear that I think the upstream security posture is the overriding concern here and that solving these secondary issues alone would not be sufficient to merge this PR.

Just to note I am note I am keeping this I no draft until stable or they improve their security.

Wait, does brave, vivaldi, opera, etc release chromium updates without properly testing it for at least a week? Such big updates can break so many things, they must have insane developers

Wait, does brave, vivaldi, opera, etc release chromium updates without properly testing it for at least a week? Such big updates can break so many things, they must have insane developers

They have normal developers doing testing on beta versions, incremental rollouts, backporting of security patches and rollbacks as their day to day job.

Yes, the only real way to keep up with browser vendors and not put users at risk is to develop and test on development versions significantly in advance of them being released, so that you can cut a well‐tested release in a timely fashion after upstream does. (And with Chromium I guess there’s also a larger ecosystem of third parties backporting security fixes to earlier versions, e.g. Qt. Firefox ESR gets similar support and would significantly reduce the frequency of churn, but I guess it wouldn’t be acceptable for Zen.)

Oh, so they get their updates in advance? I might need to take a look into that, that sounds like a good thing to do

Oh wow, this actually opened my eyes a lot. Ill be changing stable releases to RC, so I can test builds 1 week before actual release (https://archive.mozilla.org/pub/firefox/candidates/)
Thanks a lot! I coudnt had learned this if it wasnt for this convo

Ideally you’d want to keep up to date with the upstream Mercurial (soon to be Git?) development version of Firefox and create release branches when they do, so that even by the time an upstream release candidate is cut you’ve already had time to adapt to the changes and get some testing of the result (say, by offering nightly builds to users).

Thanks a lot!

Ideally you’d want to keep up to date with the upstream Mercurial (soon to be Git?)

I heard about Firefox switching to git, is that still happen or not cause I heard at nov 2023 they were going to start switching in 6 months but I don't know any progress has been done?


rm secondary button color

Remove specifying the color button as "secondary" seems to allow the text to be blue in both light and dark mode.

I still want to fix something in the theme because this issue occurs elsewhere (such as the contributor's guide) but this is a quick fix to make the sign up visible!

Ignore link checker here, unrelated to PR


MASS_VHOST with php-fpm

Hi,
im just trying to get the MASS_VHOST work with php-fpm.
 But when i call the index.php i got a No input file specified..
Any ideas on how resolve that?
Thanks & best regards
Thomas

More Debug Informations:
/var/log/nginx-mainline/mytest-error.log is empty, cat /var/log/nginx-mainline/mytest-access.log gives status 200 on index.html and status 404 on index.php

Ok, was pretty obvious... 🤦
Changed PHP -v to
-v /var/www/5.2:/shared/httpd \


[Feature]: K8sgpt-deployment ownerref to operator

Checklist

[X] I've searched for similar issues and couldn't find anything matching
[X] I've discussed this feature request in the K8sGPT Slack and got positive feedback

Is this feature request related to a problem?
No
Problem Description
No response
Solution Description
Adding an owner-reference from the k8sgpt-operator to the  deployment assets would help visualise it in argocd and flux
Benefits
better visualisation
Potential Drawbacks
No response
Additional Information
No response

I will pick this up tomorrow , feel free to assign it to me @AlexsJones


Overloading Avalonia.Media.Imaging classes

Greeting,
Am am currently looking at Avalonia for x-platform apps.
I was wondering if there are plans to overload the constructors for the various classes that are defined in System.Drawing.Common, like Bitmap?  An Example would the ability to construct an Avalonia.Media.Imaging.Bitmap without going the route of streams and using System.Drawing.Common items natively in Avalonia, since they are x-platform.  Some thing like this:
Avalonia.Media.Imaging.Bitmap resBitmap = Properties.Resources.SomeImage;

instead of:
MemoryStream memStream = new MemoryStream();
((System.Drawing.Image)Properties.Resources.SomeImage).Save(memStream, ImageFormat.Png);
memStream.Seek(0, SeekOrigin.Begin);  //Throws error if this is this is missed should be caught in Bitmap
Avalonia.Media.Imaging.Bitmap resBitmap = new Avalonia.Media.Imaging.Bitmap(memStream);

IMHO - The streams method slows things down and is cumbersome.
Cheers,
Noral

It seems like a bad idea to add an extra dependency to the main project. Instead, you can create a separate library where an extension will be defined with a signature similar to the following
public static Avalonia.Media.Imaging.Bitmap Avalonia.ToAvaloniaBitmap(System.Drawing.Image value)

@kekekeks @grokys I think we have talked about this before? seems like we could improve api here?


Variable inferred as unbound although defined

Environment data

Language Server version: Pylance language server 2021.11.2 (pyright b27108d5)
OS and version: Win 10.0.19044
Python version (& distribution if applicable, e.g. Anaconda): CPython 3.6

Expected behaviour
The following code should be valid:
new_mount_path = Path(tempfile.gettempdir()) / f'flsync_union_mnt-{mount_uid}'
drive_letter = '*' if os.name == 'nt' else str(new_mount_path)

Actual behaviour
new_mount_path generates error

Argument type is unknown
Argument corresponds to parameter "object" in function "__new__"
PylancereportUnknownArgumentType

Additionally, hovering over the parameter we see it's value is unbound:

Logs

Logs

[Info  - 21:35:11] Pylance language server 2021.11.2 (pyright b27108d5) starting
[Info  - 21:35:11] Server root directory: c:\Users\styagev\.vscode\extensions\ms-python.vscode-pylance-2021.11.2\dist
[Info  - 21:35:11] Setting pythonPath for service "python": "C:\Users\styagev\.virtualenvs\flsync\Scripts\python.exe"
[Info  - 21:35:11] Loading configuration file at d:\Projects\flsync\flsync\python\pyrightconfig.json
[Info  - 21:35:12] Assuming Python version 3.6
[Info  - 21:35:12] Assuming Python platform Windows
[Info  - 21:35:12] No include entries specified; assuming d:\Projects\flsync\flsync\python
Search paths for d:\Projects\flsync\flsync\python
  c:\Users\styagev\.vscode\extensions\ms-python.vscode-pylance-2021.11.2\dist\typeshed-fallback\stdlib
  d:\Projects\flsync\flsync\python
  d:\Projects\flsync\flsync\python\src
  d:\Projects\flsync\flsync\python\typings
  c:\Users\styagev\.vscode\extensions\ms-python.vscode-pylance-2021.11.2\dist\typeshed-fallback\stubs\...
  c:\Users\styagev\.vscode\extensions\ms-python.vscode-pylance-2021.11.2\dist\bundled\stubs
  c:\Program Files\Python36\DLLs
  c:\Program Files\Python36\Lib
  c:\Program Files\Python36
  c:\Users\styagev\.virtualenvs\flsync
  c:\Users\styagev\.virtualenvs\flsync\Lib\site-packages
  d:\Projects\flsync\flsync\python\src
[Info  - 21:35:12] Searching for source files
[Info  - 21:35:12] Found 11 source files
[Info  - 21:35:12] Background analysis(1) root directory: c:\Users\styagev\.vscode\extensions\ms-python.vscode-pylance-2021.11.2\dist
[Info  - 21:35:12] Background analysis(1) started
Background analysis message: setConfigOptions
Background analysis message: setImportResolver
Background analysis message: ensurePartialStubPackages
Background analysis message: setTrackedFiles
Background analysis message: markAllFilesDirty
Background analysis message: analyze
Background analysis message: markFilesDirty
Background analysis message: analyze
Background analysis message: invalidateAndForceReanalysis
[Info  - 21:35:18] Searching for source files
[Info  - 21:35:18] Found 11 source files
Background analysis message: setTrackedFiles
Background analysis message: markAllFilesDirty
Background analysis message: analyze
Background analysis message: markFilesDirty
Background analysis message: analyze
Background analysis message: invalidateAndForceReanalysis
Background analysis message: invalidateAndForceReanalysis
Background analysis message: markFilesDirty
Background analysis message: markFilesDirty
Background analysis message: markFilesDirty
[Info  - 21:35:20] Searching for source files
[Info  - 21:35:20] Found 11 source files
Background analysis message: setTrackedFiles
Background analysis message: markAllFilesDirty
Background analysis message: analyze
Background analysis message: setFileOpened
[FG] parsing: d:\Projects\flsync\flsync\python\src\flsync\rclone.py (203ms)
[FG] parsing: c:\Users\styagev\.vscode\extensions\ms-python.vscode-pylance-2021.11.2\dist\typeshed-fallback\stdlib\builtins.pyi [fs read 13ms] (232ms)
[FG] binding: c:\Users\styagev\.vscode\extensions\ms-python.vscode-pylance-2021.11.2\dist\typeshed-fallback\stdlib\builtins.pyi (95ms)
[FG] binding: d:\Projects\flsync\flsync\python\src\flsync\rclone.py (6ms)
Background analysis message: getDiagnosticsForRange
Background analysis message: analyze
[BG(1)] analyzing: d:\Projects\flsync\flsync\python\src\flsync\rclone.py ...
[BG(1)]   parsing: d:\Projects\flsync\flsync\python\src\flsync\rclone.py (130ms)
[BG(1)]   parsing: c:\Users\styagev\.vscode\extensions\ms-python.vscode-pylance-2021.11.2\dist\typeshed-fallback\stdlib\builtins.pyi [fs read 7ms] (227ms)
[BG(1)]   binding: c:\Users\styagev\.vscode\extensions\ms-python.vscode-pylance-2021.11.2\dist\typeshed-fallback\stdlib\builtins.pyi (97ms)
[BG(1)]   binding: d:\Projects\flsync\flsync\python\src\flsync\rclone.py (7ms)
[BG(1)]   checking: d:\Projects\flsync\flsync\python\src\flsync\rclone.py ...
[BG(1)]     parsing: c:\Users\styagev\.vscode\extensions\ms-python.vscode-pylance-2021.11.2\dist\typeshed-fallback\stdlib\typing.pyi [fs read 1ms] (53ms)
[BG(1)]     binding: c:\Users\styagev\.vscode\extensions\ms-python.vscode-pylance-2021.11.2\dist\typeshed-fallback\stdlib\typing.pyi (31ms)
[BG(1)]     parsing: c:\Users\styagev\.vscode\extensions\ms-python.vscode-pylance-2021.11.2\dist\typeshed-fallback\stdlib\_typeshed\__init__.pyi [fs read 1ms] (24ms)
[BG(1)]     binding: c:\Users\styagev\.vscode\extensions\ms-python.vscode-pylance-2021.11.2\dist\typeshed-fallback\stdlib\_typeshed\__init__.pyi (3ms)
[BG(1)]     parsing: c:\Users\styagev\.vscode\extensions\ms-python.vscode-pylance-2021.11.2\dist\typeshed-fallback\stdlib\typing_extensions.pyi [fs read 0ms] (4ms)
[BG(1)]     binding: c:\Users\styagev\.vscode\extensions\ms-python.vscode-pylance-2021.11.2\dist\typeshed-fallback\stdlib\typing_extensions.pyi (6ms)
[BG(1)]     parsing: c:\Users\styagev\.vscode\extensions\ms-python.vscode-pylance-2021.11.2\dist\typeshed-fallback\stdlib\abc.pyi [fs read 0ms] (5ms)
[BG(1)]     binding: c:\Users\styagev\.vscode\extensions\ms-python.vscode-pylance-2021.11.2\dist\typeshed-fallback\stdlib\abc.pyi (1ms)
[BG(1)]     parsing: c:\Users\styagev\.vscode\extensions\ms-python.vscode-pylance-2021.11.2\dist\typeshed-fallback\stdlib\logging\__init__.pyi [fs read 0ms] (35ms)
[BG(1)]     binding: c:\Users\styagev\.vscode\extensions\ms-python.vscode-pylance-2021.11.2\dist\typeshed-fallback\stdlib\logging\__init__.pyi (13ms)
[BG(1)]     parsing: c:\Users\styagev\.vscode\extensions\ms-python.vscode-pylance-2021.11.2\dist\typeshed-fallback\stdlib\os\__init__.pyi [fs read 0ms] (26ms)
[BG(1)]     binding: c:\Users\styagev\.vscode\extensions\ms-python.vscode-pylance-2021.11.2\dist\typeshed-fallback\stdlib\os\__init__.pyi (26ms)
[BG(1)]     parsing: c:\Users\styagev\.vscode\extensions\ms-python.vscode-pylance-2021.11.2\dist\typeshed-fallback\stdlib\pathlib.pyi [fs read 1ms] (14ms)
[BG(1)]     binding: c:\Users\styagev\.vscode\extensions\ms-python.vscode-pylance-2021.11.2\dist\typeshed-fallback\stdlib\pathlib.pyi (8ms)
[BG(1)]     parsing: c:\Users\styagev\.vscode\extensions\ms-python.vscode-pylance-2021.11.2\dist\typeshed-fallback\stdlib\re.pyi [fs read 1ms] (8ms)
[BG(1)]     binding: c:\Users\styagev\.vscode\extensions\ms-python.vscode-pylance-2021.11.2\dist\typeshed-fallback\stdlib\re.pyi (6ms)
[BG(1)]     parsing: c:\Users\styagev\.vscode\extensions\ms-python.vscode-pylance-2021.11.2\dist\typeshed-fallback\stdlib\subprocess.pyi [fs read 1ms] (14ms)
[BG(1)]     binding: c:\Users\styagev\.vscode\extensions\ms-python.vscode-pylance-2021.11.2\dist\typeshed-fallback\stdlib\subprocess.pyi (11ms)
[BG(1)]     parsing: c:\Users\styagev\.vscode\extensions\ms-python.vscode-pylance-2021.11.2\dist\typeshed-fallback\stdlib\tempfile.pyi [fs read 1ms] (9ms)
[BG(1)]     binding: c:\Users\styagev\.vscode\extensions\ms-python.vscode-pylance-2021.11.2\dist\typeshed-fallback\stdlib\tempfile.pyi (9ms)
[BG(1)]     parsing: c:\Users\styagev\.vscode\extensions\ms-python.vscode-pylance-2021.11.2\dist\typeshed-fallback\stdlib\urllib\parse.pyi [fs read 1ms] (4ms)
[BG(1)]     binding: c:\Users\styagev\.vscode\extensions\ms-python.vscode-pylance-2021.11.2\dist\typeshed-fallback\stdlib\urllib\parse.pyi (4ms)
[BG(1)]     parsing: c:\Users\styagev\.vscode\extensions\ms-python.vscode-pylance-2021.11.2\dist\typeshed-fallback\stdlib\uuid.pyi [fs read 1ms] (9ms)
[BG(1)]     binding: c:\Users\styagev\.vscode\extensions\ms-python.vscode-pylance-2021.11.2\dist\typeshed-fallback\stdlib\uuid.pyi (2ms)
[BG(1)]     parsing: d:\Projects\flsync\flsync\python\src\flsync\path_mapper.py [fs read 0ms] (79ms)
[BG(1)]     binding: d:\Projects\flsync\flsync\python\src\flsync\path_mapper.py (2ms)
[BG(1)]     parsing: c:\Users\styagev\.vscode\extensions\ms-python.vscode-pylance-2021.11.2\dist\typeshed-fallback\stdlib\enum.pyi [fs read 1ms] (5ms)
[BG(1)]     binding: c:\Users\styagev\.vscode\extensions\ms-python.vscode-pylance-2021.11.2\dist\typeshed-fallback\stdlib\enum.pyi (9ms)
[BG(1)]     parsing: c:\Users\styagev\.vscode\extensions\ms-python.vscode-pylance-2021.11.2\dist\typeshed-fallback\stdlib\types.pyi [fs read 0ms] (35ms)
[BG(1)]     binding: c:\Users\styagev\.vscode\extensions\ms-python.vscode-pylance-2021.11.2\dist\typeshed-fallback\stdlib\types.pyi (10ms)
[BG(1)]     parsing: c:\Users\styagev\.vscode\extensions\ms-python.vscode-pylance-2021.11.2\dist\typeshed-fallback\stdlib\collections\abc.pyi [fs read 1ms] (2ms)
[BG(1)]     binding: c:\Users\styagev\.vscode\extensions\ms-python.vscode-pylance-2021.11.2\dist\typeshed-fallback\stdlib\collections\abc.pyi ...
[BG(1)]       parsing: c:\Users\styagev\.vscode\extensions\ms-python.vscode-pylance-2021.11.2\dist\typeshed-fallback\stdlib\_collections_abc.pyi [fs read 1ms] (3ms)
[BG(1)]       binding: c:\Users\styagev\.vscode\extensions\ms-python.vscode-pylance-2021.11.2\dist\typeshed-fallback\stdlib\_collections_abc.pyi (1ms)
[BG(1)]     binding: c:\Users\styagev\.vscode\extensions\ms-python.vscode-pylance-2021.11.2\dist\typeshed-fallback\stdlib\collections\abc.pyi (4ms)
[BG(1)]   checking: d:\Projects\flsync\flsync\python\src\flsync\rclone.py (985ms)
[BG(1)] analyzing: d:\Projects\flsync\flsync\python\src\flsync\rclone.py (1450ms)
Background analysis message: getDiagnosticsForRange
Background analysis message: resumeAnalysis
Background analysis message: getDiagnosticsForRange
Background analysis message: getDiagnosticsForRange
Background analysis message: getDiagnosticsForRange
Background analysis message: getDiagnosticsForRange
Background analysis message: getDiagnosticsForRange
Background analysis message: getDiagnosticsForRange
Background analysis message: setFileOpened
Background analysis message: markFilesDirty
Background analysis message: analyze
[BG(1)] analyzing: d:\Projects\flsync\flsync\python\src\flsync\rclone.py ...
[BG(1)]   parsing: d:\Projects\flsync\flsync\python\src\flsync\rclone.py (16ms)
[BG(1)]   binding: d:\Projects\flsync\flsync\python\src\flsync\rclone.py (3ms)
[BG(1)]   checking: d:\Projects\flsync\flsync\python\src\flsync\rclone.py (167ms)
[BG(1)] analyzing: d:\Projects\flsync\flsync\python\src\flsync\rclone.py (187ms)
Background analysis message: getDiagnosticsForRange
Background analysis message: resumeAnalysis
Background analysis message: getDiagnosticsForRange
[FG] parsing: d:\Projects\flsync\flsync\python\src\flsync\rclone.py (14ms)
[FG] binding: d:\Projects\flsync\flsync\python\src\flsync\rclone.py (1ms)
Background analysis message: getDiagnosticsForRange
Background analysis message: getDiagnosticsForRange
Background analysis message: getDiagnosticsForRange
Background analysis message: getDiagnosticsForRange
[FG] parsing: c:\Users\styagev\.vscode\extensions\ms-python.vscode-pylance-2021.11.2\dist\typeshed-fallback\stdlib\typing.pyi [fs read 0ms] (34ms)
[FG] binding: c:\Users\styagev\.vscode\extensions\ms-python.vscode-pylance-2021.11.2\dist\typeshed-fallback\stdlib\typing.pyi (13ms)
[FG] parsing: c:\Users\styagev\.vscode\extensions\ms-python.vscode-pylance-2021.11.2\dist\typeshed-fallback\stdlib\_typeshed\__init__.pyi [fs read 1ms] (13ms)
[FG] binding: c:\Users\styagev\.vscode\extensions\ms-python.vscode-pylance-2021.11.2\dist\typeshed-fallback\stdlib\_typeshed\__init__.pyi (1ms)
[FG] parsing: c:\Users\styagev\.vscode\extensions\ms-python.vscode-pylance-2021.11.2\dist\typeshed-fallback\stdlib\typing_extensions.pyi [fs read 0ms] (2ms)
[FG] binding: c:\Users\styagev\.vscode\extensions\ms-python.vscode-pylance-2021.11.2\dist\typeshed-fallback\stdlib\typing_extensions.pyi (1ms)
[FG] parsing: c:\Users\styagev\.vscode\extensions\ms-python.vscode-pylance-2021.11.2\dist\typeshed-fallback\stdlib\abc.pyi [fs read 0ms] (1ms)
[FG] binding: c:\Users\styagev\.vscode\extensions\ms-python.vscode-pylance-2021.11.2\dist\typeshed-fallback\stdlib\abc.pyi (0ms)
[FG] parsing: d:\Projects\flsync\flsync\python\src\flsync\path_mapper.py [fs read 0ms] (3ms)
[FG] binding: d:\Projects\flsync\flsync\python\src\flsync\path_mapper.py (1ms)
[FG] parsing: c:\Users\styagev\.vscode\extensions\ms-python.vscode-pylance-2021.11.2\dist\typeshed-fallback\stdlib\pathlib.pyi [fs read 0ms] (8ms)
[FG] binding: c:\Users\styagev\.vscode\extensions\ms-python.vscode-pylance-2021.11.2\dist\typeshed-fallback\stdlib\pathlib.pyi (3ms)
[FG] parsing: c:\Users\styagev\.vscode\extensions\ms-python.vscode-pylance-2021.11.2\dist\typeshed-fallback\stdlib\os\__init__.pyi [fs read 1ms] (22ms)
[FG] binding: c:\Users\styagev\.vscode\extensions\ms-python.vscode-pylance-2021.11.2\dist\typeshed-fallback\stdlib\os\__init__.pyi (15ms)
[FG] parsing: c:\Users\styagev\.vscode\extensions\ms-python.vscode-pylance-2021.11.2\dist\typeshed-fallback\stdlib\logging\__init__.pyi [fs read 0ms] (21ms)
[FG] binding: c:\Users\styagev\.vscode\extensions\ms-python.vscode-pylance-2021.11.2\dist\typeshed-fallback\stdlib\logging\__init__.pyi (8ms)
Background analysis message: getDiagnosticsForRange
Background analysis message: getDiagnosticsForRange
[FG] parsing: c:\Users\styagev\.vscode\extensions\ms-python.vscode-pylance-2021.11.2\dist\typeshed-fallback\stdlib\tempfile.pyi [fs read 1ms] (7ms)
[FG] binding: c:\Users\styagev\.vscode\extensions\ms-python.vscode-pylance-2021.11.2\dist\typeshed-fallback\stdlib\tempfile.pyi (2ms)
[FG] parsing: c:\Users\styagev\.vscode\extensions\ms-python.vscode-pylance-2021.11.2\dist\typeshed-fallback\stdlib\subprocess.pyi [fs read 1ms] (6ms)
[FG] binding: c:\Users\styagev\.vscode\extensions\ms-python.vscode-pylance-2021.11.2\dist\typeshed-fallback\stdlib\subprocess.pyi (7ms)
[FG] parsing: c:\Users\styagev\.vscode\extensions\ms-python.vscode-pylance-2021.11.2\dist\typeshed-fallback\stdlib\uuid.pyi [fs read 1ms] (4ms)
[FG] binding: c:\Users\styagev\.vscode\extensions\ms-python.vscode-pylance-2021.11.2\dist\typeshed-fallback\stdlib\uuid.pyi (1ms)
Background analysis message: getDiagnosticsForRange
Background analysis message: getDiagnosticsForRange
Background analysis message: getDiagnosticsForRange
Background analysis message: getDiagnosticsForRange
Background analysis message: getDiagnosticsForRange
Background analysis message: getDiagnosticsForRange

Code Snippet / Additional information
IMO it has something to do with the os.name == 'nt' conditional, since changing it to os.name != 'nt' makes the error go away. Also, testing the value of that parameter in runtime produces a results as expected:
>>> new_mount_path
WindowsPath('C:/Users/styagev/AppData/Local/Temp/flsync_union_mnt-46d727')

I was unable to easily create a minimal repro, so I'm attaching the entire file:

rclone.py
""" rclone wrappers """

import logging
import os
from pathlib import Path
import re
import subprocess
import tempfile
from urllib.parse import urlparse
import uuid
from typing import IO, Dict, Match, Optional, cast

from .path_mapper import PeerDef

_LOG = logging.getLogger('flsync')

class _RCloneState():
    def __init__(self) -> None:
        self.mounts = {}                # type: Dict[Path, PeerDef]
        self.mount_path = None          # type: Optional[Path]
        self.remote_mounts_path = None  # type: Optional[Path]

        # the rclone proc that mounts a union of the remotes (with VFS enabled)
        self.remote_union_proc = None   # type: Optional[subprocess.Popen[str]]

        # the rclone proc that mounts a union of the above union together with the local path (without VFS)
        self.union_proc = None          # type: Optional[subprocess.Popen[str]]

    def is_peer_mounted(self, root_path: Path) -> bool:
        """ Checks whether the peer is already mounted """
        return root_path in self.mounts

_RC = _RCloneState()

def mount_peer(peer_def: PeerDef, local_path: Path) -> Path:
    """ Mount the specified peer (if required) """

    # normalize the peer's root path so that D:\Datasets matches D:/Datasets and D:/datasets etc.
    peer_root_path = Path(peer_def['root-path'])

    # if the peer is mounted, return the existing mount path
    if not _RC.is_peer_mounted(peer_root_path):

        mount_uid = str(uuid.uuid4())[-6:]  # UID for the mount to avoid collisions in the temp filesystem

        def _verify_mount_succeeded(rclone_proc: 'subprocess.Popen[str]') -> Optional[Path]:
            """ utility function listening on stdout for rclone's confirmation that mounting succeeded """

            drive_letter = None # type: Optional[Match[str]]
            for out_line in iter(cast(IO[str], rclone_proc.stderr).readline, ''):
                if drive_letter is None:
                    drive_letter = re.search('Assigning drive letter "([A-Za-z]:)"', out_line)
                if re.match('The service .* has been started', out_line) is not None:
                    return None if drive_letter is None else Path(drive_letter.group(1))

            raise RCloneException('Failed to mount remote union')

        if peer_def['type'] != 'local':
            # if the new peer is a remote, re-mount a union of the remotes
            _RC.remote_mounts_path = Path(tempfile.gettempdir()) / f'flsync_remote_mnt-{mount_uid}'
            remote_mount_vfs_cache_pathname = str(_RC.remote_mounts_path) + '-vfs'

            remote_union_args = {
                'RCLONE_UNION_UPSTREAMS': ' '.join(
                    [
                        f'"{_connection_string(mounted_peer_def)}"'
                        for mounted_peer_def in filter(
                            lambda mounted_peer_def: mounted_peer_def['type'] != 'local',
                            _RC.mounts.values())
                    ] +
                    [f'"{_connection_string(peer_def)}"']
                ),
                'RCLONE_UNION_SEARCH_POLICY': 'epall',
                'RCLONE_UNION_ACTION_POLICY': 'epff',
                'RCLONE_UNION_CREATE_POLICY': 'epff'
            }

            if _RC.remote_union_proc is not None:
                _RC.remote_union_proc.terminate()
            _RC.remote_union_proc = subprocess.Popen(
                [
                    'rclone', 'mount', ':union:',
                    str(_RC.remote_mounts_path),
                    '--cache-dir', remote_mount_vfs_cache_pathname,
                    '--vfs-cache-mode', 'full',
                    '--vfs-cache-max-age', '99h',
                    '--read-only'
                ],
                env=remote_union_args,
                universal_newlines=True,
                stdout=subprocess.PIPE,
                stderr=subprocess.PIPE)

            _verify_mount_succeeded(_RC.remote_union_proc)

        _RC.mounts[peer_root_path] = peer_def

        # the primary mount - a union of the previous union and the local paths
        new_mount_path = Path(tempfile.gettempdir()) / f'flsync_union_mnt-{mount_uid}'

        drive_letter = '*' if os.name == 'nt' else str(new_mount_path)

        union_args = {
            'RCLONE_UNION_UPSTREAMS': ' '.join(
                [f'"{local_path}"'] +
                [f'"{local_peer_def["root-path"]}"' for local_peer_def in
                 filter(lambda local_peer_def: local_peer_def['type'] == 'local', _RC.mounts.values())] +
                ([f'"{_RC.remote_mounts_path}"'] if _RC.remote_mounts_path is not None else [])
            ),
            'RCLONE_UNION_SEARCH_POLICY': 'epall',
            'RCLONE_UNION_ACTION_POLICY': 'epff',
            'RCLONE_UNION_CREATE_POLICY': 'epff'
        }

        if _RC.union_proc is not None:
            _RC.union_proc.terminate()

        _RC.union_proc = subprocess.Popen(
            [
                'rclone', 'mount', ':union:',

            ],
            env=union_args,
            universal_newlines=True,
            stdout=subprocess.PIPE,
            stderr=subprocess.PIPE)

        win_net_drive_path = _verify_mount_succeeded(_RC.union_proc)
        _RC.mount_path = win_net_drive_path if os.name == 'nt' else new_mount_path

        _LOG.info('Mounted "%s"', peer_def['root-path'])

    return cast(Path, _RC.mount_path)

class RCloneException(Exception):
    """ Represents an error from rclone """
    pass

def _connection_string(peer_def: PeerDef) -> str:
    try:
        if peer_def['type'] == 'azureblob':
            try:
                # currently we only support container URLs (not nested folders)
                container_name = urlparse(peer_def['url']).path
                if '/' in container_name:
                    raise ValueError('Azure Blob peer must be defined as the entire container, nested folder '
                                     f'"{container_name}" not allowed')

                return (
                    ":azureblob,"
                    f"sas_url=''{peer_def['url']}{peer_def['auth']['sas-query-str']}'':{container_name},"
                    "read_only"
                    )

            except KeyError as ex:
                raise ValueError(f'Malformed azureblob peer definition\n{peer_def}') from ex

        raise ValueError(f'Unknown peer type "{peer_def["type"]}"')
    except KeyError as ex:
        raise ValueError(f'Malformed peer definition\n{peer_def}') from ex

Thanks for the bug report. Here's a minimal, self-contained repro. I'll investigate further.
# pyright: strict

import os

x = 1
y = "" if os.name == "nt" else str(x)

Ahhh I had that in my editor in a new file, in my active multi-folder workspace (configured to 'strict' at the folder level), and the error didn't show up!
Apparently VSCode applies the 'strict' mode only after it's saved in the specific folder (the other folder I have in the workspace does not have 'strict' mode).
I guess this behavior makes sense but it sure drove me a little crazy!
Anyway thanks for ack :)

This will be fixed in the next release.

This issue has been fixed in version 2021.12.0, which we've just released. You can find the changelog here:  CHANGELOG.md


No docker-ce packages in fedora 27 repo

No docker packages available in fedora 27 repo path: https://download.docker.com/linux/fedora/27/x86_64/stable/Packages/
docker repo is enabled, but still I cannot install docker-ce
$ sudo dnf repolist
Last metadata expiration check: 2:35:07 ago on Mon 11 Dec 2017 12:40:12 PM IST.
repo id                                 repo name                                                  status
docker-ce-stable                        Docker CE Stable - x86_64                                       0
*fedora                                 Fedora 27 - x86_64                                         54,801
*rpmfusion-free                         RPM Fusion for Fedora 27 - Free                               574
*rpmfusion-free-updates                 RPM Fusion for Fedora 27 - Free - Updates                      72
*rpmfusion-nonfree                      RPM Fusion for Fedora 27 - Nonfree                            205
*rpmfusion-nonfree-updates              RPM Fusion for Fedora 27 - Nonfree - Updates                    8
*updates                                Fedora 27 - x86_64 - Updates                                6,919

$ sudo dnf -y update
Docker CE Stable - x86_64                                                                                571  B/s | 257  B     00:00
Fedora 27 - x86_64 - Updates                                                                                1.3 MB/s |  12 MB     00:08
Fedora 27 - x86_64                                                                                1.2 MB/s |  58 MB     00:47
RPM Fusion for Fedora 27 - Free - Updates                                                                                121 kB/s | 117 kB     00:00
RPM Fusion for Fedora 27 - Free                                                                                729 kB/s | 717 kB     00:00
RPM Fusion for Fedora 27 - Nonfree - Updates                                                                                16 kB/s | 8.3 kB     00:00
RPM Fusion for Fedora 27 - Nonfree                                                                                275 kB/s | 163 kB     00:00
Last metadata expiration check: 0:00:00 ago on Mon 11 Dec 2017 03:18:11 PM IST.
Dependencies resolved.
Nothing to do.
Complete!

$ sudo dnf install docker-ce
Last metadata expiration check: 0:00:19 ago on Mon 11 Dec 2017 03:18:11 PM IST.
No match for argument: docker-ce
Error: Unable to find a match

File: engine/installation/index.md, CC @mistyhacks

Did you notice that Fedora 27 is not yet listed in https://docs.docker.com/engine/installation/linux/docker-ce/fedora/#os-requirements ? :)

@mistyhacks why is the newest fedora not listed there? While the fedora that is "end of life" listed there?
Fedora 24 is already end of life and Fedora 25 will be end of life by tomorrow: https://fedoramagazine.org/fedora-25-end-life/

We currently can't build for F27 because of https://github.com/rpm-software-management/rpm/issues/367.
I created #5488 to remove F24 and add F26, since we do have builds for it for 17.09 CE and higher.

See also #5489

Thanks @mistyhacks appreciate all the efforts! :+1:


Fix envmod

module files come in different flavours: with or without system dependencies and particularly build with different compilers. Hence, to avoid conflicts the need to purge all previously loaded environment modules for local rules or to clean polluted environments for cluster jobscripts arises.
This fix should solve it.

@cmeesters the {cmd} was missing, so it did not execute anything. I have fixed this in a slightly different syntax now in commit 07cc089.


Make new stat regex backwards compatible (#52031)

Fixes #52161

@keithmattix: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

release-notes_istio_release-1.23
a2e2a2500d312cf8893343e036a8d774a73208b1
link
true
/test release-notes

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-sigs/prow repository. I understand the commands that are listed here.

/test release-notes

@keithmattix: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

unit-tests-arm64_istio_release-1.23
a2e2a2500d312cf8893343e036a8d774a73208b1
link
unknown
/test unit-tests-arm64

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-sigs/prow repository. I understand the commands that are listed here.

/restest

/retest