Revert "Delete tests for property which no longer exists"

These tests are still important as setDestination still exists, so these properties could still be wired like this.
This reverts commit 80cafb1d658988f905a5df34f0a545a3c0373d19.

@bot-gradle test and merge

Your PR is queued. See the queue page for details.

I've triggered a build for you.


Outline and progress

Here is the current outline for the documentation. Checked items are completed and ready for review.
Summary

[ ] Getting Started

[ ] Quick Start
[ ] Your First App

[x] Services
[ ] REST
[ ] Real-Time

[ ] Events
[ ] Socket.io
[ ] Primus

[ ] Databases

[ ] Querying and Pagination
[ ] In Memory
[ ] NeDB
[ ] Mongoose
[ ] Sequelize
[ ] KnexJS
[ ] Waterline

[ ] Middleware

[ ] Hooks
[ ] Express middleware
[ ] Versioning

[ ] Authentication
[ ] Authorization
[ ] Front End
[x] API Documentation
[ ] Guides

[ ] Creating a plugin
[ ] React and React Native
[ ] CanJS

[ ] Feathers vs.
[ ] FAQ
[ ] Getting Help
[ ] Contributing
[ ] Changelog
[x] License

/cc @marshallswain @ekryski and anybody else for thoughts

This layout makes much more sense.
Do we want an Examples section, I'd say toward the end, for things like the feathers-react-native-chat  Actually, weren't we planning some npm integration with the site that crawls the feathers-plugin tag?
Is there a provider spec that we could show somewhere so users could build more providers?
How about the plugin docs?  Where would, say, feathers-configuration docs go?  Stay in the README?  Maybe an official plugins section.
What are the thoughts on the Microservices section and the Performances sections that were removed?

I don't want the guides part to be a dumping ground but I think that a lot of what you mentioned @marshallswain could maybe go in there for now?? We might need an examples section later though.
I do think we probably need a plugins section.

I'd like to make a plugin guide but I don't think anybody will create their own provider any time soon (maybe as feature requests but then we can always create a guide later).
I think the guides can for now be a dumping ground for things that aren't fully fleshed out yet and client framework specific guides (so it doesn't look like Framework X isn't supported, we just don't have a guide for it). I'd also include the React Native Chat there in the "React and React Native" guide and maybe a page for examples (if we have enough?) and an overview of incubating plugins (like feathers-batch or feathers-sync) with a short description and a link to their repository.
We should keep track of questions and topics that come up more often and turn them into top level topics when there is enough solid content and interest.

Here is my current progress of chapters that I wrote and reviewed (which means they definitely have to be reviewed by someone else ;):

[ ] Getting Started

[ ] Quick Start
[ ] Your First App

[ ] Why Feathers

[ ] Express + Socket.io
[ ] Feathers vs Meteor
[ ] Feathers vs Sails
[ ] Feathers vs Firebase

[ ] Services
[ ] REST
[ ] Real-Time

[ ] Service events
[ ] Socket.io
[ ] Primus
[ ] Event Filtering

[ ] Client Use

[ ] Universal Feathers
[ ] REST
[ ] Socket.io
[ ] Primus

[ ] Databases

[ ] Pagination and sorting
[ ] Querying
[ ] Extending adapters
[ ] In Memory
[ ] NeDB
[ ] Mongoose
[ ] Sequelize
[ ] KnexJS
[ ] Waterline

[ ] Hooks

[ ] Bundled hooks

[ ] Middleware

[ ] Express Middleware
[ ] Routing and Versioning

[ ] Authentication

[ ] Local (username & password)
[ ] OAuth (Twitter, Facebook, etc)
[ ] Two-Factor (MFA)

[ ] Authorization / Access Control

[ ] Bundled Auth Hooks

[ ] API
[ ] Guides

[ ] Migrating to Feathers 2
[ ] Creating a plugin
[ ] React and React Native
[ ] CanJS

[ ] Help

[ ] FAQ
[ ] Contributing
[ ] Changelog

[ ] License

I just wrapped up the last core piece. I think we can probably close this issue now and create separate issues for each guide.
Wahoo nice work @marshallswain and @daffl! :tada: :beers:

Awesome.


New rate limit for the audit log API endpoints

Summary
The audit log API endpoint will impose a rate limit of 15 queries per minute per enterprise or org starting August 1st, 2023. To prepare for this change, Enterprises and Organizations currently exceeding this limit should ensure individuals, applications and integrations querying the audit log API:

Query at a maximum frequency of 15 queries per minute, and/or;
Honor HTTP 429 and HTTP 403 responses, as outline in our documentation for rate limits for requests from personal accounts and rate limits for GitHub Apps

Intended Outcome
A high-quality audit log is an essential tool used by enterprises to ensure compliance, maintain security, investigate issues, and promote accountability. To support these objectives, the audit log API needs to be highly reliable, consistently available, and extremely scalable. The new rate limit safeguards the audit log APIs availability and scalability by providing back pressure to individuals, applications, or integrations querying the audit log APIs.
How will it work?
When the 15 query per minute rate limit is exceeded, the audit log API will return either a HTTP 429 or HTTP 403 response indicating that a rate limit has been reached. When these responses are received, the querying entity should wait at least 4 seconds before attempting to query the audit log API again.

🚢 This has shipped: https://github.blog/changelog/2023-08-01-new-rate-limit-for-the-audit-log-api-endpoints-is-active


Arrival timetable

Describe wanted Enhancement !
Arrival timetable for stations
Why should we put effort in it ?
Similar to the departure time table arrivals for stations would be helpful so user of visualization may obtain information like "dad is in time / will be late by 20 minutes"
Additional context
hafas-client already implents arrival and departure timetables

Hi @murki25
can't you use the route-function ?

It's the last station on (one) line. I could use the route function from the last stop before that station, but that result will be available only until the train reaches that last station.
-> Planned arrival on station B is 18:00, if using route from A to B will give me e.g. 17:50 A -> 18:02 B (2 min delayed) but this information will be available only up to 17:50 as only future routes are listed.

Reopen

Hi @murki25
I'm sorry, but I don't have much time at the moment.
I will keep your feature request in backlog. When more users request it, I will integrate your request.
I hope this is ok for you.
Regards, Ralf


disable-endpoint-check required during installation on private AKS cluster

What happened:
Got the following error when installing on a private AKS cluster:
While installing on a private AKS cluster, got this error.
Error extracting chart parameters: the retrieved cluster information and the cluster selected in the kubeconfig do not match
It works when adding --disable-endpoint-check to the liqoctl install aks ... command. This is most likely due to the AKS API DNS resolving to <cluster-name>.privatelink.<azure-region>.azmk8s.io. It adds privatelink to the k8s API URI when it's deployed in private mode.
Not necessarily a bug, but could use better documentation?
Environment:

Liqo version: v0.4.0
Kubernetes version (use kubectl version):

Client Version: version.Info{Major:"1", Minor:"21", GitVersion:"v1.21.2", GitCommit:"092fbfbf53427de67cac1e9fa54aaa09a28371d7", GitTreeState:"clean", BuildDate:"2021-06-16T12:59:11Z", GoVersion:"go1.16.5", Compiler:"gc", Platform:"windows/amd64"}
Server Version: version.Info{Major:"1", Minor:"23", GitVersion:"v1.23.3", GitCommit:"4015228033c2306f221f84754fdf59f6d2a59891", GitTreeState:"clean", BuildDate:"2022-04-01T00:49:04Z", GoVersion:"go1.17.6", Compiler:"gc", Platform:"linux/amd64"}

Cloud provider or hardware configuration: AKS
Network plugin and version: Azure CNI

Hi @colincmac,
Thanks for the suggestions, much appreciated.
We will perform a few tests and integrate them in the new documentation we are currently working on.


175893 - [ASA] - Bypassable business logic

Business logic vulnerabilities often arise due to the flawed assumptions about how users will interact with the application. These bad assumptions can lead to inadequate validation of user input.
1.From date to date .
'1. Avoid making implicit assumptions about user behaviour or the behaviour of other functions of the application
2. Identify what assumptions have been made about the server-side state and implement the necessary logic to verify that these assumptions are met. This includes making sure that the value of any input is sensible before proceeding
When from date is modified with the future date and to date to previous date application gives the 200 response

Azdo link: https://dev.azure.com/accenturecio26/WebContentDigAssetMgmt_PR1093/_workitems/edit/175893
cc: @ravkiran @amol-anand @raymond-h-dev

@amol-anand @ravkiran - this is kind of backend related issue. can we take a look on this?

@raymond-h-dev there's no server side logic running here, when the user selects the date, it tries to find the results from the query-index.json, if anything falls into this category, otherwise it returns empty results
For example in this request, from_date is 2025, https://main--accenture-newsroom--hlxsites.hlx.page/?to_date=4%2F14%2F2021&from_date=10%2F27%2F2025, so the results is empty, as there're no results that fall into this range. I don't see a problem with this, what is the issue?

@ravkiran  @amol-anand fyi this a low priority bug. we can fix this post go live. thanks


Report Section to report the discovered incident using a marker

Community app user able to report the incident that he/she got. via a report or location marker

fixes by #166


add graphql schema

Description

References

#0000

Codecov Report

Merging #1480 (5c55b72) into main (10c54ca) will increase coverage by 19.60%.
The diff coverage is 0.00%.

@@             Coverage Diff             @@
##             main    #1480       +/-   ##
===========================================
+ Coverage   31.80%   51.40%   +19.60%
===========================================
  Files          54       69       +15
  Lines         827     1208      +381
  Branches       47        0       -47
===========================================
+ Hits          263      621      +358
- Misses        554      572       +18
- Partials       10       15        +5

Impacted Files
Coverage Δ

...ntrollers/MarketParticipantPermissionController.cs
0.00% <0.00%> (ø)

...taHub.WebApi/Controllers/Wholesale/Dto/BatchDto.cs
0.00% <0.00%> (-100.00%)
:arrow_down:

...trollers/MarketParticipant/Dto/FilteredActorDto.cs
16.66% <0.00%> (-83.34%)
:arrow_down:

...gistration/HealthEndpointRegistrationExtensions.cs
45.45% <0.00%> (-36.37%)
:arrow_down:

...WebApi/RequireNonNullablePropertiesSchemaFilter.cs
80.00% <0.00%> (-8.00%)
:arrow_down:

apps/dh/api-dh/source/DataHub.WebApi/Startup.cs
91.66% <0.00%> (-0.93%)
:arrow_down:

.../DataHub.WebApi.Tests/Integration/EndpointTests.cs
100.00% <0.00%> (ø)

...Tests/ServiceMocks/JwtAuthenticationServiceMock.cs
100.00% <0.00%> (ø)

...ntegration/Controllers/WholesaleControllerTests.cs
97.75% <0.00%> (ø)

...rce/DataHub.WebApi.Tests/Fixtures/WebApiFactory.cs
90.00% <0.00%> (ø)

... and 11 more

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


fix: remove count and for each from attrs (CLOUD-1764)

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

Thanks @alexpetrean80!
Thinking about this more, I don't like that something like WithCount/WithForEach which should idiomatically only add a count goes and modifies the attributes in place.  I guess the problem is that we're conflating different responsibilities a bit: we're setting WithCount/WithForEach from the "outside" of the term; but this is really an internal attribute.
I would therefore propose the following implementation strategy:

WithCount and WithForEach should be removed from term.go.
Instead, TermFromBody should determine whether or not there is a count or for_each attribute and set this accordingly; and then delete the corresponding thing from attrs.

I realize this is a bit of a bigger refactoring but I think it's worth it and it will improve the design overall: this way we can just call TermFromBody which will do the right thing.
Feel free to ping me on Slack if you have questions on this, or we can look at it together again.

The CI failed because we're expecting a new CHANGELOG entry.  You can generate this by using make install_tools (to get changie), then running changie new, pick Fix and write down a message, then add the generated file(s) to the git index.


Explicitly support dispatching to multiple GPUs

It should be possible to explicitly dispatch a model on multiple GPUs.
This probably affects data operations and .cuda() calls.

Using DataParallel in the module itself is currently possible. Assigning the devices could be done using a module__dataparallel__device parameter or something similar. We could still think about supporting multiple devices in NeuralNet though but this is not a priority for 0.3.0.


Move tasks under 'agent' subcommand

What does this PR do?
Move Agent-related tasks away from ddev release into their own subcommand:
(core3) ↳ ddev agent
Usage: ddev agent [OPTIONS] COMMAND [ARGS]...

Options:
  -h, --help  Show this message and exit.

Commands:
  changelog     Provide a list of updated checks on a given Datadog Agent
                version, in changelog form
  requirements  Generate the list of integrations to ship with the Agent and
                save it to 'requirements-agent-release.txt'

Motivation
Preparing the tool to accommodate another agent-related task
Review checklist

[ ] PR has a meaningful title or PR has the no-changelog label attached
[ ] Feature or bugfix has tests
[ ] Git history is clean
[ ] If PR impacts documentation, docs team has been notified or an issue has been opened on the documentation repo
[ ] If PR adds a configuration option, it has been added to the configuration file.

Additional Notes
Command names were slightly changed, this would be a breaking change in theory but we're not yet ready for 1.0

Codecov Report

Merging #2819 into master will decrease coverage by 6.74%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #2819      +/-   ##
==========================================
- Coverage    84.7%   77.95%   -6.75%
==========================================
  Files         662       24     -638
  Lines       37610      794   -36816
  Branches     4507       81    -4426
==========================================
- Hits        31857      619   -31238
+ Misses       4434      147    -4287
+ Partials     1319       28    -1291

@ofek @masci This is really good! Clean and clear senior engineer work.

Documentation is good ✅
Cleanup work is good - code isolations - simplicity ✅


{stack-hci} HTML tags are rendering as empty parameter values in reference docs

Describe the bug
Problem to solve:
HTML tags in source code are causing build warnings in MicrosoftDocs/azure-docs-cli. More importantly, customer-facing reference docs are not instantiating properly -- parameter values formatted with `<>` are missing. Here's an example:

Requested solution:
These values should be escaped with a backtick. Here's an example from az webpubsub.

Related GitHub issues:
This is the same issue as these GitHub issues.
List of HTML tag instances that need update:

File name
Build error

latest/docs-ref-autogen/stack-hci/arc-setting.yml
HTML tag 'indexToRemove' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.

latest/docs-ref-autogen/stack-hci/arc-setting.yml
HTML tag 'value' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.

latest/docs-ref-autogen/stack-hci/cluster.yml
HTML tag 'indexToRemove' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.

latest/docs-ref-autogen/stack-hci/cluster.yml
HTML tag 'value' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.

Related command
az stack-hci
Errors
n/a
Issue script & Debug output
n/a
Expected behavior
n/a
Environment Summary
Azure CLI 2.62.0
Additional context
No response

Thank you for opening this issue, we will look into it.


fix: Update python 'cryptography' module version

Pip is reporting that "paramiko 2.4.1 has requirement cryptography>=1.5,
but you'll have cryptography 1.2.3 which is incompatible." The latest
'cryptography' version requires 'pyOpenSSL==17.5.0'.

I'm not certain this is necessary. Is anybody else seeing a pip error during 'scripts/install.sh'?


[SPARK-27800][SQL][DOC] Fix wrong answer of example for BitwiseXor

What changes were proposed in this pull request?
Fix example for bitwise xor function. 3 ^ 5 should be 6 rather than 2.

See https://spark.apache.org/docs/latest/api/sql/index.html#_14

How was this patch tested?
manual tests

Can one of the admins verify this patch?

Can one of the admins verify this patch?

Can one of the admins verify this patch?

ok to test

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/10917/
Test PASSed.

Test build #105663 has started for PR 24669 at commit 82e6528.

This is a documentation change and I verified manually.
spark-sql> DESCRIBE FUNCTION EXTENDED ^;
Function: ^
Class: org.apache.spark.sql.catalyst.expressions.BitwiseXor
Usage: expr1 ^ expr2 - Returns the result of bitwise exclusive OR of `expr1` and `expr2`.
Extended Usage:
    Examples:
      > SELECT 3 ^ 5;
       6

Merged to master/2.4/2.3.

Test build #105663 has finished for PR 24669 at commit 82e6528.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/105663/
Test FAILed.

It seems the related unit test should be fixed. Since this PR been closed, is it any way to append that commit to current PR?
https://github.com/alex-lx/spark/commit/4dc990faa9bd88bf29193ec7a0f43974bbce52de

Oops. My bad. I tested with only spark-sql environment. Thanks. I'll fix that as a follow-up.

https://github.com/apache/spark/pull/24674 is made.


[Connector] Search option for connector parameters

Description:
$subject
To improve UX when there are large set of parameters we need to provide option to search connector parameters.

Related: https://github.com/wso2/devstudio-tooling-ei/issues/929

Fixed with https://github.com/wso2/devstudio-tooling-esb/pull/1340

Fixed with https://github.com/wso2/devstudio-tooling-esb/pull/1340


Unhandled exception in Paho _thread_main leaves the device client in a falsely 'connected' state

Context

OS and version used: Debian GNU/Linux 11 (bullseye) (actually python:3.10-slim docker image)
Python version: Python 3.10.4
pip version: pip 22.0.4
list of installed packages:

Package             Version
------------------- ---------
azure-iot-device    2.11.0
certifi             2021.10.8
charset-normalizer  2.0.12
click               8.1.1
croniter            1.3.4
deprecation         2.1.0
idna                3.3
iotclient           0.6.0
janus               1.0.0
netifaces           0.11.0
packaging           21.3
paho-mqtt           1.6.1
peewee              3.14.10
pip                 22.0.4
pydantic            1.9.0
pyparsing           3.0.7
PySocks             1.7.1
python-dateutil     2.8.2
PyYAML              6.0
pyzmq               22.3.0
requests            2.27.1
requests-unixsocket 0.3.0
setuptools          58.1.0
six                 1.16.0
typing_extensions   4.1.1
urllib3             1.26.9
uvloop              0.16.0
wheel               0.37.1

Description of the issue
I have a device that was up and running for a couple of days until at one point where it permanently lost connectivity to IoT Hub. By digging through my logs I identified that this started happening after a thread, likely started by Paho, crashed due to an unhandled ssl.SSLEOFError. The device client did not seem to react to it and ended up behaving as if it was connected but not actually sending any messages through. This is the first time that I see this error, I would suspect it's very rare. Connectivity did not recover until I manually restarted the application.
I see a maybe relevant/related issue in the Paho tracker here: https://github.com/eclipse/paho.mqtt.python/issues/637.
Code sample exhibiting the issue
I don't know how to reproduce this explicitly or in what conditions this happens.
Console log of the issue
[2022-04-08 12:19:45,554] INFO:7:azure.iot.device.iothub.aio.async_clients: Sending method response to Hub...
[2022-04-08 12:19:45,556] INFO:7:azure.iot.device.common.mqtt_transport: publishing on $iothub/methods/res/200/?$rid=1
[2022-04-08 12:19:45,624] INFO:7:azure.iot.device.iothub.aio.async_clients: Sending method response to Hub...
[2022-04-08 12:19:45,624] INFO:7:azure.iot.device.common.mqtt_transport: disconnected with result code: 7
[2022-04-08 12:19:45,626] INFO:7:azure.iot.device.common.mqtt_transport: Forcing paho disconnect to prevent it from automatically reconnecting
[2022-04-08 12:19:45,626] INFO:7:azure.iot.device.common.mqtt_transport: publishing on $iothub/methods/res/200/?$rid=2
[2022-04-08 12:19:45,627] INFO:7:azure.iot.device.common.pipeline.pipeline_stages_mqtt: MQTTTransportStage: _on_mqtt_disconnect called: The connection was lost.
[2022-04-08 12:19:45,628] INFO:7:azure.iot.device.common.async_adapter: Callback completed with error The client is not currently connected.
[2022-04-08 12:19:45,629] INFO:7:azure.iot.device.common.async_adapter: ['azure.iot.device.common.transport_exceptions.NoConnectionError: The client is not currently connected.\n']
[2022-04-08 12:19:45,630] WARNING:7:IoTMessageGatewayMux: Ignoring raised unhandled exception while sending data through <AzureIoTHubConnectionAdapter object at 0x7f8cf9966b90>

<redacted>

Traceback (most recent call last):
  File "/opt/venv/lib/python3.10/site-packages/iotclient/services/connectivity/connection/iothub.py", line 204, in send_method_response
    await self._device_client.send_method_response(azure_response)
  File "/opt/venv/lib/python3.10/site-packages/azure/iot/device/aio/patch_documentation.py", line 66, in send_method_response
    return await super(IoTHubDeviceClient, self).send_method_response(method_response)
  File "/opt/venv/lib/python3.10/site-packages/azure/iot/device/iothub/aio/async_clients.py", line 418, in send_method_response
    await handle_result(callback)
  File "/opt/venv/lib/python3.10/site-packages/azure/iot/device/iothub/aio/async_clients.py", line 39, in handle_result
    raise exceptions.NoConnectionError("Client is not connected to IoTHub") from e
azure.iot.device.exceptions.NoConnectionError: Client is not connected to IoTHub
[2022-04-08 12:19:45,630] INFO:7:azure.iot.device.common.pipeline.pipeline_stages_mqtt: MQTTTransportStage: Unexpected disconnect (no pending connection op)
[2022-04-08 12:19:45,630] INFO:7:azure.iot.device.iothub.abstract_clients: Connection State - Disconnected
[2022-04-08 12:19:45,632] INFO:7:azure.iot.device.iothub.abstract_clients: Cleared all pending method requests due to disconnect
[2022-04-08 12:19:45,632] ERROR:7:azure.iot.device.common.handle_exceptions: Exception caught in background thread.  Unable to handle.
[2022-04-08 12:19:45,632] ERROR:7:azure.iot.device.common.handle_exceptions: ['azure.iot.device.common.transport_exceptions.ConnectionDroppedError: Unexpected disconnection\n']

[2022-04-08 12:19:45,634] INFO:7:AzureIoTHubConnectionAdapter: Connection lost!
[2022-04-08 12:19:45,634] INFO:7:AzureIoTHubConnectionAdapter: Attempting to connect to IoT Hub..
[2022-04-08 12:19:45,634] INFO:7:azure.iot.device.iothub.aio.async_clients: Connecting to Hub...
[2022-04-08 12:19:45,636] INFO:7:azure.iot.device.common.mqtt_transport: Connect using port 8883 (TCP)
[2022-04-08 12:19:49,552] INFO:7:azure.iot.device.common.mqtt_transport: connected with result code: 0
[2022-04-08 12:19:49,555] INFO:7:azure.iot.device.common.pipeline.pipeline_stages_mqtt: _on_mqtt_connected called
[2022-04-08 12:19:49,557] INFO:7:azure.iot.device.iothub.abstract_clients: Connection State - Connected
[2022-04-08 12:19:49,564] INFO:7:azure.iot.device.iothub.aio.async_clients: Successfully connected to Hub
[2022-04-08 12:19:49,564] INFO:7:AzureIoTHubConnectionAdapter: Connection established!

