'hybrid mutants' can leak to the next run --ignoreStatic

Summary
Testing hybrid mutants with --ignoreStatic doesn't work as expected with --ignoreStatic.
For an explanation about what "hibrid" mutants are, see
https://github.com/stryker-mutator/mutation-testing-elements/pull/1547/files
The assumption was that we would be able to test hybrid mutants as regular non-static mutants without the state leaking out. This assumption is incorrect. See the next example (grabbed from expressjs):
From test/res.format.js
var app1 = express();

app1.use(function(req, res, next){
  res.format({ /* redacted for readability */ });
});

app1.use(function(err, req, res, next){
/* redacted for readability */
})

var app2 = express();

app2.use(function(req, res, next){
/* redacted for readability */
});

app2.use(function(err, req, res, next){
/* redacted for readability */
})

var app3 = express();

app3.use(function(req, res, next){
/* redacted for readability */
});

var app4 = express();

app4.get('/', function(req, res, next){
/* redacted for readability */
});

app4.use(function(err, req, res, next){
/* redacted for readability */
})

var app5 = express();

app5.use(function (req, res, next) {
/* redacted for readability */
});

describe('res', function(){
  /* a lot of tests here, using `app1` through `app5` */
});

As you can see, the tests themselves add static coverage in this example (the initialization of app1 through app5 is done in static context (no test was active yet)). Now imagine a test runner first testing hybrid mutants in scope and next running another non-static mutant. The result will be that these app1 through app5 variables will have loaded the hybrid mutants. The only way to clear them would be by restarting the test runner process.
The result is tons of runtime errors. See this report.
express-v6-concurrency-15-ignore-static.zip
I've rerun with this change (ignoring hybrid mutants):
diff --git a/packages/core/src/mutants/mutant-test-planner.ts b/packages/core/src/mutants/mutant-test-planner.ts
index 4bc9e051..dcc1a7c0 100644
--- a/packages/core/src/mutants/mutant-test-planner.ts
+++ b/packages/core/src/mutants/mutant-test-planner.ts
@@ -68,7 +68,7 @@ export class MutantTestPlanner {
       // If there was coverage information (coverageAnalysis not "off")
       const tests = this.testsByMutantId.get(mutant.id) ?? [];
       const coveredBy = toTestIds(tests);
-      if (!isStatic || (this.options.ignoreStatic && coveredBy.length)) {
+      if (!isStatic) {
         // If not static, or it was "hybrid" (both static and perTest coverage) and ignoreStatic is on.
         // Only run covered tests
         const netTime = calculateTotalTime(tests);

And the result seems to be a lot more consistent (about as consistent as StrykerJS v5). But entire (hybrid) functions are ignored now. Not sure that is what we want. See this report:
express-v6-concurrency-15-ignore-static-hybrid.zip
Note: running without --ignoreStatic works as expected.
I can think of 4 possible solutions here:

Fix
Keep testing hybrid mutants, but make sure that the mutant isn't active yet during the loading of the files. Our test runners will have to know if it is running under --ignoreStatic. since you don't want that behavior when not running with --ignoreStatic. Both mocha and Jasmine support this.
Known issue
Keep behavior like it is now and try to educate people to initialize their suts in beforeEach. This will make it impossible to make --ignoreStatic the default because this is essentially a bug.
Ignore
Always ignore hybrid mutants under --ignoreStatic
Configure
Allow users to configure the behavior: --static run|ignore|hybrid

Stryker config
Using the epic/esm branch.
{
  "$schema": "../../../packages/core/schema/stryker-schema.json",
  "testRunner": "mocha",
  "coverageAnalysis": "perTest",
  "mochaOptions": {
    "require": ["test/support/env"],
    "files": ["test/*.js", "test/acceptance/*.js"]
  },
  "ignoreStatic": true
}

Test runner config
none
Stryker environment
Using the epic/esm branch.
+--<EMAIL_ADDRESS>
Test runner environment
mocha --require test/support/env --reporter spec --bail --check-leaks test/ test/acceptance/

Add stryker.log
stryker.log

I thought about it this weekend and I think we don't really have a choice in the matter. It should be fixed. I went ahead and implemented the fix in #3443.
@simondel can you review this tomorrow?

Closed with #3443


Storybook/issue #20

Reviewers
Changes

adding storybook

Definition of Done (from ticket)
Storybook is available on the default URL.
HeaderComponent story is visible in Storybook.
QA steps (optional)
Known Issues

This PR is duplicated. Storybook was added on this one https://github.com/clevercanary/data-browser/pull/24


[FEAT] Create a CI workflow to automatically build the IR files

Description
Currently, the IR files are being updated manually, which means the files won't be updated immediately each time a new commit is made. It'd be great if a CI workflow was made to automatically update the IR files. This will also help in actions such as Setup Jule.

I think the IR updates should be manual. But I think a script or something like that can be done to speed up this process. That's why I developed a Pure Jule IR updater, currently available in the repository.
IR codes will continue to be updated manually, but the process can now be completed automatically with an executed program. This way, we won't lose our control over IR updates while saving time.
Thanks for your contribution.


plan status stays in progress

What happened:
Installing a KUDO operator, it deploys the operator as expected but the plan stays in progress:
kubectl kudo plan status  --instance=kafka
Plan(s) for "kafka" in namespace "default":
.
└── kafka (Operator-Version: "kafka-1.0.2" Active-Plan: "deploy")
    ├── Plan deploy (serial strategy) [IN_PROGRESS]
    │   └── Phase deploy-kafka [IN_PROGRESS]
    │       └── Step deploy (IN_PROGRESS)

In the controller logs I see:
2019/11/28 13:22:09 PlanExecution: default/kafka all phases of the plan deploy are ready
2019/11/28 13:22:09 InstanceController: Error when updating instance status. the server could not find the requested resource (put instances.kudo.dev kafka)
2019/11/28 13:22:09 InstanceController: Error when updating instance. the server could not find the requested resource (put instances.kudo.dev kafka)
{"level":"error","ts":1574943729.648818,"logger":"controller-runtime.controller","msg":"Reconciler error","controller":"instance","request":"default/kafka","error":"the server could not find the requested resource (put instances.kudo.dev kafka)","stacktrace":"github.com/go-logr/zapr.(*zapLogger).Error\n\t/Users/zain/go/pkg/mod/github.com/go-logr/zapr@v0.1.0/zapr.go:128\nsigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).reconcileHandler\n\t/Users/zain/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.4.0/pkg/internal/controller/controller.go:258\nsigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).processNextWorkItem\n\t/Users/zain/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.4.0/pkg/internal/controller/controller.go:232\nsigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).worker\n\t/Users/zain/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.4.0/pkg/internal/controller/controller.go:211\nk8s.io/apimachinery/pkg/util/wait.JitterUntil.func1\n\t/Users/zain/go/pkg/mod/k8s.io/apimachinery@v0.0.0-20191004115801-a2eda9f80ab8/pkg/util/wait/wait.go:152\nk8s.io/apimachinery/pkg/util/wait.JitterUntil\n\t/Users/zain/go/pkg/mod/k8s.io/apimachinery@v0.0.0-20191004115801-a2eda9f80ab8/pkg/util/wait/wait.go:153\nk8s.io/apimachinery/pkg/util/wait.Until\n\t/Users/zain/go/pkg/mod/k8s.io/apimachinery@v0.0.0-20191004115801-a2eda9f80ab8/pkg/util/wait/wait.go:88"}

What you expected to happen:
To plan to be marked as complete
How to reproduce it (as minimally and precisely as possible):
I have tested it in both 0.8.0 and master branch.
Anything else we need to know?:
Environment:

Kubernetes version (use kubectl version):
Kudo version (use kubectl kudo version):
Operator:
operatorVersion:
Cloud provider or hardware configuration:
OS (e.g. from /etc/os-release):
Kernel (e.g. uname -a):
Install tools:
Others:

restarting the controller didn't help in this case
go run -ldflags "-X github.com/kudobuilder/kudo/pkg/version.gitVersion=0.8.0 -X github.com/kudobuilder/kudo/pkg/version.gitCommit=7685bcdd -X github.com/kudobuilder/kudo/pkg/version.buildDate=2019-11-28T09:07:13Z" ./cmd/manager/main.go
{"level":"info","ts":1574945047.140621,"logger":"entrypoint","msg":"KUDO Version: version.Info{GitVersion:\"0.8.0\", GitCommit:\"7685bcdd\", BuildDate:\"2019-11-28T09:07:13Z\", GoVersion:\"go1.13.3\", Compiler:\"gc\", Platform:\"darwin/amd64\"}"}
{"level":"info","ts":1574945047.140666,"logger":"entrypoint","msg":"setting up manager"}
{"level":"info","ts":1574945050.58253,"logger":"controller-runtime.metrics","msg":"metrics server is starting to listen","addr":":8080"}
{"level":"info","ts":1574945050.582634,"logger":"entrypoint","msg":"Registering Components."}
{"level":"info","ts":1574945050.5826402,"logger":"entrypoint","msg":"setting up scheme"}
{"level":"info","ts":1574945050.582755,"logger":"entrypoint","msg":"Setting up operator controller"}
{"level":"info","ts":1574945050.5828,"logger":"entrypoint","msg":"Setting up operator version controller"}
{"level":"info","ts":1574945050.5828302,"logger":"entrypoint","msg":"Setting up instance controller"}
{"level":"info","ts":1574945050.582858,"logger":"entrypoint","msg":"Starting the Cmd."}
{"level":"info","ts":1574945050.583022,"logger":"controller-runtime.manager","msg":"starting metrics server","path":"/metrics"}
{"level":"info","ts":1574945050.5831292,"logger":"controller-runtime.controller","msg":"Starting EventSource","controller":"operator","source":"kind source: /, Kind="}
{"level":"info","ts":1574945050.5831192,"logger":"controller-runtime.controller","msg":"Starting EventSource","controller":"operatorversion","source":"kind source: /, Kind="}
{"level":"info","ts":1574945050.583176,"logger":"controller-runtime.controller","msg":"Starting EventSource","controller":"instance","source":"kind source: /, Kind="}
{"level":"info","ts":1574945050.784757,"logger":"controller-runtime.controller","msg":"Starting EventSource","controller":"instance","source":"kind source: /, Kind="}
{"level":"info","ts":1574945050.784823,"logger":"controller-runtime.controller","msg":"Starting Controller","controller":"operator"}
{"level":"info","ts":1574945050.784907,"logger":"controller-runtime.controller","msg":"Starting EventSource","controller":"instance","source":"kind source: /, Kind="}
{"level":"info","ts":1574945050.784938,"logger":"controller-runtime.controller","msg":"Starting workers","controller":"operator","worker count":1}
2019/11/28 13:44:10 OperatorController: Received Reconcile request for an operator named: kafka
2019/11/28 13:44:10 OperatorController: Received Reconcile request for an operator named: zookeeper
{"level":"info","ts":1574945050.8835928,"logger":"controller-runtime.controller","msg":"Starting Controller","controller":"operatorversion"}
{"level":"info","ts":1574945051.083984,"logger":"controller-runtime.controller","msg":"Starting workers","controller":"operatorversion","worker count":1}
2019/11/28 13:44:11 OperatorVersionController: Received Reconcile request for an operatorVersion named: kafka-1.0.2
2019/11/28 13:44:11 OperatorVersionController: Received Reconcile request for an operatorVersion named: zookeeper-0.2.0
{"level":"info","ts":1574945051.085506,"logger":"controller-runtime.controller","msg":"Starting EventSource","controller":"instance","source":"kind source: /, Kind="}
{"level":"info","ts":1574945051.489055,"logger":"controller-runtime.controller","msg":"Starting EventSource","controller":"instance","source":"kind source: /, Kind="}
{"level":"info","ts":1574945051.690645,"logger":"controller-runtime.controller","msg":"Starting EventSource","controller":"instance","source":"kind source: /, Kind="}
{"level":"info","ts":1574945051.891954,"logger":"controller-runtime.controller","msg":"Starting EventSource","controller":"instance","source":"kind source: /, Kind="}
{"level":"info","ts":1574945051.8920178,"logger":"controller-runtime.controller","msg":"Starting Controller","controller":"instance"}
{"level":"info","ts":1574945051.892033,"logger":"controller-runtime.controller","msg":"Starting workers","controller":"instance","worker count":1}
2019/11/28 13:44:11 InstanceController: Received Reconcile request for instance "kafka"
2019/11/28 13:44:11 InstanceController: Going to proceed in execution of active plan deploy on instance default/kafka
2019/11/28 13:44:16 HealthUtil: Unknown type *v1.ServiceAccount is marked healthy by default
2019/11/28 13:44:16 HealthUtil: Unknown type *v1.Role is marked healthy by default
2019/11/28 13:44:16 HealthUtil: Unknown type *v1.RoleBinding is marked healthy by default
2019/11/28 13:44:16 HealthUtil: Unknown type *v1.ConfigMap is marked healthy by default
2019/11/28 13:44:16 HealthUtil: Unknown type *v1.ConfigMap is marked healthy by default
2019/11/28 13:44:16 HealthUtil: Unknown type *v1.ConfigMap is marked healthy by default
2019/11/28 13:44:16 HealthUtil: Unknown type *v1.ConfigMap is marked healthy by default
2019/11/28 13:44:16 HealthUtil: Unknown type *v1.ConfigMap is marked healthy by default
2019/11/28 13:44:16 HealthUtil: Unknown type *v1.ConfigMap is marked healthy by default
2019/11/28 13:44:16 HealthUtil: Unknown type *v1.ConfigMap is marked healthy by default
2019/11/28 13:44:16 HealthUtil: Unknown type *v1.Service is marked healthy by default
2019/11/28 13:44:16 Statefulset kafka-kafka is marked healthy
2019/11/28 13:44:16 HealthUtil: Unknown type *v1beta1.PodDisruptionBudget is marked healthy by default
2019/11/28 13:44:16 PlanExecution: default/kafka all phases of the plan deploy are ready
2019/11/28 13:44:17 InstanceController: Error when updating instance status. the server could not find the requested resource (put instances.kudo.dev kafka)
2019/11/28 13:44:17 InstanceController: Error when updating instance. the server could not find the requested resource (put instances.kudo.dev kafka)
{"level":"error","ts":1574945057.065208,"logger":"controller-runtime.controller","msg":"Reconciler error","controller":"instance","request":"default/kafka","error":"the server could not find the requested resource (put instances.kudo.dev kafka)","stacktrace":"github.com/go-logr/zapr.(*zapLogger).Error\n\t/Users/zain/go/pkg/mod/github.com/go-logr/zapr@v0.1.0/zapr.go:128\nsigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).reconcileHandler\n\t/Users/zain/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.4.0/pkg/internal/controller/controller.go:258\nsigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).processNextWorkItem\n\t/Users/zain/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.4.0/pkg/internal/controller/controller.go:232\nsigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).worker\n\t/Users/zain/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.4.0/pkg/internal/controller/controller.go:211\nk8s.io/apimachinery/pkg/util/wait.JitterUntil.func1\n\t/Users/zain/go/pkg/mod/k8s.io/apimachinery@v0.0.0-20191004115801-a2eda9f80ab8/pkg/util/wait/wait.go:152\nk8s.io/apimachinery/pkg/util/wait.JitterUntil\n\t/Users/zain/go/pkg/mod/k8s.io/apimachinery@v0.0.0-20191004115801-a2eda9f80ab8/pkg/util/wait/wait.go:153\nk8s.io/apimachinery/pkg/util/wait.Until\n\t/Users/zain/go/pkg/mod/k8s.io/apimachinery@v0.0.0-20191004115801-a2eda9f80ab8/pkg/util/wait/wait.go:88"}

We reworked updating instance plan status and I haven't seen this issue in the recent releases. Feel free to reopen should the issue resurface.


Move test_file_menu.py to new app model location

References and relevant issues
Reference: https://github.com/napari/napari/pull/4865#discussion_r1292882135
Description
Move test_file_menu.py to new app model location, as file_menu no longer exists in napari/_qt/menus and this folder is scheduled to be removed as we move to app model.

cc @DragaDoncila


Use release docker images for tlbc quickstart

Note: the quickstart for the tlbc network will not work for the moment, since there is no tlbc-node:release image so far. This must be provided in future when the setup is ready.
Closes: #464

Codecov Report

Merging #525 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #525   +/-   ##
=======================================
  Coverage   75.89%   75.89%
=======================================
  Files          18       18
  Lines         921      921
=======================================
  Hits          699      699
  Misses        222      222

Flag
Coverage Δ

#bridge_end2end
0% <ø> (ø)
:arrow_up:

#bridge_unit
75.89% <ø> (ø)
:arrow_up:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update fc10513...48d75aa. Read the comment docs.


[LSP] Goto definition is getting response null

Expected behavior
Should get the response for the step.
Actual behavior
Getting the following response
19:54:01.024 --> request #0: initialize: {"processId":13660,"rootPath":"c:\\work\\getgauge\\gauge-lsp-tests\\data\\steps-gotodefinition","rootUri":"file:///c%3A/work/getgauge/gauge-lsp-tests/data/steps-gotodefinition","capabilities":{"workspace":{"applyEdit":true,"didChangeConfiguration":{"dynamicRegistration":true},"didChangeWatchedFiles":{"dynamicRegistration":true},"symbol":{"dynamicRegistration":true},"executeCommand":{"dynamicRegistration":true}},"textDocument":{"synchronization":{"dynamicRegistration":true,"willSave":true,"willSaveWaitUntil":true,"didSave":true},"completion":{"dynamicRegistration":true,"completionItem":{"snippetSupport":true,"commitCharactersSupport":true}},"hover":{"dynamicRegistration":true},"signatureHelp":{"dynamicRegistration":true},"definition":{"dynamicRegistration":true},"references":{"dynamicRegistration":true},"documentHighlight":{"dynamicRegistration":true},"documentSymbol":{"dynamicRegistration":true},"codeAction":{"dynamicRegistration":true},"codeLens":{"dynamicRegistration":true},"formatting":{"dynamicRegistration":true},"rangeFormatting":{"dynamicRegistration":true},"onTypeFormatting":{"dynamicRegistration":true},"rename":{"dynamicRegistration":true},"documentLink":{"dynamicRegistration":true}}},"trace":"off","experimental":{}}
19:54:01.027 <-- result #0: initialize: {"capabilities":{"textDocumentSync":1,"completionProvider":{"resolveProvider":true,"triggerCharacters":["*","* ","\"","\u003c",":",","]},"definitionProvider":true,"documentSymbolProvider":true,"workspaceSymbolProvider":true,"codeActionProvider":true,"codeLensProvider":{},"documentFormattingProvider":true,"renameProvider":true}}
19:54:01.034 --> notif: initialized: {}
19:54:01.040 --> notif: textDocument/didOpen: {"textDocument":{"uri":"file:///c%3A/work/getgauge/gauge-lsp-tests/data/steps-gotodefinition/specs/implementedStep.spec","languageId":"markdown","version":1,"text":"Go to definition of specification\r\n=================================\r\nA scenario\r\n-------------------------\r\n* step1\r\nAnother scenario\r\n-------------------------\r\n* step1\r\n* step1"}}
19:54:01.063 --> request #1: textDocument/definition: {"position":{"line":8,"character":4},"textDocument":{"uri":"file:///c%3A/work/getgauge/gauge-lsp-tests/data/steps-gotodefinition/specs/implementedStep.spec"}}
19:54:01.079 <-- result #1: textDocument/definition: null
19:54:01.092 <-- notif: textDocument/publishDiagnostics: {"uri":"file:///c%3A/work/getgauge/gauge-lsp-tests/data/steps-gotodefinition/specs/concept_definition.spec","diagnostics":[]}
19:54:01.093 <-- notif: textDocument/publishDiagnostics: {"uri":"file:///c%3A/work/getgauge/gauge-lsp-tests/data/steps-gotodefinition/specs/implementedStep.spec","diagnostics":[]}
19:54:02.624 <-- request #0: client/registerCapability: {"registrations":[{"id":"gauge-runner-didOpen","method":"textDocument/didOpen","registerOptions":{"documentSelector":{"scheme":"file","language":"javascript","pattern":"c:\\work\\getgauge\\gauge-lsp-tests\\data\\steps-gotodefinition/**/*"}}},{"id":"gauge-runner-didClose","method":"textDocument/didClose","registerOptions":{"documentSelector":{"scheme":"file","language":"javascript","pattern":"c:\\work\\getgauge\\gauge-lsp-tests\\data\\steps-gotodefinition/**/*"}}},{"id":"gauge-runner-didChange","method":"textDocument/didChange","registerOptions":{"documentSelector":{"scheme":"file","language":"javascript","pattern":"c:\\work\\getgauge\\gauge-lsp-tests\\data\\steps-gotodefinition/**/*"},"syncKind":1}},{"id":"gauge-runner-codelens","method":"textDocument/codeLens","registerOptions":{"documentSelector":{"scheme":"file","language":"javascript","pattern":"c:\\work\\getgauge\\gauge-lsp-tests\\data\\steps-gotodefinition/**/*"}}}]}
19:54:02.626 --> result #0: client/registerCapability: null
19:54:02.660 <-- notif: textDocument/publishDiagnostics: {"uri":"file:///c%3A/work/getgauge/gauge-lsp-tests/data/steps-gotodefinition/specs/concept_definition.spec","diagnostics":[{"range":{"start":{"line":4,"character":0},"end":{"line":4,"character":10000}},"severity":1,"code":"step(\"another scenario\", async function() {\n\tthrow 'Unimplemented Step';\n});","message":"Step implementation not found"},{"range":{"start":{"line":7,"character":0},"end":{"line":7,"character":10000}},"severity":1,"code":"step(\"undefined Concept\", async function() {\n\tthrow 'Unimplemented Step';\n});","message":"Step implementation not found"}]}
19:54:02.660 <-- notif: textDocument/publishDiagnostics: {"uri":"file:///c%3A/work/getgauge/gauge-lsp-tests/data/steps-gotodefinition/specs/implementedStep.spec","diagnostics":[]}

Steps to replicate

Run LSP tests gotodefinition\goto a step definition.spec

Version
Gauge version: 0.9.8.nightly-2018-01-16
Commit Hash: bd76268

Plugins
-------
js (2.1.1.nightly-2018-01-16)

With the latest working as expected


Status of this project

From #216 and #161, it looks like this project is still maintained by the original author @dtao . Just that it's not so active. So, I am just wondering, after many years of development, is this project stable now? Is the last sentence added 6 years ago in the README ("This library is experimental and still a work in progress.") still reflecting the current status?
Thanks

Fair question :)
I think this library is pretty stable. It's got lots of dependent projects. (I'm not sure how active they all are, of course.)
With that in mind, I should probably remove that note about the library being experimental from the README.
Aside from the library being stable, there are plenty of improvements I would like to make, if I had unlimited time. For what it's worth, I think I have generally made at least a modest effort to fix actual bugs when they are raised. Last I checked, most of the open issues today are requests for new features, or for existing features to work a bit differently.

@dtao Nice to know that! :) Thanks for your effort!

@dtao I have created a PR https://github.com/dtao/lazy.js/pull/226 to help you remove the notice :)


submodules: make shallow clones

Make shallow clones in order to prevent unnecessary downloading
during dependency fetching.

Looks like this was approved, any reason it can't be merged?


NET: Implementation of CoordinateSequence for FlatGeobuf needs proper Copy method

The current implementation of CoordinateSequence for FlatGeobuf needs a proper CoordinateSequence.Copy method. Without it, calls to Geometry.Copy() return empty geometries.

@bjornharrtell, I'm sorry but the initial implementation is buggy for multi-part geometries due to wrong offset for System.Buffers.Copy(...).

@FObermaier does it make sense to reopen this or treat as new bug?

I think that this will do


Init breaks if path callback immediately returns void

As per the docs, the path callback should return void to signal that we have reached the end of content.
If however, this condition if met right at the first init, the plugin will fail to even start:
Test case: https://jsfiddle.net/bm2upo61/4/
More elaborate example: https://codepen.io/anon/pen/RMoOeV?selected_tag=infinite-scroll-v3-docs
The plugin requires the result of the path callback to be a string at least once because proto.updateGetAbsolutePath performs a regex on it.
If you're wondering about the use case: I added some select fields to filter the content by categories, then add the input values as GET parameters in the path callback. So it's entirely possible to navigate to a combination of categories that does not have any content. Then, if I refresh the page, infiniteScroll crashes

