Fixgraph

fix usage of deprecated walk_edges_directed()

Hey, the build is failing. You need to change the iterator for this to work.

Did have to run cargo update to run into this.
And until now, I still haven't figured out how to deal with the return value/type of the iterator.
I tried something like
for edge in self.g.edges_directed(*n, EdgeDirection::Outgoing) {
but in essence don't know how to extract the id from it.

I'm not quite sure about the last commit.
Before the code was matching on a ConstraintEdge. I wanted to reproduce this behaviour but was not able to match on the generic type of a struct. (I did not find out whether this is even possible.)
So the iterator returns something that looks like EdgeReference<Ix = EdgeIndex<ConstraintEdge::EdgeIdx(i)>, _>. I did not find out how to match on the generic types of EdgeReference and EdgeIndex.
This problem also occurs further down...

fixed the compiler errors, but one test is now failing. I need to check that the semantics stayed the same.

this is really appreciated, could you please fix the last conflict? thank you!

sorry that i was not very explicit.
i am aware of the conflict and aware that one testcase is failing, so i guess the semantic of my fix is a different than before. to resolve that i am currently reading the paper that was implemented and understand the algorithm.
i had a look at the merge conflict. it seems to be solvable trivially. but i am not quite sure about the desired way to resolve it. simply merge the master into the fixgraph branch?

yes, preferably, simply fix up fixgraph branch and that should affect this PR in being mergeable

@some-username Hey, sorry I couldn't reply earlier. But here is something that you can refer to make these changes (same petgraph changes that I made in another repo): https://github.com/sushant94/libsmt.rs/commit/596a502ef7b4190c3bad7dd8e975f955c85c2558#diff-715b22b5b97eeb559e4c8148c710f6a2R105
Let me know if you can do that, otherwise I can handle it and merge this in for you :)

@sushant, thanks for the hint. that was useful.
i would like to try to do it. but right now, i have no time. so later today or tomorrow.

yes, preferably, simply fix up fixgraph branch and that should affect this PR, and result in it being mergeable

the question was more on how to fixup the branch. i still have only few git experience, so i'm wondering whether to merge, branch or doing something completely different.

ok, i was a little impatient for the answer on how to fix the merge conflict, so i did a simple merge.
still i did not finish reading the TIE paper and there is still one test failing so i guess the semantics are not correct.
this is probably caused by the confusion whether the target or the source of an edge is/was used. (previously this was the .0 or .1 -notation, but i was not able to find what either was referring to when trying to search the petgraph history.)
i commented the places with respective TODOs.

Stacktrace of failed test is
env RUST_BACKTRACE=1 travis-cargo test
---- backend::lang_c::c_simple::test::c_ast_basic_test stdout ----
	thread 'backend::lang_c::c_simple::test::c_ast_basic_test' panicked at 'not yet implemented', src/backend/lang_c/c_simple.rs:338
stack backtrace:
   1:     0x55cff12f13df - std::sys::backtrace::tracing::imp::write::h6f1d53a70916b90d
   2:     0x55cff12f55dd - std::panicking::default_hook::{{closure}}::h137e876f7d3b5850
   3:     0x55cff12f438d - std::panicking::default_hook::h0ac3811ec7cee78c
   4:     0x55cff12f4a88 - std::panicking::rust_panic_with_hook::hc303199e04562edf
   5:     0x55cff10ad983 - std::panicking::begin_panic::h341b039f84d0b176
                        at /build/rustc-1.13.0+dfsg1/src/libstd/panicking.rs:413
   6:     0x55cff12688b2 - radeco_lib::backend::lang_c::c_simple::CAST::emit_c::h932924a1f281ae53
                        at /tmp/radeco-lib/src/backend/lang_c/c_simple.rs:338
   7:     0x55cff126cc70 - radeco_lib::backend::lang_c::c_simple::CAST::print::h76ebfe302366179e
                        at /tmp/radeco-lib/src/backend/lang_c/c_simple.rs:516
   8:     0x55cff126d412 - radeco_lib::backend::lang_c::c_simple::test::c_ast_basic_test::h654703ecf3b699b9
                        at /tmp/radeco-lib/src/backend/lang_c/c_simple.rs:538
   9:     0x55cff1297f4b - <F as alloc::boxed::FnBox<A>>::call_box::h141ef11b98b7e190
  10:     0x55cff1291443 - std::panicking::try::do_call::h2806fe336a468627
  11:     0x55cff12fcf36 - __rust_maybe_catch_panic
  12:     0x55cff12980f9 - <F as alloc::boxed::FnBox<A>>::call_box::h7fbe52e75ba03afb
  13:     0x55cff12f3250 - std::sys::thread::Thread::new::thread_start::h759e10bc4abc7e72
  14:     0x7f0efc516463 - start_thread
  15:     0x7f0efc0429de - __clone
  16:                0x0 - <unknown>

failures:
    backend::lang_c::c_simple::test::c_ast_basic_test

test result: FAILED. 35 passed; 1 failed; 0 ignored; 0 measured

Which means it fails under emit_c
src/backend/lang_c/c_simple.rs (line 338):
CASTNode::FunctionHeader(_) => unimplemented!(),

Also don't worry with GIT, we can always squash your multiple commits into one, rewrite them or rebase them on top of the repository, if the branch fixgraph will compile and all tests pass in your env, then we can help you with proper git works.

Yes, I have seen that. And as the behavior differs from the behavior before my fix, I assume that I changed the semantics unfortunately I have only very little time right now. I hope I am able to commit something useful before monday.

W00t W00t ! Thank you @some-username

:D
I'm very glad myself. One of the first times to contribute to a project.
Let's continue. :)

LGTM

