Permission Denied Error

Describe the bug:

▶ fyne-cross linux -arch="*"
[i] Target: linux/amd64
[i] Cleaning target directories...
[✓] "bin" dir cleaned: /home/abhisek/go/src/my-app/fyne-cross/bin/linux-amd64
[✓] "dist" dir cleaned: /home/abhisek/go/src/my-app/fyne-cross/dist/linux-amd64
[✓] "temp" dir cleaned: /home/abhisek/go/src/my-app/fyne-cross/tmp/linux-amd64
[i] Checking for go.mod: /home/abhisek/go/src/my-app/go.mod
[✓] go.mod found
[i] Building binary...
failed to initialize build cache at /go/go-build: mkdir /go/go-build: permission denied
[✗] exit status 1

▶ fyne-cross windows -arch="*"
[i] Target: windows/amd64
[i] Cleaning target directories...
[✓] "bin" dir cleaned: /home/abhisek/go/src/my-app/fyne-cross/bin/windows-amd64
[✓] "dist" dir cleaned: /home/abhisek/go/src/my-app/fyne-cross/dist/windows-amd64
[✓] "temp" dir cleaned: /home/abhisek/go/src/my-app/fyne-cross/tmp/windows-amd64
[i] Checking for go.mod: /home/abhisek/go/src/my-app/go.mod
[✓] go.mod found
2023/02/18 12:02:09 could not create the rc file: open /app/fyne-cross/tmp/windows-amd64/main.rc: permission denied
[✗] could not package the Fyne app: exit status 1

To Reproduce:
Steps to reproduce the behaviour:

Go to 'command line'
Run the command the given commands
See error

Device and debug info (please complete the following information):
Device info

OS:  Linux
Version:  Ubuntu 20.04.5 LTS
Go version:  1.19.2
fyne-cross version:  v1.3.0
Fyne version:  v2.3.1

Debug info

▶ fyne-cross linux -no-cache -debug
[i] Target: linux/amd64
command.Context{Volume:volume.Volume{binDirHost:"/home/abhisek/go/src/my-app/fyne-cross/bin", cacheDirHost:"/home/abhisek/.cache/fyne-cross", distDirHost:"/home/abhisek/go/src/my-app/fyne-cross/dist", tmpDirHost:"/home/abhisek/go/src/my-app/fyne-cross/tmp", workDirHost:"/home/abhisek/go/src/my-app"}, Architecture:"amd64", Engine:command.Engine{Name:"docker", Binary:"/usr/bin/docker"}, Env:map[string]string{"CC":"gcc", "GOARCH":"amd64", "GOOS":"linux"}, ID:"linux-amd64", LdFlags:[]string(nil), OS:"linux", Tags:[]string(nil), AppBuild:"10", AppID:"com.abhisekp.rqipxmlgenerator", AppVersion:"1.0.0", CacheEnabled:false, DockerImage:"docker.io/fyneio/fyne-cross:1.3-base", Icon:"Icon.png", Name:"MY_APP", Package:".", Release:false, StripDebug:true, Debug:true, Pull:false, Category:"", Certificate:"", Developer:"", Keystore:"", KeystorePass:"", KeyPass:"", Password:"", Profile:""}
[i] Cleaning target directories...
[✓] "bin" dir cleaned: /home/abhisek/go/src/my-app/fyne-cross/bin/linux-amd64
[✓] "dist" dir cleaned: /home/abhisek/go/src/my-app/fyne-cross/dist/linux-amd64
[✓] "temp" dir cleaned: /home/abhisek/go/src/my-app/fyne-cross/tmp/linux-amd64
[i] Checking for go.mod: /home/abhisek/go/src/my-app/go.mod
[✓] go.mod found
[i] Building binary...
/usr/bin/docker run --rm -t -w /app -v /home/abhisek/go/src/my-app:/app:z -u 1003:1003 --entrypoint fixuid -e CGO_ENABLED=1 -e GOCACHE=/go/go-build -e CC=gcc -e CGO_LDFLAGS=-w -s -e GOOS=linux -e GOARCH=amd64 docker.io/fyneio/fyne-cross:1.3-base go build -trimpath -o /app/fyne-cross/bin/linux-amd64/MY_APP -v .
fixuid: fixuid should only ever be used on development systems. DO NOT USE IN PRODUCTION
fixuid: updating user 'docker' to UID '1003'
fixuid: updating group 'docker' to GID '1003'
fixuid: recursively searching path /
fixuid: chown /home/docker
fixuid: chown /home/docker/.bash_logout
fixuid: chown /home/docker/.bashrc
fixuid: chown /home/docker/.profile
internal/unsafeheader
internal/goarch
internal/goos
internal/goexperiment
internal/itoa
internal/cpu
runtime/internal/atomic
runtime/internal/syscall
math/bits
unicode/utf8
internal/race
internal/abi
runtime/internal/math
runtime/internal/sys
sync/atomic
unicode
image/color
container/list
crypto/internal/subtle
crypto/subtle
crypto/internal/boring/sig
internal/bytealg
math
unicode/utf16
vendor/golang.org/x/crypto/cryptobyte/asn1
internal/nettrace
vendor/golang.org/x/crypto/internal/subtle
encoding
fyne.io/fyne/v2/internal/color
golang.org/x/image/colornames
golang.org/x/net/html/atom
golang.org/x/text/encoding/internal/identifier
golang.org/x/text/internal/utf8internal
github.com/go-text/typesetting/di
golang.org/x/image/math/f64
golang.org/x/sys/internal/unsafeheader
runtime
github.com/benoitkugler/textlayout/fonts
internal/reflectlite
sync
internal/testlog
internal/singleflight
math/rand
runtime/cgo
errors
sort
internal/oserror
path
io
vendor/golang.org/x/net/dns/dnsmessage
strconv
crypto/internal/nistec/fiat
syscall
golang.org/x/text/internal/tag
strings
bytes
hash
hash/crc32
crypto
reflect
crypto/internal/randutil
crypto/rc4
vendor/golang.org/x/text/transform
golang.org/x/text/transform
bufio
net/http/internal/ascii
regexp/syntax
hash/adler32
golang.org/x/text/encoding
golang.org/x/text/runes
time
internal/syscall/unix
internal/syscall/execenv
image
golang.org/x/text/encoding/internal
golang.org/x/text/encoding/charmap
golang.org/x/text/encoding/japanese
golang.org/x/text/encoding/korean
regexp
image/internal/imageutil
image/draw
internal/poll
io/fs
context
golang.org/x/image/vector
golang.org/x/text/encoding/simplifiedchinese
embed
internal/fmtsort
encoding/binary
os
golang.org/x/text/encoding/traditionalchinese
golang.org/x/text/encoding/unicode
github.com/benoitkugler/textlayout/fonts/glyphsnames
image/jpeg
golang.org/x/image/draw
crypto/internal/nistec
crypto/cipher
crypto/internal/edwards25519/field
fmt
io/ioutil
crypto/internal/boring
crypto/des
crypto/aes
crypto/sha512
crypto/internal/edwards25519
crypto/hmac
crypto/md5
crypto/sha1
crypto/sha256
log
compress/flate
math/big
encoding/hex
encoding/base64
internal/godebug
net/url
path/filepath
vendor/golang.org/x/crypto/chacha20
internal/intern
encoding/pem
net/netip
vendor/golang.org/x/crypto/internal/poly1305
vendor/golang.org/x/sys/cpu
compress/gzip
vendor/golang.org/x/crypto/curve25519/internal/field
vendor/golang.org/x/crypto/hkdf
vendor/golang.org/x/text/unicode/bidi
vendor/golang.org/x/text/unicode/norm
vendor/golang.org/x/crypto/chacha20poly1305
vendor/golang.org/x/net/http2/hpack
vendor/golang.org/x/crypto/curve25519
net
mime
mime/quotedprintable
net/http/internal
encoding/json
vendor/golang.org/x/text/secure/bidirule
encoding/xml
golang.org/x/image/math/fixed
golang.org/x/net/html
github.com/srwiley/rasterx
vendor/golang.org/x/net/idna
crypto/rand
crypto/elliptic
crypto/internal/boring/bbig
encoding/asn1
crypto/ed25519
crypto/rsa
crypto/dsa
golang.org/x/text/internal/language
compress/zlib
github.com/benoitkugler/textlayout/fonts/binaryreader
github.com/benoitkugler/textlayout/fonts/psinterpreter
golang.org/x/image/ccitt
golang.org/x/image/tiff/lzw
image/png
vendor/golang.org/x/crypto/cryptobyte
crypto/x509/pkix
golang.org/x/image/tiff
github.com/benoitkugler/textlayout/language
github.com/goki/freetype/raster
github.com/benoitkugler/textlayout/unicodedata
crypto/ecdsa
golang.org/x/text/internal/language/compact
github.com/go-text/typesetting/language
golang.org/x/image/font
github.com/yuin/goldmark/util
github.com/go-gl/gl/v3.2-core/gl
github.com/goki/freetype/truetype
os/exec
golang.org/x/text/language
github.com/go-text/typesetting/segmenter
os/user
github.com/jsummers/gobmp
golang.org/x/text/encoding/htmlindex
github.com/goki/freetype
golang.org/x/net/html/charset
github.com/srwiley/oksvg
github.com/fyne-io/image/ico
github.com/go-gl/glfw/v3.3/glfw
os/signal
golang.org/x/sys/unix
golang.org/x/sys/execabs
net/textproto
crypto/x509
vendor/golang.org/x/net/http/httpguts
vendor/golang.org/x/net/http/httpproxy
mime/multipart
github.com/fredbi/uri
github.com/godbus/dbus/v5
crypto/tls
github.com/fsnotify/fsnotify
github.com/godbus/dbus/v5/introspect
fyne.io/systray/internal/generated/menu
fyne.io/systray/internal/generated/notifier
github.com/godbus/dbus/v5/prop
fyne.io/systray
net/http/httptrace
net/http
github.com/benoitkugler/textlayout/fonts/simpleencodings
fyne.io/fyne/v2
github.com/benoitkugler/textlayout/fonts/type1C
fyne.io/fyne/v2/internal/cache
fyne.io/fyne/v2/internal/svg
fyne.io/fyne/v2/driver/desktop
fyne.io/fyne/v2/storage/repository
fyne.io/fyne/v2/internal/async
fyne.io/fyne/v2/driver/mobile
fyne.io/fyne/v2/storage
fyne.io/fyne/v2/internal/driver
github.com/benoitkugler/textlayout/fonts/truetype
fyne.io/fyne/v2/internal/animation
fyne.io/fyne/v2/internal/app
fyne.io/fyne/v2/canvas
fyne.io/fyne/v2/data/binding
fyne.io/fyne/v2/theme
fyne.io/fyne/v2/internal/repository
fyne.io/fyne/v2/layout
fyne.io/fyne/v2/internal/widget
fyne.io/fyne/v2/internal
github.com/benoitkugler/textlayout/graphite
github.com/benoitkugler/textlayout/harfbuzz
github.com/go-text/typesetting/font
github.com/yuin/goldmark/text
github.com/go-text/typesetting/shaping
fyne.io/fyne/v2/internal/painter
github.com/yuin/goldmark/ast
github.com/yuin/goldmark/renderer
github.com/yuin/goldmark/parser
github.com/yuin/goldmark/renderer/html
github.com/yuin/goldmark
fyne.io/fyne/v2/widget
fyne.io/fyne/v2/container
fyne.io/fyne/v2/internal/painter/gl
fyne.io/fyne/v2/internal/driver/common
fyne.io/fyne/v2/internal/driver/glfw
fyne.io/fyne/v2/app
my-app
go build my-app: copying /tmp/go-build634998477/b001/exe/a.out: open /app/fyne-cross/bin/linux-amd64/MY_APP: permission denied
[✗] exit status 1

