text:
likelihood encoding and stacking

Hi kazanova,
Thanks for the great work! I have one question:
When we do apply likelihood encoding, why do we have this:

The second model makes use of the new data_prefix command which tells StackNet to expect different pairs of train and validation data to run stacking on. In other words the User supplies the data per fold. This schema is used because likelihood features and counts are created within cross-validation.

i am confused at this point. If likelihood encoding is applied at a nested cv fold, example: with 10 cv, we have an inner 5 cv. Can we simply stack them instead of using data_prefix to manually do the folds? Is there a case of direct leakage?

Hi @germayneng ,
I'm not @kaz-Anova but I'll try to answer your question ;-) under his control!
There has been a lot of discussion on target/likelihood encoding and stacking during the Porto Seguro's competition on Kaggle.
In particular CPMP made a clear point that not using the same CV folds at each stage of your process may introduce leakage. I may need some time to find the thread...
Likelihood encoding is an estimator by itself and therefore using these features can be seen as a 1st level stacking. In other words if you do use likelihood encoding, you have to perform this inside your CV loop to avoid leakage.
It's not what I've done here : https://www.kaggle.com/ogrellier/xgb-classifier-upsampling-lb-0-283?scriptVersionId=1638269
but it's what Andy Harless did here : https://www.kaggle.com/aharless/xgboost-cv-lb-284
Now StackNet has a different random number generator than say Python and if you do stacking with it and performed likelihood encoding in Python with a given CV fold seed you want to tell StackNet what these folds are.
The only way to do this is to provide StackNet with the folds directly using data_prefix and I think that is why @kaz-Anova encourages users to use data_prefix and avoid any sort of leakage.
Hope this helps and let me know if what I wrote is not clear.
Cheers, Olivier

repo: kaz-Anova/StackNet


text:
vue-i18n-service

Hi @kazupon,
First of all great plugin! Keep up good work!
Our translation team wants "one file" to translate all the documents. And making them all global is not manageable, my global translation file becomes a mess.
So I made an extension to extract all the <i18n> tags into a file, and after bulk edit in one file, distribute them back to the .vue files. It's named vue-i18n-service (https://github.com/f/vue-i18n-service)
It uses Vue's template compiler to parse .vue files and extract <i18n> tags.
cd /my/vue/project
npx vue-i18n-service export > translations.json

generates an output like:
{
  "src/components/Hello.vue": {
    "en": {
      "hello": "Hello"
    },
    "tr": {
      "hello": "Merhaba"
    }
  },
  "src/views/World.vue": {
    "en": {
      "world": "World"
    },
    "tr": {
      "world": "Dünya"
    }
  }
}

And after editing this file, you can simply change all the files by running
npx vue-i18n-service import < translations.json

And TA-DA! Done. All of your files were updated :)
I'm asking if the plugin interface would support this by opening a code editor and saving it?

@f
That's awesome SFC locale message management tool! 🚀
I'll plan to support locale messages of SFCs in this plugins for the future. 😉
https://github.com/kazupon/vue-cli-plugin-i18n/issues/10

This would help who are waiting for SFC  translations :) Here is the link: https://f.github.io/vue-i18n-translator
A quick dirty work, if you find bugs please inform :)

@f
thank you for your use-case image. :)

source: gharchive/issue

authors: f kazupon

license: MIT

license_type: permissive

license_source: github-api


text:
First launch will always result in a crash, subsequent launches work fine

MC 1.19.2
JumpQuilt 2.3.0

Make a new instance with Forge 43.2.0 (or any version, really)
Add JumpQuilt
Launch the game and crash
Launch the game again - now everything works

Logs: https://gist.github.com/SplendidAlakey/b80dc6af74c4bed007529a9165707338

Can't reproduce.
Works on first launch over here.

Could it be something system related? I can reproduce it 100% consistently on Prism Launcher and CF app. Running Nvidia GTX980 and 16GB RAM at 2133mhz, Windows 10.

I don't have any Nvidia GPU or Windows system able to run MC to verify that, but that doesn't sound like JumpQuilt's fault.

Hmm.. alright. I suspect it's something to do with how Windows manages processes. The error used to be a bit different on previous versions of Forge, it said something along the lines of "[...] can't initialize [...], because library is already in use [...]". So I chalked it up to JumpQuilt being technically ran on Forge first, and so some necessary library was being used by Forge already, which made Quilt crash. I only reported it now, because the error message changed to what it is now, so I thought maybe it's something else.
If you believe it's not a JQ issue, feel free to close this. Otherwise, I'll keep it open for visibility. I've seen at least 1 other person over at Quilt's Discord having the same issue a while ago.

Thinking a bit more about it, I'd blame the download progress window, which uses LWJGL already, which might cause it to refuse to initialize a second time.
Can you reproduce this using Jumploader as well?

I tried supplying a config, that disables that window, before the initial launch. Didn't help.
Jumploader doesn't work for me at all:
Exception caught from launcher
java.lang.reflect.InvocationTargetException
	at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:77)
	at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.base/java.lang.reflect.Method.invoke(Method.java:568)
	at io.github.zekerzhayard.forgewrapper.installer.Main.main(Main.java:57)
	at org.prismlauncher.launcher.impl.StandardLauncher.launch(StandardLauncher.java:88)
	at org.prismlauncher.EntryPoint.listen(EntryPoint.java:126)
	at org.prismlauncher.EntryPoint.main(EntryPoint.java:71)
Caused by: java.lang.reflect.InaccessibleObjectException: Unable to make field private static final java.lang.Object java.nio.file.spi.FileSystemProvider.lock accessible: module java.base does not "opens java.nio.file.spi" to module jumploader
	at java.base/java.lang.reflect.AccessibleObject.checkCanSetAccessible(AccessibleObject.java:354)
	at java.base/java.lang.reflect.AccessibleObject.checkCanSetAccessible(AccessibleObject.java:297)
	at java.base/java.lang.reflect.Field.checkCanSetAccessible(Field.java:178)
	at java.base/java.lang.reflect.Field.setAccessible(Field.java:172)
	at LAYER SERVICE/jumploader@2.1.3/link.infra.jumploader.launch.ReflectionUtil.reflectStaticField(ReflectionUtil.java:17)
	at LAYER SERVICE/jumploader@2.1.3/link.infra.jumploader.launch.serviceloading.FileSystemProviderAppender.handlePreLaunch(FileSystemProviderAppender.java:37)
	at LAYER SERVICE/jumploader@2.1.3/link.infra.jumploader.launch.PreLaunchDispatcher.dispatch(PreLaunchDispatcher.java:21)
	at LAYER SERVICE/jumploader@2.1.3/link.infra.jumploader.Jumploader.onLoad(Jumploader.java:132)
	at MC-BOOTSTRAP/cpw.mods.modlauncher@10.0.8/cpw.mods.modlauncher.TransformationServiceDecorator.onLoad(TransformationServiceDecorator.java:53)
	at MC-BOOTSTRAP/cpw.mods.modlauncher@10.0.8/cpw.mods.modlauncher.TransformationServicesHandler.lambda$loadTransformationServices$11(TransformationServicesHandler.java:116)
	at java.base/java.util.HashMap$Values.forEach(HashMap.java:1065)
	at MC-BOOTSTRAP/cpw.mods.modlauncher@10.0.8/cpw.mods.modlauncher.TransformationServicesHandler.loadTransformationServices(TransformationServicesHandler.java:116)
	at MC-BOOTSTRAP/cpw.mods.modlauncher@10.0.8/cpw.mods.modlauncher.TransformationServicesHandler.initializeTransformationServices(TransformationServicesHandler.java:48)
	at MC-BOOTSTRAP/cpw.mods.modlauncher@10.0.8/cpw.mods.modlauncher.Launcher.run(Launcher.java:87)
	at MC-BOOTSTRAP/cpw.mods.modlauncher@10.0.8/cpw.mods.modlauncher.Launcher.main(Launcher.java:77)
	at MC-BOOTSTRAP/cpw.mods.modlauncher@10.0.8/cpw.mods.modlauncher.BootstrapLaunchConsumer.accept(BootstrapLaunchConsumer.java:26)
	at MC-BOOTSTRAP/cpw.mods.modlauncher@10.0.8/cpw.mods.modlauncher.BootstrapLaunchConsumer.accept(BootstrapLaunchConsumer.java:23)
	at cpw.mods.bootstraplauncher@1.1.2/cpw.mods.bootstraplauncher.BootstrapLauncher.main(BootstrapLauncher.java:141)
	... 8 more
Exiting with ERROR
Process exited with code 2.

As I'm still unable to reproduce this, I'll have to ask you to help debugging this.
Could you please attach a debugger and set a breakpoint on ExceptionInInitializerError?

Nothing shows up, when I'm looking specifically for ExceptionInInitializerError. If I look for any exception, I get a ton, although not sure how relevant, since all of them are caught and handled.

Happens to me too on both Quilt beta and release channels, and on Adoptium and Amazon Corretto JDKs.
My logs are practically the same:
Quilt Loader crash log on first launch.
Minecraft log on first launch crash.
Subsequent Minecraft log after first launch crash.
There is a modpack on CurseForge using JumpQuilt that warns "sometimes the pack crashes on first launch please launch a second time and it will launch successfully."

I am noticing exact same bug.
OS: Linux x64 Arch Linux
GPU: Nvidia RTX 3060
Launching with 3rd party launch PortableMC

Sounds like an Nvidia driver bug, then.
But as said, without you helping further debugging this as mentioned above, I have no way of debugging or fixing anything here.

CF now natively supports QL, so closing this.

authors: Eaterminer FibreTTP SplendidAlakey kb-1000


text:
SCT-1486 Get builds working

attempt one. No dockerhub push at this point

Looks fine. Big blob o' boilerplate.

source: gharchive/pull-request

authors: MrCreosote briehl

repo: kbase/groups


text:
No default_value_os for reliably specifying filesystem paths as default arguments

Affected Version of clap
2.20.3
Expected Behavior Summary
Functions like validator_os and value_of_os should be complemented with a default_value_os.
Actual Behavior Summary
Only default_value and its variants are provided... which means that it's not possible to specify all valid paths as default values.
Sample Code or Link to Sample Code
// env::current_dir is fallible and default_value can't take a callback for lazy eval, so
// resort to "." but future-proof it in case of esoteric platforms.
// (Not perfect, but to_string_lossy() is necessary without a `default_value_os`)
let lazy_currdir = &Component::CurDir.as_os_str().to_string_lossy();

let matches = App::new(env!("CARGO_PKG_NAME"))
    .version(crate_version!())
    // .about("Description text here")
    // TODO: Add args to control slog logging level
    .arg(arg::with_name("inpath")
        .help("file(s) to use as input")
        .multiple(true)
        .empty_values(false)
        .default_value(lazy_currdir)
        // .validator_os(validators::path_readable)
        .required(true))
    .get_matches();

(It's an excerpt from the "new project" boilerplate I'm putting together)

While I agree there could be a default_value_os and I'm not opposed to adding it, do you actually need to add a path with invalid UTF-8? I know it's possible, but that doesn't mean it's practical. I'm asking for my own curiosity :wink:

At the moment, it's more a matter of wanting correctness in how I glue the "get me the current directory" APIs to clap and wanting the APIs I deal with to be complete.
However, there is actually a set of situations where I expect this to be a problem. Some of the projects I have on hold (currently partially prototyped in old Python code using optparse) embed a shell in a way where default values can get very dynamic... and I intend to use them on folders where round-tripping through different distros over the years has not been kind.
(ie. Folders full of files with Japanese filenames names so mojibake'd that they're not even valid UTF-8)
As-is, to play it safe in those projects, I'll be setting a dummy default value (probably \0) and then reinventing defaulting using match if I don't have default_value_os.

I finally got around to looking at this and it seems you implemented default_value_if_os and default_value_ifs_os but, despite the commit message saying it should be there, you neglected to implement default_value_os.
I can't find any evidence of it in the diff and here are the search results from locally-built docs for clap 2.23.1:

