fix(DataStore): Reconcile and save serially

Issue #, if available:
Description of changes:
Problem

SyncOrchestator will perform sync queries in order of dependency order (great!)
Enqueue the remote models retrieved from the sync queries to individual ModelQueues for reconcilation

Because the models are reconciled while the next model in the dependecy order is fetched from the sync query,
it may not finish reconciling before the next batch of results for the next model is enqeued and reconciled as well.
If the next batch of reconciliation occurs, before the first batch is completed, then there will be a
foreign key constraint erorr. ie. A depends on B, save B before saving A will fail.
The changes in this PR isolates the operation queue that used to be internal for each AWSModelReconciliationQueue and abstracts it away in ReconcileAndSaveQueue as a single queue. the internals of ReconcileAndSaveQueue uses 1 queue among all AWSModelReconciliationQueue's to perform operations serially, however this can be improved in the future to create an operation queue per group of models (each group containing its own dependency root)
Performance metrics
https://github.com/lawmicha/datastoreLoadTesting
Set up: Saved 100 blogs, each with 3 posts, and each post with 3 comments. Totalling 100 blogs, 300 posts, 900 comments.
Without this change
Time elapsed Blog: 6.5854270458221436 s

Blog length 100
Post length 282
Comment length 762

The blogs are reconciled successfully, however the missing post and comments failed during ReconcileAndSaveOperation with error:
[ReconcileAndLocalSaveOperation] respond(to:): inError(DataStoreError: The operation couldn’t be completed. (SQLite.Result error 0.)
Recovery suggestion: The operation couldn’t be completed. (SQLite.Result error 0.)
Caused by:
FOREIGN KEY constraint failed (code: 19))

With this change, the remote models are reconciled serially
Time elapsed Blog: 5.949587941169739 s.
Time elapsed Post: 14.409731984138489 s.
Time elapsed Comments: 34.13021099567413 s.

Blog length 100
Post length 300
Comment length 900

Check points:

[x] Added new tests to cover change, if needed
[x] All unit tests pass
[x] All integration tests pass
[ ] Documentation update for the change if required
[x] PR title conforms to conventional commit style

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Running the sample app with thread sanitizer enabled against this PR:
WARNING: ThreadSanitizer: Swift access race (pid=68748)
  Modifying access of Swift variable at 0x7b10000430e0 by thread T17:
    #0 ReconcileAndSaveQueue.modelReconcileAndSaveOperations.modify <compiler-generated> (AmplifyPlugins:x86_64+0x177ea4)
    #1 closure #1 in ReconcileAndSaveQueue.addOperation(_:modelName:) ReconcileAndLocalSaveQueue.swift:85 (AmplifyPlugins:x86_64+0x179a6a)
    #2 partial apply for closure #1 in ReconcileAndSaveQueue.addOperation(_:modelName:) <compiler-generated> (AmplifyPlugins:x86_64+0x179edd)
    #3 thunk for @escaping @callee_guaranteed () -> () <compiler-generated> (AmplifyPlugins:x86_64+0xdb73)
    #4 __tsan::invoke_and_release_block(void*) <null>:2 (libclang_rt.tsan_iossim_dynamic.dylib:x86_64+0x70ebb)
    #5 _dispatch_client_callout <null>:2 (libdispatch.dylib:x86_64+0x39c7)

  Previous modifying access of Swift variable at 0x7b10000430e0 by thread T14:
    #0 ReconcileAndSaveQueue.modelReconcileAndSaveOperations.modify <compiler-generated> (AmplifyPlugins:x86_64+0x177ea4)
    #1 closure #1 in closure #1 in ReconcileAndSaveQueue.addOperation(_:modelName:) ReconcileAndLocalSaveQueue.swift:79 (AmplifyPlugins:x86_64+0x17a1cb)
    #2 partial apply for closure #1 in closure #1 in ReconcileAndSaveQueue.addOperation(_:modelName:) <compiler-generated> (AmplifyPlugins:x86_64+0x17d47c)
    #3 Subscribers.Sink.receive(completion:) <null>:2 (Combine:x86_64+0x16faa)
    #4 ReconcileAndLocalSaveOperation.respond(to:) ReconcileAndLocalSaveOperation.swift:111 (AmplifyPlugins:x86_64+0x16b02b)
    #5 closure #1 in closure #1 in ReconcileAndLocalSaveOperation.init(modelSchema:remoteModel:storageAdapter:stateMachine:) ReconcileAndLocalSaveOperation.swift:65 (AmplifyPlugins:x86_64+0x16a03d)
    #6 partial apply for closure #1 in closure #1 in ReconcileAndLocalSaveOperation.init(modelSchema:remoteModel:storageAdapter:stateMachine:) <compiler-generated> (AmplifyPlugins:x86_64+0x1778db)
    #7 thunk for @escaping @callee_guaranteed () -> () <compiler-generated> (AmplifyPlugins:x86_64+0xdb73)
    #8 __tsan::invoke_and_release_block(void*) <null>:2 (libclang_rt.tsan_iossim_dynamic.dylib:x86_64+0x70ebb)
    #9 _dispatch_client_callout <null>:2 (libdispatch.dylib:x86_64+0x39c7)

  Location is heap block of size 56 at 0x7b10000430c0 allocated by thread T6:
    #0 __sanitizer_mz_malloc <null>:2 (libclang_rt.tsan_iossim_dynamic.dylib:x86_64+0x4f29a)
    #1 _malloc_zone_malloc <null>:2 (libsystem_malloc.dylib:x86_64+0x129cf)
    #2 AWSIncomingEventReconciliationQueue.init(modelSchemas:api:storageAdapter:syncExpressions:auth:modelReconciliationQueueFactory:) AWSIncomingEventReconciliationQueue.swift:62 (AmplifyPlugins:x86_64+0x8da47)
    #3 AWSIncomingEventReconciliationQueue.__allocating_init(modelSchemas:api:storageAdapter:syncExpressions:auth:modelReconciliationQueueFactory:) AWSIncomingEventReconciliationQueue.swift (AmplifyPlugins:x86_64+0x8cf1c)
    #4 implicit closure #3 in implicit closure #2 in RemoteSyncEngine.init(storageAdapter:dataStoreConfiguration:outgoingMutationQueue:initialSyncOrchestratorFactory:reconciliationQueueFactory:stateMachine:networkReachabilityPublisher:requestRetryablePolicy:) RemoteSyncEngine.swift:80 (AmplifyPlugins:x86_64+0x18c9dd)
    #5 thunk for @escaping @callee_guaranteed (@guaranteed [ModelSchema], @guaranteed APICategoryGraphQLBehavior, @guaranteed StorageEngineAdapter, @guaranteed [DataStoreSyncExpression], @guaranteed AuthCategoryBehavior?, @guaranteed @escaping @callee_guaranteed (@guaranteed ModelSchema, @guaranteed StorageEngineAdapter, @guaranteed APICategoryGraphQLBehavior, @in_guaranteed ReconcileAndSaveOperationQueue, @in_guaranteed QueryPredicate?, @guaranteed AuthCategoryBehavior?, @in_guaranteed IncomingSubscriptionEventPublisher?) -> (@out ModelReconciliationQueue)?) -> (@owned AWSIncomingEventReconciliationQueue) <compiler-generated> (AmplifyPlugins:x86_64+0x18cad9)
    #6 partial apply for thunk for @escaping @callee_guaranteed (@guaranteed [ModelSchema], @guaranteed APICategoryGraphQLBehavior, @guaranteed StorageEngineAdapter, @guaranteed [DataStoreSyncExpression], @guaranteed AuthCategoryBehavior?, @guaranteed @escaping @callee_guaranteed (@guaranteed ModelSchema, @guaranteed StorageEngineAdapter, @guaranteed APICategoryGraphQLBehavior, @in_guaranteed ReconcileAndSaveOperationQueue, @in_guaranteed QueryPredicate?, @guaranteed AuthCategoryBehavior?, @in_guaranteed IncomingSubscriptionEventPublisher?) -> (@out ModelReconciliationQueue)?) -> (@owned AWSIncomingEventReconciliationQueue) <compiler-generated> (AmplifyPlugins:x86_64+0x18cc28)
    #7 thunk for @escaping @callee_guaranteed (@guaranteed [ModelSchema], @guaranteed APICategoryGraphQLBehavior, @guaranteed StorageEngineAdapter, @guaranteed [DataStoreSyncExpression], @guaranteed AuthCategoryBehavior?, @guaranteed @escaping @callee_guaranteed (@guaranteed ModelSchema, @guaranteed StorageEngineAdapter, @guaranteed APICategoryGraphQLBehavior, @in_guaranteed ReconcileAndSaveOperationQueue, @in_guaranteed QueryPredicate?, @guaranteed AuthCategoryBehavior?, @in_guaranteed IncomingSubscriptionEventPublisher?) -> (@out ModelReconciliationQueue)?) -> (@owned IncomingEventReconciliationQueue) <compiler-generated> (AmplifyPlugins:x86_64+0x1894ab)
    #8 partial apply for thunk for @escaping @callee_guaranteed (@guaranteed [ModelSchema], @guaranteed APICategoryGraphQLBehavior, @guaranteed StorageEngineAdapter, @guaranteed [DataStoreSyncExpression], @guaranteed AuthCategoryBehavior?, @guaranteed @escaping @callee_guaranteed (@guaranteed ModelSchema, @guaranteed StorageEngineAdapter, @guaranteed APICategoryGraphQLBehavior, @in_guaranteed ReconcileAndSaveOperationQueue, @in_guaranteed QueryPredicate?, @guaranteed AuthCategoryBehavior?, @in_guaranteed IncomingSubscriptionEventPublisher?) -> (@out ModelReconciliationQueue)?) -> (@owned IncomingEventReconciliationQueue) <compiler-generated> (AmplifyPlugins:x86_64+0x18cd1a)
    #9 thunk for @escaping @callee_guaranteed (@in_guaranteed [ModelSchema], @in_guaranteed APICategoryGraphQLBehavior, @in_guaranteed StorageEngineAdapter, @in_guaranteed [DataStoreSyncExpression], @in_guaranteed AuthCategoryBehavior?, @in_guaranteed @escaping @callee_guaranteed @substituted <A, B, C, D, E, F, G, H> (@in_guaranteed A, @in_guaranteed B, @in_guaranteed C, @in_guaranteed D, @in_guaranteed E, @in_guaranteed F, @in_guaranteed G) -> (@out H) for <ModelSchemaStorageEngineAdapterAPICategoryGraphQLBehaviorReconcileAndSaveOperationQueueQueryPredicate?AuthCategoryBehavior?IncomingSubscriptionEventPublisher?ModelReconciliationQueue>?) -> (@out IncomingEventReconciliationQueue) <compiler-generated> (AmplifyPlugins:x86_64+0x18994a)
    #10 partial apply for thunk for @escaping @callee_guaranteed (@in_guaranteed [ModelSchema], @in_guaranteed APICategoryGraphQLBehavior, @in_guaranteed StorageEngineAdapter, @in_guaranteed [DataStoreSyncExpression], @in_guaranteed AuthCategoryBehavior?, @in_guaranteed @escaping @callee_guaranteed @substituted <A, B, C, D, E, F, G, H> (@in_guaranteed A, @in_guaranteed B, @in_guaranteed C, @in_guaranteed D, @in_guaranteed E, @in_guaranteed F, @in_guaranteed G) -> (@out H) for <ModelSchemaStorageEngineAdapterAPICategoryGraphQLBehaviorReconcileAndSaveOperationQueueQueryPredicate?AuthCategoryBehavior?IncomingSubscriptionEventPublisher?ModelReconciliationQueue>?) -> (@out IncomingEventReconciliationQueue) <compiler-generated> (AmplifyPlugins:x86_64+0x18ce68)
    #11 RemoteSyncEngine.initializeSubscriptions(api:storageAdapter:) RemoteSyncEngine.swift:266 (AmplifyPlugins:x86_64+0x1944e5)
    #12 RemoteSyncEngine.respond(to:) RemoteSyncEngine.swift:159 (AmplifyPlugins:x86_64+0x190656)
    #13 closure #1 in closure #1 in RemoteSyncEngine.init(storageAdapter:dataStoreConfiguration:outgoingMutationQueue:mutationEventIngester:mutationEventPublisher:initialSyncOrchestratorFactory:reconciliationQueueFactory:stateMachine:networkReachabilityPublisher:requestRetryablePolicy:) RemoteSyncEngine.swift:135 (AmplifyPlugins:x86_64+0x18fe39)
    #14 partial apply for closure #1 in closure #1 in RemoteSyncEngine.init(storageAdapter:dataStoreConfiguration:outgoingMutationQueue:mutationEventIngester:mutationEventPublisher:initialSyncOrchestratorFactory:reconciliationQueueFactory:stateMachine:networkReachabilityPublisher:requestRetryablePolicy:) <compiler-generated> (AmplifyPlugins:x86_64+0x19a2d8)
    #15 thunk for @escaping @callee_guaranteed () -> () <compiler-generated> (AmplifyPlugins:x86_64+0xdb73)
    #16 __tsan::invoke_and_release_block(void*) <null>:2 (libclang_rt.tsan_iossim_dynamic.dylib:x86_64+0x70ebb)
    #17 _dispatch_client_callout <null>:2 (libdispatch.dylib:x86_64+0x39c7)

  Thread T17 (tid=1536006, running) is a GCD worker thread

  Thread T14 (tid=1536003, running) is a GCD worker thread

  Thread T6 (tid=1535557, running) is a GCD worker thread

SUMMARY: ThreadSanitizer: Swift access race <compiler-generated> in ReconcileAndSaveQueue.modelReconcileAndSaveOperations.modify
==================
ThreadSanitizer report breakpoint hit. Use 'thread info -s' to get extended information about the report


ace is loaded even if useAceEditor is set to false

Hello,
I am using jodit-react: 1.0.42
I have a problem when setting the useAceEditor to false. It looks like the flag is not respected and my application is fetching the "https://cdnjs.cloudflare.com/ajax/libs/ace/1.3.3/ace.js" resource.
This cause conflicts inside my application as ace is overriding some of my code implementations.
Looking at the jodit sources I don't see any indication that the flag is checked before fetching ace:
you can see this in ace.ts, line 219:
// global add ace editor in browser 		if (!this.aceExists()) { 			loadNext(editor, editor.options.sourceEditorCDNUrlsJS).then(() => { 				if (!editor.isInDestruct) { 					tryInitAceEditor(); 				} 			}); 		}
I do see this kind of flag check for beautifyHTML.
Is this a bug?
Thanks

Hello,
i use this to disable ace editor :

new Jodit(#editor, {
sourceEditor: "area",
useAceEditor: false,
beautifyHTML: false,
});


The "kubernetes-cni" package is not mentioned in the package list

This is a Bug Report

Problem:
The "kubernetes-cni" is not mentioned, in the list of packages installed by kubernetes
https://kubernetes.io/docs/setup/production-environment/tools/kubeadm/kubelet-integration/#kubernetes-binaries-and-package-contents

Package name
Description

kubeadm
Installs the /usr/bin/kubeadm CLI tool and the kubelet drop-in file for the kubelet.

kubelet
Installs the kubelet binary in /usr/bin and CNI binaries in /opt/cni/bin.

kubectl
Installs the /usr/bin/kubectl binary.

cri-tools
Installs the /usr/bin/crictl binary from the cri-tools git repository.

Proposed Solution:
Add a new row:
kubernetes-cni | Installs the /opt/cni/bin binaries from the plugins git repository.
Page to Update:
https://kubernetes.io/docs/setup/production-environment/tools/kubeadm/kubelet-integration/

Kubernetes Version:
v1.23.4
Additional Information:
The kubernetes-cni package is a dependency, from both kubeadm and kubelet.
Package: kubeadm
Version: 1.23.4-00
...
Depends: kubelet (>= 1.19.0), kubectl (>= 1.19.0), kubernetes-cni (>= 0.8.7), cri-tools (>= 1.19.0)

/assign

#32228

The old text should also be removed from the kubelet row:
Installs the kubelet binary in /usr/bin and CNI binaries in /opt/cni/bin.
Installs the /usr/bin/kubelet binary.
Otherwise the content would be duplicated, between the packages.

There was a plan by sig release to consolidate the cni package inside the kubelet package but that did not go well due to package manager errors and complexities for upgrading users.
+1 to reflect current state.

/sig cluster-lifecycle
/triage accepted
Aside: I'd be tempted to move https://kubernetes.io/docs/setup/production-environment/tools/kubeadm/kubelet-integration/#kubernetes-binaries-and-package-contents so that it lives inside https://kubernetes.io/docs/reference/node/

/language en

We could instead move that section of the page to live within https://kubernetes.io/releases/

Moving the package list to another location makes sense. I think "installing kubeadm" is the only page that talks about packages today (?) so that seems like a good fit. But ideally there ahould be a sig release page that talks about all produced artifacts - source tars, deb, rpm, images etc.

i'm sort of -1 of enumerating the deps of e.g. the kubelet package or other packages on the website.
these are in flux and sig node are not maintaining them.
linking to the deb/rpm specs might not be a stable link either.
the kubelet deps are not enumerated anywhere by the owners - sig node.

So they (crictl and /opt/cni) are undocumented on purpose ?

i'm not sure i understand.
what i'm trying to say above is that we should probably accurately enumerate kubeadm, kubelet, kubectl, cri-tools, kubernetes-cni but not their inner deps like socat and iptables, etc.

Thanks for clarifying, sounds good.

Moving the package list to another location makes sense. I think
"installing kubeadm" is the only page that talks about packages today (?)
so that seems like a good fit. But ideally there ahould be a sig release
page that talks about all produced artifacts - source tars, deb, rpm,
images etc.
On Mar 15, 2022 22:52, "Tim Bannister" @.***> wrote:

We could instead move that section of the page to live within
https://kubernetes.io/releases/
—
Reply to this email directly, view it on GitHub
https://github.com/kubernetes/website/issues/32222#issuecomment-1068462122,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AACRATFKQ53TGNGHFKYWQ2TVAD2AVANCNFSM5QRTWQZQ
.
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 commented.Message ID:
@.***>


Add Client Class

DESIGN
Client class extending Person class with this design:

Client name only mandatory field for constructing

RATIONALE
Client class created to provide flexibility in creating Persons who are clients as:

Not all client details are mandatory but all Person fields are mandatory
Tags in Client class can be restricted to "manager", "private", etc.
Existing tests for Person class supported and Client-specific tests can be added.

BENEFITS

Supports creating other Person sub-classes like "Teammate", "Lead", etc. later on.
Supports creating types of clients later such as 'Office', 'NGO', etc.

I'll continue the thread here: I'd ask you to help me refactor the package structure of the current project.
One of the good points on the packaging is that (1) it provides some sort of hierarchical structure in code, and (2) that package visibilities help out a pretty good amount in organising code. That is to say, best practice is to avoid imports across packages, for imports within (sub)packages. From my experience, imports across packages are a sort of antipattern - they make messy, spaghetti code over time. Would recommend either moving Client.java into the model.person package, or creating a model.person.client package instead.
Regarding people, I am unsure whether the Person class is even needed at this stage. We are only keeping track of Clients, correct? I would recommend either deleting the Person class, or if you see any other subclasses of Person.java, I would recommend changing it to an abstract class at this moment.

Other than that, as @ConradLew mentioned, I'm not too sure about keeping the Tag class, but I guess we can keep it right now, it isn't too important - I'll leave the decision up to you @Aishwarya-Hariharan-Iyer
Other than that, LGTM!

Other than that, as @ConradLew mentioned, I'm not too sure about keeping the Tag class, but I guess we can keep it right now, it isn't too important - I'll leave the decision up to you @Aishwarya-Hariharan-Iyer
Other than that, LGTM!

Tysm for the suggestions! Thanks @ConradLew too for all the suggestions including the ones in the linked thread. @Yongbeom-Kim we considered removing the Tag and Address bits for Client but hesitated considering LSP. But that is a very important point that we might have to discuss in our meeting!


Failure to launch on Mac OS X after upgrade to 3.0.0b2

Description of your problem
Attempted to upgrade to v3.0.0b2 in order to fix Issue #2724, following the steps described in the comment here. After following those steps, Spyder fails to launch, giving a 'Python crashed unexpectedly' error.
What steps will reproduce the problem?

Upgrade Spyder and PyQt, following these steps.
Launch Spyder, either from command line or Anaconda Launcher.

What is the expected output? What do you see instead?
Expected is an instance of Spyder.  Launching via Anaconda Launcher GUI gives same result. Rolling back to 2.3.8 works fine again, though Issue #2724 persists.
Please provide any additional information below
During rollback to 2.3.8, conda gives warning messages
Warning: 4 possible package resolutions (only showing differing packages):

qtawesome-0.3.2-py27_0.tar.bz2, qtpy-1.0-py_0.tar.bz2
qtawesome-0.3.2-py_0.tar.bz2, qtpy-1.0-py_0.tar.bz2
qtawesome-0.3.2-py27_0.tar.bz2, qtpy-1.0-py27_0.tar.bz2
qtawesome-0.3.2-py_0.tar.bz2, qtpy-1.0-py27_0.tar.bz2

Do not know if this is relevant...
Versions and main components

Spyder Version: 3.0.0b2
Python Version: 2.7.11 via Anaconda 4.0.0
Operating system: Mac OS X 10.11.3

Dependencies
These obtained after rollback to 2.3.8:
IPython >=1.0      :  4.1.2 (OK)
jedi >=0.8.1;<0.9.0:  0.8.1 (OK)
matplotlib >=1.0   :  1.5.1 (OK)
pandas >=0.13.1    :  0.18.0 (OK)
pep8 >=0.6         :  1.7.0 (OK)
psutil >=0.3       :  4.1.0 (OK)
pyflakes >=0.5.0   :  1.1.0 (OK)
pygments >=1.6     :  2.1.1 (OK)
pylint >=0.25      :  1.5.4 (OK)
qtconsole >=4.0    :  4.2.1 (OK)
rope >=0.9.2       :  0.9.4 (OK)
sphinx >=0.6.6     :  1.3.5 (OK)
sympy >=0.7.3      :  0.7.2 (NOK)
zmq >=2.1.11       :  15.2.0 (OK)

Is there something printed in the terminal before the crash occurs?

Nothing other than the
'/Users/username/anaconda/bin/python.app: line 3: 87074 Bus error: 10'
message when the crash occurs.

This is going to be definitely solved when we release Spyder 3.0 with Anaconda 4.1 at the end of the month :-)


Adding support for Docker service 'After' attribute in Unit file

This is a pull request for: https://github.com/garethr/garethr-docker/issues/619

Hi @eyal-lupu. Thanks for your contribution! The PR is looking good, though we require a few things to move forward.

There will need to be some spec tests to confirm your changes are behaving in the manner you expect.

An example is https://github.com/garethr/garethr-docker/pull/534/files#diff-57c32a956fccf5af23aba2bce1d74d1d.

The commits will need to be squashed before they can be merged.

If you have any questions just let us know.

Hi @garethr
thank you for your response. I an not familiar with Ruby at all but reverse engineering the existing tests it seems that adding a test similar to the below should work
context 'with systemd service_unit_after' do
        let(:params) { { 'service_unit_after' => 'network-online.target' } }
        it { should contain_file(service_override_file).with_content(/After=network-online.target/) }
        end

It does run but seems to be failing as the override files is missing:

docker on RedHat with systemd service_unit_after should contain File[/etc/systemd/system/docker.service.d/service-overrides.conf] with content =~ /After=network-online.target/
Failure/Error: it { should contain_file(service_override_file).with_content(/After=network-online.target/) }
expected that the catalogue would contain File[/etc/systemd/system/docker.service.d/service-overrides.conf]
# ./spec/classes/docker_spec.rb:214:in `block (5 levels) in <top (required)>'

As I am really not familiar with that environment I am a bit blocked in here. If someone could enable the tests to create the file I will be more than happy to take that from there


MHRise launched, but HMD screen only shows steamvr background

Are you using an HDR screen? Can you post the re2_framework_log.txt that's in your game folder?

Are you using an HDR screen? Can you post the re2_framework_log.txt that's in your game folder?

re2_framework_log.txt

re2_framework_log.txt

ok, I somehow managed to launch the game and see it in my HMD, but it looks a bit weird...

ok, I somehow managed to launch the game and see it in my HMD, but it looks a bit weird...

Can you try closing SteamVR, open MHRise without your headset on, and then put it on after the mod fully initializes?

Can you try closing SteamVR, open MHRise without your headset on, and then put it on after the mod fully initializes?

Ok, ignore what I said there since you got it working. Turn off Borderless mode.

Ok, ignore what I said there since you got it working. Turn off Borderless mode.

Ok, ignore what I said there since you got it working. Turn off Borderless mode.

So which mode should I use, maybe fullscreen?

Ok, ignore what I said there since you got it working. Turn off Borderless mode.

So which mode should I use, maybe fullscreen?

thanks, i fixed it :)

thanks, i fixed it :)

sorry for the off-topic question - it is possible to make the game first-person?

sorry for the off-topic question - it is possible to make the game first-person?

It is possible, but it's only currently implemented in RE2 and RE3.

It is possible, but it's only currently implemented in RE2 and RE3.


Frontend: Hide and deprecate options for Swift 3 @objc inference

The compiler has not supported migrating Swift 3 code to Swift 4 for a long time. The -enable-swift3-objc-inference option and related options were originally designed to aid that transition and should be deprecated and no longer advertised.
Resolves rdar://120490061

@swift-ci please smoke test

Driver update: https://github.com/apple/swift-driver/pull/1521


Changed names of bucket and dataset in semseg watch

Changed name of parameters to make them more intuitive - called out by voxel. Will update the docs

Codecov Report

Merging #676 (bdf9d2a) into main (5b9ea07) will increase coverage by 0.00%.
The diff coverage is 69.23%.

@@           Coverage Diff           @@
##             main     #676   +/-   ##
=======================================
  Coverage   84.08%   84.08%
=======================================
  Files         167      167
  Lines       13375    13380    +5
=======================================
+ Hits        11246    11251    +5
  Misses       2129     2129

Impacted Files
Coverage Δ

...uality/integrations/torch_semantic_segmentation.py
0.00% <0.00%> (ø)

...lity/loggers/model_logger/semantic_segmentation.py
0.00% <0.00%> (ø)

dataquality/core/log.py
95.00% <100.00%> (+0.12%)
:arrow_up:

tests/core/test_log.py
100.00% <100.00%> (ø)

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


Uncaught ErrorException: var_export does not handle circular references

Describe the bug
When there's a circular reference in an object, I am getting a PHP Warning:  Uncaught ErrorException: var_export does not handle circular references in /.../vendor/spatie/ray/src/Payloads/LogPayload.php:64 even though I am on 1.37.3 version which has try try/catch
        try {
            return var_export($value, true);
        } catch (Exception $ex) {
            return '';
        }

It is quite weird because I thought that ErrorException is a children of Exception. It is even more weird that I am getting out of memory exception in the Ray itself on the same line.

Versions

spatie/ray package version: 1.37.3
spatie/laravel-ray package version (if applicable): 1.32.6
PHP version: 8.2
Laravel version (if applicable): 10.XX

@genesiscz @bartbrinkman I added an extra check for recursiveness before doing the var_export. Could you give 1.37.5 a try?

@timvandijck Still broken with 1.37.5

@genesiscz @bartbrinkman I added an extra check for recursiveness before doing the var_export. Could you give 1.37.5 a try?

Can you help me understand what the clipboard means? And isn't doing this check just resulting in Ray not receiving what it should?

In my case, this fix doesn't help, because I have magic __debugInfo() in my BaseModel which is being checked for recursiveness but results in false negative because I am redacting some of the key-values because of other dumpings (including ray). My print_r looks like this:
App\Lead\Manager\LeadHandlerUtils\CascadeOfferItemsGrouper Object
(
    [lastDistributionType:App\Lead\Manager\LeadHandlerUtils\CascadeOfferItemsGrouper:private] => exclusive
    [cascadeOfferItemGroups] => Illuminate\Support\Collection Object
        (
            [items:protected] => Array
                (
                    [0] => App\Collections\CascadeOfferItemsCollection Object
                        (
                            [items:protected] => Array
                                (
                                    [0] => App\Models\CascadeOfferItem Object
                                        (
                                            [guarded:protected] => Array
                                                (
                                                )

                                            [fillable:protected] => Array
                                                (
                                                )

                                            [original:protected] => retracted
                                            [netteRow:protected] => retracted
                                            [notDbValues] => retracted
                                            [notApiValues:protected] => Array
                                                (
                                                )

                                        )

                                )

                            [escapeWhenCastingToString:protected] =>
                        )

                    [1] => App\Collections\CascadeOfferItemsCollection Object
                        (
                            [items:protected] => Array
                                (
                                    [0] => App\Models\CascadeOfferItem Object
                                        (
                                            [guarded:protected] => Array
                                                (
                                                )

                                            [fillable:protected] => Array
                                                (
                                                )

                                            [original:protected] => retracted
                                            [netteRow:protected] => retracted
                                            [notDbValues] => retracted
                                            [notApiValues:protected] => Array
                                                (
                                                )

                                        )

                                )

                            [escapeWhenCastingToString:protected] =>
                        )

                    [2] => App\Collections\CascadeOfferItemsCollection Object
                        (
                            [items:protected] => Array
                                (
                                    [0] => App\Models\CascadeOfferItem Object
                                        (
                                            [guarded:protected] => Array
                                                (
                                                )

                                            [fillable:protected] => Array
                                                (
                                                )

                                            [original:protected] => retracted
                                            [netteRow:protected] => retracted
                                            [notDbValues] => retracted
                                            [notApiValues:protected] => Array
                                                (
                                                )

                                        )

                                    [1] => App\Models\CascadeOfferItem Object
                                        (
                                            [guarded:protected] => Array
                                                (
                                                )

                                            [fillable:protected] => Array
                                                (
                                                )

                                            [original:protected] => retracted
                                            [netteRow:protected] => retracted
                                            [notDbValues] => retracted
                                            [notApiValues:protected] => Array
                                                (
                                                )

                                        )

                                )

                            [escapeWhenCastingToString:protected] =>
                        )

                    [3] => App\Collections\CascadeOfferItemsCollection Object
                        (
                            [items:protected] => Array
                                (
                                    [0] => App\Models\CascadeOfferItem Object
                                        (
                                            [guarded:protected] => Array
                                                (
                                                )

                                            [fillable:protected] => Array
                                                (
                                                )

                                            [original:protected] => retracted
                                            [netteRow:protected] => retracted
                                            [notDbValues] => retracted
                                            [notApiValues:protected] => Array
                                                (
                                                )

                                        )

                                )

                            [escapeWhenCastingToString:protected] =>
                        )

                )

            [escapeWhenCastingToString:protected] =>
        )

)

Unfortunatelly even after commenting these methods, it won't start working. Even worse, the print_r is now resulting in memory error:
PHP Fatal error:  Allowed memory size of<PHONE_NUMBER> bytes exhausted (tried to allocate 803213312 bytes) in /.../vendor/spatie/ray/src/Payloads/LogPayload.php on line 84
Maybe it's a bug in PHP not being able to detect the RECURSION because I have some weird recursion there? To be honest, I can't even find a documented *RECURSION* detection in the print_r itself: https://www.php.net/manual/en/function.print-r.php

@genesiscz @bartbrinkman I added an extra check for recursiveness before doing the var_export. Could you give 1.37.5 a try?

Can you help me understand what the clipboard means? And isn't doing this check just resulting in Ray not receiving what it should?

It was added to support the new copy button that allows you to copy the output in the Ray app. We need to send it in a different way (var_export) to make it usefull.
The copy button will not be shown if we detect a circular reference because it's hard to output that in a string format and var_export doesn't even support it. Most of the time these aren't the variables you would want to copy anyway.
Anyway: thank you for the input, I'm going to try and replicate it and see how we can resolve this.

Shouldn't we revert this nice to have feature so that the core feature of Ray can be used?

I was able to replicate scenario's that triggered the problems that were mentioned. I now added a more robust implementation to log variables.
As far as my own test scenario's go this seems to resolve all issues. It has been added to release 1.37.6.
In the future we might add some extra options to skip exporting these variables for when you want things to be faster like in tests.

I can confirm this resolved the issue. Thank you! Although, is there a way to force the depth to be deeper?
Because

I can override LogPayload
I can override PayloadFactory to return my LogPayload
I would have to override Ray.php and copy all of it excluding the $payloads = PayloadFactory::createForValues($arguments); which would be a different (my) PayloadFactory.

I kinda like the clipboard feature, but hitting depth 5 is pretty easy a lot of times:
App\Lead\Manager\LeadHandlerUtils\CascadeOfferItemsGrouper#1
(
    [App\Lead\Manager\LeadHandlerUtils\CascadeOfferItemsGrouper:lastDistributionType] => 'exclusive'
    [cascadeOfferItemGroups] => Illuminate\Support\Collection#2
    (
        [*:items] => [
            0 => App\Collections\CascadeOfferItemsCollection#3
            (
                [*:items] => [
                    0 => App\Models\CascadeOfferItem(...),
                ]
                [*:escapeWhenCastingToString] => false
            ),
            1 => App\Collections\CascadeOfferItemsCollection#4
            (
                [*:items] => [
                    0 => App\Models\CascadeOfferItem(...),
                ]
                [*:escapeWhenCastingToString] => false
            ),
            2 => App\Collections\CascadeOfferItemsCollection#5
            (
                [*:items] => [
                    0 => App\Models\CascadeOfferItem(...),
                    1 => App\Models\CascadeOfferItem(...),
                ]
                [*:escapeWhenCastingToString] => false
            ),
            3 => App\Collections\CascadeOfferItemsCollection#6
            (
                [*:items] => [
                    0 => App\Models\CascadeOfferItem(...),
                ]
                [*:escapeWhenCastingToString] => false
            ),
        ]
        [*:escapeWhenCastingToString] => false
    )
)

Ray

have the same problem on 1.32,  all I did was throw an exception, and log the exception with ray.

I am on 1.33.0 on laravel-ray and 1.37.7 on ray itself. Still happens on that version?


checks for babel polyfill

Adds a check to ensure babel polyfill has not been defined. This ensures the script can be loaded in multiple webpack entries on the same page.

Also adds a fix for IE 11, nodelist.forEach does not exist.

Hi there, any update on this? Our team has to build the package manually on each npm install as the repo does not have the dist folder.
Thanks! :)


Adding myself to plugin-jx-resources.yml

CC @jstrachan to let me deal with problems like https://github.com/jenkinsci/jx-resources-plugin/pull/24#issuecomment-463023469.

@jstrachan Do you sign off on this? Thanks!

@jglick I am not sure that @jstrachan checks notifications from github, so you may want to contact him directly to get him to look at this.

Alternately, perhaps @rawlingsj wishes to resurrect the automatic releaser.

@slide I sign off on this thanks!

@batmat yet I still lack write permission to the repository. I thought that was handled when one of these got merged?

Not by default @jglick, there are many cases where people already actually have permission to work/merge PRs, but not to release yet. So better please ask explicitly for it in general indeed.
Anyway, done now.
[14:30] <+     batmat> | jenkins-admin: yo
[14:30] <@jenkins-adm> | I didn't understand the command
[14:30] <+     batmat> | jenkins-admin: make jglick committer on jx-resources-plugin
[14:30] <@jenkins-adm> | Added jglick as a GitHub committer for repository jx-resources-plugin
[14:30] <+     batmat> | jenkins-admin: thanks botty friend
[14:30] <@jenkins-adm> | You're welcome
[14:30] <+     batmat> | jenkins-admin: no, really, that was helpful
[14:30] <@jenkins-adm> | Wut?


Incorrect Office language for Kazakh

In "https://officedev.github.io/Office-IT-Pro-Deployment-Scripts/XmlEditor.html" you can choose language for Kazakh that add value: Language ID="kk-kh" ,but this is incorrect. With this configuration installation will fail.
Correct: Language ID="kk-kz"
More information:
https://technet.microsoft.com/en-us/library/cc179219.aspx
Thanks! :)

We have updated the language ID for Kazakh.  Thank you for pointing our this issue.


Need list of supporting grants

Research papers typically include a list of supporting grants in the acknowledgements section and we will need to compile a list of the grants that have supported HyP3 throughout its development. For each grant we will need:

Grant name
Grant number (if applicable)
Grant award date

The DAAC funding grants are the obvious place to start, but I'm unsure if there are other grants that need to be included.

Franz will likely be the best person for this info.


add location_session_path for SessionsClient

WHAT
Add location_session_path method for SessionsClient v2beta1.
WHY
We need to set location in the case of requesting for non-US locations (e.g. asia-northeast1).
https://cloud.google.com/dialogflow/es/docs/how/region#api
I'm sure there are other paths developer will need, but in the meantime, let me add the path we need.

@googlebot I signed it!

This PR is obsolete as the file being changed no longer exists. Please open an issue if the problem still exists.


spring cloud gateway 2.0.x exception

Please answer these questions before submitting your issue.

Why do you submit this issue?
[ ] Question or discussion
[x] Bug
[ ] Requirement
[ ] Feature or performance improvement

Question

What do you want to know?
How to fix this bug? is this version skywalking cannot supported?
OR now which spring cloud version is supported so I can switch to.

Bug

Which version of SkyWalking, OS and JRE?
SkyWalking version: 6.2.0
OS:  ubuntu 16.04
jre: oracle jre-8u161-linux-x64
spring-cloud-dependencies: Greenwich.RELEASE
spring-cloud-starter-gateway: 2.1.0.RELEASE ( depend on spring-boot-starter-webflux )

Which company or project?
Guo Tai Jun An Futures.

What happen?
when I start project,  many warn Exception occured like this:

java.lang.IllegalStateException: Cannot resolve type description for javax.servlet.http.HttpServlet

the first trace print this Exception:

ERROR 2019-07-10 02:50:52:881 reactor-http-epoll-6 InstMethodsInter :  class[class reactor.netty.http.client.HttpClientOperations] before method[send] intercept failure
java.lang.IllegalArgumentException: ContextSnapshot can't be null.
at org.apache.skywalking.apm.agent.core.context.ContextManager.continued(ContextManager.java:145)
at org.apache.skywalking.apm.plugin.spring.cloud.gateway.v2.HttpClientOperationsSendInterceptor.beforeMethod(HttpClientOperationsSendInterceptor.java:59)
at org.apache.skywalking.apm.agent.core.plugin.interceptor.enhance.InstMethodsInter.intercept(InstMethodsInter.java:82)
at reactor.netty.http.client.HttpClientOperations.send(HttpClientOperations.java)
at org.springframework.http.client.reactive.ReactorClientHttpRequest.lambda$writeWith$0(ReactorClientHttpRequest.java:87)
at java.util.stream.ReferencePipeline$3$1.accept(ReferencePipeline.java:193)
at java.util.ArrayList$ArrayListSpliterator.forEachRemaining(ArrayList.java:1374)
at java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:481)
at java.util.stream.AbstractPipeline.wrapAndCopyInto(AbstractPipeline.java:471)
at java.util.stream.ReduceOps$ReduceOp.evaluateSequential(ReduceOps.java:708)
at java.util.stream.AbstractPipeline.evaluate(AbstractPipeline.java:234)
at java.util.stream.ReferencePipeline.collect(ReferencePipeline.java:499)
at org.springframework.http.client.reactive.AbstractClientHttpRequest.doCommit(AbstractClientHttpRequest.java:133)
at org.springframework.http.client.reactive.ReactorClientHttpRequest.writeWith(ReactorClientHttpRequest.java:83)
at org.springframework.http.codec.FormHttpMessageWriter.lambda$write$0(FormHttpMessageWriter.java:139)
at reactor.core.publisher.FluxFlatMap.trySubscribeScalarMap(FluxFlatMap.java:141)
at reactor.core.publisher.MonoFlatMap.subscribe(MonoFlatMap.java:53)
at reactor.core.publisher.Mono.subscribe(Mono.java:3710)
at reactor.core.publisher.FluxFlatMap.trySubscribeScalarMap(FluxFlatMap.java:169)
at reactor.core.publisher.MonoFlatMap.subscribe(MonoFlatMap.java:53)
at reactor.core.publisher.MonoDefer.subscribe(MonoDefer.java:52)
at reactor.netty.http.client.HttpClientConnect$HttpIOHandlerObserver.onStateChange(HttpClientConnect.java:441)
at reactor.netty.ReactorNetty$CompositeConnectionObserver.onStateChange(ReactorNetty.java:470)
at reactor.netty.resources.PooledConnectionProvider$DisposableAcquire.onStateChange(PooledConnectionProvider.java:515)
at reactor.netty.resources.PooledConnectionProvider$DisposableAcquire.run(PooledConnectionProvider.java:544)
at io.netty.util.concurrent.AbstractEventExecutor.safeExecute(AbstractEventExecutor.java:163)
at io.netty.util.concurrent.SingleThreadEventExecutor.runAllTasks(SingleThreadEventExecutor.java:405)
at io.netty.channel.epoll.EpollEventLoop.run(EpollEventLoop.java:338)
at io.netty.util.concurrent.SingleThreadEventExecutor$5.run(SingleThreadEventExecutor.java:906)
at io.netty.util.internal.ThreadExecutorMap$2.run(ThreadExecutorMap.java:74)
at java.lang.Thread.run(Thread.java:745)

And only the first request trace item can be sent to oap server,  then oap server can not receive trace any more.
the detail log please see the attatchment.
skywalking-api.log

Requirement or improvement

could you provide the supported version of webflux or gateway version?
Thanks a lot.

We don't support 2.0.x. Supported list is there

@zhaoyuguang I have switched spring-cloud-gateway version to 2.1.x, and it doesn't work well too. through serveral test cases,

I found it's because gateway 2.1.x can't work with spring-boot version 2.1.6.
Then I use spring boot 2.1.4, It's work. may be we should support in next skywalking version, right?

Thanks a lot.


User hits back while signing the Docusign process still the status is updated

When user gets directed to docu-sign for ICLA & if he/she clicks back button then the problem arises - the system consider icla as signed which should not happen. However, as this is a rare case, we decided to log a different ticket to tackle it after the 1st easycla release.

This has been resolved.  Closing ticket.


Sensu sent only one email

I got this message repeated:
{"timestamp":"2016-08-09T16:28:28.539539+0200","level":"info","message":"handler output","handler":{"type":"pipe","command":"cat","name":"stdout"},"output":["{\"client\":{\"name\":\"n2.client.io\",\"address\":\"<IP_ADDRESS>\",\"subscriptions\":[\"etcd\",\"openshift-node\",\"default_rhel\",\"default\"],\"load\":{\"warning\":\"1,1,1\",\"critical\":\"2,2,2\"},\"version\":\"0.20.3\",\"timestamp\":1470720441},\"check\":{\"thresholds\":{\"warning\":120,\"critical\":180},\"name\":\"keepalive\",\"issued\":1470752908,\"executed\":1470752908,\"output\":\"No keepalive sent from client for 32467 seconds (>=180)\",\"status\":2,\"type\":\"standard\",\"history\":[\"2\",\"2\",\"2\",\"2\",\"2\",\"2\",\"2\",\"2\",\"2\",\"2\",\"2\",\"2\",\"2\",\"2\",\"2\",\"2\",\"2\",\"2\",\"2\",\"2\",\"2\"],\"total_state_change\":0},\"occurrences\":1074,\"action\":\"create\",\"timestamp\":1470752908,\"id\":\"c2b54e25-79fc-415f-bb0f-429279fbdac5\",\"last_state_change\":null,\"last_ok\":null}"]}
But sensu only sent message on first occurrence of this event.
I went through configuration (which was done via ansible scripts) and I don't know where to look at.
I am using standard sensu-plugin-mailer handler.
Can there be a problem that some checks has defined refresh interval to one day? (which I will see tomorrow)?

I've wirtten refresh interval like this:
"keepalive": {
  "thresholds": {
    "warning": 60,
    "critical": 300
  },
  "handlers": ["mailer"],
  "refresh": 1800
},

Into client.json file and it seems that everything is working from now.

This looks to be an issue related to the event handler doing it's own event filtering (not in Sensu core). Event handlers built on the sensu-plugin library do support occurrence filtering, using the check definition attributes occurrences and refresh. It looks like you have figured this out, by changing the refresh value to 30 minutes :+1:


ErrorException at http://mage2.website/forum/general/post

Hello, I just want to report an exception in your forum at http://mage2.website/forum/general/post/create. It throws an exception when I click the Create option:
ErrorException in PostController.php line 58: Trying to get property of non-object

 in PostController.php line 58
    at HandleExceptions->handleError(8, 'Trying to get property of non-object', '/var/www/laravel/app/Http/Controllers/PostController.php', 58, array('request' => object(PostRequest), 'categorySlug' => 'general', 'category' => object(Category), 'user' => null)) in PostController.php line 58

AugustoSL

@agsotelo  Thanks.  this bug should be fixed on website.


Watch compass not working smooth on LG G Watch R

I do now own a LG G Watch R and tested c:geo wear on it. I am however not sure about the exact cause of the problem, so I try to descibe my experience:

Basically the compass if alway off by 180°. I never had a correct direction up to now.
If I turn the watch there are some positions which make the arrow move permanently more or less randomly. Turning the watch a bit more makes it go back to the 180° offset.
It seems a bit as if slow movements would keep the arrow at 180° offset while fast movements might get it unsteady also after the movement is stopped (but that is only a guess).

I checked my watch compass with this app:
https://play.google.com/store/apps/details?id=com.runar.wearcompass
It is working fine as you can see here:
http://youtu.be/40m_54qRALY
Next is a video of the typical error case with c:geo wear (Note: The watch is not moved, good conditions are checked with the bearing app...compass hardware is working fine):
http://youtu.be/ZOySZNEN9f8
If I set c:geo wear to use the smartphone compass everything is OK.
Tell me if I can help by testing any APK snapshots or alike.
Environment:
Samsung Galaxy S4, Android 4.4.2
c:geo wear Version 2.1.1
LG G Watch R 5.0.1 (Android Wear <IP_ADDRESS>7902, Play Services 6.5.90(1610726-534)
Build LWX48P

I've been experiencing the same issue with my Asus ZenWatch.
Environment:
Samsung Galaxy S4, Android 4.4.4
c:geo wear Version 2.1.1
ASUS ZenWatch B4A0
SW 5.0.1
Android Wear ver. <IP_ADDRESS>0507

If you disable watch compass, does the compass displayed on the watch match the compass displayed by selecting "Navigate > Compass" in c:geo?
If so, then this is very confusing because all the position calculations are exactly the same regardless of whether they happen on the phone or watch; they are defined in this file: https://github.com/culmor30/cgeo-wear/blob/master/locationUtils/src/main/java/com/javadog/LocationUtils/LocationUtils.java
Perhaps there's some 'offset' variable the system provides which I'm not accounting for? I really don't want to go the route of "offset compatibility lists" for each Android Wear device because that would be very difficult to maintain. Any suggestions?

I will try to get more experience with how the watch compass behaves and also compare to other wear apps and the behavior if the phone compass is used and come back to you in some days.

I was looking at the settings and I'm not sure exactly how to disable the
watch compass.  I checked again and I believe it's actually offset 90deg
and not 180deg as I had originally stated.  That said, I've had problems w/
another caching program on the phone (WhereYouGo) being offset by 90 as
well.   All the other caching and compass related ones on the phone have
been spot on.
That said, I believe the sensor's Native orientation is 90 off (I remember
seeing this somewhere in one of the diagnostic programs, but can't seem to
locate it right now), but the OS compensates when passing to programs
through typical APIs.  However, the way WhereYouGo pulls it it has the
offset (I switch to map mode on WhereYouGo to do the WhereIGo's)
I'll see if I can dig further.  If you can let me know how to disable the
watch compass I'll give your first test a try.
On Tue, Feb 10, 2015 at 2:53 PM, Cullin Moran<EMAIL_ADDRESS>wrote:

If you disable watch compass, does the compass displayed on the watch
match the compass displayed by selecting "Navigate > Compass" in c:geo?
If so, then this is very confusing because all the position calculations
are exactly the same regardless of whether they happen on the phone or
watch; they are defined in this file:
https://github.com/culmor30/cgeo-wear/blob/master/locationUtils/src/main/java/com/javadog/LocationUtils/LocationUtils.java
Perhaps there's some 'offset' variable the system provides which I'm not
accounting for? I really don't want to go the route of "offset
compatibility lists" for each Android Wear device because that would be
very difficult to maintain. Any suggestions?
—
Reply to this email directly or view it on GitHub
https://github.com/culmor30/cgeo-wear/issues/13#issuecomment-73781305.

@Lineflyer, thanks :)
@TAZ427, I meant that you should try opening the c:geo wear phone app and uncheck the "Use watch compass" preference.

I tested it w/ the watch compass disabled via the c:geo wear phone app.  It consistently matched what the compass (from the listing and in compass mode) within c:geo displayed.  I tried it in both orientations and the direction continued to match.
Also, here's a link showing my watch tracking of it's internal compass http://youtu.be/Iit6M1pwZgQ

Okay, so it looks like there is some issue specific to Wear devices, unless I'm overlooking something. I'll experiment in trying to fix this.

OK, as promised here are some more details:
First of all I made some more test runs using the watch compass on my LG G Watch R and the main problem is still as described initially.

The compass still has a stable 180° offset (I tried calibrating, etc, etc.) but is still working normal in other apps.

Here are screenshots with comparison of phone and watch in every orientation:

If I continuously rotate the watch there are some (2-3) angles which make the compass "jumpy". If I stop rotating at this point it keeps jumping randomly, if I continue rotation it is back to the 180° offset. Here is another video of this:
http://youtu.be/89WYoS0KN2Y

If I select to use the phone compass the watch arrow is identical to the phone compass. However I managed to reproduce the jumpy behaviour also with this setting, but it only lasted for a few seconds then it got stable again.
Pure speculation: It could be that both modes (watch or phone compass) have the same bug here, but the compass of the phone delivers a kind of filtered data, which the watch does not.

@culmor30
Please let me know If I can help e.g. by testing development builds, etc.
I was out caching today and tried to use cgeo wear on my LG. It was quite disappointing due to the issues mentioned above.

The best I can do for now is mark this as help-wanted. I'd love if someone could take a look at the source and let me know if I'm doing something wrong (or potentially fix the issue with a pull request) because I can't replicate this bug on my Moto 360 and I have no idea what's causing it.

I can try to organize a Zenwatch for testing. According to @TAZ427 it has the same issue.

That would be very helpful. Let me know the details by email: my gmail is 'culmor30'. (Not listing the address in plaintext because of spambots.)

I have an LG G Watch R and a Nexus 5 both running Lollipop. Happy to test builds :)

AFAIk android wear also provides ADB logs (although I never tested how this should work)...but If you would create a version with log outputs I could try to provide a logs of that...
That would of course mean, that you first need to have an idea about what might be helpful to analyze/log.

What I can tell from my testing, the cgeoWearService.java has following place where it initializes the cache location:
		if(useWatchCompass) {
			Location cacheLoc = new Location("phoneApp");
			cacheLoc.setLatitude(startIntent.getFloatExtra(MessageDataset.KEY_CACHE_LATITUDE, 0f));
			cacheLoc.setLongitude(startIntent.getFloatExtra(MessageDataset.KEY_CACHE_LONGITUDE, 0f));
			cacheLocation = cacheLoc;
		}

What I can tell, those CACHE_LATITUDE and CACHE_LONGITUDE keys do not exists. Thus the heading points to 0,0.
Changing that to
			cacheLocation = (Location) startIntent.getExtras().get(MessageDataset.KEY_CACHE_LOCATION);

Magically fixes the arrow on the watch.

@culmor30 Any clues from that?

I have the same problem with Sony Smartwatch 3.
@gittiku Is it possible to get the fixed version from you as an .apk file?

@Tobeias You can try https://dl.dropboxusercontent.com/u/66375210/wear-debug.apk

Hi gittiku,
Thank you for quick reply. After installed both apk files, the navigation
option "wear" is visible. But there is no app at the watch. Do you have an
idea what's going wrong here? I tried to install both .apk files in
different order.
BR
@Tobeias https://github.com/Tobeias You can try
https://dl.dropboxusercontent.com/u/66375210/wear-debug.apk
—
Reply to this email directly or view it on GitHub
https://github.com/culmor30/cgeo-wear/issues/13#issuecomment-109732613.

@Tobeias Did the wear-debug.apk install without errors to the watch (not to the phone)?

@Tobeias Try https://dl.dropboxusercontent.com/u/66375210/mobile-release.apk instead. It is signed and should automatically get installed on the watch.

Sorry I've been largely unresponsive; been very busy with work. I'll promise I'll take a closer look at this soon and get an official patch on Gplay :)

Oh, sorry. I installed both on the smartphone. I will try the other way
soon.
2015-06-07 18:29 GMT+02:00 gittiku<EMAIL_ADDRESS>
@Tobeias https://github.com/Tobeias Did the wear-debug.apk install
without errors to the watch (not to the phone)?
—
Reply to this email directly or view it on GitHub
https://github.com/culmor30/cgeo-wear/issues/13#issuecomment-109769065.

@Tobeias Try https://dl.dropboxusercontent.com/u/66375210/mobile-release.apk instead. It is signed and should automatically get installed on the watch.

I also installed the APK from the link mentioned above.
It installs on my LG G watch R without a problem.
I did a short first test of the compass and it seems to work more reliable now. Most of the time it shows the correct direction to the cache. Only at some angles it suddenly turns by 180° but turns back to the correct direction instantly.
So generally working but a small glitch seems still to be in.

@Lineflyer What I can tell it is just very noisy input from the watch compass which causes those sudden jumps.

It works now fine for me. The compaas is not accurate all the time but it works. If the smartwatch has a GPS receiver, do the app use it?

I can confirm that this issue also affects the LG Watch Urbane and is also fixed with gittiku's solution. Has anyone made a pull request for that change to be added to the master branch?

Hi guys,
I tested the version from @gittiku and the compass works fine on the sony smartwatch 3. I have some ideas to improve the app (e.g. like using the watches gps, maybe store some caches directly on the watch, etc) and also dwonloaded  the zip file nut unfortunately I am not able to build it with android studio :-(
Maybe someone could help me getting started?
Btw. is there any chance to dend private messages in github?


Undo/redo causes error with columns

What happened
Removing a column and undoing the removal causes the error

Cannot read properties of undefined (reading 'span')

What I expected to happen
The column to be restored
Steps to reproduce

Visit demo app
Add a Columns component
Remove a column
Undo the change

Notes

Reported in Discord
Still occurs in #283

Closing as unable to reproduce in 0.13.0.


How would you implement RAG / Document chat?

In your readme you mention:

Maybe doing a full RAG-in-browser example using tinyllama?

I've been looking into a way to allow users to 'chat with their documents'. A popular concept. Specifically I was looking into 'Fully local PDF chatbot'. It seems.. complicated.
So I was wondering: if one wanted to implement this feature using Wllama, what are the 'components' of such a solution?
Would it be something like...

Wllama's embedding feature turns text chunks into vector objects?
Those could then be stored in Voy?
magic
magic
The user gets an answer to their question, e.g. "The sun is 2948520 degrees, which I found on page 16"?

What would the steps actually be?

A classic RAG system consist of a vector database + a generative model. With wllama, this can be archived by:

Embedding model. However, I still couldn't find a good embedding model.
For database, we can use Voy as you mentioned, or HNWS which is a pure JS implementation (we don't need to much performance on this part, our database is relatively small anyway)
A good generative model that does not hallucinate. This is very important and requires using specific model, for example Llama3-ChatQA-1.5-8B by nvidia. These models are generally "dumb" or "stupid", but will be safe because they don't make up information if it is not found in our RAG

Another idea that is only possible if your document is short and predefined, is to construct a session and reuse it later (via sessionSave and sessionLoad) - This is useful in my case for example, if the chatbot is purely to introduce a specific website, we don't even need to make a vector database or to have embeddings at all. The downside is that this is not practical for any other usages.

For a small embedding model good for this case, I can recommend this one:
sentence-transformers/multi-qa-MiniLM-L6-cos-v1 (GGUF)

Getting there...

Currently using:
extractor = await pipeline('feature-extraction', 'Xenova/all-MiniLM-L6-v2', {
			quantized: false,
			progress_callback: data => {
				self.postMessage({
					type: 'embedding_progress',
					data
				});
			}

        });

		embeddings =  await extractor(texts, { pooling: 'mean', normalize: true });

I've alse seen mention of this model for embedding: nomic-ai/nomic-embed-text-v1? But for now.. it works.
Next: get an LLM to summarize the chunks.

Ah nice. I tried nomic-embed-text before but it doesn't work very well. But maybe because I used Albert Einstein wiki page as the example, which is a very hard one.
Maybe you can give it a try?
Some questions that I tried but no success:

Does he play guitar?
Does he have a child?
How many wives does he have?

Some questions that I tried but no success:
Does he play guitar?

Did you let the LLM re-formulate the prompt first? In my project I just added the step to do that by looking at the conversation history first and rewriting the user's prompt to be explicit. So "he" becomes "Albert Einstein. It seems to work.
In fact it's all now working. Although the answer in this case seems almost too good to be solely based on the retrieved chunks..


Disabled Word export tool after implementing Input Form?

I need to export the cal pad output to word so I can get MathTtpe equations. The program was exporting the document to word but, at some point stop doing it. Now, when I export to Word, I just get a blank (empty) word file. Would be possible that implementing the Input forms created this issue? If so, how can I go back and remove the input form? Thank you

Hi!
If you have broken Html inside, it may cause the problem. Maybe if you post your code, or part of it that do not export, we can provide more specific recomendations.

Got it, I'll debug it and look for the broken html. It's an extensive document so, I don't think it makes sense for me to upload. Btw, and FYI, I tried to copy and paste the code to another instance of calcpad (for creating a new version of the code for backup) and the new instance crashed. I think I need to do it piece by piece. Anyway, it's an outstanding software. I'm using it for my academic documents. It's like Jupyter Notes, but I like it more. Thank you for developing this for our community.

Hello-
One of the problems seems to be the hyperlink. I cleaned up the attached file.
Example_debugging.txt

Hi!
Please, note that Calcpad puts automatically each line in a separate paragraph unless it find that the lines starts with an Html tag. Otherwise you will not be able to create other block level elements like tables, divs, etc. In order to be compatible with Word, inline elements like spans, links, u, i, b must be inside a block level one - e.g. paragraph or table cell.
So, you have to manually add paragraphs, when you start the line with an inline element. For example:
"Example 1 - Two Span Bridgeshould become"Example 1 - Two Span Bridge`
and
'Google should become:
'
Google

Also, you can start a paragraph on one line and close it on another line if all lines start with a tag:
'
Example Seismic Design

'Example 1 - Two Span Bridge

Yes, that makes sense. I need to add the p-element before each in-line element. Thank you,


I'd like to run the test found in tests, how is it possible?

Run this inside your shell at the repo root folder:
npm test

Thx!


RHBPMS-75: Complete i18n of simulation tab

Note that RHBPMS-75 has been approved to go into 6.4.x

+1


Refactor type hierarchy

Now already looking at quite a few abstract types. It may be more useful to reduce the use of that and instead rely on THTT.

Addressed in #21
@ablaom is this what you had in mind? Instead of ConformalSet <: MMI.Supervised we'd ideally have ConformalSet <: MMI.Set` in the future.

Yeah, mostly:

At present Interval is a subtype of Supervised.
I don't see a need for a separate ConformalInterval <: Interval subtype in MLJModelInterface. If it were useful to you, that could live in ConformalPrediction.jl, no?
I would make make Set and ProbababilisticSet subtypes of Supervised.

In other words, we currently have
Probabilistic <: Supervised
Deterministic <: Supervised
Interval <: Supervised

and I would propose extending this with
Set <: Supervised # if you think you even need this
ProbabilisticSet <: Supervised

(In the new LearnAPI.jl, we would add two target proxy types, Set and ProbabilisticSet. These are possible values of a trait target_proxy and there would be no need to restrict to supervised models,  but that's another story...)

Would that work for you?

Hi Anthony! Yes, absolutely that works. In fact, that's what I had in mind and also reflect the way things are currently implemented (I think the diagram needs some clarification perhaps).
Also, good point ProbabilisticSet <: Supervised, have added a placeholder for this now in #26. To be clear, at this point we have the following:
"An abstract base type for conformal models that produce interval-valued predictions. This includes most conformal regression models."
abstract type ConformalInterval <: MMI.Interval end

"An abstract base type for conformal models that produce set-valued deterministic predictions. This includes most conformal classification models."
abstract type ConformalSet <: MMI.Supervised end                    # ideally we'd have MMI.Set

"An abstract base type for conformal models that produce set-valued probabilistic predictions. This includes most conformal classification models."
abstract type ConformalProbabilisticSet <: MMI.Supervised end       # ideally we'd have MMI.ProbabilisticSet

"An abstract base type for conformal models that produce probabilistic predictions. This includes some conformal classifier like Venn-ABERS."
abstract type ConformalProbabilistic <: MMI.Probabilistic end

For set-valued predictions, I am at this point still just subtyping <: MMI.Supervised, since the specific types still need to be added to LearnAPI.jl. In particular, for conformal models of type ConformalSet currently produce prediction of type UnivariateFinite (linking our related discussion on discourse).
I will close this issue now and open a new one related to set-valued predictions specifically.
Thanks!

Yes, this sound good.
To clarify, MLJModelInterface.jl remains the home for MLJ's basement-level model interface. I just mention LearnAPI.jl because that is where I hope to move to later.
So should add two new abstract types to MLJModelInterface: Set <: Supervised and ProbabilisticSet <: Supervised. We already have Interval <: Supervised. Would you be willing to make the PR?

Thanks @ablaom 👍🏽
Yes, I'll make the PR as soon as I can (have a few commitments these next two weeks, but will get to it eventually 😅)


[MXNet] - [BERT]

There is a problem with a custom BERT model training with the later version of MXNet 1.5.0 (observed with cu90).
mlm_loss stops around 7.2X and nsp_acc stopps around 54.
The last mxnet-cu90 version is still viable is 1.5.0b20190425.
1.5.0b20190426 onward has this issue. Thus, you cannot train a custom BERT model with the latest version of MXNet now.
I assume there was a change in optimization between April 25th and 26th.
I used the latest version of gluonnlp for the following test. I think it is not the problem with gluonnlp (0.6.0).
(i.e. pip install https://github.com/dmlc/gluon-nlp/tarball/master )
With mxnet-cu90==1.5.0b20190425 (This is working)
(mxnet_p36_updated_4) sh-4.2$ python run_pretraining.py --gpus 0,1,2,3,4,5,6,7 --batch_size 8 --lr 1e-3 --data "out_mcg_test-big/part-001.npz"  @--warmup_ratio 0.01 --num_steps 1000000 --log_interval=250 --data_eval "out_mcg_test-big/part-001.npz" --batch_size_eval 8 --ckpt_dir ckpt --ckpt_interval 25000 --accumulate 4 --num_buckets 10 --dtype float16
INFO:root:Namespace(accumulate=4, batch_size=8, batch_size_eval=8, by_token=False, ckpt_dir='ckpt', ckpt_interval=25000, data='out_mcg_test-big/part-001.npz', data_eval='out_mcg_test-big/part-001.npz', dataset_name='book_corpus_wiki_en_uncased',dtype='float16', eval_only=False, gpus='0,1,2,3,4,5,6,7', kvstore='device', log_interval=250, lr=0.001, model='bert_12_768_12', num_buckets=10, num_steps=1000000, pretrained=False, profile=False, seed=0, start_step=0, verbose=False, warmup_ratio=0.01)
INFO:root:Using training data at out_mcg_test-big/part-001.npz
[20:42:24] src/kvstore/././comm_tree.h:356: only 32 out of 56 GPU pairs are enabled direct access. It may affect the performance. You can set MXNET_ENABLE_GPU_P2P=0 to turn it off
[20:42:24] src/kvstore/././comm_tree.h:365: .vvvv...
[20:42:24] src/kvstore/././comm_tree.h:365: v.vv.v..
[20:42:24] src/kvstore/././comm_tree.h:365: vv.v..v.
[20:42:24] src/kvstore/././comm_tree.h:365: vvv....v
...
[20:42:24] src/kvstore/./././gpu_topology.h:216: cudaDeviceGetP2PAttribute incorrect. Falling back to cudaDeviceEnablePeerAccess for topology detection
[20:42:24] src/kvstore/././comm_tree.h:380: Using Kernighan-Lin to generate trees
[20:42:24] src/kvstore/././comm_tree.h:391: Using Tree
[20:42:25] src/kvstore/././comm_tree.h:488: Size 2 occurs 1 times
[20:42:25] src/kvstore/././comm_tree.h:488: Size 768 occurs 114 times
[20:42:25] src/kvstore/././comm_tree.h:488: Size 1536 occurs 2 times
[20:42:25] src/kvstore/././comm_tree.h:488: Size 3072 occurs 12 times
[20:42:25] src/kvstore/././comm_tree.h:488: Size 30522 occurs 1 times
[20:42:25] src/kvstore/././comm_tree.h:488: Size 393216 occurs 1 times
[20:42:25] src/kvstore/././comm_tree.h:488: Size 589824 occurs 50 times
[20:42:25] src/kvstore/././comm_tree.h:488: Size 2359296 occurs 24 times
[20:42:25] src/kvstore/././comm_tree.h:488: Size 23440896 occurs 1 times
INFO:root:[step 249] mlm_loss=8.02087 mlm_acc=6.88167 nsp_loss=0.69021 nsp_acc=53.343 throughput=24.2K tks/s lr=0.0000249 time=315.28
INFO:root:[step 499] mlm_loss=6.85134 mlm_acc=11.51758 nsp_loss=0.65648 nsp_acc=60.298 throughput=57.7K tks/s lr=0.0000499 time=133.49
INFO:root:[step 749] mlm_loss=6.60548 mlm_acc=13.98383 nsp_loss=0.58539 nsp_acc=67.169 throughput=57.7K tks/s lr=0.0000749 time=133.54

With mxnet-cu90==1.5.0b20190426 (This is not working)
#(Same)#
INFO:root:[step 249]    mlm_loss=nan    mlm_acc=4.56305 nsp_loss=nan    nsp_acc=54.454  throughput=23.7K tks/s  lr=0.0000249 time=321.78
INFO:root:[step 499]    mlm_loss=7.27492        mlm_acc=5.76089 nsp_loss=0.68847        nsp_acc=54.719  throughput=57.4K tks/s     lr=0.0000499 time=134.22
INFO:root:[step 749]    mlm_loss=7.26470        mlm_acc=5.82224 nsp_loss=0.68894        nsp_acc=54.428  throughput=57.3K tks/s     lr=0.0000749 time=134.40

https://github.com/apache/incubator-mxnet/issues/14864

I used run_pretraining.py from...
http://gluon-nlp.mxnet.io/_downloads/bert.zip

I believe this is the same issue I've been seeing, bisected to apache/incubator-mxnet@369b66d0f from apache/incubator-mxnet#14785

@tlby thanks reporting. Was your issue also about running the pre-training script?

I was testing with the finetuning example.  It looks like MXNet reverted the PR in question so I think things are good now.

@tlby thanks!
BTW - I'm adding some enhancements to the finetuning script in https://github.com/dmlc/gluon-nlp/pull/692 feel free to comment on it

@eric-haibin-lin @tlby I'm trying to fix the trouble PR in MXNet, but failed to setup the bert example to reproduce the regression. The reported command line doesn't work for me, because out_mcg_test-big/part-001.npz not found.  I didn't try gluon-nlp bert before, may I know the minimal command lines to reproduce this issue on top of MXNet and gluon-nlp only? Thanks in advance.

@ZhennanQin are you able to reproduce https://github.com/apache/incubator-mxnet/pull/14868 with
python run_pretraining.py --gpus 0 --batch_size 32 --lr 2e-5 --data 'out/*.npz' --warmup_ratio 0.5 --num_steps 20 --pretrained --log_interval=2 --data_eval 'out/*.npz' --batch_size_eval 8 --ckpt_dir ckpt

from http://gluon-nlp.mxnet.io/model_zoo/bert/index.html#bert-pre-training ?

@eric-haibin-lin This command works. Thanks. The fixed PR is filed again at https://github.com/apache/incubator-mxnet/pull/14931, please take a look.


[BUG] Adding bracket in metadata parses as shoppingList

Describe the bug
Small issue, but if there is a [ in metadata, we parse a recipe as a shopping-list.
I see this as a minor bug, but want to double-check it's unexpected before I put in any work to make a fix.
To Reproduce
Steps to reproduce the behavior:
// can ignore import syntax; this is standard usage via Deno
import { Parser } from 'npm:@cooklang/cooklang-ts';

const parser = new Parser()

console.log(parser.parse(`
>> source: https://www.youtube.com/watch?v=oTyVtAAKPRo
>> tags: [ breakfast ]
>> description: It's scrambled egg, with kimchi, and miso soup
>> servings: 1

Crack @eggs{2} into a #bowl, and beat with chopsticks

Make @Kombu broth (or dashi)

Heat a #small pan{} to high heat with #cooking oil{}

Slowly stir eggs onto pan, cook for about ~{10-15%sec}, then remove and add @sesame oil{} and @kimchi

Stir @miso paste{} into kombu broth, and bring to boil

Pour the soup into the egg-stirring bowl, and top with chopped @scallions

`))

this will produce a result of:
{
  ingredients: [],
  cookwares: [],
  metadata: { source: "https://www.youtube.com/watch?v=oTyVtAAKPRo", tags: "" },
  steps: [],
  shoppingList: {
    " breakfast ": [
      {
        name: ">> description: It's scrambled egg, with kimchi, and miso soup",
        synonym: ""
      },
      { name: ">> servings: 1", synonym: "" }
    ]
  }
}

Expected behavior
Should parse as a recipe (with ingredients, cookwares, and steps instead of `shoppingList:
{
  ingredients: [
    { type: "ingredient", name: "eggs", quantity: 2, units: "" },
    { type: "ingredient", name: "Kombu", quantity: "some", units: "" },
    ...
    {
      type: "ingredient",
      name: "scallions",
      quantity: "some",
      units: ""
    }
  ],
  cookwares: [
    { type: "cookware", name: "bowl,", quantity: 1 },
    { type: "cookware", name: "small pan", quantity: 1 },
    { type: "cookware", name: "cooking oil", quantity: 1 }
  ],
  metadata: {
    source: "https://www.youtube.com/watch?v=oTyVtAAKPRo",
    tags: "[ breakfast ]",
    description: "It's scrambled egg, with kimchi, and miso soup",
    servings: "1"
  },
  shoppingList: {},
...
}

Fixed in b95cfd71c45cc83363aea287926445f3cea394ed.
Thanks for contributing!


Text inside TextArea goes over the placeholder

Your issue may already be reported!
Please search on the issue tracker before creating one.
Expected Behavior
Text should be padded somehow not to go over the placeholder when scrolled but rather always stay below it
Current Behavior
Text clips the upper boundary of text area and it just looks bad
Possible Solution

Steps to Reproduce (for bugs)

Hi there
Thanks for reporting that we will fix that on the next update of the product.
All the best
Sajad

This bug still exists in material-tailwind/react 2.1.9. I'm using MT with Next 14.1.0


UNIQUE_HASH_INDEX not being updated locally in asynchronous replication.

I have a three-node cluster (let's call the nodes n1, n2 and n3) and a graph database set to use executionMode equal to asynchronous. I have the following schema in-place:
CREATE CLASS Thing EXTENDS V
CREATE PROPERTY Thing.uuid STRING
ALTER PROPERTY Thing.uuid MANDATORY TRUE
ALTER PROPERTY Thing.uuid NOTNULL TRUE
CREATE INDEX Thing.uuid UNIQUE_HASH_INDEX

Now, I issue the following to n1 (using the console, but the same thing happens with the Java Graph API):
CREATE VERTEX Thing SET uuid = '2113de93-604a-4b98-a071-fec7a025f884'

If I SELECT FROM Thing now, all three nodes now report the existence of a Thing record with uuid equal to 2113de93-604a-4b98-a071-fec7a025f884 (as expected). However,
SELECT FROM INDEX:Thing.uuid WHERE key = '2113de93-604a-4b98-a071-fec7a025f884'

only returns the expected result in n2 and n3. n1 (the target node when writing) reports 0 item(s) found.. The same thing happens on n2 or n3 if the CREATE VERTEX is issued to any of these nodes. It does not happen if executionMode is set to undefined or synchronous.

@lvca where you aware of this?

What release are you using?

@lvca This affects 2.1.2 and 2.1.3 (at least).

Please could you try 2.1.5?

Fixed long time ago.


Bloom CI pipeline badge not working

Describe the bug
The Bloom CI pipeline on the Readme is broken.
To Reproduce
Steps to reproduce the behavior:

Go to Readme.md
Look at the badge for the CI pipeline.
You will see that there is no badge in the screen shot below.

Expected behavior
We should see the "passing" badge as expected on github Repositories.
Screenshots

Additional context

This bug is caused by the old pipeline being deleted. Instead we should be connecting to the deploy to staging pipeline.
See resource about badges

can i work on this?

can i work on this?

Yes thank you @Danishkar


add c++ binding

@cocoa-xu I have a refactored version in my branch(https://github.com/whyb/ruapu/commit/44d1925ac6d30b2dd2c9b982e832b775a0f177fb) When you have time, Please review codes.
NOTE:

change std::vector to std::list. Because it may inserted frequently.
when I convert C style string to C++ string, I suggest use std::string_view without making a copy of the string.
use std::unique_ptr without making a copy of the list object memory(transfer pointer ownership to outside).

@cocoa-xu I have a refactored version in my branch(whyb@44d1925) When you have time, Please review codes. NOTE:

change std::vector to std::list. Because it may inserted frequently.
when I convert C style string to C++ string, I suggest use std::string_view without making a copy of the string.
use std::unique_ptr without making a copy of the list object memory(transfer pointer ownership to outside).

Actually, I mean, the real question is that, do we real need a C++ version of ruapu while it's already available to all C++ users (as ruapu is written in C)? A C++ wrapper would only add complexity for using it.
And speaking of without making a copy, using ruapu's C API already satisfies this one.
    // loop all supported features
    const char* const* supported = ruapu_rua();
    while (*supported)
    {
        fprintf(stderr, "%s\n", *supported);
        supported++;
    }

I think we don't need any C++ "magic", if it can be done in C++, it surely can be done in C. Please kindly see and review the code in #83.

Okay, fine

ruapu implemented in C is naturally compatible with cpp, and cpp binding is unnecessary
Thanks anyway


Layer Bearer Token

In the Readme, it specifies using the LAYER_BEARER_TOKEN, but it's not entirely clear where can we find the LAYER_BEARER_TOKEN ? In the dashboard, there is a sample token under "Platform API", which I'm not sure is the same as the webhooks

The Platform API Token is used for both Platform API and Webhooks API.


Issues with polish

Hi!
I'm trying to walk through the isoseq3 pipeline. And on the polish step, I get empty fastq/fasta files.
Here is my pipeline:

ccs m*.subreads.bam ccs.bam --noPolish --minPasses 1 --numThreads 16

lima ccs.bam primer.fasta demux.ccs.bam --isoseq --no-pbi --dump-clips --min-passes 1 --min-length 100 --chunk-size 20 --num-threads 16

isoseq3 cluster demux.ccs.pr_5p--pr_3p.bam unpolished.bam -j 16 --split-bam 24

and for all splitted files I run
4. isoseq3 polish $file m*.subreads.bam ${file/unpolished/polished}.bam -j 8 -v;
There was no warning messages and errors. Also, polished..transcriptset.xml and polished..bam are not empty but do not contain any sequences. It does not show an additional info (with -v or --logFile or --log-level INFO options) only prints "0^M0" in the log for each file.
What could cause the problem? How to solve it?
Thank you!
Anastasia

Would you be willing to share an example privately to reproduce?

In my polish log file, a error had been reported：

|> 20180711 17:18:10.953 -|- ERROR      -|- ConsensusQualities -|- 0x2b9ba13af700|| -|- In Polish::ConsensusQualities(ai): negative inf in mutation testing: 'm54172_180419_112009/49676773/3858_7331'
However, isoSeq3 polish had finished.

This is a debug information from Arrow, not a real runtime error, please  ignore the message.

Anastasia sent me data to reproduce, I'll debug her case and then report back here.

Armin, thank you so much for your help! I did not have the .pbi index of my subread.bam, so a simple "pbindex m.subreads.bam" solved it. Everything works great now.
Thank you!
Anastasia

Great! The new isoseq3 version will warn you if there is no .pbi file present!


The attribute "id" does not exist on the type "string | Partial| StoragePro".  Attribute 'id' does not exist on type 'string'.

Temporary solution, e.g <{id:string}>store(info)?.id
Next version plan, e.g store<{id:string}>(info)?.id

Please upgrade to version 2.0.0


Optimize file delivery, cache-busting, offline support (CSS, JS)

Currently, we append a version modifier to the query string for our CSS and JS files where feasible. However, this approach is not ideal for several reasons. For instance, the automatically generated MyApp.styles.css files for CSS isolation do not include this version modifier. Additionally, there are problems related to offline mode in PWAs, as highlighted in issue #444, among other concerns.
In the Blazor roadmap, there's a promising feature under development titled 'Optimize file delivery', which could address these issues. More details can be found here: https://github.com/dotnet/aspnetcore/issues/52824.
We should monitor this development closely and integrate the solutions into our library as soon as they become available.

Resolved within Blazor in .NET 9.


Maintaining a site-specific profile in offline mode

Description of feature
Might be a broader nf-core issue, but thought I would start asking here.
We have a CMD-specific profile used when running Tomte, which is added to nextflow.config. This is currently maintained as a non-commited change in the repo. I.e.:
[jakob@rs-fe1 tomte]$ git diff nextflow.config
diff --git a/nextflow.config b/nextflow.config
index 025ca1b..1aee4bf 100644
--- a/nextflow.config
+++ b/nextflow.config
@@ -207,6 +207,7 @@ profiles {
     }
     test      { includeConfig 'conf/test.config'      }
     test_full { includeConfig 'conf/test_full.config' }
+    cmd       { includeConfig 'conf/cmd.config' }
 }

Furthermore, the conf/cmd.config file is also present as an untracked file in the repo.
[jakob@rs-fe1 tomte]$ git status
# On branch dev
# Changes not staged for commit:
#   (use "git add <file>..." to update what will be committed)
#   (use "git checkout -- <file>..." to discard changes in working directory)
#
#       modified:   nextflow.config
#
# Untracked files:
#   (use "git add <file>..." to include in what will be committed)
#
#       conf/cmd.config
no changes added to commit (use "git add" and/or "git commit -a")

I would like to find a solution where we don't need to git stash and git stash pop before and after each git pull 🤔 How do you guys deal with this?
There seems to be support for having custom configs, but this does not seem to be intended to work offline, looking at the following line in nextflow.config.
includeConfig !System.getenv('NXF_OFFLINE') && params.custom_config_base ? "${params.custom_config_base}/nfcore_custom.config" : "/dev/null"

Ah that sounds annoying :)
We have our configs in a separate github repository for version control. On updates of the configs we do sync to our hpc and then when running tomte we use the full path to that config. Something like this:
nextflow run path/to/tomte -config /path/to/our/config -params-file /path/to/params.yaml.
The reason being that we want to be able to update the config without having to do a new release of the pipeline.
If that doesn't work for you we can look into modifying that includeConfig statement to work offline. Or if you prefer to have the config coupled with the pipeline to have a folder in conf with the cmd config.


Error occured at runing test_lambda_local.sh

> ./test_lambda_local.sh                                                                                Traceback (most recent call last):
  File "/usr/local/bin/python-lambda-local", line 6, in <module>
    from lambda_local import main
  File "/usr/local/lib/python3.7/site-packages/lambda_local/__init__.py", line 12, in <module>
    from .main import run
  File "/usr/local/lib/python3.7/site-packages/lambda_local/main.py", line 25, in <module>
    urllib3.disable_warnings()
AttributeError: module 'botocore.vendored.requests.packages.urllib3' has no attribute 'disable_warnings'

I have the same error. How did you solve it, please?

I edited the file (/usr/local/lib/python3.7/site-packages/lambda_local/main.py) to import directly from urllib3 package (instead of from botocore.verdored.requests.packages).
However I understand that this is just a workaround, as it will fail again when I update the package (unless the issue is solved for the next version, of course).

Interesting, I am installing it like normal pip packages on Mac - pip install -r requirements.txt, or just one package from here - https://pypi.org/project/python-lambda-local/
$ python -V
Python 3.7.5

I think you have wrong versions of dependencies, but I am not sure which exactly.

I am experiencing the same issue. Has this been resolved?

It turned out this issue has been just fixed and merged - https://github.com/HDE/python-lambda-local/pull/55
Let's wait for a few hours/days to get it updated.

python-lambda-local has been updated to 0.1.9 where this issue is fixed.


Support Aggregate and Union on Rust

Depends on #375. Same acceptance criteria for the Aggregate and Union test model, therefore covering all Smithy aggregation types (https://smithy.io/2.0/spec/aggregate-types.html).

Closed by #549.


fix get metadata when set serve_on_root

@oklemenz2 , This PR is try to fix #9 , can you please check ?

I checked and it looks like an error in CDS core. The services are still exposed at default protocol path "/odata/v4", even serve_on_root is active. This should not be the case. So I would like to clarify this with the CDS core..

Close this,  and let's see discuss in #9


Do not save credentials on a Validate

Validate should only perform validation and should not save the credentials for an ems record.

@miq-bot add_label bug,providers

@miq-bot add_label darga/yes


Printing unwrapped tensors doesn't work under grad-type transform

Repro
x = torch.randn(3)
def f(y):
  print(x)
  return y
vjp(f, torch.randn(4)) # or equivalent with grad or jvp

Gets error:
RuntimeError: Cannot access data pointer of Tensor that doesn't have storage

Full Stacktrace
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/Users/samdow/Documents/jacfwd_fix/functorch/functorch/_src/eager_transforms.py", line 270, in vjp
    primals_out = func(*diff_primals)
  File "<stdin>", line 2, in f
  File "/Users/samdow/Documents/jacfwd_fix/torch/_tensor.py", line 423, in __repr__
    return torch._tensor_str._str(self, tensor_contents=tensor_contents)
  File "/Users/samdow/Documents/jacfwd_fix/functorch/functorch/_src/monkey_patching.py", line 23, in _functorch_str
    return _old_str(tensor)
  File "/Users/samdow/Documents/jacfwd_fix/torch/_tensor_str.py", line 594, in _str
    return _str_intern(self, tensor_contents=tensor_contents)
  File "/Users/samdow/Documents/jacfwd_fix/torch/_tensor_str.py", line 557, in _str_intern
    tensor_str = _tensor_str(self, indent)
  File "/Users/samdow/Documents/jacfwd_fix/torch/_tensor_str.py", line 320, in _tensor_str
    return _tensor_str_with_formatter(self, indent, summarize, formatter)
  File "/Users/samdow/Documents/jacfwd_fix/torch/_tensor_str.py", line 249, in _tensor_str_with_formatter
    return _vector_str(self, indent, summarize, formatter1, formatter2)
  File "/Users/samdow/Documents/jacfwd_fix/torch/_tensor_str.py", line 230, in _vector_str
    data = [_val_formatter(val) for val in self.tolist()]
RuntimeError: Cannot access data pointer of Tensor that doesn't have storage

What we think is happening
There's some monkey patching to make printing work. We think that since the transform is still on, whatever functions normal printing calls are getting wrapped in tensor wrappers that don't have storage
Potential Solutions
An option could be to turn off all the transforms while printing (or even when just printing an unwrapped tensor)

I'm surprised that no one has tried to do this until now

Fixed in https://github.com/pytorch/pytorch/pull/85556


minor doc change to reflect the current filename

minor doc change to reflect the current filename
Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

It will help us expedite review of your Pull Request if you tag someone (e.g. @username) to look at it.
Post-Commit Tests Status (on master branch)

Lang
SDK
Apex
Dataflow
Flink
Gearpump
Samza
Spark

Go

---
---
---
---
---
---

Java

Python

---

---
---
---

run website precommit

Website pre-commits are failing due to BEAM-5681; I'm working on a fix now; sorry for the noise.

Links check is failing because of https://issues.apache.org/jira/browse/BEAM-5681


error when exec'ing a command with no tty

Due to the way container tty access is currently wired in podman, we
must have a tty available where the user executes podman.  Failure to
do so results in a hard podman lock where no container related commands
can be run.
When we can leverage conmon for console handling, this requirement can
be removed.


Backend/Add missing category

Adding missing category. Not sure if we have a description somewhere @agnessa ?
Test snapshot was weird, but ids are normally IGNORED and not compared, so it worked ;]
Testing instructions
api docs
Tracking
No tracking

we don't have the description yet

We can add description in another PR.


Add SUSPENDED in models.py on ./iambic/plugins/v0_1_0/google_workspace

What changed?

Added another status in class GroupMemberStatus.

Rationale

With this change we can avoid the error: "ValueError: 'SUSPENDED' is not a valid GroupMemberStatus" when trying to setup IAMbic with Google.

How was it tested?
If it was manually verified, list the instructions for your reviewers to follow.

[ ] Unit Tests
[ ] Functional Tests
[X] Manually Verified

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.victorsouzamobi seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.

I've verified victorSouza-DevOPS has signed the CLA on Jul 4, 2023 1:40:56 PM on https://cla-assistant.io.
Thanks for contributing the PR.


Fix getting the directory path on Mac OS X.

With love from PyconUK 2017 sprints!

Thanks! Good luck with playing with the library. Sorry I'm busy with commercial stuff this week, but if you spam tickets I'll reply in the coming days. :)


KSTREAMS-4026: Fix type parameter bounds of ProcessorContext in Scala

The AK PR https://github.com/apache/kafka/pull/8414 introduced type parameters
for the ProcessorContext. Since Scala requires generic arguments for any
type that takes generic parameters, the Scala code in the examples that uses
the ProcessorContext did not compile anymore.

Does this expose an unexpected backward incompatibility?  \cc @vvcephei

According to https://github.com/apache/kafka/pull/8414#issuecomment-608644050 it is not unexpected.

Thanks for the reference. Not sure how to proceed...

Thanks, all. I'm not sure how to proceed either. Let's resume the discussion here:

Hmm, that last commit illustrates a problem with this approach. Adding generics to a previously raw type is only a compiler warning for Java users, but it's a compiler error for Scala users, because Scala insists on having the generic arguments for any type that takes generic parameters.
I think the way to fix this is to propose to add a new ProcessorContext as well as a new Processor interface. Or we can accept this level of source code incompatibility in the Scala API. For context, many changes we've made in minor versions break Scala source compatibility, since Scala generally makes it harder for libraries to implement non-breaking deprecation paths.

Clearly, the choice I made before is that it's ok to break in this way, but maybe now it seems "a little too real". Should we instead take the alternative approach I proposed?

I don't know Scala very well. But if you can fit it in the Scala API, it seems reasonable to me?

We can't fit it into the Scala API because these are types from the Java API. My alternative proposal was to create a brand new Java ProcessorContext, similar to how we are going to create a brand-new Processor. Basically, we leave ProessorContext untouched and replace it with a generically-typed one.

Not sure if I can follow: are you saying we would need to revert the AK PR that added generics?

Yes, we'd revert that change and add a new ProcessorContext with generics, and then deprecate the old one. The thing I don't like about that is that the scope of deprecating ProcessorContext is much larger than the scope of deprecating the Processor interface, since ProcessorContext is exposed even to DSL users in a number of places, such as Transformers.
I guess a middle ground is to introduce the new ProcessorContext without deprecating the old one, to limit the splash damage, while still supporting both backward compatibility and the change we want to make.

Hey, @cadonna @mjsax ,
I'd like to propose this approach instead:
It seems like supporting backward compatibility and supporting cross-language usage are both feasible, but supporting backward compatibility WITH cross-language usage is potentially too much to ask.
I'd be more inclined just to hand-wave this particular breakage if we could say with confidence that it won't happen again. But I'm not sure we can say that. What would help is to create a "pure" Scala API. In other words, we would not leak any objects from the Java API through to the Scala API, so we'd have a Scala ProcessorContext, Scala Transformer, etc., etc. This would let us explicitly manage the APIs' backward-compatibility properties independently.
For example, in this case, we would already have had a Scala ProcessorContext (with no generics) that adapts the Java one. We would have had to update the Scala ProcessorContext implementation to cope with the new generics, but wouldn't add the generics to the Scala ProcessorContext interface.
Shoring up the Java interfaces that already leak through to the Scala API would itself be a breaking change, although we would be able to transition most of the usages via deprecation. However, even though we'd still break ProcessorContext usages under this plan, it comes with a promise that we stand a better chance of avoiding such breakage in the future. Essentially, we'd be admitting we made a mistake in the API design, and that we have to break compatibility to some extent to fix the mistake.
Specifically, if you feel ok with this plan, I'd make a 2.6 blocker to do what I said above, and then we would proceed to merge this PR.

@vvcephei IMO it would be indeed more robust to have a dedicated Scala API that does not leak the Java API. The only concern that I have is that if we now merge this PR (and do not revert the other), we must complete the Scala API for the 2.6 release. Are we confident to get that done? Or are you saying we just accept this specific breakage in any case?

Thanks for the reply, @cadonna .
Yes, just to be clear, this particular usage would break in any case. The “full Scala API” plan is just to soften the blow. I’d be willing to commit to it for 2.6 if that lets us make progress here.

Not sure how much work this would be? Maybe @apurvam has some thoughts on this, too, with regard to planning?

Just to clarify the context here, in https://cwiki.apache.org/confluence/display/KAFKA/KIP-478+-+Strongly+typed+Processor+API the only "in-place change" we proposed is ProcessorContext, while for all others we are introducing as either new classes or new APIs. So does this mean the only issue we are having is for ProcessorContext, and with this "full Scala Api" work, the only fix would be for ProcessorContext while others are actually okay to still get the (new, strong-typed) Java object leaked into it. Is that right?

Yes, that's correct, @guozhangwang . The other thing I can do is investigate how much of an impact it would be to back out this change and instead introduce a new (typed) ProcessorContext.

For some more context, I just talked with a community user of the scala API, and he indicated that he would be satisfied with the breakage, since it improves the type safety of the system. Adding a "shielding" layer to prevent Java types from leaking through the Scala interface also struck him as a really good idea.
On the other hand, he said that he only has a handful of references to ProcessorContext, so if he were a heavy user of PAPI, he might feel differently.
Of course, it's just one data point.

If the extra amount of work of maintaining this shielding in the Scala interface is not huge, I'm +1 for it :) Just want to make sure we are not unconsciously committing to a huge maintenance overhead moving forward.

I think it won't be immediately necessary now that I'm backtracking on the ProcessorContext change, but the shielding would still do more good than harm in the long run. Specifically, maintaining it would be some amount of work, but the nature of the work should be pretty straightforward compared to tracking down and repairing unintentional breaking API changes, like the one that this PR is for.
But we can defer that work for a later day, or even implement it in stages.

Hey @cadonna , I've just reverted the upstream change, so this PR should no longer be necessary. Sorry for the trouble.
cf https://github.com/apache/kafka/pull/8595