▶ fyne-cross windows -no-cache -debug
[i] Target: windows/amd64
command.Context{Volume:volume.Volume{binDirHost:"/home/abhisek/go/src/my-app/fyne-cross/bin", cacheDirHost:"/home/abhisek/.cache/fyne-cross", distDirHost:"/home/abhisek/go/src/my-app/fyne-cross/dist", tmpDirHost:"/home/abhisek/go/src/my-app/fyne-cross/tmp", workDirHost:"/home/abhisek/go/src/my-app"}, Architecture:"amd64", Engine:command.Engine{Name:"docker", Binary:"/usr/bin/docker"}, Env:map[string]string{"CC":"x86_64-w64-mingw32-gcc", "GOARCH":"amd64", "GOOS":"windows"}, ID:"windows-amd64", LdFlags:[]string{"-H=windowsgui"}, OS:"windows", Tags:[]string(nil), AppBuild:"11", AppID:"com.abhisekp.rqipxmlgenerator", AppVersion:"1.0.0", CacheEnabled:false, DockerImage:"docker.io/fyneio/fyne-cross:1.3-windows", Icon:"Icon.png", Name:"MY_APP.exe", Package:".", Release:false, StripDebug:true, Debug:true, Pull:false, Category:"", Certificate:"", Developer:"", Keystore:"", KeystorePass:"", KeyPass:"", Password:"", Profile:""}
[i] Cleaning target directories...
[✓] "bin" dir cleaned: /home/abhisek/go/src/my-app/fyne-cross/bin/windows-amd64
[✓] "dist" dir cleaned: /home/abhisek/go/src/my-app/fyne-cross/dist/windows-amd64
[✓] "temp" dir cleaned: /home/abhisek/go/src/my-app/fyne-cross/tmp/windows-amd64
[i] Checking for go.mod: /home/abhisek/go/src/my-app/go.mod
[✓] go.mod found
/usr/bin/docker run --rm -t -w /app/fyne-cross/tmp/windows-amd64 -v /home/abhisek/go/src/my-app:/app:z -u 1003:1003 --entrypoint fixuid -e CGO_ENABLED=1 -e GOCACHE=/go/go-build docker.io/fyneio/fyne-cross:1.3-windows /usr/local/bin/gowindres -arch amd64 -output MY_APP.exe -workdir /app/fyne-cross/tmp/windows-amd64
fixuid: fixuid should only ever be used on development systems. DO NOT USE IN PRODUCTION
fixuid: updating user 'docker' to UID '1003'
fixuid: updating group 'docker' to GID '1003'
fixuid: recursively searching path /
fixuid: chown /home/docker
fixuid: chown /home/docker/.bash_logout
fixuid: chown /home/docker/.bashrc
fixuid: chown /home/docker/.profile
2023/02/18 12:36:11 could not create the rc file: open /app/fyne-cross/tmp/windows-amd64/main.rc: permission denied
[✗] could not package the Fyne app: exit status 1

Does your user have write permission for the directory you are running in?

@andydotxyz Yes, /home/abhisek/go/src/my-app has the user permission because it's inside the home dir. And my app dir.
As evident, these dirs are cleaned.
[✓] "bin" dir cleaned: /home/abhisek/go/src/my-app/fyne-cross/bin/linux-amd64
[✓] "dist" dir cleaned: /home/abhisek/go/src/my-app/fyne-cross/dist/linux-amd64
[✓] "temp" dir cleaned: /home/abhisek/go/src/my-app/fyne-cross/tmp/linux-amd64

@andydotxyz the following error is from inside the container. Which directory does it map to in the host sytem?

Which directory does it map to in the host sytem?

The current directory, by default. Maybe your disk ran out of space? Or Docker is running as a user who cannot write to your files?
The clearing of old builds message isn't proof it can write, as if they were missing it wouldn't have to do anything.

This might be useful: https://stackoverflow.com/questions/48957195/how-to-fix-docker-got-permission-denied-issue#48957722

