text:
"Erase all my data" button.

This one is technically unnecessary of you understand how jupyterLite work, though this is more a question of User-interface than anything else.
We had a couple of request on the security mailing list of people asking us to "delete [their] data from [our] servers", in particular some quite panicked folks that had uploaded medical information and got their finger slapped.
User don't make the difference, or don't understand that the data is in their browser, and when they come back and see that files are still there, they may panic.
I suggest we add a button "Erase all my data", that pop up a dialog with:

a short explanation that no data is collected and everything is store on the current computer.
a "Erase all my data" (that clean any local storage or relevant).

I don't think it is pressing, but if this get a more usage we might start to have requests.
--
Alternatively we should have the "Go back" button discard the data as well and/or automatically discard on next usage if more than a certain amount of time as passed (potentially with warning), that would avoid the opposite case where someone assume it's persited, and lose work after a page refresh, or a browser update.

Yeah this is also a popular request in JupyterLite itself: https://github.com/jupyterlite/jupyterlite/issues/9
Two possible ways forward:

Fix https://github.com/jupyterlite/jupyterlite/issues/9, which should be done anyway at some point
Provide documentation in jupyterlite-sphinx to make it more visible how to use volatile memory storage: https://jupyterlite.readthedocs.io/en/stable/howto/configure/storage.html#volatile-memory-storage

or make it the default in jupyterlite-sphinx?

I guess once this is in JupyterLite, we can just have a hook to have say a link in the documentation footer when using jupyterlite-sphinx, that allow to erase w/o having to actually launch jupyter-lite. I think that not everyone will think at launching and then erasing.

authors: Carreau jtpio

repo: jupyterlite/jupyterlite-sphinx


text:
Wanted stars don't get displayed anymore

PlayerCompanion 1.2 hides the wanted stars. The relevant code line is here.

Is funny that this was easy to fix after #8 lol.
Anyway, here it is:

source: gharchive/issue

authors: justalemon vierse

repo: justalemon/PlayerCompanion

license: MIT

license_type: permissive

license_source: github-api


text:
Disable docs workflow

Apply local updates from mdsnippets as the workflow cannot push to the main branch due to the branch protections.
Disable the docs workflow push triggers for now until can get it working automatically in the desired way.

Codecov Report

Merging #331 (c309cb8) into main (5a42eab) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##              main      #331   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files           16        16
  Lines         1128      1128
=========================================
  Hits          1128      1128

Flag
Coverage Δ

linux
100.00% <ø> (ø)

macos
?

windows
?

Flags with carried forward coverage won't be shown. Click here to find out more.

Continue to review full report at Codecov.

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

source: gharchive/pull-request

authors: codecov-commenter martincostello

repo: justeat/httpclient-interception


text:
feat(pie-notification): DSW-1901 support full width notification (banner)

This PR adds a new prop to the pie-notification component position which applies the constraints of the design spects that the notification component does not have border radius when set to full-width
Description

═══════════════════════════════════════════════════════════
Describe your changes (can list changeset entries if preferable)
Author Checklist (complete before requesting a review)

[x] I have performed a self-review of my code
[x] I have added thorough tests where applicable (unit / component / visual)
[x] I have reviewed the PIE Storybook/PIE Docs PR preview
[x] I have reviewed visual test updates properly before approving
[x] If changes will affect consumers of the package, I have created a changeset entry.
[x] If a changeset file has been created, I have used the /snapit functionality to test my changes in a consuming application

Reviewer checklists (complete before approving)
Reviewer 1 - @raoufswe

[ ] I have reviewed the PIE Storybook/PIE Docs PR preview
[ ] If there are visual test updates, I have reviewed them

Reviewer 2 - @xander-marjoram

[x] I have reviewed the PIE Storybook/PIE Docs PR preview
[x] If there are visual test updates, I have reviewed them

This looks good. I noticed that there isn't currently a storybook control for the new position prop, can this be added in another PR?

@xander-marjoram i will add it as part of this PR https://github.com/justeattakeaway/pie/pull/1435 🤝

This looks good. I noticed that there isn't currently a storybook control for the new position prop, can this be added in another PR?

@xander-marjoram Looks like the control were lost on some rebase/merge.

authors: raoufswe thejfreitas xander-marjoram

repo: justeattakeaway/pie


text:
🛑 NextCloud is down

