Zarr Python 3 tracking issue

What is your issue?
Zarr-Python 3.0 is getting close to a full release. This issue tracks the integration of the 3.0 release with Xarray.
Here's a running list of issues we're solving upstream related to integration with Xarray:

[x] https://github.com/zarr-developers/zarr-python/pull/2113
[x] https://github.com/zarr-developers/zarr-python/pull/2204
[x] https://github.com/zarr-developers/zarr-python/pull/2186
[ ] ...?

Special shout out to @TomAugspurger has been front running a lot of this 🙌.

A few more I'm tracking:

[ ] basic zarr-python 2.x compatibility: https://github.com/zarr-developers/zarr-python/pull/2098
[ ] _FillValue and Zarr's fill_value causing valid values to be cast to NaN: https://github.com/pydata/xarray/issues/5475 (this could use feedback from the xarray maintainers).
[ ] incorrect fill_value handling for bytes and unicode dtypes: https://github.com/zarr-developers/zarr-python/issues/2153
[ ] zarr 3.x doesn't really handle object dtype (will make an issue)
[ ] Update for filters / compressor -> codecs change: https://github.com/zarr-developers/zarr-python/issues/2194 (most likely will require changes in xarray).

@TomAugspurger are you able to open a WIP PR with in-progress work. It'd be nice to see what's needed

Sure, https://github.com/pydata/xarray/pull/9552 has that.

Question for the group: does anyone object to xarray continuing to write Zarr V2 datasets by default? I hesitate to have xarray's default be different from zarr-python's, but that would relive some pressure to address https://github.com/pydata/xarray/issues/5475 quickly, since v2 datasets should be round-tripable.

I think that support for reading Zarr V2 datasets with zarr-python v3 is close to being ready. I updated https://github.com/pydata/xarray/issues/9515#issuecomment-2359242213 with some instructions on how to install two branches if anyone is able to test that out:
In [4]: xr.open_dataset("abfs://daymet-zarr/annual/hi.zarr", engine="zarr", storage_options={"account_name": "daymeteuwest"})
Out[4]:
<xarray.Dataset> Size: 137MB
Dimensions:                  (y: 584, x: 284, time: 41, nv: 2)
Coordinates:
    lat                      (y, x) float32 663kB ...
    lon                      (y, x) float32 663kB ...
  * time                     (time) datetime64[ns] 328B 1980-07-01T12:00:00 ....
  * x                        (x) float32 1kB -5.802e+06 ... -5.519e+06
  * y                        (y) float32 2kB -3.9e+04 -4e+04 ... -6.22e+05
...
    start_year:        1980

In [5]: xr.open_dataset("s3://cmip6-pds/CMIP6/ScenarioMIP/AS-RCEC/TaiESM1/ssp126/r1i1p1f1/Amon/clt/gn/v20201124", engine="zarr", storage_options={"anon": True})
Out[5]:
<xarray.Dataset> Size: 228MB
Dimensions:    (time: 1032, lat: 192, lon: 288, bnds: 2)
Coordinates:
  * lat        (lat) float64 2kB -90.0 -89.06 -88.12 -87.17 ... 88.12 89.06 90.0
...
    variant_label:             r1i1p1f1

Thank you for all your work on Zarr V3 in Xarray! Super excited about the progress here 🎉
I've been using the https://github.com/pydata/xarray/tree/zarr-v3 branch to test out icechunk, and thought I'd share some odd behavior when writing data to/from S3 just in case it's not a known issue. I ran this code multiple times - the first time only the attributes were written and the second the col and row variables were also written, but the S variable would never get written. All data variables were written if I used a local filesystem rather than object storage:
testv3_store = "s3://nasa-veda-scratch/test-weight-caching/scratch/test-v3.zarr"
s = np.ones(10, dtype='float64')
c = np.ones(10, dtype='int32')
r = np.ones(10, dtype='int32')
ds = xr.Dataset(
    data_vars=dict(
        S = (["n_s"], s),
        col = (["n_s"], c),
        row = (["n_s"], r)
    ),
    attrs=dict(n_in = 100, n_out = 200)
)
print(f"Original data vars: {ds.data_vars}")
ds.to_zarr(testv3_store, zarr_format=3, mode="w")
ds2 = xr.open_zarr(testv3_store, zarr_format=3).load()
print(f"Round tripped data vars: {ds2.data_vars}")

Original data vars: Data variables:
    S        (n_s) float64 80B 1.0 1.0 1.0 1.0 1.0 1.0 1.0 1.0 1.0 1.0
    col      (n_s) int32 40B 1 1 1 1 1 1 1 1 1 1
    row      (n_s) int32 40B 1 1 1 1 1 1 1 1 1 1
Round tripped data vars: Data variables:
    col      (n_s) int32 40B 1 1 1 1 1 1 1 1 1 1
    row      (n_s) int32 40B 1 1 1 1 1 1 1 1 1 1

Thanks for the testing it out and reporting that issue. I'll see if I can reproduce it.

This sounds like an issue with the RemoteStore in zarr3. I wonder if something bad is happening because S is a single character var name.

I'm able to reproduce with the moto test server used in the zarr-python tests. It seems like all the files were written:
(Pdb) pp store.fs.glob("test/**/*")
['test/test-weight-caching/scratch/test-v3.zarr',
 'test/test-weight-caching/scratch/test-v3.zarr/S',
 'test/test-weight-caching/scratch/test-v3.zarr/S/c',
 'test/test-weight-caching/scratch/test-v3.zarr/S/c/0',
 'test/test-weight-caching/scratch/test-v3.zarr/S/zarr.json',
 'test/test-weight-caching/scratch/test-v3.zarr/col',
 'test/test-weight-caching/scratch/test-v3.zarr/col/c',
 'test/test-weight-caching/scratch/test-v3.zarr/col/c/0',
 'test/test-weight-caching/scratch/test-v3.zarr/col/zarr.json',
 'test/test-weight-caching/scratch/test-v3.zarr/row',
 'test/test-weight-caching/scratch/test-v3.zarr/row/c',
 'test/test-weight-caching/scratch/test-v3.zarr/row/c/0',
 'test/test-weight-caching/scratch/test-v3.zarr/row/zarr.json',
 'test/test-weight-caching/scratch/test-v3.zarr/zarr.json']

I think the array metadata is correct:
(Pdb) pp json.loads(store.fs.cat("test/test-weight-caching/scratch/test-v3.zarr/S/zarr.json"))
{'attributes': {'_ARRAY_DIMENSIONS': ['n_s'], '_FillValue': 'AAAAAAAA+H8='},
 'chunk_grid': {'configuration': {'chunk_shape': [10]}, 'name': 'regular'},
 'chunk_key_encoding': {'configuration': {'separator': '/'}, 'name': 'default'},
 'codecs': [{'configuration': {'endian': 'little'}, 'name': 'bytes'}],
 'data_type': 'float64',
 'fill_value': 0.0,
 'node_type': 'array',
 'shape': [10],
 'storage_transformers': [],
 'zarr_format': 3}

Ah, the consolidated metadata is missing though?
(Pdb) pp json.loads(store.fs.cat("test/test-weight-caching/scratch/test-v3.zarr/zarr.json"))
{'attributes': {'n_in': 100, 'n_out': 200},
 'consolidated_metadata': {'kind': 'inline',
                           'metadata': {},
                           'must_understand': False},
 'node_type': 'group',
 'zarr_format': 3}

Some print statements shows that consolidated_metadata is being called, and we are writing the output to zarr.json. But it fails to discover the metadata under the group. I guess that's show in the output above, since we have metadata: {}, rather than metadata: None.
So right now it looks like an issue with Group.members using a remote store. I'll keep looking.

@maxrjones when you get a chance, can you try with storage_options={"use_listings_cache": False} in the to_zarr and open_zarr calls? That seems to fix it for me locally.

Assuming that is the issue, the problem is fsspec's dircache, which maintains a cache of directory listings. We must have previously listed the zarr.json directory and found just the zarr.json. After we've written the arrays, when we go to consolidate the metadata we list the zarr.json again, we get the stale read from the directory cache. We'll need to find a way to handle this in zarr-python. IMO, fsspec should at least be able to invalidate a cache when its the one doing the invalidating (by writing / deleting objects).

Thanks for digging into this @TomAugspurger - @rabernat and I hit something similar a week ago. See https://github.com/zarr-developers/zarr-python/pull/2348 for a zarr-side attempt at working around the fsspec cache issues.

@maxrjones when you get a chance, can you try with storage_options={"use_listings_cache": False} in the to_zarr and open_zarr calls? That seems to fix it for me locally.

Yes, adding those storage options to the to_zarr call fixes the issue. It doesn't seem to be necessary on the open_zarr call. I think this makes sense for why it wasn't an issue when using icechunk, since it doesn't rely on fsspec afaik. Thanks @TomAugspurger!


offline anuglar cli installer

I am having trouble installing the angular cli from my offline station.
As you know npm install command of @angular/cli try to reach to the npm registry and the process get aborted.
Is there a simple solution??

You might be able to use NPM offline if you have proxy, but I don't have any information about how to set it up myself. The only time Angular CLI tries to use npm install is when you do ng new though, and you can do ng new appname --skip-install to not automatically use npm install.


[BUG] Richtextbox multilingual

Version information

Laravel: v5.8
Voyager: v1.3
PHP: 7.2
Database: 5.6

Description
from any translatable bread model edit page, language switch not working with rich text box (TinyMCE) , other text fields are fine.
When I update or create it shows error page (Only when bread contains rich text box) Undefined index: en
Steps To Reproduce
Steps to reproduce the behavior:

Enable Multilingual from voyager config
Add multiple languages

'locales' => [
            'en',
            'ar',
        ],

Create Bread for any table and add rich text for a text column.
Enable Translatable from the model of the corresponding table

Expected behavior
When I update or create it shows error page (Only when bread contains rich text box) Undefined index: en

https://github.com/the-control-group/voyager/pull/4077

Closing as a duplicate of https://github.com/the-control-group/voyager/issues/4072


[WIP] 12515- unskip test display data

PR to see if this flaky test is still failing

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Choose reviewer(s) and mention them in a comment (R: @username).
[ ] Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.
[ ] Update CHANGES.md with noteworthy changes.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.

GitHub Actions Tests Status (on master branch)

See CI.md for more information about GitHub Actions CI.

Run Python PreCommit

It looks like this is still flaky: https://ci-beam.apache.org/job/beam_PreCommit_Python_Phrase/2876

@AlikRodriguez  Can we close this?


Implement QC Capsule

Is there data? (NAN, number of frames)
if <1200frames (=1min), likely a test sessions or alike
Are there NaNs in either the raw FIP data or processed FIP data?
number of ROI (columnN of the CSV) correct?
checking the source CSV (maybe QA) and nwb packaged data
Some metric of SNR.
histgram of raw values to see baseline intensity, fluctuations
Is there saturation ?
if == 65535 (16bit)
Is the trace stable?
histgram of 1st derivative, outlier detection (>% of sliding baseline mean, etc)
Are there dropped frames?
number of frames for 3 ch the same? same as number of sync pulses? (but can be QA-level)
Is there cross-talk between channels?
correlations between fibers/channels but can be tricky as we may be actually measuring highly correlated signals.
Is there bleaching?
histogram of subtracted bleaching?
Is there timing issues? Different channels locked to one another properly.
TBD what would be the best (should be agnostic to specific behavior)

[ ] need to specific what the QC capsule should do

Ok. So first, you best source of information on this is @dbirman
Here are some useful instructions.
https://aind-data-schema.readthedocs.io/en/latest/quality_control.html
Here is an example QC capsule template : https://github.com/AllenNeuralDynamics/aind-qc-capsule-example/blob/main/code/run_capsule.py
Here is the QC portal that is pulling those metrics real-time (4h delay currently). https://qc.allenneuraldynamics.org/qc_portal_app

I would recommend you both block one or 2 afternoon of work to get this started.

Kenta is still working on this.
By the end of the year, Dan and Kenta will put together a design.
By next year, Dan will help out Kenta to do this.
Jerome said that higher order analysis will be higher priority next year, so the sooner we can wrap this up, the better it will be.

@dyf  says it should be trivial to add an additional QC (but if we want to update backwards it will take more work).
Jerome thinks success for EOY is:

Data collected, processed, tracked, and QC within 24 hours.

per @hagikent -- QC will be checked by the end week...!


Minor code improvements

This looks pretty cool. I’ll look into the match commit in particular.

Closing because I’ve refactored the plugin using ES6 syntax.


Apply styler to files containing HNSW source code

To make HNSW code conform to library code conventions, astyle has been applied with the following parameters --indent=spaces=2 --style=java

Thank you, after some thought, I decided that it would be more easier for us to publish a fix for #137. Then, you could re-run styler for the updated code. Otherwise, this would require hand-merging in critical parts, which is not possible to do automatically (unlike applying a styler).
Thank you!


Add setGithubButtonId to AuthMethodPickerLayout

Add method setGithubButtonId to AuthMethodPickerLayout.java so custom UI can use Github login

@alorma thank you!  This seems like it was just a mistake, so this can go out with 4.3.2 rather than waiting for a "minor" release.

Wuhu! Many thanks @samtstern


Input text is the same as placeholder text

I believe that the input fields on the app should be updated to be easier to read, otherwise, even after filling the form fields, they all still look. This is likely breaking the WCAG standard for color contrast on a website: https://webaim.org/resources/contrastchecker/
Only the email field has a high enough contrast!

@piyushkdas0611 Please Assign this task to me


Add Enable Flattened custom result index checkbox

Description
Add Enable Flattened custom result index checkbox to allow customer to enable this feature
https://github.com/user-attachments/assets/a9d768ea-a0fc-41e0-8c4b-5e6e805d8835

Issues Resolved
https://github.com/opensearch-project/anomaly-detection/issues/1213
Check List

[ ] New functionality includes testing.

[ ] All tests pass

[ ] New functionality has been documented.
[ ] Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Looks good. Wait for CI to pass.

Looks good. Wait for CI to pass.

2 tests that are not related to my change failed for my previous commit because of this error:
FAIL public/expressions/__tests__/overlay_anomalies.test.ts
  ● Test suite failed to run

    Cannot find module '!!raw-loader!../../target/public/xjson.editor.worker.js' from '../../packages/osd-monaco/target/xjson/language.js'

They might fail again in the current run. Will monitoring it

UT CI failed due to same unrelated issue. Working with OSD team about this issue...
Summary of all failing tests
FAIL public/components/FeatureAnywhereContextMenu/AssociatedDetectors/containers/__tests__/AssociatedDetectors.test.tsx
  ● Test suite failed to run

    Cannot find module '!!raw-loader!../../target/public/xjson.editor.worker.js' from '../../packages/osd-monaco/target/xjson/language.js'
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

    Require stack:
      /Users/runner/work/anomaly-detection-dashboards-plugin/anomaly-detection-dashboards-plugin/OpenSearch-Dashboards/packages/osd-monaco/target/xjson/language.js
      /Users/runner/work/anomaly-detection-dashboards-plugin/anomaly-detection-dashboards-plugin/OpenSearch-Dashboards/packages/osd-monaco/target/xjson/index.js
      /Users/runner/work/anomaly-detection-dashboards-plugin/anomaly-detection-dashboards-plugin/OpenSearch-Dashboards/packages/osd-monaco/target/index.js
      /Users/runner/work/anomaly-detection-dashboards-plugin/anomaly-detection-dashboards-plugin/OpenSearch-Dashboards/src/plugins/data/public/antlr/opensearch_sql/code_completion.ts
      /Users/runner/work/anomaly-detection-dashboards-plugin/anomaly-detection-dashboards-plugin/OpenSearch-Dashboards/src/plugins/data/public/plugin.ts
      /Users/runner/work/anomaly-detection-dashboards-plugin/anomaly-detection-dashboards-plugin/OpenSearch-Dashboards/src/plugins/data/public/index.ts
      /Users/runner/work/anomaly-detection-dashboards-plugin/anomaly-detection-dashboards-plugin/OpenSearch-Dashboards/src/plugins/saved_objects/public/saved_object/helpers/serialize_saved_object.ts
      /Users/runner/work/anomaly-detection-dashboards-plugin/anomaly-detection-dashboards-plugin/OpenSearch-Dashboards/src/plugins/saved_objects/public/saved_object/helpers/build_saved_object.ts
      /Users/runner/work/anomaly-detection-dashboards-plugin/anomaly-detection-dashboards-plugin/OpenSearch-Dashboards/src/plugins/saved_objects/public/saved_object/saved_object.ts
      /Users/runner/work/anomaly-detection-dashboards-plugin/anomaly-detection-dashboards-plugin/OpenSearch-Dashboards/src/plugins/saved_objects/public/saved_object/index.ts
      /Users/runner/work/anomaly-detection-dashboards-plugin/anomaly-detection-dashboards-plugin/OpenSearch-Dashboards/src/plugins/saved_objects/public/plugin.ts
      /Users/runner/work/anomaly-detection-dashboards-plugin/anomaly-detection-dashboards-plugin/OpenSearch-Dashboards/src/plugins/saved_objects/public/index.ts
      /Users/runner/work/anomaly-detection-dashboards-plugin/anomaly-detection-dashboards-plugin/OpenSearch-Dashboards/src/plugins/vis_augmenter/public/saved_augment_vis/saved_augment_vis.ts
      /Users/runner/work/anomaly-detection-dashboards-plugin/anomaly-detection-dashboards-plugin/OpenSearch-Dashboards/src/plugins/vis_augmenter/public/saved_augment_vis/index.ts
      /Users/runner/work/anomaly-detection-dashboards-plugin/anomaly-detection-dashboards-plugin/OpenSearch-Dashboards/src/plugins/vis_augmenter/public/plugin.ts
      /Users/runner/work/anomaly-detection-dashboards-plugin/anomaly-detection-dashboards-plugin/OpenSearch-Dashboards/src/plugins/vis_augmenter/public/index.ts
      public/components/FeatureAnywhereContextMenu/AssociatedDetectors/containers/AssociatedDetectors.tsx
      public/components/FeatureAnywhereContextMenu/AssociatedDetectors/containers/__tests__/AssociatedDetectors.test.tsx

      37 | import { registerWorker } from '../worker_store';
      38 | // @ts-ignore
    > 39 | import workerSrc from '!!raw-loader!../../target/public/xjson.editor.worker.js';
         | ^
      40 |
      41 | const wps = new WorkerProxyService();
      42 |

      at Resolver.resolveModule (../../node_modules/jest-resolve/build/resolver.js:324:11)
      at Object.<anonymous> (../../packages/osd-monaco/src/xjson/language.ts:39:1)
      at Object.<anonymous> (../../packages/osd-monaco/src/xjson/index.ts:34:1)
      at Object.<anonymous> (../../packages/osd-monaco/src/index.ts:32:1)
      at Object.<anonymous> (../../src/plugins/data/public/antlr/opensearch_sql/code_completion.ts:6:1)
      at Object.<anonymous> (../../src/plugins/data/public/plugin.ts:96:1)
      at Object.<anonymous> (../../src/plugins/data/public/index.ts:500:1)
      at Object.<anonymous> (../../src/plugins/saved_objects/public/saved_object/helpers/serialize_saved_object.ts:34:1)
      at Object.<anonymous> (../../src/plugins/saved_objects/public/saved_object/helpers/build_saved_object.ts:34:1)
      at Object.<anonymous> (../../src/plugins/saved_objects/public/saved_object/saved_object.ts:42:1)

FAIL public/expressions/__tests__/overlay_anomalies.test.ts
  ● Test suite failed to run

    Cannot find module '!!raw-loader!../../target/public/xjson.editor.worker.js' from '../../packages/osd-monaco/target/xjson/language.js'

    Require stack:
      /Users/runner/work/anomaly-detection-dashboards-plugin/anomaly-detection-dashboards-plugin/OpenSearch-Dashboards/packages/osd-monaco/target/xjson/language.js
      /Users/runner/work/anomaly-detection-dashboards-plugin/anomaly-detection-dashboards-plugin/OpenSearch-Dashboards/packages/osd-monaco/target/xjson/index.js
      /Users/runner/work/anomaly-detection-dashboards-plugin/anomaly-detection-dashboards-plugin/OpenSearch-Dashboards/packages/osd-monaco/target/index.js
      /Users/runner/work/anomaly-detection-dashboards-plugin/anomaly-detection-dashboards-plugin/OpenSearch-Dashboards/src/plugins/data/public/antlr/opensearch_sql/code_completion.ts
      /Users/runner/work/anomaly-detection-dashboards-plugin/anomaly-detection-dashboards-plugin/OpenSearch-Dashboards/src/plugins/data/public/plugin.ts
      /Users/runner/work/anomaly-detection-dashboards-plugin/anomaly-detection-dashboards-plugin/OpenSearch-Dashboards/src/plugins/data/public/index.ts
      /Users/runner/work/anomaly-detection-dashboards-plugin/anomaly-detection-dashboards-plugin/OpenSearch-Dashboards/src/plugins/saved_objects/public/saved_object/helpers/serialize_saved_object.ts
      /Users/runner/work/anomaly-detection-dashboards-plugin/anomaly-detection-dashboards-plugin/OpenSearch-Dashboards/src/plugins/saved_objects/public/saved_object/helpers/build_saved_object.ts
      /Users/runner/work/anomaly-detection-dashboards-plugin/anomaly-detection-dashboards-plugin/OpenSearch-Dashboards/src/plugins/saved_objects/public/saved_object/saved_object.ts
      /Users/runner/work/anomaly-detection-dashboards-plugin/anomaly-detection-dashboards-plugin/OpenSearch-Dashboards/src/plugins/saved_objects/public/saved_object/index.ts
      /Users/runner/work/anomaly-detection-dashboards-plugin/anomaly-detection-dashboards-plugin/OpenSearch-Dashboards/src/plugins/saved_objects/public/plugin.ts
      /Users/runner/work/anomaly-detection-dashboards-plugin/anomaly-detection-dashboards-plugin/OpenSearch-Dashboards/src/plugins/saved_objects/public/index.ts
      /Users/runner/work/anomaly-detection-dashboards-plugin/anomaly-detection-dashboards-plugin/OpenSearch-Dashboards/src/plugins/vis_augmenter/public/saved_augment_vis/saved_augment_vis.ts
      /Users/runner/work/anomaly-detection-dashboards-plugin/anomaly-detection-dashboards-plugin/OpenSearch-Dashboards/src/plugins/vis_augmenter/public/saved_augment_vis/index.ts
      /Users/runner/work/anomaly-detection-dashboards-plugin/anomaly-detection-dashboards-plugin/OpenSearch-Dashboards/src/plugins/vis_augmenter/public/plugin.ts
      /Users/runner/work/anomaly-detection-dashboards-plugin/anomaly-detection-dashboards-plugin/OpenSearch-Dashboards/src/plugins/vis_augmenter/public/index.ts
      public/expressions/helpers.ts
      public/expressions/__tests__/overlay_anomalies.test.ts

      37 | import { registerWorker } from '../worker_store';
      38 | // @ts-ignore
    > 39 | import workerSrc from '!!raw-loader!../../target/public/xjson.editor.worker.js';
         | ^
      40 |
      41 | const wps = new WorkerProxyService();
      42 |

      at Resolver.resolveModule (../../node_modules/jest-resolve/build/resolver.js:324:11)
      at Object.<anonymous> (../../packages/osd-monaco/src/xjson/language.ts:39:1)
      at Object.<anonymous> (../../packages/osd-monaco/src/xjson/index.ts:34:1)
      at Object.<anonymous> (../../packages/osd-monaco/src/index.ts:32:1)
      at Object.<anonymous> (../../src/plugins/data/public/antlr/opensearch_sql/code_completion.ts:6:1)
      at Object.<anonymous> (../../src/plugins/data/public/plugin.ts:96:1)
      at Object.<anonymous> (../../src/plugins/data/public/index.ts:500:1)
      at Object.<anonymous> (../../src/plugins/saved_objects/public/saved_object/helpers/serialize_saved_object.ts:34:1)
      at Object.<anonymous> (../../src/plugins/saved_objects/public/saved_object/helpers/build_saved_object.ts:34:1)
      at Object.<anonymous> (../../src/plugins/saved_objects/public/saved_object/saved_object.ts:42:1)

Test Suites: 2 failed, 1 skipped, 77 passed, 79 of 80 total
Tests:       2 skipped, 371 passed, 373 total
Snapshots:   71 passed, 71 total
Time:        175.192 s
Ran all test suites.
error Command failed with exit code 1.
Error: Process completed with exit code 1.

tracking the failing ut issue here - https://github.com/opensearch-project/anomaly-detection-dashboards-plugin/issues/832


the selector stuff to indicate if a text view is clicked not working?

i write some selector drawables including normal state and selected state.
when i used them in verticalLayout in Activity.create(), it's not working.
is Anko designed to abandon all xml stuff, or i did something wrong?

Can you show some code?


how i make the opponent notes only downscroll?

Describe your problem here.
i'm trying to make a script that make the opponent notes only go from up to down (downscroll) like this:

it can be in haxe or lua whatever but i just want an answer please
Are you modding a build from source or with Lua?
Lua
What is your build target?
Windows x64
Did you edit anything in this build? If so, mention or summarize your changes.
no

podrías utilizar ''setPropertyFromGroup('opponentStrums', 0, 'y', 570)'' y ''setPropertyFromGroup('strumLineNotes', 1, 'direction', 270)'' creo que funcionaria

it worked but the notes are like this:

Prueba esto:
luaDebugMode = true NotasDad = {0, 570, 570, 570, 570}
function onCreatePost() for i = 0, 3 do setPropertyFromGroup('opponentStrums', i, 'y', NotasDad[i + 2]) end end
function onUpdatePost() songosition = getSongPosition() songSpeed = getProperty('songSpeed')
for i = 0, getProperty('notes.length') - 1 do
    if not getPropertyFromGroup('notes', i, 'mustPress') then
        noteData = getPropertyFromGroup('notes', i, 'noteData')
        strumTime = getPropertyFromGroup('notes', i, 'strumTime')
        Y = NotasDad[noteData + 2] + 0.45 * (songPosition - strumTime) * songSpeed
        setPropertyFromGroup('notes', i, 'y', Y)

        if getPropertyFromGroup('notes', i, 'isSustainNote') then
            setPropertyFromGroup('notes', i, 'angle', 180)
        end
    end
end

end

it didn't work

perdon me confundí en 'songosition = getSongPosition()'  en realidad es 'songPosition = getSongPosition()'
codigo:

perdon me confundí en 'songosition = getSongPosition()' en realidad es 'songPosition = getSongPosition()' codigo:

i worked but the sustain notes look like this:

but thank you man i'm not all that good in lua script but this don't have solution right? anyway it's good for me thanks again

I tried on a faster song and also saw that error. So, I started looking for something to fix it in PlayState, and I found this, but I don't know if it works. The only thing is that you have to do it in Lua:


Refactor: shorten & un-nest functions, re-think return values

Opening this issue for visibility (and also because I'd like to do this :D)
Imo it'd help with readability and maintainability to do a refactoring run.
Things that I've been bumping into:

[ ] checks in notmain() could be pulled into separate functions for readability
[ ] construct_backtrace() is pretty long and involved; amount of parameters is smelly
[ ] construct_backtrace() always returns OK, even if there was an exception (then it's an OK(Some(TopException))). Returning a Result<(), TopException> would be more intuitive imo, but this could also be that I'm misunderstanding anyhow::Error
[ ] update_cfa()has another unintuive return value, could be Option<new_cfa> imo

These can also be sneaked in as drive-bys on bugfixes and feature implementation.

Totally agree that there is room for quite some refactoring!
Also we might want to add some unit, but also end-to-end tests. Maybe the kind of @jonas-schievink described in the github-actions blog Post :)

very much agreed! I've tracked that one in https://github.com/knurling-rs/probe-run/issues/173 :D Maybe we can chat about planning/funds for this in the next bi-weekly?

construct_backtrace was refactored in PR #197

@Lotterleben Do you consider this resolved by #222?

very much so! thanks for the bump


not able to run example server , client

https://github.com/crs4/hl7apy/issues/30#issue-210109399
I am trying on python 2.7.12

https://github.com/Nabellaleen/hl7apy/tree/master examples working fine..


Do not trim whitespace around custom elements

Thanks for the great library! We have a usecase where our HTML has custom React elements inside it, like this:

Paragraph with <CustomElement /> between text

And when used with collapse: true, react-pdf-html will strip the whitespace around the custom element so you end up displaying this in the PDF:

Paragraph with<CustomElement />between text

This is not desireable. This PR updates the block detection logic so that custom elements are considered as non-block elements to handle this situation gracefully.
I fully recognize that this isn't a fully complete solution as it's possible that your custom element might actually be a block element, but I think supporting that would require very complex recursive logic to review the contents of all children. The implementation in this PR keeps things pretty simple and works for the most basic usecases, which will be enough for us (and hopefully others).
I hope you'll consider this PR and include it in the library! Any feedback is appreciated.

@danomatic Thank you for merging this! Would you mind releasing a new version of react-pdf-html when you get a chance?


Client Crash when ME Conduits shall connect

When I try to connect a ME Conduit to anything other (even another ME Conduit) the client crashes.
AE v2beta8 is installed. EnderIO{1.7.10-<IP_ADDRESS>4}
Crashreport: http://c0nnex.de/dl/crash-2015-02-20_16.20.47-client.txt

Update to EnderIO version 2.2.8 build 349 available on Curse


Removed the plural s from DataModelParameters

Removed the plural s from DataModelParameters from the Get-RsRestItemDataModelParameters & Set-RsRestItemDataModelParameters functions, to meet the PowerShell naming standard.
Changes proposed in this pull request:

Removed the plural s from the Get-RsRestItemDataModelParameters function, added an alias.
Removed the plural s from the Set-RsRestItemDataModelParameters function, added an alias.
Updated the corresponding tests as well.

How to test this code:

Run the updated Pester tests.

Has been tested on (remove any that don't apply):

PowerShell 7.1
Windows 10
PBIRS

This is a breaking change, we have documentation that references this. Also this is the same name used by the RestAPI which this command is wrapping, my opinion is that we keep consistent with that.

This won't be a breaking change since I added the alias' to the commands to export.  There's no reason to continue with the wrong names.


dscp value set through GRPC_ARG_DSCP channel argument does not cause the socket options to be updated on the GRPC server side.

What version of gRPC and what language are you using?
grpc C++ V1.60.0
What operating system (Linux, Windows,...) and version?
AlmaLinux 9
I recently upgraded to v1.60.0 to use the GRPC_ARG_DSCP channel argument that was added as part of https://github.com/grpc/grpc/pull/28322. But I noticed that after adding the following change to server side code when initializing and starting the grpc service,
"""
builder.AddChannelArgument(GRPC_ARG_DSCP, dscp);
"""
The tos value was not getting set in the stream channel packets sent from the server to the client.
After looking at the grpc c++ core library code, I noticed that the "PosixTcpOptions" arg passed to PrepareSocket ( core/lib/event_engine/posix_engine/posix_engine_listener_utils.cc ) has the custom dscp value set. But there is no call to set dscp socket options inside the function.
"""
absl::Status PrepareSocket(const PosixTcpOptions& options,
ListenerSocket& socket) {
....
GRPC_RETURN_IF_ERROR(socket.sock.SetSocketNonBlocking(1));
GRPC_RETURN_IF_ERROR(socket.sock.SetSocketCloexec(1));
if (socket.addr.address()->sa_family != AF_UNIX &&
!ResolvedAddressIsVSock(socket.addr)) {
GRPC_RETURN_IF_ERROR(socket.sock.SetSocketLowLatency(1));
GRPC_RETURN_IF_ERROR(socket.sock.SetSocketReuseAddr(1));
GRPC_RETURN_IF_ERROR(socket.sock.SetSocketDscp(options.dscp));
socket.sock.TrySetSocketTcpUserTimeout(options, false);
}
GRPC_RETURN_IF_ERROR(socket.sock.SetSocketNoSigpipeIfPossible());
GRPC_RETURN_IF_ERROR(socket.sock.ApplySocketMutatorInOptions(
GRPC_FD_SERVER_LISTENER_USAGE, options));
"""
Adding "GRPC_RETURN_IF_ERROR(socket.sock.SetSocketDscp(options.dscp));" fixed the issue and I do see the tos value being set correctly in the outgoing packets from the server side. But I would like to get some confirmation if the fix is the right one and how this got missed in PR# 28322

@bjosv Any thoughts?

Ouch, its my mistake. During development and delivery the event_engine_listener feature was OFF by default and today it ON by default. When investigating how this got through I see that the feature was not enabled correctly in our setup, resulting in that the iomgr codepath was running while verifying the EventEngine path.
I verified it correctly this time and created a PR with the fix, sorry.


Change approval of e2e issuer to use cmctl

Uses cmctl to approve the e2e test certificate, since the previous logic causes problems if other CRs are present in the e2e cluster and found by the kubectl get
Plus cmctl is cleaner to use for this anyway!

/approve


[Bug] [BYOC] After partitioning through BYOC, the constant memory of the operator in the model is out of order

After partitioning through BYOC, the constant memory in the operator in the model is out of order

I don't think this is a problem. Actually I'm not sure if these numbers represent some ordering. Feel free to reopen if this is causing you a real problem.


OSX 64bit build error

Brief Description
Trying to build CppSharp release_x64 causes System.NotSupportedException: Specified method is not supported.
OS:  OS X El Capitan 10.11.6 (15G1004)
Build process

Clone CppSharp: git clone git@github.com:mono/CppSharp.git. The latest CppSharp revision for this was f5ea7a1d50143b20f41f3eee53eb15e23f58cd79
Change CppSharp/build/Scripts/LLVM.lua:264 to    "-DLLVM_ENABLE_LIBCXX=true -DLLVM_BUILD_32_BITS=false" or ""
clone_llvm in premake failed so clone LLVM manually with git clone https://github.com/llvm-mirror/llvm.git /Users/(removed)/Documents/CppSharp/CppSharp/deps/llvm
clone_llvm in premake failed so clone Clang manually with git clone https://github.com/llvm-mirror/clang.git /Users/(removed)/Documents/CppSharp/CppSharp/deps/llvm/tools/clang
Run

 ../premake5-osx --file=LLVM.lua clone_llvm
 ../premake5-osx --file=LLVM.lua build_llvm
 ../premake5-osx --file=LLVM.lua package_llvm

(cloning step to ensure correct revision in clang and LLVM)
6) Run ./premake5-osx gmake
7) Run config=release_x64 make -C gmake
Target: CppSharp
Build script output
config=release_x64 make -C gmake
==== Building CppSharp.AST (release_x64) ====
Creating ../lib/Release_x64
Creating ../obj/Release_x64/x64/Release/CppSharp.AST
Generating response file
==== Building CppSharp (release_x64) ====
Creating ../obj/Release_x64/x64/Release/CppSharp
Generating response file
../../../src/Core/Toolchains/MSVCToolchain.cs(193,17): warning CS0219: The variable `includes' is assigned but its value is never used
Compilation succeeded - 1 warning(s)
==== Building CppSharp.Runtime (release_x64) ====
Creating ../obj/Release_x64/x64/Release/CppSharp.Runtime
Generating response file
==== Building CppSharp.CppParser (release_x64) ====
Creating ../obj/Release_x64/x64/Release/CppSharp.CppParser
AST.cpp
Comments.cpp
CppParser.cpp
Parser.cpp
../../../src/CppParser/Parser.cpp:381:13: warning: 28 enumeration values not handled in switch: 'UnknownOS', 'CloudABI',
      'Darwin'... [-Wswitch]
    switch (Target.getOS()) {
            ^
../../../src/CppParser/Parser.cpp:2714:13: warning: 42 enumeration values not handled in switch: 'Builtin', 'Complex',
      'Pointer'... [-Wswitch]
    switch (Loc.getTypeLocClass())
            ^
../../../src/CppParser/Parser.cpp:3534:22: warning: using the result of an assignment as a condition without parentheses
      [-Wparentheses]
        if (Existing = NS->FindTypedef(Name, /*Create=*/false))
            ~~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
../../../src/CppParser/Parser.cpp:3534:22: note: place parentheses around the assignment to silence this warning
        if (Existing = NS->FindTypedef(Name, /*Create=*/false))
                     ^
            (                                                 )
../../../src/CppParser/Parser.cpp:3534:22: note: use '==' to turn this assignment into an equality comparison
        if (Existing = NS->FindTypedef(Name, /*Create=*/false))
                     ^
                     ==
../../../src/CppParser/Parser.cpp:3558:22: warning: using the result of an assignment as a condition without parentheses
      [-Wparentheses]
        if (Existing = NS->FindTypeAlias(Name, /*Create=*/false))
            ~~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
../../../src/CppParser/Parser.cpp:3558:22: note: place parentheses around the assignment to silence this warning
        if (Existing = NS->FindTypeAlias(Name, /*Create=*/false))
                     ^
            (                                                   )
../../../src/CppParser/Parser.cpp:3558:22: note: use '==' to turn this assignment into an equality comparison
        if (Existing = NS->FindTypeAlias(Name, /*Create=*/false))
                     ^
                     ==
4 warnings generated.
Sources.cpp
Target.cpp
Linking CppSharp.CppParser
ld: warning: directory not found for option '-L/usr/lib64'
Running postbuild commands
cp -rf /Users/(removed)/Documents/CppSharp/CppSharp/build/scripts/llvm-cccdd2-macosx-Release/lib ../lib/Release_x64
==== Building CppSharp.Parser.CSharp (release_x64) ====
Creating ../obj/Release_x64/x64/Release/CppSharp.Parser.CSharp
Generating response file
==== Building CppSharp.Parser (release_x64) ====
Creating ../obj/Release_x64/x64/Release/CppSharp.Parser
Generating response file
../../../src/Parser/ASTConverter.cs(888,27): warning CS0184: The given expression is never of the provided (`CppSharp.Parser.AST.PreprocessedEntity') type
Compilation succeeded - 1 warning(s)
==== Building CppSharp.Generator (release_x64) ====
Creating ../obj/Release_x64/x64/Release/CppSharp.Generator
Generating response file
../../../src/Generator/Generator.cs(91,21): warning CS0219: The variable `includeDir' is assigned but its value is never used
../../../src/Generator/Generators/CSharp/CSharpSources.cs(2691,25): warning CS0219: The variable `specialization' is assigned but its value is never used
../../../src/Generator/Passes/IgnoreSystemDeclarationsPass.cs(58,29): warning CS0219: The variable `l' is assigned but its value is never used
../../../src/Generator/BindingContext.cs(27,60): warning CS0414: The private field `CppSharp.Generators.BindingContext.libraryMappings' is assigned but its value is never used
Compilation succeeded - 4 warning(s)
==== Building CppSharp.Generator.Tests (release_x64) ====
Creating ../obj/Release_x64/x64/Release/CppSharp.Generator.Tests
Generating response file
==== Building CLI.Native (release_x64) ====
Creating ../obj/Release_x64/x64/Release/CLI.Native
CLI.cpp
In file included from ../../../tests/CLI/CLI.cpp:1:
../../../tests/CLI/CLI.h:17:46: warning: calling convention 'stdcall' ignored for this target [-Wignored-attributes]
    typedef int AttributedFuncType(int, int) ATTR;
                                             ^
../../../tests/CLI/CLI.h:10:29: note: expanded from macro 'ATTR'
#define ATTR __attribute__((stdcall))
                            ^
1 warning generated.
Linking CLI.Native
ld: warning: directory not found for option '-L/usr/lib64'
==== Building CLI.Gen (release_x64) ====
Creating ../obj/Release_x64/x64/Release/CLI.Gen
Generating response file
==== Building Common.Native (release_x64) ====
Creating ../obj/Release_x64/x64/Release/Common.Native
AnotherUnit.cpp
Common.cpp
In file included from ../../../tests/Common/Common.cpp:1:
../../../tests/Common/Common.h:323:14: warning: calling convention 'stdcall' ignored for this target [-Wignored-attributes]
typedef int (STDCALL *DelegateStdCall)(int);
             ^
../../../tests/Common/../Tests.h:17:32: note: expanded from macro 'STDCALL'
#define STDCALL __attribute__((stdcall))
                               ^
In file included from ../../../tests/Common/Common.cpp:1:
../../../tests/Common/Common.h:1082:9: warning: 'visibility' attribute ignored [-Wignored-attributes]
typedef DLL_API union
        ^
../../../tests/Common/../Tests.h:14:33: note: expanded from macro 'DLL_API'
#define DLL_API __attribute__ ((visibility ("default")))
                                ^
2 warnings generated.
Linking Common.Native
ld: warning: directory not found for option '-L/usr/lib64'
==== Building Common.Gen (release_x64) ====
Creating ../obj/Release_x64/x64/Release/Common.Gen
Generating response file
==== Building Common.CSharp (release_x64) ====
Creating ../obj/Release_x64/x64/Release/Common.CSharp
Running prebuild commands
mono --debug "../lib/Release_x64/Common.Gen.exe"

Generating bindings for Common (CLI)
Looking for tests in: /Users/(removed)/Documents/CppSharp/CppSharp/tests/Common
Parsed 'AnotherUnit.h, Common.h'

Unhandled Exception:
System.NotSupportedException: Specified method is not supported.
  at CppSharp.Generators.CLI.CLITypePrinter.VisitPrimitiveType (CppSharp.AST.PrimitiveType primitive) [0x00166] in /Users/(removed)/Documents/CppSharp/CppSharp/src/Generator/Generators/CLI/CLITypePrinter.cs:229
  at CppSharp.Generators.CLI.CLITypePrinter.VisitBuiltinType (CppSharp.AST.BuiltinType builtin, CppSharp.AST.TypeQualifiers quals) [0x00008] in /Users/(removed)/Documents/CppSharp/CppSharp/src/Generator/Generators/CLI/CLITypePrinter.cs:198
  at CppSharp.AST.BuiltinType.Visit[T] (CppSharp.AST.ITypeVisitor`1[T] visitor, CppSharp.AST.TypeQualifiers quals) [0x00004] in /Users/(removed)/Documents/CppSharp/CppSharp/src/AST/Type.cs:1164
  at CppSharp.Generators.CLI.CLIGenerator.TypePrinterDelegate (CppSharp.AST.Type type) [0x00011] in /Users/(removed)/Documents/CppSharp/CppSharp/src/Generator/Generators/CLI/CLIGenerator.cs:50
  at CppSharp.AST.Type.ToString () [0x00007] in /Users/(removed)/Documents/CppSharp/CppSharp/src/AST/Type.cs:37
  at CppSharp.AST.QualifiedType.ToString () [0x00007] in /Users/(removed)/Documents/CppSharp/CppSharp/src/AST/Type.cs:81
  at CppSharp.AST.Declaration.<GetDeclName>m__9 (CppSharp.AST.TemplateArgument a) [0x00028] in /Users/(removed)/Documents/CppSharp/CppSharp/src/AST/Declaration.cs:195
  at (wrapper delegate-invoke) System.Func`2[CppSharp.AST.TemplateArgument,System.String]:invoke_TResult_T (CppSharp.AST.TemplateArgument)
  at System.Linq.Enumerable+WhereSelectListIterator`2[TSource,TResult].MoveNext () [0x00064] in /private/tmp/mono-20160919-56374-10ac2i9/mono-4.6.0/mcs/class/referencesource/System.Core/System/Linq/Enumerable.cs:372
  at System.String.Join (System.String separator, System.Collections.Generic.IEnumerable`1[T] values) [0x00025] in /private/tmp/mono-20160919-56374-10ac2i9/mono-4.6.0/mcs/class/referencesource/mscorlib/system/string.cs:172
  at CppSharp.AST.Declaration.GetDeclName (CppSharp.AST.Declaration decl, System.String name) [0x00041] in /Users/(removed)/Documents/CppSharp/CppSharp/src/AST/Declaration.cs:194
  at CppSharp.AST.Declaration.<get_QualifiedName>m__1 (CppSharp.AST.Declaration decl) [0x00007] in /Users/(removed)/Documents/CppSharp/CppSharp/src/AST/Declaration.cs:158
  at CppSharp.AST.Declaration.GetQualifiedName (System.Func`2[T,TResult] getName, System.Func`2[T,TResult] getNamespace) [0x00059] in /Users/(removed)/Documents/CppSharp/CppSharp/src/AST/Declaration.cs:134
  at CppSharp.AST.Declaration.get_QualifiedName () [0x0003c] in /Users/(removed)/Documents/CppSharp/CppSharp/src/AST/Declaration.cs:158
  at CppSharp.Passes.ResolveIncompleteDeclsPass.EnsureCompleteDeclaration (CppSharp.AST.Declaration declaration) [0x00029] in /Users/(removed)/Documents/CppSharp/CppSharp/src/Generator/Passes/ResolveIncompleteDeclsPass.cs:68
  at CppSharp.Passes.ResolveIncompleteDeclsPass.VisitClassDecl (CppSharp.AST.Class class) [0x00016] in /Users/(removed)/Documents/CppSharp/CppSharp/src/Generator/Passes/ResolveIncompleteDeclsPass.cs:13
  at CppSharp.AST.AstVisitor.VisitClassTemplateSpecializationDecl (CppSharp.AST.ClassTemplateSpecialization specialization) [0x00003] in /Users/(removed)/Documents/CppSharp/CppSharp/src/AST/ASTVisitor.cs:463
  at CppSharp.AST.ClassTemplateSpecialization.Visit[T] (CppSharp.AST.IDeclVisitor`1[T] visitor) [0x00003] in /Users/(removed)/Documents/CppSharp/CppSharp/src/AST/Template.cs:307
  at CppSharp.AST.AstVisitor.VisitClassTemplateDecl (CppSharp.AST.ClassTemplate template) [0x00072] in /Users/(removed)/Documents/CppSharp/CppSharp/src/AST/ASTVisitor.cs:454
  at CppSharp.Passes.ResolveIncompleteDeclsPass.VisitClassTemplateDecl (CppSharp.AST.ClassTemplate template) [0x00015] in /Users/(removed)/Documents/CppSharp/CppSharp/src/Generator/Passes/ResolveIncompleteDeclsPass.cs:20
  at CppSharp.AST.ClassTemplate.Visit[T] (CppSharp.AST.IDeclVisitor`1[T] visitor) [0x00003] in /Users/(removed)/Documents/CppSharp/CppSharp/src/AST/Template.cs:213
  at CppSharp.AST.AstVisitor.VisitDeclarationContext (CppSharp.AST.DeclarationContext context) [0x0012a] in /Users/(removed)/Documents/CppSharp/CppSharp/src/AST/ASTVisitor.cs:535
  at CppSharp.AST.AstVisitor.VisitNamespace (CppSharp.AST.Namespace namespace) [0x00003] in /Users/(removed)/Documents/CppSharp/CppSharp/src/AST/ASTVisitor.cs:515
  at CppSharp.AST.Namespace.Visit[T] (CppSharp.AST.IDeclVisitor`1[T] visitor) [0x00003] in /Users/(removed)/Documents/CppSharp/CppSharp/src/AST/Namespace.cs:461
  at CppSharp.AST.AstVisitor.VisitDeclarationContext (CppSharp.AST.DeclarationContext context) [0x0027e] in /Users/(removed)/Documents/CppSharp/CppSharp/src/AST/ASTVisitor.cs:550
  at CppSharp.AST.AstVisitor.VisitNamespace (CppSharp.AST.Namespace namespace) [0x00003] in /Users/(removed)/Documents/CppSharp/CppSharp/src/AST/ASTVisitor.cs:515
  at CppSharp.AST.Namespace.Visit[T] (CppSharp.AST.IDeclVisitor`1[T] visitor) [0x00003] in /Users/(removed)/Documents/CppSharp/CppSharp/src/AST/Namespace.cs:461
  at CppSharp.AST.AstVisitor.VisitDeclarationContext (CppSharp.AST.DeclarationContext context) [0x0027e] in /Users/(removed)/Documents/CppSharp/CppSharp/src/AST/ASTVisitor.cs:550
  at CppSharp.Passes.TranslationUnitPass.VisitTranslationUnit (CppSharp.AST.TranslationUnit unit) [0x00036] in /Users/(removed)/Documents/CppSharp/CppSharp/src/Generator/Passes/Pass.cs:38
  at CppSharp.Passes.TranslationUnitPass.VisitLibrary (CppSharp.AST.ASTContext context) [0x0001d] in /Users/(removed)/Documents/CppSharp/CppSharp/src/Generator/Passes/Pass.cs:25
  at CppSharp.Generators.BindingContext.<RunPasses>m__0 (CppSharp.Passes.TranslationUnitPass pass) [0x0002e] in /Users/(removed)/Documents/CppSharp/CppSharp/src/Generator/BindingContext.cs:53
  at CppSharp.PassBuilder`1[T].RunPasses (System.Action`1[T] action) [0x0001d] in /Users/(removed)/Documents/CppSharp/CppSharp/src/Generator/Passes/PassBuilder.cs:49
  at CppSharp.Generators.BindingContext.RunPasses () [0x00013] in /Users/(removed)/Documents/CppSharp/CppSharp/src/Generator/BindingContext.cs:48
  at CppSharp.Driver.ProcessCode () [0x00007] in /Users/(removed)/Documents/CppSharp/CppSharp/src/Generator/Driver.cs:345
  at CppSharp.ConsoleDriver.Run (CppSharp.ILibrary library) [0x00136] in /Users/(removed)/Documents/CppSharp/CppSharp/src/Generator/Driver.cs:510
  at CppSharp.Tests.CommonTestsGenerator.Main (System.String[] args) [0x00007] in /Users/(removed)/Documents/CppSharp/CppSharp/tests/Common/Common.cs:96
[ERROR] FATAL UNHANDLED EXCEPTION: System.NotSupportedException: Specified method is not supported.
  at CppSharp.Generators.CLI.CLITypePrinter.VisitPrimitiveType (CppSharp.AST.PrimitiveType primitive) [0x00166] in /Users/(removed)/Documents/CppSharp/CppSharp/src/Generator/Generators/CLI/CLITypePrinter.cs:229
  at CppSharp.Generators.CLI.CLITypePrinter.VisitBuiltinType (CppSharp.AST.BuiltinType builtin, CppSharp.AST.TypeQualifiers quals) [0x00008] in /Users/(removed)/Documents/CppSharp/CppSharp/src/Generator/Generators/CLI/CLITypePrinter.cs:198
  at CppSharp.AST.BuiltinType.Visit[T] (CppSharp.AST.ITypeVisitor`1[T] visitor, CppSharp.AST.TypeQualifiers quals) [0x00004] in /Users/(removed)/Documents/CppSharp/CppSharp/src/AST/Type.cs:1164
  at CppSharp.Generators.CLI.CLIGenerator.TypePrinterDelegate (CppSharp.AST.Type type) [0x00011] in /Users/(removed)/Documents/CppSharp/CppSharp/src/Generator/Generators/CLI/CLIGenerator.cs:50
  at CppSharp.AST.Type.ToString () [0x00007] in /Users/(removed)/Documents/CppSharp/CppSharp/src/AST/Type.cs:37
  at CppSharp.AST.QualifiedType.ToString () [0x00007] in /Users/(removed)/Documents/CppSharp/CppSharp/src/AST/Type.cs:81
  at CppSharp.AST.Declaration.<GetDeclName>m__9 (CppSharp.AST.TemplateArgument a) [0x00028] in /Users/(removed)/Documents/CppSharp/CppSharp/src/AST/Declaration.cs:195
  at (wrapper delegate-invoke) System.Func`2[CppSharp.AST.TemplateArgument,System.String]:invoke_TResult_T (CppSharp.AST.TemplateArgument)
  at System.Linq.Enumerable+WhereSelectListIterator`2[TSource,TResult].MoveNext () [0x00064] in /private/tmp/mono-20160919-56374-10ac2i9/mono-4.6.0/mcs/class/referencesource/System.Core/System/Linq/Enumerable.cs:372
  at System.String.Join (System.String separator, System.Collections.Generic.IEnumerable`1[T] values) [0x00025] in /private/tmp/mono-20160919-56374-10ac2i9/mono-4.6.0/mcs/class/referencesource/mscorlib/system/string.cs:172
  at CppSharp.AST.Declaration.GetDeclName (CppSharp.AST.Declaration decl, System.String name) [0x00041] in /Users/(removed)/Documents/CppSharp/CppSharp/src/AST/Declaration.cs:194
  at CppSharp.AST.Declaration.<get_QualifiedName>m__1 (CppSharp.AST.Declaration decl) [0x00007] in /Users/(removed)/Documents/CppSharp/CppSharp/src/AST/Declaration.cs:158
  at CppSharp.AST.Declaration.GetQualifiedName (System.Func`2[T,TResult] getName, System.Func`2[T,TResult] getNamespace) [0x00059] in /Users/(removed)/Documents/CppSharp/CppSharp/src/AST/Declaration.cs:134
  at CppSharp.AST.Declaration.get_QualifiedName () [0x0003c] in /Users/(removed)/Documents/CppSharp/CppSharp/src/AST/Declaration.cs:158
  at CppSharp.Passes.ResolveIncompleteDeclsPass.EnsureCompleteDeclaration (CppSharp.AST.Declaration declaration) [0x00029] in /Users/(removed)/Documents/CppSharp/CppSharp/src/Generator/Passes/ResolveIncompleteDeclsPass.cs:68
  at CppSharp.Passes.ResolveIncompleteDeclsPass.VisitClassDecl (CppSharp.AST.Class class) [0x00016] in /Users/(removed)/Documents/CppSharp/CppSharp/src/Generator/Passes/ResolveIncompleteDeclsPass.cs:13
  at CppSharp.AST.AstVisitor.VisitClassTemplateSpecializationDecl (CppSharp.AST.ClassTemplateSpecialization specialization) [0x00003] in /Users/(removed)/Documents/CppSharp/CppSharp/src/AST/ASTVisitor.cs:463
  at CppSharp.AST.ClassTemplateSpecialization.Visit[T] (CppSharp.AST.IDeclVisitor`1[T] visitor) [0x00003] in /Users/(removed)/Documents/CppSharp/CppSharp/src/AST/Template.cs:307
  at CppSharp.AST.AstVisitor.VisitClassTemplateDecl (CppSharp.AST.ClassTemplate template) [0x00072] in /Users/(removed)/Documents/CppSharp/CppSharp/src/AST/ASTVisitor.cs:454
  at CppSharp.Passes.ResolveIncompleteDeclsPass.VisitClassTemplateDecl (CppSharp.AST.ClassTemplate template) [0x00015] in /Users/(removed)/Documents/CppSharp/CppSharp/src/Generator/Passes/ResolveIncompleteDeclsPass.cs:20
  at CppSharp.AST.ClassTemplate.Visit[T] (CppSharp.AST.IDeclVisitor`1[T] visitor) [0x00003] in /Users/(removed)/Documents/CppSharp/CppSharp/src/AST/Template.cs:213
  at CppSharp.AST.AstVisitor.VisitDeclarationContext (CppSharp.AST.DeclarationContext context) [0x0012a] in /Users/(removed)/Documents/CppSharp/CppSharp/src/AST/ASTVisitor.cs:535
  at CppSharp.AST.AstVisitor.VisitNamespace (CppSharp.AST.Namespace namespace) [0x00003] in /Users/(removed)/Documents/CppSharp/CppSharp/src/AST/ASTVisitor.cs:515
  at CppSharp.AST.Namespace.Visit[T] (CppSharp.AST.IDeclVisitor`1[T] visitor) [0x00003] in /Users/(removed)/Documents/CppSharp/CppSharp/src/AST/Namespace.cs:461
  at CppSharp.AST.AstVisitor.VisitDeclarationContext (CppSharp.AST.DeclarationContext context) [0x0027e] in /Users/(removed)/Documents/CppSharp/CppSharp/src/AST/ASTVisitor.cs:550
  at CppSharp.AST.AstVisitor.VisitNamespace (CppSharp.AST.Namespace namespace) [0x00003] in /Users/(removed)/Documents/CppSharp/CppSharp/src/AST/ASTVisitor.cs:515
  at CppSharp.AST.Namespace.Visit[T] (CppSharp.AST.IDeclVisitor`1[T] visitor) [0x00003] in /Users/(removed)/Documents/CppSharp/CppSharp/src/AST/Namespace.cs:461
  at CppSharp.AST.AstVisitor.VisitDeclarationContext (CppSharp.AST.DeclarationContext context) [0x0027e] in /Users/(removed)/Documents/CppSharp/CppSharp/src/AST/ASTVisitor.cs:550
  at CppSharp.Passes.TranslationUnitPass.VisitTranslationUnit (CppSharp.AST.TranslationUnit unit) [0x00036] in /Users/(removed)/Documents/CppSharp/CppSharp/src/Generator/Passes/Pass.cs:38
  at CppSharp.Passes.TranslationUnitPass.VisitLibrary (CppSharp.AST.ASTContext context) [0x0001d] in /Users/(removed)/Documents/CppSharp/CppSharp/src/Generator/Passes/Pass.cs:25
  at CppSharp.Generators.BindingContext.<RunPasses>m__0 (CppSharp.Passes.TranslationUnitPass pass) [0x0002e] in /Users/(removed)/Documents/CppSharp/CppSharp/src/Generator/BindingContext.cs:53
  at CppSharp.PassBuilder`1[T].RunPasses (System.Action`1[T] action) [0x0001d] in /Users/(removed)/Documents/CppSharp/CppSharp/src/Generator/Passes/PassBuilder.cs:49
  at CppSharp.Generators.BindingContext.RunPasses () [0x00013] in /Users/(removed)/Documents/CppSharp/CppSharp/src/Generator/BindingContext.cs:48
  at CppSharp.Driver.ProcessCode () [0x00007] in /Users/(removed)/Documents/CppSharp/CppSharp/src/Generator/Driver.cs:345
  at CppSharp.ConsoleDriver.Run (CppSharp.ILibrary library) [0x00136] in /Users/(removed)/Documents/CppSharp/CppSharp/src/Generator/Driver.cs:510
  at CppSharp.Tests.CommonTestsGenerator.Main (System.String[] args) [0x00007] in /Users/(removed)/Documents/CppSharp/CppSharp/tests/Common/Common.cs:96
make[1]: *** [prebuild] Error 1
make: *** [Common.CSharp] Error 2

Tried to look at this yesterday, the exception itself is pretty easy to fix.
But then the build still fails.
Turns out the build system already has some code to deal with 64-bit Mono in https://github.com/mono/CppSharp/blob/master/src/CppParser/Bindings/CSharp/premake5.lua#L21.
The problem is that we check if the Mono binary itself is 64-bit, which in the latest SDKs is false, we need to check for the existence of a mono64 binary.
But then I hit a Premake bug, https://github.com/premake/premake-core/issues/589.
I have a workaround idea in mind which should work which I'll send once I get a chance.

That's unfortunate, but thanks for the effort. Where did your Mono binary come from? AFAIK, Homebrew installs a 64bit binary, which would probably sidestep the issue you ran into. On my system:
lipo -info `which mono`
Non-fat file: /usr/local/bin/mono is architecture: x86_64

Would you mind putting the fix to my initial problem available somewhere so I can check?

Yeah if you are using the build from Homebrew then the existing code should be fine.
I sent the fix I talked about, see if it works for you.

Yup, worked and built nicely. Now onto learning how to use this thing :) Thanks a bunch!

could you link this issue in the official readme? took me a bit to find it

@mschneider I'd rather fix the issue you're having directly. Can you explain the issue / errors you have?


State class total_increasing, but its state is not strictly increasing

Got the following warning in Home Assistant log:
Entity sensor.rain_rate_2 from integration ecowitt has state class total_increasing, but its state is not strictly increasing. Please report it to the custom component author.
Logger: homeassistant.components.sensor.recorder
Source: components/sensor/recorder.py:309
Integration: Sensor (documentation, issues)
First occurred: November 21, 2021, 7:05:10 PM (1 occurrences)
Last logged: November 21, 2021, 7:05:10 PM

Entity sensor.rain_rate_2 from integration ecowitt has state class total_increasing, but its state is not strictly increasing. Please report it to the custom component author.

huh.. thats.. odd.. I need to dig into this again.  in AZ I never get rain..

No worries, in NZ and its Spring, lots of opportunity for rain.
If you do a potential fix, happy to test and report back.

Can I ask, which rain rate is that?  Is that the current rate? Not any of the monthly/weekly/daily phizz?  If so, yeah, I think the fix is to set that one to measurement.

Yer its the current rate, just a 2nd one as measured in mm here.

As far as I can tell on the graph, it was still raining, but it looks like the rain rate decreased for a time.

Yep, my bad, forgot that one should be measurement.  Will fix when I have a sec.  Thx!

Yep, my bad, forgot that one should be measurement. Will fix when I have a sec. Thx!

Any luck on getting this one fixed? The log entry is super annoying every time it rains.


Post-monorepo commentary: CI builds should be matrix builds

After the monorepo drops, the CI yaml should generate a matrix build at least across [operating systems, node versions].
I am happy to do the labor.  This should not block the current PR.

Nod.  Windows is probably most important to add, but I'm afraid the parts of the system that are most OS sensitive are in the build and release pipeline, which will be hard to reach.

I already did it for my now-dead fork.  It'll be really hard in mocha, but I'm in the middle of advocating for jest, which I'm willing to do the labor for, and under that context it's actually not too bad


Carousels example

Link to the Page
https://www.skeleton.dev/elements/scroll-containers
Describe the Issue (screenshots encouraged!)
This code:
function carouselLeft(): void {
	const x =
		elemCarousel.scrollLeft === 0
			? elemCarousel.clientWidth * elemCarousel.childElementCount // loop
			: elemCarousel.scrollLeft - elemCarousel.clientWidth; // step left
	elemCarousel.scroll(x, 0);
}

with this code:
<div bind:this={elemCarousel} …

when together, will try to scroll x to (the width of the entire carousel * the number of elements).
I cannot reliably confirm that the code does not work because the example does not seem to be scrolling at all in my browser (Librewolf), but this code did not work in my own website (the left button would always switch between the left and the right with no in-between).
I think elemCarousel is supposed to be an item in the Carousel, since this should fix the formula (it did in my own website, but with an other layout).
I have not checked the other scroll container examples in detail because I had to change both the formulas and the layout in order to have the expected behaviour on my own website.

I just checked the existing issues, my problem may just be a duplicate of #2731

@yacinecheikh in #2731 the issue is the image source we were using has stopped working. Those images need to be replaced. However the carousel should be fully functional with working images, similar to our other example:
https://www.skeleton.dev/elements/scroll-containers#multicolumn
I've never heard of Librewolf, but checking their site it seems to be based on Firefox. It should render and operate the same as Firefox does, and we have done extensive cross browser testing on this feature.
The team and I have [shifted our focus ) to Skeleton v3](https://github.com/skeletonlabs/skeleton/discussions/2729, so I'm going to do two things - close this issue as a duplicate, ask that you consider sending a PR to resolve the images as we don't have the bandwidth right now.
I will call this out to the team though as it should be an easy fix. Maybe one of them will have a chance to jump on it soon.


[ic-top-navigation] navigation items with target blank icons move when focused on small devices

Summary of the bug
When target is "_blank" for navigation items and the external link icon is shown in the side menu on top nav small devices, the icon moves when the navigation item is focused on.
🪜 How to reproduce
Tell us the steps to reproduce the problem:

Go to top navigation - with navigation story
Make screen size small enough that the side menu shows
Move focus throughout the menu
See every time you focus the item with external link, the icon moves.

📸 Screenshots or code
https://github.com/mi6/ic-ui-kit/assets/111882034/9304f5d2-866c-4d5a-ad94-703323cb3be0
🖥 📱 Device

Type: Mobile simulation in dev tools
Device: MacBook
Browser version: Chrome

🧐 Expected behaviour
The icon should stay in the same place no matter if it is focused or not.

Tested this out on develop branch's storybook today.
This is no longer an issue, possibly thanks to this recent change (https://github.com/mi6/ic-ui-kit/pull/1306) that removed right padding on focus.
https://github.com/mi6/ic-ui-kit/assets/111292477/c6f5992c-b54d-46c1-a85b-d3d8187dc61f


ci: new Jenkins pipeline build pipeline and related changes

WIP. Do not merge.
Changes required to enable the Jenkins pipeline.

[x] (Unrelated) Remove edgexfoundry-holding references. This was causing compile errors
[x] Remove VERSION file in favor of git-semver
[x] Add VERSION file to .gitignore
[x] Add Dockerfile.build to provide build container image where code is tested and compiled
[x] Add new make target to build all artifacts and create tar files

Signed-off-by: Ernesto Ojeda<EMAIL_ADDRESS>

recheck

I will wait for @difince PR for to remove the holding references before I merge this PR.

What do you think about having docker build functionality inside the make file ?
In Dockerfile I do not see a way to execute cli command ...  am i wrong

LGTM


ci: bump NUnit from 4.1.0 to 4.2.0

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

Project coverage is 73.30%. Comparing base (7b1586c) to head (57b3163).

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #1099   +/-   ##
=======================================
  Coverage   73.30%   73.30%
=======================================
  Files         293      293
  Lines        3679     3679
  Branches      632      632
=======================================
  Hits         2697     2697
  Misses        812      812
  Partials      170      170

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


Backend for files API

 Create Files table, migrations and corresponding form for accepting files

 Realise CRUD operations for files/folders and uploading of files

 Add SafeDelete option for files

 Create ShareLink table and migrations

 Add API endpoint with creation of share links for files with certain time expiry


Search bar (on translation keys) + keyboard shortcuts

Added a search bar on the toolbar to search among the translation keys present in the page. (This saves time when searching for a particular translation in a large list.
Added keyboard shortcuts for this search bar to navigate between items matching the search. As well as keyboard shortcuts section in the settings page

Added toolbar search bar and keyboard shortcuts.
(first image : search bar preview, second image : list keyboard shortcuts)


Add support for transactions to attach method of belongsToMany relationships

Hello, I would like to include the call to attach in a transaction, but it seems that this feature isn't implemented right now. The attach method in Lucid/Relations/BelongsToMany.js doesn't support a trx parameter like the create and save methods for example.
When I try to run the seeder, the second part with attach fails because of a foreign key constraint violation, with these details: Key (user_id)=(1) is not present in table "users", so it seems that at the moment of invocation the User record isn't in the db.
Is there an alternative way to do it?
Here is the code I would like to write. Please correct me if I am missing something or doing something the wrong way. Thank you!
class UserSeeder {
  async run () {
    const Database = use('Database')
    const User = use('App/Models/User')
    const Group = use('App/Models/Group')
    const trx = await Database.beginTransaction()

    let superusersGroup = null

    try {
      superusersGroup = await Group.findByOrFail('type', 'superuser')
    }
    catch (e) {
      console.log('Transaction error 1:', e)
      trx.rollback()
    }

    let adminUser = new User()
    adminUser.email =<EMAIL_ADDRESS>    adminUser.password = 'password'
    adminUser.first_name = 'Admin'
    adminUser.last_name = 'Admin'

    try {
      await adminUser.save(trx)
    }
    catch (e) {
      console.log('Transaction error 2:', e)
      trx.rollback()
    }

    try {
      await adminUser.groups().attach([superusersGroup.id], trx) // here the problem
    }
    catch (e) {
      console.log('Transaction error 3:', e)
      trx.rollback()
    }

    trx.commit()
  }
}

Yes, seems like to be unsupported right now. Would you mind creating a PR for same with couple of tests?

I'm sorry, but right now I don't have the necessary level of expertise with AdonisJS and it's internals and I don't know how to properly add the transaction support to the code related to BelongsToMany relationships, which seem to be more complex at low-level.
Regarding my problem, I temporarily moved the line with attach after trx.commit() and it works, even if it doesn't seem to be the optimal solution. Let's hope that someone will add that functionality in the future.
Thank you!

No issues, I'll add it

Has it been resolved?

Yes, done in referenced commit

@thetutlage how to use transaction in attach with attributes extras ?

I got:
await curso.disciplinas().attach(disciplinas, (row) => {
let current = row.disciplina_id;
row.disciplina_id = current.disciplina_id,
row.num_total_hrs = current.num_total_hrs,
row.obrigatorio = current.obrigatorio
}, transaction);

Yes, done in referenced commit

How do we get the updated lucid library as it depends on the<EMAIL_ADDRESS>in<EMAIL_ADDRESS>belongsToMany doesn't have transaction support except for attach thank you

Hello, I'm trying to attach roles to a user by using transactions and my code always goes in timeout. Could someone hint me the correct way to do it?
My code:
 const trx = await Database.beginTransaction()
        try {
            await user.save(trx)

            await user.roles().attach(roles, trx)

            await trx.commit()
        } catch(e) {
            await trx.rollback()
        }
        ```


implement the srai instruction

In order to activate the memcmp tests, srai needs to be implemented. It's implemented in powdr assembly, and not as a powdr instruction. Still in draft, as it needs more testing, but I am sharing it to ensure that this is the favored approach.

Are you sure that is the correct implementation? As far as I can tell, it only keeps the sign bit and does not shift it in if it's there.
Would you want to try to implement a new opcode for the binary machine? I don't think it's too complicated and should be much cheaper.

Are you sure that is the correct implementation? As far as I can tell, it only keeps the sign bit and does not shift it in if it's there.

I followed the spec:

SRAI is an arithmetic right shift (the original sign bit is copied into the vacated upper bits).

But as said in the intro comment, it's not completely tested yet: I just wanted to confirm this was the right approach. Which brings it to the next question:

Would you want to try to implement a new opcode for the binary machine? I don't think it's too complicated and should be much cheaper.

Yes, I would really want to! I will need a bit more time to get acquainted with that part of the codebase, though.

Are you sure that is the correct implementation? As far as I can tell, it only keeps the sign bit and does not shift it in if it's there.

I followed the spec:

SRAI is an arithmetic right shift (the original sign bit is copied into the vacated upper bits).

But as said in the intro comment, it's not completely tested yet: I just wanted to confirm this was the right approach. Which brings it to the next question:

Would you want to try to implement a new opcode for the binary machine? I don't think it's too complicated and should be much cheaper.

Yes, I would really want to! I will need a bit more time to get acquainted with that part of the codebase, though.


Feature/transfer and vesting function cli

:tada: This issue has been resolved in version 0.25.0-development.1 :tada:
The release is available on:

npm package (@development dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This issue has been resolved in version 0.25.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Update README.md

Updated grammar, spelling, order of content for readability, in preparation for Josh Ekandem's upcoming DXA studies.

I understand. I don't have a problem with this.

@ddeuerme thanks for your contribution!


Build failure: pkgsCross.mingwW64.pkgsStatic.stdenv

Steps To Reproduce
Steps to reproduce the behavior:

build pkgsCross.mingwW64.pkgsStatic.stdenv

Build log
error: builder for '/nix/store/v1ycfkiivjszsl8qagsw2v86r81amwxs-mingw-w64-static-x86_64-w64-windows-gnu-10.0.0-headers.drv' failed with exit code 1;
       last 10 log lines:
       > checking for x86_64-w64-windows-gnu-strip... no
       > checking for strip... no
       > checking for a race-free mkdir -p... /nix/store/khndnv11g1rmzhzymm1s5dw7l2ld45bc-coreutils-9.4/bin/mkdir -p
       > checking for gawk... gawk
       > checking whether make sets $(MAKE)... yes
       > checking whether make supports nested variables... yes
       > checking whether to enable maintainer-specific portions of Makefiles... no
       > checking build system type... x86_64-unknown-linux-gnu
       > checking host system type... Invalid configuration 'x86_64-w64-windows-gnu': Kernel 'windows' not known to work with OS 'gnu'.
       > configure: error: /nix/store/9vafkkic27k7m4934fpawl6yip3a6k4h-bash-5.2-p21/bin/bash ./build-aux/config.sub x86_64-w64-windows-gnu failed

Metadata
Please run nix-shell -p nix-info --run "nix-info -m" and paste the result.
[user@system:~]$ nix-shell -p nix-info --run "nix-info -m"
 - system: `"x86_64-linux"`
 - host os: `Linux 6.6.10-zen1, NixOS, 24.05 (Uakari), 24.05.20240115.c3e128f`
 - multi-user?: `yes`
 - sandbox: `yes`
 - version: `nix-env (Nix) 2.18.1`
 - channels(root): `"nixos"`
 - channels(user): `"nixgl, nixpkgs"`
 - nixpkgs: `/nix/store/11zbgb8j7wnnccbbjcq0q556h28g7p4r-source`

Add a :+1: reaction to issues you find important.

pkgsCross.mingwW64.pkgsStatic.stdenv.targetPlatform.config is "x86_64-w64-windows-gnu" for some reason, unlike pkgsCross.mingwW64.stdenv.targetPlatform.config which is "x86_64-w64-mingw32" as expected.

https://github.com/NixOS/nixpkgs/blob/2fba629f59f3de8cf773ad5fcac782e62a934faa/pkgs/top-level/stage.nix#L265-L278
The Windows case doesn't seem to be covered here. I suppose the following should be added to crossSystem conditionally.
https://github.com/NixOS/nixpkgs/blob/cefcf19e1c6d4255b2aede5535d04064f6917e9b/lib/systems/examples.nix#L311-L316

Bump, this issue is quite unfortunate when attempting to build static apps through nix.

I was able to build a static windows (mingwW64) executable with 34cefd7dea46e02932c2413ae7068574d0352ce9. I think this closes the issue? Thanks @wolfgangwalther! :heart:

Hi, is there any possible work around for this?

Hi, is there any possible work around for this? (just facing this now after upgrading from 22.11 to 24.05)

The work-around is to "properly" instantiate cross compilation.
Compare the following on nixos-24.05 at dc2e0028d274394f73653c7c90cc63edbb696be1.
❯ nix-build <nixpkgs> -A pkgsCross.mingwW64.pkgsStatic.stdenv
[..]
checking host system type... Invalid configuration 'x86_64-w64-windows-gnu': Kernel 'windows' not known to work with OS 'gnu'.
configure: error: /nix/store/516kai7nl5dxr792c0nzq0jp8m4zvxpi-bash-5.2p32/bin/bash ./build-aux/config.sub x86_64-w64-windows-gnu failed
error: builder for '/nix/store/j8yx9qfk3yyfq2p5w7k0lmg2xkbypfkr-mingw_w64-headers-static-11.0.1.drv' failed with exit code 1;

vs
❯ nix-build --expr '(import ./. { crossSystem = { config = "x86_64-w64-mingw32"; isStatic = true; }; }).stdenv'
/nix/store/m77b2dla2w3k8cx4ggjdmm2j8nldy6j6-stdenv-lin

What is the difference between
pkgsCross.mingwW64.pkgsStatic.stdenv.targetPlatform.config
and
pkgsStatic.pkgsCross.mingwW64.stdenv.targetPlatform.config
?
It seems the later does yield x86_64-w64-mingw32

I see, that makes sense.
Interestingly pkgsStatic.pkgsCross.mingwW64.pkgsStatic.stdenv.targetPlatform.config does yield x86_64-w64-mingw32.


ssl certificate has expired

Found a twit about is, will leave open so other people don't re-create it:
https://twitter.com/pydanny/status/574005015188226048

Found a twit about is, will leave open so other people don't re-create it.

Thanks!

We've been trying to resolve it since Friday:
https://twitter.com/pydanny/status/575056311479574528
https://twitter.com/pydanny/status/575055875842424833

Resolved and documented in c4ea735bde9f1c390953e823e43c1a20e48ec0a9.


[vite] RollupError: Duplicate export 'default'

const test = [
    { test: 123, add: 123 },
    { test: 123, add: 123 },
    { test: 123, add: 123 },
    { test: 123, add: 123 },
  ]

  test.forEach((module, index) => {
    console.log('🚀 ~ test.forEach ~ module:', module)
    if (index == 1) {
      module.test = 123
    }
  })

The above code example will have a packaging exception
Abnormal information：
ERROR  Duplicate export 'default' (Note that you need plugins to import files that are not JavaScript)                                                                            11:31:29
204: const CJS__export_default = (module.exports == null ? {} : module.exports).default || module.exports;
205: export {
206:   CJS__export_default as default,
^
207: }
208: /* [vite-plugin-commonjs] export-statement-E */

Were you able to find a workaround for this issue?

Can you provide a minimal reproduction repo?

Were you able to find a workaround for this issue?

It looks like module is treated as CommonJS's module. You can try replacing module with module1 or something.
const test = [
    { test: 123, add: 123 },
    { test: 123, add: 123 },
    { test: 123, add: 123 },
    { test: 123, add: 123 },
  ]

-  test.forEach((module, index) => {
+  test.forEach((module1, index) => {
    console.log('🚀 ~ test.forEach ~ module:', module)
    if (index == 1) {
      module.test = 123
    }
  })

It looks like module is treated as CommonJS's module. You can try replacing module with module1 or something.看起来module被视为 CommonJS 的module 。你可以尝试用module1或其他东西替换module 。
const test = [
    { test: 123, add: 123 },
    { test: 123, add: 123 },
    { test: 123, add: 123 },
    { test: 123, add: 123 },
  ]

-  test.forEach((module, index) => {
+  test.forEach((module1, index) => {
    console.log('🚀 ~ test.forEach ~ module:', module)
    if (index == 1) {
      module.test = 123
    }
  })

This example was written by a business developer. It is necessary to notify all developers to pay attention to this problem, which is too much of a burden. Can this problem be fundamentally fixed in the plug-in?


Wheel installation in container does not use proxy for git dependencies.

Bug Description
Pip's --proxy argument does not pass the proxy to Git (functionality described here), so the wheel installation will fail to clone a Git dependency even if http-proxy is set.
To Reproduce

Define python sub dependency specified with Git (e.g. django-rest-generator = { git = "https://github.com/canonical/django-rest-generator.git" } in pyproject.toml)
Set http-proxy, https-proxy, no-proxy  in configuration file as needed.
Pip installation of wheel dependencies fails.

Environment
latest/stable on a machine that requires an HTTP proxy.
Relevant log output
unit-temporal-worker-k8s-0: 19:25:32 ERROR unit.temporal-worker-k8s/0.juju-log Uncaught exception while in charm code:
Traceback (most recent call last):
  File "/var/lib/juju/agents/unit-temporal-worker-k8s-0/charm/./src/charm.py", line 516, in <module>
    main.main(TemporalWorkerK8SOperatorCharm)
  File "/var/lib/juju/agents/unit-temporal-worker-k8s-0/charm/venv/ops/main.py", line 456, in main
    _emit_charm_event(charm, dispatcher.event_name)
  File "/var/lib/juju/agents/unit-temporal-worker-k8s-0/charm/venv/ops/main.py", line 144, in _emit_charm_event
    event_to_emit.emit(*args, **kwargs)
  File "/var/lib/juju/agents/unit-temporal-worker-k8s-0/charm/venv/ops/framework.py", line 351, in emit
    framework._emit(event)
  File "/var/lib/juju/agents/unit-temporal-worker-k8s-0/charm/venv/ops/framework.py", line 853, in _emit
    self._reemit(event_path)
  File "/var/lib/juju/agents/unit-temporal-worker-k8s-0/charm/venv/ops/framework.py", line 943, in _reemit
    custom_handler(event)
  File "/var/lib/juju/agents/unit-temporal-worker-k8s-0/charm/src/log.py", line 41, in decorated
    return method(self, event)
  File "/var/lib/juju/agents/unit-temporal-worker-k8s-0/charm/./src/charm.py", line 98, in _on_config_changed
    self._update(event)
  File "/var/lib/juju/agents/unit-temporal-worker-k8s-0/charm/./src/charm.py", line 297, in _update
    self._validate(event)
  File "/var/lib/juju/agents/unit-temporal-worker-k8s-0/charm/./src/charm.py", line 269, in _validate
    self._process_wheel_file(event)
  File "/var/lib/juju/agents/unit-temporal-worker-k8s-0/charm/./src/charm.py", line 223, in _process_wheel_file
    _install_wheel_file(
  File "/var/lib/juju/agents/unit-temporal-worker-k8s-0/charm/./src/charm.py", line 448, in _install_wheel_file
    _, error = container.exec(command).wait_output()
  File "/var/lib/juju/agents/unit-temporal-worker-k8s-0/charm/venv/ops/pebble.py", line 1540, in wait_output
    raise ExecError[AnyStr](self._command, exit_code, out_value, err_value)
ops.pebble.ExecError: non-zero exit code 1 executing ['pip', 'install', '--proxy=http://XXXXXXX:3128', '/user_provided/sqa_artifact_scheduler-1.0.0-py3-none-any.whl'], stdout="Processing /user_provided/sqa_artifact_scheduler-1.0.0-py3-none-any.whl\nCollecting django-rest-generator@ git+https://github.com/canonical/django-rest-generator.git\n  Cloning https://github.com/canonical/django-rest-generator.git to /tmp/pip-install-vkedz15c/django-rest-generator_3409f8a2bac24923889287b415afcc27\n  Resolved https://github.com/canonical/django-rest-generator.git to commit cda0d661f9a473625fc39556f34ee317c6af7650\n  Installing build dependencies: started\n  Installing build dependencies: still running...\n  Installing build dependencies: still running...\n  Installing build dependencies: still running...\n  Installing build dependencies: still running...\n  Installing build dependencies: still running...\n  Installing build dependencies: still running...\n  Installing build dependencies: finished with status 'error'\n", stderr="  Running command git clone --filter=blob:none --quiet https://github.com/canonical/django-rest-generator.git /tmp/pip-install-vkedz15c/django-rest-generator_3409f8a2bac24923889287b415afcc27\n  error: subprocess-exited-with-error\n  \n  × pip subprocess to install build dependencies did not run successfully.\n  │ exit code: 1\n  ╰─> [7 lines of output]\n      WARNING: Retrying (Retry(total=4, connect=None, read=None, redirect=None, status=None)) after connection broken by 'NewConnectionError('<pip._vendor.urllib3.connection.HTTPSConnection object at 0x7ffbcdab1340>: Failed to establish a new connection: [Errno 101] Network is unreachable')': /simple/setuptools/\n      WARNING: Retrying (Retry(total=3, connect=None, read=None, redirect=None, status=None)) after connection broken by 'NewConnectionError('<pip._vendor.urllib3.connection.HTTPSConnection object at 0x7ffbcdab16d0>: Failed to establish a new connection: [Errno 101] Network is unreachable')': /simple/setuptools/\n      WARNING: Retrying (Retry(total=2, connec" [truncated]
unit-temporal-worker-k8s-0: 19:25:33 ERROR juju.worker.uniter.operation hook "config-changed" (via hook dispatching script: dispatch) failed: exit status 1

Additional context
Setting HTTP_PROXY, HTTPS_PROXY, and NO_PROXY in the environment for the install in _install_wheel_file should resolve this.

@rpbritton This PR is supposed to make the worker charm accept rocks instead of wheels, and the proxy won't be an issue, since the rock can be built locally.

Sounds good, I will mark this closed


Best practice on how to use in Amplify Console build process

Hi there,
Thanks a lot for this. This really should be part of Amplify core, but until then, this plugin has worked very well for us for about a month.
The biggest issue for us was figuring out how we install this package in the build process without installing our entire package.json which includes all our frontend packages.
We did a --no-save in the preBuild process and that worked without issues for a month or so, then just suddenly out of the blue it failed today.
How are you doing this? What's the cleanest way to do this where we are not spending build time on installing more than needed while still getting this package installed? If you have the golden solution here, then I would thank you by adding it to the README as a PR for this repository so others may have an easier time getting it set up. At the same time I may also add a bit of a Q&A that explains how DynamoDB reacts and handles this stuff.

Hi @houmark
Thanks for your request.
About the first part, I personally really just install it in the package.json as explained in the README. Therefore I don't have a solution ready for this. But once you or somebody else finds a solution I'd love to include it in the docs of this directive. I'll therefore leave this issue open for now.
About the seconds part how this directive works behind the scenes, I've now linked the AWS docs about the DeletionPolicy in the README. Hope this helps 🙂


[BUG] image clone unusable

Describe the bug
can not clone a image
To Reproduce

web ui, select an image, choose clone
jumps to image create page
change namespace/name
we have to re-upload the same image file again.

this is not clone but a pure create new
Expected behavior
clone the old image without url-download/local-upload
Environment:

Harvester ISO version:  v1.0.1

Currently (1.0.3),  Clone only means clone yaml in Harvester


Wait for registration callback before running commands

Fixes a race condition where CLI commands would not be registered by the time the CLI attempts to execute them.

Works for me. Merging.


Recursive clone in Dockerfiles, use build target for tofnd

Also, a sentence or two in the PR description saying why the changes are needed. It's not obvious to me what recursive clone is solving.

Also, a sentence or two in the PR description saying why the changes are needed. It's not obvious to me what recursive clone is solving.

For sure. This was a quick fix done over the weekend that @danbryan and I had chatted through, but will add a description.


Thumb layers stuck after moving the upperThumbLayer to be same as lowerThumbLayer

Set min = lower = 0, max = upper = 100. Move upper to 0, the thumb layers now stuck on 0 position.

LINE 193 need to change (instead of checking from lower thumb, there should be a var to keep what's the last highlighted thumb)

Fixed, coming in the next version (0.5.1)


Migrate examples from rxros repository (and other suggestions)

As per subject.
This PR suggests a new repository layout, in which all examples are moved to the rxros_examples repository (rosin-project/rxros_examples#1), rxros is the only package in this repository and a new dependency is added: rxcpp_vendor (which packages in the RxCpp dependency).
Some other changes:

further streamlining of build scripts and package manifests
exploit (transitive) dependency declarations more (avoid restating primary dependencies in multiple places)
update readme with all these changes

To test this new setup, do the following:
source /opt/ros/$ROS_DISTRO/setup.bash
rosdep update
mkdir -p $HOME/rxros_refactor_ws
cd $HOME/rxros_refactor_ws
wstool init src https://raw.githubusercontent.com/gavanderhoorn/rxros_examples/refactor/rxros_examples.rosinstall
rosdep install --from-paths ~/rxros_ws/src --ignore-src
catkin_make  # or if you prefer: catkin build
source devel/setup.bash

This should build rxcpp_vendor, rxros, the BrickPi and the teleop packages/examples.
After sourceing the workspace you should be able to run all of the examples.
Note: to initialise a workspace with just rxros (so none of the examples), use this .rosinstall file instead of the one shown in the listing above.

If/when we agree to merge this, I can add CI (based on Travis CI) and setup some (regression) testing if that would be desirable.

@henrik7264: I've left the tf dependency in rxros (so no rxros_tf yet), but at least made it explicit in 8e883cb8.
rosdep should now install it on any system that doesn't already have it installed (there probably aren't many, but this way we can be sure).

I'll look at this tomorrow evening (will try to install and test drive).

Testing will be desirable :), I was planning to write some tests, when I have time.  So a setup for getting them to run will be needed.

Testing will be desirable :), I was planning to write some tests, when I have time. So a setup for getting them to run will be needed.

Just having a will-it-compile test is already very valuable in my experience.

I have managed to run your commands and build successfully in a clean container with ros melodic. There are some very minor problems with your instructions above, but this does not matter much (they are only for use in this PR).
I have also read through all the commits. I also have some trouble understanding the bottom one (about installation of include files), but this is simply caused by lack of background.  It does look reasonable.
I noticed that you did not split away the tf stuff, and I think this is the right thing to do.  We should do this in a separate PR.  Otherwise it is too hard to discuss and too hard to understand what is going on.
I suggest that we merge this (after @henrik7264 gives as a second opinion).

@wasowski wrote:

There are some very minor problems with your instructions above, but this does not matter much (they are only for use in this PR).

could you describe those problems? They may be important to fix before attempting to release the package.

I noticed that you did not split away the tf stuff, and I think this is the right thing to do. We should do this in a separate PR. Otherwise it is too hard to discuss and too hard to understand what is going on.

Yes, I didn't want to conflate the different issues.
This PR is about restructuring the repository and splitting of the examples. Nothing more.

Worked fine on my machine (ros-melodic-desktop-full). Installation as described above worked fine and the catkin_build was sucessfull. Ran a "rospack list" to verify that the packages were available - all OK.

@gavanderhoorn of course, I wen underground for a month, and no longer remember what the issues were.  You probably already fixed what needed to be fixed.  I consider this case to be closed :)

@wasowski: yes, I believe we've covered everything here.


Undo is broken in master (canvas doesn't redraw properly)

@MandaBrown I think this was caused by your commit 32e89182d10bb4fffe8fadc5d76563911641d8bf. Could you explain why you made the change?

Fixed by reverting 32e8918.

Ugh, it made sense to me at the time. I am very sorry. :(

It's OK, you made the change in a small commit so it was really easy to revert.

The canvas rendering code is pretty obtuse so I'm not surprised that the "correct-looking" version isn't actually correct.


Tests: treat Windows as Linux

Treat Windows similarly to Linux as the functionality is near similar in completeness.  While it is possible to support the DirectoryMonitor on Windows, it is not yet implemented in DocC, so simply treat it as we do Linux.

@swift-ci please test


"commit retry 100" seems to always cause repeated execution

The "retry" operation in SQL batch mode is causing repeated statement execution even though the statements in the batch worked the first time.  The following example in python uses commit retry 100 and results in the statements executing 101 times:
import requests

url='http://<IP_ADDRESS>:2480/batch/mydb'
user = 'admin'
pswd = 'admin'

data = """{
    "transaction" : false,
    "operations" : [
    {
    "type" : "script",
    "language" : "sql",
    "script" : [ "begin;",
    "let a = create vertex set script = true;",
    "let b = select from v limit 1;",
    "let e = create edge from $a to $b;",
    "commit retry 100;" ]
    }
    ]
    }"""

r = requests.post(url, data=data, auth=(user,pswd))

I would only expect the above code to insert one vector and one edge, but looking at my database I see 101 additional vectors and 101 additional edges.

Already fixed in 2.0.5-SNAPSHOT

As workaround use the RETURN statement at the end.

ok, thanks!  In the mean time I'll try out the workaround.


Add support for Deferred object

See http://api.jquery.com/category/deferred-object/ :)

finally in july 13, 2015, jquery promises are following the standard http://blog.jquery.com/2015/07/13/jquery-3-0-and-jquery-compat-3-0-alpha-versions-released/
lol

with upcoming ES6 Promise object I think we should move on native adoption.

Yeah, sure I agree! :)
El 26 mar. 2016 14:21, "Denis Ciccale"<EMAIL_ADDRESS>escribió:

with upcoming ES6 Promise object I think we should move on native adoption.
—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub
https://github.com/dciccale/kimbo.js/issues/6#issuecomment-201821887


Change log into zap log by Uber-go

We have test many go logs and find that Zap get the best performance in all log lib.
With zap log, the access log can be staged with a very small cost.
Bad thing is Zap should be a dependency for shadowsocks-go.
Whats your opinion.

@lixin9311  I can help this with a PR if necessary

I'm planning to reconstruct the whole project, and rewrite the client program.
So I'm afraid we do not have any plan to introduce new features and improvement to the current version.
Anyway, it's a good suggestion, I will try it in my new version.
And I'll keep this open.

Awesome. Is there any schedule for this milestone? I'd like to make some PR

Unfortunately, we do not have a schedule. I work on this project only as a side work.
Currently, it is hard to use the code in other projects, and so is the server/client program.
As a result, it's hard to make improvements for server/client.
I'm planning to reconstruct the shadowsocks package, make it more like a library, friendly to be used in other projects.
If you have any idea and suggestion, welcome to open an issue and share it.

I will keep watching on it. Thank you


WIP Getting started guide

Motivation
Add getting started guide for the JS SDK.
https://issues.jboss.org/browse/AGCORDOVA-200
Progress

[x] Getting Started Guide
[x] Core module skeleton
[x] Instructions to add mobile-services.json
[ ] Core module API for Logging?
[ ] Core module API for Networking?
[ ] Core module API for Metrics

@josemigallas @wtrocki I added some stubs for a networking and logging APIs from core, but I'm not sure if they're going to be there. I imagine at least logging should be, not sure if we'll do networking for the JS sdk.

ping @ciaranRoche

I imagine at least logging should be, not sure if we'll do networking for the JS sdk.

I have no strong opinions about it. Considering how many options they are and what other libraries we going to reuse I think it will be hard to do networking.
If we use keycloak adapter library for example it comes with their own networking and logging.

I don't know how useful would be a networking module and for the logger, I think it would just be a wrapper around console.log. I might be wrong on this though.

@wtrocki sure, thanks I'll leave the empty headings for other modules then, even though they might not exist