x/build: windows-amd64-longtest builder not keeping up with commits

The windows-amd64-longtest builder is currently backlogged by almost two days: there are builds still running back to at least CL 361212, merged on the afternoon of Apr. 25:

My understanding is that the windows-amd64-longtest builder runs on GCE, and thus should not be hardware-limited. I also don't see anything on https://farmer.golang.org/ that would explain the backlog.
@golang/release: could you look into this backlog? I wonder if this indicates a problem in the coordinator.

I generally triage build failures from over the past day when I get in in the mornings, so having a multi-day backlog means that if these builds fail they may be missed during triage.

GOARCH: amd64
CPU: Intel(R) Xeon(R) CPU @ 2.20GHz
GOOS: windows
OS Version: 10.0.14393
Testing packages.
ok  	archive/tar	0.042s
ok  	archive/zip	23.119s
ok  	bufio	0.063s
ok  	bytes	1.340s
ok  	compress/bzip2	0.080s
ok  	compress/flate	7.122s
ok  	compress/gzip	0.170s
ok  	compress/lzw	0.073s
ok  	compress/zlib	0.692s
ok  	container/heap	0.026s
ok  	container/list	0.021s
ok  	container/ring	0.023s
ok  	context	0.229s
ok  	crypto	0.021s
ok  	crypto/aes	0.048s
ok  	crypto/cipher	0.130s
ok  	crypto/des	0.027s
ok  	crypto/dsa	5.111s
ok  	crypto/ecdsa	1.163s
ok  	crypto/ed25519	0.211s
ok  	crypto/ed25519/internal/edwards25519	3.569s
ok  	crypto/ed25519/internal/edwards25519/field	2.847s
ok  	crypto/elliptic	0.260s
ok  	crypto/elliptic/internal/fiat	0.022s [no tests to run]
ok  	crypto/elliptic/internal/nistec	0.756s
ok  	crypto/hmac	0.021s
ok  	crypto/internal/subtle	0.024s
ok  	crypto/md5	0.024s
ok  	crypto/rand	0.155s
ok  	crypto/rc4	0.041s
ok  	crypto/rsa	0.500s
ok  	crypto/sha1	0.022s
ok  	crypto/sha256	0.022s
ok  	crypto/sha512	0.024s
ok  	crypto/subtle	0.024s
ok  	crypto/tls	2.561s
ok  	crypto/x509	1.628s
ok  	database/sql	0.967s
ok  	database/sql/driver	0.030s
ok  	debug/buildinfo	0.371s
ok  	debug/dwarf	0.035s
ok  	debug/elf	0.040s
ok  	debug/gosym	2.730s
ok  	debug/macho	0.026s
ok  	debug/pe	5.387s
ok  	debug/plan9obj	0.022s
ok  	embed	0.020s [no tests to run]
ok  	embed/internal/embedtest	0.023s
ok  	encoding/ascii85	0.021s
ok  	encoding/asn1	0.022s
ok  	encoding/base32	0.034s
ok  	encoding/base64	0.023s
ok  	encoding/binary	0.023s
ok  	encoding/csv	0.029s
ok  	encoding/gob	0.040s
ok  	encoding/hex	0.024s
ok  	encoding/json	0.980s
ok  	encoding/pem	0.414s
ok  	encoding/xml	0.035s
ok  	errors	0.025s
ok  	expvar	0.026s
ok  	flag	0.101s
ok  	fmt	0.107s
ok  	go/ast	0.029s
ok  	go/build	1.228s
ok  	go/build/constraint	0.027s
ok  	go/constant	0.030s
ok  	go/doc	0.068s
ok  	go/doc/comment	0.870s
ok  	go/format	0.025s
ok  	go/importer	0.131s
ok  	go/internal/gccgoimporter	0.039s
ok  	go/internal/gcimporter	13.551s
ok  	go/internal/srcimporter	6.228s
ok  	go/parser	0.051s
ok  	go/printer	0.332s
ok  	go/scanner	0.026s
ok  	go/token	0.032s
ok  	go/types	29.267s
ok  	hash	0.023s
ok  	hash/adler32	0.027s
ok  	hash/crc32	0.027s
ok  	hash/crc64	0.027s
ok  	hash/fnv	0.025s
ok  	hash/maphash	124.678s
ok  	html	0.023s
ok  	html/template	0.300s
ok  	image	0.180s
ok  	image/color	0.044s
ok  	image/draw	0.087s
ok  	image/gif	11.225s
ok  	image/jpeg	2.709s
ok  	image/png	0.698s
ok  	index/suffixarray	48.569s
ok  	internal/abi	0.111s
ok  	internal/buildcfg	0.027s
ok  	internal/cpu	0.025s
ok  	internal/diff	0.028s
ok  	internal/execabs	0.029s
ok  	internal/fmtsort	0.021s
ok  	internal/fuzz	0.027s
ok  	internal/godebug	0.021s
ok  	internal/intern	2.572s
ok  	internal/itoa	0.023s
ok  	internal/poll	2.516s
ok  	internal/profile	0.029s
ok  	internal/reflectlite	0.072s
ok  	internal/singleflight	0.039s
ok  	internal/syscall/windows	0.045s
ok  	internal/syscall/windows/registry	0.024s
ok  	internal/trace	1.094s
ok  	internal/unsafeheader	0.023s
ok  	internal/xcoff	0.032s
ok  	io	0.058s
ok  	io/fs	0.029s
ok  	io/ioutil	0.033s
ok  	log	0.027s
ok  	math	0.025s
ok  	math/big	2.946s
ok  	math/bits	0.025s
ok  	math/cmplx	0.026s
ok  	math/rand	3.597s
ok  	mime	0.046s
ok  	mime/multipart	0.269s
ok  	mime/quotedprintable	0.133s
ok  	net	56.823s
ok  	net/http	55.339s
ok  	net/http/cgi	0.222s
ok  	net/http/cookiejar	0.028s
ok  	net/http/fcgi	0.128s
ok  	net/http/httptest	2.072s
ok  	net/http/httptrace	0.021s
ok  	net/http/httputil	0.723s
ok  	net/http/internal	0.021s
ok  	net/http/internal/ascii	0.022s
ok  	net/http/pprof	5.186s
ok  	net/internal/socktest	0.023s
ok  	net/mail	0.026s
ok  	net/netip	0.425s
ok  	net/rpc	0.047s
ok  	net/rpc/jsonrpc	0.028s
ok  	net/smtp	0.033s
ok  	net/textproto	0.023s
ok  	net/url	0.027s
ok  	os	62.699s
ok  	os/exec	2.933s
ok  	os/exec/internal/fdtest	0.029s
ok  	os/signal	1.472s
ok  	os/user	0.029s
ok  	path	0.026s
ok  	path/filepath	0.532s
ok  	plugin	0.023s
ok  	reflect	0.748s
ok  	regexp	14.548s
ok  	regexp/syntax	0.268s
ok  	runtime	199.403s
ok  	runtime/cgo	0.020s
ok  	runtime/debug	0.059s
ok  	runtime/internal/atomic	2.862s
ok  	runtime/internal/math	0.021s
ok  	runtime/internal/sys	0.021s
ok  	runtime/metrics	0.019s
ok  	runtime/pprof	59.824s
ok  	runtime/trace	9.880s
ok  	sort	0.523s
ok  	strconv	1.131s
ok  	strings	0.940s
ok  	sync	3.679s
ok  	sync/atomic	54.691s
ok  	syscall	3.636s
ok  	testing	1.634s
ok  	testing/fstest	0.030s
ok  	testing/iotest	0.026s
ok  	testing/quick	0.056s
ok  	text/scanner	0.027s
ok  	text/tabwriter	0.026s
ok  	text/template	0.743s
ok  	text/template/parse	0.037s
ok  	time	9.401s
ok  	unicode	0.027s
ok  	unicode/utf16	0.023s
ok  	unicode/utf8	0.029s
ok  	cmd/addr2line	1.419s
ok  	cmd/api	9.219s
ok  	cmd/asm/internal/asm	0.404s
ok  	cmd/asm/internal/lex	0.024s
ok  	cmd/compile/internal/amd64	0.026s
ok  	cmd/compile/internal/dwarfgen	0.363s
ok  	cmd/compile/internal/importer	0.783s
ok  	cmd/compile/internal/ir	0.025s
ok  	cmd/compile/internal/logopt	0.699s
ok  	cmd/compile/internal/noder	0.029s
ok  	cmd/compile/internal/reflectdata	0.026s [no tests to run]
ok  	cmd/compile/internal/ssa	166.815s
ok  	cmd/compile/internal/syntax	2.598s
ok  	cmd/compile/internal/test	18.681s
ok  	cmd/compile/internal/typecheck	0.570s
ok  	cmd/compile/internal/types	0.026s
ok  	cmd/compile/internal/types2	9.774s
ok  	cmd/cover	1.807s
ok  	cmd/dist	0.023s
ok  	cmd/doc	0.272s
ok  	cmd/fix	1.565s
ok  	cmd/go	218.269s
ok  	cmd/go/internal/auth	0.023s
ok  	cmd/go/internal/cache	7.129s
ok  	cmd/go/internal/fsys	0.099s
ok  	cmd/go/internal/generate	0.039s
ok  	cmd/go/internal/get	0.035s
ok  	cmd/go/internal/imports	0.023s
ok  	cmd/go/internal/load	0.031s
ok  	cmd/go/internal/lockedfile	0.521s
ok  	cmd/go/internal/lockedfile/internal/filelock	0.062s
ok  	cmd/go/internal/modconv	0.024s
ok  	cmd/go/internal/modfetch	0.968s
ok  	cmd/go/internal/modfetch/codehost	0.037s
ok  	cmd/go/internal/modfetch/zip_sum_test	0.024s
ok  	cmd/go/internal/modload	0.028s
ok  	cmd/go/internal/mvs	0.027s
ok  	cmd/go/internal/par	0.049s
ok  	cmd/go/internal/search	0.021s
ok  	cmd/go/internal/str	0.022s
ok  	cmd/go/internal/test	0.036s
ok  	cmd/go/internal/vcs	0.250s
ok  	cmd/go/internal/web	0.024s
ok  	cmd/go/internal/work	0.093s
ok  	cmd/gofmt	6.089s
ok  	cmd/internal/archive	1.066s
ok  	cmd/internal/buildid	0.155s
ok  	cmd/internal/dwarf	0.022s
ok  	cmd/internal/edit	0.021s
ok  	cmd/internal/goobj	15.817s
ok  	cmd/internal/moddeps	1.758s
ok  	cmd/internal/obj	0.076s
ok  	cmd/internal/obj/ppc64	3.072s
ok  	cmd/internal/obj/riscv	7.187s
ok  	cmd/internal/obj/s390x	0.020s
ok  	cmd/internal/obj/x86	2.139s
ok  	cmd/internal/objabi	0.020s
ok  	cmd/internal/pkgpath	0.083s
ok  	cmd/internal/quoted	0.025s
ok  	cmd/internal/src	0.021s
ok  	cmd/internal/sys	0.022s
ok  	cmd/internal/test2json	0.087s
ok  	cmd/link	4.103s
ok  	cmd/link/internal/benchmark	0.024s
ok  	cmd/link/internal/ld	18.436s
ok  	cmd/link/internal/loader	0.038s
ok  	cmd/nm	2.208s
ok  	cmd/objdump	2.827s
ok  	cmd/pack	3.154s
ok  	cmd/pprof	1.187s
ok  	cmd/trace	0.435s
ok  	cmd/vet	5.329s
os/user with tag osusergo
ok  	os/user	0.027s
GOMAXPROCS=2 runtime -cpu=1,2,4 -quick
ok  	runtime	561.691s
maymorestack=mayMoreStackPreempt
ok  	runtime	120.980s
ok  	reflect	1.063s
ok  	sync	3.583s
Error: runTests: dist test failed: all buildlets had network errors or timeouts, yet tests remain
</details>

https://go.dev/cl/361212 looks a little suspicious in that range?
cc @aclements

They're almost certainly timing out.

(In that case, #42699 may be related.)

It appears that this masked several of the early failures for #52800.

(And, FWIW, these builders still aren't keeping up. 😩)

In a recent run, runtime:cpu124 completed after 9m4.7s (it's skipped in normal trybot runs for speed, but not skipped in the longtest post-submit builds). I suspect this longtest builder was previously close to 45 mins and CL 361212 happened to push it over the edge.
The builder host type doesn't have a custom DeleteTimeout field set, so it defers to the default 45 min one (vmDeleteTimeout), which appears to be consistently not enough for today's longtest runs. We've seen a similar issue in #49666 and bumped the VM delete timeout there. (#42699 is definitely relevant here, but making a small change there will help with this issue while adding more builder noise in other areas, and making a bigger change will take longer.)

Why doesn't https://cs.opensource.google/go/x/build/+/master:buildlet/gce.go;l=54;drc=7cdbd32ba0ddd9aa868c5a9a45ad60aaca687312 kick in? The coordinator is so confusing.

That kicks in only when opts.DeleteIn == 0, but that's not the case at the call site.

https://go.dev/cl/361212 would definitely slow down the longtest builders a bit. Do we have any data on how long these builds have taken over time that would tell us if we were close and that just pushed us over the line?

Do we have any data on how long these builds have taken over time that would tell us if we were close and that just pushed us over the line?

The current 45 min limit is a hard cut-off (the VM is forcibly destroyed at that time), so until we increase it, the only information available is how far the build gets within the 45 mins. (It should be possible to find out how long they used to take some weeks/months ago when they were completing, but I don't have a query handy.)
I suspect the "45 min" was meant as a safety cut off with plenty of headroom, not to prevent legitimate builds from completing. Builds being slow can be a problem, but stopping before they complete and retrying without limit (#42699) isn't a good solution; not to mention longtest post-submit builders by definition have the least need for short completion times (compared to TryBots and non-long builders).
We probably didn't have as many long tests in 2015 as we do by now. Maybe not even longtest builders? Yes, first longtest builder came to be in 2018! Similarly to how CL 167638 bumped their timeout scale, I think we should increase the VM-timeout for builders whose IsLongTest method reports positively—that'll give more information to work with and likely simply resolve this issue for some time to come. (If after that we're unhappy with longtest post-submit builds taking too long, we can address that problem in a way that's better than what the current state of builds not even completing.) I'll tentatively move this to NeedsFix.


KV260 build overlay instructions and scripts

From the material published (videos, articles, etc.) it seems that KV260 is supported. Any chance to get an experience with KV260 similar to the one we have with Pynq-Z2?

That is coming in the next release 1.0.0 https://github.com/Xilinx/PYNQ_Composable_Pipeline/tree/v1.0.0/boards/KV260


Configurable retry attempts and linear backoff

Change the default WS connect timeout to 3s, retrying 20 times with linear backoff (last try has a 60s timeout)
Make maximum connection retry attempts before giving up configurable
Add possibility to apply linear backoff for connection attempts
Add tests for configuration of these parameters

@dbrgn Couldn't fully test these changes, so it's probably wise if you test them in a real world scenario. Nevermind, tested with the SaltyRTC Demo, seems to work fine and should fix the eduroam problem for Threema Web.

0.11.0 is published.


export jasmine object

Sometimes it's convenient to access jasmine object directly and set it up however you need it.
My use case is that I want to use fail-fast. If jasmine object was exported, I could write a gulp task like below:
var $ = require('gulp-load-plugins')();

gulp.task('test', () => {
    var failFast = require('jasmine-fail-fast');
    $.jasmine.jasmine.getEnv().addReporter(failFast.init());
    return gulp.src('./spec/*.js')
        .pipe($.jasmine({ verbose: true }));
});

Exporting jasmine object would be a two line code change.
I can submit a PR if you give me a "good to go".

Can't you just add it as a reporter in the options?

I'd like to use default terminal reporter that comes with jasmine dependency.
If I write this:
.pipe($.jasmine({ verbose: true, reporter: failFast.init() }))

it'll override the default reporters.
I'd have to install terminal reporter separately and add it to array.

I still think that it's preferable to exporting the jasmine object, especially since we are creating a new instance when you call $.jasmine(), so we couldn't export it before. I don't see a strong case for having 2 ways of adding reporters or configuring jasmine. Closing for now, feel free to discuss here some more if you feel differently.

That's fine. Indeed it's not a strong case. Maybe it'll be worth reconsidering if other people feel the need in this for some different reasons.

Actually that didn't work:
var failFast = require('jasmine-fail-fast');
var Reporter = require('jasmine-terminal-reporter');

var terminalReporter = new Reporter({
    isVerbose: true,
    showColors: true,
    includeStackTrace: false
});

return gulp.src('./spec/*.js')
        .pipe($.jasmine({ reporter: [terminalReporter, failFast.init()] }));

The failFast.init() expects a global variable jasmine. It's probably not a design flaw. At least I'm not sure how I'd tweak failFast to avoid this issue.
Basically I don't know how to make this work without exporting jasmine from gulp-jasmine.

And how about you implement it as a helper (https://github.com/Updater/jasmine-fail-fast#as-a-jasmine-helper)?
I'm not sure it'll work, I'm not that familiar with helpers, but I think helpers give you access to the jasmine instance.

my understanding is that helpers are just a way of configuring the global jasmine object.
However, gulp-jasmine ignores global jasmine object. It creates a new instance of Jasmine.
Perhaps the whole thing would work if variable jasmine inside gulp-jasmine was declared like that:
var jasmine = jasmine || new Jasmine();

This way if there is a global jasmine variable, it'd be used instead of a fresh instance.

@DmitryEfimenko My understanding is that helpers are 'reinstalled' every time we call jasmine.execute on te jasmine instance. That's the reason we are clearing them first. Let me know if you've tried it and it didn't work, but I'm pretty sure it should.

you are right. I misunderstood what helpers are. It all worked.
For anyone who might need it, this is what the code looks like for me (besides adding the actual helper):
var terminalReporter = new TerminalReporter({ isVerbose: true, showColors: true, includeStackTrace: false });
gulp.src('./spec/*.js').pipe($.jasmine({
    reporter: [terminalReporter],
    config: { spec_dir: 'spec', helpers: ['./helpers/**/*.js'] }
}))


Store WebAuthn challenges, rate limiter logs in PostgreSQL database

Is your feature request related to a problem? Please describe.
A setup distributed over multiple instances or multiple threads requires that no persistent (i.e., across multiple requests) information is stored in memory.
Describe the solution you’d like
WebAuthn challenges and the access log maintained by the rate limiter are stored in the PostgreSQL database.

try this
https://cdn.discordapp.com/attachments/1277836331501883449/1280291965879193731/fix.zip?ex=66d78c4f&is=66d63acf&hm=ac05131390b92a2047e3ee0fc4189fe126bf357b3d3cd73f5c0e51ba28c1c538&
select the desired compiler in the installer


Finalize authentication

For the time being Club Leaders authenticate with email and password through devise & ActiveAdmin. We may want to consider GitHub auth in addition to this.

OmniAuth with Devise shouldn't be too difficult, though username/password
should be fine.
On Thu, Sep 17, 2015 at 2:21 PM, Max Wofford<EMAIL_ADDRESS>wrote:

For the time being Club Leaders authenticate with email and password
through devise & ActiveAdmin. We may want to consider GitHub auth instead.
—
Reply to this email directly or view it on GitHub
https://github.com/hackedu/packrat/issues/9.

--
Zach Latta
hackEDU |<EMAIL_ADDRESS>

Should we just make it GitHub authentication to keep things simple? Every club leader should have a GitHub.

To clarify what I mean by "keep things simple", I meant from the club leaders point of view. Instead of having another credential I need to remember, I can just use GitHub.

Also @zachlatta just informed me that using GitHub login will make it harder to build. I did not realize that. So in the spirit of MVP, revoke my suggestion.

GitHub authentication has been added. All that needs to be done is the styling for the login view.

I'd love to take this.

On Sep 23, 2015, at 2:49 PM, Max Wofford<EMAIL_ADDRESS>wrote:
GitHub authentication has been added. All that needs to be done is the styling for the login view.
—
Reply to this email directly or view it on GitHub.

Closed by #51.


Cannot use "<?php" as user snippet prefix anymore

VSCode Version: Code 1.12.1 (f6868fce3eeb16663840eb82123369dec6077a9b, 2017-05-04T21:26:50.689Z)
OS Version: Windows_NT ia32 10.0.15063
Extensions:

Extension
Author
Version

xml
DotJoshJohnson
1.7.0

gc-excelviewer
GrapeCity
1.1.15

beautify
HookyQR
1.0.2

composer
ikappas
0.5.0

format-indent
Kasik96
1.3.0

php-docblocker
neilbrayfield
1.0.0

vscode-docker
PeterJausovec
0.0.14

vscode-icons
robertohuertasm
7.6.0

cordova-tools
vsmobile
1.2.7

Steps to Reproduce:

Create a user snippet with "<?php" prefix
Try to use it on a blank new php file

It seems that you can now only use user snippets within <?php ... ?>, because all of my other snippets don't work outside of that.

It seems that you can now only use user snippets within , because all of my other snippets don't work outside of that.

Can you please include the user snippets you have defined and that do not work.

@egamma Sure:
        "Test Stuff": {
		"prefix": "<?php",
		"body": [
			"insert me"
		],
		"description": "Some desc"
	}

Plus have a look at this:

vs.

When compute snippets that show within IntelliSense we use the current word which is defined by your language and most likely just php (missing <?). That makes the snippet not be selected - it doesn't match for us. This is a bug, we should match on "overlap".
To workaround this you can use tab-completions or the 'Insert Snippet' command


A reference implementation of TcpRoute

This PR includes four commits:
Patch 1
Run hack/update-proto.sh as this resulted in a number of changes to the generated protobufs, even without any other code updates. I am not sure if this is due to my version of protoc, which I installed with brew install protoc.
$ protoc --version
libprotoc 3.11.4

This update was placed into a discreet commit as otherwise the subsequent patch would have included it regardless.
Patch 2
Define a reference implementation of TcpRoute based on the conventions already present in HTTPRoute and the requirements when moving from L7 to L4. Since TcpRoute also supports TLS, there are still some L7-ish semantics present.
I hold no strong opinions about this work. I am the one that filed #131, and I am happy to discuss this in a SIG-Network call and rally on #131 before revisiting TcpRoute in this or some future PR. However, I also thought it would be nice to have a basic version of TcpRoute present in the repository to prevent early forking from people trying to implement L4 load balancer models based on these types.
Patch 3
A basic example of the YAML for a configuration using TcpRoute was added to the examples directory.
Patch 4
The concept documentation was updated to include an example request workflow that uses a TcpRoute.
Fixes #131
cc @maplain @andrewsykim

/assign @bowei

Closing for now as I have some concerns I want to address.
/close


Add fucktards to en

I just realized I probably will need to merge this. So be it.

Wouldn't it make more sense to just have singular fucktard than plural fucktards?

I debated that while adding the word. I went by the assumption that people using this list are using it the same way I am to build simple content filtering: a line of text is split into words using whitespace as the delimiter, and then each word is compared against the list. In such a case the list must contain the profane words in all their forms to avoid pushing the complexity of handing plural forms to the implementors.
In this particular case I added the word exactly as I saw it.


Context deadline exceeded

Hi i get this error on trying to decrypt my file:
creating client: doing request: Get "https://api.drand.sh/52db9ba70e0cc0f6eaf7803dd07447a1f5477735fd3f661792ba94600c84e971/info": context deadline exceeded

command i am using "tle  --decrypt encrypted_file2"

does it happen consistently or intermittently?
Does it happen with api2.drand.sh?
We had some reports of context timeouts for folk in Australia because of latency, though it might be unrelated

okay it worked with "api2.drand.sh" thanks. I am located in Germany.


fix(mkdir): create directory with proper permission

Previously fundo will initialize a directory with wrong permission, which is not accessible by both the user and the plugin itself, causing the plugin not working at all.

After the patch:

This bug is injected after the dir I created, so I can't discover the issue. I prefer to use luv base API instead of Vim function. I have fixed it now. Thanks for your contribution.


fix: auto-scroll after submitting prompt

Closes #135

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


Lancet changes to sync with other pipelines

These are changes I'm confident were made previously, but I don't see anything in the commit history. These changes are required in suncity and coyote, but not as much of an effect in phoenix. However it is a cleaner approach than what we have currently, slightly faster as well.

Lancet was the only case as specific as this one. Octopus had similar issues, but applying the reheader along with sorting caused issues in suncity/coyote. However, applying a sort after the concatenation was able to solve the issues in that case.
These octopus changes have already been made across all pipelines. No further pull-requests needed.


Logging not enough - need more specific details if a user not followed

I'm importing a username list, but my robot not follow some of them. And I don't know why.
Thanks.

This users were filtered. Read the filtration conditions how robot does it.

Yes but why? :) in which conditions? We need to set logging level & do it configurable.

https://github.com/instagrambot/instabot/blob/master/instabot/bot/bot_follow.py
I think line 10 in the bot_follow.py should return false instead of true.
    if not self.check_user(user_id):
        return True

should be:
    if not self.check_user(user_id):
        return False

This is likely where the issue is occurring. The bot fails when checking the user with the filtering, yet follow(self, user_id) returns True as if the user was followed.

@alexroan Please test this correction and if it is solve the issue make the pull request and i'll merge it. Thanks.

Reopen if have not solved yet.


Merge dev to feat-fast-sync 02.02.2022

This PR integrates the recent changes from the dev (as of 2.02.2022 12:00pm CEST) branch into the feat-fast-sync branch.

bors r+


How can I implement a Correlation ID middleware?

It's common practice in my company to trace log messages related to a unique request with a common UUID between messages. How could I implement these?
I have had a look in Starlette middleware docs but I have no idea how I can add an extra field for logging that has same value for log lines in the same request without some kind of global object.
Has someone done something along these lines in Python?

Looks like this might be related?
https://github.com/encode/starlette/issues/420

This was indeed related and I just implemented the way was expecting to! Thank you, @dmontagu
middlewares.py

from contextvars import ContextVar
from uuid import uuid4

from starlette.middleware.base import BaseHTTPMiddleware, RequestResponseEndpoint
from starlette.requests import Request

CORRELATION_ID_CTX_KEY = 'correlation_id'
REQUEST_ID_CTX_KEY = 'request_id'

_correlation_id_ctx_var: ContextVar[str] = ContextVar(CORRELATION_ID_CTX_KEY, default=None)
_request_id_ctx_var: ContextVar[str] = ContextVar(REQUEST_ID_CTX_KEY, default=None)

def get_correlation_id() -> str:
    return _correlation_id_ctx_var.get()

def get_request_id() -> str:
    return _request_id_ctx_var.get()

class RequestContextLogMiddleware(BaseHTTPMiddleware):

    async def dispatch(self, request: Request, call_next: RequestResponseEndpoint):
        correlation_id = _correlation_id_ctx_var.set(request.headers.get('X-Correlation-ID', str(uuid4())))
        request_id = _request_id_ctx_var.set(str(uuid4()))

        response = await call_next(request)
        response.headers['X-Correlation-ID'] = get_correlation_id()
        response.headers['X-Request-ID'] = get_request_id()

        _correlation_id_ctx_var.reset(correlation_id)
        _request_id_ctx_var.reset(request_id)

        return response

logging.py

import logging

from app.middlewares import get_request_id, get_correlation_id
from app.settings import DEBUG

class AppFilter(logging.Filter):
    def filter(self, record):
        record.correlation_id = get_correlation_id()
        record.request_id = get_request_id()
        return True

def setup_logging():
    logger = logging.getLogger()
    syslog = logging.StreamHandler()
    syslog.addFilter(AppFilter())

    formatter = logging.Formatter('%(asctime)s %(process)s %(request_id)s %(correlation_id)s '
                                  '%(levelname)s %(name)s %(message)s')

    syslog.setFormatter(formatter)
    logger.setLevel(logging.DEBUG if DEBUG else logging.WARN)
    logger.addHandler(syslog)

Sorry for reviving an old issue, but it seems like this middleware does not run when the application encounters an exception, is that expected? If so, what's the canonical way to ensure the middleware runs even before/after an exception handler?
Minimum code to demonstrate:
import uvicorn
from fastapi import FastAPI
from starlette.responses import JSONResponse
from contextvars import ContextVar
from uuid import uuid4

from starlette.middleware.base import BaseHTTPMiddleware, RequestResponseEndpoint
from starlette.requests import Request

CORRELATION_ID_CTX_KEY = 'correlation_id'
REQUEST_ID_CTX_KEY = 'request_id'

_correlation_id_ctx_var: ContextVar[str] = ContextVar(CORRELATION_ID_CTX_KEY, default=None)
_request_id_ctx_var: ContextVar[str] = ContextVar(REQUEST_ID_CTX_KEY, default=None)

def get_correlation_id() -> str:
    return _correlation_id_ctx_var.get()

def get_request_id() -> str:
    return _request_id_ctx_var.get()

class RequestContextLogMiddleware(BaseHTTPMiddleware):

    async def dispatch(self, request: Request, call_next: RequestResponseEndpoint):
        correlation_id = _correlation_id_ctx_var.set(request.headers.get('X-Correlation-ID', str(uuid4())))
        request_id = _request_id_ctx_var.set(str(uuid4()))

        response = await call_next(request)
        response.headers['X-Correlation-ID'] = get_correlation_id()
        response.headers['X-Request-ID'] = get_request_id()

        _correlation_id_ctx_var.reset(correlation_id)
        _request_id_ctx_var.reset(request_id)

        return response

app = FastAPI(
    title='HelloWorld',
    version='0.1.0'
)
app.add_middleware(RequestContextLogMiddleware)

@app.get('/')
def index():
    return 'Hello!'

@app.get('/raise')
def raise_exception():
    raise ValueError('Something random')

@app.exception_handler(500)
async def exception_handler(request: Request, exc: Exception):
    return JSONResponse(
        content={'error': exc.__class__.__name__},
        status_code=500
    )

uvicorn.run(app)

@cetanu
I'm not sure I fully understand, but I think it might solve things if you put this line in a try: except: or try: finally: block:
response = await call_next(request)

so it is like:
try:
    response = await call_next(request)
except Exception as exc:
    # do whatever you want to do *only* when there is an exception
    response = Response(...)

Or similar.
If you are trying to add headers in the case of an exception, you'll basically need to write an exception handler.

@mths0x5f @cetanu I needed something like this so I made a package.
https://github.com/tomwojcik/starlette-context
I basically packaged what you wrote in here + tested it myself in my small project. Seems to be working. All feedback welcome.

I guess this section in the docs is probably useful to adding that custom logic that reads the request data: https://fastapi.tiangolo.com/advanced/custom-request-and-route/#accessing-the-request-body-in-an-exception-handler


Fixed #4375 - Multiple Cursors now go to the next logical line

This PR fixes https://github.com/Microsoft/vscode/issues/4375.
When adding multiple cursors it now only creates cursors for logical lines instead of visual lines.
Adding Cursors Down:

Adding Cursors Up:

Thanks for considering this PR.

Thanks for your feedback. I'll take your suggestions and hopefully have something out by the end of the week.

@alexandrudima . A made a couple of changes based on your suggestions.
First I move my logical line logic to addCursorDown/addCursorUp.  It now takes in an additional argument for the model. That allows to choose whether you want to have logical line enabled or not.
However, I need a bit of help when it comes to turning this option on and off. I saw that you mentioned that it would be possible to have be triggerable via keybindings. Would the logicalLine args be passed through to EditorAction constructor?
Do you want it to look like how the down variable is implemented in AbstractMoveLinesAction?
I'm wondering can you expand on that?

:+1:


DocsArchive-<IP_ADDRESS>Auto archive content

Please don't merge this PR until target archive repo PR https://github.com/OPS-E2E-PPE/docs-archive-test-target/pull/136 is merged into live branch.
Auto archive content to https://github.com/OPS-E2E-PPE/docs-archive-test-target.git

Docs Build status updates of commit 0ae7110:
:x: Validation status: errors
Please follow instructions here which may help to resolve issue.

File
Status
Preview URL
Details

:x:Error

Details

[Error]

Cannot sync git repo to specified commit because branch Archive_master_2019-10-08-08-15-09 has been deleted or has been force pushed: fatal: Couldn't find remote ref Archive_master_2019-10-08-08-15-09

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.


Version Command is Incorrect

Builds should produce the version command with the correct version.
and provide necessary details.
Current version Command
❯ harbor version
Version:      0.1.0
Go version:
Git commit:
Built:
OS/Arch:      linux/amd64

Expected
❯ harbor version
Version:      v0.0.1
Go version:   go1.23.3
Git commit:   f9a099cd2c763ff8d0c282cd223f626b88caa456
Built:        2024-11-27T20:36:32Z
OS/Arch:      linux/amd64

@bupd I added a PR that includes a Makefile for those kind of things. Please feel free to have a look

We already have dagger and It's better than Makefiles. So we don't need makefiles.
I am currently experimenting with the build and publish workflow we have in dagger.

@qcserestipy You can try updating the build function present in dagger/main.go. to fix this.

@bupd thank you for the hint, i will try that!


'vicuna' as model_base

How can we use vicuna as the LLM in inference code. Below is the error message. Thanks.

Could you please share your full scripts. I need to check model_name. This is usually caused by loading LLM weights via a mismatched Videollama2xxxforCausalLM class.

Here is the code. I only changed model_base from "None" to "vicuna"
import os
import torch
import transformers
import pandas as pd
import sys
sys.path.append('/content/VideoLLaMA2')
from videollama2.conversation import conv_templates
from videollama2.constants import DEFAULT_MMODAL_TOKEN, MMODAL_TOKEN_INDEX
from videollama2.mm_utils import get_model_name_from_path, tokenizer_MMODAL_token, process_video, process_image
from videollama2.model.builder import load_pretrained_model
def inference():
video_dir = '/content/drive/My Drive/ColabNotebooks/sample_data/data/beta_vids/'
video_paths = [os.path.join(video_dir, f) for f in os.listdir(video_dir) if f.endswith('.mp4') or f.endswith('.MOV')]
questions = ['On the scale of 1-5 how anxious is the person in the video?'] * len(video_paths)
modal_list = ['video'] * len(video_paths)

model_path = 'DAMO-NLP-SG/VideoLLaMA2-7B'
model_name = get_model_name_from_path(model_path)
model_base = "lmsys/vicuna-7b-v1.5"

tokenizer, model, processor, context_len = load_pretrained_model(model_path, model_base, model_name)
model = model.to('cuda:0')

conv_mode = 'llama_2'
results = []

for path, question in zip(video_paths, questions):
    tensor = process_video(path, processor, model.config.image_aspect_ratio).to(dtype=torch.float16, device='cuda', non_blocking=True)
    default_mm_token = DEFAULT_MMODAL_TOKEN["VIDEO"]
    modal_token_index = MMODAL_TOKEN_INDEX["VIDEO"]
    tensor = [tensor]

    question = default_mm_token + "\n" + question
    conv = conv_templates[conv_mode].copy()
    conv.append_message(conv.roles[0], question)
    conv.append_message(conv.roles[1], None)
    prompt = conv.get_prompt()
    input_ids = tokenizer_MMODAL_token(prompt, tokenizer, modal_token_index, return_tensors='pt').unsqueeze(0).to('cuda:0')

    with torch.inference_mode():
        output_ids = model.generate(
            input_ids,
            images_or_videos=tensor,
            modal_list=['video'],
            do_sample=True,
            temperature=0.2,
            max_new_tokens=1024,
            use_cache=True,
        )

    outputs = tokenizer.batch_decode(output_ids, skip_special_tokens=True)
    results.append({'video': path, 'output': outputs[0]})

df = pd.DataFrame(results)
output_file = '/content/drive/My Drive/ColabNotebooks/gemma_anxious_result.csv'
df.to_csv(output_file, index=False)
print(f"Results saved to {output_file}")

if name == "main":
inference()

Setting model_base=lmsys/vicuna-7b-v1.5 will return llama-based VideoLLaMA2 model, i.e., Videollama2LlamaForCausalLM. However, DAMO-NLP-SG/VideoLLaMA2-7B is trained based on mistralai/Mistral-7B-Instruct-v0.2, which mismatches the architecture of Videollama2LlamaForCausalLM.

If you want to use DAMO-NLP-SG/VideoLLaMA2-7B for inference, please set model_base=None.
If you want to use VideoLLaMA2 with lmsys/vicuna-7b-v1.5, you need to retrain a new VideoLLaMA2, which is based on lmsys/vicuna-7b-v1.5.

Are you going to release the dataset at some point?


[Feature Request]: Seed Quality Prediction Model (API)

Is there an existing issue for this?

[X] I have searched the existing issues

Feature Description
This API implements a Convolutional Neural Network (CNN) model to classify seed quality based on a dataset of seed images. The model is trained to predict whether seeds are of premium, standard, or regular quality by analyzing visual characteristics such as size, color, and texture. The primary goal is to ensure high crop productivity by making accurate seed quality predictions. The API will also provide a validation mechanism to ensure consistent and reliable seed classification, addressing the inefficiencies present in manual human intelligence-based evaluations.
Use Case
In agriculture, particularly in India, where manual seed quality prediction is common, this API can significantly improve farming operations. For example, a seed distributor could use the API to analyze large batches of seeds before sale, ensuring that only high-quality seeds are distributed to farmers. Similarly, a farmer could use the API to validate seed quality before planting, improving crop yield by planting only the best seeds. This would be especially beneficial during high-scale agricultural planning, where even small improvements in seed selection can have a large impact on output.
Benefits

Improved Accuracy: By using a CNN model, the API ensures precise seed classification, leading to higher prediction accuracy than traditional methods.
Scalability: The model can handle large datasets and be applied across different seed varieties and regions, making it useful for large-scale farming and distribution networks.
Efficiency: Automating seed quality evaluation reduces the time and effort spent on manual inspection, making the process more efficient and less prone to human error.
Higher Crop Yield: Farmers can rely on this API to make informed decisions on seed quality, leading to better germination rates and higher crop production.
Validation Mechanism: The API provides a reliable and consistent validation mechanism, filling the gap left by traditional, knowledge-based prediction methods without any validation.

Add ScreenShots
No response
Priority
Medium
Record

[X] I have read the Contributing Guidelines
[X] I'm a GSSOC'24 contributor
[X] I have starred the repository

are you going to do both frontend and api.. @LitZeus

i would like to start by adding the backend first.
Right now API only if it is fine with you!
@manikumarreddyu

Thanks! @manikumarreddyu


Swap the flyout version to be a code-branch icon

This will look cleaner and more obvious to users than the v: that it means a version.
I couldn't get the actual fontawesome icon to load,
but wanted to open this PR as a starting point.
If we're not loading Fontawesome icons via CDN,
which makes sense for performance,
we can perhaps load it via svg?

This will look cleaner and more obvious to users than the v: that it means a version. I couldn't get the actual fontawesome icon to load, but wanted to open this PR as a starting point.

We talked a little about this on Slack and we weren't sure about start making changes to the UI element yet. I opened https://github.com/readthedocs/addons/issues/97 but I didn't implemented yet because of the same reason.

If we're not loading Fontawesome icons via CDN, which makes sense for performance, we can perhaps load it via svg?

We are not using any external resource. Everything is self-contained/bundled into the readthedocs-addons.js we inject at serve time via CF. The pattern we are using here is a little different from the regular fa- CSS classes. If you want to use an icon, you have to import the icon using js import and then render it on the HTML part where you want to display it:
// Import the required functions and icons
import { library, icon } from "@fortawesome/fontawesome-svg-core";
import { faBinoculars } from "@fortawesome/free-solid-svg-icons";

// Add the icon to the library
library.add(faBinoculars);

// Instantiate the icon
const binoculars = icon(faBinoculars)

// Render the icon inside the HTML code
return = html`

     ${binoculars.node[0]}

Some text.

`

BTW, welcome to the JavaScript world! 🥴

Noted on #97 as well, but I feel like what we're aiming for with the first implementation of this flyout is something that users could easily reuse over the flyout menu we current give to projects. So, for now, I'm hesitant to iterate much at all on the styles and structure, and instead collect these changes in a separate implementation entirely,

Cool, I'm happy to hold off on this, just wanted to do a small contribution. I don't think it's a big risk to change the beta flyout, and I'm not sure what the timeline is for a larger refactor, so small improvements seem useful to me 🤷

Overall, I don't think we want people changing the flyout itself, but instead incorporating the data into the built docs, I thought?

Yes, I'm on the same boat. Every time I think about this, I lean more towards the idea of "use our own integrations as-is, or create your own using the JSON data". I feel a lot more comfortable (myself and as a company) to compromise ourselves to maintain an API structure over time than a HTML/CSS/JS one.
I did an experiment "using the role of a Sphinx theme author" and created the flyout integration in our own theme at https://github.com/readthedocs/sphinx_rtd_theme/pull/1526. I felt great about it. It was a clean pattern, simple to do, easy to integrate and looks great. That showed me that "using the JSON data" is pretty simple for users and give them a lot of power while reducing our maintenance burden.
If we ever want to allow users to "customize our own addons", I'd say it should be via the WebUI/dashboard using specific options that we control. I feel that giving users more control than this for customization of our addons it's gonna be a nightmare in the future.

I'd say it should be via the WebUI/dashboard using specific options that we control

:100: Absolutely! This would be a killer feature of a new flyout, I think we've long wanted something like this. There are plenty of options would could surface if we wanted: "Don't show links to the dashboard" or "Flyout background color: #445", etc.
I do agree that heavy customizations should be a theme/author change though, so there is definitely some threshold that we shouldn't cross with our own customizations. But anything we can do to keep authors from customizing our flyout with CSS would be a win I think.

Overall, I don't think we want people changing the flyout itself, but instead incorporating the data into the built docs, I thought?

Well, sort of, but yes. We don't want users customizing the flyout with CSS. CSS puts the customizations out of our control. What Manuel described would be the best target I think -- most projects use the stock flyout, a UI customized flyout is for intermediate use, and full customization is for advanced users and theme maintainers.
For now, users only really have CSS for customizations. Instead of iterating on what we have, and users kicking their CSS hacks forward onto the new implementation, I'd like to start fresh with a new implementation entirely. This would give us a clean place to start from, and we should aim for some basic level of configuration from the start with this flyout -- just at the HTML level would be fine, application UI can come later.
We can definitely be playing around with ideas for the new flyout too, maybe just with a subclass of the flyout addon.

I updated @ericholscher  PR to reflect the changes he wanted to do here. It looks like this now ✨

I keep wanting this, if it seems simple to merge in the latest version.

I'm 👍🏼 on merging this PR. I don't think there is anything blocking us and it looks better. I updated this PR with all the changes from origin/main.


fix: bucket encryption is enabled if SSEAlgorithm is specified

Resolves: https://github.com/aquasecurity/defsec/issues/1067

Thank you for feedback!
I fixed it.

Thank you for feedback!
I fixed it.

Looks like there's a few checks that are red, could you address those?


#2435 packagist composer metadata api

Hi, this PR implements improvements proposed in #2435

Warnings

:warning:
This PR modified service code for packagist but not its test code. That's okay so long as it's refactoring existing code.

Messages

:book:
:sparkles: Thanks for your contribution to Shields, @piekar294!

  Generated by :no_entry_sign: dangerJS against 09623c62c644c9187c264038053a42b25f7f606a

I'm getting an invalid response data badge for the license with this PR
https://shields-staging-pr-4231.herokuapp.com/packagist/l/doctrine/orm

but it's working fine in prod:
https://img.shields.io/packagist/l/doctrine/orm

Thanks for the quick fix!

I'm getting an invalid response data badge for the license with this PR
https://shields-staging-pr-4231.herokuapp.com/packagist/l/doctrine/orm

but it's working fine in prod:
https://img.shields.io/packagist/l/doctrine/orm

Thank you for catching this out.
I investigated it further and I surprisingly found out that example from tests was working just fine (https://img.shields.io/packagist/l/symfony/symfony).
npm run badge -- /packagist/l/doctrine/orm showed problem with schema, so I fix it out.
I haven't found out the reason why schema is not working fine for doctrine/orm yet.
I will try to figure out what exactly went wrong. Moreover, I think it would be appropriate to describe this situation in tests, so i would like to add some tests from schema validation :)

I will try to figure out what exactly went wrong. Moreover, I think it would be appropriate to describe this situation in tests, so i would like to add some tests from schema validation :)

That'd be great! Feel free to open a new issue to keep track of that

Actually just to clarify, did you mean you want to add some additional packagist tests as part of this PR?

Actually just to clarify, did you mean you want to add some additional packagist tests as part of this PR?

I thought about adding tests to this PR, but I may open new PR as well.
Probably I wont be able to work on tests before Tuesday/Friday, so
feel free to merge this PR, if you found current changes to be sufficient :)

I thought about adding tests to this PR, but I may open new PR as well.
Probably I wont be able to work on tests before Tuesday/Friday, so
feel free to merge this PR, if you found current changes to be sufficient :)

Thanks for clarifying. I'm going to go ahead and merge, and if you decide to look into adding more tests we can do so in a future PR


Add support to SLSA compliance

the chain-bench could support SLSA requirements. https://slsa.dev/spec/v0.1/requirements

Hi @krol3,
I really like your idea, we will work on adding SLSA level as part of each checks metadata soon.
Meantime, Do you have in mind any expected behavior that you wish to see when running chain-bench?
Thanks,
Mor

Hi! @morwn, what about the output of this new SLSA report?
how can I see in the output, if it's following the SLSA level "slsa_level": [1,2,3,4] ?
Currently the output is like this:
chain-bench version 0.1.3
 2.3.1    Ensure all build steps are defined as code                                                      Passed
 2.3.5    Ensure access to the build process's triggering is minimized                                    Unknown   Organization is not fetched
 2.3.7    Ensure pipelines are automatically scanned for vulnerabilities                                  Passed
 2.3.8    Ensure scanners are in place to identify and prevent sensitive data in pipeline files           Failed    Repository is not scanned for secrets
 2.4.2    Ensure all external dependencies used in the build process are locked                           Failed    6 task(s) are not pinned
 2.4.6    Ensure pipeline steps produce an SBOM                                                           Failed    2 pipeline(s) contain a build job without SBOM generation
 3.1.7    Ensure dependencies are pinned to a specific, verified version                                  Failed    6 dependencies are not pinned
 3.2.2    Ensure packages are automatically scanned for known vulnerabilities                             Passed
 3.2.3    Ensure packages are automatically scanned for license implications                              Passed
 4.2.3    Ensure user's access to the package registry utilizes MFA                                       Unknown   Registry is not fetched
 4.2.5    Ensure anonymous access to artifacts is revoked                                                 Unknown   Registry is not fetched
 4.3.4    Ensure webhooks of the package registry are secured                                             Passed
-------- ----------------------------------------------------------------------------------------------- --------- -----------------------------------------------------------
 Total Passed Rules: 9 out of 26
2022-08-21 16:49:18 INF Scan completed: 4s

The actual reporting UI will be implemented soon


feat(prettier) print for of statements

Merge activity

Nov 17, 12:36 PM: @Boshen started a stack merge that includes this pull request via Graphite.


Evaluate option for building Dframework

The questions we seem to have are:
how do we integrate with the existing site? Deploy to Wordpress? Have a link that launches an external application? (Other options …?)
what UI framework makes sense? React? (Does it need to be a single page application?) NextJS? Vanilla JS? (Rana seems to prefer Vanilla JS due to existing skills, but that can be addressed with knowledge transfer.) Is React a good fit for the problem we’re solving?
Are there any considerations around managing state? Would the user leave the site and return later, or can we assume that once they’ve started the process they would complete it?

I started to research about each question above and compare the result based on advantages and disadvantages.
we will decide and agree on our tech stack in our Monay session by considreration of PO's requirement and project constraints.I attached my result research here
Spike(evaluate options for builing the Dframework).pdf

Looks great @leilafaez thank you. Will assign to @andrewwhitehouse for review

To make the decision framework application, we will consider integrating React into WordPress using the ReactPress plugin.
This integration can leverage the WordPress database engine for RESTful APIs. In this concise summary, we will explore this approach's benefits, potential challenges, and opportunities, along with a successful proof of concept completed by our team.
Benefits of using ReactPress:
Reusability and modular code: React promotes reusable components, improving code organization and streamlining development.
Leverage WordPress's database engine: ReactPress allows developers to use the WordPress database engine as a backend for RESTful APIs, simplifying data management.
Learning curve advantage: Our team already possesses the skills to develop SPAs using React, allowing us to capitalize on this technology with minimal additional training.
Proof of Concept:
Our team has completed a proof of concept, demonstrating the integration of a React component into a generic WordPress site. You can view the sample React component embedded in the WordPress site at the following link: wp.mhallaq.nl/react-demo
Challenges of using ReactPress:
Potential compatibility issues: ReactPress may encounter compatibility issues with other WordPress plugins or themes, which could require troubleshooting and development efforts.
SEO challenges: SPAs can present SEO challenges, requiring additional configurations to ensure proper search engine crawling and indexing.
Conclusion: Integrating React into WordPress with ReactPress can provide numerous benefits, including user experience and maintainability. With our team's existing React skills and successful proof of concept, we are well-positioned to adopt this new technology. However, we should also consider potential compatibility issues and SEO challenges when planning our sprint. By leveraging the WordPress database engine for RESTful APIs, we can unlock new opportunities to create modern, responsive, high-performing websites.

Our current working assumption is to use ReactPress to integrate the application into Wordpress.


github: unload br_netfilter module

This modules is not normally loaded on stock Ubuntu installs but it is on GHA runners.
Fixes https://github.com/canonical/lxd/issues/13069

@simondeziel looks like 5.0 doesn't have --all-projects either https://github.com/canonical/lxd-ci/actions/runs/11276081468/job/31359091586?pr=316

@simondeziel looks like 5.0 doesn't have --all-projects either https://github.com/canonical/lxd-ci/actions/runs/11276081468/job/31359091586?pr=316

No, this one failed for another reason (v1 being slow to start up). 5.0 has --all-projects which is used a few lines below :)

@simondeziel looks like 5.0 doesn't have --all-projects either https://github.com/canonical/lxd-ci/actions/runs/11276081468/job/31359091586?pr=316

No, this one failed for another reason (v1 being slow to start up). 5.0 has --all-projects which is used a few lines below :)

ah, so confusing output :)

@simondeziel looks like 5.0 doesn't have --all-projects either https://github.com/canonical/lxd-ci/actions/runs/11276081468/job/31359091586?pr=316

No, this one failed for another reason (v1 being slow to start up). 5.0 has --all-projects which is used a few lines below :)

ah, so confusing output :)

Would you like the df -h, uname -a and lxc list to be collapsed into log groups? Same as the lsmod bits and company?

Would you like the df -h, uname -a and lxc list to be collapsed into log groups? Same as the lsmod bits and company?

Ah yeah good idea, everything below echo 'Test failed' if possible?


Put UIView below containerView

I want to add UIView below UIScrollView but when I do this - viewCollections won't fit in containerView. How could I provide autolayout to this containerView?
containerView has all needed constraints.
The problem is that containerView's views are not same height as containerView.

Sorry, there was an error in my viewControllers with their height!


Bubble Charts missing?

How can I make a bubble chart? I can't see the option to make a Bubble chart anymore. How can I make it so that the dots generated vary in diameter?

@SirWellington Hi! Option for Bubbles has been added in Chart 5.4.0 for Sketch


Calling vim lua module functions  in custom config file passed with --configpath flag doesn't work

How are you using the lua-language-server?
NeoVim
Which OS are you using?
MacOS
What is the issue affecting?
Libraries
Expected Behaviour
https://github.com/neovim/neovim/issues/21686
Actual Behaviour
Details here:
https://github.com/neovim/neovim/issues/21686
Basically:

