Разбор json в Го выдал ошибку invalid character 'Â'
поскольку был NBSP пробел который появился при копировании из доков.
Найдите его тут:
{
"user": {
}
}
Разбор json в Го выдал ошибку invalid character 'Â'
поскольку был NBSP пробел который появился при копировании из доков.
Найдите его тут:
{
"user": {
}
}
The go build -gcflags -S internal/utils/str.go 2> test.s
worked i.e. the stdout was empty and the stderr needs to be redirected 2> test.s
.
Use the mcedit test.s
to see asm.
I'll try the https://github.com/loov/lensm
go install --tags nox11 loov.dev/lensm@main
sudo apt install libwayland-dev libvulkan-dev libegl-dev libxkbcommon-dev libxfixes-dev
go install --tags nox11 loov.dev/lensm@main
lensm -watch -filter Fibonacci lensm
```
func CopyDir(srcDir string, dstDir string) error { | |
err := os.CopyFS(dstDir, os.DirFS(srcDir)) | |
return err | |
} |
**maintainer-script-needs-depends-on-adduser** | |
You postinst script creates a user by using the adduser command that technically may not be installed yet in the system | |
**Fix:** | |
Add to the `debian/control`: | |
Pre-Depends: adduser | |
debmake -u 1.0.0 -n | |
# remove useless files | |
rm -fr ./debian/tests/ ./debian/upstream/ ./debian/README.Debian ./debian/watch | |
# now edit all the files inside of the debian folder | |
# from the debian/control in the Build-Depends remove the gcj | |
debuild # build a package |
certtool --generate-privkey --key-type=ed25519 --outfile privkey.pem | |
certtool --generate-self-signed --load-privkey privkey.pem --outfile cert.pem | |
certtool --p7-detached-sign --load-certificate cert.pem --load-privkey privkey.pem --infile msg.txt --outfile msg.txt.p7s | |
certtool --p7-info --infile msg.txt.p7s | |
certtool --p7-verify --load-certificate cert.pem --infile msg.txt.p7s --load-data msg.txt |
package main | |
import ( | |
"context" | |
"sync" | |
"time" | |
) | |
func main() { | |
serverReadyCond := sync.NewCond(&sync.Mutex{}) |
### SQS send | |
POST http://sqs.us-east-1.localhost.localstack.cloud:4566/000000000000/example-topic?Action=SendMessage | |
Content-Type: multipart/form-data; boundary=WebAppBoundary | |
Accept: application/json | |
--WebAppBoundary | |
Content-Disposition: form-data; name="MessageBody" | |
Content-Type: application/json | |
{ |
Signed-off-by: certifies that you wrote it or otherwise have the right to pass it on as a open-source patch. Specifically, that you agree to the Developer's Certificate of Origin
Acked-by: If a person was not directly involved in the preparation or handling of a patch but wishes to signify and record their approval of it then they can arrange to have an Acked-by: line. Acked-by: does not necessarily indicate acknowledgement of the entire patch.
Tested-by: A Tested-by: tag indicates that the patch has been successfully tested (in some environment) by the person named. This tag informs maintainers that some testing has been performed, provides a means to locate testers for future patches, and ensures credit for the testers.
Reviewed-by: A Reviewed-by tag is a statement of opinion that the patch is an appropriate modification without any remaining serious technical issues. Any interested reviewer (who has done the work) can offer a Reviewed-by tag for a patch.
Also we have **Co-developed-by: