A Jupyter Notebook to perform Regression Analysis for RHOAI Model Serving

Introduction
A Jupyter Notebook that uses Normal Distribution to determine the limits/threshold for Regression Analysis. The Current test results/measurements should be with in +/- 3 standards deviations from the sample mean.
The same mean is calculated from the sample space and the sample space have measurements/results of the previous version.
Highlights of the PR

A Table Graph for each KPI(Throughput, ITL, TTFT, TPOT) that summarizes the regression analysis of each data point/measurement.
A Line Graph for each KPI that summarizes the performance over different versions.

Prerequisites

You need a json file with the following schema in order to execute the Jupyter Notebook. You should provide Absolute Path of the json file in the Notebook.

{
	"opensearch_cluster": "<A URL to access OpenSearch Cluster and it should be given without trailing />",
	"opensearch_user": "<Username to be used for authentication with OpenSearch Cluster>",
	"opensearch_user_password": "<Password to be used for authentication with OpenSearch Cluster>",
	"ca_cert_file": "<Cert file for SSL Verification>"
}

I'm thinking it may make more sense to create a new directory one level up (projects/kserve/visualizations/notebooks or something like that) and put the notebook there.

The Current test results/measurements should be with in +/- 3 standards deviations from the sample mean.
Isn't that too lenient? do you have examples of current standard deviation and sample mean numbers for the model serving tests ?

I believe it is not lenient because we need exactly +/- 3 standard deviations in Normal Distribution to cover all the measurements/data points in the sample space but how we control the data points in the sample space plays a important factor in the regression analysis.
For example, If you could look the Line Graph that I have attached here, you can see that lines remain flat for all the models except japanese-llama-2-7b-instruct and llama-2-13b-chat-hf.

Flat lines tells us that numbers are distributed in a very short range, that also means that standard deviation is very low or negligible. Now, lets take a look at codellama-34b-instruct-hf measurements.
[
    618.6,
    618.3,
    624.8,
    619.3,
    612.7,
    620.9,
    621.3,
    623.6
]

>>> throughput = '''[
...     618.6,
...     618.3,
...     624.8,
...     619.3,
...     612.7,
...     620.9,
...     621.3,
...     623.6
... ]'''
>>> throughput = eval(throughput)
>>>
>>> statistics.stdev(throughput)
3.7244127053805225

>>> statistics.stdev(throughput) * 3     # Basically +/- 12 Token/sec
11.17323811614156

For model codellama-34b-instruct-hf at concurrency 32, we expect the latest version's value to fall within +/- 12 Tokens/Sec threshold. Anything otherwise will be marked as regression.
Now lets take a look at one of the uneven lines that we have here from model  japanese-llama-2-7b-instruct.
[
    152.8,
    90.3,
    190.1,
    129.9,
    83.6,
    87.5,
    339.7,
    151.1
]

>>> throughput = '''[
...     152.8,
...     90.3,
...     190.1,
...     129.9,
...     83.6,
...     87.5,
...     339.7,
...     151.1
... ]'''
>>>
>>>
>>> throughput = eval(throughput)
>>>
>>> statistics.mean(throughput)
153.125
>>>
>>> statistics.mean(throughput) * 3
459.375

And in here, we expect the new version's value to fall within +/- 500 Tokens/Sec threshold. This is wild side of it.
But again, like I said, It totally depends on how we control the measurements/data points in sample space. I have attached a table which is generated by the notebook as part of regression analysis. If you could see, for llama-2-13b-chat-hf at 1 concurrency believed to have regression even though the stddev is very small, which is (0.4 tokens/sec) and the delta is (2.1 tokens/sec).

Thanks for the explanation @mcharanrm. One more question: can you explain what do you mean by 'present_ver_mean' and 'previous_ver_mean' ?

Sure I can and apologies for not explaining it in the first place.
present_ver_mean  -  In other words, the average throughput of the latest version.
previous_ver_mean - sample mean, Avg of the sample space where space space is a list which has avg throughput from the previous version.
std_dev - standard deviation of the sample space.
std_dev_[1, 2, 3] - A %percentage value that shows what chunk of sample space fall within 1st, 2nd and 3rd standard deviation.
std_dev_[1, 2, 3]_bound - A boolean value that defines the closure property. Does the latest value fall within the 1st, 2nd, and 3rd standard deviation of the sample space ?
change - % change in average throughput w.r.t sample mean
delta - difference between average throughput and sample mean

I'm thinking it may make more sense to create a new directory one level up (projects/kserve/visualizations/notebooks or something like that) and put the notebook there.

Seems like ideal choice but I would like to hear @kpouget thoughts on it.

I'm thinking it may make more sense to create a new directory one level up (projects/kserve/visualizations/notebooks or something like that) and put the notebook there.

Seems like ideal choice but I would like to hear @kpouget thoughts on it.

🤔
I'm not 100% sure.
Either:
projects/kserve/visualizations/kserve-llm/notebooks/regression-analysis-using-normal-distribution.ipynb

if the notebook is 100% focused on kserve-llm metrics (which I doublt, in the medium term at least)
or
projects/kserve/visualizations/notebooks/regression-analysis-using-normal-distribution.ipynb

if it's related to kserve-llm and kserve-prom. Any of the two would work IMO.
I would recommend adding a way to launch this notebook and capture its output.
And better if it works with rhoai-plot as it doesn't require a cluster.
This mean:

adding jupiter as a dependency,
adding a configuration flag in the config.yaml + a preset
adding a hook in this function (or perhaps in this one, if we consider this general purpose)
running the notebook, saving the artifacts
adapting the code to connect to OpenSearch & download the artifacts, using the secrets from the vault

Yeah, notebook is 100% focused on kserve-llm metrics. So I will go with following path that was suggested.

projects/kserve/visualizations/kserve-llm/notebooks/regression-analysis-using-normal-distribution.ipynb

And looking at the other recommendations, I believe that they are leaning towards the activity that is defined in PSAP-1392, "Adding regression analysis to topsail pipeline".

@mcharanrm I think this can be closed as outdated.
Feel free to contribute to the analyze module in MatrixBenchmarking if you see things missing
https://github.com/openshift-psap/matrix-benchmarking/tree/main/matrix_benchmarking/analyze


[PayPal] Billing Address For Payer Info

Summary
We at the New York Times are in need of retrieving the billing address
for a given Billing Agreement Nonce using the Vault Flow.
We would like to propose the follow changes to satisfy this need.
Changes

Adds Address object to enable retrieval of the PayPal Billing Address
from the backend.

Side Effects
Can expect the Billing Address to be populated from the Billing Address
found in PayPal.
Example

Checklist

[x] Added changelog entry
[x] Ran unit tests (mvn verify -DskipITs)

@braebot @dan-manges I would be happy to add unit and integration tests if the changes are acceptable.

Sounds good. Let me know if you need anything on our end.

@eliasjpr We wanted to send a quick heads up, we're building on this work you submitted. The main change we're making is to use international address labels, so getCity -> getLocality. This way it's in parity with other Address objects returned by our API.

Thanks for the heads up I have informed my team about this change.

Hi @eliasjpr Happy friday! We just merged in our updates with your work to master, and plan to include this in the next release (which we're hoping to do next week). I'm going to go ahead and close this PR, thanks again for your contribution 😃

This is out in 2.109.0 https://github.com/braintree/braintree_java/commit/3cf022e01a8598c658a0c25d847f42838471c781


CI against Rails 6.0

Exclude CI matrix between Ruby 2.6 and Rails 6.0
Rails 6.0 requires Ruby 2.5

https://github.com/rails/rails/pull/34754

No need to exclude any JRuby because "JRuby 9.2.x is compatible with Ruby 2.5.x"

https://www.jruby.org/2019/04/09/jruby-9-2-7-0.html

I'm closing this pull request because I do not need it anymore. Anyone needs this one, please feel free to open another one.


Migrate CI & Pipeline to github actions

Summary

Concisely describe the issue and your solution:
Link to existing issue (type "#" to check):
Specify the tests done so far:

Solutions (Optional)
Please describe the details of your solution if it might be too complicated for reviewers.

Codecov Report

Merging #205 into develop will increase coverage by 0.56%.
The diff coverage is n/a.

@@              Coverage Diff              @@
##             develop     #205      +/-   ##
=============================================
+ Coverage      41.91%   42.47%   +0.56%
- Complexity      1579     1593      +14
=============================================
  Files            232      232
  Lines          12708    12708
  Branches        1574     1574
=============================================
+ Hits            5326     5398      +72
+ Misses          6740     6652      -88
- Partials         642      658      +16

Impacted Files
Coverage Δ
Complexity Δ

.../weid/protocol/response/ResolveEventLogResult.java
57.14% <0.00%> (-28.58%)
3.00% <0.00%> (-1.00%)

...m/webank/weid/protocol/base/CredentialWrapper.java
15.38% <0.00%> (-15.39%)
2.00% <0.00%> (-1.00%)

...rvice/impl/engine/fiscov2/WeIdServiceEngineV2.java
73.84% <0.00%> (-3.08%)
44.00% <0.00%> (-3.00%)

...ain/java/com/webank/weid/util/CredentialUtils.java
80.41% <0.00%> (-2.58%)
53.00% <0.00%> (-3.00%)

.../webank/weid/service/impl/EvidenceServiceImpl.java
36.61% <0.00%> (-2.35%)
26.00% <0.00%> (-2.00%)

...e/impl/engine/fiscov2/EvidenceServiceEngineV2.java
75.13% <0.00%> (-1.12%)
42.00% <0.00%> (-2.00%)

...k/weid/service/impl/CredentialPojoServiceImpl.java
44.57% <0.00%> (-0.18%)
133.00% <0.00%> (-1.00%)

...weid/suite/persistence/sql/driver/MysqlDriver.java
35.43% <0.00%> (+0.78%)
12.00% <0.00%> (ø%)

...m/webank/weid/suite/persistence/sql/SqlDomain.java
55.76% <0.00%> (+5.76%)
10.00% <0.00%> (+3.00%)

...ank/weid/suite/persistence/sql/ConnectionPool.java
86.59% <0.00%> (+26.80%)
12.00% <0.00%> (+8.00%)

... and 1 more

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 0e45e94...9934097. Read the comment docs.


The formatting could be better

When multiple questions come through at once it's not clear where one question ends and the next one begins, would be nice if the formatting was a little clearer.

Covered by: https://github.com/mbonig/so-notifier/pull/4

PR merged. Closing...


error on using :total-steps="total"

my code

		<radial-progress-bar :diameter="70"
                       :completed-steps="ladders.upvote"
                       :total-steps="total"
                       :strokeWidth="5"
                       :animateSpeed="2000"
                       startColor="#E80A0A"
                       innerStrokeColor="#C5BDBD">

{{ ladders.upvote }}

		  </radial-progress-bar>

</template>```

note: i gets error when total start with 0
error message: vue.js?3de6:4814 Error: <radialGradient> attribute fx: Expected length, "NaN".

I have the same error

anybody fixed?

what i hv to do when my page contains two radial-progress-bars

if i have two radial-progress-bars in a single page ... wt should i do ?? .... to fix these errors....

@jagadeesh01 Please start a new issue for multiple radial bars on a single page
@jhawas Is this still an issue?  I cannot reproduce by setting total-steps=0


Update INTRO_PATH to be Mac/unix friendly

Description
Running the Enterprise Template project in VS Code on a Mac throws a runtime error due to the Intro.json file not being found caused by the Windows forward-slash not being interpreted into the path.
Swapping the forward-slashes for back-slashes solves this issue and continues to function on Windows w/out issue.

Architecture
Bug Fixes
Conversational Experience
Maintenance
Language Understanding
Testing Steps

Checklist

[ X] I have tested this in VS Code on Mac, Visual Studio 2017 on Windows 10, in Azure App Service (Windows)

@lauren-mills one for the new template :)
Thanks @rob-derosa ! We now have a couple of macs for deployment/runtime testing but appreciate the spot!


add case if MemAvailable is existing in /proc/meminfo

Pull Request Checklist
This is related to Issue #45 (see thread)
General

[ ] Update Changelog following the conventions laid out on Keep A Changelog
Yes
[ ] Update README with any necessary configuration snippets
N/A
[ ] Binstubs are created if needed
N/A
[ ] RuboCop passes
N/A
[ ] Existing tests pass
tested on centos 6.8 (no MemAvailable field) and Ubuntu 16.04 (MemAvailable field exist)

Purpose
Rationnalize check and metrics for system with field MemAvailable in /proc/meminfo
Known Compatibility Issues
None

released: https://rubygems.org/gems/sensu-plugins-memory-checks/versions/3.0.3


Update InlineFunctionExample.java

I would like to suggest to use the current Java language specification codes.
Then it will be more easily to understand the code.

@yoshioterada, thanks, merged


Filament's online demo is no longer working

Describe the bug
Filament's suzanne demo cannot be displayed
To Reproduce
Steps to reproduce the behavior:

Go to the suzanne demo page
https://google.github.io/filament/webgl/tutorial_suzanne.html

Expected behavior
Expected behavior is that Suzanne will be displayed.
Logs
reason: Material version mismatch. Expected 15 but received 20.
Desktop (please complete the following information):

OS: Windows 10
GPU: NVIDIA GeForce RTX 2060
Browser: Chrome 100
Backend: WebGL

Additional context
Firefox outputs the same warning to the console and the model is not displayed.

Thanks, we probably forgot to regenerate it again. We need to automate this.

Partially fixed with #5405 but there are still issues, working on it.  We definitely need to overhaul the web site and make it automated.

Should be fixed now, although you might need to refresh your cache.


Consider adding extensions methods for adding ext providers with display names

...so users don't need to use "workarounds" like
services.Configure<AuthenticationOptions>(o => o.SchemeMap["OIDC"].DisplayName = whatever
..after all that display name is used to dynamically populate the login UI (as it was supposed to be used)...

I am running into that problem on aspnetcore 1.x.
There seems to be no display name for the IDP in the client.
Have you seen this problem?  (only happens on dynamic registration.)
..tom

OK - MS added the feature back due to popular demand ;)
https://github.com/aspnet/Security/pull/1320


Color overlays break with greyscale images

Cool project! Really like the idea.
While running 100x100 greyscale png's, the color overlays broke. I added cmap="grey" to the try statement in update which displays the images correctly, but the color overlays turn into a checkerboard of two colors. Changing the colors to "black"/"k" produced a solid output, although one that is purple.
I tracked the issue to np.resize. It only fills every other value of the first channel (the only one overlayed) with the a value because it thinks the image has three channels when in reality it doesn't (img.shape returns (width, height) only for greyscale).
This problem can be fixed by changing:
self.ax.imshow(np.resize(mpcolors.to_rgb(overlay), self.image.shape), alpha=0.4)
to something like
width, height = self.image.shape
self.ax.imshow(np.resize(mpcolors.to_rgb(overlay), (width, height, 3), alpha=0.4))

Thanks for comment! I have made this fix. All the best

Awesome. Used this project for some research, should find yourself in the acknowledgments of the manuscript eventually!

Glad it helped! Feel free to cite this repo or the article I wrote about it https://towardsdatascience.com/one-mouse-click-to-label-an-image-within-a-jupyter-notebook-40053095333a


Microsoft.VisualStudioCode.Insiders_v1.95.0 desktop

Microsoft.VisualStudioCode.Insiders_v1.95.0
Microsoft Reviewers: Open in CodeFlow

Hi @lszomoru,
It appears that the host for the PackageUrl and LicenseUrl is blocking our scans.
Since only the installer files was modified, the pipelines build a composite manifest, replacing missing files with those in repo. And then it performs all scans on them, including URL scans, which are what is failing here. Could these URLs be commented out of this and subsequent manifests?

Url validation error

manifests\m\Microsoft\VisualStudioCode\Insiders\1.95.0

https://code.visualstudio.com

Http status code: Forbidden

https://code.visualstudio.com/license/insiders

Http status code: Forbidden


Enhancement: Update phpunit settings to ignore the API

This PR will ignore the API classes for code coverage, and exclude the remaining API tests from the standard testsuite.
This should give a better idea of the code coverage, and speed up the tests just a little bit.
Since phpunit will use phpunit.xml over phpunit.xml.dist
$ cp phpunit.xml.dist phpunit.xml

Should be ran locally to update the file.

@BackEndTea
What do you think about splitting tests into

integration tests
unit tests

Then we could speed up the builds significantly by only collecting coverage for unit tests. I think we have a lot of mixed tests here, that’s why the build where we collect coverage is rather slow.

@localheinz
Our real integration tests are currently the controller tests. But those are also the only thing covering the controllers right now.
Due to the way the controllers are set up, if we want to make true unit tests of those we need to use the mockery 'overload' feature. This slows the test down by a lot. When i played around with it they took twice as long as a test that builds up the database, interacts with it, and tears it down again.
I'm all for properly splitting up the tests, having unit tests for every inch, and then integration tests which do a full run of the app, it would require a different setup for the controllers to be any faster.
If the goal is speeding up the travis build we could also run the assets and style stages paralel, which would save a minute or so.


Addition of animations

The page is not dynamic right now, I would like to add few transitions and animations using CSS and bootstrap classes

I would like to work on this issue


Implementation of render and act

PR Checklist
For reviewers:

This is build on top of #226 so that should be reviewed/merged first.

If you are contributing to Javis.jl, please make sure you are able to check off each item on this list:

[ ] Did I update CHANGELOG.md with whatever changes/features I added with this PR?
[ ] Did I make sure to only change the part of the file where I introduced a new change/feature?
[ ] Did I cover all corner cases to be close to 100% test coverage (if applicable)?
[ ] Did I properly add Javis dependencies to the Project.toml + set an upper bound of the dependency (if applicable)?
[ ] Did I properly add test dependencies to the test directory (if applicable)?
[ ] Did I check relevant tutorials that may be affected by changes in this PR?
[x] Did I clearly articulate why this PR was made the way it was and how it was made?

Link to relevant issue(s)
Closes #227
How did you address these issues with this PR? What methods did you use?
Instead of using javis(video, objects) one now has to define all objects beforehand and run
render(video). This removes the weird array syntax.
Additionally instead of using + to add an action to an object the function is called act! now.
An example looks like this:
video = Video(500, 500)

translate_action = Action(Translation(100, 10))
BackgroundObject(1:100, ground)
c1 = Object((args...) -> circle(O, 25, :fill))
c2 = Object(30:70, (args...) -> circle(O, 25, :fill), Point(0, 40))
act!(c1, translate_action)
act!(c2, translate_action)

render(video, pathname = "current/_trans.gif")

Okay @TheCedarPrince this is the next one to review. Only ~400 lines of code :smile:


clinvar_2024_11_11_v2_0_0_alpha dataset missing clinical assertion interpretation_description

As part of this I think I should verify that it's easy for us to wipe out past data and re-trigger the parse and bq_ingest steps on all of those re-run files

Closing as complete in pending PR and re-runs #257


About development of sealer upgrade command

i have learned about two relative command: "kubeadm upgrade" and "helm upgrade". the former focus on upgrade of nodes,that is,to a new version of k8s, while the later focus on upgrade of applications. that is, to a new version of image(chart). which one do we prefer "sealer upgrade" to do?

Do we want "sealer upgrade" do something as the command "sealos upgrade" do?

sealer upgrade has already been supported, closing this.


[WIP] Create TF Serving notebook

remaining work

add more comments
add how to build docker image for k8s

@sayakpaul
Modified the notebook based on your comment :)

Great!
Feel free to add the rest of the parts. I think we could do the rest of the components via scripts as done for the ONNX model. In that case, feel free to merge this PR.


How to obtain backend error messages, And that are not displayed in the console？

I want to be able to proactively capture this error, so that it is not displayed in the console, but in the form of a UI on the page. I couldn't find a similar hook, can you help me check this problem?

export const createLanguageClient = (
  transports: MessageTransports,
): MonacoLanguageClient => {
  return new MonacoLanguageClient({
    name: 'xxx Language Client',
    clientOptions: {
      documentSelector: ['isogql'],
      errorHandler: {
        error: () => ({ action: ErrorAction.Continue }),
        closed: () => ({ action: CloseAction.Restart }),
      },
    },
    connectionProvider: {
      get: () => {
        return Promise.resolve(transports);
      },
    },
  });
};

export const createWebSocket = (url: string): WebSocket => {
  const webSocket = new WebSocket(url);
  webSocket.onopen = () => {
    const socket = toSocket(webSocket);
    const reader = new WebSocketMessageReader(socket);
    const writer = new WebSocketMessageWriter(socket);
    const languageClient = createLanguageClient({
      reader,
      writer,
    });
    languageClient.start();
    reader.onClose(() => {
      createWebSocket(url);
    });
  };
  return webSocket;
};

You can probably replace the Log/Logger service override with you custom impl. The default one logs to the console

I've answered too fast! It's an  UnexpectedError, the code allows to override the handler but the libs don't expose it, fixing that

with https://github.com/CodinGame/monaco-vscode-api/pull/513, you'll be able to do
import { setUnexpectedErrorHandler } from 'vscode/monaco'

setUnexpectedErrorHandler((e) => {
  // whatever you want
})


Add dtype functionality in DWPC computation

Turns out this is already an issue there.
https://github.com/scipy/scipy/issues/7408


in .tsx file not workings

I did not make any changes in configuration after installation
in .tsx file

in .ts file

@chanceyliu
It seems like VSCode bug. Related issue - https://github.com/microsoft/vscode/issues/173244
Advice to use snippets: Try Ctrl+Space after having entered the snippet prefix. Or move the text cursor away, then back, and then do Ctrl+Space.


Provide API to get the list of library coordinates without calling findLibraries

Expected Behavior
The VersionCatalog view provides a number of methods like getLibraryAliases or findLibrary, which have performance issues. It is missing methods to query the model without sorting.
Current Behavior (optional)
No response
Context
In our case, we don't really need to know about the aliases, but simply need to memorize the coordinates. Ideally the view should be enriched with methods allowing to query the model without performance penalties : get the list of dependency providers for example.
See this PR which involves a quite dirty solution.
A pull request was created to improve the performance of findLibrary, but it would still involve, in our case, calling getLibraryAliases on each project, for each catalog, which would still sort items when we don't need it.

Thank you for your interest in Gradle!
This feature request is in the backlog of the relevant team and is prioritized by them.


Temporarily revert extended table functions for Druid 26

We received last-minute feedback about the enhanced table functions created as part of the catalog project. Since we don't have time to address those concerns, and we don't want to release the functions without the revisions, this PR pulls the table functions and the corresponding documentation. The code still exists, along with the unit tests, but the functions are not available to users.
Release note
No release notes needed because the functions were not part of a prior release.

This PR has:

[X] been self-reviewed.
[X] a release note entry in the PR description.
[ ] been tested in a test Druid cluster.

This PR seems ready. There is a build failure, but in the always-flaky Kafka IT.


Commit 47f87859 breaks requester notification email

I run a test suite against my staging environment to verify that when a requester sends an email that causes Handesk to open a ticket that the requester receives a response from Handesk acknowledging that the ticket has been opened.
This test passes in 1.4.2, but fails in origin:dev.  I bisected for the error and found the problem is introduced in commit 47f87859, because it removes the line:
$requester->notify($newTicketNotification);
Part of the commit message says "Notify team not requester on ticket created", so this change was intentional.  However, it seems incorrect to simply de-implement this valuable feature.  Could I submit a pull request to reenable this line for the moment until a global requester notifications option can be added?  The feature was present in 1.4.2 and it would be nice to not lose it in the main up to date branch.

Hi, You are right, we removed it since our customers can see the open tickets in the app itself so there was no need to notify them again as it was already displayed.
However, looks like a good setting to have, I believe we could add It to the settings table, something like "notify requester when ticket received"
Feel free to submit a PR with this, I'll be more than happy to add it
Thanks!

Are your issue requesters mostly within your organization?
In the use case where most requesters are outside the organization (and don't have a handesk account) then they cannot see the ticket history by logging in.  The only way for them to access the ticket history is if Handesk sends them a publicly accessible link to the issue.
In order to avoid too much inbox noise, it could make sense to send an email to the requester ONLY IF the requester has not already received a notification of the issue due to being a handesk user.

Our customers are not from the orgnization but they see the tickets within the app we provide support :)
The app fetches the tickets through the api
Jordi Puigdellívol

El 17 des 2019, a les 19:01, Joel<EMAIL_ADDRESS>va escriure:

Are your issue requesters mostly within your organization?
In the use case where most requesters are outside the organization (and don't have a handesk account) then they cannot see the ticket history by logging in. The only way for them to access the ticket history is if Handesk sends them a publicly accessible link to the issue.
In order to avoid too much inbox noise, it could make sense to send an email to the requester ONLY IF the requester has not already received a notification of the issue due to being a handesk user.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or unsubscribe.


Fix auto / manual mode detection on Somfy's Smart Thermostat.

Did you test it with your own thermostat?

I did, that's where it's coming from


SoftwareDiagnostics reset-watermarks doesn't reset

Problem
CurrentHeapHighWatermark remains the same before and after chip-tool softwarediagnostics reset-watermarks command.

Fixed : https://github.com/project-chip/connectedhomeip/pull/19104

Issue is still there.
ubuntu@ubuntu:~$ ./chip-tool softwarediagnostics  reset-watermarks 1 0
[1662490793.763453][4651:4651] CHIP:DL: ChipLinuxStorage::Init: Using KVS config file: /tmp/chip_kvs
[1662490793.769030][4651:4651] CHIP:DL: ChipLinuxStorage::Init: Using KVS config file: /tmp/chip_factory.ini
[1662490793.769319][4651:4651] CHIP:DL: ChipLinuxStorage::Init: Using KVS config file: /tmp/chip_config.ini
[1662490793.769460][4651:4651] CHIP:DL: ChipLinuxStorage::Init: Using KVS config file: /tmp/chip_counters.ini
[1662490793.769839][4651:4651] CHIP:DL: writing settings to file (/tmp/chip_counters.ini-LJhdg3)
[1662490793.770511][4651:4651] CHIP:DL: renamed tmp file to file (/tmp/chip_counters.ini)
[1662490793.770584][4651:4651] CHIP:DL: NVS set: chip-counters/reboot-count = 22 (0x16)
[1662490793.771684][4651:4651] CHIP:DL: Got Ethernet interface: eth0
[1662490793.772388][4651:4651] CHIP:DL: Found the primary Ethernet interface:eth0
[1662490793.773176][4651:4651] CHIP:DL: Got WiFi interface: wlan0
[1662490793.779322][4651:4651] CHIP:DL: Found the primary WiFi interface:wlan0
[1662490793.779406][4651:4651] CHIP:IN: UDP::Init bind&listen port=0
[1662490793.779523][4651:4651] CHIP:IN: UDP::Init bound to port=46569
[1662490793.779546][4651:4651] CHIP:IN: BLEBase::Init - setting/overriding transport
[1662490793.779566][4651:4651] CHIP:IN: TransportMgr initialized
[1662490793.779600][4651:4651] CHIP:FP: Initializing FabricTable from persistent storage
[1662490793.779753][4651:4651] CHIP:TS: Last Known Good Time: 2022-09-01T18:26:37
[1662490793.781231][4651:4651] CHIP:FP: Fabric index 0x1 was retrieved from storage. Compressed FabricId 0x92AA20E93FC9E286, FabricId 0x0000000000000001, NodeId 0x000000000001B669, VendorId 0xFFF1
[1662490793.783507][4651:4651] CHIP:ZCL: Using ZAP configuration...
[1662490793.788279][4651:4651] CHIP:DL: Avahi client registered
[1662490793.789942][4651:4651] CHIP:CTL: System State Initialized...
[1662490793.790060][4651:4651] CHIP:CTL: Stopping commissioning discovery over DNS-SD
[1662490793.790116][4651:4651] CHIP:CTL: Setting attestation nonce to random value
[1662490793.790165][4651:4651] CHIP:CTL: Setting CSR nonce to random value
[1662490793.790566][4651:4656] CHIP:DL: CHIP task running
[1662490793.790866][4651:4656] CHIP:DL: HandlePlatformSpecificBLEEvent 32784
[1662490793.790982][4651:4656] CHIP:CTL: Stopping commissioning discovery over DNS-SD
[1662490793.791035][4651:4656] CHIP:CTL: Setting attestation nonce to random value
[1662490793.791274][4651:4656] CHIP:CTL: Setting CSR nonce to random value
[1662490793.792529][4651:4656] CHIP:CTL: Generating NOC
[1662490793.793865][4651:4656] CHIP:FP: Validating NOC chain
[1662490793.796495][4651:4656] CHIP:FP: NOC chain validation successful
[1662490793.796755][4651:4656] CHIP:FP: Updated fabric at index: 0x1, Node ID: 0x000000000001B669
[1662490793.796802][4651:4656] CHIP:TS: Last Known Good Time: 2022-09-01T18:26:37
[1662490793.796836][4651:4656] CHIP:TS: New proposed Last Known Good Time: 2021-01-01T00:00:00
[1662490793.796865][4651:4656] CHIP:TS: Retaining current Last Known Good Time
[1662490793.846407][4651:4656] CHIP:FP: Metadata for Fabric 0x1 persisted to storage.
[1662490793.850220][4651:4656] CHIP:TS: Committing Last Known Good Time to storage: 2022-09-01T18:26:37
[1662490793.853867][4651:4656] CHIP:CTL: Joined the fabric at index 1. Compressed fabric ID is: 0x0000000000000000
[1662490793.863896][4651:4656] CHIP:TOO: Sending command to node 0x1
[1662490793.863948][4651:4656] CHIP:CSM: FindOrEstablishSession: PeerId = [1:0000000000000001]
[1662490793.863971][4651:4656] CHIP:CSM: FindOrEstablishSession: No existing OperationalSessionSetup instance found
[1662490793.864006][4651:4656] CHIP:CTL: OperationalSessionSetup[1:0000000000000001]: State change 1 --> 2
[1662490793.864035][4651:4656] CHIP:DIS: Resolving 92AA20E93FC9E286:0000000000000001 ...
[1662490793.972067][4651:4656] CHIP:DL: Avahi resolve found
[1662490793.972223][4651:4656] CHIP:DIS: Node ID resolved for 92AA20E93FC9E286:0000000000000001
[1662490793.972288][4651:4656] CHIP:DIS:        Hostname: EA1FEB7E88E978B2
[1662490793.972349][4651:4656] CHIP:DIS:        IP Address #1: fd11:35::a106:40e7:f142:8d6
[1662490793.972410][4651:4656] CHIP:DIS:        Port: 5540
[1662490793.972532][4651:4656] CHIP:DIS:        Mrp Interval idle: 5000 ms
[1662490793.972644][4651:4656] CHIP:DIS:        Mrp Interval active: 2000 ms
[1662490793.972805][4651:4656] CHIP:DIS:        TCP Supported: 0
[1662490793.974728][4651:4656] CHIP:DIS: Lookup clearing interface for non LL address
[1662490793.974814][4651:4656] CHIP:DIS: UDP:[fd11:35::a106:40e7:f142:8d6%veth9a68622]:5540: new best score: 6
[1662490793.974872][4651:4656] CHIP:DIS: Checking node lookup status after 111 ms
[1662490793.974925][4651:4656] CHIP:DIS: Keeping DNSSD lookup active
[1662490794.064159][4651:4656] CHIP:DIS: Checking node lookup status after 200 ms
[1662490794.064228][4651:4656] CHIP:DIS: OperationalSessionSetup[1:0000000000000001]: Updating device address to UDP:[fd11:35::a106:40e7:f142:8d6]:5540 while in state 2
[1662490794.064251][4651:4656] CHIP:CTL: OperationalSessionSetup[1:0000000000000001]: State change 2 --> 3
[1662490794.064381][4651:4656] CHIP:IN: SecureSession[0xffff7c00a0a0]: Allocated Type:2 LSID:10351
[1662490794.064426][4651:4656] CHIP:SC: Initiating session on local FabricIndex 1 from 0x000000000001B669 -> 0x0000000000000001
[1662490794.065277][4651:4656] CHIP:SC: Including MRP parameters
[1662490794.065444][4651:4656] CHIP:IN: Prepared unauthenticated message 0xffff7c0053a8 to 0x0000000000000000 (0)  of type 0x30 and protocolId (0, 0) on exchange 1897i with MessageCounter:80552473.
[1662490794.065494][4651:4656] CHIP:IN: Sending unauthenticated msg 0xffff7c0053a8 with MessageCounter:80552473 to 0x0000000000000000 at monotonic time:<PHONE_NUMBER>5AD068 msec
[1662490794.065697][4651:4656] CHIP:SC: Sent Sigma1 msg
[1662490794.065788][4651:4656] CHIP:CTL: OperationalSessionSetup[1:0000000000000001]: State change 3 --> 4
[1662490794.180559][4651:4656] CHIP:EM: Received message of type 0x10 with protocolId (0, 0) and MessageCounter:32080393 on exchange 1897i
[1662490794.180705][4651:4656] CHIP:EM: Found matching exchange: 1897i, Delegate: 0xffff7c00b138
[1662490794.180790][4651:4656] CHIP:EM: Rxd Ack; Removing MessageCounter:80552473 from Retrans Table on exchange 1897i
[1662490794.180844][4651:4656] CHIP:EM: Removed CHIP MessageCounter:80552473 from RetransTable on exchange 1897i
[1662490794.335597][4651:4656] CHIP:EM: Received message of type 0x31 with protocolId (0, 0) and MessageCounter:32080394 on exchange 1897i
[1662490794.335694][4651:4656] CHIP:EM: Found matching exchange: 1897i, Delegate: 0xffff7c00b138
[1662490794.335751][4651:4656] CHIP:EM: CHIP MessageCounter:80552473 not in RetransTable on exchange 1897i
[1662490794.335837][4651:4656] CHIP:SC: Received Sigma2 msg
[1662490794.335916][4651:4656] CHIP:SC: Peer assigned session session ID 12923
[1662490794.343995][4651:4656] CHIP:SC: Found MRP parameters in the message
[1662490794.344073][4651:4656] CHIP:SC: Sending Sigma3
[1662490794.344705][4651:4656] CHIP:EM: Piggybacking Ack for MessageCounter:32080394 on exchange: 1897i
[1662490794.344777][4651:4656] CHIP:IN: Prepared unauthenticated message 0xffff7c003a68 to 0x0000000000000000 (0)  of type 0x32 and protocolId (0, 0) on exchange 1897i with MessageCounter:80552474.
[1662490794.344820][4651:4656] CHIP:IN: Sending unauthenticated msg 0xffff7c003a68 with MessageCounter:80552474 to 0x0000000000000000 at monotonic time:<PHONE_NUMBER>5AD180 msec
[1662490794.345049][4651:4656] CHIP:SC: Sent Sigma3 msg
[1662490794.730595][4651:4656] CHIP:IN: Received a duplicate message with MessageCounter:32080394 on exchange 1897i
[1662490794.730703][4651:4656] CHIP:EM: Received message of type 0x31 with protocolId (0, 0) and MessageCounter:32080394 on exchange 1897i
[1662490794.730771][4651:4656] CHIP:EM: Found matching exchange: 1897i, Delegate: 0xffff7c00b138
[1662490794.730833][4651:4656] CHIP:EM: Forcing tx of solitary ack for duplicate MessageCounter:32080394 on exchange 1897i
[1662490794.730893][4651:4656] CHIP:EM: Sending Standalone Ack for MessageCounter:32080394 on exchange 1897i
[1662490794.730983][4651:4656] CHIP:IN: Prepared unauthenticated message 0xffff91a0d9b8 to 0x0000000000000000 (0)  of type 0x10 and protocolId (0, 0) on exchange 1897i with MessageCounter:80552475.
[1662490794.731072][4651:4656] CHIP:IN: Sending unauthenticated msg 0xffff91a0d9b8 with MessageCounter:80552475 to 0x0000000000000000 at monotonic time:<PHONE_NUMBER>5AD302 msec
[1662490794.740499][4651:4656] CHIP:EM: Received message of type 0x10 with protocolId (0, 0) and MessageCounter:32080395 on exchange 1897i
[1662490794.740585][4651:4656] CHIP:EM: Found matching exchange: 1897i, Delegate: 0xffff7c00b138
[1662490794.740697][4651:4656] CHIP:EM: Rxd Ack; Removing MessageCounter:80552474 from Retrans Table on exchange 1897i
[1662490794.740753][4651:4656] CHIP:EM: Removed CHIP MessageCounter:80552474 from RetransTable on exchange 1897i
[1662490794.750373][4651:4656] CHIP:EM: Received message of type 0x40 with protocolId (0, 0) and MessageCounter:32080396 on exchange 1897i
[1662490794.750444][4651:4656] CHIP:EM: Found matching exchange: 1897i, Delegate: 0xffff7c00b138
[1662490794.750493][4651:4656] CHIP:EM: CHIP MessageCounter:80552474 not in RetransTable on exchange 1897i
[1662490794.750566][4651:4656] CHIP:SC: Success status report received. Session was established
[1662490794.755652][4651:4656] CHIP:SC: SecureSession[0xffff7c00a0a0]: Moving from state 'kEstablishing' --> 'kActive'
[1662490794.755736][4651:4656] CHIP:IN: SecureSession[0xffff7c00a0a0]: Activated - Type:2 LSID:10351
[1662490794.755778][4651:4656] CHIP:IN: New secure session activated for device <0000000000000001, 1>, LSID:10351 PSID:12923!
[1662490794.755830][4651:4656] CHIP:CTL: OperationalSessionSetup[1:0000000000000001]: State change 4 --> 5
[1662490794.755924][4651:4656] CHIP:TOO: Sending cluster (0x00000034) command (0x00000000) on endpoint 0
[1662490794.756019][4651:4656] CHIP:DMG: ICR moving to [AddingComm]
[1662490794.756114][4651:4656] CHIP:DMG: ICR moving to [AddedComma]
[1662490794.756336][4651:4656] CHIP:IN: Prepared secure message 0xffff7c009b78 to 0x0000000000000001 (1)  of type 0x8 and protocolId (0, 1) on exchange 1898i with MessageCounter:19940449.
[1662490794.756424][4651:4656] CHIP:IN: Sending encrypted msg 0xffff7c009b78 with MessageCounter:19940449 to 0x0000000000000001 (1) at monotonic time:<PHONE_NUMBER>5AD31B msec
[1662490794.756796][4651:4656] CHIP:DMG: ICR moving to [CommandSen]
[1662490794.756898][4651:4656] CHIP:EM: Sending Standalone Ack for MessageCounter:32080396 on exchange 1897i
[1662490794.756982][4651:4656] CHIP:IN: Prepared unauthenticated message 0xffff91a0d968 to 0x0000000000000000 (0)  of type 0x10 and protocolId (0, 0) on exchange 1897i with MessageCounter:80552476.
[1662490794.757052][4651:4656] CHIP:IN: Sending unauthenticated msg 0xffff91a0d968 with MessageCounter:80552476 to 0x0000000000000000 at monotonic time:<PHONE_NUMBER>5AD31C msec
[1662490794.757270][4651:4656] CHIP:EM: Flushed pending ack for MessageCounter:32080396 on exchange 1897i
[1662490794.830564][4651:4656] CHIP:EM: Received message of type 0x9 with protocolId (0, 1) and MessageCounter:63762487 on exchange 1898i
[1662490794.830655][4651:4656] CHIP:EM: Found matching exchange: 1898i, Delegate: 0xffff7c009908
[1662490794.830731][4651:4656] CHIP:EM: Rxd Ack; Removing MessageCounter:19940449 from Retrans Table on exchange 1898i
[1662490794.830783][4651:4656] CHIP:EM: Removed CHIP MessageCounter:19940449 from RetransTable on exchange 1898i
[1662490794.830852][4651:4656] CHIP:DMG: ICR moving to [ResponseRe]
[1662490794.830951][4651:4656] CHIP:DMG: InvokeResponseMessage =
[1662490794.831004][4651:4656] CHIP:DMG: {
[1662490794.831058][4651:4656] CHIP:DMG:        suppressResponse = false,
[1662490794.831113][4651:4656] CHIP:DMG:        InvokeResponseIBs =
[1662490794.831182][4651:4656] CHIP:DMG:        [
[1662490794.831236][4651:4656] CHIP:DMG:                InvokeResponseIB =
[1662490794.831356][4651:4656] CHIP:DMG:                {
[1662490794.831417][4651:4656] CHIP:DMG:                        CommandStatusIB =
[1662490794.831485][4651:4656] CHIP:DMG:                        {
[1662490794.831552][4651:4656] CHIP:DMG:                                CommandPathIB =
[1662490794.831627][4651:4656] CHIP:DMG:                                {
[1662490794.831725][4651:4656] CHIP:DMG:                                        EndpointId = 0x0,
[1662490794.831805][4651:4656] CHIP:DMG:                                        ClusterId = 0x34,
[1662490794.831888][4651:4656] CHIP:DMG:                                        CommandId = 0x0,
[1662490794.831963][4651:4656] CHIP:DMG:                                },
[1662490794.832066][4651:4656] CHIP:DMG:
[1662490794.832128][4651:4656] CHIP:DMG:                                StatusIB =
[1662490794.832203][4651:4656] CHIP:DMG:                                {
[1662490794.832300][4651:4656] CHIP:DMG:                                        status = 0x00 (SUCCESS),
[1662490794.832381][4651:4656] CHIP:DMG:                                },
[1662490794.832461][4651:4656] CHIP:DMG:
[1662490794.832548][4651:4656] CHIP:DMG:                        },
[1662490794.832624][4651:4656] CHIP:DMG:
[1662490794.832738][4651:4656] CHIP:DMG:                },
[1662490794.832813][4651:4656] CHIP:DMG:
[1662490794.832888][4651:4656] CHIP:DMG:        ],
[1662490794.832954][4651:4656] CHIP:DMG:
[1662490794.833007][4651:4656] CHIP:DMG:        InteractionModelRevision = 1
[1662490794.833057][4651:4656] CHIP:DMG: },
[1662490794.833192][4651:4656] CHIP:DMG: Received Command Response Status for Endpoint=0 Cluster=0x0000_0034 Command=0x0000_0000 Status=0x0
[1662490794.833279][4651:4656] CHIP:DMG: ICR moving to [AwaitingDe]
[1662490794.833417][4651:4656] CHIP:EM: Sending Standalone Ack for MessageCounter:63762487 on exchange 1898i
[1662490794.833570][4651:4656] CHIP:IN: Prepared secure message 0xffff91a0d978 to 0x0000000000000001 (1)  of type 0x10 and protocolId (0, 0) on exchange 1898i with MessageCounter:19940450.
[1662490794.833675][4651:4656] CHIP:IN: Sending encrypted msg 0xffff91a0d978 with MessageCounter:19940450 to 0x0000000000000001 (1) at monotonic time:<PHONE_NUMBER>5AD369 msec
[1662490794.833949][4651:4656] CHIP:EM: Flushed pending ack for MessageCounter:63762487 on exchange 1898i
[1662490794.834341][4651:4651] CHIP:CTL: Shutting down the commissioner
[1662490794.834414][4651:4651] CHIP:CTL: Stopping commissioning discovery over DNS-SD
[1662490794.834465][4651:4651] CHIP:CTL: Shutting down the controller
[1662490794.834513][4651:4651] CHIP:IN: Expiring all sessions for fabric 0x1!!
[1662490794.834560][4651:4651] CHIP:IN: SecureSession[0xffff7c00a0a0]: MarkForEviction Type:2 LSID:10351
[1662490794.834610][4651:4651] CHIP:SC: SecureSession[0xffff7c00a0a0]: Moving from state 'kActive' --> 'kPendingEviction'
[1662490794.834651][4651:4651] CHIP:IN: SecureSession[0xffff7c00a0a0]: Released - Type:2 LSID:10351
[1662490794.834867][4651:4651] CHIP:FP: Forgetting fabric 0x1
[1662490794.834951][4651:4651] CHIP:TS: Pending Last Known Good Time: 2022-09-01T18:26:37
[1662490794.835232][4651:4651] CHIP:TS: Previous Last Known Good Time: 2022-09-01T18:26:37
[1662490794.835378][4651:4651] CHIP:TS: Reverted Last Known Good Time to previous value
[1662490794.835618][4651:4651] CHIP:CTL: Shutting down the commissioner
[1662490794.835675][4651:4651] CHIP:CTL: Stopping commissioning discovery over DNS-SD
[1662490794.835730][4651:4651] CHIP:CTL: Shutting down the controller
[1662490794.835852][4651:4651] CHIP:CTL: Shutting down the System State, this will teardown the CHIP Stack
[1662490794.837319][4651:4651] CHIP:DMG: IM WH moving to [Uninitialized]
[1662490794.837373][4651:4651] CHIP:DMG: IM WH moving to [Uninitialized]
[1662490794.837434][4651:4651] CHIP:DMG: IM WH moving to [Uninitialized]
[1662490794.837462][4651:4651] CHIP:DMG: IM WH moving to [Uninitialized]
[1662490794.837494][4651:4651] CHIP:DMG: All ReadHandler-s are clean, clear GlobalDirtySet
[1662490794.837604][4651:4651] CHIP:BLE: BleConnectionDelegate::CancelConnection is not implemented.
[1662490794.837950][4651:4651] CHIP:DL: writing settings to file (/tmp/chip_counters.ini-IqQmVO)
[1662490794.838936][4651:4651] CHIP:DL: renamed tmp file to file (/tmp/chip_counters.ini)
[1662490794.839022][4651:4651] CHIP:DL: NVS set: chip-counters/total-operational-hours = 0 (0x0)
[1662490794.839115][4651:4651] CHIP:DL: Inet Layer shutdown
[1662490794.839142][4651:4651] CHIP:DL: BLE shutdown
[1662490794.839170][4651:4651] CHIP:DL: System Layer shutdown
ubuntu@ubuntu:~$ ./chip-tool softwarediagnostics read current-heap-high-watermark 1 0
[1662490799.478014][4657:4657] CHIP:DL: ChipLinuxStorage::Init: Using KVS config file: /tmp/chip_kvs
[1662490799.483737][4657:4657] CHIP:DL: ChipLinuxStorage::Init: Using KVS config file: /tmp/chip_factory.ini
[1662490799.484023][4657:4657] CHIP:DL: ChipLinuxStorage::Init: Using KVS config file: /tmp/chip_config.ini
[1662490799.484177][4657:4657] CHIP:DL: ChipLinuxStorage::Init: Using KVS config file: /tmp/chip_counters.ini
[1662490799.484568][4657:4657] CHIP:DL: writing settings to file (/tmp/chip_counters.ini-0nae2l)
[1662490799.485269][4657:4657] CHIP:DL: renamed tmp file to file (/tmp/chip_counters.ini)
[1662490799.485335][4657:4657] CHIP:DL: NVS set: chip-counters/reboot-count = 23 (0x17)
[1662490799.486299][4657:4657] CHIP:DL: Got Ethernet interface: eth0
[1662490799.486930][4657:4657] CHIP:DL: Found the primary Ethernet interface:eth0
[1662490799.487599][4657:4657] CHIP:DL: Got WiFi interface: wlan0
[1662490799.493807][4657:4657] CHIP:DL: Found the primary WiFi interface:wlan0
[1662490799.493885][4657:4657] CHIP:IN: UDP::Init bind&listen port=0
[1662490799.494021][4657:4657] CHIP:IN: UDP::Init bound to port=56706
[1662490799.494050][4657:4657] CHIP:IN: BLEBase::Init - setting/overriding transport
[1662490799.494073][4657:4657] CHIP:IN: TransportMgr initialized
[1662490799.494134][4657:4657] CHIP:FP: Initializing FabricTable from persistent storage
[1662490799.494304][4657:4657] CHIP:TS: Last Known Good Time: 2022-09-01T18:26:37
[1662490799.496058][4657:4657] CHIP:FP: Fabric index 0x1 was retrieved from storage. Compressed FabricId 0x92AA20E93FC9E286, FabricId 0x0000000000000001, NodeId 0x000000000001B669, VendorId 0xFFF1
[1662490799.522738][4657:4657] CHIP:ZCL: Using ZAP configuration...
[1662490799.526953][4657:4657] CHIP:DL: Avahi client registered
[1662490799.528379][4657:4657] CHIP:CTL: System State Initialized...
[1662490799.528485][4657:4657] CHIP:CTL: Stopping commissioning discovery over DNS-SD
[1662490799.528531][4657:4657] CHIP:CTL: Setting attestation nonce to random value
[1662490799.528572][4657:4657] CHIP:CTL: Setting CSR nonce to random value
[1662490799.528960][4657:4662] CHIP:DL: CHIP task running
[1662490799.529216][4657:4662] CHIP:DL: HandlePlatformSpecificBLEEvent 32784
[1662490799.529306][4657:4662] CHIP:CTL: Stopping commissioning discovery over DNS-SD
[1662490799.529349][4657:4662] CHIP:CTL: Setting attestation nonce to random value
[1662490799.529518][4657:4662] CHIP:CTL: Setting CSR nonce to random value
[1662490799.530471][4657:4662] CHIP:CTL: Generating NOC
[1662490799.531494][4657:4662] CHIP:FP: Validating NOC chain
[1662490799.533217][4657:4662] CHIP:FP: NOC chain validation successful
[1662490799.533397][4657:4662] CHIP:FP: Updated fabric at index: 0x1, Node ID: 0x000000000001B669
[1662490799.533434][4657:4662] CHIP:TS: Last Known Good Time: 2022-09-01T18:26:37
[1662490799.533454][4657:4662] CHIP:TS: New proposed Last Known Good Time: 2021-01-01T00:00:00
[1662490799.533473][4657:4662] CHIP:TS: Retaining current Last Known Good Time
[1662490799.539003][4657:4662] CHIP:FP: Metadata for Fabric 0x1 persisted to storage.
[1662490799.540966][4657:4662] CHIP:TS: Committing Last Known Good Time to storage: 2022-09-01T18:26:37
[1662490799.542833][4657:4662] CHIP:CTL: Joined the fabric at index 1. Compressed fabric ID is: 0x0000000000000000
[1662490799.552183][4657:4662] CHIP:TOO: Sending command to node 0x1
[1662490799.552244][4657:4662] CHIP:CSM: FindOrEstablishSession: PeerId = [1:0000000000000001]
[1662490799.552268][4657:4662] CHIP:CSM: FindOrEstablishSession: No existing OperationalSessionSetup instance found
[1662490799.552305][4657:4662] CHIP:CTL: OperationalSessionSetup[1:0000000000000001]: State change 1 --> 2
[1662490799.552335][4657:4662] CHIP:DIS: Resolving 92AA20E93FC9E286:0000000000000001 ...
[1662490799.554210][4657:4662] CHIP:DL: Avahi resolve found
[1662490799.554292][4657:4662] CHIP:DIS: Node ID resolved for 92AA20E93FC9E286:0000000000000001
[1662490799.554315][4657:4662] CHIP:DIS:        Hostname: EA1FEB7E88E978B2
[1662490799.554369][4657:4662] CHIP:DIS:        IP Address #1: fd11:35::a106:40e7:f142:8d6
[1662490799.554393][4657:4662] CHIP:DIS:        Port: 5540
[1662490799.554413][4657:4662] CHIP:DIS:        Mrp Interval idle: 5000 ms
[1662490799.554433][4657:4662] CHIP:DIS:        Mrp Interval active: 2000 ms
[1662490799.554455][4657:4662] CHIP:DIS:        TCP Supported: 0
[1662490799.555296][4657:4662] CHIP:DIS: Lookup clearing interface for non LL address
[1662490799.555345][4657:4662] CHIP:DIS: UDP:[fd11:35::a106:40e7:f142:8d6%veth9a68622]:5540: new best score: 6
[1662490799.555368][4657:4662] CHIP:DIS: Checking node lookup status after 3 ms
[1662490799.555386][4657:4662] CHIP:DIS: Keeping DNSSD lookup active
[1662490799.752815][4657:4662] CHIP:DIS: Checking node lookup status after 201 ms
[1662490799.752939][4657:4662] CHIP:DIS: OperationalSessionSetup[1:0000000000000001]: Updating device address to UDP:[fd11:35::a106:40e7:f142:8d6]:5540 while in state 2
[1662490799.753003][4657:4662] CHIP:CTL: OperationalSessionSetup[1:0000000000000001]: State change 2 --> 3
[1662490799.753234][4657:4662] CHIP:IN: SecureSession[0xffff7c00a0a0]: Allocated Type:2 LSID:51894
[1662490799.753326][4657:4662] CHIP:SC: Initiating session on local FabricIndex 1 from 0x000000000001B669 -> 0x0000000000000001
[1662490799.755004][4657:4662] CHIP:SC: Including MRP parameters
[1662490799.755297][4657:4662] CHIP:IN: Prepared unauthenticated message 0xffff7c0053a8 to 0x0000000000000000 (0)  of type 0x30 and protocolId (0, 0) on exchange 23225i with MessageCounter:145707524.
[1662490799.755402][4657:4662] CHIP:IN: Sending unauthenticated msg 0xffff7c0053a8 with MessageCounter:145707524 to 0x0000000000000000 at monotonic time:<PHONE_NUMBER>5AE6A2 msec
[1662490799.755768][4657:4662] CHIP:SC: Sent Sigma1 msg
[1662490799.755844][4657:4662] CHIP:CTL: OperationalSessionSetup[1:0000000000000001]: State change 3 --> 4
[1662490799.870005][4657:4662] CHIP:EM: Received message of type 0x10 with protocolId (0, 0) and MessageCounter:32080397 on exchange 23225i
[1662490799.870071][4657:4662] CHIP:EM: Found matching exchange: 23225i, Delegate: 0xffff7c00b138
[1662490799.870121][4657:4662] CHIP:EM: Rxd Ack; Removing MessageCounter:145707524 from Retrans Table on exchange 23225i
[1662490799.870152][4657:4662] CHIP:EM: Removed CHIP MessageCounter:145707524 from RetransTable on exchange 23225i
[1662490800.025279][4657:4662] CHIP:EM: Received message of type 0x31 with protocolId (0, 0) and MessageCounter:32080398 on exchange 23225i
[1662490800.025370][4657:4662] CHIP:EM: Found matching exchange: 23225i, Delegate: 0xffff7c00b138
[1662490800.025431][4657:4662] CHIP:EM: CHIP MessageCounter:145707524 not in RetransTable on exchange 23225i
[1662490800.025514][4657:4662] CHIP:SC: Received Sigma2 msg
[1662490800.025587][4657:4662] CHIP:SC: Peer assigned session session ID 12924
[1662490800.034222][4657:4662] CHIP:SC: Found MRP parameters in the message
[1662490800.034358][4657:4662] CHIP:SC: Sending Sigma3
[1662490800.034978][4657:4662] CHIP:EM: Piggybacking Ack for MessageCounter:32080398 on exchange: 23225i
[1662490800.035052][4657:4662] CHIP:IN: Prepared unauthenticated message 0xffff7c003a68 to 0x0000000000000000 (0)  of type 0x32 and protocolId (0, 0) on exchange 23225i with MessageCounter:145707525.
[1662490800.035103][4657:4662] CHIP:IN: Sending unauthenticated msg 0xffff7c003a68 with MessageCounter:145707525 to 0x0000000000000000 at monotonic time:<PHONE_NUMBER>5AE7BA msec
[1662490800.035326][4657:4662] CHIP:SC: Sent Sigma3 msg
[1662490800.300283][4657:4662] CHIP:EM: Received message of type 0x10 with protocolId (0, 0) and MessageCounter:32080399 on exchange 23225i
[1662490800.300377][4657:4662] CHIP:EM: Found matching exchange: 23225i, Delegate: 0xffff7c00b138
[1662490800.300457][4657:4662] CHIP:EM: Rxd Ack; Removing MessageCounter:145707525 from Retrans Table on exchange 23225i
[1662490800.300510][4657:4662] CHIP:EM: Removed CHIP MessageCounter:145707525 from RetransTable on exchange 23225i
[1662490800.365418][4657:4662] CHIP:EM: Received message of type 0x40 with protocolId (0, 0) and MessageCounter:32080400 on exchange 23225i
[1662490800.365515][4657:4662] CHIP:EM: Found matching exchange: 23225i, Delegate: 0xffff7c00b138
[1662490800.365579][4657:4662] CHIP:EM: CHIP MessageCounter:145707525 not in RetransTable on exchange 23225i
[1662490800.365674][4657:4662] CHIP:SC: Success status report received. Session was established
[1662490800.372226][4657:4662] CHIP:SC: SecureSession[0xffff7c00a0a0]: Moving from state 'kEstablishing' --> 'kActive'
[1662490800.372292][4657:4662] CHIP:IN: SecureSession[0xffff7c00a0a0]: Activated - Type:2 LSID:51894
[1662490800.372318][4657:4662] CHIP:IN: New secure session activated for device <0000000000000001, 1>, LSID:51894 PSID:12924!
[1662490800.372354][4657:4662] CHIP:CTL: OperationalSessionSetup[1:0000000000000001]: State change 4 --> 5
[1662490800.372442][4657:4662] CHIP:TOO:        cluster 0x0000_0034, attribute: 0x0000_0003, endpoint 0
[1662490800.372486][4657:4662] CHIP:TOO: Sending ReadAttribute to:
[1662490800.372526][4657:4662] CHIP:DMG: SendReadRequest ReadClient[0xffff7c00d010]: Sending Read Request
[1662490800.372733][4657:4662] CHIP:IN: Prepared secure message 0xffff7c009b78 to 0x0000000000000001 (1)  of type 0x2 and protocolId (0, 1) on exchange 23226i with MessageCounter:254959774.
[1662490800.372793][4657:4662] CHIP:IN: Sending encrypted msg 0xffff7c009b78 with MessageCounter:254959774 to 0x0000000000000001 (1) at monotonic time:<PHONE_NUMBER>5AE90C msec
[1662490800.373034][4657:4662] CHIP:DMG: MoveToState ReadClient[0xffff7c00d010]: Moving to [AwaitingIn]
[1662490800.373114][4657:4662] CHIP:EM: Sending Standalone Ack for MessageCounter:32080400 on exchange 23225i
[1662490800.373171][4657:4662] CHIP:IN: Prepared unauthenticated message 0xffff8f7ed968 to 0x0000000000000000 (0)  of type 0x10 and protocolId (0, 0) on exchange 23225i with MessageCounter:145707526.
[1662490800.373220][4657:4662] CHIP:IN: Sending unauthenticated msg 0xffff8f7ed968 with MessageCounter:145707526 to 0x0000000000000000 at monotonic time:<PHONE_NUMBER>5AE90C msec
[1662490800.373343][4657:4662] CHIP:EM: Flushed pending ack for MessageCounter:32080400 on exchange 23225i
[1662490800.440188][4657:4662] CHIP:EM: Received message of type 0x5 with protocolId (0, 1) and MessageCounter:76652341 on exchange 23226i
[1662490800.440244][4657:4662] CHIP:EM: Found matching exchange: 23226i, Delegate: 0xffff7c00d020
[1662490800.440289][4657:4662] CHIP:EM: Rxd Ack; Removing MessageCounter:254959774 from Retrans Table on exchange 23226i
[1662490800.440311][4657:4662] CHIP:EM: Removed CHIP MessageCounter:254959774 from RetransTable on exchange 23226i
[1662490800.440377][4657:4662] CHIP:DMG: ReportDataMessage =
[1662490800.440407][4657:4662] CHIP:DMG: {
[1662490800.440427][4657:4662] CHIP:DMG:        AttributeReportIBs =
[1662490800.440455][4657:4662] CHIP:DMG:        [
[1662490800.440476][4657:4662] CHIP:DMG:                AttributeReportIB =
[1662490800.440509][4657:4662] CHIP:DMG:                {
[1662490800.440531][4657:4662] CHIP:DMG:                        AttributeDataIB =
[1662490800.440561][4657:4662] CHIP:DMG:                        {
[1662490800.440591][4657:4662] CHIP:DMG:                                DataVersion = 0x23494e62,
[1662490800.440621][4657:4662] CHIP:DMG:                                AttributePathIB =
[1662490800.440683][4657:4662] CHIP:DMG:                                {
[1662490800.440720][4657:4662] CHIP:DMG:                                        Endpoint = 0x0,
[1662490800.440752][4657:4662] CHIP:DMG:                                        Cluster = 0x34,
[1662490800.440784][4657:4662] CHIP:DMG:                                        Attribute = 0x0000_0003,
[1662490800.440813][4657:4662] CHIP:DMG:                                }
[1662490800.440845][4657:4662] CHIP:DMG:
[1662490800.440877][4657:4662] CHIP:DMG:                                Data = 12048,
[1662490800.440901][4657:4662] CHIP:DMG:                        },
[1662490800.440930][4657:4662] CHIP:DMG:
[1662490800.440953][4657:4662] CHIP:DMG:                },
[1662490800.440980][4657:4662] CHIP:DMG:
[1662490800.441001][4657:4662] CHIP:DMG:        ],
[1662490800.441028][4657:4662] CHIP:DMG:
[1662490800.441051][4657:4662] CHIP:DMG:        SuppressResponse = true,
[1662490800.441073][4657:4662] CHIP:DMG:        InteractionModelRevision = 1
[1662490800.441095][4657:4662] CHIP:DMG: }
[1662490800.441227][4657:4662] CHIP:TOO: Endpoint: 0 Cluster: 0x0000_0034 Attribute 0x0000_0003 DataVersion: 592006754
[1662490800.441307][4657:4662] CHIP:TOO:   CurrentHeapHighWatermark: 12048
[1662490800.441396][4657:4662] CHIP:EM: Sending Standalone Ack for MessageCounter:76652341 on exchange 23226i
[1662490800.441505][4657:4662] CHIP:IN: Prepared secure message 0xffff8f7ed978 to 0x0000000000000001 (1)  of type 0x10 and protocolId (0, 0) on exchange 23226i with MessageCounter:254959775.
[1662490800.441550][4657:4662] CHIP:IN: Sending encrypted msg 0xffff8f7ed978 with MessageCounter:254959775 to 0x0000000000000001 (1) at monotonic time:<PHONE_NUMBER>5AE950 msec
[1662490800.441707][4657:4662] CHIP:EM: Flushed pending ack for MessageCounter:76652341 on exchange 23226i
[1662490800.442082][4657:4657] CHIP:CTL: Shutting down the commissioner
[1662490800.442135][4657:4657] CHIP:CTL: Stopping commissioning discovery over DNS-SD
[1662490800.442158][4657:4657] CHIP:CTL: Shutting down the controller
[1662490800.442178][4657:4657] CHIP:IN: Expiring all sessions for fabric 0x1!!
[1662490800.442197][4657:4657] CHIP:IN: SecureSession[0xffff7c00a0a0]: MarkForEviction Type:2 LSID:51894
[1662490800.442218][4657:4657] CHIP:SC: SecureSession[0xffff7c00a0a0]: Moving from state 'kActive' --> 'kPendingEviction'
[1662490800.442238][4657:4657] CHIP:IN: SecureSession[0xffff7c00a0a0]: Released - Type:2 LSID:51894
[1662490800.442262][4657:4657] CHIP:FP: Forgetting fabric 0x1
[1662490800.442306][4657:4657] CHIP:TS: Pending Last Known Good Time: 2022-09-01T18:26:37
[1662490800.442472][4657:4657] CHIP:TS: Previous Last Known Good Time: 2022-09-01T18:26:37
[1662490800.442499][4657:4657] CHIP:TS: Reverted Last Known Good Time to previous value
[1662490800.442546][4657:4657] CHIP:CTL: Shutting down the commissioner
[1662490800.442567][4657:4657] CHIP:CTL: Stopping commissioning discovery over DNS-SD
[1662490800.442596][4657:4657] CHIP:CTL: Shutting down the controller
[1662490800.442615][4657:4657] CHIP:CTL: Shutting down the System State, this will teardown the CHIP Stack
[1662490800.443630][4657:4657] CHIP:DMG: IM WH moving to [Uninitialized]
[1662490800.443681][4657:4657] CHIP:DMG: IM WH moving to [Uninitialized]
[1662490800.443739][4657:4657] CHIP:DMG: IM WH moving to [Uninitialized]
[1662490800.443785][4657:4657] CHIP:DMG: IM WH moving to [Uninitialized]
[1662490800.443834][4657:4657] CHIP:DMG: All ReadHandler-s are clean, clear GlobalDirtySet
[1662490800.443953][4657:4657] CHIP:BLE: BleConnectionDelegate::CancelConnection is not implemented.
[1662490800.444317][4657:4657] CHIP:DL: writing settings to file (/tmp/chip_counters.ini-gjeNpm)
[1662490800.445328][4657:4657] CHIP:DL: renamed tmp file to file (/tmp/chip_counters.ini)
[1662490800.445418][4657:4657] CHIP:DL: NVS set: chip-counters/total-operational-hours = 0 (0x0)
[1662490800.445441][4657:4657] CHIP:DL: Inet Layer shutdown
[1662490800.445462][4657:4657] CHIP:DL: BLE shutdown
[1662490800.445482][4657:4657] CHIP:DL: System Layer shutdown
ubuntu@ubuntu:~$ ./chip-tool softwarediagnostics read current-heap-used 1 0
[1662490807.418375][4664:4664] CHIP:DL: ChipLinuxStorage::Init: Using KVS config file: /tmp/chip_kvs
[1662490807.423933][4664:4664] CHIP:DL: ChipLinuxStorage::Init: Using KVS config file: /tmp/chip_factory.ini
[1662490807.424241][4664:4664] CHIP:DL: ChipLinuxStorage::Init: Using KVS config file: /tmp/chip_config.ini
[1662490807.424389][4664:4664] CHIP:DL: ChipLinuxStorage::Init: Using KVS config file: /tmp/chip_counters.ini
[1662490807.424814][4664:4664] CHIP:DL: writing settings to file (/tmp/chip_counters.ini-V1GqEt)
[1662490807.425490][4664:4664] CHIP:DL: renamed tmp file to file (/tmp/chip_counters.ini)
[1662490807.425568][4664:4664] CHIP:DL: NVS set: chip-counters/reboot-count = 24 (0x18)
[1662490807.426525][4664:4664] CHIP:DL: Got Ethernet interface: eth0
[1662490807.427246][4664:4664] CHIP:DL: Found the primary Ethernet interface:eth0
[1662490807.427970][4664:4664] CHIP:DL: Got WiFi interface: wlan0
[1662490807.430325][4664:4664] CHIP:DL: Found the primary WiFi interface:wlan0
[1662490807.430411][4664:4664] CHIP:IN: UDP::Init bind&listen port=0
[1662490807.430532][4664:4664] CHIP:IN: UDP::Init bound to port=32906
[1662490807.430559][4664:4664] CHIP:IN: BLEBase::Init - setting/overriding transport
[1662490807.430578][4664:4664] CHIP:IN: TransportMgr initialized
[1662490807.430616][4664:4664] CHIP:FP: Initializing FabricTable from persistent storage
[1662490807.430774][4664:4664] CHIP:TS: Last Known Good Time: 2022-09-01T18:26:37
[1662490807.432275][4664:4664] CHIP:FP: Fabric index 0x1 was retrieved from storage. Compressed FabricId 0x92AA20E93FC9E286, FabricId 0x0000000000000001, NodeId 0x000000000001B669, VendorId 0xFFF1
[1662490807.434735][4664:4664] CHIP:ZCL: Using ZAP configuration...
[1662490807.438973][4664:4664] CHIP:DL: Avahi client registered
[1662490807.440389][4664:4664] CHIP:CTL: System State Initialized...
[1662490807.440495][4664:4664] CHIP:CTL: Stopping commissioning discovery over DNS-SD
[1662490807.440540][4664:4664] CHIP:CTL: Setting attestation nonce to random value
[1662490807.440581][4664:4664] CHIP:CTL: Setting CSR nonce to random value
[1662490807.440982][4664:4669] CHIP:DL: CHIP task running
[1662490807.441229][4664:4669] CHIP:DL: HandlePlatformSpecificBLEEvent 32784
[1662490807.441316][4664:4669] CHIP:CTL: Stopping commissioning discovery over DNS-SD
[1662490807.441359][4664:4669] CHIP:CTL: Setting attestation nonce to random value
[1662490807.441528][4664:4669] CHIP:CTL: Setting CSR nonce to random value
[1662490807.442496][4664:4669] CHIP:CTL: Generating NOC
[1662490807.443529][4664:4669] CHIP:FP: Validating NOC chain
[1662490807.445233][4664:4669] CHIP:FP: NOC chain validation successful
[1662490807.445419][4664:4669] CHIP:FP: Updated fabric at index: 0x1, Node ID: 0x000000000001B669
[1662490807.445455][4664:4669] CHIP:TS: Last Known Good Time: 2022-09-01T18:26:37
[1662490807.445475][4664:4669] CHIP:TS: New proposed Last Known Good Time: 2021-01-01T00:00:00
[1662490807.445494][4664:4669] CHIP:TS: Retaining current Last Known Good Time
[1662490807.450717][4664:4669] CHIP:FP: Metadata for Fabric 0x1 persisted to storage.
[1662490807.452991][4664:4669] CHIP:TS: Committing Last Known Good Time to storage: 2022-09-01T18:26:37
[1662490807.454988][4664:4669] CHIP:CTL: Joined the fabric at index 1. Compressed fabric ID is: 0x0000000000000000
[1662490807.463975][4664:4669] CHIP:TOO: Sending command to node 0x1
[1662490807.464029][4664:4669] CHIP:CSM: FindOrEstablishSession: PeerId = [1:0000000000000001]
[1662490807.464054][4664:4669] CHIP:CSM: FindOrEstablishSession: No existing OperationalSessionSetup instance found
[1662490807.464091][4664:4669] CHIP:CTL: OperationalSessionSetup[1:0000000000000001]: State change 1 --> 2
[1662490807.464123][4664:4669] CHIP:DIS: Resolving 92AA20E93FC9E286:0000000000000001 ...
[1662490807.466016][4664:4669] CHIP:DL: Avahi resolve found
[1662490807.466089][4664:4669] CHIP:DIS: Node ID resolved for 92AA20E93FC9E286:0000000000000001
[1662490807.466112][4664:4669] CHIP:DIS:        Hostname: EA1FEB7E88E978B2
[1662490807.466138][4664:4669] CHIP:DIS:        IP Address #1: fd11:35::a106:40e7:f142:8d6
[1662490807.466159][4664:4669] CHIP:DIS:        Port: 5540
[1662490807.466179][4664:4669] CHIP:DIS:        Mrp Interval idle: 5000 ms
[1662490807.466199][4664:4669] CHIP:DIS:        Mrp Interval active: 2000 ms
[1662490807.466219][4664:4669] CHIP:DIS:        TCP Supported: 0
[1662490807.467046][4664:4669] CHIP:DIS: Lookup clearing interface for non LL address
[1662490807.467079][4664:4669] CHIP:DIS: UDP:[fd11:35::a106:40e7:f142:8d6%veth9a68622]:5540: new best score: 6
[1662490807.467105][4664:4669] CHIP:DIS: Checking node lookup status after 3 ms
[1662490807.467125][4664:4669] CHIP:DIS: Keeping DNSSD lookup active
[1662490807.664512][4664:4669] CHIP:DIS: Checking node lookup status after 200 ms
[1662490807.664631][4664:4669] CHIP:DIS: OperationalSessionSetup[1:0000000000000001]: Updating device address to UDP:[fd11:35::a106:40e7:f142:8d6]:5540 while in state 2
[1662490807.664735][4664:4669] CHIP:CTL: OperationalSessionSetup[1:0000000000000001]: State change 2 --> 3
[1662490807.664964][4664:4669] CHIP:IN: SecureSession[0xffff7800a0a0]: Allocated Type:2 LSID:60218
[1662490807.665056][4664:4669] CHIP:SC: Initiating session on local FabricIndex 1 from 0x000000000001B669 -> 0x0000000000000001
[1662490807.666699][4664:4669] CHIP:SC: Including MRP parameters
[1662490807.667173][4664:4669] CHIP:IN: Prepared unauthenticated message 0xffff780053a8 to 0x0000000000000000 (0)  of type 0x30 and protocolId (0, 0) on exchange 5216i with MessageCounter:210541572.
[1662490807.667282][4664:4669] CHIP:IN: Sending unauthenticated msg 0xffff780053a8 with MessageCounter:210541572 to 0x0000000000000000 at monotonic time:<PHONE_NUMBER>5B058A msec
[1662490807.667645][4664:4669] CHIP:SC: Sent Sigma1 msg
[1662490807.667727][4664:4669] CHIP:CTL: OperationalSessionSetup[1:0000000000000001]: State change 3 --> 4
[1662490807.785041][4664:4669] CHIP:EM: Received message of type 0x10 with protocolId (0, 0) and MessageCounter:32080401 on exchange 5216i
[1662490807.785144][4664:4669] CHIP:EM: Found matching exchange: 5216i, Delegate: 0xffff7800b138
[1662490807.785233][4664:4669] CHIP:EM: Rxd Ack; Removing MessageCounter:210541572 from Retrans Table on exchange 5216i
[1662490807.785296][4664:4669] CHIP:EM: Removed CHIP MessageCounter:210541572 from RetransTable on exchange 5216i
[1662490807.939884][4664:4669] CHIP:EM: Received message of type 0x31 with protocolId (0, 0) and MessageCounter:32080402 on exchange 5216i
[1662490807.939978][4664:4669] CHIP:EM: Found matching exchange: 5216i, Delegate: 0xffff7800b138
[1662490807.940038][4664:4669] CHIP:EM: CHIP MessageCounter:210541572 not in RetransTable on exchange 5216i
[1662490807.940120][4664:4669] CHIP:SC: Received Sigma2 msg
[1662490807.940196][4664:4669] CHIP:SC: Peer assigned session session ID 12925
[1662490807.950169][4664:4669] CHIP:SC: Found MRP parameters in the message
[1662490807.950459][4664:4669] CHIP:SC: Sending Sigma3
[1662490807.951724][4664:4669] CHIP:EM: Piggybacking Ack for MessageCounter:32080402 on exchange: 5216i
[1662490807.951856][4664:4669] CHIP:IN: Prepared unauthenticated message 0xffff78003a68 to 0x0000000000000000 (0)  of type 0x32 and protocolId (0, 0) on exchange 5216i with MessageCounter:210541573.
[1662490807.951954][4664:4669] CHIP:IN: Sending unauthenticated msg 0xffff78003a68 with MessageCounter:210541573 to 0x0000000000000000 at monotonic time:<PHONE_NUMBER>5B06A7 msec
[1662490807.952334][4664:4669] CHIP:SC: Sent Sigma3 msg
[1662490808.240132][4664:4669] CHIP:EM: Received message of type 0x10 with protocolId (0, 0) and MessageCounter:32080403 on exchange 5216i
[1662490808.240239][4664:4669] CHIP:EM: Found matching exchange: 5216i, Delegate: 0xffff7800b138
[1662490808.240329][4664:4669] CHIP:EM: Rxd Ack; Removing MessageCounter:210541573 from Retrans Table on exchange 5216i
[1662490808.240391][4664:4669] CHIP:EM: Removed CHIP MessageCounter:210541573 from RetransTable on exchange 5216i
[1662490808.259771][4664:4669] CHIP:EM: Received message of type 0x40 with protocolId (0, 0) and MessageCounter:32080404 on exchange 5216i
[1662490808.259853][4664:4669] CHIP:EM: Found matching exchange: 5216i, Delegate: 0xffff7800b138
[1662490808.259909][4664:4669] CHIP:EM: CHIP MessageCounter:210541573 not in RetransTable on exchange 5216i
[1662490808.259991][4664:4669] CHIP:SC: Success status report received. Session was established
[1662490808.265731][4664:4669] CHIP:SC: SecureSession[0xffff7800a0a0]: Moving from state 'kEstablishing' --> 'kActive'
[1662490808.265828][4664:4669] CHIP:IN: SecureSession[0xffff7800a0a0]: Activated - Type:2 LSID:60218
[1662490808.265874][4664:4669] CHIP:IN: New secure session activated for device <0000000000000001, 1>, LSID:60218 PSID:12925!
[1662490808.265933][4664:4669] CHIP:CTL: OperationalSessionSetup[1:0000000000000001]: State change 4 --> 5
[1662490808.266063][4664:4669] CHIP:TOO:        cluster 0x0000_0034, attribute: 0x0000_0002, endpoint 0
[1662490808.266137][4664:4669] CHIP:TOO: Sending ReadAttribute to:
[1662490808.266189][4664:4669] CHIP:DMG: SendReadRequest ReadClient[0xffff7800d010]: Sending Read Request
[1662490808.266368][4664:4669] CHIP:IN: Prepared secure message 0xffff78009b78 to 0x0000000000000001 (1)  of type 0x2 and protocolId (0, 1) on exchange 5217i with MessageCounter:124142243.
[1662490808.266426][4664:4669] CHIP:IN: Sending encrypted msg 0xffff78009b78 with MessageCounter:124142243 to 0x0000000000000001 (1) at monotonic time:<PHONE_NUMBER>5B07E1 msec
[1662490808.266699][4664:4669] CHIP:DMG: MoveToState ReadClient[0xffff7800d010]: Moving to [AwaitingIn]
[1662490808.266777][4664:4669] CHIP:EM: Sending Standalone Ack for MessageCounter:32080404 on exchange 5216i
[1662490808.266849][4664:4669] CHIP:IN: Prepared unauthenticated message 0xffff8b7ed968 to 0x0000000000000000 (0)  of type 0x10 and protocolId (0, 0) on exchange 5216i with MessageCounter:210541574.
[1662490808.266902][4664:4669] CHIP:IN: Sending unauthenticated msg 0xffff8b7ed968 with MessageCounter:210541574 to 0x0000000000000000 at monotonic time:<PHONE_NUMBER>5B07E2 msec
[1662490808.267043][4664:4669] CHIP:EM: Flushed pending ack for MessageCounter:32080404 on exchange 5216i
[1662490808.334501][4664:4669] CHIP:EM: Received message of type 0x5 with protocolId (0, 1) and MessageCounter:33205557 on exchange 5217i
[1662490808.334556][4664:4669] CHIP:EM: Found matching exchange: 5217i, Delegate: 0xffff7800d020
[1662490808.334596][4664:4669] CHIP:EM: Rxd Ack; Removing MessageCounter:124142243 from Retrans Table on exchange 5217i
[1662490808.334618][4664:4669] CHIP:EM: Removed CHIP MessageCounter:124142243 from RetransTable on exchange 5217i
[1662490808.334681][4664:4669] CHIP:DMG: ReportDataMessage =
[1662490808.334708][4664:4669] CHIP:DMG: {
[1662490808.334728][4664:4669] CHIP:DMG:        AttributeReportIBs =
[1662490808.334755][4664:4669] CHIP:DMG:        [
[1662490808.334777][4664:4669] CHIP:DMG:                AttributeReportIB =
[1662490808.334812][4664:4669] CHIP:DMG:                {
[1662490808.334835][4664:4669] CHIP:DMG:                        AttributeDataIB =
[1662490808.334861][4664:4669] CHIP:DMG:                        {
[1662490808.334888][4664:4669] CHIP:DMG:                                DataVersion = 0x23494e62,
[1662490808.334914][4664:4669] CHIP:DMG:                                AttributePathIB =
[1662490808.334942][4664:4669] CHIP:DMG:                                {
[1662490808.334970][4664:4669] CHIP:DMG:                                        Endpoint = 0x0,
[1662490808.334998][4664:4669] CHIP:DMG:                                        Cluster = 0x34,
[1662490808.335027][4664:4669] CHIP:DMG:                                        Attribute = 0x0000_0002,
[1662490808.335053][4664:4669] CHIP:DMG:                                }
[1662490808.335082][4664:4669] CHIP:DMG:
[1662490808.335111][4664:4669] CHIP:DMG:                                Data = 9168,
[1662490808.335136][4664:4669] CHIP:DMG:                        },
[1662490808.335164][4664:4669] CHIP:DMG:
[1662490808.335186][4664:4669] CHIP:DMG:                },
[1662490808.335214][4664:4669] CHIP:DMG:
[1662490808.335234][4664:4669] CHIP:DMG:        ],
[1662490808.335260][4664:4669] CHIP:DMG:
[1662490808.335283][4664:4669] CHIP:DMG:        SuppressResponse = true,
[1662490808.335306][4664:4669] CHIP:DMG:        InteractionModelRevision = 1
[1662490808.335326][4664:4669] CHIP:DMG: }
[1662490808.335452][4664:4669] CHIP:TOO: Endpoint: 0 Cluster: 0x0000_0034 Attribute 0x0000_0002 DataVersion: 592006754
[1662490808.335527][4664:4669] CHIP:TOO:   CurrentHeapUsed: 9168
[1662490808.335619][4664:4669] CHIP:EM: Sending Standalone Ack for MessageCounter:33205557 on exchange 5217i
[1662490808.335726][4664:4669] CHIP:IN: Prepared secure message 0xffff8b7ed978 to 0x0000000000000001 (1)  of type 0x10 and protocolId (0, 0) on exchange 5217i with MessageCounter:124142244.
[1662490808.335778][4664:4669] CHIP:IN: Sending encrypted msg 0xffff8b7ed978 with MessageCounter:124142244 to 0x0000000000000001 (1) at monotonic time:<PHONE_NUMBER>5B0827 msec
[1662490808.335929][4664:4669] CHIP:EM: Flushed pending ack for MessageCounter:33205557 on exchange 5217i
[1662490808.336160][4664:4664] CHIP:CTL: Shutting down the commissioner
[1662490808.336224][4664:4664] CHIP:CTL: Stopping commissioning discovery over DNS-SD
[1662490808.336273][4664:4664] CHIP:CTL: Shutting down the controller
[1662490808.336321][4664:4664] CHIP:IN: Expiring all sessions for fabric 0x1!!
[1662490808.336345][4664:4664] CHIP:IN: SecureSession[0xffff7800a0a0]: MarkForEviction Type:2 LSID:60218
[1662490808.336363][4664:4664] CHIP:SC: SecureSession[0xffff7800a0a0]: Moving from state 'kActive' --> 'kPendingEviction'
[1662490808.336381][4664:4664] CHIP:IN: SecureSession[0xffff7800a0a0]: Released - Type:2 LSID:60218
[1662490808.336407][4664:4664] CHIP:FP: Forgetting fabric 0x1
[1662490808.336440][4664:4664] CHIP:TS: Pending Last Known Good Time: 2022-09-01T18:26:37
[1662490808.336592][4664:4664] CHIP:TS: Previous Last Known Good Time: 2022-09-01T18:26:37
[1662490808.336620][4664:4664] CHIP:TS: Reverted Last Known Good Time to previous value
[1662490808.336697][4664:4664] CHIP:CTL: Shutting down the commissioner
[1662490808.336721][4664:4664] CHIP:CTL: Stopping commissioning discovery over DNS-SD
[1662490808.336740][4664:4664] CHIP:CTL: Shutting down the controller
[1662490808.336758][4664:4664] CHIP:CTL: Shutting down the System State, this will teardown the CHIP Stack
[1662490808.337765][4664:4664] CHIP:DMG: IM WH moving to [Uninitialized]
[1662490808.337813][4664:4664] CHIP:DMG: IM WH moving to [Uninitialized]
[1662490808.337836][4664:4664] CHIP:DMG: IM WH moving to [Uninitialized]
[1662490808.337855][4664:4664] CHIP:DMG: IM WH moving to [Uninitialized]
[1662490808.337874][4664:4664] CHIP:DMG: All ReadHandler-s are clean, clear GlobalDirtySet
[1662490808.337952][4664:4664] CHIP:BLE: BleConnectionDelegate::CancelConnection is not implemented.
[1662490808.338707][4664:4664] CHIP:DL: writing settings to file (/tmp/chip_counters.ini-lOme0c)
[1662490808.339630][4664:4664] CHIP:DL: renamed tmp file to file (/tmp/chip_counters.ini)
[1662490808.339719][4664:4664] CHIP:DL: NVS set: chip-counters/total-operational-hours = 0 (0x0)
[1662490808.339745][4664:4664] CHIP:DL: Inet Layer shutdown
[1662490808.339764][4664:4664] CHIP:DL: BLE shutdown
[1662490808.339781][4664:4664] CHIP:DL: System Layer shutdown
ubuntu@ubuntu:~$


taskId using extended ascii char which is invisible when

I have more than 128-97 = 31 spec files to run for single capabilities, in which case the following code
if (queue.specLists.length > 1) {
    taskId += String.fromCharCode(97 + queue.specsIndex); //ascii 97 is 'a'
}

would create a taskId with extended ascii chars and these chars are invisible in our screwdriver which causes lots of confusion.
Maybe create taskId like "#1aa" instead?

I knew supporting sharding was a bad idea :)

Thanks @juliemr !

2.1 is out.


Migrate to envelopes

A transaction is already reported as an envelope - it would be good to do some refactoring & migrate the rest to Envelopes as well, same as in other SDKs.

We'll tackle this in 1.0.
For now, we will do https://github.com/getsentry/team-webplatform-meta/issues/49 as a quick win.


galaxy s3 AOSP browser: view-head MUG title doesn't wrap

This is a real problem if there's a long unbroken MUG name; the ... will be pushed outside the viewport

Won't fix


[Request] Add command option to input Websocket Password

Hey there! I'd like to recommend adding a command option for specifying the websocket password to eliminate the need for the ~/.config/obs-cmd.toml config file. My previous scripts, based on obs-cli, already specified this info using my own global config file and it'd be nice if I could continue this trend as I have 5 live streaming rigs with their own unique configs. Thanks!

Fixed in https://github.com/grigio/obs-cmd/releases/tag/v0.16.1


Intensity predicting model with tensorboard

That's a nice development, @jennmald! I'd love to learn a bit more about the things you are developing here with @jklynch. Could we have a short demo soon?
As a suggestion, before the PRs are merged, maybe it'd be valuable to post some kind of output of the developed features, and some corresponding visualizations? That would demonstrate the evolution of the solutions :).

Thanks @mrakitin ! Sure a short demo sounds great. I will definitely add visuals for upcoming features :)


LocalReader Plugin Not Available in Store

Localhost Plugin Not Available in Store
Description
I've noticed that the localhost plugin, which is essential for the functionality of the chatgpt-local-reader-plugin, is currently not available in the store. This issue is preventing users from fully utilizing the capabilities of the chatgpt-local-reader-plugin.
Steps to Reproduce

Navigate to the plugin store.
Search for the localhost plugin.

Expected Behavior
The localhost plugin should be available for installation from the store.
Actual Behavior
The localhost plugin is not found in the store.
Possible Solution
Please consider adding the localhost plugin back to the store to ensure the chatgpt-local-reader-plugin can function as intended.
Thank you for your attention to this matter.

Hello @josefdc, I apologize for the misunderstanding. This plugin is an extension of the Python http.server module, enabling ChatGPT to directly read local directories. Therefore, it's not feasible to list it in the store.


200.4.0 post release version updates

Upgrade 3rd party dependencies
bump version number for the sdk

@eri9000 I have upgraded the KSP version and created the issue for the Android Studio Iguana bug that is unrelated to the changes in this PR.
https://devtopia.esri.com/runtime/kotlin/issues/3863

Thanks @shubham7109 @ruiqima , merging..


Folder structure for Kinetics train, val and test data

For me it is not quite clear how to structure the video_directory with these datasets for kinetics. Should it be video_directory/{train,val,test}/jpg, so that it can train and validate at the same time ? or is there another folder structure i should adhere to ?

Structure of Kinetics is as the following.
video_directory
class1
video_id1
video_id2
...
class2
...
test
Training and validation sets are located in the same directory.
DIrectory of test set is located in video_directory similar to directories of each class.

Is it normal that training with val and train in the same folder slows down training ? When I had only train videos in one folder, the training seemed to be doing fine; but since training and val data are in the same folder, my training has slowed down (0 accuracy after 10 epochs)

It is the same configuration as the official structure of Kinetics.
Such structure does not affect the training performance
because train_loader just load training videos based on kinetics.json.
So, I cannot understand why your experiment resulted in such thing...


cssobj 2.0 wishlist

I'm thinking of cssobj 2.0, the wish lists:

[ ] bug fix (e.g. $extend not updating)
[ ] drop IE 8
[ ] drop intros
[ ] add $assign
[ ] allow at-rules nest into any level
[ ] performance improvement
[ ] more modern JS feature using IE9+

Related issue: #14

Provide a attach and detach to dom methods will be nice.

Can you provide more details about this feature?

Kind of like JSS provide,  insert the style element or remove it when not need it


Choose catalog/schema modal is always empty

I just upgraded to v4.2.3 CE. When I open a SQL editor and try to click on 'Active catalog/schema' to select the database to use for querying, the 'Choose catalog/schema' modal that opens is always empty. I have several MySQL and Redshift connection and it doesn't work on any of them.

Duplicate of #2348. See fix in 4.2.4.
See #2348 comments for workaround.


InvalidCharacterString

Hi!
using !GetAtt 'MailFromDomain.RecordSets'  I'm getting the next error on CloudFormation console:
 [Invalid Resource Record: 'FATAL problem: InvalidCharacterString (Value should be enclosed in quotation marks) encountered with 'v=spf1 include:amazonses.com ~all'']
Thank you!

Hi Victor,  which version of the provider are you using? It was resolved in version 0.8.2

Hi Mark,
I'm using cfn-ses-provider-0.8.2.zip lambda.
Thank you!

Hi Mark,
I'm using cfn-ses-provider-0.8.2.zip lambda.
Thank you!

I implemented the fix in 0.8.3. Please let me know if it works for you,


App crashes on opening inbox with wrong password

The app crashes after importing an account with the wrong password. After importing you are promted to input the password for the account. Though it seems that its not checked at all at that point so the app can't get the accounts folders and thus crashes when I try to open the inbox from the account list (or the unified inbox).
Expected behavior
Check password and show a wrong password notice either on account import or when opening the inbox.
Actual behavior
The app just crashes.
Steps to reproduce

Import Account from .k9s file
Input wrong password for the account
Try open the inbox of that account from account list/or unified inbox

Environment
K-9 Mail version: 5.700-SNAPSHOT
Android version: 8.0.0
Account type (IMAP, POP3, WebDAV/Exchange): IMAP

Developer note: since the app now starts in the message list, there needs to exist at least one folder that could be displayed.
A proper fix would be to show a placeholder screen when there are no folders yet. For now we fall back to displaying the Outbox folder which is a local folder that should always exist. However, I believe there are still situations where the local Outbox folder isn't created. See issue #4352.

Note:
If it's a dup of #4376, then there is no import of any setting needed!
I created a new Acc, entered just any PW, because I didn't knew it at this moment and there was no option to switch (A other issue?), but I didn't imported any setting (file), so the second Acc is completely new!


Error log in console after first install

Uncaught (in promise) Directory imageretainer/pf2e does not exist or is not accessible in this storage location

I got this after enabling module for the first time.  It stopped appearing after a refresh (probably because it created the directory?).

Fixed, finally. I'm not sure what stopped me from fixing it before.


chore(deps): upgrade dependencies

Upgrades project dependencies. See details in workflow run.

Automatically created by projen via the "upgrade-1.x" workflow

⚪ Backport skipped
The pull request was not backported as there were no branches to backport to. If this is a mistake, please apply the desired version labels or run the backport tool manually.
Manual backport
To create the backport manually run:
backport --pr 710

Questions ?
Please refer to the Backport tool documentation


Random color not working

Describe the bug
Passing "random" as the value for "color" to a light node often fails. A few clicks on the inject node in the supplied flow shows that this long-standing bug is still present in 2.7.0.
Flow to Reproduce
[{"id":"c6b31d5b.017bb","type":"inject","z":"e483373d.aebfb8","name":"","topic":"","payload":"{\"on\":true,\"color\":\"random\"}","payloadType":"json","repeat":"","crontab":"","once":false,"onceDelay":0.1,"x":170,"y":320,"wires":[["c9bfe00e.6ec4f"]]},{"id":"c9bfe00e.6ec4f","type":"hue-light","z":"e483373d.aebfb8","name":"Floor Lamp","bridge":"d75a339d.b8a97","lightid":"9","colornamer":true,"skipevents":false,"x":310,"y":320,"wires":[[]]},{"id":"d75a339d.b8a97","type":"hue-bridge","z":"","name":"Hue Chez Nous","bridge":"<IP_ADDRESS>","key":"V7BxU8fI9bL2Pz7Mun4hBLG3g4CBTeaorkAc1uAH","interval":"3000","disableupdates":false}]

Expected behavior
Passing "random" as the value for "color" should work reliably.
Screenshots

Please complete the following information:

NodeRED version: 1.0.6
NodeJS version: 12.16.3
Device running NodeRED: Raspberry Pi 3B+ (Raspbian buster)

Additional context
In case it jogs any thoughts about a fix, here is the jsonata expression I use as a work-around for this bug:
(
   $r:=$floor($random()*256);
   $g:=$floor($random()*256);
   $b:=$floor($random()*256);
   $l:=$floor(0.2126*$r + 0.7152*$g + 0.0722*$b);
   {
       "on":true,
       "rgb":[$r,$g,$b],
       "brightnessLevel":$l
   }
)

Do you have the same issues with “any” instead of “random” for the parameter?

This weird error is finally fixed with the latest release. You can use "random" as well as "any" or "whatever" now as a color name to get a random color.

This error still occurs in 2.8.1
[
    {
        "id": "a3b87cd4.e67e9",
        "type": "inject",
        "z": "93ed4ec.16204b",
        "name": "8:{\"on\":true,\"color\":\"any\",\"brightness\":100}",
        "topic": "8",
        "payload": "{\"on\":true,\"color\":\"any\",\"brightness\":100}",
        "payloadType": "json",
        "repeat": "",
        "crontab": "",
        "once": false,
        "onceDelay": 0.1,
        "x": 200,
        "y": 240,
        "wires": [
            [
                "cf7c76e6.8b8c48"
            ]
        ]
    },
    {
        "id": "cf7c76e6.8b8c48",
        "type": "hue-group",
        "z": "93ed4ec.16204b",
        "name": "",
        "bridge": "5a3e3ef6.ce10a",
        "groupid": "",
        "colornamer": true,
        "skipevents": false,
        "x": 450,
        "y": 240,
        "wires": [
            []
        ]
    },
    {
        "id": "5a3e3ef6.ce10a",
        "type": "hue-bridge",
        "z": "",
        "name": "Hue Chez Nous",
        "bridge": "<IP_ADDRESS>",
        "key": "vq9C66nmN2hrToNOMMgaxi90G8ExsyEHKDymxDKR",
        "interval": "3000",
        "disableupdates": false
    }
]


Fix #1436 - compatibity with gem-compiler.

The extconf.rb clean task removes most of the files, that are used only while build. However this broke gem-compiler, because it removed the archives as well, although they are part of the gemspec.
With this patch the archives are kept on disk. The downside is, that it increases the disk space used by nokogiri from 21MB to 30MB after install.
An alternative is gem-compiler's option --prune, as described here: https://github.com/luislavena/gem-compiler/issues/12

I think the --prune option to gem-compiler is a acceptable solution, so that we can close this PR.


Use config { mode: 'usage' } and the corejs path was not found

Describe the bug

Use config { mode: 'usage' } and the corejs path was not found

Input code
No response
Config
{
    test: /\.(js|jsx)$/,
    include: [/(src)/, /(node_modules(\/|\\)@seeyon)/],
    use: [
      {
        loader: 'swc-loader',
        options: {
          "jsc": {
            "parser": {
                "syntax": "ecmascript",
                "jsx": true,
            },
        },
        "isModule": true,
          "env": {
              "targets": "Chrome >= 65",
              mode: 'usage',
              "coreJs": '3.26.1'
          }
        },
      },
    ],
},

Playground link
No response
Expected behavior

Finding correct core-js path like 'core-js/modules/web.url-search-params.js' and the wepack building pass
My node_modules's core-js file

Actual behavior

The webpack building  error
Why are there more '. size' ？

Version
"@swc/core": "1.3.41", "@swc/helpers": "0.4.14", "swc-loader": "0.2.3"
Additional context

webpack version

"webpack": "5.52.1",
"webpack-cli": "4.10.0",

Note that web.url-search-params.size was added in<EMAIL_ADDRESS>and should not be injected with "coreJs": '3.26.1'.

It was work, thanks very much !


Additional tests for distributions

Summary
Additional tests for distributions to increase coverage. All tests pass with the current codebase.
Tests

bernoulli_logit_lpmf involves a cutoff, continuity around the cutoff is tested
inv_gamma_lpmf and weibull_lpmf had no tests for derivatives. A new test testing all derivatives  against values precomputed byt Mathematica was added.
adapted the tests from #1497 to neg_binomial_lpmf (test against precomputed values from Mathematica, test against complex step, testing continuity at cutoff for alpha, testing extreme values of alpha)

Side Effects
None
Checklist

[x] Math issue: I decided not to open an math issue for this, as it seemed like clutter. Will open, if desired.

[x] Copyright holder: Institute of Microbiology of the Czech Academy of Sciences
The copyright holder is typically you or your assignee, such as a university or company. By submitting this pull request, the copyright holder is agreeing to the license the submitted work under the following licenses:
- Code: BSD 3-clause (https://opensource.org/licenses/BSD-3-Clause)
- Documentation: CC-BY 4.0 (https://creativecommons.org/licenses/by/4.0/)

[ ] the basic tests are passing

unit tests pass (to run, use: ./runTests.py test/unit)
header checks pass, (make test-headers)
docs build, (make doxygen)
code passes the built in C++ standards checks (make cpplint)

[x] the code is written in idiomatic C++ and changes are documented in the doxygen

[x] the new changes are tested

This PR needs a merge with recent develop to avoid failure on the upstream. I apologize, there was a lot of churn with this flattening...

@rok-cesnovar I merged the develop, but upstream still fails on CmdStan >> Linux interface tests with MPI with
src/cmdstan/command.hpp:55:50: fatal error: stan/math/prim/functor/mpi_cluster.hpp: No such file or directory

I believe this is not related to this PR and not sure what to do about it.
@bob-carpenter  May I ask for review on this? It is almost the same tests as written for #1497.

Yeah, that is weird. On develop this file exists (see https://github.com/stan-dev/math/blob/develop/stan/math/prim/functor/mpi_cluster.hpp), so not usre what is going on. Will monitor.

Sure---I can review this.


Reorder addition of pinot table views API

Move addition of pinot tables views below the existing list.
Keeping it clustered with other GET calls hides existing paths.
Testing: manual

Current coverage is 64.30% (diff: 100%)

Merging #835 into master will increase coverage by <.01%

@@             master       #835   diff @@
==========================================
  Files           727        727
  Lines         34123      34123
  Methods           0          0
  Messages          0          0
  Branches       5219       5219
==========================================
+ Hits          21941      21943     +2
- Misses        10637      10639     +2
+ Partials       1545       1541     -4

Powered by Codecov. Last update 85f2416...31b52c2


Guide for adding new plugin

emqttd-relx is being used to make a build of the broker. It seems there is no instruction how to add new plugin to emqttd-relx and build it. Can someone help?

1 step： Makefile add deps  new plugin
2 step：cp  plugin.conf to etc/plugins/
3 step：relx.config add {plugin_name, load}

@turtleDeng It works. Thanks!

I updated the Plugin Development Guide : http://emqtt.io/docs/v2/plugins.html#plugin-development-guide


Add important admonition about using System.Decimal POCO property types

Bump AsciiDoctNet to support additional asciidoc syntax
Closes #2463

ported to master and 5.x


Add a comm target registry

cc @jdfreder @jasongrout @SylvainCorlay

I released a new jupyter-js-utils with loadClass, and updated the API here.

Sweet

These changes look great to me.  I think we should merge and iterate, if needed.

@blink1073 - since this is a breaking change, perhaps bumping to 0.5.0 is in order?


ERROR Mysql Integrate

After try to integrate to Mysql, I receive ::
SyntaxError: Unexpected end of input
Anyone can help me?

Someone can have Query file Upload with Mysql Download?

Please don't misuse the pull request feature.


Teding/feat/compression

Use actual Lua class syntax. (I finally read up on Lua 🎉)
Avoids recording duplicate image sequences.

Eeep!! I forgot to close the files I opened. Also check if any file opens.

@thomaseding Thanks for updating. Going to pull it down later today and do another pass through.


auto keyword not supported in C++03

https://github.com/Rantanen/node-mumble/issues/69

Thanks!
Version 0.1.9 published to npm.


Feature/ShareMessage

Implement method share message to zalo
Should I create a PR to dev or master?

@metajet98 Thanks for your PR


Update the tooltip 'Dequeue' to 'Dequeue Message'

Storage Explorer Version: 1.8.1_20190513.2
Platform/OS: Linux Ubuntu/macOS High Sierra/Windows 10
Architecture: ia32/x64
Commit: 41005d14
Regression From: Not a regression
Steps to reproduce:

Expand a storage account -> Queues -> Create a new queue.
Hover the mouse on 'Dequeue Message' button in toolbar and check the tooltip.

Expect Experience:
Show 'Dequeue Message' as the tootip.
Actual Experience:
Show 'Dequeue' as the tootip.

Fix in PR.

Fix merged into master.

The fix has been merged to the npm package's source file. It needs to be published.

Hi @JasonYeMSFT Thanks for your update!
Verified this issue on the latest build 20190619.4. It has been fixed. So we close it!


Use native CLI functions for slave node management rather than groovy

I'd like to be able to create jnlp slaves with minimal security privileges on the master, and ideally through http mode instead of remoting.
Matrix-based security supports granting just the rights to manage nodes. The cli has specific commands for all of the node management actions. It should be rather straight forward.
Currently though, all the actions are performed with groovy code, which means the user doing them needs the Overall/RunScripts right. As documented by Matrix-based Security, "RunScripts allows executing arbitrary code in the context of any (Jenkins internal) user, including the internal SYSTEM user."
The current approach also requires the cli be invoked in -remoting mode rather than -http mode. Remoting is deprecated as a major security vulnerability and recommended to be turned off.
Remoting is "inherently vulnerable to remote code execution bugs, even “preauthentication” exploits (by anonymous users able to physically access the Jenkins network)."

On initial look getting slave JNLP secret is not possible with native CLI functions so this probably needs changes on Jenkins side as well


Nested ContentDialog leads crash System.Runtime.InteropServices.COMException

Describe the bug
I tried to display the one content dialog inside another content dialog (Nested ContentDialog), but when i open the second content dialog it leads to a crash.
Steps to reproduce the bug

Run the Nested_ContentDialog.zip sample and click "Open dialog 1".
First content dialog will be displayed.
Now, click "Open dialog 2" to display the second content dialog.
Crash occurs.

Expected behavior
Second content dialog should be displayed.
Screenshots

NuGet package version
WinUI 3 - Windows App SDK 1.0 (If you're seeing your issue in older previews of WinUI 3, please try this release)
Windows app type

[ ] UWP
[X] Win32

Device form factor
Desktop
Windows version
October 2020 Update (19042)
Additional context
No response

Hi @gabbybilka,
I am also facing the same issue when loading custom Flyout instead of a second content dialog.
Regards,
SaiGanesh Sakthivel

I encounter the same issue when trying to use a another pre-made component which has a ContentDialog built in - this component can't be used inside another ContentDialog.

As far as I can see this is still not resolved with the current release of WinUI (1.3). Any updates on this?

Any update on this?


LORM

Let's implement LORM metric.
L. Etzkorn and H. Delugach, “Towards a semantic metrics suite
for object-oriented design,” in Technology of Object-Oriented Languages
and Systems, 2000. TOOLS 34. Proceedings. 34th International
Conference on. IEEE, 2000, pp. 71–80.
No PDF available :(
http://ieeexplore.ieee.org/document/868960/
It's explained here, briefly: http://www.math.md/files/csjm/v25-n1/v25-n1-(pp44-74).pdf

Hello,
so how we define

set of concepts

of method? Can we assume that it is all local and class variables? And if two methods use the same field of the class we can collect it is as conceptual relation between methods? Do we adding static method calls to that?
Overall, it is an interesting metric. It is suppose to show the correlated methods with each other. Another interesting thing is - how much does it related to quality?