Webhook/slack features failing to send.

I am having trouble getting the messaging features of sentinl to work (email, slack, webhook etc.). I am able to send a webhook for example to the slack hooks api via a curl command but my watcher configuration does not send the desired message after execution.
Many thanks.
System Details
Versions

Type
Version

Kibana
6.2.4

Elasticsearc
6.2.3

Server OS
centos 7.6

Browser
Chrome

Original Install Method
Downloaded zip file for sentinl and ran ./kibana-plugin install file:///home/user/downloads/sentinl-6.2.4.zip
Bug Details
Bug Description
Steps to Reproduce

Expected Behavior
Sample of data you have in Elasticsearch

Full Watcher JSON
{
  "actions": {
    "Webhook_04bd55aa-2deb-4b6e-bf0b-2a8b859fe686": {
      "name": "Webhook",
      "throttle_period": "1m",
      "webhook": {
        "priority": "low",
        "stateless": false,
        "method": "POST",
        "host": "https://hooks.slack.com",
        "port": "80",
        "path": "/services/XXXXXXXXXXXXXXX/XXXXXXXXXXXXX/XXXXXXXXXXXXXXXXXXXXX",
        "body": "{\n  \"watcher\": \"{{watcher.title}}\",\n  \"payload_count\": \"{{payload.hits.total}}\"\n}",
        "params": {
          "watcher": "{{watcher.title}}",
          "payload_count": "{{payload.hits.total}}"
        },
        "headers": {
          "Content-Type": "application/json"
        },
        "auth": "",
        "message": "",
        "use_https": false
      }
    }
  },

Screenshots (if relevant)
Errors in Browser Console (if relevant)
Kibana verbose logs

#### Kibana logs and/or server output (attached if relevant)
{"type":"response","@timestamp":"2019-01-17T10:54:36Z","tags":[],"pid":43306,"method":"get","statusCode":304,"req":{"url":"/ui/favicons/favicon-32x32.png","method":"get","headers":{"host":"<IP_ADDRESS>:5601","connection":"keep-alive","user-agent":"Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/71.0.3578.98 Safari/537.36","accept":"image/webp,image/apng,image/*,*/*;q=0.8","referer":"http://<IP_ADDRESS>:5601/app/sentinl","accept-encoding":"gzip, deflate","accept-language":"en-US,en;q=0.9","if-none-match":"\"8e183c2e644fb050707d89402e1f7a120a95e4d2\"","if-modified-since":"Mon, 03 Dec 2018 10:15:49 GMT"},"remoteAddress":"<IP_ADDRESS>","userAgent":"<IP_ADDRESS>","referer":"http://<IP_ADDRESS>:5601/app/sentinl"},"res":{"statusCode":304,"responseTime":3,"contentLength":9},"message":"GET /ui/favicons/favicon-32x32.png 304 3ms - 9.0B"}
{"type":"response","@timestamp":"2019-01-17T10:54:36Z","tags":[],"pid":43306,"method":"get","statusCode":304,"req":{"url":"/ui/favicons/favicon-16x16.png","method":"get","headers":{"host":"<IP_ADDRESS>:5601","connection":"keep-alive","user-agent":"Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/71.0.3578.98 Safari/537.36","accept":"image/webp,image/apng,image/*,*/*;q=0.8","referer":"http://<IP_ADDRESS>:5601/app/sentinl","accept-encoding":"gzip, deflate","accept-language":"en-US,en;q=0.9","if-none-match":"\"13b869be5df4bdc56920edc16a28e67a7c08203b\"","if-modified-since":"Mon, 03 Dec 2018 10:15:49 GMT"},"remoteAddress":"<IP_ADDRESS>","userAgent":"<IP_ADDRESS>","referer":"http://<IP_ADDRESS>:5601/app/sentinl"},"res":{"statusCode":304,"responseTime":3,"contentLength":9},"message":"GET /ui/favicons/favicon-16x16.png 304 3ms - 9.0B"}
{"type":"log","@timestamp":"2019-01-17T10:54:38Z","tags":["plugin","debug"],"pid":43306,"message":"Checking Elasticsearch version"}
{"type":"ops","@timestamp":"2019-01-17T10:54:39Z","tags":[],"pid":43306,"os":{"load":[1.93994140625,1.7060546875,1.11767578125],"mem":{"total":3965587456,"free":140013568},"uptime":8023094},"proc":{"uptime":1116.996,"mem":{"rss":126062592,"heapTotal":100118528,"heapUsed":84131720,"external":747232},"delay":0.5439004898071289},"load":{"requests":{"5601":{"total":6,"disconnects":0,"statusCodes":{"200":2,"304":4}}},"concurrents":{"5601":2},"responseTimes":{"5601":{"avg":6.333333333333333,"max":20}},"sockets":{"http":{"total":0},"https":{"total":0}}},"message":"memory: 80.2MB uptime: 0:18:37 load: [1.94 1.71 1.12] delay: 0.544"}
{"type":"response","@timestamp":"2019-01-17T10:54:39Z","tags":[],"pid":43306,"method":"post","statusCode":200,"req":{"url":"/api/sentinl/watcher/6cd7e660-18d5-11e9-a974-0923c2203d1a","method":"post","headers":{"host":"<IP_ADDRESS>:5601","connection":"keep-alive","content-length":"0","accept":"application/json, text/plain, */*","origin":"http://<IP_ADDRESS>:5601","kbn-version":"6.2.4","user-agent":"Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/71.0.3578.98 Safari/537.36","referer":"http://<IP_ADDRESS>:5601/app/sentinl","accept-encoding":"gzip, deflate","accept-language":"en-US,en;q=0.9"},"remoteAddress":"<IP_ADDRESS>","userAgent":"<IP_ADDRESS>","referer":"http://<IP_ADDRESS>:5601/app/sentinl"},"res":{"statusCode":200,"responseTime":8,"contentLength":9},"message":"POST /api/sentinl/watcher/6cd7e660-18d5-11e9-a974-0923c2203d1a 200 8ms - 9.0B"}
{"type":"log","@timestamp":"2019-01-17T10:54:39Z","tags":["debug","Sentinl","get_elasticsearch_client"],"pid":43306,"message":"auth via Kibana server elasticsearch plugin"}
{"type":"log","@timestamp":"2019-01-17T10:54:39Z","tags":["debug","Sentinl","get_elasticsearch_client"],"pid":43306,"message":"auth via Kibana server elasticsearch plugin"}
{"type":"log","@timestamp":"2019-01-17T10:54:39Z","tags":["info","Sentinl","watcher_handler"],"pid":43306,"message":"executing"}
{"type":"log","@timestamp":"2019-01-17T10:54:39Z","tags":["warning","Sentinl","watcher_handler"],"pid":43306,"message":"Siren federate: \"elasticsearch.plugins\" is not available when running from kibana: Error: Unknown config key: investigate_core.clusterplugins"}
{"type":"log","@timestamp":"2019-01-17T10:54:39Z","tags":["debug","Sentinl","watcher_handler"],"pid":43306,"message":"condition: {\n  \"script\": {\n    \"script\": \"payload.aggregations.dateAgg.buckets.some(b => b.doc_count>=0)\"\n  }\n}"}
{"type":"log","@timestamp":"2019-01-17T10:54:39Z","tags":["info","Sentinl","watcher_handler"],"pid":43306,"message":"successfully applied condition"}
{"type":"log","@timestamp":"2019-01-17T10:54:39Z","tags":["debug","Sentinl","get_elasticsearch_client"],"pid":43306,"message":"auth via Kibana server elasticsearch plugin"}
{"type":"log","@timestamp":"2019-01-17T10:54:39Z","tags":["debug","Sentinl"],"pid":43306,"message":"processing action"}
{"type":"log","@timestamp":"2019-01-17T10:54:39Z","tags":["info","Sentinl","watcher_handler"],"pid":43306,"message":"successfuly executed"}
{"type":"response","@timestamp":"2019-01-17T10:54:39Z","tags":[],"pid":43306,"method":"post","statusCode":200,"req":{"url":"/api/sentinl/watcher/_execute","method":"post","headers":{"host":"<IP_ADDRESS>:5601","connection":"keep-alive","content-length":"1433","accept":"application/json, text/plain, */*","origin":"http://<IP_ADDRESS>:5601","kbn-version":"6.2.4","user-agent":"Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/71.0.3578.98 Safari/537.36","content-type":"application/json;charset=UTF-8","referer":"http://<IP_ADDRESS>:5601/app/sentinl","accept-encoding":"gzip, deflate","accept-language":"en-US,en;q=0.9"},"remoteAddress":"<IP_ADDRESS>","userAgent":"<IP_ADDRESS>","referer":"http://<IP_ADDRESS>:5601/app/sentinl"},"res":{"statusCode":200,"responseTime":336,"contentLength":9},"message":"POST /api/sentinl/watcher/_execute 200 336ms - 9.0B"}
{"type":"log","@timestamp":"2019-01-17T10:54:40Z","tags":["error","Sentinl"],"pid":43306,"message":"fail to ship webhook, Error: getaddrinfo ENOTFOUND https://hooks.slack.com https://hooks.slack.com:80"}
{"type":"log","@timestamp":"2019-01-17T10:54:40Z","tags":["plugin","debug"],"pid":43306,"message":"Checking Elasticsearch version"}
{"type":"log","@timestamp":"2019-01-17T10:54:43Z","tags":["plugin","debug"],"pid":43306,"message":"Checking Elasticsearch version"}
{"type":"ops","@timestamp":"2019-01-17T10:54:44Z","tags":[],"pid":43306,"os":{"load":[1.78466796875,1.677734375,1.11181640625],"mem":{"total":3965587456,"free":135213056},"uptime":8023099},"proc":{"uptime":1121.996,"mem":{"rss":127512576,"heapTotal":101167104,"heapUsed":85076616,"external":789625},"delay":0.4967002868652344},"load":{"requests":{"5601":{"total":2,"disconnects":0,"statusCodes":{"200":2}}},"concurrents":{"5601":2},"responseTimes":{"5601":{"avg":171.5,"max":336}},"sockets":{"http":{"total":0},"https":{"total":0}}},"message":"memory: 81.1MB uptime: 0:18:42 load: [1.78 1.68 1.11] delay: 0.497"}

#### Any additional information

The author solved this problem


dose esp32-c3 support GPIO wakeup? (IDFGH-5160)

Hi
I am test the deep sleep in ESP32-C3, and can not run deep sleep example with external io wakeup

Any comment is welcome


Custom messages

Hello, it there any way to make this package work with custom messages?

change folder to your customized package,  compile your own messages and "source install/setup.bash". Then you can execute the script in the current terminal


Use my API key to check if I know the recipe

This one is probably an "I'd love a pull request" issue; it also opens potential for discussion of cross-platform configuration files, which is usually not a favorite topic. Opening this so it's available for discussion.
I might work on this when I'm more comfortable with Rust - I do not know enough yet to get file caching for #7 working successfully.

Some issues I've run into w/a first step implementation.
The API appears to not list automatically unlocked recipes; so we'll have to check for available chars of an appropriate crafting level as well. The API does list if a recipe is an auto unlock, at what level, for what disciplines, so there's that at least.
I've run into situations where I bought a recipe to craft something, only to learn that I needed an inscription recipe as well; so we need to check all recursive recipes.
I am uncertain how recipe data should be shown in the large table view; we have the data, so we may as well show it to influence higher level decisions.
This would be a useful precursor to #8.


Build failure with opentelemetry dependency: cannot find package "."

Hi, first off big fan of your work and thank you for making a much nicer way to build go binaries. So much nicer as a developer than having to figure out the current SHA all the time :)
I recently encountered an issue where gomod2nix seems to result in a build failure when I import a specific dependency, go.opentelemetry.io/otel/exporters/otlp/otlptrace. The build failure is as follows:
$ nix build .
warning: Git tree '/Users/pd/code/gomod2nix-failure-repro' is dirty
error: builder for '/nix/store/92rq9r8nv8nhpdl0z9dnic98hhizmw4y-demo-0.0.1.drv' failed with exit code 1;
       last 10 log lines:
       > unpacking sources
       > unpacking source archive /nix/store/x5s2b55ans4iz9alw39n3zw95bp2515g-1bgxmfm63niqndrby5yxqb55dlm97ncz-source
       > source root is 1bgxmfm63niqndrby5yxqb55dlm97ncz-source
       > patching sources
       > updateAutotoolsGnuConfigScriptsPhase
       > configuring
       > building
       > Building subPackage .
       > vendor/go.opentelemetry.io/otel/exporters/otlp/otlptrace/exporter.go:22:2: cannot find package "." in:
       > 	/private/tmp/nix-build-demo-0.0.1.drv-0/1bgxmfm63niqndrby5yxqb55dlm97ncz-source/vendor/go.opentelemetry.io/otel/exporters/otlp/internal
       For full logs, run 'nix log /nix/store/92rq9r8nv8nhpdl0z9dnic98hhizmw4y-demo-0.0.1.drv'.
$ nix log /nix/store/92rq9r8nv8nhpdl0z9dnic98hhizmw4y-demo-0.0.1.drv
@nix { "action": "setPhase", "phase": "unpackPhase" }
unpacking sources
unpacking source archive /nix/store/x5s2b55ans4iz9alw39n3zw95bp2515g-1bgxmfm63niqndrby5yxqb55dlm97ncz-source
source root is 1bgxmfm63niqndrby5yxqb55dlm97ncz-source
@nix { "action": "setPhase", "phase": "patchPhase" }
patching sources
@nix { "action": "setPhase", "phase": "updateAutotoolsGnuConfigScriptsPhase" }
updateAutotoolsGnuConfigScriptsPhase
@nix { "action": "setPhase", "phase": "configurePhase" }
configuring
@nix { "action": "setPhase", "phase": "buildPhase" }
building
Building subPackage .
vendor/go.opentelemetry.io/otel/exporters/otlp/otlptrace/exporter.go:22:2: cannot find package "." in:
        /private/tmp/nix-build-demo-0.0.1.drv-0/1bgxmfm63niqndrby5yxqb55dlm97ncz-source/vendor/go.opentelemetry.io/otel/exporters/otlp/internal

The opentelemetry project / packages are quite complex and involve URLs that don't match the resolved package names, complicated versioning, etc. Here are some helpful links:

godoc page https://pkg.go.dev/go.opentelemetry.io/otel/exporters/otlp/otlptrace#section-readme
.mod file https://github.com/open-telemetry/opentelemetry-go/blob/main/exporters/otlp/otlptrace/go.mod
line exporter.go:22 with the broken import https://github.com/open-telemetry/opentelemetry-go/blob/main/exporters/otlp/otlptrace/exporter.go#L22

In order to make this easier to debug, here is a repository with full information on the problem and steps to repro. I hope it helps. If you could even give me some advice on how to debug this sort of thing, I'm happy to try to learn.

Ah, this is a duplicate of https://github.com/nix-community/gomod2nix/issues/20


DataTables warning: table id=DataTables_Table_0 - Ajax error. For more information about this error, please see http://datatables.net/tn/7

Hello.  I have a problem, I am not sure if anyone here can help me, as I am new to coding etc. Please forgive for lack of knowledge...
I download a website on HTTrack which I placed my:
user-agent="Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/89.0.4389.114 Safari/537.36" and
Cookie: PHPSESSID=2j0hb3liiv5km4grhvcmn6q933  as and my username and pass word.
The problem here is this: After downloading on my computer and opened the local website. I got and error which states:
"DataTables warning: table id=DataTables_Table_0 - Ajax error. For more information about this error, please see http://datatables.net/tn/7"
I tried following the steps on the line provided, in Google Chrome http://datatables.net/tn/7 but no avail. Next
I followed the steps and source to the problem: Inspect>>Network>>XHR>>Name.
Under the "Name" tab, There are 8 on the list. Each name has the same initiator. Which is: "jquery-1.9.1.min.js:5"
Please view photo:
https://imgur.com/a/1oIUw1G
Even the "Response tab" "Failed to load response data" on all listings.
I am not sure how to move forward from here. I did some researched, which pointed to the 400 and 500 common errors.
I am sorry for the long texts...
As I pasted the "jquery-1.9.1.min.js:5" code in https://jsonlint.com I came up with the following errors.
Error: Parse error on line 1: /*! jQuery v1.9.1 |  ^ Expecting 'STRING', 'NUMBER', 'NULL', 'TRUE', 'FALSE', '{', '[', got 'undefined'
I have no idea what that means and which part of the code to begin with. "pulling my hair out right now"...
What do you suggest I do to move forward? How can this problem fix?
I am afraid and terrify to pasted the whole code here. I am not sure if it was a ridiculous idea to view the code in the link below:
https://drive.google.com/file/d/1pw7ik_WtfeuvzwM9lBE76kW4w3xiR5K1/view?usp=sharing
Thanks in advance
I cannot drink no more caffeine

It seems like this is a difficult task to accomplish...

Hello,
if you have the Debug mode from laravel on true you can click on "OK" in the modal field.-After you did this the response in the Network tab says you where the error occured. It would help us here if you can provide us your controller code and your view code. In your google drive is only a jquery file which has nothing to do with this package. Also please consider to use the issue template next time :-)

Hello. schonhoff, I am really thankful for your feedback. I do...
I am sorry for my lack of knowledge with the jquery file.
Please, if you are willing. Below is the website information. This may have the controller code requested:
https://drive.google.com/file/d/14uvvldLcLIkLwstg9K8KenQZqYLbiqLz/view
It my seems like I may have knowledge about "Debug mode from laravel on true you can click "OK"".
I am sorry. But how can I do that?
What is the steps to follow your tuition?
Thanks in advance
Corrie

Hi,
here is how you are handling the debug mode on Laravel:
https://laravel.com/docs/8.x/configuration#debug-mode
You can put your code in here. Just use the "insert code" control on top of the editor. I don't want to download a rar file nor am I willing to visit a google drive for security reasons.
Try to open another issue, copy the text from editor in here and fill out the form given there :-) It will help us to understand your problem. There is also a mask to handle code inline here.
In your screenshot from the first request there is a CORS error. I think your server isn't set up correctly and I would guess that you aren't even using Laravel. But you can provide the things asked for in the "new issue" -template.

Thanks schonhoff for your shift response.
I am sorry schonhoff, I was hesitant to write back to you, openly for others to read.
I was not sure what is "Laravel"? and How can Laravel can help me? As I have no understanding of coding.
I am not even clear, if Laravel is built installed on my windows 10 computer.
I apologies schonhoff. I may have to get sometime to really understand  and research some more on what you are saying. Concerning, The code you want me to paste, Laravel, and CORS error.
As a baby, the only thing I can feed on is milk. I may need someone to help with the diapers and the burping.
What video you recommend to watch base on your explanations?
Thanks in advance for your time and consideration.
Cheers

Hello,
(Forgive for weak English when I'm not English speaker)
It seem like that the website you downloaded is using DataTables library, which is a library built in jQuery.
One of its features that its calling some data from anywhere and format it like a table with a lot of advanced features this call done via AJAX call.
But actually this call failed because you haven't any data to return " it is just a downloaded template and not customized yet".
So you have to read more about JavaScript then jQuery then DataTables.
BTW This issue dose not belong to Laravel.
Thank you.

Thank you Momenoor. I was waiting for a response to move forward.
I am sorry, what do you suggest to do to move forward? How can I get the data download?
I am not sure if you have any suggestions or recommendations..
Thanks Momenoor

Hi,
Could you please clarify what kind of data you want to download (is it a data on a page? Or website template? Or what exactly data you need?).
The issue is not clear to me.
I will do my best to provide you with what you need.
Thanks

Thanks Momenoor for your swift responce. Yes I am trying to download a website template.
I am not sure whose recommendation I should follow. Yours or schonhoff.
Thanks again

Hi,
It is depend on your needs,( where GitHub is a Developers Community )
Are you a web developer? So you must follow schonhoff for advanced level "Backend", or my first comment for basic to solve your current issue "frontend".
If you just want to download the website so no need to dive into the code.
And you must share the files you downloaded to help on this.

Thank you Momenoor. I seems like you are really generous with your time and I really appriceate your effort to help me solved my problems.
Below is the download files. the problem with such files are this:
I can only view the first page. Every time I tried to click on any other links, I automatically is transferred to the login page.
I am sorry Momenoor. I am not sure how to bypass this? Then again, I am not even sure, if I did the right thing.
How can you point me to the right direction?
I appreciate your wisdom Momenoor
Cheers
Corrie
Push Button.zip

I'm not sure if what you are trying to do is legal or not, but after reviewing the files you send, sadly I'm must tell you that it's need a hard work to bypass login screen.
I'm sorry to tell you I can't help.
Best wishes for you

Momenoor. I am sorry. I currently have my username and password. Is it a ridiculous idea that it can not work?

For offline version of files no way to make login, since there is no connection with database on live server.

Hello Momenoor & schonhoff Thanks for your feedback and contribution.
I did not know there were so many issues to fix this. I decided not to move forward with the site again.
Thanks again
Corrie


Multiple session with the same Microsoft Account in Windows 11 Enterprise

In windows 11 Enterprise, I can't login by different device which use the same microsoft account at the same time. Pls help.

Closed because of missing answer


SectionList Performance iOS

Is this a bug report?
Yes

Have you read the Contributing Guidelines?
Yes
Environment
Environment:
OS: macOS High Sierra 10.13.1
Node: 8.0.0
Yarn: 1.3.2
npm: 5.5.1
Watchman: 4.7.0
Xcode: Xcode 9.1 Build version 9B55
Android Studio: 2.3 AI-162.4069837
Packages: (wanted => installed)
react: ^16.1.1 => 16.1.1
react-native: ^0.50.3 => 0.50.3
Target Platform: iOS (11.1)
Steps to Reproduce

We're having quite a big app completely build with react-native. For navigation we're using react-navigation and for the store redux. As you will see in the following .gif and when you run my example, the performance of our SectionList is really bad. To mention, it's a long list with different sections, sectionheaders and so on, but I can't find the cause of this really bad performance. If I'm testing the app with the PerfMonitor, I'm seeing the UI Thread is dropping frames, the JS thread doesn't have a problem. If I understand things right, then this means that this is not a bug in my JS integration. Is this suggestion right?
(to clarify the performance is not only bad in debug mode, it's also bad on release and on every device I've tested it. (iPad, iPhone 6, iPhone 7))
So steps to reproduce:

Build a large SectionList with different sections
Scroll through the list
Press on items

Expected Behavior

The SectionList should scroll smooth up and down, items can get pressed, just as you would expect it from an app you already know.
Actual Behavior

Really bad performance by scrolling up and down, stocking transitions
Debug Mode with PerfMonitor:

Release Mode:

(same happens on every test device)
Reproducible Demo

A snack doesn't make really sense in this case, so I uploaded the relevant parts to a new github repository. You can get it here https://github.com/vanBrunneren/Bug.git (obviously some parts are removed because I can't show the full code, but the example should show the problem). To see the problem just download and install my demo, start the app, and scroll through it.

Additional information
Maybe a list of my dependency is also helping:
"dependencies": {
    "bugsnag-react-native": "^2.6.0",
    "prop-types": "^15.5.10",
    "react": "^16.1.1",
    "react-native": "^0.50.3",
    "react-native-camera": "^0.10.0",
    "react-native-carousel": "^0.10.0",
    "react-native-device-info": "^0.11.0",
    "react-native-fabric": "^0.5.1",
    "react-native-facebook-login": "^1.6.0",
    "react-native-google-analytics-bridge": "^5.3.3",
    "react-native-htmlview": "^0.12.1",
    "react-native-maps": "^0.17.1",
    "react-native-push-notification": "^3.0.1",
    "react-native-qrcode-scanner": "^0.0.23",
    "react-native-radio-buttons": "^1.0.0",
    "react-native-render-html": "^3.5.1",
    "react-native-send-intent": "^1.0.21",
    "react-native-swiper": "^1.5.13",
    "react-native-tab-view": "^0.0.70",
    "react-native-vector-icons": "^4.4.2",
    "react-navigation": "^1.0.0-beta.21",
    "react-redux": "^5.0.6",
    "redux": "^3.6.0",
    "redux-logger": "^3.0.6",
    "redux-thunk": "^2.2.0"
  },
  "devDependencies": {
    "babel-jest": "21.2.0",
    "babel-preset-react-native": "4.0.0",
    "jest": "21.2.1",
    "react-test-renderer": "16.0.0"
  },

If I run the same on android it's performing perfectly. The only difference between iOS and android is the navigation structure. On iOS i'm having a TabNavigator and on Android I'm having a DrawerNavigator. But in my opinion this should not be a problem because these problems are always there and are seen without any routing. I made quite the same with a ListView but in fact of replacing ListView through SectionList this performance issues occurred.
If you need additional information or if I can explain something more deeply, let me know.

Are you implementing your Rows/Headers as PureComponents? What other steps are you doing minimize re-rendering?

@Ehesp I tried several things. I made the Rows PureComponents, I made shouldComponentUpdate lifecycles, I implemented getItemLayout and so on. Nearly everything in the "Performance" Section on the RN docs. Is there a problem with using Redux in the way I'm doing it, because I'm wondering if I'm the only one with such problems.
I made another very small example and I'm still getting performance issues.
HomeView.js
/**
 *
 */

'use strict';

import React, { Component } from 'react';
import {
	View,
	Text,
	SectionList,
	Image
} from 'react-native';

import {
	fetchJSON,
	updateGlobals
} from '../../actions/dataActions';

import urls from '../../config/urls';

class HomeView extends Component {

	_renderItem({item}) {

		if(item.type) {

			switch(item.type) {

				case "title":
					return(
						<View style={{height: 200, justifyContent: 'center', alignItems: 'center'}}>
							<Text>{item.title}</Text>
						</View>
					);
					break;

				case "more_button":
					return(
						<View style={{height: 200, justifyContent: 'center', alignItems: 'center'}}>
							<Text>{item.title}</Text>
						</View>
					);
					break;

				case "vendor":

					return (
						<View style={{height: 200, justifyContent: 'center', alignItems: 'center'}}>
							<Text>{item.items[0].title}</Text>
						</View>
					)
					break;

				case "deal":

					return (
						<View style={{height: 200, justifyContent: 'center', alignItems: 'center'}}>
							<Text>{item.items[0].title}</Text>
							<Image
								source={{uri: 'https://storage.cpstatic.ch'+item.items[0].storageurl_imageTeaser.src}}
								style={{width: 80, height: 100}} />
						</View>
					)
					break;

			}

		}

		if(item.upoxType) {

			return(
				<View style={{height: 200, justifyContent: 'center', alignItems: 'center'}}>
					<Text>{item.title}</Text>
				</View>
			);

		}

		return <View />;

	}

	_getItemLayout(data, index) {

		let height = 200;
		return {
			length: height,
			offset: height * index,
			index
		};

	}

	componentDidMount() {

		// Initial Loads ------------------------------------------------------
		this.props.dispatch(fetchJSON('homeView', urls.homeUrl));

		if(this.props.data && this.props.data.navigation && this.props.data.navigation.params && this.props.data.navigation.params.loggedIn) {
			this.props.dispatch(fetchJSON('watchListIds', urls.baseUrl + urls.getWatchList));
		}

		this.props.dispatch(updateGlobals({loggedIn: this.props.data.navigation.params.loggedIn}));
		this.props.dispatch(updateGlobals({activeRoute: 'home'}));
		// ---------------------------------------------------------------------

	}

	render() {

		if(this.props.data && this.props.data.homeView && this.props.data.homeView.sections) {

			return(
				<SectionList
					getItemLayout={this._getItemLayout}
					renderItem={this._renderItem.bind(this)}
					keyExtractor={ (item, index) => index }
					sections={this.props.data.homeView.sections} />
			);

		}

		return <View />;

	}

}

module.exports = HomeView;

My Sections are coming from a redux state. It's an array with 5 entries, each entry has a data array with one or more items in it.
With this very small example (I'm only showing the title and an Image per row), I'm getting a stocking SectionList as seen in my .gif below.

Can you share what each item in your data (sections) contains?

Yeah so the problem is your renderItem needs to return a component which handles shouldComponentUpdate. Currently you're just returns a View inline, which means it'll re-render it every single time (causing you performance issues), as your data is all over the show - it cannot do a shallow compare.
I'd suggest getting the data in a format which is (1) a flat object and (2) in the same format for every single product. Then you can easily handle whether each row should update.

FlatList and SectionList is bad performance. Try this,please. may be it is a surprise for you
https://github.com/bolan9999/react-native-largelist

@bolan9999 no, the performance is bad if you don't implement it properly.

Do not say this sarcastically, I think most developer give up react native because of the FlatList and SectionList. It is the most commonly used component，but bugs keep 2 years.

I have now managed to get a good performance by rethinking and mostly rewriting a lot of my components. It was a huge time consuming process but now I'm having a performant app again. The frustrating thing was, with ListView everything performed very well and as the relaese notes sayed FlatList and SectionList are more performant than the old ListView I had to change several things to get a good performance again. I hope for the future, I don't have to rewrite so much components because of a concept change in react-native.
@bolan9999 your plugin is very well and i would wish react-native would adapt some concepts, but it's always a little bit of a risk with such plugins. Because I'm having a very large app and if sometime your plugin isn't supported anymore or react-native gets changed and there is a huge update to do on your site and then on my site, its always a mess. I had alot of these updates and problems in the past 2 years of developing a very large app in react-native.
I'm closing this issue. For everyone with the same problem:

read the docs section "performance"
think of how you made your components
rethink how you made your components
read the docs section "performance" again
keep your components simple
shouldComponentUpdate is your fried (read exactly how this works and whats the benefit of it)

If it's a performance problem caused by listview
You can try this library
react-native-nlist


Question: Do you have an example that opens the app if it not in background and load a route in flutter using the path info?

No


panic on importing github.com/golang/protobuf/proto

I am trying to interpret go code, which uses grpc (protobuf) definitions as function arguments and response. (reference: https://github.com/cs3org/go-cs3apis/blob/main/cs3/identity/user/v1beta1/resources.pb.go#L77).
On running, I get following error:
run: reflect.Set: value of type func(interface {}, interface {}) bool is not assignable to type *interp.node

which is caused by https://github.com/protocolbuffers/protobuf-go/blob/master/internal/order/order.go#L51.

@mvertes, sorry to ping, but is there any way around this? How do I interpret go code that has dependencies on protobuf?


Adding a new BaseCardElement  Badge for iOS

Related Issue
Adding support for new Element Badge
Description
This PR implements a new BaseCardElement Badge.
This new element supports following properties

https://github.com/user-attachments/assets/1b0ed25d-a25c-4546-81a5-73a81fb0a69c

I think, all new headers files should be in private headers directory.
Also, you should be creating symlink in Include folder.

I think, all new headers files should be in private headers directory. Also, you should be creating symlink in Include folder.

fixed.


[Bug]: Main website not working properly

Give a brief about the bug ✍
Description: these bugs are based on latest clone of the project

The scroller of the website don't work , it hangs anywhere , anytime .
The Socials have duplicate entry.
The page buttons of the contributors sections are not working properly.
Images are placed at wrong places
Main page is horizontally aligned , it should be vertically aligned
Games don't load on the main website

What is the expected behavior? 🤔
Description:

The scroller should work smoothly.
Duplicate socials should be removed
page buttons of the contributors section should work , so that one can see all contributors
Images should be moved to right folder
Main page should be vertically aligned

Provide step by step information reproduce the bug 📄
Description:
You can see all these bugs by opening index.html in your browser from the latest clone of the repo .

the bug for scroller needs to be addressed by analyzing the codebase
duplicate socials can be removed from main html file directly
bug regarding page button not working also needs to be searched for.
Images that are placed in wrong folders can be moved to the right destination
HTML structure and CSS need to be checked to make to page vertical
games not loading , for this we need to check JS files .

Select program in which you are contributing
GSSoC24
Code of Conduct

[X] I follow CONTRIBUTING GUIDELINE of this project.

Hey @mohitgedar !
Thank you for raising an issue 💗
You can self assign the issue by commenting /assign in comment 😀
Make sure you follow CODE OF CONDUCT and CONTRIBUTING GUIDELINES 🚀
Don’t Forget to ⭐ our GameZone🎮
Make sure you join our Discord🕹

/assign

Hey @mohitgedar ! Thank you so much for your raising the issue💗
It’s all yours, you can come anytime again and make some contributions! 🚀
Alone, we can do little, but together we can do so much! 😇


fixes #1039 - Adds content check before parsing sentence.

a unit test to demonstrate the PR (MessageParser ligne 142) would be great
Added :)

why using logger.warn ? please use debug or explain
logger.warn replaced with debug as suggested

Why using System.identityHashCode in log?
Was a leftover from a debug session - removed


⚠ SolarOscp has degraded performance

In 9d3572f, SolarOscp ($SOLAROSCP_URL) experienced degraded performance:

HTTP code: 200
Response time: 228 ms

Resolved: SolarOscp performance has improved in 0bc1e36 after 9 minutes.


[GSSoC'21] adding dark mode with toggle button

I want to add a dark mode to the website as i had already raised this issue before and made a PR but by mistake i closed the PR and issue was also closed i had already added this feature to website just had to make a PR

@rupeshmohanty kindly assign me this issue again sorry for inconvenience seriously I don't know how i closed that PR its my work of 3 hours how can i closed it i can't believe my self.

@arpit456jain Did that PR get accepted?

This was the PR you added the labels and request the changes.
This morning when I saw you closed the issue then I notice may be I had closed the PR by mistake

There was already a PR for this issue, so that's why I closed this issue.

no sir I think some misunderstanding happens.
1 .I had raised a issue for adding dark mode which was assign to me.
2 I had created a PR for that.
3 then last night by mistake I had closed the PR.
4 This morning you closed my previous issue for that may be because I had closed the PR.
5. Then I created this new issue for dark mode.
If some else is working on this then I have no problem.
Otherwise kindly assign me this issue I already done the work yesterday just have to make a PR.

@rupeshmohanty kindly assign me this issue if possible

Thank you @rupeshmohanty


Saving caches stops when rotating screen

Hi,
when screen autorotates by turning the device saving of a listing for offline use stops. Same when display turns off automatically. I have to tap on the screen regularly while saving caches to not let the screen turn off itself.
Thanks

duplicate of #292


[Bug]: Custom Cipher Suites doesn't seem to work

Version of the software
0.2.4
Operating system
Windows Server 2019
Browser / Native
Chrome
What happened?
According to https://github.com/salesforce/ja3

JA3 is a method for creating SSL/TLS client fingerprints that should be easy to produce on any platform and can be easily shared for threat intelligence.

JA3 gathers the decimal values of the bytes for the following fields in the Client Hello packet; SSL Version, Accepted Ciphers, List of Extensions, Elliptic Curves, and Elliptic Curve Formats. It then concatenates those values together in order, using a "," to delimit each field and a "-" to delimit each value in each field.

You can view your tls fingerprint here: https://ja3er.com/ or here in JSON format: https://ja3er.com/json
I made a small project to get JA3 fingerprint of Openbullet2(code provided below).
After sending multiple requests, JA3 fingerprint hash was identical for all of them. Next, I changed Http Library to SystemNet and switched on Use Custom Cipher Suites, according to how JA3 fingerprinting works, the hash should change as one of five values is Accepted Ciphers, leaving only of the default listed chipers in OpenBullet2, the hash stayed identical to what I got previously.
Proof: https://prnt.sc/D4LP4AEw4bsO and https://prnt.sc/gekBrmu8Mz13
So, my conclusion is: Custom Cipher Suites does not work as it should, giving various custom chipers should change TLS fingerprint to bypass WAF of such companies as Akamai, etc.
Article to better understand how spoofing JA3 works: https://medium.com/cu-cyber/impersonating-ja3-fingerprints-b9f555880e42
Relevant LoliCode if needed
BLOCK:HttpRequest
LABEL:ja3
  url = "https://ja3er.com/json"
  httpLibrary = SystemNet
  useCustomCipherSuites = True
  TYPE:STANDARD
  ""
  "application/x-www-form-urlencoded"
ENDBLOCK

BLOCK:Parse
LABEL:hash
  input = @data.SOURCE
  jToken = "ja3_hash"
  MODE:Json
  => VAR @hash
ENDBLOCK

Hello, currently you cannot use this feature on Windows since by default it uses the SChannel TLS provider which does not allow to configure cipher suites on a per-request basis, unless you manually change them from your windows policies. You can only use this feature on macOS/Linux if you installed the latest openssl library.
There is already an issue where I mention this
https://github.com/openbullet/OpenBullet2/issues/691
I will leave this open as it's a bit more informative.

Thanks a lot for the reply. Didn't know it doesn't work on windows. I'll try use it on linux.
For anyone wondering, how to randomize JA3 fingerprint on windows, I used CycleTLS library for NodeJS (https://github.com/Danny-Dasilva/CycleTLS)
`
const initCycleTLS = require('cycletls');
// Typescript: import initCycleTLS from 'cycletls';
(async () => {
// Initiate CycleTLS
const cycleTLS = await initCycleTLS();
// Send request
const response = await cycleTLS('https://ja3er.com/json', {
body: '',
ja3: '771,4865-4867-4866-49195-49199-52393-52392-49196-49200-49162-49161-49171-49172-51-57-47-53-10,0-23-65281-10-11-35-16-5-51-43-13-45-28-21,29-23-24-25-256-257,0',
userAgent: 'Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:87.0) Gecko/20100101 Firefox/87.0',
proxy: 'http://username:password@hostname.com:443'
}, 'get');
console.log(response);
// Cleanly exit CycleTLS
cycleTLS.exit();
})();
`
You can also use this code with Openbullet2 nodejs interop block. You can create an array with JA3 fingerprints downloaded from here: https://ja3er.com/downloads.html and then just take random item from array. It worked perfectly for me on Windows 11 + OpenBullet2.
I also wish something like this could be implemented in OpenBullet, since randomizing only ciphers is kinda weak randomization.
Thanks!

bump

At today there is an project made in c# https://github.com/mnickw/CycleTLS-dotnet,
You could add this proyect into openbullet2, or looking for a way to compile into DLL the go module inside the main project https://github.com/Danny-Dasilva/CycleTLS


Kubectl Command - Screen simplification. Menu et. al.

This all sorted under this https://github.com/Azure/vscode-aks-tools/pull/233 Thanks,


how do i get the emoji from standalone

hi sir mervick. how can i put the emoji i have selected from the standalone emojionearea to my textarea? thank you very much

for get value from EmojioneArea use this code
$("#element").data("emojioneArea").getText();

should i use this event to get the value?
click: function (editor, event) {
console.log('event:click');
}

https://jsfiddle.net/3qcfr09s/1/


[5.7] Route not checking for aliases

When registering routes you can for example write
Route::name('foo')->prefix('foo')->namespace('Foo')->group(function(){});
But can't write
Route::group ( [ 'name' => 'foo', 'prefix' => 'foo', 'namespace' => 'Foo' ], function(){});
and have to change the 'name' to 'as' like so
Route::group ( [ 'as' => 'foo', 'prefix' => 'foo', 'namespace' => 'Foo' ], function(){});
because the Route::group doesn't check for aliases, but RouteRegistrar does.
But with this pull request they both will check for aliases and everything will work as expected.
This change will benefit to end users that prefer using one function call instead of nested function calls.
Issue #25182

I am closing this pull request because it lacks sufficient explanation, tests, or both. It is difficult for us to merge pull requests without these things because the change may introduce breaking changes to the framework.
Feel free to re-submit your change with a thorough explanation of the feature and tests - integration tests are preferred over unit tests. Please include it's benefit to end users; the reasons it does not break any existing features; how it makes building web applications easier, etc.
Thanks!

In your first example, calling "name", followed by a call to "group", should not be allowed and will cause problems when using named routes. Every route in the group will have the same name and if you subsequently call "name" on the routes inside the group, it will be ignored.
So IMO, if anything, calling "name" in a chain with "group" should be disallowed.
The  "as" method is appropriate for groups as it allows creating a "name" prefix for the entire group, like "posts." Then inside your group, you can specify route names that will yield names like "posts.show", "posts.index", etc.


All hosts on one line causes resolution trouble, especially on Windows

Could goodhosts use a single line per host in the hosts file? Or a limit of how many hosts get added to a single line? The long lines seem to cause occasional trouble with name resolution macOS, and more than 10 hosts per line seems to be completely nonfunctional at least in some WIndows versions, see https://superuser.com/questions/932112/is-there-a-maxium-number-of-hostname-aliases-per-line-in-a-windows-hosts-file
Spurred by request in https://github.com/drud/ddev/issues/948

As far as I can tell the limit is 9 aliases per line in Windows - so yeah would definitely be excellent to get this fixed, or have some way to work around it, at least. Say, disabling the behaviour where it bundles aliases for same IP together (could even just be disabled by default on Windows)

I did take an extensive look at this, but. this project is very, very hostsfle-line focused., so it's nearly a rewrite to fix.  It assumes that the first line where it finds the IP is the only one.

I just took a closer look at the code, and found a way to add this behaviour. I needed only to re-write the Add method a bit. I have introduced the appendToLine constant which is setup in const.go (true for Linux/Darwin systems) and const_windows.go (false for Windows).
// Add an entry to the hosts file.
func (h *Hosts) Add(ip string, hosts ...string) error {
	if net.ParseIP(ip) == nil {
		return errors.New(fmt.Sprintf("%q is an invalid IP address.", ip))
	}

	if appendToLine {
		position := h.getIpPosition(ip)
		if position == -1 {
			newLine := NewHostsLine(buildRawLine(ip, hosts))
			// Ip line is not in file, so we just append our new line.
			h.Lines = append(h.Lines, newLine)
		} else {
			// Otherwise, we replace the line in the correct position
			newHosts := h.Lines[position].Hosts
			for _, addHost := range hosts {
				if itemInSlice(addHost, newHosts) {
					continue
				}

				newHosts = append(newHosts, addHost)
			}
			newLine := NewHostsLine(buildRawLine(ip, newHosts))
			h.Lines[position] = newLine
		}
	} else {
		// Otherwise we append the line to the end
		newLine := NewHostsLine(buildRawLine(ip, hosts))
		h.Lines = append(h.Lines, newLine)
	}

	return nil
}

I simply always append to the end when adding a host, when not appendToLine is enabled.
This has a few quirks:

It will allow you to add host -> ip mappings which already exists, whereas existing logic ensures not to add duplicates (could be mitigated in the new code, I just didn't need it for our use case).
It will allow you to add more than the 9 maximum hosts for a single line, if you invoke Add with more than 9 hosts, so the client code need to not add multiple hosts at once, or only add up to 9 at a time. Could also easily be fixed by iterating the hosts slice when not in append mode.

Would love to see your PR. Probably your fork and your PR :) , but we can hope for a response from the maintainer, this issue queue hasn't had much in recent years. This has been a solidly reliable library for us on all platforms though, and much appreciated for that.

I took another look into it and put a bit more effort into the implementation, accommodating the two quirks I mentioned earlier.
https://github.com/lextoumbourou/goodhosts/pull/13


The "Used by" counter on Github is misleading

I guess it's because 'my' is a somewhat common Python package name? Wonder if it can be fixed...

dunno, what happened, but it's not there anymore


Support CMCC Kilo

What issues does this address?
What's this change do?
Archive the code made by SE to support CMCC Kilo. Those change will not merged into release branch.
Where should the reviewer start?
Any background context?

One unclear change. Need to get confirmation from SE.
diff --git a/f5_openstack_agent/lbaasv2/drivers/bigip/agent_manager.py b/f5_openstack_agent/lbaasv2/drivers/bigip/agent_manager.py
index 3e9630d..ccc493c 100644
--- a/f5_openstack_agent/lbaasv2/drivers/bigip/agent_manager.py
+++ b/f5_openstack_agent/lbaasv2/drivers/bigip/agent_manager.py

@@ -810,6 +813,7 @@ class LbaasAgentManager(periodic_task.PeriodicTasks):  # b --> B
                 pools = self.lbdriver.get_all_deployed_pools()
                 if pools:
                     self.purge_orphaned_pools(pools)
+                    self.purge_orphaned_nodes(pools)

                 # Ask the BIG-IP for all deployed monitors not associated
                 # to a pool


Run unit tests on python client in CI

This will currently fail CI until https://github.com/stytchauth/stytch-python/pull/38 is merged.


test: increased timeout in HtmlBuilderTest

The timeout was a bit tight for execution on github actions and failed sometimes.

:tada: This PR is included in version 3.0.1 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Custom domain

Using your github-pages account gives easy deployment and HTTPS support, but a shorter address would be nice.
keeweb.com is taken, but what about keeweb.co?

Or keeweb.io

So, the app is now available here:
http://app.keeweb.info - the app itself, will redirect to github repo pages as it's https
http://keeweb.info - app website, under construction for now, will be created in a week or so
I've chosen .info because keepass has .info as well and .io is 3x more expensive.

Great!

Bad part that the redirect still lacks HTTPS support (so the redirect app.keeweb.info is vulnerable to mitm attack), I'm thinking how to solve it...

You should be able to have HTTPS on all keyweb.info URLs if you use a custom domain on Github pages: https://help.github.com/articles/setting-up-a-custom-domain-with-github-pages/

Unfortunately, no. If I want to use HTTPS on custom domain, I have to use some proxy like cloudflare. There's no option to use HTTPS directly with github pages...

You're right.  Might be better to use something other than Github pages then

Something other using HTTPS is either expensive or slow. I'm thinking about cloudfront... if the price will be no more than $0.5/month, I'll witch to it.

That's what I would recommend, too.  Amazon's pricing is pretty unclear, though.  Probably best to just use the free period as an estimate.

Hm, for me, they looks rather clear: number or requests + traffic in gb/month + dns. My free period was finished several years ago... I have a couple of websites and a commercial project there, what I'm trying to estimate is traffic per month. Kind of marketing stuff, not technical, this is hard for me.

I've decided to use CloudFlare free plan, for now it should do the job very well.
So the website now has https: https://keeweb.info/ - and the app is available as https://app.keeweb.info/
I'm updating the links and adding support for Dropbox, tomorrow everything will be ready, together with DNS propagation.

@antelle It doesn't seem wise to use unvalidated TLS for an online password manager. You should get your own certificates and change your hosting provider.


CTL locking script and NFT minting policy

Build step will likely fail, to be solved by #365
Have verified it builds successfully locally

Verified builds on my machine


MPX international export: Remove NML_LIMS from the export options list

The NML_LIMS export option should only be available for the Canadian version of the template, so no need to offer it in the Monkeypox_international template.
Can we please remove the NML_LIMS option from the Monkeypox_international export list?

Done


Feeds tab fixes

Bold the saved feeds on mobile (looked wrong to me)
Better loading state of saved feeds (placeholders)
Add soft reset to the feeds page (tapping on the # when already open now reloads)
Show feed descriptions in profile listings
Add an "About this feed" button to the dropdown to see the details

I'm not in love with the "about this feed" UI but it's enough for now.

going to merge w/o review so I can put up a testflight tonight


marwaita-peppermint: 0.3 -> 0.4

Motivation for this change
Update to version 0.4
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/prs-ready-for-review/3032/319

As it is a simple package update, tested locally, I am going to merge.


feat(connlib): parallelise TUN operations

Currently, connlib is entirely single-threaded. This allows us to reuse a single buffer for processing IP packets and makes reasoning of the packet processing code very simple. Being single-threaded also means we can only make use of a single CPU core and all operations have to be sequential.
Analyzing connlib using perf shows that we spend 26% of our CPU time writing packets to the TUN interface 0. Because we are single-threaded, connlib cannot do anything else during this time. If we could offload the writing of these packets to a different thread, connlib could already process the next packet while the current one is writing.
Packets that we send to the TUN interface arrived as an encrypted WG packet over UDP and get decrypted into a - currently - shared buffer. Moving the writing to a different thread implies that we have to have more of these buffer that the next packet(s) can be decrypted into.
To avoid IP fragmentation, we set the maximum IP MTU to 1280 bytes on the TUN interface. That actually isn't very big and easily fits into a stackframe. The default stack size for threads is 2MB 1.
Instead of creating more buffers and cycling through them, we can also simply stack-allocate our IP packets. This incurs some overhead from copying packets but it is only ~3.5% 2 (This was measured without a separate thread). With stack-allocated packets, almost all lifetime-annotations go away which in itself is already a welcome ergonomics boost. Stack-allocated packets also means we can simply spawn a new thread for the packet processing. This thread is connected with two channel to connlib's main thread. The capacity of 1000 packets will at most consume an additional 3.5 MB of memory which is fine even on our most-constrained devices such as iOS.
Resolves: #6653.
Resolves: #5541.

Damn this array indexing stuff for the NAT46 offset is quite nasty ..

Damn this array indexing stuff for the NAT46 offset is quite nasty ..

I feel you, hah

@conectado I think I fixed everything. I'll do some final speedtests and flamegraphs once I have a better internet connection to make sure the recent changes don't introduce regressions.

@conectado I think I fixed everything. I'll do some final speedtests and flamegraphs once I have a better internet connection to make sure the recent changes don't introduce regressions.

Final speedtests and flamegraphs look good. With my connection from Australia, I am getting ~10 Mbps more download and ~5 Mbps more upload on my Linux machine. I've only tested the MacBook over WiFi and there it is a bit more flaky. I also haven't spent any time profiling the MacOS code itself.


Update DNS PowerShell to DSC

- name: Check for xDnsServer Powershell module
  win_psmodule:
    name: xDnsServer
    state: present

- name: Configure DNS Forwarders
  win_dsc:
    resource_name: xDnsServerSetting
    Name: DNSServerProperties
    NoRecursion: false
    Forwarders:
      - "<IP_ADDRESS>"
      - "<IP_ADDRESS>"

Replacing it with DSC should also fix #6 and #7


Vue3

Could you make this project for VUE 3?

Its possible, I will make a vue 3 version at some point.


Point to correct Version file.

Summary of the changes / Why this improves CrateDB
io.crate.Version -> org.elasticsearch.Version
I will update it on master in the same PR with release notes sync.
Because I want to move a bit faster with the 4.0.0 release (tag 4.0 after this pr is merged)
Checklist

[ ] User relevant changes are recorded in CHANGES.txt
[ ] Touched code is covered by tests
[ ] Documentation has been updated if necessary
[ ] CLA is signed
[ ] This does not contain breaking changes, or if it does:

It is released within a major release
It is recorded in CHANGES.txt
It was marked as deprecated in an earlier release if possible
You've thought about the consequences and other components are adapted
(E.g. AdminUI)

https://github.com/crate/crate/pull/8867


hive: Reimplement on top of dig

This reimplements hive directly on top of the uber/dig library. This simplifies
dealing with lifecycles and logging, and most importantly allows implementing
the configuration flag registration in a straightforward way with an invoke.
The usage is also simplified as now there's only one library to learn. The
API is very similar to uber/fx, but has support for configs. At "hive" creation
time the config command-line flags are registered, but object graph instantiation
is deferred to start time. This allows supporting command-line applications with
many commands (with each their own object graph) and only instantiating when
we know which command to run.
The configuration dumping in "cilium-agent objects" is for now removed as the
output was not very pretty and it is yet unclear how this should be done cleanly
with nested cells.
Usage looks like this now:
type ExampleConfig struct { ... }
func (def ExampleConfig) Flags(flags *pflag.FlagSet) {
  flags.String("foo", def.Foo, "usage of foo")
  ...
}
var defaultConfig = ExampleConfig{...}

var Example = cell.Module(
  "example",

  cell.Config(defaultConfig), // Provides `ExampleConfig` and registers the flags

  cell.Provide(newExample, newSomethingElse),
  cell.Invoke(func(ex *Example, se *SomethingElse) error { ...}),

  cell.Decorate(
    func(thing *Thing) *Thing { /* return some augmented Thing */ },
    // Constructor gets augmented Thing:
    cell.Provide(newUserOfThing),
  )
)

fx.Option is no longer used, so there's now just one library to learn and should be less confusing to users.
Using dig directly allows more fine-grained control of what gets instantiated when. This allows for way simpler implementation for configs.
Provide, Invoke and Module has the same API as Fx does. Decorate instead takes a set of cells to "decorate".
Lifecycle is now implemented in pkg/hive, which allows more complicated uses like nested lifecycles that we need for the operator.

/test

Revamped PrintObjects:
$ ./cilium-agent objects
Cells:

  gops:
    ⚙  gops.GopsConfig:
      gops-port[uint16]=9890

    🛠  pkg/gops.registerGopsHooks (cell.go:38) (func(hive.Lifecycle, logrus.FieldLogger, gops.GopsConfig))

  k8s-client:
    ⚙  client.Config:
      enable-k8s-api-discovery[bool]=false
      k8s-api-server[string]=
      k8s-client-burst[int]=0
      k8s-client-qps[float32]=0
      k8s-heartbeat-timeout[duration]=30s
      k8s-kubeconfig-path[string]=

    🚧 pkg/k8s/client.newClientset (cell.go:106): func(hive.Lifecycle, logrus.FieldLogger, client.Config) (client.Clientset, error)

  ⚙  cmd.DaemonCellConfig:
    skip-daemon[bool]=false

  🛠  daemon/cmd.registerDaemonHooks (daemon_main.go:1570) (func(cmd.daemonParams) error)

  🚧 pkg/node.newLocalNodeStore (local_node_store.go:71): func(node.LocalNodeStoreParams) (node.LocalNodeStore, error)

Start hooks:

  • pkg/gops.registerGopsHooks.func1 (cell.go:43)
  • pkg/node.newLocalNodeStore.func1 (local_node_store.go:80)
  • daemon/cmd.registerDaemonHooks.func1 (daemon_main.go:1591)

Stop hooks:

  • daemon/cmd.registerDaemonHooks.func2 (daemon_main.go:1607)
  • pkg/node.newLocalNodeStore.func2 (local_node_store.go:95)
  • pkg/gops.registerGopsHooks.func2 (cell.go:50)

/test


Helmfile doesn't respect --helm-binary option when using helmCharts in kustomization.yaml

Operating system
macOS (aarch_64)
Helmfile Version
0.158.0
Helm Version
3.12.3
Bug description
Despite specifying the --helm-binary option in Helmfile, the default helm command is still used when a helmChart is specified in the kustomization.yaml file.
Example helmfile.yaml

name: kafka-ui
namespace: kafka-ui
chart: ./kafka-ui/{{ .Environment.Name }}

Error message you've seen (if any)
Error: accumulating resources: accumulation err='accumulating resources from '../../../../../../../../..//beta': read //beta: is a directory': recursed accumulation of path '//beta': accumulating resources: accumulation err='accumulating resources from '../base': read //base: is a directory': recursed accumulation of path '//base': unable to run: 'helm version -c --short' with env=[HELM_CONFIG_HOME=/var/folders/rg/6nvd_9352tn17g3czmjnd1y80000gq/T/kustomize-helm-2352119409/helm HELM_CACHE_HOME=/var/folders/rg/6nvd_9352tn17g3czmjnd1y80000gq/T/kustomize-helm-2352119409/helm/.cache HELM_DATA_HOME=/var/folders/rg/6nvd_9352tn17g3czmjnd1y80000gq/T/kustomize-helm-2352119409/helm/.data] (is 'helm' installed?): exec: "helm": executable file not found in $PATH]
Steps to reproduce
https://gist.github.com/moririnson/d38d1e5991367f1312379f72a2542769
Working Helmfile Version
No
Relevant discussion
No response

I don't think there are cases where a user specifying --helm-binary would want to use `helm.Thank you for your consideration.
https://github.com/helmfile/chartify/pull/64


Extract DB creation into server

Pull Request Test Coverage Report for Build 327315916

27 of 50 (54.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-1.1%) to 77.868%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

cmd/api/server/database.go
27
50
54.0%

Totals

Change from base Build 327264104:
-1.1%

Covered Lines:
862

Relevant Lines:
1107

💛  - Coveralls


Example with global data in spherical projection

https://www.ncei.noaa.gov/products/optimum-interpolation-sst
oisst-avhrr-v02r01.19810901.nc.zip
import xarray
ds = xarray.open_dataset('oisst-avhrr-v02r01.19810901.nc')
ds.err.plot()

The tricky part is performing the 3D coordinate transform - this can get very complicated very quickly and this library's goal is not to perform coordinate transforms.
I'm going to see what I can do to use existing tools to do this.

had a great chat with @bjlittle about using geovista to this end - he's created some fantastic functionality in that library to handle all of the coordinate transforms, and I think with a little bit of work, we can leverage geovista's transformer/bridge to handle the 3D reprojections here.
ref https://geovista.readthedocs.io/en/latest/ and https://github.com/bjlittle/geovista
We will follow up in a few weeks

@banesullivan I've made some time to spin back up and show some love to geovista.
I've bolstered the README.md in the short-term until it get space to fully bootstrap the docs for the 0.1.0 release.
However, you'll be glad to hear that I've also made most of the geovista/examples self-contained, so that they are agnostic of SciTools/iris and automatically download and cache the required geovista sample data. I just have a couple of examples still to self-contain, so I'll let you know when I've done that.
There are still a few major wrinkles to iron out prior to the 0.1.0 release, but I'm also keen to start thinking about providing support for rectilinear/uniform/structured grids to underpin the pyvista-xarray use case.

@banesullivan BTW the above NOAA/NCEI OISST AVHRR dataset looks like this:

Which looks rather lush. I also added the dataset as a GeoVista pantry sample, and highlighted it on the README and also created an example, see example_from_1d__oisst.py.

This looks excellent.

I'm going to mark this issue complete with examples in the examples/ directory now that show how to use PyVista-Xarray with GeoVista. However, this work is not fully complete until the following Pull Requests merge:

https://github.com/pyvista/pyvista/pull/3318
https://github.com/bjlittle/geovista/pull/127


OSS 2.3 Release Notes

Maintenance

Upgrade Flux from 0.161.0 to 0.171.0
Upgrade Go to 1.18.3

Features

Add --instance-id flag to influxd runtime for adding _instnace_id Tag to outgoing metrics via remote replications. This will help users ID where metrics came from and ensure two instances don't overwrite each others data in some cases.
Add signifier to replication user-agent when replication write requests are made. This helps ID that the metric was written via replications.

Flux advancement
Performance:

Vectorize arithmetic operators in map()
Vectorize logical operations in map()
Enable movingAverage() and cumulativeSum() optimizations by default

Other:

Add preview() to experimental package for limiting return rows and tables (as opposed to just rows with limit())
Add date.scale() to let users dynamically scale durations in dates
Add OpenTracing spans to Flux transformations. This allows developers to more precisely monitor Flux scripts.
Add trace option to Flux CLI
Move addDuration() and subDuration() out of experimental to date package.
Add location support to date.truncate()
Add _status Tag to PagerDuty record
Refactor operator profile to be in the query statistics

Bug Fixes

Fix race condition when remote replicating that deadlocks the remote writer, resulting in no more writes to the target.
Error when creating v1 auth with a nonexistent bucket ID
Add fields to _tasks bucket to match schema of the same bucket in InfluxDBCloud. Provides consistency for clients accessing both.
Fix rare case where Measurement cardinality reported less than zero
No longer panic on cleaning up failed iterators

Maintenance

Upgrade Flux from 0.161.0 to 0.171.0
Upgrade Go to 1.18.3

Features

Add --instance-id flag to influxd runtime for adding _instnace_id Tag to outgoing metrics via remote replications. This will help users ID where metrics came from and ensure two instances don't overwrite each others data in some cases.
Add signifier to replication user-agent when replication write requests are made. This helps ID that the metric was written via replications.

Flux advancement
Performance:

Vectorize arithmetic operators in map()
Vectorize logical operations in map()
Enable movingAverage() and cumulativeSum() optimizations by default

Other:

Add preview() to experimental package for limiting return rows and tables (as opposed to just rows with limit())
Add date.scale() to let users dynamically scale durations in dates
Add OpenTracing spans to Flux transformations. This allows developers to more precisely monitor Flux scripts.
Add trace option to Flux CLI
Move addDuration() and subDuration() out of experimental to date package.
Add location support to date.truncate()
Add _status Tag to PagerDuty record
Refactor operator profile to be in the query statistics

Bug Fixes

Fix race condition when remote replicating that deadlocks the remote writer, resulting in no more writes to the target.
Error when creating v1 auth with a nonexistent bucket ID
Add fields to _tasks bucket to match schema of the same bucket in InfluxDBCloud. Provides consistency for clients accessing both.
Fix rare case where Measurement cardinality reported less than zero
No longer panic on cleaning up failed iterators


Integer filter select does not work

When filtering on Less than or Greater than, it always filters on Equals.

Fixee

Looks like this is broken again on themes branch.


Force Closing channel due to close-required error: Invalid commitment tx signature from peer

Reproduced here https://github.com/get10101/10101/blob/test/force-close-with-reversed-order-in-dlc-setup-with-reconnects/crates/ln-dlc-node/src/tests/dlc/dlc_setup_with_reconnects.rs
Upon reconnecting during opening a position here
https://github.com/get10101/10101/blob/test/force-close-with-reversed-order-in-dlc-setup-with-reconnects/crates/ln-dlc-node/src/tests/dlc/dlc_setup_with_reconnects.rs#L103
or during closing a position here
https://github.com/get10101/10101/blob/test/force-close-with-reversed-order-in-dlc-setup-with-reconnects/crates/ln-dlc-node/src/tests/dlc/dlc_setup_with_reconnects.rs#L182
the channel gets force closed with the following error:
Closing channel 006d235e495a7e034bde6449c04aa55628afb931b2cc6a431958081709326248 due to close-required error: Invalid commitment tx signature from peer

@luckysori can you check on your machine if this is still not reproducible for you?

@luckysori can you check on your machine if this is still not reproducible for you?

I've tried to reproduce this by reverting back to https://github.com/p2pderivatives/rust-dlc/commit/d4b69cb, but I've not been able to. Let's close this for now and reopen it if we ever run into it again.

Still happens to me on my m1 mac. Re-opening.

Unfortunately I can't run tests so I can't reproduce it :/

Pushed a new version of the test with only reproducing that particular bug. Note, during testing I noticed that this bug is also flaky on my machine. About 95% it fails, but sometimes it succeeds without any changes.

This bug just happened on the testvm.
My position was expired and got automatically closed. I didn't notice and closed the app at processing the Event:SubChannelCloseOffer. After starting the app again the channel got force-closed wth the following error:
Closing channel de08d4608abea3edbc5b8b56df27c685d29cdaba0446be2dcb63f76940b37c2f due to close-required error: Invalid commitment tx signature from peer

app logs
| 2023-07-30 07:14:03.448 | LogLevel.TRACE | lightning_background_processor: Calling PeerManager's timer_tick_occurred
| 2023-07-30 07:14:03.463 | LogLevel.INFO | Processing message from: 03507b924dae6595cfb78492489978127c5f1e3877848564de2015cd6d41375802,kind: SubChannelCloseOffer
| 2023-07-30 07:14:03.474 | LogLevel.INFO | Accepting DLC channel collaborative settlement channel_id: de08d4608abea3edbc5b8b56df27c685d29cdaba0446be2dcb63f76940b37c2f
| 2023-07-30 07:14:03.477 | LogLevel.TRACE | lightning::ln::channel: Updating HTLC state for a newly-sent commitment_signed...
| 2023-07-30 07:14:03.478 | LogLevel.TRACE | lightning::ln::channel: Building commitment transaction number<PHONE_NUMBER>10618 (really 37 xor<PHONE_NUMBER>50067) for channel de08d4608abea3edbc5b8b56df27c685d29cdaba0446be2dcb63f76940b37c2f for remote, generated by us with fee 253...
| 2023-07-30 07:14:03.479 | LogLevel.TRACE | lightning::ln::channel:    ...including to_remote output with value 98070
| 2023-07-30 07:14:03.480 | LogLevel.TRACE | lightning::ln::channel:    ...including to_local output with value 91747
| 2023-07-30 07:14:03.480 | LogLevel.TRACE | lightning::chain::chainmonitor: Updating ChannelMonitor for channel de08d4608abea3edbc5b8b56df27c685d29cdaba0446be2dcb63f76940b37c2f
| 2023-07-30 07:14:03.481 | LogLevel.INFO | lightning::chain::channelmonitor: Applying update to monitor de08d4608abea3edbc5b8b56df27c685d29cdaba0446be2dcb63f76940b37c2f, bringing update_id from 95 to 96 with 1 changes.
| 2023-07-30 07:14:03.481 | LogLevel.TRACE | lightning::chain::channelmonitor: Updating ChannelMonitor with latest counterparty commitment transaction info
| 2023-07-30 07:14:03.482 | LogLevel.TRACE | lightning::chain::channelmonitor: Tracking new counterparty commitment transaction with txid 0fc441a898126973f433c2016efd635a9522b3cccf95801de551ad1513fa25b4 at commitment number<PHONE_NUMBER>10618 with 0 HTLC outputs
| 2023-07-30 07:14:03.485 | LogLevel.DEBUG | lightning::chain::chainmonitor: Persistence of ChannelMonitorUpdate for channel de08d4608abea3edbc5b8b56df27c685d29cdaba0446be2dcb63f76940b37c2f completed
| 2023-07-30 07:14:03.485 | LogLevel.TRACE | lightning::ln::channel: Creating an announcement_signatures message for channel de08d4608abea3edbc5b8b56df27c685d29cdaba0446be2dcb63f76940b37c2f
| 2023-07-30 07:14:03.486 | LogLevel.TRACE | lightning::ln::channel: Ignore : Channel is not available for public announcements
| 2023-07-30 07:14:03.486 | LogLevel.TRACE | lightning::ln::channel: Regenerated latest commitment update in channel de08d4608abea3edbc5b8b56df27c685d29cdaba0446be2dcb63f76940b37c2f with 0 update_adds, 0 update_fulfills, 0 update_fails, and 0 update_fail_malformeds
| 2023-07-30 07:14:03.487 | LogLevel.TRACE | lightning::ln::channel: Building commitment transaction number<PHONE_NUMBER>10618 (really 37 xor<PHONE_NUMBER>50067) for channel de08d4608abea3edbc5b8b56df27c685d29cdaba0446be2dcb63f76940b37c2f for remote, generated by us with fee 253...
| 2023-07-30 07:14:03.487 | LogLevel.TRACE | lightning::ln::channel:    ...including to_remote output with value 98070
| 2023-07-30 07:14:03.488 | LogLevel.TRACE | lightning::ln::channel:    ...including to_local output with value 91747
| 2023-07-30 07:14:03.488 | LogLevel.TRACE | lightning::ln::channel: Signed remote commitment tx<PHONE_NUMBER>de08d4608abea3edbc5b8b56df27c685d29cdaba0446be2dcb63f76940b37c2f00000000003685f780026366010000000000160014fab788e4c1921ace81ad85b16b47527d8857fb92167f0100000000002200205b20f1e7b435ac8dfb7a37d655c5286670c1f062df05d54b0554cd376f17916556aed620 (txid 0fc441a898126973f433c2016efd635a9522b3cccf95801de551ad1513fa25b4) with redeemscript<PHONE_NUMBER>bc88fbeeaf34e8a0d225aa23bd54317a9ab7db4833da4501cc9ceffa11dd362103d76d2ca47215e5fa1e36757a911719c5651b0e5c9cfc752b4e976594f8b4843c52ae with value 190000 -> 4f8db3e61399f3be4140cf344a94f9b28c6c443dfe0c1430e2abe970d35ed47203346b9940012f8a51fa8a8e41491bda1566e26477558641e20a23f735561e06 in channel de08d4608abea3edbc5b8b56df27c685d29cdaba0446be2dcb63f76940b37c2f
| 2023-07-30 07:14:03.489 | LogLevel.DEBUG | lightning::ln::channel: Restored monitor updating in channel de08d4608abea3edbc5b8b56df27c685d29cdaba0446be2dcb63f76940b37c2f resulting in a commitment update and no RAA, with RAA first
| 2023-07-30 07:14:03.489 | LogLevel.TRACE | lightning_background_processor: Persisting ChannelManager...
| 2023-07-30 07:14:03.493 | LogLevel.TRACE | lightning_background_processor: Done persisting ChannelManager.
| 2023-07-30 07:14:04.345 | LogLevel.DEBUG | Publishing event ServiceHealthUpdate(ServiceUpdate { service: Coordinator, status: Online })
| 2023-07-30 07:14:04.347 | LogLevel.DEBUG | Forwarding event to flutter event: ServiceHealthUpdate(ServiceUpdate { service: Coordinator, status: Online })
| 2023-07-30 07:14:04.348 | LogLevel.DEBUG | Received event: Event.serviceHealthUpdate(field0: Instance of 'ServiceUpdate')
| 2023-07-30 07:14:07.633 | LogLevel.INFO | lightning_transaction_sync::esplora: Starting transaction sync.
| 2023-07-30 07:14:09.897 | LogLevel.INFO | Initialized logger
| 2023-07-30 07:14:09.898 | LogLevel.INFO | App data will be stored in: /var/mobile/Containers/Data/Application/D0AB85E9-2D8F-47DF-9BDC-8312C48C4EFF/Documents
| 2023-07-30 07:14:09.898 | LogLevel.INFO | Seed data will be stored in: /var/mobile/Containers/Data/Application/D0AB85E9-2D8F-47DF-9BDC-8312C48C4EFF/Library/Application Support
| 2023-07-30 07:14:09.899 | LogLevel.DEBUG | Parsing config from flutter config: Config { coordinator_pubkey: "03507b924dae6595cfb78492489978127c5f1e3877848564de2015cd6d41375802", esplora_endpoint: "http://<IP_ADDRESS>:3000", host: "<IP_ADDRESS>", p2p_port: 9045, http_port: 80, network: "regtest", oracle_endpoint: "http://<IP_ADDRESS>:8081", oracle_pubkey: "16f88cf7d21e6c0f46bcbc983a4e3b19726c6c98858cc31c83551a88fde171c0", health_check_interval_secs: 10 }
| 2023-07-30 07:14:09.906 | LogLevel.DEBUG | Database migration run - db initialized
| 2023-07-30 07:14:09.906 | LogLevel.DEBUG | Publishing event Init("Starting full ldk node")
| 2023-07-30 07:14:09.906 | LogLevel.DEBUG | Forwarding event to flutter event: Init("Starting full ldk node")
| 2023-07-30 07:14:09.930 | LogLevel.INFO | Creating the wallet network: Regtest
| 2023-07-30 07:14:11.146 | LogLevel.INFO | Found channel manager data on disk. Recovering from stored state
| 2023-07-30 07:14:11.149 | LogLevel.INFO | lightning::ln::channelmanager: Successfully loaded channel de08d4608abea3edbc5b8b56df27c685d29cdaba0446be2dcb63f76940b37c2f
| 2023-07-30 07:14:11.150 | LogLevel.TRACE | lightning::chain::chainmonitor: Got new ChannelMonitor for channel de08d4608abea3edbc5b8b56df27c685d29cdaba0446be2dcb63f76940b37c2f
| 2023-07-30 07:14:11.161 | LogLevel.INFO | lightning::chain::chainmonitor: Persistence of new ChannelMonitor for channel de08d4608abea3edbc5b8b56df27c685d29cdaba0446be2dcb63f76940b37c2f completed
| 2023-07-30 07:14:11.162 | LogLevel.INFO | Started on-chain sync
| 2023-07-30 07:14:11.162 | LogLevel.DEBUG | Getting all non-pending channels
| 2023-07-30 07:14:11.162 | LogLevel.INFO | lightning_transaction_sync::esplora: Starting transaction sync.
| 2023-07-30 07:14:11.163 | LogLevel.DEBUG | Got all non-pending channels channels: [Channel { user_channel_id: UserChannelId(594bc62c-93d8-401e-9105-3402e0aff5f4), channel_id: Some([222, 8, 212, 96, 138, 190, 163, 237, 188, 91, 139, 86, 223, 39, 198, 133, 210, 156, 218, 186, 4, 70, 190, 45, 203, 99, 247, 105, 64, 179, 124, 47]), inbound: 25964000, outbound: 71595000, funding_txid: Some(2f7cb34069f763cb2dbe4604bada9cd285c627df568b5bbceda3be8a60d408de), channel_state: Open, counterparty: PublicKey(025837416dcd1520de64858477381e5f7c127899489284b7cf9565ae4d927b503380c813bff475d8fff4ba07f2502e5c14db46571898340e2a37d6f2bb1f4d1a), created_at: 2023-07-26 4:57:57.0 +00:00:00, updated_at: 2023-07-30 5:12:46.0 +00:00:00 }]
| 2023-07-30 07:14:11.163 | LogLevel.DEBUG | Syncing 1 shadow channels
| 2023-07-30 07:14:11.163 | LogLevel.DEBUG | Inserting channel channel: Channel { user_channel_id: UserChannelId(594bc62c-93d8-401e-9105-3402e0aff5f4), channel_id: Some([222, 8, 212, 96, 138, 190, 163, 237, 188, 91, 139, 86, 223, 39, 198, 133, 210, 156, 218, 186, 4, 70, 190, 45, 203, 99, 247, 105, 64, 179, 124, 47]), inbound: 96353000, outbound: 89847000, funding_txid: Some(2f7cb34069f763cb2dbe4604bada9cd285c627df568b5bbceda3be8a60d408de), channel_state: Open, counterparty: PublicKey(025837416dcd1520de64858477381e5f7c127899489284b7cf9565ae4d927b503380c813bff475d8fff4ba07f2502e5c14db46571898340e2a37d6f2bb1f4d1a), created_at: 2023-07-26 4:57:57.0 +00:00:00, updated_at: 2023-07-30 5:14:11.162395 +00:00:00 }
| 2023-07-30 07:14:11.164 | LogLevel.DEBUG | Got all transactions transactions: []
| 2023-07-30 07:14:11.164 | LogLevel.DEBUG | Syncing 0 shadow transactions
| 2023-07-30 07:14:13.085 | LogLevel.INFO | Listening on <IP_ADDRESS>:53904
| 2023-07-30 07:14:13.086 | LogLevel.INFO | Starting background processor
| 2023-07-30 07:14:13.087 | LogLevel.TRACE | lightning_background_processor: Calling ChannelManager's timer_tick_occurred on startup
| 2023-07-30 07:14:13.088 | LogLevel.INFO | Lightning node started with node ID 03fa5268ee1d544f82df15d47cfe615b43b987d891eaba42def17ad0e85d1a69e1@<IP_ADDRESS>:53904
| 2023-07-30 07:14:13.089 | LogLevel.DEBUG | Broadcasting node announcement inc_connection_addresses: [IPv4 { addr: [0, 0, 0, 0], port: 53904 }]
| 2023-07-30 07:14:13.090 | LogLevel.DEBUG | lightning::ln::peer_handler: Broadcasting NodeAnnouncement after passing it to our own RoutingMessageHandler.
| 2023-07-30 07:14:13.091 | LogLevel.DEBUG | Setting up connection peer: 03507b924dae6595cfb78492489978127c5f1e3877848564de2015cd6d41375802@<IP_ADDRESS>:9045
| 2023-07-30 07:14:13.091 | LogLevel.DEBUG | Publishing event Init("10101 is ready.")
| 2023-07-30 07:14:13.092 | LogLevel.DEBUG | Forwarding event to flutter event: Init("10101 is ready.")
| 2023-07-30 07:14:13.093 | LogLevel.DEBUG | Parsing config from flutter config: Config { coordinator_pubkey: "03507b924dae6595cfb78492489978127c5f1e3877848564de2015cd6d41375802", esplora_endpoint: "http://<IP_ADDRESS>:3000", host: "<IP_ADDRESS>", p2p_port: 9045, http_port: 80, network: "regtest", oracle_endpoint: "http://<IP_ADDRESS>:8081", oracle_pubkey: "16f88cf7d21e6c0f46bcbc983a4e3b19726c6c98858cc31c83551a88fde171c0", health_check_interval_secs: 10 }
| 2023-07-30 07:14:13.093 | LogLevel.DEBUG | Broadcasting node announcement inc_connection_addresses: [IPv4 { addr: [0, 0, 0, 0], port: 53904 }]
| 2023-07-30 07:14:13.093 | LogLevel.INFO | Backend started
| 2023-07-30 07:14:13.094 | LogLevel.DEBUG | lightning::ln::peer_handler: Broadcasting NodeAnnouncement after passing it to our own RoutingMessageHandler.
| 2023-07-30 07:14:13.095 | LogLevel.DEBUG | Pruning expired orders
| 2023-07-30 07:14:13.095 | LogLevel.DEBUG | Got all spendable outputs outputs: []
| 2023-07-30 07:14:13.096 | LogLevel.DEBUG | Connecting to orderbook API
| 2023-07-30 07:14:13.096 | LogLevel.DEBUG | Publishing event ServiceHealthUpdate(ServiceUpdate { service: Orderbook, status: Online })
| 2023-07-30 07:14:13.097 | LogLevel.DEBUG | Forwarding event to flutter event: ServiceHealthUpdate(ServiceUpdate { service: Orderbook, status: Online })
| 2023-07-30 07:14:13.097 | LogLevel.DEBUG | Received event: Event.serviceHealthUpdate(field0: Instance of 'ServiceUpdate')
| 2023-07-30 07:14:13.400 | LogLevel.INFO | Built on commit: 75b4d72042da6d2c23304a3ee0a1acbaab2cccbb
| 2023-07-30 07:14:13.401 | LogLevel.INFO | Built on branch: main
| 2023-07-30 07:14:13.401 | LogLevel.DEBUG | Connection setup completed peer: 03507b924dae6595cfb78492489978127c5f1e3877848564de2015cd6d41375802@<IP_ADDRESS>:9045
| 2023-07-30 07:14:13.401 | LogLevel.DEBUG | Waiting to confirm established connection peer: 03507b924dae6595cfb78492489978127c5f1e3877848564de2015cd6d41375802@<IP_ADDRESS>:9045
| 2023-07-30 07:14:13.405 | LogLevel.INFO | Build number: 1726
| 2023-07-30 07:14:13.405 | LogLevel.INFO | Build version: 1.1.0
| 2023-07-30 07:14:13.405 | LogLevel.INFO | Network: regtest
| 2023-07-30 07:14:13.405 | LogLevel.INFO | Esplora endpoint: http://<IP_ADDRESS>:3000
| 2023-07-30 07:14:13.405 | LogLevel.INFO | Coordinator: 03507b924dae6595cfb78492489978127c5f1e3877848564de2015cd6d41375802@<IP_ADDRESS>:9045
| 2023-07-30 07:14:13.406 | LogLevel.INFO | Oracle endpoint: http://<IP_ADDRESS>:8081
| 2023-07-30 07:14:13.406 | LogLevel.INFO | Oracle PK: 16f88cf7d21e6c0f46bcbc983a4e3b19726c6c98858cc31c83551a88fde171c0
| 2023-07-30 07:14:13.406 | LogLevel.INFO | Node ID: 03fa5268ee1d544f82df15d47cfe615b43b987d891eaba42def17ad0e85d1a69e1
| 2023-07-30 07:14:13.406 | LogLevel.DEBUG | Last login was at 2023-07-28 18:06:00 +00:00:00
| 2023-07-30 07:14:13.792 | LogLevel.DEBUG | lightning::ln::peer_handler: Finished noise handshake for connection with 03507b924dae6595cfb78492489978127c5f1e3877848564de2015cd6d41375802
| 2023-07-30 07:14:13.793 | LogLevel.DEBUG | Publishing event ServiceHealthUpdate(ServiceUpdate { service: Coordinator, status: Online })
| 2023-07-30 07:14:13.794 | LogLevel.DEBUG | Forwarding event to flutter event: ServiceHealthUpdate(ServiceUpdate { service: Coordinator, status: Online })
| 2023-07-30 07:14:13.795 | LogLevel.DEBUG | Received event: Event.serviceHealthUpdate(field0: Instance of 'ServiceUpdate')
| 2023-07-30 07:14:13.796 | LogLevel.INFO | Connected to orderbook realtime API
| 2023-07-30 07:14:13.797 | LogLevel.DEBUG | New message from orderbook msg: {"AllOrders":[{"id":"2fa58622-a63d-48d7-b7fc-bdf0a0ff6a5d","price":29313.0,"trader_id":"03f75f318471d32d39be3c86c622e2c51bd5731bf95f98aaa3ed5d6e1c0025927f","taken":false,"direction":"Long","quantity":1000.0,"order_type":"Limit","timestamp":"2023-07-30T05:13:15.266566Z","expiry":"2023-07-30T05:14:15.265798Z"},{"id":"d3f8bcd0-dd12-401b-90aa-3b0295cd0159","price":29358.0,"trader_id":"03f75f318471d32d39be3c86c622e2c51bd5731bf95f98aaa3ed5d6e1c0025927f","taken":false,"direction":"Short","quantity":1000.0,"order_type":"Limit","timestamp":"2023-07-30T05:13:15.268641Z","expiry":"2023-07-30T05:14:15.267978Z"},{"id":"78253c63-de34-4921-9ec5-40bb8b02f2dc","price":29313.0,"trader_id":"03f75f318471d32d39be3c86c622e2c51bd5731bf95f98aaa3ed5d6e1c0025927f","taken":false,"direction":"Long","quantity":1000.0,"order_type":"Limit","timestamp":"2023-07-30T05:13:15.270614Z","expiry":"2023-07-30T05:14:15.270017Z"},{"id":"6d58a661-11e7-43be-99b7-c70ba87f4513","price":29358.0,"trader_id":"03f75f318471d32d39be3c86c622e2c51bd5731bf95f98aaa3ed5d6e1c0025927f","taken":false,"direction":"Short","quantity":1000.0,"order_type":"Limit","timestamp":"2023-07-30T05:13:15.272644Z","expiry":"2023-07-30T05:14:15.272002Z"},{"id":"6df6e03b-3cbb-4cab-a8c9-053e452e89c2","price":29313.0,"trader_id":"03f75f318471d32d39be3c86c622e2c51bd5731bf95f98aaa3ed5d6e1c0025927f","taken":false,"direction":"Long","quantity":1000.0,"order_type":"Limit","timestamp":"2023-07-30T05:13:15.274417Z","expiry":"2023-07-30T05:14:15.273889Z"},{"id":"45926aed-fcef-4882-9edd-b1bb03770c80","price":29358.0,"trader_id":"03f75f318471d32d39be3c86c622e2c51bd5731bf95f98aaa3ed5d6e1c0025927f","taken":false,"direction":"Short","quantity":1000.0,"order_type":"Limit","timestamp":"2023-07-30T05:13:15.276519Z","expiry":"2023-07-30T05:14:15.275968Z"},{"id":"e81ddd74-1660-4501-9371-d7ae6a28d492","price":29313.0,"trader_id":"03f75f318471d32d39be3c86c622e2c51bd5731bf95f98aaa3ed5d6e1c0025927f","taken":false,"direction":"Long","quantity":1000.0,"order_type":"Limit","timestamp":"2023-07-30T05:13:15.278753Z","expiry":"2023-07-30T05:14:15.278109Z"},{"id":"25d3189f-45b9-4a88-a1d5-bfeab9333945","price":29358.0,"trader_id":"03f75f318471d32d39be3c86c622e2c51bd5731bf95f98aaa3ed5d6e1c0025927f","taken":false,"direction":"Short","quantity":1000.0,"order_type":"Limit","timestamp":"2023-07-30T05:13:15.281134Z","expiry":"2023-07-30T05:14:15.280306Z"},{"id":"880a2943-1fb0-4879-8afd-8e8b16633d0f","price":29313.0,"trader_id":"03f75f318471d32d39be3c86c622e2c51bd5731bf95f98aaa3ed5d6e1c0025927f","taken":false,"direction":"Long","quantity":1000.0,"order_type":"Limit","timestamp":"2023-07-30T05:13:15.283569Z","expiry":"2023-07-30T05:14:15.282818Z"},{"id":"5b0af415-9657-49a1-908c-9ab77225e7fd","price":29358.0,"trader_id":"03f75f318471d32d39be3c86c622e2c51bd5731bf95f98aaa3ed5d6e1c0025927f","taken":false,"direction":"Short","quantity":1000.0,"order_type":"Limit","timestamp":"2023-07-30T05:13:15.28595Z","expiry":"2023-07-30T05:14:15.28528Z"}]}
| 2023-07-30 07:14:13.798 | LogLevel.DEBUG | Received all orders from orderbook orders: []
| 2023-07-30 07:14:13.798 | LogLevel.DEBUG | Updating prices prices: {BtcUsd: Price { bid: Some(29313), ask: Some(29358) }}
| 2023-07-30 07:14:13.799 | LogLevel.DEBUG | Publishing event PriceUpdateNotification({BtcUsd: Price { bid: Some(29313), ask: Some(29358) }})
| 2023-07-30 07:14:13.800 | LogLevel.DEBUG | Forwarding event to flutter event: PriceUpdateNotification({BtcUsd: Price { bid: Some(29313), ask: Some(29358) }})
| 2023-07-30 07:14:14.193 | LogLevel.INFO | lightning::ln::peer_handler: Received peer Init message from 03507b924dae6595cfb78492489978127c5f1e3877848564de2015cd6d41375802: DataLossProtect: supported, InitialRoutingSync: not supported, UpfrontShutdownScript: supported, GossipQueries: supported, VariableLengthOnion: required, StaticRemoteKey: required, PaymentSecret: required, BasicMPP: supported, Wumbo: supported, AnchorsZeroFeeHtlcTx: not supported, ShutdownAnySegwit: supported, OnionMessages: not supported, ChannelType: supported, SCIDPrivacy: supported, ZeroConf: supported, unknown flags: none
| 2023-07-30 07:14:14.194 | LogLevel.DEBUG | lightning::ln::channelmanager: Generating channel_reestablish events for 03507b924dae6595cfb78492489978127c5f1e3877848564de2015cd6d41375802
| 2023-07-30 07:14:14.195 | LogLevel.TRACE | lightning::ln::channel: Enough info to generate a Data Loss Protect with per_commitment_secret fc4059cb2a324bbade34d9c9bd6c1a4fe0ecd258475988be8024573083ad99e4 for channel de08d4608abea3edbc5b8b56df27c685d29cdaba0446be2dcb63f76940b37c2f
| 2023-07-30 07:14:14.196 | LogLevel.TRACE | lightning_background_processor: Persisting ChannelManager...
| 2023-07-30 07:14:14.197 | LogLevel.DEBUG | New message from orderbook msg: "Authenticated"
| 2023-07-30 07:14:14.197 | LogLevel.DEBUG | Skipping message from orderbook msg: Authenticated
| 2023-07-30 07:14:14.199 | LogLevel.DEBUG | lightning::ln::peer_handler: Handling SendChannelReestablish event in peer_handler for node 03507b924dae6595cfb78492489978127c5f1e3877848564de2015cd6d41375802 for channel de08d4608abea3edbc5b8b56df27c685d29cdaba0446be2dcb63f76940b37c2f
| 2023-07-30 07:14:14.205 | LogLevel.TRACE | lightning_background_processor: Done persisting ChannelManager.
| 2023-07-30 07:14:14.392 | LogLevel.INFO | Connection established peer: 03507b924dae6595cfb78492489978127c5f1e3877848564de2015cd6d41375802@<IP_ADDRESS>:9045
| 2023-07-30 07:14:15.018 | LogLevel.TRACE | lightning::ln::channel: Creating an announcement_signatures message for channel de08d4608abea3edbc5b8b56df27c685d29cdaba0446be2dcb63f76940b37c2f
| 2023-07-30 07:14:15.019 | LogLevel.TRACE | lightning::ln::channel: Ignore : Channel is not available for public announcements
| 2023-07-30 07:14:15.020 | LogLevel.DEBUG | lightning::ln::channel: Reconnected channel de08d4608abea3edbc5b8b56df27c685d29cdaba0446be2dcb63f76940b37c2f with no loss
| 2023-07-30 07:14:15.021 | LogLevel.TRACE | lightning::ln::channelmanager: Attempting to generate channel update for channel de08d4608abea3edbc5b8b56df27c685d29cdaba0446be2dcb63f76940b37c2f
| 2023-07-30 07:14:15.022 | LogLevel.TRACE | lightning::ln::channelmanager: Generating channel update for channel de08d4608abea3edbc5b8b56df27c685d29cdaba0446be2dcb63f76940b37c2f
| 2023-07-30 07:14:15.022 | LogLevel.TRACE | lightning::ln::channelmanager: Handling channel resumption for channel de08d4608abea3edbc5b8b56df27c685d29cdaba0446be2dcb63f76940b37c2f with no RAA, no commitment update, 0 pending forwards, not broadcasting funding, without channel ready, without announcement
| 2023-07-30 07:14:15.023 | LogLevel.TRACE | lightning_background_processor: Persisting ChannelManager...
| 2023-07-30 07:14:15.024 | LogLevel.TRACE | lightning::ln::channel: Updating HTLC state for a newly-sent commitment_signed...
| 2023-07-30 07:14:15.025 | LogLevel.TRACE | lightning::ln::channel: Building commitment transaction number<PHONE_NUMBER>10618 (really 37 xor<PHONE_NUMBER>50067) for channel de08d4608abea3edbc5b8b56df27c685d29cdaba0446be2dcb63f76940b37c2f for remote, generated by us with fee 253...
| 2023-07-30 07:14:15.026 | LogLevel.TRACE | lightning::ln::channel:    ...including to_remote output with value 98070
| 2023-07-30 07:14:15.026 | LogLevel.TRACE | lightning::ln::channel:    ...including to_local output with value 91747
| 2023-07-30 07:14:15.026 | LogLevel.TRACE | lightning::chain::chainmonitor: Updating ChannelMonitor for channel de08d4608abea3edbc5b8b56df27c685d29cdaba0446be2dcb63f76940b37c2f
| 2023-07-30 07:14:15.027 | LogLevel.INFO | lightning::chain::channelmonitor: Applying update to monitor de08d4608abea3edbc5b8b56df27c685d29cdaba0446be2dcb63f76940b37c2f, bringing update_id from 96 to 97 with 1 changes.
| 2023-07-30 07:14:15.027 | LogLevel.TRACE | lightning::chain::channelmonitor: Updating ChannelMonitor with latest counterparty commitment transaction info
| 2023-07-30 07:14:15.028 | LogLevel.TRACE | lightning::chain::channelmonitor: Tracking new counterparty commitment transaction with txid 0fc441a898126973f433c2016efd635a9522b3cccf95801de551ad1513fa25b4 at commitment number<PHONE_NUMBER>10618 with 0 HTLC outputs
| 2023-07-30 07:14:15.031 | LogLevel.TRACE | lightning_background_processor: Done persisting ChannelManager.
| 2023-07-30 07:14:15.032 | LogLevel.DEBUG | lightning::chain::chainmonitor: Persistence of ChannelMonitorUpdate for channel de08d4608abea3edbc5b8b56df27c685d29cdaba0446be2dcb63f76940b37c2f completed
| 2023-07-30 07:14:15.032 | LogLevel.TRACE | lightning::ln::channel: Creating an announcement_signatures message for channel de08d4608abea3edbc5b8b56df27c685d29cdaba0446be2dcb63f76940b37c2f
| 2023-07-30 07:14:15.033 | LogLevel.TRACE | lightning::ln::channel: Ignore : Channel is not available for public announcements
| 2023-07-30 07:14:15.033 | LogLevel.TRACE | lightning::ln::channel: Regenerated latest commitment update in channel de08d4608abea3edbc5b8b56df27c685d29cdaba0446be2dcb63f76940b37c2f with 0 update_adds, 0 update_fulfills, 0 update_fails, and 0 update_fail_malformeds
| 2023-07-30 07:14:15.034 | LogLevel.TRACE | lightning::ln::channel: Building commitment transaction number<PHONE_NUMBER>10618 (really 37 xor<PHONE_NUMBER>50067) for channel de08d4608abea3edbc5b8b56df27c685d29cdaba0446be2dcb63f76940b37c2f for remote, generated by us with fee 253...
| 2023-07-30 07:14:15.034 | LogLevel.TRACE | lightning::ln::channel:    ...including to_remote output with value 98070
| 2023-07-30 07:14:15.034 | LogLevel.TRACE | lightning::ln::channel:    ...including to_local output with value 91747
| 2023-07-30 07:14:15.035 | LogLevel.TRACE | lightning::ln::channel: Signed remote commitment tx<PHONE_NUMBER>de08d4608abea3edbc5b8b56df27c685d29cdaba0446be2dcb63f76940b37c2f00000000003685f780026366010000000000160014fab788e4c1921ace81ad85b16b47527d8857fb92167f0100000000002200205b20f1e7b435ac8dfb7a37d655c5286670c1f062df05d54b0554cd376f17916556aed620 (txid 0fc441a898126973f433c2016efd635a9522b3cccf95801de551ad1513fa25b4) with redeemscript<PHONE_NUMBER>bc88fbeeaf34e8a0d225aa23bd54317a9ab7db4833da4501cc9ceffa11dd362103d76d2ca47215e5fa1e36757a911719c5651b0e5c9cfc752b4e976594f8b4843c52ae with value 190000 -> 4f8db3e61399f3be4140cf344a94f9b28c6c443dfe0c1430e2abe970d35ed47203346b9940012f8a51fa8a8e41491bda1566e26477558641e20a23f735561e06 in channel de08d4608abea3edbc5b8b56df27c685d29cdaba0446be2dcb63f76940b37c2f
| 2023-07-30 07:14:15.035 | LogLevel.DEBUG | lightning::ln::channel: Restored monitor updating in channel de08d4608abea3edbc5b8b56df27c685d29cdaba0446be2dcb63f76940b37c2f resulting in a commitment update and no RAA, with RAA first
| 2023-07-30 07:14:15.036 | LogLevel.TRACE | lightning::ln::channel: Building commitment transaction number<PHONE_NUMBER>10619 (really 36 xor<PHONE_NUMBER>50067) for channel de08d4608abea3edbc5b8b56df27c685d29cdaba0446be2dcb63f76940b37c2f for us, generated by remote with fee 253...
| 2023-07-30 07:14:15.036 | LogLevel.TRACE | lightning::ln::channel:    ...including to_local output with value 91747
| 2023-07-30 07:14:15.037 | LogLevel.TRACE | lightning::ln::channel:    ...including to_remote output with value 98070
| 2023-07-30 07:14:15.037 | LogLevel.TRACE | lightning::ln::channel: Checking commitment tx signature 5b5febc89948029ae09baf243baea1443e0b6bfc9f2d6dfd56dde2d0b19da0b6148dbd28cc0bbe940929dab9d98cdc6bb59b1cd9816d49430779254698002420 by key 03d76d2ca47215e5fa1e36757a911719c5651b0e5c9cfc752b4e976594f8b4843c against tx<PHONE_NUMBER>de08d4608abea3edbc5b8b56df27c685d29cdaba0446be2dcb63f76940b37c2f00000000003685f78002636601000000000022002000979af0049e96c24baa1f8587760a465452622d9c706513fe479e192d157418167f010000000000160014d8ff4571872efd004c851d1a4f5e8b2c4e90413a57aed620 (sighash ed60195cf8c1c6c52b50286be5fb1db83eb3151cb10f81c5144ec6644cbcd650) with redeemscript<PHONE_NUMBER>bc88fbeeaf34e8a0d225aa23bd54317a9ab7db4833da4501cc9ceffa11dd362103d76d2ca47215e5fa1e36757a911719c5651b0e5c9cfc752b4e976594f8b4843c52ae in channel de08d4608abea3edbc5b8b56df27c685d29cdaba0446be2dcb63f76940b37c2f
| 2023-07-30 07:14:15.038 | LogLevel.ERROR | lightning::ln::channelmanager: Closing channel de08d4608abea3edbc5b8b56df27c685d29cdaba0446be2dcb63f76940b37c2f due to close-required error: Invalid commitment tx signature from peer
| 2023-07-30 07:14:15.038 | LogLevel.DEBUG | lightning::ln::channelmanager: Finishing force-closure of channel with 0 HTLCs to fail
| 2023-07-30 07:14:15.039 | LogLevel.TRACE | lightning::chain::chainmonitor: Updating ChannelMonitor for channel de08d4608abea3edbc5b8b56df27c685d29cdaba0446be2dcb63f76940b37c2f
| 2023-07-30 07:14:15.039 | LogLevel.INFO | lightning::chain::channelmonitor: Applying update to monitor de08d4608abea3edbc5b8b56df27c685d29cdaba0446be2dcb63f76940b37c2f, bringing update_id from 97 to 98 with 1 changes.
| 2023-07-30 07:14:15.039 | LogLevel.TRACE | lightning_background_processor: Persisting ChannelManager...
| 2023-07-30 07:14:15.040 | LogLevel.TRACE | lightning::chain::channelmonitor: Updating ChannelMonitor: channel force closed, should broadcast: true
| 2023-07-30 07:14:15.040 | LogLevel.DEBUG | lightning::chain::channelmonitor: Getting signed latest holder commitment transaction!
| 2023-07-30 07:14:15.040 | LogLevel.INFO | lightning::chain::channelmonitor: Broadcasting local commitment tx with txid 72b4278fff3b6fa1398b794e4307693ecdd7ecc685747b7e94b3c36ac1923cac
| 2023-07-30 07:14:15.041 | LogLevel.INFO | Broadcasting transaction raw_tx:<PHONE_NUMBER>010186ed5436e30e6a021adceaabe791bfa477e24a022151c2a52ee6512bd957c3f000000000003685f78002216c000000000000160014d8ff4571872efd004c851d1a4f5e8b2c4e90413a171f010000000000220020eb31bbee2e4fe796f94166f2541b5b11ad14583440fcbad991b643c936846d74040047304402206eb7c0ac5bbaecd33c73acca164411d3d93310abf875c8c23fc6d144aa7d87de02206723395f2a65c8859fe49109af793467c8b949a0e7dac733f3d0f9c3e81fdc1e014730440220332fde6289db3e70a6434ffe4f3967b17b693818c47645d760f1b9830266f85f0220750da2adad6316b350d67cfdc4b20f4ba595f0ed62838726cf71dbaed669e06a014752210360bc88fbeeaf34e8a0d225aa23bd54317a9ab7db4833da4501cc9ceffa11dd362103d76d2ca47215e5fa1e36757a911719c5651b0e5c9cfc752b4e976594f8b4843c52ae50aed620,txid: 72b4278fff3b6fa1398b794e4307693ecdd7ecc685747b7e94b3c36ac1923cac
| 2023-07-30 07:14:15.297 | LogLevel.DEBUG | New message from orderbook msg: {"DeleteOrder":"2fa58622-a63d-48d7-b7fc-bdf0a0ff6a5d"}

@holzeis : I've taken over your branch and made some changes. The test runs now. I hope I did not change the logic but I think this ticket is no bug anymore and works with latest main.

@holzeis : I've taken over your branch and made some changes. The test runs now. I hope I did not change the logic but I think this ticket is no bug anymore and works with latest main.

Nice, did you verify that the test fails on an older version. I am curious what commit exactly fixed it 🙂

Nice, did you verify that the test fails on an older version. I am curious what commit exactly fixed it 🙂

yes, the test was failing on an older version. Check the diff, I left the fixup commit in the PR for you to see what I changed .


Use shadow helium api

Issue

Link:
https://github.com/NebraLtd/hm-config/issues/195
https://github.com/NebraLtd/maker-starter-app/issues/143

Summary:
Use a private Helium API to get the Hotpot details reliably.

How

Screenshots

References

Checklist

[ ] Tests added
[ ] Cleaned up commit history (rebase!)
[ ] Documentation added
[ ] Thought about variable and method names

Will these error messages be displayed to the user? I guess this is the follow up ticket to fix that behavior? #143

Right


Create a data flow diagram for FAM

Describe the task
Create a business process diagram for FAM that illustrates how data flows
Acceptance Criteria

[ ] create a draft
[ ] show to Michelle
[ ] Post on confluence/github wiki

Additional context

Add any other context about the task here.
Who is the audience for this diagram, what will they use it for?
This is for business data in a security app

Data flow not applicable for an RBAC application.


Check Windows SDK version to use '/permissive-' flag only when supported

When building on Windows, this change makes sure we don't set '/permissive-' flag with older Windows SDK that don't support it and cause compilation errors in some sdk headers.
Fixes #36671

IMO it's better to just remove the flag, we can re-add it with proper checks if we actually need it.
GCC and Clang should already be restrictive enough on CI checks.

Ok, sounds good. I'll make a new PR to remove the flag completely then.


[AIRFLOW-283] Make store_to_xcom_key a templated field in GoogleCloudStorageDownloadOperator

Dear Airflow Maintainers,
Please accept this PR that addresses the following issues:

https://issues.apache.org/jira/browse/AIRFLOW-283

Testing Done:
Reminders for contributors:

Your PR's title must reference an issue on Airflow's JIRA. For example, a PR called "[AIRFLOW-1] My Amazing PR" would close JIRA issue #1. Please open a new issue if required!
Please squash your commits when possible and follow the 7 rules of good Git commits.

Please rebase. Looks like you never rebased after your merge was squashed.


missing highlights in .cu files

The following are not highlighted/recognized, though some of them might arguably not make sense to highlight:
<<< , >>> kernel launch parameter brackets
float2, float3 ... uint2, uint2 ... int3 ... dim3.. types
__device__ __host__ function qualifiers

Also global should be highlighted