Thanks for reporting this bug. I'll look to fix this in a future release.


Go to next line (move the caret one line down independent of word wrap)

I would like to go to next line (move the caret one line down) when the line I am currently on is affected by word wrap (a long line takes up multiple rows, so using down key moves the caret within the same line).
This is similar to how the command "Insert line below" inserts new line after the current line (even when current line is affected by word wrap).
This command would preferably move the cursor to the beginning of next line, but could make sense to have a command that moves identical number of characters into the next line as well.

This can be done by using the cursorMove command. This command is used internally by all other cursor navigation commands. e.g.:
{
    "key": "down",
    "command": "cursorMove",
    "args": { "by": "line", "to": "down" },
    "when": "editorTextFocus"
}

This can be done by using the cursorMove command. This command is used internally by all other cursor navigation commands. e.g.:
{
    "key": "down",
    "command": "cursorMove",
    "args": { "by": "line", "to": "down" },
    "when": "editorTextFocus"
}

Possible to make this accessible in the "keyboard shortcuts" settings?

AFAIK The rich keyboard shortcuts editor cannot currently edit the args or when section of a keybinding. This is tracked in https://github.com/microsoft/vscode/issues/84072

AFAIK The rich keyboard shortcuts editor cannot currently edit the args or when section of a keybinding. This is tracked in #84072

This means that this is not a solution to my request. Any more information that is needed @alexdima?


It should be easy to define the mouse cursor for buttons and other actionable items

Currently, Lumo does not use pointer: cursor; for many of the clickable items in the UI (buttons, dropdown toggles, checkboxes/radio buttons, list items). This is a deliberate choice, that the pointer cursor is reserved for “link-like” actions. Tabs is currently an exception, as they are not actual links, though they are a similar navigational element as traditional links.
But, this is a divisive topic (see this and this article and this discussion), and we should make it easy to switch to the opposite “camp” where most clickable elements do have pointer: cursor;.
Something like a --lumo-clickable-cursor property which could be used in the component themes.

Hi, in the description of the issue, Jouni mentioned for many of the clickable items in the UI (buttons, dropdown toggles, checkboxes/radio buttons, list items). but then for what I was able to see this was only applied to buttons, not to other clickable elements like checkboxes and radio groups.

Yes, the change is still yet to be done for most of the components. We should open issue for each individual component to track that we apply this property there.


[UI] [Peer registration] Create peer 'close' icon doesn't work.

For replay this bug you need:
Test case

Go to SS and login under any account.
Go to 'Peer registration' page and click on 'create peer' button then click on close icon.

Result: popup form doesn't close.

@Commander223 Notice: you can reproduce it only if you don't have any registered peers.


automatically generate progress at a few intervals (count # of questions and divide)

query: do this in the code block or in the question modifier?

When I've used this, I've found it easier to do in the interview order code block because there I can keep a sense of where questions are at any given time. Keeping track of each question block and where in the interview it is hasn't been very successful for me.

When I've used this, I've found it easier to do in the interview order code block because there I can keep a sense of where questions are at any given time. Keeping track of each question block and where in the interview it is hasn't been very successful for me.

I think you're right

Fixed in https://github.com/SuffolkLITLab/docassemble-assemblylinewizard/commit/14866a728194af810f8f1af9d2b12e2b97f68fc2


ansible/artifactory code-style fixes

PR Checklist
[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]

[X] Title of the PR starts with installer/product name (e.g. [ansible/artifactory])
[ ] CHANGELOG.md updated
[ ] Variables and other changes are documented in the README.md

What this PR does / why we need it:
ansible-lint show a few small issues. This fixes.
Which issue this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged): fixes #
Special notes for your reviewer:

Thanks for the PR.We will include this in the next release.


[Godot 4.0] Shader only works if the mesh is pointing towards Z+

Mesh pointing towards positive Z:

Mesh pointing towards negative Z:

Changing
vec3 I = normalize(vertexW - CameraPosition);
to
vec3 I = -normalize(vertexW - CameraPosition);
Makes it work pointing towards -Z.
Pointing it towards X- or X+ also makes it not work.

Hello @kimamb ,
I am aware of the issue, and already working on the fix, I am trying to simplify the new implementation so it can perform well in large scenes.

Thank you very much.
I am looking forward for the update!

Thank you for using it.

@kimabjorkede Hi, the new update is UP, can you try it?

Now its like this:
https://user-images.githubusercontent.com/70962730/196826390-8692fa8b-62f1-4961-9e1f-61429b630343.mp4

Yup my friend and I are facing this very same issue. Fixed the hints for godot 4 but the shader seems broken on certain meshes for some reason. The middle building works perfectly but the ones to the side have the exact issue as the above video. Exporting glb from blender? same issue. It works on a csgmesh > planemesh though.

Yup my friend and I are facing this very same issue. Fixed the hints for godot 4 but the shader seems broken on certain meshes for some reason. The middle building works perfectly but the ones to the side have the exact issue as the above video. Exporting glb from blender? same issue. It works on a csgmesh > planemesh though.

afaik it had to do with the mesh object origin point.


input file validation is not working as expected

I have included a file validation criteria for .conf file with Annotated and FlyteMetadata.
However, in production, the file regex doesn't work as intended.
Code snippet:
@workflow
def shasta(
    input_dir: LatchDir,
    config: Annotated[
            LatchFile,
            FlyteMetadata(
                {
                    "rules": [
                        {
                            "regex": "(.conf)$",
                            "message": "Only .conf extensions are valid",
                        }
                    ]
                }
            ),
        ],
) -> (LatchFile, LatchDir):

Full code: https://github.com/nahid18/shasta/blob/main/wf/init.py
Production tool to check the issue live: wf.shasta v1.0.8 workflow on LatchBio

What do you mean by 'doesn't work as intended'? Please provide
(1) What you wanted to happen (what you intended)
(2) What actually happened


Official package support from Archlinux and NixOS

Ponyc on official Archlinux packages . I will update ponyc for Archlinux later. The Nix Package is also working but only for Darwin yet. See https://hydra.nixos.org/jobset/nixpkgs/trunk#tabs-jobs. I am working on it

The "we have" are official packages from us that are installable with ponyup.
Also any 3rd party package is not official and isn't supported by us. Please update the language to indicate this is a 3rd party option that isn't supported by the pony team.

If you would like to discuss where to add "other packages from 3rd parties" we can do that, but in the officially supported options page isn't the place for it.
Additionally, a 3 year old arch package isn't something I'm will to put advertise.
I'd be good with adding a "3rd party packages" page and linking it after "installation" from the main README.md. But 3rd party packages do not belong on the INSTALLATION page as is is written as "how to install official packages".
There's no guarantee what is in 3rd party packages and we do not want there to be any confusion as to their source. I'm closing this PR. Feel free to open a new PR for 3rd party packages when you something that is up to date in NixOS or Arch.
Re: NixOS, I believe that something already exists. @redvers can speak to that.


RenderWindow disables GL_DEPTH_TEST in draw()

While trying to use a RenderWindow for SFML and OpenGL 4.4 rendering, the RenderTexture::draw() function appears to disable GL_DEPTH_TEST, so I have to re-enable it myself after all the SFML rendering has been done.
At the very least, this should be mentioned in the documentation, but if possible, this should be handled in some kind of cleanup code (maybe in display()?). Other than this, resetGLStates() seems to suffice.
Granted, the guide recommends using glPushAttrib() and glPopAttrib(), which may solve this problem, but these have been deprecated. Perhaps it's now appropriate to have some sort of counterpart to resetGLStates() that does cleanup after SFML rendering is done.

SFML uses a set of OpenGL states for its own drawing, and leaves them active after it has finished for obvious reasons; GL_DEPTH_TEST is just one of them, there's nothing special about it.
How to mix sfml-graphics and your own OpenGL code is explained in the tutorial, documentation and in various forum posts. Please read these resources carefully before posting, and if you do, please do it on the forum. This tracker is for confirmed bugs and tasks.


CSV stringify module - basic structure

Basic files (tests and module) created and configured.
Module connected to library.

Landed to csv branch in https://github.com/metarhia/common/commit/edd2ad1f1d9cc622115ee2294043a3def457a21c


Show how many times a specific decoding function has been called

Currently, floss can identify the decoding functions in a binary and prints them with offset and score while running usng -v flag. Now, it's maybe useful to know that how many times a functions has been called which may better indicate several decoding routine present in the binary under analysis.

Hello , could you assign this issue to me .  I have kind of made some changes , could you check it ?

You got it. Maybe @r0ny123 can specify a bit on what to display: number of xrefs to a function, number of emulated calls, etc. Curious to see what you display here.

@r0ny123 could you please specify me what to do next ?

@mr-tz @r0ny123 Could you please specify on what i need to do next now ?

Let's start on what you've done above. What were your thoughts and how did you go about them?

When I thought about adding a feature to FLOSS to track how often each decoding function is called, I had a few key ideas in mind:

I wanted to give people using FLOSS more insight into which decoding functions the binary file uses the most. This information could help someone figure out which functions play a big role in hiding or changing data, making their analysis more focused and efficient.

Since FLOSS already finds and runs these decoding functions by simulating (or "emulating") the program, I thought about keeping track of each time a function is called. For this, I used a dictionary function which would do the job well.

My goal was to add this new tracking feature without altering too much of FLOSS's existing code. This way, we can improve FLOSS without risking the stable parts of the program that already work well.

I see these ideas as just the beginning of making FLOSS even better. By introducing this feature thoughtfully, I aimed to make FLOSS not just more powerful for advanced users, but also more helpful and accessible for everyone, aligning with the tool's main goals and offering real benefits to its users.
@mr-tz Please correct me if i missed something.

If you already have some code feel free to open a PR, maybe it's easier to discuss in there concretely on the implementation. I'm curious to see how your count differs from the call counts displayed in the progress bar line.

https://github.com/mandiant/flare-floss/pull/958 - Please check this PR

@mr-tz could you provide me with the changes required or is it ok ?

@r0ny123 Ok , I'll work upon it .

@r0ny123, to clarify: do you mean how often a function is called as analyzed via static analysis (I.e. all the code cross-references to a function)?

Yes, cross references(I should have mentioned it).

@r0ny123  could you please provide me with the command , to get this type of flare floss results .

Run floss with -v flag.

@mr-tz @r0ny123 ?

@mr-tz @r0ny123 could you tell me if the count values like this are correct ?

https://github.com/mandiant/flare-floss/pull/968 please check this pr @mr-tz @r0ny123

This is the new output as you suggested .

That looks great. @r0ny123, does that meet your expectations?
Maybe instead of calls we use xrefs to (depending on the implementation)?

@r0ny123 Thankyou!!

Closing as already fixed with https://github.com/mandiant/flare-floss/pull/978.


Support audit

Needs to be added to the kubeadm deployment too?

@woopstar  support kubeadm

ci check this

ci passed.

Please add a new PR with the fixes :)

Thanks @mirwan

@woopstar roger that, on my way.
@riverzhang you're welcome


turn off auto notify in debug mode

just like handlePromiseRejections, prefer redbox in dev mode so it doesn't send the bug to bugsnag

Thanks for the contribution, @evollu. The current behavior in debug mode should be to do both -- notify bugsnag and show the red box. Is that not happening? In general, autoNotify being on by default avoids confusion during initial setup where a user may not understand why errors are not immediately being caught, though the option is easily changed.

It is just annoying to receive error reporting email in while developing. Overriding default config is easy so you can close this if this is expected behavior

@evollu It is recommended that after confirming that the bugsnag is working in development, to change this setting so you won't get any more development notifications.
configuration.notifyReleaseStages = ['beta', 'production'];

Ah, thanks for the clarification @evollu. This behavior is intended but we can revisit if it becomes a usage problem.
@wordofchristian Thanks, that's also a good point. Maybe its something we can clarify in the initial usage guide.
Closing for now.


iOS Native SDK intialization doesn't work any longer

Description:

Notification opened event is not triggered when SDK is initialized in AppDelegate.m
self.oneSignal = [[RCTOneSignal alloc] initWithLaunchOptions:launchOptions
                                                           appId:@"APP_ID"
                                                        settings:@{kOSSettingsKeyInFocusDisplayOption: @(OSNotificationDisplayTypeNotification), kOSSettingsKeyAutoPrompt: @NO}];
  }

Environment

React Native: v0.42.0
React Native OneSignal: v3.2.3
Steps to Reproduce Issue:

Install the OneSignal SDK
Initialize the SDK in the iOS AppDelegate
Attach opened event listener in index.ios.js
Receive a push notification
Click on the notification when app is in background/closed state
opened event not fired

@sachinB94 Thank you for reporting this, I was able to reproduce and fix the issue thanks to all of the helpful information you've provided. Great job troubleshooting! This should now be fixed in the new update (3.2.4)


New Bidder:ehealthcaresolutions

🏷 Type of documentation

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

📋 Checklist

[ ] Related pull requests in prebid.js or server are linked -> Paste link in this list or reference it on the PR itself
[x] For new adapters check [submitting your adapter docs] -> https://github.com/prebid/Prebid.js/pull/12384

I suspect that the inclusion of tapnative here is accidental. Please remove.
And ehealthcaresolutions is in the wrong directory -- please move to /dev-docs/bidders

@bretg we have move ehealthcaresolutions to dev-docs/bidders.
we are using same fork which we used for tapnative. so how you are suggesting to remove tapnative from here?

we are using same fork which we used for tapnative. so how you are suggesting to remove tapnative from here?

This is a git thing. You'll have to research it -- basically, just commit only the files you've changed into the fork.

we are using same fork which we used for tapnative. so how you are suggesting to remove tapnative from here?

This is a git thing. You'll have to research it -- basically, just commit only the files you've changed into the fork.

HI @bretg ,
updated from master, can you please check and merged to master.
thanks.


License and a bit more readme.

Thanks for sharing this.  Could you go ahead and please include an appropriate license with this repository?
And perhaps expand the readme a bit more to include some more context, and a declaration of "For Educational Purposes Only"?  (I added that to the repo descriptions already as well.)
Thanks!

Sure thing! I've added an MIT license to the repository, and expanded the readme file.


Enable etcd-dump-logs tool to decode kubernetes data objects in WAL log

etcd-dump-logs now is a great tool for wal log analysis. However, some kubernetes data in wal log is stored in a binary storage representation (starting kubernetes 1.6+). Output from etcd-dump-logs could not reveal kubernetes object. If we could provide an option for etcd-dump-logs to decode kubernetes object data at the same time of wal log dump, it would be very helpful for kubernetes users.
@jpbetz

/assign @wenjiaswe

it seems that this should not belong to etcd repo. Or we need to provide a generic way to hook a decoder into the wal analysis tool.

/assign

Addressed by #9790.


Elements >Counter > Selecting light theme & color Variant light outline is not display.

Describe the bug
Selecting light theme & color Variant light outline is not display.
Selecting dark theme & color Variant dark+,- icon is not display
Element Collapse Click on toggle element open popup alignment issue.
To Reproduce
Steps to reproduce the behavior:

Go to 'Elements'
2.Click on 'Counter '
3.Click on 'Default'

Screenshots
.

Desktop (please complete the following information):
-OS: [Windows 10 Enterprise]
-Browser [ edge]
-Version [ 125.0.2535.92]
Smartphone (please complete the following information):NA

Device: [e.g. iPhone6]
OS: [e.g. iOS8.1]
Browser [e.g. stock browser, safari]
Version [e.g. 22]

Additional context
Add any other context about the problem here.

Completed -

Version 1.1.7


[Danger] Ensure node 4 builds fine on travis

Summary
Danger was breaking on the node4 CI runs - https://travis-ci.org/facebook/jest/jobs/190225150
This replaces the array includes with a lodash one, which comes from Danger's dependencies.
Test plan
If this greens, then we're 👍

lodash.includes should be an explicit dependency of the package.json file in the danger folder.

Oh yeah, good thinking 👍


How to train Quadruple Model, pretty confused. is it possible to fine tune it based on your model, how train data looks like?

@yangheng95, first of all thank you for your amazing work.
Inspired from your work I want to train Quadruple model:
1)How input data looks like in training stage?
Is this below correct?
{"text": "keyboard and mouse pad seem fine , but overall it seems strangely slow .", "labels": [{"aspect": "keyboard", "opinion": "fine", "polarity": "positive", "category": "KEYBOARD#DESIGN_FEATURES"}, {"aspect": "mouse pad", "opinion": "fine", "polarity": "positive", "category": "KEYBOARD#DESIGN_FEATURES"}, {"aspect": "NULL", "opinion": "slow", "polarity": "negative", "category": "LAPTOP#GENERAL"}]}

How train this model in Hugging face way, as I saw couple of spaces as examples here, is it possible to fine tune them: https://huggingface.co/spaces/yangheng/PyABSA

Should I follow here to train the model: https://github.com/yangheng95/PyABSA/tree/v2/examples-v2/aspect_opinion_sentiment_category_extraction
rely on your support and guidance!

This model is only tested and available for pyabsa. To train your own model, you can try to annotate your own dataset and use the training script in https://github.com/yangheng95/PyABSA/tree/v2/examples-v2/aspect_opinion_sentiment_category_extraction, ie., multitask_train.py

Thank you so much @yangheng95  for prompt response.
If I want to annotate my own dataset, is it should look like that:
{"text": "keyboard and mouse pad seem fine , but overall it seems strangely slow .", "labels": [{"aspect": "keyboard", "opinion": "fine", "polarity": "positive", "category": "KEYBOARD#DESIGN_FEATURES"}, {"aspect": "mouse pad", "opinion": "fine", "polarity": "positive", "category": "KEYBOARD#DESIGN_FEATURES"}, {"aspect": "NULL", "opinion": "slow", "polarity": "negative", "category": "LAPTOP#GENERAL"}]}
If not, can you please provide one example snapshot how training data should look like?
Much appreciate your support on that

Thank you so much @yangheng95 for prompt response.
If I want to annotate my own dataset, it should look like that:
{"text": "keyboard and mouse pad seem fine , but overall it seems strangely slow .", "labels": [{"aspect": "keyboard", "opinion": "fine", "polarity": "positive", "category": "KEYBOARD#DESIGN_FEATURES"}, {"aspect": "mouse pad", "opinion": "fine", "polarity": "positive", "category": "KEYBOARD#DESIGN_FEATURES"}, {"aspect": "NULL", "opinion": "slow", "polarity": "negative", "category": "LAPTOP#GENERAL"}]}
If not, can you please provide one example snapshot how training data should look like?
Much appreciate your support on that

Yes

Hi, thanks a lot for your work.
Can you provide also for me a snapshot in order to fine tune the Quadruple model?? I'm very interesting on that.

@lorisdiquilio Please refer to: https://github.com/yangheng95/PyABSA/blob/v2/examples-v2/aspect_opinion_sentiment_category_extraction/multitask_train.py

Ok, thanks a lot. Once I trained the model with this structure mentioned:
{"text": "keyboard and mouse pad seem fine , but overall it seems strangely slow .", "labels": [{"aspect": "keyboard", "opinion": "fine", "polarity": "positive", "category": "KEYBOARD#DESIGN_FEATURES"}, {"aspect": "mouse pad", "opinion": "fine", "polarity": "positive", "category": "KEYBOARD#DESIGN_FEATURES"}, {"aspect": "NULL", "opinion": "slow", "polarity": "negative", "category": "LAPTOP#GENERAL"}]}
how can i predict on the new sentences?

You can refer to the example:
https://github.com/yangheng95/PyABSA/blob/v2/examples-v2/aspect_opinion_sentiment_category_extraction/inference.py

I was able to train the model thanks to @yangheng95  guide! Thanks


Maven standard dependencies should take precedence over managed dependencies

Managed dependencies are not real dependencies so they should not take precedence over standard dependencies.
Dependency management is used to control the versions of artifacts used in transitive dependencies. https://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html#Dependency_Management
Also, version requirements in managed dependencies are only referred when the requirement is not defined for that dependency in standard dependencies section.

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

Project coverage is 65.50%. Comparing base (804589a) to head (a233f52).
Report is 3 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #1000      +/-   ##
==========================================
+ Coverage   64.47%   65.50%   +1.03%
==========================================
  Files         148      149       +1
  Lines       12088     9518    -2570
==========================================
- Hits         7794     6235    -1559
+ Misses       3843     2830    -1013
- Partials      451      453       +2

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

Can you just check this against what I believe is the section of the docs I referred to when I did this?

a and c both are declared as dependencies of the project so version 1.0 is used due to dependency mediation. Both also have runtime scope since it is directly specified.
b is defined in B's parent's dependency management section and since dependency management takes precedence over dependency mediation for transitive dependencies, version 1.0 will be selected should it be referenced in a or c's POM. b will also have compile scope.
Finally, since d is specified in B's dependency management section, should d be a dependency (or transitive dependency) of a or c, version 1.0 will be chosen - again because dependency management takes precedence over dependency mediation and also because the current POM's declaration takes precedence over its parent's declaration.

I assume my mistake is in not understanding what's being referred to is triggered in specific cases which are not true (most of the time at least) for the scanner when it's reading a pom, but would like to have that confirmed.

I think the dependency management in root pom.xml takes precedence over the dependencies in pom.xml of transitive dependencies.
However, since we are only scanning the root pom.xml with direct dependencies only, dependencies take precedence over the managed dependencies, and this is also what mvn does.


with_terminal broken

I think https://github.com/JuliaPluto/PlutoUI.jl/pull/140 broke with_terminal for me. As far as I can tell, the problem is that https://github.com/JuliaPluto/PlutoUI.jl/blob/9948cb4f30cfabb3f98f376a84395d57ff256004/src/TerminalNotebook.jl#L112-L113 needs to say something like
ansi_up = new AnsiUp;
container.innerHTML = ansi_up.ansi_to_html(txt);

Problem description
I saw this on Chrome 97 via Binder, so I couldn't test the fix. Here is what I saw.

(The behavior on latest version of PlutoUI is the same as in the screenshot)
On previous version of PlutoUI, it works.

Huh, strange.. But good catch!
Can you try it out and make a pull request? :)

It might take me quite a while to get around to that, unfortunately.
On Wed, Jan 26, 2022, 7:47 PM Michiel Dral @.***> wrote:

Huh, strange.. But good catch!
Can you try it out and make a pull request? :)
—
Reply to this email directly, view it on GitHub
https://github.com/JuliaPluto/PlutoUI.jl/issues/196#issuecomment-1022820429,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AA7OTJ7GG4AP542WNMY4JB3UYC54NANCNFSM5M4RV2CA
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you authored the thread.Message ID:
@.***>

with_terminal() has stopped working entirely for me: I cannot bring it to produce any output.

Hey @dojt! Could you give a little bit more info about your setup? fwiw, I have been finding the following on my end at least:
Linux x86_64
Julia 1.7.1
Pluto main: https://github.com/fonsp/Pluto.jl/commit/143cae813478b18499b01dfa99e394fbdaef2dec
Pluto release: v0.17.7
PlutoUI main: https://github.com/JuliaPluto/PlutoUI.jl/commit/eb8b13ce97cbb92fe6e259d4169afbe657a82e0a
PlutoUI release: v0.7.32

Pluto // PlutoUI
main
release

main
✅
✅

release
❌
❌

So I would test again on the main branch of Pluto if you haven't tried it out already!

Can you guys try this from main branch? Should be fixed now

I checked on binder.plutojl.org, and it works! (For now, one must remember to explicitly update PlutoUI to latest version). Thank you :)
One thing that still bothers me a little is that if the AnsiUp fails to load for any reason (e.g. the user has no internet connection), with_terminal will stop working entirely; there is no graceful degradation or even notification to the user that something is wrong. Hopefully, that happens rarely.

Yeah.. Next step is just embedding ansiUp in the notebook

One thing that still bothers me a little is that if the AnsiUp fails to load for any reason (e.g. the user has no internet connection), with_terminal will stop working entirely; there is no graceful degradation or even notification to the user that something is wrong. Hopefully, that happens rarely.

This is also fixed now!


Fix attribute parsing

This PR fixes Attributes on line preceding the function are not parsed.

Function comment now are not parsed when any attribute is present

Function comment now are not parsed when any attribute is present

This is not related to this PR, the error exists in the latest release as well.


TODO: Documentation for z3cform widget in README

documentation of z3cform widget is missing in README.rst.

I'll see if I can add some info there.


[ALLUXIO-1819] Used diamond operator instead of Guava's shorthand

https://alluxio.atlassian.net/browse/ALLUXIO-1819
This is JIRA is still work in progress and needs more PRs.

LGTM

Jenkins, test this please

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/9480/
Test PASSed.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/9481/
Test PASSed.


训练模型报错

我用自己的数据集训练模型
!bash tools/dist_train.sh configs/agilegan/agile_transfer_photo2cartoon256x256_zplus_lpips0.5_freezeD5_ada_bs4x2_lr_2e-3_1600iter.py 1 --work-dir ./work_dirs/experiments/experiments_name

Traceback (most recent call last):
File "tools/train.py", line 161, in
main()
File "tools/train.py", line 157, in main
meta=meta)
File "/content/mmgeneration/mmgen/apis/train.py", line 208, in train_model
runner.run(data_loaders, cfg.workflow, cfg.total_iters)
File "/content/mmgeneration/mmgen/core/runners/dynamic_iterbased_runner.py", line 285, in run
iter_runner(iter_loaders[i], **kwargs)
File "/content/mmgeneration/mmgen/core/runners/dynamic_iterbased_runner.py", line 215, in train
outputs = self.model.train_step(data_batch, self.optimizer, **kwargs)
File "/content/mmgeneration/mmgen/core/ddp_wrapper.py", line 123, in train_step
output = self.module.train_step(*inputs[0], **kwargs[0])
File "/content/MMGEN-FaceStylor/agilegan/transfer.py", line 414, in train_step
loss_gen, log_vars_g, source_results = self.get_gen_loss(data_dict)
File "/content/MMGEN-FaceStylor/agilegan/transfer.py", line 121, in get_gen_loss
loss = loss_module(outputs_dict)
File "/usr/local/lib/python3.7/dist-packages/torch/nn/modules/module.py", line 722, in _call_impl
result = self.forward(*input, **kwargs)
File "/content/mmgeneration/mmgen/models/losses/gen_auxiliary_loss.py", line 261, in forward
**kwargs)
File "/content/mmgeneration/mmgen/models/losses/gen_auxiliary_loss.py", line 104, in gen_path_regularizer
only_inputs=True)[0]
File "/usr/local/lib/python3.7/dist-packages/torch/autograd/init.py", line 192, in grad
inputs, allow_unused)
RuntimeError: module 'torch.backends.cudnn' has no attribute 'allow_tf32'
Traceback (most recent call last):
File "/usr/lib/python3.7/runpy.py", line 193, in _run_module_as_main
"main", mod_spec)
File "/usr/lib/python3.7/runpy.py", line 85, in _run_code
exec(code, run_globals)
File "/usr/local/lib/python3.7/dist-packages/torch/distributed/launch.py", line 261, in
main()
File "/usr/local/lib/python3.7/dist-packages/torch/distributed/launch.py", line 257, in main
cmd=cmd)
subprocess.CalledProcessError: Command '['/usr/bin/python3', '-u', 'tools/train.py', '--local_rank=0', 'configs/agilegan/agile_transfer_photo2cartoon256x256_zplus_lpips0.5_freezeD5_ada_bs4x2_lr_2e-3_1600iter.py', '--launcher', 'pytorch', '--work-dir', './work_dirs/experiments/experiments_name']' returned non-zero exit status 1.

