Scalable subsciptions proposal

I saw the PR for the Websockets subscription support but from what i can see there is not code or plan for how they are going to be managed.
NATS is a golang highly horizontally scalable solution. 500k to 800 k concurrent on just a decent laptop is possible. Its fast.
SO this looks promising.
https://github.com/cdmbase/graphql-nats-subscriptions
TO be honest i am not sure of the logic required to make a query subscription work. I am used to use  REST and letting the user opt to subscribe to a REST endpoint. The endpoint you subscribe to is a ViewModel ( like graphql in a way). So with a event sourced system when a mutation comes in, the commands run and Read only ViewModels / Materialised views get updated and the events that updated the View model are PUSHED back to the Client, and so he can simple update hsi cached copy or react in whatever way he needs. 99% of the time he just makes the exact same change to his ViewModel.  Its cheap to have viewModels. You can even run it off triggers in a Database that support Materialised VIews ( but i would not do that )
Its important to stress that the Client needs no flux pattern or anything in this architecture.
For the graphql world i am not sure how the mutation of the logic.... If anyone know i would love to get educated...

Subscriptions are already working well 😅

@DenisNeustroev i do agree. Chat app has it in the schema and is using only demonstrating a single query structure.

I would argue that cross-server distribution should not be part of this project, and the library should just enable the app to do that however it sees fit. Less bloat and dependencies is good, and one size fits nobody.
The glue between your Subscription_* and NATS should be really simple.

It sounds like whats really needed here is a good example of using gqlgen and NATS (or some other message bus).

There isn't anything that can be actioned on here, use https://gitter.im/gqlgen/Lobby for discussion


the difference of your idea and UDLOD

i know its clipmap based but it uses quad tree and looks similar to yours
https://dl.gi.de/bitstreams/cf03f446-82fe-424f-a289-118f624a0fae/download

Hi there!
Thanks for sending me this I will read that and I will tell my Idea about that!


Refactor get_key and Key

This patch refactors get_key and Key to make it easier to use:

tags is changed from an Optional[list[str]] to a list[str] that is empty if no tags are set.
modulus, public_exponent and data are moved into the RsaPublicKey and EcPublicKey dataclasses so that only the fields for the selected key type are used.

Fixes: https://github.com/Nitrokey/nethsm-sdk-py/issues/88

The test cases should be expanded to also cover EC and Generic keys.

→ https://github.com/Nitrokey/nethsm-sdk-py/issues/100


Service domain on supercluster cannot be resolved

$ oc run netshoot-cl-a-new -n test-submariner --image nicolaka/netshoot --pod-running-timeout=5m --restart=Never -- sleep 5m
pod/netshoot-cl-a-new created

$ oc describe svc nginx-cl-b -n test-submariner-cl-b-new
Name:              nginx-cl-b
Namespace:         test-submariner-cl-b-new
Labels:            app=nginx-cl-b
Annotations:       submariner.io/globalIp: <IP_ADDRESS>
Selector:          app=nginx-cl-b
Type:              ClusterIP
IP:                <IP_ADDRESS>
Port:              <unset>  8080/TCP
TargetPort:        8080/TCP
Endpoints:         <IP_ADDRESS>:8080
Session Affinity:  None
Events:            <none>

# Domain nginx-cl-b.test-submariner-cl-b-new can be resolved:

$ oc exec netshoot-cl-a-new -n test-submariner -- ping -c 1 nginx-cl-b.test-submariner-cl-b-new
PING nginx-cl-b.test-submariner-cl-b-new.svc.cluster.local (<IP_ADDRESS>) 56(84) bytes of data.
From <IP_ADDRESS> (<IP_ADDRESS>) icmp_seq=1 Destination Host Unreachable

--- nginx-cl-b.test-submariner-cl-b-new.svc.cluster.local ping statistics ---
1 packets transmitted, 0 received, +1 errors, 100% packet loss, time 0ms

# Domain nginx-cl-b on local cluster also resolves:

$ oc exec netshoot-cl-a-new -n test-submariner -- ping -c 1 nginx-cl-b.test-submariner-cl-b-new.svc.cluster.local
PING nginx-cl-b.test-submariner-cl-b-new.svc.cluster.local (<IP_ADDRESS>) 56(84) bytes of data.
From <IP_ADDRESS> (<IP_ADDRESS>) icmp_seq=1 Destination Host Unreachable

--- nginx-cl-b.test-submariner-cl-b-new.svc.cluster.local ping statistics ---
1 packets transmitted, 0 received, +1 errors, 100% packet loss, time 0ms

# But domain nginx-cl-b on super cluster cannot be resolved:

$ oc exec netshoot-cl-a-new -n test-submariner -- ping -c 1 nginx-cl-b.test-submariner-cl-b-new.svc.supercluster.local
ping: nginx-cl-b.test-submariner-cl-b-new.svc.supercluster.local: Name does not resolve

@manosnoam can you provide the logs of the lighthouse-agents?
Also, please check this:https://submariner-io.github.io/quickstart/openshift/service_discovery/#verify-deployment
Now you need to create a service export object to have a service exposed on other clusters:
kubectl -n default apply -f - <<EOF
apiVersion: lighthouse.submariner.io/v2alpha1
kind: ServiceExport
metadata:
  name: nginx-demo
EOF

after creating the regular service as usual.
Btw, that's all verified by subctl verify.

@mangelajo Thanks for the info. The env has already been destroyed, will retry with the new ServiceExport creation in advanced.
@vthapar , is it already documented ?
Also, should I add ServiceExport with {service name}.{namespace} as:
kubectl -n default apply -f - <<EOF
apiVersion: lighthouse.submariner.io/v2alpha1
kind: ServiceExport
metadata:
  name: {service name}.{namespace}
EOF

No not the {namespace} part, but you should create the Service export in
the same namespace, so if it's not default
use
kubectl -n {namespace} apply -f - <<EOF
apiVersion: lighthouse.submariner.io/v2alpha1

kind: ServiceExport
metadata:
  name: {service name}

EOF

On Tue, Jun 9, 2020 at 11:52 AM Noam Manos<EMAIL_ADDRESS>wrote:

@mangelajo https://github.com/mangelajo Thanks for the info. The env
has already been destroyed, will retry with the new ServiceExport creation
in advanced.
@vthapar https://github.com/vthapar , is it already documented ?
Also, should I add ServiceExport with {service name}.{namespace} as:
kubectl -n default apply -f - <<EOF
apiVersion: lighthouse.submariner.io/v2alpha1
kind: ServiceExport
metadata:
name: {service name}.{namespace}
EOF
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/submariner-io/submariner/issues/627#issuecomment-641176124,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAI7G4X2WUAWCNU3A5ZCDBLRVYA5ZANCNFSM4NXLCM6A
.

--
Miguel Ángel Ajo  @mangel_ajo https://twitter.com/mangel_ajo
OpenShift / Kubernetes / Network Federation team.
OSP / Networking DFG, OVN Squad Engineering

Thanks, is there a way to wait for the ServiceExport to be ready, like:
kubectl wait ServiceExport {service name} --for condition=available

After creating the ServiceExport:
oc describe serviceexport.lighthouse.submariner.io/nginx-cl-b -n test-submariner-cl-b-new
Name:         nginx-cl-b
Namespace:    test-submariner-cl-b-new
Labels:       <none>
Annotations:  kubectl.kubernetes.io/last-applied-configuration:
                {"apiVersion":"lighthouse.submariner.io/v2alpha1","kind":"ServiceExport","metadata":{"annotations":{},"name":"nginx-cl-b","namespace":"tes...
API Version:  lighthouse.submariner.io/v2alpha1
Kind:         ServiceExport
Metadata:
  Creation Timestamp:  2020-06-09T11:42:11Z
  Generation:          1
  Resource Version:    85079
  Self Link:           /apis/lighthouse.submariner.io/v2alpha1/namespaces/test-submariner-cl-b-new/serviceexports/nginx-cl-b
  UID:                 56d5c3ff-109e-423c-a57d-aa653afa39e0
Events:                <none>

I tried to check status with "wait", but it failed on timeout:
$ oc wait "serviceexport.lighthouse.submariner.io/nginx-cl-b" --for condition=available -n test-submariner-cl-b-new
And with "rollout" it also failed, since ServiceExport is not registered:
$ oc rollout status "serviceexport.lighthouse.submariner.io/nginx-cl-b" -n test-submariner-cl-b-new
error: no kind "ServiceExport" is registered for version "lighthouse.submariner.io/v2alpha1" in scheme "k8s.io/kubernetes/pkg/kubectl/scheme/scheme.go:28"

Yeah, according to U/S specification we should probably implement the status field of ServiceExport ^ @vthapar

Yeah, according to U/S specification we should probably implement the status field of ServiceExport ^ @vthapar

Yes, that is in plans for later. To support status on ServiceExport we need some more work in the Admiral framework. As of today we have no callback mechanism for when an object is synced. Even then, it will not be possible to 100% confirm if service is not imported correctly to all other clusters or not.

https://github.com/submariner-io/submariner-website/pull/177

Hi @vthapar, I tried to run same scenario, after cleaning Lighthouse ServiceExport DNS list:
$ oc apply -f - <<EOF
  apiVersion: operator.openshift.io/v1
  kind: DNS
  metadata:
    finalizers:
    - dns.operator.openshift.io/dns-controller
    name: default
  spec:
    servers: []
EOF

dns.operator.openshift.io/default configured

^ This was executed on Cluster B only, since Cluster A was completely destroyed and created again.
Then, trying to reach the ngnix service (which got a GlobalNet IP), has failed:
$ oc exec netshoot-cl-a-new -n test-submariner -- ping -c 1 nginx-cl-b.test-submariner-cl-b-new.svc.supercluster.local
PING nginx-cl-b.test-submariner-cl-b-new.svc.supercluster.local (<IP_ADDRESS>) 56(84) bytes of data.

$ oc exec netshoot-cl-a-new -n test-submariner -- /bin/bash -c "curl --max-time 30 --verbose nginx-cl-b.test-submariner-cl-b-new.svc.supercluster.local:8080"
   % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                  Dload  Upload   Total   Spent    Left  Speed

  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
  0     0    0     0    0     0      0      0 --:--:--  0:00:01 --:--:--     0
  0     0    0     0    0     0      0      0 --:--:--  0:00:02 --:--:--     0
  0     0    0     0    0     0      0      0 --:--:--  0:00:03 --:--:--     0
  0     0    0     0    0     0      0      0 --:--:--  0:00:04 --:--:--     0*   Trying <IP_ADDRESS>:8080...

  0     0    0     0    0     0      0      0 --:--:--  0:00:06 --:--:--     0
  0     0    0     0    0     0      0      0 --:--:--  0:00:07 --:--:--     0*
connect to <IP_ADDRESS> port 8080 failed: Host is unreachable

Full test report:
https://qe-jenkins-csb-skynet.cloud.paas.psi.redhat.com/job/Submariner-OSP-AWS/555/Test-Report/

Works on 0.5.0


How to synchronize mouse actions between two NGL stages?

I created two NGL stage objects :
var stage1 = new NGL.Stage( "viewport1", {backgroundColor: "white"});
var stage2 = new NGL.Stage( "viewport2", {backgroundColor: "white"});

I want the mouse operations of the two stages to be synchronized, that is, when rotating or moving the molecule of one stage, the other stage performs the same action. At present, I have implemented the scrolled action.
stage1.mouseObserver.signals.scrolled.add(function (delta) {
    console.log('scrolled', delta);
    stage2.mouseBehavior._onScroll(delta);
});

But other mouse actions are invalid. i.e. dragged.
stage1.mouseObserver.signals.dragged.add(function (deltaX, deltaY) {
    console.log('dragged', deltaX, deltaY);
    stage2.mouseBehavior._onDrag(deltaX, deltaY);
});

How can I solve this problem? Thank you very much.

I've already solved the problem.
For scrolled action:
stage1.mouseObserver.signals.scrolled.add(function (delta) {
    stage2.mouseBehavior._onScroll(delta);
});

For click:
stage1.signals.clicked.add(function (pickingProxy) {
    stage2.animationControls.move(pickingProxy.position.clone());
});


Android Splash Screen Incorrectly Sized

ITS-PRO: MA-34
The splash screen on Samsung Galaxy S7 is not correctly sized.
This is done when:

[ ] Splash screens correctly sized on Android

The dpi range I can test on using android emulator is 420dpi - 560dpi.
Works on:
Pixel 2 API 30 is 108 x 1920: 420dpi.
Pixel 4 API 30 is 1080 x 2280: 440dpi.
Pixel 5 API 30 is 1080 x 2030: 440dpi.
Pixel XL API 30 is 1440 x 2560: 560dpi
Does not work on:
Samsung Galaxy S7 is 1440 X 2560: 577dpi.

Deferred until the next platform upgrade


CAPTCHA

Description

Currently only a static image is displayed in the place of captcha
Find ways to generate real captcha and match it with user input.
Discover React libraries to implement captcha Feature.
The randomly generated captcha image being similar to the current static image is preferred style-wise
However any new modifications in the generated image is allowed for consideration.

Screenshots

Captcha Image

Additional information
Make sure to read the CONTRIBUTING and SETUP docs before proceeding
Happy contributing. 💐
Star my other Repositories here

I would like to take up this.

Great! Assigning you right away

Hey after doing npm i I'm getting these errors. Could you help me out?

And when I tried to install those dependencies manually I got these.

Can you do npm i --force that might resolve.

Can you do npm i --force that might resolve?

Sorry, I'm still I'm getting these errors on npm start.
Here's the log:
Failed to compile.

Module not found: Error: Can't resolve '@progress/kendo-drawing' in 'D:\CODING\contributions\uemcrp\client\node_modules\@progress\kendo-react-pdf\dist\es'
ERROR in<EMAIL_ADDRESS>28:0-61
Module not found: Error: Can't resolve '@progress/kendo-drawing' in 'D:\CODING\contributions\uemcrp\client\node_modules\@progress\kendo-react-pdf\dist\es'

ERROR in<EMAIL_ADDRESS>32:0-55
Module not found: Error: Can't resolve '@progress/kendo-licensing' in 'D:\CODING\contributions\uemcrp\client\node_modules\@progress\kendo-react-pdf\dist\es'

ERROR in<EMAIL_ADDRESS>1:0-61
Module not found: Error: Can't resolve '@progress/kendo-drawing' in 'D:\CODING\contributions\uemcrp\client\node_modules\@progress\kendo-react-pdf\dist\es'

webpack compiled with 3 `errors`

I think this @progress\kendo-react-pdf might have some dependencies that it is not installing automatically. But when I'm trying to install them manually I'm getting stuck in a dependency loop.

Do one thing! Try commenting out this package, then try npm i.

Hey @isayakmondal! What is the status of the work

Hey, I'm sorry I couldn't make it work. I tried everything :(

Its alright. This issue will be open unless anyone solves it

assign it to me


Make pyshp and pyproj external dependencies

This is in response to Issue #230.
This patch makes pyshp and pyproj packages external dependencies.  It most removes shapefile.py and pyproj.py.  It still maintains import locations for pyproj and shapefile, so code such as from mpl_toolkits.basemap.shapefile import Reader should still work.
I have NOT tested this.  The unitesting in test.py does not make use of shapefiles, and I'm unsure if it will catch a problems with pyproj.  There very will could have been something that I've missed.  For the moment, this might need to go in a separate branch.
Installation will be a little harder due to the new dependencies.
src folder with PROJ4 has been left untouched.

Hmm, looks like the import of pyproj is still getting messed up somehow. The pyproj that becomes available is essentially empty, causing the attribute errors Travis is seeing.

Progress... but it looks like we have angered the py3k gods somehow. Nothing obvious to me at the moment.

From my local testing I think it is pyproj.  I tested this on Python 3.4.3.  I installed pyproj 1.9.3 and 1.9.4 and both produced two errors on the same tests (test_convert and test_results_should_be_same_for_c_and_f_order_arrays).
test_results_should_be_same_for_c_and_f_order_arrays is very new to test for #212, which is https://github.com/jswhit/pyproj/pull/29  . That is only in the development version of pyproj.  That is odd that it only impacts Python 3.
test_convert is very new test too.
I installed the development version (and added an import sys, which is a current PR), and there were no errors.
The development version of pyproj plays nicely with Python 3.x.
Here's where pyproj is at at the moment.   There is currently an PR to add Travis-CI to pyproj.  In a patch that I sent I forgot an import sys.
I will ask for the development version pyproj to be runnable, but a new pyproj release is likely needed.  Using the development version can cause unexpected problems like this.

Ok, so to help guide decision-making here, let's settle some questions. First, is there a work-around for this bug we are encountering? If not, which versions of pyproj are we going to have to blacklist?
Tangentially, this section of code is ancient and is causing a number of problems elsewhere. The reason for its existence was for back in the numeric/numarray days. Perhaps it makes sense to rip this stuff out (separately, of course)?

I should revise my statement above:  both failing tests are from PR #223, which patch issue #209.  pyproj patched this same issue in https://github.com/jswhit/pyproj/pull/29 .
There could be a minimal version of pyproj, perhaps 1.9.3, for Python 2.x.  The minimum version pyproj for Python 3.x should probably the next release.
It is possible to skip the two (2) failing unit tests for Python 3 using current version of pyproj .  Doing something like this in test.py:
import sys
PY3 = (sys.version_info[0] == 3)
  ...
@unittest.skipIf( PY3 and pyproj.__version__ <= "1.9.4",
                  "TestProjectCoords tests skipped for pyproj version 1.9.4 for Python 3.x" )
class TestProjectCoords(TestCases):
   ...

That will cause it to skip the failing tests. IMO it is slightly unfair for an unpatched library to be expected pass new unit tests.
I see two courses of action.  (1.) Add the code above to skip the tests (my preference).  (2.) Wait for pyproj to get the development version working, install pyproj using the development version, but that means that basemap will probably should wait for a new version of pyproj to be released before it can have a new release.
I agree with getting rid of the old numeric/numarray code if it causes problems elsewhere.

I think that I've got this working per the unit tests.
The syntax from mpl_toolkit.basemap import pyproj still works because there is an import pyproj statement in init.py.   import mpl_toolkit.basemap.pyproj  does not work.
Currently, from mpl_toolkit.basemap import shapefile does not work. The  could easily be added for some backward compatibility, if desired.  Let me know if you want me to make that change.
@WeatherGod  Thank you for all your help with this.  Sorry for gridlocking the project for about a week.

I just thought of this; pyshp could easily be made an optional dependency.  It is required for .readshapefile() and .drawcounties().  Only three of of the examples need it: fillstates.py, hurrtracks.py, and counties.py.

:+1: looks good to me
Making pyshp optional makes sense but that could just as easily be done in a different PR

I am -1 on making pyshp optional at this point. I know I have used it
myself when I didn't want the bulkiness of GDAL, and I have seen others use
it, too. I don't think there would be much to gain by making it optional,
versus the confusion it could cause.
I just remembered that there is a hidden optional dependency in basemap:
OWSLib for wmsimage(). Obviously, it isn't tested.
On Mon, Dec 7, 2015 at 12:26 PM, Jens Hedegaard Nielsen <
<EMAIL_ADDRESS>wrote:

[image: :+1:] looks good to me
Making pyshp optional makes sense but that could just as easily be done in
a different PR
—
Reply to this email directly or view it on GitHub
https://github.com/matplotlib/basemap/pull/234#issuecomment-162599911.

Since pyshp is a python only library, it is so easy to install.  I don't see it being a problem to requiring it.  I thought I would bring it up.

:+1: Will wait for @WeatherGod to merge

Great work, @micahcochran! We will have to see about unbundling libgeos completely, but at least there is existing pathways for distributors to package it without the old geos codebase.

@WeatherGod  Thanks for all your help.

thanks for adopting the idea to remove these dependencies from the code base.


Lock Attribute and HP Max form fields when one or more talents has been applied to a character

Quick note to remind myself actor.overrides can be used to see what values are being overriden.

This may conflict with #225 depending on how we implement this.


ID base support new question:
User feedback: something
(base_support_new)

Question ID
base support new question

Details
Add a new page before this one:

On the following pages, you will be asked about the support amounts that you want the court to approve. Select the option below that describes these amounts.
-The support amounts were calculated using the MiChildSupport Calculator.
-The support amounts are different from the MiChildSupport Calculator amounts.
-I was unable to use the MiChildSupport Calculator.
Variable being sought | base_support_new
Package version | 0.0.5
Filename | docassemble.MLHMotionRegardingChildSupport:data/questions/motion_regarding_child_support.yml

Just to confirm, if the user answers "Support amounts are different" or "I was unable to use the MiChildSupport Calculator", we should check number 11 in FOC 10, "The support provisions ordered do not follow the Michigan Child
Support Formula.", right? Should we do anything different with FOC 10d as well?
For now, I've added the question, but I do need a bit more guidance on what to do with the answer.

W/r/t forms:
-If support was calculated using the MiChildSupport Calculator, the interview should produce the FOC 50 (filled) and FOC 10 (blank except for header/caption/parties.)
-If support amounts are different from the Calculator amounts, the interview should produce the FOC 50 (filled), FOC 10 (blank except for header/caption/parties), and FOC 10d (Deviation Addendum), blank except for header/caption/parties
-If user answers they were unable to use Calculator, skip all the questions about the support amounts and go to the end of the interview.  Produce FOC 50 (filled), and FOC 12 . For FOC 12, I would like to have the case info and party info filled, and an X or checkmark next to #1 ("An investigation was requested by one of the parties.") On FOC 50, even if user answers that they have reached an agreement, if they then answer that they were unable to use the MiChildSupport Calculator, leave par. 6 unchecked, and under par. 7, fill in "I ask the court to enter a referral order to the Friend of the Court for a support investigation."

I'll get back to you soon re: your question above. I want to make sure Ang and I are on the same page.

Re: your question above, when the user answers "Support amounts are different," we don't need to fill in anything beyond the case info and party info on the FOC 10 and 10d. Jonathan Pyle is working on a different Docassemble interview for us that will fill in both of those forms using the calculation results and the user's answers on support deviation (if any), but for this interview I will just update the instructions w/info on how the user can fill out those forms on their own. Not ideal, but it's the plan for now.

@BryceStevenWilley in case you come back to this, I did some initial work on getting the right documents to generate under the right circs, I just haven't been able to add it to Github because I don't seem to have access to write to this repo.
@scoellis I'd really appreciate if you could give me full access to this repo as soon as possible.

@ekressmiller I just added you as an admin to this repo! Apologies, I'll check the other repos too to make sure you have access where needed.

Thanks @BryceStevenWilley!  Will add the changes on github now.
@scoellis No need to add me to this repo anymore.

@ABillmire I'm wondering if something similar should happen in the Response.
If the respondent says they do not agree with the moving party's request, before we ask what the respondent wants, should we ask if they used the calculator and use similar logic to the above? Or do anything else in particular?
Or should we leave things as they are, such that we just fill in the moving party's request and leave it at that, without getting into what the child support calculator.
For reference, the LHI version currently goes like this, before asking what the respondent wants to request:


Normalization of FFTW.r2r for FFTW.RODFT00

I am confused about the r2r transform with odd symmetry. According to the FFTW manual, if I apply the RODFT00 transform to a unit vector of length 1, the result should be the vector [2]. But in Julia the commands u=ones(1,1) and v = FFTW.r2r(u,FFTW.RODFT00) gives the vector 4. Am I using this routine wrong?

With ones(1,1) you have a 2d array, so you did a 2d RODFT00 x RODFT00 transform, which multiplies by 2 twice.  If you want a 1d vector of length 1, use ones(1).


Add basic mocks

Signed-off-by: Mingkun Ma<EMAIL_ADDRESS>Description
Add basic mocks, types, service, etc.
Issues Resolved
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

@ps48 @msfroh New commit resolved comments. Thanks!


Unable to calibrate Radio with Pixracer with QGC

Whether with QGC stable nor daily and PX4 stable or master the Radio can't be
calibrated. Clicking on calibrate the screen becomes dark, clicking on OK the same screen as bevor
apears. An allert on bottem screen: 0 Channels detected....
On the 4 Channel lines still to read: Not mapped.
With PixMini, Pixhawk and Pix Light no problem.
And Pixracer with MissionPlanner and AC 3.3.3 even no problem with same HW setup.
And Pixracer with QGC and AC 3.3.3 even no problem.
Checked with Futaba 6303, 8208 and FrSky X8R. (S-Bus)
Sensors can be calibrated. 3DR Radio is working.
OS Windows 7 64 Bit.

The issue is solved. Hardware modification produced this.
QGC with PX4 Master works now with Pixracer R14.


Add displayName to all stateless components. Fixes #222. r=vporof

+100 to this. We should also enforce it via eslint. Care to look into that as well, Lin?

👍 I can take a look at that

Coverage increased (+0.1%) to 37.973% when pulling bf13d485a26d00eb4a2e070ca5726a9d2c790dbf on linclark:display-name into 6628a1bfc5910169877274971d92a8158b7321fd on mozilla:master.


⚠ GitLab Server has degraded performance

In 1f130ec, GitLab Server (https://gitlab01.its-telekom.eu) experienced degraded performance:

HTTP code: 200
Response time: 3147 ms

Resolved: GitLab Server performance has improved in ae25933.


⚠ Processors has degraded performance

In be475af, Processors ($STATUS_URL) experienced degraded performance:

HTTP code: 200
Response time: 74 ms

Resolved: Processors performance has improved in 7d65d76.


Coordinate accessibility events/clinics/workshops for the community

Part of this project is to provide accessibility education events/clinics/workshops/some other popular synonym to bring accessibility knowledge to the community and document it accordingly. I’ve been tasked with coming up with at least two events for this. I have three proposed event topics. We may choose two or end up doing all three. My proposed topics (in no particular order) are

Accessibility in your digital day-to-day. An event outlining accessibility considerations relating to common tasks to encourage people to better their everyday digital interactions with smaller actions that add up.
Recommendations for more accessible data visualizations. (A popular request.)
FAQ: Frequent Accessibility Quagmires. Documenting the sensory impacts of popular accessibility issues on the Internet, ways to test for them, and ways to improve them. The main draw of this over more general accessibility events would be that this event actually demonstrates what happens when things are built less accessibly as well the methods to discover them, more of an opportunity for interaction and understanding than being told a list of things to follow without thinking.

I have more details on format for these events, but I do want to check that these topics seem fitting before I dive too deep into ironing out each detail. They need to be completed by December.
I did not find an issue for this previously on this repository, but if there is one please let me know and I’ll consolidate information to it. Thank you!
cc: @trallard

Agreed topics:

Data vis 🎨

Ideas & discussions

Accessibility in your digital day-to-day

People wanting to do better but perceiving a lack of deep a11y knowledge as a barrier

FAQ

what happens when items are inaccessible?

Summarizing the discussion:
Topics!

Data visualization as a topic is totally agreed upon.
Accessibility in your day to day is the next most likely. More examples/clarity is wanted.
FAQ is a backup option. There are concerns about the work it will take to have so many demonstrations ready.
Focus more on a scientific spin than totally general accessibility applications.

Scheduling!

Schedule two events 4 weeks apart from one another.
Schedule Accessibility in your day to day first. Schedule Data visualization second.
I am proposing the dates be Tuesday, October 15 and Tuesday, November 19. I could also do Tuesday, September 17 and Tuesday, October 15 if we want to start a month earlier.

I’m adding a rough agenda outline for the accessibility in digital day to day topic for clarification and feedback. Right now this is written for about 1.5 hours since I don’t want to plan anything too long it is hard to commit to or schedule, but I don’t want to lose all the time setting up.
Concept
Taking action to try and improve access of the world around you to disabled people is not often a clear path. Some of the main feedback I’ve heard from people in advocating for accessibility over the years is that knowing it is important makes sense, but figuring out what to do is a challenge and taking action on limited resources—time, energy, and power—makes all of it much more difficult.
Even so, there’s so many opportunities in everyday routines online to complete tasks with more consideration of disabilities. The goal in this workshop is to give attendees examples of immediately actionable accessibility considerations in things they likely already do, to help them notice opportunities for accessibility, provide practice with well-scoped actions, and make a habit of individuals making online spaces more accessible. To do this, the format will be:

Go from beginning to end of a day via a set of common online tasks (ie. writing an email, inviting people to a social event).
At each task, the audience will have at least two options of how to complete that task. They will choose an via Zoom poll.
Like a choose-your-own-adventure story, the option with the most votes will lead to a slide with the outcome. Choices that consider accessibility will be noted and a quick “why they help” will be covered on the slide. Choices that miss accessibility considerations will describe its negative impacts and point to what to do instead.
A tally of choices will be mentioned at the end to help the group see how these small choices can add up by the end of a day.

Draft agenda outline

Pre-workshop filing in and hellos.
Introductions.
Summarize agenda and give out links. Code of conduct.
Explain the format and expectations.

What we’ll cover in this workshop
What we will not cover in this workshop
How we’ll play (scenario, options, vote, results)
Rules

Trial run scenario (not accessibility related)
Real scenario. Let’s start the day!
Say good morning to loved ones

Happens in messaging software. Goal: remember this is about people, and people all benefit from different things. Know your audience.

Check email and/or Slack

Happens in email software or messaging software. Can be in the browser or not.

Review your calendar and schedule a meeting.

Happens in web-based calendar. Goal: Provide a meaningful meeting invite with relevant support. Give it a meaningful title. Provide an agenda and/or things attendees need to know before attending. Provide opportunity to reschedule and request something from the meeting host (ie. slides ahead of time).

Present something at work.

Could happen virtually or in-person, but it is likely digital supports like a document or slides or a demonstration will be there too. Goal: Have a table of contents. Define terms. Briefly describe the contents and meaning of what you are presenting, especially diagrams or demonstrations. Use headings and appropriate formatting to section contents.

Scenario lunch! Take a break in the scenario and in real life too.
Break (5 minutes)
Send something fun to your friends.

Happens in messaging software. Goal: Provide meaningful text for any links sent. Check if that cute animal video needs sound or has captions.

Host a meeting.

Could happen virtually or in-person. Goal: Plan breaks, especially for anything longer than an hour. Choose a venue that will meet the needs of all your attendees. Minimize or eliminate side conversations (ie. audibly, in the meeting chat, elsewhere within the group). Consider providing captioning or interpreters; make this a requirement if planning something public facing. Set expectations for speaking order (ie. raise hands or other signal). Have shared group notes.

Share a social invite.

Happens via messaging software with the invite as an image. Goal: Share the invite with relevant information in text outside the image. This could be alt text or it could be in the message itself. Pass on any questions or requests you have for the social hosts.

Tally and summarize choices.
Further resources and wrap up.
How to get involved with next workshops.

Logistics:

Venue: thinking about Zoom, we can use the Quansight Zoom account
Event registration: Eventbrite
Places to advertise: Scientific Python, NumFOCUS newsletter (15th of every month), CZI Science newsletter, social media
Recording: yes, preferable (we can put it on the Scientific Python Youtube)
Can do a write up for the handbook

Date: I think I'd rather go earlier to avoid running into the holidays that often make scheduling difficult. That means Tuesday, September 17 and Tuesday, October 15 barring other rescheduling needed.

Draft event checklist for your review! I want to make sure we're on the same page about what should be done. Please let me know what you think it missing or anything you think might be inaccurate.
Before event

Zoom event set up
Preset Zoom settings
Event registration set up
Advertise event via NumFocus
Advertise event via other mailing lists
Advertise event via Scientific Python channels
Advertise via Quansight Labs blog post
Illustrate for advertisement
Illustrate for slides
Make event agenda and notes
Schedule/arrange captioning
Schedule event moderators
Compile extra resources
Make feedback survey

One week before event

Slides are complete
Dry run of event transitions and interactions
Reminder/join now email for registrees

During event

Team appears early
Internal resources document
Test screen share before starting
Reply to comments in chat where possible
Refer to agenda document and notes
Post questions/activities as planned
Keep time/time check in signal

After event

Thank you email
Captioning and transcription for recording
Illustrate thumbnail
Upload recording to YouTube
Summary and resource blog post to Quansight Labs
Link recording in other advertising areas as follow up
Send feedback survey


Help wanted: Login form customisation

I would like to customise the look of the login page but I can't see it anywhere in the documentation. Would you be able to point me to the correct place or advise on how I can do this. Thanks

Hi, you can check this page in the react-admin documentation.

Hi, thanks for getting back to me. Yes, that did the trick. I wasn't sure that react-admin-amplify used the same react-admin login form.


New files are not added to the sidebar

Describe the bug A clear and concise description of what the bug is.
If you run npm run docs:dev and update a file, the new file contents show up correctly
But if you create a new file while npm run docs:dev is running, it won't appear in the sidebar
To Reproduce Steps to reproduce the behavior:
Make a new file while npm run docs:dev is running and it won't show up in the sidebar
Expected behavior A clear and concise description of what you expected to happen.
The file should appear in the sidebar
Screenshots If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):

OS: [e.g. Windows 10]
Browser [e.g. Chrome, Safari]

Additional context Add any other context about the problem here.

Hello, thank you for using vitepress-sidebar.
This is a hot reload issue with Vite + VitePress and unfortunately there is currently no way to fix it in vitepress-sidebar.
I'll open an issue to help others figure this out, but until we have a solution in the near future, you may need to manually restart the server.
Regards,


prisma 5.6.0 libquery_engine-darwin-arm64.dylib.node regression

Bug description
Prisma Client could not locate the Query Engine for runtime "darwin-arm64".

This is likely caused by a bundler that has not copied "libquery_engine-darwin-arm64.dylib.node" next to the resulting bundle.
Ensure that "libquery_engine-darwin-arm64.dylib.node" has been copied next to the bundle or in "node_modules/.prisma/client".

We would appreciate if you could take the time to share some information with us.
Please help us by answering a few questions: https://pris.ly/engine-not-found-bundler-investigation

The following locations have been searched:
  /Users/cipri/dev/acme/mono/apps/ops/node_modules/.prisma/client
  /Users/cipri/dev/acme/mono/apps/ops/.next/server
  /Users/cipri/dev/acme/mono/packages/db/node_modules/@prisma/client
  /Users/cipri/dev/acme/mono/apps/ops/.prisma/client
  /tmp/prisma-engines

How to reproduce
Monorepo setup
Prisma randomly fails with errors that it cannot find the schema or the runtime. I am using accelerate. Started happening with the latest 5.6.0
Expected behavior
As you can see the prisma db module is used in a nextjs app called ops
The prisma script is searching everywhere except for where it actually should which is
  /Users/cipri/dev/acme/mono/packages/db/node_modules/.prisma/client
Not to add that the .prisma/client and @prisma/client generated folders is confusing af
Prisma information
Not relevant
Environment & setup

OS: mac
Database: postgres
Node.js version: 18.17.1

Prisma Version
5.6.0

Hey @cipriancaba, sorry to hear that you are experiencing this, you should have been pointed to a help page in the error message. Can you please visit and try https://www.prisma.io/docs/guides/other/troubleshooting-orm/help-articles/nextjs-prisma-client-monorepo, and let me know if that helped you?

I am curious as well about what you said. You said that you are using Accelerate. According to the error, you are not, as Accelerate is engine-less and will not search or depend on an engine. Perhaps you have passed a regular URL instead of a prisma://... URL?

Hey @millsp thanks for the quick reply.
You are right, i was using accelerate but kept running into problems with transactions in server actions so reverted to direct access.
I've already done the fix, that's not the problem as this setup was working pre 5.6.0, i just upgraded from 5.5.2
As you see in the trace, which is very helpful btw, prisma is not searching in the prisma package node-modules, which should be a quick fix for this issue. It's only searching in the next app itself and the @prisma/client of the actual db package. It should search in the prisma package's node-modules/.prisma/client where the runtime gets copied

As you see in the trace, which is very helpful btw, prisma is not searching in the prisma package node-modules, which should be a quick fix for this issue

I see that would help you now. The "engine search" is something that we are aware of and we know it is not perfect. In your case, the client has been bundled with Next.js. This means that in a real deployment, db may not actually be present in the deployment so it wouldn't help to search there. I don't want to make assumptions about your setup, maybe db is also deployed?

Prisma randomly fails with errors that it cannot find the schema or the runtime.

Now cross-linking what you just told me and this. It sounds that you are maybe experiencing a bug from the webpack plugin, which sometimes "misses" to copy the engine. Could it be this? If so, we may have a solution for TS and ESM users in the coming weeks so that this plugin is not necessary at all anymore.
In the mean time, I wonder if marking db as external could be a solution for you?

If you have some time, I'd really appreciate if you could give us a reproduction that we can run easily (ready to run basically).

Hi @millsp, thanks for your replies here, will try to setup a repro example, the only problem is that this randomly happens when I add various packages. It's really just this template with another web app, will try to create that for you
https://github.com/t3-oss/create-t3-turbo

Just to confirm again an avoid any confusion, this only happened when you were not using Prisma Accelerate @cipriancaba, correct?
With versions before 5.6.0 you were also using Prisma directly (not via Accelerate) and you did not have this problem?

Hey @janpio and @millsp
Here is the repro repo:
https://github.com/cipriancaba/prisma-query-lib
Just run pnpm install from the root
Go to the db package and run pnpm db:generate
Funny enough the issue doesn't seem to reproduce here because prisma client gets generated in the root node_modules as opposed to local node_modules. On my private repo it behaves differently and I am not sure why on one monorepo it's hoisted and on the other it's not. How does prisma generate choose where to generate the client by default in a monorepo?
And to answer the above:
This only happened when you were not using Prisma Accelerate, correct? -> YES
With versions before 5.6.0 you were also using Prisma directly (not via Accelerate) and you did not have this problem? -> YES but also didn't have 2 nextjs packages in the repo. So the problem started happening at some point after upgrading to 5.6.0 and adding a new next app in the repo

So it might not actually be a regression? Or does it work in 5.5.0?
If I understand your message correct, the repro repo does not actually reproduce, correct?

It doesn't reproduce because the prisma client folder gets generated in the root of the repo node_modules and not in the local package (packages/db/node_modules). I am confused as to why that happens and was hoping you can help me understand

@cipriancaba for starters, we'd really like to actually get a reproduction of the issue. Unfortinately, repo where issue does not happen does not help us either. Could you try to reduce you private repo to a minimum size where issue still reproduces but remove all actually private stuff from it and get something you can share?
Btw. one think worth checking is . npmrc file - does it have the same contents in your public repo and in your private one?

@cipriancaba Do you have time to take a look at @SevInf request? Thanks.

what got me working is by doing this
package.json
{
  "name": "@package/database",
  "version": "1.0.0",
  "main": "dist/index.js",
  "types": "dist/index.d.ts",
  "scripts": {
    "build": "tsup && npx prisma generate"
  },

schema.prisma
generator client {
provider        = "prisma-client-js"
previewFeatures = ["fullTextSearch", "fullTextIndex"]
output = "../dist"
}

Hey @cipriancaba ,
Without a proper reproduction, we unfortunately have to close the issue for now. Feel free to comment if you manage to create one and we'll reopen the issue.
Thank you 🙏

Getting the same error with tsup and turborepo
PrismaClientInitializationError: Prisma Client could not locate the Query Engine for runtime "darwin-arm64".

This is likely caused by a bundler that has not copied "libquery_engine-darwin-arm64.dylib.node" next to the resulting bundle.
Ensure that "libquery_engine-darwin-arm64.dylib.node" has been copied next to the bundle or in "packages/api/dist".

We would appreciate if you could take the time to share some information with us.
Please help us by answering a few questions: https://pris.ly/engine-not-found-bundler-investigation

Hi @Jolg42 . Monorepos are normally used in complex environments which are not easy to replicate. I've tried doing this but can't replicate it on a new project because in my actual setup the prisma client gets generated in:
packages/db/node_modules/.prisma

and while in my repro above it gets correctly generated in
node_modules/.prisma

Now if I were to understand how prisma generate chooses the location to generate the client by default, it might help with the repro case.
While i know it would be really helpful for you to have a repro case, i feel this is a help me to help you situation as opposed to closing the issue.
For anyone wondering, I am working around the issue with having a custom output location and using the stupid nextjs prisma plugin which is somethings causing infinite loops while prisma is trying to locate the query engine and just hangs forever
generator client {
  provider        = "prisma-client-js"
  output          = "../client"
  previewFeatures = ["multiSchema", "views", "relationJoins"]
  binaryTargets   = ["native", "darwin-arm64", "rhel-openssl-3.0.x"]
  engineType      = "library"
}

next.config.js
webpack: (config, { isServer }) => {
    if (isServer) {
      config.plugins = [...config.plugins, new PrismaPlugin()]
    }

    return config
  },

@Jolg42 is there maybe a different way of importing the libquery_engine-darwin-arm64.dylib.node query engine? Maybe setting an ENV path or something that would reference it?

@cipriancaba Indeed there is that one PRISMA_QUERY_ENGINE_LIBRARY=custom/libquery_engine-darwin-arm64.dylib.node
Sounds interesting to try it out, good idea 😉
https://www.prisma.io/docs/orm/reference/environment-variables-reference#prisma_query_engine_library

I ran into the same issue using the same monorepo provided above, and with the env variable @Jolg42 mentioned I got it to work. It feels really hacky but this did it for me:
PRISMA_QUERY_ENGINE_LIBRARY="../../node_modules/.pnpm/@prisma+client<EMAIL_ADDRESS>

Thanks @idebeijer for the update for the workaround. I think our problem here is that we would need to get a reproduction first before we can attempt a fix.

@Jolg42
I think I found one reason why this could happen. We have a mono repo and we are using esbuild. Since we need to keep some dependencies in the node_modules (pg, events), we were having trouble with the final dist file. So we ended up doing something lazy but simple. We just have another package.json with these dependencies so we can copy whatever node_modules folder is generated into a zip file for distribution. The structure is as follows (simplified):

build

node_modules

package.json (this has pg, pg-native and prisma)

node_modules (folder for local dev)
src

prisma

schema.prisma

package.json (this one has prisma again, and all of our other dependencies which will later be bundled by esbuild, but ignoring the build folder)

Now, in the beginning, we added the schema in the first package.json as "../src/prisma/schema.prisma" and "ran npx prisma generate" inside the "build" folder. The client was being generated but in the top parent node_modules. The one in build/node_modules/.prisma was not initialised and also was missing the engines. I was expecting prisma generate to run from the "build/node_modules" but it was not.
In order to fix it, we just copy the schema.prisma into the build folder during the packing and then the client generates inside the right build/node_modules and we can copy the client to the final dist.zip file. I guess I was expecting the prisma generate to generate the client relative to where the script is ran but I believe it is doing it from the schema.prisma and the nearest node_modules

Another possible problem, since we also had this is that we were using pm2 as a package manager. When running, pm2 changes the cwd so your app looks for the prisma client in a different path. More info here: https://github.com/Unitech/pm2/issues/96
So if you are using pm2 you need to set up your cwd as well (this is related to pm2, not Prisma) but we had that issue as well.

Ran in to this issue today when trying to setup a new monorepo using turborepo with the prisma example like:
yarn dlx create-turbo@latest --example with-prisma.
Did a search for the engine in the repo with find ./ -name "libquery_engine-darwin-arm64.dylib.node" -type f -print0 and find it at these places:
./node_modules/prisma/engines/12e25d8d06f6ea5a0252864dd9a03b1bb51f3022/libquery_engine-darwin-arm64.dylib.node
./node_modules/prisma/libquery_engine-darwin-arm64.dylib.node
<EMAIL_ADDRESS>./packages/database/node_modules/prisma/libquery_engine-darwin-arm64.dylib.node
./packages/database/node_modules/.prisma/client/libquery_engine-darwin-arm64.dylib.node
<EMAIL_ADDRESS>
Did try to use the PRISMA_QUERY_ENGINE_LIBRARY to set the location manually as suggested above but that did not solve the problem.


Research requirements for good accessibility

ARIA, WCAG color / contrast, tab focussing, how to accomodate screen reader?

Google Lighthouse audit!!


Check for XML documentation file and document dependencies. Fixes #917

PR Details
This changes the way that documentation is cached for the editor to consider the standard XML documentation if available as a fallback when usrdoc is not provided. It will also now look at dependencies of solution project assemblies.
Recreated due to invalid GitHub link with commit user.
Description
When first loading a project, the UserDocumentationService caches docs it finds in the .usrdoc files. This is a simple key-value format and is not generated automatically by Stride projects. The XML documentation file can be produced easily by including the appropriate directives in a csproj file as laid out in https://docs.microsoft.com/en-us/dotnet/csharp/codedoc. With this change, we will first look for a .usrdoc file before falling back to the .xml path. A future enhancement could be made to respect the project's specified documentation path. When looking at XML, it only considers the <userdoc> element
Related Issue
https://github.com/stride3d/stride/issues/917
Motivation and Context
When  is added to a public property, game studio should show the text when the mouse is over that property in the Property Grid. The only supported file is a custom key-value doc with the .userdoc extension and XML documentation is ignored. The <userdoc> element is currently what is being used in the .usrdoc file so the convention is continued here.
Types of changes

[ ] Docs change / refactoring / dependency upgrade
[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist

[x] My change requires a change to the documentation.
[ ] I have added tests to cover my changes.
[x] All new and existing tests passed.

 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.You have signed the CLA already but the status is still pending? Let us recheck it.

Thanks, good change!
I am a little bit worried about the large XML parsing in the main thread. I wonder if it could be moved outside of UI thread (i.e. using async, Task or Lazy).
Maybe not trivial since it seems needed while building the nodes in DocumentationNodeUpdater.  Possibly DocumentationData.Key needs to change from string to Task<string>?

XML Parsing is slow, but I'm not sure what an average size of this file would be. My project is small/medium that I was testing against with a 132 KB docs file and it wasn't perceptible. Using async should be okay. When you say DocumentationData.Key, are you referring to the cachedDocumentations dictionary in here? Since I will have parsed by that point should I attempt to wrap the parsing of the files in an async task instead?

@xen2

@xen2 I'm just coming back to this now. It seems like the async changes you discussed are related to #178. I'm not familiar enough with the engine to make a change that drastic.
This information doesn't seem like something we should be caching on-demand as it generates with the build. Should we instead pre-cache while loading the projects into the session?
For example, the following area:
https://github.com/stride3d/stride/blob/a8977da1e215e301ed5f9af6d1ca44cc6a853004/sources/editor/Stride.Core.Assets.Editor/ViewModel/SessionViewModel.cs#L1260-L1270
Could be modified to perform this work like this:
internal void ProcessAddedProjects(LoggerResult loggerResult, WorkProgressViewModel workProgress, bool packageAlreadyInSession)
{
    var newPackages = new List<PackageViewModel>();
    var documentationService = ServiceProvider.Get<UserDocumentationService>();
    foreach (var package in session.Projects.Where(x => !packageMap.ContainsValue(x)))
    {
        var viewModel = CreateProjectViewModel(package, packageAlreadyInSession);
        viewModel.LoadPackageInformation(loggerResult, workProgress);
        newPackages.Add(viewModel);

        // Add documentation at load time.
        foreach (var packageAssembly in viewModel.LoadedAssemblies)
        {
            documentationService.CacheAssemblyDocumentation(packageAssembly.Assembly);
        }
    }
    ProcessAddedPackages(newPackages);
}

(Is there a better place?)
These .xml and .usrdoc files are generally quite small for most projects and we already require a reload on code change. What are your thoughts?

@Eideren mind giving this one another look? I think this should take care of the concurrency concerns, but my fire-and-forget per assembly vs. one Task with the foreach loop within has me second guessing myself.

@AmbulantRex while you're working on this service can you take a look at fixing #1102? Should be quick, as it just needs a replace of + with . wherever the Type.FullName is used.

Almost done, two small issues !
Do note that right now documentation removed while systems are running are not removed from this cache, I don't think it's a big deal as it would increase complexity quite a bit for something that has no side effect. If someone has a good argument to make sure it's cleaned up feel free to step in.
As for @manio143 's suggestion, if you really want to go the extra mile you could look at the source for those formats to see how/why it formats inner class with a . instead of a + and replicate that formatting on our end to make sure that it's always accurate. Feel free to just do a string replace +->. if you don't have time.

I was able to throw in the simple replacement as part of this one. I dug around to see if there was a more elegant way to solve it, but .NET under the hood populates the qualified name using + for subclasses. The classes in the engine that dealt with this were very generic so I was afraid of unintended consequences modifying it any further up the chain, but I could come back to it if I come across a better way down the road.


Make the app name known for dynamic bridge

Dynamic bridge example build instructions did not include info on what artifacts are generated. As a result this gets a compile error:
./scripts/build/build_examples.py --target linux-x64-dynamic-bridge build --copy-artifacts-to out/artifacts

Log looks like:
...
Step #5 - "Linux":   File "/workspace/./scripts/build/build_examples.py", line 224, in cmd_build
Step #5 - "Linux":     context.obj.CreateArtifactArchives(create_archives)
Step #5 - "Linux":   File "/workspace/scripts/build/build/__init__.py", line 83, in CreateArtifactArchives
Step #5 - "Linux":     builder.CompressArtifacts(os.path.join(
Step #5 - "Linux":   File "/workspace/scripts/build/builders/builder.py", line 98, in CompressArtifacts
Step #5 - "Linux":     for target_name, source_name in self.outputs().items():
Step #5 - "Linux":   File "/workspace/scripts/build/builders/builder.py", line 83, in outputs
Step #5 - "Linux":     artifacts = self.build_outputs()
Step #5 - "Linux":   File "/workspace/scripts/build/builders/host.py", line 399, in build_outputs
Step #5 - "Linux":     for name in self.app.OutputNames():
Step #5 - "Linux":   File "/workspace/scripts/build/builders/host.py", line 169, in OutputNames
Step #5 - "Linux":     raise Exception('Unknown app type: %r' % self)
Step #5 - "Linux": Exception: Unknown app type: <HostApp.DYNAMIC_BRIDGE: 22>

This PR adds the name of the output files for the dynamic bridge, so that artifact generation works.

Hotifx: build fix that is not verifiable by any CI.


Factor mode improved

More precise Factor code coloring

Would it be possible to make these improvements without writing a completely new interpreter for this style of mode? I really don't want to maintain a second copy of such an interpreter. What precisely does your patch improve, and why did you decide to not use defineSimpleMode?

Sorry - I was sure I was using the simple mode. Fixed it now.

Merged as 37d59ff4


test: youch source-map

Codecov Report

Merging #2366 into dev will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##              dev    #2366   +/-   ##
=======================================
  Coverage   98.39%   98.39%
=======================================
  Files          15       15
  Lines         996      996
=======================================
  Hits          980      980
  Misses         16       16

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 29df01f...dc53b98. Read the comment docs.


add basic test which simulates user input

When trying to write a test for #446, I noticed that there aren't any test yet covering user interactions. After some iterations I came up with a possible solution, which at least works for simple cases. I thought it may make sense to open a separate pull request for that one to keep the discuss in #446 focused.
My original goal was to paint a simile in that test. But I faced some issues when trying to paint a stroke. So for the first iteration it is three dots only.

Glad to hear that you are happy with that approach. Will use it to add a test for #446.


Use a variant for OpenCL-xor-CUDA parameter pairs

There are multiple functions in kernel-runner.cpp which take both OpenCL-specific and CUDA-specific params - only one of which is non-empty / non-null. We could use a single variant class instead. This should be trivial in C++17 (std::variant), but we're stuck with C++14 for now.

Dupe of #26.


Security information leak in internal qcow handler's check_config callback

The implementation of qcow_check_config presents an information leak, because it allows any user with access to the dbus system bus to check for the existance of files and directories, even if the user shouldn't have access to those files.
For example issuing this command as a regular user allows to get the knowledge, whether /root/.bash_history exists:
dbus-send --system --print-reply --dest=org.kernel.TCMUService1 /org/kernel/TCMUService1/qcow org.kernel.TCMUService1.CheckConfig string://root/.bash_history

These kind of information leaks in combination with other security issues often leverage more serious security issues.
I'd have suggested a bugfix for this but it is difficult to get right. If we knew the peer credentials from dbus we could do a comparison of those credentials against the target file credentials. This still would be difficult for corner cases, where the file itself would be accessible to the user, but not some of the upper components of the path.
The check_config callback does currently not provide a possibility to pass peer credential information in, so this would affect public API in some way. Also I've not found a simple way to get the dbus peer credentials via libgio, maybe by using a GDBusAuthObserver.
All quite complicated, might be easier to drop this config callback altogether.

We are actually in the process of removing the check_config callback, so just send a patch to remove them all (file_example.c will have a similar issue I think).

Okay I did as you suggested. Good hint with the file_example.c. It contains an even worse vulnerability, allows to temporarily create arbitrary files in the system, possibly deleting other processes' files after winning a race.


Automatically hide expressions preference

Some users asked for an option for a preference to automatically hide expressions on startup. I managed to successfully add it the preferences (which defaults to false), but when I try to add the functionality to these two functions in app.rs, it seems like it will hide the expressions for one frame, but make all every mesh visible immediately afterwards and I can't figure out why.
pub fn add_folder_to_workspace(&mut self) {
        if let Some(folder) = FileDialog::new().pick_folder() {
            // Users may want to load multiple animation folders at once for stages.
            let new_models = load_models_recursive(&folder);

            self.animation_state
                .animations
                .extend(new_models.iter().enumerate().map(|(i, model)| {
                    if let Some(anim_index) =
                        model.anims.iter().position(|(f, _)| f == "model.nuanmb")
                    {
                        // The model.nuanmb always plays, so assign it automatically.
                        vec![AnimationSlot {
                            is_enabled: true,
                            animation: Some(AnimationIndex {
                                folder_index: self.models.len() + i,
                                anim_index,
                            }),
                        }]
                    } else {
                        // Add a dummy animation to prompt the user to select one.
                        vec![AnimationSlot::new()]
                    }
                }));

            self.models.extend(new_models);
            // TODO: Only update the models that were added?
            self.should_reload_models = true;
            self.should_validate_models = true;

            if self.preferences.autohide_expressions {
                self.hide_expressions();
            }
        }
    }

    pub fn reload_workspace(&mut self) {
        // This also reloads animations since animations are stored as indices.
        for model in &mut self.models {
            *model = ModelFolder::load_folder(&model.folder_name);
        }
        self.should_reload_models = true;
        self.should_validate_models = true;

        if self.preferences.autohide_expressions {
            self.hide_expressions();
        }
    }

The expression hiding modifies the render models, which haven't been loaded yet in the code you posted. You would hide expressions when reloading models in main.rs instead. It's split up to avoid having rendering related code in the UI functions.

Oh thanks. I figured it out.


Persist circuit state

Is your feature request related to a problem? Please describe.
When the page closes or reloads, user loses all their work.
Describe the solution you'd like
No functional changes to the UI, but the workspace should never change unless the user intended to. Use Cache-control headers..
Describe alternatives you've considered
Leaving it as-is for now, which is fine while we focus on the task flow.

There can be a dedicated "Save" button, but saving it to the browser cache or the cloud (once logins are established) are fine. This will be especially important for templating.

Need to define this user story a little better

This issue is not relevant anymore. Closing it. See #323 for more details.


Ability to have a custom slider template

In the AngularJS library that this library is based on, there was a way to set a custom template on the slider via an rz-slider-tpl-url directive.
<rzslider ...
  rz-slider-tpl-url="path/to/template.html">

Is there a way to do this in this library/is this a planned feature for this library? The documentation doesn't seem to say anything about this functionality.

No, sorry, I have no plans to support custom templates in Angular 5+.
Unlike angularjs, Angular 5+ requires each component to have a static template, able to be resolved at compile time.
While there are some workarounds that could be applied, like transcluding user-specified content, the problem is that managing code like this very quickly becomes borderline insane. I already went through something similar to support custom tooltips. This was to get rid of dependency on ng-bootstrap, and that's about as far as I'm willing to go.

Thanks for getting back to me so quick!
I think I'll fork this repo and give it a shot since there's not really a nice workaround for my particular use case.

Yes, forking will be an easier option.


Rebuild for python311 (patched)

This PR duplicates the commits from #54 with extra patches to sort the failing builds.
Closes #54.

Checklist

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

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.
I do have some suggestions for making it better though...
For recipe:

License is not an SPDX identifier (or a custom LicenseRef) nor an SPDX license expression.

Documentation on acceptable licenses can be found here.

@grlee77 as someone that's more familiar with conda feedstocks, is this sufficient? Can we merge after successful CI? @duncanmmacleod changes look benign to me.

Yes, this looks good to me. Thanks @duncanmmacleod!

Thanks all! 🙏


pretrained swin-L model and loaded state dict do not match exactly

Here is the output:
Load encoder backbone from: model_zoo/swin_transformer/swin_large_patch4_window7_224_22k.pth
The model and loaded state dict do not match exactly
unexpected key in source state_dict: norm.weight, norm.bias, head.weight, head.bias, layers.0.blocks.1.attn_mask, layers.1.blocks.1.attn_mask, layers.2.blocks.1.attn_mask, layers.2.blocks.3.attn_mask, layers.2.blocks.5.attn_mask, layers.2.blocks.7.attn_mask, layers.2.blocks.9.attn_mask, layers.2.blocks.11.attn_mask, layers.2.blocks.13.attn_mask, layers.2.blocks.15.attn_mask, layers.2.blocks.17.attn_mask
missing keys in source state_dict: norm0.weight, norm0.bias, norm1.weight, norm1.bias, norm2.weight, norm2.bias, norm3.weight, norm3.bias
It seems that the pretrained swin-L model and the source state dict do not match.

This is normal. There are some differences between the original backbone and the one in our model.


Less strict code of the TinylogLoggingProvider #168

Description
Implementation of the changes discussed in issue #168.

Moved the writer generation code from ConfigurationParser into the non static, non final class TinylogLoggingConfiguration to allow other providers to use it.
Moved commonly useful methods like log entry handling from TinylogLoggingProvider into the non static, non final class TinylogLoggingConfiguration
Contrary to the initial suggestion did not change the static code of ConfigurationParser as it now just calls static methods of Configuration. So static is ok.
Some smaller methods are kept in TinylogLoggingProvider (like level calculation) as this will be used inside the logging write  itself and might affect the performance (all other changes are constructor only changes). Can be discussed but I think it is ok to keep it in its original place.
Added new unit tests to cover these changes
It could be discussed as idea (but I decided not to follow it for the moment) to put other access function to Configuration elements (e.g. filename) which is done by the writers constructors or support methods into ConfigurationParser  as the parser now more or less translates string elements of Configuration  into method getters. Similar functions might be getFilename()  and alike from the writers. I did not follow this up as it can also be argued that there is not so much common or usefull stuff to justify it and the writers know themself best what they are doing. So here just as possibility.

As result you can now more easily duplicate/write an own logging provider with similar functionality to TinylogLoggingProvider and use the helper functions from TinylogLoggingConfiguration. Much less code duplication is now needed.
Linked issue: #168
Definition of Done

[x] There are no TODOs left in the code
[x] Code style follows the tinylog standard
[x] All classes and methods have Javadoc
[x] Changes are covered by JUnit tests including corner cases, errors, and exception handling
[x] Maven build works including compiling, tests, and checks (mvn verify)
[x] Changes are committed by a verified email address that is assigned to the GitHub account (https://github.com/settings/emails)

Documentation
Additions or amendments for the public documentation:
No changed to documentation.

Agreements

[x] I agree that my changes will be published under the terms of the Apache License 2.0
[x] I agree that my GitHub user name will be published in the release notes

Please check the pull request throurougly. It is a bit more code change so you should look at it whether it is all ok or tell me where you desire changes.
The change can go to 2.2. or 2.3.
It does not change API or usage and the tests pass but of course it is a some LOC changes  which always can introduce undetected bugs - although mainly moving the methods to another file.

PS: The latest top level POM file has the javadoc line
<javadocExecutable>${java.home}/bin/javadoc</javadocExecutable>
removed.  Without this it does not build with me anymore. What do I have to change to build with the latest POM?

You are right a bit odd indentation...  Must be some editor settings.
I will fix all style errors and create the pull request again against 2.3. as you suggested tomorrow.

Closed in favor of #173


Scatterplot color with Boolean values is not rendering properly

On texthero.visualization.scatterplot, when a column of boolean values is passed as color arguments, no colors are rendered.

@jbesomi can you show the steps to recreate this bug? texthero.visualization.scatterplot with boolean values as color seem to be working fine for me.

Hey @cedricconol, thank you for pointing this out! Until recently, we were using plotly_express instead of plotly.express. plotly_express wasn't updated since more than one year and had this kind of bugs. So, just by moving to plotly.express we solved this issue. I will close it now then; thank you again!
P.s if you are interested in helping out with the visualization.py module, these two related issues need some help: #77 and #78! :)

Yes, I'm interested in helping! I'll take a look at those issues. Thanks @jbesomi!


Update balanced team image

Good to go. Broken links check failed for some reason but fine on my machine.

Hey @joemoore, sorry about that, looks like it's issue #954 manifesting a bit, nothing wrong with the PR. I reran and everything passed, so I've gone ahead and merged.


NodeMCU on Infinite loop when Changing Hardware Settings to MFRC-522

I've read issues #99 and #98 , which both related to 0.7.
I've been trying to sort this out, and found out the NodeMCU chip only enters in the infinite loop when I change the hardware settings to MFRC-522.
I've changed, one by one, almost every other setting and it would work normally. The moment I changed the hardware to the MFRC, it stopped working again.
So that makes me think the issue may be related to the MFRC-522 coding at some level.
I'm using the LoLin 0.1 NodeMCU v3 card (which seems to be the same one as the one from the issue #98 )
Tried using both Chrome and Edge, private mode, always erased the flash before uploading the new firmware.
My loop log is the following:
`Soft WDT reset
ctx: cont
sp: 3fff12f0 end: 3fff1660 offset: 01b0

stack>>>
3fff14a0:  00241001 00000001 3fff0640 40106a59
3fff14b0:  00000002 3fff0440 3fff04c8 40215d78
3fff14c0:  40201566 00000001 00000032 4020155b
3fff14d0:  00000000 00000010 3fff0440 40215eed
3fff14e0:  3fff186c 00000020 3fff0440 40215fdd
3fff14f0:  00000000 00000000 3fff0440 40215ffb
3fff1500:  3fff1548 00000020 3fff36a0 40232e5c
3fff1510:  3fff3860 3fff3768 3fff36a0 40233fdc
3fff1520:  40107530 00000000 000003e8 00000100
3fff1530:  3fff3304 3fff3344 feefeffe 00000020
3fff1540:  00000001 000000fc 40107168 40202644
3fff1550:  3fff378c 00000400 3fff2a84 3fff2d84
3fff1560:  3fff2a1c 3fff046c 3fff161c 00000578
3fff1570:  000000f0 3fff25e0 3fff25dc 4021adb1
3fff1580:  00000578 4021c124 3fff161c 4020b775
3fff1590:  4021af28 4021afe4 4021b124 002fb000
3fff15a0:  00100000 00001000 00002000 00000100
3fff15b0:  3fff335c 00002fb0 4020b7a0 4020b4b8
3fff15c0:  3fff38d8 3fff3818 00000000 3fff062c
3fff15d0:  3fff186c 3fff25e0 3fff25dc 4021adfb
3fff15e0:  0001c200 00000000 3fff0625 3fff062c
3fff15f0:  3fff186c 3ffe962f 3ffe90e4 402344b8
3fff1600:  40207d3c feefeffe 4021b348 4021b334
3fff1610:  00000000 00000000 feefeffe 00000000
3fff1620:  00000000 feefeffe feefeffe feefeffe
3fff1630:  feefeffe feefeffe feefeffe feefeffe
3fff1640:  3fffdad0 00000000 3fff0625 4021a1d0
3fff1650:  feefeffe feefeffe 3fff0640 40100700
<<<stack<<<

ets Jan  8 2013,rst cause:2, boot mode:(3,6)
load 0x4010f000, len 1384, room 16
tail 8
chksum 0x2d
csum 0x2d
v614f7c32
~ld
`
I hope you can help me, I really liked the solution provided and was really excited about implementing it on a project.
Thanks

The problem is the RC522 module must be connected on SPI bus correctly.
See https://github.com/omersiar/esp-rfid/issues/134#issuecomment-411693609
and
https://github.com/omersiar/esp-rfid/issues/134#issuecomment-411889844

Thanks for the tip, I will try this in the next couple of days and will tell you if it worked!


Task: Improve Rate Limiter Handling of Time

Description
#47 introduced a basic rate limiting implementation with some unit tests, but they're not ideal. One of the main limitations here is around the mocking we have in place for the clock:

The mock requires that we checkpoint it between calls to set different return values, which requires a mutable reference.
The mock also doesn't implement clone, so once we create at TokenLimiter we can't checkpoint it (since it's moved on creation).
To test the rate limiter nicely, we want the clock to be able to return different times.

Steps to Complete

Update tests to use a static start time (unix epoch?) rather than the current time.
Improve tests to mock out progression of time rather than this workaround, this could either be:
2.1. Update handling of mock to report different timestamps / figure out how to clone + checkpoint afterwards
2.2. Add a duration_since method to the Clock trait, which can be more easily mocked (though still suffers similar issues) - perhaps stealing ideas from LDK

@carlaKC (or perhaps @orbitalturtle, who is currently more active).
What are your thoughts on using Tokio's built-in testing features(such as advance method)?
This approach differs from what you suggested earlier, but it allows us to manage time without relying on mocking.


Update Libraries and General JS maintenance

Update of:

billboard.js
D3.js
fullCalendar
util.js
Dompurifiy

General Code Rework and Maintenance:

Switch from ES5 to ES6
Fix ESLint Error
Update Formatting

Development Done. Will be included in next Release.


Allow layout builder blocks to be translated

Summary
This updates the custom block types to be translatable. This also updates all custom paragraph entities to be translatable. I re-exported the features with the most recent Covid database to capture any overrides that were showing.
A hook_preprocess_block was added to allow the custom and inline block labels to be translated.
Metadata

Question
Answer

Did you use a meaningful pull request title?
yes

Did you apply meaningful labels to the pull request?
yes

Did you perform a self review first?
yes

Documentation reflects changes?
no

CHANGELOG reflects changes?
yes

Unit/Functional tests reflect changes?
no

Did you perform browser testing?
yes

Risk level
Low

Relevant links
RIG-160

@ben-hamelin, I fixed the translation configurations you found and updated the php in the .theme file. As for the metatag overrides. Those all came from exporting out of the covid site. I don't think it will hurt anything having them in the codebase.
With these configuration updates, features:list give us a clean features list:
Philips-MacBook-Pro-2:develop-ecms-profile pfrilling$ ldr fl --bundle=ecms
 ----------------------- ----------------------- -------------- --------- -------
  Name                    Machine name            Status         Version   State
 ----------------------- ----------------------- -------------- --------- -------
  Basic page              ecms_basic_page         Installed      9.x-1.0
  Event                   ecms_event              Installed      9.x-1.0
  eCMS Executive Orders   ecms_executive_orders   Uninstalled    9.x-1.0
  eCMS Hotels             ecms_hotel              Uninstalled    9.x-1.0
  Landing page            ecms_landing_page       Installed      9.x-1.0
  Location                ecms_location           Installed      9.x-1.0
  Notification            ecms_notification       Installed      9.x-1.0
  eCMS Paragraphs         ecms_paragraphs         Installed      9.x-1.0
  Person                  ecms_person             Installed      9.x-1.0
  Press release           ecms_press_release      Installed      9.x-1.0
  eCMS Projects           ecms_projects           Uninstalled    9.x-1.0
  Promotions              ecms_promotions         Installed      9.x-1.0
  eCMS Publications       ecms_publications       Uninstalled    9.x-1.0
  eCMS Speeches           ecms_speeches           Uninstalled    9.x-1.0
  Webform                 webform                 Not exported
  User                    user                    Not exported
  Core                    core                    Not exported
  Site                    site                    Not exported
 ----------------------- ----------------------- -------------- --------- -------

Ok looks good!
/approved


3D Structures Page

Get this page working. Accessed in the notebook from the More menu. There is already a placeholder page. See Strabo Spot 1 for functionality. Uses the 4 forms in assets/forms/three-d-structures.

Added with commit c18975533d2b6de5101ed1ecdfcc829d1f632a52

@nicolasmroberts Are there UI changes you want to make to this? It's pretty much like SS1 now.

@nicolasmroberts Are there UI changes you want to make to this? It's pretty much like SS1 now.

@nicolasmroberts I know @panamint55 wants a compass to show up for 3D Structures. I was going to put this is in but not every 3D Structure has strike/dip or trend/plunge so not sure how to do this yet. And you're probably going to want to change around the UI, adding a modal for quick-entry like the other pages which would incorporate the compass.

Here is the mockup for 3D structure page. Assets coming in new icons package

StraboIcons_18Feb2021.zip
Icons with 3D structure assets ("FoldAttitude_" and "FoldShape" families). "Close" symbol also updated

Related #373

@nicolasmroberts We're missing the image for a dominant fold attitude of 'unknown' and also missing all of the images for dominant hinge shape.

With commit 8a5e1f99a55c2f7951bd5d2cc8aa660f55b311df the rest of the quick entry modal for Folds was fleshed out, including the Compass.

@nicolasmroberts Do we have other quick-entry mockups for Tensor or Other? Right now they're just basic forms for the quick-entry.

@Jessicagood Tensors will stay as it is, because it is a pretty rare one. We will send a mockup for "Other" along with the fold geometry icons for hinge shapes.

@jessicagood Here is a mockup for the "Other" tab within 3D structures.

The "Primary Boudin Layer Plane", "Primary Neckline", and "Secondary Neckline" buttons bring up the compass tab similar to the fold hinge button. The  "Primary Boudin Layer Plane" is a planar feature (Strike and Dip) and "Primary Neckline"/"Secondary Neckline"  are linear (Trend and Plunge).

@jessicagood The new icon package has been added on #385 . It includes the "HingeShape" family of icons.

Added Hinge Shape icons with commits 181c6ae3ede6bfd5c975ebd75253c0ad31eee1a1 and 7654cc6a12afdd6ba7d3ab3dcd908e114fae90dd
@ellennelson10 Still need icon for Fold Attitude of Unknown

Icon for Fold Attitude of Unknown added with commit 180ad41117ab9dd9f574ac51a37ce34654e33d84

Added Other quick entry fields with commit 297211c131c207c038f381ac3d939da879bd1791

Fold Notes are where they are to follow @nicolasmroberts mockup (see above). I can easily move them if you want. Let me know.
When you make a selection on the main page of the Quick Entry Modal the fields shown on the next page are all the fields relevant to the initial field that was selected. So when mullion is selected as a 3D Type all relevant fields are shown on the next page. I can make it so that for 3D Type only the choices for the 3D Type itself are shown on the next page. But then you would never see fields relevant to Lobate-Cuspate or other 3D structure. In order to maintain consistency, for all 3D Types we should either show all relevant fields or show no relevant fields (only the choices for 3D Type itself). This may be a little confusing but which way do you think it should be?
Do you want any fields to show up for Lobate-Cuspate or 'other 3D structurein the main page of the Quick Entry Modal? Onlyboudinagewas illustrated above andmullion` is similar.

Yes, please move the field notes to the bottom of the page.
All 3D types should show no relevant fields until the main page, I included a video attempting to articulate the workflow for that page more clearly. I also did a mockup of the Lobate-Cuspate and other 3D structure fields for the main page which hopefully mitagates the need to show the relevant fields on the 3D type page.

RPReplay_Final1644957528.mov.zip

Fixed with 8b88eabd2dbb4f7f4e9246f10a6a91c6efc3020f. We should be able to close this after you check the next release @ellennelson10.

@jessicagood I have a couples changes for the 3D structure tab. First, we want to move "tensor" to be part of the "other" section. I attempted to make this change in the Kobo forms, but please let me know if there is something I need to fix on that end. Second, we want to add a "fault" section. It will be redundant to the planar measurement tab, but having it in 3D structures would be useful as well. Again, I added this to the Kobo forms.

I can easily add Fault to 3D Structures but if we remove tensor as a primary type of 3D Structure and move it under Other we will lose the data for where the tensor is already set as a primary 3D Structure. We can have it in both places or see how many people have used tensors or add another section for Tensors (Deprecated). @panamint55 What do you think?

I would say that we see how many are there.  I bet it is none.  If that is the case then we can do the change easily.
What is the reason to remove tensor as a primary structure?
From: Jessica Good @.>
Reply-To: StraboSpot/StraboSpot-Mobile @.>
Date: Thursday, March 31, 2022 at 4:09 PM
To: StraboSpot/StraboSpot-Mobile @.>
Cc: Doug Walker @.>, Mention @.***>
Subject: Re: [StraboSpot/StraboSpot-Mobile] 3D Structures Page (#207)
I can easily add Fault to 3D Structures but if we remove tensor as a primary type of 3D Structure and move it under Other we will lose the data for where the tensor is already set as a primary 3D Structure. We can have it in both places or see how many people have used tensors or add another section for Tensors (Deprecated). @panamint55https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fpanamint55&data=04|01|jdwalker%40ku.edu|6a52c83a2868489689d508da135acaa3|3c176536afe643f5b96636feabbe3c1a|0|0|637843577915558733|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000&sdata=dvTRVVQiIz%2FpF0Bl0mG2EPYYov1Deb2w4N7E0C4KA8o%3D&reserved=0 What do you think?
—
Reply to this email directly, view it on GitHubhttps://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FStraboSpot%2FStraboSpot-Mobile%2Fissues%2F207%23issuecomment-1085119184&data=04|01|jdwalker%40ku.edu|6a52c83a2868489689d508da135acaa3|3c176536afe643f5b96636feabbe3c1a|0|0|637843577915558733|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000&sdata=P422yn5%2Ffp2QxJv5ONsMKjr2y%2Fhrgd0DnnaS%2FKNmAmg%3D&reserved=0, or unsubscribehttps://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FACG2MN6VFS3KJQNQE2MEYI3VCYIBZANCNFSM4ULCDJZQ&data=04|01|jdwalker%40ku.edu|6a52c83a2868489689d508da135acaa3|3c176536afe643f5b96636feabbe3c1a|0|0|637843577915558733|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000&sdata=C91OwESZx8BH1hRg2XQoF7wtumMJrr%2Fm1EqF0isG%2Bns%3D&reserved=0.
You are receiving this because you were mentioned.Message ID: @.***>

@panamint55 I moved it to "Other" because I don't think the Tensor category is heavily used. It seems reasonable to have it in the "Other" tab instead of at the same level as faults and folds. That being said I didn't realize that it was considered a "primary feature" and wouldn't see any issue with it being [folds][faults][tensors][other].

@ellennelson10 So should we leave it as is or find out how many people are already using it to see if it's even possible to change?

Ellen will take a look.  It is fine to move tensor under other.  Faults will be added with graphic interface.

Let's check and see if it is used yet.  So go with the 8/23 comment.

@jasonash says 65 spots use tensors
So @ellennelson10 do think there is a good enough reason to switch the field organization here and lose that data (or go through too much work to try and save the data)?

No, it likely isn't worth losing data. So it will be four tabs of "Fold", "Fault", "Tensor", and "Other".

Added Faults with commit 5a76567a2c1568ebc9615ad5b8bce15db8278d05
Once this comes out in the next release is it good to close @ellennelson10?

@jessicagood Yes it will be good to close.


add version to clues, log cli command and flags

Does this PR need a docs update or release note?

[x] :no_entry: No

Type of change

[x] :broom: Tech Debt/Cleanup

Issue(s)

#2329

Test Plan

[x] :muscle: Manual

Removed the code that added version to clues. Going to queue @ryanfkeepers

Added the version to information getting logged.


GraphRAG performance enhacements

Issue: When property graph store gets filled (~12K nodes, 15K relationships) insertion time in dataprep gets slow.
Extraction + insertion starts at ~30 sec and once it gets filled grows to (~12K nodes, 15K relationships) ~800 sec
Perf bottleneck this cypher call in llama-index to do node upsert:
https://github.com/run-llama/llama_index/blob/795bebc2bad31db51b854a5c062bedca42397630/llama-index-integrations/graph_stores/llama-index-graph-stores-neo4j/llama_index/graph_stores/neo4j/neo4j_property_graph.py#L334
WIP solution:

mode initialization out of detaprep and retrieve function so only performed once
...

There are lot of dataprep backends and neoj4/llama is not the default one used in docker compose files and Helm charts.
Do the ones used by default have also similar bottleneck?


[✨ Improvement] Remove or replace old/useless libraries , improve data returned by lib

This pull request introduces several improvements to the src/index.ts file:

Dependency Updates: Replaced axios with the fetch API for HTTP requests and updated the XML parsing library to 'fast-xml-parser', also removed lodash as it is kinda useless in the kinds.
Code Refactoring: Streamlined and enhanced the parseArxivObject and parseTag functions for better error handling and simplicity.
XML Parsing Optimization: Implemented the 'fast-xml-parser' library for more efficient and reliable XML parsing in the search function.

Additional Information: The search function now returns an object with totalResults, startIndex, itemsPerPage, and an array of parsed entries
Overall all these changes where made in an effort to minimize the dependency footprint of the library

Thank you for the good patch!!

You're welcome :)


Mahja/master

Latest improvements:
MSFT employees can try out our new experience at OpenAPI Hub  - one location for using our validation tools and finding your workflow.

Contribution checklist:

[ ] I have reviewed the documentation for the workflow.
[ ] Validation tools were run on swagger spec(s) and have all been fixed in this PR.
[ ] The OpenAPI Hub was used for checking validation status and next steps.

ARM API Review Checklist

[ ] Service team MUST add the "WaitForARMFeedback" label if the management plane API changes fall into one of the below categories.
adding/removing APIs.
adding/removing properties.
adding/removing API-version.
adding a new service in Azure.

Failure to comply may result in delays for manifest application. Note this does not apply to data plane APIs.

[ ] If you are blocked on ARM review and want to get the PR merged urgently, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.
Please follow the link to find more details on API review process.

Automation for azure-sdk-for-ruby

Automation for azure-sdk-for-python

Automation for azure-sdk-for-java

Can one of the admins verify this patch?

Automation for azure-sdk-for-js

Automation for azure-sdk-for-go

@antmarti-microsoft I and @roramc have replied to your comments. Please have a look.

I have approved this change. But since this is a breaking change, per ARM guidelines I have added ARM feedback label


README corrections

There were some texts and links that weren't updated correctly

Thank you! That was the hot needle in action... 🤦♂🤓


DNSSEC Claim flow

The button get's misaligned here. For some reason the Container component isn't fully rendered?


Controls Lagging - 2023 Hyundai Santa Cruz

Describe the bug
Roughly once per day will receive the error "Controls lagging, take control" (paraphrased). However will continue to work with error subsiding very quickly.
Which car does this affect?
2023 Hyundai Santa Cruz
Provide a route where the issue occurs
https://connect.comma.ai/099fdbcfdfbba538/1710109177530/1710109206715
openpilot version
4b93a6417c1a8e6c02e2e081e163a0cd380cc4ba
Additional info
This isn't specific to this commit, has been occurring for some time in my parent's vehicle. They've been running a fork with the issue but I switched them to master-ci yesterday and it's still occurring.

A couple more segments with the issue: 099fdbcfdfbba538/00000034--1dafec9b74/47
099fdbcfdfbba538/00000032--a0548890bf/45

As an update, I've replaced the usb-c cable with another shipped from China and it has no effect on the issue occurring. Next I may try another harness box I have but it will be a couple weeks.

Tracking in #32286