profile
viewpoint
If you are wondering where the data of this site comes from, please visit https://api.github.com/users/dzhlobo/events. GitMemory does not store any data, but only uses NGINX to cache data for a period of time. The idea behind GitMemory is simply to give users a better reading experience.
Dmitry Zhlobo dzhlobo @datarockets Minsk, Belarus https://dima.zhlobo.net CTO @datarockets

datarockets/dreact 7

Build web applications as easy as datarockets do 🚀

dzhlobo/tau 5

Tool for web designers want to use haml, sass, coffee-script and others.

dzhlobo/dotfiles 1

My config files for git, zsh and others

dzhlobo/imperavi-rails 1

Imperavi wysiwyg editor for Rails 3.1+

dzhlobo/sublime-text-2-git 1

Plugin for some git integration into sublime text 2

dzhlobo/active_merchant 0

Active Merchant is a simple payment abstraction library extracted from Shopify. The aim of the project is to feel natural to Ruby users and to abstract as many parts as possible away from the user to offer a consistent interface across all supported gateways.

dzhlobo/calendar_helper 0

Calendar-generating plugin for Ruby

startedtestdouble/suture

started time in 11 days

startedpulumi/pulumi

started time in 14 days

startedterraform-linters/tflint

started time in 16 days

issue commentNXPmicro/mfgtools

New release due to a fix for M1 macs

@nxpfrankli, yes, there's no difference in git and tarball but homebrew has additional checks specifically for GitHub. It parses tarball url, detects that it is from GitHub and pulls meta information about the GitHub release.

It wouldn't be a problem if I upgrade version of an existing package but homebrew is much more strict to new packages. I've also posted a comment in the pull request to homebrew-core, maybe maintainers will comment.

dzhlobo

comment created time in a month

pull request commentHomebrew/homebrew-core

uuu 1.4.139 (new formula)

Maintainers of uuu created a "pre-release" 1.4.149 on GitHub but it seems pre-release versions aren't allowed in homebrew-core unless they are mentioned in exceptions list. So I guess I'll have to wait until 1.4.149 becomes "latest" release.

$ brew audit --new uuu
uuu:
  * uuu_1.4.149 is a GitHub pre-release.
Error: 1 problem in 1 formula detected
dzhlobo

comment created time in a month

issue commentNXPmicro/mfgtools

New release due to a fix for M1 macs

@nxpfrankli, thank you ❤️. I can successfully build homebrew formula locally and uuu seems working. Unfortunately, it seems pre-release versions aren't allowed in homebrew-core:

$ brew audit --new uuu
uuu:
  * uuu_1.4.149 is a GitHub pre-release.
Error: 1 problem in 1 formula detected

So I think I'll have to wait until it become "latest" version.

dzhlobo

comment created time in a month

push eventdzhlobo/homebrew-core

Dmitry Zhlobo

commit sha be2dbc46e05a4ad206ada70c0fe1be3d5ff8b7e8

uuu 1.4.139 (new formula)

view details

push time in a month

issue openedNXPmicro/mfgtools

New release due to a fix for M1 macs

I'm creating a formula for uuu in homebrew but I got an issue building the latest released version on mac with M1 chip: https://github.com/Homebrew/homebrew-core/pull/83254.

It is already fixed in master on June 29: https://github.com/NXPmicro/mfgtools/issues/274.

Can you please release a new version?

created time in a month

issue commentNXPmicro/mfgtools

Failure claim interface with MacOS Big Sur

It seems it was mitigated in upstream libusb: https://github.com/libusb/libusb/pull/911.

I've installed the latest unreleased version of libusb and uuu works well for me: brew install --head libusb.

almatthew

comment created time in a month

pull request commentHomebrew/homebrew-core

uuu 1.4.139 (new formula)

@SMillerDev, @carlocab, can you please advice on what I should do next? It doesn't build on mac arm64 w/o a patch due to a compilation error and patches are not allowed for new formulas so it doesn't build anyway due to audit.

The patch itself is in upstream already.

dzhlobo

comment created time in a month

pull request commentHomebrew/homebrew-core

uuu 1.4.139 (new formula)

I realized that a better idea would be to check for architecture in the .install block.

It seems it is not recommended to use ifs in .install:

Avoid the use of flip-flop operators.
dzhlobo

comment created time in a month

