profile
viewpoint

levex/cgroups-rs 59

Native Rust library for managing control groups under Linux

ordovicia/controlgroup-rs 4

Native Rust crate for operating on cgroups.

ordovicia/hikey960-debian 1

Build Debian Image for HiKey960.

ordovicia/atcoder 0

Solutions for AtCoder (https://atcoder.jp/).

ordovicia/cargo 0

The Rust package manager

ordovicia/cargo-modules 0

A cargo plugin for showing a tree-like overview of a crate's modules.

ordovicia/cargo-watch 0

Watches over your Cargo project's source

delete branch ordovicia/kustomize-controller

delete branch : supress-healthchecks-when-no-changes

delete time in 5 days

pull request commentfluxcd/kustomize-controller

Suppress health check events when no changes made

Ah, right. Thank you. I removed the len(DependsOn) > 0 condition.

ordovicia

comment created time in 10 days

push eventordovicia/kustomize-controller

Hidehito Yabuuchi

commit sha 5ed74635524c6e0332aece563202b89767e8d57c

Suppress health check events regardless of dependencies Because if a dependency is failing, the reconciliation will never get to the health check part.

view details

push time in 10 days

PR opened fluxcd/kustomize-controller

Suppress health check events when no changes made

When no Kubernetes resources are created or configured for a Kustomization and it has no dependencies, the health check status for the Kustomization will not change. In this case kustomize-controller does not have to deliver health check events. What do you think?

+8 -8

0 comment

1 changed file

pr created time in 10 days

push eventordovicia/kustomize-controller

Hidehito Yabuuchi

commit sha 4df55dde113d722d3b80a63e134817ba08c13205

Suppress health check events when no changes made

view details

push time in 10 days

issue openedmarmelab/react-admin

AppBarProps is not exported

<!-- Please do not submit support requests or "How to" questions here. For that, go to Stack Overflow. -->

What you were expecting: <!-- Describe what the behavior would be without the bug. -->

AppBarProps would be exported from ra-ui-materialui here: https://github.com/marmelab/react-admin/blob/9bf186b0522b9c82bf126c21d772dc6ef367ce68/packages/ra-ui-materialui/src/layout/index.ts#L1

What happened instead: <!-- Describe how the bug manifests. -->

AppBarProps is not exported. So I can't assign a proper type to my app bar implementation like this:

import { AppBarProps } from 'ra-ui-materialui'; // error

const MyAppBar: React.FC<AppBarProps> = (props) => {
 ...
};

Other information: <!-- List any other information that is relevant to your issue. Stack traces, related issues, suggestions on how to fix, Stack Overflow links, forum links, etc. For visual or layout problems, please include images or animated gifs.-->

Environment

  • React-admin version: 3.9.3

created time in 15 days

startedfluxcd/image-automation-controller

started time in 17 days

fork ordovicia/source-controller

The GitOps Toolkit source management component

https://toolkit.fluxcd.io

fork in 20 days

delete branch ordovicia/toolkit

delete branch : prep-main

delete time in 20 days

delete branch ordovicia/toolkit

delete branch : rename-tk-to-gotk

delete time in 20 days

delete branch ordovicia/toolkit

delete branch : master

delete time in 20 days

delete branch ordovicia/toolkit

delete branch : gh-pages

delete time in 20 days

delete branch ordovicia/toolkit

delete branch : helmrelease-json-pointer

delete time in 20 days

create barnchordovicia/toolkit

branch : main

created branch time in 20 days

delete branch ordovicia/kustomize-controller

delete branch : master

delete time in 21 days

create barnchordovicia/kustomize-controller

branch : main

created branch time in 21 days

pull request commentfluxcd/flux

Notify upstream of sync failures

@marcosnils Thank you for that information! I use Flux in read-only mode and I believe that GitOps Toolkit will be parity with Flux read-only mode soon. I agree that this PR will be beneficial, so @fdpeiter please feel free to cherry-pick @marcosnils and my commits and open a new PR.

ordovicia

comment created time in a month

PR closed fluxcd/flux

Notify upstream of sync failures

This PR is a substitution of #3145 since the fork of #3145 was deleted. From #3145 description:

Sync can fail for many other reasons besides the manifests not being ok. Some of these errors could be due to some pre processing scripts in the .flux.yaml file or some git checkout errors. This commits logs sync erros and allows upstream log event providers to properly display the errors

Signed-off-by: Marcos Lilljedahl marcosnils@gmail.com

I cherry-picked the commit of #3145 and added commits 7c84304e974f2da371c43fc1a1e33a2082284f37 to include commit info in sync failure event.

+124 -24

3 comments

2 changed files

ordovicia

pr closed time in a month

pull request commentfluxcd/flux

Notify upstream of sync failures

@fdpeiter Hi. Sorry for not being active on this PR. I am just closing this PR as Flux v1 is not actively maintained and I am inclined to migrate to GitOps Toolkit (Flux v2).

ordovicia

comment created time in a month

issue commentfluxcd/kustomize-controller

Option for using `kubectl replace --force` when fail to apply

Ah, you are quite right. Thank you for your explanation.

So, what do you think is the best practice for changing immutable fields when using GitOps Toolkit? Do we need to delete old resources in a reconciliation and add the resources again with new definitions (manifests) in another reconciliation?

ordovicia

comment created time in a month

issue openedfluxcd/kustomize-controller

Option for using `kubectl replace --force` when fail to apply

When we want change immutable fields (e.g. label selector in Deployment), currently we need to take two steps:

  1. Enable garbage collection for a resource and delete the resource from a repository
  2. Add the resource again to the repository with a new definition

It would be great if kustomize-controller does the above operation in one reconciliation by using kubectl replace --force command.

created time in a month

issue commentkubernetes/code-generator

SchemeGroupVersion should change to GroupVersion

/remove-lifecycle stale

ordovicia

comment created time in a month

push eventordovicia/controlgroup-rs

Hidehito Yabuuchi

commit sha 010f72a2b4766088a9c1123f284fe12fc3af6cc8

[WIP] Make docs concise

view details

push time in a month

issue commentlevex/cgroups-rs

Status of the repository?

JFYI: I forked this project into https://github.com/ordovicia/controlgroup-rs and redesigned the whole project. The interface is incompatible.

bergwolf

comment created time in a month

created tagordovicia/controlgroup-rs

tagv0.3.0

Native Rust crate for operating on cgroups.

created time in a month

startedmarmelab/react-admin

started time in a month

fork ordovicia/kustomize-controller

Experimental Kubernetes operator for building GitOps pipelines with Kustomize

https://toolkit.fluxcd.io

fork in 2 months

fork ordovicia/toolkit

Experimental toolkit for assembling CD pipelines the GitOps way

https://toolkit.fluxcd.io

fork in 2 months

startedColorlibHQ/AdminLTE

started time in 2 months

PR opened fluxcd/flux

Notify upstream of sync failures

This PR is a substitution of #3145 since the fork of #3145 was abondoned. From #3145 description:

Sync can fail for many other reasons besides the manifests not being ok. Some of these errors could be due to some pre processing scripts in the .flux.yaml file or some git checkout errors. This commits logs sync erros and allows upstream log event providers to properly display the errors

Signed-off-by: Marcos Lilljedahl marcosnils@gmail.com

I cherry-picked the commit of #3145 and added commits 7c84304e974f2da371c43fc1a1e33a2082284f37 to include commit info in sync failure event.

+124 -24

0 comment

2 changed files

pr created time in 2 months

create barnchordovicia/flux

branch : sync-error-upstream-log

created branch time in 2 months

pull request commentfluxcd/flux

Log even when sync fails

@marcosnils Thank you for your quick response! I have just asked the maintainers on the Slack. I will resolve the merge conflict if they agree to merge this PR.

marcosnils

comment created time in 3 months

pull request commentfluxcd/flux

Log even when sync fails

Hi @marcosnils -- what do you think about merging topfreegames/flux#1 on top of this PR?

marcosnils

comment created time in 3 months

delete branch ordovicia/pftaskqueue

delete branch : config-path-from-env-var

delete time in 3 months

pull request commentpfnet-research/pftaskqueue

Set config file path via PFTQ_CONFIG env var

Thank you for your quick response.

I came up with three options:

  1. PFTQCONFIG
  2. PFTASKQ_CONFIG
  3. PFTASKQUEUE_CONFIG

I am a little inclined to the option 1 because it is the most concise. c69882391f47a18ee2a5b4f0c4ec83fda73a0b5c changes the environment variable name to PFTQCONFIG.

But I am fine with other names. What name do you think is the best?

ordovicia

comment created time in 3 months

push eventordovicia/pftaskqueue

Hidehito Yabuuchi

commit sha c69882391f47a18ee2a5b4f0c4ec83fda73a0b5c

Rename PFTQ_CONFIG env var to PFTQCONFIG

view details

push time in 3 months

delete branch ordovicia/flux

delete branch : issue-3184-mitigation

delete time in 3 months

PR opened pfnet-research/pftaskqueue

Set config file path via PFTQ_CONFIG env var

With this PR merged, pftaskqueue will read PFTQ_CONFIG environment variable (if set) to get the path of a config file. --config flag is prioritized over PFTQ_CONFIG env var, so this change should not break the current behavior.

This feature would be useful when one does not want to place .pftaskqueue.yaml on a home directory and does not also want to type --config=... flag every time.

+8 -3

0 comment

2 changed files

pr created time in 3 months

create barnchordovicia/pftaskqueue

branch : config-path-from-env-var

created branch time in 3 months

pull request commentfluxcd/flux

Do not return error when failed to load last-synced resources

Rebased.

ordovicia

comment created time in 3 months

push eventordovicia/flux

Michael Bridgen

commit sha 947739b119628433e5ebd3031b9cd77726615627

Get shellcheck from new URL .. at the request of the author. NB the arch in the URL is fixed, which may need attention at some point.

view details

Michael Bridgen

commit sha 87cacd9b522c5982456a7b9bb3dca27fc54981f9

Merge pull request #3224 from fluxcd/update-shellcheck-url Get shellcheck from new URL

view details

Hidehito Yabuuchi

commit sha 8e0ee62e378804767c0dd27c435fedfc6d668022

Do not return error when failed to load last-synced resources

view details

push time in 3 months

pull request commentfluxcd/flux

Log even when sync fails

I would love to see this PR merged!

I opened a PR topfreegames/flux#1 on top of this PR. With my PR, the sync events will include commit info.

marcosnils

comment created time in 3 months

PR opened topfreegames/flux

Include commits in sync failure events

It would be nice to include commit info in sync failure events.

This PR is on top of fluxcd/flux#3145 and will include commits in sync events that are emitted when sync fails.

+26 -11

0 comment

1 changed file

pr created time in 3 months

push eventordovicia/flux

Hidehito Yabuuchi

commit sha cb82da60d5ec12a2abed7312c73af4f2baad6bbf

Include commits in sync failure events

view details

push time in 3 months

create barnchordovicia/flux

branch : sync-fail-event-include-commits

created branch time in 3 months

pull request commentfluxcd/flux

Do not return error when failed to load last-synced resources

e2e tests failed because of outdated ShellCheck.

You are downloading ShellCheck from an outdated URL!

Please update to the new URL: https://github.com/koalaman/shellcheck/releases/download/v0.7.0/shellcheck-v0.7.0.linux.x86_64.tar.xz

For more information, see: https://github.com/koalaman/shellcheck/issues/1871

PS: Sorry for breaking your build. The hosting costs were getting out of hand :(

ordovicia

comment created time in 3 months

PR opened fluxcd/flux

Do not return error when failed to load last-synced resources

This PR is a mitigation for a bug described in #3184 . With this PR merged, Flux will emit warning log and not return error when it fails to load last-synced resources.

cc @squaremo

+2 -1

0 comment

1 changed file

pr created time in 3 months

create barnchordovicia/flux

branch : issue-3184-mitigation

created branch time in 3 months

more