Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Behavior Request] Sort Names When Submitting as Sub Labels #217

Closed
NickM-27 opened this issue May 30, 2022 · 4 comments
Closed

[Behavior Request] Sort Names When Submitting as Sub Labels #217

NickM-27 opened this issue May 30, 2022 · 4 comments
Labels
bug Something isn't working

Comments

@NickM-27
Copy link

Describe the bug
Not really a bug, but I have seen a couple multiple-name submissions for frigate sub labels and they appear in chronological order but I think it would be better if they were alphabetized. We are adding a filter and otherwise John, Bob Bob, John appear as separate entries which can add clutter. I don't think it makes as much sense for frigate to handle this but I am open to that if it makes more sense for frigate to check for comma separated names.

@NickM-27 NickM-27 added the bug Something isn't working label May 30, 2022
@jakowenko
Copy link
Owner

I'll take care of this on the Double Take side. It's easy enough to sort before pushing to Frigate.

jakowenko added a commit that referenced this issue Jun 6, 2022
## [1.11.0-beta.3](v1.11.0-beta.2...v1.11.0-beta.3) (2022-06-06)

### Features

* **frigate:** sort sub labels alphabetically [#217](#217) ([82d8736](82d8736))

### Build

* **deps:** bump outdated packages ([0842d98](0842d98))
jakowenko added a commit that referenced this issue Jun 6, 2022
## [1.12.0-beta.1](v1.11.0...v1.12.0-beta.1) (2022-06-06)

### Features

* **frigate:** sort sub labels alphabetically [#217](#217) ([82d8736](82d8736))

### Build

* **deps:** bump outdated packages ([0842d98](0842d98))
@jakowenko
Copy link
Owner

@NickM-27 have you had a chance to try out the beta build? It should include this.

@NickM-27
Copy link
Author

NickM-27 commented Jun 9, 2022

I've been running it but haven't had an opportunity to test multiple people at the same time. That being said, I don't see how this wouldn't be working as expected

jakowenko added a commit that referenced this issue Jun 13, 2022
## [1.12.0](v1.11.0...v1.12.0) (2022-06-13)

### Features

* **api:** opencv preprocess face check ([ed30ad1](ed30ad1))
* aws rekognition support ([7904852](7904852))
* **detectors:** process images from specific cameras ([5d39d0c](5d39d0c))
* **frigate:** sort sub labels alphabetically [#217](#217) ([82d8736](82d8736))
* **frigate:** stop_on_match config option to break process loop ([4b98990](4b98990))
* **opencv:** adjust classifier settings via config ([2e6c512](2e6c512))
* **ui:** show config errors ([ddcaf89](ddcaf89))
* **ui:** upload images to process with detectors ([f774406](f774406))

### Bug Fixes

* **api:** sleep if image hasn’t changed during retry loop ([78e9808](78e9808))
* better handling of update check ([6de1cf1](6de1cf1))

### Build

* **deps:** bump outdated packages ([0842d98](0842d98))
* workflow dispatch [skip ci] ([a4f6e13](a4f6e13))
@jakowenko
Copy link
Owner

This was merged into master and included in the latest release. Let me know if you run into any issues.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants