doc: VXLAN in IPv6 is only supported for kernel versions >=4.19.1 or redhat kernel version >= 4.18.0

Description

VXLAN in IPv6 is only supported for kernel versions >=4.19.1 or redhat kernel version >= 4.18.0
Related issues/PRs
fixes https://github.com/projectcalico/calico/issues/7251 https://github.com/projectcalico/calico/issues/6273 https://github.com/projectcalico/calico/issues/6877
PR links https://github.com/projectcalico/calico/pull/7195
Todos

[ ] Tests
[ ] Documentation
[ ] Release note

Release Note

TBD

Reminder for the reviewer
Make sure that this PR has the correct labels and milestone set.
Every PR needs one docs-* label.

docs-pr-required: This change requires a change to the documentation that has not been completed yet.
docs-completed: This change has all necessary documentation completed.
docs-not-required: This change has no user-facing impact and requires no docs.

Every PR needs one release-note-* label.

release-note-required: This PR has user-facing changes. Most PRs should have this label.
release-note-not-required: This PR has no user-facing changes.

Other optional labels:

cherry-pick-candidate: This PR should be cherry-picked to an earlier release. For bug fixes only.
needs-operator-pr: This PR is related to install and requires a corresponding change to the operator.

This docs contribution has been moved to https://github.com/tigera/docs/pull/515. Closing here.


Proposal: lack of documentation

There is no documentation right now, may be it's time to add some wiki or docs?

Added docs for NodeServices in the README.md file: https://github.com/aspnet/JavaScriptServices/tree/master/src/Microsoft.AspNetCore.NodeServices
Will do the same for SpaServices soon.

Added docs for SpaServices at https://github.com/aspnet/JavaScriptServices/blob/master/src/Microsoft.AspNetCore.SpaServices/README.md

I've also updated the repo's root README.md file to describe the repo generally and link to specific docs for NodeServices and SpaServices.
So, although there are still other places that more docs could be added, the level of documentation is good now. I'm closing this issue as there's no longer a general lack of docs. We can still add more docs elsewhere as needed.


Add dockerfile

Add Docker support. This file will download dependencies and install shiori inside an image. This is extremely useful for server maintainers, because it's secure and easy.
Run docker build -t shiori . to build the image
Run docker run -p 8080:8080 -d --rm --name shiori shiori to start a docker container
Run docker exec shiori shiori <COMMAND> to interact with the container

#27 and #11 trying to solve the same problem.

As written in #27: I suggest to use multi stage builds instead: https://docs.docker.com/develop/develop-images/multistage-build/#name-your-build-stages. There's no need for a full "go"-aware alpine image for that. The link contains a suggestion about how to build go projects with that docker feature.

I don't know much about Go. And I made a dockerfile for my own needs, and thought I would share it with you. But I do not know enough about Go to improve it.
Please see #27 for a better implementation


Failed to create esm bundled application

What version of Remix are you using?
2.0.0
Are all your remix dependencies & dev-dependencies using the same version?

[X] Yes

Steps to Reproduce

Create a new app with pnpx create-remix@latest test.
In remix.config.js add serverDependenciesToBundle: [/.*/]
Run pnpm run dev.

Expected Behavior
The application should start.
Actual Behavior
The application actually fails while trying to require 'http' from node.
It looks like the package @remix-run/node does not contain any valid esm export. I assume it does fallback to commonjs instead and from there it takes @remix-run/web-fetch in commonjs as well.
Not sure if this is the correct assumption.
markusw@xxx:/tmp/test (main)$ pnpm run dev

> test@ dev /tmp/test
> remix dev --manual

 💿  remix dev

 info  building...
 info  built (797ms)
Error: Dynamic require of "http" is not supported
    at file:///tmp/test/build/index.js?t=1695049617985.849:11:9
    at node_modules/.pnpm/@remix-run+web-fetch<EMAIL_ADDRESS>(file:///tmp/test/build/index.js?t=1695049617985.849:4452:16)
    at file:///tmp/test/build/index.js?t=1695049617985.849:17:50
    at node_modules/.pnpm/@remix-run+node@2.0.0_typescript<EMAIL_ADDRESS>(file:///tmp/test/build/index.js?t=1695049617985.849:5476:20)
    at file:///tmp/test/build/index.js?t=1695049617985.849:17:50
    at node_modules/.pnpm/@remix-run+node@2.0.0_typescript<EMAIL_ADDRESS>(file:///tmp/test/build/index.js?t=1695049617985.849:9751:20)
    at file:///tmp/test/build/index.js?t=1695049617985.849:17:50
    at file:///tmp/test/build/index.js?t=1695049617985.849:20675:27
    at ModuleJob.run (node:internal/modules/esm/module_job:194:25)
^C ELIFECYCLE  Command failed.

If the assumption above is correct (ESM exports missing) I will try to create a PR which addresses the issue.
Other than that I have no clue why we see commonjs for this in the server bundle if the output is set (and defaults) to ESM.

The 'serverDependenciesToBundle' attribute should not match all.

Was anyone able to figure this out? I'm facing the same issue.

Not yet

Also ran into this on Remix 2.0.1 when building to deploy to AWS Lambda, using either @remix-run/architect or remix-aws. This error occurred when using remix-aws:
2023-10-23T13:31:32.103Z	undefined	ERROR	Uncaught Exception 	{
    "errorType":"Error",
    "errorMessage":"Dynamic require of \"path\" is not supported",
    "stack":[
        "Error: Dynamic require of \"path\" is not supported",
        "    at file:///var/task/ui/build/index.mjs:11:9",
        "    at node_modules/source-map-support/source-map-support.js (file:///var/task/ui/build/index.mjs:1082:76)",
        "    at file:///var/task/ui/build/index.mjs:17:50",
        "    at<EMAIL_ADDRESS>(file:///var/task/ui/build/index.mjs:9592:29)",
        "    at file:///var/task/ui/build/index.mjs:17:50",
        "    at file:///var/task/ui/build/index.mjs:31229:27",
        "    at ModuleJob.run (node:internal/modules/esm/module_job:194:25)"
    ]
}

or this one when using @remix-run/architect:
2023-10-21T02:21:26.578Z	undefined	ERROR	Uncaught Exception 	{
    "errorType":"Error",
    "errorMessage":"Dynamic require of \"node:crypto\" is not supported",
    "stack":[
        "Error: Dynamic require of \"node:crypto\" is not supported",
        "    at file:///var/task/ui/build/index.mjs:11:9",
        "    at<EMAIL_ADDRESS>(file:///var/task/ui/build/index.mjs:87308:19)",
        "    at file:///var/task/ui/build/index.mjs:17:50",
        "    at<EMAIL_ADDRESS>(file:///var/task/ui/build/index.mjs:87510:34)",
        "    at file:///var/task/ui/build/index.mjs:17:50",
        "    at file:///var/task/ui/build/index.mjs:107950:32",
        "    at ModuleJob.run (node:internal/modules/esm/module_job:194:25)"
    ]
}

Workaround was to bundle the server module as CommonJS by removing "type": "module" from package.json and modifying remix.config.js:
module.exports = {
  ...
  serverBuildPath: "build/index.cjs",
  serverModuleFormat: "cjs",
}

which is not ideal, but works for us for now.

...that is, I thought it worked for us, but instead it results in the issue described here: https://github.com/remix-run/remix/discussions/7761

This PR repros the bug with a failing integration test: #7779
What else needs to happen for a https://github.com/remix-run/remix/labels/bug%3Aunverified to become a https://github.com/remix-run/remix/labels/bug, and what can I do next to help the PR move along?

I tried working on it for a few more hours, I was able to hack remix.run to run in CJS mode but it has issues. Will keep trying.
I found this site:
https://arethetypeswrong.github.io/?p=%40copilotkit%2Freact-core%400.14.0

The solution to this is as @mao437303994 mentioned, do not use serverDependenciesToBundle: 'all' and instead explicitly define it as and array of specific packages to bundle: serverDependenciesToBundle: ['some-package', 'another-package']


Add Hack Series cohort 4 recap notes

As with #438, I am so sorry for the long delay with this. Merging now.


Add foreman

This little tiny tools seems like a good addition:
http://flyingmachinestudios.com/foreman/
It has a free and a paid version as well.

Awesome!


bug generating outwork slug

If you create a new outwork content page as a child of the top-level outwork page, you get outwork duplicated in the slug, e.g. outwork/2018/outwork/test-outwork - the custom get_slug logic should take that into account and handle properly.

When I added 2 new outwork files, they had clean URLS
https://test-derrida.cdh.princeton.edu/outwork/2018/draft-database-statement/
https://test-derrida.cdh.princeton.edu/outwork/2018/draft-data-story/


Cache cabal2nix expr to avoid IFD

cc @aravindgopall who continues this.

A good CI will cache it for you.
If you want to avoid IFD, you could perhaps look for a local file, and rely on something like the cabal2nix pre-commit hook.


Gracefully fall back to unlit shading in ModelExperimental for models without normals

This PR makes two changes to make rendering models handle edge cases more gracefully:

If a primitive in a ModelExperimental does not have normals, now the lighting mode falls back gracefully to UNLIT, since this looks better than attempting to render PBR with default settings (which often results in everything turning solid black). Technically speaking, this behavior is not correct by the glTF spec, but in Cesium the unlit behavior is consistent with the old Model. Unlit shading is very common in geospatial data (e.g. photogrammetry) where we want to render the textures directly.
For CustomShader, I noticed that if you specify the lightingModel or isTranslucent but do not include vertexShaderText/fragmentShaderText, these settings were being optimized out. I moved the if checks earlier in CustomShaderPipelineStage so they always get applied, this is more useful.

Local Sandcastle for testing
@j9liu could you review when you get a chance?

Thanks for the pull request @ptrgags!

:heavy_check_mark: Signed CLA found.
:grey_question: CHANGES.md was not updated.

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

Reviewers, don't forget to make sure that:

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

@ptrgags these changes look good, and the Sandcastle works as intended. I made a few suggestions unrelated to the code -- once those get addressed I'll go ahead with the merge!

@j9liu updated!

Merging now. Thanks @ptrgags !


Share echo instances in mirroring tests

Builds on #25636
This will be a bit cleaner once the refactoring in
https://github.com/istio/istio/pull/25754 lands
This cuts runtime from 30s to 10s. The addition of external will be used in another test as well, so its generally useful.

@howardjohn: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

release-notes_istio
98e040baa5e9f88375cb1d7e34454001b7b3cf83
link
/test release-notes_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@howardjohn: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

release-notes_istio
98e040baa5e9f88375cb1d7e34454001b7b3cf83
link
/test release-notes_istio

lint_istio
98e040baa5e9f88375cb1d7e34454001b7b3cf83
link
/test lint_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

12 min test run for pilot - https://prow.istio.io/view/gs/istio-prow/pr-logs/pull/istio_istio/25782/cache-integ-pilot-k8s-tests_istio/110

@howardjohn: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

release-notes_istio
98e040baa5e9f88375cb1d7e34454001b7b3cf83
link
/test release-notes_istio

lint_istio
98e040baa5e9f88375cb1d7e34454001b7b3cf83
link
/test lint_istio

integ-multicluster-k8s-tests_istio
98e040baa5e9f88375cb1d7e34454001b7b3cf83
link
/test integ-multicluster-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

I'm doing this same thing in https://github.com/istio/istio/pull/25774

@howardjohn: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-multicluster-k8s-tests_istio
99bf4ef10c297014c55cbf6c649d0c4a1c16ea72
link
/test integ-multicluster-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/retest


Add Kfdef for Data Science pipelines operator

Enables Data Science Pipelines Operator as a Kfdef CR
Description
This will add Data Science Pipelines Operator as a Kfdef to deploy DSP in a multi-stack architecture. DSPO will be deployed on redhat-ods-applications namespace.
How Has This Been Tested?

Merge criteria:
PRs for RHODS-6926, RHODS-739, and RHODS-7400 must be merged first

[X] The commits are squashed in a cohesive manner and have meaningful messages.
[ ] For commits that came from upstream, [UPSTREAM] has been prepended to the commit message.
[X] JIRA link(s): https://issues.redhat.com/browse/RHODS-7151
[ ] The Jira story is acked.
[ ] Live build image:
[ ] Testing instructions have been added in the PR body (for PRs involving changes that are not immediately obvious).
[ ] The developer has manually tested the changes and verified that the changes work.
[ ] QE contact acknowledges that this has been tested and is approved for merge.

If we are introducing deployments in redhat-ods-applications, we would need to update NetworkPolicy for that namespace https://github.com/red-hat-data-services/odh-deployer/blob/main/network/applications_network_policy.yaml

Mental note: Don't forget to add the parameters for all DSP images.

@VaishnaviHire, there is no ingress/egress traffic for this application except for internal traffic to the api server, this is an operator that submits resources to the cluster. It has the appropriate rbac permission. In this case, it seems to me the network policy doesn't need to be updated -- can you confirm?

@VaishnaviHire, there is no ingress/egress traffic for this application except for internal traffic to the api server, this is an operator that submits resources to the cluster. It has the appropriate rbac permission. In this case, it seems to me the network policy doesn't need to be updated -- can you confirm?

I see the 8080 and 8081 ports are used by the application are already added in the Network Policy. If there are any other ports that are accessed by external traffic, then you would need to update the Network Policy.
Do you have a live-build where this can be tested?

/lgtm
Code changes look good

I've tested quay.io/hukhan/rhods-operator-live-catalog:1.25.0-dspo-18 and the rhods-data-science-pipelines-operator kfdef was deployed and the dspo components were deployed too

Using quay.io/hukhan/rhods-operator-live-catalog:1.25.0-dspo-18
data-science-pipelines-operator-controller-manager-57b6bcf4cm2k   1/1     Running   0          63m
data-science-pipelines-operator-controller-manager-57b6bcf6cgqp   1/1     Running   0          63m
data-science-pipelines-operator-controller-manager-57b6bcfcj8h6   1/1     Running   0          63m

Okay we should be good to merge this once https://github.com/red-hat-data-services/odh-manifests/pull/324
is merged.


in Windows use Android UX

I noticed that it is no longer possible to drag and scroll on windows,
On ListView, only the scroll wheel can be used. Is this a bug or a Windows platform UX behavior? If you switch this platform behavior to Android

[√] Flutter (Channel master, 2.3.0-2.0.pre.107, on Microsoft Windows [Version 10.0.17763.1879], locale zh-CN)
    • Flutter version 2.3.0-2.0.pre.107 at D:\flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 55354aa28b (2 days ago), 2021-05-11 03:24:03 -0700
    • Engine revision 5d3dde58ef
    • Dart version 2.14.0 (build 2.14.0-74.0.dev)
    • Pub download mirror https://pub.flutter-io.cn
    • Flutter download mirror https://storage.flutter-io.cn

[√] Android toolchain - develop for Android devices (Android SDK version 30.0.2)
    • Android SDK at C:\Users\autopMateBook\AppData\Local\Android\sdk
    • Platform android-30, build-tools 30.0.2
    • Java binary at: D:\androidstudio\jre\bin\java
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b01)
    • All Android licenses accepted.

[√] Chrome - develop for the web
    • Chrome at C:\Program Files\Google\Chrome\Application\chrome.exe

[√] Visual Studio - develop for Windows (Visual Studio Enterprise 2019 16.9.0)
    • Visual Studio at C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise
    • Visual Studio Enterprise 2019 version 16.9.31025.194
    • Windows 10 SDK version 10.0.18362.0

[√] Android Studio (version 4.1.0)
    • Android Studio at D:\androidstudio
    • Flutter plugin can be installed from:
       https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
       https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b01)

[√] IntelliJ IDEA Community Edition (version 2020.3)
    • IntelliJ at D:\IntelliJ IDEA Community Edition 2020.3.2
    • Flutter plugin can be installed from:
       https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
       https://plugins.jetbrains.com/plugin/6351-dart

[√] VS Code
    • VS Code at C:\Users\autopMateBook\AppData\Local\Programs\Microsoft VS Code
    • Flutter extension version 3.22.0

[√] VS Code, 64-bit edition (version 1.55.2)
    • VS Code at C:\Program Files\Microsoft VS Code
    • Flutter extension version 3.22.0

[√] Connected device (4 available)
    • FRL AN00a (mobile)                 • EYDNW20A27001031 • android-arm64  • Android 10 (API 29)
    • Android SDK built for x86 (mobile) • emulator-5554    • android-x86    • Android 10 (API 29) (emulator)
    • Windows (desktop)                  • windows          • windows-x64    • Microsoft Windows [Version 10.0.17763.1879]
    • Chrome (web)                       • chrome           • web-javascript • Google Chrome 90.0.4430.212

• No issues found!

Hi @au-top
This is a recent change https://github.com/flutter/flutter/pull/81569, working as intended
Closing, as this isn't an issue with Flutter itself. If you disagree, please write in the comments and I will reopen it.
Thank you


Random Testimonial Generator

Describe the project you want to add with tech stack
A random testimonial generator using HTML CSS and Javascript
Screenshots (optional)

i will make it kindly assign it to me'

@MohitGupta121 please assign this


Why does Vcpkg try to download and install older versions of tools than ones that I have already installed?

Is your feature request related to a problem? Please describe.
I have already installed PowerShell 7.0.0, but Vcpkg downloaded and installed 6.2.1.  This spended my time and network bandwidth.
Looking into scripts/vcpkgTools.xml and toolsrc/src/tools.cpp, Vcpkg does not seem to check the versions of tools installed in system.
Proposed solution
It wold be nice if maximum and minimum required versions for each tool, and how to analyze versions of tools already in PATH are given in vcpkgTools.xml.
Describe alternatives you've considered
Additional context

Using the lastest/greatest versions of the utility software introduces an unknown element into the stability of vcpkg and degrades the user experience.
Example a few weeks ago, ninja was upgraded from 1.8.2 to 1.10.0 and many ports began failing as a change was made in how multiple build versions defined in cmake files where handled - under 1.8.2, this was flagged as a warning and the build continued, now under 1.10.0, this is flagged as an error and the build stops. There is a solution, but it will take time to test/implement effectively considering the 100's of ports vcpkg is capable of installing.
One can always experiment and create test versions of vcpkg with customized changes to use the latest/greatest utility software. One can then share their findings and experience which will greatly enhance the experience using vcpkg.
In the end, it would be nice if there was a gui type interface that one could put the path of already installed utility software to use...

1.9.2 to 1.10.0

the vcpkg ninja was actually upgraded from 1.8.2 to 1.10.0 https://github.com/microsoft/vcpkg/commit/19ef8e31479d8f0d6a469c134080812944f2d7c1#diff-1efa33d774ab169851c15310ec385b92
the vcpkg ninja update from 1.8.2 to 1.10.0 identified how ninja was changed between 1.8.2 and 1.9.0 documented in #10887

the problem is another, it's when compiling at once a dynamic and static library

the problem is another, it's when compiling at once a dynamic and static library

to clarify, where ninja 1.8.2 previously treated by default the multiple definitions for release/debug (static/dynamic) as a warning, continuing the build
now version 1.10.0 (changed with 1.9.0) treats by default the multiple definitions for release/debug (static/dynamic) as an error, stopping the build
see PR https://github.com/microsoft/vcpkg/pull/10964

https://github.com/microsoft/vcpkg/pull/7055
https://github.com/microsoft/vcpkg/pull/7052

I think this issue was resolved, right?

It would be nice if Vcpkg could designate the version of dependencies as the formats like ^x.y.z, <x.y.z, or something, which can be used in package managers for other languages (npm, yarn, cargo, and poetry) if possible, but I will hold it off because Vcpkg can retain just single version per package.
This seems not to be possible to fix as long as Vcpkg adopts Git, not an ecosystem like npm, PyPI, or crates, as package management.


Wont start on Ubuntu after install

Describe the bug
I installed surrealist on my ubuntu desktop, i can see the icon on my apps page but when i click it, it seems to try to open but i get no GUI and there is no process running for it.
To Reproduce
Steps to reproduce the behavior:

downloaded deb package
installed using gdeb
tried to run via icon on apps page
No gui starts and no process running

Expected behavior
Should start
Environment:
Linux
Paste your environment here by following these steps
Ubuntu 23.10

Having the same issue, when trying to start the app from the CLI, I believe the issue is one of can't open shared resources, missing libssl.so.1.1 (even though my machine, Linux Mint Virginia 21.3, does have libssl.so.3.0 installed, after it's was built from source downloaded at openssl.org).

I am also facing this issue on Ubuntu Desktop. I installed v2.0.3 but it would not open.

Apparently it will be fixed in the next release, i asked on discord and the developer replied.

This should have been fixed in a recent release


Italian translation

Italian translation of

[x] strings.xml
[ ] full_description.txt
[ ] short_description.txt
[ ] title.txt
[ ] changelog 1
[ ] changelog 101
[ ] changelog 102
[ ] changelog 103
[ ] changelog 104

Thank you


Update mocha to 3.0.0

Changelog: https://github.com/mochajs/mocha/blob/master/CHANGELOG.md#300--2016-07-31

Thanks :octocat:

Is there any time frame for the new version which contains the new mocha dependency?


Cannot access viewing popup after editing

From Mike T:
"This error means that there are no popups in the webmap once the editor has been opened and closed."

verified that this has been resolved on devext


[Feature Request] Improve database search speed for ontologies

Is your feature request related to a problem? Please describe.
Since we added over 2 million terms and is-a relationships the search speed noticebaly decreased.
Describe the solution you'd like
Improved search speed without decreasing the quality in search results.

I reduced the term search procedure from:
BEGIN
SELECT *
FROM Term
WHERE
	(
		Match(Term.Name) AGAINST(Concat(query,'*') IN BOOLEAN MODE)
                OR INSTR(Term.Name,query) > 0
	);
END

... to:
BEGIN
SELECT *
FROM Term
WHERE
	(
		MATCH(Term.Name) AGAINST(Concat(query,"*") IN BOOLEAN MODE)
	);
END

This variant has no option to find e.g. "experimental" by search string "peri" as only a wildcard after the querstring is used. After testing this seems to work fine, but we need to keep an eye on search speed vs search quality.
This change is live in production!

I reduced the term search procedure from:
BEGIN
SELECT *
FROM Term
WHERE
	(
		Match(Term.Name) AGAINST(Concat(query,'*') IN BOOLEAN MODE)
                OR INSTR(Term.Name,query) > 0
	);
END

... to:
BEGIN
SELECT *
FROM Term
WHERE
	(
		MATCH(Term.Name) AGAINST(Concat(query,"*") IN BOOLEAN MODE)
	);
END

This variant has no option to find e.g. "experimental" by search string "peri" as only a wildcard after the querstring is used. After testing this seems to work fine, but we need to keep an eye on search speed vs search quality.
This change is live in production!


Make command to update docs

Note, doesn't add a check to our CI but that can be done as a later step

Yay, cross-team sharing!


[otlLib] In PairPos, always build one class-based subtable

Fixes https://github.com/fonttools/fonttools/issues/2772

#2776 is this plus tests, right?

closing as duplicate of #2776


Use https://github.com/wuub/rxv ?

https://github.com/wuub/rxv looks like a well maintained python library for dealing with Yamaha devices.  Would it make sense to use that underneath the hood of this plugin?

I haven't had much experience implementing 3rd party libs in Indigo plugins as it most of the ones I've build have only consisted of simple calls to restful apis.   Feel free to open a PR if you'd like :)

The 1.0.0 version of the plugin uses a custom (and embedded) version of the rxv library to add support for the RX-Vx73 receiver line.


Remove nodejs and Tiltfile from coupon sample

Fixed in https://github.com/liferay/liferay-localdev/commit/d2332a936ad957cda4bbf30de43d5b61a14904a8


static_key_parse_error  how can i fix this

why happend this

this profile dont has this part

this profile dont has this part


fix socket fuzzer mode

xref #300
Note: the unittest.sh still seems a bit racy. I'll update once I've figured out what's going on there.

Thaanks,
I'll ask @dobin to take a look, but if he's unable I'll merge it in a day or two or three.


[Feature] Suggested as the design a one-to-many structure

It is recommended to design a one-to-many structure:
IDictionary<TKey, IList<TValue>> { }

This is somewhat similar to: NameValueCollection  But allowed to be generic


Discussion - testing Honeywell panel

Hi there,
I wanted to share some feedback with testing my Honeywell panel. This may be better as a discussion post but I cannot open one :)

I migrated from a config-based setup. Changing from envisalink to envislink_new worked fine.
Using a Honeywell panel.
Zone updates are really fast now. This was my main gripe with the current version. I am using a dump interval of 3s but it seems much faster than that.

Arming via HomeAssistant / HomeKit works now. My issue was on the Vista 20P side; evidently the EVL was on the same address as another keypad. Hazards of configuring without an alphanumeric keypad and doing it blind... ~I haven't been able to test arming as it only works in the EVL and not in HomeAssistant yet. I don't see any errors in the logs or anything, so I'm still debugging. It wasn't working beforehand so I'm 95% sure it's an issue on my end. If you have suggestions let me know. I did just try changing the password used for the TPI.~

I was having issues with arming from Home Assistant working intermittently. Turns out, I had placed the EVL on the same address as another panel which was causing the problem. Arming from the UI works now.
I did notice a few things:
Logbook spam when alarm triggered
I did notice that when the alarm goes off, the integration generates a LOT of messages like:
.
It went on for a while, despite me canceling the alarm within 30 seconds. I am not sure why I see an ALARM 04 message in the logbook for up to an hour.  The "Alarm Canceled" messages may be caused by me going into HomeKit and disabling the alarm from there (and it failing with retries due to the device address conflict). I'll try to find time to test this again.
Issue with hardware version detection
The integration shows up as Hardware Version 3. I have an EVL4 MAX.

I have configured in the configuration.yaml to be evil_version: 4:
envisalink_new:
    host: $HOST
    panel_type: HONEYWELL
    user_name: $PASSWORD # For Honeywell this must match password
    password: $PASSWORD
    evl_version: 4
    partitions:
        1:
            name: "Home Alarm"
    zones:
        1:
            name: "Zone 1"
            type: "door"
... ...

@automation-dude-hass The Home Alarm Keypad entity's state directly reflects the state of the text that should be displayed on a keypad.  The EVL provides these updates and they are reflected in the entity.  So I expect the messages are you seeing would have also been displayed on any physical keypads you have.  I'm not familiar enough with Honeywell systems to know what those messages mean but it's likely something that needs to be resolved on the panel itself rather than anything related to this integration.
Regarding the hardware detection being incorrect: can you confirm you are running v0.7.1?  I attempted to fix a detection issue with that version but was unable to test against an EVL 4MAX as I don't have one of those units.
If you are still seeing this issue with 0.7.1, can you confirm whether you're seeing any warnings or errors in the HA logs?  If it's unable to parse the version when it queries the EVL, it should log a message.

Regarding the hardware detection being incorrect: can you confirm you are running v0.7.1? I attempted to fix a detection issue with that version but was unable to test against an EVL 4MAX as I don't have one of those units.

(Just chiming in, I don't have this issue, but helping with the EVL4 Max...)
I can confirm on my board that it shows EVL4 Max.

Oh my, sorry for the lack of response. I did not have email forwarding for this account to my primary email.
This is what I see:

Indeed I am on the 0.7.1 version

In the past few weeks everything has worked flawlessly. I currently use:

Arming / disarming
Zone status changes (viewed in History page)

We can probably close this, unless there are other things you'd like me to check. I don't see errors about being unable to parse the hardware type, however I do have an EVL4-EZ and it does show it as Envisalink 3 - @ufodone
2023-10-10 15:00:23.073 ERROR (MainThread) [custom_components.envisalink_new.pyenvisalink.alarm_panel] Unable to validate connection: invalid authorization.
2023-10-10 15:00:23.116 INFO (MainThread) [custom_components.envisalink_new.pyenvisalink.alarm_panel] Checking panel type for envisalink.lan
2023-10-10 15:00:24.807 INFO (MainThread) [custom_components.envisalink_new.pyenvisalink.alarm_panel] Panel type: HONEYWELL

@automation-dude-hass: Sorry, my turn for the badly delayed response!  😄
That invalid authorization message in the last log snippet you posted could be the problem.  This means that the integration is unable to query the envisalink device for its version, etc.  The culprit is likely that your config has the user_name set to the password.  I see the comment you have there that these two must match but I don't believe that's true (at least not anymore).  Try setting you user_name to user, restart HA and see if that fixes the issue.


[pilot] Support Xcode 11 (beta)

New Issue Checklist

[x] Updated fastlane to the latest version
[x] I read the Contribution Guidelines
[x] I read docs.fastlane.tools
[x] I searched for existing GitHub issues

Issue Description
Fastlane seems to lack support for uploading build to testflight with Xcode 11 beta, which is required for building apps that are targeting iOS 13.
Error is "Could not find transporter at /Applications/Xcode-beta.app/Contents/Developer/" which makes sense given that Xcode 11 doesn't include the Transporter application anymore.
See also: https://stackoverflow.com/questions/56504929/bitrise-could-not-find-transporter-at-applications-xcode-beta-app-contents-devel and https://developer.apple.com/videos/play/wwdc2019/301/
Command executed
fastlane upload_to_testflight
Complete output when running fastlane, including the stack trace and command used

[09:02:37]: Get started using a Gemfile for fastlane https://docs.fastlane.tools/getting-started/ios/setup/#use-a-gemfile
[09:02:37]: WARNING: fastlane requires your locale to be set to UTF-8. To learn more go to https://docs.fastlane.tools/getting-started/ios/setup/#set-up-environment-variables
[09:02:37]: ----------------------------------------
[09:02:37]: --- Step: Verifying fastlane version ---
[09:02:37]: ----------------------------------------
[09:02:37]: Your fastlane version 2.125.2 matches the minimum requirement of 2.121.1  ✅
[09:02:37]: ------------------------------
[09:02:37]: --- Step: default_platform ---
[09:02:37]: ------------------------------
[09:02:37]: Driving the lane 'ios publish' 🚀
[09:02:37]: ----------------------------------
[09:02:37]: --- Step: upload_to_testflight ---
[09:02:37]: ----------------------------------
[09:02:38]: Login to App Store Connect (****)
Available session is not valid any more. Continuing with normal login.
[09:02:40]: Login successful
[09:02:41]: Ready to upload new build to TestFlight (App: xxxxxxxxx)...
[09:02:41]: Going to upload updated app to App Store Connect
[09:02:41]: This might take a few minutes. Please don't interrupt the script.
+------------------+-------------+
|          Lane Context          |
+------------------+-------------+
| DEFAULT_PLATFORM | ios         |
| PLATFORM_NAME    | ios         |
| LANE_NAME        | ios publish |
+------------------+-------------+
[09:02:41]: Could not find transporter at /Applications/Xcode-beta.app/Contents/Developer/. Please make sure you set the correct path to your Xcode installation.
+------+----------------------------+-------------+
|                fastlane summary                 |
+------+----------------------------+-------------+
| Step | Action                     | Time (in s) |
+------+----------------------------+-------------+
| 1    | Verifying fastlane version | 0           |
| 2    | default_platform           | 0           |
| 💥   | upload_to_testflight       | 3           |
+------+----------------------------+-------------+
[09:02:41]: fastlane finished with errors
[!] Could not find transporter at /Applications/Xcode-beta.app/Contents/Developer/. Please make sure you set the correct path to your Xcode installation.

@edwinvanderham Thanks for letting us know! We will look into getting this working as soon as possible 😊
BRB, downloading Xcode 11 😉

Couple of findings/thoughts on this:

Xcode <10 included the Application Loader.app (Contents > Applications)
There was/is the standalone Transporter client: https://help.apple.com/itc/transporteruserguide/#/itc0937fdf65 It was previously "bundled" with the Application Loader. It's possible to download it: https://help.apple.com/itc/transporteruserguide/#/apdA3ae5a8b0?sub=apdA687d545d
https://developer.apple.com/videos/play/wwdc2019/301/ talks about a new native Transporter.app When it gets release, if it uses Transporter "under the hood" or other things are so far unknown

@joshdholtz it looks like it works now, thanks a lot for the swift response!


Add commands reset and hold-in-reset

I'm not sure if it will cause any problems but I see three(?) resets when I exercise the reset command:
	ESP-ROM:esp32s3-20210327
	Build:Mar 27 2021
	rst:0x15 (USB_UART_CHIP_RESET),boot:0x8 (SPI_FAST_FLASH_BOOT)
	Saved PC:0x40378c52
	SPIWP:0xee
	mode:DIO, clock div:2
	load:0x3fce3810,len:0x1198
	load:0x403c9700,len:0xa50
	load:0x403cc700,len:0x2d88
	SHA-256 comparison failed:
	Calculated: b655b51fda251ec5ef85c33a9a8c1216e6db0cef46867cad3c9f5dbda0850921
	Expected: 7b22d32478d4df842a38e06a59debd2d38f6e76f524fdd78597a3546450207f0
	Attempting to boot anyway...
	entry 0x403c9894

	ESP-ROM:esp32s3-20210327
	Build:Mar 27 2021
	rst:0x15 (USB_UART_CHIP_RESET),boot:0x0 (DOWNLOAD(USB/UART0))
	Saved PC:0x40056f59
	waiting for download
	ESP-ROM:esp32s3-20210327
	Build:Mar 27 2021
	rst:0x15 (USB_UART_CHIP_RESET),boot:0x8 (SPI_FAST_FLASH_BOOT)
	Saved PC:0x40048df3
	SPIWP:0xee
	mode:DIO, clock div:2
	load:0x3fce3810,len:0x1198
	load:0x403c9700,len:0xa50
	load:0x403cc700,len:0x2d88
	SHA-256 comparison failed:
	Calculated: b655b51fda251ec5ef85c33a9a8c1216e6db0cef46867cad3c9f5dbda0850921
	Expected: 7b22d32478d4df842a38e06a59debd2d38f6e76f524fdd78597a3546450207f0
	Attempting to boot anyway...
	entry 0x403c9894
	I (229) esp_psram: Found 2MB PSRAM device
	I (229) esp_psram: Speed: 80MHz
	I (234) cpu_start: Pro cpu up.
	I (234) cpu_start: Starting app cpu, entry point is 0x40375fc4
	I (0) cpu_start: App cpu up.

I added the linefeed to help parse things.
The three resets:
	rst:0x15 (USB_UART_CHIP_RESET),boot:0x8 (SPI_FAST_FLASH_BOOT)
	rst:0x15 (USB_UART_CHIP_RESET),boot:0x0 (DOWNLOAD(USB/UART0))
	rst:0x15 (USB_UART_CHIP_RESET),boot:0x8 (SPI_FAST_FLASH_BOOT)

For comparison I used esptool.py to reset the board (and I realized I don't know the command Anthony is using to do this).
I used:
esptool.py --chip esp32s3 -p /dev/tty.usbmodem2121301 --before=default_reset --after=hard_reset read_flash 0 0x1000 ~/deleteme.bin

And this resulted in two resets:
ESP-ROM:esp32s3-20210327
Build:Mar 27 2021
rst:0x15 (USB_UART_CHIP_RESET),boot:0x0 (DOWNLOAD(USB/UART0))
Saved PC:0x40378c52
waiting for download

ESP-ROM:esp32s3-20210327
Build:Mar 27 2021
rst:0x15 (USB_UART_CHIP_RESET),boot:0x8 (SPI_FAST_FLASH_BOOT)
Saved PC:0x40378bb6
SPIWP:0xee
mode:DIO, clock div:2
load:0x3fce3810,len:0x1198
load:0x403c9700,len:0xa50
load:0x403cc700,len:0x2d88
SHA-256 comparison failed:
Calculated: b655b51fda251ec5ef85c33a9a8c1216e6db0cef46867cad3c9f5dbda0850921
Expected: 7b22d32478d4df842a38e06a59debd2d38f6e76f524fdd78597a3546450207f0
Attempting to boot anyway...
entry 0x403c9894
I (229) esp_psram: Found 2MB PSRAM device
I (229) esp_psram: Speed: 80MHz
I (234) cpu_start: Pro cpu up.

@bobsjune
You can build from the local repo with cargo build --release -p espflash -p cargo-espflash
Install the new espflash from the local repo with:
cargo install --path ./espflash
cargo install --path ./cargo-espflash

I don't know why there would be three resets; I only expect two:  I'm guessing that in the first one, the ROM expects to load (based on the default strapping options) from SPI flash, but then "changes its mind", perhaps because it sees a connection on the DFU/UART; then the second is trying to download in DFU mode from the UART; that times out that and the ROM shifts back to reading from SPI flash (the DFU download would be the RAM stub).

Using hold-in-reset issues two resets:
	rst:0x15 (USB_UART_CHIP_RESET),boot:0x8 (SPI_FAST_FLASH_BOOT)
	rst:0x15 (USB_UART_CHIP_RESET),boot:0x0 (DOWNLOAD(USB/UART0))

I think this is OK because it doesn't seem to get out of the ROM bootloader

I'd still like to see an option to prevent it from automatically resetting after a call to erase-region or write-bin but that can be a different PR.

That's right.  That's simply a different request/desire.  This PR is about adding reset and hold-in-reset commands, not about adding options to other commands.

I'm not sure if it will cause any problems but I see three(?) resets when I exercise the reset command:

I think I know why this is:  I believe the code here is loading the RAM stub that is used to flash or erase the device.  I don't believe this is necessary for the reset functionality.
Which do you prefer:  Land this now and get the existing functionality which does perform a reset even if it's a bit extra?  Or wait until I or someone else can dig in further and refine the behavior?

I vote for land it now.  I don't think an extra reset causes us any grief.

I took another look at this.  We're already specifying --no-stub in the reset command and it still performs these extra resets.  We'd have to untangle some code pretty deep in espflash to avoid this.  If it's important to you, let's make another ticket for it.


Remodel DOI

DOI -> Doi
rdfs:resource is OK as range of hasDOI (but change property to "doi" or use existing one)
its just a class with a label, use real DOI URL instead
then we don't have to define the individual
report change in next meeting

:%s/:doi :i\([^-]*\)-\([^ ]*\)/:doi <https:\/\/doi.org\/\1\/\2>/c

https://www.bibsonomy.org/ uses the biblio ontology http://purl.org/ontology/biblio/ with the predicate bibo:doi and the DOI string as an object, I will copy that.

http://purl.org/ontology/biblio/ does not exist, created an issue at https://bitbucket.org/bibsonomy/bibsonomy/issues/2917/rdf-export-bibo-namespace-does-not-exist.

Decision: Keep URIs in HITO, use @prefix bibo: <http://purl.org/ontology/bibo/>. and datatype property bibo:doi.


ARMv7 - Float4_NEON.h - Crash (SIGBUS)

Hi!
I have a problem that I'm not able to solve.
First I'm using the latest 1.60d release;
When I use Effekseer on some Android devices that use ARMv7 processors sometimes there is a SIGBUS (signal SIGBUS: illegal alignment).
My game basically only has the effekseer implemented... I have a triangle on the screen and the effekseer calls (with the examples from the library itself).
What I could see is that the problem is in Float4_NEON.h, the error happens in the constructor:
Float4(float x, float y, float z, float w) { const float f[4] = {x, y, z, w}; s = vld1q_f32(f); }
I did dozens of tests, and the crash happens sometimes, and sometimes not, really intermittent.
So I turned off the EFK_SIMD_NEON preprocessor and turned on EFK_SIMD_GEN to test without the neon instructions, and the crash didn't happen anymore, I opened the app more than 100x and the problem didn't happen anymore.
Returning the EFK_SIMD_NEON as in the original code, the error happens again.
Below the logcat showing the entire callstack:
07-08 16:09:53.130 19992-20005/br.com.daldegam.game A/libc: Fatal signal 7 (SIGBUS), code 1, fault addr 0xb8e0dbe8 in tid 20005 (GLThread 2467)
07-08 16:09:53.190 398-398/?  A/DEBUG: Build fingerprint: 'samsung/j5lteub/j5lte:6.0.1/MMB29M/J500MUBU1BRD1:user/release-keys'
07-08 16:09:53.190 398-398/? A/DEBUG: Revision: '5'
07-08 16:09:53.190 398-398/? A/DEBUG: ABI: 'arm'
07-08 16:09:53.190 398-398/? A/DEBUG: pid: 19992, tid: 20005, name: GLThread 2467  >>> br.com.daldegam.game <<<
07-08 16:09:53.190 398-398/? A/DEBUG: signal 7 (SIGBUS), code 1 (BUS_ADRALN), fault addr 0xb8e0dbe8
07-08 16:09:53.210 398-398/? A/DEBUG:     r0 b8e0dbe8  r1 b2c232e0  r2 00000000  r3 00000000
07-08 16:09:53.210 398-398/? A/DEBUG:     r4 b2fa5e20  r5 6f924374  r6 12c80280  r7 b2c23338
07-08 16:09:53.210 398-398/? A/DEBUG:     r8 12cb2670  r9 b89534b0  sl 00000000  fp 00000000
07-08 16:09:53.210 398-398/? A/DEBUG:     ip b6d37e40  sp b2c232d0  lr 951a8ade  pc b2da8ba2  cpsr 400b0030
07-08 16:09:53.220 398-398/? A/DEBUG: backtrace:
07-08 16:09:53.220 398-398/? A/DEBUG:     #00 pc 0015cba2  /data/app/br.com.daldegam.game-1/lib/arm/libGameCore.so (_ZN9Effekseer4SIMD6Float4C2Effff+97)
07-08 16:09:53.220 398-398/? A/DEBUG:     #01 pc 001602af  /data/app/br.com.daldegam.game-1/lib/arm/libGameCore.so (_ZN9Effekseer4SIMD5Vec3fC2Efff+58)
07-08 16:09:53.220 398-398/? A/DEBUG:     #02 pc 00169765  /data/app/br.com.daldegam.game-1/lib/arm/libGameCore.so (_ZN9Effekseer14InstanceGlobalC1Ev+52)
07-08 16:09:53.220 398-398/? A/DEBUG:     #03 pc 0017295d  /data/app/br.com.daldegam.game-1/lib/arm/libGameCore.so (_ZN9Effekseer18ManagerImplemented4PlayERKNS_6RefPtrINS_6EffectEEERKNS_8Vector3DEi+104)
07-08 16:09:53.220 398-398/? A/DEBUG:     #04 pc 0012ce0f  /data/app/br.com.daldegam.game-1/lib/arm/libGameCore.so (_ZN12EffectEngine7PlayAllEv+138)
07-08 16:09:53.220 398-398/? A/DEBUG:     #05 pc 0012cccf  /data/app/br.com.daldegam.game-1/lib/arm/libGameCore.so (_ZN12EffectEngine6RenderEv+54)
07-08 16:09:53.220 398-398/? A/DEBUG:     #06 pc 0012b4b5  /data/app/br.com.daldegam.game-1/lib/arm/libGameCore.so (_ZN12NativeEngine9DrawSceneEv+72)
07-08 16:09:53.220 398-398/? A/DEBUG:     #07 pc 0012b955  /data/app/br.com.daldegam.game-1/lib/arm/libGameCore.so (Java_br_com_daldegam_game_RendererWrapper_on_1draw_1frame+14)
07-08 16:09:53.220 398-398/? A/DEBUG:     #08 pc 004daf3f  /data/app/br.com.daldegam.game-1/oat/arm/base.odex (offset 0x2e2000) (void br.com.daldegam.game.RendererWrapper.on_draw_frame()+74)
07-08 16:09:53.220 398-398/? A/DEBUG:     #09 pc 004db157  /data/app/br.com.daldegam.game-1/oat/arm/base.odex (offset 0x2e2000) (void br.com.daldegam.game.RendererWrapper.onDrawFrame(javax.microedition.khronos.opengles.GL10)+58)
07-08 16:09:53.220 398-398/? A/DEBUG:     #10 pc 03f55bef  /system/framework/arm/boot.oat (offset 0x303f000)
07-08 16:09:53.660 1692-20010/? W/ActivityManager:   Force finishing activity br.com.daldegam.game/.MainActivity
07-08 16:09:53.670 398-398/? A/DEBUG: Tombstone written to: /data/tombstones/tombstone_07
07-08 16:09:53.670 398-398/? E/DEBUG: AM write failed: Broken pipe
07-08 16:09:53.670 3328-3328/? E/audit: type=1701 msg=audit(1625771393.670:265): auid=4294967295 uid=10146 gid=10146 ses=4294967295 subj=u:r:untrusted_app:s0:c512,c768 pid=20005 comm=474C5468726561642032343637 reason="memory violation" sig=7

Some images with marked lines:

It's not just a device that this error happens.
Here are the specifications of the device I'm testing:
PROCESSOR
CPU Architecture: ARMv7 Processor rev 0 (v7l)
Board: MSM8916
Chipset: Qualcomm Technologies, Inc MSM8916
Cores: 4
Clock Speed: 1190 MHz - 1190 MHz
Instruction Sets: armeabi-v7a, armeabi
CPU Features: swp half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva idivt vfpd32 evtstrm
CPU Governor: interactive
Kernel Version: 3.10.49-12405330
Kernel Architecture: armv7l

GRAPHICS
Renderer: Adreno (TM) 306
Vendor: Qualcomm
OpenGL Version: OpenGL ES 3.0

RAM
Total: 1383 MB
Java Heap: 128 MB

Another device that also has the same crash sometimes:
PROCESSOR
CPU Architecture: ARMv7 Processor rev 3 (v7l)
Board: unknown
Chipset: MT6570
Cores: 2
Clock Speed: 604 MHz - 1300 MHz
Instruction Sets: armeabi-v7a, armeabi
CPU Features: half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva idivt vfpd32 lpae evtstrm
CPU Governor: interactive
Kernel Version: 3.18.35
Kernel Architecture: armv7l

GRAPHICS
Renderer: Mali-400 MP
Vendor: ARM
OpenGL Version: OpenGL ES 2.0

RAM
Total: 443 MB
Java Heap: 128 MB

Any ideas how I can solve this?
Thanks.

I will check it. Please wait in a few days

I didn't reproduce this error. But I fixed a possible bug.
Please try it.
EffekseerRuntime160d_0709.zip

I did several tests, and the crash didn't happen anymore.
We can consider it resolved!
Nice job!
Thanks @durswd


pump_dac: implement GetPumpOutputDuty() for DAC output

(cherry picked from commit 4ab46ce6c48f3a7fe9ad68e4254ac38b2845c872)

@mck1117 how about this one :)


mm down command not found

λ ./node_modules/.bin/mm down --migrations add-dummy-collection
mm: no such command 'down'

down command seems to be not available
node v8.9.4
npm v5.6.0
mongodb-migrations: v0.8.5

See #8


README.md Setup section missing "sudo apt install git" step for Raspberry Pi OS 64bit

Setup  section needs to add sudo apt install git step after ansible installation.
Otherwise git clone https://github.com/geerlingguy/internet-pi.git will fail with "command not found" error.

@btcpuertorico - Note that only the lite version of Pi OS (afaict) doesn't include git out of the box. It might be worth putting a note in that section though, saying "if you get a "command not found" error, also install git with sudo apt install git"

Agreed. Thanks.


SDF Text Labels!

Hi everyone!
This PR adds Signed Distance Field (SDF) text rendering to Cesium.  Signed Distance Fields are a rendering technique made popular by Valve for rendering crisp, scalable text (and other images) without using a ton of texture memory.  Regular bitmap fonts tend to start to look bad when they are rotated or when they are scaled up or down, but Signed Distance Fields solve this problem by storing the "distance" from the edge of a glyph in the texture instead and using a special fragment shader that can render crisp antialiased edges.
This isn't totally done but I wanted to get it out there to get some feedback.
Here is an example of what the new fonts look like.

Here is a summary of major changes to Cesium.

Glyphs are now being generated by the TinySDF library https://github.com/mapbox/tiny-sdf.  TinySDF is a library from MapBox that generates character glyphs using a canvas and then computes the SDF texture directly from the pixels in the canvas.  There are other libraries that generate SDF textures but they generally work offline are use the TTF font files directly and can't run right in the browser.
The Billboard and BillboardCollection classes have been updated to do optional SDF rendering.  This is not part of the public API and is only turned on by the LabelCollection.
Previously every small change to a font or a character color would result in a new, colored, glyph being generated in the texture atlas.  So generating a 24px green B and a 24px yellow B would result in 2 characters in the atlas.  Or requesting a 48px green Q and a 49px green Q would also result in 2 glyphs.  Now, all fonts, regardless of requested size, are generated once at a fixed size (48px currently) and then scaled up or down under the hood using the billboard scale.  This works with the Label.scale parameter as it did before, but it also works by setting a CSS font.  So setting a label to use "48px Calibri" and another to use "24px Calibri" will use just a single glyph set between them for the font, but the character billboards will be scaled.
Because of the way that outlining works when using SDF it is no longer necessary to generate glyphs with outlines included, freeing up more space in the texture atlas as well.  You can change the outline at runtime and it just sends a parameter to the shader and does all the outlining there, so you can do things like animate the outline size of a label and it'll be fast.
There haven't been any changes to the Cesium public API, the label API should work as it did before.
There is a new Labels SDF example that lets you scale labels up and down and play with the outline width with a slider as well as shows an animated label.
I added a new BillboardCollection.debugTextureAtlas property that will display a full screen debug quad that shows the contents of the texture atlas.  The Labels SDF example shows that off with a checkbox.

What is left to do?

The glyphs are generated at size 48 currently.  This seemed to give a good balance of texture size and quality for everything I've tried.  We might be able to get away with a smaller font size, but I might need some help with coming up a good test case for this.
I still need to write some new unit tests.
The glyphs are currently grayscale RGBA textures.  We really don't need RGBA and can use single band luminance textures instead.  I've got code that does this and it works fine, but there are issues with the TextureAtlas class using a luminance texture when it does it's resizing b/c it tries to attach it as a color buffer to the frame buffer object, which is illegal.  If we want to use luminance textures in the future we'll need to change the way the texture atlas resizing works.
There is a little jitter when labels are scaled down, it might be something with the texture filtering, where is that set?
I need to do a little work to get the measureText based kerning to work again.
I need to tweak the outline width setting a little so that it doesn't let you push the outlining higher than it can actually go.

Looking forward to your feedback!

Thanks for the pull request @jasonbeverage!

:heavy_check_mark: Signed CLA found.
:grey_question: Changes to third party files were made.

Looks like a file in one of our ThirdParty folders (ThirdParty/, Source/ThirdParty/) has been added or modified. Please verify that it has a section in LICENSE.md and that its license information is up to date with this new version.

:grey_question: Unit tests were not updated.

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

Reviewers, don't forget to make sure that:

[ ] Cesium Viewer works.
[ ] Works in 2D/CV.
[ ] Works (or fails gracefully) in IE11.

@jasonbeverage I haven't looked at the code yet but these were some of the things I noticed while going through all the Sandcastle examples:

Text looks sharper but also a bit thinner than master which can lead to some aliasing. Is this what you mean by the jitter / texture filtering?

Some of the ones I noticed it on was Callback Property (used in the gifs), CZML Reference Properties, and KML.
master

sdf

The text box fill color expands too far. See 3D Tiles Interactivity and CZML Billboard and Label (screenshot).

There are some crashes which look like the same error:

Labels - Offset label by distance
Labels - Scale label by distance
Picking - hover the mouse off the globe (gif)

Would we want to use SDF in PinBuilder/writeTextToCanvas? I think this would probably be a lot of work and not worth doing, but I'm curious if you had thought about it.

[ ] Use a new image for the Label SDF sandcastle

Hi @lilleyse, I pushed some changes that should fix the crash and the odd label positioning you were seeing.  When I added the CSS font based scaling I ended up breaking the positioning.
I also pushed a dynamic SDF scale factor that seems to look pretty good as well.  Give it a look and see what you think.

The outline color alpha doesn't seem to be blending properly: working sandcastle on cesiumjs.org

Good catch.  I'm encoding the width in the alpha component of that
attribute.  I'll pack the color so its compressed and add the alpha back
in.
On Tue, Apr 30, 2019, 2:29 PM Sean Lilley<EMAIL_ADDRESS>wrote:

The outline color alpha doesn't seem to be blending properly: working
sandcastle on cesiumjs.org
https://cesiumjs.org/Cesium/Build/Apps/Sandcastle/#c=bVRrb9owFP0rFl8IEjNlfa2UViuhndBoO7Vl01SqykkuYOHYke1A2bT/vmub0NKSD3nc63Pu69xMSplariSZgo2VUDpK3f2G5dAkTBQz1iB/x5LgtWCaeCc5IzEYXubUIx43CGrVqChAx8xA1Hg6DTgNttRyC0InWuUXjj2Ea5KCaQNXQjEbhagNRP8by7F0YRccluDiSlhWRD+9Laqn/jNW0jIuQdcdcCxbLfIwAw+8VhkIYjVL54ZYNBrLLBA1IarUJOeSE1YUgqfMNYK+RgzAs6p+VVqBEX7xzM5Ih+zR48Nm8JiUCUBTm+41t876YtFRv4OsvsNl0PcYnKT+TQNI99ITJbjnbxBCLYOLrYIHi6g/YWeqIrHuBWjr63rNOYc8AWTn0ioylyqdY1SiEgN6wRIBBqtct7HyUt+gaMPh2oj8PS6zd+RI6Qz922sCAnKQ1rhmOttogA9mCfZDkAmWzu26n1YpkTA3wkylpQNRVNxlwPdWgyyqr4/4Ab5Pzg1o5XLhcmpek2xWvJuhxxrccBkRLMFcUV0CgsCXHMdmlyp4TEgrvGNWQWHUpCCBFprn3PIF9ollWfRGdEN3Pt6QRl6mGyLkCYQetpZNoQz3CXQ2K8C0xTcm9/0e9GGKkzfRp+ND2j46aB8dHTfJ/gk9OfzsrsZaNxZerJPSjxkXDGsvZpxVmppwIbygOttrdnfZp67usGp7tF2RJTjrqValzHbBesOL+PsOuX44NrrcTf92VTqkWpMJ7qir4OBL8UJiJniieVWBsSsBna023zsTvRoMh88XN/3n29HDcHBzidpvnNaata5HnAf0V54XCreg1CKitGUhLwTKwLSSMp2DpakxblDdVgXqZnxBeHY2rr37fYxrJBXMGPRMSiHu+R8Y1867LTy/BcM/ldPiLS6fYCt3ZNY+HwYjpbTbws+PqLVa3zD+Bw
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/AnalyticalGraphicsInc/cesium/pull/7730#issuecomment-488063034,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AACPXYSIKIRJGHXVYVNRYJDPTCFW5ANCNFSM4HETUX5A
.

@jasonbeverage I went through the code and thought it looked pretty good. I pushed a commit with style tweaks (https://github.com/AnalyticalGraphicsInc/cesium/pull/7730/commits/56ca95aea3a05c4c20b1e0a7bb8570d79e6dbc180 and left a few comments.

Thanks Sean, I'm going to push some more updates today and tomorrow.

There are also some issues still with the glyph positioning related to the descent not being computed and applied correctly

I ran through most of the sandcastle examples again. The only issue I noticed was the label borders are smaller in the Picking demo in this branch compared to master.

Awesome I'll take a look.
On Thu, May 16, 2019, 11:05 AM Sean Lilley<EMAIL_ADDRESS>wrote:

I ran through most of the sandcastle examples again. The only issue I
noticed was the label borders are smaller in the Picking demo in this
branch compared to master.
[image: label]
https://user-images.githubusercontent.com/915398/57864625-3f438700-77ca-11e9-9571-5cfe1924fcc5.jpg
[image: label2]
https://user-images.githubusercontent.com/915398/57864627-3fdc1d80-77ca-11e9-8174-129f63983bad.png
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/AnalyticalGraphicsInc/cesium/pull/7730?email_source=notifications&email_token=AACPXYSSWJT7G3WG3UOTH53PVVZ4XA5CNFSM4HETUX5KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODVSDJWA#issuecomment-493106392,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AACPXYSDPVIAFRVUY4I5W4DPVVZ4XANCNFSM4HETUX5A
.

I pushed a fix for the background.  The background padding is specified in pixels relative to the size of the specified font, so it has to be scaled by the inverse of the relative size of the generated glyphs so it looks correct when it's finally rendered.

This should be ready to merge right after the June release.

@jasonbeverage the updates look good, thanks!

@pjcozzi sorry I missed these reviews coming through for some reason, I'll try to address them as soon as I can.
To respond to your questions:

Sure I'd be happy to write a guest blog post.  I'll do something similar to what I did for the particle system blog post and send it along.
I didn't do any specific performance tests vs the previous approach.  The fragment shader is more complicated b/c of the multi-sampling to remove the aliasing, so I imagine it will be slower than the original approach but hopefully not drastically.  I can can do a little FPS test and let you know what I find.
As for the most common use cases I'm going to say that SDF should actually be FASTER than the original approach.  Changing font size, color, and outline width all resulted in the generation of new glyphs previously.  For example in the new Labels SDF example it scales the Morgantown label up and down each frame.  Cesium master would chug along generating different sized glyphs for each of the potential scales until the scaling had oscillated up and down one cycle and all the glyphs for the potential sizes had been generated.  With SDF the glyph is generated once and that's it.  Changing fonts of a label requires new glyphs to be generated as it does in the master, but there is the slight overhead of computing the SDF field from the glyphs so it will be just a little slower.  I haven't seen any case where it's a new bottleneck though.

Cool, I will connect you with @OmarShehata via email now.
Great, I look forward to the stats
Fantastic news!

Hey @pjcozzi I addressed most of your reviews with either a code change or a comment.  I'm going to take a look at a FPS test next.

I did a little sandcastle test to display a big number of labels
var viewer = new Cesium.Viewer('cesiumContainer');
var scene = viewer.scene;
scene.debugShowFramesPerSecond = true;

Cesium.Math.setRandomNumberSeed(3);

var labels = viewer.scene.primitives.add(new Cesium.LabelCollection());
var i = 0;
for (i = 0; i < 10000; i++) {
    labels.add({
        position: Cesium.Cartesian3.fromDegrees(Cesium.Math.randomBetween(-180.0, 180.0), Cesium.Math.randomBetween(-90.0, 90.0)),
        text: 'Label ' + i,
        fillColor: Cesium.Color.WHITE,
        outlineColor: Cesium.Color.BLACK,
        outlineWidth: 1.0,
        font: '24px Calibri',
        style: Cesium.LabelStyle.FILL_AND_OUTLINE
    });
}

At 10K labels there is no difference between the master and the SDF branch on my machine, they both run at 60fps with the globe totally covered in labels.
At 100K labels the master runs at 10fps and my SDF branch runs at 7fps, so there is a difference in performance at some level but 100K labels is such an extreme case I don't think its going to be noticeable to anyone doing a sensible use case in Cesium.

@jasonbeverage great news on performance; does not sound like a concern at all for the cases you tested.
For test coverage, the best thing to do would be to just run coverage and double check that the new code paths are covered well.  Have you done this?  See https://github.com/AnalyticalGraphicsInc/cesium/tree/master/Documentation/Contributors/TestingGuide#run-all-tests-against-combined-file-run-all-tests-against-combined-file-with-debug-code-removed
Otherwise, I'll leave it to @lilleyse for the final merge and release as time allows for him.

I did one last smokescreen through the Sandcastle examples and they look fine. Thanks @jasonbeverage!
I'll try to get to https://github.com/AnalyticalGraphicsInc/cesium/issues/7875 this month so SDF can look even better,

Awesome, thanks @lilleyse!


User is able to set the schedule scan and alerting for cluster Scans when the CIS v2 app has not been upgraded to the latest version

Upgrade use case from 2.5.3 to 2.5-head - commit id: baf4867c

On 2.5.3, deploy a custom cluster.
Deploy CIS v2 app
Run cluster scans - rke-permissive, rke-hardened, and cis 1.5 profiles
Upgrade rancher to 2.5-head
Create a cluster scan, user is able to set the schedule scan and alerting on the UI. (doesnt work though as a cis v2 app upgrade is required).

Expected:
User should not allowed to configure alerts and scheduled scans unless the app has been upgraded
Note:
User should NOT be able to see/perform actions related to the latest CIS version when in an earlier CIS v2 app version

On 2.5-head - commit id: baf4867

Deploy a CIS v2 app version 1.0.2
Deploy a CIS scan.
No alerts/cron for schedule scan is seen.
Only the scan profile is available

Config page:


Fixing issues in setting up the dev container

While setting up the development environment for this extension I recognized that the devcontainer is not working with recent versions/images. Therefore I did the following adjustments.

Added missing apt packages tzdata and g++
Configures installation of requirements to ignore disttool installation
changed the default logger level to warning to better follow the installation packet

Please consider this for pulling into the master branch

This was fixed in https://github.com/custom-components/wienerlinien/commit/11c9b0f2fbd4031ab87b802512b92c834c889e0f your branch is outdated


when try use FetchConfirmations

GenerateSteamGuardCode work perfect, but fetchconfirmations send err

Get steammobile://lostauth: unsupported protocol scheme "steammobile"

Use refresh session


Expanding support for global variable objects.

This is something which was lacking in the C version, according to the current documentation yara-x only supports "global external variable" but not "external object" which would include arrays and structures for richer data enrichment.
This could be really great for modules that would want to keep the same name convention of VirusTotal live hunting to make rules interoperable for example variables like vt.behaviour.command_executions or vt.behaviour.modules_loaded which are only accessible as an array via the for loop keyword. But also variables under specific structures such as vt.behaviour.
More information about existing issues which were not addressable in the current C version of yara:
Support for EXTERNAL OBJECT_TYPE_ARRAY and OBJECT_TYPE_STRUCTURE
Exporting yr_object_create() to enable custom structures?

This is something that I have in mind for future releases. I'm currently focused in releasing a version that has feature parity with yara, but more advanced features like this are in the plan.

Excellent! Amazing job as usual @plusvic !


FileSystemWatcher Changed event is raised twice

REF.: http://stackoverflow.com/questions/1764809/filesystemwatcher-changed-event-is-raised-twice
Are there any working workarounds for the bug available? I am experiencing this in .net Framework 4.5.2. Maybe fixed in later versions?

I'm unfamiliar with this issue. Did you try one of the workarounds in the SO page?

Please re-activate if this is still an issue.

Thank you for the reply. Yes I tried every thing.
Just tried to create a reproducable example but failed 😞. I was not able to reproduce this behavior on my machine. In fact I am getting System.IO.IOExceptions at https://github.com/s-a/dot-net-filesystemwatch-experiment/blob/bb2753d3e2072654d4ee4e736ace8c8565b0a238/Program.cs#L109 on our production servers. The main difference is that this this custom filewatcher class is implemented in a Windows service executable.
I noticed this behaviour years ago to face this again now.
A user on SO wrote

I am afraid that this is a well-known bug/feature of the FileSystemWatcher class. This is from the documentation of the class:  ...

So I guess I am not the only person having trouble with this. I just thought maybe it is not a .NET problem. Maybe it has something to do with Windows messaging on specific servers.
I need to investigate more time to explore behavior of code in a Windows service. Anyway any help would be wonderful. So maybe we can hold this issue open for a while? A coder reading this could have an idea to help.

/cc @terrajobst @stephentoub

@richlander
Can this be reopened?
This is still an issue on .net Framework 4.6
Watching a specific file, I get 2 OnFileChanged event notifications (using MS NotePad).
Both FileSystemEventArgs args say ChangeType = Changed
I believe that one is for File Date changed. And one is for LastWrite changed. (could be other change types)
But there is no way to tell what the change type is from the FileSystemEventArgs arg.
My code uses
watcher.NotifyFilter = NotifyFilters.LastWrite;
It would be nice if the FileSystemEventArgs would specify  "change type" (ie LastWrite, FileDate, etc)
Then the program could just process the event it cares about and ignore the rest.

@SmokinLeather are you able to reproduce this with this code? https://github.com/s-a/dot-net-filesystemwatch-experiment/
What Windows Version are you using?

@s-a
Thanks. I'll take a look at that experiment.
My test code is very simple. It's a windows forms app. I start it, then open the text file in Notepad. Make and edit to the textfile and save it. Then  consistently the OnFileChanged event fires two times, every time I save the text file. The FileSystemEventArgs are identical each time.
On Windows 10, Home Edition. Creator Update.
.Net Framework 4.6
     private void FileWatcherSetup(string path)
        {
            FileSystemWatcher watcher = new FileSystemWatcher();
            string folderName = Path.GetDirectoryName(path);
            string fileName = Path.GetFileName(path);
            watcher.Path = folderName;

            watcher.NotifyFilter = NotifyFilters.LastWrite;
            watcher.Filter = fileName;
            watcher.Changed += new FileSystemEventHandler(OnFileChanged);
            watcher.EnableRaisingEvents = true;
        }
 int ctr = 0;
 private void OnFileChanged(object source, FileSystemEventArgs e)
        {
            Console.WriteLine("OnFileChanged" + ctr);
		ctr++;
        }

        public Form1()
        {
		  string  aFilepath = @"C:\Test\TestFile.txt";
            FileWatcherSetup(aFilepath);
	}

I can confirm the behavior @SmokinLeather described. His efforts brought me to test this line of code at https://github.com/s-a/dot-net-filesystemwatch-experiment/blob/master/Program.cs#L132 which fires twice and is definitely reproducable on my system running on Microsoft Windows [Version 10.0.10586] using .NET Framework 4.5.2.
I am sure construe underlying issue @SmokinLeather described will lead to the bug I originally reported.
So @terrajobst @stephentoub @richlander please reopen this issue.

Only the changed event is execute twice, didn't try the .net core version.
Example executed in Linqpad 4:
void Main()
{
    Watch (GetTestDirectory(), "*.txt", true);
}

void Watch (string path, string filter, bool includeSubDirs)
{
using (var watcher = new FileSystemWatcher (path, filter))
{
    watcher.Created += FileCreatedChangedDeleted;
    watcher.Changed += FileCreatedChangedDeleted;
    watcher.Deleted += FileCreatedChangedDeleted;
    watcher.Renamed += FileRenamed;
    watcher.Error += FileError;
    watcher.IncludeSubdirectories = includeSubDirs;
    watcher.EnableRaisingEvents = true;
    Console.WriteLine ("Listening for events - press <enter> to end");
    Console.ReadLine();
    }
    }
    void FileCreatedChangedDeleted (object o, FileSystemEventArgs e)
    { Console.WriteLine ("File {0} has been {1}", e.FullPath, e.ChangeType);}

    void FileRenamed (object o, RenamedEventArgs e)
    { Console.WriteLine ("Renamed: {0}->{1}", e.OldFullPath, e.FullPath);}

    void FileError (object o, ErrorEventArgs e)
    { Console.WriteLine ("Error: " + e.GetException().Message);}

// Define other methods and classes here
string GetTestDirectory(){ return RuntimeInformation.IsOSPlatform (OSPlatform.Windows)? @"C:\Temp": "/tmp";}


I cannot access to to the rigid body's rotation, when autoBalance is desactivated

When the autoBalance is desactivated, I cannot access to the rigid body's rotation. I need this value, because I want to send the Avatar's transforms via WebSocekts. Is there a way to access to the rotation of the Ecctrl?. If I activate the autoBalance, I get an error, that is that the avatar in low hardware computer rotates without control on the X axis.
return (
<Ecctrl
ref={avatarBodyRef}
debug={false}
camInitDis={-1}
camMaxDis={-1}
camTargetPos={{ x: 0, y: 0.5, z: 0 }}
turnSpeed={16}
maxVelLimit={3}
position={[0, 2, 0]}
camMoveSpeed={2}
autoBalance={false}
>

I solved yet this problem. I had to configure autoBalance={true} and  enabledRotations={[false, true, false]} in the Ecctrl. With this solution, when the computer does not have good FPS the avatar does not rotate without control on the X and Z axis.


Fix: User Validation in Password Reset Process.

At present, there is no validation check in place when resetting a password to verify whether the user exists in the database or not.
To improve this, we should implement a validation check when the user clicks on the "Reset Password" button. This check will verify whether the user exists in the database. If the user is not found, a pop-up message will be displayed, saying "No such email exists. Please sign up on our website." This message will also include a button that, when clicked, will redirect the user to the signup page.

How do you propose to do this?

When the user clicks the "Reset Password" button, an API request will be initiated to determine whether the user exists in the database. If the API call response confirms the user's existence (i.e., returns true), they will be redirected to the password reset page. However, if the API response indicates that the user is not found(i.e., returns false), a popup message will be displayed stating above mentioned message.

@satvik225 How do you propose to do this?

@jain-anshika
Would it be helpful if I provided more details?


Set the Integration/Example version number in the Version GH Action

The version GH action updates the tiki-sdk-android build.gradle version number. This version is used by the IntegrationTests and ExampleApp projects to get tiki-sdk-android dependency locally and is defined by the developer. It can lead to version mismatch during the execution of integration tests and the example app will be using the wrong version.
Proposed solution
Update the tiki-sd-android dependency version in build.gradle files for IntegrationTests and ExampleApp with the version GH action

outdated


Fix CMake build on Windows platform with MinGW toolchain

Description
Add additional fix to the issue #1496 that fix CMake build on Windows platform with MinGW toolchain.
Status
READY
Requires Backporting
NO
Migrations
NO
Steps to test or reproduce

Windows 10, CMake 3.13, MinGW64-x86_64 - build success (without the fix it fails)
macOS 10.14, CMake 3.11, Apple Clang 10.0 - always succeeded

Closing in favor of https://github.com/ARMmbed/mbedtls/pull/2473 which fixes the same issue as this PR, https://github.com/ARMmbed/mbedtls/issues/1496.


Replace hard-coded auth token valid duration with value from env variable

Fix issue 640

I will split this PR into little PRs


pact-consumer 0.7.6 compile is broken

After updating dependencies with cargo update, pact-consumer 0.7.6 fails to build. Transitive dependency to pact_matching has been bumped to 0.9.4, and pact-consumer is incompatible with it. Lots of compile errors, the first one is:
   Compiling pact_consumer v0.7.6
error[E0432]: unresolved import `pact_matching::models::matchingrules::RuleLogic`
 --> /Users/audun/.cargo/registry/src/github.com-1ecc6299db9ec823/pact_consumer-0.7.6/src/patterns/special_rules.rs:3:80
  |
3 | use pact_matching::models::matchingrules::{MatchingRule, MatchingRuleCategory, RuleLogic};
  |                                                                                ^^^^^^^^^ no `RuleLogic` in `models::matchingrules`

I think semver has been violated somewhere in the inter-dependency of the various pact-reference crates. In the future, I think problems like this could be minimized if all crates are always released simultaneously. I know I have encountered similar problems before for pact-consumer (this crate appears to be a bit less "prioritized" than the others)

I don’t really have the context for the rust libs, but I think semver isn’t violated, because these are 0.x.x, which allows arbitrary breaking changes (this clearly isn’t ideal, as you point out)
@uglyog can we get a v1 release for the rust pieces so that we can communicate breaking changes clearer?
Also any way to orchestrate the builds / releases to reduce the risk of breaking changes is a win in my book.

For 0.x.y packages, a changed x will denote a breaking change, at least in the Cargo interpretation of semver. cargo update will only bump to the latest y while keeping x the same. Cargo doc explains it better than me:
https://doc.rust-lang.org/cargo/reference/specifying-dependencies.html#caret-requirements

Oh, that's interesting! That's a widening of the semver spec which just says:

Major version zero (0.y.z) is for initial development. Anything MAY change at any time. The public API SHOULD NOT be considered stable.

Looks like the Cargo docs mention this explicitly:

This compatibility convention is different from SemVer in the way it treats versions before 1.0.0. While SemVer says there is no compatibility before 1.0.0, Cargo considers 0.x.y to be compatible with 0.x.z, where y ≥ z and x > 0.

I hadn't noticed before that ^ ~ etc for selecting versions aren't part of the semver spec - meaning that they could potentially mean different things in (say) Cargo and npm. However, it looks like npm follows the same convention as cargo- see here.
Anyway, I'll stop hijacking this issue.

Sorry about this, I haven't released the pact-consumer crate. I'm doing that now.
There has been a bit of churn while we're trying to get a good FFI interface. I don't think things will have to change much from here on, as we have moved all the FFI functions into a separate library and extracted all the models from the pact-matching one.
With hindsight, we should have bumped the minor versions of all the dependent crates, but it is now done and can't be changed.

With pact-js we automate the version bumping from the commit history, which helps them be correct. It’s not a perfect solution, because you have to remember to mark breaking changes in the commit, but it does help reduce the risk. Would something like that help here?

No, I don't think so. The minor versions had to be bumped.

0.7.7 is released

The minor versions had to be bumped.

Yes, that's what I'm saying - we have tooling that reads the commit history and bumps the appropriate part of the version. It requires using conventional commits), but then you can automate the process.
On a release, all commits since the last release are read:
After 1.0.0,  If there's a commit that contains BREAKING CHANGE the major version, is bumped, otherwise if there's a commit that starts with feat: or feat(whatever): then the minor version is bumped, otherwise it's a patch version.
Before 1.0.0, I think the behaviour is BREAKING CHANGE is a minor bump as in the rust/npm docs, but I'm not sure (but since we are exposing this publicly, we should technically be at 1.0.0).
Look like this rust crate does a similar thing: https://crates.io/crates/convco

This is the tool we use https://github.com/conventional-changelog/standard-version
It can be run with npx standard-version, and configured to bump files that aren't package.json, but you'd probably want something natively rust or at least rust toolchain aware.

0.7.7 works, thanks.


Error

How fix this nullpoint
com.vikramezhil.droidspeech.DroidSpeech.startLanguageReceiver(DroidSpeech.java:104)

https://github.com/vikramezhil/DroidSpeech/pull/39
Added fix


[Slack] Cannot login

Extension
https://www.raycast.com/mommertf/slack
Raycast Version
1.83.2
macOS Version
No response
Description
Error:
FetchError: request to https://slack.oauth.raycast.com/token failed, reason: unable to get local issuer certificate

    at withAccessToken(H5)
_r:index.js:8:2593
    at ray-navigation-stack
Eo:index.js:8:2094

Steps To Reproduce

Open raycast
Try to use slack related features
Login to slack
Confirm slack permission disclaimer
Return to raycast
Breaks

Current Behaviour
No response
Expected Behaviour
No response

Are you using some kind of VPN/firewall/proxy?

I am facing the same, with or without VPN

Makes me think of this issue: https://github.com/raycast/extensions/issues/13301. Are you sure there's nothing else tampering with your network?

Yeah, nothing. I am getting this in the console error.

@thomaslombart
The URL parameters show the state field is empty. If this information may help with debugging.

That's weird. Does it also happen for the URL if you copy it from the OAuth screen?


Read-Timeout not applied with Apache Http Components and no-SSL

When using Apache Http Components with an http (non-SSL) Vault URI, the read-timeout option is not applied to the HttpClientBuilder.  This results in the Apache-default of 3-minutes always being used, regardless of the settings provided via Spring Boot.
I've created a trivial example project to demonstrate the issue here: https://github.com/p120ph37/spring-vault-test
I believe the fix would be to add .setResponseTimeout(Timeout.ofMilliseconds(options.getReadTimeout().toMillis())) here:
https://github.com/spring-projects/spring-vault/blob/542786151495f1bde4d51434c0067705e58f62f1/spring-vault-core/src/main/java/org/springframework/vault/client/ClientHttpRequestFactoryFactory.java#L329-L333
I have prototyped this fix in the FixedClientFactoryWrapper in my test suite -- test that fix by uncommenting this line: https://github.com/p120ph37/spring-vault-test/blob/0ffcea4bc2d7401721f29b419c9596c91827023b/src/test/java/spring/vault/test/TimeoutTests.java#L43

As a temporary workaround for Spring Boot applications that need to support timeouts on HTTP Vault requests, adding this bean to your application will force the use of the JDK request factory rather than the Apache one:
        // This is a workaround for https://github.com/spring-projects/spring-vault/issues/861
        @Bean
        @Order(Ordered.HIGHEST_PRECEDENCE)
        org.springframework.vault.client.RestTemplateCustomizer restTemplateCustomizer(VaultProperties vp) {
            return rt -> {
                if(vp.getSsl().getKeyStore() == null && vp.getSsl().getTrustStore() == null) {
                    SimpleClientHttpRequestFactory rf = new SimpleClientHttpRequestFactory();
                    rf.setConnectTimeout(vp.getConnectionTimeout());
                    rf.setReadTimeout(vp.getReadTimeout());
                    rt.setRequestFactory(rf);
                }
            };
        }

Thanks for the report. We should fix that issue in HttpComponents.getHttpClientBuilder(…). Since you already had a look into the issue, care to submit a pull request?

I've stumbled upon the same problem and found this issue. I've submitted a PR


3.3 Milestone 2 does not start successfully

I'm using the latest ArangoDB of the respective release series:

[ x ] 3.3 Milestone 2 Community Edition

Mode:

[ x ] Cluster
There are 2 vms, each with 2 primary db servers and 2 coordinators. There are 5 agents, 3 on 1 vm, and 2 on the other

Storage-Engine:

[ x ] mmfiles

On this operating system:

[ x ] RedHat .rpm

The following problem occurs:
Using the same configuration that works for 3.2.2, after starting the agency, coordinators and db servers fail to completely startup. The processes run, but they never start listening on their ports. The last log from the db server is
2017-11-07T02:02:27Z [11599] INFO {cluster} Starting up with role PRIMARY
In the logs, you can see looping repeating requests from each of the db servers and coordinators that look like this:
2017-11-07T02:05:29Z [11386] INFO {requests} "http-request-end","0x7facfc6eba90","dbserver2:port","POST","HTTP/1.1",412,134,15,"/_api/agency/write",0.000139
2017-11-07T02:05:29Z [11386] INFO {requests} "http-request-end","0x7facfc6eba90","dbserver2:port","POST","HTTP/1.1",200,21,30,"/_api/agency/read",0.000062
2017-11-07T02:05:29Z [11386] INFO {requests} "http-request-end","0x7facfc6eba90","dbserver2:port","POST","HTTP/1.1",200,32,43,"/_api/agency/read",0.000050
2017-11-07T02:05:29Z [11280] INFO {requests} "http-request-end","0x7fed9c340a10","dbserver2:port","POST","HTTP/1.1",307,134,0,"/_api/agency/write",0.000121
Instead I would be expecting: them to startup

Hi,
can you please try to replace /usr/bin/arangodb by https://github.com/arangodb-helper/arangodb/releases/download/0.10.2/arangodb-linux-amd64 and check back whether its then starting properly?

It sounds as if you are not using the starter arangodb. And indeed, 3.3 Milestone 2 has a bug which does not allow startup with the exact command line options that used to work for 3.2.2. This will be fixed in newer releases. A restart with data should work (after upgrading the data directories), the start of a new cluster will not work.
In the meantime, can you please send your startup setup, it is probably enough to remove the options --cluster.my-local-info to start up a new cluster.
Alternatively, you could use the starter tool arangodb, which is described here:
https://github.com/arangodb-helper/arangodb
and is included with recent releases. Note however, that the starter included in the Milestone release suffers from the same bug. If you want to try this, you should download the latest arangodb executable exactly as @dothebart suggested.

If all this fails, please post the exact way you try to start up the cluster and if you are starting a new one or try to restart an old one.

removing cluster.my-local-info from the coordinators and db servers worked. (Not sure if removing from all was necessary or not), replacing /usr/bin/arangodb had no effect. Unfortunately, im running into a new issue when creating the databases/initializing the collections. (Looks eerily familiar to the same issue i reported here: https://github.com/arangodb/arangodb/issues/3598)
ERROR {cluster} Timeout in _create collection: database: userInfo, collId:3010020 {big json object}
2017-11-07T18:56:48Z [18546] ERROR In database "mydb": Executing task #1 (setupGraphs: setup _graphs collection) failed with exception: ArangoError 1457: timeout in cluster operation ArangoError: timeout in cluster operation
2017-11-07T18:56:48Z [18546] ERROR     at createSystemCollection (/usr/share/arangodb3/js/server/upgrade-database.js:148:14)
2017-11-07T18:56:48Z [18546] ERROR     at Object.task (/usr/share/arangodb3/js/server/upgrade-database.js:442:16)
2017-11-07T18:56:48Z [18546] ERROR     at runTasks (/usr/share/arangodb3/js/server/upgrade-database.js:271:27)
2017-11-07T18:56:48Z [18546] ERROR     at upgradeDatabase (/usr/share/arangodb3/js/server/upgrade-database.js:342:16)
2017-11-07T18:56:48Z [18546] ERROR     at upgrade (/usr/share/arangodb3/js/server/upgrade-database.js:784:12)
2017-11-07T18:56:48Z [18546] ERROR     at /usr/share/arangodb3/js/server/upgrade-database.js:799:10
2017-11-07T18:56:48Z [18546] ERROR     at /usr/share/arangodb3/js/server/upgrade-database.js:800:2
2017-11-07T18:56:48Z [18546] ERROR     at Object.exports.loadStartup (/usr/share/arangodb3/js/server/bootstrap/modules/internal.js:291:20)
2017-11-07T18:56:48Z [18546] ERROR     at /usr/share/arangodb3/js/server/bootstrap/local-database.js:37:25
2017-11-07T18:56:48Z [18546] ERROR     at /usr/share/arangodb3/js/server/bootstrap/local-database.js:56:2
2017-11-07T18:56:48Z [18546] ERROR In database "mydb": Executing task #1 (setupGraphs: setup _graphs collection) failed. Aborting init procedure.
2017-11-07T18:56:48Z [18546] ERROR In database "mydb": Please fix the problem and try starting the server again.
2017-11-07T18:57:48Z [18436] WARNING {v8} giving up waiting for unused V8 context after 60.000000 s
2017-11-07T18:57:48Z [18436] WARNING {heartbeat} DBServerAgencySync::execute took 60.086166 s to execute handlePlanChange
I was able to get it up and running by creating the databases through the web ui instead of javascript + arangosh. The javascript is something like this
// Create the databases
db._createDatabase("db1");
db._createDatabase("db2");
db._createDatabase("db3");

Hi @ldap4life ,
Thanks for opening this ticket
So as far as I understand:

the original problem of this ticket (startup problem) has been solved by using the following workaround: removing the option --cluster.my-local-info. In 3.3-beta1 the problem does not occur anymore
the second problem (db creation error) cannot be reproduced with 3.3-beta1

Issue #3598 is still open and we can discuss more in that ticket
If all the above is correct - I am wondering if we can now close this ticket, or if there are open action items
Many Thanks,

Correct, closing: fix for the original issue was removing
removing the option --cluster.my-local-info (That problem may or may not happen in 3.3-beta1)
the second problem was fixed by using 3.3-beta1


Docs: Bring Pagination above Feedback/Support hierarchy

At the bottom of each documentation page there is a Feedback component, a link to Dev Resources, and then Pagination to the next section.
I notice when I'm on these pages I have to look for the pagination buttons, but I think they could be super helpful in letting users know there's more content to explore.
I propose adjusting the hierarchy of this section and bringing the pagination above the Feedback component.

moved to: https://github.com/near/docs/issues/2080


fix(searchfield): show clear btn after submit when input has no value

This PR fixes the following issue: https://github.com/edx/paragon/issues/356
Now, the SearchField component keeps track of when a search has been submitted. The clear button will be rendered if a search has been submitted regardless of whether the input has a non-empty value. The hasSubmitted state is reset to false on clear.
I've also included a minor refactor to remove the use of componentWillReceiveProps (in favor of componentDidUpdate) as this lifecycle method will be become deprecated in React. I also moved the prop types configuration to the bottom of the file.

Coverage increased (+0.005%) to 99.057% when pulling 17d933e69dfb2638420a8d25970875df5f933536 on astankiewicz/searchfield-remove-disable into 1fbbefe1936ba72577adad9af10272067f2f2579 on master.

:tada: This PR is included in version 3.7.1 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Support error handling for start/stop trace server

Signed-off-by: Ankush Tyagi<EMAIL_ADDRESS>This PR adds error handling for the start/stop trace server. It also prevents the user from accidentally killing a process through the preferences settings.
Steps to test:

Provide an incorrect path for the executable and click the start trace server button.
Provide a busy port in the preferences settings and click the start trace server button.
You should see a Toast message with a detailed error.

I think we're still running into some problems with the variable time of the pinging in the TraceServerConnectionStatusService when the connection to the server is slow. I'd propose the following changes to the TraceServerConnectionStatusService:

replace private scheduledPing: number | undefined; with private lastPing = new Deferred();
change the schedulePing function to the following:

    protected schedulePing(): void {
        const ping = async () => {
            this.lastPing.reject();
            this.lastPing = new Deferred();
            try {
                await Promise.race([this.tspClient.fetchExperiments(), this.lastPing.promise]);
                this.updateStatus(true);
            } catch (e) {
                this.updateStatus(false);
                this.logger.trace(e);
            }
        };

        ping();

        setInterval(ping, this.options.offlineTimeout);
    }

The current code still allows up to a 9 second gap between state updates, but this should guarantee at least one state update in every five-second period after startup, though the actual gap between updates may vary.

I think we're still running into some problems with the variable time of the pinging in the TraceServerConnectionStatusService when the connection to the server is slow. I'd propose the following changes to the TraceServerConnectionStatusService:

replace private scheduledPing: number | undefined; with private lastPing = new Deferred();
change the schedulePing function to the following:

    protected schedulePing(): void {
        const ping = async () => {
            this.lastPing.reject();
            this.lastPing = new Deferred();
            try {
                await Promise.race([this.tspClient.fetchExperiments(), this.lastPing.promise]);
                this.updateStatus(true);
            } catch (e) {
                this.updateStatus(false);
                this.logger.trace(e);
            }
        };

        ping();

        setInterval(ping, this.options.offlineTimeout);
    }

The current code still allows up to a 9 second gap between state updates, but this should guarantee at least one state update in every five-second period after startup, though the actual gap between updates may vary.

I think we're still running into some problems with the variable time of the pinging in the TraceServerConnectionStatusService when the connection to the server is slow. The current code still allows up to a 9 second gap between state updates, but it's desirable to report more often. I'd propose the following changes to the TraceServerConnectionStatusService:

replace private scheduledPing: number | undefined; with private lastPing = new Deferred();
change the schedulePing function to the following:

    protected schedulePing(): void {
        const ping = async () => {
            this.lastPing.reject();
            this.lastPing = new Deferred();
            try {
                await Promise.race([this.tspClient.fetchExperiments(), this.lastPing.promise]);
                this.updateStatus(true);
            } catch (e) {
                this.updateStatus(false);
                this.logger.trace(e);
            }
        };

        ping();

        setInterval(ping, this.options.offlineTimeout);
    }

This version will report in every five-second period after startup, although the actual time between updates may vary.
Alternatively, this code will report status (more or less) exactly every five seconds:
    protected schedulePing(): void {
        let timeout = new Deferred();
        let lastPing: Promise<unknown> = Promise.reject();

        const ping = async () => {
            timeout.reject();
            timeout = new Deferred();
            try {
                await lastPing;
                this.updateStatus(true);
            } catch (e) {
                this.updateStatus(false);
                this.logger.trace(e);
            } finally {
                lastPing = Promise.race([this.tspClient.fetchExperiments(), timeout.promise]);
            }
        };

        ping();

        setInterval(ping, this.options.offlineTimeout);
    }

That has the benefit of regularity, but the downside that it's no faster for success than for failure.

Bernd pointed out some issues with gitpod. It looks like we were running into timeout issues likely due to the slowness of the start and stop process on Gitpod. We decided to modify the changes proposed by @colin-grant-work in this patch itself.
Note: One change to the assumption is that if we do not get an error or exit within 2 seconds, we are considering it as a success.

I think we're still running into some problems with the variable time of the pinging in the TraceServerConnectionStatusService when the connection to the server is slow. The current code still allows up to a 9 second gap between state updates, but it's desirable to report more often. I'd propose the following changes to the TraceServerConnectionStatusService:

replace private scheduledPing: number | undefined; with private lastPing = new Deferred();
change the schedulePing function to the following:

    protected schedulePing(): void {
        const ping = async () => {
            this.lastPing.reject();
            this.lastPing = new Deferred();
            try {
                await Promise.race([this.tspClient.fetchExperiments(), this.lastPing.promise]);
                this.updateStatus(true);
            } catch (e) {
                this.updateStatus(false);
                this.logger.trace(e);
            }
        };

        ping();

        setInterval(ping, this.options.offlineTimeout);
    }

This version will report in every five-second period after startup, although the actual time between updates may vary.
Alternatively, this code will report status (more or less) exactly every five seconds:
    protected schedulePing(): void {
        let timeout = new Deferred();
        let lastPing: Promise<unknown> = Promise.reject();

        const ping = async () => {
            timeout.reject();
            timeout = new Deferred();
            try {
                await lastPing;
                this.updateStatus(true);
            } catch (e) {
                this.updateStatus(false);
                this.logger.trace(e);
            } finally {
                lastPing = Promise.race([this.tspClient.fetchExperiments(), timeout.promise]);
            }
        };

        ping();

        setInterval(ping, this.options.offlineTimeout);
    }

That has the benefit of regularity, but the downside that it's no faster for success than for failure.

Bernd pointed out some issues with gitpod. It looks like we were running into timeout issues likely due to the slowness of the start and stop process on Gitpod. We decided to modify the changes proposed by @colin-grant-work in this patch itself.
Note: One change to the assumption is that if we do not get an error or exit within 2 seconds, we are considering it as a success.

I tried pressing "Start trace server" right after stopping it. After 10 seconds I got a toaster message "Failed to start the trace server: no such file or directory. Please make sure that the path is correct in Trace Viewer settings and retry".
Not only is the path setting correct and the file exists, but 60 seconds later I can see that the server is started and connection is established.
This reproduces only intermittently.

I tried pressing "Start trace server" right after stopping it. After 10 seconds I got a toaster message "Failed to start the trace server: no such file or directory. Please make sure that the path is correct in Trace Viewer settings and retry".
Not only is the path setting correct and the file exists, but 60 seconds later I can see that the server is started and connection is established.
This reproduces only intermittently.

I tried pressing "Start trace server" right after stopping it. After 10 seconds I got a toaster message "Failed to start the trace server: no such file or directory. Please make sure that the path is correct in Trace Viewer settings and retry".
Not only is the path setting correct and the file exists, but 60 seconds later I can see that the server is started and connection is established.
This reproduces only intermittently.

@PatrickTasse  Yes, I've seen it. We'll increase the timeout. In a separate patch we'll revise the startup procedure and error handling. I'd like to merge this one because it fixes the stop procedure by using a npm library and the PID.

I tried pressing "Start trace server" right after stopping it. After 10 seconds I got a toaster message "Failed to start the trace server: no such file or directory. Please make sure that the path is correct in Trace Viewer settings and retry".
Not only is the path setting correct and the file exists, but 60 seconds later I can see that the server is started and connection is established.
This reproduces only intermittently.

@PatrickTasse  Yes, I've seen it. We'll increase the timeout. In a separate patch we'll revise the startup procedure and error handling. I'd like to merge this one because it fixes the stop procedure by using a npm library and the PID.