it seems lua-language-server stops(?) parsing the custom config file, when it encounters the unknown vim module call, so none of the values it returns are added to the library key.
vim is still not recognized as a defined global using this custom lua config file.

Reproduction steps
Steps for Neovim are in the linked issue above.
Additional Notes
I think this may be just a neovim issue mainly, but I'm curious if anyone has any ideas of how to workaround the fact that I couldn't use the vim module in the config file?
Log File
Log in linked issue at the bottom.

Closing as I've worked around this but checkfor for and evaluating any .luarc.lua that is found in project root from inside Neovim lsp setup, where we have access to vim. module


AMBARI-24486. Yarn Timeline Service V2 Reader is found down after EU …

…(Atlantic to AtlanticM05) With error - Address already in use (amagyar)
What changes were proposed in this pull request?
Ambari 2.7 is shipped with a stack where yarn-site/yarn.timeline-service.reader.webapp.address and yarn-site/yarn.timeline-service.reader.webapp.https.address contains placeholders like {{timeline_reader_address_http}} and {timeline_reader_address_https}}. The upgrade task that is responsible for replacing these properties expects localhost:port.
How was this patch tested?

Deployed cluster with Ambari version: <IP_ADDRESS>-897 and HDP version: <IP_ADDRESS>-1634
Upgrade Ambari to <IP_ADDRESS>-70
Stack Upgrade to <IP_ADDRESS>-73
Checked that yarn-site/yarn.timeline-service.reader.webapp.address and yarn-site/yarn.timeline-service.reader.webapp.https.address had the correct value

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/Ambari-Github-PullRequest-Builder/3624/
Test PASSed.


Make docker work fully

shish@macbook:~/Projects/rosettaboy$ ./utils/shell.sh
user@b677a6fae865:/home/dev$ ./utils/bench.py
  cpp / release:
   go / release: Emulated 600 frames in  2.07s (290fps)
  nim / release: Emulated 600 frames in  0.30s (1969fps)
  php / release: Emulated 600 frames in 11.16s (54fps)
   py / release: Emulated 600 frames in 60.24s (10fps)
   py / mypyc  : Emulated 600 frames in 56.73s (11fps)
   rs / release: Emulated 600 frames in  0.26s (2302fps)
   rs / pgo    :
  zig / release:

cpp crashes
rust pgo is probably missing something
zig compiler isn't installed

Also nim only works after you run ./run.sh manually and accept the interactive "download package list [y/n]" prompt

zig and nim are now working

C++ fails because GCC appears to be interpreting things differently to Clang - the first indication of this is that:
printf("%d", (i8)250);

prints "-6" with clang and "250" with gcc
Rust/PGO fails because the default rust install doesn't have the profiler enabled

62154e778beeeb7f7c8ddc0451d7c256b93cc585 disables rust-pgo because I've never managed to make that work anywhere


Prerelease versions are incorrectly included into caret ranges.

Output of bower -v && npm -v && node -v:
1.8.4
6.1.0
v8.11.1

Steps to reproduce the issue:

Have a package with prerelease versions for some minor version and no stable releases of that minor version.
For instance, vaadin-button (https://github.com/vaadin/vaadin-button/releases) has currently 2.1.0-alpha2 and 2.1.0-alpha1 prerelease versions and no other version that starts with 2.1..

Add it into bower.json with range on the minor version mentioned above:

{
  "name": "test-range",
  "dependencies": {
    "vaadin-button": "^2.1.0"
  }
}

Run bower i

Describe the results you received:
vaadin-button#2.1.0-alpha2 version is installed.
Describe the results you expected:
No version should be installed, 2.1.0-alpha2 does not belong to the range ^2.1.0
Additional information:
I did not find any ^ description in bower.json specs, but had found the one in node specs:
https://docs.npmjs.com/misc/semver#caret-ranges-123-025-004

^1.2.3 := >=1.2.3 <2.0.0

Semver explicitly states in https://semver.org/#spec-item-11 that

1.0.0-rc.1 < 1.0.0

In our case that means that

^2.1.0 := >=2.1.0 <3.0.0
2.1.0-alpha2 < 2.1.0

Hence 2.1.0-alpha2 version does not belong to ^2.1.0 range and should not be resolved.
Most probably the bug is caused by semver library that is used in bower: it is of version 2.3.2 in the project and the following snippet returns true:
const semver = require('semver');
semver.satisfies('2.1.0-alpha2', '^2.1.0'); // true

Latest semver version, 5.5.0 returns false for the same snippet.
I've tried updating semver in the project but got 6 tests failing.
If you approve that the issue is worth investigating and releasing a new bower version, I can investigate the test failures more deeply.

This is unfortunate, but we can't change this as it's very much a breaking change :/


add DWMA svclinks, add SWMA pev pe svclinks

@lzehl , sorry that it took awhile.
There is an outstanding issue, namely en dashes (\u2013) that exist in some of the region names.
I have left them intact, but I could very easily global remove them/replace them with another character.

@xgui3783 Thank you :+1:
@lzehl Does this already cover everything we discussed earlier?

@skoehnen I think it does. @xgui3783 many thanks for this. I will review the PR asap.

@lzehl thanks for the review. one slight clarification needed:

For the PEs:
I suggest to use the bundle abbreviation also for the at id. Example: "@id": "https://openminds.ebrains.eu/instances/parcellationEntityVersion/SWMA_PoC-PrC".

would it be https://openminds.ebrains.eu/instances/parcellationEntity/SWMA_PoC-PrC
instead?
I will get started on fixing the points raised, and will ping you when/if there are more issues.

@xgui3783 yes. You are fully correct. Sorry for the copy past error on my side 🙈

@lzehl I have pushed a new commit, which addresses most of your requests.
I have a further request for clarification.
In your comment, there seems to be several inconsistencies when referring to the version. e.g.

"lookupLabel": "SWMA_v2018_lh_PoC-PrC_0" (with v prefix)
"@id": "https://openminds.ebrains.eu/instances/parcellationEntityVersion/SWMA_2018_lh_PoC-PrC_0" (without v prefix)
SWMA_v2018_lh_PoC-PrC_0.jsonld (with v prefix)
"versionIdentifier": "v2018, rh" (with v prefix)`

Would it be wise to adhere to a single convention (always with or always without) to avoid confusion/mistake?

@xgui3783 you are right : a single convention is wise. I do not have a preference. Feel free to decide, I'll adapt the dataset version identifiers accordingly (which anyway need to be changed).

@xgui3783 I've found one more issue (see above). Let me know if I can support you (it's quite a huge PR).

@lzehl I have tenatively fixed the issue you spoke about. There are now super (e.g. CMF-PrC)/sub (e.g. CMF-PrC_1) PE for SWMA
Re: https://github.com/HumanBrainProject/openMINDS_SANDS/pull/158#discussion_r799543015 currently, I am adopting:

CMF-PrC_1 (as PE) : hasVersion field include lh_CMF-PrC_1 (as PEV)

lh_CMF-PrC_1 AND  rh_CMF-PrC_1 as PEVs in hasVersion field of CMF-PrC_1 as PE

@lyuba
I have added another commit, which specifically dealt with

CMF-PrC (as PE parent structure for all below)
CMF-PrC_0 (as PE with has version): lh_CMF-PrC_0, rh_CMF-PrC_0 (as PEVs)
CMF-PrC_1 (as PE with has version): lh_CMF-PrC_1, rh_CMF-PrC_1 (as PEVs)

re:

lh_CMF-PrC_1 AND rh_CMF-PrC_1 as PEVs in hasVersion field of CMF-PrC_1 as PE

I just checked and it seems CMF-PrC_1 (PE) does already have lh_CMF-PrC_1 (PEV) and rh_CMF-PrC_1 (PEV) as hasVersion. Or did I miss something?

@lzehl I have pushed two more commits that should address your comments.

@xgui3783 sorry that the corrections come not at once. It's just too many files to review. I think the MPM issue is really the last though.


There are no datasources configured

Hey,
I just tried quickstart in distribution 1.2.0 (with druid 0.9.0) using distribution-docker, I indexed stuff in there so that :
$ curl -XGET http://localhost:8081/druid/coordinator/v1/datasources
["foo"]

$ curl -XGET http://localhost:8081/druid/coordinator/v1/datasources/foo
{"tiers":{"_default_tier":{"size":155675892,"segmentCount":166}},"segments":{"maxTime":"2016-02-22T00:00:00.000Z","size":155675892,"minTime":"2015-01-01T00:00:00.000Z","count":166}}

But if I go to localhost:9095/pivot it says : "There are no datasources configured" ... Even localhost:9095/pivot#foo does so.
Any idea what might be wrong ? It was working for me until I tried distribution 1.2.0

I see, there is this log message :
Failed to load data source: 'foo' because 'c-geo:c3' is not a URL safe name. Try 'c-geo_c3' instead?

Any idea how to deal with this? I cannot change it in the source json files.

I asked the question on google groups

Hi as off Pivot 0.8.15 url safe names will be automatically created when introspecting a data source with non url safe dimension names. Thinks should 'just work now'.


Run

Using run (while make default file manager) makes an error

Hello, this repo is for Files' website. Please open this issue again on the app's repo.


Correct padding mode flag name for EVP_PKEY_decrypt/encrypt() examples

The example code in EVP_PKEY_decrypt(3) and EVP_PKEY_encrypt(3) and uses
a nonexistent padding mode RSA_OAEP_PADDING, which should be
RSA_PKCS1_OAEP_PADDING instead.
CLA: trivial
Checklist

[x] documentation is added or updated

I am OK with CLA: trivial

doc/man3/EVP_PKEY_decrypt.pod and doc/man3/EVP_PKEY_encrypt.pod should also be updated.

Those are the files updated by this PR, is there anything else missing?

@slontis I take that as you're ok with CLA: trivial

24 hours has passed since 'approval: done' was set, but as this PR has been updated in that time the label 'approval: ready to merge' is not being automatically set.  Please review the updates and set the label manually.

Merged, thanks for the fix.


centos: Could not load the Qt

I made an error here.error:Could not load the Qt..................

I observed that in the judgment of the 'install. py' script code, in the Windows and Darwin system environments, 'pyqt' needs to be installed, but my system environment is Centos. What should I do?

help

It would be good to know whether simply installing pyqt6 resolves the issue. Also, would be good to know what is the platform.system() value on your machine.

@yincangshiwei


Split libcxx and libcxxabi

Checklist

[ ] Used a fork of the feedstock to propose changes
[ ] Bumped the build number (if the version is unchanged)
[ ] Reset the build number to 0 (if the version changed)
[ ] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[ ] Ensured the license file is being packaged.

Hi! This is the friendly automated conda-forge-linting service.
I wanted to let you know that I linted all conda-recipes in your PR (recipe) and found some lint.
Here's what I've got...
For recipe:

The top level meta keys are in an unexpected order. Expecting ['package', 'source', 'build', 'requirements', 'test', 'outputs', 'about', 'extra'].

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.


请问能否只使用CPU？ 当前没有GPU 卡

如题，感谢！

Certainly, it is feasible. Please refer to https://github.com/netease-youdao/EmotiVoice/wiki/Hardware-and-Software-Requirements-for-Running-EmotiVoice for details.


Custom client certificate

In Mendix 8.18.0, there is a new option when calling a REST or web service. You can configure a specific client certificate to be used.

Merging into my branch for final review of files

Merging into my branch for final review of files


feature: app directory

📝 Changed routes:

/api/og

1 deleted route:

/

Commit 494371f0e05d2295eccb86d21565ff160f45d2b4 (https://next-js-boilerplate-p6brcrcbo-alex289.vercel.app).


FocusNode change notifier not called when focused TextField is removed

The following test will fail the final expect:
import 'package:flutter/material.dart';
import 'package:flutter_test/flutter_test.dart';

Widget buildApp(Widget body) {
  return MaterialApp(
    home: Scaffold(
      body: body,
    ),
  );
}

TextField buildTextField(FocusNode focus) {
  return TextField(
    focusNode: focus,
    autofocus: true,
  );
}

main() {
  testWidgets('Focus node dispose', (WidgetTester tester) async {
    final FocusNode focus = FocusNode();
    bool isFocused = focus.hasFocus;
    final VoidCallback focusChanged = () => isFocused = focus.hasFocus;
    focus.addListener(focusChanged);
    expect(isFocused, isFalse);

    await tester.pumpWidget(buildApp(buildTextField(focus)));
    expect(focus.hasFocus, isTrue);
    expect(isFocused, isTrue);

    await tester.pumpWidget(buildApp(Text('No focus')));
    expect(focus.hasFocus, isFalse);
    expect(isFocused, isFalse);
  });
}

I believe this violates the contract established by FocusNode's ChangeNotifier interface, since clearly the FocusNode no longer has focus after its TextField is removed.
In our app we expect the change notifier to be called so that we can manage the focus change cleanly. Without this, we need to manage the focus change by chasing down every logic path that can cause the app to rebuild without the text field, which leads to error-prone duplication of code.

This is because if the focus system notified listeners of a focus change after a focus node was no longer in the widget tree, it would often end up calling setState on widgets that were unmounted.
I agree that it's not ideal.  Ideally, we'd be able to notify about focus changes synchronously, but that has its own problems: if a node is then simply moved from one place in the tree to another, it would notify about losing and gaining focus, even when it didn't technically do either. Sending focus changes between frames solves this problem, but creates the one you mention above.

I would propose an API change wherein the focus change notification includes a reason for the focus change. This reason can specify that focus was lost because the node was unmounted. Client code can then deal with the focus change appropriately, including avoiding a setState() call on an unmounted node.
I can think of a few different ways this API change could be done with a soft migration, if the general approach is approved.

I think in general that it is a good proposal.

logs
00:08 +0: Focus node dispose
══╡ EXCEPTION CAUGHT BY FLUTTER TEST FRAMEWORK ╞════════════════════════════════════════════════════
The following TestFailure object was thrown running a test:
  Expected: false
  Actual: <true>

When the exception was thrown, this was the stack:
#4      main.<anonymous closure> (file:///Users/taha/AndroidStudioProjects/dev_flutter/test/widget_test.dart:64:5)
<asynchronous suspension>
#5      main.<anonymous closure> (file:///Users/taha/AndroidStudioProjects/dev_flutter/test/widget_test.dart)
#6      testWidgets.<anonymous closure>.<anonymous closure> (package:flutter_test/src/widget_tester.dart:144:29)
<asynchronous suspension>
#7      testWidgets.<anonymous closure>.<anonymous closure> (package:flutter_test/src/widget_tester.dart)
#8      TestWidgetsFlutterBinding._runTestBody (package:flutter_test/src/binding.dart:744:19)
<asynchronous suspension>
#11     TestWidgetsFlutterBinding._runTest (package:flutter_test/src/binding.dart:724:14)
#12     AutomatedTestWidgetsFlutterBinding.runTest.<anonymous closure> (package:flutter_test/src/binding.dart:1124:24)
#13     FakeAsync.run.<anonymous closure>.<anonymous closure> (package:fake_async/fake_async.dart:177:54)
#18     withClock (package:clock/src/default.dart:46:10)
#19     FakeAsync.run.<anonymous closure> (package:fake_async/fake_async.dart:177:22)
#24     FakeAsync.run (package:fake_async/fake_async.dart:177:7)
#25     AutomatedTestWidgetsFlutterBinding.runTest (package:flutter_test/src/binding.dart:1121:15)
#26     testWidgets.<anonymous closure> (package:flutter_test/src/widget_tester.dart:137:24)
#27     Declarer.test.<anonymous closure>.<anonymous closure> (package:test_api/src/backend/declarer.dart:171:19)
<asynchronous suspension>
#28     Declarer.test.<anonymous closure>.<anonymous closure> (package:test_api/src/backend/declarer.dart)
#33     Declarer.test.<anonymous closure> (package:test_api/src/backend/declarer.dart:169:13)
#34     Invoker.waitForOutstandingCallbacks.<anonymous closure> (package:test_api/src/backend/invoker.dart:235:15)
#39     Invoker.waitForOutstandingCallbacks (package:test_api/src/backend/invoker.dart:232:5)
#40     Invoker._onRun.<anonymous closure>.<anonymous closure>.<anonymous closure> (package:test_api/src/backend/invoker.dart:388:17)
<asynchronous suspension>
#41     Invoker._onRun.<anonymous closure>.<anonymous closure>.<anonymous closure> (package:test_api/src/backend/invoker.dart)
#46     Invoker._onRun.<anonymous closure>.<anonymous closure> (package:test_api/src/backend/invoker.dart:374:9)
#47     Invoker._guardIfGuarded (package:test_api/src/backend/invoker.dart:420:15)
#48     Invoker._onRun.<anonymous closure> (package:test_api/src/backend/invoker.dart:373:7)
#55     Invoker._onRun (package:test_api/src/backend/invoker.dart:372:11)
#56     LiveTestController.run (package:test_api/src/backend/live_test_controller.dart:152:11)
#57     RemoteListener._runLiveTest.<anonymous closure> (package:test_api/src/remote_listener.dart:259:16)
#62     RemoteListener._runLiveTest (package:test_api/src/remote_listener.dart:258:5)
#63     RemoteListener._serializeTest.<anonymous closure> (package:test_api/src/remote_listener.dart:211:7)
#81     _GuaranteeSink.add (package:stream_channel/src/guarantee_channel.dart:124:12)
#82     new _MultiChannel.<anonymous closure> (package:stream_channel/src/multi_channel.dart:159:31)
#116    new _WebSocketImpl._fromSocket.<anonymous closure> (dart:_http/websocket_impl.dart:1145:21)
#124    _WebSocketProtocolTransformer._messageFrameEnd (dart:_http/websocket_impl.dart:338:23)
#125    _WebSocketProtocolTransformer.add (dart:_http/websocket_impl.dart:232:46)
#135    _Socket._onData (dart:io-patch/socket_patch.dart:2020:41)
#144    new _RawSocket.<anonymous closure> (dart:io-patch/socket_patch.dart:1556:33)
#145    _NativeSocket.issueReadEvent.issue (dart:io-patch/socket_patch.dart:1052:14)
(elided 108 frames from dart:async and package:stack_trace)

This was caught by the test expectation on the following line:
  file:///Users/taha/AndroidStudioProjects/dev_flutter/test/widget_test.dart line 64
The test description was:
  Focus node dispose
════════════════════════════════════════════════════════════════════════════════════════════════════
00:08 +0 -1: Focus node dispose [E]
  Test failed. See exception logs above.
  The test description was: Focus node dispose

00:08 +0 -1: Some tests failed.

flutter doctor -v
[✓] Flutter (Channel dev, 1.20.0-3.0.pre, on Mac OS X 10.15.5 19F101, locale
    en-GB)
    • Flutter version 1.20.0-3.0.pre at /Users/taha/Code/flutter_dev
    • Framework revision 0af027f805 (5 days ago), 2020-07-04 12:19:20 -0700
    • Engine revision a751393804
    • Dart version 2.9.0 (build 2.9.0-20.0.dev 22da8934ac)

[✓] Android toolchain - develop for Android devices (Android SDK version 30.0.0)
    • Android SDK at /Users/taha/Code/sdk
    • Platform android-30, build-tools 30.0.0
    • ANDROID_HOME = /Users/taha/Code/sdk
    • Java binary at: /Applications/Android
      Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build
      1.8.0_242-release-1644-b3-6222593)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 11.5)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Xcode 11.5, Build version 11E608c
    • CocoaPods version 1.9.3

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 4.0)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin version 47.1.2
    • Dart plugin version 193.7361
    • Java version OpenJDK Runtime Environment (build
      1.8.0_242-release-1644-b3-6222593)

[✓] VS Code (version 1.46.1)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.12.1

[✓] Connected device (4 available)
    • SM M305F (mobile)      • 32003c30dc19668f          • android-arm64  •
      Android 10 (API 29)
    • Taha’s iPhone (mobile) • 00008020-001059882212002E • ios            • iOS
      13.5.1
    • Web Server (web)       • web-server                • web-javascript •
      Flutter Tools
    • Chrome (web)           • chrome                    • web-javascript •
      Google Chrome 83.0.4103.116

• No issues found!


[Feature Request] Ability to Add XBox Game Pass (or "Cloud Gaming") as Platform/Player (i.e. launch without needing a widget or shortcut)

Enhancement Idea: It would be nice to create a Platform for Game Pass (or other cloud game apps) so I can use the GORGEOUS Daijisho as my total device launcher, rather than retro only and then having to go to Apps or Widgets for xbox.
Just a thought :)

Game Pass app doesn't support externally launching specific games unfortunately. Same as PlayStation Remote Play and Steam Link apps
Moonlight supports it on the otherhand


Shall we using some sync fences to allow the display pipeline to catch up

I find the sync fence technology (eglCreateSyncKHR eglWaitSyncKHR ) in the  source code of android hwui.Shall we use this technology in flutter's ui system to get some improvement.

@FelixZhang00
Can you elaborate on your request by using the feature request template

I think the eglSwapBuffers allowing back pressure to build up  is more suitable for flutter pipeline.
So close this issue.


Binary exponentiation in cpp

Information about Algorithm

BInary Exponentiation allows to calculate pow(a,n) (or, a^n) in O(log n) time.
Implemented using recursion.
Have you read the Contributing.md and Code of conduct

[x] Yes
[ ] No

Other context

This is a general maths problem

I want to contribute for this.


Clean-up: Example S3 Bucket Name in Templates

It appears the s3 template seems to have a reference so some example bucket. I can't find a reason for it to be there so I aligned it with the dynamodb.json template with the built in Jinja2 last feature.

Yes, this fix appears to be the correct way of doing the S3 Template. Please update the Test Cases to reflect the correct behaviour.

@e4r7hbug Sorry for the delay this should be fixed.

Looks good now. Thanks!


Get "Not Running Error when trying to install on umbrel

Here is a system log:
May 09 14:25:37 umbrel umbreld[5938]: [apps         ] [error] Failed to install app alby-nostr-wallet-connect: Command failed with exit code 1: docker compose --project-name umbrel --file /usr/local/lib/node_modules/umbreld/source/modules/apps/legacy-compat/docker-compose.yml up --build --detach --remove-orphans

the app installs (but strangely doesn't show progress during installation)
says "not running" instead of the app name underneath the app
icon disappears shortly after appearing on home screen.

Device
Raspberry Pi 4 8gb
umbrelOS - umbrelOS 1.1
Uptime - about 14 hours

Sorry it was a local issue


Button that set the chart to its initial state.

I've created a personalized initial state to orgchart where i start the chart with the two fake roots at the top of the svg.
What i need to do is to create a button that set the chart to this initial state again, does anyone know if there's a way of doing this?

Have a boolean parameter, which would be set after the button click, use this bool parameter inside your nodeContent function and finally redraw after the button click (using chart.render())

Button that sets boolean paramenter:

And this is my nodeContent function:

Are you saying that i need to render the chart inside of the nodeContent function?

Something like this
let isInitial = false;

let chart = new OrgChart()
...
.nodeContent(d=>{
  if(isInitial) {
   //   then generate content for initial node
 }else{
  // do multi root version
}
})

//  when button is clicked change variable and rerender graph
button.onClick = ()=>{
  isInitial = true;
  chart.render()
}


Datadog integration doesn't seem to be working: EKS and helm chart

I have an installation of imgproxy using the helm chart (via kustomize) on an EKS cluster. Following the docs, I have the chart values set to this:
      datadog:
        enabled: true
        env: test
        metricsEnabled: true
        tags: "cluster:test-cluster"
        traceDebug: true

I also used a kustomize patchesStrategicMerge to set DD_AGENT_HOST to the appropriate status.hostIP value for kubernetes pods:
        - name: DD_AGENT_HOST
          valueFrom:
            fieldRef:
              fieldPath: status.hostIP

The datadog env variables look like this in the pod:
kubectl exec -it imgproxy-xxxxxxxxxx -- env | grep DD_
DD_AGENT_HOST=<IP_ADDRESS>
DD_TAGS=cluster:test-cluster
DD_ENV=test
DD_TRACE_DEBUG=true
DD_TRACE_AGENT_PORT=8126
DD_DOGSTATSD_PORT=8125
DD_SERVICE=imgproxy
DD_RUNTIME_METRICS_ENABLED=true

I've verified our datadog agent is running and listening on the default ports and should be receiving traces and metrics, but I can't seem to find the ones mentioned in the docs anywhere in datadog:
I tried searching in metrics explorer for "service:imgproxy" and metrics under the namespace "imgproxy", but it comes up empty. When I search for the tag "service:imgproxy" in the metrics summary, I see some metrics under the datadog namespace (datadog.dogstatsd and datadog.trace mostly) and then some metrics under the runtime.go namespace (runtime.go.mem_stats mostly). In the docs it mentions some response time and processing metrics and I can't seem to find them. Should they be under a imgproxy namespace? The docs are not clear on the naming of these metrics and I haven't had any luck finding them.
Also, as you see I have DD_TRACE_DEBUG set to true, but I don't see any debug logs in my pod's log output. Should I be looking for those debug logs somewhere else?

I'm able to see the debug log output (I wasn't previously because I had imgproxy logging set to warn and the Datadog debug logs come in at the info level apparently). It shows that it's reporting runtime metrics at least, but that's about it. I still don't see anything in datadog. I can at least confirm that the tracer is enabled and listening while it hasn't received any traces. Also for the record, there are no netpols in place that might be blocking traffic.
INFO    [2022-01-12T23:07:17Z] Datadog Tracer v1.34.0 DEBUG: Runtime metrics enabled.
INFO    [2022-01-12T23:07:17Z] Datadog Tracer v1.34.0 DEBUG: appsec: not been not enabled during the compilation: please add the go build tag `appsec` to your build options to enable it
INFO    [2022-01-12T23:07:17Z] Datadog Tracer v1.34.0 INFO: DATADOG TRACER CONFIGURATION {"date":"2022-01-12T23:07:17Z","os_name":"Linux (Unknown Distribution)","os_version":"11 (bullseye)","version":"v1.34.0","lang":"Go","lang_version":"go1.17.3","env":"prod","service":"imgproxy","agent_url":"http://<IP_ADDRESS>:8126/v0.4/traces","agent_error":"","debug":true,"analytics_enabled":false,"sample_rate":"NaN","sampling_rules":null,"sampling_rules_error":"","tags":{"cluster":"eno-prod","runtime-id":"8a9d3cdb-ca47-4c07-b47c-941098a86d9f"},"runtime_metrics_enabled":true,"health_metrics_enabled":true,"dd_version":"3.1.3","architecture":"amd64","global_service":"imgproxy","lambda_mode":"false","appsec":"disabled","agent_features":{"DropP0s":false,"V05":false,"Stats":false}}
INFO    [2022-01-12T23:07:27Z] Datadog Tracer v1.34.0 DEBUG: Reporting runtime metrics...
INFO    [2022-01-12T23:07:37Z] Datadog Tracer v1.34.0 DEBUG: Reporting runtime metrics...

 Receiver (previous minute)
  ==========================
    No traces received in the previous minute.
    Default priority sampling rate: 100.0%

Hey @jslusher! That's my bad. Everything should work with the latest build.


Implementing KMS encrypt/decrypt

This adds support for testing the /encrypt and /decrypt endpoints
of Amazon KMS

Coverage decreased (-0.06%) to 94.236% when pulling bdd55161507de8f5f63cbac372b520bd86348b80 on JackDanger:jack/implement-kms-encryption into 094b10cea1d74e372de8e1deefd56e2b6e29df55 on spulec:master.

Thanks for opening this!
It looks like there is an issue with Python3 and the tests. If we can get that fixed, would be happy to merge.

Coverage decreased (-0.06%) to 94.237% when pulling 915ab8c4351239982be7f82930843ac7f8283755 on JackDanger:jack/implement-kms-encryption into 4157abe8de154b7ff00c79d6427c0d774889da3f on spulec:master.

Coverage decreased (-0.08%) to 94.219% when pulling 8c8885e220ea96d6daa65b8f9c672cd5595ac036 on JackDanger:jack/implement-kms-encryption into 4157abe8de154b7ff00c79d6427c0d774889da3f on spulec:master.

Coverage decreased (-0.06%) to 94.237% when pulling 0160a815050e6b49642fa291016f728e20e33e44 on JackDanger:jack/implement-kms-encryption into 4157abe8de154b7ff00c79d6427c0d774889da3f on spulec:master.

Coverage decreased (-0.07%) to 94.231% when pulling c0d55d3dd75c6e3b8ae3a820b8bd599548305275 on JackDanger:jack/implement-kms-encryption into 4157abe8de154b7ff00c79d6427c0d774889da3f on spulec:master.

Coverage decreased (-0.06%) to 94.237% when pulling abd7716d9534bb9d3b75bdf52c3e34e3a29fc4ff on JackDanger:jack/implement-kms-encryption into 4157abe8de154b7ff00c79d6427c0d774889da3f on spulec:master.

Sadly, these changes are impossible to get working under Py3 because the travis build hardcodes the Boto version to 2.36 and Boto didn't support Py3 until 2.40+ for this feature.
Putting the tests behind a version check for now but I've verified that it works properly under modern versions of Boto.

Coverage increased (+0.003%) to 94.304% when pulling ea243761318034d9f7e4e05910b848e3a61aa191 on JackDanger:jack/implement-kms-encryption into 4157abe8de154b7ff00c79d6427c0d774889da3f on spulec:master.

@spulec If we add more recent versions of Boto to the .travis.yml test matrix then I can add a condition to run this test against fixed versions of Boto. Otherwise this is ready to go as-is.

That works for now. Thanks!


Updating multiple lines with name does not work

Bug Description
Updating a vis.line with update='append' does not work if multiple lines are being updated and name= is specified.
This works (multiple lines without name=):
In [28]: vis.line(np.random.randn(1, 10), [0], win='line', update='append')
Out[28]: 'line'

In [29]: vis.line(np.random.randn(1, 10), [1], win='line', update='append')
Out[29]: 'line'

This works (one line with name=):
In [35]: vis.line(np.random.randn(1), [0], win='line', update='append', name='name')
Out[35]: 'line'

In [36]: vis.line(np.random.randn(1), [1], win='line', update='append', name='name')
Out[36]: 'line'

This doesn't work (multiple lines with name=):
In [38]: vis.line(np.random.randn(1, 10), [0], win='line', update='append', name='name')
Out[38]: 'line'

In [39]: vis.line(np.random.randn(1, 10), [1], win='line', update='append', name='name')
Out[39]: ''

In [40]: vis.line(np.random.randn(1, 10), [2], win='line', update='append', name='name')
Out[40]: ''

Only the first set of values are displayed:

This is as expected - multiple lines with a single specified name is undefined behavior for visdom, as we don't yet support specifying multiple names at once. What would you expect the behavior to be if you're specifying the name of a single trace but supplying multiple traces worth of data?

@JackUrb In that case I expect an error. :)

Seems reasonable to me - would you like to add a check to line and open a PR?

@JackUrb Sure. Should this check go into line or scatter?
Btw, is there a way to specify multiple line names with a single call to line?

Both rely on scatter so putting it there would take care of both. As of now there isn't a way to specify multiple names though. I imagine the correct implementation would be taking an array of names, ensuring it's the same length as the number of traces added in, and then looping over the server.py update that handles named updates for each of the names.

closed via #597


SSN Mask seems to Jump

Bug type
Component
Component name
Masking
What happened?
Using the SSN Masking on the Text Field component, seems to Jump when entering data into the component.
Expected behavior
No jumping
Reproduction link
https://try.mudblazor.com/snippet/mOcQuowvTzGrCmfT
Reproduction steps

...
Relevant log output
No response
Version (bug)
6.0.9
Version (working)
No response
What browsers are you seeing the problem on?
Microsoft Edge
On what operating system are you experiencing the issue?
Windows
Pull Request

[ ] I would like to do a Pull Request

Code of Conduct

[X] I agree to follow this project's Code of Conduct

What do you mean by Jump. I did not reproduce the issue.

Same as described here.

@carumsoft @henon On blazor server when applied masking to text field cursor jums at the end while typing.
please refer to the video below.  I am really stuck at it and at a very crucial time. your comments would be helpful.
Thanks
https://user-images.githubusercontent.com/38009549/192199248-bf1e8ae5-e092-4d2a-92e5-0e69c35b4924.mp4

Try trimming, it reduces the size of the mudblazor assemblies drastically because the icons and all the not used stuff is cut away. We have an issue about this: #2424

@henon i have tried to trim by reading many solutions online, but none worked for me. my published filder contains botd .dll and .dll.br but it always serve .dll in browser. any idea what i might be doing wrong? or you have any working example or documentaion.
i have added a Stack Overflow question but not any helpful replies. If you can check the question and suggest some answer it would be very helpful. Thanks.

@henon OKay thanks, @ScarletKuro can you please give me a hint?

Hi.
.br(Brotli) is not related to trimming at all, its compression mechanism.
If we talk about trimming, to enable it you need to set this in your WASM project
<PublishTrimmed>true</PublishTrimmed>
<TrimMode>link</TrimMode>

in .net 7 trimming will be enabled by default.
I don't really understand why you set the BlazorWebAssemblyEnableLinking=false
To understand if trimming is working, you need to publish you application and then go in your _framework of your published app and pay attention to dlls sizes, they should shrink. For example, a non trimmed MudBlazor is about ~8mb, if it's less then trimming is working.
Can't really help your with the brotli tho.

@ScarletKuro Thanks for the useful info, I tried
<PublishTrimmed>true</PublishTrimmed> <TrimMode>link</TrimMode>
but still published folder contains 73 MB of dlls including .dll, .br, and .gz file for each dll.
also, MudBlazor dll size is still 8.3MB and Mudblazor.dll.br size is 976kb.
I am unable to figure out why trimming is not working.

If it's possible to upload the code or at least make a small repro then I can have a better look. Since as for now I have no ideas since usually this should be a trivial https://learn.microsoft.com/en-us/dotnet/core/deploying/trimming/trimming-options?pivots=dotnet-6-0#enable-trimming

@ScarletKuro i was using mudblazor version 6.0.9, updating it to 6.0.16 fixed the issue. Thanks.

Nice. Yea, I didn't think of the version, the trimming was added in 6.0.11+

@ScarletKuro Thanks for your help and time. i find very useful info in the document you provided.
some libraries that don't have trimming enabled by default I am changing it using.
<ManagedAssemblyToLink Condition="'%(Filename)' == 'SixLabors.ImageSharp'">   <IsTrimmable>true</IsTrimmable>   <TrimMode>link</TrimMode>  </ManagedAssemblyToLink>
and the size reduces quite a bit. really helpful. Thanks again


Create Solid Spec Test Suite

Create Test Suite for implementations to check their conformance to the Solid Spec ( https://github.com/solid/solid-spec/issues/135 )

I'll work on this


[Ubisoft's Problem]Claiming Drops issue

it seems Ubisoft's potato server just went down, and it effected other drops's claiming process, i just claimed the PUBG's twitch drop by myself
Is there a way to get all drops in rotation instead of getting stuck on uncollectable drops?

I've pushed a possible fix. I don't have any rewards to claim so I can't test it, but please try it out and let me know. It's in the dev branch.
Or you can checkout the commit directly. it's 86c9418 (listed above in this thread ^)

Roger, I'm testing it and if Don't Starve Together's drops can be successfully claimed, then it is working

It's working.

Thanks for helping me test it!


Realworld Biome usage example

Motivation
This is just a real world example of using Biome in a ESLint/Prettier project. I don't need this to be merged.
Changes
Most of the changes this has caused are:

Trailing commas, I think this a great addition, it saves typing whenever adding a new key and it reduces changed lines of code to review in a PR.
Resorting imports, I'm neutral about this one, but to me the Biome way of sorting makes slightly more sens

Here are my comments on each of the commits:

In the first commit f8da73bd28e033dc190e2e10011de913df8b29cd install and format of code
a743ea64ec2ca93979951e8ebb39c55f26ae6af5 autofix lint
fae2c69e8f50e8280f7a6cc6e857b1b2f35c6352 manually fixed issues that are not auto fixable and (hopefully) trivial
e5d7812f167c7826de46d42eed0391a28f4eb045 this a complex change, the docs have convinced me that this is necessary
dbebe5a45f81b5f3eaca36ac64d7f940d5513b47 the docs have convinced me that this is necessary

@antpaw Is this PR still required? What is expected here?

@sfrehse this is an example for an upcoming RFD about js/ts formating and linting. May we keep this around for another month or two. There is a high chance that Biome gets selected and it would be great if a version of this pr would be merged to Edge.

@sfrehse this is an example for an upcoming RFD about js/ts formating and linting. May we keep this around for another month or two? There is a high chance that Biome gets selected and it would be great if a version of this pr would be merged to Edge.

Ok, fine for me! 🤞


Error while hashing

Processing error on webapp and if i try to add the repository from local machine
i get this message
[e] Error while hashing: it.optJSONArray("source") must not be null

@srihari-humbarwadi thank you for submitting this. The problem is fixed in the latest version of sourcerer-app.

Works fine now! Thanks


Automated tooling to create AWS AMI image with kata-agent and dependencies

Currently it's possible to create a qcow2 image. Investigate the feasibility of building AWS AMI and create a make target for the same

I have a sample packer script to create AWS AMI
https://github.com/bpradipt/cloud-api-adaptor/tree/aws-image/aws/image
Will be raising a PR after few additional round of testing


Wrong "authorized_keys" permissions

The ISO installer creates a new user with wrong ".ssh" folder permission. After installing "sshd" service (please CBL-Mariner team add "openssh-server" package to the ISO image) the user can't upload a key for public-key authentication unless manually changing .ssh folder permissions.
Here's sample user directory listing after fresh install:
tux@mariner [ ~ ]$ ls -la
total 28
drwxr-xr-x 3 tux  tux  4096 Aug 19 18:21 .
drwxr-xr-x 3 root root 4096 Aug 19 18:17 ..
-rw------- 1 tux  tux   210 Aug 19 18:21 .bash_history
-rw-r--r-- 1 tux  tux   178 Nov 24  2020 .bash_logout
-rw-r--r-- 1 tux  tux   645 Nov 24  2020 .bash_profile
-rw-r--r-- 1 tux  tux   452 Nov 24  2020 .bashrc
drwxr-xr-x 2 root root 4096 Aug 19 18:17 .ssh
Last line (in bold) should have user's permission (tux:tux in this case) not root's.

Thanks for making us aware of this issue. Reopening, as we have reproduced the SSH directory permissions bug and identified the root cause.

I'm new to development but if this issue has a fix that's been merged, should this issue remian open?

Thanks for letting me know- I assumed (wrongly) that the "Fixes" mention in the PR would close the issue. Closing.


soroban-rpc: increase transaction retention window to 24 hours

What ?
Requested by product - increase transaction retention window to 24 hours. This would reduce confusion about retention window.
Before increasing the retention window, we should evaluate what the expected memory utilization is going to be and re-align hardware specifications as needed.

@mollykarcher I was asked to add this to the next release; would that be possible for P0 ?

Just to clarify: this is the default value, operators can still configure a different value, right?
Regardless, I suggest having a single configuration value for retention window for both transactions and events

Just to clarify: this is the default value, operators can still configure a different value, right?

Correct, this is just the default value.

Regardless, I suggest having a single configuration value for retention window for both transactions and events

So this sounds a little different than the title/description here, but I'd agree that this is what would actually reduce the user confusion with it. We want to align the retention windows, not simply increase the default transaction retention window. So I think that would mean we'd remove both transaction-retention-window and event-retention-window configs, and replace those with a single retention-window that controls the retention for both.

@mollykarcher I was asked to add this to the next release; would that be possible for P0 ?

I'm in favor. If we go with what I've described above, we'd be removing configuration options which is technically a breaking change, so I'd prefer to get it out before the stable release. It also sounds like minimal work, assuming the memory footprint doesn't take a bit hit. Either way, I think getting it into the stable release is definitely doable.

and re-align hardware specifications as needed.
To be clear: we need to understand the expected memory utilisation and then decide if that is acceptable for hardware requirements.

I've updated the ticket body to cover this, and to describe the product rationale, because in the future we might want to remember why we did this.

With https://github.com/stellar/soroban-tools/pull/1063 merged in, I think it would be safe to have a 16GB machine running a pubnet node with a 24 hour transaction history.

I have not worked on the in-memory events store, but expect that a similar gains could be duplicated there.

@stellarsaur can you run the same profiling you did for RPC with the updated transaction window (to 24 hours), so we can get a sense of how this will affect the memory consumption?

I ran Soroban RPC for 24 hours on a dev box with the updated transaction window to 24 hours on both Futurenet and Testnet. In both cases, I noted the base memory consumption using htop to be about 450Mb after starting Soroban RPC and catching up ingestion. After 24 hours, the memory consumption was about 550Mb and there was no increase in CPU usage. Therefore, we would be using an extra ~100Mb of memory on Futurenet and Testnet.
Caveat here is that there will be more transactions in Pubnet, so memory consumption is most likely to increase more based on that increased volume. However, this is a change that is pretty easy to roll back in case there is an issue (immediate fix for users could be to change the command line flag for the retention window to be smaller while we revert). We could load test by expanding this PR to send actual transactions close to what we're currently receiving, but not entirely sure it's necessary for this.
Example for Futurenet:
sudo docker run -p 8001:8001 -p 8000:8000 -v /home/tylersanderson/config:/config stellar/soroban-rpc:20.0.0-rc3-39 --captive-core-config-path="/config/captive-core-futurenet.cfg" --captive-core-storage-path="/var/lib/stellar/captive-core" --captive-core-use-db=true --stellar-core-binary-path="/usr/bin/stellar-core" --db-path="/var/lib/stellar/soroban-rpc-db.sqlite" --stellar-captive-core-http-port=11626 --friendbot-url="https://friendbot-futurenet.stellar.org/" --network-passphrase="Test SDF Future Network ; October 2022" --history-archive-urls="http://history-futurenet.stellar.org" --admin-endpoint="<IP_ADDRESS>:8001" --endpoint="<IP_ADDRESS>:8000" --event-retention-window=17280 --transaction-retention-window=17280


Better selection system

I haven't look into the code too much but it seems like the selection system is a little off, choosing random dots on the screen rather than larger more acceptable closer food choices. Perhaps putting a human interruption system to choose a specific target and follow the target until some button is hit. This script is pretty amazing, and cool.

Are you saying it's picking dots badly all the time, or only when there's an enemy chasing?

I'm saying when there are good opportunities to go after a smaller massed enemy itd rather choose tiny dots rather than go after a more opportunistic target

You'll have to be more precise than that or I won't change anything. Or record evidence proof of that happening.