In cee8604, NextCloud (https://pan.mkacg.com) was down:

HTTP code: 0
Response time: 0 ms

Resolved: NextCloud is back up in 75421be after 10 minutes.


text:
🛑 Misskey is down

In 31671ad, Misskey (https://mkacg.social) was down:

HTTP code: 530
Response time: 179 ms

Resolved: Misskey is back up in 729376a after 1 hour, 58 minutes.


text:
Add JustList: {JustList name}

Before submission deletes this line:
THIS IS NOT A TOKEN LISTING REQUEST FORM. IF YOU DO NOT FOLLOW THE FORMAT OR MAKE A GENERIC TOKEN REQUEST YOUR ISSUE WILL BE DELETED WITHOUT COMMENT
YOUR JUSTLIST MUST FOLLOW THE JSON SPECIFICATION
https://github.com/justswaporg/justlists/blob/main/example.justlists.ts
Checklist

[ ] I understand that this is not the place to request a token listing.
[ ] I have tested that my JustList is compatible by pasting the URL into the add a list UI at justswap.org.
[ ] I understand that filing an issue or adding liquidity does not guarantee addition to the justlists website.

Please provide the following information for your token.
JustList URL must be HTTPS.
JustList URL:
JustList Name:
Link to the official homepage of the JustList manager:

Please submit the correct information, invalid information will cause the issue to close

repo: justswaporg/justlists


text:
Accept buffer

Default exported function readBarcode(input,[options]) should also handle data from type of Buffer as input argument. Fixes #2.

Pull Request Test Coverage Report for Build 52

8 of 8 (100.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 100.0%

Totals

Change from base Build 49:
0.0%

Covered Lines:
323

Relevant Lines:
323

💛  - Coveralls


text:
live.spec: test with filter

@dmehra

+1 on the test with filter, but question: is the live mode here based on read -every n -lag m? If so, maybe we should have tests using -every and -lag options? It's not clear to me if the testing of those belongs only in the base class, or if each adapter should retest in an integration-test scenario against a real instance of the backend.

I added a test for -every, but I had to skip it on https://github.com/juttle/juttle/pull/400. I don't know how we can test -lag at this level, although if it were to break altogether my tests would fail as they depend on a 2-second lag.

authors: davidvgalbraith dmehra

repo: juttle/juttle-elastic-adapter

license_source: bigquery


text:
Allow specifying precision with Math.{floor,round,ceil}

Add optional digits argument to Math.floor, Math.round, and Math.ceil to allow specifying rounding precision.
(This issue was tracked as PROD-7285 internally.)

Do we want to simply apply toPrecision after the calculation of floor,round or ceil ?

The implementation Will started before open-sourcing did something slightly more complicated.
Calling toPrecision before/after the calculation definitely won’t work as JavaScript’s Math.round & co. always round to 0, destroying any more fine-grained rounding. One has to multiply, round, and divide.

@dmajda I can take this one on then and pull in that decimal rounding approach in the link you provided.

@rlgomes Sure, go ahead.

authors: dmajda rlgomes

repo: juttle/juttle


text:
Add a --trace option for --eval to reproduce the "relevant expression context"

If, during evaluation, we record the expression trees involved, and "color" them as we go, then at the point of reaching throwError we could dump the minimal expression tree relevant to the error:

Delete unreferenced set members
Delete unreferenced function arguments (if taking a parameter set)
Delete unused default arguments
Replace unevaluated thunks with nulls

This would make it easier to turn errors into test cases.

This is actually done now! I'm going to have to write a blog post tonight on how powerful recursion schemes can be. I was able to add this functionality without changing a single line in the original data types or evaluators.

@ryantrinkle The option is --trace, which for the given input file:
let x = { z = import ./eighty.nix + 20; w = 123; };
    y = "Hello";
    z = "Goodbye";
in assert 1 == 1; if x.z == 100 then y else 3

Produces this output:
Expression tree before winnowing:
--------
let
  x = {
    z = import ./eighty.nix + 20;
    w = 123;
  };
  y = "Hello";
  z = "Goodbye";
in assert 1 == 1;
if x.z == 100 then y else 3
--------
Expression tree after winnowing:
--------
let
  x = {
    z = 80 + 20;
    w = null;
  };
  y = "Hello";
in y
--------
"Hello"

This is actually working well enough that it produces a file which reproduces the <<loop>> I'm encountering in nixpkgs right now, within a file that is <10k lines.  It still contains imports when those imports are the result of evaluation (i.e., the tracer can't see the import directly), but I think I could work around this write a custom evaluator that does very gentle (i.e., no effect) elimination.

I need to use an evaluator here that does "no effect reduction", to further simplify the resulting expression tree and discover more importing opportunities. Right now the following fails to trigger a static load:
let callLibs = file: import file { lib = self; };
    trivial = callLibs ./trivial.nix;
in trivial

Also, we should be able to reduce all statically computable subexpressions. This will mean flagging builtins to know which cause external effects and which are pure.

This is insanely awesome.  Both the functionality and the fact that it was so clean to add.

😻

The code for this approach is here: https://github.com/jwiegley/hnix/blob/master/src/Nix/Trace.hs. Note that the only function doing real work here is pruneTree, which decides what it means for an expression node to have unreferenced parts. This code is called from here: https://github.com/jwiegley/hnix/blob/master/src/Nix/Entry.hs#L74

Blog article describing this process is up: http://newartisans.com/2018/04/win-for-recursion-schemes/

The pure reduction evaluator is now working and is part of --trace.  See Reduce.hs for more details.

authors: gilligan jwiegley ryantrinkle

repo: jwiegley/hnix


text:
Generate an event with a signal to docker-gen

Hi,
it will be great to be able to send a signal to docker-gen that create a "fake" event (like if a container is starting/dying).
With that we can "force" docker-gen to regenerate file(s) with template(s) without creating/stopping a container.

You can send a sighup signal to trigger a regeneration if the templates.

I searching for something similar.
But sighup isn't an option for me, because it kill the container. I also tried to exec into the container and send the sighup to the process itself, but with the same result.
The problem is, this could trigger other stuff when managed by docker-compose and/or similar scheduling components. I.e. in my case this would rebuild the whole stack of proxy.
I tried a workaround by invoking invoking docker-gen with the template inside the running docker-gen container. But against my assumption /usr/local/bin/docker-gen -only-exposed /my/template.tmpl /my/generated.file started docker-gen as "watching" process.
I would assume without -wait it would just generate the file and exit. But it waits as it would be started with -wait.
Probably this is a bug?
@jwilder should I create a separate Issue for this or did I miss something?

@spali sighup won't kill docker-gen process.  Are you sure you are sending the signal to the correct process?  docker-gen not exiting should be fixed in 0.6 version.

I tried it with docker kill -signal=sighup to the docker-gen Container. As I know this should send it to the main process which is docker-gen.
Also tried docker exec to the container with pkill. Same result.
Probalby I have to say I use alpine as base image for docker-gen. But beside this the Image is exaclty the same setup as your original one.
Am 16. Februar 2016 01:21:41 MEZ, schrieb Jason Wilder notifications@github.com:

@spali sighup won't kill docker-gen process.  Are you sure you are
sending the signal to the correct process?  docker-gen not exiting
should be fixed in 0.6 version.

Reply to this email directly or view it on GitHub:
https://github.com/jwilder/docker-gen/issues/162#issuecomment-184450532

It seems to work with version 0.6.0.
Thanks @jwilder

I can confirm it to, sighup works with 0.6.0
thanks

authors: JrCs jwilder spali

repo: jwilder/docker-gen

license: mit


text:
🛑 le Zata is down

In c8d04f8, le Zata (http://zata.free.fr) was down:

HTTP code: 0
Response time: 0 ms

Resolved: le Zata is back up in a7e2ee0.

repo: jyhem/upptime-jyhem


text:
Customize typescript compiler version?

I need a typescript compiler flag(option) recently introduced in typescript(1.8.0 nightly build) for my project, but grunt-typescript does not seem to be picking up the new version of typescript compiler from my typescript npm install, and also tried to manually copied over the new version of typescript bits under "node_modules\grunt-typescript\node_modules\typescript", still no luck.
By simply doing below, I confirmed that the typescript compiler version I applied can actually respect the new flag(forceConsistentCasingInFileNames) I want to apply, but I could not make it work for grunt-typescript.
node <project_path>\node_modules\grunt-typescript\node_modules\typescript\bin\tsc --forceConsistentCasingInFileNames hello.ts hello1.ts test.ts error TS1149: File name 'test.ts' differs from already included file name '../TeSt/test.ts' only in casing
For reference, here is my gruntfile, by using it to build same ts files, I don't get the compiler error, which is what I expect in this case by specifying the compile option(forceConsistentCasingInFileNames).
module.exports = function (grunt) {
grunt.initConfig({
typescript: {
base: {
src: ['*.ts'],
dest: '',
options: {
module: 'amd', //or commonjs
target: 'es5', //or es3
sourceMap: false,
declaration: false,
forceConsistentCasingInFileNames: true
}
}
}
});
grunt.loadNpmTasks('grunt-typescript');
grunt.registerTask('default', ['typescript:base']);
};
Any thoughts?

For anyone else having this issue.. if you are using yarn, you can edit the yarn.lock file to modify the version grunt-typescript uses.

repo: k-maru/grunt-typescript


text:
merge from template-arlac77-github

package.json

chore(deps): add ^10.1.1 remove ^10.0.0 (devDependencies.c8)

.github/pr_labeler.yml

chore: (lint)

Pull Request Test Coverage Report for Build 9484822988
Details

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

Totals

Change from base Build 9483894977:
0.0%

Covered Lines:
275

Relevant Lines:
313

💛  - Coveralls


text:
[BUG] Luks volume prevents cluster creation

What did you do
k3d command
k3d cluster create cluster  --volume /var/lib/kubelet:/var/lib/kubelet --verbose
DEBU[0000] DOCKER_SOCK=/var/run/docker.sock
DEBU[0000] Runtime Info:
&{Name:docker Endpoint:/var/run/docker.sock Version:20.10.14 OSType:linux OS:Fedora Linux 35 (Workstation Edition) Arch:x86_64 CgroupVersion:2 CgroupDriver:systemd Filesystem:UNKNOWN}
DEBU[0000] Additional CLI Configuration:
cli:
  api-port: ""
  env: []
  k3s-node-labels: []
  k3sargs: []
  ports: []
  registries:
    create: ""
  runtime-labels: []
  volumes:
  - /var/lib/kubelet:/var/lib/kubelet
hostaliases: []
DEBU[0000] Configuration:
agents: 0
image: docker.io/rancher/k3s:v1.22.7-k3s1
network: ""
options:
  k3d:
    disableimagevolume: false
    disableloadbalancer: false
    disablerollback: false
    loadbalancer:
      configoverrides: []
    timeout: 0s
    wait: true
  kubeconfig:
    switchcurrentcontext: true
    updatedefaultkubeconfig: true
  runtime:
    agentsmemory: ""
    gpurequest: ""
    hostpidmode: false
    serversmemory: ""
registries:
  config: ""
  use: []
servers: 1
subnet: ""
token: ""
DEBU[0000] ========== Simple Config ==========
{TypeMeta:{Kind:Simple APIVersion:k3d.io/v1alpha4} ObjectMeta:{Name:} Servers:1 Agents:0 ExposeAPI:{Host: HostIP: HostPort:} Image:docker.io/rancher/k3s:v1.22.7-k3s1 Network: Subnet: ClusterToken: Volumes:[] Ports:[] Options:{K3dOptions:{Wait:true Timeout:0s DisableLoadbalancer:false DisableImageVolume:false NoRollback:false NodeHookActions:[] Loadbalancer:{ConfigOverrides:[]}} K3sOptions:{ExtraArgs:[] NodeLabels:[]} KubeconfigOptions:{UpdateDefaultKubeconfig:true SwitchCurrentContext:true} Runtime:{GPURequest: ServersMemory: AgentsMemory: HostPidMode:false Labels:[]}} Env:[] Registries:{Use:[] Create:<nil> Config:} HostAliases:[]}
==========================
DEBU[0000] ========== Merged Simple Config ==========
{TypeMeta:{Kind:Simple APIVersion:k3d.io/v1alpha4} ObjectMeta:{Name:} Servers:1 Agents:0 ExposeAPI:{Host: HostIP: HostPort:46573} Image:docker.io/rancher/k3s:v1.22.7-k3s1 Network: Subnet: ClusterToken: Volumes:[{Volume:/var/lib/kubelet:/var/lib/kubelet NodeFilters:[]}] Ports:[] Options:{K3dOptions:{Wait:true Timeout:0s DisableLoadbalancer:false DisableImageVolume:false NoRollback:false NodeHookActions:[] Loadbalancer:{ConfigOverrides:[]}} K3sOptions:{ExtraArgs:[] NodeLabels:[]} KubeconfigOptions:{UpdateDefaultKubeconfig:true SwitchCurrentContext:true} Runtime:{GPURequest: ServersMemory: AgentsMemory: HostPidMode:false Labels:[]}} Env:[] Registries:{Use:[] Create:<nil> Config:} HostAliases:[]}
==========================
WARN[0000] No node filter specified
DEBU[0000] generated loadbalancer config:
ports:
  6443.tcp:
  - k3d-cluster-server-0
settings:
  workerConnections: 1024
DEBU[0000] ===== Merged Cluster Config =====
&{TypeMeta:{Kind: APIVersion:} Cluster:{Name:cluster Network:{Name:k3d-cluster ID: External:false IPAM:{IPPrefix:zero IPPrefix IPsUsed:[] Managed:false} Members:[]} Token: Nodes:[0xc000103ba0 0xc000103d40] InitNode:<nil> ExternalDatastore:<nil> KubeAPI:0xc00042bf40 ServerLoadBalancer:0xc000421bf0 ImageVolume: Volumes:[]} ClusterCreateOpts:{DisableImageVolume:false WaitForServer:true Timeout:0s DisableLoadBalancer:false GPURequest: ServersMemory: AgentsMemory: NodeHooks:[] GlobalLabels:map[app:k3d] GlobalEnv:[] HostAliases:[] Registries:{Create:<nil> Use:[] Config:<nil>}} KubeconfigOpts:{UpdateDefaultKubeconfig:true SwitchCurrentContext:true}}
===== ===== =====
DEBU[0000] '--kubeconfig-update-default set: enabling wait-for-server
INFO[0000] Prep: Network
INFO[0000] Created network 'k3d-cluster'
INFO[0000] Created image volume k3d-cluster-images
INFO[0000] Starting new tools node...
DEBU[0000] DOCKER_SOCK=/var/run/docker.sock
DEBU[0000] DOCKER_SOCK=/var/run/docker.sock
DEBU[0000] DOCKER_SOCK=/var/run/docker.sock
DEBU[0000] Detected CgroupV2, enabling custom entrypoint (disable by setting K3D_FIX_CGROUPV2=false)
DEBU[0000] DOCKER_SOCK=/var/run/docker.sock
DEBU[0000] [Docker] DockerHost: '' ()
DEBU[0000] Created container k3d-cluster-tools (ID: da9c9b93b817c425eedf3f6204bc48a376e38407cfe6fadc7e164d2929fe2b3d)
DEBU[0000] Node k3d-cluster-tools Start Time: 2022-04-13 15:33:00.571834249 +0200 CEST m=+0.183063588
INFO[0000] Starting Node 'k3d-cluster-tools'
DEBU[0000] Truncated 2022-04-13 13:33:00.860083849 +0000 UTC to 2022-04-13 13:33:00 +0000 UTC
INFO[0001] Creating node 'k3d-cluster-server-0'
DEBU[0001] Created container k3d-cluster-server-0 (ID: 0bab476940e2c211fed9f7cfddef05024999efc2b8260dcdd7ed0578746773cd)
DEBU[0001] Created node 'k3d-cluster-server-0'
INFO[0001] Creating LoadBalancer 'k3d-cluster-serverlb'
DEBU[0001] Created container k3d-cluster-serverlb (ID: b75828b86c1d7ed1d70bec94ac9ea6c0913e106c32364f8e3d6215f077a5b442)
DEBU[0001] Created loadbalancer 'k3d-cluster-serverlb'
DEBU[0001] DOCKER_SOCK=/var/run/docker.sock
INFO[0001] Using the k3d-tools node to gather environment information
DEBU[0001] no netlabel present on container /k3d-cluster-tools
DEBU[0001] failed to get IP for container /k3d-cluster-tools as we couldn't find the cluster network
DEBU[0001] Deleting node k3d-cluster-tools ...
DEBU[0001] DOCKER_SOCK=/var/run/docker.sock
INFO[0001] HostIP: using network gateway 172.25.0.1 address
INFO[0001] Starting cluster 'cluster'
INFO[0001] Starting servers...
DEBU[0001] >>> enabling cgroupsv2 magic
DEBU[0001] Node k3d-cluster-server-0 Start Time: 2022-04-13 15:33:01.719721941 +0200 CEST m=+1.330951281
INFO[0001] Starting Node 'k3d-cluster-server-0'
DEBU[0001] Truncated 2022-04-13 13:33:02.141510745 +0000 UTC to 2022-04-13 13:33:02 +0000 UTC
DEBU[0001] Waiting for node k3d-cluster-server-0 to get ready (Log: 'k3s is up and running')
DEBU[0005] Finished waiting for log message 'k3s is up and running' from node 'k3d-cluster-server-0'
INFO[0005] All agents already running.
INFO[0005] Starting helpers...
DEBU[0005] Node k3d-cluster-serverlb Start Time: 2022-04-13 15:33:05.858417659 +0200 CEST m=+5.469647051
INFO[0005] Starting Node 'k3d-cluster-serverlb'
DEBU[0005] Truncated 2022-04-13 13:33:06.215226464 +0000 UTC to 2022-04-13 13:33:06 +0000 UTC
DEBU[0005] Waiting for node k3d-cluster-serverlb to get ready (Log: 'start worker processes')
DEBU[0011] Finished waiting for log message 'start worker processes' from node 'k3d-cluster-serverlb'
DEBU[0011] Found network {Name:k3d-cluster ID:5815d0b91bebcd92fd865c8a103d78a89a341686efa600476c381193d4f1d50f Created:2022-04-13 15:33:00.41126982 +0200 CEST Scope:local Driver:bridge EnableIPv6:false IPAM:{Driver:default Options:map[] Config:[{Subnet:172.25.0.0/16 IPRange: Gateway:172.25.0.1 AuxAddress:map[]}]} Internal:false Attachable:false Ingress:false ConfigFrom:{Network:} ConfigOnly:false Containers:map[0bab476940e2c211fed9f7cfddef05024999efc2b8260dcdd7ed0578746773cd:{Name:k3d-cluster-server-0 EndpointID:3434adf4ddbd101b57335593b37a48c390cbda99804bfbab71d95bd2debfdc76 MacAddress:02:42:ac:19:00:02 IPv4Address:172.25.0.2/16 IPv6Address:} b75828b86c1d7ed1d70bec94ac9ea6c0913e106c32364f8e3d6215f077a5b442:{Name:k3d-cluster-serverlb EndpointID:c4cfffefd05fda7a5270cf7632006b9fc8930e1aa71b2215dd37871c2ce6d263 MacAddress:02:42:ac:19:00:03 IPv4Address:172.25.0.3/16 IPv6Address:}] Options:map[com.docker.network.bridge.enable_ip_masquerade:true] Labels:map[app:k3d] Peers:[] Services:map[]}
INFO[0011] Injecting records for hostAliases (incl. host.k3d.internal) and for 2 network members into CoreDNS configmap...
DEBU[0011] Finished waiting for log message 'Cluster dns configmap' from node 'k3d-cluster-server-0'
DEBU[0012] Executing command '[sh -c cat /tmp/-etc-hosts-aDhcWmfMktqyUpRiaIBi > /etc/hosts]' in node 'k3d-cluster-server-0'
DEBU[0013] Exec process in node 'k3d-cluster-server-0' exited with '0'
INFO[0013] Cluster 'cluster' created successfully!
DEBU[0013] Updating default kubeconfig with a new context for cluster cluster
DEBU[0014] Setting new current-context 'k3d-cluster'
DEBU[0014] Wrote kubeconfig to '/home/username/.kube/config'
INFO[0014] You can now use it like this:
kubectl cluster-info

Docker logs
I0413 13:31:25.567767       8 state_mem.go:88] "Updated default CPUSet" cpuSet=""
I0413 13:31:25.567792       8 state_mem.go:96] "Updated CPUSet assignments" assignments=map[]
I0413 13:31:25.567797       8 policy_none.go:49] "None policy: Start"
I0413 13:31:25.569397       8 memory_manager.go:168] "Starting memorymanager" policy="None"
I0413 13:31:25.569429       8 state_mem.go:35] "Initializing new in-memory state store"
I0413 13:31:25.569548       8 state_mem.go:75] "Updated machine memory state"
W0413 13:31:25.569582       8 fs.go:588] stat failed on /dev/mapper/luks-61e76090-4342-45ca-96a5-7cbeba016158 with error: no such file or directory
E0413 13:31:25.569605       8 kubelet.go:1423] "Failed to start ContainerManager" err="failed to get rootfs info: failed to get device for dir \"/var/lib/kubelet\": could not find device with major: 0, minor: 33 in cached partitions map"

What did you do afterwards?
cluster-server fails to start

What did you expect to happen
cluster-server starts
Which OS & Architecture
Fedora 35 x86_64
k3d version v5.4.1
k3s version v1.22.7-k3s1 (default)
/kubelet $ docker version
Client: Docker Engine - Community
 Version:           20.10.14
 API version:       1.41
 Go version:        go1.16.15
 Git commit:        a224086
 Built:             Thu Mar 24 01:48:41 2022
 OS/Arch:           linux/amd64
 Context:           default
 Experimental:      true

Server: Docker Engine - Community
 Engine:
  Version:          20.10.14
  API version:      1.41 (minimum version 1.12)
  Go version:       go1.16.15
  Git commit:       87a90dc
  Built:            Thu Mar 24 01:46:30 2022
  OS/Arch:          linux/amd64
  Experimental:     false
 containerd:
  Version:          1.5.11
  GitCommit:        3df54a852345ae127d1fa3092b95168e4a88e2f8
 runc:
  Version:          1.0.3
  GitCommit:        v1.0.3-0-gf46b6ba
 docker-init:
  Version:          0.19.0
  GitCommit:        de40ad0

~/kubelet $ docker info
Client:
 Context:    default
 Debug Mode: false
 Plugins:
  app: Docker App (Docker Inc., v0.9.1-beta3)
  buildx: Docker Buildx (Docker Inc., v0.8.1-docker)
  scan: Docker Scan (Docker Inc., v0.17.0)

Server:
 Containers: 2
  Running: 1
  Paused: 0
  Stopped: 1
 Images: 3
 Server Version: 20.10.14
 Storage Driver: btrfs
  Build Version: Btrfs v5.16.2
  Library Version: 102
 Logging Driver: json-file
 Cgroup Driver: systemd
 Cgroup Version: 2
 Plugins:
  Volume: local
  Network: bridge host ipvlan macvlan null overlay
  Log: awslogs fluentd gcplogs gelf journald json-file local logentries splunk syslog
 Swarm: inactive
 Runtimes: io.containerd.runc.v2 io.containerd.runtime.v1.linux runc
 Default Runtime: runc
 Init Binary: docker-init
 containerd version: 3df54a852345ae127d1fa3092b95168e4a88e2f8
 runc version: v1.0.3-0-gf46b6ba
 init version: de40ad0
 Security Options:
  seccomp
   Profile: default
  cgroupns
 Kernel Version: 5.16.18-200.fc35.x86_64
 Operating System: Fedora Linux 35 (Workstation Edition)
 OSType: linux
 Architecture: x86_64
 CPUs: 10
 Total Memory: 15.58GiB
 Name: fedora
 ID: TY2I:46KA:BADF:2K2N:TL6Z:23NE:HCCB:GTN6:I64P:V4JU:MXNR:IOOF
 Docker Root Dir: /var/lib/docker
 Debug Mode: false
 Registry: https://index.docker.io/v1/
 Labels:
 Experimental: false
 Insecure Registries:
  127.0.0.0/8
 Live Restore Enabled: false

Note
I tried the exact same pattern on an unencrypted distro and it went perfectly well.

Hi @theonlydoo , thanks for opening this issue!
I see /dev/mapper.. so maybe similar to the btrfs issue? See https://k3d.io/v5.4.1/faq/faq/#issues-with-btrfs

Did you try the tip from the FAQ?

-v /dev/mapper:/dev/mapper fixes the issue! thanks


text:
Tutorial request: k3s for developers, from container to scale (on own servers, without k8s knowledge)

Dear k3s team,
it would be great to get a developer friendly tutorial how to use k3s and its preferred tools to move from a dev container to a production cluster. I am looking for a bare metal ("dedicated server" with linux) simple command line tutorial without the need of learning Terraform, Vagrant, Ansible, Helm, BGP and so on and so forth.
Currently we have an external high-available load-balancer, 3 ingress servers running Traefik and Docker Swarm Masters, and multiple worker nodes. We spin up 3+ containers for each tennant, they automatically register with Traefik and are available load-balanced via their sub-domain.

Docker Swarm has served us well as a very easy to use tool to get started, but we seem to have some minor issues with high loads. At the same time no-one seems to be using Docker Swarm nowadays, related GitHub projects are mostly dormant. K3s seems to be a good alternative, especially as the initial setup seems as easy as Docker Swarm.
What I haven't found so far is an overarching tutorial of how to scale a web container with k3s on own servers. Yes, it is k8s compatible, but at the same time it has some tools build in and/or preferred, so a dedicated tutorial would be helpful. And it would be great to NOT have a lot of external tools which need to be understood and maintained. For starters it's just easier to setup a new server every month by hand instead of learning yet another tool to do this automatically. And for GDPR and money saving reasons our infrastructure is on dedicated servers, even A18z recognised cloud is expensive. To make live easier our scenario just uses an external load balancer.
It should include (using Docker Swarm terms here)

[x] setup of k3s cluster
[ ] setup of ingress with traefik and (purchased) SSL certificates (on 3 servers with fixed IP:port for high availability)
[ ] start a service with x containers with sub-domain as label and node-constraint (on workers only)
[ ] view status of cluster (maybe with a GUI)
[ ] do a rolling update of a service
[ ] advanced: collect logs with Prometheus/Grafana or Beats/Elastic/Kibana
[ ] more advanced: make it high-available without external LB but with external Floating IP

For reference a post which gets Traefik and a web service up and running on Docker Swarm with two config files and 3 CLI commands.

Have you looked at the Rancher Academy course on k3s?
https://community.suse.com/courses/4522316?utm_source=manual


text:
[Backport 1.20] - Possible race where bootstrap data might not save

This fix needs to be backported to previous release branches.
Original issue can be found here #3414  .

Validated on k3s version v1.20.9-rc1+k3s1. Bootstrap data is saved.
/bootstrap/7b23e6c72545
/registry/clusterroles/system:node-bootstrapper
/registry/rolebindings/kube-public/system:controller:bootstrap-signer
/registry/rolebindings/kube-system/system:controller:bootstrap-signer
/registry/roles/kube-public/system:controller:bootstrap-signer
/registry/roles/kube-system/system:controller:bootstrap-signer

authors: ShylajaDevadiga briandowns


text:
[release-1.20] Update packaged etcd

etcd 3.4.18 - multiple fixes

Steps to verify:
Using this commit id: 29b4bd8a1d318b7f31f4b3f3f87e04369a19478e
Install k3s using --cluster-int
curl -sfL https://get.k3s.io | INSTALL_K3S_COMMIT=29b4bd8a1d318b7f31f4b3f3f87e04369a19478e  INSTALL_K3S_EXEC="server --write-kubeconfig-mode 644 --token secret --cluster-init" sh -

Once k3s is running, look for the etcd version using this command, looking for this line
Expected result: ..."msg":"starting an etcd server","etcd-version":"3.4.18"
$sudo journalctl -u k3s | grep -i etcd-version

Actual result, displayed correctly:
Jan 19 23:22:23 ip-172-31-47-39 k3s[1543]: {"level":"info","ts":"2022-01-19T23:22:23.500Z","caller":"embed/etcd.go:303","msg":"starting an etcd server","etcd-version":"3.4.18","git-sha":"Not provided (use ./build instead of go build)","go-version":"go1.15.15","go-os":"linux"
...
...
...


text:
Fix help text with flannel-backend

Help text with flannel-backend has duplicate default: "vxlan"
$ k3s server --help  |grep flannel
   --flannel-backend value                    (networking) One of 'none', 'vxlan', 'ipsec', 'host-gw', 'wireguard'(deprecated), or 'wireguard-native' (default: vxlan) (default: "vxlan")

Environmental Info:
K3s Version: v1.23.5+k3s-483eadb5

Validated using commit id 3307d53f8f2b45d06ad346eb0dc54dcbc12bcdaf
$ k3s -v
k3s version v1.23.5+k3s-3307d53f (3307d53f)

$ k3s server --help|grep flannel
   --flannel-backend value                    (networking) One of 'none', 'vxlan', 'ipsec', 'host-gw', 'wireguard'(deprecated), or 'wireguard-native' (default: "vxlan")


text:
Installation on CentOS Stream 9 aborts due to failed GPG check

Environmental Info:
Node(s) CPU architecture, OS, and Version: CentOS Stream 9 on x86_64
Describe the bug:
Ran curl -sfL https://get.k3s.io | sh - as root, fails during package installation with:
Downloading Packages:
(1/3): container-selinux-2.183.0-1.el9.noarch.rpm                                                             313 kB/s |  47 kB     00:00
(2/3): policycoreutils-python-utils-3.3-5.el9.noarch.rpm                                                      433 kB/s |  74 kB     00:00
(3/3): k3s-selinux-1.1-1.el8.noarch.rpm                                                                        28 kB/s |  20 kB     00:00
----------------------------------------------------------------------------------------------------------------------------------------------
Total                                                                                162 kB/s | 142 kB     00:00
Rancher K3s Common (stable)                                                                                4.6 kB/s | 2.4 kB     00:00
Importing GPG key 0xE257814A:
 Userid     : "Rancher (CI) <ci@rancher.com>"
 Fingerprint: C8CF F216 4551 26E9 B9C9 18BE 925E A29A E257 814A
 From       : https://rpm.rancher.io/public.key
Key imported successfully
Import of key(s) didn't help, wrong key(s)?
Problem opening package k3s-selinux-1.1-1.el8.noarch.rpm. Failing package is: k3s-selinux-1.1-1.el8.noarch
 GPG Keys are configured as: https://rpm.rancher.io/public.key
The downloaded packages were saved in cache until the next successful transaction.
You can remove cached packages by executing 'dnf clean packages'.
Error: GPG check FAILED

Steps To Reproduce:
Run curl -sfL https://get.k3s.io | sh - on a CentOS Stream 9 or other RPM distribution.

Given that the repo config uses https://rpm.rancher.io/public.key for the GPG key, is it out of date or have the RPM packages been compromised?

Same issue on RHEL 9. Interestingly I was able to perform a successful install on RHEL 9 earlier.

In fact, yes, after running update-crypto-policies --set DEFAULT:SHA1 (see https://access.redhat.com/articles/6846411), installing k3s-selinux works just fine.
This is a repo/packaging problem, I think Rancher needs to sign their packages with a SHA256 or SHA521 key instead of SHA1.

Yeah, sorry, that's what I meant. :)

Another affected user here, but just to add to @hbjydev's comment about updating crypto policies, SHA1 can be disabled after install like this update-crypto-policies --set DEFAULT:NO-SHA1

Another affected user here, but just to add to @hbjydev's comment about updating crypto policies, SHA1 can be disabled after install like this update-crypto-policies --set DEFAULT:NO-SHA1

It certainly could be, but I don't think it's wise until they fix the package signatures, because doing this will just break any updates to the package until it's sorted out at the repo end.
For a dev or test box, sure, but I can't recommend if you're in production.

@brandond That's fair, yeah, but I'd still rather not need to turn it on and off either side, hence I'm just cautioning that it's not a great solution. :)

Yeah, since we only technically support EL7 and EL8 we haven't updated the signing hash algorithms to account for the deprecation of SHA-1. We'll take a look at addressing this for our next release cycle.

Not to put any pressure, but when is the next release cycle due? I can wait for a few days to install k3s if it's due shortly, otherwise I'll have to try one of the workaround I'd prefer to avoid.

"Not to be too blunt about it, but if you're super paranoid about running untrusted software (or software with 'weak' signatures) you're probably not using containers, right?"
It's more complicated than that.  The script overrides the .repo file, so even setting gpgcheck=0 won't fix it.  Supply side attacks are also a very real threat to enterprise environments, but ignoring that doesn't provide an obvious workaround here.  I downloaded the updated rpm and installed it with rpm -Uvh --nosignature and was able to continue that way but it is not a great upgrade experience to have to go that far into what is supposed to be a "here, run this script again" as the docs present.

I'm not sure anyone is using CentOS 9 Stream in production,

Yes, we are, with k3s for several months now with k3s, and it's actually been working great.  This recent upgrade was my first real snag.

Not to be too blunt about it, but if you're super paranoid about running untrusted software (or software with 'weak' signatures) you're probably not using containers, right? Image signing still isn't really a thing so all you have is TLS to verify the source of your pulls...

Not paranoid, just "aware", in my job I have to answer to security people and customers if I do things like enable a deprecated crypto algorithm.

Any movement on this at all?

Been hitting a similar issue with CentOS streams 8.
    openstack: TASK [Install sigul client for EL 8 (Streams)] *********************************
    openstack: Wednesday 08 June 2022  20:51:03 +1000 (0:00:00.026)       0:12:18.049 ********
    openstack: fatal: [default]: FAILED! => {
    openstack:     "changed": false
    openstack: }
    openstack:
    openstack: MSG:
    openstack:
    openstack: Failed to validate GPG signature for sigul-1.1-1.el8.infra.x86_64

Stream 8 is basically EL9 but worse, so yes.
We will address this once our current in-flight releases are complete.

An updated package is now available in the testing channel. You should now be able to do:
curl -ks https://get.k3s.io | INSTALL_K3S_CHANNEL=testing sh -

[root@2975a4d1a4bf /]# cat /etc/os-release
NAME="Red Hat Enterprise Linux"
VERSION="9.0 (Plow)"
ID="rhel"
ID_LIKE="fedora"
VERSION_ID="9.0"
PLATFORM_ID="platform:el9"
PRETTY_NAME="Red Hat Enterprise Linux 9.0 (Plow)"
ANSI_COLOR="0;31"
LOGO="fedora-logo-icon"
CPE_NAME="cpe:/o:redhat:enterprise_linux:9::baseos"
HOME_URL="https://www.redhat.com/"
DOCUMENTATION_URL="https://access.redhat.com/documentation/red_hat_enterprise_linux/9/"
BUG_REPORT_URL="https://bugzilla.redhat.com/"

REDHAT_BUGZILLA_PRODUCT="Red Hat Enterprise Linux 9"
REDHAT_BUGZILLA_PRODUCT_VERSION=9.0
REDHAT_SUPPORT_PRODUCT="Red Hat Enterprise Linux"
REDHAT_SUPPORT_PRODUCT_VERSION="9.0"
[root@2975a4d1a4bf /]# curl -ks https://get.k3s.io | INSTALL_K3S_SKIP_START=1 INSTALL_K3S_CHANNEL=testing sh -
[INFO]  Finding release for channel testing
[INFO]  Using v1.24.1-rc5+k3s1 as release
[INFO]  Downloading hash https://github.com/k3s-io/k3s/releases/download/v1.24.1-rc5+k3s1/sha256sum-amd64.txt
[INFO]  Downloading binary https://github.com/k3s-io/k3s/releases/download/v1.24.1-rc5+k3s1/k3s
[INFO]  Verifying binary download
[INFO]  Installing k3s to /usr/local/bin/k3s
Updating Subscription Management repositories.
Unable to read consumer identity
Subscription Manager is operating in container mode.

This system is not registered with an entitlement server. You can use subscription-manager to register.

Rancher K3s Common (testing)                                                                                3.6 kB/s | 3.0 kB     00:00
Dependencies resolved.
=============================================================================================================================================================================================
 Package                                    Architecture                          Version                                    Repository                                                 Size
=============================================================================================================================================================================================
Installing:
 k3s-selinux                                noarch                                1.2-2.el8                                  rancher-k3s-common-testing                                 20 k

Transaction Summary
=============================================================================================================================================================================================
Install  1 Package

Total download size: 20 k
Installed size: 94 k
Downloading Packages:
k3s-selinux-1.2-2.el8.noarch.rpm                                                                                111 kB/s |  20 kB     00:00
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Total                                                                                110 kB/s |  20 kB     00:00
Rancher K3s Common (testing)                                                                                7.1 kB/s | 2.4 kB     00:00
Importing GPG key 0xD161F542:
 Userid     : "Rancher (CI) <ci@rancher.com>"
 Fingerprint: 856A 0069 529C A63B 21AA 4E0A 089F A20E D161 F542
 From       : https://rpm-testing.rancher.io/public.key
Key imported successfully
Running transaction check
Transaction check succeeded.
Running transaction test
Transaction test succeeded.
Running transaction
  Preparing        :                                                                                1/1
  Running scriptlet: k3s-selinux-1.2-2.el8.noarch                                                                                1/1
  Installing       : k3s-selinux-1.2-2.el8.noarch                                                                                1/1
  Running scriptlet: k3s-selinux-1.2-2.el8.noarch                                                                                1/1
  Verifying        : k3s-selinux-1.2-2.el8.noarch                                                                                1/1
Installed products updated.

Installed:
  k3s-selinux-1.2-2.el8.noarch

Complete!

This is now fixed for me.  I upgraded to 1.23.8 on CentOS Stream 9 normally with the regular update script today without any workarounds.

Stream 8 is basically EL9 but worse, so yes.

No.  Stream 8 is used for EL8 and Stream 9 is used for EL9.  The confusion on the "rolling release" is strong, but really simple.  Updates to Centos 8 will show up as minor upgrade for EL8 and similar for Cent9 -> EL9.

Any update on this?
Downloading Packages:
(1/9): k3s-selinux-1.1-1.el8.noarch.rpm                                                                                33 kB/s |  20 kB     00:00
(2/9): container-selinux-2.188.0-1.el9_0.noarch.rpm                                                                                243 kB/s |  47 kB     00:00
(3/9): python3-setools-4.4.0-4.el9.x86_64.rpm                                                                                478 kB/s | 547 kB     00:01
(4/9): python3-audit-3.0.7-101.el9_0.2.x86_64.rpm                                                                                162 kB/s |  83 kB     00:00
(5/9): checkpolicy-3.3-1.el9.x86_64.rpm                                                                                273 kB/s | 339 kB     00:01
(6/9): policycoreutils-python-utils-3.3-6.el9_0.noarch.rpm                                                                                149 kB/s |  68 kB     00:00
(7/9): python3-setuptools-53.0.0-10.el9.noarch.rpm                                                                                297 kB/s | 841 kB     00:02
(8/9): python3-libsemanage-3.3-2.el9.x86_64.rpm                                                                                222 kB/s |  80 kB     00:00
(9/9): python3-policycoreutils-3.3-6.el9_0.noarch.rpm                                                                                612 kB/s | 2.0 MB     00:03
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Total                                                                                737 kB/s | 4.0 MB     00:05
Problem opening package k3s-selinux-1.1-1.el8.noarch.rpm
The downloaded packages were saved in cache until the next successful transaction.
You can remove cached packages by executing 'yum clean packages'.
Error: GPG check FAILED

I'm having the same issue on CentOS Stream 9.
@KyleSanderson I think we'll have to wait for the next release of k3s-selinux.
@brandond  The testing channel did not work for me.
@1player Thx, that workaround is working.

Using testing and the Centos 8 packages worked for me on Centos 9, however I am not using the k3s install script but just set this via ansible:
[bbennett@kube01]~% cat /etc/yum.repos.d/rancher-k3s-common-testing.repo
[rancher-k3s-common-testing]
async = 1
baseurl = https://rpm-testing.rancher.io/k3s/testing/common/centos/8/noarch
gpgkey = https://rpm-testing.rancher.io/public.key
name = Rancher K3 Common (testing)

the updated k3s-selinux package should now be available in other channels.

Reverted back to stable and everything is good.  Any chance on packaging specifically for centos9?  Probably not a big deal now unless se policies ore dependencies drift more.

authors: 1player KyleSanderson StefanNienhuis askb brandond hbjydev mickare mplinuxgeek nemith vwbusguy


text:
Update to OpenAI package ver. 1.3.3

Upon doing some tests, working with the 1.3.3 version worked much better for me! I'm still having issues with the 8-second timeout on Alexa, don't know how to go around that :(

@k4l1sh What do you think? 1.3.3 documentation is much easier to find, specially for newcomers like me 😄


text:
[statping] hardcoded env causes undesired results

Details
Helm chart name and version:
statping-3.1.1
Container name and tag:
N/A
What steps did you take and what happened:
Defined some values via env: and some via envFrom:
Relevant Helm values:
  env:
    NAME: cajun.pro status
    DESCRIPTION: cajun.pro hosting status page
    VIRTUAL_HOST: https://status.cajun.pro
    DB_CONN: postgres
    DB_HOST: postgres-statping
    DB_DATABASE: postgres
  envFrom:
    - secretRef:
        name: statping

https://github.com/DirtyCajunRice/GitOps-Argo-CD/blob/2ebaec880e25deee3cdba1aa09a44e7237f11449/statping/values.yaml
What did you expect to happen:
for only the values i defined in env to be used
Anything else you would like to add:
N/A
Additional Information:
Adding a check for ENVVARNAME: "-" is going to be too verbose. Some type of globally set var should toggle using all defaults or none. There are workarounds for wiping the env dict like env: ~ but that doesnt work when the chart checks and sets anyway.

This is by design in all Helm charts though: if a chart has a set of default values set in values.yaml, any user-provided values  are overridden and/or appended. Anything that is not provided by the user will then be set to the default value.
The only way we could circumvent that is by not providing any default env values in the chart, and/or comment them out so that they are only provided as a sort of guide.

Ideally we should migrate this over the the common library :)

statping is already migrated ;)
https://github.com/k8s-at-home/charts/tree/master/charts/stable/statping

ignore me, on mobile 😅

Right but some of these values are not something everyone wants to have in a public repo, and the way the priority is set in k8s for env vars the envFrom is overwritten by env

Here is a blatant example:
current code:
https://github.com/k8s-at-home/charts/blob/a3ac7d6c76fcd06a32693a7f4d69746308c96b35/charts/stable/statping/templates/common.yaml#L7-L22
And if you disable postgres... and verbosely disable the environment variables it still is setting the DB_HOST, DB_USER and DB_PASS and DB_DATABASE variables from the postgres chart you arent using.
I would prefer to not have to have my config look like
  env:
    ...
    ADMIN_USER: ""
    ADMIN_PASSWORD: ""
    ADMIN_EMAIL: ""
    DB_USER: ""
    DB_PASS: ""
  envValueFrom:
    ADMIN_USER:
      secretKeyRef:
        name: "statping"
        key: admin-user
    ADMIN_PASSWORD:
      secretKeyRef:
        name: "statping"
        key: admin-password
    ADMIN_EMAIL:
      secretKeyRef:
        name: "statping"
        key: admin-email
    DB_USER:
      secretKeyRef:
        name: "statping"
        key: username
    DB_PASS:
      secretKeyRef:
        name: "statping"
        key: password

it already is unfortunate that i have to define the env values in the first place when realistically all i should have to put is
env:
  ...
envFrom:
  - secretRef:
      name: "statping"

The ultimate statement here is that by forcing all of these to exist in env: you completely disable/negate the common chart's ability to use envTpl, envFrom, and envValeFrom for those variables

I think the answer to your problem is to open a PR and comment out the envars in the valurs.yaml, no?

@onedr0p i just updated my answer with a solution

authors: DirtyCajunRice bjw-s onedr0p


text:
Add Speedtest-Exporter or replace the existent

Details
Helm chart name:
Speedtest-Exporter
Describe the solution you'd like:
Would be possible to add https://github.com/MiguelNdeCarvalho/speedtest-exporter/ ?
Thanks,
MiguelNdeCarvalho

I believe this is possible, I will change the chart over to the common library too.

Nice thanks


text:
operator project-quay (3.8.8)

Add 3.8.8 to community operators

/merge possible

/merge possible

authors: framework-automation quay-devel


text:
feature: Create a Helm Chart for k8sgtp in cluster deployment

Checklist:

[x] I've searched for similar issues and couldn't find anything matching
[x] I've discussed this feature in the #k8sgpt slack channel

Is this feature request related to a problem?

[x] Yes
[ ] No

Describe the solution you'd like

Since we are covering the in-cluster K8sgpt deployment, it will be beneficial having also a helm chart where we can deploy K8sgpt.
We can use tools like helmify and also have the Helm Chart creation taking place when we merge in master with a pipeline to automate the process
Benefits for the project and its users

Two main benefits,

Seamless K8sgpt deployment with Helm chart, many people are leveraging HELM for their K8s workloads so supporting this use case will be beneficial
A way to parameterise the K8sgpt deployment. For example, control creation of serviceMonitor and enable further parameterization in the future

Potential drawbacks

Additional context

Hey @arbreezy! I would like to work on this.

@rakshitgondwal ofc.
Just to add on my initial take, I think to begin with a manual helm chart will suffice.
My main concern was the way we cut releases which is quite streamlined so we either manually bump the appVersion with every release to correspond to latest k8sgpt image or we find a way to bump it automatically when we merge to master or we have a new release.

There's already a PR closing this issue raised by @TylerGillson, so unassigning myself.

authors: arbreezy rakshitgondwal


text:
NettyTlsClientAuthTest fails because cassandra script is not executable

(Encountered on MacOS, this might be system-dependent.)
NettyTlsClientAuthTest requires a local distribution of Cassandra, that gets downloaded and untarred by the Maven build. However, there seems to be an issue when making the startup script executable:
[INFO] --- maven-antrun-plugin:3.0.0:run (download.cassandra.bin) @ datastax-mgmtapi-server ---
[INFO] Executing tasks
[INFO]     [mkdir] Created dir: management-api-for-apache-cassandra/management-api-server/.cassandra-bin
[INFO]       [get] Getting: https://archive.apache.org/dist/cassandra/3.11.15/apache-cassandra-3.11.15-bin.tar.gz
[INFO]       [get] To: management-api-for-apache-cassandra/management-api-server/.cassandra-bin/apache-cassandra-3.11.15-bin.tar.gz
[INFO]     [untar] Expanding: management-api-for-apache-cassandra/management-api-server/.cassandra-bin/apache-cassandra-3.11.15-bin.tar.gz into management-api-for-apache-cassandra/management-api-server/.cassandra-bin
[ERROR]     [chmod] Result: 137

The offending instruction is:
<chmod file=".cassandra-bin/apache-cassandra-${cassandra3.version}/bin/cassandra" perm="777"/>

As a result, the test fails with a message saying that CASSANDRA_HOME is not set.
TODO:

make the POM fail if the ANT script fails (there is probably an option for that)
find out why the chmod is failing and fix it

An easy workaround is to fix the permissions manually:
chmod +x management-api-server/.cassandra-bin/apache-cassandra-3.11.15/bin/cassandra

@burmanm ran into this I believe as well. I think this is a MacOS thing as it's not a problem on Linux.


text:
Move publishing Docker images to K8ssandra org

This relocates Docker images into the K8ssandra repo.
Fixes #96

@jdonenine @bradfordcp I'd appreciate a review on this before merging. Particularly on the naming/tagging of Docker images.
For example, the 4.0 images are deployed to DockerHub here:
https://github.com/k8ssandra/management-api-for-apache-cassandra/pull/99/files#diff-db56167851b2143359151cc30a7c672cff85bd15f7051a2580cc42792b162540R74-R77
The 3.11.x images each have their own deployments, similar to this:
https://github.com/k8ssandra/management-api-for-apache-cassandra/pull/99/files#diff-db56167851b2143359151cc30a7c672cff85bd15f7051a2580cc42792b162540R97-R98
All images (except the DSE image) will now be published to k8ssandra/cass-mgmt-api, with 2 tags applied:

a simple tag of x.y.z that correlates to the associated Cassandra version
an extended tag of x.y.z-mgmtapi_version

where mgmtapi_version is whatever version tag is applied to this GitHub repository project. For example, the next release of Management API will be v0.1.24. So the image tags will be:
k8ssandra/cass-mgmtapi:3.11.7
k8ssandra/cass-mgmtapi:3.11.7-v0.1.24
k8ssandra/cass-mgmtapi:3.11.8
k8ssandra/cass-mgmtapi:3.11.8-v0.1.24
k8ssandra/cass-mgmtapi:3.11.9
k8ssandra/cass-mgmtapi:3.11.9-v0.1.24
k8ssandra/cass-mgmtapi:3.11.10
k8ssandra/cass-mgmtapi:3.11.10-v0.1.24
k8ssandra/cass-mgmtapi:4.0.0
k8ssandra/cass-mgmtapi:4.0.0-v0.1.24

The DSE image will stay in the datastax DockerHub repo, and stay named dse-mgmtapi-6_8. Unless we want to change the name/tag on that as well.

After some discussion, the image name will be changed to cass-management-api


text:
Adress Book

Please search to check for an existing issue (including closed issues, for which the fix may not have yet been released) before opening a new issue: https://github.com/k9mail/k-9/issues?q=is%3Aissue
Expected behavior
Tell us what should happen
An inbuilt adressbook would be an advantage.
Actual behavior
Tell us what happens instead
None available
Steps to reproduce

Environment
K-9 Mail version: 5.207
Android version: 6+
Account type (IMAP, POP3, WebDAV/Exchange):

An inbuilt adressbook would be an advantage.

For what reason?
It's a lot of work to allow Contacts to exist outside of Android Contacts.
Even if we implemented a separate Contacts database we'd end up writing more code to sync between the two.
I don't see many practical benefits for this.

I got your point. It just would be comfortable for me.
thanks for your work

What's your problem with using the default Android address book?

i don't find a link in the K9 app connecting the address book.

Just start typing into the "To" field and suggestions from your Android address book will pop up. That should solve your issue

i don't use/have an addressbook just for emails. Only my telephone contacts where i don't store email addresses until now.

I actually left a comment recently regarding this in the K9 Google Group, and I'd argue it is a useful thing to have.
Sometimes I can't remember the addresses I'd like to send to and/or have to send to a bunch of them. Opening the address list in the stock e-mail app and selecting the recipients is a fast and very intuitive solution to do so. Apart for that, though, the stock app fails in almost everything else (hence K-9).
Of course, if it's time-consuming to code this, one can easily survive without it. It would be nice to have it, so I would humbly request that you at least consider it in the future if enough people report it.

@frothfrenzy I'm pretty sure this is never going to be implemented. I'm surprised it hasn't been closed already.
Your usecase seem to be a bit different than the original poster's one, but still when you are composing new email, "To" field is automatically filled up with possible matches from your default contacts list.

@pixelipo Yes, this is how I use it at a moment, works great for what it is. Though I would always prefer if there was a browsable list in addition to it, either by filtering mail addresses from existing contacts or having an address book of its own.
In any case, thank you for the response.

That would be a useful feature, however, it sounds more like something a contacts app should do

My issue is, that I have very few emails in my adressnook, it would be great if all email adresses I send emails to or received from would be suggested in the To field. I think that's also what the others meant. This it's common behavior in eg Outlook

authors: frothfrenzy philipwhiuk pixelipo ueen werano


text:
Update enums.py

Update colour names to the liking of AE

This took me 3 tries because ubisoft is fucking retarded

I did not mean to close it fuck


text:
Command center page throws an error when you open Configuration/Overview in Command center

