No instructions

Oh dear, I guess unless there's instructions on how to compile or even use goswi, how would anyone know how to use it?
What is the 'Go' package?  When I do 'apt search go', there's about 500 lines of everything that contains the word go, so unless we know exactly what package go is, how can we install it?
How is go compiled?  Only the developer knows this, as there is no instructions.
How does one integrate it into an opensim grid?  again only the developer knows this, because there's no instructions.

In the ReadMe is full instructions. As mentioned therein, the Go you will need to install: https://go.dev/doc/install Then just follow the "Configuration" for the other stuff. She did mention she has not compiled the binaries yet, so you may have to compile it yourself.

I'm looking at the readme now, and I don't see anything that refers to an 'Installation', there is only 'Purpose' explaining how goswi came about, 'Configuration' on how to configure it, 'TLS' on how to use Secure Sockets Layer, 'New Relic' and 'Disclaimers and License', there is nowhere in that 'Readme' is anything that says how to install or even compile it.

Oh!... you're right, @Usalabs, the installation instructions are not obvious at all if you're not a Go developer :-)
First, of course, you need to install Go. Go is a programming language, BTW, which essentially compiles under any platform/operating system, and can cross-compile to any other platform without changing anything but an environment variable. It was originally developed in the mid-2000s by Google's compiler workgroup, which includes famous celebrities from the compiler development community, namely, one of the inventors of the C programming language (55 years ago) and the inventor of the Perl language. As a result, few still living people have more experience in developing programming languages than this Dream Team, and Go is one of their 'modern' creations.
That said, and assuming you're on a Debian/Ubuntu variant (or else you'd not use apt...), you'll need to do
sudo apt install golang
and that should be it. Mind you, the bundled version with Ubuntu is insanely outdated (as most Ubuntu packages are, especially on the LTS versions). I sincerely recommend using the backport from the longsleep PPA: https://launchpad.net/~longsleep/+archive/ubuntu/golang-backports
Simon Eisenmann, the maintainer of that repository, is usually just one or two minor versions behind (and very rarely he even manages to release the binaries as quickly as Google releases them!... but this is not always the case).
If you don't trust third-party PPAs on your system, well, you can always grab the package directly from Google: https://go.dev/dl/
Note that the first entry on the list is usually the bundle with the source code, which you will not need (note: Go compiles itself); you'd be better off with one of the many binaries, depending on the architecture you're on. Go runs natively on lots of processor architectures, but you need the correct binaries. Installing it is quite straightforward (how I wish that other programming languages were that easy...), just download the tar file to /usr/local and extract it. That's all it takes. You might wish to add a symlink to the Go binary afterwards (e.g. sudo ln -s /usr/local/go/bin/go /usr/local/bin, assuming that you do have /usr/local/bin on your path). BTW, Ubuntu and Eisenmann seem to prefer a not-so-obvious installation path for Go, but that's ok, Go can run from anywhere. If you want, you can run it in userland, under your own account (I do that on shared hosting providers, such as Dreamhost and Bluehost, because it's so easy to install and does not require tinkering with any privileged — i.e., root-only — files or directories).
Once you've got the Go compiler up and running, you have a few options to install gOSWI...
The easiest is go install github.com/GwynethLlewelyn/goswi@latest. It will download/upgrade all required dependencies automagically and finally compile everything into a binary, which is dropped on your path. On a decent machine, this should take a few minutes, most of which will be spent downloading everything it requires. The Go compiling tool (called, well, go...) is notoriously quiet, and most of the time it won't write anything on the screen for a long while. You can use the -v flag to show some progress. The theory is that, on most scenarios, Go compiles so fast that it takes far longer to download everything it needs than actually compiling it, so, in most cases, you won't 'need' to see what it's doing.
That's the theory, of course. On a fresh Go installation — or one that has been kept around for quite a long time without any upgrades — the first time it runs, it should take considerably longer (afterwards, the Go compiler tools work incrementally, compiling on demand whatever has been changed on disk (but only that!) and linking every component together.
Go is statically compiled, which means it can run from anywhere and you don't need ever to worry about having the correct libraries in the right places, etc. That also means that the binary will be much bigger than expected! But don't mind its size; it does not mean that the actual application will have to launch everything into memory! Rather, it only loads what it needs, and calls the rest on demand. It's remarkable how this is accomplished so easily across every supported system.
The next step, of course, is to actually install gOSWI itself.
By far, the easiest way is to do go install github.com/GwynethLlewelyn/goswi@latest, which should drop you a freshly compiled binary under $GOPATH/bin/goswi (or $HOME/go/bin if the GOPATH environment variable is not set).
If by any chance you get some errors related to ImageMagick, try installing the required header files with sudo apt install libmagick-dev libmagick-cor-dev libmagickwand-dev. ImageMagick is perhaps the trickiest bit on the whole setup, ranging from "it gives too many errors and is impossible to fix" to "what's ImageMagick and why did I have to worry about it?" YMMV, but I've tested on four different machines, with different architectures and operating systems, and each had its own share of issues.
This might make me reconsider the usage of ImageMagick as a compiled-in library, and delegate it to whatever executable is installed. We'll see what I'll come up with...
Once you've got gOSWI installed, you're welcome to continue reading the rest of the instructions to see how to configure it!

@GwynethLlewelyn I do indeed use Ubuntu, I use headless Ubuntu version 20.04 LTS, on a Dell PowerEdge T710 server with 2x octa core Zeon CPU's each with 8x2 cores (8 physical cores, 8 logical cores), totaling 32 cores, 212GB RAM, and 16TB SSD (8x 2TB) in RAID 5.
I think I would consider this a "decent" machine lol.
If you're wondering why I haven't upgraded Ubuntu to 22.04 LTS, it's because 20.04 has not reached it's EOL yet.
I'll try the golang install and keep you informed of what happens.

Oh! All right then — replace "minutes" by "seconds" then :-) I was thinking more along the lines of the time it takes on a Raspberry Pi Zero 2 W (which is one of the machines I use to do the testing :) ).
Either 20.04 or 22.04 is fine; I believe I have even managed to test it back in the 16.04 days (!). Well, admittedly, it was a very early and rudimentary version... not that the current version is really "advanced"... anyway, the trick, of course, is to use either the longsleep PPA (which also supports many earlier Ubuntu versions), or simply download it from go.dev/dl — your choice!

@GwynethLlewelyn OK, well nothing worked, well, the downloads worked with the go install command:-
go install github.com/GwynethLlewelyn/goswi@latest
Which created a go directory in my user root, oh nobody said if it should be installed as a root or normal user, so I'm trying at as a normal user, but I don't have permissions to delete the go folder to start again, so I had to use root command to recursively delete the go folder, but anyway, when it gets imagemagick, it throws a fit, with:-
 gopkg.in/gographics/imagick.v3/imagick go/pkg/mod/gopkg.in/gographics/imagick.v3@v3.5.0/imagick/affine_matrix.go:8:10: fatal error: MagickWand/MagickWand.h: No such file or directory     8 | #include <MagickWand/MagickWand.h>       |          ^~~~~~~~~~~~~~~~~~~~~~~~~ compilation terminated.
And I have installed everything imagemagick by using:-  sudo apt install imagemagic* magicwand* libmagic*-dev and still there's the error.
A google search found that your latest version of GoSWI needs imagick v3, whereas the latest imagick is 6, and that's probably why it's throwing up that error, it's looking for imagemagick version 3, whereas in fact version 6 is installed, and a full drive search using sudo find / -name MagicWand.h yields nothing found.

/usr/include/ImageMagick-6/wand/MagickWand.h

@Usalabs sorry for the lack of reply :(
Soooo some things...

Aye, you should be able to run everything as a user, and not as root. And, in fact, that's the recommended way of running it!
It's so weird that you needed to delete things as root! Go will only install the system library as root, the rest, well, third-party libraries (or packages, as Go calls them) are supposed to be local for each user and should be easily deleted/removed. Also, there is a Go command for cleaning up things: go help clean for more instructions! It's safer and sure to catch all broken things (well, those that matter, at least.
ImageMagick... whew! Ok, let's try to explain this a bit better. ImageMagick is a C/C++ library for image manipulation which I happen to like a lot (mostly because it has extensive documentation and many of its manipulation algorithms are robust, well-tested, academy-grade algorithms). The C library's current version is actually 7.1. However, the guys from Debian have something strange against version 7, and Ubuntu Linux — even 24.04! — strictly follows Debian and therefore still sticks to version 6, and that's what you found to be the "latest" version. 7 is not really extraordinarily different from 6, and most applications don't necessarily require the "latest and greatest", so I guess that's why Ubuntu is still sticking to 6.9.
In order for Go to directly access a C/C++ library, it needs a "wrapper package" — a fancy name just to say that, on one side, you have Go functions (which your Go code will happily call), and on the other side, you have C functions. The so-called CGO interface is what deals with passing arguments and calling functions between the languages. This is important for huge, carefully fine-tuned libraries — which is what ImageMagick is — written in superfast C code, and which would simply take eternities to fully port to Go.  There might be many other Go packages around which do the same, but, for my purposes, I used gopkg.in/gographics/imagick.v3/imagick, of which the latest version is 3.7.0. That's the version of the Go package — not of ImageMagick.
I now realise that I never thought that people would still use ImageMagick version 6. But the nice guys at GoGraphics have thought about that, and, therefore, they have three versions. Version 3, which I use, is for ImageMagick 7 (see their README). Version 2 is for ImageMagick 6.9 — what everybody has by default on Debian & derivatives. And version 1 is for ImageMagick 6.7, which nobody should be using right now, except possibly for some embedded devices (such as NAS and similar things) which might not be upgradeable.
And as a side-note, you most definitely don't need to "Search on Google to see what ImageMagick version I'm using" :) All packages and dependencies of Go are written to two files, go.mod and go.sum. The first shows the direct and indirect dependencies used by the package; go.sum goes far further, showing all versions and subversions it has downloaded over time and which are available for the current package to use. These are generated automatically, and are in plain ASCII (not even JSON or XML or YAML). There are no surprises there: either a package is listed there, or it isn't used. Granted, these are just Go packages, not any external non-Go libraries. A cool thing is that the first column of these files is actually an URL to where the package is hosted, and, in most cases, it will open directly into its README.

That said... you have essentially two options.
The first is to simply change everything in the Go code to use gopkg.in/gographics/imagick.v2/imagick. It's a simple search & replace, really. Then build everything from scratch again. Obviously, you really need to have a working ImageMagick development environment — libraries and header files — which apparently are either missing or misplaced in your system. As @Deiiji explained, if MagickWand.h is not on that path, it means that something is missing (or, worse, broken).
As far as I could figure it out, these are the two only Ubuntu packages you need to install:
$ sudo apt install libmagickcore-6.q16-dev libmagick++-6.q16-dev

Give it a try :) Check for /usr/include/ImageMagick-6/wand/MagickWand.h. Once it's there, you know that you have installed everything you needed to compile things with ImageMagick support (not only Go-related software).
The second option is to go wild and install ImageMagick 7, and let the Go code alone :)
Depending on what else you do on your system, this might be either an excellent idea, or a very very bad one.
There are plenty of instructions how to accomplish that:
https://stackoverflow.com/questions/74951619/how-to-install-imagemagick-7-on-ubuntu-image
https://askubuntu.com/questions/1042436/how-to-install-delegate-libraries-for-image-magick-7-0-7
It's not too hard to do, just a bit... challenging, IMHO. It requires lots of dependencies to get just the basic formats to be understood and manipulated. At the very least, you should make sure you get support for JPEG, PNG, JPEG2000, Targa (TGA) — all of which are actively being used by OpenSimulator — and optionally BMP and TIFF (mostly for supporting ancient formats which have been more popularly used a couple of decades ago, and a few of those might still be around).
The main problem with self-compiling ImageMagick is its side-effects. For instance, since PHP also encapsulates ImageMagick as part of its php-magick module, it means that you'll need to recompile it and link it to the new library — otherwise, Apache/nginx/etc. won't be able to load that module, and that can have some terrible consequences for some web-based applications.
But if you're not running anything that uses PHP (or none of them require ImageMagick to work), then you'll be fine.
Happy compiling 😁

Closing, since @Usalabs has not provided any further feedback for half a year now, so I'm assuming everything is working for them again!


Root Download

Hi, I've noticed that all downloads will end-up on their respective directory... Eg. {ArtistName} - {AlbumTitle} - [{AlbumYear}]
Is there a way to download the files directly to a specific path: Eg Download Folder

Why would you close this?


Added 00_basic and 01_tips_n_tricks examples

Added 00_basic and 01_tips_n_tricks examples from the pymechanical repo to this repo. Below is what the remote examples webpage will look like with these changes.

@klmcadams Great job. I mostly made minor edits, changing titles to sentence case. Based on the screen captures, other content in the Mechanical examples should be edited in a similar manner. Did you want me to check out this branch and do an edit of all the examples?

@PipKat Thank you! I applied your suggestions to the rest of the files in this repository. If you see anything that should still be changed, could you let me know? If it would be easier, feel free to check out this branch and edit the examples instead


Proposal: Logically group commands

When a user does kf, they get the following:
Usage:
  kf [flags]
  kf [command]

Available Commands:
  apps              List pushed apps
  bind-service      Bind a service instance to an app
  bindings          List bindings
  buildpacks        List buildpacks in current builder.
  create-service    Create a service instance
  delete            Delete an existing app
  delete-service    Delete a service instance
  doctor            Doctor runs validation tests against one or more components
  env               List the names and values of the environment variables for an app
  help              Help about any command
  marketplace       List available offerings in the marketplace
  proxy             Creates a proxy to an app on a local port.
  push              Push a new app or sync changes to an existing app
  service           Show service instance info
  services          List all service instances in the target namespace
  set-env           Set an environment variable for an app
  unbind-service    Unbind a service instance from an app
  unset-env         Unset an environment variable for an app
  upload-buildpacks Create and upload a new buildpacks builder. This is used to set the available buildpacks that are used while pushing an app.
  vcap-services     Print the VCAP_SERVICES environment variable for an app

Flags:
      --built-in            do not use remote override commands from CRD
  -h, --help                help for kf
      --kubeconfig string   kubectl config file (default is $HOME/.kube/config)
      --namespace string    kubernetes namespace (default "default")
  -v, --verbose             make the operation more talkative

Use "kf [command] --help" for more information about a command.

This can be overwhelming as the commands are not grouped by functionality (e.g., service commands are mixed in with push commands).

We might be able to use the same template library that Kubernetes does to do this with kubectl: https://github.com/kubernetes/kubernetes/blob/master/pkg/kubectl/cmd/cmd.go#L463
https://github.com/kubernetes/kubernetes/blob/master/pkg/kubectl/util/templates/templater.go

Relevant issue: https://github.com/spf13/cobra/issues/836

We should fix that cobra issue. That would be pretty cool

I'm going to use the k8s template package. It seems to be a solid solution to the problem.


toggle-article-read (N) does not undelete an article marked for deletion (D)

Hi All,
I'm using the current head. The issue is all in the subject, it looks like a bug to me, but perhaps it's a feature?
Imagine you deleted an article and then changed your mind, and want to mark it as unread. With the current version of Newsbeuter what you do is:
D (to delete it) - D (to undelete it) - N (to mark it as unread)

... but it feels more natural from a user point of view if it was sufficient to do:
D (to delete it) - N (to undelete it and mark it as unread)

Note that the reverse is not true: an article can go from N to D without being read first.
What do you reckon?

Yes, you're totally right, N should undelete and mark as read. Will fix in 2.11.

Yes, 2.10 isn't officially out yet because I don't have access to all the infrastructure, like newsbeuter.org. I've shot an email to @akrennmair but haven't heard back yet—maybe he's on vacation or something. I don't do tags and GitHub releases because I don't want to step on his toes. I'm using this pause as a break, too—no coding is being done, I only respond to issues and whatnot.

I understand, is there some way to say thanks for your work btw?

Words work just fine ;)


Error in html with params.ananke_socials = "twitter"

Put my url in config.toml and set params.ananke_socials to name: "twitter".
The resulting html in the svg of the icon contains {{ .fill }} and a semi-colon in the style of the new-window class : fill:;.

Thanks for this, we have a release coming up to day, this will be addressed by it.


Pretraining from a checkpoint

Is there a way to run the pretraining of the model from a checkpoint? I'm unable to run it all at once and I don't see a way to do this.

Did you figure a way out @imharris2702?


Error: The requested operation cannot be performed on a file with a user-mapped section open.

I have played with enabling SSL on Windows 7 by link  https://github.com/edenhill/librdkafka/wiki/Using-SSL-with-librdkafka, changed server.properties file, then got error on starting kafka: The requested operation cannot be performed on a file with a user-mapped section open.
I rollbacked changes but error is still here. I even unpack new version of kafka in another folder, but still have the same issue.

Is this a broker error? Try https://kafka.apache.org/contact, this is the issue section for the C# client only, I have no experience running a broker on Windows.


Add Node Packages to solution

Is it possible to add other node packages to be used with Electron.
For instance i wanted to add NodeGit.

Oh - great question! @GregorBiswanger, any ideas? Maybe users could add additional npm packages in the electron.manifest.json and we install them and to invoke them we would need a more generic API, something like Electron.Invoke(...)?

i'm not a maintener here, but it might be a good idea to think OPT-IN for few feature in order to decouple stuff and avoid a monolith effect on init and code ;)

It´s a good idea.. I marked it as a feature request.. We can implement it..

@newblord & community: How do you like to use the integration feature? To include a npm package is one part.. but how do you like to integrate own node code? I think to use electron-edge is here a good solution.. but I have not tried it before..
Or should we execute a own javascript file in electrons node container?
As example:

You have a JS-File with your logic in node.
In Electron.NET call Electron.Invoke("myLogic.js");

Do you like the second one? It´s easy for me to implement it..

@GregorBiswanger did you guys remove the stock node backend when you added the dotnet backend? If not, couldn't we just run the JS in the node backend (where it would behave the way one would expect). If the stock node backend was removed, would it be possible to have a config setting that adds it back in when desired?


Set GeoIP default database paths to empty

Change the default GeoIP file location to empty, unless database files exist in /data/moloch/etc
Clearly describe the problem and solution
As GeoIP now requires a license key, change the default setting not to use GeoIP unless database files exist.
Relevant issue number(s) if applicable
#1350 is still broken but it will no longer cause the capture service to stop as it will no longer look for GeoIP databases
Did you run npm run lint from the viewer or parliament directory (whichever you are making changes to) and correct any errors
n/a
Did you Ensure that all tests still pass by navigating to the tests directory and running ./tests.pl --viewer
yes
License
I confirm that this contribution is made under an Apache 2.0 license and that I have the authority necessary to make this contribution on behalf of its copyright owner.

Thanks, went with a different solution.
FYI, you can call moloch_config_str(keyfile... with NULL and it will do the right thing.


disks created by packer are not deleted

the OS disk of the temporary VM used to build an image is not removed by packer

Open issue on packer https://github.com/hashicorp/packer/issues/11260


Various TCP serialization stuff

fallocate: fallocate failed: No space left on device

jenkins test please

jenkins test please


Add addressMap in Storefront

Add https://github.com/sportium-fan/sportium-contract/commit/c771954498960f2ed815086c8b4e48db6e963e67 commit


Package filter

Should use settings to pick packaging details.
settings:

export location
package type (mcpack, mcaddon?)
path to world to package it with
option to clear data from world like player data?
what else do we need for packaging?

Closing, lets implement this in Core


Add Bootstrap 5 theme

Bootstrap 5 is in beta2 and will soon be in RC stage. There won't be many changes to be expected so we could already start with a theme skeleton. Support from early adopters is highly appreciated.

select fields are missing "form-select" class, causing them to not render the arrow down on the right

Thanks for the hin @ferjep would you mind opening a PR where this is added? I will review and publish asap


Add explicit PR trigger to azure pipelines

Summary
According to the trigger docs for azure [1] not specifying a pr field in
the config should have an implicit pr trigger on all branches.
However, this default PR trigger has stopped working. This commit adds a
manual pr trigger field in an attempt to workaround this issue. It has
been reported that manually adding the PR trigger will resolve the
issue. [2]
Details and comments
[1] https://docs.microsoft.com/en-us/azure/devops/pipelines/build/triggers?view=azure-devops&tabs=yaml#pr-triggers
[2] https://developercommunity.visualstudio.com/comments/949243/view.html

Yep, it looks like this did the trick, the azure pipelines jobs are running again: https://github.com/Qiskit/qiskit-terra/pull/3977/checks?check_run_id=508285084

I've reverted the 2 temporary workaround switching back to travis now that azure runs on PRs again.


Update README.md

hacktoberfest pr accepted

Make some good changes bro not that simple, add some value in this project


320 authentication client for frontend

Basics

[ ] Details of what you changed are in commit messages.
[ ] References to issues, e.g. close #X, are in the commit messages.
[ ] The buildserver is happy.
[ ] The PR is rebased with current master.

Checklist

[ ] I added unit tests for my code
[ ] I fully described what my PR does in the documentation
(not in the PR description)
[ ] I fixed all affected documentation
[ ] I fixed all affected decisions
[ ] I added code comments, logging, and assertions as appropriate
[ ] I translated all strings visible to the user
[ ] I mentioned every code or binary not directly written or done by me in reuse syntax

Review

[ ] I've tested the code
[ ] I've read through the whole code
[ ] Documentation is conforming to our Documentation Guidelines
[ ] Examples are well chosen and understandable
[ ] Code is conforming to our Coding Guidelines
[ ] Code is consistent to our Design Decisions

Target date to merge this PR: Tuesday 14:00.

One quite nasty bug: when the frontend cannot reach keycloak or backend anymore, the whole landing page gets replaced by:

Expected behavior:
User simply gets logged out by timeout and still sees the landing page.
Can also be fixed by follow-up issue, but please create the follow-up issues first.

One quite nasty bug: when the frontend cannot reach something (keycloak or backend?) anymore, the whole landing page gets replaced by:

Expected behavior: User simply gets logged out by timeout and still sees the landing page.
Can also be fixed by follow-up issue, but please create the follow-up issues first.

This happens when the backend isn't reachable.
Good point though. There is no reason why the landing page should not be displayed. I will look into it.

One quite nasty bug: when the frontend cannot reach something (keycloak or backend?) anymore, the whole landing page gets replaced by:

Expected behavior: User simply gets logged out by timeout and still sees the landing page.
Can also be fixed by follow-up issue, but please create the follow-up issues first.

This happens when the backend isn't reachable. Good point though. There is no reason why the landing page should not be displayed. I will look into it.

Unfortunately there is no easy fix for this.
The AuthProvider expects the correct configuration. We can delay the initialization of the AuthProvider and wait for the configuration from the backend and then intitialize it.
If the backend is down the AuthProvider never receives the config and we can return an error message.
This was our first approach. This leads to the problem that nothing except an error message is displayed because the AuthProvider can't be initialized.
We tried to fix this by passing a default config.
Then wait for the config from the backend (until it is online again) and then rerendering the AuthProvider component.
This can achieved by providing a key prop:
const config = data ?? defaultConfig;
return <AuthProvider key={config.authority} {...config}>{children}</AuthProvider>;
Now the problem is that once the configuration has changed and the AuthProvider is reloaded the login does not work anymore.

@Bushuo @badnames @buenaflor can you take a look here?

jenkins build please

One quite nasty bug: when the frontend cannot reach something (keycloak or backend?) anymore, the whole landing page gets replaced by:

Expected behavior: User simply gets logged out by timeout and still sees the landing page.
Can also be fixed by follow-up issue, but please create the follow-up issues first.

This happens when the backend isn't reachable. Good point though. There is no reason why the landing page should not be displayed. I will look into it.

Unfortunately there is no easy fix for this. The AuthProvider expects the correct configuration. We can delay the initialization of the AuthProvider and wait for the configuration from the backend and then intitialize it. If the backend is down the AuthProvider never receives the config and we can return an error message. This was our first approach. This leads to the problem that nothing except an error message is displayed because the AuthProvider can't be initialized.
We tried to fix this by passing a default config. Then wait for the config from the backend (until it is online again) and then rerendering the AuthProvider component. This can achieved by providing a key prop:
const config = data ?? defaultConfig; return <AuthProvider key={config.authority} {...config}>{children}</AuthProvider>;
Now the problem is that once the configuration has changed and the AuthProvider is reloaded the login does not work anymore.
I have created a seperate issue for this here: #365

This issue is now fixed in #365

@markus2330 should be done

pr.permaplant.net should be tested too

Finally done! Great job!


Handle localized_build_info as env value PILOT_LOCALIZED_BUILD_INFO

New Issue Checklist

[x] Updated fastlane to the latest version
[x] I read the Contribution Guidelines
[x] I read docs.fastlane.tools
[x] I searched for existing GitHub issues

Issue Description
I want to transform
upload_to_testflight(
    localized_build_info: {
      "default": {
        whats_new: "LIVE Version"
      },
      "en-GB": {
        whats_new: "LIVE Version"
      }
    }
  )

into
PILOT_LOCALIZED_BUILD_INFO = '{"default":{"whats_new":"LIVE Version"},"en-GB":{"whats_new":"LIVE Version"}}'
but it doesn't work
the upload to TestFlight is fine without errors, but the test description is always empty
Environment
Latest fastlane v2.195.0

still exist


Why the mark is reduced by nearly half when run the test in docker container.

Generally, the docker container's extra CPU consumption is able to be dismissed.
However, the fact is conflicted.
Specifically, I ran a sysbench test both in docker and in bare machine. The result is almost reduced to half.
For test, you can use sudo docker run --rm -it cfbsks/docker-images:alpine python3 app.py

Yes, it is possible to use Docker in Linux for testing, but Docker for Windows and macOS runs in a virtual machine.

Yes, it is possible to use Docker in Linux for testing, but Docker for Windows and macOS runs in a virtual machine.

You might misunderstood what I said. I have already update the issue.

Sorry, I missed this question, is your environment limiting the performance calls of Docker? In the current test list, the 'M1 virtual 虚拟机 Linux' runs with Docker, while the 'M1 macOS' runs natively. The difference between the two is only in multi-core calls, and Docker will not take up all the performance of macOS.

Yes, it is possible to use Docker in Linux for testing, but Docker for Windows and macOS runs in a virtual machine.

You might misunderstood what I said. I have already update the issue.

Sorry, I missed this question, is your environment limiting the performance calls of Docker? In the current test list, the 'M1 虚拟机 Linux' runs with Docker, while the 'M1 macOS' runs natively. The difference between the two is only in multi-core calls, and Docker will not take up all the performance of macOS.

Yes, it is possible to use Docker in Linux for testing, but Docker for Windows and macOS runs in a virtual machine.

You might misunderstood what I said. I have already update the issue.

Sorry, I missed this question, is your environment limiting the performance calls of Docker? In the current test list, the 'M1 虚拟机 Linux' runs with Docker, while the 'M1 macOS' runs natively. The difference between the two is only in multi-core calls, and Docker will not take up all the performance of macOS.

I didnt set any extra limit for Docker, and I tried on the TencentVPS. The point is single-core score under docker was nearly half by bare-machine.
I will try again on my PC, just wait for a few minutes.

Yes, it is possible to use Docker in Linux for testing, but Docker for Windows and macOS runs in a virtual machine.

You might misunderstood what I said. I have already update the issue.

Sorry, I missed this question, is your environment limiting the performance calls of Docker? In the current test list, the 'M1 虚拟机 Linux' runs with Docker, while the 'M1 macOS' runs natively. The difference between the two is only in multi-core calls, and Docker will not take up all the performance of macOS.

I didnt set any extra limit for Docker, and I tried on the TencentVPS. The point is single-core score under docker was nearly half by bare-machine.
I will try again on my PC, just wait for a few minutes.

According to our test results, the performance scheduling of Tencent Cloud is very strange, and the multi-core has not exerted its power at all. Please try other hardware platforms.

Yes, it is possible to use Docker in Linux for testing, but Docker for Windows and macOS runs in a virtual machine.

You might misunderstood what I said. I have already update the issue.

Sorry, I missed this question, is your environment limiting the performance calls of Docker? In the current test list, the 'M1 虚拟机 Linux' runs with Docker, while the 'M1 macOS' runs natively. The difference between the two is only in multi-core calls, and Docker will not take up all the performance of macOS.

I didnt set any extra limit for Docker, and I tried on the TencentVPS. The point is single-core score under docker was nearly half by bare-machine.
I will try again on my PC, just wait for a few minutes.

According to our test results, the performance scheduling of Tencent Cloud is very strange, and the multi-core has not exerted its power at all. Please try other hardware platforms.

I tried several tests. We only consider the single-core test.

on J1900 bare-machine 68.54% in docker alpine image
on E5-2696 v2 bare machine 36.9% in docker alpine image
on E5-2696 v2 bare machine 56.7% in docker ubuntu image
on Amazon Lightsail 1-core 49.5% in docker alpine image

Confused! 😕

Sorry I wasn't clear either, I don't have this problem on macOS.

I retested M1 with Python 3.10 after upgrading Docker on macOS. Got test scores that surpassed previous ones.


Collect anonymous usage

Collected Data
This feature is disabled by default.
Why ?
In order to help us learn more about how Træfik is being used and improve it, we collect anonymous usage statistics from running instances.
Those data help us prioritize our developments and focus on what's more important (for example, which configuration backend is used and which is not used).
What ?
Once a day, we collect:

the Træfik version
the UUID of the instance
an obfuscated and anonymous version of the static configuration (token, user name, password, URL, IP, domain, email, etc, are removed)

We do not collect the dynamic configuration (frontends & backends).
We do not collect data behind the scenes to run advertising programs or to sell such data to third-party.
Here is an example

Source configuration:

[entryPoints]
    [entryPoints.http]
       address = ":80"

[web]
  address = ":8080"

[Docker]
  endpoint = "tcp://<IP_ADDRESS>:2375"
  domain = "foo.bir"
  exposedByDefault = true
  swarmMode = true

  [Docker.TLS]
    CA = "dockerCA"
    Cert = "dockerCert"
    Key = "dockerKey"
    InsecureSkipVerify = true

[ECS]
  Domain = "foo.bar"
  ExposedByDefault = true
  Clusters = ["foo-bar"]
  Region = "us-west-2"
  AccessKeyID = "AccessKeyID"
  SecretAccessKey = "SecretAccessKey"

Obfuscated and anonymous configuration:

[entryPoints]
    [entryPoints.http]
       address = ":80"

[web]
  address = ":8080"

[Docker]
  Endpoint = "xxxx"
  Domain = "xxxx"
  ExposedByDefault = true
  SwarmMode = true

  [Docker.TLS]
    CA = "xxxx"
    Cert = "xxxx"
    Key = "xxxx"
    InsecureSkipVerify = false

[ECS]
  Domain = "xxxx"
  ExposedByDefault = true
  Clusters = []
  Region = "us-west-2"
  AccessKeyID = "xxxx"
  SecretAccessKey = "xxxx"

Show me the code !
If you want to dig into more details, here is the source code of the collecting system: collector.go
By default we obfuscate all configuration fields, except fields tagged with export=true.
How to enable this ?
You can enable the collecting system by:

adding this line in the configuration TOML file:

# Send anonymous usage data
#
# Optional
# Default: false
#
sendAnonymousData = true

adding this flag in the CLI:

./traefik --sendAnonymousData=true

This should be rolled out with care, as some people might be using workarounds in their config for missing features, a la https://github.com/containous/traefik/issues/751#issuecomment-292169545

@george-angel we don't export the dynamic configuration of Traefik (which contains frontends & backends), so we don't see any risk of data leak.
But you are right, this feature should be rolled out with care, that's why we carefully tested it, and that's why we ask people to review it here :)
If you have any doubt on this, you are welcome to drop a comment here.

Thanks @emilevauge
Could you clarify regarding dynamic configuration exclusion. Does that include all frontends, or the ones creating via docker/kubernetes?
My example its a frontend matching a Host with a secret value defined in traefik.toml.

@george-angel frontends & backends defined in your toml will also be excluded. Those are part of the dynamic configuration. You could have defined those in a separate file, but you can also choose to merge your static & dynamic configuration in one toml file (like you did).
In one word, frontends & backends are not collected (obviously :) ).

@alkar, @egtann, @kachkaev: I'm curious to understand why you reacted with :-1: / :confused: to this PR.
I'm sure your understand why we need to get some usage metrics to better understand our community and improve Traefik accordingly. Could you elaborate?

Thanks for offering to leave feedback @emilevauge! I'm personally a bit confused about the fact that the option is true by default, however I think I understand why it it so.
Given that this is a last-minute PR for 1.4, could the option be made false by default to avoid bugs in critical environments in its early days? Then once this functionality matures, you can maybe release 2.0 with sendAnonymousData = true by default and clearly explain what this means in the changelog. Quickly upgrading from 1.3 to 1.4 and later realising that you've been tracked for quite some time may frustrate a lot of users. May be risky for traefik's reputation IMO.

@emilevauge great, thank you.

@kachkaev Thanks for your feedback !
We need more usage stats (for example, which version is still deployed, etc), to know better how Traefik is deployed. We just need anonymous data, we really really don't care about something else ;)
But we really don't want to upset our community.
So let's disable this option to by default for now. But we need your help to enable this by default in the future, without loosing your trust :)

@emilevauge although I understand that the data you're going to collect can be useful for the team, there's two points that actually make me sceptical:

this feature is enabled by default and users could potentially be unaware when upgrading a minor version, like @kachkaev explained

you'll be extracting information from the config which is always dangerous in a sense

To be perfectly honest, I don't see how such a feature makes sense to be a core part of a reverse proxy - to my knowledge it's a first.

@alkar The feature is disabled by default.

@ldez I am aware, I read Emile's comment above.

Following all the feedback from the community, we think it's better to close the PR and not ship this feature in 1.4. We don't want to rush, we shouldn't have tried to add this to 1.4 (I thought it would be "ok" but it's not ^^).
I will instead open a proposal to explain why we (developers) need more stats and which data we need precisely. We really need your help to build something that match the developers and the users needs.

A proposal is alive here #2172 :)


Fix postcss-modules being required as a dependency in projects

Changes

Use require rather than NATIVE_REQUIRE to import postcss and postcss-modules so that they end up in Snowpack's own bundle, meaning that Snowpack projects do not need to install these packages themselves.
This reverts a change in #2008 and fixes #2256.
Testing

I haven't added any automated tests, but manually tested that this works in a project where the issue was occurring. Please let me know if automated testing is needed for this PR and the best way to go about doing so for this change :)
Docs

Bug fix only so no docs updated

Thank you! I think I originally moved them to NATIVE_REQUIRE because they were having trouble bundling, so lets see if CI passes here. I'll do some manual testing as well before merging. Thanks for taking a look at this!

Thank you! I think I originally moved them to NATIVE_REQUIRE because they were having trouble bundling, so lets see if CI passes here. I'll do some manual testing as well before merging. Thanks for taking a look at this!

 :)
On CI, it seems to be failing but for an unrelated reason - the main branch is also failing, and oddly all tests passed despite the exit code of 1 😕

You're welcome! :)
On CI, it seems to be failing but for an unrelated reason - the main branch is also failing, and oddly all tests passed despite the exit code of 1 😕

Whoops, that was my bad, I was isolating a test last night and forgot to turn off the it.only() call. Just pushed a fix for that to main, if you want to rebase.

 Just pushed a fix for that to main, if you want to rebase.

Thanks! I think there's now a new issue possibly related to #2251?

Thanks! I think there's now a new issue possibly related to #2251?

Passing at least on Linux CI now 🎉
Side note for the meantime: is there a reason to use require within the function, rather than using import statements for postcss and postcss-modules at the top of this file like other imports? I can see it was done that way even before #2008 so wondering the reason for this.

Passing at least on Linux CI now 🎉
Side note for the meantime: is there a reason to use require within the function, rather than using import statements for postcss and postcss-modules at the top of this file like other imports? I can see it was done that way even before #2008 so wondering the reason for this.

I believe it was originally for performance, but now that we're bundling into a single JS file that doesn't really matter anymore.
To at least unblock people for the v3.0.0 release, I'm going to move these back into regular "dependencies" for now. But getting them supported via bundling and moving them back out is definitely still a priority.

I believe it was originally for performance, but now that we're bundling into a single JS file that doesn't really matter anymore.
To at least unblock people for the v3.0.0 release, I'm going to move these back into regular "dependencies" for now. But getting them supported via bundling and moving them back out is definitely still a priority.

I believe it was originally for performance, but now that we're bundling into a single JS file that doesn't really matter anymore.

On that basis I've updated this PR to use ES imports.

To at least unblock people for the v3.0.0 release, I'm going to move these back into regular "dependencies" for now in a separate commit. But getting them supported via bundling and moving them back out is definitely still a priority.

Sounds good!

I believe it was originally for performance, but now that we're bundling into a single JS file that doesn't really matter anymore.

On that basis I've updated this PR to use ES imports.

To at least unblock people for the v3.0.0 release, I'm going to move these back into regular "dependencies" for now in a separate commit. But getting them supported via bundling and moving them back out is definitely still a priority.

Sounds good!

Confirmed that this is working, thanks for fixing! Back down to (almost) zero deps!

Confirmed that this is working, thanks for fixing! Back down to (almost) zero deps!


[Hub Generated] Review request for Microsoft.CostManagement to add version 2019-03-01-preview

Main changes:

Field changes related to CloudConnector,ExternalBillingAccount,ExternalSubscription
Remove API POST: /providers/Microsoft.Management/managementGroups/{managementGroupId}/providers/Microsoft.CostManagement/getEntities
Add API PUT:
/providers/Microsoft.Management/managementGroups/{managementGroupId}/providers/Microsoft.CostManagement/externalSubscriptions
Reformat costmanagement.json with VisualStudio Code
Fix typo Managment -> Management

Details of Field changes:

CloudConnector: renamed providerAccountId to providerBillingAccountId
CloudConnector: added providerBillingAccountDisplayName, externalBillingAccountId
CloudConnector: changed status to be readonly (no longer part of PUT)
CloudConnector: changed PATCH to not take a connector properties, and therefore to be used only for verifying an existing cloudconnector
ExternalBillingAccount: added providerBillingAccountId, connectorId
ExternalBillingAccount: added GET $expand=collectionInfo
ExternalSubscription: added providerBillingAccountId, providerAccountId
ExternalSubscription: added GET $expand=collectionInfo

If you are a MSFT employee you can view your work branch via this link.
Contribution checklist:

[x] I have reviewed the documentation for the workflow.
[x] Validation tools were run on swagger spec(s) and have all been fixed in this PR.

Automation for azure-sdk-for-js

Automation for azure-sdk-for-python

Automation for azure-sdk-for-node

Automation for azure-sdk-for-ruby

Can one of the admins verify this patch?

Automation for azure-sdk-for-go

@AutorestCI regenerate azure-sdk-for-go

Automation for azure-sdk-for-java

@AutorestCI regenerate azure-sdk-for-go

@sergey-shandar Can you look into the issue with the Defrault build issue?
https://azuresdkci.westus2.cloudapp.azure.com/job/DotNetSwaggerToSdkCI/73/

startbuild

startbuild

@praries880 ignore failures on "default" job.
We recently renamed the job to "Automation for azure-sdk-for-net"

Arieh, There are lot of breaking changes and must be done in new api version.

    "operationId": "CloudConnector_Verify",

why renaming a patch operation as '_verify' , instead of '_update' ?

Refers to: specification/cost-management/resource-manager/Microsoft.CostManagement/preview/2019-03-01-preview/costmanagement.json:1326 in ef9b6d3. [](commit_id = ef9b6d3914b85107a9d26a999f30f44c3564395f, deletion_comment = False)

Automation for azure-sdk-for-net
A PR has been created for you:
https://github.com/azure/azure-sdk-for-net/pull/-1
.NET SDK Commits:
https://github.com/adxsdknet/azure-sdk-for-net/pull/-1/commits/

    "operationId": "CloudConnector_Verify",

why renaming a patch operation as '_verify' , instead of '_update' ?
Refers to: specification/cost-management/resource-manager/Microsoft.CostManagement/preview/2019-03-01-preview/costmanagement.json:1326 in ef9b6d3. [](commit_id = ef9b6d3, deletion_comment = False)

Renamed _verify to _update

Automation for azure-sdk-for-net
A PR has been created for you:
https://github.com/azure/azure-sdk-for-net/pull/-1
.NET SDK Commits:
https://github.com/adxsdknet/azure-sdk-for-net/pull/-1/commits/

@sanjaiganesh / @antmarti-microsoft Can you validate that the latest commits handle the ARM feeback?

Automation for azure-sdk-for-net
A PR has been created for you:
https://github.com/azure/azure-sdk-for-net/pull/-1
.NET SDK Commits:
https://github.com/adxsdknet/azure-sdk-for-net/pull/-1/commits/


x/crypto: add chacha20, xchacha20

Package chacha20 currently lives at x/crypto/internal/chacha20 which is not importable by users outside of x/crypto. Please move it to x/crypto/chacha20. Additionally, please make the API similar to x/crypto/salsa20 (along with its subpackage x/crypto/salsa20/salsa) as the two are extremely similar.
Background: x/crypto/internal/chacha20 was previously located at x/crypto/chacha20poly1305/internal/chacha20. It was moved up one level to be imported by x/crypto/ssh.

Related: #23885 (add support for XChaCha20).

(CC: @FiloSottile)

It sounds like doing x/crypto/chacha20 and x/crypto/xchacha20 is OK (or maybe just one package), but @agl and @FiloSottile will need to think a bit more about what the API should be. Because the current code is internal, not as much care has been taken with the API details.

The proposal is approved but the API is still yet to be decided.

If everyone is okay with it, I'll send a CL based on https://github.com/aead/chacha20.

We'll want a AEAD version of XChaCha20, and we don't want to expose HChaCha20, so we have some work to do on the API.

But a chacha20 package should expose the XChaCha20 variant (as stream cipher / XORKeystream) too?
If so we probably have to duplicate the HChaCha20 logic.
Another question is whether it's worth to add all the optimized asm implementations (SSE,AVX(2) for x86/amd64 and NEON for arm64)?  Like shown by Vlad's chacha20poly1305 implementation we can get the best performance for the AEAD by combining the chacha20 and poly1305 implementations.

Is there a published security analysis of XChaCha20?
We wanted to add it to Tink, but decided not to because we cannot find any published cryptanalysis results. There are plenty results for Salsa20. There's a paper for XSalsa20, but there's nothing for XChaCha20.

@thaidn A security analysis of ChaCha20 can be found here. I'm not aware of a explicit scientific analysis of XChaCha20's HChaCha20 function. However D. Bernstein published an analysis of XSalsa20 containing a security reduction to Salsa20.
The XChaCha20 construction is equivalent to the XSalsa20 expect for using ChaCha20/r and HChaCha20 instead of Salsa20/r and HSalsa20:
XChaCha20 takes a 192 bit nonce where keyxchacha := KDF(key, nonce[0:16]) (the first 128 bit of the nonce) and noncexchacha := nonce[16:24] (the remaining 64 bit of the nonce) where KDF is the HChaCHa20 function.
Conceptually the reduction for XChaCha20 should be the same as for XSalsa20 (D.B. does not assume anything specific about HSalsa20 which is not true for HChaCha20). The security proof for generalized cascades should also work for XChaCha20. So it's at least a reasonable assumption that XChaCha20 is secure if ChaCha20 is secure. However, I haven't done the formal proof.

@riobard

Optimized implementations are really helpful, even just for stream ciphers alone.

Well, you should always prefer (X)ChaCha20Poly1305 over plain (X)ChaCha20. I'm not aware of an reasonable use case for (X)ChaCha20 which could and should not use (X)ChaCha20Poly1305. Assembler code is hard to maintain and it's easy to screw up. We should only add (a lot) of assembler - ChaCha20 asm is a lot - if there is a real benefit.

@aead I respectfully disagree. There are lots of valid use cases where stream ciphers are desired.

@riobard I don't want to start a fundamental discussion about this topic - Providing confidentially but not integrity is considered "not state of the art" and should/must be considered as security issue for almost all use cases. Exceptions may be use cases like PRNG or legacy systems, but these are quite  rare and adding a lot of complexity/maintenance cost is probably not worth it.

@aead You're making too much assumption about how/why people use stream ciphers. Not everything is a nail when you have a hammer. Both stream ciphers and AEAD ciphers have their important use cases, and sometimes they are even used together (e.g. x/crypto/ssh).

@aead IMHO x/crypto/ssh is an important-enough use case to justify optimized chacha20 code. Its use of C20P1305 does not work with cipher.AEAD interface.

In wireguard-go, we're just doing this -- https://git.zx2c4.com/wireguard-go/tree/xchacha20poly1305/xchacha20.go#n142 -- pretty ugly, and I'd very much appreciate having this in x/crypto instead.

The APIs I'm thinking about for golang.org/x/crypto/chacha20 are
func NewUnauthenticated(key []byte) (cipher.Stream, error)
func NewXUnauthenticated(key []byte) (cipher.Stream, error)

returning a cipher.Stream because most other Stream implementations are not type-assertable anyway.
I agree the golang.org/x/crypto/salsa20 API should match, but the one-shot XORKeyStream function is bad because it doesn't match any interface and can't be chunked, even if Salsa and ChaCha have good key agility, so instead let's add NewUnauthenticated to golang.org/x/crypto/salsa20.
Sounds good to everyone who needs these?

@FiloSottile  For low-level crypto code, I think it's better to keep it consistent with DJB's original NaCl and libsodium API, as it makes the job easier to port code from/to C. Fewer things to learn and mess up at least.

@riobard Since we have an idiomatic Go interface which works for a superset of use-cases, we should use it. Matching C APIs is not a goal of the Go crypto libraries.

@FiloSottile, I'm curious why you suggest returning cipher.Stream rather than a concrete type that implements it. What leads you to believe that the chacha20 implementation will never have any interesting methods beyond XORKeyStream?
(See http://golang.org/wiki/CodeReviewComments#interfaces.)

@FiloSottile But the cipher.Stream interface has different signature and semantics than that of salsa20 and chacha20.

Salsa20 differs from many other stream ciphers in that it is message orientated rather than byte orientated. Keystream blocks are not preserved between calls, therefore each side must encrypt/decrypt data with the same segmentation.
Another aspect of this difference is that part of the counter is exposed as a nonce in each call. Encrypting two different messages with the same (key, nonce) pair leads to trivial plaintext recovery. This is analogous to encrypting two different messages with the same key with a traditional stream cipher.

If you give me just a cipher.Stream, I cannot specify nonce. Therefore it's a subset rather than a superset of use cases. I'd still need a way to call the underlying XORKeyStream function somehow.

@bcmills Yeah, this problem appears elsewhere too, e.g. AEAD implementations return cipher.AEAD interface instead of concrete types. Does changing from returning an interface to returning a concrete type implementing that interface violate Go1 compatibility promise? API does change, but nothing should break I guess?

@riobard Ah, no, the issue here is that I forgot the nonce argument to NewUnauthenticated. Now the issue is that I dislike both having two easy to invert []byte arguments, and clunky *[N]byte arguments requiring extra copies and risking incomplete copy()s. The good news is that there is no overlap in nonce and key lengths, so we can catch inversions at runtime, so let's go for
func NewUnauthenticated(nonce, key []byte) (cipher.Stream, error)
func NewXUnauthenticated(nonce, key []byte) (cipher.Stream, error)

Does that make it a superset?
@bcmills Well I can't imagine what else it might be doing, after all the alternative we are discussing is a single XORKeyStream package level function. And the other advantage of returning concretes—type assertions—is blocked by the fact that most other cipher.Stream implementations (from crypto/cipher) are unexported. So a CIpher type felt like API clutter. But maybe it's not a good enough reason to break style?

SetCounter is actually an example of a possible useful method, proving there's a reason style should be followed even if one can't think of why at the moment. Let's have a Cipher type.
And while at it, no need for NewXUnauthenticated when we can look at the nonce length.
import "golang.org/x/crypto/chacha20"
func NewUnauthenticated(nonce, key []byte) (*Cipher, error)
func (*Cipher) XORKeyStream(dst, src []byte)

import "golang.org/x/crypto/salsa20"
func NewUnauthenticated(nonce, key []byte) (*Cipher, error)
func (*Cipher) XORKeyStream(dst, src []byte)
func XORKeyStream(out, in []byte, nonce []byte, key *[32]byte) // Existing.

I'm glad to see this nearly matches the github.com/aead/chacha20 API by @aead.

Ah I see.
In which case I would propose we go for the same API as in https://godoc.org/github.com/aead/chacha20 by @aead and make the main function func NewCipher(nonce, key []byte) (*Cipher, error), as there's nothing about authentication in stream ciphers anyway.
Wait… so why don't we just take @aead's implementation and amend crypto/salsa20 to match that? :D

To summarize the current state:

New struct type Cipher representing a (X)ChaCha20 stream cipher instance.
New function NewUnauthenticated(nonce, key []byte) (*Cipher, error) or
NewCipher(nonce, key []byte) (*Cipher, error).
Cipher implements cipher.Stream (and maybe `SetCounter(...) to allow e.g. random access)

Now some personal opinions:

I can see the idea behind NewUnauthenticated to explicitly mention that the primitive does not provide integrity (IND-CTXT). However, I would go for NewCipher for two reasons:

NewCipher(...) matches the crypto/aes package API that is probably used most frequently. So chacha20.NewCipher(...) will look familiar and consistent.
If there is a type Cipher then it is obvious that NewCipher will create a new instance of that type.
The package doc should mention that chacha20 does not provide integrity, anyway.

It's not really clear to me what's the rationale behind XORKeyStream(out, in []byte, nonce []byte, key *[32]byte) (salsa20 and chacha20 API). It's implementation is pretty much:c, err := NewCipher(nonce, key)
if err != nil {
    panic(err)
}
c.XORKeyStream(dst, src)

Maybe it's worth to implement it just to make code using it a bit simpler - but is
chacha20.XORKeyStream(...) really a common thing to do?!

I can't imagine what else it might be doing, after all the alternative we are discussing is a single XORKeyStream package level function.

The main thing you can do with concrete types is add methods later: for example, methods to report block sizes or the number of blocks encoded, or to seed initial state.
I'm not saying that you need any of those now — just that it's difficult to predict that you will not need them, and if you do the package will be much cleaner if the type on which those methods are documented is the same as one returned by the corresponding New function.

@riobard

Does changing from returning an interface to returning a concrete type implementing that interface violate Go1 compatibility promise?

Yes. Consider the following snippet:
s := cipher.NewCTR(block, iv)
s = chacha20.NewAuthenticated(nonce, key)

@FiloSottile, crypto/rc4.NewCipher is an example of a standard-library that returns a concrete implementation of the cipher.Stream interface. In addition to the XORKeyStream method required by the interface, it provides an additional Reset method.

I definitely want it to be called NewUnauthenticated. chacha20 vs chacha20poly1305 is too subtle a difference, and chacha20 is easier to type. (Otherwise by style when there's only a single type in a package the function should just be called New.)
We should not have a package-level XORKeyStream function in chacha20, I only included it in https://github.com/golang/go/issues/24485#issuecomment-463525235 because it's already in golang.org/x/crypto/salsa20.

In addition to the XORKeyStream method required by the interface, it provides an additional Reset method.

@bcmills I recognized in https://github.com/golang/go/issues/24485#issuecomment-463525235 that you are right, but about Reset... https://go-review.googlesource.com/c/go/+/162297 ;)

@aead Are you taking this? Otherwise I was going to work on it this week.

@FiloSottile I'm okay with you sending the CL. Let me know if I should review :)

@FiloSottile I wouldn't worry too much about the potential confusion about chacha20 and chacha20poly1305 as the two feature vastly different API. Calling it NewUnauthenticated is rather confusing because there's no NewAuthenticated counterpart in any packages. Further, I think your concern should probably be better reflected in documentation if necessary at all.

I'd also be interested in access to chacha20, I'd like a pure Go implementation of libsodium's secretstream (https://download.libsodium.org/doc/secret-key_cryptography/secretstream). Implementing this needs HChaCha20 as the key construction is based on HChaCha20.

I'd also be interested in access to chacha20, I'd like a pure Go implementation of libsodium's secretstream (https://download.libsodium.org/doc/secret-key_cryptography/secretstream). Implementing this needs HChaCha20 as the key construction is based on HChaCha20.

I was looking for the exact same thing.. we need to build a cek using HChaCha20 and use chach20poly1305 (aead for the message) cipher

I'd like to add a use case for ChaCha20. QUIC uses it for protecting the QUIC packet header, see https://tools.ietf.org/html/draft-ietf-quic-tls-22#section-5.4.4.
Unfortunately, as far as I can see, the interface suggested in https://go-review.googlesource.com/c/crypto/+/185991/ would not be sufficient for this use case, since QUIC's header protection algorithm relies on setting both the counter as well as the nonce. It seems like the original interface would be a better fit here.

@marten-seemann Would a SetCounter method help?

Yes, I think a SetCounter method would work, as long as it allow setting the counter to any uint32 value.

Come on,  guys, please add the support for xchacha20-ietf-poly1305

@stevenshea That's already implemented! :)
https://godoc.org/golang.org/x/crypto/chacha20poly1305#NewX


Add CITATION.cff

https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-citation-files
see #49

resolved by #49


Use markdown in notification message

The gist link in the sync success message is broken, because the notification manager uses markdown to format the message.

Notifications use Marked which allows HTML.
I also prefer the link on a new line:

Screenie of this PR:

@antm611 Can you provide some (reproducible) information when the "success message is broken" ...

I can't reproduce the problem either. Does any of you still see this problem (with current up-to-date versions of everything) and can provide a reproducible example?

Let's close this PR. As commented here, HTML is allowed. If someone can provide a reproducible situation we can report this to Atom.


Added fileHighlight function

This is what we were discussing on this issue https://github.com/PrismJS/prism/issues/390
I'm no JavaScript ninja so I don't even know if what I made is correct, but it works for me and it let's me call this function whenever I need it, so I can use it when loading dinamic content.

I'd prefer if the variable was not declared globally. Using it as a property of the Prism object would be better IMO (Prism.fileHighlight(...)).

I don't know if I feel capable to do the task... As I mentioned earlier, I'm no JavaScript ninja :P
If you think that would be useful, be my guest, or have someone else do it, for the sake of Prism! Hehe!

What I'm asking for is in fact just a little change:
Instead of doing this:
var fileHighlight = (function fileHighlight(){
    if (!self.Prism || !self.document || !document.querySelector) {
        return;
    }

    var Extensions = /* ...
        Plugin's code...
    ... */

    return fileHighlight;
}());

I'm suggesting you do this:
(function () {
    if (!self.Prism || !self.document || !document.querySelector) {
        return;
    }

    // Declare it as a property of the Prism object
    self.Prism.fileHighlight = function() {

        var Extensions = /* ...
            Plugin's code...
        ... */

    };

    // Call it immediately
    self.Prism.fileHighlight();
}());

Um, sorry for being thick, but what’s the purpose of this?

It's all explained in issue #390. The purpose is to be able to call fileHighlight dynamically...

Have I done it right? It's works for me.

This looks good to me now ;) Thanks for refactoring it.
Now it's up to @LeaVerou to decide whether to merge it or not.

Merged, thanks!


Inf in spacing stats

spacing_stats_mean is Infinity in https://github.com/fpsim/fpsim/blob/main/tests/baseline.json
This file is generated when update_baselines is run, but the issue seems to be arising somewhere in the extract_birth_spacing method (https://github.com/fpsim/fpsim/blob/main/fpsim/experiment.py#L312)

@robynstuart Related issue - i can have a look this week cause i know you're super busy
https://github.com/fpsim/fpsim/issues/286

I will also take a look at this, as I modified the extract_birth_spacing function for the autocalibration PR

@robynstuart @pausz @MObrien-IDM I think the inf we're seeing in the data portion is because the afb.table.csv country data contains many values of 'Inf' in the afb column, which are currently included in the extraction of the ranked afb values (so end up in the 75th percentile). Prior to the autocalibration PR I made (where we saw this baseline affected), both the afb and spacing data was pulled from Senegal's 'BirthSpacing.obj' file...but with standardizing Senegal data to match that of Kenya (and other locations), we changed the data to pull from afb.table.csv and birth_spacing_dhs.csv. My guess is that the data in BirthSpacing.obj didn't have these inf values whereas the data in afb.table.csv does (hence baseline changed in this regard). I'm not sure why these afb values say Inf (missing data perhaps?) but I can exclude these rows if that's preferable.

@emilydriano - Okay thanks for looking into this - Let's take a look at the underlying data, but we definitely don't want the Inf included.

Opened this issue which addresses the root cause of the issue above

Resolved with #264 ? @robynstuart @emilydriano ?

Resolved with #264 ? @robynstuart @emilydriano ?

@MObrien-IDM I don't think it's resolved with 264, as the root cause is the 'Inf' values which are in the afb (see issue 309, thus we still have Infinity in the baseline.json:


Update standalone containers

Description
This PR updates base VSCode version for standalone containers to 22.04 (21.10 is in EOL since July) and several other components used within the containers.

/deploy-staging build-all

/deploy-staging build-all

/deploy-staging build-all

/merge


Linked Librespot volume control to mopidy default volume

Librespot always started with 50% volume control by default. This edit links the Mopidy setting to the librespot daemon

Good idea. Thanks.


fix: #120 Support users moving between uneven categories

Codecov Report

Merging #121 (d3bf7f1) into main (1e59fa3) will decrease coverage by 0.20%.
The diff coverage is 50.00%.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
@@            Coverage Diff             @@
##             main     #121      +/-   ##
==========================================
- Coverage   99.22%   99.03%   -0.20%
==========================================
  Files          11       11
  Lines        1030     1034       +4
  Branches      241      243       +2
==========================================
+ Hits         1022     1024       +2
- Misses          6        8       +2
  Partials        2        2

Flag
Coverage Δ

unittests
99.03% <50.00%> (-0.20%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

src/c2mChart.ts
98.23% <50.00%> (-0.35%)
:arrow_down:

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


[1.10.2-1.2.1] Satellite Builder UI Item Slots Broken(?) & Broken Space Station Assembler

The satellite builder is connected to power and everything checks out until I try to put in the empty satellite chassis in. The only things I can put into the slots are the Satellite ID chips into the correct slot and I can put anything into the IO slot just to the right of the power indicator. I can't put the satellite chassis in the bottom, I can't put the optical sensor in the top, I can't install memory chips into the lower IO slots and I can't install modules into the module slots.
I'm running Advanced Rocketry version 1.10.2-1.2.1 and libVulpes 1.10.2-0.2.4

1.7.10-1.2.1 have this bug too.

I think this is more of a graphical issue than anything, the IO icon in the top left slot was actually a placeholder for a satellite icon that I forgot to actually put in.  You should be able to have something like the following:

!! But I can"t put anything into it

Do you have an empty chassis in the top right slot?

yep,they are empty,

Try putting a satellite chassis into the top left slot, the behavoir of the machine has been modified so that the upgrades go directly into the satellite in a manner similar to steve's carts.  When trying to test this out I did notice it was not showing up in the vanilla creative menu in 1.7.10 (this is patched for the next build), so you may need to spawn the satellite in via NEI, the give command, or just crafting it.  (The item is advancedrocketry:item.satellite if memory serves)

ya u have to put the chassis in first then the rest will go in properly

Oh ,thanks,I can't get chassis at 1.7.10,and can you join create power at 1.7.10

you should be able to craft it or spawn it in with the give command, like I said in my last post, I forgot to put it in the vanilla creative UI in 1.7.10.  Also turns out to not be in NEI because I forgot to remove it there too... what a day...
Anyway this recipe in the crafting bench should work even though it doesn't show in NEI in this build:

The things on the top and bottom are aluminum sheets.
Also what do you mean by can i join creative power in 1.7.10?

yep,like 1.10.2 creative power

Backported the creative battery


Display source filename for S3 objects

Is your feature request related to a problem? Please describe.
I sync audio files from an S3 bucket in label-studio. I want to label events in these audios. Unfortunately, there doesn't seem to be any way to display the source filenames and to see the names as they are displayed in the bucket.
Describe the solution you'd like
As a user,
I would like to be able to see the name of my S3 synced files as they are displayed in my S3 bucket
so that i can better know which files I am annotating.
Describe alternatives you've considered
Clicking on "Show task source" doesn't help.
Additional context
My bucket files:

In label-studio:

When clicking on show task source:

@Antoine101 Try to click on "aud" and select "str":

Hi @makseq ,
Thanks for your swift reply!
I tried as you suggest and it works.
Although going from "aud" to "str" made label-studio crash at first. And loading the interface with the "aud" selected by default takes some time and crashes every now and then.
Maybe the "str" mode should be set by default on the main interface (with possibility to switch to "aud" once the main interface is loaded)?
Also, the name displayed in "str" mode is the full URL. Could it be changed to the folllowing:
bucket_name+object_name (including any prefix)
OR
object_name (including any prefix)
Cheers
Antoine

I end up with the following error
No, it's not related to aud/str. Looks like you used incorrect option in the storage settings - try to play with toggle "Treat files as ... " (something like this) in the Cloud Storage Settings dialog.

I agree with the OP, binary file imports are not adequate in LS.
I also think there is definitely room for improvement around data import workflows, in general.
Treat every bucket object as a source file
As I understand this feature as currently implemented for S3 imports, when switched on, it is bleeding in several places:

There is no way to link an imported source (binary) file to its original location.   When binary files are imported, LS seems to shove their encoded representation under an arbitrary field with no path/link to its original location in the cloud. From usability perspective this is terrible because I can't correlate the file with any extra metadata I may want to enrich my tasks with.
The documentation for S3 is incorrect regarding "This setting creates a URL for each bucket object to use for labeling.". This statement is not true. LS does not create any URLs, but simply returns an encoded form of the binary file. I have wasted over an hour trying to figure out the local URL of binary files sync'ed over from S3.

Since a task import from S3 with the above feature switched on seems to be a mere file encoding process, why not document it as such?
We are pushing binary files to S3 for no reason, only to be base64 encoded by LS from there; I could simply serialise my binary files into a JSON file locally and import into LS directly.
Document this.
Even better, please create recipes! Integrate recipes as running code into your CI so that they break when software and recipes are no longer in agreement.

@tilusnet  @Antoine101
I tried to fix this bug about missing Source filename property, you can check this branch or wait until we release it.  https://github.com/heartexlabs/label-studio/pull/2555


Add global.json

Installing VS2017 breaks the build as dotnet-cli preview3 breaks compatibility with preview2 projects. Specifying latest preview2 version (3177) in global.json prevents this behavior from happening.

@crisberrios  Is there any way we can be ... slightly less specific while still blocking using the preview? Specifying EXACTLY 3177, I suppose it won't build if somebody's a tiny point-version off unless they change their version of the framework, which seems pretty inconvenient. (esp if they have another project that has a different point version installed)

For now there isn't. There's an open issue on dotnet repo https://github.com/dotnet/core-setup/issues/679
Specifying 3177-1 should be safe as preview2 shouldn't get new versions since the current is preview3

Think I am going to hold off on this as having to rely on a specific might-be-hard-to-obtain version that is a few points away from what someone has  is also pretty troublesome. Instead, once 2017 comes out of beta, which should be very soon (this month?) XlsToEf is getting upgraded all the way up, and then, goodbye to json based project files.

Upgraded to new core csproj fanciness, this should no longer be an issue.


Updated ix.md

Updated the following to clarify the documentation regarding mediaTypes.video:
Updated the description of the video parameter in the Video table
Updated a code annotation in the Video (Instream) example
Thanks for improving the documentation 😃
Please give a short description and check the matching checkboxes to help us review this as quick as possible.
🏷 Type of documentation

[ ] new bid adapter
[ yes ] update bid adapter
[ ] new feature
[ ] text edit only (wording, typos)
[ ] bugfix (code examples)
[ ] new examples

📋 Checklist

[ ] Related pull requests in prebid.js or server are linked
[ ] For new adapters check submitting your adapter docs

@bretg to review and approve for us

@rimaburder-index - any thoughts about my suggestion above?


Remove users no longer in overrides file

Signed-off-by: Goutham Veeramachaneni<EMAIL_ADDRESS>

#154 is a better version


Update QueryPagination.java code for better paginated iteration

Thanks for stopping by to let us know something could be better!
PLEASE READ: If you have a support contract with Google, please create an issue in the support console instead of filing on GitHub. This will ensure a timely response.
Is your feature request related to a problem? Please describe.
With regards to the query pagination example, the existing example doesn't cover scenario to iterate through all next row page-by-page. And I couldn't find an example to do so anywhere else.
Describe the solution you'd like
An easier approach would be to iterate 1st page in the result and then loop through next pages while updating result object
Describe alternatives you've considered
I have tried using iterateAll(), but it fetches all rows at once, instead iteration should be page-by-page as defined query config pageSize.

PR merged, hence closing this issue.


Add Helm Chart to helm/charts stable/incubator repo?

Helm Operates a "stable" and "incubator" repository of charts that are included without any additional configuration to the helm command. It appears that all that would be required to have the helm chart in this repo included in the default repository would be to open a pull request to helm/charts (assuming there were no objections to the chart). If the chart was in the stable or incubator repositories it would eliminate the git checkout step from the installation process.
I'd be happy to make a copy of the current state of the chart in this repo and make a PR from my fork of helm/charts but I thought I'd ask permission / guidance first.

@sanketsudake we should add BotKube to the stable/incubator repo now

Closed issue as BotKube chart is now part of https://github.com/infracloudio/charts.


Fix image unloading flash in modal exit animation

In the current implementation of modal exit animations in the /settings/profile route, images in the modals disappear or change to defaults during transition, producing an unpleasant 'flash' (as described and shown here: https://github.com/epicweb-dev/epic-stack/pull/246#issuecomment-1629266271).
This happens because the loader data used to derive the images is unloaded during client-side navigation from the modal's child route back to the parent route. A simple fix for this is to track the data used to derive the images as React state so that it is not affected by data unloading during navigation. This PR applies that fix to the user's profile image in profile.photo.tsx and the QR code image in profile.two-factor.verify.ts.
Test Plan

Check that the profile photo modal looks as expected when:

exiting the modal without changing the image
exiting the modal after deleting the image
exiting the modal after updating the image

Check that the two factor verification modal looks as expected when verifying or cancelling

Checklist

No changes to tests or docs

Screenshots (slowed down to make the change visible)
Before:

After:

Hopefully this won't somehow introduce complications to work on #295 .

Doing that in a simple way seems to work for removing the flash, but I'm not sure how to handle propogating changes, like an updated user profile image, from the child component back up into the parent wrapper. My mental models of react hooks and state might just be too wobbly/fuzzy here. I'll spend some time researching and considering further

Thanks for this! As we discussed on office hours, I've removed the dialog altogether: https://github.com/epicweb-dev/epic-stack/discussions/309


Systemd Stage 1 ISO Boot

Issue description
We do not yet support ISO boot for systemd-initrd because we currently set root=LABEL=[label] for the installer ISO but we really should be setting root=live:CDLABEL=[label] or something like that, on par with other distros and what systemd expects
We'll probably only want this to generate differently for the installer ISO with boot.initrd.systemd.enable on so that the old stage-1-init.sh script will not have to be changed. We also will need special handling to get the /iso mount to come from that cmdline rather than /dev/root (which is something specific to stage-1-init.sh)
Steps to reproduce
Try to build the installer ISO with boot.initrd.systemd.enable on and boot it
Technical details
Please run nix-shell -p nix-info --run "nix-info -m" and paste the result.
 - system: `"x86_64-linux"`
 - host os: `Linux 6.1.12, NixOS, 23.05 (Stoat), 23.05.20230217.e6ade07`
 - multi-user?: `yes`
 - sandbox: `yes`
 - version: `nix-env (Nix) 2.13.2`
 - nixpkgs: `/nix/store/84yx0jz81cwfz4nmrvjplq65xgam8grn-source`

cc: @NixOS/systemd

I do plan on working on this sometime in the next few weeks and will update here

Related: #217171

This issue has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/installer-iso-aarch64-dev-root-cant-open-blockdev/28485/1

https://github.com/systemd/systemd/pull/27792 Seems related to this too

I'd like to try to aim this for 24.05 with us defaulting to systemd stage 1 for 24.05 while deprecating the scripted initrd.


Add support for ZFS facts on GNU/Linux

OpenZFS can be installed on Linux nodes, and is packaged in some Linux
distros such as Debian, so it makes sense to make these facts available
when the system has support for ZFS.

Can one of the admins verify this patch?


Broken hyperlink

"I'm looking for a solution provider" hyperlink broken in the How do I get Business Central? section.

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

ID: 79ad74cc-aba8-7c05-93c2-da28efdbf375
Version Independent ID: 2f07a9a9-4cf3-c835-29d0-aab1c830277c
Content: FAQ About Using Business Central - Business Central
Content Source: business-central/across-faq.md
Service: dynamics365-business-central
GitHub Login: @edupont04
Microsoft Alias: edupont

Hello justinbpink,
Thank you for your feedback! This has now been fixed. This is the correct link: https://www.microsoft.com/en-us/solution-providers/home


Remove Open4 gem

With the removal of open4 from automate:
https://github.com/ManageIQ/manageiq-automation_engine/pull/251
MiqCockpitWsWorker::Runner is the only place that his is currently using open4 in the ManageIQ organization:
https://github.com/search?l=Ruby&q=org%3AManageIQ+Open4&type=Code
Open3 seems to be able to do everything that is asked of Open4, so the change should have little to no affect.
Links

For a longer description... https://github.com/ManageIQ/manageiq-automation_engine/pull/251
https://github.com/ManageIQ/manageiq-automation_engine/pull/251

@miq-bot add_label technical debt, hammer/no
@miq-bot assign @jrafanie
@jrafanie  hopefully you are cool with me adding you as a reviewer here.  Unsure who would be better suited, but you seem to have worked on the PR where this worker was initially integrated.


No module named discum

I've basically been tearing my hair out for the past few hours trying to figure out how to get this to work, I've tried running the various commands posted in other closed issues to no avail, I've reinstalled python as well as used Git to install Discum. Any advice?

try to install a simple package like discord.py and then try the discum install agian

I assume you meant install through Git bash, so I tried that. Didn't work. Still can't detect the discum module.

have you tried replace the keyword pip with pip3 ?

Let me try that

Nope same error

try #51 he seemed to get it working

Well it’s more an issue with python installation process usually multiple instances where pip is installing the discum in the wrong place so I was
Testing it on a new machine and I saw that
When using python from the install location doing “import discum” worked but in idle doing import discum didn’t work so the issue that happening it that you do have the discum module but pip installed it in the wrong location
Unfortunately I do not know where my idle version is going off of yet but if I find out I’ll let you know
Sent from my iPhone

On Jun 7, 2021, at 2:34 PM, ToxicLime @.***> wrote:

Sorry for the late reply, but no it doesn't seem that worked.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or unsubscribe.

A small work around is you can use python within the cmd.
you can traverse the file structure of your computer using cd (folder name) and dir and when you get into the folder with mudaeautobot.py
you can run the command
python mudaeautobot.py which should get it to run
and you can figure out the separate instances issue later


Cleanly separating model and dataset code from egs/

Refs #180
So I just wanted to work through the similarities and differences of the models, datasets and egs. First thing I noticed is that for some egs, model and dataset code lives in the eg folder, and for some it lives in the asteroid package. Is there a reason for this (other than historic :-)? If not, what do you think about moving all the model code and dataset code out of the egs?

I recall that we decided to offer some generic (and multi-purpose e.g. ConvTasNet, DPRNN) architectures into the toolkit but more specific ones just into the egs (e.g. WHAMR stacked Bi-LSTM TasNet).  It is a reasonable compromise I think otherwise we will have to add every new thing to the toolkit and it will be hard to maintain.

For the datasets, if we have a unified way to preprocess the data, it should live inside Asteroid, I agree.
For models, it's not as clear IMO. For example, we have the audio-visual recipes where the architectures are really specific, SEGAN (merged soon) doesn't really share structure with other architectures etc..
But you're right that there is also a historical reason.
At first, we aimed at providing well-abstracted (hopefully) building blocks rather than architectures. We decided to include architecture as well and I'm very happy with that now !
I'd be ok to move some things back from egs but probably not all.. How to decide is the next question.


[HTTP] Remove DataSource which is from carbon-messaging dependency

At the moment DataSource interface is from carbon-messaging, we need to move it to the thin layer.

This has been done in the 0.95.5 release.


Cant set "//" as custom emote

Awesome tool!
Tried setting // as a custom emote, but it makes all the HTML look weird.

Another thing is a suggestion: is there a way to set different colors to custom emotes. For example on the server I'm playing we use:

asdasd* for emotes -> (blue)
// for OOC  -> (red)
( asdas ) for thoughts ->  (green)

Thanks!

Working on fixing this issue and looking into the other one! It might take a little bit, but I hope to get them addressed soon.

This is in 0.7.7!


The location of snap-codelabs-code has been moved to https://github.com/ubuntu in github

In the tutorial (http://localhost:8123/codelabs/build-a-nodejs-service#1), it is still stated to grab the nodejs app from "https://github.com/ubuntu-core/snap-codelabs-code" but in fact, it should be from "https://github.com/ubuntu/snap-codelabs-code"

Oh, good catch! Just fixed it in the source. I'll close the bug when I regenerate the snap. Thanks for your contribution :)


Global & Local & Team Chat Options

The ability to disable global chat ("disableGlobalChat"), enable local chat ("enableLocalChat") and specify it's range ("localChatRange") in the server-side config.
These chats will then appear on clients just as IRC channels would and can be switched to. Also, "enableTeamChat", using Minecraft's scoreboard team system.

Not so sure about this anymore. Might not fit into the whole "IRC" thingy. Put on hold until it's actually requested by someone.


Typo

more tha Microsoft search

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

ID: abb4771c-6c09-daca-5a88-e6f0b2e08175
Version Independent ID: 5156d0e5-1a97-b722-a8dd-f6c7a2ecd1e1
Content: SharePoint Online classic search administration overview - SharePoint Online
Content Source: SharePoint/SharePointOnline/manage-search-the-admin-center.md
Service: sharepoint-online
GitHub Login: @MikePlumleyMSFT
Microsoft Alias: mikeplum

@hwkwicre Thank you for submitting feedback. We understand that this issue has been resolved.
Please feel free to re-open this issue if there is a specific area of the docs that we can improve or make better. Thank you.


[BackPort]: CVE Fixes from Upstream

…… (#15363)
Patched security vulnerability by updating Ranger libraries to the newest available version.

Fixes #XXXX.

Description

Fixed the bug ...
Renamed the class ...
Added a forbidden-apis entry ...

Release note

For tips about how to write a good release note, see Release notes.

Key changed/added classes in this PR

MyFoo
OurBar
TheirBaz

This PR has:

[ ] been self-reviewed.

[ ] using the concurrency checklist (Remove this item if the PR doesn't have any relation to concurrency.)

[ ] added documentation for new or modified features or behaviors.
[ ] a release note entry in the PR description.
[ ] added Javadocs for most classes and all non-trivial methods. Linked related entities via Javadoc links.
[ ] added or updated version, license, or notice information in licenses.yaml
[ ] added comments explaining the "why" and the intent of the code wherever would not be obvious for an unfamiliar reader.
[ ] added unit tests or modified existing tests to cover new code paths, ensuring the threshold for code coverage is met.
[ ] added integration tests.
[ ] been tested in a test Druid cluster.

Let's make sure we "rebase and merge for this PR" and DO NOT squash. Otherwise it will be very hard to keep track of which patches we have merged or not, and make it hard to revert if some cause unexpected issues.

@Pankaj260100 can you update the PR description to include the set of patches you are backporting? Right now the description only lists one, but I see others.


Automated Package Upgrade

:tada: This PR is included in version 7.7.318 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


⚠ Science Web Services - QState has degraded performance

In d8005d7, Science Web Services - QState (https://sws.labbricks.com/qstate/) experienced degraded performance:

HTTP code: 200
Response time: 8264 ms

Resolved: Science Web Services - QState performance has improved in a276bcb after 12 minutes.


Short solution needed: "How to find container docker id" (docker)

Please help us write most modern and shortest code solution for this issue:
How to find container docker id (technology: docker)
Fast way
Just write the code solution in the comments.
Prefered way

Create pull request with a new code file inside inbox folder.
Don't forget to use comments to make solution explained.
Link to this issue in comments of pull request.

How to find container docker id


CustomReward init not compatible with EventSub data

rewards.py lines 71-74 try to get a broadcaster_id or channel_id from the data object that is passed in.
However, the reward data sent from twitch contains only 4 fields: Id, Title, Cost, and Prompt.
As such, the creation of the CustomReward in /eventsub/models.py line 437 breaks any method attempting to use that data.

I hit this problem as well, and debugged my way to discovering this bug report and its associated pull request (which DOES fix CustomReward handling for me! Thanks!!)


[Unexpected Behavior] GAMESTATE:GetGameSeed isn't random

What you're using
GAMESTATE:GetGameSeed()
Always returns 8365 on the first game after starting the program.
Expected behavior
Seed is will be different every time you "Game Start", and remain the same until "Game Over". E.g. when you return to song selection between songs, the seed can be used to produce a consistent random sequence for that game, but each game will have a different seed.

Hiya!
thanks for this report! It appears neither the Game seed or the stage seed actually had a 'seed' being generated at the beginning of the game, so it always reported the same number from the rand() call.
We have added an actual seed generation call before these are set and now it works as designed.
The fix will be out the next release.
Thanks again!

Hello @JustinLove
Project Moondance Discord Moderator here, a while ago we created a bug hunter system, users who make issue on this repository gain points and can be rewarded in our discord, so I'm here to ask, are you in Project Moondance discord?
If not, you can join using this link: https://discord.gg/3DgsbSg
If you don't wish to join, that's okay. Please be sure to contact any moderator if you join.

@moruzerinho6 wondible on discord, though I don't keep up very well.


refactor: move gitoid code to cyrptoutil, use digestvalue everywhere

When the functionality to calculate gitoids was added, there was a bit of tech debt incurred since they didn't implement hash.Hash. This remedies this with an admitedly hacky implementation of hash.Hash that wraps the gitoid code. This also standardizes our cryptoutil fucntions around the DigestValue struct that was added around this time to differentiate between gitoids and regular hash functions.

This is the first part of breaking up the VSA PR into a few smaller, easier to digest PRs.

This seems okay enough, tried my best to proof read and while I agree the solution is somewhat hacky but seems neater than how it was implemented before 👍

I've approved, but won't merge as I have one small question. Don't think it's a blocker to merging though

sorry for some reason it's not letting me comment inline - at attestation/context.go:107, sorry for my ignorance, but why do we create 3 separate digest values?

So these are the default hashes, and currently we were only using sha256 as our default. However, the material/product attestors were hard coded to also record sha256-gitoid and sha1-gitoid hashes, so they were added here to maintain consistent functionality


SXSSFWorkbook leaveOpen doesn't work as intend.

NPOI Version
2.7.1
File Type

[X] XLSX

Issue Description
I have a large set of data, and I'm using it like this
SXSSFWorkbook workbook = new();
var dataSheet = workbook.CreateSheet("Data");

foreach(var dataRow in dataRows)
{
    WriteRow(dataRow, dataSheet);

    var buffer = new MemoryStream();
    workbook.Write(buffer, leaveOpen: true);

    buffer.Flush();
    buffer.Seek(0, SeekOrigin.Begin);
}

The first data row can be write perfectly fine, but the second loop, it splitting out an exception
Here is the exception I got.

"ClassName":"System.ObjectDisposedException","Message":"Cannot write to a closed TextWriter.","Data":null,"InnerException":null,"HelpURL":null,"StackTraceString":"   at System.IO.StreamWriter.g__ThrowObjectDisposedException|77_0()\r\n   at System.IO.StreamWriter.Write(String value)\r\n   at NPOI.XSSF.Streaming.SheetDataWriter.WriteAsBytes(String text)\r\n   at NPOI.XSSF.Streaming.SheetDataWriter.BeginRow(Int32 rownum, SXSSFRow row)\r\n   at NPOI.XSSF.Streaming.SheetDataWriter.WriteRow(Int32 rownum, SXSSFRow row)\r\n   at NPOI.XSSF.Streaming.SXSSFSheet.flushOneRow()\r\n   at NPOI.XSSF.Streaming.SXSSFSheet.FlushRows(Int32 remaining, Boolean flushOnDisk)\r\n   at NPOI.XSSF.Streaming.SXSSFSheet.FlushRows()\r\n   at NPOI.XSSF.Streaming.SXSSFWorkbook.FlushSheets()\r\n   at NPOI.XSSF.Streaming.SXSSFWorkbook.Write(Stream stream, Boolean leaveOpen)\r\n   at
...
"RemoteStackTraceString":null,"RemoteStackIndex":0,"ExceptionMethod":null,"HResult":-2146232798,"Source":"System.Private.CoreLib","WatsonBuckets":null,"ObjectName":"StreamWriter"}

Also, I tried to use NPOI version 2.6.2, I got another exception instead of the above, here is the exception I got.

{"ClassName":"System.ObjectDisposedException","Message":"Cannot access a closed Stream.","Data":null,"InnerException":null,"HelpURL":null,"StackTraceString":"   at System.IO.Strategies.BufferedFileStreamStrategy.Write(ReadOnlySpan`1 buffer)\r\n   at System.IO.StreamWriter.Flush(Boolean flushStream, Boolean flushEncoder)\r\n   at System.IO.StreamWriter.Write(String value)\r\n   at NPOI.XSSF.Streaming.SheetDataWriter.WriteAsBytes(String text)\r\n   at NPOI.XSSF.Streaming.SheetDataWriter.WriteCell(Int32 columnIndex, ICell cell)\r\n   at NPOI.XSSF.Streaming.SheetDataWriter.WriteRow(Int32 rownum, SXSSFRow row)\r\n   at NPOI.XSSF.Streaming.SXSSFSheet.flushOneRow()\r\n   at NPOI.XSSF.Streaming.SXSSFSheet.FlushRows(Int32 remaining, Boolean flushOnDisk)\r\n   at NPOI.XSSF.Streaming.SXSSFSheet.FlushRows()\r\n   at NPOI.XSSF.Streaming.SXSSFWorkbook.FlushSheets()\r\n   at NPOI.XSSF.Streaming.SXSSFWorkbook.Write(Stream stream, Boolean leaveOpen)\r\n   at
...
"RemoteStackTraceString":null,"RemoteStackIndex":0,"ExceptionMethod":null,"HResult":-2146232798,"Source":"System.Private.CoreLib","WatsonBuckets":null,"ObjectName":""}

Or did I do something wrong here?

you should not call workbook.Write inside foreach loop

you should not call workbook.Write inside foreach loop

So it's by design that the stream will close after writing? even if I explicitly state leaveOpen: true?
The example might be an extreme case, but what I want to do is write the data in bulk, eg. write row every 100 rows at once, then upload to an API, then write another 100 rows, then upload and so on.
The example for loop here might look a bit silly, but the idea is like I state above.


Shamir 39 Tool: Add option to use satoshilabs word list?

I was experimenting with inputing the Shamir shares (20 word list) produced by Trezor into your tool however there is a word not used ("academic") in your tool that they use. Would it be possible to add an option/switch to use their wordlist to reconstruct shares in the combine list? Their list is located at
https://github.com/satoshilabs/slips/blob/master/slip-0039/wordlist.txt
This would be helpful as an escape hatch to restore a wallet in case Trezor/satoshilabs ever disappears.

Bip39/shamir39 use 2048 word list (11 bit per word), but slip39 use 1024 (10 bit per word). Therefore it is no way just replace word list.