Image creation fails

I am trying to build this into Caddy 2.7.4. The command I am using is:
FROM caddy:2.7.4-builder AS builder

RUN xcaddy build --with github.com/muety/caddy-remote-host

FROM caddy:2.7.4

COPY --from=builder /usr/bin/caddy /usr/bin/caddy

However this fails with this log output:

 ---> db0a75ba01ef

Step 2/4 : RUN xcaddy build --with github.com/muety/caddy-remote-host

 ---> Running in f005aed7d391

2023/08/22 18:30:12 [INFO] Temporary folder: /tmp/buildenv_2023-08-22-1830.1583521926

2023/08/22 18:30:12 [INFO] Writing main module: /tmp/buildenv_2023-08-22-1830.1583521926/main.go
package main

import (
	caddycmd "github.com/caddyserver/caddy/v2/cmd"

	// plug in Caddy modules here
	_ "github.com/caddyserver/caddy/v2/modules/standard"
	_ "github.com/muety/caddy-remote-host"
)

func main() {
	caddycmd.Main()
}

2023/08/22 18:30:12 [INFO] Initializing Go module

2023/08/22 18:30:12 [INFO] exec (timeout=0s): /usr/local/go/bin/go mod init caddy

go: creating new go.mod: module caddy

go: to add module requirements and sums:
	go mod tidy

2023/08/22 18:30:12 [INFO] Pinning versions

2023/08/22 18:30:12 [INFO] exec (timeout=0s): /usr/local/go/bin/go get -d -v<EMAIL_ADDRESS>
go: downloading github.com/caddyserver/caddy/v2 v2.7.4

go: downloading github.com/caddyserver/certmagic v0.19.2

go: downloading github.com/google/uuid v1.3.0

go: downloading github.com/prometheus/client_golang v1.14.0

go: downloading github.com/quic-go/quic-go v0.37.5

go: downloading go.uber.org/zap v1.25.0

go: downloading golang.org/x/sys v0.11.0

go: downloading golang.org/x/term v0.11.0

go: downloading github.com/klauspost/cpuid/v2 v2.2.5

go: downloading github.com/libdns/libdns v0.2.1

go: downloading github.com/mholt/acmez v1.2.0

go: downloading github.com/miekg/dns v1.1.55

go: downloading github.com/zeebo/blake3 v0.2.3

go: downloading golang.org/x/crypto v0.12.0

go: downloading golang.org/x/net v0.14.0

go: downloading github.com/beorn7/perks v1.0.1

go: downloading github.com/cespare/xxhash/v2 v2.2.0

go: downloading github.com/cespare/xxhash v1.1.0

go: downloading github.com/golang/protobuf v1.5.3

go: downloading github.com/prometheus/client_model v0.3.0

go: downloading github.com/prometheus/common v0.37.0

go: downloading github.com/prometheus/procfs v0.8.0

go: downloading google.golang.org/protobuf v1.31.0

go: downloading go.uber.org/multierr v1.11.0

go: downloading github.com/quic-go/qpack v0.4.0

go: downloading github.com/golang/mock v1.6.0

go: downloading github.com/onsi/ginkgo/v2 v2.9.5

go: downloading golang.org/x/tools v0.10.0

go: downloading golang.org/x/text v0.12.0

go: downloading github.com/matttproud/golang_protobuf_extensions v1.0.1

go: downloading golang.org/x/exp v0.0.0-20230310171629-522b1b587ee0

go: downloading golang.org/x/mod v0.11.0

go: downloading github.com/quic-go/qtls-go1-20 v0.3.1

go: downloading github.com/go-task/slim-sprig v0.0.0-20230315185526-52ccab3ef572

go: downloading github.com/google/pprof v0.0.0-20210720184732-4bb14d4b1be1

go: added github.com/beorn7/perks v1.0.1
go: added github.com/caddyserver/caddy/v2 v2.7.4
go: added github.com/caddyserver/certmagic v0.19.2
go: added github.com/cespare/xxhash/v2 v2.2.0
go: added github.com/go-task/slim-sprig v0.0.0-20230315185526-52ccab3ef572
go: added github.com/golang/mock v1.6.0
go: added github.com/golang/protobuf v1.5.3
go: added github.com/google/pprof v0.0.0-20210720184732-4bb14d4b1be1
go: added github.com/google/uuid v1.3.0
go: added github.com/klauspost/cpuid/v2 v2.2.5
go: added github.com/libdns/libdns v0.2.1
go: added github.com/matttproud/golang_protobuf_extensions v1.0.1
go: added github.com/mholt/acmez v1.2.0
go: added github.com/miekg/dns v1.1.55
go: added github.com/onsi/ginkgo/v2 v2.9.5
go: added github.com/prometheus/client_golang v1.14.0
go: added github.com/prometheus/client_model v0.3.0
go: added github.com/prometheus/common v0.37.0
go: added github.com/prometheus/procfs v0.8.0
go: added github.com/quic-go/qpack v0.4.0
go: added github.com/quic-go/qtls-go1-20 v0.3.1
go: added github.com/quic-go/quic-go v0.37.5
go: added github.com/zeebo/blake3 v0.2.3
go: added go.uber.org/multierr v1.11.0
go: added go.uber.org/zap v1.25.0
go: added golang.org/x/crypto v0.12.0
go: added golang.org/x/exp v0.0.0-20230310171629-522b1b587ee0
go: added golang.org/x/mod v0.11.0
go: added golang.org/x/net v0.14.0
go: added golang.org/x/sys v0.11.0
go: added golang.org/x/term v0.11.0
go: added golang.org/x/text v0.12.0
go: added golang.org/x/tools v0.10.0
go: added google.golang.org/protobuf v1.31.0

2023/08/22 18:30:30 [INFO] exec (timeout=0s): /usr/local/go/bin/go get -d -v github.com/muety/caddy-remote-host<EMAIL_ADDRESS>
go: downloading github.com/muety/caddy-remote-host v0.0.0-20211013090634-b21775afa730

go: downloading github.com/patrickmn/go-cache v2.1.0+incompatible

go: downloading github.com/google/cel-go v0.15.1

go: downloading github.com/spf13/cobra v1.7.0

go: downloading google.golang.org/genproto/googleapis/api v0.0.0-20230706204954-ccb25ca9f130

go: downloading github.com/aryann/difflib v0.0.0-20210328193216-ff5ff6dc229b

go: downloading github.com/spf13/pflag v1.0.5

go: downloading github.com/smallstep/certificates v0.24.3-rc.5

go: downloading google.golang.org/genproto v0.0.0-20230706204954-ccb25ca9f130

go: downloading github.com/tailscale/tscert v0.0.0-20230509043813-4e9cb4f2b4ad

go: downloading github.com/antlr/antlr4/runtime/Go/antlr/v4 v4.0.0-20230305170008-8188dc5388df

go: downloading github.com/antlr/antlr4 v0.0.0-20200503195918-621b933c7a7f

go: downloading github.com/stoewer/go-strcase v1.2.0

go: downloading github.com/smallstep/truststore v0.12.1

go: downloading go.step.sm/crypto v0.33.0

go: downloading github.com/inconshreveable/mousetrap v1.1.0

go: downloading github.com/cpuguy83/go-md2man/v2 v2.0.2

go: downloading github.com/cpuguy83/go-md2man v1.0.10

go: downloading gopkg.in/yaml.v3 v3.0.1

go: downloading github.com/pkg/errors v0.9.1

go: downloading github.com/slackhq/nebula v1.6.1

go: downloading go.step.sm/cli-utils v0.8.0

go: downloading go.step.sm/linkedca v0.20.0

go: downloading github.com/smallstep/nosql v0.6.0

go: downloading google.golang.org/grpc v1.56.2

go: downloading gopkg.in/square/go-jose.v2 v2.6.0

go: downloading howett.net/plist v1.0.0

go: downloading github.com/Microsoft/go-winio v0.6.0

go: downloading github.com/mitchellh/go-ps v1.0.0

go: downloading github.com/russross/blackfriday/v2 v2.1.0

go: downloading github.com/Masterminds/sprig/v3 v3.2.3

go: downloading google.golang.org/genproto/googleapis/rpc v0.0.0-20230711160842-782d3b101e98

go: downloading filippo.io/edwards25519 v1.0.0

go: downloading github.com/russross/blackfriday v1.5.2

go: downloading github.com/Masterminds/sprig v2.22.0+incompatible

go: downloading github.com/urfave/cli v1.22.14

go: downloading github.com/micromdm/scep/v2 v2.1.0

go: downloading go.mozilla.org/pkcs7 v0.0.0-20210826202110-33d05740a352

go: downloading github.com/manifoldco/promptui v0.9.0

go: downloading github.com/chzyer/readline v1.5.1

go: downloading github.com/Masterminds/goutils v1.1.1

go: downloading github.com/Masterminds/semver/v3 v3.2.0

go: downloading github.com/huandu/xstrings v1.3.3

go: downloading github.com/imdario/mergo v0.3.12

go: downloading github.com/Masterminds/semver v1.5.0

go: downloading github.com/mitchellh/copystructure v1.2.0

go: downloading github.com/shopspring/decimal v1.2.0

go: downloading github.com/spf13/cast v1.4.1

go: downloading github.com/go-kit/kit v0.10.0

go: downloading github.com/dgraph-io/badger v1.6.2

go: downloading github.com/dgraph-io/badger/v2 v2.2007.4

go: downloading go.etcd.io/bbolt v1.3.7

go: downloading github.com/go-sql-driver/mysql v1.7.0

go: downloading github.com/jackc/pgx/v4 v4.18.0

go: downloading github.com/mitchellh/reflectwalk v1.0.2

go: downloading github.com/go-logfmt/logfmt v0.5.1

go: downloading github.com/dgraph-io/ristretto v0.1.0

go: downloading github.com/dustin/go-humanize v1.0.1

go: downloading github.com/dgryski/go-farm v0.0.0-20200201041132-a6ae2369ad13

go: downloading github.com/mgutz/ansi v0.0.0-20200706080929-d51e80ef957d

go: downloading github.com/AndreasBriese/bbloom v0.0.0-20190825152654-46b345b51c96

go: downloading github.com/jackc/pgconn v1.14.0

go: downloading github.com/jackc/pgio v1.0.0

go: downloading github.com/jackc/pgproto3/v2 v2.3.2

go: downloading github.com/jackc/pgtype v1.14.0

go: downloading github.com/golang/snappy v0.0.4

go: downloading github.com/klauspost/compress v1.16.7

go: downloading github.com/golang/glog v1.1.0

go: downloading github.com/shurcooL/sanitized_anchor_name v1.0.0

go: downloading github.com/mattn/go-colorable v0.1.8

go: downloading github.com/jackc/chunkreader/v2 v2.0.1

go: downloading github.com/jackc/pgpassfile v1.0.0

go: downloading github.com/jackc/pgservicefile v0.0.0-20221227161230-091c0ba34f0a

go: downloading github.com/mattn/go-isatty v0.0.16

go: added github.com/muety/caddy-remote-host v0.0.0-20211013090634-b21775afa730
go: added github.com/patrickmn/go-cache v2.1.0+incompatible

2023/08/22 18:31:09 [INFO] exec (timeout=0s): /usr/local/go/bin/go get -d -v

go: downloading github.com/go-chi/chi v4.1.2+incompatible

go: downloading gopkg.in/natefinch/lumberjack.v2 v2.2.1

go: downloading golang.org/x/sync v0.3.0

go: downloading github.com/mastercactapus/proxyprotocol v0.0.4

go: downloading github.com/BurntSushi/toml v1.3.2

go: downloading github.com/alecthomas/chroma/v2 v2.7.0

go: downloading github.com/yuin/goldmark v1.5.5

go: downloading github.com/yuin/goldmark-highlighting/v2 v2.0.0-20230729083705-37449abec8cc

go: downloading github.com/yuin/goldmark-highlighting v0.0.0-20210516132338-9216f9c5aa01

go: downloading github.com/fxamacker/cbor/v2 v2.4.0

go: downloading github.com/google/go-tpm v0.3.3

go: downloading github.com/smallstep/go-attestation v0.4.4-0.20230509120429-e17291421738

go: downloading github.com/alecthomas/chroma v0.9.2

go: downloading go.opentelemetry.io/contrib/instrumentation/net/http/otelhttp v0.42.0

go: downloading go.opentelemetry.io/contrib/propagators/autoprop v0.42.0
go: downloading go.opentelemetry.io/otel/exporters/otlp/otlptrace/otlptracegrpc v1.16.0

go: downloading go.opentelemetry.io/contrib v0.20.0

go: downloading go.opentelemetry.io/otel/exporters/otlp/otlptrace v1.16.0

go: downloading go.opentelemetry.io/otel v1.16.0

go: downloading go.opentelemetry.io/otel/exporters/otlp v0.20.0

go: downloading go.opentelemetry.io/otel/sdk v1.16.0

go: downloading go.opentelemetry.io/otel/trace v1.16.0

go: downloading github.com/google/go-tspi v0.3.0

go: downloading github.com/rs/xid v1.5.0
go: downloading github.com/x448/float16 v0.8.4

go: downloading github.com/felixge/httpsnoop v1.0.3
go: downloading github.com/sirupsen/logrus v1.9.3

go: downloading go.opentelemetry.io/contrib/propagators/aws v1.17.0

go: downloading go.opentelemetry.io/contrib/propagators/b3 v1.17.0

go: downloading go.opentelemetry.io/contrib/propagators/jaeger v1.17.0

go: downloading go.opentelemetry.io/contrib/propagators/ot v1.17.0

go: downloading go.opentelemetry.io/otel/metric v1.16.0

go: downloading go.opentelemetry.io/otel/exporters/otlp/internal/retry v1.16.0

go: downloading go.opentelemetry.io/proto/otlp v0.19.0

go: downloading github.com/dlclark/regexp2 v1.7.0

go: downloading github.com/google/certificate-transparency-go v1.1.4

go: downloading github.com/go-logr/logr v1.2.4

go: downloading github.com/cenkalti/backoff/v4 v4.2.1

go: downloading github.com/go-logr/stdr v1.2.2

go: downloading github.com/cenkalti/backoff v2.2.1+incompatible

go: downloading github.com/grpc-ecosystem/grpc-gateway/v2 v2.7.0

go: downloading github.com/grpc-ecosystem/grpc-gateway v1.16.0

2023/08/22 18:31:19 [INFO] Build environment ready

2023/08/22 18:31:19 [INFO] Building Caddy
2023/08/22 18:31:19 [INFO] exec (timeout=0s): /usr/local/go/bin/go mod tidy -e

go: downloading github.com/stretchr/testify v1.8.4
go: downloading go.uber.org/goleak v1.2.1

go: downloading github.com/onsi/gomega v1.27.6

go: downloading github.com/davecgh/go-spew v1.1.1

go: downloading github.com/benbjohnson/clock v1.3.0

go: downloading gopkg.in/check.v1 v1.0.0-20200227125254-8fa46927fb4f

go: downloading github.com/zeebo/assert v1.1.0

go: downloading github.com/smallstep/assert v0.0.0-20200723003110-82e2b9b3b262

go: downloading github.com/google/go-cmp v0.5.9

go: downloading github.com/pmezard/go-difflib v1.0.0

go: downloading github.com/alecthomas/assert/v2 v2.2.1

go: downloading github.com/google/go-tpm-tools v0.3.12

go: downloading github.com/peterbourgon/diskv/v3 v3.0.1

go: downloading github.com/schollz/jsonstore v1.1.0

go: downloading github.com/alecthomas/assert v0.0.0-20170929043011-405dbfeb8e38

go: downloading gopkg.in/yaml.v2 v2.4.0

go: downloading github.com/alecthomas/repr v0.2.0

go: downloading github.com/chzyer/test v1.0.0

go: downloading github.com/aws/aws-sdk-go v1.44.307

go: downloading cloud.google.com/go/kms v1.15.0

go: downloading github.com/googleapis/gax-go/v2 v2.12.0

go: downloading google.golang.org/api v0.132.0

go: downloading github.com/googleapis/gax-go v2.0.2+incompatible

go: downloading cloud.google.com/go v0.110.4

go: downloading github.com/niemeyer/pretty v0.0.0-20200227124842-a10e7caefd8e

go: downloading github.com/google/btree v1.1.2

go: downloading github.com/cockroachdb/apd v1.1.0

go: downloading github.com/gofrs/uuid v4.0.0+incompatible

go: downloading github.com/zeebo/pcg v1.0.1

go: downloading github.com/hexops/gotextdiff v1.0.3

go: downloading github.com/go-stack/stack v1.8.0

go: downloading github.com/chzyer/logex v1.2.1

go: downloading cloud.google.com/go/iam v1.1.0

go: downloading github.com/kr/text v0.2.0

go: downloading github.com/jackc/pgmock v0.0.0-20210724152146-4ad1a8207f65

go: downloading github.com/lib/pq v1.10.2

go: downloading github.com/jmespath/go-jmespath v0.4.0

go: downloading golang.org/x/oauth2 v0.10.0

go: downloading cloud.google.com/go/compute/metadata v0.2.3

go: downloading go.opencensus.io v0.24.0

go: downloading cloud.google.com/go/compute v1.20.1

go: downloading google.golang.org/appengine v1.6.7

go: downloading github.com/OneOfOne/xxhash v1.2.2

go: downloading github.com/spaolacci/murmur3 v1.1.0

go: downloading github.com/google/s2a-go v0.1.4

go: downloading github.com/googleapis/enterprise-certificate-proxy v0.2.5

go: downloading github.com/golang/groupcache v0.0.0-20210331224755-41bb18bfe9da

2023/08/22 18:31:29 [INFO] exec (timeout=0s): /usr/local/go/bin/go build -o /usr/bin/caddy -ldflags -w -s -trimpath

github.com/miekg/dns: /usr/local/go/pkg/tool/linux_amd64/compile: signal: killed

github.com/google/cel-go/parser/gen: /usr/local/go/pkg/tool/linux_amd64/compile: signal: killed

github.com/yuin/goldmark/util: /usr/local/go/pkg/tool/linux_amd64/compile: signal: killed

2023/08/22 18:32:01 [INFO] Skipping cleanup as requested; leaving folder intact: /tmp/buildenv_2023-08-22-1830.1583521926

2023/08/22 18:32:01 [FATAL] exit status 1

The command '/bin/sh -c xcaddy build --with github.com/muety/caddy-remote-host' returned a non-zero code: 1

That's weird, because works on my machine :thinking:. What Go version are you using and what system did you try the build on? Potentially in CI runner or something similar? To me, the error sounds like the build process gets killed due to some timeout, rather than anything "code"-related. Can you build with other plugins than caddy-remote-host?

I am an imbecile. Apparently my build box was low on disk space. Sorry to waste your time.


Allow comments prefixed by "//" in settings.json and bindings.json

Both Sublime Text and VS Code allow comments prefixed by "//" in their settings config files and it's quite convinient.

Can't speak on the author's behalf of course but while convenient, comments aren't included in the JSON spec. You can find a diagram of json syntax here if you're curious: http://www.json.org/

Yes, i know it, but this config json-file is not for interchanging data between different apps. Furthermore SublimeText/VSCode experience proves that it's OK.
Of course, i think that ini/toml is more suitable for config files but i accept authors decision.

We could do this by using json5. There is a nice library for go here which seems to work and is very easy to implement in micro. Let me know what you think.

Yes, json5 is much better (i didn't know about that lib). It has comments and unquoted keys.

And it allows trailing commas ;)

Alright, micro now uses json5.


OSX setup and installation

I have gone through the fbcunn install instructions and have made it to the "Install Folly, fbthrift, thpp and fblualib"  Part(I have Torch th and iTorch working with Cuda).  I am unable to use the curl command on OS X, so I am trying to install folly by itself.  In order to do this I need to instal google-glob.  I am getting the following error when I "make" goggle-glog.
"n file included from ./src/glog/stl_logging.h:54:
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/../include/c++/v1/ext/hash_set:205:5: warning:
Use of the header <ext/hash_set> is deprecated. Migrate to <unordered_set>
[-W#warnings]
warning Use of the header <ext/hash_set> is deprecated.  Migrate to ...
^

In file included from src/stl_logging_unittest.cc:53:
In file included from ./src/glog/stl_logging.h:55:
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/../include/c++/v1/ext/hash_map:212:5: warning:
Use of the header <ext/hash_map> is deprecated. Migrate to <unordered_map>
[-W#warnings]
warning Use of the header <ext/hash_map> is deprecated.  Migrate to ...
^

In file included from src/stl_logging_unittest.cc:53:
./src/glog/stl_logging.h:56:11: fatal error: 'ext/slist' file not found
include <ext/slist>
      ^

2 warnings and 1 error generated.
make: *** [stl_logging_unittest-stl_logging_unittest.o] Error 1"
Anyone know how I can fix this?  I have asked on the blog forum, but no response thus far.  Are there more complete and detailed instructions for installing fbcunn on OS X?  The instructions seem to be more geared towards Ubuntu.
I am using OS X Yosemite 10.10.2

I ran this command in folly:  ./bootstrap-osx-homebrew.sh
and it says: "Warning: glog-0.3.3 already installed"
but at the end it says:  "configure: error: Please install google-glog library"
Any guidance?

Do the workarounds in http://stackoverflow.com/questions/19758400/ext-slist-file-not-found-on-os-x-10-9 work?
./src/glog/stl_logging.h:56:11: fatal error: 'ext/slist' file not found

doesn't sound good.

I ran the make command from the Terminal, where would I make the changes suggested in the stack overflow post?

Whoops, it's OS X - that's not supported (sorry, I didn't notice originally).  See
https://github.com/facebook/fbcunn/blob/master/INSTALL.md
Find a machine with Ubuntu 14.04+ and an NVIDIA GPU with compute capability 3.5 or above

I saw that.. I thought maybe OS X was forgotten to be posted on there.  I have everything else working to that point.  Using Torch, nn, th, iTorch.  Will fbcunn ever be supported on OS X?

What do you want to do with fbcunn on OS X? Most of it is CUDA kernels and Torch modules, for which OS X isn't a great operating system (do you have a GPU in your OS X machine?)

Yes, 2 of them.
On Feb 2, 2015 6:17 PM, "Andrew Tulloch"<EMAIL_ADDRESS>wrote:

What do you want to do with fbcunn on OS X? Most of it is CUDA kernels and
Torch modules, for which OS X isn't a great operating system (do you have a
GPU in your OS X machine?)
—
Reply to this email directly or view it on GitHub
https://github.com/facebook/fbcunn/issues/19#issuecomment-72573904.

Oops... Just one:   Chipset Model: NVIDIA GeForce GT 640M
Type: GPU
Bus: PCIe
PCIe Lane Width: x16
VRAM (Total): 512 MB
Vendor: NVIDIA (0x10de)
Device ID: 0x0fd8
Revision ID: 0x00a2
ROM Revision: 3707
I'm really not sure what i am going to do with it yet.  I am new to nn's
an, Deep Learning and AI all together, but I really want to learn it.
Unfortunately my Windows laptop has no GPU and I am working on building a
PC to run VM's where I can install Ubuntu, but I don't have the funds saved
yet, so when I saw that Facebook open sources their Deep Learning code, I
was excited to dig in and learn.  I honestly have no idea what it does yet,
I was messing with iTorch and luarockt, but I'm still a bit in the dark.
On Mon, Feb 2, 2015 at 6:18 PM, Antonio Piazza<EMAIL_ADDRESS>wrote:

Yes, 2 of them.
On Feb 2, 2015 6:17 PM, "Andrew Tulloch"<EMAIL_ADDRESS>wrote:

What do you want to do with fbcunn on OS X? Most of it is CUDA kernels
and Torch modules, for which OS X isn't a great operating system (do you
have a GPU in your OS X machine?)
—
Reply to this email directly or view it on GitHub
https://github.com/facebook/fbcunn/issues/19#issuecomment-72573904.

Cool - I would suggest either:

Dual booting OS X/Ubuntu and using Ubuntu with torch,
Learning torch and deep learning with CPU code (there's plenty of interesting stuff to do there, it's mostly computer vision and larger models that benefit from GPUs)
Using an Amazon AWS GPU instance (http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/using_cluster_computing.html, ~50c/hr)

Thanks!

@antman1p with a 640M GPU, your multi-core CPU will be faster than the GPU

Ok, thank you both. I'll just mess with torch until I get my system built.
On Feb 2, 2015 6:46 PM, "Soumith Chintala"<EMAIL_ADDRESS>wrote:

@antman1p https://github.com/antman1p with a 640M GPU, your multi-core
CPU will be faster than the GPU
—
Reply to this email directly or view it on GitHub
https://github.com/facebook/fbcunn/issues/19#issuecomment-72576810.

Question:  Is there anything preventing fbcunn from running on Mac OS X other than the lack of numa?

@elbamos I never tried doing it. @tudor says folly might or might not work in OSX. So, short answer, we dont know.

Well folly is now installable from homebrew.  Where I get into trouble on the install is just numa, which prevents fbthrift, which then prevents everything that follows.

Well folly is now installable from homebrew.

Woah! you just blew my mind there. Didn't know this piece of info. Only if there was something similar for Ubuntu as well.


Add TileDB vectorstore implementation

Description: Add TileDB vectorstore implementation. TileDB offers ANN search capabilities using the TileDB-Vector-Search module. It provides serverless execution of ANN queries and storage of vector indexes both on local disk and cloud object stores (i.e. AWS S3). More details in:

Why TileDB as a Vector Database
TileDB 101: Vector Search

Twitter handle: @tiledb

Thanks for the quick review @baskaryan! Let me know if you need any more changes


Adapter crashes

EDIT: With APIv1 it works, switching to v2 as explained in the adapter the following happens (No sure if your "use API v1" is still valid)

I got a new go-e Gemini 11kW Hardware Version V4
When I start the adapter it crashes.
Debug says:
`

go-e.0
2023-05-25 18:33:43.381
warn
Terminated (UNCAUGHT_EXCEPTION): Without reason

go-e.0
2023-05-25 18:33:43.380
info
terminating

go-e.0
2023-05-25 18:33:43.360
error
this.translationObjectV2.keys is not a function

go-e.0
2023-05-25 18:33:43.360
error
TypeError: this.translationObjectV2.keys is not a function at GoE.getStateFromDevice (/opt/iobroker/node_modules/iobroker.go-e/main.js:331:76) at GoE.onReady (/opt/iobroker/node_modules/iobroker.go-e/main.js:126:20) at GoE.emit (node:events:513:28) at GoE.emit (node:domain:489:12) at /opt/iobroker/node_modules/@iobroker/js-controller-adapter/build/lib/adapter/adapter.js:8232:26

go-e.0
2023-05-25 18:33:43.358
error
unhandled promise rejection: this.translationObjectV2.keys is not a function

go-e.0
2023-05-25 18:33:43.358
error
Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().

go-e.0
2023-05-25 18:33:43.356
debug
Subscribe foreign object 0_userdata.0.PV_Produktion

go-e.0
2023-05-25 18:33:43.355
debug
Subscribe foreign object 0_userdata.0.PV_Eigenverbrauch

go-e.0
2023-05-25 18:33:43.347
warn
Sentry enabled. You can switch it off in settings of the adapter.

go-e.0
2023-05-25 18:33:43.346
info
Intervall: 60

go-e.0
2023-05-25 18:33:43.346
info
Server: go-eCharger.fritz.box

go-e.0
2023-05-25 18:33:43.345
info
Update selectable values from ["alw","car","amp"] to alw,rbc,rbt,car,amp

go-e.0
2023-05-25 18:33:43.325
info
starting. Version 1.0.27 in /opt/iobroker/node_modules/iobroker.go-e, node: v18.15.0, js-controller: 4.0.24

`
1.0.27 in /opt/iobroker/node_modules/iobroker.go-e, node: v18.15.0, js-controller: 4.0.24
Versions:

Adapter version: 1.0.27
JS-Controller version: 4.0.24
Node version: v.18.15.0
Operating system: debian

Thank you for your info.
Please use API V1 only. V2 is not ready yet on all environments


[WIP] Fixed #25605 -- Made GeoDjango DB functions work with expressions.

https://code.djangoproject.com/ticket/25605

Could you please rebase this one?

I'm still working on it, probably will push update tomorrow.

I worked a bit on this issue this morning and here's the result: claudep@69e2fb85b9c2d74c0cadc38aad2bfe4b9ccf8cda
It's not yet thoroughly tested (as yours) but what do you think about the approach taken?

Well, I'm still sure that we should remove handling of string that differs from Func, because WKT parameters could mask fields (this example was done on your branch):
In [33]: qs = Test.objects.annotate(**{'SRID=4326;POINT (10 10)': Centroid('point')})

In [34]: qs.values().first()
Out[34]:
{'SRID=4326;POINT (10 10)': <Point object at 0x7f094f0827f0>,
 u'id': 1,
 'name': u'name',
 'point': <Point object at 0x7f094f082880>}

In [35]: qs = qs.annotate(union=Union('SRID=4326;POINT (10 10)', 'point'))

In [36]: {k: str(v) for k, v in qs.values().first().items()}
Out[36]:
{'SRID=4326;POINT (10 10)': 'SRID=4326;POINT (0.0000000000000000 0.0000000000000000)',
 u'id': '1',
 'name': 'name',
 'point': 'SRID=4326;POINT (0.0000000000000000 0.0000000000000000)',
 'union': 'SRID=4326;MULTIPOINT (10.0000000000000000 10.0000000000000000, 0.0000000000000000 0.0000000000000000)'}

Though this example is speculative (but still valid), there is no guarantee that GEOSGeometry will not support some formats more similar to common field names.

Makes sense. Still undecided about adding deprecation or not for this removal...

I think we should just remove it from 1.9 while it's not released.

I mean only new GIS functions, not old GeoManager methods.

Tested that in #5583. If tests are happy and you approve it, I'll commit and backport.

WIP patch updated in claudep@304d700057

The title of the PR stills contains WIP, is it really still WIP?

Yes, this is still WIP, I think we should make decision on this at first.

OK, I'll push that one on my review list first.

Closing due to inactivity.


Ability to enable/disable users temporarily

We should add two endpoints accessible by the admin:
r.With(api.requireAdminCredentials).Post("/disable", api.DisableUser)
r.With(api.requireAdminCredentials).Post("/enable", api.EnableUser)
we would need an is_disabled column on the users table which is checked before a token is requested, and returns an error "this user has been disabled by the admin" if is true

@awalias what to do in situations when user already got token and after that admin blocked him? do we need handle this case or it's OK and lets wait while his token expire?

I don't think it's possible for us to force expire an access token? I think we just have to wait for it to expire 🤷♂

@awalias maybe better make route like /admin/users/{user_id}/disable and /admin/users/{user_id}/enable and switch method from POST to PATCH? In my opinion, it seems to be more better choice. What do you think?

@awalias maybe better make route like /admin/users/{user_id}/disable and /admin/users/{user_id}/enable and switch method from POST to PATCH? In my opinion, it seems to be more better choice. What do you think?

I wonder whether we should extend the existing POST /user endpoint with enable/disable functionality:

and make a new route for UserUpdate that is only accessible by Admin Users
what do you think? It will enable admins to change other data about a user (and can add more in the future)

but I also like your solution 🤔

Your approach is more scalable in future than mine. OK, I'll implement admin's analog of UserUpdate method=)

