New project to develop free (as in freedom) versions of GPRS_C_SDK and CSDTK

Hello everyone,
As many of you might already know, Ai-Thinker has abandoned this repository and CSDTK for more than two years, with various critical issues still unresolved. So during the last few weeks I have been taking notes on how the A9, GPRS_C_SDK and CSDTK work. Then I found the firmware blobs used by the A9 that contain the bootloader, GSM/GPRS stacks, HAL and many other useful resources were released with full debug information (code was compiled using the -g flag), which makes it easier to reverse-engineer. This means it is possible to write a free (as in freedom) alternative to all the proprietary tools and firmware blobs released by Ai-Thinker that the community can benefit from.
So I have set up a repository at https://github.com/XaviDCR92/a9_free that compiles all the information I have found so far about the A9 and A9G. These are very complex pieces of hardware, so help is definitely wanted. Anyone interested in making stuff with the A9/A9G should come by and help this project becoming a reality.
So please join in our mission to free the A9 and A9G!

Thank you very much @XaviDCR92 for this.
Just wanted to point that  RDA8955 libraries has been published on github https://github.com/cherryding1/RDA8955_W17.44_IDH
but without toolchain nor a documentation.
There is so many issues in the software but the hardware is absolutely amazing.
Cheers

Thank you very much @faithware for the link - I was not aware of it. However, most of its files are under a proprietary license (example), so unfortunately we cannot use this. Actually, I don't know where the repository author got this repository from as I cannot find any other references on the Internet.
So I have written the following e-mail to Unisoc (who bought RDA Technologies) through their contact form:

Dear Unisoc Team,
I have been lately interested in one of your products, the RDA8955, which is featured on the A9 and A9G products designed by Ai-Thinker, who provide an open source toolchain (namely GPRS_C_SDK) on their Github account, allowing users to write and flash their own firmware into the microcontroller.
However, they rely on a pair of proprietary binaries that contain the logic for the most important aspects of the microcontroller, such as the bootloader, the GSM/GPRS modem, the C standard library, third-party libraries and HAL. Unfortunately, the repository has been abandoned by Ai-Thinker since 2018 and there are many reported issues, some of them critical security issues, that are affected by these unmaintained binaries.
We the community think the RDA8955, as well as the A9 and A9G, have great potential for many IoT solutions and deserve better. There is another Github repository, namely RDA8955_W17.44_IDH, that apparently includes the source code of these binaries. Unfortunately, the whole repository is under a proprietary license from RDA Technologies.
Therefore, we the community want to solve this situation by requesting you, the copyright holder, to release all the source code from these two repositories under a free license such as the Apache, MIT, BSD or GPLv3 licenses, as well as the toolchain distributed by Ai-Thinker as CSDTK (which includes binaries of GPLv3-licensed tools modified by RDA Technologies such as the GNU toolchain, whose source must be distributed according to the license terms), so we can improve upon the existing source code and make the RDA8955 more accessible and safer against vulnerabilities. I hope you understand the benefits this brings to both you and the community.
Thank you very much for your attention.

I am not sure to get any response from them, but I encourage you all to contact them so we can convince them to release their repositories under free licenses so we can maintain them. Feel free to copy the e-mail above and send it to Unisoc and Ai-Thinker.

I'd been trying to work out how to make calls to some of the functions that are in the elf binary but not exposed through the API. e.g. in the binary are USB host library functions.
As part of that digging I came across the AliOS source which contains an RDA8955 tree:
https://code.aliyun.com/alios_bull/alios/tree/dd836abd6fde8ce0a2d7cfa94cbfd4f73d970e1f/platform/mcu/rda8955
but I didn't have time to get any further working out how any of that could be built or used.

Hi guys,
I think we should probably email unisoc all of us.
Cheers

I'd been trying to work out how to make calls to some of the functions that are in the elf binary but not exposed through the API. e.g. in the binary are USB host library functions.

That should be possible by following these steps:

Use mips-elf-objdump -Wi, Ghidra (might not yield correct results) or any other reverse-engineering tool on SW_V2129_csdk.elf.
Figure out the function signature and address for the function(s) to call. For example, I used mips-elf-objdump -Wi on the following function:
void hal_UsbEpEnableInterrupt(UINT8 ep, BOOL enable); (Ghidra swaps its parameters, showing void hal_UsbEpEnableInterrupt (uint param_1, char param_2) instead)
Address: 0x88073334 (both returned the same)
Place this function signature on any header file inside your project.
Insert function address and name via a PROVIDE instruction in your linker script. According to https://github.com/XaviDCR92/a9_free/blob/ff41e4cefed93aaac86f02f7041f079726d8d4b0/doc/notes.txt#L72 , the project-specific linker script is generated from gprs_c_sdk/platform/compilation/cust.ld, so add the following line inside SECTIONS:
PROVIDE(hal_UsbEpEnableInterrupt = 0x88073334);

Now you should be able to call the function as usual.

As part of that digging I came across the AliOS source which contains an RDA8955 tree:
https://code.aliyun.com/alios_bull/alios/tree/dd836abd6fde8ce0a2d7cfa94cbfd4f73d970e1f/platform/mcu/rda8955
but I didn't have time to get any further working out how any of that could be built or used.

Sounds very interesting, but it is unfortunately also released under proprietary licenses.

Hi guys,
I think we should probably email unisoc all of us.

Please everyone feel free to do so - use my example mail from above if needed. I have not received any response from Unisoc or Ai-Thinker yet, but the more we contact them, the more chances we have to achieve our mission.

I have written a tool which converts 8955_hard.xml, a file bundled with the csdtk package which describes register information, into HTML so it is more readable.
The generated HTML file is rather large (~3 MiB) so I have uploaded a compressed version here so you can read it for yourself. Some comments from the XML are still missing due to how they are laid out (see example here), but still this should help users to understand how the RDA8955 works internally.
Compressed HTML output:
rda8955_register_map.zip

In the process of figuring out the HST protocol I've got a proof of concept code that can be used to extract flash contents directly over UART HST.
It's slow (does one word at a time since I was still trying to understand how to get it working)
https://github.com/ihewitt/ivrtrack/blob/main/util/dump.c
also only after writing it did I figure out which bytes are the command so it's not as generic as it should be.

@ihewitt , I have tried your dump tool but it stops receiving at random points (less than 1000 bytes). I added the following two lines in the main loop to get progress information.
for (size_t word = 0; word < size / 4; word++) {
    printf("\r%u/%u", word, size / 4);
    fflush(stdout);

That also happens with coolwatcher sometimes. Any ideas?

Hmm, it was only a proof of concept, the serial receive needs completely reworking really now I know how it's arranged.
It was working reliably, consistently for me. Try increasing the usleep before the read. Odd that you'd be getting that with coolwatched also though, make sure coolwatcher is disconnected when it runs.
The attached will try to do nonblocking, but retry over and over on the read, give that a spin.
dump.diff.txt

Thanks for your help! I have just realized the FTDI was connected to a USB hub shared with other peripherals and plugging the FTDI into its own port immediately solved it - no delay was needed at all, not even the usleep(700) before read on getWord.
BTW, Your tool was using some C++ features that weren't mandatory, so I have slightly modified it to work with a C compiler.
dump.zip

@XaviDCR92 is there any news about RDA email?
Cheers

@faithware Unfortunately neither Ai-Thinker or Unisoc have replied so far.

@ihewitt , I have done some experimentation with the commands used by coolwatcher and your tool and now I have a better understanding of the HST protocol. However, I still do not know how to modify the SPI flash. coolwatcher provides a clearSpiFlash command, but seems to do nothing, whereas apparently w32 can only be used for read/write memory e.g.: RAM.

Hi,
I can't even find a link to download CSDTK4.2, which I gather is the toolchain for using the c sdk.
Does anyone know where I can get it? Ideally for windows, but I guess Linux would do.
Thanks!

Hi,
I can't even find a link to download CSDTK4.2, which I gather is the toolchain for using the c sdk.
Does anyone know where I can get it? Ideally for windows, but I guess Linux would do.
Thanks!

@devmattr see: https://github.com/zkemble/GPRS_C_SDK/releases/tag/v2.129

@devmattr see: https://github.com/zkemble/GPRS_C_SDK/releases/tag/v2.129

New interesting repo:
Huge code size
https://github.com/ReleaseBug/RDA8955_W17.44_IDH

@ens4dz  have you tried that?


Extend this for Kaggle Kernels?

Thanks for your feedback. I will try if i can make it work on kaggle notebook :)

I am sorry to say, after my survey, kaggle does not support proxy the port to external. And i also try if tensorboard can do it, i found kaggle has dropped the support for this kind of proxy.


Driver: add support for the WebAssembly toolchain

WebAssemblyToolChains.cpp is added to the Driver with a basic toolchain for WebAssembly. This supports building and linking Swift code that targets WebAssembly.

Resolves a part of SR-9307.

CC @kateinoigakukun

@swift-ci please smoke test

@swift-ci please smoke test

@swift-ci please smoke test

Could you add driver test for this toolchain using --driver-print-jobs ?

@swift-ci please smoke test

@swift-ci please smoke test

@swift-ci please smoke test

@swift-ci please smoke test

@swift-ci please smoke test

@swift-ci please smoke test

@swift-ci please test


Remove: mpark-variant

With most codes transitioned to C++17, especially the ones that I maintain and added this package for, we don't need mpark-variant anymore for development environments.
Thanks and kudos!! :sparkling_heart:
Let me know if I also shall update some .yaml files. I cannot spot where the "E4S-next" release list is currently located.

Ill defer this to @sameershende @maherou. I personally don't know this package and no one has asked for this package at NERSC based on our ticket history

@sameershende @wspear Following up on this, is it OK to remove mpark-variant as suggested? Are we aware of anyone else needing this?


fix(website): listStyleType examples

Summary
The listStyleType examples on the website look like this:

The problem is that smooth-doc supplies a nested style for unordered lists, and <x.div> can't override it.
Test plan
Make a PR and see if it worked :stuck_out_tongue_winking_eye:

@gregberge You wanna fix the deploys?
1:30:08 PM: Can't resolve 'react-simple-code-editor' in '/opt/build/repo/website/src/smooth-doc/components'


arch board feedback

Description
Please add an informative description that covers that changes made by the pull request and link all relevant issues.
If an SDK is being regenerated based on a new swagger spec, a link to the pull request containing these swagger spec changes has been included above.
All SDK Contribution checklist:

[ ] The pull request does not introduce [breaking changes]
[ ] CHANGELOG is updated for new features, bug fixes or other significant changes.
[ ] I have read the contribution guidelines.

General Guidelines and Best Practices

[ ] Title of the pull request is clear and informative.
[ ] There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For more information on cleaning up the commits in your PR, see this page.

Testing Guidelines

[ ] Pull request includes test coverage for the included changes.

API changes have been detected in com.azure:azure-storage-blob. You can review API changes here
API changes
-         public boolean getRetrieveSystem()
-         public BlobContainerListDetails setRetrieveSystem(boolean retrieveSystem)
+         public boolean getRetrieveSystemContainers()
+         public BlobContainerListDetails setRetrieveSystemContainers(boolean retrieveSystemContainers)

API changes have been detected in com.azure:azure-storage-file-share. You can review API changes here
API changes
-         public Integer getProvisionedEgressMBps()
-         public ShareProperties setProvisionedEgressMBps(Integer provisionedEgressMBps)
-         public Integer getProvisionedIngressMBps()
-         public ShareProperties setProvisionedIngressMBps(Integer provisionedIngressMBps)
+         @Deprecated public Integer getProvisionedEgressMBps()
+         @Deprecated public ShareProperties setProvisionedEgressMBps(Integer provisionedEgressMBps)
+         @Deprecated public Integer getProvisionedIngressMBps()
+         @Deprecated public ShareProperties setProvisionedIngressMBps(Integer provisionedIngressMBps)

API changes have been detected in com.azure:azure-storage-file-datalake. You can review API changes here
API changes
-         public boolean getRetrieveSystem()
-         public FileSystemListDetails setRetrieveSystem(boolean retrieveSystem)
+         public boolean getRetrieveSystemFileSystems()
+         public FileSystemListDetails setRetrieveSystemFileSystems(boolean retrieveSystemFileSystems)


[WIP] Value generics

This implements the feature described in the GenericsManifesto here: https://github.com/swiftlang/swift/blob/main/docs/GenericsManifesto.md#generic-value-parameters
One can introduce a value generic parameter by marking the type let in the generic parameter clause:
struct MyType<let N: Int>

and you must declare the value type that this is a value for. At the moment this is limited to Int (but I've left the door open to "easily" expanding it for potential future directions). You can specialize a type with a value generic with an integer literal or by passing another value generic with the same underlying value type:
func test1(with myType: MyType<128>) {
  ...
}

func test2<let M: Int>(with myType: MyType<M>) {
  ...
}

This is still a WIP.

@swift-ci please smoke test

@swift-ci please smoke test

https://github.com/swiftlang/llvm-project/pull/9030
@swift-ci please smoke test

Please test with following pull request:
https://github.com/swiftlang/llvm-project/pull/9030
@swift-ci please smoke test

Please test with following pull request:
https://github.com/swiftlang/llvm-project/pull/9030
@swift-ci please smoke test

Please test with following pull request:
https://github.com/swiftlang/llvm-project/pull/9030
@swift-ci please smoke test

Please test with following pull request:
https://github.com/swiftlang/swift-syntax/pull/2785
https://github.com/swiftlang/llvm-project/pull/9030
@swift-ci please smoke test

Please test with following pull request:
https://github.com/swiftlang/swift-syntax/pull/2785
https://github.com/swiftlang/llvm-project/pull/9030
@swift-ci please smoke test

Please test with following pull request:
https://github.com/swiftlang/swift-syntax/pull/2785
https://github.com/swiftlang/llvm-project/pull/9030
@swift-ci please smoke test

Please test with following pull request:
https://github.com/swiftlang/swift-syntax/pull/2785
https://github.com/swiftlang/llvm-project/pull/9030
@swift-ci please smoke test

Please test with following pull request:
https://github.com/swiftlang/swift-syntax/pull/2785
https://github.com/swiftlang/llvm-project/pull/9030
@swift-ci please smoke test

Please test with following pull request:
https://github.com/swiftlang/swift-syntax/pull/2785
https://github.com/swiftlang/llvm-project/pull/9030
@swift-ci please test

Please test with following pull request:
https://github.com/swiftlang/swift-syntax/pull/2785
https://github.com/swiftlang/llvm-project/pull/9030
@swift-ci please smoke test Linux

Please test with following pull request:
https://github.com/swiftlang/swift-syntax/pull/2785
https://github.com/swiftlang/llvm-project/pull/9030
@swift-ci please test

Please test with following pull request:
https://github.com/swiftlang/swift-syntax/pull/2785
https://github.com/swiftlang/llvm-project/pull/9030
@swift-ci please test macOS

Please test with following pull request:
https://github.com/swiftlang/swift-syntax/pull/2785
https://github.com/swiftlang/llvm-project/pull/9030
@swift-ci please test

Please test with following pull request:
https://github.com/swiftlang/swift-syntax/pull/2785
https://github.com/swiftlang/llvm-project/pull/9030
@swift-ci please test

CC @rauhul

I'd be happy to give this a spin in swift-mmio and swift-embedded-examples when you need early adopters!

Please test with following pull request:
https://github.com/swiftlang/swift-syntax/pull/2785
https://github.com/swiftlang/llvm-project/pull/9030
@swift-ci please test

Please test with following pull request:
https://github.com/swiftlang/swift-syntax/pull/2785
https://github.com/swiftlang/llvm-project/pull/9030
@swift-ci please test

Please test with following pull request:
https://github.com/swiftlang/swift-syntax/pull/2785
https://github.com/swiftlang/llvm-project/pull/9030
@swift-ci please test Windows


./swarmdb --help doesn't show help

$ ./swarmdb -h
NotFound$~~~~~~~~~~
no replica found (.swarmdb)

$ ./swarmdb --help
NotFound$~~~~~~~~~~
no replica found (.swarmdb)

fixed, thanks


multiple time axis files can have confusing timestamp

With model level data from the AUS2200 files have two time axis, for example
each file at 1200 hours have variable defined at 1200 hours but also variable defined at 1300 hour.
This causes issue when only timestamp is used to work out time range. So adding check in get_timedim to returned if multiple times are in axis
and then using check_in_range instead of check_timestamp if multiple_times is True.
This seems to work but we also have to now adapt the set(time) after calculation to make sure we're not cutting off day after at 00 hour where this occurs.
So in cli.py
dsin = dsin.sel({time_dim: slice(ctx.obj['tstart'], ctx.obj['tend'])})
and later on
out_var = out_var.sel({time_dim: slice(ctx.obj['tstart'], ctx.obj['tend'])})

fixed in 189ad2a3743464a77c1c45103d3b89172d2a5f27


Better support for RGB-D data

RGB-D data provides colored point clouds that can be input into Cartographer for scan matching (which would currently ignore  the color information). However the results are quite bad. The current theory is that the noise model of RGB-D cameras is different from that of laser scanners (the depth uncertainty in RGB-D increases steeply with depth, less so for laser scanners).
We should invest more thought into this and find a way to reliably scan match against RGB-D data.

Related and possible interesting for tuning: googlecartographer/cartographer_ros#318

I understand the color will be ignored in scan matching, but for a successful rgbd mapping, will the color information remain in the map with the asset_writer?

@Changliu52 If it is in the bag, it will also be used in the asset writer.

Perfect! Great. Thank you very much.
Chang

On 6 Nov 2017, at 08:17, Holger Rapp<EMAIL_ADDRESS>wrote:
@Changliu52 https://github.com/changliu52 If it is in the bag, it will also be used in the asset writer.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/googlecartographer/cartographer/issues/545#issuecomment-342075776, or mute the thread https://github.com/notifications/unsubscribe-auth/AEdVxe_WdzbPFnpv_FvRb8Sya0wuaf9Tks5szsCtgaJpZM4PmymX.

Duplicate of #33


Provide support for Cyrillic characters

I checked it locally with Russian and Ukrainian languages and it works fine

Thanks!


chore: upgrade github actions

the failures seem unrelated to this PR
dropped node 14 since svelte 4 only supports node 16+

closing in favor of https://github.com/sveltejs/svelte-hmr/pull/72 since commit was included there


Release 0.7.2

With multiple important issues fixed since the last release, I think it's time to consider a new one.
This time let's not forget the version number! (slaps self)
Anyone object? Any last requests?

Insert gentle reminder about 0.7.2.

Uploaded 0.7.2 to LuaRocks since it's tagged.


docs: update CONTRIBUTING.md for pnpm usage instead of yarn

While trying to come up to speed with Analog development I realized the contribution doc was out of date, mentioning yarn being used while the project has migrated to pnpm. This PR corrects the information on the manager to use, as well as addresses and adds other minor improvements based on Discord conversations.
PR Checklist
Please check if your PR fulfills the following requirements:

[X] The commit message follows our guidelines: https://github.com/analogjs/analog/blob/main/CONTRIBUTING.md#-commit-message-guidelines
[ ] Tests for the changes have been added (for bug fixes / features)
[X] Docs have been added / updated (for bug fixes / features)

PR Type
What kind of change does this PR introduce?

[ ] Bugfix
[ ] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] CI related changes
[X] Documentation content changes
[ ] Other... Please describe:

Which package are you modifying?

[ ] vite-plugin-angular
[ ] vite-plugin-nitro
[ ] astro-angular
[ ] create-analog
[ ] router
[ ] platform
[X] content
[ ] nx-plugin
[ ] trpc

What is the current behavior?

Closes #
What is the new behavior?
Does this PR introduce a breaking change?

[ ] Yes
[X] No

Other information
[optional] What gif best describes this PR or how it makes you feel?

Thanks! @allcontributors add @jeremyhofer for doc


Media modal requires selecting twice

Bug Description
Selecting an asset in the media modal requires two clicks.
Expected Behaviour
I should be able to select an image the first time around.
Steps to Reproduce

Add new text element with link
Click on brand icon placeholder to select image from media modal
Media modal opens with Upload Files tab open
Click on Media Gallery tab, choose an image and click on Select as link icon
⚠ Jump back to Upload Files tab
Click on Media Gallery tab again, choose an image and click on Select as link icon
Now it works! Media modal is closed and link icon is applied.

This also applies to other cases, not just the link brand icon

Do not alter or remove anything below. The following sections will be managed by moderators only.
Acceptance Criteria
QA Instructions

@swissspidy @wassgha
It doesn't actually require selecting twice, it just triggers opening the media modal twice due to having the onClick both on wrapper and on the icon, should be on icon only. It's also fixed in https://github.com/google/web-stories-wp/pull/667:
https://github.com/google/web-stories-wp/pull/667/files#diff-7efe0f7281e890ed858014270c3fd845L157

Closing as fixed within #667


Fixes IPython notebook title margin.

This PR remove margins from leaflet-tiles in the IPython notebook template to fix an offset in the first tile.  The solution is thanks to @lennart0901 who fixed that for folium.
Before,

and another after the fix

Awesome!! Thanks @ocefpaf!
Closes #2 and #3 too.


Todo Application

An app where you can plan your project with todo card.

@bellom , @Torres-ssf thanks for the reviews.


az webapp deployment using zip file fails

az feedback auto-generates most of the information requested below, as of CLI version 2.0.62

Describe the bug
az webapp deployment fails ,
Following not very friendly error is coming
WARNING: Getting scm site credentials for zip deployment
null_resource.run_script_curl (local-exec):   0     0    0     0    0     0      0      0 --:--:--  0:00:03 --:--:--     0
WARNING: Starting zip deployment. This operation can take a while to complete ...
ERROR: The command failed with an unexpected error. Here is the traceback:
ERROR: ('Connection aborted.', OSError(0, 'Error'))
Traceback (most recent call last):
File "/opt/az/lib/python3.6/site-packages/urllib3/connectionpool.py", line 706, in urlopen
chunked=chunked,
File "/opt/az/lib/python3.6/site-packages/urllib3/connectionpool.py", line 382, in _make_request
self.validate_conn(conn)
File "/opt/az/lib/python3.6/site-packages/urllib3/connectionpool.py", line 1010, in validate_conn
conn.connect()
File "/opt/az/lib/python3.6/site-packages/urllib3/connection.py", line 421, in connect
tls_in_tls=tls_in_tls,
File "/opt/az/lib/python3.6/site-packages/urllib3/util/ssl.py", line 450, in ssl_wrap_socket
sock, context, tls_in_tls, server_hostname=server_hostname
File "/opt/az/lib/python3.6/site-packages/urllib3/util/ssl.py", line 493, in _ssl_wrap_socket_impl
return ssl_context.wrap_socket(sock, server_hostname=server_hostname)
File "/opt/az/lib/python3.6/ssl.py", line 407, in wrap_socket
_context=self, _session=session)
File "/opt/az/lib/python3.6/ssl.py", line 817, in init
self.do_handshake()
File "/opt/az/lib/python3.6/ssl.py", line 1077, in do_handshake
self._sslobj.do_handshake()
File "/opt/az/lib/python3.6/ssl.py", line 689, in do_handshake
self._sslobj.do_handshake()
OSError: [Errno 0] Error
To Reproduce
az webapp deployment source config-zip -g $FUNC_APP_RESOURCE_GROUP -n $FUNC_APP_NAME --src $FUNC_APP_PACKAGE_SRC
Expected behavior
it should publish the package
Environment summary
azure-cli                         2.25.0 *
core                              2.25.0 *
telemetry                          1.0.6
Extensions:
azure-devops                      0.18.0
I am using consumption plan, with Windows.
Additional context
Why this is so unstable?.

route to CXP team

@na-init Apologies for the late reply. Could you please confirm if there is any corporate proxy in your environment? If Yes, then you should follow the steps mentioned in this article to make the AzCLI work via proxy.
Alternatively to test the functionality, you can try to run the command from another machine which is not in your corporate network (without the proxy) and try to run the command again? and check if that helps.
On a side note, please use the most recent version of the Azure CLI to perform the test. Awaiting your reply.

@na-init I wanted to do quick follow-up to check if you had a chance to look at my above comment. Please let us know if you need any further assistance on this. Awaiting your reply.

@na-init I hope you had a chance to follow the suggested action plan in above comment. We will now proceed with closure of this github issue. If you need any further assistance on this issue in future, please feel free to reopen this thread. We would be happy to help.


Dictionary view in Jadite should have way to expose transient symbol list

If you actually do put symbol dictionaries into the transient symbol list, they cannot be browser using the System Browser ... it should be possible to choose to view the transient symbol dictionary. See Issue #212 for a tangible use case

along these same lines, senders and implementers should be based off of the transient symbol list as well ...


intents dont work?

im still struggling with this - while changing the URL in your script from homeassistant.local to homeassistant did fix the initial call, I still cannot use the intents at all. when I'm amazon's developer console I can try them out and they seem to work but in the real world they don't at all. instead it's doing web searches or offers me music...
any thoughts? :(
I'm still really new to this... sorry about all the questions. i do really appreciate you putting this on github!

my bad... i didnt use it correctly.


 If we can make the canonical location be the website, and store them in the website repo, we can prevent duplication and the inevitable drift into inconsistency.
Example: https://github.com/openservicemesh/osm-docs/pull/39
To do: find all such examples in this repo.

Resolving as there has been significant change since I opened this.


Purge one time run containers from UI

Raising to issue to ask whether there's already an auto-purge setting, if not feature request.
Rancher Versions:
Server: v1.5.5
Steps to Reproduce:
Create lots of "cron" one time run containers or Jobs in Kubernetes.
Results:
The Hosts page in the Rancher UI is very slow to load and long to scroll down. See example:

I guess workaround is one of the GC tools out there, e.g. https://github.com/flaccid/docker-docker-gc-crond.

With the release of Rancher 2.0, development on v1.6 is only limited to critical bug fixes and security patches.


Condition Refactoring: Map Methods Can Change Datatypes

As is normal, map methods should allow type conversions.

Coverage remained the same at 100.0% when pulling 74f57a205903a4156147508ed6bdfdbac35a0532 on jeffgbutler:map-can-change-type into d468f1f5a2c26532cee31d9170703b0dacbafe94 on mybatis:master.


Android build failure with v2.2.0 - RNDatePickerDialogFragment.java:105: error: missing return statement

Bug
Android fails to build version 2.2.0.
> Task :@react-native-community_datetimepicker:compileReleaseJavaWithJavac FAILED /data/workspace/AndroidReactBuildNew/node_modules/@react-native-community/datetimepicker/android/src/main/java/com/reactcommunity/rndatetimepicker/RNDatePickerDialogFragment.java:105: error: missing return statement   }   ^ Note: Some input files use or override a deprecated API. Note: Recompile with -Xlint:deprecation for details. 1 error
Environment info
React native info output:
  IDEs:
    Android Studio: 3.4 AI-183.6<IP_ADDRESS>22156
    Xcode: 11.3.1/11C504 - /usr/bin/xcodebuild
  npmPackages:
    @react-native-community/cli: ^1.9.5 => 1.12.0
    react: 16.8.6 => 16.8.6
    react-native: 0.60.4 => 0.60.4

Library version: 2.2.0
Steps To Reproduce
Try to build.
Describe what you expected to happen:
App to build successfully.
Reproducible sample code

Getting the same error here.

Same error.

I am returning null as temporary fix not ideal
      DatePickerDialog dialog = new RNDismissableDatePickerDialog(activityContext, onDateSetListener, year, month, day);
      switch (display) {
        case CALENDAR:
          dialog.getDatePicker().setCalendarViewShown(true);
          dialog.getDatePicker().setSpinnersShown(false);
          break;
        case SPINNER:
          dialog.getDatePicker().setCalendarViewShown(false);
          break;
      }
      return dialog;
    }
    return null;
  }

How did a compile a error get past a release... Same issue here, rolling back to 2.1 until then.

Same error. Currently fixed it with installing older version (2.1.0).


show help when options on command line

Is it possible to show the help screen if no options are added to the command line?

If any of the options are required, when you set Required=true in the option attribute constructor it will cause the parser to generate an error. There is unfortunately nothing built in to enforce at least one option while still keeping every option 'optional'.


Extract key backup engine

As part of implementing key backups with Rust-based CryptoSDK I need to separate out shared and distinct backup functionality in the existing codebase. In the past I have simply duplicated a class (MXCrypto, MXKeyVerificationManager) and overriden all of its methods, but this approach is not suitable for backups, because a lot more code ends up being shared (state management, enabling/disabling backups, restoring, sending http requests etc).
The approach I have chosen instead is to identify all of the code specific to native / legacy implementation and refactor it as new MXKeyBackupEngine protocol. At the moment only Native implementation exists, but in a future PR I will add the rust-based variant. It is absent from this PR to make the refactor cleaner and easier to review.
As for the refactor I have copy-pasted entire chunks of code with no or very minimal changes to avoid any regressions. There are some integration tests that cover this functionality, but given the complexity of this code it is best to be extra careful. In reviewing I recommend comparing the deleted and added chunks to confirm there are no behaviour changes.

@aringenbach it seems that codecov has made reviewing this PR quite difficult, in that it annotates almost every line of the refactor. I can disable codecov for the purpose of the review, unless you have some other flow of reviewing (e.g. from local command line)


Distinguishing instructions for RAR-b

Have been discussing with @gowitheflow-1998 how to distinguish results w/ & w/o instructions for RAR-b in the result files & the LB. Two ideas:

We differentiate at the model level. E.g. we have a GritLM-7B & a GritLM-7B-noinstruct folder in the results repo. For models that are no instruct by default, we'd have to add an instruct folder e.g. text-embedding-3-large & text-embedding-3-large-instruct.

Works out of the box when running mteb without overwriting results from the other setup by just specifying the results_folder via the kwargs.
Generalizes nicely to other tasks - e.g. if you want to benchmark GritLM-7B on MTEB or FollowIR without instructions you just put those results in GritLM-7B-noinstruct.
For the LB we could consider adding a Model types filter that says instructions to filter for models that do/do not use instructions. Maybe that way we don't need two tabs anymore for RAR-b & RAR-b No instructions but just put all of them in the same RAR-b tab and then people can filter out for instruction usage similar to how one can filter out Cross Encoders for the FollowIR tab.

We differentiate at the task level. E.g. the files are named RARbMath.json for instructions & RARbMathNoInstruct.json for no instructions.

It would not work nicely out of the box as it would interfere with previously written results unless a new results_folder is specified. But then you still need to rename them and move them back into the same folder which makes it more complex than 1.
Can also generalize to other tasks but requires renaming json files which is a bit more complex than placing it in a different folder. We could have an automatic script for that though but still a bit clunky.
Adds some complexity for the LB because we'd break the behavior that the filename equals the taskname (e.g. the task would likely still be called RARbMath). Also does not work out of the box with our Model types-based filtering and would not allow showing e.g. GritLM-7B no instruction results in the main mteb tab.

So I suggest we go with 1. but lmk if you disagree! Curious about your thoughts @orionw @gowitheflow-1998! 😊

Thanks for kicking off the discussion @Muennighoff @gowitheflow-1998!  I agree we should start updating the leaderboard!
I think the core issue here again is the centrality of the instructions. If the instructions can be changed, if they are model specific, then (1) is a much better choice IMO. However, for FollowIR/InstructIR/other follow up works, the instruction is fixed, it's part of the data. You can't run FollowIR without instructions since the instruction is what defines the query relevance, if that makes sense.
For RAR-B, from what I've understood at looking at the data, the instructions are not part of the data but are part of the model approach (and it is desirable for follow up work to show that better instructions can lead to better models).  This falls in the same bucket as SciFact and others where the goal is to adapt to something using an instruction and that instruction can be model designed and is not part of the data. Correct me if I'm wrong @gowitheflow-1998!

Have been discussing with @gowitheflow-1998 how to distinguish results w/ & w/o instructions for RAR-b in the result files & the LB. Two ideas:

It would not work nicely out of the box as it would interfere with previously written results unless a new results_folder is specified. But then you still need to rename them and move them back into the same folder which makes it more complex than 1.

If I'm understanding correctly, the issue is comparing models that use instructions on retrieval datasets vs those that don't (so GritLM style vs Contriever style). Given that the instructions are model specific for all the current Retrieval tasks (and I think it's a fair point that depending on the instruction, it often leaks dataset info in many cases so it can be a non-fair comparison to those without instructions) then I would probably vote for (1) as well -- splitting the models into categories: models using instructions, models not using instructions.
Because FollowIR and InstructIR cannot be evaluated without instructions, they would only show up in leaderboards where "Models with Instructions" is selected.
This would be a fairly large change -- all GritLM evaluations would be moved to "with instructions" since I assume every value on the leaderboard includes instructions.  I think that's a reasonable move, but something to consider.  I think such a leaderboard would also help show how important the instructions are to the model: if you see a 10 point drop in performance when switching off instructions then you can see the robustness.

We differentiate at the model level. E.g. we have a GritLM-7B & a GritLM-7B-noinstruct folder

Not super on topic, but I think it would be nice if could save the instructions in the run. Both for research purposes and because they have a pretty large impact on performance!

thanks for the detailed discussions! @Muennighoff @orionw
I think both suggestions are great! The only concern for differentiating on the model-level might be aligning/distinguishing with a model's defined setting. e.g., models like BGE are trained with the same instruction for one big task (e.g. sts; retrieval), so depending on the instruction centrality of the task, it is hard to say if the model's default setting corresponds to model-noinstruct or model-instruct when placing the results. It's by default w/ instruction in the sense that they actually do add an instruction, but w/o instruction in the sense that the default instruction is too general and not useful for dataset-based like RAR-b or even example-based tasks and FollowIR @orionw. For such tasks for examples, one would replace BGE's general retrieval instruction and add more specific instructions. Might be in general a concern for tasks that need instructions that are not default to the models. And this poses a misalignment with other previous tasks in defining whether the results should fall under model-instruct or model-noinstruct.
Otherwise I think it makes more sense in the long run to do model-level given its advantages to the repo/LB usage & structure that @Muennighoff mentioned!

it is hard to say if the model's default setting corresponds to model-noinstruct or model-instruct when placing the result

BGE is definitely the outlier on instructions, they are really vague.  FWIW, my guess is that that style of "one instruction for all of retrieval" is not going to be very popular -- I don't even think BGE-M3 has it although I may have missed it. I think we could pick either way for the early BGE models and it wouldn't make too much of a difference.

A minor comment here (otherwise it seems like most aspects are discussed). If 1) then I would probably make sure to also update the model_meta.json file to include the information as well.

@Muennighoff re the recent PR into the results repo, so we all are on the same page.

Default way the model is intended to be used model_name - If model is used in non-default way with instruction add -instruct, w/o instruction add -noinstruct? But if you prefer not leaving the default names as is, we can also consider renaming.

From the above I think I and @gowitheflow-1998 understood it that if models use instructions they get the naming convention of "instructions".  That's why I said above:

This would be a fairly large change -- all GritLM evaluations would be moved to "with instructions" since I assume every value on the leaderboard includes instructions. I think that's a reasonable move, but something to consider. I think such a leaderboard would also help show how important the instructions are to the model: if you see a 10 point drop in performance when switching off instructions then you can see the robustness.

Hence the results Github issue about renaming all models which used instructions.

Default way the model is intended to be used model_name

I think this would work for the model side, but wouldn't work for the task side -- what you suggested as (1) at the beginning of this issue. We could do default and non-default for models, but then we'd have to end up doing something else to differentiate tasks where the models used instructions since default is model-specific.
So it seems we need to have one consistent tag that applies to all models. I'm fine using either non-instruct and normal or instruct and normal -- my preference would be to specifically call out instructions since they're newer and non-standard until the last year but either would work. Either way we have to re-label some set of models to specify the no-instructions or to specify they do use instructions.

On that one note - Why does this PR have bge-base-en-v1.5-instruct? Isn't using the retrieval instruction the default way for bge base and thus the existing results in bge-base-en-v1.5 are with instruction? Sorry maybe I am missing something.

Thus, it has the instruct version attached to the name because it used instructions for rar-b and so we needed a model category for bge-base that used instructions.

Please let me know if this doesn't make sense or if you have alternative suggestions!

Makes sense thanks for the detailed explanation!

I think this would work for the model side, but wouldn't work for the task side

Why wouldn't it work for the task side? The way I understand it is that users will have to rename the folder, no? So if they run with the expected setting for the model (i.e. instructions fro GritLM etc; no instructions for all-MiniLM etc) then they don't rename the folder. If they run with the non-default setting they add -noinstruct or -instruct?
But I'm also fine with also renaming the default folders to include the suffix if you prefer 👍

I think when we talk about instructions, we are talking about dataset-specific or example-specific instructions?
As models like GritLM-7B and e5-mistral-7b-instruct are trained to follow fine-grained instructions, when showing on RAR-b and FollowIR leaderboard, it makes sense they have their original names, as the task settings align with their default settings. When we force them not to take in instructions, it makes sense to call GritLM-7B-noinstruct and e5-mistral-7b-instruct-noinstruct to distinguish with original settings. We can perhaps show noinstruct as a subscript with different fonts on the leaderboard?
The opposite applies to models like all-mpnet-base-v2. I think when it shows in FollowIR, it makes sense to call all-mpnet-base-v2-instruct to show it's not aligning with default settings.
For models like BGE, as it by default has the same instruction for one big task, @orionw and I agree they are not aligning with what RAR-b and FollowIR are doing with instructions, so it makes more sense that their default is defined as noinstruct, therefore bge-base-en-v1.5 and bge-base-en-v1.5-instruct on the leaderboard that requires dataset-level or example-level instructions.
what do you think? @Muennighoff I actually agree newer models should have their original names (without emphasing instruct) because they are originally trained to follow fine-grained instructions, and align with instruction-following tasks. We can perhaps put a short note on the leaderboard?

Bumping up a level of abstraction, I see three reasons for why we'd want to distinguish instructions overall:

We can then filter these instruction tags to create the leaderboard of tasks (one version for models using instructions, one without)
We can compare the same model using instructions vs not-using instructions
We already have a system setup so that if someone uses the non-default setting, we have a place for them to put results (using instructions when they don't normally or vice versa).

The TLDR is I think it's easier to add a consistent tag then one that uses ambiguous "default" that goes in both directions. Whether that's a consistent "-instruct" for models using instructions or we go very explicit and every model gets a "-instruct" or "non-instruct" tag to clear up ambiguity.
For models not in the results folder, I think we'll have to make a mapping in the model_meta that is is_instruct_results or something.

I actually agree newer models should have their original names (without emphasizing instruct)

Ah perhaps this is where the confusion is @gowitheflow-1998 @Muennighoff. For the leaderboard name I think we can easily strip off the suffixes. They can just be there in the results folder we can easily use that when creating the leaderboard.  I agree we don't want to confuse people by naming models that don't exist on HF! :)

I think this would work for the model side, but wouldn't work for the task side

Lets say we go with default and non-default. Then we have Contriever-instruct and GritLM-no-instruct as non-defaults. If someone wanted to filter all models using instructions, we can't use instruct as the filtering mechanism since we'd have to have a mapping of what models use a default.  It seems simplest to just have some naming convention for the results folder that is consistent.
My other concern with a default as the naming convention is that it gets a bit weird when models can do both, which ones is the default? There's a few models like this (I think some BGE ones, would have to double check). My guess is in the future this will also be more common.

For the leaderboard name I think we can easily strip off the suffixes. They can just be there in the results folder we can easily use that when creating the leaderboard. I agree we don't want to confuse people by naming models that don't exist on HF! :)

yeah I think this is where the confusion is! indeed having both in the folder names and stripping them off the suffixes in the leaderboard will work as well.


#308 add Django 3.1 as supported

Just mark Django 3.1 as supported. A quick actual test and Travis both seem to be OK.

Thanks @d9pouces !


kubicorn explain

Using the reconciler pattern we can pull data about what is Actually running and what is Expected to be running...
Being able to run kubicorn explain and get a list of resources for each actual and expected would be handy!
We can output them as a table -o table
or as json --output json -o json
etc
etc
If you'd like to learn more about kubicorn project, you can read The Project Walkthrough.
If you have any question, comment on the issue, join us on the #kubicorn channel in the Gophers Slack community or open a PR. We'll always do everything we can to get the PR though.

Working on this one :)

Submitted PR #509 that should fix this issue


Fix  code-block formatting in usage.rst

Hello.
This code block doesn't look good.

I fixed it.
Love,
Kamil

@mik-laj thanks for spotting this


UI enhancement: Indicate task of operation and others

Hello. Thank you for all the time, effort and love you are putting into this really user-friendly interface.
When we select a file to be processed, we select the model, language and task to be done (Transcription or Translation).
I believe it will be useful perhaps all these parameters are indicated as columns in the Queue table. Currently the Queue table has only 2 columns - File Name and Status. With the current setup, when something goes wrong, I find it difficult to troubleshoot batch file operations, especially if files need to be both translated and transcribed. Thank a lot once again!

Thanks for your kind words! Your suggestion will be added in the next release.


Directory included in pattern matching is confusing

The documentation states that "These tests define a directory to scan for test data, a pattern (a regular expression) to match". However it doesn't make clear that the directory string must match the pattern and also is not automatically prepended to template filenames. This seems like an unexpected choice since the directory appears to be a prefix to the pattern / template definitions.
For example, given a configuration like this, nothing will ever match because the input pattern does not match "src/foo/tests".
#[datatest::files("src/foo/tests", {
    input in r"^(test_.*).in.yml",
    output = r"${1}.out.yml",
})]

Intuitively, the input pattern seems like it should be relative to the directory that is being searched. I was left scratching my head as to why this pattern wasn't matching anything, so at the very least this behavior should be documented. Although it would potentially be a disruptive change, I think it would greatly improve usability if the regex & file templates were applied rooted at the given directory.

I feel you. I myself spent like 30 minutes today figuring out why my pattern didn't work 😀

I was also confused by this, until I found this issue. Once known I just used '/filename$' instead of '^filename$' and it worked.
I'm still a bit confused, because the example in the readme starts with ^ and doesn't include the path in the pattern either. Seems like it wouldn't work, or am I missing something?


HR HTML Tag formatting issue for marked down notes

Hi,
First I should say Notestack rocks! There is one small issue though:
If I use the < hr> tag for pinned down notes, the line below that  tag starts showing the default font and not the font that I'd customized from options menu.
Screehshot:
http://www.freeimagehosting.net/24c79

Thanks for the reply! By pinned down, I meant marked down! I didn't try in non marked down notes, just marked down notes.
Also I tried the methods mentioned in http://daringfireball.net/projects/markdown/syntax#hr
When I use the ----, the text above this line becomes like H1 or H2.
But if I use anything else

HR is drawn perfectly as you've said! I was tying the HR tag manually and this might be the cause of the problem. This is entirely my fault :D Sorry about that! And thanks a lot for your help! Your app rocks! Keep up the great work! I use your site everyday! The interface is awesome!

Thanks for the support shriganesh - glad to help


[FEATURE] Add manual angle adjustment for gliding control

Add the ability to control what angle means forwards relative to your controllers

Might also adjust the actual default angle just to account for other controllers

I have been experiencing issues with wings not aligning how they intuitively would work. I use Quest2 controllers (with Standable), and to glide forward I have to hold my wings vertically, like I'm breaking in the air/about to land, instead of holding them flat horizontally. To fly up I have to twist my wing completely unnaturally. Sadly It is both uncomfortable and not immersive, it's like there is 90 degrees offset almost.

Having some way to adjust rotational offset (even if it's a manual per-world VRCX-saved setting) would make it actually properly usable.
Additionally it would be very beneficial to have an option to draw debug visualization of how the Open Flight expects your wings to be rotated and sized (like a transparent wing, or just a plane).

I'm available to contact for additional feedback and testing! Discord/Telegram is Salireths

Added and confirmed functional in latest beta


Chore: Fix SVG Link in 'Contributing to Open Source' Page

Category

[ ] Documentation
[ ] Resource Addition
[x] Codebase
[ ] User Interface
[ ] Feature Request

Description
We need to fix a broken SVG link in the 'Contributing to Open Source' page.
Step 1: Go to client/pages/contributing-to-open-source/index.html
Step 2: Find the following link under <head>...</head>
<link rel="icon" href="./assets/short-logo.svg">

Step 3: Change it to
<link rel="icon" href="../../assets/short-logo.svg">

Assign me this issue

Assigned, @RahulSingh9131!


Missing step in dependencies section "dep" install part of pre requisite

Output of the info page (if this is a bug)
calling dep ensure
/bin/bash: dep: command not found

Describe what happened:
Dependency check doesn't talk about dep package i.e. "Go dependency management tool"
Describe what you expected:
When running command

invoke deps

It gives error
calling dep ensure
/bin/bash: dep: command not found
To fix it
install "dep-0.5.4-1.fc31.x86_64" Go dependency management tool.
Steps to reproduce the issue:

invoke deps

calling dep ensure
/bin/bash: dep: command not found
Additional environment details (Operating System, Cloud provider, etc):
Fedora 31
Linux version 5.3.12-300.fc31.x86_64<EMAIL_ADDRESS>(gcc version 9.2.1 20190827 (Red Hat 9.2.1-1) (GCC))

Hi @irfancode, the dep binary should be installed by invoke deps in $GOPATH/bin.
As documented in the README our invoke commands expects $GOPATH/bin to be in your $PATH, can you double-check that in your environment?


Add new transpiler exception class for too many qubits

Summary
This commit adds a new exception class for when the transpiler is given a circuit too many qubits for a given backend. Previously the generic TranspilerError was raised for this, but it made it difficult for downstream users to catch as it wasn't easy to differentiate this error condition from other TranspilerError exceptions. There isn't any backwards compatibility issues with this because the new CircuitToWideForTarget class is a subclass of TranspilerError so any of the previous catches for TranspilerError will still catch this.
Details and comments

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

5 of 5 (100.0%)  changed or added relevant lines in 3 files are covered.
30 unchanged lines in 3 files lost coverage.
Overall coverage decreased (-0.04%) to 85.892%

Files with Coverage Reduction
New Missed Lines
%

crates/qasm2/src/expr.rs
1
93.76%

crates/qasm2/src/lex.rs
5
91.16%

crates/qasm2/src/parse.rs
24
96.2%

Totals

Change from base Build<PHONE_NUMBER>:
-0.04%

Covered Lines:
65912

Relevant Lines:
76738

💛  - Coveralls

This seems like a generally sensible option. Would ApplyLayout and SetLayout potentially raise this as well?

It turns out the answer is no because neither SetLayout nor ApplyLayout take in a target. They just blindly set the layout in the property set or take the layout from the property set and transform the circuit based on that. I think in general we'll want to refactor how this check is handled because besides not catching the generate_preset_pass_manager() case the current logic also precludes something like qiskit-qubit-reuse shrinking the circuit prior to layout. I'm thinking the easiest way is to add a new pass that runs in the pre_layout stage which checks if the circuit is too big for the target and raises with this exception. But that's outside the scope of this PR I think.

Do you want to enforce the new type of the exception in the transpile call with a test?

I adjusted the existing test to catch the more specific error in: https://github.com/Qiskit/qiskit/pull/11241/commits/15af4e2d64b54fcb17d9659d0b7001d09d0ea201


Ability to disable S3 multipart upload

For instance, it's not supported by GCS.
Opening for visibility, since we shouldn't be using this API at all with the current policy.

storage:
  s3:
    disable_multipart_upload

Closed via #3591.


openapi(dm): adjust openapi of new task state

What problem does this PR solve?

Issue Number: ref #4484
What is changed and how it works?
TBD
Check List
Tests

Unit test
Integration test
Manual test (add detailed scripts or steps below)
No code

Code changes

Has exported function/method change
Has exported variable/fields change
Has interface methods change
Has persistent data change

Side effects

Possible performance regression
Increased code complexity
Breaking backward compatibility

Related changes

Need to cherry-pick to the release branch
Need to update the documentation
Need to update key monitor metrics in both TiCDC document and official document

Release note
Please add a release note.
If you don't think this PR needs a release note then fill it with `None`.

ut for source change passed checkponit https://ci.pingcap.net/blue/organizations/jenkins/tiflow-verify-pipeline/detail/tiflow-verify-pipeline/1163/pipeline

/run-dm-integration-tests

Codecov Report

Merging #4627 (7d9323f) into master (9607554) will decrease coverage by 0.3495%.
The diff coverage is 54.0983%.

Flag
Coverage Δ

cdc
59.9080% <54.0983%> (-0.0142%)
:arrow_down:

dm
51.6141% <ø> (-0.4148%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.
@@               Coverage Diff                @@
##             master      #4627        +/-   ##
================================================
- Coverage   55.6402%   55.2906%   -0.3496%
================================================
  Files           494        521        +27
  Lines         61283      65767      +4484
================================================
+ Hits          34098      36363      +2265
- Misses        23750      25823      +2073
- Partials       3435       3581       +146

/run-dm-integration-tests

/run-dm-integration-tests

/run-dm-integration-tests

/run-dm-integration-tests

/run-dm-integration-tests

/run-dm-integration-tests

/run-dm-integration-tests

/run-dm-integration-tests

/run-dm-integration-tests

[2022-03-11T08:53:51.670Z] ____________________________________

[2022-03-11T08:53:51.670Z] [Fri Mar 11 16:53:49 CST 2022] Executing SQL: select count(1) from shardddl.tb

[2022-03-11T08:53:51.670Z] *************************** 1. row ***************************

[2022-03-11T08:53:51.670Z] count(1): 16

[2022-03-11T08:53:51.670Z] ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

shardddl_optimistic failed
/run-dm-integration-tests

/run-dm-integration-tests

/run-dm-integration-tests

could you please take another look for this pr ? thanks 🧡🧡🧡
/cc @D3Hunter @WizardXiao
The ui-logic for this PR is not yet stable and is being testing with the UI part, but you can start reviewing the important logic changes for any major errors

The ui-logic is in openapi_controller.go.
Important changes are in scheduler.go and syncer.go

such a large pr, will review later.

yes becasue there is so many breaking change, so i can't split this pr (will affects nighty version)
we need feature branch to slove this problem

/run-all-tests

/run-all-tests

/run-dm-integration-tests

/run-all-tests

/run-all-tests

/merge


Add new Text component

This Pull Request meets the following criteria:

[ ] Tests have been added/adjusted for my new feature
[ ] New Components are registered in index.js of my project

Closes: #91

and one more thing: I don't see component registering in index.js @williamkolmacka

I don't see component registering in index.js

yes please, don't forget to add this 🙂


Integrate Educational Content like Corona Simulation Applications to encourage taking reasonable actions

In my opinion it could make sense to include links to projects like:
https://gifted-einstein-2065af.netlify.app/

Hey @michael-spengler 👋
Thanks for your contribution. For feature requests, we normally use the CWA-wishlist.
Please consider to close this issue here and open a new one there.
Thanks.

... or a friendly moderator could move the contribution.


Upgrading on OS X: GPG not available, then forced reprovision

I installed the new Keybase without first installing GPG. It worked fine, including Keybase FS.
After upgrading to 1.0.16-20160803190018+268b023: Keybase forced login, which failed with an error about GPG not being available.
After brew install gnupg2, logging in worked, but Keybase took me through the new device process.

Trying again on my other device, which has gnupg2… sailed through. Didn't prompt me for login.

CC @gabriel, and maybe @maxtaco
@garthk Please could you run keybase log send?

(On the device that didn't work properly.)

Done. e8891acaf199b06d77526e1c

Thanks,  I attached this to issue CORE-3481.  CC: @patrickxb

Hey,
Yeah, I'm having a similar issue. Did an update and Keybase is telling me that the system I'm on needs to be provisioned...but it is and is one of the options I can even use to authenticate.
I too have done a log send: 7b46c04396a8f02860e93b1c
That said, I did get some errors on opening log files that where not there..."no such file or dir"
--Brian

I guess I could always just revoke my devices and just re add them using my paper key ;)
But I'll wait to see if you guys find anything interesting.

Interesting, on my other device, I did the same updates and everything logged in just fine. Keybase Status did confirm the device name and it's provisioned status. Originally I thought there might have been an issue with the latest GPG Tools for OSX install, so I did two log dumps:
Pre GPG Update: 25c80734f22a4354ae14cf1c
Post GPG Update:<PHONE_NUMBER>666a78123fdd1c
But looking at KB Status twice...seems to be OK...
I'm interested to see what you guys find.
--Brian


Add new sensors samples

This patch adds the documentation files for the following samples:

DHT11/22;
PWM;
GY-251 I2C Accelerometer and Gyroscope.

@alla3 could you review it again, please?


Order payment status performance

I want to merge this change because it improves performance of order paymentStatus and paymentStatusDisplay resolving.
Related tickets:
SALEOR-2737
SALEOR-2738
Local testing (10 orders, 3 payments for each order):
before: "query-count": 36, "duplicates": 10
after: "query-count": 17, "duplicates": 0
⚠  containts tests from #7124 will be rebased after merge and reviewers will be assigned afterwards.

Impact

[ ] New migrations
[ ] New/Updated API fields or mutations
[ ] Deprecated API fields or mutations
[ ] Removed API types, fields, or mutations
[ ] Documentation needs to be updated

Pull Request Checklist

[ ] Privileged queries and mutations are guarded by proper permission checks
[ ] Database queries are optimized and the number of queries is constant
[ ] Database migration files are up to date
[X] The changes are tested
[ ] GraphQL schema and type definitions are up to date
[ ] Changes are mentioned in the changelog

Task linked: SALEOR-2737 Optimize paymentStatus resolver in Order type

Task linked: SALEOR-2738 Optimize paymentStatusDisplay resolver in Order type


Ripple effect

There is a way to maintain the Ripple Effect after removing the shifting mode?
I'm using this configuration:
bottomNavigationView.enableAnimation(false);
bottomNavigationView.enableShiftingMode(false);
bottomNavigationView.enableItemShiftingMode(false);
bottomNavigationView.setTextVisibility(true);
bottomNavigationView.setIconVisibility(true);

I don't want any kind of Shifting but I want to continue having the ripple effect.
Thank you and amazing job!

Using these api will not cause the ripple effect to disappear. I test in Android 5.0 and it works well.
The ripple effect was supported from Android 5.0. So you can't see it on Android 4.x.
You can see this image.

And you just need call these api. The text and icon are visible by default.
bottomNavigationView.enableAnimation(false);
bottomNavigationView.enableShiftingMode(false);
bottomNavigationView.enableItemShiftingMode(false);

I'm glad to see someone using my library.

@ittianyu the library works fine, it was my issue setting the same color on the background.
Again, thank you for your effort and be sure that this library saved my life 😄 .

if you wan to custom the menu item click ripper, you can define style in styles.xml like this
so set the BottomNavigationMenuEX theme in xml, it will work!


Link to live website

Weeeee where is the link to the live website?

is it https://aquariuminsider.org/?


Update scalafmt-core to 3.7.12 in java8

About this PR
📦 Updates org.scalameta:scalafmt-core from 3.7.9 to 3.7.12
📜 GitHub Release Notes - Version Diff
Usage
✅ Please merge!
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

⚙ Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.scalameta", artifactId = "scalafmt-core" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "org.scalameta", artifactId = "scalafmt-core" }
}]