Oh wow!

Thanks for letting me know, I'll get this added shortly!

authors: kbknapp ssokolow

repo: kbknapp/clap-rs

license: mit

license_source: bigquery


text:
Book list

Add a book list to my site that includes "most influential" reads and why they were influential

Instead of a book list, it may be more valuable to write blogs on "core concepts" and then reference books that have helped me understand these core concepts.
I recently learned Naval Ravikant and I have the same reading style. I pick up many books and pick through them - not always finishing the books. I'll be reading many many books at the same time.
I used to look at this as a failure - not having completed all the books. It's valuable to free myself of this and just focus on pure learning. As long as I grasp the core concepts - I've achieved my goal and do not need to finish the book in order to get a trophy.

repo: kcdenman/mywebsite


text:
feat: impl string-like schema attribute parser and ast printer

1. Does this PR affect any open issues?(Y/N) and add issue references (e.g. "fix #123", "re #123".):

[x] N
[ ] Y

Closes #585
feat: impl string-like schema attribute parser and ast printer

2. What is the scope of this PR (e.g. component or file name):

kclvm/ast/src/token.rs
kclvm/ast_pretty/src/node.rs
kclvm/parser/src/parser/stmt.rs

3. Provide a description of the PR(e.g. more details, effects, motivations or doc link):

[ ] Affects user behaviors
[ ] Contains syntax changes
[ ] Contains variable changes
[ ] Contains experimental features
[ ] Performance regression: Consumes more CPU
[ ] Performance regression: Consumes more Memory
[x] Other

4. Are there any breaking changes?(Y/N) and describe the breaking changes(e.g. more details, motivations or doc link):

[x] N
[ ] Y

5. Are there test cases for these changes?(Y/N) select and add more details, references or doc links:

[x] Unit test
[x] Integration test
[ ] Benchmark (add benchmark stats below)
[ ] Manual test (add detailed scripts or steps below)
[ ] Other

kclvm/ast_pretty/src/test_data/codelayout.input
kclvm/parser/src/tests/error_recovery.rs

Pull Request Test Coverage Report for Build 6770592667

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 87.82%

Totals

Change from base Build 6766089635:
0.0%

Covered Lines:
2300

Relevant Lines:
2619

💛  - Coveralls

authors: Peefy coveralls

repo: kcl-lang/kcl


text:
📖 docs: add rest access patterns, etcd storage path

Replaces #1086

/lgtm
/approve

authors: ncdc sttts

repo: kcp-dev/kcp


text:
Retry requests if the connection is closed when we make a request

There's a race condition where we can make a request and the server can close the tcp connection at the same time. When this happens we see a connection closed error. I was able to reproduce this behavior by running a local apache server with the following keep alive settings:
KeepAlive On
KeepAliveTimeout 1
MaxKeepAliveRequests 100

I then ran the following in iex:
Finch.start_link(name: TestPool, pools: %{"http://localhost:8080" => [size: 1, count: 1, protocol: :http1]})
for i <- 0..100 do
  :timer.sleep(1000)
  Finch.request(TestPool, :get, "http://localhost:8080")
end

Using this I was able to determine that we were, in fact, hitting this race condition. If we delay the next request even slightly then the connection waits longer in the pool and we receive the tcp connection closed message in the inbox and correctly clean up the connection. I ran a packet capture which further verified this behaviour.
The solution here is to check if a request returns a closed error. If it does we attempt to re-open the connection and re-issue the request. This should be a safe operation but it still feels...scary. All of this happens in the caller process, which means we could starve the pool if this happens a lot. But, I'm more comfortable with that then forcing a new checkout to happen.
I don't believe that this is the only issue

Digging into it further, I don't think this behaviour is appropriate. Closing this for now.

repo: keathley/finch


text:
Alexa problem whit amazon.de

Excuse me my english is not the best :-)
i have a problem white the integration over HACS- Alexa Media Player 2.0.0
i have my configuration.yaml modifyied with this
Alexa
alexa_media:
accounts:

email: xxxxxxxatxxxxx.de
password: XXXXXXX
url: amazon.com

and capache maked
and i change the URL in:
url: amazon.de and i have confirme
and restart.
my Alexa devices have the state: No state available for media_player.alexa
installed over HACS - Home Assistant version 0.97.2
edit: and i have a problem with this
setup of alexa_media is taking over 10 seconds.
Thanks
Ghosty

Another german here. This is how it works here:
alexa_media:
accounts:
- email: a.b@c.de
password: "password"
url: amazon.de

Hello
my Alexa devices registered in Germany
i have this in my configuration.yaml
alexa_media:
accounts:
- email: a.b@c.de
password: "password"
url: amazon.de
and Home Assistant says -
Alexa Media Player - Begin - email at email.de
Please hit confirm to begin login attempt.
"Confirm"
and I click on Confirm again and again and it does not work
Thanks for your help

I did but it does not work
still the same as in this video
https://github.com/keatontaylor/alexa_media_player/issues/307#issue-485842255
Thanks

Ok, the workaround is described in #307 to downgrade to 1.4.1 login, and then upgrade to 2.0.0. I'll continue debugging in that thread since it has a video to reference.

many thanks for the help.
I managed to connect to Alexa.
All automations, scripts etc .. are available and can be controlled with Alexa.
Home assistant does not find Alexa-Media version 1.4.1
I have the alexa_media_player-master from 22.09.2019 in HASSIO \ config \ custom_components \ alexa_media but he has no connection with Amazon.de.
As soon as I switch to Amazon.com I get Alexa but they are all "Not Available"
I change it again to amazon.de I get told Alexa-media not found. (All under 1.4.1)


text:
PS-756: Project stats api call

Pridal som sem API call na stats. Mozem tohto clienta pouzit v tom Billing API nie? Neni "deprecated"? :)

prijde me, ze je dost deprecated :D

authors: MiroCillik odinuv

repo: keboola/syrup-php-client


text:
E2E tests are unstable

Report
E2E tests are unstable, Solace and Cassandra e2e tests are failing the most of time. Then there are frequent issues with Selenium Grid and Redis related tests.
Specified timeouts are probably to low for these tests.
TODO:

[ ] Solace
[x] Cassandra
[ ] Selenium Grid
[ ] Redis Cluster Streams/Lists
[ ] Redis Sentinel Streams

https://github.com/kedacore/keda/actions?query=workflow%3Anightly-e2e-test

@nilayasiktoprak FYI:
Cassandra test logs:
2021-11-01T14:59:31.1924801Z >>> scalers/cassandra.test.ts.log <<<
2021-11-01T14:59:31.1925387Z
2021-11-01T14:59:31.1926419Z namespace/cassandra-test created
2021-11-01T14:59:31.1927482Z deployment.apps/cassandra created
2021-11-01T14:59:31.1928449Z service/cassandra created
2021-11-01T14:59:31.1929253Z ***
2021-11-01T14:59:31.1929835Z ***
2021-11-01T14:59:31.1930458Z ***
2021-11-01T14:59:31.1944548Z ***
2021-11-01T14:59:31.1945151Z ***
2021-11-01T14:59:31.1945627Z ***
2021-11-01T14:59:31.1946135Z ***
2021-11-01T14:59:31.1946610Z ***
2021-11-01T14:59:31.1947087Z ***
2021-11-01T14:59:31.1947565Z ***
2021-11-01T14:59:31.1948043Z ***
2021-11-01T14:59:31.1948522Z ***
2021-11-01T14:59:31.1949001Z ***
2021-11-01T14:59:31.1949465Z ***
2021-11-01T14:59:31.1950009Z ***
2021-11-01T14:59:31.1950492Z ***
2021-11-01T14:59:31.1950972Z ***
2021-11-01T14:59:31.1951456Z ***
2021-11-01T14:59:31.1951936Z ***
2021-11-01T14:59:31.1952415Z ***
2021-11-01T14:59:31.1952878Z ***
2021-11-01T14:59:31.1953354Z ***
2021-11-01T14:59:31.1953834Z ***
2021-11-01T14:59:31.1954316Z ***
2021-11-01T14:59:31.1954792Z ***
2021-11-01T14:59:31.1955278Z ***
2021-11-01T14:59:31.1955755Z ***
2021-11-01T14:59:31.1956232Z ***
2021-11-01T14:59:31.1956694Z ***
2021-11-01T14:59:31.1957804Z deployment.apps/cassandra-client created
2021-11-01T14:59:31.1958619Z ***
2021-11-01T14:59:31.1959102Z ***
2021-11-01T14:59:31.1959584Z ***
2021-11-01T14:59:31.1960065Z ***
2021-11-01T14:59:31.1960547Z ***
2021-11-01T14:59:31.1961008Z ***
2021-11-01T14:59:31.1961722Z ***
2021-11-01T14:59:31.1962213Z ***
2021-11-01T14:59:31.1962693Z ***
2021-11-01T14:59:31.1963171Z ***
2021-11-01T14:59:31.1963647Z ***
2021-11-01T14:59:31.1964132Z ***
2021-11-01T14:59:31.1964610Z ***
2021-11-01T14:59:31.1965075Z ***
2021-11-01T14:59:31.1965550Z ***
2021-11-01T14:59:31.1966030Z ***
2021-11-01T14:59:31.1966499Z ***
2021-11-01T14:59:31.1966980Z ***
2021-11-01T14:59:31.1967456Z ***
2021-11-01T14:59:31.1967928Z ***
2021-11-01T14:59:31.1968403Z ***
2021-11-01T14:59:31.1968864Z ***
2021-11-01T14:59:31.1969342Z ***
2021-11-01T14:59:31.1969815Z ***
2021-11-01T14:59:31.1970289Z ***
2021-11-01T14:59:31.1970768Z ***
2021-11-01T14:59:31.1971249Z ***
2021-11-01T14:59:31.1971727Z ***
2021-11-01T14:59:31.1972192Z ***
2021-11-01T14:59:31.1973217Z cassandra-client-86f5f57c4b-bcxz2
2021-11-01T14:59:31.1974477Z deployment.apps/nginx-deployment created
2021-11-01T14:59:31.1976048Z scaledobject.keda.sh/cassandra-scaledobject created
2021-11-01T14:59:31.1977289Z secret/cassandra-secrets created
2021-11-01T14:59:31.1978927Z triggerauthentication.keda.sh/keda-trigger-auth-cassandra-secret created
2021-11-01T14:59:31.1980527Z 0
2021-11-01T14:59:31.1981496Z   ✔ Should start off deployment with 0 replicas (290ms)
2021-11-01T14:59:31.1982698Z cassandra-client-86f5f57c4b-bcxz2
2021-11-01T14:59:31.1983525Z 0
2021-11-01T14:59:31.1984000Z 0
2021-11-01T14:59:31.1984457Z 0
2021-11-01T14:59:31.1984936Z 0
2021-11-01T14:59:31.1985404Z 0
2021-11-01T14:59:31.1985876Z 0
2021-11-01T14:59:31.1986329Z 0
2021-11-01T14:59:31.1986797Z 0
2021-11-01T14:59:31.1987265Z 0
2021-11-01T14:59:31.1987735Z 0
2021-11-01T14:59:31.1988452Z 0
2021-11-01T14:59:31.1989223Z 0
2021-11-01T14:59:31.1990218Z 0
2021-11-01T14:59:31.1990717Z 0
2021-11-01T14:59:31.1991185Z 0
2021-11-01T14:59:31.1991653Z 0
2021-11-01T14:59:31.1992320Z 0
2021-11-01T14:59:31.1993359Z 0
2021-11-01T14:59:31.1993842Z 0
2021-11-01T14:59:31.1994312Z 0
2021-11-01T14:59:31.1994762Z 0
2021-11-01T14:59:31.1995235Z 0
2021-11-01T14:59:31.1995700Z 0
2021-11-01T14:59:31.1996183Z 0
2021-11-01T14:59:31.1996655Z 0
2021-11-01T14:59:31.1997105Z 0
2021-11-01T14:59:31.1997582Z 0
2021-11-01T14:59:31.1998670Z 0
2021-11-01T14:59:31.1999158Z 0
2021-11-01T14:59:31.1999627Z 0
2021-11-01T14:59:31.2000863Z   ✖ Replicas should scale to 4 (the max) then back to 0 Replica count should be 4 after 60 seconds
2021-11-01T14:59:31.2002087Z namespace "cassandra-test" deleted
2021-11-01T14:59:31.2002893Z   ─
2021-11-01T14:59:31.2003211Z
2021-11-01T14:59:31.2003905Z   Replicas should scale to 4 (the max) then back to 0
2021-11-01T14:59:31.2004441Z
2021-11-01T14:59:31.2005130Z   scalers/cassandra.test.ts:***09
2021-11-01T14:59:31.2005629Z
2021-11-01T14:59:31.2006222Z    ***08:
2021-11-01T14:59:31.2007759Z    ***09:     t.is(maxReplicaCount, replicaCount, `Replica count should be ${maxR…
2021-11-01T14:59:31.2008764Z    ***0:
2021-11-01T14:59:31.2009163Z
2021-11-01T14:59:31.2009836Z   Replica count should be 4 after 60 seconds
2021-11-01T14:59:31.2010339Z
2021-11-01T14:59:31.2010857Z   Difference:
2021-11-01T14:59:31.2011254Z
2021-11-01T14:59:31.2011908Z   - '4'
2021-11-01T14:59:31.2012508Z   + '0'
2021-11-01T14:59:31.2012846Z
2021-11-01T14:59:31.2013667Z   › scalers/cassandra.test.ts:***09:7
2021-11-01T14:59:31.2014168Z
2021-11-01T14:59:31.2014763Z   ─
2021-11-01T14:59:31.2015079Z
2021-11-01T14:59:31.2015799Z   *** test failed

KEDA Operator logs related to Cassandra:
2021-11-01T14:59:32.0823763Z 202***-***-0***T***4:48:25.590Z	INFO	controller.scaledobject	Reconciling ScaledObject	{"reconciler group": "keda.sh", "reconciler kind": "ScaledObject", "name": "cassandra-scaledobject", "namespace": "cassandra-test"}
2021-11-01T14:59:32.0826654Z 202***-***-0***T***4:48:25.590Z	INFO	controller.scaledobject	Adding Finalizer for the ScaledObject	{"reconciler group": "keda.sh", "reconciler kind": "ScaledObject", "name": "cassandra-scaledobject", "namespace": "cassandra-test"}
2021-11-01T14:59:32.0830282Z 202***-***-0***T***4:48:25.62***Z	INFO	controller.scaledobject	Detected resource targeted for scaling	{"reconciler group": "keda.sh", "reconciler kind": "ScaledObject", "name": "cassandra-scaledobject", "namespace": "cassandra-test", "resource": "apps/v***.Deployment", "name": "nginx-deployment"}
2021-11-01T14:59:32.0834414Z 202***-***-0***T***4:48:25.62***Z	INFO	controller.scaledobject	Creating a new HPA	{"reconciler group": "keda.sh", "reconciler kind": "ScaledObject", "name": "cassandra-scaledobject", "namespace": "cassandra-test", "HPA.Namespace": "cassandra-test", "HPA.Name": "keda-hpa-cassandra-scaledobject"}
2021-11-01T14:59:32.0839109Z 202***-***-0***T***4:48:25.62***Z	ERROR	scalehandler	Error getting triggerAuth	{"type": "ScaledObject", "namespace": "cassandra-test", "name": "cassandra-scaledobject", "triggerAuthRef.Name": "keda-trigger-auth-cassandra-secret", "error": "TriggerAuthentication.keda.sh \"keda-trigger-auth-cassandra-secret\" not found"}
...
2021-11-01T14:59:32.0878894Z 202***-***-0***T***4:48:25.622Z	ERROR	controller.scaledobject	Error getting scalers	{"reconciler group": "keda.sh", "reconciler kind": "ScaledObject", "name": "cassandra-scaledobject", "namespace": "cassandra-test", "error": "error getting scaler for trigger #0: error parsing cassandra metadata: no keyspace given"}

I'm getting:
ERROR	controller	Reconciler error	{"reconcilerGroup": "keda.sh", "reconcilerKind": "ScaledObject", "controller": "scaledobject", "name": "cassandra-scaledobject", "namespace": "cassandra-test", "error": "error getting scaler for trigger #0: no scaler found for type: cassandra"}
I'm not sure why it throws this error, however, I'm on it

@nilayasiktoprak you are probably using old code.
I think I have fixed the problem, see the two PRs mentioned above. Now waiting for a couple of test runs to see if my fixes helped. Let's wait until then.

I already applied your changes to my code yet somehow I get that error

@nilayasiktoprak you have probably old KEDA deployed :) you need to rebuild the code from the main branch.

I have 2.4. Have your changes passed the the tests?

I have 2.4. Have your changes passed the tests?

The code with your scaler will be present with 2.5. You need to build KEDA from main branch until then.
The test is still running here, but it was passing for me locally: https://github.com/kedacore/keda/runs/4071362965?check_suite_focus=true

Oh yes, how come didnt i figure that out! Thank you for reminding that :))

@nilayasiktoprak there is still a problem, it is an intermittent failure, I can reproduce it locally sometimes, sometimes the test passes, see the logs:
2021-11-01T20:25:16.0544454Z cassandra-client-5d88fb86f8-cp9hj
2021-11-01T20:25:16.0546025Z Connection error: ('Unable to connect to any servers', {'***0.0.32.***24:9042': error(***, "Tried connecting to [('***0.0.32.***24', 9042)]. Last error: Connection refused")})
2021-11-01T20:25:16.0547013Z command terminated with exit code ***
2021-11-01T20:25:16.0548291Z Connection error: ('Unable to connect to any servers', {'***0.0.32.***24:9042': error(***, "Tried connecting to [('***0.0.32.***24', 9042)]. Last error: Connection refused")})
2021-11-01T20:25:16.0549267Z command terminated with exit code ***
2021-11-01T20:25:16.0550270Z secret/cassandra-secrets created
2021-11-01T20:25:16.0551617Z triggerauthentication.keda.sh/keda-trigger-auth-cassandra-secret created
2021-11-01T20:25:16.0552995Z deployment.apps/nginx-deployment created
2021-11-01T20:25:16.0554102Z scaledobject.keda.sh/cassandra-scaledobject created
2021-11-01T20:25:16.0554843Z 0
2021-11-01T20:25:16.0555572Z   ✔ Should start off deployment with 0 replicas (229ms)
2021-11-01T20:25:16.0556544Z cassandra-client-5d88fb86f8-cp9hj
2021-11-01T20:25:16.0557984Z Connection error: ('Unable to connect to any servers', {'***0.0.32.***24:9042': error(***, "Tried connecting to [('***0.0.32.***24', 9042)]. Last error: Connection refused")})
2021-11-01T20:25:16.0558959Z command terminated with exit code ***
2021-11-01T20:25:16.0559476Z 0

The problem is, that it might take some time for Cassandra to actually start, even though both Cassandra and Cassandra client pods reports status as Ready, the application itself is still starting, you can see that by checking the logs during the startup.
https://github.com/kedacore/keda/blob/197594dcdb466b822f374b5b99f2aef4a15bbe52/tests/scalers/cassandra.test.ts#L44 ^^ here we should put some check & wait that will actually test that both Cassandra and Client are accessible so the following commands (// create table} don't fail as we can see in the log above.

I'll take the redis ones. I've fought with them before.

Redis Sentinel Streams test is still failing, @jerbob92 FYI:
2021-11-01T21:47:32.4763182Z >>> scalers/redis-sentinel-streams.test.ts.log <<<
2021-11-01T21:47:32.4764610Z
2021-11-01T21:47:32.4765613Z namespace/redis-sentinel-streams created
2021-11-01T21:47:32.4766520Z "bitnami" already exists with the same configuration, skipping
2021-11-01T21:47:32.4767697Z NAME: redis-sentinel-streams
2021-11-01T21:47:32.4768405Z LAST DEPLOYED: Mon Nov  *** 2***:28:58 202***
2021-11-01T21:47:32.4769258Z NAMESPACE: redis-sentinel-streams
2021-11-01T21:47:32.4769909Z STATUS: deployed
2021-11-01T21:47:32.4770413Z REVISION: ***
2021-11-01T21:47:32.4770896Z TEST SUITE: None
2021-11-01T21:47:32.4771553Z NOTES:
2021-11-01T21:47:32.4772032Z CHART NAME: redis
2021-11-01T21:47:32.4772737Z CHART VERSION: ***5.5.3
2021-11-01T21:47:32.4774235Z APP VERSION: 6.2.6
2021-11-01T21:47:32.4774579Z
2021-11-01T21:47:32.4776283Z ** Please be patient while the chart is being deployed **
2021-11-01T21:47:32.4776738Z
2021-11-01T21:47:32.4778164Z Redis™ can be accessed via port 6379 on the following DNS name from within your cluster:
2021-11-01T21:47:32.4778731Z
2021-11-01T21:47:32.4801449Z     redis-sentinel-streams.redis-sentinel-streams.svc.cluster.local for read only operations
2021-11-01T21:47:32.4802827Z
2021-11-01T21:47:32.4803714Z For read/write operations, first access the Redis™ Sentinel cluster, which is available in port 26379 using the same domain name above.
2021-11-01T21:47:32.4804469Z
2021-11-01T21:47:32.4804897Z
2021-11-01T21:47:32.4805165Z
2021-11-01T21:47:32.4805636Z To get your password run:
2021-11-01T21:47:32.4806006Z
2021-11-01T21:47:32.4807967Z     export REDIS_PASSWORD=$(kubectl get secret --namespace redis-sentinel-streams redis-sentinel-streams -o jsonpath="{.data.redis-password}" | base64 --decode)
2021-11-01T21:47:32.4809212Z
2021-11-01T21:47:32.4809752Z To connect to your Redis™ server:
2021-11-01T21:47:32.4810153Z
2021-11-01T21:47:32.4810769Z ***. Run a Redis™ pod that you can use as a client:
2021-11-01T21:47:32.4811221Z
2021-11-01T21:47:32.4812942Z    kubectl run --namespace redis-sentinel-streams redis-client --restart='Never'  --env REDIS_PASSWORD=$REDIS_PASSWORD  --image docker.io/bitnami/redis:6.2.6-debian-***0-r2*** --command -- sleep infinity
2021-11-01T21:47:32.4813988Z
2021-11-01T21:47:32.4814547Z    Use the following command to attach to the pod:
2021-11-01T21:47:32.4814982Z
2021-11-01T21:47:32.4815676Z    kubectl exec --tty -i redis-client \
2021-11-01T21:47:32.4816597Z    --namespace redis-sentinel-streams -- bash
2021-11-01T21:47:32.4817287Z
2021-11-01T21:47:32.4817829Z 2. Connect using the Redis™ CLI:
2021-11-01T21:47:32.4819133Z    redis-cli -h redis-sentinel-streams -p 6379 -a $REDIS_PASSWORD # Read only operations
2021-11-01T21:47:32.4820496Z    redis-cli -h redis-sentinel-streams -p 26379 -a $REDIS_PASSWORD # Sentinel access
2021-11-01T21:47:32.4822510Z
2021-11-01T21:47:32.4823401Z To connect to your database from outside the cluster execute the following commands:
2021-11-01T21:47:32.4824061Z
2021-11-01T21:47:32.4825658Z     kubectl port-forward --namespace redis-sentinel-streams svc/redis-sentinel-streams 6379:6379 &
2021-11-01T21:47:32.4826931Z     redis-cli -h ***27.0.0.*** -p 6379 -a $REDIS_PASSWORD
2021-11-01T21:47:32.4827606Z Waiting for 3 pods to be ready...
2021-11-01T21:47:32.4828238Z Waiting for 2 pods to be ready...
2021-11-01T21:47:32.4828866Z Waiting for *** pods to be ready...
2021-11-01T21:47:32.4829790Z partitioned roll out complete: 3 new pods have been updated...
2021-11-01T21:47:32.4830431Z ***0.0.83.50
2021-11-01T21:47:32.4831313Z namespace/redis-sentinel-streams-test created
2021-11-01T21:47:32.4832446Z secret/redis***
2021-11-01T21:47:32.4833652Z triggerauthentication.keda.sh/keda-redis-stream-triggerauth created
2021-11-01T21:47:32.4835012Z deployment.apps/redis-streams-consumer created
2021-11-01T21:47:32.4836222Z scaledobject.keda.sh/redis-streams-scaledobject created
2021-11-01T21:47:32.4837017Z ***
2021-11-01T21:47:32.4837769Z   ✔ Deployment should have *** replica on start (***53ms)
2021-11-01T21:47:32.4838722Z job.batch/redis-streams-producer created
2021-11-01T21:47:32.4839365Z ***

2021-11-01T21:47:32.4851788Z ***
2021-11-01T21:47:32.4852808Z   ✖ Deployment should scale to 5 with ***00 messages and back to *** Replica count should be 5 within 60 seconds
2021-11-01T21:47:32.4854106Z scaledobject.keda.sh "redis-streams-scaledobject" deleted
2021-11-01T21:47:32.4855575Z triggerauthentication.keda.sh "keda-redis-stream-triggerauth" deleted
2021-11-01T21:47:32.4856770Z secret "redis-password" deleted
2021-11-01T21:47:32.4857749Z deployment.apps "redis-streams-consumer" deleted
2021-11-01T21:47:32.4858791Z job.batch "redis-streams-producer" deleted
2021-11-01T21:47:32.4859866Z namespace "redis-sentinel-streams-test" deleted
2021-11-01T21:47:32.4860948Z release "redis-sentinel-streams" uninstalled
2021-11-01T21:47:32.4862488Z namespace "redis-sentinel-streams" deleted
2021-11-01T21:47:32.4863606Z   ─
2021-11-01T21:47:32.4864101Z
2021-11-01T21:47:32.4864967Z   Deployment should scale to 5 with ***00 messages and back to ***
2021-11-01T21:47:32.4865619Z
2021-11-01T21:47:32.4866747Z   scalers/redis-sentinel-streams.test.ts:79
2021-11-01T21:47:32.4867490Z
2021-11-01T21:47:32.4868782Z    78:   // With messages published, the consumer deployment should start recei…
2021-11-01T21:47:32.4870602Z    79:   t.true(await waitForDeploymentReplicaCount(5, 'redis-streams-consumer'…
2021-11-01T21:47:32.4872762Z    80:   t.true(await waitForDeploymentReplicaCount(***, 'redis-streams-consumer'…
2021-11-01T21:47:32.4873701Z
2021-11-01T21:47:32.4874587Z   Replica count should be 5 within 60 seconds
2021-11-01T21:47:32.4875207Z
2021-11-01T21:47:32.4875811Z   Value is not `true`:
2021-11-01T21:47:32.4876156Z
2021-11-01T21:47:32.4876745Z   false
2021-11-01T21:47:32.4877032Z
2021-11-01T21:47:32.4878338Z   › scalers/redis-sentinel-streams.test.ts:79:3
2021-11-01T21:47:32.4879953Z   › step (scalers/redis-sentinel-streams.test.ts:33:23)
2021-11-01T21:47:32.4881652Z   › Object.next (scalers/redis-sentinel-streams.test.ts:***4:53)
2021-11-01T21:47:32.4883391Z   › fulfilled (scalers/redis-sentinel-streams.test.ts:5:58)
2021-11-01T21:47:32.4884202Z
2021-11-01T21:47:32.4884977Z   ─
2021-11-01T21:47:32.4885469Z
2021-11-01T21:47:32.4885928Z   *** test failed

2021-11-01T21:47:33.3968929Z 202***-***-0***T2***:3***:29.594Z	ERROR	controller.scaledobject	Error getting scalers	{"reconciler group": "keda.sh", "reconciler kind": "ScaledObject", "name": "redis-streams-scaledobject", "namespace": "redis-sentinel-streams-test", "error": "error getting scaler for trigger #0: connection to redis sentinel failed: redis: all sentinels specified in configuration are unreachable"}
2021-11-01T21:47:33.3971631Z github.com/kedacore/keda/v2/controllers/keda.(*ScaledObjectReconciler).createAndDeployNewHPA

@zroubalik going to look into it today :)

Seems like I have been able to reduce the number of problems on Redis tests, so marking them as done (FYI @ahmelsayed). Hopefully it will last 🤞

We can also mark Cassandra as solved :)

Report
E2E tests are unstable, Solace and Cassandra e2e tests are failing the most of time. Then there are frequent issues with Selenium Grid and Redis related tests.
Specified timeouts are probably to low for these tests.
TODO:

[ ]  Solace
[ ]  Cassandra
[ ]  Selenium Grid
[x]  Redis Cluster Streams/Lists
[x]  Redis Sentinel Streams

https://github.com/kedacore/keda/actions?query=workflow%3Anightly-e2e-test

Unmarking Redis, because they are still faling.

Can this issue be closed? I think that now they are reliable

Yeah, let's open a new issue if there are still problems. Great work @JorTurFer !

authors: JorTurFer ahmelsayed jerbob92 nilayasiktoprak zroubalik

repo: kedacore/keda


text:
Kafka scaler sometimes fails with no matching metrics found

Report
I have a scaled object with 4 scalers: one prometheus, one cron and two Kafka on two different topics.
We have a lot of failures inside the events on the corresponding HPA like  unable to fetch metrics from external metrics API: no matching metrics found for s3-kafka-private_aoaa_anomaly_v1
The same error appears in the Keda operator logs (see bellow).
When doing a describe on the corresponding scaled objects at the time of the issue, the metric is listed in the External Metric Names but there is no entry of it in the Health: section.
Describe of the scaled objet:
Name:         vcstream-gen-anomaly
Namespace:    vcstream-dev
Labels:       app.kubernetes.io/managed-by=Helm
              scaledobject.keda.sh/name=vcstream-gen-anomaly
Annotations:  meta.helm.sh/release-name: vcstream-gen-anomaly
              meta.helm.sh/release-namespace: vcstream-dev
API Version:  keda.sh/v1alpha1
Kind:         ScaledObject
Metadata:
  Creation Timestamp:  2022-01-10T15:19:18Z
  Finalizers:
    finalizer.keda.sh
  Generation:  6
    Manager:         keda-adapter
    Operation:       Update
    Time:            2022-02-16T07:41:36Z
  Resource Version:  335673688
  UID:               d24419d0-0360-4ab4-b9dc-a2b1f161da1c
Spec:
  Advanced:
    Restore To Original Replica Count:  true
  Cooldown Period:                      60
  Fallback:
    Failure Threshold:  3
    Replicas:           1
  Max Replica Count:    6
  Min Replica Count:    1
  Scale Target Ref:
    Name:  vcstream-gen-anomaly
  Triggers:
    Metadata:
      Desired Replicas:  1
      End:               59 18 * * *
      Start:             0 8 * * *
      Timezone:          Europe/Brussels
    Type:                cron
    Metadata:
      Metric Name:     process_cpu_usage
      Query:           avg(process_cpu_usage{component="vcstream-gen-anomaly", namespace="vcstream-dev"} * 100) > 5 OR on() vector(0)
      Server Address:  http://prometheus-server.monitoring.svc.cluster.local
      Threshold:       75
    Type:              prometheus
    Authentication Ref:
      Name:  keda-trigger-auth-kafka-credential
    Metadata:
      Bootstrap Servers:    decathlon-aoaa-vcstream-dev-01-peered-aoaa.aivencloud.com:12658
      Consumer Group:       vcstream-gen-anomaly
      Lag Threshold:        100
      Offset Reset Policy:  latest
      Topic:                private_aoaa_anomaly_v1
    Type:                   kafka
    Authentication Ref:
      Name:  keda-trigger-auth-kafka-credential
    Metadata:
      Bootstrap Servers:    decathlon-aoaa-vcstream-dev-01-peered-aoaa.aivencloud.com:12658
      Consumer Group:       vcstream-gen-anomaly
      Lag Threshold:        100
      Offset Reset Policy:  latest
      Topic:                private_aoaa_deadletter_v1
    Type:                   kafka
Status:
  Conditions:
    Message:  ScaledObject is defined correctly and is ready for scaling
    Reason:   ScaledObjectReady
    Status:   True
    Type:     Ready
    Message:  Scaling is performed because triggers are active
    Reason:   ScalerActive
    Status:   True
    Type:     Active
    Message:  No fallbacks are active on this scaled object
    Reason:   NoFallbackFound
    Status:   False
    Type:     Fallback
  External Metric Names:
    s0-cron-Europe-Brussels-08xxx-5918xxx
    s1-prometheus-process_cpu_usage
    s3-kafka-private_aoaa_anomaly_v1
    s3-kafka-private_aoaa_deadletter_v1
  Health:
    s0-cron-europe-brussels-08xxx-5918xxx:
      Number Of Failures:  0
      Status:              Happy
    s1-prometheus-process_cpu_usage:
      Number Of Failures:  0
      Status:              Happy
    s3-kafka-private_aoaa_deadletter_v1:
      Number Of Failures:  0
      Status:              Happy
  Last Active Time:        2022-02-16T09:12:16Z
  Original Replica Count:  1
  Scale Target GVKR:
    Group:            apps
    Kind:             Deployment
    Resource:         deployments
    Version:          v1
  Scale Target Kind:  apps/v1.Deployment
Events:               <none>

Describe of the HPA:
Name:                                                              keda-hpa-vcstream-gen-anomaly
Namespace:                                                         vcstream-dev
Labels:                                                            app.kubernetes.io/managed-by=Helm
                                                                   app.kubernetes.io/name=keda-hpa-vcstream-gen-anomaly
                                                                   app.kubernetes.io/part-of=vcstream-gen-anomaly
                                                                   app.kubernetes.io/version=2.6.0
                                                                   scaledobject.keda.sh/name=vcstream-gen-anomaly
Annotations:                                                       <none>
CreationTimestamp:                                                 Mon, 10 Jan 2022 16:19:18 +0100
Reference:                                                         Deployment/vcstream-gen-anomaly
Metrics:                                                           ( current / target )
  "s0-cron-Europe-Brussels-08xxx-5918xxx" (target average value):  1 / 1
  "s1-prometheus-process_cpu_usage" (target average value):        0 / 75
  "s3-kafka-private_aoaa_anomaly_v1" (target average value):       <unknown> / 100
  "s3-kafka-private_aoaa_deadletter_v1" (target average value):    0 / 100
Min replicas:                                                      1
Max replicas:                                                      6
Deployment pods:                                                   1 current / 1 desired
Conditions:
  Type            Status  Reason                   Message
  ----            ------  ------                   -------
  AbleToScale     True    ReadyForNewScale         recommended size matches current size
  ScalingActive   False   FailedGetExternalMetric  the HPA was unable to compute the replica count: unable to get external metric vcstream-dev/s3-kafka-private_aoaa_anomaly_v1/&LabelSelector{MatchLabels:map[string]string{scaledobject.keda.sh/name: vcstream-gen-anomaly,},MatchExpressions:[]LabelSelectorRequirement{},}: unable to fetch metrics from external metrics API: no matching metrics found for s3-kafka-private_aoaa_anomaly_v1
  ScalingLimited  False   DesiredWithinRange       the desired count is within the acceptable range
Events:
  Type     Reason                   Age                    From                       Message
  ----     ------                   ----                   ----                       -------
  Warning  FailedGetExternalMetric  109s (x7439 over 46h)  horizontal-pod-autoscaler  unable to get external metric vcstream-dev/s3-kafka-private_aoaa_anomaly_v1/&LabelSelector{MatchLabels:map[string]string{scaledobject.keda.sh/name: vcstream-gen-anomaly,},MatchExpressions:[]LabelSelectorRequirement{},}: unable to fetch metrics from external metrics API: no matching metrics found for s3-kafka-private_aoaa_anomaly_v1

Expected Behavior
No failure event on the HPA
Actual Behavior
Failure event on the HPA and the metric is show as <unknown>.
Steps to Reproduce the Problem
No idea how to reproduce it.
Logs from KEDA operator
E0216 09:14:02.481279       1 status.go:71] apiserver received an error that is not an metav1.Status: &errors.errorString{s:"no matching metrics found for s3-kafka-private_aoaa_anomaly_v1"}: no matching metrics found for s3-kafka-private_aoaa_anomaly_v1

KEDA Version
2.6.0
Kubernetes Version
1.19
Platform
Google Cloud
Scaler Details
prometheus, kafka, cron
Anything else?
No response

You have probably hit this issue: https://github.com/kedacore/keda/issues/2592
I recommend you to update to 2.6.1

@zroubalik upgrading it now ;), thanks for the info.
I'll give feedback after upgrade and a few hours to see if the failures still happened.

@zroubalik so after a few hours running with 2.6.1 I confirm that this issue is fixed ;)
I'm closing it now.

In version 2.7.1 it still happening.

@zroubalik, i'm still with this problem also.
my keda version: 2.7.1
I created scaledObjet with kafka consumer.

$ kubectl describe hpa keda-hpa-ccs-relationship-worker-metrics --namespace ccs-dev
...
Conditions:
  Type           Status  Reason                   Message
  ----           ------  ------                   -------
  AbleToScale    True    SucceededGetScale        the HPA controller was able to get the target's current scale
  ScalingActive  False   FailedGetExternalMetric  the HPA was unable to compute the replica count: unable to get external metric ccs-dev/s0-kafka-alias-bank-account-events/&LabelSelector{MatchLabels:map[string]string{scaledobject.keda.sh/name: ccs-relationship-worker-metrics,},MatchExpressions:[]LabelSelectorRequirement{},}: unable to fetch metrics from external metrics API: the server could not find the requested resource (get s0-kafka-alias-bank-account-events.external.metrics.k8s.io)
Events:
  Type     Reason                   Age                   From                       Message
  ----     ------                   ----                  ----                       -------
  Warning  FailedGetExternalMetric  43s (x4078 over 17h)  horizontal-pod-autoscaler  unable to get external metric ccs-dev/s0-kafka-alias-bank-account-events/&LabelSelector{MatchLabels:map[string]string{scaledobject.keda.sh/name: ccs-relationship-worker-metrics,},MatchExpressions:[]LabelSelectorRequirement{},}: unable to fetch metrics from external metrics API: the server could not find the requested resource (get s0-kafka-alias-bank-account-events.external.metrics.k8s.io)

Boa tarde @johnnytardin, voce conseguiu algo?

authors: joaopuccini johnnytardin loicmathieu zroubalik


text:
VideoDataSet with GeneratorVideo save is broken

Description
I wasn't sure if I should put this issue here or in the Kedro core repo since the VideoDataSet has been broken after a change in Kedro core.
Shortly, the video dataset has multiple backends that can be saved. One of them is the GeneratorVideo which is an Iterable.
In commit fcf3ab4a9 "Enable the usage of generator functions in nodes (#2161)" by @idanov the runner functionality was changed to handle generator datasets.
Snippet from _run_node_sequential in kedro/runner/runner.py:
    items: Iterable = outputs.items()
    # if all outputs are iterators, then the node is a generator node
    if all(isinstance(d, Iterator) for d in outputs.values()):
        # Python dictionaries are ordered so we are sure
        # the keys and the chunk streams are in the same order
        # [a, b, c]
        keys = list(outputs.keys())
        # [Iterator[chunk_a], Iterator[chunk_b], Iterator[chunk_c]]
        streams = list(outputs.values())
        # zip an endless cycle of the keys
        # with an interleaved iterator of the streams
        # [(a, chunk_a), (b, chunk_b), ...] until all outputs complete
        items = zip(it.cycle(keys), interleave(*streams))

    for name, data in items:
        hook_manager.hook.before_dataset_saved(dataset_name=name, data=data, node=node)
        catalog.save(name, data)
        hook_manager.hook.after_dataset_saved(dataset_name=name, data=data, node=node)
    return node

Context
I have not had time yet to dive into the code and see what is actually happening, or how we should treat it in these situations. The effect now is that the runner will yield the first frame from the video and try to save that frame to the Video Dataset which is not possible.
The quick and dirty way to fix it would be to remove the __iter__ method from the GeneratorVideo class and implement some special logic in the VideoDataSet class to iterate it correctly. This would however not be very nice from a user perspective since iter(video) would then result in an indexed-iteration of the generator.
Steps to Reproduce

Create a GeneratorVideo
Create a VideoDataSet
Call save on the video dataset with the generator video

Current workaround:
Note the comment "if all outputs are iterators, then the node is a generator node" - the issue only happens when all outputs from the node is Iterable, therefore we can create a dummy output to the node (e.g. a MemoryDataset) and save some garbage value ( e.g. None) to it.
def my_node(input_video):
    def my_generator():
        ...
    return GeneratorVideo(my_generator(), ...)

node = node(
    my_node,
    inputs="my_video",
    outputs=[
        "my_output_ds",
        "dummy"
    ],
    name="Create video dataset",
)

Didn't have time to check this now, just quick question is this covered in the unit tests?

@noklam Probably not, and the question is where it should be covered. The video dataset works as expected with the framework design as it was when I implemented the dataset. The commit linked above changed the behaviour of Kedro, so sure, there could have been a unit test of the runner that verified that Iterable datasets are possible to save, but it is a very niche thing to test.
The change is however already in and there has been multiple releases since then. Since the change was user-facing I suspect it will not be changed. Therefore I guess the only solution to this is to update the dataset to work with the new behaviour of the runner.
I also think that the new changes to the runner looks very interesting, so it might be something we can make use of to make the video dataset even better.

If anyone comes across this and would like to open a PR, please go ahead 🙂

authors: daniel-falk merelcht noklam

repo: kedro-org/kedro-plugins


text:
The dapp allows you to use someone else's TDT ID for redemption

During redemption, you can use any previously unused TDT ID, not just the owner TDT ID. It seems to me that this is not correct, or I did not fully understand the essence of TDT)

This is only true for TDTs that have been used to mint TBTC. These TDTs no longer belong to an individual owner; instead they belong to the tBTC system, and may be redeemed by anyone. See the Minting section of the spec for a more detailed technical explanation.
Closing this issue since it's working as expected, but let us know if there are details that would merit reopening!

Ok, thanks for the explanation!

authors: Shadowfiend Tuzemunez

repo: keep-network/tbtc-dapp


text:
[feat] Contract Bindings

Generate Contract bindings with Cainome.
References
https://github.com/cartridge-gg/cainome

i'd like to work on this

i'd like to work on this

Awesome! Thank you for considering contributing. If you have any question let us know.

https://github.com/cartridge-gg/cainome

hi @glihm could you perhaps provide more resources/references, for more insight as to how you what this issue handled? technical insight from you would go a long way as well. Thanks

Hey @Akinbola247 for sure, thanks for considering contributing.
The idea of cainome is that it is able to generate the rust bindings from a contract ABI.
So, this would be the worflow:

Create a rust project (library) inside the repo (can be at the root of the repo for now).
In this library, you will want to use a generated Sierra file to parse the ABI using abigen! macro from cainome: example here.
This can be a first step. And then we will see how to structure the rust code to be imported as a library by other project to easily interact with the piltover contracts.

Does it make more sense? If it's too blurry, I'll attempt to create a first version of the rust bindings (or @drspacemn or @b-j-roberts), and then you can take over.

okay! i'll give this a shot. i'll revert if i have anymore questions, perhaps we can maintain TG as a means of communication.

@Akinbola247 are you still working on this one or we can re-assign?

Hey there, can I be assigned for this task. Would love to take it up!

@glihm yes I am. Although, I don’t mind working together on it with @KeneePatel .

Thanks @Akinbola247. Would be awesome to collab. @glihm feel free to assign me as well.

Reference for this ticket:
https://github.com/keep-starknet-strange/blobstream-starknet/pull/132

Hey @glihm, which Sierra file are we supposed to parse using abigen! macro from cainome in our case?

Hey @glihm, which Sierra file are we supposed to parse using abigen! macro from cainome in our case?

Hum, when you mean which, you mean which "contract" right?
In out case here it should be the app chain contract, that should contain all the exposes methods in the ABI that we want to call.

Do we have a TG group for means of communicating?

We do, join us here

Thanks sire. Just joined it.

Hello ser @drspacemn,
Is this issue complete or should there be more development needed on this. If yes, I would be happy to contribute towards it.

Completed by #28.

authors: Akinbola247 KeneePatel drspacemn glihm

repo: keep-starknet-strange/piltover


text:
[feat] Utreexo: removing item from the accumulator

[x] resolves #209
[x] follows contribution guide
[x] code change includes tests

@m-kus  first draft.
Need to add more tests to it, not 100% sure of my implementation.
Works well for a simple test where i remove one leave to a 2 leaves - 1 root forest merkle tree

can you confirm that once an UtreexoState has contained n roots, then even if we remove all leaves, we should still have n roots, all set to Option::None ?

Also, can you confirm that the deletion algorithm doesnt require to use leaf_index binary representation in any step? just to make sure

can you confirm that desired behaviour is that once an UtreexoState has contained n roots, then even if we remove all leaves, we should still have n roots, all set to Option::None ?
I think there is no choice actually. Because we need to ''copy paste'' all the remaining roots that are not concerned by the removal, we need to append residual roots to the utreexostate. Hence, in case where we remove a lot of leaves, we'll have multiple Option::None appended. I dont see any way (that is not costly and doesnt require to loop over all the remaining roots) to check whether we should append or not remaining roots to stick to only one Option::None at the end of our array of roots. not sure if i'm totally clear

There always has to be at least one root (Option::None if the forest is empty).
It's ok to have multiple None roots, the total number will remain pretty small (e.g. in ZeroSync they have a fixed array)

Also, can you confirm that the deletion algorithm doesnt require to use leaf_index binary representation in any step? just to make sure

It requires leaf index (which is part of the proof) to determine the position of the sibling node from the proof when you compute parent hash.

@m-kus  ready for final review

repo: keep-starknet-strange/raito


text:
Crash with unity 5.5

Description
Apparently, there are some crash with android since the update to unity 5.5
https://forum.unity3d.com/threads/camera-to-render-texture-crash.442663/

It seems that
Webcam.Stop();

is the origin of the crash when the LoadScene is called.

A proper issue was open by unity:

https://issuetracker.unity3d.com/issues/android-crash-when-reloading-scene-which-uses-wecamtexture

Reproducible: 5.5.0b1, 5.5.0f3, 5.6.0a5
Not reproducible: 5.4.3p2

Got a notification from unity, they fixed the issue in the last patch version 5.5.0p4

(855603, 859268) - Android: Fixed a crash when reloading or resuming scene which uses WebCamTexture.

So this fix should arrive soon in the next 5.5.1 and be backported in 5.4.x and 5.3.x later

authors: dyoxyne kefniark

repo: kefniark/UnityBarcodeScanner

license: WTFPL


text:
Effect jumping between Skinner sources

Hey @keijiro, hoping you can shed some light on this issue. The rendered effect seems to be jumping between Skinner sources. Here's a simple project that demonstrates the issue:
SkinnerBugDemo.zip

Thanks for reporting the issue.
I found there is a regression issue in Unity 2017.1.0. Fortunately I found a simple workaround for the problem. Please try the latest version.
https://github.com/keijiro/Skinner/releases

Thanks @keijiro! Tested and working.

authors: dash-x keijiro

repo: keijiro/Skinner


text:
Waveglow vocoder

Hey there, I'm currently working on Polish model based on keithito implementation.
I've succesfully frozen graph for inference. I'm grabbing mel's from BiasAdd:0 and then I've implemented Griffin-Lim in C++ ( "Industrial purposes") however it's still too slow. It is posible to use other network as a vocoder now ? I mean, makes an BiasAdd:0 output as an input to waveglow or other vocoder. Maybe you have some other ideas about faster vocoders, thanks .

waveglow should be super slow.
Howewer it's interesting which existing vocoders are compatible with this implementation.

@Clouxie Try to use lpcnet c++ as vocoder .its quite fast .There are discussion and project using tacotron2 for generating mels( 20 coefficient ) and then lpcnet as vocoder for realtime solution.

authors: Clouxie alokprasad mrgloom

repo: keithito/tacotron


text:
Manga TV

Source name
Manga TV
Source link
https://www.mangatv.net/
Source language
Spanish
Other details
18+/NSFW = yes
Acknowledgements

[X] I have checked that the extension does not already exist by searching the extension listing and verified it does not appear there.
[X] I have searched the existing issues and this is a new ticket, NOT a duplicate or related to another open or closed issue.
[X] I have written a meaningful title with the source name.
[X] I will fill out all of the requested information in this form.

Site mimics the ManagaThemesia theme somewhat, not entirely sure if it's actually using it.

authors: ashliepolanco vetleledaal

repo: keiyoushi/extensions-source


text:
Remove LuraToon

Source name
Lura toon 1.4.53
Source language
Português
Source link
https://lura-toons.com/
Other details
Thanks to the damned "Empresário", Luraton stopped being free, you can only read it now by paying, I don't know the extension allows you to read paid works (although it's not even theirs).

To read from now on, you have to pay 7 reais (brl) a month
Acknowledgements

[X] I have updated all installed extensions.
[X] I have opened WebView and checked that the source website is down.
[X] I have searched the existing issues and this is a new ticket, NOT a duplicate or related to another open or closed issue.
[X] I have written a meaningful title with the source name.
[X] I will fill out all of the requested information in this form.

I don't think it's necessary to remove the extension. I believe it would be better to update it. This way, whoever is using Mihon would only need to log in to the website through the extension and use Mihon normally. I think now that the website is paid, there is no problem in using Mihon, as there are no ads on both the website and the app.

There is no reason to end the source.  As already said, just update the source to a login system and log in to the website in the same way as DemonSect.  If you have a login and password, great, if you don't, look for other means!

Even with the login system (whose create and say login), I always see chapter shows that there is no chapter.
When I go to web views and click on the chapter, it returns to the site's home menu.

🙄🫤😑🤐😶.

When I go to web views and click on the chapter, it returns to the site's home menu.

If it doesn't work on the site itself, don't expect it to work in the extension as well. Maybe users will require a special account

When I go to web views and click on the chapter, it returns to the site's home menu.

If it doesn't work on the site itself, don't expect it to work in the extension as well. Maybe users will require a special account

Yes, special account and paying 7 reais (brl) per month, but I'm already migrating and then I'll delete the extension because of this luratoon mess, almost every scan in the world will take all their works.
I'll leave the issues open for you to decide what to do.
Because I'm going to report all their works to the DMCA (it may take a while, but one day it will come).

since it was not removed, users with issues who have site's premium account can open new issue

authors: AwkwardPeak7 EvaldoCeBr bapeey choppeh gamespvp93 nomaxsnx


text:
Allmanga: manga pages url change

Source information
Allmanga 1.4.7
Source language
English
Steps to reproduce

Open Chapters or the manga page
Pages dont load
Open webview (error pages shows)

Expected behavior
See the manga pages load
Actual behavior
Pages dont load
Also there's a error page on webview
Mihon/Tachiyomi version
0.17.1
Android version
Android 10
Other details
No response
Acknowledgements

[X] I have searched the existing issues and this is a new ticket, NOT a duplicate or related to another open or closed issue.
[X] I have written a short but informative title.
[X] I have updated the app to version 0.15.3.
[X] I have updated all installed extensions.
[X] I have tried the troubleshooting guide.
[X] If this is an issue with the app itself, I should be opening an issue in the app repository.
[X] I will fill out all of the requested information in this form.

Add a :+1: reaction to issues you find important.

Might be lost in translation, but I'm only seeing issues with WebView / the manga URL. The chapter images work as expected.

Might be lost in translation, but I'm only seeing issues with WebView / the manga URL. The chapter images work as expected.

Now yes you can see the chapters, but Previously You couldn't see them is wierd.


text:
bootstrapping etcd cluster

In all the controller machines, downloaded the etcd  binaries, configured the etcd server and started the etcd server.  It seem to be successful.
When i try to list
xxxxxx@controller-0:~$ sudo ETCDCTL_API=3 etcdctl member list \
>   --endpoints=https://127.0.0.1:2379 \
>   --cacert=/etc/etcd/ca.pem \
>   --cert=/etc/etcd/kubernetes.pem \
>   --key=/etc/etcd/kubernetes-key.pem
Error: context deadline exceeded

getting an error context deadline exceeded.
I am not sure of, am i missing something or doing wrong here ?

Did a quick check on cluster-health getting error as below
etcdctl cluster-health
cluster may be unhealthy: failed to list members
Error:  client: etcd cluster is unavailable or misconfigured; error #0: client: endpoint http://127.0.0.1:2379 exceeded header timeout
; error #1: dial tcp 127.0.0.1:4001: getsockopt: connection refused

error #0: client: endpoint http://127.0.0.1:2379 exceeded header timeout
error #1: dial tcp 127.0.0.1:4001: getsockopt: connection refused

It only works when you have at least 2 nodes configured.

min 1 or 3 etcd required and please check ps -ef | grep etcd, wether etcd running or not, and Try to check logs  journalctl -xe

I can confirm this behavior too. I followed the instructions here, and I clearly have all 3 hosts running etcd.
I even see this:
etcdctl cluster-health
member 8e9e05c52164694d is healthy: got healthy result from http://localhost:2379

But when I try the following:
sudo ETCDCTL_API=3 etcdctl member list \

--endpoints=https://127.0.0.1:2379
--cacert=/etc/etcd/ca.pem
--cert=/etc/etcd/kubernetes.pem
--key=/etc/etcd/kubernetes-key.pem
Error: context deadline exceeded

Adding a firewall rule that allows TCP ports 2379 and 2380 to all instances in the Kubernetes cluster

also happened to me.
But, following @MisguidedEmails 's suggest, it worked.
This is a sample code I did for adding the firewall
gcloud compute firewall-rules create kubernetes-the-hard-way-allow-internal-etcd --allow tcp:2379,tcp:2380 --network kubernetes-the-hard-way --source-ranges 10.240.0.0/24,10.200.0.0/16

Looks like you may have missed the early infrastructure  section where these ports are opened cluster wide.

It happened to me. but  @MisguidedEmails suggestion doesn't work for me. For me, etcd on controller-0, controller-1 works just fine. but etcd on controller-2 returns 'getting an error context deadline exceeded.' when I try
`xxxxxx@controller-2:~$ sudo ETCDCTL_API=3 etcdctl member list \

--endpoints=https://127.0.0.1:2379
--cacert=/etc/etcd/ca.pem
--cert=/etc/etcd/kubernetes.pem
--key=/etc/etcd/kubernetes-key.pem
Error: context deadline exceeded
`
I am sure all ports are open cluster wide as instructed.

@jskwon73 on your controller, run journalctl -u etcd.service to see the logs. I had the same issue due to INTERNAL_IP and ETCD_NAME not being set. I had to do a manual export and recreate the service config files then all controllers started to work.
Make sure your /etc/systemd/system/etcd.service have the variables set correctly.

Thanks! @hoadinhmai Your advise really helped. I checked the log and found it has some issue with a certificate. And I went through all steps again and found I did a silly mistake when I generated api server certificate. I typed wrong IP address of controller-2. That's why I had the problem on the controller-2 only. Thank you!

Getting this error while configuring etcd servers:
ubuntu@controller-1:~$ {

sudo mkdir -p /etc/etcd /var/lib/etcd
sudo chmod 700 /var/lib/etcd
sudo cp ca.pem kubernetes-key.pem kubernetes.pem /etc/etcd/
}
cp: cannot stat 'ca.pem': No such file or directory
cp: cannot stat 'kubernetes-key.pem': No such file or directory
cp: cannot stat 'kubernetes.pem': No such file or directory

Hi @santhoshreddykeesara,
You are receiving that message because the files you are trying to copy do not exist in your current location ($HOME directory of your controller)!
List the current files in your location with ls -l to validate if they exist there or search for where the kubernetes-key.pem file exists with:
sudo find / -name "'kubernetes-key.pem"
or
sudo find / -name "'kubernetes.pem"

Hi @santhoshreddykeesara,
You are receiving that message because the files you are trying to copy do not exist in your current location ($HOME directory of your controller)!
List the current files in your location with ls -l to validate if they exist there or search for where the kubernetes-key.pem file exists with:
sudo find /tmp -type f -name "kubernetes-key.pem"
or
sudo find /tmp -type f -name "kubernetes.pem"

Hi @santhoshreddykeesara ,
You are receiving that message because the files you are trying to copy do not exist in your current location ($HOME directory of your controller)!
List the current files in your location with ls -l to validate if they exist there or search for where the kubernetes-key.pem file exists with:
sudo find / -type f -name "kubernetes-key.pem"
or
sudo find / -type f -name "kubernetes.pem"
Or use any other location where you consider your files exist!

repo: kelseyhightower/kubernetes-the-hard-way


text:
Remove redundant rbac bootstrapping

Issue 509 - remove redundant RBAC bootstrapping

need to test first


text:
Nocode found in the fossil record

I was stunned to find numerous examples of nocode in the fossil record.
It appears that many slate quarries have found slate actually containing nocode.
Could this be an example of prior art from past eons ?

Nothing happened before the Internet. You are seeing random fluctuations.

repo: kelseyhightower/nocode


text:
Add Drag and Drop Support

I was just recently working on a svelte array displayed with ul/li that needed sorting.
I came across https://github.com/isaacHagoel/svelte-dnd-action which returned a "missing el" error for some code whose header mentioned that it came from stack overflow (they need to integrate it a bit more, I was unable to reproduce the error reliably enough to file a bug report in the time I had - but I will try harder).
So wrote my own sortable code, which is 4 lines of code, and does not need a library, I leave it here as reference for Drag and Drop support that I would like to see in your program.

    List

        {#each list as item, index (item.id)}

event.dataTransfer.setData("text/plain", index)}
          on:dragover={(event)=>(parseInt(event.dataTransfer.getData("text/plain"))==index)?null:event.preventDefault()}
          on:drop={(event)=>{event.preventDefault(); list.splice(index, 0, list.splice(parseInt(event.dataTransfer.getData("text/plain")), 1)[0]); list=list;}}
          class="list-group-item text-bg-dark" on:click={()=>{selected=item.id; console.log(selected)}}>
          {item.title}

        {/each}

I truly am inspired by the code quality of this project. It is so purrrfect. And I am deeply impressed, that to integrate these four lines, you don't have to do anything. I am learning form you.

Maybe try stackoverflow?
This is for NoCode, not svelte.
But, I can think why you want to add drag and drop in this.
My suggestion is to simplify that four line of code into this:

authors: catpea rizrmd


text:
Faith

Commit to resolve conflicts

Resolved conflicts

repo: kelvinmburu/timesy


text:
Fix "was reset" key

Right now it seems like a key you can use to access whether a timer has ever been reset, but what it actually does is a latching run around timer_check for a repeating timer (since timers don't repeat using timer_check). Investigate whether we can simplify this behavior and if not, rename the key to something better.

Also, it happens on timer_restart which is not necessary - it only needs to fire on repeating timers so we have at least one frame to do a check. When it fires on timer_restart, it shouldn't fire off because someone may want to immediately restart and pause a timer for later reuse.

renamed to RESTARTED_THIS_FRAME and only fires on repeating timers now

repo: kemonologic/fuwafuwa


text:
modintの整数/modintがバグってそう

import cplib/modint/modint
import atcoder/modint

type mint = modint998244353_montgomery
type mint2 = modint998244353

echo 1/mint(5)
echo 1/mint2(5)

5
598946612

これやばいな、なんで今まで発覚してなかったんだ

authors: kemuniku seekworser

repo: kemuniku/cplib


text:
Ensure nouislider is ^7 until addon is reworked.

Fixes #8.

This solves the bugs for those on ^0.4 and the fix to support v8 of noUiSlider is in #10

repo: kennethkalmer/ember-cli-nouislider


text:
Correct boolean return value of prompt.yn

Close #145
See also: #150

ping

ping

repo: kennethreitz/clint

license: isc


text:
Release v1.0

Hey @kenneth-reitz @timofurrer
Thinking of release v.1.0 here, it will fix some bugs and completely release the asyncIO support. Also, I'm thinking of automating this process with a CI for releases and running tests on PRs.

This was done :)

repo: kennethreitz/requests-html


text:
behavior of encoding

Hello,
I am having a terrible time figuring out what requests is doing here.
 print(r.url) #debug
 print(r.encoding)
 print(r.text)
 print(r.headers)

debugging commands in console produce:
payload in function is {"key1": "foo", "key2": "bar"}
http://0.0.0.0:5006/buy?%7B%22key1%22:%20%22foo%22,%20%22key2%22:%20%22bar%22%7D
ISO-8859-1```

The URL looks wrong to me, is it somehow being created incorrectly?

Hey @fredzannarbor, are you sure that your payload variable is of type dict and not str. The results you're seeing seem to be consistent with url encoding a string rather than passing a dictionary for iteration.

The URL is right; its urlencoding the string payload you gave it. You cannot just send arbitrary data in a URL: as it is structured, certain bytes have semantic meaning. If you don't want that meaning, you need to encode those bytes using what is called urlencoding. That's what we have done here.

authors: Lukasa fredzannarbor nateprewitt

repo: kennethreitz/requests


text:
How to avoid SSRF when you use requests to parse untrusted URLs?

For an example I have a Flask app, it gets 'url' parameter from GET request. Then it do something like this:
requests.get(params['url']).text

So how to avoid localhost requests? Should I make a new network interface, which can access only external network and then send requests? I tried to search some answers for that and I found only https://github.com/JordanMilne/Advocate/ but the autor says that we shouldn't use it in production. So how to properly secure from SSRF in case like this? Can requests do requests through specified virtual network interfaces?

I'd say this isn't within the realm of requests responsibility. This is an input sanitization issue not an HTTP issue. My recommendation would be parsing the URL and maintaining an "allow list" of hosts and URL constructions that are acceptable to make requests to (scheme, w/o userinfo, etc).

I have found a better way: https://stackoverflow.com/questions/691045/how-do-you-determine-if-an-ip-address-is-private-in-python you can just check if IP is blacklisted by this or not. Idk how secure it is but I think it's better than nothing.

>>> ip = '169.254.169.254'
>>> ipaddress.ip_address(ip).is_global
False
>>>

Lol, it's just a default python3 module and it can secure you even against aws metadata ip!! How can I make a module which will "proxy" the default requests module and add url ssrf protection?

authors: marataziat sethmlarson


text:
Ambassador

Name: kobayashi
Background: 5 years <= python, 2 years <= go
interests: craft a tool

Hi @kobayashi
You've been invited to kennethreitz.org! You'll be receiving an email shortly. You can also visit https://github.com/kennethreitz to accept the invitation.

authors: kobayashi sadikkuzu

repo: kennethreitz/team


text:
onChange with handleSelect not working

I have to store placeid and address when user clicks on suggestion item. For this I have code like this but it is not calling this.handleSelect callback.
         const inputProps = {       value: this.state.address,       onChange: this.onChange,       placeholder: 'Location or postcode'     };  <PlacesAutocomplete                 inputProps={inputProps}                 onSelect={this.handleSelect}                 autocompleteItem={AutocompleteItem}                 debounce={500}                 googleLogo={false}                 options={options}                 styles={defaultStyles}                 clearItemsOnError={true}               />
I have also tried this : https://github.com/kenny-hibino/react-places-autocomplete/issues/23
but it says inputProps is mandatory.
What's wrong in this code?

@kenny-hibino Any updates here?

Hey had the same issue when passed my onSelect callback inside  inputProps.
When I changed my code to this:
<PlacesAutocomplete inputProps={inputProps} onSelect={this.handleSelect} />
It works fine.
Somehow the module doesn't recognize onSelect as a function when it is passed through inputProps.

repo: kenny-hibino/react-places-autocomplete


text:
Load model for Transfer Learning

Hello! First of all, thank you very much for sharing your code! Congrats on your project! :)
I'm new in PyTorch and I was wondering if it is possible to load the pre-trained models (for example resnext-101) using model = torch.load(PATH), for example? I wanted to use their conv layers for this kaggle contest https://www.kaggle.com/c/youtube8m-2019. If you have any hint on where to start I would really appreciate :)
Thank you and congratulations again!

