Update sumneko lua docs

cc: @clason

Thanks! Maybe we could add for now a notice that if sumneko was previously installed via :LspInstall, you should set sumneko_root_path = vim.fn.stdpath('cache')..'/lspconfig/sumneko_lua/lua-language-server'?
(make it as frictionless as possible to migrate for people whose cheese has just been moved ;))

Thanks! Maybe we could add for now a notice that if sumneko was previously installed via :LspInstall, you should set sumneko_root_path = vim.fn.stdpath('cache')..'/lspconfig/sumneko_lua/lua-language-server'?
(make it as frictionless as possible to migrate for people whose cheese has just been moved ;))

Added, let me know if this looks good to you and I'll merge.

Added, let me know if this looks good to you and I'll merge.

Close :) You're using sumneko_root_path without defining it first (and the comment about it is after the use -- and uses the wrong variable ;)).
How about
 -- set the path to the sumneko installation; if you previously installed via the now deprecated :LspInstall, use
local sumneko_root_path = vim.fn.stdpath('cache')..'/lspconfig/sumneko_lua/lua-language-server'
local sumneko_binary ="/path/to/lua-language-server"..sumneko_root_path.."/bin/"..system_name.."/lua-language-server"

Close :) You're using sumneko_root_path without defining it first (and the comment about it is after the use -- and uses the wrong variable ;)).
How about
 -- set the path to the sumneko installation; if you previously installed via the now deprecated :LspInstall, use
local sumneko_root_path = vim.fn.stdpath('cache')..'/lspconfig/sumneko_lua/lua-language-server'
local sumneko_binary ="/path/to/lua-language-server"..sumneko_root_path.."/bin/"..system_name.."/lua-language-server"

Just to clarify, this isn't the sumneko_root_path, this is the binary
vim.fn.stdpath('cache')..'/lspconfig/sumneko_lua/lua-language-server'
This is an alternative path to the binary if you install somewhere else
"/path/to/lua-language-server"..sumneko_root_path.."/bin/"..system_name.."/lua-language-server"

Just to clarify, this isn't the sumneko_root_path, this is the binary
vim.fn.stdpath('cache')..'/lspconfig/sumneko_lua/lua-language-server'
This is an alternative path to the binary if you install somewhere else
"/path/to/lua-language-server"..sumneko_root_path.."/bin/"..system_name.."/lua-language-server"


Need a link to the IDataModelScriptProvider topic

https://docs.microsoft.com/en-us/windows-hardware/drivers/ddi/content/dbgmodel/nn-dbgmodel-idatamodelscriptprovider

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

ID: 6249d1b7-8bfa-991a-0771-1ff58dc4a297
Version Independent ID: e8989fb0-15f7-09ff-5dc6-b414a881fbd9
Content: IDataModelScriptManager::RegisterScriptProvider (dbgmodel.h) - Windows drivers
Content Source: wdk-ddi-src/content/dbgmodel/nf-dbgmodel-idatamodelscriptmanager-registerscriptprovider.md
Product: windows-hardware
Technology: windows-devices
GitHub Login: @DOMARS
Microsoft Alias: domars

@jazzdelightsme - I have added the link. I will close this issue when the changes are live. You are always welcome to send a PR for changes like this.

@jazzdelightsme - The topic updates are live, so closing this issue. Thanks for the issue and your interest in the DbgModel docs.


Correction for raw affiliation Sciences po Rennes (FR)

Correction needed for raw affiliation Sciences po Rennes (FR)
raw_affiliation_name: Sciences po Rennes (FR)
new_rors: 01fmctt82
previous_rors: 05fe7ax82
works_examples: W3134094778;W3130132475

This issue was accepted and ingested by the OpenAlex team on 2024-10-10. The new affiliations should be visible within the next 7 days.


[SEDONA-227] Implemented Python geometry serializer as a native extension

Did you read the Contributor Guide?

Yes, I have read Contributor Rules and Contributor Development Guide

Is this PR related to a JIRA ticket?

Yes, the URL of the associated JIRA ticket is https://issues.apache.org/jira/projects/SEDONA/issues/SEDONA-227. The PR name follows the format [SEDONA-XXX] my subject.

What changes were proposed in this PR?
This patch provides a Python geometry serializer implemented as a native extension. The original pure python serializer was still kept around as a fallback implementation when the native extension failed to load.
Please be acknowledged that the existence of native extensions will complicate the release process of apache-sedona python packages, since we have to build wheels for various CPython versions and platforms. There is a newly added Github Action for building wheels as a reference approach.
For platforms not covered by prebuilt wheels, users can easily install the package using the source distribution since the newly added extension does not require any third-party libraries to build.
How was this patch tested?
Multi-platform Compatibility
We've added a Github Action for testing the native extension on various platforms. We've also run tests on Apple M1, so it is also expected to work on various ARM64 platforms.
Performance
This is the result of running benchmarking code in https://github.com/apache/sedona/pull/745 on an ECS instance with Intel(R) Xeon(R) Platinum 8269CY CPU @ 2.50GHz.

No, this PR does not affect any public API so no need to change the docs.

The Github Action for building wheels is unable to run. Seems that Github does not allow running cibuildwheel on ASF projects.

Just create https://issues.apache.org/jira/browse/INFRA-24203 Let's see if the ASF infra team will allow this GitHub action.

@douglasdennis @umartin Doug and Martin, since you were following the new serializer improvement, any comment on this PR?

@douglasdennis @umartin Doug and Martin, since you were following the new serializer improvement, any comment on this PR?

I haven't worked with C in 20 years, but from my understanding, everything looks good. I don't have any objections to merging.

@Kontinuation Will this work out of the box with a pip install? Like, once this gets pushed to pypi, will I be able to just do pip install apache-sedona and I'll get the speeded up version?

@Kontinuation Will this work out of the box with a pip install? Like, once this gets pushed to pypi, will I be able to just do pip install apache-sedona and I'll get the speeded up version?

In most cases, yes. We will release precompiled wheels for commonly used platforms.
You'll still encounter problems on platforms not having matching wheel releases, such as Windows running on ARM64. If you do not have toolchains installed on your system, pip install won't be able to build the extension from the source release.

@Kontinuation Will this work out of the box with a pip install? Like, once this gets pushed to pypi, will I be able to just do pip install apache-sedona and I'll get the speeded up version?

In most cases, yes. We will release precompiled wheels for commonly used platforms.
You'll still encounter problems on platforms not having matching wheel releases, such as Windows running on ARM64. If you do not have toolchains installed on your system, pip install won't be able to build the extension from the source release.

That's awesome! I'm excited to be able to use it. Thanks for putting so much work into this, this will all help me out quite a bit.


input.boolean "Failed to Fetch"

On Alexa, when trying to switch a boolean item I get it to change but get a erro "item is not responding", on the web interface I get a:

on the log is like the bridge got rebooted:
           ^
SynchronousTransactionConflictError: Cannot lock 693312ca0f3e4900a507ab828b95e735.aggregator.input_boolean_b_tv_sala.onOff.state synchronously
    at ResourceSet.acquireLocksSync (file:///usr/local/lib/node_modules/home-assistant-matter-hub/node_modules/@matter/node/dist/esm/behavior/state/transaction/ResourceSet.js:66:13)
    at Tx.beginSync (file:///usr/local/lib/node_modules/home-assistant-matter-hub/node_modules/@matter/node/dist/esm/behavior/state/transaction/Tx.js:198:32)
    at startWrite (file:///usr/local/lib/node_modules/home-assistant-matter-hub/node_modules/@matter/node/dist/esm/behavior/state/managed/Datasource.js:192:17)
    at Object.change (file:///usr/local/lib/node_modules/home-assistant-matter-hub/node_modules/@matter/node/dist/esm/behavior/state/managed/Datasource.js:145:7)
    at OnOff$State.set [as onOff] (file:///usr/local/lib/node_modules/home-assistant-matter-hub/node_modules/@matter/node/dist/esm/behavior/state/managed/values/StructManager.js:105:32)
    at OnOffServer.update (file:///usr/local/lib/node_modules/home-assistant-matter-hub/dist/backend/cli.js:1179:28)
    at #reactWithLocks (file:///usr/local/lib/node_modules/home-assistant-matter-hub/node_modules/@matter/node/dist/esm/behavior/internal/Reactors.js:286:26)
    at #reactWithContext (file:///usr/local/lib/node_modules/home-assistant-matter-hub/node_modules/@matter/node/dist/esm/behavior/internal/Reactors.js:262:32)
    at #react (file:///usr/local/lib/node_modules/home-assistant-matter-hub/node_modules/@matter/node/dist/esm/behavior/internal/Reactors.js:192:44)
    at reactorListener (file:///usr/local/lib/node_modules/home-assistant-matter-hub/node_modules/@matter/node/dist/esm/behavior/internal/Reactors.js:98:35)
Node.js v18.20.4
s6-rc: info: service legacy-services: stopping
s6-rc: info: service legacy-services successfully stopped
s6-rc: info: service legacy-cont-init: stopping
s6-rc: info: service legacy-cont-init successfully stopped
s6-rc: info: service fix-attrs: stopping
s6-rc: info: service base-addon-log-level: stopping
s6-rc: info: service fix-attrs successfully stopped
s6-rc: info: service base-addon-log-level successfully stopped
s6-rc: info: service base-addon-banner: stopping
s6-rc: info: service base-addon-banner successfully stopped
s6-rc: info: service s6rc-oneshot-runner: stopping
s6-rc: info: service s6rc-oneshot-runner successfully stopped
s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service base-addon-banner: starting
-----------------------------------------------------------
 Add-on: Home-Assistant-Matter-Hub
 Publish your entities from Home Assistant to any Matter-compatible controller like Alexa, Apple Home or Google Home.
-----------------------------------------------------------
 Add-on version: 3.0.0-alpha.28
 You are running the latest version of this add-on.
 System: Home Assistant OS 13.2  (amd64 / generic-x86-64)
 Home Assistant Core: 2024.11.1
 Home Assistant Supervisor: 2024.11.2
-----------------------------------------------------------
 Please, share the above information when looking for help
 or support in, e.g., GitHub, forums or the Discord chat.
-----------------------------------------------------------
s6-rc: info: service base-addon-banner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service base-addon-log-level: starting
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service base-addon-log-level successfully started
s6-rc: info: service legacy-cont-init: starting
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service legacy-services: starting
s6-rc: info: service legacy-services successfully started
[ 2024-11-12T18:02:14.984Z ] [ INFO  ] [ Storage                                            ]: Storage location: /config/data
[ 2024-11-12T18:02:15.274Z ] [ INFO  ] [ matter.js / ServerNodeStore                        ]: Opened 693312ca0f3e4900a507ab828b95e735 storage at /config/data/693312ca0f3e4900a507ab828b95e735
[ 2024-11-12T18:02:15.281Z ] [ INFO  ] [ matter.js / SessionManager                         ]: restoring resumption record for node<PHONE_NUMBER>29848961 and peer node<PHONE_NUMBER>29848961 for fabric index 1
[ 2024-11-12T18:02:15.919Z ] [ INFO  ] [ matter.js / Endpoint                               ]: 693312ca0f3e4900a507ab828b95e735 ready endpoint#: 0 type: RootNode (0x16) behaviors: 💤parts ✔index ✔basicInformation ✔accessControl ✔groupKeyManagement ✔generalCommissioning ✔administratorCommissioning ✔operationalCredentials ✔generalDiagnostics ✔commissioning ✔network 💤productDescription 💤sessions 💤controller ✔descriptor
[ 2024-11-12T18:02:15.933Z ] [ INFO  ] [ matter.js / Endpoint                               ]: 693312ca0f3e4900a507ab828b95e735.aggregator ready endpoint#: 1 type: Aggregator (0xe) behaviors: 💤parts ✔index ✔descriptor
[ 2024-11-12T18:02:15.972Z ] [ INFO  ] [ matter.js / Node                                   ]: 693312ca0f3e4900a507ab828b95e735 going online
[ 2024-11-12T18:02:16.339Z ] [ INFO  ] [ matter.js / Endpoint                               ]: 693312ca0f3e4900a507ab828b95e735.aggregator.light_sanca_estar ready endpoint#: 2 type: ExtendedColorLight (0x10d) behaviors: ✔identify ✔groups ✔onOff ✔levelControl ✔colorControl ✔bridgedDeviceBasicInformation ✔homeAssistant ✔descriptor
[ 2024-11-12T18:02:16.369Z ] [ INFO  ] [ matter.js / Endpoint                               ]: 693312ca0f3e4900a507ab828b95e735.aggregator.light_balcao ready endpoint#: 3 type: DimmableLight (0x101) behaviors: ✔identify ✔groups ✔onOff ✔levelControl ✔bridgedDeviceBasicInformation ✔homeAssistant ✔descriptor
[ 2024-11-12T18:02:16.519Z ] [ INFO  ] [ matter.js / Endpoint                               ]: 693312ca0f3e4900a507ab828b95e735.aggregator.light_retro ready endpoint#: 4 type: ColorTemperatureLight (0x10c) behaviors: ✔identify ✔groups ✔onOff ✔levelControl ✔colorControl ✔bridgedDeviceBasicInformation ✔homeAssistant ✔descriptor
[ 2024-11-12T18:02:16.567Z ] [ INFO  ] [ matter.js / Endpoint                               ]: 693312ca0f3e4900a507ab828b95e735.aggregator.light_color4 ready endpoint#: 5 type: ExtendedColorLight (0x10d) behaviors: ✔identify ✔groups ✔onOff ✔levelControl ✔colorControl ✔bridgedDeviceBasicInformation ✔homeAssistant ✔descriptor
[ 2024-11-12T18:02:16.611Z ] [ INFO  ] [ matter.js / Endpoint                               ]: 693312ca0f3e4900a507ab828b95e735.aggregator.light_cama_lais ready endpoint#: 6 type: ExtendedColorLight (0x10d) behaviors: ✔identify ✔groups ✔onOff ✔levelControl ✔colorControl ✔bridgedDeviceBasicInformation ✔homeAssistant ✔descriptor
[ 2024-11-12T18:02:16.659Z ] [ INFO  ] [ matter.js / Endpoint                               ]: 693312ca0f3e4900a507ab828b95e735.aggregator.light_rgb_strip ready endpoint#: 7 type: ExtendedColorLight (0x10d) behaviors: ✔identify ✔groups ✔onOff ✔levelControl ✔colorControl ✔bridgedDeviceBasicInformation ✔homeAssistant ✔descriptor
[ 2024-11-12T18:02:16.685Z ] [ INFO  ] [ matter.js / Endpoint                               ]: 693312ca0f3e4900a507ab828b95e735.aggregator.input_boolean_musica_varanda ready endpoint#: 28 type: OnOffPlugInUnit (0x10a) behaviors: ✔identify ✔groups ✔onOff ✔bridgedDeviceBasicInformation ✔homeAssistant ✔descriptor
[ 2024-11-12T18:02:16.983Z ] [ INFO  ] [ matter.js / Endpoint                               ]: 693312ca0f3e4900a507ab828b95e735.aggregator.climate_split_escritorio ready endpoint#: 8 type: Thermostat (0x301) behaviors: ✔identify ✔bridgedDeviceBasicInformation ✔homeAssistant ✔relativeHumidityMeasurement ✔temperatureMeasurement ✔thermostat ✔descriptor
[ 2024-11-12T18:02:17.007Z ] [ INFO  ] [ matter.js / Endpoint                               ]: 693312ca0f3e4900a507ab828b95e735.aggregator.light_centro_l6 ready endpoint#: 9 type: OnOffLight (0x100) behaviors: ✔identify ✔groups ✔onOff ✔bridgedDeviceBasicInformation ✔homeAssistant ✔descriptor
[ 2024-11-12T18:02:17.029Z ] [ INFO  ] [ matter.js / Endpoint                               ]: 693312ca0f3e4900a507ab828b95e735.aggregator.light_entrada_l3 ready endpoint#: 10 type: OnOffLight (0x100) behaviors: ✔identify ✔groups ✔onOff ✔bridgedDeviceBasicInformation ✔homeAssistant ✔descriptor
[ 2024-11-12T18:02:17.051Z ] [ INFO  ] [ matter.js / Endpoint                               ]: 693312ca0f3e4900a507ab828b95e735.aggregator.light_centro_l1 ready endpoint#: 11 type: OnOffLight (0x100) behaviors: ✔identify ✔groups ✔onOff ✔bridgedDeviceBasicInformation ✔homeAssistant ✔descriptor
[ 2024-11-12T18:02:17.072Z ] [ INFO  ] [ matter.js / Endpoint                               ]: 693312ca0f3e4900a507ab828b95e735.aggregator.light_centro_l4 ready endpoint#: 12 type: OnOffLight (0x100) behaviors: ✔identify ✔groups ✔onOff ✔bridgedDeviceBasicInformation ✔homeAssistant ✔descriptor
[ 2024-11-12T18:02:17.095Z ] [ INFO  ] [ matter.js / Endpoint                               ]: 693312ca0f3e4900a507ab828b95e735.aggregator.light_entrada_l2 ready endpoint#: 13 type: OnOffLight (0x100) behaviors: ✔identify ✔groups ✔onOff ✔bridgedDeviceBasicInformation ✔homeAssistant ✔descriptor
[ 2024-11-12T18:02:17.128Z ] [ INFO  ] [ matter.js / Endpoint                               ]: 693312ca0f3e4900a507ab828b95e735.aggregator.light_entrada_l6 ready endpoint#: 14 type: OnOffLight (0x100) behaviors: ✔identify ✔groups ✔onOff ✔bridgedDeviceBasicInformation ✔homeAssistant ✔descriptor
[ 2024-11-12T18:02:17.154Z ] [ INFO  ] [ matter.js / Endpoint                               ]: 693312ca0f3e4900a507ab828b95e735.aggregator.light_centro_l5 ready endpoint#: 15 type: OnOffLight (0x100) behaviors: ✔identify ✔groups ✔onOff ✔bridgedDeviceBasicInformation ✔homeAssistant ✔descriptor
[ 2024-11-12T18:02:17.175Z ] [ INFO  ] [ matter.js / Endpoint                               ]: 693312ca0f3e4900a507ab828b95e735.aggregator.light_entrada_l4 ready endpoint#: 16 type: OnOffLight (0x100) behaviors: ✔identify ✔groups ✔onOff ✔bridgedDeviceBasicInformation ✔homeAssistant ✔descriptor
[ 2024-11-12T18:02:17.196Z ] [ INFO  ] [ matter.js / Endpoint                               ]: 693312ca0f3e4900a507ab828b95e735.aggregator.light_entrada_l5 ready endpoint#: 17 type: OnOffLight (0x100) behaviors: ✔identify ✔groups ✔onOff ✔bridgedDeviceBasicInformation ✔homeAssistant ✔descriptor
[ 2024-11-12T18:02:17.227Z ] [ INFO  ] [ matter.js / Endpoint                               ]: 693312ca0f3e4900a507ab828b95e735.aggregator.light_corredor_l1 ready endpoint#: 18 type: OnOffLight (0x100) behaviors: ✔identify ✔groups ✔onOff ✔bridgedDeviceBasicInformation ✔homeAssistant ✔descriptor
[ 2024-11-12T18:02:17.247Z ] [ INFO  ] [ matter.js / Endpoint                               ]: 693312ca0f3e4900a507ab828b95e735.aggregator.light_corredor_l2 ready endpoint#: 19 type: OnOffLight (0x100) behaviors: ✔identify ✔groups ✔onOff ✔bridgedDeviceBasicInformation ✔homeAssistant ✔descriptor
[ 2024-11-12T18:02:17.281Z ] [ INFO  ] [ matter.js / Endpoint                               ]: 693312ca0f3e4900a507ab828b95e735.aggregator.light_modulo_l3 ready endpoint#: 20 type: OnOffLight (0x100) behaviors: ✔identify ✔groups ✔onOff ✔bridgedDeviceBasicInformation ✔homeAssistant ✔descriptor
[ 2024-11-12T18:02:17.315Z ] [ INFO  ] [ matter.js / Endpoint                               ]: 693312ca0f3e4900a507ab828b95e735.aggregator.light_relayatv0_6_32_2 ready endpoint#: 21 type: OnOffLight (0x100) behaviors: ✔identify ✔groups ✔onOff ✔bridgedDeviceBasicInformation ✔homeAssistant ✔descriptor
[ 2024-11-12T18:02:17.339Z ] [ INFO  ] [ matter.js / Endpoint                               ]: 693312ca0f3e4900a507ab828b95e735.aggregator.light_relayatv0_6_32_1 ready endpoint#: 22 type: OnOffLight (0x100) behaviors: ✔identify ✔groups ✔onOff ✔bridgedDeviceBasicInformation ✔homeAssistant ✔descriptor
[ 2024-11-12T18:02:17.377Z ] [ INFO  ] [ matter.js / Endpoint                               ]: 693312ca0f3e4900a507ab828b95e735.aggregator.light_lavabo_center ready endpoint#: 24 type: OnOffLight (0x100) behaviors: ✔identify ✔groups ✔onOff ✔bridgedDeviceBasicInformation ✔homeAssistant ✔descriptor
[ 2024-11-12T18:02:17.399Z ] [ INFO  ] [ matter.js / Endpoint                               ]: 693312ca0f3e4900a507ab828b95e735.aggregator.light_lavabo_left ready endpoint#: 25 type: OnOffLight (0x100) behaviors: ✔identify ✔groups ✔onOff ✔bridgedDeviceBasicInformation ✔homeAssistant ✔descriptor
[ 2024-11-12T18:02:17.421Z ] [ INFO  ] [ matter.js / Endpoint                               ]: 693312ca0f3e4900a507ab828b95e735.aggregator.light_modulo_l1 ready endpoint#: 26 type: OnOffLight (0x100) behaviors: ✔identify ✔groups ✔onOff ✔bridgedDeviceBasicInformation ✔homeAssistant ✔descriptor
[ 2024-11-12T18:02:17.442Z ] [ INFO  ] [ matter.js / Endpoint                               ]: 693312ca0f3e4900a507ab828b95e735.aggregator.light_modulo_l2 ready endpoint#: 27 type: OnOffLight (0x100) behaviors: ✔identify ✔groups ✔onOff ✔bridgedDeviceBasicInformation ✔homeAssistant ✔descriptor
[ 2024-11-12T18:02:17.464Z ] [ INFO  ] [ matter.js / Endpoint                               ]: 693312ca0f3e4900a507ab828b95e735.aggregator.input_boolean_b_tv_sala ready endpoint#: 29 type: OnOffPlugInUnit (0x10a) behaviors: ✔identify ✔groups ✔onOff ✔bridgedDeviceBasicInformation ✔homeAssistant ✔descriptor
[ 2024-11-12T18:02:17.484Z ] [ INFO  ] [ WebApi                                             ]: HTTP server (API & Web App) listening on port 8482
[ 2024-11-12T18:02:17.551Z ] [ INFO  ] [ matter.js / Node                                   ]: 693312ca0f3e4900a507ab828b95e735 is online
[ 2024-11-12T18:02:17.558Z ] [ INFO  ] [ matter.js / AccessControlServer                    ]: initializing ACL manager with ACL { privilege: 5, authMode: 2, subjects: [<PHONE_NUMBER>0825763882,<PHONE_NUMBER>0824715265 ], targets: null, fabricIndex: 1 }
[ 2024-11-12T18:02:17.701Z ] [ INFO  ] [ matter.js / CaseServer                             ]: Received pairing request from udp://<IP_ADDRESS>:5541
[ 2024-11-12T18:02:17.730Z ] [ ERROR ] [ matter.js / Transaction                            ]: Error post-commit of 693312ca0f3e4900a507ab828b95e735.aggregator.input_boolean_b_tv_sala.homeAssistant.state: Error in reactor<693312ca0f3e4900a507ab828b95e735.aggregator.input_boolean_b_tv_sala.onOff.update>: reactor<693312ca0f3e4900a507ab828b95e735.aggregator.input_boolean_b_tv_sala.onOff.update> returned a Promise but the observable is synchronous; you must set the "offline" option so this reactor runs with a dedicated transaction
  at #react (file:///usr/local/lib/node_modules/home-assistant-matter-hub/node_modules/@matter/node/dist/esm/behavior/internal/Reactors.js:194:15)
  at reactorListener (file:///usr/local/lib/node_modules/home-assistant-matter-hub/node_modules/@matter/node/dist/esm/behavior/internal/Reactors.js:98:35)
  at emitNext (file:///usr/local/lib/node_modules/home-assistant-matter-hub/node_modules/@matter/general/dist/esm/util/Observable.js:70:20)
  at BasicObservable.emit (file:///usr/local/lib/node_modules/home-assistant-matter-hub/node_modules/@matter/general/dist/esm/util/Observable.js:109:12)
  at file:///usr/local/lib/node_modules/home-assistant-matter-hub/node_modules/@matter/node/dist/esm/behavior/Behavior.js:170:36
  at emitNext (file:///usr/local/lib/node_modules/home-assistant-matter-hub/node_modules/@matter/general/dist/esm/util/Observable.js:70:20)
  at ObservableProxy.emit (file:///usr/local/lib/node_modules/home-assistant-matter-hub/node_modules/@matter/general/dist/esm/util/Observable.js:109:12)
  at emitNext (file:///usr/local/lib/node_modules/home-assistant-matter-hub/node_modules/@matter/general/dist/esm/util/Observable.js:70:20)
  at BasicObservable.emit (file:///usr/local/lib/node_modules/home-assistant-matter-hub/node_modules/@matter/general/dist/esm/util/Observable.js:109:12)
  at emitChanged (file:///usr/local/lib/node_modules/home-assistant-matter-hub/node_modules/@matter/node/dist/esm/behavior/state/managed/Datasource.js:332:30)
[ 2024-11-12T18:02:17.771Z ] [ INFO  ] [ matter.js / CaseServer                             ]: session 57312 resumed with udp://<IP_ADDRESS>:5541 for Fabric 03F9F5B602627D40(index 1) and PeerNode 03F3FEF17352BD81 with CATs 1114154
[ 2024-11-12T18:02:17.774Z ] [ INFO  ] [ matter.js / InsecureSession                        ]: End insecure session insecure/9859076642587292040
[ 2024-11-12T18:02:17.784Z ] [ INFO  ] [ matter.js / Behavior                               ]: Invoke 693312ca0f3e4900a507ab828b95e735.aggregator.input_boolean_b_tv_sala.onOff.off online#2c6bfba@3f3fef17352bd81 (no payload)
[ 2024-11-12T18:02:17.789Z ] [ INFO  ] [ matter.js / Behavior                               ]: Invoke 693312ca0f3e4900a507ab828b95e735.aggregator.input_boolean_b_tv_sala.onOff.off online#2c6bfbb@3f3fef17352bd81 (no payload)
[ 2024-11-12T18:04:12.397Z ] [ INFO  ] [ matter.js / CaseServer                             ]: Received pairing request from udp://<IP_ADDRESS>:5541
[ 2024-11-12T18:04:12.424Z ] [ INFO  ] [ matter.js / CaseServer                             ]: session 57313 resumed with udp://<IP_ADDRESS>:5541 for Fabric 03F9F5B602627D40(index 1) and PeerNode 03F3FEF17352BD81 with CATs 1114154
[ 2024-11-12T18:04:12.429Z ] [ INFO  ] [ matter.js / InsecureSession                        ]: End insecure session insecure/16277977632084660391
[ 2024-11-12T18:04:15.264Z ] [ INFO  ] [ matter.js / InteractionServer                      ]: Successfully created subscription<PHONE_NUMBER> for Session 57313. Updates: 1 - 300 => 188 seconds (sendInterval = 94 seconds)

this should be fixed with alpha.31.


Optimize Server startup time using multi-threading for annotation scanning

This is a redo of Previous PR: https://github.com/apache/tomcat/pull/349
The following changes have been made based on the suggestions earlier:

Flag (parallelAnnotationScanning) can be passed through Host Configuration. See example below.
By default parallelAnnotationScanning remains disabled and thus default tomcat behavior is untouched.
Number of threads could be triggered by startStopThreads parameter.
PR is against master.

Apologies in case something is missed.
<Host name="localhost"  appBase="webapps"
            unpackWARs="true" autoDeploy="true" parallelAnnotationScanning="true" >

I don't agree with this. There is a "utility" executor (Server.getUtilityExecutor()), it could be used for that instead of adding special purpose threads. Then you can add a flag to do the scanning as executor tasks or the usual way.

I still don't really like some items, like the explicit flag (but I don't see yet how to do it) or some of the "optimizations".
By default the utility thread count is 2, so not too much parallelism.

I still don't really like some items, like the explicit flag (but I don't see yet how to do it) or some of the "optimizations".
By default the utility thread count is 2, so not too much parallelism.

Yes, You're right with the default Value, but that can be changed through the Host Configuration.. right?

@rmaucher I actually tested the optimization with the flag in a large application having 1000's of Jar in the classpath and the server startup gains are significant and the stats are as follows :
2816 classes -  44% improvement
1800 classes - 40% improvement
1000 classes - 40% improvement
The default tomcat app shows an improvement of 6% with the flag.

Since the release cycle is done, I'll work on this feature.

I merged the PR with some changes and a minor fix. The flag was moved to the Context since that's where it belongs, and it avoids the unnecessary API changes.

Thank you @rmaucher @martin-g to get this moving fast 👍 .
Will this be backported to version 9 ?

Will this be backported to version 9 ?

Actually, it seems like this was merged right into the version 9 branch - see 101476c3536ac09a105d0b603b2c51dd0f3770e9. So it is available since Tomcat 9.0.39.
I can confirm about 1/3 scanning speed improvement with parallelAnnotationScanning="true" on a <context>. Thank you, guys. :)


Flutter is not working with JAWS Screenreader

Is there an existing issue for this?

[X] I have searched the existing issues
[X] I have read the guide to filing a bug

Steps to reproduce

Using Text Widget with or without Semantics Wrapper. (see code sample)
Running App in Web and open with Chrome
Start JAWS Screenreader
The widget is not selectable with JAWS screen reader and will not be read
The NVDA screen reader has no problems reading the widget

Expected results
The Widget Labels should be read and selectable with the arrow keys, just like it works with NVDA.
Actual results
Compatibility with the JAWS screen reader is very poor to non-existent.
Or am I doing something wrong? Can anyone else share their experiences with Flutter & Jaws?
Code sample
Code sample
                      Semantics(
                        readOnly: true,
                        label: AppLocalizations.of(context).title_login_page_text,
                        child: Text(
                          AppLocalizations.of(context).title_login_page_text,
                          textScaleFactor: Provider.of<FontSizeService>(context).currentFirstHeadlineScaleFactor,
                          style: Theme.of(context).textTheme.headline1,
                        ),
                      ),

Flutter Doctor output
Doctor output
[√] Flutter (Channel stable, 3.10.6, on Microsoft Windows [Version 10.0.19044.3086], locale de-DE)
    • Flutter version 3.10.6 on channel stable at C:\Users\er\Documents\Software\flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision f468f3366c (3 months ago), 2023-07-12 15:19:05 -0700
    • Engine revision cdbeda788a
    • Dart version 3.0.6
    • DevTools version 2.23.1

[√] Windows Version (Installed version of Windows is version 10 or higher)

[X] Android toolchain - develop for Android devices
    X Unable to locate Android SDK.
      Install Android Studio from: https://developer.android.com/studio/index.html
      On first launch it will assist you in installing the Android SDK components.
      (or visit https://flutter.dev/docs/get-started/install/windows#android-setup for detailed instructions).
      If the Android SDK has been installed to a custom location, please use
      `flutter config --android-sdk` to update to that location.
[√] Connected device (3 available)
    • Windows (desktop) • windows • windows-x64    • Microsoft Windows [Version 10.0.19044.3086]
    • Chrome (web)      • chrome  • web-javascript • Google Chrome 117.0.5938.92
    • Edge (web)        • edge    • web-javascript • Microsoft Edge 117.0.2045.43

[√] Network resources
    • All expected network resources are available.

@erhadesso
There's a similar issue open describing your case, https://github.com/flutter/flutter/issues/122607, so please follow-up in it for further updates.
Closing this as a duplicate.


Update documentation with deployment steps

Explain how to upgrade, publish reaction-force and add the latest version into force

This would still be very helpful! I'd like to do these steps and am trying to remember how...

This is done.


how to load crelly before content

hi
i love your plugin.. its very easy and effective.
i am having a issue with the plugin..
it is loading after the content.. so it looks odd
can you please help me on this...

What's the problem exactly? Is the preloader broken?
Il 19 lug 2016 1:08 PM, pvschaitanya<EMAIL_ADDRESS>ha scritto:
hi
i love your plugin.. its very easy and effective.
i am having a issue with the plugin..
it is loading after the content.. so it looks odd
can you please help me on this...
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHubhttps://github.com/fabiorino/crelly-slider/issues/30, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AF9SoaqKot96QeFLkRanbQ3XWgklTFTtks5qXLAMgaJpZM4JPna7.

Hi Sir
i don't know exactly what problem is.. because i am new to word press and web designing.
where i tried with "Slider Revolution" it is loading before content
example : http://chaitanya.esy.es/revo-slider/
but "Crelly Slider" is loading after content
example : http://chaitanya.esy.es/crelly-slider/
note: the above site is in fee hosting.. so some time it is not loading.. please bare with me and please press refesh
regards
Chaitanya

Revolution slider loads the content through Ajax. My plugin isn't as sophisticated as Revslider. I'm sorry, noway to achieve the same result in this moment.

Ohh... Ok Sir.. thanks for the reply
regards
chaitanya

Hi Sir
today i saw that in your plugin home page..
http://fabiorino1.altervista.org/projects/crellyslider/
there the slider, which is in your home page is working how i want.. how can i do the same with my slicer in my site?()
http://chaitanya.esy.es/crelly-slider/
regards
chaitanya

The source code is exactly the same. Maybe it looks different because the image sizes are such that "hide" that behaviour


Third-party apps / extensions: fluentcms-teaser

Thanks for django-fluent-[contents|pages], here is my small contribution https://github.com/bashu/fluentcms-teaser
PS: fluentcms-filer (django-file integration) and fluentcms-suit (django-suit integration) will be ready soon =)

Wonderful. thanks for making that a plugin.
I had a similar plugin (called announcement item) but teaser is a much better name.
One suggestion: make the description a PluginHtmlField. In my experience, users want to be able to place links there. I'm tempted to make some wysiwyg-hint like PluginHtmlField(style='simple') because it shouldn't have to show all toolbar buttons.

@vdboor done


WIP nix(arm64): make nix setup ARM64 compatible

Problem
Current nix setup don't build on ARM64 Mac 🍎
Solution
Add system.aarch64-darwin and make dream "buildable"

Working on debian
KO on macos with M1...
$ nix build .#deku
warning: Using saved setting for 'trusted-substituters = https://cache.nixos.org/ https://deku.cachix.org' from ~/.local/share/nix/trusted-settings.json.
error: builder for '/nix/store/3vnjap7s0jid8yi3k812gapik83732np-ocaml5.00.0+trunk-dream-1.0.0-alpha2.drv' failed with exit code 1;
       last 10 log lines:
       >   [OK]          headers         20   with_header update.
       >
       > Full test results in `/private/tmp/nix-build-ocaml5.00.0+trunk-dream-1.0.0-alpha2.drv-0/source/_build/default/test/unit/_build/_tests/Dream'.
       > Test Successful in 0.004s. 34 tests run.
       > File "test/expect/eml/dune", line 10, characters 1-15:
       > 10 |  (inline_tests)
       >       ^^^^^^^^^^^^^^
       > (cd _build/default/test/expect/eml && .test_expect_eml.inline-tests/inline_test_runner_test_expect_eml.exe inline-test-runner test_expect_eml -source-tree-root ../../.. -diff-cmd -)
       > Command got signal BUS.
       >
       For full logs, run 'nix log /nix/store/3vnjap7s0jid8yi3k812gapik83732np-ocaml5.00.0+trunk-dream-1.0.0-alpha2.drv'.
error: 1 dependencies of derivation '/nix/store/r0viy5cv8gcrgz7c7s03gcqma6iq8666-ocaml5.00.0+trunk-sidechain-0.0.0-dev.drv' failed to build

I am feeling so dumb... Thanks @ulrikstrid!
I didn't even think about adding doCheck = false within the dream of nix/overlay.nix... Working perfectly now!

@ulrikstrid for some reason I'm still not able to get nix to work properly on my mac. Please don't block this PR on my account :p


"Message content over the limit has been removed" in robot html log files.

Originally submitted to Google Code by lishuang990338 on 1 Aug 2013

Using Robot 2.7.7, Jython 2.6.
There are some errors in the robot testcases we design. But it seems that there robot could not print all the fail log information just as below. I.e., just from 1) to  8) and then from 15) to the last one.
There is a sentence which given that "[ Message content over the limit has been removed. ]", I don't know what's happened? Is it because the fail log is too long? How long is it for the error logs in the log summary? Is the length configurable? If not, why it omit the middle part and leave the begin and end part? Please find enclosed log for more details.
Thank you very much!
TEST CASE: FEED6
Full Name:  Robot.UT.David.FEED-6.FEED6
Start / End / Elapsed:  20130801 15:10:09.142 / 20130801 16:31:48.336 / 01:21:39.194
Status: FAIL (critical)
Message:    Several failures occurred: 1) unually the CMP_NME_ET value of the RIC should be 1, if it not 1, should confirm with Dev: 2 != 1 2) the MC_LABEL value of the RIC not match the dataview result: 2100 != 2101 3) the MC_REC_LAB value of the RIC not match the dataview result: 2100 != 2101 4) unually the CMP_NME_ET value of the RIC should be 1, if it not 1, should confirm with Dev: 2 != 1 5) the MC_LABEL value of the RIC not match the dataview result: 2100 != 2101 6) the MC_REC_LAB value of the RIC not match the dataview result: 2100 != 2101 7) unually the CMP_NME_ET value of the RIC should be 1, if it not 1, should confirm with Dev: 2 != 1 8) unually the CMP_NME_ET value of the RIC should be 1, if it not 1, should... [ Message content over the limit has been removed. ] 15) the MC_REC_LAB value of the RIC not match the dataview result: 2100 != 2101 16) unually the CMP_NME_ET value of the RIC should be 1, if it not 1, should confirm with Dev: 2 != 1 17) unually the CMP_NME_ET value of the RIC should be 1, if it not 1, should confirm with Dev: 2 != 1 18) the MC_LABEL value of the RIC not match the dataview result: 2100 != 2101 19) the MC_REC_LAB value of the RIC not match the dataview result: 2100 != 2101 20) unually the CMP_NME_ET value of the RIC should be 1, if it not 1, should confirm with Dev: 2 != 1

Maybe should make this limit changeable without changing robot's source files?


Restrict StaticArrays.jl @v1.5.16- to Julia v1.10-

Following up on https://github.com/JuliaRegistries/General/pull/86950#issuecomment-2403361516:
In #86950, the julia compat was restricted to ≤ 1.10 for<EMAIL_ADDRESS>However, the code which errors was only removed in 1.5.17, see here.
This is my attempt on adjusting the Compat.toml accordingly.

This broke tests in Juli: https://buildkite.com/julialang/julia-master/builds/41256#_  I'm going to revert it urgently

So, how should this be dealt with then? 😶


[BUG] Interpret Data meet Oops!

Describe the bug
I render a bar graph, when click 'Interpret Data' meet a Oops bug.
To Reproduce
Steps to reproduce the behavior:

render a bar graph
click 'Interpret Data' on a bar, There will be a Oops Error

Expected behavior
Screenshots

Versions

pygwalker version: 0.4.6
python version: 3.8
browser: chrome latest

Additional context

It seems that the kernel calculation is not compatible with the old workflow.
We'll fix it within 7 days.
Thanks!

fixed it.
pip install --upgrade pygwalker


Fix plausible script tags and make them configurable

Before, the plausible scripts added by this theme were:

broken in some metrics like bounce rate because the Script tag put them at the bottom.
all hard-coded to point to dvc.org :grimacing:

This PR changes that by turning the plausible domain and script source into options configurable via Gatsby's siteMetadata feature under the keys plausibleDomain and plausibleSrc.

plausibleDomain determines the domain the site reports to Plausible as, and if it isn't specified the plausible script element will not be rendered at all.
plausibleSrc allows us to specify the src tag of the plausible script, defaulting to the outbound-links version of the script from the website. Cases where this would be overridden would include wanting to use a non-outbound-links version of the script and/or using a proxy for the script like we do for dvc.org.

:warning: I've rebased this branch onto a new maintenance branch that reverts #33, so we can make a bugfix release on the 0.1 line and make this fix get in today

I'm struggling to find out where we actually put /pl/api/event link, I'm looking over all the existing plausible code but it seems like the only two values used are the domain and src that links import from. In the meantime, I'll add the automagic setup for what this PR has to make the patch more seamless.

Found it! It's just data-api on the main script :facepalm:. Integrating it now.

Hi. Now that this has been merged everywhere, should we setup some follow-up date to check on the bounce rates?

I've actually been checking in the whole time! Bounce rates went down immediately after the initial quickfix, and have stayed at that same low/normal level with all other metrics normal ever since the merge. My last check was Monday, and I planned to give yet another Friday for extra measure.


Make Turing.jl 0.6 compatible

Typing system is kind of changed - would need some refactors.
Related issue: https://github.com/yebai/Turing.jl/issues/173
I would suggest that we fix https://github.com/yebai/Turing.jl/issues/177 and also put 0.6 support in our 0.3 release?

@ChrisRackauckas This is already planed in 0.3.1, which we plan to fix the adaption issue (#324) and Julia 0.6 compatibility.

Closed the duplicate issue https://github.com/yebai/Turing.jl/issues/330

cc @xukai92 @emilemathieu @ae-foster @ChrisRackauckas
We have fixed all known compatibility issues of Turing with Julia 0.6. The master branch of Turing now supports (requires) Julia 0.6.

Great thanks! When do you plan on tagging?

There are some remaining issues with the NUTS sampler, mostly related to robust adaption (see https://github.com/yebai/Turing.jl/milestone/5). I planned to fix those issues altogether in 0.3.1. But perhaps we can move these issues to 0.3.2 and make a new tagging now. What do you think?

I would prefer a quicker tag, and more can always be added later of course. Reviewing tags in METADATA is easier when you have less per tag.

I see - will do.

I have weird errors now:

LoadError: MethodError: no method matching ##mhtest_model#687()
The applicable method may be too new: running in world age 23509, while current world is 23513.

@yebai Would you have any idea of where that could come from ?


My podspec is not passing validation due to SwiftyJSON

Hello,
My WMATAFetcher pod cannot be published due to errors in SwiftyJSON.  I ran pod spec lint --verbose and copied its output to Pastebin here.
Things I have tried:

Updated to the prerelease version of Cocoapods (1.1.0.rc.2)
pod repo update
Cleared the Cocoapods cache

pod spec lint shows that I'm using SwiftyJSON 3.1.0, so I think I have things configured properly.  Here is the podspec and Podfile that I am using.  That repo is up to date with my local project.
There are no errors or warnings in any of the targets (cross platform) in my project in Xcode 8.0 (8A218a).
Thank you in advance for the help!

Same error for SwiftyConcur, hoping we can get this fixed soon!

@brennick @clrung you have to add .swift-version to you project root.
Otherwise, cocoapods will think you're using swift2.3 instead

Thank you, @zhigang1992!!


Non-existant output lookups return 500 error

For example:
https://ordinals.com/output/0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef:123
This is because the JSON RPC status code / message for output not found was changed, so we don't correctly transform it into a 404 not found HTTP error.

When reproduced in the env terminal I see this error:
error serving request: JSON-RPC error: RPC error response: RpcError { code: -5, message: "No such mempool or blockchain transaction. Use gettransaction for wallet transactions.", data: None }
I hope this information will help in getting to the bottom of it.  I looked into the code and wasn't able to get very far in fixing it.


added hover tooltips to labels in the dapp views

used react-tooltip instead as there were some problems with tippyjs-react and I was unable to came up with a solution. maybe it's good to use it at least for a temporary solution until someone comes up with a fix #12

@Vienio99 Are you using Prettier + VSCode? I'm confused by the formatting/spacing going on in the diff. Please rectify if you can.
Also surprised that this adds 3k+ lines of code to the package-lock. Seems like an excessive number of sub-dependencies. I'm going to compare this to tippy and see which is preferable in terms of bundle-size.

A few visual notes:
Let's add some opacity to the icon, so it doesn't distract from the actual label. opacity: 0.4 looks good.
To the parent, add align-items: center and gap: 0.4rem, so it centers nicely. Here is screenshot of before/after for reference:

And for the tooltip text, I wonder if caption typography  would look better than body2 typography. Either way the line-height is a bit tall which hurts readability.

@Atmosfearful I've fixed mentioned issues, looks way better now. When it comes to dependencies, indeed react-tooltip has it more unfortunately

@Vienio99 Thanks it looks perfect on my end!!
I decided I am going to copy paste your code to my branch and install the deps myself (just to avoid the security risk as I can't visually audit all those package-lock changes).
Feel free to DM me on discord and we can get you set up on another ticket, if you want :) ❤


feat: update mathlib mod-tac-stx 2022-12-01

This adds all the changes to tactic syntax that have happened in the period 2022-11-01 thru 2022-12-01.

bors merge


Problem with starting.

I installed Atom from .deb package. And see this after start. Ubuntu 14.04 with Mate.
https://i.gyazo.com/b5e34cbc41100770a91d473b75d908f0.png

To solve the problem i used
sudo chown -R whoami ~/.atom


Problem with 14.1.1: Could not find the 'ngx-build-plus:dev-server

Hi. I updated the version of module-federation-plugin of my angular application. When I start my application, I've got this error:
Could not find the 'ngx-build-plus:dev-server' builder's node package

+1 -- please just add this lib. For new projects, our ng-add respective init schematic adds it automatically.


HELP needed for using an SPFx library component from an npm public/private registry.

What type of issue is this?
Question
What SharePoint development model, framework, SDK or API is this about?
💥 SharePoint Framework
Target SharePoint environment
SharePoint Online
What browser(s) / client(s) have you tested

[ ] 💥 Internet Explorer
[ ] 💥 Microsoft Edge
[X] 💥 Google Chrome
[ ] 💥 FireFox
[ ] 💥 Safari
[ ] mobile (iOS/iPadOS)
[ ] mobile (Android)
[ ] not applicable
[ ] other (enter in the "Additional environment details" area below)

Additional environment details

browser version
SPFx version: 1.17.3 (both for webpart and library)
Node.js version: 16.13.0

Issue description
Hello,
We have mutiple (+10 ) web parts solutions. To share code among these web parts, we utilized the SPFx library component, which has been highly effective.
However, when decided to introduce some of our web parts to the SharePoint store, we encountered a challenge. The SharePoint marketplace allows for the upload of a single package solution (.sppkg) file. For our web parts to function correctly, we currently have to upload two separate packages: one for the web part (".sppkg") and another for the library (".sppkg").
To circumvent this limitation, we tried deploying our library component to the NPM registry. We then consumed it in our web part using a package manager. This approach seemed successful during local testing on the workbench; in the network tab, we could see the library component's JS files being fetched from the web part's node_modules folder.
Yet, when we executed a build with the --ship flag and deployed the web part to the app catalog, it couldn't retrieve the library component.
We're keen to find a solution, but before delving deeper, we want to confirm if our approach is feasible. Is it possible to utilize the library component without deploying it to the app catalog?
Thank you in advance for your insights. If additional details are required, please let me know.

@heesungjang - npm registry is an alternative to a library component. But with npm you package will be bundled to every web part.
Library component must be deployed to the app catalog to work correctly.
Could you try combining a web part and library component in a single package?
Theoretically, you will need to do that for every separate solution in the store and test what happens if a user installs multiple of those.

This is a common downside to library components because you've set a dependency to have another SharePoint package deployed to your tenant (the library component) that the project containing the web parts assumes is already installed.
For your scenario in deploying to the store, library components aren't going to work.
You can bundle your code in your web part project, OR if you want to externalize it (which I would prefer) to keep the shared code separate, you can package & deploy it as an NPM package, but also host a production bundle in a CDN. Then in your project that contains the web parts, you'll add the NPM package (so you can still develop easily), but update the project's config.json to set an external reference to the production CDN.
This way, when you build your project with the web parts in it, your NPM package won't be bundled in the SPPKG you publish to the store, but when a web part is added to a page, it will tell the SPFx runtime to load the CDN referenced bundle before the web part is added to the page.

Hey @andrewconnell, @AJIXuMuK
Thank you so much for taking the time to provide such a detailed response. We really needed to understand what is possible and what isn't. Currently, we have over 15 web parts bundled into one solution package. However, our goal is to eventually separate them all into individual packages. Hosting a production bundle in a CDN seems like a great approach for us.
Warm regards,

Hey @andrewconnell ,
Thanks for your advice. I have another question regarding the "host a production bundle in a CDN" part. Can we host the bundled SPFx library component on a CDN and then externalize it in the web part via config.json?
To elaborate:
Execute "gulp package-solution --ship" for the library component.
Host the resulting bundle on a CDN.
Update the web part's config.json like so:
"externals":{ "library": {     "path": "path to the CDN",     "globalName": "library" } }
Is this feasible? Or should we avoid packaging shared code as an SPFx library component and instead package our custom shared code?

@heesungjang asked:

Can we host the bundled SPFx library component on a CDN and then externalize it in the web part via config.json?

No.

Or should we avoid packaging shared code as an SPFx library component and instead package our custom shared code?

MIHO, that's what I recommend.
It's either/or... you either 1⃣ share your code with a library component that's fully deployed to your tenant, OR 2⃣ you use an NPM package & let the consumer of it either bundle it or externalize it in their config.json from your self-hosted CDN.
Speaking just for myself & to be crystal clear that I'm not speaking for Microsoft...
IMHO, I don't see much value in SPFx library components

Honest, I see zero value and never use them. I only use NPM packages and have never found a reason why an SPFx library component would be better than an NPM package. There are too many sharp edges with library components It's also why the chapter about sharing code in my Mastering SPFx course (chapter preview here), I show both options and present the adv/disad of each.

From my POV: library components solved a problem that was already solved by the JS & web community, but Microsoft's solution did so in a very restrictive SPFx way. To me, that doesn't make sense. But... just $0.02 USD.
Depending on the size & who the consumer is, I'll either let projects include it in their bundles OR I'll post it to a CDN (either a public one or one that's private to an org, as I've done with highly secure & restricted environments).
Of course, YMMV and I know plenty that disagree with my take. That's why I make it clear it's just my opinion. :)


bugfix: support defaults which are unhashable (e.g. JsonField default={}...

bugfix: support defaults which are unhashable.
As an example now JsonField(default={}) causes an exception while executing the migration.

Thanks for the patch, but please also file a ticket to report the bug. A regression test is also required. See also our patch review checklist.

Closing in absence of a ticket and test.


Certain formulas prevent MathJax from finishing rendering

First of all I'd like to say thank you for building such an awesome piece of open source software! You guys rock!
Second of all I'm not super experienced with LaTex and JS so I might have missed a ticket for this issue - this might be a duplicate. If so then I'm sorry!
Alas, to the point. I'll be short. Entering following formula:
$$\begin{aligned}|A_1\cup\dots \cup A_n|&=\sum_i|A_i|-\sum_{i<j}|A_i\cap A_j|\\&+\sum_{i<j<k}|A_i\cap A_j\cap A_k|-\dots+(-1)^{n+1}|A_1\cap\dots\cap A_n|\end{aligned}$$

hangs MathJax - I'm not getting any rendered output.
Issue Summary
We're using MathJax to render LaTex formulas into SVGs and then display them in our app. One of our users recently reported that entering this formula prevented LaText from being displayed.
I did a bit of digging and it looks like this formula prevents any sort of output after MathJax hits it and tries to parse it.
Steps to Reproduce

Use the aforementioned formula in MathJax
MathJax hangs and doesn't produce any output

Expected: MathJax should return a rendered formula.
I've also tried using this formula in Live Demo mode on your website and here's the result I got (both browsers, see below):

Technical details:

MathJax Version: 2.6
Client OS: Mac OS X 10.11.5
Browser: Happened on both Safari Version 9.1.1 (11601.6.17) and Chrome Version 51.0.2704.84 (64-bit)

This is expected behavior.
If you don't  escape < > (and &), browser might parse them as element (or for & entity) names, leading to erratic DOM results.
Since this happens long before MathJax gets to the equation, there's nothing MathJax could do to work around this -- the DOM simply contains no discernible mathematics to pick up.
If you escape your strings properly, you shouldn't have any trouble.
You might also want to check out the docs of the noErrors and noUndefined extension, http://docs.mathjax.org/en/latest/tex.html#noerrors etc.

@pkra thanks for the info 🎉 that was the exact issue!
I'm closing this issue as it's working as expected.
One idea that came to my mind - perhaps it'd be nice to add escaping to aforementioned Live Demo? That would make experience consistent (aka that formula should work).
Or display information that this formula contains unescaped characters and thus it will not render correctly.
I'd love to do this myself, but my JS/HTML skills are a bit... rusty. 😉 Should I add this to https://github.com/mathjax/MathJax-website ?

One is allowed to enter HTML in the demo, and so unescaped characters are legal, and you are seeing the behavior the you would get if you entered that formula in an actual web page.  it is not clear to me how one would identify this situation (other than looking for "foreign" tags, like the <j> tag that your equation would introduce).  But foreign tags are also legal, so such a test would be quite fragile.

(aka that formula should work)

No, that formula should not work in an HTML page.  That's the point.  If you entered what you did in an HTML page and ran MathJax on it, you would get the same output you see above.  That's part of how HTML works, and MathJax can't resolve that in an HTML page, because the conversion to HTML tags has been completely long before MathJax runs.  So it can't spot this or fix it for you.
Some more information about the fact that you are entering HTML at the top of the demo is the only thing I can think of that would help the situation.  This is implicit in the fact that you are allowed to enter MathML tags, but it could be stated more explicitly.

@dpvc I see the point now, I forgot you can also input plain HTML there. Adding logic to validate input in this case sounds insanely complicated. You're completely right, this works exactly as it should right now.
Adding some sort of information that you're entering HTML there (and thus certain MathJax formulas might not work due to escaping) would be a nice touch there.
Sorry for the confusion and once again thanks for the feedback and the awesome framework you're building 🚀

Thanks for the kind words!

Np, you deserve it! I've added an issue on website repo to keep track of this!


Deleting

Can you add a feature to delete screens or something of that sort? It would be helpful.

Yes I will! :)

Pressing the 'delete' key on your keyboard should now delete the last screen that you interacted with


Latest release is missing linux and mac clients

Describe the bug
On the latest release 4.2.1, there aren't included packages for Linux or Mac clients is this intentional?
Because of it, the install.sh script is broken.
Steps to reproduce:
curl -sSL https://raw.githack.com/stoplightio/prism/master/install | sh
Error requesting. Download binary from https://github.com/stoplightio/prism/releases/latest/download/prism-cli-linux

https://github.com/stoplightio/prism/releases/tag/v4.2.1

@P0lip thanks, its good now thank you


[Drawer] Remove unreachable code in getSlideDirection

The function getSlideDirection gets one parameter. Its branches cover all of the options for an anchor prop for Drawer. Yet it still has a default return line which is unreachable because of the PropType set for the anchor prop.

[x] PR has tests / docs demo, and is linted.
[x] Commit and PR titles begin with [ComponentName], and are in imperative form: "[Component] Fix leaky abstraction".
[x] Description explains the issue / use-case resolved, and auto-closes the related issue(s) (http://tr.im/vFqem).

Thanks!

+0.04% 💪


'dotnet' is not recognized as an internal or external command

Problem encountered on https://dotnet.microsoft.com/en-us/learn/dotnet/hello-world-tutorial/install
Operating System: windows
Provide details about the problem you're experiencing. Include your operating system version, exact error message, code sample, and anything else that is relevant.

windows 10.1. exact error is title.

@thegopher4me did you install the SDK? And if so, did you open a new command prompt window after that?


Expiry is not set correctly in ActiveMQ

Expiry does not work as it should in MassTransit with ActiveMQ.
Consider this message for instance:

There, we can see that expirationTime in the "Message details" is set correctly to the expiry that I specified (in one day). However, the "Expiration" field under "Headers" is set to far into the future.
It looks like this leads to an issue where a message has not expired yet in ActiveMQ, but MassTransit refuses to consume pending messages, because they are technically expired to it. At least that's my main theory.
I'm setting TimeToLive on the context. I think MassTransit is then treating this incorrectly.

MassTransit sets the TimeToLive directly on the transport, I'm not sure how that translates to ActiveMQ:
   if (context.TimeToLive.HasValue)
                        transportMessage.NMSTimeToLive = context.TimeToLive > TimeSpan.Zero ? context.TimeToLive.Value : TimeSpan.FromSeconds(1);

MassTransit sets the TimeToLive directly on the transport, I'm not sure how that translates to ActiveMQ:
   if (context.TimeToLive.HasValue)
                        transportMessage.NMSTimeToLive = context.TimeToLive > TimeSpan.Zero ? context.TimeToLive.Value : TimeSpan.FromSeconds(1);

Is it correctly understood that the expirationTime in the JSON is MassTransit's, and the Expiration in the message headers is ActiveMQ?

Is it correctly understood that the expirationTime in the JSON is MassTransit's, and the Expiration in the message headers is ActiveMQ?

Is it correctly understood that the expirationTime in the JSON is MassTransit's, and the Expiration in the message headers is ActiveMQ?

Correct.

Is it correctly understood that the expirationTime in the JSON is MassTransit's, and the Expiration in the message headers is ActiveMQ?

Correct.

In that image, expirationTime and sentTime are days earlier than the Timestamp in ActiveMQ (same image). They're like a week apart.

In that image, expirationTime and sentTime are days earlier than the Timestamp in ActiveMQ (same image). They're like a week apart.

Ah yes. In that particular screenshot, the expiry is not one day. It's around a week, yes.

Ah yes. In that particular screenshot, the expiry is not one day. It's around a week, yes.

Hmmm yes. What do you mean by that though?

Hmmm yes. What do you mean by that though?

Why are they so far off?

Why are they so far off?

I think this particular message was scheduled.

I think this particular message was scheduled.

I also only think it happens for scheduled messages, now that I think about it.

I also only think it happens for scheduled messages, now that I think about it.

I also only think it happens for scheduled messages, now that I think about it.

Setting TimeToLive on scheduled messages seems like it would need to adjust based upon the scheduled time.

I also only think it happens for scheduled messages, now that I think about it.

Setting TimeToLive on scheduled messages seems like it would need to adjust based upon the scheduled time.

When you say "It" do you mean MassTransit, or ActiveMq?

When you say "It" do you mean MassTransit, or ActiveMq?

I can't think about this right now.

I can't think about this right now.

What does that mean? Do you need a break, or more time to think?
No rush either way. This particular issue can most likely be worked around.

What does that mean? Do you need a break, or more time to think?
No rush either way. This particular issue can most likely be worked around.

Related Question: https://stackoverflow.com/questions/65128514/in-masstransit-if-i-set-a-ttl-for-a-scheduled-message-is-the-initial-delay-incl

Related Question: https://stackoverflow.com/questions/65128514/in-masstransit-if-i-set-a-ttl-for-a-scheduled-message-is-the-initial-delay-incl

Which is a question I asked - a long time ago.
However, that's a question that asks how the delay works. But there is a bug too.
In the screenshot, notice ActiveMQ's expiry is<PHONE_NUMBER> seconds (epoch), which translates to 01/25/2021 @ 11:32pm (UTC). But the expiryTime is 2021-01-18T07:52:12.
That should never be possible, right?
If the expiry is set, those two numbers should be somewhat the same.
Something odd is happening.

Which is a question I asked - a long time ago.
However, that's a question that asks how the delay works. But there is a bug too.
In the screenshot, notice ActiveMQ's expiry is<PHONE_NUMBER> seconds (epoch), which translates to 01/25/2021 @ 11:32pm (UTC). But the expiryTime is 2021-01-18T07:52:12.
That should never be possible, right?
If the expiry is set, those two numbers should be somewhat the same.
Something odd is happening.

Time zone offset?

Time zone offset?

Not likely. All our servers (producers and the ActiveMQ server) are in eu-west-1 in AWS. So they should have UTC.
Funny thing. After reverting to the version that didn't use the new ActiveMQ implementation, the messages that weren't consumed before suddenly started getting consumed.
This seems to indicate that the new version introduces more errors than just #2255.

Not likely. All our servers (producers and the ActiveMQ server) are in eu-west-1 in AWS. So they should have UTC.
Funny thing. After reverting to the version that didn't use the new ActiveMQ implementation, the messages that weren't consumed before suddenly started getting consumed.
This seems to indicate that the new version introduces more errors than just #2255.

I can confirm now that the latest NuGet package does this, but if I downgrade to before the new ActiveMQ library was made, it seems it consumes all messages just fine.
All the messages that are "stuck" and not getting consumed, are all scheduled messages.

I can confirm now that the latest NuGet package does this, but if I downgrade to before the new ActiveMQ library was made, it seems it consumes all messages just fine.
All the messages that are "stuck" and not getting consumed, are all scheduled messages.

And they all share the same characteristics as mentioned above. Weird inconsistent timestamps.

And they all share the same characteristics as mentioned above. Weird inconsistent timestamps.

Yeah, with 7.1.5 I went back to the NetStd unofficial library as the official library which was neglected for nearly five years just isn't up to snuff with the fork that's been maintained all this time.
They need to seriously look at what's been done in the fork and make sure their library works (because there are so many breaks in it, I had to just walk away from it and continue with the forked version).

Yeah, with 7.1.5 I went back to the NetStd unofficial library as the official library which was neglected for nearly five years just isn't up to snuff with the fork that's been maintained all this time.
They need to seriously look at what's been done in the fork and make sure their library works (because there are so many breaks in it, I had to just walk away from it and continue with the forked version).

Since I've moved back to that other library, I'm going to close this.

Since I've moved back to that other library, I'm going to close this.


Add additional process attributes to registry

Changes
This PR adds additional fields from the ECS process schema to the process registry. The fields added are mainly based on the POSIX process model, and will allow sending enhanced process telemetry from these systems.
Merge requirement checklist

[x] CONTRIBUTING.md guidelines followed.
[x] CHANGELOG.md updated for non-trivial changes.
[x] schema-next.yaml updated with changes to existing conventions.

FYI @open-telemetry/semconv-system-approvers

I've removed env_vars from this PR, which I think was the source all the open discussions on this PR, and created https://github.com/open-telemetry/semantic-conventions/issues/672 to track and discuss it in the future

@mjwolf could you please update the PR to use new way  of adding a changelog entry?

I've changed to use the new changelog method

Hi @jsuereth, @lmolkova, @trisch-me, could you take a look at this PR again?  I've moved the process creation and exit fields into namespaces, added the experimental stability tag to all new fields, and resolved conflicts with main


Handle border width & color not working

New Issue Checklist

[x] Updated RangeSeekSlider to the latest version
[x] Checked Gitter

Issue Description
Setting handle border and color has no effect. Looks like its property is not even used in the code.
Environment
Just define a value for the border properties other than the color used for the handle itself.

Just the border color is not used. It is setting the same color for the border than the filling.


Is it possible to use envoy gateway 1.1.2 as a transparent proxy before redis cluster?

Description:
I have a redis cluster with 3 shards (1 master per shard as the PoC). The cluster sits inside the Kubernetes where EG is installed as well. Is it possible to use the CRDs this helm chart provides to build the configuration on top of that cluster?
I expected that it would be possible with kind: Backend and TCPRoute, but no... (ref)
Example here in the repo is not useful as well.
There are no examples how to set up filters and so on.

It looks like Gateway of gateway.networking.k8s.io, which contains spec.listeners does not support of specifying of filter_chains. That means we cannot simply use the CRD for the task, correct?

we may need a RedisRoute CRD to support this? Before that, we need to align with Gateway API project's roadmap.

for the time being , you can use EnvoyPatchPolicy as a workaround https://gateway.envoyproxy.io/docs/tasks/extensibility/envoy-patch-policy/  to add these Redis Cluster specific config https://www.envoyproxy.io/docs/envoy/latest/api-v3/extensions/clusters/redis/v3/redis_cluster.proto  to the xDS cluster config

Another option is using https://gateway.envoyproxy.io/docs/tasks/extensibility/extension-server/.

Hello @arkodg. I'm trying to do in this way:

envoy-gateway is deployed by the helm chart into sys-envoy-proxy namespace. Using ArgoCD for that (I think this is not a big deal). Helm chart values are:

---
deployment:
  replicas: 1
  pod:
    affinity: {}
    tolerations: []

config:
  envoyGateway:
    gateway:
      controllerName: gateway.envoyproxy.io/gatewayclass-controller
    provider:
      type: Kubernetes
    extensionApis:
      enableEnvoyPatchPolicy: true
      enableBackend: true
    logging:
      level:
        default: info

My Redis Cluster is located inside website-staging namespace (as well as the node.js application which should use that cluster).
After the deployment of envoy-gateway is done, trying to do the next:
a) Deploying of the EnvoyProxy with:

apiVersion: gateway.envoyproxy.io/v1alpha1
kind: EnvoyProxy
metadata:
  name: redis-cluster-proxy-config
  namespace: website-staging
spec:
  provider:
    type: Kubernetes
    kubernetes:
      envoyDeployment:
        replicas: 2
        container:
          resources:
            limits:
              cpu: 500m
              memory: 1Gi
            requests:
              cpu: 100m
              memory: 256Mi
      envoyHpa:
        minReplicas: 2
        maxReplicas: 3
        metrics:
          - resource:
              name: cpu
              target:
                averageUtilization: 60
                type: Utilization
            type: Resource
  bootstrap:
    type: Merge
    value: |
      static_resources:
        listeners:
          - name: redis_listener
            address:
              socket_address:
                address: <IP_ADDRESS>
                port_value: 6379
            filter_chains:
              - filters:
                  - name: envoy.filters.network.redis_proxy
                    typed_config:
                      "@type": type.googleapis.com/envoy.extensions.filters.network.redis_proxy.v3.RedisProxy
                      stat_prefix: redis_stats
                      prefix_routes:
                        catch_all_route:
                          cluster: redis_cluster
                      settings:
                        op_timeout: 5s
                        enable_redirection: true
                      # TODO: This gets deleted?? Why?
                      # Maybe this helps: https://github.com/envoyproxy/envoy/blob/release/v1.31/test/extensions/filters/network/redis_proxy/redis_proxy_integration_test.cc
                      downstream_auth_passwords:
                        - inline_string: qRpDh7a4Pt9jCSHM

        clusters:
          - name: redis_cluster
            connect_timeout: 1s
            dns_lookup_family: V4_ONLY
            load_assignment:
              cluster_name: redis_cluster
              endpoints:
                - lb_endpoints:
                    endpoint:
                      address:
                        socket_address:
                          address: redis-cluster-headless.website-staging.svc.cluster.local
                          port_value: 6379
            #hosts:
            #  - socket_address:
            #      address: redis-cluster-headless.website-staging.svc.cluster.local
            #      port_value: 6379
            cluster_type:
              name: envoy.clusters.redis
              typed_config:
                "@type": type.googleapis.com/google.protobuf.Struct
                value:
                  cluster_refresh_rate: 30s
                  cluster_refresh_timeout: 0.5s
                  redirect_refresh_interval: 10s
                  redirect_refresh_threshold: 10

b) Deploying GatewayClass as:
apiVersion: gateway.networking.k8s.io/v1
kind: GatewayClass
metadata:
  name: redis-eg-cls
  namespace: website-staging
spec:
  controllerName: gateway.envoyproxy.io/gatewayclass-controller
  parametersRef:
    group: gateway.envoyproxy.io
    kind: EnvoyProxy
    name: redis-cluster-proxy-config
    namespace: website-staging

c) Deploying Gateway as:
apiVersion: gateway.networking.k8s.io/v1
kind: Gateway
metadata:
  name: eg-gw
  namespace: website-staging
spec:
  gatewayClassName: redis-eg-cls
  infrastructure:
    parametersRef:
      group: gateway.envoyproxy.io
      kind: EnvoyProxy
      name: redis-cluster-proxy-config
  listeners:
    - name: redis-listener
      protocol: TCP
      port: 6379

As a result I can see envoy-website-staging-eg-gw-12e00436 Deployment had appeared inside sys-envoy-proxy namespace with 2 pods under it. The logs of the pod say:
[2024-10-07 19:52:52.548][1][warning][misc] [source/extensions/filters/network/http_connection_manager/config.cc:83] internal_address_config is not configured. The existing default behaviour will trust RFC1918 IP addresses, but this will be changed in next release. Please explictily config internal address config as the migration step.
[2024-10-07 19:52:52.549][1][warning][redis] [source/extensions/filters/network/redis_proxy/proxy_filter.cc:33] redirections without DNS lookups enabled might cause client errors, set the dns_cache_config field within the connection pool settings to avoid them
[2024-10-07 19:52:52.582][1][warning][config] [source/extensions/config_subscription/grpc/delta_subscription_state.cc:269] delta config for type.googleapis.com/envoy.config.listener.v3.Listener rejected: Error adding/updating listener(s) website-staging/eg-gw/redis-listener: error adding listener '<IP_ADDRESS>:6379': no filter chains specified
[2024-10-07 19:52:52.582][1][warning][config] [source/extensions/config_subscription/grpc/grpc_subscription_impl.cc:138] gRPC config for type.googleapis.com/envoy.config.listener.v3.Listener rejected: Error adding/updating listener(s) website-staging/eg-gw/redis-listener: error adding listener '<IP_ADDRESS>:6379': no filter chains specified

Connecting using redis-cli with auth does not work. downstream_auth_passwords: is not available in the envoy-proxy pod as well. Also don't know what to do with those warnings.

Redid EnvoyProxy configuration. Looks like this now:
---
apiVersion: gateway.envoyproxy.io/v1alpha1
kind: EnvoyProxy
metadata:
  name: redis-cluster-proxy-config
  namespace: website-staging
spec:
  provider:
    type: Kubernetes
    kubernetes:
      envoyDeployment:
        replicas: 2
        container:
          resources:
            limits:
              cpu: 500m
              memory: 1Gi
            requests:
              cpu: 100m
              memory: 256Mi
        patch:
          type: StrategicMerge
          value:
            spec:
              template:
                spec:
                  containers:
                    - name: curl
                      image: curlimages/curl:8.10.1
                      command:
                        - "sleep"
                        - "infinity"
                      resources:
                        requests:
                          cpu: 100m
                          memory: 20Mi
                        limits:
                          cpu: 200m
                          memory: 126Mi
                      securityContext:
                        allowPrivilegeEscalation: false
                        capabilities:
                          drop:
                            - ALL
                        privileged: false
                        readOnlyRootFilesystem: true
                        runAsGroup: 1001
                        runAsNonRoot: true
                        runAsUser: 1001
                        seccompProfile:
                          type: RuntimeDefault
      envoyService:
        name: redis-envoy-service
        type: ClusterIP
        annotations:
          custom1: svc-annotation1
          custom2: svc-annotation2
      envoyHpa:
        minReplicas: 2
        maxReplicas: 3
        metrics:
          - resource:
              name: cpu
              target:
                averageUtilization: 60
                type: Utilization
            type: Resource
  logging:
    level:
      default: info
  bootstrap:
    type: Merge
    value: |
      static_resources:
        listeners:
          - name: redis_listener
            address:
              socket_address:
                address: <IP_ADDRESS>
                port_value: 6379
            filter_chains:
              - filters:
                  - name: envoy.filters.network.redis_proxy
                    typed_config:
                      "@type": type.googleapis.com/envoy.extensions.filters.network.redis_proxy.v3.RedisProxy
                      stat_prefix: redis_stats
                      prefix_routes:
                        catch_all_route:
                          cluster: redis_cluster
                      settings:
                        op_timeout: 5s
                        enable_redirection: true
                      downstream_auth_username:
                        inline_string: default
                      downstream_auth_passwords:
                        - inline_string: qRpDh7a4Pt9jCSHM

        clusters:
          - name: redis_cluster
            connect_timeout: 1s
            dns_lookup_family: V4_ONLY
            #type: STRICT_DNS
            #lb_policy: ROUND_ROBIN
            #load_assignment:
            #  cluster_name: redis_cluster
            #  endpoints:
            #    - lb_endpoints:
            #        endpoint:
            #          address:
            #            socket_address:
            #              address: redis-cluster-headless.website-staging.svc.cluster.local
            #              port_value: 6379
            hosts:
              - socket_address:
                  address: redis-cluster-headless.website-staging.svc.cluster.local
                  port_value: 6379

            cluster_type:
              name: envoy.clusters.redis
              typed_config:
                "@type": type.googleapis.com/google.protobuf.Struct
                value:
                  cluster_refresh_rate: 30s
                  cluster_refresh_timeout: 0.5s
                  redirect_refresh_interval: 10s
                  redirect_refresh_threshold: 10

            typed_extension_protocol_options:
              envoy.filters.network.redis_proxy:
                "@type": type.googleapis.com/envoy.extensions.filters.network.redis_proxy.v3.RedisProtocolOptions
                auth_username:
                  inline_string: default
                auth_password:
                  inline_string: qRpDh7a4Pt9jCSHM

The problem now is with the healthcheck:
Startup probe failed: Get "http://<IP_ADDRESS>:19001/ready": dial tcp <IP_ADDRESS>:19001: connect: connection refused

I'd added curl sidecar. Doing the request to that address fails. Another request to http://<IP_ADDRESS>:19000/ready shows PRE_INITIALIZING

...Added debug log, have this:
[2024-10-08 17:58:46.144][1][debug][main] [source/server/server.cc:247] Envoy is not fully initialized, skipping histogram merge and flushing stats
[2024-10-08 17:58:46.225][1][debug][dns] [source/extensions/network/dns_resolver/cares/dns_impl.cc:385] dns resolution for envoy-gateway started
[2024-10-08 17:58:46.225][1][debug][dns] [source/extensions/network/dns_resolver/cares/dns_impl.cc:385] dns resolution for envoy-gateway started
[2024-10-08 17:58:46.227][1][debug][dns] [source/extensions/network/dns_resolver/cares/dns_impl.cc:167] dns resolution without records for envoy-gateway
[2024-10-08 17:58:46.227][1][debug][dns] [source/extensions/network/dns_resolver/cares/dns_impl.cc:167] dns resolution without records for envoy-gateway
[2024-10-08 17:58:46.228][1][debug][dns] [source/extensions/network/dns_resolver/cares/dns_impl.cc:302] dns resolution for envoy-gateway completed with status 0
[2024-10-08 17:58:46.228][1][debug][upstream] [source/common/upstream/upstream_impl.cc:469] transport socket match, socket default selected for host with address <IP_ADDRESS>:18002
[2024-10-08 17:58:46.228][1][debug][upstream] [source/extensions/clusters/strict_dns/strict_dns_cluster.cc:193] DNS refresh rate reset for envoy-gateway, refresh rate 5000 ms
[2024-10-08 17:58:46.228][1][debug][dns] [source/extensions/network/dns_resolver/cares/dns_impl.cc:302] dns resolution for envoy-gateway completed with status 0
[2024-10-08 17:58:46.228][1][debug][upstream] [source/common/upstream/upstream_impl.cc:469] transport socket match, socket default selected for host with address <IP_ADDRESS>:18000
[2024-10-08 17:58:46.228][1][debug][upstream] [source/extensions/clusters/strict_dns/strict_dns_cluster.cc:193] DNS refresh rate reset for envoy-gateway, refresh rate 5000 ms
[2024-10-08 17:58:51.147][1][debug][main] [source/server/server.cc:237] flushing stats

...added dnsutil sidecar, the DNS name is resolveable and provides the endpoints:
bash-5.0$ cat /etc/resolv.conf
search sys-envoy-proxy.svc.cluster.local svc.cluster.local cluster.local ec2.internal
nameserver <IP_ADDRESS>
options ndots:5

bash-5.0$ dig redis-cluster-headless.website-staging.svc.cluster.local

; <<>> DiG 9.16.27 <<>> redis-cluster-headless.website-staging.svc.cluster.local
;; global options: +cmd
;; Got answer:
;; WARNING: .local is reserved for Multicast DNS
;; You are currently testing what happens when an mDNS query is leaked to DNS
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 62564
;; flags: qr aa rd; QUERY: 1, ANSWER: 3, AUTHORITY: 0, ADDITIONAL: 1
;; WARNING: recursion requested but not available

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
; COOKIE: b7a714e91e52331f (echoed)
;; QUESTION SECTION:
;redis-cluster-headless.website-staging.svc.cluster.local. IN A

;; ANSWER SECTION:
redis-cluster-headless.website-staging.svc.cluster.local. 5 IN A <IP_ADDRESS>
redis-cluster-headless.website-staging.svc.cluster.local. 5 IN A <IP_ADDRESS>
redis-cluster-headless.website-staging.svc.cluster.local. 5 IN A <IP_ADDRESS>

;; Query time: 0 msec
;; SERVER: <IP_ADDRESS>#53(<IP_ADDRESS>)
;; WHEN: Tue Oct 08 18:18:58 UTC 2024
;; MSG SIZE  rcvd: 345

...have no idea what is going on here. Could be similar to envoyproxy/envoy#8223

...don't know, but envoyproxy/envoy:distroless-v1.31.2 image cannot use Redis. Stuck in that PRE_INITIALIZING state and that's it.

The problem was with load_assignment block. missed - before endpoint word.
The final EnvoyProxy looks like:
---
apiVersion: gateway.envoyproxy.io/v1alpha1
kind: EnvoyProxy
metadata:
  name: redis-cluster-proxy-config
  namespace: website-staging
spec:
  provider:
    type: Kubernetes
    kubernetes:
      envoyDeployment:
        replicas: 2
        container:
          resources:
            limits:
              cpu: 500m
              memory: 1Gi
            requests:
              cpu: 100m
              memory: 256Mi
        patch:
          type: StrategicMerge
          value:
            spec:
              template:
                spec:
                  containers:
                    - name: envoy
                      ports:
                        - containerPort: 6379
                          name: tcp-6379
                          protocol: TCP
                        - containerPort: 19001
                          name: metrics
                          protocol: TCP
                        - containerPort: 19000
                          name: admin
                          protocol: TCP
                    - name: curl
                      image: curlimages/curl:8.10.1
                      imagePullPolicy: IfNotPresent
                      command:
                        - "sleep"
                        - "infinity"
                      resources:
                        requests:
                          cpu: 100m
                          memory: 20Mi
                        limits:
                          cpu: 200m
                          memory: 126Mi
                      securityContext:
                        allowPrivilegeEscalation: false
                        capabilities:
                          drop:
                            - ALL
                        privileged: false
                        readOnlyRootFilesystem: true
                        runAsGroup: 1001
                        runAsNonRoot: true
                        runAsUser: 1001
                        seccompProfile:
                          type: RuntimeDefault
                    - name: dnsutils
                      image: registry.k8s.io/e2e-test-images/agnhost:2.39
                      imagePullPolicy: IfNotPresent
                      resources:
                        requests:
                          cpu: 100m
                          memory: 20Mi
                        limits:
                          cpu: 200m
                          memory: 126Mi
                      securityContext:
                        allowPrivilegeEscalation: false
                        capabilities:
                          drop:
                            - ALL
                        privileged: false
                        readOnlyRootFilesystem: true
                        runAsGroup: 1001
                        runAsNonRoot: true
                        runAsUser: 1001
                        seccompProfile:
                          type: RuntimeDefault
      envoyService:
        name: redis-envoy-service
        type: ClusterIP
        annotations:
          custom1: svc-annotation1
          custom2: svc-annotation2
      envoyHpa:
        minReplicas: 2
        maxReplicas: 3
        metrics:
          - resource:
              name: cpu
              target:
                averageUtilization: 60
                type: Utilization
            type: Resource
  logging:
    level:
      default: debug
  bootstrap:
    type: Merge
    value: |
      admin:
        address:
          socketAddress:
            address: <IP_ADDRESS>
            portValue: 19000

      static_resources:
        listeners:
          - name: redis_listener
            address:
              socket_address:
                address: <IP_ADDRESS>
                port_value: 6379
            filter_chains:
              - filters:
                  - name: envoy.filters.network.redis_proxy
                    typed_config:
                      "@type": type.googleapis.com/envoy.extensions.filters.network.redis_proxy.v3.RedisProxy
                      stat_prefix: redis_stats
                      prefix_routes:
                        catch_all_route:
                          cluster: redis_cluster
                      settings:
                        op_timeout: 5s
                        enable_redirection: true
                      downstream_auth_username:
                        inline_string: default
                      downstream_auth_passwords:
                        - inline_string: qRpDh7a4Pt9jCSHM

        clusters:
          - name: redis_cluster
            connect_timeout: 1s
            load_assignment:
              cluster_name: redis_cluster
              endpoints:
                - lb_endpoints:
                    - endpoint:
                        address:
                          socket_address:
                            address: redis-cluster-headless.website-staging.svc.cluster.local
                            port_value: 6379
            dns_lookup_family: V4_ONLY
            lb_policy: ROUND_ROBIN
            upstream_connection_options:
              tcp_keepalive:
                keepalive_time: 60
                keepalive_probes: 1
                keepalive_interval: 5
            type: STRICT_DNS
            typed_extension_protocol_options:
              envoy.filters.network.redis_proxy:
                "@type": type.googleapis.com/envoy.extensions.filters.network.redis_proxy.v3.RedisProtocolOptions
                auth_username:
                  inline_string: default
                auth_password:
                  inline_string: qRpDh7a4Pt9jCSHM

glad you got it working @zentavr
my suggestion would be to implement this via TCPRoute + Backend + EnvoyPatchPolicy (edit cluster fields
once https://github.com/envoyproxy/gateway/issues/4036 has been fixed

@arkodg I think the trick is to set up those filters and redis stuff like timeouts and credentials. And the filters need to be done in the listener and at the cluster blocks of the configuration. Does TCPRoute/Backend support the filters?

extensionApis:
      enableEnvoyPatchPolicy: true
      enableBackend: true

where are these documented at?

@davem-git extensionsApis.enableEnvoyPatchPolicy  is here
extensionsApis.enableBackend is here


Azure Databricks Workspace and Azure Analysis Services missing

Azure Databricks Workspace and Azure Analysis Services is missing in the resource type prefix list. Perhaps "dbw-" and "as-"?

This issue has been resolved. Thanks!


Removing the necessity of associating organisation roles with Applications

There are two types of roles introduced from IS 7.0.0 onwards “application audience roles” and “organization audience roles”. The “organization-audience” roles serve the purpose of being reused across multiple applications. The main use case of the “organization audience roles”  is when an omnichannel application that uses the same set of roles is configured in IS as different applications (web app and mobile app). In addition to the aforementioned points, in the B2B use case, the roles related to B2B applications’ intended role audience should be available in sub-organizations to assign roles to users/groups of sub-organizations. This facilitates effective management of entitlements within the system.
The implementation of IS-7.0.0 aligns with achieving the above two main use cases.
There the organization-audience roles needed to be explicitly associated with an application for role consumption in application authorization mainly targeting the use-case of B2B where the requirement is to share all roles or a set of roles within the organizations. However, we noticed that the necessity for explicit association of organization roles with applications will raise a user experience issue for B2E applications. Even though the role creation is one-time, the developer has to navigate through all the required applications and associate the role.
To address the user experience issue mentioned above, the modification will be to remove the necessity to associate organization audience roles with applications. Then if an application is expected to consume the organization's audience roles, all the organization-level created roles will be effective.

https://github.com/wso2/carbon-identity-framework/pull/5619
https://github.com/wso2-extensions/identity-inbound-auth-oauth/pull/2425
https://github.com/wso2-extensions/identity-organization-management/pull/357
https://github.com/wso2/identity-api-server/pull/604
https://github.com/wso2/identity-apps/pull/5922

Remaining items.

[ ] To update documentation
[ ] To update IS 7 migration client
[ ] To write unit tests


why for $valve

@rultor release, tag is 0.15.5

@rultor release, tag is 0.15.5

@yegor256 OK, I will release it now. Please check the progress here

@rultor release, tag is 0.15.5

@yegor256 Done! FYI, the full log is here (took me 9min)

@rultor release, tag is 0.15.6

@rultor release, tag is 0.15.6

@yegor256 OK, I will release it now. Please check the progress here

@rultor release, tag is 0.15.6

@yegor256 Done! FYI, the full log is here (took me 8min)


Server repairs

I'm currently repairing a server and I need to bring another server down because of it. Hopefully everything will be done quickly.


Documentation: "Creating Custom Estimators" says that it uses same train_input_fn as "pre-made Estimator implementation", but replaces the dataset return value by an iterator.get_next() without explaining

Please go to Stack Overflow for help and support:
https://stackoverflow.com/questions/tagged/tensorflow
If you open a GitHub issue, here is our policy:

It must be a bug, a feature request, or a significant problem with documentation (for small docs fixes please send a PR instead).
The form below must be filled out.
It shouldn't be a TensorBoard issue. Those go here.

Here's why we have that policy: TensorFlow developers respond to issues. We want to focus on work that benefits the whole community, e.g., fixing bugs and adding features. Support only helps individuals. GitHub also notifies thousands of people when issues are filed. We want them to see you communicating an interesting problem, rather than being redirected to Stack Overflow.

System information

Have I written custom code (as opposed to using a stock example script provided in TensorFlow):No
OS Platform and Distribution (e.g., Linux Ubuntu 16.04):na
Mobile device (e.g. iPhone 8, Pixel 2, Samsung Galaxy) if the issue happens on mobile device:na
TensorFlow installed from (source or binary):na
TensorFlow version (use command below):na
Python version:na
Bazel version (if compiling from source):na
GCC/Compiler version (if compiling from source):na
CUDA/cuDNN version:na
GPU model and memory:na
Exact command to reproduce:na

You can collect some of this information using our environment capture script:
https://github.com/tensorflow/tensorflow/tree/master/tools/tf_env_collect.sh
You can obtain the TensorFlow version with
python -c "import tensorflow as tf; print(tf.GIT_VERSION, tf.VERSION)"
Describe the problem
Describe the problem clearly here. Be sure to convey here why it's a bug in TensorFlow or a feature request.
In the documentation "Creating Custom Estimators" (https://www.tensorflow.org/guide/custom_estimators), under "Write an Input function", it is claimed that the function is the same as in "pre-made Estimator implementation" (https://www.tensorflow.org/guide/premade_estimators) and in iris_data.py (https://github.com/tensorflow/models/blob/master/samples/core/get_started/iris_data.py). But in both these sources the function is returning the created dataset, while in "Creating Custom Estimators" the function returns dataset.make_one_shot_iterator().get_next() instead.
I haven't been able to understand if both approaches are equivalent, or if both are correct but yield different results, or if one of them is wrong. But in any of these situations, I think the documentation should state why it is using the get next operations instead of the original dataset, since it refers to sources where dataset is used instead.
Source code / logs
Include any logs or source code that would be helpful to diagnose the problem. If including tracebacks, please include the full traceback. Large logs and files should be attached. Try to provide a reproducible test case that is the bare minimum necessary to generate the problem.
"Creating Custom Estimators": https://www.tensorflow.org/guide/custom_estimators
Claim: "Our custom Estimator implementation uses the same input function as our pre-made Estimator implementation, from iris_data.py. Namely:"
Function:
def train_input_fn(features, labels, batch_size):
    """An input function for training"""
    # Convert the inputs to a Dataset.
    dataset = tf.data.Dataset.from_tensor_slices((dict(features), labels))

    # Shuffle, repeat, and batch the examples.
    dataset = dataset.shuffle(1000).repeat().batch(batch_size)

    # Return the read end of the pipeline.
    return dataset.make_one_shot_iterator().get_next()

"Premade Estimators": https://www.tensorflow.org/guide/premade_estimators
Function:
def train_input_fn(features, labels, batch_size):
    """An input function for training"""
    # Convert the inputs to a Dataset.
    dataset = tf.data.Dataset.from_tensor_slices((dict(features), labels))

    # Shuffle, repeat, and batch the examples.
    return dataset.shuffle(1000).repeat().batch(batch_size)

iris_data.py: https://github.com/tensorflow/models/blob/master/samples/core/get_started/iris_data.py
Function:
def train_input_fn(features, labels, batch_size):
    """An input function for training"""
    # Convert the inputs to a Dataset.
    dataset = tf.data.Dataset.from_tensor_slices((dict(features), labels))
    # Shuffle, repeat, and batch the examples.
    dataset = dataset.shuffle(1000).repeat().batch(batch_size)
    # Return the dataset.
    return dataset

Nagging Assignee @MarkDaoust: It has been 14 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.

Nagging Assignee @MarkDaoust: It has been 29 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.

Nagging Assignee @MarkDaoust: It has been 44 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.

Yes, these docs have gotten out of sync.
The only reasonable direction to go for these is to update them to be .ipynb notebooks, inline all the code and delete those example directories.

Nagging Assignee @MarkDaoust: It has been 32 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.


ActiveDirectoryResourceId is missing in the environment configs

Looks like Go SDK uses ServiceManagementEndpoint parameter to refer to token audience. Other SDKs (Ruby/CLI/Python) call this parameter as ActiveDirectoryResourceId. Should we stick to the same name across different SDKs?

@seyadava not sure what you mean by pasting that email here

@seyadava @vladbarosan  we agreed offline that we wouldn't remove the ServiceManagementEndpoint field but could still consider adding an ActiveDirectoryResourceID field.
Still, IMHO ActiveDirectoryResourceID is a generic name for a scope/resource (token audience) and @seyadava a more specific name should be used in other SDKs rather than adding a generic name here.

Closing as we aren't renaming this.


Fix incorrect cron expression in test case test_server_recompile (#5922)

Pull request opened by the merge tool on behalf of #5922

Merged into branches iso6 in d92824dcedc48737386fedd09fa0999a38e22409


Print statement doesn't support print lists

BrightScript's print statement is surprisingly powerful.  It supports tabulated output (via print "foo", "bar", "baz"), where a comma prints the next expression at the next 16-character "tab stop".  It also supports printing multiple expressions with no space in between with a semiclon (e.g. print "hello"; "world"   ' prints 'helloworld').  It's all rather complicated.
https://sdkdocs.roku.com/display/sdkdoc/Program+Statements#ProgramStatements-PRINTitemlist has the official docs.  I'm not sure if fixing this issue requires pos(x) and tab(expression) to also be implemented, since they're "global functions" but are probably only valid within an print statement.

Fixed in v0.8.0