[Bug] Error creating report in JSON format in v0.2.x

chainsaw version Version
v0.2.4
Description
I'm trying to generate a JSON report to then parse for errors but the report is never being generated. I'm following the docs here using the getting started test. It works when --report-format is set to XML, but not JSON.
I checked v0.1.9 and the JSON output worked, but v0.2.0 did not. I'm wondering if it's related to the changes from this feature: https://github.com/kyverno/chainsaw/issues/1099.
Steps to reproduce

Setup a directory with the getting started test
Run chainsaw test --report-name chainsaw-report --report-format JSON --report-path "$PWD". No report should be generated.
Run chainsaw test --report-name chainsaw-report --report-format XML --report-path "$PWD". A report should be generated

Expected behavior
When --report-format is set to JSON a report will be generated.
Screenshots
No response
Logs
❯ chainsaw test --report-name chainsaw-report --report-format JSON --report-path "$PWD"
Version: 0.2.4
Loading default configuration...
- Using test file: chainsaw-test
- TestDirs [.]
- SkipDelete false
- FailFast false
- ReportFormat 'JSON'
- ReportName 'chainsaw-report'
- ReportPath '/Users/jwinton/Development/example-test'
- Namespace ''
- FullName false
- IncludeTestRegex ''
- ExcludeTestRegex ''
- ApplyTimeout 5s
- AssertTimeout 30s
- CleanupTimeout 30s
- DeleteTimeout 15s
- ErrorTimeout 30s
- ExecTimeout 5s
- DeletionPropagationPolicy Background
- Template true
- NoCluster false
- PauseOnFailure false
Loading tests...
- quick-start (.)
Loading values...
Running tests...
=== RUN   chainsaw
=== PAUSE chainsaw
=== CONT  chainsaw
=== RUN   chainsaw/quick-start
=== PAUSE chainsaw/quick-start
=== CONT  chainsaw/quick-start
    | 08:23:50 | quick-start | @setup   | CREATE    | OK    | v1/Namespace @ chainsaw-helpful-hagfish
    | 08:23:50 | quick-start | step-1   | TRY       | RUN   |
    | 08:23:50 | quick-start | step-1   | APPLY     | RUN   | v1/ConfigMap @ chainsaw-helpful-hagfish/chainsaw-quick-start
    | 08:23:50 | quick-start | step-1   | CREATE    | OK    | v1/ConfigMap @ chainsaw-helpful-hagfish/chainsaw-quick-start
    | 08:23:50 | quick-start | step-1   | APPLY     | DONE  | v1/ConfigMap @ chainsaw-helpful-hagfish/chainsaw-quick-start
    | 08:23:50 | quick-start | step-1   | ASSERT    | RUN   | v1/ConfigMap @ chainsaw-helpful-hagfish/chainsaw-quick-start
    | 08:23:50 | quick-start | step-1   | ASSERT    | DONE  | v1/ConfigMap @ chainsaw-helpful-hagfish/chainsaw-quick-start
    | 08:23:50 | quick-start | step-1   | TRY       | DONE  |
    | 08:23:50 | quick-start | step-1   | CLEANUP   | RUN   |
    | 08:23:50 | quick-start | step-1   | DELETE    | RUN   | v1/ConfigMap @ chainsaw-helpful-hagfish/chainsaw-quick-start
    | 08:23:50 | quick-start | step-1   | DELETE    | OK    | v1/ConfigMap @ chainsaw-helpful-hagfish/chainsaw-quick-start
    | 08:23:50 | quick-start | step-1   | DELETE    | DONE  | v1/ConfigMap @ chainsaw-helpful-hagfish/chainsaw-quick-start
    | 08:23:50 | quick-start | step-1   | CLEANUP   | DONE  |
    | 08:23:50 | quick-start | @cleanup | DELETE    | RUN   | v1/Namespace @ chainsaw-helpful-hagfish
    | 08:23:50 | quick-start | @cleanup | DELETE    | OK    | v1/Namespace @ chainsaw-helpful-hagfish
    | 08:23:56 | quick-start | @cleanup | DELETE    | DONE  | v1/Namespace @ chainsaw-helpful-hagfish
--- PASS: chainsaw (0.00s)
    --- PASS: chainsaw/quick-start (5.36s)
PASS
Tests Summary...
- Passed  tests 1
- Failed  tests 0
- Skipped tests 0
Done.

### Slack discussion

_No response_

### Troubleshooting

- [X] I have searched other issues in this repository and mine is not recorded.

Oh, looks like the JSON case is empty

Attempting to fix in this PR: https://github.com/kyverno/chainsaw/pull/1538
Happy to make any necessary changes

I'm not sure if junit supports json 🤔
Trying to confirm that

Ah that would be a fun gotcha 😅
For context, I really like the idea of a json output because I'm trying to build some continuous automated testing for some clusters and being able to parse the test results would be super helpful. If json should not be a supported output I'm also happy to just remove that option entirely, but I would say that I love the idea of having the report in json format even if the json output isn't junit compatible.

Yeah, i agree, i'm not a test report format expert but it looks like junit only supports xml officially.
I'd like to find a json equivalent if it exists.

@eddycharly I've done some searching around and have found some javascript projects that a junit style json conversion, like this one. Is this what you're imagining for the feature? I'd be happy to implement something like this, if so.
That said, I'm not sure if this would be in "bug" scope. Would we be able to consider the lack of JSON output a bug and go forward being able to output the json file in the current format of the Report struct and then make it a breaking change to update the output format to junit style as a breaking change?