@WittmannF : I am trying to do the same? Did you figure it out? Thanks!

authors: WittmannF priyanka-chaudhary


text:
Use proxyquire to mock fs object ...

instead of using mock-fs.
This should fix the issue shown in #6

Huh... I wonder why this didn't kick off a travis build... I'll pull it down locally and give it a look. Thanks!

I think travis only kicks in on PRs to the master branch, I compared against and created the PR towards your ava-bug branch.

Ah! That makes sense. Do you mind making this same PR to master? I haven't had a chance to pull it down yet. Thanks :+1:

See #8.
Strange, this pr got its checks through travis now...

repo: kentcdodds/eslint-find-new-rules


text:
Check credentials beyond the schema

Issue: KNTK-333

This change does not help with plan_id case and is a dead end. Closing.


text:
provided example code doesn't seem to be useful, actually

After copying the example html from http://kenwheeler.github.io/slick/#getting-started and fixing the asset paths I get nothing really useful on page. Also, there's no obvious error on page.

  <title>My Now Amazing Webpage</title>
  <link rel="stylesheet" type="text/css" href="http://kenwheeler.github.io/slick/slick/slick.css"/>
  <link rel="stylesheet" type="text/css" href="http://kenwheeler.github.io/slick/slick/slick-theme.css"/>

your content

your content

your content

Result page is attached.

Actually, you should pop open your dev tools.

authors: kenwheeler spaghetticode

repo: kenwheeler/slick


text:
Can't handle multiple sliders

short description of the bug / issue, provide more detail below.
The issue happens when I try to use slick more than once on my client's website. It works for the first slider but the second slider is broken. Not sure what is causing this and atm don't have time to elaborate much. The second slider has a significantly wrong width of 52,494 px and exponentially increases. Any help is much appreciated.
===================================================================

Steps to reproduce the problem

Have a slider initialized on slider1
Have slider initialized on slider2
Slider2 is broken and slider1 works

More Details

Which browsers/versions does it happen on? Firefox, Chrome, IE
Which jQuery/Slick version are you using? 1.8.0
Did this work before?  No

Can you post a link and your code? I'm nearly positive I've had multiple sliders going on 1 page with Slick.

I will post the code when I return home from work today. Thanks

I have many cases of multiple sliders and never encountered any problems. I believe the demo page is another example of having multiple sliders on the same page. I suggest having two identical sliders to ensure that the issue isn't caused by something else.

I have tens of sliders on one page and Slick works without any problem.

I'm having the same problem. But the problem is because I'm using inside Bootstrap Tabs: each tab has one slick slider... trying to fix it out here...

Apologies for leaving this post behind. I had to use a different slider to finish the project. I was never able to figure out the problem because it became too costly time-wise. I tried using the same slider class on both instances but the issue persisted.

Visibility problem when switching tabs in bootstrap 4
Solution
.tab-content>.tab-pane{ display: block; height: 0px; overflow: hidden; }
.tab-content>.active{ height: auto;}

Thanks @sinjuangajan this is the only solution that works.

authors: DrewDouglass ajCastiglione bassm fnonaka kevinfarrugia mikemix sinjuangajan


text:
docs: mention Prometheus in intro

@agardnerIT commented:
Nitpicking but: Datadog, Dynatrace, Lightstep, Honeycomb, Splunk

missing Prometheus
it should be alphabetical OR we are subtly suggesting that datadog is better than DT.
(My opinion) but we shouldn’t give free promotion. If the vendors want their name listed here, they should write a provider. By giving this list, we’re putting Honeycomb on the same footing at DT.

This PR:

Adds Prometheus to the list of data providers and arranges them in the order they were implemented for KLT
Replaced the names of other data providers with "and others"
Tweaked the prose a bit for better flow

The build error is about the link to the HPA docs.  The link works fine -- I think markdownlint has a bit of trouble to xrefs to subsections of a page

repo: keptn/lifecycle-toolkit


text:
Introductions and Guide lead to 404

Describe the problem
The Introduction to Keras for engineers, Introduction to Keras for researchers, and Developer Guide links in the README all lead to a 404 page.

Seems like this is fixed now.

repo: keras-team/keras


text:
DOC: explain the meaning of model.fit() history tracking in a distributed scenario

The tensorflow team requested that I post this issue over here as well.
URL(s) with the issue:
Perhaps most closely related to some of these docs pages:

https://www.tensorflow.org/api_docs/python/tf/keras/Model#fit
https://www.tensorflow.org/tutorials/distribute/multi_worker_with_keras#overview

Description of issue (what needs changing):
There are fairly substantial docs about distributed training with tensorflow, including docs related to the MultiWorkerMirroredStrategy. But, as far as I can tell, reading those docs still doesn't prepare the end user for some of the perils of distributed training. One thing I'd like to see described/explained by an expert, is what it means to track the history result of model.fit() from many different distributed workers.
For example, what does it mean that the learning curves are different between different workers? Should they be? What about accuracy results exceeding 100 % like in the two-worker example results below? Should we even be looking at these individually?
Node 0 model.fit() results:

Node 1 model.fit() results:

Should the results be condensed/reduced somehow? For that matter, is there any troubleshooting documentation on what an accuracy greater than 100 % means?
Correct links
Not related to links.
Parameters defined
Not related to parameters.
Returns defined
Perhaps for model.fit() there could be a side-note of some sort on how to interpret history.history in distributed scenarios, and what kinds of fluctuations between workers are normal vs. suspicious?
Raises listed and defined
No exception handling issues reported here.
Usage example
I don't think I've actually seen a good usage example that shows the distributed history.history tracking plots differ between workers?
Request visuals, if applicable
I could probably provide some sample loss/accuracy plots for distributed cases if that would help.
Submit a pull request?
Are you planning to also submit a pull request to fix the issue?
If you can offer some guidance on how this is supposed to work, I think that would be useful enough for me to justify helping improve the docs as well.
To make it a bit clearer why this can be confusing, the exact same code on a single MPI rank/node produces what looks to me like fairly sensible ML progress curves--sure the overfitting is extreme because it is one GPU for a few minutes and a microscopic sub-sample of imagenet2012, but not nearly as wild as the multi-node/multi-GPU case.

I also almost wonder if an accuracy > 100 % warrants a warning message with suggestions for improvements/likely fixes, but maybe there are custom/debugging ML scenarios where that is valid.

Hi @tylerjereddy, Are you using the sharded dataset?

I think so yeah, and I tried a mixture of automatic and manual sharding options.
In the end, I decided to switch to Horovod to coordinate the workflow over multiple nodes/GPUs, and this seemed to work much more smoothly, fwiw.

Loss and Accuracy will depend on the data and model.

Model is replicated across the workers in MultiWorkerMirroredStrategy -> model is same for each worker.
With the sharded dataset - > data on each worker is different  -> This might explain the difference you observe in Loss and Accuracy.

Hello, Thank you for reporting an issue.
We're currently in the process of migrating the new Keras 3 code base from keras-team/keras-core to keras-team/keras.
Consequently, This issue may not be relevant to the Keras 3 code base . After the migration is successfully completed, feel free to reopen this Issue at keras-team/keras if you believe it remains relevant to the Keras 3 code base. If instead this Issue is a bug or security issue in legacy tf.keras, you can instead report a new issue at keras-team/tf-keras, which hosts the TensorFlow-only, legacy version of Keras.
To know more about Keras 3, please read https://keras.io/keras_core/announcement/

authors: SuryanarayanaY nithish08 tylerjereddy


text:
Unexpected Losses with Sample Weights

When using sample_weight, and the default reduction sum_over_batch_size, the computed losses are technically correct (they are the sum divided by the batch size), but they are not what someone would want them to be. They are computed by summing the loss * sample_weight and dividing by the number of [mask applied] items in the tensor. That is, they are not computed by dividing by the sum of the sample weights.
For example,
keras.losses.MeanAbsoluteError()(
    y_true=np.array([[1.0], [2.0]]),
    y_pred=np.array([[2.0], [3.0]]),
    sample_weight=np.array([[0.0], [1.0]])
    ).numpy()

returns 0.5 not 1.0. (The denominator of the calculation is 2.0 because there are two samples where the loss is applied, despite one of them having a sample weight of 0.0.)
Notably, the metric version
keras.metrics.MeanAbsoluteError()(
    y_true=np.array([[1.0], [2.0]]),
    y_pred=np.array([[2.0], [3.0]]),
    sample_weight=np.array([[0.0], [1.0]])
    ).numpy()

returns 1.0 as one would expect because it divides by the sum of the sample weights.
The metrics version uses keras.src.utils.metrics_utils.Reduction() of weighted_mean by default (not sum_over_batch_size). However, the losses keras.losses.Reduction() has no such equivalent. This means the loss computes a different value from the associated metric during training.
This is a long-standing issue, but I verified this in both Keras 2.15.0 (TensorFlow 2.15.0) and 3.3.3 (TensorFlow 2.16.1).
https://colab.research.google.com/drive/1TRBeOE79kfxPwz1-C60N3IjXeLSUbgST?usp=sharing
Should someone either change the default behavior to be the weighted mean (divide by sum of the sample weights) or add another loss reduction option that enables this? I think this is a significant issue that affects neural network training.
Note that when a mask is applied, the function keras.utils.losses_utils.apply_valid_mask is used to exclude some items from the loss calculation by setting their sample weights to 0.0 and adjusting the denominator to only count the number of items in the tensor that pass through the mask. Therefore, in the special case of all sample weights being 1.0 but some getting masked out, the denominator is adjusted to get the effect of dividing by the sum of the sample weights rather than the "batch size". Thus, in this one special (but likely common) case, the output is what one would expect. It just doesn't work out that way when some of the included sample weights are different from 1.0.

Hi @seandaug ,
I have replicated the reported behaviour and attached gist. Will dig more and comeback. Thanks!

I have come across a similar problem. Using keras 3. I tested it with jax and torch backend.
The sample_weight is not giving weight to the error on a given position, but already to the final reduced error.
Example with MeanSquaredError:
In [11]: MeanSquaredError(reduction="sum")(np.array([1,2,3]), np.array([1,1,1]),  sample_weight=np.array([1,1,1]))
Out[11]: Array(5., dtype=float32)

In [12]: MeanSquaredError(reduction="sum")(np.array([1,2,3]), np.array([1,1,1]),  sample_weight=np.array([1,0,0]))
Out[12]: Array(1.6666667, dtype=float32)

In [13]: MeanSquaredError(reduction="sum")(np.array([1,2,3]), np.array([1,1,1]),  sample_weight=np.array([0,1,0]))
Out[13]: Array(1.6666667, dtype=float32)

In [14]: MeanSquaredError(reduction="sum")(np.array([1,2,3]), np.array([1,1,1]),  sample_weight=np.array([0,0,1]))
Out[14]: Array(1.6666667, dtype=float32)

In [17]: MeanSquaredError(reduction="sum")(np.array([1,2,3]), np.array([1,1,1]),  sample_weight=np.array([1,0,1]))
Out[17]: Array(3.3333335, dtype=float32)

In [15]: MeanSquaredError(reduction=None)(np.array([1,2,3]), np.array([1,1,1]),  sample_weight=np.array([0,0,1]))
Out[15]: Array([0.       , 0.       , 1.6666667], dtype=float32)

In [16]: MeanSquaredError(reduction=None)(np.array([1,2,3]), np.array([1,1,1]),  sample_weight=np.array([1,1,1]))
Out[16]: Array([1.6666667, 1.6666667, 1.6666667], dtype=float32)

In this case, from what I gather, the expected behavior should be to have the answer be the squared errors: [0, 1, 4] and the sample weights would multiply by this result, and then after apply the reduction (mean).

Thanks. It seems like the following now makes the same calculation as the metric case using tf-nightly:
keras.losses.MeanAbsoluteError(reduction='mean_with_sample_weight')(
    y_true=np.array([[1.0], [2.0]]),
    y_pred=np.array([[2.0], [3.0]]),
    sample_weight=np.array([[0.0], [1.0]])
    ).numpy()

However, I am concerned that the default reduction for Loss still doesn't match the behavior for Metric, which will lead to confusion and unexpected behavior. I think the default reduction should now be mean_with_sample_weight instead of sum_over_batch_size, even though this breaks backward compatibility (it fixes a longstanding bug). When someone specifies sample weights, they expect them to be used by default. If the the default reduction is changed, someone could still manually re-enable the old behavior by setting the reduction to sum_over_batch_size if they wish.

authors: JotaFan SuryanarayanaY seandaug


text:
External  Data generator for Audio files

I have a very large audio dataset with 300hr of data.
There is a 'Data' folder with multiple sub-folders, and a text file specifying train-test-validation protocol.
I need help with data_generator function so that I can read a batch of wave files process them and pass them to keras .fit() function for model training.
I am new to python, so any help will be appreciated.
Thanks

Hi!
This question seems best suited for StackOverflow. Could you post your issue there? Also, remember to close your issue if you do so!
Thanks!


text:
@unit types and format discussion, addition of new units

While rechecking @unit in the files, I have this one with a ? type:

values of A 1 are on average ∼ 10 −8 au/d 2

au/d^2 seems to convert to m/s^2 so I annotate it like this:
values of A 1 are on average ∼ <measure type="value"><num>10 −8</num> <measure
type="ACCELERATION" unit="au/d^2">au/d 2</measure></measure>

au/d^2 and m/s^2 are not yet in the units.json file, how do we proceed to add them?

I am actually not sure we should add this kind of unit in units.json, as it is the composition of existing "sub-units".
As we say at the EPO, we need a step back and see what we are trying to achieve with this attribute :D
Let's take the week-end to think about it...

FYI here is a file listing the units present in the annotated files but not in the units.json.
We are not sure what to do with them.
Units not in units.json.txt

I'm not sure I've understand this last comment... these are all composed units ... so I don't see why we should have them in unit.json...

Well it wasn't clear at the time but if it is now we can close this issue?

authors: ebenaissa everzeni kermitt2 lfoppiano


text:
Changed confirmation shown upon saving application

Added some additional context around what it means for the application to be "saved". I wanted to make the differences between save and submit clear by illustrating the action of leaving the website, coming back, and still needing to submit. Tried to maintain as close a character count as possible to the application submitted message to ensure it's not too long.

lgtm
thanks for your contribution @mulligan-madness!

authors: mulligan-madness simonkernel

repo: kernel-community/services


text:
Presenters and automatic reload raises an exception

I am opening an issue to know if I should do something else in my project or if it is possible to improve the shortcode gem.
I created my presenters in the app/presenters directory in my rails app to get automatic reload in development environment so I don't have to restart the server when I change something in a presenter. The presenters are registered in an initializer.
However, when I modify a presenter, on the next load of a page using shortcode, I get that exception:
A copy of ExamplePresenter has been removed from the module tree but is still active!

I was able to fix this temporarily by registering my presenters in my controller, but I don't like the idea.
The other solution I think would be good is to change the register implementation to store string of the class name instead of the class itself. So the class can be reloaded and called over and over dynamically.
def register(presenter)
  validate presenter
  [*presenter.for].each { |k| presenters[k.to_sym] = presenter.to_s }
end

Then each time the class is needed, we'll have to use  "Classname".constantize. Maybe we should make a getter method...
I'm not 100% sure this will fix the problem, so I will be working on it. If that's not the solution, I will tell you. If it is, I will create a PR. If you have a better idea, I'd like to try it.

I have the same issue, would it be possible to merge this? I understand @kernow had some objection for using this fix in production, but I'm not sure what the issues could be?
@sophiedeziel I suggest using safe_constantize instead of constantize

@mtarnovan I'll have a look at this later today, the main reason I haven't merged is because I've not had the time, there were a few tweaks I wanted to make before merging that I haven't got around to yet.

Ok, let me know if I can help.

Ok so the issue is that contstantize is a rails method so it can't be used. Another way will need to be found to solve this issue.

How about Module.const_getor cherry-picking ActiveSupport's constantize?

Oh, I did not know that about constantize. Module.const_get seems an excellent approach. It would make us use symbols instead of strings, which is also good.

I think this will cause more problems for other users as const_get does not work for all situations e.g. Foo::Bar. Could you try registering your presenters as ::ExamplePresenter rather than ExamplePresenter to see if that fixes the situation?

I will experiment with every scenarios I can think of and write the proper tests for it. Thanks for the feedback :smile:

@sophiedeziel I meant trying out Shortcode.register_presenter(::CustomPresenter) rather than changing anything within the gems code. See if this resolves your problem first.

That would be awesome if it's solving it. I can't remember, I think I tried a couple of months ago and it didn't. But honestly, it's hard to remember.

What about:
2.0.0-p353 :003 > module Foo; module Bar;class Baz; end;end;end
 => nil
2.0.0-p353 :004 > 'Foo::Bar::Baz'.split('::').reduce(Module, :const_get)
 => Foo::Bar::Baz

I think this is a problem with the rails class reloading in development that's not related to Shortcode. If your presenters are in the /app directory they they are set to reload on each request. If this issue is only happening occasionally then it's likely that it's something outside of Shortcode causing the problem.
If it's only happening occasionally (and not on every request) then restarting the rails app isn't much of an issue. I'm going to close this issue for now.

@mtarnovan to reproduce it, change something in your presenter file. Each time the class changes, it is reloaded but the reference we keep remains the same. I'll have a look on other gems to see what strategy they use when they have to register classes and keep a reference to them.
Another solution would be to have the presenters in the lib/ directory, but we'll have to restart our server each time we modify our presenters.

For some reason this issue happens for us from time to time even without changing a presenter file, and after it happens a server restart is required for it to go away. Obviously not a blocker, but rather annoying, so I'd like to find a fix other than moving the presenters out of autoload_path.

authors: kernow mtarnovan sophiedeziel

repo: kernow/shortcode


text:
Is this a severe bug?

http://recordit.co/Ku2BfXpduM   Here you could see a screen recording I made.
When I tried to import some new modules or I just press shift+ctrl+alt+o to try to import, all the import lines will go inside the class...That's terrible.. Could you help me solve the issue? Thanks a lot!

This is a known issue. All java source files usually contain a package declaration but you don't have one in your file. Add a package declaration or at least couple of empty lines at the beginning of java source file and it should work fine. Currently the package does not support java files without package declaration.

#35 duplicate

OK  I see  ,thanks~

repo: keskiju/autocomplete-java