only available returns are cumprod

Currently the only returns available are cumulative products.
I couldn't find any alternative to Calculations().create_mult_index() for cumulative sums
Suggest cumulative sum flag when calculating backtest cumulative PnL

I think that's a good idea @flipdazed. I had already started to add this functionality to the QuickCharts class. I'll add it to the backtest too, as a flag. I can add it to the BacktestRequest as a flag for the user to set.

@flipdazed I've added a cumulative sum flag to BacktestRequests (and added the associated method in Calculations in findatapy.
eg. br.cum_index = 'mult' # 'mult' or 'add'


Add option {ast:bool} to take, fix take(n)

take(n) now calls read(null, cb) exactly n times.

Will be replaced with another PR in a sec.


[HotFix] [E2E] Fix config not suite for zeta parser

Purpose of this pull request

Check list

[ ] Code changed are covered with tests, or it does not need tests for reason:
[ ] If any new Jar binary package adding in your PR, please add License Notice according
New License Guide
[ ] If necessary, please update the documentation to describe the new feature. https://github.com/apache/incubator-seatunnel/tree/dev/docs
[ ] If you are contributing the connector code, please check that the following files are updated:

Update change log that in connector document. For more details you can refer to connector-v2
Update plugin-mapping.properties and add new connector information in it
Update the pom file of seatunnel-dist

[ ] Update the release-note.

same with #4536


Use ChunkFive Ex font

With permission of Meredith Mandel, the original author of the ASCII-Font Chunk Five, I have extended Chunk Five Ex to a full featured unicode font with all figures used in latin and cyrillic writing. All latin and cyrillic extensions as well as a lot of letterlike symbols will make this to one of the most complete fonts I offer here.

http://www.dafont.com/chunkfive-ex.font
This should make international font support a lot better.

Is this available for using in web browser?

I don't know, I couldn't work it out and don't know much about webfonts.

couldn't find any useful information, I guess it not supported to be used in defferent browsers

Will consider this in a future redesign.


[4.0] CI: Change GODOT_BASE_BRANCH to 4.0, checkout that branch for godot-cpp

Thanks! Keep in mind that the engine version needs to be guarded as a string, otherwise builds will fail for numeric versions (but master is obviously fine).


Allow default values in hana define struct

Current usage looks like this:
struct Person {
    BOOST_HANA_DEFINE_STRUCT(Person,
        (std::string, name),
        (int, age)
    );
};

It's not clear from this whether the members will be declared as int age; or int age{};. Either way, one can't easily control the behavior. You can write a default constructor for Person by hand, but this involves repeating all the members and still has some limitations where multiple constructors are involved compared to inline initializers. Inline initializers are a fantastic feature and it would be fantastic to be able to simply write:
struct Person {
    BOOST_HANA_DEFINE_STRUCT(Person,
        (std::string, name, "Bob"),
        (int, age, 42)
    );
};

Or something similar (you could for example, make the user write anything they want to be appear between the variable name and the semi colon, so it would instead be (int, age, =42)).
This would be very useful for my purposes; I use Hana with POD structs but sometimes it would be nice to control their default construction without lots of boilerplate.

I think your number 2 example (int, age, =42) would be very useful for supporting generalized annotations, such as bitfields where we would write (int, age, :7). There are probably other sorts of annotations out there that could benefit from this.

If you want more control you can simply use BOOST_HANA_ADAPT_STRUCT.
It's slightly more redundant, but another custom macro could easily be created to use it for the above desired interface. There are probably a lot of use cases that could be added to the library, but I suspect it would bloat the interface and add compile time overhead.

@ricejasonf not repeating member variables is one of the main reasons we want reflection in the first place. IMHO, the real use case of adapt struct is for classes/structs you don't control. Define struct is written well to allow you to add methods, aliases, CRTP, etc, anything you want to your class. There's only two things you can't do when you use the define struct, one is have different access levels for different members (which probably isn't sensible), and the other is what's described in the original issue. So, for define struct I don't think there are a bunch of different use cases/features at all, it's really primarily this one and it's really not going to be any dramatic increase in compilation time (it's just a matter of having the macro expand one additional thing).

I should mention that something like
struct myStruct{
 int myArray[40];
}

is not too unreasonable either...
So the proposed macro would be like
struct myStruct{
  BOOST_HANA_DEFINE_STRUCT(myStruct,
    (int, myArray, [40]));
}

in this case, as per @quicknir 's second version, where the annotation goes in the third argument.

It wouldn't be my call to include it in the library. Are you adding a new macro or enhancing the existing one? If it breaks the existing macro it would not likely be accepted.
For the case of the array, why not use std::array<int, 40>?
It would be interesting to see it work with bit fields, but that might require reworking Struct from the ground up.

Here is an example file that supports initialisation such as:
struct workspace_t {

  TUN_DEFINE_STRUCT(workspace_t, (std::string, "workspace", name),
                    (std::string, "", notes), (std::vector<std::pair<win_info_t, int>>, , window_list),
                    (int, 0, counter));
};

Note, you have to specify the initializer, but you may leave it blank. The macro semantics are such that the last two items define the name and the initialiser. The other items specify the type which means that additional commas are OK as per the above example with the more complicated std::vector<std::pair<  type which includes an embedded comma as per the original HANA macro style.
It is just a copy / paste / regex replace from the original BOOST_HANA_DEFINE_STRUCT.
struct_macro_helper.zip

@mjhurd Cool, thanks for providing. @ricejasonf Why not just create a new macro, BOOST_HANA_DEFINE_INIT_STRUCT, similar to what mjhurd has provided? it can be in its own header file. Then there is zero impact on existing compile times etc for people who don't use it. I know the header is long but it is mostly repetitive stuff it seems like (for whatever reason boost hana seems to prefer to define its own Nth version of things rather than lean more on BOOST PP).

I'm looking at using locally-defined structures to describe Python argument parsing defaults. Being able to specify default values would be helpful: these default values would become the default values of the "parameters", which we need for optional parameters.

I think @quicknir is correct that my approach with possible empty initialisers is a bit ugly. Having an optional third parameter for an initialiser that may cope with commas with or without parentheses would be better. Though I'm not a fan of the ()()() approach of a Boost PP sequence. Bad LISP and FP memories ;-)
Here is my somewhat automagically generated from Hana TUN_DEFINE_STRUCT macro you can use until Hana provides something more suitable.
struct_macro_helper.zip


Make cross mapping ratio = 0.1 the default

In theory, this should not be necessary. Already the current default of 0.02 is quite liberal since the cross-mapping ratio between two sequences that have a difference of 1 should be one third of the sequencing error rate.

Closed in favor of #62


Possible problem with the onnx representation

Resolved

Hi @silent-code, curious to know what your issue was? :)

@JaredP94
I seem to be having a similar issue as you where everything with my re-trained network classifies with the class 1 label from the list contained in label.txt:
BACKGROUND
class 1
I thought maybe something was getting messed up in the onnx conversion step so I tested simply converting the base network, mobilenet-v1-ssd-mp-0_675.pth to onnx without doing any re-trainning. It appears to work correctly, classifying multiple classes with expected accuracy. Thus it appears the re-training pipleline should in theory work. This is the issue I resolved.
My next step is to just try using a larger training data set so it learns "not class 1" better, I suppose. Right now, I only have around 100 samples.
Have you made any progress?

Hi @silent-code,
I didn't make any progress on mb1-ssd, but seemed to get everything working using mb2-ssd-lite (more detail here)


Bug: There may be phantom fragments present in the e2e test

Describe the bug
https://buildkite.com/risingwavelabs/pull-request/builds/39536#018cfd06-0bce-4b29-adb4-35d724237d5c
In this test, alter parallelism used rw_fragments to check the parallelism of fragments after scaling (which hadn't been used before), resulting in two excess fragments and leading to a test error. A hot fix from pr #14542 has been applied to avoid this issue, but we should continue to investigate the specific cause.
Error message/log
-08-12T11:53:09.950280Z DEBUG risingwave_simulation::slt: Record Statement { loc: Location { file: "e2e_test/ddl/alter_parallelism.slt", line: 16, upper: None }, conditions: [], connection: Default, expected_error: None, sql: "create table t (v int);", expected_count: None } finished in 204.53815ms
2022-08-12T11:53:24.287452Z DEBUG risingwave_simulation::slt: Running cmd=Others
2022-08-12T11:53:24.287452Z DEBUG risingwave_simulation::slt: retry count iteration=0
2022-08-12T11:53:24.300087Z DEBUG risingwave_simulation::slt: Record Query { loc: Location { file: "e2e_test/ddl/alter_parallelism.slt", line: 19, upper: None }, conditions: [], connection: Default, expected_types: [Text], sort_mode: None, label: None, expected_error: None, sql: "select parallelism from table_parallelism where name = 't';", expected_results: ["AUTO"] } finished in 12.634383ms
2022-08-12T11:53:25.000779Z  INFO risingwave_simulation::cluster: kill frontend-1
2022-08-12T11:53:25.000779Z ERROR risingwave_simulation::client: postgres connection error: connection closed
2022-08-12T11:53:25.171745Z  INFO risingwave_simulation::cluster: kill frontend-2
2022-08-12T11:53:25.273469Z  INFO risingwave_simulation::cluster: restart frontend-2
2022-08-12T11:53:25.945804Z  INFO risingwave_simulation::cluster: restart frontend-1
2022-08-12T11:53:40.945804Z DEBUG risingwave_simulation::slt: Running cmd=Alter
2022-08-12T11:53:41.151871Z DEBUG risingwave_simulation::slt: Record Statement { loc: Location { file: "e2e_test/ddl/alter_parallelism.slt", line: 24, upper: None }, conditions: [], connection: Default, expected_error: None, sql: "alter table t set parallelism = 2;", expected_count: None } finished in 206.067ms
2022-08-12T11:53:41.151871Z DEBUG risingwave_simulation::slt: Running cmd=Others
2022-08-12T11:53:41.151871Z DEBUG risingwave_simulation::slt: retry count iteration=0
2022-08-12T11:53:41.170372Z DEBUG risingwave_simulation::slt: Record Query { loc: Location { file: "e2e_test/ddl/alter_parallelism.slt", line: 27, upper: None }, conditions: [], connection: Default, expected_types: [Text], sort_mode: None, label: None, expected_error: None, sql: "select parallelism from table_parallelism where name = 't';", expected_results: ["FIXED(2)"] } finished in 18.500955ms
2022-08-12T11:53:41.529664Z  INFO risingwave_simulation::cluster: kill compactor-2
2022-08-12T11:53:41.531752Z  INFO risingwave_simulation::cluster: kill frontend-1
2022-08-12T11:53:41.558412Z  INFO risingwave_simulation::cluster: kill compactor-1
2022-08-12T11:53:41.623950Z  INFO risingwave_simulation::cluster: restart frontend-1
2022-08-12T11:53:41.807413Z  INFO risingwave_simulation::cluster: kill frontend-2
2022-08-12T11:53:41.807413Z ERROR risingwave_simulation::client: postgres connection error: connection closed
2022-08-12T11:53:41.947542Z  INFO risingwave_simulation::cluster: restart compactor-1
2022-08-12T11:53:42.190175Z  INFO risingwave_simulation::cluster: restart compactor-2
2022-08-12T11:53:42.579259Z  INFO risingwave_simulation::cluster: restart frontend-2
2022-08-12T11:53:57.579259Z DEBUG risingwave_simulation::slt: Running cmd=Others
2022-08-12T11:53:57.579259Z DEBUG risingwave_simulation::slt: retry count iteration=0
2022-08-12T11:53:57.649849Z DEBUG risingwave_simulation::slt: Record Query { loc: Location { file: "e2e_test/ddl/alter_parallelism.slt", line: 32, upper: None }, conditions: [], connection: Default, expected_types: [Integer], sort_mode: None, label: None, expected_error: None, sql: "select parallelism from rw_fragments;", expected_results: ["2", "2"] } finished in 70.590276ms
2022-08-12T11:53:57.649849Z ERROR risingwave_simulation::slt: failed to run test: query result mismatch:
[SQL] select parallelism from rw_fragments;
[Diff] (-expected|+actual)
+   6
+   6
    2
    2
at e2e_test/ddl/alter_parallelism.slt:32

To Reproduce
seed = 1
--
  | Configuration {
  | config_path: Regular(
  | "src/config/ci-sim.toml",
  | ),
  | frontend_nodes: 2,
  | compute_nodes: 3,
  | meta_nodes: 3,
  | compactor_nodes: 2,
  | compute_node_cores: 2,
  | etcd_timeout_rate: 0.0,
  | etcd_data_path: None,
  | per_session_queries: [],
  | }
  | e2e_test/ddl/alter_owner.slt
  | e2e_test/ddl/alter_parallelism.slt

Expected behavior
No response
How did you deploy RisingWave?
No response
The version of RisingWave
No response
Additional context
No response

Is it possible that the fragment is from a table that's not dropped in another test case? 😕


[GHSA-rfj2-q3h3-hm5j] Cargo extracting malicious crates can corrupt arbitrary files

Updates

CVSS
Severity

Comments
The Security Response WG intentionally marked this vulnerability as "low" severity rather than going with the CVSS assessment, with the following reasoning:

Note that by design Cargo allows code execution at build time, due to build scripts and procedural macros. The vulnerabilities in this advisory allow performing a subset of the possible damage in a harder to track down way. Your dependencies must still be trusted if you want to be protected from attacks, as it's possible to perform the same attacks with build scripts and procedural macros.

This updates the severity of this advisory to reflect the text of the advisory.

Hi there @pietroalbini! A community member has suggested an improvement to your security advisory. If approved, this change will affect the global advisory listed at github.com/advisories. It will not affect the version listed in your project repository.
This change will be reviewed by our highly-trained Security Curation Team. If you have thoughts or feedback, please share them in a comment here! If this PR has already been closed, you can start a new community contribution for this advisory

Rather than erasing the CVSS score to force this to low, I think it would also be possible to change the privileges required to "high" rather than "low". This vulnerability only affects alternate registries, which are currently only used inside companies to host their private packages. There are no public alternate registries I'm aware of. So, to exploit a vulnerability someone would have to have publish access to those packages, which I feel should be marked as high privileges.


Remove useless dependencies

Moved python-dotenv to dev-dependencies and replaced discord and bs4 with discord.py and beautifulsoup4, since discord and bs4 are just mirror packages

This has been addressed with lockfile changed in my branch, this PR can be ignored.

This has been addressed with lockfile changed in my branch, this PR can be ignored.


dts: bindings: Have 'required: true/false' instead of 'category: ...'

The category: required/optional setting for properties is just a
yes/no thing. Using a boolean makes it clearer, so have
required: true/false instead.
The scripts in scripts/dts/ ignore this setting, and only print a
warning if category: required in an inherited binding is changed
to category: optional. Update the code for that warning.
Print a warning if category: ... appears in the settings for a
property, along with a hint to replace it with required: true/false.
The new device tree parser will turn it into an error, and will keep the
hint.
The replacement was done with
git ls-files 'dts/bindings/*.yaml' | xargs sed -i \
    -e 's/category:\s*required/required: true/' \
    -e 's/category:\s*optional/required: false/'

dts/bindings/device_node.yaml.template was updated as well.

There's one more binding format change I want to make after this one, but I'll probably wait until the new parser is in.
The way it's currently used, !include isn't really needed. We could just have
inherits:
    - foo.yaml
    - bar.yaml

That'd get rid of some hairy PyYAML stuff too.

There's one more binding format change I want to make after this one, but I'll probably wait until the old parser is gone.

If you are changing the binding format you should also think about the '#cells' information in the binding. This might become ambiguous if you have several cell based properties in the same binding. It might be better to make it more specific; aka. '#interrupt-cells', '#clock-cells', .... "#cells" may just be the fallback if no specific info is found.

@b0661
Hadn't thought of that. Could look into later.
Wonder if it's caused any workarounds yet.

@galak
Don't think it'll be that bad as long as the error clearly says what needs to change for outdated bindings. Probably doesn't take more than a minute to fix.
If we lock down the format, then we're stuck and can't improve on it.
Not against moving towards some other schema format later. For now, this feels like a small immediate improvement though. Maybe it's already a bit closer too.


Guarding against clojure.core/any?

Guarding against any?, which is part of clojure.core in 1.9.

I tried this, but the any warning still showed up at a bunch of places
lmt
WARNING: any? already refers to: #'clojure.core/any? in namespace: such.shorthand, being replaced by: #'such.shorthand/any?
WARNING: any? already refers to: #'clojure.core/any? in namespace: commons.clojure.core, being replaced by: #'commons.clojure.core/any?
WARNING: any? already refers to: #'clojure.core/any? in namespace: midje.emission.levels, being replaced by: #'commons.clojure.core/any?
WARNING: any? already refers to: #'clojure.core/any? in namespace: midje.util.pile, being replaced by: #'commons.clojure.core/any?
WARNING: any? already refers to: #'clojure.core/any? in namespace: midje.repl, being replaced by: #'commons.clojure.core/any?
WARNING: any? already refers to: #'clojure.core/any? in namespace: midje.emission.api, being replaced by: #'commons.clojure.core/any?
WARNING: any? already refers to: #'clojure.core/any? in namespace: midje.data.nested-facts, being replaced by: #'commons.clojure.core/any?
WARNING: any? already refers to: #'clojure.core/any? in namespace: midje.data.project-state, being replaced by: #'commons.clojure.core/any?
WARNING: any? already refers to: #'clojure.core/any? in namespace: midje.doc, being replaced by: #'commons.clojure.core/any?
WARNING: any? already refers to: #'clojure.core/any? in namespace: midje.parsing.other.arglists, being replaced by: #'commons.clojure.core/any?
WARNING: any? already refers to: #'clojure.core/any? in namespace: midje.emission.plugins.util, being replaced by: #'commons.clojure.core/any?
WARNING: any? already refers to: #'clojure.core/any? in namespace: midje.emission.plugins.default-failure-lines, being replaced by: #'commons.clojure.core/any?
WARNING: any? already refers to: #'clojure.core/any? in namespace: midje.parsing.1-to-explicit-form.metadata, being replaced by: #'commons.clojure.core/any?
WARNING: any? already refers to: #'clojure.core/any? in namespace: midje.parsing.util.recognizing, being replaced by: #'commons.clojure.core/any?
WARNING: any? already refers to: #'clojure.core/any? in namespace: midje.sweet, being replaced by: #'commons.clojure.core/any?
WARNING: any? already refers to: #'clojure.core/any? in namespace: midje.checking.checkables, being replaced by: #'commons.clojure.core/any?
WARNING: any? already refers to: #'clojure.core/any? in namespace: midje.checking.core, being replaced by: #'commons.clojure.core/any?
WARNING: any? already refers to: #'clojure.core/any? in namespace: midje.data.prerequisite-state, being replaced by: #'commons.clojure.core/any?
WARNING: any? already refers to: #'clojure.core/any? in namespace: midje.parsing.2-to-lexical-maps.fakes, being replaced by: #'commons.clojure.core/any?
WARNING: any? already refers to: #'clojure.core/any? in namespace: midje.parsing.lexical-maps, being replaced by: #'commons.clojure.core/any?
WARNING: any? already refers to: #'clojure.core/any? in namespace: midje.parsing.3-from-lexical-maps.from-fake-maps, being replaced by: #'commons.clojure.core/any?
WARNING: any? already refers to: #'clojure.core/any? in namespace: midje.checking.checkers.chatty, being replaced by: #'commons.clojure.core/any?
WARNING: any? already refers to: #'clojure.core/any? in namespace: midje.checking.checkers.util, being replaced by: #'commons.clojure.core/any?
WARNING: any? already refers to: #'clojure.core/any? in namespace: midje.checking.checkers.simple, being replaced by: #'commons.clojure.core/any?
WARNING: any? already refers to: #'clojure.core/any? in namespace: midje.checking.checkers.collection, being replaced by: #'commons.clojure.core/any?
WARNING: any? already refers to: #'clojure.core/any? in namespace: midje.checking.checkers.collection-util, being replaced by: #'commons.clojure.core/any?
WARNING: any? already refers to: #'clojure.core/any? in namespace: midje.checking.checkers.collection-comparison, being replaced by: #'commons.clojure.core/any?
WARNING: any? already refers to: #'clojure.core/any? in namespace: midje.parsing.util.fnref, being replaced by: #'commons.clojure.core/any?
WARNING: any? already refers to: #'clojure.core/any? in namespace: midje.parsing.util.error-handling, being replaced by: #'commons.clojure.core/any?
WARNING: any? already refers to: #'clojure.core/any? in namespace: midje.parsing.1-to-explicit-form.parse-background, being replaced by: #'commons.clojure.core/any?
WARNING: any? already refers to: #'clojure.core/any? in namespace: midje.parsing.2-to-lexical-maps.expects, being replaced by: #'commons.clojure.core/any?
WARNING: any? already refers to: #'clojure.core/any? in namespace: midje.parsing.2-to-lexical-maps.data-fakes, being replaced by: #'commons.clojure.core/any?
WARNING: any? already refers to: #'clojure.core/any? in namespace: midje.util.laziness, being replaced by: #'commons.clojure.core/any?
WARNING: any? already refers to: #'clojure.core/any? in namespace: midje.parsing.0-to-fact-form.tabular, being replaced by: #'commons.clojure.core/any?
WARNING: any? already refers to: #'clojure.core/any? in namespace: midje.parsing.1-to-explicit-form.facts, being replaced by: #'commons.clojure.core/any?
WARNING: any? already refers to: #'clojure.core/any? in namespace: midje.parsing.0-to-fact-form.formulas, being replaced by: #'commons.clojure.core/any?

These warnings are fixed by marick/suchwow/pull/4 and marick/clojure-commons/pull/1.

I was hoping that I could piggyback the changes on top of a new release of Potemkin, but it looks like not. I'll try to propagate fixes in the next couple of days.

I think the just-created 1.9-alpha4 fixes this problem.

Confirmed. Thank you.


Fix issue on minisite references

Issue https://github.com/marmelroy/Zip/issues/59 occurs when trying to build app :

no such module 'minizip'

As discussed with @mostafaberg, this issue comes from a problem of reference in project.
Like the master branch (swift 3), now sources are copied directly in source folder.

wrong files


fixed locals in elasticsearch

Terraform apply and plan both works perfectly

@kezhenxu94  whats the command for updating docs? i know terraform docs updates the readme i guess

@kezhenxu94 whats the command for updating docs? i know terraform docs updates the readme i guess

use terraform-doc
terraform-docs markdown table --output-file configurations.md --output-mode inject aws

@kezhenxu94  Done

@kezhenxu94 Why checks are failing ? any idea?

Checking out the codes failed, I believe this is an incident of GitHub itself,


Application Detail UI

To complete that we need to have:

App data and metrics ui ( https://github.com/platformatic/meraki/issues/260 )
start/stop actions ( https://github.com/platformatic/meraki/issues/227 )

Done!


Outdated dependencies in 1.2.5

Expected Behavior
There should be a maintenance branch for the older version which is used for Micronaut 3.
Actual Behaviour
The current 1.2.5 for micronaut 3 contains a few outdated dependencies.
I wanted to privde a PR with updated dependencies but couldn't find a maintenance branch.
Steps To Reproduce
Branches drop-down in Git-UI :)
Sorry, I couldn't find a better fitting ticket-type.
I didn't want to file the CVE-report because I think there should still be a maintenance path for this until Micronaut 3 is officially EoL.
Environment Information
Git
Example Application
No response
Version
3.10.1

There's a 1.2.x branch for 1.2.x, but indeed it hasn't been updated for a while.

I am so sorry.
I blame caffeine deficiency for overlooking it.
You are perfectly right.
Should I provide a PR or is that something you are handling?

Would be great if you provide a PR!

Would love to, but need a pointer:
I was trying to follow the CONTRIBUTING.md but running
./gradlew check produces:
Could not resolve all files for configuration 'classpath'.
> Could not find null:groovydoc-gradle-plugin:null.
  Searched in the following locations:
    - https://plugins.gradle.org/m2/null/groovydoc-gradle-plugin/null/groovydoc-gradle-plugin-null.pom
    - https://repo.maven.apache.org/maven2/null/groovydoc-gradle-plugin/null/groovydoc-gradle-plugin-null.pom
  Required by:
      unspecified:unspecified:unspecified > io.micronaut.build.shared.settings:io.micronaut.build.shared.settings.gradle.plugin:5.4.5 > io.micronaut.build.internal:micronaut-build:5.4.5 > io.github.groovylang.groovydoc:io.github.groovylang.groovydoc.gradle.plugin:1.0.1

* Try:
> Run with --stacktrace option to get the stack trace.
> Run with --info or --debug option to get more log output.
> Run with --scan to get full insights.

* Get more help at https://help.gradle.org

I can't find any further docs on what to do.
Any idea what I am missing?

Sorry for pestering you, but I really don't know where to go from here.

@codepitbull
I don't know what branch you are trying to build, but it looks like you need to update the version of the micronaut build plugin in settings.gradle. That will fix the problem with the unresolvable plugin.
plugins {
    id 'io.micronaut.build.shared.settings' version '6.5.6'
}

For Micronaut 3.x that would be .5.4.10 and for Micronaut 4.x it is 6.5.6.

@wetted thank you!! That solved it :)
Will test everything and there will be a PR tomorrow!

Here is the PR:
https://github.com/micronaut-projects/micronaut-test-resources/pull/407
I just can't sign the CLA ... the page seems broken:
https://cla-assistant.io/melix/micronaut-test-resources

Now it worked.

What's the state on this?

I was quite busy for the past 2 weeks. I'm trying to get the 1.2.x branch passing.


Add function to check if call node has an async argument

We already have a function that checks for async arguments with no side effects, however, since we intend to allow for impure node delegation, we should have a function that simply checks for async arguments regardless of node purity.

✅ No public API change.


ci: Test current versions of Node.js

Builds on #1084 to have CircleCI test on the versions of Node.js at https://github.com/nodejs/release#readme
Linux 20 fails on:
[4/4] Building fresh packages...
$ npm run compile
/usr/bin/env: ‘node’: Text file busy
error Command failed with exit code 126.

Codecov Report

Merging #1085 (76caf43) into main (29365ad) will decrease coverage by 2.03%.
The diff coverage is 74.50%.

@@            Coverage Diff             @@
##             main    #1085      +/-   ##
==========================================
- Coverage   76.44%   74.41%   -2.03%
==========================================
  Files          19       20       +1
  Lines         692      688       -4
  Branches      134      129       -5
==========================================
- Hits          529      512      -17
- Misses        118      125       +7
- Partials       45       51       +6

Impacted Files
Coverage Δ

src/clang-fetcher.ts
70.00% <ø> (-11.09%)
:arrow_down:

src/module-type/prebuild-install.ts
89.28% <ø> (-0.72%)
:arrow_down:

src/module-type/node-gyp/worker.ts
66.66% <66.66%> (ø)

src/module-type/node-gyp/node-gyp.ts
82.25% <75.00%> (ø)

src/module-rebuilder.ts
91.52% <100.00%> (ø)

src/sysroot-fetcher.ts
83.87% <100.00%> (-0.51%)
:arrow_down:

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more

The Linux 20 failure in this PR looks to be related to Node.js 20.3.0, see https://github.com/websockets/bufferutil/issues/152. Testing with 20.2.0 works.

Downgrade to Linux Node.js v20.2 passes the tests.

Closing in favor of #1086


Auto-detection for tokens at launch should include CryptoKitties

Relevant: GetContractInteractions.getContractList

@hboon please elaborate

Appending Victor's wallet to https://api.etherscan.io/api?module=account&action=txlist&address= and 0x06012c8cf97BEaD5deAe237070F9587f8E7A266d doesn't appear. 0xb1690c08e213a35ed9bab7b318de14420fb57d8c does though, if we want to special case.

@hboon this is the same issue as trying to get contract's whereby you have tokens but haven't directly transacted with it.
We have not found a good solution in either case as it would involve indexing the entire chain.

As this is an old issue and one we cannot solve in the short term, I am gonna close it.


How to get alerted before image update?

I would like to get an alert before an image is updated.

Some slack notifications are contributed with #61 . I would like to introduce some generic notifications layer, where different notification providers could easily be implemented. Unfortunately I haven't found any time yet to implement that.

Slack and email support has been merged and is available since version v0.3.0.


Fix OS compatibility issues with building Clap on Windows so the build succeeds

Describe the bug
error[E0433]: failed to resolve. Could not findunixinos--> C:\Users\ChosunOne\.cargo\registry\src\github.com-1ecc6299db9ec823\clap-2.31.2\src\app\parser.rs:7:14 | 7 | use std::os::unix::ffi::OsStrExt; | ^^^^ Could not findunixinos``

From https://gitter.im/Drops-of-Diamond/Development?at=5aed4e101eddba3d04d3ddb2.
To Reproduce
Steps to reproduce the behavior:

Run cargo make build on a Windows OS

Expected behavior
The project should build.
Desktop (please complete the following information):

OS: Windows 10 64-bit

A workaround is to change the parser.rs file line 7 to:
use std::os::windows::ffi::OsStrExt;
and add the line:
use osstringext::OsStrExt3;
after it.  This will fix the build errors but will leave you with a nonstandard version of clap.

So that we don't have to configure this manually, try:
#[cfg(not(target_os = "windows"))]
use std::os::unix::ffi::OsStrExt;
#[cfg(target_os = "windows")]
use osstringext::OsStrExt3;

From https://github.com/kbknapp/clap-rs/pull/1190/files#diff-3519f1369b63436798d9d7841c7940e2R672.

The alternative method still doesn't build, but reintroducing the target checks in parser.rs of clap fixes the issue.  We should raise an issue with clap about this.

Thanks for pointing this one out! It seems a case that has been both missed during my changes and before that time also. I have fixed the issue and tested using a copy of your specific project also and can report success. Once the PR merges you should be good to update and go.


Error on pre-build

Cross.toml:
[target.x86_64-unknown-linux-gnu] pre-build = [     "dpkg --add-architecture amd64 && apt-get update && apt-get install --assume-yes libssl-dev:amd64", ]
Running with : cross build --target x86_64-unknown-linux-gnu  --release
Error:

Builds well without Cross.toml pre-build option.

Missing some important context here!
Can you show us the entire build log when doing cross build -v --target x86_64-unknown-linux-gnu --release, note the added -v
You could upload the log to https://gist.github.com


Add new donation page

@stvnrlly @gregjd
New donation page hooked to stripe.
To test:
Run bundle exec jekyll serve
Got to http://localhost:4000/donate
And try a sample donation.

This looks good, but there's a slightly updated version over at https://github.com/district-civic-labs/districtciviclabs.org/blob/develop/_includes/donation-form.html if you'd like to borrow that.
I think the main difference is supporting donations other than whole dollars. In this older format, submitting cents will confuse the script (and possibly the donor).


Bump pymodbus into 3.7

No change in functionality. Simply bumped PyModbus into latest version of 3.7.

Tests are failing, please check https://wasilukm.github.io/hoymiles_modbus/contributing/#get-started how to run tests on your locally.

I am closing this PR due to a lack of activity. I added support for pymodbus 3.7 in #23
Thank you for your inspiration.


Use host X server istead of RDP proposal

Hi guys!
Thank you very much for this images are really useful. (I was getting mad about the downgrade dependencies of gtk) .
My little contribution is the following (how I use it):
I've created a docker-compose.yml like the following:
version: "3"
services:
  capella:
    image: capella/base:latest
    environment:
      - DISPLAY=${DISPLAY}
      - GTK_THEME=Adwaita
    volumes:
      - /tmp/.X11-unix:/tmp/.X11-unix
      - ./git:/git
      - ./extworkspace:/extworkspace
    network_mode: host
    entrypoint: ./capella/capella -data /extworkspace

Basically it sets the DISPLAY variable accordingly to execute GUIs application inside the docker and sets my git and an external workspace to use by default.
here some reference on GUI apps on docker.
https://gursimar27.medium.com/run-gui-applications-in-a-docker-container-ca625bad4638

Hi @juanvaccarezza! Thanks for your comment. In fact, our use case is a little more advanced.
We built a complete platform around capella, which also serves the Capella container allows the use from external devices. If you are interested, you can find more here: https://github.com/DSD-DBS/capella-collab-manager.
However, your approach is definitely very practical for local work and we could integrate the docker-compose.yml into our repository. What do you think about this?

very nice solution indeed! I can see us using it for local debug of Capella containers / pyease scripts, etc. Thanks for sharing, @juanvaccarezza


Changed none auth to apiKey for arcsecond API

[x] My submission is formatted according to the guidelines in the contributing guide
[x] My addition is ordered alphabetically
[x] My submission has a useful description
[x] The description does not have more than 100 characters
[x] The description does not end with punctuation
[x] Each table column is padded with one space on either side
[x] I have searched the repository for any relevant issues or pull requests
[x] Any category I am creating has the minimum requirement of 3 items
[x] All changes have been squashed into a single commit

Link to API testing

Thank you.


run 'vite' and  'rsw && vite build'  should not change the yarn.lock

The code has been committed. Running 'rsw && vite build'  changed the yarn.lock.
It's happened after upgrading the vite-plugin-rsw and rsw-node
modified   yarn.lock
@@ -1238,8 +1238,8 @@
   optionalDependencies:
     "fsevents" "~2.3.2"

-"foobar@file:foobar/pkg":
-  "resolved" "file:foobar/pkg"
+"foobar@file:.rsw/crates/foobar/pkg":
+  "resolved" "file:.rsw/crates/foobar/pkg"
   "version" "0.1.5"

<EMAIL_ADDRESS>
Current version
"vite": "2.7.4",
"vite-plugin-pwa": "^0.11.12",
"vite-plugin-rsw": "^1.10.2",

At present, I have not thought of a good solution. Welcome to communicate.
yarn build needs to use rsw-node, .rsw/crates/ will be the root path of the build. When executing yarn related commands, yarn.lock will be rewritten, you can try to execute npm run build.
{
  "scripts": {
    "build": "rsw && vite build"
  }
}

What about the previous version?  I used them without this problem until upgrading the node from v12 to v16 then reinstalling rsw-node.

v0.1.2 may be the version you used before.

 "rsw-node": "0.1.2"  +   "vite-plugin-rsw": "^1.10.2"  works fine.  :)