I actually think I've uncovered an XML report bug as well with the file output not rendering failures properly. For context, I'm working on a test harness to execute chainsaw in Kuberhealthy (which is working really nicely and I'm loving it), and I'm now working on improving the error surfacing. I'd love to invest a little time into the reporting if you're looking for someone to do any work in that area.

Ok, sorry for all the noise, but I took a quick stab at fixing a couple of things I was running into for my own purposes: https://github.com/kyverno/chainsaw/pull/1539
On my side project I'm just using yq to handle my XML --> JSON conversion quickly but I'm still interested in finding the most ideal reporting fix so I can just use native output. Let me know if there's anything I can help collaborate on! I also just joined the chainsaw channel in the Kubernete slack and am happy to talk more there if it's better

I've been thinking about a good fix too.
One option would be to use the raw output from the golang testing package and defer to tools that work with the native output.
While i like this solution i feel like it will lack test details.
I need to think about it more :(

I think the best approach is to  create an internal report and use conversion to specific formats.

@eddycharly I'm down to work on this but won't have time until next week at the earliest.

Thanks for that @eddycharly ! Sorry I wasn't able to finish this fully but I'm hoping to be able to get into chainsaw more soon


Support JUnit 3 TestSuite

I understand if the original intention of the fix for @Suite was to only fix JUnit 4 suites. I only wish to provide some feedback about other cases.
steps
// src/test/MathTest.scala
// This is a definition of a JUnit 3 test case. Many of these test cases will be "dynamically" collected into a JUnit 3 `TestSuite` and run.

class MathTest(op1: Int, op2: Int, res: Int) extends TestCase(s"$op1 + $op2 = $res") {
  final override def runTest(): Unit = {
    assertEquals(res, op1 + op2)
  }
}

// src/test/MathSuite.scala

class MathSuite extends TestCase

object MathSuite {
  // This is essentially a Scala 2.12+ hack, where methods on the companion object produce static forwarders on the class.
  // This is the Scala equivalent of the JUnit 3 convention public static Test suite() { ... }
  def suite(): Test = {
    val s = new TestSuite("MathSuite")
    s.addTest(new MathTest(1, 2, 3))
    s.addTest(new MathTest(2, 3, 4))
    s
  }
}

problem
It still produces:
[error] java.lang.RuntimeException: Test class MathTest is not enclosed by MathSuite

notes
The JUnit 3 TestSuite is still not fixed by https://github.com/sbt/sbt-jupiter-interface/pull/87 (I did a publishLocal).
Originally posted by @vasilmkd in https://github.com/sbt/sbt-jupiter-interface/issues/87#issuecomment-2254618861

Thanks for opening this ticket!

An additional detail to this ticket, "org.junit.vintage" % "junit-vintage-engine" % JupiterKeys.junitVintageVersion.value % Test is required as a dependency for reproducing the described problem.


User can submit a program form (submitting updates for a block)

blocked by #113
Done when

Applicant can submit the block form and persist question answers.
On success applicant is redirected to the next block (if there is one. create a simple stub "you're done!" page if there isn't)

wireframes: https://miro.com/app/board/o9J_lXULxwE=/?moveToWidget=3074457354365631793&cot=14

M1 Review - In progress

#256 covers the implementation of and redirect to the review page.
With that, I think we can say that PR #438 will resolve this issue.

Oops - I meant #382 will resolve this! But it hasn't been approved and merged yet.


Ignore iCCP section if it is invalid

This PR makes invalid iCCP sections get ignored instead of throwing an error. Let me know if I should add an option to toggle this behavior.
Ideally, I think the icc_profile field should be an Option<Result<_, _>>, but that would be breaking. To ensure duplicate iccp sections are handled correctly, I introduced a new have_iccp field.

This might change if we switch to lazy loading of metadata chunks, but looks good to me


so long, and thanks for all the fish

please create as plugin

please persist

http://i.giphy.com/52i4mbxzA2jFS.gif

when you leave, you leave me no other choice:


Use Mergify to automate backporting to 1.2.x

Now, any PR merged to master with Milestone 1.2.X will have a backport PR automatically generated.
Checklist

[x] Did you specify the type of improvement?
[x] Did you state the API impact?
[x] Did you specify the code generation impact?
[x] Did you request a desired merge strategy?

Type of Improvement
Release automation improvement

API Impact
No change

Backend Code Generation Impact
No change

Desired Merge Strategy
Squash

I also added labeling to try to help organize backporting. The basic problems I'm trying to solve are

Backport bug fixes to stable (1.2.x)
Help @ucbjrl or whoever is doing releases know that things have been backported properly

These changes will have Mergify automatically back port PRs that have the Milestone 1.2.X, it will then label the PR Backported and once it creates a new PR against branch 1.2.x it will label it Backport. The idea here is that we can check the Milestone 1.2.X to ensure everything has been properly backported and we can check that back ports have been properly merged.
This means cleaning up some old PRs, to illustrate what I'd like to see, I changed https://github.com/freechipsproject/firrtl/pull/1202 to Milestone 1.2.X, labeled it Backported and then labeled the back port of that PR https://github.com/freechipsproject/firrtl/pull/1225 Backport.
What do people think?

That comment was very repetitive, but hopefully it gets the idea across 😅

That makes sense. And the mention in the new PR will pop up in the conversation of the original PR.

That makes sense. And the mention in the new PR will pop up in the conversation of the original PR.

Yeah exactly, they are linked, we just want some way of checking that we are actually back porting stuff. Checking that everything is labeled with either Backport or Backported in 1.2.X seems like a reasonable way of doing this.
If we adopt this flow, we'll probably want to move stuff in Milestone 1.2.X to 1.2.0 or elsewhere.

The only negative is that issues also get the milestone, but they're marked with different icons so it's fairly easy to tell you can ignore them.


Feature Request: where allow raw builder

Hello again 👋
Seem like you can't use .where with .raw method, to use BETWEEN for exemple

Yep, that's probably a good idea. I'll add versions of where, orWhere, having, orHaving, on and orOn that take a single RawBuilder instance.
Still, I'd use where('foo', '>', a).where('foo', '<', b) instead of a raw between statement.


Segfault in update_call_arg_area_offset

struct F00{
        int a;
};
struct F00 func()=func();

The above input file leads to a segfault in c2m update_call_arg_area_offset.
Found while fuzzing d51b45f6c76d2ca03a5b2e1968c195b867eaed30, verified with cf3c9c106afdda59c402bdd40e61241aa20a755d
AddressSanitizer:DEADLYSIGNAL
=================================================================
==1447396==ERROR: AddressSanitizer: SEGV on unknown address 0x000000000020 (pc 0x55a3bc63b869 bp 0x000000000001 sp 0x7fd4e3afb7c0 T1)
==1447396==The signal is caused by a READ memory access.
==1447396==Hint: address points to the zero page.
    #0 0x55a3bc63b868 in update_call_arg_area_offset c2mir/c2mir.c:8125
    #1 0x55a3bc6bf7b6 in check c2mir/c2mir.c:9065
    #2 0x55a3bc6d5a35 in create_decl c2mir/c2mir.c:7798
    #3 0x55a3bc6b35c7 in check c2mir/c2mir.c:9159
    #4 0x55a3bc6b6b1f in check c2mir/c2mir.c:8286
    #5 0x55a3bc6b6099 in check c2mir/c2mir.c:9431
    #6 0x55a3bc6f9314 in do_context c2mir/c2mir.c:9697
    #7 0x55a3bc6f9314 in c2mir_compile c2mir/c2mir.c:13481
    #8 0x55a3bc6fcd6a in compile c2mir/c2mir-driver.c:498
    #9 0x7fd4e7154608 in start_thread /build/glibc-SzIz7B/glibc-2.31/nptl/pthread_create.c:477
    #10 0x7fd4e7079132 in __clone (/lib/x86_64-linux-gnu/libc.so.6+0x11f132)

AddressSanitizer can not provide additional info.
SUMMARY: AddressSanitizer: SEGV c2mir/c2mir.c:8125 in update_call_arg_area_offset
Thread T1 created by T0 here:
    #0 0x7fd4e72fe815 in __interceptor_pthread_create ../../../../src/libsanitizer/asan/asan_interceptors.cc:208
    #1 0x55a3bc6116f8 in init_compilers c2mir/c2mir-driver.c:540
    #2 0x55a3bc6116f8 in main c2mir/c2mir-driver.c:656

==1447396==ABORTING

Thank you for all the tests.  I fixed this one by bdac1fa


feat: externalize typescript support

Types of changes

[ ] Bug fix (a non-breaking change which fixes an issue)
[ ] New feature (a non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Description
External repo (private and very WIP) : https://github.com/nuxt/typescript
TODO before ready

[x] Refactor core to be able to externalize TypeScript Support implementation (#5854)
[x] Merge the refactor in dev & merge dev into the branch related to this PR
[x] Implement TypeScript support in external repo
[ ] Write new tests in external repo
[ ] Move and update examples in external repo
[ ] Publish new @nuxt/typescript & nuxt-ts
[ ] Prepare docs for migration

Checklist:

[x] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly. (PR: #)
[x] I have updated tests to cover my changes (if not applicable, please state why)
[ ] All new and existing tests are passing.

Codecov Report

Merging #5858 into dev will increase coverage by 0.07%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##              dev    #5858      +/-   ##
==========================================
+ Coverage   95.68%   95.76%   +0.07%
==========================================
  Files          82       80       -2
  Lines        2689     2645      -44
  Branches      690      675      -15
==========================================
- Hits         2573     2533      -40
+ Misses         98       96       -2
+ Partials       18       16       -2

Flag
Coverage Δ

#e2e
100% <ø> (ø)
:arrow_up:

#fixtures
51.07% <75%> (+0.72%)
:arrow_up:

#unit
92.36% <100%> (-0.32%)
:arrow_down:

Impacted Files
Coverage Δ

packages/cli/src/utils/banner.js
100% <ø> (+5.26%)
:arrow_up:

packages/cli/src/imports.js
100% <ø> (ø)
:arrow_up:

packages/utils/src/route.js
100% <ø> (ø)
:arrow_up:

packages/webpack/src/config/base.js
94.73% <ø> (-0.22%)
:arrow_down:

packages/config/src/config/build.js
100% <ø> (ø)
:arrow_up:

packages/cli/src/command.js
98.96% <ø> (-0.03%)
:arrow_down:

packages/webpack/src/config/client.js
98.07% <100%> (-0.11%)
:arrow_down:

packages/cli/src/utils/config.js
96.66% <100%> (+2.91%)
:arrow_up:

packages/config/src/options.js
100% <100%> (ø)
:arrow_up:

packages/builder/src/builder.js
99.6% <100%> (ø)
: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 2fabea9...f12565d. Read the comment docs.

@nuxt/core-team Alright, I made this PR ready to review.
Some things are still missing but it's not something to do with code changes.
I just want review for the changes and we'll merge it only on another GO.
I would like it to be shipped with 2.9. External typescript support (https://github.com/nuxt/typescript) needs at least nuxt-edge to have the current typescript support removed so it can be really well tested manually and that the unit tests pass.
Only docs & examples should be remaining, i'm on it but for either tests or examples it's not relevant to have either nuxt/nuxt-edge with "old" builtin typescript support + new typescript module.


Publish Cert Auth and Google Auth from Devastator project as public plugins for Neptulon JSON-RPC

..so everyone can use and contribute to them.

https://github.com/nbusy/devastator/blob/master/auth_cert.go
https://github.com/nbusy/devastator/blob/master/auth_google.go

Moved: https://github.com/neptulon/jsonrpc/issues/1


Pattern Matching on List Literal

[x] Make List Literal an atomPattern
[x] Desugaring
[x] Tests

We may need to extract a PatternDesugarer instead of writing code in Desugarer.

bors cancel

bors merge


Update images for dark theme in Lisk docs - Partially closes  #1408

Partially closes #1408

@shuse2 Hi Shu, Mona and I discussed this, and decided that there were a couple of rather complex, intricate diagrams whereby it was much clearer and easier to be viewed with a white background. However, the majority should now be with a transparent background. Which particular diagrams are you referring to..? For example the P2P architecture diagram we decided to leave it with a white background.

I think having white background make sense and more readable, but I thought it just inconsistent to have transparent background for some image.

Hey Mona, Agreed...You are right. This is great feedback, as it looks much better with the titles of the Plugin and Module and Assets diagrams without the white background. I quite like the titles here, but also it seemed to me maybe they were a bit too large, so I have reduced the size of them.
I will also remove the white background on the NW topology diagram and in the Devnet and Testnet diagrams. Finally, I will check the other diagrams as well, and where there is any text on a white background I will remove it. 👍

Hey Mona, OK thanks. I will recheck this white border issue. Yes, good point regarding the Plugin anatomy diagram...I agree it would look better here if it were reduced in size, as this is often the case with simple block-type diagrams which do not contain so much detail, as they tend to appear somewhat overpowering. No worries, I will take care of it. 👍


build error on macOS

I was suddenly unable to start IJulia in the terminal. I re-installed Homebrew, then built IJulia again, but got the following error message:
LoadError: UndefVarError: Unicode not defined
while loading /Users/igor/.julia/v0.6/IJulia/deps/build.jl, in expression starting on line 4
This is basically the same error I got when I tried to start IJulia before the new installation.

A recent re-install resolved the issue.


Add testing

Add a unit test that runs on Chrysalis or another machine (not on GitHub Actions Linux machine).

Try testing on small simulation runs
Try testing what the bash files look like as a result of running a configuration file. Add dry-run option so that the scripts would not actually get submitted.


Vim9: inconsistent handling of number as first argument for "repeat()"

Describe the bug
In Vim9 script, passing a number as first argument to repeat() is accepted at the script level, but not in compiled code, which is inconsistent.
To Reproduce
Run this shell command:
vim -Nu NONE -S <(cat <<'EOF'
    vim9script
    var s: string
    s ..= repeat(0, 3)
EOF
)

No error is given.
Now, run this other shell command:
vim -Nu NONE -S <(cat <<'EOF'
    vim9script
    def Func()
      var s: string
      s ..= repeat(0, 3)
    enddef
    defcompile
EOF
)

E1012 is given:
E1012: Type mismatch; expected string but got number

Expected behavior
To be consistent, either the first command should give an error, or the second one should not complain.
Environment

Vim version: 8.2 Included patches: 1-3249
OS: Ubuntu 20.04.2 LTS
Terminal: XTerm(353)

Additional context
The error message lacks some context:
vim9script
def Func()
  var s: string
  s ..= repeat(0, strlen(s))
enddef
defcompile

E1012: Type mismatch; expected string but got number

Who expected a string but got a number? strlen()?  repeat()?  ..=?
It turns out that it's repeat(), but it's not obvious.
Also, since the error is in an argument, why doesn't the message start with Argument 1::
E1012: Argument 1: Type mismatch; expected string but got number
       ^---------^

Just like here:
vim9script
def Func()
    strlen({})
enddef
defcompile

E1013: Argument 1: type mismatch, expected string but got dict<unknown>
       ^---------^

It turns out that it's repeat(), but it's not obvious.

Sorry, I completely misunderstood the issue.  It's not repeat() which is buggy.  It's the ..= assignment operator:
vim9script
var s: string
s ..= 123
echo 'no error'

no error

vim9script
def Func()
    var s: string
    s ..= 123
enddef
Func()

E1012: Type mismatch; expected string but got number

This is inconsistent, but I don't know which of these snippets need to be fixed.
One could argue that the first one is OK, because we can concatenate a string with a simple type like a number:
vim9script
echo 'string' .. 123

string123

Sorry, I completely misunderstood the issue.

It would have helped a lot if the error message had clearly stated who expected a number but got a string.  Here, it was actually ..=; not repeat().

Describe the bug
In Vim9 script, passing a number as first argument to repeat() is accepted at the script level, but not in compiled code, which is inconsistent.
To Reproduce
Run this shell command:
vim -Nu NONE -S <(cat <<'EOF'
    vim9script
    var s: string
    s ..= repeat(0, 3)
EOF
)

No error is given.
Now, run this other shell command:
vim -Nu NONE -S <(cat <<'EOF'
    vim9script
    def Func()
      var s: string
      s ..= repeat(0, 3)
    enddef
    defcompile
EOF
)

E1012 is given:
E1012: Type mismatch; expected string but got number

Expected behavior
To be consistent, either the first command should give an error, or
the second one should not complain.

The repeat() function is tolerant, if the first argument is a number it
is used like a string.  Perhaps for Vim9 we should change this?  Might
lead to unexpected errors when converting code to Vim9.

Environment

Vim version: 8.2 Included patches: 1-3249
OS: Ubuntu 20.04.2 LTS
Terminal: XTerm(353)

Additional context
The error message lacks some context:
vim9script
def Func()
  var s: string
  s ..= repeat(0, strlen(s))
enddef
defcompile

E1012: Type mismatch; expected string but got number

Who expected a string but got a number? strlen()?  repeat()?  ..=?
It turns out that it's repeat(), but it's not obvious.
Also, since the error is in an argument, why doesn't the message start with Argument 1::
E1012: Argument 1: Type mismatch; expected string but got number
       ^---------^

Just like here:
vim9script
def Func()
    strlen({})
enddef
defcompile

E1013: Argument 1: type mismatch, expected string but got dict<unknown>
       ^---------^

The error is not with the argument but with the return type.  It is
assumed to be equal to the type of the first argument, but with a number
a string is returned.
--
A successful man is one who makes more money than his wife can spend.
A successful woman is one who can find such a man.
/// Bram Moolenaar -- @.*** -- http://www.Moolenaar.net   \
///                                                                      \
\\        sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ ///
\\            help me help AIDS victims -- http://ICCF-Holland.org    ///

It turns out that it's repeat(), but it's not obvious.

Sorry, I completely misunderstood the issue.  It's not repeat() which is buggy.  It's the ..= assignment operator:
vim9script
var s: string
s ..= 123
echo 'no error'

no error

vim9script
def Func()
    var s: string
    s ..= 123
enddef
Func()

E1012: Type mismatch; expected string but got number

This is inconsistent, but I don't know which of these snippets need to be fixed.
One could argue that the first one is OK, because we can concatenate a string with a simple type like a number:
vim9script
echo 'string' .. 123

string123

When using ".." separately it does accept a number.  The idea is that
using ".." is a strong indication the left and right should be strings.
If you then have a number, we automatically convert it to a string.
This is convenient for things like:
echo 'the result is ' .. count

While it's unlikely this is a mistake that goes unnoticed.
Thus the problem is with "..=" not accepting a string in a :def
function.  Oh, and at script level "s ..= true" doesn't work, while it
does in a :def function.
--
GALAHAD: No, please.  Please! I can defeat them!  There's only a hundred.
GIRLS:   He will beat us easily.  We haven't a chance.
"Monty Python and the Holy Grail" PYTHON (MONTY) PICTURES LTD
/// Bram Moolenaar -- @.*** -- http://www.Moolenaar.net   \
///                                                                      \
\\        sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ ///
\\            help me help AIDS victims -- http://ICCF-Holland.org    ///


⚠ ClamAV has degraded performance

In e19b0b5, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 68 ms

Resolved: ClamAV performance has improved in c691ad8.


The tab doesn't temporarily open when clicking one ADLS Gen2 blob container

Storage Explorer Version: 1.19.0-dev
Build Number: 20210326.10
Branch: main
Platform/OS: Windows 10/ Linux Ubuntu 18.04/ MacOS Catalina
Architecture: ia32/x64
Regression From: Previous release(1.18.1)
Steps to Reproduce

Expand one ADLS Gen2 storage account -> Blob Containers.
Select one blob container (no opened tabs in the explorer).
Click the blob container -> Check whether the tab temporarily opens.

Expected Experience
The tab temporarily opens.

Actual Experience
The tab doesn't temporarily open.

Additional Context
This issue doesn't reproduce for one regular blob container.

Verified on build main/20210330.6. Fixed.


[SAM] Meikyo bugifx

Bugfix for Meikyo because apparently, Samurais are unable to bend space time, my bad.
Short tl;dr EoF cursed, can return possible GCDs that exceed 3. Hard capping it to 3.

@ayyaruq requested changes made


Add bats-file to Dockerfile

Here's more information on bats-file. This library provides a Bats way of testing filesystems which is nice to have.

@yellowplane13 Thank you for your contributions. Couple of questions on this pull request

We see you have added github actions through files .github/workflows/docker-image.yml and .github/workflows/docker-publish.yml. Based on those github actions looks like you are building the image using Dockerfile and publishing. Please can you confirm if you were intending to add these github actions as part of the PR to this repo ? If so what are we trying to achieve with them as we currently do not have any github actions in this repo ?

Please can we add an test example in the readme file on how bats-file can be used

Thanks for the pull request! bats-file support was just added in #45


Fixed #29697 -- Changed Query.trim_start for avoid removing the aux tables

https://code.djangoproject.com/ticket/29697

I tried to apply your recommendations. Could you check again?

@charettes thanks a lot. sorry about these shortcomings and thank again for your help.

thanks for your reviews. @charettes you're right about alias, I think so too but I couldn't find a better solution, it exceeded me. I changed is_alias_available_join

you're right about alias, I think so too but I couldn't find a better solution, it exceeded me.

This part of the ORM is definitely tricky, it's normal that you are feeling overwhelmed. I still think we should find a way to test the multi-alias case and address it before merging this change though.

hi @charettes, pushed a commit about maintaining is available check func before unref_alias and test for multi-alias queries.

The added test passes without changes in Query. Bug was probably fixed by Simon refactorization or test doesn't cover this issue. I believe in Simon :smile: , so I will check which commit has fixed this.

Bug was fixed by f19a4945e1191e1696f1ad8e6cdc6f939c702728.
Tests updated in #11142.

that's a great solution. @charettes :+1:


List of blocks that need updated geometry

This will be a long list- I'll update it as things get patched. This list was made in the v1.1.1 Pre-Release Many of these have textures different to what they should and that will be analyzed after they're fixed since their textures may also be fixed with correct geometry.
- mob heads
- sea pickles
- ground-mounted banner (only block with hitbox)
- wall-mounted banner (render as a wall in the block with the hitbox)
- chain
- one-high flowers (including wither rose)
- flowing water (Currently banned)
- flowing lava (Currently banned)
- fence posts
- fence gates
- doors
- iron bars
- glass panes
- beds
- campfire
- soul campfire
- brewing stand
- crimson roots
- warped roots
- coral
- coral fans
- turtle eggs
- dragon egg
- fern
- tall fern
- grass
- tall grass
- nether sprouts
- brown/red mushroom
- crimson/warped fungus
- sweet berry bush
- cake
- saplings
- crops
- nether wart
- vines
- weeping/twisting vines
- dead bush
- bamboo sprout
- bamboo (multiple tall texture)
- lever
- buttons
- cocoa bean
- string
- tripwire hook
- bell (ground and wall-mounted)
- fire
- soul fire
- piston heads
- end rods
- conduit
- snow layer
- cobweb
- chorus plant/flower (Doesn't matter imho, but still a bug)
- anvil
- grindstone
- enchantment table
- lectern
- chest/trapped chest/ender chest (Also doesn't matter imho, but still bug and will show the ghost block when you place a chest over it)
- all pressure plates except spruce and stone
- grounded signs
- wall-mounted signs (render as wall)
- flower pot
- portal (nether)
- end portal frame
- end portal
- end gateway
- bubble column
- soul sand (same issue as chests)
- repeater (currently trapdoor)
- comparator (currently trapdoor)
- dirt pat
- beacon
- farmland
- trapdoors (too thin)
- composter
- cauldron
- lit redstone torch
- torch
- soul torch
- ladder

I believe this is everything. Check out the list of blocks I checked here: Everything block list.txt
If a contributor could make a comment of the patched ones I can edit the list most accurately. I'd like to keep "hack fixes" out of this list if possible so you have a full list of what needs to be changed.
Reference photo:

What hackfixes are there currently so I can add them? I can think of a couple: Daylight sensors as half slabs and repeaters as trapdoors.

What hackfixes are there currently so I can add them? I can think of a couple: Daylight sensors as half slabs and repeaters as trapdoors.

I think i patched the daylight sensor. If you do patch can you put the structure file in a "unit test folder".
I also added a "hacks.json" to the lookups... i pushed it to my dev branch for now

I think i patched the daylight sensor. If you do patch can you put the structure file in a "unit test folder".
I also added a "hacks.json" to the lookups... i pushed it to my dev branch for now

Structura 1.3 will allow for this to happen

I broke this into individual tickets. I think i will close this one for now. It is easier to work with multiple tickets


Two-step training (feature importance)

Discussed in https://github.com/autogluon/autogluon/discussions/3075

Originally posted by mglowacki100 March 22, 2023
I've use that is quite common and generic, namely I've training dataset with a lot of features (a few thousands) and  I've no control on them, so I train autogluon model and look at feature importance - typically only top 10-30% really matters. Next I re-train autogluon on selected features. Typically doing this procedure once or twice is enough, but some care is required regarding overfitting.
I wonder if it is possible to add such functionality to autogluon, that could be activated by parameter like refit_on_top_features.
What do you think about it?

(Reposting my answer to the discussion)
We actually have this feature to some extent, but it isn't well documented / tested:
feature_prune_kwargs in https://auto.gluon.ai/stable/api/autogluon.tabular.TabularPredictor.fit.html
You might find it useful. In our past testing, it was able to generally enhance the accuracy of the final model. We will probably plan to refactor it slightly prior to v1.0 so it is more officially supported.

@Innixma
How do I get pruned feature now ? I don't see any way in doc.
My case is select features with several rolling split timeseries dataset.
Since good feature may change along the time, I'd like train severl split , and merge the best 30 features in each model.


Linux

Hello,
Thank you for PR! I would like you to refactor as follows, please:

make Header::used_20_calling_method available only on Windows;
read Header in Smbios_table::from_system() to the front of Smbios_table::data_;
return reinterpret_cast<const Structure*>(data_.data() + sizeof(Header)) from Smibios_table::first_structure() either on Linux and Windows.

Implemented in 8e02a1f9cfbb30badbed450124e5162d77425339


[BUG] ServiceBus body containing ExpiresAtUtc field is not parsed properly

Investigative information
Please provide the following:

Related CRI: 219200398
Timestamp: 2020-12-22 22:58:33
Function App name: prod-azureing-governor
Function name(s) (as appropriate):
Core Tools version:

Repro steps
Provide the steps required to reproduce the problem:

Create a function app with service bus trigger.
Send a message to the ServiceBus namespace, with ExpiresAtUtc in the body which contains an invalid format.
The function will now fails with ValueError: time data '12/18/2020 20:57:23' does not match format '%Y-%m-%dT%H:%M:%S.%fZ'

Expected behavior
Provide a description of the expected behavior.
The function app should not fail since we should not parse of the ServiceBus message.body

Actual behavior
Provide a description of the actual behavior observed.
ValueError: time data '12/18/2020 20:57:23' does not match format '%Y-%m-%dT%H:%M:%S.%fZ'

Known workarounds
Provide a description of any known workarounds.

Contents of the requirements.txt file:
Provide the requirements.txt file to help us find out module related issues.

Related information
Provide any related information

Links to source
Bindings used

cc: @gzuber @vrdmr @anirudhgarg @stefanushinardi

Overwriting the ExpiresAtUtc field in body will results in trigger_metadata change even before any processing in azure-functions package. Wondering if the servicebus-extension is not handling it properly.

Node also has the same issue, metadata got overwritten by message.body

@alrod, @sidkri - FYI
Good Catch Roger - yes - looks like the issue from the extension side.


badge colors

I really like the looks of this theme. But I don't like the badge colors in a picture-element card. They look a bit pinky instead of red.

Also, in light mode I cannot see the upper navigation bar. See attached screenshot.

Can I edit these things somehow without modifying your theme yaml ? Because that would give me issues whenever I update the theme.

What I tried to show in the second screenshot is the top right when in edit mode. I can show you more but it's all blurred like in the screenshot. When switching back to the HA default in blue I can see everything clear.
Also, thanks for the fast badge fixing. I will try to update it in hacs.

Ah I see now, it was so washed out in the screenshot that I couldn't see the views or done button. This may be a caching issue as this is what it looks like in light view for me:

Also, this theme turns the header toolbar into a footer, so if it still appearing at the top of the screen (and you have card-mod installed) then you definitely need to refresh or clear cache.

I tried and with card mod installed it looks better in respect to the colors but I don't want the header at the footer 😄
I guess that can not be made configurable, right ? That would make for a general solution.

I can make it configurable in the sense that I can include a copy of the theme that doesn't have the card-mod section, and then work on fixing the colors of it. I'll try to work on it later tonight.

Can you try 1.4.0-beta.006? It should fix the toolbar colors when card-mod isn't used, and adds a "no mod" version.

Seems to work indeed. I tried the nomod version. The badges are now red but with white text font so they look empty now 🤔
The toolbar looks readable now 👍

That might really be a caching issue this time, because the text is black for me. Can you try hard refreshing (Ctrl + F5)?

Unfortunately it doesn't help. It's in both Firefox and Chrome. But I think I'll stick to the default theme. I got really used to it after four years of using the default blue HA theme 😃

Fixed in 1.4.0


Typo

There should be a space in History of TrueTypedocument

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

ID: bb966bef-f887-40af-3602-46cdf4bf96ec
Version Independent ID: 39c36be8-9aac-9f6b-04d3-53fbf5acd31f
Content: TrueType overview - Typography
Content Source: typographydocs/truetype/index.md
Product: typography
GitHub Login: @alib-ms
Microsoft Alias: alib

Thank you for the feedback. Fixed!


Make CalculationListener a functional interface

I've realised the use case I wanted this for actually needs to implement both methods in the interface.


Accessibility Updates

##Accessibility Updates
In this milestone above I :

[ ] added a title that briefly describes the content of the page
[ ] added alternative texts on each image tag
[ ] added  the correct heading level on tittle  and subtitles
[ ] added darker colors to add contrast on language texts
[ ] added label on html form fields fields. However, to match the Figma design, it was made invisible
[ ] moving content,  and multimedia no issues found
[ ] Also, I had previously added a semantic structure and fully responsive site that shrink the content properly.

Hi @PeteUgwu,
While you made a great effort in this project, unfortunately, I cannot proceed to review your code.
Invalid Code Review Request
You have submitted a project, that;

Linters isn't running. Kindly fix branch conflicts so that linters checks can run.
This is a pair programming exercise so you are supposed to finish the project with your partner. I can only see one contributor on this pull request. Kindly ask your coding partner to contribute to this project.

Your Code Review Request will be marked as invalid in your Dashboard, so please submit a new one once you are ready 🙏
Cheers and Happy coding!👏👏👏
Feel free to leave any questions or comments in the PR thread if something is not 100% clear.
Please, remember to tag me in your question so I can receive the notification.
Please, do not open a new Pull Request for re-reviews. You should use the same Pull Request submitted for the first review, either valid or invalid unless it is requested otherwise.

Invalid Code Review Request does not count into the code reviews limit.


Implement the macros feature in the analyzer

This issue tracks the implementation of the macros feature in the analyzer.
@srawlins, I couldn't find an issue which is tracking this work. It is needed in order to be able to approve test failures when the test uses parts of the macro feature that haven't yet been implemented. Is there a suitable issue already?
Otherwise I'll approve some test failures using this issue. Feel free to delete these organizational questions and write whatever is suitable for the purpose here.

@itsjustkevin normally creates such issues, but as far as I know we don't have any feature issues yet for macros.

OK, thanks!
@itsjustkevin, do you have a particular format that we ought to use for this kind of feature implementation tracking issue?

@eernstg I have a script that I use to generate these issues and projects.  Taking a note to get that done on Monday.

Sounds good, thanks!


Reanalyze button takes user to confusingly similar page

I just want to make sure this is intended. Steps:

From the default organization page (here /organizations/stanford), click "Reanalyze"

You are routed to the stream's specific page at (/organizations/stanford/streams/thedefault) which looks like this:

The page is very similar, just without the tabs we are implementing for the Provider page. This confused me, I didn't know where I was in the app. Is this intended? Should the stream pages look different than the Provider Pages? Should they also implement the tabs? I am likely missing some context, thanks!

@marlo-longley This is not a technical answer but if I remember correctly, before you made the updates to the org page selecting "Re-analyze" performed an action without a noticeable change to the page. Perhaps it refreshed the page so it just looked like nothing changed, but I think the point is that action shouldn't redirect the user anywhere. At most it would refresh the current page.
We probably should consider a flash message to indicate the "Re-analyze" action was accepted and is underway (does this create a background job? If so, we could include a link the flash message to the Processing status page, Action jobs open), but that's beyond your question, I think.

Oh wait, I see now from your second screenshot we already do show a flash message. So at least from a UX point of view, ideally after the user selects "Re-analyze":

Remain on current page (no redirect)
Display the current flash message
If applicable, add to the current flash message View current processing status. as a link that redirects to the processing status page

@ggeisler thanks! That makes sense not to redirect the page, I'll try to implement that.
I guess this situation just revealed to me that stream pages like /organizations/stanford/streams/thedefault contain the same info and header as the Provider page /organizations/stanford which shows the default stream, but the /stream page shows everything in one vertical view without the tabs.

@marlo-longley yeah...that's not great. I think we can fix it by changing this line to something like:
format.html { redirect_back_or_to([@organization, @stream], notice: 'Upload was successfully updated.') }

Per discussion in the permissions doc, I am going to restrict seeing the Reanalyze button to only POD admins and Org Owners.

@marlo-longley I think the re-analyze stream button should remain restricted to POD Admins. I've updated the spreadsheet to reflect this.


Uncaught SyntaxError: Unexpected token '<'

I followed the instructions to install and got this error, any ideas what the cause is please?
Fri Nov 08 2019 15:34:20 GMT+0000 (Greenwich Mean Time)
https://www.myurl.com/local/vertical-stack-in-card.js?v=0.1.3:7:1 Uncaught SyntaxError: Unexpected token '<'

This is most likely because you downloaded the html instead of the raw. That is not valid javascript. Always make sure you download using raw button. After downloading the file again with the 'raw' button, remember to bump the version number for the custom component speficied in the 'resources' of your lovelace-ui.yaml file.

Thanks for this.  I saved the raw format, uploaded it to HA, changed the version to 0.1.4, restarted but I'm getting the same error.  I tried changing the version back but same error.  I'm feeling a bit silly for not knowing but when you are not familiar with something it's difficult to know what to do.  I've followed the instructions and it's not working.

I've sorted it.  it was the '-' and indentation in your example.  I removed the '-' and moved everything left 2 spaces and it's working.


Add Webster, MA please!

Feature request
Webster, MA like many small towns needs pressure to be put on them now. This is a town that NEEDS reinvestment in the community, defunding of police, and the resources to share that story of what is possible IF we defund the police!
Want to add a new feature to the site? Please describe the requested feature and provide any relevant information:

Hi @pmurp, thanks for your interest in adding Webster to the website. Emails on defund12.org are all written by community members. To add your city, you must provide:

Email addresses (at least one) of the government officials you’d like to receive the message
Detailed message concerning the budgeting decisions at stake in your community

Until you provide this content, we cannot post your city.
Follow our email style guidelines for quicker acceptance. Remember that messages must be city-specific and focused on defunding the police. If your message is copied from an external source, please provide a link to the original source.
Your request will be closed until you reply with the necessary content. Thank you!


repeatWhen operator broken since 5.5.6

RxJS version:
5.5.6, 5.5.7
Code to reproduce:
https://jsfiddle.net/jy5fj6r8/16/
Expected behavior:
No errors, see
https://jsfiddle.net/cm6abypb/3/
Actual behavior:
Throws error Rx.min.js:234 Uncaught TypeError: Cannot read property 'next' of null
Additional information:
It appears that changes in 5.5.6 broke the repeatWhen operator. The fiddle mentioned as "code to reproduce" uses 5.5.7 while the one in "expected behavior" uses 5.5.5.
When the unit test is slightly modified (as shown below) by wrapping the code in a try..catch, the error is also visibile in the tests.
  it('should retry when notified and complete on returned completion', (done: MochaDone) => {
    try {
      const expected = [1, 2, 1, 2];
    Observable.of(1, 2)
      .map((n: number) => {
        return n;
      })
      .repeatWhen((notifications: any) => Observable.empty())
      .subscribe((n: number) => {
        expect(n).to.equal(expected.shift());
      }, (err: any) => {
        done(new Error('should not be called'));
      }, () => {
        done();
      });
    }
    catch (e) {
      done(new Error('should not throw'));
    }
  });

Thank you for reporting this, @wwjhu!

I've had a quick peek at this. The repeatWhen implementation in 5.5.6 is unchanged from that in 5.5.5 - so 5.5.5 has the error, too.
However, prior with the change made in this PR, the error was swallowed.
The problem is that _unsubscribeAndRecycle sets this.notifications to null, but this.notifications.next() is called immediately after _unsubscribeAndRecycle.

Does this error exist in the latest RxJS (6.0.0-beta) version?

Does this error exist in the latest RxJS (6.0.0-beta) version?

Yes. And no. There is still an error in the beta, but - as in 5.5.5 - the error is swallowed.
My comment above was overly simplistic. This is what happens:

When the source observable completes, the complete implementation in the repeatWhen subscriber wires up the notification observable by calling subscribeToRetries.
When subscribeToResult is called in the subscribeToRetries implementation, the completion of the notification observable sees the inner subscriber call notifyComplete on the repeatWhen subscriber (the outer subscriber).
notifyComplete then calls super.complete which calls the repeatWhen subscriber's _unsubscribe and this.notifications is set to null.
Then, later in the complete implementation in the repeatWhen subscriber, the call to this.notifications.next() fails due to this.notifications being null.

The same problem occurs in 5.5.5, 5.5.6, 5.5.7 and in the beta, but the error is swallowed in versions other than 5.5.6 and 5.5.7.
It seems to me that the test in notifiyComplete is the wrong way around and should be:
notifyComplete(innerSub: InnerSubscriber<T, R>): void {
  if (this.sourceIsBeingSubscribedTo) {
    return super.complete();
  }
}

Thoughts?
Note there would still be the problem that errors are being swallowed in some versions.


Localizable.strings updated with new keys, but the values still empty

Hi @Dschee , last month, I used BartyCrouch without any problems.
After some time and BartyCrouch installation updated I'm back to translating new strings.
But now a new problem arises, the new keys are generated but with empty values.
It's seems the values from line is not saved to .strings files, only the keys:
self.noResultTitleLabel.text = BartyCrouch.translate(key: "search_no_result_title", translations: [.indonesia: "Hasil tidak ditemukan", .english: "Result not found"])

I'm not sure what is going on

Me neither, probably a bug in the recent changes. Will have a look soon alongside some other issues and hopefully fix. Could you please post your config file contents just in case I can't reproduce this issue? Thanks!

here's my .toml config:
[update]
tasks = ["code", "transform", "normalize"]

[update.interfaces]
path = "."
defaultToBase = false
ignoreEmptyStrings = false
unstripped = false

[update.code]
codePath = "."
localizablePath = "."
defaultToKeys = false
additive = true
unstripped = false

[update.transform]
codePath = "."
localizablePath = "."
transformer = "swiftgenStructured"
supportedLanguageEnumPath = "."
typeName = "BartyCrouch"
translateMethodName = "translate"

[update.normalize]
path = "."
sourceLocale = "id"
harmonizeWithSource = true
sortByKeys = true

[lint]
path = "."
duplicateKeys = true
emptyValues = true

Thanks. Could you also please post your BartyCrouch.swift file and it's directory path? Did you already try setting the path parameters to more detailed paths like recommended in the README? Also, are you sure your enum cases in BartyCrouch.swift are indonesia and not indonesian (note tha n at the end)? Just trying to help ...
I jus ttested this configuration and it's working on my machine ...

Here's my BartyCrouch.swift
import Foundation

enum BartyCrouch {
    enum SupportedLanguage: String {
        // TODO: remove unsupported languages from the following cases list & add any missing languages
        case english = "en"
        case indonesia = "id"
    }

    static func translate(key: String, translations: [SupportedLanguage: String], comment: String? = nil) -> String {
        let typeName = String(describing: BartyCrouch.self)
        let methodName = #function

        print(
            "Warning: [BartyCrouch]",
            "Untransformed \(typeName).\(methodName) method call found with key '\(key)' and base translations '\(translations)'.",
            "Please ensure that BartyCrouch is installed and configured correctly."
        )

        // fall back in case something goes wrong with BartyCrouch transformation
        return "BC: TRANSFORMATION FAILED!"
    }
}

@Dschee , I've tried to debug the source code.
I think the error is related with the recent changes at SupportedLanguagesReader
It seems the incorrect enum from another location was considered as SupportedLanguage enum by SupportedLanguagesReader
Here's the incorrect enum that stored into caseToLangCode[langCase] :
enum ExampleEnum: String, CaseIterable {
    case custom = "custom"
    case discount = "discount"
    case voucher = "voucher"
}

I already make sure that the .toml config is correct

@MSlaski As I don't have much time, to fix this, I'd need a Demo project (with code and config) where this can be reproduced. This way it will be much easier for me (or someone else) to fix.

@MSlaski @deden, someone on issue #133 had a solution for that which help me too. Can you please try?
" I've updated supportedLanguageEnumPath parameter for the update.transform action and problem have gone. "
Basically you need to make sure the supportedLanguageEnumPath param takes you to the BartyCrouch file with the languages enum.


UI changes - make cards responsive

In the home.html template, all playlists are shown as cards in rows.

Make this responsive, to adjust according to screen width.

@pvgupta24, @mishal23 can you add a description of the task?

@ifedyukin Please check the updated issue.

@mishal23 ok, assign me please. I fix that soon.

@ifedyukin  Please try sending a PR within 24 hours, else others will be able to claim.
Also, please do include screenshots will sending a PR.


Upstream translation

This implements the SHED system where we don't break the To/From node pair across a buffer.  This also helps to facilitate combining data after filtering. In the prior PR we wouldn't combine the raw and analyzed data streams until after the buffer, which would cause us to loose information about which raw data points were filtered out on the analysis stream. However, now we can combine before the buffer/gather which will allow us to properly combine the data together and filter out the analyzed and raw data simultaneously which means we will have properly aligned data.

pending rapidz release

Codecov Report

Merging #149 into master will decrease coverage by 5.47%.
The diff coverage is 88%.

@@            Coverage Diff             @@
##           master     #149      +/-   ##
==========================================
- Coverage   94.43%   88.96%   -5.48%
==========================================
  Files          13       16       +3
  Lines        1115     1441     +326
  Branches      194      223      +29
==========================================
+ Hits         1053     1282     +229
- Misses         40      125      +85
- Partials       22       34      +12

Impacted Files
Coverage Δ

shed/tests/test_doc_gen.py
100% <100%> (ø)

shed/translation_parallel.py
100% <100%> (ø)

shed/doc_gen.py
100% <100%> (ø)

shed/tests/test_writers.py
100% <100%> (ø)
:arrow_up:

shed/tests/test_replay.py
57.32% <53.17%> (-42.68%)
:arrow_down:

shed/tests/conftest.py
88.23% <80%> (ø)
:arrow_up:

shed/replay.py
83.33% <80.95%> (-14.17%)
:arrow_down:

shed/translation.py
90.52% <85.71%> (-5.08%)
:arrow_down:

shed/simple_parallel.py
87.67% <87.67%> (ø)

shed/tests/utils.py
95% <92.85%> (-5%)
:arrow_down:

... and 10 more

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 4bdb1e3...95870a9. Read the comment docs.

Needs:

[ ] check replay with numpy
[ ] flake8
[ ] string data address (time)
[ ] tuple data address
[ ] no principle nodes error
[ ] emergency stop

I think this is close enough on the tests, we don't use slow_mul anymore so the coverage fell a little.


Add scikit-network in machine learning and AI

Merged, thanks @tbonald!

Great!
Is there a way to be referenced in the scikit list?
http://scikits.appspot.com/scikits
The package is on PyPI:
https://pypi.org/project/scikit-network/
Thanks.

Le 2 mai 2020 à 13:13, Ralf Gommers<EMAIL_ADDRESS>a écrit :
Merged, thanks @tbonald https://github.com/tbonald!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/scipy/scipy.org/pull/344#issuecomment-622937216, or unsubscribe https://github.com/notifications/unsubscribe-auth/AGIT435NYESKL6DS5V4EW7LRPP565ANCNFSM4MXTU2VQ.

In principle it should appear there automatically, but it seems the site is broken now. E.g. this shouldn't be a blank page: https://scikits.appspot.com/scikit-data


About '--Inverse'

Thanks for your great work! I want to compare the inverse output data with origin data. But once I added '--inverse' to 'ECL.sh', an error occurred. 'ValueError: Found array with dim 3. None expected <= 2.'。 What should be done about it?
Traceback (most recent call last):
File "/mnt/sdb1/Timer/Large-Time-Series-Model-main/run.py", line 179, in
exp.test(setting)
File "/mnt/sdb1/Timer/Large-Time-Series-Model-main/exp/exp_forecast.py", line 252, in test
outputs = test_data.inverse_transform(outputs.squeeze(0)).reshape(shape)
File "/mnt/sdb1/Timer/Large-Time-Series-Model-main/data_provider/data_loader_benchmark.py", line 150, in inverse_transform
return self.scaler.inverse_transform(data)
File "/mnt/sdb1/miniconda3/envs/Timer/lib/python3.10/site-packages/sklearn/preprocessing/_data.py", line 1034, in inverse_transform
X = check_array(
File "/mnt/sdb1/miniconda3/envs/Timer/lib/python3.10/site-packages/sklearn/utils/validation.py", line 915, in check_array
raise ValueError(
ValueError: Found array with dim 3. None expected <= 2.

Hello, I think this should be the problem of incompatible dataset dimension. Could yo provide more information for us to help you correct this problem>


DIA-NN proteotypic peptide filtering

Hello,
I have noticed that directLFQ does not filter out shared peptides from the DIA-NN output so the quant can be highly misleading for certain protein families. I can use the generic input format with the precursors table as a work-around, but it would be great to filter for proteotypic peptides only by default or as an optional parameter if possible.
Thanks!

Hi Rob,
thanks a lot for your input! Indeed we do not filter out any peptides based on this criterium. The reasoning behind this is, that when we use the Protein.Groups column every peptide maps to only one protein group. So the mapping is unique, but indeed it can be that the assignment of the protein group is wrong. So it would be good to have an option to filter for proteotypic peptides and I will include it in the next releases. Another option to filter now is to subset the DIA-NN report.tsv to only prototypic peptides, save it and feed that directly into directLFQ.
Best&thanks
Constantin

Hi Rob,
in the new directLFQ version there the now the switch 'filter_dict', where you can specify individual filters as a dictionary. In the Python API you can for example do something like this:
filter_dict={'proteotypic_filter' :{'param' : 'Proteotypic','comparator': '==', 'value': 1}}
directlfq.lfq_manager.run_lfq(.....,filter_dict = filter_dict)
In the CLI and GUI, you need to specify this as a .yaml file (see also GitHub docu). Hope this works for you? I did not include the proteotypicity filter as a default because I think this is too stringent. There I would rely on the parsimony principle usually applied for the grouping (see response above)
Best & thanks
Constantin

Hi Constantin,
Thanks very much for adding this filter. I will give the new version a try.
Rob


post request available (not get method) ??

every example from google,, use get method request,,
but i need post request.. send data with url..
how can i send data when url request??

I actually need that too. How can I have
page.open('example.com', function (status) { ... });

send a POST request instead of GET?


keep sarama default setting ,use hash key for partition

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.weixian.cxy seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.

LGTM

Cloud you merge the main branch of upstream to trigger CI process ?
Please add change log.

git remote add upstream git@github.com:alibaba/ilogtail.git
git fetch upstream
git merge upstream/main
git commit -am "some git logs"
git push origin keep_default_hashkey_partiton


remote validation limited support on rest style URL

For rest style URLs, normally they are the combination of baseURL and resource ID.
E.g. http://xxx.com/books/1
And the resource ID normally populated with the input's value.
In this case, an interface to manipulate the URL is required. But currently this is not supported in remote validator. Can this be added?

This is now easy to do in master, with url: "http://api/checkvatid/{value}"


Remove cas-server-support-console

Strongly consider removing cas-server-support-console subproject as similar capability is provided by Boot's remote shell subsystem and then some, out of the box: http://docs.spring.io/spring-boot/docs/current/reference/html/production-ready-remote-shell.html
My reasoning is well-known: 1) Don't re-invent the wheel 2) Less custom code to maintain == less bugs; less liability. 3) Use best tools available out there.

Good. I'll get to it today

Caveat: Remove all the code, but not the module perhaps. Not sure yet, but we probably would want to have the module pull in the right boot dependencies and make them streamlined with other config and we probably may want to make the behavior of the module a bit more CAS specific. Otherwise, it would be up to the overlay to configure things.

I'd personally lean towards - just leave it up to overlay/local build to configure Boot's shell. Besides, this kind of a need (get into the server internals via remote shell) would be a "niche" use case, etc.

But sure, I'll remove the code, PR, and we take it from there...

I don't mind the overlay to make the decision on whether a shell is required or not. But I don't want the overlay to configure the internals of the shell configuration. I would not want an adopter to figure out which boot module must go in, what boot version, how to resolve conflicts, how to configure things, where to find docs on this stuff, who maintains the docs, etc. All they should need to do is declare a single CAS module that [re]configures everything needed. If the adopter needs it, they can always declare or undeclare the module, but they should not have to do any more than that. This is similiar to how we do things with Spring session where CAS modules simply act as mere wrappers, enabling/massaging functionality already available. (Another advantage of the module is that it makes it more of a "CAS feature", rather than a "boot feature" which is a big :trophy:  )

+1


Updating staging & perf01 grinder numbers to match new query rates in prod

Now that lbaas has stopped their queries we are now running 1 mplot/minute per db node.

+1


LESS

Would you be interested in having someone port this to LESS?

That would be great!

Cool I will work on it over the weekend proably.

Awesome, thanks

Where can I find the LESS port of this library?

Hi @goodpixels! Unfortunately it doesn't exist right now, and I don't use LESS


Added support for array-subset

Demo:
OK:
rio ~/rio/tests/integration bin/asynit Api/ProjectTest.php
Asynit Test suite

.                                              1 / 1 (100%)

Time: 0.32 seconds, Memory: 5.79MB

OK, Tests: 1, Assertions: 27.

KO:
rio ~/rio/tests/integration bin/asynit Api/ProjectTest.php
Asynit Test suite

F                                              1 / 1 (100%)

# Failures:

1) Rio\Tests\Api\ProjectTest::test_greg_can_get_orpis_project failed

bovigo\assert\AssertionFailure: Failed asserting that an array has the subset Array &0 (
    'inTrial' => true
)
--- Expected
+++ Actual
@@ @@
   'schedule' => NULL,
   'legacyCloudflareScript' => false,
   'subscription' => false,
-  'inTrial' => true,
+  'inTrial' => false,
 )
 in Api/ProjectTest.php:51 at /home/rio/rio/tests/integration/vendor/jolicode/asynit/src/Assert/Assertion.php:73

#0 Asynit\Assert\Assertion->evaluate() at /home/rio/rio/tests/integration/vendor/jolicode/asynit/src/Assert/AssertCaseTrait.php:576
#1 Asynit\TestCase->assert() at /home/rio/rio/tests/integration/vendor/jolicode/asynit/src/Assert/AssertCaseTrait.php:563
#2 Asynit\TestCase->assertArraySubset() at /home/rio/rio/tests/integration/Api/ProjectTest.php:51
#3 Rio\Tests\Api\ProjectTest->test_greg_can_get_orpis_project() at n/a:n/a
#4 Generator->send() at /home/rio/rio/tests/integration/vendor/amphp/amp/lib/Coroutine.php:118
#5 Amp\Coroutine->Amp\{closure}() at /home/rio/rio/tests/integration/vendor/amphp/amp/lib/Internal/Placeholder.php:149
#6 Amp\Coroutine->resolve() at /home/rio/rio/tests/integration/vendor/amphp/amp/lib/Coroutine.php:123
#7 Amp\Coroutine->Amp\{closure}() at /home/rio/rio/tests/integration/vendor/amphp/amp/lib/Internal/ResolutionQueue.php:70
#8 Amp\Internal\ResolutionQueue->__invoke() at /home/rio/rio/tests/integration/vendor/amphp/amp/lib/Internal/Placeholder.php:149
#9 Amp\Coroutine->resolve() at /home/rio/rio/tests/integration/vendor/amphp/amp/lib/Coroutine.php:123

Time: 0.37 seconds, 6.03MB

Failed, Tests: 1, Assertions: 26.

Hello @mikey179 ; Did you miss this PR? Thanks

Hello @mikey179 ; Did you miss this PR? Thanks

Sorry, I'm still out due to sickness reasons (not Covid related), but hopefully will return next week. Might take me a while to catch up with everything, so don't hold your breath for the next few days. :-)

Sorry, I'm still out due to sickness reasons (not Covid related), but hopefully will return next week. Might take me a while to catch up with everything, so don't hold your breath for the next few days. :-)

No problem, there is no rush :)
Take care of you, it's the most important 👍🏼

Sorry for not getting to this earlier, took me a bit longer than expected to catch up. Will have a look right now...

Hello, I pushed a new version, where I hope I addressed your comments :) Could you give a second review?
Thanks

Merged and released.


Query, Mutation, Subscription code are not generated from codegen (Android)

Note: If your question is regarding the AWS Amplify Console service, please log it in the
official AWS Amplify Console forum

Which Category is your question related to?
Codegen
Amplify CLI Version
4.20.0
What AWS Services are you utilizing?
AppSync, Amplify
Provide additional details e.g. code snippets
I have my schema.graphql file ready in my android project with my mutation and query and also data types(I didnt put the full file but just piece of it):
type Queue {
}

type Mutation {
	addQueue(input: AddQueueInput!): Queue
}

type Subscription {
	onAddQueue(customerId: ID!): Queue
		@aws_subscribe(mutations: ["addQueue"])
	onDeleteQueueEntity(queueId: ID!): String
		@aws_subscribe(mutations: ["deleteQueueEntity"])
}

After executing the codegen gradle task (in the terminal it shows codegen is successful), i can see only the model classes are there,  however , there are no mutation and query and subscription code.
I can see a empty Mutation.java/Query.java/Subscription.java file with nothing inside:

Noted im not using any directive in our schema.graphql file since we are not planning to use dynamodb or any other feature directive provides.
Thanks!

Hello @richardissuperman
Are you referring to generate models in the getting started guide? If so this is used mainly for DataStore projects as the modelgen works on @model based schemas. If you are looking to generate code for your own schema that does not use @model we do have a code-gen getting started guide for android. Docs: https://docs.amplify.aws/cli/graphql-transformer/codegen#android-usage
The CLI builds GraphQL files from the schema and provides another gradle plugin script which creates java classes.

@SwaySway thanks, but i still dont find any other option, when i execute:
amplify codegen

It generates the graphql mutation/query/subscription files but not the java classes:

Other than this command i dont see other scripts available . Also its pretty inconsistent on why it was still using AppSyncClient but not Amplify.API in this doc:
https://docs.amplify.aws/cli/graphql-transformer/codegen#sample
Not sure what is the recommended way?
thanks!

Did you add the following dependency?
classpath 'com.amazonaws:aws-android-sdk-appsync-gradle-plugin:2.6.+'

@SwaySway yes i did

@SwaySway is there any example or doc for non-datastore project?

@SwaySway Hi There, we are still not able to find a way to generate our Query/Mutation/Subscription without using @model directives. Please help and provide some hints on how to do that? thanks~

@richardissuperman
I was unable to repro this below is the schema I used
type Member {
  id: ID!
  name: String!
}
input CreateMemberInput {
  id: ID!
  name: String!
}
# used a lambda function as the datasource
type Mutation {
  createMember(input: CreateMemberInput!): Member @function(name: "myFunction-${env}")
}
type Query {
  getMember(id: ID!): Member @function(name: "myFunction-${env}")
}

type Subscription {
	onCreateMember(id: ID!): Member
		@aws_subscribe(mutations: ["createMember"])
}

Running amplify codegen generated the graphql files located in app/src/main/graphql/com/amazonaws/amplify/generated/graphql then after running a project build the generated java classes were located in app/build/generated/source/appsync
Does running amplify codegen generate the necessary graphql files?
We also have docs on how to setup a non datastore project with amplify.
Docs: https://docs.amplify.aws/lib/project-setup/create-application/q/platform/android#n1-create-a-new-project

@SwaySway I do see those graph ql files  after running amplify codegen

But i dont see anything under app/build/generated/source/appsync there is no appsync folder after i click make project, is that the project build you are talking about?

Generally speaking, even if the query/mutatuon/subscription classes are generated, but looks like both Amplify.API and Amplify.DataStore’s API are model driven which is not like the normal Apollo GraphQL java client (or appsync client) which is more Query/Mutation/Subscription driven. How can we make use of those generated Query/Mutation/Subscription classes?

Transferring this issue to the android team as this question seems related to the library.


Fix K8s version for Tinkerbell E2E test

Description of changes:
'TestTinkerbellKubernetes131UbuntuWorkerNodeUpgrade' was using the wrong K8s version during init. Fix the test to use the template form the expected K8s version which 1.31.
Testing (if applicable):
Documentation added/planned (if applicable):
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

/lgtm
/approve


Options to keep the dropdown menu open

Right now, the menu closes when a selection is made, and also when there's a mouse click outside anywhere on the screen.
We need two new options:
close_menu_after_selection: Defaults to false. If true, the dropdown menu stays open after an option is selected.
Use case: You type something to filter the options, then want to select several from the filtered list in quick succession. Right now you have to do it one by one, which is very cumbersome.
persistent_menu: Defaults to false. If true, the menu stays open and needs to be closed programmatically.
Use case: Right now there's no way to inspect the HTML markup of the dropdown field options, because the menu automatically closes when using the Inspect Element tool in Chrome. So we can't write tests for components that use LiveSelect!

First option: sounds like a good idea, thanks! I'll work on it.
Second option: not sure why you need this for "writing tests". What kind of tests are you talking about here? An automated test can always inspect the generated DOM after a browser event, and this is unrelated to Chrome devtools.
However, if you want to manually inspect the dropdown content in Chrome devtools, you can use this simple technique.

Hi there. Any development on this issue?

hi @egeersoz. Unfortunately, I have 0 bandwidth to work on this right now. You're free to take a stab at it though, if you want to.Thx


ESP32 BLE Mesh Bridge example crashing (CON-1004)

The BLE Mesh Bridge example crashes upon startup and then restarts.

Environment

ESP-Matter Commit Id: 52a95ea
ESP-IDF Commit Id: 6b1f40b9bf
SoC (eg: ESP32 or ESP32-C3): ESP32-C3
Device Logs (Please attach the log file):
Host Machine OS: Ubuntu 22.04

Looks like you didn't set the DeviceInstanceInfoProvider for in your code. Are you using custom device instance info provider in your example? if yes, please call esp_matter::set_custom_device_instance_info_provider() before your call esp_matter::start().

The example hasn't been modified in any way. If the external platform is removed, it won't restart.

@tomlinyama The issue is fixed by this commit: https://github.com/espressif/esp-matter/commit/668e22da6fca1092e43fbf8fe615db71b9b78e2d, please try again.


param.grad is None when using CNN model in model-centric example

Description
I changed the model in model-centric federated learning example (01-Create-plan-Copy1.ipynb) to a CNN-based model:
class Net(nn.Module):
    def __init__(self):
        super(Net, self).__init__()
        self.conv1 = nn.Conv2d(1, 32, 3, 1)
        self.conv2 = nn.Conv2d(32, 64, 3, 1)
        self.dropout1 = nn.Dropout(0.25)
        self.dropout2 = nn.Dropout(0.5)
        self.fc1 = nn.Linear(9216, 128)
        self.fc2 = nn.Linear(128, 10)

    def forward(self, x):
        x = self.conv1(x)
        x = F.relu(x)
        x = self.conv2(x)
        x = F.relu(x)
        x = F.max_pool2d(x, 2)
        x = self.dropout1(x)
        x = th.flatten(x, 1)
        x = self.fc1(x)
        x = F.relu(x)
        x = self.dropout2(x)
        x = self.fc2(x)
        output = F.log_softmax(x, dim=1)
        return output

and changed the X to the correct shape:
X = th.randn(3, 1, 28, 28)

However, when executed training_plan.build, it failed:
<ipython-input-19-0bbb2467578c> in naive_sgd(param, **kwargs)
      1 def naive_sgd(param, **kwargs):
----> 2     return param - kwargs['lr'] * param.grad
...
TypeError: mul(): argument 'other' (position 1) must be Tensor, not NoneType

It looks like the parameter's grad is None.
Is this because the current version of PyGird does not support CNN model ? How to solve this problem? Thanks.
System Information

OS: Ubuntu-20.04
Language Version: Python 3.6

0.2.x is no longer supported. Please refer to the new 0.5 release.


Filter out system dbs from create project from db dialog

This PR fixes https://github.com/microsoft/azuredatastudio/issues/15396
before:

after:

Pull Request Test Coverage Report for Build 900871154

2 of 3 (66.67%)  changed or added relevant lines in 2 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.0007%) to 43.427%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

extensions/sql-database-projects/src/dialogs/publishDatabaseDialog.ts
0
1
0.0%

Totals

Change from base Build 900862881:
0.0007%

Covered Lines:
26574

Relevant Lines:
55610

💛  - Coveralls


Why is get() used when processing effects

https://github.com/modderme123/reactively/blob/9081fa4bf302a5f768962e0a4421a28d705439ff/packages/core/src/core.ts#L318
Wouldn't EffectQueue[i].updateIfNecessary() achieve the same behavior while doing a bit less work?

Yes. However, updateIfNecessary is currently internal (private), and the scheduler is a bit more external and (somewhat intentionally) cannot access all of the internals.


Add codacy badge

Coverage remained the same at 83.091% when pulling 45535e9c1b86c9a903b1133ac8677d595fae946f on Google-Cal-Api into cd5735aacc392bb6aaf7bba81ea458d40a7a25c0 on master.


No useable alternative to Contributor rights

Repeatedly this page says:

"You don't need to grant the user-assigned managed identity contributor rights on the resource group to deploy a VM to an existing virtual network.  However, the user-assigned managed identity needs the following Azure Actions permissions...

This information is not usable.  The Azure portal (1) does not allow direct selection of Azure Action permissions and (2) does not reveal what Azure Actions are associated with any given role.  Furthermore, this page does not suggest what example role can be selected that fulfills the intended "least privilege" strategy.
The best option I have found for helping this documentation be relevant, is this MS-employee personal project website..  This website allows finding a role, based on an Azure Action.  However, even with this tool I was unable to make this MS documentation useable.  For example, the documentation says I need the Azure Action Microsoft.Compute/images/delete, but when I use the aforementioned website to locate a role which has that Action...it finds nothing.
Thus this documentation either (1) needs to provide a tool or further documentation that explains exactly how to use Actions to look up a pertinent role or (2) it needs to remove references to "you don't need contributor" rights.  Right now, the only way to achieve anything this page claims...is to assign contributor rights.

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

ID: 2126bd34-1166-5fe1-0d8c-e6ffe8ab5477
Version Independent ID: 0871f20e-a04f-4afb-36a7-8e4fcab132cf
Content: Configure Azure VM Image Builder permissions by using the Azure CLI - Azure Virtual Machines
Content Source: articles/virtual-machines/linux/image-builder-permissions-cli.md
Service: virtual-machines
Sub-service: image-builder
GitHub Login: @kof-f
Microsoft Alias: kofiforson

@brentarias
Thanks for your feedback! We will investigate and update as appropriate.

@brentarias
I'm going to assign this to the document author so they can take a look at it accordingly.
@kof-f
please review it.

Thanks for your contribution to our documentation
We sincerely apologize for the delayed response. Unfortunately, we have been unable to review this issue in a timely manner. However, we are making overall enhancements to our content. We are closing this issue for now as there has been no activity for a while. If you feel that the problem persists, please respond to this issue with additional information.
?
Please continue to provide feedback about the documentation. We appreciate your contributions to our community.
#please-close


In dataprep, I wish we have a function like format_number()

Is your feature request related to a problem? Please describe.

Doesn't it look like a bug?
Describe the solution you'd like
Spark has a built-in function for this.
https://spark.apache.org/docs/latest/api/sql/index.html#format_number
I wish we have this too.

My name daud I'm 21 old i need your support for my account to be available online market services and on adding cart


Bug try to fix the coredump of streambyte decode of sse

Proposed changes
Issue Number: close #xxx

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

run buildall


ssl error page

Project: https://app.asana.com/0/1177771139624306/1206753149050909/f
Task: https://app.asana.com/0/0/1206830346637938/f

#945
#939  👈
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @SabrinaTardio and the rest of your teammates on  Graphite


fix(main-content): set overflow to auto

https://github.com/altence/lightence-admin/issues/154

closes #154


Is't possible to use data retrieved from Fluidity into Umbraco document type and API?

Is't possible to use data retrieved from Fluidity into Umbraco backend ( for example into a document type ) and API ( alternative via PETA POCO )?

If you need to link to an entity in umbraco then fluidity comes with an entity picker property editor you can configure. Docs here https://umco.github.io/umbraco-fluidity/property-editors/entity-picker/
In terms of accessing data directly from Fluidity repositories then you can do that also. Docs here https://umco.github.io/umbraco-fluidity/api/repositories/#accessing-a-repository-in-code


Using Proxy Service in Safari throws an error if called from an Injected script

First off, thank you so much for this amazing package. I've refactored my codebase to be much more manageable and straightforward.
However, I did notice this one issue where you call a registered Proxy Service from an Injected script's UI (using React, not sure if that matters) and it throws this error. Any idea on what might be causing it? The error does not appear in Safari's console.
This works flawlessly on Chrome.
Thanks!

This package uses the webextension-polyfill, which has some known issues with Safari and messaging. Add this code at the beginning of your background script: https://github.com/mozilla/webextension-polyfill/issues/234#issuecomment-702403327

mozilla/webextension-polyfill#234 (comment)

added this, but it's still encountering the same error

Hmm, then I'm not sure. The error message isn't providing any useful information, so I don't even know where the problem might be

I think it has to do with Safari service workers being non-responsive: https://developer.apple.com/forums/thread/764594 and not with your package itself.

OK, then I'm gonna close this issue. If you find out more and it is related to this package, feel free to reopen.


python312Packages.python-homewizard-energy: 6.3.0 -> 6.3.0

Diff: https://github.com/DCSBL/python-homewizard-energy/compare/refs/tags/v6.3.0...v6.3.0
Changelog: https://github.com/homewizard/python-homewizard-energy/releases/tag/v6.3.0
Description of changes

Things done

Built on platform(s)

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

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

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

5 packages built:

home-assistant-component-tests.homewizard
python311Packages.python-homewizard-energy
python311Packages.python-homewizard-energy.dist
python312Packages.python-homewizard-energy
python312Packages.python-homewizard-energy.dist


Add StringFormat to TextColumn<TModel,TValue> options

I can not control the string format when display double number data, so add a StringFormat to TextColumn's options will be nice.
Is this suitable for TreeDataGrid? If so, I can create a pr to do that.

I'd also very much like this feature and would be willing to contribute to it, if it's feasible according to the main devs.


Recompiles Thrift plugin integration tests for libthrift v0.10.0+

Thfit v0.10.0 introduced breaking changes to generated AsyncIface methods. Thrift plugin integration tests implement and invoke these methods so changes have been made.
Unfortunately, this means binary incompatibilitiy with previous libthrift versions so integration tests for 0.9.x libthrift are removed.

Current coverage is 39.94% (diff: 100%)

Merging #2533 into master will increase coverage by 0.03%

@@             master      #2533   diff @@
==========================================
  Files          1696       1696
  Lines         59614      59614
  Methods       11568      11568
  Messages          0          0
  Branches       8311       8311
==========================================
+ Hits          23794      23815    +21
+ Misses        35820      35799    -21
  Partials          0          0

Powered by Codecov. Last update d71f442...6bc18f9


Discussion of pebble movement infrastructure

This issue is for workshopping the broader code infrastructure didymus will use for moving pebbles within an active core.  While there will be multiple modes of movement, there will be a necessity for tracking pebble data that they will share (at the very least).
didymus will need to track:

pebble material
a pebble's unique ID, which should not change over the pebble's lifetime
number of passes each pebble has made (for a mulitpass cycle)
If a pass would cause a pebble's material to change (for example, if material is determined by pass, and a pebble leaves its first pass and goes to its second) then didymus needs to be able to recognize this, identify what material it currently is, and update it to the corresponding new material
pebble discharge criterion (once a pebble has been discharged, should its unique ID be retired as well, or reused?) (should didymus create some sort of output tracking pebbles that exit the core, and when?)

(this initial list may be updated if more things to track are thought of)

pebble material

less get some more fidelity on what this means.... maybe material composition/isotopic vector (or what Cyclus calls "compID") ?

a pebble's unique ID, which should not change over the pebble's lifetime

yes

number of passes each pebble has made (for a mulitpass cycle)

yes

If a pass would cause a pebble's material to change (for example, if material is determined by pass, and a pebble leaves its first pass and goes to its second) then didymus needs to be able to recognize this, identify what material it currently is, and update it to the corresponding new material

all passes will change the material composition
definitely review cyclus approach here

pebble discharge criterion (once a pebble has been discharged, should its unique ID be retired as well, or reused?) (should didymus create some sort of output tracking pebbles that exit the core, and when?)

do not reuse unique ids.

This issue can be closed with a short description of the proposed structure of capabilities to be implemented in didymus and discussion of complementary capabilities potentially to be implemented in other tools. This could be executed as a .rst file in the docs directory of didymus.


Fix Tacotron2 inference example

the wavernn_vocode called on line 327 is missing the wavernn_checkpoint_name argument, this PR fixes this
also refactored the function call griffin_lim_vocode on line 338 so that it is more readable

Cannot tell if this is the right signature from the PR but otherwise it looks good. Token approval.

Thanks for the reminder, I've rerun the speech generation script for all three vocoders and they worked.


Make CLI option shortcuts more predictable

Some of the CLI options have shortcut forms. For instance, --renderer is -r and --source-root is --src. However, some of the shortcuts are less intuitive, such as -t for --request.
We should make the option shortcuts more intuitive.
This might be an API breaking change, so it should be treated with caution.

@armiol, assuming we agreed to have a YAML configuration file instead of a bunch of shortcuts, this issue is going to be resolved by itself.
@dmdashenkov, I could not find an issue on YAML. Please link this one to that one.

Closing as outdated since options were reworked significantly recently.


Invalid platform

I'm trying to build osx app on ubuntu and I'm getting an error:
electron-builder \"dist/osx/MyApp.app\" --platform=osx --out=\"dist/osx\" --config=packager.json
- Running electron-builder 2.4.0
/usr/local/lib/node_modules/electron-builder/cli.js:40
    throw error;
    ^

Error: Invalid platform.
    at Object.OSXBuilder.build (/usr/local/lib/node_modules/electron-builder/lib/osx.js:28:24)
    at Object.Builder.build (/usr/local/lib/node_modules/electron-builder/index.js:74:42)
    at Object.<anonymous> (/usr/local/lib/node_modules/electron-builder/cli.js:36:9)
    at Module._compile (module.js:434:26)
    at Object.Module._extensions..js (module.js:452:10)
    at Module.load (module.js:355:32)
    at Function.Module._load (module.js:310:12)
    at Function.Module.runMain (module.js:475:10)
    at startup (node.js:118:18)
    at node.js:952:3

My packager.json is exactly the same as in your readme example.

The error message isn't very helpful, but it's from node-appdmg and it mean that there is no way to build dmg on non-osx.

Look at https://github.com/LinusU/node-appdmg/issues/14 for details.

I think I'll close this one for now as there is no way to fix it here. :(
Feel free to reopen later on. :)

@stefanjudis is there this info in the readme?


Nashorn is Null error when running through mvn terminal

karate_framework2.zip
I have a karate 0.9.9.RC3 project with Java 11, tests run correctly if running directly through runner, however if I chose to run through 'mvn test' I get below error:
java.lang.ExceptionInInitializerError
at examples.ExamplesParallelTest.testParallel(ExamplesParallelTest.java:14)
Caused by: java.lang.NullPointerException: Cannot invoke "javax.script.ScriptEngine.createBindings()" because "com.intuit.karate.ScriptBindings.NASHORN" is null
at examples.ExamplesParallelTest.testParallel(ExamplesParallelTest.java:14)

you still have karate-apache in your pom.xml, you don't need it. read the docs: https://github.com/intuit/karate/wiki/1.0-upgrade-guide#breaking-changes

Putting the latest dependency 0.9.9.RC4 and just keeping one dependency only karate-junit4 solved this problem as mentioned at the link shared by @ptrthomas Thank you
<dependency>
        <groupId>com.intuit.karate</groupId>
        <artifactId>karate-junit4</artifactId>
        <version>0.9.9.RC4</version>
        <scope>test</scope>
    </dependency>


WhitePaper and YellowPaper for Dothraki language

Changes

Add WhitePaper markdown in the Dothraki language
Add YellowPaper markdown in the Dothraki language

Nice contribution : )
But I don't think there will be any hours rewarded for fictional languages.
https://github.com/MorpheusAIs/Morpheus/blob/main/!KEYDOCS README FIRST!/8.Code Contributor Best Practices.md
You can update the pull request and I'll merge the language but I'm not credited hours : )

I have resolved the conflicts.

Thanks : )


Running Xelmish on androi

Is it possible to run a Xelmish game on android?
I assume yes, but my attempts so far have not gotten anywhere near successful.

Hi @kaeedo! I would assume not, since Xelmish is built using dotnet core and dotnet core does not compile on Android.
That being said, I am sure you could do something crazy hacky to get it running but I have not tried; if you want to have a go, this repo looks like a good first step: https://github.com/qmfrederik/coredroid


Other projects? Lay of the land?

Hi, thank you for the project!
I came across your project looking to get a friendly way to do lucene-style queries in input boxes (and also provide at AST of query itself).
Are their similar projects out there you've found that are actually active? Planning on continuing yours?
Parsing

search-input-query-parser (here): npm, repo
lucene-kit: npm, repo
The underlying parsing projects that rely on PEG grammars are in bad shape. Lots of abandoned projects, or they don't work with TypeScript, or ESM.

Searching

search-input-query-react (here): npm, repo
react-structured-search: npm, repo

P.S. You Look prodigy level at TypeScript search parsing and inputs. I see https://github.com/williamcotton/guish also.

Thanks for the high-level view of other related projects, I'm definitely interested in seeing some other approaches. Your research has probably led you to know more about the landscape than I do!
Yes, I am planning on continuing development, and the impetus is that we're actively using this parser and React component at my workplace.
I'd say at this point in the development process that this should be considered alpha software. I plan on doing a launch on HackerNews at some point after the holiday season.
I hope you're doing well and think you for the kind words!


[stdlib] Freeze some internal std lib protocols

Builds on #32887
Freezes three internal protocols to reduce memory use.
rdar://problem/65642583

@swift-ci please benchmark

@swift-ci please test

@swift-ci please benchmark

Build failed
Swift Test Linux Platform
Git Sha - 9991addaaa280f9bc30124910ac54467385aa85d

Build failed
Swift Test OS X Platform
Git Sha - 9991addaaa280f9bc30124910ac54467385aa85d

Performance: -O

Regression
OLD
NEW
DELTA
RATIO

ObjectiveCBridgeFromNSArrayAnyObjectForced
4600
5080
+10.4%
0.91x (?)

Prims.NonStrongRef.UnownedUnsafe
256
281
+9.8%
0.91x (?)

Prims.NonStrongRef.UnownedUnsafe.Closure
257
282
+9.7%
0.91x

Breadcrumbs.MutatedIdxToUTF16.Mixed
431
467
+8.4%
0.92x (?)

Breadcrumbs.MutatedUTF16ToIdx.Mixed
422
456
+8.1%
0.93x

Improvement
OLD
NEW
DELTA
RATIO

ArrayInClass
1655
1540
-6.9%
1.07x (?)

DistinctClassFieldAccesses
331
308
-6.9%
1.07x

