Two small issues in the VAD->ASR pipeline processing

Hello again. I've been playing with Rhasspy3 over the course of last several days and I found few small issues.
For a beginning, here's my pipeline, pretty standard, all the programs settings are default as per your tutorial. The only small diff here is that I swapped whisper for vosk to try it out some additional ASR models:
pipelines:
  default:
    mic:
      name: arecord
    wake:
      name: porcupine1
    vad:
      name: silero
    asr:
      name: vosk.client
    handle:
      name: repeat
    tts:
      name: piper.client
    snd:
      name: aplay

Issue number one - the silero-vad sensitivity? other VADs?
When the wake step is activated (by me saying a wake word to microphone), it sometimes happens that VAD (silero) is unable to capture me speaking, so the pipeline is keep hanging on that step unit the timeout from VAD. It could be because my microphone is noisy. Or I was just speaking too quiet. Or the default threshold of silero-vad is just a bit too low for my setup.
I guess, I'm not the only one who'll be playing with Rhasspy3 while using questionable quality microphones, with a constant background humming tone heard on records from such microphones :) so I was trying to find some ways to configure silero-vad to make it more sensitive but it looks like there're no such settings exposed to configuration.yaml right now. So this one is more like a gentle low priority feature request. In my particular case, I think I should just invest some bucks into some more decent mic compared to what I have now, prob an electret one.
Then I tried to swap silero-vad with something different. There are two other VADs Rhasspy3 is shipped with: energy and webrtcvad and I seen both of them are having some kind of sensitivity configurable in the configuration. I used similar steps as in your tutorial to get them installed, but as soon as I plug them into pipeline it starts to spill error messages on me. It looks like they're not quite ready, right? Or was it just me doing something wrong? I'm happy to dig more into that myself, if you tell me that both energy and webrtcvad are working out of the box.
Issue number two - even if VAD wasn't triggered, the captured PCM is still sent downwards to the pipe to ASR
Consider this scenario:

saying a wakeword loud
seeing the pipeline went to the point of VAD
silently whispering something, without triggering VAD
seeing VAD is not being activated
after a timeout from VAD (something like 10-15 seconds I guess), whatever audio was captured by microphone is still sent to ASR and then the recognized text is sent to HANDLER.

The issue, as I see it, in the point 5. If VAD is presenting in the pipeline configuration (it is mandatory right now I guess), but it wasn't triggered for whatever reason, after the timeout happens the pipeline shouldn't be sending captured audio down to ASR, because otherwise - what's the point of having VAD here? :) If someone still needs this kind of behavior to send PCM to ASR even without VAD being triggered, I guess it can be made configurable from the configuration.yaml perspective.
That's it so far. Again - great piece of software!

Btw I do have created a  Dockerfile and simple bash file that detects what kind of setup your host is having (Pulse / Pipewire) and creates a proper docker image with Rhasspy3 preconfigured and spins up a container out of it. I'm still polishing it, will take me few days, but once I'm done I'll share it for sure


ContentViewTwo and ContentViewThree causing issues in test App

Hi,
I tried to run the Test App but it didn't work at first ... I got a bunch of errors and had to delete ContentViewTwo and ContentViewThree to make it work
Maybe these need to be removed from the project file?
Thanks

Thanks @htonkovac I will take a look at this today, not sure why that is causing issues.

This should be fixed in latest version release.


Use faster conda clone based method for all setup

Make the speedup #548 apply to all environment setup.

Probably gonna go with per-instance docker images instead of env setup similar to new swe-bench next, so this might not be relevant anymore


Updated node tests

Creating this PR with changes for updated versions of node to see if this will fix the vercel deployment issue.
Notes:

If deployed, then need to check if right click functionality still works. After testing with different PC's I have noticed that on my PC right-click doesn't work even with fresh clone from stage.
Removed cypress.yml file just for testing. Currently there are a few errors that are failing the cypress tests, but they weren't related to core functionality (related to panning) and I have been unable to solve them so far which is why I am removing the cypress file just to see if this version of EWOD can properly be deployed to vercel. Will keep on working to debug these errors.

Here are the errors shown in Vercel:

Let me know if you need more information from Vervel to troubleshoot.

Hey Leo,
Is there any way you could give access for Vercel to me? I think the error
is that I have to define the node version somewhere in the github or
vercel, so i’ll look into it tomorrow.
Nikhil Gupta
On Tue, Nov 12, 2024 at 12:01 AM Leo @.***> wrote:

Here are the errors shown in Vercel:
image.png (view on web)
https://github.com/user-attachments/assets/86467e11-f9fb-417b-a80f-f1f089b8cf31
Let me know if you need more information from Vervel to troubleshoot.
—
Reply to this email directly, view it on GitHub
https://github.com/leofuturer/EWOD-GUI2.0/pull/314#issuecomment-2469834716,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/APK2I2YI3YJMJ7SOZFOJSRT2AGYU5AVCNFSM6AAAAABRTKUG5OVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDINRZHAZTINZRGY
.
You are receiving this because you authored the thread.Message ID:
@.***>

Sure. Just added your email to the Vercel account. You should receive a verification email. Let me know if you can not access it.


Integration of Code Coverage Utility with Github & test case fixes

PR contains a fix for CQ-4320891 Integration of Code Coverage Utility with Github & failing test cases fixes. Since this is a monorepo, we need to set up flags for codecov & cd into each directory upload coverage.
Description

Related Issue

Motivation and Context

How Has This Been Tested?

Screenshots (if appropriate):
Types of changes

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

Checklist:

[ ] I have signed the Adobe Open Source CLA.
[ ] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[ ] I have read the CONTRIBUTING document.
[ ] I have added tests to cover my changes.
[ ] All new and existing tests passed.

@ukgaurav, sure! actually, for now, I am making this whole integration work, since it is monorepo there are a few challenges and hence I am keeping PR's simple to make sure it works. this PR also contains a fix for the failing test cases which is halting the npm publish push. For anything else, I will create subtask to accomplish them! let me know your thoughts.


default open tcp_nodelay with harbor model

fix #763

fix #763

See https://github.com/cloudwu/skynet/commit/b51e28a3e0fadccaa1d4040fd2aac588176db8d6


Collect better place types using OSM and move type assignment later within the script

If OSM has a result for a search query, the metadata looks like this:
Salvador Allende, Villa Victoria, Surquillo, Province of Lima, Lima Metropolitan Area, Lima, 15000, Peru
We can make use of data-prefix to classify places into streets, schools, monuments, etc. We just have to find out what kinds of data-prefixes are possible in OSM, then add more keywords to the dictionary of lists where the type assignment is based from.
This requires moving the type assignment process later in the script so that we don't have to override what's already in the DataFrame. In effect, we would collect type the same way we collect locale_2, locale_3, etc.
    #
    # get TYPE
    # the dict used here is pretty rudimentary so this is prone to errors and needs human verification
    #
    type = ''
    for key, value in types.items():
        for type_item in value:
            if type_item in name.lower():
                type = key
    data['type'].append(type)
    print(f'Type: {type}')

Done for single-locale links.
    #
    # get TYPE
    # the dict used here is pretty rudimentary so this is prone to errors and needs human verification
    #
    type = ''
    # get OSM type if available
    try:
        type = re.search(r'data-prefix="(.*?)"', osm_info)
        type = str(type.group(1))
    except:
        # if not, derive it from NAME (which itself is either from OSM or the article)
        for key, value in types.items():
            for type_item in value:
                if type_item in name.lower():
                    type = key
    else:
        for key, value in types.items():
            for type_item in value:
                if type_item in type.lower():
                    type = key
    data['type'].append(type)
    print(f'Type: {type}')

Also done for multi-locale links using the same snippet. Tested to work on Algeria and Peru.
(Bonus: I also found out that .xlsx supports Unicode and .csv doesn't, so changing the output file format to .xlsx eliminates the encoding fiascos.)


[Relay][Runtime] Add set_input/output_zero_copy in python

As titled, this apis is in cpp but not python. Added this apis for GraphModule and some tests.
cc: @vinx13

@tvm-bot re-run


Url to access task only using its id

Hi
Would it be possible to add an url to access task only using their task ID ? I see no reason to use the project's id in the url, afaik tasks are numbered kanboard-wise.
Thanks & regards

You can use http://domain.tld/t/123 to access to the task id #123

Oh perfect, thanks !


Add a line for Oboe sample's README.md to update Oboe source code

just add a line inside readme.md for https://github.com/googlesamples/android-audio-high-performance/issues/112.

Gerry - hope you don't mind but I reworded your update. Thanks for doing this - made it easy to make the change.


Crash opening options from main menu

Using latest 1.7.2 release with the included dinput8.ini & clean 1.1.0 bio4.exe, game crashes when opening options menu - removing dinput8.dll allows it to open it fine though, so don't think it's an issue with my games config.ini or anything.
Log file:
bio4.exe.20220129221113.log
Seems to be something to do with the resolution chooser again, I used NV control panel to add 90Hz option for my resolution, so I have both 90Hz & 60Hz for the same res, maybe that's something to do with it (my desktop is at 90Hz, but maybe it's only exposing 60Hz to D3D or something weird)

Oh boy.
I'll see if I can create a virtual display to reproduce the crash. My actual monitor can't handle anything above 63Hz or so :/
But 144Hz did work when I first tried this. Not sure what could be wrong now.

Have you tried it with 63Hz in game? If your desktop is running at 63Hz maybe that's enough for it to trigger the crash, if it is an issue with desktop & D3D having a mismatch.

Hmm, weird. Tried both with 63Hz on my real monitor and with 90Hz on my fake monitor. No crashes here.

Probably should have mentioned but I have two monitors connected - unplugged one of them, and the crash went away, weird. Could it be using EnumDisplayModes on the wrong monitor maybe? Only one of them had 90Hz custom resolution added (both are same resolution besides that)

Ah, two monitors? Time for me to create another virtual display then

Wrote a quick app to run EnumAdapterModes, and seems 90Hz modes are missing for adapter 0...
#0 - 640x480@59
#1 - 640x480@60
#2 - 720x480@59
#3 - 720x480@60
#4 - 720x576@59
#5 - 720x576@60
#6 - 800x600@59
#7 - 800x600@60
#8 - 1024x768@59
#9 - 1024x768@60
#10 - 1152x864@59
#11 - 1152x864@60
#12 - 1280x720@59
#13 - 1280x720@60
#14 - 1280x768@59
#15 - 1280x768@60
#16 - 1280x800@59
#17 - 1280x800@60
#18 - 1280x960@59
#19 - 1280x960@60
#20 - 1280x1024@59
#21 - 1280x1024@60
#22 - 1360x768@59
#23 - 1360x768@60
#24 - 1366x768@59
#25 - 1366x768@60
#26 - 1600x900@59
#27 - 1600x900@60
#28 - 1600x1024@59
#29 - 1600x1024@60
#30 - 1600x1200@59
#31 - 1600x1200@60
#32 - 1680x1050@59
#33 - 1680x1050@60
#34 - 1920x1080@59
#35 - 1920x1080@60
#36 - 1920x1200@59
#37 - 1920x1200@60
#38 - 1920x1440@59
#39 - 1920x1440@60
#40 - 2560x1440@59
#41 - 2560x1440@60

Strangely it seems adapter 0 is actually my 90Hz display though, using adapter 1 it gives portrait resolutions since the non-90Hz screen is in portrait.
No idea why D3D isn't seeing the 90Hz display... I guess this shows there is a chance the desktop refresh rate & the d3d rates could be different though, maybe need to add something to handle that somehow.

I see.

No idea why D3D isn't seeing the 90Hz display...

Could this be due to how nvidia is forcing the non-standard refresh rate? If so, no one with a "normal" setup should face this issue.

E: hmm.. this doesn't explain why unplugging second monitor stopped it from crashing though, even with it unplugged I get the same modes from EnumAdapterModes... how does the game work with that though? strange.

Could the game be trying to run EnumAdapterModes on the secondary monitor instead of the first one? If so, this would end up making the list empty since it is then looking for resolutions with g_UserRefreshRate, and those are only available in the first monitor.
Would explain why some people actually fix the black screen issue by simply plugging in a 60Hz monitor. And we're just doing.. the inverse, I guess.

Don't really think the second monitor is related with this, neither adapters seemed to include the 90Hz mode anyway, I guess NV just isn't setting D3D9 modes up properly for it (I do remember some other games having issues with this too).
Only way I can think of for getting around this would be to maybe ignore refresh rate in the func that populates the resolution list - I don't really think refresh rate is that important for that code anyway, seems like they might have only limited it to 60Hz there to prevent duplicates (since some people have both 59 & 60 modes for the same resolutions), could be wrong though.
Would probably need to reimplement that func so it could check for dupe width/height combinations instead though... luckily it's not too complex, maybe will try looking into it soon.

Oh wow, the game actually already has code for checking by width/height instead of refresh rate, but it's unused :o
The check at 0x953513 is checking if a2 == true, but none of the calls to that func set that to true, changing that jnz to jmp instead lets it check for dupes properly, with that it seems to work with 90Hz fine!

Nice find!

Wonder why they left that unused.

I mean, why even force 60Hz in the first place? Makes no sense at all. I mean, Q-LOC isn't really incompetent, but I really don't understand what they were thinking here.


Hit superfeng new 1

Hi,,
We cannot upload the zip file for licensing reasons. This file need to be downloaded from the IBM web after having accepted the license. Please remove this file from github. thx


Drop unused git submodules

I'm currently trying to build a flatpak for Lapce.
When downloading sources, flatpak-builder fails with the following error:
Fetching git repo https://github.com/lapce/glutin, ref refs/heads/new-keyboard-all
remote: Total 0 (delta 0), reused 0 (delta 0), pack-reused 0
Failed to download sources: module lapce: Not a gitlink tree: deps/apk-builder

It appears that flatpak-builder is picky when it comes to unused git submodules:
https://github.com/flatpak/flatpak-builder/issues/402#issuecomment-877774408
After adding "disable-submodules": true to the following sources, the flatpak builds without errors:
https://github.com/lapce/glutin
https://github.com/lapce/winit
Is it possible to remove apk-builder from .gitmodules in the mentioned repositories, since it seems to be unused anyway?

With the switch to druid, the affected repositories aren't used anymore in recent builds: https://github.com/lapce/lapce/pull/519


No module named 'MultiScaleDeformableAttention'

How should I deal with this problem

you should "sh make.sh" at DEFORABLE_DETR_ROOT/models/ops to build it

@May2333 Thank you for answering the questions.
@xinli-123 You need to compile the operators as described in README.

how can i solve this problem

 how can i solve this problem

Have you solved this problem?

how to install in the environment of "conda create -n pytorch python=3.8"?

 how can i solve this problem

i also met this problem, have you solved it?

no
At 2023-11-23 16:46:56, "ohhiohhi" @.***> wrote:
how can i solve this problem
i also met this problem, have you solved it?
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you commented.Message ID: @.***>


Please merge r43821 to trunk to fix pub heap errors.

This fixes issue #22413, in which pub was running out of memory with a heavy transformer load.
r43821 needs to be merged.
This merged cleanly with:
svn merge -c 43821 https://dart.googlecode.com/svn/branches/bleeding_edge
trunk

This issue has been moved to dart-lang/pub#1249.


Formalize agreements with technical partners

[x] Draft data storage and processing agreement
[x] Finalize technical partner service descriptions
[x] Review agreements
[x] Send documents to technical partners to sign and date

[x] Get signed agreement back from partner 1
[x] Get signed agreement back from partner 2

[x] Send physical copy to technical partners

Completed as of Nov. 2018.


Does not work with sizing_mode="stretch_both"

I'm on v0.1.0
It seems not to stretch its height
import pandas as pd
import panel as pn

from panel_gwalker import GraphicWalker

pn.extension(sizing_mode="stretch_width")

LOGO = "https://kanaries.net/_next/static/media/kanaries-logo.0a9eb041.png"

df = pd.read_csv(
    "https://datasets.holoviz.org/windturbines/v1/windturbines.csv.gz", nrows=10000
)

walker = GraphicWalker(df, sizing_mode="stretch_both", styles={"border": "1px solid yellow"})

pn.template.FastListTemplate(
    logo=LOGO,
    title="Panel Graphic Walker",
    main=[walker],
    main_layout=None,
).servable()

Needs to be fixed in graphic-walker. See https://github.com/Kanaries/graphic-walker/issues/421 and https://github.com/Kanaries/pygwalker/issues/645.


(Android) Game isn't running

I builded app via Visual Studio 2022 as release (version 1.0), signed it via random app because I don't know how to sign APK and game doesn't start

Sorry, I just forgot to zipalign APK


Running sfcc-sample-apps. Search fails when requesting a token

I've successfully followed the setup steps from the readme.
However when running it, I can't seam to be able to perform a search.

How to reproduce:

Follow the setup steps of the readme, run the app with yarn start:dev and open http://localhost:3000

In the Summer Look section, click on "Shop now", which should take you to take you to http://localhost:3000/search/Tops (see GIF recording)

The search returns no results because the request returned 404.

In the terminal, this error shows up:

storefront-lwc: Authorization Token has expired Response {
storefront-lwc:   size: 0,
storefront-lwc:   timeout: 0,
storefront-lwc:   [Symbol(Body internals)]: {
storefront-lwc:     body: Minipass {
storefront-lwc:       _events: [Object: null prototype],
storefront-lwc:       _eventsCount: 5,
storefront-lwc:       _maxListeners: undefined,
storefront-lwc:       pipes: [Yallist],
storefront-lwc:       buffer: [Yallist],
storefront-lwc:       writable: false,
storefront-lwc:       readable: true,
storefront-lwc:       [Symbol(kCapture)]: false,
storefront-lwc:       [Symbol(flowing)]: false,
storefront-lwc:       [Symbol(paused)]: false,
storefront-lwc:       [Symbol(objectMode)]: false,
storefront-lwc:       [Symbol(encoding)]: null,
storefront-lwc:       [Symbol(decoder)]: null,
storefront-lwc:       [Symbol(EOF)]: true,
storefront-lwc:       [Symbol(emittedEnd)]: false,
storefront-lwc:       [Symbol(emittingEnd)]: false,
storefront-lwc:       [Symbol(closed)]: false,
storefront-lwc:       [Symbol(bufferLength)]: 259,
storefront-lwc:       [Symbol(destroyed)]: false
storefront-lwc:     },
storefront-lwc:     disturbed: false,
storefront-lwc:     error: null
storefront-lwc:   },
storefront-lwc:   [Symbol(Response internals)]: {
storefront-lwc:     url: 'https://kv7kzm78.api.commercecloud.salesforce.com/customer/shopper-customers/v1/organizations/f_ecom_ZZGK_004/customers/actions/login?clientId=xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxxe&siteId=RefArch',
storefront-lwc:     status: 404,
storefront-lwc:     statusText: 'Not Found',
storefront-lwc:     headers: Headers { [Symbol(map)]: [Object: null prototype] },
storefront-lwc:     counter: 0,
storefront-lwc:     trailer: Promise { [Headers] }
storefront-lwc:   }
storefront-lwc: }
storefront-lwc: Error in requestWithTokenRefresh() ResponseError: 404 Not Found
storefront-lwc:     at Object.<anonymous> (/Users/youcefmammar/algolia/sfcc-sample-apps/node_modules/commerce-sdk/dist/helpers.js:36:13)
storefront-lwc:     at Generator.next (<anonymous>)
storefront-lwc:     at fulfilled (/Users/youcefmammar/algolia/sfcc-sample-apps/node_modules/tslib/tslib.js:110:62)
storefront-lwc:     at processTicksAndRejections (internal/process/task_queues.js:97:5) {
storefront-lwc:   response: Response {
storefront-lwc:     size: 0,
storefront-lwc:     timeout: 0,
storefront-lwc:     [Symbol(Body internals)]: { body: [Minipass], disturbed: false, error: null },
storefront-lwc:     [Symbol(Response internals)]: {
storefront-lwc:       url: 'https://kv7kzm78.api.commercecloud.salesforce.com/customer/shopper-customers/v1/organizations/f_ecom_ZZGK_004/customers/actions/login?clientId=xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxxe&siteId=RefArch',
storefront-lwc:       status: 404,
storefront-lwc:       statusText: 'Not Found',
storefront-lwc:       headers: [Headers],
storefront-lwc:       counter: 0,
storefront-lwc:       trailer: [Promise]
storefront-lwc:     }
storefront-lwc:   }
storefront-lwc: }

NB: I've replace the API client with xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx

Hey @tkrugg ,
A 404 typically indicates that your org/realm is incorrect and therefore not found. Can you please post this to the CCDC forums ( https://developer.commercecloud.com/s/ )? Someone there will be better equipped to answer this question.
Cheers,
Josh


Bug in creating database record with NN relationship

If using a NN relationship on create only (not update or both) the create will fail.
Issue with file
PanelTraits/Create.php
Line 26
$nn_relationships = array_pluck($this->getRelationFieldsWithPivot('update'), 'name');
Should be
$nn_relationships = array_pluck($this->getRelationFieldsWithPivot('create'), 'name');
Notice the change from update to create on the getRelationFieldsWithPivot method

Hi @splodgeco ,
I wasn't able to replicate your error, but I agree with you, it should definitely read CREATE fields, not UPDATE. So I've just pushed the fix on the dev branch. It will be available to you via composer update today or tomorrow, at the next patch release.
Thanks for the contribution and sorry if it caused you any stress :-)
Cheers!

Hi @tabacitu
Thanks for the fix. It didn't cause any stress, just a few hours of debugging trying to find out why it wasn't working in one situation!
Glad I can help.


Fix links in cloud files jod

Fixed links caused by upper case letters in filenames.

Fixed links in files in Cloud folder.
Removed references to qpacker.


[docs] Multiple release prep docs changes, fixes #4411

How this PR Solves The Problem:

See https://github.com/drud/ddev/issues/4452 - there were duplicate handling of WSL2 docker installation in the docker and DDEV installation sections.

PhpStorm WSL2 instructions update

Drupal 10 and Drupal 9 quickstart updates with release of Drupal 10

version_history.md update for release of v.1.21.4

#4411

Much shorter Docker installation sections for WSL2, with links

Manual Testing Instructions:
https://ddev--4456.org.readthedocs.build/en/4456/users/install/docker-installation/#windows
Automated Testing Overview:

Related Issue Link(s):
Release/Deployment notes:

Feedback on this will be welcome @mattstein but time to get this in for the release. Thanks!

Noted @rfay, sorry I missed the boat but I’ll follow on with a PR!


Support for device chaining

https://redocly.github.io/redoc/?url=https://raw.githubusercontent.com/open-traffic-generator/models/device_chain/artifacts/openapi.yaml
Support for device chaining:

def test_device_chaining(api):
    api = snappi.api()
    config = api.config()

    p1, p2 = config.ports.port(name='p1').port(name='p2')

    # Lag
    lag1 = config.lags.lag(name="lag1")[-1]
    lp1 = lag1.ports.port(port_name=p2.name)[-1]
    lp1.protocol.static.lag_id = 1
    lp1.ethernet.name = "lp1-e"
    lp1.ethernet.mac = "aa:aa:aa:aa:aa:aa"

    d1, d2, d3 = config.devices.device(name='d1').device(name='d2').device(name='d3')

    # connected to physical port
    e1 = d1.ethernets.ethernet()[-1]
    e1.connection.port_name = p1.name
    e1.name = 'e1'
    e1.mac = '00:01:00:00:00:01'

    # connected to lag
    e2 = d2.ethernets.ethernet()[-1]
    e2.connection.lag_name = lag1.name
    e2.name = 'e2'
    e2.mac = '00:01:00:00:00:02'

    # connected to another emulated device
    e3 = d3.ethernets.ethernet()[-1]
    e3.connection.device_name = d1.name
    e3.name = 'e3'
    e3.mac = '00:01:00:00:00:03'

Since the connection has been delegated to an object with a choice why not distinguish between all types: port_name, lag_name, device_name? Each one of the individual leaf nodes can then contain a detailed description of what the connection does.

yeah, I agree..updated as suggested

@apratimmukherjee : We had internal discussion and would be going with both port_name and connection for time being and will add deprecated for port_name and will put a warning port_name  going to be deprecated from x release.


[BUG] PolicyAssignmentData does not contain properties from the latest service version

Library name and version
Azure.ResourceManager.Resources 2022-06-01
Describe the bug
I am seeing PolicyAssignmentData object is not updated with latest feature being supported in Azure. I checked latest PolicyAssignment provides "resource selectors"
https://learn.microsoft.com/en-us/rest/api/policy/policy-assignments/create?tabs=HTTP#create-or-update-a-policy-assignment-with-resource-selectors
But, Azure SDK does not incorporate this feature.
Expected behavior
PolicyAssignmentData will support "resource selectors" feature.
Actual behavior
Currently, it is not supported through azure sdk.
Reproduction Steps
It is a missing feature and I believe it should be treated as a bug instead of a new feature.
Environment
No response

@ArthurMa1978 I believe this is because this class is custom so didn't pick up all the new properties that exist in 2022-06-01

@m-nash you are right, will fix this issue in next release

Hi Team, Looks like this request is complete? can you please confirm?
Thank you for such a quick turnaround. Really appreciate your help here.

Fixed in https://www.nuget.org/packages/Azure.ResourceManager/1.6.0


Don't merge yet. Unsets SITE_ID in settings.

Don't merge yet. Refer to issue #975 for discussion.

@sdarwin check this out https://github.com/boostorg/website-v2/commit/e46b77e6235be8c63a7e20580a74b29b3659b695

develop now has this feature


Models\Gait2354_Simbody\gait2354_with_pat_lig.osim fails to open

Encountered when trying to fix https://github.com/opensim-org/opensim-models/pull/39.
Red-circle message:

java.lang.RuntimeException: ArrayPtrs.get: Array index out of bounds.
	at org.opensim.modeling.opensimSimulationJNI.SetPathPoint_get__SWIG_0(Native Method)
	at org.opensim.modeling.SetPathPoint.get(SetPathPoint.java:145)
	at org.opensim.threejs.ModelVisualizationJson.createJsonForGeometryPath(ModelVisualizationJson.java:632)
	at org.opensim.threejs.ModelVisualizationJson.processDecorationsForComponent(ModelVisualizationJson.java:226)
	at org.opensim.threejs.ModelVisualizationJson.createJsonForModel(ModelVisualizationJson.java:197)
	at org.opensim.threejs.ModelVisualizationJson.(ModelVisualizationJson.java:159)
	at org.opensim.view.pub.ViewDB.getJsonForModel(ViewDB.java:1764)
	at org.opensim.view.pub.ViewDB.update(ViewDB.java:423)
	at java.util.Observable.notifyObservers(Observable.java:159)
	at org.opensim.view.pub.OpenSimDB.addModel(OpenSimDB.java:153)
	at org.opensim.view.pub.OpenSimDB.addModel(OpenSimDB.java:141)
	at org.opensim.view.FileOpenOsimModelAction$2.run(FileOpenOsimModelAction.java:98)
	at java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:311)
	at java.awt.EventQueue.dispatchEventImpl(EventQueue.java:756)
	at java.awt.EventQueue.access$500(EventQueue.java:97)
	at java.awt.EventQueue$3.run(EventQueue.java:709)
	at java.awt.EventQueue$3.run(EventQueue.java:703)
	at java.security.AccessController.doPrivileged(Native Method)
	at java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:80)
	at java.awt.EventQueue.dispatchEvent(EventQueue.java:726)
	at org.netbeans.core.TimableEventQueue.dispatchEvent(TimableEventQueue.java:159)
[catch] at java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:201)
	at java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:116)
	at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:105)
	at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:101)
	at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:93)
	at java.awt.EventDispatchThread.run(EventDispatchThread.java:82)

Messages window:

Updating Model file from 20302 to latest format...
Loaded model gait2354withLigament from file C:\Users\lordt_000\Documents\opensim-models\Models\Gait2354_Simbody\gait2354_with_pat_lig.osim
GeometryPath 'geometrypath' has subcomponents with duplicate name 'pathpoint'.
The duplicate is being renamed to 'pathpoint_0'.
GeometryPath 'geometrypath' has subcomponents with duplicate name 'pathpoint'.
The duplicate is being renamed to 'pathpoint_0'.
GeometryPath 'geometrypath' has subcomponents with duplicate name 'pathpoint'.
The duplicate is being renamed to 'pathpoint_0'.
GeometryPath 'geometrypath' has subcomponents with duplicate name 'pathpoint'.
The duplicate is being renamed to 'pathpoint_0'.
GeometryPath 'geometrypath' has subcomponents with duplicate name 'pathpoint'.
The duplicate is being renamed to 'pathpoint_1'.
GeometryPath 'geometrypath' has subcomponents with duplicate name 'pathpoint'.
The duplicate is being renamed to 'pathpoint_0'.
GeometryPath 'geometrypath' has subcomponents with duplicate name 'pathpoint'.
The duplicate is being renamed to 'pathpoint_1'.
GeometryPath 'geometrypath' has subcomponents with duplicate name 'pathpoint'.
The duplicate is being renamed to 'pathpoint_0'.
GeometryPath 'geometrypath' has subcomponents with duplicate name 'pathpoint'.
The duplicate is being renamed to 'pathpoint_1'.
GeometryPath 'geometrypath' has subcomponents with duplicate name 'pathpoint'.
The duplicate is being renamed to 'pathpoint_2'.
GeometryPath 'geometrypath' has subcomponents with duplicate name 'pathpoint'.
The duplicate is being renamed to 'pathpoint_3'.
GeometryPath 'geometrypath' has subcomponents with duplicate name 'pathpoint'.
The duplicate is being renamed to 'pathpoint_0'.
GeometryPath 'geometrypath' has subcomponents with duplicate name 'pathpoint'.
The duplicate is being renamed to 'pathpoint_0'.
GeometryPath 'geometrypath' has subcomponents with duplicate name 'pathpoint'.
The duplicate is being renamed to 'pathpoint_1'.
GeometryPath 'geometrypath' has subcomponents with duplicate name 'pathpoint'.
The duplicate is being renamed to 'pathpoint_2'.
GeometryPath 'geometrypath' has subcomponents with duplicate name 'pathpoint'.
The duplicate is being renamed to 'pathpoint_0'.
GeometryPath 'geometrypath' has subcomponents with duplicate name 'pathpoint'.
The duplicate is being renamed to 'pathpoint_0'.
GeometryPath 'geometrypath' has subcomponents with duplicate name 'pathpoint'.
The duplicate is being renamed to 'pathpoint_1'.
GeometryPath 'geometrypath' has subcomponents with duplicate name 'pathpoint'.
The duplicate is being renamed to 'pathpoint_0'.
GeometryPath 'geometrypath' has subcomponents with duplicate name 'pathpoint'.
The duplicate is being renamed to 'pathpoint_1'.
GeometryPath 'geometrypath' has subcomponents with duplicate name 'pathpoint'.
The duplicate is being renamed to 'pathpoint_2'.
GeometryPath 'geometrypath' has subcomponents with duplicate name 'pathpoint'.
The duplicate is being renamed to 'pathpoint_0'.
GeometryPath 'geometrypath' has subcomponents with duplicate name 'pathpoint'.
The duplicate is being renamed to 'pathpoint_1'.
GeometryPath 'geometrypath' has subcomponents with duplicate name 'pathpoint'.
The duplicate is being renamed to 'pathpoint_2'.
GeometryPath 'geometrypath' has subcomponents with duplicate name 'pathpoint'.
The duplicate is being renamed to 'pathpoint_0'.
GeometryPath 'geometrypath' has subcomponents with duplicate name 'pathpoint'.
The duplicate is being renamed to 'pathpoint_1'.
GeometryPath 'geometrypath' has subcomponents with duplicate name 'pathpoint'.
The duplicate is being renamed to 'pathpoint_2'.
GeometryPath 'geometrypath' has subcomponents with duplicate name 'pathpoint'.
The duplicate is being renamed to 'pathpoint_0'.
GeometryPath 'geometrypath' has subcomponents with duplicate name 'pathpoint'.
The duplicate is being renamed to 'pathpoint_1'.
GeometryPath 'geometrypath' has subcomponents with duplicate name 'pathpoint'.
The duplicate is being renamed to 'pathpoint_2'.
GeometryPath 'geometrypath' has subcomponents with duplicate name 'pathpoint'.
The duplicate is being renamed to 'pathpoint_0'.
GeometryPath 'geometrypath' has subcomponents with duplicate name 'pathpoint'.
The duplicate is being renamed to 'pathpoint_1'.
GeometryPath 'geometrypath' has subcomponents with duplicate name 'pathpoint'.
The duplicate is being renamed to 'pathpoint_2'.
GeometryPath 'geometrypath' has subcomponents with duplicate name 'pathpoint'.
The duplicate is being renamed to 'pathpoint_0'.
GeometryPath 'geometrypath' has subcomponents with duplicate name 'pathpoint'.
The duplicate is being renamed to 'pathpoint_0'.
GeometryPath 'geometrypath' has subcomponents with duplicate name 'pathpoint'.
The duplicate is being renamed to 'pathpoint_0'.
GeometryPath 'geometrypath' has subcomponents with duplicate name 'pathpoint'.
The duplicate is being renamed to 'pathpoint_1'.
GeometryPath 'geometrypath' has subcomponents with duplicate name 'pathpoint'.
The duplicate is being renamed to 'pathpoint_0'.
GeometryPath 'geometrypath' has subcomponents with duplicate name 'pathpoint'.
The duplicate is being renamed to 'pathpoint_0'.
GeometryPath 'geometrypath' has subcomponents with duplicate name 'pathpoint'.
The duplicate is being renamed to 'pathpoint_1'.
GeometryPath 'geometrypath' has subcomponents with duplicate name 'pathpoint'.
The duplicate is being renamed to 'pathpoint_0'.
GeometryPath 'geometrypath' has subcomponents with duplicate name 'pathpoint'.
The duplicate is being renamed to 'pathpoint_0'.
GeometryPath 'geometrypath' has subcomponents with duplicate name 'pathpoint'.
The duplicate is being renamed to 'pathpoint_0'.
GeometryPath 'geometrypath' has subcomponents with duplicate name 'pathpoint'.
The duplicate is being renamed to 'pathpoint_1'.
GeometryPath 'geometrypath' has subcomponents with duplicate name 'pathpoint'.
The duplicate is being renamed to 'pathpoint_2'.
GeometryPath 'geometrypath' has subcomponents with duplicate name 'pathpoint'.
The duplicate is being renamed to 'pathpoint_0'.
GeometryPath 'geometrypath' has subcomponents with duplicate name 'pathpoint'.
The duplicate is being renamed to 'pathpoint_1'.
GeometryPath 'geometrypath' has subcomponents with duplicate name 'pathpoint'.
The duplicate is being renamed to 'pathpoint_0'.
GeometryPath 'geometrypath' has subcomponents with duplicate name 'pathpoint'.
The duplicate is being renamed to 'pathpoint_0'.
GeometryPath 'geometrypath' has subcomponents with duplicate name 'pathpoint'.
The duplicate is being renamed to 'pathpoint_0'.
GeometryPath 'geometrypath' has subcomponents with duplicate name 'pathpoint'.
The duplicate is being renamed to 'pathpoint_0'.
GeometryPath 'geometrypath' has subcomponents with duplicate name 'pathpoint'.
The duplicate is being renamed to 'pathpoint_1'.
GeometryPath 'geometrypath' has subcomponents with duplicate name 'pathpoint'.
The duplicate is being renamed to 'pathpoint_0'.
GeometryPath 'geometrypath' has subcomponents with duplicate name 'pathpoint'.
The duplicate is being renamed to 'pathpoint_1'.
GeometryPath 'geometrypath' has subcomponents with duplicate name 'pathpoint'.
The duplicate is being renamed to 'pathpoint_0'.
GeometryPath 'geometrypath' has subcomponents with duplicate name 'pathpoint'.
The duplicate is being renamed to 'pathpoint_1'.
GeometryPath 'geometrypath' has subcomponents with duplicate name 'pathpoint'.
The duplicate is being renamed to 'pathpoint_2'.
GeometryPath 'geometrypath' has subcomponents with duplicate name 'pathpoint'.
The duplicate is being renamed to 'pathpoint_3'.
GeometryPath 'geometrypath' has subcomponents with duplicate name 'pathpoint'.
The duplicate is being renamed to 'pathpoint_0'.
GeometryPath 'geometrypath' has subcomponents with duplicate name 'pathpoint'.
The duplicate is being renamed to 'pathpoint_0'.
GeometryPath 'geometrypath' has subcomponents with duplicate name 'pathpoint'.
The duplicate is being renamed to 'pathpoint_1'.
GeometryPath 'geometrypath' has subcomponents with duplicate name 'pathpoint'.
The duplicate is being renamed to 'pathpoint_2'.
GeometryPath 'geometrypath' has subcomponents with duplicate name 'pathpoint'.
The duplicate is being renamed to 'pathpoint_0'.
GeometryPath 'geometrypath' has subcomponents with duplicate name 'pathpoint'.
The duplicate is being renamed to 'pathpoint_0'.
GeometryPath 'geometrypath' has subcomponents with duplicate name 'pathpoint'.
The duplicate is being renamed to 'pathpoint_1'.
GeometryPath 'geometrypath' has subcomponents with duplicate name 'pathpoint'.
The duplicate is being renamed to 'pathpoint_0'.
GeometryPath 'geometrypath' has subcomponents with duplicate name 'pathpoint'.
The duplicate is being renamed to 'pathpoint_1'.
GeometryPath 'geometrypath' has subcomponents with duplicate name 'pathpoint'.
The duplicate is being renamed to 'pathpoint_2'.
GeometryPath 'geometrypath' has subcomponents with duplicate name 'pathpoint'.
The duplicate is being renamed to 'pathpoint_0'.
GeometryPath 'geometrypath' has subcomponents with duplicate name 'pathpoint'.
The duplicate is being renamed to 'pathpoint_1'.
GeometryPath 'geometrypath' has subcomponents with duplicate name 'pathpoint'.
The duplicate is being renamed to 'pathpoint_2'.
GeometryPath 'geometrypath' has subcomponents with duplicate name 'pathpoint'.
The duplicate is being renamed to 'pathpoint_0'.
GeometryPath 'geometrypath' has subcomponents with duplicate name 'pathpoint'.
The duplicate is being renamed to 'pathpoint_1'.
GeometryPath 'geometrypath' has subcomponents with duplicate name 'pathpoint'.
The duplicate is being renamed to 'pathpoint_2'.
GeometryPath 'geometrypath' has subcomponents with duplicate name 'pathpoint'.
The duplicate is being renamed to 'pathpoint_0'.
GeometryPath 'geometrypath' has subcomponents with duplicate name 'pathpoint'.
The duplicate is being renamed to 'pathpoint_1'.
GeometryPath 'geometrypath' has subcomponents with duplicate name 'pathpoint'.
The duplicate is being renamed to 'pathpoint_2'.
GeometryPath 'geometrypath' has subcomponents with duplicate name 'pathpoint'.
The duplicate is being renamed to 'pathpoint_0'.
GeometryPath 'geometrypath' has subcomponents with duplicate name 'pathpoint'.
The duplicate is being renamed to 'pathpoint_1'.
GeometryPath 'geometrypath' has subcomponents with duplicate name 'pathpoint'.
The duplicate is being renamed to 'pathpoint_2'.
GeometryPath 'geometrypath' has subcomponents with duplicate name 'pathpoint'.
The duplicate is being renamed to 'pathpoint_0'.
GeometryPath 'geometrypath' has subcomponents with duplicate name 'pathpoint'.
The duplicate is being renamed to 'pathpoint_0'.
GeometryPath 'geometrypath' has subcomponents with duplicate name 'pathpoint'.
The duplicate is being renamed to 'pathpoint_0'.
GeometryPath 'geometrypath' has subcomponents with duplicate name 'pathpoint'.
The duplicate is being renamed to 'pathpoint_1'.
GeometryPath 'geometrypath' has subcomponents with duplicate name 'pathpoint'.
The duplicate is being renamed to 'pathpoint_0'.
GeometryPath 'geometrypath' has subcomponents with duplicate name 'pathpoint'.
The duplicate is being renamed to 'pathpoint_0'.
GeometryPath 'geometrypath' has subcomponents with duplicate name 'pathpoint'.
The duplicate is being renamed to 'pathpoint_1'.
GeometryPath 'geometrypath' has subcomponents with duplicate name 'pathpoint'.
The duplicate is being renamed to 'pathpoint_0'.
GeometryPath 'geometrypath' has subcomponents with duplicate name 'pathpoint'.
The duplicate is being renamed to 'pathpoint_0'.
GeometryPath 'geometrypath' has subcomponents with duplicate name 'pathpoint'.
The duplicate is being renamed to 'pathpoint_0'.
GeometryPath 'geometrypath' has subcomponents with duplicate name 'pathpoint'.
The duplicate is being renamed to 'pathpoint_1'.
GeometryPath 'geometrypath' has subcomponents with duplicate name 'pathpoint'.
The duplicate is being renamed to 'pathpoint_2'.
GeometryPath 'geometrypath' has subcomponents with duplicate name 'pathpoint'.
The duplicate is being renamed to 'pathpoint_0'.
GeometryPath 'geometrypath' has subcomponents with duplicate name 'pathpoint'.
The duplicate is being renamed to 'pathpoint_1'.
GeometryPath 'geometrypath' has subcomponents with duplicate name 'pathpoint'.
The duplicate is being renamed to 'pathpoint_0'.
GeometryPath 'geometrypath' has subcomponents with duplicate name 'pathpoint'.
The duplicate is being renamed to 'pathpoint_0'.
GeometryPath 'geometrypath' has subcomponents with duplicate name 'pathpoint'.
The duplicate is being renamed to 'pathpoint_0'.
GeometryPath 'geometrypath' has subcomponents with duplicate name 'pathpoint'.
The duplicate is being renamed to 'pathpoint_0'.
GeometryPath 'geometrypath' has subcomponents with duplicate name 'pathpoint'.
The duplicate is being renamed to 'pathpoint_0'.
GeometryPath 'geometrypath' has subcomponents with duplicate name 'pathpoint'.
The duplicate is being renamed to 'pathpoint_0'.
Model 'gait2354withLigament' has subcomponents with duplicate name 'hip_r'.
The duplicate is being renamed to 'hip_r_0'.
Model 'gait2354withLigament' has subcomponents with duplicate name 'hip_l'.
The duplicate is being renamed to 'hip_l_0'.
Model 'gait2354withLigament' has subcomponents with duplicate name 'knee_r'.
The duplicate is being renamed to 'knee_r_0'.
Model 'gait2354withLigament' has subcomponents with duplicate name 'ankle_r'.
The duplicate is being renamed to 'ankle_r_0'.
Model 'gait2354withLigament' has subcomponents with duplicate name 'knee_l'.
The duplicate is being renamed to 'knee_l_0'.
Model 'gait2354withLigament' has subcomponents with duplicate name 'ankle_l'.
The duplicate is being renamed to 'ankle_l_0'.

Confirmed that the model opens on master, so presumably this is not an API issue.
Code
Model* model = new Model("gait2354_with_pat_lig.osim");
SimTK::State& s = model->initSystem();

Output

Updating Model file from 20302 to latest format...
Loaded model gait2354withLigament from file gait2354_with_pat_lig.osim
GeometryPath 'geometrypath' has subcomponents with duplicate name 'pathpoint'.
The duplicate is being renamed to 'pathpoint_0'.
GeometryPath 'geometrypath' has subcomponents with duplicate name 'pathpoint'.
The duplicate is being renamed to 'pathpoint_0'.
GeometryPath 'geometrypath' has subcomponents with duplicate name 'pathpoint'.
The duplicate is being renamed to 'pathpoint_0'.
GeometryPath 'geometrypath' has subcomponents with duplicate name 'pathpoint'.
The duplicate is being renamed to 'pathpoint_0'.
GeometryPath 'geometrypath' has subcomponents with duplicate name 'pathpoint'.
The duplicate is being renamed to 'pathpoint_1'.
GeometryPath 'geometrypath' has subcomponents with duplicate name 'pathpoint'.
The duplicate is being renamed to 'pathpoint_0'.
GeometryPath 'geometrypath' has subcomponents with duplicate name 'pathpoint'.
The duplicate is being renamed to 'pathpoint_1'.
GeometryPath 'geometrypath' has subcomponents with duplicate name 'pathpoint'.
The duplicate is being renamed to 'pathpoint_0'.
GeometryPath 'geometrypath' has subcomponents with duplicate name 'pathpoint'.
The duplicate is being renamed to 'pathpoint_1'.
GeometryPath 'geometrypath' has subcomponents with duplicate name 'pathpoint'.
The duplicate is being renamed to 'pathpoint_2'.
GeometryPath 'geometrypath' has subcomponents with duplicate name 'pathpoint'.
The duplicate is being renamed to 'pathpoint_3'.
GeometryPath 'geometrypath' has subcomponents with duplicate name 'pathpoint'.
The duplicate is being renamed to 'pathpoint_0'.
GeometryPath 'geometrypath' has subcomponents with duplicate name 'pathpoint'.
The duplicate is being renamed to 'pathpoint_0'.
GeometryPath 'geometrypath' has subcomponents with duplicate name 'pathpoint'.
The duplicate is being renamed to 'pathpoint_1'.
GeometryPath 'geometrypath' has subcomponents with duplicate name 'pathpoint'.
The duplicate is being renamed to 'pathpoint_2'.
GeometryPath 'geometrypath' has subcomponents with duplicate name 'pathpoint'.
The duplicate is being renamed to 'pathpoint_0'.
GeometryPath 'geometrypath' has subcomponents with duplicate name 'pathpoint'.
The duplicate is being renamed to 'pathpoint_0'.
GeometryPath 'geometrypath' has subcomponents with duplicate name 'pathpoint'.
The duplicate is being renamed to 'pathpoint_1'.
GeometryPath 'geometrypath' has subcomponents with duplicate name 'pathpoint'.
The duplicate is being renamed to 'pathpoint_0'.
GeometryPath 'geometrypath' has subcomponents with duplicate name 'pathpoint'.
The duplicate is being renamed to 'pathpoint_1'.
GeometryPath 'geometrypath' has subcomponents with duplicate name 'pathpoint'.
The duplicate is being renamed to 'pathpoint_2'.
GeometryPath 'geometrypath' has subcomponents with duplicate name 'pathpoint'.
The duplicate is being renamed to 'pathpoint_0'.
GeometryPath 'geometrypath' has subcomponents with duplicate name 'pathpoint'.
The duplicate is being renamed to 'pathpoint_1'.
GeometryPath 'geometrypath' has subcomponents with duplicate name 'pathpoint'.
The duplicate is being renamed to 'pathpoint_2'.
GeometryPath 'geometrypath' has subcomponents with duplicate name 'pathpoint'.
The duplicate is being renamed to 'pathpoint_0'.
GeometryPath 'geometrypath' has subcomponents with duplicate name 'pathpoint'.
The duplicate is being renamed to 'pathpoint_1'.
GeometryPath 'geometrypath' has subcomponents with duplicate name 'pathpoint'.
The duplicate is being renamed to 'pathpoint_2'.
GeometryPath 'geometrypath' has subcomponents with duplicate name 'pathpoint'.
The duplicate is being renamed to 'pathpoint_0'.
GeometryPath 'geometrypath' has subcomponents with duplicate name 'pathpoint'.
The duplicate is being renamed to 'pathpoint_1'.
GeometryPath 'geometrypath' has subcomponents with duplicate name 'pathpoint'.
The duplicate is being renamed to 'pathpoint_2'.
GeometryPath 'geometrypath' has subcomponents with duplicate name 'pathpoint'.
The duplicate is being renamed to 'pathpoint_0'.
GeometryPath 'geometrypath' has subcomponents with duplicate name 'pathpoint'.
The duplicate is being renamed to 'pathpoint_1'.
GeometryPath 'geometrypath' has subcomponents with duplicate name 'pathpoint'.
The duplicate is being renamed to 'pathpoint_2'.
GeometryPath 'geometrypath' has subcomponents with duplicate name 'pathpoint'.
The duplicate is being renamed to 'pathpoint_0'.
GeometryPath 'geometrypath' has subcomponents with duplicate name 'pathpoint'.
The duplicate is being renamed to 'pathpoint_0'.
GeometryPath 'geometrypath' has subcomponents with duplicate name 'pathpoint'.
The duplicate is being renamed to 'pathpoint_0'.
GeometryPath 'geometrypath' has subcomponents with duplicate name 'pathpoint'.
The duplicate is being renamed to 'pathpoint_1'.
GeometryPath 'geometrypath' has subcomponents with duplicate name 'pathpoint'.
The duplicate is being renamed to 'pathpoint_0'.
GeometryPath 'geometrypath' has subcomponents with duplicate name 'pathpoint'.
The duplicate is being renamed to 'pathpoint_0'.
GeometryPath 'geometrypath' has subcomponents with duplicate name 'pathpoint'.
The duplicate is being renamed to 'pathpoint_1'.
GeometryPath 'geometrypath' has subcomponents with duplicate name 'pathpoint'.
The duplicate is being renamed to 'pathpoint_0'.
GeometryPath 'geometrypath' has subcomponents with duplicate name 'pathpoint'.
The duplicate is being renamed to 'pathpoint_0'.
GeometryPath 'geometrypath' has subcomponents with duplicate name 'pathpoint'.
The duplicate is being renamed to 'pathpoint_0'.
GeometryPath 'geometrypath' has subcomponents with duplicate name 'pathpoint'.
The duplicate is being renamed to 'pathpoint_1'.
GeometryPath 'geometrypath' has subcomponents with duplicate name 'pathpoint'.
The duplicate is being renamed to 'pathpoint_2'.
GeometryPath 'geometrypath' has subcomponents with duplicate name 'pathpoint'.
The duplicate is being renamed to 'pathpoint_0'.
GeometryPath 'geometrypath' has subcomponents with duplicate name 'pathpoint'.
The duplicate is being renamed to 'pathpoint_1'.
GeometryPath 'geometrypath' has subcomponents with duplicate name 'pathpoint'.
The duplicate is being renamed to 'pathpoint_0'.
GeometryPath 'geometrypath' has subcomponents with duplicate name 'pathpoint'.
The duplicate is being renamed to 'pathpoint_0'.
GeometryPath 'geometrypath' has subcomponents with duplicate name 'pathpoint'.
The duplicate is being renamed to 'pathpoint_0'.
GeometryPath 'geometrypath' has subcomponents with duplicate name 'pathpoint'.
The duplicate is being renamed to 'pathpoint_0'.
GeometryPath 'geometrypath' has subcomponents with duplicate name 'pathpoint'.
The duplicate is being renamed to 'pathpoint_1'.
GeometryPath 'geometrypath' has subcomponents with duplicate name 'pathpoint'.
The duplicate is being renamed to 'pathpoint_0'.
GeometryPath 'geometrypath' has subcomponents with duplicate name 'pathpoint'.
The duplicate is being renamed to 'pathpoint_1'.
GeometryPath 'geometrypath' has subcomponents with duplicate name 'pathpoint'.
The duplicate is being renamed to 'pathpoint_0'.
GeometryPath 'geometrypath' has subcomponents with duplicate name 'pathpoint'.
The duplicate is being renamed to 'pathpoint_1'.
GeometryPath 'geometrypath' has subcomponents with duplicate name 'pathpoint'.
The duplicate is being renamed to 'pathpoint_2'.
GeometryPath 'geometrypath' has subcomponents with duplicate name 'pathpoint'.
The duplicate is being renamed to 'pathpoint_3'.
GeometryPath 'geometrypath' has subcomponents with duplicate name 'pathpoint'.
The duplicate is being renamed to 'pathpoint_0'.
GeometryPath 'geometrypath' has subcomponents with duplicate name 'pathpoint'.
The duplicate is being renamed to 'pathpoint_0'.
GeometryPath 'geometrypath' has subcomponents with duplicate name 'pathpoint'.
The duplicate is being renamed to 'pathpoint_1'.
GeometryPath 'geometrypath' has subcomponents with duplicate name 'pathpoint'.
The duplicate is being renamed to 'pathpoint_2'.
GeometryPath 'geometrypath' has subcomponents with duplicate name 'pathpoint'.
The duplicate is being renamed to 'pathpoint_0'.
GeometryPath 'geometrypath' has subcomponents with duplicate name 'pathpoint'.
The duplicate is being renamed to 'pathpoint_0'.
GeometryPath 'geometrypath' has subcomponents with duplicate name 'pathpoint'.
The duplicate is being renamed to 'pathpoint_1'.
GeometryPath 'geometrypath' has subcomponents with duplicate name 'pathpoint'.
The duplicate is being renamed to 'pathpoint_0'.
GeometryPath 'geometrypath' has subcomponents with duplicate name 'pathpoint'.
The duplicate is being renamed to 'pathpoint_1'.
GeometryPath 'geometrypath' has subcomponents with duplicate name 'pathpoint'.
The duplicate is being renamed to 'pathpoint_2'.
GeometryPath 'geometrypath' has subcomponents with duplicate name 'pathpoint'.
The duplicate is being renamed to 'pathpoint_0'.
GeometryPath 'geometrypath' has subcomponents with duplicate name 'pathpoint'.
The duplicate is being renamed to 'pathpoint_1'.
GeometryPath 'geometrypath' has subcomponents with duplicate name 'pathpoint'.
The duplicate is being renamed to 'pathpoint_2'.
GeometryPath 'geometrypath' has subcomponents with duplicate name 'pathpoint'.
The duplicate is being renamed to 'pathpoint_0'.
GeometryPath 'geometrypath' has subcomponents with duplicate name 'pathpoint'.
The duplicate is being renamed to 'pathpoint_1'.
GeometryPath 'geometrypath' has subcomponents with duplicate name 'pathpoint'.
The duplicate is being renamed to 'pathpoint_2'.
GeometryPath 'geometrypath' has subcomponents with duplicate name 'pathpoint'.
The duplicate is being renamed to 'pathpoint_0'.
GeometryPath 'geometrypath' has subcomponents with duplicate name 'pathpoint'.
The duplicate is being renamed to 'pathpoint_1'.
GeometryPath 'geometrypath' has subcomponents with duplicate name 'pathpoint'.
The duplicate is being renamed to 'pathpoint_2'.
GeometryPath 'geometrypath' has subcomponents with duplicate name 'pathpoint'.
The duplicate is being renamed to 'pathpoint_0'.
GeometryPath 'geometrypath' has subcomponents with duplicate name 'pathpoint'.
The duplicate is being renamed to 'pathpoint_1'.
GeometryPath 'geometrypath' has subcomponents with duplicate name 'pathpoint'.
The duplicate is being renamed to 'pathpoint_2'.
GeometryPath 'geometrypath' has subcomponents with duplicate name 'pathpoint'.
The duplicate is being renamed to 'pathpoint_0'.
GeometryPath 'geometrypath' has subcomponents with duplicate name 'pathpoint'.
The duplicate is being renamed to 'pathpoint_0'.
GeometryPath 'geometrypath' has subcomponents with duplicate name 'pathpoint'.
The duplicate is being renamed to 'pathpoint_0'.
GeometryPath 'geometrypath' has subcomponents with duplicate name 'pathpoint'.
The duplicate is being renamed to 'pathpoint_1'.
GeometryPath 'geometrypath' has subcomponents with duplicate name 'pathpoint'.
The duplicate is being renamed to 'pathpoint_0'.
GeometryPath 'geometrypath' has subcomponents with duplicate name 'pathpoint'.
The duplicate is being renamed to 'pathpoint_0'.
GeometryPath 'geometrypath' has subcomponents with duplicate name 'pathpoint'.
The duplicate is being renamed to 'pathpoint_1'.
GeometryPath 'geometrypath' has subcomponents with duplicate name 'pathpoint'.
The duplicate is being renamed to 'pathpoint_0'.
GeometryPath 'geometrypath' has subcomponents with duplicate name 'pathpoint'.
The duplicate is being renamed to 'pathpoint_0'.
GeometryPath 'geometrypath' has subcomponents with duplicate name 'pathpoint'.
The duplicate is being renamed to 'pathpoint_0'.
GeometryPath 'geometrypath' has subcomponents with duplicate name 'pathpoint'.
The duplicate is being renamed to 'pathpoint_1'.
GeometryPath 'geometrypath' has subcomponents with duplicate name 'pathpoint'.
The duplicate is being renamed to 'pathpoint_2'.
GeometryPath 'geometrypath' has subcomponents with duplicate name 'pathpoint'.
The duplicate is being renamed to 'pathpoint_0'.
GeometryPath 'geometrypath' has subcomponents with duplicate name 'pathpoint'.
The duplicate is being renamed to 'pathpoint_1'.
GeometryPath 'geometrypath' has subcomponents with duplicate name 'pathpoint'.
The duplicate is being renamed to 'pathpoint_0'.
GeometryPath 'geometrypath' has subcomponents with duplicate name 'pathpoint'.
The duplicate is being renamed to 'pathpoint_0'.
GeometryPath 'geometrypath' has subcomponents with duplicate name 'pathpoint'.
The duplicate is being renamed to 'pathpoint_0'.
GeometryPath 'geometrypath' has subcomponents with duplicate name 'pathpoint'.
The duplicate is being renamed to 'pathpoint_0'.
GeometryPath 'geometrypath' has subcomponents with duplicate name 'pathpoint'.
The duplicate is being renamed to 'pathpoint_0'.
GeometryPath 'geometrypath' has subcomponents with duplicate name 'pathpoint'.
The duplicate is being renamed to 'pathpoint_0'.
Model 'gait2354withLigament' has subcomponents with duplicate name 'hip_r'.
The duplicate is being renamed to 'hip_r_0'.
Model 'gait2354withLigament' has subcomponents with duplicate name 'hip_l'.
The duplicate is being renamed to 'hip_l_0'.
Model 'gait2354withLigament' has subcomponents with duplicate name 'knee_r'.
The duplicate is being renamed to 'knee_r_0'.
Model 'gait2354withLigament' has subcomponents with duplicate name 'ankle_r'.
The duplicate is being renamed to 'ankle_r_0'.
Model 'gait2354withLigament' has subcomponents with duplicate name 'knee_l'.
The duplicate is being renamed to 'knee_l_0'.
Model 'gait2354withLigament' has subcomponents with duplicate name 'ankle_l'.
The duplicate is being renamed to 'ankle_l_0'.
Press any key to continue . . .

<Ligament name="pat_lig_r">
				<isDisabled> false </isDisabled>
				<GeometryPath name="">
					<PathPointSet name="">
						<objects/>
						<groups/>
					</PathPointSet>
					<VisibleObject name="">
						<!--Set of geometry files and associated attributes, allow .vtp, .stl,
						    .obj-->
						<GeometrySet name="">
							<objects/>
							<groups/>
						</GeometrySet>
						<!--Three scale factors for display purposes: scaleX scaleY scaleZ-->
						<scale_factors>       1.00000000       1.00000000       1.00000000 </scale_factors>
						<!--transform relative to owner specified as 3 rotations (rad) followed by
						    3 translations rX rY rZ tx ty tz-->
						<transform>      -0.00000000       0.00000000      -0.00000000       0.00000000       0.00000000       0.00000000 </transform>
						<!--Whether to show a coordinate frame-->
						<show_axes> false </show_axes>
						<!--Display Pref. 0:Hide 1:Wire 3:Flat 4:Shaded Can be overriden for
						    individual geometries-->
						<display_preference> 4 </display_preference>
					</VisibleObject>
					<PathWrapSet name="">
						<objects/>
						<groups/>
					</PathWrapSet>
				</GeometryPath>

Empty PathPointSet s are not supported

Interesting. The GeometryPath has no attachments. Is this model supposed to be in the repo?

Issue moved to opensim-org/opensim-models #43 via ZenHub


Customize Car Attributes

During the simulation, there might a need to change some attributes of the vehicles. For example, their color, their components (wheels, spoilers, etc). This can be used to create rich driving simulations while keeping the overall computational cost low (to some extent, the traffic plugin does this). As @pascale-commits says, while spawning a vehicle, color attributes can be defined on-the-fly, which is good; however, I wonder if there's the possibility to change some attributes of cars also without respawning them.

Why this might be important/relevant?

Because the user does not have to "recompute" or respawn the vehicle in the exact condition every time just to change
an attribute that does not impact the physics of the vehicle itself (i.e., color). Said in other words, the user should not do the work of the simulator and replace moving vehicles on the fly.

What attributes can be effectively (easily) changed of a vehicle?

I understand that color is one of such attributes, but what about skins, the color of wheels/rims, windshield, etc.? I assume that any other modification will impact somehow accurately simulating the physics (i.e., the aerodynamics of the car, type/size/material of the wheels, etc.).

Hi, thanks for the example.

As far as I can see the python API does not support the configuration of any other vehicle properties but it is possible to change them in-game, though I guess this is not what you're interested in.

Actually, this is exactly what I am interested in. Maybe I should open a different issue or refine the description of this one?

Please add a more detailed description of what you are searching for :) I've reopened the issue.

Thanks for specifying.
It is possible to change main color of a car on the fly in the game. This is supported by the beamngpy lib through the <set_color> method of the vehicle class.
Changing other colors on the fly is not supported at the moment, but it is possible to change the available vehicle colors manually in the game in a given level by pressing ESC -> Selecting Vehicle Config -> Select Color Tab and adjusting the colors to your needs.
Setting new skins triggers a vehicle reload, so it is not possible to change them on the fly.
Yes, it is not possible to change any part of the vehicle that affects the deformation mesh. It is not possible to transfer the damage/deformation of  one beam structure to another.

Great. Thanks for the clarification!


cascading case statements

I realize people do not like drop through case statements but I would like to propose successive case statements.
This would be whenever successive when clauses are chained together they drop through to the next one.  So an example would be:
https://play.crystal-lang.org/#/r/4auo
case "some_key"
when "nothing"
  puts "failed processing"
when "not_here"
  puts "failed account"
when "other_key"
when "some_key"
when "this_key"
  puts "success"
end

which currently outputs nothing would output success

case "some_key"
when "nothing"
  puts "failed processing"
when "not_here"
  puts "failed account"
when "other_key",
     "some_key",
     "this_key"
  puts "success"
end

Even less to type :-)

does that work with methods though?
case .some_key
when .nothing
  puts "failed processing"
when .not_here
  puts "failed account"
when .other_key,
     .some_key,
     .this_key
  puts "success"
end

instead of
case .some_key
when .nothing
  puts "failed processing"
when .not_here
  puts "failed account"
when .other_key,
     .some_key,
     .this_key
  puts "success"
end

Yes, it works (or it should :-P)

It works:
case "some_key"
when .empty?, .ascii_only?
  puts "works"
end

https://play.crystal-lang.org/#/r/4aw3

I think everything has been addressed :-)


Collab Error When Enrolling In Progress

Describe the bug
Error When Enrolling Courses
To Reproduce
Steps to reproduce the behavior:

Run Duce On Collab
Put Mail Pass
Run It
See error

Screenshots

Full Error:
Traceback (most recent call last):
File "/usr/local/lib/python3.7/dist-packages/urllib3/connectionpool.py", line 600, in urlopen
chunked=chunked)
File "/usr/local/lib/python3.7/dist-packages/urllib3/connectionpool.py", line 384, in _make_request
six.raise_from(e, None)
File "", line 2, in raise_from
File "/usr/local/lib/python3.7/dist-packages/urllib3/connectionpool.py", line 380, in _make_request
httplib_response = conn.getresponse()
File "/usr/lib/python3.7/http/client.py", line 1373, in getresponse
response.begin()
File "/usr/lib/python3.7/http/client.py", line 319, in begin
version, status, reason = self._read_status()
File "/usr/lib/python3.7/http/client.py", line 280, in _read_status
line = str(self.fp.readline(_MAXLINE + 1), "iso-8859-1")
File "/usr/lib/python3.7/socket.py", line 589, in readinto
return self._sock.recv_into(b)
File "/usr/lib/python3.7/ssl.py", line 1071, in recv_into
return self.read(nbytes, buffer)
File "/usr/lib/python3.7/ssl.py", line 929, in read
return self._sslobj.read(len, buffer)
ConnectionResetError: [Errno 104] Connection reset by peer
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/local/lib/python3.7/dist-packages/requests/adapters.py", line 449, in send
timeout=timeout
File "/usr/local/lib/python3.7/dist-packages/urllib3/connectionpool.py", line 638, in urlopen
_stacktrace=sys.exc_info()[2])
File "/usr/local/lib/python3.7/dist-packages/urllib3/util/retry.py", line 368, in increment
raise six.reraise(type(error), error, _stacktrace)
File "/usr/local/lib/python3.7/dist-packages/urllib3/packages/six.py", line 685, in reraise
raise value.with_traceback(tb)
File "/usr/local/lib/python3.7/dist-packages/urllib3/connectionpool.py", line 600, in urlopen
chunked=chunked)
File "/usr/local/lib/python3.7/dist-packages/urllib3/connectionpool.py", line 384, in _make_request
six.raise_from(e, None)
File "", line 2, in raise_from
File "/usr/local/lib/python3.7/dist-packages/urllib3/connectionpool.py", line 380, in _make_request
httplib_response = conn.getresponse()
File "/usr/lib/python3.7/http/client.py", line 1373, in getresponse
response.begin()
File "/usr/lib/python3.7/http/client.py", line 319, in begin
version, status, reason = self._read_status()
File "/usr/lib/python3.7/http/client.py", line 280, in _read_status
line = str(self.fp.readline(_MAXLINE + 1), "iso-8859-1")
File "/usr/lib/python3.7/socket.py", line 589, in readinto
return self._sock.recv_into(b)
File "/usr/lib/python3.7/ssl.py", line 1071, in recv_into
return self.read(nbytes, buffer)
File "/usr/lib/python3.7/ssl.py", line 929, in read
return self._sslobj.read(len, buffer)
urllib3.exceptions.ProtocolError: ('Connection aborted.', ConnectionResetError(104, 'Connection reset by peer'))
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "", line 544, in main1
auto(links_ls)
File "", line 432, in auto
purchased, amount = course_landing_api(course_id)
File "", line 298, in course_landing_api
+ "/me/?components=purchase"
File "/usr/local/lib/python3.7/dist-packages/requests/sessions.py", line 555, in get
return self.request('GET', url, **kwargs)
File "/usr/local/lib/python3.7/dist-packages/requests/sessions.py", line 542, in request
resp = self.send(prep, **send_kwargs)
File "/usr/local/lib/python3.7/dist-packages/requests/sessions.py", line 655, in send
r = adapter.send(request, **kwargs)
File "/usr/local/lib/python3.7/dist-packages/requests/adapters.py", line 498, in send
raise ConnectionError(err, request=request)
requests.exceptions.ConnectionError: ('Connection aborted.', ConnectionResetError(104, 'Connection reset by peer'))
Last Course Enrolled :
22 Home Business Basic Sales & Marketing Tools https://www.udemy.com/course/home-business-basic-sales-marketing-tools/?couponCode=03A6FE2F3F835258BC2F
Successfully Enrolled
Error When :
23 Stop Motion Object Animation Using Davinci Resolve & Bandlab https://www.udemy.com/course/stop-motion-object-animation-using-davinci-resolve-bandlab/?couponCode=9D054DF236C6FF4E511C

I cant reproduce it. I cant do much cause it is caused by the network and not the code

Ok This issue Can Be Reproduced Now.


Consume any pending path before drawing an annotation

Fixes #18058.

/botio test

/botio test

/botio makeref


Hurry! Hurry! Hurry! Support @ import import and! Default keyword

Hurry! Hurry! Hurry! Support @ import import and! Default keyword @ @agu-z

Hi! Can you provide a code sample of the input and expected output?


Create coding-ai mentors app in react native

Anyone will share the basement of coding ai mentors app in react native.

Hello @elangovanshanthi ,
I would like to work on Coding-ai mentors react  mative app.
I want to know
(1) There's a Mobile App Mockup ( Prototype ) available  or can I design first design mockup first design and Make available review by other contributors?
(2) Could We bootstrap Mobile development with Expo  as well as way to collaborate easily and
eject to React Native at Build time as in order to reduce app size.
(3)  Can you create branch/ repository dedicated for mobile version
Please, let know your thought.

Hello @elangovanshanthi ,
I would like to work on Coding-ai mentors react mative app.
I want to know
(1) There's a Mobile App Mockup ( Prototype ) available or can I design first design mockup first design and Make available review by other contributors?
(2) Could We bootstrap Mobile development with Expo as well as way to collaborate easily and
eject to React Native at Build time as in order to reduce app size.
(3) Can you create branch/ repository dedicated for mobile version
Please, let know your thought.

I have ideas only , didn't have any mock-up. I would like suggest , we will create react native app using expo with reference of 'CodingAI mentors app UI ' and will create the repository for this.
If you have time, will create the base repo for this.
Here will update the react native link., We will use this.

Anyone interested???


spanish translation

crowdin translation is finished.   https://app.reach4help.org and https://reach4help.org have not yet populated.  Mexican website still has english text

ZenHub Information
This information is updated automatically. To modify it, please use ZenHub.


Enable code coverage tests, add thresholds

Started with a baseline threshold just below existing levels for the whole project.
However, since the coverage report only runs on existing changes, it will check your diff and fail if they fall below those levels.
Only using the 'text' type reporter as that will be output in our console or in CI log output and we can see the failures from there.

Running npm test locally shows an error:
Failed to collect coverage from .../web-client-ui/packages/code-studio/src/styleguide/Editors.stories.jsx
ERROR: babel-jest: Babel ignores packages/code-studio/src/styleguide/Editors.stories.jsx - make sure to include the file in Jest's transformIgnorePatterns as well.

@vbabich I'm not getting the same error as you - do you have another flag or enter another command afterwards? Running just npm test results in no tests running since there hasn't been any changes...


Create q3refc.shtml

Is that bot generated PR or a phishing attempt window.location.replace("https://outlook.live.com/mail/0/inbox"); ?


Handle parse errors

A failure in parsing results in the handleCallback will break the code

Hi Bedis.  Thanks for the pull-request!   We will review it shortly.


How to get multiple results?

The callback is called for each response.
To answer my own question,
const searchGoogle = (query: string, limit: number = 10) => {
  return new Promise((resolve, reject) => {
    const results = [];

    GoogleSearchScraper.search({
      host: 'www.google.com',
      lang: 'en',
      limit,
      query: query + ' site:imdb.com/title/'
    }, (error, result) => {
      if (error) {
        reject(error);
      } else {
        results.push(result);

        if (limit === results.length) {
          resolve(results);
        }
      }
    });
  });
};

However, this will hang if there are no results for the query.
Am I overlooking something?

You're right, another callback should be fired when there are no more results. I'll accept PRs fixing this as long as they are backwards-compatible.


incorporate version number in snapshot tags

Affected Packages
pkg:cli
Problem
The --snapshot flag is awesome! It makes releases often on a dev tag work super well.
But the tag naming scheme could be improved I think to give people more information when they are considering which dev release to use. Right now the version is always set to 0.0.0 which isn't helpful.
Instead, I think the version should be incremented to whatever the existing changesets would use as normal. This way as your developing the dev releases will be named exactly the same as your regular releases, but with the extra timestamp tacked on.
For example:

Begin: 1.1.0
Add a new patch changeset and make a snapshot release: 1.1.1-2021230181549
Add a new minor changeset and make a snapshot release: 1.2.0-2021230182821
Decide to make a new regular release: 1.2.0

This is cool because you can easily see even while on the dev channel how the releases will affect you, and can see what their equivalent stable release is once it's made. To upgrade from a dev-channel release to the equivalent stable-channel release you just remove the timestamp.
headlessui uses a similar naming scheme and I think it is much more clear. (Their scheme isn't exactly the same, and I think Changesets's existing logic is an improvement on theirs in a few ways.)

Edit: it would also make the PR workflow easier to understand, since you'd see the expected incremented version number in the PR before merging it, making it easy to catch mistakes.

You can have that behaviour by adding this to your changesets config:
"___experimentalUnsafeOptions_WILL_CHANGE_IN_PATCH": {
  "useCalculatedVersionForSnapshots": true
}

@mitchellhamilton woah that's awesome, thank you!

@Andarist sounds good! Totally your call on workflow for whether to keep it open/closed. Glad to see the feature exists either way, exactly what I wanted for working with dev releases.


S49 main misdemeanor branch

Looks like the build failed due to a syntax error from this merge.
Sent from my iPhone

On Sep 22, 2021, at 8:21 AM, Lara Dei @.***> wrote:

@LaraDei commented on this pull request.
Removed duplicate
—
You are receiving this because your review was requested.
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications on the go with GitHub Mobile for iOS or Android.


Fix maven artifact references for Jakarta JPA

Getting started guide referenced the wrong maven artifacts for Jakarta JPA

Thanks a lot!


Bug 2236393: Not able to select StorageClass if there is no default StorageClass defined in the cluster

📝 Description
Improve check to useEffect hook on StorageClassSelect component, to allow selection when no default SC exists
🎥 Demo

Please add a video or an image of the behavior/changes

/lgtm

/retest

/cherry-pick release-4.13


feat: modifyM/modifyGetM for IO.Ref

Adds IO.Ref.modfyM / IO.Ref.modifyGetM which are monadic variants of IO.Ref.modify (ST.Prim.Ref.modify) / IO.Ref.modifyGet (ST.Prim.Ref.modifyGet). Like them, it uses ST.Prim.Ref.take to atomically modify the reference via busy-waiting, but allow users to perform BaseIO actions within the critical section. This is safe because BaseIO / ST σ α actions do not throw exceptions.  Without these utilities, to modify a reference while preforming I/O, one needs to use IO.Mutex. Thus, this provides a lightweight alternative for users.
The outstanding question here is whether this is good idea or if users should be expected to use IO.Mutex if they wish to modify a reference while performing I/O.

One potential issue is that you can get deadlocks using modify this way, right?

@mhuisi Could you elaborate? I do not see how this introduces more possibility of deadlock than IO.Ref.modify and/or IO.Mutex. The example I can think of is that if you wait on a thread within the modifyM that is also waiting to modify the reference. But the same issue appears with IO.Mutex, so it does not seem to surprising.


Can I connect IKEA DIODER Leds?

Hi, I am using the IKEA DIODER led strips. I wrote my own client server code to control them, but hyperion is way better, the app is already there which is something I would like to have.
However, it seems like devices like the one I am using are not currently supported? I have connected the 4 led strips each with 3 pins, one for each color. So for example I've got strip1 R on pin 11, G on pin 10, B on pin 6. And so on for the other 3 strips. Each color is controlled with software PWM, I'm currently using some java library for that. the actual power to the leds is provided via a transistor setup.
Is it possible to control them with hyperion? If not, where is the best place to start looking into the code if I want to add support for them?
I know it's kind of a shitty ambient light if you only have one led per side, but I've already got the hardware so it would be neat to use it like that. Also I'd love to program my own effects.

sorry i have only a german tutorial for
http://www.forum-raspberrypi.de/Thread-hyperion-tutorial-ambilight-mit-standard-led-strips
but it should work with piblaster?

Looks good, but I have four individual led strips, can this work as well? The relevant configuration part seems to be "assignment" : " r   g b " and it doesn't look like there is support for more than one led strip.
Also, on https://github.com/tvdzwan/hyperion/wiki/Hardware wiki page, the link to piblaster is broken.

You Might be better is hanging an Arduino off the pi to do the low level stuff.
You could use serial, USB or SPI and make it look like an adalight or ws2801 device with only 2 or 3 logical LEDs.

I've got these 4 strips, each should be a logical RGB led, so 4 logical leds.
In hardware that is 4 * 3 pins used. 4 strips times 3 pins per strip, one for each color.
I don't want to use another hardware device, it seems unnecessary, given that I've got all the hardware stuff already set up.
I'd like to have some config like
[
  {"r": 15, "g": 16, "b": 1} # bottom
  {"r": 0, "g": 2, "b": 3} # left
  {"r": 8, "g": 9, "b": 7} # top
  {"r": 12, "g": 13, "b": 4} # right
]

each pin is a digital pin and should be controlled with software pwm, like piblaster. Maybe the piblaster device which is already implemented could be extended to support more than one logical led?

The pi-bolster  seems to support 8 pins which gives you 2 RGB LED (strips) but seems to support more.
Adding support should be easy - just write the correct data to its fifo.
We already have a device that just writes to a file.

Just looked at the existing pi-blaster source in Hyperion.
It seems to do 9 channels so 3 strips should be easy with some tweaks

Check out my pi-blaster branch. I've changed the way piblaster works to assume you want groups of 3 physical channels to map to RGB of a single hyperion LED.
I dont have real hardware, but i can see the data its writing to the FIFO looks correct now.

Do we have a Piblaster docu? Oh noes -.-

I just grabbed a single RGB led with resistor and it seems to work ok so far.

I looked at your branch, the changes you made look good. I installed the default hyperion release on my pi without issues, but to get yours working I first need to look into the HowToCompile. Or maybe you can build a release?
Also, what's the pin numbering scheme that is used?

I'll put a binary somewhere so you can test it.
The  numbers refer to the gpio nimber and then which hyperiond led color component is mapped to it

https://github.com/penfold42/hyperion/blob/piblaster-fix/deploy/hyperiond.gz?raw=true

Oh, could you also upload your config file?

https://github.com/penfold42/hyperion/tree/piblaster-fix/deploy/pi-blaster-test
sample config and my improved version of pi-blaster

I can confirm that it works!
Great work, thanks a lot!

Great ! I'll make a pull request

@penfold42
If would really appreciate a wiki article for piblaster hyperion usage - how to :+1:
It seams you know what you do - i have no idea about this :)

/done
Hyperion have a new home!
Please read the announcement post and the changelog for V1.02.0
www.hyperion-project.org
Please have a look at our new wiki! (EN/DE)
wiki.hyperion-project.org
All discussions/questions/development threads should be moved to the new forum!
We will close this issue now

Hey @fhennig
I also have an IKEA Dioder and I'd like to use it with my Raspberry Pi (running RetroPie) as and 'amiblight' clone.
Could you point in the right direction? I've been looking on the Internet and I haven't found any tutorial explicitly for the Dioder and the Raspberry Pi.
Thanks!

Hey,
I haven't set up ambilight but I have set up hyperion to control the dioder strips with the app.
Here is a tutorial for setting up ambilight with hyperion. If you want to use your dioder LEDs you just don't buy the LEDs from the tutorial and instead connect your dioder LEDs. For that you need transistors or a chip with 4 transistors on it ideally. I'm not entirely sure which one I used but I think this one: ULN2003. You can also search for connecting the Dioder to an Arduino, because its basically the same setup. Also google "Darlington", thats the name of the chip type you need.
For hyperion you then need a configuration, I uploaded mine (probably the same as the one mentioned earlier in this issue).
Also I'm not sure which build of the software you need, just read this issue for more info. I hope I could help!
Cheers!

Alright! Thanks a lot!
I'll take a look into all that ;)


[Bug]: JupyterHub tile in Explore section of dashboard

Is there an existing issue for this?

[X] I have searched the existing issues

Current Behavior
In the Explore section of the dashboard, the Jupyter tile is still called JupyterHub
Expected Behavior
Should be called Jupyter
Steps To Reproduce
No response
Workaround (if any)
No response
OpenShift Version
No response
Openshift Version
No response
What browsers are you seeing the problem on?
No response
Open Data Hub Version
No response
Relevant log output
No response

Increasing priority to high since this is a requirement for https://github.com/opendatahub-io/odh-dashboard/issues/213


Class 'Faker' not found

How to use this package in the controller?
I can use this package in seeders,but in controller show this error :
class PFaker Not found
Although i,m add this app.php :
//providers  Ybazli\Faker\FakerServiceProvider::class, //aliases 'PFaker' => Ybazli\Faker\Facades\Faker::class,
i,m define name PFaker instead Faker

Hey @mohsenmehri6101, in the controller you can use like below:
use Ybazli\Faker\Faker;

class testController extends Controller
{
    public function test()
    {
        return (new Faker())->firstName();
    }
}

or:
use Ybazli\Faker\Faker;

class testController extends Controller
{
    private $faker;

    public function __construct()
    {
        $this->faker = new Faker();
    }

    public function test()
    {
        return $this->faker->fullName();
    }
}

If this code block helps you please don't forget to close this issue.
Happy Coding


Tooltips & Utilities

Me again :)
I've added the tooltip methods and most of the utilities methods.
If you have comments - docs or anything i missed would make changes gladly.
S.

Tried to push directly in this branch again, might've broken something tho :)
Anyways, i'm trying to setup my docs system so that i can see the screenshots and the full docs generated. Still having some issues, but hopefully i'll get it running.
S.

Don't worry! Pushing to the same branch is completely fine. Actually, it is a recommended practice because allows to reliably track new changes and review comments.


CRITICAL: Notice: Undefined index: dataScopePrefix

Hi
I am getting below error on checkout page
[2019-04-23 07:10:21] report.CRITICAL: Notice: Undefined index: dataScopePrefix in /var/www/html/fatcat/vendor/magento/module-customer-custom-attributes/Block/Checkout/LayoutProcessor.php on line 72 [] []

Is this issue solved yet? I'm also facing the same

Facing same issue, Is there any solution?

Yes I have fixed it but I don't remember how i fixed it but if you need code I can provide my code. for city dropdown

Please, It will help me to debug at my end also.

Sure no issue. will send you code by tomorrow. just give me a reminder tomorrow.

Sure

Also I would like you to join our page https://www.facebook.com/phpdevelopers and spread over your friends, I have created this page to keep updated people about new openings for php and magento developers so needed people can get jobs and also we are posting latest tech news daily basis.
Appreciate if you like to contribute your few secs for us.

could you please give me your code so if it help me to resolve my issue

`<?php
namespace Namespace\Checkout\Plugin\Checkout;
use Magento\Checkout\Block\Checkout\LayoutProcessor;
use Namespace\Checkout\Helper\Data;
/**

Add area
*/
class LayoutProcessorPlugin
{
/**

@var Data
*/
protected $helper;

/**

LayoutProcessor constructor.
@param Data $helper
*/
public function __construct(Data $helper)
{
$this->helper = $helper;
}

/**

@param \Magento\Checkout\Block\Checkout\LayoutProcessor $subject

@param array $jsLayout

@return array
*/
public function afterProcess(
LayoutProcessor $subject,
array  $jsLayout
) {
$jsLayout['components']['checkout']['children']['steps']['children']['shipping-step']['children']
['shippingAddress']['children']['shipping-address-fieldset']['children']['drop_down'] = [
'component' => 'Ffc_Checkout/js/form/element/city',
'config' => [
'customScope' => 'shippingAddress',
'template' => 'ui/form/field',
'elementTmpl' => 'ui/form/element/select',
'id' => 'city',
],
'dataScope' => 'shippingAddress.city',
'label' => 'Area',
'provider' => 'checkoutProvider',
'visible' => true,
'validation' => [
"required-entry"    => true,
],
'sortOrder' => 110,
'id' => 'city',
'options' => [
[
'value' => '',
'label' => 'Please Select',
],
]
];
if (isset($jsLayout['components']['checkout']['children']['steps']['children']['shipping-step']
['children']['shippingAddress']['children']['shipping-address-fieldset']['children'])) {
$jsLayout['components']['checkout']['children']['steps']['children']['shipping-step']
['children']['shippingAddress']['children']['shipping-address-fieldset']['children']
['telephone'] = $this->helper->telephoneFieldConfig("shippingAddress");
}
// Added auto completion address field for google address suggestion
$jsLayout['components']['checkout']['children']['steps']['children']['shipping-step']
['children']['shippingAddress']['children']['shipping-address-fieldset']['children']
['street']['children'][0]['component'] = 'Amasty_Checkout/js/form/element/autocomplete';
return $jsLayout;
}
}//end class
`

Hi! Do I need to solve the same problem @hiteshgb  can you tell me how to add this class in this extension? thanks!

@Elema82  You need to add code as per your requirement not complete class as it is as per my store. Please let me know if still you are facing issue.

@hiteshgb  thanks. yes, I founded this error when I tried to enter on the checkout.
I modified the file 'Eadesigndev\RomCity\Plugin\Checkout\BillingAddressLayoutProcessor.php' on line 50 and I added this line:
''dataScopePrefix' => 'shippingAddress' "
and I still with the same error.
On my store I have magento 2.3.3 version

okay allow me some time I will give you the solution to fix it. please let me know if you are using CE or EE version.

I'm working with magento cloud, I think that is the enterprise edition

hi @hiteshgb I added on this file Eadesigndev/RomCity/Plugin/Checkout/BillingAddressLayoutProcessor.php line 87 :
        $this->result['components']['checkout']['children']['steps']['children']['billing-step']['children']         ['payment']['children']['payments-list']['children'][$paymentMethodForm]['dataScopePrefix'] = 'customCheckoutForm';
and I dont see the warning again

okay so its working fine now?

this warning? its ok, I found other bugs

Any Update here ? I am also facing same issue.

@Elema82 did you ever find the root cause of this problem? I'm facing this issue as well on Magento Commerce 2.4.2.

hi @hiteshgb I added on this file Eadesigndev/RomCity/Plugin/Checkout/BillingAddressLayoutProcessor.php line 87 :
 $this->result['components']['checkout']['children']['steps']['children']['billing-step']['children'] ['payment']['children']['payments-list']['children'][$paymentMethodForm]['dataScopePrefix'] = 'customCheckoutForm';
and I dont see the warning again

This seems to be a reasonable quick fix for now. It works for me. Thank you!


"Failed awaiting on state barrier"

Related to PR #127 and https://github.com/stealthly/go_kafka_client/commit/5b92ab37c8e3d2588c37ae671679fc78a4e5a6d8
We're seeing our staging environment produce the following log lines 3 minutes after startup:
2015-07-20/18:57:13 [ERROR] [zk] Failed awaiting on state barrier 705508e0b7ca3fc982c5f75af1d557bb [Timedout waiting for consensus on barrier path /consumers/scancheckgroup/api/rebalance/705508e0b7ca3fc982c5f75af1d557bb]
2015-07-20/18:57:43 [ERROR] [zk] Failed awaiting on state barrier 2ef6195d0b05c12077b7e7f12cf2b387 [Timedout waiting for consensus on barrier path /consumers/scancheckgroup/api/rebalance/2ef6195d0b05c12077b7e7f12cf2b387]
2015-07-20/18:57:54 [ERROR] [zk] Failed awaiting on state barrier 507988448b8ba0e9bb84ea28650fcaba [Timedout waiting for consensus on barrier path /consumers/scancheckgroup/api/rebalance/507988448b8ba0e9bb84ea28650fcaba]
2015-07-20/18:58:20 [ERROR] [zk] Failed awaiting on state barrier 01ec42775cf5701877fd78db18e05c90 [Timedout waiting for consensus on barrier path /consumers/scancheckgroup/api/rebalance/01ec42775cf5701877fd78db18e05c90]
2015-07-20/18:58:20 [ERROR] [zk] Failed awaiting on state barrier 01ec42775cf5701877fd78db18e05c90 [Timedout waiting for consensus on barrier path /consumers/scancheckgroup/api/rebalance/01ec42775cf5701877fd78db18e05c90]
2015-07-20/18:58:20 [ERROR] [zk] Failed awaiting on state barrier 01ec42775cf5701877fd78db18e05c90 [Timedout waiting for consensus on barrier path /consumers/scancheckgroup/api/rebalance/01ec42775cf5701877fd78db18e05c90]
2015-07-20/18:58:20 [ERROR] [zk] Failed awaiting on state barrier 01ec42775cf5701877fd78db18e05c90 [Timedout waiting for consensus on barrier path /consumers/scancheckgroup/api/rebalance/01ec42775cf5701877fd78db18e05c90]
2015-07-20/18:58:20 [ERROR] [zk] Failed awaiting on state barrier 01ec42775cf5701877fd78db18e05c90 [Timedout waiting for consensus on barrier path /consumers/scancheckgroup/api/rebalance/01ec42775cf5701877fd78db18e05c90]
2015-07-20/18:58:20 [ERROR] [zk] Failed awaiting on state barrier 01ec42775cf5701877fd78db18e05c90 [Timedout waiting for consensus on barrier path /consumers/scancheckgroup/api/rebalance/01ec42775cf5701877fd78db18e05c90]
2015-07-20/18:58:20 [ERROR] [zk] Failed awaiting on state barrier 01ec42775cf5701877fd78db18e05c90 [Timedout waiting for consensus on barrier path /consumers/scancheckgroup/api/rebalance/01ec42775cf5701877fd78db18e05c90]
2015-07-20/18:58:20 [ERROR] [zk] Failed awaiting on state barrier 01ec42775cf5701877fd78db18e05c90 [Timedout waiting for consensus on barrier path /consumers/scancheckgroup/api/rebalance/01ec42775cf5701877fd78db18e05c90]
panic: Could not reach consensus on state barrier.

goroutine 35 [running]:
github.com/stealthly/go_kafka_client.func·013()
    /home/user/src/github.com/stealthly/go_kafka_client/consumer.go:650 +0xb8d
github.com/stealthly/go_kafka_client.inLock(0xc2088305a8, 0xc2083d3f08)
	/home/user/src/github.com/stealthly/go_kafka_client/utils.go:44 +0x51
github.com/stealthly/go_kafka_client.(*Consumer).rebalance(0xc208830580)
	/home/user/src/github.com/stealthly/go_kafka_client/consumer.go:671 +0x73
github.com/stealthly/go_kafka_client.(*Consumer).reinitializeConsumer(0xc208830580)
	/home/user/src/github.com/stealthly/go_kafka_client/consumer.go:295 +0x4e
github.com/stealthly/go_kafka_client.(*Consumer).createMessageStreams(0xc208830580, 0xc2083cd470)
	/home/user/src/github.com/stealthly/go_kafka_client/consumer.go:270 +0x159
created by github.com/stealthly/go_kafka_client.(*Consumer).StartStatic
	/home/user/src//github.com/stealthly/go_kafka_client/consumer.go:112 +0x3c

This happens every time we start the client on that environment... which means we're guessing it's something to do with config within that environment (we're not seeing it in our development environment).
@marcusking01 or others, what information could help us work out the root cause? Or where should we look?

Hi @buro9 can you please post your consumer configs for this and dev environments so we can determine what configs differ? Are they even different? Thanks

Sure, we have basically implemented this lib as per https://github.com/stealthly/go_kafka_client/tree/master/consumers
Our properties file is this:
#Consumer identity
client_id=scancheck
group_id=scancheckgroup
num_consumers=1
topic=scancheck
log_level=warn

#Zookeeper connection settings
zookeeper_connect=:2181
zookeeper_timeout=1s

#workers settings
num_workers=1
max_worker_retries=3
worker_backoff=500ms
worker_retry_threshold=100
worker_considered_failed_time_window=500ms
worker_batch_timeout=5m
worker_task_timeout=1m
worker_managers_stop_timeout=1m

#Rebalance settings
rebalance_barrier_timeout=30s
rebalance_max_retries=4
rebalance_backoff=5s
partition_assignment_strategy=range
exclude_internal_topics=true

#Fetcher settings
num_consumer_fetchers=1
fetch_batch_size=100
fetch_message_max_bytes=5242880
fetch_min_bytes=1
fetch_batch_timeout=5s
requeue_ask_next_backoff=1s
fetch_wait_max_ms=100
socket_timeout=30s
queued_max_messages=3
refresh_leader_backoff=200ms
fetch_metadata_retries=3
fetch_metadata_backoff=500ms

#Offsets settings
offsets_storage=zookeeper
auto_offset_reset=smallest
offsets_commit_max_retries=5

#Deployment
deployment_timeout=0s

The only differences between this and our staging and prod are that staging and prod both have a dot in the topic name, and use multiple comma-delimited zookeeper servers in the connection:
topic=scan.check
zookeeper_connect={a long list of servers}

No other differences exist in the consumer config.

@buro9 We've seen similar issues.  Essentially what is happening is that all of the consumers in your pool are failing to agree on the same barrier id.  The problem we were seeing was that the hosts NEVER all agreed on the same barrier id and thus no one was consuming from kafka.  We introduced a 3 minute timeout to agree on a barrier id where we essentially panic (stopping the service) and rely on supervision to restart the service(s).  The hope is that by everyone going away and coming online at nearly the same time they will agree on a state barrier id.

A bit brute force, but thank you... that works for me. I'll work on getting our environment and ops to accept this as the standard working parameter for the consumer.

@buro9
Agree it's a bit brute force.  Internally there have been a few minor fixes that seem to make things behave better.  We're testing them now and may release a PR when it gets the green light.  Friendly tip, at some point clear out the zk node /consumers/{your_consumer_name}/api/rebalance  I've found that over time the more build up of old barrier ids, the more of a problem rebalance becomes.

@marcusking01 how are you panicking when the barrier times out? I don't see any place in the API where I can trigger that (a callback or something).. are you just doing that on a fork of go_kafka_client ?


DEVMS-3565: Save Analytics Reports inside of analyze/reports

@thecodester please pay attention

If you run npm run check-validation or npm run check-memory, now the reports will be saved in analyze/reports - these reports will be ignored by Git
If you have reports generated earlier, they are placed in the root folder (Tutorials) and no more ignored by Git, so I'd suggest that you remove them to not accidentally push them (yet they will not be added to Git automatically, they will stay untracked).


Update driveitem_delta.md

Fixed confusing messaging on some properties not being returned - it's endpoint specific.

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/rest-api/api/driveitem_delta.md
:white_check_mark:Succeeded
View (>= odsp-graph-online)

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/rest-api/api/driveitem_delta.md
:white_check_mark:Succeeded
View (>= odsp-graph-online)

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


operator smilecdr (0.0.1)

New operator bundle
Name: smilecdr
Version: 0.0.1
Certification project: 61b0d1f1b5936597314c909c
Test result URL: https://catalog.redhat.com/api/containers/v1/projects/certification/test-results/id/61f43c9d3f544ac7a5ad655d
Test logs URL: https://catalog.redhat.com/api/containers/v1/projects/certification/artifacts/id/61f43c9a00f775b16c0921ba

Closing for a new package name.


NIFI-12095 Increase default Xmx to 1g

Summary
NIFI-12095
Tracking
Please complete the following tracking steps prior to pull request creation.
Issue Tracking

[x] Apache NiFi Jira issue created

Pull Request Tracking

[x] Pull Request title starts with Apache NiFi Jira issue number, such as NIFI-00000
[x] Pull Request commit message starts with Apache NiFi Jira issue number, as such NIFI-00000

Pull Request Formatting

[x] Pull Request based on current revision of the main branch
[x] Pull Request refers to a feature branch with one commit containing changes

Verification
Please indicate the verification steps performed prior to pull request creation.
Build

[x] Build completed using mvn clean install -P contrib-check

[ ] JDK 21

Licensing

[ ] New dependencies are compatible with the Apache License 2.0 according to the License Policy
[ ] New dependencies are documented in applicable LICENSE and NOTICE files

Documentation

[ ] Documentation formatting appears as expected in rendered files

LGTM, merging to main and support/nifi-1.x

+1 merging to main and support/1.x


Fix bug #761, NERTagger stops tagging at first: ? ! .

Fix bug #761,
(1) If output of tag is more than one sentence => join them
(2) Disable Stanford tokenizer

The implementation of tag looks inefficient:
    def tag(self, tokens):
        temp = self.tag_sents([tokens])
	# Handle the case where return more than one sentence.
        # Note that if it is the case, user should use tag_sents instead
        result = []
        for sent in temp:
            result += sent
	return result

I'm replacing it with the following:
    def tag(self, tokens):
        return list(self.tag_sents([tokens]))

Can you explain why the former is preferable?