@andydotxyz  @Jacalz  My current user has all the permissions. And I'm able to run helloworld docker. But with fyne it throws this error.
This is the output of id command. As you can see 1003 the current user and while running docker, that user is given permission in the docker container. And obviously, my current user has the appropriate permissions.
▶ id
uid=1003(abhisek) gid=998(docker) groups=998(docker),27(sudo),139(libvirt),1003(abhisek)

My disk has a lot of space too
▶ df -h /
Filesystem      Size  Used Avail Use% Mounted on
/dev/sda9       122G  110G  6.8G  95% /

Can you please help me settings these things manually? I will create a custom docker and would like fyne-cross use that instead?

I think it is not a docker image problem, but that docker doesn't have access to your app subdirectory. You can try the following command to check:
/usr/bin/docker run --rm -t -w /app -v /home/abhisek/go/src/my-app:/app:z -u 1003:1003 --entrypoint fixuid -e CGO_ENABLED=1 -e GOCACHE=/go/go-build -e CC=gcc -e CGO_LDFLAGS=-w -s -e GOOS=linux -e GOARCH=amd64 docker.io/fyneio/fyne-cross:1.3-base mkdir -p /app/fyne-cross/bin/linux-amd64/ && touch /app/fyne-cross/bin/linux-amd64/MY_APP

@Bluebugs This is the full output
▶ /usr/bin/docker run --rm -t -w /app -v /home/abhisek/go/src/my-app:/app:z -u 1003:1003 --entrypoint fixuid -e CGO_ENABLED=1 -e GOCACHE=/go/go-build -e CC=gcc -e CGO_LDFLAGS='-w -s' -e GOOS=linux -e GOARCH=amd64 docker.io/fyneio/fyne-cross:1.3-base sh -c "mkdir -p fyne-cross/bin/linux-amd64 && touch fyne-cross/bin/linux-amd64/MY_APP"

fixuid: fixuid should only ever be used on development systems. DO NOT USE IN PRODUCTION
fixuid: updating user 'docker' to UID '1003'
fixuid: updating group 'docker' to GID '1003'
fixuid: recursively searching path /
fixuid: chown /home/docker
fixuid: chown /home/docker/.bash_logout
fixuid: chown /home/docker/.bashrc
fixuid: chown /home/docker/.profile
touch: cannot touch 'fyne-cross/bin/linux-amd64/MY_APP': Permission denied

@Bluebugs  But this command works fine without the -u 1003:1003 --entrypoint fixuid
/usr/bin/docker run --rm -t -w /app -v /home/abhisek/go/src/my-app:/app:z -e CGO_ENABLED=1 -e GOCACHE=/go/go-build -e CC=gcc -e CGO_LDFLAGS='-w -s' -e GOOS=linux -e GOARCH=amd64 docker.io/fyneio/fyne-cross:1.3-base sh -c "mkdir -p fyne-cross/bin/linux-amd64 && touch fyne-cross/bin/linux-amd64/MY_APP"

A file is created properly.

My docker version
▶ docker -v
Docker version 20.10.22, build 3a2c30b

That's interesting. @lucor, I think you have a better knowledge here than I do, any guess what could be going on?

running in a project idx workspace. rootless docker. I had to do the following at various stages
chmod 777 -R fyne-cross/  # inside MY-APP-FOLDER
chmod 777 MY-APP-FOLDER # inside my home
chmod 777 -R /home/user/.cache/fyne-cross

This still results in
[i] Target: windows/amd64
[i] Cleaning target directories...
[✓] "bin" dir cleaned: /app/fyne-cross/bin/windows-amd64
[✓] "dist" dir cleaned: /app/fyne-cross/dist/windows-amd64
[✓] "temp" dir cleaned: /app/fyne-cross/tmp/windows-amd64
[i] Checking for go.mod: /home/user/myapp/MY-APP-FOLDER/go.mod
[✓] go.mod found
[i] Packaging app...
  adding: MY-APP-FOLDER.exe (deflated 47%)
[✗] rename /home/user/myapp/MY-APP-FOLDER/fyne-cross/tmp/windows-amd64/MY-APP-FOLDER.exe.zip /home/user/myapp/MY-APP-FOLDER/fyne-cross/dist/windows-amd64/MY-APP-FOLDER.exe.zip: permission denied

While last step failed, I still got the output zip file. This seems like docker shenanigans. fyne-cross's docker images are not properly doing the sub-uid/gid stuff. Maybe you guys are using rootful docker so doesn't get affected by these. I use podman (which is by default rootless) in my own pc, so can't provide more insight. But It has been my experience that people assume rootful docker when building container images and those images craps out when it doesn't have that whole rootful docker permissions.

We are definitely not supporting rootless docker. Only podman rootless is supported. Is that the case here, we are talking about rootless docker?

It could be that because your user isn't 1000 you are getting issues. I've had issues with docker container permissions before where containers only work if your uid is 1000.


[5.5] MassAssignmentException JSON error output not explicit for non-fillable fields

Laravel Version: 5.5.2
PHP Version: PHP 7.1.3 (cli) (built: Apr  4 2017 18:40:27) ( NTS )
Database Driver & Version: 10.1.19-MariaDB

Description:
When using Model::create, if a non-fillable field is used, an error is returned.
The standard HTML output tells it is a MassAssignmentException which is quite explicit.
However when expecting a JSON response, the error output is unclear. It looks like that:
{
    "message": "title",
    "file": "/Users/rgehan/Sites/laravel-preset-react/vendor/laravel/framework/src/Illuminate/Database/Eloquent/Model.php",
    "line": 237,
    "trace": [
        {
            "file": "/Users/rgehan/Sites/laravel-preset-react/vendor/laravel/framework/src/Illuminate/Database/Eloquent/Model.php",
            "line": 157,
            "function": "fill",
            "class": "Illuminate\\Database\\Eloquent\\Model",
            "type": "->",
            "args": [
                {
                    "title": "This is the title",
                    "content": "Etiam natoque fusce dis euismod dolor condimentum egestas parturient fermentum, sociis habitasse libero nam adipiscing cubilia scelerisque enim dignissim pulvinar, aliquam ad convallis in mollis quisque proin praesent."
                }
            ]
        },
        {
            "file": "/Users/rgehan/Sites/laravel-preset-react/vendor/laravel/framework/src/Illuminate/Database/Eloquent/Model.php",
            "line": 280,
            "function": "__construct",
            "class": "Illuminate\\Database\\Eloquent\\Model",
            "type": "->",
            "args": [
                {
                    "title": "This is the title",
                    "content": "Etiam natoque fusce dis euismod dolor condimentum egestas parturient fermentum, sociis habitasse libero nam adipiscing cubilia scelerisque enim dignissim pulvinar, aliquam ad convallis in mollis quisque proin praesent."
                }
            ]
        },

        ...

Nothing say in this error that it is a MassAssignmentException. The titlefield of the output is simply the field that is not fillable.
Steps To Reproduce:

Create a model with a field that is not fillable
Attempts to Model::create(['not_fillable_field' => 'abc', ...]); from a request with the header: Accept: application/json

Here's an attempt to make it look more informative: https://github.com/laravel/framework/pull/21043

Thanks 👍


Express not registering file changes

Version: v4.17.1

Platform: Windows x64

What steps will reproduce the bug?
Make changes to file
Run node index.js
The situation
I am developing a server running NodeJS with Express (v4.17.12), and every time I make a file change to a route, it's as if nothing happened. I try to restart the server multiple times but with no avail, it still won't register the changes.
What do you see instead?
File changes have no effect on the server, even after a server restart.
Additional information
This has happened on several other occasions.

Could you please share a project example so I can try to run it from my side?


Exclude Restore from NuGet Client Version Usage Stats

To get a more accurate picture of the NuGet client version usage, we should exclude Unknown and Restore operations from those stats.  I suspect (hope) that the reason 1.6 is so high on that list is because of nuget.exe-based package restores.

@xavierdecoster is this still relevant?

Nope


Reference to the non-existent class dwc:all in dwctermshistory.rdf and dwcterms.rdf

The dwcattributes:organizedInClass properties for the record level terms have the value "all", as in:
<dwcattributes:organizedInClass rdf:resource="all"/>

This XML syntax is interpreted such that the object of the triple is http://rs.tdwg.org/dwc/terms/all, a class that doesn't exist in DwC.  It's easier to see in Turtle, where the triple would render like this:
dwc:dataGeneralizations-2009-04-24 dwcattributes:organizedInClass dwc:all.

I suspect that the best solution is to just delete the
<dwcattributes:organizedInClass rdf:resource="all"/>

tags from the RDF/XML rather than trying to define some class that is a union of all Darwin Core classes.

Fixed in commit c4ae49504e15cb14a2a506c29d29c345afc3c542.


docs: support upload image to search icon

What problem does this feature solve?
easier to find icons.
What does the proposed API look like?
https://ant.design/components/icon-cn/

hhh. I will do that.

HI @wendellhu95. Is this feature in your plan? If not, can I implement this feature? :)

HI @wendellhu95. Is this feature in your plan? If not, can I implement this feature? :)

Appreciate it! Looking forward to you contribution. :heart:


Search for MedicationRequests with medication contained does not return correct results

Describe the bug
When a search is made to find a MedicationRequest with a certain Medication, the results will not return the correct MedicationRequest if the Medication is included as a contained resource. This is with IndexOnContainedResources set to true and using _contained=true.
To Reproduce
Steps to reproduce the behavior:

Enabled IndexOnContainedResources
Submit the following MedicationRequest resource

{
	"resourceType": "MedicationRequest",
	"contained": [
		{
			"resourceType": "Medication",
			"id": "med0312",
			"code": {
				"coding": [
					{
						"system": "http://snomed.info/sct",
						"code": "324689003",
						"display": "Nystatin 100,000 units/ml oral suspension (product)"
					}
				]
			}
		}
	],
	"identifier": [
		{
			"use": "official",
			"system": "http://www.bmc.nl/portal/prescriptions",
			"value": "12345689"
		}
	],
	"status": "completed",
	"intent": "order",
	"medicationReference": {
		"reference": "#med0312",
		"display": "Nystatin 100,000 u/ml oral suspension"
	}
}

Search with the following query: MedicationRequest?medication.code=http://snomed.info/sct|324689003&_contained=true
See no results

Expected behavior
Should return the MedicationRequest
Environment (please complete the following information):

HAPI FHIR Version: 6.9.5
OS: MacOS
Browser: chrome

Root cause:
Some search parameters include parenthetical expressions (e.g. (MedicationRequest.medication as Reference)). The leading ( was causing searches using parenthetical expressions to fail where the reference target was a contained resource. The culprit is in ReferenceChainExtractor#extractPaths(...) in QueryStack.java, which filters on startsWith without expecting any parentheses.

Nice diagnosis, @dmuylwyk


[WIP] auth: Force remove session cookies set on root domain for clients.

This will break the login loops for people who tried login using
github (social auth) and got stuck in endless login loops.
The issue of login loops has been reported to happen on Microsoft Edge
only.
For other browsers like Firefox or Chrome, people seemed to aparantly
get logged out of their sessions on realms (which are hosted on same
Zulip server) when they logged into another realm on same server
using github (social auth). Trying to login back into the realms from
which user got logged out worked fine.
This behaviour difference seems to orginate from the way browsers
arrange the list of cookies to be sent to the server in the headers.
Django seems to maintain the cookies in its Request Objects using
dictionaries with cookie name being used as a key. Therefore if
multiple cookies with same name were sent from browser Django would
retian only one of them and which cookie would be retained would
probably depend on the order they are parsed from the request
headers.
Chrome and Firefox seem to arrange cookies sent in request headers
according to expiry (ascending order). This behaviour makes
logging back in possible because now the expiry of the session
cookie for the subdomain would be greater than that of the cookie
setup by python-social-auth (which was set when user logged into
another realm before causing log outs in the first place).
Microsoft Edge doesn't seem follow the same pattern of arranging
cookies into the request headers. Instead it seems like it always
puts in the cookie setup on root domain at the end. This results
people getting stuck in login loops because no matter what one
may do, once the cookie on root domain is created it will endup
masking other session cookies.
Fixes: #9940.

@adnrs96 thanks for your hard work on this!  The places this involves changing are scary and difficult to test, and I think given the 2-week expiry behavior, I've decided to just not merge this (and the problem will go away in 2 weeks).  I already integrated the ROOT_SUBDOMAIN_ALIASES part.
Thanks again @adnrs96!


Continue standardising embeds

Code is not tested
I am sure I missed a lot of embeds

What is going on :notLikeCrawl:

wrong files lol


When can you put the project here?

Apologies for the delay. Please allow me a month to complete the cleanup.

Hi,
Sorry for the wait. I have cleaned and uploaded relevant codes. Feel free to ask any questions.
Kind regards


Opening new PS tab using the Plus button freezes the app

Environment
Windows build number: Microsoft Windows NT 10.0.19042.0
Windows Terminal version : 1.7.572.0 (Beta preview)

Steps to reproduce

Have PowerShell set as your default profile
Start the app and check you only have one PowerShell tab open
Click on the "+" button to open a new tab in your default profile
And the app not responds from now

Expected behavior
A PS tab opening normally
Actual behavior
App freezes for a few seconds and it automatically quits
Moreover, PS prompt does not show up

Enabled customizations

Unable to reproduce under same versions for OS and Windows Terminal. Try restarting your computer or checking Task Manager to see what resource usage is there including for Powershell and Terminal. Also check your profile settings. Is there anything there besides the defaults? If there is customizations to the profile, was it configured with the Settings UI or the settings.json?

Sorry, I just updated my issue

"App freezes for a few seconds and it automatically quits" this sounds a lot like the app crashes.
God I wish the bot listen to me. Can you try the steps in https://github.com/microsoft/terminal/issues/8287#issuecomment-733893742 ?

My Windows Feedback is here : https://aka.ms/AAbfjxq

"App freezes for a few seconds and it automatically quits" this sounds a lot like the app crashes.
God I wish the bot listen to me. Can you try the steps in #8287 (comment) ?

yeah clearly this is a crash

@DHowett I'm assigning you because I can't open feedback hub links anymore 😕

Okay I finally got access again. Feedbacks f583dce3-8df8-4cf4-992f-583b0f588591 and fa4c67a1-8881-4238-bc85-e7ac9d6a5230.  I did manage to find:
 "lineNumber": "430",
 "fileName": "E:\\BA\\1\\s\\src\\cascadia\\TerminalSettingsModel\\CascadiaSettingsSerialization.cpp",
 "hresult": "2147942402",
 "message": "Dynamic Profile Namespace: \"Windows.Terminal.Wsl\" -- E:\\BA\\1\\s\\src\\cascadia\\TerminalSettingsModel\\WslDistroGenerator.cpp(66)\\Microsoft.Terminal.Settings.Model.dll!00007FFD8C3E9960: (caller: 00007FFD8C3D03B1) Exception(1) tid(3364) 80070002 The system cannot find the file specified.\r\n",
 "module": "Microsoft.Terminal.Settings.Model.dll"

it's ERROR_FILE_NOT_FOUND'ing... wsl.exe? When opening a new tab? That doesn't make any sense. Maybe those logs are just the expected "couldn't load WSL, whatever, log it and move on" messages.
@cl-ement05 Could you share your whole settings.json? Do you have WSL installed? Or maybe any other PowerShell Core instances?
But then there's also a ERROR_BAD_FORMAT but there's no other context on that other than Terminal.Settings.Model.dll. Maybe there's a x64 powershell installed on a x86 machine? The first tab loads fine, so that's probably not it.

@cl-ement05 Could you share your whole settings.json?

Yes of course so here is my entire settings.json (I just removed the color schemes otherwise this file is 190 lines long) :
{
    "$schema": "https://aka.ms/terminal-profiles-schema",
    // Add custom actions and keybindings to this array.
    // To unbind a key combination from your defaults.json, set the command to "unbound".
    // To learn more about actions and keybindings, visit https://aka.ms/terminal-keybindings
    "actions":
    [
        // Copy and paste are bound to Ctrl+Shift+C and Ctrl+Shift+V in your defaults.json.
        // These two lines additionally bind them to Ctrl+C and Ctrl+V.
        // To learn more about selection, visit https://aka.ms/terminal-selection
        {
            "command":
            {
                "action": "copy",
                "singleLine": false
            },
            "keys": "ctrl+c"
        },
        {
            "command": "paste",
            "keys": "ctrl+v"
        },
        // Press Ctrl+Shift+F to open the search box
        {
            "command": "find",
            "keys": "ctrl+shift+f"
        },
        {
            "command": "exit",
            "keys": "ctrl+d"
        },
        // Press Alt+Shift+D to open a new pane.
        // - "split": "auto" makes this pane open in the direction that provides the most surface area.
        // - "splitMode": "duplicate" makes the new pane use the focused pane's profile.
        // To learn more about panes, visit https://aka.ms/terminal-panes
        {
            "command":
            {
                "action": "splitPane",
                "split": "auto",
                "splitMode": "duplicate"
            },
            "keys": "alt+shift+d"
        }
    ],
    "copyFormatting": "none",
    "copyOnSelect": false,
    "defaultProfile": "{574e775e-4f2a-5b96-ac1e-a2962a402336}",
    "profiles":
    {
        "defaults":
        {
            "acrylicOpacity": 0.6,
            "cursorShape": "underscore",
            "useAcrylic": true
        },
        "list":
        [
            {
                "commandline": "powershell.exe",
                "guid": "{61c54bbd-c2c6-5271-96e7-009a87ff44bf}",
                "hidden": true,
                "name": "Windows PowerShell"
            },
            {
                "commandline": "cmd.exe",
                "guid": "{0caa0dad-35be-5f56-a8ff-afceeeaa6101}",
                "hidden": false,
                "name": "Command Prompt"
            },
            {
                "guid": "{b453ae62-4e3d-5e58-b989-0a998ec441b8}",
                "hidden": false,
                "name": "Azure Cloud Shell",
                "source": "Windows.Terminal.Azure"
            },
            {
                "guid": "{574e775e-4f2a-5b96-ac1e-a2962a402336}",
                "hidden": false,
                "name": "PowerShell",
                "source": "Windows.Terminal.PowershellCore"
            }
        ]
    },
    "schemes":
    [
        {
            someColorScheme
        },
        {
            anotherColorScheme...
        }
    ],
    "tabSwitcherMode": "mru",
    "tabWidthMode": "equal",
    "theme": "system"
}

Do you have WSL installed? Or maybe any other PowerShell Core instances?

Well I have installed the WSL 2 update package
However I didn't enable neither WSL neither VM platform in Windows features (because I realized this would not be useful for me). So no WSL is not enabled but WSL2 pkg installed.
About PowerShell Core I don't releally understand you mean by this but I installed PS 7 (and I use it as my default profile)

About PowerShell Core I don't releally understand you mean by this but I installed PS 7 (and I use it as my default profile)

That's exactly what I meant. Interesting though. Does this bug repro with Windows Powershell, or PowerShell 7? Does it still repro if you remove the "commandline": "powershell.exe", from your Windows Powershell profile?

About PowerShell Core I don't releally understand you mean by this but I installed PS 7 (and I use it as my default profile)

Does this bug repro with Windows Powershell, or PowerShell 7?

This bug happens with both Powershell and newer PowerShell 7.
And well if I remove "commandline": "powershell.exe", from the Powershell profile (not the 7 one) PS simply does not start.. of course because of the missing commandline parameter. So I get an error code.

Well, that's weird though. defaults.json has the full path to powershell.exe in it, so removing it from your "Windows Powershell" profile should fall back to using that one.
What if you manually set the commandline to:
"commandline": "%SystemRoot%\\System32\\WindowsPowerShell\\v1.0\\powershell.exe",

?
Or maybe, a weird theory, what happens when you run wsl.exe? I know it's not actually set up, but I think the exe should still be in C:\Windows\system32

PowerShell

Well, that's weird though. defaults.json has the full path to powershell.exe in it, so removing it from your "Windows Powershell" profile should fall back to using that one.

Oh I am sorry actually yes when I remove the commandline parameter, PS still starts.

And well if I remove "commandline": "powershell.exe", from the Powershell profile (not the 7 one) PS simply does not start.. of course because of the missing commandline parameter. So I get an error code.

This was happening because I thought I had removed the commandline parameter by leaving the field blank in Settings. Now I truly removed it from the JSON file so yes defaults.json is loaded and PS prompt appears as expected.
Also, when setting commandline to "commandline": "%SystemRoot%\\System32\\WindowsPowerShell\\v1.0\\powershell.exe", PS successfully starts
WSL

Or maybe, a weird theory, what happens when you run wsl.exe? I know it's not actually set up, but I think the exe should still be in C:\Windows\system32

I didn't try to do this but you can be 100% sure it won't work since

No actually there is wsl.exe in system32. There is only a DLL named wslapi
wsl is not recognized by PS as command

First off, sorry we never looped back on this one earlier.

Also, when setting commandline to "commandline": "%SystemRoot%\\System32\\WindowsPowerShell\\v1.0\\powershell.exe", PS successfully starts

Well, seems to me that the issue here was that whatever powershell.exe that was on your path was _not actually powershell.exe. Whatever bad exe it was, it was getting started instead of the main system one.
If I'm reading this whole thread right, seems like this is fixed now, so I'm gonna close this out. Thanks!


experiment: bump candid tests

to see how many fail against master

Just doing some repo cleanup for better focussing on active work:
Closing PR as it seems inactive for a longer time. Please re-open if it is still relevant and after it has been updated with latest master changes.


V2 RoadMap

Hi, These are the features being targeted for V2

[ ] Multiple Selection - Allowing users to multiselect options. Just like ...
[ ]  as option  - Allowing to pass Views to options, this will allow users to have icons inside options
[ ] Slide the selection menu from Top or Bottom of screen ..

@stoffern @technology-studio-apiary
Thanks

How about a dropdown instead of a modal overlay?

Yeah Good question. But positioning is one hell of thing.
I have contributed at lot to https://github.com/alinz/react-native-dropdown.
But the problem is when we embed the component inside navigator or otherviews the top and left positions are relative to parent component.
So what I thought is to have a complete view for selection. It is easy UX wise too and also coding wise.
We can have that options too.

@gs-akhan Have you had chance to validate my sample for setSelectedText alternative through props ? Would you like me to create pull request for given approach?

@gs-akhan i will fix v2 by this week, just need to land a few things @ work

Cool. Create a branch we both can share the features and implement them
On Mon, May 15, 2017 at 7:07 PM, Kristoffer<EMAIL_ADDRESS>wrote:

@gs-akhan https://github.com/gs-akhan i will fix v2 by this week, just
need to land a few things @ work
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/gs-akhan/react-native-chooser/issues/22#issuecomment-301477056,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AFYnVuCQVuPYo_tzCjZAlnYT6z2Nwy3zks5r6FUogaJpZM4NaKPK
.

@rostislav-simonik  I havent. will do it tonight.

@gs-akhan Ok, thanks, let me now then and  I'll do a more clean proposal.

@gs-akhan can you add me as collaborator on NPM?
Also activate Travis on the repo 😉
I am starting with v2 now

Sure sir !!
On Sun, 21 May 2017 at 1:03 PM, Kristoffer<EMAIL_ADDRESS>wrote:

@gs-akhan https://github.com/gs-akhan can you add me as collaborator on
NPM?
Also activate Travis on the repo 😉
I am starting with v2 now
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/gs-akhan/react-native-chooser/issues/22#issuecomment-302920506,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AFYnVtSNx--LkqKotljrQbOSeSS2B4wwks5r7-i6gaJpZM4NaKPK
.

@stoffern  What's your NPM profile name ?

https://www.npmjs.com/~stoffern

added
direction (fromLeft, fromRight, fromTop, fromBottom)
and
renderButton={ currentValue => <Text>{'Current Value: ' + currentValue}</Text> }

Did You get access ?
On Sun, May 21, 2017 at 3:51 PM, Kristoffer<EMAIL_ADDRESS>wrote:

added
direction (fromLeft, fromRight, fromTop, fromBottom)
and
renderButton={ currentValue => {'Current Value: ' +
currentValue} }
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/gs-akhan/react-native-chooser/issues/22#issuecomment-302927785,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AFYnVpHzBQmksMUrqMMR8iZn3OpMiAPnks5r8BAtgaJpZM4NaKPK
.

Activated Travis
On Sun, May 21, 2017 at 3:53 PM, Azhar uddin<EMAIL_ADDRESS>wrote:

Did You get access ?
On Sun, May 21, 2017 at 3:51 PM, Kristoffer<EMAIL_ADDRESS>wrote:

added
direction (fromLeft, fromRight, fromTop, fromBottom)
and
renderButton={ currentValue => {'Current Value: ' +
currentValue} }
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/gs-akhan/react-native-chooser/issues/22#issuecomment-302927785,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AFYnVpHzBQmksMUrqMMR8iZn3OpMiAPnks5r8BAtgaJpZM4NaKPK
.

i feed we should remove sendting styles into the Select and rather let the user send custom components into it with styles..
This is for SelectButton and Options

passing it like this:
renderButton={ currentValue => <Text>{'Current Value: ' + currentValue}</Text> }
renderOptionItem = { ({value, text, index}) => <View key={index} style={{}}>{text}</View>}
renderOptionSeperator={ data => <View style={{height: 1, backgroundColor: 'black'}}></View>}

How would end API look like.. ? Are we getting rid of
Component then, and then replacing it with renderOptionItem ?
On Sun, May 21, 2017 at 5:18 PM, Kristoffer<EMAIL_ADDRESS>wrote:

passing it like this:
renderButton={ currentValue => {'Current Value: ' + currentValue} }
renderOptionItem = { ({value, text, index}) => {text}}
renderOptionSeperator={ data => <View style={{height: 1, backgroundColor: 'black'}}>}
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/gs-akhan/react-native-chooser/issues/22#issuecomment-302931808,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AFYnVucNuZGd-SLr_xaapY0SQkr9J5PXks5r8CSKgaJpZM4NaKPK
.

Ohh Got it. Lets accept styles. that should not be a worry.
On Sun, May 21, 2017 at 5:20 PM, Azhar uddin<EMAIL_ADDRESS>wrote:

How would end API look like.. ? Are we getting rid of
Component then, and then replacing it with renderOptionItem ?
On Sun, May 21, 2017 at 5:18 PM, Kristoffer<EMAIL_ADDRESS>wrote:

passing it like this:
renderButton={ currentValue => {'Current Value: ' + currentValue} }
renderOptionItem = { ({value, text, index}) => {text}}
renderOptionSeperator={ data => <View style={{height: 1, backgroundColor: 'black'}}>}
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/gs-akhan/react-native-chooser/issues/22#issuecomment-302931808,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AFYnVucNuZGd-SLr_xaapY0SQkr9J5PXks5r8CSKgaJpZM4NaKPK
.

Passing Component would be little too much to do for users. I think so
On Sun, May 21, 2017 at 5:27 PM, Azhar uddin<EMAIL_ADDRESS>wrote:

Ohh Got it. Lets accept styles. that should not be a worry.
On Sun, May 21, 2017 at 5:20 PM, Azhar uddin<EMAIL_ADDRESS>wrote:

How would end API look like.. ? Are we getting rid of
Component then, and then replacing it with renderOptionItem ?
On Sun, May 21, 2017 at 5:18 PM, Kristoffer<EMAIL_ADDRESS>wrote:

passing it like this:
renderButton={ currentValue => {'Current Value: ' + currentValue} }
renderOptionItem = { ({value, text, index}) => {text}}
renderOptionSeperator={ data => <View style={{height: 1, backgroundColor: 'black'}}>}
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/gs-akhan/react-native-chooser/issues/22#issuecomment-302931808,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AFYnVucNuZGd-SLr_xaapY0SQkr9J5PXks5r8CSKgaJpZM4NaKPK
.

It's a normal practise to do in React

Let's go with it .. once it is all done we will see if we can make it even
simpler
On Sun, 21 May 2017 at 5:49 PM, Kristoffer<EMAIL_ADDRESS>wrote:

It's a normal practise to do in React
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/gs-akhan/react-native-chooser/issues/22#issuecomment-302933328,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AFYnVgtBswr6MO2vNKE3KufMdYNu3RORks5r8CvsgaJpZM4NaKPK
.

@gs-akhan @stoffern Hi guys, what about the change I has been proposing. The one which substitutes setSelectedText with props logic?

@rostislav-simonik i am rewriting the Select totally, into v2.
There will be no setSelectText 😉

@gs-akhan how do you want to solve the multiple select?
What should the user do after he has selected multiple items?

@rostislav-simonik  Yeaah your concerns are taken care by @stoffern 's fix.
@stoffern
So the API for multiselect should be based of prop multiple = true just like we have in HTML Select tag.
And selected values should be as array of options selected.

Yes, but when is the user done selecting?

yes. That should be ok.
You have any suggestions ?
On Mon, May 22, 2017 at 5:05 PM, Kristoffer<EMAIL_ADDRESS>wrote:

Yes, but when is the user done selecting?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/gs-akhan/react-native-chooser/issues/22#issuecomment-303075064,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AFYnVkutfCiyS-VxnDxqTw4D6VzISfg_ks5r8XLxgaJpZM4NaKPK
.

Then er need a "done" button?

No, we can close the menu my tapping anywhere outside. the will trigger
"close" dropdown
On Mon, May 22, 2017 at 5:11 PM, Kristoffer<EMAIL_ADDRESS>wrote:

Then er need a "done" button?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/gs-akhan/react-native-chooser/issues/22#issuecomment-303076337,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AFYnVmwgpYdhCrHQ8O71OLLNVMBQXLsiks5r8XRygaJpZM4NaKPK
.

Ok, that will be the last piece in the puzzle..

done

I think "Searching options" should be a v3..
Lets keep changes to a minimum in v2 and making it compatible for upgrades..

Perfect.  I am good with that..  Is every thing committed to v2 branch ?
On Mon, May 22, 2017 at 6:45 PM, Kristoffer<EMAIL_ADDRESS>wrote:

I think "Searching options" should be a v3..
Lets keep changes to a minimum in v2 and making it compatible for
upgrades..
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/gs-akhan/react-native-chooser/issues/22#issuecomment-303096513,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AFYnVgCSUbmzTYnHQLTi6_uwCHJZLvDgks5r8YpdgaJpZM4NaKPK
.

yup, needs some testing..
I will fix Travis testings and README.md + MIGRATION.md later today

I can test tonight from that branch ..
On Mon, May 22, 2017 at 7:08 PM, Kristoffer<EMAIL_ADDRESS>wrote:

yup, needs some testing..
I will fix Travis testings and README.md + MIGRATION.md later today
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/gs-akhan/react-native-chooser/issues/22#issuecomment-303102418,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AFYnVm3uvQ1Z3LUwc0fOOPvbBNf6hUTWks5r8Y-7gaJpZM4NaKPK
.

@gs-akhan I realize this is a few months old by now but do you still have plans to release v2?

@rtman  Yes we would like you. The thing is we need some beta testers who can validate if its working well. If you wish to help it. we can make a release.
Thanks

@gs-akhan
Hey I'm willing to test it in my app, I can't guarantee I can help too much in any debug but I can report what is happening. My time is a bit limited at the moment since I am developing full time with a deadline looming.

@rtman  Absolutely yes sir. :)