Array2D
7216
6720
-6.9%
1.07x (?)

StringBuilderWithLongSubstring
1810
1690
-6.6%
1.07x (?)

Code size: -O
Performance: -Osize

Regression
OLD
NEW
DELTA
RATIO

FlattenListFlatMap
4720
5462
+15.7%
0.86x (?)

DataAccessBytesMedium
91
100
+9.9%
0.91x (?)

Breadcrumbs.MutatedUTF16ToIdx.Mixed
418
453
+8.4%
0.92x (?)

Breadcrumbs.MutatedIdxToUTF16.Mixed
432
465
+7.6%
0.93x (?)

Improvement
OLD
NEW
DELTA
RATIO

Data.hash.Empty
77
71
-7.8%
1.08x

Code size: -Osize
Performance: -Onone

Regression
OLD
NEW
DELTA
RATIO

String.data.Empty
42
47
+11.9%
0.89x (?)

String.data.Small
45
50
+11.1%
0.90x (?)

Improvement
OLD
NEW
DELTA
RATIO

ObjectiveCBridgeStubFromNSDate
6780
5840
-13.9%
1.16x (?)

UTF8Decode_InitFromData_ascii_as_ascii
673
618
-8.2%
1.09x (?)

Code size: -swiftlibs

How to read the data
The tables contain differences in performance which are larger than 8% and
differences in code size which are larger than 1%.
If you see any unexpected regressions, you should consider fixing the
regressions before you merge the PR.
Noise: Sometimes the performance results (not code size!) contain false
alarms. Unexpected regressions which are marked with '(?)' are probably noise.
If you see regressions which you cannot explain you can try to run the
benchmarks again. If regressions still show up, please consult with the
performance team (@eeckstein).

Hardware Overview
  Model Name: Mac Pro
  Model Identifier: MacPro6,1
  Processor Name: 12-Core Intel Xeon E5
  Processor Speed: 2.7 GHz
  Number of Processors: 1
  Total Number of Cores: 12
  L2 Cache (per Core): 256 KB
  L3 Cache: 30 MB
  Memory: 64 GB

@swift-ci please test

Build failed
Swift Test Linux Platform
Git Sha - a03c5c2accd7ee3644e1bafabbaf387b0cdbc97f

Build failed
Swift Test OS X Platform
Git Sha - a03c5c2accd7ee3644e1bafabbaf387b0cdbc97f

@swift-ci please test macOS platform

Build failed
Swift Test OS X Platform
Git Sha - 399683eb092190287250dc9c276b8e5c16ad011e

@swift-ci please test macOS platform

Build failed
Swift Test OS X Platform
Git Sha - 399683eb092190287250dc9c276b8e5c16ad011e

@swift-ci please test

Build failed
Swift Test OS X Platform
Git Sha - 399683eb092190287250dc9c276b8e5c16ad011e

@swift-ci please test

Build failed
Swift Test Linux Platform
Git Sha - 399683eb092190287250dc9c276b8e5c16ad011e

Build failed
Swift Test OS X Platform
Git Sha - 399683eb092190287250dc9c276b8e5c16ad011e

@swift-ci please test macOS

Build failed
Swift Test OS X Platform
Git Sha - 1ffd4233bbcd732b07449f05d7d23dcaf1cc9b9a

@swift-ci please test

Build failed
Swift Test OS X Platform
Git Sha - 219d2218a239ac9c12b5bf7b11bd8231bb22e668

@swift-ci please test

Build failed
Swift Test OS X Platform
Git Sha - 219d2218a239ac9c12b5bf7b11bd8231bb22e668

Build failed
Swift Test Linux Platform
Git Sha - 219d2218a239ac9c12b5bf7b11bd8231bb22e668

@swift-ci please clean test macOS

Build failed
Swift Test OS X Platform
Git Sha - 05a7d923349059e5ebd3b7523ba7dc60e7cba039

Please update the base branch to main by Oct 5th otherwise the pull request will be closed automatically.

How to change the base branch: (Link)
More detail about the branch update: (Link)


Add question of poll for other variants of results

Issue has been fixed in https://github.com/SecondThundeR/secondthunder-js-bot/commit/3ddc93ca8ee56247c572127b5d6ab4938111b278


Apply latest open source development

Can you please pull the latest fixes for the last year?

Closed because other pulls are pending with same content.