text:
Reduce katosys/zookeeper docker image size

Use an Alpine Linux base image to package zookeeper.

Done.

repo: katosys/kato


text:
Modal issue when used with Refined Github

Hi there! I love this extension, thank you for creating it.
When using this extension with Refined Github, I have noticed the modal is obscured by some of the UI:
.
Adding a z-index: 1 to the <details-menu> element fixes the issue.
I used the custom CSS option of Refined Github to fix it, but wanted to file an issue here in case someone else runs into this. The custom CSS I used was:
li.npm-stats > details > details-menu {
z-index: 1;
}

Hey @jonchurch, thanks a lot for your contribution 🥇 I'll release your fix at the weekend 👍

Thanks! I just pushed a new commit to the PR, I was previously targeting a style which wasn't always applied.

Submitted v1.3.3 with your fix 🎉

source: gharchive/issue

authors: jonchurch katranci

repo: katranci/github-npm-stats

license: mit

license_type: permissive

license_source: bigquery


text:
Example Makefile dependent actions

Related to https://github.com/kaustubh-sadekar/OmniCV-Lib/issues/19
cc https://github.com/openjournals/joss-reviews/issues/2533

closing stale PR

source: gharchive/pull-request

repo: kaustubh-sadekar/OmniCV-Lib

license: MIT

license_source: github-api


text:
Add files via upload

Google Translator
Description
Please include a summary of the changes you have made in regard with this issue.
Fixes #(issue number)
Type of change
Please delete options that are not relevant

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] This change requires a documentation update

Checklist:

[ ] I have read the contribution guidelines before making this PR.
[ ] My code follows the style guidelines of this project
[ ] I have performed a self-review of my own code
[ ] I have commented in my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation (Language folder or any other readme instructed to)
[ ] My changes generates no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works

This translate Hindi to engish and Speaks too


text:
Because every version of flutter_test from sdk depends on xml 3.5.0 and excel >=1.0.4 depends on xml ^4.1.0

I have tried to use excel 1.0.4
I can't advance by this error..
Please, help me. Thank you.
"Because every version of flutter_test from sdk depends on xml 3.5.0 and excel >=1.0.4 depends on xml ^4.1.0, flutter_test from sdk is incompatible with excel >=1.0.4.
So, because flutter_app_sheet depends on both excel ^1.0.4 and flutter_test any from sdk, version solving failed.
pub get failed (1; So, because flutter_app_sheet depends on both excel ^1.0.4 and flutter_test any from sdk, version solving failed.)"

Can You share your pubspec.yaml file ?

If it not works then please run flutter doctor -v and post your logcat here.
Thank You

Hey I found that issue is being resopved after running command
flutter update-packages --force-upgrade

Thank you.
I will try to it and let you know again..
Thank you again.

Closing this issue as command flutter update-packages --force-upgrade worked and  version solving failed no longer appeared.
Feel free to further re-open up the issue if you feel so.
~Thank You
LONG LIVE OPEN S🔥URCE

Thank you .
I will try to and let you know about result .
Thank you again

Closing this issue as command flutter update-packages --force-upgrade worked and version solving failed no longer appeared.
Feel free to further re-open up the issue if you feel so.
~Thank You
LONG LIVE OPEN S🔥URCE

I had tried it by myself.


text:
Unable to use vue-cli-service i18n:report in Windows 10

If i want to use this command line : "vue-cli-service i18n:report", i have error with windows 10 :
screen of error on vue-cli 3
http://prntscr.com/oc5brr

I have similar error, using bash from git for windows, with most recent version of plugin

Have you tried escaping the pipe character and/or using double quotes on source path?
Anyway, this seems a bash error and not an error with the plugin itself.

Yes, escaping pipe has nos effect for me :/

I think the problem is with underlying library used for wildcard that it doesn’t support format

I solved this issue by replacing the single-quotes with douple-quotes in the package.json:
"i18n:report": "vue-cli-service i18n:report --src \"./src/**/*.?(js|vue)\" --locales \"./src/locales/**/*.json\""

related #81

authors: Dragoon1010 georgyfarniev kazupon niccord sense-it-gmbh


text:
WIT should expire after 24 hours

v0.7.0 supported supported the WIT (Warning/Ignorable/Total) as #224
The WIT persists forever at the moment, it is not very good. It should expire in a certain period. e.g., 24 hours.

See https://www.sohamkamani.com/blog/javascript-localstorage-with-ttl-expiry/ for how to set the expiry to the item stored in the localStorage.

repo: kazurayam/materialstore


text:
MaterialProduct class; in which package should this class belong?

in v0.8.0, MaterialProduct class belongs to the com.kazurayam.materialstore.reduce package as
https://github.com/kazurayam/materialstore/blob/main/src/main/java/com/kazurayam/materialstore/reduce/MaterialProduct.java
Is it the best choice?
Why not com.kazurayam.materialstore.filesystem.MaterialProduct?
Or why not com.kazurayam.materialstore.differ.MaterialProduct?

worked out at v0.8.3-SHAPSHOT


text:
Batch Normalization freeze

Hi @kazuto1011 , thanks for this wonderful work. While reading your code, I noticed that before the training, you freezed the batch_normalization layers.

model.train()
model.module.scale.freeze_bn()

I am wondering what is the propose of this freeze, and if i train a network from scratch, does it still make sense to impose the freeze_bn()?
Thanks by advance for your kind reply!

If you start from scratch, you must train all the batch norm layers, with adequate batch size to estimate the statistics of the mini-batch. The reason to freeze the batch norm layers in training is to reduce the computational cost, but note that the layers are pre-trained on ImageNet/COCO. It is a common technique in training models that need a very large memory, like in semantic segmentation.
If you'd like to train the batch norm params with multiple GPUs, you cannot use this repository as is. Please search for "sync batch norm" and replace with it.


text:
Version 1.0 not working

Since updating from version 0.5 to 1.0 the tooltips on my site no longer work (using Chrome 73). This is not just a problem with my site, I also tested the JSFiddle linked to in the readme and it worked at first, but after I changed the balloon-css resource in the sidebar from version 0.3 to 1.0, the tooltips in the demo no longer work.

Yes. v1.0 is a major update and thus has breaking changes. It's not working in your website probably because we now use aria-label instead of data-balloon.
The new website will be released soon.

New website released.

authors: kazzkiq tjohnsonBCM


text:
DISC-12 abstract imageserver

This moves specification of the imageserver URL used as injection to the transformers to a central property in the configuration flow, as opposed to duplicating the URL.

Ready for review.

I've put this on hold again until I have it fully running on the devel server.

Setting this to active as the overriding issue has been resolved. Calling
http://:10001/ds-present/v1/records?collection=samlingsbilleder&maxRecords=1&format=SolrJSON
demonstrates working injection. Note that <internaldevelserver must be replaced with the real server name.

Setting this to active as the overriding issue has been resolved. Calling
http://:10001/ds-present/v1/records?collection=samlingsbilleder&maxRecords=1&format=SolrJSON
demonstrates working injection. Note that <internaldevelserver must be replaced with the real server name.

The injection works. However it injects our IIIF server where the test corpus uses the IIP server. Will you fix this here or should i do that on the branch I am working on?

authors: VictorHarbo tokee

repo: kb-dk/ds-present


text:
Get rid of dependencies in configuration of docker-compose

Relavant part from README:

RDF4J_SERVER_URL -- to set up different Rdf4j server (defaults to internal docker service at http://rdf4j:8080/rdf4j-server).
Note that this variable must be consistent with variable RDF4J_PCONFIGURL.
RDF4J_REPOSITORYNAME -- to set up different Rdf4j repository name where SPipes logs from execution are created
(defaults to s-pipes-hello-world). Note that this variable must be consistent with
variable RDF4J_PCONFIGURL.
RDF4J_PCONFIGURL -- to set up configuration of Rdf4j repository where SPipes logs from execution are created
(defaults to $SPIPES_ROOT/doc/examples/hello-world/config.ttl). Note that this variable must be consistent with
variables RDF4J_SERVER_URL and RDF4J_REPOSITORYNAME.

Maybe config.ttl would be template with variables?

repo: kbss-cvut/s-pipes-editor-ui


text:
Secret decode

This PR contains a new keybinding for char('x'). When viewing secrets, this new handler logic allows the user to see the base64-decoded secret contents.

Awesiome! Thanks. Could you add one or two tests for the decoding part please

I've added a test -- test_decode_secret. I've also done a little cleanup to make clippy happy. Let me know if you'd like me to change the way its implemented. I wasn't sure where exactly to put the handler for decoding the secret, so I put the logic within the handle_describe_or_yaml_action() function - possibly not the ideal place, but it does work.

repo: kdash-rs/kdash


text:
Delete unnecessary files like *.iml, *.DS_Store, etc.

Deleted files that match the patterns:
*.DS_Store # Hide files made by MacOS
*.iml # Hide files made by IntelliJ IDE
*.project # Hide files made by Eclipse IDE

and added these patterns to .gitignore.
I also fixed a small typo in the file extension of one file. The extension was .javaa so I renamed it to .java

I could squash the commits into one if you wish


text:
Include attachments in Message event type

I've been playing around with fawkes and found I needed the attachments from the message.
I tried to add it in a way that is consistent with the current code, but happy to do it another way. Just point me in the direction you prefer.

Example of the raw message data.
%{
  "attachments" => [
    %{
      "author_name" => "rollout-test.flagger",
      "color" => "2eb886",
      "fallback" => "New revision detected, progressing canary analysis.",
      "fields" => [
        %{
          "short" => false,
          "title" => "Target",
          "value" => "Deployment/rollout-test.flagger"
        },
        %{
          "short" => false,
          "title" => "Failed checks threshold",
          "value" => "5"
        },
        %{"short" => false, "title" => "Progress deadline", "value" => "300s"},
        %{
          "short" => false,
          "title" => "Traffic routing",
          "value" => "Weight step: 10 max: 50"
        }
      ],
      "id" => 1,
      "mrkdwn_in" => ["text"],
      "text" => "New revision detected, progressing canary analysis."
    }
  ],
  "bot_id" => "B0164TD383V",
  "bot_profile" => %{
    "app_id" => "AN89XFLBU",
    "deleted" => false,
    "icons" => %{
      "image_36" => "https://avatars.slack-edge.com/2020-06-26/1208551132130_a2f53ebb1f87db1ece3c_36.png",
      "image_48" => "https://avatars.slack-edge.com/2020-06-26/1208551132130_a2f53ebb1f87db1ece3c_48.png",
      "image_72" => "https://avatars.slack-edge.com/2020-06-26/1208551132130_a2f53ebb1f87db1ece3c_72.png"
    },
    "id" => "B0164TD383V",
    "name" => "Flagger",
    "team_id" => "TB3CSLAF6",
    "updated" => 1593191652
  },
  "channel" => "C016H634X2M",
  "event_ts" => "1596760084.004600",
  "subtype" => "bot_message",
  "suppress_notification" => false,
  "team" => "TB3CSLAF6",
  "text" => "",
  "ts" => "1596760084.004600",
  "type" => "message"
}

Thanks @forest this LGTM :tada:

authors: forest keathley

repo: keathley/fawkes


text:
Add volume adjustment while in standby

This should resolve #43.
This is done by forcing a TTS for "......." before setting the volume if nothing is detected playing.  When playing a Flash Briefing, there is no media reported, but it appears to successfully change the volume without interrupting the skill.   Tested for US English so it's possible the multiple period may break in another language.

@keatontaylor Would you object to using the TTS hack as a temporary fix until you have time to reverse the APK?
As for your other thought on routine sequences from the script, I looked when I implemented routines in the API but I didn't see an effective way to do it. While I could find examples of how to call existing sequences, I didn't see a programmatic way to create them. The script doesn't have a solution either for volume.
Of course, I'll need to refactor this for #73 before I merge it in.

Nevermind, I found the sequence being used in routines Alexa.DeviceControls.Volume. This is tested to work even when set_media didn't. I'll close this proposal and add it to the 1.0.0 release.


text:
Parallel CI tests

Changes:

Run CI and KBC tests in parallel.
It is 2x faster, and other versions of the MySQL server can be easly added to the tests.

@ondrajodas vdaka, to som nejak nezachystil, upravim PRs

@ondrajodas myslim, ze tu akciu nepojde pouzit, pouziva sa tam verzia a latest tag.
Spytam sa na Slacku.

můžeš tam poslat nějaký test tag... viz:
https://github.com/keboola/component-generator/pull/85/files#diff-4101956605fc3541c242a0a8a788dfe7b122cfd86fe39eb9aefa10df68ecc31bR31

a latest tag můžeš přeskočit...
tag: test
push_latest: false

koukni na https://github.com/ondrajodas/test-component-generator7/runs/3395165592?check_suite_focus=true

tu pull akci jsem měl ještě v plánu udělat po dokončení component generatoru aby byla připravená...

@ondrajodas daj prosim approve ako si pisal
mam pripravene upravy, ale potrebjem ich vyskusat a lepsi bude dalsi PR, vdaka ;)

authors: ondrajodas webrouse

repo: keboola/db-extractor-mysql


text:
změna struktury

9:19]
pro mě: strukturovat šablonu tak, ať můžu vzít root uzly a porovnat je s configem a podle toho určit, zda to je z té šablony
eg:
{
  "name": "abc",
  "desc": "cde",
  "data": {
    "config": {
      "incrementalOutput": true,
      "jobs": [...],
      "mappings": {...}
    }
  }
}

(edited)
[9:19]
v data by mohlo být cokoliv, to by byl obsah šablony, a v json editoru by mohlo bejt cokoliv, co má s tímhle nulovej průnik
a v UI by se to při uložení merglo (edited)
najlos [9:31 AM]
přepnutí do editace otevře jeden JSON editor s uzlem config
najlos [9:36 AM]
vymyslet s padákem jak stvořit template, aby se nemotal ve složitejch jsonech

hotovo

repo: keboola/kbc-ui-templates


text:
CT-875 bucket sharing use JSON

Jira: CT-875 CT-874
KBC: https://github.com/keboola/connection/pull/4226
Before asking for review make sure that:
Checklist

[x] New client method(s) has tests
[x] Apiary file is updated

Release

[x] I gave the PR a proper label:

major (BC break)
minor (new feature)
patch (backwards compatible fix)
no release (just test changes)

Když už šaháš na ty metody klienta tak jim mohls přidat typy normálně, to imho BC není a min verze je php7.4

Uz jsme to nekolikrat resili u jinych endpointu, a dosli k tomu, ze to muze byt BC.
Pac tam nekdo muze posilat cislo 123 a my tam ted dame string, tak mu to spadne, pac ocekava "123".

repo: keboola/storage-api-php-client


text:
add ['allowTruncate' => true] to tests

Jira: CT-XXX
KBC: XXX
Before asking for review make sure that:
Checklist

[x] New client method(s) has tests
[x] Apiary file is updated

Release

[x] I gave the PR a proper label:

major (BC break)
minor (new feature)
patch (backwards compatible fix)
no release (just test changes)

rebase


text:
clean up documentation for 2.13 deprecation release

Hi team,
This PR updates the documentation for clean up deprecation in prepration for 2.13 release
Checklist

[x] Commits are signed with Developer Certificate of Origin (DCO)

Hi @JorTurFer , is there anything that need to be fixed before we merge this PR?

repo: kedacore/keda-docs


text:
feat: Provide support for specifying identity to use for Azure managed identity auth

This PR aims at improving the way pod managed identities are used with Azure Services and Azure Storage in particular. Workloads can specify the identity to be used by the operator when peeking the Azure service
Checklist

[x] Commits are signed with Developer Certificate of Origin (DCO - learn more)
[ ] Tests have been added
[ ] A PR is opened to update our Helm chart (repo) (if applicable, ie. when deployment manifests are modified)
[ ] A PR is opened to update the documentation on (repo) (if applicable)
[ ] Changelog has been updated and is aligned with our changelog requirements

Relates to https://github.com/kedacore/keda/issues/2656.

Would you mind sending a PR for our docs please?

Would you mind sending a PR for our docs please?

No problem. I was waiting for this PR to move on :)

Let us know if you need any other feedback @stephaneey!

@tomkerkhove  I applied all the changes on my own branch. Should I make a new PR?

Nope, you can just push them here indeed, thanks!
Would you mind rebasing/merging latest from main to fix the conflicts please?

Nope, you can just push them here indeed, thanks!
Would you mind rebasing/merging latest from main to fix the conflicts please?

Hey @tomkerkhove
Sorry to bother but I'm not sure what I'm supposed to do here. I applied all the changes to this branch on my own repo: https://github.com/stephaneey/keda/tree/stephaneey/podidentity
I thought of closing this PR and making a new one so that all the latest changes would be part of the new PR.  Merging is greyed out for me...I also don't want to do something that violates the DCO (I lost quite some time with this already). So, what am I supposed to to exactly?
Thanks

No need to create a new PR or we will lose the context from this one.
What you should do is:

Add upstream remote to kedacore/keda
Fetch main branch and pull it
Merge changes to your fork's branch

This should help you : https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/working-with-forks/merging-an-upstream-repository-into-your-fork

It's alwasy better to do git pull --rebase instead of merging new changes from main. DCO is fixable (Details on DCO provides a customized command that fixes DCO).
But if you think that it is too complicated, there's no need to open a new PR, you can just force push to your branch :)

Hey @tomkerkhove @zroubalik
Thanks for your review. I resolved the conflicts and the PR is being validated.
Best regards

Thanks a ton!

/run-e2e azure*

Looking good, but I think we should document this, could you please open docs PR?
@tomkerkhove @zroubalik

Where should it be documented? I don't see a "general" category in the docs. Can you elaborate on what is expected to avoid back & forth conversations? I already "documented" the changes in the initial issue #2656. I have forked the docs repo..
Thanks

All docs live in kedacore/keda-docs (see PR description) where we need to document this new feature in how people can configure to use a different identity (not perse how it works under the covers)

Feel free to have a look at our contribution guide.

Feel free to have a look at our contribution guide.

That's exactly what I did (as mentioned I already cloned the doc repo & created my own branch) and why I come back to ask what is expected. The contribution guide just says that you must open a PR for the doc...On Keda Docs, there are only instructions for:

Adding a new blob post
Adding a new scaler
Adding a new FAQ
Adding a new troubleshooting guidance

So my question is: where should I document my changes, given none of the above category corresponds. The closest one could be a blog post. Do you confirm?
Thanks

No, we already have a documentation page for trigger authentication where you can just extend the pod Identity option for Azure.
https://keda.sh/docs/latest/concepts/authentication/
Just make sure this is only in v2.7.
Every documentation page also has a "suggest a change" button that takes you to the exact file.

The reason why it's not in that section is because there is no dedicated page per auth provider.
But I'll update the guidance to look for the suggest a change button as well if need be.

Ok thanks, I'll have a look at it

Feel free to let us know if you need any help @stephaneey

Bump @stephaneey

Bump @stephaneey, anything we can help you with?
Do note that our workload identity support is close as well - #2907

Hi Tom,
Indeed, sorry for the late reply. I guess we'd better discard the PR with the arrival of workload identities and the low value added to the product.
Best Regards

Oh I don't think this is low value add as it allows for identity segregation but maybe you don't have time to work on it anymore?

Oh I don't think this is low value add as it allows for identity segregation but maybe you don't have time to work on it anymore?

Well, indeed, it's a bit tricky these days and I spent more time in fixing conflicts than writing the actual code. The review process takes time (it's normal and even a very good practice to ensure high quality), but this leads to new conflicts each time I adjust the changes to the remarks, so it's a never ending story and I don't have much time to allocate (my bad). I don't know if someone can take this over, else, it was a nice attempt :)

No problem at all - I will merge this in to azure-identity-seperation branch and hopefully somebody else can pick this up.
Thanks for the initial start.

Oh I don't think this is low value add as it allows for identity segregation but maybe you don't have time to work on it anymore?

Well, indeed, it's a bit tricky these days and I spent more time in fixing conflicts than writing the actual code. The review process takes time (it's normal and even a very good practice to ensure high quality), but this leads to new conflicts each time I adjust the changes to the remarks, so it's a never ending story and I don't have much time to allocate (my bad). I don't know if someone can take this over, else, it was a nice attempt :)

We are always happy to hear feedback on how we can improve though

authors: stephaneey tomkerkhove zroubalik

repo: kedacore/keda


text:
Wordpress examples don't seem to work.

Using kedge + wordpress, the example does not seem to deploy:
▶ kedge create -f db.yaml -f web.yaml
deployment "database" created
service "database" created
unable to unmarshal data: could not unmarshal into internal struct: error converting YAML to JSON: yaml: line 304: mapping values are not allowed in this context

Ping @surajssd

@cdrage, it's working on my machine:
$ kedge create -f db.yaml -f web.yaml
deployment "database" created
service "database" created
deployment "web" created
service "wordpress" created

it worked for me
$ kedge create -f db.yaml -f web.yaml
deployment "database" created
service "database" created
deployment "web" created
service "wordpress" created

kedge version
$ kedge version
0.0.0 (9c3094b)

k8s version
$ k version
Client Version: version.Info{Major:"1", Minor:"6", GitVersion:"v1.6.4", GitCommit:"d6f433224538d4f9ca2f7ae19b252e6fcb66a3ae", GitTreeState:"clean", BuildDate:"2017-05-19T18:44:27Z", GoVersion:"go1.7.5", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"6", GitVersion:"v1.6.4", GitCommit:"d6f433224538d4f9ca2f7ae19b252e6fcb66a3ae", GitTreeState:"dirty", BuildDate:"2017-06-22T04:31:09Z", GoVersion:"go1.7.5", Compiler:"gc", Platform:"linux/amd64"}

Also the app is running
$ k get pods
NAME                        READY     STATUS    RESTARTS   AGE
database-4172966911-mk6g8   1/1       Running   0          2m
web-3796593503-5zb75        1/1       Running   0          2m
web-3796593503-nk9sj        1/1       Running   0          2m

$ k get svc
NAME        CLUSTER-IP   EXTERNAL-IP   PORT(S)          AGE
database    10.0.0.126   <none>        3306/TCP         2m
wordpress   10.0.0.250   <nodes>       8080:30947/TCP   2m

$ curl -L `minikube ip`:30947
<!DOCTYPE html>
<html xmlns="http://www.w3.org/1999/xhtml" lang="en-US" xml:lang="en-US">
<head>
        <meta name="viewport" content="width=device-width" />
        <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
        <meta name="robots" content="noindex,nofollow" />
        <title>WordPress › Installation</title>
        <link rel='stylesheet' id='buttons-css'  href='http://192.168.42.199:30947/wp-includes/css/buttons.min.css?ver=4.8' type='text/css' media='all' />
...

not sure what got messed up @cdrage

@surajnarwade @surajssd Odd. Deleted the binary and re-builtand it works. May have used the binary form the $GOPATH folder.
It works now!
Thanks @surajssd for checking it out and @surajnarwade

authors: cdrage surajnarwade surajssd

repo: kedgeproject/kedge


text:
Move to using kedge schema structs in kedge init

Right now we use golang templates, so we should think of moving to using kedge schema a.k.a. structs that kedge has defined. Golang templates tend to get complex very soon. With structs we can add more features and have easier control on what is to be generated.

When we start doing more complex generation it might become a bit complex with templates, I agree.
The thing is that we actually lose control over what is generated if we start serializing Kedge schema. For example, we lose ability to add comments.
The idea was that generated Kedge file should also contain some comments when we start doing a little bit more than just image and ports.