I don't think it's possible for us to force expire an access token? I think we just have to wait for it to expire 🤷♂

This is not necessarily true, and largely depends on how you verify the validity of tokens. Aside from checking the signature, and indeed even before checking the signature, you might want to check the sub (or other relevant claim) against a blacklist to see if the token should be disallowed.
The tricky bit is of course how you make sure your blacklist is accurate and up to date. It may not be palatable to look it up in the DB on every request, but on the other hand if you don't look it up on every request, there's a good chance you'll have a race condition where a request comes in and makes it all the way before the blacklist is propagated to wherever tokens are checked. To be fair though, depending on where in the flow you're checking the validity of a token you may well end up with a race condition anyway.
The way I've done this in the past is to have a mechanism for blacklisting tokens based on one or a combination of claims, e.g. for individual users it may be the sub claim, for groups of users it may be something else, a custom claim like grp or even individual role permissions like role. Maybe it's a combination of things, maybe a user should have general access, but lost admin privileges so any token with sub=1234 and role='admin' should be rejected. This blacklist lives at the API gateway, and that's the source of truth. Anything that gets passed the gateway is assumed to be valid (though signatures may still be checked, just not blacklist rules,) and anything behind the gateway only accepts requests coming from the gateway. Any request coming from another source is dropped without further consideration.
It's a decent compromise which allows for blocking tokens even if their expiration time is quite far in to the future. Blacklist rules generally don't expire, so care has to be taken to make it performant, and that of course largely depends on how complicated the rules can get. If all you're doing is field comparison it's a pretty fast lookup, but if you start doing fancy stuff like regex checks or multiple field comparisons you have to be real careful to make sure the expensive checks happen as late as possible, and the cheap checks act as circuit breakers first.


non-mandatory-script-verify-flag (Signature must be zero for failed CHECK(MULTI)SIG operation)

non-mandatory-script-verify-flag (Signature must be zero for failed CHECK(MULTI)SIG operation)

Please provide the demo and data, we will look at the specific reasons.


Resolving the issue of inside_vm_job depending on action-id generated by action-up in gitea-actions-runner

Thank you to @ChristopherHX for the dedication to developing gitea-actions-runner, which provides a great solution for integrating github-runner into Gitea. However, during usage, I encountered some issues.
Specifically, I noticed a scenario in veertuinc's anka-actions-up (https://github.com/veertuinc/anka-actions-up), where inside_vm_job's runs-on depends on a self-hosted runner, and the identification of this runner is determined by the action-id generated by the action-up job. This mechanism works fine when using github + https://github.com/actions/runner.

However, when using gitea + gitea-actions-runner + https://github.com/actions/runner, it seems to encounter problems.
Specifically, I found that inside_vm_job remains waiting even though the action-up step successfully registers the runner with gitea. I suspect that inside_vm_job's runs-on cannot retrieve the action-id generated by action-up.

Below is the YAML code snippet:
jobs:

  action-up:
    runs-on: ubuntu-latest
    steps:
      - uses: veertuinc/anka-actions-up@v1
        id: action-up
        with:
          gh-pat: ${{ secrets.SERVICE_USER_PAT }}
          template-id: '9690461a-02b5-412d-8778-dab4167743db'
          controller-url: 'https://controller.mysite.com'
    outputs:
      action-id: ${{ steps.action-up.outputs.action-id }}

  inside_vm_job:
    needs: action-up
    runs-on: [ self-hosted, "${{ needs.action-up.outputs.action-id }}" ]
    steps:
      - name: Inside VM Job
        id: inside_vm_job
        run: |
          echo "running on runner inside of VM (${{ needs.action-up.outputs.action-id }})"
          echo "user: $USER"
          echo "home: $HOME"

  action_down:
    if: always()
    needs: [ action-up, inside_vm_job ]
    runs-on: ubuntu-latest
    steps:
      - uses: veertuinc/anka-actions-down@v1
        with:
          action-id: ${{ needs.action-up.outputs.action-id }}
          gh-pat: ${{ secrets.SERVICE_USER_PAT }}
          controller-url: 'https://controller.mysite.com'

Therefore, I kindly invite @ChristopherHX, the author, to improve gitea-actions-runner to address this issue. Thank you!

I don't think veertuinc/anka-actions-up works with gitea in any way. You provide GitHub Credentials to it and it registeres the runner to Github.com not gitea. (see ghes note in readme)
Typically orchestration tools for github.com/GHES doesn't work together with this wrapper.

they depend (those are not emulated)

