KeyError: "The following input nodes were not found: set(['Mul'])\n"

I have a model named rounded_graph.pb that's been produced from the TensorFlow for Poets codelab. Then I should strip the DecodeJpeg Op from model by the following command :
python strip_unused.py --input_graph=rounded_graph.pb --output_graph=output.pb --input_node_names="Mul" --output_node_names="final_result" --input_binary=true
But I got the following error :
File "strip_unused.py", line 107, in
app.run(main=main, argv=[sys.argv[0]] + unparsed)
File "/home/eli/.local/lib/python2.7/site-packages/tensorflow/python/platform/app.py", line 126, in run
_sys.exit(main(argv))
File "strip_unused.py", line 61, in main
FLAGS.placeholder_type_enum)
File "/home/eli/.local/lib/python2.7/site-packages/tensorflow/python/tools/strip_unused_lib.py", line 114, in strip_unused_from_files
placeholder_type_enum)
File "/home/eli/.local/lib/python2.7/site-packages/tensorflow/python/tools/strip_unused_lib.py", line 83, in strip_unused
raise KeyError("The following input nodes were not found: %s\n" % not_found)
KeyError: "The following input nodes were not found: set(['Mul'])\n"
eli@eli-virtual-machine:~/Documents/tensorflow-master/tensorflow/python/tools$ python strip_unused.py --input_graph=optimized_graph.pb --output_graph=output.pb --input_node_names="Mul" --output_node_names="final_result" --input_binary=true
Traceback (most recent call last):
File "strip_unused.py", line 107, in
app.run(main=main, argv=[sys.argv[0]] + unparsed)
File "/home/eli/.local/lib/python2.7/site-packages/tensorflow/python/platform/app.py", line 126, in run
_sys.exit(main(argv))
File "strip_unused.py", line 61, in main
FLAGS.placeholder_type_enum)
File "/home/eli/.local/lib/python2.7/site-packages/tensorflow/python/tools/strip_unused_lib.py", line 114, in strip_unused_from_files
placeholder_type_enum)
File "/home/eli/.local/lib/python2.7/site-packages/tensorflow/python/tools/strip_unused_lib.py", line 83, in strip_unused
raise KeyError("The following input nodes were not found: %s\n" % not_found)
KeyError: "The following input nodes were not found: set(['Mul'])\n"
If I don't do this before moving the model to APP, "Error initializing TensorFlow" will happen when APP run.
What should I do? Please help me, thanks!

I got the error: APP use the inceptionv3 model ,but TensorFlow for Poets codelab have updated the model from inceptionv3 to mobilenet. So error happened.

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

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

/CC @wolffg any ideas? Maybe this is more suited to StackOverflow.

Mark, do you have insight here?

If you are getting an error KeyError: "The following input nodes were not found: {'input'}\n" then change "input" to "Mul"
If anybody still has doubt refer TensorFlow on Mobile: Tutorial

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

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

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

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

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

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

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

if the Protocol Buffer file is created by retrain.py, change the input node name to "Placeholder".
my graph optimized successfully by doing so.

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

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

I'm going to close this, as we have a vastly different converter at this point.


Create an Issue Template.

Description
This issue aims to establish a standardized issue template for this repository. Issue templates serve as essential guidelines for users and contributors when creating new issues, ensuring that relevant information is consistently provided. By implementing a well-defined template, we can streamline issue creation, enhance issue tracking, and improve communication within the repository.
This issue will involve:

Defining the template's structure
Outlining the required content
Establishing guidelines for use

We will also seek input and feedback from the community to ensure that the issue template aligns with our project's needs and goals.
Goal
The goal of this issue is to create a structured and consistent issue template that benefits both the project maintainers and the community by improving issue reporting and tracking.

We can do this later on because this will create a bottleneck for new contributors


Update Validator.php

What's the problem it's trying to fix?

It's jQuery.
$('#country').value = undefined (always)
$('#country').val() = input value

Thanks!


Allow ignore of directories

Before this commit, any line under the [ignore] section of .zod/config matched only filenames, not directory names.  This commit allows the user to indicate whole directories to ignore.  The user does
this by ending the name spec with /.
For instance, using the snippet
[ignore]
Makefile
.hide/

in .zod/config will cause zod to ignore files matching Makefile and directories matching .hide.
Additionally, directories matching .zod and .git are already ignored by default (as a convenience to the user).

Hi Chase!
The idea behind this change -- which you will have gathered for yourself quickly, but I state here anyway for completeness sake -- is that, when the user indicates a directory spec in the [ignore] section (like hide/), zod will, in part, emit a find command which looks like this
find "site" -type d \( -name ".zod" -o -name ".git" -o -name ".hide" \) -prune -o -type f \(  ! -name "helpers.awk" ! -name "*.partial" ! -name "*.layout" ! -name "*.meta" ! -name "*.html" ! -name "*.md" ! -name "*.htm" \) -exec zod-copy "/usr/local/lib/zodiac" "site" "www" {} \;

as opposed to the current behavior which would emit something like
find "site" -type f \(  ! -name "helpers.awk" ! -name "*.partial" ! -name "*.layout" ! -name "*.meta" ! -name "*.html" ! -name "*.md" ! -name "*.htm" \) -exec zod-copy "/usr/local/lib/zodiac" "site" "www" {} \;

the difference being the addition of the
-type d \( -name ".zod" -o -name ".git" -o -name ".hide" \) -prune -o

part (clause).
If you like this method and accept it -- I hope you do -- you should be able also to close the related PR #2 and then: no more open PRs.  \o/
Also, it was good to get rid of config as an [ignore] spec on the off-chance that zod-copy needed to copy, say, some site resource file named config.
I tried to be thorough (including updating the doc), but please edit/correct anything I missed.
Cheers, --Rick

Bump.  (I hope this finds you well and enjoying your summer!)

I'll need to try these changes locally, but looks good.


Consistently use tuples instead of lists for actions

Actions are converted to tuples, but ['guard'] is returned for invalid ones. Replace it with ('guard',).

lgtm


Fix Linting

The ruff linting is out of date and throwing some errors that are unnecessary. There are also lots of places where the code does not pass the linting. This issue is to track fixing the linting for this repo.

@jacobbieker sir, i want to work on it can you please assign me this issue ?

Sure!


CI for rust code?

It is a good practice to run:

cargo fmt --check
cargo clippy
on CI runs.

One more thing, Rust CI should run only when Rust code is changed.
I that's fine - I can send a PR.

Yes please!


block eligibility check failed - err: proof counter must be less than number of eligible blocks

Description
A user reported that their testnet smesher, which had been working fine, suddenly got stuck at layer 4716. In the logs I see this error, which I've never seen before:
2020-12-09T17:41:39.394+0800    ERROR   13a23.sync         .blockFetchQueue     block fast validation failed    {"node_id": "13a234e7bd06ad22bebd2a4e94bae5496d3f5877a62775f8ebeb9ae11c928553", "block_id": "c5606952a6", "layer_id": 4649, "epoch_id": 16, "miner_id": "6be39", "view_edges": 54, "vote_count": 498, "atx_id": "b5a20f86ab95a800b879d85613439c5f47af4d90fe07324489f0883c3d7f8850", "eligibility_counter": 90, "ref_block": "e9dd250616", "active_set": 0, "tx_count": 0, "errmsg": "block eligibility check failed - err: proof counter (90) must be less than number of eligible blocks (90), activeset 159"}
Full logfile: https://drive.google.com/file/d/1LcC4xXrrWOeXtI9A6b1A__JfRJ4opL0S/view?usp=sharing
Environment
App version: v0.1.17. Git: HEAD - 5f1237a7ee06884d55712faf04655b064fe49225 . Go Version: go1.15.3. OS: windows-amd64

Another user reported this issue. He said his node was "stuck syncing layer 4688 for a few hours now" but that after restarting the app it continued syncing


There's a retain cycle problem that causes memory leaks in AMTagListView

Brief intro
My app uses your control on each view controller in UIPageViewController. Recently, I detected that there’s a memory leak when scrolling in PageViewController.
I’ve used CRChecker to detect possible retain cycles and troublesome controls, and the analysis indeed shows that your control definitely has this problem.
Possible sources
After brief source inspection I detected few possible sources:

- [AMTagListView setup] contains this code:
  self.orientationNotification = [center addObserverForName:UIDeviceOrientationDidChangeNotification object:nil queue:nil usingBlock:^(NSNotification *note) {
      [self rearrangeTags];
  }];
      self.tagNotification = [center addObserverForName:AMTagViewNotification object:nil queue:nil usingBlock:^(NSNotification *notification) {
      if (self == notification.userInfo[@"superview"]) {
          if (_tapHandler) {
              self.tapHandler(notification.object);
          }
      }
  }];

- [AMTagListView rearrangeTags]  contains this one:
  [self.tags enumerateObjectsUsingBlock:^(AMTagView* obj, NSUInteger idx, BOOL *stop) {
  size = obj.frame.size;
  [self.subviews enumerateObjectsUsingBlock:^(UIView* obj, NSUInteger idx, BOOL *stop) {
      if ([obj isKindOfClass:[AMTagView class]]) {
          maxY = MAX(maxY, obj.frame.origin.y);
      }
  }];

  [self.subviews enumerateObjectsUsingBlock:^(UIView* obj, NSUInteger idx, BOOL *stop) {
      if ([obj isKindOfClass:[AMTagView class]]) {
          if (obj.frame.origin.y == maxY) {
              maxX = MAX(maxX, obj.frame.origin.x + obj.frame.size.width);
          }
      }
  }];

  // Go to a new line if the tag won't fit
  if (size.width + maxX > (self.frame.size.width - self.marginX)) {
      maxY += size.height + self.marginY;
      maxX = 0;
  }
  obj.frame = (CGRect){maxX + self.marginX, maxY, size.width, size.height};
      [self addSubview:obj];
  }];

There is link to self in both - [NSNotificationCenter addObserverForName:object:queue:usingBlock] and [NSArray enumerateObjectsUsingBlock:].
And blocks always retain all captured variables.
So now we have a strong reference to AMTagListView that keeps that object in memory until the block object is deallocated.
Possible solution
You should pass weak pointers to self, instead of strong ones.
But …
I’m not sure that the problem is limited to these two cases, so you should check your code further for any other possible sources of memory leaks.

@Skogetroll something like this, right?
    __weak AMTagListView *weakSelf = self;
    self.orientationNotification = [center addObserverForName:UIDeviceOrientationDidChangeNotification object:nil queue:nil usingBlock:^(NSNotification *note) {
        [weakSelf rearrangeTags];
    }];
    self.tagNotification = [center addObserverForName:AMTagViewNotification object:nil queue:nil usingBlock:^(NSNotification *notification) {
        if (weakSelf == notification.userInfo[@"superview"]) {
            if (_tapHandler) {
                weakSelf.tapHandler(notification.object);
            }
        }
    }];

Weird that something like this flew over my head. So weird that I had to checkout the git blame and.... Yep, that was me. :smile:
I'll fix it asap, thanks for the heads up


Annotation for listeners

This may be a duplicate, but I did not find such a question. Is it possible to use annotations to better handle listeners, something like in RabbitMQ?
Example:
@RabbitListener(queues = "${name}")
public void receiveMessage(Object message, Channel channel) {
// do something
}

Thank you!

Does this annotation work only in Spring application?

Yep'org.springframework.amqp', name: 'spring-rabbit'


Add documentation on how to do a multi-key transaction with the CLI

A common use case for administrators is to share keys amongst multiple parties for the control of an account. While it's possible with the CLI to build up this transaction by getting signatures from each key, it's not well documented and should be added to the Transactions section.

Issue already solved.


Refactoring

As a developer i want to work with clean and structured code in order to implement new features faster and easier.
Key Areas:

Buttons
Elements
Images
Toolbar
popup

ca. 8-10h
ca. 13 story points

0h
0P


Approving managed private endpoint for SQL times out

Bicep version
v0.24.24
Describe the bug
When approving a private endpoint connection on Azure SQL server for a Data Factory managed private endpoint the command successfully approves the connection, Data Factory also shows the connection state as approved but the command never exits resulting in a timeout.
To Reproduce
create a managed private endpoint for Azure SQL in Data Factory.
use a module to get the SQL private endpoint connections:
param sqlServerName string

resource sqlServer 'Microsoft.Sql/servers@2023-05-01-preview' existing = {
  name: sqlServerName
}

module approveEndpoint 'module.privateEndpointConnections.bicep' = {
  name: 'approve-sql-endpoint'
  params: {
    endpointArray:  sqlServer.properties.privateEndpointConnections
    sqlServerName: sqlServer.name
  }
}

use a second module to read the connection info and approve
param endpointArray array

param sqlServerName string

resource sqlServer 'Microsoft.Sql/servers@2023-05-01-preview' existing = {
  name: sqlServerName
}

var privateEndpoint = [for pep in endpointArray: {
  status: pep.properties.privateLinkServiceConnectionState.status
  name: last(split(pep.id, '/'))
}
]

resource privateEndpointConnection 'Microsoft.Sql/servers/privateEndpointConnections@2023-05-01-preview' = [for endpoint in privateEndpoint: if (endpoint.status != 'Approved') {
  name: endpoint.name
  parent: sqlServer
  properties: {
    privateLinkServiceConnectionState: {
      status: 'Approved'
      description: 'Approved by pipeline'
    }
  }
}]
resource privateEndpointConnection 'Microsoft.Sql/servers/privateEndpointConnections@2023-05-01-preview' = [for endpoint in privateEndpoint: if (endpoint.status != 'Approved') {
  name: endpoint.name
  parent: sqlServer
  properties: {
    privateLinkServiceConnectionState: {
      status: 'Approved'
      description: 'Approved by pipeline'
    }
  }
}]

use az cli to deploy the template:
az deployment group create -g $resourceGroup -n $name -f $bicepFile
I have tested hard coding the endpoint name which results in the same deployment error:
"The resource provision operation did not complete within the allowed timeout period.".
For reference this is the storage account code which works:
module to get the private endpoint connections:
param storageAccountName string

resource storageAccount 'Microsoft.Storage/storageAccounts@2023-01-01' existing = {
  name: storageAccountName
}

module approveEndpoint 'module.privateEndpointConnections.bicep' = {
  name: 'approve-storage-endpoint'
  params: {
    endpointArray:  storageAccount.properties.privateEndpointConnections
    storageAccountName: storageAccount.name
  }
}

use a second module to read the connection info and approve
param endpointArray array

param storageAccountName string

resource storageAccount 'Microsoft.Storage/storageAccounts@2023-01-01' existing = {
  name: storageAccountName
}

var privateEndpoint = [for pep in endpointArray:  {
  status: pep.properties.privateLinkServiceConnectionState.status
  name:  pep.name
}
]

resource privateEndpointConnection 'Microsoft.Storage/storageAccounts/privateEndpointConnections@2023-01-01' = [for endpoint in privateEndpoint : if(endpoint.status != 'Approved') {
  name: endpoint.name
  parent: storageAccount
  properties: {
    privateLinkServiceConnectionState: {
      status: 'Approved'
      description: 'Approved by pipeline'
    }
  }
}]

I did notice the output for storage private endpoint connections contains a name property which is not in the sql output.
Additional context
If I use cli az network private-endpoint-connection approve this works fine.

Opened a support ticket in Azure TrackingID#2402090030000035

Update from Microsoft regarding this issue:
Incident Title:  Issue with Azure SQL Server Private Connection
Incident Summary:
The incident started on Feb 9, 2024. It affected the SQL server [iverxue-logisql] and disrupted its normal operation. This incident did not allow resources to be deployed due to a continuous "Ready" status response which caused ARM deployment jobs to go past their allowed timeout period.
Analysis and Mitigation:
Investigations show that a provisioningState value of "Ready" was continuously returned which is seen as a non-terminal state and resulted in the ARM deployment jobs running over the allowed timeout period. These jobs were expecting a terminal state of "Succeeded" for successful resource provision. The issue was fixed via a reconfiguration of the SQL server and private endpoint connections.
Next Steps:
To avoid repeats of this issue in the future, steps have been put in place to ensure operations run smoothly and that the "Ready" status does not cause the ARM deployment jobs to overrun their timeout period. We have created a repair item to fix this issue. We assure you that we are doing our best to provide the highest quality service and will address this incident accordingly. We are sorry for this disruption, and we appreciate your understanding.

New update from Microsoft:


Add calculuswhiz/Assembly-Syntax-Definition grammar and use it for Unix Assembly

Checklist:

[ ] I am associating a language with a new file extension.

[ ] The new extension is used in hundreds of repositories on GitHub.com

Search results for each extension:

https://github.com/search?utf8=✓&type=Code&ref=searchresults&q=extension%3AFOOBAR+KEYWORDS+NOT+nothack

[ ] I have included a real-world usage sample for all extensions added in this PR:

Sample source(s):

[URL to each sample source, if applicable]

Sample license(s):

[ ] I have included a change to the heuristics to distinguish my language from others using the same extension.

[ ] I am adding a new language.

[ ] The extension of the new language is used in hundreds of repositories on GitHub.com.

Search results for each extension:

https://github.com/search?utf8=✓&type=Code&ref=searchresults&q=extension%3AFOOBAR+KEYWORDS+NOT+nothack

[ ] I have included a real-world usage sample for all extensions added in this PR:

Sample source(s):

[URL to each sample source, if applicable]

Sample license(s):

[ ] I have included a syntax highlighting grammar.
[ ] I have included a change to the heuristics to distinguish my language from others using the same extension.

[ ] I am fixing a misclassified language

[ ] I have included a new sample for the misclassified language:

Sample source(s):

[URL to each sample source, if applicable]

Sample license(s):

[ ] I have included a change to the heuristics to distinguish my language from others using the same extension.

[x] I am changing the source of a syntax highlighting grammar

Old: https://github-lightshow.herokuapp.com/?utf8=✓&scope=source.assembly&grammar_format=auto&grammar_url=&grammar_text=&code_source=from-url&code_url=https%3A%2F%2Fraw.githubusercontent.com%2Ftorvalds%2Flinux%2Fmaster%2Farch%2Fx86%2Fentry%2Fentry_32.S&code=
New: https://github-lightshow.herokuapp.com/?utf8=✓&scope=from-url&grammar_format=auto&grammar_url=https%3A%2F%2Fraw.githubusercontent.com%2Fcalculuswhiz%2FAssembly-Syntax-Definition%2Fmaster%2FAssembly%2520x86%2520AT%2526T.tmLanguage&grammar_text=&code_source=from-url&code_url=https%3A%2F%2Fraw.githubusercontent.com%2Ftorvalds%2Flinux%2Fmaster%2Farch%2Fx86%2Fentry%2Fentry_32.S&code=

[ ] I am adding new or changing current functionality

[ ] I have added or updated the tests for the new or changed functionality.

Thanks for submitting the pull reqtest!
Please fill in the template; it's there for a reason.

Also I forgot to run script/list-grammers, I'll take care of that.


Crunchyroll missing thumbnail fix

When thumbnail is missing returning json skips it instead of the NoneType error
Template

Before submitting a pull request make sure you have:

[x] At least skimmed through contributing guidelines including yt-dlp coding conventions
[x] Searched the bugtracker for similar pull requests
[ ] Checked the code with flake8 and ran relevant tests

In order to be accepted and merged into yt-dlp each piece of code must be in public domain or released under Unlicense. Check one of the following options:

[x] I am the original author of this code and I am willing to release it under Unlicense
[ ] I am not the original author of this code but it is in public domain or released under Unlicense (provide reliable evidence)

What is the purpose of your pull request?

[x] Fix or improvement to an extractor (Make sure to add/update tests)
[ ] New extractor (Piracy websites will not be accepted)
[ ] Core bug fix/improvement
[ ] New feature (It is strongly recommended to open an issue first)

Description of your pull request and other information

DESCRIPTION
When Crunchyroll is missing thumbnail image processing code, here throws NoneType error and does not process the episode to the end.
Fixes #
During processing, if any issues come from a thumbnail, the result got ignored, and thumbnail data is missing from yt-dlp resulting JSON data.

Fixes #4399

test this with videos that have thumbnail

Tested works fine.
For example, https://www.crunchyroll.com/parallel-world-pharmacy episode 3 returns https://beta.crunchyroll.com/imgsrv/display/thumbnail/1920x1080/catalog/crunchyroll/75e03acdd38124b90e27f641b9353439.jpeg

ah, it seems I misunderstood the code a bit. But while looking into this, I found similar issues for formats, subtitles etc. Pls check my changes haven't broken anything

Hmm, whatever you changed in that two commits broke subtitle downloading. I am sure subtitles was fine before that changes:
[debug] Command-line config: ['-u', 'PRIVATE', '-p', 'PRIVATE', '-j', '-vU', 'https://beta.crunchyroll.com/watch/G7PU4ZDEZ/a-reincarnated-pharmacologist-and-a-parallel-world']
[debug] Encodings: locale cp1252, fs utf-8, pref cp1252, out utf-8, error utf-8, screen utf-8
[debug] yt-dlp version 2022.07.18 [135f05e]
[debug] Python 3.10.1 (CPython 64bit) - Windows-10-10.0.22000-SP0
[debug] Checking exe version: ffmpeg -bsfs
[debug] Checking exe version: ffprobe -bsfs
[debug] exe versions: ffmpeg N-107501-g2d924b3a63-20220723 (setts), ffprobe N-107501-g2d924b3a63-20220723
[debug] Optional libraries: Cryptodome-3.11.0, brotli-1.0.9, certifi-2021.10.08, mutagen-1.45.1, sqlite3-2.6.0, websockets-10.0
[debug] Proxy map: {}
[debug] Fetching release info: https://api.github.com/repos/yt-dlp/yt-dlp/releases/latest
Latest version: 2022.07.18, Current version: 2022.07.18
yt-dlp is up to date (2022.07.18)
[crunchyroll:beta] Getting session id
[crunchyroll:beta] Logging in
[debug] [crunchyroll:beta] Extracting URL: https://beta.crunchyroll.com/watch/G7PU4ZDEZ/a-reincarnated-pharmacologist-and-a-parallel-world
[crunchyroll:beta] Retrieving main page
[crunchyroll:beta] Authenticating with cookie
[crunchyroll:beta] Retrieving signed policy
[crunchyroll:beta] a-reincarnated-pharmacologist-and-a-parallel-world: Retrieving episode metadata
[crunchyroll:beta] a-reincarnated-pharmacologist-and-a-parallel-world: Retrieving stream info
[crunchyroll:beta] a-reincarnated-pharmacologist-and-a-parallel-world: Downloading adaptive_hls HLS manifest
[debug] Formats sorted by: hasvid, ie_pref, lang, quality, res, fps, hdr:12(7), vcodec:vp9.2(10), acodec, filesize, fs_approx, tbr, vbr, abr, asr, proto, vext, aext, hasaud, source, id
ERROR: 'str' object has no attribute 'get'
Traceback (most recent call last):
  File "C:\Users\AlexI\AppData\Local\Programs\Python\Python310\lib\site-packages\yt_dlp\YoutubeDL.py", line 1431, in wrapper
    return func(self, *args, **kwargs)
  File "C:\Users\AlexI\AppData\Local\Programs\Python\Python310\lib\site-packages\yt_dlp\YoutubeDL.py", line 1521, in __extract_info
    return self.process_ie_result(ie_result, download, extra_info)
  File "C:\Users\AlexI\AppData\Local\Programs\Python\Python310\lib\site-packages\yt_dlp\YoutubeDL.py", line 1578, in process_ie_result
    ie_result = self.process_video_result(ie_result, download=download)
  File "C:\Users\AlexI\AppData\Local\Programs\Python\Python310\lib\site-packages\yt_dlp\YoutubeDL.py", line 2443, in process_video_result
    if subtitle_format.get('url'):
AttributeError: 'str' object has no attribute 'get'

should be fixed now

I tested with the link that generated subtitle error, and it was fine.
I tested with the link that initially had no thumbnail, and it was fine.


Audit our webhook integrations for ping messages that should be handled

As a follow-up to #3994, it'd be super awesome to audit our other integrations for whether they have "ping" type messages that are being silently accepted and should instead send out a similar notice.  Probably the best way to check is to read the webhook docs for the integration, but we could also check our code in most cases.
I'd sorta do this in a few stages that all feel fairly quick (and log findings in this issue).  E.g. start by checking out the 5 other Git integrations and opening issues for any that need work, and going from there.

@zulipbot claim
On it.

airbrake -> has no info about ping event in the doc
appfollow -> I didn't find webhooks doc
basecamp -> has no ping event.
beanstalk -> no info in the doc
bitbucket - > deprecated, I ignored it
bitbucket2 -> no ping event
circleci -> has no info about ping event in the doc
codeship -> has no info about ping event in the doc
crashlytics -> "ping" event implemented

delighted -> no info about ping event in the doc
deskdotcom -> N/A
freshdesk -> doc says nothing about it and free plan does not allow to set it up
github_webhook -> Done already
gitlab -> No ping event
gogs -> has test event but Test delivery button does nothing (not working)
gosquared - no ping event
greenhouse - has something like ping event but we have to request demo account to implement it (https://developers.greenhouse.io/webhooks.html#what-is-a-web-hook)

hellosign ->  No info about ping event in doc
helloworld -> N/A
heroku -> No ping event
homeassistant -> No ping event in the doc
iftt -> No ping event
jira -> No ping event in the doc (also I don't remember something like this during the setup)

librato -> No ping info in the doc.
mention -> N/A
newrelic -> N/A
pagerduty -> No ping event in the doc
papertail -> No ping event
pingdom -> No ping event

sempahore -> No ping info in the doc
sentry -> No ping event
slack -> No ping event
solano -> Test event handler added
splunk -> No info about ping event

@zulipbot claim

@timabbott
How should I proceed with the issue? There is already an audit of previously available integrations present. There were new integrations after 2017 and I think they are already returning a message.

@Udit107710 I think we should just close this issue as hopeless stale.  I think we've likely discovered those integrations that support this sort of ping feature long ago.


Bugs in URDF parser

I am currently fixing the URDF parser and there are a few points on which I'm not completely sure:

[x] https://github.com/stack-of-tasks/pinocchio/blob/devel/src/parsers/urdf/model.cpp#L392 the frame placement is different with and without inertia. Is this correct ?
[x] Zero inertias are not an issues for kinematic only algorithm, right ?
[x] In the comparison between hpp-model and Pinocchio, have the positions of geometries been check for geom in fixed joints, geom with offsets ? I suspect there is a missing shift for geometry placements in those cases.
[x] Where is the package romeo_pinocchio which is needed to load the hpp-model / pinocchio comparison ?

This is bug. It must be jointPlacement instead of nextPlacementOffset. Concerning this issue, we must think on: what is a frame of a body. Is it the frame centered around the centre of mass or the frame from which the inertia is defined?
What is the origin frame of the meshes?

It is right. It is an issue only for ABA and the LLT decomposition.

3.I do not get the question. Please rephrase.

4.There is no package, only a urdf model in models directory with meshes.

This is bug. It must be jointPlacement instead of nextPlacementOffset. Concerning this issue, we must think on: what is a frame of a body. Is it the frame centered around the centre of mass or the frame from which the inertia is defined? What is the origin frame of the meshes?

The modifications I have added to the parser puts a body for each link of the URDF. As pinocchio do not define (yet?) any convention, I think taking what the file defines is the right behaviour.

3.I do not get the question. Please rephrase.

Sorry, I have updated the question.

4.There is no package, only a urdf model in models directory with meshes.

https://github.com/stack-of-tasks/pinocchio/blob/devel/unittest/geom.cpp#L256

For the two last points, it is not my work. It was done by @fvalenza. Hope it can answer you rapidly.

1.Becareful, when you call appendBodyToJoint it also adds a frame for the body automatically.
In addition, I think this method must return the id of the created frame (because, in case of empty name, we cannot retrieve the body frame info).

In addition, I think this method must return the id of the created frame (because, in case of empty name, we cannot retrieve the body frame info).

:+1: it makes sense to me.

This Issue seems to be solved. I'll close it now.

They have been corrected in the not yet merged pull-request #302


[Fix](Oracle External Table) fix that oracle external table can not insert batch values

Proposed changes
Issue Number: close #xxx
This pr fix two bugs:

_jdbc_scanner may be nullptr in vjdbc_connector.cpp, so we use another method to count jdbc statistic. close #15914
In the batch insertion scenario, oracle database does not support syntax insert into tables values (...),(...); , what it supports is:

insert all
into table(col1,col2) values(c1v1, c2v1)
into table(col1,col2) values(c1v2, c2v2)
SELECT 1 FROM DUAL;

Problem summary
Describe your changes.
Checklist(Required)

Does it affect the original behavior:

[ ] Yes
[ ] No
[ ] I don't know

Has unit tests been added:

[ ] Yes
[ ] No
[ ] No Need

Has document been added or modified:

[ ] Yes
[ ] No
[ ] No Need

Does it need to update dependencies:

[ ] Yes
[ ] No

Are there any changes that cannot be rolled back:

[ ] Yes (If Yes, please explain WHY)
[ ] No

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

TeamCity pipeline, clickbench performance test result:
the sum of best hot time: 33.4 seconds
load time: 489 seconds
storage size:<PHONE_NUMBER>6 Bytes
https://doris-community-test-1308700295.cos.ap-hongkong.myqcloud.com/tmp/20230120084641_clickbench_pr_84608.html


[nrfconnect] Refactored configuration for child images

Problem
Currently used approach for nrfconnect regarding child images results in significant duplication of configuration files,
what hardens maintenance.
Change overview

Created Kconfig.mcuboot.defaults file that sets default configuration for all examples using mcuboot child image
Created Kconfig.multiprotocol_rpmsg file that sets default configuration for all examples using multiprotocol
rpmsg child image
Removed from rpc.overlay comment describing how to use it, as it duplicates example README.md information

Does the change mean that we're able to flatten the configuration tree and not to duplicate files across boards?

A little bit. We still need to duplicate prj.confs for mcuboot and multiprotocol_rpmsg in the child_image directories, as not all configs can be set in defaults, due to overrides in board files. At least we will get rid of plenty overlays containing the same options and having different names (like multiprotocol_rpmsg, multiprotocol_rpmsg_release, multiprotocol_rpmsg_no_dfu)


feat: implement table selection

Pull Request Test Coverage Report for Build 2083

83 of 242 (34.3%)  changed or added relevant lines in 26 files are covered.
11 unchanged lines in 2 files lost coverage.
Overall coverage decreased (-4.9%) to 71.168%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

src/components/Input/inputCheckbox/index.js
5
6
83.33%

src/components/Table/body/cell.js
2
3
66.67%

src/components/Table/body/row.js
7
8
87.5%

src/components/Table/head/header.js
1
2
50.0%

src/components/Table/helpers/columns/getColumns.js
3
4
75.0%

src/components/Table/helpers/rows/computeUniqueRowKey.js
4
5
80.0%

src/components/Table/helpers/selector/getCurrentSelectionLength.js
2
3
66.67%

src/components/Table/helpers/selector/getUpdatedRowsWhenDeselectAll.js
0
1
0.0%

src/components/Table/helpers/selector/isDisabledRow.js
3
4
75.0%

src/components/Table/body/index.js
3
5
60.0%

Files with Coverage Reduction
New Missed Lines
%

src/components/Table/body/index.js
1
80.0%

src/components/Table/index.js
10
49.61%

Totals

Change from base Build 2077:
-4.9%

Covered Lines:
1980

Relevant Lines:
2640

💛  - Coveralls

fix: #486


Teams Meeting add-in in Outlook using incorrect account

I haven't found any other document on the topic of MS Teams add-in for Outlook, so I'm posting here.
My issue is on Windows 10. According to this document, the add-in should automatically use the same account I'm using with the MS Teams desktop application. For me it does not. I have access to more than one organization with both Outlook e-mail accounts and MS Teams. When I had 1, everything was fine. When I added the second account to Outlook, everything still worked OK. When I switched MS Teams to use the second account (there seems to be no way to set up 2 accounts in MS Teams, which is a separate PITA), I thought everything is fine too, but it was not.
The MS Teams add-in seems to still be using the first account: when used to add a Teams meeting to a calendar entry, it creates the meetings in the context of the first account. It does so even if I switched the default account in Outlook to the second one.
The meetings are created in the Outlook calendar of the second account (and don't appear in the calendar of the first account), but can only be managed by my first account, and - as I have it set up to use a waiting room - I have to use my first account to accept people to the meeting, so I actually have to use the first account (e.g. by opening Teams in a browser) to accept myself (the second account) to the meeting (although my second account is the meeting organizer).
Has anyone experienced such an issue?
Any resolution?
I'm afraid what will happen, when I'll have to use the MS Teams from other accounts/organizations? Outlook in general seems to be working relatively fine in such scenarios (although I'd really like it to show me from which account is the reminder/alert or a particular open item window). MS Teams (the desktop app and web app) offers absolutely no support for such scenarios, but works, and the add-in does not.

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

ID: 37e10f52-d726-d29a-e0a8-93729a32dfae
Version Independent ID: 83555f80-a8ca-ee85-c1fc-e39891029758
Content: Use the Microsoft Teams Meeting add-in in Outlook - Microsoft Teams
Content Source: Teams/Teams-add-in-for-Outlook.md
Service: msteams
GitHub Login: @LanaChin
Microsoft Alias: v-lanac

@hilari0n Thank you for submitting feedback.
I think the best way forward is if you open a service ticket in your tenant so this can get resolved ASAP. Based on the outcome let me know if it is something that can be called out in the docs.
Please follow this link to contact support for business products:https://docs.microsoft.com/office365/admin/contact-support-for-business-products
Please keep us posted here on the resolution so we can feed whatever information you discover into the content.


Sets: should they be ^$ instead of #$?

Not really sure why I chose #$ originally.  But if we're going to end with $ maybe it's more fun to use ^$.

On the other hand there's not really a particularly good reason to force everyone to update their implementations just to be amused by this...

I'm going to close this.  Someone can reopen it if they feel opinionated... within a short timeframe.  At the moment I think this is probably unnecessary bikeshedding... the ^ pun might be fun, but also confusing, because it might imply regexps as a joke.  By contrast, # does seem to mnemonically indicate something: it sounds "hash'y", and many languages do a hacky implementation of sets on top of the hashmaps they already have.
Disagree?  Reopen.  But do it soon...


Use fetch-ponyfill instead of requiring isomorphic-fetch downstream

This ended up being drastically harder than the equivalent register-resin-device change (see https://github.com/resin-io-modules/resin-register-device/pull/27), but it's now all working. Some caveats:

There's quite a few workarounds for various fetch-mock issues, leading to some remaining strange and wonderful setup code for that in setup.coffee. Everything elsewhere comes out nicely though, and I've filed a couple of issues and linked them inline, so we can improve this later as they get solved.

Mockery works fine in Node, but getting any mocking working in Browserify without breaking Node  became a huge pain, and I've opted for the far simpler option: exposing utils.fetch, and letting you change it externally. Less elegant, and I'd welcome an improvement on that if anybody has an easy one, but I spent quite a while fighting with proxyquirify-universal and even the bits that worked leave you with a big mess.

I've given this a quick test in resin-sdk, dropping it in and taking isomorphic-fetch out seems to work perfectly.

The other outstanding issue from https://github.com/resin-io-modules/resin-register-device/pull/27 is cancelling requests. I think the best case there is that we get cancellation working in Node, but not the browser, at the cost of making the code here a bit more complicated.
I think we decided we don't need that for now, and it's a separate issue anyway, but feel free to assign me an issue for it and I'll take a look at doing that too once this piece is in.

I think we decided we don't need that for now, and it's a separate issue anyway, but feel free to assign me an issue for it and I'll take a look at doing that too once this piece is in.

Yeah let's keep it separate, you can file an issue yourself.

Timeout issue: https://github.com/resin-io-modules/resin-request/issues/83

@emirotin @Page- I'd like to release this so I can get the two downstream PRs ready to go today too. How strict are we with semver? This fetch change is backward compatible I believe, but there's a tiny outstanding change in how errors are thrown on timeout, which is technically not backward compatible: https://github.com/resin-io-modules/resin-request/blob/master/CHANGELOG.md#changed. Seems unlikely that anybody is depending on the error message imo, but who knows.
Does that warrant a major version bump?

Normally we do follow it strictly but if this speeds up the process I'm OK with going with minor bump here. I don't think anybody except us is using this and we know all the places in our code that do (and I don't remember any that specifically handles the timeouts).

I don't think it makes much difference to the speed either way, it's just that we need to make a decision, and I felt like a major bump was maybe over the top. That's probably not a good instinct though, since the downside to a bump is very minimal indeed.
I've looked into exactly how timeouts are handled downstream, and it does look like the timeout error we throw here is just directly rethrown by Resin-SDK, so this will also be a visible change there too. Given that, I think this should be a major bump for both. Presumably there are end users actually using Resin-SDK, so we should definitely play it safe there, we should be consistent here, and there's no real downside anyway. I'll release this as 7.0.0 in just a sec.


Fixes enhancing of environment by local's guest implementation

It was expecting env to be either missing, or mapping, ignoring the possibility of env being set to perfctly acceptable None.

@psss I'd like to include this patch in v1.18 milestone, if at all possible.


[Task]: Show Similar templates

Is there an existing issue for this?

[X] I have searched the existing issues

SubTasks

[x] UI
[x] Api integraton

Closed with https://github.com/appsmithorg/appsmith/pull/10964


Bot doesn't receive participants notifications from Graph API when the participants join to the meeting as guest

Describe the issue
I've been testing the bot in a meeting with guest participants and the bot didn't receive the graph notification from some of those participants. In this scenario, the Bot has Graph API permissions for the tenant A (tenant that hosts the meeting), and the invited participants are from tenant B and tenant C. We received the notifications of the tenant A and tenant B participants, but couldn't received the participants notifications from tenant C.
Expected behavior
I expected to receive the notifications of all guest participants.
Graph SDK (please complete the following information):
SDK Version <IP_ADDRESS>-alpha

@JonatanMedinilla We are soon attempting to receive similar notifications - would you mind sharing the fix?

@philomathikus Hi philo, I don't know if your scenario is gonna be the same, but something that we detected while debugging the bot's samples is that we receive all the user's notifications, including the guests but the notifications aren't the same.  For example, we were filtering the participants by following the same logic as one of the bot's samples. This sample considers a participant as user if the User identity property is not null, but we found that the guests' participants always have that property in null but contain a "guest" key inside the identity additional data. So, as mentioned before, you are gonna to receive all the participants notifications (including guests) but you should check the participants' resources data in order to know what to do with the notification.

@JonatanMedinilla Thank you for the quick and insightful reply!

@JonatanMedinilla FYI: added you on LinkedIn (Max) to stay in touch :)


Docker containers no longer build due to dart v2

Please make sure that you have checked the boxes:

[x] Pease review the Troubleshooting doc for additional details regarding your issue.
[x] Review the Quickstart guide
[x] Search for both open and closed issues regarding the problem you are experiencing
[x] For permissions issues (Access Denied and credential related errors), please refer to the requisite docs before submitting an issue:
AWS, GCP, OpenStack, GitHub

Description of issue:
docker containers fail to build as unittest is incompatible with dart sdk 2 but dart_stable debian repo now defaults to install dart v2.

We'll probably need to do what we did here: https://github.com/Netflix/security_monkey/blob/develop/docker/nginx/Dockerfile#L19-L25 and place it into the regular Dockerfile.

Or... Are you seeing this somewhere else?

No its in docker/nginx/Dockerfile that I had the problem, but specifically on the release tags.

@jsharpe can you build off the develop branch? this was fixed in https://github.com/Netflix/security_monkey/pull/1104 but hasn't been released yet


Better TS type formatting for array types

Small PR. If the TS item type of an array is a valid identifier, we don't need to the parens.
FYI, the parens are necessary for imported types. Imported types can specify an arbitrary TS type expression as their TS type.

What is an "arbitrary TS type expression"?

Anything that isn't just a plain identifier. E.g. number | string. Absent the ability to specify custom types for parameters and return types, people are currently using this workaround:
#[wasm_bindgen]
extern "C" {
    #[wasm_bindgen(typescript_type = "number | string")]
    type CustomType;
}

#[wasm_bindgen]
pub fn single(a: CustomType) {}

I added a test.

Why can that contain invalid Unicode (if I'm interpreting the code correctly)?

By the guarantees of str, obviously no. What in the code gave you that idea? (Because I just moved the stuff that we already had.)


[Color Picker] There's no way to remove the eye dropper icon from the macOS menu bar with a Raycast command

Extension
https://www.raycast.com/thomas/color-picker
Raycast Version
1.81.1
macOS Version
14.5
Description
This raycast command should toggle on/off the extension's menu bar icon, not just activate it.
extensions/color-picker/src/menu-bar.tsx
Hi there! Love your great work and I'm very impressed about how complete this extension is. I just have this observation.
Steps To Reproduce
When hitting enter to the Menu Bar Color Picker command from the Raycast command window, it only allows to add the eye dropper icon to the macOS menu bar over and over again.
Current Behaviour
No response
Expected Behaviour
To remove the eye dropper icon from the macOS menu bar when hitting enter to the same Raycast command that activated it. (with an option to add it back again with the same raycast command window)

@lord-reptilia The command Deactivate Menu Bar Item in the action can deactivate a menu bar command.

Hi!
Yeah, I know how to deactivate the Menu Bar Item,
However, the current design is quite inconvenient, and it would be greatly appreciated if this deactivation could be as simple as hitting enter to the same command that activated it.
Could a "Toggle Menu Bar Item Command" be considered to be offered?
Thank you for your review and consideration!

Could a "Toggle Menu Bar Item Command" be considered to be offered?

No. It is better not add too many commands to the extension. There are enough commands now. I don't want the plugin to become a mess.

Hello Lito,
The current design is already inconvenient from my experience.
This is not a request for an additional command:

Expected Behaviour
To remove the eye dropper icon from the macOS menu bar when hitting enter to the same Raycast command that activated it.

For your consideration.


[turborepo] Update codemod doesn't support custom registries and fails if NPM registry is unavailable

What version of Turborepo are you using?
1.8.1
What package manager are you using / does the bug impact?
pnpm
What operating system are you using?
Windows
Describe the Bug
I have an outdated version 1.8.1 of turborepo. When I run turbo commands, it shows me a message to run a codemod to update. However, when I run the codemod to update turborepo it fails. It shows "Unable to fetch the latest version of turbo" error message.
NPM registry is banned by our corporate firewall, and we use a proxy registry. In this scenario the codemod doesn't work.
The reason why it happens is because the registry url is hardcoded in the codemod: https://github.com/vercel/turbo/blob/main/packages/turbo-codemod/src/commands/migrate/steps/getLatestVersion.ts#LL5
Expected Behavior
It should use the same registry as the package manager and shouldn't rely on availability of NPM registry.
To Reproduce
To reproduce this issue, configure your package manager to use custom registry, ban npm registry on a network level and run pnpm dlx @turbo/codemod update.
Reproduction Repo
No response

Hi! Thanks for raising this. We may be able to get this information from your current package manager instead but obviously the command will need to be reworked to support that. Another alternative is providing a flag to override this value. I will update this issue with any developments. Thanks!


[Feature Request] MathJax preamble support

Hi, thank you very much for this great project!
My notes contain a lot of mathematical equations, which rely on my user-defined MathJax commands.
These commands are defined in preamble.sty in my vault root, which looks like this:
⋮
\newcommand{\set}[1]{\left\{{#1}\right\}}
⋮

In Obsidian, we can load this preamble.sty using a plugin Extended MathJax and use these commands in our notes.
However, these commands are not displayed correctly when we publish our notes with Digital Garden.
So it would be super nice if Digital Garden can support loading preambles.
By the way, the plugin that I've mentioned seems to be very simple (less than 100 lines of code). I'm not sure how to realize the same functionality in Digital Garden, though.

Would also love this functionality!  @RyotaUshio, were you able to find any work arounds for this in the meantime?  Thanks!

I still love this plugin but I use Webpage HTML Export when I need a preamble because it supports Extended MathJax.


Bug: 0.8.1 is missing courier.toml

What happened?
Between myself setting up the Messenger AP randomiser and a friend doing so, you published 0.8.1. He reported that after installing the mod, the randomiser options were not present in Third Party Mod Options.
After some investigation, I saw in The Messenger\log.txt  that it reported Located 0 mods containing a courier.toml, and the issue was resolved by installing 0.8.0 and then 0.8.1 on top.
What were the expected results?
.
Is this reproducible?
Attempt to install the mod fresh using only the 0.8.1 release.

0.8.1 was also missing the randomizer dll. I think my release script failed somewhere but it's fixed now. Also I apparently didn't get a notification for this so that's fixed now too 😓 Thanks for the reports! 😄


OpenVPN constantly resetting connection when run in TCP mode

I followed the tutorial on https://github.com/kylemanna/docker-openvpn/blob/master/docs/tcp.md to setup OpenVPN to work over TCP.
I run it on AWS. 443 port is open to security groups and I can telnet to it.

OpenVPN logs:
Fri Mar 23 10:43:11 2018 <IP_ADDRESS>:19141 TLS: Initial packet from [AF_INET]<IP_ADDRESS>:19141, sid=177f8fc3 c0de4ad3
Fri Mar 23 10:43:11 2018 <IP_ADDRESS>:19141 Connection reset, restarting [-1]
Fri Mar 23 10:43:11 2018 <IP_ADDRESS>:19141 SIGUSR1[soft,connection-reset] received, client-instance restarting
Fri Mar 23 10:43:11 2018 TCP connection established with [AF_INET]<IP_ADDRESS>:19149
Fri Mar 23 10:43:12 2018 <IP_ADDRESS>:19149 TLS: Initial packet from [AF_INET]<IP_ADDRESS>:19149, sid=550f2d8b 04527227
Fri Mar 23 10:43:12 2018 <IP_ADDRESS>:19149 Connection reset, restarting [-1]
Fri Mar 23 10:43:12 2018 <IP_ADDRESS>:19149 SIGUSR1[soft,connection-reset] received, client-instance restarting
Fri Mar 23 10:43:13 2018 TCP connection established with [AF_INET]<IP_ADDRESS>:19168
Fri Mar 23 10:43:14 2018 <IP_ADDRESS>:19168 TLS: Initial packet from [AF_INET]<IP_ADDRESS>:19168, sid=f45aef6c fc3cdb40
Fri Mar 23 10:43:14 2018 <IP_ADDRESS>:19168 Connection reset, restarting [-1]
Fri Mar 23 10:43:14 2018 <IP_ADDRESS>:19168 SIGUSR1[soft,connection-reset] received, client-instance restarting
Fri Mar 23 10:43:14 2018 TCP connection established with [AF_INET]<IP_ADDRESS>:19172
Fri Mar 23 10:43:15 2018 <IP_ADDRESS>:19172 TLS: Initial packet from [AF_INET]<IP_ADDRESS>:19172, sid=cddd1676 a833b93d
Fri Mar 23 10:43:15 2018 <IP_ADDRESS>:19172 Connection reset, restarting [-1]
Fri Mar 23 10:43:15 2018 <IP_ADDRESS>:19172 SIGUSR1[soft,connection-reset] received, client-instance restarting
Fri Mar 23 10:43:15 2018 TCP connection established with [AF_INET]<IP_ADDRESS>:19178
Fri Mar 23 10:43:16 2018 <IP_ADDRESS>:19178 TLS: Initial packet from [AF_INET]<IP_ADDRESS>:19178, sid=9e2a75a0 b1866815
Fri Mar 23 10:43:16 2018 <IP_ADDRESS>:19178 Connection reset, restarting [-1]
Fri Mar 23 10:43:16 2018 <IP_ADDRESS>:19178 SIGUSR1[soft,connection-reset] received, client-instance restarting

Tunnelblick logs:
2018-03-23 10:43:10 NOTE: the current --script-security setting may allow this configuration to call user-defined scripts
2018-03-23 10:43:10 Outgoing Control Channel Authentication: Using 160 bit message hash 'SHA1' for HMAC authentication
2018-03-23 10:43:10 Incoming Control Channel Authentication: Using 160 bit message hash 'SHA1' for HMAC authentication
2018-03-23 10:43:10 MANAGEMENT: >STATE:1521801790,RESOLVE,,,,,,
2018-03-23 10:43:10 TCP/UDP: Preserving recently used remote address: [AF_INET]<IP_ADDRESS>:443
2018-03-23 10:43:10 Socket Buffers: R=[131072->131072] S=[131072->131072]
2018-03-23 10:43:10 Attempting to establish TCP connection with [AF_INET]<IP_ADDRESS>:443 [nonblock]
2018-03-23 10:43:10 MANAGEMENT: >STATE:1521801790,TCP_CONNECT,,,,,,
2018-03-23 10:43:10 MANAGEMENT: CMD 'hold release'
2018-03-23 10:43:11 TCP connection established with [AF_INET]<IP_ADDRESS>:443
2018-03-23 10:43:11 TCP_CLIENT link local: (not bound)
2018-03-23 10:43:11 TCP_CLIENT link remote: [AF_INET]<IP_ADDRESS>:443
2018-03-23 10:43:11 MANAGEMENT: >STATE:1521801791,WAIT,,,,,,
2018-03-23 10:43:11 Connection reset, restarting [-1]
2018-03-23 10:43:11 SIGUSR1[soft,connection-reset] received, process restarting
2018-03-23 10:43:11 MANAGEMENT: >STATE:1521801791,RECONNECTING,connection-reset,,,,,
2018-03-23 10:43:11 MANAGEMENT: CMD 'hold release'
2018-03-23 10:43:11 NOTE: the current --script-security setting may allow this configuration to call user-defined scripts
2018-03-23 10:43:11 Outgoing Control Channel Authentication: Using 160 bit message hash 'SHA1' for HMAC authentication
2018-03-23 10:43:11 Incoming Control Channel Authentication: Using 160 bit message hash 'SHA1' for HMAC authentication
2018-03-23 10:43:11 MANAGEMENT: >STATE:1521801791,RESOLVE,,,,,,
2018-03-23 10:43:11 TCP/UDP: Preserving recently used remote address: [AF_INET]<IP_ADDRESS>:443
2018-03-23 10:43:11 Socket Buffers: R=[131072->131072] S=[131072->131072]
2018-03-23 10:43:11 Attempting to establish TCP connection with [AF_INET]<IP_ADDRESS>:443 [nonblock]
2018-03-23 10:43:11 MANAGEMENT: >STATE:1521801791,TCP_CONNECT,,,,,,
2018-03-23 10:43:11 MANAGEMENT: CMD 'hold release'
2018-03-23 10:43:12 TCP connection established with [AF_INET]<IP_ADDRESS>:443
2018-03-23 10:43:12 TCP_CLIENT link local: (not bound)
2018-03-23 10:43:12 TCP_CLIENT link remote: [AF_INET]<IP_ADDRESS>:443
2018-03-23 10:43:12 MANAGEMENT: >STATE:1521801792,WAIT,,,,,,
2018-03-23 10:43:12 Connection reset, restarting [-1]
2018-03-23 10:43:12 SIGUSR1[soft,connection-reset] received, process restarting
2018-03-23 10:43:12 MANAGEMENT: >STATE:1521801792,RECONNECTING,connection-reset,,,,,
2018-03-23 10:43:13 MANAGEMENT: CMD 'hold release'
2018-03-23 10:43:13 NOTE: the current --script-security setting may allow this configuration to call user-defined scripts
2018-03-23 10:43:13 Outgoing Control Channel Authentication: Using 160 bit message hash 'SHA1' for HMAC authentication
2018-03-23 10:43:13 Incoming Control Channel Authentication: Using 160 bit message hash 'SHA1' for HMAC authentication
2018-03-23 10:43:13 MANAGEMENT: >STATE:1521801793,RESOLVE,,,,,,
2018-03-23 10:43:13 TCP/UDP: Preserving recently used remote address: [AF_INET]<IP_ADDRESS>:443
2018-03-23 10:43:13 Socket Buffers: R=[131072->131072] S=[131072->131072]
2018-03-23 10:43:13 Attempting to establish TCP connection with [AF_INET]<IP_ADDRESS>:443 [nonblock]
2018-03-23 10:43:13 MANAGEMENT: >STATE:1521801793,TCP_CONNECT,,,,,,
2018-03-23 10:43:13 MANAGEMENT: CMD 'hold release'
2018-03-23 10:43:14 TCP connection established with [AF_INET]<IP_ADDRESS>:443
2018-03-23 10:43:14 TCP_CLIENT link local: (not bound)
2018-03-23 10:43:14 TCP_CLIENT link remote: [AF_INET]<IP_ADDRESS>:443
2018-03-23 10:43:14 MANAGEMENT: >STATE:1521801794,WAIT,,,,,,
2018-03-23 10:43:14 Connection reset, restarting [-1]
2018-03-23 10:43:14 SIGUSR1[soft,connection-reset] received, process restarting
2018-03-23 10:43:14 MANAGEMENT: >STATE:1521801794,RECONNECTING,connection-reset,,,,,
2018-03-23 10:43:14 MANAGEMENT: CMD 'hold release'
2018-03-23 10:43:14 NOTE: the current --script-security setting may allow this configuration to call user-defined scripts
2018-03-23 10:43:14 Outgoing Control Channel Authentication: Using 160 bit message hash 'SHA1' for HMAC authentication
2018-03-23 10:43:14 Incoming Control Channel Authentication: Using 160 bit message hash 'SHA1' for HMAC authentication
2018-03-23 10:43:14 MANAGEMENT: >STATE:1521801794,RESOLVE,,,,,,
2018-03-23 10:43:14 TCP/UDP: Preserving recently used remote address: [AF_INET]<IP_ADDRESS>:443
2018-03-23 10:43:14 Socket Buffers: R=[131072->131072] S=[131072->131072]
2018-03-23 10:43:14 Attempting to establish TCP connection with [AF_INET]<IP_ADDRESS>:443 [nonblock]
2018-03-23 10:43:14 MANAGEMENT: >STATE:1521801794,TCP_CONNECT,,,,,,
2018-03-23 10:43:14 MANAGEMENT: CMD 'hold release'
2018-03-23 10:43:15 TCP connection established with [AF_INET]<IP_ADDRESS>:443
2018-03-23 10:43:15 TCP_CLIENT link local: (not bound)
2018-03-23 10:43:15 TCP_CLIENT link remote: [AF_INET]<IP_ADDRESS>:443
2018-03-23 10:43:15 MANAGEMENT: >STATE:1521801795,WAIT,,,,,,
2018-03-23 10:43:15 Connection reset, restarting [-1]
2018-03-23 10:43:15 SIGUSR1[soft,connection-reset] received, process restarting
2018-03-23 10:43:15 MANAGEMENT: >STATE:1521801795,RECONNECTING,connection-reset,,,,,
2018-03-23 10:43:15 MANAGEMENT: CMD 'hold release'
2018-03-23 10:43:15 NOTE: the current --script-security setting may allow this configuration to call user-defined scripts
2018-03-23 10:43:15 Outgoing Control Channel Authentication: Using 160 bit message hash 'SHA1' for HMAC authentication
2018-03-23 10:43:15 Incoming Control Channel Authentication: Using 160 bit message hash 'SHA1' for HMAC authentication
2018-03-23 10:43:15 MANAGEMENT: >STATE:1521801795,RESOLVE,,,,,,
2018-03-23 10:43:15 TCP/UDP: Preserving recently used remote address: [AF_INET]<IP_ADDRESS>:443
2018-03-23 10:43:15 Socket Buffers: R=[131072->131072] S=[131072->131072]
2018-03-23 10:43:15 Attempting to establish TCP connection with [AF_INET]<IP_ADDRESS>:443 [nonblock]
2018-03-23 10:43:15 MANAGEMENT: >STATE:1521801795,TCP_CONNECT,,,,,,
2018-03-23 10:43:15 MANAGEMENT: CMD 'hold release'
2018-03-23 10:43:16 TCP connection established with [AF_INET]<IP_ADDRESS>:443
2018-03-23 10:43:16 TCP_CLIENT link local: (not bound)
2018-03-23 10:43:16 TCP_CLIENT link remote: [AF_INET]<IP_ADDRESS>:443
2018-03-23 10:43:16 MANAGEMENT: >STATE:1521801796,WAIT,,,,,,
2018-03-23 10:43:16 Connection reset, restarting [-1]
2018-03-23 10:43:16 SIGUSR1[soft,connection-reset] received, process restarting
2018-03-23 10:43:16 MANAGEMENT: >STATE:1521801796,RECONNECTING,connection-reset,,,,,
2018-03-23 10:43:16 SIGTERM[hard,init_instance] received, process exiting
2018-03-23 10:43:16 MANAGEMENT: >STATE:1521801796,EXITING,init_instance,,,,,

This happens with me using UDP as well.

This looks quite similar to #180.
Can you check the last comment from @2ge:
https://github.com/kylemanna/docker-openvpn/issues/180#issuecomment-327683431

I do not have it running now. Will check when have a moment.

Since you are using TCP, I think that is very likely that you have a Load Balancer fronting the OpenVPN service?
The provided OpenVPN server log looks as if there is an AWS LoadBalancer firing every second. With each ELB Health Check ping, telnet or netcat etc. you will get this.
Fri Mar 23 10:43:12 2018 <IP_ADDRESS>:19149 TLS: Initial packet from [AF_INET]<IP_ADDRESS>:19149, sid=550f2d8b 04527227
Fri Mar 23 10:43:12 2018 <IP_ADDRESS>:19149 Connection reset, restarting [-1]
Fri Mar 23 10:43:12 2018 <IP_ADDRESS>:19149 SIGUSR1[soft,connection-reset] received, client-instance restarting

There is not really a way around it apart from getting less of such entrances in the logs by adjusting the ELB interval.

Just to be absolutely certain, you do have a valid ssl cert/key while using port 443, right?

If you deployed OpenVPN server in AWS and are runing it behind a Network Load Balancer, make it hit a different port/service for health checking. You can make it probe port 22 (SSH) for example.

as @quater points it is due the healthcheck but not restricted to NLB, it happens on ELB too.
Even probably do not matter if you have it on AWS or not. the health check is just a 'service alive' that check the port is open and answering whatever that makes openvpn to see an incomming but not properly finishing with the protocol.
Since vpn is a service I will notice very soon when it fails, I have just increased the healthcheck period from the 10 secs aws standard to 120secs. is is waaaaay less annyoing on the logs, despite it does not fully dissapears.

Have the same problem without load balancers

I have the exact same problem (AWS NLB + OpenVPN ran at ECS).  It does not provide separate ports for monitoring and healthcheck. This problem is especially relevant when using the UDP protocol.


Request: Subitems in the Todo list

Hi there,
It would be nice to have have subitem in the list;

[  ] @ToDo //2022-05-30 Head Item --> Shown

[ ] @ToDo //2022-05-05 Second Item --> Not shown in current version
[ ] @ToDo //2022-05-07 Third Item --> Not shown in current version

This has been fixed in version v1.1.1 (deployed just now, so it should be available within the hour).
Just a note though, subitems won't maintain their dependence on the parent item. So they will be out-of-order in the summary note. If you want them in order you can prefix each item with a number.
example

[ ] @todo //2022-05-30 1 Head Item --> Shown

[ ] @todo //2022-05-05 2 Second Item --> Now shown in current version
[ ] @todo //2022-05-07 3 Third Item --> Now shown in current version


Persistence

I wonder how it could be achieved to have openwrt-tailscale-enabler configured persistent across firmware updates.
Correct me if I'm wrong, but right now, after upgrading the firmware, openwrt-tailscale-enabler would need to get re-installed manually, right ?
Edit: ~As well for reboots, since /tmp is a RAM fs ?~ From the README.md, openwrt-tailscale-enabler survives a reboot.

Under System > Backup/Flash > Configuration, you can manually add files to be backed up. I am not sure about how it handles upgrades, although I would assume /etc/ is saved. If so, that should be plenty.


Provide quality limitation reason in output video stats

Provide qualityLimitationReason in OutputVideo.
Linked to this issue in Dolby Millicast RTS app: https://github.com/dolbyio-samples/rts-app-react-publisher-viewer/issues/325

Available in version 0.2.0


GUI Select USB port

Hi, Is it possible to integrate a dropdown list in the GUI, same style as the "Permit join" checkbox that goes into the "configuration.yaml" to modify the USB port ? And would it be useful to some of you ?
In my case the CC2531 is sometimes allocated to /dev/ttyACM0 or ACM1.

That wouldn't be possible as it is zigbee2mqtt configuration, not plugin one.
I wouldn't recommend to use syntax like /dev/ttyACM0, you can use /dev/serial/by-id/.... instead


Add annotations in Blokus.py and an introduction in README

Add annotations in Blokus.py and an introduction in README

Try for lots of times to make readme.md perfect


"lncli stop" not working

Background
Unable to stop LND daemon. "lncli stop" is not working. "Ctrl+C" is not working too.
Your environment

version of lnd: 0.8.2-beta
which operating system (uname -a on *Nix): Ubuntu Server 18.04
version of btcd, bitcoind, or other backend: bitcoind <IP_ADDRESS>

Steps to reproduce
Run the daemon for a while and try to stop it
Expected behaviour
The daemon should stop.
Actual behaviour
The daemon is not reacting to "lncli stop" command. Nothing happens.

@peername  Does it work if you do lncli getinfo?

Yes, all other commands are working and the daemon is not stopping.

@peername

"Ctrl+C" is not working too.

I don't think it has to do with lnd, try kill -9 <pid> or killall -9 <process name>

hi @peername
Thanks for reporting this. Can you reproduce the issue every time? If yes, would you mind please uploading a debug log (debuglevel=debug in lnd.conf) if possible?

Also if you can reliably reproduce this issue you might send a SIGTRAP signal to the LND process, which will make it dump call stacks for all goroutines (which will help figuring out where the deadlock is).
You can do this by first getting the PID for your LND:
ps aux | grep lnd
Then sending SIGTRAP (substitute  with the process' PID) by:
kill -5 <pid>

May be this is the reason:

2020-01-02 22:30:26.225 [INF] WTCL: Watchtower client unclean shutdown complete, stats: tasks(received=18 accepted=18 ineligible=0) sessions(acquired=0 exhausted=72)

Can you reproduce the issue reliably? If yes, would you mind adding a stack dump as described above?

I disabled the wtclient. I will test periodically whether it will stop successfully when wtclient is stopped. In my opinion he is the reason.

After I disabled the wtclient, the problem dissapeared. Now the daemon stops every time without any delay. I prefer to disable my watchtower instead of risking damage to my database.

@peername to get to the bottom of this, we'll need a goroutine profile. You'll want to stop your node and see if it hangs. Once you confirm that it does, the profile can be obtained by following https://github.com/lightningnetwork/lnd/blob/master/docs/debugging_lnd.md#capturing-pprof-data-with-lnd.

I will not risk to corrupt my database. The problem disappeared with disabling the wtclient. I would not reactivate it.

2020-01-02 22:30:26.225 [INF] WTCL: Watchtower client unclean shutdown complete, stats: tasks(received=18 accepted=18 ineligible=0) sessions(acquired=0 exhausted=72)

@peername If the client detects it hasn't backed everything up, it will wait up to 15s before giving up and allowing shutdown to complete. In that scenario you get the log above. Did you notice the daemon hanging much longer, e.g. minutes?
If you're only encountering the 15s delay, there shouldn't be any risk to your database. It's also more than likely a configuration error or a false positive in thinking the client isn't complete.

Closing due to inactivity, unable to reproduce.


[25/01/2022, 00:13:37] [CameraUI] MQTT: Can not assign the MQTT topic (XiaoMod2/Xiaofang2/motion/send_mail) to a camera!
[25/01/2022, 00:13:37] [CameraUI] MQTT: New message: Topic: XiaoMod2/Xiaofang2/motion/send_telegram - Data: ON - Type: string
[25/01/2022, 00:13:37] [CameraUI] MQTT: Can not assign the MQTT topic (XiaoMod2/Xiaofang2/motion/send_telegram) to a camera!
[25/01/2022, 00:13:37] [CameraUI] MQTT: New message: Topic: XiaoMod2/Xiaofang2/motion/tracking - Data: OFF - Type: string
[25/01/2022, 00:13:37] [CameraUI] MQTT: Can not assign the MQTT topic (XiaoMod2/Xiaofang2/motion/tracking) to a camera!
[25/01/2022, 00:13:37] [CameraUI] MQTT: New message: Topic: XiaoMod2/Xiaofang2/recording - Data: OFF - Type: string
[25/01/2022, 00:13:37] [CameraUI] MQTT: Can not assign the MQTT topic (XiaoMod2/Xiaofang2/recording) to a camera!
[25/01/2022, 00:13:37] [CameraUI] MQTT: New message: Topic: XiaoMod2/Xiaofang2/timelapse - Data: OFF - Type: string
[25/01/2022, 00:13:37] [CameraUI] MQTT: Can not assign the MQTT topic (XiaoMod2/Xiaofang2/timelapse) to a camera!
[25/01/2022, 00:13:37] [CameraUI] MQTT: New message: Topic: XiaoMod2/Xiaofang2/motors/vertical - Data: 0 - Type: string
[25/01/2022, 00:13:37] [CameraUI] MQTT: Can not assign the MQTT topic (XiaoMod2/Xiaofang2/motors/vertical) to a camera!
[25/01/2022, 00:13:37] [CameraUI] MQTT: New message: Topic: XiaoMod2/Xiaofang2/motors/horizontal - Data: 0 - Type: string
[25/01/2022, 00:13:37] [CameraUI] MQTT: Can not assign the MQTT topic (XiaoMod2/Xiaofang2/motors/horizontal) to a camera!
[25/01/2022, 00:13:37] [CameraUI] MQTT: New message: Topic: XiaoMod2/Xiaofang2 - Data: {"uptime":" 00:13:06 up  2:25,  0 users,  load average: 2.62, 2.78, 2.61",  "ssid":"Terminal", "bitrate":"72.2 Mb/s", "signal_level":"88%", "link_quality":"87%", "noise_level":"0%" } - Type: string
[25/01/2022, 00:13:37] [CameraUI] MQTT: {"camera":"Xiaofang2","topic":"XiaoMod2/Xiaofang2","data":"{"uptime":" 00:13:06 up  2:25,  0 users,  load average: 2.62, 2.78, 2.61",  "ssid":"Terminal", "bitrate":"72.2 Mb/s", "signal_level":"88%", "link_quality":"87%", "noise_level":"0%" }","json":false,"message":"ON","try":0}
[25/01/2022, 00:13:37] [CameraUI] MQTT: {"camera":"Xiaofang2","topic":"XiaoMod2/Xiaofang2","data":"{"uptime":" 00:13:06 up  2:25,  0 users,  load average: 2.62, 2.78, 2.61",  "ssid":"Terminal", "bitrate":"72.2 Mb/s", "signal_level":"88%", "link_quality":"87%", "noise_level":"0%" }","json":false,"message":"OFF","try":1}
[25/01/2022, 00:13:37] [CameraUI] The incoming MQTT message ({"uptime":" 00:13:06 up  2:25,  0 users,  load average: 2.62, 2.78, 2.61",  "ssid":"Terminal", "bitrate":"72.2 Mb/s", "signal_level":"88%", "link_quality":"87%", "noise_level":"0%" }) for the topic (XiaoMod2/Xiaofang2) was not the same as set in config.json (ON). Skip...
[25/01/2022, 00:13:37] [CameraUI] MQTT: New message: Topic: XiaoMod2/Xiaofang2/night_mode - Data: ON - Type: string
[25/01/2022, 00:13:37] [CameraUI] MQTT: Can not assign the MQTT topic (XiaoMod2/Xiaofang2/night_mode) to a camera!
[25/01/2022, 00:13:37] [CameraUI] IMOU: {"probe":true,"timedout":false,"audio":["aac (LC)","16000 Hz","mono","fltp"],"video":["hevc (Main)","yuvj420p(pc","bt470bg/bt470bg/smpte170m)","1920x1080","90k tbr","90k tbn","90k tbc"]}
[25/01/2022, 00:13:37] [CameraUI] IMOU: Incoming ping request for: rtsp://admin:L2657671@<IP_ADDRESS>:554/cam/realmonitor?channel=1&subtype=0&unicast=true&proto=Onvif - Timeout: 1s
[25/01/2022, 00:13:37] [CameraUI] IMOU: Pinging <IP_ADDRESS>:554
[25/01/2022, 00:13:37] [CameraUI] MQTT: New message: Topic: XiaoMod2/Xiaofang2/night_mode/auto - Data: ON - Type: string
[25/01/2022, 00:13:37] [CameraUI] MQTT: Can not assign the MQTT topic (XiaoMod2/Xiaofang2/night_mode/auto) to a camera!
[25/01/2022, 00:13:37] [CameraUI] MQTT: New message: Topic: XiaoMod2/Xiaofang2/motion/detection - Data: ON - Type: string
[25/01/2022, 00:13:37] [CameraUI] MQTT: Can not assign the MQTT topic (XiaoMod2/Xiaofang2/motion/detection) to a camera!
[25/01/2022, 00:13:38] [CameraUI] MQTT: New message: Topic: XiaoMod2/Xiaofang2/motion/led - Data: ON - Type: string
[25/01/2022, 00:13:38] [CameraUI] MQTT: Can not assign the MQTT topic (XiaoMod2/Xiaofang2/motion/led) to a camera!
[25/01/2022, 00:13:38] [CameraUI] MQTT: New message: Topic: XiaoMod2/Xiaofang2/motion/snapshot - Data: OFF - Type: string
[25/01/2022, 00:13:38] [CameraUI] MQTT: Can not assign the MQTT topic (XiaoMod2/Xiaofang2/motion/snapshot) to a camera!
[25/01/2022, 00:13:38] [CameraUI] MQTT: New message: Topic: XiaoMod2/Xiaofang2/motion/video - Data: OFF - Type: string
[25/01/2022, 00:13:38] [CameraUI] MQTT: Can not assign the MQTT topic (XiaoMod2/Xiaofang2/motion/video) to a camera!
[25/01/2022, 00:13:38] [CameraUI] MQTT: New message: Topic: XiaoMod2/Xiaofang2/motion/mqtt_publish - Data: ON - Type: string
[25/01/2022, 00:13:38] [CameraUI] MQTT: Can not assign the MQTT topic (XiaoMod2/Xiaofang2/motion/mqtt_publish) to a camera!
[25/01/2022, 00:13:38] [CameraUI] MQTT: New message: Topic: XiaoMod2/Xiaofang2/motion/mqtt_snapshot - Data: ON - Type: string
[25/01/2022, 00:13:38] [CameraUI] MQTT: Can not assign the MQTT topic (XiaoMod2/Xiaofang2/motion/mqtt_snapshot) to a camera!
[25/01/2022, 00:13:38] [CameraUI] Dafang: Pinging <IP_ADDRESS>:8554 - successful
[25/01/2022, 00:13:38] [CameraUI] Dafang: Start prebuffering...
[25/01/2022, 00:13:38] [CameraUI] Dafang: Prebuffering command: /usr/local/lib/node_modules/homebridge-camera-ui/node_modules/ffmpeg-for-homebridge/ffmpeg -hide_banner -loglevel error -fflags +genpts -fflags +discardcorrupt -i rtsp://<IP_ADDRESS>:8554/unicast -vcodec copy -bsf:a aac_adtstoasc -acodec libfdk_aac -profile:a aac_low -flags +global_header -ar 8k -b:a 100k -ac 1 -f tee -map 0:v? -map 0:a? [movflags=frag_keyframe+empty_moov+default_base_moof:f=mp4]tcp://<IP_ADDRESS>:30949|[f=mpegts]tcp://<IP_ADDRESS>:21113
[25/01/2022, 00:13:38] [CameraUI] Xiaofang2: Pinging <IP_ADDRESS>:8554 - successful
[25/01/2022, 00:13:38] [CameraUI] Xiaofang2: Start prebuffering...
[25/01/2022, 00:13:38] [CameraUI] Xiaofang2: Prebuffering command: /usr/local/lib/node_modules/homebridge-camera-ui/node_modules/ffmpeg-for-homebridge/ffmpeg -hide_banner -loglevel error -fflags +genpts -i rtsp://<IP_ADDRESS>:8554/unicast -vcodec copy -bsf:a aac_adtstoasc -acodec libfdk_aac -profile:a aac_low -flags +global_header -ar 8k -b:a 100k -ac 1 -f tee -map 0:v? -map 0:a? [movflags=frag_keyframe+empty_moov+default_base_moof:f=mp4]tcp://<IP_ADDRESS>:32224|[f=mpegts]tcp://<IP_ADDRESS>:20254
[25/01/2022, 00:13:38] [CameraUI] MQTT: New message: Topic: XiaoMod2/Xiaofang2/motion/send_mail - Data: OFF - Type: string
[25/01/2022, 00:13:38] [CameraUI] MQTT: Can not assign the MQTT topic (XiaoMod2/Xiaofang2/motion/send_mail) to a camera!
[25/01/2022, 00:13:38] [CameraUI] MQTT: New message: Topic: XiaoMod2/Xiaofang2/motion/send_telegram - Data: ON - Type: string
[25/01/2022, 00:13:38] [CameraUI] MQTT: Can not assign the MQTT topic (XiaoMod2/Xiaofang2/motion/send_telegram) to a camera!
[25/01/2022, 00:13:38] [CameraUI] MQTT: New message: Topic: XiaoMod2/Xiaofang2/motion/tracking - Data: OFF - Type: string
[25/01/2022, 00:13:38] [CameraUI] MQTT: Can not assign the MQTT topic (XiaoMod2/Xiaofang2/motion/tracking) to a camera!
[25/01/2022, 00:13:38] [CameraUI] MQTT: New message: Topic: XiaoMod2/Xiaofang2/recording - Data: OFF - Type: string
[25/01/2022, 00:13:38] [CameraUI] MQTT: Can not assign the MQTT topic (XiaoMod2/Xiaofang2/recording) to a camera!
[25/01/2022, 00:13:39] [CameraUI] MQTT: New message: Topic: XiaoMod2/Xiaofang2/timelapse - Data: OFF - Type: string
[25/01/2022, 00:13:39] [CameraUI] MQTT: Can not assign the MQTT topic (XiaoMod2/Xiaofang2/timelapse) to a camera!
[25/01/2022, 00:13:39] [CameraUI] MQTT: New message: Topic: XiaoMod2/Xiaofang2/motors/vertical - Data: 0 - Type: string
[25/01/2022, 00:13:39] [CameraUI] MQTT: Can not assign the MQTT topic (XiaoMod2/Xiaofang2/motors/vertical) to a camera!
[25/01/2022, 00:13:39] [CameraUI] MQTT: New message: Topic: XiaoMod2/Xiaofang2/motors/horizontal - Data: 0 - Type: string
[25/01/2022, 00:13:39] [CameraUI] MQTT: Can not assign the MQTT topic (XiaoMod2/Xiaofang2/motors/horizontal) to a camera!
[25/01/2022, 00:13:39] [CameraUI] IMOU: Pinging <IP_ADDRESS>:554 - successful
[25/01/2022, 00:13:39] [CameraUI] IMOU: Start videoanalysis...
[25/01/2022, 00:13:39] [CameraUI] IMOU: Videoanalysis command: /usr/local/lib/node_modules/homebridge-camera-ui/node_modules/ffmpeg-for-homebridge/ffmpeg -hide_banner -loglevel error -rtsp_transport tcp -i rtsp://admin:L2657671@<IP_ADDRESS>:554/cam/realmonitor?channel=1&subtype=0&unicast=true&proto=Onvif -an -vcodec pam -pix_fmt rgb24 -f image2pipe -vf fps=2,scale=640:360 pipe:1
[25/01/2022, 00:13:39] [CameraUI] IMOU: Videoanalysis: Difference: 50 - Sensitivity: 40 - Zones: [{"name":"region0","difference":50,"percent":60,"polygon":[{"x":0,"y":360},{"x":0,"y":0},{"x":640,"y":0},{"x":640,"y":360}]}]
[25/01/2022, 00:13:39] [CameraUI] IMOU: Videoanalysis scheduled for restart at 4AM: 226 minutes
[25/01/2022, 00:13:39] [CameraUI] MQTT: New message: Topic: XiaoMod2/Xiaofang2 - Data: {"uptime":" 00:13:39 up  2:25,  0 users,  load average: 2.48, 2.73, 2.60",  "ssid":"Terminal", "bitrate":"72.2 Mb/s", "signal_level":"90%", "link_quality":"84%", "noise_level":"0%" } - Type: string
[25/01/2022, 00:13:39] [CameraUI] MQTT: {"camera":"Xiaofang2","topic":"XiaoMod2/Xiaofang2","data":"{"uptime":" 00:13:39 up  2:25,  0 users,  load average: 2.48, 2.73, 2.60",  "ssid":"Terminal", "bitrate":"72.2 Mb/s", "signal_level":"90%", "link_quality":"84%", "noise_level":"0%" }","json":false,"message":"ON","try":0}
[25/01/2022, 00:13:39] [CameraUI] MQTT: {"camera":"Xiaofang2","topic":"XiaoMod2/Xiaofang2","data":"{"uptime":" 00:13:39 up  2:25,  0 users,  load average: 2.48, 2.73, 2.60",  "ssid":"Terminal", "bitrate":"72.2 Mb/s", "signal_level":"90%", "link_quality":"84%", "noise_level":"0%" }","json":false,"message":"OFF","try":1}
[25/01/2022, 00:13:39] [CameraUI] The incoming MQTT message ({"uptime":" 00:13:39 up  2:25,  0 users,  load average: 2.48, 2.73, 2.60",  "ssid":"Terminal", "bitrate":"72.2 Mb/s", "signal_level":"90%", "link_quality":"84%", "noise_level":"0%" }) for the topic (XiaoMod2/Xiaofang2) was not the same as set in config.json (ON). Skip...
[25/01/2022, 00:13:40] [CameraUI] Dafang: Prebuffering scheduled for restart at 2AM: 106 minutes
[25/01/2022, 00:13:40] [CameraUI] Dafang: Incoming ping request for: rtsp://<IP_ADDRESS>:8554/unicast - Timeout: 1s
[25/01/2022, 00:13:40] [CameraUI] Dafang: Pinging <IP_ADDRESS>:8554
[25/01/2022, 00:13:40] [CameraUI] Dafang: Pinging <IP_ADDRESS>:8554 - successful
[25/01/2022, 00:13:40] [CameraUI] Dafang: Start videoanalysis...
[25/01/2022, 00:13:40] [CameraUI] Dafang: Videoanalysis command: /usr/local/lib/node_modules/homebridge-camera-ui/node_modules/ffmpeg-for-homebridge/ffmpeg -hide_banner -loglevel error -analyzeduration 0 -probesize 500000 -f mpegts -i tcp://<IP_ADDRESS>:35219 -an -vcodec pam -pix_fmt rgb24 -f image2pipe -vf fps=2,scale=640:360 pipe:1
[25/01/2022, 00:13:41] [CameraUI] Dafang: Videoanalysis: Difference: 14 - Sensitivity: 4 - Zones: [{"name":"region0","difference":14,"percent":96,"polygon":[{"x":0,"y":360},{"x":0,"y":0},{"x":640,"y":0},{"x":640,"y":360}]}]
[25/01/2022, 00:13:41] [CameraUI] Dafang: Videoanalysis scheduled for restart at 4AM: 226 minutes
[25/01/2022, 00:13:41] [Google Smart Home] Sending Sync Request
[25/01/2022, 00:13:42] [Google Smart Home] Received SYNC intent
[25/01/2022, 00:13:42] [CameraUI] Xiaofang2: Prebuffering scheduled for restart at 2AM: 106 minutes
[25/01/2022, 00:13:42] [CameraUI] Xiaofang2: Incoming ping request for: rtsp://<IP_ADDRESS>:8554/unicast - Timeout: 1s
[25/01/2022, 00:13:42] [CameraUI] Xiaofang2: Pinging <IP_ADDRESS>:8554
[25/01/2022, 00:13:46] [CameraUI] Xiaofang2: Pinging <IP_ADDRESS>:8554 - successful
[25/01/2022, 00:13:46] [CameraUI] Xiaofang2: Start videoanalysis...
[25/01/2022, 00:13:46] [CameraUI] Xiaofang2: Videoanalysis command: /usr/local/lib/node_modules/homebridge-camera-ui/node_modules/ffmpeg-for-homebridge/ffmpeg -hide_banner -loglevel error -analyzeduration 0 -probesize 500000 -f mpegts -i tcp://<IP_ADDRESS>:22085 -an -vcodec pam -pix_fmt rgb24 -f image2pipe -vf fps=2,scale=640:360 pipe:1
[25/01/2022, 00:13:46] [CameraUI] Xiaofang2: Videoanalysis: Difference: 15 - Sensitivity: 7 - Zones: [{"name":"region0","difference":15,"percent":93,"polygon":[{"x":0,"y":360},{"x":0,"y":0},{"x":640,"y":0},{"x":640,"y":360}]}]
[25/01/2022, 00:13:46] [CameraUI] Xiaofang2: Videoanalysis scheduled for restart at 4AM: 226 minutes
[25/01/2022, 00:13:46] [CameraUI] Starting interface...
[25/01/2022, 00:13:46] [CameraUI] camera.ui v5.0.14 is listening on port 8081 (http)
[25/01/2022, 00:13:46] [CameraUI] Dafang: Videoanalysis finished launching
[25/01/2022, 00:13:46] [CameraUI] IMOU: Videoanalysis finished launching
[25/01/2022, 00:13:46] [CameraUI] Xiaofang2: Videoanalysis finished launching
[25/01/2022, 00:14:09] [CameraUI] MQTT: New message: Topic: XiaoMod2/Xiaofang2/leds/blue - Data: OFF - Type: string
[25/01/2022, 00:14:09] [CameraUI] MQTT: Can not assign the MQTT topic (XiaoMod2/Xiaofang2/leds/blue) to a camera!
[25/01/2022, 00:14:09] [CameraUI] MQTT: New message: Topic: XiaoMod2/Xiaofang2/leds/yellow - Data: OFF - Type: string
[25/01/2022, 00:14:09] [CameraUI] MQTT: Can not assign the MQTT topic (XiaoMod2/Xiaofang2/leds/yellow) to a camera!
[25/01/2022, 00:14:10] [CameraUI] MQTT: New message: Topic: XiaoMod2/Xiaofang2/leds/ir - Data: ON - Type: string
[25/01/2022, 00:14:10] [CameraUI] MQTT: Can not assign the MQTT topic (XiaoMod2/Xiaofang2/leds/ir) to a camera!
[25/01/2022, 00:14:10] [CameraUI] MQTT: New message: Topic: XiaoMod2/Xiaofang2/ir_cut - Data: OFF - Type: string
[25/01/2022, 00:14:10] [CameraUI] MQTT: Can not assign the MQTT topic (XiaoMod2/Xiaofang2/ir_cut) to a camera!
[25/01/2022, 00:14:10] [CameraUI] MQTT: New message: Topic: XiaoMod2/Xiaofang2/rtsp_server - Data: ON - Type: string
[25/01/2022, 00:14:10] [CameraUI] MQTT: Can not assign the MQTT topic (XiaoMod2/Xiaofang2/rtsp_server) to a camera!
[25/01/2022, 00:14:10] [CameraUI] MQTT: New message: Topic: XiaoMod2/Xiaofang2/night_mode - Data: ON - Type: string
[25/01/2022, 00:14:10] [CameraUI] MQTT: Can not assign the MQTT topic (XiaoMod2/Xiaofang2/night_mode) to a camera!
[25/01/2022, 00:14:11] [CameraUI] MQTT: New message: Topic: XiaoMod2/Xiaofang2/night_mode/auto - Data: ON - Type: string
[25/01/2022, 00:14:11] [CameraUI] MQTT: Can not assign the MQTT topic (XiaoMod2/Xiaofang2/night_mode/auto) to a camera!
[25/01/2022, 00:14:11] [CameraUI] MQTT: New message: Topic: XiaoMod2/Xiaofang2/motion/detection - Data: ON - Type: string
[25/01/2022, 00:14:11] [CameraUI] MQTT: Can not assign the MQTT topic (XiaoMod2/Xiaofang2/motion/detection) to a camera!
[25/01/2022, 00:14:11] [CameraUI] MQTT: New message: Topic: XiaoMod2/Xiaofang2/motion/led - Data: ON - Type: string
[25/01/2022, 00:14:11] [CameraUI] MQTT: Can not assign the MQTT topic (XiaoMod2/Xiaofang2/motion/led) to a camera!
[25/01/2022, 00:14:11] [CameraUI] MQTT: New message: Topic: XiaoMod2/Xiaofang2/motion/snapshot - Data: OFF - Type: string
[25/01/2022, 00:14:11] [CameraUI] MQTT: Can not assign the MQTT topic (XiaoMod2/Xiaofang2/motion/snapshot) to a camera!
[25/01/2022, 00:14:11] [CameraUI] MQTT: New message: Topic: XiaoMod2/Xiaofang2/motion/video - Data: OFF - Type: string
[25/01/2022, 00:14:11] [CameraUI] MQTT: Can not assign the MQTT topic (XiaoMod2/Xiaofang2/motion/video) to a camera!
[25/01/2022, 00:14:11] [CameraUI] MQTT: New message: Topic: XiaoMod2/Xiaofang2/motion/mqtt_publish - Data: ON - Type: string
[25/01/2022, 00:14:11] [CameraUI] MQTT: Can not assign the MQTT topic (XiaoMod2/Xiaofang2/motion/mqtt_publish) to a camera!
[25/01/2022, 00:14:11] [CameraUI] MQTT: New message: Topic: XiaoMod2/Xiaofang2/motion/mqtt_snapshot - Data: ON - Type: string
[25/01/2022, 00:14:11] [CameraUI] MQTT: Can not assign the MQTT topic (XiaoMod2/Xiaofang2/motion/mqtt_snapshot) to a camera!

 Is this a good sign?? It does show up on my Apple TV.

But only one camera so far. The IMOU camera doesn't even have MQTT feature, would it work with just HTTP-based motion?

 Is this a good sign?? It does show up on my Apple TV.

But only one camera so far. The IMOU camera doesn't even have MQTT feature, would it work with just HTTP-based motion?

Sure, if the http server is enabled, you can automatically trigger motion for this camera
See https://github.com/seydx/homebridge-camera-ui/wiki/HTTP-Config

Unfortunately, it stops working again. I've tried restarting MQTT, rebooted hub, rebooted the camera, restarted Homebridge multiple times. It seems like when it detects something, it starts to produce a really long cryptic messages in the log:
EH
IL
MP
QT
UX
YZ[^
_stszqco64`
k�/�;_D�O}]Kf�rx~����^���5�eħ!-8VJoT�[�l;vc��^�����������m��J��C
�;�#�d�o�u�{������7�-����ɨ����y�����)�2�>-F7W9]�h$'6/>�E�M
YzbOj`r����.���x���0����C�����������&�/'�trak\tkhd����
��@�{mdia mdhd����X :hdlrmhlrvideapplApple Video Media Handlerminfvmhd@���9hdlrdhlralisapplApple Alias Data Handler$dinfdref
alis�stbl�stsd�avc1appl�HHH.264��.avcCM@��gM@��n��h�<�sttst(<stss
%1=IUamtstsc�stszt
[��4rs��n�c��?M�      ��8���(���Z�I�����`]8��$�-���
�P
[25/01/2022, 10:19:00] [CameraUI] MQTT: Can not assign the MQTT topic (DafangMod1/Dafang1/motion/video) to a camera!
[25/01/2022, 10:19:01] [CameraUI] Dafang: Prebuffering scheduled for restart at 2AM: 941 minutes
[25/01/2022, 10:19:06] [CameraUI] Dafang: Incoming ping request for: rtsp://<IP_ADDRESS>:8554/unicast - Timeout: 1s
[25/01/2022, 10:19:06] [CameraUI] Dafang: Pinging <IP_ADDRESS>:8554
[25/01/2022, 10:19:06] [CameraUI] Dafang: FFmpeg prebuffer process exited (expected)
[25/01/2022, 10:19:06] [CameraUI] Dafang: Prebufferring process closed
[25/01/2022, 10:19:06] [CameraUI] Dafang: Restart prebuffer session..
[25/01/2022, 10:19:06] [CameraUI] Dafang: FFMPEG socket closed during read for 8 bytes!
[25/01/2022, 10:19:06] [CameraUI] Dafang: Pinging <IP_ADDRESS>:8554 - successful
[25/01/2022, 10:19:06] [CameraUI] Dafang: Start prebuffering...
[25/01/2022, 10:19:06] [CameraUI] Dafang: Prebuffering command: /usr/local/lib/node_modules/homebridge-camera-ui/node_modules/ffmpeg-for-homebridge/ffmpeg -hide_banner -loglevel error -fflags +genpts -fflags +discardcorrupt -i rtsp://<IP_ADDRESS>:8554/unicast -vcodec copy -bsf:a aac_adtstoasc -acodec libfdk_aac -profile:a aac_low -flags +global_header -ar 8k -b:a 100k -ac 1 -f tee -map 0:v? -map 0:a? [movflags=frag_keyframe+empty_moov+default_base_moof:f=mp4]tcp://<IP_ADDRESS>:28849|[f=mpegts]tcp://<IP_ADDRESS>:29635
[25/01/2022, 10:19:10] [CameraUI] MQTT: New message: Topic: DafangMod1/Dafang1/motion - Data: OFF - Type: string
[25/01/2022, 10:19:10] [CameraUI] MQTT: Can not assign the MQTT topic (DafangMod1/Dafang1/motion) to a camera!
[25/01/2022, 10:19:11] [CameraUI] Dafang: Prebuffering scheduled for restart at 2AM: 941 minutes
[25/01/2022, 10:19:16] [CameraUI] Dafang: Incoming ping request for: rtsp://<IP_ADDRESS>:8554/unicast - Timeout: 1s
[25/01/2022, 10:19:16] [CameraUI] Dafang: Pinging <IP_ADDRESS>:8554
[25/01/2022, 10:19:16] [CameraUI] Dafang: FFmpeg prebuffer process exited (expected)
[25/01/2022, 10:19:16] [CameraUI] Dafang: Prebufferring process closed
[25/01/2022, 10:19:16] [CameraUI] Dafang: Restart prebuffer session..
[25/01/2022, 10:19:16] [CameraUI] Dafang: FFMPEG socket closed during read for 8 bytes!
[25/01/2022, 10:19:16] [CameraUI] Dafang: Pinging <IP_ADDRESS>:8554 - successful
[25/01/2022, 10:19:16] [CameraUI] Dafang: Start prebuffering...
[25/01/2022, 10:19:16] [CameraUI] Dafang: Prebuffering command: /usr/local/lib/node_modules/homebridge-camera-ui/node_modules/ffmpeg-for-homebridge/ffmpeg -hide_banner -loglevel error -fflags +genpts -fflags +discardcorrupt -i rtsp://<IP_ADDRESS>:8554/unicast -vcodec copy -bsf:a aac_adtstoasc -acodec libfdk_aac -profile:a aac_low -flags +global_header -ar 8k -b:a 100k -ac 1 -f tee -map 0:v? -map 0:a? [movflags=frag_keyframe+empty_moov+default_base_moof:f=mp4]tcp://<IP_ADDRESS>:20662|[f=mpegts]tcp://<IP_ADDRESS>:38809
[25/01/2022, 10:19:21] [CameraUI] Dafang: Prebuffering scheduled for restart at 2AM: 941 minutes

@ahmadnazirafiq
The camera sends a video buffer  to topic „ DafangMod1/Dafang1/motion/video“ which can not be assigned to a camera
what are the defined topics in your config?

@ahmadnazirafiq
The camera sends a video buffer to topic „ DafangMod1/Dafang1/motion/video“ which can not be assigned to a camera
what are the defined topics in your config?

The topics are DafangMod1/Dafang1 which I pasted inside Motion Topic Prefix of the camera.

@ahmadnazirafiq
The camera sends a video buffer to topic „ DafangMod1/Dafang1/motion/video“ which can not be assigned to a camera
what are the defined topics in your config?

The topics are DafangMod1/Dafang1 which I pasted inside Motion Topic Prefix of the camera.

Are these fixed topics defined by the camera? Or can you change it in the camera settings?
can you post a screenshot of the camera mqtt settings pls

Yes, that’s the only way I could define the topic for this Dafang camera. Below is the web UI for the camera:

Odd enough, after removing other cameras from the Camera-UI (leaving just Dafang), it suddenly reports the motion again. Not sure if its a bug.

@ahmadnazirafiq
can you change the topics in your config.json to DafangMod1/Dafang1/motion and try again pls

@ahmadnazirafiq
can you change the topics in your config.json to DafangMod1/Dafang1/motion and try again pls

This helps. It’s consistently monitoring motion and notifies me now. I’ll add additional camera to camera-ui with similar specs and see how this goes. Thanks for your help! 👍


Add CI check for consistency on the Consensus changelog management

Description
This CI check ensures that the management of the consensus versions and changelogs is consistent with the release process.
Checklist

Branch

[x] Commit sequence broadly makes sense
[x] Commits have useful messages
[x] The documentation has been properly updated
[x] New tests are added if needed and existing tests are updated
[x] Any changes affecting Consensus packages must have an entry in the appropriate changelog.d directory created using scriv. If in doubt, see the Consensus release process.
[x] If this branch changes Network and has any consequences for downstream repositories or end users, said changes must be documented in interface-CHANGELOG.md
[x] If serialization changes, user-facing consequences (e.g. replay from genesis) are confirmed to be intentional.

Pull Request

[x] Self-reviewed the diff
[x] Useful pull request description at least containing the following information:

What does this PR change?
Why these changes were needed?
How does this affect downstream repositories and/or end-users?
Which ticket does this PR close (if any)? If it does, is it linked?

[x] Reviewer requested

I added a description at the top and related it to each one of the steps @dnadales

Cool :smile: -- maybe we should record somewhere that this CI script should be updated when new packages are included, or when existing packages change names?

bors r+

bors r+


Add cart information to commerce

What are the schemas that are affected by the issue
https://github.com/adobe/xdm/blob/master/docs/reference/datatypes/marketing/commerce.schema.md
What are examples of products that are impacted by the issue
In Adobe Commerce, every cart is identified by a unique identifier, typically referred to as 'cart ID'. It is important for us to understand the cart ID for multiple reasons :

In order to execute an analysis of a particular customer cart. For example, cart ID = '123' has 4 products with a total value of $534. Last product was added to it on 1/1/22. The cart was viewed several times between 1/1/22 and 1/14/22, cart seems abandoned due to lack of activity since. Cart ID is typically utilized as a primary key to join events such as addtoCart, cartView and abandonCart to perform such an analysis.

Another use case, although not currently supported by Adobe commerce is for merchants to have multiple carts and the ability to identify the specific cart pertaining to an event.

For example, if you were to refer to amazon.com, you can simultaneously add products to the 'amazon cart' as well as 'the whole foods cart' on the same website.
Also, a product can be added to cart from several different locations on a website such as a product page, a recently viewed carousel, product recommendations carousel, candy isle etc. The "source" field represents where the product is added to cart from.
This information is utilized to comprehend the effectiveness of features such as product recommendations and act as a success metric for such features on a website that allow customer to add a product to cart.

Consolidated with #1468


Fix snippets index.html to use results_template_name for results

Until now, if you've set an index_results_template_name or used the namespaced template-lookup to override it, it was only used for the ajax-results, but not the normal index requests.
The {% include ... %} is now similar to wagtailadmin/generic/index.html (code).

[x] Do the tests still pass?[^1]
[x] Does the code comply with the style guide?

[x] Run make lint from the Wagtail root.

[x] For Python changes: Have you added tests to cover the new/fixed behaviour?

Please describe additional details for testing this change.
[^1]: Development Testing
[^2]: Browser and device support
[^3]: Accessibility Target

Going to put this into 5.2.2 as this would probably be a blocker for some migrations to use Snippets.

Added to 5.2 stable bc4f04067af09cb6e4a825f74d31975dc15abcbc


Fix Validate Code Coverage of an Unlocked Package task

The build function in Validate Code Coverage of an Unlocked Package task has not been updated to use the devhub username parameter in sfpowerkit, and will hence the task fails

Fixed in Relase 15


Add deduplication_level to engagement #757

Please see https://github.com/DefectDojo/Documentation/pull/12 for documentation.
As long as the other PRs which also change API-Upload are not merged, I wait. Afterwards I will create tests.

@wurstbrot Would you mind changing the migrations as there are some that have customized migrations. In order to account for this a new option has been added to track migrations in a different folder.

Is there an example where I can see how to add migrations in DefectDojo?

@aaronweaver I guess the code is good to go now?

@wurstbrot would you mind making the field deduplication_level a boolean? I chatted with @devGregA and once that's complete we'll merge this request up. Thanks for making DefectDojo better.

done.

Done thanks @wurstbrot


[explore] Tweaks to sorting in metric search

Is your feature request related to a problem? Please describe.
Currently when users searches metric in Chart Explore Metric dropdown, the search first displays the "ending" string of the metric, even if there is an exact match. For example if you search for san_francisco and your metrics include population_in_san_francisco san_francisco and san_francisco_weather your first result would be population_in_san_francisco
The proposal is to at least put the exact match first. See below more on ideal experience.
Describe the solution you'd like
Ideal experience?

exact match
starting string matches
anything else (string in middle or end)

From above example the expected result would be
san_francisco
san_francisco_weather
population_in_san_francisco

@zuzana-vej thanks for suggesting! it makes perfect sense.  It is a good-first-issue, but in case no one picks it up, we should be able to squeeze it in when enhancing the metric component.


Create Traversal_in_BinaryTree.cpp

Please mention the issue link in PRs comment section.
ISSUE: https://github.com/GoTo-Coders/DS-Algo/issues/40


[BUG] Invalid URL for tkn

Version
redhat-actions/openshift-tools-installer@v1
Describe the bug
Error: Invalid URL: /pub/openshift-v4/x86_64/clients/pipeline/0.13.1/
it appears the openshift-tools-installer has an invalid URL to where the tools are. it appears https://mirror.openshift.com/pub/openshift-v4/clients/pipeline/0.13.1/ shows the tarballs but i'm not seeing an x86_64 in the path
Steps to reproduce, workflow links, screenshots
Run redhat-actions/openshift-tools-installer@v1
Installing tkn matching version "0.13.1"
ℹ Tools will be installed from "mirror".

🔎 Searching for a version of tkn satisfying the range "0.13.1" that was input as "0.13.1"
Download directory for tkn is https://mirror.openshift.com/pub/openshift-v4/clients/pipeline/
Max tkn version satisfying 0.13.1 is 0.13.1
Error: Invalid URL: /pub/openshift-v4/x86_64/clients/pipeline/0.13.1/

❌ Failed to install tkn.

Using temporary directory for storage
📁 CLIs will be downloaded to /home/runner/work/_temp/openshift-bin
Added /home/runner/work/_temp/openshift-bin to PATH
Wrote out installed versions to /home/runner/work/_temp/openshift-bin/openshift-clients-installed.json

Thanks for reporting this. We are investigating this problem and update you as soon as possible.
If your use case satisfies please feel free to use input source: github to download and install binaries from GitHub instead of OpenShift Mirror.

Related issue https://github.com/redhat-actions/openshift-tools-installer/issues/58

@pcarney8 We have fixed this issue, could you please re-run your workflows and confirm.

Resolved in #59
Feel free to re-open if you find this not working.


You cannot drop a column ref'd in a partial index

Fixes DOC-7050
Relates to DOC-7029

Hi @mgartner !  Mind taking a look at this docs PR? it attempts to update the docs based on the limitation described in TA-96924, which has been published
Entirely possible there is nuance here that this docs update does not capture, happy to update the PR as needed!


Joey's comprehensive test of TileMerge filter

This is a squashed version of #87.

@dzenanz @joeykleingers outstanding work! :green_apple: