Update README_MACOSX_NOTES and fix db/strip_checkpoint

Updates notes with syntax and heuristic changes to deal with mysql > 8.
Removes workarounds added by Joe that do not work any longer in MySQL 8 or 9.
Fixes the script strip_checkpoint so you can run it from your local mushroom-observer directory.

coverage: 93.495% (-0.008%) from 93.503%
when pulling 6b1f77cddf05da25b1a97bd036ddf42fc635b7e6 on rename-macosx-notes
into 64c295cb6afd5d5d551519bbc70656e6c1bb08fe on main.


Possibility to make bindings mockable in LWJGL N (4?)

Question
This is not a question about current major version of LWJGL, but rather a future version (4 or perhaps later?..)
Would it be possible to make bindings a non-utility classes?
For example:
public interface Binding<C, T> {

	T create(C context);
}

public interface GL11 {

	void glLoadIdentity();

	void glPushMatrix();

	void glPopMatrix();

	...
}

Binding<GlContext, GL11> GL11 = GL11C::new;
Binding<GlContext, GL$N> GL$N = GL${N}C::new;

Java provides a way to import static fields, so the old "singleton" style could still be used for developers  who don't want to maintain the binding instance or they are sure that it is safe to store it in a static final field.
This:

Eliminates LWJGL-specific thread local variable stored in JNIEnv function table;
Allows developers to implement a layer on top of GL${N}C (or any binding in general);
LWJGL can utilize this style of the API to generate implementation of bindings with unsupported methods stubbed, instead of doing this.

HotSpot is good at inlining virtual calls, thanks to type profiling, but the approach to structuring the API this way should of course be measured.

Hey @xxDark,
I don't know about the Binding interface, but yes, the current FFM-based binding generation prototype produces instances (implementations of bindings specified as interfaces), i.e. a non-static API. This is very much a work-in-progress, but you can see some examples in the ffm branch:
https://github.com/LWJGL/lwjgl3/blob/ffm/modules/samples/src/test/java22/org/lwjgl/demo/glfw/CustomBindings.java
https://github.com/LWJGL/lwjgl3/blob/ffm/modules/samples/src/test/java22/org/lwjgl/demo/system/windows/CustomKernel32.java
With this approach, a library like GLFW would still be exposed as a static API (the actual generated instance will be encapsulated internally). However, OpenGL(ES) bindings will become instance-based (gl.Clear(...) or ctx.glClear(...) instead of glClear(...)) and that instance will implicitly carry what is GLCapabilities now and will solve all the issues you mention above. A static GL(ES) API may also be available to simplify migration from lwjgl3, but it will suffer from thread-local lookup overhead on every call.


ignore option does not work with "dist-newstyle"

Hi,
The ignore option does not work with a folder named "dist-newstyle", it does work with folders with different names.

Just realised it doesn't work with files/directories with a hyphen in their naming.


breadcrumb spacing still an issue

Breadcrumb spacing with whitespace is still an issue. Please either reopen #17473 or track here.
Thanks

Breadcrumbs are built with flexbox and shouldn't be picking up whitespace. Without a new live demo to reproduce, I'm closing this for now.

@mdo
he live demo was at the end of the above-linked issue. This is happening in v4.3.1
Here it is:
https://codepen.io/francescomazzurco/pen/BaazRLY

Ah sorry about that. Looking at this particular behavior, I don't know how we could fix it off the top of my head. Reformatting the HTML is an easy fix, but that's also not an acceptable answer.

Hey there,
FWIW, simply adding d-inline-flex utility on your active breadcrumb item solves this. So I guess it's safe to add display: inline-flex to .breadcrumb-item, isn't it?

Adding display: inline-flex will indeed fix this. Maybe we can just use display: flex since the inline part is moot because .breadcrumb already has display: flex applied to.
We should add this by default to our .breadcrumb-item, feel free to open a PR for this.

@MartijnCuppens Does this need to be done in V5, or V4 — maybe both? I'd be pleased to open dedicated PR if it can help.

Both is fine, just open a PR for master and we'll cherry-pick this in v4.


application has stopped !

application has stopped when selecting several images for the first time in android,
Please new update! thanks!

I think i know the reason why that happens. But it would be great if you could give me some more details, like the error stack trace and your flutter doctor -v output.
Thank you.

Closing as no answer.


Examples are not saved using Docker

I am unable to find the files while running the example
python3 -m manim example_scenes.py SquareToCircle -l
This is the output I'm getting, but there is no folder past /videos/

Using Docker, Windows 10.
Thanks in advance.

I haven't been able to reproduce this. Can you give some more details? Are you bind-mounting manim in or cloning it from the container?

I haven't been able to reproduce this. Can you give some more details? Are you bind-mounting manim in or cloning it from the container?

Cloning.
I should probably try to bind as well and report back

No files are shared between the docker container and the host by default, so you'll have to bind mount a directory into the container to make the changes persist.

I've tried binding and replaced my absosulte math to my manim repo from this instruction:
docker run -itv /absolute/path/to/your/local/manim/repo:/root/manim eulertour/manim
Docker asked for my system's password, which I included and can now access my hard drive.
Running the example, I get:
`\path_to_python3\ : no module named 'manim'.
So I installed manim with 'pip3 install manim'
However, running the example now prints:
`No module named manim.main; 'manim' is a package and cannot be directly executed.
I've made sure that manim is installed, am I missing something?
Am I skipping something?
I'm new to this, so sorry for the inconvinience.

It seems that you forgot to cd into the manim directory and python is getting confused thinking you want it to execute a directory.

So I installed manim with 'pip3 install manim'

I'm surprised that that did anything at all.

I made sure that I cd into manim, but I still get the error.


Wrong conditional type breaks code

TypeScript Version:  latest (nightly playground)

Search Terms: infer generic const
Code
https://www.typescriptlang.org/play/?ts=4.0.0-dev.20200701&ssl=2&ssc=65&pln=2&pc=69#code/FAFwngDgpgBA8gIwM5QE4DcCGCA2UA8AKgHwwC8MACqgPYC2AlikcQNwwD0HMAVgK5IQMAGaYA1gwB2AcxioAHjyQwayNFlyxw0YKEixCqTJKTCaqOgEYW5GIRhR5IKJIAmy6vSYEpwtDABVUgB+eDUMbDx8IJgALjCUCM0WVj1oOyMTMwsAJhsKRESNKJJUtK1LW0NjU3MrfAQaGjxjNnKYEByqzNrchqaWyTZObiQACxo+HFcYMAYoaZgkTDotfRhMZRBLABoYBD4hVxooZUkaEF0OACpgRpAxjJrsqw23J6y6roBlAAk4AIAGQAIjBjg55JgAMYgHBgDpjWDLVYIqSybIddYAIkazSgxixugAmgBRezbN4zTobVCwYEASQAYoySQAlEkAOXJ+iQugA6r8iTAGBs6DAIDRBGjUUhYrptBV9rTxMoFEoYAAKanHU4wc4gACUcuAUJoJiEqmUsW2FEkUxwG2UxjAqUtADoIAxoBq6JgIBqaGRiABmA0G9hcByoWioXQwa4cIA
both Transform1 and Transform2 SHOULD do exactly the same thing for type "boolean"
YET t1 and t2 are DIFFERENT types
WHY i am posting this:
type t1 breaks rxjs (t2 does not):
const obs :t1= null as any;
obs.pipe(map(o=>3)); // error

a far BETTER example:
https://www.typescriptlang.org/play/?ts=4.0.0-dev.20200701#code/FAFwngDgpgBAKgJwIYDsDOAzA9ggtgRgB44A+GAXnhigA8QoUATNGABQS1wEs0pCuUGKAhgBVMgH4YAQQTIwhcTABcMuUgWkA3KEixEqTDlwAmYmUqz55nbugwQ+CvGTpseIgCMsWADZRUEh1wexATZwM3YzNvPwCUIJgAeiSYNAALLABXX0YYMC4oXLSkXFgQ2CQWRwAaGE8skBhGLCgWFCwQYGAANyQRPoR8VUdnFBzfGCqplDAdQZhBkxHwynHfSenUOe7B-AA6XCQIAAosCjIAZgBKLWTU4Q4EXv6TQ+Ozi5gbu5SYDuochwQA
a workaround would be ok with me (how i can transform t1 back to t2?)

Distributive conditional types
Use this instead:
type Transform1<T> = [T] extends [Promise<infer U>] ? Observable<U> : Observable<T>;

Ok thanks, but unfortunately not getting anywhere. Is THIS a bug?
https://www.typescriptlang.org/play/?ts=4.0.0-dev.20200701&ssl=5&ssc=33&pln=5&pc=40#code/C4TwDgpgBAKg9gQQE5IIYgDwwHxQLxQDaMAulBAB7AQB2AJgM5EAKScAtgJYMQac0AzCEigBVbCQBQUKAH4oyNJnHSZUAFwKU6LNgDcqyaEhQAEhAA2kJFnJVajKAAoAlHmyoaIXHniKdAEoQwACuSDQw4Lw4+pKSAPTxdpAAxsBQwHBQAEbQDKjs0MYQDAA0OSHpqEjQAHIA8jBGUVBBDCEW6QTmVsIYrvi42XBwFhCescWtJR3AAEwEftqYQaHhkZD9LoM5I2MTsUA

Please don't just paste raw playground links, it makes it very difficult for us to read without inline code samples and makes it impossible for other to use search terms to find similar issues.

Sorry, I understand. Still, I'm unsure if any of the code samples are bugs because of missing feedback. I will do my best to double check I have actually found bugs, and will open new issue(s) if that is the case and in a proper manner.


Update CAPI to v1.8.1

Add a build-e2e target to
Clean up existing build target deps
refactor tests and controllers to match updated dependencies

@thunderboltsid don't you need also to update devbox clusterctl dependency to 1.8.1 ??

nixpkgs don't have 1.8.1 yet only 1.8.0.


SPIKE: Design DOD for EA approval and billing for cloud compute and storage consumption

Describe the issue
Ministry teams will be working with us under our Early Adopter Program as of late November, 2020. We need a process whereby they will gain Expense Authority approval, preferably for a draw-down amount that they can spend on cloud infrastructure without needing to repeatedly request approval.
Which Sprint Priority is this issue related to?
1
Additional context

Mirella is doing the work and we are reaching out for updates

Definition of done

Collaborate with Belinda Lucoe and Mirella Standbridge to design a process that will work for OCIO and for ministries
Review with Gen, Paul, Julian
Document and diagram for clarity

Reviewed with PO, 2021-01-05, and amended wording. Reviewed with Early Adopter PO 2021-01-06 - awaiting review and approval with MoH Expense Authority (Jeff Aitken, who returns to work 2021-01-12)

Reviewed with PO, 2021-01-05, and amended wording. Reviewed with Early Adopter PO 2021-01-06 - awaiting review and approval with MoH Expense Authority (Jeff Aitken, who returns to work 2021-01-12)


Add frontend TLS/SSL

/botio test

From: Bot.io (Main)

Received
Command cmd_test from @aayanl received. Current queue size: 0
Live output at: http://aayanl.tech:9000/80f369f27f9e1de/output.txt

From: Bot.io (Main)

Received
Command cmd_preview from @aayanl received. Current queue size: 1
Live output at: http://aayanl.tech:9000/b908d05fc6e9ff6/output.txt

/botio preview

From: Bot.io (Main)

Success
Full output at http://aayanl.tech:9000/80f369f27f9e1de/output.txt
Total script time: 0.72 mins

From: Bot.io (Main)

Success
Full output at http://aayanl.tech:9000/b908d05fc6e9ff6/output.txt
Total script time: 0.02 mins
Published
You can view your repo files at: http://aayanl.tech:9000/b908d05fc6e9ff6

:+1:


source_device_iden support

Hi! I've added the support of custom source_device_iden along pushes. It allows to specify explicitly specify from which device comes the push. It envolved minor changes to the code, as I simply created overloading methods for each of the send methods.
I also accidentally reformatted the code a bit, feel free to decline this pull request and I'll take the time to insert my code more smoothly into the project.
See https://docs.pushbullet.com/#pushes for more information on the feature.

I just added a bug fix (c3693d3) which solve the issue of sending non-alphanumerical characters such as the degree symbol.

Although I am not Robert...
Could you perhaps close this pull request and send two seperate ones, the first just adding the source_device_iden, and a second one afterwards that does all the reformating? This would make reviewing your changes much easier.

Ah, sorry, I didn’t see it.
…
OK I think it’s merged.
-Rob

On Sep 18, 2015, at 6:41 AM, Hakan Tandogan<EMAIL_ADDRESS>wrote:
Although I am not Robert...
Could you perhaps close this pull request and send two seperate ones, the first just adding the source_device_iden, and a second one afterwards that does all the reformating? This would make reviewing your changes much easier.
—
Reply to this email directly or view it on GitHub https://github.com/rharder/jpushbullet2/pull/5#issuecomment-141440739.


testing: Example test with runtime.Goexit hangs

What version of Go are you using (go version)?

$ go version
go version go1.15 linux/amd64

(Also verified on 1.14 on both linux and darwin)
Does this issue reproduce with the latest release?
Yes
What operating system and processor architecture are you using (go env)?
go env Output
$ go env
GO111MODULE="on"
GOARCH="amd64"
GOBIN=""
GOCACHE="/home/user/.cache/go-build"
GOENV="/home/user/.config/go/env"
GOEXE=""
GOFLAGS=""
GOHOSTARCH="amd64"
GOHOSTOS="linux"
GOINSECURE=""
GOMODCACHE="/opt/go/path/pkg/mod"
GONOPROXY=""
GONOSUMDB=""
GOOS="linux"
GOPATH="/opt/go/path"
GOPRIVATE=""
GOPROXY="https://proxy.golang.org,direct"
GOROOT="/home/user/.gimme/versions/go"
GOSUMDB="sum.golang.org"
GOTMPDIR=""
GOTOOLDIR="/home/user/.gimme/versions/go/pkg/tool/linux_amd64"
GCCGO="gccgo"
AR="ar"
CC="gcc"
CXX="g++"
CGO_ENABLED="1"
GOMOD="/home/user/go-test/go.mod"
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
PKG_CONFIG="pkg-config"
GOGCCFLAGS="-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build701379955=/tmp/go-build -gno-record-gcc-switches"

What did you do?
Used runtime.Goexit in an example test from the main test goroutine.
package main

import "runtime"

func ExampleGoexit() {
        runtime.Goexit()
        // Output:
}

What did you expect to see?
A failure, similar to when runtime.Goexit is used in a test,
package main

import "runtime"
import "testing"

func TestGoexit(t *testing.T) {
        runtime.Goexit()
}

> go test -v -run Test
=== RUN   TestGoexit
--- FAIL: TestGoexit (0.00s)
panic: test executed panic(nil) or runtime.Goexit
[...]

What did you see instead?
The example test hangs (until the test timeout is hit):
> go test -v -run Example -timeout 10s
=== RUN   ExampleGoexit
--- PASS: ExampleGoexit (0.00s)
panic: test timed out after 10s

goroutine 8 [running]:
testing.(*M).startAlarm.func1()
	[...]/go/src/testing/testing.go:1609 +0xe5
created by time.goFunc
	[...]/go/src/time/sleep.go:167 +0x45
exit status 2
FAIL	goexit_test	10.008s

I can send a SIGQUIT to get the backtrace:
=== RUN   ExampleGoexit
--- PASS: ExampleGoexit (0.00s)
^\SIGQUIT: quit
PC=0x7fff6a9c4766 m=0 sigcode=0

goroutine 0 [idle]:
runtime.kevent(0x7ffe00000003, 0x0, 0x0, 0x7ffeefbfece8, 0x40, 0x7ffeefbfecc0, 0x0)
        /usr/local/Cellar/go/1.14.2_1/libexec/src/runtime/sys_darwin.go:355 +0x39
runtime.netpoll(0x25408e43c, 0xadf60b77b01)
        /usr/local/Cellar/go/1.14.2_1/libexec/src/runtime/netpoll_kqueue.go:120 +0xae
runtime.findrunnable(0xc000026800, 0x0)
        /usr/local/Cellar/go/1.14.2_1/libexec/src/runtime/proc.go:2323 +0x72b
runtime.schedule()
        /usr/local/Cellar/go/1.14.2_1/libexec/src/runtime/proc.go:2520 +0x2fc
runtime.park_m(0xc000000180)
        /usr/local/Cellar/go/1.14.2_1/libexec/src/runtime/proc.go:2690 +0x9d
runtime.mcall(0x105f4a6)
        /usr/local/Cellar/go/1.14.2_1/libexec/src/runtime/asm_amd64.s:318 +0x5b

In the Go playground, this triggers a deadlock:
https://play.golang.org/p/xaSFhxBPeKB

Is it the documented behavior?

Thank you for filing this @prashantv, and thank you @go101 for responding to @prashantv’s question. Indeed as @go101 points out, that is the behavior of Goexit(), and in the main test code, there are other goroutines running in the background and as documented it can’t return until all the other goroutines have. I shall close this issue, but thank you again.

Hi @odeke-em, I think this is a testing package issue, since TestGoexit works correctly (as I documented in my issue), while ExampleGoexit hangs. Shouldn't they both behave in the same way?
The Goexit function is expected to end the goroutine, but the testing package handles this correctly for TestX functions, but not for ExampleX functions.

@prashantv there are other goroutines running for Example as I had mentioned and for example if you see the implementation in https://github.com/golang/go/blob/4fc3896e7933e31822caa50e024d4e139befc75f/src/testing/run_example.go#L21
by you invoking runtime.Goexit() you are killing that goroutine in its main without ever returning yet there are other goroutines that haven't yet been terminated and are waiting for output. This is an implementation detail about Example tests that I don't think needs to be changed.
You can validate that the goroutines are running by printing the stack of the entire system like this
package main

import (
        "runtime"
)

func ExampleGoexit() {
        buf := make([]byte, 1024)
        for {
            n := runtime.Stack(buf, true)
            if n < len(buf) {
                break
            }
            buf = make([]byte, 2*len(buf))
        }
        println(string(buf))
        runtime.Goexit()
        // Output:
}

which will produce
$ go test
goroutine 1 [running]:
github.com/odeke-em/bugs/golang/41084.ExampleGoexit()
	/Users/emmanuelodeke/Desktop/openSrc/bugs/golang/41084/example_test.go:10 +0x9f
testing.runExample(0x1140b3b, 0xd, 0x1148c80, 0x0, 0x0, 0x0, 0x0)
	/Users/emmanuelodeke/go/src/go.googlesource.com/go/src/testing/run_example.go:62 +0x209
testing.runExamples(0xc00009ce80, 0x12149c0, 0x1, 0x1, 0xbfcacc4fada05fc8)
	/Users/emmanuelodeke/go/src/go.googlesource.com/go/src/testing/example.go:44 +0x1af
testing.(*M).Run(0xc0000cc000, 0x0)
	/Users/emmanuelodeke/go/src/go.googlesource.com/go/src/testing/testing.go:1354 +0x2cd
github.com/odeke-em/bugs/golang/41084.TestMain(...)
	/Users/emmanuelodeke/Desktop/openSrc/bugs/golang/41084/it_test.go:8
main.main()
	_testmain.go:45 +0x165

goroutine 19 [runnable]:
syscall.syscall(0x1076d00, 0x6, 0xc000102000, 0x8000, 0xffffffffffffffff, 0xffffffffffffffff, 0x23)
	/Users/emmanuelodeke/go/src/go.googlesource.com/go/src/runtime/sys_darwin.go:63 +0x2e
syscall.read(0x6, 0xc000102000, 0x8000, 0x8000, 0x1208840, 0x1723fd8, 0x100a3bf)
	/Users/emmanuelodeke/go/src/go.googlesource.com/go/src/syscall/zsyscall_darwin_amd64.go:1242 +0x66
syscall.Read(0x6, 0xc000102000, 0x8000, 0x8000, 0x72, 0x0, 0x0)
	/Users/emmanuelodeke/go/src/go.googlesource.com/go/src/syscall/syscall_unix.go:187 +0x49
internal/poll.ignoringEINTRIO(0x11492d0, 0x6, 0xc000102000, 0x8000, 0x8000, 0x1723fd8, 0x1106d01, 0x10100000111eb80)
	/Users/emmanuelodeke/go/src/go.googlesource.com/go/src/internal/poll/fd_unix.go:563 +0x52
internal/poll.(*FD).Read(0xc0000a41e0, 0xc000102000, 0x8000, 0x8000, 0x0, 0x0, 0x0)
	/Users/emmanuelodeke/go/src/go.googlesource.com/go/src/internal/poll/fd_unix.go:155 +0x149
os.(*File).read(...)
	/Users/emmanuelodeke/go/src/go.googlesource.com/go/src/os/file_posix.go:31
os.(*File).Read(0xc0000a2030, 0xc000102000, 0x8000, 0x8000, 0x0, 0xc000040700, 0x100645d)
	/Users/emmanuelodeke/go/src/go.googlesource.com/go/src/os/file.go:116 +0x71
io.copyBuffer(0x11694b8, 0xc000100000, 0x11693d8, 0xc0000a2030, 0xc000102000, 0x8000, 0x8000, 0xc00008c120, 0xc0000407a8, 0x1005eab)
	/Users/emmanuelodeke/go/src/go.googlesource.com/go/src/io/io.go:409 +0x12c
io.Copy(...)
	/Users/emmanuelodeke/go/src/go.googlesource.com/go/src/io/io.go:368
testing.runExample.func1(0xc0000a2030, 0xc00008c1e0)
	/Users/emmanuelodeke/go/src/go.googlesource.com/go/src/testing/run_example.go:37 +0x85
created by testing.runExample
	/Users/emmanuelodeke/go/src/go.googlesource.com/go/src/testing/run_example.go:35 +0x176

and you'll see the goroutine that's still waiting in there.

I understand why it's hanging, but it doesn't hang for TestX functions, since there's explicit logic to detect and handle this case,
https://github.com/golang/go/blob/4fc3896e7933e31822caa50e024d4e139befc75f/src/testing/testing.go#L1069
This logic doesn't exist for example tests, and so it hangs, which doesn't seem ideal. It seems beneficial to users to detect a runtime.Goexit or panic(nil) in an example test the same way as a TestX function, and in general for consistency.
Perhaps I'm missing a reason for why Example tests should not have consistent behaviour with standard test functions, I thought it might have just been overlooked.

Thank you for the follow-up question @prashantv, you raise a great concern which I don't have an answer to off the top of my head, thus I shall re-open this for investigation and other comments.

@prashantv I misunderstood the issue and incorrectly renamed it with the runtime package. It's been corrected.

/cc @mpvl

In theory we could run each Example function in its own goroutine, and move the output-checking to a defer statement so that it can trigger even in case of a Goexit.
That said, use of runtime.Goexit outside of the testing package itself should be rare enough that I'm not sure this is worth the risk of the refactoring. (If someone wants to contribute a fix, we can see just how invasive it is and decide at that point.)

@bcmills I don't know refactoring to run Example in its own goroutine is the planned approach. But the current examples are executed sequentially, it seems that  I can send a simple CL to fix what was reported originally. Should I do that?

If the examples are executed sequentially on the same goroutine, then a runtime.Goexit in an Example is always wrong. A change to panic in that case instead of deadlocking seems like it would be fine, but it still wouldn't let you safely write that ExampleGoexit function.

@bcmills Thanks for the quick response. What's the behavior to safely write ExampleGoexit? I thought the bug report is expecting to fail the ExampleGoexit and panicking on errNilPanicOrGoexit whereas the current behavior is getting a PASS on ExampleGoexit with a long pause.


Cache files for vernon and york_region

[ ] ca/on/york_region  - Current cached file is not a valid zip file.  Replace with this one and remove skip tag
[ ] ca/bc/vernon - Old url not available for direct download. Move dropbox file to the OA cache and remove skip tag

@iandees Could you cache these files for me?


Editing Snapshot URL doesn't allow new proposal

trying to add the Snapshot space but the button remains disabled after we enter the snapshot URL.
any clue why that would happen on a multisig (he’s connected from a wallet as a signer)

https://decentdao.slack.com/archives/C06QZTUTKRC/p1719941778542629

This was a false bug report, closing


Fix mmap/fs_munmap.c:122:15: error: ‘struct fs_rammap_s’ has no member named ‘kernel’

Summary
Minor fix
Impact
Fix build break with CONFIG_FS_RAMMAP
Testing
local daily build

@xiaoxiang781216 See https://github.com/apache/incubator-nuttx/pull/4143/checks?check_run_id=3056521753#step:7:321

Done.


The Powershell script is displayed incorrectly above with '&quot' showing instead of a single quote.  Looks like the same may be true in the DSC section too.

The Powershell script is displayed incorrectly above with '&quot' showing instead of a single quote.  Looks like the same may be true in the DSC section too.   If you copy with ctrl+C or use the copy button, it also copies &quot instead of an actual single quote.

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 1826d7a4-27c5-7238-0bf0-6e2dd9118cde
Version Independent ID: ca92fdd3-48f3-6577-95f1-2c058257bf57
Content: Wire Data solution in Log Analytics
Content Source: articles/log-analytics/log-analytics-wire-data.md
Service: log-analytics
GitHub Login: @MGoedtel
Microsoft Alias: magoedte

@antonihanus thanks for the catch.


Failed to execute 'setRequestHeader' on 'XMLHttpRequest':

I am getting this error:
Error: Failed to execute 'setRequestHeader' on 'XMLHttpRequest': 'function (xhr) {
config.__XHR = xhr;
xhr.upload.addEventListener('progress', function(e) {
if (config.progress) {
$timeout(function() {
config.progress(e);
});
}
}, false);
//fix for firefox not firing upload progress end, also IE8-9
xhr.upload.addEventListener('load', function(e) {
if (e.lengthComputable) {
$timeout(function() {
config.progress(e);
});
}
}, false);
}' is not a valid HTTP header field value.
at http://localhost:8282/lifeengage-groupuw-ui/resources/js/angular/angular.js:7855:17
at forEach (http://localhost:8282/lifeengage-groupuw-ui/resources/js/angular/angular.js:307:20)
at http://localhost:8282/lifeengage-groupuw-ui/resources/js/angular/angular.js:7853:7
at sendReq (http://localhost:8282/lifeengage-groupuw-ui/resources/js/angular/angular.js:7721:9)
at $http.serverRequest (http://localhost:8282/lifeengage-groupuw-ui/resources/js/angular/angular.js:7455:16)
at wrappedCallback (http://localhost:8282/lifeengage-groupuw-ui/resources/js/angular/angular.js:10696:81)
at wrappedCallback (http://localhost:8282/lifeengage-groupuw-ui/resources/js/angular/angular.js:10696:81)
at http://localhost:8282/lifeengage-groupuw-ui/resources/js/angular/angular.js:10782:26
at Scope.$eval (http://localhost:8282/lifeengage-groupuw-ui/resources/js/angular/angular.js:11697:28)
at Scope.$digest (http://localhost:8282/lifeengage-groupuw-ui/resources/js/angular/angular.js:11525:31) angular.js:9199

any other answer

@ckken this is a closed issue if you have the same issue post your html here.

Hi, I have got the same issue:
Error: Failed to execute 'setRequestHeader' on 'XMLHttpRequest': 'function (xhr) {
          if (!xhr || !(xhr instanceof XMLHttpRequest)) return;
          config.__XHR = xhr;
          if (config.xhrFn) config.xhrFn(xhr);
          xhr.upload.addEventListener('progress', function (e) {
            e.config = config;
            notifyProgress(getNotifyEvent(e));
          }, false);
          //fix for firefox not firing upload progress end, also IE8-9
          xhr.upload.addEventListener('load', function (e) {
            if (e.lengthComputable) {
              e.config = config;
              notifyProgress(getNotifyEvent(e));
            }
          }, false);
        }' is not a valid HTTP header field value.

I am using latest version of ng-file-upload and angular 1.5.0 (but tested it with 1.4.7 too, same error). I just copied the example, so my HTML of directive with upload looks like:

    {{field.label}} *

      {{field.help}}

    Drop File:

Drop pdfs or images here or click to upload

File Drag/Drop is not supported for this browser

    Files:

{{f.name}} {{f.$error}} {{f.$errorParam}}

    Upload Log:

{{log}}

My upload service:
scope.$watch('files', function() {
				scope.upload(scope.files);
			});

			scope.log = '';

			scope.upload = function(files) {
				if (files && files.length) {
					for (var i = 0; i < files.length; i++) {
						var file = files[i];
						if (!file.$error) {
							Upload.upload({
								url: 'https://angular-file-upload-cors-srv.appspot.com/upload',
								data: {
									file: file
								}
							}).progress(function(evt) {
								var progressPercentage = parseInt(100.0 * evt.loaded / evt.total);
								scope.log = 'progress: ' + progressPercentage + '% ' +
									evt.config.data.file.name + '\n' + scope.log;
							}).success(function(data, status, headers, config) {
								$timeout(function() {
									scope.log = 'file: ' + config.data.file.name + ', Response: ' + JSON.stringify(data) + '\n' + scope.log;
								});
							});
						}
					}
				}
			};

And I am including shim before angular.js:

...

Any idea what could be wrong?

Could be a conflict with another library, try to create a jsfiddle showing the error that would help figuring out the issue.

Ok I found out that the problem was caused by PACE library (http://github.hubspot.com/pace/docs/welcome/)

Ok, this fix from @Fabbok1x seems to be working - https://github.com/danialfarid/ng-file-upload/issues/832

I have the same problem and my dep are injected via gulp so...i create a small patch as describe in #832
Bower : pace-ng-file-upload-inlinepatch 0.0.6
https://github.com/Dufgui/pace-ng-file-upload-patch

I have archaic socket.io 1.2 and for some reasons can't change this.
According to source code https://github.com/danialfarid/ng-file-upload/blob/750068e259c47c0ced7e8dbee570dc5d1875f487/src/upload.js#L69
The possible workaround is  Upload.upload({ ... disableProgress: true });


In graph view, Environment and Setting menus are not accessible

Build from master June 9th
Steps:
1 Add a project
2. Add a couple of services and a couple of balancers
3. Click on project name to go into project
4. Now click on graph view icon
5. Try to click on items in settings or environment menus
Results:
Can't click on menu items,  graph view is on top of menu
Expected:
To be able to click on menu items

Build from master
Verified fixed


Document 'influx pkg' command

PR: https://github.com/influxdata/influxdb/pull/15937
We need to document the new influx pkg command when allows users to create custom packages of dashboards, buckets, lables, tasks, etc. We also need to create a doc that walk through how to use the pkg system in general.

[x] influx pkg doc
[ ] Using InfluxDB packages

The pkg command work is wrapping up, so you should be good to doc it. let me know if you have questions.

The influx pkg command has been fully documented. Closing this issue and linking it to #706.


Minor copy editing fixes

@tylerbutler are you still intentionally blocking this review? you need to re-review to unblock after doing change-requested.

@anthony-murphy No, I got lost in my notifications... reviewed and approved. Sorry for the delay, @scarlettjlee.


Active timestamp in carry-over items is not updated

Describe the bug
When carrying-over an item from the previous day, the active timestamp is not updated, hence the entry no longer shows in the agenda.
To Reproduce
Steps to reproduce the behavior:

have the following in the previous day journal entry:

* TODO testing
 <2020-10-21>

open the current day (October 22) journal entry (with C-u org-journal-new-entry)
The item is carried-over as

* TODO testing
 <2020-10-21>

Expected behavior
The item is carried-over as
* TODO testing
 <2020-10-22>

Your Emacs Configuration
(use-package! org-journal
  :config
  (map!
   (:leader
    (:n "d o j" 'org-journal-new-entry)))
  :custom
  (org-journal-dir deft-directory)
  (org-journal-cache-file "~/.emacs.d/.local/org-journal.cache")
  (org-journal-date-prefix "#+TITLE: ")
  (org-journal-time-prefix "* ")
  (org-journal-file-format "%Y-%m-%d.org")
  (org-journal-date-format "%Y-%m-%d (%A)"))
(setq org-journal-enable-agenda-integration t)

The regex is wrong https://github.com/bastibe/org-journal/blob/master/org-journal.el#L833, also https://github.com/bastibe/org-journal/blob/master/org-journal.el#L839 needs to be updated.

Should be fixed with commit 00f3d39.

It's almost fixed: it works for the last item to be carried over. If I have this for October 22:
* TODO test 1
 <2020-10-22>

* TODO test 2
 <2020-10-22>

after carry-over to October 23, I get this:
* TODO test 1
 <2020-10-22>

* TODO test 2
 <2020-10-23 Fri>

hmm, in test it does work. Can you post a complete entry please.

Would be appreciated if you can make a PR with some test journals files based on you configuration, and put it under tests/journals/daily. Than I can write a test similar to the test =org-journal-scheduled-carryover-test= in tests/org-journal-test.el
Thanks!

I created a PR. I'm not sure this is what you expected. The behavior I get currently is that only the last entry has its inactive stamp updated.

Thanks! Indeed, it doesn't work with your configuration. I'll debug it and let you know when I pushed a fix for it.

I confirm it works. Thanks!


Enable support on CentOS-6

The end goal for these CentOS6-related mods is to support a manylinux2010 build environment on ROCm.
On CentOS-6, the 'numactl-libs' package does not exist.  The same functionality belongs to the 'numactl' package instead.  Additionally, CentOS-6 doesn't include a '/etc/os-release' file, so we grab the details from the '/etc/centos-release' file instead (if it exists).

Just did a rebase to grab the newest commits on 'develop' that conflicted with this PR.


unreal_asset: implement double const kismet expression

Let me know if you want me to write a test or anything

You need to sign your commits

Ok, it's signed now.


Update DatePicker to load it's own version of Auro Input, similar to how ComboBox handles this

Describe the bug
There are build issues when a page uses the latest version of Auro Input, and has Datepicker on it, since DatePicker uses a slightly older version of Auro Input/
To Reproduce
Steps to reproduce the behavior:

Make a page with Auro Input and DatePicker
Attempt to build the page

Expected behavior
Build is successful
Additional context
To Be solved the way that we solved this issue with Combobox: https://github.com/AlaskaAirlines/auro-combobox/issues/127

See issue for additional context

https://github.com/AlaskaAirlines/auro-datepicker/issues/163


Add note for naming Output class

It seems there's some confusion with custom return objects. This PR intends to avoid this confusion by adding a not in the docs.

Ah yes, I remember

probably unrelated (second comment in the issue thread that you've linked), but i also raised a PR for updating the deprecated list type usage in one of the examples a while ago


Expose a __version__ attribute

It would be useful if the main __init__.py exposed a __version__ attribute. While it's not required that a packge have one, it is fairly standard and a lot of tools expect it to exist. It seems the tool is currently using scm_version from setuptools-scm. Not sure what the exact right way to use this is, but modifying setup.py to include:
setuptools.setup(
...
    use_scm_version={
        'write_to': 'dataframe_image/_version.py',
        'write_to_template': '__version__ = "{version}"',
        'tag_regex': r'^(?P<prefix>v)?(?P<version>[^\+]+)(?P<suffix>.*)?$',
    },
...
)

Seems like a good starting point. Then __init__.py can include from ._version import __version__.

Thanks for your good idea and I'll put it into project next release.

Finished at https://github.com/dexplo/dataframe_image/commit/cf3351dd5179f3ed0f11868184fe848cca2d0298


[WFLY-18984] Remove the microprofile-rest-client dependency from the …

…jaxrs-server layer.
https://issues.redhat.com/browse/WFLY-18984

@bstansberry sorry to do the ping Brian for review thing but I think in this case you were discussing the scope with James.

Thanks @jamezp


BDE-Logo-Change-and-MainNet-logo

Logo Update for BDE Coin
I agree to not ping anybody on Discord/Twitter/email about this pull request. Instead I will inquire by posting a new comment in the pull request if needed.

PRs are reviewed in bulk and and can take up to two weeks to be merged.
This repository is managed using an auto merge action. Please ensure your PR has no deleted lines, and it will be merged.
Please provide the following information for your token.
Please include change to the src/tokens/solana.tokenlist.json file in the PR.
DON'T modify any other token on the list.
At minimum each entry should have

Token Address: H5gczCNbrtso6BqGKihF97RaWaxpUEZnFuFUKK4YX3s2
Token Name: Big Defi Energy
Token Symbol: BDE
Logo: https://raw.githubusercontent.com/bigchickendefi/bigchicken/main/bde3.png
Link to the official homepage of token: bigdefienergy.com
Coingecko ID : https://www.coingecko.com/en/coins/big-defi-energy

just updated the BDE Logo! If you have any questions Ask Me!

This will include a "deletion" although its just changing of the LOGO URI (Url) for the BDE Token...
Again if you have questions, please ask.

updated to include only one logo url


Fixes materials library's testing page

On Ubuntu, material library's testing page (localhost:1338/materialsLibrary/index.html, served by gulp webserver) is broken because several paths are not found. This patch fixes these paths.

Thanks a lot!


implemented indices page

Base on pull #7 , created indices page without sorting feature.

Created pull #17


bbup to query nargo --version and lookup a compatible version of bb to install if no version is provided.

Currently the only tracking of the compatibility between nargo and bb versions is done in the docs readme and users are expected to copy this across into the CLI.
An alternative solution is that we put this into a json file or similar (or even just leave it as a plain text file), and if no version is specified by the user we have bbup query nargo --version, extract the version number and then perform a lookup against this mapping file on github. bbup can then go download a compatible version of bb for the version of nargo the user has installed.

Happy Case:

Dev runs bbup --noir-version 0.34.0
bbup automatically installs bb 0.55.0 (the version tested compatible with Noir 0.34.0)

Does this Issue also imply a prerequisite Issue that ensures:

bb tests against Noir versions
bb stores a list of bb <> Noir version compatibilities


US 01.01.01

As a doer, I want to add a habit, giving it a brief title, reason, and date to start.
Completion Requirements:
-User has ability to click a button that opens a "Add Habit" UI
-Add habit UI permits user to enter data regarding the habit and save it to their account
Halfway Checkpoint Completion:
-Fully complete by halfway checkpoint

Add button
New activity/fragment to edit title,reason,date
Save the habit in firebase

Encountered Database login issue ("java.lang.AssertionError: Method getAlpnSelectedProtocol not supported for object SSL socket")

Encountered Database login issue ("java.lang.AssertionError: Method getAlpnSelectedProtocol not supported for object SSL socket")

Try adding to this to your build.gradle:
implementation "io.grpc:grpc-okhttp:1.32.2"
Should hopefully resolve the issue

Initial functionality fully completed.  New functionality (public vs. private) not worked on at this juncture.  Creating separate issue to account for new user story requirements. Considering this story closed (as all initial requirements met).


Hover over links in IE: Remove underline on preceding icons

When hovering over a link, the preceding icon is underlined in IE. In other browsers the behavior (Firefox, Chrome, Opera) is correct, i.e. only the link is underlined but not the icon.
e.g. https://swiss.github.io/styleguide/en/typography.html#04-typography-09-top-link

Please precise which version of IE if you can. Thanks

IE version

I am not able to fix this issue in a simple way. Its a IE only bug for pseude Element styling.
The current implementation looks like this:
Back to top
That I'm able to style this, I have to create a span element only for the text like this:
Back to top
This means I have to change every link in the whole project. I think the effort to fix this issue is way to high for such a little styling bug which doesn't affect a lot of people. @bit-pro-iew-eui Please assess if I really should fix it.

@janissbinder Did you try the solution described here: https://stackoverflow.com/a/8820459

@almeidap It's unfortunately already styled like this

Won't fix


2.4.2: Multiple Placeholders issue

I have an issue that seems to occur with the following temlpate:
{% extends "base.html" %}
{% load cms_tags sekizai_tags %}
{% load staticfiles %}
{% load menu_tags %}
{% load placeholder_tags %}
{% block base_content %}

        {% block breadcrumbs %}
            {% show_breadcrumb 0 "menu/breadcrumbs.html" 0 %}
        {% endblock %}

{% block banner %}

        {% placeholder banner %}

{% endblock %}

{% block leftcol %}

            {% placeholder sub_banner %}

        {% placeholder left_column %}

{% endblock %}

{% block rightcol %}

        {% placeholder right_column %}

{% endblock %}

{% endblock %}
On attempting to publish an existing page that has been updated an error is being thrown that there are multiple placeholder with the same slot name, specifically this only occurs for 'sub_banner'.  Is this a known issue with 2.4.2?  I am using MySQL InnoDB, Python 2.7.3, Django 1.5.1 on CentOS 5.9 (I know, legacy system - I have no choice >.< ).  Any help would be hugely appreciated on this

Closing due to inactivity


[Testing] add test id's for hostDisk and PV initialization tests

What this PR does / why we need it:
Test id's for hostDisk and PV initialization tests
Release note:

None

all ids are in place, pr finished from my perspective

ci test please


CFR Implementation

Been bumbling around Rebel's code. Perhaps it's too late at night and I'm missing something, but shouldn't hand value propagated up for non-traverser node here:
https://github.com/facebookresearch/rebel/blob/452c837ab7e0f59d5e7c969f4595e2f5d4c166ae/csrc/liars_dice/subgame_solving.cc#L570
be multiplied by OP's action strategy in the node exactly as it happens here:
https://github.com/facebookresearch/rebel/blob/452c837ab7e0f59d5e7c969f4595e2f5d4c166ae/csrc/liars_dice/subgame_solving.cc#L556-L557
Even if we pretend we know nothing about OP's strategy(why?), we can not simply sum up all the child values - probably take any or calc a weighted average.

is the opponents strategy already accounted for when passing down the opponent reach probabilities?

You're right, it is just different in my CFR implementation, so I missed it here. Thanks, closing this then.


Vote: a new repository for implementation of a subset of pkcs7/CMS (RFC5652)

I would like to propose the creation of a new repository for implementation of a subset of pkcs7/CMS (Cryptographic Message Syntax) as specified in (RFC5652). This repo will be used by timestamp repo, which is proposed in https://github.com/notaryproject/.github/issues/58.
Here are the details:
Repository name, two options:

Option-1: pkcs7
Option-2: cms

Description:
This repository contains an implementation of a subset of pkcs7/CMS (Cryptographic Message Syntax) as specified in RFC5652.
@notaryproject/notaryproject-governance-maintainers If you agree with above proposal, please comment LGTM or +1 and the repository name (pkcs7 or cms) that you preferred.

Do we really need separate repo for pkcs7? Can this code go in timestamp repo ?

Do we really need separate repo for pkcs7? Can this code go in timestamp repo ?

This repo allows users to use or contribute to pkcs7 separately. Some users may not need timestamp functionality.

The 'timestamp' repository should not include any additional third-party dependencies beyond the 'pkcs7' repository. This setup ensures that users wishing to utilize the 'pkcs7' module need not be overly concerned about taking a dependency on the 'timestamp' repository.
Initially, we can consolidate the pkcs7 related code within the 'timestamp' repository. If necessary, we can subsequently separate the pkcs7-related module and place it in its dedicated repository. This process should be relatively straightforward, primarily involving updates to the 'timestamp' package only.

Thanks @priteshbandi. I will close this vote, and update vote https://github.com/notaryproject/.github/issues/58 to include the pkcs7/cms module.


[New Feature] Add microphone support

Describe the new feature you'd like
It would be lovely to have bidirectional audio.
Describe the reason why you want to add the feature
I want this feature because then I could use my analog wired gaming headset as a wireless one using this app.
Describe how to implement the feature if you can
I'm not sure, but I have a feeling Pipewire can do this.

Your headset plug into the Android phone and you want to let the sound of microphone share to PC?

Yes, at the same time as audio from PC goes to phone. So I can use it for voice chat while gaming. I think that would be a nice feature!

Describe the new feature you'd like It would be lovely to have bidirectional audio.
Describe the reason why you want to add the feature I want this feature because then I could use my analog wired gaming headset as a wireless one using this app.
Describe how to implement the feature if you can I'm not sure, but I have a feeling Pipewire can do this.

Will not be particularly useful for everyone.

This would be a really nice feature, as I could use my phone as a wireless proxy for my Bluetooth headset which I can take away with me inside the house while doing conference calls. My WiFi coverage is much better than what my computer's Bluetooth allows.

I need this feature too )


Audit documentation now calls out that pc and pr are both supported.

Some of the documentation was altered to match the property style from restore/pack and to remove redundant/repetitive wording.
Fixes https://github.com/NuGet/docs.microsoft.com-nuget/issues/3247

@NuGet/nuget-client - Can I please get a review.


chore(deps): bump from

Update zeebe-io/zeebe-operate-helm from 0.0.9 to 0.0.10
Command run was jx step create pr chart --name zeebe-operate --version 0.0.10 --repo https://github.com/zeebe-io/zeebe-full-helm.git

Update zeebe-io/zeebe-cluster-helm from 0.0.21 to 0.0.22
Command run was jx step create pr chart --name zeebe-cluster --version 0.0.22 --repo https://github.com/zeebe-io/zeebe-full-helm.git

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approver: salaboy
If they are not already assigned, you can assign the PR to them by writing /assign @salaboy in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@salaboy: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

serverless-jenkins
8e856594c94cded216f544d6d3beb62cd0d3985d
link
/test this

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@salaboy: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

serverless-jenkins
7207c1a73fe970ba150cd6c744d4863ad3f4f75c
link
/test this

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@salaboy: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

serverless-jenkins
03d043d66a6fb025cf37448c29e93346067047ab
link
/test this

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.


Separate graphs option

Layout graphs in a grid
Turn Y radios into checkboxes
Sync cursors

Looks pretty slow right now, see https://github.com/njoyard/corona/compare/multiple-charts
Maybe wait for chartjs 3 perf improvements ?


Numerical differentiation of cost models

This task refers to writing the c++ class of: https://github.com/loco-3d/crocoddyl/blob/devel/unittest/python/crocoddyl/cost.py#L70.
And it also includes the Python bindings.

Solved in #661


ARK-Retouch#75: ARK Filepicker enhancements

ARK-Builders/ARK-Retouch#75

Automatic scanning is more difficult than it was anticipated.
See #21 for newer definition of the task.
https://github.com/ARK-Builders/ARK-Retouch/issues/75 should be done without automatic scanning.


Charm cannot be built using charm-tools 3.x

This bug is to tracked all charms which cloud not build with charm-tools 3.x.
Right now we can fixed this with using build-snaps: [charm/2.x/stable],
but this will need to be fixed in the future.
Potential fixes are:

update wheelhouse.txt to work on multiple python versions
use multiple series with build-on

list of known bugs:

https://github.com/canonical/charmcraft/issues/888
https://github.com/juju/charm-tools/issues/646
https://github.com/juju-solutions/layer-basic/issues/209

Imported from Launchpad using lp2gh.

date created: 2022-10-26T13:42:52Z

owner: rgildein

assignee: rgildein

the launchpad url

(by hloeung)
We've had success (so far only tried with the autocert and ubuntu-repository-cache charm) with switching to Launchpad for building charms and the wheelhouse.txt to support multiple python versions. There is a PR open to get the wheelhouse.txt change into layer-basic[1].
As for getting Launchpad to build charms, see the charmcraft.yaml and the charm receipe in Launchpad.
[1]https://github.com/juju-solutions/layer-basic/pull/211


fix: ability to disable download of metrics agent

Currently one can't skip the download of the metrics agent.

Closing since we discovered this is not the buildpack that was intended to be fixed. See: https://github.com/heroku/buildpacks-jvm/pull/444


Update maintenance to 2023

Proposed Changes

(Describe the changes and rationale behind them)

Related Issues

(Github link to related issues or pull requests)

Thanks a lot!


Pre-permission not working with .Bluetooth

I'm having an issue using the pre-permission with the .Bluetooth Permission type. Does this have something to do with this line in Permission.swift case .Bluetooth:         requestBluetooth(self.callback)?
Still a bit new to Swift so not 100% sure what is wrong here.

What issue do you have?

The pre-permission seems to always fire, even if the permission has already been authorized previously, is this correct behaviour? Perhaps I'm just a bit confused about the expected behaviour.

It definitely shouldn't fire indeed.
I'm gonna look into it

That would be awesome, thanks so much for looking into it. If you have any issue re-creating the error I can try to send you some sample code of exactly how I am implementing the framework, but my implementation was pretty much just based on the sample documentation you gave but using the .Bluetooth permission.

@delba: Im seeing this too.
I'm also getting a system dialog permission pop-up when I access Permission.bluetooth.status

@AndrewSB I believe I found a fix to this if you check out #70. 😄

@AndrewSB did you had a change to try #70 ? I'm going to test it as well on my side :)

I'll test #70 later today!
On Thu, Oct 20, 2016 at 8:18 AM Damien<EMAIL_ADDRESS>wrote:

@AndrewSB https://github.com/AndrewSB did you had a change to try #70
https://github.com/delba/Permission/pull/70 ? I'm going to test it as
well on my side :)
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/delba/Permission/issues/36#issuecomment-255136942,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ADo1dMvUB5BJSyVFakok2JKDHFlrSIVaks5q14YxgaJpZM4JDkMH
.

This is now replaced with #74 for isolation from #69 @delba @AndrewSB

#74 has now been replaced with #76 😛 @AndrewSB

Fixed in https://github.com/delba/Permission/commit/f6b36cebcc72f2f99148b05cc813774d9a87972b


Ensure AuthClient is cached

Closes https://github.com/google-github-actions/upload-cloud-storage/issues/364
/cc @GregoireW @danielbankhead could you please test this?
@verbanicm hold on merge until further testing.

@sethvargo The action is not built here.

@sethvargo The action is not built here.

Fixed

Now I got 2 api when I launch my test with 200 files so this is good.
I notice a real application with ~75 api call for 3500 files, not sure why, but let say it is not related.  it is already a huge improvement.
Thank you!

@verbanicm ready for review
@danielbankhead - I'd still like your feedback on https://github.com/google-github-actions/upload-cloud-storage/pull/373#discussion_r1720790152.


appc->oci: get rid of docker2aci

As part of OCI, we will need to get rid of docker2aci conversion when handling OCI, importing them directly.
Current plan is to adopt the c/image library for fetching and storing OCI blobs in native format.

@lucab Is it still valuable? I'm wondering if I could work on it.

@lucasallan I believe this continues to be valuable if you're still up for it.

@iaguis I would like to work on this issue. could you guide me that how can I start?

@sch00lb0y At a very high level, the first thing would be to get https://github.com/containers/image into rkt/vendor.  Then look at the places where docker2aci is used and consider how to convert those to use the the c/image library.


Biopsy of muscle tissue and biopsy of muscle are redundant

Probably remove Biopsy of muscle tissue  and keep biopsy of muscle.
If we do decide the keep biopsy of muscle tissue, then the definition needs work:
Removal of tissue from the muscle tissue.

obsoleted biopsy of muscle and replaced with biopsy of muscle tissue. df:about="http://purl.obolibrary.org/obo/MAXO_0000386">
<obo:IAO_0100001 rdf:resource="http://purl.obolibrary.org/obo/MAXO_0000387"/>
rdfs:labelobsolete biopsy of muscle</rdfs:label>


Compatibility  awesome_notification and workmanager

I have some issue when i try to use awesome_notification with workmanager...
"Tried to send a platform message to Flutter, but FlutterJNI was detached from native C++. Could not send. Channel: awesome_notifications. Response ID: 0"
Is it possible to fix?
Code where i get this issue:
void callbackDispatcher() {
  Workmanager().executeTask((task, inputData) async {
    switch (task) {
      case channelDelayedTask:
        await awesomeNotifications.createNotification(
            content: NotificationContent(
                id: idAwa,
                channelKey: channelAwareness,
                title: 'title',
                body: 'body',
                payload: {'uuid': 'user-profile-uuid1'}),);

        Workmanager().registerOneOffTask(
          tagAwaTask,
          channelDelayedTask,
          initialDelay: Duration(seconds: intervalDelay),
          existingWorkPolicy: ExistingWorkPolicy.append,
        );

        break;
      case Workmanager.iOSBackgroundTask:
        print("The iOS background fetch was triggered");

        break;
    }

I dont know how workmanager plugin works. I believe you gonna need to initialize every alternative plugin by your own. Check it with the workmanager Git community of how to do it.

Solved it to use background_fetch with awesome_notifications...now i don't have this issue.
Rafael, Thanks for the awesome package! Would be great if you will create in future method or something for replace notifications with different id..something like tag. it's reason why now i try to use awesome_notifications with background_fetch to solve this task.

Having the same problem -
Works in iOS but not on android -
Error -
W/FlutterJNI(17550): Tried to send a platform message to Flutter, but FlutterJNI was detached from native C++. Could not send. Channel: awesome_notifications. Response ID: 0
Package Versions -
awesome_notifications: ^0.0.6+9
workmanager: ^0.4.1
@rafaelsetragni


Add Redoc API reference information

This is a Feature Request

What would you like to be added
Initially as an experiment, add API reference information using Docsy's support for redoc.
Why is this needed
There are different ways of thinking about the Kubernetes API. Some readers are mainly interested in writing manifests; others want to interact with the control plane via HTTP.
This experiment could help us offer another way to access the API information. We have https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.25/ and friends already; the trouble with that page is that it doesn't integrate with the rest of the site navigation.
Comments
/area web-development
/wg api-expression
/kind feature
See [https://github.com/kubernetes/website/issues/37971#issuecomment-1434815502] for some very relevant commentary.
If the experiment is a success, we could change the generator for https://kubernetes.io/docs/reference/kubernetes-api/ to link to the Redoc version, and change the Redoc version to link to pages within https://kubernetes.io/docs/reference/kubernetes-api/

To work on this, you will need a copy of the OpenAPI document. I think api-ref-assets/api/swagger.json should work.

BTW @tengqm what do you think of this idea?

Sorry I didn't notice this issue before.
When revisit the API reference generation topic, we have to consider several things:

The k8s API is HUGE. When compiling/rendering the API specification into a PDF file, you get a dictionary rather than a booklet. We have to consider how to divide the API into several sections. There is no ideal grouping given the nature of the domains the API covers. By the way, some API types are migrating from one group to another, now and then.
The k8s API is more about definitions (or concepts, or nouns) rather than operations (or verbs), thanks to its declarative API design philosophy. The implication is that most of the existing swagger viewers/editors may appear useless -- they are more focused on paths and verbs rather than the payload (data model).
Pure markdown output is more likely to mimic the look and feel of the current website, but I'm a big fan of tables when trying to figure out the definition of a Resource. Indentations may work in other places, but not for Kubernetes. Consider this: we have Deployment->ReplicaSet->Pod Template->Pod->Container(s)->... This hierarchy has to be flattened. This doesn't look like what Redoc is good at.

 I suspended that work to give way to the GSOC initiative. You can still see the code here. When I can get some cycles, I'd like to resume that work and share the output. I had a similar effort converting the kubectl reference into markdown, by the way.

/remove-lifecycle stale
I'm OK if this now rots out. We have many competing priorities.


Deserializing 'A' to 'IBonded'?

I have been looking at the code and samples to try to figure out how this is done but to no avail. I want to deserialize from a stream WITHOUT a container object to an IBonded. IE:
struct A
{
  0: required string Type;
}

struct B : A
{
  0: string BStuff;
}

struct C : A
{
  0: string CStuff;
}

var rdr = new SimpleJsonReader(stream);
var a = Deserialize<IBonded<A>>.From(rdr);
if (a.Deserialize().Type == "BType")
{
  var b = a.Deserialize<B>();
}

etc...
But I don't want to have to make another object such as:
struct Wrapper
{
  0: IBonded<A> PolymorphicData;
}

I have also tried telling the base type directly to be (typeof(Bonded) and typeof(A). It seems like no matter what the "Cache" fails to know how to realize the type. I have even gone so far as to write a CustomBonded<T> much like the tests that seek/reset the underlying stream so I can effectively deserialize it again without a mem copy but this seems crazy.
Any guidance / updates to the Polymorphic examples would be awesome! Thanks.

What you want to do with bonded types won't work with the current SimpleJsonReader implementation in C#, as it doesn't support lazy deserialization. There's an existing issue, #96 JSON doesn't support lazy deserialization open for this.
If you use an encoding protocol that does support lazy deserialization, like Compact Binary, this would work, with code that looks like the following. Notice that we're not deserializing to a IBonded<A>; we're just creating an IBonded<A> backed by a reader.
static void DeserializeAndPrint(ArraySegment<byte> data)
{
    var reader = new CompactBinaryReader<InputBuffer>(new InputBuffer(data));
    IBonded<A> bondedA = new Bonded<A, CompactBinaryReader<InputBuffer>>(reader);
    var a = bondedA.Deserialize<A>();

    switch (a.Type)
    {
        case "BType":
            {
                var b = bondedA.Deserialize<B>();
                Console.WriteLine($"Got a B: {b.BStuff}");
                break;
            }

        case "CType":
            {
                var c = bondedA.Deserialize<C>();
                Console.WriteLine($"Got a C: {c.CStuff}");
                break;
            }

        default:
            Console.WriteLine($"Unknown derived type {a.Type}");
            break;
    }
}

@chwarr - Thank you for the link to the other issue! That now makes total sense why this wasn't working. I can likely just switch to the CompactBinary protocol in my case.


Request to support another thermostat

Hello, Thanks again for supporting these devices, I came with new Thermostat.
While trying to add the thermostat it shows as switch only.
The thermostat is from a company called saswell here is a link of the product
and another link for the manual
The below is what I can read from the device
{
  "result": {
    "active_time":<PHONE_NUMBER>,
    "biz_type": 18,
    "category": "wk",
    "create_time":<PHONE_NUMBER>,
    "icon": "smart/icon/ay1537509218624daaHb/1568701541ef9f14aff8e.jpg",
    "id": "quoted for security",
    "ip": "quoted for security",
    "lat": "quoted for security",
    "local_key": "quoted for security",
    "lon": "quoted for security",
    "model": "T29UTW-7-WIFI(TY)",
    "name": "Room Thermostat",
    "online": true,
    "owner_id": "quoted for security",
    "product_id": "q2cf9qt8zl2qyqhz",
    "product_name": "T29UTW",
    "status": [
      {
        "code": "switch",
        "value": true
      },
      {
        "code": "mode",
        "value": "cold"
      },
      {
        "code": "c_f",
        "value": "C"
      },
      {
        "code": "temp_set",
        "value": 23
      },
      {
        "code": "temp_current",
        "value": 23
      },
      {
        "code": "temp_set_f",
        "value": 74
      },
      {
        "code": "temp_current_f",
        "value": 81
      }
    ],
    "sub": false,
    "time_zone": "+00:00",
    "uid": "quoted for security",
    "update_time": quoted for security,
    "uuid": "quoted for security"
  },
  "success": true,
  "t": .....
}

Edit:
I added the DPS from HA while detecting it as simple switch and what I think it will be
Device matches simple_switch with quality of 7%. DPS: {
'1': True, #True the thermostat is on position False is off position
'2': 240,  #set tempreture 24.0 (exact reading on the panel)
'3': 241,  #currunt tempreture 24.1 (exact reading on the panel)
'4': 'cold',  #mode cold / off (it can be heat as well) it changes from cold to off when the thermostat in off position
'5': 'auto',  #fan auto or on
'19': 'c',  # Celsius or Fahrenheit
'101': False,
'102': False,
'103': 'cold',  #mode it doesn't change when it is in off position
'112': '1',
'113': 0,
'114': 24, #set temp in C
'115': 24,  #current temp in C
'116': 75,  #set temp in F
'117': 81,  # current temp in F
'updated_at':<PHONE_NUMBER>.2673612
}

I can find out the others if I played with the configuration of the device if needed
Thanks again :)

Device matches simple_switch with quality of 7%. DPS: {'1': True, '2': 240, '3': 241, '4': 'cold', '5': 'auto', '19': 'c', '101': False, '102': False, '103': 'cold', '112': '1', '113': 0, '114': 24, '115': 24, '116': 75, '117': 81, 'updated_at':<PHONE_NUMBER>.2673612}
DPS in Home Assistant Sorry forgot about it

From the manual, one of 101 or 102 should be the child lock, the other may be an aux_heat setting.
112 may be related to the program settings, or the configuration of the thermostat, and 113 an error code (covering the other indicators on the panel, such as UV lamp replacement indicator).

I have checked for the remaining dps and found the below,
Also I want to note that once I have added the new thermostat the old one went missing from HA I don't know why I will try restarting HA and reconnecting it.
DPS: {
'1': False, #true is on false is off
'2': 240, # set temp
'3': 275, # current temp
'4': 'off', # mode off or cold
'5': 'auto', # fan auto or on
'19': 'c',  #c or F
'101': False, #True = away mode (it sets the temp to 28 C)
'102': False, #True = activate 7 day program / False if you don't want to use it
'103': 'cold', # mode cold (related to the 7 days program)
'112': '1',
'113': 0,
'114': 24, # set temp "c"
'115': 27, # current temp "c"
'116': 75, # set temp "f"
'117': 81, # current temp "f"
'updated_at':<PHONE_NUMBER>.2566292}

You can try the change I just pushed on 'main' (not released yet).  I haven't yet made the changes from your last comment, but it looks like they can be accommodated as presets.

Release 0.11.0 has preliminary support (with the away/program settings still reported as unknown)

Hello,
I got it reporting the correct temps, but I cant control anything with HA

I found out the below, Mode can be cold hot or off
to enable the thermostat switch on it should (turn the switch to on "true" and change mode to cold at the same time)
Mode:
type: Enum
{
  "range": [
    "cold",
    "hot"
  ]
}

as for setting the temp, it can only read the temp_set_f, I have tired setting the temp with temp_set (which is the c unit) it will not accept it for some reason.

Only one method of setting the temperature can be provided.  Previously dps 2 was used (in 0.11.0 that is the case), but in main, I have changed it to dps 114/116 depending on the setting of dps 19 (c = 114, f = 116).
But it may be that there is still some problem with the scaling, or with the C/F conditions in the 0.11.0 version, so if it is still not working in main, I could try simplifying the temperature set conditions.  Like the Beka thermostat, we may end up needing to use different configs for the C and F settings so the conditions can be removed.

I have tried the main as well, I can't control the thermostat, If you need me to do anything else I'm ready.
I just want to share the info I have in Tuya developer page if that can help
Standard Instruction Set tap

Standard Status Set tap

Still I can't control the thermostat, when trying to control it via HA, it shows idle.

For DPS 1, is it turning off the full system, or just the display?  I notice that quite a few thermostats use DPS 1 for the display on/off, and don't actually have a way to turn them off remotely.  If it is full system, then it needs to be linked to hvac_mode.

0.11.3 should have the changes raised in the last comment.  If you have any suggestions for further improvement, please open a new issue.


Page titles

If we have a page title, add this to the HTML <title> element, so that it is used for the browser tab and bookmarks.
Before:

After:

I think you have commits from #310 at the same time

yeah, sorry - I was too fast with opening this PR..
Also just added in the description meta tag..


Redis 4.x.x Support

Just saw Redis 4.0.0 was released, and seems to have some major changes.
Just curious as to the timetable to support this, if at all.

I'm planning on adding Redis 4 support, probably within the next week or 2 for at least the basic support of the config file running and the version being 4.0.0
Extra features feel free to request and I'll merge PRs 👍

I'd love to see some Redis 4.0 for EL.   Hope you can find some time to work on this again :)

I should be able to have a go at this, came back from a long holiday and ready to pick up some open source stuff 😄

be really helpful if they got the 4.0.x RPMs into EPEL.  the latest thats available is 3.2.10.

Yeah, I wouldn't get your hopes up on that front. It took them 3 years to go from 2.4 to 3.2... 😞 (https://bugzilla.redhat.com/show_bug.cgi?id=923970)

Yeah, I didn't have high hopes for that.  Where are you planning to get the RPMs for 4.x.x from?

Most people use Remi repo: https://rpms.remirepo.net/
I think I'll just add an example of using the remi repo for Redis install, I don't want to add too many dependancies to the module.

I had come across this repo before, which seems to stay up to date pretty well.  I'll keep it in mind, thank you.

have you had any chance to work on the 4.0 stuff?

Alrighty, so, now that #216 is fixed, I can start working on this again and get it released 😄

Any update on 4.x support? I tested the add_redis_4_support branch but still got some issues of the configuration file not being idempotent on the second puppet run. Here is some debug info, running on Ubuntu Bionic with Puppet 5.
Manifest: class { '::redis': }
First run:
root@ubuntu-bionic:~# /opt/puppetlabs/bin/puppet apply --modulepath=./modules test.pp
Warning: Scope(Class[Redis::Params]): Ubuntu release 18.04 isn't 'officially' supported by module, but will git it a shot
Notice: Compiled catalog for ubuntu-bionic.ognet.se in environment production in 0.15 seconds
Notice: /Stage[main]/Redis::Install/Package[redis-server]/ensure: created
Notice: /Stage[main]/Redis::Config/File[/etc/redis]/owner: owner changed 'root' to 'redis'
Notice: /Stage[main]/Redis::Config/File[/etc/redis]/group: group changed 'root' to 'redis'
Notice: /Stage[main]/Redis::Config/File[/var/log/redis]/mode: mode changed '0750' to '0755'
Notice: /Stage[main]/Redis::Ulimit/File[/etc/systemd/system/redis-server.service.d/]/ensure: created
Notice: /Stage[main]/Redis::Ulimit/File[/etc/systemd/system/redis-server.service.d/limit.conf]/ensure: created
Notice: /Stage[main]/Redis::Config/File[/etc/default/redis-server]/owner: owner changed 'root' to 'redis'
Notice: /Stage[main]/Redis::Config/File[/etc/default/redis-server]/group: group changed 'root' to 'redis'
Notice: /Stage[main]/Redis::Config/Redis::Instance[default]/File[/etc/redis/redis.conf.puppet]/ensure: defined content as '{md5}4d8d63b059980726b994e0879b77edf1'
Notice: /Stage[main]/Redis::Config/Redis::Instance[default]/Exec[cp -p /etc/redis/redis.conf.puppet /etc/redis/redis.conf]: Triggered 'refresh' from 1 event
Error: Could not enable redis-server:
Error: /Stage[main]/Redis::Service/Service[redis-server]/enable: change from 'false' to 'true' failed: Could not enable redis-server:
Notice: /Stage[main]/Redis::Service/Service[redis-server]: Triggered 'refresh' from 1 event
Notice: Applied catalog in 5.40 seconds

Redis version being installed:
root@ubuntu-bionic:~# apt-cache policy redis-server
redis-server:
  Installed: 5:4.0.9-1
  Candidate: 5:4.0.9-1
  Version table:
 *** 5:4.0.9-1 500
        500 http://archive.ubuntu.com/ubuntu bionic/universe amd64 Packages
        100 /var/lib/dpkg/status

root@ubuntu-bionic:~# ls -l /etc/redis/
total 64
-rw-r--r-- 1 redis redis 31260 Jul 17 15:21 redis.conf
-rw-r--r-- 1 redis redis 31260 Jul 17 15:21 redis.conf.puppet

The redis-server systemd unit cannot be enabled:
root@ubuntu-bionic:~# systemctl enable redis-server
Synchronizing state of redis-server.service with SysV service script with /lib/systemd/systemd-sysv-install.
Executing: /lib/systemd/systemd-sysv-install enable redis-server
Failed to enable unit: Unit file /lib/systemd/system/redis-server.service is masked.

If  you uninstall it manually apt-get --purge remove redis-server -y && apt-get autoremove -y && rm -rf /etc/redis and then install it apt install redis-server -y you still cannot enable the systemd unit file. But if you recreate your vagrant machine and install manually and then enable you can.
Second run:
root@ubuntu-bionic:~# /opt/puppetlabs/bin/puppet apply --modulepath=./modules test.pp
Warning: Scope(Class[Redis::Params]): Ubuntu release 18.04 isn't 'officially' supported by module, but will git it a shot
Notice: Compiled catalog for ubuntu-bionic.ognet.se in environment production in 0.16 seconds
Notice: /Stage[main]/Redis::Config/Redis::Instance[default]/File[/etc/redis/redis.conf.puppet]/content: content changed '{md5}4d8d63b059980726b994e0879b77edf1' to '{md5}0c28a2f8ced87153f4825ba268272e79'
Notice: /Stage[main]/Redis::Config/Redis::Instance[default]/Exec[cp -p /etc/redis/redis.conf.puppet /etc/redis/redis.conf]: Triggered 'refresh' from 1 event
Error: Could not enable redis-server:
Error: /Stage[main]/Redis::Service/Service[redis-server]/enable: change from 'false' to 'true' failed: Could not enable redis-server:
Error: /Stage[main]/Redis::Service/Service[redis-server]: Failed to call refresh: Systemd restart for redis-server failed!
journalctl log for redis-server:
-- Logs begin at Tue 2018-07-17 15:14:04 UTC, end at Tue 2018-07-17 15:28:44 UTC. --
Jul 17 15:24:56 ubuntu-bionic systemd[1]: Stopping Advanced key-value store...
Jul 17 15:24:56 ubuntu-bionic systemd[1]: Stopped Advanced key-value store.
Jul 17 15:25:46 ubuntu-bionic systemd[1]: Starting Advanced key-value store...
Jul 17 15:25:46 ubuntu-bionic systemd[1]: redis-server.service: Can't open PID file /var/run/redis/redis-server.pid (yet?) after start: No such file or directory
Jul 17 15:25:47 ubuntu-bionic systemd[1]: Started Advanced key-value store.
Jul 17 15:26:38 ubuntu-bionic systemd[1]: Stopping Advanced key-value store...
Jul 17 15:26:38 ubuntu-bionic systemd[1]: Stopped Advanced key-value store.
Jul 17 15:26:38 ubuntu-bionic systemd[1]: Starting Advanced key-value store...
Jul 17 15:26:53 ubuntu-bionic systemd[1]: Stopped Advanced key-value store.
Jul 17 15:27:06 ubuntu-bionic systemd[1]: Starting Advanced key-value store...
Jul 17 15:27:06 ubuntu-bionic systemd[1]: redis-server.service: Can't open PID file /var/run/redis/redis-server.pid (yet?) after start: No such file or directory
Jul 17 15:27:06 ubuntu-bionic systemd[1]: Started Advanced key-value store.
Jul 17 15:27:08 ubuntu-bionic systemd[1]: Stopping Advanced key-value store...
Jul 17 15:27:08 ubuntu-bionic systemd[1]: Stopped Advanced key-value store.
Jul 17 15:27:08 ubuntu-bionic systemd[1]: Starting Advanced key-value store...
Jul 17 15:27:08 ubuntu-bionic systemd[1]: redis-server.service: Can't open PID file /var/run/redis/redis-server.pid (yet?) after start: No such file or directory
Jul 17 15:27:08 ubuntu-bionic systemd[1]: Started Advanced key-value store.
Jul 17 15:27:13 ubuntu-bionic systemd[1]: Stopping Advanced key-value store...
Jul 17 15:27:13 ubuntu-bionic systemd[1]: Stopped Advanced key-value store.
Jul 17 15:27:13 ubuntu-bionic systemd[1]: Starting Advanced key-value store...
Jul 17 15:28:44 ubuntu-bionic systemd[1]: redis-server.service: Start operation timed out. Terminating.
Jul 17 15:28:44 ubuntu-bionic systemd[1]: redis-server.service: Failed with result 'timeout'.
Jul 17 15:28:44 ubuntu-bionic systemd[1]: Failed to start Advanced key-value store.

Error: /Stage[main]/Redis::Service/Service[redis-server]: Systemd restart for redis-server failed!
journalctl log for redis-server:
-- Logs begin at Tue 2018-07-17 15:14:04 UTC, end at Tue 2018-07-17 15:28:44 UTC. --
Jul 17 15:24:56 ubuntu-bionic systemd[1]: Stopping Advanced key-value store...
Jul 17 15:24:56 ubuntu-bionic systemd[1]: Stopped Advanced key-value store.
Jul 17 15:25:46 ubuntu-bionic systemd[1]: Starting Advanced key-value store...
Jul 17 15:25:46 ubuntu-bionic systemd[1]: redis-server.service: Can't open PID file /var/run/redis/redis-server.pid (yet?) after start: No such file or directory
Jul 17 15:25:47 ubuntu-bionic systemd[1]: Started Advanced key-value store.
Jul 17 15:26:38 ubuntu-bionic systemd[1]: Stopping Advanced key-value store...
Jul 17 15:26:38 ubuntu-bionic systemd[1]: Stopped Advanced key-value store.
Jul 17 15:26:38 ubuntu-bionic systemd[1]: Starting Advanced key-value store...
Jul 17 15:26:53 ubuntu-bionic systemd[1]: Stopped Advanced key-value store.
Jul 17 15:27:06 ubuntu-bionic systemd[1]: Starting Advanced key-value store...
Jul 17 15:27:06 ubuntu-bionic systemd[1]: redis-server.service: Can't open PID file /var/run/redis/redis-server.pid (yet?) after start: No such file or directory
Jul 17 15:27:06 ubuntu-bionic systemd[1]: Started Advanced key-value store.
Jul 17 15:27:08 ubuntu-bionic systemd[1]: Stopping Advanced key-value store...
Jul 17 15:27:08 ubuntu-bionic systemd[1]: Stopped Advanced key-value store.
Jul 17 15:27:08 ubuntu-bionic systemd[1]: Starting Advanced key-value store...
Jul 17 15:27:08 ubuntu-bionic systemd[1]: redis-server.service: Can't open PID file /var/run/redis/redis-server.pid (yet?) after start: No such file or directory
Jul 17 15:27:08 ubuntu-bionic systemd[1]: Started Advanced key-value store.
Jul 17 15:27:13 ubuntu-bionic systemd[1]: Stopping Advanced key-value store...
Jul 17 15:27:13 ubuntu-bionic systemd[1]: Stopped Advanced key-value store.
Jul 17 15:27:13 ubuntu-bionic systemd[1]: Starting Advanced key-value store...
Jul 17 15:28:44 ubuntu-bionic systemd[1]: redis-server.service: Start operation timed out. Terminating.
Jul 17 15:28:44 ubuntu-bionic systemd[1]: redis-server.service: Failed with result 'timeout'.
Jul 17 15:28:44 ubuntu-bionic systemd[1]: Failed to start Advanced key-value store.

Notice: Applied catalog in 90.97 seconds

If you uninstall again and then change your manifest to:
class { '::redis':
  service_provider => 'systemd',
  service_enable    => false,
}

You're still gonna have issues with idempotent configuration file (on the second run) and the service failing to start, so something is going wrong with the template, if you diff the attached files you can see some sections are missing. Here is the output of the two puppet runs with the above manifest:
root@ubuntu-bionic:~# /opt/puppetlabs/bin/puppet apply --modulepath=./modules test.pp
Warning: Scope(Class[Redis::Params]): Ubuntu release 18.04 isn't 'officially' supported by module, but will git it a shot
Notice: Compiled catalog for ubuntu-bionic.ognet.se in environment production in 0.17 seconds
Notice: /Stage[main]/Redis::Install/Package[redis-server]/ensure: created
Notice: /Stage[main]/Redis::Config/File[/etc/redis]/owner: owner changed 'root' to 'redis'
Notice: /Stage[main]/Redis::Config/File[/etc/redis]/group: group changed 'root' to 'redis'
Notice: /Stage[main]/Redis::Config/File[/var/log/redis]/mode: mode changed '0750' to '0755'
Notice: /Stage[main]/Redis::Config/File[/etc/default/redis-server]/owner: owner changed 'root' to 'redis'
Notice: /Stage[main]/Redis::Config/File[/etc/default/redis-server]/group: group changed 'root' to 'redis'
Notice: /Stage[main]/Redis::Config/Redis::Instance[default]/File[/etc/redis/redis.conf.puppet]/ensure: defined content as '{md5}4d8d63b059980726b994e0879b77edf1'
Notice: /Stage[main]/Redis::Config/Redis::Instance[default]/Exec[cp -p /etc/redis/redis.conf.puppet /etc/redis/redis.conf]: Triggered 'refresh' from 1 event
Notice: /Stage[main]/Redis::Service/Service[redis-server]: Triggered 'refresh' from 1 event
Notice: Applied catalog in 3.96 seconds

root@ubuntu-bionic:~# /opt/puppetlabs/bin/puppet apply --modulepath=./modules test.pp
Warning: Scope(Class[Redis::Params]): Ubuntu release 18.04 isn't 'officially' supported by module, but will git it a shot
Notice: Compiled catalog for ubuntu-bionic.ognet.se in environment production in 0.13 seconds
Notice: /Stage[main]/Redis::Config/Redis::Instance[default]/File[/etc/redis/redis.conf.puppet]/content: content changed '{md5}4d8d63b059980726b994e0879b77edf1' to '{md5}0c28a2f8ced87153f4825ba268272e79'
Notice: /Stage[main]/Redis::Config/Redis::Instance[default]/Exec[cp -p /etc/redis/redis.conf.puppet /etc/redis/redis.conf]: Triggered 'refresh' from 1 event
Error: /Stage[main]/Redis::Service/Service[redis-server]: Failed to call refresh: Systemd restart for redis-server failed!
journalctl log for redis-server:
-- Logs begin at Tue 2018-07-17 15:14:04 UTC, end at Tue 2018-07-17 15:33:59 UTC. --
Jul 17 15:29:41 ubuntu-bionic systemd[1]: Stopped Advanced key-value store.
Jul 17 15:30:03 ubuntu-bionic systemd[1]: Starting Advanced key-value store...
Jul 17 15:30:03 ubuntu-bionic systemd[1]: redis-server.service: Can't open PID file /var/run/redis/redis-server.pid (yet?) after start: No such file or directory
Jul 17 15:30:03 ubuntu-bionic systemd[1]: Started Advanced key-value store.
Jul 17 15:30:05 ubuntu-bionic systemd[1]: Stopping Advanced key-value store...
Jul 17 15:30:05 ubuntu-bionic systemd[1]: Stopped Advanced key-value store.
Jul 17 15:30:05 ubuntu-bionic systemd[1]: Starting Advanced key-value store...
Jul 17 15:30:05 ubuntu-bionic systemd[1]: redis-server.service: Can't open PID file /var/run/redis/redis-server.pid (yet?) after start: No such file or directory
Jul 17 15:30:05 ubuntu-bionic systemd[1]: Started Advanced key-value store.
Jul 17 15:30:11 ubuntu-bionic systemd[1]: Stopping Advanced key-value store...
Jul 17 15:30:11 ubuntu-bionic systemd[1]: Stopped Advanced key-value store.
Jul 17 15:30:11 ubuntu-bionic systemd[1]: Starting Advanced key-value store...
Jul 17 15:31:42 ubuntu-bionic systemd[1]: redis-server.service: Start operation timed out. Terminating.
Jul 17 15:31:42 ubuntu-bionic systemd[1]: redis-server.service: Failed with result 'timeout'.
Jul 17 15:31:42 ubuntu-bionic systemd[1]: Failed to start Advanced key-value store.
Jul 17 15:31:42 ubuntu-bionic systemd[1]: redis-server.service: Service hold-off time over, scheduling restart.
Jul 17 15:31:42 ubuntu-bionic systemd[1]: redis-server.service: Scheduled restart job, restart counter is at 1.
Jul 17 15:31:42 ubuntu-bionic systemd[1]: Stopped Advanced key-value store.
Jul 17 15:31:42 ubuntu-bionic systemd[1]: Starting Advanced key-value store...
Jul 17 15:31:46 ubuntu-bionic systemd[1]: Stopped Advanced key-value store.
Jul 17 15:32:22 ubuntu-bionic systemd[1]: Starting Advanced key-value store...
Jul 17 15:32:22 ubuntu-bionic systemd[1]: redis-server.service: Can't open PID file /var/run/redis/redis-server.pid (yet?) after start: No such file or directory
Jul 17 15:32:22 ubuntu-bionic systemd[1]: Started Advanced key-value store.
Jul 17 15:32:24 ubuntu-bionic systemd[1]: Stopping Advanced key-value store...
Jul 17 15:32:24 ubuntu-bionic systemd[1]: Stopped Advanced key-value store.
Jul 17 15:32:24 ubuntu-bionic systemd[1]: Starting Advanced key-value store...
Jul 17 15:32:24 ubuntu-bionic systemd[1]: redis-server.service: Can't open PID file /var/run/redis/redis-server.pid (yet?) after start: No such file or directory
Jul 17 15:32:24 ubuntu-bionic systemd[1]: Started Advanced key-value store.
Jul 17 15:32:29 ubuntu-bionic systemd[1]: Stopping Advanced key-value store...
Jul 17 15:32:29 ubuntu-bionic systemd[1]: Stopped Advanced key-value store.
Jul 17 15:32:29 ubuntu-bionic systemd[1]: Starting Advanced key-value store...
Jul 17 15:33:59 ubuntu-bionic systemd[1]: redis-server.service: Start operation timed out. Terminating.
Jul 17 15:33:59 ubuntu-bionic systemd[1]: redis-server.service: Failed with result 'timeout'.
Jul 17 15:33:59 ubuntu-bionic systemd[1]: Failed to start Advanced key-value store.

Error: /Stage[main]/Redis::Service/Service[redis-server]: Systemd restart for redis-server failed!
journalctl log for redis-server:
-- Logs begin at Tue 2018-07-17 15:14:04 UTC, end at Tue 2018-07-17 15:33:59 UTC. --
Jul 17 15:29:41 ubuntu-bionic systemd[1]: Stopped Advanced key-value store.
Jul 17 15:30:03 ubuntu-bionic systemd[1]: Starting Advanced key-value store...
Jul 17 15:30:03 ubuntu-bionic systemd[1]: redis-server.service: Can't open PID file /var/run/redis/redis-server.pid (yet?) after start: No such file or directory
Jul 17 15:30:03 ubuntu-bionic systemd[1]: Started Advanced key-value store.
Jul 17 15:30:05 ubuntu-bionic systemd[1]: Stopping Advanced key-value store...
Jul 17 15:30:05 ubuntu-bionic systemd[1]: Stopped Advanced key-value store.
Jul 17 15:30:05 ubuntu-bionic systemd[1]: Starting Advanced key-value store...
Jul 17 15:30:05 ubuntu-bionic systemd[1]: redis-server.service: Can't open PID file /var/run/redis/redis-server.pid (yet?) after start: No such file or directory
Jul 17 15:30:05 ubuntu-bionic systemd[1]: Started Advanced key-value store.
Jul 17 15:30:11 ubuntu-bionic systemd[1]: Stopping Advanced key-value store...
Jul 17 15:30:11 ubuntu-bionic systemd[1]: Stopped Advanced key-value store.
Jul 17 15:30:11 ubuntu-bionic systemd[1]: Starting Advanced key-value store...
Jul 17 15:31:42 ubuntu-bionic systemd[1]: redis-server.service: Start operation timed out. Terminating.
Jul 17 15:31:42 ubuntu-bionic systemd[1]: redis-server.service: Failed with result 'timeout'.
Jul 17 15:31:42 ubuntu-bionic systemd[1]: Failed to start Advanced key-value store.
Jul 17 15:31:42 ubuntu-bionic systemd[1]: redis-server.service: Service hold-off time over, scheduling restart.
Jul 17 15:31:42 ubuntu-bionic systemd[1]: redis-server.service: Scheduled restart job, restart counter is at 1.
Jul 17 15:31:42 ubuntu-bionic systemd[1]: Stopped Advanced key-value store.
Jul 17 15:31:42 ubuntu-bionic systemd[1]: Starting Advanced key-value store...
Jul 17 15:31:46 ubuntu-bionic systemd[1]: Stopped Advanced key-value store.
Jul 17 15:32:22 ubuntu-bionic systemd[1]: Starting Advanced key-value store...
Jul 17 15:32:22 ubuntu-bionic systemd[1]: redis-server.service: Can't open PID file /var/run/redis/redis-server.pid (yet?) after start: No such file or directory
Jul 17 15:32:22 ubuntu-bionic systemd[1]: Started Advanced key-value store.
Jul 17 15:32:24 ubuntu-bionic systemd[1]: Stopping Advanced key-value store...
Jul 17 15:32:24 ubuntu-bionic systemd[1]: Stopped Advanced key-value store.
Jul 17 15:32:24 ubuntu-bionic systemd[1]: Starting Advanced key-value store...
Jul 17 15:32:24 ubuntu-bionic systemd[1]: redis-server.service: Can't open PID file /var/run/redis/redis-server.pid (yet?) after start: No such file or directory
Jul 17 15:32:24 ubuntu-bionic systemd[1]: Started Advanced key-value store.
Jul 17 15:32:29 ubuntu-bionic systemd[1]: Stopping Advanced key-value store...
Jul 17 15:32:29 ubuntu-bionic systemd[1]: Stopped Advanced key-value store.
Jul 17 15:32:29 ubuntu-bionic systemd[1]: Starting Advanced key-value store...
Jul 17 15:33:59 ubuntu-bionic systemd[1]: redis-server.service: Start operation timed out. Terminating.
Jul 17 15:33:59 ubuntu-bionic systemd[1]: redis-server.service: Failed with result 'timeout'.
Jul 17 15:33:59 ubuntu-bionic systemd[1]: Failed to start Advanced key-value store.

Notice: Applied catalog in 90.47 seconds

The service doesn't start because of this Jul 17 15:32:24 ubuntu-bionic systemd[1]: redis-server.service: Can't open PID file /var/run/redis/redis-server.pid (yet?) after start: No such file or directory as you can see in the above output.
I have attached the files from /etc/redis from after the first and second run.
Hopefully this will be helpful for you in adding Redis 4.x support, I would help you out more but I don't have the time to work on this right now, I was hoping to get it working on the CI system for the Puppet OpenStack project which requires this for testing on Ubuntu Bionic.
Attachments:
redis.conf.first.txt
redis.conf.puppet.first.txt
redis.conf.puppet.second.txt
redis.conf.second.txt
Best regards
Tobias

Looks like the redis-server.service is masked due to an empty file created in /etc/systemd/system/redis-server.service.d/limit.conf . Try adding "ulimit => false" to invocation of redis class - this solves "masked" issue for me.

I set ulimit => false but nothing changed.
I then manually removed /etc/systemd/system/redis-server.service.d/limit.conf and the error disappeared.
Suggestions:  Ensure absent for the limit.conf file in  ulimit.pp and always contain ::redis::ulimit in config.pp#L42

Recent versions can deploy newer versions. Please open new issues/PRs if there's still something missing.


Multiple serviceentries with same port causing connections to be closed.

Two service entries with different CIDRs, but the same port cause connections to close.
Here is an example (note: the CIDRs are made up for the example):
apiVersion: networking.istio.io/v1alpha3
kind: ServiceEntry
metadata:
  name: cassandra-example1
  namespace: examplens1
spec:
  hosts:
    - cassandraex1.ports # used for metrics
  addresses:
    - <IP_ADDRESS>/24
  ports:
    - name: cassandraex1-client-port
      number: 9042
      protocol: TCP

apiVersion: networking.istio.io/v1alpha3
kind: ServiceEntry
metadata:
  name: cassandra-example2
  namespace: examplens2
spec:
  hosts:
    - cassandraex2.ports # used for metrics
  addresses:
    - <IP_ADDRESS>/24
  ports:
    - name: cassandraex2-client-port
      number: 9042
      protocol: TCP

This will cause intermittent closed connections. Most of the time it will work, but sometimes it will fail.
If I combine these two serviceentries into one, then everything works.
apiVersion: networking.istio.io/v1alpha3
kind: ServiceEntry
metadata:
  name: cassandra-example
  namespace: examplens
spec:
  hosts:
    - cassandra.ports # used for metrics
  addresses:
    - <IP_ADDRESS>/24
    - <IP_ADDRESS>/24
  ports:
    - name: cassandra-client-port
      number: 9042
      protocol: TCP

Affected product area (please put an X in all that apply)
[x] Configuration Infrastructure
[ ] Docs
[ ] Installation
[x] Networking
[ ] Performance and Scalability
[ ] Policies and Telemetry
[ ] Security
[ ] Test and Release
[ ] User Experience
[ ] Developer Infrastructure
Expected behavior
That one can have the same port in multiple service entries as long as the CIDR is different
Version (include the output of istioctl version --remote and kubectl version)
Istio-Version: 1.2.2
Kubernetes-version: v1.12.3
How was Istio installed?
Helm template and then Kubectl apply -f -
Environment where bug was observed (cloud vendor, OS, etc)
AWS

cc @sbezverk to triage


problem with jar files in nativescript plugins

Tell us about the problem
problem with jar files in nativescript plugins

CLI: next
Cross-platform modules:next
Runtime(s): plamen5kov/revert

Please tell us how to recreate the issue in as much detail as possible.
https://github.com/NativeScript/android-runtime/pull/905

Addressed in https://github.com/NativeScript/android-runtime/commit/3f651e9648ff220584d4661924cd1d8a827b2331 currently part of the plamen5kov/revert branch.


Specific data type management testing

Notably

masked data
mixed masks and NaNs (?? but what can you expect?)
integer data with missing
various types of string data

Think this is now done, since new tests here


Feature request and implement: Progressive download for WebP images

New Issue Checklist

[x] I have read and understood the CONTRIBUTING guide
[x] I have read the Documentation
[x] I have searched for a similar issue in the project and found none

Issue Info

Info
Value

Platform Name
all

Platform Version
7.0 above

SDWebImage Version
master(4.1.x)

Integration Method
cocoapods

Xcode Version
Xcode 7.3.2

Repro rate
e.g. all the time (100%) / sometimes x% / only once

Repro with our demo prj
e.g. does it happen with our demo project?

Demo project link
e.g. link to a demo project that highlights the issue

Issue Description and Steps
This is an feature request issue. I completed the implementation of progressive download for WebP images. But it's not suitable to create an Pull Request immediately(lack of race condition test or something). And this also include some code refactor which is on 4.1.1 milstone. So I think create a new issue about this feature and to discuss is better.
Changes:

Add progressive decoding using libwebp's WebPIDecoder. Because currently we use ImageIO to load progressive images. But it does not support WebP and will fail on CGImageSourceCreateWithData.
Refactor code about current progressive code after than long if ((self.options & SDWebImageDownloaderProgressiveDownload) && self.expectedSize > 0) {xxxxxxx}. I create two method called progressiveDownloadForImageIO and progressiveDownloadForWebP to do these procedure.

The demo is here :

Pull request is here:  #1987

Merged via #1991.


Added video classification TFLite code.

This is the first pull request to add a video classification sample to the TFLite Reference app repo.
This pull request contains:

VideoClassifier: The wrapper class to run video classification with an interface that resembles the TFLite Task Library.
VideoClassifierTest: The test code of the video classifier.
CalculateUtils: Some shared utils.

@mbrenon PTAL as well. Thanks!

@lu-wang-g Thanks for reviewing! I've fixed the feedback and made some minor changes:

Changed the model used from float model to int8 quantized model to reduce inference time.
Changed the test video as the previous one didn't work well with int8 model.

Submitted in https://github.com/tensorflow/examples/commit/86e95a594ffd7a74016a2b15991d2294725d7e28


installed CBS with overrides

Changes

moved to Carbon Design System (aka. CBS in commit messages)

still supports react v17 (override allows installation as-is)

Discussion and Override
See here for the v18 support, https://github.com/carbon-design-system/carbon/issues/11308

Renders

side effect of this was the sidebar animation improving through better layout


Chance to display prices on notification messages

Added method _indicator_messages() to get OHLCV prices and then can be used on notification messages.
For the moment it is used only for notifiy_telegram(). After testing can be used for all other notify methods.

I'm going to add more changes, thats why I'm closing this pull request.


python311Packages.botocore-stubs: 1.34.134 -> 1.34.135

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for python311Packages.botocore-stubs is: Type annotations and code completion for botocore
meta.homepage for python311Packages.botocore-stubs is: https://pypi.org/project/botocore-stubs/
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 1.34.127 with grep in /nix/store/wkqaakmvaf69srl93ccqgidna66gy7k6-python3.11-botocore-stubs-1.34.127
found 1.34.127 in filename of file in /nix/store/wkqaakmvaf69srl93ccqgidna66gy7k6-python3.11-botocore-stubs-1.34.127

Rebuild report (if merged into master) (click to expand)

8 total rebuild path(s)

8 package rebuild(s)

First fifty rebuilds by attrpath

aws-sam-cli
python311Packages.boto3-stubs
python311Packages.botocore-stubs
python311Packages.types-aiobotocore
python312Packages.boto3-stubs
python312Packages.botocore-stubs
python312Packages.types-aiobotocore

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/wkqaakmvaf69srl93ccqgidna66gy7k6-python3.11-botocore-stubs-1.34.127 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A python311Packages.botocore-stubs https://github.com/r-ryantm/nixpkgs/archive/1b802f41a69c97c16cf62054462600268d52c99c.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/1b802f41a69c97c16cf62054462600268d52c99c#python311Packages.botocore-stubs

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/wkqaakmvaf69srl93ccqgidna66gy7k6-python3.11-botocore-stubs-1.34.127
ls -la /nix/store/wkqaakmvaf69srl93ccqgidna66gy7k6-python3.11-botocore-stubs-1.34.127/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review --extra-nixpkgs-config '{ allowInsecurePredicate = x: true; }' run on x86_64-linux 1

2 packages failed to build:

aws-sam-cli
aws-sam-cli.dist

12 packages built:

python311Packages.boto3-stubs
python311Packages.boto3-stubs.dist
python311Packages.botocore-stubs
python311Packages.botocore-stubs.dist
python311Packages.types-aiobotocore
python311Packages.types-aiobotocore.dist
python312Packages.boto3-stubs
python312Packages.boto3-stubs.dist
python312Packages.botocore-stubs
python312Packages.botocore-stubs.dist
python312Packages.types-aiobotocore
python312Packages.types-aiobotocore.dist

Maintainer pings
cc @fabaff for testing.

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for python311Packages.botocore-stubs is: Type annotations and code completion for botocore
meta.homepage for python311Packages.botocore-stubs is: https://pypi.org/project/botocore-stubs/
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 1.34.135 with grep in /nix/store/kqnsw0cw2fqqr702f0bng3lbyq17qbj6-python3.11-botocore-stubs-1.34.135
found 1.34.135 in filename of file in /nix/store/kqnsw0cw2fqqr702f0bng3lbyq17qbj6-python3.11-botocore-stubs-1.34.135

Rebuild report (if merged into master) (click to expand)

8 total rebuild path(s)

8 package rebuild(s)

First fifty rebuilds by attrpath

aws-sam-cli
python311Packages.boto3-stubs
python311Packages.botocore-stubs
python311Packages.types-aiobotocore
python312Packages.boto3-stubs
python312Packages.botocore-stubs
python312Packages.types-aiobotocore

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/kqnsw0cw2fqqr702f0bng3lbyq17qbj6-python3.11-botocore-stubs-1.34.135 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A python311Packages.botocore-stubs https://github.com/r-ryantm/nixpkgs/archive/70a5855fb6a383b35e6b232178e5471e26b9b7df.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/70a5855fb6a383b35e6b232178e5471e26b9b7df#python311Packages.botocore-stubs

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/kqnsw0cw2fqqr702f0bng3lbyq17qbj6-python3.11-botocore-stubs-1.34.135
ls -la /nix/store/kqnsw0cw2fqqr702f0bng3lbyq17qbj6-python3.11-botocore-stubs-1.34.135/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

14 packages built:

aws-sam-cli
aws-sam-cli.dist
python311Packages.boto3-stubs
python311Packages.boto3-stubs.dist
python311Packages.botocore-stubs
python311Packages.botocore-stubs.dist
python311Packages.types-aiobotocore
python311Packages.types-aiobotocore.dist
python312Packages.boto3-stubs
python312Packages.boto3-stubs.dist
python312Packages.botocore-stubs
python312Packages.botocore-stubs.dist
python312Packages.types-aiobotocore
python312Packages.types-aiobotocore.dist

Maintainer pings
cc @fabaff for testing.

Done in #323437.


Disable roll angle saturation

The Whipple model and Kalman filter seem to work and this isn't necessary for now. Disabling roll would also give us nicer plots of the state.

PR https://github.com/oliverlee/phobos/pull/113

Merged https://github.com/oliverlee/phobos/commit/faf1e7ebef8d266071c185f9bd71b0b81f2ee18b