misleading info message in compute_rank

in reviewing #7085 I noticed the output of running mne.compute_covariance(epochs, ...) yields the info message

Computing data rank from raw with rank=None

Looks like mne.compute_covariance converts epochs to a numpy array (let's call it "data"), and then _compute_covariance_auto(data, ...) calls compute_rank(RawArray(data.T, ...), ...).  So the message will always say you're computing from "raw" regardless of whether you pass in Raw or Epochs

Yeah it should probably say "Computing rank from data with rank=None" or so, feel free to put it in some PR


Playback issue with Raspberry Pi Stretch 2017-11-29

Briefly summarize your issue:
Raspberry Pi reference 2017-11-29:
I have no audio playback, the Alexa keyword is detected, I ask my question but when it says "Speaking" nothing comes out to the speaker.
Note: I can successfully play a sound using "aplay"
Raspberry Pi reference 2017-09-07:
Same SDK, same hardware, same ALSA config as above but it works fine.
It seems that something related to the MediaPlayer is broken with the latest Raspbian image
What is the expected behavior?
I would expect the same behavior in "Raspberry Pi reference 2017-11-29" as in "Raspberry Pi reference 2017-09-07". Both are Raspbian Stretch
What behavior are you observing?
No audio playback within the Alexa Sample App with "Raspberry Pi reference 2017-11-29"
Provide the steps to reproduce the issue, if applicable:
Follow the instructions provided in this wiki to install the Alexa sample app on a Raspberry Pi
Tell us about your environment:
cat /etc/os-release
PRETTY_NAME="Raspbian GNU/Linux 9 (stretch)"
NAME="Raspbian GNU/Linux"
VERSION_ID="9"
VERSION="9 (stretch)"
ID=raspbian
ID_LIKE=debian
HOME_URL="http://www.raspbian.org/"
SUPPORT_URL="http://www.raspbian.org/RaspbianForums"
BUG_REPORT_URL="http://www.raspbian.org/RaspbianBugs"
uname -a
Linux Microsemi-AVS 4.9.59-v7+ #1047 SMP Sun Oct 29 12:19:23 GMT 2017 armv7l GNU/Linux
cat /etc/rpi-issue
Raspberry Pi reference 2017-11-29
Generated using pi-gen, https://github.com/RPi-Distro/pi-gen, b71bf3179310aadf9aaf2ffcdf094a88e488dce8, stage5
What version of the AVS Device SDK are you using?
  <1.3.0> and <1.2.1> both have the issue

Tell us what hardware you're using:

[ ] Desktop / Laptop
[X] Raspberry Pi
[ ] Other - tell us more:

Tell us about your OS (Type & version):

[ ] Linux
[ ] MacOS
[X] Raspbian Stretch
[ ] Raspbian Jessy
[ ] Other - tell us more:

I believe I am having the same issue with no audio out from Alexa using the 3.5mm jack.
@XPlay1990 what config file did you modify to get alexa working ?  Thanks,

Hi @mikejrh
I haven't fixed it yet, I'm still using "Raspbian 2017-09-07"


Update README Post Installation steps

As discussed here:
https://github.com/nvim-lua/kickstart.nvim/issues/478
Change the recommendation to just run nvim normally instead of the headless mode for the first run. This will show Lazy UI updating the plugins which would match what the video show and may be easier to understand what is going on thant the silent headless run.
Perhaps now it is too verbose? Let me know if you would prefer to word it differently.

Thanks very much. This is a great contribution. Small improvements like this are super important!


fix: adjusts json field joi schema to allow editorOptions

This prevents the JSON Field type from producing an error when editorOptions are provided.
Documentation claims editorOptions is supported by JSON Field type, but defining any in a collection config produces an error:
[16:08:59] ERROR (payload): There were 1 errors validating your Payload config
[16:08:59] ERROR (payload): 1: Collection "surveys" > Field "content" > "value" does not match any of the allowed types

This is because a previous joi validation fix to the code Field type was not applied to JSON fields: https://github.com/payloadcms/payload/pull/2731/files
Description

[x] I have read and understand the CONTRIBUTING.md document in this repository.

Type of change

[ ] Chore (non-breaking change which does not add functionality)
[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Change to the templates directory (does not affect core functionality)
[ ] Change to the examples directory (does not affect core functionality)
[ ] This change requires a documentation update

Checklist:

[ ] I have added tests that prove my fix is effective or that my feature works
[ ] Existing test suite passes locally with my changes
[ ] I have made corresponding changes to the documentation

Thanks @jschuur! We definitely needed this - I will merge and reply to you over on your issue.


x/tools/gopls: Cannot find method when using C structs

Hello!
gopls version
$ gopls version
golang.org/x/tools/gopls v0.11.0
<EMAIL_ADDRESS>h1:/nvKHdTtePQmrv9XN3gIUN9MOdUrKzO/dcqgbG6x8EY=

go env
$ go env
GO111MODULE=""
GOARCH="arm64"
GOBIN=""
GOCACHE="/Users/mine/Library/Caches/go-build"
GOENV="/Users/mine/Library/Application Support/go/env"
GOEXE=""
GOEXPERIMENT=""
GOFLAGS=""
GOHOSTARCH="arm64"
GOHOSTOS="darwin"
GOINSECURE=""
GOMODCACHE="/Users/mine/go/pkg/mod"
GONOPROXY=""
GONOSUMDB=""
GOOS="darwin"
GOPATH="/Users/mine/go"
GOPRIVATE=""
GOPROXY="https://proxy.golang.org,direct"
GOROOT="/Users/mine/homebrew/Cellar/go/1.19.4/libexec"
GOSUMDB="sum.golang.org"
GOTMPDIR=""
GOTOOLDIR="/Users/mine/homebrew/Cellar/go/1.19.4/libexec/pkg/tool/darwin_arm64"
GOVCS=""
GOVERSION="go1.19.4"
GCCGO="gccgo"
AR="ar"
CC="clang"
CXX="clang++"
CGO_ENABLED="1"
GOMOD="/Users/mine/code/temp/go-with-cgo/go.mod"
GOWORK=""
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
PKG_CONFIG="pkg-config"
GOGCCFLAGS="-fPIC -arch arm64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=/var/folders/2n/v_rmrnt16qbd3kt9jqb8g8sc0000gp/T/go-build4171816550=/tmp/go-build -gno-record-gcc-switches -fno-common"

What did you do?
The code below compiles and runs just fine.
package main

import (
	"fmt"
)

/*
typedef struct number {
    int value;
} number_t;
*/
import "C"

func (n C.number_t) show() {
	fmt.Printf("%d\n", n.value)
}

func main() {
	var n C.number_t
	n.show()
}

$ go run main.go
0

However, gopls complains because it cannot find the "show method".
$ ~/go/bin/gopls check main.go
main.go:21:4-8: n.show undefined (type _Ctype_struct_number has no field or method show)

What did you expect to see?
I expected gopls to find all the references.
What did you see instead?
gopls did not find a reference to the show method, even though it is defined and found by the compiler.
Editor and settings
Using it in the command line. Even though I do not report it here, the same error appears in VSCode, given that it uses gopls.
Thanks ;)

I question whether this program is valid as it attempts to declare a method on a type that is ostensibly defined in another package, which should be a syntax error; see https://github.com/golang/go/issues/57926. Let's see what the outcome of that discussion is before we decide what to do in gopls.


Extend time difference docstring to warn against using large values

need stems from https://github.com/sentinel-hub/eo-learn/issues/503

Codecov Report
Base: 83.67% // Head: 83.67% // No change to project coverage :thumbsup:

Coverage data is based on head (8c7695f) compared to base (ea971d6).
Patch has no changes to coverable lines.

Additional details and impacted files
@@           Coverage Diff            @@
##           develop     #505   +/-   ##
========================================
  Coverage    83.67%   83.67%
========================================
  Files           60       60
  Lines         5671     5671
========================================
  Hits          4745     4745
  Misses         926      926

Impacted Files
Coverage Δ

io/eolearn/io/sentinelhub_process.py
89.21% <ø> (ø)

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

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


odo config volumes do not have owner references

/kind bug

What versions of software are you using?
Operating System: MacOS
Output of odo version:
maysuns-mbp:spring-devfile maysun$ ./odo version
odo v1.1.0 (c64e84bde)

Server: <cluster ip>
OpenShift: v3.11.0+e5dbec2-186
Kubernetes: v1.11.0+d4cacc0

How did you run odo exactly?
odo create, add storage to .odo/config.yaml and odo push
Actual behavior
Noticed this when working on #2472
When i delete the deployment config, the volumes/pvc defined in config.yaml are not deleted
Expected behavior
When you delete the deployment config, the volumes/pvc defined in config.yaml should be deleted
Any logs, error output, etc?
printed pvc after owner refs were added in https://github.com/openshift/odo/blob/master/pkg/occlient/volumes.go#L187
I0306 00:41:00.456342    5682 volumes.go:205] mjf after latestPVC &PersistentVolumeClaim{ObjectMeta:k8s_io_apimachinery_pkg_apis_meta_v1.ObjectMeta{Name:maysunvol-app-pvc,GenerateName:,Namespace:myproject,SelfLink:/api/v1/namespaces/myproject/persistentvolumeclaims/maysunvol-app-pvc,UID:93191f6b-5f5a-11ea-9264-664b76d93af3,ResourceVersion:39735,Generation:0,CreationTimestamp:2020-03-05 22:28:40 -0500 EST,DeletionTimestamp:<nil>,DeletionGracePeriodSeconds:nil,Labels:map[string]string{app: app,app.kubernetes.io/instance: nodejs-nodejs-ex-xwcu,app.kubernetes.io/managed-by: odo,app.kubernetes.io/managed-by-version: v1.1.0,app.kubernetes.io/part-of: app,app.kubernetes.io/storage-name: maysunvol,},Annotations:map[string]string{pv.kubernetes.io/bind-completed: yes,pv.kubernetes.io/bound-by-controller: yes,},OwnerReferences:[],Finalizers:[kubernetes.io/pvc-protection],ClusterName:,Initializers:nil,},Spec:PersistentVolumeClaimSpec{AccessModes:[ReadWriteOnce],Resources:ResourceRequirements{Limits:ResourceList{},Requests:ResourceList{storage: {{1073741824 0} {<nil>} 1Gi BinarySI},},},VolumeName:pv0042,Selector:nil,StorageClassName:nil,VolumeMode:nil,DataSource:nil,},Status:PersistentVolumeClaimStatus{Phase:Bound,AccessModes:[ReadWriteOnce ReadWriteMany ReadOnlyMany],Capacity:ResourceList{storage: {{107374182400 0} {<nil>} 100Gi BinarySI},},Conditions:[],},}
I0306 00:41:00.456587    5682 volumes.go:206] mjf after &latestPVC 0xc0000cd0e8
 ✓  Creating component [487ms]

oc get po,dc,pvc
NAME                                    READY   STATUS    RESTARTS   AGE
pod/nodejs-nodejs-ex-xwcu-app-1-6l9m4   1/1     Running   0          5m

NAME                                                           REVISION   DESIRED   CURRENT   TRIGGERED BY
deploymentconfig.apps.openshift.io/nodejs-nodejs-ex-xwcu-app   1          1         1         config,image(nodejs:latest)

NAME                                                      STATUS   VOLUME   CAPACITY   ACCESS MODES   STORAGECLASS   AGE
persistentvolumeclaim/maysunvol-app-pvc                   Bound    pv0042   100Gi      RWO,ROX,RWX                   5m
persistentvolumeclaim/nodejs-nodejs-ex-xwcu-app-s2idata   Bound    pv0012   100Gi      RWO,ROX,RWX                   5m

oc get pvc maysunvol-app-pvc -o yaml
maysuns-mbp:~ maysun$ oc get pvc maysunvol-app-pvc -o yaml
apiVersion: v1
kind: PersistentVolumeClaim
metadata:
  annotations:
    pv.kubernetes.io/bind-completed: "yes"
    pv.kubernetes.io/bound-by-controller: "yes"
  creationTimestamp: "2020-03-06T03:28:40Z"
  finalizers:
  - kubernetes.io/pvc-protection
  labels:
    app: app
    app.kubernetes.io/instance: nodejs-nodejs-ex-xwcu
    app.kubernetes.io/managed-by: odo
    app.kubernetes.io/managed-by-version: v1.1.0
    app.kubernetes.io/part-of: app
    app.kubernetes.io/storage-name: maysunvol
  name: maysunvol-app-pvc
  namespace: myproject
  resourceVersion: "39735"
  selfLink: /api/v1/namespaces/myproject/persistentvolumeclaims/maysunvol-app-pvc
  uid: 93191f6b-5f5a-11ea-9264-664b76d93af3
spec:
  accessModes:
  - ReadWriteOnce
  resources:
    requests:
      storage: 1Gi
  volumeName: pv0042
status:
  accessModes:
  - ReadWriteOnce
  - ReadWriteMany
  - ReadOnlyMany
  capacity:
    storage: 100Gi
  phase: Bound
maysuns-mbp:~ maysun$

config.yaml
Maysuns-MacBook-Pro:nodejs-ex maysun$ cat .odo/config.yaml
kind: LocalConfig
apiversion: odo.openshift.io/v1alpha1
ComponentSettings:
  Type: nodejs
  SourceLocation: ./
  SourceType: local
  Ports:
  - 8080/TCP
  Application: app
  Project: myproject
  Name: nodejs-nodejs-ex-xwcu
  Storage:
  - Name: maysunvol
    Size: 1Gi
    Path: /root/maysunpath

The issue is in function https://github.com/openshift/odo/blob/master/pkg/occlient/volumes.go#L187
pvc and latestPVC are pointers to different objects of the same PVC. In the above function, the pvc object is being updated but it is not reflected in latestPVC and when we update PVC with the API on latestPVC, the changes are not reflected.
the pvc object in the above function:
I0306 00:41:00.456204    5682 volumes.go:202] mjf pvc &PersistentVolumeClaim{ObjectMeta:k8s_io_apimachinery_pkg_apis_meta_v1.ObjectMeta{Name:maysunvol-app-pvc,GenerateName:,Namespace:myproject,SelfLink:/api/v1/namespaces/myproject/persistentvolumeclaims/maysunvol-app-pvc,UID:93191f6b-5f5a-11ea-9264-664b76d93af3,ResourceVersion:39730,Generation:0,CreationTimestamp:2020-03-05 22:28:40 -0500 EST,DeletionTimestamp:<nil>,DeletionGracePeriodSeconds:nil,Labels:map[string]string{app: app,app.kubernetes.io/instance: nodejs-nodejs-ex-xwcu,app.kubernetes.io/managed-by: odo,app.kubernetes.io/managed-by-version: v1.1.0,app.kubernetes.io/part-of: app,app.kubernetes.io/storage-name: maysunvol,},Annotations:map[string]string{},OwnerReferences:[{apps.openshift.io/v1 DeploymentConfig nodejs-nodejs-ex-xwcu-app 9336e925-5f5a-11ea-ac41-664b76d93af3 <nil> <nil>}],Finalizers:[kubernetes.io/pvc-protection],ClusterName:,Initializers:nil,},Spec:PersistentVolumeClaimSpec{AccessModes:[ReadWriteOnce],Resources:ResourceRequirements{Limits:ResourceList{},Requests:ResourceList{storage: {{1073741824 0} {<nil>} 1Gi BinarySI},},},VolumeName:,Selector:nil,StorageClassName:nil,VolumeMode:nil,DataSource:nil,},Status:PersistentVolumeClaimStatus{Phase:Pending,AccessModes:[],Capacity:ResourceList{},Conditions:[],},}

the latestPVC object in the above function:
I0306 00:41:00.456342    5682 volumes.go:205] mjf after latestPVC &PersistentVolumeClaim{ObjectMeta:k8s_io_apimachinery_pkg_apis_meta_v1.ObjectMeta{Name:maysunvol-app-pvc,GenerateName:,Namespace:myproject,SelfLink:/api/v1/namespaces/myproject/persistentvolumeclaims/maysunvol-app-pvc,UID:93191f6b-5f5a-11ea-9264-664b76d93af3,ResourceVersion:39735,Generation:0,CreationTimestamp:2020-03-05 22:28:40 -0500 EST,DeletionTimestamp:<nil>,DeletionGracePeriodSeconds:nil,Labels:map[string]string{app: app,app.kubernetes.io/instance: nodejs-nodejs-ex-xwcu,app.kubernetes.io/managed-by: odo,app.kubernetes.io/managed-by-version: v1.1.0,app.kubernetes.io/part-of: app,app.kubernetes.io/storage-name: maysunvol,},Annotations:map[string]string{pv.kubernetes.io/bind-completed: yes,pv.kubernetes.io/bound-by-controller: yes,},OwnerReferences:[],Finalizers:[kubernetes.io/pvc-protection],ClusterName:,Initializers:nil,},Spec:PersistentVolumeClaimSpec{AccessModes:[ReadWriteOnce],Resources:ResourceRequirements{Limits:ResourceList{},Requests:ResourceList{storage: {{1073741824 0} {<nil>} 1Gi BinarySI},},},VolumeName:pv0042,Selector:nil,StorageClassName:nil,VolumeMode:nil,DataSource:nil,},Status:PersistentVolumeClaimStatus{Phase:Bound,AccessModes:[ReadWriteOnce ReadWriteMany ReadOnlyMany],Capacity:ResourceList{storage: {{107374182400 0} {<nil>} 100Gi BinarySI},},Conditions:[],},}

This is currently expected behavior as we don't want to delete user defined pvcs when user deletes the component.

so this is not a bug

It same as https://github.com/openshift/odo/issues/2710

if it is expected behavior than odo push after odo delete would fail and we need to handle this in some other way.

This is currently expected behavior as we don't want to delete user defined pvcs when user deletes the component.

I'm actually starting to incline towards deleting the pvcs. As a user I would expect that it gets deleted when I delete the component.
Originally we were thinking that we wouldn't delete the storage as we had a mechanism to unmount storage from one component and mount it to another one, but that functionality was dropped, so now it actually makes sense to delete pvcs, as they have no use after the component is deleted, and users don't have any mechanism to access that pvc using just odo.

Resolved with this PR https://github.com/openshift/odo/pull/2750
/close


When importing a dump in txt format, the asset breaks

When importing a dump in txt format, the asset breaks. After saving and re-exporting it says Asset failed to deserialize. Everything works with a dump in json format

Need more information to fix. What did you change (if anything)? What's in the file (any managed references)? What type is the asset? Anything you can give me is helpful.

Open globalgamemanagers - BuildSettings, export it to txt, you don’t even have to edit it, import it back and save it’s broken

Can you try replacing your classdata.tpk file with the tpk in this zip? https://nightly.link/AssetRipper/Tpk/workflows/type_tree_tpk/master/lz4_file.zip

Yes, now the import works correctly, the asset does not break. Thanks


examples?

Where are examples for how to retrieve metrics with PowerShell and CLI?  There's nothing really useful here https://docs.microsoft.com/en-us/cli/azure/monitor/metrics?view=azure-cli-latest#az-monitor-metrics-list that shows what to expect, how to work with metrics in a shell and how to manipulate the output.

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

ID: a309a81b-ea61-d82a-3ff7-5be5bb908c4a
Version Independent ID: ea5b0931-1397-a0ea-4ad0-2cf2e6200fb8
Content: Azure Log Analytics PowerShell Samples
Content Source: articles/azure-monitor/platform/powershell-samples.md
Service: log-analytics
GitHub Login: @MGoedtel
Microsoft Alias: magoedte

@christiankuhtz Thanks for bringing this to our attention. Your feedback has been shared with the content owner for further review.

@christiankuhtz - To retrieve metrics in Azure Monitor using PowerShell, here is the guidance I believe you are interested - https://docs.microsoft.com/en-us/azure/azure-monitor/platform/rest-api-walkthrough#retrieve-metric-values.

Where is the info for Azure cli?

That page was not discoverable from the cli docs. Can you fix please?

@christiankuhtz - Yes, I will bug this and help get that corrected.  Thanks.

Upon review to address the issue, I realized that because the CLI reference is auto-generated using an internal process fed by an input file from engineering, I cannot update the articles directly to provide a link to our documentation.  As part of the work we are doing to improve the Azure Monitor content and restructuring/consolidating content, we will evaluate what/if we can do anything to improve this situation. #please-close


feat(icon): add new link icon. closes #382

closes #382

Thanks for the icon and the extension of the readme file @xonic ;)

:+1:

👍

👍

@xonic can you remove the package-lock.json file?

done!

👍

:+1:


How to add nginx proxy between victim and evilginx2

I am try to add Nginx reverse proxy before Evilginx2
So, Nginx have address site1.com, Evilginx - site2.com
On Nginx I am got certificates for domain and other settings, but when I am go to site1.com I am have error 'too_many_redirects'
But if in Nginx settings I am set any other site (site3.com) then all traffic proxied.
Why not working Nginx proxy with Evilginx?
Anybody have working methods?

Hello! If you were already able to resolve your doubts and achieve your goals, close the issue so that we know which ones are pending.
Thank you!
If you want expedited help and have the assistance of many professional people, join our private group. Contact us<EMAIL_ADDRESS>to give you access to the group.


Create accordion component

initial version of accordion as a component, will be iterated on
GA code will be updated during iteration but for now should be exactly what was in place before
CSS for taxon pages reorganised to prevent CSS collisions with component (taxon pages have blanket rules like '.taxon h2 {}' which cannot be overridden using our BEM approach)
JS kept as a module but moved to 'components' dir. Possibly unnecessary, but the JS is very specific to this component. Could be moved back, we don't really have guidance on this yet

Notable changes from original accordion:

accordion headers now get wrapped in buttons rather than links, solves some accessibility issues
accordion header has darker hover colour
BEM used for CSS (as per component conventions) but JS only classes (.js-something) don't, as BEM too verbose and not needed there
inner wrapping element removed as unnecessary

https://govuk-collections-pr-394.herokuapp.com/component-guide/accordion
https://govuk-collections-pr-394.herokuapp.com/education/funding-and-finance-for-students
Relates to: https://trello.com/c/o0BCuFub/190-rewrite-the-accordion-to-meet-our-teams-needs

Just was thinking, maybe we could account for this usecase:

User visits a page
Opens an accordion
Shares link with accordion hash in URL
User 2 visits shared link
JavaScript fails
User 2 is not anchored to the correct heading

This could be bad if you're on a page like a manual with many sections, we could include the ID in the fallback headings and it should be ok?

@nickcolley In step 6, wouldn't the hash in the URL scroll them to the right section?

Tested in IE11, IE10, IE9, IE8, Firefox latest, Firefox 48, Chrome latest, Chrome 53, Opera latest, Google Nexus 6, iphone 6s, Samsung Galaxy S5, ipad pro.
Tested in Voiceover on Chrome and Safari.

@fofr I might be wrong but the default markup does not contain markup that'd anchor the user to the correct header?

@nickcolley it does, I've just tried it. It's got the ID in the markup.

@andysellick my mistake, the page isn't long enough for the anchors to work, I scrunched it up and it worked, sorry. 👍

https://github.com/alphagov/collections/pull/394#pullrequestreview-69621268
Can you share the pages that use this new component?


feat: add entire bluefin branding as package

This should add the entirety of the bluefin branding through a spec file with multiple subpackages. Hell yeah!

I just need to add the GNOME schemas now

https://copr.fedorainfracloud.org/coprs/tulilirockz/bluefin-wallpapers-test/build/8450770/
Seems to build just fine on COPR

https://copr.fedorainfracloud.org/coprs/tulilirockz/bluefin-wallpapers-test/build/8450773/
It works!!!!


feat: @attr v2 (support of serializer/parser)

:tada: This PR is included in version 4.0.0-beta.9 :tada:
The release is available on:

npm package (@beta dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Automate consistent update of primitive crds for helm chart

As per a comment in the CI script, there needs to be a way for any contributor to consistently update the primitive CRDs packaged with the helm chart.
kubefed2 depends on openapi schema to determine the validation for the CRDs it generates, and openapi needs to be sourced from a kube-apiserver.  The openapi schema will vary with the version of kube-apiserver, and it's not reasonable to expect that every contributor will be using the same version.  Instead, it should be possible to create a script that launches the version of kube-apiserver that is downloaded as part of kubebuilder and runs kubefed2 against that server.  Since the same kube-apiserver version will be used in CI, this approach should allow the ci check linked above to be re-enabled.

FYI @xunpan


'Log In' misaligned in error page

As you can see below, the 'Log In' sentence is not correctly centered in its place (it is a bit to the left).

On which page did you meet this problem? Can you please put the link here?

Sorry, I forgot.
For example accessing http://codecombat.com/admin/clas without being logged in.


Add isStarted() to DatabaseManager

Add a way to see if a DatabaseManager instance is already started

Fixes #1


Clarify perf implication in WASM debug note

Fixes #19476
Draft wording for sure ... we might need to play with it a bit on review.

🤔 .... debug mode? ... Don't we usually say, "debug configuration"?

Yeah ... I think so. VS calls it a "solution configuration," so let's go with "configuration."


[ComboBox] Placeholder label not visible when a value is selected

What would you like to be added:
Need to have the placeholder label visible when a value is selected for the ComboBox similar to the TextBox control.
Why is this needed:
Due to no placeholder visible when a value is selected, it looks odd that all other controls have the placeholder visible, and Combobox didn't in UI form.

For which Platform:

[x] UWP
[x] iOS
[x] Android
[x] WebAssembly
[x] macOS

Anything else we need to know?

@jeromelaban
Filled ComboBox style is also missing in addition to the Header for the Material styles.
(For the TextBox control we both have the filled and outlined styles like in the guidelines).
I will work on it at the same time as properly adding the Header with the translate animation similar to the TextBox Control.

Separated issue entered for the Filled style missing:
https://github.com/unoplatform/Uno.Themes/issues/600

Thanks


[BUG] Tracking page issue.

Describe the bug
There is a gap between the nav and top bar.
Screenshots

CheckList

[ ] I'm a JWOC'24 Contributor
[x] I've checked the existing issues, this issue is not a duplicate

(Tip - place an "x" between the square brackets to check mark)

@nepalivai assigned

please assign it to me under JWOC'2024.

@vishal2005025 assigned


Fix retrieval of commit data and most recent tag

git._iter_log_online() returns None in some cases for instance when SKIP_WRITE_GIT_CHANGELOG is set to true. This needs to be handled in packaging._get_revno_and_last_tag().

Thank you for contributing to openstack-dev/pbr!
openstack-dev/pbr uses Gerrit for code review.
Please visit
http://docs.openstack.org/infra/manual/developers.html#development-workflow
and follow the instructions there to upload your change to Gerrit.


Support external scheduler

There is great value for this project to support many types of schedulers.
Just replacing here to create user's scheduler is the easy way for users to use their scheduler in simulator, but, if user's scheduler is based on different version of Kubernetes or built on a completely different mechanism than kube-scheduler in k/k, it doesn't work.
For those schedulers, I propose here to support "external scheduler".
Users can run any type of scheduler as outside schedulers and that scheduler will communicate with kube-apiserver in the simulator to run simulation on the simulator.
There is drawback to outside scheduler: they cannot change scheduler configuration via Web UI (or simulator API).
But, the big advantage of this is users can use their scheduler with the other advanced features of the simulator like Scenario.
https://github.com/kubernetes-sigs/kube-scheduler-simulator/issues/140
/kind feature
/triage accepted
/priority important-longterm

/retitle Support external scheduler

/priority important-soon

/remove-priority important-soon

/remove-priority important-longterm
/priority important-soon

give this a higher priority. It will important both for version issue and scenario API.

/area simulator

/priority next-release

/assign

/remove-lifecycle rotten
/lifecycle frozen

/remove-priority next-release
Still quite important, but just remove it from next release candidate.

@sanposhiho how to use external scheduler? is there a doc?

We're now working on the prioritized issues for the first release.
We'll work on this after that. (so, not immediately)

@sanposhiho it's ok. just want an instruction for config external scheduler.


(REOPENED) Click on the asbplayer action button in the top-right of the browser window to enable audio recording for this tab.

Ever since last update, when I use the keyboard shortcut to mine a sentence, it shows this error message
"Click on the asbplayer action button in the top-right of the browser window to enable audio recording for this tab."
I do that, I click on the ASB Player action button, it says I'm good to go, but then it shows the same message when I try again. I have not been able to add video or audio to any card in the past two days.
Sorry if this is a known issue, I'm new to this.

@pomaa666 Can you paste any error logs you see here? You can find them in the extension manager.

@killergerbah Hey! I haven't been able to find the reports. However, today it worked again, so I will mark it as solved as seemingly noone else has had this problem

Hello, I am finding this problem again, and I have managed to find the error reports. Here they are:

Thanks for the logs. Do you have any clues regarding how you might be causing the mining command to be spammed? Which shortcut is it?
In the meantime, I suspect that restarting your browser, and using the click-to-mine buttons instead should avoid this issue.

Hello! I have no clue what happens... I am using Ctrl+Shift+X for my shortcut. And, ever since this bug has come up, I only see the mining button on the UI sometimes, most times it looks like this.

@pomaa666 One thing you could try is disabling screenshots from the "streaming video" section of the settings and see if that helps. If it still doesn't work then it'd be good to know if there are any new error logs.
Also, for this to work you can't spam or hold the keyboard shortcut. You just hit it once.

Hey! Thanks again for keeping up. I tried disabling the screenshots from the settings, and it didn't work because the problem seems to be with the audio. I turned off "record audio" from the same panel, and now it works, it adds an image which makes the flashcard more visual. I'm happy with that for now. And, no, I wasn't spamming the shortcut lol, I just hit it once, and get multiple error messages, couldn't tell you why 🤷. Let me know if you find out how to solve the problem with audio, though!

@pomaa666 Since I have am unable to reproduce the issue yourself, if you have time, could you reproduce the problem on your computer, grab the very first error logs that appear and send them here? That would help discern why the audio recording is failing in the first place. Thanks!

Sorry it took so long for me to get back to you, I've been a bit busy. Here are the error logs again, top to bottom of the page.

I just now realized that there are different dropdown menus for each error, I'll post it here in case it helps.

Thanks!

@pomaa666 Do you happen to have any other extension which could be recording the tab at the same time? Maybe it captures similar keyboard shortcuts to trigger recording?

@pomaa666 1.5.0 has some changes that may help prevent you from entering the permanently broken state you're describing. I'd be curious to know if your experience improves with 1.5.0.


CAR AVOIDANCE GAME USING JAVASCRIPT

@Vishal-raj-1 @urvashi-code1255
PLEASE GO THROUGH THIS PROJECT IDEA ONCE AND ASSIGN IT TO ME, IT WILL BE A GREAT CONTRIBUTION TO YOUR AWESOME JAVASCRIPT PROJECTS.
DESCRIPTION
I want to create a car avoidance game using HTML, CSS AND JAVASCRIPT.
FEATURES:

CALCULATES SCORE.
HANDLE DIRECTION WITH ARROW KEYS.
IF CAR COLLIDES WITH ANOTHER CAR, GAME FINISHES.
FINAL SCORE IS DISPLAYED WHEN GAME IS OVER.
REPLAY BUTTON IS ALSO THERE
UI WILL BE SIMILAR TO RACING TRACKS

@pushpakumari5117 I Loved this project idea :) go for it

Thank you so much @urvashi-code1255


Allow deserializing models with json files in tests

I'm trying to write some unit tests where I need the model objects, but there doesn't seem to be a way of doing this without setting up a mock server that takes in a request, which is a lot of overhead for a unit test.

I'm not sure I understand what you are trying to achieve or what is lacking?

You can try to replicate the logic inside server response body parser https://github.com/apollographql/apollo-android/blob/master/apollo-runtime/src/main/java/com/apollographql/apollo/internal/interceptor/HttpResponseBodyParser.java#L36
where you replace response.body().source() with json string

Can you use mockito?
On Sep 11, 2017 8:31 PM, "Mandeep Singh"<EMAIL_ADDRESS>wrote:

@sav007 https://github.com/sav007 What about the case where I don't
want to mock an entire query? For example, what if I want to just want to
deserialize some fragment with some JSON and use that in my test? Is there
any way to do that?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/apollographql/apollo-android/issues/653#issuecomment-328696318,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AEUX3Dw9_syrDoU9RDiNbZy_yh0q7B9mks5shdDLgaJpZM4PRh9H
.

Mocking a JSON model is a lot of effort, I would rather use JSON and deserialize my models from that

@mandrizzle any model generated by Apollo including fragments, has a Mapper class, that can be used to deserialize from JSON. It has one method map(ResponseReader) where response reader can be custom implementation that backed by string json.

Do you have any example of a customer reader?

I don't have right now, but will come up with smth later this week

Guys thanks a lot for this. You've saved a me a lot of effort in my unit tests.


v2.1.0

Update event-listener to v5.0.0. (#67)

Does https://github.com/smol-rs/event-listener/issues/118 affect our use case? If so, it would be preferable to release it first and then release a new version specifying event-listener = "5.1" in Cargo.toml.

Does smol-rs/event-listener#118 affect our use case? If so, it would be preferable to release it first and then release a new version specifying event-listener = "5.1" in Cargo.toml. Otherwise, LGTM.

Yes, see https://github.com/smol-rs/event-listener/pull/120


ConditionTagDefinition

Could we make this class public?  It is a useful one to be able to inherit from and add as a custom tag (have tested successfully)

I've done my own #compare (like #if but with operators).
#compare @index 'eq' 0 // Will be true if current index EQuals 0
#compare @index 'ne' 0 // Will be true if current index is Not Equal to 0
#compare @index 'factor' 2 // Will be true if current index is evenly divided by 2
#compare @index 'gt' 0 // Will be true if current index greater than 0
#compare @index 'ge' 1 // Will be true if current index greater than or equal to 1
#compare @index 'lt' 10 // Will be true if current index less than 10
#compare @index 'le' 9 // Will be true if current index less than or equal to 9
Only had to reproduce a minimal amount of code from ConditionTag into it but I agree. If I could have inherited ConditionTagDefinition it'd be cleaner.

Can u please give me a complete example , how you create ur own #compare tag. i also need to do this type of work.


Add the enterprise option for fixer.io service

Updates documentation and example to leverage https://github.com/florianv/exchanger/pull/53

Thanks @philperusse :)


Dropdown lists : auto close ?

Hi,
I wonder, for dropdown of the list variety, shouldn't a click/touch on a list element automatically close the dropdown ?
My 2 cents

	$(".nav-item").on( "click", function( event ) {
    	if($('.navbar-toggler').is(':visible')) {
            $(".navbar-toggler").trigger('click');
        }
    });

@danger89's solution worked for me.

I am working on a website with React and Bootstrap and had the same problem.
Here is the solution that worked for me (add it inside useEffect on the navigation component):
`//get all nav items elements
let navItems = document.querySelectorAll(".nav-link")
    //iterate the nav items and add a listener to each of them
    navItems.forEach(item => item.addEventListener("click", () => {
        //validate if toggler button is displayed
        if (document.getElementById("button-toggler").offsetParent !== null) {
            //trigger click event of the toggler button
            document.getElementById("button-toggler").click()
        }
    }))`

and Bootstrap

Just as a side note, mixing frameworks is rarely a good idea (there can be many conflicts).

and Bootstrap

Just as a side note, mixing frameworks is rarely a good idea (there can be many conflicts).

Yep, I think the same but, I am not the one who makes desisions. xD


Add UCH

add Chien Hsin University of Science and Technology

https://www.uch.edu.tw/index.htm
http://www.csie.uch.edu.tw/

The university official website URL
https://www.uch.edu.tw/index.htm
An URL of a page on the official website where a long-term (>1 year) IT related course is offered by the university
http://www.csie.uch.edu.tw/

@jimlee0507 Pull request merged. Thank you!


Feature/strict flag post signing

Description of the changes
In the case of LTV/LTA post signing the strict flag was not implemented.
Checklist
Please go over this checklist to increase the chances of your PR being worked on in a timely manner. Deviations are allowed with proper justification (see previous section).

[x] I have read the project's CoC and contribution guidelines.
[x] I understand and agree to the terms in the Developer Certificate of Origin as applied to this contribution.
[x] All new code in this PR has full test coverage.

For new features (delete if not applicable)

[x] I have discussed the implementation of this feature with the project maintainer(s) on the discussion forum or over email.
[x] I have verified that my changes do not break existing API or CLI functionality, or ensured that all breaking changes are clearly documented in this PR.
[x] All public API functionality in this PR is documented.

Hi, sorry about the delay, I didn't have much bandwidth to work on this.
I'm going to merge this with some changes & with regression tests, but from a separate branch since I can't push to yours (perhaps you forgot to enable the "allow maintainers to make changes" option when creating the PR?).
Long story short, I moved the wiring of this option into PostSignInstructions to avoid boolean parameter sprawl. The value of the setting is then derived from the signing context instead of relying on the caller to specify it explicitly (basically, disable strict mode if we're incrementally signing a file that was opened in nonstrict mode). I also tracked down an instance where the fix had not been applied.

Released as part of 0.25.2 today. Thanks for taking the initiative on this!


GTLF animations only work with keyboard when in the same system

Bevy version
"0.8.1"
The release number or commit hash of the version you're using.
Should be latest
[Optional] Relevant system information
If you cannot get Bevy to build or run on your machine, please include:

the Rust version you're using (you can get this by running cargo --version): 1.63.0

Bevy relies on the "latest stable release" of Rust
nightly should generally work, but there are sometimes regressions: please let us know!

the operating system or browser used, including its version Mac OSX 12.5.1 Monterey

If your bug is rendering-related, copy the adapter info that appears when you run Bevy.
You should also consider testing the examples of our upstream dependencies to help isolate any setup-specific issue:

wgpu for rendering problems
winit for input and window management
gilrs for gamepad inputs

What you did
Describe how you arrived at the problem. If you can, consider providing a code snippet or link.
What went wrong
If it's not clear, break this out into:
I've provided a minimal working example here

what were you expecting? It should be possible to separate keyboard input logic from animation triggering into separate systems to separate concerns and decouple animation from player input.

what actually happened?
Instead, animation in response to player input only works when everything is in the same system (function)## Additional information

Other information that can be used to further reproduce or isolate the problem.
Theory: I think there is some sort of synchronization issue with the way bevy handles keyboard inputs.

Your system set_animation_direction is starting to play an animation at every frame. So the animations are never played, and always restarted.
You could check that movement was actually changed in that system before starting an animation, for example with movement.is_changed()

Yep this is correct. I'll cancel this report


Change Char.notify to subscribe

In Bleno,there are onSubscribe: null, // optional notify/indicate subscribe handler, function(maxValueSize, updateValueCallback) { ...}
onUnsubscribe: null, // optional notify/indicate unsubscribe handler, function() { ...}
onNotify: null // optional notify sent handler, function() { ...}
onIndicate: null // optional indicate confirmation received handler, function() { ...}
But in Noble, we only have characteristic.notify(notify[, callback(error)]); // notify is true|false
I suggest we change the method to characteristic.subscribe(subscribe[, callback]).  It will reflect what we do in a better way.
..and before that, we need a simple way to check if the char is subscriptable. (check for CCCD)
even better, we can separate Notification and Indication in Noble.
Thanks.

@VinceGa

But in Noble, we only have characteristic.notify(notify[, callback(error)]); // notify is true|false
I suggest we change the method to characteristic.subscribe(subscribe[, callback]). It will reflect what we do in a better way.

This is a good point however I would prefer the following:

characteristic.subscribe(callback(error)```` which calls characteristic.notify(true, callback``` internally.
characteristic.unsubscribe(callback(error)```` which calls characteristic.notify(false, callback``` internally.

..and before that, we need a simple way to check if the char is subscriptable. (check for CCCD)

Can't characteristic.properties be used for this? https://github.com/sandeepmistry/noble#characteristics-discovered

even better, we can separate Notification and Indication in Noble

We're stuck with them combined, as the OS X CoreBluetooth API does not separate them ...
https://developer.apple.com/library/mac/documentation/CoreBluetooth/Reference/CBPeripheral_Class/index.html#//apple_ref/occ/instm/CBPeripheral/setNotifyValue:forCharacteristic:

Yep, agreed on the new signature.
Yes, the Char Discovered event could be used for this.
Thanks a lot!

@VinceGa great, would you be able to submit a PR for the new API's?

Added in https://github.com/sandeepmistry/noble/commit/472c6036eaa4e9c236e91e23987289d1c074731f


🐛 Fix for repos which do not squash PR commits

Please check if the PR fulfills these requirements

[ ] Tests for the changes have been added (for bug fixes / features)
[ ] PR title follows the guidelines defined in  https://github.com/ossf/scorecard/blob/main/CONTRIBUTING.md#pr-process

What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
Part of #575. Repos which do not squash their PR commits end up with multiple commits associated with a single PR. This PR fixes that.

Does this PR introduce a breaking change? (What changes might users need to make in their application due to this PR?)
No.

Disabled Auto merge.
@azeemshaikh38 Can we add tests for this PR?

Thanks! Looks like the issue is gone. I think it would be great if scorecard could show reviewed commits with --verbosity Debug as well because as far as I can remember I saw projects where PRs weren't reviewed even though scorecard thought they were. It was before the commit-based analysis was introduced though.

Just to clarify, more generally, what I'm trying to say is that it would be great if it was possible to kind of keep track of what scorecard does with --verbosity Debug (or something like that).

Disabled Auto merge.
@azeemshaikh38 Can we add tests for this PR?

Added some basic unit tests.

Thanks! Looks like the issue is gone. I think it would be great if scorecard could show reviewed commits with --verbosity Debug as well because as far as I can remember I saw projects where PRs weren't reviewed even though scorecard thought they were. It was before the commit-based analysis was introduced though.

I think this exists already and this PR improves the log messaging a bit more.

Just to clarify, more generally, what I'm trying to say is that it would be great if it was possible to kind of keep track of what scorecard does with --verbosity Debug (or something like that).

This is hard since the code is going through refactoring and sometimes we lose some debug messages. Although if you let us know what specific messages help we can look into adding those messages. Also, as always, PRs are welcome :)

I think this exists already and this PR improves the log messaging a bit more.

It appears it does. But I ran it with --verbosity Debug (which was supported and is still documented at https://github.com/ossf/scorecard/blob/main/checks/write.md#how-to-write-a-check) but it seems when scorecard switched to another logger it broke Debug:
./scorecard  --repo https://github.com/systemd/systemd --verbosity Debug --show-details --checks Code-Review --format json |& jq
{
  "date": "2022-02-14",
  "repo": {
    "name": "github.com/systemd/systemd",
    "commit": "b6fc52408afa91f2fb7650e6a7d42c65396e7815"
  },
  "scorecard": {
    "version": "4.0.1-88-g1e488a8",
    "commit": "1e488a804fa102dffca444e84f7c8ffbedbb3bce"
  },
  "score": 10.0,
  "checks": [
    {
      "details": null,
      "score": 10,
      "reason": "all last 30 commits are reviewed through GitHub",
      "name": "Code-Review",
      "documentation": {
        "url": "https://github.com/ossf/scorecard/blob/1e488a804fa102dffca444e84f7c8ffbedbb3bce/docs/checks.md#code-review",
        "short": "Determines if the project requires code review before pull requests (aka merge requests) are merged."
      }
    }
  ],
  "metadata": null
}

With debug instead of Debug it works:
{
  "date": "2022-02-14",
  "repo": {
    "name": "github.com/systemd/systemd",
    "commit": "b6fc52408afa91f2fb7650e6a7d42c65396e7815"
  },
  "scorecard": {
    "version": "4.0.1-88-g1e488a8",
    "commit": "1e488a804fa102dffca444e84f7c8ffbedbb3bce"
  },
  "score": 10.0,
  "checks": [
    {
      "details": [
        "Debug: commit b6fc52408afa91f2fb7650e6a7d42c65396e7815 was reviewed through GitHub #22510 approved merge request",
        "Debug: commit f3376ee8fa28aab3f7edfad1ddfbcceca5bc841c was reviewed through GitHub #22487 approved merge request",
        "Debug: commit 88586e5d3217b681af52abb7a8f0ffe52a20a048 was reviewed through GitHub #22508 approved merge request",
        "Debug: commit d1e7fa02ca974c1f10930854fae66c90e16de189 was reviewed through GitHub #22507 approved merge request",
        "Debug: commit 1d7150ec7fd819805b2a19b1dd485be7de54a6a8 was reviewed through GitHub #22509 approved merge request",
        "Debug: commit d6b218e7426ef78e1682959c37b015e6eb692dc5 was reviewed through GitHub #22508 approved merge request",
        "Debug: commit c20c77eff8ef1a76ef5aea02df7121507bf9be69 was reviewed through GitHub #22508 approved merge request",
        "Debug: commit 675e7fc22c7ab45bf9f4a4414bf7c87734a00d15 was reviewed through GitHub #22508 approved merge request",
        "Debug: commit a9dac7a6dd31225dbe9633061dcade12c0c90a32 was reviewed through GitHub #22508 approved merge request",
        "Debug: commit 38db6211b5aa6e2fb65883ae3353914e82f5bef1 was reviewed through GitHub #22508 approved merge request",
        "Debug: commit d74da762a3b1edbb7935c3b3a229db601f734125 was reviewed through GitHub #22506 approved merge request",
        "Debug: commit bfba9946a1cd9f9219de9656e47c3ceb534a7bb0 was reviewed through GitHub #22445 approved merge request",
        "Debug: commit d5ac1d4e10e6bec3ab63cd95fb3b729e3e5d1d96 was reviewed through GitHub #22487 approved merge request",
        "Debug: commit f63b5ad93592ff64b5e8a83b63f2a3daade28114 was reviewed through GitHub #22487 approved merge request",
        "Debug: commit<PHONE_NUMBER>8c6979c60d46b7825e9671ee31f09c was reviewed through GitHub #22487 approved merge request",
        "Debug: commit bb6820576870d0b38dbf9f6e489b126558fc87d9 was reviewed through GitHub #22487 approved merge request",
        "Debug: commit a78e472dfd7832a13e3d52797e672d4e77fc2a49 was reviewed through GitHub #22487 approved merge request",
        "Debug: commit d403d8f0d65bdcecf7555a0cf040aa6de3de666e was reviewed through GitHub #22487 approved merge request",
        "Debug: commit fdc5c0429982a0b072736f0031bd61caf48a4193 was reviewed through GitHub #22487 approved merge request",
        "Debug: commit 4cddc18d0ac8127b8cad47d250563dc791c41c10 was reviewed through GitHub #22487 approved merge request",
        "Debug: commit 736783d42035e0e654508cf3ea0ae95e76dbc1f5 was reviewed through GitHub #22487 approved merge request",
        "Debug: commit 9951736b7fe532f266ad8457a889047e1396fb76 was reviewed through GitHub #22487 approved merge request",
        "Debug: commit 93e0d3204c76618c21d7eac1a4952af0a96c3cb9 was reviewed through GitHub #22507 approved merge request",
        "Debug: commit fe9bd5ad3670f6a34f9ea9b4e2c16bec6000ce11 was reviewed through GitHub #22507 approved merge request",
        "Debug: commit e46433bb92e0db1c87591c6dc5e280ceec2842c6 was reviewed through GitHub #22507 approved merge request",
        "Debug: commit 75a505c6006f9ddf536b426941ace1f87b263399 was reviewed through GitHub #22507 approved merge request",
        "Debug: commit b74163607b4e513288d38b7f16e230f5a61400c0 was reviewed through GitHub #22507 approved merge request",
        "Debug: commit fdf9de694f4c55b8cebd9d749f9c17c4bfb32650 was reviewed through GitHub #22505 approved merge request",
        "Debug: commit 42672c80dc9d4d3f918e2e6e49f064155c90d8e4 was reviewed through GitHub #22501 approved merge request",
        "Debug: commit d0ebe2a83579f1f6a300dc50882e99c6018dda01 was reviewed through GitHub #22496 approved merge request"
      ],
      "score": 10,
      "reason": "all last 30 commits are reviewed through GitHub",
      "name": "Code-Review",
      "documentation": {
        "url": "https://github.com/ossf/scorecard/blob/1e488a804fa102dffca444e84f7c8ffbedbb3bce/docs/checks.md#code-review",
        "short": "Determines if the project requires code review before pull requests (aka merge requests) are merged."
      }
    }
  ],
  "metadata": null
}

I don't think I have a lot of bash scripts I have to fix but it would be great if it was possible to keep the command line interface backward compatible going forward (or at least it should fail hard if a flag it can't handle is passed to it)


[BIT-523] Add message to synapse_callback return outputs

BIT-523 Add message to synapse_callback return outputs
Allows direct loss evaluations and statistics to be passed through from the server model synapse execution to the axon logging output, useful to display server-side loss values for verification at validation.

Pull Request Test Coverage Report for Build 9a5ae800-25fb-4b7a-a439-839151f1b03f

3 of 3 (100.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+25.0%) to 83.146%

Totals

Change from base Build eb86b8ab-93e7-4bba-bfa2-ea56ed16d3c4:
25.0%

Covered Lines:
5032

Relevant Lines:
6052

💛  - Coveralls


Consent form should be printable

Ensure that visitors to Future Thinking and all future studies can print he consent form, and make this option explicit, with a button in the interface for doing so.

completed.


Report error under Windows

output.toTuple()->elements()[0].toTensor();

Refer to: issue #4

output.toTuple()->elements()[0].toTensor();

I got the error too !!


MarkUs Demo Server Offline

The demo server (http://www.markusproject.org/admin-demo or http://demo.markusproject.org/) is currently offline.

Hey @mcgibbon,
The demo server should be back up and running, thanks for letting us know! The easy admin login is username "a" with password "a".


How do I specify an extended version？

I'm through the brew install<EMAIL_ADDRESS>PHP8 installed, and then through the brew install<EMAIL_ADDRESS>installation swoole extensions
At present, I need php8 to expand the version of swoole 4.8.11, not 5.1.0, how to specify the extension version，

I found that the swoole version of php7.2 is just 4.8.11. After copying the content of<EMAIL_ADDRESS>to<EMAIL_ADDRESS>I realized the function that I needed to specify the version. But once I or the system automatically executed brew upgrade, swoole's version will be automatically upgraded to version 5. How can I avoid this problem? Thank you

I also tried to copy php7.2 swoole.so directly into php8's<EMAIL_ADDRESS>directory, but php --ri swoole displays Extension 'swoole' not present.

I will copy the contents of<EMAIL_ADDRESS>to<EMAIL_ADDRESS>and then execute the brew reinstall -s<EMAIL_ADDRESS>after the success of the execution, and then execute PHP - ri swoole, I found that swoole version has been successfully changed to<EMAIL_ADDRESS>version. At present, I can only temporarily solve my demands through this method, but it still cannot solve the automatic upgrade problem caused by brew upgrade

You can use brew pin to solve this
https://docs.brew.sh/FAQ#how-do-i-stop-certain-formulae-from-being-updated
But the better way is to fork the project and maintain your own tap, since this tap is updated when a new version is released for an extension, by default it will be updated on your end when you run brew upgrade.

I use After the brew pin<EMAIL_ADDRESS>and then execute The brew upgrade<EMAIL_ADDRESS>found swoole versions have been fixed down, thank you!

However, this is certainly not the final optimal solution, so I hope to be able to support the installation of the specified version, thank you


Testnet RGB Modal

Test-net RGB somewhere
Cross compatibility ( wallet + Desktop wallet + One another Mobile wallet)

Completed


Fix enum exports

Description
Enums should not be exported as types.
Verification

[x] Your code builds clean without any errors or warnings
[x] Manual testing done (required)
[x] All tests run green

Codecov Report
Base: 94.20% // Head: 94.21% // Increases project coverage by +0.00% :tada:

Coverage data is based on head (865730a) compared to base (2a70f44).
Patch coverage: 100.00% of modified lines in pull request are covered.

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #231   +/-   ##
=======================================
  Coverage   94.20%   94.21%
=======================================
  Files          82       82
  Lines        1122     1123    +1
  Branches      330      330
=======================================
+ Hits         1057     1058    +1
  Misses         57       57
  Partials        8        8

Impacted Files
Coverage Δ

src/components/index.ts
100.00% <100.00%> (ø)

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

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


[Bug] Decrement/Increment affeting all rows instead of selected one

Laravel Version: 5.4
PHP Version: 7.1

Description:
If I choose an User and try to decrement , it affects all the users in the database.
Steps To Reproduce:
Open tinker or in your code and try
$user = \App\User::find(1);
$user::decrement('credits');
Instead of just decrementing user with id 1, it decrements all users in table.

Replace :: with ->.

(facepalm)
Thanks @bonzai


Little refactoring

Coverage decreased (-0.04%) to 85.342% when pulling dab8b111d3bec67f97ccd6f6c35117cbdef88fe3 on amousset:small-fixes into 521681c0f7b731608c2965941a80802a125695a2 on lettre:master.


Test to break everything

Breaking stuff to test Travis CI

This was just meant to demonstrate that the Travis-CI build would properly fail when receiving a bad pull request.  It does - the results for future reference can be seen here.


SvelteKit v2 Update!

Describe the feature in detail (code, mocks, or screenshots encouraged)
Full announcement:
https://svelte.dev/blog/sveltekit-2
What type of pull request would this be?
Enhancement
Provide relevant links or additional information.
No response

Got an error installing vite-plugin-tailwind-purgecss:
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR!
npm ERR! While resolving<EMAIL_ADDRESS>npm ERR! Found<EMAIL_ADDRESS>npm ERR! node_modules/vite
npm ERR!   dev<EMAIL_ADDRESS>from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm ERR! node_modules/vite-plugin-tailwind-purgecss
npm ERR!   dev vite-plugin-tailwind-purgecss@"*" from the root project
npm ERR!
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR!
npm ERR!

Since it is mentioned here in the docs (Link), I thought I would post the problem here.

Thanks @ninogjoni, per Nik's updated above he's reported and provided a potential PR fix to Adrian's PurgeCSS plugin. Please follow this for updates. We'll then aim to inform folks to update this plugin alongside any other required migration steps alongside our next release early next week. Thanks!

@AdrianGonz97 has pushed out a fix for the PurgeCSS plugin. We recommend you updated to v0.20 asap!
https://github.com/AdrianGonz97/vite-plugin-tailwind-purgecss/releases/tag/v0.2.0
ATTN: @ninogjoni @daaa1m

Looks like we'll have some updates to viteProcess and a few dependencies when we update our own doc site:
https://kit.svelte.dev/docs/migrating-to-sveltekit-2#vitepreprocess-is-no-longer-exported-from-sveltejs-kit-vite

Just a note for the sites/skeleton.dev migration that the vitePreprocess export is changed: https://kit.svelte.dev/docs/migrating-to-sveltekit-2#vitepreprocess-is-no-longer-exported-from-sveltejs-kit-vite

Quick update on this: the migration for Svelte 4 went smoothly, however I've hit a roadblock with the SvelteKit 2 update. Three issues specifically:

The hook.server.ts iteration of event.cookies.set did not set the path as expected in the migration guide. Setting this manually did not seem to make a difference outside of resolving a highlighted error in that page.
Our DocSiderbar component was incorrectly using a click listener to trigger drawer.close() when an <li> tag was tapped - triggering an a11y warning. This has been migrated to automatically close the drawer on navigation instead.
Unfortunately we're still getting a slew of errors in the terminal complaining that the Stepper component path cannot be resolved. I have no idea why that component specifically.

NOTE: that I did upgrade to the latest version of PurgeCSS

@niktek @AdrianGonz97 I have a pending draft PR here if you guys would like to take a stab at this:
https://github.com/skeletonlabs/skeleton/pull/2325
I'll plan to move forward with our new release today and let folks know we're still testing SK2 support. But generally speaking it should be fine for new projects.

@AdrianGonz97 @niktek I'm going to go ahead and call this a wrap. Feel free to reopen and revisit anytime before we archived the v2 branch, but for now we've got bigger fish to fry.


⚠ Bofrost.at has degraded performance

In 85f0719, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 1367 ms

Resolved: Bofrost.at performance has improved in abab036 after 22 minutes.


Add a $id

The schema should have an $id property to be able to refer to it.

You're absolutely right. Adding an $id property to the schema allows for easy referencing and identification.


Remove test stuff from the changelog

No need to add these to the changelog. Also fixup the wording of the
windows_task change since that's super important and people should know
about it.
Signed-off-by: Tim Smith<EMAIL_ADDRESS>

I'm kind of philosophically opposed to manually hacking up the ChangeLog and think we need to get back to PR titles being the source of truth and being able to regen the ChangeLog (completely) from information in github.   If we just had a log of which version numbers were promoted releases we would have all the information necessary to do that.

@lamont-granquist 🙈 we went away from that because it was such a total disaster. I think hacking up the changelog after the fact in general is not worth the time, but I definitely do not want us to change our current approach.

In the ideal world we'd just get the names right the first time and use the nice new labels to exclude appveyor and travis changes from the changelog. I updated this one primarily because the windows_task change is super significant and we have users waiting on that. The title of the PR was cryptic and not something you could search for. I try to tag things for exclusion and fixup the names as I see them, but it's a best effort sort of thing.

Driving the changelog entirely off the issues and PR titles worked great up until we went down the crazy CI version numbering route.   All we'd need to get back to that was a list of the promoted versions (which is 98% captured in rubygems.org) and we
could teach the changelog generator to construct changelogs entirely from the issue contents and that version log.    Before that it was working pretty well.


Remove git merging code

This was commented out so it wasn't caught.
#no-changelog

Merging without checks since this is a comment only change.