labels: library-update, early-semver-patch, semver-spec-patch, commit-count:1

Superseded by #481.


Client-side interface to pick which horse/pet to summon OR item to target single pet

Also from MokahTGS on CurseForge:  Perhaps you could have a UI come up on right click in the air to pick the pet to summon.  If you right click on a pet it adds it to the list.  Sneak right click removes it from the list.
Currently this would require a complete rewrite along with packet handling on the server/client side, as well as an interface. Alternately, a specific item could be implemented that could be shift-clicked against a certain mob and it would only summon that mob.
Again, this would require NBT shenanigans.

Honestly, I won't be doing this. It's beyond my skill and desire.


Fix broken links in CesiumTerrainProvider docs

Fixes https://github.com/CesiumGS/cesium/issues/7478
Added a comment to the constructor doc linking to references on the accepted terrain formats.

Thank you so much for the pull request @jjhembd! I noticed this is your first pull request and I wanted to say welcome to the Cesium community!
The Pull Request Guidelines is a handy reference for making sure your PR gets accepted quickly, so make sure to skim that.

:x: Missing CONTRIBUTORS.md entry.

Please add yourself to the contributors file!

:x: Missing CLA.

Please send in a Contributor License Agreement (CLA) and comment back here to let us know to check this!
Maintainers, here's how to check for a submitted CLA.

:grey_question: CHANGES.md was not updated.

If this change updates the public API in any way, please add a bullet point to CHANGES.md.

:grey_question: Unit tests were not updated.

Make sure you've updated tests to reflect your changes, added tests for any new code, and ran the code coverage tool.

Reviewers, don't forget to make sure that:

[ ] Cesium Viewer works.
[ ] Works in 2D/CV.

Hi @cesium-concierge, I updated the CONTRIBUTORS and CHANGELOG. Will update the CLA once I have it.
Thanks!

Thanks @jjhembd! I can confirm that you're CLA has been added!
Congrats on your first PR!


ex 15.35 & ex.15.39

Links to Query class implementation are dead.

I have submitted a PR to correct the link for 15.35 and 15.39 'query.h'. I have not been able to locate 'query_base.h' to correct for 15.39


[Feature] Implement Mqtt standard specification

It would be interesting to implement in this project the specification describe here :
https://homieiot.github.io/
However, MQTT doesn’t define the structure and content of these messages and their relation. An IoT device publishes data and provides interaction possibilities but a controlling entity will need to be specifically configured to be able to interface with the device.
The Homie convention defines a standardized way of how IoT devices and services announce themselves and their data on the MQTT broker.
It is thereby a crucial aspect on top of the MQTT protocol for automatic discovery, configuration and usage of devices and services.
Some other xxx2mqtt already purpose this and I think specification for MQTT is the futur of home automation.
It would be not changing the way of this project work actually, but add another way to publish.
I'm from the open source project NextDom (home automation software) and we are working on another solution from scratch. We want to organize NextDom directly with MQTT and Node-Red (Nextdom becoming a kind of orchestrator. In this way, this standard for MQTT will be very interesting for us of course, but also for all others home automation software.
Thanks for reading and give me some feed back about that !

Thanks for the suggestion. I've already implemented Home assistant auto-discovery. The homie MQTT layout should be doable as well. Pull requests appreciated.


Gera.newspaper screen

👍  Good work with that immutable DataSource 🎉🎉🎉
In this (kind of) simple scenario it works nicely.
⚠ However, keep an eye on it if it grows and becomes more complicated... It can become really cumbersome and sometimes it's just better to use a mutable DataSource to make things simpler. It happened to me in some overwhelming classes in other projects.


v0 state performance ratings page

Rudimentary, hard-coded table and static image
Some light styling

Not pressing to review the code while we are still reviewing/iterating on the preview, unless something strikes you


CLI don't work when is install locally

Related to: https://github.com/javascript-obfuscator/javascript-obfuscator/issues/245, https://github.com/javascript-obfuscator/javascript-obfuscator/issues/246
I have shared hosting, and I can't install packages globally. (npm)
And local version try using "my project" package.json

Please, use search. Try to run npm link or npm link javascript-obfuscator

I don't have with run command, but after running it program throws error.

Do you understated what is sharing hosting?

[czat@s12]:<~/test2>$ npm link javascript-obfuscator
npm WARN checkPermissions Missing write access to /usr/local/lib/node_modules
npm ERR! path /usr/local/lib/node_modules
npm ERR! code EACCES
npm ERR! errno -13
npm ERR! syscall access
npm ERR! Error: EACCES: permission denied, access '/usr/local/lib/node_modules'
npm ERR!     at Error (native)
npm ERR!  { Error: EACCES: permission denied, access '/usr/local/lib/node_modules'
npm ERR!     at Error (native)
npm ERR!   stack: 'Error: EACCES: permission denied, access \'/usr/local/lib/node_modules\'\n    at Error (native)',
npm ERR!   errno: -13,
npm ERR!   code: 'EACCES',
npm ERR!   syscall: 'access',
npm ERR!   path: '/usr/local/lib/node_modules' }
npm ERR!
npm ERR! The operation was rejected by your operating system.
npm ERR! It is likely you do not have the permissions to access this file as the current user
npm ERR!
npm ERR! If you believe this might be a permissions issue, please double-check the
npm ERR! permissions of the file and its containing directories, or try running
npm ERR! the command again as root/Administrator (though this is not recommended).

So, run it locally with ./node_modules/javascript-obfuscator/bin/javascript-obfiscator

Mesh...
$ pwd
/root/test3
$ npm install  --save-dev javascript-obfuscator
$ ./node_modules/javascript-obfuscator/bin/javascript-obfuscator
Error: ENOENT: no such file or directory, open '/root/test3/package.json'
    at Error (native)
    at Object.fs.openSync (fs.js:642:18)
    at Object.fs.readFileSync (fs.js:510:33)
    at Object.<anonymous> (/root/test3/node_modules/pjson/pjson.js:4:19)
    at Module._compile (module.js:570:32)
    at Object.Module._extensions..js (module.js:579:10)
    at Module.load (module.js:487:32)
    at tryModuleLoad (module.js:446:12)
    at Function.Module._load (module.js:438:3)
    at Module.require (module.js:497:17)

Oh, this is bug. Will try to fix it in the near future.

Sabe here...

Fix in the master branch now. You can use version from master branch until release.

0.17.0 version in out!


Allow SocketClientConfig to have a Future initPayload

Breaking changes

none

Fixes / Enhancements

Added the ability to use a Future for the initPayload of a SocketClient in the same way the AuthLink.getToken is. This allows a user to provide their bearer token more easily.

Docs
SocketClientConfig(
  initPayload: () async {
    FirebaseUser user = await FirebaseAuth.instance.currentUser();
    IdTokenResult idTokenResult = await user.getIdToken();

    return {
      "headers": {"Authorization": 'Bearer ${idToken.token}'},
    };
  },
)

@mainawycliffe do you know why test_coverage would be hanging and then timing out? i tried running locally and get the same thing.

blocked by #514

@kulture-rob can you rebase against the latest beta branch?

@mainawycliffe all set!

I'm not sure what checks haven't been completed in circle ci

resubmitting since codecov seems to be broken


Issue 855

First thing, PLEASE READ THIS: ReactPlay Code Review Checklist

Description
Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context. List any dependencies that are required for this change.
Fixes #855
Type of change
Please delete options that are not relevant.

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

How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce.
Checklist:

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

Screenshots or example output

@atapas  @koustov please review the changes.

@koustov can you plz review?


Update transitive.swift

Disable failing testing pending fix (SR-12554)

Replace this paragraph with a description of your changes and rationale. Provide links to external references/discussions if appropriate.

Resolves SR-NNNN.

@swift-ci please test

Fixed in #30908 rather than disabling the test.

Build failed
Swift Test Linux Platform
Git Sha - 3e7ef4b775b597612145c95c952134a3d2608607

Build failed
Swift Test OS X Platform
Git Sha - 3e7ef4b775b597612145c95c952134a3d2608607


Splitting compaction changes stage 1

Issue

[ ] My PR addresses the following issues and references them in the PR title. For example, "Issue 1234 - My Sleeper
PR"

Resolves https://github.com/gchq/sleeper/issues/967

Tests

[ ] My PR adds the following unit tests OR does not need testing for this extremely good reason:

Tests updated

Documentation

[ ] In case of new functionality, my PR adds documentation that describes how to use it, or I have linked to a
separate issue for that below.

Javadoc updated

These changes have been gradually introduced in milestone 0.21 as part of this parent issue: https://github.com/gchq/sleeper/issues/966


Build test engine/version image for both amd64/arm64

Signed-off-by: Chris Chien<EMAIL_ADDRESS>From https://github.com/longhorn/longhorn/issues/1961, https://github.com/longhorn/longhorn/issues/4206
Will build amd64/arm64 test engine image by API version for longhorn-test use and push to specific docker hub repo
chanow/longhorn-engine:upgrade-test.5-3.3-3.1-1
chanow/longhorn-engine:version-test.5-3.3-3.1-1
chanow/longhorn-engine:version-test.6-4.3-3.1-1
chanow/longhorn-engine:version-test.6-6.3-3.1-1
chanow/longhorn-engine:version-test.4-2.3-3.1-1
chanow/longhorn-engine:version-test.2-2.3-3.1-1

Test reault : amd64, arm64
Environment

Have docker installed
Have local private ssh key
Have jq installed

Environment Variable

TF_VAR_build_engine_aws_access_key
TF_VAR_build_engine_aws_secret_key
TF_VAR_docker_repo (should be set to longhornio/longhorn-test)
TF_VAR_docker_id (docker id for longhornio/longhorn-test)
TF_VAR_docker_password (docker password for longhornio/longhorn-test)

Run

Switch to build_engine_test_images folder
run ./run.sh
Result as below when set TF_VAR_docker_repo to chanow/longhron-engine

We should have an independent pipeline (jenkins job) to run run.sh as other pipelines instead of manually running run.sh.

Created issue https://github.com/longhorn/longhorn/issues/4219 and will setup local pipeline first, thank you

Can we change the folder from test_engine to build_engine_test_images to align with other pipeline folder names like mirror_csi_images?
cc @yangchiu

I renamed test_engine to build_engine_test_images
cc @yangchiu

HI @innobead ,
I updated code to add build_engine_test_images/Dockerfile.setup and build_engine_test_images/Jenkinsfile and little refactor to let pipeline from https://github.com/longhorn/infra/pull/91 can trigger this PR properly.
Also I checked full jenkins log, sensitive information like secret key and docker password will auto marked as ***** by jenkins, thank you
cc @yangchiu

HI @innobead ,
I updated code to add build_engine_test_images/Dockerfile.setup and build_engine_test_images/Jenkinsfile and little refactor to let pipeline from longhorn/infra#91 can trigger this PR properly.
Also I checked full jenkins log, sensitive information like secret key and docker password will auto marked as ***** by jenkins, thank you
cc @yangchiu

How about terraform? Is it possible to output these sensitive information by terraform (since the docker secret is set a terraform variable)? Does adding sensitive = true make it more secure?

HI @innobead ,
I updated code to add build_engine_test_images/Dockerfile.setup and build_engine_test_images/Jenkinsfile and little refactor to let pipeline from longhorn/infra#91 can trigger this PR properly.
Also I checked full jenkins log, sensitive information like secret key and docker password will auto marked as ***** by jenkins, thank you
cc @yangchiu

How about terraform? Is it possible to output these sensitive information by terraform (since the docker secret is set a terraform variable)? Does adding sensitive = true make it more secure?

Yes it's more secure but most of console output become  null_resource.build_images[0] (remote-exec): (output suppressed due to sensitive value in config) null_resource.build_images[0] (remote-exec): (output suppressed due to sensitive value in config)
And looks like longhorn-test pipeline do not use this setting as well


Use Sauce Labs to test Multi–Browser

https://saucelabs.com/opensauce/
Free Accounts for open source projects.

Might take a look at this later. Not a priority for now.


Create 0000-01-02-gatoratemylips.md

created a branch, created a file and made a commit, and opened a pull request

update


MS0108_01 : BUG WrapObject Property

a bug accure when selecting the wrap object from the navigator more specificly trying to get the OpenSim name property unlike the other nodes.
and prevent selecting the Prob in the visualizer for the wrapobjects

Please add a link to the part(s) of related the code

vsNavigatorNode 67

Update !
after some debbuggin the error happend when trying to convert std::string to QString
But: it only happen for the WrapObject  and transforms
the pointer for the WrapObject does not contain informations about the object but only when called in the setupPropertiesModel and when it called from vsWrapObjectNode it has all the values set up
so problem still open!

@yasseerr
If you like we can skype to discuss this. It is not clear to me what is the bug here.
I just downloaded and built the recent version. Here are some comments:

it seems the slow problem is gone.
The event handler of the vtk widget has some problems as sometimes geometry disappears.

Usually there already some events pre-defined so we need to override them.
check if there are similar examples.

when we reload the model , the small icons and the ground disappear.

I think what we need is to have our own Qt-VTK-Widget class that inherits and overrides the current functions:

the widget has opensim small icons and their functions by default
different observers that monitor the mouse event in the widget to decide the action based on the mouse event  e.g. move, click, drag, ..etc
each object in the widget should have some properties:

visible
selected

if selected, its color should be changed to e.g. orange

type  e.g. model object or widget object

widget object: these small icons on the top left in addition to the skybox and the ground.
model object: geometry, joints, ...

based on these properties we define different actions

@yasseerr
Here is what I found, check my last comment:
We can use something like
 bool isEmptyName = true;
 if(openSimObject != nullptr){
    isEmptyName = (openSimObject->getName()=="");
    if (not isEmptyName ){
         // get object properties
   else{
        //get object properties using a different method
   }

Using the above if-else allows the application to continue without crashing. Still, we need to find how to get the object properties.  An idea is to get the navigator parent node of this object then handle this object using its parent object and the current navigator node name.

@idhamari
yes that would work but the core problem is you can't test it when you call opensimObject->getName() the program crashes

@yasseerr
I don't have this in Linux using this code. In the navigator, I select  jointset  ---> r_elbow ---> rotation1 and the program does not crash.
Could you please describe or record a short video to show this using the arm model.

did you test it on the transforms and the wrap objects , for windows it still crashes but not on the rotations as in this video

Thanks for sharing the video.
This is the output when  I select TRIlonghh
 bug here ================================ start
 Object
 TRIlonghh
 0
 bug here ================================ end
"TRIlonghh"
 VisSim: line 92 ........................
 VisSim: Getting object properties ........................
 Segmentation fault (core dumped)

This means we get the name property and the error happens somewhere after that.

do you mean the to upload the code with the changes you sent because i already uploded the last version, and i will try to run it outside of qt creator.
note that for me it crashed before the name like this
Loaded model arm26 from file F:/arm26.osim
bug here ================================ start
Object
01:46:23: The program has unexpectedly finished.
and only sometimes that it manage to get the name

The code I am using is from before our last skype. I see now, you already pushed new code. I will use it on my testing. I will also test this on windows.

@yasseerr
I can confirm that the bug exists in windows and I have different behavior than Linux. I will investigate that.
I also found out that there is a path problem when running using different environment e.g. Linux, Visual studio or QtCreator.
  ERROR: In D:\sw\vtk-9.0.0.rc3\src\IO\Image\vtkPNGReader.cxx, line 264
  vtkPNGReader (00000211C2DB2360): Unable to open file ./vtk_images/zoom-in.png

This should be fixed now so we don't keep doing the same thing again and again. Please do:

Create an initial file e.g. vsOpenSimQt.ini inside the Gui folder. This file should contain important paths e.g. Geometry path, images , icons, ....etc.
CMake should copy this file to the same location of the target exe file
Cpp files should read the paths using this file instead of hard-coded paths.

When this is done, please inform me here so I can continue investigating the bug.

@yasseerr
Update:
As I understood:

user select a node in the navigator
this triggers void vsModelNode::setupPropertiesModel(vsPropertyModel *model)
which calls    void vsNavigatorNode::setupPropertiesModel(vsPropertyModel *model){

What is not clear:

why we have the same function name? I suggest change to setupPropertiesModelNode
how the functions knows which node is selected?
how the node object is connected to the openSimObject?

I tried this but each time I get a different number for the same object, do you know why? it seems to me there is something wrong with these pointers when they are generated.
void vsNavigatorNode::setupPropertiesModel(vsPropertyModel *model){
	bool isEmptyName = true;
	if (openSimObject != nullptr) {
		//name property
		//qDebug() << QString::fromStdString(openSimObject->getName());
		//qDebug() << QString::fromStdString(openSimObject->getName());
		std::cout << "bug here ================================ start" << std::endl;
		std::cout << openSimObject->getClassName() << std::endl;
		std::cout << openSimObject->getNumProperties() << std::endl;
		//std::cout << openSimObject->getName() << std::endl;
		//isEmptyName = (openSimObject->getName() == "");
		isEmptyName = (openSimObject->getNumProperties()<=0) | (openSimObject->getNumProperties() > 1000);
		std::cout << isEmptyName << std::endl;
		std::cout << "bug here ================================ end" << std::endl;
		/* windows test
           bodyset ---->base ----> Trilongglen  name ="" ok
		   jointset ---->r_elbow ----> rotation1, can not get the name, "Segmentation Fault"

		*/
		vsPropertyItem *nameItem = new vsPropertyItem();
		//qDebug() << QString::fromLatin1(openSimObject->getName(),(int)openSimObject->getName().size());

		if (! isEmptyName) {
				std::cout << "VisSim: Getting object prperties ........................" << std::endl;
				nameItem->m_name = "name";
				std::string nameTmp = openSimObject->getName();
				nameItem->m_value = QString::fromStdString(nameTmp);
				qDebug() << nameItem->m_value;
				nameItem->m_type = vsPropertyItem::Text;
				nameItem->setText(nameItem->m_value);
				model->m_propertiesItem->appendRow(QList<QStandardItem*>() << new QStandardItem("name") << nameItem);

				//type property
				vsPropertyItem *typeItem = new vsPropertyItem();
				typeItem->m_name = "type";
				typeItem->m_isEditable = false;
				std::string typeTmp = openSimObject->getConcreteClassName();
				typeItem->m_value = QString::fromStdString(typeTmp);
				typeItem->m_type = vsPropertyItem::Text;
				typeItem->setText(typeItem->m_value);
				model->m_propertiesItem->appendRow(QList<QStandardItem*>() << new QStandardItem("type") << typeItem);

				for (int i = 0; i < openSimObject->getNumProperties(); ++i) {

					auto ap = &openSimObject->getPropertyByIndex(i);
					QString apName = QString::fromStdString(ap->getName());
					vsPropertyItem *apItem = new vsPropertyItem();
					QStandardItem *apNameItem = new QStandardItem(apName);
					qDebug() << apName << QString::fromStdString(ap->getTypeName());

					if (ap->isListProperty()) {

						apItem->m_type = vsPropertyItem::List;
						QString listRepresentation = "[ ";
						for (int j = 0; j < ap->size(); ++j) {
							listRepresentation += QString::fromStdString(ap->getValueAsObject(j).getConcreteClassName());
							listRepresentation += " ";
						}
						if (ap->size() == 0) listRepresentation += " empty ";
						listRepresentation += "]";
						apItem->m_value = listRepresentation;
						apItem->setText(apItem->m_value);
					}
					//            else if(ap->isOptionalProperty()){

					//            }
					//            else if(ap->isUnnamedProperty()){\
					//            }
					else if (ap->isObjectProperty()) {
						if (OpenSim::Function::safeDownCast(const_cast<OpenSim::Object*>(&ap->getValueAsObject()))) {
							qDebug() << "it is a function indeed";
						}
						else if (apName == "Appearance") {
							auto _appr = &ap->getValueAsObject();
							auto appr = OpenSim::Appearance::safeDownCast(const_cast<OpenSim::Object*>(_appr));
							//visible property
							auto visibleProp = &appr->getProperty_visible();
							vsPropertyItem *visibleItem = new vsPropertyItem();
							QStandardItem *visibleNameItem = new QStandardItem("visible");
							visibleItem->m_type = vsPropertyItem::Check;
							visibleItem->m_value = QString::fromStdString(visibleProp->toString());
							visibleItem->setText(visibleItem->m_value);
							visibleItem->setEditable(true);
							model->m_appearancexItem->appendRow(QList<QStandardItem*>() << visibleNameItem << visibleItem);

							//opacity property
							auto opacityProp = &appr->getProperty_opacity();
							vsPropertyItem *opacityItem = new vsPropertyItem();
							QStandardItem *opacityNameItem = new QStandardItem("opacity");
							opacityItem->m_type = vsPropertyItem::Text;
							opacityItem->m_value = QString::fromStdString(opacityProp->toString());
							opacityItem->setText(opacityItem->m_value);
							opacityItem->setEditable(true);
							model->m_appearancexItem->appendRow(QList<QStandardItem*>() << opacityNameItem << opacityItem);

							//color property
							auto colorProp = &appr->getProperty_color();
							vsPropertyItem *colorItem = new vsPropertyItem();
							QStandardItem *colorNameItem = new QStandardItem("color");
							colorItem->m_type = vsPropertyItem::Color;
							colorItem->m_value = QString::fromStdString(colorProp->toString());
							colorItem->setText(colorItem->m_value);
							colorItem->setEditable(true);
							model->m_appearancexItem->appendRow(QList<QStandardItem*>() << colorNameItem << colorItem);

							//color property
							auto dpProp = &appr->getProperty_SurfaceProperties();
							vsPropertyItem *dpItem = new vsPropertyItem();
							QStandardItem *dpNameItem = new QStandardItem("DisplayPreferences");
							dpItem->m_type = vsPropertyItem::Text;
							dpItem->m_value = QString::fromStdString(dpProp->toString());
							dpItem->setText(dpItem->m_value);
							dpItem->setEditable(true);
							model->m_appearancexItem->appendRow(QList<QStandardItem*>() << dpNameItem << dpItem);

							continue;
						}
						else {
							apItem->m_type = vsPropertyItem::Object;
							apItem->m_object = const_cast<OpenSim::Object*>(&ap->getValueAsObject());
							apItem->setText(QString::fromStdString(apItem->m_object->getName()));
							apItem->setEditable(false);
						}
					}
					else {
						apItem->m_type = vsPropertyItem::Text;
						apItem->m_value = QString::fromStdString(ap->toStringForDisplay(1));
						apItem->setText(apItem->m_value);
					}

					QRegExp socketRegEx("^socket.*");
					if (socketRegEx.exactMatch(apName)) {
						model->m_socketsItem->appendRow(QList<QStandardItem*>() << apNameItem << apItem);
					}
					else {
						model->m_propertiesItem->appendRow(QList<QStandardItem*>() << apNameItem << apItem);
					}

				}

		}
    }
	std::cout << "VisSim: Getting object prperties is done ........................" << std::endl;

thanks for the feedback!
to understand how the nodes and models work you should understand Qt Model/View to represent the data

1:  how the function knows which node is selected

when you click on the treeview it triggers  a signal that will call the onNavigatorClicked in the vsMainWindow which give you the index of the node QModelIndex

after that the helper funcion nodeForIndex() give you the node that was clicked which inherit vsNavigatorNode it can be all the other nodes using simple polymorphism
that node when it was created in the constructor it was given the openSimObject that represent it so it can do operation on it
2 : for the function name we are using the same function name because it is the same function overrided in the modelNode as every other node using inheretance so when you click the function corresponded to the node type(model,body...) will be call if it was not ovverided in the class the default one in vsNavigatorNode will be called
*3: opensimObject is connected  when we add a new model like this
the modelNode is created and connected to the  OpenSim::Model which inherit OpenSim::Object
the modelNode create subNodes like ground bodysetsNode
the bodyset create the bodies and assign a OpenSim::Body to the openSimObject ..ex

for the image please make sure you have the latest version clean the project  and run cmake , it should copy the zoom image to it's appropriate folder , because there in no hardcore path added vtk cant use qt resources  files qrc/rcc(compiled) so its images are put in target/vtk_images unlike the others

Thanks for the info.

for the image please make sure you have the latest version clean the project and run cmake , it should copy the zoom image to it's appropriate folder ,

In visual studio the application is inside build\release so this does not work.  I already solved this manually for now.
We will need the .ini file in the future for other things as well. When we have a lot of paths hard-coded this will make a problem if we need to reconstruct our repository. The standard is to read the paths and the settings from a .ini file. So it is better to do it now.

to understand how the nodes and models work you should understand Qt Model/View to represent the data

It seems that you are following the java interface approach. Maybe the bug comes from a difference between java and cpp pointers handling? I was hopping we are handling this our way e.g. by reading the text osim file and create the nodes. This gives us more control and more independent from OpenSim.
Please make sure that each node in the navigator is correctly connected to only one pointer and this pointer is the correct pointer to the related OpenSim object.
I will try to investigate more about the bug.

for the ini file QSetting give you the option to store the settings in the ini file or system registry
a static instance of it will be in vsOpenSimTools to store the settings
for the openSimObject they should be connected even for wrapobject as you can print the name normaly on other parts of the code except in the setupPropertiesModel function which is the abnormal behavior that we trying to solve
we need further look into the OpenSim::WrapObject and rotation to see what special about them


[1.21.1] Minimum Water Texture Not Working on Iris 1.8 Release/Sodium 0.6

Describe the bug
When switching from the Iris 1.8/Sodium 0.6 betas to the full releases, the 'Minimum Water Texture' feature appears to have stopped working. Other features like waves & color settings seem to still apply
To Reproduce
Steps to reproduce the behavior:

Install Iris 1.8 & Sodium 0.6 full releases
Enable Mini Shader
Load up world & find water

Expected behavior
Expected no changes to the water visuals from initial settings, since the default Min Water Texture was kept at 4.
Screenshots

Before, running on Iris 1.8.0-beta-4 & Sodium 0.6.0-beta-2

After, running on Iris 1.8.0 & Sodium 0.6.0
System Information

MC 1.21.1, Simply Optimized 4.2 with only these mods changed
Shader v2.13.3
Nvidia Geforce GTX 1660Ti

Additional context
Unsure if this is something that you would have to fix, or if it's an Iris/Sodium issue, but just wanted to bring it up in case you could fix it!

I fixed the water texture, but shadows broke too and that's on them to fix.

Gotcha, thanks for looking into it!


CDPT 790 Fix duplicate breadcrumb path

This PR has a couple of treats:

Selectively drops a longer path in the breadcrumb, if needed
High-level code refactoring in a breadcrumb function
Flexbox has been added to tabs to assist in a clearer display for the user

Before

The breadcrumb was repeated
Tabs looking displaced

After

Thanks, as ever, Meena! I appreciate your attention to this.


Update services.md

Fixed link to GCP Cloud Console

@cjnova : Thanks for your contribution! The author(s) have been notified to review your proposed change.

#Sign-Off


Finish progress bar and implement in all places

The progress bar(s) are an inconsistent mess. Finish redesigning them so that they refresh properly upon activity completion.

Just haven't had the capacity to look at this. Next sprint!!


New Field: Channel Type

In our software we know two different channels, on which an application can be entered. The channel might have an influence on the price or on which client advisor is relevant for this application.
For this reason, we would like to have a new field in the object "application":
Name: channelType
Description: The type of the channel the application was generated
string
enum: [advisor, direct]
"advisor" could also be replaced by "broker"

Agreement MP / TKB on 29.09.22: Ok


Improve uguid API

Codecov Report

Merging #47 (93cc15f) into main (9a61043) will increase coverage by 0.04%.
The diff coverage is 98.93%.

@@            Coverage Diff             @@
##             main      #47      +/-   ##
==========================================
+ Coverage   92.57%   92.61%   +0.04%
==========================================
  Files          15       16       +1
  Lines        1427     1449      +22
==========================================
+ Hits         1321     1342      +21
- Misses        106      107       +1

Impacted Files
Coverage Δ

uguid/src/guid_parse.rs
98.92% <98.92%> (ø)

uguid/src/lib.rs
98.27% <100.00%> (-0.66%)
:arrow_down:

Continue to review full report at Codecov.

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