push eventdzhlobo/homebrew-core

Dmitry Zhlobo

commit sha 145c45de82301d5e9052ea722088e6dd396c6f3c

uuu 1.4.139 (new formula)

view details

push time in a month

pull request commentHomebrew/homebrew-core

uuu 1.4.139 (new formula)

Should I leave this patch or not?

I realized that a better idea would be to check for architecture in the .install block.

dzhlobo

comment created time in a month

pull request commentHomebrew/homebrew-core

uuu 1.4.139 (new formula)

Build fails for arm64. There is unmerged patch in upstream so I can apply it in this formula:

  stable do
    url "https://github.com/NXPmicro/mfgtools/releases/download/uuu_1.4.139/uuu_source-1.4.139.tar.gz"
    sha256 "25a24575f9e4781b78f8f0930f751ed371dc1a00fc22d543e9cbe4a9a70a615c"

    # Fixes building formula for M1 macs. Remove for version above 1.4.139
    # https://github.com/NXPmicro/mfgtools/issues/274
    patch do
      url "https://github.com/NXPmicro/mfgtools/commit/3c02ae8b2f2b64823b19c425816252fa36229974.patch?full_index=1"
      sha256 "497787465c5545934b510f84782b4f30c2bb7cbb37e8a84e88502aac3ba87ed2"
    end
  end

But in that case I get an error from brew audit --new uuu:

uuu:
  * Formulae should not require patches to build. Patches should be submitted and accepted upstream first.
Error: 1 problem in 1 formula detected

Should I leave this patch or not?

dzhlobo

comment created time in a month

Pull request review commentHomebrew/homebrew-core

uuu 1.4.139 (new formula)

+class Uuu < Formula+  desc "Universal Update Utility, mfgtools 3.0. NXP I.MX Chip image deploy tools"+  homepage "https://github.com/NXPmicro/mfgtools"+  url "https://github.com/NXPmicro/mfgtools/releases/download/uuu_1.4.139/uuu_source-1.4.139.tar.gz"+  sha256 "25a24575f9e4781b78f8f0930f751ed371dc1a00fc22d543e9cbe4a9a70a615c"+  license "BSD-3-Clause"++  head "https://github.com/NXPmicro/mfgtools.git", branch: "master"++  depends_on "cmake" => :build+  depends_on "pkg-config" => :build++  # Change to stable when libusb 1.0.25 is released+  # https://github.com/libusb/libusb/pull/911+  depends_on "libusb" => :head

@SMillerDev, it is runtime dependency, uuu tool won't work without it.

dzhlobo

comment created time in a month

PullRequestReviewEvent

Pull request review commentHomebrew/homebrew-core

uuu 1.4.139 (new formula)

+class Uuu < Formula+  desc "Universal Update Utility, mfgtools 3.0. NXP I.MX Chip image deploy tools"+  homepage "https://github.com/NXPmicro/mfgtools"+  url "https://github.com/NXPmicro/mfgtools/releases/download/uuu_1.4.139/uuu_source-1.4.139.tar.gz"+  sha256 "25a24575f9e4781b78f8f0930f751ed371dc1a00fc22d543e9cbe4a9a70a615c"+  license "BSD-3-Clause"++  head "https://github.com/NXPmicro/mfgtools.git", branch: "master"++  depends_on "cmake" => :build+  depends_on "pkg-config" => :build++  # Change to stable when libusb 1.0.25 is released+  # https://github.com/libusb/libusb/pull/911+  depends_on "libusb" => :head

@SMillerDev, is is okay if I check for version of libusb in the .install block and output a warning to user? Are there any ways to output warnings nicely?

dzhlobo

comment created time in a month

PullRequestReviewEvent

PR opened Homebrew/homebrew-core

uuu 1.4.139 (new formula)
  • [x] Have you followed the guidelines for contributing?
  • [x] Have you ensured that your commits follow the commit style guide?
  • [x] Have you checked that there aren't other open pull requests for the same formula update/change?
  • [x] Have you built your formula locally with brew install --build-from-source <formula>, where <formula> is the name of the formula you're submitting?
  • [x] Is your test running fine brew test <formula>, where <formula> is the name of the formula you're submitting?
  • [x] Does your build pass brew audit --strict <formula> (after doing brew install --build-from-source <formula>)? If this is a new formula, does it pass brew audit --new <formula>?

I'm not sure about dependencies, e.g. should I somehow list dependencies installed by XCode like /usr/lib/libbz2.1.0.dylib?

otool -L $(which uuu):

/usr/local/bin/uuu:
	/usr/local/opt/openssl@1.1/lib/libssl.1.1.dylib (compatibility version 1.1.0, current version 1.1.0)
	/usr/local/opt/openssl@1.1/lib/libcrypto.1.1.dylib (compatibility version 1.1.0, current version 1.1.0)
	/usr/local/Cellar/libusb/HEAD-1a90627/lib/libusb-1.0.0.dylib (compatibility version 4.0.0, current version 4.0.0)
	/usr/local/opt/libzip/lib/libzip.5.dylib (compatibility version 5.0.0, current version 5.4.0)
	/usr/lib/libz.1.dylib (compatibility version 1.0.0, current version 1.2.11)
	/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 1292.100.5)
	/usr/lib/libbz2.1.0.dylib (compatibility version 1.0.0, current version 1.0.5)
	/usr/lib/libc++.1.dylib (compatibility version 1.0.0, current version 905.6.0)
+28 -0

0 comment

1 changed file

pr created time in a month

push eventdzhlobo/homebrew-core

Dmitry Zhlobo

commit sha 379016905764af3f62c6ce04b8a3a1731f5c9e1b

uuu 1.4.139 (new formula)

view details

push time in a month

create barnchdzhlobo/homebrew-core

branch : uuu

created branch time in a month

push eventdzhlobo/homebrew-core

Daniel Nachun

commit sha 2e16a66f94614b7729c15b1c66efea13f31d42ad

liquidctl: update 1.7.1_1 bottle.

view details

Daniel Nachun

commit sha 2d581d277e4051c33ff6edb360ae933b7d514304

i2c-tools: add 4.3 bottle.

view details

Michael Cho

commit sha e17f17779568aebaa5149ce33424c9d33ce2387d

openvdb: fix build for Linux (#82765)

view details

Michael Cho

commit sha a1608291ef94a1c8752e4d99bc90bd0d9be958ae

ykclient: fix build for Linux (#82767)

view details

Michael Cho

commit sha 043c1efc40e463a7e29223995873672cbf89ab7c

tarsnap: fix build for Linux (#82768)

view details

Michael Cho

commit sha 318bb6122a885ae66d7ca43e36f9bd1b39b75a88

duktape: update 2.6.0 bottle.

view details

Dustin Rodrigues

commit sha 439b1ed3c56723648bdc210a3b5e2122ff44325b

twarc 2.4.0 Closes #82780. Signed-off-by: Nanda H Krishna <me@nandahkrishna.com> Signed-off-by: BrewTestBot <1589480+BrewTestBot@users.noreply.github.com>

view details

BrewTestBot

commit sha 139a15925d9a8cbdcac17e242d0f31150d87b963

twarc: update 2.4.0 bottle.

view details

Dustin Rodrigues

commit sha 81f9ddcd6658f68972f37aa31251595a280b91d8

richmd 10.7.0 Closes #82779. Signed-off-by: Nanda H Krishna <me@nandahkrishna.com> Signed-off-by: BrewTestBot <1589480+BrewTestBot@users.noreply.github.com>

view details

BrewTestBot

commit sha 9796b7d34876458e3094160e452e18e4a5da81b0

richmd: update 10.7.0 bottle.

view details

Michael Cho

commit sha 05000593e10aaa5dc80a7e62253df5e563a20c80

tarsnap: update 1.0.39_1 bottle.

view details

Michael Cho

commit sha 1f15b6ea55cda367bd52f3a586fff63701bbdab1

ykclient: update 2.15_1 bottle.

view details

Michael Cho

commit sha 9e79c3383d525fc151d83cefe07ef4c09fe61c7c

i386-elf-gdb: update 10.2_1 bottle.

view details

Michael Cho

commit sha e83186a21a9966de0c3c5ee93205fdfcd1af4092

openvdb: update 8.1.0 bottle.

view details

Bojan

commit sha da905dee594be94f365038c51b6c042ef16021cf

ghz 0.98.0 Created by https://github.com/mislav/bump-homebrew-formula-action Closes #82771. Signed-off-by: rui <rui@chenrui.dev> Signed-off-by: BrewTestBot <1589480+BrewTestBot@users.noreply.github.com>

view details

BrewTestBot

commit sha 7aabf37dabd5e99cad6ec541c358d044e590130b

ghz: update 0.98.0 bottle.

view details

Rui Chen

commit sha 38575e2fa09069cc9b3a5561d2d6079bb0fa7629

exploitdb 2021-08-05 Closes #82731. Signed-off-by: BrewTestBot <1589480+BrewTestBot@users.noreply.github.com>

view details

rui

commit sha 137fb914d3a478d9c74b3e701b12b684cd8892fa

exploitdb: update 2021-08-05 bottle.

view details

miccal

commit sha 501e7ff5b1f3f6b189a26be9bd0e0276aa42f09b

nss 3.69 Closes #82754. Signed-off-by: rui <rui@chenrui.dev> Signed-off-by: BrewTestBot <1589480+BrewTestBot@users.noreply.github.com>

view details

BrewTestBot

commit sha dcbcae9f7ff2aa6aefd36b8bf9bb28028235fc14

nss: update 3.69 bottle.

view details

push time in a month

issue commentpypa/virtualenv

Python 2.7: import virtualenv error: ImportError: No module named entry_points_selectable

I have the same issue also with pip 18.1 on debian buster. Installing virtualenv 20.4.7 helps.

bialix

comment created time in a month

issue openeddocker/for-mac

Update quemu-user (can't run systemd's init in arm container)

<!--


READ ME FIRST

This repository is for reporting bugs with the Docker Desktop for Mac software, which we respond to on a best-effort basis.

Support requests in this repository (i.e., trouble installing or using the software) will be ignored, but personalized support is available to Docker Pro and Team customers at https://hub.docker.com/support/desktop/, and community support is available from the Docker community Slack (https://www.docker.com/docker-community).

Issues without sufficient detail to debug them will be closed. They generally need a clear title and description, steps to reproduce, and a diagnostics ID. See https://docs.docker.com/docker-for-windows/troubleshoot/#diagnose-and-feedback for how to generate a diagnostics ID either from inside the app or from the command line.


-->

<!-- Click these checkboxes after submitting, or place an "x" in them. -->

  • [x] I have tried with the latest version of Docker Desktop
  • [x] I have tried disabling enabled experimental features
  • [x] I have uploaded Diagnostics
  • Diagnostics ID: 0AAE061E-57C7-48AE-9A47-5325896C788F/20210730173920

It seems it is a known issue of qemu with systemd: https://bugs.launchpad.net/qemu/+bug/1886811. There is a patch that was submitted and merged to upstream qemu: https://lists.gnu.org/archive/html/qemu-devel/2020-07/msg04573.html.

Currently, Docker for Mac has qemu 5.0.1 which doesn't include the fix: qemu/linux-user/fd-trans.c#L1202. The next minor version 5.1.0 includes the fix: qemu/linux-user/fd-trans.c#L1207.

Can we please update qemu in the underlying VM with linux?

There's a similar request already submitted about a different issue with qemu 5.0.1: https://github.com/docker/for-mac/issues/5879.

Expected behavior

systemd init process is launched with the underlying services.

Actual behavior

init process crashes:

$ docker run --rm -it --tmpfs /tmp --tmpfs /run -v /sys/fs/cgroup:/sys/fs/cgroup:ro --cap-add SYS_ADMIN jrei/systemd-debian:latest@sha256:d927ef42040d28ca426115d5884c2da35fd072b479bc1f7c85a4a2729460ffd5 init
WARNING: The requested image's platform (linux/arm/v7) does not match the detected host platform (linux/amd64) and no specific platform was requested
systemd 241 running in system mode. (+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN2 +IDN -PCRE2 default-hierarchy=hybrid)
Detected virtualization docker.
Detected architecture arm.
Failed to create symlink /sys/fs/cgroup/cpuacct: File exists
Failed to create symlink /sys/fs/cgroup/cpu: File exists
Failed to create symlink /sys/fs/cgroup/net_cls: File exists
Failed to create symlink /sys/fs/cgroup/net_prio: File exists

Welcome to Debian GNU/Linux 10 (buster)!

Set hostname to <62931e56a709>.
Failed to enqueue loopback interface start request: Operation not supported
Caught <ILL>, core dump failed (child 8, code=killed, status=4/ILL).
Exiting PID 1...

Information

<!-- Please, help us understand the problem. For instance:

  • Is it reproducible?
  • Is the problem new?
  • Did the problem appear with an update?
  • A reproducible case if this is a bug, Dockerfiles FTW. -->
  • macOS Version: 11.4
  • Intel chip or Apple chip: Intel
  • Docker Desktop Version: 3.5.2 (66501)

Steps to reproduce the behavior

<!-- A reproducible case, Dockerfiles FTW. -->

Run:

docker run --rm -it --tmpfs /tmp --tmpfs /run -v /sys/fs/cgroup:/sys/fs/cgroup:ro --cap-add SYS_ADMIN jrei/systemd-debian:latest@sha256:d927ef42040d28ca426115d5884c2da35fd072b479bc1f7c85a4a2729460ffd5 init

created time in 2 months

startedamirgamil/apollo

started time in 2 months

created tagdatarockets/infrastructure

tagv0.2.2

Infrastructure as Code

created time in 2 months

release datarockets/infrastructure

v0.2.2

released time in 2 months

delete branch datarockets/infrastructure

delete branch : upgrade-dependencies

delete time in 2 months

push eventdatarockets/infrastructure

Dmitry Zhlobo

commit sha c73e3b1cb69ea95459a89e6ff404bed15c5c354f

Upgrade hashicorp/kubernetes to 2.3.2 2.2.0: https://github.com/hashicorp/terraform-provider-kubernetes/releases/tag/v2.2.0 2.3.0: https://github.com/hashicorp/terraform-provider-kubernetes/releases/tag/v2.3.0 2.3.1: https://github.com/hashicorp/terraform-provider-kubernetes/releases/tag/v2.3.1 2.3.2: https://github.com/hashicorp/terraform-provider-kubernetes/releases/tag/v2.3.2

view details

Dmitry Zhlobo

commit sha 3ce7f3c787e19a0b619dd5a405d22c7418c38b92

Upgrade hashicorp/helm to 2.2.0 2.2.0: https://github.com/hashicorp/terraform-provider-helm/releases/tag/v2.2.0

view details

Dmitry Zhlobo

commit sha 0ab274c8b1044e8928f18c47abcbde634929db6b

Upgrade digitalocean/digitalocean to 2.10.1 digitalocean_kubernetes_cluster supports maintenance policy now. 2.9.0: https://github.com/digitalocean/terraform-provider-digitalocean/releases/tag/v2.9.0 2.10.0: https://github.com/digitalocean/terraform-provider-digitalocean/releases/tag/v2.10.0 2.10.1: https://github.com/digitalocean/terraform-provider-digitalocean/releases/tag/v2.10.1

view details

Dmitry Zhlobo

commit sha 1c491e5518e3aa5c3f2fadbdf6944da985e95157

Upgrade cert-manager to 1.4.1 1.4.0: https://github.com/jetstack/cert-manager/releases/tag/v1.4.0 1.4.1: https://github.com/jetstack/cert-manager/releases/tag/v1.4.1

view details

Dmitry Zhlobo

commit sha 826a68e6119bd94ffca398750f97fadb6e9f578b

Upgrade nginx-ingress helm chart

view details

Dmitry Zhlobo

commit sha 77ab6bc3b5d9bd262805a60313875b8a1eb9b876

Upgrade terraform-aws-modules/rds/aws module to 3.3.0 3.1.0: https://github.com/terraform-aws-modules/terraform-aws-rds/releases/tag/v3.1.0 3.2.0: https://github.com/terraform-aws-modules/terraform-aws-rds/releases/tag/v3.2.0 3.3.0: https://github.com/terraform-aws-modules/terraform-aws-rds/releases/tag/v3.3.0

view details

push time in 2 months

push eventdatarockets/infrastructure

Dmitry Zhlobo

commit sha 77ab6bc3b5d9bd262805a60313875b8a1eb9b876

Upgrade terraform-aws-modules/rds/aws module to 3.3.0 3.1.0: https://github.com/terraform-aws-modules/terraform-aws-rds/releases/tag/v3.1.0 3.2.0: https://github.com/terraform-aws-modules/terraform-aws-rds/releases/tag/v3.2.0 3.3.0: https://github.com/terraform-aws-modules/terraform-aws-rds/releases/tag/v3.3.0

view details

push time in 2 months