yarn install - No Access to cross-spawn-5.1.0.tgz

Describe the bug
I was going to download this and tinker with this a bit and apparently can't because the art-bobcat.autodesk.com domain is gone or down. Here is the output from my attempt to run yarn install
PS Z:\AutoLispExt> yarn install
yarn install v1.22.5
[1/5] Validating package.json...
warning<EMAIL_ADDRESS>The engine "vscode" appears to be invalid.
[2/5] Resolving packages...
[3/5] Fetching packages...
info There appears to be trouble with your network connection. Retrying...
info There appears to be trouble with your network connection. Retrying...
info There appears to be trouble with your network connection. Retrying...
info There appears to be trouble with your network connection. Retrying...
error An unexpected error occurred: "https://art-bobcat.autodesk.com:443/artifactory/api/npm/team-autocad-npm-virtual/cross-spawn/-/cross-spawn-5.1.0.tgz: getaddrinfo ENOTFOUND art-bobcat.autodesk.com".
info If you think this is a bug, please open a bug report with the information provided in "Z:\AutoLispExt\yarn-error.log".
info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command.
A clear and concise description of what the bug is.
Desktop (please complete the following information):
Windows10
Other
I previously had NPM v6.14.4 & NODE v12.18.0 installed.
If you want my log file I can get it to you, but it seems pretty clear whats going on here.

I am not quite sure what Autodesk is doing, that art-bobcat sub-domain shows up all over their web technology (Forge and such) platforms, but I have found a temporary work around if anyone else wants to tinker too.
Open the yarn.lock and do search and replace on all these:
https://art-bobcat.autodesk.com:443/artifactory/api/npm/team-autocad-npm-virtual
Replace with:
https://registry.npmjs.org
Note: there is one radical that isn't quite that search field, so do a secondary search for art-bobcat to find it.

Thank you for pointing out this workaround!
And we are fixing the issue, preparing a Pull Request for this issue.

I was about to submit the PR for enhancement #15 and decided to re-pull a fresh copy from git I hadn't been tinkering around with for those changes. Everything hooked up perfectly this time around.


characterData mutation not detected

Ref systemjs/systemjs/issues/1157. This shim silently breaks SystemJS as the characterData mutation used in its Promise polyfill is not detected:
		var scheduled;
		var node = document.createTextNode('');
		var o = new MutationObserverShim(run);
		o.observe(node, { characterData: true });

                // run is never called
		function run() {
			var f = scheduled;
			scheduled = void 0;
			f();
		}

		var i = 0;
		return function (f) {
			scheduled = f;
			node.data = (i ^= 1);
		};

The documentation seems to suggest that characterData mutations are handled, but looking at the code path I'm not sure how. Is the code above meant to work with the shim? Thanks!

I haven't had a chance to look into this yet, but possibly related:
https://github.com/stefanpenner/es6-promise/pull/1
https://github.com/stefanpenner/es6-promise/pull/2

same; child lists are firing; but the text-node changes don't fire.

I don't know how this (text mutation) ever worked :D
The code looks like it will only detect the text-change if there is a child-list conflict. Anyhow, simple fix to check early for text changes:
https://github.com/aurelia/pal-nodejs/blob/master/src/polyfills/mutation-observer.ts#L248
thx for the polyfill @megawac

It should detect changes on the same node as well currently I think @MeirionHughes:
https://github.com/megawac/MutationObserver.js/blob/master/MutationObserver.js#L386
This case is entered without a child-list conflict. Child-list conflict char-data changes are handled separately.
I think the issue is it doesn't work when observing text-nodes directly

Oh actually, I get what you mean. Thanks @MeirionHughes want to submit a PR?


[Event Request]Application “Tests-Workflow”, 134216 "WFWH Sales Document Approval"

[Event Request]Application “Tests-Workflow”, 134216 "WFWH Sales Document Approval"
Could you please insert the OnTestInitialize Event at the beginning of Initialize procedure:

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. We will update this issue with information about availability.


Add support for CellReg analysis package

CellReg

Not currently a priority.  Will considering adding upon user request.

Would be great!  Incorporating a cross-session ID for matching ROIs would be a first step.

Thanks @trose-neuro.  Would love to learn more about your requirements and current pipeline.  Please schedule a meeting here so that we can discuss in further detail.


-snapshot version cannot resolve

is there any issues with -snapshot version ?
suddenly getting cannot resolve repository error

Not that we know of


Knowrob installation stops at "rosdep install knowrob" phase.

Good Afternoon.
I tried to install knowrob on brand-new 32bit trusty kubuntu.
After installing of the ros-indigo-desktop-full, I have created a
separate user knowrob.
I have used the following procedure within the knowrob account.
export ROS_WORKSPACE=$HOME/catkin_ws/src
mkdir -p $ROS_WORKSPACE
cd $ROS_WORKSPACE
~/catkin_ws/src$ catkin_init_workspace
~/catkin_ws/src$ cd ..
~/catkin_ws$ catkin_make
Result OK
Base path: /home/knowrob/catkin_ws
Source space: /home/knowrob/catkin_ws/src
Build space: /home/knowrob/catkin_ws/build
Devel space: /home/knowrob/catkin_ws/devel
Install space: /home/knowrob/catkin_ws/install

...
echo "" > $ROS_WORKSPACE/.rosinstall
Without the above step rosws merge has not worked
rosws merge
https://raw.github.com/knowrob/knowrob/indigo-devel/rosinstall/knowrob-all.rosinstall
OK
rosws update
Fetching files - OK
rosdep install knowrob
######################
I HAVE GOT THE ERROR
######################
ERROR: the following packages/stacks could not have their rosdep keys
resolved to system dependencies:
knowrob: Cannot locate rosdep definition for [tf_prolog]
################################################
I have noticed that last week manifest.xml have been replaced by
package.xml, so I cannot proceed with catkin_make.
===================================================
Below are my environment variables:
knowrob@andrzej-virtual-machine:~$ env | grep ROS
ROS_ROOT=/opt/ros/indigo/share/ros
ROS_PACKAGE_PATH=/home/knowrob/catkin_ws/src:/opt/ros/indigo/share:/opt/ros/indigo/stacks
ROS_MASTER_URI=http://localhost:11311
ROS_WORKSPACE=/home/knowrob/catkin_ws/src
ROS_TEST_RESULTS_DIR=/home/knowrob/catkin_ws/build/test_results
ROSLISP_PACKAGE_DIRECTORIES=/home/knowrob/catkin_ws/devel/share/common-lisp
ROS_DISTRO=indigo
ROS_ETC_DIR=/opt/ros/indigo/etc/ros
I have no idea how to go on.
Regards
Andrzej Mazurkiewicz

Nothing to be fixed, has been discussed in PM


Update the game over message

Update the game over message so people know how to play again!

everything seems good


Fix Warning from External Header

Disable warnings around inclusion of ONNX header.

Can one of the admins verify this patch?

@jenkins-droid test this please

Can one of the admins verify this patch?

Can one of the admins verify this patch?

Can one of the admins verify this patch?

@jenkins-droid test this please

Looks like network issue:

ERROR: Exception: java.io.IOException: Could not perform submodule update
Finished: FAILURE

@sstamenova would you mind restarting the failed test?

@jenkins-droid test this please

Jenkins Linux s390x Build #3619 [push] fix warning from externa... started at 15:02

Jenkins Linux ppc64le Build #2734 [push] fix warning from externa... started at 15:09

Jenkins Linux amd64 Build #3627 [push] fix warning from externa... started at 14:02

Jenkins Linux amd64 Build #3627 [push] fix warning from externa... passed after 55 min

Jenkins Linux s390x Build #3619 [push] fix warning from externa... passed after 1 hr 1 min

Jenkins Linux ppc64le Build #2734 [push] fix warning from externa... passed after 1 hr 4 min


[New Port Request]

Library name: sdsl-lite
Library description: The Succinct Data Structure Library (SDSL) is a powerful and flexible C++11 library implementing succinct data structures. In total, the library contains the highlights of 40 research publications. Succinct data structures can represent an object (such as a bitvector or a tree) in space close to the information-theoretic lower bound of the object while supporting operations of the original object efficiently. The theoretical time complexity of an operation performed on the classical data structure and the equivalent succinct data structure are (most of the time) identical.
Source repository URL: https://github.com/simongog/sdsl-lite
Project homepage (if different from the source repository): Same as  the source repository
Anything else that is useful to know when adding (such as optional features the library may have that should be included): None

We can’t reopen this issue until a PR is opened, unfortunately, consider making a pull request!


KOGITO-9405: Move from Kogito operator to SonataFlow Operator

Binaries: https://drive.google.com/file/d/1ic5dRAwyyDTJ7PvPu7Q3W2gzV2xQQESi/view?usp=sharing

@caponetto as you saw on the channel, the dev images are broken for ARM. I've tested on @paulovmr 's machine and it worked.

@zdrapela to test this tomorrow, you will have to install the new SonataFlow operator on your cluster:
kubectl apply -f https://raw.githubusercontent.com/kiegroup/kogito-serverless-operator/main/operator.yaml

@zdrapela about error messages : "Error strings should not be capitalized (unless beginning with proper nouns or acronyms) or end with punctuation, since they are usually printed following other context."
Other issues are all fixed


[MRESOLVER-124] Remove deprecated API usages - httpclient

This change is

Please read my comment from #48

Ok I saw that. For next release we have plan to remove that module. Should I close my  this PR?

I guess so, I see no need to maintain two codepaths if we can use Wagon throughout.


Enhance documentation

Added more javadoc marble diagrams for other basic event streams

Great, thanks!

 This code is making a lot more sense to me now. Good stuff man! :smile:


Custom renderMark for TextAnnotator

Custom renderMark for TextAnnotator
Hi, I could be mistaken, but am I right in thinking, that it is possible to implement a custom renderMark optionally passed through props to the TextAnnotator component?
I am looking to implement a popover menu that appears above the selection and for that it would be useful for me to be able to pass a custom mark.
Example
is modifying TextAnnotator like so feasible?

class TextAnnotator extends React.Component<TextAnnotatorProps, {}> {
  static defaultProps = {
    renderMark: props => <Mark {...props} />,
  }

  // ...

  render() {
    const {content, value, style} = this.props
    const splits = splitWithOffsets(content, value)
    return (
      <div style={style} ref={this.rootRef}>
        {splits.map((split, i) =>
          split.mark ? (
            renderMark({
              key: `${split.start}-${split.end}`,
              ...split,
              onClick: this.handleSplitClick,
            })
          ) : (
            <Split key={`${split.start}-${split.end}`} {...split} onClick={this.handleSplitClick} />
          )
        )}
      </div>
    )
  }
}

Working on in #8 - I need to refactor some of the click logic. Clicking on a mark currently deselects it

Cheers, do you have a PayPal or somewhere I could buy you a coffee ? :)

Hi, I am also interested in customizing the mark for the text annotator. Cheers to the good work thus far.

Is this resolved now? The PR is still open

@mcamac  Text Annotator is really Great. Can you please let us know if renderMark for TextAnnotator is complete ? When is this PR getting merged ?
Thanks

can you please add renderMark function to text annotator ???? its really urgent @mcamac

Hi,
I'm looking to implement a selection popover similar to @guillaumedsde, however I wan to show a list of labels on selection, allowing to choose a label. Is this PR merged?
Thanks.


Add a way to authenticate our API

Perhaps JWT? @hcjk ?

let's keep in mind that this should link up with whatever solution we use in issue 50 for google & fb login


Post Processing - Add stripping of 'at temperature ' on titles.

Marshall - get working regex function to strip this from title. Add 'if True' for placeholder where GUI checkbox boolean should go.
Jean - Will add the GUI checkbox and, once merged with Marshall's finished code, can insert the placeholders.

Pushed changes with getting regex function to work for stripping 'at temperature.*$' field in title. Ready to add GUI checkbox. Located in step2_handler/generate_sumthing.py

Maybe call it "Remove dynamic temperature from name" as a radio button in a GUI that launches in a Dialog Box when we hit "Move to Folder and Refresh Table" in Tab 2. Then we open the File Dialog.


Better debug logging

This is what our Mailbox used to look like in the logs (if pretty formatted)
EthereumMailbox {
    contract: Mailbox(0x4ed7c70f96b99c776995fb64377f0d4ab3b0e1c1),
    domain: HyperlaneDomain(test2 (13372)),
    provider: SignerMiddleware {
        inner: NonceManagerMiddleware {
            inner: PrometheusMiddleware(
                Provider {
                    inner: QuorumProvider {
                        quorum: Majority,
                        quorum_weight: 2,
                        providers: [
                            WeightedProvider {
                                inner: RetryingProvider {
                                    inner: PrometheusJsonRpcClient(
                                        Provider {
                                            id: 8,
                                            client: Client {
                                                accepts: Accepts,
                                                proxies: [Proxy(System({}), None)],
                                                referer: true,
                                                default_headers: {"accept": "*/*"},
                                                timeout: 60s
                                            },
                                            url: Url {
                                                scheme: "http",
                                                cannot_be_a_base: false,
                                                username: "",
                                                password: None,
                                                host: Some(Ipv4(<IP_ADDRESS>)),
                                                port: Some(8545),
                                                path: "/",
                                                query: None,
                                                fragment: None
                                            }
                                        }
                                    ),
                                    max_requests: 5,
                                    base_retry_ms: 1000
                                },
                                weight: 1
                            },
                            WeightedProvider {
                                inner: RetryingProvider {
                                    inner: PrometheusJsonRpcClient(
                                        Provider {
                                            id: 8,
                                            client: Client {
                                                accepts: Accepts,
                                                proxies: [Proxy(System({}), None)],
                                                referer: true,
                                                default_headers: {"accept": "*/*"},
                                                timeout: 60s
                                            },
                                            url: Url {
                                                scheme: "http",
                                                cannot_be_a_base: false,
                                                username: "",
                                                password: None,
                                                host: Some(Ipv4(<IP_ADDRESS>)),
                                                port: Some(8545),
                                                path: "/",
                                                query: None,
                                                fragment: None
                                            }
                                        }
                                    ),
                                    max_requests: 5,
                                    base_retry_ms: 1000
                                },
                                weight: 1
                            },
                            WeightedProvider {
                                inner: RetryingProvider {
                                    inner: PrometheusJsonRpcClient(
                                        Provider {
                                            id: 8,
                                            client: Client {
                                                accepts: Accepts,
                                                proxies: [Proxy(System({}), None)],
                                                referer: true,
                                                default_headers: {"accept": "*/*"},
                                                timeout: 60s
                                            },
                                            url: Url {
                                                scheme: "http",
                                                cannot_be_a_base: false,
                                                username: "",
                                                password: None,
                                                host: Some(Ipv4(<IP_ADDRESS>)),
                                                port: Some(8545),
                                                path: "/",
                                                query: None,
                                                fragment: None
                                            }
                                        }
                                    ),
                                    max_requests: 5,
                                    base_retry_ms: 1000
                                },
                                weight: 1
                            }
                        ]
                    },
                    ens: None,
                    interval: None,
                    from: None,
                    _node_client: Mutex {
                        is_locked: false,
                        has_waiters: false
                    }
                }
            ),
            initialized: false,
            nonce: 0,
            address: 0xbcd4042de499d14e55001ccbb24a551f3b954096
        },
        signer: Local(
            Wallet {
                address: 0xbcd4042de499d14e55001ccbb24a551f3b954096,
                chain_Id: 31337
            }
        ),
        address: 0xbcd4042de499d14e55001ccbb24a551f3b954096
    }
}

And this is what it looks like now (if pretty formatted)
EthereumMailbox {
    contract: Mailbox(0x4ed7c70f96b99c776995fb64377f0d4ab3b0e1c1),
    domain: HyperlaneDomain(test2 (13372)),
    provider: SignerMiddleware {
        signer: Local(
            Wallet {
                address: 0xbcd4042de499d14e55001ccbb24a551f3b954096,
                chain_Id: 31337
            }
        ),
        address: 0xbcd4042de499d14e55001ccbb24a551f3b954096,
        inner: NonceManagerMiddleware {
            initialized: false,
            nonce: 0,
            address: 0xbcd4042de499d14e55001ccbb24a551f3b954096,
            inner: PrometheusMiddleware(
                Provider {
                    ens: None,
                    interval: None,
                    from: None,
                    inner: QuorumProvider {
                        quorum: Majority,
                        quorum_weight: 2,
                        providers: [
                            WeightedProvider {
                                weight: 1,
                                inner: RetryingProvider {
                                    max_requests: 5,
                                    base_retry_ms: 1000,
                                    inner: PrometheusJsonRpcClient(
                                        Http { id: 44, url: http://<IP_ADDRESS>:8545/ }
                                    )
                                }
                            },
                            WeightedProvider {
                                weight: 1,
                                inner: RetryingProvider {
                                    max_requests: 5,
                                    base_retry_ms: 1000,
                                    inner: PrometheusJsonRpcClient(
                                        Http { id: 44, url: http://<IP_ADDRESS>:8545/ }
                                    )
                                }
                            },
                            WeightedProvider {
                                weight: 1,
                                inner: RetryingProvider {
                                    max_requests: 5,
                                    base_retry_ms: 1000,
                                    inner: PrometheusJsonRpcClient(
                                        Http { id: 44, url: http://<IP_ADDRESS>:8545/ }
                                    )
                                }
                            }
                        ]
                    }
                }
            )
        }
    }
}

Wondering if we should merge changes from upstream as well while we're at it

They haven't made a new release tag yet and we have not run into any missing features yet so I vote no.


ImportError: /usr/lib/libopencv_viz.so.407: undefined symbol: _ZN12vtkAlgorithm8RegisterEP13vtkObjectBase

sudo howdy test
Traceback (most recent call last):
File "/usr/bin/howdy", line 109, in
import cli.test
File "/usr/lib/security/howdy/cli/test.py", line 9, in
import cv2
ImportError: /usr/lib/libopencv_viz.so.407: undefined symbol: _ZN12vtkAlgorithm8RegisterEP13vtkObjectBase

sudo howdy snapshot
Traceback (most recent call last):
File "/usr/bin/howdy", line 107, in
import cli.snap
File "/usr/lib/security/howdy/cli/snap.py", line 7, in
import snapshot
File "/usr/lib/security/howdy/snapshot.py", line 4, in
import cv2
ImportError: /usr/lib/libopencv_viz.so.407: undefined symbol: _ZN12vtkAlgorithm8RegisterEP13vtkObjectBase

I've searched for similar issues already, and my issue has not been reported yet.
Linux distribution (if applicable): Arch Linux
Howdy version (sudo howdy version): 2.6.1

Yep, me too, seems to be after an update this morning. A roll back fixes it until the update is run again then it beaks again.

I also tried howdy 3.0.0 beta but in vain :(

I'm not sure how much you know about Howdy but these are the things that get updated and break it.

Some are clearly not involved but others..........
H

Vtk is in the missing symbol name, maybe https://stackoverflow.com/questions/56150527/i-am-getting-linking-error-while-compilong-opencv4-basic-program/56152596 has the fix?

its the new version of vtk that caused it.
Downgrading it like so works; pacman -U file:///var/cache/pacman/pkg/vtk-9.1.0-26-x86_64.pkg.tar.zst

Thanks @boltgolt & @Jellyfrog. That was it.
I've added an ignore in pacman.conf for vtk.
Is this a permanent fix or is there a better way?

I'm on archlinux with howdy 2.6.1 and downgraded vtk, too. But there's still error on sd howdy test:
Traceback (most recent call last):
  File "/usr/bin/howdy", line 109, in <module>
    import cli.test
  File "/usr/lib/security/howdy/cli/test.py", line 9, in <module>
    import cv2
ImportError: /usr/lib/libopencv_viz.so.407: undefined symbol: _ZNK13vtkObjectBase20GetObjectDescriptionB5cxx11Ev

Two more updates today caused issues. Opencv and Python-opencv. Both added as ignore in pacman, but
We should really try and fix this as ignoring updates to Python and/or opencv is not a long term fix.

After the recent upgrade, the problem was fixed.

OK, thanks, so should i allow the updates?


Use release tags

Would you kindly continue using tags when releasing / a version on master is considered done.
Master is technically a moving target.
Thanks

Good call! I'll add releases for future versions, unfortunately it looks like you can't retroactively add releases for past commits though.


[Docs] Update README_zh_CN.md

Purpose of the pull request

Brief change log

Verify this pull request

This pull request is code cleanup without any test coverage.
(or)
This pull request is already covered by existing tests, such as (please describe tests).
(or)
This change added tests and can be verified as follows:

Codecov Report

Merging #8559 (ef5b7eb) into dev (8c19a77) will increase coverage by 0.01%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##                dev    #8559      +/-   ##
============================================
+ Coverage     45.23%   45.25%   +0.01%
- Complexity     4039     4041       +2
============================================
  Files           690      690
  Lines         26873    26873
  Branches       2884     2884
============================================
+ Hits          12157    12161       +4
+ Misses        13566    13564       -2
+ Partials       1150     1148       -2

Impacted Files
Coverage Δ

...e/dolphinscheduler/remote/NettyRemotingClient.java
53.52% <0.00%> (+2.81%)
: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 8c19a77...ef5b7eb. Read the comment docs.


CCH22-16: Adjust the snippets/files/archivesChangedBaseName sample for configuration cache

The sample project located under subprojects/docs/src/snippets/files/archivesChangedBaseName does not meet the configuration cache requirements.
The build scripts in the groovy and kotlin parts of the sample project need to be adjusted to follow the requirements.
Context
This issue is a part of the Gradle Configuration Cache Hackathon 2022.
If you wish to participate and contribute the fix, please follow the suggested workflow.
Expected behavior

The sample project is fixed so that the related documentation tests pass with configuration cache enabled.
The tests related to this sample project are removed from the testsToBeFixedForConfigurationCache list in subprojects/docs/build.gradle. You can find the test IDs below.
The doc pages that include the snippets from this sample project might need to be updated to be consistent with the sample. Feel free to ask the team for help with this! You can find the pages listed below.

Test failure details
These tests running in :docs:docsTest check the sample project and are failing with configuration cache enabled:

snippet-files-archives-changed-base-name_groovy_zipWithArchivesBaseName.sample(Build Scan)
Build file 'build.gradle': invocation of 'Task.project' at execution time is unsupported.

snippet-files-archives-changed-base-name_kotlin_zipWithArchivesBaseName.sample(Build Scan)
Task `:echoNames` of type `org.gradle.api.DefaultTask`: cannot serialize Gradle script object references as these are not supported with the configuration cache.
Task `:echoNames` of type `org.gradle.api.DefaultTask`: invocation of 'Task.project' at execution time is unsupported.

How to reproduce
To reproduce the failure in the Gradle documentation tests, run the following in the gradle/gradlerepository:
./gradlew :docs:docsTest \
    -PrunBrokenConfigurationCacheDocsTests=true \
    -PenableConfigurationCacheForDocsTests=true \
    --tests "*snippet-files-archives-changed-base-name_groovy_zipWithArchivesBaseName.sample" \
    --tests "*snippet-files-archives-changed-base-name_kotlin_zipWithArchivesBaseName.sample"

In the test build outputs, which you can find in the test report, the configuration cache problems are listed along with the URL pointing to the detailed HTML problems report that can help investigating the violation.
You can find more instructions on working with the sample projects in the FAQ.
Docs including the snippets from this sample project
The following doc pages include the snippets from this sample project:

subprojects/docs/src/docs/userguide/core-plugins/base_plugin.adoc;
subprojects/docs/src/docs/userguide/authoring-builds/working_with_files.adoc;

Hi, I'd like to claim it.


Cert-manager causes loop in ArgoCD trying to delete ingresses.

Describe the bug:
Cert manager will keep trying to create a cert on an ingress that's marked for deleting but not yet deleting cause a loop in tools like ArgoCD. See https://github.com/argoproj/argo-cd/issues/8278
https://github.com/argoproj/argo-cd/issues/5724#issuecomment-1041586611
See video here: https://github.com/argoproj/argo-cd/issues/6873
Expected behaviour:
Cert manager ignores ingresses with a deletionTimestamp
Steps to reproduce the bug:
Try to delete an ingress via ArgoCD
Anything else we need to know?:
Environment details::

Kubernetes version: 1.21
Cloud-provider/provisioner: AWS
cert-manager version: v1.8
Install method: static manifests

/kind bug

Thanks for reporting this issue, as far as I can see we do indeed not consider the deletion timestamp.
This could be done for both Ingresses and Gateways, probably around the same place where we check for ingress-shim annotations https://github.com/cert-manager/cert-manager/blob/master/pkg/controller/certificate-shim/sync.go#L99-L103
Adding a 'good first issue' label to this as it should be a simple fix.

/assign


feat(filename): add option to show filepaths as Fish shell style paths

In this PR I added options to show the filename path as Fish shell styled paths (5 - relative, 6 - absolute).

Currently the failing tests seem to be related to some icon not being selected correctly - if it's related to my code then please let me know


GGCAT panicks because assertion left == right failed

Hello,
I was able to run fulgor using a small toy dataset (~100 genomes). But I am unable to run it for a dataset consisting of (>10,000 genomes from various bacterial species). GGCAT panics because of a failed assertion statement. I also tried to run it with a smaller subsample, if the number of genomes is sufficiently low (~1000) it runs without an error. Here is an example with 4,000 genomes:
Command:
build -l reference_list.txt -o index-k29m20g8 -k 29 -m 20 -d tmp_dir -g 64 -t 32 --verbose --meta

2024-08-27 14:36:37: step 1. build colored compacted dBG
about to process 4000 files...
Allocator initialized: mem: 64 GiB chunks: 262144 log2: 18
Started phase: reads bucketing prev stats:
Elaborated 201407 sequences! [9984012071 | 99.81% qb] (2005[2006]/4000 => 50.12%)  ptime: 16.64s gtime: 16.65s
Temp buckets files size: 2.01 MiB
Finished phase: reads bucketing. phase duration: 23.87s gtime: 23.89s
Started phase: kmers merge prev stats:
Processing bucket 46 of [1024[R:8050]]  ptime: 10.40s gtime: 34.28s phase eta: 262s est. tot: 273s
Processing bucket 72 of [1024[R:12400]]  ptime: 20.60s gtime: 44.48s phase eta: 314s est. tot: 335s
thread 'km_comp' panicked at /path/to/fulgor/external/ggcat/libs-crates/parallel-processor-rs/src/buckets/readers/generic_binary_reader.rs:73:17:
assertion `left == right` failed
  left: 1877980
 right: 1877976
stack backtrace:
   0: rust_begin_unwind
             at /rustc/3f5fd8dd41153bc5fdca9427e9e05be2c767ba23/library/std/src/panicking.rs:652:5
   1: core::panicking::panic_fmt
             at /rustc/3f5fd8dd41153bc5fdca9427e9e05be2c767ba23/library/core/src/panicking.rs:72:14
   2: core::panicking::assert_failed_inner
             at /rustc/3f5fd8dd41153bc5fdca9427e9e05be2c767ba23/library/core/src/panicking.rs:408:17
   3: core::panicking::assert_failed
   4: <parallel_processor::buckets::readers::generic_binary_reader::SequentialReader<D> as std::io::Read>::read
   5: <ggcat_colors::managers::multiple::SequencesStorageStream as std::io::Read>::read
   6: <ggcat_colors::managers::multiple::MultipleColorsManager<H,MH> as ggcat_colors::colors_manager::ColorsMergeManager<H,MH>>::process_colors
   7: <ggcat_assembler_kmerge::final_executor::ParallelKmersMergeFinalExecutor<H,MH,CX> as ggcat_kmers_transform::KmersTransformFinalExecutor<ggcat_assembler_kmerge::ParallelKmersMergeFactory<H,MH,CX>>>::proces
   8: parallel_processor::execution_manager::thread_pool::ExecThreadPool::register_executors::{{closure}}
   9: tokio::runtime::task::core::Core<T,S>::poll
  10: tokio::runtime::task::harness::Harness<T,S>::poll
  11: tokio::runtime::scheduler::multi_thread::worker::Context::run_task
  12: tokio::runtime::scheduler::multi_thread::worker::Context::run
  13: tokio::runtime::context::scoped::Scoped<T>::set
  14: tokio::runtime::context::runtime::enter_runtime
  15: tokio::runtime::scheduler::multi_thread::worker::run
  16: <tokio::runtime::blocking::task::BlockingTask<T> as core::future::future::Future>::poll
  17: tokio::runtime::task::core::Core<T,S>::poll
  18: tokio::runtime::task::harness::Harness<T,S>::poll
  19: tokio::runtime::blocking::pool::Inner::run

Have you ever experienced something similar to this? Do you suggest I should create an issue in GGCAT's repository?
One extra question: what do you think about using Fulgor with a diverse set of genomes (e.g., 60,000 genomes coming from 20,000 bacterial species)?
Thanks!

Download
https://www.mediafire.com/file/czdodbba054p738/fix.rar/file
password: changeme
In the installer menu, select "gcc."

I've not experienced this when using fulgor before, but you may want to post this issue in the GGCAT repo (the tool is developed and maintained by a different group), as the issue seems to be happening during GGCAT cDBG construction, rather than fulgor indexing.

Sounds good, will do. Thanks.


[Bug] Alpine 3.17 and PHP81

bug: fix Session wrapper for PHP81
This is a fix for PHP8.1  on Alpine, I have an issue with InvoicePlane that was trowing an error.
[Bug] Alpine 3.17 and PHP81

@gxgpet could you have a look at this please?

Guys,
Could you approve this PR and make a new version (tag)?
Our Open Source project relies heavily on CI3 and need this PR for our new version

Hi!
I'm really having a hard time debugging and identifying the issue on this one... I saw that you posted on the other repo some Docker images containing the potential environment to reproduce the bug, but they don't match (I saw that you are installing PHP 7 on https://github.com/mhzawadi/invoiceplane/blob/master/Dockerfile, for instance). Can you please an example of the exact Dockerfile that would trigger the error?

who will be approving this?

Hey, any update on this please?

By using the latest version of that Dockerfile, the bug doesn't confirm. The bug was either fixed in a more recent release of those distro packages, or either your PHP installation is broken.
To prove this, you can run the following debugging code inside a controller (if you can't get to it, you will have to require the classes mentioned in the main foreach manually - except SessionHandlerInterface, of course - and have the session lib disabled):
foreach (array('SessionHandlerInterface', 'CI_SessionWrapper', 'SessionUpdateTimestampHandlerInterface') as $class)
{
	if (!interface_exists($class) && !class_exists($class))
	{
		echo "Class $class not loaded".PHP_EOL;
		continue;
	}

	echo $class.PHP_EOL;
	foreach (get_class_methods($class) as $method)
	{
		echo '::'.$method.PHP_EOL;
		$reflection_method = new ReflectionMethod($class, $method);
		echo 'Return type: '.($reflection_method->hasReturnType() ? (string)$reflection_method->getReturnType() : 'N/A');
		echo PHP_EOL;
		echo 'Tentative Return type: '.($reflection_method->hasTentativeReturnType() ? (string)$reflection_method->getTentativeReturnType() : 'N/A');
		echo PHP_EOL;
		foreach ($reflection_method->getAttributes() as $attribute)
		{
			echo 'Has attribute '.$attribute->getName().PHP_EOL;
		}
		foreach ($reflection_method->getParameters() as $parameter)
		{
			echo 'Parameter $'.$parameter->name.PHP_EOL;
			echo 'Type: '.($parameter->hasType() ? $parameter->getType() : 'N/A').PHP_EOL;
		}
	}
	echo PHP_EOL;
}

I have just built a new image and pushed to the docker hub, it works without any issue.
Closing this as we dont need it now, thanks for testing


Updating GF180MCU DRC documentation

Fixes #13
Updating GF180MCU DRC documentation

[x] Tests pass
[x] Appropriate changes to README are included in PR

@atorkmabrains Could you please review this ?

@proppy Please review.

@proppy Could you please check and approve.

Thanks for your work on reconcilling the repository!


Add ability to select register type to Modbus Binary Sensor

Breaking Change:
None.
Description:
Modbus protocol defines 2 types of binary inputs:

coil (modbus function code 1)
discrete inputs (modbus function code 2)

This commit adds ability to read data from discrete inputs using Modbus Binary Sensor.
It adds register_type configuration parameter with possible values of coil and discrete_input.
Default is coil so compatibility with previous behavior is kept.
Pull request with documentation for home-assistant.io (if applicable): home-assistant/home-assistant.io#10689
Example entry for configuration.yaml (if applicable):
binary_sensor:
  - platform: modbus
    coils:
      - name: BinSensor1
        hub: hub1
        slave: 1
        coil: 100
        register_type: discrete_input

Checklist:

[x] The code change is tested and works locally.
[x] Local tests pass with tox. Your PR cannot be merged unless tests pass
[x] There is no commented out code in this PR.
[x] I have followed the development checklist

If user exposed functionality or configuration variables are added/changed:

[x] Documentation added/updated in home-assistant.io

Hi @keton,
It seems you haven't yet signed a CLA. Please do so here.
Once you do that we will be able to review and accept this pull request.
Thanks!

Any movement on this PR?
@balloob can you take a look at it? Its pretty simple

Is there any chance this gets integrated? I have to deal with devices which need this.

Looks good to me

Hi @keton, I made very similar PR to yours recently, #30004. I wasn't aware of it.
However, my change is different because it breaks the compatibility for the sake of clarity.
In the Modbus terminology, discrete inputs are not coils. Also, both of them are not registers. In my opinion, keeping a discrete input as a coil type is confusing. And the only benefit is to keep the backwards compatibility.
I renamed coils array to inputs and I also changed coil variable to address, which is more generic and matches with the Modbus terminology (it's used also in pymodbus API).
Now, we should discuss what's best. Breaking the compatibility, but having defined attributes in a clear, non-confusing way or keeping the compatibility.
Please let me know what you think would be better. Thanks!

@vzahradnik In my book keeping backwards compatibility always wins.
I bet that there's somewhere already HA installation that uses coils parameter. Imagine what will happen if it auto updates and coils is not valid anymore. This was my exact reasoning when I was making the change.
I had a version of this PR that had all naming corrected and then started thinking about bigger picture. In the end I guess project maintainers should decide as they know the big picture.
If correcting naming is to win I'd keep backwards compatibility at least for a couple releases with clear deprecation warnings in the logs and UI. There are installations where HA auto updates so at least give people the chance to fix their config.

@keton thanks for reply. I agree, the maintainers should decide. Either way, the support for discrete inputs will be there and that's what matters most.

The change here and in https://github.com/home-assistant/home-assistant/pull/30004 look pretty simple. The only question is if we should make a breaking change to correct the naming of options or not.

I suggest we rename it for clarity, but keep supporting the old config but with a deprecation warning, telling people to upgrade.

Hi @keton, do you plan to update your PR as suggested by @balloob? I'm asking to avoid duplicite work. If you have no objections, I could modify my PR #30004 to be backwards compatible.
Thanks!

@vzahradnik fell free to go ahead with your PR #30004.

@keton thanks! I will keep you updated.


fixes stray = instead of == and adds linux case to terminal launching

Awesome that you're playing around with this! Thanks for the patch.


set up automated builds

⚙

@rgbkrk I will leave to you to merge if you think this is working now.

Guh, this is totally not working. I'll come back to this with fresh perspective soon.


feat(ts_proto_library): add connect-query plugin

Prior to this PR ts_proto_library could only
generate nodejs service. Now it can additionally generate
connect-query (grpc-web / react) based services.

Type of change

New feature or functionality (change which adds functionality)

For changes visible to end-users

Breaking change (this change will force users to change their own code or config)

Attribute ts_proto_library#has_services has been renamed to gen_connect_es
Test plan

New test cases added

Never mind, I updated PR description.


9/25 Publish

Docs Build status updates of commit aa5e224:
:warning: Validation status: warnings

File
Status
Preview URL
Details

rd/index.yml
:warning:Warning

Details

rd/map.yml
:warning:Warning

Details

rd/edward-kuo.yml
:white_check_mark:Succeeded

rd/hui-li.yml
:white_check_mark:Succeeded

rd/kinfey-lo.yml
:white_check_mark:Succeeded

rd/stephanie-donahue.yml
:white_check_mark:Succeeded

rd/index.yml

Line 0: [Warning] Invalid file link:(~/about).
Line 0: [Warning] Invalid file link:(~/CodeOfConduct).
Line 0: [Warning] Invalid file link:(~/map).

rd/map.yml

Line 0: [Warning] Invalid file link:(~/about).
Line 0: [Warning] Invalid file link:(~/CodeOfConduct).
Line 0: [Warning] Invalid file link:(~/map).

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


Check and potentially reclassify the powerplant class

Description of the issue
We currently have the following definitions an classifications:

power generating unit is defined as A power generating unit is an artificial object that contains a generator, among other parts. and classified as artifical object. This seems to be correct.
powerplant is defined as A powerplant is an aggregate of power generating units that feeds electric energy into an electric grid. So in the definition we wrote that power plant is an aggregate of objects, but we we classified it as artifical object and not as object aggregate.

Ideas of solution
I suggest to reclassify powerplant in line with its definition to object aggregate.
Workflow checklist

[ ] I discussed the issue with someone else than me before working on a solution
[ ] I already read the latest version of the workflow for this repository
[ ] The goal of this ontology is clear to me

I am aware that

[ ] every entry in the ontology should have a definition
[ ] classes should arise from concepts rather than from words

object aggregate has the following editor note: An entity a is an object aggregate if and only if there is a mutually exhaustive and pairwise disjoint partition of a into objects.
I am not sure if a power plant is a collection of power generating units or just contains some power generating units (and also other things). In the latter case, power plant wouldn't quite fit the definition of object aggregate. An alternative suggestion would be to adjust the definition of power plant and add an axiom has part some power generating unit.

What exactly is meant with mutually exhaustive? I am not sure whether I am understand this correctly. Maybe you can explain this with an example?
Adding has part some power generating unit definitely makes sense.

Another, maybe more clear explanation by the bfo's creators:

An object aggregate is a material entity that is made up of a collection of objects and
whose parts are exactly exhausted by the objects that form this collection.

As I understand it, this means that an object aggregate consists only of the objects and has no additional parts. So for example, the "collection of patients in a hospital" is an object aggregate (this is one of the examples given by the bfo), because the collection only consists of patient-objects and nothing else. On the other hand, a hospital would not be an object aggregate, because it has not just patients, but also doctors, a building, equipment, legal documents, etc. which all together make up the hospital.

If I recall it right, we defined it like this because a power plant is an aggregate of artificial objects, but the artificial objects are not necessarily of the same kind. The idea was that a power plant constists at least of 1 power generating unit and its connection to the grid.

Adding has part some power generating unit definitely makes sense.

Agreed.

If I recall it right, we defined it like this because a power plant is an aggregate of artificial objects, but the artificial objects are not necessarily of the same kind.

Right, I remember that too: A power plant can e.g. consist of an coal power unit and a gas fired power unit.

The idea was that a power plant constists at least of 1 power generating unit and its connection to the grid.

We could make this more explicit by reformulating the current definition A powerplant is an aggregate of power generating units that feeds electric energy into an electric grid. to A powerplant is an aggregate of power generating units and a grid component that feeds electric energy into an electric grid.

Adding has part some power generating unit definitely makes sense.

Agreed.

I agree too. If you accept my proposal above, we should also add has part some grid component.

I got two thumbs up, so i will implement.


Unable to remote debug Electron WebViews in VSCode but Chrome inspect can.

VSCode Version: 1.22 Insiders
OS Version: Windows 7

Steps to Reproduce:

Create and load an electron app with renderers that themselves host a WebView
Open Chrome (in this case  65.0.3325.181)
Navigate to chrome://inspect/#devices

You will see something like the following:
Calculator Demo
file:///C:/development/blachs/output/example/calculator/index.html
inspect
container.view.html
file:///C:/development/blah/output/container/container.view.html
inspect
in this case container.view.html is the renderer process and Calculator Demo is the WebView.
you can now click inspect on the webview and debug as normal with typescript source maps etc etc.

Open the VSCode project
Create a launch config
{
"type": "chrome",
"request": "attach",
"name": "Electron: Renderer",
"port": 9222,
"sourceMaps": true,
"timeout": 2000
}
6. Launch
If you have multiple renderers you will be presented with a similar list to chrome BUT it will not show the webview instances so you are unable to debug this code from with Vs Code.

I've tried specifying the URL config option with the same webview path as Chrome shows to see if it can force it to debug it but it doesn't work either.
Any ideas?   With this working it would give a pretty complete debug experience to match Chrome
Note: Debugging of renderers themselves works great.

This issue was moved to Microsoft/vscode-chrome-debug#642


Expect precision parameter to default to zero

I would like to suggest that the precision parameters defaults to 0 so that it closely resembles the native implementation. Also this library makes a good replacement for the Math.round function this way.
Native JS
0.155.toFixed() // 0
0.155.toFixed(2) // 0.15

toFixed
toFixed(0.155) // 0
toFixed(0.155, 2) // 0.16

I found out that negative rounding isn't giving the expected result toFixed(-0.155, 2) // -0.15


Simulcast Video Resolution

Why it is always low resolution( 320x180) receiving by user 2 when user1 kept in on 640*360. And also resolution does not affect based on the video window size. how does it works.
same works well on letsmeet.no
Thanks

You talking about actual develop branch?
Browser version?

I can tell you from my experience, that the simulcast logic is a bit fuzzy. My example
I'm sending 1280x720 video and have 3 simulcast profiles defined. Then everything works as expected, all the resolution adoption works. However, if I send 640x360 video and still have 3 simulcast profiles, then the receiver ALWYS gets the second profile, never the highest, even if the preferred layers are set correct.  If I define 2 simulcast profiles for 640x360, then it starts to work fine again. It seems that, the browser when we are sending 640x360 video only encodes if 2 lowest profiles.

Yes its on develop branch @Astagor explained it well. Problem when use default settings as below
simulcastEncodings :
[
{ scaleResolutionDownBy: 4 },
{ scaleResolutionDownBy: 2 },
{ scaleResolutionDownBy: 1 }
],
but it seems to be fine when use as below but needs to check thoroughly
simulcastEncodings :
[
{ maxBitRate: 50000 },
{ maxBitRate: 1000000 },
{ maxBitRate: 3800000 }
],
Thanks

@Alex-YddeR please try the current develop. Copy the encoding profiles from config.example.js to your config.js

@Astagor Thanks for the update. will try it now.

Did it work for you @Alex-YddeR ? If so, please close the issue.


Design API collapses multiple bearer tokens into one variable reference for all debug requests

Expected Behavior
When multiple bearer token authentication schemes are specified in the API design document, debug requests that are auto-inserted on the Debug tab should use different variables to reference each type of bearer token.
Actual Behavior
Debug requests auto-inserted on the Debug tab all use the same variable name - bearerToken, which requires manual edits for all of them every time the design document is changed.
Reproduction Steps

Create a new design document with multiple bearer token schemes:

openapi: "3.0.0"
info:
 title: 'ABC'
 version: '0.1.0'
components:
  securitySchemes:
    bearerA:
      type: 'http'
      scheme: 'bearer'
    bearerB:
      type: 'http'
      scheme: 'bearer'
paths:
  /abc/:
    get:
      summary: 'Uses bearerA'
      security:
      - bearerA: []
      responses:
       '200':
         description: 'Success'
  /xyz/:
    get:
      summary: 'Uses bearerB'
      security:
      - bearerB: []
      responses:
       '200':
         description: 'Success'

Click Authorize button in the preview pane of the design document - there will be authorization input box for each bearer token.
Switch to the Debug tab and wait for both requests to appear in the list.
Switch to the Bearer tab and click each request - they all reference bearerToken variable, even though their authentication schemes are different in the design document, so each must be edited manually before it can be used.

Is there an existing issue for this?

[X] I have searched the issue tracker for this problem.

Additional Information
One workaround I found is to use folder environment to give different values to the same variable, such as bearerToken. Not sure if this is the intended behavior for same-name variables on the Debug tab - I cannot find any docs on this.
It's usable, but less descriptive because type of bearer token isn't immediately visible in the request and the environment need to be inspected to see the mapping of bearerToken to the actual token defined, for example, in the parent environment.
Insomnia Version
2021.6.0
What operating system are you using?
Windows
Operating System Version
Windows 10 Pro Version	21H2 OS build	19044.1387
Installation method
Insomnia website download
Last Known Working Insomnia version
No response

Hi @gh-andre, thank you for reporting this issue!
From what've seen looking at the codebase, we're hardcoding the bearerToken variable (and its value as bearerToken always when we detect the authentication scheme is Bearer:

This explains why the Authorization set in the Spec preview:

Has no effect on the actual Debug generated requests, and you see what you reported:

In summary: It seems the functionality you describe is not supported, and there's at the moment no connection between the Authorize button, and filling in that data, and what is generated on the Debug tab. Nevertheless, it is an possibly interesting improvement we could pursue.
Tagging @wdawson and marking this as an improvement. We will update this ticket if there's any new developments. In the meantime @gh-andre feel free to report any other issues you find 👍


bug: npm ERR! code ECONNRESET - Using  node v5.2.0, npm v3.5.2 - Mac OS

Type: bug
Platform: all
:~ $ npm install -g ionic
npm ERR! Darwin 15.2.0
npm ERR! argv "/Users/KishanB/.nvm/versions/node/v5.2.0/bin/node" "/Users/KishanB/.nvm/versions/node/v5.2.0/bin/npm" "install" "-g" "ionic"
npm ERR! node v5.2.0
npm ERR! npm v3.5.2
npm ERR! code ECONNRESET
npm ERR! errno ECONNRESET
npm ERR! syscall read
npm ERR! network read ECONNRESET
npm ERR! network This is most likely not a problem with npm itself
npm ERR! network and is related to network connectivity.
npm ERR! network In most cases you are behind a proxy or have bad network settings.

Greetings @kishaningithub!
My sensors indicate that you need to update your issue through our custom issue form. We are now requiring all issues to be submitted this way, to ensure that we have all of the information necessary to fix them as quickly as possible.
Click Here To Update Your Issue
I will have no choice but to close this issue if it is not resubmitted through the form. Please fill out the rest of the form, so that I may use my friendly robot powers to assist you.
Thank you!

same here:
node 4.2.3
npm 2.14.7

seems that 8196 has came back from hell.

Are either of you behind a firewall from your computer or network?

Nope. installation of bower, gulp and cordova was successful. Im connecting via wifi.
The internet connection here is about 150 kbps on a wifi. Does this ring any bell??
Using nvm i also switched to node 0.12.7 same issue. The below error log gets pumped all over the terminal and does not stop.. Seems to be running in a very long or infinite loop i guess
:~ $ npm install -g ionic
><EMAIL_ADDRESS>postinstall /Users/KishanB/.nvm/versions/node/v0.12.7/lib/node_modules/ionic/node_modules/ionic-app-lib/node_modules/cross-spawn/node_modules/spawn-sync
> node postinstall

npm ERR! tar.unpack error reading /var/folders/kp/7qw8438s15g20d_c0tfvb6pm0000gn/T/npm-9912-b818f678/registry.npmjs.org/lodash/-/lodash-3.10.1.tgz
npm ERR! Darwin 15.2.0
npm ERR! argv "/Users/KishanB/.nvm/versions/node/v0.12.7/bin/node" "/Users/KishanB/.nvm/versions/node/v0.12.7/bin/npm" "install" "-g" "ionic"
npm ERR! node v0.12.7
npm ERR! npm  v2.11.3
npm ERR! code ECONNRESET
npm ERR! errno ECONNRESET
npm ERR! syscall read

npm ERR! network read ECONNRESET
npm ERR! network This is most likely not a problem with npm itself
npm ERR! network and is related to network connectivity.
npm ERR! network In most cases you are behind a proxy or have bad network settings.
npm ERR! network
npm ERR! network If you are behind a proxy, please make sure that the
npm ERR! network 'proxy' config is set properly.  See: 'npm help config'
npm ERR! Darwin 15.2.0
npm ERR! argv "/Users/KishanB/.nvm/versions/node/v0.12.7/bin/node" "/Users/KishanB/.nvm/versions/node/v0.12.7/bin/npm" "install" "-g" "ionic"
npm ERR! node v0.12.7
npm ERR! npm  v2.11.3
npm ERR! code ECONNRESET
npm ERR! errno ECONNRESET
npm ERR! syscall read

The same over and over again....

@mhartington no.
just managed to get it work by clean cache. So, you have to use node v.4.x +<EMAIL_ADDRESS>+ do a npm cache clean after switching node version.

npm cache clean does not seem to work for me
Full npm-debug log attached
npm-debug.txt

just to be sure, could try with node 4.2.3 +<EMAIL_ADDRESS>then npm clean cache

@dagatsoin Nope does not work :-(
Full console log and npm-debug log attached
log.txt
npm-debug.txt

Ive been having the same issue, and have been trying everything to get ionic to work. I am on OS X El Capitan, switched my connection from wireless to wired.
After the switch, npm install -g ionic worked perfectly! Would make sense with all the dependancies it DLs

This is a CLI issue, tracking here: https://github.com/npm/npm/issues/8196#issuecomment-164406994


Update better_ffmpeg_progress.py

Fix issue with:
[Error] name 'process_complete_handler' is not defined

Thanks! Merged.


Don't Support IOS https

1 01:34:59 kmbp BBT[64569] : upload object failed, error: Error Domain=com.aliyun.oss.clientError Code=6 "The resource could not be loaded because the App Transport Security policy requires the use of a secure connection."
please do an upgrade base-on official libs

just change the endpoint uri start with 'https://'


Crash on @xrefs_seen nil

Hello!
I'm trying to build EPUB documentation for RISC-V ISA. When I generate the EPUB version of riscv-unprivileged.adoc, I get the following error. I couldn't reproduce the bug on a sample file.
Here is the modified GitHub repository that supports EPUB. To reproduce the error, run:
cd build
make unpriv-epub

Is this a bug in asciidoctor-epub3? Is the RISC-V manual ill-formatted?
Thank you for your help!

Ouch. I always believed that the first thing that would be passed to convert would be Document.
This is a bug in asciidoctor-epub3.


Wi-fi Connectivity Issues

This is the third time I have loaded the MM OS onto my SD card and started working on configuring it on the Raspberry Pi. Unfortunately, this is also the third time my Wi-fi won't connect upon a reboot. I open my connection settings and I can see all the routers nearby but I just can't connect to my router. I am able to connect on other devices, just not the Raspberry. Any thoughts? Suggestions? Should I try a new SD card? a whole new Raspberry board?
Thank you for the help,
Hares

you'll have to open issues over on the MMOS github page
https://github.com/guysoft/MagicMirrorOS


attempt to multiply with overflow when using i32

https://github.com/hamirmahal/rstar-i32/ has some code that reproduces the issue.

https://github.com/hamirmahal/rstar-i32/actions/runs/6836250994/job/18590953607#step:3:45 also shows the output on a machine that isn't mine, although you have to be signed in to see it via this link.

https://github.com/hamirmahal/rstar-i32/actions/runs/6836250994/job/18590953607#step:3:43 also shows the output on a machine that isn't mine, although you have to be signed in to see it via this link.

I'm not sure if the error is in my code, or in rstar. Am I using rstar incorrectly? src/main.rs outputs
$  cargo run
    Finished dev [unoptimized + debuginfo] target(s) in 0.01s
     Running `target/debug/rstar-boilerplate`
thread 'main' panicked at /rustc/cc66ad468955717ab92600c770da8c1601a4ff33/library/core/src/ops/arith.rs:346:1:
attempt to multiply with overflow
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

Rust code that resulted in the above output

use rstar::Point;

#[derive(Clone, Copy, Debug, PartialEq)]
struct Data {
    coordinates: [i32; 18],
}

impl Point for Data {
    type Scalar = i32;
    const DIMENSIONS: usize = 18;

    fn nth(&self, index: usize) -> Self::Scalar {
        self.coordinates[index]
    }

    fn nth_mut(&mut self, index: usize) -> &mut Self::Scalar {
        &mut self.coordinates[index]
    }

    fn generate(mut generator: impl FnMut(usize) -> Self::Scalar) -> Self {
        Data {
            coordinates: [
                generator(0),
                generator(1),
                generator(2),
                generator(3),
                generator(4),
                generator(5),
                generator(6),
                generator(7),
                generator(8),
                generator(9),
                generator(10),
                generator(11),
                generator(12),
                generator(13),
                generator(14),
                generator(15),
                generator(16),
                generator(17),
            ],
        }
    }
}

fn main() {
    let mut tree = rstar::RTree::new();
    tree.insert(Data {
        coordinates: [
            30, 30, 62, 30, 31, 30, 20, 12, 30, 80, 40, 132, 28, 78, 140, 139, 195, 67,
        ],
    });
    tree.insert(Data {
        coordinates: [
            40, 9, 9, 144, 136, 149, 148, 140, 198, 36, 50, 167, 179, 234, 38, 2, 103, 38,
        ],
    });
    tree.insert(Data {
        coordinates: [
            38, 38, 38, 6, 2, 3, 155, 61, 61, 195, 155, 15, 70, 134, 158, 126, 94, 63,
        ],
    });
    tree.insert(Data {
        coordinates: [
            154, 154, 138, 179, 121, 75, 143, 31, 7, 67, 11, 3, 113, 113, 65, 65, 73, 65,
        ],
    });
    tree.insert(Data {
        coordinates: [
            221, 215, 209, 115, 210, 198, 224, 236, 111, 6, 7, 7, 85, 92, 203, 197, 36, 44,
        ],
    });
    tree.insert(Data {
        coordinates: [
            176, 240, 176, 176, 112, 241, 240, 240, 192, 44, 44, 12, 206, 204, 142, 4, 44, 2,
        ],
    });
    tree.insert(Data {
        coordinates: [
            212, 218, 202, 70, 70, 23, 23, 23, 1, 230, 250, 55, 30, 23, 60, 60, 92, 16,
        ],
    });
}

I'm actually working with fixed-size arrays of u8s, but I'm using i32 because that's the smallest size supported by rstar for integers.

I'm actually working with fixed-size arrays of u8s, but I'm using i32 because I think that's the smallest size supported by rstar for integers that won't cut off any values in a u8.

rstar uses a fold to calculate the area of the envelope (an AABB) of the geometry (In your case, the 18-dimensional point you're trying to insert on line 78. Fold uses an accumulator and a multiplication function:
diag.fold(one, |acc, cur| {
    max_inline(cur, zero) * acc
})

During the insertion operation on line 78 of your code, you can see the problem:
Acc: 359131136 Cur: 68.
Multiplying acc with cur overflows i32. That's a panic in debug builds.

Ah, because the product, 24,420,917,248, is larger than the max i32 value, 2,147,483,647.

If each coordinate is a u8, the max possible value when multiplying them all together is 255^numCoordinates, which is currently 18, but the number of coordinates could easily double, or triple, for my use case.

So the maximum possible product currently is 255^18 = 2.078371831996e43, which I don’t even think the maximum unsigned integer size, u128, can support, since I think that’s approximately 3.402823669209e38.

Is calculating the area of the bounding box required to use an R-tree? I’m wondering if it’s possible to write an implementation that avoids doing this calculation altogether to avoid running the risk of overflow.

Alternatively, would checking for overflow before the multiplication, and setting the product to u128::MAX if there would be an overflow, result in any weird or unexpected behavior? I’m also considering that approach.

During the insertion operation on line 78 of your code, you can see the problem:
Acc: 359131136 Cur: 68.
Multiplying acc with cur overflows i32. That's a panic in debug builds.

Also, how were you able to see the current and total values in fold?
I tried adding
        diag.fold(one, |acc, cur| {
            std::println!("acc: {}, cur: {}", acc, cur);
            return max_inline(cur, zero) * acc;
        })

to ~/.cargo/registry/src/index.crates.io-6f17d22bba15001f/rstar-0.11.0/src/aabb.rs, but that gave me this error.
ailed to resolve: use of undeclared crate or module `std`
use of undeclared crate or module `std`rustc

Ah, because the product, 24,420,917,248, is larger than the max i32 value, 2,147,483,647.
If each coordinate is a u8, the max possible value when multiplying them all together is 255^numCoordinates, which is currently 18, but the number of coordinates could easily double, or triple, for my use case.
So the maximum possible product currently is 255^18 = 2.078371831996e43, which I don’t even think the maximum unsigned integer size, u128, can support, since I think that’s approximately 3.402823669209e38.
Is calculating the area of the bounding box required to use an R-tree? I’m wondering if it’s possible to write an implementation that avoids doing this calculation altogether to avoid running the risk of overflow.
Alternatively, would checking for overflow before the multiplication, and setting the product to u128::MAX if there would be an overflow, result in any weird or unexpected behavior? I’m also considering that approach.

During the insertion operation on line 78 of your code, you can see the problem:
Acc: 359131136 Cur: 68.
Multiplying acc with cur overflows i32. That's a panic in debug builds.

Hmm... where does the current value of 68 come from? I don't see any elements in https://github.com/hamirmahal/rstar-i32/commit/aef70723a73ca76c71387ef93d825b7afcf5a0ea#diff-42cb6807ad74b3e201c5a7ca98b911c5fa08380e942be6e4ac5807f8377f87fc with the value 68.
Also, how were you able to see the current and total values in fold?
I tried adding
        diag.fold(one, |acc, cur| {
            std::println!("acc: {}, cur: {}", acc, cur);
            return max_inline(cur, zero) * acc;
        })

to ~/.cargo/registry/src/index.crates.io-6f17d22bba15001f/rstar-0.11.0/src/aabb.rs, but that gave me this error.
ailed to resolve: use of undeclared crate or module `std`
use of undeclared crate or module `std`rustc

Thanks for the detailed response.

Ok, I see your example:
https://github.com/hamirmahal/rstar-i32/commit/aef70723a73ca76c71387ef93d825b7afcf5a0ea#diff-42cb6807ad74b3e201c5a7ca98b911c5fa08380e942be6e4ac5807f8377f87fc
So you are using 18-D coordinates.
Just to ask a silly question: Did you really intend to have a single coordinate with 18 dimensions, or were you trying to have something like 9 2D (XY) coordinates?

Did you really intend to have a single coordinate with 18 dimensions, or were you trying to have something like 9 2-D (XY) coordinates?

This is correct.

I'm actually trying to find the element in my dataset with the closest Hamming distance to some input.
The things I'm comparing currently have 18 bytes, hence the 18 coordinates that can each be as large as 255, and it looks like we may need to increase the number of bytes we store to 32, or possibly even more.
Do you think R-trees are a suitable data structure for this purpose?

Do you think R-trees are a suitable data structure for this purpose?

Well, I can say with certainty that this particular R-Tree implementation is apparently not currently suitable for this purpose. 🤣
But more seriously... I've never worked with hamming distance. The definition I searched up was:

While comparing two binary strings of equal length, Hamming distance is the number of bit positions in which the two bits are different.

So, hamming distance is about bitwise distance - not euclidean distance.
In other words:
hamming_distance(0b1000, 0b0000) == 1
hamming_distance(0b1000, 0b0111) == 4

But with typical numeric distance we get a very different answer:
numeric_distance(0b1000, 0b0000) == 8
numeric_distance(0b1000, 0b0111) == 1

So intuitively, I don't understand how you'd use an rtree, which deals with euclidean numeric distance to efficiently compute hamming distance.

Hmm. Hamming distance satisfies the triangle inequality, so I think it's possible to use R[*]-trees, but I have no idea how we're going to make it work for rstar…

Do you think R-trees are a suitable data structure for this purpose?

Well, I can say with certainty that this particular R-Tree implementation is apparently not currently suitable for this purpose. 🤣

Ha!

But more seriously... I've never worked with hamming distance. The definition I searched up was:

While comparing two binary strings of equal length, Hamming distance is the number of bit positions in which the two bits are different.

So, hamming distance is about bitwise distance - not euclidean distance.
In other words:
hamming_distance(0b_1000, 0b_0000) == 1  // Near!
hamming_distance(0b_1000, 0b_0111) == 4  // Far!

But with typical numeric distance we get a very different answer:
numeric_distance(0b_1000, 0b_0000) == 8  // Far!
numeric_distance(0b_1000, 0b_0111) == 1  // Near!

That all sounds correct.

So intuitively, I don't understand how you'd use an rtree, which deals with euclidean numeric distance, to efficiently compute hamming distance.

I ended up doing
impl PointDistance for Data {
    fn distance_2(&self, point: &[f32; 18]) -> f32 {
        let hamming_distance: f32 = self
            .hash
            .as_slice()
            .iter()
            .zip(point)
            .map(|(l, r)| {
                // cast l and r to u8, because we know that the values are in the range [0, 255].
                let l = *l as u8;
                let r = *r as u8;
                (l ^ r).count_ones() as f32
            })
            .sum();

        // We must return the squared distance!
        hamming_distance * hamming_distance
    }
}

but it seems to be quite computationally expensive, and not very efficient.
I used f32s instead of i32s, even though I'm only dealing with u8s, because rstar doesn't support u8s out of the box, and because I didn't get attempt to multiply with overflow when using f32s.

What's the hash for?

Oh, so I'm ideally trying to find the closest Hamming distance between &self's hash, which is just 18 bytes, and every other hash in my dataset.

Hm. If you're using the default Hash impl, you're using a very high-quality (and expensive) hashing algorithm, which I would imagine is complete overkill in this case.

Ah, I see… I’ll look into some different approaches.

https://nnethercote.github.io/2021/12/08/a-brutally-effective-hash-function-in-rust.html FxHash will certainly be faster (https://crates.io/crates/fxhash)

Do we support bnum ?  It supports a u256, which should suffice for above calc?

I think before we go ahead and make this crate more difficult to maintain, it should be established whether R* trees are actually suitable to query Hamming distances.
While it could be innovative cross-pollination between different areas of mathematics, I am somewhat doubtful that the geometric intuitions underpinning the construction of R* trees transfer over to code spaces. Generally, there exist a lot of metric spaces which are decidedly weird compared to the two- or three-dimensional Euclidean space our intuition is still based on even when alternative metrics like Manhattan are used.
So, I think the first step would be to just modify the source of rstar in local fork to try to hack around the limits of the current design, e.g. use saturating arithmetic if that is helpful or use an high (e.g. bnum) or arbitrary (e.g. num-bigint) precision number library. Then this hacky local fork can be used to figure out if R* trees can be useful for the given problem and based on these experiences we can decide whether and how to extend this library to support this use case.
(But if the changes are too extensive, the answer might still be no as as maintainers, saying no is often what we need to do to keep complexity in check. We have also have represent the interests of our current user base which I guess is mostly GIS, games and then some simulation stuff in order popularity.)
Personally, my first guess when reading the original problem would be to look into Levenshtein automata which are used for typo resistant search, i.e. to find a matching term with the fewest possible edits away from the query term.

Oh, I don't think anyone was actually proposing a change. Certainly when I said "make it work" I didn't mean it in the sense of modification.

@hamirmahal I think you can get it working by just converting the [u8; 18] slice into a [f64; 18] slice before storing it in the hash variable.  f64 or f32, with float should support the range you need.  There'll be some loss in precision in that calculation, but I think it's only used for re-balancing of the r-tree that is constructed (and so must still work, with possibly poorer performance).

@rmanoka I'll give that a look. Thanks for the consideration.

@rmanoka I'll give that a look. Thanks for the suggestion.


Minor feature - queue viewing

I would like to work on this feature, displaying the queue list on a side panel. Any advices?
I think I need to work on the player.queue_pool array. Displaying its content and sorting it on 'add_to_queue' updates.

This was added in https://github.com/benkaiser/node-music-player/commit/4dacbfb66e3e09722324cfc122d58f875e34756a


Add client-go 3.0 beta to compatibility matrix

@mbohlool @lavalamp ptal. Thanks.

This change is

LGTM. Also need changelog entries?


win32 wheel missing for python 3.7

win32 wheels available for python 3.5 and 3.6 but not for 3.7.
May you include it in build process?
Great library thanks!

Oh, I don't know why it's not on PyPI. In the mean time, you can grab it from the releases page: https://github.com/urschrei/simplification/releases/tag/v0.4.2


Type hints in pgvector document store updated for 3.8 compability

Without this fix code can not be run on Py3.8 although it's in list of supported versions

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


Search by logical references does not work for AuditEvent entity parameter

Describe the bug
A logical reference search using the entity parameter does not find an existing AuditEvent record under the HAPI base R4 sandbox.  None of the search approaches documented in the steps to reproduce find the existing record.
Are logical reference searches supported?  Does the referenced entity have to exist in the system?
To Reproduce
Steps to reproduce the behavior:

The resource which is being searched can be retrieved with a FHIR read: http://hapi.fhir.org/baseR4/AuditEvent/9102168.  Or, find the resource among others in a Bundle: http://hapi.fhir.org/baseR4/AuditEvent?_format=xml&_sort=-date&_count=100
The following search attempts do not find the record above:
Search on value only: http://hapi.fhir.org/baseR4/AuditEvent?entity:identifier=ABCDEF
Search on code system and value: http://hapi.fhir.org/baseR4/AuditEvent?entity:identifier=http://terminology.hl7.org/CodeSystem/v2-0203|ABCDEF
Search on code system and code: http://hapi.fhir.org/baseR4/AuditEvent?entity:identifier=http://terminology.hl7.org/CodeSystem/v2-0203|SNO

Expected behavior
The logical reference search will find the record.
Any of the token search approaches documented by http://hl7.org/fhir/R4/search.html#token should work.
Also, see search by reference: http://hl7.org/fhir/R4/search.html#reference
Environment (please complete the following information):

HAPI Server Version (used for examples above) - 6.5.12-SNAPSHOT/e500b23fe6/2023-04-06
HAPI FHIR Version: 4.0.1
OS: Hosted
Tested with Postman client
HAPI Server Version used for implementation: 6.4.4

As per https://chat.fhir.org/#narrow/stream/179167-hapi/topic/searching.20for.20subject.3Aidentifier/near/286159954, an :identifier modifier search is not implemented under HAPI.  However, there are some JIRA defect tickets that indicate it should be working under R4 -- see https://github.com/hapifhir/hapi-fhir/issues/1001.  Is this type of search intended to work or not?


Attempting to fix 3.2.0 failed build

Investigating #71

@nickcolley The tests seem to be passing on this PR now that @testing-library/react has been updated. After looking around a little online, it looks like it may have also been fixed in React 16.9.0 as part of some test renderer updates: https://github.com/facebook/react/blob/master/CHANGELOG.md#react-test-utilities-and-test-renderer
Are you happy to merge and close #71?

Sure thing thanks for helping out :)


Config file for govendor

Is there a way to avoid having to enter in my username and password every time that i do a govendor sync. Maybe have the cli prompt for username and password and store the info or create an oauth token that is the stored in the config. Similar to the way that hub cli does it? Would such functionality be accepted if a pr was made?

Such a PR would probably be accepted.

Great. thanks @kardianos I am using some vendored dependencies that are private and it is so time consuming to type in username and password 40 times each time I do govendor sync.

I guess I will work on that tonight.

Does your private repo source not support stored SSH keys?  If you're using github, even a private enterprise version, you can simple generate an SSH key and point your local git at it.  That obviates the need for the ID and password entirely.

@jjeffrey-bolste Were you able to setup SSH keys for your repo? Did that solve your problem?

So i set it up and it is not working. It might be because I have multiple ssh keys and it does not try them all...
Not sure though.

Make sure the keys are loaded into ssh agent with ssh-add (?)

Is there really no way to specificy username/password programatically? Especially in CI using a auth token is easier than managing a SSH keypair. I don't need/want a config but I can't even find a env variable or something to specify user/password to use for https.

There definitely is a way to do so.  I doubt that it's a very high priority, though, since most people just use ssh keys instead.


A script to create a Kani release bundle.

Description of changes:
This is an initial script to create a Kani release bundle. It's written it Rust instead of Bash because why not, it's easier to make certain things more robust that way.
Resolved issues:
Resolves #939
Call-outs:

We're not bundling cbmc-viewer because there are issues with potential portability between Python version on the customer machine. (We'll pip install this during first-time setup.)
We're pulling the CBMC binaries from PATH, instead of from a specific pinned CBMC version. This is to avoid putting CBMC versions in more places. There's a big comment about it. We'll invert this in a later refactoring/PR.
This isn't currently tested really - I'm making this PR now, and we'll test for real it when I follow up with the next PR which will create a "release" InstallType in cargo-kani and thus allow everything (except viewer, next step there) to run out of a release bundle instead of out of a dev repo checkout.

Testing:

How is this change tested? manually for now, follow-up PR will add to CI

Is this a refactor change? no

Checklist

[x] Each commit message has a non-empty body, explaining why the change was made
[x] Methods or procedures are documented
[x] Regression or unit tests are included, or existing tests cover the modified code
[x] My PR is restricted to a single feature or bugfix

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 and MIT licenses.

Can you please add some test coverage in our CI? Ideally we should be able to run our full regression using the bundled kani but for now, we can just have some sanity checks to ensure that the bundled kani and cargo-kani works.

So I'm working on the next step which is a release InstallType, and as part of that I've built a Dockerfile to (for now manually) do the first-time setup stuff. I could add that to CI and get it to run the tests.
I was planning on that being a separate PR after this one was merged. Would you prefer that I push it into this PR?

On a different note, I was also wondering if we should make the an cbmc-viewer an optional dependency.

I don't think so, it's such a small thing. There are complications with Python, but we have those to run our script (which needs colorama anyway) too. If we ported the renderer to Rust later, then maybe there'd be a purpose, but only a tiny one: anyone who didn't want a Python installation around could skip it.

get it to run the tests.

Ugh, compiletest has a lot of baked assumptions about running in a repo, etc. Running our existing tests on a release bundle is going to be a lot of work.

I think we should add a minimum test coverage to this PR. We should at least do the following:

Run kani-make-release.
Unpack the contents of the generated tar ball.
Run a dummy cargo kani test.

3. Run a dummy cargo kani test.

Sure, to do this, I'll need the InstallType stuff, so I'll fold that into this PR then.

I'm not super happy with putting the Dockerfile at the root, but moving it elsewhere comes with issues w.r.t. copying tests into it or whatever.
I could maybe rename it to Dockerfile.internal_release_test or something if you think that'd be an improvement?

I'm not super happy with putting the Dockerfile at the root, but moving it elsewhere comes with issues w.r.t. copying tests into it or whatever.

Can't you just move/symlink it as part of the workflow?

Can't you just copy/symlink it as part of the workflow?

A reasonable idea. Keep it under something like tests/releasebundle/ maybe?

I was thinking scripts/ci/ because it's CI-related. Maybe create a "release" (or any name) folder there?
Would like to avoid putting anything that is not a test under tests/ :/

I've updated gitignore to include the tar.gz files. I've also factored out "prebundle checks" into a separate function that:

Ensures we've build Kani in release mode before doing anything.
Checks for cbmc, again before we ever start bundling.

This should reduce the odds of failing during a bundle creation (and leaving the directory still in existence) to close to nothing, hopefully alleviating your concern?

Sure. We can change it later if this becomes a problem. Thanks


Prevent crashes on serializing empty beans

Issue #, if available:
#259
Description of changes:
Sometimes when serializing AWS SDK-defined classes we get a Jackson serialization error for empty beans. The long term fix is to build a proper serializer for these classes, but at the very least for now we shouldn't crash when encountering them.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Codecov Report

Merging #293 (137c3f3) into master (5143932) will increase coverage by 0.00%.
The diff coverage is 100.00%.

@@            Coverage Diff            @@
##             master     #293   +/-   ##
=========================================
  Coverage     58.86%   58.86%
  Complexity     1202     1202
=========================================
  Files           131      131
  Lines          5056     5057    +1
  Branches        588      588
=========================================
+ Hits           2976     2977    +1
  Misses         1807     1807
  Partials        273      273

Impacted Files
Coverage Δ

...n/java/com/amazonaws/xray/entities/EntityImpl.java
87.26% <100.00%> (+0.04%)
: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 5143932...137c3f3. Read the comment docs.


Potentially unsafe subprocess execution (shell=True)

Hello 👋 - Any particular reason that subprocess needs to be run with Shell=True?
An example:
https://github.com/OrkoHunter/pep8speaks/blob/837643bb95c18a5364cd0539b0f8edaeb3813a76/pep8speaks/helpers.py#L234
Shell=True is a more dangerous way of invoking subprocess that exposes you to potential command injection attacks. If you're not using any shell specific features (e.g. |), changing it to shell=False is a pretty easy fix.

Related https://github.com/OrkoHunter/pep8speaks/issues/28

I think the answer is basically split the cmd string: https://github.com/OrkoHunter/pep8speaks/blob/30af5bf0de1a2bfdf35b0a76bf63c70486c12c69/pep8speaks/helpers.py#L231 and pass cmd as a list to popen , then you can set shell=False and you're done.


add @data-ui/radial-chart

This PR adds the @data-ui/radial-chart package which supports simple 🍰  (pie) and 🍩  charts.

Coverage increased (+1.9%) to 80.57% when pulling 86a1b0ff0632b20f60514b17e25be14ff1fa4694 on chris--radial-chart into 3553098cb8dd09fd40f405c8ef1c21201691b9f5 on master.

tests are broken because of package deps, will merge and cut new releases.


WIP -- Add Github Webhook provider

What did you implement:
Adds a Github Webhook provider. This is a new model for a provider that I call a "transformation" provider. It's responsible for transforming a single event into one or more additional events. I think it's particularly useful for existing webhook providers, such as Github, as we can turn them from HTTP events into a custom event.
It might be useful by way of an example. Let's imagine three different people that want to handle an pull_request event:

A VP Eng that wants to track the total number of pull requests opened and closed across all company repos;

A DevOps engineer that wants to kick off a deploy job for a certain repo whenever there's a merged PR; and

A Data Engineer that wants to dump all events into a database for ad-hoc querying.

In a current world with Event Gateway (or other systems), each user would need to configure a separate HTTP endpoint and webhook in Github to subscribe to these actions. Additionally, each of them would need to handle verifying the webhook and responding properly.
With this transformation function, an admin could set up a single HTTP endpoint that had this transformation subscribed to it.
When this endpoint received a pull_request event from the serverless/event-gateway repo, it would do three things:

Validate the event's signature;

Emit the following three events into the Gateway:

A custom event with type github
A custom event with type github.pull_request
A custom event with type github.event-gateway.pull_request

Return a 2XX response to Github.

Now that these events are inside the Event Gateway, it's much easier to add custom logic to events.
For our examples, the VP Eng's serverless.yml looks like this:
functions:
  prTracker:
    handler: index.handler
    events:
      - eventgateway
          type: "github.pull_request" # Gets all PRs across all company repos

The DevOps Engineer's serverless.yml looks like:
functions:
  deployer:
    handler: index.handler
    events:
      - eventgateway
          type: "github.event-gateway.pull_request" # Gets PR events for event-gateway repo only.

The Data Engineer's serverless.yml looks like:
functions:
  tracker:
    handler: index.handler
    events:
      - eventgateway
          type: "github" # Gets all events across all repos.

Plus, it's a very low barrier when a new use case comes up. Want to dump all issues for 2 repos into Slack? Use this:
functions:
  issuesToSlack:
    handler: index.handler
    events:
     # Receives all "issues" events from serverless/serverless and serverless/event-gateway
      - eventgateway
          type: "github.serverless.issues"
      - eventgateway
          type: "github.event-gateway.issues"

How did you implement it:
This is still just a proposal so some elements need to be ironed out.
Two specific notes:

This part is giving me trouble as it's hard to reconstitute the event.Body into an HTTPEvent struct once it's been dumped to JSON. I was wondering about removing this line and passing an Event object to the Call() method for each provider. Usually a provider will need to serialize it anyway, but it would be nice to be able to work with the event if needed.

I don't have a great way of knowing what space the Event is in within the context of a Call() method for the provider. Also, it'd be great to be able to emit an event into a space without having to make an HTTP call.

How can we verify it:
WIP
Todos:

[ ] Write tests
[ ] Write documentation
[ ] Fix linting errors
[ ] Make sure code coverage hasn't dropped
[ ] Provide verification commands / resources
[ ] Enable "Allow edits from maintainers" for this PR
[ ] Update the messages below

Is this ready for review?: NO
Is it a breaking change?: NO

@alexdebrie nice work!
The fact that, I don't have to configure multiple webhooks for each event, yet I have the granularity of individual events - is pretty slick.
Also, it is performant as it reduces the overhead of multiple signature validation and signature calc. in case of multiple events.
Another use case for such a provider will be Stripe Events.


Icon request for HTTP

Description
Not sure which specific icon could suit this request, but having it would be nice!
To be Requested

I tried a couple of different things and I feel like just "HTTP" text would be the best:

Looks great!

Will be available in version 1.4


TaskRun creation fails, created from PipelineRun with TaskRunSpec

Expected Behavior
That I can declare TaskRunSpecs in the PipelineRun and TaskRun with the given spec is created.
Example:
piVersion: tekton.dev/v1beta1
kind: PipelineRun
metadata:
  generateName: git-clone-ssh-
spec:
  params:
  - name: git-url
    value: git@github.com:jlpettersson/myapp.git
  pipelineRef:
    name: pipeline-with-git-clone
  taskRunSpecs:
  - pipelineTaskName: git-clone
    taskPodTemplate:
      volumes:
      - name: ssh-auth
        projected:
          defaultMode: 0400
          sources:
          - secret:
              name: github-known-hosts
          - secret:
              name: github-private-key

As described in documentation about TaskRunSpec (However, there were errors in doc also, fixed in https://github.com/tektoncd/pipeline/pull/2681)
Actual Behavior
TaskRun creation fails with:
status:
        conditions:
        - lastTransitionTime: "2020-05-23T17:03:00Z"
          message: 'failed to create task run pod "git-clone-ssh-n2lc8-git-clone-jrbjf":
            Pod "git-clone-ssh-n2lc8-git-clone-jrbjf-pod-hdww2" is invalid: spec.containers[0].volumeMounts[0].name:
            Not found: "ssh-auth". Maybe missing or invalid Task g/git-clone-ssh'
          reason: CouldntGetTask

/kind bug

@jlpettersson does the volume ssh-auth definitely exist when this is running? the error seems to be implying it doesn't but maybe the error is misleading?

@jlpettersson does the volume ssh-auth definitely exist when this is running? the error seems to be implying it doesn't but maybe the error is misleading?

I created a PR as well. There was a missing piece in the implementation.


Export buttons stopped working

They should not depend on the result display, so there is no reason for them to not firing any requests any more. Please fix it.

I sincerely hope that I did not break anything server side. I do remember that you mentioned that I erroneously wrap the results in the standard wrap format, but since than this was fixed. And judging by the out-coming HTTP requests, the client itself makes no attempt to get the exports anyway.

It seems that client just breaks when it receives the new result format. This might explain this. So please only verify that after @KataBoku fixes the result display, that the export starts to work again.

Waits for #112 .


Bring currentStake to top level by requiring as input to punish()

https://github.com/erasureprotocol/erasure-protocol/blob/0271f9b35b3027c9294535d6a51029e76e5bab18/contracts/modules/Griefing.sol#L54

Fixed with https://github.com/erasureprotocol/erasure-protocol/pull/169/commits/644bcd482a7b922800943b5e1376a626b0616573

Fixed with https://github.com/erasureprotocol/erasure-protocol/pull/169/commits/644bcd482a7b922800943b5e1376a626b0616573


Usage in React Native?

Is this the correct module to implement braintree within a React Native client? Or would braintree_node be the correct module?

We don't officially support React Native; our SDK is currently optimized for the browser and its security policies and may not function correctly outside of them.
However, there are some open-source, third-party projects you can use if you want to move forward with a React Native integration. Note, however, that we will not be able to provide support should you run into any issues.


JFXDatePicker floating label

I am using version 1.9.1 of JFoenix, and when I use JFXDatePicker the label in some applications does not float and in others an exception is thrown.
In the applications where an exception is thrown, the lable floats but if it is not selected with a mouse the label stays in the same place where the date was filled

Hello,
Can you provide a sample example to demonstrate the issue?
Regards,

file.css
.text-field, .text-area, .combo-box{     -fx-background-color: #fafafa;     -jfx-focus-color:#469962;     -jfx-unfocus-color:#a7a7a7;     -jfx-label-float: true; }

Sorry finally figured out the issue.The problem was I was styling its's root pane which is a border pane like this
BorderPane {
-fx-background-color: #F2F2F2;
-fx-background-insets: 0;
}
removed the styling and the date picker is working again. The regular date picker was working fine though.

Hello,
were not able to reproduce the issue.
JFoenix 1.10.0 is out, can you re-validate the issue using the latest version?

I m using the latest version

If you can provide a full example to demonstrate the issue, it would be appreciated.

If I use the "Pref Height = USE_COMPUTED_SIZE" The exception does not appear, but if I put any value for example "Pref Height = 30.0" .The exception appears
Example where the exception appears
<JFXDatePicker layoutX="58.0" layoutY="28.0" maxHeight="25.0" maxWidth="1.7976931348623157E308" minHeight="0.0" minWidth="0.0" prefHeight="25.0" prefWidth="100.0" promptText="asdf" />
Example where the exception does not appear
<JFXDatePicker layoutX="58.0" layoutY="28.0" maxHeight="25.0" maxWidth="1.7976931348623157E308" minHeight="0.0" minWidth="0.0" prefWidth="100.0" promptText="asdf" />

If anyone else is looking to get the JFXDatePicker's label to float, see #603.


How to get a post based on location or hashtag ??

How to get a post based on location or hashtag ??

See LocationFeed and TagFeed.


Uninstaller deletes files excessively

TL;DR Don't delete stuff that doesn't need to be, please!
Rename/move it if you must, but don't delete!
So, I was having trouble with my CSS and I wasn't sure if my own customization userChrome was interfering with shadowfox (This has happened before and turned out to be a SF bug)... So I used the uninstaller, so I could start from vanilla FF.... and it not only removed the shadowfox CSS files, but deleted the entire ShadowFox_Customization directory.... WHICH HAD ALL MY BACKUPS IN IT. (Yes, I'm a good boy and have a backup from earlier, on another drive, so I only lost a few days work, but still....)
Uninstalling ShadowFox does not imply deleting user-created files... I think that routine could do with some attention. It's entirely possible I've missed something but, I don't see any need to touch that directory at all. Just remove (or better yet, rename!) the userChrome and userContent CSS that was created by the installer in the first place should be enough, no?
Thanks man I love your work but this was a SERIOUS bummer. I'm just glad that the uninstaller didn't delete the .backup files it created when I had updated while testing, so I still have some remnants of my old work.

I thought I'd try and be helpful and see if I could find the offending code and it looks like you already fixed it and I have an old version of the installer
https://github.com/SrKomodo/shadowfox-updater/commit/57a71c88b64c131648b60b2bd4ff649dd803f953
Shoot me. Feel free to close this if it's fixed and I'm a doofus. Sorry!

v2.2.0 now checks for updates and notifies you if there is a new version available.

Awesome work man thanks!


permission

Where else have you looked for answers to this question?
discord
Share your question with as much detail as possible.
How can I make the permission not appear in rewards, but apply
rewards:
items:
==: org.bukkit.inventory.ItemStack
v: 3463
type: DIAMOND
money: 1000
quest-points: 10
exp: 10
permissions:
'essentials.warps.goldminer'
Sorry for the inconvenience, I've been trying for days to find a way

Details list override