holiday date not correct

please update the holiday of diwali in month of november instead in october.The date for diwali is 12/11/2023 not 12/10/2023.

Which country is this for? @tyagi858

India
On Thu, 22 Jun 2023, 2:22 pm PPsyrius, @.***> wrote:

Which country is this for? @tyagi858 https://github.com/tyagi858
—
Reply to this email directly, view it on GitHub
https://github.com/dr-prodigy/python-holidays/issues/1329#issuecomment-1602260779,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/A6O2EO3XZAPTH6V5BFCY6SDXMQBT5ANCNFSM6AAAAAAZPWLIK4
.
You are receiving this because you were mentioned.Message ID:
@.***>

Can you confirm a bit whether if your version of python-holidays is up-to-date? Here's the code for v0.26 for example which seems correct to me: @tyagi858
        # Directly lifted Diwali and Holi dates from FBProphet from:
        # https://github.com/facebook/prophet/blob/main/python/prophet/hdays.py
        # Warnings kept in place so that users are aware
        if year < 2001 or year > 2030:
            warning_msg = "Diwali and Holi holidays available from 2001 to 2030 only"
            warnings.warn(warning_msg, Warning)

        # https://www.timeanddate.com/holidays/india/diwali
        diwali_dates = {
            2001: (NOV, 14),
            2002: (NOV, 4),
            2003: (OCT, 25),
            2004: (NOV, 12),
            2005: (NOV, 1),
            2006: (OCT, 21),
            2007: (NOV, 9),
            2008: (OCT, 28),
            2009: (OCT, 17),
            2010: (NOV, 5),
            2011: (OCT, 26),
            2012: (NOV, 13),
            2013: (NOV, 3),
            2014: (OCT, 23),
            2015: (NOV, 11),
            2016: (OCT, 30),
            2017: (OCT, 19),
            2018: (NOV, 7),
            2019: (OCT, 27),
            2020: (NOV, 14),
            2021: (NOV, 4),
            2022: (OCT, 24),
            2023: (NOV, 12),
            2024: (NOV, 1),
            2025: (OCT, 20),
            2026: (NOV, 8),
            2027: (OCT, 29),
            2028: (OCT, 17),
            2029: (NOV, 5),
            2030: (OCT, 26),
        }

        # https://www.timeanddate.com/holidays/india/holi
        holi_dates = {
            2001: (MAR, 10),
            2002: (MAR, 29),
            2003: (MAR, 18),
            2004: (MAR, 7),
            2005: (MAR, 26),
            2006: (MAR, 15),
            2007: (MAR, 4),
            2008: (MAR, 22),
            2009: (MAR, 11),
            2010: (MAR, 1),
            2011: (MAR, 20),
            2012: (MAR, 8),
            2013: (MAR, 27),
            2014: (MAR, 17),
            2015: (MAR, 6),
            2016: (MAR, 24),
            2017: (MAR, 13),
            2018: (MAR, 2),
            2019: (MAR, 21),
            2020: (MAR, 10),
            2021: (MAR, 29),
            2022: (MAR, 18),
            2023: (MAR, 8),
            2024: (MAR, 25),
            2025: (MAR, 14),
            2026: (MAR, 4),
            2027: (MAR, 22),
            2028: (MAR, 11),
            2029: (MAR, 1),
            2030: (MAR, 20),
        }

        if year in diwali_dates:
            self._add_holiday("Diwali", *diwali_dates[year])

        if year in holi_dates:
            self._add_holiday("Holi", *holi_dates[year])

Can u check for 0.13 version beacuse i use python3.6 version
On Thu, 22 Jun 2023, 3:25 pm PPsyrius, @.***> wrote:

Can you confirm a bit whether if your version of python-holidays is
up-to-date? Here's the code for v0.26 for example
https://github.com/dr-prodigy/python-holidays/blob/master/holidays/countries/india.py
which seems correct to me: @tyagi858 https://github.com/tyagi858
    # Directly lifted Diwali and Holi dates from FBProphet from:
    # https://github.com/facebook/prophet/blob/main/python/prophet/hdays.py
    # Warnings kept in place so that users are aware
    if year < 2001 or year > 2030:
        warning_msg = "Diwali and Holi holidays available from 2001 to 2030 only"
        warnings.warn(warning_msg, Warning)

    # https://www.timeanddate.com/holidays/india/diwali
    diwali_dates = {
        2001: (NOV, 14),
        2002: (NOV, 4),
        2003: (OCT, 25),
        2004: (NOV, 12),
        2005: (NOV, 1),
        2006: (OCT, 21),
        2007: (NOV, 9),
        2008: (OCT, 28),
        2009: (OCT, 17),
        2010: (NOV, 5),
        2011: (OCT, 26),
        2012: (NOV, 13),
        2013: (NOV, 3),
        2014: (OCT, 23),
        2015: (NOV, 11),
        2016: (OCT, 30),
        2017: (OCT, 19),
        2018: (NOV, 7),
        2019: (OCT, 27),
        2020: (NOV, 14),
        2021: (NOV, 4),
        2022: (OCT, 24),
        2023: (NOV, 12),
        2024: (NOV, 1),
        2025: (OCT, 20),
        2026: (NOV, 8),
        2027: (OCT, 29),
        2028: (OCT, 17),
        2029: (NOV, 5),
        2030: (OCT, 26),
    }

    # https://www.timeanddate.com/holidays/india/holi
    holi_dates = {
        2001: (MAR, 10),
        2002: (MAR, 29),
        2003: (MAR, 18),
        2004: (MAR, 7),
        2005: (MAR, 26),
        2006: (MAR, 15),
        2007: (MAR, 4),
        2008: (MAR, 22),
        2009: (MAR, 11),
        2010: (MAR, 1),
        2011: (MAR, 20),
        2012: (MAR, 8),
        2013: (MAR, 27),
        2014: (MAR, 17),
        2015: (MAR, 6),
        2016: (MAR, 24),
        2017: (MAR, 13),
        2018: (MAR, 2),
        2019: (MAR, 21),
        2020: (MAR, 10),
        2021: (MAR, 29),
        2022: (MAR, 18),
        2023: (MAR, 8),
        2024: (MAR, 25),
        2025: (MAR, 14),
        2026: (MAR, 4),
        2027: (MAR, 22),
        2028: (MAR, 11),
        2029: (MAR, 1),
        2030: (MAR, 20),
    }

    if year in diwali_dates:
        self._add_holiday("Diwali", *diwali_dates[year])

    if year in holi_dates:
        self._add_holiday("Holi", *holi_dates[year])

—
Reply to this email directly, view it on GitHub
https://github.com/dr-prodigy/python-holidays/issues/1329#issuecomment-1602351453,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/A6O2EO3TRBV3CE4LKKGQW73XMQI75ANCNFSM6AAAAAAZPWLIK4
.
You are receiving this because you were mentioned.Message ID:
@.***>

I did check and it seems that the correction above was done in v0.18 which requires python >=3.7 at the very least.

Ok, thanks for the clarification.
On Thu, 22 Jun 2023, 3:41 pm PPsyrius, @.***> wrote:

I did check and it seems that the correction above was done in v0.18
https://github.com/dr-prodigy/python-holidays/releases/tag/v.0.18 which
requires python >=3.7 at the very least.
—
Reply to this email directly, view it on GitHub
https://github.com/dr-prodigy/python-holidays/issues/1329#issuecomment-1602374986,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/A6O2EOY4BPCW6AKTSFUQKKTXMQK5DANCNFSM6AAAAAAZPWLIK4
.
You are receiving this because you were mentioned.Message ID:
@.***>


Wrong attribution

I was surprised to found my shader from https://www.shadertoy.com/view/XsVSzW among the demos of your shader-toy project for VS Code https://github.com/stevensona/shader-toy/blob/master/demos/plasma1.glsl with attribution to S.Guillitte.
As You can see, the sources are the same, if skip the attribution. Could you remove that wrong attribution?

I'm super sorry, we should always link to the sources on shadertoy.com to make sure we give the right attribution. But I never made a pass to make sure that this is updated for our older examples.
Unfortunately I don't have any reliable access to push any changes until next week, so if this feels urgent to you I would encourage you to create a pull request with the attribution changes.
Otherwise I will do a pass on all shaders that we didn't create ourselves and unify the attributions as well as double check if they are correct.

My apologies for that, @alxklk. Thanks for bringing to our attention.


MAINT: remove uses of np.sctypeDict

Reference issue

https://github.com/numpy/numpy/issues/23999
What does this implement/fix?

Remove internal uses of numpy.sctypeDict, replace with less exotic idioms.

gh-18841 covers this already


Add Support for GetAppState Command

Change list
Added GetAppState.
Types of changes
What types of changes are you proposing/introducing to .NET client?
Put an x in the boxes that apply

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

Integration tests

[ ] Have you provided integration tests to pass against the latest version of appium? (for Bugfix or New feature)

Details
Added GetAppState-Command (http://appium.io/docs/en/commands/device/app/app-state/).

@akinsolb Do you have time to merge and publish these changes?


Manage packages to install/update

Signed-off-by: Bogdan Dobrelya<EMAIL_ADDRESS>

@tomassedovic note, the cluster deployed for me, with -e manage_packages=false. Testing e2e now.


Legitimate emails getting flagged as spam

Our legitimate emails are getting flagged as spam. It's surprising since email contains customer specific information so it's not the same email for each recipient. How do we turn this feature off or flag our emails as legitimate so this policy knows that we've approved them and it's not some rogue process?

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

ID: c3c27660-0f0b-3002-7183-854e4fb8716b
Version Independent ID: 3f436862-e6b3-2a9d-70b5-f7eee02eec2e
Content: Configure the outbound spam policy
Content Source: microsoft-365/security/office-365-security/configure-the-outbound-spam-policy.md
Service: o365-seccomp
GitHub Login: @MSFTTracyP
Microsoft Alias: tracyp

@LukeChung - Thank you for submitting feedback.
I think the best way forward is if you can open a service ticket in your tenant so this can get resolved ASAP. Based on outcome, let me know if it is something that can be called out in the docs.
If you don't mind please keep us posted here on the resolution and I really want to get this information you are discovering back into the docs.

We've submitted a ticket to no avail. The problem is the algorithm for flagging outbound spam is not good enough to differentiate between legitimate emails that may go out to a group of contacts vs. a real spammer, and can't be turned off. Having it trigger a blockage after 100 emails is way too low a threshold. Worse, it is not going to stop real spammers who do a lot more than 100 at a time.
This is especially annoying as we had to notify all of our customers of a bug Microsoft introduced with a Security Update (http://fmsinc.com/MicrosoftAccess/Errors/query_is_corrupt/), and Office 365 is preventing us from doing so. It just makes a bad situation worse. If a message is flagged as spam, Office 365 should allow customers to approve it and continue emailing it. If the customer is later found to be spamming, that can be dealt with but customers shouldn't be treated as guilty in advance. Note, we are well within the daily limits of Office 365 email accounts. It's the content of the emails that's being judged.
There are many situations with alerts where the failure to send out timely emails can lead to serious harm both financially and bodily. The change needs to be made at the policy level, or an explanation for how we need to change our emails to avoid having them flagged as spam.
Note, the last time we had a similar need was in March when we broadcasted without any blockage.


Always install crds for nonolm

For each of the following check the box when you have verified either:

the changes have been made for each applicable version
no changes are required for the item

Affected versions:

[x] Latest
[ ] 1.1
[ ] 1.0

The CSV is responsible in OLM installs for

[ ] Operator permissions
[ ] Operator deployment
[ ] Operand permissions
[ ] CRDs

The operator.yml is responsible in non-OLM installs for

[ ] Operator permissions
[ ] Operator deployment

The ansible role is responsible in non-OLM installs for:

[ ] Operand permissions
[ ] CRDs

The ansible role is always responsible for:

[ ] Operand deployment

If this PR updates a release or replaces channel

[ ] I created a new z release directory in deploy/olm-catalog/konveyor-operator
[ ] I updated channels in the konveyor-operator.package.yaml
[ ] I created a new release directory in deploy/non-olm
[ ] I created or updated the major.minor link in deploy/non-olm
[ ] Updated the .github/pull_request_template.md Affected versions list

This is in line with what OLM installs would do. OLM installs the CRDs regardless of whether the controller and UI are installed. And the MCG tasks expect the migstorage CRD to exist which seems rational.


feat(region): Regularly and automatically synchronize the status of cloud accounts

What this PR does / why we need it:

[x] Smoke testing completed

Does this PR need to be backport to the previous release branch?:

/area region
/cc @zexi @ioito

/lgtm
/approve


HDDS-9587. No serializer found for class ThreadLocal in DBSCanner for pipelines in scm.db

What changes were proposed in this pull request?
Fix for an exception which occurs during serialization of nodesInOrder when using ldb scan for scm.db and pipelines column family.
What is the link to the Apache JIRA
https://issues.apache.org/jira/browse/HDDS-9587
How was this patch tested?
Manual tests

Thanks @mladjan-gadzic for the patch.  Can you please add a test case in TestLDBCli?

@xBis7, @adoroszlai thanks for the review. Test is added.

Thanks @mladjan-gadzic for the patch, @xBis7 for the review.


Controllers freeze when switching scenes

When I switch from on scene to another my controllers freeze. No pose-updates or button interactions are possible. Headtracking works fine. I tried SteamVR_Loadlevel.Begin and pure SceneManager.LoadScene.
I also get an error: Failed to load IVRRenderModels interface version IVRRenderModels_006
SteamVR Plugin v2.1
HTC Vive - Standard

Looks like that error is unrelated. What scene are you trying to switch out of? I tested this in the Interaction Sample scene and it worked for me. Are there any other errors?

I think I just had problems with "SceneManager.MoveGameObjectToScene". With "DontDestroyOnLoad" i have a working solution now. Sorry for bothering you with this non-issue :sweat_smile:

I to had this issue but found the cause - you have to carry over the [SteamVR] prefab between scenes otherwise it has to be re-created (which is why I was able to get controllers to track again by toggling the component as that calls SteamVR.Initialize()
It's not a bug so much as something you have to do to handle scene-switching as out of the box the camera rig doesn't switch scenes either. Thought I'd post it here for anyone who needs it.

@BenWoodford Thanks! I will try your solution.

Ah that makes sense. I'll add a checkbox to the component for DoNotDestroy.

@zite probably worth adding one to the CameraRig too, and if the [SteamVR] object is spawned in automatically rather than already part of the scene, copy the settings over from the CameraRig.

I've added this checkbox in the 2.2b1 beta on the releases page: https://github.com/ValveSoftware/steamvr_unity_plugin/releases/tag/2.2b1


Panes within tabs?

I have a Vim workflow that I am having trouble recreating in Atom. Most of my tabs consist of a split, for a file and its tests:

Thus I can { and } my way through tabs and [ and ] my way through splits within them, and all was right with the world. My splits are about keeping related files together, not separate panes or editors.
The modeling of Pane and EditSession doesn't really allow this right now. It's fairly easy to see a number of ways to do it, but I was stymied when I started to edit core stuff by things marked as internal. @kevinsawicki said to ignore that, so I'm going to slowly work on something that works for me. But he also said to make an issue, so here it is. I'm hoping that one of you core guys sees a super easy way to do it :)

+1 coming from Vim this is my biggest drawback right now. I use my tabs as different workspaces (like tmux also).

+1

+1

I could really use this as well. In my "pre-atom" workflow I used tmux and vim. It would be great to fire up a terminal, start my dev server, hop over to a new tab, and open a split-pane view of my html/css/js code.

+1

Moving my comment from #11349 here:
When I code, I conceptually split work into logically separate sections of the project, each of which involves working with multiple files at once: Data flow, Styling, UI components, etc. Surely I'm not alone.
Atom's current tab model sadly makes it difficult to map this way of working to the current workspace. I think we would all benefit immensely from changing it to Vim's model.

+1

+1

+1

+1

+1

+1

👍

I would love in-tab splits. Maybe we can keep Atom's current functionality and just add onto it. The current commands for splitting panes can remain the same, and new commands can be added that can make split windows (perhaps call these ones windows instead of panes, in order to differentiate?) inside of a tab.  The end result would be that panes contain tabs, and tabs contain windows (named similarly to vim's windows).

In NeoVim I like having files for a single component inside a tab. For example, a js file, html file, and css file, all split within a single tab. The workflow in Atom is quite different: it encourages bunching of similar files (for example, all CSS files in one pane, all HTML files in another pane, and all JS files in a third), so that the files for a single component can be visible all at once by selecting the appropriate tabs in each pane, but this will get in the way when trying to view other files that don't fit into the same component pattern. The splits-inside-tabs functionality would make it easier to group things (co-locate things) component-wise.

Another idea could be to introduce an ability to switch Workspaces easily within a window, along with an extra UI around that feature to make it easy. Since Atom already has tabs on a per-pane basis, then maybe "workspaces" could be used to group panes together. After thinking for a little while, I like this idea better, and think that it would be better than NeoVim's.
But, since thetab UX feature is already used on panes, how would the workspace switching look like? Would it be similar to OS X's Expose (Mission Control)? Or perhaps more like Gnome 3's vertical workspaces?
On a side note, I'm making a 3D library at http://infamous.io (demos and docs coming soon), and I might like to implement something useful with it (for example, workspace switching).
Does anyone reading this know if it's possible to have multiple Workspace instances in a single window currently?

Hmmmm, after researching the API for a little while, it seems that Workspaces have some functionality that we may not want to duplicate across some form of end-user "workspaces".
Maybe we can instead call this new feature PaneGroups, an have it strictly contain panes, so that the window's overall Workspace can still have things like top panels, etc, stuff that we wouldn't necessarily want to modify on a per-panegroup basis.
Question to anyone reading: would you like file tree instances on a per-panegroup basis? Or just one file-tree in the workspace, with pane groups containing literally nothing but panes (along with some way of navigating them)?

Alright, so after taking a look at the Workspace class, it appears that Workspace is a proxy over PaneContainer (Workspace contains a single PaneContainer).
It seems that in order to make this change I would have to modify (or extend) Workspace to make it possible for Workspace to contain multiple PaneContainers.
I'm completely new to Atom, so I'm not sure yet if it's possible to extend Workspace (and replace the class with the extended version) before it gets instantiated. If not, then it might not be possible to do this as an Atom package, and would need some modifications to Atom's Workspace class.
PaneContainer already is the pane-containing thing we'd want to take advantage of (rather than PaneGroup I suggested above).
I'm not yet sure how best to make this happen. If anyone has any ideas please do share. Will be back later...

Some other things to note are that the current Workspace (souped-up PaneContainer) also contains things like a PackageManager instance, etc, things that we wouldn't want to duplicate. The change needed to make this effective might be to first separate those concerns so that it's possible to have multiple WorkSpaces in the same window without duplicate things like the package manager.

Another idea might be to use PaneContainer inside of a tab, so then the UI would become a nested set of PaneContainers (the current commands for splitting panes would work on the focused PaneContainer or Pane). So inside of tabs we could have Panes with more tabs. I still have to get more familiar with the API...

Setting aside whether or not it is a good idea to try and replace Workspace, it doesn't look like it will be easy to do it through a package if you look at how the atom environment is initialized:
You can see here that the PackageManager is created before the Workspace. However, loadPackages is not called until startEditorWindow. By that time, Workspace has already been created and maybe used for several other things.
As far as trying to replace Workspace, that seems like a pretty heavy handed solution since it could potentially cause a lot of breakage for other packages. Maybe it could be done but if there was any other way it would probably be better to avoid it.

This has already gotten it's fair share of +1's but I would love this as it is my biggest drawback to sticking with atom. I have many years of a 'vim' workflow that involved splitting inside of a tab that is too hard to overcome

I too would love this. +1!

+1

+1

+1

but I would love this as it is my biggest drawback to sticking with atom

Agreed, +1

+1

+1, it's indeed the biggest drawback

+1

👍

👍

+1

👍

I'm using this plugin https://github.com/vim-ctrlspace/vim-ctrlspace which makes even more use of panes within a tab. This plugin has a separate on demand pane with list of opened buffers in a tab. Together with ability to rename a tab this gives you even more structure.
Usually I have 6 - 12 tabs opened in VIM, named by project part. And within each tab I have 1-20 buffers (files) attached (opened) while only one or two are simultaneously visible (opened as panes).
While similar structure may be achieved by proper arrangement of files within a project folders, it's much more flexible to have an alternative "folder view" on the project functionality part in the editor.
Unfortunately this plugin is no more maintained and it makes VIM very slow soon.
So, not having panes within a tab is a show-stopper for me to enjoy great Atom infrastructure.

True, panes within tabs make much organizational sense. If people took the time to learn Vim, then they'd realize how nice organization with panes inside tabs. If Atom took the time to make it, then they'd also realize how powerful it is.

Also no one explains the ideas behind the concept used in Atom (VS Code, IntelliJ, ...), where I see writeups like @Dmitra why Vims version is better more often. Which are the use cases developers of these editors thought "hey lets do tabs in splits, it makes sense because XYZ"?

+1

+1

+1 for me as well. This may stop me from switching to Atom :(.

Lately, there's a new plugin on the block that adds it's own tab system, so we can have panes inside tabs: https://atom.io/packages/atom-vim-like-tab
If you disable Atom's tab plugin, and use this one instead, you can split panes inside these tabs. It works great! You can, for example, map gt to go to next tab, gT for previous tab.

+1 — I, too, was surprised/disappointed to find out I couldn't make a "tab of tabs", so to speak...

Forget  it and use Neovim ;)

Thanks everyone for the feedback.
At this point, we don't have any plans to change Atom's view system to enable this scenario. If this is functionality that you need, you may want to check out the atom-vim-like-tab package that @trusktr mentions above.
Thanks again for everyone's input and especially the link to the great community package!


Unable to save training data extracted with gradient method

Hi,
I was able to smoothly run the code and save the file with the template method. However, when the same input file is processed with the gradient method,  I am unable to save it. This is the error message I get:
ValueError                                Traceback (most recent call last)
Cell In[22], line 2
1 # Save the result
----> 2 x = np.array(events)
3 y = np.array(scores)
4 indices = np.array(idx)
ValueError: setting an array element with a sequence. The requested array has an inhomogeneous shape after 1 dimensions. The detected shape was (303,) + inhomogeneous part.
Can you please help me solve this issue?

Just to clarify, this is to extract training data to train a model, right?
Regarding the error message, I had a quick look at the code. With the example data provided by us I can extract and save training data and open it. I assume that you are trying to extract data from your own data? Without the data I cannot reproduce the error.
But in any case, the error occurs because "events" is a list that contains arrays. Each array corresponds to an extracted stretch of data. They should all have the length of win_size (but in your case they likely don't). The error occurs when the list of arrays is converted into an array of arrays. This only works if all arrays have the same length, which probably is not the case here, and leads to the error. At least that's my guess without being able to reproduce the error.
My best guess is that the problem comes from the following line:

for ind, location in enumerate(peaks):
if location < trace.data.shape[0] - int(win_size1.5):
event = copy.deepcopy(trace.data[location-int(1/6win_size):location+int(5/6*win_size)])
if location is very close to the start of the data, it may cause issues because we extract:
location-int(1/6win_size) : location+int(5/6win_size)
This happens twice, when we extract clear events and when we extract unclear events, FPs and so on.
You can replace the two parts with the following snippet:

for ind, location in enumerate(peaks):
if location < trace.data.shape[0] - int(win_size1.5) and location > int(1/2win_size):
event = copy.deepcopy(trace.data[location-int(1/6win_size):location+int(5/6win_size)])
I'll have updated the file on GitHub as well. In case you can just pull the changes and hopefully it fixes the issue. But let me know if it persists.

Hi,
Yes I mean to extract training data to train the model.
I tried to implement what you suggested but the same problem persists.
However I think I found where it is coming from. I think the issue comes when you change the window size from 600 to anything else.
I tried this also with the example data that you have provided. I had no issues saving the extracted data when the window size was set to 600. But when I change it to anything else, then the same issue appears.
Best regards,
Anusha.

Ok, I believe now I found the issue (at least I could reproduce the error). The following lead to rounding issues:
event = copy.deepcopy(trace.data[location-int(1/6win_size):location+int(5/6win_size)])
I replaced it with the following:
left_buffer = int(1/6*win_size)
right_buffer = win_size - left_buffer
event = copy.deepcopy(trace.data[location-left_buffer:location+right_buffer])
The file is already updated, I hope this fixes the issue, but let me know if it persists for you.

Hi,
Yes the issue is fixed for me now.
Thank you so much!


Sysmon TCP SYN

Whether the network monitoring of SYSMON supports the behavior of trying to connect, for example, only sending the SYN packet, and the connection is not established. thx

Thanks for the question. No, Sysmon does not currently support this and there are not current plans to support this level of monitoring.


Update dependency on parity-wasm

@DemiMarie-parity could you provide some more description here so that it's easy for someone not deeply involved to pick this up?

I am afraid that it would entail some deep changes, so assigning it to myself.


Middleware validation callback receives request by value

References the #8, can be merged after testing.

This works for me!
I actually forked this library yesterday and made these changes, and switching from my fork to your impl required no changes on my end (probably because the changeset was identical)

Actually it looks like my fork was naive, I didn't get rid of the Validate struct, I just modified how it worked.

Thank you for this library, btw. I hope to have it in a "production" system sometime soon. My project is a hobby, though, so we'll see how it turns out


Fix sqlworkbenchj URL

Editing an existing cask

[x] Commit message includes cask’s name (and new version, if applicable).
[x] brew cask audit --download {{cask_file}} is error-free.
[x] brew cask style --fix {{cask_file}} left no offenses.

The download fails because a newer version was released and this version
was moved to the archive folder.
I've asked the maintainer for more durable download urls. In the
meantime, I figured it's better to have a working url than the latest
url which will break again when a new version is released.

I figured it's better to have a working url than the latest
url which will break again when a new version is released.

Broken URLs are the worst. 😜


External terminal not working for debugging node program

Bug found while testing #12252

VSCode Version: 1.6 Insider
OS Version: Ubuntu 16.04

Debug on external terminator only works for gnome-terminal, the default on Ubuntu. Fails for rxvt-unicode and terminator.
Steps to Reproduce:
One: Create an empty project. npm i express. Make app.js like this:
var express = require('express');
var app = express();

var process = require('process');

console.log(process.cwd());
console.log(process.argv);

app.get('/', function (req, res) {
  res.send('Hello World!');
});

app.listen(3000, function () {
  console.log('Example app listening on port 3000!');
});

Two:
My launch.json
{
    "version": "0.2.0",
    "configurations": [
        {
            "name": "Launch",
            "type": "node",
            "request": "launch",
            "program": "${workspaceRoot}/app.js",
            "stopOnEntry": false,
            "args": ["test"],
            "cwd": "${workspaceRoot}/node_modules",
            "preLaunchTask": null,
            "runtimeExecutable": null,
            "runtimeArgs": [
                "--nolazy"
            ],
            "env": {
                "NODE_ENV": "development"
            },
            "console": "externalTerminal",
            "sourceMaps": false,
            "outFiles": []
        }
    ]
}

Workspace setting:
{
    "terminal.external.linuxExec": "rxvt-unicode"
}

rxvt-unicode
Launches external terminal. Outputs Debugger listening on [::]:43160, but after few seconds VSCode show error saying "Cannot launch debug target in terminal (timeout)".
terminator
Launches external terminal. Almost look like cd'ed into cwd, because it shows octref@ubuntu:~/Downloads/test/node_modules, the cwd I specified in the launch config.
Same error "Cannot launch debug target in terminal (timeout)" is shown after a few seconds.

I think this is as designed and that rxvt-unicode and terminator where never supported. Anyways leaving for @weinand to decide.


Added support for SSML

This resolves #2132.
Since SSML is just a markup language, SSML is implemented as an alias of markup.

While committing, I got a 502 from GitHub. It was merged but this is still open. I'll just close this and pretend nothing bad happened.


vlog_to_model and vlog_to_pbtype ignore ASSOC_CLOCK attribute

According to https://github.com/antmicro/symbiflow-arch-defs/blob/master/utils/vlog/vlog_to_model.py#L8 this attribute can be used to manually associate clock to a specific port. However, this attribute seems to be ignored.

this commit https://github.com/SymbiFlow/symbiflow-arch-defs/pull/639/commits/de99a2c7223847186afcf5600cce52ea0c8a574d
from #639 adds ASSOC_CLOCK handling to vlog_to_model

this is fixed


Setup default passthrough TCP route in proxy

As discussed with @rshriram I will take over his PR #4376
cc @costinm @mandarjog @kyessenov
ref envoyproxy/data-plane-api#208
This will allow traffic to unknown egress destinations to pass through as is, for any port that does not match the listeners.
This appears to be a bit more nuanced:

For HTTPS on port 443 pass through for unknown destinations will work no matter if 443 is used inside the mesh as well.
For e.g. HTTP on port 80 this is not the case.

As far as I see that is because https://github.com/istio/istio/blob/ba00f31714321d17de99854097fe2a441c04e127/pilot/pkg/networking/deprecated/config.go#L443-L455 registers outbound HTTP listeners with WildcardAddress while HTTPS listener is registered for the specific IP address. https://github.com/istio/istio/blob/c5499c42660c936a5f0e5cd622615aac1b248e8e/pilot/pkg/proxy/envoy/v1/config.go#L771-L779
Fixes #3876

[x] Add original_dst cluster
[x] Add TCPProxyFilter to point to original_dst cluster
[ ] Add mixer config to get telemetry (and policy enforcement?)
Don't see a way to apply mixer config for the outbound path.
[x] Add feature flag to istio/api MeshConfig (pending PR https://github.com/istio/api/pull/428)
[ ] Provide unit tests
[ ] Provide e2e test
[ ] Document how to switch on this behaviour
[ ] Repeat vor v1alpha3
I guess this best goes into a separate PR. Thoughts?

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approver: ayj
Assign the PR to them by writing /assign @ayj in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

pilot/OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

Hi @loewenstein. Thanks for your PR.
I'm waiting for a istio member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.
I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

same as earlier; must come at least with a flag and probably also go to mixer for telemetry/discovering that fall through fallback. the default at least for most test must be off as otherwise we'll gloss over basic bugs

@ldemailly flag will be introduced here: https://github.com/istio/api/issues/428
Telemetry turns out not to be not too easy for outbound traffic... Reporting is usually done on the destination side. Any ideas how to do it nonetheless are welcome.

@loewenstein: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-unit-tests.sh
666ff5db1a1df22111a491a2d276aba80c60cdda
link
/test istio-unit-tests

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@loewenstein: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-unit-tests.sh
c068fcd4df4c54198ab42e73367d88eb5dadf90b
link
/test istio-unit-tests

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/test istio-unit-tests

@loewenstein: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-unit-tests.sh
c068fcd4df4c54198ab42e73367d88eb5dadf90b
link
/test istio-unit-tests

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/retest

@loewenstein: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-unit-tests.sh
c068fcd4df4c54198ab42e73367d88eb5dadf90b
link
/test istio-unit-tests

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

#. I didn't find an example of how to get mixer reporting into the outbound path for tcp traffic. Unless someone can offer a pointer or help I don't see how to do it or if it is at all possible.
#. My current setup for manually testing this change has two k8s clusters and an small go app responding 'pong' to 'ping' requests.

Cluster 'external' has the pinger app listening on 8888 for http traffic and on 443 for https traffic.
Cluster 'istio' has the pinger app configured to ping both apps on the other cluster.
How would I bring that into a single cluster? I didn't try to just put the 'external' apps into a separate namespace without injection configured. Would that work or confuse Istio in some way?
#. Where would I document how to use the new configuration option?
#. Should we run the golden tests with and without the option set? I hesitated to duplicate the golden files, so my response would be: No! Thoughts?

@loewenstein: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-unit-tests.sh
c068fcd4df4c54198ab42e73367d88eb5dadf90b
link
/test istio-unit-tests

prow/istio-pilot-e2e-v1alpha3.sh
c068fcd4df4c54198ab42e73367d88eb5dadf90b
link
/test istio-pilot-e2e-v1alpha3

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@loewenstein: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-e2e-v1alpha3.sh
c068fcd4df4c54198ab42e73367d88eb5dadf90b
link
/test istio-pilot-e2e-v1alpha3

prow/istio-unit-tests.sh
2b1e38faa7b9d7a160d480ae7416c3706bb894f1
link
/test istio-unit-tests

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@loewenstein: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-e2e-v1alpha3.sh
c068fcd4df4c54198ab42e73367d88eb5dadf90b
link
/test istio-pilot-e2e-v1alpha3

prow/istio-unit-tests.sh
2b1e38faa7b9d7a160d480ae7416c3706bb894f1
link
/test istio-unit-tests

prow/istio-pilot-e2e.sh
c068fcd4df4c54198ab42e73367d88eb5dadf90b
link
/test istio-pilot-e2e

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@loewenstein: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-unit-tests.sh
2b1e38faa7b9d7a160d480ae7416c3706bb894f1
link
/test istio-unit-tests

prow/istio-pilot-e2e.sh
c068fcd4df4c54198ab42e73367d88eb5dadf90b
link
/test istio-pilot-e2e

prow/istio-pilot-e2e-v1alpha3.sh
2b1e38faa7b9d7a160d480ae7416c3706bb894f1
link
/test istio-pilot-e2e-v1alpha3

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@loewenstein: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-unit-tests.sh
2b1e38faa7b9d7a160d480ae7416c3706bb894f1
link
/test istio-unit-tests

prow/istio-pilot-e2e-v1alpha3.sh
2b1e38faa7b9d7a160d480ae7416c3706bb894f1
link
/test istio-pilot-e2e-v1alpha3

prow/istio-pilot-e2e.sh
2b1e38faa7b9d7a160d480ae7416c3706bb894f1
link
/test istio-pilot-e2e

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@loewenstein: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-e2e.sh
2b1e38faa7b9d7a160d480ae7416c3706bb894f1
link
/test istio-pilot-e2e

prow/istio-pilot-e2e-v1alpha3.sh
e85435779a07425e15fbed464a509ac6370400ae
link
/test istio-pilot-e2e-v1alpha3

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@loewenstein: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-e2e-v1alpha3.sh
e85435779a07425e15fbed464a509ac6370400ae
link
/test istio-pilot-e2e-v1alpha3

prow/istio-pilot-e2e.sh
e85435779a07425e15fbed464a509ac6370400ae
link
/test istio-pilot-e2e

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

I still suggest targeting v2 and not v1. We are going to be dropping v1 very soon (its deprecated). It makes no sense to add features to v1.

on the other hand v2 doesn't fully work yet so at least for 0.8, v1 is still likely to be what people uses first, before migrating to v2

@rshriram @ldemailly I suppose covering both would be good. I definitely plan to cover v2 next.
I hoped to get some response to my earlier comments...

@loewenstein: PR needs rebase.

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.


0.11.0

Yay! I have been waiting to update glium_graphics for a while now. Using different major version on the image library causes some problems with integration.


Preferences setting getting from project scope inconsistent

I'm wanting to be able to read and write preferences for the current project. The below code works fine when reading and writing preferences while editing a file in the current project.
However when editing a file that isn't in the current project (but displayed in the "working files" area), getPref("my-pref", "project") returns the default value instead of value in the current opened project while setPref("my-pref", "something", "project") correctly writes the value to the current open project.
I'm not sure if this is a bug - but even if it isn't how can I read preferences from the currently opened project even if the file that is currently in the editor isn't from the project?
function getPref(pref, passedScope) {
    if (passedScope === "project" || passedScope === "user") {
        return prefs.get(pref, {
            location: {
                scope: passedScope
            }
        });
    } else {
        return prefs.get(pref);
    }
}

function setPref(pref, value, passedScope) {
    if (passedScope === "project" || passedScope === "user") {
        prefs.set(pref, value, {
            location: {
                scope: passedScope
            }
        });
    } else {
        prefs.set(pref, value);
    }
}

@abagshaw We usually use our slack channel, https://brackets.slack.com or the brackets-dev google group to discuss technical stuff.
I think we need to dig in a bit into why this is happening. Would you mind debugging a bit more into why the default settings are getting read (I am thinking this is by design, buy this is just my hunch). Also  please start a conversation in our slack channel, about this. Thanks!

Hi @nethip sure - I'll see if I can dig up any more info on how this is happening. I'm not super familiar with Slack - but is seems I need an invite to join https://brackets.slack.com is this correct?

@abagshaw You could register at this URL. https://brackets-slack.herokuapp.com/.


Fixes code title not visible on light theme.

Code titles were not visible on light theme because they had white text color. It was small enough fix so, I directly created this PR.
Reproduction of the issue

Goto:  https://ui.shadcn.com/docs/theming#list-of-variables
Switch to light mode. The code titles will not be visible.
Not if we switch back to dark theme they will be visible.

Here are the screenshot as well:
Dark Mode

Light Mode

Alternate Solution
We can also fix this by this css as well:
[data-rehype-pretty-code-title] {
    color: initial;
}

closes in favour of #3894


Bot cant connect to discord?

Summary
Im trying to make a Selfbot but its just saying: "cannot import name 'handle_message_parameters' from 'discord.http'"
Reproduction Steps
I just installed discord and discord.py-self with the pip command. Thats it.

Checklist

[X] I have searched the open issues for duplicates.
[X] I have shared the entire traceback.
[X] I am using a user token (and it isn't visible in the code).

Additional Information
i coded many of selfbots 1-2 Months ago before and now its saying that i need Intents? idk i think thats weird.

Uninstall discord.py

Please try actually looking at previous issues and discussions first. For example (from yesterday)...


Cannot get real time data being always zero despite good communication according debug logs

Describe The Bug:
Real time value is always 0 lux
To Reproduce:
Nothing special.
Expected behavior:
Having the real time data correct as it look to be a calculation issue.
Logs:
[4/13/2022, 5:21:32 PM] [SolaredgeRealTime] Connecting to Inverter real-time at <IP_ADDRESS>
[4/13/2022, 5:21:32 PM] [SolaredgeRealTime] Connected
[4/13/2022, 5:21:32 PM] [SolaredgeRealTime] Received Power:  [ 10198 ]
[4/13/2022, 5:21:32 PM] [SolaredgeRealTime] Interpreted power value:  -55338
[4/13/2022, 5:21:32 PM] [SolaredgeRealTime] Received SF:  [ 65535 ]
[4/13/2022, 5:21:32 PM] [SolaredgeRealTime] Computed: -5533.8
[4/13/2022, 5:21:32 PM] [SolaredgeRealTime] Updating Ambient Light Level:  0.0001
[4/13/2022, 5:21:32 PM] [SolaredgeRealTime] closed connection to <IP_ADDRESS>

Plugin Config:
{
    "name": "SolaredgeRealTime",
    "inverter": [
        {
            "id": "Inverter-realtime",
            "displayName": "Inverter real-time",
            "ip": "<IP_ADDRESS>",
            "port": 1502,
            "updateInterval": 5,
            "powerAddress": 40083,
            "powerSfAddress": 40084,
            "powerUnsignedValue": false
        }
    ],
    "platform": "SolaredgeRealTime"
}

Screenshots:

Environment:

Plugin Version:
OS: Ubuntu 20.04.4 LTS (HassIO under vmware VM)
Software: 1.4.0
Node: 16.14.2
npm: 8.6.0

You are right. It works.
But instructions seems not correct so:

in your json.config it's now
"powerUnsignedValue": true
and that is the truth ;-)

Correct. Updating the GUI for clarity can be appreciated.

Starting with version 0.11 the plugin can display two light meters when values are signed (can be negative). So you can now monitor import and export. I will adapt the UI for more clarity.
Thanks for the feedback

Check out version 0.13


sidecar back button behaves oddly

Desired behavior: if i'm looking at resource R1, click on something in that view that drills down to resource R2, the back button should bring me back to R1
Actual behavior: if R1 is at history index i1, and R2 is at index i2 != i1 + 1, then the back button activates whatever resource R3 is at i2 - 1.
History: [ R1, R3, R2 ]

history is ordered by insertion, not by visitation


Update Readme with examples from test cases

First, thank you so much for creating this project, it's absolutely brilliant, and has made using Supabase with Swift so nice.
When first coming to use this project, the examples in the integration tests were super useful for getting up to speed. The existing examples in the Readme didn't work for me, but these did. I thought it might be useful to update the Readme with these examples, so new people coming to the project can also use them.
This PR is just taking some of the examples from the integration tests, and using them as examples in the Readme.

Thanks for PR this @richthornton


Create Broker Form Component

Broker Form Component :

@Msarawan  Form name filed should not be take full width of page. It should take half width of page. You can use layout like Grid etc.  Buttons are missing in form i.e. Create and Cancel
On cancel, user should redirect on brokers list page , it should be done by routing.
See below screenshot for reference.

closing this PR against new PR https://github.com/artemiscloud/activemq-artemis-self-provisioning-plugin/pull/47


Updated dependencies + Avoided expressjs deprecation warning

Note that while npm test was successful and the debugger UI is working so far, we should do more testing before we merge this PR. Let me know if anyone finds any new bugs.

Coverage remained the same at 86.842% when pulling 7d9f48bf871ef11bf63039f1c68966e5a769f3d0 on tejashah88:master into b622cf131b10194b080de77bd2331ae15ddc3df4 on alexa-js:master.

Coverage remained the same at 86.842% when pulling f9a62cffd316925a4406f723eaa50366cd7ed4c3 on tejashah88:master into b622cf131b10194b080de77bd2331ae15ddc3df4 on alexa-js:master.

Trust the tests. I'm merging this. Onward :)


Today.com

Checklist

[x ] I'm reporting a broken site support
[ ] I've verified that I'm running youtube-dl version 2020.03.24
[ ] I've checked that all provided URLs are alive and playable in a browser
[ ] I've checked that all URLs and arguments with special characters are properly quoted or escaped
[ ] I've searched the bugtracker for similar issues including closed ones

Verbose log

[debug] System config: []
[debug] User config: []
[debug] Custom config: []
[debug] Command-line args: ['--no-check-certificate', '--verbose', 'https://www.today.com/health/coronavirus-outbreak-how-avoid-going-stir-crazy-during-self-isolation-t176155']
[debug] Encodings: locale UTF-8, fs utf-8, out utf-8, pref UTF-8
[debug] youtube-dl version 2020.03.24
[debug] Python version 3.8.2 (CPython) - macOS-10.15.4-x86_64-i386-64bit
[debug] exe versions: ffmpeg 4.1-tessus, ffprobe 4.2.2, rtmpdump 2.4
[debug] Proxy map: {}
[NBCNews] t176155: Downloading webpage
ERROR: An extractor error has occurred. (caused by KeyError('video')); please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; see  https://yt-dl.org/update  on how to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.
Traceback (most recent call last):
  File "/Library/Frameworks/Python.framework/Versions/3.8/lib/python3.8/site-packages/youtube_dl/extractor/common.py", line 530, in extract
    ie_result = self._real_extract(url)
  File "/Library/Frameworks/Python.framework/Versions/3.8/lib/python3.8/site-packages/youtube_dl/extractor/nbc.py", line 401, in _real_extract
    video_data = data['article']['content'][0]['primaryMedia']['video']
KeyError: 'video'
Traceback (most recent call last):
  File "/Library/Frameworks/Python.framework/Versions/3.8/lib/python3.8/site-packages/youtube_dl/extractor/common.py", line 530, in extract
    ie_result = self._real_extract(url)
  File "/Library/Frameworks/Python.framework/Versions/3.8/lib/python3.8/site-packages/youtube_dl/extractor/nbc.py", line 401, in _real_extract
    video_data = data['article']['content'][0]['primaryMedia']['video']
KeyError: 'video'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/Library/Frameworks/Python.framework/Versions/3.8/lib/python3.8/site-packages/youtube_dl/YoutubeDL.py", line 797, in extract_info
    ie_result = ie.extract(url)
  File "/Library/Frameworks/Python.framework/Versions/3.8/lib/python3.8/site-packages/youtube_dl/extractor/common.py", line 543, in extract
    raise ExtractorError('An extractor error has occurred.', cause=e)
youtube_dl.utils.ExtractorError: An extractor error has occurred. (caused by KeyError('video')); please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; see  https://yt-dl.org/update  on how to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.

Description

URL: https://www.today.com/health/coronavirus-outbreak-how-avoid-going-stir-crazy-during-self-isolation-t176155

crap...already an issue


vulns: add curl and libcurl vulns

I ran a genesis dump without these changes (see https://github.com/stackrox/scanner/pull/1276). You'll notice in that PR in the genesis dump logs, you will find logs saying CVE-2023-38545 and CVE-2023-38546 are missing for several dsitributions. With this PR, they are no longer missing, as we utilize the CVSSv3 scores from our "NVD" manual entries.
Note: this does not affect Red Hat, as they track CVSS scores, themselves

/retest

postgres=# select v.name, n.name, v.metadata from vulnerability v join namespace n on v.namespace_id = n.id where v.name = 'CVE-2023-38545';
      name      |      name       |
                                                                                metadata

----------------+-----------------+-----------------------------------------------------------
----------------------------------------------------------------------------------------------
----------------------------------------------------------------------------------------------
---------------------------------------------
 CVE-2023-38545 | debian:12       | {"NVD":{"CVSSv2":{"ExploitabilityScore":0,"ImpactScore":0,
"Score":0,"Vectors":""},"CVSSv3":{"ExploitabilityScore":1.6,"ImpactScore":5.9,"Score":7.5,"Vec
tors":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H"},"LastModifiedDateTime":"2023-10-11T00:00
Z","PublishedDateTime":"2023-10-11T00:00Z"}}
 CVE-2023-38545 | debian:unstable | {"NVD":{"CVSSv2":{"ExploitabilityScore":0,"ImpactScore":0,
"Score":0,"Vectors":""},"CVSSv3":{"ExploitabilityScore":1.6,"ImpactScore":5.9,"Score":7.5,"Vec
tors":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H"},"LastModifiedDateTime":"2023-10-11T00:00
Z","PublishedDateTime":"2023-10-11T00:00Z"}}
 CVE-2023-38545 | debian:13       | {"NVD":{"CVSSv2":{"ExploitabilityScore":0,"ImpactScore":0,
"Score":0,"Vectors":""},"CVSSv3":{"ExploitabilityScore":1.6,"ImpactScore":5.9,"Score":7.5,"Vec
tors":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H"},"LastModifiedDateTime":"2023-10-11T00:00
Z","PublishedDateTime":"2023-10-11T00:00Z"}}
 CVE-2023-38545 | debian:11       | {"NVD":{"CVSSv2":{"ExploitabilityScore":0,"ImpactScore":0,
"Score":0,"Vectors":""},"CVSSv3":{"ExploitabilityScore":1.6,"ImpactScore":5.9,"Score":7.5,"Vec
tors":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H"},"LastModifiedDateTime":"2023-10-11T00:00
Z","PublishedDateTime":"2023-10-11T00:00Z"}}
 CVE-2023-38545 | debian:10       | {"NVD":{"CVSSv2":{"ExploitabilityScore":0,"ImpactScore":0,
"Score":0,"Vectors":""},"CVSSv3":{"ExploitabilityScore":1.6,"ImpactScore":5.9,"Score":7.5,"Vec
tors":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H"},"LastModifiedDateTime":"2023-10-11T00:00
Z","PublishedDateTime":"2023-10-11T00:00Z"}}
 CVE-2023-38545 | alpine:v3.17    | {"NVD":{"CVSSv2":{"ExploitabilityScore":0,"ImpactScore":0,
"Score":0,"Vectors":""},"CVSSv3":{"ExploitabilityScore":1.6,"ImpactScore":5.9,"Score":7.5,"Vec
tors":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H"},"LastModifiedDateTime":"2023-10-11T00:00
Z","PublishedDateTime":"2023-10-11T00:00Z"}}
 CVE-2023-38545 | alpine:v3.15    | {"NVD":{"CVSSv2":{"ExploitabilityScore":0,"ImpactScore":0,
"Score":0,"Vectors":""},"CVSSv3":{"ExploitabilityScore":1.6,"ImpactScore":5.9,"Score":7.5,"Vec
tors":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H"},"LastModifiedDateTime":"2023-10-11T00:00
Z","PublishedDateTime":"2023-10-11T00:00Z"}}
 CVE-2023-38545 | alpine:v3.16    | {"NVD":{"CVSSv2":{"ExploitabilityScore":0,"ImpactScore":0,
"Score":0,"Vectors":""},"CVSSv3":{"ExploitabilityScore":1.6,"ImpactScore":5.9,"Score":7.5,"Vec
tors":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H"},"LastModifiedDateTime":"2023-10-11T00:00
Z","PublishedDateTime":"2023-10-11T00:00Z"}}
 CVE-2023-38545 | alpine:v3.18    | {"NVD":{"CVSSv2":{"ExploitabilityScore":0,"ImpactScore":0,
"Score":0,"Vectors":""},"CVSSv3":{"ExploitabilityScore":1.6,"ImpactScore":5.9,"Score":7.5,"Vec
tors":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H"},"LastModifiedDateTime":"2023-10-11T00:00
Z","PublishedDateTime":"2023-10-11T00:00Z"}}
 CVE-2023-38545 | alpine:edge     | {"NVD":{"CVSSv2":{"ExploitabilityScore":0,"ImpactScore":0,
"Score":0,"Vectors":""},"CVSSv3":{"ExploitabilityScore":1.6,"ImpactScore":5.9,"Score":7.5,"Vec
tors":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H"},"LastModifiedDateTime":"2023-10-11T00:00
Z","PublishedDateTime":"2023-10-11T00:00Z"}}
 CVE-2023-38545 | ubuntu:16.04    | {"NVD":{"CVSSv2":{"ExploitabilityScore":0,"ImpactScore":0,
"Score":0,"Vectors":""},"CVSSv3":{"ExploitabilityScore":1.6,"ImpactScore":5.9,"Score":7.5,"Vec
tors":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H"},"LastModifiedDateTime":"2023-10-11T00:00
Z","PublishedDateTime":"2023-10-11T00:00Z"}}
 CVE-2023-38545 | ubuntu:14.04    | {"NVD":{"CVSSv2":{"ExploitabilityScore":0,"ImpactScore":0,
"Score":0,"Vectors":""},"CVSSv3":{"ExploitabilityScore":1.6,"ImpactScore":5.9,"Score":7.5,"Vec
tors":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H"},"LastModifiedDateTime":"2023-10-11T00:00
Z","PublishedDateTime":"2023-10-11T00:00Z"}}
 CVE-2023-38545 | ubuntu:23.04    | {"NVD":{"CVSSv2":{"ExploitabilityScore":0,"ImpactScore":0,
"Score":0,"Vectors":""},"CVSSv3":{"ExploitabilityScore":1.6,"ImpactScore":5.9,"Score":7.5,"Vec
tors":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H"},"LastModifiedDateTime":"2023-10-11T00:00
Z","PublishedDateTime":"2023-10-11T00:00Z"}}
 CVE-2023-38545 | ubuntu:18.04    | {"NVD":{"CVSSv2":{"ExploitabilityScore":0,"ImpactScore":0,
"Score":0,"Vectors":""},"CVSSv3":{"ExploitabilityScore":1.6,"ImpactScore":5.9,"Score":7.5,"Vec
tors":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H"},"LastModifiedDateTime":"2023-10-11T00:00
Z","PublishedDateTime":"2023-10-11T00:00Z"}}
 CVE-2023-38545 | ubuntu:22.04    | {"NVD":{"CVSSv2":{"ExploitabilityScore":0,"ImpactScore":0,
"Score":0,"Vectors":""},"CVSSv3":{"ExploitabilityScore":1.6,"ImpactScore":5.9,"Score":7.5,"Vec
tors":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H"},"LastModifiedDateTime":"2023-10-11T00:00
Z","PublishedDateTime":"2023-10-11T00:00Z"}}
 CVE-2023-38545 | ubuntu:20.04    | {"NVD":{"CVSSv2":{"ExploitabilityScore":0,"ImpactScore":0,
"Score":0,"Vectors":""},"CVSSv3":{"ExploitabilityScore":1.6,"ImpactScore":5.9,"Score":7.5,"Vec
tors":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H"},"LastModifiedDateTime":"2023-10-11T00:00
Z","PublishedDateTime":"2023-10-11T00:00Z"}}
(16 rows)

postgres=# select v.name, n.name, v.metadata from vulnerability v join namespace n on v.namespace_id = n.id where v.name = 'CVE-2023-38546';
      name      |      name       |

                         metadata

----------------+-----------------+-----------------------------------------------------------
----------------------------------------------------------------------------------------------
----------------------------------------------------------------------------------------------
----------------------------------------------------------------------------------------------
----------------------------------------------------------------------------------------------
----------------------------------------------------------------------------------------------
------------------------
 CVE-2023-38546 | debian:unstable | {"NVD":{"CVSSv2":{"ExploitabilityScore":0,"ImpactScore":0,
"Score":0,"Vectors":""},"CVSSv3":{"ExploitabilityScore":1.6,"ImpactScore":3.4,"Score":5,"Vecto
rs":"CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:L/A:L"},"LastModifiedDateTime":"2023-10-11T00:00Z"
,"PublishedDateTime":"2023-10-11T00:00Z"}}
 CVE-2023-38546 | debian:13       | {"NVD":{"CVSSv2":{"ExploitabilityScore":0,"ImpactScore":0,
"Score":0,"Vectors":""},"CVSSv3":{"ExploitabilityScore":1.6,"ImpactScore":3.4,"Score":5,"Vecto
rs":"CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:L/A:L"},"LastModifiedDateTime":"2023-10-11T00:00Z"
,"PublishedDateTime":"2023-10-11T00:00Z"}}
 CVE-2023-38546 | debian:10       | {"NVD":{"CVSSv2":{"ExploitabilityScore":0,"ImpactScore":0,
"Score":0,"Vectors":""},"CVSSv3":{"ExploitabilityScore":1.6,"ImpactScore":3.4,"Score":5,"Vecto
rs":"CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:L/A:L"},"LastModifiedDateTime":"2023-10-11T00:00Z"
,"PublishedDateTime":"2023-10-11T00:00Z"}}
 CVE-2023-38546 | debian:11       | {"NVD":{"CVSSv2":{"ExploitabilityScore":0,"ImpactScore":0,
"Score":0,"Vectors":""},"CVSSv3":{"ExploitabilityScore":1.6,"ImpactScore":3.4,"Score":5,"Vecto
rs":"CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:L/A:L"},"LastModifiedDateTime":"2023-10-11T00:00Z"
,"PublishedDateTime":"2023-10-11T00:00Z"}}
 CVE-2023-38546 | debian:12       | {"NVD":{"CVSSv2":{"ExploitabilityScore":0,"ImpactScore":0,
"Score":0,"Vectors":""},"CVSSv3":{"ExploitabilityScore":1.6,"ImpactScore":3.4,"Score":5,"Vecto
rs":"CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:L/A:L"},"LastModifiedDateTime":"2023-10-11T00:00Z"
,"PublishedDateTime":"2023-10-11T00:00Z"}}
 CVE-2023-38546 | alpine:v3.17    | {"NVD":{"CVSSv2":{"ExploitabilityScore":0,"ImpactScore":0,
"Score":0,"Vectors":""},"CVSSv3":{"ExploitabilityScore":1.6,"ImpactScore":3.4,"Score":5,"Vecto
rs":"CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:L/A:L"},"LastModifiedDateTime":"2023-10-11T00:00Z"
,"PublishedDateTime":"2023-10-11T00:00Z"}}
 CVE-2023-38546 | alpine:v3.15    | {"NVD":{"CVSSv2":{"ExploitabilityScore":0,"ImpactScore":0,
"Score":0,"Vectors":""},"CVSSv3":{"ExploitabilityScore":1.6,"ImpactScore":3.4,"Score":5,"Vecto
rs":"CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:L/A:L"},"LastModifiedDateTime":"2023-10-11T00:00Z"
,"PublishedDateTime":"2023-10-11T00:00Z"}}
 CVE-2023-38546 | alpine:v3.18    | {"NVD":{"CVSSv2":{"ExploitabilityScore":0,"ImpactScore":0,
"Score":0,"Vectors":""},"CVSSv3":{"ExploitabilityScore":1.6,"ImpactScore":3.4,"Score":5,"Vecto
rs":"CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:L/A:L"},"LastModifiedDateTime":"2023-10-11T00:00Z"
,"PublishedDateTime":"2023-10-11T00:00Z"}}
 CVE-2023-38546 | alpine:v3.16    | {"NVD":{"CVSSv2":{"ExploitabilityScore":0,"ImpactScore":0,
"Score":0,"Vectors":""},"CVSSv3":{"ExploitabilityScore":1.6,"ImpactScore":3.4,"Score":5,"Vecto
rs":"CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:L/A:L"},"LastModifiedDateTime":"2023-10-11T00:00Z"
,"PublishedDateTime":"2023-10-11T00:00Z"}}
 CVE-2023-38546 | alpine:edge     | {"NVD":{"CVSSv2":{"ExploitabilityScore":0,"ImpactScore":0,
"Score":0,"Vectors":""},"CVSSv3":{"ExploitabilityScore":1.6,"ImpactScore":3.4,"Score":5,"Vecto
rs":"CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:L/A:L"},"LastModifiedDateTime":"2023-10-11T00:00Z"
,"PublishedDateTime":"2023-10-11T00:00Z"}}
 CVE-2023-38546 | centos:6        | {"NVD":{"CVSSv2":{"ExploitabilityScore":0,"ImpactScore":0,
"Score":0,"Vectors":""},"CVSSv3":{"ExploitabilityScore":1.6,"ImpactScore":3.4,"Score":5,"Vecto
rs":"CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:L/A:L"},"LastModifiedDateTime":"","PublishedDateTi
me":"2023-10-11T00:00:00Z"},"Red Hat":{"CVSSv2":{"ExploitabilityScore":0,"ImpactScore":0,"Scor
e":0,"Vectors":""},"CVSSv3":{"ExploitabilityScore":1.6,"ImpactScore":3.4,"Score":5,"Vectors":"
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:L/A:L"},"LastModifiedDateTime":"","PublishedDateTime":"
2023-10-11T00:00:00Z"}}
 CVE-2023-38546 | centos:8        | {"NVD":{"CVSSv2":{"ExploitabilityScore":0,"ImpactScore":0,
"Score":0,"Vectors":""},"CVSSv3":{"ExploitabilityScore":1.6,"ImpactScore":3.4,"Score":5,"Vecto
rs":"CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:L/A:L"},"LastModifiedDateTime":"","PublishedDateTi
me":"2023-10-11T00:00:00Z"},"Red Hat":{"CVSSv2":{"ExploitabilityScore":0,"ImpactScore":0,"Scor
e":0,"Vectors":""},"CVSSv3":{"ExploitabilityScore":1.6,"ImpactScore":3.4,"Score":5,"Vectors":"
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:L/A:L"},"LastModifiedDateTime":"","PublishedDateTime":"
2023-10-11T00:00:00Z"}}
 CVE-2023-38546 | centos:7        | {"NVD":{"CVSSv2":{"ExploitabilityScore":0,"ImpactScore":0,
"Score":0,"Vectors":""},"CVSSv3":{"ExploitabilityScore":1.6,"ImpactScore":3.4,"Score":5,"Vecto
rs":"CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:L/A:L"},"LastModifiedDateTime":"","PublishedDateTi
me":"2023-10-11T00:00:00Z"},"Red Hat":{"CVSSv2":{"ExploitabilityScore":0,"ImpactScore":0,"Scor
e":0,"Vectors":""},"CVSSv3":{"ExploitabilityScore":1.6,"ImpactScore":3.4,"Score":5,"Vectors":"
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:L/A:L"},"LastModifiedDateTime":"","PublishedDateTime":"
2023-10-11T00:00:00Z"}}
 CVE-2023-38546 | ubuntu:16.04    | {"NVD":{"CVSSv2":{"ExploitabilityScore":0,"ImpactScore":0,
"Score":0,"Vectors":""},"CVSSv3":{"ExploitabilityScore":1.6,"ImpactScore":3.4,"Score":5,"Vecto
rs":"CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:L/A:L"},"LastModifiedDateTime":"2023-10-11T00:00Z"
,"PublishedDateTime":"2023-10-11T00:00Z"}}
 CVE-2023-38546 | ubuntu:14.04    | {"NVD":{"CVSSv2":{"ExploitabilityScore":0,"ImpactScore":0,
"Score":0,"Vectors":""},"CVSSv3":{"ExploitabilityScore":1.6,"ImpactScore":3.4,"Score":5,"Vecto
rs":"CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:L/A:L"},"LastModifiedDateTime":"2023-10-11T00:00Z"
,"PublishedDateTime":"2023-10-11T00:00Z"}}
 CVE-2023-38546 | ubuntu:23.04    | {"NVD":{"CVSSv2":{"ExploitabilityScore":0,"ImpactScore":0,
"Score":0,"Vectors":""},"CVSSv3":{"ExploitabilityScore":1.6,"ImpactScore":3.4,"Score":5,"Vecto
rs":"CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:L/A:L"},"LastModifiedDateTime":"2023-10-11T00:00Z"
,"PublishedDateTime":"2023-10-11T00:00Z"}}
 CVE-2023-38546 | ubuntu:18.04    | {"NVD":{"CVSSv2":{"ExploitabilityScore":0,"ImpactScore":0,
"Score":0,"Vectors":""},"CVSSv3":{"ExploitabilityScore":1.6,"ImpactScore":3.4,"Score":5,"Vecto
rs":"CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:L/A:L"},"LastModifiedDateTime":"2023-10-11T00:00Z"
,"PublishedDateTime":"2023-10-11T00:00Z"}}
 CVE-2023-38546 | ubuntu:20.04    | {"NVD":{"CVSSv2":{"ExploitabilityScore":0,"ImpactScore":0,
"Score":0,"Vectors":""},"CVSSv3":{"ExploitabilityScore":1.6,"ImpactScore":3.4,"Score":5,"Vecto
rs":"CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:L/A:L"},"LastModifiedDateTime":"2023-10-11T00:00Z"
,"PublishedDateTime":"2023-10-11T00:00Z"}}
 CVE-2023-38546 | ubuntu:22.04    | {"NVD":{"CVSSv2":{"ExploitabilityScore":0,"ImpactScore":0,
"Score":0,"Vectors":""},"CVSSv3":{"ExploitabilityScore":1.6,"ImpactScore":3.4,"Score":5,"Vecto
rs":"CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:L/A:L"},"LastModifiedDateTime":"2023-10-11T00:00Z"
,"PublishedDateTime":"2023-10-11T00:00Z"}}
(19 rows)


setuphook: Quote path for updateSourceDateEpoch

Not all sources unpack without spaces.
Description of changes

Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
24.05 Release Notes (or backporting 23.05 and 23.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

Change looks good. Please target staging

Done

ofborg failure unrelated

Updated to fix commit message.


fix: apply prettier

all was good except for chai-dom-equals that needed a // prettier-ignore for one function (but only on Firefox and Safari)... thank god we have tests covering that :)


[QPG610x] Advertising bug fix and device name changes

Problem

Advertising was broken by previous change
Device name was being advertised passively against spec recommendations

Change overview
Buffer changes to restore the advertising
Move device name advertising to scan response
Testing

Tested on top of test_event_6 branch by running MA 1.10 testcase

@mrjerryjohns @saurabhst @andy31415 @Damian-Nordic @jelderton @jepenven-silabs @jmartinez-silabs ?


Curious about ffmpeg hardware acceleration with this image

I'm curious about the support for ffmpeg's hardware acceleration.
Since most Synology devices are Intel based, has the support for Quicksync been tested?

I use  hwaccel_args: -hwaccel vaapi -hwaccel_device /dev/dri/renderD128 -hwaccel_output_format yuv420p
which seems reduce the cpu utilisation of my most high-res camera from 23% to 17% even though the qsv method should be technically superior.

@jmtatsch on which arch / device?

@dotWee 920+ / Celeron J4125
but someone doing more scientific tests than me just looking at top would be really appreciated :)
no idea about simultaneous access

Works absolutely flawless, minimal CPU usage while transcoding & detecting 2x 2K cameras.
After testing together with Jellyfin transcoding no issues appeared. Seems like Quicksync can handle multiple jobs.
Thank you for the easy implementation, keep up the great work! 🙏🏻

I use  hwaccel_args: -hwaccel vaapi -hwaccel_device /dev/dri/renderD128 -hwaccel_output_format yuv420p which seems reduce the cpu utilisation of my most high-res camera from 23% to 17% even though the qsv method should be technically superior.

Thank you! This made a world of difference for me on my 720+

Been trying to use a combination of hwaccel parameters for my (old) DS916+
According to Intel, the Pentium N3710 supports quicksync
But with or without the environment variable, it won't enable any acceleration
With  hwaccel_args: qsv -qsv_device /dev/dri/renderD128 in the config, I get a bunch of errors
2023-07-11 20:31:55.546014945  (Kernel 4.16 or newer is required for i915 PMU support.)
[...]
2023-07-11 20:33:19.756992731  [2023-07-11 20:33:19] ffmpeg.camera-abri.detect      ERROR   : [AVHWDeviceContext @ 0x7fb452d1e580] libva: /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so init failed
2023-07-11 20:33:19.757509425  [2023-07-11 20:33:19] ffmpeg.camera-abri.detect      ERROR   : [AVHWDeviceContext @ 0x7fb452d1e580] Failed to initialise VAAPI connection: 1 (operation failed).
2023-07-11 20:33:19.757937469  [2023-07-11 20:33:19] ffmpeg.camera-abri.detect      ERROR   : Device creation failed: -5.
2023-07-11 20:33:19.758406388  [2023-07-11 20:33:19] ffmpeg.camera-abri.detect      ERROR   : Failed to set value '/dev/dri/renderD128' for option 'qsv_device': Input/output error
2023-07-11 20:33:19.758936283  [2023-07-11 20:33:19] ffmpeg.camera-abri.detect      ERROR   : Error parsing global options: Input/output error```

I also tried various config from the docs, and the posts above, but no luck. I tried:
- hwaccel_args: preset-intel-qsv-h264
- hwaccel_args: preset-intel-qsv-h265
- hwaccel_args: preset-vaapi
- hwaccel_args: -hwaccel vaapi -hwaccel_device /dev/dri/renderD128 -hwaccel_output_format yuv420p

In the best case (preset-vaapi), I get no error, but I get no acceleration either

I'm not sure if I'm mis-using the options, or my CPU is just tool old to accelerate frigate

Even through your model supports Intel's quicksync,  I'd recommend using VAAPI over quicksync. Some models have issues with the Quicksync implementation, as noted in the official documentation:

VAAPI supports automatic profile selection so it will work automatically with both H.264 and H.265 streams. VAAPI is recommended for all generations of Intel-based CPUs if QSV does not work.

NOTICE: With some of the processors, like the J4125, the default driver iHD doesn't seem to work correctly for hardware acceleration. You may need to change the driver to i965 by adding the following environment variable LIBVA_DRIVER_NAME=i965 to your docker-compose file or in the frigate.yml for HA OS users.

There are some tweaks you could try to debug your issues (like docker exec frigate bash'ing into the container and using ffmpeg's hwa info; checking the kernel log; chmod'ing the /dev/dri/renderD128 device)
If you could share your type of video streams (mjpeg, rtsp or other) and more details regarding your frigate configuration and container setup would be helpful.

Sure.
Camera1 is a Reolink RLC-520A, using HTTP stream
Camera2 is a Tapo C200, using RTSP
Frigate config:
mqtt:
  enabled: True
  host: mosquitto-server.mydomain
  port: 1883
  topic_prefix: frigate
  client_id: frigate
  user: 'mqtt-user'
  password: 'mqtt_pawword'
  stats_interval: 60

detectors:
  coral:
    type: edgetpu
    device: usb

#detectors:
#  ov:
#    type: openvino
#    device: AUTO
#    model:
#      path: /openvino-model/ssdlite_mobilenet_v2.xml

#model:
#  width: 300
#  height: 300
#  input_tensor: nhwc
#  input_pixel_format: bgr
#  labelmap_path: /openvino-model/coco_91cl_bkgr.txt

ffmpeg:
  global_args: -hide_banner -loglevel warning -threads 2
#  hwaccel_args: qsv -qsv_device /dev/dri/renderD128
#  hwaccel_args: preset-vaapi
  hwaccel_args: []
#  hwaccel_args: -preset-intel-qsv-h264 -hwaccel_device /dev/dri/renderD128 -hwaccel_output_format yuv420p
  input_args: preset-rtsp-generic
  output_args:
    detect: -threads 2 -f rawvideo -pix_fmt yuv420p
    record: preset-record-generic
    rtmp: preset-rtmp-generic

birdseye:
  enabled: True
  mode: continuous

go2rtc:
  streams:
    camera1:
      - http://camera1.mydomain/flv?port=1935&app=bcs&stream=channel0_main.bcs&user=frigate&password=password
      - "ffmpeg:reolink#audio=opus"
    camera1_sub:
      - http://camera1.mydomain/flv?port=1935&app=bcs&stream=channel0_ext.bcs&user=frigate&password=password
    camera2:
      - 'rtsp://frigate:password@camera2.mydomain:554/stream1'
    camera2_sub:
      - 'rtsp://frigate:password@camera2.mydomain:554/stream2'

cameras:
  camera1:
    ffmpeg:
      inputs:
        - path: rtsp://<IP_ADDRESS>:8554/camera1?video=copy&audio=aac
          input_args: preset-rtsp-restream
          roles:
            - record
        - path: rtsp://<IP_ADDRESS>:8554/camera1_sub?video=copy
          input_args: preset-rtsp-restream
          roles:
            - detect
    detect:
      width: 896
      height: 672
    record:
      enabled: True
      events:
        retain:
          default: 7
          mode: active_objects
    birdseye:
      mode: motion
  camera2:
    ffmpeg:
      inputs:
        - path: rtsp://<IP_ADDRESS>:8554/camera2?video=copy&audio=aac
          input_args: preset-rtsp-restream
          roles:
            - record
        - path: rtsp://<IP_ADDRESS>:8554/camera2_sub?video=copy
          input_args: preset-rtsp-restream
          roles:
            - detect
    detect:
      width: 640
      height: 360
    record:
      enabled: True
      events:
        retain:
          default: 7
          mode: active_objects
    birdseye:
      mode: motion

I tried a basic ffmpeg of a MP4 file to another mp4 file, using  -hwaccel auto.  Log is bit long but here goes
To me, it looks like there's no hardware encoder found
root@5138e1369398:/opt/frigate# ffmpeg -hwaccel auto -i /media/frigate/recordings/VID_20180807_123441_1.mp4 /media/frigate/recordings/test.mp4
ffmpeg version n5.1-2-g915ef932a3-20220731 Copyright (c) 2000-2022 the FFmpeg developers
  built with gcc 12.1.0 (crosstool-NG <IP_ADDRESS>_3defb7b)
  configuration: --prefix=/ffbuild/prefix --pkg-config-flags=--static --pkg-config=pkg-config --cross-prefix=x86_64-ffbuild-linux-gnu- --arch=x86_64 --target-os=linux --enable-gpl --enable-version3 --disable-debug --enable-iconv --enable-libxml2 --enable-zlib --enable-libfreetype --enable-libfribidi --enable-gmp --enable-lzma --enable-fontconfig --enable-libvorbis --enable-opencl --enable-libpulse --enable-libvmaf --enable-libxcb --enable-xlib --enable-amf --enable-libaom --enable-libaribb24 --enable-avisynth --enable-libdav1d --enable-libdavs2 --disable-libfdk-aac --enable-ffnvcodec --enable-cuda-llvm --enable-frei0r --enable-libgme --enable-libass --enable-libbluray --enable-libjxl --enable-libmp3lame --enable-libopus --enable-mbedtls --enable-librist --enable-libtheora --enable-libvpx --enable-libwebp --enable-lv2 --enable-libmfx --enable-libopencore-amrnb --enable-libopencore-amrwb --enable-libopenh264 --enable-libopenjpeg --enable-libopenmpt --enable-librav1e --enable-librubberband --disable-schannel --enable-sdl2 --enable-libsoxr --enable-libsrt --enable-libsvtav1 --enable-libtwolame --enable-libuavs3d --enable-libdrm --enable-vaapi --enable-libvidstab --enable-vulkan --enable-libshaderc --enable-libplacebo --enable-libx264 --enable-libx265 --enable-libxavs2 --enable-libxvid --enable-libzimg --enable-libzvbi --extra-cflags=-DLIBTWOLAME_STATIC --extra-cxxflags= --extra-ldflags=-pthread --extra-ldexeflags=-pie --extra-libs='-ldl -lgomp' --extra-version=20220731
  libavutil      57. 28.100 / 57. 28.100
  libavcodec     59. 37.100 / 59. 37.100
  libavformat    59. 27.100 / 59. 27.100
  libavdevice    59.  7.100 / 59.  7.100
  libavfilter     8. 44.100 /  8. 44.100
  libswscale      6.  7.100 /  6.  7.100
  libswresample   4.  7.100 /  4.  7.100
  libpostproc    56.  6.100 / 56.  6.100
Input #0, mov,mp4,m4a,3gp,3g2,mj2, from '/media/frigate/recordings/VID_20180807_123441_1.mp4':
  Metadata:
    major_brand     : mp42
    minor_version   : 0
    compatible_brands: mp42mp41
    creation_time   : 2018-10-30T09:26:23.000000Z
  Duration: 00:00:17.96, start: 0.000000, bitrate: 4279 kb/s
  Stream #0:0[0x1](eng): Video: h264 (Main) (avc1 / 0x31637661), yuv420p(tv, bt709, progressive), 1280x720, 3973 kb/s, 25 fps, 25 tbr, 25k tbn (default)
    Metadata:
      creation_time   : 2018-10-30T09:26:24.000000Z
      handler_name    : ?Mainconcept Video Media Handler
      vendor_id       : [0][0][0][0]
      encoder         : AVC Coding
  Stream #0:1[0x2](eng): Audio: aac (LC) (mp4a / 0x6134706D), 48000 Hz, stereo, fltp, 317 kb/s (default)
    Metadata:
      creation_time   : 2018-10-30T09:26:24.000000Z
      handler_name    : #Mainconcept MP4 Sound Media Handler
      vendor_id       : [0][0][0][0]
[AVHWDeviceContext @ 0x7f590dc38440] Cannot load libcuda.so.1
[AVHWDeviceContext @ 0x7f590dc38440] Could not dynamically load CUDA
Device creation failed: -1.
[AVHWDeviceContext @ 0x7f590dc20ac0] libva: /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so init failed
[AVHWDeviceContext @ 0x7f590dc20ac0] Failed to initialise VAAPI connection: 1 (operation failed).
Device creation failed: -5.
[h264 @ 0x7f590dc22f40] Auto hwaccel disabled: no device found.
Stream mapping:
  Stream #0:0 -> #0:0 (h264 (native) -> h264 (libx264))
  Stream #0:1 -> #0:1 (aac (native) -> aac (native))
Press [q] to stop, [?] for help
[libx264 @ 0x7f590db4ce00] using cpu capabilities: MMX2 SSE2Fast SSSE3 SSE4.2
[libx264 @ 0x7f590db4ce00] profile High, level 3.1, 4:2:0, 8-bit
[libx264 @ 0x7f590db4ce00] 264 - core 164 - H.264/MPEG-4 AVC codec - Copyleft 2003-2022 - http://www.videolan.org/x264.html - options: cabac=1 ref=3 deblock=1:0:0 analyse=0x3:0x113 me=hex subme=7 psy=1 psy_rd=1.00:0.00 mixed_ref=1 me_range=16 chroma_me=1 trellis=1 8x8dct=1 cqm=0 deadzone=21,11 fast_pskip=1 chroma_qp_offset=-2 threads=6 lookahead_threads=1 sliced_threads=0 nr=0 decimate=1 interlaced=0 bluray_compat=0 constrained_intra=0 bframes=3 b_pyramid=2 b_adapt=1 b_bias=0 direct=1 weightb=1 open_gop=0 weightp=2 keyint=250 keyint_min=25 scenecut=40 intra_refresh=0 rc_lookahead=40 rc=crf mbtree=1 crf=23.0 qcomp=0.60 qpmin=0 qpmax=69 qpstep=4 ip_ratio=1.40 aq=1:1.00
Output #0, mp4, to '/media/frigate/recordings/test.mp4':
  Metadata:
    major_brand     : mp42
    minor_version   : 0
    compatible_brands: mp42mp41
    encoder         : Lavf59.27.100
  Stream #0:0(eng): Video: h264 (avc1 / 0x31637661), yuv420p(tv, bt709, progressive), 1280x720, q=2-31, 25 fps, 12800 tbn (default)
    Metadata:
      creation_time   : 2018-10-30T09:26:24.000000Z
      handler_name    : ?Mainconcept Video Media Handler
      vendor_id       : [0][0][0][0]
      encoder         : Lavc59.37.100 libx264
    Side data:
      cpb: bitrate max/min/avg: 0/0/0 buffer size: 0 vbv_delay: N/A
  Stream #0:1(eng): Audio: aac (LC) (mp4a / 0x6134706D), 48000 Hz, stereo, fltp, 128 kb/s (default)
    Metadata:
      creation_time   : 2018-10-30T09:26:24.000000Z
      handler_name    : #Mainconcept MP4 Sound Media Handler
      vendor_id       : [0][0][0][0]
      encoder         : Lavc59.37.100 aac
frame=  447 fps=5.2 q=-1.0 Lsize=   17971kB time=00:00:17.89 bitrate=8225.0kbits/s speed=0.21x
video:17675kB audio:282kB subtitle:0kB other streams:0kB global headers:0kB muxing overhead: 0.080720%
[libx264 @ 0x7f590db4ce00] frame I:11    Avg QP:23.86  size: 50960
[libx264 @ 0x7f590db4ce00] frame P:158   Avg QP:27.12  size: 49302
[libx264 @ 0x7f590db4ce00] frame B:278   Avg QP:28.42  size: 35064
[libx264 @ 0x7f590db4ce00] consecutive B-frames: 11.0% 13.9% 13.4% 61.7%
[libx264 @ 0x7f590db4ce00] mb I  I16..4: 10.3% 56.3% 33.3%
[libx264 @ 0x7f590db4ce00] mb P  I16..4:  8.2% 43.3% 19.4%  P16..4: 18.2%  7.6%  2.1%  0.0%  0.0%    skip: 1.2%
[libx264 @ 0x7f590db4ce00] mb B  I16..4:  4.5% 13.9% 10.6%  B16..8: 37.8% 15.2%  3.2%  direct: 7.1%  skip: 7.7%  L0:62.2% L1:28.2% BI: 9.6%
[libx264 @ 0x7f590db4ce00] 8x8 transform intra:55.6% inter:37.2%
[libx264 @ 0x7f590db4ce00] coded y,uvDC,uvAC intra: 72.5% 33.0% 2.3% inter: 52.2% 22.1% 0.1%
[libx264 @ 0x7f590db4ce00] i16 v,h,dc,p:  9% 36%  8% 47%
[libx264 @ 0x7f590db4ce00] i8 v,h,dc,ddl,ddr,vr,hd,vl,hu: 21% 27% 16%  4%  5%  5%  7%  5%  8%
[libx264 @ 0x7f590db4ce00] i4 v,h,dc,ddl,ddr,vr,hd,vl,hu: 19% 23% 18%  7%  7%  6%  8%  6%  7%
[libx264 @ 0x7f590db4ce00] i8c dc,h,v,p: 55% 23% 16%  6%
[libx264 @ 0x7f590db4ce00] Weighted P-Frames: Y:19.0% UV:12.7%
[libx264 @ 0x7f590db4ce00] ref P L0: 64.8% 16.8% 12.5%  5.1%  0.8%
[libx264 @ 0x7f590db4ce00] ref B L0: 88.7%  9.7%  1.7%
[libx264 @ 0x7f590db4ce00] ref B L1: 97.4%  2.6%
[libx264 @ 0x7f590db4ce00] kb/s:8097.57
[aac @ 0x7f590db4b000] Qavg: 1263.382

Checked dmesg, and the only thing suspicious I see is below
2023-07-12T17:14:22,902963+02:00 intel_gpu_top[19528]: segfault at 78 ip 00007f6ae7177464 sp 00007ffdc6695f30 error 4 in intel_gpu_top[7f6ae7174000+a000]

I have a few of these in dmesg. It looks related to GPU, but have no idea why it's doing that. The docker container was created with the LIBVA_DRIVER_NAME=i965 environment variable
Here is content of /dev/dri

On the synology host

doudou@Reblochon:~$ ls -la /dev/dri/
total 0
drwxr-xr-x  2 root root             100 Jul 11 07:59 .
drwxr-xr-x 15 root root           14680 Jul 11 08:08 ..
crw-------  1 root root        226,   0 Jul 11 07:59 card0
crw-------  1 root root        226,  64 Jul 11 07:59 controlD64
crw-rw----  1 root videodriver 226, 128 Jul 11 07:59 renderD128

Inside the frigate container

root@5138e1369398:/opt/frigate# ls -la /dev/dri/
total 0
drwxr-xr-x  2 root root      100 Jul 12 17:16 .
drwxr-xr-x 11 root root    14560 Jul 12 17:16 ..
crw-------  1 root root 226,   0 Jul 12 17:16 card0
crw-------  1 root root 226,  64 Jul 12 17:16 controlD64
crw-rw----  1 root  937 226, 128 Jul 12 17:16 renderD128

Hey, a chmod a+rw on /dev/dri/render128 seemed to wake it up
The same ffmpeg command now detects vaapi
root@8ff317191fd4:/opt/frigate# ffmpeg -hwaccel auto -i /media/frigate/recordings/VID_20180807_123441_1.mp4 /media/frigate/recordings/test.mp4
ffmpeg version n5.1-2-g915ef932a3-20220731 Copyright (c) 2000-2022 the FFmpeg developers
  built with gcc 12.1.0 (crosstool-NG <IP_ADDRESS>_3defb7b)
  configuration: --prefix=/ffbuild/prefix --pkg-config-flags=--static --pkg-config=pkg-config --cross-prefix=x86_64-ffbuild-linux-gnu- --arch=x86_64 --target-os=linux --enable-gpl --enable-version3 --disable-debug --enable-iconv --enable-libxml2 --enable-zlib --enable-libfreetype --enable-libfribidi --enable-gmp --enable-lzma --enable-fontconfig --enable-libvorbis --enable-opencl --enable-libpulse --enable-libvmaf --enable-libxcb --enable-xlib --enable-amf --enable-libaom --enable-libaribb24 --enable-avisynth --enable-libdav1d --enable-libdavs2 --disable-libfdk-aac --enable-ffnvcodec --enable-cuda-llvm --enable-frei0r --enable-libgme --enable-libass --enable-libbluray --enable-libjxl --enable-libmp3lame --enable-libopus --enable-mbedtls --enable-librist --enable-libtheora --enable-libvpx --enable-libwebp --enable-lv2 --enable-libmfx --enable-libopencore-amrnb --enable-libopencore-amrwb --enable-libopenh264 --enable-libopenjpeg --enable-libopenmpt --enable-librav1e --enable-librubberband --disable-schannel --enable-sdl2 --enable-libsoxr --enable-libsrt --enable-libsvtav1 --enable-libtwolame --enable-libuavs3d --enable-libdrm --enable-vaapi --enable-libvidstab --enable-vulkan --enable-libshaderc --enable-libplacebo --enable-libx264 --enable-libx265 --enable-libxavs2 --enable-libxvid --enable-libzimg --enable-libzvbi --extra-cflags=-DLIBTWOLAME_STATIC --extra-cxxflags= --extra-ldflags=-pthread --extra-ldexeflags=-pie --extra-libs='-ldl -lgomp' --extra-version=20220731
  libavutil      57. 28.100 / 57. 28.100
  libavcodec     59. 37.100 / 59. 37.100
  libavformat    59. 27.100 / 59. 27.100
  libavdevice    59.  7.100 / 59.  7.100
  libavfilter     8. 44.100 /  8. 44.100
  libswscale      6.  7.100 /  6.  7.100
  libswresample   4.  7.100 /  4.  7.100
  libpostproc    56.  6.100 / 56.  6.100
Input #0, mov,mp4,m4a,3gp,3g2,mj2, from '/media/frigate/recordings/VID_20180807_123441_1.mp4':
  Metadata:
    major_brand     : mp42
    minor_version   : 0
    compatible_brands: mp42mp41
    creation_time   : 2018-10-30T09:26:23.000000Z
  Duration: 00:00:17.96, start: 0.000000, bitrate: 4279 kb/s
  Stream #0:0[0x1](eng): Video: h264 (Main) (avc1 / 0x31637661), yuv420p(tv, bt709, progressive), 1280x720, 3973 kb/s, 25 fps, 25 tbr, 25k tbn (default)
    Metadata:
      creation_time   : 2018-10-30T09:26:24.000000Z
      handler_name    : ?Mainconcept Video Media Handler
      vendor_id       : [0][0][0][0]
      encoder         : AVC Coding
  Stream #0:1[0x2](eng): Audio: aac (LC) (mp4a / 0x6134706D), 48000 Hz, stereo, fltp, 317 kb/s (default)
    Metadata:
      creation_time   : 2018-10-30T09:26:24.000000Z
      handler_name    : #Mainconcept MP4 Sound Media Handler
      vendor_id       : [0][0][0][0]
[AVHWDeviceContext @ 0x7f24575ef440] Cannot load libcuda.so.1
[AVHWDeviceContext @ 0x7f24575ef440] Could not dynamically load CUDA
Device creation failed: -1.
[h264 @ 0x7f24575d9f40] Using auto hwaccel type vaapi with new default device.
Stream mapping:
  Stream #0:0 -> #0:0 (h264 (native) -> h264 (libx264))
  Stream #0:1 -> #0:1 (aac (native) -> aac (native))
Press [q] to stop, [?] for help
[libx264 @ 0x7f2457503e00] using cpu capabilities: MMX2 SSE2Fast SSSE3 SSE4.2
[libx264 @ 0x7f2457503e00] profile High, level 3.1, 4:2:0, 8-bit
[libx264 @ 0x7f2457503e00] 264 - core 164 - H.264/MPEG-4 AVC codec - Copyleft 2003-2022 - http://www.videolan.org/x264.html - options: cabac=1 ref=3 deblock=1:0:0 analyse=0x3:0x113 me=hex subme=7 psy=1 psy_rd=1.00:0.00 mixed_ref=1 me_range=16 chroma_me=1 trellis=1 8x8dct=1 cqm=0 deadzone=21,11 fast_pskip=1 chroma_qp_offset=-2 threads=6 lookahead_threads=1 sliced_threads=0 nr=0 decimate=1 interlaced=0 bluray_compat=0 constrained_intra=0 bframes=3 b_pyramid=2 b_adapt=1 b_bias=0 direct=1 weightb=1 open_gop=0 weightp=2 keyint=250 keyint_min=25 scenecut=40 intra_refresh=0 rc_lookahead=40 rc=crf mbtree=1 crf=23.0 qcomp=0.60 qpmin=0 qpmax=69 qpstep=4 ip_ratio=1.40 aq=1:1.00
Output #0, mp4, to '/media/frigate/recordings/test.mp4':
  Metadata:
    major_brand     : mp42
    minor_version   : 0
    compatible_brands: mp42mp41
    encoder         : Lavf59.27.100
  Stream #0:0(eng): Video: h264 (avc1 / 0x31637661), nv12(tv, bt709, progressive), 1280x720, q=2-31, 25 fps, 12800 tbn (default)
    Metadata:
      creation_time   : 2018-10-30T09:26:24.000000Z
      handler_name    : ?Mainconcept Video Media Handler
      vendor_id       : [0][0][0][0]
      encoder         : Lavc59.37.100 libx264
    Side data:
      cpb: bitrate max/min/avg: 0/0/0 buffer size: 0 vbv_delay: N/A
  Stream #0:1(eng): Audio: aac (LC) (mp4a / 0x6134706D), 48000 Hz, stereo, fltp, 128 kb/s (default)
    Metadata:
      creation_time   : 2018-10-30T09:26:24.000000Z
      handler_name    : #Mainconcept MP4 Sound Media Handler
      vendor_id       : [0][0][0][0]
      encoder         : Lavc59.37.100 aac
frame=  447 fps=5.8 q=-1.0 Lsize=   17971kB time=00:00:17.89 bitrate=8225.0kbits/s speed=0.232x
video:17675kB audio:282kB subtitle:0kB other streams:0kB global headers:0kB muxing overhead: 0.080720%
[libx264 @ 0x7f2457503e00] frame I:11    Avg QP:23.86  size: 50960
[libx264 @ 0x7f2457503e00] frame P:158   Avg QP:27.12  size: 49302
[libx264 @ 0x7f2457503e00] frame B:278   Avg QP:28.42  size: 35064
[libx264 @ 0x7f2457503e00] consecutive B-frames: 11.0% 13.9% 13.4% 61.7%
[libx264 @ 0x7f2457503e00] mb I  I16..4: 10.3% 56.3% 33.3%
[libx264 @ 0x7f2457503e00] mb P  I16..4:  8.2% 43.3% 19.4%  P16..4: 18.2%  7.6%  2.1%  0.0%  0.0%    skip: 1.2%
[libx264 @ 0x7f2457503e00] mb B  I16..4:  4.5% 13.9% 10.6%  B16..8: 37.8% 15.2%  3.2%  direct: 7.1%  skip: 7.7%  L0:62.2% L1:28.2% BI: 9.6%
[libx264 @ 0x7f2457503e00] 8x8 transform intra:55.6% inter:37.2%
[libx264 @ 0x7f2457503e00] coded y,uvDC,uvAC intra: 72.5% 33.0% 2.3% inter: 52.2% 22.1% 0.1%
[libx264 @ 0x7f2457503e00] i16 v,h,dc,p:  9% 36%  8% 47%
[libx264 @ 0x7f2457503e00] i8 v,h,dc,ddl,ddr,vr,hd,vl,hu: 21% 27% 16%  4%  5%  5%  7%  5%  8%
[libx264 @ 0x7f2457503e00] i4 v,h,dc,ddl,ddr,vr,hd,vl,hu: 19% 23% 18%  7%  7%  6%  8%  6%  7%
[libx264 @ 0x7f2457503e00] i8c dc,h,v,p: 55% 23% 16%  6%
[libx264 @ 0x7f2457503e00] Weighted P-Frames: Y:19.0% UV:12.7%
[libx264 @ 0x7f2457503e00] ref P L0: 64.8% 16.8% 12.5%  5.1%  0.8%
[libx264 @ 0x7f2457503e00] ref B L0: 88.7%  9.7%  1.7%
[libx264 @ 0x7f2457503e00] ref B L1: 97.4%  2.6%
[libx264 @ 0x7f2457503e00] kb/s:8097.57
[aac @ 0x7f2457502000] Qavg: 1263.382

It does encode faster now. I guess that's the best I can hope for with this Intel N3710.
Thanks for the suggestion to chmod the device. Didn't think about that!

When trying to force qsv, I get a weird error
ffmpeg -hwaccel qsv -y -i /media/frigate/recordings/VID_20180807_123441_1.mp4 -s 3480x2160 -vcodec libx264 -acodec copy /media/frigate/recordings/test.h264.docker.mp4

[...]

[AVHWDeviceContext @ 0x7f762f0f8d00] libva: /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so init failed
[AVHWDeviceContext @ 0x7f762f0f8d00] Failed to initialise VAAPI connection: 1 (operation failed).

Why is it searching for /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so? Shouldn't it look for /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so
I do have the environment variable set correctly:
root@da2fd403435c:/opt/frigate# echo $LIBVA_DRIVER_NAME
i965

I'm also using a Reolink camera (different model tho) with a DS920+, which officially supported for quicksync but wasted many hour trying to get it to work. VAAPI working fine. Here are some notes from my docker-compose.yml could maybe help you out:
services:
  frigate:
    image: "ghcr.io/blakeblackshear/frigate:0.12.0"
    # either priviledged or with added cap; but cap-config aren't supported on DSM
    # https://docs.frigate.video/configuration/hardware_acceleration#intel-based-cpus
    privileged: true
    devices:
      - /dev/bus/usb:/dev/bus/usb # for the google coral
      - /dev/dri/renderD128 # for intel hwaccel
      - /dev/dri/card0 # :/dev/dri/card0
    environment:
      LIBVA_DRIVER_NAME: i965

Regarding the LIBVA_DRIVER_NAME, you could try setting it in frigate's config.yaml and see if it makes a difference:
environment_vars:
  LIBVA_DRIVER_NAME: i965

If you really want to look into Quicksync with Frigate on DSM, I'll recommend looking through Intel's QuickSync documentation: https://dgpu-docs.intel.com/technologies/media/index.html
And ffmpeg's QuickSync docs: https://trac.ffmpeg.org/wiki/Hardware/QuickSync
There's also the $ vainfo command tool, which should help you debugging VAAPI.
Make sure to share some findings if you get it to work!


A few DataFrame-related fixes

Fix backing memory calculation
Fix a potential memory leak if no data frames are available
Free DataFrame on drop to reduce the risk of a leak
Print error if no DataFrame is available
Pass exactly sized slices to callbacks
Fix a potential panic when passing a too big buffer to from_bytes

I think that's all, besides the cleanup :)

Looks good to me but raises a new code warning:
warning: variable does not need to be mutable
    --> esp-wifi\src\wifi\mod.rs:1097:24
     |
1097 |         while let Some(mut packet) = queue.dequeue() {
     |                        ----^^^^^^
     |                        |
     |                        help: remove this `mut`
     |
     = note: `#[warn(unused_mut)]` on by default


Scroll hover popup

Is there any way to scroll the hover popup without the mouse? I tried C-e & C-y, also  vim.lsp.util.scroll(false, 1).

No not currently.


Support IBM Upgrading for MQ V9.4 onwards

Create new roles to handle the new method for applying maintenance on windows and linux.
From IBM MQ 9.4.0, you apply maintenance to your IBM MQ installations on Windows and Linux by upgrading IBM MQ instead of having to keep the older fix pack files stored on the system

Declarative installation considerations for the new 9.4 maintenance process:

Removal of 'applyfixpack' role for 9.4+
Upgrade/downgrade as appropriate during main installation roles based on specified version
Version checking for existing installations and warnings for major downgrades


HTML Cache META attributes doesn't work

Even with the following in the HTML files, it is cached. I think, the service-worker.js is causing this issue.

Yup, SW overrides the network cache. You need to handle this in your applications Service Worker or remove the SW if you don't want to handle the client-side application caching manually.

@Garbee Is there a way I can exclude certain html files from the caching?

My HTML cache attributes still doesn't work any comments or update


Why do we need minUptime?

minUptime is introduced in a rewrite (76b58cd4cea869a2c427f4475c5d175d5fecbfc0).
What's the problem of calling _acceptOpen immediately rather than minUptime seconds later?

To avoid deadloop in case of logical bug?