New story line: Who predicted they would win the game?

@howardchung mentioned in the discord chat that the replays do include "player has predicted!" data. It'd be neat to see that added to the story view as well.
Not sure if it's parsed and available in the JSON yet.
Would be super cool if streak data was available too. But that's not important. Not sure how universal it is, since charms don't really have a "streak" per se.
Would also be amusing to mention at the end of the story to mention how the predictions panned out.

@mdiller

👍


Unflattened one-line workflows

Changed all oneline workflows to the unflattened JSON one using
cat wf.ga | jq . -S > out.ga

from https://github.com/usegalaxy-eu/workflow-testing
This way small changes to the workflow can be easily compared.

This is again one step towards deleting the tools.yaml files. After this I will change some workflows in a way that workflow-to-tools from ephermeris is able to detect all the tools.


Cannot have multiple buttons that launch the same popover

When I have multiple buttons that launch the same popover, I found that the second button I clicked on would show the popover off the screen (negative coords).
It is happening b/c $this.data('modal-popover') stores the options that you pass in and even if you redefine those options just prior to showing the popover, it just pulls the first value from $.data() (which is for the wrong button).
Not sure if I'm using the control wrong, but I modified the modalPopover (line 113 in the current src) where I force data to undefined when passing in options. This resets it so it's not pulled from $.data() and now it's working:
$.fn.modalPopover = function (option) {
...
var data = typeof option == 'string' ? $this.data('modal-popover') : undefined;
(Love this simple control btw! Thanks for making it)

Thanks for the fix.  I know it's been a while.  I haven't been maintaining this component.  But since others are apparently still finding use for it, I made an example in the demo to test this and committed your fix.


Why I can't import fmt and  local packages ?????

What version of Go are you using (go version)?

$ go version
go version go1.13.4 darwin/amd64

Does this issue reproduce with the latest release?
What operating system and processor architecture are you using (go env)?
go env Output
$ go env
GO111MODULE=""
GOARCH="amd64"
GOBIN=""
GOCACHE="/Users/roadup/Library/Caches/go-build"
GOENV="/Users/roadup/Library/Application Support/go/env"
GOEXE=""
GOFLAGS=""
GOHOSTARCH="amd64"
GOHOSTOS="darwin"
GONOPROXY=""
GONOSUMDB=""
GOOS="darwin"
GOPATH="/Users/roadup/.go"
GOPRIVATE=""
GOPROXY="https://goproxy.cn,direct"
GOROOT="/usr/local/Cellar/go/1.13.4/libexec"
GOSUMDB="sum.golang.org"
GOTMPDIR=""
GOTOOLDIR="/usr/local/Cellar/go/1.13.4/libexec/pkg/tool/darwin_amd64"
GCCGO="gccgo"
AR="ar"
CC="clang"
CXX="clang++"
CGO_ENABLED="1"
GOMOD="/Users/roadup/.go/src/github.com/onsunnny/paokemo/go.mod"
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
PKG_CONFIG="pkg-config"
GOGCCFLAGS="-fPIC -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=/var/folders/c5/dvsgj0412q18f6v7sxzxpr700000gn/T/go-build461240957=/tmp/go-build -gno-record-gcc-switches -fno-common"

What did you do?

What did you expect to see?
Why go package manager is so hard to use?
Why I can't import some package by a relative path, if I rename my project , I need replace all of my imported packages in this project
What did you see instead?

Hi @onsunny - Go files under the same directory belong to the same package. So you don't need to "import" anything if you want to use things from db.go into main.go. I don't know why you cannot import "fmt' though.
In any case, unlike other projects, we do not use the issue tracker for questions such as these. It is only used for bugs and feature proposals. I will close this issue, but please feel free to ask it in any of these forums below:

Stack Overflow with questions tagged "go"

The Go Forum, a web-based forum

Gophers Slack, use the invite app for access. The #general channel is a good starting point.

Go Community on Hashnode with questions and posts tagged with "go"

The golang-nuts mailing list

IRC channel #go-nuts on Freenode

Thanks


Ways to structure modules missing at the root of a project

Problem
In the root of a project (src/main.rs / src/lib.rs), it is not possible to treat main.rs or lib.rs as Rust files with their own "pair" of folders that will contain submodules.
This is possible:
src/
    main.rs
    moduleA.rs
    moduleA/
        ...
    moduleB.rs
    moduleB/

Cargo will only accept accept main.rs or lib.rs having submodules if these submodules are placed side-by-side with main.rs or lib.rs. For deeper modules in the directory structure, you can organize modules in this way:
src/
    main.rs
    moduleA.rs <- The module*.rs can only be put side-by-side with main.rs
    moduleA/
        submodule1.rs
        submodule1/
            sub_submodule1.rs <-- However sub_submodule*.rs can be placed inside the folder of submodule*.rs.
            sub_submodule1/
        submodule2.rs
        submodule2/
    moduleB.rs
    moduleB/

Proposed Solution
My solution is to allow the same arrangement to be also allowed at the root. It creates consistency across the entire project arrangement:
In a binary:
src/
    main/
        moduleA.rs
        moduleA/
            ...
        moduleB.rs
        moduleB/
    main.rs

In a library:
src/
    lib/
        moduleA.rs
        moduleA/
            ...
        moduleB.rs
        moduleB/
    lib.rs

Notes
No response

Can you build an example of what does not work?

Here: https://github.com/dasifefe/cargo-should-allow-this-structure-at-root
I made two versions:
src_fails is the one that fails, but I believe that this organization should be possible, as it is consistent with what is possible to do in the deeper nesting of a project.
src_succeeds is a version that compiles.
Rename any of these to src/ and try it out.
In the version that fails, Cargo cannot find lib/foo.rs nor lib/bar.rs, because the Cargo never tries to find a folder with the same name as the root file (main.rs or lib.rs).
This is part of the error message that we get:
error[E0583]: file not found for module `bar`
 --> src/lib.rs:3:1
  |
3 | mod bar; // Cargo cannot find this module, because it expects it to be side-by-side with `lib.rs` or be a folder containing `mod.rs`.
  | ^^^^^^^^
  |
  = help: to create the module `bar`, create file "src/bar.rs" or "src/bar/mod.rs"
  = note: if there is a `mod bar` elsewhere in the crate already, import it with `use crate::...` instead

error[E0583]: file not found for module `foo`
 --> src/lib.rs:6:1
  |
6 | mod foo; // Cargo cannot find this module, because it expects it to be side-by-side with `lib.rs` or be a folder containing `mod.rs`.
  | ^^^^^^^^
  |
  = help: to create the module `foo`, create file "src/foo.rs" or "src/foo/mod.rs"
  = note: if there is a `mod foo` elsewhere in the crate already, import it with `use crate::...` instead

error[E0412]: cannot find type `FooThing` in this scope
  --> src/lib.rs:10:14
   |
10 |     pub foo: FooThing,
   |              ^^^^^^^^ not found in this scope

error[E0412]: cannot find type `BarThing` in this scope
  --> src/lib.rs:11:14
   |
11 |     pub bar: BarThing,
   |              ^^^^^^^^ not found in this scope

The src_succeeds/ works because I created a "dummy" module side-by-side to lib.rs, which lib.rs first imports, and then that module imports the others.

src/lib.rs is called the “crate root”. It's kinda special and will be fed to rustc as the input file. The module resolution then starts from the crate root file and applies the rule you've described.
The crate root is so special that you don't even need to name it with .rs extension. The following example works:
cargo new foo --lib && cd foo
echo "[lib]" >> Cargo.toml
echo "path = 'src/lib.cpp'" >> Cargo.toml
mv src/lib.rs src/lib.cpp
cargo build --verbose # It builds! And you can see `src/lib.cpp` passed to rustc

Unfortunately I don't think this issue can be solved on Cargo side. Cargo doesn't understand module resolution; it's the compiler's job! I would suggest opening this in rust-lang/rust repository instead.

Thank you! I will open the issue on the rust-lang/rust repository, I really thought that the project module hierarchy was determined Cargo-side.
Closing the issue.


Custom class

I tried to do
.search-select .form-control {
    background-color: #000;
}

just to check if the color will be changed, unfortunately, no luck. is there a way to do this?

Did you solve this? I am also trying to change the color of the select pickers..


Update onelogin.yaml

Fixed Spelling.

attually I got the latest .yaml off the author y'all can reach out to him on icq @mrgretzky to get issues fixed if needed.


SCB-1282 Support for custom "omegaUniqueIdGenerator" bean.

Modify the "OmegaSpringConfig" class of the omega-spring-starter module. When injecting the bean "omegaUniqueIdGenerator", add the @ConditionalOnMissingBean annotation.

Coverage increased (+0.02%) to 80.347% when pulling fac1698124f8aafd8612e866562564b30ac04c16 on zengxiangjiang:zengxiangjiang into cdd571e030b8ca4ce4ca31fa8d233508c161ac46 on apache:master.

I suspect it wasn't caused by the code I submitted. Please tell me the test steps. thank.

"Coverage increased (+ 0.02%) to 80.347%", what does this mean and do I need to fix it?

@zengxiangjiang  coverage change may only relate to you last commit.  It looks good now, you don't need to do anything.


Prevent infinite recursion in NormalizerFormatter::normalize

something like
    protected function normalize($data, $depth = 5)
    {
        if ($depth === 0) {
            return 'too deep';
        }

        ...

        if (is_array($data)) {
                ...
                $normalized[$key] = $this->normalize($value, $depth - 1);
                ...
            return $normalized;
        }

        ...
    }

$parent = [];
$child = [];
$child['parent'] = &$parent;
$parent['child'] = &$child;

function t($parent) {
	// log
}

t($parent);

fixed in #808

#808 - Move these changes to the branch 1x, please.

Just FYI, change of plans, this was backported in #1050

Hi.
I recently upgraded a long overdue projetct using a monolog version < 1.23.0 and this change breaks normalization for some important json data.
Do you think you could make the nesting limit optionnal ?
Thanks/

@AlanCrevon what kind of depth are you looking at? I can see that 9 is pretty arbitrary, but I do wonder what would be a reasonable number to you?
Anyway perhaps we could add a setter to change the max depth on the NormalizerFormatter.. Can you please open a new issue (or even a PR?)

Hello,
@Seldaek https://github.com/Seldaek/monolog/pull/1633


Minisafe daemon backbone

This implements the configuration, database backend, bitcoind connection and initialization of the Minisafe daemon.
A lot of code was ported from revaultd and miradord, although the interface (for bitcoind and the database) changed and many things were re-written. This contains some basic unit tests for startup and database initialization. I intend to port the functional test framework from revaultd in a future PR.

cc @edouardparis. FYI i intend to merge this soon since this is mainly reusing revaultd's code. Just waiting on CI to make sure the unit tests pass on other platforms than Linux.

Sigh... Windows :sob:


libreoffice and libreoffice-qt packages use icon names incompatible with icon themes

Describe the bug
Libreoffice desktop files seems to be using names for icons that are not adopted by icons packs and also are sometimes overlap with other existing icons like calc. I'm not sure if it's a upstream change in libreoffice source, but since I only had this issue in NixOS, I'm writing about it here.
Steps To Reproduce
Steps to reproduce the behavior:

Install libreoffice or libreoffice-qt in system packages
Install and apply papirus-icon-theme
See how only icon changed is calc, which now shows calculator icon

Expected behavior
.desktop file using libreoffice-* icons instead of * icons (like libreoffice-calc instead of calc)
Screenshots

Additional context
I have only tested it with Papirus icons with KDE, and have not found the issue simmilar to this one in nixpkgs or papirus icons issue trackers.
Notify maintainers

Metadata
[user@system:~]$ nix-shell -p nix-info --run "nix-info -m"
this path will be fetched (0.00 MiB download, 0.00 MiB unpacked):
  /nix/store/gd9mmij8iifhldkhjsgbr08i55nm4lsg-nix-info
copying path '/nix/store/gd9mmij8iifhldkhjsgbr08i55nm4lsg-nix-info' from 'https://cache.nixos.org'...
 - system: `"x86_64-linux"`
 - host os: `Linux 6.1.53, NixOS, 23.05 (Stoat), 23.05.20230921.55ac2a9`
 - multi-user?: `yes`
 - sandbox: `yes`
 - version: `nix-env (Nix) 2.13.5`
 - channels(root): `"nixos-23.05, nixos-hardware"`
 - nixpkgs: `/nix/var/nix/profiles/per-user/root/channels/nixos`

I cannot specify which commit but it was fixed for me.


No permission to download dataset.

Hi, I still have no idea why I cant access the dataset. Could you please help me? Thanks!

Hi there,
Can you be more specific about the issues you're having? Common issues are that you may not have filled out the Google form for access on waymo.com/open, or that you're signed into a different Google account than the one you used to fill out the form when trying to download the data.

I cannot find the form in any pages on https://waymo.com/open/ ...

 I cannot find the form in any pages on https://waymo.com/open/ ...

Solved.
I registered at  https://waymo.com/open/licensing/


Bring back PauseFocusLoss=false?

I quite enjoyed this setting back before it was removed, and didn't suffer from any crashes myself (despite alt-tabbing a lot). Is there a chance this can be put back in, perhaps with a warning in the .ini file that some people (one person?) have experienced crashes with it?
More of a wish or suggestion rather than an issue really, so sorry if this is in the wrong place.

I just use "Continue Rendering" feature in SpecialK

I just use "Continue Rendering" feature in SpecialK

are you using steam? cuz mine on ms store version won't launch with specialK

Thank you!


wails: v2.0.0-beta.37 -> v2.0.0-beta.38

Description of changes
Update Wails app builder to latest version.
Changelog: https://github.com/wailsapp/wails/releases/tag/v2.0.0-beta.38
Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/prs-ready-for-review/3032/981


Rails assessment, incomplete.

Rails assessment, incomplete.

Ok, I can see you're getting the idea for routes.


[Scenario] Scape Mansion

What kind of mission do you want to add (mark with an X, e.g. [X] Descent)?

[X] Mansions of Madness
[ ] Descent

Please enter the GitHub Url to your scenario here
https://github.com/davidfraj/scapeMansion

Great, a escape room in Spanish!
@scrubbless , would you mind to add this one to Valkyrie?

Added to the manifest, should be listed within the hour


feat(packaging): update library packaging to support Angular Package …

…Format v5.0

Coverage remained the same at 92.017% when pulling 0a66d8f25199ae22014dbf26f07cd3712f3edf71 on feat-packaging-v5 into 0cd015c5a6621c0f38bc848579793796f1344adc on master.

Coverage remained the same at 92.017% when pulling 0a66d8f25199ae22014dbf26f07cd3712f3edf71 on feat-packaging-v5 into 0cd015c5a6621c0f38bc848579793796f1344adc on master.


Add support for tree view with hierarchical elements

Some things are still not working properly, but showing hierarchical data with multiple columns should work fine now.


Add syncRender to synchronously render templates

A synchronous API to render and get error would be helpful.

Hi @subwiz,
I see why such an API could be useful. However this library uses Promises/A+ extensively at its core, especially relying on this behavior:

2.2.4 onFulfilled or onRejected must not be called until the execution context stack contains only platform code.

There's more elaboration on this in this "Synchronous promise resolution" answer.
I don't see a way to add this feature in a maintainable fashion.

Thanks for letting me know!


Snapshot release cycle

I was in the process of updating some documentation when I realized this (quickstart.md) is based on a snapshot. getting_started_verilator.md on the other hand should reflect the current state of the repo. So these documents might contain different instructions, which could be confusing.
Do we have a plan of how frequently the snapshot should be released? Or is this more on the basis of a need.

Good that you bring that up. A regular snapshot release is something we should aim for; given that it is a snapshot release, ~1 a month sounds like a good cadence. We should however make sure that we can release such a release with minimal or no manual work/testing.

Once a month sounds like a reasonable suggestion.
The release creation should be automated by adding a tag.
One part which should be updated with this is doc/ug/quickstart.md.
Other than that the only manual task would be to test the release? Or do I miss something @imphil?

A snapshot release does have some advantages, but I think it might be worth considering instead beefing up testing of bitstreams in CI, and pointing people to artifacts from master instead.

Actually I was not aware of the artifacts until Philipp pointed that out to me.
So making this more obvious would indeed help.
But I also think it makes sense to keep the quickstart.md together with the release reasonably up to date in order to minimize the difference to the development progress.

Closing in favor of #1928 as it seems like we do the snapshot if it is needed. Please reopen if there is still a need to discuss a more structured approach to release cycles.


Create cktap-cli tool

Replace examples/pcsc.rs with new bin cktap-cli tool. Use clap for cli features, should be able to borrow code from pcsc.rs.

Do we want to mark this as done as it is? Otherwise, we might need a definition of scope

I'll close this one and we can open new issues or PRs for to improve the bare bones cli in #14.


⚠ Bofrost.es has degraded performance

In 0af11ee, Bofrost.es (https://www.bofrost.es) experienced degraded performance:

HTTP code: 200
Response time: 1821 ms

Resolved: Bofrost.es performance has improved in 7a1ed79.


[release/1.6] Update hcsshim to v0.9.11 + gowinio to v0.5.3

Update hcsshim to v0.9.11 + gowinio to v0.5.3 + go mod tidy/vendor
Full list of changes:
https://github.com/microsoft/hcsshim/compare/v0.9.10...v0.9.11
https://github.com/microsoft/go-winio/compare/v0.5.2...v0.5.3
closes #10245

Addressed by PR https://github.com/containerd/containerd/pull/10245. Therefore closing this PR.


STM32 Crypto Accelerator

Adds support for the CRYP peripheral in all STM32s. This does not include support for any implementation of the AES peripheral, which is functionally a subset of the CRYP IP but is an entirely different implementation. (That said, I believe the design of these two IP are close enough that AES implementations could share this API.)
Only a blocking mode is implemented initially. I anticipate this mode is likely to be more commonly used than an async DMA implementation since most crypto traits, such as the Rust Crypto AEAD traits, are not async. All supported cipher modes are implemented.
The API is structured differently than a typical implementation of these algorithms to support suspend/resume functionality and incremental computation. This allows the application to feed payload and associated data for encryption/decryption on a block-by-block basis. This is useful in a microcontroller, where encrypting or decrypting a large stream of data such as a large file or secure firmware update image is not practical or possible to perform in one go. It is also useful for a concurrent send/receive scenario, where an application is simultaneously sending and receiving packetized data that must be encrypted and decrypted simultaneously.
For ciphers that do not support partial blocks (ECB and CBC modes), no padding scheme (such as PKCS#7) is implemented. Thus, only complete blocks may be supplied in these modes. The application must manage padding in these modes to ensure all blocks supplied to the processor are complete, otherwise a panic will occur. Panics due to malformed parameters are largely avoided through the use of traits that enforce key, IV, and tag length constraints.
An example for the STM32F7 series is included that demonstrates use of this API for the AES-GCM-128 cipher. In my testing, this example encryption/decryption ran >10x faster with hardware acceleration compared to the aes-gcm crate implementation!
This is a work in progress. All algorithms have been trivially verified but tests still need to be added.

CI Build issue is apparently due to an STM32H7 RCC register naming issue. Addressed in a PR here: https://github.com/embassy-rs/stm32-data/pull/411


[Burn-P3+ FR]: Numeric Lookup for Seasons and Weather Zones

Contact Details
<EMAIL_ADDRESS>What is needed?
Currently the season and weather zone are text based on the seasons and weather zones we enter. A numeric identifier would be helpful as it would allow us to tie it back to the rasters we're importing. Further it's not atypical to do an extract of the zone data from the raster for the weather data which would make it numeric typically.
How will this improve the project or tool?
Less user input for the same output.
Approvals Process

[ ] Testing For Issue
[ ] Merge

Not certain I follow, but there are currently two unique numerical values tied to each  fire zone and weather zone, one of which seasons are also assigned.
The first is the raster cell value for each zone, which is mandatory for using zones and set by the user in the project scope. For doing raster extractions by zone, I think the user-provided zone rasters and this table linking zone names to cell values is all you would need? Let me know if not though, might be overlooking something. Seasons have no analog to this. It would be easy to add a user-defineable integer ID column, but I'm not sure I understand how that would be used since season isn't spatial.
The other value is a unique identifier assigned to each season, zone, and a couple other things by SyncroSim when a record is created. I believe these are primary keys in the underlying SQL and they are totally static. We generally don't show these numbers because the user has no control over them, they aren't used anywhere else in the basic user interface, and we don't want to cause confusion. That being said, these values are used for things like naming season-specific output files since they are guaranteed to be unique and only include safe characters. Also, you can access these columns from all SyncroSim APIs except for the GUI. For example, SeasonID here is that unique identifier accessed here through rsycnrosim:
https://github.com/BurnP3/BurnP3PlusPrometheus/blob/4583d081c859e68992d5b3c0e89003b95f618f6f/src/growth-pandora.R#L819
We could make this column hidden by default but viewable in the GUI, though we'll probably want to stress somehow that this is not editable or a raster cell value.

Sorry this wasn't clear as I should have mentioned this was on import. When I import my files have Seasons and Zones labelled numerically. This may end up being an issue of my workflow, but I could see others having similar data within their weather list file.
I'll update the title to reflect the problem.


Repeatable scripts don't work in the version 3.0.0

Now repeatable scripts don't work: if you try to execute a folder with a single R__ script - it says:
schemachange version: 3.0.0
Using change history table METADATA.SCHEMACHANGE.CHANGE_HISTORY (last altered 2021-09-13 17:07:29.614000+02:00)
Max applied change script version: XXX
Successfully applied 0 change scripts (skipping 1)

We were needed to rollback to previous version (pip install schemachange==2.9.2) to get expected behaviour of the tool.

Hi there @arkhipkin, please check out the CHANGELOG for details about what changed in version 3.0.0. There was a bug in the logic for Repeatable scripts which was changed in 3.0.0. Now Repeatable scripts are only re-run with the contents of the script change. To achieve the same prior behaviour we introduced the new "A" scripts which always run even if the contents of the script haven't changed. Hope that helps.

thank you for the explanations @sfc-gh-jhansen


Show captions in "Home" and "Explore"

As you scroll you see titles (=filenames) over the thumbnails, these should be captions:

Show titles at first but replace with captions when available

@nicolas-raoul here are the commits for showing captions in Explore and home

Also, this must be implemented in the "Media" tab of Explore search.

I'll add it int my next commit

Strangely, my home does not seem to show captions.
For instance, I recently uploaded https://commons.wikimedia.org/wiki/File:隅田川駅_JR倉庫_3.jpg with the app, then added an English caption using the Commons website.
Problem: In my home activity the filename is used, not the English caption (my Android's locale is English):

OK I'll check this out

Please test it on your device with a picture you uploaded. You can add captions easily using the Commons website :-)

@nicolas-raoul this issue is resolved here https://github.com/commons-app/apps-android-commons/pull/2970/commits/238a91a0462e71c7e860a5af9d8443a8fbbf01ed.
Please check :-)

Wonderful!
Similarly, we must show captions in the list of images shown by depiction search.
For instance, search for the "boat" Wikidata item and you will find this image: https://commons.wikimedia.org/wiki/File:Stade,Hansehafen--2018--_2961.jpg
Problem: On my English locale Android it is not shown with its English caption but rather with its filename (minus the .jpg):

Similarly, we must show captions in the list of images shown by depiction search.

I'll add it in my next commit

@nicolas-raoul I have made the necessary changes in the commit
Please check :-)

Wonderful, thanks for all the fixes you performed yesterday, that's impressive :-)

Thanks @nicolas-raoul :-)