I'm marking this as a low priority. What we have is working right now. We can start thinking about this once it becomes an issue, or we need add more stuff to kedge init

@surajssd  @kadel Now we have golang structs in kedge init instead of templates, shall we close this ?

we are using golang structs but not kedge schema structs yet

authors: kadel surajnarwade surajssd


text:
CI is broken

https://github.com/kedro-org/kedro-starters/pull/136 made a one character change in the README but there were some test failures.
https://app.circleci.com/pipelines/github/kedro-org/kedro-starters/618/workflows/687e92b1-d6d7-41e1-9348-dc8566bb9c39/jobs/6650
Failing scenarios:
  features/run.feature:26  Run a Kedro project created from pyspark-iris

0 features passed, 1 failed, 0 skipped
4 scenarios passed, 1 failed, 0 skipped
24 steps passed, 1 failed, 0 skipped, 0 undefined
Took 3m56.385s

Exited with code exit status 1

CircleCI received exit code 1

This is the error:
DatasetError: An exception occurred when parsing config for dataset
'example_classifier':
Dataset type 'kedro.io.memory_dataset.MemoryDataSet' is invalid: all data set
types must extend 'AbstractDataSet'.

Root cause:
https://github.com/kedro-org/kedro-starters/blob/2d86c0f2bbf5e535a7c0ec3f2470e979990df966/pyspark-iris/{{ cookiecutter.repo_name }}/conf/base/catalog.yml#L97-L103
and
https://github.com/kedro-org/kedro/blob/fd8162d5bf384ef666c01ef2c529d01fd9fa8354/kedro/io/core.py#L427-L431

In progress at https://github.com/kedro-org/kedro/pull/2724

Test: gh-138

repo: kedro-org/kedro-starters


text:
Adding signature safety margin on DKG result

Close https://github.com/keep-network/keep-core/issues/1585
In this PR we are increasing the DKG nofail signature threshold to 75%.  It gives us a 25% safety margin for relay entry signing.

@eth-r @ngrinkevich would love to have your 👀 on this one.

The solidity side looks good to me

And everything else looks good to me too. Let's merge.

authors: dimpar eth-r pdyraga

repo: keep-network/keep-core


text:
Improve-temaplte-api

In this API template we need to add all the basics we need to make it work. Lets make a list.

Jest testing (max workers 1 and passing with no test)
eslint
structure folder (infra,domain... etc)
minimal express config
default helathcheck endpoint (we dont need to apply checks)
graceful stopper (we dont need to stop anything at this point, but lets have this)
Docker
Docker-compose
Mongo db handler
package.json with minimal scripts (run, dev with nodemon, test)

I take it

All yours

<3

authors: AlfonMnz EsteveSegura

repo: keep-secrets/template-api


text:
use snforge for tests

base on issue #47 , we are now using snforge 0.23.0 for test

CI does not seem to run smart contract tests? Would you please re enable them?

@maciejka this is what am adding to yml file
 tests:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v3
      - uses: software-mansion/setup-scarb@v1
      - uses: foundry-rs/setup-snfoundry@v3
      - name: Run cairo tests
        run: scarb test
        working-directory: onchain

but github action does not run it, what could their be the problem

  shell: /usr/bin/bash -e {0}
Error:  Cannot find `scarb` binary. Make sure you have Scarb installed https://github.com/software-mansion/scarb: cannot find binary path

could this be a path issue @maciejka

  shell: /usr/bin/bash -e {0}
Error:  Cannot find `scarb` binary. Make sure you have Scarb installed https://github.com/software-mansion/scarb: cannot find binary path

could this be a path issue @maciejka

Ask here: https://t.me/starknet_foundry

Github action is successfully running the test setup

repo: keep-starknet-strange/joyboy


text:
[Proposal] Transfer this repository to @sjtu-ieee

By accident, today I found there's already a group for IEEE pilot class @sjtu-ieee.
Would it be better to transfer this repo to that group for better maintenance and make it seem more 'collective' instead of 'personal' under @keithnull's account?
If so, I think there would be quite a lot of work to do for that transfer. For example:

[ ] Contact the current owner(s) of @sjtu-ieee
[ ] Gitalk config
[ ] Links and references
[ ] Github Action
[ ] Github Page
[ ] ... and more?

cc @xxchan @ghost-no1337


text:
Closes #5232

Checklist:

[x] Updated extVersionCode value in build.gradle for individual extensions
[ ] Updated overrideVersionCode or baseVersionCode as needed for all multisrc extensions
[x] Referenced all related issues in the PR body (e.g. "Closes #xyz")
[ ] Added the isNsfw = true flag in build.gradle when appropriate
[x] Have not changed source names
[ ] Have explicitly kept the id if a source's name or language were changed
[x] Have tested the modifications by compiling and running the extension through Android Studio
[ ] Have removed web_hi_res_512.png when adding a new extension

Put "Closes #5232" in the PR description so it actually links to it, and write a short title about this PR request instead (ex. "CosplayTele: Update popularMangaRequest" or whatever)

authors: Smol-Ame fqrious

repo: keiyoushi/extensions-source


text:
🛑 bigdata is down

In 1816497, bigdata (https://bigdata.ministep.cn/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: bigdata is back up in 006f053 after 5 minutes.

repo: kemistep/upptime


text:
Replace validate_* functions with native puppet validation

All stdlib validation functions should be replaced with native puppet types and type validation. This will clean up the code and make it future proof.

All deprecated validation functions will be replaced with PR #62.

authors: ggeldenhuis samjmarshall


text:
is the file test-db.sql fully updated?

現在の test-db.sql は本番DBのschemaとどれくらい一致していますか？
こちらにはindexが張られていませんが、本番のDBもそうなっていますか？

たぶん反映されていないです。反映します。

本番DBも同じスキーマでした。かつてはindexを張っていたと思いますが、DBサーバーを移行してからは張られていなかったぽいです。

確認ありがとうございます。
となるといくつか貼るべきindexがあるはずなので調べて見つけたら報告します。

:pray: :bowing_man: :pray:

authors: kenkoooo kmyk

repo: kenkoooo/AtCoderProblems


text:
Easier cmd list (add newline and indent)

Closes #179

BEFORE
branches Get a nice pretty list of branches.
graft <branch> <into-branch> Merges specified branch into the second branch, and removes it.
harvest [<branch>] <into-branch> Auto-Merge/Rebase of specified branch changes into the second branch.
help <command> Display help for legit command.
install Installs legit git aliases.
publish <branch> Publishes specified branch to the remote.
sync <branch> Syncronizes the given branch.
settings Opens legit settings in a text editor.
sprout [<branch>] <new-branch> Creates a new branch off of the specified branch.
switch <branch> Switches to specified branch.
sync <branch> Syncronizes the given branch.
unpublish <branch> Removes specified branch from the remote.

AFTER
branches
  Get a nice pretty list of branches.
graft <branch> <into-branch>
  Merges specified branch into the second branch, and removes it.
harvest [<branch>] <into-branch>
  Auto-Merge/Rebase of specified branch changes into the second branch.
help <command>
  Display help for legit command.
install
  Installs legit git aliases.
publish [<branch>]
  Publishes specified branch to the remote.
resync <upstream-branch>
  Re-synchronize current branch with specified upstream branch.
settings
  Opens legit settings in a text editor.
sprout [<branch>] <new-branch>
  Creates a new branch off of the specified branch.
switch <branch>
  Switches to specified branch.
sync <branch>
  Synchronizes the given branch.
unpublish <branch>
  Removes specified branch from the remote.

I like it

authors: hickford wkentaro

repo: kennethreitz/legit


text:
COC?

Hi,
I'm just wondering what your code of conduct is for this project?
Thanks,
Alison

Hi @alison985!
Currently our relatively minor code of conduct is defined here. There is interest amongst some of the maintainers in moving to something based on the Contributor Covenant, given that both myself and @sigmavirus24 maintain personal projects that use it, but I'm unwilling to change that by fiat: I'd want consensus from the whole team.
Regardless, I believe that the Contributor Covenant implicitly applies to this project, and certainly that's the standard to which the maintainers hold themselves.

repo: kennethreitz/requests


text:
Issue-1.0.0

Automated Review Comments
Issues in package-lock.json:

(3, 'Hardcoded string found')
(4, 'Hardcoded string found')
(5, 'Hardcoded string found')
(6, 'Hardcoded string found')
(7, 'Hardcoded string found')
(8, 'Hardcoded string found')
Issues in package.json:
(3, 'Hardcoded string found')
(4, 'Hardcoded string found')
(5, 'Hardcoded string found')
(6, 'Hardcoded string found')
(7, 'Hardcoded string found')

I got it.

authors: hitosisasaki kentaurse

repo: kentaurse/coinage


text:
Prefix user tags correctly

Addresses #183, correctly setting user tag attributes.

:rocket:

repo: kentik/ktranslate


text:
Create kyocera-printer.yml

resolves #214

@Mesverrum - some YAML syntax errors caught by the validator; otherwise looks good

authors: Mesverrum thezackm

repo: kentik/snmp-profiles


text:
set responsive breakpoint to min-width instead of max-width

Is there a way to change this?
In the documentation i can't find anything for switching the breakpoint from max-width to min-width

mobileFirst

authors: leggomuhgreggo moesphemie

repo: kenwheeler/slick


text:
Handle specially wxSearchCtrl which isn't wxTextCtrl on MSW

This class is documented as it is-a wxTextCtrl,
https://docs.wxwidgets.org/3.2/classwx_search_ctrl.html
but it isn't.
https://github.com/wxWidgets/wxWidgets/blob/v3.2.0/include/wx/srchctrl.h#L26
it actually mimic the wxTextCtrl API through wxTextCtrlIface. so can't static_cast<wxTextCtrl*>().
This result the generated code fails to compile:
// Mix-in(s) to wxSearchCtrl
wxTextEntry *wxSearchCtrl_AsTextEntry(wxSearchCtrl* obj) {
    return static_cast<wxTextEntry*>(obj);
}

pending generate binding for wxSearchCtrl for now.

https://github.com/wxWidgets/wxWidgets/blob/61340fcc82cea1c7bbb66a3d34f5a958d3c58e9f/include/wx/textctrl.h#L718
In fact, wxTextCtrl is not a wxTextEntry.
In this case, this is the problem.
Using wxTextEntryBase here instead of wxTextEntry may work.


text:
Add option to specify dynatrace.conf.yaml as part of prepare project

In order to support custom tags for Dynatrace events, one must pass in dynatrace.conf.yaml.
Solution is to add an addition input field to the extension. The default form value is blank.  Here is a mockup

Reference: https://github.com/keptn-contrib/dynatrace-service#sending-events-to-dynatrace-monitored-entities

Fixed since 1.0.4

authors: heydenb robertjahn


text:
Handle the delete command to remove a service from a Keptn project

As a Keptn user, I would like to delete a service by executing the following command:
keptn delete service carts --project sockshop

Tasks:

Specify the event: sh.keptn.internal.event.service.delete in https://github.com/keptn/go-utils/blob/master/pkg/lib/events.go#L31
Implement a DELETE endpoint in the api-service: /project/{projectName}/service/{serviceName}

This endpoint sends out the event sh.keptn.internal.event.service.delete, like for deleting a project.

Implement/verify the implementation of the DELETE endpoint in the configuration-service: /project/{projectName}/stage/{stageName}/service/{serviceName}

This endpoint deletes the service in the repo by removing the folders in the branches.
If a Git upstream is defined, sync to upstream.
Remove the service from the materialized view (<- this is already implemented)

shipyard-service listens to: sh.keptn.internal.event.service.delete

If event is received, it calls the DELETE service endpoint from the configuration-service for all stages

Definition of Done:

[ ] keptn delete service successfully removes a service from a Keptn project
[ ] Implementation of the command is covered by a test (like in: https://github.com/keptn/keptn/blob/master/test/test_delete_project.sh)

I've prepared a data structure for https://github.com/keptn/go-utils/pull/193

If a user deletes a project with keptn delete project but has not deleted the services before, the shipyard-service should delete all services before deleting the project, i.e. by sending out sh.keptn.internal.event.service.delete events for all services.

I agree! As a user, I would expect to get the services deleted when deleting a project, which is per definition the enclosing entity of services.

authors: agrimmer johannes-b

repo: keptn/keptn


text:
MongoDB authentication error "AuthenticationFailed: SCRAM-SHA-1 authentication failed, storedKey mismatch"

Environment

Client OS (e.g., Linux, macOS, Windows): MacOS 11.3
Keptn Version (keptn version): 0.8.2
Kubernetes Cloud Provider (e.g., GKE, AKS): EKS
Kubernetes version (kubectl version):

$ kubectl version
Client Version: version.Info{Major:"1", Minor:"20+", GitVersion:"v1.20.4-dirty", GitCommit:"e87da0bd6e03ec3fea7933c4b5263d151aafd07c", GitTreeState:"dirty", BuildDate:"2021-03-15T09:58:13Z", GoVersion:"go1.16.2", Compiler:"gc", Platform:"darwin/amd64"}
Server Version: version.Info{Major:"1", Minor:"19+", GitVersion:"v1.19.8-eks-96780e", GitCommit:"96780e1b30acbf0a52c38b6030d7853e575bcdf3", GitTreeState:"clean", BuildDate:"2021-03-10T21:32:29Z", GoVersion:"go1.15.8", Compiler:"gc", Platform:"linux/amd64"}

Affected Component

[ ] Docs
[ ] CLI
[ ] Kubernetes Integration
[ ] Openshift Integration
[ ] Helm
[ ] Istio
[ ] Bridge
[ ] Approval
[x] Datastore
[ ] REST API
[ ] eventbroker / distributor
[ ] jmeter

Describe the bug

After running a Keptn install for a few days, all API requests are failing. If you look into the logs of the shipyard-controller, mongodb-datastore and mongodb you will see the following errors:
shipyard-controller
shipyard-controller-6844695949-ht4fd:shipyard-controller MongoDB client lost connection. Attempt reconnect.
shipyard-controller-6844695949-ht4fd:shipyard-controller Error retrieving projects from mongoDB: connection() : auth error: sasl conversation error: unable to authenticate using mechanism "SCRAM-SHA-1": (AuthenticationFailed) Authentication failed.
shipyard-controller-6844695949-ht4fd:shipyard-controller [GIN] 2021/05/03 - 16:20:36 | 500 |   497.06822ms |   10.247.146.19 | GET      "/v1/event/triggered/sh.keptn.event.service.delete.finished"

mongodb-datastore
mongodb-datastore-84c975559-jdzgl:mongodb-datastore {"timestamp":"2021-05-03T16:26:54.310005181Z","logLevel":"DEBUG","message":"MongoDB client lost connection. Attempt reconnect."}
mongodb-datastore-84c975559-jdzgl:mongodb-datastore {"timestamp":"2021-05-03T16:26:54.330087199Z","logLevel":"ERROR","message":"error counting elements in events collection: connection() : auth error: sasl conversation error: unable to authenticate using mechanism \"SCRAM-SHA-1\": (AuthenticationFailed) Authentication failed."}

mongodb
mongodb-6b455c56fb-4lj56:2021-05-03T16:21:47.486+0000 I NETWORK  [conn1184792] received client metadata from 10.247.145.228:40042 conn: { driver: { name: "mongo-go-driver", version: "v1.4.6" }, os: { type: "linux", architecture: "amd64" }, platform: "go1.13.7" }
mongodb-6b455c56fb-4lj56:2021-05-03T16:21:47.493+0000 I ACCESS   [conn1184792] SCRAM-SHA-1 authentication failed for user on keptn from client 10.247.145.228:40042 ; AuthenticationFailed: SCRAM-SHA-1 authentication failed, storedKey mismatch
mongodb-6b455c56fb-4lj56:2021-05-03T16:21:47.493+0000 I NETWORK  [conn1184792] end connection 10.247.145.228:40042 (2271 connections now open)

To Reproduce

Steps to reproduce the behavior:

Leave Keptn to run for a good amount of time. I have not noticed any specific time
Try access Bridge or check any service and you'll notice the API requests fail
Check logs and notice the SCRAM-SHA-1 authentication failed, storedKey mismatch error

Additional context

To restore the API, kubectl delete ... the Pods from the Deployment's above, shipyard-controller mongodb-datastore and mongodb and then everything is restored.

Leave Keptn to run for a good amount of time. I have not noticed any specific time

Our Keptn installations are running since we released 0.8.2 without the aforementioned problem.
What looks suspicious to me is the following line:
mongodb-6b455c56fb-4lj56:2021-05-03T16:21:47.493+0000 I NETWORK  [conn1184792] end connection 10.247.145.228:40042 (2271 connections now open)
``
There should not be 2271 connections open, I think mongodb is running in some sort of limit here.

Could you please provide the following details:

1. How was Keptn installed (using `keptn install`, `helm`, or any other method)? Was it ever upgraded?
2. Did you ever modify the mongodb credentials?
3. Are there any 3rd-party Keptn-services running, and if so, in which version? (`kubectl -n keptn get deployments -owide`)

Helm chart install. Control plane in one cluster, execution plane in another cluster. It has not been upgraded. Brand new install via ArgoCD Helm Application
In trying to debug the issue initially I did delete the credentials Secret, which was promptly replaced by ArgoCD and after restarting the services mentioned above, all was well (for a few days...)
There are no additional services running in the control plane, but the following in the execution plane:

Control plane:
$ kubectl -n keptn get deployments -owide
NAME                    READY   UP-TO-DATE   AVAILABLE   AGE     CONTAINERS                        IMAGES                                                                        SELECTOR
api-gateway-nginx       2/2     2            2           7d15h   api-gateway-nginx                 docker.io/nginxinc/nginx-unprivileged:1.19.4-alpine                           app.kubernetes.io/instance=keptn,app.kubernetes.io/name=api-gateway-nginx
api-service             1/1     1            1           7d15h   api-service,distributor           docker.io/keptn/api:0.8.2,docker.io/keptn/distributor:0.8.2                   app.kubernetes.io/instance=keptn,app.kubernetes.io/name=api-service
approval-service        1/1     1            1           7d15h   approval-service,distributor      docker.io/keptn/approval-service:0.8.2,docker.io/keptn/distributor:0.8.2      app.kubernetes.io/instance=keptn,app.kubernetes.io/name=approval-service
bridge                  1/1     1            1           7d15h   bridge                            docker.io/keptn/bridge2:0.8.2                                                 app.kubernetes.io/instance=keptn,app.kubernetes.io/name=bridge
configuration-service   1/1     1            1           7d15h   configuration-service             docker.io/keptn/configuration-service:0.8.2                                   app.kubernetes.io/instance=keptn,app.kubernetes.io/name=configuration-service
lighthouse-service      1/1     1            1           7d15h   lighthouse-service,distributor    docker.io/keptn/lighthouse-service:0.8.2,docker.io/keptn/distributor:0.8.2    app.kubernetes.io/instance=keptn,app.kubernetes.io/name=lighthouse-service
mongodb                 1/1     1            1           5d20h   mongodb                           docker.io/centos/mongodb-36-centos7:1                                         app.kubernetes.io/instance=keptn,app.kubernetes.io/name=mongodb
mongodb-datastore       1/1     1            1           7d15h   mongodb-datastore,distributor     docker.io/keptn/mongodb-datastore:0.8.2,docker.io/keptn/distributor:0.8.2     app.kubernetes.io/instance=keptn,app.kubernetes.io/name=mongodb-datastore
remediation-service     1/1     1            1           7d15h   remediation-service,distributor   docker.io/keptn/remediation-service:0.8.2,docker.io/keptn/distributor:0.8.2   app.kubernetes.io/instance=keptn,app.kubernetes.io/name=remediation-service
secret-service          1/1     1            1           7d15h   secret-service                    docker.io/keptn/secret-service:0.8.2                                          app.kubernetes.io/instance=keptn,app.kubernetes.io/name=secret-service
shipyard-controller     1/1     1            1           7d15h   shipyard-controller,distributor   docker.io/keptn/shipyard-controller:0.8.2,docker.io/keptn/distributor:0.8.2   app.kubernetes.io/instance=keptn,app.kubernetes.io/name=shipyard-controller
statistics-service      1/1     1            1           7d15h   statistics-service,distributor    docker.io/keptn/statistics-service:0.8.2,docker.io/keptn/distributor:0.8.2    app.kubernetes.io/instance=keptn,app.kubernetes.io/name=statistics-service

Execution plane:
$ kubectl -n keptn get deployments -owide
NAME                       READY   UP-TO-DATE   AVAILABLE   AGE     CONTAINERS                             IMAGES                                                                                SELECTOR
argo-service               1/1     1            1           7d15h   distributor,argo-service               keptn/distributor:0.8.0,grabnerandi/argo-service:0.8.0                                 run=argo-service
generic-executor-service   1/1     1            1           14h     distributor,generic-executor-service   keptn/distributor:0.8.2,keptnsandbox/generic-executor-service:0.8.0                    run=generic-executor-service
keptn-helm-service         1/1     1            1           7d15h   helm-service,distributor               docker.io/keptn/helm-service:0.8.2-hotfix1,docker.io/keptn/distributor:0.8.2-hotfix1   app.kubernetes.io/instance=keptn,app.kubernetes.io/name=helm-service
keptn-jmeter-service       1/1     1            1           7d15h   distributor,jmeter-service             docker.io/keptn/distributor:0.8.2,docker.io/keptn/jmeter-service:0.8.2                 app.kubernetes.io/instance=keptn,app.kubernetes.io/name=jmeter-service

This happened again and I'm leaning towards it being related to Keptn Pods shuffling around after a cluster scaling event (EKS, Spot EC2 nodes and Cluster Autoscaler). Note the Pod ages:
$ kubectl get pods -n keptn
NAME                                    READY   STATUS    RESTARTS   AGE
api-gateway-nginx-5b854464cf-24wq6      1/1     Running   0          8m35s
api-gateway-nginx-5b854464cf-6k8mb      1/1     Running   0          8m32s
api-service-7bc6ff97fc-284c2            2/2     Running   0          24m
approval-service-dcb7979c8-wcms7        2/2     Running   0          24m
bridge-788f564489-fvpwk                 1/1     Running   0          24m
configuration-service-5bc9548bd-pp5n4   1/1     Running   0          140m
keptn-nats-cluster-0                    3/3     Running   0          10m
lighthouse-service-857df5646b-hbjkk     2/2     Running   0          124m
mongodb-6b455c56fb-c65qs                1/1     Running   0          140m
mongodb-datastore-84c975559-bqg4t       2/2     Running   0          124m
remediation-service-5b9ffb54f9-mjl6s    2/2     Running   0          26m
secret-service-7ffdf597d7-n67q7         1/1     Running   0          24m
shipyard-controller-6844695949-6brkr    2/2     Running   0          24m
statistics-service-7bd9968dbd-p6mlz     2/2     Running   0          26m

I'll check next time this happens but could it be that the mongodb Pod get's killed and spun up on another node and the services, in an attempt to reconnect cause some sort of issue that can only be resolved by forcing those services to restart only once mongodb is actually running again? 🤔

If that's the case we should be able to reproduce it by killing mongodb on purpose.

I tried killing the mongodb pod and see what happens. So far nothing spectacular, everything is still working after the pod came back up.
What I am still puzzled about is the fact that your mongodb is telling that there are 2271 open connections
mongodb-6b455c56fb-4lj56:2021-05-03T16:21:47.493+0000 I NETWORK  [conn1184792] end connection 10.247.145.228:40042 (2271 connections now open)

I was wondering what that number is on my system, so I greped my logs for connections now open, and this is what I got
2021-05-04T15:20:36.711+0000 I NETWORK  [conn1] end connection 127.0.0.1:36814 (0 connections now open)
2021-05-04T15:20:37.714+0000 I NETWORK  [conn2] end connection 127.0.0.1:36824 (0 connections now open)
2021-05-04T15:20:38.815+0000 I NETWORK  [conn3] end connection 127.0.0.1:36852 (0 connections now open)
2021-05-04T15:20:39.811+0000 I NETWORK  [conn4] end connection 127.0.0.1:36868 (0 connections now open)
2021-05-04T15:20:41.008+0000 I NETWORK  [conn5] end connection 127.0.0.1:36878 (0 connections now open)

I then started to kill the following pods:

api-service
shipyard-controller
mongodb-datastore

and I finally got some numbers popping up:
2021-05-04T15:44:01.029+0000 I NETWORK  [conn6] end connection 10.60.1.6:42622 (54 connections now open)
2021-05-04T15:44:01.029+0000 I NETWORK  [conn15] end connection 10.60.1.6:43578 (52 connections now open)
2021-05-04T15:44:01.029+0000 I NETWORK  [conn19] end connection 10.60.1.6:43724 (51 connections now open)
2021-05-04T15:44:01.029+0000 I NETWORK  [conn17] end connection 10.60.1.6:43628 (55 connections now open)
2021-05-04T15:44:01.029+0000 I NETWORK  [conn5] end connection 10.60.1.6:42624 (50 connections now open)
2021-05-04T15:44:01.030+0000 I NETWORK  [conn14] end connection 10.60.1.6:43528 (49 connections now open)
2021-05-04T15:44:01.029+0000 I NETWORK  [conn16] end connection 10.60.1.6:43608 (53 connections now open)
2021-05-04T15:44:01.030+0000 I NETWORK  [conn18] end connection 10.60.1.6:43716 (48 connections now open)
2021-05-04T15:44:07.789+0000 I NETWORK  [conn38] end connection 10.60.3.7:59014 (47 connections now open)
2021-05-04T15:44:07.789+0000 I NETWORK  [conn1] end connection 10.60.3.7:51186 (27 connections now open)
2021-05-04T15:44:07.789+0000 I NETWORK  [conn36] end connection 10.60.3.7:59012 (45 connections now open)
2021-05-04T15:44:07.789+0000 I NETWORK  [conn35] end connection 10.60.3.7:56876 (46 connections now open)
2021-05-04T15:44:07.789+0000 I NETWORK  [conn30] end connection 10.60.3.7:53524 (44 connections now open)
2021-05-04T15:44:07.789+0000 I NETWORK  [conn27] end connection 10.60.3.7:52428 (43 connections now open)
2021-05-04T15:44:07.789+0000 I NETWORK  [conn22] end connection 10.60.3.7:52412 (42 connections now open)
2021-05-04T15:44:07.789+0000 I NETWORK  [conn25] end connection 10.60.3.7:52426 (41 connections now open)
2021-05-04T15:44:07.789+0000 I NETWORK  [conn28] end connection 10.60.3.7:52432 (40 connections now open)
2021-05-04T15:44:07.789+0000 I NETWORK  [conn31] end connection 10.60.3.7:53526 (38 connections now open)
2021-05-04T15:44:07.789+0000 I NETWORK  [conn26] end connection 10.60.3.7:52430 (39 connections now open)
2021-05-04T15:44:07.789+0000 I NETWORK  [conn37] end connection 10.60.3.7:59010 (36 connections now open)
2021-05-04T15:44:07.789+0000 I NETWORK  [conn23] end connection 10.60.3.7:52422 (37 connections now open)
2021-05-04T15:44:07.789+0000 I NETWORK  [conn20] end connection 10.60.3.7:52408 (35 connections now open)
2021-05-04T15:44:07.789+0000 I NETWORK  [conn21] end connection 10.60.3.7:52406 (34 connections now open)
2021-05-04T15:44:07.789+0000 I NETWORK  [conn24] end connection 10.60.3.7:52424 (33 connections now open)
2021-05-04T15:44:07.789+0000 I NETWORK  [conn29] end connection 10.60.3.7:53522 (32 connections now open)
2021-05-04T15:44:07.789+0000 I NETWORK  [conn7] end connection 10.60.3.7:51222 (31 connections now open)
2021-05-04T15:44:07.789+0000 I NETWORK  [conn4] end connection 10.60.3.7:51204 (30 connections now open)
2021-05-04T15:44:07.789+0000 I NETWORK  [conn3] end connection 10.60.3.7:51202 (29 connections now open)
2021-05-04T15:44:07.789+0000 I NETWORK  [conn2] end connection 10.60.3.7:51188 (28 connections now open)

This is now looking much more like there are some open connections that are never closed, which would lead to the aforementioned error on mongodb.

After killing remediation-service it seems that a lot of connections were closed. I will monitor that situation.

Still not sure if remedation-service is where the problem comes from, but there sure as hell is a memory-leak / connection-leak for MongoDB in remediation-service.
The connection-leak can be seen by looking at the logs of remediation-service and mongodb, the memory leak can be seen by looking at goroutine count:

One of the pods must be starting to behave weird now:

@donovanmuller I am unable to reproduce the exact error that you are reporting.
SCRAM-SHA-1 authentication failed, storedKey mismatch

I believe that mongodb is crashing (which I was able to reproduce), and the error you are seeing is just a symptom of the crash.
One thing that could verify this is if you do the following:
$ kubectl -n keptn describe pod mongodb-6967b65894-hb6c5 # replace with your pod name

and look for container infos, e.g.:
Containers:
  mongodb:
    Container ID:   docker://ab61238b46c08f2762589d2279296fbd42ed6e2b36ea6a107a03bec3b74ab360
    Image:          docker.io/centos/mongodb-36-centos7:1
    Image ID:       docker-pullable://centos/mongodb-36-centos7@sha256:c93e5ea16ba6c2637e16d753a4c4128a99a09ee23a7c338694132eb2ca46d9ad
    Port:           27017/TCP
    Host Port:      0/TCP
    State:          Running
      Started:      Wed, 05 May 2021 10:52:27 +0200
    Last State:     Terminated
      Reason:       OOMKilled
      Exit Code:    137
      Started:      Wed, 05 May 2021 10:41:18 +0200
      Finished:     Wed, 05 May 2021 10:52:25 +0200
    Ready:          True
    Restart Count:  9

Here I can see that it was last killed because of OOMKilled, and that it has 9 restarts.

@christian-kreuzberger-dtx unfortunately don't have the time right now to dig in deeper but all I can say is that a cluster scaling event seems to trigger the behaviour in most cases. I.e. whenever a node is added/removed and the mongo Pods are moved around, this issue comes up for me.

We will keep an eye on this, but so far we haven't been able to reproduce it. I will close the issue for now.

As a follow up to this issue. I kept experiencing the same issue as described initially. In my case it was always seemed to be related to a cluster autoscaling event where the Keptn MongoDB Pod would be rescheduled into another node etc.
I Googled a bit more and found this specific https://github.com/bitnami/bitnami-docker-mongodb/issues/159 on the bitnami-docker-mongodb image. It seemed very related to the issue I was experiencing, so I decided to replace the Keptn provided Mongo Helm Chart with the Bitnami Chart.
Suffice to say I have not had this issue since deploying the Bitnami MongoDB Chart. Not sure if there is any further action but leaving this comment here for posterity.

Thanks, I will create a follow-up issue suggesting to change to the bitnami mongodb container for this reason.

authors: christian-kreuzberger-dtx donovanmuller


text:
#1881 Send action started before doing scaling

Implements https://github.com/keptn/keptn/issues/1881.
This PR implements the sending of an action.started event in the scaling action.

Codecov Report

Merging #1889 into master will decrease coverage by 0.04%.
The diff coverage is 6.66%.

@@            Coverage Diff             @@
##           master    #1889      +/-   ##
==========================================
- Coverage   32.21%   32.17%   -0.05%
==========================================
  Files          99       99
  Lines        7673     7680       +7
==========================================
- Hits         2472     2471       -1
- Misses       4883     4891       +8
  Partials      318      318

Impacted Files
Coverage Δ

api/handlers/configure.go
12.71% <0.00%> (ø)

helm-service/controller/action_handler.go
41.89% <7.69%> (-2.79%)
:arrow_down:

Continue to review full report at Codecov.

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

authors: agrimmer codecov-commenter


text:
SparseKerasTensor loses shape after casting

Please go to TF Forum for help and support:
https://discuss.tensorflow.org/tag/keras
If you open a GitHub issue, here is our policy:
It must be a bug, a feature request, or a significant problem with the documentation (for small docs fixes please send a PR instead).
The form below must be filled out.
Here's why we have that policy:.
Keras developers respond to issues. We want to focus on work that benefits the whole community, e.g., fixing bugs and adding features. Support only helps individuals. GitHub also notifies thousands of people when issues are filed. We want them to see you communicating an interesting problem, rather than being redirected to Stack Overflow.
System information.

Have I written custom code (as opposed to using a stock example script provided in Keras): Yes
OS Platform and Distribution (e.g., Linux Ubuntu 16.04): Multiple, checked on Linux Ubuntu 18.04.6 LTS and MacOS 12.2.1 (21D62)
TensorFlow installed from (source or binary): binary
TensorFlow version (use command below): Multiple, checked on 2.5, 2.6 and v2.8.0-rc1-32-g3f878cff5b6 2.8.0
Python version: Multiple, checked on 3.6.9 and 3.8.2
Bazel version (if compiling from source): NA
GPU model and memory: NA
Exact command to reproduce: tf.cast(tf.keras.Input(3, 3, sparse=True, dtype=tf.bool), tf.int32).shape

You can collect some of this information using our environment capture script:
https://github.com/tensorflow/tensorflow/tree/master/tools/tf_env_collect.sh
You can obtain the TensorFlow version with:
python -c "import tensorflow as tf; print(tf.version.GIT_VERSION, tf.version.VERSION)"
Describe the problem.
Describe the problem clearly here. Be sure to convey here why it's a bug in Keras or why the requested feature is needed.
Describe the current behavior.
The problem is the shape of the symbolic sparse tensor is lost and set to None after casting.
>>> a.shape
TensorShape([3, 3])
>>> b.shape
TensorShape([None, None])

Describe the expected behavior.
The shape should be preserved after casting.
Contributing.

Do you want to contribute a PR? (yes/no): no
If yes, please read this page for instructions
Briefly describe your candidate solution(if contributing):

Standalone code to reproduce the issue.
Provide a reproducible test case that is the bare minimum necessary to generate
the problem. If possible, please share a link to Colab/Jupyter/any notebook.
a = tf.keras.Input(3, 3, dtype=tf.bool, sparse=True)
b = tf.cast(a, dtype=tf.int32)
assert a.shape == b.shape, \
    f"a.shape ({a.shape} is different from b.shape ({b.shape}))"

Colab link
Source code / logs.
Include any logs or source code that would be helpful to diagnose the problem. If including tracebacks, please include the full traceback. Large logs and files should be attached. Try to provide a reproducible test case that is the bare minimum necessary to generate the problem.
NA

Possible solution:
Replace x.dense_shape with x.get_shape() in tensorflow.python.ops.maths_ops::cast:
x = sparse_tensor.SparseTensor(x.indices, values_cast, x.dense_shape)

would be replaced with:
x = sparse_tensor.SparseTensor(x.indices, values_cast, x.get_shape())

@chunduriv ,
I was able to reproduce the issue in tf v2.7, v2.8 and nightly.Please find the gist of it here.

authors: sergiovalmac tilakrayal

repo: keras-team/keras


text:
Custom Constraints in Keras layers

Hello Everyone,
I want to add custom constraints on the weights of a layer. For example, I want to impose sparsity constraints on the weights of a layer. Is there a way to write our own custom constraints while learning the weight parameters of a layer. I could not find much documentation on keras docs for constraints.

I'm also looking to implement the same. Is there any way to do this?

Hi!
Look at how in-built constraints are implemented:
https://github.com/keras-team/keras/blob/master/keras/constraints.py
I think you can also create a class inheriting from Constraint:
from keras.constraints import Constraint

class CustomConstraint (Constraint):
    def __init__(self, your, parameters, go, here):
        self. your = your
        self. parameters = parameters
        .....

    def __call__(self, w):
        new_w = write_your_custom_transformations_here(w)
        return new_w

And then use CustomConstraint in the same way as in-built:
model.add(Dense(64, kernel_constraint= CustomConstraint(your', parameters', go', here')))
Hope this helps :)

@kochkinaelena In a bidirectional wrapper, can we use two separate custom kernel constraints: one for the forward layer and other for backward layer?

Hi,
I don't think you can easily plug in two different kernel constraints into bidirectional wrapper, but you could use two RNN layers of your choice (one of which goes backwards) and then merge them in the way you want, e.g:
  layer1 = LSTM(64, kernel_constraint= CustomConstraint1, go_backwards=False)(layer0)
  layer2 = LSTM(64, kernel_constraint= CustomConstraint2, go_backwards=True)(layer0)
  layer3 = keras.layers.add([layer1, layer2])

This method doesn't work for the LSTM layer. Same CustomConstraint when used for Dense layer works but for LSTm gives error 'Unknown Constraint'. Anybody facing similar problems?

This method doesn't work for the LSTM layer. Same CustomConstraint when used for Dense layer works but for LSTm gives error 'Unknown Constraint'. Anybody facing similar problems?

Hey @prakharg24, did you figure this out? I'm facing this issue in TF2-Keras with a Dense Layer!


text:
Segfault

This looks very interesting, but I'm unable to successfully run the example. I modified the trainData, testData, and logFile paths of the config file appropriately. Valgrind reports this:
==12259== Memcheck, a memory error detector
==12259== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al.
==12259== Using Valgrind-3.15.0 and LibVEX; rerun with -h for copyright info
==12259== Command: ./runme Config_amz.csv
==12259==
new Network
==12259== Invalid write of size 4
==12259==    at 0x10F124: Network::Network(int*, NodeType*, int, int, float, int, int*, int*, int*, float*, std::map<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >, cnpy::NpyArray, std::less<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > >, std::allocator<std::pair<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const, cnpy::NpyArray> > >) (Network.cpp:13)
==12259==    by 0x10D01E: main (main.cpp:472)
==12259==  Address 0xb is not stack'd, malloc'd or (recently) free'd

Apologize for the late reply! The team just got back from the conference. We'd happy to help. As mentioned in the README: "Additionally, Transparent Huge Pages must be enabled. SLIDE requires approximately 900 2MB pages, and 10 1GB pages. (https://wiki.debian.org/Hugepages)"
May I ask if you that is enabled?

I have similar issue:
./runme Config_amz.csv
new Network
new Layer
new Node array
Illegal instruction (core dumped)

I reversed to  2d10d46 and then I was able to run the experiment.
My TPH configuration:
hugeadm --pool-list
      Size  Minimum  Current  Maximum  Default
   2097152     1000     1000     1000        *
1073741824       20       20       20

TL;DR on my Ubuntu 19.10 machine I added:
transparent_hugepage=always hugepagesz=1GB hugepages=10 hugepagesz=2MB hugepages=900
to GRUB_CMDLINE_LINUX_DEFAULT in /etc/default/grub. Then update-grub and reboot. You can verify with cat /sys/kernel/mm/transparent_hugepage/enabled and hugeadm --pool-list.

Note: mmap returns -1 on error, the current code checks for NULL:
https://github.com/keroro824/HashingDeepLearning/blob/b7b3bba9bab1fb0e70de7644daa9e2312f21de82/SLIDE/Layer.h#L58

@yvdriess  This should be resolved in the pull request #22.

TL;DR on my Ubuntu 19.10 machine I added:
transparent_hugepage=always hugepagesz=1GB hugepages=10 hugepagesz=2MB hugepages=900
to GRUB_CMDLINE_LINUX_DEFAULT in /etc/default/grub. Then update-grub and reboot. You can verify with cat /sys/kernel/mm/transparent_hugepage/enabled and hugeadm --pool-list.

so sorry to interrupt, but I could not find the grub file, should I create one in the location /etc/default/grub ?

Hi,
Im sorry but I don't know why you are missing this file if you have a recent Ubuntu. Perhaps running the update grub command would restore it.
Best regards,
Jose

From: One-punch24 notifications@github.com
Sent: Monday, November 2, 2020 7:26 PM
To: keroro824/HashingDeepLearning HashingDeepLearning@noreply.github.com
Cc: Jose Lopez lopez.jo@northeastern.edu; Comment comment@noreply.github.com
Subject: Re: [keroro824/HashingDeepLearning] Segfault (#6)
TL;DR on my Ubuntu 19.10 machine I added:
transparent_hugepage=always hugepagesz=1GB hugepages=10 hugepagesz=2MB hugepages=900
to GRUB_CMDLINE_LINUX_DEFAULT in /etc/default/grub. Then update-grub and reboot. You can verify with cat /sys/kernel/mm/transparent_hugepage/enabled and hugeadm --pool-list.
so sorry to interrupt, but I could not find the grub file, should I create one in the location /etc/default/grub ?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHubhttps://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fkeroro824%2FHashingDeepLearning%2Fissues%2F6%23issuecomment-720884472&data=04|01|lopez.jo%40northeastern.edu|558d265d7a3545a9649008d87fa84628|a8eec281aaa34daeac9b9a398b9215e7|0|0|637399707993220673|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=a4g8w7krqWS0fJa%2F5rcswaG9aY%2Bp4WPcz6LXbF8poYs%3D&reserved=0, or unsubscribehttps://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAE3WNBV7HK555A4HKBRE333SN5Z63ANCNFSM4K75GGGA&data=04|01|lopez.jo%40northeastern.edu|558d265d7a3545a9649008d87fa84628|a8eec281aaa34daeac9b9a398b9215e7|0|0|637399707993220673|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=5umWRaYJubP%2B%2BZ6wDWVPNs3EfA9Cfp4yvO4BBtxIWIY%3D&reserved=0.

Thank you so much for replaying. I am a little bit busy these days for some exams.
 Can I consult you later? I was so happy and amazed that you answer me so
------------------ 原始邮件 ------------------
发件人:                                                                                "keroro824/HashingDeepLearning"                                                                                <notifications@github.com>;
发送时间: 2020年11月10日(星期二) 凌晨0:12
收件人: "keroro824/HashingDeepLearning"<HashingDeepLearning@noreply.github.com>;
抄送: "1482806551"<1482806551@qq.com>;"Comment"<comment@noreply.github.com>;
主题: Re: [keroro824/HashingDeepLearning] Segfault (#6)
Hi,
Im sorry but I don't know why you are missing this file if you have a recent Ubuntu. Perhaps running the update grub command would restore it.
Best regards,
Jose

From: One-punch24 <notifications@github.com>
Sent: Monday, November 2, 2020 7:26 PM
To: keroro824/HashingDeepLearning <HashingDeepLearning@noreply.github.com>
Cc: Jose Lopez <lopez.jo@northeastern.edu>; Comment <comment@noreply.github.com>
Subject: Re: [keroro824/HashingDeepLearning] Segfault (#6)
TL;DR on my Ubuntu 19.10 machine I added:
transparent_hugepage=always hugepagesz=1GB hugepages=10 hugepagesz=2MB hugepages=900
to GRUB_CMDLINE_LINUX_DEFAULT in /etc/default/grub. Then update-grub and reboot. You can verify with cat /sys/kernel/mm/transparent_hugepage/enabled and hugeadm --pool-list.
so sorry to interrupt, but I could not find the grub file, should I create one in the location /etc/default/grub ?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub<https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fkeroro824%2FHashingDeepLearning%2Fissues%2F6%23issuecomment-720884472&data=04%7C01%7Clopez.jo%40northeastern.edu%7C558d265d7a3545a9649008d87fa84628%7Ca8eec281aaa34daeac9b9a398b9215e7%7C0%7C0%7C637399707993220673%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=a4g8w7krqWS0fJa%2F5rcswaG9aY%2Bp4WPcz6LXbF8poYs%3D&reserved=0>, or unsubscribe<https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAE3WNBV7HK555A4HKBRE333SN5Z63ANCNFSM4K75GGGA&data=04%7C01%7Clopez.jo%40northeastern.edu%7C558d265d7a3545a9649008d87fa84628%7Ca8eec281aaa34daeac9b9a398b9215e7%7C0%7C0%7C637399707993220673%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=5umWRaYJubP%2B%2BZ6wDWVPNs3EfA9Cfp4yvO4BBtxIWIY%3D&reserved=0>.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or unsubscribe.

I seemed to have solved this problem but still got segment fault. I really want to consult you later to solve some strange problem.
Thank you for your help again! You are a nice person treating my problem so seriously.
------------------ 原始邮件 ------------------
发件人:                                                                                "keroro824/HashingDeepLearning"                                                                                <notifications@github.com>;
发送时间: 2020年11月10日(星期二) 凌晨0:12
收件人: "keroro824/HashingDeepLearning"<HashingDeepLearning@noreply.github.com>;
抄送: "1482806551"<1482806551@qq.com>;"Comment"<comment@noreply.github.com>;
主题: Re: [keroro824/HashingDeepLearning] Segfault (#6)
Hi,
Im sorry but I don't know why you are missing this file if you have a recent Ubuntu. Perhaps running the update grub command would restore it.
Best regards,
Jose

From: One-punch24 <notifications@github.com>
Sent: Monday, November 2, 2020 7:26 PM
To: keroro824/HashingDeepLearning <HashingDeepLearning@noreply.github.com>
Cc: Jose Lopez <lopez.jo@northeastern.edu>; Comment <comment@noreply.github.com>
Subject: Re: [keroro824/HashingDeepLearning] Segfault (#6)
TL;DR on my Ubuntu 19.10 machine I added:
transparent_hugepage=always hugepagesz=1GB hugepages=10 hugepagesz=2MB hugepages=900
to GRUB_CMDLINE_LINUX_DEFAULT in /etc/default/grub. Then update-grub and reboot. You can verify with cat /sys/kernel/mm/transparent_hugepage/enabled and hugeadm --pool-list.
so sorry to interrupt, but I could not find the grub file, should I create one in the location /etc/default/grub ?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub<https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fkeroro824%2FHashingDeepLearning%2Fissues%2F6%23issuecomment-720884472&data=04%7C01%7Clopez.jo%40northeastern.edu%7C558d265d7a3545a9649008d87fa84628%7Ca8eec281aaa34daeac9b9a398b9215e7%7C0%7C0%7C637399707993220673%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=a4g8w7krqWS0fJa%2F5rcswaG9aY%2Bp4WPcz6LXbF8poYs%3D&reserved=0>, or unsubscribe<https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAE3WNBV7HK555A4HKBRE333SN5Z63ANCNFSM4K75GGGA&data=04%7C01%7Clopez.jo%40northeastern.edu%7C558d265d7a3545a9649008d87fa84628%7Ca8eec281aaa34daeac9b9a398b9215e7%7C0%7C0%7C637399707993220673%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=5umWRaYJubP%2B%2BZ6wDWVPNs3EfA9Cfp4yvO4BBtxIWIY%3D&reserved=0>.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or unsubscribe.

Is code run, I have killed problem  ???

@jlopezNEU
Is code work now or not?


text:
HA log errors ref 2025.1

Version of the custom_component
Latest version
Describe the bug
Hi,
I just saw some errors in the HA logbook referring to 2025.1.
I guess it's just a remark for future incompatibility as from the 2025.1 CORE release, so nothing urgent :-)
Erros in log:

Thanks!

Hi kesteraernoudt,
i was wondering if you still intend to address the issue reported by timvdsm, i also noticed some additional warnings in my log about deprecated supported features values which will be removed in HA Core.
i'm not sure how timvdsm was able to present them this nicely, i uploaded the log file with the warnings:
home-assistant_2024-12-26T19-39-24.371Z.log
I hope you find some time to address it sometime, i really appeciate your work!
Cheers!

I'll see if I can find a solution for these. Problem is that I don't have a dobiss installation any more to test things out. I do welcome pull requests btw if you or someone else would have done some work on this!

authors: Eightball1990 kesteraernoudt timvdsm

repo: kesteraernoudt/dobiss


text:
feat(gcp): allow ability to impersonate a service account

What changes are being made and why?
This change allows GCP tasks to be run by impersonating another service account, reasons for this could include

Enhanced Security with Least Privilege Access
Delegated and Scoped Access Control
Temporary Access with Auditing
Simplifying Resource Access in Multi-Project Environments

Thinking about how to structure this, we could change serviceAccount from a String to a HashMap and have key and impersonate keys
serviceAccount:
    key: "{{ secret('GCP_SERVICE_ACCOUNT') }}"
    impersonate: target-sa@email.com

If you do not want to impersonate a service account then do not include the impersonate key.

How the changes have been QAed?
id: gcp_gcs_list
namespace: company.team

tasks:
  - id: list
    type: io.kestra.plugin.gcp.gcs.List
    serviceAccount:
        key: "{{ secret('GCP_SERVICE_ACCOUNT') }}"
        impersonate: target-sa@email.com
    from: "gs://my_bucket/dir/"

I'm not sure of the best way to go about testing this - if guidance can be provided I'm happy to take it on.

Setup Instructions
In order to make this work you will need two service accounts setup and allow the main service account to impersonate the other, documentation on this can be found here. Below is an example gcloud command
gcloud iam service-accounts add-iam-policy-binding TARGET_SERVICE_ACCOUNT_EMAIL \
    --role="roles/iam.serviceAccountTokenCreator" \
    --member="serviceAccount:SOURCE_SERVICE_ACCOUNT_EMAIL" \
    --project=YOUR_PROJECT_ID

A good example may be to give one service account no GCS ObjectViewer role but give it to the other one, then the above task would be a good test, as running without impersonate should not work but providing it should then make the task work
I have never touched Java before so this is completely new to me, I think the formatting I'm using may be different to what is being used in the repo as well 🤦.
There will be lots of other places to change references to service account, including any examples, but wanted to get feedback on the concept before tackling that
closes #452

@loicmathieu - thanks for the feedback.
I think having a separate property for the impersonated account works well. I'll rework the PR to reflect this.
I've also worked out how to build the develop docker image with local plugins so will be able to test the changes in more detail

@loicmathieu - I have made the requested changes, creating a separate property for impersonated service account.
I have tested by adding the plugin to latest develop docker image and running the following flow, which runs successfully. The service account does not have storage permissions but the impersonated account does
id: impersonate
namespace: test

tasks:
  - id: create_bucket
    type: io.kestra.plugin.gcp.gcs.CreateBucket
    projectId: "poppy-demo"
    serviceAccount: "{{ read('demo-sa.json') }}"
    impersonatedServiceAccount: "storage-account@demo.iam.gserviceaccount.com"
    name: "kestra-test-bucket-creation"

In order to setup the impersonated account you need to do the following

Enable the IAM Service Account Credentials API
On the service account to be impersonated grant access to the base service account giving it the Service Account Token Creator permission. This allows the base service account to create short live tokens for the impersonated account

repo: kestra-io/plugin-gcp


text:
io.kestra.plugin.kubernetes.PodCreate metadata.name - assigning a name to the Kubernetes Pod

Feature description
Currently when using plugin-kubernetes PodCreate task, then it is impossible to assign a custom name to the Pod created in Kubernetes. It is possible to assign a name to the containers within that Pod, but not to the Pod itself.
Documentation under metadata definition includes the possibility of assigning a name (as per k8s spec), but this will be overriden by AbstractConnection.java L95.
Could it be considered, that when a Pod name is passed from the metadata.name configuration, then it is used instead of a generated name?
Use case: we have a standard way of naming Pods in Kubernetes and since the executions are not dropped, we prefer a better naming scheme.

it seems feasible, thx for the issue!

authors: anna-geller kriko

repo: kestra-io/plugin-kubernetes


text:
Windows: include hub devices in list like other platforms

I note there is mention of this in the docs but is it intended or just the nature of only using GUID_DEVINTERFACE_USB_DEVICE? Since importing GUID_DEVINTERFACE_USB_HUB for the list_buses, I realise that non-root hubs can be obtained with this too in the list_devices().
I believe it makes since to add it so hubs are included in the device list. If only because it makes Windows listing the same as the other platforms. I also think it makes sense as hub are devices and descriptors can be read, control messages used etc. unlike root hubs.

Yeah, this seems to work, so no reason to exclude them.

repo: kevinmehall/nusb


text:
Cache data presented as String and not Array

I apologies firstly as i am quite new to JSON
When i run the following line the first time with DECODE_ENABLED = TRUE;
$getGame = $testCache->getCurrentGame($summoner_id,OC1);
var_dump ($getGame);
It returns an array, but if i go and refresh the page it will return it as a string.
If i do the same thing again with DECODE_ENABLED = FALSE;
it returns a string both times.
Am i missing an option to decode from cache somewhere or am i making a silly mistake?

https://github.com/kevinohashi/php-riot-api/issues/42
I think might have solved this.

I am able to read code, but quite poor at writing so if this is wrong can someone please correct me.
I modified line 64 in FileSystemCache.php from
return json_decode(file_get_contents($this->getPath($key)));
to
return json_decode(file_get_contents($this->getPath($key)),true);
and it "seems" to be working.

It actually looks like a mistake in the library itself
	//returns a summoner's id
	public function getSummonerId($name) {
			$name = strtolower($name);
			$summoner = $this->getSummonerByName($name);
			if (self::DECODE_ENABLED) {
				return $summoner[$name]['id'];
			}
			else {
				$summoner = json_decode($summoner, true);
				return $summoner[$name]['id'];
			}
	}

the if and else should probably be reversed
	//returns a summoner's id
	public function getSummonerId($name) {
			$name = strtolower($name);
			$summoner = $this->getSummonerByName($name);
			if (!self::DECODE_ENABLED) {
				return $summoner[$name]['id'];
			}
			else {
				$summoner = json_decode($summoner, true);
				return $summoner[$name]['id'];
			}
	}

Does that fix the issue instead of having to add your own true?

Just testing

Let me know if that fixes it, I will patch the library :)

That seems to be working, i will have to play around some more as the site is still being created an a lot of stuff doesn't currently work.

Getting the same issue on
$getSummonerName = $testCache->getSummoner($summoner_id);
var_dump ($getSummonerName);

I really need to sit down one of these days and go through a bunch of fixes, it hasn't been well thought out lately. I haven't had the time to do everything right.
It shouldn't need DECODE_ENABLED checks anywhere. It's done in request(). All those other ones should be redundant. But if it's not working right, I need to really take a deeper look.

honestly, it could just be me..

it could be, but I haven't had the time to maintain this library as well I should lately. I am looking through it and it's me quickly patching stuff and not really fully thinking about the design and structure. Even if it's just you, I need to sit down for a day and just clean the whole thing up.

Is there any way i would be able to assist you with this?

I appreciate the offer, if you want to look through and see what you think is wrong, how you would change it, I'm always open to help and ideas

I also noticed that.
You can fix it by deleting the ifs where it checks for "self:DECODE_ENABLED" on "request" method, and then add one of those at the end of the "request" method, so you check if you need to decode just before you return the $result.
It would look like this:
´´´php
if (self::DECODE_ENABLED) {
return json_decode($result, true);
}
return $result;
´´´

authors: Krayt1x kevinohashi sylven

repo: kevinohashi/php-riot-api


text:
Why is Elephant-Bird offering its own LZO Input/Output Formats?

Kevin's project "hadoop-lzo" (Which EB depends on anyway) already offers LZO I/O formats for Text, etc. - just not protobuf.
Why does EB choose to maintain a forked copy?
Would it be acceptable if I contributed a patch that makes EB classes extend the hadoop-lzo one (with tests to ensure we not break users of it)?
Some users of EB classes reported that it does not properly gel with Hive's CombineHiveInputFormat usage (which is now the default I/F).
For the same, simple "README.lzo" text file input that spans four blocks (worth 512 bytes each):
hive> describe extended lzoblocks;
OK
r	string
Detailed Table Information	Table(tableName:lzoblocks, dbName:default, owner:root, createTime:1329727318, lastAccessTime:0, retention:0, sd:StorageDescriptor(cols:[FieldSchema(name:r, type:string, comment:null)], location:hdfs://localhost/user/hive/warehouse/lzoblocks, inputFormat:com.hadoop.mapred.DeprecatedLzoTextInputFormat, outputFormat:org.apache.hadoop.hive.ql.io.HiveIgnoreKeyTextOutputFormat, compressed:false, numBuckets:-1, serdeInfo:SerDeInfo(name:null, serializationLib:org.apache.hadoop.hive.serde2.lazy.LazySimpleSerDe, parameters:{serialization.format=1}), bucketCols:[], sortCols:[], parameters:{}), partitionKeys:[], parameters:{transient_lastDdlTime=1329727393}, viewOriginalText:null, viewExpandedText:null, tableType:MANAGED_TABLE)
Time taken: 0.078 seconds
hive> describe extended ebblocks;
OK
r	string
Detailed Table Information	Table(tableName:ebblocks, dbName:default, owner:root, createTime:1329730707, lastAccessTime:0, retention:0, sd:StorageDescriptor(cols:[FieldSchema(name:r, type:string, comment:null)], location:hdfs://localhost/user/hive/warehouse/ebblocks, inputFormat:com.twitter.elephantbird.mapred.input.DeprecatedLzoTextInputFormat, outputFormat:org.apache.hadoop.hive.ql.io.HiveIgnoreKeyTextOutputFormat, compressed:false, numBuckets:-1, serdeInfo:SerDeInfo(name:null, serializationLib:org.apache.hadoop.hive.serde2.lazy.LazySimpleSerDe, parameters:{serialization.format=1}), bucketCols:[], sortCols:[], parameters:{}), partitionKeys:[], parameters:{transient_lastDdlTime=1329732671}, viewOriginalText:null, viewExpandedText:null, tableType:MANAGED_TABLE)
Time taken: 0.07 seconds
Doing a simple select of the hadoop-lzo class based table works fine, while the latter fails - when used with CDH3u3. The error the ebblocks table gets on a select * is [0].
This may be MAPREDUCE-1597 but I still think EB should be reusing classes rather than duplicating code and diverging in behavior.
[0] - 2012-02-17 11:04:07,598 WARN com.hadoop.compression.lzo.LzopInputStream: IOException in getCompressedData; likely LZO corruption.
java.io.IOException: Compressed length 439750499 exceeds max block size 67108864 (probably corrupt file)
at com.hadoop.compression.lzo.LzopInputStream.getCompressedData(LzopInputStream.java:285)
at com.hadoop.compression.lzo.LzopInputStream.decompress(LzopInputStream.java:255)
at org.apache.hadoop.io.compress.DecompressorStream.read(DecompressorStream.java:75)
at org.apache.hadoop.io.compress.DecompressorStream.read(DecompressorStream.java:63)
at com.twitter.elephantbird.util.StreamSearcher.search(StreamSearcher.java:47)
at com.twitter.elephantbird.mapreduce.io.BinaryBlockReader.skipToNextSyncPoint(BinaryBlockReader.java:102)
at com.twitter.elephantbird.mapreduce.io.BinaryBlockReader.parseNextBlock(BinaryBlockReader.java:107)
at com.twitter.elephantbird.mapreduce.io.BinaryBlockReader.setupNewBlockIfNeeded(BinaryBlockReader.java:139)
at com.twitter.elephantbird.mapreduce.io.BinaryBlockReader.readNextProtoBytes(BinaryBlockReader.java:75)
at com.twitter.elephantbird.mapreduce.io.BinaryBlockReader.readNext(BinaryBlockReader.java:63)
at com.twitter.elephantbird.mapreduce.io.ProtobufBlockReader.readProtobuf(ProtobufBlockReader.java:42)
at com.twitter.elephantbird.mapred.input.DeprecatedLzoProtobufBlockRecordReader.next(DeprecatedLzoProtobufBlockRecordReader.java:84)
at com.twitter.elephantbird.mapred.input.DeprecatedLzoProtobufBlockRecordReader.next(DeprecatedLzoProtobufBlockRecordReader.java:27)
at org.apache.hadoop.hive.ql.io.CombineHiveRecordReader.doNext(CombineHiveRecordReader.java:98)
at org.apache.hadoop.hive.ql.io.CombineHiveRecordReader.doNext(CombineHiveRecordReader.java:42)
at org.apache.hadoop.hive.ql.io.HiveContextAwareRecordReader.next(HiveContextAwareRecordReader.java:67)
at org.apache.hadoop.hive.shims.Hadoop20SShims$CombineFileRecordReader.next(Hadoop20SShims.java:208)
at org.apache.hadoop.mapred.MapTask$TrackedRecordReader.moveToNext(MapTask.java:208)

yes, EB's LzoInputFormat (not LzoInputStream) has diverged from hadoop-lzo and is in heavy production use.
EB's LzoInputFormat should be ported over to hadoop-lzo and not the otherway round. EB has evolved to lot more than LzoInputFormat.. We are going to make hadoop-lzo a soft dependency (ie. EB works with other file formats gzip, bz2, seqfiles, rcfiles etc) so that EB could be free from GPL restrictions from hadoop-lzo.
That said, the error you are seeing does not look like it is related to EB. I would be very surprised if you don't see this error with hadoop-lzo alone. lzo files are not splittable unless you have README.lzo.index file, even then, the splits have to be adjusted.

The issue comes up due to Hive's use of CombineFileInputFormat (it splits the inputs even if splitting has been disabled, which is the case when there aren't indexes).
I can't reproduce it if I use the hadoop-lzo version, but I haven't yet determined which bit of the diff makes the difference. Its probably the parts around getSplits() and isSplitable(), as thats where differences seem to lie. But yes, the real bug is MAPREDUCE-1597, am only curious why hadoop-lzo did not trigger that and that made me file this issue.
So we should be porting and maintaining, or deprecating the MR bits on hadoop-lzo and asking folks to use EB?

I would say yes. Use EB, looks like just hadoop-lzo is not enough for you anyway. In future EB starts using LzoInputFormat from hadoop-lzo, it will be transparent to you..

authors: QwertyManiac rangadi

repo: kevinweil/elephant-bird


text:
🛑 FX blog (kty) is down

In e34be51, FX blog (kty) (https://foxter-blogeditor.konecty.com) was down:

HTTP code: 0
Response time: 0 ms

Resolved: FX blog (kty) is back up in 4748268 after 5 minutes.

repo: keviocastro/upptime


text:
🛑 FX corretor (kty) is down

In 2276764, FX corretor (kty) (https://corretores.foxterciaimobiliaria.com.br) was down:

HTTP code: 0
Response time: 0 ms

Resolved: FX corretor (kty) is back up in a015bf2 after 25 minutes.


text:
🛑 FX corretor (kty) is down

In 6e7cd30, FX corretor (kty) (https://corretores.foxterciaimobiliaria.com.br) was down:

HTTP code: 0
Response time: 0 ms

Resolved: FX corretor (kty) is back up in f193bd9 after 6 minutes.


text:
🛑 FX corretor (kty) is down

In 19d8344, FX corretor (kty) (https://corretores.foxterciaimobiliaria.com.br) was down:

HTTP code: 0
Response time: 0 ms

Resolved: FX corretor (kty) is back up in b9b621c after 6 minutes.


text:
⚠ AVS (kty) has degraded performance

In 5e21f39, AVS (kty) (https://avus.com.br) experienced degraded performance:

HTTP code: 200
Response time: 8855 ms

Resolved: AVS (kty) performance has improved in a0aee84.


text:
🛑 FX corretor (kty) is down

In 50f6ab0, FX corretor (kty) (https://corretores.foxterciaimobiliaria.com.br) was down:

HTTP code: 0
Response time: 0 ms

Resolved: FX corretor (kty) is back up in 9419025 after 9 minutes.


text:
🛑 FX blog (kty) is down

In d4cd952, FX blog (kty) (https://foxter-blogeditor.konecty.com) was down:

HTTP code: 0
Response time: 0 ms

Resolved: FX blog (kty) is back up in 32efeeb after 13 minutes.


text:
🛑 FX corretor (kty) is down

In d18a8a6, FX corretor (kty) (https://corretores.foxterciaimobiliaria.com.br) was down:

HTTP code: 0
Response time: 0 ms

Resolved: FX corretor (kty) is back up in 593a12a after 37 minutes.


text:
🛑 FX corretor (kty) is down

In 099d4d9, FX corretor (kty) (https://corretores.foxterciaimobiliaria.com.br) was down:

HTTP code: 0
Response time: 0 ms

Resolved: FX corretor (kty) is back up in 56149d4 after 36 minutes.


text:
🛑 FX corretor (kty) is down

In bffe970, FX corretor (kty) (https://corretores.foxterciaimobiliaria.com.br) was down:

HTTP code: 0
Response time: 0 ms

Resolved: FX corretor (kty) is back up in 14a7f45 after 24 minutes.


text:
🛑 FX blog (kty) is down

In bca7874, FX blog (kty) (https://foxter-blogeditor.konecty.com) was down:

HTTP code: 0
Response time: 0 ms

Resolved: FX blog (kty) is back up in 2f7f842 after 6 minutes.


text:
🛑 FX blog (kty) is down

In fc638fc, FX blog (kty) (https://foxter-blogeditor.konecty.com) was down:

HTTP code: 0
Response time: 0 ms

Resolved: FX blog (kty) is back up in 463fad1 after 10 minutes.


text:
🛑 FX blog (kty) is down

In a9f97d1, FX blog (kty) (https://foxter-blogeditor.konecty.com) was down:

HTTP code: 0
Response time: 0 ms

Resolved: FX blog (kty) is back up in a6a06fe after 8 minutes.


text:
🛑 FX blog (kty) is down

In 2c2b5b6, FX blog (kty) (https://foxter-blogeditor.konecty.com) was down:

HTTP code: 0
Response time: 0 ms

Resolved: FX blog (kty) is back up in 9471dfd after 44 minutes.


text:
🛑 FX net (kty) is down

In 9b5cdcf, FX net (kty) (https://foxter.net.br) was down:

HTTP code: 0
Response time: 0 ms

Resolved: FX net (kty) is back up in d3890e9.


text:
🛑 Ciscontinuum api is down

In 2e009f0, Ciscontinuum api (https://api.ciscontinuum.com.br) was down:

HTTP code: 503
Response time: 212 ms

Resolved: Ciscontinuum api is back up in 208b143.


text:
🛑 FX blog (kty) is down

In 17fb589, FX blog (kty) (https://blog.foxterciaimobiliaria.com.br) was down:

HTTP code: 503
Response time: 394 ms

Resolved: FX blog (kty) is back up in debffb8 after .


text:
🛑 FX corretor (kty) is down

In 2fe5b9b, FX corretor (kty) (https://corretores.foxterciaimobiliaria.com.br) was down:

HTTP code: 0
Response time: 0 ms

Resolved: FX corretor (kty) is back up in 48fa228 after 6 minutes.


text:
Added 512kb.club

This PR is:

[x] Adding a new domain
[ ] Updating existing domain size
[ ] Changing domain name
[ ] Removing existing domain from list
[ ] Website code changes (512kb.club site)
[ ] Other not listed

[x] I used the uncompressed size of the site
[x] I have included a link to the GTMetrix report
[ ] The domain is in the correct alphabetical order
[x] This site is not a ultra lightweight site
[x] The following information is filled identical to the data file

I confirm that I have read the FAQ section, particularly the two red items around minimal pages and inappropriate content and I attest that this site is neither of these things.

[x] Check to confirm

- domain: 512kb.club
  url: https://512kb.club/
  size: 91.5
  last_checked: 2022-03-06

GTMetrix Report: https://gtmetrix.com/reports/512kb.club/U7SXlhgX/

I thought our site was already in there, ha! Thanks for adding.


text:
Background Service Data Usage

It seems that the keybase daemons /usr/bin/keybase and /usr/bin/kbfsfuse are constantly sending a small amount of data across the network at all times even when I'm not doing anything.
I haven't looked into what the payload actually is, but this could probably be eliminated, which would be especially nice for clients on low-bandwidth networks (e.g. tethering)

Also interested in this. Somewhat related: I'm occasionally seeing /usr/bin/keybase transfer a relatively large amount of data (~34 MB just now, in a couple of minutes) for no obvious reason (no kbfs activity on my part whatsoever, although I can't exclude that some unrelated system process might be doing something in the background).
Tried poking around in the log files, but didn't find anything enlightening.

authors: JeremyRubin yelworc

repo: keybase/client


text:
Unable to track location in the background (Android)

I recently discovered the /location command, handily built into the app. This could mostly replace the Glympse app for me (except for those occations when I want to share my location with non-keybase users). I like the privacy that I get when using Keybase to share my location.
However, it seems that the Keybase app on Android is having trouble tracking the location in the background. For instance when I'm on my bike, or if I'm on the tram and using another app.
Is this something that's possible to solve in the app?
Is there some settings I should set in Android to allow the app to update my location in the background?
I'm using a LG V40.

It might also just be that the location is updated infrequently. It should probably be updated every 5-10 seconds? Maybe it could be configurable?


text:
Policy change PGP storage warning is misleading

When running keybase login today I was confronted with this message about the passphrase policy change:
Policy change on passphrases

We've gotten lots of feedback that it's annoying as all hell to enter a
Keybase passphrase after restarts and updates. The consensus is you can
trust a device's storage to keep a secret that's specific to that device.
Passphrases stink, like passed gas, and are bloody painful, like passed stones.

Note, however: on this device you have a PGP private key in Keybase's local
keychain.  Some people want to type a passphrase to unlock their PGP key, and
this new policy would bypass that. If you're such a person, you can run the
following command to remove your PGP private key.

    keybase pgp purge

If you do it, you'll have to use GPG for your PGP operations.

If you're ok with the new policy, you can run this command so you won't
get bothered with this message in the future:

    keybase dismiss pgp-storage

Thanks!

This message makes it sound as though by running keybase pgp purge I can make it so that using my PGP private key(s) requires a passphrase. However, I've determined that I can still use my private keys when I have a network connection because the CLI uses my session with the Keybase API to decrypt and sign using my stored PGP keys.
It may be that the intersection of folks who want to have to use their passphrase to unlock their PGP key and folks who upload their PGP key is small, but I thought this was surprising behavior that isn't clear from the messaging of the policy change text.

Perhaps the client could be changed so that if the PGP key is not in the local keyring the client asks for a passphrase before pulling the secret key from the keybase API.