Back from a longer vacation 😉 what is the status of v2 ? 😄

Should i continue on this one?

Yes.. with full force
On Fri, Dec 8, 2017 at 1:17 PM, Kristoffer<EMAIL_ADDRESS>wrote:

Should i continue on this one?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/gs-akhan/react-native-chooser/issues/22#issuecomment-350196594,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AFYnViM9pNSIrO9wZhYa_np_bTbgzR_wks5s-OmugaJpZM4NaKPK
.


Fix document collection Add button

Work for Zendesk ticket: https://govuk.zendesk.com/tickets/1127310
The Add button for collection documents gets covered up by the Reorder groups button if:

a document collection group heading is long
the browser width is reduced

This PR moves the Reorder groups button out of the Add form. @fofr also suggested a copy change for the Add document form.
Before:

Can't see Add button:

Move reorder button outside of Add document form:

LGTM when tests pass.


Fix permissions of /app folder for sqlite in docker

I am trying to run sqlite in docker and was getting the same error as shown in issue #526. The app user does not own the /app directory, and so the it cannot create/open the sqlite file that sits in there. This isn't an issue when using postgres/mysql, but it is when you use a file based db.
This PR sets the /app directory's owner to app, so that the running user can modify the sqlite file

Disregard, This looked like it worked, but there was some other environmental thing that made it look like it made a difference. What I ended up having to do, was specifying the user (app) and voluming to the /data directory (which is owned by app)
My full docker-compose.yml for anyone that has the same issue:
version: "3.7"

services:
  wakapi:
    image: ghcr.io/muety/wakapi:latest
    ports:
      - 3000:3000
    restart: always
    environment:
      # See README.md and config.default.yml for all config options
      WAKAPI_DB_NAME: "/data/wakapi_db.db"
      WAKAPI_DB_USER: "wakapi"
      WAKAPI_DB_PASSWORD: "YOUR PASSWORD"
      ENVIRONMENT: "prod"
    user: app
    volumes:
      - ./data:/data


Add new mod: madkamel.TidalGrove

Closes #784
https://github.com/MadKamel/madkamel.TidalGrove

I've got a more recent version 0.3 committed and released. Will I have to do anything to get the package updated in the database, or not?


minor fixes to pass go vet checks

Currently, make check reports lot of issues, this PR is part of fix to make current code compatible with go vet  check.
This is partial fix  to resolve issues #578
Signed-off-by: Kunal Kushwaha<EMAIL_ADDRESS>

Unfortunately, this PR breaks a whole bunch of stuff. I am going to close it.

Sorry for this bad PR.
Will look into it again and discuss.

@kunalkushwaha No worries. This is the problem with automated linting.


Fixed docker image tag for "quay.io/prometheus/node-exporter".

The docker image tag for the node exporter ("quay.io/prometheus/node-exporter") was not valid so I changed it to "v0.13.0".

Thanks 👍


Add support for exception analysis.

We've found cases where we used a Pervasives, atd, or yojson function without a proper try/catch, and it didn't hit us until it was in production, at which point the lack any meaningful stack traces in Async Reason meant that we had a challenging time tracking down the source.
This is made worse by the fact that our code base has grown into using the Result type, and there are still a few places that throw even in our own code. Now that we've grown to a certain size and experience, it'd be nice if we had a way of generating a TODO list to clean up all of these exceptions, and to know that they could never throw and escape the type system.

Thank you for bringing up this issue, and for our conversation about it.
Here are some preliminary notes for a possible design.
The goal is to guide the user towards progressively replacing exceptions by other mechanisms, such as option or result types.
In truly exceptional circumstances, you would want to just add annotations to acknowledge intentional uses of exceptions and what areas of code are affected by them.
If you use exceptions extensively, and want to continue doing so, this analysis won't be helpful.
Some design thoughts:

You need to opt into exception checking.
Any function that throws exceptions gives a warning.
An annotation is supported to acknowledge that the function throws (those) exceptions.
Even when a function is annotated, any user of that function that does not catch the exceptions will get a waring. Unless the user itself is annotated, and so on.
Enough knowledge needs to be made available somehow of what library functions throw what exceptions.

To test the ideas quickly, one could build an extremely simplified prototype that:

Operates at the level of individual value definitions, disregarding nesting.
Does not distinguish between kinds of exceptions.
Only checks if there is some occurrence of an exception-catching mechanism.

That rough first experiment would be very imprecise, but could give a feel for the process to follow when using such an analysis. Before the full analysis is built.

Progress here https://github.com/cristianoc/reanalyze/pull/29
And here https://github.com/cristianoc/reanalyze/pull/32

https://github.com/cristianoc/reanalyze/pull/34

https://github.com/cristianoc/reanalyze/pull/35

@sgrove this is the first full-featured iteration, except it can't read annotations across files.
So if an annotation is added to A.re, and B.re uses A.re, then B.re will not see any annotations from A.

https://github.com/cristianoc/reanalyze/pull/36

https://github.com/cristianoc/reanalyze/pull/37

https://github.com/cristianoc/reanalyze/pull/38

https://github.com/cristianoc/reanalyze/commit/e2a82b0140c54c8b055393bad5a962a533dd518a

https://github.com/cristianoc/reanalyze/pull/39

A feature-complete version is in release 1.8.0
https://github.com/cristianoc/reanalyze/releases/tag/v1.8.0


Fix circleci timeout problem

As titled.

Is this ready to merge @chenghuzi?

Is this ready to merge @chenghuzi?

yes

I'd approve the rebase and merge myself but it only gives me the option to auto-merge. Any idea why this is @jasmainak?

I guess it's because "Linkcheck" is marked as a required test to pass ... we could change which tests are required but I suggest just fixing the linkcheck by ignoring the relevant link so we stop worrying about CIs once and for all

I guess it's because "Linkcheck" is marked as a required test to pass ... we could change which tests are required but I suggest just fixing the linkcheck by ignoring the relevant link so we stop worrying about CIs once and for all

Hmm, I don't recall encountering this before when the linkcheck broke. Maybe I just forgot though.
Huzi fixed the linkcheck in #596 and we're just waiting to merge this PR before merging the other.

okay I bypassed the branch protection rules for this PR

Thanks @chenghuzi !


able to run test code, but returns a blank page

i'm running the test demo provided in https://eth-ait.github.io/aitviewer/ and here is my code on my remote linux server:
from aitviewer.viewer import Viewer
from aitviewer.configuration import CONFIG as C

C.update_conf({'smplx_models':'/home/guoling/HOIs/all_body_models'})

if __name__ == '__main__':
    v = Viewer()
    v.scene.add(SMPLSequence.t_pose())
    v.run()

Meanwhile, I use the XQuartz for visualization, after running python test_viewer.py, the terminal returns:

and an aitviewer page pumps out, but the page is only a blank page like this:

I have tried many times, but it's always a blank page, my xeyes command can work and cv2.imshow can work too(when using opencv-python). I'm using opencv-python-headless version for aitviewer but it just doesn't work.
Hope someone can help, thanks a lot!

I am not entirely sure what your setup is here but I'm assuming you are trying to X forward the aitviewer output to your local machine from a Linux server? I have no experience with XQuartz unfortunately. You could try to swap the window type to pyglet instead of Qt, but I doubt that this will change anything:
from aitviewer.configuration import CONFIG as C
from aitviewer.viewer import Viewer
C.update_conf({"window_type": "pyglet"})
v = Viewer()
v.run()

Other than that I would simply avoid X forwarding and use the remote viewer capabilities to transfer data via TCP.


Changing a very long (4000s) deadline to 10s.

Updates  the release branch with a change that fixes the deb build on 32bit debian

this done in preparation for add a new release tag 0.10.2
this is needed so we can cut a debian backport package

Build Failure seems unrelated to PR. Hence merging.


Bink logo for showcasing