Sincerely Radeco still does not compile, radeco-lib is ok, but dependencies in Radeco are not properly done. I've made my clone, in case anybody wants to test it out.
If you edit r2pm/db/radeco to fetch sources from https://github.com/smarek/radeco
Compile than fails like this:
> r2pm -i radeco
Processing radeco ...
Already up-to-date.
Install Done For radeco
    Updating git repository `https://github.com/radare/r2pipe.rs`
    Updating registry `https://github.com/rust-lang/crates.io-index`
    Updating git repository `https://github.com/smarek/radeco-lib`
    Updating git repository `https://github.com/radare/esil-rs`
       Fresh libc v0.2.17
       Fresh regex-syntax v0.3.9
       Fresh strsim v0.5.2
       Fresh esil v0.1.0 (https://github.com/radare/esil-rs#3a8375f6)
       Fresh log v0.3.6
       Fresh utf8-ranges v0.1.3
       Fresh winapi v0.2.8
       Fresh lazy_static v0.2.2
       Fresh ordermap v0.2.7
       Fresh rand v0.3.14
       Fresh fixedbitset v0.1.5
       Fresh rustc-serialize v0.3.21
       Fresh winapi-build v0.1.1
       Fresh num-traits v0.1.36
       Fresh petgraph v0.4.1
       Fresh r2pipe v0.4.0 (https://github.com/radare/r2pipe.rs#23018f83)
       Fresh num-integer v0.1.32
       Fresh num-complex v0.1.35
       Fresh memchr v0.1.11
       Fresh num-iter v0.1.32
       Fresh num-bigint v0.1.35
       Fresh aho-corasick v0.5.3
       Fresh kernel32-sys v0.2.2
       Fresh num-rational v0.1.35
       Fresh thread-id v2.0.0
       Fresh num v0.1.36
       Fresh thread_local v0.2.7
       Fresh regex v0.1.80
       Fresh docopt v0.6.86
       Fresh radeco-lib v0.1.0 (https://github.com/smarek/radeco-lib#960c3120)
   Compiling radeco v0.1.0 (file:///home/user/.config/radare2/r2pm/git/radeco)
     Running `rustc src/main.rs --crate-name radeco --crate-type bin -C codegen-units=4 -g --cfg feature=\"default\" --out-dir /home/user/.config/radare2/r2pm/git/radeco/target/debug --emit=dep-info,link -L dependency=/home/user/.config/radare2/r2pm/git/radeco/target/debug -L dependency=/home/user/.config/radare2/r2pm/git/radeco/target/debug/deps --extern r2pipe=/home/user/.config/radare2/r2pm/git/radeco/target/debug/deps/libr2pipe-7486d38511f6d9ac.rlib --extern rustc_serialize=/home/user/.config/radare2/r2pm/git/radeco/target/debug/deps/librustc_serialize-b495e2b03d862e12.rlib --extern log=/home/user/.config/radare2/r2pm/git/radeco/target/debug/deps/liblog-bf16bb9a4912b11d.rlib --extern docopt=/home/user/.config/radare2/r2pm/git/radeco/target/debug/deps/libdocopt-664aa2a6d9ccf7ca.rlib --extern radeco_lib=/home/user/.config/radare2/r2pm/git/radeco/target/debug/deps/libradeco_lib-05b2ae512aff3750.rlib`
error[E0432]: unresolved import `radeco_lib::utils::Analysis`
 --> src/structs.rs:6:25
  |
6 | use radeco_lib::utils::{Analysis, Pipeline, Pipeout, Runner};
  |                         ^^^^^^^^ no `Analysis` in `radeco_lib::utils`

error[E0432]: unresolved import `radeco_lib::utils::Pipeline`
 --> src/structs.rs:6:35
  |
6 | use radeco_lib::utils::{Analysis, Pipeline, Pipeout, Runner};
  |                                   ^^^^^^^^ no `Pipeline` in `radeco_lib::utils`

error[E0432]: unresolved import `radeco_lib::utils::Pipeout`
 --> src/structs.rs:6:45
  |
6 | use radeco_lib::utils::{Analysis, Pipeline, Pipeout, Runner};
  |                                             ^^^^^^^ no `Pipeout` in `radeco_lib::utils`

error[E0432]: unresolved import `radeco_lib::utils::Runner`
 --> src/structs.rs:6:54
  |
6 | use radeco_lib::utils::{Analysis, Pipeline, Pipeout, Runner};
  |                                                      ^^^^^^ no `Runner` in `radeco_lib::utils`

error[E0412]: type name `radeco_lib::utils::Runner` is undefined or not in scope
  --> src/args.rs:67:20
   |
67 |     runner: Option<radeco_lib::utils::Runner>,
   |                    ^^^^^^^^^^^^^^^^^^^^^^^^^ undefined or not in scope
   |
   = help: no candidates by the name of `Runner` found in your project; maybe you misspelled the name or forgot to import an external crate?

error: no method named `get_bin_info` found for type `r2pipe::R2` in the current scope
   --> src/structs.rs:102:31
    |
102 |             let bin_info = r2.get_bin_info().unwrap();
    |                               ^^^^^^^^^^^^

error: no method named `get_reg_info` found for type `r2pipe::R2` in the current scope
   --> src/structs.rs:198:24
    |
198 |             let r = r2.get_reg_info().ok();
    |                        ^^^^^^^^^^^^

error: the type of this value must be known in this context
  --> src/args.rs:89:12
   |
89 |         if runner.is_err() {
   |            ^^^^^^^^^^^^^^^

error: aborting due to 3 previous errors

error: Could not compile `radeco`.

Caused by:
  Process didn't exit successfully: `rustc src/main.rs --crate-name radeco --crate-type bin -C codegen-units=4 -g --cfg feature="default" --out-dir /home/user/.config/radare2/r2pm/git/radeco/target/debug --emit=dep-info,link -L dependency=/home/user/.config/radare2/r2pm/git/radeco/target/debug -L dependency=/home/user/.config/radare2/r2pm/git/radeco/target/debug/deps --extern r2pipe=/home/user/.config/radare2/r2pm/git/radeco/target/debug/deps/libr2pipe-7486d38511f6d9ac.rlib --extern rustc_serialize=/home/user/.config/radare2/r2pm/git/radeco/target/debug/deps/librustc_serialize-b495e2b03d862e12.rlib --extern log=/home/user/.config/radare2/r2pm/git/radeco/target/debug/deps/liblog-bf16bb9a4912b11d.rlib --extern docopt=/home/user/.config/radare2/r2pm/git/radeco/target/debug/deps/libdocopt-664aa2a6d9ccf7ca.rlib --extern radeco_lib=/home/user/.config/radare2/r2pm/git/radeco/target/debug/deps/libradeco_lib-05b2ae512aff3750.rlib` (exit code: 101)

Merged your work, thanks a lot! I hope you'll continue to contribute :)

@smarek can you please open an issue in radeco instead of a lib. And yes, it's a known issue. Radeco (apart from the lib) should be rewritten almost completely.


add mention of steel to dev docs site

The dev docs site doesn't mention Steel yet. This PR adds a brief section to the Ethereum Examples page, to improve findability of Steel.
Questions worth thinking about:

is the risc0-steel crate is the appropriate place to point users
do we want to add mentions/paths to Steel elsewhere (mb in the sidebar?)

Weird that can see the preview, but I cannot see the changes on https://docs-website-git-paulg-mention-steel-risczero.vercel.app/api/blockchain-integration/eth-examples
Also a 404 for access the inspect url https://vercel.com/risczero/docs-website/5weXuQhj5RLTJ7ykoxWN4oKT2n5X - maybe I need to be grated access @pdg744 ?

Idea: Would it be appropriate to expand a bit on each example listed here here on the "why" of Them? The steel blog linked for view cals helps give me a bit more understanding:

How is this different from storage proofs?
With traditional storage proofs, developers must manually select which storage slots their smart contract uses, and re-implement smart contract logic. With steel, all storage slots are discovered and fetched automatically based on the view call execution. This saves developers a significant amount of time and decreases the room of implementation errors, reducing the chance of security vulnerabilities.

Overall I think this page could be a good way to succinctly duscuss not just pointers to what exists, but why each one of these is unique and important for EVM related integrations. :thinking:

Idea: Would it be appropriate to expand a bit on each example listed here here on the "why" of Them?

thanks for raising this idea! i think we should aim for keeping these pretty concise especially considering that this list is likely to grow. that said, this page, and our blockchain docs in general, could use some improvement. would be great for the docs to offer a clearer answer to the question of "where should i start?" and "where should i go next?" when it comes to blockchain development.


Application-wide default for input-sizes (HxDefaults.InputSize?)

Instead of having to set HxComponent.Defaults.InputSize for every single input component, allow using some central setting such as HxDefault.sInputSize.
Suggested names?

Duplicates #234


Add PrivateTunnel v2.5

Thank you for the contribution. It needed some fixes, so they were made in 7ecfade182529028627ccf517c8595ce68aa5f62. Your contribution is still included (and still credited to you), with the appropriate modifications. Please feel free to ask about any of the changes.


Some config options cannot be set through cli flags

Description
Hello, I have been working through the migration guide and have hit a roadblock due to changes in config settings
We have many different backend services at different URLS that we generate from, and as far as I can tell it is not possible for us to use one config file and set the input URL separately each run.
Our package.json looks something like this:
"generate": "yarn run generate:facts && yarn run generate:users"
"_generate:base": "openapi-ts --client axios --name AppClient --schemas false --enums typescript",
"generate:facts": "yarn run _generate:base --input https://facts.foobar.com/openapi.json --output ./src/generated/facts",
"generate:users": "yarn run _generate:base --input https://users.foobar.com/openapi.json --output ./src/generated/users",

Since the enums option has been moved in the config file to be under types, it does not appear to be possible to set the enums through the command line anymore, I have tried ---types.enum javascript, --types \\{enums:\\ 'javascript'\\} etc.
Hope you can help
Reproducible example or configuration
No response
OpenAPI specification (optional)
No response
System information (optional)
No response

Hey @JordanWeatherby that's correct, I'd need to add support for nested configuration flags

Yep, agreed

One issue I've noticed with setting output via command line flag is that it overwrites the entire output block to a string even if it was previously an object. So you can't configure formatter/linter options in the file and then set just the output dir at runtime.

I have a script that handles checking if the openapi files are up-to-date with a dry-run mode by swapping the output dir and comparing. But unforatunately I can't do that and also have formatter settings.


update local copy of json backup from aws

Description
Update local backup JSON file

The latest ip ranges from aws is dated 2021-01-07-15-54-18
The current local backup is from 2020-02-18-20-43-10

Thanks, I pushed v1.0.8 with the same change.

Thanks, I pushed v1.0.8 with the same change.


Test coverage for authentication

At a high level this should involve pushing some of the code in main.swift into the XcodesKit module so that it can be tested without invoking xcodes.

Gonna close this for now, I’m probably not going to write tests just for their own sake.


Partial fit single epoch

@stsievert posting this in case any of it is useful for your implementation, no need to review this or anything like that

In addition, BaseWrapper should not default to epochs=1. I think it should default to epochs=200 like SGDClassifier or epochs=100 like Dask-ML's LogisticRegression.
I started to modify the code to do this, but ran into some blockers around initialization.

It's currently epochs=1 because that's the default for Keras.

There's a difference between the Scikit-learn API and the Keras API here. Which API should SciKeras follow?
Relevant questions:

Does a Keras model reinitialize when recalling fit?
Does SciKeras's warm_start default to True?
Is a keras_model.fit used like partial_fit in practice?

Which API should SciKeras follow?

This is a hard question that we're starting to bud up against more and more. I think that in general, we try to follow the Scikit-Learn API. Clearly we've chosen to go with the Scikit-Learn definition of fit, as I think you are hinting at, because Keras' fit acts more like sklearns partial_fit.
To try to answer the actual questions:

Does a Keras model reinitialize when recalling fit?

In vanilla Keras, it does not. Model.fit is closer to partial_fit than fit.

Does SciKeras's warm_start default to True?

It does not. In this sense, we "differ" from Keras.

Is a keras_model.fit used like partial_fit in practice?

It is.

partial_fit should train for 1 epoch.

Isn't that the case on master right now? How does this PR change that?

Currently, this is the behavior:
est = KerasClassifier(..., epochs=10)
est.fit(...)  # trains for 10 epochs
est.partial_fit(...)  # trains for 10 epochs

This PR changes it to:
est = KerasClassifier(..., epochs=10)
est.fit(...)  # trains for 10 epochs
est.partial_fit(...)  # trains for 1 epoch

Got it.
I think the default values of epochs should still be changed. I think that should be implemented in this PR or added to #68.

I think the default values of epochs should still be changed.

I agree it should at least warrant more discussion. I don't think it should be in this PR. I'll edit #51 to reflect that we may want to change the name and/or default value.

Approving because this implements the functionality I'd like to see (but not necessarily the logic I'd prefer).

Could you clarify which logic part is missing? I made it all parameter based. Are you referring to the discussion in #51 ?

Could you clarify which logic part is missing? I made it all parameter based. Are you referring to the discussion in #51

There's no logic missing from this PR. I tried to implement this PR on my fork, so I've seen some of the internal logic. It's not the cleanest, that's all.

Got it. We can always fix internally later, as long as we're not changing the API...

This PR is still ready for merge.

Thanks for the reminder. I would have forgotten to hit the button until tomorrow.


libpam4j authenticate() fails on centos 8 with org.jvnet.libpam.PAMException: pam_acct_mgmt failed : Authentication failure

The libpam4j authenticate() function does not seem to work on the recently released CentOS/RHEL8, at least in a docker container.
See below to reproduce. Maybe some PAM configuration requires changes or something needs to be installed for the PAM functionality used by libpam4j to work on centos 8?
/**
 * This simple test program does not work on centos:8, at least in a docker container.
 * It has been working on centos:6 and centos:7.6.1810 Any idea what changed in centos
 * maybe some configuration is needed to enable something libpam4 relied on?
 *
 # SETUP:
 * Download libpam4j and JNA jars:
 * http://mvnrepository.com/artifact/org.kohsuke/libpam4j
 * https://github.com/twall/jna
 * $ docker run -ti centos:8 bash
   yum install -y passwd # already installed on centos:7.6.1810
   yum install -y java-11-openjdk-devel passwd # same behavior with java-8,
   curl -fLO https://repo1.maven.org/maven2/net/java/dev/jna/jna/5.4.0/jna-5.4.0.jar  # this newer version didn't help
   curl -fLO https://repo1.maven.org/maven2/net/java/dev/jna/jna/4.5.2/jna-4.5.2.jar
   curl -fLO https://repo1.maven.org/maven2/org/kohsuke/libpam4j/1.11/libpam4j-1.11.jar
   useradd -p password gw-john  # -p does not seem to work
   passwd gw-john # enter "password" twice
 * BUILD:
   javac -classpath ./jna-4.5.2.jar:./libpam4j-1.11.jar:. PamHello.java
 * RUN:
   java -classpath ./jna-4.5.2.jar:./libpam4j-1.11.jar:. PamHello gw-john password
 * ERROR on centos8:
Exception: org.jvnet.libpam.PAMException: pam_acct_mgmt failed : Authentication failure
org.jvnet.libpam.PAMException: pam_acct_mgmt failed : Authentication failure
	at org.jvnet.libpam.PAM.check(PAM.java:110)
	at org.jvnet.libpam.PAM.authenticate(PAM.java:131)
	at PamHello.main(PamHello.java:40)
 */
import org.jvnet.libpam.PAM;
import org.jvnet.libpam.UnixUser;
public class PamHello {
    public static void main(String[] argv) {
        if (argv.length != 2) {
            System.out.println("Run: 'PamHello username password' to test libpam4j authentication: " + argv.length);
            System.exit(1);
        }
        try {
            PAM pam = new PAM("login");
            UnixUser u = pam.authenticate(argv[0], argv[1]);
            System.out.println("User " + u.getUserName() + " " + u.getUID() + " " + u.getGID() + " " + u.getDir() + " " + u.getGecos() + " " + u.getShell() + " in " + u.getGroups());
        } catch (Exception e) {
            System.out.println("Exception: " + e);
            e.printStackTrace();
            System.exit(1);
        }
        System.exit(0);
    }
}

There are a few differences between 7 and 8 in the files under /etc/pam.d/ but they don't seem to affect this exception.
I looked for PAM-related changes in RHEL 8, not sure if this is related.
https://www.simplylinuxfaq.com/p/major-differences-between-rhel-8-and-7.html

The securetty PAM module has been disabled by default and the '/etc/securetty' file has been removed from RHEL8.

Closing this as it turns out the problem is a bug or quirk in the official centos:8 image. It contains a file /var/run/nologin that somehow breaks PAM authentication. Just remove the file in your Dockerfile.
FROM centos:8
...
# Fix centos:8 image bug/quirk that breaks PAM authentication: https://github.com/kohsuke/libpam4j/issues/25
RUN rm -f /var/run/nologin
...

The above  java program succeeds once the file is gone.
Will try to followup here if it's a bug in the image:
https://github.com/CentOS/CentOS-Dockerfiles/issues/173


remove special CMAKE_CUDA_ARCHITECTURES, aligned with raft.

issue: #332

kind/improvement

/lgtm

/kind improvement


etebase_client_new throw ETEBASE_ERROR_CODE_MSG_PACK

I trying to implement Etebase on my application but I'm getting stuck on etebase_client_new function which throws ETEBASE_ERROR_CODE_MSG_PACK.
I would know in which case this exception is thrown ?
Also, I would know what is the purpose of the first argument const char *client_name of the function ?
Here is my code :
EtebaseErrorCode EteSync::createClient(std::string &customServerUrl, EtebaseClient **client) {
    const char *serverUrl = serverUrl.empty() ? etebase_get_default_server_url() : customServerUrl.c_str();

    *client = etebase_client_new("client", serverUrl);
    EtebaseErrorCode err = etebase_error_get_code();
    if (err != ETEBASE_ERROR_CODE_NO_ERROR) {
        return err;
    }

    ...

    return ETEBASE_ERROR_CODE_NO_ERROR;
}

Thank you

client_name: should be for error messages, but also user agent for the http request.
msgpack error: means that serializing (or more likely deserializing) the request failed. Most likely because it's not actually an etebase server you are connecting to.
Also, the code is wrong. You should only check the error code if client is NULL. If the previous function did not return null, the value of err is undefined.

Thank you for your answer !
I'm currently working on an API reference, only for C/C++ for now. I will modify the doc according to your comment.
So, it would be nice if we could work together to develop this API reference, because for example it's almost impossible for me to know what exceptions could throw a function because I have to guess it. I've opened a pull request etebase-docs#27

Exceptions: that's a bit opaque at the moment (not documented).
Anyhow, I'm closing this ticket as the issue is solved. Let's talk in the PR.


YoBitExchange throws NullPointerException on creation

Version 4.3.1
This issue could be related to https://github.com/timmolter/XChange/issues/1907 although the stack-trace is different.
ExchangeFactory.createExchange(YoBitExchange.class) consistently throws:
Exception in thread "main" java.lang.IllegalStateException: cannot create digest
	at org.knowm.xchange.yobit.YoBitDigest.createInstance(YoBitDigest.java:24)
	at org.knowm.xchange.yobit.service.YoBitBaseService.<init>(YoBitBaseService.java:18)
	at org.knowm.xchange.yobit.service.YoBitMarketDataServiceRaw.<init>(YoBitMarketDataServiceRaw.java:17)
	at org.knowm.xchange.yobit.service.YoBitMarketDataService.<init>(YoBitMarketDataService.java:38)
	at org.knowm.xchange.yobit.YoBitExchange.initServices(YoBitExchange.java:39)
	at org.knowm.xchange.BaseExchange.applySpecification(BaseExchange.java:106)
	at org.knowm.xchange.ExchangeFactory.createExchange(ExchangeFactory.java:98)
	at org.knowm.xchange.ExchangeFactory.createExchange(ExchangeFactory.java:147)
Caused by: java.lang.NullPointerException
	at org.knowm.xchange.service.BaseParamsDigest.<init>(BaseParamsDigest.java:33)
	at org.knowm.xchange.yobit.YoBitDigest.<init>(YoBitDigest.java:17)
	at org.knowm.xchange.yobit.YoBitDigest.createInstance(YoBitDigest.java:22)
	... 9 more

The code seems to assume that a secret key will be present, though it never checks whether this is the case. If this exchange requires a secret key (i.e. there is no public market data) then the code should assert that a secret key has been provided and provide a nicer error message.

I'm new to using XChange and I've hit this bug. I'd love to be able to use XChange to connect to YoBit. Yobit definitely allows public market data: https://yobit.net/en/api/
I might try to fix this. @timmolter , any advice for me? It there a particularly well implemented exchange I should reference?

I'd only suggest reading this: https://github.com/knowm/XChange/wiki/New-Implementation-Best-Practices
All modules have been more of less implemented in the same way.

Hi all !
Any news about this issue ? :)

Pull request done for this issue :) https://github.com/knowm/XChange/pull/2885


chore(common): upgrade dependencies

What?
This PR upgrades some dependencies and match them to have the same version across the repository.

LGTM! 🎉
Just a question, is there any changes in Vite we need to be aware, or they didn't change anything in those versions that we need to pay attention to?

Nothing! It was just a minor upgrade and nothing changed in terms of usage, AFAIK :D


notify service has stopped working. amazon.in

Describe the bug
The notify service is not working.
The volume control is also not working.
It will work once in span of 3 - 4 hours time. But stops working immediatly.
Since nobody else is reporting this issue I think it might be limited to amazon.in (India)
I am having the same problem in my other house where I have a fresh install of Home Assistant
I am using the inbuilt app for 2FA.
To Reproduce
'
service: notify.alexa_media
data:
message: test
data:
type: announce
target: media_player.beau_hall
'
Expected behavior
The speaker should say test
System details
Home Assistant 2023.8.1
Supervisor 2023.08.1
Operating System 10.4

alexa_media (version from const.py or HA startup): 4.6.5
alexapy (version from pip show alexapy or HA startup):
Amazon 2 factor is enabled

Logs
Logger: homeassistant
Source: /usr/src/homeassistant/homeassistant/runner.py:137
First occurred: August 10, 2023 at 1:41:16 PM (87 occurrences)
Last logged: 1:33:31 PM
Error doing job: Task exception was never retrieved
Traceback (most recent call last):
File "/usr/local/lib/python3.11/site-packages/aiohttp/connector.py", line 1155, in _create_direct_connection
hosts = await asyncio.shield(host_resolved)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/site-packages/aiohttp/connector.py", line 874, in _resolve_host
addrs = await self._resolver.resolve(host, port, family=self._family)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/site-packages/aiohttp/resolver.py", line 33, in resolve
infos = await self._loop.getaddrinfo(
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/asyncio/base_events.py", line 867, in getaddrinfo
return await self.run_in_executor(
^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/concurrent/futures/thread.py", line 58, in run
result = self.fn(*self.args, **self.kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/socket.py", line 962, in getaddrinfo
for res in _socket.getaddrinfo(host, port, family, type, proto, flags):
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
socket.gaierror: [Errno -5] Name has no usable address
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "/usr/local/lib/python3.11/site-packages/alexapy/helpers.py", line 137, in wrapper
return await func(*args, **kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/site-packages/alexapy/alexaapi.py", line 430, in run_behavior
await self._post_request("/api/behaviors/preview", data=data)
File "/usr/local/lib/python3.11/site-packages/alexapy/alexaapi.py", line 225, in _post_request
return await self._request("post", uri, data, query)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/site-packages/backoff/_async.py", line 151, in retry
ret = await target(*args, **kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/site-packages/alexapy/alexaapi.py", line 201, in _request
response = await getattr(self._session, method)(
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/site-packages/aiohttp/client.py", line 536, in _request
conn = await self._connector.connect(
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/site-packages/aiohttp/connector.py", line 540, in connect
proto = await self._create_connection(req, traces, timeout)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/site-packages/aiohttp/connector.py", line 901, in _create_connection
_, proto = await self._create_direct_connection(req, traces, timeout)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/site-packages/aiohttp/connector.py", line 1169, in _create_direct_connection
raise ClientConnectorError(req.connection_key, exc) from exc
aiohttp.client_exceptions.ClientConnectorError: Cannot connect to host alexa.amazon.in:443 ssl:<ssl.SSLContext object at 0x7f1ec34c7260> [Name has no usable address]
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "/usr/local/lib/python3.11/site-packages/alexapy/helpers.py", line 137, in wrapper
return await func(*args, **kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/site-packages/alexapy/alexaapi.py", line 885, in send_tts
await self.send_sequence(
File "/usr/local/lib/python3.11/site-packages/alexapy/helpers.py", line 137, in wrapper
return await func(*args, **kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/site-packages/alexapy/alexaapi.py", line 508, in send_sequence
await self.run_behavior(node_data, queue_delay=queue_delay)
File "/usr/local/lib/python3.11/site-packages/alexapy/helpers.py", line 147, in wrapper
raise AlexapyConnectionError from ex
alexapy.errors.AlexapyConnectionError

I checked the contents of the file alexa_media.sam********mail.com.pickle and they are as below :
'utf-8' codec can't decode byte 0x80 in position 0: invalid start byte
I did a fresh installation with a different account at my other house and the same thing is seen.

You have network errors which is either a hardware or network configuration problem. I can't solve that for you.
annot connect to host alexa.amazon.in:443 ssl:<ssl.SSLContext object at 0x7f1ec34c7260> [Name has no usable address]

Hi. Yes that was the problem. After updating unifi dream machine pro to the latest on 2 separate sites this problem has come up. I have tplink omada in my office and it working fine here.
The firewall rules are fine since all the IOT devices and even the google nest speakers work with TTS in home assistant. Only the echo and alexa related speakers are giving a problem.
Thanks for the heads up will look more into this.

Ok. So I found the problem and it was disabling IGMP snooping. All the services start working after this. This option was working before unifi update so I dont know what changed.


feat: Add functions sum() and avg() to DataArray

Adds two functions to DataArray to calculate the sum and the average of the elements.

This assumes that your array has only column which is a number. There is no option, as far as I can see,  to choose which column to sum or take the average from. Doesn't this reduce the usefulness of such functions?

If you want the sum of a particular column you can always do array.column.sum(). That's how it works in pandas or other libraries.

Nice. It may be worth adding an assertion to fail-fast if it's a type for which + makes no sense but this is fine.


[SIL] Reenable destroy hoisting under lexical lifetimes.

Until https://github.com/apple/swift/pull/40392 lands, run destroy hoisting with lexical lifetimes.

@swift-ci please smoke test

@swift-ci please test and merge

@swift-ci please test and merge


Custom welcome message

Rasa Core version: 0.8.5
Python version: 3.6
Operating system (windows, osx, ...): Ubuntu 16
Issue: Users often request the bot to utter something on startup, instead of being presented with an empty input. rasa-core actually provides a welcome message but it is hard-coded in console.py: "Bot loaded. Type a message and press enter: "
Would it be possible to make this message configurable?
The solution I've found is overwriting the method, but that is a lot of code to change just one element in the method:
...
from rasa_core.channels.console import *
class MyConsoleInputChannel(ConsoleInputChannel):
    def _record_messages(self, on_message, max_message_limit=None):
        utils.print_color("Hallo, ich bin ein ChatBot.",utils.bcolors.OKBLUE)
        num_messages = 0
        while max_message_limit is None or num_messages < max_message_limit:
            text = input().strip()
            if six.PY2:
                # in python 2 input doesn't return unicode values
                text = text.decode("utf-8")
            if text == INTENT_MESSAGE_PREFIX + 'stop':
                return
            on_message(UserMessage(text, ConsoleOutputChannel(),
                                self.sender_id))
        num_messages += 1
...

This is just for the command line though, this doesn't happen when it's deployed on a channel somewhere.
You can easily have the bot say something the first time a user talks to it on a deployed channel though. e.g. if it's on Telegram, you have to start the first conversation by pressing "/start" or something similar. So you can add a story like this:
* start
    - utter_greet

Many thanks for your answer. I was wondering if my workoaround would work for other channels.
This seems to be a challenge for most chatbot frameworks (the MS bot framework has trouble with producing a welcome message, too). Yet our users say they are disoriented by an empty input in the messenger-like GUI frontend. Would you have an advice for making a story like this work?:
## a story example
    - bot_utter_greet
* start
    - utter_what_can_i_do_for_you

i.e. the bot would utter something defined in the domain as soon as the channel is opened

Usually this should be configured in the input / output channel. Nevertheless, I see the point for being able to configure an initial message of the bot when it picks up a conversation. I don't see this being integrated soon though.
The way to do it atm.: when you open a chat, send a message to the bot eg /init which is treated as the first message from the user and the bot can normally respond to it. To the user it will seem as the bot started the conversation. FB let's you easily do that.


Fix #3422 by using the CommandEdit class to support history

Thanks for the PR! I feel that CommandEdit should stay specific for commands, but I'm not too familiar with that code. @kajojify?

CommandEdit should really only be used for commands, closing this.


Unable to authenticate requests from pipectl

What happened:
After v0.24.0-4-g7628abe, pipectl faces this error when running any sub-command.
Error: failed to get application: rpc error: code = Unauthenticated desc = Unauthorized: HTTP status code 401; transport: received the unexpected content-type "text/html; charset=UTF-8"

Before v0.24.0-3-gf087020, it goes well; possibly everything is caused by https://github.com/pipe-cd/pipecd/pull/3046 which is the only change included in v0.24.0-4-g7628abe
What you expected to happen:
How to reproduce it:
Environment:

piped version:
control-plane version:
Others:

/label priority/P1


useRef is returning wrong data from the cache

I have a list of item where I fetch each item by its id.
Here is the scenario:

I click on the first item (key: /api/data/cka9elscf0003x2s5sbqxm5ad) to fetch it
I click on the second one (key: /api/data/cka9elnv60002x2s5kj40qviz)
Then I click on the first one again

Before revalidation, swr is returning for the first item the cached data from the second one. I tried to understand why and I nailed it to the useRef hook.
Here are 2 screenshots of the debugger where the problem is.
When the swr hook is triggered again for the first item, the initialData from the cache is right (notice the id - it's the first item):

But right after, the useRef hook set its data (from initialData) and the returning value is the previous one (notice the id - it's the second item).

I think the problem comes from the useRef hook. Maybe a useEffect hook is necessary to update it?
Happy to help debugging this issue!
Code:
const DataDisplay = ({ id }) => {
  const { data } = useSWR(`/api/data/${id}`)
  console.log(`/api/data/${id}`, data)

  return (<Card>Id: {id}</Card>)
}

Edit: I've just tried using useRef({ data: id }) directly in my component and even tho my props changed, the ref is still returning the old data.
Incorrect code (swr like):
const DataDisplay = ({ id }) => {
  const ref = useRef({ id })
  console.log(`/api/data/${id}`, ref.current.id)

  return (<Card>Id: {id}</Card>)
}

Correct code:
const DataDisplay = ({ id }) => {
  const ref = useRef({ id })
  useEffect(() => {
    ref.current.id = id
  }, [id])

  console.log(`/api/data/${id}`, ref.current.id)

  return (<Card>Id: {id}</Card>)
}

useEffect runs after render, here's how:

ref get assign with initial data: assume the id is "first"
log "/api/data/first", and "first"
render out card with "first"
useEffect runs, ref.current.id gets assign with "first" (nothing changed)
the component update id prop: id is now "second"
prepare ref, but it already has initialized so it gets ignored
log "/api/data/second", and "first".
render out card with "second"
useEffect runs, ref.current.id gets assign with "second" (changed)
end

Feel free to reopen if you have other questions! 👍


[OTHER] Add a custom 404 Not found page

What would you like to share or ask?
Add a custom 404 Not Found page

Additional information
No response

I would like to contribute to this issue.Can you please ellaborate the issue?

Assigin in chronological order go for it @Sukhendu2002  :rocket:

@himanshu1221, Can i do this

Yes Looks good, Generate PR


Create Mozilla Hubs Blender importer

Context and Problem Statement
We need content to be able to export to OMI
Describe the feature / enhancement and how it helps to overcome the problem or limitation
We need to be able to import Mozilla hubs to Blender to be able to export to OMI
Describe how your proposal will work, with code, pseudo-code, mock-ups, and/or diagrams

Modify https://github.com/MozillaReality/hubs-blender-exporter to be able to import
Add import button
Parse MOZ_hubs_components
Import "spawn-point"

If this enhancement will not be used often, can it be worked around with a few lines of script?
Not a few lines
Positive Consequences
Bidirectional import is import for exchanging glbs.
Negative Consequences
No response
Is there a reason why this should be core and done by us?
Can collaborate with Mozilla Hubs Blender team.
References
No response
Derivative License
Copyright (c) 2020-2021 V-Sekai contributors.
Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.
 IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
SOFTWARE.

Superseded by https://github.com/V-Sekai/v-sekai-proposals/issues/41


Add support for custom struct tags

When working with structs, struct tags are used to add additional information to a field. This is for example very common when using validation packages. But currently there is no way to add additional struct tags to take advantage of this.
I think it would be a great idea to add a comment syntax just like the -- name:NameForQuery for table columns.
A possible option to express these custom struct tags would be to write create table statements like this:
CREATE TABLE user (
  id   BIGSERIAL PRIMARY KEY,

  -- tags:`validate:"min=10,max=0"`
  username text NOT NULL,

  -- tags:`validate:"gt=18"`
  age  integer NOT NULL,

  -- tags:`validate:"url"`
  website text NOT NULL
);

or alternatively:
CREATE TABLE user (
  id   BIGSERIAL PRIMARY KEY,
  username text NOT NULL,     -- tags:`validate:"min=10,max=0"`
  age integer NOT NULL,       -- tags:`validate:"gt=18"`
  website text NOT NULL       -- tags:`validate:"url"`
);

Has anyone pickup this enhancement yet?

Is there a way to achieve this now?
I want to ignore the password field on my user struct, like so
type User struct {
    Password string `json:"-"`
}

any solution for this issue please?

@kyleconroy Would you be open to a solution that utilised the config overrides?
Something like the following:
overrides:
  - column: "chat.id"
    custom_tag_key: "gorm"
    go_type:
      type: "int"

I think this might also need something like custom_tag_value for instances like validate where consumers want to set a custom value. Otherwise, the default would be whatever the json emit type is set to.
Further to the above, this wouldn't override json tags, it would be in addition to emitting json tags.

@kyleconroy can we hope to see a feature like this in the foreseeable future? In my project, we started using Gorm way back in time, and it has been something we have been considering moving away from (towards sqlc). However, we rely on some 3rd party code that uses Gorm under the hood, so completely running away from it isn't feasible at the moment.
If there were a way to let sqlc generate our Gorm-compatible models, this would be fantastic. It's the one thing that's stopping us from getting all in on sqlc.
The only other alternative is still keep two copies of each model, which isn't that bad, but possibly error-prone.

I agree that this seems like a good thing to add to the configuration file.

We're facing this right now as well. I'm game to work on it, if we can get to an agreement about the design.
FWIW, I would prefer adding custom struct tags to the config file, using something like:
overrides:
  - column: chat.id
    go_struct_tag: 'validate:"required" sometagtype:"some_value"'

I like that design

Implemented in https://github.com/kyleconroy/sqlc/pull/1569 if anyone wants to kick the tires.


Why always No significant changes?

Describe the bug
I'm first to use this tool to auto release on github.
But every time release content is:

I see https://github.com/antfu/unplugin-vue-components changelog is:

Reproduction
https://github.com/tjx666/unplugin-externalize-deps/releases
System Info
Not need

Used Package Manager
npm
Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guide.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Check that this is a concrete bug. For Q&A, please open a GitHub Discussion instead.
[X] The provided reproduction is a minimal reproducible of the bug.

It only generate for fix/feat/perf by default: https://github.com/antfu/changelogithub/blob/f6995c9cb4dda18a0fa21efe908a0ee6a1fc26b9/src/config.ts#L11-L13

@antfu Hi, sorry for commenting in a closed issue. It seems this is a bug.
You committed https://github.com/antfu/changelogithub/commit/92c3817e03e309401ae910216ab9a77dd2e48162, which begins with feat, however the changelog does not contain this change.


Controller Manager list not returning items

The controller manager is meant to monitor helm releases and retain a cache of them that we can use mgr.client.List() to retrieve.
This is not working, see https://github.com/fidelity/kraan/issues/37.
Need to workout how to make this work.

fixed https://github.com/fidelity/kraan/pull/65


Prepare next release

Description
Preparation of the next major release.
Do you introduce a breaking change?

[x] Yes
[ ] No
[ ] I am unsure (no worries, we'll find out)

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Istio-telemetry rebalancing with session affinity.

Stack driver adapter for mixer v1 needs session affinity from istio-proxy to istio-telemetry pods. If a telemetry pods becomes overloaded,  we start dropping metrics.
Under normal circumstances an HPA will kick in and take up extra load, but this will not happen due to affinity.
We need to experiment and provide guidance for how to distribute load.
Potential solution

Bring up new capacity (several extra pods).
Remove the endpoint of the overloaded pod from endpoints
This should stop new traffic to the pod and give it time to shutdown.
Shutdown the pod. --> this will break existing TCP connections and they will be redistributed to other pods.

@mandarjog this is fairly open-ended. can you help scope the work effort intended?
what priority do you think this should be treated as?
also, how wild can/should we get with our experimentation?  for instance, can/should we consider creating alternate architectures/adapters that push reports into a separate location for offline processing (sorta recreate the mixer backend with a separate set of services)? or say implement/configure some sort of consistent-hashing sharding scheme that uses Mixer's own load-shedding calculations in Mixer's frontend in combination with HPA?

For a customer that plans to use Mixer V1 /Stackdriver in production with 1.2 or 1.3, We need to provide guidance or double back on "please pre-scale". I would not add too much new code if possible, and too much complexity. We would like to have bounded worst case behaviour.


[Discuss] Use WebContentItem for downstream presenter

Offers a sizeable speed improvement when presenting content items with
multiple links. This builds on a spike to simplify WebContentItem as a (currently)
read-only struct with all data fetched in a single query.
Also slims down the ExpandedLinkSet presenter to work solely on a content_id
instead of an entire LinkSet object. This massively reduces both number of queries
and amount of ActiveRecord instantiation required.
This outcome of the spike can be merged as a standalone performance improvement
and built upon for other improvements to PutContent, Publish and PatchLinkSet.
/cc @danielroseman @elliotcm
Before:
Many reverse dependencies: 6667cce2-e809-4e21-ae09-cb0bdc1ddda3
..........
  1.960000   0.160000   2.120000 (  3.817923)
Many forward dependencies: 5eb84e7c-7631-11e4-a3cb-005056011aef
..........
 25.760000   1.680000  27.440000 ( 34.142420)
No dependencies: 23e13323-874f-4210-aad3-ca6ade9206f8
..........
  0.080000   0.000000   0.080000 (  0.103394)
Single link each way: 000227a8-f0d2-417d-8ce4-27a18d62d442
..........
  0.100000   0.020000   0.120000 (  0.150513)
Import export topic: 4bda0be5-3e65-4cc1-850c-0541e95a40ca
..........
113.480000  22.710000 136.190000 (166.417259)

After:
Many reverse dependencies: 6667cce2-e809-4e21-ae09-cb0bdc1ddda3
..........
  2.490000   0.290000   2.780000 (  5.016019)
Many forward dependencies: 5eb84e7c-7631-11e4-a3cb-005056011aef
..........
  1.670000   0.100000   1.770000 (  3.174643)
No dependencies: 23e13323-874f-4210-aad3-ca6ade9206f8
..........
  0.050000   0.010000   0.060000 (  0.083467)
Single link each way: 000227a8-f0d2-417d-8ce4-27a18d62d442
..........
  0.060000   0.020000   0.080000 (  0.119172)
Import export topic: 4bda0be5-3e65-4cc1-850c-0541e95a40ca
..........
 42.300000   7.000000  49.300000 ( 75.734204)

Looks good to me, nice speed improvement. reads better then plain SQL. 👍

Comments addressed

👍


Remove "as const" requirement from Nest API

Currently we need "as const" in the Nest response, investigate whether this can be removed using some kind of type narrowing.

from all i know, type narrowing can only work with functions.
So you'll need something like this :
function response<T extends Response>(res: Narrow<T>): T {
  return res;
}

return response({
  status: 200,
  body: { posts, total: totalPosts },
});


minimummarks not working for an m_n_x MCQ

See git://gist.github.com/1671456.git

Just as a point of order, could you please add some more context than "see gist.XXX"?

I do include some context in the gist reference! But not much it must be admitted. I have included minimum marks set to 0 in an m_n_x question, matrix includes variables which are sometimes set to negative marks. However, the minimum marks constraint is ignored.

It's much more helpful to me if the context is here in the issue, and the gist just contains a compileable exam file.

Agreed - will do this from now on


Add support for AWS EC2 elastic IP addresses

Description:
It would be nice to be able to query for elastic IPs and the resources they're attached to (or not attached to).
[optional Relevant Links:]
https://boto3.amazonaws.com/v1/documentation/api/latest/reference/services/ec2.html#EC2.Client.describe_addresses

Not stale


State gets lost with "soft" reset when using @vite-pwa/nuxt and nuxt-auth-utils

Hi there 👋
I have an issue with using a Nuxt App with PWA functionality when using nuxt-auth-utils for user authentication. To see whether a user is still authenticated, a middleware using the nuxt-auth-utils is used.
Here, the Nuxt useState composable is used to save the session data into the payload.
When using a "hard" refresh, the state for the session gets fetched correctly and the user remains logged in, however the state gets lost when using a normal refresh.
The following repo contains the repro with two branches: the main branch with PWA functionalities and the "no-pwa" branch, which does not have PWA but auth works as expected.
https://github.com/vincentdorian/nuxt-pwa-with-auth.git
I have already tried various workarounds to fetch the session via hooks, but have not been able to restore the state before the middleware gets activated.

Cannot test the app, added .env with the password but getting nitro error on login page and login action, do I need to configure some missing entry in the nuxt.config.ts file?:

PR sent to the repo.

Hiya, Thanks for getting back me.
Other than the NUXT_SESSION_PASSWORD, which should be 32 chars min (which yours is), there should be no additional configuration needed for the repro. That's quite odd. I am using pnpm on WSL, which you seem to do too.
I will try using the configuration in the PR.

I'm not using WSL, I'm using Windows 10 PRO command prompt.

The PR sent solves the error: https://github.com/vincentdorian/nuxt-pwa-with-auth/pull/1#issuecomment-1879817143


Multiple instances of Material UI get imported using web components

Multiple instances of Material UI get imported using web components

[x] The issue is present in the latest release.
[x] I have searched the issues of this repository and believe that this is not a duplicate.

Current Behavior 😯

Two react components are created. Both of them are using material ui button and makeStyles hook to change the background of this button. First one is yellow, the second one is blue.

The second component was build productive as a web component (using direflow, but it shouldn't matter) and imported in the first component

Second button is placed near the first button. Project started

The first button is purple instead of yellow

Expected Behavior 🤔

Yellow button and the blue button near the first one
While loading the page and inspecting it, it is too see, that multiple instances of Material UI were loaded. This also overrides the rules, that were defined in the upper stylesheet.

As we can see the second load from material UI (from component 2) sets .Mui classes on top of makeStyles-button-1
If you delete the second component then the button will be yellow
Your Environment 🌎

`npx @material-ui/envinfo`
  Don't forget to mention which browser you used: **Chrome**
  Output from `npx @material-ui/envinfo` goes here.

  System:
    OS: macOS 10.15.7
  Binaries:
    Node: 14.15.4 - ~/.nvm/versions/node/v14.15.4/bin/node
    Yarn: 1.22.10 - ~/.nvm/versions/node/v14.15.4/bin/yarn
    npm: 6.14.10 - ~/.nvm/versions/node/v14.15.4/bin/npm
  Browsers:
    Chrome: 88.0.4324.96
    Edge: Not Found
    Firefox: 84.0.1
    Safari: 13.1.3
  npmPackages:
    @material-ui/core: ^4.11.2 => 4.11.2
    @material-ui/styles:  4.11.2
    @material-ui/system:  4.11.2
    @material-ui/types:  5.1.0
    @material-ui/utils:  4.11.2
    @types/react: 16.9.3 => 16.9.3
    react: 16.13.1 => 16.13.1
    react-dom: 16.13.1 => 16.13.1
    typescript: ^3.9.3 => 3.9.7

I'm closing for #17473. You need to configure JSS to inject the style in each shadow dom. Unless you have a strong use case for use web components, I wouldn't encourage them.

I'm closing for #17473. You need to configure JSS to inject the style in each shadow dom. Unless you have a strong use case for use web components, I wouldn't encourage them.

You need to configure JSS to inject the style in each shadow dom. Unless you have a strong use case for use web components, I wouldn't encourage them. I'm closing for #17473.

But I'm not using shadow dom. You can see it on the last screenshot in Chrome Dev Tools.

You need to configure JSS to inject the style in each shadow dom. Unless you have a strong use case for use web components, I wouldn't encourage them. I'm closing for #17473.

But I'm not using shadow dom. You can see it on the last screenshot in Chrome Dev Tools.

@GeorgeBalat Please provide a reproduction in this case

@GeorgeBalat Please provide a reproduction in this case


Build Bower package

Hi, have you considered making rangeslider.js independent of Ember CLI? Not all of us use it because of the half-working transpiler and opinionated asset pipeline. I was wondering if you could provide a version of the file in as a standard RequireJS module that only uses AMD when it's detected:
if ( typeof define === "function" && define.amd ) {
    define("ember-cli-nouislider", [], function() {
        return rangeSlider;
    });
} else {
    window.rangeSlider = rangeSlider;
}

I'll have to do some research, but this does sound like a reasonable request!

Given how the ember landscape has now really embraced ember-cli, and even the notion that ember itself could just become an ember-cli addon (ember-data already is), I don't think this is worth pursuing anymore.
If this is still relevant, please open a PR with support for this.
Thanks for the feedback!


It seems the "protocol" (if one can call it that) for this is a bit funny.  First, board will kill power anyway, even if there is no software running (presumably so customers that didn't install script won't complain, at cost of causing hard crash which usually doesn't lead to data loss or corruption).  Second, it seems that a "set fan speed to zero" (over I2C) serves as an "ACK" of the button press (the press itself is signalled via a GPIO pulse, with it's duration encoding type of press). If an "ACK" is received by the board, then it won't kill power, unless a "set fan speed to 255" (note invalid speed value) is sent to explicitly request power-off?
That's my best guess so far, but still need to verify the "protocol".  This is complicated a bit by the fact that, if I mis-guess what the board does/expects, then the hard-crash that the board causes will often lead to lost log messages (so I often have to guess blindly.. argh!).
While at it, might refactor hardware protocol class a bit.

Closed by v0.2.1; see README.md and commit message(s) for more info.  Briefly, the bit about "ACK" above turned out to be an incorrect guess: there is no way to prevent the board from powering off, and neither does there seem to be a way to change the power off delay after a "shutdown" button press to more than 1-2 seconds.
Perhaps the daemon could re-interpret "reboot" (double-press) as "shutdown" but (a) it still can't prevent a hard-crash on a "shutdown" (3-5sec press), and (b) doing so may have inadvertent side-effects (e.g., board powering back on anyway -- most likely to happen, but haven't tested).  Therefore, not much that can be changed/done on the software side, unfortunately.


Is it normal for this prompt to appear repeatedly in the console?

Yep, those are used to help debug. If a user experiences slow performance, this will help identify how slow.


Try to onboard package(s) of FAS user than for Fedora downstream automation

Followup of #2227

[x] check whether the maintainer already uses Packit, if yes, contact them and ask about the feedback, offer help with setting up Packit for their other packages

If no:

[x] contact the maintainer (Matrix/Slack/email), introduce Packit downstream automation and ask if you could create a PR with Packit config for one of their packages (you can ask whether they have access to the upstream repos or would be interested in having the config only in dist-git)

use the mail template (adjust it if needed)

After an agreement:

[ ] check this spreadsheet for the list of packages and choose one (ideally with pending release to rebase, having Git upstream, easy to configure),

the spreadsheet should be updated accordingly, make sure that the package was not onboarded already (there is overlap of the packages since they can have multiple maintainers)

[ ] create a Packit configuration setting up the Fedora downstream automation (for syncing start with one branch to not spam)
[ ] optionally test the syncing locally (see comment)
[ ] create a PR, try to do a test run (/packit pull-from-upstream --with-pr-config) and communicate further with the maintainer the follow-up steps (e.g. create issues if some functionality is missing, setup on more of their packages)

Part of #2204 epic

Moving back to backlog for now, according to the maintainer, it is not easy to automate the update of these packages because they have a big dependency on many other components (Plasma):

I take an example from okular in rawhide. The package has a big dependency on KF6 (a lot of KF6 packages). If we want to update it to a new version, we sometimes have to update KF6 first, if packit does not handle these packages the update of okular will fail


ruksan91Rename access-permissions-on-github.md to access-permissions-on-githu…

…b.mdruksan91

Why:

What's being changed:

Check off the following:

[x] All of the tests are passing.
[x] I have reviewed my changes in staging. (look for the deploy-to-heroku link in your pull request, then click View deployment)
[x] For content changes, I have reviewed the localization checklist
[x] For content changes, I have reviewed the Content style guide for GitHub Docs.

ruksan91:patch-5

ruksan91:patch-5

ruksan91:patch-5

…b.mdruksan91
Why:
What's being changed:
Check off the following:

[x]  All of the tests are passing.
[x]  I have reviewed my changes in staging. (look for the deploy-to-heroku link in your pull request, then click View deployment)
[x]  For content changes, I have reviewed the localization checklist
[x]  For content changes, I have reviewed the Content style guide for GitHub Docs.


docs(README): UglifyJS v3 should be uglify-es

The current README states:

This plugin uses UglifyJS v3 to minify your JavaScript

That is incorrect.
uglify-js@3 only handles ES5, whereas uglify-es handles ES6+.
The README should state:

This plugin uses uglify-es to minify your JavaScript

I thought UglifyJS v3 is uglify-es on npm, where the -es is the 'harmony'  branch/version of uglify (ES2015+), your release/package management is very confusing :). Is it absolutely incorrect to refer to a UglifyJS version? If so, please let me know and I will fix it later then 😛 . Anything else which isn't correct ?

I appreciate that the nomenclature is confusing.
uglify-es is the npm package name based off of the harmony branch of uglify supporting ES6+. The master branch of the UglifyJS2 repository presently only supports ES5 and has the npm package name "uglify-js".
I suppose that uglify-es could loosely be called "Uglify" or "UglifyJS" but when v3 is used there is ambiguity between it and uglify-js. uglify-js@3 only handles ES5, whereas uglify-es@3 handles ES6+. It is fair to say that both share the UglifyJS v3 API, although the uglify-es API is a superset of the uglify-js@3 API.
Perhaps one day uglify-es could be merged into the mainline uglify-js but that's a call for the maintainer of uglify.


Accept API requests with lowercase GUID Keys

As per definition UUIDs are case-insensitive. Yet the Key Pipe verifies UUID values not in their byte representation, but in their case-sensitive string representation.
The Primitive::matches helper method can be handy to address similar quirks with other types.

Thanks @yvo-niedrich  !


grammar check for part-2-app-structure.md

Thanks for the PR!
To better assist you, please select the type of PR you want to create.
Click the "Preview" tab above, and click on the link for the PR type:

:bug: Bug fix or new feature
:memo: Documentation Fix
:book: New/Updated Documentation Content

Thank's!


doubletap event are broken in IE10 / WIndows Phone 8

When you double tap fast (  <= ~200ms ), MSPointerUp event only triggered once.
When you double tap slow (  > ~300ms ), MSPointerUp event can be triggered normal.
Test page
http://jsbin.appfn.com/omavus/6/edit

Closing this in favor of #808, but since this appears to be a unique case of pointer events not working properly on a platform, this particular bug should be accounted for in testing. @arschmitz


Use symlinks to add dists in the Pex CLI.

This avoids copying dists from ~/.pex/installed_wheels to a PEXBuilder
tmpdir before finally zipping up the tmpdir. Instead, with just a single
symlink added to the PEXBuilder tmpdir for each dist, the zip is created
directly from the sources under ~/.pex/installed_wheels providing a
modest speed up when building large PEX files.


[MGDOBR-417]: Create a generic Table component

https://issues.redhat.com/browse/MGDOBR-417
With this PR, the InstancesListPage has been updated, to show how the Table component will be integrated. However, consider that the page itself will be managed later: https://issues.redhat.com/browse/MGDOBR-450

Hi @vpellegrino, quick question before a proper review.
I see you use the "legacy" PF table. The docs say it will still be maintained but new features will only be added to the "default" TableComposable.
Any particular reason behind your choice? Do you think Table is better?

Hi @kelvah.
I've used TableComposable in the past and it led to really complex JSX and complex configuration. It was suggested to me when I wanted to integrate react-table library inside that project.
Since "Both implementations are supported and fully maintained" I decided to use the simple/basic Table which seems more aligned to our mockups/use-cases.
Let me add that the fact that we are wrapping PF Table inside a specific component, will make easy any change we are committed to do in the future, in one shot.
However, if you think we should switch to TableComposable, no issue from my side. Just let me know your opinion.

@vpellegrino Thanks for clarifying.
I think developer experience should not overcome user experience. If choosing a "legacy" tool for ease-of-development could prevent us from bringing new features to the user, then I consider it a bad idea.
This is a general rule, of course. In our context we are talking about a... table. It's not the most complex UI element.
We also do not have particular requirements ATM. Just a table doing table things.
So no big deal right now If you want to stay with Table. We can move over to other things.

@vpellegrino Thanks for clarifying.
I think developer experience should not overcome user experience. If choosing a "legacy" tool for ease-of-development could prevent us from bringing new features to the user, then I consider it a bad idea.
This is a general rule, of course. In our context we are talking about a... table. It's not the most complex UI element.
We also do not have particular requirements ATM. Just a table doing table things.
So no big deal right now If you want to stay with Table. We can move over to other things.

@kelvah looking at your comment, I am a bit worried that you could think that adopting Table can potentially lead to a worse user experience.
I need to clarify that I am always willing to provide the best user experience possible, as the first factor I consider while developing is, indeed, the user.
So, I am going to change Table to TableComposable as you require.

@kelvah accomplished all your feedbacks.
I am just waiting for your answer to https://github.com/5733d9e2be6485d52ffa08870cabdee0/sandbox-ui/pull/10#discussion_r834257488


[AIRFLOW-XXX] Added DataCamp to list of companies in README

We use it to schedule our data pipeline. Thanks for the great work!

Happy to know that you guys are using Airflow :)


Stability checking of VP's position in camera2car auto calibration algorithm

Hi, I have a question for camera2car auto calibration algorithm. I found that there are following words in the paper SensorX2car: Sensors-to-car calibration for autonomous driving in road scenarios: Note that the vehicle doesn’t need to travel straightly all the time. We use the stability of the position of the vanishing point as a judgment condition in our algorithm to extract useful segments.
But when I used image sequences collected in a trajectory composed of both straight part and curve part, the calibration results were pretty bad. I use the pretrained model and it works well for my images representing straight motion, so I think the problem is not in the model.
I am wondering if there are codes conducting the stability checking of VP's position as the paper says? When I was checking the code, it seems that there are no such kind of things.
Thank you very much for your help!

You can add the code, which is very simple. For example, when it is judged that the vanishing point changes very little, it is considered that the vehicle is walking in a straight line, and only this part is used for calibration.

You can add the code, which is very simple. For example, when it is judged that the vanishing point changes very little, it is considered that the vehicle is walking in a straight line, and only this part is used for calibration.

Thank you for your answers, I will try to add the relevant code.


Add K40 Whisperer v0.43

After making all changes to the cask:

[x]  brew cask audit --download {{cask_file}} is error-free.
[x]  brew cask style --fix {{cask_file}} reports no offenses.
[x]  The commit message includes the cask’s name and version. (No version information is published, so the commit only includes the cask name, not version.)
[x]  The submission is for a stable version or documented exception.

Additionally, if adding a new cask:

[x]  Named the cask according to the token reference.
[x]  brew cask install {{cask_file}} worked successfully.
[x]  brew cask uninstall {{cask_file}} worked successfully.
[x]  Checked there are no open pull requests for the same cask.
[x]  Checked the cask was not already refused.
[x]  Checked the cask is submitted to the correct repo.

Hey @alebcay, I've seen in another PR that you are the maintainer of this repo. Do you have access to the TravisCI config? The check fails because some problem related to SSL. There's more info in this issue: Unable to download data from https://rubygems.org/ - SSL_connect returned=1 errno=0 state=SSLv2/v3 read server hello A: tlsv1 alert protocol version #1912


How to know when the end of a cursor-iteration was reached?

We have a test workspace where we run manual and automatic end-2-end tests for our internal API stuff. In this process we create, edit, archive a lot of channels and groups. So over time quite a number of channels (5k+) were created (most of them though being archived). While we store the Slack specific channel and/or group identifier on creation, we have the case that some of the channels existed before and thus a typical channel creation would return name_taken.
As a fallback to that case we try to look up the the channel via name to learn the Slack ID for that channel and then perform an update for it. We therefore use the conversations.list API method which allows us to i.e. specify the size of the number of channels we want to receive per request (needs to be 999 or less) and a cursor to iterate through further results. I'm aware that filters are only applied AFTERWARDS and therefore I can receive less than the specified limit number of channels, which makes checking for receiving less than that limit to exit the loop impossible, at least when archived channels are not included in the result set. I therefore thought that for the last "page" the cursor will be set to null and could therefore be used to exit the loop and avoid having to restart from the beginning again, which reflects in the code below:
    // excludeArchived == true in this case which therefore returns less than the defined limit when
    // channels are archived
    ConversationsListRequest.ConversationsListRequestBuilder rb =
            ConversationsListRequest.builder();
    rb.token(env.getBotToken())
            .limit(limit)
            .excludeArchived(excludeArchived);

    String cursor = null;
    do {
      if (cursor != null) {
        rb.cursor(cursor);
      }

      final ConversationsListResponse response =
              env.getApp().client().conversationsList(rb.build());
      if (response.isOk()) {
        LOG.debug("Retrieved {} channels", response.getChannels().size());
        for (Conversation conversation : response.getChannels()) {
          // do some stuff with the channels
        }
      } else {
        LOG.warn("Failure while retrieving channels. Reason: {}", response.getError());
      }
      LOG.debug("Updating cursor to retrieve next page of channels");
      cursor = response.getResponseMetadata().getNextCursor();

     // attempt to prevent rate-limiting errors as the API basically says 20+ requests per minute
      try {
        Thread.sleep(3000L);
      } catch (InterruptedException iEx) {
        LOG.debug("Sleep was interrupted while waiting for the next poll interval of available "
                + "channels");
        break;
      }
    } while (cursor != null);

With the given code I noticed that the code will "page" through all channels but then start from the beginning all over again and eventually end up in a rate limiting exception even though a sleep of 3 seconds should correspond to 20 requests per minute, which should be within the 20+ requests limit tier 2 operations have.
I thought that at the end of the iteration the cursor would return null to state that there are no further channels to retrieve. Unfortunately, I haven't found anything related to that in the documentation.
So, how do I prevent iterating though the same results over and over again? While a channel lookup per name or at least a filter that is applied BEFORE so that the returned size matches the specified limit where less than that would indicate the end of the list would be great, I'm not sure how much of a change this would be on the Slack API side.

Hey @RovoMe 👋 Really appreciate the code snippet and question! Having a conversations.lookupName method would be super useful here and I've shared this with our teams, but for now we can still tackle this with pagination.
Instead of checking for a null cursor for the end of results when paginating, a check for the empty string will be useful for knowing when no more results are present. Could you check if this change prevents the repeated looping?
-    } while (cursor != null);
+    } while (!cursor.isEmpty());

Will check that on Monday. Our DEV environment is shut down during off-hours since we should not work during these hours :)
In the meantime I did my own "circular loop breaker" logic by storing the first name that is returned and then checking after each request whether I see that name again and then just break the loop. A bit of a duct tape and glue solution but it at least gets the job done for now.

@RovoMe great to hear! Just wanted to check that usergroups.list is returning all the responses with one call and not that it's missing pagination? I'll make a note of this too if so, but am not sure if it'll be tackled with any changes around the conversations.lookupName...
Thanks for checking the change and hope you enjoy the weekend!


docs: Fix incorrect link in listener_filters.rst

Commit Message:
docs: Fix incorrect link in listener_filters.rst
Additional Description:
The docs currently link to network filters instead of listener filters.
Risk Level: None
Testing: Generated preview and confirmed link works
Docs Changes: N/A
Release Notes: N/A
Platform Specific Features: N/A
[Optional Runtime guard:]
[Optional Fixes #Issue]
[Optional Fixes commit #PR or SHA]
[Optional Deprecated:]
[Optional API Considerations:]

Please sign and force push.

Please sign and force push.

Done, thanks for the quick review Kuat!


Closed ways tagged with public_transport=platform should be rendered as areas

URL
https://www.openstreetmap.org/edit?way=470027608#map=19/42.64961/23.39364
How to reproduce the issue?
No response
Screenshot(s) or anything else?
See https://wiki.openstreetmap.org/wiki/Tag:railway=platform
Which iD Editor versions do you see the issue on?
Released version at openstreetmap.org/edit
Which browsers are you seeing this problem on?
Firefox

As far as I can tell, this is a regression from 309bfacf74737d381cb19e8c149ebdf4b7f1d815, which essentially flipped the logic to consider all presets which can be used on lines and areas to be lines by default. This change was not unreasonable, since there exist some commonly used tags which should be handled in such a way: e.g. leisure=track or barrier=wall.
But then there are also examples where the inverse logic should be used: waterway=dam would be an additional example to the already mentioned public_transport=platform. :thinking:


The usemap element on  is obsolete (documentation update)

http://www.w3.org/TR/html5/obsolete.html#attr-input-usemap

Thanks again! As for release timeline, the promise stuff is looking pretty good these days, so I'm thinking I want to wait until that comes out to do a major release on this.

No worries, these are only small things I've picked up for shorthand. I doubt anyone will miss it short term!


Shell up the samples

Hey @PureWeen I remember looking at this when we livestreamed, but it's still in draft. Do you think it's ready to merge or more work required?

Just comment to bring the PR up again. :) Mergeable or closable?


Question: using wkhtmltopdf-heroku during Development on Mac

I'm developing on a MacBook Pro, deploying to Heroku.
I'm following the README, and it tells me that because using pdfkit I don't need to configure anything. However, when I run I get the following error:
command failed (exitstatus=126): ~/.rvm/gems/ruby-2.2.4/gems/wkhtmltopdf-heroku-<IP_ADDRESS>/bin/wkhtmltopdf-linux-amd64 --quiet --page-size Letter --margin-top 8mm --margin-right 8mm --margin-bottom 8mm --margin-left 8mm --encoding UTF-8 - -

So it looks like wkhtmltopdf-linux-amd64 is specific to Ubuntu... README.md is very confusing — it says that pdfkit users don't need to configure anything, yet if you want the app to run on both Mac and Ubuntu there's some configuration necessary.
You will need to configure the path manually. You can get the path to the executable by using this: `Gem.bin_path('wkhtmltopdf-heroku')`

Yes, it seems the path is configured correctly.
The problem here is that you are trying to run a linux(ubuntu) program in OS X. :)
The binary included in this gem only works in Ubuntu 14 LTS (wkhtmltopdf-linux-amd64)
If you need to run it in OS X, please use this:
https://github.com/pallymore/wkhtmltopdf-binary-edge
(just make sure it's only used in development group).

Got it. Working well.


Konflux update test-component-pac-meilfr

Pipelines as Code configuration proposal
To start the PipelineRun, add a new comment with content /ok-to-test
For more detailed information about running a PipelineRun, please refer to Pipelines as Code documentation Running the PipelineRun
To customize the proposed PipelineRuns after merge, please refer to Build Pipeline customization

Pipelines as Code CI/test-component-pac-meilfr-on-pull-request has successfully validated your commit.


VUE_DEVTOOLS_UID' of undefined

Version
4.1.2
Browser and OS info
mac os 10.13.3, Chrome Version 63.0.3239.132
Steps to reproduce
In vue dev tools when i do inspect vue element it gives me error on click elements in left panel :
Error is :
Uncaught TypeError: Cannot read property '__VUE_DEVTOOLS_UID__' of undefined

more
e=>{h=e,function(e){const t=e.__VUE_DEVTOOLS_UID__

What is expected?
don't know what is this.
What is actually happening?
looks like i can't able to click, vue-dev tools hang

i can share video if require.

Be sure you aren't using the .min version of vue
It's not just minified, it is also missing dev tools


fix: api deleted by console bug

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Regenerate Using Latest Swagger to Add Encryption Features

Fixes #15908
This PR regenerates azure-search-documents to add encryption features that were recently added into the swagger.

/azp run java - search - tests

@heaths is the new SHA being used what you were planning on targeting?

I wasn't yet targeting anything specific. Latetly, I've been taking the SHA of the last commit that touched any files we care about, so if this is that SHA, great. But even the latest master commit SHA would be fine. The idea is that regenerating doesn't yield any surprises down the road.


[SPARK-50130][SQL][PYTHON][TEST] Add more test for outer reference

What changes were proposed in this pull request?
Adds more test for outer reference.
Why are the changes needed?
One test is missing.
Does this PR introduce any user-facing change?
No.
How was this patch tested?
Added the test.
Was this patch authored or co-authored using generative AI tooling?
No.

merged to master


Windows Spotlight can't be run after running the tweak

Describe the bug
I'm using Windows 10 on Microsoft Surface Laptop Studio. After running the laptop preset at the Tweak section, the Windows Spotlight doesn't work anymore. It stuck at only 1 image for a week. Beside that, the "Like what you see" button at the lock screen also disappear.
To Reproduce
Steps to reproduce the behavior:

Open Settings
Click on Personalization
Click on Lock screen
At the background section, change to Windows Spotlight
Run PowerShell with Admin privilege
Run the following code: irm christitus.com/win | iex
Click on Tweaks
Click on Laptop
Click on Run Tweaks
After running the tweaks, click Windows + L

Expected behavior
The Windows Spotlight keeps showing only 1 image, day by day.
Screenshots

Thank you for making this tool, as well as reading my report. After running the tweaks, my laptop runs a bit faster. That's what Microsoft must do, but they don't. Thank you so much! All the best wishes to you.

This is a huge backend that eats up system resources. I'd recommend switching it to a more controlled spotlight 3rd party app called "Dynamic Theme" from the MS Store.
It can auto download and switch the lock screen and desktop to spotlight or bing image of the day.


Wrong links and name in charmcraft-prometheus in chamhub.io

I'm trying to deploy charmcraft-prometheus (VM version) from charmhub.io (stable 3)
Multiple issues:

The "URL" in the docs for the VM machine class charm points to this repo. So, I don't know if this issue belongs here, but its the reference in charmhub.io

The URL should point to the correct repo?

The documentation claims it is for Kubernetes, where it clearly is for VM charm (See screenshot)

The charm errors when deploying on AWS. (See separate issue)

As mentioned in #57, that is not the COS Lite charm. The actual charm is available at https://charmhub.io/prometheus-k8s


#57 C++ builder seattle compat

Some patches to increase the compatibility with C++-Builder 10 Seattle.

Thanks. I will include these fixes in the next version.

I have another issue with test qutil: The expected output differs in some lines, because under Windows it's documented that the used strerror or strerror_s function adds a newline to the error message. So if the exception occurs because missing files, on Windows the error message already contains one newline and gets another one using std::endl.
----
before remove
exception: remove file: No such file or directory
----
before fopen
exception: open /this/file/does/not/exist: No such file or directory
----

vs.
----
before remove
exception: remove file: No such file or directory

----
before fopen
exception: open /this/file/does/not/exist: No such file or directory

----

I see some possible solutions: Remove the addition of std::endl in the mentioned tests on Windows by checking _WIN32 or such, always remove an added newline in QUtil::throw_system_error or change your TestDriver to remove empty lines only containing whitespace altogether. Your already available NORMALIZE_WHITESPACE documents to remove newlines, but doesn't actually do so and because you read input files line by line one can't easily implement thing like collapsing newlines to exactly one, because each line is terminated by one newline and afterwards a completely empty line only containing the added newline from std::endl is read.
Optionally removing lines with only whitespace and using that in qutil.test seems reasonable to me.
What do you think?

qtest lets you add filtering to the output. I'd just add filtering for that test case to filter out the extra blank lines, or I'd otherwise modify the test code in a way that doesn't require any _WIN32 checks or anything like that.

If I understand your filter logic correctly, it depends on invoking seperate programs? In that case I find an approach like your already available NORMALIZE_NEWLINES easier to use for every user. If you could have a look at my former commits, they look exactly like what you have donme already and are only some lines of code...

I'll definitely take a look. I'm not sure when I'm going to have time to get to it though. Not for a few weeks at least I'm afraid.

I took all the changes and incorporated the RM_WS_ONLY_LINES into qtest as well. Note that in the PR with the constant in void context, the correct fix was to remove then "\n", not to include it in the print. This makes sense because it was always ignored, so preserving functionality would be to remove it. qtest has a test suite that fails if the "\n" is included. Anyway, these are good changes, and I've tested that they don't break any of the other compilers I'm using. Thanks again!


Is there an optimized function for ( ( a ^ b ) % c )?

Is there an optimized function for this pair of operations ( ( a ^ b ) % c )?
This pair of operations has very broad application in cryptography.
Note: ^ is power and % is reminder.

Yes. It is modpow.


Why it says in the documentation that the token is for testing only

"token - temporary token to advertise (for testing)"

Thanks @JoaoPV , can you also put a reference to the docmentation in question ?

Sry, here>

https://github.com/MohGovIL/rn-contact-tracing#setconfigconfig


pip packaging?

With the new setup.py (https://github.com/neulab/awesome-align/pull/7), it might be nice to also have awesome-align be installable through pip as well?

You can actually can via:
pip install -e git+https://github.com/neulab/awesome-align#egg=awesome_align

Cool, thanks. I guess I actually meant something like "pypi packaging" so you don't need to do it directly with the URL.

Uploaded awesome-align to pypi (https://pypi.org/project/awesome-align/).

@zdou0830 Awesome, thanks! Maybe also update the README?


Downgrading broad admin access in repo create API

Similar to #30, working to protect large swaths of admin permission grants. This change actively downgrades 'admin' permissions to the broad/everyone teams to 'read' only.
A nice-to-have future improvement on this might be to add configuration to opt in or out of this feature if you have a scenario where you want such a large grant.

@jeffwilcox,
Thanks for your contribution as a Microsoft full-time employee or intern. You do not need to sign a CLA.
Thanks,
Microsoft Pull Request Bot


Add support for promises.

I wrapped the ping function inside a promise as below.
const tcpping = opt => new Promise((resolve, reject) => tcpp.ping(opt, (err, data) => err ? reject(err) : resolve(data)));

Perhaps native support for promises could be added.

Native support would mean extra dependencies, and as you noted it's just a one-liner to wrap it if that's what you're using. I'm not sure if it's a good idea.

@nalyd88 util.promisify is a thing since node v8.
const util = require('util');
const tcpping = util.promisify(tcpp.ping)`

@apaszke:  The ease with which callers can do the above aside, Node has had Promise natively since v0.12 so... no extra dependencies, really.  I think this is more about changing tastes in JS development.  Promises weren't the preferred style of coding until more recently, but now that async-await is available, promise-based APIs are (and, imho, should be) the preferred coding style so we don't have to have little hacks like the above all over the place.

If anyone wants to send a PR that sounds good to me, but I'm not actively maintaining this thing, so I can only review it at best.

@nalyd88
`var tcpp = require('tcp-ping');
var util = require('util');
const tcpProbe = util.promisify(tcpp.probe);
const tcpPing = util.promisify(tcpp.ping);
async function ping(ip) {
try {
const result = await tcpPing({address: ip});
console.log(result);
} catch (error) {
console.log(error);
}
}
async function probe(ip, port) {
try {
const result = await tcpProbe(ip, port);
console.log(result);
} catch (error) {
console.log(error);
}
}
probe('<IP_ADDRESS>', 80);
ping('<IP_ADDRESS>');
`

Implemented on #11


Enhance button responsiveness and input field styles for better mobil…

Changes Made:
Improved responsiveness for the "Save" button and input field.
HTML: Ensured proper structure with Bootstrap classes for better alignment.
CSS Updates:
style.css: Added padding and styles for the input field and button.
responsive.css: Implemented media queries for mobile, ensuring full-width button and improved spacing.
Tested on various screen sizes to confirm functionality.

@Web-Dev-Learner please resolve the merge conflicts.

Also please mention your issue no.

Pull Request #2 (Level 1, GSSoC-Ext) , Hacktoberfest.
I've successfully resolved the merge conflicts in the branch fix-savebutton-section.
Changes made:
Adjusted styles and responsiveness for the save button and input fields.
Merged with the latest changes from the main branch.

Ok


Remove unneccessary AppsandFeaturesEntries * manifests/r/RandomEngy/VidCoder/9.18/RandomEngy.VidCoder.installer.yaml

Microsoft Reviewers: Open in CodeFlow

URL:
Invalid URI: The hostname could not be parsed.
(Automated message - build 899)


Expected end of line but found class name

With the new beta version of Iterm I get the following erorr.
47:53: syntax error: Expected end of line but found class name. (-2741)
windows:
   - name: projectName
     root: ~/dev/repos/projectName
     layout: main-vertical
     panes:
       - commands:
         - . ./setantenv.sh
         - ant clean
         - ant all
         - ./startHybris-osx.sh debug
         name: Hybris server
       - commands:
         - git status
         name: 'git'
       - git fetch origin`

I had 2 Iterm versions co-existing, when removing the non beta version the issue was resolved.


[sccache] Fix sccache folders to be consistent and work with move repo

Sccache isn't setup correctly, so this'll make the folders consistent.

Do we still use sccache? I seemed to remember us having some issues with it a while back and can't remember if its even still used

Do we still use sccache? I seemed to remember us having some issues with it a while back and can't remember if its even still used

We can remove it, this just is to make it consistent if some one still uses it

/help

@gregnazario: :key: Insufficient privileges: Not Collaborator

/help

@davidiw: :key: Insufficient privileges: Not Collaborator

/help

Bors help and documentation

Bors is a Github App used to manage merging of PRs in order to ensure that CI is always green. It does so by maintaining a Merge Queue. Once a PR reaches the head of the Merge Queue it is rebased on top of the latest version of the PR's base-branch (generally master) and then triggers CI. If CI comes back green the PR is then merged into the base-branch. Regardless of the outcome, the next PR is the queue is then processed.
General

This project's Merge Queue can be found here.
This project requires PRs to be Reviewed and Approved before they can be queued for merging.
Before PR's can be merged they must be configured with "Allow edits from maintainers" enabled. This is needed for Bors to be able to update PR's in-place so that Github can properly recognize and mark them as "merged" once they've been merged into the upstream branch.

Commands
Bors actions can be triggered by posting a comment which includes a line of the form /<action>.

Command
Action
Description

Land
land, merge
attempt to land or merge a PR

Canary
canary, try
canary a PR by performing all checks without merging

Cancel
cancel, stop
stop an in-progress land

Cherry Pick
cherry-pick <target>
cherry-pick a PR into <target> branch

Priority
priority
set the priority level for a PR (high, normal, low)

Help
help, h
show this help message

Options
Options for Pull Requests are configured through the application of labels.

          Option
Description

Indicates that the PR is high-priority. When queued the PR will be placed at the head of the merge queue.

Indicates that the PR is low-priority. When queued the PR will be placed at the back of the merge queue.

Before merging the PR will be squashed down to a single commit, only retaining the commit message of the first commit in the PR.

/help

Bors help and documentation

Bors is a Github App used to manage merging of PRs in order to ensure that CI is always green. It does so by maintaining a Merge Queue. Once a PR reaches the head of the Merge Queue it is rebased on top of the latest version of the PR's base-branch (generally master) and then triggers CI. If CI comes back green the PR is then merged into the base-branch. Regardless of the outcome, the next PR is the queue is then processed.
General

This project's Merge Queue can be found here.
This project requires PRs to be Reviewed and Approved before they can be queued for merging.
Before PR's can be merged they must be configured with "Allow edits from maintainers" enabled. This is needed for Bors to be able to update PR's in-place so that Github can properly recognize and mark them as "merged" once they've been merged into the upstream branch.

Commands
Bors actions can be triggered by posting a comment which includes a line of the form /<action>.

Command
Action
Description

Land
land, merge
attempt to land or merge a PR

Canary
canary, try
canary a PR by performing all checks without merging

Cancel
cancel, stop
stop an in-progress land

Cherry Pick
cherry-pick <target>
cherry-pick a PR into <target> branch

Priority
priority
set the priority level for a PR (high, normal, low)

Help
help, h
show this help message

Options
Options for Pull Requests are configured through the application of labels.

          Option
Description

Indicates that the PR is high-priority. When queued the PR will be placed at the head of the merge queue.

Indicates that the PR is low-priority. When queued the PR will be placed at the back of the merge queue.

Before merging the PR will be squashed down to a single commit, only retaining the commit message of the first commit in the PR.

/help

Bors help and documentation

Bors is a Github App used to manage merging of PRs in order to ensure that CI is always green. It does so by maintaining a Merge Queue. Once a PR reaches the head of the Merge Queue it is rebased on top of the latest version of the PR's base-branch (generally master) and then triggers CI. If CI comes back green the PR is then merged into the base-branch. Regardless of the outcome, the next PR is the queue is then processed.
General

This project's Merge Queue can be found here.
This project requires PRs to be Reviewed and Approved before they can be queued for merging.
Before PR's can be merged they must be configured with "Allow edits from maintainers" enabled. This is needed for Bors to be able to update PR's in-place so that Github can properly recognize and mark them as "merged" once they've been merged into the upstream branch.

Commands
Bors actions can be triggered by posting a comment which includes a line of the form /<action>.

Command
Action
Description

Land
land, merge
attempt to land or merge a PR

Canary
canary, try
canary a PR by performing all checks without merging

Cancel
cancel, stop
stop an in-progress land

Cherry Pick
cherry-pick <target>
cherry-pick a PR into <target> branch

Priority
priority
set the priority level for a PR (high, normal, low)

Help
help, h
show this help message

Options
Options for Pull Requests are configured through the application of labels.

          Option
Description

Indicates that the PR is high-priority. When queued the PR will be placed at the head of the merge queue.

Indicates that the PR is low-priority. When queued the PR will be placed at the back of the merge queue.

Before merging the PR will be squashed down to a single commit, only retaining the commit message of the first commit in the PR.

/help
Guess i'll join in the fun

@bmwill: :key: Insufficient privileges: Not Collaborator

Closing, as there doesn't seem to be a want to fix the sccache config and I no longer have access to this repo