+1

+1


Auto completion gets blocked by helper in strings

When writing NodePaths or other kind of strings, the helper shows up to demonstrate the use of the current function. And it's very annoying. I've lost count on how many times I couldn't use the auto completion feature because it switched to the helper. Just try to get_node by script, it's way harder than it should.

I'm unable to fully understand the issue, can you provide a screenshot?

It should show up "Main menu", "Main menu/something", etc. It does show up at times, but doesn't at others. Very strange. A simple way to fix it would be that no helper is shown after the ".

I think this shows problem.

I tested for get_node("Main  with current master.
It shows helper (with white box) but changed to node path suggestion list within a second.
but anyway, my demo gif is related in somehow, I guess.

First of all thank you for your report and sorry for the delay.
We released Godot 3.0 in January 2018 after 18 months of work, fixing many old issues either directly, or by obsoleting/replacing the features they were referring to.
We still have hundreds of issues whose relevance/reproducibility needs to be checked against the current stable version, and that's where you can help us.
Could you check if the issue that you described initially is still relevant/reproducible in Godot 3.0 or any newer version, and comment about it here?
For bug reports, please also make sure that the issue contains detailed steps to reproduce the bug and, if possible, a zipped project that can be used to reproduce it right away. This greatly speeds up debugging and bugfixing tasks for our contributors.
Our Bugsquad will review this issue more in-depth in 15 days, and potentially close it if its relevance could not be confirmed.
Thanks in advance.
Note: This message is being copy-pasted to many "stale" issues (90+ days without activity). It might happen that it is not meaningful for this specific issue or appears oblivious of the issue's context, if so please comment to notify the Bugsquad about it.

This doesn't appear anymore in 3.1 master and 2.1.5

Cool, thanks !


Configurable polling?

I was wondering if allowing the polling interval of clipmenud to be configured was within the scope of this project?
Currently I have:
--- clipmenu/clipmenud
+++ clipmenu/clipmenud.new
@@ -1,11 +1,29 @@
 #!/bin/bash

+wait=1
+
+while getopts ":w:" opt; do
+  case $opt in
+    w)
+      wait="$OPTARG"
+      ;;
+    \?)
+      echo "Invalid option: -$OPTARG" >&2
+      exit 1
+      ;;
+    :)
+      echo "Option -$OPTARG requires an argument." >&2
+      exit 1
+      ;;
+  esac
+done
+
 cache_dir=/tmp/clipmenu.$USER/
 mkdir -p -m0700 "$cache_dir"

 declare -A last_data

-while sleep 1; do
+while sleep "$wait"; do
     for selection in clipboard primary; do
         if type -p xsel >/dev/null 2>&1; then
             data=$(xsel --"$selection"; printf x)

Your thoughts?

1 second was chosen as a balance between catching everything (if you copy two things within 1 second, probably the first one was a mistake) and keeping wakeups low.
If you can convince me that there's some legitimate reason to change it, then sure. I'm not sure what that would be, though.

Isn't there an inotifywait equivalent for clipboard changes? That would be the sane way forward. :)

If you think the X spec is sane and would include such a thing, you'd be sadly mistaken. As far as I know the X clipboard provides no notify interface (which would be required for that).

Well my personal use case was that I needed/wanted to reduce the sleep to .5 since I was copying and switching windows pretty quickly with key bindings and several times my selection hadn't made it to /tmp yet. Not a huge deal, but @ .5 it hasn't happened since. Obviously that would be to much for some people; hence, the configuration (with a default of 1).

Let me do some profiling and see what the performance impact of reducing the sleep would be.

@cdown thanks


CI: pin OpenBLAS to specific build in macOS job to avoid gges issue

xref gh-16949. This doesn't fix the root cause of the problem, but stops the CI job from failing.
[skip azp] [skip circle]

This worked, the macOS tests (meson) build is green now.

Argh, this is not correct. It fixes CI, but breaks package resolution on platforms other than macOS x86-64:
nothing provides requested openblas ==0.3.21 openmp_h2bb6d6c_

I will revert this, and resubmit once I have the right incantation to make it cross-platform.

I forgot, this can't actually work because conda/mamba don't support selectors, only conda-build does: https://github.com/conda/conda/issues/8089


fix(lnd): ensure lnd start errors are displayed

Description:
Ensure that lnd errors get displayed properly.
Motivation and Context:
LND startup errors are not displaying correctly
How Has This Been Tested?
From the wallet launcher, try connecting to a node that is offline
Types of changes:
Bug fix
Checklist:

[x] My code follows the code style of this project.
[x] I have reviewed and updated the documentation accordingly.
[x] I have read the CONTRIBUTING document.
[ ] I have added tests to cover my changes where needed.
[ ] All new and existing tests passed.
[x] My commits have been squashed into a concise set of changes.

Coverage remained the same at 20.276% when pulling 38ea8cc5f499a27e622c20fc906ef3b1a4c32589 on mrfelton:fix/lnd-start-errors into 464ba196cedf66ccd51df54c7829628bb569ac79 on LN-Zap:next.


Test Duplicate

while duplicating the test, the name of the test would be different or same..?
as mentioned in SRS that Test names should be Unique...but duplicating means the copy of particular test.

While duplicating the test, it will open a dialog prompting the user to enter a Name for the new Duplicated Test (Same as Create Test). Hence the Test Name will be always unique.


Fix rocksdb using

Signed-off-by: Andrew Nikitin<EMAIL_ADDRESS>

The branch was updated based on https://github.com/anikitinDSR/indy-plenum/tree/issue-1546 directly.


[HIGH] ManageProjectList

Display/Open Projects page

[ ] Add functionality in ARA
[ ] Add NRT

Moved to another project


Site down

Hi, the site seems to be down now. Would it be possible to put it back up?

hi @Pyrodash, the site is no longer actively maintained.


Remove TRA references

Context
We’re removing all references to ‘the Teacher Regulation Agency’ / ‘the tra’ / ‘we’ for accessibility reasons
Changes proposed in this pull request
A number of changes across the forms
Guidance to review
Link to Trello card
https://trello.com/c/a37zsLNY/1156-remove-references-to-the-tra
Checklist

[ ] Attach to Trello card
[ ] Rebased main
[ ] Cleaned commit history
[ ] Tested by running locally

Thanks @paulodeon - looks good. We've got some content changes upcoming for 1) the declaration, and 2) the service 'exit' pages, but we'll cover these in a design history + separate tickets

@paulodeon One more thing - we've also updated the footer throughout the service to remove mentions of the TRA. (Just realised I miss this from the Trello ticket.) Should I make a separate ticket for it, or want to include it as part of this work?

Created a ticket for the footer here: https://trello.com/c/84NFudI7/1169-update-the-footer


fix(docs): gradle compile config depreciation

PR facebook/react-native#20767 bumped the version of the Android
Gradle Plugin to v3 which uses the newer Gradle dependency
configurations implementation and api which make compile
obsolete.
PR facebook/react-native#20853 covered the link command.
Using compile will result in a warning message during app build and
compile will be eventually removed by Gradle.

@joeferraro Could you merge this PR ? 🙏
Note: Tell me if you need a maintainer.

I have forked the repo here: https://github.com/safaiyeh/react-native-cookie-store
We can create issues and PRs there to continue the development of the project.


Add views (day, week) to the calendar

Add the possibility to use different views for the calendar.
Desired views would be in prioritized order:
*Day
*Week
😀👍

We're closing old issues so we can get back to actively maintaining the extension. Feel free to reopen if this is still an issue for you.


Kernel crash in optimizer.apply_gradient for complex-valued gradients

TensorFlow is able to correctly compute gradients for complex-valued variables. However, the Keras3 optimizers do not seem to be able to correctly apply complex-valued gradients. This worked with Keras 2.
Here is a code snippet that works in TF2.15, but leads to a Kernel crash with Keras 3.7 and TF 2.18.
The crash is caused by the function optimizer.apply_gradients.
import tensorflow as tf

# Complex-valued variable
x = tf.Variable(tf.complex(3., 2.), trainable=True)
optimizer = tf.keras.optimizers.SGD()
with tf.GradientTape() as tape:
    loss = tf.abs(x)**2
grads = tape.gradient(loss, tape.watched_variables())
optimizer.apply_gradients(zip(grads, tape.watched_variables()))
print(x)

# Real-valued variable equivalent
x_r = tf.Variable(3., trainable=True)
x_i = tf.Variable(2., trainable=True)
optimizer = tf.keras.optimizers.SGD()
with tf.GradientTape() as tape:
    x = tf.complex(x_r, x_i)
    loss = tf.abs(x)**2
grads = tape.gradient(loss, tape.watched_variables())
optimizer.apply_gradients(zip(grads, tape.watched_variables()))
print(tf.complex(x_r, x_i))

Hi @jhoydis -
Thanks for reporting the issue. I am not able to reproduce any kernel crash using complex-valued gradient with Keras 3.7 and TF 2.18 version.
Attached gist for your reference.

Hi @mehtamansi29,
Thanks for looking into this so rapidly.
When I run this code on GPU (using Colab and a T4 GPU instance) the kernel crashes.

Hi @jhoydis -
I am also reproduce this issue on GPU (using Colab and a T4 GPU instance). After seeing logs from crash runtime it seems that TensorFlow is overriding a memory allocation setting due to the TF_FORCE_GPU_ALLOW_GROWTH environment variable being set.
And also TensorFlow build might be missing some CPU optimization flags.
I0000 00:00:1733326291.211008 13282 gpu_device.cc:2022] Created device /job:localhost/replica:0/task:0/device:GPU:0 with 13949 MB memory: -> device: 0, name: Tesla T4, pci bus id: 0000:00:04.0, compute capability: 7.5
2024-12-04 15:31:31.210156: W tensorflow/core/common_runtime/gpu/gpu_bfc_allocator.cc:47] Overriding orig_value setting because the TF_FORCE_GPU_ALLOW_GROWTH environment variable is set. Original config value was 0.
To enable the following instructions: AVX2 FMA, in other operations, rebuild TensorFlow with the appropriate compiler flags.

We will dig into the issue and update here.

Hi @jhoydis
I could repro the crash with TensorFlow 2.18 but when I changed the TensorFlow version to 2.15 and it didn't crash anymore. So this is probably a TensorFlow related issue, not Keras.

@jhoydis My bad! My runtime wasn't set to T4 GPU and that's probably why the issue wasn't reproduced.
Have you tried using Keras Variable instead of tf.Variable?

@SamanehSaadat I have the feeling that Keras Variable does not allow for a complex datatype:
The following code throws a type error "TypeError: Cannot convert (3+1j) to EagerTensor of dtype float":
x = tf.keras.Variable(tf.complex(3., 2.), trainable=True)


Dodged Bars

If I have lots of dodged bars in a Geom.bar plot, the drawn plot is too zoomed in

plot should look like this:

To reproduce:
x=[0,1,0,1,0,1,0,1]
y=[0.9722222222222222,0.027777777777777776,0.9871111111111112,0.012888888888888889,0.6737777777777778,0.32622222222222225,0.7188888888888889,0.2811111111111111]
plot(x = x, y=y, Geom.bar(position=:dodge),
     color = [1,1,2,2,3,3,4,4],
     Scale.color_discrete(), Guide.colorkey("Chain"),
     Guide.xlabel("Value", orientation=:horizontal),
     Guide.ylabel("Density", orientation=:vertical),
     Guide.title(sim.names[i]),Theme(lowlight_opacity=0.5))

I think that using Scale.x_discrete helps to get the right zoom.

Right, Scale.x_discrete will work, but it should also should work as written. It turns out the discrete version only works via kludge that I've forgot to take care of. I'll do so.

this seems to work now.  so i'll close this issue.  please reopen if the problem persists.


Show slide by id on a custom button click

Hello !
How can i roll to a slide number x from a custom button event ?

Please use $GoTo or $PlayTo method.
jssor_slider1.$GoTo(index);
or
jssor_slider1.$PlayTo(index);
Note that index is zero based integer value. index = number - 1

thank you !


Move models/db to modules/db

This fixes quite a few imports to models inside modules.
In addition, it is the conceptually better fitting place for a package that has no application-specific dependencies but a lot of dependents.

Why does the linter fail, even though my local make fmt doesn't change anything?

Not sure about this. The idea was that modules would not be dependent on db or the models.
Why does this help?

In theory, I absolutely agree.
But then please explain to me why the changes between https://github.com/go-gitea/gitea/pull/22881/files#diff-fa07e296d614e796de67f7ae9268a0660b89c09b6e5f6373b4ca7bf76a20dec7 and https://github.com/go-gitea/gitea/pull/22881/files#diff-df6792f0bd4f2d349508731c08110a47e5cf0c9559f863f9bb5d7c37cd4f1240 were necessary…
Apparently, that rule wasn't kept previously.
I'm simply trying to untangle this import mess we've already produced to stay consistent with what our Docs say on how Gitea is structured.
And as I said in the body of this PR, you can even argue that modules is a better root package for this package, as it only depends on modules/settings, and nothing else. And as shown above, even a lot of already existing code in modules depends on it.

I think the db package is better to be kept in the models package, and refactor other dependencies.
The reason of putting the db package in models is that they are all database-related, while modules should do their best not touch database directly.
The purpose of defining the dependency order is to make the structure clear, and sometimes it's just difficult to strictly follow that pre-defined order.
My opinion is:

Do the best to keep the structure import order (say, just do the best, but not strictly follow)
If the db in the models is by purpose and clearer,  I  think it's good  to keep it there, while refactor other packages.
If the benefit is not big enough, keep restraint for refactoring

I drafted a refactoring guideline in #22880 (I have experiences for maintaining systems which are 10 years old and refactoring them to modern, there are some my opinions to share).

Looks like there is no difference between putting db in models or modules, so we can keep it as before.

This reefactoring seems to be unwanted.

@delvh thanks for trying though!
We should instead finish the move to make the dependency tree:
routers -> services -> models -> modules

So if a package in modules relies on models it should be moved to services or reconsidered entirely

😒 That's what this PR attempted to do in the least intrusive way.
Everything else will result in equivalent behavior, but with a lot more refactoring  work.


How to add suffix in when using "clrInput" label?

Is there a way to add a suffix or prefix when using "clrInput"?
just like below:

@vmware.com

I tried to add a 'span' in , but it doesn't work!

This is a duplicate of https://github.com/vmware/clarity/issues/3778 which is being worked on currently.
Closing as duplicate.


angular2: update typings for angular2 and angular2 router Alpha 31

@alexeagle already peer-reviewed this on our fork: https://github.com/angular/DefinitelyTyped/pull/7

:+1:

By the way, we've had a pattern of these typings lagging the public release of angular by as much as a week. On a couple occasions, users have asked us "where are the typings for the current release? Can you publish them on NPM as well" which is not the distribution pattern we are recommending.
Maybe we could discuss a faster track for this part of our release? @vvakame @basarat

Maybe we could discuss a faster track for this part of our release

Perhaps one of you can become a collab for this repo /cc @borisyankov

That sounds like a solution, @basarat.
@alexeagle will that work for you guys, or thinking of something more automated?

That would be fantastic. We will review PRs into DT/angular2/... and then
we'll be able to commit them ourselves on our own release schedule.
What can we do to ensure we don't commit anything to another directory? Is
our promise and good intention enough for you?
Thanks!
On Fri, Jul 17, 2015, 3:40 PM Boris Yankov<EMAIL_ADDRESS>wrote:

That sounds like a solution, @basarat https://github.com/basarat.
@alexeagle https://github.com/alexeagle will that work for you guys, or
thinking of something more automated?
—
Reply to this email directly or view it on GitHub
https://github.com/borisyankov/DefinitelyTyped/pull/4952#issuecomment-122437451
.

I have a rather high confidence of your abilities not to mess up anything (and/or to fix it if so) :)
If touching other definitions is a high enough concern, in future, I think we can add some step in the CI to check if files only in a single directories have changed on a given commit.
@alexeagle do you want your account added or another one?

You can add me, please. Thanks!
-Alex
On Sat, Jul 18, 2015 at 12:31 AM Boris Yankov<EMAIL_ADDRESS>wrote:

I have a rather high confidence of your abilities not to mess up anything
(and/or to fix it if so) :)
If touching other definitions is a high enough concern, in future, I think
we can add some step in the CI to check if files only in a single
directories have changed on a given commit.
@alexeagle https://github.com/alexeagle do you want your account added
or another one?
—
Reply to this email directly or view it on GitHub
https://github.com/borisyankov/DefinitelyTyped/pull/4952#issuecomment-122508754
.

You are in, Alex.
Welcome ;)

Thanks Boris, I'm looking forward to contributing to the TypeScript
ecosystem!
On Sat, Jul 18, 2015, 1:21 PM Boris Yankov<EMAIL_ADDRESS>wrote:

You are in, Alex.
Welcome ;)
—
Reply to this email directly or view it on GitHub
https://github.com/borisyankov/DefinitelyTyped/pull/4952#issuecomment-122590898
.


Add install instruction for linux users

The steps described in section "Running a sketch from Atom" does not work on linux systems as the menu entry "Install processing-java" is not available in current processing versions for linux.
However, the same can be easily achieved by adding processing-java to your executable search path. This can be done by adding the processing directory to your PATH environment variable or by adding a symlink to any existing directory within your PATH. I'd suggest adding a symlink to /usr/local/bin as it is usually already in your PATH:
sudo ln -s /path/to/processing/processing-java /usr/local/bin/

if sudo is not installed or the operation is not allowed, switch to a user that has write permissions to /usr/local/bin and run the command without sudo (or ask someone other with write permissions to do it):
ln -s /path/to/processing/processing-java /usr/local/bin/

This should work on most Linux distributions, so I'd suggest adding these notes to the README file for your package.

@theArchonius Any interest in opening up a Pull Request with the instructions? I'd be happy to merge it.


Scenario Validation Bug

The scenario validation tooltip does not give the correct message. In the screen shot below, the tool tip is messaging to the user that they need to select a damage category for the preview compute, but the real issue is with the stage damage functions.

It also appears that the live updating is not working. When we fix stage-damage functions, the validation on scenarios still reflects bad stage-damage functions.

@rnugent3 You mention that "the real issue is with the stage damage functions", but I see in the pic that the stage damage is selected. The tooltip message seems correct to me. I do need to update that validation to include the new stage damage combo that I added if the user is modeling non-failure.

I see. I am not sure that requiring a selection of damage category for optional visualization is fatal enough to be worthy of a red exclamation mark.

Thank you for updating the validation for non failure.

I revisited the images.
It looks to me like the red exclamation mark on the specific bank is signaling the same problem that the error signals in the study tree are catching and the same problem messages in red in the compute log, but the tooltip gives a message about the preview compute.

Yes, i see that too. I am on it. This is the message we want the tooltip in the editor showing. It should be consistent.

I think that is what it ultimately was doing, but the wording should be the same:

If there is something to select then we select the first one automatically:

tab validation is working better now:

I added the validation for the non failure combo:


Overhaul ECDSA signature parsing: strict DER, compact sigs, tests, lower-S

There are now 2 encoding formats supported: 64-byte "compact" and DER. The latter is strict: the data has to be exact DER, though the values inside don't need to be valid.
This means that applications that need more than strict DER as input, it needs to have a parser itself. I wish there was a better solution, but there really isn't. Any subset of BER to implement would be arbitrary, incompatible with many other applications anyway, or be very complex and nearly untestable. Despite that, a code snippet to do so (with extensive testing) is included in the contrib/ directory now.
Finally, by default, we now require non-malleable signatures (by requiring the lower-S form), but a separate function is provided to normalize a signature before verification if needed.

Added a commit that introduces a snippet for lax DER parsing (tested!).

Addressed many comments.

Added a certainly_not_der as output from the BER generator, and tests using it.

ACK


chore: fix format of input in dashboard lint script

Motivation
After further looking into why we get random dashboard diffs on __inputs it looks like downloaded dashboards have __inputs fields and the format that Grafana uses it different from the format we use in the lint script.
Maybe depends on Grafana version or when dashboard was last time updated as it does not happen for all dashboards. Tested it with our grafana instance.
Description

fix format of input in dashboard lint script
fix inputs on remaining dashboards that were not updated

:tada: This PR is included in v1.10.0 :tada:


[FEATURE]: Save stakeholders into team_user table

Summary
Instead save stakeholders inside a static JSON, save on a property inside team_user table.
Notes

Delete the stakeholders file;
Update the stakeholders endpoint.

Motivation
No need to manually update this file.

Removed "/all" from "/boards/stakeholders/all" in the backend and in the frontend. Now both sides use GET /boards/stakeholders.


OnSSET variables

New variables for OnSSET

@mvittorio-unh, I fixed some of the issues and now we're getting close to finishing this PR.
Couple of issues to get through but then we should be done
Re-defined variables
Currently you re-defined 8 variables. This is an issue since a variable must only be defined once. These are the 8 in question:
ValueError: Collected 8 errors:
  1. Duplicate item in variable codelist: Population|Electricity access|Share
  2. Duplicate item in variable codelist: Network|Electricity|Expansion Cost
  3. Duplicate item in variable codelist: Population|Connected|Grid|Existing
  4. Duplicate item in variable codelist: Population|Connected|Grid|New
  5. Duplicate item in variable codelist: Population|Connected|PV
  6. Duplicate item in variable codelist: Population|Connected|Hybrid|PV
  7. Duplicate item in variable codelist: Population|Connected|Hybrid|Wind
  8. Duplicate item in variable codelist: Population|Connected|Hydro

I could just remove the ones that you added but at least for some of them you use different units to what was already there. Please take a look to make sure that your model outputs conform to the variables and remove your variables accordingly.
End Year variables
There are still a number of variables that contain End Year. From my understanding that would just be the last value in the time series. If that's correct please remove these variables. If my assumption is not correct, just let me know.
skip-region-aggregation: true
There are a number of variables that you introduced where you put skip-region-aggregation: true. Is that on purpose? What this attributes means that this variable will be skipped for region aggregation. As we're currently implementing African regions (West Africa, North Africa, etc...) we would want to aggregated as many variables as we can. So if you remove this line our processing will attempt to aggregate the variable.
Non-sum aggregations
There are a number of variables that are maximum or minimum values. These need special aggregation as the default is to just sum values. I'd be happy to help with that if you provide me with a list of variables that you'd like to add where you would say that a summation is not the right way to compute a meaningful aggregate.
Open comments
I have closed all the comments that you addressed from my last review. However, there's still a few open ones left. Please have a look, you can answer them in the comments directly.

@mvittorio-unh, thanks for your answers via email. I've addressed all the open points mentioned above.
Unfortunately, we have a new (hopefully final) set of errors:
The following variables are used as 'weight' for aggregation but are not defined in the variable codelist:
'Final Energy|Diesel' used for 'Price|Final Energy|Diesel|Low' in: variable/energy/energy-prices.yaml
'Final Energy|Diesel' used for 'Price|Final Energy|Diesel|High' in: variable/energy/energy-prices.yaml
'Primary Energy|Electricity' used for 'Price|Primary Energy|Electricity' in: variable/energy/energy-prices.yaml
'Primary Energy|Electricity' used for 'Price|Primary Energy|Electricity|Expansion' in: variable/energy/energy-prices.yaml

these errors mean that as an aggregation weight you've used a variable that does currently not exist.
There are two possible fixes for this solution:

You take a look at the current list of variables and find one that most closely matches the weight that you would want to use
You add the missing variables to the codelists

Option 1. is preferable for me since it does not introduce new variables. If you can't find a good fit though adding new variables is totally fine as well.

@mvittorio-unh @phackstock removed the variables as per the email, and resolved a merge conflict with the original repo regarding economy.yaml variables (the fork was behind main). Please double-check it's all good there.


Add from_text method to instantiate Dataset object from string

[x] Include documentation when adding new features.
[x] Include new tests or update existing tests when applicable.

@dchandan

Looks good to me. Thanks David!


fixes #567: ( Impact on BC/DR - Data loss ) - High priority, Nodes with PointValue property cannot be successfully sink to Neo4j With Neo4j Streams Plugin

Fixes #567 in branch 5.0 (Kafka Connect)
One sentence summary of the change.
Proposed Changes (Mandatory)
A brief list of proposed changes in order to fix the issue:

fixed the bug
added tests

Same question as in #583, what do we do for AVRO messages?

As the Streams Transaction Event Handler does not support AVRO format we never thought about this. If we have to is a new implementation that we need to discuss internally.

It looks like kafka connect platform supports AVRO out of the box and we even have it documented: https://neo4j.com/docs/kafka/kafka-connect/source/#_create_the_source_instance. Nevermind, I think since that schema key is part of the message value, I think it will work with any serialization type supported by kafka connect.


Test and document ROMS-Tools for large / operational use cases

Until now, we have used ROMS-Tools for small test cases. Next, we need to test it on large and operational use cases, which might involve the correct usage of Dask clusters etc.
Test cases
Let us define three grids surrounding Iceland (with increasing dimensions nx, ny, N) for testing "operational use cases":

Grid A: nx = 1080, ny = 1080, N = 100 (Ulla's outer nest)
Grid B: nx = 5000, ny = 5000, N = 100
Grid C: nx = 5000, ny = 5000, N = 500

Notes on ROMS-Tools objects to be tested
Grid / Topography / Mask (Grid object)

Grid object does not use Dask
Grid handles 2D arrays (horizontal directions)

unless the optional grid.plot_vertical_coordinate(s=s) is called, which needs to compute the full 3D vertical coordinate system
note that grid.plot_vertical_coordinate(eta=eta)  or grid.plot_vertical_coordinate(xi=xi) only computes a slice of the 3D vertical coordinate system, so should be cheaper

Tidal Forcing
Surface Forcing
Initial Conditions
Boundary Forcing
River Forcing

Testing on Perlmutter
Jupyter Notebook run on CPU node (~250GB of memory)
Grid / Topography / Mask (Grid object)
Grid A:

[x] Grid initialization:  peak memory: 701.46 MiB, increment: 502.90 MiB, Wall time: 12.7 s
[x] grid.plot_vertical_coordinate(s=s): peak memory: 2959.17 MiB, increment: 2384.32 MiB, Wall time: 1.47 s
[x]  grid.plot_vertical_coordinate(eta=eta): peak memory: 584.21 MiB, increment: 0.60 MiB, Wall time: 294 ms

Tidal Forcing
Surface Forcing
Initial Conditions
Boundary Forcing
River Forcing


Curiosity-Driven Exploration

What is SOTA in Curiosity-Driven Exploration currently? Will you plan implement that or simple version?

The plan is to implement the version described in Curiosity-driven Exploration by Self-supervised Prediction. Not sure how much further the SOTA is regarding curiosity - let me know if you find anything interesting!

https://arxiv.org/abs/1810.12894
And maybe this can be interesting too: https://eng.uber.com/go-explore/


Send sheets to users while finalizing

Each user should get their sheet back.

We could also send the link to the players' last sheet to them instead of the contents.


User must be in master database error

Msg 5001, Level 16, State 5, Procedure sp_set_firewall_rule, Line 1 [Batch Start Line 0]
User must be in the master database.
returned when trying to add a firewall rule for ABC database using
EXECUTE sp_set_firewall_rule @name = N'ContosoFirewallRule',
@start_ip_address = '<IP_ADDRESS>', @end_ip_address = '<IP_ADDRESS>'
from SQL management studio 17.5

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

ID: 79891897-a11e-6e20-9d41-e4fbbb84311e
Version Independent ID: c8317b35-e80a-7f5d-51bf-7a26b2279595
Content: Azure SQL Database and Data Warehouse firewall rules
Content Source: articles/sql-database/sql-database-firewall-configure.md
Service: sql-database
GitHub Login: @VanMSFT
Microsoft Alias: vanto

@TJHAutoLtd The T-SQL as you have it detailed above is going to return an error because spsetfirewallrule does not exist. The correct name for this SProc is: sp_set_firewall_rule
EXECUTE spsetfirewallrule @name = N'ContosoFirewallRule', @startipaddress = '<IP_ADDRESS>', @endip_address = '<IP_ADDRESS>'
Msg 2812, Level 16, State 62, Line 3
Could not find stored procedure 'spsetfirewallrule'.
Please update your T-SQL statement to reflect the correct SProc reference.

As per my first comment I had indeed used the correct sp_set_firewall_rule which is also detailed on this page in the example, I did not use "spsetfirewallrule" which is also why you have a different error message than the one I received and posted about above?

I should add that I am connected using SQL authentication and leaving all other connection parameters as default, this rule did work but I now have 6 db that all show the same error when attempting to set db - level firewall rules

having reviewed all the information I have found that it was not entirely clear that the SPoc in this instance should have been sp_set_database_firewall_rule, command has now run successfully and i'll update my notes

@TJHAutoLtd We will now proceed to close this thread. If there are further questions regarding this matter, please comment and we will gladly continue the discussion.


Feature/IndexElicitation-&-testing-report-for-case-survillence

Added a new reporting dataset for showing no of clients elicited & tested from index clients of a particular cohort

These changes are in a previous PR with 3 files changed

Hey Mary, oh yeah, I think I created the branch in the other PR from this one. Should be all good once I merge.


Clear cache for specific file

Hello,
How to clear cache for specific file ? (specific url)

You should be able to clear for a specific URL by using the getUrlSuffix on the URL
https://github.com/lau1944/just_audio_cache/blob/d202c77ca8e42c763a8a3f6cc710cdcdfc3a54b8/lib/src/parser.dart#L5
To get the key in SharedPreferences where the file Dir is stored.
Then delete the file manually and set the key to null.
The only issue is that if the file is removed while it is playing then it won't switch over to web one automatically.
I would not recommend this package.
Just audio has built in cache. I would trust that more.


Tvdb UI classes rework + profile command

I'm marking this as ready for review, even though the /profile command definitely isn't complete, in fact there are a lot of improvements that it definitely needs, however, to speed development up, I'd like the reworked classes to get merged as soon as possible, as it will affect development of other things. The profile command can be finished later.

@Paillat-dev feel free to push any changes into this, as you'll probably wake up much sooner than I will and I don't want to block anything here. Do note though that if you will decide to push here, you will not be able to get an approving review for this PR that would make it mergeable. So you'd need to wait for me. Alternatively, you can just merge this and open another PR with any changes you'd like to make. Even more alternatively, you can work off of this branch (even after you've pushed to it), leaving the PR opened but still getting the benefit of working off of these changes.

I adapted it to use the new system for series,  but it doesn't work because the relationship on UserListtem.episode returns none.