[2022-04-08 12:19:49,569] INFO:7:azure.iot.device.iothub.aio.async_clients: Sending message to Hub...
[2022-04-08 12:19:49,570] INFO:7:azure.iot.device.iothub.aio.async_clients: Sending message to Hub...
[2022-04-08 12:19:49,571] INFO:7:azure.iot.device.common.mqtt_transport: publishing on <redacted>
[2022-04-08 12:19:49,571] INFO:7:azure.iot.device.common.mqtt_transport: message received on $iothub/methods/POST/<redacted>/?$rid=1
[2022-04-08 12:19:49,573] INFO:7:azure.iot.device.common.mqtt_transport: publishing on <redacted>
[2022-04-08 12:19:49,583] INFO:7:azure.iot.device.iothub.aio.async_clients: Received method request
[2022-04-08 12:19:49,587] INFO:7:azure.iot.device.iothub.aio.async_clients: Waiting for method request...
[2022-04-08 12:19:49,593] INFO:7:azure.iot.device.common.mqtt_transport: message received on $iothub/methods/POST/<redacted>/?$rid=2
Exception in thread Thread-17221 (_thread_main):
Traceback (most recent call last):
  File "/usr/local/lib/python3.10/threading.py", line 1009, in _bootstrap_inner
    self.run()
  File "/usr/local/lib/python3.10/threading.py", line 946, in run
    self._target(*self._args, **self._kwargs)
  File "/opt/venv/lib/python3.10/site-packages/paho/mqtt/client.py", line 3591, in _thread_main
    self.loop_forever(retry_first_connection=True)
  File "/opt/venv/lib/python3.10/site-packages/paho/mqtt/client.py", line 1756, in loop_forever
    rc = self._loop(timeout)
  File "/opt/venv/lib/python3.10/site-packages/paho/mqtt/client.py", line 1181, in _loop
    rc = self.loop_write()
  File "/opt/venv/lib/python3.10/site-packages/paho/mqtt/client.py", line 1577, in loop_write
    rc = self._packet_write()
  File "/opt/venv/lib/python3.10/site-packages/paho/mqtt/client.py", line 2464, in _packet_write
    write_length = self._sock_send(
  File "/opt/venv/lib/python3.10/site-packages/paho/mqtt/client.py", line 649, in _sock_send
    return self._sock.send(buf)
  File "/usr/local/lib/python3.10/ssl.py", line 1205, in send
    return self._sslobj.write(data)
ssl.SSLEOFError: EOF occurred in violation of protocol (_ssl.c:2396)
[2022-04-08 12:19:49,709] INFO:7:azure.iot.device.iothub.aio.async_clients: Received method request
[2022-04-08 12:19:49,712] INFO:7:azure.iot.device.iothub.aio.async_clients: Waiting for method request...
[2022-04-08 12:19:51,504] INFO:7:azure.iot.device.iothub.aio.async_clients: Sending method response to Hub...
[2022-04-08 12:19:51,507] INFO:7:azure.iot.device.common.mqtt_transport: publishing on $iothub/methods/res/200/?$rid=1
[2022-04-08 12:19:51,591] INFO:7:azure.iot.device.iothub.aio.async_clients: Sending method response to Hub...
[2022-04-08 12:19:51,593] INFO:7:azure.iot.device.common.mqtt_transport: publishing on $iothub/methods/res/200/?$rid=2

<redacted, nothing interesting>

[2022-04-08 12:20:14,721] INFO:7:azure.iot.device.iothub.aio.async_clients: Sending message to Hub...
[2022-04-08 12:20:14,723] INFO:7:azure.iot.device.common.mqtt_transport: publishing on <redacted>
[2022-04-08 12:20:19,572] INFO:7:azure.iot.device.iothub.aio.async_clients: Sending message to Hub...
[2022-04-08 12:20:19,573] INFO:7:azure.iot.device.common.mqtt_transport: publishing on <redacted>
[2022-04-08 12:20:44,745] INFO:7:azure.iot.device.iothub.aio.async_clients: Sending message to Hub...
[2022-04-08 12:20:44,746] INFO:7:azure.iot.device.common.mqtt_transport: publishing on <redacted>

@zopp
Thanks for bringing this to our attention. I suspect you are correct and that this is a bug in the Paho library. We'll look into it.

@zoopp
Looking into this further, it suggests there's something going on with your SSL configuration that might be the issue.

What type of authentication are you using with your IoTHub Client? Are you using any additional features? (cipher suites, proxy, etc.)

Does your device support TLS v 1.2?

Hi @cartertinney, I don't believe that this is the case. The device does support TLS 1.2 and I'm not using any additional features. Right now I default to using the following options when creating the device client:
IoTHubDeviceClient.create_from_connection_string(
        connection_string,
        keep_alive=_CONNECTION_KEEPALIVE_INTERVAL.total_seconds(),
        auto_connect=True,
        connection_retry=True,
        connection_retry_interval=_CONNECTION_RETRY_BACKOFF.total_seconds(),
    )
)

The environment in which I run the application is based on the official python:3.10-slim container image with very little modifications apart from installing my app in a venv.
Like I said in the opening message, I suspect that this error, while problematic1, it is very rare. So far I've seen only one instance of it and I've been running close to 700 application instances 24/7.

1: there's no indication that something is wrong so apart from periodically forcing a reconnection I don't see a better way to handle/workaround it.

Just a small update: over time I came across multiple instances of this error and looking back through my commit history I have seen that only just "recently" I have updated from v2.10.0 to v2.11.0. I've reverted back to v2.10.0 a couple of days ago and so far I did not see this issue anymore.

@zoopp This is an interesting data point - let us know if that changes. I can't think of anything that changed between 2.10 and 2.11 that would result in this behavior, but if that's true, it's very helpful.

Ah, I unfortunately just came across this issue again with v2.10.0 so it looks like this wasn't introduced in-between 2.10 and 2.11. @cartertinney can you think of anything that I could to do to gather additional information for you for the next time I see this issue?

@zoopp
Are you connecting directly to an IoTHub? Or are you using EdgeHub (or something else) as well?

Closing due to inactivity. We are monitoring the Paho GitHub issue however.


train my data

My dataset is a csv file and the tag file is also a csv file, after training and prediction I want to get still a csv file, how can I change it in the program, thanks.

Hi,
you could try by adding and creating an ad hoc .csv file storing your predictions in a dataframe.
If you want some help, you might share your snippet code related to it, if interested.


Progress mismatch

Logs
Node 1
🕙 07:55:11 ✖  python ./examples/memstore/main.py --bootstrap --web-server=<IP_ADDRESS>:8001
DEBUG:asyncio:Using selector: KqueueSelector
INFO:root:Bootstrap a Raft Cluster
INFO:root:Initial RaftState: RaftState { hard_state: HardState { term: 0, vote: 0, commit: 0 }, conf_state: ConfState { voters: [1], learners: [], voters_outgoing: [], learners_next: [], auto_leave: false } }
raft_id: 1
 Sep 13 22:55:12.327 INFO switched to configuration, config: Configuration { voters: Configuration { incoming: Configuration { voters: {1} }, outgoing: Configuration { voters: {} } }, learners: {}, learners_next: {}, auto_leave: false }
 Sep 13 22:55:12.327 DEBG reset election timeout 0 -> 543 at 0, election_elapsed: 0, timeout: 543, prev_timeout: 0
 Sep 13 22:55:12.327 INFO became follower at term 0, term: 0
 Sep 13 22:55:12.327 INFO newRaft, peers: Configuration { incoming: Configuration { voters: {1} }, outgoing: Configuration { voters: {} } }, last term: 0, last index: 0, applied: 0, commit: 0, term: 0
 Sep 13 22:55:12.327 INFO RawNode created with id 1., id: 1
 Sep 13 22:55:12.327 DEBG reset election timeout 543 -> 589 at 0, election_elapsed: 0, timeout: 589, prev_timeout: 543
 Sep 13 22:55:12.327 INFO became candidate at term 1, term: 1
 Sep 13 22:55:12.327 DEBG reset election timeout 589 -> 756 at 0, election_elapsed: 0, timeout: 756, prev_timeout: 589
 Sep 13 22:55:12.327 INFO became leader at term 1, term: 1
DEBUG:grpc._cython.cygrpc:Using AsyncIOEngine.POLLER as I/O engine
INFO:root:Start listening gRPC requests on "<IP_ADDRESS>:60061"...
 Sep 13 22:55:12.433 DEBG persisted index 1
 Sep 13 22:55:12.433 DEBG committing index 1, index: 1
INFO:root:Entries [1, 2) requested
INFO:root:Reserved peer id 2.
 Sep 13 22:55:16.081 DEBG persisted index 2
 Sep 13 22:55:16.081 DEBG committing index 2, index: 2
INFO:root:Entries [2, 3) requested
INFO:root:Node '<IP_ADDRESS>:60062 (node id: 2)' added to the cluster.
 Sep 13 22:55:16.082 INFO switched to configuration, config: Configuration { voters: Configuration { incoming: Configuration { voters: {1, 2} }, outgoing: Configuration { voters: {} } }, learners: {}, learners_next: {}, auto_leave: false }
INFO:root:Entries [2, 3) requested
 Sep 13 22:55:16.386 DEBG Sending from 1 to 2, msg: Message { msg_type: MsgHeartbeat, to: 2, from: 0, term: 0, log_term: 0, index: 0, entries: [], commit: 0, commit_term: 0, snapshot: Snapshot { data: "None", metadata: None }, request_snapshot: 0, reject: false, reject_hint: 0, context: "None", deprecated_priority: 0, priority: 0 }, to: 2, from: 1
DEBUG:root:Node 1 Received Raft message from the "node 2"
INFO:root:Entries [2, 3) requested
 Sep 13 22:55:16.398 DEBG Sending from 1 to 2, msg: Message { msg_type: MsgAppend, to: 2, from: 0, term: 0, log_term: 1, index: 1, entries: [], commit: 2, commit_term: 0, snapshot: Snapshot { data: "None", metadata: None }, request_snapshot: 0, reject: false, reject_hint: 0, context: "None", deprecated_priority: 0, priority: 0 }, to: 2, from: 1
DEBUG:root:Node 1 Received Raft message from the "node 2"
 Sep 13 22:55:16.404 DEBG received msgAppend rejection, index: 1, from: 2, reject_hint_term: 0, reject_hint_index: 1
 Sep 13 22:55:16.404 DEBG decreased progress of 2, progress: Progress { matched: 0, next_idx: 1, state: Probe, paused: false, pending_snapshot: 0, pending_request_snapshot: 0, recent_active: true, ins: Inflights { start: 0, count: 0, buffer: [], cap: 256, incoming_cap: None }, commit_group_id: 0, committed_index: 0 }
INFO:root:Entries [1, 3) requested
 Sep 13 22:55:16.405 DEBG [firstindex: 1, commit: 2] sent snapshot[index: 2, term: 1] to 2, progress: Progress { matched: 0, next_idx: 1, state: Probe, paused: false, pending_snapshot: 0, pending_request_snapshot: 0, recent_active: true, ins: Inflights { start: 0, count: 0, buffer: [], cap: 256, incoming_cap: None }, commit_group_id: 0, committed_index: 0 }, to: 2, snapshot_term: 1, snapshot_index: 2, committed: 2, first_index: 1
 Sep 13 22:55:16.405 DEBG paused sending replication messages to 2, progress: Progress { matched: 0, next_idx: 1, state: Snapshot, paused: false, pending_snapshot: 2, pending_request_snapshot: 0, recent_active: true, ins: Inflights { start: 0, count: 0, buffer: [], cap: 256, incoming_cap: None }, commit_group_id: 0, committed_index: 0 }
 Sep 13 22:55:16.405 DEBG Sending from 1 to 2, msg: Message { msg_type: MsgSnapshot, to: 2, from: 0, term: 0, log_term: 0, index: 0, entries: [], commit: 0, commit_term: 0, snapshot: Snapshot { data: "{}", metadata: Some(SnapshotMetadata { conf_state: Some(ConfState { voters: [1, 2], learners: [], voters_outgoing: [], learners_next: [], auto_leave: false }), index: 2, term: 1 }) }, request_snapshot: 0, reject: false, reject_hint: 0, context: "None", deprecated_priority: 0, priority: 0 }, to: 2, from: 1
DEBUG:root:Node 1 Received Raft message from the "node 2"
 Sep 13 22:55:16.413 DEBG snapshot caught up, resumed sending replication messages to 2, progress: Progress { matched: 2, next_idx: 3, state: Snapshot, paused: false, pending_snapshot: 2, pending_request_snapshot: 0, recent_active: true, ins: Inflights { start: 0, count: 0, buffer: [], cap: 256, incoming_cap: None }, commit_group_id: 0, committed_index: 0 }, from: 2
 Sep 13 22:55:16.414 DEBG Sending from 1 to 2, msg: Message { msg_type: MsgAppend, to: 2, from: 0, term: 0, log_term: 1, index: 2, entries: [], commit: 2, commit_term: 0, snapshot: Snapshot { data: "None", metadata: None }, request_snapshot: 0, reject: false, reject_hint: 0, context: "None", deprecated_priority: 0, priority: 0 }, to: 2, from: 1

Node 2
🕙 07:53:49 ✖  sleep 2; python ./examples/memstore/main.py --raft-addr=<IP_ADDRESS>:60062 --web-server=<IP_ADDRESS>:8002
DEBUG:asyncio:Using selector: KqueueSelector
INFO:root:Attempting to join the cluster through "<IP_ADDRESS>:60061"...
DEBUG:grpc._cython.cygrpc:Using AsyncIOEngine.POLLER as I/O engine
INFO:root:Obtained node id 2 from the leader node 1.
INFO:root:Running in follower mode
INFO:root:Initial RaftState: RaftState { hard_state: HardState { term: 0, vote: 0, commit: 0 }, conf_state: ConfState { voters: [], learners: [], voters_outgoing: [], learners_next: [], auto_leave: false } }
raft_id: 2
 Sep 13 22:55:16.079 INFO switched to configuration, config: Configuration { voters: Configuration { incoming: Configuration { voters: {} }, outgoing: Configuration { voters: {} } }, learners: {}, learners_next: {}, auto_leave: false }
 Sep 13 22:55:16.079 DEBG reset election timeout 0 -> 617 at 0, election_elapsed: 0, timeout: 617, prev_timeout: 0
 Sep 13 22:55:16.079 INFO became follower at term 0, term: 0
 Sep 13 22:55:16.079 INFO newRaft, peers: Configuration { incoming: Configuration { voters: {} }, outgoing: Configuration { voters: {} } }, last term: 0, last index: 2, applied: 0, commit: 0, term: 0
 Sep 13 22:55:16.079 INFO RawNode created with id 2., id: 2
DEBUG:grpc._cython.cygrpc:Using AsyncIOEngine.POLLER as I/O engine
INFO:root:Start listening gRPC requests on "<IP_ADDRESS>:60062"...
DEBUG:root:Node 2 Received Raft message from the "node 1"
 Sep 13 22:55:16.392 INFO received a message with higher term from 1, msg type: MsgHeartbeat, message_term: 1, term: 0, from: 1
 Sep 13 22:55:16.392 DEBG reset election timeout 617 -> 542 at 3, election_elapsed: 3, timeout: 542, prev_timeout: 617
 Sep 13 22:55:16.393 INFO became follower at term 1, term: 1
 Sep 13 22:55:16.393 DEBG Sending from 2 to 1, msg: Message { msg_type: MsgHeartbeatResponse, to: 1, from: 0, term: 0, log_term: 0, index: 0, entries: [], commit: 0, commit_term: 0, snapshot: Snapshot { data: "None", metadata: None }, request_snapshot: 0, reject: false, reject_hint: 0, context: "None", deprecated_priority: 0, priority: 0 }, to: 1, from: 2
DEBUG:root:Node 2 Received Raft message from the "node 1"
 Sep 13 22:55:16.401 DEBG rejected msgApp [logterm: 1, index: 1] from 1, logterm: Ok(0), index: 1, from: 1, msg_index: 1, msg_log_term: 1
 Sep 13 22:55:16.402 DEBG Sending from 2 to 1, msg: Message { msg_type: MsgAppendResponse, to: 1, from: 0, term: 0, log_term: 0, index: 1, entries: [], commit: 0, commit_term: 0, snapshot: Snapshot { data: "None", metadata: None }, request_snapshot: 0, reject: true, reject_hint: 1, context: "None", deprecated_priority: 0, priority: 0 }, to: 1, from: 2
DEBUG:root:Node 2 Received Raft message from the "node 1"
 Sep 13 22:55:16.408 INFO log [committed=0, persisted=2, applied=0, unstable.offset=3, unstable.entries.len()=0] starts to restore snapshot [index: 2, term: 1], snapshot_term: 1, snapshot_index: 2, log: committed=0, persisted=2, applied=0, unstable.offset=3, unstable.entries.len()=0
 Sep 13 22:55:16.409 INFO switched to configuration, config: Configuration { voters: Configuration { incoming: Configuration { voters: {1, 2} }, outgoing: Configuration { voters: {} } }, learners: {}, learners_next: {}, auto_leave: false }
 Sep 13 22:55:16.409 INFO restored snapshot, snapshot_term: 1, snapshot_index: 2, last_term: 1, last_index: 2, commit: 2
 Sep 13 22:55:16.409 INFO [commit: 2, term: 1] restored snapshot [index: 2, term: 1], snapshot_term: 1, snapshot_index: 2, commit: 2, term: 1
 Sep 13 22:55:16.409 DEBG Sending from 2 to 1, msg: Message { msg_type: MsgAppendResponse, to: 1, from: 0, term: 0, log_term: 0, index: 2, entries: [], commit: 0, commit_term: 0, snapshot: Snapshot { data: "None", metadata: None }, request_snapshot: 0, reject: false, reject_hint: 0, context: "None", deprecated_priority: 0, priority: 0 }, to: 1, from: 2
 Sep 13 22:55:16.411 DEBG snapshot's persisted index 2
DEBUG:root:Node 2 Received Raft message from the "node 1"
 Sep 13 22:55:16.416 DEBG Sending from 2 to 1, msg: Message { msg_type: MsgAppendResponse, to: 1, from: 0, term: 0, log_term: 0, index: 2, entries: [], commit: 2, commit_term: 0, snapshot: Snapshot { data: "None", metadata: None }, request_snapshot: 0, reject: false, reject_hint: 0, context: "None", deprecated_priority: 0, priority: 0 }, to: 1, from: 2

Progress
Node 1
🕙 07:39:58 ❯ curl -XGET http://localhost:8001/progress
['Progress { matched: 2, next_idx: 3, state: Replicate, paused: false, pending_snapshot: 0, pending_request_snapshot: 0, recent_active: false, ins: Inflights { start: 0, count: 0, buffer: [], cap: 256, incoming_cap: None }, commit_group_id: 0, committed_index: 2 }', 'Progress { matched: 2, next_idx: 3, state: Probe, paused: false, pending_snapshot: 0, pending_request_snapshot: 0, recent_active: true, ins: Inflights { start: 0, count: 0, buffer: [], cap: 256, incoming_cap: None }, commit_group_id: 0, committed_index: 2 }']⏎

Node 2
raftify  🍣 main [$!?] via 🐳 desktop-linux 🐍 v3.11.4
🕙 07:42:43 ❯ curl -XGET http://localhost:8002/progress
['Progress { matched: 0, next_idx: 2, state: Probe, paused: false, pending_snapshot: 0, pending_request_snapshot: 0, recent_active: true, ins: Inflights { start: 0, count: 0, buffer: [], cap: 256, incoming_cap: None }, commit_group_id: 0, committed_index: 0 }', 'Progress { matched: 1, next_idx: 2, state: Probe, paused: false, pending_snapshot: 0, pending_request_snapshot: 0, recent_active: true, ins: Inflights { start: 0, count: 0, buffer: [], cap: 256, incoming_cap: None }, commit_group_id: 0, committed_index: 0 }']⏎

Issue
While data replication appears to be occurring normally, upon investigating the progress of each node, it was discovered that the ProgressTracker is not functioning correctly.
According to the logs below, the MsgAppend that occurred after the log joined was rejected. This seems to be the reason why the first progress of the second node has a matched value of 0. The matched value for the second progress of the second node is 1, because it restored the snapshot sent from the leader. Although the leader node believes the snapshot was correctly restored, in reality, the second progress.matched of the second node is 1.
I have confirmed that the issue of the ProgressTracker not functioning correctly also occurs in riteraft. The rejection of the first MsgAppend might be because it was received before the snapshot was restored. However, even after the snapshot was restored, the matched value is not consistent with the leader node.

The initially rejected MsgAppend was processed again later, so I think there's no issue with the log itself.
The issue is that the Progress of the two nodes still does not match.

I have observed that the ProgressTracker is updated only within the handle_append_response. Hence, this implies that it is intentionally updated only in the step_leader.


Feature Request: Provide ability to switch between --config flags

By default, we use gcc to build our C++ code, but, we also enforce that our code compiles and passes tests with clang.  To use clang, we use the flag --config=clang-5.0.  Currently, pressing CTRL+F9 in CLion will cause bazel to build using gcc.  In order to build with clang, I've defined a run configuration that has flags identical to the ones used by the default build, plus the --config flag.
This works, but, it doesn't scale great.  It means that for each bazel command I want to define (i.e. I have a "test all" command), I need to make a copy of that for each --config that we support.  Ideally, there would be a drop down that would let me choose between any configs that our build system may support.  It would then apply that config with CTRL+F9 or with any Run Configuration.
I expect that this is super low priority and am not counting on it being implemented any time soon, but, still figured I would request.  Thanks.

Hi there! We're doing a clean up of old issues and will be closing this one. Please reopen if you’d like to discuss anything further. We’ll respond as soon as we have the bandwidth/resources to do so.


[FLINK-20767][table planner] Support filter push down on nested fields

What is the purpose of the change
Support filter push down on nested fields
For example:
SELECT * FROM users WHERE user.age > 18
In the above SQL, user.age > 18 filter can be pushed to table source to avoid scanning records that don't match the predicate. This is especially useful in analytics with columnar formats as well as in JDBC datasources.
Brief change log

Introduce a new ResolvedExpression called NestedFieldReferenceExpression to handle filters on nested fields
Changes to RexNodeToExpressionConverter and ExpressionConverter to convert RexFieldAccess <=> NestedFieldReferenceExpression and vice versa.

Verifying this change
Added unit tests in PushFilterIntoTableSourceScanRuleTest
Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): (yes / no)
The public API, i.e., is any changed class annotated with @Public(Evolving): (yes / no)
The serializers: (yes / no)
The runtime per-record code paths (performance sensitive): (yes / no)
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Kubernetes/Yarn, ZooKeeper: (yes / no)
The S3 file system connector: (yes / no)

Documentation

Does this pull request introduce a new feature? (yes / no)
If yes, how is the feature documented? (not applicable / docs / JavaDocs / not documented)

@flinkbot run azure

@wuchong @swuferhong @JingsongLi @becketqin please review

Also tagging @slinkydeveloper

@becketqin @swuferhong Addressed review comments mainly adding ITCases.

@venkata91 Thanks for your contribution, please use git rebase instead of git merge. I can't get your all commits correctly when pull your pr to local.

@lsyldliu Do you want me to fix it?

@venkata91 Thanks for your contribution, please use git rebase instead of git merge.

I used to use rebase before. But with rebase the commit ids changes and therefore it is hard to only see the requested changes which is why I changed to merge instead of rebase. See here, started doing it after this comment.

@venkata91 Thanks for your contribution, please use git rebase instead of git merge. I can't get your all commits correctly when pull your pr to local.

@lsyldliu Do you want me to fix it?

nvm, fixed it as requested.

@swuferhong @becketqin @lsyldliu Gentle ping for reviews.

Merged to master: 5be4688e8b8a055b9e8891c265f6f354083d630f


Only first group of node types is displayed in Cheat Sheet when using firefox

When using firefox browser, the Cheat Sheet only display first group of node types. In chrome web browser it works fine.
Tested with soletta-dev-app beta17

I'm using Firefox 45.0 and it seems to be working fine

I'm checking it against our online version (not beta17) - http://solettaproject.github.io/docs/nodetypes/

The online version is working fine here too (using firefox 45.0.1).
Tested with dev-app on master and it is also failing.

Yes I can confirm this bug.
When looking in the console errors the firefox points to me for this:
https://github.com/desandro/get-size/#firefox-hidden-iframe-bug
It is a conflict between angularjs and firefox. The angular uses the "display: none".
I will go through this bug

@bdilly, @otaviobp proposed fix here: https://github.com/solettaproject/soletta-dev-app/pull/100
Can you guys test/review it ?

lgtm. Tested and working fine.

ops, commented in wrong place

Patch merged and issue resolved. Thanks!


CRA TypeScript template "cannot find name "

Describe the bug
I'm having an issue in VSCode using the out-of-the-box create-react-app my-app --template typescript project not recognizing any element. I constantly get the error cannot find name xxx with 'xxx' being whatever the HTML element I'm using in the JSX.
What's interesting is that the project will run initally with zero edits. As soon as I actually go into App.tsx and change anything or just save it breaks.
Did you try recovering your dependencies?
I ensured to attempt recovering dependencies, no effect on errors.
yarn --version
1.22.4

Which terms did you search for in User Guide?
'typescript 2304' / 'cannot find name' / 'not recognizing html elements' + many shorter combinations of these phrases.
Environment
Environment Info:
current version of create-react-app: 3.4.1
running from /Users/nickray/.config/yarn/global/node_modules/create-react-app
System:
OS: macOS 10.15.6
CPU: (4) x64 Intel(R) Core(TM) i7-7660U CPU @ 2.50GHz
Binaries:
Node: 14.6.0 - /usr/local/bin/node
Yarn: 1.22.4 - /usr/local/bin/yarn
npm: 6.14.7 - /usr/local/bin/npm
Browsers:
Chrome: 86.0.4240.75
Firefox: Not Found
Safari: 14.0
npmPackages:
react: ^16.13.1 => 16.13.1
react-dom: ^16.13.1 => 16.13.1
react-scripts: 3.4.3 => 3.4.3
npmGlobalPackages:
create-react-app: 3.4.1
NOTE: I'm actually using Firefox Developer Edition 82.0b7 (64-bit)
Code Editor: VSCode
Steps to reproduce

Create new React App using TypeScript template -> create-react-app my-app --template typescript
Run yarn start or npm start to see the project works initially
Open VSCode (or your text editor), open App.tsx, change anything at all, and save.

Expected behavior
I expected to create a the very simple example found here in the TypeScript-Handbook basic tutorial. I didn't even open App.tsx initially and started by creating a new, very basic component only to find this error.
Actual behavior
I created a new react-app using the TypeScript template and was unable to make any basic changes without causing the 'cannot find name xxx' errors.
src/components/Hello.tsx

src/App.tsx

I didn't bother importing Hello into App since it wouldn't work with the existing errors so I'm aware that I didn't do that.
Reproducible demo
Link to Project:
https://github.com/STLnick/ts-trial
Just clone, yarn or npm i and yarn start or npm start. Open VSCode and view App.tsx or Hello.tsx to see errors.
The only thing that I edited from the project given by create-react-app my-app --template typescript is adding a .eslintrc.json file and eslint dev-dependencies. I spent hours looking up this issue and trying things. Adding linting was the only one that actually changed the project structure at all.
You can absolutely look at my code link and it would be just the same as if you ran CRA with the TypeScript template.

I solved this using the following command.
npm uninstall -g create-react-app
npm cache clean --force
then
npx create-react-app project_name --template all
Thanks for this! Worked for me too.


[terra-application-layout] add onBlur handler

Summary

There's a need to track when sidebar navigation menu get out of focus. I'm proposing adding the blur handler that will accept the callback from utilityConfig
What was changed:
New property onBlur added to utilityConfig
Added new handler to _ApplicationMenu.jsx with the default logic to check if menu is still in focus
Testing

This change was tested using:

[ ] WDIO
[ ] Jest
[ ] Visual testing (please attach a screenshot or recording)
[ ] Other (please describe below)
[ ] No tests are needed

Reviews
In addition to engineering reviews, this PR needs:

[ ] UX review
[ ] Accessibility review
[ ] Functional review

Additional Details

This PR resolves:
UXPLATFORM-XXXX

Thank you for contributing to Terra.
@cerner/terra

What prompted this change?


feat: Added multiline functionality

Hi,
Hope you're doing well.
There was this requirement pertaining to having multi-line feedback texts in Streamlit-feedback. So I went ahead and made it possible as best as I could. I have replaced the InputField with a TextField to enable the textbox to be scrollable. Also, I have made sure to preserve the previous one-line textbox and ensure that this feature adds value to the current structure, not modify it.
Hope it adds some value to this already awesome package!

Hello @parsa-asgari
First thanks for this contrib, it's awesome!
To make it simpler for users who want to use this, I see there being a single parameter. Something like this:
def streamlit_feedback(multiline_text_length=None):
    """
    multiline_text_length: Optional[int]
        If specified, a multiline text box will be configured with this as a maximum number of characters.
    """

Also, to reduce code complexity, could we use an if statement to treat this behaviour directly in ThumbsWithQualiFeedback and FacesWithQualiFeedback?
Many thanks!

Sure!
I'm glad that you have found the contribution valuable.
To be honest, I decided not to change your code due to the fact that I'm not fluent in JS or React. And about the parameter, you are indeed correct. The two parameters are redundant. Thanks for pointing out.
I'll try to incorporate your feedback into the contribution.
Big Thanks!

This would be a great feature. Being able to provide more than a single line of feedback would be awesome.

Hi,
Sorry for the late response. I've been really busy lately.
I've modified the code based on your feedback. I hope it is now best aligned with the direction of your repository.
If there is anything, please let me know.
Thanks,
Best Regards

hey @parsa-asgari
LGTM! Thanks for this 🔥


DB Retry Behavior

Don't just error on db connections. DBs lose connections, it happens. Retry periodically, with increasing intervals before finally returning an error to connect to the database.
This is also beneficial for our container compositions. If postgres does not startup in time, it will retry.

@sayplastic How does coverage decrease if the function adjusted has a unit test covering it?

@sayplastic How does coverage decrease if the function adjusted has a unit test covering it?

Test coverage is not binary, you added a logical branch to the function that the existing test does not cover.

@tiger5226, @sayplastic says you can and should merge this


Correct energy units

Describe the bug
Every smart-plug using tuya-local reports energy units as Wh, which isn't the correct unit in Homeassistant. it should report energy in kWh.
To Reproduce
add any smart plug into HA using tuya-local
Expected behavior
Report energy units in kWh.
Additional context
Add any other context about the problem here.
If the bug involves a device, then please include device diagnostics from
Settings / Devices & Services / Tuya Local (your device) / "1 device"
    "domain": "tuya_local",
    "name": "Tuya Local",
    "codeowners": [
      "@make-all"
    ],
    "config_flow": true,
    "dependencies": [],
    "documentation": "https://github.com/make-all/tuya-local",
    "integration_type": "device",
    "iot_class": "local_push",
    "issue_tracker": "https://github.com/make-all/tuya-local/issues",
    "requirements": [
      "pycryptodome~=3.17",
      "tinytuya==1.12.4"
    ],
    "version": "2022.4.1",
    "is_built_in": false
  },
  "data": {
    "name": "Energy monitoring smartplug",
    "type": "smartplugv2_energyv3",
    "device_id": "**REDACTED**",
    "local_key": "**REDACTED**",
    "host": "**REDACTED**",
    "protocol_version": 3.4,
    "api_version_set": 3.4,
    "api_version_used": 3.4,
    "api_working": true,
    "status": {},
    "cached_state": {
      "updated_at":<PHONE_NUMBER>.5008566,
      "1": true,
      "9": 0,
      "17": 2,
      "18": 0,
      "19": 0,
      "20": 2173,
      "21": 1,
      "22": 566,
      "23": 29794,
      "24": 16000,
      "25": 2610,
      "26": 0,
      "38": "memory",
      "39": false,
      "40": "on",
      "41": false,
      "42": "",
      "43": "",
      "44": ""
    },
    "pending_state": {},
    "connected": true,
    "force_dps": [
      18,
      19,
      20
    ],
    "home_assistant": {
      "name": "Energy monitoring smartplug",
      "name_by_user": null,
      "disabled": false,
      "disabled_by": null,
      "entities": [
        {
          "disabled": false,
          "disabled_by": null,
          "entity_category": null,
          "device_class": null,
          "original_device_class": "outlet",
          "icon": null,
          "unit_of_measurement": null,
          "state": {
            "entity_id": "switch.energy_monitoring_smartplug",
            "state": "on",
            "attributes": {
              "test_bit": 1,
              "fault_code": 0,
              "cycle_timer": "",
              "random_timer": "",
              "inching": "",
              "device_class": "outlet",
              "friendly_name": "Energy monitoring smartplug"
            },
            "last_changed": "2023-12-27T03:50:57.806968+00:00",
            "last_updated": "2023-12-27T03:50:57.806968+00:00"
          }
        },
        {
          "disabled": false,
          "disabled_by": null,
          "entity_category": "config",
          "device_class": null,
          "original_device_class": "switch",
          "icon": null,
          "unit_of_measurement": null,
          "state": {
            "entity_id": "switch.energy_monitoring_smartplug_overcharge_protection",
            "state": "off",
            "attributes": {
              "device_class": "switch",
              "friendly_name": "Energy monitoring smartplug Overcharge protection"
            },
            "last_changed": "2023-12-27T03:50:57.807514+00:00",
            "last_updated": "2023-12-27T03:50:57.807514+00:00"
          }
        },
        {
          "disabled": false,
          "disabled_by": null,
          "entity_category": "diagnostic",
          "device_class": null,
          "original_device_class": "problem",
          "icon": null,
          "unit_of_measurement": null,
          "state": {
            "entity_id": "binary_sensor.energy_monitoring_smartplug_error",
            "state": "off",
            "attributes": {
              "device_class": "problem",
              "friendly_name": "Energy monitoring smartplug Error"
            },
            "last_changed": "2023-12-27T03:50:57.807868+00:00",
            "last_updated": "2023-12-27T03:50:57.807868+00:00"
          }
        },
        {
          "disabled": false,
          "disabled_by": null,
          "entity_category": "config",
          "device_class": null,
          "original_device_class": null,
          "icon": null,
          "unit_of_measurement": null,
          "state": {
            "entity_id": "lock.energy_monitoring_smartplug_child_lock",
            "state": "unlocked",
            "attributes": {
              "icon": "mdi:hand-back-right-off",
              "friendly_name": "Energy monitoring smartplug Child Lock",
              "supported_features": 0
            },
            "last_changed": "2023-12-27T03:50:57.808166+00:00",
            "last_updated": "2023-12-27T03:50:57.808166+00:00"
          }
        },
        {
          "disabled": false,
          "disabled_by": null,
          "entity_category": "config",
          "device_class": null,
          "original_device_class": null,
          "icon": null,
          "unit_of_measurement": "min",
          "state": {
            "entity_id": "number.energy_monitoring_smartplug_timer",
            "state": "0.0",
            "attributes": {
              "min": 0.0,
              "max": 1440.0,
              "step": 1.0,
              "mode": "auto",
              "unit_of_measurement": "min",
              "icon": "mdi:timer",
              "friendly_name": "Energy monitoring smartplug Timer"
            },
            "last_changed": "2023-12-27T03:50:57.808611+00:00",
            "last_updated": "2023-12-27T03:50:57.808611+00:00"
          }
        },
        {
          "disabled": false,
          "disabled_by": null,
          "entity_category": "config",
          "device_class": null,
          "original_device_class": null,
          "icon": null,
          "unit_of_measurement": null,
          "state": {
            "entity_id": "select.energy_monitoring_smartplug_initial_state",
            "state": "Last State",
            "attributes": {
              "options": [
                "Last State",
                "Off",
                "On"
              ],
              "icon": "mdi:toggle-switch",
              "friendly_name": "Energy monitoring smartplug Initial state"
            },
            "last_changed": "2023-12-27T03:57:40.029963+00:00",
            "last_updated": "2023-12-27T03:57:40.029963+00:00"
          }
        },
        {
          "disabled": false,
          "disabled_by": null,
          "entity_category": "config",
          "device_class": null,
          "original_device_class": null,
          "icon": null,
          "unit_of_measurement": null,
          "state": {
            "entity_id": "select.energy_monitoring_smartplug_light_mode",
            "state": "On",
            "attributes": {
              "options": [
                "Position",
                "Off",
                "State",
                "On"
              ],
              "icon": "mdi:lightbulb",
              "friendly_name": "Energy monitoring smartplug Light mode"
            },
            "last_changed": "2023-12-27T03:50:57.809352+00:00",
            "last_updated": "2023-12-27T03:50:57.809352+00:00"
          }
        },
        {
          "disabled": false,
          "disabled_by": null,
          "entity_category": "diagnostic",
          "device_class": null,
          "original_device_class": null,
          "icon": null,
          "unit_of_measurement": "Wh",
          "state": {
            "entity_id": "sensor.energy_monitoring_smartplug_energy",
            "state": "2",
            "attributes": {
              "calibration": 2610,
              "unit_of_measurement": "Wh",
              "friendly_name": "Energy monitoring smartplug Energy"
            },
            "last_changed": "2023-12-27T03:50:57.809697+00:00",
            "last_updated": "2023-12-27T03:50:57.809697+00:00"
          }
        },
        {
          "disabled": false,
          "disabled_by": null,
          "entity_category": "diagnostic",
          "device_class": null,
          "original_device_class": "current",
          "icon": null,
          "unit_of_measurement": "mA",
          "state": {
            "entity_id": "sensor.energy_monitoring_smartplug_current",
            "state": "0",
            "attributes": {
              "state_class": "measurement",
              "calibration": 29794,
              "unit_of_measurement": "mA",
              "device_class": "current",
              "friendly_name": "Energy monitoring smartplug Current"
            },
            "last_changed": "2023-12-27T04:00:05.503492+00:00",
            "last_updated": "2023-12-27T04:00:05.503492+00:00"
          }
        },
        {
          "disabled": false,
          "disabled_by": null,
          "entity_category": "diagnostic",
          "device_class": null,
          "original_device_class": "power",
          "icon": null,
          "unit_of_measurement": "W",
          "state": {
            "entity_id": "sensor.energy_monitoring_smartplug_power",
            "state": "0.0",
            "attributes": {
              "state_class": "measurement",
              "calibration": 16000,
              "unit_of_measurement": "W",
              "device_class": "power",
              "friendly_name": "Energy monitoring smartplug Power"
            },
            "last_changed": "2023-12-27T04:00:05.504211+00:00",
            "last_updated": "2023-12-27T04:00:05.504211+00:00"
          }
        },
        {
          "disabled": false,
          "disabled_by": null,
          "entity_category": "diagnostic",
          "device_class": null,
          "original_device_class": "voltage",
          "icon": null,
          "unit_of_measurement": "V",
          "state": {
            "entity_id": "sensor.energy_monitoring_smartplug_voltage",
            "state": "217.3",
            "attributes": {
              "state_class": "measurement",
              "calibration": 566,
              "unit_of_measurement": "V",
              "device_class": "voltage",
              "friendly_name": "Energy monitoring smartplug Voltage"
            },
            "last_changed": "2023-12-27T03:59:54.478757+00:00",
            "last_updated": "2023-12-27T03:59:54.478757+00:00"
          }
        }
      ]
    }
  }
}

Please check if there are messages from Tuya Local in the Home
Assistant log (Settings / System / Logs), and include those too.
If applicable, add screenshots to help explain your problem.

Can you point me to where in the documentation "correct units" are defined?

it will make it consist of standard billing units, https://en.wikipedia.org/wiki/Kilowatt-hour.

HA energy dasboard doesn't accept it

That is not because of the units. It is because that sensor is not suitable for use due to reesetting too frquently, as I said in my earlier comment.

That is not because of the units. It is because that sensor is not suitable for use due to reesetting too frquently, as I said in my earlier comment.

so this sensor should be ignored instead a new sensor should use Riemann integration and calculate it based on device usage, e.g. using the left method for devices which gives a constant power value over a long period.


CTC build failed for speech_recognition example

Environment info
Operating System: Ubuntu 14.04
Compiler:
Package used (Python/R/Scala/Julia): python
MXNet version: 0.10.0
Or if installed from source: git clone https://github.com/dmlc/mxnet.git ~/mxnet --recursive
Error Message:
There are 3 Errors with different build schedules:
git clone with MxNet, modify the config.mk with
USE_BLAS = openblas
USE_CUDA = 1
USE_CUDA_PATH = /usr/local/cuda
USE_CUDNN = 1
three different modifications as follows, and then run the example of speech_recognition:
1.  without MXNET_PLUGINS += plugin/warpctc/warpctc.mk
net = mx.sym.WarpCTC(data=net, label=label, label_length=num_label, input_length=seq_len)
AttributeError: 'module' object has no attribute 'WarpCTC'
2. with MXNET_PLUGINS += plugin/warpctc/warpctc.mk
terminate called after throwing an instance of 'std::runtime_error'
what(): Error: compute_ctc_loss, stat = cuda memcpy or memset failed
3. with MXNET_PLUGINS += plugin/warpctc/warpctc.mk, and delete all the new ctc_loss files (the folder ctc_include, ctc_loss.cc, ctc_loss.cu and ctc_loss-inl.h) as mentioned in the previous issue https://github.com/dmlc/mxnet/issues/6121
terminate called after throwing an instance of 'std::runtime_error'
what():  Error: compute_ctc_loss, stat = execution failed
Aborted (core dumped)
Minimum reproducible example
As mentioned above, modify the config.mk in different ways, then run the example.
Steps to reproduce
after make the mxnet, and python installed, run the example of speech_recognition with the deepspeech.cfg
python main.py --configfile deepspeech.cfg
From the three different builds and errors, it shows that the mxnet need the wrap-ctc plugin, and the problem is still the ctc of mxnet in the src\operator\contrib folder?
@piiswrong, Would you please help me to dig into this issue? How can I fix it?
Many thanks
Xin.q.

@sbodenstein Any updates on fixing this?

@piiswrong: I tried one or two things to fix it (which didn't work), and then ran out of time for a release.
I will try and make some time this Saturday to return to this.

same issue with warp-ctc's lstm_ocr.py and toy_ctc.py @sbodenstein

@sbodenstein Another approach is to change warpctc implementation to be the same with the new ctc_loss, while keeping the original interface

@piiswrong: that would be easy to do. I guess the advantage of having a warpctc plugin that does not rely on our new CTC layer, is that upstream Warp CTC changes are immediately useable.
What do you think?

any update for this problem? @sbodenstein

is there any update for this issue? @piiswrong, @sbodenstein
and there is a question may be not related to mxnet.
I've built the deep speech2 architecture in keras, tensorflow, and mxnet, but any of them achieves a good performance.
The architecture is believed to be right. So how can I optimize the neural network to get the performance in  papers?
Many thanks

@sbodenstein I think making it work is enough for now. Let's use the new ctc layer.

@piiswrong: ok, I'll add it.

@xinq2016 What dataset did you use? You need hundreds of thousands of hours of training data to get baidu's numbers.

@sbodenstein Any updates? I just noticed that there is a removeblank step in warpctc but not in the new ctcloss. Are the results equivalent? If not why?

@sbodenstein，
I use the librispeech for English, and my own corpus for mandarin, which has about 1,400 hours.

For English, I build the model with English character, which has 29 labels including
For Mandarin, I build the model in two ways, no  for mandarin modeling.
1). phone-level modeling with 218 labels;
2). character-level modeling with 4816 labels

Before MXNet, I used the code coming from Baidu github, coding in Keras, with 1 Conv + 3 GRU + 1 FC.
For three models, the final loss seem to be around 40 and bad CER about 40%+.
While there is some issue with the MXNet with warp-ctc, so I have no result in MXNet.
How can I optimize the RNN architecture? Is there some tips?
Many thanks

Anyone still seeing the issue (AttributeError: 'module' object has no attribute 'WarpCTC')? I have tried all possible solutions suggested in various GitHub issues. But I still see this error with speech recognition example. It seems to work fine with the ctc example.


Show Slide Preview doesn't load on startup

If the Slide Preview was open when Obsidian was closed then after Obsidian is reopened the Advanced Slides Slide Preview pane remains blank and never updates. After toggling the slide preview on and off again it works.
Note: This also affects loading a workspace that includes an Advanced Slides Slide Preview pane.

will be fixed with next version


Unsupported machine?

Model: BEKO WDB 7425 R2W

I can't easily verify if your model is supported, but the error doesn't indicate that.
A similar problem was described here: https://github.com/hbldh/bleak/issues/631
From what I understand the problem is just an unreliable connection.


fix: various issues

Follow-ups for #610

I cannot start the game on Mac 😕  The process is started, but nothing shows up. Last part in the game's log is:
13:05:06.132 [main] INFO  o.terasology.engine.TerasologyEngine - Initialization completed in 20.50sec.
13:05:08.900 [o.t.r.n.l.m.a.AdvancedGameSetupScreen-0] INFO  o.t.e.module.ModuleListDownloader - Downloading modules ..
13:05:09.057 [o.t.r.n.l.m.a.AdvancedGameSetupScreen-0] INFO  o.t.e.module.ModuleListDownloader - Parsing content ..
13:05:09.200 [o.t.r.n.l.m.a.AdvancedGameSetupScreen-0] INFO  o.t.e.module.ModuleListDownloader - Retrieved 184 entries

We have log for java start string in logs.
And which game version you using?
Before or after lwjgl?

And which game version you using?
Before or after lwjgl?

Good point - I tried with latest stable... So we actually need different kinds of Java parameters/flags for different versions... 🤔 which makes me wish for sortable version numbers even more... 🙄


WifiSettings combined endpoint

Most users try and change the wifi settings while on wifi themselves
this causes a bunch of problems when they attempt to change several
settings at different endpoints but their connection is disrupted by
each individual change.
From the users perspective only some changes get applied when they
hit save.
This commit updates the /wifi_settings endpoint to interpret the
same json objects previously posted to individual endpoints as an array
of tokens all of which are iterated over and applied as one operation

Tested and updated dashboard in https://github.com/althea-mesh/althea-dash/commit/4ac1f3bead0c20e56c64090b5d61845d1d11898c


Rebecca development

Description
I added the example "continuous beam" in the folder "examples". It's a continuous concrete beam with user input for the number of fields, span and a continuous member load. The example contains two loadcases - selfweight and continuous member load. The example uses classes from "RFEMWebServiceLibrary".
Type of change

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update

How Has This Been Tested?
Manual testing.
Test Configuration:

RFEM / RSTAB version: 6.02.0041
.Net SDK: .NET 6.0

Checklist:

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes
[ ] Any dependent changes have been merged and published in downstream modules

I just noticed that I accidentaly commited another example that I have worked on.


Memory leak while wifi is disonnected/trying to reconnect (IDFGH-6851)

Environment

Development Kit:      [none]

Module or chip used:  [ESP32-WROVER-E]

IDF version (run git describe --tags to find it):v4.3.2 (PIO version)

framework-espidf 3.40302.0 (4.3.2)

tool-cmake 3.16.4

tool-esptoolpy 1.30100.210531 (3.1.0)

tool-ninja 1.7.1

toolchain-esp32ulp 1.22851.191205 (2.28.51)

toolchain-riscv32-esp 8.4.0+2021r2-patch2

toolchain-xtensa-esp32 8.4.0+2021r2-patch2

toolchain-xtensa-esp32s2 8.4.0+2021r2-patch2

Operating System:     [Linux]

Using an IDE?: [Yes VsCode + Platformio

Power Supply:         [external 5V]

Problem Description
My code connects to wifi and regularly executes esp_client_https requests to a server.
I am testing the behavior when the wifi is unstable. So turning the wifi off waiting a bit and then turning it back on the chip seems to reconnect correctly.
After being disconnected for a while though (over night) the reconnection failed with this error:
W (133186006) wifi:m f probe req l=0

W (133186246) wifi:m f probe req l=0

W (133186486) wifi:m f probe req l=0

W (133186726) wifi:m f probe req l=0

W (133186976) wifi:m f probe req l=0

and no other output.
I've found this to be related (maybe) https://github.com/espressif/esp-idf/issues/3592#issuecomment-638029097 but I don't get the warning for failed memory allocation. I also thought that maybe this was the case so in components I enabled "stop on failed heap allocation" but the system never stopped so I am assuming no heap allocation failed at any point.
I am also using the SPIRAM and have produced memory reports.
This is the memory state when the system starts:
I (15676) time-mod: xPortGetFreeHeapSize: 4178423
I (15676) time-mod: heap_caps_get_minimum_free_size(MALLOC_CAP_8BIT|MALLOC_CAP_DMA)  64460
I (14666) time-mod: esp_get_free_internal_heap_size() 67819

And this is the memory state when the system can no longer reconnect; though it doesn't fully crash it just shows the before mentioned error repeatedly.
I (132853626) time-mod: xPortGetFreeHeapSize: 4178499
I (132853626) time-mod: heap_caps_get_minimum_free_size(MALLOC_CAP_8BIT|MALLOC_CAP_DMA)  60964
I (132853626) time-mod: esp_get_free_internal_heap_size() 61351

The available space is massive so I don't understand why any allocation should fail or why i get that kind of probe error.
I also couldn't confirm if the memory allocation error doesn'T show up for me because i have the flag turned off; even after searching through the flags I couldn't find anything relevant besides setting wifi debug log level to verbose.
Expected Behavior
To reconnect correctly no matter how long the system was disconnected
Actual Behavior
W (133186486) wifi:m f probe req l=0
Error with wifi and bluetooth not responding
I've also attached the sdk.
sdkconfig.esp-wrover-kit.txt

I have a TCP socket listening on the network interface and before it crashes it also prints out this, but i don't know how to interpret these warnings. Also there are http clients running.
W (1883841) wifi:<ba-del>idx
W (1883841) wifi:<ba-del>idx
W (1907321) wifi:<ba-add>idx:0 (ifx:0, d8:07:b6:79:e3:00), tid:0, ssn:1868, winSize:64
W (1908011) wifi:<ba-add>idx:1 (ifx:0, d8:07:b6:79:e3:00), tid:1, ssn:2442, winSize:64
W (2301451) wifi:<ba-del>idx
W (2301451) wifi:<ba-del>idx
W (2325401) wifi:<ba-add>idx:0 (ifx:0, d8:07:b6:79:e3:00), tid:1, ssn:2976, winSize:64
W (2327031) wifi:<ba-add>idx:1 (ifx:0, d8:07:b6:79:e3:00), tid:0, ssn:2146, winSize:64
W (3347861) wifi:<ba-del>idx
W (3347871) wifi:<ba-del>idx
W (3364981) wifi:<ba-add>idx:0 (ifx:0, d8:07:b6:79:e3:00), tid:1, ssn:163, winSize:64
W (3366301) wifi:<ba-add>idx:1 (ifx:0, d8:07:b6:79:e3:00), tid:0, ssn:2839, winSize:64
I (3385611) wifi:bcn_timout,ap_probe_send_start
I (3388111) wifi:ap_probe_send over, resett wifi status to disassoc
I (3388111) wifi:state: run -> init (c800)
I (3388111) wifi:pm stop, total sleep time:<PHONE_NUMBER> us /<PHONE_NUMBER> us

W (3388121) wifi:<ba-del>idx
W (3388121) wifi:<ba-del>idx
I (3388121) wifi:new:<2,0>, old:<2,1>, ap:<255,255>, sta:<2,1>, prof:1
E (3388141) TRANS_TCP: [sock=50] delayed connect error: Software caused connection abort
E (3388141) HTTP_CLIENT: Connection failed, sock < 0
W (3395641) wifi:m f probe req l=0

W (3395881) wifi:m f probe req l=0

W (3396131) wifi:m f probe req l=0

W (3396371) wifi:m f probe req l=0

W (3396611) wifi:m f probe req l=0

My error was ultimately caused by having too many tasks with too high priority.
From what I found wifi has prio 23, I had multiple tasks that were lower and on occasion they'd hold wifi up so much it would fail.
The error it incredibly uninformative though


gNOI-4.1: Software Upgrade does not wait for Supervisor Sync post reboot

Describe the bug
After the rebootDUT function, there should be some mechanism to wait for the Supervisor synchronization to complete before attempting verifyInstall(). This results in the DUT returning an empty string as the OS.Version for the standby supervisor.
As a brute-force method, I simply added a time.Sleep(5 * time.Minute) after the reboot and the test passed successfully.
To Reproduce
Steps to reproduce the behavior:

Setup gNOI server on the DUT
Run OSInstall script on dual supervisor DUT
Observe Got/Want in output where got is ""

Expected behavior
Wait for the Standby Supervisor to be up and synchronized before attempting to fetch version
Additional context
Once added, the test passed:
    osinstall_test.go:329: Transfer progress:<PHONE_NUMBER> bytes received by DUT
    osinstall_test.go:248: OS.Install supervisor image transfer complete.
    osinstall_test.go:116: OS.Activate complete.
    osinstall_test.go:214: DUT standby supervisor has valid preexisting image; skipping transfer.
    osinstall_test.go:114: OS.Activate standby supervisor complete.
    osinstall_test.go:153: Send DUT Reboot Request
    osinstall_test.go:174: DUT has not rebooted.
    osinstall_test.go:180: Waiting for reboot to complete...
    osinstall_test.go:174: DUT has not rebooted.
    osinstall_test.go:180: Waiting for reboot to complete...
    osinstall_test.go:180: Waiting for reboot to complete...
    osinstall_test.go:171: Reboot completed.
    osinstall_test.go:96: Waiting for Supervisors to Synchronize - 5 Minutes <----- t.Logf added wtih the 5 minute timer after reboot
    osinstall_test.go:277: OS.Verify complete
--- PASS: TestOSInstall (1046.85s)
PASS

cc @robshakir  @xw-g

I see that  rebootDUT already adds 10m in the waiting. If you want brutal force, maybe just add there.
I think another way (maybe better) would be continuously verifyintall, but only report failure after say (15min).
What do you think?

PR835 was merged - closing issue


Echoing flute

You have the address for what map you're in.  You should be able to get the Echoing Flute to work now.

The Echoing Flute should work correctly now.


test: add test cases for upload file

PR Details

Description

Related Issue

Motivation and Context

How Has This Been Tested

Types of changes

[ ] Docs change / refactoring / dependency upgrade
[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist

[ ] My code follows the code style of this project.
[ ] I have updated changeset
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[ ] I have read the CONTRIBUTING document.
[ ] I have added tests to cover my changes.
[ ] All new and existing tests passed.

对 PR 改动范围的描述可以更详细一点喔，改动的文件是有涉及到源码变更的，与标题不是很一致

PR Details
Description
为 BFF 上传文件增加测试用例，在使用 egg 和 koa 框架时，删除 resolveFormData 的逻辑，使用 koa-body。
Related Issue
Motivation and Context
How Has This Been Tested
Types of changes

[ ]  Docs change / refactoring / dependency upgrade
[ ]  Bug fix (non-breaking change which fixes an issue)
[ ]  New feature (non-breaking change which adds functionality)
[ ]  Breaking change (fix or feature that would cause existing functionality to change)

Checklist

[ ]  My code follows the code style of this project.
[ ]  I have updated changeset
[ ]  My change requires a change to the documentation.
[ ]  I have updated the documentation accordingly.
[ ]  I have read the CONTRIBUTING document.
[ ]  I have added tests to cover my changes.
[ ]  All new and existing tests passed.


ldap authentication broken ?

For some buggy reason my ldap admin account gets the level=0 in the mysql database at each login, hence no access to devices at all.
Running the ./scripts/auth_test.php -u <ldap_user> says the correct level = 10, which is correct.
Let me know what debug info is required to fix this one...

You should post in the community forums. This is the myLibreNMS app repo.


Token healing (under 40 LOC)

Feature request
Token healing rectifies the token boundary bias in greedy tokenization. It does this by trimming and regrowing the prompt to better align with the model's tokenizer, thus enhancing generation quality. The improvement is clearest with completion models.
Token boundary bias is a silent performance killer that doesn't seem very well known. It has clear impact on completion quality, though I'm not sure where it would fit as a exllamav2 feature.
A more thorough explanation of the problem: The Art of Prompt Design: Prompt Boundaries and Token Healing | by Scott Lundberg.
Motivation
Given a completion prompt with a partial url ending with :, the model might have seen the expected completion :// as a single token in training. However, the prompt's tail token : tells it that the next token is not //, and so it generates a wrong completion. Such errors compound in auto-regressive language models.
Your contribution
My implementation (under 40 LOC): https://github.com/Ayenem/TokenHealer/tree/main

Found out about existing impl in exllamav2.

Found out about existing impl in exllamav2.


Bundled Cable interaction with Mekanism

Minecraft version & Mod Version:
1.12.2
Cyclic-1.12.2-1.15.9
Single player or Server:
SP
Describe problem (what you were doing / what happened):
A Cyclic Bundled Cable touched a Mekanism Universal Cable (energy pipe)
Crash log (if any):
https://paste.dimdev.org/unevonetor.txt

Yep fix coming out soon, same root cause as https://github.com/PrinceOfAmber/Cyclic/issues/841

Try this fix https://minecraft.curseforge.com/projects/cyclic/files/2572232

Seems fixed, thank you!


Enhance docs with explicit example of handling params supplied via withTransformerParameter

It was non-obvious to me that the parameters supplied to the model via the withTransformerParameter would be under a "parameters" key rather than the raw key supplied in the DSL call. I think it would be helpful to have an explicit example in addition to the several request based examples.
I'm happy to raise a PR to the docs if this seems like a good idea.

I only found out about this parameters by coming across this issue


Failure in Credentials Verification

I took the checkout of the latest walt.id repo and built the images locally and ran the setup with local built images.
But whenever I try verifying the credentials, it fails
This is the last log I see in the wallet-api docker (Attached log.txt)
Is there an issue with the presentation?

log.txt

I'm seeing a similar issue but on the offer side, seems to be related to this PR.
The browser isn't reaching the the issuer-container as the host of the vc-request sting is a internal docker URL reference.

@niwim in the etc/hosts file you can add those lines to resolve the issue :
<IP_ADDRESS> host.docker.internal
<IP_ADDRESS> gateway.docker.internal

Thanks @SuperBatata, noticed that the issues were not related.
Managed to reproduce @mahtovivekUBT issue. It looks like its ebsi-related, idk much about the ebsi resolver but managed to extract this error at least.
docker-compose-verifier-api-1       | [DefaultDispatcher-worker-8] TRACE id.walt.credentials.schemes.JwsSignatureScheme - Verifying with issuer did: did:ebsi:zf39qHTXaLrr6iy3tQhT3UZ
docker-compose-verifier-api-1       | [DefaultDispatcher-worker-8] TRACE id.walt.credentials.schemes.JwsSignatureScheme - Imported key: Failure(io.ktor.network.tls.TLSException: Received alert during handshake. Level: FATAL, code: ProtocolVersion) from did: did:ebsi:zf39qHTXaLrr6iy3tQhT3UZ, public is: null

Thanks @SuperBatata  and @niwim
These are the logs from the verifier_api (After clicking on accept presentation)
verifier_api.log
I have Windows 11 OS with Docker-desktop, and I'm running the demo on Chrome browser although the behavior is same on other browsers. Please let me know if you need any more info.

@laserguy Thank you for providing the logs from the verifier-api. Could you please also provide the steps to reproduce the issue? For example, how are you running the project, and how do you issue the VC? etc..  This information will help us better understand and address the problem. Thank you!

@SuperBatata I tried with did:jwk, and the verification works with it. I tried with other did methods as well.
Except did:key and did:cheqd, other methods are working fine.
I have made a video that shows how issue can be reproduced, but it is more than 10 MB so I have uploaded it to the discord Failed Verification

@SuperBatata I had one small question, I was able to resolve the did:cheqd using Uniresolver, but I couldn't resolve the did:ebsi. Is did:ebsi not stored on the ebsi blockchain?
did:ebsi:zf39qHTXaLrr6iy3tQhT3UZ


Hi, can this be used for coverting a epub file to mobi?

Thanks

I haven't tried it, but I think it might work.
It should do everything thing that the calibre ebook-convert command does. Here are the docs: https://manual.calibre-ebook.com/generated/en/ebook-convert.html
It detects the type of the document by looking at the file suffix, so if you pass book.epub as the input and book.mobi as the output it may work.

Thank you very much. It is very helpful

Once you've created the epub, then you need the KindleGen, which should do this rather painlessly.


neon/st3: Add shuffle vector implementations

Adds SIMDE_SHUFFLE_VECTOR implementations for vst3

That's strange.  It looks like the emscripten build's error is unrelated to the code.

Yep, it was a failure to install emscripten.  I restarted the build.
I think we're at a bit over 50 builds in CI, and most (all?) require installing packages from the network, so an occasional spurious failure is fairly common.


Allow custom output directory for diagnostics collection

Signed-off-by: Andreas Neumann<EMAIL_ADDRESS>What this PR does / why we need it:
Allow kudo diagnostics collect --outputDir instance1 so we can collect multiple diagnostics in the same directory

How does this differ from #1599?

How does this differ from #1599?

It doesn't. Alena and I implemented this independently. She was trying out the diagnostic feature, I was trying to integrate it with KUDO Cassandra and we both noticed that it needs to be done

Can you and @alenkacz reconcile which one should be closed?

I've closed Alenas PR (after reconciling with her), I'm going to add her as Co-Author on this one when it's merged.


User changing the branch for an application

If a user changes the branch for an application then the wego-label that we are using to keep from creating duplicate applications is now out of date. The label is created from a hash of path, branch, and url of an application. We need to determine a way to change/validate the label when the branch is changed.

@J-Thompson12 Instead of storing a hash, can we calculate "uniqueness" by querying the cluster to see if the Application name/namespace combo already exists?


[developmnet] fix npm publish

Pull Request Test Coverage Report for Build 4e9080ae-9ed4-4346-af15-219780067103
Details

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 91.057%

Totals

Change from base Build 9b9207bd-7946-41cb-a3b5-d3865c099363:
0.0%

Covered Lines:
357

Relevant Lines:
394

💛  - Coveralls


SBOM empty file for final bucket

Use the "put trick" for the empty *.sbom.json file, similar to the *.tar.gz file

/uncc jjerger
/cc zmarano

/cc dorileo


⚠ Bofrost.lu has degraded performance

In 714e5bd, Bofrost.lu (https://www.bofrost.lu) experienced degraded performance:

HTTP code: 200
Response time: 1301 ms

Resolved: Bofrost.lu performance has improved in 580f83a after 28 minutes.


Create CyndiPipeline resources in kafka providers

Add connectNamespace to "kafka" provider in ClowdEnvironment spec which indicates the namespace that the "Kafka Connect" cluster resides in for the given ClowdEnvironment. If unset, we default to be the same namespace as 'kafka'
Add param "cyndi: " to ClowdApp spec

If kafka provider mode is "app-interface", and ClowdApp has "cyndi: true", Clowder will simply verify that a CyndiPipeline resource exists in the connectNamespace. At the moment these are being defined in app-interface here: https://gitlab.cee.redhat.com/service/app-interface/-/blob/master/data/services/insights/xjoin/deploy-cyndi.yml
If provider mode is "operator", and ClowdApp has "cyndi: true", Clowder will drop a CyndiPipeline resource into the connectNamespace that looks something like:
apiVersion: cyndi.cloud.redhat.com/v1alpha1
kind: CyndiPipeline
metadata:
  name: {ClowdApp name}
spec:
  appName: {ClowdApp name}

If provider mode is 'local', we will drop the CyndiPipeline resource into the target env namespace. For the scope of this PR, we are assuming kafka-connect is already provisioned in that namespace (Clowder is not yet creating it)
In 'app-interface' mode, it is assumed that all the configuration that cyndi-operator needs (correct CyndiPipeline content, 'cyndi' ConfigMap, and secrets for accessing respective app databases) are already present in the kafka connect namespace (because they've been provisioned via definitions in app-interface). We'll add more validations in a future PR.

Do we merge this now - or add the extra stuff @BlakeHolifield is working on into it?

Do we merge this now - or add the extra stuff @BlakeHolifield is working on into it?

Well, the plan was to add in full cyndi support over the course of several PRs. What he's working on should be able to go in as a separate piece, and even once his work goes in, there are still a couple more PRs to go after that. This PR was just the first step at adding cyndi support

Well, the plan was to add in full cyndi support over the course of several PRs. What he's working on should be able to go in as a separate piece, and even once his work goes in, there are still a couple more PRs to go after that. This PR was just the first step at adding cyndi support

Yeah I'd like to get this in and add my changes in a new PR

Yeah I'd like to get this in and add my changes in a new PR


log4j support

Hi,
I am new to Jaeger, and need some help on how to make span reported with logs.
With logback, I see spans with logs including application logs from the UI, but with log4j2 it doesn't get any log messages.
Is there any way to work with log4j2?
Thanks,
Seho

Im facing the same problem, i could see a open PR here:
https://github.com/opentracing-contrib/java-spring-jaeger/pull/60

Are you using logging reporter? The implementation is using slf4j https://github.com/jaegertracing/jaeger-client-java/blob/master/jaeger-core/src/main/java/io/jaegertracing/internal/reporters/LoggingReporter.java. The issue is probably a configuration on your side.
the #60 is adding trace IDs into MDC it does not log span content (operation name, time...)

I have found that we already have MDCScopeManager.
What we should do is likely just put MDCScopeManager in JaegerAutoConfiguration.
This way maybe better.

I saw #60 was closed and not merged, is there a reason? Would be nice to have that feature added

The reason is mentioned in https://github.com/opentracing-contrib/java-spring-jaeger/pull/60#issuecomment-664165735 - the MDC support is directly in Jaeger. Could somebody open a PR to configure the scope manager?

The reason is mentioned in #60 (comment) - the MDC support is directly in Jaeger. Could somebody open a PR to configure the scope manager?

Does java-spring-jaeger has any plan to update the jaeger-client version from 1.1 to 1.3+?
Since MDCScopeManager  is new feature in jaeger-client v1.3+

Hopefully soon

@geoand , don't want to push, but any updates here? can I help somehow?

@geoand , don't want to push, but any updates here? can I help somehow?

@pavolloffay do you know what the status of the Jaeger client is? Should we update to the latest?

@pavolloffay do you know what the status of the Jaeger client is? Should we update to the latest?


Hit Points

Whenever I import now (it was working last week), the hit points are always 0/0.  I created a new world with only this module active and it still doesn't set the HP.

I had a colon after "Hit Points".  So, the input looked like this:
Armor Class: 10
Hit Points: 18 (4d8)
Speed: 30 ft.
Once I removed the colon it imported fine.