Download AMQP Gateway from Kaazing.com (4.0.6.57)
Start the gateway and the server.
Login as admin/admin.
Go to configuration/overview.
Javascript error appears:
Error message: Uncaught TypeError: Cannot read property 'cssServiceType' of undefined
URL: http://localhost:8000/commandcenter/js/views.js
Line Number: 2797

@sbadugu This issue also occurs in gateway EE when the 'amqp' service is configured. This is due to the fact that in the constants.js file there is no constant for the amqp.proxy service (there is also no image for this service in the web\commandcenter\images folder).
I attached a screenshot with this alert error.

Command center is going to be deprecated. This won't be fixed.

authors: mgherghe nemigaservices sbadugu

repo: kaazing/gateway


text:
Help make the website better

I would love it if people would help in making the website better in terms of style, content and otherwise.

Thanks to @Pyeskyhigh for working on this. Great work!

repo: kabirnagral/LPXscripts


text:
Added SAML integration

Hi,
Hopefully you'll accept my change; happy to maintain my fork otherwise. This most recent change adds SAML support for single sign on using google or some other authorization provider.

I'm diverging plenty from your code base, and it seems like there isn't much interest for these fixes, so I'm repackaging and maintaining my own fork for now. If things change for you and you'd like to grab my changes, please let me know.

repo: kabukky/journey


text:
code . displays much warnings for Electron/Chromium options in NixOS

https://github.com/kachick/dotfiles/blob/9e56c304d1c13536e5f3ae5934f9317192947595/nixos/desktop/default.nix#L176-L191
https://github.com/NixOS/nixpkgs/blob/b681065d0919f7eb5309a93cea2cfa84dec9aa88/pkgs/applications/editors/vscode/generic.nix#L207-L217
> code .
Warning: 'ozone-platform-hint' is not in the list of known options, but still passed to Electron/Chromium.
Warning: 'enable-features' is not in the list of known options, but still passed to Electron/Chromium.
Warning: 'enable-wayland-ime' is not in the list of known options, but still passed to Electron/Chromium.
Warning: 'disable-features' is not in the list of known options, but still passed to Electron/Chromium.

ref: https://github.com/kachick/dotfiles/issues/689, https://github.com/NixOS/nixpkgs/issues/271461

https://github.com/microsoft/vscode/commit/13bf3f81eea7628de356e43231d9292dbcca4615#diff-788b37ed8722dc4c120edab5e74b4425dd8fb3bf3e391412840bc9a79bf1d11fR16 :thinking:

I don't have any idea, but keeping in open state does not worth values.

repo: kachick/dotfiles


text:
Improvement request : rclone sync

Hello,
Since we are now able to download / upload files, can you please add the rclone sync command to sync Android directories like the SD-card content or a specific folder to a remote server ?
Thanks for rcloneExplorer, it rocks ! :+1:
Regards

This would be an excellent alternative for replacing rclone through termux

Or maybe should you add a terminal to rcloneExplorer to interact with the built-in rclone?

@FoxP
There are already great apps for accessing rclone through terminal, like termux. I made this app to provide GUI for rclone on Android, and I do not intend on adding terminal interface. However sync will be available soon.

Added sync in #193. The feature will be available in the next stable release, and is already available in the current beta release

authors: FoxP Sergi0O kaczmarkiewiczp

repo: kaczmarkiewiczp/rcloneExplorer


text:
Better messaging

This fixes both messaging errors reported by Stu in Slack this morning

Hey @slpopejoy, I was working on dropping the current abbreviation method in favor of a truncated pretty, but I ran into two places that make me nervous. Do you have an opinion on what we should do in these places?
https://github.com/kadena-io/pact/blob/761adfe5dcb93d054e7883a3776c9bf70889f8ae/src/Pact/Native/Ops.hs#L63-L69
https://github.com/kadena-io/pact/blob/761adfe5dcb93d054e7883a3776c9bf70889f8ae/src/Pact/Types/Term.hs#L1006

Do you have an opinion on what we should do in these places?

In both they are abusing abbrev to get a string key -- which if we fix Objects to only have string refs would go away. In any case show is fine/accomplishes same hack.

authors: joelburget slpopejoy

repo: kadena-io/pact


text:
suggestion sentencing update

May read better

Yeah. Thanks.

authors: TimeBandit arunoda

repo: kadirahq/flow-router


text:
Infra: Enable sonar for frontend

Despite the new (?) sonarcloud feature to do an automatic analysis without CI (github in our case) for all the languages in the repo the results for the frontend are ignored. We need to fix that.
https://sonarcloud.io/project/activity?id=kafbat_kafka-ui

@Haarolean I can look into it.

authors: Haarolean timwehrle

repo: kafbat/kafka-ui


text:
License file?

Is PNGTuber-Plus open source? If so what license does it fall under?

@WichitPritchett since you opened this a LICENSE file was uploaded. Should answer what you need (if you still need it)?

authors: Abablabab WichitPritchett

repo: kaiakairos/PNGTuber-Plus

license: Unlicense


text:
Automated commit improvement

Somehow unasuke was an author of the automated commits, now it's bot account (kind of)
Putting commit message itself into the variable so that it can be directly used as YAML string

Somehow unasuke was an author of the automated commits

？！？！？！？！？！？！？！？？？？？？？？？？
https://github.com/kaigionrails/conference-app/commit/6c8324f4c3e1ad82d00fd731f5ea8529d913990f.patch

authors: okuramasafumi unasuke

repo: kaigionrails/conference-app


text:
fix: 🐛 New Docker CentOS 7 repository

Notice: Shutting down dockerproject.org APT and YUM repos 2020-03-31
BREAKING CHANGE: 🧨 https://www.docker.com/blog/changes-dockerproject-org-apt-yum-repositories/
✅ Closes: #77
✅ Closes: #79

LGTM!

repo: kairen/kubeadm-ansible


text:
MySQL アクセス情報の削除

パスワードとユーザー直書きはさすがにやばいのでそろそろ環境変数から取るように変更する

Done


text:
Support code lenses

see: https://vscode.rocks/codelens/
It would be great to be able to use code-lenses in kakoune!
In nvim they're rendered as "virtual text" hanging off the end of lines.

See here for a discussion on virtual text: https://github.com/mawww/kakoune/issues/1813

added as of ab07f913 (Support LSP code lenses, 2022-04-28)

Wow, thanks!
On Tue, 3 May 2022, 7:06 am Johannes Altmanninger, @.***>
wrote:

Closed #490 https://github.com/kak-lsp/kak-lsp/issues/490.
—
Reply to this email directly, view it on GitHub
https://github.com/kak-lsp/kak-lsp/issues/490#event-6536781755, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAGRJXHLT7MFXJJBL4MJ4DLVIBNYTANCNFSM453YYZ4A
.
You are receiving this because you authored the thread.Message ID:
@.***>

This doesn't seem to work.  Using v12.2.0, when I run the lsp-code-lens command (or type ,ll), with the cursor on the line marked by >, I get an empty lsp-menu-select menu.
This used to work.  On April 28th, the head of your code-lens branch was commit d7fb3b56a85c21299838c414d2379fa6ad28ed1c.  (This doesn't appear to be in your branch history, but it can be directly checked out.)  While the unicode gutter character you had at that time caused issues, the lsp-code-lens command itself worked.

My bad I should have added a test. Fixed as of ed1fb46a7ce0821e11ad96da31b12b917dbdb245

Yep, that works for me.  Thanks for the quick fix!

authors: Rotaerk expipiplus1 krobelus

repo: kak-lsp/kak-lsp


text:
[refactor] 키워드로 필터링한 여행치 추천 조회 요청 API 결과를 캐싱하여 성능을 최적화

🕹 구현할 기능
키워드로 필터링한 여행치 추천 조회 요청 API 결과의 성능을 개선하고자 합니다. 요청 내용을 로컬 캐시로 캐싱하여, 성능을 최적화합니다.
🛠 상세작업내용

[x] 로컬 캐시 Hit/Miss 관련 학습
[x] 로컬 캐시 최적화

⏰ 예상소요시간
8시간
📄 참고자료
No response

#425 에서 중복되는 내용이라 이슈 클로즈합니다


text:
Nominal classes

#126 adds allowing creating classes as a type which can be referenced
As of #126 they are treated as being nominal. Given
class X { a: number = 2 }

The only two cases of types where instance passes is for
const x: X = instance

is when

Type::Constant has a base type (there is a function in the code which does this) that is X. (this is because string, number and boolean are treated as special classes)
Type::Object where the information.prototype.get(object_type_id) is X

Therefore it does not perform property checks for let x: X = { a: 2 } and so will raise a type error. However it only works one way, so let x: { a: number } = new X is fine.

There is also some benefit to the variable_current_value and side effect system which means that shouldn't create to many issues. For let x: { a: number } = new X, x still has the class instance of X type as it doesn't widen.

This can simplify things. In the future:

The methods on X can be treated as a known function and therefore know the side effects (if they are already registered)

However TypeScript allows both ways. There may be a way in the future for a CLI flag to check properties (and also drop that for (x: Set<number>) => x.add x.add might not be the Set.prototype.add function)

This is now implemented. This hopefully allows the checker to assume methods on Array etc have known effects.
Might need revisiting, but good for now 👍

repo: kaleidawave/ezno


text:
[pending] run ica

can merge only after #3 and rebasing

Rebased onto main. Ready for review, @levchenkoegor.

Do we use somewhere ZipPath?
It is imported on line 4:
from zipfile import ZipFile, Path as ZipPath

At my local brunch everything works well - can be merged.

authors: kalenkovich levchenkoegor

repo: kalenkovich/reproduced-MEEG-group-study


text:
Init

Ik moet m nog testen, maar alvast een draft. Er zijn 3 specifieke usecases:

Image: afbeelding met height: auto
ImageFixedAspectRatio: afbeelding met een fixed height, gebaseerd op een aspect ratio (om het aantal crops onder controle te houden)
ImageCover: afbeelding met height: auto, en object-fit: cover. De height is hierbij variabel. Hiervoor kan niet Image gebruikt worden, omdat de bereking voor je sizes attribuut anders is, omdat je afbeelding in sommige gevallen wordt opgeblazen.

ImageFixedAspectRatio is gerenamed naar ImageCropped

repo: kaliberjs/sanity-image


text:
Publishing apk to Google is no more working

Since the API changed:
[!] Google Api Error: apiDeprecated: This version of the Play Developer API is no longer available. For more information see https://android-developers.googleblog.com/2019/03/changes-to-google-play-developer

https://medium.com/@AndreSand/automate-publishing-app-bundle-or-apk-to-google-play-store-8641f0ba2f64

repo: kalisio/kApp


text:
Add dependency injection site for FatFs

Currently, FatFs is hard coded to work with an SD card.
That SD card library is also hardcoded to use the SSP interface for LPC40xx.
To allow this to be multi platform there must be some way to do the following:

Inject your own version of the disk_io at runtime without having to modify diskio.cpp in 3p/fatfs. Possibly having
Use of a lookup table for which the developer can specify the size that will lookup the correct device to communicate with depending on the drive number.

Partially resolved by #448. The injection point is the diskio.cpp file within each platform folder. This way any platform can implement their own means of handling the FatFS implementation.
This doesn't help if your application uses more media than what the default platform provides though. Should probably still inject this from startup and allow applications to inject their own once main is called.


text:
Generator audio samples at 100k iterations

Many of these GAN vocoders here always start with pertaining their corresponding generator up to 100k iterations. I am curious if anyone can upload some audio samples generated from this pertained generator using the auxiliary loss alone.
I want to know if I'm headed to the right direction. Thank you!

Usually, prtrained generators produce synthetic sounds with a lot of mechanical sounds.

You can check my google drive.
https://drive.google.com/drive/folders/1q_SUadUjEdbykHsfVxuIM7n6vtzgfK5L?usp=sharing

authors: LLianJJun francislata kan-bayashi

repo: kan-bayashi/ParallelWaveGAN


text:
Clippy lint clippy::str_to_string fails on generated commands with String arguments

I run a fairly extensive set of lints on my projects. Since updating Poise from 2746481a6cef9c141ac7940b5f1eed240dff33a8 to 60106518ea0ec5940682a724c257b246ff8ac2b2, I've found  that the lint clippy::str_to_string warns for commands that have String arguments.
#![warn(clippy::str_to_string)]

#[command(prefix_command)]
pub async fn some_command(
	ctx: PoiseContext<'_>,
	#[rest]
	#[description = "Some description."]
	command: String,
) -> Result<(), Error> {
	Ok(())
}

Warns with the following error:
warning: `to_string()` called on a `&str`
  --> src\commands\mod.rs:40:1
   |
40 | #[command(prefix_command)]
   | ^^^^^^^^^^^^^^^^^^^^^^^^^^
   |
   = help: consider using `.to_owned()`
   = help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#str_to_string
   = note: this warning originates in the macro `$crate::_parse_prefix` (in Nightly builds, run with -Z macro-backtrace for more info)

It seems to only be with prefix_command, not slash_command. Not a huge deal at all, but I thought I'd mention it.

Thanks for the report
Fixed in 7830e76010621ca8a380ef537534ae1ed9b725e9
If you don't mind, can you give me the list of clippy lints you use? I'll put them into the example code to make sure the generated code doesn't trigger them again

Sure, here's the list I'm running: https://github.com/zedseven/radium/blob/dev/src/main.rs#L4-L38
Keep in mind these are partly personal preference and there's quite a few, so you don't have to set them up.

authors: kangalioo zedseven

repo: kangalioo/poise


text:
step is lost while being edit in workflow fork action

When a workflow is forked , steps can be edited. If a step is the main one, and user updates it;s script, whne saving an error message appears "there is already a main step for this workflow". If after that the workflow is saved that steps is no longer in place.

confirmed

A solution is to make node.data.main=false; for all steps that are DnDed from other WFs.
A side-effect is that we would not be able to locate the main steps of non-root WFs.
A solution to this is to visually distinguish the main steps of the root WF, with the main steps of non-root WFs.
A possible schema is:

main step of a root WF: RED BORDER
main step of a non-root WF: BLACK BORDER

The "If after that the workflow is saved that steps is no longer in place." is a separate bug..
How to reproduce:

Create a WF with a step that is NOT main
Add a step thay is main
Click the "non-main" step
Click the main check box
Click update

The node is deleted

authors: giatrakister kantale

repo: kantale/OpenBioC


text:
fix: Add redis db number to url

It looks like the database number has to be in the pathname even though there is an option to pass it in as options.
This PR keeps the database number in the options object and adds it to the URL as well.

Closing as this was not the issue

repo: kapetacom/sdk-nodejs-redis


text:
Add support for styles

This adds support for styles for the pins as given in the shields.io site. It's pretty easy to use, you just need to add a style parameter to the end of the url.
Example:
http://sopins.herokuapp.com/twitter/https://www.google.com/pin.png?style=flat-square
http://sopins.herokuapp.com/twitter/https://www.google.com/pin.png?style=plastic

Also, you haven't pushed the LinkedIn changes to Heroku.. It's showing a 500 server error.

Also, All your classes now inherit from object for better Python 2 and 3 compatibility.

Also in your requests.exceptions.HTTPError error handling, you were returning self.write_shield which should be simply write_shield.

Can you update the README and add a sample of using flat buttons?

Sure..

README updated.

authors: geekpradd karan

repo: karan/sopins


text:
Tried to remove the unwanted characters from the integer array but getting the error

Below is the function and its returning the integer values with %.
def functions = []
eval for(var i=0; i<response.functions.length; i++) functions.add(response.functions[i].value) *print functions
It's return the below output. ['2.16%','1.34%','1.32%','1.25%','0.65%','0.48%','0.42%','0.26%','0.14%','0.06%','0.03%','0%']
I want to remove the single codes and % symbol. After removing it should be like below. [2.16,1.34,1.32,1.25,0.65,0.48,0.42,0.26,0.14,0.06,0.03,0]
Tried below code to remove the single codes and % symbol. But getting the error : Failed generating bytecode for :1

def response = ['2.16%','1.34%','1.32%']
def cleaned = response.map(x => x.replace('%', '') * 1)
match cleaned == [2.16, 1.34, 1.32]

@saiimmadi follow the process exactly as described here to reopen: https://github.com/karatelabs/karate/wiki/How-to-Submit-an-Issue

authors: ptrthomas saiimmadi

repo: karatelabs/karate


text:
Update dependencies

This change is

bors r+

repo: karen-irc/option-t


text:
fix argument of type 'float' is not iterable

fix "argument of type 'float' is not iterable" in show_balance_handle and message_handle

Nice. Thank you!

authors: TanNhatCMS karfly


text:
orgparse.load() generates a ResourceWarning when called with a text file

Consider the attached files testorgparse.py and test.org.
The file testorgparse.py is a simple test of orgparse.load() on an external text file test.org using unittest. It contains the following:
import orgparse
import unittest
import os

class TestLoadOrgFile(unittest.TestCase):
    """A class for testing check_org_file"""

    def test_check_org_file_ok(self):
        file_dir = os.path.dirname(os.path.abspath(__file__))
        test_file = os.path.join(file_dir,"test.org")
        s = orgparse.load(test_file)

if __name__ == "__main__":
    # Run self-tests
    unittest.main()

The file test.org is a simple, one-line org file and should reside in the same directory as testorgparse.py. Then, the call below generates a ResourceWarning due to an unclosed file in loadparse.load():
$ python3 testorgparse.py
testorgparse.py:11: ResourceWarning: unclosed file <_io.BufferedReader name='/home/user/python/test.org'>
  s = orgparse.load(test_file)
ResourceWarning: Enable tracemalloc to get the object allocation traceback
.
----------------------------------------------------------------------
Ran 1 test in 0.004s

OK

The pushed code fixes the warning by enclosing codecs.open() by a with statement.
This is the output with the modified code:
$ python3 testorgparse.py
.
----------------------------------------------------------------------
Ran 1 test in 0.000s

OK

test_load.zip

thanks, good catch!
I guess in theory would be nice if it was iterative (presumably then loadi would have to be under with block as well). However seems that readline always converts to a list anyway, so this change is OK!

authors: karlicoss niclasborlin

repo: karlicoss/orgparse


text:
Addressing memory leaks

Related to https://github.com/mochajs/mocha/issues/1991
Is there any way we could reasonably expose the the runner (from mocha.run(..)) so that we can delete suite properties as mentioned in the linked issue?

+1 On this one. This hurts on large test suites.

@rcollette @tarjei is issue still actual?

@maksimr good question. It seems to me to at least have become better. I've done a number of tricks to improve test performance, and I'm not sure if the memory leaks are as big as they used to.
But, I think that is a very good idea to be able to access the runner for testsuite cleanups.
T

Thanks,
I think this problem could be solved on project(client) side.
You can simple put code below to your test-main.js
var orgMochaRun = mocha.run

mocha.run = function (fn) {
  var runner = orgMochaRun(fn)

  runner.on('suite end', function (suite) {
    delete suite.tests
    delete suite._beforeAll
    delete suite._beforeEach
    delete suite._afterEach
    delete suite.ctx
    delete suite._afterAll
  })

  return runner
}

@maksimr, you didn't give me much time to response.  It is absolutely still an issue and I have also tried the delete code above and it didn't work.  In fact, we finally wound up having to split our unit tests (4k+) into separate runs.   Kind of a problem when you have two groups and you want to use a .only as the group not containing the .only will still run all tests.

@rcollette as I understand memory leaks inside mocha's runner and you want get access to this runner inside your tests, yes?
Code above only show how get access to runner from test code
var orgMochaRun = mocha.run
var runner;

mocha.run = function (fn) {
  runner = orgMochaRun(fn)
  return runner
}

Thanks

authors: maksimr rcollette tarjei

repo: karma-runner/karma-mocha


text:
Proposition - create sbt-publish.bat

There is one proposition to make an additional file named "sbt-publish.bat" that will run:
sbt clean update compile package publish-local
So afte git pull, we can simply call sbt-publish.bat.
Maybe it is very small, but can be useful until package published publicly.
makese sense?

Yes it makes sense thank you. I am on a linux system so I am not 100% sure how to set this up, but I guess it should be something like this
set SCRIPT_DIR=%~dp0
java -XX:+CMSClassUnloadingEnabled -XX:MaxPermSize=256m -Xmx712M -Xss2M -jar "%SCRIPT_DIR%\sbt-launch.jar" clean update compile package publish-local
Could you try it out ? and I make a eqv. linux shell script.

Just tried sbt-publish.bat with content you proposed, and it worked like a charm!

Thank you, I will publish it in a few minutes.


text:
Improved loading of config files and CLI parameters

Hi Andrej,
Thank you for this project. According to configurator.py, you are looking for a better, simpler Python solution to  parameter loading.
This PR introduces argparse for parameter loading, while still adhering to the constraints of the original code (overwriting globals, not having to write config.[param], optional loading from param files).
By using argparse, it is very easy to get an overview over all the tunable variables, their types and their defaults:
$ python3 train.py -h
usage: train.py [-h] [--config_files [CONFIG_FILES ...]] [--out_dir] [--eval_interval] [--log_interval] [--eval_iters] [--eval_only]
                [--always_save_checkpoint] [--init_from] [--wandb_log] [--wandb_project] [--wandb_run_name] [--batch_size] [--max_seq_len] [--dim]
                [--n_layers] [--n_heads] [--multiple_of] [--dropout] [--gradient_accumulation_steps] [--learning_rate] [--max_iters] [--weight_decay]
                [--beta1] [--beta2] [--grad_clip] [--decay_lr] [--warmup_iters] [--device] [--dtype] [--compile]

options:
  -h, --help            show this help message and exit
  --config_files [CONFIG_FILES ...]
  --out_dir             str (default: out)
  --eval_interval       int (default: 2000)
  --log_interval        int (default: 1)
  --eval_iters          int (default: 100)
[... snip ...]

Basic usage example:
$ cat config/test_config1.py
beta1 = 0.12345

$ cat config/test_config2.py
beta1 = 0.98765

$ python3 train.py --config_files config/test_config1.py config/test_config2.py

-----------------------------------------------------
Loaded from extra config file config/test_config1.py:
-----------------------------------------------------
{'beta1': 0.12345}

-----------------------------------------------------
Loaded from extra config file config/test_config2.py:
-----------------------------------------------------
{'beta1': 0.98765}

-----------------------------------
Loaded from CLI params:
-----------------------------------
{'config_files': ['config/test_config1.py', 'config/test_config2.py']}

-----------------------------------
Full config:
-----------------------------------
{'always_save_checkpoint': False,
 'batch_size': 128,
 'beta1': 0.98765,
 'beta2': 0.95,
 'compile': True,
 'decay_lr': True,
 'device': 'cuda',
 'dim': 288,
 'dropout': 0.0,
 'dtype': 'bfloat16',
 'eval_interval': 2000,
 'eval_iters': 100,
 'eval_only': False,
 'grad_clip': 1.0,
 'gradient_accumulation_steps': 4,
 'init_from': 'scratch',
 'learning_rate': 0.0005,
 'log_interval': 1,
 'max_iters': 100000,
 'max_seq_len': 256,
 'multiple_of': 32,
 'n_heads': 6,
 'n_layers': 6,
 'out_dir': 'out',
 'wandb_log': False,
 'wandb_project': 'llamac',
 'wandb_run_name': 'run2023_07_24_01_24_26',
 'warmup_iters': 1000,
 'weight_decay': 0.1}
[... snip ...]

Optional override from CLI:
$ python3 train.py --config_files config/test_config1.py config/test_config2.py --beta1=0.999

-----------------------------------------------------
Loaded from extra config file config/test_config1.py:
-----------------------------------------------------
{'beta1': 0.12345}

-----------------------------------------------------
Loaded from extra config file config/test_config2.py:
-----------------------------------------------------
{'beta1': 0.98765}

-----------------------------------
Loaded from CLI params:
-----------------------------------
{'beta1': 0.999,
 'config_files': ['config/test_config1.py', 'config/test_config2.py']}

-----------------------------------
Full config:
-----------------------------------
{'always_save_checkpoint': False,
 'batch_size': 128,
 'beta1': 0.999,  # <-------- beta1 is set from CLI
 'beta2': 0.95,
 'compile': True,
 'decay_lr': True,
 'device': 'cuda',
 'dim': 288,
 'dropout': 0.0,
 'dtype': 'bfloat16',
 'eval_interval': 2000,
 'eval_iters': 100,
 'eval_only': False,
 'grad_clip': 1.0,
 'gradient_accumulation_steps': 4,
 'init_from': 'scratch',
 'learning_rate': 0.0005,
 'log_interval': 1,
 'max_iters': 100000,
 'max_seq_len': 256,
 'multiple_of': 32,
 'n_heads': 6,
 'n_layers': 6,
 'out_dir': 'out',
 'wandb_log': False,
 'wandb_project': 'llamac',
 'wandb_run_name': 'run2023_07_24_01_25_25',
 'warmup_iters': 1000,
 'weight_decay': 0.1}
[... snip ...]

Warning: Code is only superficially tested right now, there might be some unintended side effects.

Hi I appreciate the attempt but I don't think it's simpler. The benefit of seeing the args in console (vs just reading the code) is very small.

authors: karpathy tringwald


text:
Add new parameter to convert function

I noticed that png generated by convert have transparent background, when converting PDFs with white background. This is not happening when using jpg, like this:
convert -quiet -density 200 Test.pdf -quality 200 Test.jpg
I would like you to add one more parameter with the file extension.
public static convert(pdfPath: string, outputImgDir: string, outputImgName: string, outputImgExtension: string): any {
.........
outputImgPath + '/' + outputImgName + outputImgExtension,
I attached a test file and the command lines to convert them:
convert -quiet -density 200 Test.pdf -quality 200 Test.jpg
convert -quiet -density 200 Test.pdf -quality 200 Test.png
Test.pdf

Hi, Sorry about the late response i just noticed this issue. I'll push the patch in a bit.
Thanks!

v1.2 will be released later this week.

I appreciate. Thank you.

Can you estimate when you can publish the latest version?

Hello,
Unfortunately, the jpg extension does not solve the transparency issue. I mean it removes transparency but for one example I am working with, it turns the white background of the PDF into black in JPG.
I found this link https://www.imagemagick.org/discourse-server/viewtopic.php?t=31014 that gives a solution for PDFs. Indeed, the below command works better:
convert -density 300x300 -units pixelsperinch Test.pdf -background white -alpha background -alpha off -antialias -compress none +adjoin Test.png
During my tests I found that this one is OK as well:
convert -density 300 -quality 100 Test.pdf -alpha background -alpha off Test.png
What I would like you to do, if you agree, is to add a generic parameter where we can add things like -alpha background -alpha off.
Obviously is up to the user to add correct options here.
Florin


text:
[BUG]Strong password required

Describe the bug
The signup form allows users to create password without any minimum length requirement, which lead to very short and potentially insecure passwords.
To Reproduce

Go to sign up page.
After filling the user name and email.
Move to password input field.
See error.

Screenshots

I would like to work on this issue. Please assign it to me.

Hello, I've fixed this issue!
This is what I've done:
To address the issue of allowing short and potentially insecure passwords, we'll add a minimum password length requirement to the signup form. We'll update the Signup.js file to include a validation check for password length before submitting the form. We'll also add a visual indicator to show the user if their password meets the minimum length requirement.
Here's a summary of the changes:

Add a minimum password length constant
Implement password length validation in the submitHandler function
Add a visual indicator for password strength
Update the password input field to show the strength indicator

I also created pull request: https://github.com/kartikayasijaa/talk-trove/pull/172

[!CAUTION]
Disclaimer: This fix was created by Latta AI and you should never merge before you check the correctness of generated code!

This bug was fixed for free by Latta AI - https://latta.ai/ourmission

repo: kartikayasijaa/talk-trove


text:
Add input signature_script checking to submitTransaction RPC

Closes #452

I suggest the following instead of the above approach:
diff --git a/consensus/Cargo.toml b/consensus/Cargo.toml
index f151e404b..3f4a1b456 100644
--- a/consensus/Cargo.toml
+++ b/consensus/Cargo.toml
@@ -30,6 +30,7 @@ kaspa-muhash.workspace = true
 kaspa-notify.workspace = true
 kaspa-pow.workspace = true
 kaspa-txscript.workspace = true
+kaspa-txscript-errors.workspace = true
 kaspa-utils.workspace = true
 log.workspace = true
 once_cell.workspace = true
diff --git a/consensus/core/src/errors/tx.rs b/consensus/core/src/errors/tx.rs
index ec1899faa..1aeb5220f 100644
--- a/consensus/core/src/errors/tx.rs
+++ b/consensus/core/src/errors/tx.rs
@@ -80,6 +80,9 @@ pub enum TxRuleError {
     #[error("failed to verify the signature script: {0}")]
     SignatureInvalid(TxScriptError),

+    #[error("failed to verify empty signature script. Inner error: {0}")]
+    SignatureEmpty(TxScriptError),
+
     #[error("input {0} sig op count is {1}, but the calculated value is {2}")]
     WrongSigOpCount(usize, u64, u64),

diff --git a/consensus/src/processes/transaction_validator/transaction_validator_populated.rs b/consensus/src/processes/transaction_validator/transaction_validator_populated.rs
index 1835ba61e..586b23e57 100644
--- a/consensus/src/processes/transaction_validator/transaction_validator_populated.rs
+++ b/consensus/src/processes/transaction_validator/transaction_validator_populated.rs
@@ -1,7 +1,11 @@
 use crate::constants::{MAX_SOMPI, SEQUENCE_LOCK_TIME_DISABLED, SEQUENCE_LOCK_TIME_MASK};
-use kaspa_consensus_core::{hashing::sighash::SigHashReusedValues, tx::VerifiableTransaction};
+use kaspa_consensus_core::{
+    hashing::sighash::SigHashReusedValues,
+    tx::{TransactionInput, VerifiableTransaction},
+};
 use kaspa_core::warn;
 use kaspa_txscript::{get_sig_op_count, TxScriptEngine};
+use kaspa_txscript_errors::TxScriptError;

 use super::{
     errors::{TxResult, TxRuleError},
@@ -167,14 +171,21 @@ impl TransactionValidator {
         let mut reused_values = SigHashReusedValues::new();
         for (i, (input, entry)) in tx.populated_inputs().enumerate() {
             let mut engine = TxScriptEngine::from_transaction_input(tx, input, i, entry, &mut reused_values, &self.sig_cache)
-                .map_err(TxRuleError::SignatureInvalid)?;
-            engine.execute().map_err(TxRuleError::SignatureInvalid)?;
+                .map_err(|err| map_script_err(err, input))?;
+            engine.execute().map_err(|err| map_script_err(err, input))?;
         }

         Ok(())
     }
 }

+fn map_script_err(script_err: TxScriptError, input: &TransactionInput) -> TxRuleError {
+    match input.signature_script.is_empty() {
+        true => TxRuleError::SignatureEmpty(script_err),
+        false => TxRuleError::SignatureInvalid(script_err),
+    }
+}
+
 #[cfg(test)]
 mod tests {
     use super::super::errors::TxRuleError;

match input.signature_script.is_empty() {
+        true => TxRuleError::SignatureEmpty(script_err),
+        false => TxRuleError::SignatureInvalid(script_err),
+    }

match bool is always looks weird. Why not use simple if-else?

authors: KaffinPX biryukovmaxim michaelsutton

repo: kaspanet/rusty-kaspa

license: ISC


text:
Cannot find module '@phenomnomnominal/tsquery'

It seems there is a problem with this dependency; on the developer tools there is this error on console:

And looking even more deeper there is no trace of this dependency on node_modules:

maybe it must be a dependency and not a devDependency on the package.json?

can you try again, please?

i tried to uninstall and reinstall, but that dependency continue to not be installed with

I moved the dependencies from dev to dependency.

I tried again to uninstall and reinstall the extension, but the dependency in package.json continue to be a devDependency, i think there is the need to push a new patch version for vscode to recognize the fix in package.json

The problem is still here. Running the extension directly from the code works, but the extension downloaded from the store doesn't. As @MRinaldi9 said, the dependency is still a devDependency. It looks like the GitHub version and the VSCode Market version are not the same.

repo: kasuken/npm-info-lens


text:
containerd-shim-kata-v2 process hangs when open stdin fifo

Description of problem
When doing some benchmark testings, we encountered the containerd-shim-kata-v2 process hangs when open stdin fifo
Expected result
the container is successfully started
Actual result
the ctr run command would hang, the containerd-shim-kata-v2 process is blocked by open stdin fifo

So it is caused by ctr bug, right?

So it is caused by ctr bug, right?

Yes, but I did not dig it why the client does not open it, but it seems also reasonable that make stdin opened with O_NONBLOCK  in kata, at least the starting process of container is not blocked.

repo: kata-containers/runtime


text:
qemu: pass rootfs image in readonly mode

It is wip as it depends on the govmm change https://github.com/intel/govmm/pull/113
I'll rebase once that one is merged.

/test

/test

/test

/test

centos-8-q-35 failure is unrelated and tracked at https://github.com/kata-containers/tests/issues/2328


text:
vendor: update kata agent

Increase dial timeout to fix context deadline exceeded when
using vsocks
Shortlog:
93fe84e protocols: increase dial timeout
730b977 client: bypass grpc dialer backoff strategy
41c09c2 agent: enable memory hierarchical account
4f70b1c channel: remove unused functions
f6486e7 channel: support communication channel hotplug
28afabb release: Kata Containers 1.2.0
fixes #576
Signed-off-by: Julio Montes julio.montes@intel.com

@egernst no, there are not changes in the agent gRPC protocol

lgtm

recheck

recheck

lgtm

authors: chavafg devimc jodh-intel