Suggestion: use smaller profile picture

Hey there, I reached your website https://vivekn.dev/ from your math app linked on hacker news and I noticed your profile picture was a bit slow to load.
Looking at https://github.com/viveknathani/vivekn.dev/blob/4003a8184b013ebb31e09f22db0c4d93f1589651/src/static/index.html#L26 I see that you're loading a 1.5mb picture.
On desktop and fast networks it may not be noticeable sometimes, but for mobile and specially on slow and/or reduced data plans it may be problematic for visitors.
Also, depending on the traffic and provider, it may get cheaper to serve smaller images since you'll use less bandwidth.
I think that for the circular avatar use case you can get away with a much smaller image (around 100k or less), and maybe if you want people to have access to the original picture, the avatar could be a link o the original picture.
Cheers.

hi @ivanalejandro0!
thanks for pointing this out in a detailed manner, i appreciate your concern. 🙌
i have pushed a fix for this. the size of the image now is ~188KB.
marking this issue as closed now.
cheers!


Item conduits causing Tick Loop

Issue Description:
We just installed EnderIO and we have been getting server lag. When they chunk load, the server crashes. Upon looking at the crash report, it details that an item conduit is casuing a tick loop.

Affected Versions (Do not use "latest"):

EnderIO: <IP_ADDRESS>
EnderCore: <IP_ADDRESS>
Minecraft: 1.10.2
Forge: 1.10.2  2096

Your most recent log file where the issue was present:
crash-2016-10-23_22.49.33-server.txt
[pastebin/gist/etc link here]

This is caused by sponge.


Bump node version to 18.16.0

Description
Bumped Node version to 18.16.0. All steps:

Bump nvmrc version to 18.16.0
Bump version of fork-ts-checker-webpack-plugin, otherwise build fails due to RPC issues
Change webpack to patched version that supports Node 18 with hash module changes

Check List

[ ] New functionality includes testing.
[ ] New functionality has been documented.
[x] All tests pass

[x] yarn lint
[x] yarn test-unit

[x] Update CHANGELOG.md
[x] Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Should node:10 be updated in scripts/deploy?

Build succeeded and Build Docs failed, which is to be expected.


Issue with top-bar and slick carousel

I am using Foundation 5, a sticky scrollbar and Owl Carousel (I have tried using Slick carousel and the result is the same).
The issue I'm experiencing is that whenever I scroll up/down and the top bar goes over the carousel, the whole page stutters and the scroll bumps and stops shorter than its expected trajectory.
I have tried a lot of solutions including applying z-index and -webkit-transform: translateZ(0) rules to the carousel with no success.
This problem doesn't seem to exist in Firefox or Edge or at least is not as obvious.
Any ideas?
How can we reproduce this bug?
Scroll up and down the page. Especially scroll up. Also, carousel would flicker when scrolling down if there is margin between carousel and topbar
What did you expect to happen?
What happened instead?
The page lags/scroll stutters.
Test case:

Site I'm working on

What browser/operating system does this appear the worst on? I tried in Chrome and Safari on Mac and couldn't reproduce.

Windows 7+, Chrome. You have to scroll up fast and steady. No issues with IE and Firefox.

Resolved in the following way:
body { -webkit-transform: translate3d(0, 0, 0);


Prepare for vfkit 0.5.1 release

Bug fix release to get a fix for the disk corruption issue podman people have been having.
Then we'll work on a 0.6.0 release with all the pending PRs.

LGTM

/approve


Is velocyto available for single-nuclei data?

I am trying to analyse RNA-velocity for single-nuclei RNA sequencing data from 10X platform. I am not sure in detail how it calculates the unspliced/spliced rate when I run the command 'velocyto run10X', especially about whether it considers the percentage of reads containing unspliced intronic sequences. And it was reported that the percentage varies among platforms in the paper 'RNA velocity of single cells'.  Then I am wondering if that percentage differs between cell soma and nuclei beyond platforms. Can you kindly tell me some information about that?

Agreed that this would be a nice feature to have although understandably a potentially difficult one to support for nuclei data. Any updates on whether there will be support of RNA velocity analysis for single-nuclei?

 Hi, thank you for replying. Firstly I checked the unspliced proportion and found it was about 66%, which I assume is higher than that seen in single 'cell' cases. Although I have not checked into Issues in scvelo platform, some also reported that single 'nuclei' data had ~70% unspliced portions.
 And when I applied the dynamical-mode velocity analysis available in the scvelo package, it successfully worked and found there were reasonable directions like immature cells-> mature cells or healthy cells -> disease cells. Other reseachers posted issues about the oppsite directions to their knowledge when used the dynamical-mode velocity analysis in the scvelo platform, but I did not see the erroneous results like that.
So I am understanding single 'nuclei' data can be applied to velocity analysis, but I am still wondering whether the mathematical model including RNA degradation parameters can be straightly applied to 'nuclei' data because the degradation event should occur in the cell soma and this should not be captured in case of 'nuclei' data....


Add 'gltf2-model-next' or similar.

Would be helpful to have a quick way of testing the latest (unstable) version of GLTF2Loader.

Done: https://github.com/donmccurdy/aframe-extras/commit/68eac470b532f588733e480968ce4b7dae3e7d51


Use Alluxio Metadata to Avoid Eventual Consistency Issues with Under Storage

Is your feature request related to a problem? Please describe.
Alluxio metadata is strongly consistent. If we make the assumption that there are no out of band operations, Alluxio should retry any inconsistencies between its metadata and the underlying storage, if that storage can be eventually consistent (ie. S3). This will avoid propagating errors to the user.
One of the error is:
2018-10-13 05:10:52,410 ERROR ObjectUnderFileSystem - Unable to rename s3a://xxxxx/_temporary/1/task_1539407183469_0001_m_000005/part-m-00005 to s3a://xxxxx/Input/part-m-00005 because source does not exist or is a directory.
2018-10-13 05:10:52,411 WARN  FileSystemMasterClientServiceHandler - Exit (Error): Rename: srcPath=/_temporary/1/task_1539407183469_0001_m_000005/part-m-000055, dstPath=/Input/part-m-00005 options=RenameTOptions(commonOptions:FileSystemMasterCommonTOptions(syncIntervalMs:-1)), Error=java.io.IOException: Failed to rename s3a://xxxxx/_temporary/1/task_1539407183469_0001_m_000005/part-m-00005 to s3a://xxxxx/Input/part-m-00005 in the under file system

Describe the solution you'd like

write-then-read (storages:S3): already fixed.
write-then-list (storages: S3, Swift): will retry listing operations in s3 and swift under system.
write-then-change metadata (storage:S3, Swift): retry listing operation in s3 and swift will also help solve the write-then-rename operation.
delete-then-read/list/change metadata (Alluxio metadata will not allow, do not consisder)
Other eventual consistency issues that may consider in the future:
(1) write-then-delete
(2) revoking access from resources (storage GCS)
(3) cache related eventual consistency issue (GCS cache-control, NFS weak cache consistency)
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.

Additional context

Done


Export to WAV

Added a method to export to WAV files. Only for OSX.

I've updated the code with the suggestions you made.


Change output device for running AudioContext

This is the second of three PRs for https://github.com/orottier/web-audio-api-rs/issues/216

#227
Change output device for running AudioContext
Create AudioContext without output

You will notice a severe lack of tests for this complicated feature. That is because the functionality is only exposed in online AudioContext which need an actual audio backend. For now, because that will be changed in PR number 3.
You can test it with cargo run --release --example sink_id but notice that cpal only lists your default audio output, so you won't be able to switch from headphones to builtin speakers (on OSX). I added a virtual passthrough device to use for testing. Sad though. It is not really testable with backend cubeb because it suffers from segfaults when closing a stream. Known issue #187  :(

That's quite a thing, I'm really not sure I understand everything (I'm pretty I don't actually :), so maybe my comments are not very relevant.
Actually it makes me think it would be quite nice to have some graph of who lives where in terms of threads, I'm always a bit lost in this part of the code.
In any case, the example seems to work on my side switching between some virtual device and real output

Actually it makes me think it would be quite nice to have some graph of who lives where in terms of threads, I'm always a bit lost in this part of the code.

Yes, I created a new issue for this: #235


.?clear doesn't work

📢 Bug reported by Dadi<PHONE_NUMBER>23161090)
What is the title of your bugreport?
.?clear doesn't work
How can you reproduce the bug?

Write some messages
?clear 5

Which result would normally have to be?
It should work, but currently you get an error
Comments:
❗✅ Dadi: could be reproduced (important)

should be fixed with the last commit


feat: add slice method to array/fixed-endian-factory

Resolves #3154 .
Description
This pull request:

adds slice method to array/fixed-endian-factory
adds the respective benchmarks and tests
updates README

Related Issues

Does this pull request have any related issues?

This pull request:

resolves #3154

Questions

Any questions for reviewers of this pull request?

No.
Other

Any other information relevant to this pull request? This may include screenshots, references, and/or implementation notes.

No.
Checklist

Please ensure the following tasks are completed before submitting this pull request.

[x] Read, understood, and followed the contributing guidelines

@stdlib-js/reviewers

kindly review this PR!!

/stdlib merge

/stdlib lint-autofix

CI failures will need to be resolved before this PR can receive further review. Cheers!

@kgryte please review PR#3269 i have made the necessary changes told by you above


Add missing semicolons

While the regular sass is fine without them, sassc-rails which uses
libsass isn't.

Can't reproduce this on the computer I'm on now. The change won't hurt anything, but maybe it isn't needed. Merge or just close as you see fit.

I'm seeing the same error, when using libsass

Ah, yeah, I don't know why I stopped seeing it, maybe ended up with compiled version cached or something. I guess it is a real error.


⚠ Bofrost.si has degraded performance

In 51515ec, Bofrost.si (https://www.bofrost.si) experienced degraded performance:

HTTP code: 200
Response time: 4678 ms

Resolved: Bofrost.si performance has improved in 69b8ffe after 6 minutes.


Create docs copy for 5.2.3

Development has already been started on Open GEE 5.2.3. So, we need a copy of the docs for the 5.2.3 development cycle. Complete sections 11 and 4 in the Release Process for Open GEE 5.2.3 development. In section 4, just create a placeholder page for the 5.2.3 release notes. These will be updated as development occurs.

Done is #768


StatusBar.setBarStyle is undefined ( index.js @36:0 )

I followed your Readme for add NavigationBar but i have this error...

That should be fixed already, try to update plugin to the latest version, please


RN FASA update

-Update fasa to use avc version file now, also fixed repo link and
changed TR to RP.

It says this passed but can someone double check the syntax and make sure the file has no errors please.

The syntax looks fine, and I don't think you need to change the epoch.
However, as it is there are no game version constraints, so the current version would be considered compatible with all versions of KSP. Is that intentional?
Also it would be nice to leave the "homepage" property set to the forum thread. A $kref pointing at GitHub will pull in the repo page as the "repository" property automatically:
Resources:
- homepage: https://github.com/KSP-RO/FASA-RO
- repository: https://github.com/KSP-RO/FASA-RO

The forum thread is dead and contains a version of the mod that breaks ksp. I don't want to link to a thread that will cause people to break their game if they decide to download something from there.
The game version constraints are in the .version file same as with all my other mods.

Ah, OK, never mind the forum thread then.
I just checked the download, and there is no .version file in it. That's probably why it's not picking up the game versions. If this isn't compatible with all game versions, then we should resolve that before merging this pull request.

It is compatible with all versions since they changed the file structure when mods used to be dae files, that was somewhere back before .18. And no it does not contain the version file yet because I was waiting for this to merge before releasing a new version. If I release that new version first, then you merge this, that version won't be indexed. I'll then need to release another new version AGAIN just to get it indexed, so i'll end up with 2 identical versions.

I'm not following that. Why wouldn't the new version be indexed?

I mean if I make a new release right now with a new version file in it, then after that you merge this. That previous release will not be indexed, the same way a mod that is marked as compatible with a certain version of ksp before that version comes out won't be indexed until you make a NEW release after that version of ksp drops.
It's kind of hard to explain, but all of my mods are marked as compatible with up to version 1.3.99 of ksp, so you'd assume that when 1.3.1 dropped for instance, that they would automatically be indexed for that version, but they aren't and only will show up if I make a new release again and that new release is indexed. This is the same situation. That's why I wanted to have this merged right before I made the release.

OK, we'll do it your way. This will mess up the metadata for v7.2, but hopefully that won't matter.

Why would it mess up the 7.2 metadata? It shouldn't reindex that release again right? Anyway I'm going to make a 7.3 release right now with an updated version file.

The latest release is always re-indexed after a netkan is changed:
https://github.com/KSP-CKAN/CKAN-meta/commit/40f0632a3af0e1260094aa7fcdc2e206a27d0bfa

That'd be the webhooks that fire off when commits are submitted to the NetKAN repo.


Use ujson if its available

If you have it, might as well monkey patch botocore.vendored.requests to use it too, but thats out of scope.
https://github.com/kennethreitz/requests/issues/1595

https://github.com/jlafon/PynamoDB/blob/33eb91a40ee252525871fa1ce0e47cf6b002ad17/pynamodb/connection/base.py#L238

That is where the monkey patching mentioned above comes in.

we don't need to patch though, why not call json.loads(request.text)?

+1 from me

@jlafon any thoughts

Thoughts on merging this in?  I'm happy to update the branch.  We've been using this in production for a while.

@joshowen definitely. let's take advantage of the new global config introduced in 1.6.0 and allow you to globally patch in whatever json parser you want, defaulting to the built-in json.
let me know if you have any questions.


[20.09] epkowa: add epson perfection v600 and v37/v370

Backport #116812 (cherry picked from commit 76b34118a911102a887401c059b10ecaa4af3326)
Motivation for this change
Add Epson Perfection V600 and V37/V370 scanner drivers to epkowa
Things done
Testing of Epson V370 was done previously as part of #107584.
Testing of Epson V600 was done on a 20.09 system using the following in /etc/nixos/configuration.nix:
nix.useSandbox = true;
nixpkgs.overlays = [
    (self: super: {
        epkowa = super.callPackage /path/to/my/nixpkgs/pkgs/misc/drivers/epkowa/default.nix {};
    })
];

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[ ] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 117124 at 958c29a3 run on aarch64-linux 1

1 package failed to build (new failures):

epkowa

Apparently Epson recently replaced their iscan-data tarball on their server at https://support.epson.net/linux/src/scanner/iscan/
old file: iscan-data_1.39.1-2.tar.gz
new file: iscan-data_1.39.2-1.tar.gz
As far as I can tell this happened in the last few days between my pull request #116812 to update master and this pull request #117124 to backport to 20.09.
Commit 9ea85b3 fixes this to use the new tarball on this 20.09 pull request.  I'm wondering whether it is better practice to close/cancel this 20.09 pull request, fix this on master, and then resubmit a backport, or fix it separately on both branches (20.09 and master)?

The build failure from the bot above must be due to a temporary server issue at archive.org as I just checked now and it's working again.

last time it wasn't working at all because archive.org regenerates archives on the fly and they don't actually have the right hash. At least that was what happened last time.
Can you fix the tarball on master first, and open a backport then ?

Now that I think of it, replacing fetchurl by fetchzip should make it so archive.org and the original location have the same hash

Hmm, it looks like the hash on archive.org is actually correct, and it was indeed a transient failure.
Regarding the original PR:
I'm a bit reluctant to backport something that I cannot test thoroughly (because of the hardware), which is not a bugfix and was merged in unstable only a few days ago. Can this wait, say, at least 2 weeks ?

@symphorien that sounds reasonable.  I will close this pull request and instead do a pull request to update master with the changes in 9ea85b3.  I will also wait at least two weeks before submitting a backport to 20.09.  Thank you!


Feed view shouldn't include pins.

Currently the feed shows your pins in it. Your pins shouldn't go into the feed because feed is people you are following.

Ah good catch. Ill get to that asap
On Tuesday, November 3, 2015, afull004<EMAIL_ADDRESS>wrote:

Currently the feed shows your pins in it. Your pins shouldn't go into the
feed because feed is people you are following.
—
Reply to this email directly or view it on GitHub
https://github.com/btstevenson/UCRInterest/issues/4.


Feature: use NavLink to avoid reloading

Fixes #324
Used NavLinks to avoid refreshing the website while changing the routes.
Improved efficiency and load time.

This branch has conflicts resolve it @kailashchoudhary11

Can you add screenshots of the website changes because some styles were applied to the anchor tags?

Can you add screenshots of the website changes because some styles were applied to the anchor tags?

Sure the style is same as before. Since the NavLink is built over a tag itself


Upgrade the pjit guide to jax.jit

Fixes #2755:

Use jax.jit in place of pjit, and adjust explanations
Use jax.sharding instead of PartitionSpec wherever possible, in light of JAX's deprecation plan
Showcase how to use the API on existed layers (surprising that it wasn't showcased earlier...)

Codecov Report

Merging #3016 (34e18a5) into main (efe3d57) will decrease coverage by 0.08%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             main    #3016      +/-   ##
==========================================
- Coverage   81.97%   81.89%   -0.08%
==========================================
  Files          55       55
  Lines        6002     5999       -3
==========================================
- Hits         4920     4913       -7
- Misses       1082     1086       +4

see 4 files with indirect coverage changes
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


Environment Variables don't update.

Environment

Operating System: Windows_NT
Node Version:     v18.14.0
Nuxt Version:     3.1.2
Nitro Version:    2.1.1
Package Manager<EMAIL_ADDRESS>Builder:          vite
User Config:      css, build, modules, imports, runtimeConfig
Runtime Modules<EMAIL_ADDRESS>Build Modules:    -

Reproduction
https://stackblitz.com/edit/github-twwcda?file=.env
Describe the bug
So i have an .env file. I export the variables via
    runtimeConfig: {
        public: {
          TEST: process.env.TEST
      }}

The variables work, and when I change the .env files content i get this message
.env updated. Restarting nuxt...
Nuxt restarts, rebuilds but the variable inside $config.TEST does not get updated.

Yeah, same here.

Let's track in https://github.com/nuxt/nuxt/issues/15040.


The RETRY tip remains after a success retry.

Explain the problem here ...
After the recent update, there's a bug: when use PlugUpdate to update the plugins and some of them fail, the tip "Press 'R' to retry, and press 'D' to..." appears as before, but if press R to retry and success, the tip remains "Press 'R' to retry, and press 'D' to ...", while before the update, the tip is only "Press 'D' to ...".

Type:

[x] Bug
[ ] Enhancement
[ ] Feature Request
[ ] Question

OS:

[ ] All/Other
[x] Linux
[ ] OS X
[x] Windows

Vim:

[x] Terminal Vim
[x] GVim
[ ] Neovim

Thanks, I'll look into it.

Should be fixed now, thanks for the report.

Sorry for the delayed reply, because till today I met the retry case.
That commit fixed that bug, but a new one is out - Now, after the retry case and then success, the 'D' message lost. (as before a 'D' message should be shown)

Thanks for letting me know, but I don't see it as a bug. R will start a new installer and it does not remember the result of the previous installer.


support Scala 2.12.0-M2

I just pushed 0.6.1 which should support 2.12.0-M2. Let's close this issue once we've confirmed that resolving works and publishing was successful.

Thanks for your quick response!


Update hyper to v1.0.x

This is blocking https://github.com/denoland/deno/issues/21578

published 0.6


Include new interactive visualizations

Summary
Add new interactive visualizations for Jupyter, including:

Bloch sphere
Cities
Hinton
Histogram
Paulivec
Qsphere

Details and comments
Closes #718

Thanks @filemaster. These look really cool.
I tried them, and below are some comments. Can you take a look and let me know what you think?

The axis font on the city map is really small and hard to read.
from qiskit import *
from qiskit.tools.visualization.interactive import *
q = QuantumRegister(1)
c = ClassicalRegister(1)
circ = QuantumCircuit(q, c)
circ.x(q[0])
circ.h(q[0])
result = execute(circ, 'local_statevector_simulator').result()

import numpy as np
v = result.get_statevector()
iplot_cities(np.outer(v, v))

The histogram does not display for me, it just shows an empty axis. The same code works for non-interactive plot_histogram function.
from qiskit import *
from qiskit.tools.visualization.interactive import *
q = QuantumRegister(1)
c = ClassicalRegister(1)
circ = QuantumCircuit(q, c)
circ.x(q[0])
circ.h(q[0])
circ.measure(q, c)
result = execute(circ, 'local_qasm_simulator').result()

counts = result.get_counts()
iplot_histogram(counts)

The iplot_paulivec function does not seem to work with the same density matrix input as other functions. In the city example above, if I replace the last line with iplot_paulivec(np.outer(v,v)) I get:
---------------------------------------------------------------------------
IndexError                                Traceback (most recent call last)
<ipython-input-9-2444bcf66697> in <module>()
      1 import numpy as np
      2 v = result.get_statevector()
----> 3 iplot_paulivec(np.outer(v,v))

~/Desktop/ajavadia-terra/qiskit/tools/visualization/interactive/_iplot_paulivec.py in iplot_paulivec(executions_results, options)
     72     data_to_plot = []
     73     for execution in executions_results:
---> 74         rho_data = process_data(execution['data'])
     75         rho_legend = execution['name']
     76         data_to_plot.append(dict(

IndexError: only integers, slices (`:`), ellipsis (`...`), numpy.newaxis (`None`) and integer or boolean arrays are valid indices

On the Qsphere, it seems like the state is displayed incorrectly. It just shows state = |1> everywhere.
There are several things going on in the picture below.
1- The state I am pointing to should be |0000>, not |1>.
2- Two of the green lines have not faded away when I try to focus on the north pole.

Finally, it would be nice to have a similar structure to the functions as the non-interactive visualizations. There, you will see a function plot_state, which takes a method argument and then plots the state (density matrix rho) using any of city, paulivec, qsphere, bloch.
This way, we have two simple user-facing functions: iplot_state and iplot_histogram. The first one draws a state (using any of the 4 methods).

Thanks @filemaster for the PR and @ajavadia for the review! Looking forward to having the neat interactive visualizations in place.
Please note as well that for this particular PR, some decisions (most of them visual, but also some of them arquitectural) involve not only terra itself, but also the design team and other forces at play. In particular, I think having the same signature compared to the static equivalents was desired (but not critical, as for example histogram has new functionality, now accepting several series), but I'm unsure about how desirable it was to replicate plot_state() - @ismaelfaro , can you take a look at some point?

@ajavadia, we already added the necessary docstring to understand how to use the functions.
About the histogram, the new function can show different execution results in the same graph, so an input array of data is required. Following your example, it must look like:
from qiskit import *
from qiskit.tools.visualization.interactive import *
q = QuantumRegister(1)
c = ClassicalRegister(1)
circ = QuantumCircuit(q, c)
circ.x(q[0])
circ.h(q[0])
circ.measure(q, c)
result = execute(circ, 'local_qasm_simulator').result()

counts = result.get_counts()
iplot_histogram([{'data': counts}])

We know it is a bit more complex than the older version, but the real advantage is the possibility of compare results from different executions:
iplot_histogram([{'data': counts, 'name':'Job1'},
                 {'data': counts, 'name':'Job2'},
                 {'data': counts, 'name':'Job3', 'device':'simulated'},
                 {'data': counts, 'name':'Job4', 'device':'simulated'},
                ])

before we merge we should make sure it is the same as the static plots and the static plots are also the same as these. I would also request that the plot defaults to interactive and then the non-interactive is made if the user does not have the extensions.

About the iplot_paulivec, the input is not the density matrix. The input for paulivec is similar to the histogram, an array of data objects. Is it possible you were trying to plot a Hinton? Hinton is like the cities but using 2D instead 3D, both of them use the density matrix as an input.

the puali_vec needs to take in the state matrix.

i will say the plots look awesome. Great job

@filemaster the paulivec should have the same input as the other state visualization methods (density matrix). This is the case in non-interactive visualizations as well.
from qiskit import *
from qiskit.tools.visualization import *
from qiskit.tools.visualization.interactive import *
q = QuantumRegister(2)
c = ClassicalRegister(2)
circ = QuantumCircuit(q, c)
circ.h(q)
result = execute(circ, 'local_statevector_simulator').result()

import numpy as np
v = result.get_statevector()
plot_state(np.outer(v,v), 'paulivec')

That's also why i suggested a wrapper method plot_state, which shows that these all plot the same thing but in different ways.

@ajavadia , @jaygambetta we are making the required changes to use the density matrix with paulivec visualization and the other issues. Thanks for your comments.

All issues were fixed. We added a new function called iplot_state()similar to the non interactive plot_state().
iplot_state() supports next plotting methods:

bloch
city
hinton
paulivec
qsphere

@filemaster thank you. I made some tiny changes mostly in the comments.
One comment about the histogram: what does the rest option do?
If you look at the static plotter, there is an option number_to_keep. It will keep the n most frequent bars, and will group the rest. This is because some plots can be really long.
from qiskit import *
from qiskit.tools.visualization import *
from qiskit.tools.visualization.interactive import *
q = QuantumRegister(5)
c = ClassicalRegister(5)
circ = QuantumCircuit(q, c)
circ.h(q)
circ.measure(q,c)
result = execute(circ, 'local_qasm_simulator').result()
c = result.get_counts()
plot_histogram(c, number_to_keep=3)

(without number to keep)

(with number to keep)

I thought the rest option in iplot_histogram would do the same, but it does not. It apparently just groups the ones that are exactly zero. Can we add the number_to_keep option, since that is more useful?

The rest option does exactly what you thought @ajavadia , it groups just the ones that are zero. We will work in this 'new' behaviour.

Thanks you @Tansito and @filemaster. These look great.
I'll follow up with another issue to think about how to make these the default when qiskit is run in Jupyter, and to see if we can make the plot_histogram and iplot_histogram more consistent.


Please correct the animation of the knives,I will be very happy, well, all other users

Can you please fix the animation of the knives that are on the video (3 links below). Is it possible to make the animations of the knives as in the onetap v3 cheat? Because there are no knife animation lags at all and there are all the animations of each knife. More Tramp Knife and Paracord Knife need to be tweaked to Osiris.
https://oxy.st/d/cfhd
https://oxy.st/d/dfhd
https://oxy.st/d/efhd

Why are you sending weird Russian scam websites.

Why are you sending weird Russian scam websites.

Why are you sending weird Russian scam websites.

they're not scam websites although i'm not sure why he didn't upload to imgur or something

Why are you sending weird Russian scam websites.

they're not scam websites although i'm not sure why he didn't upload to imgur or something


Teleop Turning

I have no idea why, but when I use theses kinematics values it works. I copied them from something else I did, and I'm not sure what is different about them (besides the small nudge in value), but it does make it turn.
const frc::Translation2d frontLeftPose  = { 0.303_m, -0.299_m},
                         frontRightPose = { 0.303_m,  0.299_m},
                         rearLeftPose   = {-0.303_m, -0.299_m},
                         rearRightPose  = {-0.303_m,  0.299_m,};

Yay! I wonder if the values are modified in some other way and making them equal in magnitude (although different in sign) is what makes them sort of balance each other out.

I'll update this locally tomorrow and PR to main for the command system setup.


Interfaces ISequentialStream, IStream, and IWICStream appear to be declared incorrectly

Using the stream types ISequentialStream, IStream, and IWICStream yields some unexpected results. For example, calling IStream.Commit(STGC_DEFAULT) sometimes returns a "not implemented" error, which seems rather unlikely; especially since there are code examples on MSDN calling this method on a WIC stream (e.g. here). So probably our interfaces aren't declared correctly.
One possible error source are the duplicate [local] and [remote] methods in the stream interfaces. Not clear whether they both need to be present in the .NET interfaces, or just one each.
One possible solution would be to compare our declaration with that of the pre-defined type System.Runtime.InteropServices.ComTypes.IStream, and see whether there are any differences… or just switch over to that type.

I did some checks:

I looked at the declarations of both ISequentialStream and IStream using the OLE / COM Object Viewer (oleview.exe) utility. They appear to be reasonably identical to our interface declarations.

I wrote a C++ test program (using Microsoft's WIC header files) that calls IWICStream::SetSize and IWICStream::Commit. These calls return a E_NOTIMPL (HRESULT 0x80004001) error as well.

Apparently, our interface declarations are not misbehaving after all; it is simply that IWICStream does not implement these methods. I am closing this issue for now.


Jest warning: use String.prototype.padStart()

🐛 Bug Report

When using jest in lerna/yarn workspaces projects, I am receiving this warning chain:
jest > jest-cli > jest-config > jest-environment-jsdom > jsdom ><EMAIL_ADDRESS>use String.prototype.padStart()

To Reproduce
Steps to reproduce the behavior:
Clone the project
git clone git@github.com:imbroisi/react-monorepo.git

then
cd react-monorepo
yarn

and watch the warning messages:
warning workspace-aggregator-f4f2e609-a5b0-4283-afd9-18e4b6de54b1 > shared > jest > jest-cli > jest-config > jest-environment-jsdom > jsdom ><EMAIL_ADDRESS>use String.prototype.padStart()

Expected behavior

Link to repl or repo (highly encouraged)
https://github.com/imbroisi/react-monorepo

envinfo

Please file this issue against jsdom, it's their dependency.

Thank you!

Jsdom have upgraded, I think it's included in jest 25

Warning still appears
root@container_id:/var/www/app# npm install jest --save-dev
npm WARN deprecated<EMAIL_ADDRESS>use String.prototype.padStart()

  "devDependencies": {
    "jest": "^25.1.0",
  },

Then you have it somewhere else, as a clean install right now just warns about request being deprecated


Issue with k8s.io/docs/concepts/services-networking/service_backup_16221/

This is a Bug Report

There are multiple backup files for service that are listed as service links in the sidebar.

Problem:
This creates confusion on what is the true link
Proposed Solution:
Remove all backup solutions and leave only one service.md
Page to Update:
https://kubernetes.io/docs/concepts/services-networking/service_backup_16221/

This PR addresses that https://github.com/kubernetes/website/pull/15008


Redirect when required sections are incomplete

What is the context of this PR?
It needs to be possible to define sections which must be completed prior to the hub being accessible.
How to review
Check if you agree with the approach and the tests cover all new behaviour.

 Disable hub until sections are completed (M)


GH-41608: [C++][Python] Extends the add_key_value to parquet::arrow and PyArrow

Rationale for this change

The previous pr ( https://github.com/apache/arrow/pull/34889 ) add a AddKeyValueMetadata to FileWriter. And now we should export it to Parquet Arrow and Python API.
What changes are included in this PR?

Add AddKeyValueMetadata in parquet::arrow
Add add_key_value_metadata in pyarrow
testing

Are these changes tested?

Yes
Are there any user-facing changes?
New api allowing add key-value metadata to Parquet file

GitHub Issue: #41608

I've no idea why R language CI failed

@AlenkaF @jorisvandenbossche @pitrou Would you mind take a look?

Migrate to test_parquet_writer.py now. @pitrou would you mind revisit C++ part or merge this?

@pitrou comment fixed

@mapleFU Feel free to merge if CI is fine.

CI failed is unrelated, merge


Various fixes for pl.seq

There are a couple of corner cases where seq.reduce and seq.skip doesn't work as expected that this PR addresses.
I've also modified seq.map and seq.reduce to just take the iter as the first argument. This allows easier chaining without having to do more function wrapping over it to get the parameter ordering right. From looking at the code I couldn't find any reason why it wasn't done this way to start with. It also makes the parameter ordering more consistent with other functional operators like seq.filter.

Changes Unknown when pulling 9be1831091ac058c2cf84f4b2455b5d4a0d3c6b3 on greatwolf:master into ** on stevedonovan:master**.

@stevedonovan I'm not sure about changing order of arguments like that in a minor versions but I don't know how strict you want to be in following semver. @greatwolf if you could split out other changes I could merge them faster.

What's the best way to do this? Should I separate out the interface breaking changes into one branch and bug fixes in another branch and resubmit them as 2 different PR?

@greatwolf yes, please do that. You can reuse this PR once by force pushing.


handle dropped api requests

This cancels API requests that have been dropped/cancelled by a client before receiving a response.
https://app.asana.com/0/198587529699250/239832897034379

Tested by clicking around a bunch really quick (which in the past would cause the error).  LGTM.
I'll look at fixing the merge conflicts.

Rebased as https://github.com/lbryio/lbry/pull/394; closing this.


Posec3d

Dose mmrazor support mmaction2(posec3d)?

Sorry, mmaction2 is not supported in the current version. Welcome to contribute the feature to mmrazor, or waiting for the support in the furture.


How to convert a model Property to an Attribute in XML based req/res spring boot application?

Please take the time to search the repository, if your question has already been asked or answered.

[ ] What version of the library are you using? Is it the latest version? The latest released version is

What kind of issue is this?

[x] Question. Is this a question about how to do a certain thing?

[ ] Bug report. If you’ve found a bug, spend the time to write a failing test. Bugs with tests or
steps to reproduce get fixed faster. Here’s an example: https://gist.github.com/swankjesse/6608b4713ad80988cdc9

[ ] spring xml/java config that is relevant
[ ] springfox specific configuration if it makes sense
[ ] include any output you've received; logs, json snippets etc.; and what the expected output should be
[ ] if you have a repo that demonstrates the issue for bonus points! See this example

[ ] Feature Request. Start by telling us what problem you’re trying to solve. Often a solution
already exists! Don’t send pull requests to implement new features without first getting our
support. Sometimes we leave features out on purpose to keep the project small.

Please do consider starring this repository if you do like this project and find it useful.

In my Spring boot application which has xml base req/res. I am using dependencies

io.springfox
springfox-swagger2
2.6.1
compile

	<dependency>
		<groupId>io.springfox</groupId>
		<artifactId>springfox-swagger-ui</artifactId>
		<version>2.6.1</version>
		<scope>compile</scope>
	</dependency>

and I have to generate the below request structure in swagger api:

But its generating as

string
string
string
string

How to create the attribute "recordId" of   tag instead of a property in my model and which annotation and property i have to use here.
public class AddressInfoType {
@ApiModelProperty(name = "This field should have minimum first line address information to validate it from Code1 API", position = 1  )
protected String addressKey;
@XmlElement(required = true)
protected String address;
@ApiModelProperty(name = "This represents 5 digits zip code of an address")
@XmlElement(required = true)
protected String zip;
@ApiModelProperty(name = "This is number which represents address index in request")
@XmlAttribute(name = "recordId")
protected String recordId;

Thanks,

Thanks for reporting

This should be fixed in 2.8.0. Closing this as fixed. If not please report back


Idea: Use the OS Feature trap to catch SIGINTs when running tests to force cleanup

Recently learned about traps and catching differnt signals and have been implementing them wherever I can in my BASH scripts.
After reading https://github.com/hashicorp/terraform-aws-vault/blob/master/test/README.md they came into mind in regards to cutting the tests short and the environment not properly cleaning up.
For go usage see: https://stackoverflow.com/questions/11268943/is-it-possible-to-capture-a-ctrlc-signal-and-run-a-cleanup-function-in-a-defe
example trap:
package main

import (
    "fmt"
    "os"
    "os/signal"
    "syscall"
    "time" // or "runtime"
)

func cleanup() {
    fmt.Println("cleanup")
}

func main() {
    c := make(chan os.Signal)
    signal.Notify(c, os.Interrupt, syscall.SIGTERM)
    go func() {
        <-c
        cleanup()
        os.Exit(1)
    }()

    for {
        fmt.Println("sleeping...")
        time.Sleep(10 * time.Second) // or runtime.Gosched() or similar per @misterbee
    }
}

Interesting idea!
Probably makes more sense to file it in https://github.com/gruntwork-io/terratest

Will move

https://github.com/gruntwork-io/terratest/issues/328


Cloud SOAR Delivery 2 - GA

Purpose of this pull request
This pull request (PR) makes the following beta article visible for GA release:
https://help.sumologic.com/docs/cloud-soar/cloud-soar-delivery-2/
It also adds a release note here:
https://help.sumologic.com/release-notes-csoar/
Issue number: Asana ticket Cloud SOAR Delivery 2 - GA

Select the type of change:

[ ] Minor Changes - Typos, formatting, slight revisions
[ ] Update Content - Revisions and updating sections
[x] New Content - New features, sections, pages, tutorials
[ ] Site and Tools - Updates, maintenance, and new packages for the site, Gatsby, React, etc

Thanks for the review, @kimsauce.

Moved this PR to draft. The term "Delivery 2" might change to a version number instead.

We'll need to publish this PR at the same time:
https://github.com/SumoLogic/sumologic-documentation/pull/3361


What is the difference between Menu and List?

I'd like to better understand the difference between List and Menu and their pros/cons. On the surface they look the same, but I'm sure there's much more beneath.
For example, if I have a larger dynamic list, which one should I use? Are there any performance or rendering differences between the two?

Hi, @ramuta. Both Menu and List used FlatList from inside, so it doesn't really matter which one to use in terms of performance, they both fits if you're willing to render large amount of data.. The decision which one to use depends on case.
Let me explain you =)
List component represents FlatList with predefined styles & methods inside. Its recommended to use it with ListItem render component, but you can render whatever you want to. Consider to use this one if you're want to display large dynamic list.
Menu represents List realisation from beneath, but it also could use nested items at a glance, so each group item can be accessed by group render element.
I recommend to use Menu component when it's really represents menu bar (items could be selected and nested). And with help of MenuGroup & MenuItem components you can create an awesome menu bar =)
You could also take a look at docs, there's really good examples of usage

Oh, they are both FlatList, I didn't know that - thanks for your explanation and links! 🙂


Now supporting a map object as a parameter for the neo4j string

The format used is eg:
MATCH(n:TestNode) SET #n $m, n.`updated?` = true RETURN n with the props {:m {:name "test", :type "query"}}
==>  MATCH(n:TestNode) SET `n`.`name` = $`m`.`name`, `n`.`type` = $`m`.`type`, n.`updated?` = true RETURN n

Okay this looks good but my worry is that there is a space between the two params which I think would have been nicer to leave off. Also it would be great if there would be a check that $m must be a non empty hash map

Okay, pull request updated now the format is #m$n without the space. And a check was added to the validation of parameters to make sure that the sent object is not empty and might cause a cypher error.


ruff: 0.0.215 -> 0.0.217

Diff: https://github.com/charliermarsh/ruff/compare/v0.0.215...v0.0.217
Changelog: https://github.com/charliermarsh/ruff/releases/tag/v0.0.217
Description of changes

Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] 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
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
23.05 Release Notes (or backporting 22.11 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
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 209924 run on x86_64-linux 1

1 package built:

ruff


x/tools/gopls: signal version differences in go.mod when using go.work

go.mod is not a lock file and go's module version selection may pick versions different from what are written in go.mod require statement. But most of time, we expect the versions appearing in go.mod are the versions actually in use. Especially, when using go.work or replace or exclude come into play, the difference can be sometimes confusing.
How about surfacing this when the versions chosen by Go and written in the main module's go.mod are different?
Either using  1) inlay hints next to the require statement or 2) informational diagnostics on the require statement.
cc ideas from @ianthehat

Makes sense to me.
CC @bcmills, who may have insight.

Peter and I just discussed this, and realized it would be useful to compute this information whenever we build the metadata graph (cache.metadataGraph.build). Then adding an inlay hint becomes a very cheap operation.


autoconf error configure.ac:34: error: possibly undefined macro: AM_INIT_AUTOMAKE

In [65]: !autoconf
configure.ac:29: error: possibly undefined macro: AC_LIBTOOL_WIN32_DLL
      If this token and others are legitimate, please use m4_pattern_allow.
      See the Autoconf documentation.
configure.ac:34: error: possibly undefined macro: AM_INIT_AUTOMAKE
configure.ac:35: error: possibly undefined macro: AM_SILENT_RULES
configure.ac:41: error: possibly undefined macro: AM_CONDITIONAL
configure.ac:44: error: possibly undefined macro: AC_DISABLE_STATIC
configure.ac:45: error: possibly undefined macro: AC_PROG_LIBTOOL
configure.ac:46: error: possibly undefined macro: AM_PROG_CC_C_O

In [66]: !autoscan
configure.ac: warning: missing AC_CHECK_FUNCS([memset]) wanted by: libudis86/udis86.c:47
configure.ac: warning: missing AC_CHECK_HEADERS([fcntl.h]) wanted by: udcli/udcli.c:48
configure.ac: warning: missing AC_PROG_INSTALL wanted by: autogen.sh:4
configure.ac: warning: missing AC_PROG_MAKE_SET wanted by: docs/manual/Makefile.am:40
configure.ac: warning: missing AC_TYPE_INT16_T wanted by: libudis86/types.h:136
configure.ac: warning: missing AC_TYPE_INT32_T wanted by: libudis86/types.h:138
configure.ac: warning: missing AC_TYPE_INT64_T wanted by: libudis86/syn.c:136
configure.ac: warning: missing AC_TYPE_INT8_T wanted by: libudis86/types.h:134
configure.ac: warning: missing AC_TYPE_SIZE_T wanted by: libudis86/decode.c:548
configure.ac: warning: missing AC_TYPE_UINT16_T wanted by: libudis86/decode.c:59
configure.ac: warning: missing AC_TYPE_UINT32_T wanted by: libudis86/decode.c:158
configure.ac: warning: missing AC_TYPE_UINT64_T wanted by: udcli/udcli.c:84
configure.ac: warning: missing AC_TYPE_UINT8_T wanted by: libudis86/decode.c:81

configure.ac:29: error: possibly undefined macro: AC_LIBTOOL_WIN32_DLL

Do you have libtool installed? If not, install it first. This may solved your issue!
If it does please close this old issue.


We want nz-sider to overlay the content instead of pushing the content

What problem does this feature solve?
nz-sider needs to have an option to make it overlay on top of existing content instead of pushing that content, while expanding the nz-sider from collapsed state, just like material design
https://stackblitz.com/edit/angular-keztzw
What does the proposed API look like?
A directive like nzBehavior="overlay | push" is better
 <nz-sider nzCollapsible nzBehavior="overlay" nzWidth="200px">
It needs to have black overlay, once you click the overlay it should go back to folded state.

It's unbelievable that this simple basic feature is missing in this library.

You can use NzDrawer to make this happens

Is someone working on this issue?

Is this issue fixed? if it means please post it here,
if not suggest me any other solution.
Thanks in advance

Is there an update for this issue ??
Please let us know, Thank you !!

Esto seria supremamente util, poder realizarlo sin tener que depender de otros controles adicionales.

I was also searching for solution to this problem. After some hours of tweaking here and there, i found one.  position: fixed and adding zome z-index did the trick for me. In my case, i had to also add height calculation, because my header was also fixed, but after some tweaking, nz-sider is overlaying content, instead of pushing it away.
At the moment of writing this comment I cannot provide an example in some sandbox, but I certainly will try to find time, to generate an example of how I achieved this.

NzDrawer worked fine for me, thanks @duongleh


Added instructions on building stand-alone Mac OS X binary

This can put an end to the pain on OS X by building a stand-alone binary inside a virtualenv.

Build occurs inside a virtualenv
Added new icon
Updated README.md and Icon GPL Attribution

It should be fairly easy to add this to a .travis file and run this on an OSX CI image to build the binary and add it to the github releases.
Also it should be fairly trivial to build a brew recipe.

Added travis osx check, took a bit to work around python version issues


Backport 1807 - Deploying External Cloud Provider with Helm Controller - Chicken:Egg problem

From rancher/k3s#1807
Version:
v1.18.2+k3s1
K3s arguments:
provider_id="$(curl -s http://<IP_ADDRESS>/latest/meta-data/placement/availability-zone)/$(curl -s http://<IP_ADDRESS>/latest/meta-data/instance-id)"

k3s server \
  --disable-cloud-controller \
  --disable servicelb \
  --disable local-storage \
  --disable traefik \
  --datastore-endpoint=${k3s_db_endpoint} \
  --token="${k3s_server_token}" \
  --agent-token="${k3s_agent_token}" \
  --node-name="$(hostname -f)" \
  --kubelet-arg="cloud-provider=external" \
  --kubelet-arg="provider-id=aws:///$provider_id" \
  --write-kubeconfig-mode=644 \
  --tls-san=${elb_dns}

Describe the bug
I would like to install the AWS CCM (external cloud provider) with a helm chart and the helm chart controller by placing a helm manifest in /var/lib/rancher/k3s/server/manifests but helm chart controller pod won't initialize on a new cluster because all the nodes are tainted with node.cloudprovider.kubernetes.io/uninitialized: true.  So I need a cloud-provider to install my cloud-provider.
I can remove the taint on one of the nodes, but then that node doesn't get properly initialized.
Is there a way to modify the helm chart controller with a tolerance so it can run on a uninitialized node?
To Reproduce
Launch a new cluster with an external cloud provider and try to install an external cloud provider with a helm chart.
/var/lib/rancher/k3s/server/manifests/00-aws-ccm.yaml
apiVersion: helm.cattle.io/v1
kind: HelmChart
metadata:
  name: aws-cloud-controller-manager
  namespace: kube-system
spec:
  chart: aws-cloud-controller-manager
  repo: http://charts.jgreat.me
  version: 0.0.0-20200508.T071542
  targetNamespace: kube-system

Expected behavior
Helm controller would launch included chart.
Actual behavior
Helm controller pods didn't tolerate node.cloudprovider.kubernetes.io/uninitialized: true taint.
Additional context / logs
➜ kubectl -n kube-system describe pods helm-install-aws-cloud-controller-manager-nd5cm
Name:         helm-install-aws-cloud-controller-manager-nd5cm
Namespace:    kube-system
Priority:     0
Node:         ip-172-20-61-193.us-east-2.compute.internal/<IP_ADDRESS>
Start Time:   Mon, 18 May 2020 15:51:20 -0500
Labels:       controller-uid=0e7af8c6-7bab-4a40-bb49-f97f782a1dd1
              helmcharts.helm.cattle.io/chart=aws-cloud-controller-manager
              job-name=helm-install-aws-cloud-controller-manager
Annotations:  <none>
Status:       Running
IP:           <IP_ADDRESS>
IPs:
  IP:           <IP_ADDRESS>
Controlled By:  Job/helm-install-aws-cloud-controller-manager
Containers:
  helm:
    Container ID:  containerd://25af9567c5dc8692f6f812530b2dfcb2602e57600bfcee72284e23b9a8adb9e6
    Image:         rancher/klipper-helm:v0.2.5
    Image ID:      docker.io/rancher/klipper-helm@sha256:b694f931ffb70c4e0b6aedf69171936cad98e79a5df49372f0e553d7d610062d
    Port:          <none>
    Host Port:     <none>
    Args:
      install
      --namespace
      kube-system
      --repo
      http://charts.jgreat.me
      --version
      0.0.0-20200508.T071542
    State:          Running
      Started:      Mon, 18 May 2020 15:51:24 -0500
    Ready:          True
    Restart Count:  0
    Environment:
      NAME:             aws-cloud-controller-manager
      VERSION:          0.0.0-20200508.T071542
      REPO:             http://charts.jgreat.me
      VALUES_HASH:      e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
      HELM_DRIVER:      secret
      CHART_NAMESPACE:  kube-system
      CHART:            aws-cloud-controller-manager
      HELM_VERSION:
      NO_PROXY:         ,<IP_ADDRESS>/16,<IP_ADDRESS>/16
    Mounts:
      /var/run/secrets/kubernetes.io/serviceaccount from helm-aws-cloud-controller-manager-token-rcgx9 (ro)
Conditions:
  Type              Status
  Initialized       True
  Ready             True
  ContainersReady   True
  PodScheduled      True
Volumes:
  helm-aws-cloud-controller-manager-token-rcgx9:
    Type:        Secret (a volume populated by a Secret)
    SecretName:  helm-aws-cloud-controller-manager-token-rcgx9
    Optional:    false
QoS Class:       BestEffort
Node-Selectors:  <none>
Tolerations:     node.kubernetes.io/not-ready:NoExecute for 300s
                 node.kubernetes.io/unreachable:NoExecute for 300s
Events:
  Type     Reason            Age        From                                                  Message
  ----     ------            ----       ----                                                  -------
  Warning  FailedScheduling  <unknown>  default-scheduler                                     0/2 nodes are available: 2 node(s) had taint {node.cloudprovider.kubernetes.io/uninitialized: true}, that the pod didn't tolerate.
  Warning  FailedScheduling  <unknown>  default-scheduler                                     0/2 nodes are available: 2 node(s) had taint {node.cloudprovider.kubernetes.io/uninitialized: true}, that the pod didn't tolerate.

The original issue was needed in 1.18.x (originally had a 1.18 milestone). We'll need to backport this for our next v1.18.x patch release.

@rancher-max same as https://github.com/rancher/k3s/issues/1807 just backported into v1.18 release branch. We should just do a quick check to ensure it's good to go. I think we should just build from that branch and test and close this out.

Validated in backport using commit id: b9542ef0014fd4c5b7d6d70a29f0a953ab7d85dd from release-1.18 branch.
Followed the same steps I did to validate the original issue.


just a speck of dust

paying attention! "a attention distribution" -> "an attention distribution"

Thanks, Lance!


Mail relay does not work when amavis is disabled

Configuration
  mailserver:
    build: mailserver/
    hostname: mail
    domainname: example.com
    environment:
      DISABLE_AMAVIS: 1

Relay server configuration
smtp_sasl_auth_enable = yes
smtp_sasl_password_maps = static:xxx:xxx
smtp_sasl_security_options = noanonymous
smtp_tls_security_level = encrypt
header_size_limit = 4096000
relayhost = [smtp.sendgrid.net]:2525

The error message
Nov 23 11:06:46 mail postfix/smtp[1013]: connect to <IP_ADDRESS>[<IP_ADDRESS>]:10024: Connection refused
Nov 23 11:06:46 mail postfix/smtp[1013]: 3B6EB950<EMAIL_ADDRESS><EMAIL_ADDRESS>relay=none, delay=0.14, delays=0.13/0.01/0/0, dsn=4.4.1, status=deferred (connect to <IP_ADDRESS>[<IP_ADDRESS>]:10024: Connection refused)

The problem is that content_filter = smtp-amavis:[<IP_ADDRESS>]:10024 is statically set even when amavis is disabled.
Current workaround is to add content_filter = to the postfix-main.cf.
I think this value needs to be setted depending  amavis is enabled or disabled?

You're right, this should be fixed. Want to contribute?

I can but I want to make sure that only amavis needs this content_listener whats about clamav?

IMHO, clamav should also be disabled because triggered by amavis.

So when DISABLE_AMAVIS is set clamAV is disabled automatically?

Yes, amavis is the entrypoint for clamav and spamassassin.
If amavis is not running, clamav should not be running neither.
Let me know if I can help.

But keeping amavis and disabling clamav should be a working solution too.
There's an old bug reported on this part:
https://github.com/tomav/docker-mailserver/issues/256

DISABLE_AMAVIS does not exist anymore in 2.1.
You can enable/disable spam and virus check separately.
I close this issue and add a new one to create ENABLE_AMAVIS env.

Thanks for you fix :)


Property Test for BigInt

Summary of changes
Changes introduced in this pull request:

Use quickcheck to test our custom implementations of BigInt

Reference issue to close (if applicable)

Closes associated task in #1881
Other information and links

N/A

I don't see the point in this test. It's a foreign type so it should be tested in its respective crate. Even ref-fvm re-exports this from num-bigint. Can you elaborate on the value added here?

We're testing the JSON serialize/de-serialize implementation which is our own and not part of any other crate. We have the assumption that a round-trip through JSON is lossless and this test is making sure that assumption is correct.

I don't see the point in this test. It's a foreign type so it should be tested in its respective crate. Even ref-fvm re-exports this from num-bigint. Can you elaborate on the value added here?
Where
We're testing the JSON serialize/de-serialize implementation which is our own and not part of any other crate. We have the assumption that a round-trip through JSON is lossless and this test is making sure that assumption is correct.

Sorry, I'm missing something. Where in this PR do we do JSON serialization in the test? Is to_string() invoking that?

Ah, you're right. The wrong serialization code is being tested. It should test the two above serialize/deserialize functions but it isn't.

@lemmih Ya, then it would make sense. In its current state, this PR needs some touch.

@jdjaustin You can use these two macros to test stand-alone serialize and deserialize functions:
    macro_rules! to_string_with {
        ($obj:expr, $serializer:path) => {{
            let mut writer = Vec::new();
            $serializer($obj, &mut serde_json::ser::Serializer::new(&mut writer)).unwrap();
            String::from_utf8(writer).unwrap()
        }};
    }

    macro_rules! from_str_with {
        ($str:expr, $deserializer:path) => {
            $deserializer(&mut serde_json::de::Deserializer::from_str($str)).unwrap()
        };
    }


Add CONTRIBUTING.md

I'm not sure we want to use the same CONTRIBUTING template from Eraser Map here. That one seems more geared to a consumer app.
For the SDK I was thinking something more along these lines: https://github.com/square/android-times-square/blob/master/CONTRIBUTING.md

That's definitely more relevant. Updated.


Multiple prompt to grant access to login keychain after always allow

VSCode Version: 1.51-Insiders
OS Version: macOS

Originally reported in #108342 which was then re-purposed.
@deepak1556 and me investigated but didn't find anything special from the logs log show --start "2020-10-07 15:27:48" --end "2020-10-07 16:27:48" --predicate 'eventMessage CONTAINS[c] "Keychain"' --info --debug and keychain info. One suspicion is maybe I'm using GitHub intensively, my setup:

Settings Sync is using GitHub account
GitHub PRI is using GitHub account
GitHub Issue Notebook is also using GitHub account

On Oct 6th, I ran into SSO bad credential issue with GitHub Issue Notebook so I signed out of my GitHub account. Then I login again and grant access to all three extensions/services. I got a prompt for login keychain access once, I clicked "always allow"
On Oct 7th afternoon, I saw the prompt again.

Does this issue occur when all extensions are disabled?: Yes/No

@rebornix Can you copy the text of the prompt you keep seeing? Which key is it trying to access in the keychain? I'm wondering if there is anything we write that is not prefixed by the product scheme, so that switching between stable and insiders would cause the prompt to be shown again. Or are you seeing multiple prompts in a row within the same session?

@RMacfarlane sure I'll take screenshot when I see it again, I'm currently seeing it once a day or every other day but every time I only saw the prompt once.

This is the prompt I always see when running into this issue.

Awesome, thanks! This is actually from the Live Share extension, not anything we write in VS Code. I can reproduce this when I have it installed in both Insider's and OSS, I sign in on Insider's, run OSS and see the prompt and allow it, then restart Insider's and see the prompt again. The key isn't prefixed with anything about the current product scheme, so switching between products causes the prompt. I'm not sure why Mac doesn't just allow both, but the behavior is that it prompts again when a new process accesses it.
Closing since this is caused by the Live Share extension.

The "VS Code Account" made me think it's controlled by us, and yes I have Live Share installed in both OSS and Insiders. Thanks a huge ton for the investigation, you made my day!
I wonder if there is no prefix for the key, Live Share can access this info from both Insiders and Stable, right? If so users who are using both Stable and Insiders may run into it as well, should we file an issue against Live Share? cc @lostintangent

Thought about it again why I didn't figure out the problem myself, it's majorly because

The prompt is controlled by macOS and we can't change the wording. By reading the prompt, I thought it was VS Code account management trying to read my account info.
Then I open the account management view but can only find GitHub Issue Notebook, PRI, and Settings Sync using my GitHub account info.

Thus I thought it was these extensions are reading the info

Is it in the long term plan that every extension moves to use the authentication api instead of reading keychains themselves?

Given the permissions dialog doesn't or can't show useful context, could you add an indicator to the Code window indicating the specific extension or feature that caused the prompt to appear? Alternatively, could you add a way to log these permissions requests including service and account, basically whatever's passed to keytar, and the extension or feature that triggered the request?


Migrate to ExoPlayer 2.11.5. Fixes #359

Updating UAMP from ExoPlayer 2.10.0 to 2.11.5
What are the changes?
Blog post: https://medium.com/google-exoplayer/exoplayer-2-11-whats-new-e0e0701e4b6c
Relnotes: https://github.com/google/ExoPlayer/blob/release-v2/RELEASENOTES.md
Changes which affect UAMP
setHandleAudioBecomingNoisy(true)
Possibly: https://github.com/google/ExoPlayer/issues/6093
Possibly: https://github.com/google/ExoPlayer/issues/5891
Issues
Problem: MusicService.kt: (325, 9): 'onNotificationPosted' overrides nothing
Cause: Method signature changed from
onNotificationPosted(
            notificationId: Int,
            notification: Notification?,
            ongoing: Boolean
        )

to
onNotificationPosted(
            notificationId: Int,
            notification: Notification,
            ongoing: Boolean
        )

Solution: Change Notification? to Notification
Problem: UampNotificationManager.kt: (88, 19): Class 'DescriptionAdapter' is not abstract and does not implement abstract member public abstract fun createCurrentContentIntent(p0: Player): PendingIntent? defined in com.google.android.exoplayer2.ui.PlayerNotificationManager.MediaDescriptionAdapter
Cause: Method signatures have changed
Solution: Update method signatures. See commit
Problem: MusicService.java:18: error: cannot find symbol
private com.example.android.uamp.media.BecomingNoisyReceiver becomingNoisyReceiver;
^
Cause: Unknown - didn't investigate further because ExoPlayer can now handle the "becoming noisy" event for us.
Solution: Remove class and add setHandleAudioBecomingNoisy(true) when SimpleExoPlayer is instantiated
Problem: MusicService.java:20: error: cannot find symbol
private com.example.android.uamp.media.PackageValidator packageValidator;
Cause: The ctor sig is class PackageValidator(context: Context, @XmlRes xmlResId: Int) and the @XmlRes causes the build to fail
Solution: ?? clean and rebuild :/
Problem: UampPlaybackPreparer.kt: (41, 1): Class 'UampPlaybackPreparer' is not abstract and does not implement abstract member public abstract fun onPrepare(p0: Boolean): Unit defined in com.google.android.exoplayer2.ext.mediasession.MediaSessionConnector.PlaybackPreparer
Cause: method signature changes. E.g. onPrepareFromMediaId now supplies playWhenReady as a parameter
Solution: add the playWhenReady parameter to method signatures and pass this to exoPlayer where appropriate. Update comments.
Problem: ExoPlayerFactory.newSimpleInstance is deprecated
Solution:
SimpleExoPlayer.Builder(this).build().apply {
            setAudioAttributes(uAmpAudioAttributes, true)
            setHandleAudioBecomingNoisy(true)
            addListener(playerListener)
        }

Problem: PlayerNotificationManager.createWithNotificationChannel deprecated
Solution: Use the version which includes the channel description
Problem: .getWindow(windowIndex, window, true) deprecated
Solution: Change to .getWindow(windowIndex, window)

Thank you!


Pass data_type to included datasets path function

We dont have an included datasets json for v4.0 genomes. This will fix that moving forward.  We ran exomes last so the existing datasets file is correct.

When you say copied and replaced, was this just a text change? Or did you confirm the paths were accurate? The v4 release pulls from v3.1 for genomes: https://github.com/broadinstitute/gnomad_qc/blob/1c1dfbc44d54379ac16b71af603c67a990fbfb4b/gnomad_qc/v4/create_release/create_release_sites_ht.py#L222

Yes, text change, I copied from gs://gnomad/release/4.0/json/exomes/gnomad.exomes.v4.0.included_datasets.json to local and edited this file, then copied it back to gs://gnomad/release/4.0/json/genomes/gnomad.genomes.v4.0.included_datasets.json
You can have a look at both. I didn't replace the exome one.
That's how I got info HT path.

@KoalaQin , are there any other changes you'd like to see?

Thank you -- I also documented the genome included datasets json file creation here.


Review

Please review, @christofelician

#Description of repository
This repository consists of the python files self_sufficiency_calculation.py, Unit Test.py and a workflow with pylint.
-self_sufficiency_calculation.py calculates the degree of self sufficiency of an installed PV.
Therefore the PV production and the consumption is compared and the degree of self sufficiency is calculated.
-Unit Test.py. is testing itself, wich contains the same copied code of self_sufficiency_calculation.py. So if only self_sufficiency_calculation.py is changing and this resulting to wrong calculations, unit Test is not able to detect them. This changed source code must be copied into UNIT Test.py too.
Pytest  Ran 0 tests in 0.000s
-Pylint is the linter used in this repository.
pylint already fails with the errors: No module named Unit (fatal), No module named Test.py (fatal), Missing module docstring ,  Unable to import 'numpy', Unable to import 'matplotlib.pyplot'.
Tests

[x] License exists
[x] Create a fork and start a pull-request
[cannot fail ] pytest fails as expected
[ already fails ] ruff linter fails as expected

ruff linter is a pylinter in this case
Pytest runs no test files

@Maxiausder4a funktioniert dein Linter nicht oder ist das nur bei mir so?
LG Christoph


OperatorNotAllowedInGraphError: using random seed in tf.function

Click to expand!
Issue Type
Feature Request
Source
binary
Tensorflow Version
tf 2.9.1
Custom Code
No
OS Platform and Distribution
Linux Ubuntu 20.04
Mobile device
No response
Python version
3.8.10
Bazel version
No response
GCC/Compiler version
No response
CUDA/cuDNN version
11.1.74 / 8.0.5
GPU model and memory
NVidia Tesla V100-SXM2-32GB
Current Behaviour?
tf.random.set_seed() in a tf.function doesn't seem to do anything.
Standalone code to reproduce the issue
For reproducible tests it might be useful to set seeds. When using a distributed strategy, it would be nice to have a different seed for each replica, hence set the seed inside the tf.function.
I've done tests (without a distributed strategy for sake of simplicity):
This works:
@tf.function
def f(X):
    tf.random.set_seed(X)

f(tf.constant(1))

This works too:
@tf.function
def f(X):
    tf.print(tf.random.normal((2,3)))

f(tf.constant(1))

But this fails:
@tf.function
def f(X):
    tf.random.set_seed(X)
    tf.print(tf.random.normal((2,3)))

f(tf.constant(1))

... with this error:
File "<ipython-input-165-c6a6c2a4e4db>", line 4, in f  *
        tf.print(tf.random.normal((2,3)))
OperatorNotAllowedInGraphError: Using a symbolic `tf.Tensor` as a Python `bool` is not allowed: AutoGraph did convert this function. This might indicate you are trying to use an unsupported feature.

Note that setting a seed in a tf.function doesn't seem to work:
@tf.function
def f():
    tf.random.set_seed(1)
    tf.print(tf.random.normal((2,3)))

f()
f()

prints different values for the two f() invocations
Using an externally provided seed for tf.random.normal() also results in a OperatorNotAllowedInGraphError:
@tf.function
def f(X):
    tf.print(tf.random.normal((2,3), seed=X))

f(tf.constant(1))

Consider this last attempt:
class MyModule(tf.Module):
    def __init__(self, seed):
        self.seed = seed
        self.strategy = tf.distribute.MirroredStrategy()

    def _train(self):
        # this works but all replicas have the same seed.
        tf.print(tf.random.normal((2,3), seed=self.seed))

        if False: # replace with True to test
            # the seed differs but this fails with OperatorNotAllowedInGraphError
            repl_id = tf.distribute.get_replica_context().replica_id_in_sync_group
            print(tf.random.normal((2,3), seed=self.seed + repl_id))

    @tf.function
    def distributed_train(self):
        self.strategy.run(self._train)

module = MyModule(seed=1)
module.distributed_train()

Again, this seems silly but the only purpose of using seeds inside a tf.function is to provide each replica with a different seed.

@tf.function
def f():
    tf.random.set_seed(1)
    tf.print(tf.random.normal((2,3)))

f()

is working for me. See https://colab.research.google.com/gist/bhack/815bd1283b4de03f21702c627919047e/untitled181.ipynb
@tf.function
def f(X):
    tf.random.set_seed(X)
    tf.print(tf.random.normal((2,3)))

f(tf.constant(1))

Is failing cause autograph is not going to covert correctly this condition
https://github.com/tensorflow/tensorflow/blob/bf22440f8485b5af3823cdd1b32b52cbce15b487/tensorflow/python/framework/random_seed.py#L89-L91

Basically It is like

@tf.function
def f(X):
    if X == (0,0):
      return True
    return False

print(f(1))
print(f(tf.constant(1))) # This will not work

Hi @thierryherrmann !
I think I found the issue here . Actually, you are passing a non integer seed in the tf.random.set_seed which is causing the issue. If only integer value are passed in above reproducible code snippets, I can get the expected values.
Attached resolved gist for reference.
Thank you!

thanks a lot @bhack for your response. Unfortunately for your first code snippet, you mention it works for you. Indeed it works but if you read carefully my initial comment, if you invoke f() several times (without redefining the function), it will give you different random numbers, which is not what we expect, given the tf.random.set_seed(1).
That's why in my snippet, I called f() twice after the function definition (this was not a typo).
I realize I should have RTFM: tf.random.set_seed()'s doc contains much more info than I thought. For a repeatable result calling f() several times, there is tf.random.stateless_normal() and other stateless_xxx() functions.
E.g. this gives the same result for the two invocations of f():
@tf.function
def f():
    tf.random.set_seed(1)
    tf.print(tf.random.stateless_normal([3], seed=[2,4]))

f()
f()

I'm not sure I understand your explanation about if seeds == (0, 0): . This is part of the get_seed() function and not the set_seed() function. But thanks for having taken the time to answer and for the snippets.

Thanks a lot @mohantym for your response. Unfortunately I'm afraid the seed I pass is really an integer.
If you add this line:
tf.print((self.seed + repl_id).dtype)

it'll print tf.int32
I saw that you replaced self.seed + repl_id with just self.seed to make the code work.
But that addition + repl_id was intentional: if you only use self.seed both replicas will generate the same random numbers.
By adding repl_id you have a different seed for each replica, but if you re-run the code, those two seeds will remain the same (self.seed + 0 for replica0 and self.seed + 1 for replica1), satisfying the reproducibility requirement. Unfortunately this ends with a OperatorNotAllowedInGraphError
But thanks for having taken the time to answer, I appreciate it.

Thanks again @bhack, @mohantym for your contribution. I searched more and the stateless_xxx() functions are the solution.
This code satisfies my requirements:
class MyModule(tf.Module):
    def __init__(self, seed):
        self.seed = seed
        self.strategy = tf.distribute.MirroredStrategy()

    def _train(self):
        repl_id = tf.distribute.get_replica_context().replica_id_in_sync_group
        tf.print('replica', repl_id, tf.random.stateless_normal((3,), seed=[self.seed + repl_id, self.seed + repl_id]))

    @tf.function
    def distributed_train(self):
        self.strategy.run(self._train)

module = MyModule(seed=0)
module.distributed_train()
module.distributed_train()

module = MyModule(seed=3)
module.distributed_train()
module.distributed_train()

Output:
INFO:tensorflow:Using MirroredStrategy with devices ('/job:localhost/replica:0/task:0/device:GPU:0', '/job:localhost/replica:0/task:0/device:GPU:1')
replica 0 [-1.697034 -0.481376708 -0.662236929]
replica 1 [1.66521633 1.36637604 0.778631628]
replica 0 [-1.697034 -0.481376708 -0.662236929]
replica 1 [1.66521633 1.36637604 0.778631628]
INFO:tensorflow:Using MirroredStrategy with devices ('/job:localhost/replica:0/task:0/device:GPU:0', '/job:localhost/replica:0/task:0/device:GPU:1')
replica 0 [0.248304084 0.671974301 0.445930719]
replica 1 [-0.991607666 0.0630038455 -0.832075655]
replica 0 [0.248304084 0.671974301 0.445930719]
replica 1 [-0.991607666 0.0630038455 -0.832075655]

So with a given seed, the results are reproducible: each replica generates different numbers but a second execution will have the replicas generate the same numbers as with the previous execution.
Changing the seed changes completely the sequences as expected.
The issue can be closed with the RTFM label if that exists!!
Thank you both.

Ok @thierryherrmann !
Thanks for the update. Actually, What I meant seed should be a python integer not an integer Tensorflow Tensor.
Marking this as resolved from above comment.
Thank you!

Are you satisfied with the resolution of your issue?
Yes
No

@mohantym

What I meant seed should be a python integer not an integer Tensorflow Tensor.

Actually passing the seed to the tf.function as a tf.constant rather than a python int was intentional. autograph reconstructs a new graph on each invocation with a different python int value. While with a tf.constant, it reuses the same graph.
My simplified example doesn't show the input_signatures I use with the tf.function to restrict inputs and ensure only one graph is generated. This wouldn't be serious in my simple example, but in our real (big) model, graph regeneration would take seconds and consume memory.
Fortunately tf.random.stateless_xxx() solves everything.
Thanks for your feedback.

Unfortunately for your first code snippet, you mention it works for you. Indeed it works but if you read carefully my initial comment

Yes sorry is that it seems, without the output, that it was empty. But reading again the "text" it is clear. So the pointer to the stateless version is correct.
P.s. the autograph problem mentioned for the non stateless impl at https://github.com/tensorflow/tensorflow/issues/58433#issuecomment-1302627410 is still valid.


Investigate telemetry for DomainManager usage

@brettsam Additional detail needed.

Closing as the requirements have changed for going forward.


Finalizing v0.3.0

This is the finish of the BpyBuild rewrite. We just need to test this and make sure it works

Need to test this locally still, traveling today but will see if I have time tonight

I've pushed some changes to how BpyBuild handles configuration, specifically taking advantage of cattrs to read YAML configs into attrs objects (we already used attrs in BpyBuild prior to this since it's basically dataclasses with some pretty useful abilities, so using cattrs was pretty easy)

This should also make adding new config options easier as we no longer have to manually parse by hand (parsing JSON and YAML is a pain...)

As a side question, do these changes by chance allow for building the addon without having to re-copy all resource files? (ie the equivalent to the old -fast option)? That's still my biggest gripe, which slows down test-driven development, since 80% of the time running tests is actually the zipping install step.

Python 3.9 was chosen as the minimum version since most libraries have stopped supporting Python 3.7, so this was more out of neccesity. I'll recheck the minimum versions of the dependencies we use and see if I can reduce it (maybe Python 3.8?), but the only option for using Python 3.7 would be using older versions of libraries, which is not ideal (the old BpyBuild used to use outdated dependencies and suffered as a result, I don't want a repeat of that).
As for the error, I'm not exactly sure what's going on, but I think it's related to to the Pip syntax. Pip syntax with packages on Git repos and a specific branch is not commonly used, so I probably made an error in the command syntax.
As for the fast option, we don't have that in BpyBuild yet, but a workaround would be to keep the resources outside of the addon folder, and have a build action (like a production build action) that copies them only when specified (which would mean fast by default, slow on opt-in). In the future, BpyBuild will allow specifying what files to copy over for certain build actions

Alright, the most I can reduce the minimum Python requirement is Python 3.8. As far as I'm aware, cattrs doesn't support 3.7 (though attrs, the parent package, supports Python 3.6), and at the moment I don't want to start pinning specific versions for dependencies. My recommendation would be either to install BpyBuild using something like PipX to make the command available globally while keeping the package isolated (this is how I use BpyBuild on my system), or use path/to/3.8 venv/bin/bab ...
As for the error you've encountered with pip, it turns out it was a configuration side error with pyproject.yaml. It's fixed now

Also, I'm working on the filters plan I mentioned earlier, so a fast option will be possible

Ok ignore what I said about 3.8, we use some 3.9 exclusive features in argparse:

I've dealt with booleans in argparse in a 3.7 compatible way with some workarounds, so I'd argue for at least 3.8 to be closer if this is the only problem.  This is what I've used before, and I think would work fine here:
    parser.add_argument('-i', '--individual', action='store_true')
    parser.set_defaults(individual=False)

And based on what you said, I'm fine to go with 3.8+ for the build env. Like I said, actual syntax problems of 3.7 will show up in automated unit tests, would rather not increase the problems based on what we are avoiding here.
For reference, blender 2.90 uses 3.7.7, but blender 2.93 uses 3.9.2, so python 3.8 is still at least relevant within the 2.9x era.
Thanks for doing the investigation - it is indeed the holiday's, please enjoy family time and feel free to not reply back until later whenever you are more free!

(also whenever it is ready for me to re-review, just click the refresh icon next to my user under the reviews section top-right!)

Alright, I got filters pushed (though I'll probably rename the config key to ignore_filters as its clearer compared to filters), you can try it on the MCprep repo with the dev action.
What makes these filters different from the Python based ones is that the Python based ones are only applied to the intermediate copy BpyBuild makes for actions (so the main folder isn't affected), whereas these are applied when making said copy.

Should be fixed now

Will push to PyPI now


Preserve undo stack when going from serial->blocks

Preserves Blockly undo stack for "editors" that use the "Go Back" button (serial, github view, etc).
Fixes https://github.com/microsoft/pxt-microbit/issues/697

yeah, i think ideally we should serialize the undo stack, and also these "overlays" (serial, pxt json, etc) should not unload the editor underneath them. i was looking into doing this with monaco too, but blockly's stack is easily accessible (and we are manually clearing it), and i think for monaco it would be a more manual process
https://github.com/microsoft/monaco-editor/issues/239
https://github.com/Microsoft/monaco-editor/issues/686


What can I assume about thread safety?

Looking through the code I see comments like this, which make me concerned about thread safety. In the current version, what should I assume is thread-safe? In particular, is operating on different memory handles but with the same gdr_t safe?

Looking through the code I see comments like this, which make me concerned about thread safety.
The problematic case is when one thread triggers an invalidation, e.g. cudaFree, while a second thread calls gdr_unpin_buffer.
It could theoretically happen, although it should be very very rare.

In particular, is operating on different memory handles but with the same gdr_t safe?
Yes, it is safe.

Thanks.

@drossetti  I do believe I've encountered this issue with concurrent (across threads) gdr_pin_buffer + gdr_maps and gdr_unmaps + gdr_unpin_buffer; completely different buffers in play... I've had situations where it is not rare.
It's interesting because ioctl returns error code -22 (unknown error), the addresses however are aligned and look good. User managing a lock is one way to deal with the problem and this seems to work, however I believe you are aiming for thread safety... the comment in that code and the nv driver lock look like a pinch of a situation; is there anything else you can do to make it safe?


How do we get the delay between two meetingers?

Do we have this api in the project?

Hi @lidh15 !! thank you for stopping by!
I intend to rewrite the transport using quic + webtransport as opposed to websockets.
Quic constantly compute rtt between the peers at all times.
If this does not work, I'll add some timestamps to the protobuf messages, if the computers have their clocks synced using srtp, it will be easy to compute the delay.

I'm looking forward to it~

Seems like https://github.com/hyperium/h3 is very close to supporting what we need for WebTransport!!


Allow using .yaml file extension instead of .yml

Describe the bug/feature
I need that Kapitan can produce YAML files from Jsonnet which have a .yaml file extension instead of .yml.
To Reproduce
kapitan compile produces .yml files.
Expected behavior
Allow Kapitan to produce YAML files with a .yaml file extension, likely controlled by the output_type in the inventory. For example, output_type: yaml would produce files named *.yaml while output_type: yml would produce files named *.yml.

This seems to be a duplicate of https://github.com/deepmind/kapitan/issues/276 and that is blocked by https://github.com/salt-formulas/reclass/pull/87 getting merged.

I think #276 is about reclass and this is more about how kapitan outputs files.

This seems to be an easy task.
https://github.com/deepmind/kapitan/blob/890094592f9d61844398828958339a29ef764890/kapitan/inputs/jsonnet.py#L77-L79
to liberal
elif output in ["yml", "yaml"]:
                file_path = os.path.join(compile_path, "%s.%s" % (item_key, output))

@uberspot @adrianchifor Good for PR?

@Cyanopus Yeah that should do


Decoding a dictionary compiles, but fails to archive

Hi!
Argo v3.0.1 with CocoaPods. Curry v2.2.0, Xcode 7.3, iOS target latest
struct MediaWithSize
{
    let width : Int
    let height : Int
    let urlString : String
}

struct MediaDetails
{
    let sizes : [String: MediaWithSize]
}

extension MediaDetails : Decodable
{
    static func decode(j : JSON) -> Decoded<MediaDetails>
    {
        return curry(MediaDetails.init)
            <^> (j <| "sizes" >>- [String : MediaWithSize].decode)
    }
}

extension MediaWithSize : Decodable
{
    static func decode(j : JSON) -> Decoded<MediaWithSize>
    {
        return curry(MediaWithSize.init)
            <^> j <| "width"
            <*> j <| "height"
            <*> j <| "source_url"
    }
}

This compiles and runs just fine in simulator and device. But can't get it to Archive. On archiving, I only get (even with xcodebuild command line), the mysterious swiftc excited with error code 1.
In particular, if I comment out the part with >>- (and return some bogus error instead), it archives fine.
Any insights?
Other than this, this lib is just awesome!

my knee-jerk reaction is "oh no not this again". We've had issues with compiler optimizations before. I'd be interested to hear:

What happens if you turn off compiler optimizations for your release build
What happens if you change the syntax to use .flatMap instead of >>- ((j <| "sizes").flatMap([String: MediaWithSize].decode))
What happens if you use decodeObject instead of [String: MediaWithSize].decode (and keep >>-)
What happens if you use decodeObject and .flatMap

Running in simulator but with Release mode: swiftc error code 1
Confirmed, turning off optimization for swift compiler for release and archive works.
Same error.
Worse: It fails with error code even without optimization
Same as 3.

damn, that's what I was afraid of. Bummer that 3 and 4 don't work.
I think the way we've handled this in the past is to deconstruct flatMap into a single function that just takes the Decoded<T> type. Maybe something like:
decodeObjectFromDecoded<T: Decodable where T.DecodedType == T>(j: Decoded<JSON>) -> Decoded<[String: T]> {
  switch j {
    case let .Success(json): return [String: T].decode(json)
    case let .Failure(e): return .Failure(e)
  }
}

just spiked this out in here so syntax might be off.

Umm, the provided function itself works, but how should I use it? I try something like <^> decodeObjectFromDecoded(j <| "sizes") but no success.

@zsszatmari That seems like it should work. What's the error you're getting?

Hm! It works. I don't know, might have been a typo from my part on the other day? Thanks for helping out!

Whew. That scared me for a bit. Glad it's working out for you! I'm going to go ahead and close this, but feel free to continue asking questions here or in a new thread if needed.

Thanks, you are great! For now everything's perfect 👍

I just ran into this with >>- [String:String].decode. Curious if we know any reason this might be happening.

oh, and the decodeObjectFromDecoded fixed it, thanks @gfontenot!

for more context:
We've had issues in the past with using flatMap or >>- and the optimizer. These issues were gone, but it sure looks like they have resurfaced. If I have time/can remember I might try to reduce this down to a reproducible test case, but if anyone beats me to it I'd appreciate having a bug to track this.

Same happened to me, and the workaround provided was successful.  Thanks, @gfontenot!  This may warrant a page in the wiki, and it was tripping me up for quite a while.


Help needed..example for GPSmylocation provider to get current location and how to change green arrow to bluedot like google maps

How to start and stop gpsmyocation       in mylocationoverlay and start location by Imylocationprovider

If you don't like the build in overlay for my location, it is trivial to make your own and use whatever icon you like. I can whip up a sample if you like

@jesuvijay there you go.


Add flags to drop into an interactive smbclient or wmiexec shell on a single target

Could be very useful in some situations

Decided against implementing this since you can just do it using lots of other scripts/tools

+1
it is actually useful. cme could pass the parameters to other tools.


self -> this in ScrollResponder

I think this is causing a crash for me in a release build (curiously, not a debug build):
ReferenceError: Can't find variable: self

I saw this in 0.18.1, which I assume was renamed to v0.19.0-rc.

LGTM

@facebook-github-bot shipit


Adding code to run on Powersystem

Hi
Here is my contribution to your code, its working good on powersystems.
Thanks for the code, its working good.
What do these changes do?
Added Architecture "ppc64le"
Are there changes in behavior for the user?
No

Added power support for the travis.yml file with ppc64le. This is part of the Ubuntu distribution for ppc64le. This helps us simplify testing later when distributions are re-building and re-releasing. For more info tag @gerrith3.


Implement rising hub heights for wind; profile smoothing for offshore wind

This PR makes several changes to improve the modelling of wind profiles:

It raises the hub heights over the investment periods (from 80m to 100m for onshore wind, from 120m to 140m for offshore), to reflect larger wind turbines, and rising capacity factors.
It implements atlite's windturbine_smooth, as described by Gorm Andersen et al's REatlas paper and Bloomfield et al 2022 Fig 5 from NationalGrid. This represents smoothing across weather cells, turbine availability and other factors deviating from raw wind power curves. This lowers capacity factors by around 20%.

The smoothing is not yet implemented for onshore wind, because we see from DTU's Global Wind Atlas that the ERA5 wind speeds are a little too low over land in Germany. This is not an issue for offshore. Once the GWA correction is implemented, we can turn the smoothing on for onshore too.
FLH from ISE Stromgestehungskosten 2024 for new turbines:

onwind: 1800-2500-3200 (Binnen-Nord-Küste)
offshore: 3200-3600-4500 (middle-far-best)

Average CF for onshore in Germany in 2019 was 21.5% (1880 FLH).
Average capacity factors/FLH before the change in 2020:

onwind: 20.2% / 1768
offwind-ac: 47.4% / 4154
offwind-dc: 58.8% / 5149

and in 2045:

onwind: 23.3% / 2042
offwind-ac: 47.9% / 4194
offwind-dc: 58.6% / 5137

(changes due to changing distribution of wind inside Germany).
After the change in 2020:

onwind: 22.2% / 1951
offwind-ac: 38.7% / 3387
offwind-dc: n/a

in 2045:

onwind: 26.3% / 2305
offwind-ac: 40.3% / 3531
offwind-dc: 51.9% / 4547

Before asking for a review for this PR make sure to complete the following checklist:

[x] Workflow with target rule ariadne_all completes without errors
[x] The logic of export_ariadne_variables has been adapted to the changes
[ ] One or several figures that validate the changes in the PR have been posted as a comment
[ ] A brief description of the changes has been added to Changelog.md
[x] The latest main has been merged into the PR
[x] The config has a new prefix of the format YYYYMMDDdescriptive_title

These changes might be a little too drastic. Offwind does not get built anymore (just when forced in).
Before:

After:

And looking at the European energy balance:
Before:

After:

That's a 365H simulation


Don't pass query string parameters to Google Analytics

We're unnecessarily fragmenting our pageviews:

Fixed.


remove the use of the analysis server --dartpad command line option

remove the use of the analysis server --dartpad command line option

This is a fairly dartpad specific feature of the analysis server - I think we're better off guarding against file paths in the dartpad backend, and not having much if any dartpad specific knowledge in the analysis server.

@domesticmouse @johnpryan @RedBrogdon - we're about to remove the --dartpad flag from the analysis server; I just want to confirm that this PR is in all the active branches of dartpad? I know it's in master, but I'm not sure if the nnbd branch is active or has this change.

I'm upgrading the nnbd branch with master in the nnbd2 branch. I deployed in on Friday but compilation broke
Analysis is working as expected on that branch, so I think it's okay to remove this flag.

As long as that branch has this commit (2dcc621) we should be good.


Adding export button to vis panel

Left to do (that I'm hoping @alex-r-bigelow will help with)

[x] Create export icon in vis title bar (currently a green checkmark)
[x] Create download icons in export overlay
[ ] When the vis panel is collapsed, the button doesn't work (I think the vis is undefined). Simplest seems to be to remove the export option when the view is collapsed.

Yes, to avoid unnecessary (and probably buggy) render calls to vis components when their container will have a size of zero, the component is destroyed altogether when the widget is collapsed.
Idea 1: I wonder if it would be better to just move the containers offscreen when the widgets are collapsed—this would do a few things. Any state inside the vis component would be preserved (e.g. geo viewport, UpSet choices of which sets to show, etc). It would also make it easy for us to specify an image size in the download, instead of just using the size that the vis happens to be in the browser (probably an icebox feature).
Idea 2: I've played a little with just forcing the vis panel open when the export button is clicked, but it looks like there are several debouncing / timing problems. Potentially, the vis component potentially might not even get instantiated until after a client-side dataset parse (or in the future, pulling a page of items from the server). This isn't a big deal for the actual serialization (vis shouldn't be undefined anymore in the time it takes the user to click the button), but to get at serializationFormats in the first place, this is a problem. Maybe we could just access serializationFormats statically from candela?
Idea 3: We could add stuff to disable the export button unless the view is open. The problem here is we don't have any code / design for disabling widget buttons yet. Weirdly, idea 1 may be less work.

Idea 3 seems much simpler to me. Couldn't the lines here just be changed to
if (!widgetIsShowing) {
    this.vis = undefined;
    // Remove Export button
} else {
    // Add Export button
}

On a side note, there has been a time or two where I wished serializationFormats was static also, so that is worth considering.

It gets a little messier than that... the widget panel stuff (including the icons) are rendered before the actual widget itself. So you'd have to do a double render to actually get the icon to show up + something to prevent an endless render loop. Or we could insert the icon directly in VisualizationView's render call, but that would duplicate code—not to mention messing with the same piece of the DOM from two totally different places.
In the long run, I imagine we'd want Idea 1 anyway (if we do it right, it could help fix #260 and #262)... it may be as simple as a couple CSS tweaks. I'll take a crack at it this morning.

@jeffbaumes I think this is ready.

@alex-r-bigelow's changes/icons LGTM. I talked to @ronichoudhury and he's ok with merging even though there is a spurious failure on heatmap that is unrelated to this branch.


CIS charts are not available even after adding the catalog/repo

What kind of request is this (question/bug/enhancement/feature request): bug
Steps to reproduce (least amount of steps as possible):

Navigate to Apps --> Repositories -->Add a repo in dashboard URL: https://github.com/prachidamle/charts.git and branch: cis-v2-chart
Go to charts
CIS benchmark charts are NOT available.

Expected Result:
CIS benchmark charts should be available
Environment information

Rancher version (rancher/rancher/rancher/server image tag or shown bottom left in the UI): master-head - commit id: 9b6984d5f
Installation option (single install/HA): HA

Cluster information

Cluster type (Hosted/Infrastructure Provider/Custom/Imported): imported rks k8s
Kubernetes version (use kubectl version):

1.18

CIS chart wont be available until it is merged into rancher/charts
After merging some parts are automated to add it to the http://charts.rancher.io/index.yaml - The github actions flow for the rancher/charts repo does that once the chart is merged.
Until then a chart can be tested using usual helm cli by forking the chart branch to local setup

Able to deploy charts using the helm command by cloning the chart branch into local.


Added Konfio to 'Who uses Superset' list.

We're very happy using superset in Konfío. You guys are doing a great job :)

Coverage remained the same at 69.315% when pulling cb234568099e93dcf3aabbfa21a2d68fd1e382eb on luis-rodriguez:master into 08b7e891a7dd65616aef4177b72b1e8770310d98 on apache:master.