[Feature]: Documentation Request: Clarification on OCO_MESSAGE_TEMPLATE_PLACEHOLDER Usage

Description
First off, I'd like to say how much I've enjoyed exploring the opencommit tool – it's evident that a lot of thought and effort has gone into its development. While diving in, I stumbled upon the OCO_MESSAGE_TEMPLATE_PLACEHOLDER feature. The current documentation reads:
To include a message in the generated message, you can utilize the template function! For instance:

oco '$msg #205’
opencommit examines placeholders in the parameters, allowing you to append additional information before and after the placeholders, such as the relevant Issue or Pull Request. Similarly, you have the option to customize the OCO_MESSAGE_TEMPLATE_PLACEHOLDER configuration item, for example, simplifying it to $m!"

I genuinely appreciate the guidance provided. However, I felt a bit uncertain about some aspects and believe that a touch more clarity could help users like me get the most out of this fantastic tool.
Suggested Solution:

Enhance the Documentation: Building upon the existing documentation could make a world of difference:

A deeper dive into the "template function" would be enlightening.
Breaking down the example oco '$msg #205’ to clarify its components could be beneficial for users.
Expanding on the "placeholders" concept with more examples would offer a richer understanding.
Some insights into the transition from $msg to $m in the OCO_MESSAGE_TEMPLATE_PLACEHOLDER configuration would be helpful.

Examples: Including real-world examples can be a game-changer, helping users visualize and understand the feature's full potential.
External Links: If there are related external resources or tutorials, those would be valuable additions, offering users a comprehensive learning experience.

Alternatives:

Reference to Standard Git Feature: I'm wondering if the OCO_MESSAGE_TEMPLATE_PLACEHOLDER or the template function might be rooted in a standard Git feature I'm unfamiliar with. If so, a nod to the official Git documentation or other trusted resources would be a wonderful touch, helping bridge any knowledge gaps.

Additional Context:
I believe these suggestions come from a place of wanting to see this already impressive tool become even more user-friendly. Thanks for considering my feedback, and keep up the great work!

Certainly! Here's a comment that addresses the GitHub issue based on the provided code, excluding point 4:

Thank you for your detailed feedback on the opencommit tool and its OCO_MESSAGE_TEMPLATE_PLACEHOLDER feature. I've taken a closer look at the codebase to understand its implementation and how it relates to your feedback:

OCO_MESSAGE_TEMPLATE_PLACEHOLDER Feature:

Your issue highlights the OCO_MESSAGE_TEMPLATE_PLACEHOLDER feature, which is designed to allow users to embed a custom message within the generated commit message using a template function.
In the codebase, this feature's implementation is evident in the line from config.ts:commitMessage = messageTemplate.replace(
   config?.OCO_MESSAGE_TEMPLATE_PLACEHOLDER,
   commitMessage
 );

This line is responsible for replacing the placeholder in the messageTemplate with the actual commitMessage.

Documentation Clarity:

You've rightly pointed out areas in the documentation that could benefit from added clarity, especially regarding the "template function" and the transition from $msg to $m.
While the code doesn't directly touch upon documentation, it does showcase the backend implementation of this feature. This can be a valuable reference when enhancing the documentation.

Commit Message Generation:

The function generateCommitMessageFromGitDiff in the codebase is designed to generate a commit message based on a git diff, and it potentially leverages the OCO_MESSAGE_TEMPLATE_PLACEHOLDER feature.
Your example oco '$msg #205’ seems to be a command that taps into this feature. The provided code likely represents the backend mechanics of such commands.

This ties back to your point about understanding the feature's full potential. By enhancing the documentation and providing clearer examples, users will likely feel more confident in using the generated messages for their commits.

In essence, the codebase offers a deep dive into the implementation details of the OCO_MESSAGE_TEMPLATE_PLACEHOLDER feature and the process of generating and committing with a message. Your feedback is invaluable, and using the code as a reference, we can certainly work towards addressing the concerns you've raised and improving the overall user experience.
Thanks again for your insights!

@EwiththeBowtie thank you for your thoughtful contribution! Hope we collaborate on other features soon.
the #242 PR was merged <3


Travis CI

Consider switching from travis to Bitrise.io. They support Swift 2 and are free. You'll be up and running in 20 minutes:)
p.s.
They also support building and testing pull requests, which is super handy for open source projects.

Thanks for the tip!
On Tue, Nov 10, 2015 at 10:58 AM, Stas Zhukovskiy<EMAIL_ADDRESS>wrote:

Consider switching from travis to Bitrise.io https://www.bitrise.io/.
They support Swift 2 and are free. You'll be up and running in 20 minutes:)
p.s.
They also support building and testing pull requests, which is super handy
for open source projects.
—
Reply to this email directly or view it on GitHub
https://github.com/DoubleSha/BitcoinSwift/issues/20.


Debug Error!    abort() has been called

So I built ultraEd in visual studio and got this error:

I got some warnings in visual studio though:

P.S. I can run it with the local windows debugger for some odd reason./
But I do want to be able to have the .exe to work because I also can't build rom's for some reason in there

Hi Sammyueru! Do you have the DirectX sdk installed? If not you can obtain from here https://www.microsoft.com/en-us/download/details.aspx?id=6812
I think I had that same problem a few days back when I refreshed my machine.


Add a check for min_gas_price in the health check process

Closes: #2776
Description

Adds a step to the health check process that verifies that the gas_price parameter in Hermes is >= the on-chain min_gas_price parameter.

PR author checklist:

[ ] Added changelog entry, using unclog.
[ ] Added tests: integration (for Hermes) or unit/mock tests (for modules).
[ ] Linked to GitHub issue.
[ ] Updated code comments and documentation (e.g., docs/).
[ ] Tagged one reviewer who will be the one responsible for shepherding this PR.

Reviewer checklist:

[ ] Reviewed Files changed in the GitHub PR explorer.
[ ] Manually tested (in case integration/unit/mock tests are absent).

One outstanding todo:

[ ] parsing of denoms should be able to handle the case of multiple min-gas-prices, eg: minimum-gas-price = 0.25token1;0.0001token2

@adizere Do these changes look good to you?


[Botskills] Improve validation warning

Purpose
What is the context of this pull request? Why is it being done?
The validation warning of the manifest schema didn't specify that the versions less than 2.1 are not supported, so we improve it.
Changes

The warning text was changed to be more precise.

Tests
Is this covered by existing tests or new ones? If no, why not?
Feature Plan
Are there any remaining steps or dependencies before this issue can be fully resolved? If so, describe and link to any relevant pull requests or issues.
Checklist
General

[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have added or updated the appropriate tests
[ ] I have updated related documentation

Bots

[ ] I have validated that new and updated responses use appropriate Speak and InputHint properties to ensure a high-quality speech-first experience
[ ] I have replicated language model changes across the English, French, Italian, German, Spanish, and Chinese .lu files and validated that deployment is successful

Deployment Scripts

[ ] I have replicated my changes in the Virtual Assistant Template and Sample projects
[ ] I have replicated my changes in the Skill Template and Sample projects

I'll be promoting this PR briefly.

Promoted to MS and already merged


Consistent use of K for number of spatial points

1D and 2D use K differently: 1D specifies K which creates K+1 spatial points but in 2D K is the number of points.

Closed by fdb7f37


Should we divide self.scale instead of multiplied self.scale for slot attention?

In line 54 of slot_attention.py, should we use
dots = torch.einsum('bsc,bnc-> bsn', q, k) / self.scale
instead of
dots = torch.einsum('bsc,bnc-> bsn', q, k) * self.scale
for temperature normalization?

At https://github.com/lucidrains/slot-attention/blob/master/slot_attention/slot_attention.py#L11, it is already -0.5.

Oh! Sorry for my silly mistake.


docs: Included description of the project in README

I have included a description of the Node Visualizer in the README file.

lg2m


Can add net framework 4.7 support for mapsui 3?

win10 default net framework is 4.7.

Hi, I'm using mapsui 2. I want update to mapsui 3, but it‘s not supported net472.
I try to compile it by myself.
I'd like to ask why not distinguish between platform publishing nugets?
like this:
Mapsui (for all)
├Mapsui.dll
├Mapsui.Geometries.dll
└Mapsui.Rendering.Skia.dll
Mapsui.Wpf  (depend on Mapsui)
├Mapsui.Render,Xaml.dll
└Mapsui.UI.Wpf.dll
Mapsui.Uwp  (depend on Mapsui)
└Mapsui.UI.Uwp.dll
Mapsui.iOS  (depend on Mapsui)
└Mapsui.UI.iOS.dll
Mapsui.Mono  (depend on Mapsui)
└Mapsui.UI.Android.dll

i have pull #1029 for update a old csproj file.
Perhaps can later support multiple .Net versions by modify
<TargetFramework>net48</TargetFramework>
to
<TargetFrameworks>net472;net48</TargetFrameworks>  in .csproj file

From what I could tell, some of the libs in the dependency tree are using incompatible frameworks. I migrated my fork to use the latest of everything about a week before I noticed it was also done in origin/master, and I can tell you - it was not possible to use any framework prior to 4.8 and make it all compile and be happy without a lot of juggling. It wasn't worth it for me as I just wanted to use the Xamarin Forms parts.

From what I could tell, some of the libs in the dependency tree are using incompatible frameworks. I migrated my fork to use the latest of everything about a week before I noticed it was also done in origin/master, and I can tell you - it was not possible to use any framework prior to 4.8 and make it all compile and be happy without a lot of juggling. It wasn't worth it for me as I just wanted to use the Xamarin Forms parts.

So there is no way to continue using mapsui 3 with net472.:pleading_face:

@memsom
I used in WPF.
I am tried to publish mapsui 3 supported by net462, and the effect was fine at my fork.
So i think the library file should keep the runtime version as low as possible.
Some projects (like Mapsui.Rendering.Skia) refer to third-party (net462) libraries, so the lowest version of the  Mapsui.Rendering.Skia was locked to net462.
In addition, I found that it might not be necessary to consolidate files from multiple platforms into a single nuget package,
so I tried to recompile the release as I thought. Of course, splitting nuget package should not be discussed in this issue.
nuget search "Net45.Mapsui"  (some mistake on publish, It's should be call Net462.Mapsui)

@IOL0ol1  well, my fork I wanted it to use the latest version of every dependency, so maybe that is more extreme. But it getting pulled to 4.8 was the simplest way to achieve that. The main version, I can't speak for the developers. I don't know why it was pushed to 4.8.

[Update] I have publish nuget package "Mapsui3".
If anyone needs it. Enable pre release included  when search nuget.
There is basically no modification of the code, just changes to the project file and how the package is built

This is not something I would like to invest in. Also, there is now a workaround with mapsui3.


ocamlPackages.sequence: 0.10 -> 1.1

Motivation for this change
Compatibility with OCaml 4.07.
Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
Built on platform(s)

[ ] NixOS
[x] macOS
[x] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[x] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[x] Fits CONTRIBUTING.md.

@GrahamcOfBorg build ocamlPackages.sequence

Success on x86_64-linux (full log)
Attempted: ocamlPackages.sequence
Partial log (click to expand)
post-installation fixup
moving /nix/store/vl75kdbp1x99k4jz4kn1ivfxdyi8caik-ocaml4.05.0-sequence-1.1/doc to /nix/store/vl75kdbp1x99k4jz4kn1ivfxdyi8caik-ocaml4.05.0-sequence-1.1/share/doc
shrinking RPATHs of ELF executables and libraries in /nix/store/vl75kdbp1x99k4jz4kn1ivfxdyi8caik-ocaml4.05.0-sequence-1.1
shrinking /nix/store/vl75kdbp1x99k4jz4kn1ivfxdyi8caik-ocaml4.05.0-sequence-1.1/lib/ocaml/4.05.0/site-lib/sequence/sequence.cmxs
shrinking /nix/store/vl75kdbp1x99k4jz4kn1ivfxdyi8caik-ocaml4.05.0-sequence-1.1/lib/ocaml/4.05.0/site-lib/sequence/bigarray/sequence_bigarray.cmxs
strip is /nix/store/1hi76hr87bd1y1q1qjk0lv8nmcjip1c8-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/vl75kdbp1x99k4jz4kn1ivfxdyi8caik-ocaml4.05.0-sequence-1.1/lib
patching script interpreter paths in /nix/store/vl75kdbp1x99k4jz4kn1ivfxdyi8caik-ocaml4.05.0-sequence-1.1
checking for references to /build in /nix/store/vl75kdbp1x99k4jz4kn1ivfxdyi8caik-ocaml4.05.0-sequence-1.1...
/nix/store/vl75kdbp1x99k4jz4kn1ivfxdyi8caik-ocaml4.05.0-sequence-1.1

Success on aarch64-linux (full log)
Attempted: ocamlPackages.sequence
Partial log (click to expand)
post-installation fixup
moving /nix/store/ba4kqp53kynfdvvlmgjisf2daad88mfw-ocaml4.06.1-sequence-1.1/doc to /nix/store/ba4kqp53kynfdvvlmgjisf2daad88mfw-ocaml4.06.1-sequence-1.1/share/doc
shrinking RPATHs of ELF executables and libraries in /nix/store/ba4kqp53kynfdvvlmgjisf2daad88mfw-ocaml4.06.1-sequence-1.1
shrinking /nix/store/ba4kqp53kynfdvvlmgjisf2daad88mfw-ocaml4.06.1-sequence-1.1/lib/ocaml/4.06.1/site-lib/sequence/sequence.cmxs
shrinking /nix/store/ba4kqp53kynfdvvlmgjisf2daad88mfw-ocaml4.06.1-sequence-1.1/lib/ocaml/4.06.1/site-lib/sequence/bigarray/sequence_bigarray.cmxs
strip is /nix/store/zrs21zqcchgyabjf4xfimncdq16njizc-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/ba4kqp53kynfdvvlmgjisf2daad88mfw-ocaml4.06.1-sequence-1.1/lib
patching script interpreter paths in /nix/store/ba4kqp53kynfdvvlmgjisf2daad88mfw-ocaml4.06.1-sequence-1.1
checking for references to /build in /nix/store/ba4kqp53kynfdvvlmgjisf2daad88mfw-ocaml4.06.1-sequence-1.1...
/nix/store/ba4kqp53kynfdvvlmgjisf2daad88mfw-ocaml4.06.1-sequence-1.1

Success on x86_64-darwin (full log)
Attempted: ocamlPackages.sequence
Partial log (click to expand)
make[1]: Leaving directory '/private/tmp/nix-build-ocaml4.05.0-sequence-1.1.drv-0/source/_build/default/qtest'
running tests
installing
Processing file sequence.install as sequence.
post-installation fixup
moving /nix/store/zg6m3d8xdr2dvqfvv99kdv847sdrkn5n-ocaml4.05.0-sequence-1.1/doc to /nix/store/zg6m3d8xdr2dvqfvv99kdv847sdrkn5n-ocaml4.05.0-sequence-1.1/share/doc
strip is /nix/store/qfxcr8c4fg7lkybrny9n2sb77bmippdx-cctools-binutils-darwin/bin/strip
stripping (with command strip and flags -S) in /nix/store/zg6m3d8xdr2dvqfvv99kdv847sdrkn5n-ocaml4.05.0-sequence-1.1/lib
patching script interpreter paths in /nix/store/zg6m3d8xdr2dvqfvv99kdv847sdrkn5n-ocaml4.05.0-sequence-1.1
/nix/store/zg6m3d8xdr2dvqfvv99kdv847sdrkn5n-ocaml4.05.0-sequence-1.1


Add custom implict conversions to InputArgument/OutputArgument

And removed Vehicle.MaxSpeed, to avoid compile error. And _GET_VEHICLE_MAX_SPEED doesn't return the vehicle's current max physical speed.

What does _GET_VEHICLE_MAX_SPEED return? Because to solve the compile error we could just add the following to the vehicle property (which was added in a385df815dd83753b1b225c4a4ead799a96de768):
void set(float value) { Entity::MaxSpeed = value; }

_GET_VEHICLE_MAX_SPEED returns the vehicle's normal max speed, but its speed isn't limited to the value this function returns.

Alright.


Use assign method from lodash to make IE work again

The latest ember-cli-mirage stopped working on IE11. After some research I found out that this happens most likely because of the Object.assign method (hopefully this is the only reason). Anyways I suggest reverting the changes from the commit 3867bcdb and use the assign method from lodash.

You're right, and I don't think this is the first time this has happened. We need to come up with a failing test of some sort... even a unit test that says "This project doesn't use Object.assign". Or we need to configure our polyfill rules somehow.

I wonder if this is better solved by updating our rollup build to target ie 11

I should give it a try
вт, 30 июл. 2019 г., 16:02 Sam Selikoff<EMAIL_ADDRESS>
I wonder if this is better solved by updating our rollup build
https://github.com/miragejs/server/blob/master/rollup.config.js#L21 to
target ie 11
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/miragejs/server/pull/36?email_source=notifications&email_token=ACLIBRLOMAX5HSEZRLKVXO3QCA3V5A5CNFSM4IHO53Q2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD3D4MWA#issuecomment-516408920,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACLIBRPTBGMCNSJMDABXMLLQCA3V5ANCNFSM4IHO53QQ
.

So I guess the #54 fixes this one. I'll close it then.

Not 100%, would like to verify


[application] Deploy the FIO Test Pod failed

Describe the bug
https://mayastor.gitbook.io/introduction/quickstart/deploy-a-test-application
When I deploy the fio pod as per the documentation, the fio pod cannot be started.
To Reproduce
kubectl apply -f https://raw.githubusercontent.com/openebs/Mayastor/v1.0.3/deploy/fio.yaml

Expected behavior
Start the fio pod for performance testing.
Screenshots
it shows in Events
  Normal Scheduled 5m25s default-scheduler Successfully assigned default/fio to spdk-2
  Normal SuccessfulAttachVolume 5m24s attachdetach-controller AttachVolume.Attach succeeded for volume "pvc-513d318a-c9f0-4341-8bc1-d12d5ed05da3"
  Warning FailedMount 67s (x10 over 5m17s) kubelet MountVolume.MountDevice failed for volume "pvc-513d318a-c9f0-4341-8bc1-d12d5ed05da3" : rpc error: code = Internal desc = Failed to stage volume 513d318a-c9f0-4341-8bc1-d12d5ed05da3 : attach failed: connect failed: NVMe connect failed: /dev/nvme-fabrics, No such file or directory (os error 2)
  Warning FailedMount 64s (x2 over 3m22s) kubelet Unable to attach or mount volumes: unmounted volumes=[ms-volume], unattached volumes=[ms-volume kube-api-access-wpt4g]: timed out waiting for the condition

** OS info (please complete the following information):**

Distro:

root@spdk-1:~# cat /etc/os-release
PRETTY_NAME="Debian GNU/Linux 11 (bullseye)"
NAME="Debian GNU/Linux"
VERSION_ID="11"
VERSION="11 (bullseye)"
VERSION_CODENAME=bullseye
ID=debian
HOME_URL="https://www.debian.org/"
SUPPORT_URL="https://www.debian.org/support"
BUG_REPORT_URL="https://bugs.debian.org/"

Kernel version

Linux spdk-1 5.10.0-9-amd64 #1 SMP Debian 5.10.70-1 (2021-09-30) x86_64 GNU/Linux

MayaStor revision or container image

v1.0.3

Additional context
msp sc pvc all seem to be fine.
root@spdk-1:~# kubectl -n mayastor get msp
NAME             NODE     STATUS   CAPACITY        USED           AVAILABLE
pool-on-node-1   spdk-1   Online<PHONE_NUMBER>576<PHONE_NUMBER>00<PHONE_NUMBER>176
pool-on-node-2   spdk-2   Online<PHONE_NUMBER>576<PHONE_NUMBER>00<PHONE_NUMBER>176
pool-on-node-3   spdk-3   Online<PHONE_NUMBER>576<PHONE_NUMBER>00<PHONE_NUMBER>176
root@spdk-1:~# kubectl -n mayastor get sc
NAME         PROVISIONER               RECLAIMPOLICY   VOLUMEBINDINGMODE      ALLOWVOLUMEEXPANSION   AGE
mayastor-3   io.openebs.csi-mayastor   Delete          WaitForFirstConsumer   false                  3h6m
root@spdk-1:~# kubectl  get pvc -A
NAMESPACE   NAME                   STATUS   VOLUME                                     CAPACITY   ACCESS MODES   STORAGECLASS   AGE
default     ms-volume-claim        Bound    pvc-513d318a-c9f0-4341-8bc1-d12d5ed05da3   100Gi      RWO            mayastor-3     152m
mayastor    data-mayastor-etcd-0   Bound    etcd-volume-0                              2Gi        RWO            manual         20h
mayastor    data-mayastor-etcd-1   Bound    etcd-volume-1                              2Gi        RWO            manual         20h
mayastor    data-mayastor-etcd-2   Bound    etcd-volume-2                              2Gi        RWO            manual         20h

Thanks @tiagolobocastro , the fio pod is up and running.
Is mayastor a storage dedicated to k8s?
Is there now or in the future support for exporting block devices for use by other clients (eg, for kvm or bare metal, like iscsi)?

The design and implementation of Mayastor's control and data planes has always been made on the premise that it should support its use with k8s but not be dependent upon it.  Use-cases outside k8s may well be considered for active development "in the future" but currently, dynamic provisioning of PVs to k8s is the one which is receiving the attention of the maintainers.

thanks for the reply!

@tiagolobocastro hi, I'm new on Linux, is this command to load nvme_tcp
sudo modprobe nvme-tcp

I tried, it works, fio pod is up and running


docs: add the incremental learning proposal

Add the incremental learning proposal was missed before by mistake.

/hold

/hold cancel

/lgtm

/approve


DocsArchive-<IP_ADDRESS>Auto archive content

Please don't merge this PR until target archive repo PR https://github.com/OPS-E2E-PPE/docs-yml-archive-non-versioning-archive/pull/88 is merged into live branch.
Auto archive content to https://github.com/VSC-Service-Account/docs-yml-archive-non-versioning-archive.git

Docs Build status updates of commit d2bd952:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

.openpublishing.redirection.json
:white_check_mark:Succeeded

docs/TOC.yml
:white_check_mark:Succeeded
View

docs/to-be-archive/level1/article3-1-1.md
:white_check_mark:Succeeded
View

docs/to-be-archive/level1/article3-1-2.md
:white_check_mark:Succeeded
View

docs/to-be-archive/level1/article3-1-3.yml
:white_check_mark:Succeeded
View

docs/to-be-archive/level2/article3-2-1.md
:white_check_mark:Succeeded
View

docs/to-be-archive/level2/article3-2-2.md
:white_check_mark:Succeeded
View

docs/to-be-archive/level2/article3-2-3.yml
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit d2bd952:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

.openpublishing.redirection.json
:white_check_mark:Succeeded

docs/TOC.yml
:white_check_mark:Succeeded
View

docs/to-be-archive/level1/article3-1-1.md
:white_check_mark:Succeeded
View

docs/to-be-archive/level1/article3-1-2.md
:white_check_mark:Succeeded
View

docs/to-be-archive/level1/article3-1-3.yml
:white_check_mark:Succeeded
View

docs/to-be-archive/level2/article3-2-1.md
:white_check_mark:Succeeded
View

docs/to-be-archive/level2/article3-2-2.md
:white_check_mark:Succeeded
View

docs/to-be-archive/level2/article3-2-3.yml
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel


How about your work on MABP estimation?

I've noticed "process_MABP.py" in your project to calculate mean ABP value during a cycle, which is not mentioned in your paper. Can you describe your work related to MABP? Thank you for your attention:)

Thank you for your interest in our work. The file process_MABP.py aims to preprocess the ABP signal to create the ground-truth output for the PPG2IABP model [12], which is the average ABP pulse (MABP) with some semantic segmentation (systolic phase, Systolic peak to Dicrotic Notch, Dicrotic Notch to the end). If I don't remember wrongly, the original preprocessing code of Aguirre et al.** was in Matlab code. Thus, we decided to reimplement it in Python to preprocess the different datasets in our benchmark. For more information about the procedure, I refer you to Aguirre's original paper [12] and code**.
Our MABP procedure follows the following steps:

Identification of each heart cycles in the ABP signal.
Fix the cycle size (limiting and padding)
Exclude cycles out of mean+-(125std).
Compute average cycle.
Extract systolic peak and Dicrotic Notch.

[12] Aguirre, N., Grall-Maës, E., Cymberknop, L. J. & Armentano, R. L. Blood pressure morphology assessment from photoplethysmogram and demographic information using deep learning with attention mechanism. Sensors 21, 2167 (2021).
** https://github.com/AguirreNicolas/PPG2IABP/tree/main


integration: fix race in WatchFromCurrentRevision

Since watching from current revision, keys should be put after the
watcher is registered or the test may time out. Shows up in CI.

/cc @gyuho

LGTM. Thanks for fixing!


[MKLDNN] Fix _copyto

Description
@pengzhao-intel @TaoLv @ZhennanQin @rongzha1
This PR is to address the segmentation fault when calibrating FP32 models in entropy mode (calling _copyto op).

remove fallback feature for non-mkldnn ops (just like previous implementation)
add unittest for quantization in entropy mode

Checklist
Essentials
Please feel free to remove inapplicable items for your PR.

[ ] 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 https://mxnet-ci-doc.s3-accelerate.dualstack.amazonaws.com/PR-$PR_ID/$BUILD_ID/index.html
[ ] To the best of my knowledge, examples are either not affected by this change, or have been fixed to be compatible with this change

Changes

[ ] Feature1, tests, (and when applicable, API doc)
[ ] Feature2, tests, (and when applicable, API doc)

Comments

If this change is a backward incompatible change, why must this change be made.
Interesting edge cases to note here

@ZhennanQin please help take a review.

cc @ciyongch


Refine the README.md

The README.md is staled, we should refine it and keep it up to date.

@lonng could you list some specific issues please?

This issue is staled


Update Aff dependency

Yeah, unfortuately - just noticed I didn't commit src though, which is why the build is failing. I'll fix that now!

👍 LGTM

Now I need to update the test :smile:
I'll merge/release once I get travis to pass... you've seen the actual change at least!


⚠ Samsung has degraded performance

In 2b4a497, Samsung (https://samsung.com) experienced degraded performance:

HTTP code: 200
Response time: 2305 ms

Resolved: Samsung performance has improved in f547554.


Design docs

This PR gathers design docs in a central place, allowing for easier discovery and refactoring into a more cohesive structure down the line.

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

Project coverage is 35.28%. Comparing base (46ec9c2) to head (0923d44).
Report is 71 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #155      +/-   ##
==========================================
- Coverage   35.80%   35.28%   -0.53%
==========================================
  Files          16       33      +17
  Lines        1363     2874    +1511
==========================================
+ Hits          488     1014     +526
- Misses        801     1750     +949
- Partials       74      110      +36

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


feat: another attempt at cjson.as_array metatable

Hey there!
I would really like to see this being pushed forward, so here is my attempt at convincing of the use of such a patch :) Criticism welcome of course.
First, I would like to point out that the lack of empty table distinction from mpx/lua-cjson has lead to several (if not many) patches trying to solve this. And that I am glad to see this fork already includes the encode_empty_table_as_object, but I would like to emphasize on the fact that this feature is not enough even in fairly common use cases.
As an example, let's consider someone using the log_by_lua_* phase of ngx_lua (maybe along with lua-resty-logger-socket) to serialize the request/response data and send it somewhere to be stored and analyzed later. Such data could have empty objects representing either arrays or objects in the same Lua table (request headers vs form parameters). This is a simple use case where a higher level of granularity is necessary.
I had to deal with this a few month ago, and the aggregating tool enforced some schema validation, which made it impossible to work around without implementing some very ugly hacks, for which I still do not sleep well at night :)

I read the discussion at #1, and while I too believe a lightuserdata would be more efficient and consistent with cjson.null, I also think it would offload the actual work to the user.
While the metatable approach is fairly straightforward:
-- arr and obj might be empty, but never nil
local function serialize(arr, obj)
  setmetatable(arr, cjson.as_array)

  local data = {
    foo = arr,
    bar = obj
  }

  return cjson.encode(data)
end

The lightuserdata is less:
local function serialize(arr, obj)
  if #arr < 1 then
    arr = cjson.empty_array
  end

  local data = {
    foo = arr,
    bar = obj
  }

  return cjson.encode(data)
end

Note: if you see a better way of dealing with the userdata approach for users, I would be glad to hear about it and update the patch eventually!

Hence, this patch proposes a slightly improved version of #1, taking the given suggestions into account (since the patch was not updated since then):

more specific name for the metatable key in the Lua registry.
tests cases moved to t/agentzh.t, where cases for
'encode_empty_table_as_object' are already written. It seems like a
better place for tests specific to the OpenResty fork's additions.
a more complex test case and slightly more concise changes.

Given the number of times such a feature was requested, I believe it would be really great if it could finally be included, if not in mpx/lua-cjson, at least in OpenResty :)

I have updated the patch taking your comment in consideration, thanks for clarifying! I also attached the lightuserdata cjson.empty_array to cjson, which allows for an alternative to the metatable approach, in case one finds it more convenient in some cases.
Let me know! :)

@thibaultCha One last thing: will you please drop a quick note to README.md (I'm aware that this file does not even exist atm)? This way people can know how to use things without checking out source or PRs. Thanks for your time!

Absolutely, I actually intended to ask you if we wanted to document this and where once the patch confirmed!

I just added a README following more or less the OpenResty layout, let me know what you think of it.

Glad you like it! I just added a test case to ensure non-empty Lua tables with the empty_array_mt metatable are not encoded as empty arrays.

Hey @agentzh, did you get any chance to give this a try? I just feel like a release is coming and I think it'd be great to include those new features! I could be wrong though :)

@thibaultCha Been busy preparing tomorrow's openresty meetup. Sorry for the delay on my side. Will look into this as soon as I can manage.

Yeah I bet. Excited! Ok :)

@thibaultCha Very Nice:)

@thibaultCha Merged with a minor file name extension change. Thanks!

Great day! :grin: Thank you!


Making a "fake" package so that I can edit my swift code in a usable editor

I'm trying to make a dummy Swift package so that I can edit my code in VS Code or vim with coc/sourcekit_lsp etc. XCode is bad enough at the best of times, and this bug makes it barely usable. By creating a Package.swift and getting a successful build by tricking the swift compiler with some flags I should be able to get live error reporting and completion etc in VS Code. I had this working once before in an iOS-only app, but I can't get it to work with KMM.
If, in my Package.swift, I only use
  dependencies: [
    .package(path: "../GCshared/swiftpackage"),
    //...
  ],
  targets: [
    .target(
      name: packageName,
      dependencies: [
        .product(name: "GCshared", package: "swiftpackage"),
        //...
      ],
      //...
    )
  ]

I get
... error: no such module 'GCshared'
import GCshared
       ^

all over the place. I tried adding:
    .binaryTarget(
      name: "GCshared",
      path: "../GCshared/swiftpackage/GCshared.xcframework"
    )

but then I get this: error: multiple targets named 'GCshared' in: 'gcios', 'swiftpackage'; consider using the moduleAliases parameter in manifest to provide unique names.

Honestly I'm not an expert of how swift package works. But, did you try making your own Package.swift instead of just running ./gradlew createSwiftPackage?


Provide a method to print build configuration

Currently there is no way to retrieve build-time configuration after installation.
It is better to provide an interface like numpy.show_config().

It is also preferable to check version consistency at run-time.
For example, CUDA version used at build time is different from one available at runtime, uses may see strange error.

Implemented in https://github.com/cupy/cupy/pull/1067


Octet string for the CN field

I want to use hex bytes as Common name in x509 certificate.
In my config, I'm specifying this:
HEX_NAME        = AA01020304
...
commonName_default  = ASN1:SEQUENCE:hex_name

And then:
[hex_name]
hash_name = FORMAT:HEX,OCTETSTRING:$HEX_NAME

When generating certificate request, it prints an error:
6870300:error:0D07A097:asn1 encoding routines:ASN1_mbstring_ncopy:string too long:a_mbstr.c:158:maxsize=2

I can't recreate this error. But in any case this doesn't look like valid syntax to me. AFAIK you can only use the "ASN1:" syntax for defining custom extensions - not arbitrary other fields.
What version of OpenSSL were you using and can you provide exact steps to produce this error?

Just try to create certificate with the commonName field of the OCTETSTRING type.
I can't do that with any version that are available now.

That's not legal and would be hard to support.  The commonName is defined as a CHOICE with only a few particular options (printableString, teletextString, etc.)
I think this issue should be closed.

That's not legal and would be hard to support.  The commonName is defined as a CHOICE with only a few particular options (printableString, teletextString, etc.)  (See, for example, https://stackoverflow.com/questions/5136198/what-strings-are-allowed-in-the-common-name-attribute-in-an-x-509-certificate)
I think this issue should be closed.

Just try to create certificate with the commonName field of the OCTETSTRING type.

I tried to use the same config file that you provided in the example. But that didn't produce any error. Instead the commonName was set to the string "ASN1:SEQUENCE:hex_name", which is what I would have expected to happen - because that syntax isn't supported for setting a commonName.

I can't do that with any version that are available now.

No, it's not supported (by us or the standard I think).

But it is possible by ASN1.
And I have such certificate.
чт, 26 апр. 2018 г., 18:59 mattcaswell<EMAIL_ADDRESS>
Just try to create certificate with the commonName field of the
OCTETSTRING type.
I tried to use the same config file that you provided in the example. But
that didn't produce any error. Instead the commonName was set to the string
"ASN1:SEQUENCE:hex_name", which is what I would have expected to happen -
because that syntax isn't supported for setting a commonName.
I can't do that with any version that are available now.
No, it's not supported (by us or the standard I think).
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/openssl/openssl/issues/5368#issuecomment-384695294,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AG2zPZn8jJSFhPiag3crDErfCzNimg4yks5tse76gaJpZM4SFfYN
.

I am sure you have such a certificate.  It is not valid according to the X.509 specifications.   Did you see my note?

But it is possible by ASN1.
And I have such certificate.

Can you share it? Do you know how it was generated?

No, I can't share it, sorry. And I don't know how it was generated, but I'm
almost sure, that it was generated with the Java BouncyCastle lib.
2018-04-27 11:26 GMT+03:00 mattcaswell<EMAIL_ADDRESS>
But it is possible by ASN1.
And I have such certificate.
Can you share it? Do you know how it was generated?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/openssl/openssl/issues/5368#issuecomment-384901944,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AG2zPYUGqjJfjyKpPECf7hj3imSv8wyWks5tstYfgaJpZM4SFfYN
.

--
Dr. MefistO, Inc.


Add setup.py

Adds a setup.py file.
I didn't list all the scripts, but the current file should give you a good head start to fulfill #8.
Fill free to make changes to the branch before merging.
Once merged, installing the scripts will be as simple as running this command:
pip install .

Thanks very much! It is helpful to have an example like this :-)


parser: add DROP ROLE support

What problem does this PR solve?
add DROP ROLE function for parser and executor.
What is changed and how it works?
Role is same as user, is store in mysql.user table. We do same action as DROP USER when we need to drop a role. Also, as we has added some system table for RBAC, like mysql.role_edges and
mysql.default_role. We have to delete information from these tables when execute DROP ROLE
tidb pr: https://github.com/pingcap/tidb/pull/9616
Check List
Tests

Unit test

Code changes

Has exported variable/fields change

Side effects

Increased code complexity

LGTM


[BUG]  Issues showing documentation in cmp plugin

Field
Description

Plugin
cmp and/or lsp

Nixpkgs
unstable

Home Manager
<VERSION>

[x ] I have read the FAQ and my bug is not listed there.

Description
Hello, I'm quite new to NixOS and Neovim, and I'm not sure if this is a bug but I'm encountering problems with cmp and/or lsp.
Mainly, the cmp list does not show any documentation. Copied below are my settings for cmp/lsp related plugins.
Is there anything else I should do to make this work? Any advice would be greatly appreciated. Thanks!

Minimal, Reproducible Example (MRE)

programs.nixvim.plugins = {
      lsp = {
        enable = true;
        servers = {
          bashls.enable = true; #bash
          ccls.enable = true; #c/c++
          dockerls.enable = true; #Docker
          gleam.enable = true; #gleam
          marksman.enable = true; #markdown
          nixd.enable = true; #nix
          ruff-lsp.enable = true; #python
          rust-analyzer = {
            enable = true;
            installCargo = true;
            installRustc = true;
          };
          yamlls.enable = true; #YAML
        };
      };
      cmp = {
        enable = true;
        autoEnableSources = true;
        settings = {
          sources = [
            {name = "nvim_lsp";}
            {name = "buffer";}
            {name = "path";}
            {name = "cmdline";}
            {name = "cmp";}
            {name = "luasnip";}
          ];

          snippet.expand = ''
            function(args)
              require('luasnip').lsp_expand(args.body)
            end
          '';

          mapping = {
            "<C-b>" = "cmp.mapping.scroll_docs(-4)";
            "<C-f>" = "cmp.mapping.scroll_docs(4)";
            "<C-Space>" = "cmp.mapping.complete()";
            "<Alt-Tab>" = "cmp.mapping.abort()";
            "<CR>" = "cmp.mapping.confirm({select = true})";
            "<Alt-`>" = "cmp.mapping.confirm({select = false})";
            "<S-Tab>" = "cmp.mapping(cmp.mapping.select_prev_item(), {'i', 's'})";
            "<Tab>" = "cmp.mapping(cmp.mapping.select_next_item(), {'i', 's'})";
          };
          view.docs.auto_open = true;

          window = {
            documentation.winhighlight = "Normal:NormalNC,FloatBorder:NormalNC,CursorLine:PmenuSel,Search:None";
            documentation.max_height = "math.floor(40 * (40 / vim.o.lines))";
            documentation.max_width = "math.floor((40 * 2) * (vim.o.columns / (40 * 2 * 16 / 9)))";
            completion.winhighlight = "Normal:NormalNC,FloatBorder:NormalNC,CursorLine:PmenuSel,Search:None";
          };
        };
      };

      cmp-nvim-lsp.enable = true;
      cmp-buffer.enable = true;
      cmp-path.enable = true;
      cmp-cmdline.enable= true;
      cmp_luasnip.enable = true;
      luasnip.enable = true;
      lspkind.enable = true;
      lspkind.cmp.enable = true; #icons

}

First and foremost, the following lines in your config are not necessary:
      cmp-nvim-lsp.enable = true;
      cmp-buffer.enable = true;
      cmp-path.enable = true;
      cmp-cmdline.enable= true;
      cmp_luasnip.enable = true;

Indeed, the plugins of the sources you enable in plugins.cmp.settings.sources are automatically installed by nixvim.
Now, what do you mean by "cmp does not show documentation" ?
You mean that the completion list you get while writting doesn't contain elements from the LSP ? (i.e. it does not autocomplete function/variable names).
If so, have you checked that your language server is attached to the buffer (:LspInfo).
Does this happens for all languages ?

I apologize for not being specific, I'll try my best specifying exactly what the issue is.
As for the plugins that I explicitly enabled, I did it as an effort to see if that was the problem. I did read the NixVim doc, but I wasn't sure where the problem lied so I tried to do everything I can think of, which included explicitly telling NixVim to enable those plugins.
By documentation I meant those little docs that normally appear right next to the completion list.  From the videos I've seen on neovim, I assumed if I install LSP and cmp the completion list and the documents will show up simultaneously right next to each other.
I haven't tried out all languages, but I did try out nix and python. I did check if the LSP is being attached, if I'm not mistaken it is, here's the text below (I was editing my nixvim.nix):
Language Client Log: /home/..../nvim/lsp.log
Detected language: nix
Client: nixd (id:1, bufnr: [1])
  filetypes: nix
  autostart: true
  root directory: /../.flake_configs (I store my flake.nix, home.nix etc here)
  cmd: /nix/store/..../bin/nixd

the LspInfo also gave me list of all configured servers list, and I didn't see any problem there.
Maybe there is a setting I forgot to adjust, or I need to make a custom lua function for this to happen, but like I said I'm new to neovim so I'm not sure what to do.
Again, sorry for being too general. If you need any more information please let me know.
Thanks!

Oh I see. So this has nothing to do with completion. It is a feature called hover documentation.
You can show documentation for the item under your cursors by running :lua vim.lsp.buf.hover(). This will open a pop-up window showing the docs.
Usually people create a keymap for this (often K, as vscode does I guess). See here fr an example.
If you want it to appear as you type, you will most likely need an extra plugin. I am not aware of such a plugin, but feel free to explore !

Apparently, it is possible. Not clear to me how.
Have a look at this as a starting point: https://github.com/neovim/neovim/issues/1934#issuecomment-399270196

Thank you so much for your help! Really appreciate it.
I'll close the issue, though I guess it wasn't even an issue of nixvim in the first place haha, just need a few tweaks here and there.
Again thank you for helping!


Fox Racing

Guide
https://iptv-org.github.io/epg/guides/en/tvpassport.com.xml
Description
Please check Fox Racing.........Guide seems to be down.
Thanks in advance

https://github.com/iptv-org/epg/issues/2017


Can't connect to the database

Workflow is failing to start because it can't connect to the database:
kubectl logs -p --namespace=deis deis-workflow-fcs7h
system information:
Django Version: 1.9.3
Python 3.5.1
Django checks:
System check identified no issues (2 silenced).
Health Checks:
Checking if database is alive
There was a problem connecting to the database

@helgi investigated a bit further than I did and found this further information:
            return self.sign(operation_name, request)
          File "/usr/local/lib/python2.7/dist-packages/botocore/signers.py", line 123, in sign
            signature_version)
          File "/usr/local/lib/python2.7/dist-packages/botocore/signers.py", line 163, in get_auth_instance

That's not a workflow problem, that log is from the database

Ok - so the real problem is that workflow can't connect to the database because the database is having problems with botocore oriented logic?

Yeah

Thanks @helgi. Will be addressed by deis/postgres#47


How transaction and rollback works in kundera with cassandra

Hi Cassandra expert
We have chosen kundera as client to access cassandra.
I have a usecase to ensure transactionality in cassandra and also understand how cassandra deletes an inserted record.
We want to understand a bit more on how kundera implements rollback.
Can you please explain.
Thanks
Prad

@almightypradeep
Kundera follows JPA specifications for implementing rollback (transactions). Please refer this wiki page.
Please refer this  link to find out more about transactions at Cassandra level.
If you face any issue while implementing transactions in your use case you can get back to us.
-Karthik

Thanks Karthik.
I want to understand how rollback is implemented using kundera, is it at the client side or at the cassandra.
A bit more on how records are inserted and deleted due to transaction breaks.
Thanks for yr reply

@almightypradeep
Rollback and commit handled at Kundera API level as per JTA specification(if running with CMP ). AFAIK Cassandra supports lightweight transaction (CAS)  only, not sure still experimental or production ready now. You should be able allowed to access CAS support via Kundera's native CQL3 support.
HTH,
-Vivek

Thanks Vivek. This helps my question.


Add policy version

Coverage increased (+0.01%) to 93.723% when pulling 992b4750931dcb3956196d2b71fbc9b35ddf82c8 on heddle317:add_policy_version into af7a5859fe7a4e12b6ec7c68c7de4c2e65fab857 on spulec:master.

Great work, @heddle317!


use minikube start --mount to mount filesystem

Issue
I can't mount my host's directory to minikube's /mnt/src directory.
Cause
Our current minikube mount approach requires the use of the 9p filesystem but  debian cloud as well as cent os and red hat all have issues supporting 9p.
Solution
Place minikube start --mount --mount-string="$PWD:/mnt/src" inside warnet's justfile start command.
Note: This fix requires that we run minikube delete on each invocation of just start. This is because docker has an issue with re-mounting filesystems, and the minikube delete approach to sidestepping this limitation comes recommended.
Rationale

The current justfile already relies on minikube.
It simplifies our mounting logic (no more pid management).
It passes CI.

Sorry I re-triggered CI to see if it will pass. I think it will if you rebase on main now (🤞🏼 )


[NNBD] Analyzer and CFE behave differently for implicit return

The following code produces an error in VM and no issues in analyzer (both with --enable-experiment=non-nullable)
main() {
  (x) {
    if (x)
      return 1;
  } (true);
}

VM output is
D:\co19\Language\Statements\Return>dart --enable-experiment=non-nullable,nonfunction-type-aliases many_return_statements_t04.dart
many_return_statements_t04.dart:21:3: Error: A non-null value must be returned since the return type 'int' doesn't allow null.
(x) {
^

Dart VM version: 2.9.0-20.0.dev (dev) (Wed Jul 1 11:29:16 2020 +0200) on "windows_x64"
@eernstg please clarify what is an expected behavior here

See also https://github.com/dart-lang/sdk/issues/39476

Blocked on https://github.com/dart-lang/language/issues/1063: the current specification makes the function literal an error,  and I'm proposing that we keep it like that even though it means that the analyzer will reject more programs.

@eernstg did we determine what the right behavoir is?

Yes, when the end of a function with inferred return type can be reached (and null is implicitly returned), the inferred return type is made nullable and there is no error.
Implementation issue for CFE, https://github.com/dart-lang/sdk/issues/42743, is closed. The analyzer already did this.


a question

hello, when you trained your AUXFORMER model with two modalities and test your model with a single modality(another modality is zero-padded),  which branch results did you choose when testing?
the result from the main branch?
or the auxiliary branch corresponding to the input modality in the test period?
thankyou!

for example, when you input video to your model with audio zero-padded, did you choose the result of the auxiliary video branch to compute accuracy?
or when you input video to your model with audio zero-padded, did you choose the result of the fusion branch to compute accuracy?

All branches contribute to the prediction at all times (full audiovisual, audio only with video set to zeroes, and video only with audios set to zeroes).
Check the file test.py lines 112 and 113.
112      preds_va, preds_a, preds_v = modelWrapper.feed_forward(xa, xv, attention_mask=mask)
113      pred = (preds_va + preds_a + preds_v) / 3


Support max length for array and map

Feature Request 🛍
Extend the metamodel to support validation facets for the length of an array and the number of keys in a map.
Use Case
Allows the model to define the maximum number of elements in array or map.
Possible Solution

Update metamodel
Update CTO grammar and parser
Update AST printer
Update validation

Context

Detailed Description

Working on this. I am yet to implement the validation.


Added parent_id to Device class

This adds parent_id to the pytos.securetrack.xml_objects.rest.device.Device class

Please change the repo to development

Done, I believe


Update build and deploy pipeline

What does this PR do?:
Summarize the changes. Are any stacks or samples added or updated?
Updates provided to build scripts and community devfile registry OpenShift template file to support new registry viewer setup. No stacks or samples updated.
Which issue(s) this PR fixes:
Link to github issue(s)
fixes devfile/api#747
PR acceptance criteria:

[ ] Contributing guide
Have you read the devfile registry contributing guide and followed its instructions?
[ ] Test automation
Does this repository's tests pass with your changes?
[ ] Documentation
Does any documentation need to be updated with your changes?
[ ] Check Tools Provider
Have you tested the changes with existing tools, i.e. Odo, Che, Console? (See devfile registry contributing guide on how to test changes)

How to test changes / Special notes to the reviewer:

blocked by devfile/registry-support#153


followed instructions, but not luck iOS iPhone 6s

ld: warning: ignoring file /usr/local/lib/libzmq.dylib, file was built for x86_64 which is not the architecture being linked (arm64): /usr/local/lib/libzmq.dylib

Yeah, it doesn't work on iOS yet. libzmq has to be compiled for iOS. There were some attempts before. But I guess they're outdated. For now SwiftZMQ only supports OS X. But maybe later it will support iOS. I'll also port nanomsg, which is a new approach from the same author. Maybe its easier to compile nanomsg for iOS.


Does downloadApolloSchema support android product flavor?

Question.
In my project, I have set up both buildType and product flavors e.g.
buildTypes {
    getByName("release") {
      isMinifyEnabled = true
      proguardFiles(getDefaultProguardFile("proguard-android-optimize.txt"), "proguard-rules.pro")
      isDebuggable = false
    }
    getByName("debug") {
      applicationIdSuffix(".debug")
      versionNameSuffix("-debug")
      isDebuggable = true
    }
  }

  flavorDimensions("mode")
  productFlavors {
    create("local") {
      dimension = "mode"
      applicationIdSuffix(".local")
      versionNameSuffix("-local")
      buildConfigField("String", "GRAPHQL_API", "\"https://local.abc.io/graphql\"")
    }
    create("staging") {
      dimension = "mode"
      applicationIdSuffix(".staging")
      versionNameSuffix("-staging")
      buildConfigField("String", "GRAPHQL_API", "\"https://staging.abc.io/graphql\"")
    }
  }

When I ran
./gradlew downloadApolloSchema --endpoint="..." --schema="..."

I got
> Task :app:downloadApolloSchema FAILED

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':app:downloadApolloSchema'.
> Cannot find compilation unit, check variant and service.
  Possible services:
  service
  Possible variants:
  localDebug
  localDebugAndroidTest
  localDebugUnitTest
  localRelease
  localReleaseUnitTest

I can't find a way to resolve this error. If I remove the product flavor {}, I am able to download the schema.json again. I'm wondering if there are any workarounds for this issue.

Sorry about that, this was an oversight. --schema should always allow to override the compilation unit automatic detection.
A fix is in #2712.
In the meantime, you should be able to workaround this by passing the variant explicitely:
./gradlew downloadApolloSchema --endpoint="..." --schema="..." --variant="localRelease"

Sorry about that, this was an oversight. --schema should always allow to override the compilation unit automatic detection.
A fix is in #2712.
In the meantime, you should be able to workaround this by passing the variant explicitely:
./gradlew downloadApolloSchema --endpoint="..." --schema="..." --variant="localRelease"

great. thanks for fixing this issue @martinbonnin


print out hypershfit cluster credential

It print credentials in the output, which is  useful for debugging

/lgtm


Consider moving website to a more traditional CMS

While Github is great, a more traditional CMS like WordPress, SquareSpace, Weebly, Magento, etc. can give us more flexibility when creating landing pages, better control of forms, and ready-to-go integrations and formatting to make blogs and other content types look professional and sleek.

I totally agree. While SquareSpace, Weebly, Magento aren't the best solutions, WordPress is due to its large and amazing community. And it's a solid platform that most people are familiar with.
WordPress with Divi is the perfect solution. Very lightweight with built-in marketing tools and SEO options. It allows anyone to build unique and amazing looking landing pages in just a few minutes.
Divi also just included an amazing React Divi API. Check it out.
https://youtu.be/vtkGEb6BnA8
WordPress is 1/3 of the worlds internet and Divi is WordPress's number page builder... because it's the perfect solution for creating working solutions quickly and easily saving so much time and money.
The comparison I always make is, why use machine code when we have dos and why use dos when we have Windows? It's the evolution of things!

*I'm currently working on building a Divi React Module to utilise LBRY.
I see Divi and LBRY as a good pair that can work together in many situations.

i would like to recommend using a framework like laravel instead of choosing a cms like wordpress. The two options will attract different types of contributors so you might base your decision on what LBRY needs to attract for the website. Although, the draw for designers (as opposed to devs) can still be influenced by what you choose for css, frontend frameworks, etc. if you went the laravel route.


Show values of formula but do not calculate the final value

Good day.
Sometimes a formula becomes very long, and it goes to the next line.
A way to display the formula, substitution of values, and then the answer in more than one line.
It would help, that there are a similar function as #noc, that

only shows the substituted values in the formula (excluding the original formula and final answer)
shows the formula, with substituted values with the formula (excluding the final answer)

To help what I mean I give a small example.
m = 5
c = 3
y = m * x + c
x = 6
for case 1) y = 5 * 6 + 3
for case 2) y = m * x + c = 5 * 6 + 3

Yes, I did and got the following:
m = 5
c = 3
y = m·x + c
x = 6
for case 1) y = 5·6 + 3
for case 2) y = m·x + c
y = 33

Yes, I did and got the following:
m = 5 c = 3 y = m·x + c x = 6 for case 1) y = 5·6 + 3 for case 2) y = m·x + c y = 33

It was a formatting example for Itenium like he want to see.

Hi!
This feature is now available in v6.1.9:
https://github.com/Proektsoftbg/Calcpad/releases/tag/v6.1.9


How to skip rendering on a view or controller

What if I don't want Google Analytics to be loaded on a view?

We're having the same issue, we trying to skip rendering on certain controllers or layouts entirely.  Not sure how to best accomplish this?

You can comment it out using this trick:
<body>
  <%= yield %>

  <!-- fake tag to fool Rack::Tracker
    </body>
  -->
</body>

Rack::Tracker will find the fake </body> tag and insert its stuff inside the comment. ;-)

you could "configure" this in a proc by checking the env["PATH_INFO"] for your views url.
sorry, this feature is a little bit hidden in the documentation...
You can find an example here: https://github.com/railslove/rack-tracker/issues/34#issuecomment-87623560

does @DonSchado's solution work for you?
If so this might be something that should be documented in the readme?

You can comment it out using this trick:
<body>
  <%= yield %>

  <!-- fake tag to fool Rack::Tracker
    </body>
  -->
</body>

Rack::Tracker will find the fake </body> tag and insert its stuff inside the comment. ;-)

it works! Thanks


Can't get the captions on Chrome

Can't get the captions on Chrome, gotta see what is wrong with it asap.

See issue number #5