Support rearranging notebook cells

This adds support for moving notebook cells around and having datasets that reference them keep working.  It does this by serializing the cell index and using the cell UUID internally so it doesnt change on cell moves.

OK this is working now. We see in this demo we move a cell in a notebook, and when we reload. the page the view of that cell points to the new cell:

OK this also adds support for displaying child datasets in the data browser. This lets us move through notebook cells and see the relevant data registry viewers in the right hand side:

@kgryte this is good to go from my perspective. It's a pretty big PR. Would you like to do any review before I merge it?


Improve perf support

This modifies and cleans up perf support a bit, with biggest change being including BSD-3 jitdump.h replacement I've implemented basing on format documentation by Stephane Eranian (Thanks!).

I haven't tested this on anything else than linux.

The travis test discovered some issues, can you please have look?
Thanks!

I have taken the PR; see f9bf527 for the adjustments (perhaps one may read the commit log). Please verify and readjust as necessary.

Thanks! I've already finished my internship, but could have done it if not for the fact I've been in Mexico for last 2 weeks, without my laptop. Thanks for handling this!


Update "Read-eval-print-loop" section with information about Node compatbility

REPL supports running in compatibility mode (deno repl --compat --unstable), but there
are currently no information about it on the page<EMAIL_ADDRESS>We should add following info:

that --compat is supported
that require and Node resolution is available
that built-in Node.js modules are already loaded: https://github.com/denoland/deno/pull/13127

The --compat flag has been dropped from Deno. This issue should probably be closed.


Liquibase locked, how to resolve? Using latest compreface.

Describe the bug
compreface-admin          | 2023-10-04 15:02:42.781  INFO 7 --- [           main] liquibase.lockservice                    : Waiting for changelog lock....
compreface-ui             | 2023/10/04 15:02:51 [error] 27#27: *1 connect() failed (111: Connection refused) while connecting to upstream, client: 192.168.
To Reproduce
Steps to reproduce the behavior:
Don't know
Expected behavior
Not to give that error
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):

OS: [e.g. iOS]
Browser [e.g. chrome, safari]
Version [e.g. 22]

Logs
Run those commands and attach result to the ticket:
docker ps
docker-compose logs
Additional context
Add any other context about the problem here.

@pospielov Not sure how this happened - i think i need to unlock the postgres db ? How does one do this ?

Ok i resolved this by doing:
docker exec -it containerid /bin/bash
pqsql -u psql
\c frs
UPDATE DATABASECHANGELOGLOCK SET LOCKED=FALSE, LOCKGRANTED=null, LOCKEDBY=null where ID=1;
and i could login again.

For anyone running postgresql in a container that isn't compreface I ran this command
docker exec -it POSTGRESQL_CONTAINER_NAME psql -U compreface -d compreface -c "UPDATE DATABASECHANGELOGLOCK SET LOCKED=FALSE, LOCKGRANTED=null, LOCKEDBY=null WHERE ID=1;"

Thanks, this got me going again


Performance of find EHR by subject-id

Background
We have been conducting load tests to determine the capabilities of EHRbase and the configuration required to support one of our national workloads.
The test dataset consists of:

~ 6 million EHRs
Each EHR has 1 - 6 compositions with 75% of EHRs having 6 compositions
~ 31 million compositions

Performance of find EHR
During the course of our load testing we found the "find EHR" request (OpenEHR query GET /ehr?subject_id={id}&subject_namespace={namespace}) to have response times significantly poorer than other requests in the workload.
The following table is an extract from our test results showing 95%-ile response times at different traffic loads.

users/sec
find comp (aql)
find EHR
post comp

10
449ms
1281ms
299ms

20
608ms
2616ms
403ms

30
835ms
8139ms
568ms

40
1221ms
22219ms
726ms

Cause
The cause appears to be the SQL generated from EHRbase and sent to Postgres can't make use of any of the indexes on the party_identified table as only values for the party_ref_namespace and party_ref_value fields are provided from the original REST request (as defined by the OpenEHR standard).  Therefore, Postgres performs a full table scan and thus the poor response times.
Available indexes to query:
Indexes:
    "party_identified_pkey" PRIMARY KEY, btree (id)
    "ehr_subject_id_index" btree (jsonb_extract_path_text(js_party_ref(party_ref_value, party_ref_scheme, party_ref_namespace, party_ref_type)::jsonb, VARIADIC ARRAY['id'::text, 'value'::text]))
    "party_identified_party_ref_idx" btree (party_ref_namespace, party_ref_scheme, party_ref_value)
    "party_identified_party_type_idx" btree (party_type, name)

Query plan showing how Postgres would execute query:
explain (analyze) select "ehr"."party_identified"."id", "ehr"."party_identified"."name", "ehr"."party_identified"."party_ref_value", "ehr"."party_identified"."party_ref_scheme", "ehr"."party_identified"."party_ref_namespace", "ehr"."party_identified"."party_ref_type", "ehr"."party_identified"."party_type", "ehr"."party_identified"."relationship", "ehr"."party_identified"."object_id_type" from "ehr"."party_identified" where ("ehr"."party_identified"."party_ref_namespace" = '--------' and "ehr"."party_identified"."party_ref_value" = '--------') limit 1;
                                                                 QUERY PLAN
--------------------------------------------------------------------------------------------------------------------------------------------
 Limit  (cost=1000.00..159330.35 rows=1 width=164) (actual time=1478.354..1479.954 rows=1 loops=1)
   ->  Gather  (cost=1000.00..159330.35 rows=1 width=164) (actual time=1478.352..1479.948 rows=1 loops=1)
         Workers Planned: 2
         Workers Launched: 2
         ->  Parallel Seq Scan on party_identified  (cost=0.00..158330.25 rows=1 width=164) (actual time=1202.982..1202.984 rows=0 loops=3)
               Filter: ((party_ref_namespace = '--------'::text) AND (party_ref_value = '--------'::text))
               Rows Removed by Filter: 1999983
 Planning Time: 0.429 ms
 Execution Time: 1480.017 ms
(9 rows)

Proposed solution
We would suggest adding a new index to the party_identified table that can be used by the query.
Indexes:
    ...
    "party_identified_namespace_value_idx" btree (party_ref_namespace, party_ref_value)

Results of proposed solution
We implemented the change and could see the difference in the Postgres query plan:
explain (analyze) select "ehr"."party_identified"."id", "ehr"."party_identified"."name", "ehr"."party_identified"."party_ref_value", "ehr"."party_identified"."party_ref_scheme", "ehr"."party_identified"."party_ref_namespace", "ehr"."party_identified"."party_ref_type", "ehr"."party_identified"."party_type", "ehr"."party_identified"."relationship", "ehr"."party_identified"."object_id_type"  from "ehr"."party_identified" where ("ehr"."party_identified"."party_ref_namespace" = '--------' and "ehr"."party_identified"."party_ref_value" = '--------') limit 1;
                                                              QUERY PLAN
--------------------------------------------------------------------------------------------------------------------------------------
 Limit  (cost=0.56..8.58 rows=1 width=164) (actual time=0.052..0.055 rows=1 loops=1)
   ->  Index Scan using gf_test_idx on party_identified  (cost=0.56..8.58 rows=1 width=164) (actual time=0.049..0.050 rows=1 loops=1)
         Index Cond: ((party_ref_namespace = '--------'::text) AND (party_ref_value = '--------'::text))
 Planning Time: 0.188 ms
 Execution Time: 0.079 ms

We re-ran our load tests with the additional index.  The following table is an extract from our test results showing 95%-ile response times at different traffic loads.

users/sec
find comp (aql)
find EHR
post comp

10
417ms
209ms
300ms

20
559ms
225ms
301ms

30
669ms
292ms
357ms

40
786ms
341ms
420ms

You can see the change lead to huge improvements to the response time of the "find EHR" request. Another benefit is that as a the DB was generally less busy and we saw improvements in the response times of the other requests in the test also.

@grantforrester-nes
Thanks for you contribution.
By the way you might want to rest on the soon to be released 0.21.0. Should give even better performance.


Updates to forgotten password styling

See  https://github.com/wagtail/wagtail/issues/6736

Changes the text from 'Forgotten it?' to 'Forgotten password' to improve accessibility and make sense when positioned outside the password field
Displays the link below the form at mobile, with white text for the link
Improves the styling of the link from tablet up - this is positioned relative to a new div so that its position is still correct even if the 'incorrect login' message is showing

Do the tests still pass? (https://docs.wagtail.io/en/latest/contributing/developing.html#testing) To check.
Does the code comply with the style guide? (Run make lint from the Wagtail root) To check.
For front-end changes: Did you test on all of Wagtail’s supported browsers? Please list the exact versions you tested.  Browser testing to come.
For new features: Has the documentation been updated accordingly? Doc updates to come - screenshots may need updating.

There are multiple django.po files with the 'Forgotten it?' text. Assuming the new wording is approved what is the process for updating these?

@helenb You don't need to update the django.po files - we'll rebuild them before the next release (usually when the release candidate comes out, if not earlier).

@helenb You don't need to update the django.po files - we'll rebuild them before the next release (usually when the release candidate comes out, if not earlier).

Ah - that's good to know - thanks @gasman

I spotted that in all versions of Safari, both desktop and mobile, you cannot tab onto the forgotten password link. This is a current issue and not introduced by this PR though.

@thibaudcolas would welcome a review if you have time.


[meta] Rearrange readme

Supersedes https://github.com/doitsujin/dxvk/pull/4123

Rearrange the readme so the entries are consistently listed in a given section where it makes sense. They are ordered from project info -> usage -> building -> native.
Moved up Online multi-player games so it sits near the start of the How to use section
Also moved up HUD above Logs since it is mentioned under How to use so you don't have to scroll far.
Change Troubleshooting to a Build troubleshooting subsection under Build instructions.
Added a DLL dependencies subsection under How to use.
Remove Setup has to be done manually in this case. under Compiling manually as i believe it is a reference to the old build script.
Add a missing d3d8 in the same subsection and rearrange the API mentions so they consistently go from lowest to highest.

Rendered version https://github.com/Blisto91/dxvk/blob/readme-boomboomboom/README.md

I think the interoperability between dxvk's dxgi.dll and vkd3d-proton also should be mentioned.
Also maybe the Vulkan 1.3 requirement.

By the way, the GitHub repository's description should be changed as it currently says:

Vulkan-based implementation of D3D9, D3D10 and D3D11 for Linux / Wine

It might be worth mentioning Windows support while we're at it :slightly_smiling_face:


collapse Key is not getting changed, I'm sending payload with different collapseKey but it's not changin in client side

const message = {
  token: "apk_token",
  notification: {
    // body: "This is an FCM notification that displays an image!",
    title: "FCM Notification",
  },
  android: {
    collapseKey: "123",
    priority: "normal",
    restrictedPackageName: "com.newnot",
    data: { name: "pathu" },
  },
};

admin
  .messaging()
  .send(message)
  .then((response) => {
    console.log("Successfully sent message:", response);
  })
  .catch((error) => {
    console.log("Error sending message:", error);
  });

Sorry for the delay in reply.  For this type of issue investigation I'd recommend filing a Firebase support ticket from https://firebase.google.com/support/troubleshooter/contact . Thanks!


OpenAI APIs for TTS/STT?

Is there (a plan for) a way to use the OpenAI servers for STT/TTS? They are fairly slow, unfortunately, but they might be a good option for some people.

It's not exactly impossible but it hasn't been a focus because as you say it's quite slow - to the point of going against our mission of an Alexa-competitive voice interface.
Willow has a fairly unique streaming method to WIS. I'm not completely familiar with the OpenAI speech API but at best you'd almost certainly need a proxy of some sort, and if you were doing advanced things like audio compression (AMR) you'd need to do more.

Makes sense, thank you.

I'd like to revisit this now with GPT-4o being out, the multimodal functionality of sending the audio directly to the model and getting audio back might be interesting. Are there any plans for WIS to send the audio to the REST endpoint directly, and receive audio back?


JS error in Safari: TypeError: undefined is not an object (evaluating 't.path.some')

Hi!
In Safari I get this error: TypeError: undefined is not an object (evaluating 't.path.some'), clickable-table-row:35.
How can I fix it?
Thanks!

I have noticed this also happening on firefox


Getting a 500 when adding an image from a field using the "AWS S3 for Craft" plug in

This code works great:
{% set offset = offset ?? 0 %}
{% set entryQuery = craft.entries.section('news').offset(offset).limit(limit) %}
{% set entries = entryQuery.all() %}

  {% for entry in entries %}

{{ entry.title }}

		<time datetime="{{ entry.postDate|date('Y-m-d') }}">{{ entry.postDate|date('M d, Y') }}</time>

	{% if entry.newsSummary|length %}
		{{ entry.newsSummary }}
	{% else %}
		{{ entry.newsContent }}
	{% endif %}

  {% endfor %}

  {% if entryQuery.count() > offset + (entries|length) %}
    <button class="btn btn--outline"
      id="load-more-oob"
      sprig
      s-val:offset="{{ offset + limit }}"
      s-select="li"
      s-target=".about__news__list"
      s-swap="beforeend"
      {{ sprig.trigger == 'load-more-oob' ? 's-swap-oob="true"' }}>
      Load more
    </button>
  {% else %}
    <button id="load-more-oob" s-swap-oob="true" style="display: none"></button>
  {% endif %}

But if I add this in the entries loop above, I get a 500 error

I'm assuming it's because the S3 images have not been fetched or something like that? Is there a way around this?
Thanks!

This is almost certainly an error in your Twig code. What does the body of the 500 response contain when devMode is enabled?

Please open the response tab of the network request (generally under Network in the browser's dev tools), where you should see a helpful error. My guess is that you're calling .url on a null value, because the image doesn't exist.

You were right… Thanks for helping me figure this out and sorry to bug you. Had nothing to do with your plug in… I should have figure this out myself!

No problem!


When matching fits files: "ValueError: Big-endian buffer not supported on little-endian compiler"

Dear all,
thanks for providing this well documented package, it seems just what I need to align some images I have for a project with students.

I tried the demo notebook, all seems to work fine without any trouble.

I am running the most recent version of astroalign (2.2).

However  I tried to align two sets of two images, two images of 47 tuc, two images of the helix nebulae. For 47 tuc where there are lots of stars it should surely work!

Instead I get this message about 'Big-endian buffer not supported on little-endian compiler'.

As far as I can tell, the shapes of the input arrays from fitsio are fine. I suspect this is hiding something else. I get the same error on macos as on a linux system.  Surely I am making some simple mistake here?
Many thanks!
Henry
image_file = os.path.join(data_dir,'calibrated-T30-fetedelascience-NGC104-20201119-230656-R-BIN1-W-300-001.fit')
source=fits.open(image_file)[0].data

target_file = os.path.join(data_dir,'calibrated-T30-fetedelascience-NGC104-20201119-231248-R-BIN1-W-300-002.fit')
target=fits.open(target_file)[0].data

registered_image, footprint = aa.register(target, source)

ValueError                                Traceback (most recent call last)
<ipython-input-9-aea43f655c9d> in <module>
----> 1 registered_image, footprint = aa.register(target, source)

~/miniconda3/envs/py37-astropy/lib/python3.7/site-packages/astroalign.py in register(source, target, fill_value, propagate_mask, max_control_points, detection_sigma, min_area)
    453     )
    454     aligned_image, footprint = apply_transform(
--> 455         t, source, target, fill_value, propagate_mask
    456     )
    457     return aligned_image, footprint

~/miniconda3/envs/py37-astropy/lib/python3.7/site-packages/astroalign.py in apply_transform(transform, source, target, fill_value, propagate_mask)
    384         cval=_np.median(source_data),
    385         clip=True,
--> 386         preserve_range=True,
    387     )
    388     footprint = warp(

~/miniconda3/envs/py37-astropy/lib/python3.7/site-packages/skimage/transform/_warps.py in warp(image, inverse_map, map_args, output_shape, order, mode, cval, clip, preserve_range)
    877                 warped = _warp_fast[ctype](image, matrix,
    878                                            output_shape=output_shape,
--> 879                                            order=order, mode=mode, cval=cval)
    880             elif image.ndim == 3:
    881                 dims = []

skimage/transform/_warps_cy.pyx in skimage.transform._warps_cy._warp_fast()

ValueError: Big-endian buffer not supported on little-endian compiler

Hi @hjmcc,
The problem seems to be in the wheels installation for scikit-image.
Or maybe the data on the fits file is saved with a different endian-ness than the local machines.
I found this to swap endian-ness.
Apparently, if you do:
target = target.newbyteorder()
source = source.newbyteorder()

before registering, it should correct the problem.
I certainly never saw this problem before, so please let me know if this fixes it! :)

hi @martinberoiz,
Thank you for this super-rapid response!

It's strange, your demo notebook works perfectly.   I tried passing a higher threshold to SEP, but it still crashes.
Is there something wrong with my conda installation? Or perhaps I should just try with two images with only stars and galaxies.
Thanks!

hi @martinberoiz I did some more experiements on my side with some other data I had. It worked fine in that case. Looking more closely, I noticed that those data were dtype=uint16 whereas the data I had been using were dtype=float32.
So now if I do
registered_image, footprint = aa.register(source.astype('uint16'), target.astype('uint16'))
It works ! So my conclusion is that something somwhere is expecting dtype=uint16 .
I guess we can close the issue.

Hi,
To be honest, that seems strange to me. Images should work with int's or floats.
Let's close this issue for now and if it reappears, feel free to open a new issue.
BTW if you don't mind sharing a few of the problem images for me to try out, you can send them to my gmail account.
Thanks!

@martinberoiz I am also facing this issue while aligning images.
import numpy as np
import astroalign as aa

from astropy.io import fits

coo_ref = np.genfromtxt('AS1A02_028T03_9000000788uvtFIIPC00F1A_l2imb_coo.dat', delimiter=',')
coo_to_match = np.genfromtxt('AS1A02_028T03_9000000788uvtNIIPC00F2A_l2imb_coo.dat', delimiter=',')
transf, (source_list, target_list) = aa.find_transform(coo_ref, coo_to_match)

data_ref = fits.open('AS1A02_028T03_9000000788uvtFIIPC00F1A_l2imb.fits.gz')
data_to_match = fits.open('AS1A02_028T03_9000000788uvtNIIPC00F2A_l2imb.fits.gz')

registered_image = aa.apply_transform(transf, data_ref[0].data, data_to_match[0].data)

---------------------------------------------------------------------------
ValueError                                Traceback (most recent call last)
<ipython-input-22-d36cdadc22fb> in <module>
----> 1 aa.apply_transform(transf, data_ref[0].data, data_to_match[0].data)

~/.local/lib/python3.8/site-packages/astroalign.py in apply_transform(transform, source, target, fill_value, propagate_mask)
    372         target_data = target
    373
--> 374     aligned_image = warp(
    375         source_data,
    376         inverse_map=transform.inverse,

~/.local/lib/python3.8/site-packages/skimage/transform/_warps.py in warp(image, inverse_map, map_args, output_shape, order, mode, cval, clip, preserve_range)
    875             ctype = 'float32_t' if image.dtype == np.float32 else 'float64_t'
    876             if image.ndim == 2:
--> 877                 warped = _warp_fast[ctype](image, matrix,
    878                                            output_shape=output_shape,
    879                                            order=order, mode=mode, cval=cval)

skimage/transform/_warps_cy.pyx in skimage.transform._warps_cy._warp_fast()

ValueError: Big-endian buffer not supported on little-endian compiler

Hi @prajwel,
Did you try byte-swapping before aligning?
data_ref = data_ref.newbyteorder()
data_to_match = data_to_match.newbyteorder()

registered_image = aa.apply_transform(transf, data_ref[0].data, data_to_match[0].data)

I'm still investigating this, seems like it's an issue with scikit-image.

I tried it but received the following error.
data_ref = data_ref.newbyteorder()
data_to_match = data_to_match.newbyteorder()

---------------------------------------------------------------------------
AttributeError                            Traceback (most recent call last)
<ipython-input-4-27c60e5640d6> in <module>
----> 1 data_ref = data_ref.newbyteorder()
      2 data_to_match = data_to_match.newbyteorder()

AttributeError: 'HDUList' object has no attribute 'newbyteorder'

Oh, glad to hear it worked in the end.


First proofreading for Pepper Course Lesson 1-3

@scribblemaniac Thank you very much for proofreading! I have a few possible corrections in the translations, but I think it would be better to discuss them in separate commit. Merging now. ^__^

@scribblemaniac @Stas-Kholodilin I have made some edits here - https://github.com/morevnaproject/subtitles-translation/commit/6d0f23668393ecf1c633b477ea1a43e3d1e2e91f
Please take a look. ^__^

@scribblemaniac Can you please take a look at pepper-course-lesson-4.msrt as well? ^__^


feat(pipettes): add tip sense check to the sensor hardware class

Overview
Tip sensing falls more under the category of general sensor hardware. The pin configurations are also more conducive to having "multiples" of the tip sense. The next bit of work will involve setting up a task that can fire off tip presence data once a state change has been detected.
Some notes for next steps. For single/eight channel the ejector stage flag is active when in 'resting' position. For ninety-six the ejector stage flag is inactive when in 'resting' position.
The ninety six channel tip presence routine will be much more involved than the single/eight because it involves moving the pick up motors slightly 😞

Codecov Report

Merging #588 (4458d00) into main (250d327) will decrease coverage by 0.03%.
The diff coverage is 0.00%.

@@            Coverage Diff             @@
##             main     #588      +/-   ##
==========================================
- Coverage   84.28%   84.26%   -0.03%
==========================================
  Files          83       83
  Lines        2966     2967       +1
==========================================
  Hits         2500     2500
- Misses        466      467       +1

Impacted Files
Coverage Δ

include/sensors/core/sensor_hardware_interface.hpp
100.00% <ø> (ø)

include/sensors/tests/mock_hardware.hpp
84.21% <0.00%> (-4.68%)
:arrow_down:

include/can/core/messages.hpp
99.21% <0.00%> (ø)


AGC reference to docs

Checklist

[ ] The title of the PR is clear and informative
[ ] If applicable, the changes made in the PR have proper test coverage
[ ] Issues addressed by the PR are mentioned in the description followed by Fixes.

Description
Reference AGC updates.
Fixes

Not getting rendered as expected.


Errors happen when doing make test

I plan to migrate these data structures to hpx [https://github.com/STEllAR-GROUP/hpx] (a GSoC project).
I want to test the performance of libcds, so I run these test cases in test directory.
Unfortunately, there are some scenarios cannot pass the tests, I guess maybe I adopt a un-correct method to compile libcds.
The following tests FAILED:
         31 - unit-set-skip (OTHER_FAULT)
         33 - unit-set-split-lazy (SEGFAULT)
         38 - unit-tree (SEGFAULT)
         40 - stress-map-delodd (OTHER_FAULT)
         41 - stress-map-del3 (OTHER_FAULT)
         42 - stress-map-find-string (OTHER_FAULT)
         43 - stress-map-insdel-func (OTHER_FAULT)
         44 - stress-map-insdel-string (OTHER_FAULT)
         45 - stress-map-insdel-item-int (OTHER_FAULT)
         46 - stress-map-insdelfind-hp (OTHER_FAULT)
         48 - stress-map-minmax (OTHER_FAULT)
         49 - stress-map-iter-erase (OTHER_FAULT)
         50 - stress-pqueue (OTHER_FAULT)
         51 - stress-queue-pop (SEGFAULT)
         52 - stress-queue-push (SEGFAULT)
         53 - stress-queue-push-pop (SEGFAULT)
         54 - stress-queue-random (OTHER_FAULT)
         57 - stress-set-delodd (OTHER_FAULT)
         58 - stress-set-del3 (SEGFAULT)
         59 - stress-set-insdelfind-hp (OTHER_FAULT)
         62 - stress-set-insdel-func (OTHER_FAULT)
         63 - stress-set-insdel-string (OTHER_FAULT)
         64 - stress-set-iteration (SEGFAULT)
         65 - stress-set-iter-erase (SEGFAULT)
         66 - stress-stack (OTHER_FAULT)

There are three main factors to cause errors.
1. *** Error in `/home/mateng/GSoC/libcds-release/bin/unit-tree': malloc(): smallbin double linked list corrupted: 0x00000000035e1370
 ***
2. *** Error in `/home/mateng/GSoC/libcds-release/bin/stress-map-iter-erase': malloc(): memory corruption (fast): 0x00002ba53801d510
3. *** Error in `/home/mateng/GSoC/libcds-release/bin/stress-pqueue': corrupted size vs. prev_size: 0x0000000000ddaae0 ***

So can someone help me to solve these issues? I will be appreciated.

How do you compile the library?

I first run cmake . and make a new release directory. Then I make all to install this library.
These are configurations.
Build type -- RELEASE
Compiler version: GNU 4.8.5
System: Linux version: 3.13.0-35-generic
Target architecture: x86_64
Compiler flags:  -O3 -DNDEBUG -std=c++11;-mcx16 -Wall;-Wextra;-pedantic
Exe flags:
-- Boost version: 1.60.0
-- Found the following Boost libraries:
--   system
--   thread
--   chrono
--   date_time
--   atomic
Boost: 1_60 in /home/mateng/boost/boost_1_60_0, lib /home/mateng/boost/boost_1_60_0/stage/
lib
GTest: /usr/include, lib: /usr/local/lib/libgtest.a

Hmm... Your trouble is a surprise for me... I have no reasonable answer.
To find solution, get latest Clang or GCC, build libcds with asan instrumentation and run the test.


Validate RefType in case of „instance of object uri”

What is the current behavior?
RefType attribute of ObjectId is not valided.
What is the expected behavior?
Support URL validation, in case RefType has the value „instance of object uri”
What is the motivation / use case for changing the behavior?
URL specification is provided in DIN SPEC 91406:2019-12. In 2022, the international standard prEN IEC 61406:2022 "Identification Link" has been published that is based on the DIN SPEC.
A reference implementation of the validation is provided by @Brezel31 at https://github.com/Brezel31/URL_Check_IEC61406. This code can be the basis for the validation code.

added first implementation
@Brezel31 : Could you review  the code? I did not implement domain checks by API calls
@Brezel31 Could you please provide Chinese translations for the following strings. Thank you.

ObjectId_VAL3=OI_003 Identification Link: id is not a valid URL.
ObjectId_VAL4=OI_004 Identification Link: Uppercase letters are only allowed in the ,  and  components.
ObjectId_VAL5=OI_005 Identification Link: URL should not be extended beyond a length of 100 characters.
ObjectId_VAL6=OI_006 Identification Link: URL shall not be longer than 255 characters.
ObjectId_VAL7=OI_007 Identification Link: URL May contain punycode.
ObjectId_VAL8=OI_008 Identification Link: Invalid character in place: {0} - {1}.

updated documentation.
waiting for final Chinse translation

Received missing translations. Thanks to @Brezel31

Feature merged


NAV-ISS-21 Fix/Clean up Sensor Proto

Looks like we are using incorrect data types for some of the fields.

Ie. gps magnetic_var_sense and gps_latitude_loc etc.

Note - after updating Sensor proto, remember to update dependent files as well.
This includes:

uri.h
uri.py
Help.h
Help.py


[Feature]: add a new split combinator that is capable of splitting the input by a known delimiter

Describe your feature
Add a Split combinator that provides a shortcut to splitting a string by a known delimiter. This should be a greedy combinator that will keep splitting until either the end of a line or the end of the input text. It should expect to split at least once.
Add a SplitN combinator that defines an expectation on the number of times the input should be split. Constraining the combinator.
Any additional information?
No response
Code of Conduct

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

In hindsight, this parser is too greedy and requires many side effects to be useful.


Document the KubeStellar upgrade procedure

Create a documented procedure on how users with existing KS environment can upgrade to a new KS version.  This should include all components (KubeFLex, WECs, agents on WECs, registration, etc..)

This is how OCM handles upgrades: https://open-cluster-management.io/getting-started/administration/upgrading/ As long as we don't change the API and break backwards compatibility we can potentially do something similar.

Upgrading in place only makes sense when there is "backward" compatibility. And this gets really exciting when we have dependency cycles.


In skillmap, "View Code" on finished card brings up blank code editor

Describe the bug
Once a card has been completed, clicking "View Code" takes user to a code editor without porting in their code.
To Reproduce
Steps to reproduce the behavior:

Add some code to a card in a skillmap, then complete it by going to the last bubble and clicking "finish"
Return to skillmap
Click on finished card to reveal button options
Click "View Code"

Expected behavior
This should open all the code I was working with from that card up until that point into the Code Editor as a new project.
Desktop (please complete the following information):

Windows 10
Chrome
Latest Version

should be fixed by https://github.com/microsoft/pxt/pull/7669, reopen if the bug returns


RFC: Colocate selectors and reducers

This RFC gets rid of the selectors/ folder and adds selectors.js/selectors.test.js files to the two containers with reducers, containers/App/ and containers/HomePage.

Inspired by a Dan Abramov tweetstorm, I think that co-locating selectors with reducers makes a lot of sense.
I don't think that putting them in the same file is necessary, since that file will explode in size and become unmanageable (see: ducks), but having them right next to the reducer makes so much more sense imo than having them in a selectors/ folder.
Also note that with #299, we would have neither a sagas/ nor a selectors/ folder, and I think that's amazing.
What do you think?
I like this a lot, but I haven't properly worked with it. One thing that's a bit weird is the locationSelector that now lives in containers/App/selectors.js, but is only used in the main app.js. Any ideas?
Todo before merging: Fix generators/templates, just wanted to get this RFC out.

In my own App I changed selector names : for instance, loadingSelector becomes  selectLoading which sounds like a getter while still keeping the idea of selectors which can be composed. Just my personnal feeling.

Solid thumbs-up from me.

Nice change!
I really like the idea of 'selectSomething' compared to 'somethingSelector'.
In the apps that I built we had selectors that have been used by multiple containers/selectors. Where would you recommend to put shared selectors?

about locationSelector:
routing is something done globally so putting  locationSelector in App would not bothers me. App could have two reducers : one for the global domain (if needed) and one for the routing domain.
The fact is that in the example app, App container deals with too much business. Maybe it would have been better to put  everything apart the nav bar in HomePage  and to put HomePage content in a HomePage Child. Like this, App would only deal with global bahaviour.

@nikgraf one can always create a root selectors/ folder if one has complex selectors which combine state between different reducers.
@ralomucho I think the App container is fine, I agree that we should actually put the routeReducer there too instead of reducers.js! Good point!

Since there seems to be a consensus that this is a net-positive change, I'll go ahead and implement the generators anew and merge this asap.

@nikgraf : in my app, I make the distinction between two kinds of selectors :

directSelector which directly selects a single part of the state and doesn't need all of this boilerplate with createSelector and which can still be composed with other selectors. For instance  I use

selectError = () => state.getIn['global', 'error']

rather than
const errorSelector = () => createSelector(
    globalSelector(),
    (globalState) => globalState.get('error')
)

computeSelector which composes selectors with createSelector to benefit from memoization

These to kinds of selectors have their own generator. The fact is we need sometimes selectors from several containers :

if  the new selector is only used by one container, we can just make proper imports inside this container directory
if it is used by several containers, it's clear we nead a shared directory. sharedSelectorswould be more appropriate to make the distinction with containers own selectors.

The reasoning is that each selector selects a part of the state, right? So the selector should be right next to the reducer that has the part of the state it selects. This means that when you change the state shape, all you have to change is two files while the rest of the files stay the exact same.
A sharedSelector/ folder is basically what we just got rid of, it's only useful if you have a multitude of very complex selectors that mix state between reducers but otherwise almost all selectors should be right next to a reducer!

So, about the exploding ducks, I don't see how adding a reducer to a file with actions makes it grow that much bigger. Am I missing something?

@wmertens I'm not a big fan of the ducks approach, see my comment here and the followup here.

Coverage decreased (-0.09%) to 98.226% when pulling 4d1d3caac1a46c9021df9901c0d44ac5d9090159 on reducer-selector-colocation into c176c687f277b98b35638f4ad134949cc00d3a59 on v3.0.0.


Skipped tests not shown in jUnit output when status-level="all"

The jUnit XML report does not seem to include skipped tests, even when the status-level is set to "all" in .config/nextest.toml.
Using the default project generated by cargo init --lib, I have this in src/lib.rs:
pub fn add(left: usize, right: usize) -> usize {
    left + right
}

#[cfg(test)]
mod tests {
    use super::*;

    #[test]
    #[ignore]
    fn it_works() {
        let result = add(2, 2);
        assert_eq!(result, 4);
    }
}

...and this in .config/nextest.toml:
[profile.default]
status-level = "all"
final-status-level = "all"
fail-fast = false

[profile.default.junit]
path = "test-results.xml"

The generated XML is in target/nextest/default/test-results.xml as expected, but contains:
<?xml version="1.0" encoding="UTF-8"?>
<testsuites name="nextest-run" tests="0" failures="0" errors="0" uuid="83992729-11dc-43e7-b5e6-58baf30be039" timestamp="2023-06-08T02:13:52.673+00:00" time="0.000">
</testsuites>

Skipped tests are reported on stdout though:
nextest-test ⚬ cargo nextest run
    Finished test [unoptimized + debuginfo] target(s) in 0.00s
    Starting 0 tests across 1 binaries (1 skipped)
        SKIP [         ] nextest-test tests::it_works
------------
     Summary [   0.000s] 0 tests run: 0 passed, 1 skipped
        SKIP [         ] nextest-test tests::it_works

I had expected skipped tests to also be listed in the jUnit output.
For comparison, here's the output from Rust 1.69 using the JSON output and cargo2junit:
<?xml version="1.0" encoding="utf-8"?>
<testsuites>
  <testsuite id="0" name="cargo test #0" package="testsuite/cargo test #0" tests="1" errors="0" failures="0" hostname="localhost" timestamp="2023-06-08T02:38:27.464333560+00:00" time="0">
    <testcase name="tests::it_works" time="0">
      <skipped />
    </testcase>
  </testsuite>
  <testsuite id="1" name="cargo test #1" package="testsuite/cargo test #1" tests="0" errors="0" failures="0" hostname="localhost" timestamp="2023-06-08T02:38:27.464333560+00:00" time="0" />
</testsuites>

The command to generate that was:
cargo +1.69 test -- -Z unstable-options --format json --report-time | cargo2junit > test-results.xml

OS: Ubuntu 22.10
Cargo: 1.70.0 (ec8a8a0ca 2023-04-25)
Rustc: 1.70.0 (90c541806 2023-05-31)
Nextest: 0.9.53 (installed via cargo install for dev, pre-built binary for CI)

Hi there! Yes, we should have a reasonable depiction of skipped tests in the JUnit output.
Would you like to work on this? I'd love to work out a design with you—if you have a general suggestion, we can take it from there. In particular, should we expose this as a config option or just include skipped tests unconditionally?

Oof, I'm sorry, I did not see a notification for this! I am happy to chip away at it, and yes, let's start with at least a vague design.

should we expose this as a config option or just include skipped tests unconditionally

First off - do you have any particular policy (or just expectations) around backwards compatibility or unexpected output changes?  Otherwise I'd go with making it include the skipped tests unconditionally, to make it consistent with the stdout reporting and the docs.

I think we do generally want machine-readable output to be stable, modulo bugs. This seems like a case where it would be pretty surprising to users to suddenly start seeing lots of extra tests in their dashboards, so I think putting it behind a config option makes sense.

Seems like this bit is responsible for skipped tests. If we'd uncomment it and update the naming the feature would work.
But I have not checked how to hide it behind the config flag yet.
https://github.com/nextest-rs/nextest/blob/6304b41ee0d07c2fdcb9d7b89d04b9c934eac0b2/nextest-runner/src/reporter/aggregator.rs#L192-L203

Yes, that looks right. So it seems like it should be easy to do, we just need to figure out the configuration UI surface for this.


Split openapi.create_paramter_for_handler into several methods to reduce complexity

once again a simple refactor which was mentioned as needed by https://github.com/starlite-api/starlite/issues/203 and fixes this
the first filter, which extracts params that are not in layered_parameters, had its logic moved to a method called _get_unlayered_params but i'm not sure if it's the best naming decision

Thanks heaps for this! I'll have a look sometime in the next few hours. Cheers.


Need help with saml 2.0 integration.

Make sure these boxes are checked before submitting your issue - thank you!

✅ I have checked the superset logs for python stacktraces and included it here as text if any
✅ I have reproduced the issue with at least the latest released version of superset
✅ I have checked the issue tracker for the same issue and I haven't found one similar

Superset version
0.25:master
Hi, is superset supports saml2.0(ex: OpenSSL,Okta) auth for login method?.
Or do I have to use flask-oidc as mentioned  here:
https://stackoverflow.com/questions/47678321/using-openid-keycloak-with-superset

We support what FAB (flask-app-builder) supports, and SAML isn't on the list. We'd like to add it to the list at some point though as it's our preferred method at Lyft, but have been using oauth in the meantime.
I'm a committer on FAB and would be happy reviewing a PR that adds SAML integration there.

No timeline no. I don't think we'll take this on.

If you just need Superset to work with Okta, here's a quick workaround: https://gist.github.com/ktmud/2475282a166893e5d17039c308cbe50d
OpenID Connect is basically just OAuth 2.0, so AUTH_OAUTH from Flask-Appbuilder should already work.

You might also want to take a look at this: https://stackoverflow.com/questions/67076134/apache-superset-with-okta-integration/67906688#67906688

Hello now saml2 sso is supported or not.


Unknown command "lightercollective" on Windows when trying to install 1.11.1

C:\path\to\webcomponents>npm i

><EMAIL_ADDRESS>postinstall C:\path\to\webcomponents\node_modules\document-register-element
> lightercollective

Der Befehl "lightercollective" ist entweder falsch geschrieben oder
konnte nicht gefunden werden.
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR<EMAIL_ADDRESS>postinstall: `lightercollective`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>postinstall script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

It might be noteworthy that our network blocks https-requests in install-scripts.

Just counterchecked: This problem does not occur with v1.9.0:
C:\path\to\webcomponents>npm i

><EMAIL_ADDRESS>postinstall C:\path\to\webcomponents\node_modules\document-register-element
> lightercollective

     *** Thank you for using document-register-element! ***

Please consider donating to our open collective
     to help us maintain this package.

  https://opencollective.com/document-register-element/donate

                    ***

https://github.com/WebReflection/document-register-element/blob/master/package.json#L45-L47
as you can see, lightercollective is a dependency so it should get installed and it should work.


assistance with authentication

Thank you for your work! Maybe you can help me!? Please tell me how to set up authentication for WebGoat? And integrate it into Jenkins work?

@DimVit23 can you take a look at the examples in the Readme: https://github.com/ICTU/zap2docker-auth-weekly
They should work with WebGoat. You can run your final command in a Jenkins Shell-script job.


Cannot build image due to ImportError: libcublas.so.10: cannot open shared object file: No such file or directory

(Same error message as https://github.com/dusty-nv/jetson-containers/issues/159 , but occurring during image build time)
I am running into the error message

ImportError: libcublas.so.10: cannot open shared object file: No such file or directory

while building an image, since the Dockerfile runs `import cv2
I have not yet gotten to the point of seeing if the runtime docker environment is providing libcublas.so.10. I am trying to build the image on an x86 host that doesn't have NVidia hardware. Is this possible?

It seems like the l4t images are missing these files:
$ docker run --platform linux/aarch64 --rm -it nvcr.io/nvidia/l4t-base:r32.5.0 find / -name "libcublas*" 2>&1 | grep -v "Permission denied"

$ docker run --platform linux/aarch64 --rm -it nvcr.io/nvidia/l4t-base:r32.7.1 find / -name "libcublas*" 2>&1 | grep -v "Permission denied"
/usr/local/cuda-10.2/targets/aarch64-linux/lib/stubs/libcublasLt.so
/usr/local/cuda-10.2/targets/aarch64-linux/lib/stubs/libcublas.so

whereas if I do it directly on a r32.7.2 native installation:
$ find / -name "libcublas*" 2>&1 | grep -v "Permission denied"
/usr/local/cuda-10.2/targets/aarch64-linux/lib/libcublas.so
/usr/local/cuda-10.2/targets/aarch64-linux/lib/libcublas.so.10
/usr/local/cuda-10.2/targets/aarch64-linux/lib/libcublas.so.<IP_ADDRESS>0
/usr/local/cuda-10.2/targets/aarch64-linux/lib/libcublasLt.so
/usr/local/cuda-10.2/targets/aarch64-linux/lib/libcublasLt.so.10
/usr/local/cuda-10.2/targets/aarch64-linux/lib/libcublasLt.so.<IP_ADDRESS>0
/usr/local/cuda-10.2/targets/aarch64-linux/lib/stubs/libcublas.so
/usr/local/cuda-10.2/targets/aarch64-linux/lib/stubs/libcublasLt.so
/usr/share/doc/libcublas-dev
/usr/share/doc/libcublas10
/var/lib/dpkg/info/libcublas-dev.list
/var/lib/dpkg/info/libcublas-dev.md5sums
/var/lib/dpkg/info/libcublas10.list
/var/lib/dpkg/info/libcublas10.md5sums

r32.5.0 is the base image used here: https://github.com/dusty-nv/jetson-containers/blob/53a882c1d373301d2998f3026a1028ee36611853/Dockerfile.ros.humble#L5

ah, sorry, the last message is not quite relevant. This is the valid test (need the nvidia runtime)
$ sudo docker run --runtime=nvidia --platform linux/aarch64 --rm -it nvcr.io/nvidia/l4t-base:r32.7.1 find / -name "libcublas*" 2>&1 | grep -v "Permission denied"
/usr/local/cuda-10.2/targets/aarch64-linux/lib/libcublas.so
/usr/local/cuda-10.2/targets/aarch64-linux/lib/libcublas.so.10
/usr/local/cuda-10.2/targets/aarch64-linux/lib/libcublas.so.<IP_ADDRESS>0
/usr/local/cuda-10.2/targets/aarch64-linux/lib/libcublasLt.so
/usr/local/cuda-10.2/targets/aarch64-linux/lib/libcublasLt.so.10
/usr/local/cuda-10.2/targets/aarch64-linux/lib/libcublasLt.so.<IP_ADDRESS>0
/usr/local/cuda-10.2/targets/aarch64-linux/lib/stubs/libcublas.so
/usr/local/cuda-10.2/targets/aarch64-linux/lib/stubs/libcublasLt.so

But then it is still unclear to me how to build the docker image.

From https://github.com/dusty-nv/jetson-containers/issues/205#issuecomment-1310393417 it seems that the intention is not that this image can be built on x86. Building it on the Jetson means that the default docker runtime is nvidia, and this error does not show up.

Thats correct, I've only built these containers natively on Jetson (not x86).  Sorry for the confusion.

From: ggoretkin-bdai @.>
Sent: Friday, February 10, 2023 2:31:20 PM
To: dusty-nv/jetson-containers @.>
Cc: Subscribed @.***>
Subject: Re: [dusty-nv/jetson-containers] Cannot build image due to ImportError: libcublas.so.10: cannot open shared object file: No such file or directory (Issue #222)
From #205 (comment)https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fdusty-nv%2Fjetson-containers%2Fissues%2F205%23issuecomment-1310393417&data=05|01|dustinf%40nvidia.com|b153f849ee1a48e8af2608db0b9d6352|43083d15727340c1b7db39efd9ccc17a|0|0|638116542824748036|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=hfofPHesNAEFIJWQJ00mRR%2FA6%2B6GNCqvuFp7Dg3MIB4%3D&reserved=0 it seems that the intention is not that this image can be built on x86. Building it on the Jetson means that the default docker runtime is nvidia, and this error does not show up.
—
Reply to this email directly, view it on GitHubhttps://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fdusty-nv%2Fjetson-containers%2Fissues%2F222%23issuecomment-1426246589&data=05|01|dustinf%40nvidia.com|b153f849ee1a48e8af2608db0b9d6352|43083d15727340c1b7db39efd9ccc17a|0|0|638116542824748036|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=WXwYpQRKoxNqVFgkf8TuLwxlbRv4cn7Avj3x2beZ72c%3D&reserved=0, or unsubscribehttps://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FADVEGKYDZPP3EVOUM7AJW6DWW2JQRANCNFSM6AAAAAAUW7V7IY&data=05|01|dustinf%40nvidia.com|b153f849ee1a48e8af2608db0b9d6352|43083d15727340c1b7db39efd9ccc17a|0|0|638116542824748036|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=RUgPsTMq3CqLaVLfaq8xl8qjT4sNAbEshS5L8XUO7uk%3D&reserved=0.
You are receiving this because you are subscribed to this thread.Message ID: @.***>

I've ran into this issue today when trying to build the "l4t-ml" image on my Jetson Nano.  When torch is installed and it tries to test the installation I get the same error message.

@ByerRA is your default docker runtime set to NVIDIA? https://github.com/dusty-nv/jetson-containers/blob/master/docs/setup.md#docker-default-runtime

@ByerRA is your default docker runtime set to NVIDIA? https://github.com/dusty-nv/jetson-containers/blob/master/docs/setup.md#docker-default-runtime

Yes, NVIDIA is set as the default runtime.
$ sudo docker info | grep -i "Default Runtime"
Default Runtime: nvidia
I can confirm that the "nvcr.io/nvidia/l4t-base:r32.7.1" image which is the image being selected as the base build image in the build script does not have the "libcublas.so.10" library.

@ByerRA on JetPack 4, the CUDA/cuDNN/TensorRT libraries get mounted into container by --runtime nvidia from the host device - do you have libcublas.so.10 under /usr/local/cuda/lib64/ ?
If you start l4t-base like this, it should be there - otherwise there's an issue with your NVIDIA Container Runtime:
sudo docker run -it --rm --net=host --runtime nvidia -e DISPLAY=$DISPLAY -v /tmp/.X11-unix/:/tmp/.X11-unix nvcr.io/nvidia/l4t-base:r32.7.1

@ByerRA it would appear you have the files, so not sure why --runtime nvidia is not finding them.  If you have another SD card, I would recommend trying a fresh JetPack image and checking that l4t-base works from the start.

I flashed a new card with JetPack and now while I no longer get the errors about the missing cuda libraries I'm now getting the following build error...
[24/35] /usr/local/cuda-10.2/bin/nvcc  -DWITH_CUDA -I/torchvision/torchvision/csrc -I/usr/local/lib/python3.6/dist-packages/torch/include -I/usr/local/lib/python3.6/dist-packages/torch/include/torch/csrc/api/include -I/usr/local/lib/python3.6/dist-packages/torch/include/TH -I/usr/local/lib/python3.6/dist-packages/torch/include/THC -I/usr/local/cuda-10.2/include -I/usr/include/python3.6m -c -c /torchvision/torchvision/csrc/ops/cuda/roi_align_kernel.cu -o /torchvision/build/temp.linux-aarch64-3.6/torchvision/torchvision/csrc/ops/cuda/roi_align_kernel.o -D__CUDA_NO_HALF_OPERATORS__ -D__CUDA_NO_HALF_CONVERSIONS__ -D__CUDA_NO_BFLOAT16_CONVERSIONS__ -D__CUDA_NO_HALF2_OPERATORS__ --expt-relaxed-constexpr --compiler-options ''"'"'-fPIC'"'"'' -DTORCH_API_INCLUDE_EXTENSION_H '-DPYBIND11_COMPILER_TYPE="_gcc"' '-DPYBIND11_STDLIB="_libstdcpp"' '-DPYBIND11_BUILD_ABI="_cxxabi1011"' -DTORCH_EXTENSION_NAME=_C -D_GLIBCXX_USE_CXX11_ABI=1 -gencode=arch=compute_53,code=sm_53 -gencode=arch=compute_62,code=sm_62 -gencode=arch=compute_72,code=sm_72 -std=c++14
ninja: build stopped: subcommand failed.
Traceback (most recent call last):
File "/usr/local/lib/python3.6/dist-packages/torch/utils/cpp_extension.py", line 1723, in _run_ninja_build
env=env)
File "/usr/lib/python3.6/subprocess.py", line 438, in run
output=stdout, stderr=stderr)
subprocess.CalledProcessError: Command '['ninja', '-v']' returned non-zero exit status 1.
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "setup.py", line 508, in
'clean': clean,
File "/usr/local/lib/python3.6/dist-packages/setuptools/init.py", line 153, in setup
return distutils.core.setup(attrs)
File "/usr/lib/python3.6/distutils/core.py", line 148, in setup
dist.run_commands()
File "/usr/lib/python3.6/distutils/dist.py", line 955, in run_commands
self.run_command(cmd)
File "/usr/lib/python3.6/distutils/dist.py", line 974, in run_command
cmd_obj.run()
File "/usr/local/lib/python3.6/dist-packages/wheel/bdist_wheel.py", line 299, in run
self.run_command('build')
File "/usr/lib/python3.6/distutils/cmd.py", line 313, in run_command
self.distribution.run_command(command)
File "/usr/lib/python3.6/distutils/dist.py", line 974, in run_command
cmd_obj.run()
File "/usr/lib/python3.6/distutils/command/build.py", line 135, in run
self.run_command(cmd_name)
File "/usr/lib/python3.6/distutils/cmd.py", line 313, in run_command
self.distribution.run_command(command)
File "/usr/lib/python3.6/distutils/dist.py", line 974, in run_command
cmd_obj.run()
File "/usr/local/lib/python3.6/dist-packages/setuptools/command/build_ext.py", line 79, in run
_build_ext.run(self)
File "/usr/local/lib/python3.6/dist-packages/Cython/Distutils/old_build_ext.py", line 186, in run
_build_ext.build_ext.run(self)
File "/usr/lib/python3.6/distutils/command/build_ext.py", line 339, in run
self.build_extensions()
File "/usr/local/lib/python3.6/dist-packages/torch/utils/cpp_extension.py", line 735, in build_extensions
build_ext.build_extensions(self)
File "/usr/local/lib/python3.6/dist-packages/Cython/Distutils/old_build_ext.py", line 195, in build_extensions
_build_ext.build_ext.build_extensions(self)
File "/usr/lib/python3.6/distutils/command/build_ext.py", line 448, in build_extensions
self._build_extensions_serial()
File "/usr/lib/python3.6/distutils/command/build_ext.py", line 473, in _build_extensions_serial
self.build_extension(ext)
File "/usr/local/lib/python3.6/dist-packages/setuptools/command/build_ext.py", line 202, in build_extension
_build_ext.build_extension(self, ext)
File "/usr/lib/python3.6/distutils/command/build_ext.py", line 533, in build_extension
depends=ext.depends)
File "/usr/local/lib/python3.6/dist-packages/torch/utils/cpp_extension.py", line 565, in unix_wrap_ninja_compile
with_cuda=with_cuda)
File "/usr/local/lib/python3.6/dist-packages/torch/utils/cpp_extension.py", line 1404, in _write_ninja_file_and_compile_objects
error_prefix='Error compiling objects for extension')
File "/usr/local/lib/python3.6/dist-packages/torch/utils/cpp_extension.py", line 1733, in _run_ninja_build
raise RuntimeError(message) from e
RuntimeError: Error compiling objects for extension
The command '/bin/sh -c git clone --branch ${TORCHVISION_VERSION} --recursive --depth=1 https://github.com/pytorch/vision torchvision &&     cd torchvision &&     git checkout ${TORCHVISION_VERSION} &&     python3 setup.py bdist_wheel &&     cp dist/torchvision.whl /opt &&     pip3 install --no-cache-dir --verbose /opt/torchvision.whl &&     cd ../ &&     rm -rf torchvision' returned a non-zero code: 1
Traceback (most recent call last):
File "/usr/lib/python3.6/runpy.py", line 193, in _run_module_as_main
"main", mod_spec)
File "/usr/lib/python3.6/runpy.py", line 85, in _run_code
exec(code, run_globals)
File "/home/rbyer/jetson-containers/jetson_containers/build.py", line 95, in
build_container(args.name, args.packages, args.base, args.build_flags, args.simulate, args.skip_tests, args.test_only, args.push)
File "/home/rbyer/jetson-containers/jetson_containers/container.py", line 128, in build_container
status = subprocess.run(cmd.replace(NEWLINE, ' '), executable='/bin/bash', shell=True, check=True)
File "/usr/lib/python3.6/subprocess.py", line 438, in run
output=stdout, stderr=stderr)
subprocess.CalledProcessError: Command 'docker build --network=host --tag jetson_l4t-ml:r32.7.4-torchvision --file /home/rbyer/jetson-containers/packages/pytorch/torchvision/Dockerfile --build-arg BASE_IMAGE=jetson_l4t-ml:r32.7.4-pytorch --build-arg TORCHVISION_VERSION="v0.11.1" --build-arg TORCH_CUDA_ARCH_LIST="5.3;6.2;7.2" /home/rbyer/jetson-containers/packages/pytorch/torchvision 2>&1 | tee /home/rbyer/jetson-containers/logs/20230922_132123/build/jetson_l4t-ml_r32.7.4-torchvision.txt; exit ${PIPESTATUS[0]}' returned non-zero exit status 1.

@ByerRA there's not an actual compilation error in there, I think it ran out of memory.  Can you try mounting more swap?
https://github.com/dusty-nv/jetson-containers/blob/master/docs/setup.md#mounting-swap


Confirmation times are outrageous (4 hours on an exchange?)

[12:56 AM] ErGo: @___ Another to add to the review and fix list...That 100 coins deposit is still not confirmed. Why? Because it takes 200 confirmations to hit the exchange.  4 hours and that transfer is at 140/200

Take a look at https://www.cryptopia.co.nz/api/GetCurrencies (DepositConfirmations":200), there's 200+ other coins which require 200 confirms too.
If we bought another one of these coins which has <20 nodes supporting the network too, we'd have similar delays.
See it as we three options.

To reduce confirm time to 2 hours we need to double. For 1 hour confirms, 80+ would be target. Ideally 30 minute confirms would be our main target with 160 nodes. To achieve this we could setup a bounty for a full node cluster or build a turn key distribution with accompanying documentation for users to easily setup their own full nodes. Second is preferred as it keeps the network for the most part fully decentralized, while the first results in more less full centralization.
We could lower original minimum confirms and hard fork; not necessarily a bad call when you consider our network is still small enough, and impact wouldn't be as great as to if say we had to deal with convincing 100+.

We've had our confirmation times reduced on Cryptotopia!


Would you like to share the trained model using the NYT datasets?

The model can be downloaded in https://pan.baidu.com/s/1Yy0okgQbbItFhX4JG67aiA with keyword "p7xh".


Updating an entity on createShape (plus get nested resource as resource)

When creating a resource, I want to be able a related resource of the same type. A good example is a catalogue API. When I create a folder, I want its children's list to update.
type Folder = {
  id: number
  parentId: number
  name: string
  children?: Folder[] // the api only returns up to one level children depth
  childrenCount: number
}

createFolder({}, { id: uuid(), name: fileName, parentId: props.id }, [
  [FolderResource.detailShape(), { id: props.id }, (updateParamA, updateParamB) => {
    // See below
    console.log(updateParamA, updateParamB)
  }]
])

My expectation is that updateParamA would return the folder with props.id, allowing me to update it  by adding the id of my new folder to the FolderResource. It doesn't even have to be optimistic, I just want to be able to update my entity.
I feel unable to visualize right now how to do it with the existing tools in rest-hooks, probable due to my inexperience with the library.
Also, the type above yields to the following schema:
  static schema: any = { // have to use any here as schema refers to self
    children: [FolderResource.asSchema()],
  };

Using the detailShape returns ids for these ie: children: ['1', '2']. Is there any way we can get the fully formed/nested objects, ie: children[FOLDER_1, FOLDER2]?
This is because returning ids prevents doing something like classList.children.map directly without creating a new component as we have to use useCache for each element row. Alternatively a useCache with multiple ids would be great (can a special shape be created for this?)

Thanks for the report. We can probably get something in for the next useFetcher() design.
To understand this use case, can you get back to me if what I say is correct?  Instead of having to fetch all those children to get the updated parent you'd like their data to be updated to point to the new ID from the created parent.

Thanks for the report. We can probably get something in for the next useFetcher() design.
To understand this use case, can you get back to me if what I say is correct?  Instead of having to fetch all those children to get the updated parent you'd like their data to be updated to point to the new ID from the created parent.

Tracking solution in https://github.com/coinbase/rest-hooks/issues/760


Nullable extension types are wonky

(Dart SDK version: 3.3.0 (stable) (Tue Feb 13 10:25:19 2024 +0000) on "macos_arm64")
Consider the following:
extension type const Money(double _value) implements double {}

void main() {
  Money? a = Money(5);
  print(a.toInt());
}

The analyzer indicates no problem
On the VM, it fails to compile: Error: Method 'toInt' cannot be called on 'Money?' because it is potentially null
In Dart2JS it both runs and prints 5

That's an analyzer bug. It's probably #54664.

Well on Dart2JS it just runs so 😅

I think it is a non-error because a is promoted at initialization (because Money is a type of interest when Money? is, and the initializing expression is non-nullable). If you add as dynamic to the initializing expression there is no promotion, and the analyzer reports the error as expected (and so does the CFE).
extension type const Money(double _value) implements double {}

void main() {
  Money? a = Money(5) as dynamic;
  print(a.toInt()); // Error.
}

So I'd say it is all working as intended.

Ok, you're right that the following also fails in Dartpad:
extension type const Money(double _value) implements double {}

void main() {
  print(Money(5));
}

void useMoney(Money? a) {
  print(a.toInt());
}

compileDDC
main.dart:8:11: Error: Method 'toInt' cannot be called on 'Money?' because it is potentially null.
Try calling using ?. instead.
  print(a.toInt());
          ^^^^^

Still of course no analysis warnings/errors, but I can track https://github.com/dart-lang/sdk/issues/54664, thanks!


download.docker.com IPV6 support

GENERAL SUPPORT INFORMATION
The official Docker repository does not support IPV6.

BUG REPORT INFORMATION
Description
We use an deb Proxy, as dowload.docker.com uses https all traffic is simply forwarded.
The deb Proxy is reached via IPV6 and so tries to forward to https://download.docker.com via IPV6.
The request fails as there is no IPv6
Steps to reproduce the issue:
Use IPV6 deb Proxy, forwards https traffic
Describe the results you received:
Updating Docker packages fails

ping @andrewhsu @friism

We'll look into it and see if we can an ipv6 address for it.

Looks good, thanks!

Thanks for reporting @aparcar!


Chore add case about insert data imidiately after create mv

Proposed changes
add case about insert data imidiately after create mv
Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

run buildall


Syntax error after styling flow type annotations

The following code:
class Selection extends React.Component<void, PropsType, void> {
    props: PropsType;
    _onItemClick: (ev: SyntheticMouseEvent) => void;
    _removeSelectedItem: (selectedItems: Array<string | number>, resp: number) => Array<string | number>;
    _isSelectedItem: (id: number) => boolean;
     isSelectedRespondent: (type: string, firmId: number, hasRespondents: boolean) => boolean;
}

gets formatted to:
class Selection extends React.Component<void, PropsType, void> {
    props: PropsType;
    _onItemClick: (ev: SyntheticMouseEvent) => void;
    _removeSelectedItem: (selectedItems: Array<string | number>, resp: number) => Array<
        | string
        | number>;
    _isSelectedItem: (id: number) => boolean;
    isSelectedRespondent: (type: string, firmId: number, hasRespondents: boolean) => boolean;
}

The babel-eslint complains that there is a syntax error around Array<         | string         | number>
part.
Also note that this is somewhat inconsistent with how type aliases are being formatted:
type X = | number | string;

gets transformed into
type X = number | string;

Babel might not support this Flow syntax yet. I'm pretty sure this is valid. @hzoo do you know if Babel should parse the above code?

type X = number | string;

It's not inconsistent; for inline types it formats it that way, but when it breaks it up, it forms it like this:
type X =
  | number
  | string
  | number
  | string
  | number
  | string
  | number;

I think what you've unconvered is a problem with array function types though, and something else in the arrow function type should break before breaking the return type.

Babylon supports it so might be a bug in babel-eslint (which I haven't updated in a long time). It does use ^ though so maybe you need to make sure you are on the latest version.

Labelling this as a bug, we should be splitting the arguments before the return type.

It seems to have been fixed since this issue was opened.
class Selection extends React.Component<void, PropsType, void> {
    props: PropsType;
    _onItemClick: (ev: SyntheticMouseEvent) => void;
    _removeSelectedItem: (selectedItems: Array<string | number>, resp: number) => Array<string | number>;
    _isSelectedItem: (id: number) => boolean;
     isSelectedRespondent: (type: string, firmId: number, hasRespondents: boolean) => boolean;
}

now looks
class Selection extends React.Component<void, PropsType, void> {
  props: PropsType;
  _onItemClick: (ev: SyntheticMouseEvent) => void;
  _removeSelectedItem: (
    selectedItems: Array<string | number>,
    resp: number
  ) => Array<string | number>;
  _isSelectedItem: (id: number) => boolean;
  isSelectedRespondent: (
    type: string,
    firmId: number,
    hasRespondents: boolean
  ) => boolean;
}

https://prettier.github.io/prettier/#{"content"%3A"class Selection extends React.Component<void%2C PropsType%2C void> {\n    props%3A PropsType%3B\n    _onItemClick%3A (ev%3A SyntheticMouseEvent) %3D> void%3B\n    _removeSelectedItem%3A (selectedItems%3A Array<string | number>%2C resp%3A number) %3D> Array<string | number>%3B\n    _isSelectedItem%3A (id%3A number) %3D> boolean%3B\n     isSelectedRespondent%3A (type%3A string%2C firmId%3A number%2C hasRespondents%3A boolean) %3D> boolean%3B\n}"%2C"options"%3A{"printWidth"%3A80%2C"tabWidth"%3A2%2C"singleQuote"%3Afalse%2C"trailingComma"%3A""%2C"bracketSpacing"%3Atrue%2C"jsxBracketSameLine"%3Afalse%2C"parser"%3A""%2C"doc"%3Afalse}}


How to handle common / global attributes?

[ ] This only affects the JavaScript OpenTelemetry library
[x] This may affect other libraries, but I would like to get opinions here first

The intent of this issue is to open a discussion about how to implement handling of common/shared attributes. Common attributes are similar to resource attributes in that they apply to all spans and logs, but they are different in that they are mutable.
Background
Client instrumentation has several use cases for attributes that should be associated with all spans and logs generated within a given time period. The primary use case is to represent a session (the session.id attribute has recently been added to semantic conventions), but there are other use cases including:

visitor id
page impression id
page url
geo location data
network information
language preference
screen width and height

Compared with Resource attributes
We originally wanted to send these as resource attributes (see this OTEP). However, the challenge with these attributes is that their values can change during the lifetime of the SDK. Therefore, the direction we have received from the TC is to add them to each signal instead.
Compared with Context attributes
A distinction also needs to be made with trace-context attributes, as proposed in this OTEP. Client attributes, like session ID, need to be applied to many traces and standalone events generated by a client application, not just a single trace.
Questions
Should there be a standard mechanism in the SDK to handle these attributes?
Should this be standardized across all SDKs and documented in the specification?
Discussion
The options that I can think of:
Option 1: Each attribute is added by a separate span/log processor
The implementation would be straight-forward. However, adding many attributes means managing many processors: two processors (span and log) for each attribute. This may be difficult to configure and manage.
Setting and retrieving the attribute values could be handled on a case-by-case basis. A processor, for example, could itself include the detection of the value. Or, it could expose methods to set the value from an external code.
Example:
tracerProvider.addSpanProcessor(new SessionIdSpanProcessor());
tracerProvider.addSpanProcessor(new VisitorIdSpanProcessor());
tracerProvider.addSpanProcessor(new GeoLocationSpanProcessor());

loggerProvider.addLogProcessor(new SessionIdLogProcessor());
loggerProvider.addLogProcessor(new VisitorIdLogProcessor());
loggerProvider.addLogProcessor(new GeoLocationLogProcessor());

Option 2: There is a single span/log processor used to add all common attributes
There would be two processors only: one for spans and one for logs. The question is how would attributes be added and updated. The processor could accept a collection of attribute providers, or it could retrieve the attributes from a global attribute store (provided by the SDK). A prototype of the latter is available here.
For the first option, an interface would need to be defined for the attribute providers. These providers would need to be configured and passed to the processor during initialization.
const providers = [
	new SessionIdAttributeProvider(),
	new VisitorIdAttributeProvider()
	new GeoLocationAttributeProvider(),
]

tracerProvider.addSpanProcessor(new GlobalAttributesSpanProcessor(providers));
loggerProvider.addLogProcessor(new GlobalAttributesLogProcessor(providers));

Option 3: The mechanism to add these attributes is built-in to the SDK
With this option, there is no span/log processor. The SDK provides an API to set/update global attributes, and it automatically adds them when a span or log is created.
For example:
tracerProvider.setGlobalAttribute(name, value);
loggerProvider.setGlobalAttribute(name, value);

or perhaps:
new TracerProvicer({
	globalAttributeProviders: [
		new SessionIdAttributeProvider(),
		new VisitorIdAttributeProvider()
		new GeoLocationAttributeProvider(),
	]
})

Existing implementations
The Android SDK currently has a SessionIdSpanAppender span processor that adds the session ID attribute to all spans. It also has the GlobalAttributesSpanAppender span processor that can add multiple attributes at the same time.
We have also implemented a prototype in JavaScript that introduces a GlobalAttributesSpanProcessor and GlobalAttributesLogRecordProcessor
processors. The attributes are retrieved from a global store, which allows for any component to add global attributes.

If this ends up in SDK I would expect it to be similar across techs. If this happens it likely needs to be an optional component/api there because techs are already different in some areas (like automatic context propagation).
Is this only applicable to browsers or also to node.js/deno/...
If only for browsers it should be likely at WebSDK or in web specific instrumentations.
If it is on API level or generic SDK we need to clearly specify how it behaves in non web setups.
Which component is responsible for such global changes?

Some blessed instrumentation?
Actual application code which did the SDK setup?
What about automatic setups in this case where monitoring is "just added"?
Is there a specific "owner" of this state?

Is it allowed to have more parallel sessions running?
If yes, how is it ensured that all (mostly independent) instrumentations are aware of this and select the "correct" session?
Is it allowed that spans on the same trace are on different sessions?
Current proposals seem to allow this as span creation is unrelated to global state change and several traces may run when state is changed.

@martinkuba

I suggest skipping option 3 as it touches TracerProvider and will require more discussion / approvals.
Option 2 looks very similar to MultiSpanProcessor in opentelemetry-java, so you can introduce the same in opentelemetry-js too.
I think we don't need the term "Global" in GlobalAttributeProcessor as the processors are global already - that is, they are applied to all the signals emitted by instrumentations configured with tracer provider. We can stop here and implement separate processors for each concern and use the MultiSpanProcessor to configure them all in one place.
Optionally, if the term Processor sounds generic and your intent is to convey that the new interface is to inject an attribute then the interface could take the attribute name to be injected as a parameter, for eg., session.id, and a generator class that generates only a value for this attribute.  For eg., AttributeInjector(attributeName, ValueGenerator)

@scheler:

Option 2 looks very similar to MultiSpanProcessor in opentelemetry-java, so you can introduce the same in opentelemetry-js too.

I agree that it is similar, but there is a subtle difference. The MultiSpanProcessor is more generic; it can take any SpanProcessor and invoke its processing, which could be doing anything. My proposal with the GlobalAttributesSpanProcessor is that this processor adds the attributes - it's a generic attributes "adder". The providers are there only to supply the attributes to be added.

I think we don't need the term "Global" in GlobalAttributeProcessor as the processors are global already

Having "GlobalAttribute" in the name denotes that this processor adds attributes that are considered global. In other words, this just describes what this processor does.


Added localization into iOS share extension

Summary
Added localization into iOS share extension for all existing UI strings, based on reusing strings from i18n/*.json files.

Updated Fastfile script to generate iOS-specific Localizable.strings files
Empty Localizable.strings files for each language were added to iOS project under MattermostShare target in order to be included to app package
Replaced strings with NSLocalizedString macros in Swift source files
Reworked usage of DateFormatters with single static instances in Swift, since creation of each Formatter object is pretty consuming operation
Removed INFOPLIST_KEY_* records from MattermostShare target build settings to prevent overriding of Info.plist values
Added new translation strings to share_extension/screens/share.tsx, which are used in iOS share extension only
Fixed missing argument in app/utils/file/index.ts

Ticket Link
Checklist

[ ] Added or updated unit tests (required for all new features)
[ ] Has UI changes
[x] Includes text changes and localization file updates
[ ] Have tested against the 5 core themes to ensure consistency between them.

Device Information
This PR was tested on: iPhone simulator iOS 16.2, Android emulator Pixel 3a Android 12
Screenshots
Release Note
Added localization into iOS share extension

Hello @Partizann,
Thanks for your pull request! A Core Committer will review your pull request soon. For code contributions, you can learn more about the review process here.

This PR has been automatically labelled "stale" because it hasn't had recent activity.
A core team member will check in on the status of the PR to help with questions.
Thank you for your contribution!

@enahum We may have to create a ticket to make sure i18n-extract also looks into these strings. Not sure how easy that is going to be. But we can discuss it after this PR is merged.

@yasserfaraazkhan Re: testing
The idea here is mainly do some smoke testing around the iOS share extension, so all texts look normal and nothing breaks. It won't translate yet because we don't have the translations, but please try also with the phone / user in a different language to make sure the "default language" (English) is taken correctly and nothing breaks.

Building app in separate branch.

Successfully building:
https://circleci.com/gh/mattermost/mattermost-mobile/29130
https://circleci.com/gh/mattermost/mattermost-mobile/29129

Should I upmerge main to get iOS build done successfully?

Should I upmerge main to get iOS build done successfully?

@Partizann , that would be a great help

Building app in separate branch.

Successfully building:
https://circleci.com/gh/mattermost/mattermost-mobile/29134
https://circleci.com/gh/mattermost/mattermost-mobile/29133

Artifact links:
https://output.circle-artifacts.com/output/job/b60756d1-951a-4946-9ec1-4a62d29c6cf1/artifacts/0/tmp/artifacts/Mattermost_Beta.ipa
https://output.circle-artifacts.com/output/job/0dc2fab4-c2c0-4ac9-9c47-4eb44b51f7ff/artifacts/0/tmp/artifacts/Mattermost_Beta.apk

I'm having trouble installing the .ipa on my old test iPhone. Have there been any purges from the registered devices for testing? It's been a while since I've tried this....
Perhaps, since v2.5 has just been approved, we could test this one post-merge when the next test build for v2.6 can happen, while we're sorting out test device issues?

@lindalumitchell LGTM, but I will leave the final decision to @yasserfaraazkhan

I'm having trouble installing the .ipa on my old test iPhone. Have there been any purges from the registered devices for testing? It's been a while since I've tried this....
Perhaps, since v2.5 has just been approved, we could test this one post-merge when the next test build for v2.6 can happen, while we're sorting out test device issues?

Reach out to me so that we can figure out the reason you cannot install it

/update-branch

We don't have permissions to update this PR, please contact the submitter to apply the update.

@Partizann Do you mind mergin main into this PR? For some reason the test step didn't went through, and a new commit should help to unstuck it.

@Partizann Thank you very much for your contribution!


ESLint: "semistandard" shared config should be considered equivalent to "standard"

Don't add "standard" to the "extends" list if it already includes "semistandard"

Still experiencing this even in 1.2.0 :S

Nevermind. :D


Add support for binding to the specific host

Some services such as Openshift requires a binding process to the specific host(IP).

Going to merge to a local branch and fix up travis, thank you for the PR @G07cha


Craft 4 compatibility

Hi! Thanks for maintaining this very cool plugin! Do you have any plans on updating for Craft 4?

Yes, planning on getting an update out within the next week or two 👍

Craft 4 compatibility added and just released. Please report any issues. Thanks.

You're a champ Sean, Thanks! 💯

Currently I can't install the plugin. 😢 I'm using the latest Craft CMS version (4.3.4). Can we expect a fix for this or should we rather downgrade to the last working version? If yes, which one would that be? Thanks!

Gonna need to give a few more details, I'm afraid.

Weird…last week the install button was disabled…maybe it was a Craft problem/bug…now I could install 👍 Thanks for this plugin!


FP - ice phishing

I'm seeing a lot of FPs casually on addresses that have traded a token called Mind.

This address was labeled in this alert

This address was labeled in this alert

This address was labeled in this alert

The token was falsely alerted as suspicious by the "Malicious Smart Contract ML V2" bot, the alerts of which are consumed by the Ice Phishing bot.
I added a check of the number of different transaction initiators (calling the "suspicious" contract). If the number is high, we consider the contract safe and don't raise an alert.

We have now removed the specific alert from the Scam Detector.


Make Reaper's backend configurable

What this PR does:
This PR adds the option to configure Reaper to use a memory sotrage backend.
If this storage type is used, Reaper will be deployed as a Stateful Set instead of a Deployment. It will also get a new volume to store the data on. This volume is not being cleared up after Reaper's parent k8ssandra cluster object gets deleted. This is intentional - we want to keep that data, plus it's a pre-work for deploying reaper individually (w/o the k8ssandra cluster).
Which issue(s) this PR fixes:
Fixes #1275
Checklist

[x] Changes manually tested
[x] Automated Tests added/updated
[ ] Documentation added/updated
[x] CHANGELOG.md updated (not required for documentation PRs)
[ ] CLA Signed:  DataStax CLA

@burmanm , I've resolved all the comments you had, plus I've amended Reaper's e2e tests to cover deployment as a STS. I chose this instead of creating a brand new e2e test. I hope it's okay. Could you please have another look?

Tests passed, merging.


Error when setting unusual frame rates

When setting the -fr flag to "unusual" values, the script crashes with an error, see for example:
~ >>> asv ~/DataShare/Video-Audio/Music/Arctic\ Monkeys\ -\ Do\ I\ Wanna\ Know\ \(Official\ Video\).mp3 ~/Desktop/testboi -e 20 -fr 18
Audio succesfully loaded. (1/4)
Traceback (most recent call last):
  File "/home/deinalptraum/DataShare/Programming/repos/AudioSpectrumVisualizer/AudioSpectrumVisualizer.py", line 329, in <module>
    full()
  File "/home/deinalptraum/DataShare/Programming/repos/AudioSpectrumVisualizer/AudioSpectrumVisualizer.py", line 297, in full
    frameData = calculateFrameData(fileData, samplerate)
  File "/home/deinalptraum/DataShare/Programming/repos/AudioSpectrumVisualizer/AudioSpectrumVisualizer.py", line 73, in calculateFrameData
    lastFrame[0:len(currentFrameData)] = currentFrameData
ValueError: could not broadcast input array from shape (2667,) into shape (2666,)

I have observed this on a 20 second with framerates 17, 18 and 31 so far.

Fixed in 6cb178f519a9a7f53d3b6567ba51239da78bea72


Fixed engine image never becomes deployed after upgrading

We recently changed the labels for engine image CR in the PR https://github.com/longhorn/longhorn-manager/pull/842. We added the label longhorn.io/managed-by: longhorn-manager to engine image, engine image daemonset, and engine image daemonset pod by updating the fucntion GetEngineImageLabels()
On the other hand, during Longhorn upgrading, we only update the label for engine image, engine image daemonset but not the engine image daemonset pod  of the existing engine image.
This creates a problem when we syncNodeDeploymentMap(), Longhorn couldn't find the pod of the old engine image using the label selector returned by GetEngineImageLabels()  and think that the old engine image is not deployed.
The propose solution in this PR is that we don't need to add the label longhorn.io/managed-by: longhorn-manager  to engine image daemonset pods at all (for both old and new engine image) because the engine image ds pods are not managed by Longhorn manager. It is managed by the daemonset controller. Then, we use the correct label selector to list the engine image pods (i.e., don't use function GetEngineImageLabels() but create a new function that returns the selector that doesn't include the label longhorn.io/managed-by: longhorn-manager)
longhorn/longhorn#2399

Thanks @innobead !
Updated the unit tests

I am running the e2e core tests just in case

Thanks @innobead !
Updated the unit tests

:+1:  but that also means the original unit tests do not take any effect when you change the label selection logic (it should fail in some cases). Probably we need to review the unit tests later.


Run Aqua VM in background

Aqua VM interpreter runs on the main thread. It may cause performance problems noticeable to browser users. An incoming particle can potentially block the entire application UI and there is no mechanism to prevent that.
There should be an option to run particles' script interpretation in a separate thread using webworkers in browser and worker  threads in nodejs.
The implementation should consider the following:

The execution strategy should be configurable
Both nodejs and browser should be supported with no difference to JS SDK consumers
The code should be reused between nodejs and browsers as possible

This issue depends on the integration of the async AVM  #73

Implemented in https://github.com/fluencelabs/fluence-js/pull/111


Fix #2075 - Pinch zooming while typing text breaks the UI on Chrome Mac OS X

Looks like event.stopPropagation() is not enough to stop Chrome from handling the pinch zoom event when the cursor is over the  for the wysiwg text.
On this PR, I added event.preventDefault() so that the Chrome browser does not handle the pinch zoom.
I tested this on:

Chrome 84 ✅
Brave 1.12 (Chromium 84) ✅
Firefox (was not affected by the problem and still works the same way) ✅
Safari (zoom and panning on wysiwg is still broken) 🔴

Thanks for this! Too bad it doesn't work on Safari. If you ever find a solution for that one (I don't have any iOS touch device to try myself), don't hesitate to make another PR.


feat: Bump default GH CLI version from 2.40.1 to 2.49.2

To implement #53

Thanks for your suggestion @f-belliard , I think a better solution for the initial issue is to use latest as default, and I'm working on that now, so I'm gonna close this issue.


Site settings page crashes, multivaluefield not found

This only seems to happen on a local site with Silverstripe 5.0+.
It is fixed by deleting /vendor and /public/_resources/vendor folders, then reinstalling all modules.

Caching issue. Not related to this module.


Word Occurrences highlighting

System information:

Operating system (distribution) and version: Fedora 26
DBeaver version: <IP_ADDRESS>009201907
Additional extensions: none

Connection specification:

Database name and version: PostgreSQL 9.4
Driver name: postgresql-42.2.5.jar
Do you use tunnels or proxies (SSH, SOCKS, etc)? NO

Describe the problem you're observing:
Word Occurrences highlighting works incorrect for the reason highlight sub-word as well.

Thank you for the report.

For me it works as expected.
Having sub-words selected is very useful in some cases.
You could try option "Mark occurences of word under cursor" in 7.2.5.

Is it expected that the option works only via the Global settings?
Should an ability be made to activate only one of the options (word under cursor or selected word) in the settings?

Yes. I've reworked SQL editor pref page and now all code editing settings are global.
Yes, these options can be set independently

closed


New Messages for Messasges.js not working; though new messages for En.js does work.

Hi Carlos and the Rest of the ArduBlockly Community,
After almost finishing -- as a newbie -- my first new block "Infrared Rx" (kindly see https://github.com/carlosperate/ardublockly/issues/107), I do have a follow-up technical question:
To add new messages, such as:
• Blockly.Msg.ARD_INFRARED_READ_BLOCK_NAME = "Comms: Infrared Rx";
• Blockly.Msg.ARD_INFRARED_READ_FROM_PIN = " * Input: Read PIN#";
I understand that I need to edit '\blockly\msg\messages.js', yet the changes do not get incorporated when running ArduBlockly, even when I do the 4-step Build according to https://github.com/carlosperate/ardublockly/wiki/Building-Ardublockly.
I end up directly editing (hacking) the generated file '\blockly\msg\js\en.js' for the new messages to work.
Am I overlooking something?
Thanks for your time Carlos (and anyone else who may be reading this).
Regards... :) Jason
(Educational-Technology Instructor for Kids & Beyond)

Hi Jason,
Sorry for the late reply, I was on holiday until recently. For the new strings to be built in all the language files and included in Ardublockly you need to build Blockly. The instruction can be found in https://github.com/carlosperate/ardublockly/wiki/Add-New-Language , as adding a new block string would follow the same steps as adding a new language. You are also right on the fact that he build instructions fail to include a step for building blockly, I will add that as soon as I get a chance.

Thanks very much again.  Your solution has been helpful.  It worked.
Yet, every once in a while, from the following command:
`C:\Dropbox\3a-Jwc\3a-Code\ArduBlockly-Engine\3f-GitGui-CURRENT\blockly>python build.py
I experience this intermittent following build error:

Error reading .\msg\json\en.json
Traceback (most recent call last):

File "i18n\create_messages.py", line 149, in
main();
File "i18n\create_messages.py", line 65, in main source_defs = read_json_file(os.path.join(os.curdir, args.source_lang_file))
File "C:\Dropbox\3a-Jwc\3a-Code\ArduBlockly-Engine\3f-GitGui-URRENT\blockly\i18n\common.py", line 64, in read_json_file     raise InputError(filename, str(e))

common.InputError: .\msg\json\en.json: Expecting property name enclosed in double quotes: line 9 column 1 (char 176) ('Error running i18n/create_messages.py: ', CalledProcessError())

But when I look into 'en.json', I cannot find the bug.  Weirdly, it deletes the body after this following header.

{
"@metadata": {
"author": "Ellen Spertus<EMAIL_ADDRESS>"lastupdated": "2016-04-14 00:12:10.784946",
"locale": "en",
"messagedocumentation" : "qqq"
},

Yet after I restore the body back into 'en.json', the second 'python build.py' appears to work.  :)
Since this issue only seems intermittent and there is a work around, I'll be happy to close this issue.  Yet, I've entered the above comments in case anybody may be familiar with this unusual but tolerated behavior.  Perhaps there's something I'm missing in my process.  :)
`

Glad it worked. I've also updated https://github.com/carlosperate/ardublockly/wiki/Building-Ardublockly to include the instructions for building Blockly.
The problem you are experiencing with the language files is a current issue with Blockly, which has been reported in https://github.com/google/blockly/issues/447

Thanks @carlosperate for the building instructions.  :)

The issue sounds to be solved, but I don't see how to fix it?
When I execute the following command in windows: c:\Python27\python.exe i18n\js_to_json.py --input_file  msg\messages.js --output_dir msg\json\
it generates the file, but the content is the following:
`{
"@metadata": {
"author": "Ellen Spertus<EMAIL_ADDRESS>"lastupdated": "2017-03-29 21:05:20.611000",
"locale": "en",
"messagedocumentation" : "qqq"
},
}`
Is it normal?

In windows I had a similar problem, in js_to_json.py I replaced _INPUT_DEF_PATTERN = re.compile("""Blockly.Msg.(\w*)\s*=\s*'([^'])';?$""")  by _INPUT_DEF_PATTERN = re.compile("""Blockly.Msg.(\w)\s*=\s*'([^']*)';?""") to match the line.
Some how it works fine in Linux, but not in windows. I think it's related to "\n" coding and how regex lib handle that in python depending on the os.


Update documentation for node & webpack usage

Fix #1403 and #1409.

@Golmote I made the one change you suggested here; if you think we should re-include manual requiring for node, let me know and I'll fix, but I'm going to merge for now.


Adding GravatarImageSource

Description of Change
Adds a new GravatarImageSource that can be easily added for any image source using a user's email address. This utilizes the image provided by gravatar.com and supports all of their default image results to handle when an email address has no associated Gravatar.

Issues

closes #312

Platforms Supported

Android
iOS
macOS
UWP
WPF
Tizen

API Changes
Added:
public enum DefaultGravatar
{
	FileNotFound,
	MysteryPerson,
	Identicon,
	MonsterId,
	Wavatar,
	Retro,
	Robohash,
	Blank
}

public class GravatarImageSource : ImageSource
{
    public string Email { get; set; }
    public int Size { get; set; }
    public DefaultGravatar Default { get; set; }
    public boo CachingEnabled { get; set; }
    public TimeSpan CacheValidity { get; set; }
}

Note that by default Caching is enabled for 7 days. An additional XAML Extension has been provided to make it even easier to use.
Behavioral Changes
none
PR Checklist

[ ] Has tests (if omitted, state reason in description)
[x] Has samples (if omitted, state reason in description)
[x] Rebased on top of main at time of PR
[x] Changes adhere to coding standard
[ ] Updated documentation

@jfversluis good catch... I'll update that shortly


Update Get-DlpCompliancePolicy.md

Updated example 3 where DistributionDetail parameter did not have dash (-DistributionDetail).

Docs Build status updates of commit 1d93389:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

exchange/exchange-ps/exchange/Get-DlpCompliancePolicy.md
:white_check_mark:Succeeded
View (exchange-ps)

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel


Parse failure: guard let self = self else { return }

🚨New Issue Checklist🚨

[ x] Updated swift-ast to the latest version
[ x] I am aware that the swift-ast -github-issue /path/to/file.swift might help me generate this file

Issue Summary
The parser fails with expected expression for syntax like the following:
guard let self = self else { return }
Reproduction Steps
Sample code
networkRequest.fetchData() { [weak self] result in
	guard let self = self else { return }

	switch result {
	case .Succeeded(let data):
		self.processData(data)

	case .Failed(let err):
		self.handleError(err)
	}
}

It could be really nice if the parser could parse vaild Swift code - upgrade self from weak to strong.
https://github.com/apple/swift-evolution/blob/master/proposals/0079-upgrade-self-from-weak-to-strong.md
Expected Result
The code should be able to be parsed.
Actual Behavior
There is a fatal error: expected expression

I am having this issue aswell!

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.
Please make sure to update to the latest version and check if that solves the issue. Let us know if that works for you by adding a comment.


[feature](merge cloud) wait system auto start

Proposed changes
Issue Number: close #xxx

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

deardeng has merge the pr, close this.


feat: add enchanting/experimentation data

Added lodash package to deep copy. If we can think of another solution, I am down to implement that instead.

The built-in structuredClone() function will likely work instead of lodash here, not positive though

The built-in structuredClone() function will likely work instead of lodash here, not positive though

I believe we're using lodash in another PR (#60) so I think might end up just keeping.


fixes #369: Added Headings to Contributors List

Added Alphabet Headings for Contributor List to group People whose name start with particular Alphabet together

As W and X are empty should we keep that or remove that for time being? What do you think @schmelto ?

As W and X are empty should we keep that or remove that for time being? What do you think @schmelto ?

but if we will remove them then the alphabet series will be broken, and then the README will not look good according to me... 🤔

As W and X are empty should we keep that or remove that for time being? What do you think @schmelto ?

I think we should leave them empty as they are for now

As W and X are empty should we keep that or remove that for time being? What do you think @schmelto ?

We should not delete that, i completely agree with @Umesh-01  point

Thank you all for the great collaboration. And a big thanks to @ish-u for the PR :)


problems using multiple monitors

Description of the new feature / enhancement
I am not an advanced user but I would like this since it would be very useful for many people
Scenario when this would be used?
good morning
I have two monitors of different resolution but the same size and it would be very useful if the mouse could be moved from one monitor to another and that the difference in pixels would be compensated, that if I move the cursor at a height of 25% of the main screen it will appear at 25% of the secondary screen regardless of the pixel difference
And the second thing even more annoying is that in my case I have since the equipment never goes into suspension but I do turn off the screens after 15min but when I turn them on again everything returns to the main screen although I have left programs on the secondary screen
It would be useful if this did not happen or at least a button with macro so that everything returns to the way it was before the screens were turned off
thanks for reading me
Supporting information
No response

I am not sure if we can do anything about this. I'd like to suggest you to file this on the Feedback hub as well.

/dup #1226


Modifying the default filters

Edges tagged with bus_guideway are not excluded from the driving, walking and cycling filters.
Changed the filter values to exclude them.
Fixes #659

Thanks!


Suggestion to restore pgadmin3 in addition to pgadmin4

These two versions of pagmin (3 and 4) are very different implementations based on different UI toolkits. Personally find pgAdmin4 ugly as heck and not pleasant to use.
Suggest to bring back the pgadmin3 cask for those of us who want to continue using it. Since the apps are called pgadmin3 and pgadmin4 it will not cause any name conflicts to keep both around.

It’s in caskroom/versions.

Thanks! I had homebrew/versions tapped but not caskroom/versions.


Using {open} option with watch re-opens browsers every change

When you configure serve like this
serve({
   open:true
})

and use rollup with watch mode
 rollup -c -w
A browser will open every time a change is made.
Can we configure this somehow? Happy to PR if I could get a pointer to the right direction

One possible fix could be: this running variable should be moved up to let server
https://github.com/thgh/rollup-plugin-serve/blob/master/src/index.js#L75


Status of FB13187399 and Xode 15.1?

I'm curious if Apple addressed FB13187399 in Xcode 15.1?

I am wondering the same. My team and I are still seeing unit tests taking 4-5x longer than normal. The release notes claim "Fixed: Executing Unit/UI tests from Xcode on the iOS Simulator takes an extended time to launch on first run of the suite. (115187363) (110330776) (FB12237092)".

Same here, we are still seeing errors related to:
Failed to get matching snapshots: Error getting main window kAXErrorServerNotFound


Keep a CHANGELOG

Let's make sure to communicate notable changes in a release (CHANGELOG.md) to the users and contributors. Every release should have relevant entry in change log. For example, what is the current set of functionalities included in the software (related to #4)? See some best practices.

Will create a changelog file after first release of Raido to prod.
The target audience for the changelog will be:

Customers of Raido service (i.e. universities/other institutions and API integrators) - either directly or indirectly where some "customer communications" process will use the changelog as input.
ARDC Change control board - for satisfying the required ARDC DevOps change control process.

https://github.com/au-research/raido/blob/main/changelog.md