on webhooks
on github rest api
actions/runner registration (a different project from me also emulates this, but then it's no longer Gitea Actions managing the workflows)

this tool (emulates the following)

wraps the undocumented lowlevel protocol of actions/runner
directly executes an unregistred actions/runner (only creating a dummy .runner file)

It would be a big challenge to make generic orchestration tools for Actions work on Gitea.
Additionally Gitea Actions would need to support job outputs like needs.action-up.outputs.action-id.
I believe it evaluated to an empty string and would even be broken if the action would be register a runner to gitea.
See https://gitea.com/gitea/act/src/commit/15045b4fc0f33dfc6ab27b6398195d2c2e3f26ce/pkg/jobparser/jobparser.go#L34, https://docs.gitea.com/usage/actions/comparison#complex-runs-on

I removed the logic of github runner credentials and it can run normally. At present, it is the action-id problem caused by the run-on of inside_vm_job depending on action-up.

I removed the logic of github runner credentials and it can run normally https://github.com/veertuinc/anka-actions-up/blob/main/src/action.ts#L102-L114. At present, it is the action-id problem caused by the run-on of inside_vm_job depending on action-up.

So you are able to see the runner with label self-hosted,<action-id> in Gitea Settings?
I wonder what you did to get that far.

Because inside_vm_job keeps spinning. So the instance is not destroyed.

1-2

Since the previous action_down was not executed, gitea's runner also contains the vm instance created by the previous action-up. If I try the following configuration, it works perfectly.
name: Build

on:
  - push
  - pull_request

jobs:
  action-up:
    runs-on: ubuntu-latest
    steps:
      - uses: oilrich25/anka-actions-up@main
        id: action-up
        with:
          gh-pat: 'xxxx'
          gh-base-url: 'http://<IP_ADDRESS>:3000/api/v3'
          template-id: '0c91eb16-80fb-43b6-808f-a32ad0f04e93'
          controller-url: 'https://anka.controller:8090'
          template-runner-dir: '/Users/runner/gitea-actions-runner'
          controller-root-token: ${{ secrets.ROOT_TOKEN }}
          controller-https-skip-cert-verify: 'true'
    outputs:
      action-id: ${{ steps.action-up.outputs.action-id }}

  inside_vm_job:
    needs: action-up
    runs-on: [self-hosted, da72bf4d-e7d1-470e-b357-4a89c6e100b3 ]
    # runs-on:
    steps:
      - name: Inside VM Job
        id: inside_vm_job
        run: |
          echo "running on runner inside of VM (${{ needs.action-up.outputs.action-id }})"
          echo "user: $USER"
          echo "home: $HOME"

  action_down:
    if: always()
    needs: [ action-up, inside_vm_job ]
    runs-on: ubuntu-latest
    steps:
      - uses: oilrich25/anka-actions-down@main
        with:
          action-id: ${{ needs.action-up.outputs.action-id }}
          gh-pat: 'xxxx'
          controller-url: 'https://anka.controller:8090'
          controller-root-token: ${{ secrets.ROOT_TOKEN }}

I would create a feature/enhancement request/proposal for job outputs in runs-on https://github.com/go-gitea/gitea/issues.
This change needs to be done inside the Gitea Server.

OK, thanks


Polish UI of sign up page.

Description
As a user, I would like to see a chatbot centered UI
Scope of Work

[ ] Create a high fidelity mock-up
[ ] Remove intro
[ ] Remove Landing
[ ] Chat interface (in full screen)

Demo requirement

The user should be able to access and sign up page and start chatting immediately.
The UI should be fully chat centered

Acceptance Criteria

The user should be able to access and sign up page and start chatting immediately.
The UI should be fully chat centered

Added the current transcript + proposed modifications to #232


Unable to load pretrained checkpoints for yolov_x and yolov_l

Dear Author,
Thanks for sharing your great work. I'm trying to train yolov_l and yolov_x, but it looks like it's unable to load the checkpoints for yoloxl_vid.pth and yoloxx_vid.pth provided in google drive.
Here's my training command
python tools/vid_train.py -f exps/yolov/yolov_l.py -c pretrained_weights/yoloxl_vid.pth --fp16
python tools/vid_train.py -f exps/yolov/yolov_x.py -c pretrained_weights/yoloxx_vid.pth --fp16
And I'm getting this error

My command below for training yolov_s is working fine. Is it possible that the large and extra large checkpoints got corrupted?
python tools/vid_train.py -f exps/yolov/yolov_s.py -c pretrained_weights/yoloxs_vid.pth --fp16
Thanks for the help!

Dear Author,
Thanks for sharing your great work. I'm trying to train yolov_l and yolov_x, but it looks like it's unable to load the checkpoints for yoloxl_vid.pth and yoloxx_vid.pth provided in google drive.
Here's my training command python tools/vid_train.py -f exps/yolov/yolov_l.py -c pretrained_weights/yoloxl_vid.pth --fp16 python tools/vid_train.py -f exps/yolov/yolov_x.py -c pretrained_weights/yoloxx_vid.pth --fp16
And I'm getting this error

My command below for training yolov_s is working fine. Is it possible that the large and extra large checkpoints got corrupted? python tools/vid_train.py -f exps/yolov/yolov_s.py -c pretrained_weights/yoloxs_vid.pth --fp16
Thanks for the help!

Hello, thanks for your interest in our work. We find the same error with the two pretrain-weights and we have updated it, please try it again.

It works for me now as well, thank you!


Indent with 4 spaces

The rest of the project is indented with 4 spaces.

NetflixOSS » servo » servo-pull-requests #38 SUCCESS
This pull request looks good