Option - Scoreboard/Stats Improvements

Outstanding items to get done with the scoreboard and statistics outputs:

Better scoreboard layout overall, more compact info so we have more menu room
Better statistics output in general - Old stats script was fine but now that it's all in python let's make it better and more organized
Better disk capacity stats on scoreboard if there's multiple drives

Most of this was crushed out in v1.5.5


Small fixes for QuickStart shell script

http calls are changed to vault -format=json;
pause after creating port-forwarding (didn't work for me without it);
spaces after # :)

Thank you! 👍


Update bool-dsl.asciidoc

@ericamick thank you for all these awesome doc PRs! :+1:
One issue though - we don't manually edit the asciidoc files directly.  They are generated by our build process from their respective .doc.cs files.
Would you mind making these changes to the cs files and opening a single PR with all of your changes?

I've made the changes for this PR to the original C# files from which the docs have been generated. I've also added a multiline comment at the top of each generated asciidoc linking back to the file from which each is generated so that it is easier to make a change and submit a PR in future :smile:
Thanks for the doc PRs, @ericamick!


Feature/visual improvements

Fix external resources loaded from google
Add breadcrumbs to implementation views
Visual fixes for implementation views

Fixed everything except the safari only issue, as that is behaviour of the mat tabs component that I don't think we can influence.


testing: add -shuffle and -shuffleseed to shuffle tests

This is a revive of #10655
Motivation
Consider the following code & corresponding tests:
package pkg

// build and cache regexp, reuse between clients
var re *regexp.Regexp

type Client struct {
	// ...
}

func NewClient(pattern string) *Client {
	if re == nil {
		re = regexp.MustCompile(pattern)
	}
	return &Client{
		// ...
	}
}

func (c *Client) HasPattern(s string) error {
	if !re.MatchString(s) {
		return errors.New("meh, incorrect param")
	}
	return nil
}

package pkg

func TestFoo(t *testing.T) {
	s := NewClient("^foo.*")
	err := s.HasPattern("foo123")
	if err != nil {
		t.Errorf("expected to pass")
	}
}

func TestFooBar(t *testing.T) {
	s := NewClient("^foobar.*")
	err := s.HasPattern("foobar1123")
	if err != nil {
		t.Errorf("expected to pass")
	}
}

Those tests pass, everything looks fine, but they're order dependent. Running them in another order will fail.
To prevent such hidden and hard to debug mistakes we need to make the order of test random for each test build.
Current workarounds

Manual ordering of tests.
Boilerplate code to specify the order of tests.
For table-driven tests we can use a map instead of slice, ex:

func TestSomething(t *testing.T) {
	testCases := map[name]struct{
		a,b int64
		res int64
	}{
		“simple case”: {1, 2, 3},
		“less simple”: {3, 3, 23},
	}

	// due to behaviour of map test cases will be
	// in a different order for each run
	// but this solution is limited and not suitable for test funcs
	// aka `func TestXXX(t *testing.T)`
	for name, tc := range testCases {
		t.Logf(“test: %s”, name)

		res := foo(tc.a, tc.b)
		if res != tc.res {
			t.Errorf(“want %v, got %v, res, tc.res)
		}
	}
}

Possible solution
We need to specify a test run to execute tests with a random/desired order:

-shuffle to run tests with a random order (used random seed may or should be printed to output depending or not on a -v flag).
-seed <int> to specify a user-defined seed to have an ability repeat a failed build.

Open questions

Should we randomize order of benchmarks and examples? (looks like not)
This makes test runs 'flaky' but this helps to reveal possible implementation caveats.
This might not happen for 1.12 'cause proposal is submitted too late.

PS. if/when it will be accepted - will be happy to work on it.

Interesting problem - reminds me of go test -race a bit. I'm a bit worried that every repository will now be expected to run three test commands on its CI; go test; go test -race; go test -shuffle.
On the other hand, making go test randomize the order could make its output non-deterministic.
I wonder if this is something we could enable when one runs go test ./.... That is, since a package's test output and results are printed all at once, we could run the tests in random order and then sort the results before printing them. That would be ideal in my opinion, since every existing user would benefit and we wouldn't need an extra flag.
That suggestion wouldn't apply to go test or go test -v, since those do need to run the tests in order - the results are printed as they happen.

That is, since a package's test output and results are printed all at once

Might be a problem with https://github.com/golang/go/issues/24929 😉

and then sort the results before printing them

But how we can know an order that triggered a test run failure? Sort only success run?

Might be a problem with #24929

Oh, I thought that proposal would affect go test -v, not go test -v ./.... If it affects both, then you're right.

But how we can know an order that triggered a test run failure? Sort only success run?

Potentially. Or one could take the usual approach like with any other test flake - run the tests over and over again with -count or stress until we find the failure again or we're convinced that it's fixed.

More command-line flags seems problematic.
What if instead we added a method on testing.M so that TestMain could call m.Shuffle(time.Now().UnixNano()) in tests that wanted to opt in to randomized execution?
Those tests could also define their own seed flags instead of having to add one to all tests.

Retitled per suggestion above.

Seems like we'd like to do this, but we're blocked on an API definition. Is that correct?

@andybons looks so

The use case that interests me from this proposed API: the ease of partitioning a single test package, that contains many individual tests, that each take a long time to run. For example, if my codebase has one particular test package that takes several minutes when run with -race -count=1, I could have 4 different CI jobs in parallel that each run 1/4 of the tests in the bottlenecked package.
Without an API like this proposal, I would have to run go test -list=. to discover the top-level tests, and then find an appropriate set of regexes to pass to each invocation of go test -run=... such that the top-level tests are split roughly evenly.

The original problem identified was reordering tests to shake out unwanted dependencies between test functions. We expanded to being able to set up the order of repetitions as well. Those still seem worth doing.
Sharding is possible for top-level tests but more difficult once subtests are involved (subtests basically can't get sharded because you don't know until you enter the outer test that they exist, and the outer test might have done expensive setup that you don't want to repeat on each shard).
All those still seem like enough reason to do this. So what would the API look like?
Currently testing.M says
type M struct {
	// Has unexported fields.
}
    M is a type passed to a TestMain function to run the actual tests.

func (m *M) Run() int

The idea I think would be to add exported slice fields Tests and Benchmarks and maybe also a convenience method Shuffle. It is unclear what the types of those slice elements are. There are also examples. Right now we have:
$ go doc testing.InternalTest
package testing // import "testing"

type InternalTest struct {
	Name string
	F    func(*T)
}
    An internal type but exported because it is cross-package; part of the
    implementation of the "go test" command.

$ go doc testing.InternalExample
package testing // import "testing"

type InternalExample struct {
	Name      string
	F         func()
	Output    string
	Unordered bool
}

$ go doc testing.InternalBenchmark
package testing // import "testing"

type InternalBenchmark struct {
	Name string
	F    func(b *B)
}
    An internal type but exported because it is cross-package; part of the
    implementation of the "go test" command.

$

Should we de-internalize these (we can type alias InternalBenchmark = Benchmark for compatibility) and then use them?
The idea is that you'd reorder however you like and then call Run.
Or maybe we could make the lists be []Test where you can only find out the name?
type Test interface {
    Name() string
}

That would hide F, which may be preferable. (Calling one of these F's is non-trivial and perhaps impossible depending on what it needs.)
Or should we just shuffle by default and not add any new API? That approach would require a new flag for -seed still, and it would not solve the benchmark iteration issue.

My previous comment asked three questions and no one has suggested any answers.
Do people care enough about this suggestion that we should continue with it?
Or is it just not that important / would not have enough widespread use?

As a user in need of randomized order of tests, I do care about having the feature, though I have no preferences about the interface — any of the options above would allow me to achieve the result: shuffle the tests, and rerun them in the same order later if needed.

It sounds like the generality we got to is overkill - no one seems to want it.
The original proposal was to add -shuffle and -seed. It would probably be good to make the latter -shuffleseed (default a random seed) so that they appear next to each other in the help output.
Changing the title back to focus on those flags.
Any thoughts, @mpvl, @robpike, @aclements?

How about just one flag that handles a default value? -shuffle=seed. If seed is 0 (say), it means be random.

Or, rather than a special value to indicate a random seed, -shuffle=random or -shuffle=N? I think people are likely to use a seed of 0 intending to get a deterministic (but shuffled) run.

Or just -shuffle and -shuffle=N?

@josharian I think that means you couldn't write -shuffle N, which would be inconsistent with the other flags. (And generally, it seems better to stick to the flag package's convention where a flag is either boolean or it's not.)

The -shuffle N problem is especially bad here, since nearly all tests don't check for extra command-line arguments, so the N would become a non-flag argument and the test would ignore it entirely, silently.
There need to be three different settings here:

By default, no shuffling.
With an easy flag, shuffle with a new random seed each time.
With more work, shuffle with a specific seed.

Using one flag is tough to get all three of those. I suppose you could have -shuffle=N where =0 (default) means no shuffle, =1 means a random seed, and =othernumber means that's the seed.
Another options is =-1 (default) means no shuffle, =0 means random seed, and =othernumber means that's the seed. But -shuffle=0 looks a lot like -shuffle=false.
Or maybe a string: -shuffle=off (default) means no shuffle, -shuffle=on means random seed, and =N means that's the seed.
That last one, the string, seems like the nicest one of the three. Thoughts?

I definitely prefer the string-based option, since it avoids bestowing special meaning to a few integer values.

Agreed with the string-based option.
When using -shuffle=on, will the randomly selected seed be printed in the event of a test failure?
The original proposal said:

(used random seed may or should be printed to output depending or not on a -v flag).

But it seems important that a user is able to reproduce a failure with a known -shuffle=N, after triggering a failure using -shuffle=on.
Assuming the shuffle seed is printed in some circumstances, I'm not sure how that affects test2json output. Is it a new Action?

No final comments, so accepted.

I would like to work on it.

@cristaloleg all yours, please go ahead and sorry if I might sound like am putting pressure on you, but the Go development tree will close down at the end of April, so please let us know if you don't have time to work on it. Thank you!

Punting this to Go1.17 as we didn’t get any action during Go1.16 development. @cuonglm here is something we could tack onto our plate for Go1.17 if you are interested.

@cristaloleg are you still picking this up?

@strideynet for the 1.17 looks possible. Will try to make early March.

Perfect, if you are unsure about it I am more than willing to take this ticket up @cristaloleg

@strideynet feel free to pick it up, I'm out of time and motivation. Sorry for a late ping.

@strideynet I could also take a stab if you're busy; let me know what you think! I'll wait for a few days and hunt for some more information in the meantime.

@tpaschalis I'm just undergoing a change in employment so it'll be a while until I'm freed up, so it's all yours

@strideynet I wish you the best of luck mate, hope you land a great offer! I've already got a POC which seems to work; I'll iron it out and send it for review this week.


Make StorageExplorer.exe file version match product version

Not sure if thats the right place or if its too much to ask but would be very nice to have the storage explorer executable (StorageExplorer.exe) file version to match the product version.  Or at least make that information available at https://api.github.com/repos/microsoft/AzureStorageExplorer/releases/latest/
It would make life a lot easier when packaging the software for enterprise deployment (for detection pursposes).
Thanks

@schenardie what do you mean by the "file version"? Do you mean having the version in the file name, or do you mean like the file properties? Also, are you asking for this to be on the installer or the executable that ends up in your program files directory?

hey @MRayermannMSFT, i'm talking about the file properties of the executable (StorageExplorer.exe).
The file currently has Product Version (1.13.1) and File version (154<IP_ADDRESS>).
Management systems like SCCM and Intune are based on file version for detection. Currently i cant tell what the next version will be, so it makes hard to automate this packaging.
Most of MS tools like VSCode have the same value for both.  If that is not doable, maybe putting a property on the intune api per release informing the version would suffice (so we can probe that information).  Thanks

Doesn't look like electron-packager lets us define that property explicitly. It's always filled in by the build version. The weird thing is the build version appears to be wrong; I don't know where it's getting that number from. As far as solutions go, we may need to use rcedit ourselves.

Moving this due to changes in dev resources for 1.19


Merge Intervals Algorithm in C++

I want to add a Merge intervals algorithm and for this, I would like to code the solution for this problem in C++ language.
Problem Description: Given an array of intervals where intervals[i] = [starti, endi], merge all overlapping intervals, and return an array of the non-overlapping intervals that cover all the intervals in the input.
Input: intervals = [[1,3],[2,6],[8,10],[15,18]]
Output: [[1,6],[8,10],[15,18]]
@Kumar-laxmi sir please assign me this issue.

Do you mean Merge Overlapping Intervals Algorithm & under what category this algorithm comes

Do you mean Merge Overlapping Intervals Algorithm & under what category this algorithm comes

This kind of questions generally fall under the greedy algorithm, and yeah merge overlapping intervals algorithm and merge intervals algorithm is the same.

@atul1510 Please specify the language you would like to work on

@atul1510 Please specify the language you would like to work on

@atul1510 Please specify the language you would like to work on

I will like to work in C++ Language.

@Kumar-laxmi @zugzwang03 assign me this issue.

@atul1510 Could you implement this algorithm in all four languages

Assigned!
@atul1510 : C, C++, Java, Python


(PUP-8502) Comment out lookup tests making faulty asssumptions about ENC

CLA signed by all contributors.

Superseeded by 6715


Projects not showing in Projects dropdown on extension

OS version: Windows 10
Browser version: 93.0.4577.82
Extension version: 1. I 70.4

Relevant integration (if any):
N/A
🐛 Describe the bug
The Projects dropdown is not showing projects. It says No Projects even though projects exist.
Expected behaviour
Projects should show.
Steps to reproduce

Steps to reproduce the behaviour:

Go to ...
...

Other details or context
Case
Slack

Merged with #2004


ObjectStore multiple_append Test is Flaky

Describe the bug

I have seen this test fail a couple of times in CI lately, most recently
https://github.com/apache/arrow-rs/actions/runs/6324042685/job/17172783580
This test was added in #3824 by @metesynnada
To Reproduce

Expected behavior

Additional context

label_issue.py automatically added labels {'object-store'} from #4869


Update Traffic Portal v2 builder and CI to NodeJS 18

#8005

Adds a new builder for Traffic Portal v2 to the Docker Hub (created in INFRA-25760), apache/traffic_portal_v2_builder
Updates GitHub Actions for TPv2 to use NodeJS 18

Which Traffic Control components are affected by this PR?

Build system
Automation - GHAs

What is the best way to verify this PR?

Verify that tests pass
PR submission checklist

[x] This PR has tests
[ ] This PR has documentation
[ ] This PR has a CHANGELOG.md entry
[x] This PR DOES NOT FIX A SERIOUS SECURITY VULNERABILITY (see the Apache Software Foundation's security guidelines for details)

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 74.17%. Comparing base (ef3fc6a) to head (a47d2f1).
Report is 16 commits behind head on master.

Additional details and impacted files
@@            Coverage Diff             @@
##           master    #8005      +/-   ##
==========================================
- Coverage   74.36%   74.17%   -0.20%
==========================================
  Files         121      121
  Lines        5548     5642      +94
  Branches      908      922      +14
==========================================
+ Hits         4126     4185      +59
- Misses       1351     1383      +32
- Partials       71       74       +3

Flag
Coverage Δ

traffic_portal_v2
74.17% <ø> (-0.20%)
:arrow_down:

unit_tests
74.17% <ø> (-0.20%)
:arrow_down:

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

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


wslu: 3.2.4 -> 4.0.0

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/wslutilities/wslu/releases.
meta.description for wslu is: "A collection of utilities for Windows 10 Linux Subsystems"
meta.homepage for wslu is: "https://github.com/wslutilities/wslu"
meta.changelog for wslu is: ""
Updates performed

Version update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 4.0.0 with grep in /nix/store/5p85qn7f73zvm3ng26s6hrnf0gd5rh1s-wslu-4.0.0
found 4.0.0 in filename of file in /nix/store/5p85qn7f73zvm3ng26s6hrnf0gd5rh1s-wslu-4.0.0

Rebuild report (if merged into master) (click to expand)

1 total rebuild path(s)

1 package rebuild(s)

First fifty rebuilds by attrpath
wslu

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/5p85qn7f73zvm3ng26s6hrnf0gd5rh1s-wslu-4.0.0 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A wslu https://github.com/r-ryantm/nixpkgs/archive/ae9628b3cdfd711cb77351ddbe1bda98bd7a7a11.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/5p85qn7f73zvm3ng26s6hrnf0gd5rh1s-wslu-4.0.0
ls -la /nix/store/5p85qn7f73zvm3ng26s6hrnf0gd5rh1s-wslu-4.0.0/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

wslu

Maintainer pings
cc @JamieMagee for testing.

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

1 package built:

wslu


Persist on load is now depreciated - and calling DontDestroyOnLoad causes errors.

Environment

Source of VRTK (Github)
Version of VRTK (Github release chore(Version): bump to version 3.2.0)
Version of Unity3D (Unity 2017.3.0f3)
Hardware used (Vive)
SDK used (SteamVR)

Steps to reproduce
Select "persist on load" checkbox of [VRTK_SDKManager] manager component. Or call DontDestroyOnLoad on the manager object.
Expected behavior
The gameobject [VRTK_SDKManager] should persist on load.
Current behavior
I require the use of "persist on load" option in my project, or the ability to call DontDestroyOnLoad to presist the [VRTK_SDKManager] object and manager component. But with the latest updates it's now depreciated.
How should I persist the [VRTK_SDKManager] gameobject through scene changes?
[edit]
I have now set the parent of [VRTK_SDKManager] to an object that has already been set to DontDestroyOnLoad just prior to a scene change, and I believe that worked ok.

DontDestroyOnLoad is evil. For more information read #1316.
Unity introduced additive scene loading as a replacement, use that instead.


No Folder Opened Translation is lost.

Reproduction steps:

Open https://insiders.vscode.dev/
Switch zh-cn or any other language except English.
Focus explorer tree view title

Version: 1.86.0-insider
Commit: fb769554405bee9be16e21ceb0a496bd29126941
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/<IP_ADDRESS> Safari/537.36
Embedder: vscode.dev

I think @mjbvz fixed this in https://github.com/microsoft/vscode/pull/203851
if (localizeCalls.length === 0) {

into
if (localizeCalls.length === 0 && localize2Calls.length === 0) {

I do see it being exported now so this should be fixed within the month as this string goes through the localization pipeline.

The translation is not in yet. Should we move this to March?

Yes I don't think we got a language pack release last month due to some pipeline issues so we should see the fix next month.


[asking some question about new release code]

Hi David:
I follow your new release code and then got something confused. can you share the reference? many thanks for your helping.
Q1: why do you use norm loss instead center loss ?
Q2: why img use fixed standardization --> img - 127.5 / 128.0, 127.5 is mean value? 128.0 is stddev?  tf.image.per_image_standardization is not better than fixed std?
BR,
Joseph

hello @akimo12345
about Q1,i think david add center loss also,there are using norm loss and center loss.
and i have same question about Q2.

Hi, billtiger
thanks for your reply. Both of two factor(center_loss_factor, prelogits_norm_loss_factor) are set to zero on vggface dataset training command, so that I think loss function only has softmax_cross_entropy, not included one of them.

Q1: maybe they made some experiments on center loss. however, the results were not satisfying.
Q2: the standardization is stretching the RGB values from [0, 255] to [-1, 1]. just a linear transformation.


Performance issue across Different PCs

CARLA version: 0.9.15
Platform/OS: Ubuntu 20.04
When running CARLA's manual_control.py on three different PCs, there's a significant performance difference observed.
CPU: 5600x
Motherboard: Gigabyte B450M
RAM: 32GB
Graphics Card: RTX 4060ti
CPU: i9-13900
Motherboard: MSI MAG B760M
RAM: 64GB
Graphics Card: RTX 3080ti
CPU: i9-10900xe
Motherboard: WS X299 SAGE/10G
RAM: 128GB
Graphics Card: RTX 3090
While the first and second PCs show very good performance with server FPS ranging from 100 to 120 FPS when executing manual_control.py, the third PC comparatively shows much poorer performance, with FPS ranging from 40 to 60.
I'm curious about the reasons for this performance discrepancy.

Hi,
We suspect that the difference of FPS is due hardware specifications of each machine.
Anyway, would be useful for us if you could share profiling to dive deep more in your case. I share you the documentation about how to profile:
https://docs.unrealengine.com/4.27/en-US/TestingAndOptimization/PerformanceAndProfiling/
Best Regards

Hi,
Also, if you're running this on the UE editor directly make sure to uncheck the "Use less CPU while in background" option.
Marcel


Enable TLS for the website

https://blog.github.com/2018-05-01-github-pages-custom-domains-https/

Thanks for reporting. This is a duplicate of stan-dev/stan-dev.github.io#32 (different repo). I'll close this and we can pick it up there.


[mergeVolumes] add sequenceDuration management-medInria

Based on https://github.com/Inria-Asclepios/medInria-public/pull/247 (will be rebased after merge) [edit:rebased]
From this issue https://github.com/Inria-Asclepios/music/issues/496
This PR handles the sequence duration parameter value from the temporal fuse (datasets) method.
:m:

Addition, cf. https://github.com/Inria-Asclepios/music/pull/497

This PR has been rebased

@fcollot this PR is needed by @paulinemig

(if it's possible to look at it. And this is an old PR)

I'll try and look at it this afternoon.

GetMaxTime should return, as its comment says, the "maximal time flag of the sequence" (which it did before), not the sequence duration. The function was not bugged, but misused in parts of the code that should actually be calling ComputeSequenceDuration. Changing the nature of GetMaxTime breaks the code that used the function properly (such as ComputeSequenceDuration)

The functions extractMetaData, extractMetaDataFromFieldData, addMetaDataAsFieldData and clearMetaDataFieldData are all directly copied from the non-4D reader and writer for VTK. This sort of duplication should be avoided and could be solved by creating a vtkDataMeshReaderBase and a vtkDataMeshWriterBase class containing those functions.

No so much functions were redundant, but i added anyway these files @fcollot .
@mjuhoor this could change your code also. Cf vtkDataMeshReaderBase and vtkDataMeshWriterBase.


Automatically activate when new function is entered

Can this plugin auto-insert the phpdoc tags when a new function is created and the "{" key is entered ?
Basically, you'd enter the function signature like so:
function addTwoNumbers(int $a, int $b) {
(pressing enter would insert the phpdoc).

In Netbeans, as soon as you're finished typing the method signature, it starts to auto-generate the docblock and auto-inserts it upon hitting "Enter" after one (or possibly the second) paren. With this extension (at least on a MBP) I need to:
1). Highlight the method sig
2) Hit Fn + F1


JupyterLab user testing script and results

Please do not merge this PR. It exists for easy and public review, but I do not want to interfere with the testing environment. I am open to where this might better live while still being related to this repository.

Finally, here are the full results from the JupyterLab accessibility user testing done with the testing environment in this repository. It's time for review.
This PR adds:

A results directory to keep the files grouped
user-testing-results.md, the full length document discussing testing results
user-testing-script.md, an empty version of the testing script used throughout these sessions
testing-environment-info.txt with the list of packages in the testing environment.

Things that might be helpful for review include:

Catching any typos, extra spaces, the usual culprits.
Coherency. Are there any sections that confuse you? Are there any sections that would benefit from different explanation or a link to another resource?
Verbosity. This document could likely afford to be cut further, but I am too close to it to know what to cut any longer.
Please feel free to only review part of this PR if that works best for you.

Please let me know if you have any further questions, and thanks for the review! 🌻 cc: @trallard @steff456 and @gabalafou since your names are on the results!

Please do not merge this PR. It exists for easy and public review, but I want to maintain the testing environment. I am open to where this might better live while still being related to this repository.

I remember us discussing this a while back. I would be +1 on merging and keeping both the environment + testing scripts in a single repository. I have held up making a tag/release for the repo until we resolve this, but we can make a release anytime.
If any of @gabalafou or @isabela-pf have particular hesitations about having all the testing resources together (env + scripts) let me know, and we can find a better place. But otherwise, I think having all these together would help with guidance on structuring these testing sessions.

I see no issue with putting the results in a new results folder in this repo

Responding to the above comment about merging.

I remember us discussing this a while back. I would be +1 on merging and keeping both the environment + testing scripts in a single repository. I have held up making a tag/release for the repo until we resolve this, but we can make a release anytime.

If any of @gabalafou or @isabela-pf have particular hesitations about having all the testing resources together (env + scripts) let me know, and we can find a better place. But otherwise, I think having all these together would help with guidance on structuring these testing sessions.

I do remember this discussion, and I had thought the decision was to, at minimum, create a release for this repo to clearly preserve the testing state as it was during these tests. And then merge post release so that we have a clearly denoted point for where we tested from. Maybe I'm being too stubborn about this, but I am interested in to obscuring what was used to host JupyterLab so that

We could use the environment again easily if desired.
Others can review the set up and reference the results to support their understanding or try and reproduce and issues.
Others have an example of what's been done if they are also trying to run a user testing environment.

I won't push on this again, but I hope having it written here clarifies why I wrote the initial comment.

There is a release for the repository now, but that means that the results/testing-environment-info.txt need removing from this PR as this is part of the current release (it is needed to reproduce the environment)


Adds the ability to capture opaque CGImages from GPUImageFilters

GPUImage is a fantastic library, thanks for all the hard work!
I frequently use GPUImage to create images for use in a UITableView or UICollectionView (creating thumbnails, adding a drop shadow, etc...).
One way to achieve smooth scrolling with a UITableView is to ensure that every image in the table is fully opaque, with no alpha channel. A quick google for "UITableView performance" yields plenty of pages that describe why opaque images are important.
I often find myself writing code that does the following:
Source UIImage
    |
    +-> GPUImageFilter
        |
        +-> Output UIImage
            |
            +-> CoreGraphics removeAlpha()
                |
                +-> Opaque UIImage

using a UIImage extension like this:
extension UIImage {
    func removeAlpha() -> UIImage {
        UIGraphicsBeginImageContextWithOptions(size, true, scale)
        self.drawInRect(CGRectMake(0, 0, size.width, size.height))
        let image = UIGraphicsGetImageFromCurrentImageContext()
        UIGraphicsEndImageContext()
        return image
    }
}

Which is just crazy, because I'm needlessly using the CPU to create a copy of an image that I just created on the GPU. It would be nice if I could just ask GPUImage to make the UIImage opaque when it's initially created.
This pull request adds a boolean flag shouldCaptureOpaqueImage to GPUImageOutput and GPUImageFrameBuffer to enable this behavior.
Thanks again for creating GPUImage!

FYI, it looks like there are some dependency problems with Travis-CI. I think the github people dealt with a similar issue here: https://github.com/github/pages-gem/issues/181


setLastRenderedPoint needs some association with PointerEvent

Most likely by taking a pointer id.

Sounds like you have some idea of how this can be addressed :)

This was addressed by #170


Fix: Chrome Driver Net::ReadTimeout when running system specs on CI/CD server

What Happened
System specs that uses Chrome Driver sometimes fail randomly with the error Net::ReadTimeout. The issue is related to low memory allocation for the Docker container.
Insight

Tried to mount the dev/shm volume but the issue still happened: https://github.com/elgalu/docker-selenium/issues/20#issuecomment-133011186
Requires to increase the size of the dev/shm volume: https://github.com/SeleniumHQ/docker-selenium/issues/198
Requires to upgrade to Docker Compse 3.5: https://docs.docker.com/compose/compose-file/#shm_size. Keeping the Docker Composer versions for dev and production to 3 to have more support on local and host machines and a newer version is not required.

Supplanted by #53


Aggregator freezing with gramine-sgx for torch_cnn_histology_gramine_ready

User in slack channel reported issue related to aggregator freezing when using gramine-sgx. Closure of this task involves:

Reproducing behavior
If confirmed issue, implement fix
If not reproduced, work with user to resolve their problem

Slack Message

This workspace has been removed as part of a broader refactoring of graminization for OpenFL.


add retention to upload

If this is unset, it falls back to the repo default.
I don't have the power to change that.
Workiva policy is 7 days for non-release artifacts, and 30 for release. Set to 7.

Security Insights
No security relevant content was detected by automated scans.
Action Items

Review PR for security impact; comment "security review required" if needed or unsure
Verify aviary.yaml coverage of security relevant code

Questions or Comments? Reach out on Slack: #support-infosec.

@Workiva/release-management-p


Adds a testPlugins

Is your feature request related to a problem? Please describe.
Often during development, the tests requires some plugin to make the test runnable.
I would like to limit the actual dependencies (as in compile time dependencies). So I would like to be able to express these runtime dependencies in different scope.
Describe the solution you'd like
At this time the plugins are declared in the intellij extension, so this would like :
intellij {
   // ...

   plugins.set(
       "org.intellij.plugins.markdown",
   )
   testPlugins.set(
       "org.intellij.plugins.markdown",
       "com.intellij.java",
   )
}

Note the testPlugins in this proposition do not inherit the plugins list, so that custom configurations could be used with or without plugins. That said I wonder if this is the right approach.
Describe alternatives you've considered
At this time, the code has to declare plugins in the compile scope even if those are only used for tests, e.g.:
intellij {
    type.set("IC")
    plugins.set(
        listOf(
            "Git4Idea",
            "com.intellij.java" // for tests
            "org.intellij.plugins.markdown",
        )
    )
}

Additional context
Somewhat related but out of scope, I believe plugins should be declared as dependencies with their configurations in order to rely on the Gradle semantics, e.g.
dependencies {
    // regular dependencies
    implementation(...)
    testImplementation(...)

    // plugins
    plugin(...)
    testPlugin(...)
}

related #336, #115

Starting with 2.0 release, it is now possible to register new test/run tasks with customized IntelliJ Platform and plugins set:
val customRunIde by intellijPlatformTesting.runIde.registering {
    type = IntelliJPlatformType.Rider
    version = "2024.2"

    plugins {
        plugin("pluginId:version")
        plugin(pluginId, version, channel)
        disablePlugins(bundledPlugiId)
    }
}

val customTest by intellijPlatformTesting.testIde.registering {
    ...
}


Add code owners config

@YanVugenfirer
Please check these errors:
    Unknown owner on line 8: make sure @viktor-prutyanov exists and has write access to the repository

    /fwcfg64/           @viktor-prutyanov @YanVugenfirer

    Unknown owner on line 13: make sure @viktor-prutyanov exists and has write access to the repository

    /pvpanic/           @viktor-prutyanov @YanVugenfirer

    Unknown owner on line 15: make sure @kostyanf14 exists and has write access to the repository

    /Tools/             @kostyanf14 @YanVugenfirer

    Unknown owner on line 17: make sure @viktor-prutyanov exists and has write access to the repository

    /viofs/             @viktor-prutyanov @YanVugenfirer

    Unknown owner on line 23: make sure @irudakov77 exists and has write access to the repository

    /viosock/           @irudakov77 @YanVugenfirer

From docs (https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-code-owners#codeowners-syntax)
The pattern is followed by one or more GitHub usernames or team names using the standard @username or @org/team-name format. Users must have read access to the repository and teams must have explicit write access, even if the team's members already have access.

From docs (https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-code-owners#codeowners-syntax)
The pattern is followed by one or more GitHub usernames or team names using the standard @username or @org/team-name format. Users must have read access to the repository and teams must have explicit write access, even if the team's members already have access.

Strange that code owners need write and not "Triage" rights. But in any case, I added the permissions to Viktor and you, I cannot add Ilya, because permissions are too wide.

@YanVugenfirer Let's merge PR and try to create PR to viosock to check


Implement heap size support on Windows

We can success to compile this on Windows by #40, but it has not implemented to measure on Windows yet.

https://msdn.microsoft.com/en-us/library/windows/desktop/aa366706(v=vs.85).aspx

That can be closed.

By #45 ?

Yes.


Bump promo-tools to v4.0.5

What type of PR is this?
/kind feature
What this PR does / why we need it:
Bump promo-tools to v4.0.5
Which issue(s) this PR fixes:
xref https://github.com/kubernetes-sigs/promo-tools/issues/1197
Does this PR introduce a user-facing change?
NONE

cc @kubernetes-sigs/release-engineering

/lgtm


Automatically deploy dist to dist branch

Every commit in public-api (it could be changed) generates automatically the distribution files and @Cartofante commits the changes to the dist branch.
Dist branch: https://github.com/CartoDB/cartodb.js/tree/dist.
CDN: https://cdn.rawgit.com/CartoDB/cartodb.js/dist/public/carto.js

I think we can use this now. I would leave the versions for the public (next) release


Add @angular-devkit/build-karma

Supersedes https://github.com/angular/devkit/pull/965

Blocking for now.

@filipesilva what's it blocked on?

@alexeagle last I spoke with @hansl about this package he preferred to not publish more architect builders until the API stabilized.

Closing this as it's been moved.


Display release & track popularity

Would be nice to have some idea of how many people have purchased a release & tracks within a release.
This could potentially just be sorting releases and tracks by most purchased, but additionally / alternatively some sort of colored heat map or something would be pretty useful. If I discover a new label with a ton of releases to go through or a big compilation album, having some way to narrow in on the most liked first would be great.
From the discography page it would be great if both release purchases and individual track purchases were somehow counted towards each release's tally, even if differently.
Popular does not always equal good and it's possible some gems could be missed this way, but it could also help reduce some of the overwhelm of sorting through a ton of tracks/releases.

This should be doable with the BC API endpoints I've found. Specifically there is an endpoint to get the discography of a label and then an endpoint to check an album/tracks ownership. My only concern is that Bandcamp's rate limiting is... a black box. And so for a label with a lot of releases the process of getting this data could be very slow.
I've hit the rate limit previously when trying to build something else. It doesn't last long but it does stop you from even being able to load the bandcamp website.
Perhaps a highly regulated API client could work and then whenever you go to a label's page it would load up all the releases in a queue and get the data at a reasonable rate...
I will need to think about this a bit


Using Set-DnsServerResourceRecord removes timestamp from changed dnsrecord.

Prerequisites

[X] Write a descriptive title.
[X] Make sure you are able to repro it on the latest released version
[X] Search the existing issues.
[X] Refer to the FAQ.
[X] Refer to Differences between Windows PowerShell 5.1 and PowerShell.

Steps to reproduce
Hello!
When I used Set-DnsServerResourceRecord to edit TTL on my records it also removed the timestamp from dynamic records making them static.
Looking at the New ciminstance record it includes the timestamp but it is lost when running Set-DnsServerResourceRecord.
A question do anyone know how to add timestamp to existing records with powershell so I can readd lost timestamps? only know how to add timestamps to all records...

PSRemotingProtocolVersion      2.3
SerializationVersion           <IP_ADDRESS>
WSManStackVersion              3.0

Visuals
No response

This cmdlet is part of Windows Server (specifically the DNS Server role) and needs to be reported via Windows Feedback as it's not serviced by this repo


OpenAPI 3.0

Any chance that this will be updated to support OpenAPI 3.0?  This new version of the Swagger specification was released in July 2017.

I won't have time. But PRs are welcome.


Entity ID

Can you provide entity linking ID in WikiData for every entity? Entity ID is necessary for inter-document information aggregation. Thank you!

We don't do entity linking. We link nouns to all the entities that have the same name to discover relations and then annotate the relation. So a noun can be linked to several entities.

I got it. Thank you!


Allow Slayer missiles to go out of bounds for exploration

No exploding when going out of bounds, allows for more exploration, such as the intro sequence area in the first level (just launch a rocket when facing the dD logo and head towards the black void)
https://github.com/fgsfdsfgs/perfect_dark/assets/1617767/cd8240e3-f320-4787-96f4-fbbce06faaeb
Works especially well with the change to add Slayer to the "All Guns" cheat: https://github.com/fgsfdsfgs/perfect_dark/pull/442 which is what the first commit contains
This allows for exploration of all levels.
This is draft because I just want to gauge interest in this change. If other folks would like this, maybe it should either be a cheat or a setting since the default behavior of the games makes sense from a gameplay standpoint and should remain. If not, I'm happy to close this PR as well. What would be close IMO would be to make rockets not explode when they collide with a wall either, basically never explode unless pressing the Z button. If there's interested, I can look into that.

Sorry, but I'd only accept this as a cheat, and even then I'm pretty sure that if you manage to fly outside of any room you could crash the game under certain conditions. That's one of the reasons there's no noclip.

Hm I'm thinking, now with the 2 hand wield that also causes weirdness if it would make sense to have a sort of "Cheat" option inside the Extended menu for things that are fun but can break the game. Basically to make it clear that those options were not in the original game and that you only use them at your own risk so anyone new to this wouldn't accidentally enable them without realizing that. I'm thinking adding Slayer to solo missions would fall in that category as well. Or ability to set up more than 1 sentry guns. I guess they're basically small mods.


lalonde example notebook fails automated tests due to R dependency

The lalonde example notebook uses the R Matching library to load the lalonde dataset.  That is the only functionality it is providing to the notebook.
I recommend we remove the R dependency and load the lalonde dataset through python alone.
notebook link: https://github.com/py-why/dowhy/blob/main/docs/source/example_notebooks/dowhy_lalonde_example.ipynb
failed build: https://github.com/py-why/dowhy/actions/runs/3147834064/jobs/5117731254

This was fixed by https://github.com/py-why/dowhy/pull/697. Closing.


Too slow to run in precommit hook

Hi, is there a way to set up detekt gradle task to run on only staged git files?
I did try my hand at it, subclassing the detekt task. However I couldn't re-use the settings in the subclassed detekt task (IIRC they are configured outside of the task itself) and there may have been some caching issues.
Similar issue #1057, do you strongly recommend SonarQube? This is for my workplace so it would be much higher scope to add that to CI, ideally we would get a quick check locally...

Hi @srcreigh
Yeah the answer is pretty much the same as in the linked issue.
In your case, you could also use a git commit hook shown in this recorded talk on YouTube.
HTH

This code post shows you how to get all staged files.
While we don't recommend this, it's certainly possible.
Detekt runs very fast. Unless you have a very big code base, this shouldn't matter at all.

Hi, forgive me, of course it is fast, I am just very impatient :-) I have a detekt pre-commit hook set up, but it usually takes 7-10 seconds to run the detekt gradle task.
Is there a particular reason you don't recommend detekting only staged files? For example could that produce false positives?

Is there a particular reason you don't recommend detekting only staged files?

When more rules use type and symbol solving, detekt will need the information from referenced types as well. Currently, only a very small number of rules (2-3) use type and symbol solving.

I have a detekt pre-commit hook set up, but it usually takes 7-10 seconds to run the detekt gradle task.

If this is a dealbreaker for you, you can also use detekt's console application.
Anyways, fetching the staged files with the code snippet in the mentioned post should work. You need to feed the received file path list into detekt (via Gradle Groovy or Kotlin DSL or CLI).
If you manage to hack this together, I can also see this pre-commit hook as a nice addition to detekt. It would also help other users with the same use case. So please feel free to submit a PR.
There are so many ways for integrating detekt into a users CI toolchain. We are actively learning from the community. Thank you for bringing this up and for the nice active discussion in this issue!

You can list of changed files and pipe them to detekt via the --input x,y,z parameter.
See git ls-files --modified for example.


Vulnerability roundup 109: edk2-202102: 1 advisory [8.1]

search, files

[ ] CVE-2021-38575 CVSSv3=8.1 (nixos-21.05)

CVE details
CVE-2021-38575
NetworkPkg/IScsiDxe has remotely exploitable buffer overflows.

Scanned versions: nixos-21.05: 3b422991781.

PR to fix: #150716


NameError: name 'reload' is not defined

Thanks for the bug report, but unfortunately we need some more information from you in order to triage this issue appropriately. Please edit your opening comment by providing a filled-in copy of our issue template. Once you are done please leave a comment to that effect.


[Question] Direct call vs. store.dispatch for action creators

I've just started reviewing ReSwift, and I'm in the process of trying to apply it to a new project.  I've been looking over the GitHubBrowserExample, and I have a question about when and why to use store.dispatch for certain situations.
The example project has an action creator that always returns nil itself, but it may fire some actions as side effects:
func authenticateUser(state: State, store: Store<State>) -> Action? {
    guard let config = state.authenticationState.oAuthConfig else { return nil }

    let url = config.authenticate()

    if let url = url {
        store.dispatch(SetOAuthURL(oAuthUrl: url))
        store.dispatch(SetRouteAction([loginRoute, oAuthRoute]))
    }

    return nil
}

The app doesn't fire this function directly, but instead uses store.dispatch(authenticateUser).  Since this particular function always returns nil, is there any special reason to use store.dispatch?  Is it safe to call a function like this - one that may trigger actions in an asynchronous completion handler - directly?
The app I'm creating will make asynchronous calls to an API server, and I'm wondering if triggering these calls needs to go through the store for some reason.  Apologies if I missed this explanation in the docs somewhere - and thanks in advance!

Thanks for pointing this out! The following is my personal opinion: the example code is misleading. I don't like it.
Action creators have a very special feature -- they get to know (State, Store<State>) as input. So this function makes use of the input without actually being a true action creator.
To me, this is cheating. I'd ask: "Why don't you write the app in a way that doesn't couple your event creation so high to ReSwift's ActionCreator? If you need the state, then get it by some other means."
As I said, that's just my personal take on this. I don't know if people repeatedly have to get access to the current store.state all of the time. I write service objects that e.g. subscribe to the authenticationState substate and act differently depending on the oAuthConfig attribute. But then again, maybe my OO is misleading :)

Action creators were replaced by thunks https://github.com/ReSwift/ReSwift-Thunk/


Learn vs Infer processor?

Hi,
I am looking at the Alpha158 data handler and it has the following for the Learn and Infer processors:
_DEFAULT_LEARN_PROCESSORS = [
    {"class": "DropnaLabel"},
    {"class": "CSZScoreNorm", "kwargs": {"fields_group": "label"}},
]
_DEFAULT_INFER_PROCESSORS = [
    {"class": "ProcessInf", "kwargs": {}},
    {"class": "ZScoreNorm", "kwargs": {}},
    {"class": "Fillna", "kwargs": {}},
]

Looking at the code for CSZScoreNorm and ZScoreNorm it appears they do similar normalization (subtract the mean and divide by std along axis 0).  The main difference appears to be that ZScoreNorm has the fit function to "learn" or keep the mean and std  of the fit set (between start and end) which could be used for inference data (new data).
Why wouldn't ZScoreNorm be used in the _DEFAULT_LEARN_PROCESSORS as well as _DEFAULT_INFER_PROCESSORS? It seems that all the data is being normalized with CSZScoreNorm.  Then at some later point, new data will use the ZScoreNorm which I assume is the same normalization with the exception that it is fitted in the time range?
Also, why wouldn't you also want the Fillna and ProcessInf also in the _DEFAULT_LEARN_PROCESSORS?
Thanks for your help.

Ok, I think I understand if someone could please confirm.  The CSZScoreNorm is only for the label which is why it has the the fields_group set to "label".  However, I believe there is no ZScoreNorm for the _DEFAULT_LEARN_PROCESSORS because the default data is already normalized as described here #590?  I am using my own data so I would need ZScoreNorm for both learn and infer if my data is raw?  I am assuming that Inf and NAs have already been fixed in the default data so that is why there is no Fillna and ProcessInf?

@jmrichardson
We have to mode for the processors.  The default mode is PTYPE_A = "append".  So the data processors for learning include the processors for inference.
Please refer to the docs here.  Thanks.
https://github.com/microsoft/qlib/blob/main/qlib/data/dataset/handler.py#L430

Makes sense now.   Thank you.

Would you mind sending a PR to improve the docs(or docstrings) about this Question?
Other users who have similar confusion will be grateful to you :)
Thanks

Will definitely help with docs soon.

Hi @you-n-g ,
I am testing the processors are being executed when running this simple workflow script in the default "append" mode:
import qlib
from qlib.contrib.data.handler import Alpha158
from qlib.contrib.model.gbdt import LGBModel
from qlib.utils import exists_qlib_data, init_instance_by_config

data_handler_config = {
    "start_time": "2008-01-01",
    "end_time": "2020-08-01",
    "fit_start_time": "2008-01-01",
    "fit_end_time": "2014-12-31",
    "instruments": 'test',
}

task = {
    "model": {
        "class": "LGBModel",
        "module_path": "qlib.contrib.model.gbdt",
        "kwargs": {
            "loss": "mse",
            "colsample_bytree": 0.8879,
            "learning_rate": 0.0421,
            "subsample": 0.8789,
            "lambda_l1": 205.6999,
            "lambda_l2": 580.9768,
            "max_depth": 8,
            "num_leaves": 210,
            "num_threads": 20,
        },
    },
    "dataset": {
        "class": "DatasetH",
        "module_path": "qlib.data.dataset",
        "kwargs": {
            "handler": {
                "class": "Alpha158",
                "module_path": "qlib.contrib.data.handler",
                "kwargs": data_handler_config,
            },
            "segments": {
                "train": ("2008-01-01", "2014-12-31"),
                "valid": ("2015-01-01", "2016-12-31"),
                "test": ("2017-01-01", "2020-08-01"),
            },
        },
    },
}

if __name__ == "__main__":

    # qlib.init(provider_uri="data/daily/qlib", dataset_cache="SimpleDatasetCache", local_cache_path='data/daily/qlib/cache')
    qlib.init(provider_uri="data/daily/qlib", dataset_cache="SimpleDatasetCache")

    # model initiaiton
    model = init_instance_by_config(task["model"])
    dataset = init_instance_by_config(task["dataset"])

    model.fit(dataset)  # fits on train and valid data segments
    model.predict(dataset)  # predicts test data

The default learn and infer processors are:
_DEFAULT_LEARN_PROCESSORS = [
    {"class": "DropnaLabel"},
    {"class": "CSZScoreNorm", "kwargs": {"fields_group": "label"}},
]
_DEFAULT_INFER_PROCESSORS = [
    {"class": "ProcessInf", "kwargs": {}},
    {"class": "ZScoreNorm", "kwargs": {}},
    {"class": "Fillna", "kwargs": {}},
]

And the Alpha158 has the following set for processors:
        infer_processors=[],
        learn_processors=_DEFAULT_LEARN_PROCESSORS,

According to process_type = "append" mode (which i have verified is append), both the infer and learn processors should be executed on the data.  However, only the learn processors appear to be executed.  Here is the output of the script:
[13404:MainThread](2021-09-16 13:19:26,155) INFO - qlib.Initialization - [config.py:350] - default_conf: client.
[13404:MainThread](2021-09-16 13:19:28,203) WARNING - qlib.Initialization - [config.py:375] - redis connection failed(host=<IP_ADDRESS> port=6379), DiskExpressionCache will not be used!
[13404:MainThread](2021-09-16 13:19:28,216) INFO - qlib.SimpleDatasetCache - [cache.py:1074] - DatasetCache directory: C:\Users\john\.cache\qlib_simple_cache, modify the cache directory via the local_cache_path in the config
[13404:MainThread](2021-09-16 13:19:28,219) INFO - qlib.Initialization - [__init__.py:58] - qlib successfully initialized based on client settings.
[13404:MainThread](2021-09-16 13:19:28,221) INFO - qlib.Initialization - [__init__.py:60] - data_path={'__DEFAULT_FREQ': WindowsPath('D:/Projects/aim/data/daily/qlib')}
D:\Anaconda3\envs\aim\lib\site-packages\pyqlib-0.7.1-py3.8-win-amd64.egg\qlib\utils\__init__.py:745: FutureWarning: MultiIndex.is_lexsorted is deprecated as a public function, users should use MultiIndex.is_monotonic_increasing instead.
  if idx.is_monotonic_increasing and not (isinstance(idx, pd.MultiIndex) and not idx.is_lexsorted()):
[13404:MainThread](2021-09-16 13:19:28,268) INFO - qlib.timer - [log.py:113] - Time cost: 0.042s | Loading data Done
[13404:MainThread](2021-09-16 13:19:28,278) INFO - qlib.timer - [log.py:113] - Time cost: 0.006s | DropnaLabel Done
[13404:MainThread](2021-09-16 13:19:43,768) INFO - qlib.timer - [log.py:113] - Time cost: 15.490s | CSZScoreNorm Done
[13404:MainThread](2021-09-16 13:19:43,769) INFO - qlib.timer - [log.py:113] - Time cost: 15.501s | fit & process data Done
[13404:MainThread](2021-09-16 13:19:43,769) INFO - qlib.timer - [log.py:113] - Time cost: 15.544s | Init data Done

Notice only Dropnalabel and CSXScoreNorm and not the inference processors.  I also put a debug breakpoint on the code for the inference processors and they are never executed.
If I change the infer_processors for Alpha168 to _DEFAULT_INFER_PROCESSORS:
class Alpha158(DataHandlerLP):
    def __init__(
        self,
        instruments="csi500",
        start_time=None,
        end_time=None,
        freq="day",
        infer_processors=[],
        learn_processors=_DEFAULT_LEARN_PROCESSORS + _DEFAULT_INFER_PROCESSORS,

Output of script (Note I commented out ProcessInf because it takes a very long time):
[18468:MainThread](2021-09-16 13:37:39,271) INFO - qlib.Initialization - [config.py:350] - default_conf: client.
[18468:MainThread](2021-09-16 13:37:41,321) WARNING - qlib.Initialization - [config.py:375] - redis connection failed(host=<IP_ADDRESS> port=6379), DiskExpressionCache will not be used!
[18468:MainThread](2021-09-16 13:37:41,337) INFO - qlib.SimpleDatasetCache - [cache.py:1074] - DatasetCache directory: C:\Users\john\.cache\qlib_simple_cache, modify the cache directory via the local_cache_path in the config
[18468:MainThread](2021-09-16 13:37:41,340) INFO - qlib.Initialization - [__init__.py:58] - qlib successfully initialized based on client settings.
[18468:MainThread](2021-09-16 13:37:41,341) INFO - qlib.Initialization - [__init__.py:60] - data_path={'__DEFAULT_FREQ': WindowsPath('D:/Projects/aim/data/daily/qlib')}
D:\Anaconda3\envs\aim\lib\site-packages\pyqlib-0.7.1-py3.8-win-amd64.egg\qlib\utils\__init__.py:745: FutureWarning: MultiIndex.is_lexsorted is deprecated as a public function, users should use MultiIndex.is_monotonic_increasing instead.
  if idx.is_monotonic_increasing and not (isinstance(idx, pd.MultiIndex) and not idx.is_lexsorted()):
[18468:MainThread](2021-09-16 13:37:41,380) INFO - qlib.timer - [log.py:113] - Time cost: 0.034s | Loading data Done
[18468:MainThread](2021-09-16 13:37:41,389) INFO - qlib.timer - [log.py:113] - Time cost: 0.006s | DropnaLabel Done
[18468:MainThread](2021-09-16 13:37:53,009) INFO - qlib.timer - [log.py:113] - Time cost: 11.619s | CSZScoreNorm Done
D:\Anaconda3\envs\aim\lib\site-packages\pyqlib-0.7.1-py3.8-win-amd64.egg\qlib\data\dataset\processor.py:236: RuntimeWarning: Mean of empty slice
  self.mean_train = np.nanmean(df[cols].values, axis=0)
C:\Users\john\AppData\Roaming\Python\Python38\site-packages\numpy\lib\nanfunctions.py:1664: RuntimeWarning: Degrees of freedom <= 0 for slice.
  var = nanvar(a, axis=axis, dtype=dtype, out=out, ddof=ddof,
[18468:MainThread](2021-09-16 13:38:08,708) INFO - qlib.timer - [log.py:113] - Time cost: 15.698s | ZScoreNorm Done
[18468:MainThread](2021-09-16 13:38:12,870) INFO - qlib.timer - [log.py:113] - Time cost: 4.160s | Fillna Done
[18468:MainThread](2021-09-16 13:38:12,872) INFO - qlib.timer - [log.py:113] - Time cost: 31.490s | fit & process data Done
[18468:MainThread](2021-09-16 13:38:12,873) INFO - qlib.timer - [log.py:113] - Time cost: 31.527s | Init data Done

Am I doing something wrong or should I just include the processors needed for each learn and infer?

@jmrichardson
Please refer to the docs here https://github.com/microsoft/qlib/blob/main/qlib/data/dataset/handler.py#L311

infer_processors=[],
I noticed that you didn't pass any processor to these parameters.

So shared_processors + infer_processors + learn_processors will be '[] + [] + _DEFAULT_LEARN_PROCESSORS
The results are expected.


Add support for loader developed by user

Not currently a priority.  Will add documentation upon user request.


Automatic lazy loading of JS type definition modules from frontend

Currently, when a DATEX value with a corresponding JS module (e.g. containing a @sync class) ist sent from the backend to the frontend, the JS module url is automatically appended to the DATEX request so that the JS type class is initialized on the frontend.
This does currently not work when a DATEX value that requires a JS sync class module is sent from the frontend to the backend.
If we have a module like this on the backend, and MySyncClass is not used anywhere else in the backend, it will never be initialized at runtime because it is only regarded as a TypeScript type definition:
// file: backend/do-something.ts
import { MySyncClass } from "common/sync-class.ts";

export function doSomething(syncClass: MySyncClass) {
	// ...
}

When the function is now called from the frontend with an instance of MySyncClass, we get a warning on the backend:

Cannot find type definition for <MySyncClass>

This can only be prevented if the frontend also sends the corresponding JS module URL to the backend together with the instance. This is currently explicitly disabled for the following reasons:

The module URL cannot be a full URL, e.g<EMAIL_ADDRESS>because the backend itself does not import modules from http, but as local files. Instead of a module URL, we would need to provide an import identifier, e.g. common/sync-class.ts. This is possible in theory, but we have to assume that the backend endpoint has a matching import map that can resolve the import identifier. This is true for normal UIX backends, but not for endpoints in general.
Severe security issues: By allowing arbitrary JS modules to be loaded on the backend when a frontend endpoint sends a DATEX request, we provide the possibility for arbitrary remote code execution (see https://github.com/unyt-org/datex-core-js-legacy/issues/27). We cannot add all frontend endpoints as trusted endpoints in the backend, but rather need to decide for each module if it can be imported on the backend: Only modules that are located in a common repository should be allowed to be loaded. This is still not perfect because a frontend endpoint can force the initialization of any common module on the backend endpoint that might have unintended side effects.

Current workaround:
import { MySyncClass } from "common/sync-class.ts";
import "common/sync-class.ts"; // <- add this import


Proposal: Lint for entities appearing in JSX

Example:
<MyComponent
  name={name}
  type={"string"}
  foo=bar>  {/* oops! */}
  x=y>
  Body Text
</MyComponent>

Now, when this renders, the body text will be "x=y>Body Text". This is almost certainly not what the developer intended.
It seems like any > that appears in the body of a react tag is probably an error. If the user wants this they should do >, or perhaps {'>'}. We could go further and also suggest that other HTML special characters are replaced with the correct entities.
Is there already a rule for this? I'm happy to look into adding this.

Here is a PR: https://github.com/yannickcr/eslint-plugin-react/pull/681

Here is another potential error that this rule might catch (from the PR):
<MyComponent>
  {'Text'}}  {/* oops, there is an extra closing brace! */}
</MyComponent>

Any feedback on this rule? I think it is very useful and it has caught several subtle errors in my project, and would help others similarly

Closed via #681?


Improve Telemetry and Job Monitoring

Business Metrics and Telemetry provides a good health of the complete architecture. As part of this lets identify and capture all the metrics and provide a dashboard through which monitoring can be setup by users in Grafana.
Some Business Metrics

Job/Task Delays, Time taken, Failures, Success, Reruns
View for getting the overall status of jobs scheduled over a period of time
Metrics to be captured at namespace/project/job level.

Server(Telemetry)

API metrics(time, count, failures, success)
Time taken at various stages of a request at each api level.

Changes will be done as part of  https://github.com/odpf/optimus/issues/314 https://github.com/odpf/optimus/issues/325


Clear search form in 'search within'

What is it and who's it for?
Anyone searching the contents of a digitised work
Users should be able to easily clear the search form so they can run a new search
User story
As a researcher
I need to be able to adjust my search keywords
So that I can make sure I've picked up everything relevant.
Implementation
Acceptance criteria

User can clear search form by clicking the clear icon

Would you expect any page highlights from a search to be cleared at the point of clearing the search input? I don't think there's currently a way to do this, beyond searching for something that yields no results. Or is the ability to clear highlights something else again?

No, I don't think clearing highlights or search results is necessary. Similar to how you can clear the search box on the regular search box - it just clears the text so you can type in something new, more easily than using delete key.


No Power BI Ribbon

In the section about "Users with multiple Power BI accounts" it states that "You can also select Profile from the Power BI ribbon tab in Excel".
However, when you open the .ODC file there is no Power BI ribbon.  You use to be able to get a similar looking Power BI ribbon by downloading the Power BI Publisher addon for Excel. The page about the Power BI Publisher takes you here to download it now (https://docs.microsoft.com/en-us/power-bi/publisher-for-excel).  So there does not seem to be any way to get that Power BI ribbon anymore.
Also, with the old Power BI Publisher addon I have the new v2 App workspaces do not show up in the workspaces lists.

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

ID: 2fcb95bc-abb8-5147-ddc5-00714e30f79b
Version Independent ID: 45626f2c-9e5c-6bdd-6fbb-b82c279962e0
Content: Analyze in Excel for Power BI - Power BI
Content Source: powerbi-docs/service-analyze-in-excel.md
Service: powerbi
Sub-service: powerbi-service
GitHub Login: @davidiseminger
Microsoft Alias: davidi

Hi, @AntiSquare -- good question. Assigning to the writer. In the meantime, you can check with the Power BI support site to see if they have more info. https://powerbi.microsoft.com/en-us/support/

Hello, I have the same problem... I'm trying to find the webpage where I can download the Power BI ribbon for Excel but I can't find it.

Finally, I find the correct link https://www.microsoft.com/en-US/download/details.aspx?id=50729

Great sleuthing, @JossephAnthony -- we can update the link with your info!

Thanks for the sleuthing! I've added that link to the article, and it'll refresh the article in the next 24 hours.


Cleanup the explicitly unwrapped parameters which had a default value…

Description
We shouldn't be using explicitly unwrapped variables when the parameters are optional. In this change I removed the explicit unwrap and only add the specific UI when the value is not nil.
Motivation and Context

The app crashed when I passed in a nil for the rate

https://github.com/AppPear/ChartView/issues/64
How Has This Been Tested?

Tested by passing in a nil for the rate change and observed that the rate was no longer displayed
Also didn't pass anything and allowed the default value of 14 to be shown.

Screenshots (if appropriate):

Types of changes

[ x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] Non-functional change (Updating Documentation, CI automation, etc..)

Checklist:

[ ] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.

Yes I’m aware of this https://github.com/AppPear/ChartView/pull/89 so I assume this won’t get merged.

Cool thanks


Use go workspace to configure multimodule dependencies

Release Note
NONE

I will wait for the outcome of the proposal to remove the other modules, so probably there won't be a need to merge this PR.

Closed in favor of #4690


Put rep-bulk into pipeline.

Using Francesca's code, build the docker and integrate it into the pipeline.

Closed by #97


add wasmJs support

Are there any plans for jsWasm support?

Right now this tool supports only .d.ts -> .kt conversion, but I am open to discussion. What kind of conversion do you need? To be honest, I don't know what is a format for describing types in WASM, which language is used for it and how to adapt them to Kotlin.

I have tried to do these type transformations on my own, and after doing some experimenting, and I determined that it is not an easy job, kotlinWasm has more limitations than kotlinJs.
 /* T */

  fun run(store: JsAny /* T */, callback: JsAny /* () => R */): JsAny /* R */

  fun run(
      store: JsAny /* T */,
      callback: JsAny /* (...args: TArgs) => R */,
      vararg args: JsAny
  ): JsAny /* R */

  fun exit(callback: JsAny /* (...args: TArgs) => R */, vararg args: JsAny): JsAny /* R */

  fun enterWith(store: JsAny /* T */): Unit /* void */
}

external interface HookCallbacks {
  val init:
      ((
          asyncId: Int,
          type: String,
          triggerAsyncId: Int,
          resource: JsAny /* object */) -> Unit /* void */)?

  val before: ((asyncId: Int) -> Unit /* void */)?

  val after: ((asyncId: Int) -> Unit /* void */)?

  val promiseResolve: ((asyncId: Int) -> Unit /* void */)?

  val destroy: ((asyncId: Int) -> Unit /* void */)?
}

external interface AsyncHook {
  fun enable(): AsyncHook /* this */

  fun disable(): AsyncHook /* this */
}

external interface AsyncResourceOptions {
  var triggerAsyncId: Int

  var requireManualDestroy: Boolean
}

wasmJs only supports a few type conversions, and in many cases we have to use JsAny instead.

It seems to me that auto-generation of externals for wasmJs is still too premature.
We need to way for the K/WASM team to relax some of the limitations.

We will discuss the possibility of this issues until a better time


Update appveyor.yml

:white_check_mark: Build bitcointrade-sdk-dotnet 1.0.171 completed (commit https://github.com/guibranco/bitcointrade-sdk-dotnet/commit/7db1169e4b by @guibranco)


Unable to load level, panics at Some(Visit(RegionDoesNotExist("NormalTexture")))

Hello. I was following the tutorial here https://rg3d.rs/tutorials/2021/03/05/tutorial1.html but when I try to load the scene, I get this error. Here is the complete log.
The system is:

Linux 5.14.2-arch1-2 x86_64 GNU/Linux
Arch Linux x86_64

Update: it works with your scene (if I do a git clone of this repo) but not with scenes made by me on the editor compiled on my own system.
Update 2: the problem seems to be the editor or some configuration of it. When I open your scenes and save them on my version of the editor, I get the same error. Btw, the textures do not load. I guess it is related to the fact that the textures folder is not asked for.
It may be useful (or maybe not, but just in case) to point out that the editor asks for my working directory (which I defined as the src of my project) but not the textures folder as shown on the tutorial.
Thanks in advance.
[INFO]: Shader FlatShader_VertexShader compiled!
[INFO]: Shader FlatShader_FragmentShader compiled!
[INFO]: Shader FlatShader linked!
[INFO]: Shader SsaoShader_VertexShader compiled!
[INFO]: Shader SsaoShader_FragmentShader compiled!
[INFO]: Shader SsaoShader linked!
[INFO]: Shader DeferredLightShader_VertexShader compiled!
[INFO]: Shader DeferredLightShader_FragmentShader compiled!
[INFO]: Shader DeferredLightShader linked!
[INFO]: Shader DeferredLightShader_VertexShader compiled!
[INFO]: Shader DeferredLightShader_FragmentShader compiled!
[INFO]: Shader DeferredLightShader linked!
[INFO]: Shader DeferredLightShader_VertexShader compiled!
[INFO]: Shader DeferredLightShader_FragmentShader compiled!
[INFO]: Shader DeferredLightShader linked!
[INFO]: Shader AmbientLightShader_VertexShader compiled!
[INFO]: Shader AmbientLightShader_FragmentShader compiled!
[INFO]: Shader AmbientLightShader linked!
[INFO]: Shader FlatShader_VertexShader compiled!
[INFO]: Shader FlatShader_FragmentShader compiled!
[INFO]: Shader FlatShader linked!
[INFO]: Shader SpotShadowMapShader_VertexShader compiled!
[INFO]: Shader SpotShadowMapShader_FragmentShader compiled!
[INFO]: Shader SpotShadowMapShader linked!
[INFO]: Shader PointShadowMapShader_VertexShader compiled!
[INFO]: Shader PointShadowMapShader_FragmentShader compiled!
[INFO]: Shader PointShadowMapShader linked!
[INFO]: Shader SpotVolumetricLight_VertexShader compiled!
[INFO]: Shader SpotVolumetricLight_FragmentShader compiled!
[INFO]: Shader SpotVolumetricLight linked!
[INFO]: Shader PointVolumetricLight_VertexShader compiled!
[INFO]: Shader PointVolumetricLight_FragmentShader compiled!
[INFO]: Shader PointVolumetricLight linked!
[INFO]: Shader FlatShader_VertexShader compiled!
[INFO]: Shader FlatShader_FragmentShader compiled!
[INFO]: Shader FlatShader linked!
[INFO]: Shader FlatShader_VertexShader compiled!
[INFO]: Shader FlatShader_FragmentShader compiled!
[INFO]: Shader FlatShader linked!
[INFO]: Shader FlatShader_VertexShader compiled!
[INFO]: Shader FlatShader_FragmentShader compiled!
[INFO]: Shader FlatShader linked!
[INFO]: Shader UIShader_VertexShader compiled!
[INFO]: Shader UIShader_FragmentShader compiled!
[INFO]: Shader UIShader linked!
[INFO]: Shader ParticleSystemShader_VertexShader compiled!
[INFO]: Shader ParticleSystemShader_FragmentShader compiled!
[INFO]: Shader ParticleSystemShader linked!
[INFO]: Shader DebugShader_VertexShader compiled!
[INFO]: Shader DebugShader_FragmentShader compiled!
[INFO]: Shader DebugShader linked!
[INFO]: Shader ForwardShader_VertexShader compiled!
[INFO]: Shader ForwardShader_FragmentShader compiled!
[INFO]: Shader ForwardShader linked!
[INFO]: Shader FXAAShader_VertexShader compiled!
[INFO]: Shader FXAAShader_FragmentShader compiled!
[INFO]: Shader FXAAShader linked!
[INFO]: Shader SpriteShader2D_VertexShader compiled!
[INFO]: Shader SpriteShader2D_FragmentShader compiled!
[INFO]: Shader SpriteShader2D linked!
[ERROR]: Unable to load model from "data/models/scene.rgs"! Reason Visit(RegionDoesNotExist("NormalTexture"))

Hi, it happens because the editor uses latest rg3d and data format of scenes changes between engine versions, in most cases there is backward compatibility between adjacent versions, but in some cases it is impossible. I'm pretty sure that in your case you're using 0.20(?) rg3d with the editor built with 0.23+. The 0.23 has new material system and there is no full backward compatibility between them, this means that terrains (and probably something else) are not backward compatible, but everything else should be. The scene has a terrain in it, so it is not compatible with 0.23+.
This is acceptable situation since the engine has not reached 1.0.0 version yet, the data format will stabilize only at 1.0.0.

Already fixed.


npm install @prisma/client and installation via prompt behave differently

Depending on if you have a package.json in your project you will get a prompt to install @prisma/client or now. Both methods behave differently:
C:\Users\Jan\Documents\throwaway\1363>prisma2 generate
In order to use the "prisma-client-js" generator, you need to install @prisma/client to your project.
√ Do you want to install it now? ... yes
yarn add v1.17.3
info No lockfile found.
[1/4] Resolving packages...
[2/4] Fetching packages...
[3/4] Linking dependencies...
[4/4] Building fresh packages...
success Saved lockfile.
success Saved 1 new dependency.
info Direct dependencies
└─<EMAIL_ADDRESS>info All dependencies
└─<EMAIL_ADDRESS>Done in 3.01s.

C:\Users\Jan\Documents\throwaway\1363>prisma2 generate
Error:
    Error: In order to use the "prisma-client-js" generator, you need to install @prisma/client to your project:
    npm install @prisma/client
        at C:/ProgramData/nvm/v12.6.0/node_modules/prisma2/build/index.js:183583:23
        at Generator.next (<anonymous>)
        at C:/ProgramData/nvm/v12.6.0/node_modules/prisma2/build/index.js:183554:71
        at new Promise (<anonymous>)
        at module.exports.9949.__awaiter (C:/ProgramData/nvm/v12.6.0/node_modules/prisma2/build/index.js:183550:12)
        at Object.prisma-client-js (C:/ProgramData/nvm/v12.6.0/node_modules/prisma2/build/index.js:183575:47)
        at Object.<anonymous> (C:/ProgramData/nvm/v12.6.0/node_modules/prisma2/build/index.js:83452:114)
        at Generator.next (<anonymous>)
        at C:/ProgramData/nvm/v12.6.0/node_modules/prisma2/build/index.js:83369:71
        at new Promise (<anonymous>)

C:\Users\Jan\Documents\throwaway\1363>npm install @prisma/client

><EMAIL_ADDRESS>postinstall C:\Users\Jan\Documents\throwaway\1363\node_modules\@prisma\client
> node scripts/postinstall.js

undefined
Error: In order to use "@prisma/photon", please install prisma2. You can install it with "npm add -D prisma2".
    at main (C:\Users\Jan\Documents\throwaway\1363\node_modules\@prisma\client\scripts\postinstall.js:22:9)
    at processTicksAndRejections (internal/process/task_queues.js:85:5)
npm notice created a lockfile as package-lock.json. You should commit this file.
npm WARN<EMAIL_ADDRESS>requires a peer of prisma2@* but none is installed. You must install peer dependencies yourself.
npm WARN<EMAIL_ADDRESS>No description
npm WARN<EMAIL_ADDRESS>No repository field.

+<EMAIL_ADDRESS>added 1 package and audited 1 package in 2.701s
found 0 vulnerabilities

C:\Users\Jan\Documents\throwaway\1363>

We don't have this prompt anymore, therefore I'm closing this.

npm ERR! code E404
npm ERR! 404 Not Found - GET https://registry.npmjs.org/@nestjs%2Ftcesting - Not found
npm ERR! 404
npm ERR! 404  '<EMAIL_ADDRESS>is not in this registry.
npm ERR! 404
npm ERR! 404 Note that you can also install from a
npm ERR! 404 tarball, folder, http url, or git url.
npm ERR!      C:\Users\Sibelle Djumeghe\AppData\Local\npm-cache_logs\2024-02-21T21_06_02_876Z-debug-0.log
i got this error when i try to install prisma client

please help

That does not look related. If you think it is, please open a new GitHub discussion instead of commenting on a four year old issue. Thank you.


Python 3.2 not supported by coverage

As can be seen on the travis build of https://github.com/bunbun/nested-dict/pull/2 , coverage explicitly no longer tries to keep syntax that is Python 3.2 compatible, and it was removed from the package metadata.
coverage 3.x supports Python 3.2.  If you need to keep Python 3.2 support, you could use that version, at least for the Python 3.2 build.  coverage-4.0a5 is the last pre-released that supported Python 3.2, if you need some of the new coverage magic.

Fixed by your patches. Thank you!

Thank you for merging all these patches!

My pleasure: you did all the hard work!


Correction for raw affiliation Western University, London, ON.

Correction needed for raw affiliation Western University, London, ON.
raw_affiliation_name: Western University, London, ON.
new_rors: 02grkyz14
previous_rors: 05cgtjz78
works_examples: W4387861337;W4320035931
contact: 99c8b48f88eed50a58e91f85eace9673:86e630c8eb203903 @ uwo.ca

This issue was accepted and ingested by the OpenAlex team on 2024-12-19. The new affiliations should be visible within the next 7 days.


Problems together with Alexa Actions Skill, seems like the spoken text is not updated?

Describe the bug
I am tinkering with Alexa Actions for a while already. Out of circumstances I wanna fix with some fun (Parents showing up in my flat when I am not at home for cleaning and complaining) I updated the skill to allow as reply ANY STRING Alexa is hearing. I abused AMAZON.SearchQuery for that. This part works flawless already, but what does not work is stacking Actions. First let me show you what I did:
Automations:
- id: telegram-bot-to-alexa
  alias: Telegram Bot Textausgabe auf Alexa
  trigger:
  - platform: event
    event_type: telegram_text
  action:
  - service: script.activate_alexa_actionable_notification
    data:
      text: '{{ trigger.event.data.text }}'
      event_id: alexa_notification_telegram-bot
      alexa_device: media_player.daniels_echo_show
  - service: notify.telegrambot
    data:
      message: '{{ trigger.event.data.text }}'
  mode: single
- id: alexa-to-telegram-bot
  alias: Alexa auf Telegram Bot Textausgabe
  trigger:
  - platform: event
    event_type: alexa_actionable_notification
    event_data:
      event_id: alexa_notification_telegram-bot
  action:
  - service: notify.telegrambot
    data:
      message: '{{ trigger.event.data.event_response }}'
  mode: single

I use a Bot driven Telegram channel for notifications, Surveillance Cam pics etc for a while already. Now I added these two automations to be able to fire phrases which Alexa then is saying. Then I catch the reply Alexa is hearing and post it back thx to the bot.
The second part works super fine, so I decided to post the problem here as report, not over there in the repo. These text messages Alexa has to say are never passing the skill, so it should be a problem here.
Sidenote, this is for debugging and to verify that my written text comes through. It will be disabled later:
  - service: notify.telegrambot
    data:
      message: '{{ trigger.event.data.text }}'

Now after the long introduction... where is the problem? Simple.

Lets start in the middle at "Test für Github" sent by me to Alexa. Telegram notification verifies that it got through. Alexa says "Test für Github". Nice. My reply "test zurück" is what I was saying and it got passed through. Fine, too. Then I added another one directly after that called "Test zwei für Github" sent by me to Alexa. Telegram notification verifies that it got through. Alexa says "Test für Github".... errr, wrong. It's funny that after some waiting it uses the new line, but if they are sort of stacked together, things go down the drain.
To Reproduce
Difficult to get separated from the text above. So please see above.
Expected behavior
The correct and recent text to be spoken by Alexa.
Screenshots
See above.
System details

Home-assistant (version): 2021.12.8
Hassio (Yes/No): Yes
alexa_media  (version from const.py or HA startup): 3.10.15
alexapy (version from pip show alexapy or HA startup): 1.25.3
Amazon 2FA is enabled (y/n). Yes

Logs
Please provide logs. We'll be most likely asking for them anyway.
home-assistant.txt
Additional context
Add any other context about the problem here.
EDIT: And another sidenote. Yesterday I listened to some music via Spotify on Alexa and before that I tinkered with that very same problem. I have a automation asking me if I wanna switch on the light when the light sensor detects darkness.
- id: nachts-lampen-an
  alias: Nachts Lampen an
  trigger:
  - platform: time_pattern
    minutes: '/5'
  condition:
  - condition: and
    conditions:
    - condition: state
      entity_id: device_tracker.hd1917
      state: 'home'
    - condition: time
      after: '16:00:00'
      before: '22:00:00'
    - condition: numeric_state
      entity_id: sensor.hue_motion_illuminance
      below: '8000'
    - condition: not
      conditions:
      - condition: state
        entity_id: media_player.plex_plex_for_windows_reimi_pc
        state: 'playing'
      - condition: state
        entity_id: timer.leaving
        state: 'active'
      - condition: state
        entity_id: timer.night_lamps
        state: 'active'
      - condition: state
        entity_id: light.wohnzimmer
        state: 'on'
  action:
  - service: script.activate_alexa_actionable_notification
    data:
      text: Es wird dunkel. Lampen an?
      event_id: actionable_notification_nachts_lampen
      alexa_device: media_player.daniels_echo_show
  - service: notify.telegrambot
    data:
      message: Es wird dunkel. Lampen an?
  mode: single
- id: nachts-lampen-an-yes
  alias: Lamps on after saying so
  trigger:
  - platform: event
    event_type: alexa_actionable_notification
    event_data:
      event_id: actionable_notification_nachts_lampen
      event_response: ResponseYes
  action:
  - service: homeassistant.turn_on
    entity_id: light.esszimmer
  - service: homeassistant.turn_on
    entity_id: light.wohnzimmer
  mode: single
- id: nachts-lampen-an-no
  alias: Lamps stay off after saying so
  trigger:
  - platform: event
    event_type: alexa_actionable_notification
    event_data:
      event_id: actionable_notification_nachts_lampen
      event_response: ResponseNo
  - platform: event
    event_type: alexa_actionable_notification
    event_data:
      event_id: actionable_notification_nachts_lampen
      event_response: ResponseNone
  action:
  - service: timer.start
    target:
      entity_id: timer.night_lamps
  mode: single

I did not even realize it was asking that question, because due to the former tinkering it never said "Es wird dunkel. Lampen an?" but one of the lines of my testing, here "Test"

I can't help you with actionable notifications. That's a different repository. https://github.com/keatontaylor/alexa-actions

The code for Amazon App Development and the howto is another repo, yes. The interface which is the problem is in your code. But as you command, I will move over there and let the report rot away as there is no one left to maintain as it seems.

Ok, try to explain simply what the issue is in the interface you're reporting because I only understand your report as dealing with the actions skill. Just because you don't like the fact keaton doesn't respond to issues doesn't mean you should take it out on me.

Well, my original intention was that the location of the code tells you where you report the bug. As the location over at keaton's github only is the skill you create on Amazon's dev page and that part does not cause a problem I thought the report is more to be posted here.
My reasoning: An Alexa Skill has different Request types and the one I see as "cause" here is the "LaunchRequest" you can find over at keaton's code, yes. But this request only does one thing, outputting/speaking the info it gets from the Home Assistant Skill we talk about here:
        home_assistant_object = HomeAssistant(handler_input)
        speak_output = home_assistant_object.ha_state['text']

This is the part where I first give the Order to say the "Test für Github". This is happily done. Then it waits for the spoken reply which can be of all kind the Skill supports, like yes, no, a number or now a line of text you can get back in Home Assistant. After you got that reply the skill is done.
So the part where I type "Test zwei für Github" and it still says the former line is a completely new session with Amazon's skill system and it gets a new text from Home Assistant in a new LaunchRequest. And here the skill sends the same old and now wrong text over to the skill.
Or in short: The skill is not able to remember the old spoken introduction between multiple instances of spoken phrase and reply of the peson in front. So it can not even accidentally throw the old text on the person in front. The error must come from the Home Assistant Addin part.
Sorry if I sounded a bit pissed and aggressive, that was not my intention. I was just a bit offended when my lengthy report is just closed down when the intention behind it should be right indeed.

Or in short: The skill is not able to remember the old spoken introduction between multiple instances of spoken phrase and reply of the peson in front. So it can not even accidentally throw the old text on the person in front. The error must come from the Home Assistant Addin part. At least if I believe in what Amazon tells me in their dev information.

This component doesn't have any Alexa skill nor have I ever worked on an Alexa skill. Are you referring to the Alexa core component? I have no idea where you go that line of code or how it interacts with this component.
To the extent the skill just interfaces with HA's notification system, we just implement a portion of that. The notify code is here. This component does not have any memory of prior text sent to it. All we do is convert HA's notify into the Alexa api we have reverse engineered where we pretend to be the mobile app.
I'd suggest you enable debug logging as in the template. Perhaps you can generate some logs showing how the skill your using interacts with AMP. If you can show me logs where you're issuing an API command and it doesn't work then perhaps I can help you but honestly I still don't know why you think it's related to this component.

I talk about your component, not the integrated Alexa feature of HA. And your component adds the needed communication to Keaton's skill made by his howto.
The code I did show you indeed is from the Alexa Skill by Keaton. It was just added to show that the component does not do much except talking what your addon passed over and then wait for a reply your addon gets back from the skill. For that it's not using the notification as there is no notification incoming sound before it starts talking. The text is should say is directly passed to the skill over at Amazon Cloud by your addon.
Regarding logs. A added logs at the very start when I opened the report. Are these wrong?

      - service: media_player.play_media
        data:
          entity_id: "{{ alexa_device }}"
          media_content_type: skill
          media_content_id: amzn1.ask.skill.5b01ab68-xxx

This is the first time you've listed anything that shows AMP in action. The logs you posted show it's working.
2022-01-08 17:26:32 DEBUG (MainThread) [alexapy.alexaapi] r***********l@f********e: Running behavior with data: {"behaviorId": "PREVIEW", "sequenceJson": "{\"@type\": \"com.amazon.alexa.behaviors.model.Sequence\", \"startNode\": {\"@type\": \"com.amazon.alexa.behaviors.model.SerialNode\", \"nodesToExecute\": [{\"@type\": \"com.amazon.alexa.behaviors.model.OpaquePayloadOperationNode\", \"type\": \"Alexa.Operation.SkillConnections.Launch\", \"operationPayload\": {\"targetDevice\": {\"deviceType\": \"A15996VY63BQ2D\", \"deviceSerialNumber\": \"G091GG07116700CW\"}, \"locale\": \"de-de\", \"customerId\": \"AC81WLWP22LFL\", \"connectionRequest\": {\"uri\": \"connection://AMAZON.Launch/amzn1.ask.skill.5b01ab68-753e-4aa1-9177-eca69afa963f\", \"input\": {}}}}]}}", "status": "ENABLED"}
2022-01-08 17:26:32 DEBUG (MainThread) [alexapy.alexaapi] r***********l@f********e: POST: https://alexa.amazon.de/api/behaviors/preview returned 200:OK:application/octet-stream

Do you have an example of the the logs showing the text to speech you're talking about? Your logs don't show any of that.
Again, if you want me to help you, you need to show me commands and logs showing interactions with alexa_media or alexapy. Just telling me about your use of alexa actions and alexa skills doesn't help me since I don't use those and frankly, I'm not here to debug that for you. In other words, it's not reasonable to expect me to research how those third-party components work. You need to show me how those components access alexa_media and alexapy and then show me how they're failing. For example, I still don't understand what you mean by "remember the old spoken introduction" and how that relates to my component at all.


fcrepo-webapp-plus: default build - webac and audit

Resolves: https://jira.duraspace.org/browse/FCREPO-1773

Resolved with: https://github.com/fcrepo4-exts/fcrepo-webapp-plus/commit/77ade85a1658602fab2e34038bc407cf87ce1421


Fix webscalesqlclient CMakeLists no download info issue

CMake: 3.2.2
ArchLinux: 4.0.4-2-ARCH ... x86_64 GNU/Linux
CMake Error at /usr/share/cmake-3.2/Modules/ExternalProject.cmake:1850 (message):
  error: no download info for 'webscalesqlclient' -- please specify
  existing/non-empty SOURCE_DIR or one of URL, CVS_REPOSITORY and CVS_MODULE,
  SVN_REPOSITORY, GIT_REPOSITORY, HG_REPOSITORY or DOWNLOAD_COMMAND

This appears to have stalled; closing. If you want to address the comments above, please update and we can reopen.


Delete button or icon on commands modal

I think it will be more user friendly if we have a delete icon or button on commands modal instead just the the modal toggle.

its already there for long time, but not really good visible i agree. Will update visibility of the "open in new Window" text and close icon

I even don't remember that I logged in the comment