Wiki page with useful user settings snippets

Shouldn't we just build them into phy? We should do this too, but... we should just build them and document

it depends... some highly-specific use-cases would be better in the wiki. phy does not intend to implement everything, the goal is to encourage user customization. but no problem to put in phy stuff used by 90% of users


[Feature]: make a admin user

Is your feature request related to a problem? Please describe.
No response
Describe the solution you'd like
make a user
this user should be able to see delete icons on all videos
this user should be able to delete all videos
Describe alternatives you've considered
No response
Additional context
No response

I want to work on this under JWOC

I want to work for it under JWOC

@mecivil assigned

I won't be able to do it within stipulated tine.Sorry for that.Please assign someone else.

I would like to work on this issue under JWOC

@Priyamakeshwari assigned !

@mnnkhndlwl If there is no PR raised in the past 8days, I would like to contribute to it under JWOC

@Priyamakeshwari are you still working on this issue??

@sarkartanmay393 assigning you this issue


Program crashes when linear color scheme settings are changed too quickly

This is caused by threading

Fixed with new render system


CLOUDP-279932: SDK based authentication

Description
Integration with Credentials module in Atlas CLI
WIP -  Intention is to provide demo for authentication capability.
In PR I have flagged number of areas that will need to be done for proper integration.
PR will not be merged, but it can be used as base for  future Auth Integration
Testing

Create profile /bin/atlas config edit --profile auth-test --debug

[auth-test]
output = 'json'
ops_manager_url = 'https://cloud-dev.mongodb.com'
org_id = '6707a96bc2b066602a4dfdcc'
project_id = '670ce177f33cea212ea202a5'
public_api_key = 'your sa id'
private_api_key = 'your sa secret'

or setup profile using cli
/bin/atlas config init --profile auth-test
? Service Account Client ID: ****************
? Service Account Secret: [? for help] ************************
😘

Run API call (command)

./bin/atlas clusters list --profile auth-test --debug

Result:
{"links":[{"href":"https://cloud-dev.mongodb.com/api/atlas/v2/groups/670ce177f33cea212ea202a5/clusters?includeCount=true&includeDeletedWithRetainedBackups=false&pageNum=1&itemsPerPage=100","rel":"self"}],"results":[],"totalCount":0}
{
  "links": [
    {
      "href": "https://cloud-dev.mongodb.com/api/atlas/v2/groups/670ce177f33cea212ea202a5/clusters?includeCount=true\u0026includeDeletedWithRetainedBackups=false\u0026pageNum=1\u0026itemsPerPage=100",
      "rel": "self"
    }
  ],
  "results": [],
  "totalCount": 0
}

@wtrocki good to close this PoC?


cachedEventHandler() needs at least 2 calls after it is invalid

Environment
Nuxt: 3.8.2
H3: 1.9.0
nitropack: 2.8.0
Server: Vercel
Storage: Vercel KV (Redis)
Reproduction
server/api/tester.ts
export default cachedEventHandler(
  async (event): Promise<any> => {
    return Date.now();
  },
  {
    maxAge: 5, // seconds
  },
);

nuxt.config.ts
export default defineNuxtConfig({
  devtools: { enabled: true },
  nitro: {
    storage: {
      cache: {
        driver: 'vercelKV',
      },
    },
  },
});

Describe the bug
Using cachedEventHandler() with Vercel KV (Redis) requires at least 2 calls after the cache is invalid until the function runs again:

GET request -> Function runs + is cached
GET request -> Returns cached response
Wait until maxAge is expired
GET request -> Returns cached response (should run the function instead)
GET request -> Function runs + is cached

Additional context
In development Nitro is using the FS driver and I there it seems to work as it should.
Logs
No response

Hi. I made a minimal sandbox to reproduce: https://stackblitz.com/edit/github-avewtb?file=routes%2Findex.ts
It is in fact an expected behavior. By default, we enable Stable-While-Revalidate strategy. The response will be invalidated in the background that's why you immediately get the old one until this time passes. (but notice the log that handler is immediately invoked)
If you wish to get response after handler resolved, you can disable SWR using swr: false

Thanks for the super fast response! Shouldnt swr be disabled by default to prevent unexpected results and confusion? When the cache is invalid, I expect my handler function to run and return the new result immediately. Otherwise the cache seems broken to me. E.g. thinking about a button on a website that says "update" wouldnt return an updated result, isntead it would return the same cached data as before.
I made a minimal reproduction repo:
https://github.com/MickL/nuxt-nitro-cache
Deployed to Vercel using Vercel KV:
https://nuxt-nitro-cache.vercel.app/api/tester
Indeed within development (using FS driver) it reruns the function immediately. Maybe because on dev everything is so fast? This would mean that on dev it is "wrong" while on Vercel it is correct.

PR welcome to clarify the docs 👍🏼 Benefits of SWR behavior for non-blocking responses was important enough that we initially decided on this default. We can discuss later to change it for next major versions of nitro if enough merits.
Yep maybe dev experience is fast enough so you haven't notice issue :p
With disabled swr do you still have issues with caching behavior on vercel?

Unrelated: Since saw date-fns in your example, consider it has a poor bundling result (for worker targets) (https://github.com/unjs/nitro/issues/1889)

I would highly suggest swr default set to false as this creates unexpected behavior: The cache is invalid but still returned.
Updated the docs to make this more clear: https://github.com/unjs/nitro/pull/1949

Lets move default discussion to https://github.com/unjs/nitro/issues/1950
Thanks for docs PR.
Do we need to keep this issue still open?


The image search API returns one less image per page given the pagesize

Describe the bug
The image search view returns n-1 images when the query parameters include pagesize=n. This has been tested at
https://api-dev.creativecommons.engineering/image/search/?q=bird&pagesize={n}

Expected behavior
For pagesize=n, n images should be returned.

I've also noticed this weird behavior though it's not consistent.
Sometimes in returns the exact pagesize as requested and sometimes it returns n-1 pages as you say.

I tried to examine the view that performs the slicing and the code written there seems perfectly alright!
start_slice = page_size * (page - 1)
end_slice = page_size * page
if start_slice + end_slice > ELASTICSEARCH_MAX_RESULT_WINDOW:
    raise ValueError("Deep pagination is not allowed.")
s = s[start_slice:end_slice]

It's because we filter out broken links in the results. If you add &filter_dead=False to your query, you'll end up with the expected number of images. See #314.
In addition to having a process for clearing out a lot of the link rot, someone is working on addressing this issue. https://github.com/creativecommons/cccatalog-api/pull/358/


TSVB issue tooltip date format

Hi Team ,
On the OD version [1.12.0] for the TSVB when I put for more than 3 days we are not able to see the date format on the tooltip below is the screenshot

When I increase the Time range for more than 7 days we are seeing the date format on the tooltip as below :

When I keep for 7 days and interval as 10m the tooltip is not working for that time range as well
interval 10m

interval 60m

For the interval 60m is fine but if we reduce the interval the tooltip is not showing
May I know is there any bug is raised for this or is there any changes need to get the tooltip correctly.
Kindly help me with this
Thanks
DILIP B K

Hi team,
Any updates on the above issue ??

Hi team,
May I know this issue will be fixed on the upcoming release ?


vscode + jupyter don't show output

Issue Type: Bug
The color of the output cell turns gray, don't show output .
VS Code version: Code 1.65.1 (8908a9ca0f221f36507231afb39d2d8d1e182702, 2022-03-08T02:06:27.846Z)
OS version: Windows_NT x64 10.0.19043
Restricted Mode: No

System Info

Item
Value

CPUs
11th Gen Intel(R) Core(TM) i7-11700 @ 2.50GHz (16 x 2496)

GPU Status
2d_canvas: enabledgpu_compositing: enabledmultiple_raster_threads: enabled_onoop_rasterization: enabledopengl: enabled_onrasterization: enabledskia_renderer: enabled_onvideo_decode: enabledvulkan: disabled_offwebgl: enabledwebgl2: enabled

Load (avg)
undefined

Memory (System)
31.72GB (26.25GB free)

Process Argv
--crash-reporter-id 47b1a46e-5206-47ab-a88c-b5f0bc099f87

Screen Reader
no

VM
0%

Extensions (11)

Extension
Author (truncated)
Version

notebook
eig
0.0.63

vscode-language-pack-zh-hans
MS-
1.65.2

python
ms-
2022.2.1924087327

vscode-pylance
ms-
2022.3.1

jupyter
ms-
2022.3.1000702358

jupyter-keymap
ms-
1.0.0

jupyter-renderers
ms-
1.0.6

cpptools
ms-
1.8.4

scala
sca
0.5.5

vscode-zipexplorer
sle
0.3.1

tconda
zhp
0.0.5

A/B Experiments
vsliv368cf:30146710
vsreu685:30147344
python383:30185418
vspor879:30202332
vspor708:30202333
vspor363:30204092
vstes627:30244334
pythonvspyl392:30443607
pythontb:30283811
pythonptprofiler:30281270
vshan820:30294714
vstes263:30335439
vscorecescf:30445987
pythondataviewer:30285071
vscod805cf:30301675
pythonvspyt200:30340761
binariesv615:30325510
bridge0708:30335490
bridge0723:30353136
vsaa593:30376534
vsc1dst:30438360
pythonvs932:30410667
wslgetstarted:30449410
vsclayoutctrt:30448491
dsvsc008:30440022
pythonvspyt640:30450904
vsbas813:30436447
vscscmwlcmc:30438804
helix:30440343
vscaat:30438848
pynewfile477:30450038

Is there some recommended workaround, maybe a downgrade to an older version?

The same issue shows on mac M1.

Can anyone share a screen shot of what you saw? A detailed reproduce steps will also be helpful, thanks in advance!

I mistakenly upgraded to 1.65.2 again - same problem, screenshot attached.

I mistakenly upgraded to 1.65.2 again - same problem, screenshot attached.
Edit: The good news is that the bug does not occur in 1.66.2 any more.

The number of my variable output may exceed the limit, resulting in the error of Jupyter. If this variable value is not output, this bug will not occur.


Added support for Tauri in the frontend.

Integrated Tauri with the frontend, React app can now be used on the desktop. We can edit the react app as normal as if nothing changed, just do yarn tauri dev to run it, it'll take some time to build for the first time, but after that it's pretty quick.

Seems pretty good, just this one thing.

Alright, I fixed the issue


improve error messages for network connection failures

This traps networking errors and makes a noble effort to be informative.
Most, if not all, network errors will be due to either network failure or pointing at the wrong URL. This PR tries to catch those that result in hitting the wrong URL.
Server responds 400 BAD REQUEST:
$ bindle --server http://bindle.f1sh.ca:8080/v1 search
Server has encountered an error: The request could not be handled by the server. Verify your Bindle server URL

A networking error occurred during connection (e.g. wrong port, server disconnects abruptly):
$ bindle --server http://bindle.f1sh.ca/v1 search
Server has encountered an error: Protocol error. Verify the Bindle URL

Closes #231
Signed-off-by: Matt Butcher<EMAIL_ADDRESS>

@technosophos Did you need any more feedback here or can we merge?

Merge away. I forgot about this PR


Catch exception in Solution generation

Exception is not handled when file is not found or there is error in creating file. It stops creating all solutions after this unhandled exception with following error:
[07:08:37] Processing logfile64.dll[07:08:37] Could not find a part of the path 'C:\spartacus\logfile64.dll-file-not-found'.
Fix catches exception, so only solution which have error is not built. Building of other solution continues.

Thanks, your fix is now in v2.2.0

Thanks. Great. You're fast. Can I ask you to add label "hacktoberfest-accepted" label to this pull request?
For more info, check out: https://hacktoberfest.com/participation/#pr-mr-details


Odd crash report with lighting updates near the Void

http://pastebin.com/zR3XZvvF - I get this when fiddling with lighting updates around the void in Extra Utilities' Deep Dark dimension.  I got this half a dozen times either picking lava source blocks up or allowing the flowing lava to pour into the void.  I get the crash placing torches as well, at Y=3.
http://pastebin.com/LCuQ3Sc8 - I get this when doing the same thing in the Overworld.  I busted a piece of bedrock and placed a torch down.  It didn't immediately crash but when I busted the torch, crash.
http://pastebin.com/K6bDJMHq - .. and, the Nether.  Just dug straight down in Creative and let the lava flow into the void.
I wasn't sure if this was something fixed in 1.3.4 (I'm still using 1.3.3 because broken sunlight) so please disregard if useless.

i think this isnt revelant any more, caused by the lighting values being larger then 0-15 for the extended data

Yeah, 1.3.3 is still quite unstable, so I'm not completely surprised.  Maybe I can spend some time here today.

Update:  Similar crash for build #29 - http://pastebin.com/wRR3wXqj
Dug straight down, broke bedrock, placed Red colored glowstone near the hole, no crash.  Placed lava, paused a few seconds, then crash.

A screen shot right before crash would be fantastic! (I'll look at this soon)

http://imgur.com/4h5bSsQ - oops, forgot to add this to GitHub.  I tossed it and a whole gallery of pics in the MCF thread if interested.  The bedrock hole is under the flowing lava (source block is to the left).  This pic was taken maybe a second, or less, before crash.

Sounds like an issue with the lava flowing out or near the edge of a world, and then the lighting engine dies on when lava is on the edge.

That was fun!  Same issue happens on lights at the TOP of the world... presumable the far x and z extremes of the world are also unstable.....
but we can ignore those for now :)

http://coloredlightscore.us.to:8080/job/ColoredLightsCore v1.7.10/30/


Support Github Enterprise installations for authentication

With just a little bit of work, you guys should be able to support Github Enterprise installations as well. We need this, or LDAP support, to really make use of Rancher for our development environment.

#502 and rancherio/ui#167

:+1:


Preparing release v1.61.0

Prepare new Jaeger operator release.

@iblancasa Tested this PR on OCP 4.16. https://issues.redhat.com/browse/TRACING-4766 We are good to merge. I'll also check once this merges and runs via our automated CI jobs.


Design: Testing Post-Sapling Validation on Short Chains

Design Goals
We need to work out how to test post-Sapling contextual validation.
Context and Problem Space
Currently, our post-Sapling contextual validation tests can only be run on a state that's synced up to Sapling activation, because the non-finalized state asserts that all blocks it receives are after Sapling activation.
But that makes it really difficult to write tests, because it takes a lot of work (or a lot of infrastructure) to set up a state that's synced up to Sapling activation.
Process
We need to:

define the problem space
create designs that solve the most important problems
decide which designs to implement
implement those designs.

Potential Designs
Some possible designs are:

#1135 - Refactor Network and NetworkUpgrade enums into structs and a trait
Refactor post-Sapling validation to separate:

post-Sapling assertions, which don't need to be tested
post-Sapling checks, which can be independently tested on short chains (or individual blocks)

We might end up implementing a combination of these designs, based on how easy it is to do these refactors for different kinds of validation.

This is covered by other tests.


Add log-level to logging module

Siebe commented:
Originally posted by @SiebeLeDe in https://github.com/TheoChem-VU/TCutility/pull/53#pullrequestreview-1703032147

Added to the package


Update for dockerdriver repo rename (ne voldriver)

Hi Diego Team,
This PR updates inigo to work with the renamed voldriver repo, now called dockerdriver. See our story for more context. In addition to this change, you will also need to bump the following submodules of diego-release:
csiplugin: 67738772ab8a44e1ef597d9513fafa87289da8f9
localdriver: cf93a407cfe5dda6c1b36492f3c8b5293f013540
volman: 12b8148976fc2ef8f49849632989ef342a16a18d
You will also need to replace the old voldriver submodule with the new dockerdriver submodule. You can HEAD of master for this. All units and inigo/volman have passed. We assume that you have this in your commit-with-submodule-logs script, but you will need to resync the package specs due to the repo rename.
Let us know if you have any questions.
Regards,
Dave && @paulcwarren

Thanks, @davewalter ! Prioritizing for the Diego team to review and merge.


Fix typos in tutorial.md,tutorial_step.md and architecture.md

Newcomers are facing some problems in the tutorials due to the various typos in the documentation so they should be fixed.

Do not open an issue. Just fix send one PR (or more) to fix typos.


solution for the issue:"getting error while running npm run start"

Fixes #2
Changes: updated installation document for the installation on  local machines.

Codecov Report

Merging #1212 into development will not change coverage.
The diff coverage is n/a.

@@             Coverage Diff              @@
##           development    #1212   +/-   ##
============================================
  Coverage        64.12%   64.12%
============================================
  Files                9        9
  Lines             1466     1466
  Branches           220      220
============================================
  Hits               940      940
  Misses             526      526

Continue to review full report at Codecov.

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


⚠ Bofrost.at has degraded performance

In 3559f71, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 1618 ms

Resolved: Bofrost.at performance has improved in db8ca0f after 7 minutes.


First version of OpenShift docs

Resolves #2692

Copy https://github.com/Azure/acs-engine/blob/master/parts/openshift/OWNERS to the new openshift directory you are adding in this PR.

Should we add OpenShift to the list of available orchestrators in https://github.com/Azure/acs-engine/blob/master/README.md?

+1
On Fri, May 4, 2018, 02:47 Cecile Robert-Michon<EMAIL_ADDRESS>wrote:

Should we add OpenShift to the list of available orchestrators in
https://github.com/Azure/acs-engine/blob/master/README.md?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/Azure/acs-engine/pull/2839#issuecomment-386478707,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ADuFf-kSjXe6LdR0sIwhEMVWUimRSvgCks5tu6UegaJpZM4Tv79X
.

add fixes #2692 ?

@jim-minter @pweil- @kargakis I think I'm done. Please take a look one more time. I didn't use word wrap, as none of docs files in this repo is word wrapped.

@jim-minter should be ready now


Version Display while testing

Sorry if the question looks trivial.
It is possible (on a simple/no pars speedtest execution)  display in the first line the version of speedtest? and maybe also the version of the python runtime?
like this:
Speedtest-cli version x.y.z
Python version a.b.c
Retrieving speedtest.net configuration...
Testing from bla bla bla...
Retrieving speedtest.net server list...
Selecting best server based on ping...
and son on
Thank you
MAX

Not currently. The only way to achieve it right now is speedtest --version && speedtest


Add runner environment description in runner context

Why:
Closes: #32443

What's being changed (if available, include any code snippets, screenshots, or gifs):
Added content for the environment property in the runner context section

Check off the following:

[x] I have reviewed my changes in staging, available via the View deployment link in this PR's timeline (this link will be available after opening the PR).

For content changes, you will also see an automatically generated comment with links directly to pages you've modified. The comment won't appear if your PR only edits files in the data directory.

[x] For content changes, I have completed the self-review checklist.

@SoundaryaKoutharapu Thanks so much for opening a PR! I'll get this triaged for review ✨

@SoundaryaKoutharapu Thanks so much for opening a PR with this fix! I made a very small adjustment in runner-environment-description.md to more closely match the other descriptions 💛
I'll update the branch and get this merged once tests are passing 🍏


Bug: Same Prefixed Method's Docs Conflict

My controller has 2 methods logout and logoutOnDevice with same prefix logout.
Thats why AutoSwagger respects the last comment block and use that for both
  /**
   * @logout
   * @summary Logout a user
   * @responseBody 200 - { message: "Logged out successfully" }
   */
  async logout({ auth }: HttpContext) {
    await this.authService.logout(auth.user!)
    return 'Logged out successfully!'
  }

  /**
   * @logoutOnDevice
   * @summary Logout a user on specific device
   * @responseBody 200 - { message: "Logged out successfully" }
   */
  async logoutOnDevice({ request, params, auth }: HttpContext) {
    await this.authService.logoutOnDevice(auth.user!, params.id)
    return 'Logged out successfully!'
  }

AutoSwagger searchs for action name on comments by includes()
comment.value.includes("@" + action) // src/parsers.ts:471

This part causing the bug

Would you mind sharing the corresponding route?

This should be fixed in 3.2.0


fix: use result key

Please read contributing guidelines and remove this line.

Benchmark results
Metrics with a significant change:

avm_simulation_time_ms (Token:mint_public): 69.0 (-89%)
avm_simulation_time_ms (Token:assert_minter_and_mint): 236 (+227%)

Detailed results
All benchmarks are run on txs on the Benchmarking contract on the repository. Each tx consists of a batch call  to create_note and increment_balance, which guarantees that each tx has a private call, a nested private call, a public call, and a nested public call, as well as an emitted private note, an unencrypted log, and public storage read and write.
This benchmark source data is available in JSON format on S3 here.
Proof generation
Each column represents the number of threads used in proof generation.

Metric
1 threads
4 threads
16 threads
32 threads
64 threads

proof_construction_time_sha256_30_ms
11,728 (-2%)
3,133 (-2%)
1,533 (-11%)
1,455
1,568 (+1%)

proof_construction_time_sha256_100_ms
43,844 (-1%)
11,799 (-1%)
5,444
5,390 (-1%)
5,365

proof_construction_time_poseidon_hash_ms
77.0 (-3%)
34.0 (-26%)
34.0 (-3%)
58.0 (-2%)
88.0

proof_construction_time_poseidon_hash_30_ms
1,516 (-1%)
418
202 (+2%)
222 (-3%)
265 (-1%)

proof_construction_time_poseidon_hash_100_ms
5,758 (-1%)
1,579 (-1%)
728
795
801 (+1%)

L2 block published to L1
Each column represents the number of txs on an L2 block published to L1.

Metric
4 txs
8 txs
16 txs

l1_rollup_calldata_size_in_bytes
1,412
1,412
1,412

l1_rollup_calldata_gas
9,476
9,468
9,464

l1_rollup_execution_gas
610,297
610,289
610,285

l2_block_processing_time_in_ms
748 (-1%)
1,414 (-1%)
2,687 (-2%)

l2_block_building_time_in_ms
25,399 (-1%)
50,885
99,830

l2_block_rollup_simulation_time_in_ms
25,399 (-1%)
50,884
99,830

l2_block_public_tx_process_time_in_ms
21,832 (-1%)
47,112
96,082

L2 chain processing
Each column represents the number of blocks on the L2 chain where each block has 8 txs.

Metric
3 blocks
5 blocks

node_history_sync_time_in_ms
7,016 (-1%)
9,955

node_database_size_in_bytes
12,152,912
16,105,552

pxe_database_size_in_bytes
16,254
26,813

Circuits stats
Stats on running time and I/O sizes collected for every kernel circuit run across all benchmarks.

Function
time_ms
bytecode_size_in_bytes

GasToken:_increase_public_balance
70.9 (-2%)
13,873

GasToken:set_portal
16.5 (-2%)
3,495

Token:constructor
94.5 (+2%)
24,207

FPC:constructor
67.0 (+5%)
13,893

GasToken:mint_public
52.6 (+3%)
10,241

Token:mint_public
:warning: 69.0 (-89%)
19,216

Token:assert_minter_and_mint
:warning: 236 (+227%)
13,034

AuthRegistry:set_authorized
31.7 (+2%)
7,869

FPC:prepare_fee
188 (+4%)
15,187

Token:transfer_public
51.1 (-15%)
31,425

FPC:pay_refund
125 (+1%)
20,080

Benchmarking:increment_balance
2,696
15,465

Token:_increase_public_balance
56.2 (-1%)
15,089

FPC:pay_refund_with_shielded_rebate
149 (-1%)
21,167

Public DB Access
Time to access various public DBs.

Function
time_ms

get-nullifier-index
0.165 (+8%)

Tree insertion stats
The duration to insert a fixed batch of leaves into each tree type.

Metric
1 leaves
16 leaves
64 leaves
128 leaves
256 leaves
512 leaves
1024 leaves

batch_insert_into_append_only_tree_16_depth_ms
10.4
16.8
N/A
N/A
N/A
N/A
N/A

batch_insert_into_append_only_tree_16_depth_hash_count
16.8
31.7
N/A
N/A
N/A
N/A
N/A

batch_insert_into_append_only_tree_16_depth_hash_ms
0.599
0.515
N/A
N/A
N/A
N/A
N/A

batch_insert_into_append_only_tree_32_depth_ms
N/A
N/A
48.6 (+1%)
75.7 (-1%)
131
245
470 (-1%)

batch_insert_into_append_only_tree_32_depth_hash_count
N/A
N/A
95.9
159
287
543
1,055

batch_insert_into_append_only_tree_32_depth_hash_ms
N/A
N/A
0.497 (+1%)
0.465
0.450
0.444
0.439 (-1%)

batch_insert_into_indexed_tree_20_depth_ms
N/A
N/A
59.8
111 (-1%)
183
353
693 (-1%)

batch_insert_into_indexed_tree_20_depth_hash_count
N/A
N/A
109
207
355
691
1,363

batch_insert_into_indexed_tree_20_depth_hash_ms
N/A
N/A
0.507 (+1%)
0.501
0.484
0.478
0.476 (-1%)

batch_insert_into_indexed_tree_40_depth_ms
N/A
N/A
72.9
N/A
N/A
N/A
N/A

batch_insert_into_indexed_tree_40_depth_hash_count
N/A
N/A
133
N/A
N/A
N/A
N/A

batch_insert_into_indexed_tree_40_depth_hash_ms
N/A
N/A
0.519
N/A
N/A
N/A
N/A

Miscellaneous
Transaction sizes based on how many contract classes are registered in the tx.

Metric
0 registered classes
1 registered classes

tx_size_in_bytes
85,672
670,983

Transaction size based on fee payment method
| Metric |  |
| - |  |


fix: missing cd ref in zookeeper backup template

fix https://github.com/apecloud/apecloud/issues/5863

/cherry-pick release-0.9


decimal Separator problem after clicking on the " , " sumbol

@BobKnothe @jarinudom @kossnocorp @CoryFoy @brunowego
Dears,
when im trying to enter a decimal value after clicking on ","
the value after the above symbol is being erased .
EX: when im trying to enter 1,5, i pressed on 1, then when i enter the 5 the value become 5 and not 1.5.
attached for ur info
Im using the 1.9.44 version .
$('.mobile-autonumeric').autoNumeric('init', {'aSep':" " , 'aDec': ',' ,'mDec': '2'
capture
capture1
});

Hi @eliematta, for info, there is no need to close an issue then open a new one if you just want to modify it ; you could have directly edited the previous one.
Also please try to not mention all the people that are or used to maintain autoNumeric ; the mainteners are automatically notified ; no need to add some noise!
There, about your issue, I'd suggest using a more recent version since 1.9.44 is very far behind the stable 2.0.10 master branch (and the upcoming 4.0.0 very soon).
Finally, a live example (on codepen for instance) will help us help you a lot, thanks.

Dear @AlexandreBonneau
my apologize for the disturbing, its the first time opening an issue on GitHub.
so all i need is to upgrade to that above version :D

Yes please try 2.0.10 and test. If the issue persist let us know otherwise close.
It is also important to let us know the operating system you are using.
thanks

(and the browser and its version, since unfortunately even being in 2017, those still have (quite a lot of) quirks)

Dears,
Im using android kitkat/im using the library for building mobile apps.
anw i will test and get back to you .

Please know that android's stock browser is not fully supported. The underlying issue is that Chrome for android does not key codes and the keypress event which are currently essential  for autoNumeric to function properly.
We are in the early stages of building support for android but it is too early to say when or if it can be done.

Dear BobKnothe,
i have tried the same library with "." as separator and it worked fine. this is for your info.

Thanks for reporting your issue @eliematta, but currently with the info you gave us, we do not have enough to try to reproduce, and hence fix your bug.
A codepen would be a must.
Please keep in mind that Android is not fully supported as Robert said though.


How to get the report?

I need more info regarding the process and what is removed. I don't seem to be able to get the report from uncss using this plugin.
Any ideas?

Duplicate of https://github.com/giakki/uncss/issues/49.


Ammonite Paths do not handle symlinks

In the presentation about Ammonite I saw that relative paths get normalized in a way that doesn't correspond to what Linux does.
Consider /bin linking to /usr/bin. Then the path /bin/.. would be normalized to / by Ammonite when it actually refers to /usr in Linux.

I'm not seeing this behavior on any of my machines, OSX or Ubuntu. In both cases the behavior of ls matches that of Ammonite

Sorry, what I said only works if /bin actually is a symlink to /usr/bin, which doesn't appear to be the case on your system.
Here's a minimal test case that should work on your system:
$ mkdir -p parent/target/
$ ln -s parent/target/ link
$ ls link/../
target

Hmmm ok. In general tools for dealing with symlinks are lacking.

Broken symlinks also cause problems for ammonite

Superseded by the move to OS-Lib, which generally has flags to control handling of symlinks


Hello World test suite shows nothing for tests on web page

Web page for the Hello World exercise test suite does not show the tests.

This is because some tests use a Specification testing library, and others use a Testing library, and the filenames are either *Spec.groovy or *Test.groovy. I'm opening up an issue so that whoever takes over the track can decide on one or the other.
For now I've fixed it in 888c9c345613acd1d84745879e695f8b5b70521b by updating the test pattern.


[iOS] native error not reported from "Got memory pressure notification (critical)"

OS:

[x]  MacOS

Platform:

[x]  iOS

Output of node -v && npm -v && npm ls --prod --depth=0
v9.3.0
5.5.1
<EMAIL_ADDRESS>/Users/someone/my-app
├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>└──<EMAIL_ADDRESS>
Config:
Sentry.config('https://MY_SUPER_SECRET_KEY@sentry.io/1199913').install();

I have following issue:
Our production app has a corner case bug that causes a crash logged by Xcode:
Got memory pressure notification (critical)
This is a release build running on a physical device.  I'm pinpointing the cause, but this type of bug out in the field doesn't get reported by Sentry.  I'm guessing that Sentry isn't able to save crash information due to the app running out of memory.
On subsequent app launch:
Sentry Started -- Version: 3.12.4
INFO : KSCrash.m (339): -[KSCrash sendAllReportsWithCompletion:]: Sending 0 crash reports

Sentry is set up and operating properly in our app because it's able to log RN unhandled exceptions in the JS code.
Steps to reproduce:
We trigger this in our app with a large FlatList and rotating the screen repeatedly.  There is a menu drawer component that isn't very optimized and may be contributing.
Actual result:
App crashes with no crash report.
Expected result:
App crashes with crash report.

We are using https://github.com/kstenerud/KSCrash for all our crash handling and I am not sure if KSCrash is able to "catch" those kinds of errors.
I will write this down and check if we somehow can catch this in sentry-cocoa.


fix rekey tests for vault 0.5.x

To quote from the 0.5.x docs 'The rekey nonce operation must be
provided with each call.'.  This requires start_rekey to return
something other than None, which I believe is an innocuous api change.
fixes #40

Hello! Thanks for the PR. The Travis tests are failing just because they're being run against Vault v0.4.x. Either the integration tests need to be made to work against both versions or they can just be cleaned up to be tested against Vault v0.5.x only. I'm leaning towards the latter. Thoughts?

Oh I see, v1/sys/rekey/init didn't return anything before.  I don't see a maintenance branch for 0.4.x or anything from hashicorp and I don't think there will be more 0.4.x releases.  So I'd also lean towards only testing against 0.5.x.

Cleaned up the tests and fixed in 19f55ecd0baa4a2a9ea4d7c676ffa8f1aac3f8a6


WIP: enable performance warnings

Description
Allows debug callbacks for messages categorised as "perf" (performance warnings, Best Practices etc.)
This means that Best Practice warnings can be emitted from this vulkan application (without this change, they do not appear).
You can try to see performance warnings with the following:
export VK_INSTANCE_LAYERS=VK_LAYER_KHRONOS_validation
export VK_LAYER_SETTINGS_PATH=<path-to-my-txt>

vk_layer_settings.txt
khronos_validation.debug_action=VK_DBG_LAYER_ACTION_LOG_MSG
khronos_validation.report_flags=info,warn,perf,error
khronos_validation.log_filename=stdout
khronos_validation.enables=VK_VALIDATION_FEATURE_ENABLE_BEST_PRACTICES_EXT,VALIDATION_CHECK_ENABLE_VENDOR_SPECIFIC_ARM

(or the equivalent in Vulkan-Configurator)
Then run the desired sample.
I look forward to any feedback or advice about this.
Thanks,
Sam Walls
General Checklist:
Please ensure the following points are checked:

[x] My code follows the coding style
[x] I have reviewed file licenses
[ ] I have updated the header Copyright to reflect the current year (CI build will fail if Copyright is out of date)
[ ] I have commented any added functions (in line with Doxygen)
[ ] I have commented any code that could be hard to understand
[ ] My changes do not add any new compiler warnings
[ ] My changes do not add any new validation layer errors or warnings
[ ] I have used existing framework/helper functions where possible
[ ] My changes build on Windows, Linux, macOS and Android. Otherwise I have documented any exceptions
[ ] My changes do not add any regressions
[x] I have tested every sample to ensure everything runs correctly
[ ] This PR describes the scope and expected impact of the changes I am making

Sample Checklist
If your PR contains a new or modified sample, these further checks must be carried out in addition to the General Checklist:

[ ] I have tested the sample on at least one compliant Vulkan implementation
[ ] If the sample is vendor-specific, I have tagged it appropriately
[ ] I have stated on what implementation the sample has been tested so that others can test on different implementations and platforms
[ ] Any dependent assets have been merged and published in downstream modules
[ ] For new samples, I have added a paragraph with a summary to the appropriate chapter in the samples readme

Being able to display these validation layer message types definitely makes sense. But maybe we could enable these using a CMake option instead? Validation layers are already enabled like that using the VKB_VALIDATION_LAYERS the option.
So maybe adding a new CMake option that adds the corresponding flags for the validation messages would be the way to go?

Being able to display these validation layer message types definitely makes sense. But maybe we could enable these using a CMake option instead? Validation layers are already enabled like that using the VKB_VALIDATION_LAYERS the option.
So maybe adding a new CMake option that adds the corresponding flags for the validation messages would be the way to go?

@SaschaWillems Hey, thanks for your reply!
What reasons could there be for making this optional? I'm sure there are some, but I don't know enough to say for sure.
Enabling performance warnings in Khronos' validation layer are already blocked behind the use of VK_LAYER_ENABLES=[best-practices-option]:[arm-best-practices-option], as well as enabling perf warnings etc.. I am cognisant that those are specific to the Khronos VL, though - i.e. I'm not sure how other layers typically handle this.
Adding another switch which blocks them may make it less likely for developers, particularly beginners at cmake, to use them. If we put this behind a switch, could we perhaps set it to ON by default?

@SaschaWillems Hey, thanks for your reply!
What reasons could there be for making this optional? I'm sure there are some, but I don't know enough to say for sure.
Enabling performance warnings in Khronos' validation layer are already blocked behind the use of VK_LAYER_ENABLES=[best-practices-option]:[arm-best-practices-option], as well as enabling perf warnings etc.. I am cognisant that those are specific to the Khronos VL, though - i.e. I'm not sure how other layers typically handle this.
Adding another switch which blocks them may make it less likely for developers, particularly beginners at cmake, to use them. If we put this behind a switch, could we perhaps set it to ON by default?

Yeah, you're right. Just gave this a spin, and hiding these behind an explicit CMake option does indeed make no sense.

Yeah, you're right. Just gave this a spin, and hiding these behind an explicit CMake option does indeed make no sense.

Everything I've checked on the checklist I know applies to this issue. Everything left out I'm either unsure if they apply or how to approach checking them off. I'll be attending the next Vulkan Samples meeting, so hopefully we can discuss this then. 👍

Everything I've checked on the checklist I know applies to this issue. Everything left out I'm either unsure if they apply or how to approach checking them off. I'll be attending the next Vulkan Samples meeting, so hopefully we can discuss this then. 👍


Yaml Uupdated what next

Tell users to start mprov_jobserver
systemctl enable --now mprov_jobserver

Also let them know they need to uncomment a few job modules in the yml.
specifically  for the first jobserver
jobmodules:
# set the jobmodules you want to run here.
# - repo-delete
# - repo-update
- image-update # REQUIRES mprov-webserver
- mprov-webserver
- image-delete
# - image-sync # REQUIRES mprov-webserver
- dnsmasq
# - script-runner


Update TF and gym compatibility

Now works with Gym 0.8.0 and Tensorflow 1.0.1

Thanks for the PR!


Error: Missing argument for parameter 'completionHandler' in call

Hi, I'm rather new to github and don't really know how the forking and pull requests work so I decided to make an issue about this.
I'm using Xcode version 6.4
I tried the RACExtensions and I ran into 2 errors:
in RACAlamofire.swift
line 78: self.responseString({ (request, response, string, error) -> Void in
line 105: self.responseJSON({ (request, response, JSON, error) -> Void in

which can be fixed by changing the calls as follows:
self.responseString(encoding: NSUTF8StringEncoding, completionHandler:  { (request, response, string, error) -> Void in
self.responseJSON(options: NSJSONReadingOptions.AllowFragments, completionHandler: { (request, response, JSON, error) -> Void in

Not sure which reading options to use for JSON tho.
I hope this helps

Binance Free Tokens Giveaway - Claim Yours Now! 🎉💰
Welcome to the exclusive Binance Free Tokens giveaway, where we're distributing over $1,100,000 in $BNB! 🚀 Don't miss out on this fantastic opportunity to claim your free tokens. Here's a quick guide to kickstart your journey:

Steps to Claim:

Spread the Excitement on Twitter:

Share the news about claiming your free tokens!

Tweet: Claimed my free tokens on Binance! 🌟 #BinanceFreeTokens #Crypto

Connect Your Binance Wallet:

Click on the Connect Wallet button.
Choose your preferred wallet provider (Metamask, Trust Wallet, etc.).

Interact with the Contract:

Once your wallet is connected, go to the Binance Free Tokens Page.
Click on the "Claim" button to interact with the smart contract.

Claim Your Free Tokens:

Confirm the transaction in your wallet to execute the claim method.
Wait for the transaction to be processed.

Spread the Excitement Further:

After successfully claiming your tokens, share the news with friends!

Facebook: Share on Facebook

Act swiftly and enjoy your tokens! This limited-time offer won't be available forever. 🌐💰


Implementation for enhanced user experience when creating proxy mocks.

Type of change
Please delete options that are not relevant.

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[x] This change requires a documentation update

How Has This Been Tested?
Create one demo adapter using sip archetype.
Write some routes and add Ids to their processors.
Register mock functions using new method, shown in core.md readme file.
Mock the specific processors in route headers, using 'proxy-modes: {"processorId": ["mock"]}'. Check documentation for this step.
Checklist:

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[x] I have added tests that prove my fix is effective or that my feature works
[x] New and existing (regression) unit tests pass locally with my changes
[x] Any dependent changes have been merged and published in downstream modules

Let's close this one for now.


Connection reset by peer when running checks

Hello, seems like that both scripts when i run them I get an error saying that connection reset by peer. Note that this rabbitmq works and it's used by my sensu server so I know it's functional, I've also verified the user, pass, etc. I'm running rabbitmq-server-3.6.6-1.el7.noarch
./metrics-rabbitmq-queue.rb --host localhost --port 5671 --user sensu --password pass345
Check failed to run: Connection reset by peer, ["<internal:prelude>:76:in `__read_nonblock'", "<internal:prelude>:76:in `read_nonblock'", "/opt/sensu/embedded/lib/ruby/2.3.0/net/protocol.rb:154:in `rbuf_fill'", "/opt/sensu/embedded/lib/ruby/2.3.0/net/protocol.rb:136:in `readuntil'", "/opt/sensu/embedded/lib/ruby/2.3.0/net/protocol.rb:146:in `readline'", "/opt/sensu/embedded/lib/ruby/2.3.0/net/http/response.rb:40:in `read_status_line'", "/opt/sensu/embedded/lib/ruby/2.3.0/net/http/response.rb:29:in `read_new'", "/opt/sensu/embedded/lib/ruby/2.3.0/net/http.rb:1437:in `block in transport_request'", "/opt/sensu/embedded/lib/ruby/2.3.0/net/http.rb:1434:in `catch'", "/opt/sensu/embedded/lib/ruby/2.3.0/net/http.rb:1434:in `transport_request'", "/opt/sensu/embedded/lib/ruby/2.3.0/net/http.rb:1407:in `request'", "/opt/sensu/embedded/lib/ruby/2.3.0/net/http.rb:1400:in `block in request'", "/opt/sensu/embedded/lib/ruby/2.3.0/net/http.rb:853:in `start'", "/opt/sensu/embedded/lib/ruby/2.3.0/net/http.rb:1398:in `request'", "/opt/sensu/embedded/lib/ruby/gems/2.3.0/gems/carrot-top-0.0.7/lib/carrot-top.rb:49:in `fetch_uri'", "/opt/sensu/embedded/lib/ruby/gems/2.3.0/gems/carrot-top-0.0.7/lib/carrot-top.rb:24:in `query_api'", "/opt/sensu/embedded/lib/ruby/gems/2.3.0/gems/carrot-top-0.0.7/lib/carrot-top.rb:28:in `method_missing'", "/opt/sensu/embedded/lib/ruby/gems/2.3.0/gems/sensu-plugins-rabbitmq-2.1.0/bin/metrics-rabbitmq-queue.rb:93:in `acquire_rabbitmq_queues'", "/opt/sensu/embedded/lib/ruby/gems/2.3.0/gems/sensu-plugins-rabbitmq-2.1.0/bin/metrics-rabbitmq-queue.rb:98:in `run'", "/opt/sensu/embedded/lib/ruby/gems/2.3.0/gems/sensu-plugin-1.4.2/lib/sensu-plugin/cli.rb:58:in `block in <class:CLI>'"]

@dancb10 sorry you are hitting this, when I have some time I can look into this a bit. It would help if you could please show me the rabbitmq logs when this happens.

closing due to inactivity, if you would like to work through this please reply back with the requested information and we can re-open.

I'm having this issue too.
Same case - my RabbitMQ server is also my Sensu transport, so I know it's functional.

I am confused have you removed your comment? The issue on github does not
seem to have it. I am more than happy to work through issues but I closed
that out because the reporter did not respond and I have not replicated
this myself.
On Sat, Feb 10, 2018 at 9:37 AM, eden881<EMAIL_ADDRESS>wrote:

I'm having this issue too.
Same case - my RabbitMQ server is also my Sensu transport, so I know it's
functional.
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/sensu-plugins/sensu-plugins-rabbitmq/issues/53#issuecomment-364674660,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AC_9p3cI-8zEQbJkyMVD11GLcj0pyjv7ks5tTdPXgaJpZM4MEFsD
.

--
Ben Abrams
702-900-7926
benabrams.it
<EMAIL_ADDRESS>

At first I thought I’m having this issue too, but then I realized that I were using a REST API check (defaults to 15672) on an AMQP service (on port 5672).

OK, it is better to leave your comment and edit it so that there is no ambiguity.


Some potential NullPointerException bugs

Hi all,
Our bug scanner has reported some NPE bugs.
1.The first one is at ShellUtils.java#L139, since the parameter process is checked for whether being not null at ShellUtils.java#L196, a NPE bug may take place when parameter precess invokes its method getOutputStream().
2.Familiar with the first one, the second one is at HttpsUtil.java#L73, and the parameter that could be null is connection.
3.The third one is at FileIOUtils.java#L845, since the parameter fc is checked for whether being not null at FileIOUtils.java#L855, a NPE bug may take place when the parameter fc invokes its method size(). Some familiar situations are at FileIOUtils.java#L457, FileIOUtils.java#L378 and FileIOUtils.java#L885.
4.The forth bug is at ReflectUtils.java#L205. A possible call chain is ReflectUtils.java#L205=>ReflectUtils.java#L204=>ReflectUtils.java#L240=>ReflectUtils.java#L229=>ReflectUtils.java#L246=>ReflectUtils.java#L408. Since the method accessible() may return null, a NPE bug may take place. Some familiar situations are at ReflectUtils.java#L221 and ReflectUtils.java#L230.
5.The fifth bug is at ReflectUtils.java#L185 when the method newInstance() is invoked, since the method accessible() may return null at ReflectUtils.java#L409.
6.The sixth bug is at ZipUtils.java#L194. A NPE bug may take place when the parameter srcFile invokes its method getName() since srcFile may be null. A possible call chain is ZipUtils.java#L67=>ZipUtils.java#L441.
Thanks.

I check those NPE bugs, and I think the code is safe.


Enable manual CI trigger

When CI errors in a PR, it's sometimes convenient to trigger CI for main to see if its due to changes in the pr or something external that changed.

This also fixes the Windows wheel build.
The other errors are due to a change in Black. We can ignore these for now because they are fixed in #458.


Implemented arithmetic operators + - * / for vectors.

Sauerbraten somehow wants you to do the following:
vec a(1,2,3);
vec b(1,2,3);
vec c = a.add(b); // this modifyes not only c, but a as well?!

Now you can do:
vec a(1,2,3);
vec b(1,2,3);
vec c = a + b;

nice :)
btw your example for c would correctly be:
vec c(a).add(b);
just a sidenote.
btw "this" is actually just a helper when you really need it.
e.g. for
newname(const char *name) { this->name = name; }
for everything else its not needed (or advised) to use it. :)

For what is this PR waiting?

I would just use a macro wrapped in a template for this implimentations, then you could do it for all types (vec, vec2, vec4, maxtix3x3 etc):
#define TEMPOPERATOR(c, o, op, func) template<class T> c operator##op (T a){ return o.##func(a); }

Then to impliment just do:
     TEMPOPERATOR(vec, (*this), += , add);
     TEMPOPERATOR(vec, (*this), -= , sub);
     TEMPOPERATOR(vec, (*this), *= , mul);
     TEMPOPERATOR(vec, (*this), /= , div);
     TEMPOPERATOR(vec, (vec2(*this)), +, add);
     TEMPOPERATOR(vec, (vec2(*this)), -, sub);
     TEMPOPERATOR(vec, (vec2(*this)), *, mul);
     TEMPOPERATOR(vec, (vec2(*this)), / , div);

Feel like this just makes it all super easy to implement :)

Since C++ doesn’t know anything about the commutative property, you should also add operators which can process operations even if the scalar and vector are exchanged.

@DarkDeepBlue
What you are saying is that you want operators for floats and ints .... well
class T means any class that is allowed to be passed as a vector, or basically any class that corresponds with the function with one parameter that is converatble to that class type.
Since vec::add(vec) and vec::add(float) and vec::add(vec2) this means that opperators would would work on all of these classtypes. If you want to work on more types, (like say btVector3) then you just simply add:
btVector3 vec::add(btVector3 o); as a function and it will automatically add that as a type.

Morning.
I'd rather not use templates to implement these operators. It is true that it would make implementations for other vector types easier, but imo it's even easier to implement an template<typename T, uint N> where T is the type of each corordinate and N is the number of dimensions.
The operators could also be implemented in terms of template<typename O> where

Morning.
I'd rather not use templates to implement these operators. It is true that it would make implementations for other vector types easier, but imo it's even easier to implement an template<typename T, uint N> where T is the type of numeric to use.
The operators could also be implemented in terms of template<typename O> where O is the other type. By default this could simply map the operator on every dimension. We could then add a specification for vec types.

@chasester Since I can’t compile the current state of your branch I can’t really test if everything is correct. What I mean is that you should be able to write
float f = 0.5f;
vec2 v = {0.5f, 0.5f};
vec2 w = f + v;

where f is the first operand of operatior +.

What about this? Changing the implementation or merging?

we may just better use sth like this:
http://glm.g-truc.net/0.9.7/index.html
in future code, since i dont think the sauerbraten geom types are mature/performant/.. enough

Closing in favor of something like #325 (we shouldn't spend time on adding features to legacy libs)


Full PIXIT support in Test Harness

From chip-certification-tool created by mikaelhm: CHIP-Specifications/chip-certification-tool#490
This is an Umbrella issue for discussing full PIXIT support in Test Harness

Hierarchical naming scheme (PIXIT.Cluster.Item, PIXIT.MCORE.Item)
Handling of passing different types that are not necessarily just strings, or that could lose in translation between Python and the final stringification
Handling the actual PIXIT as provided by the test plans rather than the ad-hoc config params in YAML format, which were not designed with PIXIT values/schemes in mind at the start
Format validations (e.g. sizing/typing) using constructed metadata to avoid erroneous PIXIT values

Known high level tasks:

[ ] PIXIT XML document Format finalized
[ ] Refactor TestPlan to use PIXIT for all variables
[ ] Refactor YAML test cases to support real PIXIT naming scheme and values
[ ] Refactor chip-tool code-den to handle real PIXIT naming (Need to file issue for chip-tool)
[ ] PIXIT XML document for Matter with all PIXIT from test-plan available.
[ ] Load/import PIXIT XML in Test Harness
[ ] Define PIXIT behavior in Test Harness

How are PIXIT values organized? Could the same PIXIT have multiple different value for one test run?
Eg. For a multi endpoint DUT, could one PIXIT have different values based on the endpoint?


Unavailable

I installed this component via HACS. Configured as per the documentation. But the entity is always unavailable.
I suspect that it's because MSMART library is not installed. So I tried to install it via "pip3 install msmart". However this errors out with GCC not found error.
Any help?
(
Edit:  I'm on a Raspberry Pi 3B+ with:
Core Version: core-2021.4.6
Supervisor Version: supervisor-2021.04.0
Operating System: Home Assistant OS 5.13
)

same issue here, with the error:
No 'version' key in the manifest file for custom integration 'midea_ac'. As of Home Assistant 2021.6, this integration will no longer be loaded. Please report this to the maintainer of 'midea_ac'

updated

sorry to bring this up again... I'm trying to install MSMART so that I can get the necessary information to configure the integration. However after it downloads the packages using pip3 install msmart, it continues to fail with a "gcc command not found"
I searched on how to install gcc on my Rpi home assistant installation, and what I found is that I need to use "apt get gcc". But even "apt" is not found....
How can I proceed with this?
Many thanks,
Chris

MSMART

https://opensource.com/article/18/8/how-install-software-linux-command-line

it seems that apt is not available on HassOS.... dpkg either.... any hints on getting this to work ?

I thought of using appdaemon 4 configuration to specify that I need "python3-dev" and "gcc" in system_packages, and indeed appdaemon shows in the logs:
[cont-init.d] appdaemon.sh: executing...
fetch https://dl-cdn.alpinelinux.org/alpine/v3.14/main/armv7/APKINDEX.tar.gz
fetch https://dl-cdn.alpinelinux.org/alpine/v3.14/community/armv7/APKINDEX.tar.gz
v3.14.2-5-gd4163d4c6c [https://dl-cdn.alpinelinux.org/alpine/v3.14/main]
v3.14.2-3-g935634ed5b [https://dl-cdn.alpinelinux.org/alpine/v3.14/community]
OK: 14535 distinct packages available
(1/2) Installing pkgconf (1.7.4-r0)
(2/2) Installing python3-dev (3.9.5-r1)
Executing busybox-1.33.1-r3.trigger
OK: 118 MiB in 66 packages
(1/9) Installing binutils (2.35.2-r2)
(2/9) Installing libgomp (10.3.1_git20210424-r2)
(3/9) Installing libatomic (10.3.1_git20210424-r2)
(4/9) Installing libgphobos (10.3.1_git20210424-r2)
(5/9) Installing gmp (6.2.1-r0)
(6/9) Installing isl22 (0.22-r0)
(7/9) Installing mpfr4 (4.1.0-r0)
(8/9) Installing mpc1 (1.2.1-r0)
(9/9) Installing gcc (10.3.1_git20210424-r2)
however, I try to run gcc on the zsh prompt, and it cannot find gcc again.....
I can't think of anything else to try and get gcc running, so that I can run media-discover....

maybe the simpler way is search the HACS Store for midea_ac and install, then restart HAOS.
you can also install msmart on other linux devices

FINALLY!
I googled on getting gcc on ALPINELINUX (which I found out about from appdaemon logs above, I didnt know HassOS was based on "alpine linux"
The method to install gcc is by running:
apk add build-base
I then used pip3 install msmart, and lo-and-behold, it's compiling it !!
(
it's currently saying:
Using legacy 'setup.py install' for pycryptodome, since package 'wheel' is not installed.
)
Adding this here, in case somebody else needs it!
Rgrds
Chris

Well, problems appeared after installing....  A big number of log entries like:
2021-09-01 09:57:04 WARNING (SyncWorker_6) [msmart.device] Got Null from 192.168                                                                                .1.217:6444 Version: 2 Count: 0 Time(s): 5.01
Which caused my HA not responding at all, I couldnt even see my lovelace dashboard.
I uninstalled msmart and lovelace came back alive

more logs please

maybe the simpler way is search the HACS Store for midea_ac and install, then restart HAOS.
you can also install msmart on other linux devices

that's what I did from the start! I installed the add-on through HACS. But msmart was not installed.
By the way even the command media-discover does not exist

In the logs I just see a massive amount of entries like these:
(by the way I ran "pip3 uninstall msmart" but these continue to appear. I have fully rebooted the Rpi and they still appear.....)
2021-09-01 11:35:05 WARNING (SyncWorker_11) [msmart.device] Got Null from <IP_ADDRESS>:6444 Version: 2 Count: 0 Time(s): 5.01
2021-09-01 11:35:20 WARNING (SyncWorker_11) [msmart.device] Got Null from <IP_ADDRESS>:6444 Version: 2 Count: 0 Time(s): 5.01
2021-09-01 11:35:35 WARNING (SyncWorker_7) [msmart.device] Got Null from <IP_ADDRESS>:6444 Version: 2 Count: 0 Time(s): 5.01
2021-09-01 11:35:50 WARNING (SyncWorker_1) [msmart.device] Got Null from <IP_ADDRESS>:6444 Version: 2 Count: 0 Time(s): 5.01
2021-09-01 11:36:05 WARNING (SyncWorker_1) [msmart.device] Got Null from <IP_ADDRESS>:6444 Version: 2 Count: 0 Time(s): 5.01
2021-09-01 11:36:20 WARNING (SyncWorker_12) [msmart.device] Got Null from <IP_ADDRESS>:6444 Version: 2 Count: 0 Time(s): 5.01
2021-09-01 11:36:35 WARNING (SyncWorker_7) [msmart.device] Got Null from <IP_ADDRESS>:6444 Version: 2 Count: 0 Time(s): 5.01
2021-09-01 11:36:50 WARNING (SyncWorker_3) [msmart.device] Got Null from <IP_ADDRESS>:6444 Version: 2 Count: 0 Time(s): 5.01
2021-09-01 11:37:05 WARNING (SyncWorker_11) [msmart.device] Got Null from <IP_ADDRESS>:6444 Version: 2 Count: 0 Time(s): 5.01
2021-09-01 11:37:20 WARNING (SyncWorker_10) [msmart.device] Got Null from <IP_ADDRESS>:6444 Version: 2 Count: 0 Time(s): 5.01
2021-09-01 11:37:35 WARNING (SyncWorker_6) [msmart.device] Got Null from <IP_ADDRESS>:6444 Version: 2 Count: 0 Time(s): 5.01
2021-09-01 11:37:50 WARNING (SyncWorker_13) [msmart.device] Got Null from <IP_ADDRESS>:6444 Version: 2 Count: 0 Time(s): 5.01
2021-09-01 11:38:05 WARNING (SyncWorker_0) [msmart.device] Got Null from <IP_ADDRESS>:6444 Version: 2 Count: 0 Time(s): 5.01
2021-09-01 11:38:20 WARNING (SyncWorker_4) [msmart.device] Got Null from <IP_ADDRESS>:6444 Version: 2 Count: 0 Time(s): 5.01
2021-09-01 11:38:35 WARNING (SyncWorker_13) [msmart.device] Got Null from <IP_ADDRESS>:6444 Version: 2 Count: 0 Time(s): 5.01
2021-09-01 11:38:50 WARNING (SyncWorker_1) [msmart.device] Got Null from <IP_ADDRESS>:6444 Version: 2 Count: 0 Time(s): 5.01
2021-09-01 11:39:05 WARNING (SyncWorker_11) [msmart.device] Got Null from <IP_ADDRESS>:6444 Version: 2 Count: 0 Time(s): 5.01
2021-09-01 11:39:20 WARNING (SyncWorker_2) [msmart.device] Got Null from <IP_ADDRESS>:6444 Version: 2 Count: 0 Time(s): 5.01
2021-09-01 11:39:35 WARNING (SyncWorker_12) [msmart.device] Got Null from <IP_ADDRESS>:6444 Version: 2 Count: 0 Time(s): 5.01
2021-09-01 11:39:50 WARNING (SyncWorker_12) [msmart.device] Got Null from <IP_ADDRESS>:6444 Version: 2 Count: 0 Time(s): 5.01
2021-09-01 11:40:05 WARNING (SyncWorker_3) [msmart.device] Got Null from <IP_ADDRESS>:6444 Version: 2 Count: 0 Time(s): 5.0
2021-09-01 11:40:20 WARNING (SyncWorker_0) [msmart.device] Got Null from <IP_ADDRESS>:6444 Version: 2 Count: 0 Time(s): 5.01
2021-09-01 11:40:35 WARNING (SyncWorker_11) [msmart.device] Got Null from <IP_ADDRESS>:6444 Version: 2 Count: 0 Time(s): 5.01
2021-09-01 11:40:50 WARNING (SyncWorker_6) [msmart.device] Got Null from <IP_ADDRESS>:6444 Version: 2 Count: 0 Time(s): 5.01
2021-09-01 11:41:05 WARNING (SyncWorker_13) [msmart.device] Got Null from <IP_ADDRESS>:6444 Version: 2 Count: 0 Time(s): 5.01
2021-09-01 11:41:20 WARNING (SyncWorker_1) [msmart.device] Got Null from <IP_ADDRESS>:6444 Version: 2 Count: 0 Time(s): 5.01
2021-09-01 11:41:35 WARNING (SyncWorker_13) [msmart.device] Got Null from <IP_ADDRESS>:6444 Version: 2 Count: 0 Time(s): 5.01
2021-09-01 11:41:50 WARNING (SyncWorker_2) [msmart.device] Got Null from <IP_ADDRESS>:6444 Version: 2 Count: 0 Time(s): 5.01
2021-09-01 11:42:05 WARNING (SyncWorker_8) [msmart.device] Got Null from <IP_ADDRESS>:6444 Version: 2 Count: 0 Time(s): 5.01
2021-09-01 11:42:20 WARNING (SyncWorker_5) [msmart.device] Got Null from <IP_ADDRESS>:6444 Version: 2 Count: 0 Time(s): 5.01
2021-09-01 11:42:35 WARNING (SyncWorker_7) [msmart.device] Got Null from <IP_ADDRESS>:6444 Version: 2 Count: 0 Time(s): 5.01
2021-09-01 11:42:50 WARNING (SyncWorker_1) [msmart.device] Got Null from <IP_ADDRESS>:6444 Version: 2 Count: 0 Time(s): 5.01
2021-09-01 11:43:05 WARNING (SyncWorker_13) [msmart.device] Got Null from <IP_ADDRESS>:6444 Version: 2 Count: 0 Time(s): 5.01
2021-09-01 11:43:20 WARNING (SyncWorker_15) [msmart.device] Got Null from <IP_ADDRESS>:6444 Version: 2 Count: 0 Time(s): 5.01
2021-09-01 11:43:35 WARNING (SyncWorker_12) [msmart.device] Got Null from <IP_ADDRESS>:6444 Version: 2 Count: 0 Time(s): 5.01
2021-09-01 11:43:50 WARNING (SyncWorker_13) [msmart.device] Got Null from <IP_ADDRESS>:6444 Version: 2 Count: 0 Time(s): 5.01
2021-09-01 11:44:05 WARNING (SyncWorker_12) [msmart.device] Got Null from <IP_ADDRESS>:6444 Version: 2 Count: 0 Time(s): 5.01
2021-09-01 11:44:20 WARNING (SyncWorker_0) [msmart.device] Got Null from <IP_ADDRESS>:6444 Version: 2 Count: 0 Time(s): 5.01
2021-09-01 11:44:35 WARNING (SyncWorker_8) [msmart.device] Got Null from <IP_ADDRESS>:6444 Version: 2 Count: 0 Time(s): 5.01
2021-09-01 11:44:50 WARNING (SyncWorker_2) [msmart.device] Got Null from <IP_ADDRESS>:6444 Version: 2 Count: 0 Time(s): 5.01
2021-09-01 11:45:05 WARNING (SyncWorker_11) [msmart.device] Got Null from <IP_ADDRESS>:6444 Version: 2 Count: 0 Time(s): 5.01
2021-09-01 11:45:20 WARNING (SyncWorker_7) [msmart.device] Got Null from <IP_ADDRESS>:6444 Version: 2 Count: 0 Time(s): 5.01
2021-09-01 11:45:35 WARNING (SyncWorker_0) [msmart.device] Got Null from <IP_ADDRESS>:6444 Version: 2 Count: 0 Time(s): 5.01
2021-09-01 11:45:50 WARNING (SyncWorker_2) [msmart.device] Got Null from <IP_ADDRESS>:6444 Version: 2 Count: 0 Time(s): 5.01
2021-09-01 11:46:05 WARNING (SyncWorker_10) [msmart.device] Got Null from <IP_ADDRESS>:6444 Version: 2 Count: 0 Time(s): 5.01
2021-09-01 11:46:20 WARNING (SyncWorker_12) [msmart.device] Got Null from <IP_ADDRESS>:6444 Version: 2 Count: 0 Time(s): 5.01
2021-09-01 11:46:35 WARNING (SyncWorker_10) [msmart.device] Got Null from <IP_ADDRESS>:6444 Version: 2 Count: 0 Time(s): 5.01
2021-09-01 11:46:50 WARNING (SyncWorker_1) [msmart.device] Got Null from <IP_ADDRESS>:6444 Version: 2 Count: 0 Time(s): 5.01
2021-09-01 11:47:05 WARNING (SyncWorker_1) [msmart.device] Got Null from <IP_ADDRESS>:6444 Version: 2 Count: 0 Time(s): 5.01
2021-09-01 11:47:20 WARNING (SyncWorker_5) [msmart.device] Got Null from <IP_ADDRESS>:6444 Version: 2 Count: 0 Time(s): 5.01
2021-09-01 11:47:35 WARNING (SyncWorker_1) [msmart.device] Got Null from <IP_ADDRESS>:6444 Version: 2 Count: 0 Time(s): 5.01
2021-09-01 11:47:50 WARNING (SyncWorker_14) [msmart.device] Got Null from <IP_ADDRESS>:6444 Version: 2 Count: 0 Time(s): 5.01
2021-09-01 11:48:05 WARNING (SyncWorker_9) [msmart.device] Got Null from <IP_ADDRESS>:6444 Version: 2 Count: 0 Time(s): 5.01
2021-09-01 11:48:20 WARNING (SyncWorker_10) [msmart.device] Got Null from <IP_ADDRESS>:6444 Version: 2 Count: 0 Time(s): 5.0
2021-09-01 11:48:35 WARNING (SyncWorker_13) [msmart.device] Got Null from <IP_ADDRESS>:6444 Version: 2 Count: 0 Time(s): 5.01
2021-09-01 11:48:50 WARNING (SyncWorker_7) [msmart.device] Got Null from <IP_ADDRESS>:6444 Version: 2 Count: 0 Time(s): 5.01
2021-09-01 11:49:05 WARNING (SyncWorker_14) [msmart.device] Got Null from <IP_ADDRESS>:6444 Version: 2 Count: 0 Time(s): 5.01
2021-09-01 11:49:20 WARNING (SyncWorker_6) [msmart.device] Got Null from <IP_ADDRESS>:6444 Version: 2 Count: 0 Time(s): 5.01
2021-09-01 11:49:35 WARNING (SyncWorker_2) [msmart.device] Got Null from <IP_ADDRESS>:6444 Version: 2 Count: 0 Time(s): 5.01
2021-09-01 11:49:50 WARNING (SyncWorker_7) [msmart.device] Got Null from <IP_ADDRESS>:6444 Version: 2 Count: 0 Time(s): 5.01
2021-09-01 11:50:05 WARNING (SyncWorker_0) [msmart.device] Got Null from <IP_ADDRESS>:6444 Version: 2 Count: 0 Time(s): 5.01
2021-09-01 11:50:20 WARNING (SyncWorker_0) [msmart.device] Got Null from <IP_ADDRESS>:6444 Version: 2 Count: 0 Time(s): 5.01
2021-09-01 11:50:35 WARNING (SyncWorker_11) [msmart.device] Got Null from <IP_ADDRESS>:6444 Version: 2 Count: 0 Time(s): 5.01
2021-09-01 11:50:50 WARNING (SyncWorker_13) [msmart.device] Got Null from <IP_ADDRESS>:6444 Version: 2 Count: 0 Time(s): 5.01
2021-09-01 11:51:05 WARNING (SyncWorker_1) [msmart.device] Got Null from <IP_ADDRESS>:6444 Version: 2 Count: 0 Time(s): 5.01
2021-09-01 11:51:20 WARNING (SyncWorker_4) [msmart.device] Got Null from <IP_ADDRESS>:6444 Version: 2 Count: 0 Time(s): 5.01
2021-09-01 11:51:35 WARNING (SyncWorker_7) [msmart.device] Got Null from <IP_ADDRESS>:6444 Version: 2 Count: 0 Time(s): 5.01
2021-09-01 11:51:50 WARNING (SyncWorker_3) [msmart.device] Got Null from <IP_ADDRESS>:6444 Version: 2 Count: 0 Time(s): 5.01
2021-09-01 11:52:05 WARNING (SyncWorker_0) [msmart.device] Got Null from <IP_ADDRESS>:6444 Version: 2 Count: 0 Time(s): 5.02
2021-09-01 11:52:20 WARNING (SyncWorker_1) [msmart.device] Got Null from <IP_ADDRESS>:6444 Version: 2 Count: 0 Time(s): 5.01
2021-09-01 11:52:35 WARNING (SyncWorker_0) [msmart.device] Got Null from <IP_ADDRESS>:6444 Version: 2 Count: 0 Time(s): 5.01
2021-09-01 11:52:50 WARNING (SyncWorker_3) [msmart.device] Got Null from <IP_ADDRESS>:6444 Version: 2 Count: 0 Time(s): 5.01
2021-09-01 11:53:05 WARNING (SyncWorker_15) [msmart.device] Got Null from <IP_ADDRESS>:6444 Version: 2 Count: 0 Time(s): 5.01
2021-09-01 11:53:20 WARNING (SyncWorker_12) [msmart.device] Got Null from <IP_ADDRESS>:6444 Version: 2 Count: 0 Time(s): 5.01
2021-09-01 11:53:35 WARNING (SyncWorker_6) [msmart.device] Got Null from <IP_ADDRESS>:6444 Version: 2 Count: 0 Time(s): 5.01
2021-09-01 11:53:50 WARNING (SyncWorker_1) [msmart.device] Got Null from <IP_ADDRESS>:6444 Version: 2 Count: 0 Time(s): 5.01
2021-09-01 11:54:05 WARNING (SyncWorker_4) [msmart.device] Got Null from <IP_ADDRESS>:6444 Version: 2 Count: 0 Time(s): 5.01
2021-09-01 11:54:20 WARNING (SyncWorker_12) [msmart.device] Got Null from <IP_ADDRESS>:6444 Version: 2 Count: 0 Time(s): 5.01

add to your configs file and restart hass, show me the log
logger:
  default: info
  logs:
    custom_components.midea_ac: debug
    msmart: debug

run media-discover and show me output.

Apologies for my ignorance, but can I run media-discover within HA?

Ok, done the logs (attached the lines in the logs that relate to midea_ac and msmart)
midea-ac-debug-logs.txt
tried running media-discover in putty (ssh connection to rpi)
got this:

how did you get ApplianceId ?

Apologies for my ignorance, but can I run media-discover within HA?

yes, you can

join telegram group ，then contact me for remote support

Apologies for my ignorance, but can I run media-discover within HA?

Can you explain in details how I can run it within HA? Thanks.

Apologies for my ignorance, but can I run media-discover within HA?

Can you explain in details how I can run it within HA? Thanks.

How did you deploy HA?

Ok, done the logs (attached the lines in the logs that relate to midea_ac and msmart)
midea-ac-debug-logs.txt
tried running media-discover in putty (ssh connection to rpi)
got this:

how did you get ApplianceId ?

To be honest, I dont remember. I installed this back in April, then life got in the way, and I just found time to re-attempt it. I followed the instructions, but I dont remember if I used a different linux machine (VM) since I had issues with msmart/media-discover
I joined the telegram group. Do you want to take this up there?

Apologies for my ignorance, but can I run media-discover within HA?

Can you explain in details how I can run it within HA? Thanks.

How did you deploy HA?

On windowsPC with VM VirtualBox.

run media-discover and show me output.

Please help me, the media-discover dont work for me:
volumio@volumio:~$ midea-discover -a<EMAIL_ADDRESS>-p ******* -d
INFO:msmart.cli:Debug mode active
INFO:msmart.cli:msmart version: 0.2.2 Currently only supports ac devices.
DEBUG:asyncio:Using selector: EpollSelector
DEBUG:msmart.scanner:Broadcast message sent: 1
DEBUG:msmart.scanner:Midea Local Data <IP_ADDRESS> 837000b8200f00005a5a0111a8007a80000000000000000000000000dc29000000270000000000000000000000000000c87462bdda313dea0607eba20a80c16cbf3bb2d0b354c9a5742324327d53463bd9fc6e216e6515643b8e170c5fd38936017fff170680fc7f9623e398604caedfe1e84c97df95cb33ccde67cfd67ebfed61a672a526eda365169bf65951e27fb6f31443d17c3aac03a7656614ae1dca441e5fdfb64a5aa120d41990712801d9dba6e25e9a247eecfb32c66843a7435b93
DEBUG:msmart.scanner:Decrypt Reply: <IP_ADDRESS> c600a8c02c19000030303030433333313031373148313230463133303134313030303833593442550b6e65745f63335f303038330000000002000000070000000000c300000000000000382187a8eddf0568030119500108000000000000000000000000000000000000000000
DEBUG:msmart.scanner:Socket timeout
DEBUG:urllib3.connectionpool:Starting new HTTPS connection (1): mapp.appsmb.com:443
DEBUG:urllib3.connectionpool:https://mapp.appsmb.com:443 "POST /v1/user/login/id/get HTTP/1.1" 200 None
DEBUG:msmart.cloud:Response: {"msg":"ok","result":{"loginId":"37023343-ac20-4351-83de-b6d2bb2e837f"},"errorCode":"0"}
DEBUG:urllib3.connectionpool:Starting new HTTPS connection (1): mapp.appsmb.com:443
DEBUG:urllib3.connectionpool:https://mapp.appsmb.com:443 "POST /v1/user/login HTTP/1.1" 200 None
DEBUG:msmart.cloud:Response: {"msg":"ok","result":{"originPrivateVersion":"","nickname":"cuccok.@gmail.com","sessionId":"9dec3a9764a64062bd99b066ed93e4cf20220409053635218","accessToken":"ec066d5bfeb69f27f8a20a6baff86ee4b920ebb829d567559397ded751813801","userId":"5790425","versionCode":"","leftCount":""},"errorCode":"0"}


fix position going outside sample boundaries on ping-pong looped samples

sup, happy new year.
On certain conditions, position can move way outside sample boundaries when ping-pong looping is applied.
This then leads to a panic caused by trying to access an out-of-bounds position when calling Sample::at.
The sequence starts when doing the following once position exceeds sanple length:
// src/state_sample.rs
if self.position as usize >= self.sample.len() {
   self.ping = false;
   self.position -= self.sample.len() as f32 - 1.0;
}

This is problematic because it can put position way before way before loop_start.
In my case loop_end ~= sample.len(), which now makes position < 1.0.
Because ping is now false, the other branch gets executed:
// src/state_sample.rs
if self.position as u32 <= self.sample.loop_start {
   self.ping = true;
   self.position = (self.sample.loop_start << 1) as f32 - self.position;
}

This part assumes position is pretty near loop_start.
Because now position is roughly 1.0, position now gets the value loop_start * 2 - 1.
No other safety checks are applied, so position can end up being much bigger than sample.len().
In my case, after position receives this value, Sample::at get called and the panic is triggered.
I have successfully tested this panic using CoreTex - Home while runing rodio_player.
The following command was used: RUST_BACKTRACE=1 cargo run --features demo --example rodio_player -- -f coretex_-_home.xm -p 48 -d
Channels 7 and 8 keep sample 7 alive past pattern 48, before pattern 49 is finished a panic will occurr.
I've found that applying the following change can fix the issue.
// src/state_sample.rs
if self.position as usize >= self.sample.len() {
   self.ping = false;
   self.position = self.sample.len() as f32 - 1.0;
}

This simply puts position at the end. Substracting 1.0 from it is required because how tricky f32 to/from u32 comversion behaves.
Omitting it can still put position after sample.len() after casting is applied.
It also has more sense because we're trying to put position in a place that allows playing the sample in reverse.

Hello Emmanuel,
I am sorry but I can't reproduce using your example: RUST_BACKTRACE=1 cargo run --features demo --example rodio_player -- -f coretex_-_home.xm -p 48 -d: no panic, no error.
I also look on original source code and it is the same.
Another idea to help me to reproduce?

Hi. Might be something related to environment. I am able to reproduce it when using JACK or ALSA directly under Ubuntu 22.04.
I've also noticed that it does not happen when using sample rates below 48khz. Of course, it might be my special case, maybe some hw latency involved.
I'm pasting my trace hoping someone else might find it useful if confronted with the same issue:
thread 'cpal_alsa_out' panicked at /home/xxx/.cargo/registry/src/index.crates.io-6f17d22bba15001f/xmrs-0.3.3/src/sample.rs:47:43:
index out of bounds: the len is 9319 but the index is 14205
stack backtrace:
   0: rust_begin_unwind
             at /rustc/a28077b28a02b92985b3a3faecf92813155f1ea1/library/std/src/panicking.rs:597:5
   1: core::panicking::panic_fmt
             at /rustc/a28077b28a02b92985b3a3faecf92813155f1ea1/library/core/src/panicking.rs:72:14
   2: core::panicking::panic_bounds_check
             at /rustc/a28077b28a02b92985b3a3faecf92813155f1ea1/library/core/src/panicking.rs:180:5
   3: <usize as core::slice::index::SliceIndex<[T]>>::index
             at /rustc/a28077b28a02b92985b3a3faecf92813155f1ea1/library/core/src/slice/index.rs:261:10
   4: core::slice::index::<impl core::ops::index::Index<I> for [T]>::index
             at /rustc/a28077b28a02b92985b3a3faecf92813155f1ea1/library/core/src/slice/index.rs:18:9
   5: <alloc::vec::Vec<T,A> as core::ops::index::Index<I>>::index
             at /rustc/a28077b28a02b92985b3a3faecf92813155f1ea1/library/alloc/src/vec/mod.rs:2728:9
   6: xmrs::sample::Sample::at
             at /home/xxx/.cargo/registry/src/index.crates.io-6f17d22bba15001f/xmrs-0.3.3/src/sample.rs:47:43
   7: xmrsplayer::state_sample::StateSample::tick
             at ./src/state_sample.rs:88:26
   8: <xmrsplayer::state_sample::StateSample as core::iter::traits::iterator::Iterator>::next
             at ./src/state_sample.rs:195:18
   9: <xmrsplayer::state_instr_default::StateInstrDefault as core::iter::traits::iterator::Iterator>::next
             at ./src/state_instr_default.rs:163:28
  10: <xmrsplayer::channel::Channel as core::iter::traits::iterator::Iterator>::next
             at ./src/channel.rs:909:24
  11: xmrsplayer::xmrsplayer::XmrsPlayer::sample
             at ./src/xmrsplayer.rs:344:19
  12: xmrsplayer::xmrsplayer::XmrsPlayer::generate_samples
             at ./src/xmrsplayer.rs:401:19
  13: <rodio_player::bufferedsource::BufferedSource as core::iter::traits::iterator::Iterator>::next
             at ./examples/bufferedsource.rs:53:13
  14: <rodio::source::speed::Speed<I> as core::iter::traits::iterator::Iterator>::next
             at /home/xxx/.cargo/registry/src/index.crates.io-6f17d22bba15001f/rodio-0.17.3/src/source/speed.rs:56:9
  15: <rodio::source::pausable::Pausable<I> as core::iter::traits::iterator::Iterator>::next
             at /home/xxx/.cargo/registry/src/index.crates.io-6f17d22bba15001f/rodio-0.17.3/src/source/pausable.rs:85:9
  16: <rodio::source::amplify::Amplify<I> as core::iter::traits::iterator::Iterator>::next
             at /home/xxx/.cargo/registry/src/index.crates.io-6f17d22bba15001f/rodio-0.17.3/src/source/amplify.rs:56:9
  17: <rodio::source::skippable::Skippable<I> as core::iter::traits::iterator::Iterator>::next
             at /home/xxx/.cargo/registry/src/index.crates.io-6f17d22bba15001f/rodio-0.17.3/src/source/skippable.rs:58:13
  18: <rodio::source::stoppable::Stoppable<I> as core::iter::traits::iterator::Iterator>::next
             at /home/xxx/.cargo/registry/src/index.crates.io-6f17d22bba15001f/rodio-0.17.3/src/source/stoppable.rs:57:13
  19: <rodio::source::periodic::PeriodicAccess<I,F> as core::iter::traits::iterator::Iterator>::next
             at /home/xxx/.cargo/registry/src/index.crates.io-6f17d22bba15001f/rodio-0.17.3/src/source/periodic.rs:86:9
  20: <rodio::source::samples_converter::SamplesConverter<I,D> as core::iter::traits::iterator::Iterator>::next
             at /home/xxx/.cargo/registry/src/index.crates.io-6f17d22bba15001f/rodio-0.17.3/src/source/samples_converter.rs:56:9
  21: <rodio::source::done::Done<I> as core::iter::traits::iterator::Iterator>::next
             at /home/xxx/.cargo/registry/src/index.crates.io-6f17d22bba15001f/rodio-0.17.3/src/source/done.rs:53:20
  22: <alloc::boxed::Box<I,A> as core::iter::traits::iterator::Iterator>::next
             at /rustc/a28077b28a02b92985b3a3faecf92813155f1ea1/library/alloc/src/boxed.rs:1941:9
  23: <rodio::queue::SourcesQueueOutput<S> as core::iter::traits::iterator::Iterator>::next
             at /home/xxx/.cargo/registry/src/index.crates.io-6f17d22bba15001f/rodio-0.17.3/src/queue.rs:184:35
  24: <rodio::source::uniform::Take<I> as core::iter::traits::iterator::Iterator>::next
             at /home/xxx/.cargo/registry/src/index.crates.io-6f17d22bba15001f/rodio-0.17.3/src/source/uniform.rs:159:17
  25: rodio::conversions::sample_rate::SampleRateConverter<I>::next_input_frame
             at /home/xxx/.cargo/registry/src/index.crates.io-6f17d22bba15001f/rodio-0.17.3/src/conversions/sample_rate.rs:111:30
  26: <rodio::conversions::sample_rate::SampleRateConverter<I> as core::iter::traits::iterator::Iterator>::next
             at /home/xxx/.cargo/registry/src/index.crates.io-6f17d22bba15001f/rodio-0.17.3/src/conversions/sample_rate.rs:160:17
  27: <rodio::conversions::channels::ChannelCountConverter<I> as core::iter::traits::iterator::Iterator>::next
             at /home/xxx/.cargo/registry/src/index.crates.io-6f17d22bba15001f/rodio-0.17.3/src/conversions/channels.rs:62:13
  28: <rodio::conversions::sample::DataConverter<I,O> as core::iter::traits::iterator::Iterator>::next
             at /home/xxx/.cargo/registry/src/index.crates.io-6f17d22bba15001f/rodio-0.17.3/src/conversions/sample.rs:38:9
  29: <rodio::source::uniform::UniformSourceIterator<I,D> as core::iter::traits::iterator::Iterator>::next
             at /home/xxx/.cargo/registry/src/index.crates.io-6f17d22bba15001f/rodio-0.17.3/src/source/uniform.rs:88:30
  30: <alloc::boxed::Box<I,A> as core::iter::traits::iterator::Iterator>::next
             at /rustc/a28077b28a02b92985b3a3faecf92813155f1ea1/library/alloc/src/boxed.rs:1941:9
  31: rodio::dynamic_mixer::DynamicMixer<S>::sum_current_sources
             at /home/xxx/.cargo/registry/src/index.crates.io-6f17d22bba15001f/rodio-0.17.3/src/dynamic_mixer.rs:170:34
  32: <rodio::dynamic_mixer::DynamicMixer<S> as core::iter::traits::iterator::Iterator>::next
             at /home/xxx/.cargo/registry/src/index.crates.io-6f17d22bba15001f/rodio-0.17.3/src/dynamic_mixer.rs:125:19
  33: <cpal::platform::platform_impl::Device as rodio::stream::CpalDeviceExt>::new_output_stream_with_format::{{closure}}::{{closure}}
             at /home/xxx/.cargo/registry/src/index.crates.io-6f17d22bba15001f/rodio-0.17.3/src/stream.rs:219:44
  34: <core::slice::iter::IterMut<T> as core::iter::traits::iterator::Iterator>::for_each
             at /rustc/a28077b28a02b92985b3a3faecf92813155f1ea1/library/core/src/slice/iter/macros.rs:254:21
  35: <cpal::platform::platform_impl::Device as rodio::stream::CpalDeviceExt>::new_output_stream_with_format::{{closure}}
             at /home/xxx/.cargo/registry/src/index.crates.io-6f17d22bba15001f/rodio-0.17.3/src/stream.rs:218:21
  36: cpal::traits::DeviceTrait::build_output_stream::{{closure}}
             at /home/xxx/.cargo/registry/src/index.crates.io-6f17d22bba15001f/cpal-0.15.2/src/traits.rs:169:17
  37: cpal::host::alsa::process_output
             at /home/xxx/.cargo/registry/src/index.crates.io-6f17d22bba15001f/cpal-0.15.2/src/host/alsa/mod.rs:836:9
  38: cpal::host::alsa::output_stream_worker
             at /home/xxx/.cargo/registry/src/index.crates.io-6f17d22bba15001f/cpal-0.15.2/src/host/alsa/mod.rs:671:35
  39: cpal::host::alsa::Stream::new_output::{{closure}}
             at /home/xxx/.cargo/registry/src/index.crates.io-6f17d22bba15001f/cpal-0.15.2/src/host/alsa/mod.rs:965:17
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.
Have a nice day!
thread 'main' panicked at /home/xxx/.cargo/registry/src/index.crates.io-6f17d22bba15001f/cpal-0.15.2/src/host/alsa/mod.rs:145:9:
assertion `left == right` failed
  left: -1
 right: 8
stack backtrace:
   0: rust_begin_unwind
             at /rustc/a28077b28a02b92985b3a3faecf92813155f1ea1/library/std/src/panicking.rs:597:5
   1: core::panicking::panic_fmt
             at /rustc/a28077b28a02b92985b3a3faecf92813155f1ea1/library/core/src/panicking.rs:72:14
   2: core::panicking::assert_failed_inner
   3: core::panicking::assert_failed
             at /rustc/a28077b28a02b92985b3a3faecf92813155f1ea1/library/core/src/panicking.rs:270:5
   4: cpal::host::alsa::TriggerSender::wakeup
             at /home/xxx/.cargo/registry/src/index.crates.io-6f17d22bba15001f/cpal-0.15.2/src/host/alsa/mod.rs:145:9
   5: <cpal::host::alsa::Stream as core::ops::drop::Drop>::drop
             at /home/xxx/.cargo/registry/src/index.crates.io-6f17d22bba15001f/cpal-0.15.2/src/host/alsa/mod.rs:984:9
   6: core::ptr::drop_in_place<cpal::host::alsa::Stream>
             at /rustc/a28077b28a02b92985b3a3faecf92813155f1ea1/library/core/src/ptr/mod.rs:497:1
   7: core::ptr::drop_in_place<cpal::platform::platform_impl::StreamInner>
             at /rustc/a28077b28a02b92985b3a3faecf92813155f1ea1/library/core/src/ptr/mod.rs:497:1
   8: core::ptr::drop_in_place<cpal::platform::platform_impl::Stream>
             at /rustc/a28077b28a02b92985b3a3faecf92813155f1ea1/library/core/src/ptr/mod.rs:497:1
   9: core::ptr::drop_in_place<rodio::stream::OutputStream>
             at /rustc/a28077b28a02b92985b3a3faecf92813155f1ea1/library/core/src/ptr/mod.rs:497:1
  10: rodio_player::rodio_play
             at ./examples/rodio_player.rs:117:1
  11: rodio_player::main
             at ./examples/rodio_player.rs:63:21
  12: core::ops::function::FnOnce::call_once
             at /rustc/a28077b28a02b92985b3a3faecf92813155f1ea1/library/core/src/ops/function.rs:250:5
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.

Thank you.
Can you try again with the last crate.io version?
I listen CoreTex - Home with Fast Tracker II clone. It seems there is a bug with volume sutain on point 2 (first instr) too :(

Hi. Updated to latest versions. Tried the same use case. I am not experiencing any issue during playback. Played the same track back and fort. Everything seems to be ok. Thank you very much.

Ok, thank you.


🐛 [Bug] backend Tests Flaky

🐛 Bug

Backend test can fail for unknown reason: https://github.com/dreammall-earth/dreammall.earth/actions/runs/8241168363/job/22537888687?pr=329

Decoupling Issue?
Wait for all timers?

Is this still an issue? Did someone observe this in the last weeks?


build-essential: "libncurses-dev" on debian

Signed-off-by: Isa Farnik<EMAIL_ADDRESS>ncurses-dev on modern debian platforms is a virtual package that causes chef running the build_essential resource to choke.
Description

Related Issue
https://github.com/chef-boneyard/build-essential/issues/137
Types of changes

[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[x] Breaking change (fix or feature that would cause existing functionality to change)
[ ] Chore (non-breaking change that does not add functionality or fix an issue)

Checklist:

[x] I have read the CONTRIBUTING document.
[x] I have run the pre-merge tests locally and they pass.
[ ] I have updated the documentation accordingly.
[ ] I have added tests to cover my changes.
[ ] All new and existing tests passed.
[ ] All commits have been signed-off for the Developer Certificate of Origin.

@curiositycasualty
Two questions:

What exactly does chef-client do with the virtual package

Do all supported versions of Debian / Ubuntu include this package?

@tas50
Drew an ugly and long vagrant/bento shell command to run in the background. Note the Note, selecting in the apt-get install output.
for platform in ubuntu-{18,20}.04 debian-{10.4,10.3,9.12}; do
  dir=$(mktemp -d);
  pushd $dir;
  vagrant init "bento/${platform}";
  vagrant up;
  vagrant ssh -c 'set -x;
    sudo apt-get update;
    sudo apt-cache policy ncurses-dev;
    set +x;
    curl -L https://omnitruck.chef.io/install.sh | sudo bash -s -- -v 14;
    set -x;
    sudo chef-apply -e "build_essential";
    sudo apt-cache policy ncurses-dev;
    sudo apt-get install ncurses-dev';
  vagrant destroy --force;
  popd;
done

bento/ubuntu-18.04:
+ sudo chef-apply -e build_essential
Recipe: (chef-apply cookbook)::(chef-apply recipe)
  * build_essential[] action install
    * apt_package[autoconf, binutils-doc, bison, build-essential, flex, gettext, ncurses-dev] action install
      - install version 2.69-11 of package autoconf
      - install version 2.30-21ubuntu1~18.04.3 of package binutils-doc
      - install version 2:3.0.4.dfsg-1build1 of package bison
      - install version 12.4ubuntu1 of package build-essential
      - install version 2.6.4-6 of package flex
      - install version <IP_ADDRESS>-6ubuntu0.3 of package gettext
      - install version 6.1-1ubuntu1.18.04 of package ncurses-dev

+ sudo apt-cache policy ncurses-dev
ncurses-dev:
  Installed: (none)
  Candidate: (none)
  Version table:
+ sudo apt-get install ncurses-dev
Reading package lists... Done
Building dependency tree
Reading state information... Done
Note, selecting 'libncurses5-dev' instead of 'ncurses-dev'
libncurses5-dev is already the newest version (6.1-1ubuntu1.18.04).
0 upgraded, 0 newly installed, 0 to remove and 48 not upgraded.

bento/ubuntu-20.04:
+ sudo chef-apply -e build_essential
Recipe: (chef-apply cookbook)::(chef-apply recipe)
  * build_essential[] action install
    * apt_package[autoconf, binutils-doc, bison, build-essential, flex, gettext, ncurses-dev] action install
      - install version 2.69-11.1 of package autoconf
      - install version 2.34-6ubuntu1 of package binutils-doc
      - install version 2:3.5.1+dfsg-1 of package bison
      - install version 12.8ubuntu1 of package build-essential
      - install version 2.6.4-6.2 of package flex
      - install version <IP_ADDRESS>-10build1 of package gettext

+ sudo apt-cache policy ncurses-dev
ncurses-dev:
  Installed: (none)
  Candidate: (none)
  Version table:
+ sudo apt-get install ncurses-dev
Reading package lists... Done
Building dependency tree
Reading state information... Done
Note, selecting 'libncurses-dev' instead of 'ncurses-dev'
libncurses-dev is already the newest version (6.2-0ubuntu2).
libncurses-dev set to manually installed.
0 upgraded, 0 newly installed, 0 to remove and 69 not upgraded.

bento/debian-10.4:
+ sudo chef-apply -e build_essential
Recipe: (chef-apply cookbook)::(chef-apply recipe)
  * build_essential[] action install
    * apt_package[autoconf, binutils-doc, bison, build-essential, flex, gettext, ncurses-dev] action install
      - install version 2.69-11 of package autoconf
      - install version 2.31.1-16 of package binutils-doc
      - install version 2:3.3.2.dfsg-1 of package bison
      - install version 12.6 of package build-essential
      - install version 2.6.4-6.2 of package flex
      - install version <IP_ADDRESS>-9 of package gettext
      - install version 6.1+20181013-2+deb10u2 of package ncurses-dev

+ sudo apt-cache policy ncurses-dev
ncurses-dev:
  Installed: (none)
  Candidate: (none)
  Version table:
+ sudo apt-get install ncurses-dev
Reading package lists... Done
Building dependency tree
Reading state information... Done
Note, selecting 'libncurses-dev' instead of 'ncurses-dev'
libncurses-dev is already the newest version (6.1+20181013-2+deb10u2).
0 upgraded, 0 newly installed, 0 to remove and 4 not upgraded.

bento/debian-10.3:
+ sudo chef-apply -e build_essential
Recipe: (chef-apply cookbook)::(chef-apply recipe)
  * build_essential[] action install
    * apt_package[autoconf, binutils-doc, bison, build-essential, flex, gettext, ncurses-dev] action install
      - install version 2.69-11 of package autoconf
      - install version 2.31.1-16 of package binutils-doc
      - install version 2:3.3.2.dfsg-1 of package bison
      - install version 12.6 of package build-essential
      - install version 2.6.4-6.2 of package flex
      - install version <IP_ADDRESS>-9 of package gettext
      - install version 6.1+20181013-2+deb10u2 of package ncurses-dev

+ sudo apt-cache policy ncurses-dev
ncurses-dev:
  Installed: (none)
  Candidate: (none)
  Version table:
+ sudo apt-get install ncurses-dev
Reading package lists... Done
Building dependency tree
Reading state information... Done
Note, selecting 'libncurses-dev' instead of 'ncurses-dev'
libncurses-dev is already the newest version (6.1+20181013-2+deb10u2).

bento/debian-9.12:
+ sudo chef-apply -e build_essential
Recipe: (chef-apply cookbook)::(chef-apply recipe)
  * build_essential[] action install
    * apt_package[autoconf, binutils-doc, bison, build-essential, flex, gettext, ncurses-dev] action install
      - install version 2.69-10 of package autoconf
      - install version 2.28-5 of package binutils-doc
      - install version 2:3.0.4.dfsg-1+b1 of package bison
      - install version 12.3 of package build-essential
      - install version 2.6.1-1.3 of package flex
      - install version <IP_ADDRESS>-2+deb9u1 of package gettext
      - install version 6.0+20161126-1+deb9u2 of package ncurses-dev

+ sudo apt-cache policy ncurses-dev
ncurses-dev:
  Installed: (none)
  Candidate: (none)
  Version table:
+ sudo apt-get install ncurses-dev
Reading package lists... Done
Building dependency tree
Reading state information... Done
Note, selecting 'libncurses5-dev' instead of 'ncurses-dev'
libncurses5-dev is already the newest version (6.0+20161126-1+deb9u2).

@curiositycasualty Is that package around on 16.04?

I think there may be more at play to this than just the chef-client's build_essential resource... I'll re-open this issue if I figure out it's solely chef that's the issue.

bento/ubuntu-16.04:
+ sudo chef-apply -e build_essential
Recipe: (chef-apply cookbook)::(chef-apply recipe)
  * build_essential[] action install
    * apt_package[autoconf, binutils-doc, bison, build-essential, flex, gettext, ncurses-dev] action install
      - install version 2.69-9 of package autoconf
      - install version 2.26.1-1ubuntu1~16.04.8 of package binutils-doc
      - install version 2:3.0.4.dfsg-1 of package bison
      - install version 12.1ubuntu2 of package build-essential
      - install version 2.6.0-11 of package flex
      - install version 0.19.7-2ubuntu3.1 of package gettext
      - install version 6.0+20160213-1ubuntu1 of package ncurses-dev

+ sudo apt-cache policy ncurses-dev
ncurses-dev:
  Installed: (none)
  Candidate: (none)
  Version table:
+ sudo apt-get install ncurses-dev
Reading package lists... Done
Building dependency tree
Reading state information... Done
Note, selecting 'libncurses5-dev' instead of 'ncurses-dev'
libncurses5-dev is already the newest version (6.0+20160213-1ubuntu1).
0 upgraded, 0 newly installed, 0 to remove and 30 not upgraded.

FWIW: all of the above platforms do accept libncurses-dev and redirect to libncurses5-dev as needed.


[UI] Registry: Same model count is reported for each Registrant

Current Behavior
All registrants have the same model count.
Expected Behavior
The model counts in parentheses should not be the same between registrants.
https://playground.meshery.io/api/meshmodels/registrants
This endpoint is intended to display the count.
Screenshots/Logs

Environment

Host OS: Mac Linux Windows
Platform: Docker or Kubernetes
Meshery Server Version: stable-v
Meshery Client Version: stable-v

Contributor Guides and Handbook

🎨 Wireframes and designs for Meshery UI in Figma (open invite)
🖥 Contributing to Meshery UI
🙋🏾🙋🏼 Questions: Discussion Forum and Community Slack

I want to work on this, @leecalcote can you please assign me

@prachinandi, sounds great. Thanks much for jumping in and volunteering. In an effort to help guarantee your success in undertaking assignment of the issue, will you:

confirm that you're able to build the project, specifically, the components necessary to resolve this issue.
confirm the approach you intend to take to resolve the issue.

Yes @leecalcote I have almost set up the project locally, have some issues in build trying to resolve it actually.
And regarding the approach I think it might be a simple fix. If the API is returning correct model count the issue might be in the frontend in displaying this data. (Chances that the data mapped from API to frontend is incorrect not sure).
If the issue is with API then need to check the backend logic, that if you can confirm that what response are we getting?

I got this issue "unable to download meshery.tar.gz file from https://github.com/meshery/meshery/releases/download/v0.7.114/mesheryctl_0.7.114_Darwin_arm64.tar.gz. Set MESHERY_VERSION environment variable to a different version and re-run. For example: export MESHERY_VERSION=v0.1.6" when I try to deploy in docker

@leecalcote if no one working, i would like to take this one.

I think it will have to display the model count according to model count mentioned in summary for that individual registrant(e.g-534 for Artifact Hub) in advance details section which is the fetched data.But it is mentioning the global count of model which is common for all the registrants making them all same.
Let me know if I am wrong anywhere.

@Aryan4884 how's your Golang and your React? Are you comfortable with both or one more than the next or neither?

@prachinandi, my apologies, I completely missed your prior messages. Do post on https://discuss.layer5.io, if you're still experiencing challenges getting setup.

@leecalcote I have an experience of 1.5 years in React and a beginner in Golang.

@Aryan4884, ok, very good. Depending upon what you find, it might be the API (golang) that needs ultimately enhanced or it might just be the client's handling of the responses. Aggregation and computation should be (must be) handled server-side. Let me (and the other contributors) know what you find. 👍

@Aryan4884 whats the progress? Its an urgent item.

@Yashsharma1911, help, help. 🙏

@leecalcote Sorry for inconvenience caused ,wasn't aware that this issue is an urgent one. I am new to the codebase and having little hard time in getting it in (making changes without conflict errors ).I will let u know as soon as I make any progress.In the mean time, since its an urgent one ,u may unassign me and assign others who can solve this quickly.

@leecalcote if you allow me i can resolve this issue

@leecalcote  i tried to resolve this  issue the problem is that each registrants type has some models count but this models count contains the data of all types of registrants. so i have filtered the models  based on the kind(artifacthub,meshery and etc...)  of the registrants. so it is showing correct result.
screenshot

@leecalcote @sudhanshutech should i
proceed with the solution or not??

@leecalcote @sudhanshutech please assign this to me.

@leecalcote i tried to resolve this issue the problem is that each registrants type has some models count but this models count contains the data of all types of registrants. so i have filtered the models based on the kind(artifacthub,meshery and etc...) of the registrants. so it is showing correct result.
screenshot

Thanks, everyone for raising your hand on this issue, @kingdarabahmad incase you have changes already please feel free to raise a quick PR for review and if possible by today.
Considering the urgency, I'll start working on this issue by this morning or afternoon in case we don't get a response.


AeroDyn_Driver_x64.exe Function

Hello, Professor,
Is there a method to achieve co-simulation for real-time interaction between AeroDyn_Driver_x64.exe and other software?

Dear @wkdanqu1,
The AeroDyn module can be called by other software (such as OpenFAST).  AeroDyn is not typically the computational bottleneck in the aero-elastic solve if your goal is real-time simulation, unless you are using the free-vortex wake OLAF.  Whether real-time simulation is available depends on the capabilities of the calling software.
FYI: The standalone AeroDyn driver is a simple wrapper to call AeroDyn in the absence of other software that would drive the solution.  So, if AeroDyn is called by other software (such as OpenFAST), the standalone AeroDyn driver is not used in that case.
Best regards,

Hello, Professors,
This has been very helpful for me. I will proceed with further real-time simulation development following your method!
Thank you again for your assistance!
Best regards,
Jesse

Hello  Professors @andrew-platt @jjonkman,
I hope this message find you well !
In the code for calculating Output in the aerodyn_inflow_library.py, it requires motion parameters for the Hub, Nacelle, root, and mesh. The example folder vtkRef also provides parameters stored in .vtp files.
However, my hydrodynamic calculation software can only provide motion parameters for the floating platform! Is there a way to obtain the motion parameters for the Hub, Nacelle, root, and mesh using the floating platform's motion parameters? Or is there a method that only requires the input of the floating platform's motion parameters?
Best regards,
Jesse