Using version @v3 should always point to latest 3.x version

I have been using hustcer/setup-nu@v3 in https://github.com/ddanier/nur to setup nu inside the GitHub actions. All other dependencies I use update the @vX version to the latest X.* version, once a new version is released. Using @v3 should by this logic currently be the same as @v3.10.
Sadly this package does not update the shorter version tags. Thus @v3 points to a pretty old version, not supporting MacOS builds. This leads to strange errors and is not matching what others are doing.
My suggestion would be to also update major release tags like the @v3 tag on every new release.
For reference other actions I am using:

https://github.com/actions/checkout/tags -> @v4 is currently the same commit SHA1 as @v4.1.4
https://github.com/softprops/action-gh-release/tags -> @2 is currently the same commit SHA1 as @v2.0.4
https://github.com/actions-rust-lang/setup-rust-toolchain/tags -> @v1 is currently the same commit SHA1 as @v1.8.0, also there is @v1.8 also pointing to this version

Thanks for the feedback, I have just update v3 tag.

v3 should always point to latest 3.x version

I will update the release script later to make sure it's always true

Thanks for the quick reply and instant fix! 👍

I just confirmed this works now using only @v3. Thanks again!


Link to help page does not work

Current Behavior
Click on"...here shows "404, page not found"
Expected Behavior
Click on"...here should show the help page.
Steps To Reproduce
On the help-page for ui-page, section «Layout» is a link”here” (https://dashboard.flowfuse.com/layouts/grid.html).
That shows 404, page not found.
Environment

Dashboard version: 1.12.2
Node-RED version: 3.1.3 (german)
Node.js version:
npm version:
Platform/OS: Rasberry PI 4 Model B Rev 1.5, Debian GNU/Linux 12 (bookworm
Browser: Microsoft Edge

Have you provided an initial effort estimate for this issue?
I am not a FlowFuse team member

Thanks for fixing this


[🐛 BUG] Can't select data nodes in data node selector

What went wrong? 🤔
I can't select and view these data nodes:

I can select initial_dataset without issue
Steps to Reproduce Issue
Use this code:
app.zip

pip install taipy develop
run app.py
In the interface, create a scenario and submit it
In the data node page, try to select a node of the scenario, it will not appear in the data node viewer

Runtime Environment
Windows 11
Browsers
Chrome
OS
Windows
Version of Taipy
develop
Code of Conduct

[X] I have checked the existing issues.
[ ] I am willing to work on this issue (optional)

Can you share some code ?

I am putting this as critical as it breaks applications/demos.


fix stacker files for arm64 arch

Describe the bug
Since zot is built with PIE mode, we need a runtime to launch zot.
Currently, stacker.yaml uses alpine as the base image, however, amd64 correctly but not arm64.
arm64v8
Need a way to use "from: arm64v8/alpine:3" from our ci/cd pipeline.

Also, in our ci/cd pipeline, we are doing docker and podman run, but we also need a client to actually connect to the running service. That is the real test.


Error while installing elasticsearch chart

Hey,
I'am unable to install the current state of the elasticsearch chart. When I execute the install command from the chart's Readme I get an JSON paring error:
[root@kube-master-1 ~]# helm install --name es-test-1 charts/incubator/elasticsearch
Error: release es-test-1 failed: [unable to decode "": [pos 301]: json: decNum: got first char '"', unable to decode "": [pos 301]: json: decNum: got first char '"', unable to decode "": [pos 288]: json: decNum: got first char '"']

The issue is a little bit hard to debug, as the input of this chart is all yaml and I don't know if and where the intermediate json gets stored.

Fixed in #115


Add fingerprints from fingerprintdb

This implements: https://github.com/ooni/backend/issues/281

31 issues done, 12 more to go!


High CPU utilization of Executor in Example

This is the same issue as #55.  I was able to reproduce on OS X 10.10.

I've submitted a PR with a fix - #183


Add edpm_baremetal_deploy

This target can be used when you've BMHs already available to be used and has no pre-req of using crc.

recheck

recheck


.gitattribute & template update

Changes / Comments

Remove a line in the template
Enforce LF line endings for specific file types

Roll20 Requests
Include the name of the sheet you made changes to in the title.

If changes fix a bug or resolves a feature request, be sure to link to that issue.
For pull request that change multiple sheets please confirm these changes are intentional for all sheets. This will help us catch unintended submissions.
When updating existing sheets if you are changing attribute names please note what steps you have taken, if any, to assist players in keeping their data.

Would it be good to also add .md and .markdown too, in case people adding Readme files with their sheets?

I've not seen a case where a .md or .markdown has caused a problem. I'm looking to mostly enforce LF endings on these extensions as our servers will some times complain if they are not LF.


observer not tracking changes to observable array

I'm experiencing an issue with observable arrays. Not sure if this is a question or a bug, but seems more like a bug.
The code works with mobx, but fails with Mobx state tree:
slicing the array makes it work, but the slice should NOT be necessary imo!
class ObjectWithArray {
  @observable arr = [0, 1, 2];
  @action pushToArray = () => {
    this.arr = this.arr.concat(this.arr.length);
  };
}

const MstObjWithArray = types
  .model({
    arr: types.optional(types.array(types.number), [0, 1, 2]),
  })
  .actions(self => ({
    pushToArray() {
      self.arr = self.arr.concat(self.arr.length);
    },
  }));

@observer
export default class App extends React.Component {
  // obj = new ObjectWithArray(); // this WORKS!!
  obj = MstObjWithArray.create();
  render() {
    const data = this.obj.arr; //add slice() to make sure component is re-rendered
    return (
      <View style={styles.container}>
        <Text onPress={this.obj.pushToArray}>add item to array</Text>
        <Text>content of array:</Text>
        <FlatList data={data} renderItem={this._renderItem} keyExtractor={this.keyExtractor} />
      </View>
    );
  }
  keyExtractor = item => {
    return String(item);
  };
  _renderItem = ({ item }) => {
    return <Text>{item}</Text>;
  };
}

runnable repro https://github.com/vonovak/mobxBug/blob/master/App.js
to run the repro, just clone, yarn and yarn start should work, you can run this on your phone
EDIT: I was able to isolate this outside of mobx-react, so this is not an issue with observer
import { autorun, observable, action } from 'mobx';
import { types } from 'mobx-state-tree';

class ObjectWithArray {
  @observable arr = [0, 1, 2];
  @action pushToArray = () => {
    this.arr = this.arr.concat(this.arr.length);
  };
}
const MstObjWithArray = types
  .model({
    arr: types.optional(types.array(types.number), [0, 1, 2]),
  })
  .actions(self => ({
    pushToArray() {
      self.arr = self.arr.concat(self.arr.length);
    },
  }));

describe('mobx autorun', () => {
  it('with mobx', () => {
    const obj = new ObjectWithArray();
    const mock = jest.fn();
    autorun(() => {
      obj.arr;
      mock();
    });
    obj.pushToArray();
    expect(mock).toHaveBeenCalledTimes(2);
  });

  it('with MST', () => {
    const obj = MstObjWithArray.create();
    const mock = jest.fn();
    autorun(() => {
      obj.arr;
      mock();
    });

    obj.pushToArray();
    expect(mock).toHaveBeenCalledTimes(2); // Expected mock function to have been called two times, but it was called one time.
  });
});

closing in favor of https://github.com/mobxjs/mobx-state-tree/issues/1213


Bound shares used for transactions

The number of shares used for transactions, intermediate state roots, evidence, etc. should be bounded by some parameter. Otherwise, a malicious validator could create a maximum-size block filled with only transactions, and all full node would be required to fully download and process the block to compute the state.

There is good reason to also separately bound the number of shares available to use for paying for messages, and all other requests with a reserved namespace ID: it avoids the two sharing a fee market.


Srl ner

@zupon I would like you to try this branch on the sentences from Robyn and see it it addresses the problems you saw.
@kwalcock somewhere about 20 if-else statements ago this code was too complex, I think I will try to refactor it dramatically, but IDK what the ETA on that will be.

I have some changes to SRLCompositionalGrounder.scala pending.  I'll try to get at least the branch pushed soon so that you know what they are.

awesome! that would be great!
I'm in the process of rethinking the algorithm fundamentally

There were fewer than I thought that made it into a commit after all the debugging statements were removed, so merging might not be too difficult after all.  It's branch kwalcock/reground.  The ensureSRLs() changed because the JsonLD only records edges.  If there are none, there's no record of the graph and the program tries to recalculate the empty graph unnecessarily.  Elsewhere, the results are still occasionally inconsistent, so the validPredicates are being sorted.  That seemed not to be enough and I have at least two files that failed a test.  There is some sorting later involving the scores that might be insufficient because of ties, which do exist.  If the topN is applied and it splits a tied group, then the order within the tie is important.  I'm not sure that's the problem, though.  Just FYI.

This may be because of the rename of the ontology file that I mentioned this morning.  I will test on a different branch and update master if needed and then report back here.
[info] TestSentenceClassifier:
[info] org.clulab.wm.eidos.text.englishGrounding.TestGrounding *** ABORTED ***
[info]   java.lang.NullPointerException:
[info]   at java.util.Properties$LineReader.readLine(Properties.java:434)
[info]   at java.util.Properties.load0(Properties.java:353)
[info]   at java.util.Properties.load(Properties.java:341)
[info]   at org.clulab.wm.eidoscommon.utils.PropertiesBuilder$$anonfun$fromResource$1.apply(PropertiesBuilder.scala:57)
[info]   at org.clulab.wm.eidoscommon.utils.PropertiesBuilder$$anonfun$fromResource$1.apply(PropertiesBuilder.scala:56)
[info]   at org.clulab.wm.eidoscommon.utils.Closer$.liftedTree1$1(Closer.scala:20)
[info]   at org.clulab.wm.eidoscommon.utils.Closer$.autoClose(Closer.scala:19)
[info]   at org.clulab.wm.eidoscommon.utils.Closer$AutoCloser.autoClose(Closer.scala:60)
[info]   at org.clulab.wm.eidoscommon.utils.PropertiesBuilder$.fromResource(PropertiesBuilder.scala:56)
[info]   at org.clulab.wm.eidos.groundings.DomainHandler$$anonfun$1.apply(DomainHandler.scala:38)
[info]   ...

That does seem to be the cause.  PR forthcoming.

Tests are passing.  @zupon, if the error above is what you're getting, it may help to merge with the latest update to master as was done here.

@kwalcock , wonderful beautiful @kwalcock  -- first, please look at my refactor of the SRL compositional grounding code.  The diff will be very hard to look at, so if you can look at them side by side (old and new) that would be ideal to marvel at how pretty the new code is!!!
Ok, prettiness aside (but boy, is it pretty!), do we have tests that will check that I didn't change the behavior toooo much (a little was on purpose, and some edges cases I may not care about bc some things I was uncertain about how to handle in the first place)...?
ps -- @MihaiSurdeanu idk yet if it works, but this code is soooo pretty now! (the parts I refactored, look especially at lines 178-275 that removed like 35 nested if-else pairs in a recursive function) :)
OH! and @marcovzla helped me with the graph traversal part so it's likely even right! :D

It worked great for 25 files, but then stack overflowed because of infinite recursion.  I'll try to track down the culprit.  A key line in the loop was
    val children: Array[GraphNode] = getThemes(idx, s, backoff).map(GraphNode(_, s, backoff, topN, threshold))

in SRLCompositionalGrounder.scala line 357.

Here's one problematic file.  I was using ReExtractCdrMetaFromDirectory to process it.  Remove .txt from the end.
005e214e0bde30d3ba7e3ab0f7ee1b7a.json.txt

@kwalcock noted, i'll run it on that.
Also .. the failing test is for the serialization -- here is a diff of the jsonlds, i am at a loss to understand how they could be diff... the SRLs and roots and all are serialized now right?  maybe I need a sort somewhere?

I saw failures in TestGrounder, TestGrounderStability, TestSRLGrounder.  I'll look at the diff  One resulted in
[info] TestSRLGrounder:
[info] SRLCompositionalGrounder
[info] org.clulab.wm.eidos.text.englishGrounding.TestSRLGrounder *** ABORTED ***
[info]   java.lang.StackOverflowError:
[info]   at org.clulab.wm.eidos.groundings.grounders.SRLCompositionalGrounder$$anonfun$getArguments$2.apply(SRLCompositionalGrounder.scala:293)
[info]   at org.clulab.wm.eidos.groundings.grounders.SRLCompositionalGrounder$$anonfun$getArguments$2.apply(SRLCompositionalGrounder.scala:293)
[info]   at scala.collection.TraversableLike$$anonfun$filterImpl$1.apply(TraversableLike.scala:248)
[info]   at scala.collection.IndexedSeqOptimized$class.foreach(IndexedSeqOptimized.scala:33)
[info]   at scala.collection.mutable.ArrayOps$ofRef.foreach(ArrayOps.scala:186)
[info]   at scala.collection.TraversableLike$class.filterImpl(TraversableLike.scala:247)
[info]   at scala.collection.TraversableLike$class.filter(TraversableLike.scala:259)
[info]   at scala.collection.mutable.ArrayOps$ofRef.filter(ArrayOps.scala:186)
[info]   at org.clulab.wm.eidos.groundings.grounders.SRLCompositionalGrounder.getArguments(SRLCompositionalGrounder.scala:293)
[info]   at org.clulab.wm.eidos.groundings.grounders.SRLCompositionalGrounder.org$clulab$wm$eidos$groundings$grounders$SRLCompositionalGrounder$$getThemes(SRLCompositionalGrounder.scala:279)

@kwalcock this has not been forgotten i promise

Please see #1047 for a merging from master with conflicts resolved.

Please see #1047 for a merging from master with conflicts resolved.

thanks for the reminder!

@kwalcock sorry, got caught in meetings but just pushed, I was thinking of making a test from the document you gave me -- thoughts?

It's probably a large document for a test.  Did you happen to notice that the problem was with a particular sentence?  I hadn't done that yet.  Or do you think some kind of problematic structure should be generated to specifically target a sensitive operation?  I'd be content to add a single sentence for now.

It's not too big, but yay for tests, I found a bug :)
fixing now

OK, failing tests are:
[error] 	org.clulab.wm.eidos.text.englishGrounding.TestGrounding
[error] 	org.clulab.wm.eidos.document.TestDocumentAttachment
[error] 	org.clulab.wm.eidos.document.TestSentenceClassifier
looking now

@kwalcock  i fixed the one test file (and corresponding tests) -- the srl roots are no longer what we want for our predicates (possibly they never were).
The other two seem to have something to do with the Document attachment for relevance (and the sentence classifier).  I didn't adjust that part of the code, is it possible that some change in processors (this branch upped the procVersion)  is causing a problem there?

Some of the tests had just worked in master.  It is the case that the ontology has been updated just recently.  It could be that the new version has kicked in.  It's possible to get the previous version by changing the line in build.sbt from "master-SNAPSHOT" to "2.1" or something like that (see https://jitpack.io/docs/).  If that works, a separate step can be used to make the tests pass with "2.2".  That's just a guess.  You might have to compare files to see if it's really the case.

but the sentence classifier isn’t related to grounding, right?
i fixed the tests that broke bc of the new ontology version (resulted in
improved tests really)
On Thursday, July 15, 2021, Keith Alcock @.***> wrote:

External Email
Some of the tests had just worked in master. It is the case that the
ontology has been updated just recently. It could be that the new version
has kicked in. It's possible to get the previous version by changing the
line in build.sbt from "master-SNAPSHOT" to "2.1" or something like that
(see https://jitpack.io/docs/). If that works, a separate step can be
used to make the tests pass with "2.2". That's just a guess. You might have
to compare files to see if it's really the case.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/clulab/eidos/pull/1042#issuecomment-881154759, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/ABJCPCMFASK66WTNNIPEITDTX6TTNANCNFSM5ABJDOOA
.

I think i found the problem!!
I think the sentence classifier was disabled because I wasn't using the flat grounding (I was only using compositional in the config).  I am going to push a permanent fix

🥇

@kwalcock please give this a whirl on a few k docs and hopefully it will (a) work, (b) not crash, (c) not be slower, and (d) be better groundings -- PLUS it's soooo pretty 🥰

Word on the street is that it is beautiful code.  How can anyone know that the groundings are better?

Agreed!
On Tue, Jul 20, 2021 at 09:13 Becky Sharp @.***> wrote:

perhaps @zupon https://github.com/zupon can run it on some documents he
previously used and we can compare? thoughts @MihaiSurdeanu
https://github.com/MihaiSurdeanu ?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/clulab/eidos/pull/1042#issuecomment-883103001, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAI75TXXNESY2NXZ4OT3OULTYUH2FANCNFSM5ABJDOOA
.

So far there hasn't been a problem with any crash after more than 60K documents.  One test measured it being slower at 61 seconds when the previous version got 34 seconds, but it's close enough.  Whether it's working or better, I don't know.

Nice!
On Wed, Jul 21, 2021 at 18:23 Keith Alcock @.***> wrote:

So far there hasn't been a problem with any crash after more than 60K
documents. One test measured it being slower at 61 seconds when the
previous version got 34 seconds, but it's close enough. Whether it's
working or better, I don't know.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/clulab/eidos/pull/1042#issuecomment-884277629, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAI75TVOEU52G2U6O4ELUULTY3RA7ANCNFSM5ABJDOOA
.

So far there hasn't been a problem with any crash after more than 60K documents. One test measured it being slower at 61 seconds when the previous version got 34 seconds, but it's close enough. Whether it's working or better, I don't know.

Send me a doc or 2?

Not until after midnight.  You're still on vacation.

jsonld files went out via email.

Perfect!  @zupon ran into this earlier today.

Is it OK to merge this after the tests pass?

Is it OK to merge this after the tests pass?

yes, thanks! if they fail I'll try to fix them asap

Is it OK to merge this after the tests pass?

yes, thanks! if they fail I'll try to fix them asap

yep, some failed. on it.

ok @kwalcock I'm befuddled.  the TestSRLGrounder and TestGrounding failed, according to jenkins (our helpful butler).  BUT when I look at the console log from jenkins, I can't find the failed tests.  When I grep for a string I'd expect to see (e.g., "SRLCompositionalGrounder" from the behavior of... block) it's not there.  Further, when I run them locally, they pass.  Git says that I don't have anything in my configs that is diff... help?

Did you click on "Full Log" at the top of the console output?  A change in the ontology, like the one committed today, could break tests.  Sometimes that dependency is slow to update locally.  Can you run that app ShowOntologyVersion?  I would expect 872c52924b3a73668f3b2801e3a5fdfa6fbde951 for the most recent changes.

Did you click on "Full Log" at the top of the console output? A change in the ontology, like the one committed today, could break tests. Sometimes that dependency is slow to update locally. Can you run that app ShowOntologyVersion? I would expect 872c52924b3a73668f3b2801e3a5fdfa6fbde951 for the most recent changes.

thanks -- looking now!

Thanks.  Someday something should happen to those tests.  Not today, though.


Fix disqus identifier (+ all the things)

markdown was renaming .md to .html which is not nice (see the shittty
plugin I had to make to allow raw html files not wrapper by react
templates).
So I dropped metalsmith-markdown (which hardcode the renaming) and
metalsmith-metallic for a homemade plugin to get back previous markdown
integration (hello anchor links).
I also stripped all html tags from title to avoid anchor like
-em-some-text-em-.
I also trimmed dash from escaped slug, that’s cool
While I was on that, I improved the highlight (which close #319).
Since I removed the hardcoding of .md to .html, I wrote a plugin to
rename files. So files are now renamed via a metalsmith plugin when we
ask for it, not by “you don’t know which plugin”.
Since we are renaming after md to react/html I had to create a plugin
to add url metdata.  Having
url field will allow us to have cleaner code so we can fix #377
the url field can also be used by the rss plugin so let’s use it
I also removed useless code from react-template plugin since renaming
is out (this was some legacy code from the original shitty plugin)
while removing some code, I droppped debug module, because using log
to debug is so 90’
No I can fix disqus identifier (close #377) with a smile

gg mec


Uncaught Error: undefined group option

[Enter steps to reproduce below:]

...
...

Atom Version: 1.2.3
System: Mac OS X 10.11.2
Thrown From: Atom Core
Stack Trace
Uncaught Error: undefined group option
At /Applications/Atom.app/Contents/Resources/app.asar/node_modules/first-mate/lib/scanner.js:31

Error: undefined group option
    at Error (native)
    at Scanner.module.exports.Scanner.createScanner (/Applications/Atom.app/Contents/Resources/app.asar/node_modules/first-mate/lib/scanner.js:31:24)
    at Scanner.module.exports.Scanner.getScanner (/Applications/Atom.app/Contents/Resources/app.asar/node_modules/first-mate/lib/scanner.js:37:31)
    at Scanner.module.exports.Scanner.findNextMatch (/Applications/Atom.app/Contents/Resources/app.asar/node_modules/first-mate/lib/scanner.js:56:22)
    at Rule.module.exports.Rule.findNextMatch (/Applications/Atom.app/Contents/Resources/app.asar/node_modules/first-mate/lib/rule.js:99:28)
    at Rule.module.exports.Rule.getNextTags (/Applications/Atom.app/Contents/Resources/app.asar/node_modules/first-mate/lib/rule.js:141:21)
    at Grammar.module.exports.Grammar.tokenizeLine (/Applications/Atom.app/Contents/Resources/app.asar/node_modules/first-mate/lib/grammar.js:150:44)
    at TokenizedBuffer.module.exports.TokenizedBuffer.buildTokenizedLineForRowWithText (/Applications/Atom.app/Contents/Resources/app.asar/src/tokenized-buffer.js:546:28)
    at TokenizedBuffer.module.exports.TokenizedBuffer.buildTokenizedLineForRow (/Applications/Atom.app/Contents/Resources/app.asar/src/tokenized-buffer.js:532:19)
    at TokenizedBuffer.module.exports.TokenizedBuffer.tokenizeNextChunk (/Applications/Atom.app/Contents/Resources/app.asar/src/tokenized-buffer.js:292:43)
    at /Applications/Atom.app/Contents/Resources/app.asar/src/tokenized-buffer.js:269:26
    at /Applications/Atom.app/Contents/Resources/app.asar/node_modules/underscore-plus/node_modules/underscore/underscore.js:666:47

Commands
     -0:11.6.0 application:new-file (atom-text-editor.editor.is-focused)
     -0:09.9.0 settings-view:check-for-package-updates (atom-workspace.workspace.scrollbars-visible-when-scrolling.theme-atom-dark-syntax.theme-atom-dark-ui)
     -0:06.7.0 encoding-selector:show (atom-text-editor.editor)
  4x -0:05.1.0 core:backspace (atom-text-editor.editor.mini.is-focused)
     -0:02.2.0 grammar-selector:show (atom-text-editor.editor)
     -0:00.7.0 core:confirm (atom-text-editor.editor.mini.is-focused)

Config
{
  "core": {
    "themes": [
      "atom-dark-ui",
      "atom-dark-syntax"
    ]
  },
  "editor": {
    "invisibles": {},
    "preferredLineLength": 160,
    "showIndentGuide": true,
    "fontSize": 12
  }
}

Installed Packages
# User
highlight-selected, v0.11.1
ios, v0.1.0
language-jade, v0.6.2
linter, v1.11.2
linter-flake8, v1.9.2
linter-javac, v1.3.0

# Dev
No dev packages

What grammar were you switching to? Likely an issue with the grammar, but we should be better about identifying it.

Thank you for your issue!
We haven't gotten a response to our questions in our comment https://github.com/atom/atom/issues/9733#issuecomment-158661045. With only the information that is currently in the issue, we don't have enough information to take action. I'm going to close this but don't hesitate to reach out if you have or find the answers we need, we'll be happy to reopen the issue.


temp fix of OOM from large group by

This PR is temporary fix to an issue where an Spark job that depends on Evaluation fail due to out of memory exception.
The root cause was introduced in https://github.com/airbnb/aerosolve/pull/231.  We ran .collect on RDD too early, resulting huge list when data is big. This PR won't fix the root cause but will get let the job pass by removing the most expensive operation on the big list. I've verified that the job will successfully finish with this change.
Because the job has been failing two weeks ago, we need some time to backfill. So I propose to merge this PR ASAP so that the failing job will pick up. After that, we can work on the permanent fix .
@jq @deerzq

Oh I had talked with Andy about this before. We should just move all the code to RDD instead of List. I have a fix and will send a PR shortly.


Issue with Start the Emulator and connect your bot

In the section start the emulator and connect your bot, it doesn't say that you need to alter the url shown in the terminal. For example, the terminal says: restify listening to http://[::]:3978. If you add this to your configuration, you get issues where it thinks the bot is remote. If you change it to localhost:3978, it the remote error is resolved. However, the messages still don't work. It's only after you set the endpoint URL to localhost:3978/api/messages, that the echo bot works as designed. We should update the docs to provide additional details for setting this up.

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

ID: f55c86f2-9c0d-015b-d44f-58914fed2deb
Version Independent ID: 85fe7f0c-002a-e449-55cb-712d92874b19
Content: Create a bot using Bot Framework SDK for JavaScript - Bot Service
Content Source: articles/javascript/bot-builder-javascript-quickstart.md
Service: bot-service
Sub-service: sdk
GitHub Login: @JonathanFingold
Microsoft Alias: v-jofing

@erhopf It is true that we need to specify that in http://[::]:3978 should be edited with localhost for javascript bots. The addition of /api/messages is specified in emulator where we give the bot url. And also if the format is wrong the emulator won't allow the user to connect to the bot.

Thanks for your feedback! This information was included in previous versions of the article.
We have added back the following detail to both the Dotnet & JavaScript quickstarts:
"Fill out the fields for your bot. Use your bot's welcome page address (typically http://localhost:3978) and append routing info '/api/messages' to this address."
This will become available once our latest document updates go live.


Elasticsearch driver version update

We need to upgrade driver version to the most recent one (7.4).

verified


ngrx wording

Hi guys, I'm really liking this checklist - kudos to you both!
I spent a bit more time on the NgRx part and spotted some typos, hence this PR.
I've also added some smaller details here and there.

Looks perfect. Thanks for this!
Could you just reword your commit message to follow angular's conventional changelog? Thanks!

Thanks @timdeschryver!


EnableTurbineStream with Kafka

I follow the guide : https://cloud.spring.io/spring-cloud-netflix/single/spring-cloud-netflix.html#_turbine config my turbine stream server, but doesn't work. hystrix-dashboard always loading ...
curl /turbine.stream:
data:{"type":"ping"}
data:{"type":"ping"}

turbine stream server:
@EnableTurbineStream
@EnableDiscoveryClient
@SpringBootApplication
public class Turbine02Application {
    public static void main(String[] args) {
        SpringApplication.run(Turbine02Application.class, args);
    }
}

gradle dep:  2.1.0.RELEASE
dependencies {
    implementation 'org.springframework.boot:spring-boot-starter-actuator'
    implementation 'org.springframework.cloud:spring-cloud-starter-netflix-turbine-stream'
    implementation 'org.springframework.cloud:spring-cloud-starter-stream-kafka'
}

console output:
Cannot determine local hostname
Initializing ExecutorService 'taskScheduler'
Registering MessageChannel nullChannel
Registering MessageChannel errorChannel
Registering MessageChannel turbineStreamInput
Registering MessageHandler hystrixStreamAggregator.sendToSubject.serviceActivator
Registering MessageHandler errorLogger
Adding {logging-channel-adapter:_org.springframework.integration.errorLogger} as a subscriber to the 'errorChann
Channel 'turbine02-1.errorChannel' has 1 subscriber(s).
started _org.springframework.integration.errorLogger
Adding {service-activator:hystrixStreamAggregator.sendToSubject.serviceActivator} as a subscriber to the 'turbin
Channel 'turbine02-1.turbineStreamInput' has 1 subscriber(s).
started hystrixStreamAggregator.sendToSubject.serviceActivator
Setting initial instance status as: STARTING
Initializing Eureka in region us-east-1
Using JSON encoding codec LegacyJacksonJson
Using JSON decoding codec LegacyJacksonJson
Using XML encoding codec XStreamXml
Using XML decoding codec XStreamXml
Resolving eureka endpoints via configuration
Disable delta property : false
Single vip registry refresh property : null
Force full registry fetch : false
Application is null : false
Registered Applications size is zero : true
Application version is -1: true
Getting all instance registry info from the eureka server
The response status is 200
Starting heartbeat executor: renew interval is: 30
InstanceInfoReplicator onDemand update allowed rate per min is 4
Discovery Client initialized at timestamp<PHONE_NUMBER>610 with initial instances count: 2
Registering application TURBINE02 with eureka with status UP
Saw local status change event StatusChangeEvent [timestamp=1554890192615, current=UP, previous=STARTING]
DiscoveryClient_TURBINE02/localhost:turbine02:8051: registering service...
DiscoveryClient_TURBINE02/localhost:turbine02:8051 - registration status: 204
Netty started on port(s): 8051
Updating port to 8051
Started Turbine02Application in 24.716 seconds (JVM running for 26.409)
Starting aggregation
Unsubscribing aggregation.

kafka topic : [hystrixStreamOutput] have data like :
{"origin":{"host":"localhost","port":8030,"serviceId":"consumer01","id":"consumer01-1"},"data":{"type":"HystrixThreadPool","name":"annotation_hello_group_key","currentTime":1554881732305,"currentActiveCount":0,"currentCompletedTaskCount":42,"currentCorePoolSize":10,"currentLargestPoolSize":10,"currentMaximumPoolSize":10,"currentPoolSize":10,"currentQueueSize":0,"currentTaskCount":42,"rollingCountThreadsExecuted":0,"rollingMaxActiveThreads":0,"propertyValue_queueSizeRejectionThreshold":5,"propertyValue_metricsRollingStatisticalWindowInMilliseconds":10000,"reportingHosts":1}}

Can you provide a complete, minimal, verifiable sample that reproduces the problem?  It should be available as a GitHub (or similar) project or attached to this issue as a zip file.

Can you provide a complete, minimal, verifiable sample that reproduces the problem? It should be available as a GitHub (or similar) project or attached to this issue as a zip file.

ok, thanks. gitee  turbine02-amqp project.

Can you please provide detailed instructions on how to recreate the error

Can you please provide detailed instructions on how to recreate the error

I fixed it. Thank you very much.

How did you solve it?@tomZF


fix(build): main migration release

:tada: This PR is included in version 5.0.1 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Update README.md

Confirm the error in the following discussion thread.
https://groups.google.com/forum/#!topic/digits-users/58zEGIbwQw0
Environment:
Ubuntu 14.04 fresh install. Everything up to date with apt-get update and upgrade.
Cuda 7.0 Fresh install
Gigabyte Geforce 770 4GB OC
Caffe version 0.13 Nvidia port, did not test with 0.12 branch
Followed instruction step by step.

Thanks for contributing!
Did this comment not do the trick?

Don't forget to set your path. For example:

CUDA_HOME=/usr/local/cuda
LD_LIBRARY_PATH=$CUDA_HOME/lib64:$LD_LIBRARY_PATH

https://github.com/NVIDIA/DIGITS/blob/v2.1.0/README.md#cuda

@ZhijieWang, I just got confirmation from one of our engineers that ldconfig is not a good solution. I'll paste his full response:

sudo ldconfig /foo/bar/path is only temporary until ldconfig is run again.

The following will happen to users using this method:

User installs CUDA
User runs sudo ldconfig /usr/local/cuda/lib64
User is happy because ldconfig sees cuda libraries
Months down the road user installs a library package. Library package runs ldconfig as part of it's required post installation actions. This removes /usr/local/cuda/lib64 from ldconfig's database.
User is grumpy because ldconfig no longer sees cuda libraries

This will be fixed for CUDA 8.0.

CUDA 8.0 rpm/deb packages will start installing ld.so.conf.d files and will ldconfig for you so you don’t need to edit LD_LIBRARY_PATH in CUDA 8.0 for rpm/deb.


Create package for libnvidia-egl-wayland libs

Create package for egl-wayland libs. This is related to pull request # https://github.com/openSUSE/nvidia-driver-G06/pull/10

Indeed this package already existed and is on version 1.1.16. wayland-protocols is too old to build it on sle15-sp6, but we plan to update wayland-protocols for sle15-sp7.

@scaronni-nvidia JFYI, see my comment above.

Indeed this package already existed and is on version 1.1.16. wayland-protocols is too old to build it on sle15-sp6, but we plan to update wayland-protocols for sle15-sp7.

Integrated this logic with latest pull request. Closing.


Image Widget's chooser modal should show minimums/specifications like minSize

Otherwise editors are given a subset of their media library without knowing why

Yup, and worse, they can upload an image and save it and then not see it in the chooser.


parser: Match parser fails when a byte literal is encountered as a case pattern

The parser fails with expected '=>' after pattern case if a case is a byte literal:
function main() {
  match b'.' {
    b';' => 0
    else => 1
  }
}

Match only accepts values as (expr) =>, right now only variant names are allowed without parenthesis:
unction main() {
  match b'.' {
    (b';') => 0
    else => 1
  }
}

oh okay, thank you. Should we leave this or close this?

The error should be more clear at the very least, and the syntax is still fairly experimental (like most of the language :P), so we can leave the issue open for "improve error message"

Since https://github.com/SerenityOS/jakt/commit/b0b7bddf6015319342418b43dd9c3ad3ce5102bd bare literals are accepted, so looks like this is not an issue anymore


Add missing python package dependency

Add missing python package dependency

Thanks, if this doesn't do it, I'll look further.

That did it, all good.


BUG: Babel config parsing error

Description
The error shows when the tests for text component converted from tsx to js
Related Tickets & Documents

The issue was caused by locally installed eslint extension. Disabling the extension it fixes the error.


Prepare for release v1.12.0-rc3

Summary of Changes
Major Changes:

Add support for Kubernetes v1.24.0 (#19545, @aanm)
Delegated IPAM plugin (#19219, @wedaly)
Enables ICMP network policy function by default (#20174, @chez-shanpu)

Minor Changes:

Add concurrency limiting for DNS message processing (#19592, @nebril)
Add config flag to add a prefix to AgentNotReadyNodeTaint value in order to enable the taint being ignored by cluster autoscaler. (#19247, @thejosephstevens)
Add counter to track all datapath timeouts due to FQDN IP updates (#19809, @ungureanuvladvictor)
Add emptyDir volume for frontend container of hubble-ui (#20027, @mkilchhofer)
Add metric on datapath update latency due to FQDN IP updates (#19992, @rahulkjoshi)
Add source filter for the cilium fqdn cache list command (#19980, @ungureanuvladvictor)
add support for AKS BYOCNI (#19379, @nbusseneau)
Add support for getting earliest events from Observer API (#19819, @chancez)
Add support for L7 policies with VTEP integration (#19473, @vincentmli)
Add support to opt-in for using ENI's primary IP for allocations (#20050, @hemanthmalla)
Add type label to the identity metric (#19999, @ungureanuvladvictor)
bgp: Check the Condition.Ready field when adding ready endpoints (#20176, @ysksuzuki)
Bugtool: Add additional Linux traffic-control (tc) data to cilium-bugtool output. (#19856, @tommyp1ckles)
Change default agent health check port to avoid conflicts (#19830, @tklauser)
Change default prometheus ports to new reserved Cilium ports (#20156, @knfoo)
clustermesh: Add support for service-affinity (#19521, @sayboras)
Dynamic Per Resource Timeouts (#19991, @tommyp1ckles)
envoy: Bump cilium envoy to latest version v1.21.3 (#20142, @sayboras)
feat(helm): allow to set Hubble Relay and UI service type and nodePort (#19450, @raphink)
helm: add description for some Helm values (#19658, @my-git9)
install/kubernetes: Add CAP_IPC_LOCK for mmap (#19812, @sayboras)
Introduce a new CRD (CiliumEgressGatewayPolicy) for Egress Gateway configuration. Deprecate the previous CRD (CiliumEgressNATPolicy). (#19561, @julianwiedmann)
IPSec key rotation without agent restart (#19814, @jibi)
Move the BGP Control Plane to utilize CiliumNode objects. This enable support for IPAM driven PodCIDR announcements. (#19872, @ldelossa)
Runtime device detection (#17460, @joamaki)
Speed up identity lookup in Hubble and L7 proxy by no longer calculating SHA256 over labels. (#20104, @tklauser)
ui: v0.9.0 images and drop envoy proxy container (#19565, @geakstr)
Update to CNI spec version 1.0.0 (#19719, @tklauser)
Use DeleteOnMetadataMatch instead of Delete for endpointUpdated (#19996, @kvaster)

Bugfixes:

Add missing packet trace for some non-NodePort SNAT egress (#19158, @YutaroHayakawa)
bpf: Use tunnel port flag instead of hardcoded value (#20115, @pchaigno)
cilium: fix conflicting iptables-legacy and iptables-nft rules (#20123, @jrfastab)
cli: Update regex for key value validation (#19794, @sayboras)
cli: Use custom named map instead of StringToStringVar (#19968, @sayboras)
clustermesh: Add ownerReferences for CiliumNodes (#19959, @sayboras)
cmd: Allow more complicated patterns in map string type. (#19955, @sayboras)
contrib: Fix passing ipFamily to kind.sh (#19707, @brb)
datapath: Fix implicit-int-conversion err in common.h (#19832, @brb)
endpoint: Fix packets to host dropped with the chaining mode and host firewall (#19734, @ysksuzuki)
Fix agent panic in some cases when service matcher local redirect policy was deployed prior to the selected service. (#19522, @aditighag)
Fix Azure IPAM 403 errors for Azure instances using Azure Compute Gallery images (#19697, @andrew-bulford-form3)
Fix blackhole route error when cleanup (#20042, @soulseen)
Fix bug where established host connections would be interrupted on agent restart if the host firewall was enabled. (#19998, @pchaigno)
Fix Cilium bootstrapping regression with etcd without relying on DNS (#20106, @aanm)
Fix Cilium initialization for clusters with etcd-operator (#20131, @aanm)
Fix error propagation in bpf_lxc (#20144, @DolceTriade)
Fix memory leak in the DNS cache when a long-lived endpoint makes many unique DNS lookups over time (#19925, @christarazi)
Fix race condition leading to inconsistent CiliumNode that can cause the agent to fatal. (#19923, @pchaigno)
Fixed SystemD >=245 sysctl(rp_filter) config incompatibility (#20072, @dylandreimerink)
Fixes a bug in the BGP control plane which causes the wrong BGP virtual servers to be selected for reconciliation or removal (#19659, @ldelossa)
helm: Relax hubble ui image versions validation (#20039, @sayboras)
iptables: ensure all rules are installed consistently (#19693, @jibi)
iptables: fix typo in addProxyRule condition (#20109, @jibi)
nodediscovery: ensure we cache the nodeResource correctly to avoid null pointer dereferencing (#20158, @odinuge)
nodemanager: Fix bug where Cilium tried to reach stale health endpoints on kubeapi-server nodes (#20210, @gandro)
operator: Add cilium node garbage collector (#19576, @sayboras)

CI Changes:

.github/workflows: bump v1.10 workflows to cilium-cli v0.10.5 (#19897, @tklauser)
.github/workflows: bump v1.10 workflows to cilium-cli v0.10.6 (#19935, @tklauser)
.travis: Disable race build on master (#19773, @pchaigno)
Add missing VTEP complexity tests (#19539, @vincentmli)
Add support for tparse in go test targets (#20032, @joestringer)
bpf: Reenable features disabled because of complexity issues (#19938, @pchaigno)
build(deps): bump actions/setup-go from 3.1.0 to 3.2.0 (#19971, @dependabot[bot])
checkpatch: Update image for "checkpatch" target, reuse target in CI (#19805, @qmonnet)
ci-l4lb: Check out stable branch (#19905, @michi-covalent)
ci: fix documentation workflow (#20025, @nbusseneau)
ci: Increase retention for release image CI artifacts to 10 days (#20141, @michi-covalent)
CI: merge NAT46x64 and L4LB GH actions (#19288, @brb)
ci: pick up cilium-cli v0.11.9 for master/v1.11 workflows (#20234, @tklauser)
ci: provide CI images with unstripped binaries (#20238, @tklauser)
ci: set Cilium base version to v1.10.12 in v1.10 conformance tests (#19946, @tklauser)
fix aws-cni conformance test (#20049, @aanm)
ipcache: Fix failing controller check from SupportsDelete (#19751, @joamaki)
jenkins: switch to ad-hoc GKE cluster creation/deletion (#19918, @nbusseneau)
Load the dev operator image into kind/microk8s as well (#19995, @ungureanuvladvictor)
master/v1.11 CI: Pick up the latest cilium-cli (#19873, @michi-covalent)
mlh: update Jenkins jobs following 1.24 support (#19904, @nbusseneau)
mlh: update Jenkins jobs following net-next fix for K8s 1.24 (#20220, @nbusseneau)
Revert "ci: use CLI 0.11.8 for AKS workflow" (#20272, @tklauser)
test: add git safe directory in test VMs (#19860, @tklauser)
test: Add info which L4LB request fails (#19714, @brb)
test: Add TS to each bash dbg output in L4LB (#20094, @brb)
test: Also delete hubble-peer when cleaning up old tests. (#19979, @DolceTriade)
test: Bump L4LB timeout from 30min to 45min (#20151, @brb)
test: Do not completely quarantine E/W svc suite (#19960, @brb)
test: Remove unused Nightly suites (#20128, @brb)
test: Use more explicit key for k8s3's taint (#19951, @pchaigno)
test: Wait for pod termination in K8sServicesTest (#19750, @brb)
tests-l4lb: Use Helm chart from local branch (#19953, @michi-covalent)
Update 5.4 VM image (#19842, @pchaigno)
update bpf_ct_tests.c to use node_config.h (#20177, @sahid)
vagrant: Bump 4.19 VM image (#20185, @pchaigno)
vagrant: Bump net-next Vagrant box version (#19915, @pchaigno)
vagrant: Fix IPv6 NAT setup (#19997, @pchaigno)
workflow: aws-cni-v1.10: use helm chart from PR (#19952, @jibi)
workflow: checkout correct ref in v1.10 and v1.11 l4lb workflows (#19898, @jibi)
workflow: l4lb: pass correct path for PR checkout (#20007, @jibi)
workflow: use correct bwm helm option for v1.11 AWS CNI test (#19895, @jibi)
workflows: Downgrade to helm v3.8.2 to fix AWS CNI runs for v1.10 (#20073, @joamaki)
workflows: Pin the kubectl version used with EKS workflows (#19716, @joamaki)
workflows: update v1.10 workflows to v0.10.7 cilium CLI (#20020, @jibi)

Misc Changes:

Add a note about conflicting node CIDRs #20204 (#20208, @wokalski)
Add Deckhouse to users (#19804, @konstantin-axenov)
Added ByteDance to users.md (#19823, @Jiang1155)
Adding IKEA IT AB to the USERS.md (#20099, @knfoo)
Adding Overstock to the USERS.md (#19762, @ntaylor1781)
Allocate Ingress IPs for new reserved:ingress identity (#19764, @jrajahalme)
api: change "group not found" log to debug (#19927, @tklauser)
api: generate markdown documentation for gRPC APIs (#18799, @rolinh)
bpf: Don't hardcode cb CB_ENCRYPT_DST index (#20105, @pchaigno)
bpf: Rename tail call targets (#19807, @pchaigno)
bpf: specify handle_lxc_traffic return type to fix -Wimplicit-int error (#19891, @tklauser)
bpf: Split bpf_lxc CT lookups to their own tail calls (#19818, @pchaigno)
bugtool: Add structured node and health output (#20011, @gandro)
build(deps): bump actions/cache from 3.0.2 to 3.0.3 (#20029, @dependabot[bot])
build(deps): bump actions/cache from 3.0.3 to 3.0.4 (#20093, @dependabot[bot])
build(deps): bump actions/setup-go from 3.0.0 to 3.1.0 (#19801, @dependabot[bot])
build(deps): bump actions/upload-artifact from 3.0.0 to 3.1.0 (#19899, @dependabot[bot])
build(deps): bump docker/build-push-action from 2.10.0 to 3 (#19725, @dependabot[bot])
build(deps): bump docker/login-action from 1.14.1 to 2 (#19727, @dependabot[bot])
build(deps): bump docker/setup-buildx-action from 1.7.0 to 2 (#19728, @dependabot[bot])
build(deps): bump docker/setup-qemu-action from 1.2.0 to 2 (#19722, @dependabot[bot])
build(deps): bump github.com/cilium/ebpf from 0.8.1 to 0.9.0 (#19972, @dependabot[bot])
build(deps): bump github.com/containernetworking/cni from 1.1.0 to 1.1.1 (#20058, @dependabot[bot])
build(deps): bump github.com/docker/docker from 20.10.14+incompatible to 20.10.16+incompatible (#19811, @dependabot[bot])
build(deps): bump github.com/docker/docker from 20.10.16+incompatible to 20.10.17+incompatible (#20136, @dependabot[bot])
build(deps): bump github.com/go-openapi/runtime from 0.24.0 to 0.24.1 (#19736, @dependabot[bot])
build(deps): bump github.com/go-openapi/validate from 0.21.0 to 0.22.0 (#20119, @dependabot[bot])
build(deps): bump github.com/google/gops from 0.3.22 to 0.3.23 (#19737, @dependabot[bot])
build(deps): bump github.com/hashicorp/consul/api from 1.12.0 to 1.13.0 (#20121, @dependabot[bot])
build(deps): bump github.com/osrg/gobgp/v3 from 3.1.0 to 3.2.0 (#19667, @dependabot[bot])
build(deps): bump github.com/osrg/gobgp/v3 from 3.2.0 to 3.3.0 (#20071, @dependabot[bot])
build(deps): bump github.com/shirou/gopsutil/v3 from 3.22.4 to 3.22.5 (#20044, @dependabot[bot])
build(deps): bump github.com/spf13/cast from 1.4.1 to 1.5.0 (#19780, @dependabot[bot])
build(deps): bump github.com/spf13/viper from 1.11.0 to 1.12.0 (#19988, @dependabot[bot])
build(deps): bump github.com/stretchr/testify from 1.7.1 to 1.7.2 (#20120, @dependabot[bot])
build(deps): bump github.com/stretchr/testify from 1.7.2 to 1.7.3 (#20253, @dependabot[bot])
build(deps): bump github/codeql-action from 2.1.11 to 2.1.12 (#20057, @dependabot[bot])
build(deps): bump github/codeql-action from 2.1.9 to 2.1.11 (#19853, @dependabot[bot])
build(deps): bump golang.org/x/tools from 0.1.10 to 0.1.11 (#20159, @dependabot[bot])
build(deps): bump golangci/golangci-lint-action from 3.1.0 to 3.2.0 (#19779, @dependabot[bot])
build(deps): bump google.golang.org/grpc from 1.46.0 to 1.46.2 (#19835, @dependabot[bot])
build(deps): bump google.golang.org/grpc from 1.46.2 to 1.47.0 (#20045, @dependabot[bot])
build(deps): bump gopkg.in/ini.v1 from 1.66.4 to 1.66.6 (#20021, @dependabot[bot])
build(deps): bump helm/kind-action from 1.2.0 to 1.3.0 (#20198, @dependabot[bot])
build(deps): bump KyleMayes/install-llvm-action from 1.5.2 to 1.5.3 (#19865, @dependabot[bot])
build(deps): bump library/alpine from 3.15.4 to 3.16.0 in /images/cache (#19943, @dependabot[bot])
Capital One added to Users doc (#20084, @bradwhitfield)
cilium: make tcp rebalance grace period configurable (#19800, @borkmann)
CODEOWNERS: Extend proxy group to pkg/fqdn (#19874, @christarazi)
contrib/scripts: Support env vars for kind script (#20035, @christarazi)
contrib: Support contrib/scripts/kind.sh on macOS (#20096, @sayboras)
daemon, option: remove deprecated native-routing-cidr option (#19677, @tklauser)
daemon, option: remove deprecated prefilter-* options (#19913, @julianwiedmann)
daemon: Fix build after VTEP routes conflict (#20077, @joestringer)
datapath: Improve sysctl warning for bpf_jit_enable (#20018, @joamaki)
datapath: Improved BPF testing framework (#20017, @dylandreimerink)
datapath: Use FROM_NETDEV instead of FROM_LXC in nodeport.h (#19986, @brb)
dependabot: Unignore prometheus/client_golang (#20075, @ti-mo)
Do not disable peer service when hubble.listenAddress is empty (#19886, @chancez)
doc: add note about checkpatch during dev workflow (#19879, @sahid)
doc: update doc to inform about SERVER_BOX/VERSION (#19749, @sahid)
doc: VTEP redirection and L7 policy partially incompatible (#19700, @vincentmli)
docs(MAINTAINERS): fix link to commit_access.rst (#20081, @raphink)
docs(README): add logo option for dark theme (#19920, @raphink)
docs, ci, test/l4lb: use latest cilium-cli release according to stable.txt (#20203, @tklauser)
docs: Add default conntrack gc interval (#19977, @aditighag)
docs: Add developers guide page about BPF testing framework (#20165, @dylandreimerink)
docs: Add docs-builder build as dependency to live preview (#19885, @qmonnet)
docs: Add getting started docs for Ingress (#19760, @sayboras)
docs: Add interactive help for make targets (Documentation/Makefile) (#20012, @qmonnet)
docs: add kube-apiserver to the special identity list (#20047, @kaworu)
docs: add missing ingress special identity (#20060, @kaworu)
docs: added GSoD technical writers (#19799, @xmulligan)
docs: Document operator.unmanagedPodWatcher (#19820, @joestringer)
docs: Fix and clean-up the build framework for the documentation (#19969, @qmonnet)
docs: Fix build after etcd v3.5.4 version bump (#20171, @joestringer)
docs: Fix incorrect command in IPsec GSG (#19767, @pchaigno)
docs: Fix incorrect FQDN flag (#19930, @pchaigno)
docs: Fix max SPI value for IPsec key rotations (#19893, @pchaigno)
docs: Fix reference to upgrade guide (#20184, @joestringer)
docs: Mark Git repo as safe in Docker build-docs container (#19861, @qmonnet)
docs: Mention KPR in DR mode sec ID limitation (#19113, @brb)
docs: minor fixes (#20218, @julianwiedmann)
docs: Nit changes to steps for image building (#20153, @pchaigno)
docs: Remove '\r' chars from grep result to parse Alpine image name (#19888, @qmonnet)
docs: remove stale EgressGW limitation with CES (#20195, @julianwiedmann)
docs: update egress gateway documentation and mark the feature stable (#19862, @jibi)
Document that clustermesh cluster-id range is 1-255 (#19683, @stonith)
Dynamic Cluster Pool follow-ups (#19777, @gandro)
Expose metrics for active FQDN connections per endpoint (#19857, @christarazi)
Fix missing capabilities when not running Cilium on containerd-based Kubernetes (#19903, @AtkinsChang)
Fix running documentation make targets on MacOS (#19900, @chancez)
Fixes:Added the declaration of license (#19834, @yulng)
gha: Add ingress conformance test (#19742, @sayboras)
gha: Add retry options for ingress sanity check (#19825, @sayboras)
gha: Bump cilum cli version to v0.11.6 (#19828, @sayboras)
go.mod, vendor: update cloud provider SDK Go modules for June 2022 (#20126, @tklauser)
helm: don't generate the hubble-peer svc during preflight checks (#19759, @kaworu)
helm: Expose agent DNS proxy parameters as chart values (#19967, @joaoubaldo)
helm: Fix syntax error in Hubble UI className (#20056, @gandro)
helm: Templatize preflight and clustermesh-apiserver repos (#20206, @michi-covalent)
helm: use port 80/443 by default for the peer service (#19933, @rolinh)
highlight values.yaml.tmpl as yaml (#20250, @kaworu)
hubble: Improve performance of identity getter (#20005, @gandro)
hubble: remove unused local observer field (#19962, @kaworu)
images/cilium: remove cilium group from Dockerfile (#19711, @aanm)
images/runtime: update CNI plugins to 1.1.1 (#19690, @tklauser)
images: Update cilium-bpftool (#20197, @NikAleksandrov)
Improve Cilium DNS Proxy-related error metrics (#19702, @christarazi)
ingress: Couple of cleanup and TODOs (#19647, @sayboras)
install/cilium-operator: fix clusterrole rules (#19686, @aanm)
install/kubernetes: Avoid quoting version twice (#20188, @joestringer)
install/kubernetes: bump etcd to v3.5.4 (#20134, @aanm)
install: Fix typos of cilium (#20113, @twpayne)
ipam: Shutdown retry trigger on node deletion (#20140, @christarazi)
ipcache: Error out from InjectLabels if Checker is nil (#19887, @jrajahalme)
ipcache: Make SupportsDelete() more robust by using a separate map (#19641, @joamaki)
ipsec: Rewrite parser for IPsec secret (#19824, @pchaigno)
k8s: Move CiliumEnvoyConfig to v2 (#19688, @jrajahalme)
maglev: use github.com/cilium/workerpool (#19940, @kaworu)
MAINTAINERS: update committers (#20014, @tklauser)
make: fix Makefile docker pull command to cause an error when using podman (#19748, @koba1t)
Makefile: Add 'make kind-image' to 'make help' (#19963, @joestringer)
Makefile: Measure unit test coverage by package (#20038, @joestringer)
metrics: Fix NaN value for cilium metrics list CLI (#19987, @sayboras)
Misc Makefile improvements for quiet mode V=0 (#20031, @joestringer)
Optimize CIDR label functions (#19843, @christarazi)
pkg/bpf: Include BPF map names during map creation (#20091, @christarazi)
pkg/fqdn: Replace remaining usages of regex compile with LRU (#19875, @christarazi)
pkg/policy/api: Optimize Decision MarshalJSON() (#19704, @MikeLing)
pkg/policy/policy: Optimize SearchContext String() (#19661, @MikeLing)
pkg/policy/rule: Optimize rule String() (#19822, @MikeLing)
preallocate memory before looping over it (#19566, @florianl)
Prepare for release v1.12.0-rc2 (#19694, @aanm)
Prepare v1.12 stable branch (#20276, @aanm)
Support builder image on arm64 (#19768, @chancez)
Support for Cilium in Exoscale SKS (#20076, @retrack)
Templatize helm template image references (#20066, @joestringer)
test/bpf: Fix format of check-complexity.sh script (#19836, @pchaigno)
test/upgrade: use the unreleased helm chart of stable branches (#19710, @aanm)
treewide: Fix typos of Kubernetes (#20114, @twpayne)
Update cli-download.rst (#20181, @nvibert)
Update Go to 1.18.2 (#19775, @tklauser)
Update Go to 1.18.3, golangci-lint to 1.46.2 (#20061, @tklauser)
Update stable releases (#19841, @joestringer)
Update stable releases (#20224, @joestringer)
Update USERS.md (#19837, @edude03)
Update USERS.md (#20002, @FaKod)
UPDATE users.md: Add CONNY (#19815, @ant31)
update-docs : add details for how to enable/disable Policy Audit Mode by endpoint (#19876, @BryanStenson-okta)
Use FQDN regex LRU everywhere (#19632, @christarazi)
vagrant: add git exception in dev VMs for cilium repo for root user (#19855, @jibi)
Various cleanups around pkg/datapath (#20041, @tklauser)

/test-backport-1.12

/test-backport-1.12


Naked domain bedanktvoorhetcontact.nl does not work

Leads to vimexx again

Hi Theo,
I believe you were seeing cached results which were still pointing at your domain registrar.
When I visit the bedanktvoorhetcontact.nl domain it redirects to www.bedanktvoorhetcontact.nl as expected. Can you please try again in a private browser session or on a different computer/phone and see if you get the correct result?


Feat: Add setting for using lowercase v.s. uppercase letters

TLDR
Wanted to be able to play in uppercase as well as lowercase mode so this PR adds that small setting.
Description
Hi, Steve ✌🏽. I played with my 4 and 3 year olds this morning who I'v been trying to teach the alphabet. Unfortunately, I haven't yet taught my 4 year old lowercase letters yet so she had a hard time. I thought it would be cool to be able to play in uppercase mode as an alternative. So here's what's included in this PR:

Adds a small "settings" button in the bottom right corner
Adds a  component to handle the new option

Preview
https://user-images.githubusercontent.com/812989/178157586-d99b36a9-24aa-4311-804f-13e3eb22bd5b.mp4

Note: I fully understand if this isn't the direction you want to take the project. Thanks for making a fun thing :). My kids and I are enjoying it!

No this works! I'd been wondering how to display settings without too much UI interference, I think this works. Thanks for the PR!


Uncaught ReferenceError: exports is not defined

I'm getting this error in validate-text.js at this point:
Object.defineProperty(exports, "__esModule", {
  value: true
});

Using webpack, it's not happening for me locally though (either with or without webpack-dev-server) only on our staging servers so currently trying to tie down the cause of the issue. But I did notice that you experienced something similar (https://github.com/sparksuite/w3c-css-validator/issues/130) recently with your demo site.

@corymharper it's a very web app but not using a framework like React the JS is compiled with webpack and babel. I still haven't figured out why it's working on one environment and not another (same node version, same babel config etc.).
I don't know enough about the different module formats, I did look at the suggestion of having the package support dual packages (ESM & CJS) and while I can get them to compile properly and the ESM one looks like it wouldn't throw the errors, when I import it into my project it still uses the CJS version.
I also looked at this https://stackoverflow.com/questions/43042889/typescript-referenceerror-exports-is-not-defined but couldn't find any help there.
So for now I've simply forked the repo and hackily compiled it without "module": "commonjs".


[AutoRelease] t2-resourcemover-2023-09-22-01515(can only be merged by SDK owner)

https://github.com/Azure/sdk-release-request/issues/4539
Live test success
https://dev.azure.com/azure-sdk/internal/_build?definitionId=1991

issue link:https://github.com/Azure/sdk-release-request/issues/4539

/check-enforcer override


[BUG] No shards indexed after 25th Feb 23:59:990

Describe the issue
A clear and concise description of what the issue is.
I have ran through the upgrade process recently to address the L4J version issue and all was running fine.  I could see data no problem, I updated ubuntu on Wed 23rd and the server was restarted on Friday 25th am.  All good so far, checked LME on the Following Wed (2nd March) and no data showing in the discovery section for last 15 mins.  I increased the time filter until it hit 25th Feb and could the last log was for 25th Feb @ 23:59:990.  I had a look at the shards and I can see the last of the indices was indeed 25th Feb.  However it seems WinLogBeats on the event forwarder is still sending logs to LME error free but i am not sure as to how to check the logs on the LME server.  Is this perhaps my not following the upgrade process correctly from 03 --> 04, the L4J upgrade fix  or something else?
To Reproduce
Steps to reproduce the behavior:

Go to 'Analytics / Discover'
Click on 'refresh'
Scroll down to '....'
See error - No results match your search criteria,  Expand your time range
Try searching over a longer period of time.
Expand this to 25th Feb and I can see data

Expected behavior
see any events for the last 15 mins
Screenshots
If applicable, add screenshots to help explain your problem.
Windows Event Collector (please complete the following information):

OS: Windows Server 2019
WEC Config V0.1
Winlogbeat Config  Unsure but is latest version in response to L4J.  Build hash = 1907c246c8b0d23ae4027699c44bf3fbef57f4a4
Winlogbeat.exe version [winlogbeat-7.13.4-windows-x86_64]
sysmon config [052754edd202e1380657c8d9d5d6ec49]
sysmon executable 13.10

Linux Server (please complete the following information):

Docker: [e.g. Docker version 18.09.3] UNSURE
Docker compose stack file version: [e.g. version 0.1] UNSURE
Linux: Ubuntu 20.04.4 LTS
Logstash Version [e.g. #LME logstash config V0.1] UNSURE

Additional context
Add any other context about the problem here.

Hey @edmitchellVS, if you were getting data in with no issues till this point it seems unlikely to be an issue with the v0.4 upgrade, and the minor updates shouldn't cause any compatibility issues I believe. It may be possible you've run out of disk space as discussed here, would you be able to check if this was the issue?
It would also be useful if you could post the logs (minus any sensitive information) from logstash/kibana/elastic using the following commands, which may help us to diagnose the problem:
sudo docker service logs lme_elasticsearch --tail 20 --timestamps
sudo docker service logs lme_kibana --tail 20 --timestamps
sudo docker service logs lme_logstash --tail 20 --timestamps

Thanks

Hi Adam,
Many thanks for this, I have ran the commad above and I can see where the error is.
:response=>{"index"=>{"_index"=>"winlogbeat-09.03.2022", "_type"=>"_doc", "_id"=>nil, "status"=>400, "error"=>{"type"=>"validation_exception", "reason"=>"Validation Failed: 1: this action would add [4] shards, but this cluster currently has [1000]/[1000] maximum normal shards open;"}}}}
I have changed the data retention to 180 days and this now seems to have fixed the issue...  May many many thanks for this!
Sorry I also forgot to mention another error message i was getting...
"4 of 708 shards failed
The data you are seeing might be incomplete or wrong."
This happens when going to the user investigator tab in the security dash board.  Do you think this will fix that or do I need to do something else?
Thanks again
Ed

Issue now completely resolved.  Thanks again for your help with this one 👍


🐛 BUG: D1 erroring on big sqlite dump import

What version of Wrangler are you using?
2.4.2
What operating system are you using?
Linux (archlinux)
Describe the Bug
While trying to import a very big sqlite dump (121098 lines) I get the following error:
$ wrangler d1 execute audio --file ./out.sq
🚧 'wrangler d1 <command>' is a beta command. Please report any issues to https://github.com/cloudflare/wrangler2/issues/new/choose
🌀 Mapping SQL input into an array of statements
🌀 Parsing 121092 statements
🌀 We are sending 13 batch(es) to D1 (limited to 10000 statements per batch)
⚠  Too much SQL to send at once, this execution will be sent as 13 batches.
ℹ  Each batch is sent individually and may leave your DB in an unexpected state if a later batch fails.
⚠  Make sure you have a recent backup. Ok to proceed? (y/n)
🌀 Let's go
🌀 Executing on table_name (fc09486d-3681-4906-a109-0b5e3d7737ab):
🚣 Executed 10000 commands in<PHONE_NUMBER>379763ms
...
🚣 Executed 10000 commands in<PHONE_NUMBER>718815ms
...
🚣 Executed 10000 commands in<PHONE_NUMBER>435894ms
...
✘ [ERROR] A request to the Cloudflare API (/accounts/285b637e867fade495c9dd74d250fa0b/d1/database/fc09486d-3681-4906-a109-0b5e3d7737ab/query)failed.

  Error 9000: exception caught in D1 core. Maximum number of keys modified in a transaction is 128.
  Error: Maximum number of keys modified in a transaction is 128.
      at Object.m [as putPage] (worker.js:2595:29)
      at put_page (worker.js:2438:15)
      at worker.js:2267:15
      at wasm://wasm/00f4590e:wasm-function[49]:0x863a
      at wasm://wasm/00f4590e:wasm-function[3209]:0x1d220e
      at wasm://wasm/00f4590e:wasm-function[3186]:0x1cd0d2
      at wasm://wasm/00f4590e:wasm-function[3189]:0x1cdb39
      at wasm://wasm/00f4590e:wasm-function[3242]:0x1d7673
      at wasm://wasm/00f4590e:wasm-function[3300]:0x1eadf0
      at wasm://wasm/00f4590e:wasm-function[3297]:0x1dd6c9 [code: 7500]

My sql file looks similar to the following:
CREATE TABLE table_name(
  entry1 TEXT NOT NULL,
  entry2 TEXT NOT NULL,
  entry3 INTEGER NOT NULL,
  entry4 TEXT,
  PRIMARY KEY (entry1, entry2)
);
INSERT INTO table_name VALUES('text','text',0,'');

With the INSERT INTO repeating until the end of the file

Duplicate of https://github.com/cloudflare/wrangler2/issues/2399

Closing as duplicate

Hey @MinmoTech,
We recently released a new D1 backend which fixes this issue, you can read more about it here: https://blog.cloudflare.com/d1-turning-it-up-to-11/


Automatically Add Alt Dataset When Requesting Alt Universe

Expected Behavior
When using alternative data universe the underlying symbol AND the alternative data should be added to the algorithm. Its a little counter intuitive to only add the equity prices
Actual Behavior
Only price data added when doing a universe subscription for alt data.
Potential Solution
Add the alt data for the symbol instead of forcing the user to do it in OnSecuritiesChanged()
Reproducing the Problem
# region imports
from AlgorithmImports import *
# endregion

class ChainedUniverseAlgorithm(QCAlgorithm):

    coarse = None
    universe_coarse = None
    universe_twitter = None

    def Initialize(self):
        self.SetCash(100000)
        self.SetStartDate(2023, 1, 2)
        self.universe_coarse = self.AddUniverse(self.CoarseFilterFunction)
        self.universe_twitter = self.AddUniverse(QuiverQuantTwitterFollowersUniverse, "QuiverQuantTwitterFollowersUniverse", Resolution.Daily, self.FollowerSelection)

    def CoarseFilterFunction(self, coarse: List[CoarseFundamental]) -> List[Symbol]:
        sorted_by_dollar_volume = sorted(coarse, key=lambda x: x.DollarVolume, reverse=True)
        self.coarse = [c.Symbol for c in sorted_by_dollar_volume[:100]]
        return Universe.Unchanged

    def FollowerSelection(self, alt_coarse: List[QuiverQuantTwitterFollowersUniverse]) -> List[Symbol]:
        self.followers = [d.Symbol for d in alt_coarse if d.Followers > 200000 and d.WeekPercentChange > 0]
        return list(set(self.coarse) & set(self.followers))

    def OnSecuritiesChanged(self, changes):
        for added in changes.AddedSecurities:          ### IDEALLY NOT REQUIRED.
            self.AddData(QuiverQuantTwitterFollowers, added.Symbol)

    def OnData(self, data):
        # Prices in the slice from the universe selection
        # Alternative data in slice from OnSecuritiesChanged Addition
        # for ticker,bar in data.Bars.items():
        #     pass
        for dataset_symbol, data_point in data.Get(QuiverQuantTwitterFollowers).items():
            self.Debug(f"{dataset_symbol} followers at {data.Time}: {data_point.Followers}")

System Information

Checklist

[x] I have completely filled out this template
[x] I have confirmed that this issue exists on the current master branch
[x] I have confirmed that this is not a duplicate issue by searching issues

[x] I have provided detailed steps to reproduce the issue

Review & test example algorithm:

returning both underlying & custom data symbol in the selection of FollowerSelection
using universe extensions chain operations to avoid keeping state on the algorithm and making the selection delay shorter


Initialize JAVA_MAJOR_VERSION variable if missing

Fix #92
I am not an experienced sh developer, so please carefully review this pr.
Tested with Java 7, 8, 11 ,13

I checked CirleCI error, it is related to this line on JVM 11: ParallelGC is not enabled on that version (but it works also on Java 13).

Thanks ! Not sure whether I'm able to review it this week (as I'm on the road), but please ping me early next week in case I should forget ;)

Ah, yes and it would be cool, if a bit of docs could be added to fish-pepper/run-java-sh/fp-files/readme.md could be added, too.

Thanks ! Fixed the test and merged your contrib in another PR.


Alpine: Add templates for Alpine Linux 3.15.0

https://www.alpinelinux.org/posts/Alpine-3.15.0-released.html

Change target version to 3.15.8
https://alpinelinux.org/posts/Alpine-3.14.10-3.15.8-3.16.5-released.html


FlightA while jumping on a slime

Description: FlightA false flag while jumping on a slime
Steps to reproduce the behavior:

Use any client (in the clip i used Badlion 1.8.9)
Jump on a piston with a slime block
Press the button and the player will jump
While jumping the false flags will show

Video: https://streamable.com/ao42k9

OS: Windows 11
Plugin Version: 4.0-RC-2
Server Version: Spigot 1.8.8
Client Version and Type: Badlion 1.8.9 (can be replicate with any client)

Fixed


Add support for password file

As a Ops
I want to generate gocd password file automatically
So that I can manage users for gocd using gocd_server.passwd_users list

merged in #3


apps sc & wc: fluentd & fluentd-elasticsearch upgrade

What this PR does / why we need it:
As we have upgraded our log discovery platform, we also need to upgrade our log engine to make it all work nice and dandy. To make fluentd-elasticsearch work we needed to compile our own image using fluentd-plugin-opensearch 1.0.4 (or 1.0.2) and change some of the values of fluentd as the core charts are made for ElasticSearch and not OpenSearch in the beginning. This will need a migration step as OpenSearch needs to be updated to handle customer fields in every cluster.
Which issue this PR fixes (use the format fixes #<issue number>(, fixes #<issue_number>, ...) to automatically close the issue when PR gets merged): fixes #806
Public facing documentation PR (if applicable)

Special notes for reviewer:
Add a screenshot or an example to illustrate the proposed solution:
Checklist:

[x] Added relevant notes to WIP-CHANGELOG.md
[x] Proper commit message prefix on all commits
[x] Updated the public facing documentation
Is this changeset backwards compatible for existing clusters? Applying:

[x] is completely transparent, will not impact the workload in any way.
[x] requires running a migration script.
[ ] will create noticeable cluster degradation.
E.g. logs or metrics are not being collected or Kubernetes API server
will not be responding while upgrading.
[ ] requires draining and/or replacing nodes.
[ ] will change any APIs.
E.g. removes or changes any CK8S config options or Kubernetes APIs.
[ ] will break the cluster.
I.e. full cluster migration is required.

Chart checklist (pick exactly one):

[ ] I upgraded no Chart.
[ ] I upgraded a Chart and determined that no migration steps are needed.
[x] I upgraded a Chart and added migration steps.

Pipeline config (if applicable)
If you change some config options (e.g. add/rename variable or change the default value) you may need to update the config used by the pipeline in pipeline/config.

Now it's done as far as this branch is concerned. https://github.com/monotek/fluentd-elasticsearch/pull/8 is waiting to get merged!


Run multiple plists under one formula

I'd like to run multiple commands when brew services start <formula>. Putting all commands under one  of the same plist works but not perfect.
Is it possible to add a new plist with different label name under that formula's directory, and then brew services start would launchd them all?

You can specify a plist path to brew services. The last discussion on adding multiple plists to Homebrew was in https://github.com/Homebrew/brew/issues/5691.

Adding "-c" to specify a custom plist doesn't work, because you cannot brew services start the same formula twice with different plists.
I didn't catch the result from the previous discussion. Was the answer a no for supportability?