Wrong Battery Voltage @ VRM and Remote Console Overview

I use a Daly 8S 150A BMS and using the newest prerelease 12b2.
The new cell voltages view displays the correct battery voltage. However, in the Remote Console overview as well as in the Victron VRM Portal the voltage is displayed incorrectly. The real voltage is ~27.58V, which is correctly read out in the new sub-item, but the Remote Console overview and the VRM show 27.50V. Attached are a few screenshots.
The whole thing is read out via Daly UART cable and the VenusOS runs on a Raspberry Pi 3 b+ with VenusOS 2.89.
It would be great if the correct voltage can also be displayed in the VRM and the Remote Console overview.

I use 3 different Daly 16S BMS with OS 2.89 and the 12b2 release but i do not see the different cell voltage page? What must i do to see the page?

I use 3 different Daly 16S BMS with OS 2.89 and the 12b2 release but i do not see the different cell voltage page? What must i do to see the page?

qml files are installed by running "sh /data/etc/dbus-serialbattery/installqml.sh"
WARNING! - by running the "installqml.sh" is the existing file "/opt/victronenergy/gui/qml/PageBattery.qml" overwritten
https://github.com/Louisvdw/dbus-serialbattery/pull/87

Thanks! 👍

I have at least managed to get the exact values displayed in the Remote Console. Replace the line in the file "PageBattery.qml":
property VBusItem dcVoltage: VBusItem { bind: service.path("/Dc/0/Voltage") }
by
property VBusItem dcVoltage: VBusItem { bind: service.path("/Voltages/Sum") }
I still fail to get the voltage displayed in the VRM portal.
I also tried to replace "/Dc/0/Voltage" with "/Voltages/Sum" in dbushelper.py. Then on the VRM overview page the voltage is displayed correct but the power display does not work and the Serial Battery menu item in the remote console has completely disappeared ;-)

The Battery voltage is a measurement over the battery (over the +pole and -pole).
The driver use the battery voltage published by the BMS and while this should be close (as in your case) the cell voltages normally do not perfectly match the battery voltage.

Thank you very much for your quick answer.
Instead of the battery voltage provided by the BMS, would it be a big effort to pick up the SUM voltage of all cells (which works great in the Remote Control Center) and display it in the VRM? Unfortunately I am a complete newbie in Python and my programming skills are rather limited to one or the other (although already quite complex) Powershell script. I am willing, eager to learn and would also add the appropriate code by hand instead of screaming for a new release.

Officially the driver will never do that as it has to work the same for all users and also for all BMS types.
But if you want to make a custom change yourself you can - you will need to change your daly.py to update the self.voltage with the total of the cell voltages.
However this will be wrong most of the time.
Why? Well the Daly protocol is not the best which means we have some limits in reading the amount data. To get around that we update the important data each polling cycle (1sec) like the battery voltage, while some not so important data like the cell voltages is only updated every other polling cycle (2 -3 seconds). Your cell voltages will be old, while your battery voltage will have the correct stuff in them.

Thank you Louis,
have tried something around but just do not come to the associated code. I just had the idea if it would not be possible to use the battery voltage measured by the used Smartsolar as a source for the display of the battery voltage in the VRM Dashboard? Except for minimal deviations, this is accurate. Unfortunately, I have not yet found a way to display the voltage measured by the Smartsolar on the dashboard. You have to switch to the Advanced tab every time.
Call me petty and it's probably a 1st world problem but I'd rather have a display that varies by 0.0x V than one that can only jump up or down in 0.10 increments ;-)


Notification Padding

Hi,
how can i change padding of notification? Regards

Thank you Ahmed, it is fixed now!.
Best Regards,
Giuseppe.
Il giorno gio 1 dic 2022 alle ore 09:42 Ahmed Khalil <
@.***> ha scritto:

Hi @Giuseppe-Argento https://github.com/Giuseppe-Argento Please try to
update to the latest release v5.0.7
https://github.com/awran5/react-floating-whatsapp/compare/v5.0.7...v5.0.7
to see if it fixed.
I also added a new props notificationStyle, notificationClassName to
modify the notification indicator style.
—
Reply to this email directly, view it on GitHub
https://github.com/awran5/react-floating-whatsapp/issues/17#issuecomment-1333406411,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AUBNOF6D5RE7VXYA2L2HIMTWLBQGTANCNFSM6AAAAAASL5DREQ
.
You are receiving this because you were mentioned.Message ID:
@.***>

--
Web Designer / Web Developer
P.IVA<PHONE_NUMBER>1
+39<PHONE_NUMBER>
giuseppeargento.it


Type erasure of AsyncSequences

I have been using this package quite a bit recently and one of the biggest pain points for me is how verbose the type inference tends to get when you start stringing these AsyncSequences together.
Similar to combine's AnyPublisher<Element,Failure> I believe that this package should expose a way to easily erase the type of the async sequence that is being produced.
Whether that be through a new AnyAsyncSequence type or leveraging the existing AsyncStream and AsyncThrowingStream types.
I realize that today AsyncSequence cannot expose its failure type (or lack thereof) and that is probably the reason why something like this does not exist today.
But maybe as a pre 1.x.x convenience we could add something that solves this issue.
At my current company (and in my own personal projects) I use something like this:
fileprivate extension AsyncStream {
    init<Base: AsyncSequence>(from sequence: Base, file: StaticString = #filePath, line: UInt = #line) where Element == Base.Element {
        var iterator = sequence.makeAsyncIterator()
        // FIXME: In later swift versions, AsyncSequence protocol will likely have an associated error type.
        // FIXME: For now, produce an assertionFailure to let developer know to use an AsyncThrowingStream instead.
        self.init {
            do {
                return try await iterator.next()
            } catch {
                assertionFailure("AsyncSequence threw \(error.localizedDescription). Use AsyncThrowingStream instead", file: file, line: line)
                return nil
            }
        }
    }
}

fileprivate extension AsyncThrowingStream {
    init<Base: AsyncSequence>(from sequence: Base) where Element == Base.Element, Failure == Error {
        var iterator = sequence.makeAsyncIterator()
        self.init {
            try await iterator.next()
        }
    }
}

extension AsyncSequence {
    /// Type erases the `AsyncSequence` into an `AsyncStream`
    /// - Returns: An `AsyncStream` created from the base `AsyncSequence`
    ///
    /// - Note: AsyncSequences do not expose their error type.
    /// So this function is available for both throwing and non-throwing `AsyncSequences`.
    /// It will produce an `assertionFailure` at runtime if the base sequence throws.
    func asAsyncStream(file: StaticString = #filePath, line: UInt = #line) -> AsyncStream<Element> {
        AsyncStream(from: self, file: file, line: line)
    }

    /// Type erases the `AsyncSequence` into an `AsyncThrowingStream`
    /// - Returns: An `AsyncThrowingStream` from the base `AsyncSequence`
    func asAsyncThrowingStream() -> AsyncThrowingStream<Element, Error> {
        AsyncThrowingStream(from: self)
    }
}

Hi @BrentMifsud – you may have better engagement if you post on the Swift forums. This definitely feels like an issue that is due further and wider discussion.

@BrentMifsud We know that this is a usability issue right now but it is not something that we want to fix with introducing an AnyAsyncSequence. We really want to express this using any and some but this requires two things:

Adopting primary associated types on AsyncSequence.
Being able to express something like some throwing AsyncSequence<Int>

Both of those require language work and I think we should focus our discussions around how to solve those two issues. This would indeed be something for the forums.

Not wanting to introduce AnyAsyncSequence to the standard library is perfectly understandable. Not wanting to introduce it to an external library is less so. What exactly are the downsides to this library filling a critical hole?

What exactly are the downsides to this library filling a critical hole?

The problem is that I don't think we can express what we want here really unless we make AnyAsyncSequence always throwing. Which to me sounds like a severe limitation. I also don't see it pressing for async-algos to fill this gap which sets out to implement generic algorithms on top of async sequences. AnyAsyncSequence is really more of a tool for internal API design and can be solved in the respective applications. For public API we recommend to create a concrete named type anyhow instead of resorting to AnyAsyncSequence.

I tend to agree with most of the comments here about this being something that should be done as part of the swift language. Rather than in this package.
I'll bring this discussion over to the swift forums.

Since this requires language work and there is an active thread in the forums. I will close this issue. Let's continue the discussion in the forums.


Handling reverse-complement duplicates in paired reads

Starting an issue to keep track of this limitation in our current implementations of deduplication and duplicate statistics.
Currently the CLUMPIFY_PAIRED process has the comment flag "NB: Will NOT handle reverse-complement duplicates". I also believe that duplication statistics are currently being generated from FASTQC, which also does not handle reverse-complement duplicates.

After reading the new Readme, I realize this may be effectively handled by the second pass of clumpify following merging (at least in the taxonomic profiling workflow)

Yeah, this is currently done in the taxonomy subworkflow (which also then gets passed to the second half of the hv subworkflow), as this is where paired reads get merged into single reads.
I'd like to test the behaviour of this step more extensively, to make absolutely sure that it's handling RC duplicates as we expect. Once that's verified, I'm open to copying this process over to other parts of the pipeline as & when it makes sense.

Unfortunately, I don't think clumpify handles reverse complement duplicates, even in non-paired-end mode. Here's a minimal reproducing example, using the same clumpify args (except memory/threads) as CLUMPIFY_SINGLE. We start with two short sequences, reverse complements of one another:
(NAO) Evans-MacBook-Pro:clumptest evan$ cat mre.fasta
>seq
GGGAAACCCTTT
>seq_rc
AAAGGGTTTCCC

(NAO) Evans-MacBook-Pro:clumptest evan$ /Applications/bbmap/clumpify.sh in=mre.fasta out=mre_out.fasta reorder dedupe containment
/Applications/bbmap//calcmem.sh: line 78: [: -v: unary operator expected
Max memory cannot be determined.  Attempting to use 2000 MB.
If this fails, please add the -Xmx flag (e.g. -Xmx24g) to your command,
or run this program qsubbed or from a qlogin session on Genepool, or set ulimit to an appropriate value.
java -ea -Xmx2000m -Xms2000m -cp /Applications/bbmap/current/ clump.Clumpify in=mre.fasta out=mre_out.fasta reorder dedupe containment
Executing clump.Clumpify [in=mre.fasta, out=mre_out.fasta, reorder, dedupe, containment]
Version 39.08

Read Estimate:          0
Memory Estimate:        0 MB
Memory Available:       1601 MB
Set groups to 1
Executing clump.KmerSort1 [in1=mre.fasta, in2=, out1=mre_out.fasta, out2=, groups=1, ecco=false, rename=false, shortname=f, unpair=false, repair=false, namesort=false, ow=true, reorder, dedupe]

Making comparator.
Made a comparator with k=31, seed=1, border=1, hashes=4
Starting cris 0.
Fetching reads.
Making fetch threads.
Starting threads.
Waiting for threads.
Fetch time: 	0.002 seconds.
Closing input stream.
Combining thread output.
Combine time: 	0.000 seconds.
Sorting.
Sort time: 	0.000 seconds.
Making clumps.
Clump time: 	0.001 seconds.
Deduping.
Dedupe time: 	0.001 seconds.
Writing.
Waiting for writing to complete.
Write time: 	0.001 seconds.
Done!
Time:                         	0.051 seconds.
Reads Processed:             2 	0.04k reads/sec
Bases Processed:            24 	0.00m bases/sec

Reads In:                    2
Clumps Formed:               2
Duplicates Found:            0	0.000%
Reads Out:                   2
Bases Out:                  24
Total time: 	0.125 seconds.

(NAO) Evans-MacBook-Pro:clumptest evan$ cat mre_out.fasta
>seq_rc
AAAGGGTTTCCC
>seq
GGGAAACCCTTT

Looking through the available command line options for clumpify, I didn't find a good way to handle RC duplicates. rcomp seemed promising but seems to act at the clump level, which doesn't guarantee correcting duplicates across clumps: a sequence and its reverse complement could end up in different clumps and not get the same canonical representation. Sorcomp doesn't handle this toy case. That said, while the clumpify docs have little to say about how clumps are formed, empirically it seems like maybe for longer sequences, a sequence and its RC do tend to end up in the same clump, or are at least more likely to? In which case a two-pass method could catch some RC duplicates at extra computational cost:
clumpify in=in_file.fastq.gz out=intermediate.fastq.gz rcomp reorder
clumpify in=intermediate.fastq.gz out=dedup.fastq.gz reorder dedupe containment

Dedupe from bbtools might be an appropriate tool here - certainly the docs are clear that it can handle exact reverse-complement duplicates - but there are also warnings about performance and memory usage on large read sets that seem likely to be binding in our use cases. https://jgi.doe.gov/data-and-tools/software-tools/bbtools/bb-tools-user-guide/dedupe-guide/

The trick is to set passes=2. With this test file
>seq copies=3
GATTACA
>seq_rc copies=5
TGTAATC
>seq_dup
GATTACA

and this command,
clumpify.sh in=test.fasta out=out.fa k=7 rcomp passes=2 dedupe addcount=t

the output is
>seq copies=9
TGTAATC

Note, the clumpify docs actually recommend passes=6,

passes=1 Use this many error-correction passes. 6 passes are
suggested, though more will be more through.

v2.3.0 now includes multiple passes of Clumpify when running single-ended. However, there appear to be other issues with deduplication beyond this, which I'll flag in a separate issue. Closing this one.


Memory Leak in the function mbedtls_rsa_rsassa_pkcs1_v15_sign

In the function mbedtls_rsa_rsassa_pkcs1_v15_sign, there is a possibility of memory leak in the below code segment (Line No 1088 for mbed-tls 2.2.0 version):
sig_try = mbedtls_calloc( 1, ctx->len );
verif   = mbedtls_calloc( 1, ctx->len );
if( sig_try == NULL || verif == NULL )
    return( MBEDTLS_ERR_MPI_ALLOC_FAILED );

In this case, if memory allocation to sig_try succeeds, but, if memory allocation to verif fails, then sig_try pointer is not freed which can lead to memory leak.
Simple Fix Suggestion:
sig_try = mbedtls_calloc( 1, ctx->len );
if(NULL == sig_try)
    return( MBEDTLS_ERR_MPI_ALLOC_FAILED );
verif   = mbedtls_calloc( 1, ctx->len );
if( NULL == verif)
{
    mbedtls_free(sig_try);
    return( MBEDTLS_ERR_MPI_ALLOC_FAILED );
}

ARM Internal Ref: IOTSSL-579

This issue has been fixed in mbed TLS releases, 2.2.1, 2.1.4 and 1.3.16.


[FLINK-7325] [futures] Replace Flink's futures by Java 8's CompletableFuture in MiniCluster

What is the purpose of the change
Replace Flink's futures by Java 8's CompletableFuture in MiniCluster.
This PR is based on #4429.
Verifying this change
This change is a trivial rework / code cleanup without any test coverage.
Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): (no)
The public API, i.e., is any changed class annotated with @Public(Evolving): (no)
The serializers: (no)
The runtime per-record code paths (performance sensitive): (no)
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Yarn/Mesos, ZooKeeper: (no)

Documentation

Does this pull request introduce a new feature? (no)

Thanks for the review @zentol. Travis passed. Merging this PR.


Inference client doc

"Fixes #issue-number" or "Add description of the problem this PR solves"
Proposed Changes

/approve


Allow logged out user to make recurring donations

Depends on #57 .  The recurring options are currently disabled for logged out users.  Enable them since we will be able to associate the donation to a user account once #57 is complete.

Recurring donations can be made with card.
TODO - enable bank payments for similar


Crashed on com.google.fira.worker

Crash reported by Crashlytics:
iOS 12.4.1 (16G102)
iPhone 7
Fatal Exception: NSInternalInconsistencyException
Incorrect or nil NSTextStorage requested for undo operation: <_UITextUndoOperationReplace: 0x280a9d900>
+[_CFXNotificationTokenRegistration keyCallbacks]
Stack trace:
com.google.fira.worker
0  libsystem_kernel.dylib         0x1acce0408 fsync + 8
1  libsqlite3.dylib               0x1ad5a63ec sqlite3_free_table + 67964
2  libsqlite3.dylib               0x1ad5b0e2c sqlite3_randomness + 2284
3  libsqlite3.dylib               0x1ad5a5cf8 sqlite3_free_table + 66184
4  libsqlite3.dylib               0x1ad590154 sqlite3_value_text + 23708
5  libsqlite3.dylib               0x1ad55bdf4 sqlite3_finalize + 3636
6  libsqlite3.dylib               0x1ad588404 sqlite3_step + 64128
7  libsqlite3.dylib               0x1ad578b40 sqlite3_step + 444
8  libsqlite3.dylib               0x1ad5415f8 sqlite3_exec + 324
9  PO3-Residential                0x104b644d8 -[APMSqliteStore endTransaction] + 1284104
10 PO3-Residential                0x104b64190 -[APMSqliteStore performTransaction:] + 1283264
11 PO3-Residential                0x104b39110 -[APMMeasurement writeEventOnWorkerQueue:] + 1107008
12 PO3-Residential                0x104b387a8 -[APMMeasurement handleEventOnWorkerQueue:] + 1104600
13 PO3-Residential                0x104b4d86c __51-[APMScheduler scheduleOnWorkerQueueBlockID:block:]_block_invoke + 1190812
14 libdispatch.dylib              0x1acb80a38 _dispatch_call_block_and_release + 24
15 libdispatch.dylib              0x1acb817d4 _dispatch_client_callout + 16
16 libdispatch.dylib              0x1acb2a324 _dispatch_lane_serial_drain$VARIANT$mp + 592
17 libdispatch.dylib              0x1acb2ae40 _dispatch_lane_invoke$VARIANT$mp + 428
18 libdispatch.dylib              0x1acb334ac _dispatch_workloop_worker_thread + 596
19 libsystem_pthread.dylib        0x1acd62114 _pthread_wqthread + 304
20 libsystem_pthread.dylib        0x1acd64cd4 start_wqthread + 4

@PradeshKumar88 Thank you for your issue report.
The provided stack trace does not look like directly related to the specified exception. Could you post a full crash log for us to better understand the issue? Feel free to mask your app calls that you wouldn't like to share or let me know if you would like to share it privately.

@PradeshKumar88 please fill out the issue template and provide your Firebase versions as well.

You can check your nanopb version, or try pod update.
I think this is related to this issue:
[app crash when calling apmpb_free_event_field on com.google.fira.worker]
https://github.com/firebase/firebase-ios-sdk/issues/4154


Restore reproducible libs

Investigating gnu lib reproducibility issue, see if we can get two birds with one PR here.

OK @kennykerr looking good. Manually verified the msvc/gnu libs against the workflow ones and they match now. We'll revisit and hopefully clean all this up soon.

A MacOS concurrency limit is holding things up - since everything else has passed I'm going to cancel the run and complete the PR to relieve some pressure.


fix(blob): add fixes along with the fuzzers that discovered them

This changes adds fuzzers+corpra that found some bugs,
along with tests and reproducers to catch future regressions.
Fixes #3727
Fixes #3728
Fixes #3729
Fixes #3730
Fixes #3731

@odeke-em, do you mind fixing linter?

Hey @odeke-em. Thank you again for your contribution. We want to merge, but we can't until the linter is fixed. We can't push to your branch so we may do another PR cherry-picking your changes if you don't fix linter and rebase.

Thanks for the ping @Wondertan! I've made an update but I'd like to point out that maybe I am missing context but it is a mistake to prefer relative imports within the same package instead of the whole package: to make things work I had to make repro_test.go skip the absolute import which doesn't look right to make and makes it later cumbersome to copy and paste full working repros
diff --git a/blob/repro_test.go b/blob/repro_test.go
index 5489a6a4..42bd966f 100644
--- a/blob/repro_test.go
+++ b/blob/repro_test.go
@@ -4,13 +4,14 @@ import (
 	"testing"

 	"github.com/celestiaorg/celestia-app/v2/pkg/proof"
-	"github.com/celestiaorg/celestia-node/blob"
 	"github.com/celestiaorg/nmt"
 	"github.com/celestiaorg/nmt/pb"
 )

 // Reported at https://github.com/celestiaorg/celestia-node/issues/3731.
 func TestCommitmentProofRowProofVerifyWithEmptyRoot(t *testing.T) {
+	cp := &CommitmentProof{
-	cp := &blob.CommitmentProof{
 		RowProof: proof.RowProof{
 			Proofs: []*proof.Proof{{}},
 		},
@@ -23,7 +24,7 @@ func TestCommitmentProofRowProofVerifyWithEmptyRoot(t *testing.T) {

 // Reported at https://github.com/celestiaorg/celestia-node/issues/3730.
 func TestCommitmentProofRowProofVerify(t *testing.T) {
+	cp := &CommitmentProof{
-	cp := &blob.CommitmentProof{
 		RowProof: proof.RowProof{
 			Proofs: []*proof.Proof{{}},
 		},
@@ -36,7 +37,7 @@ func TestCommitmentProofRowProofVerify(t *testing.T) {
 // Reported at https://github.com/celestiaorg/celestia-node/issues/3729.
 func TestCommitmentProofVerifySliceBound(t *testing.T) {
 	proof := nmt.ProtoToProof(pb.Proof{End: 1})
+	cp := &CommitmentProof{
-	cp := &blob.CommitmentProof{
 		SubtreeRootProofs: []*nmt.Proof{
 			&proof,
 		},
@@ -48,7 +49,7 @@ func TestCommitmentProofVerifySliceBound(t *testing.T) {

 // Reported at https://github.com/celestiaorg/celestia-node/issues/3728.
 func TestCommitmentProofVerifyZeroSubThreshold(t *testing.T) {
+	cp := new(CommitmentProof)
-	cp := new(blob.CommitmentProof)
 	if _, err := cp.Verify(nil, 0); err == nil {
 		t.Fatal("expected a non-nil error")
 	}
@@ -56,8 +57,8 @@ func TestCommitmentProofVerifyZeroSubThreshold(t *testing.T) {

 // Reported at https://github.com/celestiaorg/celestia-node/issues/3727.
 func TestBlobUnmarshalRepro(t *testing.T) {
+	blob := new(Blob)
+	if err := UnmarshalJSON([]byte("{}")); err == nil {
-	blob := new(blob.Blob)
-	if err := blob.UnmarshalJSON([]byte("{}")); err == nil {
 		t.Fatal("expected a non-nil error")
 	}
 }

but it is a mistake to prefer relative imports within the same package instead of the whole package

@odeke-em, I highly doubt that unless you meant particularly for tests. For tests, yes, we could make every test file its own pkg blob_test instead of blob to enforce that, and it might be something we will do at some point, but currently, this is very far from our current prioritize and has low to no impact.

Well, linter is still failing

@Wondertan thanks for the review, kindly help me re-run the bots and all tests should pass now!

@Wondertan perhaps we have a test flake at https://github.com/celestiaorg/celestia-node/actions/runs/11126830327/job/30918109533?pr=3732
2024-10-01T14:05:14.951Z	ERROR	share/full	full/availability.go:71	availability validation failed	{"root": "94B65AB76ACAE0512B7A450F77110CD8CE25DD417ECDEDEE26814FAA2FEAF678", "err": "data not found\nread status from stream: protocols not supported: [/private/shrex/v0.1.0/eds_v0]\ndata not found\ncontext deadline exceeded\ncontext deadline exceeded"}
2024-10-01T14:08:14.972Z	ERROR	pruner/service	pruner/find.go:44	failed to get range from header store	{"from": 1024, "to": 1025, "error": "header/store: invalid range(1025,1024)"}
2024-10-01T14:08:15.044Z	ERROR	pruner/service	pruner/find.go:44	failed to get range from header store	{"from": 1024, "to": 1025, "error": "header/store: invalid range(1025,1024)"}
2024-10-01T14:08:15.102Z	ERROR	pruner/service	pruner/find.go:44	failed to get range from header store	{"from": 1024, "to": 1025, "error": "header/store: invalid range(1025,1024)"}
2024-10-01T14:08:15.116Z	ERROR	pruner/service	pruner/find.go:44	failed to get range from header store	{"from": 1024, "to": 1025, "error": "header/store: invalid range(1025,1024)"}
2024-10-01T14:08:15.191Z	ERROR	share/full	full/availability.go:71	availability validation failed	{"root": "94B65AB76ACAE0512B7A450F77110CD8CE25DD417ECDEDEE26814FAA2FEAF678", "err": "data not found\nopen stream: failed to negotiate protocol: protocols not supported: [/private/shrex/v0.1.0/eds_v0]\ndata not found\ncontext deadline exceeded\ncontext deadline exceeded"}
2024-10-01T14:14:15.236Z	ERROR	share/full	full/availability.go:71	availability validation failed	{"root": "94B65AB76ACAE0512B7A450F77110CD8CE25DD417ECDEDEE26814FAA2FEAF678", "err": "data not found\nopen stream: failed to negotiate protocol: protocols not supported: [/private/shrex/v0.1.0/eds_v0]\ndata not found\ncontext deadline exceeded\ncontext deadline exceeded"}
panic: test timed out after 20m0s
	running tests:
		TestArchivalBlobSync (20m0s)

goroutine 750540 [running]:
testing.(*M).startAlarm.func1()
	/opt/hostedtoolcache/go/1.23.1/x64/src/testing/testing.go:2373 +0x385
created by time.goFunc
	/opt/hostedtoolcache/go/1.23.1/x64/src/time/sleep.go:215 +0x2d

goroutine 1 [chan receive, 20 minutes]:
testing.(*T).Run(0xc0007ae000, {0x2fdd437?, 0x0?}, 0x384ea60)
	/opt/hostedtoolcache/go/1.23.1/x64/src/testing/testing.go:1751 +0x3ab
testing.runTests.func1(0xc0007ae000)
	/opt/hostedtoolcache/go/1.23.1/x64/src/testing/testing.go:2168 +0x37
testing.tRunner(0xc0007ae000, 0xc00129fc70)
	/opt/hostedtoolcache/go/1.23.1/x64/src/testing/testing.go:1690 +0xf4
testing.runTests(0xc000147158, {0x56acb00, 0x2, 0x2}, {0x475e90?, 0x475afa?, 0x57d7740?})
	/opt/hostedtoolcache/go/1.23.1/x64/src/testing/testing.go:2166 +0x43d
testing.(*M).Run(0xc0012da640)
	/opt/hostedtoolcache/go/1.23.1/x64/src/testing/testing.go:2034 +0x64a
main.main()
	_testmain.go:47 +0x9b

goroutine 5 [select, 20 minutes]:
github.com/desertbit/timer.timerRoutine()
	/home/runner/go/pkg/mod/github.com/desertbit/timer@v0.0.0-20180107155436-c41aec40b27f/timers.go:119 +0x9e
created by github.com/desertbit/timer.init.0 in goroutine 1
	/home/runner/go/pkg/mod/github.com/desertbit/timer@v0.0.0-20180107155436-c41aec40b27f/timers.go:15 +0x1a

goroutine 7 [select, 20 minutes]:
github.com/ipfs/go-log/writer.(*MirrorWriter).logRoutine(0xc0000c6420)
	/home/runner/go/pkg/mod/github.com/ipfs/go-log@v1.0.5/writer/writer.go:71 +0x105
created by github.com/ipfs/go-log/writer.NewMirrorWriter in goroutine 1
	/home/runner/go/pkg/mod/github.com/ipfs/go-log@v1.0.5/writer/writer.go:36 +0xbf

goroutine 20 [select]:
github.com/golang/glog.(*fileSink).flushDaemon(0x57d7958)
	/home/runner/go/pkg/mod/github.com/golang/glog@v1.2.1/glog_file.go:351 +0xb4
created by github.com/golang/glog.init.1 in goroutine 1
	/home/runner/go/pkg/mod/github.com/golang/glog@v1.2.1/glog_file.go:166 +0x126

goroutine 21 [select]:
go.opencensus.io/stats/view.(*worker).start(0xc0003bc200)
	/home/runner/go/pkg/mod/go.opencensus.io@v0.24.0/stats/view/worker.go:292 +0x9f
created by go.opencensus.io/stats/view.init.0 in goroutine 1
	/home/runner/go/pkg/mod/go.opencensus.io@v0.24.0/stats/view/worker.go:34 +0x8d

goroutine 23 [IO wait, 20 minutes]:
internal/poll.runtime_pollWait(0x7f417b662038, 0x72)
	/opt/hostedtoolcache/go/1.23.1/x64/src/runtime/netpoll.go:351 +0x85
internal/poll.(*pollDesc).wait(0xc0006c0880?, 0xc0005bdd50?, 0x0)
	/opt/hostedtoolcache/go/1.23.1/x64/src/internal/poll/fd_poll_runtime.go:84 +0x27
internal/poll.(*pollDesc).waitRead(...)
	/opt/hostedtoolcache/go/1.23.1/x64/src/internal/poll/fd_poll_runtime.go:89
internal/poll.(*FD).ReadMsg(0xc0006c0880, {0xc0005bdd50, 0x10, 0x10}, {0xc0004f0c28, 0x1000, 0x1000}, 0x40000000)
	/opt/hostedtoolcache/go/1.23.1/x64/src/internal/poll/fd_unix.go:302 +0x385
net.(*netFD).readMsg(0xc0006c0880, {0xc0005bdd50?, 0x9?, 0x8d07000000?}, {0xc0004f0c28?, 0x3caae40?, 0x0?}, 0x1?)
	/opt/hostedtoolcache/go/1.23.1/x64/src/net/fd_posix.go:78 +0x31
net.(*UnixConn).readMsg(0xc00008a988, {0xc0005bdd50?, 0x41806b?, 0x7f[413](https://github.com/celestiaorg/celestia-node/actions/runs/11126830327/job/30918109533?pr=3732#step:4:414)49c12c8?}, {0xc0004f0c28?, 0xc0006ebdd0?, 0x472c1d?})
	/opt/hostedtoolcache/go/1.23.1/x64/src/net/unixsock_posix.go:115 +0x45
net.(*UnixConn).ReadMsgUnix(0xc00008a988, {0xc0005bdd50?, 0x30?, 0x50?}, {0xc0004f0c28?, 0x7f41349c12c8?, 0x18?})
	/opt/hostedtoolcache/go/1.23.1/x64/src/net/unixsock.go:143 +0x36
github.com/godbus/dbus.(*oobReader).Read(0xc0004f0c08, {0xc0005bdd50?, 0xc0006ebe30?, 0x413025?})
	/home/runner/go/pkg/mod/github.com/godbus/dbus@v0.0.0-20190726142602-4481cbc300e2/transport_unix.go:21 +0x3c
io.ReadAtLeast({0x3c71c00, 0xc0004f0c08}, {0xc0005bdd50, 0x10, 0x10}, 0x10)
	/opt/hostedtoolcache/go/1.23.1/x64/src/io/io.go:335 +0x90
io.ReadFull(...)
	/opt/hostedtoolcache/go/1.23.1/x64/src/io/io.go:354
github.com/godbus/dbus.(*unixTransport).ReadMessage(0xc000146e10)
	/home/runner/go/pkg/mod/github.com/godbus/dbus@v0.0.0-20190726142602-4481cbc300e2/transport_unix.go:91 +0xfe
github.com/godbus/dbus.(*Conn).inWorker(0xc000611050)
	/home/runner/go/pkg/mod/github.com/godbus/dbus@v0.0.0-20190726142602-4481cbc300e2/conn.go:294 +0x35
created by github.com/godbus/dbus.(*Conn).Auth in goroutine 1
	/home/runner/go/pkg/mod/github.com/godbus/dbus@v0.0.0-20190726142602-4481cbc300e2/auth.go:118 +0x8ee

@odeke-em, it is flaky, yes


Update to 0.3.0

Change Description
Add getName
Bump to UAL v0.3.0
API Changes

[ ] API Changes

Documentation Additions

[ ] Documentation Additions

Since CI doesn't seem to be working here, just run the tests and build locally and if its good I'll merge

Running successfully locally


Bug fix in OVEP csharp sample

Updated OVEP csharp sample for a bug fix

@jywu-msft Please review

@shamaksx please read the following Contributor License Agreement(CLA). If you agree with the CLA, please reply with the following information.
@microsoft-github-policy-service agree [company="{your company}"]

Options:

(default - no company specified) I have sole ownership of intellectual property rights to my Submissions and I am not making Submissions in the course of work for my employer.
(when company given) I am making Submissions in the course of work for my employer (or my employer has intellectual property rights in my Submissions by contract or applicable law). I have permission from my employer to make Submissions and enter into this Agreement on behalf of my employer. By signing below, the defined term “You” includes me and my employer.

Contributor License Agreement

@microsoft-github-policy-service agree [company="intel"]

@shamaksx the command you issued was incorrect. Please try again.
Examples are:
@microsoft-github-policy-service agree

and
@microsoft-github-policy-service agree company="your company"

@microsoft-github-policy-service agree company="intel"


"paste code into file" without creating a new cell

Please consider adding a toggle for "paste code into file" without creating a new cell and sometimes users may just wanna insert the code somewhere in the existing code.

The latest behavior here is to just support a copy-to-clipboard button in the interactive window. This still includes the initial # %%. However, you can also just click into the IW cell and press Ctrl+A to select all, then Ctrl+C to copy just the text.


fix: add reachable label when a purl does not have a vendor

This solves an issue where a purl does exists but the reachable label is skipped as vendor param is missing.
Ref: https://github.com/owasp-dep-scan/dep-scan/discussions/339#discussioncomment-10594626

Please use signed commits next time to make auto merge work.


production setup doc cleanup and updates

Related issues
none
Short description and why it's useful

gets rid of issues when setting vhost when not understanding how to setup SSL
includes vhost config change already merged in https://github.com/DivanteLtd/vue-storefront/pull/2570
simplifies the text based on the community feedback and questions asked
bumps the software versions to most recent available (ES) or the most recent supported (node)

Screenshots of visual changes before/after (if there are any)
none, just doc update
Which environment this relates to
Check your case. In case of any doubts please read about Release Cycle

[x] Test version (https://test.storefrontcloud.io) - this is a new feature or improvement for Vue Storefront. I've created branch from develop branch and want to merge it back to develop
[x] RC version (https://next.storefrontcloud.io) - this is a stabilisation fix for Release Candidate of Vue Storefront. I've created branch from release branch and want to merge it back to release
[x] Stable version (https://demo.storefrontcloud.io) - this is an important fix for current stable version. I've created branch from hotfix or master branch and want to merge it back to hotfix

Upgrade Notes and Changelog

[x] No upgrade steps required (100% backward compatibility and no breaking changes)
[x] I've updated the Upgrade notes and Changelog on how to port existing VS sites with this new feature

IMPORTANT NOTICE - Remember to update CHANGELOG.md with description of your change
Contribution and currently important rules acceptance

[x] I read and followed contribution rules
[x] I read the TypeScript Action Plan and adjusted my PR according to it
[x] I read about Vue Storefront Modules and I am aware that every new feature should be a module

@janmyszkier looks pretty awesome to me, the only thing is that it should be merged to master rather than develop. We usually update docs right away without going through the whole release cycle unless docs changes are code dependent.

@lukeromanowicz should I (in that case) re-crate the PR to master? or we can just wait till it's merged with the next release from develop?


cudart64_110.dll not found (v1.6.1)

uh hello it's me again i'm sorry to bother you but i have another problem on the new version
i'm going to attach a image of my error and again i'm sorry to bother you
i don't know maybe i just have a bad pc

It seems like an error with GPU configuration, you might want to follow the setup of CUDA here. Did you use the old TTS or the new one?

i don't know which tts i use i just download a new version and delete old version

i'm sorry i don't really that much in programming and this stuff

What options did you choose on the login screen?

on that login screen?

Nevermind it was an import error that doesn't matter, you can try following the guide in my first reponse and I'll try to make a release without GPU.

okay

Okay so I read install Pygmalion locally and I think that it needs an Nvidia gpu right?

Yes, the specs are specified there

Well I don't have an Nvidia so it may be a trouble for me

Okay I'll make a build available asap

What is asap?

As soon as possible

Okay I'll wait then

I've made a new built and a new procedure to have separate setup for CPU or GPU. Check the new tutorial here: https://github.com/Rubiksman78/MonikA.I/wiki/Installation-tutorial-(after-1.6.1)

i installed all as it says in the new tutorial

Can you launch the file run.bat from your terminal?
Do right click in the project folder in a blank space, click Open in terminal/Command Prompt, when the terminal open write ./run.bat, enter and do the login. Then report the error that will be displayed.

There were some issue with this new procedure, check the wiki again and follow the new instructions.

okay i'll try to follow the instructions and tell you the result

when i try to install a c++ build tools but it displays error so i can't install c++ build tools

What is the error? I suggest you to follow the tutorial linked and find the version of Visual Studio that corresponds to your OS.

I've updated the wiki page and the new drive link. You can maybe try with this new install.

Okay I'll try

great now i have this problem

i'm already tired of getting this errors
maybe i need a new pc

yes i download a new file and follow all the instruction except a setup a gpu

I've updated it quiet recently, maybe you can check again. Can you show me your folder after unzipping it please?

that folder?

where i unzip this right?

Yes the Monik.A.I-v1.6.1.zip folder after extracting it

this folder?

or this folder?

Try running update.bat and then running run.bat. If it still doesn't work, reinstall the zip file from the link that might have been updated from before.

when i first download a new zip file for first i run run.bat then i run update.bat
but okay i'll try to reinstall zip file

This error was due to a forgotten package on my side. I'll update the zip file asap, sorry for the inconvenience.

It is updated, let me know if you run into other errors.

i download an updated version
then i run update.bat
then i run run.bat and now it shows this

does this mean that i already have this requrirement?

Yes, there were some bugs with the actual link, I'll update it once again with the messing packages.

okay i'll wait

Here: https://drive.google.com/file/d/12If6hb7HvoYkLYzuh52wAWLn6KOQ6f6m/view?usp=sharing

okay thanks

i download this new version and it displays the same as my last screenshot

thanks the login screen has appear

so i need just to fill the options and submit and then the game will be turned on right?

Yes, follow the wiki.

okay thanks for the help

I'll close this issue for now. Feel free to reopen it if you run into other troubles not addressed in the documentation.


Not an issue but suggestion

To run on Jetson Nano via CSI camera this script I found was very helpful:
./darknet detector demo cfg/obj.data cfg/yolov4-tiny/masks.cfg yolov4-tiny-obj_last.weights "nvarguscamerasrc ! video/x-raw(memory:NVMM), width=1920, height=1080, format=(string)NV12, framerate=(fraction)30/1 ! nvvidconv flip-method=2  ! video/x-raw, format=(string)BGRx ! videoconvert ! video/x-raw, format=(string)BGR ! appsink"

Thanks for the feedback!


sample dataset

@methylDragon Thanks for the awesome tutorial. It will be a great help if provided with a sample dataset.(bagfile).
Kind regards

Hi there!
Unfortunately, I don't have access to a robot at the moment :( It's going to take awhile before I do.

@methylDragon ok I understood, Anyhow am trying with fuse /gnss_pose, lidar_localizer_pose and /imu_raw using EKF. I have recorded a bag file, will it possible to help me to test and verify my dataset with your package.
I greatly appreciate your support.
Kind regards.

Hi, I don't think I have the capacity to help with that at the moment.
The tutorial should be sufficient for you to implement sensor fusion on
your own.
Cheers,
CH3
On Fri, 10 Apr 2020, 09:25 ajay1606<EMAIL_ADDRESS>wrote:

@methylDragon https://github.com/methylDragon ok I understood, Anyhow
am trying with fuse /gnss_pose, lidar_localizer_pose and /imu_raw using
EKF. I have recorded a bag file, will it possible to help me to test and
verify my dataset with your package.
I greatly appreciate your support.
Kind regards.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/methylDragon/ros-sensor-fusion-tutorial/issues/5#issuecomment-611829924,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AE2TVRSAD6JMN5B7O52O2PDRLZYPZANCNFSM4MEPQG3A
.

@methylDragon Thank you. I have successfully tested the package with my dataset (GNSS + LIDAR + IMU ). Thank you so much for the detailed explanation.
If anyone looking for a dataset, I am happy to share.
Regards,
Ajay

Hi @ajay1606, if you would like to, you can send a pull request to update the README with a link to your dataset, so people can use it.

@methylDragon Well, please find the sample dataset in the following link.
https://drive.google.com/open?id=1Qk9Vu4d5MxOcwKdsoboUAesqctSonuwZ
Dataset acquired in the LGSVL (An Autonomus Vehicle Simulator) along with Autoware (Autonomous driving open source).
Parameter setting required to use this bag file:

[true, true, true,
false, false, false,
false, false, false,
false, false, true,
false, false, false]
[true, true, true,
false, false, false,
false, false, false,
false, false, true,
false, false, false]
[false, false, false,
true,  true,  true,
false, false, false,
true,  true,  true,
true,  true,  true]
Thanks

link with the data set is no longer available. Is there any chance to find the data set and try the tutorial?

link with the data set is no longer available. Is there any chance to find the data set and try the tutorial?

Unfortunately at this time I don't have any plans to record a dataset to use with the tutorial...
But it shouldn't be too hard to set up a Gazebo simulation environment with one of the many different simulated robots and set up the sensor fusion to try it out.

Thanks for your quick answer, I will do it.


Binding issue with Tizen.NET

Hello
I added a Tizen.NET API v5 platform project and I get the following exception when starting the App:
System.TypeInitializationException: The type initializer for 'SQLite.SQLiteConnection' threw an exception.
---> System.Exception: This is the 'bait'.  You probably need to add one of the SQLitePCLRaw.bundle_* nuget packages to your platform project.
at SQLitePCL.Batteries_V2.Init()
at SQLite.SQLiteConnection..cctor()
--- End of inner exception stack trace ---
at SQLite.SQLiteConnection..ctor(SQLiteConnectionString connectionString)
at SQLite.SQLiteConnectionWithLock..ctor(SQLiteConnectionString connectionString)
at SQLite.SQLiteConnectionPool.Entry.Connect()
at SQLite.SQLiteConnectionPool.GetConnection(SQLiteConnectionString connectionString)
at SQLite.SQLiteAsyncConnection.GetConnection()
at SQLite.SQLiteAsyncConnection.get_TableMappings()
at Todo.TodoItemDatabase.InitializeAsync()
at Todo.TaskExtensions.SafeFireAndForget(Task task, Boolean returnToCallingContext, Action`1 onException)
at System.Threading.Tasks.Task.<>c.<ThrowAsync>b__139_0(Object state)
at Tizen.Applications.TizenSynchronizationContext.<>c__DisplayClass1_0.<Post>b__0()
at Tizen.Applications.TizenSynchronizationContext.GSourceManager.Handler(IntPtr userData)
at Tizen.Applications.CoreBackend.UICoreBackend.Run(String[] args)
at Tizen.Applications.CoreApplication.Run(String[] args)
at Tizen.Applications.CoreUIApplication.Run(String[] args)
at Todo.Tizen.Program.Main(String[] args) in ...
Can you please help me to solve it?
Regards

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

ID: bdcea465-138a-d586-5297-dc93370826b3
Version Independent ID: a41a6f67-0675-036f-0781-13b9165d3848
Content: Xamarin.Forms Local Databases - Xamarin
Content Source: docs/xamarin-forms/data-cloud/data/databases.md
Product: xamarin
Technology: xamarin-forms
GitHub Login: @profexorgeek
Microsoft Alias: jusjohns

Hi @hadihashem
Looks like you need to add the SQLite NuGet package to your Tizen project.

Hi @davidbritch
Sorry but this did not fix the problem
A TypeInitializationException is still showing
Please advise
Regards
System.TypeInitializationException: The type initializer for 'SQLite.SQLiteConnection' threw an exception.
 ---> System.Exception: This is the 'bait'.  You probably need to add one of the SQLitePCLRaw.bundle_* nuget packages to your platform project.
   at SQLitePCL.Batteries_V2.Init()
   at SQLite.SQLiteConnection..cctor()
   --- End of inner exception stack trace ---
   at SQLite.SQLiteConnection..ctor(SQLiteConnectionString connectionString)
   at SQLite.SQLiteConnectionWithLock..ctor(SQLiteConnectionString connectionString)
   at SQLite.SQLiteConnectionPool.Entry.Connect()
   at SQLite.SQLiteConnectionPool.GetConnection(SQLiteConnectionString connectionString)
   at SQLite.SQLiteAsyncConnection.GetConnection()
   at SQLite.SQLiteAsyncConnection.get_TableMappings()
   at Todo.TodoItemDatabase.InitializeAsync()
   at Todo.TaskExtensions.SafeFireAndForget(Task task, Boolean returnToCallingContext, Action`1 onException)
   at System.Threading.Tasks.Task.<>c.<ThrowAsync>b__139_0(Object state)
   at Tizen.Applications.TizenSynchronizationContext.<>c__DisplayClass1_0.<Post>b__0()
   at Tizen.Applications.TizenSynchronizationContext.GSourceManager.Handler(IntPtr userData)
   at Tizen.Applications.CoreBackend.UICoreBackend.Run(String[] args)
   at Tizen.Applications.CoreApplication.Run(String[] args)
   at Tizen.Applications.CoreUIApplication.Run(String[] args)
   at Todo.Tizen.Program.Main(String[] args) in ...

Hi @hadihashem
As the error suggests, you need to add one of the SQLitePCLRaw.bundle_* nuget packages to your platform project.

Hi @davidbritch
I'm afraid after adding the mentionned package, the App will simply crash without any exception or error message
Please see example attached
Regards
Todo.zip

Hi @hadihashem
This is something you'll have to take up with Samsung, who develop the Tizen platform. See https://docs.microsoft.com/xamarin/xamarin-forms/platform/other/tizen for more info.


Draft: Multi vector: Enable the option to configure multi target vectors

Add the capability to configure the class with multiple target vectors and run queries towards them.

Looking into this do you think we could separate this into a named vectors PR first (which we definitely should add) vs a multi target vectors PR?
For multi target vectors, I'm not sure we should add to the benchmarker like this because it will load identical data into each named vector index named_vector_%d. This risk here is we will not be testing recall properly and ideally should have some datasets with different data.


Google OAuth sign in fails for some users

I noticed the problem on my android phone, and now it seems to be fixed.
Thank you
Godfrey
On Thu, 13 Jan 2022 at 08:03, Tom Smyth @.***> wrote:

—
Reply to this email directly, view it on GitHub
https://github.com/gather-community/gather/issues/904, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AQGU6ECBEAXXMBRDXOPBS4DUV3ZVJANCNFSM5L4IAFDQ
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>


Generate classes

Many thanks for submitting your Pull Request :heart:!
What this PR does / why we need it:
Classes generated from json schema.
Special notes for reviewers:
Additional information (if needed):

very cool. sry for late review. will merge


Rattitude mode for PX4

This PR is similar to #3017 though implemented differently.  It creates a new main state and navigation state called "rattitude" which is similar to OpenPilot's rattitude mode.  It allows multirotor pilots to generate attitude commands when easy on the sticks and rate commands when aggressive on the sticks.
@kd0aij, @AndreasAntener, @psiorx  I would appreciate some help flight testing with this PR as I don't have a pixhawk yet that I am free to use for personal use (only have a CC3D though I hope to change this soon).
This is my first multirotor contribution so I don't have HIL/SITL up and running yet but I did test the switching logic on the bench which you can find here:  http://logs.uaventure.com/view/KcLu9LGovC3Mqd8wVqrwfA
Note the larger pitchrate and rollrate setpoints in second part of graph.  Also the main state transitions to 9 which is RATTITUDE mode.
I will update this PR with HIL/SITL results as I establish my setup and hopefully flight tests ASAP.

Awesome!

@scott-eddy Integration tests failed, could you have a look?

@LorenzMeier it was unhappy with code style too.  Should pass now

@scott-eddy Nice! Adding a new flight mode is certainly a better way to do this. Does this also work for fixed wing platforms? The logfile you reference for the bench test is titled "Fixedwing...", but there's a comment that fixed wing "doesn't need" a Rattitude mode.

Log file was on a multirotor, must have been tired when I uploaded it.
I guess I didn't see the need for it in fixedwing but no reason to limit the capability.  I can add the logic for that too, but it would be nice to get it into master for multirotor soon.

Also this PR needs a sister PR on QGroundControl to add Rattitude into flight mode calibration and main state handeling.

I tested Rattitude mode yesterday and this morning.  Last night everything looked fine on the bench but in the air the copter refused to flip.  I've since updated how mc_att_control handles being in rattitude mode and today was doing all the flips.  Here is the log file: http://logs.uaventure.com/view/fXaUuxEKggjrV7K2EYwt89
I even inverted the copter and then went easy on the sticks to let attitude control resume and no problems.
Not sure what's going on with my GPS, its a new config for me ¯_(ツ)_/¯.

Also I think that the variations in pitch rate were the result of poor tuning, not the mode.  Here is a better tuned log with a few flips in there:
http://logs.uaventure.com/view/SHndB9DA6CfQAjcgkNLeAo

@scott-eddy Just added another comment. I need go get this in soon in lockstep with QGC, so a swift fix + testing would be awesome.

I will test the elseif tonight.  I agree that the implementation is wrong as it seems now if rattitude is configured it will lock you out of switching into ACRO.
I don't follow the rattitude switch not configured problem.  If not configured we want to switch to manual mode correct?
I will post a log tonight hopefully showing the main state switching from Manual/Ratt/Acro once the elseif is implemented

￼A fully updated version of this would make my head not explode when I try to update Flight Mode config:

@DonLakeFlyer, here is the new mode logic with blue representing decisions made in the commander and green representing decisions made by the state machine helper.

Mode switching with Acro/Manual/Rattitude now works as in diagram: http://logs.uaventure.com/view/bUZ9W9wkSkqbmSttDmWTjL
After rebase sitl is not working.

Not sure why rebase broke the checks.  Can look at tomorrow

That's a break on master. Has been reverted and I'm re-running builds.

@DonLakeFlyer @LorenzMeier , I'm fairly new to git so I could use some help on my end here.  Tried fetching/rebasing this morning and still have fails.  Should I checkout and reset to 72c339a and then rebase again?  Or merely wait for Master fixes and fetch/rebase once they come in.
Thanks

Travis is failing internally on something. I'm re-running yet again. If that doesn't work I'll take a really close look and just merge if it all looks good.

Travis is failing because it has submodule changes committed. Revert them to the current state in master.

Woot! @LorenzMeier I think this is good to go.

Awesomeness! @DonLakeFlyer In master, so good to go from the QGC perspective.

Finally getting to QGC side of this. If you look at Flight Mode ui you'll see there is a user friendly name for the mode as well as a text desctiption for what the mode is:

Can someone give me those two things for QGC and I'll implement the new mode.

Title: Rattitude
Description: Combination of Attitude and Rate control: Stick near center operates like attitude stabilization mode. Stick at the edges of its range operates like rate control mode.

Description: Combination of Attitude and Rate control: Stick near center
operates in attitude stabilization mode. Stick above threshold (MC_RATT_TH)
operates in rate control mode.
On Sat, Dec 12, 2015 at 12:07 AM Lorenz Meier<EMAIL_ADDRESS>wrote:

Title: Rattitude
Description: Combination of Attitude and Rate control: Stick near center
operates like attitude stabilization mode. Stick at the edges of its range
operates like rate control mode.
—
Reply to this email directly or view it on GitHub
https://github.com/PX4/Firmware/pull/3038#issuecomment-164116521.

Awesome, thanks.


Alter login attempts

add column login_attempts.system_event_id and change code to accommodate.

Instead, removing login_attempts table and entity and incorporating into events.


Skeleton2D Modifications Throw Error and Warnings stating that bone index needs to be updated

Godot version
v4.0.rc1.mono.official [8843d9ad3]
System information
Windows 10, Nvidia RTX 2080
Issue description
I am using the Skeleton2D node with the modification stack to add IK bones but they seem to throw errors telling me that the target cache is out of date. But it seems that I cannot do anything against this issue since I don't have any control over the bone index or cache.
Another issue is that the errors still get thrown even when I set the enabled flag of the ModificationStack to false.
Here is the error log of the reproduction project:

Steps to reproduce
Open provided project and start scene with F6. Debugger logs a lot of warnings and errors.
Minimal reproduction project
BugreportIK.zip

Same issue.

Getting presumably the same errors for Fabrik IK setup in Godot 4.1.1

I'm also seeing this issue. Has anyone found any workarounds?

Anyone knows what caused this? I know it used to work up to some version, so maybe we could find the PR that introduced this?

Yeah that would be a good idea to see what caused this but it could also be a side effect of some other change?

For me it also outputs "!is_inside_scene_tree is true" and disables the modifications completely. I have to remove and readd all the skeleton mods from scratch every time I start the engine. Very annoying, hope it is fixed soon.

I had a bit of free time and tried to test the MRP with older Godot versions. The oldest Godot 4 build that was able to open the project was v4.0.alpha4.official [f47097973] (before that it was unable to load the MRP saying it was corrupted). Even in that build, I had the same errors as the ones described in the issue.
This leads me to believe the issue appeared in the transition from Godot 3 to Godot 4. I know this is not very informative since a lot of things changed between those versions, but it's where we should look into from now.

So, the issue is still there in Godot 4.1. Are there any fixes for that?

Can you rest in 4.2-beta3?

Can you rest in 4.2-beta3?

Just tested in 4.2 b3 - the bug is still there.

Can you rest in 4.2-beta3?

Did a quick test and I get the same errors on a small test project

(Was wondering for a second if perhaps it had something to do with projects being ported over from 3.x, but this is a fresh project so no)

I am also experiencing this as well, and noticed it occur after reordering the bones inside a skeleton.

Still ongoing.

Still Ongoing.

I'm new to the Godot source, but I tried to do some deep diving. I hope this is helpful for someone who might know a bit more.
Got a stack trace from gdb for 4.2-stable from break scene/resources/skeleton_modification_2d_twoboneik.cpp:253 by runnint run -e --path ~/workspace/<my-project-path>.
It looks like some sort of initialization order which causes noisy warnings because everything seems to work afterwards as others have found. I'm to new to see if there's any initialization bug or if it's just a missing check in set_target_node to see if the object is setup before calling update_target_cache. But this wouldn't fix all the warnings I see like ones that call here: https://github.com/godotengine/godot/blob/master/scene/resources/skeleton_modification_2d_twoboneik.cpp#L42.
The common root cause seems to be that _setup_modification is not called sooner on all the modifications, but I'm not sure how to make that change.
Stack trace:
#0  SkeletonModification2DTwoBoneIK::update_target_cache (this=0x555574122230)
    at scene/resources/skeleton_modification_2d_twoboneik.cpp:253
253			ERR_PRINT_ONCE("Cannot update target cache: modification is not properly setup!");
(gdb) f 1
#1  0x000055555b1cf1fe in SkeletonModification2DTwoBoneIK::set_target_node (this=0x555574122230, p_target_node=...)
    at scene/resources/skeleton_modification_2d_twoboneik.cpp:330
330		update_target_cache();
(gdb) backtrace
#0  SkeletonModification2DTwoBoneIK::update_target_cache (this=0x555574122230)
    at scene/resources/skeleton_modification_2d_twoboneik.cpp:253
#1  0x000055555b1cf1fe in SkeletonModification2DTwoBoneIK::set_target_node (this=0x555574122230, p_target_node=...)
    at scene/resources/skeleton_modification_2d_twoboneik.cpp:330
#2  0x0000555558272de8 in call_with_variant_args_helper<__UnexistingClass, NodePath const&, 0ul> (p_instance=0x555574122230,

    p_method=(void (__UnexistingClass::*)(__UnexistingClass * const, const NodePath &)) 0x55555b1cf1c4 <SkeletonModification2DTwoBoneIK::set_target_node(NodePath const&)>, p_args=0x7fffffffa3a0, r_error=...) at ./core/variant/binder_common.h:303
#3  0x000055555826e73b in call_with_variant_args_dv<__UnexistingClass, NodePath const&> (p_instance=0x555574122230,
    p_method=(void (__UnexistingClass::*)(__UnexistingClass * const, const NodePath &)) 0x55555b1cf1c4 <SkeletonModification2DTwoBoneIK::set_target_node(NodePath const&)>, p_args=0x7fffffffa470, p_argcount=1, r_error=..., default_values=...)
    at ./core/variant/binder_common.h:450
#4  0x000055555826a9e4 in MethodBindT<NodePath const&>::call (this=0x5555646afed0, p_object=0x555574122230,
    p_args=0x7fffffffa470, p_arg_count=1, r_error=...) at ./core/object/method_bind.h:335
#5  0x000055555c65a7b2 in ClassDB::set_property (p_object=0x555574122230, p_property=..., p_value=..., r_valid=0x0)
    at core/object/class_db.cpp:1235
#6  0x000055555c672097 in Object::set (this=0x555574122230, p_name=..., p_value=..., r_valid=0x0) at core/object/object.cpp:257
#7  0x000055555b175a9a in ResourceLoaderText::load (this=0x7fffffffa740) at scene/resources/resource_format_text.cpp:628
#8  0x000055555b1802fc in ResourceFormatLoaderText::load (this=0x5555627c2430, p_path=..., p_original_path=...,
    r_error=0x55557d352fac, p_use_sub_threads=false, r_progress=0x55557d352fa0,
    p_cache_mode=ResourceFormatLoader::CACHE_MODE_REPLACE) at scene/resources/resource_format_text.cpp:1653
#9  0x000055555c22335d in ResourceLoader::_load (p_path=..., p_original_path=..., p_type_hint=...,
    p_cache_mode=ResourceFormatLoader::CACHE_MODE_REPLACE, r_error=0x55557d352fac, p_use_sub_threads=false,
    r_progress=0x55557d352fa0) at core/io/resource_loader.cpp:261
#10 0x000055555c223acf in ResourceLoader::_thread_load_function (p_userdata=0x55557d352f58) at core/io/resource_loader.cpp:319
#11 0x000055555c2248eb in ResourceLoader::_load_start (p_path=..., p_type_hint=...,
    p_thread_mode=ResourceLoader::LOAD_THREAD_FROM_CURRENT, p_cache_mode=ResourceFormatLoader::CACHE_MODE_REPLACE)
    at core/io/resource_loader.cpp:500
#12 0x000055555c22432e in ResourceLoader::load (p_path=..., p_type_hint=...,
    p_cache_mode=ResourceFormatLoader::CACHE_MODE_REPLACE, r_error=0x7fffffffccb8) at core/io/resource_loader.cpp:417
#13 0x0000555559383e0a in EditorNode::load_scene (this=0x555564eff2c0, p_scene=..., p_ignore_broken_deps=false,
    p_set_inherited=false, p_clear_errors=true, p_force_open_imported=false, p_silent_change_tab=false)
    at editor/editor_node.cpp:3789
#14 0x0000555559391063 in EditorNode::_load_open_scenes_from_config (this=0x555564eff2c0, p_layout=...)
    at editor/editor_node.cpp:5499
#15 0x000055555938df55 in EditorNode::_load_editor_layout (this=0x555564eff2c0) at editor/editor_node.cpp:5123
#16 0x000055555936e444 in EditorNode::_sources_changed (this=0x555564eff2c0, p_exist=false) at editor/editor_node.cpp:1050
#17 0x00005555593e388a in call_with_variant_args_helper<EditorNode, bool, 0ul> (p_instance=0x555564eff2c0, p_method=(void (EditorNode::*)(EditorNode * const, bool)) 0x55555936e394 <EditorNode::_sources_changed(bool)>, p_args=0x7fffffffd370, r_error=...) at ./core/variant/binder_common.h:303
#18 0x00005555593e2525 in call_with_variant_args<EditorNode, bool> (p_instance=0x555564eff2c0, p_method=(void (EditorNode::*)(EditorNode * const, bool)) 0x55555936e394 <EditorNode::_sources_changed(bool)>, p_args=0x7fffffffd370, p_argcount=1, r_error=...) at ./core/variant/binder_common.h:417
#19 0x00005555593dd8f6 in CallableCustomMethodPointer<EditorNode, bool>::call (this=0x5555740c7b20, p_arguments=0x7fffffffd370, p_argcount=1, r_return_value=..., r_call_error=...) at ./core/object/callable_method_pointer.h:98
#20 0x000055555c2e4fc8 in Callable::callp (this=0x55557d0fbf00, p_arguments=0x7fffffffd370, p_argcount=1, r_return_value=..., r_call_error=...) at core/variant/callable.cpp:57
#21 0x000055555c67623a in Object::emit_signalp (this=0x555564f561d0, p_name=..., p_args=0x7fffffffd370, p_argcount=1) at core/object/object.cpp:1127
#22 0x000055555a3fc3ad in Node::emit_signalp (this=0x555564f561d0, p_name=..., p_args=0x7fffffffd370, p_argcount=1) at scene/main/node.cpp:3606
#23 0x00005555589e1577 in Object::emit_signal<bool> (this=0x555564f561d0, p_name=...) at ./core/object/object.h:922
#24 0x0000555559296471 in EditorFileSystem::_notification (this=0x555564f561d0, p_what=17) at editor/editor_file_system.cpp:1285
#25 0x00005555592a4410 in EditorFileSystem::_notificationv (this=0x555564f561d0, p_notification=17, p_reversed=false) at editor/editor_file_system.h:146
#26 0x000055555c674454 in Object::notification (this=0x555564f561d0, p_notification=17, p_reversed=false) at core/object/object.cpp:837
#27 0x000055555a428bdf in SceneTree::_process_group (this=0x555564e8faf0, p_group=0x555564e8fd48, p_physics=false) at scene/main/scene_tree.cpp:951
#28 0x000055555a42911d in SceneTree::_process (this=0x555564e8faf0, p_physics=false) at scene/main/scene_tree.cpp:1028
#29 0x000055555a426eec in SceneTree::process (this=0x555564e8faf0, p_time=0.1166666666666667) at scene/main/scene_tree.cpp:508
#30 0x00005555580362b3 in Main::iteration () at main/main.cpp:3636
#31 0x0000555557fa412e in OS_LinuxBSD::run (this=0x7fffffffd790) at platform/linuxbsd/os_linuxbsd.cpp:933
#32 0x0000555557f9c2a8 in main (argc=4, argv=0x7fffffffdd58) at platform/linuxbsd/godot_linuxbsd.cpp:74

I was still working in 4.1.3stable, and decided to try switching to 4.2 today. However, when opening my player character, it now gets fully locked up and I cannot move anything in the skeleton. It's as though there's another skeletonmodification than the one I see still active or something, forcing it to always return to a certain, scrunched up state.
I'm wondering if all of these problems have something to do with trying out several configurations of skeletonmodification, and deleting them but some kind of trace remaining, because even if I just plain delete the current skeletonmodificationstack2D, the whole skeleton remains scrunched up.
When starting up the game, I get these errors now.

Looking at C++ code in scene/2d/skeleton_2d.cpp, around line 435, there is a function, Bone2D::calculate_length_and_rotation, that is the one that prints the bug.
Why that function is called?
Do see the inspector when you click on a Bone2D, there is a flag, "auto calculate length and angle":

Few things:
1- It seems there is no documentation for this flag.
2- If you uncheck it, the warning will not appear.
3- The values requested don't have description either. I can imagine what they are asking for, but not knowing the units does not help.

Interesting. That computes length and angle based on children nodes. Its possible that those nodes arent fully loaded yet, and that is why the warning is thrown? Maybe that calculation should happen in another place, if at all, since its already calculated in editor time, why it needs again at start of runtime.

The calculate_length_and_rotation is called from
		case NOTIFICATION_READY: {
			if (autocalculate_length_and_angle) {
				calculate_length_and_rotation();
			}
		} break;

and also from set_autocalculate_length_and_angle which is called as a setter it feels like from editor or from api layer.
So my thoughts on this is if someone calls this method, set_autocalculate_length_and_angle, it will call `calculate_length_and_rotation which will get the children nodes and update the bone length and angle.
Why this function is called? It's called to update the bone length and angle based on children. What happens is sometimes you have a child bone that is the last one that doesnt have any children of it's own. In that case, it cannot compute length and angle so it's using the transform instead. Is that a bug tho? So if setting all your last bone nodes with autocalculate false, you won't get the warning anymore.
I would propose that the warning isn't thrown at all, since if you don't have children nodes, it doesn't compute length and angle but instead puts a default one, that isn't a warning state or error state(it could be a node warning, but probably not) since there are and there will be nodes that have no children and just exist as last nodes. I think having them there is normal, many people use it as a sort of indication or place to move the higher bones. Having a warning for this isn't really bringing much value.
That is however just one warning.

Another warning/error is with the bone index.
This is called from: scene/resources/skeleton_modification_2d_lookat.cpp from set_bone_index
This function seems to do look if the stack has a skeleton member or if is_setup && the stack isn't null, eg:
stack->skeleton
if not throws warning.

The is_setup becomes true in the _setup_modification function. This is called from the setup function on the scene/resources/skeleton_modification_stack_2d.cpp.
So if called from there, the is_setup is made true before getting called.
However another problem could be that stack->skeleton is null for any reason. This is set in the set_skeleton function of the scene/resources/skeleton_modification_stack_2d.cpp. So it could very well be an issue with the setter not getting called when it should?
I'll try attack a debugger and see the order of how they are called and what might cause it.

Indeed, the _setup_modification function is called later. Thats the issue. So what happens is there are multiple functions like:
PhysicalBone2D::set_bone2d_index
SkeletonModification2DCCDIK::set_ccdik_joint_bone_index
SkeletonModification2DFABRIK::set_fabrik_joint_bone_index
SkeletonModification2DJiggle::set_jiggle_joint_bone_index
SkeletonModification2DLookAt::set_bone_index
SkeletonModification2DTwoBoneIK::set_joint_one_bone_idx

(The naming on these, uh)
These functions are called before the setup started, so the is_setup is false. However it still makes a note of this index, in all of these functions the implementation does:
if(is_setup) {
joint_bone_idx = p_bone_idx;
joint_bone2d_node_cache = ..
joint_bone2d_node = ..
} else {
joint_bone_idx = p_bone_idx;
}

So it really doesn't set the cache from the skeleton. (Now, should it? Should the even be called in some other order, I don't know)
Ok, afterwards, when the setup is called, it will do an update on the cache:
W 0:00:00:0545   _execute: Target cache is out of date. Attempting to update...
  <C++ Source>   scene/resources/skeleton_modification_2d_lookat.cpp:119 @ _execute()

If you look at the log where that is called, it's basically calling:
update_target_cache

Which in turn does what the initial function should have done.
So, to me this seems like what happens is the bone isn't setup yet when the setter is called, but no problem, because it is caching the index and restoring the node_cache later. Again these shouldn't really be warnings even, not sure though. Will try to investigate more and see if I can have a fix, but then we will need someone to review the fix and understand why that would be the fix.

If anyone can try test, I implemented what I spoke about earlier here: https://github.com/godotengine/godot/pull/89387
Not sure if it catches all cases though. Some dissapeared and it makes sense to remove those warnings, as I wrote above. There is still some of these:
Cannot update Bone2D cache: modification is not properly setup!

Seems to be related to calls of update_node_cache when the setup is not started(or stack is null, more rare). I would say it could be because of the set_bone2d_node method that sets the bone_node but probably the setup phase isn't started yet again. In that case it's probably ok as well to do no op instead of erroring. Investigating all use cases to see i am not missing anything, but it seems in a lot of cases not erroring should be fine, as its not an error case, it's a normal use case(eg setting a value and not computing cache until execute is called).

Seems in these cases in the setter we don't want to update if the is_setup is not true. This way the error is not thrown at startup. I'll give it a try see if all errors dissapear.

Ok, tested locally (in the PR i linked) and i have 0 warnings and 0 errors. Things work well, I worked out through all warnings and errors and they were indeed not warnings or errors, in the sense that it was not an error case happening.

I tried your build, and I'm still getting a ton of errors when loading in my project:
scene\2d\skeleton_2d.cpp:620 - Condition "!is_inside_tree()" is true. Returning: 0
scene\2d\skeleton_2d.cpp:620 - Condition "!is_inside_tree()" is true. Returning: 0
Passed-in Bone index is out of range!
scene\2d\skeleton_2d.cpp:620 - Condition "!is_inside_tree()" is true. Returning: 0
scene\2d\skeleton_2d.cpp:620 - Condition "!is_inside_tree()" is true. Returning: 0
Passed-in Bone index is out of range!
scene\2d\skeleton_2d.cpp:620 - Condition "!is_inside_tree()" is true. Returning: 0
scene\2d\skeleton_2d.cpp:620 - Condition "!is_inside_tree()" is true. Returning: 0
Passed-in Bone index is out of range!
scene\2d\skeleton_2d.cpp:620 - Condition "!is_inside_tree()" is true. Returning: 0
scene\2d\skeleton_2d.cpp:620 - Condition "!is_inside_tree()" is true. Returning: 0
Passed-in Bone index is out of range!
scene\2d\skeleton_2d.cpp:620 - Condition "!is_inside_tree()" is true. Returning: 0
scene\2d\skeleton_2d.cpp:620 - Condition "!is_inside_tree()" is true. Returning: 0
Passed-in Bone index is out of range!
scene\2d\skeleton_2d.cpp:620 - Condition "!is_inside_tree()" is true. Returning: 0
scene\2d\skeleton_2d.cpp:620 - Condition "!is_inside_tree()" is true. Returning: 0
Passed-in Bone index is out of range!
scene\2d\skeleton_2d.cpp:620 - Condition "!is_inside_tree()" is true. Returning: 0
scene\2d\skeleton_2d.cpp:620 - Condition "!is_inside_tree()" is true. Returning: 0
Passed-in Bone index is out of range!
scene\2d\skeleton_2d.cpp:620 - Condition "!is_inside_tree()" is true. Returning: 0
scene\2d\skeleton_2d.cpp:620 - Condition "!is_inside_tree()" is true. Returning: 0
Passed-in Bone index is out of range!
scene\2d\skeleton_2d.cpp:620 - Condition "!is_inside_tree()" is true. Returning: 0
scene\2d\skeleton_2d.cpp:620 - Condition "!is_inside_tree()" is true. Returning: 0
Passed-in Bone index is out of range!
scene\2d\skeleton_2d.cpp:630 - Condition "!is_inside_tree()" is true. Returning: nullptr
scene\2d\skeleton_2d.cpp:630 - Condition "!is_inside_tree()" is true. Returning: nullptr
scene\2d\skeleton_2d.cpp:630 - Condition "!is_inside_tree()" is true. Returning: nullptr
scene\2d\skeleton_2d.cpp:630 - Condition "!is_inside_tree()" is true. Returning: nullptr
scene\2d\skeleton_2d.cpp:630 - Condition "!is_inside_tree()" is true. Returning: nullptr
scene\resources\2d\skeleton\skeleton_modification_2d_twoboneik.cpp:113 - Target cache is out of date. Attempting to update...
scene\resources\2d\skeleton\skeleton_modification_2d_twoboneik.cpp:119 - Joint one Bone2D node cache is out of date. Attempting to update...
scene\resources\2d\skeleton\skeleton_modification_2d_twoboneik.cpp:123 - Joint two Bone2D node cache is out of date. Attempting to update...
although I will admit I am new to compiling the engine so maybe I did something wrong

Can you out a test project i can verify with? Thanks.

Can you out a test project i can verify with? Thanks.

emailed it to the email on your profile


No project-colors for the project since V8 changes

Hi,
since the newest changes fpr API V8 the project colors are not visible anymore.
Could you please check that?
Best regards
Maurice

After installing this module, I noticed this too. Doing a bit of reading, it seems Todoist have changed the ID of colours from 0-21 to 30-49.
I had a look through the module's files, and in MMM-Todoist.js found this;
	projectColors: ["#95ef63", "#ff8581", "#ffc471", "#f9ec75", "#a8c8e4", "#d2b8a3", "#e2a8e4", "#cccccc", "#fb886e",
		"#ffcc00", "#74e8d3", "#3bd5fb", "#dc4fad", "#ac193d", "#d24726", "#82ba00", "#03b3b2", "#008299",
		"#5db2ff", "#0072c6", "#000000", "#777777"
	], //These colors come from Todoist and their order matters if you want the colors to match your Todoist project colors.

Guessing that this is where the colours are looked up from the colour ID returned from Todoist,  I amended this to:
	projectColors: ["","","","","","","","","","","","","","","","","","","","",
		"", "", "", "", "", "", "", "", "", "",
		"#b8256f", "#db4035", "#ff9933", "#fad000", "#afb83b", "#7ecc49", "#299438", "#6accbc", "#158fad",
		"#14aaf5", "#96c3eb", "#4073ff", "#884dff", "#af38eb", "#eb96eb", "#e05194", "#ff8d85", "#808080",
		"#b8b8b8", "#ccac93", "#000000", "#777777"
	], //These colors come from Todoist and their order matters if you want the colors to match your Todoist project colors.

and it seems to work for me.

Thats funny because 1 hour ago I also checked the v7 and v8 documentation again. You're right.

Can you make the update and submit a pull request? Thanks!


Microsoft.Portal definition a bit misleading says "for the subscription"

Hi,
As per subject , these permissions can also be granted at Resource Group level, assume this is supported ? ie where you don't want to grant perms to whole subscription.
cheers
Andy.

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

ID: 33219707-3b9f-cc6b-541e-a806dc82622a
Version Independent ID: b4e96391-bcf9-1f30-cb44-ed339469da4f
Content: Azure Resource Manager resource provider operations
Content Source: articles/role-based-access-control/resource-provider-operations.md
Service: role-based-access-control
GitHub Login: @rolyon
Microsoft Alias: rolyon

@andyjballgit Thanks for your comment. The feedback has been shared with the content owner for further review. Thanks for your patience.

Hi @andyjballgit
I'll see what I can find out about this.


No tag on docker image for scality/s3server

Hello !
For the moment we use your docker image in our deployment, mostly because it's easier to upgrade.
But as there isn't any tag on hub.docker.com, we can't know for sure what version we are using, and we can't easily install the same version on several servers.
Do you think you can add some during your next release on docker hub ?
Sorry if this issue is misplaced.
Best regards,

Hey @Tiduster ,
We are discussing about that.
Will come back to you soon.

Hey @Tiduster ,
We started versioning our Docker image using our git commit hashes.
Check it out: https://hub.docker.com/r/scality/s3server/

Hey @nicolas2bert ,
Thanks for the quick reaction, commit hashes is a good idea, and it solve my issue.
May I ask for a stable tag too ? :-)
And it will be perfect.
Best regards,


PLY vertex size mismatch,expected 248 but file has 236

Is the file coming from scaniverse by chance? If so, then it's the same issue as #108, closing this one as duplicate.


Canvas pattern

http://www.patternfly.org/angular-patternfly/#/api/patternfly.canvas.directive:pfCanvas
http://www.patternfly.org/angular-patternfly/#/api/patternfly.canvas.directive:pfCanvasEditor
View and edit modes

Closing due to inactivity.


add uuid for capability and talent

Description
use uuid4 to generate id for talent and capability as one of fields in the json
Fixes #(add issue number here and remove parentheses)
Review Time Estimate
Please give your idea of how soon this pull request needs to be reviewed by selecting one of the options below. This can be based on the criticality of the issue at hand and/or other relevant factors.

[ ] Immediately
[ ] Within a week
[x] When possible

Type of changes
Please select a relevant option:

[ ] Bug fix (non-breaking change which fixes an issue).
[ ] New feature (non-breaking change which adds functionality).
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected).
[ ] Other (any another change that does not fall in one of the above categories.)

Checklist:
Please select all applicable options:

[ ] I have signed the Rokwire Contributor License Agreement (CLA). (Any contributor who is not an employee of the University of Illinois whose official duties include contributing to the Rokwire software, or who is not paid by the Rokwire project, needs to sign the CLA before their contribution can be accepted.)
[ ] I have updated the CHANGELOG.
[ ] I have read the Contributor Guidelines.
[ ] I have performed a self-review of my own code.
[ ] I have commented my code, particularly in hard-to-understand areas.
[ ] My change requires updating the documentation.
[ ] I have made necessary changes to the documentation.
[ ] I have added tests related to my changes.
[ ] My changes generate no new warnings.
[ ] New and existing unit tests pass locally with my changes.
[ ] Any dependent changes have been merged and published in downstream modules.

@wenjzhu, please update the CHANGELOG. Thanks.

The generation of Capability and Talent IDs looks fine. Please update the CHANGELOG, and I think we can merge this PR after that. Obviously, this needs to be later tested along with the backend changes. Thanks.

The generation of Capability and Talent IDs looks fine. Please update the CHANGELOG, and I think we can merge this PR after that. Obviously, this needs to be later tested along with the backend changes. Thanks.

I just updated

Thanks, @wenjzhu. Please resolve the merge conflict too.

Thanks, @wenjzhu. Please resolve the merge conflict too.

I fixed it

Thanks for the updates, @wenjzhu. I will merge this now. We still need to test this along with the backend changes.


Vernemq crashes out more or less  on every 7 days

Environment

VerneMQ Version: 1.3.0
OS: ubuntu 16.04
Erlang/OTP version (if building from source): Using  binary to install
Issue :
Vernemq crashes after a running for a week time.I'm constituently  facing this issue.
I have 20 active connections( shared subscription with Qos1), with web-hook authentication. I have attached the error logs and my configuration for your reference.

[###]
vernemq issue log
vernemq_conf.txt

Hi,
Could you share the erl_crash.dump file. Also, what's the memory load on the server when this happens?

@tamilhce I suspect the leveldb.maximum_memory.percent = 70 default setting could be the problem here, especially if it's a smaller server. I'd set this to something much lower and observe what happens (to 15 or 20%).
Also, look at the findings here for more insights into stabilizing LevelDB memory usage:
https://github.com/erlio/vernemq/issues/591

@ioolkos sure, I am using aws t2.mirco(1 GB RAM, 1 VCPU), seems like  a memory issue.
is there any way i can check the LevelDB  usage percentage at real-time.
@larshesel  erl_crash.dump  has 656 MB  of data.

@tamilhce can you post the first 100 lines of the crash dump - it usually is enough to tell if it the VM terminated due to an OOM issue.

Hi @larshesel  attached t last 200 lines of the crash dump
vernemq_erl_crash.log

Hi,
I meant the first 100 lines :)

I have attached first 100 lines :)
vernemq_erl_crash.log

Hi,
Based on the high memory usage and this reply on the Erlang mailing list: http://erlang.org/pipermail/erlang-questions/2017-February/091721.html I'd guess it's the Linux OOM killer which terminates VerneMQ.
I'd try to set the setting described in the thread @ioolkos linked earlier to limit the resources leveldb can use and see if that helps.

thanks for quick reply


Adding "file"-attribute to "testcase"-tag in JUnit format

This PR adds a "file" attribute to the "testcase" tags in the JUnit output format. This is e.g. necessary when trying to parallelize testruns on CircleCI that can split tests automatically by timing data.
Example of output:
<?xml version="1.0" encoding="UTF-8"?>
<testsuites name="default">
    <testsuite name="World consistency" tests="1" skipped="0" failures="1" errors="0" time="-IGNORE-VALUE-">
        <testcase name="Failed" classname="World consistency" file="features/World.feature" status="failed" time="-IGNORE-VALUE-">
            <failure message="Given I have entered 10: failure (Exception)" type="teardown"></failure>
        </testcase>
    </testsuite>
</testsuites>

I fixed the test failure in #1336, perhaps you could review that? Then once it’s merged you can rebase this PR

I fixed the test failure in #1336, perhaps you could review that? Then once it’s merged you can rebase this PR

done :+1:

@ciaranmcnulty I need to take a look at appveyor too. The tests that are passing on Github Actions, are not yet passing on appveyor. I have no experience with that tool yet.

It may be easier to get windows builds on GA

@ciaranmcnulty Found it:
file="features/World.feature" on GitHub
vs.
file="features\World.feature" on AppVeyor
I'm using the DIRECTORY_SEPARATOR constant (like it is used in other parts of the code). But it seems that AppVeyor is running on operating systems using Backslashes as separators...
Should I use simple slashes ("/") as separators instead?

@ciaranmcnulty In any case, I'll close this PR and open a fresh one after having rebased your merge. I already tinkered around too much in this one.

Yes Appveyor is there to test Windows

@ciaranmcnulty To make this work, the only way I currently see is to duplicate the concerned Scenarios, adapt them to their respective operating system and to exclude them via tags in the builds where they don't belong.
Something like this:
behat --tags="~@windows-only" (on GA)
behat --tags="~@unix-only" (on AV)

Would that be acceptable?

I'm not a Windows user, but it may be fine to make it / in the report - a lot of apps seem to cope ok with forward slashes.
We could also 'fix' it in FeatureContext:: fileXmlShouldBeLike - there's already some manipulation there to remove timestamps

@ciaranmcnulty Yes, I was currently examining this option too. Using some sort of Placeholder for the Directory Separator should do the trick here. I'll get back to you with a fresh PR in the next couple of hours, having a fix for this.
Thanks :+1:

I guess what it comes down to is not which OS you're running on, but which directory separator is appropriate in the XML format; i.e. which separators JUnit tools will work best with. My assumption is that / everywhere makes the most sense

closed in favor of #1337


abapGit source: One include for each object type

Where possible, add folder?, Will help keeping track of history
split
https://github.com/larshp/abapGit/blob/master/src/zabapgit_object.prog.abap
into multiple
zabapgit_object_++++.prog.abap includes
perhaps create a folder
https://github.com/larshp/abapGit/blob/master/src/objects/ to store the new files

Also adding folder per object type for serialized data would be great (may be optional via some settings)

I meant to refer to the abapGit source code, I've updated the description and title, sorry about the confusion.
I guess the above refers to projects using abapGit. Currently subpackages will create extra folders, eg. in https://github.com/larshp/abapGitServer/tree/master/src/ddic there is an subpackage which contains the DDIC objects. It might be a good idea to automatically create directories for TADIR-OBJECT types. @sbcgua can you raise this as a separate issue?


MWPW-161240 Add CSP script source

Resolves: MWPW-161240

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 84.69%. Comparing base (1cdc3e2) to head (ce777e7).

Additional details and impacted files
@@           Coverage Diff           @@
##            stage     #902   +/-   ##
=======================================
  Coverage   84.68%   84.69%
=======================================
  Files          48       48
  Lines        6170     6173    +3
=======================================
+ Hits         5225     5228    +3
  Misses        945      945

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

🚨 Try these New Features:

Flaky Tests Detection - Detect and resolve failed and flaky tests
JS Bundle Analysis - Avoid shipping oversized bundles


Make the website responsive

It might be better to consider this as a milestone since there's a lot of moving components involved. These are the following that I think need to be considered:

Make sure all of the elements that require no interaction at all are responsive to the changing viewports. This could be done by manually changing font, div sizes, or whatnot for different @media params
The trickier part of this is the interactive components. Currently, the canvases are operating on 500 pixels x 500 pixels. There should be a way to make the canvases change its whole game engine on the given viewport size

Helpful
http://stackoverflow.com/questions/23445907/jquery-to-make-html5-canvas-responsive

We'll see how well the OOP migration fixed this when levels 2 and 3 are re-coded in the new framework.


Update broken link to physics engines tutorial

🦟 Bug fix
Fixes #
Summary
Fix broken link in physics engine tutorial MD.
Checklist

[x] Signed all commits for DCO
[x] Added tests
[x] Updated documentation (as needed)
[ ] Updated migration guide (as needed)
[x] Consider updating Python bindings (if the library has them)
[x] codecheck passed (See contributing)
[x] All tests passed (See test coverage)
[x] While waiting for a review on your PR, please help review another open pull request to support the maintainers

Note to maintainers: Remember to use Squash-Merge and edit the commit message to match the pull request summary while retaining Signed-off-by messages.

Superceeded by https://github.com/gazebosim/gz-physics/pull/708


xcodebuild fail if 8081 in use

I'm on a Yosemite box and got this failure:
$ natal init FutureApp
Creating FutureApp

Creating Leiningen project
Updating Leiningen project
Compiling ClojureScript
Creating React Native skeleton
Installing Pod dependencies
Updating Xcode project
Creating Natal config
Compiling Xcode project
Command failed: xcodebuild -workspace native/ios/FutureApp.xcworkspace -scheme FutureApp -destination platform='iOS Simulator',OS=latest,id='AB511846-7E27-4434-9714-84DBCC8B5256' test

Digging into this, I can see that the root cause is that port 8081 is already in use on my box, which the React Native Packager wants to use.
Logging an issue in case there is anything Natal can do to soften this particular failure mode (or maybe even avoid it if React can be told to use some other port).

Good catch.
For now I added a warning if 8081 is in use by anything besides the React Native packager. In the future we could add a CLI option to change the packager port.

Perfect! Confirmed with master:
$ ./index.js init SomeAppName
Port 8081 is currently in use by another process and is needed by the React Native packager.


Log Spam: Loading FXML / CSS

Loading FXML document with JavaFX API of version 11.0.1 by JavaFX runtime of version 10.0.2
Could not resolve '-fx-text-base-color' while resolving lookups for '-fx-text-fill' from rule '*.label' in stylesheet /build/resources/main/theme/style.css
Caught 'java.lang.ClassCastException: java.base/java.lang.String cannot be cast to<EMAIL_ADDRESS>while converting value for '-fx-effect' from rule '*.card' in stylesheet /build/resources/main/theme/style.css
Caught 'java.lang.ClassCastException: java.base/java.lang.String cannot be cast to<EMAIL_ADDRESS>while converting value for '-fx-background-color' from rule '*.card' in stylesheet /build/resources/main/theme/style.css

See also: #1384

I addressed this in one PR lemme think ... PR #1415

Cannot reproduce CSS errors on PR #1415


README: Clarify podRestartThreshold applying to the sum over containers

calcContainerRestarts sums over containers.  The new language makes that clear, avoiding potential confusion vs. an altenative that looked for pods where a single container had passed the configured threshold. For example, with three containers with 50 restarts and a threshold of 100, the actual "sum over containers" logic makes that pod a candidate for descheduling, but the "largest single container restart count" hypothetical would not have made it a candidate.
Also shifts labelSelector into the parameter table, because when it was added in 29ade13ce7 (#510), it landed a few lines too high.

Good suggestion @wking! I have opened a PR here to do just that: https://github.com/kubernetes/test-infra/pull/23956


Reports: Table CSV Export not formatted properly when using COLLECT(DISTINCT())

The exported CSV from Neodash differs from the exported CSV from the Neo4j Browser, with the Neo4j Browser export respecting lists as a single column, and the Neodash export treating list entities as individual columns.
In short, it looks like the CSV export process treats commas as delimiters, which causes issues when using a COLLECT(DISTINCT()) on tabular fields, as the lists generated by the COLLECT(DISTINCT()) have the entities in the list separated by commas.
To help us understand your issue, please specify important details, primarily:

NeoDash version: 2.4.3

Neo4j Database version: 5.17 Enterprise

Steps to reproduce

Create a Tabular Report

In the report, use a query to return multiple fields that returns multiple properties using COLLECT(DISTINCT)).  Sample query using "Movies":

MATCH (n:Movie)
OPTIONAL MATCH (n)-[:ACTED_IN]-(b)
OPTIONAL MATCH (n)-[:DIRECTED]-(c)
OPTIONAL MATCH (n)-[:PRODUCED]-(d)
RETURN
n.title AS `Movie Name`
, COLLECT(DISTINCT(b.name)) AS `Actors`
, COLLECT(DISTINCT(c.name)) AS `Directors`
, COLLECT(DISTINCT(d.name)) AS `Producers`

Export the CSV from the tabular report, and the columns won't line up with the exported values (instead of there being 4 columns total, each list entity will create its own column)

Expected behavior
For the above query, there should be 4 columns in the CSV export

Actual behavior
I believe the CSV export should have around 12 columns

@nielsdejong - Is there a status update for this bug? Thank you!

Hi @geoffinfosecpersona ,
Thanks for reporting this. To fix this we'll need to make the CSV delimiter configurable as an advanced setting for the table report - you can then choose to go for semicolon or tab, etc.
For now you can probably work around it by using apoc.text.join to turn the list into a ';' seperated string, but it will probably be nicer to customize the CSV delimiter instead.

Brilliant, @nielsdejong.  I'll give that a shot.  Thank you!!

Hi @geoffinfosecpersona , Thanks for reporting this. To fix this we'll need to make the CSV delimiter configurable as an advanced setting for the table report - you can then choose to go for semicolon or tab, etc.
For now you can probably work around it by using apoc.text.join to turn the list into a ';' seperated string, but it will probably be nicer to customize the CSV delimiter instead.


Accept starting position of FEN tag

There seems to be no way to set a custom starting position for the board even though the first move does honor the FEN tag. Shouldn't pygn-mode-display-gui-board-at-pos check if a FEN tag is present and setup the board to the corresponding position ? The FEN position only takes affect after the first move (pygn-mode-next-move-follow-board) is executed. This makes it difficult for instance to use a PGN file that is meant to be a puzzle.

@balbirthomas like #212 this was also fixed long ago, and it should be apparent when you upgrade to the newly-tagged version.


Add enable_coverage_for_eval to coverage

This is supported on ERB and simplecov -
https://github.com/simplecov-ruby/simplecov#coverage-for-eval - but also
seems to work on HAML! We have to run the views for it to identify the
relevant lines, it seems, so we should add at least one
render_views-enabled spec per view, but then it shows coverage data for
each line successfully within HAML too.
Likely needs a lot of tweaks all over the place to make sure we're rendering all the views at least once, and to the final branch coverage metrics and so on, but seems like a cool start, so wanted to open this draft!

CI/CD pipeline failure is just due to coverage, which makes sense with the drop we're seeing here.
Next up: add render_views tests that make sure we exercise all these other views, then merge (even if it results in a coverage drop) so we can work upwards from there

Gonna add a bunch more request specs (#728) in this MR!

[x] admin#index
[x] admin/characters#relocate
[x] admin/characters#preview_relocate
[x] admin/posts#preview_split
[x] admin/posts#regenerate_flat
[x] admin/posts#split
[ ] blocks#_editor
[ ] blocks#edit
[ ] blocks#index
[ ] blocks#new
[x] boards#create
[x] boards#index
[x] boards#new
[ ] board_sections#_editor
[ ] board_sections#edit
[ ] board_sections#new
[ ] board_sections#show
[ ] boards#_reorder_posts
[ ] boards#search
[ ] characters#facecasts
[ ] characters#search
[ ] contribute#index
[ ] galleries#_add_existing
[ ] galleries#_add_new
[ ] galleries#add
[ ] galleries#search
[ ] icons#_editor
[ ] icons#edit
[ ] icons#replace
[ ] index_posts#edit
[ ] index_posts#new
[ ] index_sections#_editor
[ ] index_sections#_single
[ ] index_sections#edit
[ ] index_sections#new
[ ] index_sections#show
[ ] indexes#edit
[ ] indexes#index
[ ] news#_editor
[ ] news#edit
[ ] news#new
[ ] posts#_import
[ ] posts#delete_history
[ ] posts#hidden
[ ] replies#history
[ ] replies#search
[ ] reports#_monthly
[ ] reports#index
[ ] tags#_editor
[ ] tags#edit
[ ] templates#edit
[ ] templates#search
[x] users#new
[x] users#show

Notable for HAML rendering - the final Ruby code often doesn't typically match the input HAML on a line-for-line basis. It's usually within a couple of lines of the raw HAML, but there's enough difference that we can't rely on specific line coverage, just whole-file aggregations and approximate location in the file. (Example where render 'replies/single' and render 'write' should always run together, but one shows as covered and one not.)

Related warning:
Warning: coverage data provided by Coverage [19] exceeds number of lines in /code/app/views/replies/preview.haml [17]

Example compilation mismatch (2 lines HAML, vs 3.5 lines Ruby):
      = link_to unread_path(@post), class: 'view-button-link' do
        .view-button.float-left Unread »

; _haml_compiler1 =  link_to unread_path(@post), class: 'view-button-link' do;
; @output_buffer.safe_concat(("
Unread »
\n".freeze)); end; @output_buffer.safe_concat(((%Q(#{::Haml::Util.escape_html_safe((_haml_compiler1))}

)).to_s)); # and this contains a partial definition of the next line's rendering


Using CRNA with Lerna and Yarn workspaces

Description
Currently CRNA includes App.js through crna-entry.js using a relative import https://github.com/react-community/create-react-native-app/blob/master/react-native-scripts/src/bin/crna-entry.js#L2
import App from '../../../../App';

Problem is that, when using a monorepo approach with Lerna and Yarn workspaces, the node_modules get installed on the root of the project which breaks the relative import for App.js
Expected Behavior
CRNA should ideally support a monorepo configuration and import App.js relative to the CRNA project root.
I've tried to change crna-entry.js to use __dirname instead but that fails once the code is loaded on the device as __dirname is not defined. I've looked into using babel-plugin-transform-dirname-filename to replace it by a string but obviously babel won't transpile node_modules folder by default.
Observed Behavior
What actually happened when you performed the above actions?
CRNA fails to load App.js
Unable to resolve module `../../../../App` from `~/test-monorepo/node_modules/react-native-scripts/build/bin/crna-entry.js` could not resolve `~/test-monorepo/App` as a folder: it did not contain a package, nor an index file

Environment

npm ls react-native-scripts: 1.3.1
npm ls react-native: 0.47.2
npm ls expo: 20.1.3
node -v: 8.4.0
npm -v: 4.6.1
yarn --version: 1.0.2
watchman version: 4.9.0

Operating system: MacOS Sierra 10.12.6
Phone/emulator/simulator & version: iOS (phone & simulator) / Android Genymotion

Reproducible Demo
I've created this example project outlining the problem:
https://github.com/jribeiro/crna-monorepo/tree/app-import-error
Additional Info
I've managed to workaround this by creating an App.js file on the root of the monorepo project that exports the CRNA project App.js. I think it would still be better to have a smother experience though.
The "patched" project can be found here:
https://github.com/jribeiro/crna-monorepo/tree/master
Let me know you're thoughts. Happy to help out as much as I can.

I agree this would be good to support. However, in order to be friendly to beginners, we want to limit the amount of code in the entry point that they have to understand in order to make changes to their project. So, we "hide" the entry point that the packager sees inside node_modules. I think that metro does actually run babel on n_m, but I think we'd have to pass babel some info about the correct project layout, and I'm not sure if the packager supports that.
I'm not entirely sure what the best approach to supporting this is, but I think it'll require some upstream work on metro-bundler.

In case anyone is stuck with this and until the different issues are fixed, I made a little guide on how to use yarn workspaces with Create React App and Create React Native App (Expo) to share common code across. Hope you find it handy! https://learn.viewsdx.com/how-to-use-yarn-workspaces-with-create-react-app-and-create-react-native-app-expo-to-share-common-ea27bc4bad62

Hi @dariocravero, I followed the instructions as per your link but still no luck :( is it possible something changed in CRNA?