Panic loading store view

Thanos, Prometheus and Golang version used:
Thanos v0.23.1 docker image

Object Storage Provider:
GCS
What happened:
Panic when trying to load /stores. Web UI shows

Returning a 503 from /api/v1/stores
What you expected to happen:
Returns list of stores and their status
How to reproduce it (as minimally and precisely as possible):
I have a lot of store nodes (16) some of which aren't currently available (they come in and out of availability) I suspect this might have something to do with the issue but have attached the logs below as well.
Full logs to relevant components:
Logs

```
	/home/circleci/project/pkg/extprom/http/instrument_server.go:108 +0x10f
net/http.HandlerFunc.ServeHTTP(0xc0003eba10, 0x7f291c49c050, 0xc000a3d1d0, 0xc000db4a00)
	/usr/local/go/src/net/http/server.go:2049 +0x44
github.com/prometheus/client_golang/prometheus/promhttp.InstrumentHandlerResponseSize.func1(0x7f291c49c050, 0xc000a3d180, 0xc000db4a00)
	/home/circleci/go/pkg/mod/github.com/prometheus/client_golang@v1.11.0/prometheus/promhttp/instrument_server.go:198 +0xee
net/http.HandlerFunc.ServeHTTP(0xc0003ebd10, 0x7f291c49c050, 0xc000a3d180, 0xc000db4a00)
	/usr/local/go/src/net/http/server.go:2049 +0x44
github.com/prometheus/client_golang/prometheus/promhttp.InstrumentHandlerCounter.func1(0x7f291c49c050, 0xc000a3d130, 0xc000db4a00)
	/home/circleci/go/pkg/mod/github.com/prometheus/client_golang@v1.11.0/prometheus/promhttp/instrument_server.go:101 +0xdf
net/http.HandlerFunc.ServeHTTP(0xc0003ebf80, 0x7f291c49c050, 0xc000a3d130, 0xc000db4a00)
	/usr/local/go/src/net/http/server.go:2049 +0x44
github.com/prometheus/client_golang/prometheus/promhttp.InstrumentHandlerRequestSize.func1(0x214e980, 0xc0008fa8c0, 0xc000db4a00)
	/home/circleci/go/pkg/mod/github.com/prometheus/client_golang@v1.11.0/prometheus/promhttp/instrument_server.go:165 +0xee
net/http.HandlerFunc.ServeHTTP(0xc00048c2a0, 0x214e980, 0xc0008fa8c0, 0xc000db4a00)
	/usr/local/go/src/net/http/server.go:2049 +0x44
github.com/thanos-io/thanos/pkg/tracing.HTTPMiddleware.func1(0x214e980, 0xc0008fa8c0, 0xc000db4900)
	/home/circleci/project/pkg/tracing/http.go:46 +0x54c
github.com/prometheus/common/route.(*Router).handle.func1(0x214e980, 0xc0008fa8c0, 0xc000db4800, 0x0, 0x0, 0x0)
	/home/circleci/go/pkg/mod/github.com/prometheus/common@v0.30.0/route/route.go:83 +0x27f
github.com/julienschmidt/httprouter.(*Router).ServeHTTP(0xc00098de60, 0x214e980, 0xc0008fa8c0, 0xc000db4800)
	/home/circleci/go/pkg/mod/github.com/julienschmidt/httprouter@v1.3.0/router.go:387 +0xc7e
github.com/prometheus/common/route.(*Router).ServeHTTP(0xc000214b20, 0x214e980, 0xc0008fa8c0, 0xc000db4800)
	/home/circleci/go/pkg/mod/github.com/prometheus/common@v0.30.0/route/route.go:121 +0x4c
net/http.(*ServeMux).ServeHTTP(0xc0005fadc0, 0x214e980, 0xc0008fa8c0, 0xc000db4800)
	/usr/local/go/src/net/http/server.go:2428 +0x1ad
net/http.serverHandler.ServeHTTP(0xc00046c540, 0x214e980, 0xc0008fa8c0, 0xc000db4800)
	/usr/local/go/src/net/http/server.go:2867 +0xa3
net/http.(*conn).serve(0xc00043e500, 0x2155d90, 0xc00087ff80)
	/usr/local/go/src/net/http/server.go:1932 +0x8cd
created by net/http.(*Server).Serve
	/usr/local/go/src/net/http/server.go:2993 +0x39b
level=warn ts=2021-11-30T02:10:54.095595359Z caller=endpointset.go:512 component=endpointset msg="update of node failed" err="getting metadata: fallback fetching info from <IP_ADDRESS>:10000 after err: rpc error: code = DeadlineExceeded desc = context deadline exceeded: rpc error: code = DeadlineExceeded desc = context deadline exceeded" address=<IP_ADDRESS>:10000
level=warn ts=2021-11-30T02:10:54.096047117Z caller=endpointset.go:512 component=endpointset msg="update of node failed" err="getting metadata: fallback fetching info from <IP_ADDRESS>:10006 after err: rpc error: code = DeadlineExceeded desc = context deadline exceeded: rpc error: code = DeadlineExceeded desc = context deadline exceeded" address=<IP_ADDRESS>:10006
level=warn ts=2021-11-30T02:10:54.097687309Z caller=endpointset.go:512 component=endpointset msg="update of node failed" err="getting metadata: fallback fetching info from <IP_ADDRESS>:10007 after err: rpc error: code = DeadlineExceeded desc = context deadline exceeded: rpc error: code = DeadlineExceeded desc = context deadline exceeded" address=<IP_ADDRESS>:10007
level=warn ts=2021-11-30T02:10:54.098111126Z caller=endpointset.go:512 component=endpointset msg="update of node failed" err="getting metadata: fallback fetching info from <IP_ADDRESS>:10003 after err: rpc error: code = DeadlineExceeded desc = context deadline exceeded: rpc error: code = DeadlineExceeded desc = context deadline exceeded" address=<IP_ADDRESS>:10003
level=warn ts=2021-11-30T02:10:54.098163667Z caller=endpointset.go:512 component=endpointset msg="update of node failed" err="getting metadata: fallback fetching info from <IP_ADDRESS>:10005 after err: rpc error: code = DeadlineExceeded desc = context deadline exceeded: rpc error: code = DeadlineExceeded desc = context deadline exceeded" address=<IP_ADDRESS>:10005
level=warn ts=2021-11-30T02:10:54.098497601Z caller=endpointset.go:512 component=endpointset msg="update of node failed" err="getting metadata: fallback fetching info from <IP_ADDRESS>:10002 after err: rpc error: code = DeadlineExceeded desc = context deadline exceeded: rpc error: code = DeadlineExceeded desc = context deadline exceeded" address=<IP_ADDRESS>:10002
level=warn ts=2021-11-30T02:10:54.098524609Z caller=endpointset.go:512 component=endpointset msg="update of node failed" err="getting metadata: fallback fetching info from <IP_ADDRESS>:10001 after err: rpc error: code = DeadlineExceeded desc = context deadline exceeded: rpc error: code = DeadlineExceeded desc = context deadline exceeded" address=<IP_ADDRESS>:10001
level=warn ts=2021-11-30T02:10:54.098719277Z caller=endpointset.go:512 component=endpointset msg="update of node failed" err="getting metadata: fallback fetching info from <IP_ADDRESS>:10004 after err: rpc error: code = DeadlineExceeded desc = context deadline exceeded: rpc error: code = DeadlineExceeded desc = context deadline exceeded" address=<IP_ADDRESS>:10004
level=warn ts=2021-11-30T02:10:54.305491706Z caller=endpointset.go:512 component=endpointset msg="update of node failed" err="getting metadata: fallback fetching info from <IP_ADDRESS>:10010 after err: rpc error: code = Unavailable desc = Service Unavailable: HTTP status code 503; transport: received the unexpected content-type \"text/html\": rpc error: code = Unavailable desc = Service Unavailable: HTTP status code 503; transport: received the unexpected content-type \"text/html\"" address=<IP_ADDRESS>:10010
level=warn ts=2021-11-30T02:10:59.099762426Z caller=endpointset.go:512 component=endpointset msg="update of node failed" err="getting metadata: fallback fetching info from <IP_ADDRESS>:10000 after err: rpc error: code = Unavailable desc = upstream connect error or disconnect/reset before headers. reset reason: connection failure: rpc error: code = DeadlineExceeded desc = context deadline exceeded" address=<IP_ADDRESS>:10000
level=warn ts=2021-11-30T02:10:59.099812437Z caller=endpointset.go:512 component=endpointset msg="update of node failed" err="getting metadata: fallback fetching info from <IP_ADDRESS>:10006 after err: rpc error: code = DeadlineExceeded desc = context deadline exceeded: rpc error: code = DeadlineExceeded desc = context deadline exceeded" address=<IP_ADDRESS>:10006
level=warn ts=2021-11-30T02:10:59.099842639Z caller=endpointset.go:512 component=endpointset msg="update of node failed" err="getting metadata: fallback fetching info from <IP_ADDRESS>:10001 after err: rpc error: code = Unavailable desc = upstream connect error or disconnect/reset before headers. reset reason: connection failure: rpc error: code = DeadlineExceeded desc = context deadline exceeded" address=<IP_ADDRESS>:10001
level=warn ts=2021-11-30T02:10:59.099923937Z caller=endpointset.go:512 component=endpointset msg="update of node failed" err="getting metadata: fallback fetching info from <IP_ADDRESS>:10005 after err: rpc error: code = DeadlineExceeded desc = context deadline exceeded: rpc error: code = DeadlineExceeded desc = context deadline exceeded" address=<IP_ADDRESS>:10005
level=warn ts=2021-11-30T02:10:59.099929147Z caller=endpointset.go:512 component=endpointset msg="update of node failed" err="getting metadata: fallback fetching info from <IP_ADDRESS>:10004 after err: rpc error: code = DeadlineExceeded desc = context deadline exceeded: rpc error: code = DeadlineExceeded desc = context deadline exceeded" address=<IP_ADDRESS>:10004
level=warn ts=2021-11-30T02:10:59.100016306Z caller=endpointset.go:512 component=endpointset msg="update of node failed" err="getting metadata: fallback fetching info from <IP_ADDRESS>:10003 after err: rpc error: code = DeadlineExceeded desc = context deadline exceeded: rpc error: code = DeadlineExceeded desc = context deadline exceeded" address=<IP_ADDRESS>:10003
```

Anything else we need to know:

Seems log not full display, could you provider more log about panc stack. it should start with "panic: xxx"
"

Hi @hanjm here is the output from the logs:
    2021/11/30 04:02:26 http: panic serving <IP_ADDRESS>:51262: runtime error: invalid memory address or nil pointer dereference
    goroutine 24149 [running]:
    net/http.(*conn).serve.func1(0xc0001a80a0)
        /usr/local/go/src/net/http/server.go:1804 +0x153
    panic(0x1b54060, 0x2f4a640)
        /usr/local/go/src/runtime/panic.go:971 +0x499
    github.com/thanos-io/thanos/pkg/api/query.(*QueryAPI).stores(0xc00030fba0, 0xc000fffb00, 0x0, 0x0, 0x0, 0x7000105, 0x0, 0xffffffffffffffff)
        /home/circleci/project/pkg/api/query/v1.go:717 +0xcb
    github.com/thanos-io/thanos/pkg/api.GetInstr.func1.1(0x2148fe0, 0xc000380d90, 0xc000fffb00)
        /home/circleci/project/pkg/api/api.go:211 +0x42
    net/http.HandlerFunc.ServeHTTP(0xc0007366d8, 0x2148fe0, 0xc000380d90, 0xc000fffb00)
        /usr/local/go/src/net/http/server.go:2049 +0x44
    github.com/thanos-io/thanos/pkg/server/http/middleware.RequestID.func1(0x2148fe0, 0xc000380d90, 0xc000fffa00)
        /home/circleci/project/pkg/server/http/middleware/request_id.go:40 +0x20c
    net/http.HandlerFunc.ServeHTTP(0xc0007366f0, 0x2148fe0, 0xc000380d90, 0xc000fffa00)
        /usr/local/go/src/net/http/server.go:2049 +0x44
    github.com/NYTimes/gziphandler.GzipHandlerWithOpts.func1.1(0x214c400, 0xc0000493e0, 0xc000fffa00)
        /home/circleci/go/pkg/mod/github.com/!n!y!times/gziphandler@v1.1.1/gzip.go:338 +0x299
    net/http.HandlerFunc.ServeHTTP(0xc00073b260, 0x214c400, 0xc0000493e0, 0xc000fffa00)
        /usr/local/go/src/net/http/server.go:2049 +0x44
    github.com/thanos-io/thanos/pkg/logging.(*HTTPServerMiddleware).HTTPMiddleware.func1(0x214c400, 0xc0000493e0, 0xc000fffa00)
        /home/circleci/project/pkg/logging/http.go:68 +0x399
    net/http.HandlerFunc.ServeHTTP(0xc00073b290, 0x214c400, 0xc0000493e0, 0xc000fffa00)
        /usr/local/go/src/net/http/server.go:2049 +0x44
    github.com/thanos-io/thanos/pkg/extprom/http.(*defaultInstrumentationMiddleware).NewHandler.func1(0x7fc8085d7410, 0xc0008aff90, 0xc000fffa00)
        /home/circleci/project/pkg/extprom/http/instrument_server.go:108 +0x10f
    net/http.HandlerFunc.ServeHTTP(0xc00073b350, 0x7fc8085d7410, 0xc0008aff90, 0xc000fffa00)
        /usr/local/go/src/net/http/server.go:2049 +0x44
    github.com/prometheus/client_golang/prometheus/promhttp.InstrumentHandlerResponseSize.func1(0x7fc8085d7410, 0xc0008aff40, 0xc000fffa00)
        /home/circleci/go/pkg/mod/github.com/prometheus/client_golang@v1.11.0/prometheus/promhttp/instrument_server.go:198 +0xee
    net/http.HandlerFunc.ServeHTTP(0xc00073b650, 0x7fc8085d7410, 0xc0008aff40, 0xc000fffa00)
        /usr/local/go/src/net/http/server.go:2049 +0x44
    github.com/prometheus/client_golang/prometheus/promhttp.InstrumentHandlerCounter.func1(0x7fc8085d7410, 0xc0008afef0, 0xc000fffa00)
        /home/circleci/go/pkg/mod/github.com/prometheus/client_golang@v1.11.0/prometheus/promhttp/instrument_server.go:101 +0xdf
    net/http.HandlerFunc.ServeHTTP(0xc00073b8c0, 0x7fc8085d7410, 0xc0008afef0, 0xc000fffa00)
        /usr/local/go/src/net/http/server.go:2049 +0x44
    github.com/prometheus/client_golang/prometheus/promhttp.InstrumentHandlerRequestSize.func1(0x214e860, 0xc0007b6700, 0xc000fffa00)
        /home/circleci/go/pkg/mod/github.com/prometheus/client_golang@v1.11.0/prometheus/promhttp/instrument_server.go:165 +0xee
    net/http.HandlerFunc.ServeHTTP(0xc00073bbc0, 0x214e860, 0xc0007b6700, 0xc000fffa00)
        /usr/local/go/src/net/http/server.go:2049 +0x44
    github.com/thanos-io/thanos/pkg/tracing.HTTPMiddleware.func1(0x214e860, 0xc0007b6700, 0xc000fff700)
        /home/circleci/project/pkg/tracing/http.go:46 +0x54c
    github.com/prometheus/common/route.(*Router).handle.func1(0x214e860, 0xc0007b6700, 0xc000ffe400, 0x0, 0x0, 0x0)
        /home/circleci/go/pkg/mod/github.com/prometheus/common@v0.30.0/route/route.go:83 +0x27f
    github.com/julienschmidt/httprouter.(*Router).ServeHTTP(0xc000680d20, 0x214e860, 0xc0007b6700, 0xc000ffe400)
        /home/circleci/go/pkg/mod/github.com/julienschmidt/httprouter@v1.3.0/router.go:387 +0xc7e
    github.com/prometheus/common/route.(*Router).ServeHTTP(0xc00007f2c0, 0x214e860, 0xc0007b6700, 0xc000ffe400)
        /home/circleci/go/pkg/mod/github.com/prometheus/common@v0.30.0/route/route.go:121 +0x4c
    net/http.(*ServeMux).ServeHTTP(0xc00045d600, 0x214e860, 0xc0007b6700, 0xc000ffe400)
        /usr/local/go/src/net/http/server.go:2428 +0x1ad
    net/http.serverHandler.ServeHTTP(0xc0007b6000, 0x214e860, 0xc0007b6700, 0xc000ffe400)
        /usr/local/go/src/net/http/server.go:2867 +0xa3
    net/http.(*conn).serve(0xc0001a80a0, 0x2155c70, 0xc000cbc240)
        /usr/local/go/src/net/http/server.go:1932 +0x8cd
    created by net/http.(*Server).Serve
        /usr/local/go/src/net/http/server.go:2993 +0x39b

Same issue with https://github.com/thanos-io/thanos/issues/4777. It has fixed by https://github.com/thanos-io/thanos/pull/4805. Could you try the v0.24.0-rc.0? https://github.com/thanos-io/thanos/releases/tag/v0.24.0-rc.0

Hi @hanjm working now - thanks a lot :)


node-gyp rebuild error on CircleCI containers

I encounter the following error when npm install<EMAIL_ADDRESS>on the CircleCI containers:
$ npm install<EMAIL_ADDRESS>-
><EMAIL_ADDRESS>install /home/ubuntu/backend/node_modules/grpc
> node-gyp rebuild

make: Entering directory `/home/ubuntu/backend/node_modules/grpc/build'
  CXX(target) Release/obj.target/grpc/ext/byte_buffer.o
  CXX(target) Release/obj.target/grpc/ext/call.o
  CXX(target) Release/obj.target/grpc/ext/channel.o
  CXX(target) Release/obj.target/grpc/ext/completion_queue_async_worker.o
../ext/completion_queue_async_worker.cc: In member function ‘virtual void grpc::node::CompletionQueueAsyncWorker::Execute()’:
../ext/completion_queue_async_worker.cc:65:60: error: could not convert ‘gpr_inf_future’ from ‘gpr_timespec (*)(gpr_clock_type)’ to ‘gpr_timespec’
make: *** [Release/obj.target/grpc/ext/completion_queue_async_worker.o] Error 1
make: Leaving directory `/home/ubuntu/backend/node_modules/grpc/build'
gyp ERR! build error
gyp ERR! stack Error: `make` failed with exit code: 2
gyp ERR! stack     at ChildProcess.onExit (/home/ubuntu/nvm/v0.10.33/lib/node_modules/npm/node_modules/node-gyp/lib/build.js:269:23)
gyp ERR! stack     at ChildProcess.emit (events.js:98:17)
gyp ERR! stack     at Process.ChildProcess._handle.onexit (child_process.js:810:12)
gyp ERR! System Linux 3.14.28-031428-generic
gyp ERR! command "node" "/home/ubuntu/nvm/v0.10.33/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"
gyp ERR! cwd /home/ubuntu/backend/node_modules/grpc
gyp ERR! node -v v0.10.33
gyp ERR! node-gyp -v v2.0.1
gyp ERR! not ok
npm ERR! Linux 3.14.28-031428-generic
npm ERR! argv "node" "/home/ubuntu/nvm/v0.10.33/bin/npm" "i" "grpc"
npm ERR! node v0.10.33
npm ERR! npm  v2.11.1
npm ERR! code ELIFECYCLE

npm ERR<EMAIL_ADDRESS>install: `node-gyp rebuild`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>install script 'node-gyp rebuild'.
npm ERR! This is most likely a problem with the grpc package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     node-gyp rebuild
npm ERR! You can get their info via:
npm ERR!     npm owner ls grpc
npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request:
npm ERR!     /home/ubuntu/backend/npm-debug.log

uname: Linux box404 3.14.28-031428-generic #201501081937 SMP Thu Jan 8 19:39:13 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux
grpc lib commit: d1408e71636f7ec74839a9bcff0429fb7e2caeb0 (git clone, make, make install...)

It looks to me like you have an older version of the gRPC C core than what the Node library requires. You should try reinstalling that.

That was it, thanks @murgatroid99


Dropdown menu dot selection shows as misaligned

Describe the bug
Dropdown menu shows the dots / ticks / icon misaligned for a user. Original thread 👉 here.
DropdownMenu uses Radix, this doesn't have any open issues related to it. Unable to reproduce locally but found that display: flow is causing this on the RadioItem component (explanation here).
Potential solution, add a global CSS fix for the specific browser?
To Reproduce
Steps to reproduce the behavior:

Open the plugin
Open any dropdown with icons (i.e. 'Apply to...')
See misalignment

Expected behavior
Icons should be aligned.
Screenshots or Screencasts

This likely comes from the DS where the DropdownMenu Item doesnt have position relative but the icon slots are using position absolute?
github.com/tokens-studio/ds

Note that I am unable to reproduce this one


[Blogpost] A Comprehensive Guide to Peer-to-Peer NFT Atomic Swaps

Thank you for your contribution to the KodaDot - One Stop Shop for Polkadot NFTs.
👇 __ Let's make a quick check before the contribution.
PR Type

[ ] Bugfix
[x] Feature
[ ] Refactoring

Context

[x] Closes #6574
[ ] Requires deployment <snek/rubick/worker>

Did your issue had any of the "$" label on it?

[x] Fill up your DOT address: Payout

Community participation

[x] Are you at KodaDot Discord?

Screenshot 📸

Copilot Summary

🤖 Generated by Copilot at ef8c32f
Added a new blog post a-comprehensive-guide-to-peer-to-peer-nft-atomic-swaps.md that explains how to use peer-to-peer NFT swaps on the kodadot/nft-gallery platform. This change aims to educate and attract users to the platform's unique feature.

🤖 Generated by Copilot at ef8c32f

NFT swaps guide
A new post for the blog
Autumn of innovation

pay 50 usd

😍 Perfect, I’ve sent the payout
💵 $50 @ 4.98 USD/DOT ~ 10.04 $DOT
🧗 16faLfsywwNATaEfbH2ah75dn6ZmctQWpMS5G4KFhbmj5hnD
🔗 0xc950f17e324f0276bcf795ce4533babc2b4ba10ced5d2c56d46b2d105945e01e
🪅 Let’s grab another issue and get rewarded!
🪄 github.com/kodadot/nft-gallery/issues


NIFI-1829 - Create new DebugFlow processor.

Create DebugFlow processor for use in testing and troubleshooting the processor framework.

0.x - commits as is.

1.x - in o.a.n.p.s.DebugFlow.java replace ProcessorLog references with ComponentLog.

reviewing this

The name isn't great but not sure what would be better.  It is indeed a debugger for the framework and less so for a flow.  It is perhaps good to call it 'CreateChaos'.  That said i personally think this is a great idea to have in the build and part of the standard processors.  It would only be used by power users or curious types.  And for everyone else it is a noop.  But it could make it easier for us to demonstrate the evil effects of constant exceptions in a flow and do interesting regression checks on various infrastructures.  There is admittedly probably a better place for this but with the upcoming nar registry work we can tackle that then.

@jskora rebased and addressed comments, @trkurc are you able to finish reviewing this for 0.7.0?

Not until this weekend
On Jun 15, 2016 4:30 PM, "Joe Percivall"<EMAIL_ADDRESS>wrote:

@jskora https://github.com/jskora rebased and addressed comments,
@trkurc https://github.com/trkurc are you able to finish reviewing this
for 0.7.0?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/apache/nifi/pull/458#issuecomment-226205185, or mute
the thread
https://github.com/notifications/unsubscribe/AC6MklhVNpoG5GKrpPEsn5Yk0ixSetZ6ks5qMAydgaJpZM4IjZYv
.

It looks like the issues I had were addressed, but I won't have a chance to dive in deeper until Saturday, maybe

@trkurc ok, in order to get 0.7.0 as soon as possible, would you mind if another committer took over reviewing?

I will review.

I don't mind even a little! Thanks @mosermw

Ok, I think that last commit covers the review feedback.

Completed review, latest changes look good, unit testing and integration testing worked as expected, code passes -Pcontrib-check.
+1 I will squash commits and merge to 0.x and master shortly.  Thanks @jskora.


Some of the GenerateXcodeprojTests are hanging on pull request testing

Some of the Xcode project generation tests were using in-memory file systems and others not.  But the Xcode project generation code does not currently support non-local file systems (which should itself perhaps be addressed), and so this could cause tests to start traversing large parts of the actual file system, including over NFS mounts.
Ideally the Xcode project generation should support the in-memory file system, but since this functionality was primarily useful before Xcode supported loading packages natively, it's not clear whether it's worth the effort to fix that.
rdar://65200866

@swift-ci please smoke test

The test failure (XCTAssertEqual failed: ("couldn't find pc file for BTarget") is not equal to ("couldn't find pc file")) is one that I've seen locally as well.  It's unrelated to this change.  Still, I'd like to fix that before merging this PR just to make sure we have a green checkmark.

I think I see what's going on here.  A change went into swift-tools-support-core that changed the diagnostic string here, but the corresponding swift-package-manager PR is still open as https://github.com/apple/swift-package-manager/pull/2779.  I'll see what's preventing that one from getting merged, but this confirms that it's unrelated to the changes in this PR.

Waiting for https://github.com/apple/swift-package-manager/pull/2779 to finish its tests, after which we can merge it (it's been approved).  That should make the tests for this PR go green, and then we just need a review before merging.

@swift-ci please smoke test

Probably best to view the diff without whitespace changes, since the nesting level changed for some of the code in the tests.


Redirect user to concierge when onboarding completed

Details
Redirect where user was when they try to deeplink to the onboarding flow after completion
Fixed Issues
$ https://github.com/Expensify/App/issues/40876
PROPOSAL: https://github.com/Expensify/App/issues/40876#issuecomment-2081298473
Tests

Complete the onboarding steps for current login.
Try to visit onboarding url, https://dev.new.expensify.com:8082/onboarding, via deeplink or directly
Should be redirected to concierge page.

[x] Verify that no errors appear in the JS console

Offline tests
If user already completed onboarding steps, https://staging.new.expensify.com/onboarding should be redirected to concierge page.
If not, this will not work, because onboarding completion status comes from Backend.
QA Steps

Complete the onboarding steps for current login.
Try to visit onboarding url, https://staging.new.expensify.com/onboarding, via deeplink or directly
Should be redirected to concierge page.

[x] Verify that no errors appear in the JS console

PR Author Checklist

[x] I linked the correct issue in the ### Fixed Issues section above
[x] I wrote clear testing steps that cover the changes made in this PR

[x] I added steps for local testing in the Tests section
[x] I added steps for the expected offline behavior in the Offline steps section
[x] I added steps for Staging and/or Production testing in the QA steps section
[x] I added steps to cover failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
[x] I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
[x] I tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).

[x] I included screenshots or videos for tests on all platforms
[x] I ran the tests on all platforms & verified they passed on:

[x] Android: Native
[x] Android: mWeb Chrome
[x] iOS: Native
[x] iOS: mWeb Safari
[x] MacOS: Chrome / Safari
[x] MacOS: Desktop

[x] I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
[x] I followed proper code patterns (see Reviewing the code)

[x] I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick)
[x] I verified that the left part of a conditional rendering a React component is a boolean and NOT a string, e.g. myBool && <MyComponent />.
[x] I verified that comments were added to code that is not self explanatory
[x] I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
[x] I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method

[x] If any non-english text was added/modified, I verified the translation was requested/reviewed in #expensify-open-source and it was approved by an internal Expensify engineer. Link to Slack message:

[x] I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
[x] I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is either coming verbatim from figma or has been approved by marketing (in order to get marketing approval, ask the Bug Zero team member to add the Waiting for copy label to the issue)
[x] I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
[x] I verified the JSDocs style guidelines (in STYLE.md) were followed

[x] If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
[x] I followed the guidelines as stated in the Review Guidelines
[x] I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
[x] I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
[x] I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
[x] I verified that if a function's arguments changed that all usages have also been updated correctly
[x] If any new file was added I verified that:

[x] The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory

[x] If a new CSS style is added I verified that:

[x] A similar style doesn't already exist
[x] The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(theme.componentBG))

[x] If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
[x] If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
[x] If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
[x] If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
[x] If the PR modifies the UI (e.g. new buttons, new UI components, changing the padding/spacing/sizing, moving components, etc) or modifies the form input styles:

[x] I verified that all the inputs inside a form are aligned with each other.
[x] I added Design label and/or tagged @Expensify/design so the design team can review the changes.

[x] If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
[x] If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.

Screenshots/Videos

Android: Native

Android: mWeb Chrome
https://github.com/Expensify/App/assets/25519849/5ebabc98-c006-41da-8df8-4408426572c9

iOS: Native
https://github.com/Expensify/App/assets/25519849/e01a9578-627c-436c-bf3f-6214d37d5505

iOS: mWeb Safari
https://github.com/Expensify/App/assets/25519849/2d60d7f5-a870-4837-870a-8e97e692e0ac

MacOS: Chrome / Safari
https://github.com/Expensify/App/assets/25519849/7dc243f0-0514-4c2a-9a82-d6e2e8eccad0

MacOS: Desktop
https://github.com/Expensify/App/assets/25519849/174e0660-6d34-4c7c-956a-7e510f7956c6

I have read the CLA Document and I hereby sign the CLA

The modal appears and after loading is complete it disappears.
https://github.com/Expensify/App/assets/102477862/2b122c3d-15f2-4d35-b608-a3d1298fa489
Can we change this to not show the modal at all for already onboarded users?

@c3024 I will look into this. BTW, this behavior depends on nvp_onboarding.hasCompletedGuidedSetupFlow so if current user session still in receiving this state, modal will be visible...
To solve this,

Set  nvp_onboarding.hasCompletedGuidedSetupFlow as true optimistically ( as most current users are already completed onboarding), so every users will be redirected to concierge by default.
For non-completed users, once BE sends false for this value, I will redirect the user to onboarding page.

Let me know your thoughts on this.

I agree.
We are showing the modal only after this promise is resolved here as well so it should be fine.
https://github.com/Expensify/App/blob/cba6916458c91e26ab8fb795956df0aa9508d6ab/src/libs/actions/Welcome.ts#L33

@c3024 I set onboarding status completed as initial.

@c3024 Thanks for your professional review. Just pushed the fixes as you guided.

Reviewer Checklist

[ ] I have verified the author checklist is complete (all boxes are checked off).
[ ] I verified the correct issue is linked in the ### Fixed Issues section above
[ ] I verified testing steps are clear and they cover the changes made in this PR

[ ] I verified the steps for local testing are in the Tests section
[ ] I verified the steps for Staging and/or Production testing are in the QA steps section
[ ] I verified the steps cover any possible failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
[ ] I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)

[ ] I checked that screenshots or videos are included for tests on all platforms
[ ] I included screenshots or videos for tests on all platforms
[ ] I verified tests pass on all platforms & I tested again on:

[ ] Android: Native
[ ] Android: mWeb Chrome
[ ] iOS: Native
[ ] iOS: mWeb Safari
[ ] MacOS: Chrome / Safari
[ ] MacOS: Desktop

[ ] If there are any errors in the console that are unrelated to this PR, I either fixed them (preferred) or linked to where I reported them in Slack
[ ] I verified proper code patterns were followed (see Reviewing the code)

[ ] I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick).
[ ] I verified that the left part of a conditional rendering a React component is a boolean and NOT a string, e.g. myBool && <MyComponent />.
[ ] I verified that comments were added to code that is not self explanatory
[ ] I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
[ ] I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method
[ ] I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
[ ] I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is either coming verbatim from figma or has been approved by marketing (in order to get marketing approval, ask the Bug Zero team member to add the Waiting for copy label to the issue)
[ ] I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
[ ] I verified the JSDocs style guidelines (in STYLE.md) were followed

[ ] If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
[ ] I verified that this PR follows the guidelines as stated in the Review Guidelines
[ ] I verified other components that can be impacted by these changes have been tested, and I retested again (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar have been tested & I retested again)
[ ] I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
[ ] I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
[ ] If a new component is created I verified that:

[ ] A similar component doesn't exist in the codebase
[ ] All props are defined accurately and each prop has a /** comment above it */
[ ] The file is named correctly
[ ] The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
[ ] The only data being stored in the state is data necessary for rendering and nothing else
[ ] For Class Components, any internal methods passed to components event handlers are bound to this properly so there are no scoping issues (i.e. for onClick={this.submit} the method this.submit should be bound to this in the constructor)
[ ] Any internal methods bound to this are necessary to be bound (i.e. avoid this.submit = this.submit.bind(this); if this.submit is never passed to a component event handler like onClick)
[ ] All JSX used for rendering exists in the render method
[ ] The component has the minimum amount of code necessary for its purpose, and it is broken down into smaller components in order to separate concerns and functions

[ ] If any new file was added I verified that:

[ ] The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory

[ ] If a new CSS style is added I verified that:

[ ] A similar style doesn't already exist
[ ] The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(theme.componentBG)

[ ] If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
[ ] If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
[ ] If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
[ ] If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
[ ] If the PR modifies the UI (e.g. new buttons, new UI components, changing the padding/spacing/sizing, moving components, etc) or modifies the form input styles:

[ ] I verified that all the inputs inside a form are aligned with each other.
[ ] I added Design label and/or tagged @Expensify/design so the design team can review the changes.

[ ] If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
[ ] If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.
[ ] I have checked off every checkbox in the PR reviewer checklist, including those that don't apply to this PR.

Screenshots/Videos

Android: Native

Android: mWeb Chrome

iOS: Native

iOS: mWeb Safari

MacOS: Chrome / Safari

MacOS: Desktop

Lint is failing too @skyweb331

Tests well
https://github.com/Expensify/App/assets/102477862/e84b57b7-579c-447f-a6da-507bf5293e21
https://github.com/Expensify/App/assets/102477862/39c357d4-35fe-4e91-906b-fba9c5331269
This is the difference prettier is showing that is causing the lint failure. I don't see any difference. 🫤

@skyweb331
please fix lint by running npm run prettier

@c3024 Prettier fixed.

@skyweb331 sorry, can you please resolve merge conflicts before I can merge?

@mountiny Done.

@skyweb331
Please move this
    if (hasCompletedGuidedSetupFlow) {
        return null;
    }

in OnboardingModalNavigator below the newly added hooks.
Hooks should not be added below null return.
Lint is failing.
There is a prettier difference as well.
Please run npm run prettier and npm run lint and fix errors (if any) every time before committing.

@skyweb331 please address the feedback whenever you can, thanks!

@c3024 Sorry for wrong merging. I will run npm run prettier && npm run lint every time.

@c3024 Done.

@c3024 can you please approve if all looks good for you. I think the comments were addressed but nowhere to rush

:hand: This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.

🚀 Deployed to production by https://github.com/Julesssss in version: 1.4.79-11 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅


Spouse/partner being asked what branch they served in

Bug Report
What is the current behavior?
As a spouse/partner of a military service member, I am asked what branch of the military I serve/served in.
What is the expected behavior?
Instead, if the user selects spouse/partner, the user should instead be asked what branch their spouse/partner is in.
What steps did you take to get this behavior?
Register a new user, select military service member (not volunteer), and see the screen posted as a screenshot. Once there, look at the 2nd input's text.
Additional Info
Operating System
Linux Fedora 23 and MacOS latest
Browser
Chrome latest
Screenshots

If its still available, I would like to take this on.
A quick and dirty solution could be simply to change the wording on the selection to something along the lines of "Service Branch affiliation." This lacks a bit of personality though.
Would a more elegant way  be to simply add an even listener to the option value for spouse that triggers the change in text for the second drop down?

You can use local state with Initial state being what it currently is. If the user chooses "Spouse/Partner", state is changed to reflect something more related to being a Spouse/Partner for the second field.

I do see value in collecting data re. service branch affiliation.

I second @hollomancer's opinion here. It's a quick fix if you change the relevant "select" name and value in src/shared/constants/status.js!

Thanks @kylemh I'll be  tackling it over the next few evenings and over the weekend. If I run across anything, I'll post it here

Ok, so I am sort of lost on this one if I'm being honest. I'm still learning a TON about react. In particular how State works. From my understanding so far, the file we need to alter is militaryInfo.js. When {MILSTATUS} is  equal to value spouse, the state should update and change the prompt for the branch id of the form.
This is where I get lost, and I am having a bit of trouble finding easy to digest information. should I be writing a function outside of render that will look/listen for when {milStatus} is selected and update the state to display the appropriate prompt in the id branch? Is this something that is handled in the onChange functions?
I have not had a decent chunk of time to really dig into the react docs on the subject ( wanted to this weekend, wife had other plans lol), am I on the right track here, or am I completely off the rails?

Every time state is updated, it re-renders. So you could do a check in the render function to determine if something should actually be rendered. I haven't looked too far into this, but this is the general idea I have in mind.
render() {
    return (
        // ...
        {this.shouldRequestBranch}
    );
},

shouldRequestBranch() {
    if (this.state.milStatus === 'spouse') return false;
    return <FormSelect />
}

@Tsilvernail you're on the right direction. you could store the branch prompt in the state of the component. once milstatus was changed, simply override the prompt with the new text according to the value of milstatus

@Tsilvernail don't give up. Feel free to ask for more advice in our Slack team. We ❤  new contributors!

sorry for the delay, progress has been hard to make with work. here is what I ahve as of right now. I'm having trouble testing it on a local set up bc its not saving the information in the signup form (I have to manually navigate there as well)
would something like this work for this issue?
` class MilitaryInfo extends Component {
const isSpouse = function(){
if({MILSTATUS} === spouse{
return "Spouse's Branch of Service"
} else{
return "Branch of Service"
})
}
...
<FormSelect
id="branch"
options={BRANCH}
prompt={isSpouse}
onChange={e => this.props.update(e, e.target.value)}
/>

`
My initial thought is that this won't work because I'm not interacting with state. I also assume we would want to refactor a final solution to line up with es6/jsx. I will have more time Sat. evening and Sunday all day to work on this, with the goal of having a solution that can be committed before monday.

@Tsilvernail Your'e on the right direction. A few issues I noticed:

You refer to MILSTATUS as the selected option. MILSTATUS is the array of options .

Another issue is that the prompt will be initialized only once instead of each time the user selects military status

@Tsilvernail any updates?

hey thanks for poking me on this. I have had the flu the last week while trying to prep for an interview. I believe I have a solution worked out. I will update when I get home and can access everything! Its been going way longer than it should have and I apologize for that!

@Tsilvernail no problemo! The repo is moving fast with #hacktoberfest and I didn't want your work getting left behind.

So I don't feel like I can get to this in a reasonable amount of time. My lschedule has taken a turn for the insane and I just don't have the time to put towards contributions like I thought I would :/ anyone who wants to pick this up is more than welcome too, so that it can be completed. I don't want to hold up progress!

No worries @Tsilvernail I'll take it

@Tsilvernail I appreciate the work you've put into this regardless. Good luck!


Updating Developer Docs

Adding Google-related diagrams and explanations
Cleaning up redundant areas

Pull Request Test Coverage Report for Build 458

8 of 16 (50.0%)  changed or added relevant lines in 4 files are covered.
4 unchanged lines in 3 files lost coverage.
Overall coverage decreased (-0.2%) to 82.512%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

src/main/java/seedu/address/model/google/PhotoHandler.java
5
6
83.33%

src/main/java/seedu/address/logic/commands/google/GoogleDlCommand.java
0
2
0.0%

src/main/java/seedu/address/logic/commands/google/GoogleRefreshCommand.java
1
3
33.33%

src/main/java/seedu/address/logic/commands/google/GoogleLsCommand.java
2
5
40.0%

Files with Coverage Reduction
New Missed Lines
%

src/main/java/seedu/address/logic/commands/google/GoogleLsCommand.java
1
44.44%

src/main/java/seedu/address/logic/commands/google/GoogleRefreshCommand.java
1
50.0%

src/main/java/seedu/address/commons/util/FileUtil.java
2
66.67%

Totals

Change from base Build 456:
-0.2%

Covered Lines:
1958

Relevant Lines:
2373

💛  - Coveralls


Adorable patch 1

Fixed a few bugs in main.py (Invalid Directory errors)
Added new breaches
Cleaned data

Note: There is a lower total record count due to me updating a few initial databases. These databases contained the hashed and dehashed versions of the same database. I managed to find full dehashed/hashed versions instead. There are still a few present like LinkedIn but I removed invalid data found in that breach as well.
New Breaches:

000WebHost
Adobe
Brazzers
Coachell
DailyQuiz
DatPiff
DropBox
Edmodo
FunOfficePools
GameStop
GateHub
LastFM
MangoFox
Mate1
MongoDex
MyFitnessPal
MySpace
NeoPets
NetEase
NitroPDF
PlexTV
Poshmark
SlideTeam
SnailGames
Twitter
Walmart
Wanelo
XboxScene
Zynga

FSU Records (Updated).xlsx


Question: Is metricsd still maintained?

Hi @mojodna and thanks for your work on metricsd, it's a really useful tool :)
It seems that there's been no activity on this project since Feb 1, 2013 though, so I'm wondering if you still have the time to maintain it?
Best,
Jan

We still use it (lightly, and I'm intermittently investigating InfluxDB to replace it) and I think others are more heavily (though I couldn't be certain).
The beauty is that (because of the metrics library) it doesn't need to do much.  Practically all of the updates have involved updating dependencies, which, if it works, aren't necessarily necessary.
I'd say that if it meets your needs in a more specific way than any of the other statsd server implementations, it should be safe to use.  If you think it needs some features to become usable, you should either take those on yourself or evaluate a different tool.


Fixes #61 wraps path to start-tc-server.bat in double quotes.

I will check in the ehcache3 integration-test once this is merged.

Revert the whitespace-only changes, first.

ok trying to do that now.  For some reason when I check it out it removes those white spaces automatically.

ok fixed the white spaces.  NetBeans was changing the file on save!  Anyways I pushed the bug fix and a unit test.

Yeah, a lot of tools come with the "do random stuff to my source" options enabled, by default, for some reason.  It is one of the reasons why I use a diff tool which isn't part of my IDE (since I don't want them colluding to hide things from me which will pollute the version history and distract other developers).
This change looks good and thanks for including a comment explaining why this case matters (I am one of the people who is pushing for more inline comments in the source so I definitely appreciate it).
We can do a release of these things, tomorrow, if this is causing immediate problems downstream (we can include a non-critical change which went into the passthrough repo, too).  Due to the recent change, only those 2 repos will need the release.


clang: error: linker command failed with exit code 1 (use -v to see invocation)

I follow step by step installation instructions but building fail with this error:
clang: error: linker command failed with exit code 1 (use -v to see invocation)

i solved it by myself unlinking all libraries except libPods.a in the section Build Phases -> Link Binary With Libraries of the main project(not Pods)


fix: update translations

Testing

Trade-offs

Dependencies

Screenshots

:tada: This PR is included in version 2.40.6 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Loki backend for rules check

There was a backend flag to rules check that allowed passing in Loki as an option. Is there an alternative to it now?
https://github.com/grafana/cortex-tools/blob/1499f5fb286e672cd238a525169d4cb05f964eab/pkg/commands/rules.go#L51
❯ ~/Downloads/cortextool_0.17.0_mac-os_x86_64 rules check alerting/loki/*.yaml
ERRO[0000] unable parse rules file                       error="6:17: group \"pulsar-bigquery\", rule 0, \"ErrorsInLogs\": could not parse expression: 1:68: parse error: unexpected character: '|'" file=alerting/loki/bqloader-alerts.yaml
cortextool_0.17.0_mac-os_x86_64: error: check operation unsuccessful, unable to parse rules files: file read error, try --help

expr in question:
expr: sum(rate({app="pulsar-bigquery", environment=~"prod|stage"} |= `ERROR`[1m])) by (environment, instance, tenant, deploy_region, team, app, org) > 0

Hey @adyanth, I believe Loki is out of the scope of this tool now and they should have their own tool to perform such kind of task. Hence, I am going to close this issue


Cleanup of profile image

Description
When user changes their profile image its ref is deleted from the user collection but the image is still available in the cloud storage. And the same goes for background image I believe. I want to cleanup both of them.
Steps to reproduce
Check the function for changing image. It just update the photoURL and nothing else.
Screenshots
No response
Desktop (please complete the following information)
No response
Smartphone (please complete the following information)
No response
Additional information
No response
Record

[X] I agree to follow this project's Code of Conduct
[X] I have checked the existing issues
[X] I'm a GSSoC'23 contributor
[X] I want to work on this issue

sure you can go ahead!


bug in setup script that causes tarball to be renamed instead of crtm install directory

On NCCS (rather than my laptop), the setup script can pickup the crtm tarball instead of the install directory (if you're lazy like me and point install and tarball location to the same spot).

resolved with #71


code not working in Godot 4.0

This code does not work in Godot 4.0 since some function names have been changed, the functions are:

update() : renamed to queue_redraw()
remove() : renamed to remove_at()
variable Time now causes conflict with an already reserved node

after changing the function names it seems to work fine, I have provided the fixed code below.

 Fixed code
extends Node2D

class Line:
	var Start
	var End
	var LineColor
	var time

	func _init(Start, End, LineColor, time):
		self.Start = Start
		self.End = End
		self.LineColor = LineColor
		self.time = time

var Lines = []
var RemovedLine = false

func _process(delta):
	for i in range(len(Lines)):
		Lines[i].time -= delta

	if(len(Lines) > 0 || RemovedLine):
		queue_redraw() #Calls _draw
		RemovedLine = false

func _draw():
	var Cam = get_viewport().get_camera_3d()
	for i in range(len(Lines)):
		var ScreenPointStart = Cam.unproject_position(Lines[i].Start)
		var ScreenPointEnd = Cam.unproject_position(Lines[i].End)

		#Dont draw line if either start or end is considered behind the camera
		#this causes the line to not be drawn sometimes but avoids a bug where the
		#line is drawn incorrectly
		if(Cam.is_position_behind(Lines[i].Start) ||
			Cam.is_position_behind(Lines[i].End)):
			continue

		draw_line(ScreenPointStart, ScreenPointEnd, Lines[i].LineColor)

	#Remove lines that have timed out
	var i = Lines.size() - 1
	while (i >= 0):
		if(Lines[i].time < 0.0):
			Lines.remove_at(i)
			RemovedLine = true
		i -= 1

func DrawLine(Start, End, LineColor, time = 0.0):
	Lines.append(Line.new(Start, End, LineColor, time))

func DrawRay(Start, Ray, LineColor, time = 0.0):
	Lines.append(Line.new(Start, Start + Ray, LineColor, time))

func DrawCube(Center, HalfExtents, LineColor, time = 0.0):
	#Start at the 'top left'
	var LinePointStart = Center
	LinePointStart.x -= HalfExtents
	LinePointStart.y += HalfExtents
	LinePointStart.z -= HalfExtents

	#Draw top square
	var LinePointEnd = LinePointStart + Vector3(0, 0, HalfExtents * 2.0)
	DrawLine(LinePointStart, LinePointEnd, LineColor, time);
	LinePointStart = LinePointEnd
	LinePointEnd = LinePointStart + Vector3(HalfExtents * 2.0, 0, 0)
	DrawLine(LinePointStart, LinePointEnd, LineColor, time);
	LinePointStart = LinePointEnd
	LinePointEnd = LinePointStart + Vector3(0, 0, -HalfExtents * 2.0)
	DrawLine(LinePointStart, LinePointEnd, LineColor, time);
	LinePointStart = LinePointEnd
	LinePointEnd = LinePointStart + Vector3(-HalfExtents * 2.0, 0, 0)
	DrawLine(LinePointStart, LinePointEnd, LineColor, time);

	#Draw bottom square
	LinePointStart = LinePointEnd + Vector3(0, -HalfExtents * 2.0, 0)
	LinePointEnd = LinePointStart + Vector3(0, 0, HalfExtents * 2.0)
	DrawLine(LinePointStart, LinePointEnd, LineColor, time);
	LinePointStart = LinePointEnd
	LinePointEnd = LinePointStart + Vector3(HalfExtents * 2.0, 0, 0)
	DrawLine(LinePointStart, LinePointEnd, LineColor, time);
	LinePointStart = LinePointEnd
	LinePointEnd = LinePointStart + Vector3(0, 0, -HalfExtents * 2.0)
	DrawLine(LinePointStart, LinePointEnd, LineColor, time);
	LinePointStart = LinePointEnd
	LinePointEnd = LinePointStart + Vector3(-HalfExtents * 2.0, 0, 0)
	DrawLine(LinePointStart, LinePointEnd, LineColor, time);

	#Draw vertical lines
	LinePointStart = LinePointEnd
	DrawRay(LinePointStart, Vector3(0, HalfExtents * 2.0, 0), LineColor, time)
	LinePointStart += Vector3(0, 0, HalfExtents * 2.0)
	DrawRay(LinePointStart, Vector3(0, HalfExtents * 2.0, 0), LineColor, time)
	LinePointStart += Vector3(HalfExtents * 2.0, 0, 0)
	DrawRay(LinePointStart, Vector3(0, HalfExtents * 2.0, 0), LineColor, time)
	LinePointStart += Vector3(0, 0, -HalfExtents * 2.0)
	DrawRay(LinePointStart, Vector3(0, HalfExtents * 2.0, 0), LineColor, time)

I forgot to add it but the function get_camera() was also changed, you now need to call either get_camera_3d() or get_camera_2d()

Thanks for this! I'll bring your change in.


Not able to scrape pages

I getting below error
========= ERROR ============
TypeError: Cannot read property 'getUrl' of null
at Scraper.loadResource (D:\my_dir\migration\ooa\node_modules\website-scraper\lib\scraper.js:65:20)
at receivedResponse (D:\my_dir\migration\ooa\node_modules\website-scraper\lib\scraper.js:161:10)
at tryCatcher (D:\my_dir\migration\ooa\node_modules\bluebird\js\release\util.js:16:23)
at Promise._settlePromiseFromHandler (D:\my_dir\migration\ooa\node_modules\bluebird\js\release\promise.js:510:31)
at Promise._settlePromise (D:\my_dir\migration\ooa\node_modules\bluebird\js\release\promise.js:567:18)
at Promise._settlePromise0 (D:\my_dir\migration\ooa\node_modules\bluebird\js\release\promise.js:612:10)
at Promise._settlePromises (D:\my_dir\migration\ooa\node_modules\bluebird\js\release\promise.js:691:18)
at Promise._fulfill (D:\my_dir\migration\ooa\node_modules\bluebird\js\release\promise.js:636:18)
at Promise._resolveCallback (D:\my_dir\migration\ooa\node_modules\bluebird\js\release\promise.js:453:14)
at Promise._settlePromiseFromHandler (D:\my_dir\migration\ooa\node_modules\bluebird\js\release\promise.js:522:17)
at Promise._settlePromise (D:\my_dir\migration\ooa\node_modules\bluebird\js\release\promise.js:567:18)
at Promise._settlePromise0 (D:\my_dir\migration\ooa\node_modules\bluebird\js\release\promise.js:612:10)
at Promise._settlePromises (D:\my_dir\migration\ooa\node_modules\bluebird\js\release\promise.js:687:18)
at Async._drainQueue (D:\my_dir\migration\ooa\node_modules\bluebird\js\release\async.js:133:16)
at Async._drainQueues (D:\my_dir\migration\ooa\node_modules\bluebird\js\release\async.js:143:10)
at Immediate.Async.drainQueues (D:\my_dir\migration\ooa\node_modules\bluebird\js\release\async.js:17:14)
============== CODE (of course website name changed) =============
var scrape = require('website-scraper');
scrape({
urls: ['http://www.my-web-site.com/'],
directory: './goo',
recursive: true,
maxDepth: 1
}).then(console.log).catch(console.log);

Hi @sirajrkhan
What version of website-scraper do you use?
Please try 2.1.0 -  it has fix for similar problem

Hi .. thanks for quick response.
The version is: 3.10.10
Also, strangely it is only working for this URL: https://sitepoint.com/
I tried with/without trailing slashes and also http AND https -- no combination clicked

version 3.10.10 of website-scraper doesn't exist
latest is 2.1.0
please check website-scraper version running next command in your project directory
npm list website-scraper

Hey Thanks for all the help, really appreciated. With latest npm version (2.1.0) i am able to extract access randomly few sites (like https://fbrctr.github.io/) but for few sites like (http://www.hammerite.ie/) it is returning empty JSON. The code is same though.
[ Resource {
url: 'http://www.hammerite.ie/',
filename: 'index.html',
type: null,
depth: 0,
parent: null,
children: [],
saved: false } ]

Hey.. pls dont bother.. looks like it is due to firewall/proxy settings of the organization


Add Support for payAssetsWithData

Adds the ability to supply a datum to an output with a payment address.

@cjkoepke looks like CI failed on the format check
pnpm fmt if you could please :)


cd override error after update zsh to v5.4.1

Hi,
I've encountered this error after update to zsh 5.4.1 on my debian testing:
/home/user/.autoenv/activate.sh:1: defining function based on alias `cd'
/home/user/.autoenv/activate.sh:151: parse error near `()'

Any help is appreciated

@pimuzzo It's the latest feature of zsh, which through an error when you defining a function with the same name with an alias. See more details here


Make maximum login lifetime configurable, increase defaults

After upgrading the image, the default login timeout seems to be VERY short. This should be altered. Not 100% sure if this should go here or sodar-docker-compose, will move if needed.
Edit: Instead of simply increasing the default maximum values, we should make them configurable by env vars.

Is this login timeout with irods icommands? IIRC, this is goverend by PAM.

There are infact two settings for maximum login length. There is a separate one for PAM, yes. For some reason, one of these was set very short in my iRODS 4.3 unattended config template.

These settings have changed in 4.3.1+, see here.

iRODS support to the rescue: this is an undocumented feature in v4.3.1+, where one is supposed to use password_min_time instead of / in addition to password_max_time.


Fix links to ephemeral volume types

Closes #33564

/sig storage

/sig storage

Looks good to me!
/lgtm

/approve
/kind clieanup

@tengqm Weird, it looks like Prow missed your approval. Trying again:
/approve
/kind cleanup


Automatic cycle_mode detection causing errors for NDA files with only rest states

See proposed changes in this PR #65


comment at the end of each file what it's outputting

Let's have a comment at each return that highlight what kind of datatype / data structure it yields. This will make troubleshooting and understanding the code much better.

In the new comment function format we're using, this is where it belongs i.e. in the function comments.


PresentationPlan.md:25: App is started.

The puzzle 3-10056129 from #3 has to be resolved:
https://github.com/Stanislau/behavior-tree-for-testing/blob/23420cd3eeefb5da70aa937623a1b3c48de58a40/Documentation/PresentationPlan.md#L25-L25
The puzzle was created by @Stanislau on 23-Sep-24.
Estimate: 20 minutes,  role: A.
If you have any technical questions, don't ask me, submit new tickets instead. The task will be "done" when the problem is fixed and the text of the puzzle is removed from the source code. Here is more about PDD and about me.

The puzzle 3-10056129 has disappeared from the source code, that's why I closed this issue.


Implement authentications and secure transfer for server.

The browser server communication must be SSL all the way down. There is no other way to get the basics.


text_MOD.js

A mod for creating a variable in the form of text, or you can convert the text to a list and save it to a variable

Already exists


Set the unique_id attribute

https://github.com/scottyphillips/mitsubishi_echonet/commit/f1fdee2e697cc5ec5a984fa00d76dff5676a9dcc provides a unique identification for each devices.
Now we can set the unique_id attribute in the entities. With that, changing various parameters through not only YAML but the web interface could be possible (see: This entity does not have a unique ID?).

Ive implemented it as part of the entity initialisation rather then continually calling the API which is more in alignment with what Home Assistant expects us to do...

@scottyphillips Thanks for looking at the PR. I totally agree with your review!


annotate inject attribute

Annotate InjectAttribute with [MeansImplicitUse] to prevent non-nullable field uninitialized warning

https://www.jetbrains.com/help/resharper/Code_Analysis__Annotations_in_Source_Code.html#embedding-declarations-of-code-annotations-in-your-source-code


Make DfSchema wrap SchemaRef

Is your feature request related to a problem or challenge? Please describe what you are trying to do.
Currently DataFusion has two ways to represent a schema, Schema and DFSchema. The former is the representation used by arrow, and in most components. DFSchema appears to "enhance" an arrow schema with the notion of a qualifier.
I'm not entirely sure of the history of this split, but to the uninitiated the split is confusing and frustrating. It also results in a non-trivial amount of schema munging logic to convert to/from the relevant representations
Describe the solution you'd like
I would like to change DfSchema to be
struct DfSchema {
    schema: SchemaRef,
    fields: Vec<DfFieldMetadata>
}

struct DfFieldMetadata {
    qualifier: Option<String>,
}

We could then make DfSchema automatically deref to SchemaRef, or at the very least implement AsRef<SchemaRef>, avoiding a lot of code that ends up looking like
let schema: Schema = self.plan.schema().as_ref().into();
Arc::new(schema)

Components wishing to combine the information can easily zip the two together, we could even assist this by adding
struct DfField<'a> {
    field: &'a Field,
    metadata: &'a DfFieldMetadata
}

impl DfSchema {

    fn df_fields() -> impl Iterator<Item=DfField<'_>> + '_ {
        self.arrow_schema.fields().iter().zip(&self.fields).map(|(field, metadata)| DfField { field, metadata })
    }
}

Describe alternatives you've considered
We could not do this
Additional context
Add any other context or screenshots about the feature request here.

This mostly works but runs into issues with the handling of schemas in datafusion-expr. In particular they have a fairly hard-coded assumption that they can pass around DFField, concatenate them and munge them back into a DFSchema. It would be possible to workaround this, but it would be a fairly non-trivial amount of code-churn.

Attaching link to DFSchema struct for convenience https://github.com/apache/arrow-datafusion/blob/main/datafusion/common/src/dfschema.rs#L108

Ive been doing some work on planning performance and in order to lay a good foundation for the next steps I think this is necessary.  So my plan is to start working on this shortly.
CC @alamb @tustvold @comphead @avantgardnerio

Ive been doing some work on planning performance and in order to lay a good foundation for the next steps I think this is necessary. So my plan is to start working on this shortly.
CC @alamb @tustvold @comphead @avantgardnerio

Thank you @matthewmturner 🙏
BTW I started hacking on some version of what this might look like  in https://github.com/apache/arrow-datafusion/pull/7944 but I haven't had a chance to finish it

@alamb yes i saw, thanks. havent decided yet whether i will pick up on that PR or create a new one.

Feel free to do anyting you want with the code / PR


The image search option is disabled still, it is showing in the search bar.

Terms

[X] Before you openning this issue, i have checked if the issue has already been reported.

Bagisto Version(s) affected
master
Issue Description
The image search option is disabled still, it is showing in the search bar.
Preconditions

Admin should be logged in.
Admin needs to disable the image search option.

Steps to reproduce

Go to 'Admin panel'
Click on 'Content' inside the configuration
Disable the image search option and save it
Go to the Homepage
See the error

Expected Result
It should not be shown the image icon if the option is disabled.
Actual Result
It is still showing the icon. Admin Shop
Screenshots
No response
Additional context
No response

Now, this issue is fixed. so I am closing this issue.
And I have attached a screenshot Here, for future reference.


Public key expired for an admin.  Need to remove and add again?

An admin's public key expired so now I can't re-encrypt files.
Do I need to remove the admin and have them added again with their new or modified key?
I'm a bit confused on the workflow.  Thanks in advance.

Gosh I'm not sure what to suggest.  I haven't had to do this process yet. My guess is that you would do:
One way would be to decrypt everything with the old key, change keys, then re-encrypt:
""""
eval $(gpg-agent --daemon)          # If you don't already have an agent running.
blackbox_decrypt_all_files
(update the key)
for i in $(blackbox_list_files) ; do echo blackbox_edit_end "$i" ; done
(test to make sure things are correct before you check them in)
"""
Would you do me a favor and try this?  Keep good notes and report back.  I will turn your notes into an item for the FAQ and it will help others that have this problem.
Tom

Here's what I ended up doing:
Step 0
blackbox_edit_end modified_file.txt
--> Error: can't re-encrypt because a key has expired.

Step 1. Administrator removes expired user
blackbox_removeadmin<EMAIL_ADDRESS># Temporarily rename any modified files so they're not replaced by the next command.
blackbox_update_all_files
git commit -m "Re-encrypt all files"
gpg --homedir=keyrings/live --delete-key<EMAIL_ADDRESS>git commit -m 'Cleaned<EMAIL_ADDRESS>from keyring'  keyrings/live/*
git push

Step 2.  Administrator re-encrypts all files with the updated key of the expired user
git pull
gpg --import keyrings/live/pubring.gpg
blackbox_update_all_files
git commit -m "Re-encrypt all files"
git push

Last step
Any files that were temporarily renamed in the first step so as to not be overwritten can now be renamed to their original name and re-encrypted with the blackbox_edit_end command.

Thanks for the most excellent documentation!  (and I know it is excellent because your style is very similar to mine!)
I've included this in the readme: https://github.com/StackExchange/blackbox/commit/f7a159d685c4af26c4c811a6e1599b8037ac602f


Create inscriptions.json

close as original collections/bitp was merged and this workaround pr is not necessary anymore.


chore(blockifier_reexecution): move reexecution to seperate function

This change is

crates/blockifier_reexecution/src/state_reader/utils.rs line 192 at r1 (raw file):
Previously, dorimedini-starkware wrote…
you are synced with @AvivYossef-starkware  on this? he is fixing this issue

I think it should probably fix itself during one the rebases, but if it doesn't, I'll fix it manually.


gradle: add jitpack.io support

allows to easily include new versions via gradle.
for example
https://jitpack.io/#Evisceration/AndroidSwipeLayout/0734b92f88
you can grab the library's state from any commit if you supply the short hash of the commit or also check out tags and releases you push.
makes it way easier for you, as you do not need to push to maven manually :)

This'll be handy to add into my fork while I wait for approval, thanks! :D


Exception when combining jqueryui draggable with ui-sortable

I'm combining ui-sortable with jqueryui draggable widget,
the basic concept is that i have two lists one of them is sortable and the other list isn't but its items are draggable with connectToSortable option linked to the first list.
When i drag an item from the unsortable list and drop it on the sortable one, console logs this error:
Uncaught TypeError: Cannot read property 'length' of undefined (sortable.js line 52)

Any chance you can share some code?
Did you base your code on the example found in README? Did you just add a vanilla jquery-ui widget? Did you use an other directive for the draggable list?

I managed to solve it by converting the two lists to sortable then cancel sorting on the first list in stop event as explained in your sample (Draggable-Sortable like interaction)
It's working fine now, thanks for your great work ☺

Congrats :+1:
I'm glad it worked for your use case.


"Production" Docker Image

This PR satisfies the auto-build functionality desired in #722 without changing anything in the docker folder.  This allows development and testing to continue to build and use images locally, but external users get a very lean Docker image they can use.  The size difference is appreciable.
REPOSITORY                     TAG                 IMAGE ID            CREATED             SIZE
lnd                            latest              3634dcf5df68        17 seconds ago      1.19GB
lnd-single                     latest              b295cc248447        30 minutes ago      56MB

Right before merging this PR, an Automated Build repository should be configured on the appropriate account (lightningnetwork?) on Docker Hub with the name of lnd in order to match documentation.
I see there are already some repositories created, however I think best practice for Docker is to have a single repository and different tags for different architectures.  The included image is based off of Alpine, but in the future we could extend into multiple Dockerfiles (example: ARM support, or being Ubuntu based).
So in this proposed scenario, lightningnetwork/lnd:latest would be alpine, but lightningnetwork/lnd:ubuntu would be an ubuntu-based image, for example.
(With thanks to @alingenhag for https://github.com/f-u-z-z-l-e/docker-lnd/ from which I borrowed heavily)

I think the changes of this PR are great and the use of a builder image and the resulting tiny production image with all the options exposed as environment variables is fantastic!
But something does not look right with your commit history. Especially the two merge commits at the beginning are very strange. I think you need to properly rebase everything. Drop me a line over at Slack if you need assistance, I have the same username there.

I was doing something weird with my fork of lnd (PRing against master rather than checking out upstream), I've rebased the changes and squashed the commits, though they're not perfect as to what files were changed.

Just tested it out with 2 docker containers. Works great.

Agreed w.r.t re-creating all the arguments. I think as is, since we're using a CMD as an entrypoint, we should be able to pass the arguments directly?

I'm not in a spot to update the PR, but I did create tyzbit/lnd:alt-cmd for everyone to test that changes the command from lncli to lnd, which allows for this to work:
docker run --name testnet-neutrino tyzbit/lnd:alt-cmd --bitcoin.active --bitcoin.testnet --bitcoin.node=neutrino --neutrino.connect=faucet.lightning.community

I will update the PR as soon as I can, as long as there aren't any concerns.
This has the benefit of allowing literal commandline options or environment variables, whichever the user prefers.

Per discussion with @Roasbeef on IRC, updated PR to only allow command-line options.
Updated Docker documentation to reflect the change and also added some information about volumes.


 converted into newlines and later lost when converting to text

 Issue by yifan
Thu Jul 16 09:57:48 2020
Originally opened as https://github.com/codelucas/newspaper/issues/827

I have a few news websites, such as this one: https://www.sott.net/article/434715-The-American-friends-New-court-files-expose-Sheldon-Adelsons-security-team-involved-in-US-spy-operation-against-Julian-Assange
The issue may be a bit more complicated than what I describe. In OutputFormatter.get_formatted, after replace_with_text(), newlines added by add_newline_to_br() disappeared. I might need to investigate it further.

it was a more complicated issue (fixing it opened a new can of worms)
fixed in 0.9.2 with a major rework of the parsing algorithm


Crash when doing project-wide search

Check for existing issues

[X] Completed

Describe the bug / provide steps to reproduce it
When doing a project-wide search for the term footnotes, Zed crashes. See crash log.
Environment
Zed: v0.85.4 (stable)
OS: macOS 13.3.1
Memory: 32 GiB
Architecture: aarch64
If applicable, add mockups / screenshots to help explain present your vision of the feature
No response
If applicable, attach your ~/Library/Logs/Zed/Zed.log file to this issue.
If you only need the most recent lines, you can run the zed: open log command palette action to see the last 1000.
No response

I put this into our internal issue tracker's triage queue.


"undefined method `webpack_asset_paths" in test environment

Hi, I am trying to run rspec/capybara/poltergeist tests and I get this error. However the app works in the browser in development environment. Any idea? It's a new app, not much code yet.
Thanks in advance.

Ehm...oops...I added the gem to the :development group of the Gemfile :p


brew tap-pin errors unnecessarily when a tap is already pinned

Please note we will close your issue without comment if you delete, do not read or do not fill out the issue checklist below and provide ALL the requested information. If you repeatedly fail to use the issue template, we will block you from ever submitting issues to Homebrew again.

[X] are reporting a bug others will be able to reproduce and not asking a question. If you're not sure or want to ask a question do so on our Discourse: https://discourse.brew.sh
[X] ran a brew command and reproduced the problem with multiple formulae? If it's a problem with a single, official formula (not cask) please file this issue at Homebrew/homebrew-core: https://github.com/Homebrew/homebrew-core/issues/new. If it's a brew cask problem please file this issue at https://github.com/caskroom/homebrew-cask/issues/new. If it's a tap (e.g. Homebrew/homebrew-php) problem please file this issue at the tap.
[X] ran brew update and can still reproduce the problem?
[X] ran brew doctor, fixed all issues and can still reproduce the problem?
[ ] ran brew config and brew doctor and included their output with your issue?

To help us debug your issue please explain:

What you were trying to do (and why)

brew tap-pin foo/bar from an Ansible playbook

What happened (include command output)

It's fine the first run obviously, but subsequent runs fail because brew tap-pin fails with an error if the tap is already pinned.

What you expected to happen

As with brew tap foo/bar, running the command multiple times just succeeds because the work was already done previously. IMHO multiple brew tap-pin foo/bar commands should also succeed.

Step-by-step reproduction instructions (by running brew commands)

brew tap foo/bar
brew tap-pin foo/bar
brew tap-pin foo/bar

Many Homebrew commands throw errors when run multiple times. I'd rather not get into changing exit codes at this point as it's more likely to break existing scripts. We'd consider accepting a PR so e.g. brew tap-pin with no arguments outputs the currently pinned taps.

Fair enough. FWIW, there is already brew tap --list-pinned 🙂


DDG360

Capture internal reason for changes.
@scoen @sjacob @yetti @jrixon @josephcurtis @shuangzhou

SonarQube analysis reported 408 issues

 23 major
 381 minor
 4 info

Top 10 issues

 Work.java: This file has 2,006 lines, which is greater than 1,000 authorized. Split it into smaller files.
 Work.java#L324: Add the missing @deprecated Javadoc tag.
 Work.java#L328: Add the missing @deprecated Javadoc tag.
 Work.java#L332: Add the missing @deprecated Javadoc tag.
 Work.java#L336: Add the missing @deprecated Javadoc tag.
 Work.java#L1346: Rename this class.
 Work.java#L1347: "mapper" is the name of a field in "Impl".
 Work.java#L1365: Make this anonymous inner class a lambda (sonar.java.source not set. Assuming 8 or greater.)
 Work.java#L1366: Add the "@Override" annotation above this method signature
 Work.java#L1503: Rename this method; there is a "private" method in the parent class with the same name.

Build finished.


Quiet Console Logs

Comments out two console logs. They seem to print on every single page/tab, making debugging js difficult.

Fixes #11


Enable fastAdditionMode by default

Description
Enable fast addition mode by default.
Make sure you've done all the following (You can delete the checklist before submitting)

[ ] Apply the AndroidStyle.xml style template to your code in Android Studio.
[ ] Code is well documented
[ ] Include unit tests for new functionality
[ ] All user-visible strings are made translatable
[ ] Code passes Travis builds in your branch
[ ] If you have multiple commits please combine them into one commit by squashing them.
[ ] Read and understood the contribution guidelines .

LGTM

Thanks @raphael0202 :-)


placement of braces with \mathscr vs. \scr and other codes

The placement of braces in MathJax appears to make a difference in \mathscr vs. \scr, \mathfrak vs. \frak, and \mathcal vs. \cal.   See https://jsfiddle.net/4nfo1joa/
It looks as thought \scr has to be encased in outer grouping braces to contain it properly: {\scr P}.  If it isn't set up this way, then all the lowercase letters that follow in the string come out as Roman and all the uppercase letters inherit the script.  \scr{P} doesn't keep the target isolated the way {\scr P} does.   The same pattern occurs with \mathfrak vs. \frak.  Almost the same thing happens with \cal: if it isn't coded as {\cal P}, then all the uppercase variables inherit the calligraphic setting, but the lowercase variables go to italic.
Is this expected behavior for these commands or a bug?

I thought that's expected behavior but I admit I don't know how one usually does \scr in actual TeX.
@dpvc ?

These are how those macros are supposed to work.  The macros like \cal (and \rm, \bf, \it, etc.) are Plain TeX macros, which work as switches:  they change the current font until another change is made.  In contrast, the macros \mathcal (and \mathrm, \mathbf, \mathit, etc.) are LaTeX macros, and they take arguments that are typeset in the given font.  In Plain TeX, one does {\cal P} to get a calligraphic "P", while in LaTeX it is \mathcal{P}.
In the early days of TeX, computers war much slower, and passing arguments incurred a certain performance cost, so many Plain TeX marcros work like these switches .  Typesetting large sections of text in a particular font by passing the text as an argument would have been prohibitively slow.  Nowadays, this is no longer a concern, but in the late 1970's, that was important.
There is also a technical issue concerning the timing of when TeX decides what category reach input token belongs to.  This is done when the token is first parsed, and that means that when an argument is passed to a macro, all the category codes have already been set for the tokens in the argument.  Since some macros work by changing the way category codes are assigned, using arguments could disrupt the ability of this macros to function.  So macros that may work over large sections of text (like font changes) are better handled by not using arguments.  This usually doesn't affect mathematical expressions, which are relatively short, but since \rm, \bf, etc., are used for text as well as mathematics, their use as switches rather than macros taking arguments was a reasonable decision.
When LaTeX was built on top of TeX, Lamport tried to normalize the syntax somewhat, and moved to arguments for everything, for consistency.  Bur the original Plain TeX macros are supported in MathJax, as well as the newer LaTeX ones.


Partial match previous search terms in streams page.

Before in a query string like:
“all, s, verona”
It would only strong match the first two terms, but now it’ll partial
string match all terms equally.

Automated message from Dropbox CLA bot
@brockwhittaker, it looks like you've already signed the Dropbox CLA. Thanks!

Can you rebase this and add it to the new test for this feature?

It's up!

@brockwhittaker looks like you forgot to update the new test suite?  It fails the existing tests :).

Merged, thanks @brockwhittaker!


Require php-intl instead of crashing on IntlTimeZone

PHP 7.2 on Ubuntu does not have php7.2-intl installed by default.
With composer install there are no check for intl extension
and first page shows misleading error:

It is better to show warning during composer install
(or composer create-project):

So it would be easier to google, that the original problem could be solved with:
sudo apt-get install php7.2-intl

@javiereguiluz as discussed in the issue, that might not be the preferred way there.

@stof I'm afraid I don't understand your comment. Do you like the change proposed in this pull request?

@javiereguiluz in the issue, I suggested that this issue should be fixed in Twig-extensions instead, to keep it compatible with the polyfill, instead of requiring the extension in the demo.

Does this issue still exist for the latest version of the project on Ubuntu?

Seems to be solved :slightly_smiling_face: Thanks. Closing.

Tested with:
Ubuntu 20.04.2 LTS
PHP 7.4.3
Symfony 5.3.1
Symfony CLI version v4.25.4

Thank you for reporting it! ❤


Dapr communications

Hello everyone, glad to be here. I can say I am pretty new to dapr implemention. So here’s my scenario. I deployed dapr on a k8 cluster through dapr cli. Everything works fine all pods for dapr running. My deployment has the “dapr annotations” and I also have a dapr service created after deployment. The major issues I am having is best way to test and sure dapr is actually working and can talk to the needed microservices. When I try to call dapr service created : “curl http://dapr-service-name” I get “connection refused on port 80”
When I also try this: “curl http://dapr-service-name:3500” I still get “connection refused on port 3500”.  Am I missing something here or by daprization isn’t done right ?
Any help or guide will be really appreciated.
Regards,
Sadiq

If you're asking on how to debug a Dapr sidecar in your k8s cluster, I recommend you port-forward to a pod and then curl on http://localhost:3500.


407 Add test workflow for leapfrogai_ui

Adds a workflow for running the existing unit tests within the new UI.
Adds a workflow to scan for active secrets using trufflehog
Adds UI-focused linting checks to the existing lint workflow
Adds eslint and prettier to pre-commit checks

After the workflows were added, linting changes were applied to this PR to get the UI compliant with the linter/formatter

I disabled the 'no-unde' rule for eslint because Typescript is already checking for this and gives no errors.
Docs Reference: https://typescript-eslint.io/troubleshooting/#i-get-errors-from-the-no-undef-rule-about-global-variables-not-being-defined-even-though-there-are-no-typescript-errors

all lgtm pending @justinthelaw's feedback being resolved.

fix conflicts then lgtm


[Docs] is there a single quick start guide documentation to deploy tvm on multiple cpus with some examples?

I want to try TVM in a multi node setup (possibly two machines and I have cpus), is there a quick start guide for end to end deployment with examples (doing simple model inference using those systems), Please point me to those documents if they already exists?

Please use https://discuss.tvm.apache.org/


Type mismatch Text after following readme

When installing Obelisk on Ubuntu 16.04 by following the instructions in the readme (installing Obelisk in the nix-env, and using hub) the command ob run gives the following error when it tries to build the frontend.
frontend/src/Frontend.hs:18:23: error:
• Couldn't match expected type ‘text
   <IP_ADDRESS>@text<IP_ADDRESS>-1cn50juu89QSL9QkUVcRY:Data.Text.Internal.Text’
              with actual type ‘T.Text’
  NB: ‘T.Text’
        is defined in ‘Data.Text.Internal’
            in package<EMAIL_ADDRESS>      ‘text-<IP_ADDRESS>@text-<IP_ADDRESS>-1cn50juu89QSL9QkUVcRY:Data.Text.Internal.Text’
        is defined in ‘Data.Text.Internal’
            in package<EMAIL_ADDRESS>• In the second argument of ‘($)’, namely ‘T.pack commonStuff’
  In the second argument of ‘($)’, namely ‘text $ T.pack commonStuff’
  In a stmt of a 'do' block: el "p" $ text $ T.pack commonStuff

I am not sure where to start searching for the issue so unfortunately I haven't tried anything to solve it yet.

Hi @SebastianCallh!  That looks to me like something that could be caused by other Haskell dependencies kicking around in ~/.cabal or ~/.ghc.  Could you try moving those out of the way (e.g. rename to .cabal.old and .ghc.old) and see if that fixes it?

Hi @ryantrinkle! Thank you for that amazingly fast answer.
Ok, right, we don't want Obelisk to use global dependencies but the ones in the local nix environment. I renamed those directories, bu running ob run again after renaming those gives the very vague error
<interactive>:10:1: error:
  parse error on input ‘$’
  Perhaps you intended to use TemplateHaskell

Do you know where the code that triggers this is? I once again am not sure where to start looking.

@luigy Any idea where this could be coming from?

Hi @luigy! Running the example app with your changes did indeed solve the problem.
Thank you for the quick response and keep up the amazing work with Reflex!

@SebastianCallh Looks like this should be closed out.  Thanks for trying things out and giving us all the feedback!


fix documentation to show that the default number of async threads is 64

What has changed:

updated documentation to reflect the fact that the default number of async threads is now 64 (as opposed to 30)

Why

The default number of async threads was bumped to 64 from 30 in this pull requests;

https://github.com/rabbitmq/rabbitmq-server/pull/212
https://github.com/rabbitmq/rabbitmq-server/pull/704

Thank you.

you are welcome


onlyExistingGroup(groupId) onlyGroupAdmin(groupId) can be reduced to onlyGroupAdmin(groupId)

Describe the improvement you're thinking about
onlyExistingGroup(groupId) onlyGroupAdmin(groupId) checks that a group exists and the msg.sender is the group admin. Just checking for onlyGroupAdmin(groupId) is sufficient for this case as a group exists only when the group has a non-zero admin. Thus, if we ensure msg.sender is the admin, we implicitly ensure that the admin is non-zero.
One of the many places where the 2 modifiers are used together: https://github.com/semaphore-protocol/semaphore/blob/v4.0.0-beta.1/packages/contracts/contracts/base/SemaphoreGroups.sol#L61
Additional context
PSE audit

Assigned to @zkfriendly


Fix missing $ in the second form of the tap! macro

I was trying to check what a length_value! parser was doing, and ended up turning this
fields: length_value!(be_u16, fielddesc) ~ // fields

into this
 len: tap!(d: be_u16 => { println!("got {} fields", d) }) ~
 fields: count!(fielddesc, len as usize) ~ // fields

but got the following error
<nom macros>:11:33: 11:34 error: unresolved name `f`. Did you mean `i`? [E0425]
<nom macros>:11 tap ! ( $ i , $ name : call ! ( f ) => $ e ) ; ) ;

This pull request fixes the (trivial) issue.

Thank you for catching this! Testing all of the macro alternatives is cumbersome, so I miss them sometimes


[IMPROVEMENT] RTL support

Hi,
Currently, I have to reorder adapter items to make RTL view.

It's done on the latest version. Thanks.


Clarification about using the "modules download cache" instead of vendoring

The 012_modvendor intro includes this statement vis-a-vis vendoring:

In a modules world, the module download cache can be used as a higher fidelity source of module dependencies.

That sentence is a bit of a mind-blower.  I'm unclear about how it can be higher fidelity; it seems that either the result of go mod vendor is correct or it isn't.
On the off chance that other folks are also confused, it'd be great if you can expand on the topic a bit.  If you can clue me in I can write it up and PR it if that's easier for you.
Thanks!

@hartzell "fidelity" is indeed the wrong word here with respect to a "clean" go mod vendor. The result of go mod vendor is a strict subset of the contents of the module download cache's zip file for the same module.
However, the point I was trying to convey here is that it's also quite easy for the contents of vendor to get outdated/modified etc. And unless you have suitable CI checks in place, you can't be sure it's identical to a clean go mod vendor, or the module download cache. Hence "higher fidelity".
This will, however, change with https://github.com/golang/go/issues/33848

Ahhh.
Repeating back to see if I understand, the issue is that the module cache is updated every time go build (or many of the other commands) is run, whereas the vendor cache is only updated when someone explicitly invokes go mod vendor.
Do you think there's any point in updating 012_modvendor, or am I a rare duck?
I ran into golang/go#33848 separately (in the same research spree that led me here) and I'm enthusiastic about making vendoring a first class citizen.
Thanks!

Repeating back to see if I understand, the issue is that the module cache is updated every time go build (or many of the other commands) is run, whereas the vendor cache is only updated when someone explicitly invokes go mod vendor.

Exactly.

Do you think there's any point in updating 012_modvendor, or am I a rare duck?

It might be worth it, although at some point we have to draw a line between how much detail we go into vs creating a neat summary. There are so many nuances of all this stuff... we could write a book!

Lets see if anyone else stumbles on this issue and says "Me too!".    I'll bet that https://github.com/golang/go/issues/33848 lands first.

Sounds good. Thanks for raising for discussion in any case.


Fix Tracers.wrap to keep MDC up to date

Previously, even though Tracer.getTraceId() would get propagated correctly across threads when one used Tracers.wrap, the generated logs would still not have a traceId set.

This change is

Thanks for your interest in palantir/http-remoting, @cjjojoba! Before we can accept your pull request, you need to sign our contributor license agreement - just visit https://cla.palantir.com/ and follow the instructions. Once you sign, I'll automatically update this pull request.

closing in favour of https://github.com/palantir/http-remoting/pull/440

You also have to modify the prepareForDeferredProcessing method.
On Jun 14, 2017, at 02:09, Grace Wang <notifications<EMAIL_ADDRESS>wrote:
@gracew commented on this pull request.

In tracing/src/main/java/com/palantir/remoting2/tracing/Tracers.java[github.com]https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_palantir_http-2Dremoting_pull_434-23discussion-5Fr121827051&d=DwMCaQ&c=izlc9mHr637UR4lpLEZLFFS3Vn2UXBrZ4tFb6oOnmz8&r=Vp81aOxWZvuVgVK_wp-VF3pIYG92B19LcCw6XKeYC0U&m=QA-GsBSRpF9SJ_5U_doz71fp9GvG98qdxjPtZ6P8I6Q&s=emtZI3qoToO0U5gupe_cT5KM5tYbexW2C2OSvDUeg3M&e=:

         Tracer.setTrace(trace);

       MDC.put(MDC_KEY, trace.getTraceId());

hm, Converter is invoked on the async thread, so you don't have access to the thread-local storage anymore and you're pretty much limited to what's in the ILoggingEvent =/
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub[github.com]https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_palantir_http-2Dremoting_pull_434-23discussion-5Fr121827051&d=DwMCaQ&c=izlc9mHr637UR4lpLEZLFFS3Vn2UXBrZ4tFb6oOnmz8&r=Vp81aOxWZvuVgVK_wp-VF3pIYG92B19LcCw6XKeYC0U&m=QA-GsBSRpF9SJ_5U_doz71fp9GvG98qdxjPtZ6P8I6Q&s=emtZI3qoToO0U5gupe_cT5KM5tYbexW2C2OSvDUeg3M&e=, or mute the thread[github.com]https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_notifications_unsubscribe-2Dauth_AAp3Q5K2I6ucCxdaG3bYNVImHUZ2YMh9ks5sDyRMgaJpZM4NlOl3&d=DwMCaQ&c=izlc9mHr637UR4lpLEZLFFS3Vn2UXBrZ4tFb6oOnmz8&r=Vp81aOxWZvuVgVK_wp-VF3pIYG92B19LcCw6XKeYC0U&m=QA-GsBSRpF9SJ_5U_doz71fp9GvG98qdxjPtZ6P8I6Q&s=HfK-J6i-vplqYJiIFW5PNu0lpx-rer_HKWFc8JYHKTk&e=.


Charts default period settings does not work

Steps:

Go to "Settings"
Click on "Default parameters"
Select "6 last months" (or anything else but "All times") in the "Chart: default period" dropdown
Click on any other settings tab, for example "Bank accounts"
Click on "Default parameters" again

What I expect:

The "Chart: default period" dropdown value is "6 last months"
When I navigate to "Graphics", every chart (category + balance) is displayed for the 6 last months only

What happens:

The "Chart: default period" dropdown value is still "All times"
When I navigate to "Graphics" the dropdown value is "6 last months" BUT:
For the "by category" chart there are the last 6 months + the current month (ie. march to september as today)
For the account balance and the differences charts, I have values since the beginning (2012)

Thanks! However, the balance chart doesn't have a dropdown, so you can't select a period there, that's a different issue (and a feature request more than a bug). You're right that the setting is wrongly displayed though, but fortunately the fix is easy...

Ok ! Not a problem for the balance, I just wanted to be clear enough :).

Fixed as https://github.com/bnjbvr/kresus/commit/8aee977d4c58afbd91753494a2553758bc4d1c3f for the wrong value in the default setting dropdown.

As for the other issue (last 3 months charts include the current month + last 3 months), I think it's actually useful to keep as is. Whether the current month should be included or not is unclear to me. The only strange part is that one asks for the last 3 months chart and sees 4 months, but other than that, it looks pretty reasonable.

I agree: the current month might be useful, I only included it in my
description to be sure that was intended.
Le mar. 8 sept. 2015 23:38, Benjamin Bouvier<EMAIL_ADDRESS>a
écrit :

As for the other issue (last 3 months charts include the current month +
last 3 months), I think it's actually useful to keep as is. Whether the
current month should be included or not is unclear to me. The only strange
part is that one asks for the last 3 months chart and sees 4 months, but
other than that, it looks pretty reasonable.
—
Reply to this email directly or view it on GitHub
https://github.com/bnjbvr/kresus/issues/189#issuecomment-138711078.

Yeah, sorry if my tone was a bit rough, it was quite late and I was merely thinking out loud :) This is something weird for sure, maybe having a toggle "include current month" would make it clearer...