text:
$(RELEASE_PATH) need some modify: distillery 1.0.0

Hi, I run the default mix edib with distillery 1.0.0 , and get the following error:
| make -f edib/make-tarball.mk
| make[2]: Entering directory '/build'
| Packaging your app ...
| mkdir -p /stage/rootfs
| cp -vfa --parents /bin/busybox /stage/rootfs/
| '/bin/busybox' -> '/stage/rootfs/bin/busybox'
| /bin/busybox --install -s /stage/rootfs/bin
| mkdir -p /stage/rootfs/app
| tar -xzf /build/app/rel/chatty/releases/0.0.1/chatty.tar.gz -C /stage/rootfs/app
| tar: can't open '/build/app/rel/chatty/releases/0.0.1/chatty.tar.gz': No such file or directory
| make[2]: *** [edib/make-tarball.mk:61: /stage/rootfs/app/bin] Error 1
| make[2]: Leaving directory '/build'
| make[1]: Leaving directory '/build'
| make[1]: *** [edib/edib.mk:20: /stage/tarballs/20161218_154215/chatty-0.0.1.tar.gz] Error 2
| make: *** [edib/Makefile:6: edib] Error 2

The issue https://github.com/edib-tool/docker-edib-tool/issues/6 inspired me, so I rebuild docker-elixir-dev (to update the hex version to 0.14.1) and docker-edib-tool. And modify the edib/shared.mk:
diff --git a/edib/shared.mk b/edib/shared.mk
index 1924937..694fd58 100644
--- a/edib/shared.mk
+++ b/edib/shared.mk
@@ -10,7 +10,7 @@ APP_VER        = $(shell $(APPINFO_RUNNER) version)

 MIX_ENV       ?= prod
 RELEASE        = releases/$(APP_VER)/$(APP_NAME).tar.gz
-RELEASE_PATH   = $(APP_DIR)/rel/$(APP_NAME)
+RELEASE_PATH   = $(APP_DIR)/_build/$(MIX_ENV)/rel/$(APP_NAME)
 RELEASE_FILE   = $(RELEASE_PATH)/$(RELEASE)

 STAGE_DIR      = /stage

As a result, the build successed:
==> Packaging was successful! \o/

However, the command:
docker run --rm -e "PORT=4000" -p 4000:4000 local/chatty:0.0.1

show the following error:
standard_init_linux.go:175: exec user process caused "no such file or directory"

Any suggestion? Thanks.

I checked the generated chatty-0.0.1.tar.gz with
$ tar -ztvf server/tarballs/chatty-0.0.1.tar.gz|rg '/bin/'
3:drwxr-xr-x root/root         0 2016-12-19 08:46 ./app/bin/
4:-rwxrwxrwx root/root       750 2016-12-19 08:46 ./app/bin/chatty
5:-rw-r--r-- root/root      5901 2016-12-19 08:46 ./app/bin/nodetool
6:-rw-r--r-- root/root     19060 2016-12-19 08:46 ./app/bin/start_clean.boot
7:-rw-r--r-- root/root     10835 2016-12-19 08:46 ./app/bin/release_utils.escript
889:drwxr-xr-x root/root         0 2016-12-19 08:46 ./app/erts-8.0.1/bin/
890:-rwxr-xr-x root/root      1148 2016-12-19 08:46 ./app/erts-8.0.1/bin/start.src
891:-rwxr-xr-x root/root   2327712 2016-12-19 08:46 ./app/erts-8.0.1/bin/beam.smp
892:-rwxr-xr-x root/root     34664 2016-12-19 08:46 ./app/erts-8.0.1/bin/inet_gethost
893:-rwxr-xr-x root/root     22376 2016-12-19 08:46 ./app/erts-8.0.1/bin/dialyzer
894:-rwxr-xr-x root/root     14000 2016-12-19 08:46 ./app/erts-8.0.1/bin/erl_child_setup
895:-rwxr-xr-x root/root     14000 2016-12-19 08:46 ./app/erts-8.0.1/bin/to_erl
896:-rwxr-xr-x root/root      1148 2016-12-19 08:46 ./app/erts-8.0.1/bin/start
897:-rwxr-xr-x root/root     22376 2016-12-19 08:46 ./app/erts-8.0.1/bin/escript
898:-rwxr-xr-x root/root      1244 2016-12-19 08:46 ./app/erts-8.0.1/bin/start_erl.src
899:-rwxr-xr-x root/root     22376 2016-12-19 08:46 ./app/erts-8.0.1/bin/erlc
900:-rwxr-xr-x root/root       850 2016-12-19 08:46 ./app/erts-8.0.1/bin/erl.src
901:-rwxr-xr-x root/root      5901 2016-12-19 08:46 ./app/erts-8.0.1/bin/nodetool
902:-rwxr-xr-x root/root   2192416 2016-12-19 08:46 ./app/erts-8.0.1/bin/beam
903:-rwxr-xr-x root/root     22208 2016-12-19 08:46 ./app/erts-8.0.1/bin/run_erl
904:-rwxr-xr-x root/root     39400 2016-12-19 08:46 ./app/erts-8.0.1/bin/erlexec
905:-rwxr-xr-x root/root      9904 2016-12-19 08:46 ./app/erts-8.0.1/bin/dyn_erl
906:-rwxr-xr-x root/root       247 2016-12-19 08:46 ./app/erts-8.0.1/bin/erl
907:-rwxr-xr-x root/root     46952 2016-12-19 08:46 ./app/erts-8.0.1/bin/epmd
908:-rwxr-xr-x root/root     22376 2016-12-19 08:46 ./app/erts-8.0.1/bin/ct_run
909:-rwxr-xr-x root/root     22376 2016-12-19 08:46 ./app/erts-8.0.1/bin/typer
910:-rwxr-xr-x root/root      9912 2016-12-19 08:46 ./app/erts-8.0.1/bin/heart
1013:drwxr-xr-x root/root         0 2016-12-19 08:46 ./bin/
1014:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/uptime -> /bin/busybox
1015:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/switch_root -> /bin/busybox
1016:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/pkill -> /bin/busybox
1017:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/bbconfig -> /bin/busybox
1018:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/whoami -> /bin/busybox
1019:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/fdisk -> /bin/busybox
1020:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/run-parts -> /bin/busybox
1021:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/reformime -> /bin/busybox
1022:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/renice -> /bin/busybox
1023:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/httpd -> /bin/busybox
1024:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/traceroute6 -> /bin/busybox
1025:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/killall5 -> /bin/busybox
1026:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/rfkill -> /bin/busybox
1027:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/iptunnel -> /bin/busybox
1028:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/adduser -> /bin/busybox
1029:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/dd -> /bin/busybox
1030:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/pscan -> /bin/busybox
1031:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/tail -> /bin/busybox
1032:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/conspy -> /bin/busybox
1033:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/cat -> /bin/busybox
1034:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/mktemp -> /bin/busybox
1035:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/dnsd -> /bin/busybox
1036:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/gzip -> /bin/busybox
1037:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/mount -> /bin/busybox
1038:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/mkdir -> /bin/busybox
1039:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/tunctl -> /bin/busybox
1040:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/inetd -> /bin/busybox
1041:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/cut -> /bin/busybox
1042:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/mkfifo -> /bin/busybox
1043:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/sleep -> /bin/busybox
1044:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/nandwrite -> /bin/busybox
1045:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/lspci -> /bin/busybox
1046:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/sha1sum -> /bin/busybox
1047:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/lsusb -> /bin/busybox
1048:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/sh -> /bin/busybox
1049:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/zcat -> /bin/busybox
1050:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/true -> /bin/busybox
1051:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/sendmail -> /bin/busybox
1052:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/lzop -> /bin/busybox
1053:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/echo -> /bin/busybox
1054:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/strings -> /bin/busybox
1055:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/vlock -> /bin/busybox
1056:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/ls -> /bin/busybox
1057:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/killall -> /bin/busybox
1058:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/seq -> /bin/busybox
1059:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/less -> /bin/busybox
1060:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/patch -> /bin/busybox
1061:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/pgrep -> /bin/busybox
1062:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/chroot -> /bin/busybox
1063:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/diff -> /bin/busybox
1064:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/ed -> /bin/busybox
1065:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/mkswap -> /bin/busybox
1066:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/logger -> /bin/busybox
1067:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/unlzma -> /bin/busybox
1068:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/swapon -> /bin/busybox
1069:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/sysctl -> /bin/busybox
1070:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/mknod -> /bin/busybox
1071:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/setlogcons -> /bin/busybox
1072:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/mdev -> /bin/busybox
1073:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/remove-shell -> /bin/busybox
1074:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/tar -> /bin/busybox
1075:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/ifconfig -> /bin/busybox
1076:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/mesg -> /bin/busybox
1077:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/route -> /bin/busybox
1078:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/ps -> /bin/busybox
1079:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/iplink -> /bin/busybox
1080:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/hostid -> /bin/busybox
1081:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/vi -> /bin/busybox
1082:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/false -> /bin/busybox
1083:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/[[ -> /bin/busybox
1084:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/fsck -> /bin/busybox
1085:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/delgroup -> /bin/busybox
1086:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/watch -> /bin/busybox
1087:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/brctl -> /bin/busybox
1088:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/arping -> /bin/busybox
1089:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/ipaddr -> /bin/busybox
1090:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/printenv -> /bin/busybox
1091:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/sed -> /bin/busybox
1092:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/realpath -> /bin/busybox
1093:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/tr -> /bin/busybox
1094:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/iprule -> /bin/busybox
1095:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/kill -> /bin/busybox
1096:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/eject -> /bin/busybox
1097:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/[ -> /bin/busybox
1098:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/id -> /bin/busybox
1099:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/dumpleases -> /bin/busybox
1100:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/nsenter -> /bin/busybox
1101:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/getopt -> /bin/busybox
1102:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/ttysize -> /bin/busybox
1103:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/add-shell -> /bin/busybox
1104:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/readahead -> /bin/busybox
1105:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/telnet -> /bin/busybox
1106:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/fbset -> /bin/busybox
1107:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/date -> /bin/busybox
1108:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/md5sum -> /bin/busybox
1109:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/yes -> /bin/busybox
1110:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/udhcpc6 -> /bin/busybox
1111:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/fsync -> /bin/busybox
1112:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/hd -> /bin/busybox
1113:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/rmdir -> /bin/busybox
1114:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/more -> /bin/busybox
1115:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/unexpand -> /bin/busybox
1116:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/readlink -> /bin/busybox
1117:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/uuencode -> /bin/busybox
1118:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/setfont -> /bin/busybox
1119:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/whois -> /bin/busybox
1120:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/nanddump -> /bin/busybox
1121:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/ifdown -> /bin/busybox
1122:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/ipcrm -> /bin/busybox
1123:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/ipcs -> /bin/busybox
1124:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/sort -> /bin/busybox
1125:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/ftpget -> /bin/busybox
1126:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/blkid -> /bin/busybox
1127:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/rdate -> /bin/busybox
1128:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/test -> /bin/busybox
1129:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/sha512sum -> /bin/busybox
1130:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/passwd -> /bin/busybox
1131:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/sha3sum -> /bin/busybox
1132:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/getty -> /bin/busybox
1133:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/chgrp -> /bin/busybox
1134:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/modprobe -> /bin/busybox
1135:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/wget -> /bin/busybox
1136:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/dc -> /bin/busybox
1137:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/ping6 -> /bin/busybox
1138:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/catv -> /bin/busybox
1139:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/deluser -> /bin/busybox
1140:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/init -> /bin/busybox
1141:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/fold -> /bin/busybox
1142:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/pipe_progress -> /bin/busybox
1143:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/fgrep -> /bin/busybox
1144:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/depmod -> /bin/busybox
1145:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/bunzip2 -> /bin/busybox
1146:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/adjtimex -> /bin/busybox
1147:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/uudecode -> /bin/busybox
1148:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/touch -> /bin/busybox
1149:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/watchdog -> /bin/busybox
1150:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/iproute -> /bin/busybox
1151:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/which -> /bin/busybox
1152:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/expand -> /bin/busybox
1153:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/find -> /bin/busybox
1154:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/fdformat -> /bin/busybox
1155:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/mv -> /bin/busybox
1156:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/printf -> /bin/busybox
1157:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/tftp -> /bin/busybox
1158:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/truncate -> /bin/busybox
1159:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/split -> /bin/busybox
1160:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/basename -> /bin/busybox
1161:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/cp -> /bin/busybox
1162:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/chown -> /bin/busybox
1163:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/dos2unix -> /bin/busybox
1164:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/poweroff -> /bin/busybox
1165:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/unlzop -> /bin/busybox
1166:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/acpid -> /bin/busybox
1167:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/arp -> /bin/busybox
1168:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/chvt -> /bin/busybox
1169:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/fbsplash -> /bin/busybox
1170:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/lzcat -> /bin/busybox
1171:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/lzma -> /bin/busybox
1172:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/ftpd -> /bin/busybox
1173:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/lzopcat -> /bin/busybox
1174:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/xzcat -> /bin/busybox
1175:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/powertop -> /bin/busybox
1176:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/addgroup -> /bin/busybox
1177:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/flock -> /bin/busybox
1178:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/time -> /bin/busybox
1179:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/pmap -> /bin/busybox
1180:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/chpasswd -> /bin/busybox
1181:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/smemcap -> /bin/busybox
1182:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/env -> /bin/busybox
1183:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/mountpoint -> /bin/busybox
1184:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/setconsole -> /bin/busybox
1185:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/timeout -> /bin/busybox
1186:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/slattach -> /bin/busybox
1187:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/rmmod -> /bin/busybox
1188:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/showkey -> /bin/busybox
1189:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/nc -> /bin/busybox
1190:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/insmod -> /bin/busybox
1191:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/syslogd -> /bin/busybox
1192:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/netstat -> /bin/busybox
1193:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/ntpd -> /bin/busybox
1194:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/rev -> /bin/busybox
1195:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/nbd-client -> /bin/busybox
1196:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/dumpkmap -> /bin/busybox
1197:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/sha256sum -> /bin/busybox
1198:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/usleep -> /bin/busybox
1199:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/lsmod -> /bin/busybox
1200:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/udhcpc -> /bin/busybox
1201:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/hostname -> /bin/busybox
1202:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/nameif -> /bin/busybox
1203:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/klogd -> /bin/busybox
1204:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/fatattr -> /bin/busybox
1205:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/uniq -> /bin/busybox
1206:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/uname -> /bin/busybox
1207:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/free -> /bin/busybox
1208:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/mkdosfs -> /bin/busybox
1209:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/ether-wake -> /bin/busybox
1210:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/rdev -> /bin/busybox
1211:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/od -> /bin/busybox
1212:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/ping -> /bin/busybox
1213:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/awk -> /bin/busybox
1214:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/swapoff -> /bin/busybox
1215:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/nologin -> /bin/busybox
1216:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/unix2dos -> /bin/busybox
1217:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/dmesg -> /bin/busybox
1218:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/ln -> /bin/busybox
1219:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/fakeidentd -> /bin/busybox
1220:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/sum -> /bin/busybox
1221:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/bzip2 -> /bin/busybox
1222:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/tee -> /bin/busybox
1223:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/umount -> /bin/busybox
1224:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/head -> /bin/busybox
1225:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/fuser -> /bin/busybox
1226:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/groups -> /bin/busybox
1227:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/fdflush -> /bin/busybox
1228:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/unxz -> /bin/busybox
1229:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/nmeter -> /bin/busybox
1230:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/rm -> /bin/busybox
1231:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/pwdx -> /bin/busybox
1232:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/tac -> /bin/busybox
1233:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/ionice -> /bin/busybox
1234:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/base64 -> /bin/busybox
1235:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/raidautorun -> /bin/busybox
1236:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/reboot -> /bin/busybox
1237:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/halt -> /bin/busybox
1238:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/dirname -> /bin/busybox
1239:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/beep -> /bin/busybox
1240:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/unshare -> /bin/busybox
1241:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/su -> /bin/busybox
1242:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/stty -> /bin/busybox
1243:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/ifup -> /bin/busybox
1244:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/makemime -> /bin/busybox
1245:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/hwclock -> /bin/busybox
1246:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/sync -> /bin/busybox
1247:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/findfs -> /bin/busybox
1248:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/kbd_mode -> /bin/busybox
1249:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/wc -> /bin/busybox
1250:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/chmod -> /bin/busybox
1251:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/cal -> /bin/busybox
1252:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/openvt -> /bin/busybox
1253:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/volname -> /bin/busybox
1254:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/pidof -> /bin/busybox
1255:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/ash -> /bin/busybox
1256:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/blkdiscard -> /bin/busybox
1257:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/bzcat -> /bin/busybox
1258:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/mpstat -> /bin/busybox
1259:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/pwd -> /bin/busybox
1260:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/du -> /bin/busybox
1261:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/setkeycodes -> /bin/busybox
1262:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/traceroute -> /bin/busybox
1263:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/udhcpd -> /bin/busybox
1264:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/unzip -> /bin/busybox
1265:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/xargs -> /bin/busybox
1266:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/top -> /bin/busybox
1267:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/tty -> /bin/busybox
1268:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/reset -> /bin/busybox
1269:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/ifenslave -> /bin/busybox
1270:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/cpio -> /bin/busybox
1271:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/unlink -> /bin/busybox
1272:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/blockdev -> /bin/busybox
1273:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/mkpasswd -> /bin/busybox
1274:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/dnsdomainname -> /bin/busybox
1275:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/grep -> /bin/busybox
1276:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/setsid -> /bin/busybox
1277:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/egrep -> /bin/busybox
1278:-rwxr-xr-x root/root    821408 2016-09-26 21:45 ./bin/busybox
1279:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/gunzip -> /bin/busybox
1280:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/vconfig -> /bin/busybox
1281:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/nslookup -> /bin/busybox
1282:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/mkfs.vfat -> /bin/busybox
1283:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/shuf -> /bin/busybox
1284:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/ipcalc -> /bin/busybox
1285:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/modinfo -> /bin/busybox
1286:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/hdparm -> /bin/busybox
1287:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/cmp -> /bin/busybox
1288:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/crond -> /bin/busybox
1289:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/cryptpw -> /bin/busybox
1290:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/iostat -> /bin/busybox
1291:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/microcom -> /bin/busybox
1292:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/login -> /bin/busybox
1293:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/pstree -> /bin/busybox
1294:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/clear -> /bin/busybox
1295:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/nice -> /bin/busybox
1296:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/stat -> /bin/busybox
1297:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/logread -> /bin/busybox
1298:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/resize -> /bin/busybox
1299:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/expr -> /bin/busybox
1300:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/loadkmap -> /bin/busybox
1301:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/setserial -> /bin/busybox
1302:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/inotifyd -> /bin/busybox
1303:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/comm -> /bin/busybox
1304:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/readprofile -> /bin/busybox
1305:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/deallocvt -> /bin/busybox
1306:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/losetup -> /bin/busybox
1307:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/loadfont -> /bin/busybox
1308:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/hexdump -> /bin/busybox
1309:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/nohup -> /bin/busybox
1310:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/df -> /bin/busybox
1311:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/install -> /bin/busybox
1312:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/crontab -> /bin/busybox
1313:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/lsof -> /bin/busybox
1314:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/ip -> /bin/busybox
1315:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/cksum -> /bin/busybox
1316:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/ftpput -> /bin/busybox
1317:lrwxrwxrwx root/root         0 2016-12-19 08:46 ./bin/fstrim -> /bin/busybox

However, both /bin/busybox and /app/bin/chatty give the same error:
$ docker run -it --rm --entrypoint=/bin/busybox local/chatty:0.0.1 -i
standard_init_linux.go:175: exec user process caused "no such file or directory"

$ docker run -it --rm --entrypoint=/app/bin/chatty local/chatty:0.0.1 -i
standard_init_linux.go:175: exec user process caused "no such file or directory"

Hi, I use docker save to make the generated image into a tarball.
$ docker save local/chatty:0.0.1 -o tar/chatty.tar

then tar xf and tar xf to list the files
$ ls
3024bf322efbf8c364111da8e513fb5071470665b16c0fa572edbe81f42624fe.json  chatty.tar     repositories
b9372c49ca0e817c66c195f5fb92047e83a67ab14ef5345e1f2a70ef7b0a5cea       manifest.json
$ cd b9372c49ca0e817c66c195f5fb92047e83a67ab14ef5345e1f2a70ef7b0a5cea
$ ls
app  bin  json  layer.tar  VERSION

$ app/bin/chatty
Usage: chatty {start|start_boot <file>|foreground|stop|restart|reboot|pid|ping|console|console_clean|console_boot <file>|attach|remote_console|upgrade|downgrade|install|escript|rpc|rpcterms|eval|command <module> <function> <args>}
$ app/bin/chatty console
/home/hoffmann/Project/elixir-is-fun/tar/b9372c49ca0e817c66c195f5fb92047e83a67ab14ef5345e1f2a70ef7b0a5cea/app/releases/0.0.1/chatty.sh: line 614: /home/hoffmann/Project/elixir-is-fun/tar/b9372c49ca0e817c66c195f5fb92047e83a67ab14ef5345e1f2a70ef7b0a5cea/app/erts-8.0.1/bin/erlexec: No such file or directory
$ app/erts-8.0.1/bin/erlexec
zsh: no such file or directory: app/erts-8.0.1/bin/erlexec
$ file app/erts-8.0.1/bin/erlexec
app/erts-8.0.1/bin/erlexec: ELF 64-bit LSB shared object, x86-64, version 1 (SYSV), dynamically linked, interpreter /lib/ld-musl-x86_64.so.1, stripped

Any idea?

Btw, /bin/busybox works in the docker image alpine:3.4.
$ docker run -it --rm --entrypoint=/bin/busybox alpine:3.4
BusyBox v1.24.2 (2016-08-12 14:38:34 GMT) multi-call binary.
BusyBox is copyrighted by many authors between 1998-2015.
Licensed under GPLv2. See source distribution for detailed
copyright notices.

...

full output: https://gist.github.com/luckynum7/fe5f3536c0fe0fdf708031ee5539fb78#file-busybox-alpine-3-4-md

Update, older title for the issue:
$(RELEASE_PATH) may need some modify: "tar: ... No such file or directory"
According to the changelog for distillery: https://github.com/bitwalker/distillery/blob/master/CHANGELOG.md#100
Default output path for release artifacts is _build/<env>/rel/<relname>, this can be configured in rel/config.exs with set output_dir: "path"

@luckynum7 I'm getting this same error, and a different error with 0.10 distillery. I was just about to go down the same path you were, so I'm glad I saw this, and I'm looking forward to yer commit!

@luckynum7 I'm getting this same error, and a different error with 0.10 distillery. I was just about to go down the same path you were, so I'm glad I saw this, and I'm looking forward to yer commit!

@luckynum7 Thank you for the wonderful detailed issue. Using the contents of your changes. I was successful at building a docker image using distillery 1.1.0
I'll push up the commits and create some PRs

We'll need more testing on this to make sure this doesn't break others.
I had an issue with a git dependency in my project but was able to switch to a hex package as a workaround. Should be investigated further.

Cancel that. Ended up running an old docker image on accident. Troubleshooting

Here's what I've found out so far
The generated docker image is unable to be started using the following command
docker run -it generated-docker-image/name /bin/sh
Searching for answers has revealed that the error message
panic: standard_init_linux.go:178: exec user process caused "no such file or directory" [recovered]
	panic: standard_init_linux.go:178: exec user process caused "no such file or directory"

@JeremyBellows, I fired a PR couple of days ago, https://github.com/edib-tool/docker-edib-tool/pull/9 and forgot to update here. To build the correct image, there's another change need to be made
diff --git a/tools/libdeps.exs b/tools/libdeps.exs
index 2399b70..4b93518 100755
--- a/tools/libdeps.exs
+++ b/tools/libdeps.exs
@@ -1,6 +1,6 @@
 *!/usr/bin/env elixir
 defmodule Libdeps do
-  @relpath "app/rel"
+  @relpath "app/_build"
   @lddpath_regex ~r/\/(lib|usr\/lib)[^ ]+/

   def all_files do

However,  this made the relpath different from the original one. The reason is that I don't know how to pass the MIX.ENV down to it. The related files: tools/libdeps, edib/make-tarball.mk.

Just change it to:
 #!/usr/bin/env elixir
 defmodule Libdeps do
-  @relpath "app/rel"
+  @current_mix_env System.get_env("MIX_ENV") || "prod"
+  @relpath "app/_build/#{@current_mix_env}"

@luckynum7 Excellent! I should've checked the existing PRs. My bad!
Would you mind sharing your process for solving this issue?
@asaaki I closed one of the PRs I opened in favor of @luckynum7 PR. Let me know if there is anything else I can do :)
Great job guys!

@luckynum7 @ryancammer @JeremyBellows Could you check again? The image chain was rebuilt recently multiple times, lots of dependencies should have been updated as well. Might be that the described issues have dissolved now.

@asaaki I tried tried the latest commit of edib-tool/mix-edib, some error:
``bash
| make -f edib/make-tarball.mk
| make[2]: Entering directory '/build'
| Packaging your app ...
| mkdir -p /stage/rootfs
| cp -vfa --parents /bin/busybox /stage/rootfs/
| '/bin/busybox' -> '/stage/rootfs/bin/busybox'
| /bin/busybox --install -s /stage/rootfs/bin
| mkdir -p /stage/rootfs/app
| tar -xzf /build/app/rel/chatty/releases/0.0.1/chatty.tar.gz -C /stage/rootfs/app
| tar: can't open '/build/app/rel/chatty/releases/0.0.1/chatty.tar.gz': No such file or directory
| make[2]: Leaving directory '/build'
| make[2]: *** [edib/make-tarball.mk:61: /stage/rootfs/app/bin] Error 1
| make[1]: *** [edib/edib.mk:20: /stage/tarballs/20170122_005702/chatty-0.0.1.tar.gz] Error 2
| make[1]: Leaving directory '/build'
| make: *** [edib/Makefile:6: edib] Error 2
==> An error happened!
==> Reason: Artifact tarball not created! Check for any errors above.

full output: https://gist.github.com/luckynum7/fe5f3536c0fe0fdf708031ee5539fb78#file-edib-tool-1-5-2-md

@asaaki I update the relpath to respect the MIX_ENV based on your comment, thanks.
Updated PR: https://github.com/edib-tool/docker-edib-tool/pull/9

I have released mix-edib v0.10.0 which uses edib-tool image v1.6.0.
Btw: You can also specify the docker image via mix edib --edib edib/edib-tool:1.6.0 now. Useful if you want to test different image versions. (Maybe the option should be renamed to --tool in the future.) 😅

authors: JeremyBellows asaaki luckynum7 ryancammer

repo: edib-tool/mix-edib


text:
Bring ClusterService interface up-to-date

There are a few new methods available in Databricks' Cluster API.
Goal:
Add support for the following methods to the ClusterService

pin
unpin
list node types
list zones
spark versions
permanent delete

@samshuster @javamonkey79  - I need some of this methods - should I open an PR?

yes please @cornelcreanga

should add, you can obviously create a pr for only those that you immediately need, no need to do all of the above.

https://github.com/edmunds/databricks-rest-client/pull/75

source: gharchive/issue

authors: cornelcreanga reillydj samshuster

repo: edmunds/databricks-rest-client

license_type: permissive

license_source: github-api


text:
add cvefeed.io

maybe add feed.io? it's more of a redirection website to several git repos and found references on cves, but it digs some quite obscure links to some cves, so it could be useful

Added under Vulnerabilities category https://github.com/edoardottt/awesome-hacker-search-engines?tab=readme-ov-file#vulnerabilities
Thanks @micaelmaciel for your contribution!

authors: edoardottt micaelmaciel

license: MIT


text:
🛑 Xcodehoster server 4 is down

In a9473d0, Xcodehoster server 4 (https://serverjogja.securityhub.id/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Xcodehoster server 4 is back up in f4d2900.

repo: edoaurahman/check-web-uptime


text:
Exception with IsUsingLatestVersion

If this issue is for a new feature, please skip the "Bug" section and fill out the "Feature Request" section at the bottom.
Bug
Plugin Version:  2.1.0
Platform (e.g., Android v21):  Multiple Android phone brands in multiple os version (10,11,12...)
Expected behavior
IsUsingLatestVersion working fine
Actual behavior
getting lot of error logged with such stacktrace:
Error comparing current app version number with latest. Version name=22.2.2.88285 and lastest version= .
at Plugin.LatestVersion.LatestVersionImplementation.IsUsingLatestVersion () [0x000e8] in :0
Steps to reproduce the issue
Happens since last update of the app version which happened today.
Error happens when having the previous app version installed (22.2.1) and updating to new one (22.2.2).
Hard to reproduce as need to have previous version from the store installed before doing the update.
Is there some cache that's not wiped out at update or what else could trigger this exception?
https://play.google.com/store/apps/details?id={_packageName}&hl=en returns the latest version number (with my package name)

I am also getting the same issue in Android app. My app checks if user is using the latest version or not. If not a latest version it won't allow login and user need to install the latest version first in order to login into the app.

This is a blocker for my app right now. @edsnider : Would you please quickly look into this issue?
Thank you.

I have same issue here. I use the version checker to deside between connecting to prod or dev/test. Due to this error our users are current unable to login at all :(
The problems started appearing sporatically over the last week or so, but this morning it is consistently appearing.
Hope you can deploy a quick fix without upgrading the Nuget!

we've got the same thing

I have the same issue. After looking at the repo code there was a regex code that finding some certain div for the version from the play store. But after google play store update the web site it seems that the div for version number has been remove so that's why the latest version is always empty string.
I suggest you guys create the versioning on your own server that's best we can do right now.

I am also getting the same issue in Android app. My app checks if user is using the latest version or not. If not a latest version it won't allow login and user need to install the latest version first in order to login into the app.

This is a blocker for my app right now. @edsnider : Would you please quickly look into this issue?
EDIT: FYI - Google has completely changed the Play Store UI. This may be the reason this Brocken?
Thank you.

Indeed the play store UI update is the culprit they removed the div that this plug in has on its regex expression.

Indeed the data we get as response for https://play.google.com/store/apps/details?id=(package name)&hl=en is completely different from before.
The version number is still returned, but it's lost in the middle of other data and have no title as was before "current version".
Not sure i know how to dig in the response to retrieve this version number.

I was able to make it work for me by changing the regex expression in https://github.com/edsnider/latestversionplugin/blob/2a3aa6bb55b3dfc3b6085043218bfb8c90ab1a0c/src/LatestVersion.android.cs#L72 to this ",\\[\\[\\[\"(\\d\\.\\d\\.\\d\\.\\d)\"\\]\\]".

@edsnider are support and maintenance ended on this plugin?

@issamben7 did you tested your regex in production environment already so i can use it over a fork on my next release?

let me know when this one is resolved

@gsgou I implemented it on my app and tested it, but I never deployed it into production since we decided to store the version on a dedicated server to avoid problems in the future.

The new beta version seems to have solve the issue on Android. Thanks to those who worked on it

is the nuget package updated yet?

When will the nuget package get this update?

when will the nuget package be updated?

You can have the nuget with these modifications in the beta version here : https://www.nuget.org/packages/Xam.Plugin.LatestVersion/2.1.1-beta.107
With VS NPM, just check "Include Prerelease" and update to 2.1.1-beta.107

I still have the problem with version 2.1.1-beta.107, though the error says  lastest version=' istead of  lastest version= .

Confirmed, I see the same problem Error comparing current app version number with latest. Version name=5.0.0 and lastest version= using the beta, and it's not fixed in the normal (non-beta) release either.

@vchelaru  there is a PR but is not getting merged 3w now. You can follow up the convdrsation and maybe leave a comment:
https://github.com/edsnider/latestversionplugin/pull/49

authors: AshaMandaliyaGohil Hjord Jerome-Liger NelBarnatia Pro-4-Soft grounch gsgou issamben7 larsfsonderskov vchelaru wesjonesCMX wtheronjones

repo: edsnider/latestversionplugin


text:
EDU-610 Add simple basic auth layer with configurable credentials

Closes https://educandu.atlassian.net/browse/EDU-610

Nice and simple!

Nice and simple!

Danke! 🙇

source: gharchive/pull-request

authors: adrianaluchian ahelmberger

repo: educandu/educandu


text:
File share not working

Hi, what is this fixed address ? Is there a config I should set for file share function to work ?
wss://tracker.lab.vvc.niif.hu:443
Thanks!

This is a torrent tracker hosted by us, the developers, instead of using public trackers. You may of course set up your own. It is used for filesharing in the client.

Thanks .. in the end .. I got that .. but it seems not to work .. to download the file ..after I replaced the value with wss://tracker.openwebtorrent.com.
If you can help with some more info I'd be grateful.

Can I enable debug on production site ? I have no logs in console ..

REACT_APP_DEBUG=* npm run build

But the defining of own torrent is just in develop branch. In Master I think it is not there. At least it is not listed in config.example.js.

I could not setup the file sharing functionality .. video and audio are working fine .. for file sharing there is configuration I'm missing .. please help..

on the develop it works fine, as in server/config.js you can add you own torrent tracker. For my users I have installed my own tracker https://github.com/webtorrent/bittorrent-tracker on my server. You set up everything within 15 minutes.

This is my console output:
fs.txt

bittorrent-tracker runs on localhost .. is this corect ? I expected to bind to ip any or to specific address .. am I wrong ?

Have you configured a TURN server?

Yes

I think I get a timeout from the 'tracker' ..I'm not sure ..

That is the reason we set up a private tracker, the public ones are unreliable.

but can you help me with that ? it's not clear how to setup one ...
the one above .. runs on localhost ..... how to set an ip ? (bittorrent-tracker)

on the develop it works fine, as in server/config.js you can add you own torrent tracker. For my users I have installed my own tracker https://github.com/webtorrent/bittorrent-tracker on my server. You set up everything within 15 minutes.

Hi Astagor, where can i put torrent tracker url into config.js? Which variable?
Because i've installed a tracker, but webtorrent won't announce the files (tried udp, wss, tcp, http...)
It seems webtorrent (in multiparty) won't contact the external server. Multiparty runs a standalone tracker on localhost?
Thanks a lot

It works on the DEVELOP branch, I think in MASTER it is not yet there.
You just put
fileTracker  : 'wss://bittorrent-tracker.YOUR-DOMAIN.COM:443',
and it works. Of course I put 443 as my tracker is behind Nginx, which is a proxy to my tracker. I would recommend this, as 443 should be opened on most firewalls. My clients use my service from within hospitals, so I have everything also multiparty and torrent on 443.

Thanks a lot Astagor. It works!
i try to reproduce here:

MASTER git: modified RoomClient.js with an open wss tracker (wss is important) [1]
apache .conf : changed proxy settings and added rewrote for wss call [2]

would you like to add a comment into readme for proxy configurations?
Thanks a lot for your work!
[1]: Open wss tracker https://github.com/ngosang/trackerslist/blob/master/trackers_all_ws.txt
[2]: first answer  https://stackoverflow.com/questions/27526281/websockets-and-apache-proxy-how-to-configure-mod-proxy-wstunnel/27534443#27534443

@verbavolant useful info thanks!
can you help me use nginx instead of apache ?

@LucaGabi  try this from stackoverflow [1]
I don't run nginx so i can't try...
server {
listen 443;
server_name xx.xx.xxx.xx;
location / {
proxy_set_header   X-Forwarded-For $remote_addr;
proxy_set_header   Host $http_host;
proxy_pass         "https://127.0.0.1:443";
proxy_http_version 1.1;
proxy_set_header   Upgrade $http_upgrade;
proxy_set_header   Connection "upgrade";
}
[1]
https://stackoverflow.com/questions/41381444/websocket-connection-failed-error-during-websocket-handshake-unexpected-respon

@Astagor thanks again for your suggestion ( https://github.com/webtorrent/bittorrent-tracker )
i leave here the apache configuration (need a proxy for the secure side of ws protocol):
https://github.com/webtorrent/bittorrent-tracker/issues/339#issuecomment-603994750

@havfo last question: did you changed tracker from webtorrent tracker to opentracker?
better? how to enable wss in opentracker?
thanks again!

@verbavolant We use webtorrent tracker, AFAIK @havfo also can't tell you more, because unfortunately we don't have experience with open tracker yet, but interested in if you have any..

Is here any open question still here?
Can we conclude with the following?
When we will merge develop to master the hardcoded tracker will be faded out.
@verbavolant @LucaGabi @Astagor what are your thoughts?

@misi i've seen yesterday tracker.lab.vvc.niif.hu:443 running opentracker, now is running again webtorrent.
I've installed opentracker but i've seen the master branch can't dialog with http tracker, only wss.
I'll try with develop branch tonight.
For opentracker take a look here: https://github.com/coldwinds/opentracker-auto-installer (and my issue for debian)
@misi (again) ok for me, you can conclude this discussion.

can someone pleas explain to me how to setup the [bittorrent-tracker] it seems to start on my ip
this._tracker = 'ws://x.x.x.x:8000/announce'; but when i set the ip in roomClient.js and config.json this are the stats
0 torrents (0 active)
Connected Peers: 0
Peers Seeding Only: 0
Peers Leeching Only: 0
Peers Seeding & Leeching: 0
IPv4 Peers: 0
IPv6 Peers: 0
Clients:

authors: Astagor LucaGabi accidentul havfo misi verbavolant

repo: edumeet/edumeet


text:
"too many WebMediaPlayers" intervention is breaking WebRTC functionality

Can we figure out a workaround for this chromium bug?
https://bugs.chromium.org/p/chromium/issues/detail?id=1232649#c87

weird that no one has encountered this.It screwed up almost every conferencing solution

The new client is conservative in the number of media elements it renders on screen. Should never be more than lastN video and the number of unmuted audio elements.

authors: dinceremre havfo


text:
dotnet-format-01-Jan-2022: fix code guidelines violations

dotnet format
dotnet format detected code guidelines violations and automatically created this PR.
:warning: Please review the suggested changes before merging.
Note
Sometimes the fix provided by the analyzers produces unecessary comments when formatting files.
This should only happen if the project supports multiple target frameworks and the fix doesn't produce the same output for all. However, it seems that sometimes the Unmerged change from project ... comment shows up even though the fix produced the same output.
If this happens, just delete the comments added. Otherwise, consider incorporating the commented out code using preprocessor directives to control conditional compilation.
Example:
csharp #if NET5_0     ... #elif NETCOREAPP3_1     ... #endif

/dotnet-format

/dotnet-format

repo: edumserrano/dot-net-sdk-extensions


text:
Add pre build environment

Build OCI image when there is a change in the main.
The OCI image will be stored in GitHub Packages.
When the action is executed, the action will use the prebuild container, which makes it a lot faster.
Related issue
Closes #6
Development
If you want to test a new feature in a branch, simple point in the action.yml to the Dockerfile again and you will have a freshly build environment again for each run.
About the container
The prebuild container has some Secure Software Supply Chain meta files attached to it. The container is signed, has a SLSA provenance file so you can prove it was created in this build pipeline, and a Software Bill of Material in SPDX format, so you can evaluate the content of the container before you want to use it.

The checks will initially fail, because the first time, there is no stored package. Rerunning the checks will resolve that.

repo: edumserrano/github-issue-forms-parser


text:
Update the Shade Plugin version

Right now the Maven shade plugin version is at 3.1.0 and your library's compatibility is at 2.4.3.
Please update the library to the latest Maven shade plugin version.

I get
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-shade-plugin:3.1.0:shade (default) on project syi-platform: Unable to parse configuration of mojo org.apache.maven.plugins:maven-shade-plugin:3.1.0:shade for parameter resource: Cannot find 'resource' in class com.github.edwgiz.mavenShadePlugin.log4j2CacheTransformer.PluginsCacheFileTransformer -> [Help 1]

Using whatever version of shade. Not sure if it is related. Any ideas?

@paulosuzart what does you pom.xml look like?

@PyvesB I think I am seeing the same issue as paulosuzart.
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-shade-plugin:2.4.3:shade (default) on project promoscombos: Unable to parse configuration of mojo org.apache.maven.plugins:maven-shade-plugin:2.4.3:shade for parameter resource: Cannot find 'resource' in class com.github.edwgiz.mavenShadePlugin.log4j2CacheTransformer.PluginsCacheFileTransformer -> [Help 1]
Here is what I have in my pom.xml:
<?xml version="1.0" encoding="UTF-8"?>
<project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
	xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd">

<modelVersion>4.0.0</modelVersion>
	<dependency>
		<groupId>com.amazonaws</groupId>
		<artifactId>aws-lambda-java-log4j2</artifactId>
		<version>1.0.0</version>
	</dependency>
	<dependency>
		<groupId>org.apache.logging.log4j</groupId>
		<artifactId>log4j-api</artifactId>
		<version>2.8.1</version>
	</dependency>
	<dependency>
		<groupId>org.apache.logging.log4j</groupId>
		<artifactId>log4j-core</artifactId>
		<version>2.8.1</version>
	</dependency>

      <plugins>
        <plugin>
            <groupId>org.apache.maven.plugins</groupId>
            <artifactId>maven-shade-plugin</artifactId>
            <version>2.4.3</version>
            <configuration>
                <createDependencyReducedPom>false</createDependencyReducedPom>
            </configuration>
            <executions>
                <execution>
                    <phase>package</phase>
                    <goals>
                        <goal>shade</goal>
                    </goals>
                    <configuration>
                    	<transformers>
				            <transformer implementation="com.github.edwgiz.mavenShadePlugin.log4j2CacheTransformer.PluginsCacheFileTransformer">
				            </transformer>
				          </transformers>
                        <artifactSet>
                            <excludes>
                                <exclude>org.apache.tomcat.embed:*</exclude>
                            </excludes>
                        </artifactSet>
                    </configuration>

                </execution>
            </executions>
            <dependencies>
		      <dependency>
		        <groupId>com.github.edwgiz</groupId>
		        <artifactId>maven-shade-plugin.log4j2-cachefile-transformer</artifactId>
		        <version>2.8.1</version>
		      </dependency>
		    </dependencies>
        </plugin>
    </plugins>

updates about this?

I got around it SLF4J. Still have bugs, but at least I am getting something to log to Cloudwatch.

I got it working by using 2.8.2.
<log4j2.version>2.8.2</log4j2.version>

I am seeing this error pop up when I bring in spring boot parent.
<parent>
    <groupId>org.springframework.boot</groupId>
    <artifactId>spring-boot-starter-parent</artifactId>
    <version>2.1.0.RELEASE</version>
    <relativePath /> <!-- lookup parent from repository -->
</parent>

Got into this as well, looks like I cannot use aws-lambda-java-libs with shade

For me, the issue was caused by having a parent pom. Removing the parent solved it for me.

@ncremaschini I too am trying to get the custom AWS lambda appender to work with Spring Boot. For now, I am using a Logback configuration that can log stack traces as a single CloudWatch event. You can find it on my GitHub page.

@vdsysvd could you throw some light on why this worked?

authors: Ghilteras MarkusKramer NicholasPurdy PyvesB feinstein kkishoreathena medinarrior mrosner17 ncremaschini nmichalares paulosuzart


text:
A Sink option to inherit file permissions from the parent HDFS folder

A Sink option to inherit file permissions from the parent HDFS folder.
This applies to any sink that writes to HDFS, e.g. Hive, Hdfs, Parquet, etc…
The problem is when an administrator has granted write permissions at the group level for a particular  HDFS folder,  then subsequent sub-folders and files created don’t inherit the write permission because the default UMASK policy is usually set to 022 – this means when a new file or folder is created the write permission bit is removed.
One could explicitly pass in a Filesystem object with the UMASK bit set appropriately for the sink but it would be nice feature to have an option to do this automagically on the sink.
val umask = new FsPermission("002")
...
val permissionToUse:FsPermission = (get permissions from parent folder)
permissionToUse.applyUMask(umask)
...
val fileSystem = FileSystem.get(new Configuration())
val stream = FileSystem.create(fileSystem, path, permissionToUse)

In eel 0.98.0 you can do HiveSource("xxx").withPermission(new FsPermission("700")) and then all files will use that ACL. It's not quite inherit permissions but you can use it for the same thing.

Yeah I guess you could obtain the file permission from parent folder and pass its FsPermission to withPermisson.
My only question is why is it on the HiveSource and not on the HiveSink ?
Another option to consider is HiveSink(blah).withPermissionsFromParent

It's on sink not source that's just me getting confused. I'll do the parent
thing too then.
On 16 Sep 2016 08:05, "hannesmiller" notifications@github.com wrote:

Yeah I guess you could obtain the file permission from parent folder and
pass its FsPermission to withPermisson.
My only question is why is it on the HiveSource and not on the
HiveSink ?
Another option to consider is HiveSink(blah).withPermissionsFromParent
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/eel-sdk/eel/issues/157#issuecomment-247532526, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAtZGh3R_txVKCuHOMZwvsoVTg6icp9Qks5qqj-cgaJpZM4JckhG
.

That would be cool!
It probably doesn't sound like a big deal but I have had permission headaches in the past where there are multiple writers belonging to the same functional group and whose permissions are set to 775 on the root folder.

User1 writes a file under a new partition directory created as 755 - where User1 is the owner

User2 attempts to write a file to the partitioned directory but cannot because the group perms are read & execute

Typically UAT & PROD applications are set up with one system account and owner permissions suffice but in DEV this problem rears its ugly head difficult to diagnose with cryptic error messages

HiveSink(Database, Table).withIOThreads(4).withInheritPermission(true)

authors: hannesmiller sksamuel

repo: eel-sdk/eel

license_source: bigquery


text:
TypeScript definition should use unions type over base type

Describe the bug
After you parse an document, you cannot narrow down the return type but check type.
To Reproduce
const doc = yaml.parseDocument(str);
const { type } = doc.contents || {};
if (doc.contents?.type === Type.MAP) {
    // doc.contents is detected as Node
}

Expected behaviour
const doc = yaml.parseDocument(str);
const { type } = doc.contents || {};
if (doc.contents?.type === Type.MAP) {
    // doc.contents is detected as BlockMap
}

Versions (please complete the following information):

Environment: Node.js 14
yaml: 1.10.0 or 2.0.0-1

Additional context
This can be fixed by replacing type of Parsed.contents to union type.
type AllNodeType = AST.FlowMap | AST.BlockMap; // Union of all possible types
interface Parsed extends Document {
  contents: AllNodeType | null
  /** The schema used with the document. */
  schema: Schema
 }

This is work as long as type is not duplicated. This is pretty common in TypeScript. You can read more at the official document.

A PR for this would be welcome. The same issue is probably repeated in other parts of the library as well. With #203 I'm starting to introduce more TS code into the source of yaml, but there isn't a schedule for if/when that might extend to replacing all of the current JS codebase, which necessitates these hand-crafted d.ts files.

A PR for this would be welcome. The same issue is probably repeated in other parts of the library as well. With #203 I'm starting to introduce more TS code into the source of yaml, but there isn't a schedule for if/when that might extend to replacing all of the current JS codebase, which necessitates these hand-crafted d.ts files.

@joshuaavalon I specified the parsed content type a bit, to Scalar | YAMLMap | YAMLSeq | null. Is that enough for your purposes, or were you doing something even more specific?

@joshuaavalon I specified the parsed content type a bit, to Scalar | YAMLMap | YAMLSeq | null. Is that enough for your purposes, or were you doing something even more specific?

@eemeli If you use the base type (i.e. YAMLMap) instead of the implementation type (i.e. FlowMap), TypeScript can only detected it as YAMLMap. It is better to create a type that contain all implementation types.
type Scalars = BlockFolded | BlockLiteral  | PlainValue | QuoteDouble | QuoteSingle;
type Maps = FlowMap | BlockMap;
type Seqs = FlowSeq | BlockSeq;

type AllNodeTypes = Scalars | Maps | Seqs;

From TypeScript compiler, it you don't state the implementation types, it does not know what is the possible types.
If you want to support custom nodes better, you can even use generics:
interface Parsed<T extends AllNodeTypes = AllNodeTypes> extends Document {
  contents: T | null
  schema: Schema
 }

This will allows users to add their custom types.

@eemeli If you use the base type (i.e. YAMLMap) instead of the implementation type (i.e. FlowMap), TypeScript can only detected it as YAMLMap. It is better to create a type that contain all implementation types.
type Scalars = BlockFolded | BlockLiteral  | PlainValue | QuoteDouble | QuoteSingle;
type Maps = FlowMap | BlockMap;
type Seqs = FlowSeq | BlockSeq;

type AllNodeTypes = Scalars | Maps | Seqs;

From TypeScript compiler, it you don't state the implementation types, it does not know what is the possible types.
If you want to support custom nodes better, you can even use generics:
interface Parsed<T extends AllNodeTypes = AllNodeTypes> extends Document {
  contents: T | null
  schema: Schema
 }

This will allows users to add their custom types.

Ah, but there's the rub; at this level, Scalar, YAMLMap and YAMLSeq are the implementation types. The last of those, for instance, is internally constructed by calling new YAMLSeq() for both flow & block sequences. It's also perfectly fine to switch the type of a node within its supported range, so e.g. this works:
const doc = YAML.parseDocument('- one\n- two\n')
doc.contents.type = 'FLOW_SEQ'
String(doc) === '[ one, two ]\n'

Ah, but there's the rub; at this level, Scalar, YAMLMap and YAMLSeq are the implementation types. The last of those, for instance, is internally constructed by calling new YAMLSeq() for both flow & block sequences. It's also perfectly fine to switch the type of a node within its supported range, so e.g. this works:
const doc = YAML.parseDocument('- one\n- two\n')
doc.contents.type = 'FLOW_SEQ'
String(doc) === '[ one, two ]\n'

I still think using implementation type is better. Since that use case is not documented, there is no need to expose internal api. If others want to use internal api, they can cast the type themselves.

I still think using implementation type is better. Since that use case is not documented, there is no need to expose internal api. If others want to use internal api, they can cast the type themselves.

The perhaps the documentation ought to be improved to make it even clearer, as the behaviour of the stringifier is documented e.g. here: https://eemeli.org/yaml/#collections
And, as I mentioned before, in the AST, Scalar, YAMLMap and YAMLSeq are the actual implementations of the nodes. In the source JS code there are not different Node descendants for e.g. flow & block sequences, just the one YAMLSeq. This is what the TS typings are intended to convey.

The perhaps the documentation ought to be improved to make it even clearer, as the behaviour of the stringifier is documented e.g. here: https://eemeli.org/yaml/#collections
And, as I mentioned before, in the AST, Scalar, YAMLMap and YAMLSeq are the actual implementations of the nodes. In the source JS code there are not different Node descendants for e.g. flow & block sequences, just the one YAMLSeq. This is what the TS typings are intended to convey.

The docs now mention type modifications more explicitly: https://eemeli.org/yaml/#modifying-nodes

The docs now mention type modifications more explicitly: https://eemeli.org/yaml/#modifying-nodes

authors: eemeli joshuaavalon

repo: eemeli/yaml

license: ISC


text:
Install nix on ubuntu 22.04 - running smoke test - missing libgit2.so.1.1

Description
Did fresh install of nix on a linux ubuntu 22.04 - cloned the openlane2 repo - opened a nix-shell in that repo and ran openlane --smoke_test
File log: - Looks like libgit2.so.1.1 is missing
File "/nix/store/jr2jxhcp4qybkyz8was3ym6m35cd869d-python3-3.11.6-env/lib/python3.11/site-packages/klayout/db/init.py", line 3, in
import klayout.dbcore
ImportError: libgit2.so.1.1: cannot open shared object file: No such file or directory
[11:05:45] ERROR    Subprocess had a non-zero exit.                                                                                step.py:1308
[11:05:45] ERROR    Last 9 line(s):                                                                                step.py:1313
Traceback (most recent call last):
File "/nix/store/jr2jxhcp4qybkyz8was3ym6m35cd869d-python3-3.11.6-env/lib/python3.11/site-packages/openlane/scripts/klayout/stream_out.py", line 50, in
import pya
File "/nix/store/jr2jxhcp4qybkyz8was3ym6m35cd869d-python3-3.11.6-env/lib/python3.11/site-packages/pya/init.py", line 5, in
from klayout.db import *  # noqa
^^^^^^^^^^^^^^^^^^^^^^^^
File "/nix/store/jr2jxhcp4qybkyz8was3ym6m35cd869d-python3-3.11.6-env/lib/python3.11/site-packages/klayout/db/init.py", line 3, in
import klayout.dbcore
ImportError: libgit2.so.1.1: cannot open shared object file: No such file or directory
[11:05:45] ERROR    Full log file: '../../../../tmp/tmppxwkart1openlane2/smoke_test_design/runs/RUN_2024-06-22_11-05-04/54-klayout-streamout/klayout-streamout.log'                                                step.py:1316
[11:05:45] WARNING  The following warnings were generated by the flow:                                                                                flow.py:671
[11:05:45] WARNING  [Odb.CustomIOPlacement] Overriding minimum distance 0.1 with 0.42 for pins on side N to avoid overlap.                                                                                flow.py:673
[11:05:45] WARNING  [OpenROAD.DetailedRouting] [DRT-0349] LEF58_ENCLOSURE with no CUTCLASS is not supported. Skipping for layer mcon (and 9 similar warnings)                                                       flow.py:673
[11:05:45] WARNING  [Checker.WireLength] Threshold for Threshold-surpassing long wires is not set. The checker will be skipped.                                                                                flow.py:673
[11:05:45] WARNING  [OpenROAD.IRDropReport] 'VSRC_LOC_FILES' was not given a value, which may make the results of IR drop analysis inaccurate. If you are not integrating a top-level chip for manufacture, you may flow.py:673
ignore this warning, otherwise, see the documentation for 'VSRC_LOC_FILES'.
[11:05:45] ERROR    The following error was encountered while running the flow:                                                                                main.py:152
GDSII Stream Out (KLayout): subprocess (1, ['/nix/store/jr2jxhcp4qybkyz8was3ym6m35cd869d-python3-3.11.6-env/bin/python3.11',
'/nix/store/jr2jxhcp4qybkyz8was3ym6m35cd869d-python3-3.11.6-env/lib/python3.11/site-packages/openlane/scripts/klayout/stream_out.py',
'/tmp/tmppxwkart1openlane2/smoke_test_design/runs/RUN_2024-06-22_11-05-04/49-openroad-fillinsertion/spm.def', '--output',
'/tmp/tmppxwkart1openlane2/smoke_test_design/runs/RUN_2024-06-22_11-05-04/54-klayout-streamout/spm.klayout.gds', '--top', 'spm', '--lyp',
'/home/jakobsen/.volare/volare/sky130/versions/bdc9412b3e468c102d01b7cf6337be06ec6e9c9a/sky130A/libs.tech/klayout/tech/sky130A.lyp', '--lyt',
'/home/jakobsen/.volare/volare/sky130/versions/bdc9412b3e468c102d01b7cf6337be06ec6e9c9a/sky130A/libs.tech/klayout/tech/sky130A.lyt', '--lym',
'/home/jakobsen/.volare/volare/sky130/versions/bdc9412b3e468c102d01b7cf6337be06ec6e9c9a/sky130A/libs.tech/klayout/tech/sky130A.map', '--input-lef',
'/home/jakobsen/.volare/volare/sky130/versions/bdc9412b3e468c102d01b7cf6337be06ec6e9c9a/sky130A/libs.ref/sky130_fd_sc_hd/techlef/sky130_fd_sc_hd__nom.tlef', '--input-lef',
'/home/jakobsen/.volare/volare/sky130/versions/bdc9412b3e468c102d01b7cf6337be06ec6e9c9a/sky130A/libs.ref/sky130_fd_sc_hd/lef/sky130_fd_sc_hd.lef', '--input-lef',
'/home/jakobsen/.volare/volare/sky130/versions/bdc9412b3e468c102d01b7cf6337be06ec6e9c9a/sky130A/libs.ref/sky130_fd_sc_hd/lef/sky130_ef_sc_hd.lef', '--with-gds-file',
'/home/jakobsen/.volare/volare/sky130/versions/bdc9412b3e468c102d01b7cf6337be06ec6e9c9a/sky130A/libs.ref/sky130_fd_sc_hd/gds/sky130_fd_sc_hd.gds']) failed
[11:05:45] ERROR    OpenLane will now quit.                                                                                main.py:153
Classic - Stage 57 - GDSII Stream Out (KLayout) ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━╸━━━━━━━━━━ 56/75 0:00:41
[nix-shell:~/opentools/openlane2]$ klayout
klayout: error while loading shared libraries: libgit2.so.1.1: cannot open shared object file: No such file or directory
[nix-shell:~/opentools/openlane2]$
Expected Behavior
Build some thing :-)
Environment report
kernel: Linux
kernel_version: 6.8.1-060801-generic
supported: True
distro: ubuntu
distro_version: 22.04
python_version: 3.11.6
python_path:
  - /nix/store/9jb8wsk32ny2yy5ghcaq3y7mbmmavi2c-python3.11-openlane/bin
  - /nix/store/jr2jxhcp4qybkyz8was3ym6m35cd869d-python3-3.11.6-env/lib/python3.11/site-packages
  - /nix/store/qp5zys77biz7imbk6yy85q5pdv7qk84j-python3-3.11.6/lib/python311.zip
  - /nix/store/qp5zys77biz7imbk6yy85q5pdv7qk84j-python3-3.11.6/lib/python3.11
  - /nix/store/qp5zys77biz7imbk6yy85q5pdv7qk84j-python3-3.11.6/lib/python3.11/lib-dynload
  - /nix/store/qp5zys77biz7imbk6yy85q5pdv7qk84j-python3-3.11.6/lib/python3.11/site-packages
  - /nix/store/9jb8wsk32ny2yy5ghcaq3y7mbmmavi2c-python3.11-openlane/lib/python3.11/site-packages
  - /nix/store/2z0jalw27lp6zm642aqvnlydlqblhcdf-python3.11-click-8.1.7/lib/python3.11/site-packages
  - /nix/store/m1a3bk12cjgk6wq445pi7xch3v2gx8ql-python3.11-cloup-3.0.2/lib/python3.11/site-packages
  - /nix/store/a8z71acldic6hqdbd18sd81sqcqgygd3-python3.11-pyyaml-6.0.1/lib/python3.11/site-packages
  - /nix/store/jlb8fjb88bx2adivdz8pq8cx5aj5615h-python3.11-rich-13.5.2/lib/python3.11/site-packages
  - /nix/store/8x0qa1j4z2907a9pvvf9lwzs6n58i5m5-python3.11-markdown-it-py-3.0.0/lib/python3.11/site-packages
  - /nix/store/69l2fjl76rad6fz5n5v38px2kiwcz5x8-python3.11-mdurl-0.1.2/lib/python3.11/site-packages
  - /nix/store/ljd22jdzx6kj0hj7wsnhr71gqa4iqj88-python3.11-pygments-2.16.1/lib/python3.11/site-packages
  - /nix/store/y8yq448xka665bqyd5gvdhajqdbsnyys-python3.11-setuptools-68.2.2/lib/python3.11/site-packages
  - /nix/store/71js2p8zx17fqgq2m1b5f7q92ig0v7nn-python3.11-requests-2.31.0/lib/python3.11/site-packages
  - /nix/store/6jj18jqyik8k06plad2hm9fwcrnhpxf3-python3.11-brotlicffi-1.1.0.0/lib/python3.11/site-packages
  - /nix/store/qxsnv4322wqi9w629b572k898viw756h-python3.11-cffi-1.16.0/lib/python3.11/site-packages
  - /nix/store/r0mzj4k7gzx3bp4mbnr69x6if6lxxsb1-python3.11-pycparser-2.21/lib/python3.11/site-packages
  - /nix/store/hk5xz5kyhr1vaq2p65990c2fxw7mxlmp-python3.11-certifi-2023.07.22/lib/python3.11/site-packages
  - /nix/store/g3kzbrnirxky2w4g3n67p01745pa8xcc-python3.11-charset-normalizer-3.2.0/lib/python3.11/site-packages
  - /nix/store/g3w192qs0avwjaw776yiyaq5l0dcbwdp-python3.11-idna-3.4/lib/python3.11/site-packages
  - /nix/store/71236y06cag3yb637q5jj358ci6f20ah-python3.11-urllib3-2.0.7/lib/python3.11/site-packages
  - /nix/store/bnadfkpcdkmrzymnpyj8x2bdxq1f6kdw-python3.11-pcpp-1.30/lib/python3.11/site-packages
  - /nix/store/i41k9kc0s446fw5vl4k05vfq3prw06hv-python3.11-volare/lib/python3.11/site-packages
  - /nix/store/i46q5s4xj3700m2srcx4rd2bv2x6w51h-python3.11-httpx-0.25.0/lib/python3.11/site-packages
  - /nix/store/6ckbxrfj5q372da9svdh7hnh67vbwyhc-python3.11-httpcore-0.18.0/lib/python3.11/site-packages
  - /nix/store/43sv2g5lsl58md1lzidlx1g7xam2mpqp-python3.11-anyio-4.0.0/lib/python3.11/site-packages
  - /nix/store/4m6453i7as66sdmkck8fiwk793lx1b29-python3.11-sniffio-1.3.0/lib/python3.11/site-packages
  - /nix/store/1c9w7989rjr417rs50bxsrinjf63mz8n-python3.11-h11-0.14.0/lib/python3.11/site-packages
  - /nix/store/q9c0733drxk1zv5j60hq0lz61g395dic-python3.11-rfc3986-2.0.0/lib/python3.11/site-packages
  - /nix/store/i24kszh5ajb03gwhjlmb1df6sm0s0x72-python3.11-zstandard-0.21.0/lib/python3.11/site-packages
  - /nix/store/608w6rc3xa1mj44ppara7pnmr6z6kbpn-python3.11-tkinter-3.11.6/lib/python3.11/site-packages
  - /nix/store/k2xqs2rp3kyb0pbq1sn9v0sh05q0cmvc-python3.11-lxml-4.9.3-3/lib/python3.11/site-packages
  - /nix/store/vp0ivbg65mnsjvfgyran0x1bzsf3x66l-python3.11-deprecated-1.2.14/lib/python3.11/site-packages
  - /nix/store/bj6g1njs2z0ivrwlpkls9qr1ar1psjaw-python3.11-wrapt-1.14.1/lib/python3.11/site-packages
  - /nix/store/cghmw4316dgv9f86y6prdybi50v1f8sn-python3.11-immutabledict-3.0.0/lib/python3.11/site-packages
  - /nix/store/sqp8y9xj0fbsmmmlyk6chhpc5wq7w3gb-python3.11-libparse/lib/python3.11/site-packages
  - /nix/store/8wkz5a9z1ppwjvr54375k69avhkmz4nc-python3.11-psutil-5.9.6/lib/python3.11/site-packages
  - /nix/store/kn3xxzgq9bx9av42h495bvxnslyg41v1-klayout-pymod/lib/python3.11/site-packages
tkinter: True
container_info: None
nix_info:
  version_string: nix (Nix) 2.23.0
  channels:
  nix_command: True
  flakes: True

Reproduction material
did not work
Relevant log output
[nix-shell:~/opentools/openlane2]$ klayout -version
klayout: error while loading shared libraries: libgit2.so.1.1: cannot open shared object file: No such file or directory

Found the error :-)  - And all good now

Antenna
Passed ✅

LVS
Passed ✅

DRC
Passed ✅

[11:30:31] INFO     Saving views to '/tmp/tmp4ehmkxuuopenlane2/smoke_test_design/runs/RUN_2024-06-22_11-29-39/final'…                                                                                state.py:193
[11:30:31] INFO     Flow complete.                                                                                sequential.py:294
Classic - Stage 75 - Report Manufacturability ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 75/75 0:00:51
[11:30:31] WARNING  The following warnings were generated by the flow:                                                                                flow.py:671
[11:30:31] WARNING  [Odb.CustomIOPlacement] Overriding minimum distance 0.1 with 0.42 for pins on side N to avoid overlap.                                                                                flow.py:673
[11:30:31] WARNING  [OpenROAD.DetailedRouting] [DRT-0349] LEF58_ENCLOSURE with no CUTCLASS is not supported. Skipping for layer mcon (and 9 similar warnings)                                                       flow.py:673
[11:30:31] WARNING  [Checker.WireLength] Threshold for Threshold-surpassing long wires is not set. The checker will be skipped.                                                                                flow.py:673
[11:30:31] WARNING  [OpenROAD.IRDropReport] 'VSRC_LOC_FILES' was not given a value, which may make the results of IR drop analysis inaccurate. If you are not integrating a top-level chip for manufacture, you may flow.py:673
ignore this warning, otherwise, see the documentation for 'VSRC_LOC_FILES'.
[11:30:31] INFO     Smoke test passed.                                                                                main.py:267
[nix-shell:~/opentools/openlane2]$

On my machine it use a local klayout build and have set LD_LIBRARY_PATH
klayout is /home/jakobsen/opentools/klayout/bin-release/klayout
jakobsen@t14:~$ echo $LD_LIBRARY_PATH
:/home/jakobsen/opentools/klayout/bin-release
jakobsen@t14:~$ klayout -v
KLayout 0.29.0
jakobsen@t14:~$

In my nix environment - the LIB_LIBRARY_PATH is still there an klayout misses out on libgit2.so....
akobsen@t14:~$ cd opentools/openlane2/
jakobsen@t14:~/opentools/openlane2$ ls
Authors.md    flake.lock  nix                Readme.md              setup.py
Changelog.md  flake.nix   notebook.ipynb     requirements_dev.txt   shell.nix
default.nix   License     openlane           requirements_docs.txt  test
docs          Makefile    openlane2_env.log  requirements.txt       type_stubs
jakobsen@t14:~/opentools/openlane2$ nix-shell

[nix-shell:~/opentools/openlane2]$ type klayout
klayout is /nix/store/gvq51plg4ydzfxma0m46w82jbvngvnch-klayout/bin/klayout

[nix-shell:~/opentools/openlane2]$ echo $LD_LIBRARY_PATH
:/home/jakobsen/opentools/klayout/bin-release:/home/jakobsen/opentools/klayout/bin-release

[nix-shell:~/opentools/openlane2]$ klayout -v
klayout: error while loading shared libraries: libgit2.so.1.1: cannot open shared object file: No such file or directory

[nix-shell:~/opentools/openlane2]$

/J

I don't know how you're setting LD_LIBRARY_PATH, but you could set it as follows:
export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/home/jakobsen/opentools/klayout/bin-release/klayout

This will make sure the right libraries can be loaded first.
Thanks for giving OpenLane 2 a try, Jørgen!

Hi Donn
That is how it all ready get set from my .bashrc file:
export PATH=$PATH:/home/jakobsen/opentools/klayout/bin-release:/home/jakobsen/.cargo/bin
export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/home/jakobsen/opentools/klayout/bin-release

In nix-shell I just get the my original LD_LIBRARY_PATH added again.
jakobsen@t14:~/opentools/openlane2$ nix-shell

[nix-shell:~/opentools/openlane2]$ echo $LD_LIBRARY_PATH
:/home/jakobsen/opentools/klayout/bin-release/klayout:/home/jakobsen/opentools/klayout/bin-release/klayout

I will try to see if I can find out why.
Yes - Openlane2 looks very nice. I will try so run some of my design this way.
/J

Sadly this appears to be inherent to Nix. You can add something like this to your rcfile:
if [ "$IN_NIX_SHELL" = "" ]; then
	export LD_LIBRARY_PATH=…
fi

authors: donn jorgenkraghjakobsen


text:
🛑 Jorge Retamoza Web is down

In 78476dd, Jorge Retamoza Web (https://www.retamoza.com.ar) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Jorge Retamoza Web is back up in e64cc80.

repo: efecear/upptime


text:
🛑 Veterinaria Colonia Animal is down

In 0de9dd7, Veterinaria Colonia Animal (https://www.coloniaanimal.com) was down:

HTTP code: 500
Response time: 656 ms

Resolved: Veterinaria Colonia Animal is back up in 48a5537 after 12 minutes.


text:
🛑 Nodo UTT Morón is down

In f0caa5e, Nodo UTT Morón (https://www.nodouttmoron.com.ar) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Nodo UTT Morón is back up in 7679573.


text:
🛑 Nodo UTT Ramos Mejia is down

In 2caf29e, Nodo UTT Ramos Mejia (https://www.uttnodoramosmejia.com.ar) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Nodo UTT Ramos Mejia is back up in 7442667.


text:
🛑 Almacén BioPandora is down

In 8f66284, Almacén BioPandora (https://www.biopandora.com.ar) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Almacén BioPandora is back up in fe9b0f1.


text:
Check return type annotation of object operations

Following up on #148, we should type check the return type annotation of object operations.
As of right now, we reject all return type annotations given by the user on an object operation.
Instead, we should properly check both the return type and the given set of effects.
There is some subtlety required to do this properly -- capability passing should be informed by the declared effects,
not by the user-annotated effects. See the discussion in #148 for more details.
Relevant code to be changed:
https://github.com/effekt-lang/effekt/blob/a6201f56e7c33d7674708d192e9ee39b41a2fc09/effekt/shared/src/main/scala/effekt/Typer.scala#L357-L368

I just want to mention that one intermediate step might be to implement block parameters on interfaces and objects (but not handlers, yet). This would make it much easier to implement tests that involve capture sets.

authors: b-studios jiribenes

repo: effekt-lang/effekt


text:
[Treantjs]: how to add text on the connect edge?

Description from treantjs issue

how to add text on the connect edge as the following?
simple_chart_config = {
    chart: {
        container: "#tree-simple",
      rootOrientation: "WEST",
       levelSeparation: 450,
      nodeAlign: "BOTTOM",
       connectors: {
      type: "step",
      style: {
        "stroke-width": 2
      }
    },
    },

    nodeStructure: {
        text: { name: "Parent node" },
        children: [
            {
                text: { name: "First child" }
            },
            {
                text: { name: "Second child" }
            }
        ]
    }
};

var my_chart = new Treant(simple_chart_config);

Treantjs issue link
https://github.com/fperucic/treant-js/issues/154

To add text labels to the connectors (edges) between parent and child nodes in a Treant chart, we can use the HTMLclass property within the connectors configuration and then add CSS to style the labels.

authors: egor-progger isidrohan

repo: egor-progger/pointlinejs


text:
Preregistration Template

Complete the preregistration template prior to preregistering VEFMAP analysis.

I'm going to close this, because I think the workflow has been described in the draft manuscript already.

repo: egouldo/EcoConsPreReg


text:
[Prachi] | Added code for muster roll search page

Added page for Search Attendance for testing purpose

@prachirane-eGov  add this ui customisation in this file as well micro-ui/web/src/Customisations

authors: jagankumar-egov prachirane-eGov

repo: egovernments/DIGIT-Works


text:
Add set-length and set-get

Without these, we can't walk over a set nor match its contents.
See tests/set.egg for examples.

I'm a little bit unsure about set-get since this seems un-idiomatic. In eggcc I had a user-defined set->vec primitive that can achieve something similar.

authors: rtjoa yihozhang

repo: egraphs-good/egglog


text:
Failure in ConcurrentWeakIdentityHashMapTest

java.lang.AssertionError:
Expected: is <9127>
but: was <10239>
See the following build for details.

@alexsnaps You may want to have a look into this.


text:
Add broadcasting of a new release to the docs

LFPH, CC Slack, MinI&W

Closing as LFPH have ceased operation and the others are country-specific.

authors: dslmeinte ryanbnl

repo: ehn-dcc-development/eu-dcc-valuesets


text:
Display site title option, Display site logo option

Options in the theme config to allow the site title to either be displayed or not displayed, likewise for the logo.  Not every site will want a logo and not every site will want a title.

Done - but in a hacky way.  It is a display: none option through theme-ui.  Not the best implementation however it works for now and given the small size there shouldn't be much performance hit.  Ideally this would be redone with javascript to just remove the logo or site-title entirely.

repo: ehowey/gatsby-theme-catalyst-core


text:
[question] Example of use filename patterns

Hello.
Will You give me a pattern example basing on a sample filename I've prepared ?
My current pattern is:
__imagepicka/[${pageHostname}] ${pageTitle} [${dateString}]/${index} - ${name}${ext}
Sample page title would be:
This is a site with Rubik cubes - index001 - something else
I would like to have only this as a title (just cut the first sentence only, until first '-' character):
This is a site with Rubik cubes
Is it possible ? How to write it ? Can I use regular expressions here (parenthesies) ?

Currently regexp is not supported. See #64. For this case, you may use .split(' - ') and get the first item.

Currently regexp is not supported. See #64. For this case, you may use .split(' - ') and get the first item.

Thanks for info.
I've spent some time on trying my best in one line, but finally I did it.
One example of how I used it:
Image Picka/[${hostname}]/${pageTitle} [${pageUrl.slice(pageUrl.replace(/\/$/,'').lastIndexOf('/')+1,pageUrl.length-1)}]/${name}${ext}
..and it works pretty nice.
Thanks!


text:
Fibonacci series in C

Issue no #48

The issue is for Fibonacci Search not Fibbonacci series. Please look into what the issue specifies and mentions

repo: ekdnam/Algorithms


text:
[load-testing] add support for IBM JVMs

What does this PR do?
Allows to use IBM JVMs for load-testing, those being packaged as executable binaries and not "regular" zip/tar.gz archives.

Codecov Report

Merging #1739 (d366e76) into master (fdfaa7c) will decrease coverage by 0.01%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##             master    #1739      +/-   ##
============================================
- Coverage     61.13%   61.12%   -0.02%
+ Complexity     3612     3611       -1
============================================
  Files           402      402
  Lines         18281    18281
  Branches       2508     2508
============================================
- Hits          11177    11175       -2
- Misses         6320     6322       +2
  Partials        784      784

Impacted Files
Coverage Δ
Complexity Δ

...ic/apm/agent/profiler/collections/LongHashSet.java
16.66% <0.00%> (-0.80%)
12.00% <0.00%> (-1.00%)

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 a8cb267...d366e76. Read the comment docs.

:green_heart: Build Succeeded

the below badges are clickable and redirect to their specific view in the CI or DOCS

Expand to view the summary

Build stats

Build Cause: Pull request #1739 opened

Start Time: 2021-04-02T13:53:30.424+0000

Duration: 54 min 12 sec

Commit: d366e76ee7c0c443f7cdc3f4be6926dd53818568

Test stats :test_tube:

Test
Results

Failed
0

Passed
1982

Skipped
19

Total
2001

Trends :test_tube:

:green_heart: Flaky test report
Tests succeeded.

Expand to view the summary

Test stats :test_tube:

Test
Results

Failed
0

Passed
1982

Skipped
19

Total
2001

authors: SylvainJuge apmmachine codecov-io

repo: elastic/apm-agent-java


text:
Add nullable support to Elastic.CommonSchema.Serilog

Introduce TryGetScalarString as extention to TryGetScalarPropertyValue that does not assume ScalarProperty.Value is never null if returned.
Further more this enables stricter null checks.

Hi, Is this released already? if so, in which version? Thanks

authors: Mpdreamz guisantos

repo: elastic/ecs-dotnet


text:
Expose Stats within Spark

What kind an issue is this?

[ ] Bug report. If you’ve found a bug, please provide a code snippet or test to reproduce it below.
The easier it is to track down the bug, the faster it is solved.
[x] Feature Request. Start by telling us what problem you’re trying to solve.
Often a solution already exists! Don’t send pull requests to implement new features without
first getting our support. Sometimes we leave features out on purpose to keep the project small.

Feature description
It'd be nice to be able to get ahold of the Stats object post write within the Spark pipeline. This would allow diagnosis of pipeline performance issues from not just the ES Server side but also on the Client side.
I think the easiest and simplest method would be to provide the Stats as a new Partition/RDD after the writes have all been preformed. This would allow the user to control how the stats are published respective of their platform. This would involve changes with the EsRDDWriter to record the stats post write. As well as the EsSpark and JavaEsSpark classes to return the data as apposed to returning nothing.

I agree that exposing the stats in Spark is a great idea, though I'm not sure how I feel about them being a resulting rdd afterward. Much of our code is laid out as though the ES connector is an action in Spark, thus running the job. That said, there is some demand for returning and RDD/Dataset of failed writes to Elasticsearch after trying to write to ES. We could probably support both with a transformation-like RDD/Dataset operation, but I think we should make sure there are no other more appropriate routes to returning the job metrics to users before going down that path.

If there hasn't been any progress here, I'd be interested in tackling this. The latter idea from @nerdynick seems flexible (not hard to construct an RDD from it or provide a util for it) and it shouldn't need to alter the spark-sql write api. Stats land in ReportingUtils and increment the counters, but could also accumulate into an exposed, top-level stats.
Agreed that failed records seem suited to a transformation output, but that could be handled separately from exposing stats

I can confirm that there hasn't been any work done on this yet from at least my end. Having looked at the issue again, I'm still not sure what the best route to follow would be from an API perspective. Perhaps if we had some information on how other integrations in the Spark ecosystem manage statistics, it would put my paranoia about modifying the main api to rest.

authors: glasperfan jbaiera nerdynick

repo: elastic/elasticsearch-hadoop


text:
Spark mode overwrite not working when using Dynamic/multi resource writes

Issue description
Spark mode overwrite not working when using Dynamic/multi resource writes.
Data in Elastic are duplicated not overwritten.
Steps to reproduce
Code:
    df.write.format("org.elasticsearch.spark.sql"). \
        option("es.resource", "my_index-{date_bucket}"). \
        option("es.nodes.wan.only", "true"). \
        option("es.http.timeout", "3m"). \
        option("es.port", "920"). \
        option("spark.es.net.http.auth.user", ""). \
        option("spark.es.net.http.auth.pass", ""). \
        option("es.nodes", "http://elastic.abc.com"). \
        mode("overwrite").save()

This code working as expected:
    df.write.format("org.elasticsearch.spark.sql"). \
        option("es.resource", "my_index"). \
        option("es.nodes.wan.only", "true"). \
        option("es.http.timeout", "3m"). \
        option("es.port", "920"). \
        option("spark.es.net.http.auth.user", ""). \
        option("spark.es.net.http.auth.pass", ""). \
        option("es.nodes", "http://elastic.abc.com"). \
        mode("overwrite").save()

Version Info
Hadoop/Spark:  Spark 3.1.1
ES-Hadoop   :  elasticsearch-spark-30_2.12-7.13.0-20210303.042227-17.jar
ES          :  7.7.1

The connector attempts to delete data before saving a dataframe when using the overwrite mode. The deletion operation takes place on the job driver before any tasks are submitted. The job driver isn't able to resolve the index pattern into a real index name because it doesn't have any records to pull values from. In this scenario, the driver simply treats the patterned index as a plain index name and checks if it exists. Since no index exists with that plain index name, the driver skips the deletion phase and just runs the job.
We should be detecting this configuration problem at runtime and throw an exception. It's possible that we could expand patterned resources into a glob pattern (use * in place of the pattern placeholders), but that should probably be controllable with a setting of some sort.

I opened #1637 to better capture this problem. Closing this issue in the mean time.

authors: dlubomski jbaiera


text:
Update a document without increasing the version.

Hi everyone,
I would like to know if It's possible to update a document without changing the document version?.
The reason is because my document needs to remove a property, in my case I use a script for do it, so look at this example:
                var respo = this.Client.Update<object>(descriptor => descriptor
                    .Id(myId)
                    .Type(myDocType)
                    .Index(myIndex)
                    .Script(string.Format("ctx._source.remove(\"{0}\")", "\\" + SessionFieldName))
                    );

I need to remove the given property, but document state is the same, so for this reason I would like to avoid that document version is modified.
Thanks in advance.

You can set version_type to force, but you would need to know the current version of the document ahead of time:
var respo = this.Client.Update<object>(descriptor => descriptor
    .Id(myId)
    .Type(myDocType)
    .Index(myIndex)
    .Version(currentVersion)
    .VersionType(VersionType.Force)
    .Script(string.Format("ctx._source.remove(\"{0}\")", "\\" + SessionFieldName))
);

See the versioning section of the elasticsearch docs for more info.

authors: TheHunter gmarz

repo: elastic/elasticsearch-net


text:
Reduce GeoDistance Insanity

https://github.com/elastic/elasticsearch/pull/19846
GeoDistance query, sort, and scripts make use of a crazy GeoDistance enum for handling 4 different ways of computing geo distance: SLOPPY_ARC, ARC, FACTOR, and PLANE. Only two of these are useful: ARC, PLANE.

I think this is covered by #2612  which completely removes GeoDistanceType?

Yep 👍  and in 5.x the old enum values will be rewritten by ES.

authors: Mpdreamz gmarz


text:
Update nest.asciidoc

Minor spelling mistake fix in nest.asciidoc

Sorry for leaving this for so long @robshakespeare, releasing 2.0 got the best of I suppose :smile:
We are working on updated docs that are powered by actual code (under Tests) so this will become obsolete rather fast.
Pulling it in nonetheless though :+1:

No problem.  Sorry for the very long reply.
Using the actual code/tests to generate the docs is a superb idea.  Keep up the great work.

authors: Mpdreamz robshakespeare


text:
Added support for enums as keys for KeyedBucket.

Given a document
{
    "color": "1"
}

and an enum definition
enum Color {
    Red = 1
}

an invalid cast exception would be throw when attempting
aggs.Terms<Color>(agg.Name).Buckets

ported to 7.x and 6.x


text:
Adds ML query optimization example

Query optimization code to accompany blog post. This contains also
submission preparation for MS MARCO Document ranking tasks.

@davidkyle @Winterflower Would be good to get some 👀 on this before merging. Nothing too detailed, just to make sure it's sane 😄

@joshdevins roger that, checking it over right now

authors: Winterflower joshdevins

repo: elastic/examples


text:
Elastic pod being flagged that privileged escalation is allowed inside that container

Chart version: elasticsearch-7.9.3 helm chart.
**Kubernetes version: 1.18.10
**Kubernetes provider: Azure
Helm Version: Helm 3
helm get release output
e.g. helm get elasticsearch (replace elasticsearch with the name of your helm release)
Be careful to obfuscate every secrets (credentials, token, public IP, ...) that could be visible in the output before copy-pasting.
If you find some secrets in plain text in helm get release output you should use Kubernetes Secrets to managed them is a secure way (see Security Example).

We have many pods deployed to this cluster, and this is the only unexpected pod being flagged that priviledged escalation is allowed inside that container. You can see from the pod spec below that privileged escalation has been set to false on this pod., yet its still being flagged by the policy. When we compare it to other pods which are not being flagged by the policy, the big difference we can see is that this contains an initContainers definition, which does run with the priviledged escalation, however I wouldn’t expect the main elasticsearch container to be flagging against the policy for a setting in the init container.
We have been able to easily prove this using the CPU and Memory Limits policy, by pulling public helm charts and updating them to include the limits in the init containers and not just the main container, and low and behold once this is done the azure policy has been flagging the pods as compliant. Whilst this “fix” works for CPU and Memory Limits, it doesn’t solve the original problem of the privileged escalation policy, as the init containers generally need to run privileged in order to perform initial setup so that the main container doesn’t need to run as root or with privileged escalation enabled.

</details>

**Describe the bug:**

**Steps to reproduce:**

1.
2.
3.

**Expected behavior:**

**Provide logs and/or server output (if relevant):**

*Be careful to obfuscate every secrets (credentials, token, public IP, ...) that could be visible in the output before copy-pasting*

**Any additional context:**

Hi @asafsofer-sl,
Elasticsearch chart use privileged so init container can configure sysctl (https://github.com/elastic/helm-charts/blob/0ff3a3c348b2cfe4fd65a17717bf8fc3e15c466d/elasticsearch/templates/statefulset.yaml#L165).
This can be disabled by setting sysctlInitContainer.enabled=false if needed.
Can you be a bit more specific about what your current problem is?

authors: asafsofer-sl jmlrt

repo: elastic/helm-charts