Read/Write API

Read API
The purpose of a Read API is get:

Users,
Posts,
Images

Just by a function (that can filter from ID, amount, content).

Can possibly reduce the amount of API methods.

Write API
The purpose of a Write API is write and update content from the Database. It will have restriction of what it can update, e.g.:

ID,
Image URLs

 Read/Write API


How to do Localization only with LeGO-LOAM (Map provided)?

Hi @TixiaoShan
I successfully generate map with your LeGO-LOAM in gazebo simulation, the map is nice. Here is the pointcloud map.

But if i want to use LeGO-LOAM to do the localization, is there anything need to be modified to allow localization in a known map? Can you guide me on this?
Best,
Samuel

Hi @HappySamuel
To localize with LOAM or LeGO-LOAM would need very heavy modifications to all the modules. For example, the feature maps are saved as a vector in mapRegistration.cpp. I would not suggest you do that. However, you may try segMap if you have an existing map.

Hi @TixiaoShan
The segMap you mentioned, is it the one that did by ethz-asl? I will look into that and try it out.  Can I get back to you and consult you if i face any trouble on this segMap? As you have the experience with it.
Best,
Samuel

Hi @TixiaoShan，have you tried relocalize the car using LeGO-LOAM with a  known lidar map? Could you give me some advice? thank you
looking forward to your reply.

@Shelfcol @HappySamuel, I'm trying to do it also, did you find a solution for it?


Thanks!

It's a shame I found out this syntax file too late, but thanks!
Now I finally have a pretty go development experience :)

I'm glad you like it! :)
Let me know if you have any issues or improvement suggestions. I have a list of things that I want to do but haven't had the time recently, but hopefully I will soon.


[FEATURE REQUEST/ISSUE] Add missing string to translation files

Before submitting the issue

[x ] I have checked that the requested feature is not a duplicate or, if it is, it needs to be reopened
[x ] I have checked that I am running the latest version of WingetUI
[x ] I have checked the FAQ section
[x ] I have read the contributing guidelines and I agree with the Code of Conduct

Is your feature request related to a problem? Please describe.
When you right-click on a package in the menu that shows up is the "Show info" string. It is not in the translation files so it is always in English.
Here I found the use of this string:
https://github.com/marticliment/WingetUI/blob/c19f8d8d79b21b2d26ead3592472779b2a4a2c2f/wingetui/uiSections.py#L250
Describe the solution you'd like
Need to add this string to the translation file. I would love to do it myself, but unfortunately I don't know python and how to develop translations in it.

I think show info appear as package details and is now translated

yes, but I deleted the old show jnfo by accident, so it will show in English.
However, versión 1.7.0 is close, so for one or two weeks I don't think it is worth to re-add those missing strings to Tolgee

now that 1.7 was released it got fixed, right?

Yes!

That went fast, thanks.


open EXCEL with password

Dears, i would like to ask there is any possible for AbapXlsx to implement the function: protect EXCEL file with password, means we need to key-in password before opening EXCEL file.
Ref. link: https://support.office.com/en-us/article/Protect-an-Excel-file-7359d4ae-7213-4ac2-b058-f75e9311b599

Hi,
This is not possible because, afaik, it is not an ooxml standard but a (Microsoft) functionality to binary encrypt the excel.
Ivan

On Jan 2, 2017, at 9:36 PM, Happyelsa<EMAIL_ADDRESS>wrote:
Dears, i would like to ask there is any possible for AbapXlsx to implement the function: protect EXCEL file with password, means we need to key-in password before opening EXCEL file.
Ref. link: https://support.office.com/en-us/article/Protect-an-Excel-file-7359d4ae-7213-4ac2-b058-f75e9311b599
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

I think it's still possible, but someone would have to dive deep into MS-OFFCRYPTO documentation and implement encryption method in ABAP. Which would take much effort and time. Hoping it's opensource project and someone could take a challenge :)

I have an ABAP project implementing much of PGP, https://github.com/larshp/abapPGP
You can have a look, and work on the encryption part if you like, much of the hardcore stuff is already done 😄


Allow proxy devices to be added on the fly for VMs

It appears right now it's not possible to add a proxy device to a running VM: Device cannot be added when instance is running.
It seems that applying it live could be done. I am willing to submit a PR; would it be as easy as implementing CanHotPlug() to always return true on proxies?

Hello, I am a coming from hacktoberfest. I am a beginner in contributing to open source. Is this an issue where I can contribute? Thank you

@bakhtiar56 assigned to you, thanks!

Take a look at https://github.com/lxc/lxd/blob/master/lxd/device/proxy.go and https://linuxcontainers.org/lxd/docs/master/installing/#installing-lxd-from-source

I understand somewhat that once the instance is running, we have to again call the runConfig function. I am sorry but I am not very proficient in OS programming. It would be helpful if you could guide me how to accomplish my task? Again, I apologize. Its just that I am very enthusiastic about my first open-source contribution but have limited understanding of intensive OS programming. I have only taken 1 OS course in my college.


Issue with models.predict() with trained hydrangea CNN

Hi friends.
I just trained a hydrangea flower vs. nature images classification app through a CNN: Train and Valid accuracy are ~93%.
Evaluate generator gives 95%.
Predict generator gives the following individual and reasonable predictions (for 10 hydrangea images and 10 nature images, in separate folders as required by the method), only one incorrect classification assuming the 0.5 threshold:
[   0.2020] | [ True]
[   0.0083] | [ True]
[   0.0004] | [ True]
[   0.0125] | [ True]
[   0.0046] | [ True]
[   0.9373] | [*False*]
[   0.0029] | [ True]
[   0.0412] | [ True]
[   0.1569] | [ True]
[   0.1617] | [ True]]

[   0.9631] | [ True]
[   0.9625] | [ True]
[   0.9087] | [ True]
[   0.9652] | [ True]
[   0.9863] | [ True]
[   0.9646] | [ True]
[   0.9638] | [ True]
[   0.9635] | [ True]
[   0.9592] | [ True]
[   0.9679] | [ True]

However, when I use the regular predict, which does not need the separate image folders as predict generator, then, for 10 random images (out of 100), I get the following individual and not reasonable predictions:
1/1 [==============================] - 0s
Prediction is:  0.0

data2\part\img (99).jpg
1/1 [==============================] - 0s
Prediction is:  0.0

data2\part\img (29).jpg
1/1 [==============================] - 0s
Prediction is:  0.0

data2\part\img (53).jpg
1/1 [==============================] - 0s
Prediction is:  0.0

data2\part\img (79).jpg
1/1 [==============================] - 0s
Prediction is:  0.0

data2\part\img (83).jpg
1/1 [==============================] - 0s
Prediction is:  0.0

data2\part\img (27).jpg
1/1 [==============================] - 0s
Prediction is:  0.0

data2\part\img (94).jpg
1/1 [==============================] - 0s
Prediction is:  0.0

data2\part\img (48).jpg
1/1 [==============================] - 0s
Prediction is:  0.991576

data2\part\img (93).jpg
1/1 [==============================] - 0s
Prediction is:  0.0

data2\part\img (32).jpg
1/1 [==============================] - 0s
Prediction is:  0.0

data2\part\img (60).jpg
1/1 [==============================] - 0s
Prediction is:  0.0

data2\part\img (31).jpg
1/1 [==============================] - 0s
Prediction is:  0.0

data2\part\img (21).jpg
1/1 [==============================] - 0s
Prediction is:  0.0

data2\part\img (12).jpg
1/1 [==============================] - 0s
Prediction is:  0.0

data2\part\img (21).jpg
1/1 [==============================] - 0s
Prediction is:  0.0

data2\part\img (27).jpg
1/1 [==============================] - 0s
Prediction is:  0.0

data2\part\img (23).jpg
1/1 [==============================] - 0s
Prediction is:  0.0

data2\part\img (26).jpg
1/1 [==============================] - 0s
Prediction is:  0.0

data2\part\img (6).jpg
1/1 [==============================] - 0s
Prediction is:  0.0

Since inside I have 50 hydrangea and 50 nature images; then, it does not make sense that ALL predictions are cero.
Any insights on this?

Is this still an issue ?
Are you using tensorflow backend here ?


Adds date ranges for role assignments

Fixes #13

Regarding adding ACME ... Wile E. Coyote would be proud.  :-)

Discussed WG 20231204. No objections.


ci: sign the jar

Checklist

[x] Tick to sign-off your agreement to the Developer Certificate of Origin (DCO) 1.1
[x] Added tests for code changes or test/build only changes
[x] Updated the change log file (CHANGES.md|CHANGELOG.md) or test/build only changes
[x] Completed the PR template below:

Description
Generate and upload jar signature.
Fixes #122
Approach

build.gradle

Set env vars as appropriate project extra properties to configure signatory
Add onlyIf to skip signing when no env vars set
Add signing extension config for jar file

Jenkinsfile

Add env vars for signing creds
Add additional upload for signature

Schema & API Changes

"No change"

Security and Privacy

"No change"

Testing

N/A build or packaging only changes - tested the following:

gradle builds without env vars skip the signing task
Jenkins build produces signature file
gpg verified the generated signature

Monitoring and Logging

"No change"

+1 but maybe there's some dead code left in there?


Tag Release

https://packagist.org/packages/laravel-notification-channels/webex
@askmrsinh Can tag a release :)

Thanks 👍
One last thing, could you please rename this repository to webex (lowercase)?

Done


Update README.md

An alternative way to "Windows+R"- run to get to the correct place of the nuget plugins.

Thank you for your contribution!


Added Connectivity check for NATS and MeshSync + Minor Refactor

Description
This PR fixes:

Change MeshSync chip to ad hoc connectivity test.
Change NATS chip to ad hoc connectivity test.

Notes for Reviewers
Signed commits

[x] Yes, I signed my commits.

Codecov Report

Merging #4191 (ea080b1) into master (2227a06) will decrease coverage by 7.57%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #4191      +/-   ##
==========================================
- Coverage   26.91%   19.34%   -7.58%
==========================================
  Files          59       59
  Lines        5031     5015      -16
==========================================
- Hits         1354      970     -384
- Misses       3262     3750     +488
+ Partials      415      295     -120

Flag
Coverage Δ

gointegrationtests
?

unittests
19.34% <ø> (+0.16%)
:arrow_up:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

mesheryctl/internal/cli/root/system/status.go
0.00% <0.00%> (-62.83%)
:arrow_down:

mesheryctl/internal/cli/root/system/start.go
0.99% <0.00%> (-53.98%)
:arrow_down:

mesheryctl/internal/cli/root/system/stop.go
0.85% <0.00%> (-36.76%)
:arrow_down:

mesheryctl/internal/cli/root/system/update.go
1.05% <0.00%> (-34.74%)
:arrow_down:

mesheryctl/internal/cli/root/system/restart.go
2.50% <0.00%> (-31.43%)
:arrow_down:

mesheryctl/internal/cli/root/system/check.go
1.39% <0.00%> (-22.38%)
:arrow_down:

mesheryctl/internal/cli/root/system/logs.go
0.00% <0.00%> (-21.60%)
:arrow_down:

mesheryctl/internal/cli/root/config/config.go
12.79% <0.00%> (+2.90%)
:arrow_up:

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 8fab9be...ea080b1. Read the comment docs.

Task linked: CU-1fzt52f Change NATS chip to ad hoc connectivity test.

Task linked: CU-1fzt529 Change MeshSync chip to ad hoc connectivity test.

@dhruv0000 before we create message types, which we should, please see the Messaging Framework and Notification Center design spec. // @mgfeller

Lets merge this till we decide if / what kind of Message Type we need for Broadcaster.
Issue tracked at #4195


Update warewulf.conf documentation for 4.3

https://warewulf.org/docs/enchiridion/configuration/ is out-of-date and needs to be updated for 4.3.

I'm happy to do this myself: can it be assigned to me?

Cleaning up old issues.


Add '$-pipe' and 'pipes'.

'pipes' returns two files that can be
used in redirects, $-pipe returns a pipe
that can be used to read the job output.
Here are some examples of usage:
($$ cat < ($-pipe echo hello))
(file/read ($-pipe echo hello) :all)

This PR depends on a new janet patch.


$t_0$ and $t_1$ in test-field-std-time

In section 4.1.3 field generation, test-field-std-time, $t_0$, and $t_1$ are mentioned in the input, and there is a big space in between them. Are they also input into the test or are they just the time stamps whose std will be recorded?

They are the two input times.


Preserve symlinks when installing

The lldb-preview component includes symlinks.  Currently, rustup
changes these to be regular files while installing.  This then causes
the resulting lldb to load liblldb twice, which causes a crash at
startup, because command line options are registered twice.  This
changes rustup to preserve symlinks when installing.

I wasn't sure if I should base this on stable perhaps?

LGTM!


Add support for docker-compose.yml files.

All credits goes to @pedropombeiro! I just reopend his PR. See original PR #1431 for more details.
Fix #390

Any update on this? Looks like it's been a pending PR for two years now...

Any update on this? Would love to have support for Docker Compose updates. Currently we have to resort to https://github.com/renovatebot/renovate for this.

👋 Sorry for the delayed response.
The reason it's "floating" is that we're currently not accepting new ecosystems, but we're also not planning for that to be true forever. So PR's adding new ecosystems are currently on-pause.

@jeffwidman this PR doesn't add a new ecosytem, it just improves a existing docker ecosystem by adding support for a commonly used file where docker images are defined.
So it would be great if you can check again if this PR should be on hold because of the "currently not accepting new ecosystems" policy.

👋 Sorry for the delayed response.
The reason it's "floating" is that we're currently not accepting new ecosystems, but we're also not planning for that to be true forever. So PR's adding new ecosystems are currently on-pause. Once we have the capacity to support new ecosystems, then we plan to go through some of these PR's evaluating them on case-by-case basis.

Hi @jeffwidman
Few months ago, PR https://github.com/dependabot/dependabot-core/pull/5348 has been accepted. It is very similar, at least in concept, to this one. Does that mean that a PR for docker compose can be taken into consideration now?

@jeffwidman Is there any chance you can reconsider the label for this change?
I also agree with the previous sentiment that this is not a new ecosystem. This change enhances the existing support for docker as docker compose files are effectively part of the same docker ecosystem

@jeffwidman Is there any chance you can reconsider the label for this change?
I also agree with the previous sentiment that this is not a new ecosystem. This change enhances the existing support for docker as docker compose files are effectively part of the same docker ecosystem

Let's have that discussion on the associated issue, and keep the discussion on this PR about implementation details if/when we're ready to pull it in.
On that note, I posted my thoughts on the topic over in that ticket here:
https://github.com/dependabot/dependabot-core/issues/390#issuecomment-1526217251

Does anybody know if it is possible to use this fork and how?
I see that dependabot.yml includes a version field, but I don't think I can just point to this branch with that.
Disappointing that this takes several years to merge.

Is there a way we can help out with this PR?
What can we do to get this change that is highly sought after since 2018 and in review and put on hold multiple times since 2019 off the ground?
I would love to use this feature as would so many others. Supporting Docker but not Docker Compose means so many workflows are broken and the available workarounds either mean migrating from this tool entirely, or breaking the image pulling without building functionality in existing codebases provided by Docker Compose.

Potential Ideas

Provide a list of tasks or other blocking jobs that could aide the PR in being reviewed for the community to pitch in and help with.
Allow as an experimental or beta feature, or document as being a work in progress, which allows the minimum viable product to still be used and tested by others.
Seek additional maintainers to lessen the workload and prevent review from blocking PRs for years at a time

These are just some quick notes, all with the best intentions, all responses are welcome

Any status update on this? Support for Docker but not compose remains a large gap

Since commenting I've switched to using Mend Renovate instead, it is night and day better than dependabot


programatically move slider with function..is it possible?

I'm on 2.2.2 of the slider. I can upgrade if needed.
Anyway to programatically move the sliider.
I noticed that once it gets set according to the first initial value, there is no way to move it without touch the display and moving the slider.
I would like to for example, move to a different index on the slider based on options selected on a different screen while the previous screen was mounted.
Anyways to expost a ref and do like ref.current.moveTo? Didn't see it in the documentation.

Or create a new component by changing the key={new value}

Fair enough, I will try that! Thx


Splitting esp8266_mission_control into HTTP and TCP managers

The current esp8266_mission_control  handles both HTTP processing and TCP connection management.  It may help to move these into seperate classes. That way we are not tied to the esp8266 for the TCP connection and we could also implement other communication protocols over the same TCP connection class.

split-mission-control splits the mission control for drive


Fix regressions in JSON view

The JSON in the transaction view page now has noticeable regressions:

the view is not collapsible or hidden by default
the fields are not copyable
larger objects cannot be collapsed and restored on demand: clicking the ellipsis expands arbitrarily large content, with no way to collapse it.

We should restore the functionality that previously existed, I'm not sure why this needed to be rewritten.

Context:

We start getting unmet peer dependencies warnings in our console when we do pnpm install.
Turns out react's most used json viewer (react-json-view) is now abandoned by its maintainer.
Given the required peer dependency is an old version of react, we are in a bit of a risky state by keeping this dep. A new version of react we update to could silently break our tx details page. We are kinda just lucky it hasn't so far.
Time to look for a new package to replace it
@textea/json-viewer appears to be actively maintained and feels like a kind of successor given how similar the features/design looks. A PR (https://github.com/penumbra-zone/web/pull/696) is opened to migrate to this. Has feature parity. After review, it's brought up that this would increase our bundle size and that we should seek for something more lean. react-json-view-lite is then used instead given how lean it is. However, we lose the features you mentioned above.
Given how minimal it is, a later PR (https://github.com/penumbra-zone/web/pull/813) adds more features like design improvements and open/collapse logic.

To recover those features from the migration, we could simply revert to the commit in that PR that implements @textea/json-viewer. It is a larger size than react-json-view-lite, but perhaps it doesn't matter. Minifront's bundle size comparisons with different json viewer libs:

react-json-view (original): 4.50 MB
@textea/json-viewer: 4.49 MB
react-json-view-lite: 4.40 MB

The 92kb diff feels like something we can live with.

i think i made some opinionated choices in #813 that conflict with @hdevalence's preferences

i deliberately made the root view expanded by default and hide its collapse button, but that doesn't have to be the case
i deliberately made all fields below the 'collapse level' default to expanded, so that inspecting a deeply-nested field didn't require may clicks
large objects are indeed collapsible on demand. but notably the collapse is achieved with the arrow next to the field name, and not the ellipsis which disappears when expanded. a changing collapse/expand arrow button is supported, but i chose to hide the 'expand arrow' in favor of the ellipsis alone, as an aesthetic choice
text fields no longer each pesent an individual copy button, but a single click highlights the entire field (even the part after the ellipsis) and it is copyable
buttons for 'expand/collapse all' and 'copy all' are available in the top right

i advocated react-json-viewer-lite as a replacement for the unmaintained dep in the interest of bundle size, and i think bundle size should be the primary concern when we select dependencies, but i have no particular attachment otherwise

notably, react-json-view-lite developer AnyRoad seems very responsive to issues so we may be able to just ask or PR for things like copy button

Thanks for the context, I didn't realize that there wasn't just a concern about the presence of a maintainer but also that it was actively at risk of breakage.
In general, I think:

for a package like this, it's probably fine for the dependency to be "unmaintained" if there's not an active problem with it and it's not core functionality
bundle size should probably not be a concern

Fine-tuning the JSON formatting seems like a pretty low priority relative to our other work so I'm happy to close it out.


Genomics service

I created a storage account as the output location for my genomics service. It works well to output delta tables into my storage container but requires the token when I want to output a vcf file into it.

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 8fcb147c-ad94-4926-6cec-da6013c6006a
Version Independent ID: a2a1e627-0b49-4757-51b3-9a1e3ddd432e
Content: Quickstart: Run a workflow - Microsoft Genomics
Content Source: articles/genomics/quickstart-run-genomics-workflow-portal.md
Service: genomics
GitHub Login: @grhuynh
Microsoft Alias: grhuynh

@YidiQin Thank you for your query. We will have this reviewed and update the thread.

@YidiQin Thank you for your query. We will have this reviewed and update the thread.

This is likely unrelated to the genomics service - it is more likely an issue with your the access restrictions you have placed on your storage account. You can read more about how to set those here https://docs.microsoft.com/en-us/azure/storage/common/storage-auth?toc=/azure/storage/blobs/toc.json__

This is likely unrelated to the genomics service - it is more likely an issue with your the access restrictions you have placed on your storage account. You can read more about how to set those here https://docs.microsoft.com/en-us/azure/storage/common/storage-auth?toc=/azure/storage/blobs/toc.json__

@YidiQin Please review your configuration as per the request and let us know . In case you are able to get it working after providing proper access as per the article . If it still does not work for you , please let us know with an error screenshot and we will help you further on this.

@YidiQin Please review your configuration as per the request and let us know . In case you are able to get it working after providing proper access as per the article . If it still does not work for you , please let us know with an error screenshot and we will help you further on this.

@YidiQin I hope that you are able to solve the issue with recommendations from @grhuynh . In case it has not worked for you . please do send us an email on azcommunity [at] microsoft [dot] com

@YidiQin I hope that you are able to solve the issue with recommendations from @grhuynh . In case it has not worked for you . please do send us an email on azcommunity [at] microsoft [dot] com


Windows on ARM support?

Since SSMS is not available for ARM, I was seeing out alternatives and ran across this.  Of course I can use mssql-cli's x86 edition via emulation, but I've been trying to only use natively compiled applications on my ARM device.  Is there any hope of an ARM64 compilation for Windows on ARM?  I need something lightweight like this to complement Visual Studio Code which is available natively on ARM64.

Definitely doable. This was prototyped awhile back in branch https://github.com/dbcli/mssql-cli/tree/ron/arm_support.

Definitely doable. This was prototyped awhile back in branch https://github.com/dbcli/mssql-cli/tree/ron/arm_support.


MLIR quantizer produces asymmetric quantization for int16 activations

1. System information

OS Platform and Distribution (e.g., Linux Ubuntu 16.04): Ubuntu 22.04
TensorFlow installation (pip package or built from source): pip package
TensorFlow library (version, if pip package or github SHA, if built from source): 2.17.0

2. Code
with open("calibrated.tflite", "rb") as model_file:
    calibrated_model = model_file.read()

inference_type = convert.convert_inference_tf_type_to_tflite_type(tf.dtypes.int16)
tflite_model = convert.mlir_quantize(calibrated_model,
                                     fully_quantize=True,
                                     inference_type=inference_type,
                                     input_data_type=tf.dtypes.int16,
                                     output_data_type=tf.dtypes.int16)

with open("quantized.tflite", "wb") as model_file:
    model_file.write(tflite_model)

Input file:
calibrated.zip
Output file:
quantized.zip
3. Failure after conversion
The model cannot run on TFLite Micro with CMSIS-NN, as its fully connected kernel supports only symmetric quantization for int16 activations.
5. (optional) Any other info / logs
The quantizer already tries to take into account the int16 requirements here: https://github.com/tensorflow/tensorflow/blob/master/tensorflow/compiler/mlir/quantization/common/quantization_lib/quantization_utils.h#L238 and here: https://github.com/tensorflow/tensorflow/blob/master/tensorflow/compiler/mlir/quantization/common/quantization_lib/quantization_utils.h#L266
But it's not enough, as it should also set narrow_range before calling quantfork::fakeQuantAttrsToType here: https://github.com/tensorflow/tensorflow/blob/master/tensorflow/compiler/mlir/quantization/common/quantization_lib/quantization_utils.h#L248 and here: https://github.com/tensorflow/tensorflow/blob/master/tensorflow/compiler/mlir/quantization/common/quantization_lib/quantization_utils.h#L274
Otherwise the zero point might drift to -1, as it happens with the attached files.

Hi, @pkgoogle
Please take look into this issue. Thank you

Hi @tagunil, would you be willing to submit a PR? As it seems you have already identified root cause here.

Hi @pkgoogle, I would be happy to submit a PR for this issue and a couple of others, but, unfortunately, we're still struggling with the CLA for the time being.

Hi @paulinesho, can you please take a look? Thanks.

I've checked https://github.com/tensorflow/tensorflow/pull/76584 and that's what we need, thanks @paulinesho!


java.lang.UnsatisfiedLinkError: no jnitensorflow in java.library.path for mkl-gpu (works for non-mkl gpu)

System information

Have I written custom code (as opposed to using a stock example script provided in TensorFlow): no
OS Platform and Distribution (e.g., Linux Ubuntu 16.04): Win10
Mobile device (e.g. iPhone 8, Pixel 2, Samsung Galaxy) if the issue happens on mobile device: N/A
TensorFlow installed from (source or binary): binary
TensorFlow version (use command below): 2.4.1 / 0.3.1
CUDA/cuDNN version: 11.0.2 / 8.0.2
GPU model and memory: Titan RTX, 24gb

Describe the current behavior
Using tensorflow-core-platform-mkl-gpu v 0.3.1 in Win10 with Java 8 results in:
java.lang.UnsatisfiedLinkError: no jnitensorflow in java.library.path
	at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1860)
	at java.lang.Runtime.loadLibrary0(Runtime.java:870)
	at java.lang.System.loadLibrary(System.java:1122)
	at org.bytedeco.javacpp.Loader.loadLibrary(Loader.java:1683)
	at org.bytedeco.javacpp.Loader.load(Loader.java:1300)
	at org.bytedeco.javacpp.Loader.load(Loader.java:1123)
	at org.tensorflow.internal.c_api.global.tensorflow.<clinit>(tensorflow.java:12)
	at java.lang.Class.forName0(Native Method)
	at java.lang.Class.forName(Class.java:348)
	at org.bytedeco.javacpp.Loader.load(Loader.java:1190)
	at org.bytedeco.javacpp.Loader.load(Loader.java:1139)
	at org.tensorflow.NativeLibrary.load(NativeLibrary.java:48)
	at org.tensorflow.TensorFlow.init(TensorFlow.java:111)
	at org.tensorflow.TensorFlow.<clinit>(TensorFlow.java:126)
	at org.tensorflow.SavedModelBundle.<clinit>(SavedModelBundle.java:438)

Using tensorflow-core-platform-gpu (i.e. non-mkl) v 0.3.1 works.
Describe the expected behavior
Both versions should work.
Code to reproduce the issue
Use existing sample program and switch the dependency to tensorflow-core-platform-mkl-gpu v 0.3.1

It's not currently possible to build TensorFlow with both CUDA and MKL enabled on Windows. There's apparently a way to work around that documented in Chinese here, but no one has taken the time to try it out:

https://blog.csdn.net/u012440550/article/details/113361176#t11

If you could take the time to report this bug upstream, we may be able to get engineers from Intel working on this! Thanks

Upstream MKL support got folded in to the native binary, and we're using those binaries now.


docs: remove css.module from default

It is invalid after 1b5bdde1

Thanks, it will be back in the next release.


Pop up an error 'command 'vscode.previewHtml' not found' when opening a Graph Explorer

OS: Windows/Mac
Build Version: 20190313.1
Repro Steps:

F1 -->Type and select 'Graph(Gremlin):Open Graph Explorer'.
Select a subscription --> Create a Gremlin account --> Create a new database --> Create a new Graph.
Check the result.

Expect:
Succeed to open Graph Explorer and no error pops up.
Actual:
Pop up an error.

Is this vscode Insiders?

Hi @StephenWeatherford yes, we always test with VS Code-insiders.

Pop up below warning like #1038 when we verified this issue with the stable VS Code.

Please verify if this still repros. Should have been fixed in 0.10.1


Printing stylesheet isn't the same as other pages

When I print this page in Windows on Chromium Edge, the first few words on the left-hand-side of the page are getting cut off.

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 1b1e0765-a7aa-6e76-3aca-751dc8a531dc
Version Independent ID: e95861b3-cfd3-2b75-95e8-1c0176ba79f2
Content: Quickstart: Direct web traffic using the portal - Azure Application Gateway
Content Source: articles/application-gateway/quick-create-portal.md
Service: application-gateway
GitHub Login: @vhorne
Microsoft Alias: victorh

@jfjcn, We have assigned this issue to the respective content developer for providing better insights.

@jfjcn, We have assigned this issue to the respective content developer for providing better insights.

no repro. Perhaps this is specific to your environment.

no repro. Perhaps this is specific to your environment.

#please-close


context.request* should gaurantee index

https://github.com/nnstreamer/nntrainer/blob/f26937ee48243bb099edd37538d90054cd735d3d/nntrainer/layers/layer_context.h#L144-L145
above todo is critical when guaranteeing serialized weight layout, without those kind of deterministic assumption, we cannot load weight outside context of layer.
eg) fully connected layer has weight - maps to a, bias - maps to b
When we load the weight from different place, the layer weights will maps to weight - a', bias - b'.  we have to guarantee a == a', b == b'. If this indexes are determined per run, we cannot never make such assumption.

:octocat: cibot: Thank you for posting issue #1814. The person in charge will reply soon.


core-js update seems to have updated with breaking changes

./node_modules/formiojs/PDF.js Module not found: Can't resolve 'core-js/modules/es6.array.find'
The PDF.js file at the formiojs github doesn't have the same references, but I can't get that version to show up locally, and the core-js version that gets installed changed the names of the files that PDF.js is trying to import. I've tried manually changing the file imports but there's also some references to files that don't exist in the current core-js either.

Or I'm missing something else...

This seems to have happened with the update of core-js@3. You will need to use 2.x version of core-js. Try typing the following within your application to see if this goes away.
npm install --save core-js@2

Oh cool, that worked. That could be fixed automatically by updating the package.json file in formio.js, right? Add to dependencies "core-js": "2.x"?

Yeah I think so. We will add that to our list.

Cool. Thanks!


raise connection error when no cellect hosts available

handle the case where the cellect node_set is empty and thus the returned host will be nil.

LGTM, but I feel like all this should really be done by the cellect client object (and thus be extracted to the cellect gem)

I think it's valid behavior for a client to return nil if there are no hosts...it's up to the user to figure out what todo in that scenario, ignore / raise.

@marten Ah - do you mean move the client code from here to the gem? We could look at that.

Yes. But again, fine to merge until then


Update request: github-runner: 2.317.0 -> 2.318.0

Package name: github-runner
Latest released version: 2.318.0

Current version on the unstable channel: 2.317.0
Current version on the stable/release channel: 2.317.0

[x] Checked the nixpkgs pull requests

Notify maintainers @veehaitch @newam @kfollesdal @aanderse @zimbatm

Note for maintainers: Please tag this issue in your PR.
I got the package updated but a ton of tests fail.  Hopefully there's a .net expert here that can help out.
Feel free to use any part of this in a PR: https://github.com/newAM/nixpkgs/commit/6e83ac1b0d4119139e6b89b342959d4c0c5da5f1

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

v2.319.0 is out now.


PS move config tool don't show up controller settings

Hi,
After I've paired the PS Move controllers, nothing happens. It should jump straight to the settings but instead, goes back to the menu where it tells me to pair the controller again. Under Controller Pairing is Controller Settings and it reads 'No connected usable controllers'. Is this a bug or have I missed something to cause this?

When I connected my controllers to my laptop, menu showed up. But when i used my dongle Asus bt400 on ma laptop sam problem as i have on my pc

After week of trying, i almost give. After all I uninstalled my bt drivers and used this one, and it worked for me.
https://www.driverscape.com/download/generic-bluetooth-adapter

I'm having the same issue. As soon as its done pairing, it screws itself up. I haven't tried reinstalling my bluetooth yet tho. I'm also wondering if using a BT adapter that's built into my motherboard (ASUS TUF Gaming X570 + wifi) is somehow... dumb or something?
I did have the controllers pairing properly yesterday; I was having the same issue but I accidentally used magic or my 1 luck point for the year because they suddenly worked and i couldn't figure out why. After I shut it down for the night and booted everything back up in the morning, however, I was back to step 1: controllers won't connect.
I think i had trinius and steamvr running and then opened psmoveconfig while psmovesteamvrbridge was auto run by steamvr but i cant recreate my immense stupidity.

I removed controllers from my PC, then reinstalled drivers for BT and used file from #634. After that everything works fine.
Maybe it's your built in BT.

I guess I'm not really sure what that means, or how this website works now that I'm looking at it. How do I use the files from 634? It sounds like I need to modify psmoveservice with them or something.
(I reinstalled my BT and that didn't fix anything.)

I mean only this file
https://1drv.ms/u/s!An8ls2qnV1z_n_57p7s2utrsq_x0LQ

Replace original file with this, pair your controllers and then replace it with original file.

still nothing. idk. i noticed everyone's using ps3 move controllers, i guess ps4 move's dont sync well maybe, or its my internal BT or something. Also, I feel like there's probably something wrong with the fact that everytime I'm syncing the controllers I have to "Allow connection to device." Whenever I click Allow it turns off psmoveservices or psmoveservicesadmin. I tried disabling it but couldn't find the option.
Don't worry about me though, i've already spent two days on this, I'll get back to it later.
thanks for helping Wikster


[DB] rm datasets remove ref.png

From this issue: https://github.com/Inria-Asclepios/medInria-public/issues/222
In the database directory, with this PR, ref.png files are realy removed when their dataset is removed.
:m:

Done @fcollot


Consider Turning ContentProvider Into a Non-Static Class

Summary
As part of the general maintainability and testability push with Duality, one of the goals is reducing the amount of static API and extracting self-contained instance classes where possible. ContentProvider would be an excellent candidate for this.
Analysis

Make ContentProvider a non-static class and introduce IDisposable API to allow for content cleanups.
Since static access is still required, have a singleton-like instance in a static DualityApp field.
The new API would likely be something like DualityApp.Content.Request(xy), which isn't much less convenient than before and even comes with some user-side advantages such as extension method support.

Progress

Made ContentProvider a non-static class, with a singleton-like global instance stored in DualityApp.Content.
Renamed ContentProvider API to avoid the redundant use of the word Content in nearly every method name.
Resolve handlers now have precedence over the default Load behavior.
Extracted default content handling code from ContentProvider and moved it into a static internal DefaultContent utility class.
Extracted static, path-based utility methods GetNameFromPath, GetFullNameFromPath and IsDefaultContentPath from ContentProvider and moved them to the Resource class.
Removed special cases that would prevent users from removing any default content from ContentProvider. As non-global instances would now be possible, there should be full control over each instance.

ToDo

Write unit tests for ContentRef<T>.
Write unit tests for ContentProvider.
Review the new API and changes and address any remaining issues.
Merge back to develop-3.0. Consider doing a squash-merge.

After the initial work on this, it should be reconsidered whether to follow through on this issue. Turning ContentProvider into a non-static class has advantages, but also introduces a bit of a design dissonance: As long as ContentRef<T> and other classes are hardwired to use a single, shared instance, resource management remains essentially static, and all other ContentProvider instances remain non-functional. Loading a Texture via a custom provider will for example trigger loading its dependent Pixmap, but do so using the shared instance, not the custom one.
Secondly, it remains an unresolved issue how to handle multiple providers in the first place. A ContentRef can only work when knowing where to request resources from, and having multiple places for this complicates the situation a lot with very little gain. Can the same content path now mean different things depending on which provider is asked? Can a ref that failed with provider A recover using provider B? Are refs locked to providers? What happens to a ref using a provider that was disposed?
Overall, it seems like a static, non-instance setup just makes a lot of sense in the ContentProvider case. It should be considered to revert all changes made as part of this issue, but retain some of the changes that are unrelated to the static / non-static change, such as:

Resolve / Load handler precedence.
Extracting default content handling code, to be moved to a static DefaultContent utility class or similar.
Extracting path-based utility methods, to be moved to Resource.
Removing default content special cases, so default content can be removed just the same as any other content.
Consider keeping some of the API changes that were introduced.

Progress

Turned ContentProvider back into a static class.
Renamed most ContentProvider API back into including the "content" keyword, as it's no longer redundant with the static API.
Added unit tests for basic ContentProvider functionality.
Fixed a bug in RenameContentTree for paths including repetitions.
Improved ContentRef recovery to work based on disposed Resource instances by keeping their path property valid on disposal.

ToDo

Write more unit tests for ContentRef<T> and ContentProvider.
Squash-Merge back to develop-3.0.

Progress

Added more unit tests for ContentProvider. Skipping ContentRef tests for now, as they're non-breaking and non-critical for now.
Squash-Merged back to develop-3.0

Didn't manage for some reason to include more than one line into the squashed commit message using SourceTree. Is this a bug? Not sure. In any case, here's the missing commit message part / changelog:
ContentProvider Bugfixes, Tweaks, API Changes, Tests

#ADD: Added unit tests for the most basic functionality of the ContentProvider.
#FIX: Fixed a bug in ContentProvider renaming behavior where Resource paths with repetitions would fail to be renamed correctly.
#CHANGE: Resources now retain their original path when disposed, allowing ContentRefs to recover based on disposed resources.
#CHANGE: Removing content from the ContentProvider now handles cases where a single Resource is registered on multiple path keys.
#CHANGE: Added content to the ContentProvider on an already used path will now dispose the previously registered Resource.
#CHANGE: Moved specialized code for discarding plugin related data out of ContentProvider and directly into the DualityApp event handler that requires it.
#CHANGE: Moved static, resource path based API from ContentProvider to Resource.
#CHANGE: Moved loading / handling of embedded default content from ContentProvider and Resource to internal static DefaultContent utility class.
#CHANGE: Default content is no longer treated with a readonly special case in ContentProvider, and a call to Clear will remove both default and non-default content.
#CHANGE: Renamed ContentRef.MakeAvailable to EnsureLoaded
#CHANGE: Internal handling of default content no longer requires a specific init code segment, and instead tracks additions and removals.
#CHANGE: Resource Resolve handlers now take precedence over automatically loading Resources from the Data directory.


Simplify the "ReaderHeadersReady" message-handler in the API

We can just return the existing Promise directly, and don't need to create a temporary one with Promise.withResolvers().
Given the age of this code it shouldn't hurt to simplify it a little bit.

/botio test

/botio unittest


[Docs] mesheryctl system mesh validate page missing

Current State
No page exists for this command in the mesheryctl Command Reference.
Desired State
A docs page for this subcommand should be available.
Implementation

Create an entry for this subcommand in https://github.com/layer5io/meshery/tree/master/docs/_data/mesheryctlcommands/

Contributor Resources

Meshery documentation site
Meshery documentation source
Instructions for contributing to documentation

Perfect, @amino19, yes.


antsibull-changelog - config&directories

I added changelog directory with the config file. And I added fragments subdirectory. Any correctly created yaml file in the fragments directory will be picked up by antsibull-changelog generate and will be added to changelog.yaml in changelog folder and CHANGELOG.rst in main directory (can be adjusted)

can you please also add a fragment: i.e. initializing changelog handling

done

recheck


add ck/ac/knuw.txt

url : https://www.knuw.ac.kr/knuw/main.do
e-mail<EMAIL_ADDRESS>students
College (University) or Undergraduate School or equivalent

@eomziC I have to close this request without merging, because you requested to add a non-existent domain to this repository: Host knuw.ac.ck not found: 3(NXDOMAIN) Please ensure that you are familiar with this repository rules located at the bottom of this page and submit a new request with the correct information. Thank you for your understanding!


fixing typos

There were a few typos I corrected that should have no effect on functionality.

Hello! We appreciate your contribution. Unfortunately, your work does not follow the contributing guidelines, and this PR will be closed.
In the future, please make sure you read over the guidelines for each repository you wish to make commits to, and work with the development teams to follow their procedures. This makes things easier for them, and more fulfilling for you!


Adding ODIN assets on INJ

Summary by CodeRabbit

New Features

Added metadata for ODIN and DOKI tokens, enhancing token information with name, logo, and additional details for users.

I don't see token metadata information for myrk and o9w. Also, some of the images are too big in size, please reduce them or convert to webp


focus point keyboard movement is buggy

Focus point for keyboard movement appears to be buggy when switching between months, years, and days

focus point is buggy when changing the ordering of the dates in the calendar. As of now, the dates are shown in order and the focus point on the keyboard is accurate


getting-started/helloworld fail to deply

While following instruction to issue:
gcloud functions deploy HelloGet --runtime go111 --trigger-http
under the helloworld folder, I got the following error message:
Deploying function (may take a while - up to 2 minutes)...failed.
ERROR: (gcloud.functions.deploy) OperationError: code=3, message=Build failed: /tmp/sgb/gopath/src/serverlessapp/worker.go:18:2: import "serverlessapp/vendor/main" is a program, not an importable package

I changed run time of app.yaml from
runtime: go
env: flex
to
runtime: go111
that fixes the problem.


⚠ Bofrost.lu has degraded performance

In 72a942d, Bofrost.lu (https://www.bofrost.lu) experienced degraded performance:

HTTP code: 200
Response time: 1164 ms

Resolved: Bofrost.lu performance has improved in 8756e3d after 15 minutes.


Update observers.md

There were a couple of places that read in a confusing way. Hopefully they are now easier to digest.
Very light changes

Much appreciated!


Unknown value 'Dolby Surround' in TwoChDecoder

Describe the bug
I am using this integration with a Yamaha RX-A3070
After restarting Home Assistant I always find the mentioned warning in the logs
To Reproduce
Expected behavior
Diagnostics
config_entry-yamaha_ynca-a5c3d179eae68e0c6def24ff16a2248f.json.txt
Logging
Error in Home Assistant Core
Logger: ynca.enums
Source: /usr/local/lib/python3.11/site-packages/ynca/enums.py:409
First occurred: 4:54:13 PM (1 occurrences)
Last logged: 4:54:13 PM

Unknown value 'Dolby Surround' in TwoChDecoder

Environment
Provide details about the versions you are using, which helps to reproduce and find the issue quicker.

Home Assistant Core version: 2023.9.2
Home Assistant operating environment (OS/Container/Supervised/Core): OS 10.5
Yamaha YNCA: 7.5.0

Additional context
Everything works fine and I haven't noticed any issues so far.

Newer receivers seems to support more/different surround decoder modes. Your receiver has a value I have not seen before, so there is no mapping.
From the manual it seems your receiver also has an "Auto" mode which is probably also missing. Could you cycle through all the modes and attach the diagnostics again? I can then add all the modes that are missing in one go.

The part your are missing from the integration is the surround decoder selection. See screenshot to see how it looks for my receiver. If it would be useful I can try adding it for other receivers, but I don't think I can autodetect which soundmodes are supported for a receiver so that would be another list in the settings like soundmodes/inputs where you would need to manually select supported surround decoders.

Ok, I cycled through the surround modes
config_entry-yamaha_ynca-a5c3d179eae68e0c6def24ff16a2248f.json-2.txt

Thanks for the complete list of Surround decoder modes. Will try to get at least the list update released fast so the errors are gone.
Making it configurable in the integration configuration will take a bit longer as it is more complicated to build. But when that is done the Surround Decoder selection should show up for all receivers.
The list of entities for your receiver seems to be complete as far as I can tell.
Only thing I see missing compared to my receiver are the bass/treble controls for headphones and speakers. From the diagnostics it looks like your receiver does support some kind of treble/bass control but uses different commands for it (TONETREBEL and TONEBASS). If it would be useful I can add those controls, but I would need more info on what the range and stepsize are and there is also a TONEMODE (only for zone 2 and 3) which is probably related to the bass/treble control.
Do you feel anything else is missing?

First I want to thank you for making this integration available.
As the receiver is in my media room and only used to watch Movies I don’t actually need tone control as I am quite happy with the automatic room correction.
I only use the main zone the rest of the house uses C4 Matrix and AMP.
But I might try to loop through the setting to provide some details on the weekend, just in case.

FYI I just released v7.5.1 which should get rid of the warning.
I will keep this issue open as a reminder to make the surround decoder values more extendible so it should work for all receivers.

Updated to latest version but still don't see the Surround Decoder options but log warning is gone
Attached is a diagnostic log including the tone control information. I never used this option as I optimised room using  YPAQ.
config_entry-yamaha_ynca-a5c3d179eae68e0c6def24ff16a2248f.json-3.txt

but still don't see the Surround Decoder options

That is expected, the 7.5.1 update only got rid of the warning (and a few other small things that were pending).
The current surround decoder entity only supports a fixed set of values. Extending it to make it support the other modes you found and have them configurable by the user (as it can't be autodetected) is more work for which I unfortunately don't have time right now. I will pick this up later.
Thanks for the log. I would be able to add the bass/treble for your receiver with that.

Sorry for the long wait. I finally got around implementing support for all (currently) known surround decoders in v7.6.0.
Note that you will have to select the surround decoders supported by your receiver in the integration configuration as it can not be automatically detected.

No worries, I don't actually use HA to control the receiver as it is only used in the media-room to basically watch movies which is mostly Netflix. But this might change soon if I can get the Samsung projector and the Yamaha Receiver to work nicely together in HA.
Fix looks great and I could configure my supported surround decoders.

Thanks for getting this implemented


Problems running KeyDive in Windows

Hello,
After running pip install keydive on Windows and having all the packages installed, I'd try running keydive -aw or python keydive -aw and the result is as follows
C:\Users\Antonio>keydive -aw "keydive" is not recognized as an internal or external command, program, or executable batch file.
C:\Users\Antonio>python keydive -aw python: can't open file 'C:\Users\Antonio\keydive': [Errno 2] No such file or directory
How can I fix this? Thank you so much in advance!

The scripts route wasn't in PATH so that's why it failed. Now it works!


Reference full Java class names in g4 files

Remove header imports for ExpressionInfo and StatementInfo.
This removes "The import ... is never used" warnings in Eclipse.

LGTM


Autoformat python syntax with black

Signed-off-by: Christian Berendt<EMAIL_ADDRESS>

Replaced by #601


Fix automodule on ReadTheDocs

https://ocds-babel.readthedocs.io/en/latest/api/extract.html is empty. It's not empty when the docs are generated locally.

I had to check "Install Project" under "Advanced Settings" on ReadTheDocs.


Added support for Bower

All this does is adds support for bower package management. Yep, it's outdated, but in our inperfect world there's still projects which use it (like mine, dah).

@pesla it would be great if you can merge this soon.


[Merge] hereditary angioedema type 3 AND  hereditary angioedema with normal c1inh

Mondo term(s) (ID and Label)
"iri" : "http://purl.obolibrary.org/obo/MONDO_0012526",
"label" : "hereditary angioedema type 3",
AND
"iri" : "http://purl.obolibrary.org/obo/MONDO_0033947",
"label" : "hereditary angioedema with normal c1inh",
Reason for review
OMIM states, for HAE3: It differs from HAE types I and II (106100) in that both concentration and function of C1 inhibitor (C1NH; 606860) are normal
What is the distinction we are trying to make between these sibling terms?

Also, if both are kept, the capitalization of C1inh needs to be corrected.

Hi Nicole!  Orphanet has all the subtypes (please see the classification below).   In GARD we probably will only have the parent term “Hereditary Angioedema” but I will let you know when we have decided.
ORPHA:91378   Hereditary angioedemahttps://www.orpha.net/consor/cgi-bin/Disease_Search.php?lng=EN&data_id=12136&Disease_Disease_Search_diseaseGroup=Hereditary-angioedema&Disease_Disease_Search_diseaseType=Pat&Disease(s)/group of diseases=Hereditary-angioedema&title=Hereditary angioedema&search=Disease_Search_Simple  Synonym(s) : Hereditary bradykinine-induced angioedema ; Hereditary non histamine-induced angioedema
 *   ORPHA:528623   (Disorder)   Hereditary angioedema with C1Inh deficiency<https://www.orpha.net/consor/cgi-bin/Disease_Search.php?lng=EN&data_id=27541&Disease_Disease_Search_diseaseGroup=Hereditary-angioedema&Disease_Disease_Search_diseaseType=Pat&Disease(s)/group%20of%20diseases=Hereditary-angioedema-with-C1Inh-deficiency&title=Hereditary%20angioedema%20with%20C1Inh%20deficiency&search=Disease_Search_Simple>
    *   ORPHA:100050   (Subtype of disorder)   Hereditary angioedema type 1<https://www.orpha.net/consor/cgi-bin/Disease_Search.php?lng=EN&data_id=14623&Disease_Disease_Search_diseaseGroup=Hereditary-angioedema&Disease_Disease_Search_diseaseType=Pat&Disease(s)/group%20of%20diseases=Hereditary-angioedema-type-1&title=Hereditary%20angioedema%20type%201&search=Disease_Search_Simple>
    *   ORPHA:100051   (Subtype of disorder)   Hereditary angioedema type 2<https://www.orpha.net/consor/cgi-bin/Disease_Search.php?lng=EN&data_id=14624&Disease_Disease_Search_diseaseGroup=Hereditary-angioedema&Disease_Disease_Search_diseaseType=Pat&Disease(s)/group%20of%20diseases=Hereditary-angioedema-type-2&title=Hereditary%20angioedema%20type%202&search=Disease_Search_Simple>
 *   ORPHA:528647   Hereditary angioedema with normal C1Inh<https://www.orpha.net/consor/cgi-bin/Disease_Search.php?lng=EN&data_id=27542&Disease_Disease_Search_diseaseGroup=Hereditary-angioedema&Disease_Disease_Search_diseaseType=Pat&Disease(s)/group%20of%20diseases=Hereditary-angioedema-with-normal-C1Inh&title=Hereditary%20angioedema%20with%20normal%20C1Inh&search=Disease_Search_Simple> Synonym(s) : Hereditary angioedema with normal C1 inhibitor
    *   ORPHA:537891   ANGPT1-related hereditary angioedema with normal C1Inh<https://www.orpha.net/consor/cgi-bin/Disease_Search.php?lng=EN&data_id=27912&Disease_Disease_Search_diseaseGroup=Hereditary-angioedema&Disease_Disease_Search_diseaseType=Pat&Disease(s)/group%20of%20diseases=ANGPT1-related-hereditary-angioedema-with-normal-C1Inh&title=ANGPT1-related%20hereditary%20angioedema%20with%20normal%20C1Inh&search=Disease_Search_Simple>
    *   ORPHA:100054   F12-related hereditary angioedema with normal C1Inh<https://www.orpha.net/consor/cgi-bin/Disease_Search.php?lng=EN&data_id=14627&Disease_Disease_Search_diseaseGroup=Hereditary-angioedema&Disease_Disease_Search_diseaseType=Pat&Disease(s)/group%20of%20diseases=F12-related-hereditary-angioedema-with-normal-C1Inh&title=F12-related%20hereditary%20angioedema%20with%20normal%20C1Inh&search=Disease_Search_Simple>  Synonym(s) : Hereditary angioedema type 3
    *   ORPHA:537072   PLG-related hereditary angioedema with normal C1Inh<https://www.orpha.net/consor/cgi-bin/Disease_Search.php?lng=EN&data_id=27892&Disease_Disease_Search_diseaseGroup=Hereditary-angioedema&Disease_Disease_Search_diseaseType=Pat&Disease(s)/group%20of%20diseases=PLG-related-hereditary-angioedema-with-normal-C1Inh&title=PLG-related%20hereditary%20angioedema%20with%20normal%20C1Inh&search=Disease_Search_Simple>

Thank you!  Gioconda
From: Nicole Vasilevsky<EMAIL_ADDRESS>Sent: Wednesday, June 10, 2020 6:36 PM
To: monarch-initiative/mondo<EMAIL_ADDRESS>Cc: Alyea, Gioconda (NIH/NCATS) [C]<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [monarch-initiative/mondo] [Merge] hereditary angioedema type 3 AND hereditary angioedema with normal c1inh (#1628)
Thanks @galyea-gardhttps://github.com/galyea-gard
I think the action items are:

[ ] 'hereditary angioedema type 3' (MONDO_0012526) should be a child of Hereditary angioedema with normal C1Inh (MONDO_0033947)
[ ] merge 'angioedema, hereditary, type 1/2' with 'hereditary angioedema with c1inh deficiency'. Note- 'hereditary angioedema with c1inh deficiency' is a grouping class in Orphanet for 'hereditary angioedema type 1' and 'hereditary angioedema type 2'

We can see this in the Orphanet hierarchy:
https://www.ebi.ac.uk/ols/ontologies/ordo/terms?iri=http%3A%2F%2Fwww.orpha.net%2FORDO%2FOrphanet_91378&viewMode=All&siblings=false
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/monarch-initiative/mondo/issues/1628#issuecomment-642303001, or unsubscribehttps://github.com/notifications/unsubscribe-auth/APG3MG56ADGD3WAZV4T343TRWADDVANCNFSM4NQWDKSA.


[MXNET-722][WIP][DO NOT MERGE] Maven publish pipeline demo

Description
https://github.com/apache/incubator-mxnet/issues/11933
Hi @marcoabreu @KellenSunderland @szha @nswamy ,
This PR will show off the ways that we can use CI to publish Scala package to Maven. As we discussed earlier in the mailing list, the publish process should be done in a restricted node with AWS credential provided.
Be aware, this package will be formed into a pure dynamically-linked way which means no dependencies will be wrapped together into a single piece.
Checklist
Essentials
Please feel free to remove inapplicable items for your PR.

[x] The PR title starts with [MXNET-$JIRA_ID], where $JIRA_ID refers to the relevant JIRA issue created (except PRs with tiny changes)
[ ] Changes are complete (i.e. I finished coding on this PR)
[ ] All changes have test coverage:
Unit tests are added for small changes to verify correctness (e.g. adding a new operator)
Nightly tests are added for complicated/long-running ones (e.g. changing distributed kvstore)
Build tests will be added for build configuration changes (e.g. adding a new build option with NCCL)
[ ] Code is well-documented:
For user-facing API changes, API doc string has been updated.
For new C++ functions in header files, their functionalities and arguments are documented.
For new examples, README.md is added to explain the what the example does, the source of the dataset, expected performance on test set and reference to the original paper if applicable
Check the API doc at http://mxnet-ci-doc.s3-accelerate.dualstack.amazonaws.com/PR-$PR_ID/$BUILD_ID/index.html
[x] To the my best knowledge, examples are either not affected by this change, or have been fixed to be compatible with this change

Since there are some dependencies installation required in docker, I think I should create a new dockerfile for these changes.

Thanks for your contribution @lanking520
@mxnet-label-bot[pr-awaiting-testing, pr-work-in-progress]

@lanking520 Is this PR still WIP?

Close this since @zachgk is working based on this.


Message Preview is not working - Certificate issue

after renewal of the secret for the Author app and Graph app the preview message does not work with following error:

I have updated the new secret to all necessary places withing function apps and the app service.

Hello @JasGo00 ,
Thanks for reaching out to us!
Could you please confrim if this is a new deployment or old? If its a new deployment please verify the secret value is copied and updated and not the client secret id for the app registrations. You need to follow the below steps to generate new client secrets and update at respective places -

Go to Azure Portal
Go to App registration
Create a new secret value for app registration and grab secret value. Here is the reference.

Then go to resource group. Select key vault from list of resources.
Click on secrets under object section.

If the secrets are not visible, Go to Access Policy--> Click on Create

Select Key, secret and certificate management

Give the Id through which one can view the secrets

3rd step is optional
Go for Review+Create
Then go to Secrets. Open author/user/graph app password
Click new version

Grab the new secret identifier

Paste it in the configuration sections of app service, 3-function apps. Here is the reference of updating the author app password in app service configuration.

Follow the same procedure for the user app password and graph app password updating.
For graph app, please dont forget to update the password in AzureAd Client Secret as well. here is the reference

Hello
this is an old deployment... I just renewed the certificate for Graph and Author apps...I have done all these steps and checked it 3 times, but the Preview is not working. this is the only thing that is not working

Hello @JasGo00
Please let us know if you are still facing this issue and require assistance and we will be happy to discuss. If no further action is needed at the moment and no response is received, we will close out the issue in 2 business days.
You may also always open a new issue or respond here if something does come back up.
Regards,

Yes we still have the problem and need assistance with this issue. We can send messages as I stated in my first post, but the preview is not working

Hi @JasGo00
Could you please check whether you have updated author app id in author's manifest file
reference:

could you please share email id so that we can start discussing the issue internally

OK, Thanks looking forward to the resolution

Hello.
I am not sure why do I need to update the app ID? That did not change.
However the key and the secret have been updated in the Manifest file
@.***
@.***
Best regards
Jasmin Gokovic
BD/WPA-UCS1 / MS Teams/Skype
Mobile +1(248)310-2978 |<EMAIL_ADDRESS>From: peddivyshnavi @.>
Sent: Tuesday, September 3, 2024 4:30 AM
To: OfficeDev/microsoft-teams-apps-company-communicator @.>
Cc: Gokovic Jasmin (BD/WPA-UCS1) @.>; Mention @.>
Subject: Re: [OfficeDev/microsoft-teams-apps-company-communicator] Message Preview is not working - Certificate issue (Issue #1553)
Hi @JasGo00https://github.com/JasGo00
Could you please check whether you have updated author app id in author's manifest file
reference:
image.png (view on web)https://github.com/user-attachments/assets/52195790-adf9-48b8-907f-95055279f9e0
could you please share email id so that we can start discussing the issue internally

Reply to this email directly, view it on GitHubhttps://github.com/OfficeDev/microsoft-teams-apps-company-communicator/issues/1553#issuecomment-2325911019, or unsubscribehttps://github.com/notifications/unsubscribe-auth/BABNUQTH64VUSQNGCOLB33DZUVXRTAVCNFSM6AAAAABNEDBLQCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGMRVHEYTCMBRHE.
You are receiving this because you were mentioned.Message ID<EMAIL_ADDRESS>

we have connected internally for call regarding Message Preview issue

upon investigating we got to know there is an issue with author and graph secrets. we have created new secrets and updated. after update we see issue got resolved. now we see preview functionality is working as expected.

we see issue of 16,000 unreceived messages, and we have mentioned to go with manual query which will elimates users which doesn't have CC will be removed from group.

we see there is issue in exporting detailed results we have cleared out the table for export data to attempt a fresh report

Could you please let us know if you are still facing this issue with preview message

The issue with the preview has been resolved.... However I am still waiting on the query to be able to delete the stale User Data... can you please send that to me as soon as possible.
Thanks!
Best regards
Jasmin Gokovic
BD/WPA-UCS1 / MS Teams/Skype
Mobile +1(248)310-2978 |<EMAIL_ADDRESS>From: peddivyshnavi @.>
Sent: Thursday, September 5, 2024 4:07 AM
To: OfficeDev/microsoft-teams-apps-company-communicator @.>
Cc: Gokovic Jasmin (BD/WPA-UCS1) @.>; Mention @.>
Subject: Re: [OfficeDev/microsoft-teams-apps-company-communicator] Message Preview is not working - Certificate issue (Issue #1553)
we have connected internally for call regarding Message Preview issue

upon investigating we got to know there is an issue with author and graph secrets. we have created new secrets and updated. after update we see issue got resolved. now we see preview functionality is working as expected.
we see issue of 16,000 unreceived messages, and we have mentioned to go with manual query which will elimates users which doesn't have CC will be removed from group.
we see there is issue in exporting detailed results we have cleared out the table for export data to attempt a fresh report

Could you please let us know if you are still facing this issue with preview message

Reply to this email directly, view it on GitHubhttps://github.com/OfficeDev/microsoft-teams-apps-company-communicator/issues/1553#issuecomment-2330876500, or unsubscribehttps://github.com/notifications/unsubscribe-auth/BABNUQQ36IBADUT3AVLJE7DZVAGJZAVCNFSM6AAAAABNEDBLQCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGMZQHA3TMNJQGA.
You are receiving this because you were mentioned.Message ID<EMAIL_ADDRESS>

I was able to use this query with extracted user IDs to delete almost 17,000 lines in the User Data table. I need to wait for next company wide message to see the result of this change

Hi @JasGo00
Marking this ticket as closed as we see issue with preview message got resolved
Could you please open a new ticket regarding another issue so that it will be easy to track the issue.
Thanks


Resident Evil Revelations 2 (287290) stutters like hell

the game has some severe stutters the whole time, it goes from a survival horror to a pure horror piece of videogame because of that. :frog:
Software information
Resident Evil Revelations 2, Highest settings
System information

CPU: Ryzen 2400G
GPU: RX 560D 4GB
Driver: mesa 21.3.4
Wine version: 7.0 RC6
DXVK version: v1.9.3-9-ga268de51

Apitrace file(s)

DXVK APITRACE: (https://drive.google.com/file/d/1KKQ8YGRkv_gFXPK5UzSxmM_PUFuh-93M/view?usp=sharing)

Log files

d3d9.log: rerev2_d3d9.log

Might be related to #2084

Note: same engine as RE0,RE1 remake
so might be related yes

I sent Kassin a DLL to with direct buffer mapping mode disabled and he confirmed that it fixes the issue. So it is indeed the same problem as #2084.

with that magic DLL the game runs smoothly, better than it ever runned on WIndows natively, that's pure magic and i'll play the game comfortably for the first time in my life, thank you kobin

I sent Kassin a DLL to with direct buffer mapping mode disabled and he confirmed that it fixes the issue. So it is indeed the same problem as #2084.

Can you please send me that file to fix the stuttering? My game is stuttering a lot, and even more using dxvk.

The fix was merged. Just get the latest build of DXVK.

I tried using the latest DXVK version. It seems working fine for a while, but the game still stutters a lot constantly. I've been playing 2 hours now and each new scenario begins to stuttering. Most of the time happens with the flashlight turned on, when I shoot an enemy, some explosion occurs or when I enter to a new room.

Sounds like regular shader stutter 👀

Yes and no. If I play the same episode again using dxvk, the game works almost just fine, I'd say even better than the vanilla version. But the stuttering appears here and there occasionally, mostly when I shoot an enemy, opening a door or any explosion occurs. Do I need to play all the game with dxvk to compile the shaders and fix the stuttering? Isn't any way to compile all shaders completely the first time I play it?
Also, I don't see any dxvk_cache file into the game's root. Is that normal?

Do I need to play all the game with dxvk to compile the shaders and fix the stuttering?

To an extend yes since dxvk can't know before it encounters them the shaders that can be compiled into the cache.
Steam shader pre caching should help with some games. But i don't know the details of how well it works between different GPU's, drivers and game updates. Or how often the caches that steam provides are updated.

Also, I don't see any dxvk_cache file into the game's root. Is that normal?

If you have steam shader pre cache enabled then yes that is normal. The cache is instead located in ~/.steam/steam/steamapps/shadercache/ and then the appID of the game. Along with driver caches.
If you turned off shader pre caching a cache file should appear in the games root folder or next to the exe in a sub folder yes.
If more complete caches are avaliable it might help https://github.com/begin-theadventure/dxvk-caches/tree/main/dxvk-caches But i'm not totally sure about that since i don't know technical details.

Isn't any way to compile all shaders completely the first time I play it?

Good news on that front is that recently on the dxvk master branch there have been ongoing work into solving, or helping alot, this issue for a lot of games. With it, depending on how the game handles it, alot of the shaders should be possible to compile before seeing them directly in the game. Like loading screens or in the main menu. Pre built caches could probably also be provided for that.
Tho at the moment only the nvidia beta vulkan driver supports the extension required for it.


Currying

Coverage increased (+9.7%) to 87.379% when pulling 9a52465b6af4b1cdc603df5a066148e38f2f6929 on currying into 5f75a07eed752f652a390bab76f5cfba35703a8f on master.


Refresh index

Could you please create a JIRA ticket so that we can track this improvement? Otherwise it looks good to me.

Hi,
opened the Jira issue, https://issues.apache.org/jira/browse/UNOMI-357
thanks for reviewing :)


Height transition results in empty string

Works (raw react-motion):
<Motion style={{ height : 88 }} defaultStyle={{ height : 0 }}>
  {value =>
}
</Motion>

Doesn't:
<Transition component={false} enter={{ height : 88 }} leave={{ height : 0 }}>

</Transition>

Nothing happens and the resulting height is "". I haven't had problems with other cases that don't involve height, e.g. paddingLeft and top.

I can't immediately think of anything that could be causing, I'll have a look at this when I can.

I'm currently tied up, but I will look into this as soon as I can and see what is wrong. Probably has to do with 'auto' height logic killing the value. Thank you for posting the issue @neverfox.

Fixed https://github.com/souporserious/react-motion-ui-pack/blob/master/CHANGELOG.md#070


Time to release the 500 solves test edit limit?

So, for those users who are not powered enough, once any language versions of a kata reaches 500 solves the test cases is locked and it's impossible to edit them anymore (except by @jhoffner himself).
This has become a great deal of daily pain for power users, because it doesn't fix the pile of old katas with poor tests that are lying around, and in the end the power users suffer from this:

People complaining about the weak tests in old katas which allows faulty solution to pass (e.g Did I Finish my Sudoku?)
Similarly, the lack of random tests
Tests that are vulnerable to input modification (this is especially bad, we literally have to respond to enquiries about this every day or so, so bad that some had to made a kata about this)
New kata makers taking bad ideas from these katas and make weak tests (this happens very often too, because CW's trainer suggestion is pretty badbiased: it keeps suggesting popular katas, so the old ones which are done more will get much more exposure than the new ones)

IIRC @jhoffner said somewhere that the original intention of the 500 solve lock was to prevent changes invalidating the test cases. However:

Almost all kata authors of these katas are not active anymore for a long time anyway, so these katas will not receive any changes in general
This would be a problem if the one performing the edit is bad and keep breaking things, but the edit button is, well, reserved to power users and kata author only
You have to invalidating existing solutions anyway if they're not conformal to the kata requirement, which means speaking from the premise there's no reasons to avoid invalidating solutions at all
As mentioned above, we have strong reasons to fix these historical debts

I guess the only question would be: if we re-validate all the solutions, how long does it take to re-validate 1 million solutions or so? I'm estimating 1 million because it's around the total solves of the site entry kata aka multiply. I guess it's prooobably still okay to leave a very low priority task for days re-validating old kata solutions?

I think we can lower the estimate to ~100k instead of 1mil since we don't have to fix Multiply itself (otherwise the site is broken from the beginning!) and the largest count of solves on a single kata was around 80k IIRC when I saw it. But still, we have a ton of such broken katas and they will likely add serious burden to the CW server if we fix them simultaneously.
(Also, I believe someone actually said that the 500 lock was to prevent server overloading, so removing the lock is probably not feasible before the CW moves to another platform, I guess?)

I believe someone actually said that the 500 lock was to prevent server overloading

That was me, but it was just a guess of mine, and is not official by any account.

Main reasons for lock:

re-evaluating lots of solutions is going to be taxing on the servers
some good well intentioned user could come along and decide to improve the test cases, and do so in a way that invalidates almost every solution that has been submitted already.

Possible solutions:

Increase the limit (works for reason #1, doesn't help with #2)
Simply retire older kata that aren't great
Prevent publishing changes to the solution and the test cases at the same time (would at least minimize #2, doesn't solve #1)

I don't honestly know how big of a performance issue #1 is. If the change is made and everyone has a field day updating older kata, it could cause the servers to get locked up enough that the site is temporarily not usable for non-red users. In practical terms, it might be ok.

Simply retire older kata that aren't great

That'd be talking about over 100 katas (my estimate is 200-300 at least), so this probably isn't a good idea either. I'd prefer just fixing them, though faulty solutions should be invalidated by this too otherwise it's not too meaningful.

The performance issues actually shouldn't be too bad. The revalidation process is already the lowest level background job there is. Worst case, other solutions from other challenges just take a long time to be rechecked.
We could consider opening up the limit at least temporarily, give power users a month to clean up the older kata, and then perhaps close it back up if we run into any difficulties.

Maybe we create a thread where people can nominate retirees.

Yeah, that's something that should be done at some point, along with

re-evaluating the ranking of old katas (most of them are seriously overranked)
retiring dangling betas that are flat out duplicates, now that I've plowed through over half of the beta katas

Though honestly there are lots of hot garbage among white published katas, and it's hard to say what exactly it means by high quality: many of those white katas have weird/nonsensical tasks/requirements, and many of them have weak tests (they're happening independently). Depending on what the majority of us think high quality is the amount of katas that end up being retired could vary by a lot. And honestly, I don't think satisfaction rating is a very useful metric here.

Adding edge cases and random tests are fine to me, anything else is just too big of a change to even bother. I'd leave this to the judgement to power users. After all, if a power user isn't editing the test cases properly, he'd be pointed at by others publicly ;-)

I expect most power users will agree on this.

re-evaluating the ranking of old katas (most of them are seriously overranked)

If this takes place, will our rank progress and honor change with it?

retiring dangling betas that are flat out duplicates, now that I've plowed through over half of the beta katas

Retiree thread looks like a good option here, as well as for some broken old katas. (Maybe a Gitter channel dedicated for this?)

If this takes place, will our rank progress and honor change with it?

Probably not currently because there's a bug with this: see #1112 and #1109.

Let's roughly make a plan what'll happen (and should happen) if the test lock is released in the future, in order of urgency:

Fix problematic katas, mostly Swift/Go language versions that are broken due to compiler version (medium effort, not many of us are fluent in Swift/Go)
Fix katas with non-conforming tests, e.g the 3 blue/purple sudoku katas currently existing (lots of effort. Also the same thing with the random tests might happen for this too)
Fix katas with random tests susceptible to input modifications (small effort, just deep clone everything)
Fix flipped expected/actual values in test assertions (tiny effort)
Add random tests to katas without them (LOTS of effort. Also we might end up discovering author's reference solution is wrong or the kata requirement has unspecified edge cases or something)
Change Test.expect to Test.assertEquals (and Test.assertSimilar to Test.assertDeepEquals for objects and arrays in JS) when applicable (lots of effort since that's pretty much 99% of the old katas)
Check that the translations are consistent with each other, or as least as consistent as possible, in terms of test cases, input ranges and amount of tests (not too much effort but require lots of skill, so probably only a handful of power users is capable of doing this)
Enable Python 2/3 compatibility for Python language versions (lots of effort)

I just realized that a kata must have "allow contributors" enabled in order to be editable by power users. What should we do if we encounter a kata with obvious issues but contribution disabled? Could we "force-edit" such a kata (using a criterion similar to translation approval, with the delay of X years), or should it be just retired, even if its issues are relatively minor or easy to fix?

IIRC the 1-week kata edit rule bypasses the "allow contributor" choice.

@Voileexperiments

Fix problematic katas, mostly Swift/Go language versions that are broken due to compiler version (medium effort, not many of us are fluent in Swift/Go)

Go shouldn't have version issues. Can you list some examples?
For Swift, it's been really difficult because I had to rewrite the runner. The original one didn't specify the version, required compiling Swift from source (changed the test framework included), the image took hours to build, etc.
The change should've been mostly compatible with existing contents. The only issue I'm aware is that the change disallowed top level expressions in solution/preloaded. This is because the files are no longer concatenated into main.swift.
I'm not sure if there're issues caused by language versions. The original one wasn't using stable release (3.0-dev or something and drifted because it wasn't locked) and it's been 3.1 since the rewrite. The new runner supports both 3.1 and 4.0.
Another issue with Swift is that some user expect some features that is not available when using Swift on Linux (like arc4random). This can't be fixed from our end.

Go shouldn't have version issues. Can you list some examples?

Not sure, but off my head I remember Go language version have crippling issue (test literally un-runnable) about as often as Swift language version, so I thought it's about roughly the same problem.
Other than Go and Swift it's mostly Python 2/3 (especially with the caveat of ////) and sometimes Node version aka ES6/ES7 features. Speaking of which, enabling Node 8 support (except for a few katas where the lack of support is intended) for all old JS katas is also something we need to do:

Enable Node 8 compatibility for JS language versions (LOTS of effort)

I've lifted the 500 limit for all users who have more than 10k honor. That's currently over 100 users. Lets see how far that gets us and take it from there. I haven't made this a dedicated privilege yet.
I'm closing this issue for now. I'll rely on you guys and especially @Voileexperiments to help monitor the progress and report if any issues come up by lifting this limit.

@jhoffner Are you sure the limit is correctly lifted? Because I was just trying to fix https://www.codewars.com/kata/sum-of-digits-slash-digital-root, and when I open the edit page the test cases are still locked and not editable.

It seems the limit was removed in production site now.


Update package to use node 20

Can you please update action to use nodejs 20?
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20<EMAIL_ADDRESS>For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.

Happy to create a PR

Done to Node 20.


Feat post auth screens

Summary of Changes
Added ability to have screens appear post enter pin screen but before the splash screen. Useful for updates to eula screens and presenting new features
https://github.com/openwallet-foundation/bifold-wallet/assets/36937407/f555fe04-1359-474c-a55c-b64458509465
Related Issues
N/A
Pull Request Checklist
Tick all boxes below to demonstrate that you have completed the respective task. If the item does not apply to your this PR check it anyway to make it apparent that there's nothing to do.

[x] All commits contain a DCO Signed-off-by line (we use the DCO GitHub app to enforce this);
[x] Updated LICENSE-3RD-PARTY.md for any added dependencies or vendored components;
[x] Updated documentation as needed for changed code and new or modified features;
[x] Added sufficient tests so that overall code coverage is not reduced.

If you have any questions to any of the points above, just submit and ask! This checklist is here to help you, not to deter you from contributing!
Pro Tip 🤓

Read our contribution guide at least once; it will save you a few review cycles!
Your PR will likely not be reviewed until all the above boxes are checked and all automated tests have passed.

PR template adapted from the Python attrs project.

Codecov Report
Attention: Patch coverage is 32.09877% with 55 lines in your changes are missing coverage. Please review.

Project coverage is 61.77%. Comparing base (3b63696) to head (aa3f004).

Files
Patch %
Lines

packages/legacy/core/App/screens/Terms.tsx
0.00%
10 Missing :warning:

...ges/legacy/core/App/navigators/OnboardingStack.tsx
0.00%
9 Missing :warning:

packages/legacy/core/App/screens/Splash.tsx
50.00%
8 Missing :warning:

...kages/legacy/core/App/screens/PushNotification.tsx
36.36%
7 Missing :warning:

packages/legacy/core/App/navigators/RootStack.tsx
0.00%
6 Missing :warning:

packages/legacy/core/App/screens/PINEnter.tsx
14.28%
6 Missing :warning:

...ackages/legacy/core/App/contexts/reducers/store.ts
68.75%
5 Missing :warning:

packages/legacy/core/App/screens/NameWallet.tsx
0.00%
2 Missing :warning:

packages/legacy/core/App/screens/UseBiometry.tsx
50.00%
2 Missing :warning:

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #1123      +/-   ##
==========================================
- Coverage   61.95%   61.77%   -0.19%
==========================================
  Files         179      179
  Lines        5762     5808      +46
  Branches     1659     1674      +15
==========================================
+ Hits         3570     3588      +18
- Misses       2169     2197      +28
  Partials       23       23

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

Questions:
1. What is the purpose of the `onboardingVersion` state? Does that account for all the different wallets that use Bifold?

2. Have you tested the upgrade path?

3. Have you tested the wallet naming feature during onboarding?

onboardingVersion is used to detect what version of onboarding the user has encountered. ie if the onboarding version is "0" then we check if onboarding is complete by looking if they've considered biometry since that was the last screen in the old onboarding flow. Otherwise we use didCompleteOnboarding to check if a user has completed onboarding.
I've tested all the onboarding flows now, there was a bug in the onboarding flow when wallet naming was enabled but I've resolved that now. I've tested the path when a user with an existing installation loads up the app and it's working as intended


Templates

This is my favorite most useful plugin.  I only use it for PHP
I am amazed by what you can do with this.
For me I would really like to be able to do something like this...
/**class[ENTER]

/**
 * @class [description]
 * @description
 * @version some version
 * @author  Jason Davis
 * @requires Dependencies
 * @todo [description]
 * @example [description]
 */

So at other time it will work like it does now but when I type class after /** it then uses a template for how I want a Class comment to be.
Would really like to see something like this possibly, thanks for the great plugin

Cool idea, I'll definitely take a look at it.

Hi Jason,
I'm going to close this with a "won't fix" sorry. The reason is that there'd be no template generic enough to be included inside the plugin by default, and so it'd be a custom template created by each user anyway. Sublime gives you the ability to create these as a snippet. They can even be scoped to only be applicable inside documentation comment blocks, so the flow would be:
/**<enter>

/**
 *
 */

/**
 * class<tab>
 */

Let me know if you need any more help with this.


Remove gcc from deps of lz4

It doesn't seem to me the crate lz4 uses gcc anywhere. lz4-sys still uses gcc so it doesn't really reduce its dependencies, though.

Thanks a lot.


Pr mag cal fix

This PR :

Fixes a bad assumption in sensor calibration code, which assumed that uORB instance ID == the ID of the file descriptor (e.g /dev/sensor_gyroX) for a sensor. This would lead to offsets being applied to the wrong sensor depending on the race between driver instantiation and uORB advertisement. This was hidden so far because of the startup order of sensors on non-v4Pro and non-v5 boards.
Enables temperature compensation and boot-calibration for HMC5x83 mags running on v4Pro and v5 hardware, which should improve performance in general.
Fixes MPU9250 mag driver to properly publish it's device ID.
Fixes LIS3MDL mag driver to properly publish it's device ID.
Adds checks to the sensor calibration code which will fail the calibration if there are inconsistencies in device IDs (usually pointing to a buggy sensor driver) so that we can catch them out and fix them. These problems have remained hidden so far because nothing was forcing a sanity check.

This needs :

Test flights on Pixhawk 1 / Pixhawk Mini, Pixhawk 2.1, Pixracer and Pixhawk Pro. Full parameter reset and redo all calibrations before flying.
Bench tests on Snapdragon Flight / Bebop / RPi to make sure that calibration still works as normal.

Awesome work!

We still need the fix is more places, I think. Flight test on Pixhawk Pro with correct mag orientation showed toiletbowling, so it seems that there is something still wrong. Will keep working on this.

Can you please share a log? I don't think that validating it using a flight says anything about correctness - it just says that the system you flew wasn't right.
It could be that the calibration data was wrongly assigned and is now correctly, etc. Please try to check separately for correctness and we'll handle any churn (e.g. a required re-calibration) separately iff required.

More locations in the code needed the fix. See the commit I just pushed : https://github.com/PX4/Firmware/pull/7287/commits/6f8997ea5d6d7f56e6336b5b207438f7cf8cbb40
However, since now we only set the rotation matrix on startup, it would require a reboot after calibration. I added the @reboot_required flags to the params, but this might need some more support on QGC calibrator side to properly propagate up to the user.

pixhawk mini; good flight, no issues.
http://review.px4.io/plot_app?log=f7047899-fd47-4ec6-9897-1b50642af153

OK, looks good. Can you test on v4 hardware? Normally it would not tell us much because v1-v4 hardware didn't expose the bug, but I will give you a custom binary in that case, which will force that situation. It would be good to fly with the board and external compass rotated (on yaw) with respect to the frame (any rotation should do). Make sure you reset params and recalibrate, setting the correct orientations during calibration.
Here is the binary for Pixracer :
px4fmu-v4_default.px4.zip

flight on pixracer
http://logs.px4.io/plot_app?log=c7c761de-baca-4b8b-974a-8aa984768e59

couple successful flight with the pixracer; external mag rotation set to yaw 270
http://logs.px4.io/plot_app?log=56252cbf-206b-43ca-8ea7-0e3129a70a7f
http://logs.px4.io/plot_app?log=770f0776-ced8-4a82-8217-80c72db9cb4f

@santiago3dr @Avysuarez Thanks for the testing. Looks good!
@LorenzMeier Good to merge after CI passes, and we make sure that QGC asks for a reboot after setting board/compass rotation.

@jywilson @mcharleb Can you please test this on Snapdragon? Please do a parameter reset and recalibrate all sensors to make sure that the calibration routine still functions properly. A bench test will be enough.


implement Sum

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

11 of 26 (42.31%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.3%) to 15.983%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

hi.go
11
26
42.31%

Totals

Change from base Build<PHONE_NUMBER>:
0.3%

Covered Lines:
331

Relevant Lines:
2071

💛  - Coveralls


Clarifying prevent delivery usage

Hi folks, quick question - I see that there was a PR to prevent delivery of the messages but I wasn't quite sure how it should be used? Based on the test, it seems like one would need to declare a prevent_delivery method in the PostMark module. Is that correct?
If yes, thoughts on instead making it one of the options passed in to the mail method?
Thank you!

Hey @oyeanuj sorry for the severely late response to this. The idea would be that you could define a prevent_delivery? method in your mailer subclasses based on whatever logic you want, and the PostmarkMailer::Base class would honor it. For instance, we use this on ScienceExchange.com to honor users' email preferences. I agree that it would probably be helpful to add it as an option to pass in for each individual mailer action for more granular control, but I don't think I'll be able to get to that any time soon. If you were to open a PR to implement this, I would be happy to review it.

@oyeanuj I've added some documentation to the README covering basic usage of the #prevent_delivery? method.


Update release process

What type of PR is this?

/kind documentation
What this PR does / why we need it:
Update release process about fixing version of Kubespray
Which issue(s) this PR fixes:

Fixes #
Special notes for your reviewer:

/lgtm

/lgtm


Move all JS projects from the AE to their own folder

I realize this is opinionated, but I feel "hiding" the JS projects nested deeply inside the VS projects is a mistake as it gets hard to find and properly manage with gitignore. It also exposes the webpack stuff better and more consistently.

Closing and resubmitting after a rebase to resolve merge conflicts.


[V9] Migrate to Bootstrap 5

Let's move Concrete CMS to Bootstrap 5
Updated libraries:

PHP: pagerfanta/pagerfanta: to v2.7 (Needed to use TwitterBootstrap5Template)
JS:    bootstrap-select to v1.14.0-beta2 (library supports BS5 only from v1.14 but still in beta)

requires a companion Bedrock PR concrete5/bedrock#151

This is tremendous. Really really nice work

This is really tremendous – but I've merged in some changes recently that have some significant conflicts. Can you add form-label to the label() method of the form class? Kind of like how we've added form-check-input to the checkbox method by default? I think that will significantly reduce the amount of files you need to modify in the core, and it will make it a lot easier for developers who are using the label() method instead to get the proper class in it.
Let me know if this is a problem and we might be able to merge this in first and make changes later.

Hello @aembler ,
I added .form-label to label label()  as you suggest, and yeah that's more easier to use.
I had just to force .form-check-label margin-bottom to 0 to prevent unwanted display issues when we get  .form-label  and .form-check-label together in a <label>.
I've resolved the conflicts as well.

This has been completed in the 9.0rc branch. Thanks for all your help! I will close this PR.


Can't save the Open Shortcut

In Pharo 7, you can't seem to change the open shortcut from Shift-Tab to anything else. If you type something in, and then try to save it it just adds meta-s as an additional shortcut.

To add to this - for anyone stuck - to get out of this mode, you have to disable Mirage and then re-enable it, and it will clear that shortcut field for you.

I just had a look, I see why it is broken so I will investigate soon.

Hum, in fact I think that it is the settings UI that is broken...

I'm seeing that in P8 as well


fix bug that displays start when server has been stopped

Context
Fix 485
The server stop messages was titled: "Start". Now correctly titled: "Stop"
Choices

Test instructions

Checklist before requesting a review

[ ] I have performed a self-review of my code
[ ] I've added documentation about this change to the README.
[ ] I've not introduced breaking changes.

You beat me to it, I was submitting a PR now. I'm very new to this and didn't know if submitting an issue first and then a PR or just a PR immediately was proper etiquette.

@xHyperElectric Both are fine! would benefit from a small message stating that you are fixing it right now, so we don't do double the work ;)

would benefit from a small message stating that you are fixing it right now, so we don't do double the work ;)

Noted!