Thank you for your contribution to the IC Developer Portal.
Before submitting your Pull Request, please make sure that:

[ ] You have updated the .github/CODEOWNERS file according to your changes.
[ ] You have registered new documents to /sidebars.js if any.

Please don't add a logo to the repo root


Changing local variable's datatype is denied, causing Unable to use type for symbol ... message

Describe the bug
With a structure defined in the application's data segment (DS) and members of said structure also defined, accessing a defined member is causing an incorrect datatype to be assigned to the local variable that cannot be changed.  I.e.:
lVar1 = *(long *)&DgnInter_1028_0000_0x61_t_1078_11be.field2_0x6;
where field2_0x6 is of type DgnInter_1018_0d46_0x?_t *32 and the assembly is:
   1018:0d55 66 a1 c4 11  012           MOV        EAX,DS:[0x11c4]
Note the use of a single 32-bit register instead of two 16-bit ones.
To Reproduce
Steps to reproduce the behavior:

Load in the enclosed function (from the Decompile:Panels Debug Function Decompilation menu)
Try changing the datatype of lVar1
Observe the warning message
See error in that the datatype hasn't changed and the later else if statement (line 30) is still malformed

Expected behavior
The size of the register to load an address shouldn't:

Affect the automatic datatype detection
Stop manual overriding

Screenshots
N/A
Attachments
dgninter_FUN_1018_0d46.zip
Environment (please complete the following information):

OS: Windows 11
Java Version: Temurin-21.0.3+9
Ghidra Version: 11.2-DEV
Ghidra Origin: locally built (based upon commit 34ba255)

Additional context
This is a Protected-Mode 16-bit Windows NE EXE from a Borland C/C++ v 4.?? compiler.

In this case (where I'm assuming the application shares the stack SS and data DS segments), setting the SS to the same value as DS for the first assembly instruction where it is MOV <reg>, SS solves the issue.  Therefore I'll close this.


drawing with the menu hidden seems to still allow interaction with the menu

If I'm in drawing mode and press "m" to hide the menu, when clicking/dragging in the space where the menu options previously were, it seems my clicks are still being passed onto the menu items - e.g. if I click where "help" was and drag down it'll still select one of the help options, instead of registering as drawing.

This appears to be resolved.


pull request for e2e test at 01/28/2017 20:45:10

:white_check_mark: Validation status: passed
For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Invalid argument for string field 'name' (given String)

Very strange results when starting a workflow defined elsewhere. Minimal demo:
irb(main):001:0> require 'temporal'
=> true
irb(main):002:0> Temporal.start_workflow('HelloWorldWorkflow')
/Users/haim/Projects/personal/temporal-ruby/lib/temporal/connection/grpc.rb:89:in `initialize': Invalid argument for string field 'name' (given String). (Google::Protobuf::TypeError)
	from /Users/haim/Projects/personal/temporal-ruby/lib/temporal/connection/grpc.rb:89:in `new'
	from /Users/haim/Projects/personal/temporal-ruby/lib/temporal/connection/grpc.rb:89:in `start_workflow_execution'
	from /Users/haim/Projects/personal/temporal-ruby/lib/temporal/client.rb:49:in `start_workflow'

If I freeze this workflow name string or pass a symbol, it works as expected! E.g. this works:
Temporal.start_workflow('HelloWorldWorkflow'.freeze)

I see this happening with Ruby 3.0.2 and 2.6.5.
My dependencies are:
  specs:
    google-protobuf (3.19.1-x86_64-darwin)
    googleapis-common-protos-types (1.3.0)
      google-protobuf (~> 3.14)
    grpc (1.41.1-universal-darwin)
      google-protobuf (~> 3.17)
      googleapis-common-protos-types (~> 1.0)
    oj (3.13.9)

PLATFORMS
  x86_64-darwin-20

@haimgel sorry for a long delay, this somehow slipped through the cracks (feel free to ping us again if this ever happens again).
It's a nasty issue, glad that you've raised it. Here's a fix and an explanation — https://github.com/coinbase/temporal-ruby/pull/128

Wow, this is indeed a weird issue! Glad you were able to get to the bottom of it. I can confirm, it works fine now (in your branch).

@haimgel brilliant, thank you for confirming!
I've merged the PR and also reported the issue to Ruby devs, very curious what's their take on it


Docs: implement data-test-id query using helpers

What:

Why:

How:

Checklist:

[ ] Documentation
[ ] Tests
[ ] Ready to be merged

[ ] Added myself to contributors table

:tada: This PR is included in version 5.2.2 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


the headerView  flashed

when you add the chatItem to the list , the tableViewReload the headerView ,the flash will show it'state .

Just replace the MJRefresh In my demo. It's worth trying.


Configuration files for multi-year, high-topped, moist Held-Suarez

Linked Issue: #1991

Could we add a dry held suarez as well?

Yes - PR against issue 1990 is on the way.

Day 250, Level 1 (snapshot)
summary_1991_1_day250.pdf

bors r+

bors r-

bors r+

bors r+


[FEATURE] Add ARIA attributes to login and signup forms

Description
ARIA attributes are crucial for enhancing web application accessibility, benefiting users with disabilities. Currently, our forms lack these attributes, hindering proper interpretation by assistive technologies.
Some steps to implement this enhancement-

Identify the login and signup form elements in your codebase.
Determine the relevant ARIA attributes to add for each form element.
Add ARIA roles to the forms and their elements (e.g., "form" role for the main form element).
Include concise and descriptive ARIA labels using the aria-label attribute.
Use the aria-describedby attribute to provide additional instructions for the forms.
Implement ARIA states and properties (e.g., aria-required for required fields).
Test the accessibility improvements using assistive technologies.

Screenshots
No response
Additional information
No response

Please assign me this issue so that I can work on this issue under GSSOC'23.


Remove copyright notices

Nice! I like it.
Remove this as well https://github.com/keras-team/keras-hub/blob/master/shell/lint.sh#L23-L28
Dunno why we have no error descriptive error messages there, bad ux.


Update Nuget package for SpecFlow 2.2.0

Current Specflow.Unity is not compatible with Specflow 2.2.0, and when trying to use it with that version throws below exception

Message: OneTimeSetUp: System.TypeLoadException : Could not load type 'TechTalk.SpecFlow.Infrastructure.IBindingInstanceResolver' from assembly 'TechTalk.SpecFlow, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=0778194805d6db41'.

Will there be any upgrade in the library to support new version?

I'll do a new version shortly

That's done over my PR.

Guys, please do it already.

For the moment you can use directly from my branch :)

Hi victorsantoss
we are also getting same error IBindingInstanceResolver. Can you please let us know what is the fix for this issue.
Thanks & Regards,
Dharma Reddy B.

Hey Dharma,
I saw that my pull request (#4 ) was merged some weeks ago, it depends on @phatcher doing a new release over the nuget package.
After that everything will works great.

Hi
Thanks for the reply. Can you please let us know what are the changes do we
need to do.
Currently installed specflow version is 2.2.0
Do we need to do any code changes. If what are the changes?
Thanks
Dharma
On Dec 5, 2017 2:54 AM, "Victor Santos"<EMAIL_ADDRESS>wrote:

Hey Dharma,
I saw that my pull request (#4
https://github.com/phatcher/SpecFlow.Unity/pull/4 ) was merged some
weeks ago, it depends on @phatcher https://github.com/phatcher doing a
new release over the nuget package.
After that everything will works great.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/phatcher/SpecFlow.Unity/issues/3#issuecomment-349110460,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AQIV5kurkG_V5db-RohF7YBBvVRM6cUZks5s9GL_gaJpZM4OnUax
.

Whats the ETA on this release?


Fix fixture test annotation

@TomasVotruba this is to adapt with latest New release 4.15.1 https://github.com/nikic/PHP-Parser/releases/tag/v4.15.1, the Attribute replacement seems now start from the annotation starter indentation.

All checks have passed 🎉 @TomasVotruba it is ready for review.

:+1: