State subscription via decorator

Provide means to hide RxJS details for the state subscription for those who favour more convention over configuration

@obedm503 so I ended up experimenting more and came pretty much to the same conclusion like you. There really isn't a nice way without overriding lifecycle methods. What I dislike with this is that you have a quite ugly path for TypeScript users as injected props and methods are not typesafe anymore.
Would you mind giving this decorator implementation a look and follow along these testcases for the usage?

cool! 2 things:

I would have used a  scoped variable instead of _stateSubscription pseudo private property to hold the subscription. the downside is that it's not testable if it's private
I don't know if this would help with the typing problem, but can't you return the target cast as different type?

type StoreConsumer<T> = {
  state: Store<T>
}

export function connectTo<T>(settings?: (store: Store<T>) => Observable<T>) {
  // ...
  return function (target: any) {
    // ...
    return (target as type extends StoreConsumer<T>);
  }
}

ps: didn't actually test if this compiles

thanks for the feedback.

I thought so as well, but then again as you stated testing becomes a lot harder. Not only that, there might also be a reason someone would like to unsubscribe earlier than unbind, for whatever reason. So hiding the subscription feels a bit dangerous.
well that would be possible but in that case you'd tie the decorator to a specific consumer, which doesn't scale well. I also thought about interfaces, but then again this doesn't feel very natural to the current Aurelia flow and besides that the optional flag you'd have to place would result in further issues.

Alright I think we're good enough here, I've added additionally the option to override the target property, so it should be fine to start with. We'll see whether more requests are coming. Closing this for now. Thanks for the help @obedm503


Adding 10.9.1 to the config.php found here.

Not sure, where exactly this config.php is used -- maybe it is just for reference. That is also good to keep it updated.
Also pushed the same (I hope) to https://gitea.owncloud.services/devops/product/pulls/239
Please review (both) carefully.

This PR doesn't look complete. At least beta channel should be changed accordingly. And may be production.
Also new tests with expectations that no updates are NOT available for 10.9.1 should be added
Regarding the daily channel - 10.8 should be updated to 10.9.1 and 10.9.1 to daily zip

Regarding the usage:
This repo doesn't affect the REAL update server. I use it to add new tests and check whether all the tests are passing locally with make test
and then I push the similar changes to gitea. Once the PR at gitea is merged the changes are immediately deployed to the real server
and then it's possible to test real server using this repo with make test-production

At least beta channel should be changed accordingly. And may be production.
Also new tests with expectations that no updates are NOT available for 10.9.1 should be added

@VicDeo Can you provide some hints, how production and beta should look like?
No idea, how production is different from stable
I'd like to update "everything" to 10.9.1 but how do we code "everything"?
Can we simply copy the same data structure that we have in stable also to beta and production?
We should probably move 10.8.0 to the EOL list at some time in future... When?

https://drone.owncloud.com/owncloud/owncloud-updater-server/56/2/2 3 test fail - they need looking at and adjusting, if the test expectations are now different.

[Thu Jan 20 16:36:14 2022] <IP_ADDRESS>:59464 Closing
    And Update to version "<IP_ADDRESS>" is available
    And URL to download is "https://download.owncloud.org/community/owncloud-daily-master.zip"
Expected url https://download.owncloud.org/community/owncloud-daily-master.zip does not equal https://download.owncloud.org/community/owncloud-10.9.1.zip (Exception)

When the version is returned as <IP_ADDRESS>, then it should also return daily-master.zip -- But I don't see, where that <IP_ADDRESS> is coming from. I cannot say, weather test expectations need to adapt, or my settings are incorrect, or both.

Note: I am no familiar with any of this - it is new to me. Please can someone with knowledge answer here, otherwise I would be reverse-engineering this whole thing to know exactly what is supposed to happen.

@jnweiger version 100 is coming from the update server. Thus daily build could be updated to the same version if the date is newer. It's a daily channel-specific thing
regarding the channels https://owncloud.com/news/owncloud-release-channels/
I used to update production channel separately after all other channels are updated. Sometimes even before the next oC release comes into RC state.
regarding this PR - you updated the channels but some expectations are still not documented in tests.

@phil-davis Do you know what needs to be done to bring the new expectations into the tests?

@phil-davis Do you know what needs to be done to bring the new expectations into the tests?

I can adjust the tests to make them pass. But by doing that, I will be assuming that the config changes in this PR are correct.
Someone needs to say that the config.php diff is correct:
https://github.com/owncloud/owncloud-updater-server/pull/17/files#diff-f55db4bc294bbb90108ccfcbdd11881f4707473ad9384b382e2a6b653e118471

Hehe, seems we are blocked here.
I'd suggest to unblock, we go forward and assume it is correct, unless somebody objects.
(We already have @VicDeo here -- without objections, that is probably the best expert we can get right now)

@jnweiger @VicDeo I made the tests pass, and added one for 10.9.*
Please review and see if this looks good now.

@jnweiger @VicDeo ping

@phil-davis well, I have no access to the owncloud mailbox where I used to read GH notifications so it's pretty useless to ping me :)
Another funny thing that I have no push access to this repo anymore.
Anyway, your recent fixes are looking good except the daily channel update flow.
For the daily channel 10.9.0 should be updated to 10.9.1 while everything else should be updated to the daily master build.
Feel free to apply this patch to achieve this:
From baec6b43754416ac370ad179ae7d4fd397efbf42 Mon Sep 17 00:00:00 2001
From: Viktar Dubiniuk<EMAIL_ADDRESS>Date: Fri, 18 Feb 2022 00:10:30 +0300
Subject: [PATCH] Minor fixes for daily channel

---
 config/config.php                             | 18 +++++++-------
 .../integration/features/update.daily.feature | 24 +++++++++++++++++--
 2 files changed, 31 insertions(+), 11 deletions(-)

diff --git a/config/config.php b/config/config.php
index 8e889f0..d6c7a4a 100644
--- a/config/config.php
+++ b/config/config.php
@@ -120,19 +120,19 @@ return [
        ],
        'daily' => [
                // 10.8 should be updated to 10.9.1 and not to daily master
-               // 10.9 should be updated to 10.9.1 as well
-               // 10.9.1 should be updated to daily master instead
-               '10.8' => [
-                       'latest' => '10.9.1',
-                       'web' => 'https://doc.owncloud.com/server/10.8/admin_manual/maintenance/upgrading/update.html',
-               ],
+               // 10.9.0 should be updated to 10.9.1 as well
+               // 10.9.* should be updated to daily master instead
                '10.9' => [
+                       'downloadUrl' => 'https://download.owncloud.org/community/owncloud-daily-master.zip',
+                       'web' => 'https://doc.owncloud.com/server/latest/admin_manual/maintenance/upgrading/update.html',
+               ],
+               '10.9.0' => [
                        'latest' => '10.9.1',
                        'web' => 'https://doc.owncloud.com/server/10.9/admin_manual/maintenance/upgrading/update.html',
                ],
-               '10.9.1' => [
-                       'downloadUrl' => 'https://download.owncloud.org/community/owncloud-daily-master.zip',
-                       'web' => 'https://doc.owncloud.com/server/latest/admin_manual/maintenance/upgrading/update.html',
+               '10.8' => [
+                       'latest' => '10.9.1',
+                       'web' => 'https://doc.owncloud.com/server/10.8/admin_manual/maintenance/upgrading/update.html',
                ],
        ],
        // to prevent individual channels from bloating all upgrade path common for all channels go below
diff --git a/tests/integration/features/update.daily.feature b/tests/integration/features/update.daily.feature
index ae517ba..f01422f 100644
--- a/tests/integration/features/update.daily.feature
+++ b/tests/integration/features/update.daily.feature
@@ -1,16 +1,36 @@
 Feature: Testing the update scenario of releases on the daily channel
 ##### Please always order by version number descending #####
   ##### Tests for 10.9 should go below #####
-  Scenario: Updating an outdated-dated ownCloud 10.9 daily
+  Scenario: Updating an outdated-dated ownCloud 10.9.100 daily
     Given There is a release with channel "daily"
     And The received version is "10.9.100"
     And the received build is "2021-03-19T18:44:30+00:00"
     When The request is sent
     Then The response is non-empty
     And Update to version "<IP_ADDRESS>" is available
+    And URL to download is "https://download.owncloud.org/community/owncloud-daily-master.zip"
+    And URL to documentation is "https://doc.owncloud.com/server/latest/admin_manual/maintenance/upgrading/update.html"
+
+  Scenario: Updating an outdated-dated ownCloud 10.9 daily
+    Given There is a release with channel "daily"
+    And The received version is "10.9.1"
+    And the received build is "2021-03-19T18:44:30+00:00"
+    When The request is sent
+    Then The response is non-empty
+    And Update to version "<IP_ADDRESS>" is available
+    And URL to download is "https://download.owncloud.org/community/owncloud-daily-master.zip"
+    And URL to documentation is "https://doc.owncloud.com/server/latest/admin_manual/maintenance/upgrading/update.html"
+
+  Scenario: Updating an outdated-dated ownCloud 10.9 daily
+    Given There is a release with channel "daily"
+    And The received version is "10.9.0"
+    And the received build is "2021-03-19T18:44:30+00:00"
+    When The request is sent
+    Then The response is non-empty
+    And Update to version "<IP_ADDRESS>" is available
     And URL to download is "https://download.owncloud.org/community/owncloud-10.9.1.zip"
     And URL to documentation is "https://doc.owncloud.com/server/10.9/admin_manual/maintenance/upgrading/update.html"
-
+
   ##### Tests for 10.8 should go below #####
   Scenario: Updating an outdated-dated ownCloud 10.8 daily
     Given There is a release with channel "daily"
--
2.34.1

And it's good to go after squashing the commits.
I'm unable to review the respective PR on Gitea so I've tried to run make test-production on this branch.
It seems to be already merged and have the same flaw:
Update candidate for daily master  instance is  10.9.1 which is pretty wrong.


Callback when reaches cero?

I have an "oferts" model in my app, you can set the time it's gonna be available and there is where the countdown plays.
the bottle_rocket is working like a charm, but Im facing a problem, how do I get the event when the countdown reaches cero?
I mean, my "oferts" model has a boolean attribute "active", I want when the countdown ends change the attribute "active" to false
I think the right way is using a callback, or there is another way?

bottle_rocket is not made to be used as a delayed job for models. It should be used to display a countdown on a html page. There is no callback function on the server side.
You could write a simple ruby script that checks the time in an endless loop and updates the model if that time is reached.

Thanks, when is it gonna be available? I tried to install it but it still shows an error when you try to start the server, are you planning to make a stable release soon?

Unfortunately this is on hold right now, and its not ready to be released.


feat(hmr): reload when HTML file is created/deleted

Description
When creating/deleting a HTML file, Vite now reloads the page if the page is opened. (e.g. when opening /foo.html and foo.html is created or deleted, a reload will happen)
This PR also merges the HMR handling when a file is created/deleted with the HMR handling when a file is modified.
Split from #16249

/ecosystem-ci run

/ecosystem-ci run nuxt


lib/options: refactor and rename (non-breaking)

lib/types: add nixvimTypes.freeformModule
We often have submodules in settings options, most of these should be freeform although many aren't.
lib/options: add rawOpts helpers
New helpers for making non-null options that support the raw type.
lib/options: move top-level helpers to nullableOpts
Most of the top-level option helpers were actually creating nullable options. Move them into their own scope.
lib/options: standardise raw-type support in defaultNullOpts
mkAttrsOf (etc) didn't inject maybeRaw everywhere they should. Also begin transitioning mkNullable and mkNullableWithRaw by introducing mkNullableNoRaw alias.
lib/options: merge mkNullOrStrLuaOr' (etc)
This is the only breaking change, although I don't think anyone ever used these.
Other
Do we still need mkCompositeOption? Should we make it freeform?

Do we still need mkCompositeOption? Should we make it freeform?

We should first look for all the occurences in the code base and then, if none of this use cases is legit, we should remove it.

Although your description is very clear, I would prefer if this set of changes is spread accross a few individual PRs.


backports.zoneinfo is only available for py<39

The current build thus can only be installed in py<39, not with Python 3.9 and 3.10
The comment is correct but was placed on the wrong line to have the right effect.

Checklist

[x] Used a personal fork of the feedstock to propose changes
[x] Bumped the build number (if the version is unchanged)
[x] Reset the build number to 0 (if the version changed)
[x] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[x] Ensured the license file is being packaged.

Hi! This is the friendly automated conda-forge-linting service.
I wanted to let you know that I linted all conda-recipes in your PR (recipe) and found some lint.
Here's what I've got...
For recipe:

noarch packages can't have selectors. If the selectors are necessary, please remove noarch: python.

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.


Restructuring and adding icons

Restructured into the standard grapesjs plugin template(ish).
Also added custom icons for column and row top level menu items.

Thanks. I'm currently busy with another project, but I will try to check this by the end of the week.

No rush, I am using based off my fork atm, but as all the clever stuff is yours I wanted to give you a pull req :)

I carried on with changes and have a few bits in prog, wasn't aware they would end up in the same PR tbh. Will tidy up later. Cheers.


fix nightly test

/test

https://github.com/pfnet/pytorch-pfn-extras/actions/runs/7484718932

Failure message: https://github.com/pfnet/pytorch-pfn-extras/actions/runs/7482314256/job/20365642158#step:5:21
_ ERROR collecting tests/pytorch_pfn_extras_tests/training_tests/extensions_tests/test_sharded_snapshot.py _
tests/pytorch_pfn_extras_tests/training_tests/extensions_tests/test_sharded_snapshot.py:88: in <module>
    fsdp.ShardedStateDictConfig(
E   TypeError: __init__() got an unexpected keyword argument 'use_dtensor'

Caused by this PR: https://github.com/pytorch/pytorch/pull/107533
The default value was False so shouldn't effect much


Verge block rejections

Currently there's 40% rejection rate for Verge blocks (briefly tested on our 30 TH production pool). I'm currently clueless as to why this happens. I suspect a problem due to Verge's hybrid PoW/PoS nature.
Another open source implementation does not suffer from this problem.
Tracking: https://github.com/vergecurrency/VERGE/issues/641

we aren't based on digibyte though. multi algo but still different

@justinvforvendetta Digibyte, was a typo. I'm solely talking about verge here. Sorry for the confusion.

well pos is completely disabled but ntime is still in the block header

@justinvforvendetta But if nTime is the only difference to a regular PoW coin why is node-stratum-pool jumping through so many hoops:

https://github.com/zone117x/node-stratum-pool/blob/f2c90d45822562aaa9e418c9069a70aaa2b88005/lib/blockTemplate.js#L113
https://github.com/zone117x/node-stratum-pool/blob/f2c90d45822562aaa9e418c9069a70aaa2b88005/lib/pool.js#L416
https://github.com/zone117x/node-stratum-pool/blob/0cd4fcbc0e0c5cf5f65ba767f32645f42b38d0ca/lib/transactions.js#L190

can you paste some specific errors? also, are you mining thru tor or clearnet? it's been a few years since I've ran a pool, but it should mine no differently than any other pow coin

Here's a rejection:

ThreadRPCServer method=submitblock
InvalidChainFound: invalid block=038462545a8fc302b1e3  height=1950681  trust=1950682  date=03/13/18 16:56:57
InvalidChainFound:  current best=00000000000005365e3f  height=1950680  trust=1950681  date=03/13/18 16:55:50
ERROR: SetBestChain() : SetBestChainInner failed
ERROR: AcceptBlock() : AddToBlockIndex failed
ERROR: ProcessBlock() : AcceptBlock FAILED

What's even more baffling is that the pool successfully submitted 5 blocks before the rejections started.

using clearnet or tor daemon?

@justinvforvendetta Sorry forgot to answer that:

On branch 4.0clearnet
Your branch is up-to-date with 'origin/4.0clearnet'.

@justinvforvendetta Do you suspect that it was just bad luck instead of a bug considering where the rejection happened?

ok yes I suspect bad luck because on occassion I check pools and haven't seen anything like that

Hmm, but 5 times in a row? Weird.

well since we are multi algo we do have checks, like one algo can't find more than x number of blocks in a row, difficulty retargeting etc..
to clarify, they were rejected, or orphaned?

@justinvforvendetta Rejected, please see the log snippet above.

@justinvforvendetta Any ideas on the rejections?

@oliverw why not reach out to another yiimp admin?

@justinvforvendetta Already did.

what did they say? since they aren't getting any rejections, maybe the configured something differently?

@oliverw I can spin up a Verge pool this weekend and see if we get similar results.

@Gadflyii Cool, please post your results.

@oliverw  What algo are you using? Where do I set the algo for XVG?

@Gadflyii The rejections happened with blake2s. You can set the algo directly below the cointype:
"coin": {
    "type": "XVG",
    "algorithm": "blake"
},

Cool, getting closer, now I get:
"[Verge] [Bitcoin Job Manager] Waiting for daemons to connect to peers ..."
Not sure why, IP is right, Daemon is up and synced, has lots of connections,

Verge needs: "hasLegacyDaemon": true in the pool config element.

like so?
"        "id": "Verge",
"enabled": true,
"coin": {
"type": "XVG",
"Algorithm": "lyra"
},
"hasLegacyDaemon": true,

Yes.

[2018-03-26 06:07:17.3123] [E] [Verge] System.NullReferenceException: Object reference not set to an instance of an object.
at MiningCore.Blockchain.Bitcoin.BitcoinJobManager`2.d__30.MoveNext() in C:\Users\gadfl\Desktop\miningcore-0.21\src\MiningCore\Blockchain\Bitcoin\BitcoinJobManager.cs:line 337

Master branch?

Yes, release 21

Investigating.

NP, Just want to help, I will be online for a few hours, I am on discord if you want to chat.

You want the full stack trace?

I will give this another shot with the new verge-codebase.


Short README.md

I’ll Create Windows 10 Online.It Haves Apps’Games’etc.

I’ll Make Apps But I Need Help


Update UseItemCaptureMessage to use spawn_point_id

Update UseItemCaptureMessage to use spawn_point_id like the other messages

I'm reluctant to merge this, stuff like this contains breaking changing. I've got a few changes like these I'd like to make myself, but I suggest we bundle this in a v2.


From private repo

@v-alje : Thanks for your contribution to the Azure documentation! The author, @dkkapur, has been notified to review your proposed change.


fix included qualifications for federated users

coverage: 87.44% (+0.08%) from 87.361%
when pulling 591c3002b563b465a385217ab43fb1ae4e2b919a on fix-federation-included-qualification
into 6c12acb46503b2dad6f3ff90684246f3d007e366 on main.


proposal: encoding/json: add schema support

Background
Currently, the encoding/json package in Go provides functionality for encoding and decoding JSON data, but it does not support JSON Schema. JSON Schema is a powerful tool for validating the structure of JSON data, and it's widely used in many applications.
Proposal
I propose to add JSON Schema support to the encoding/json package. This would allow developers to validate JSON data against a schema, and it could also provide a way to automatically generate Go types from a JSON Schema.
Benefits
Adding JSON Schema support would have several benefits:

Data validation: JSON Schema provides a clear and standardized way to validate JSON data. This can help prevent bugs and improve the reliability of applications.

Code generation: With JSON Schema support, we could potentially generate Go types from a schema. This could save developers time and reduce the risk of errors.

Interoperability: JSON Schema is a widely used standard. By supporting it in Go, we can improve the interoperability of Go applications with other systems.

Implementation
The implementation details would need to be discussed further. One possible approach could be to integrate an existing open-source JSON Schema library into the encoding/json package
The new functionality could look something like this:
// Load a JSON Schema from a file
schema, err := json.LoadSchema("schema.json")
if err != nil {
    // handle error
}

// Validate JSON data against the schema
err = schema.Validate(jsonData)
if err != nil {
    // handle validation error
}

// Unmarshal Go types from the schema
types, err := schema.Unmarshal(jsonData)
if err != nil {
    // handle error
}

This would make it much easier to work with JSON data in Go, especially in applications that need to handle complex or variable data structures.
Impact
Adding JSON Schema support to the encoding/json package would increase its complexity and maintenance cost. However, I believe the benefits would outweigh the costs. JSON Schema is a widely used standard, and supporting it in Go would make the language more attractive to developers who work with JSON data.
I'm looking forward to hearing your thoughts on this proposal.
Thank you.

CC @dsnet @mvdan

Hi, thanks for your proposal.
It's not clear to me that this is something that needs to live inside the standard library, as opposed to something that is first developed externally and once it has proven it's utility and worth, then be considered for adoption. In your example, all of the schema parsing and validation logic occurs separate from the unmarshal, which calls into question whether this needs to be part of the "json" package versus say a "jsonschema" package.
Also, I think it is highly unlikely to adopt something in the stdlib where the specification is not finalized: https://json-schema.org/specification.html

Ok, thanks for the answer, I'll look for another way。


How to perform cross-validation during the fine-tuning process?[Question]

Question
I have been fine-tuning the llava-v1.5-13b model on my own dataset using the finetune_task_lora.sh script. While the training phase performed well, I observed an absence of any validation process throughout the training, potentially culminating in overfitting concerns. It would be grateful if someone could offer some advice.

I am finetuning llava-v1.6-vicuna-7b and want to know how can I calculate validation loss during lora fine-tuning


fix(barbar): CurrentBackground

Before (Low icon contrast):

After:

Super personal but I don't enjoy some parts of this change. The BufferTabPageFill looks terrible to me, the color becomes almost like a grey thing that doesn't match the rest of the theme. I replaced it back to bg_statusline

Super personal but I don't enjoy this change or the separator change. The BufferTabPageFill becomes almost like a grey thing that doesn't match the rest of the theme. I rolled back till this commit, because there are also other changes into the separator.
btw this is how it looks before this change for me

So beautiful, more than enough contrast. Maybe these changes could be applied only to a style and not the entire theme? @folke @otavioschwanck
I am using night style

The Active background icon contrast problem that was fixed is not for every icon, just some.  Every change was made based on another editors (VSCode has a similar approach to the contrasts).

Personally, i find it must more elegant and less intrusive then before.  Less pollution on the screen, the current tab is more clear, the active background tab mixes with the editor bg (like vscode as example), and i can still see the inactive tabs.

Hi, I prefer the darker tabfill (example 2), maybe that is also why I like the night variant? 😆 .  Thanks for taking the time to answer and try it out 😄

Hi, I prefer the darker tabfill (example 2), maybe that is also why I like the night variant? 😆 . Thanks for taking the time to answer and try it out 😄

Merged. A tip: The current separator of barbar messes the padding. If it bothers you, you can copy my config:
      require('bufferline').setup({
        hide = {extensions = true},
        icons = {
          -- Configure the base icons on the bufferline.
          buffer_index = false,
          buffer_number = false,
          button = '',
          -- Enables / disables diagnostic symbols
          diagnostics = {
            [vim.diagnostic.severity.ERROR] = {enabled = true, icon = 'ﬀ'},
            [vim.diagnostic.severity.WARN] = {enabled = false},
            [vim.diagnostic.severity.INFO] = {enabled = false},
            [vim.diagnostic.severity.HINT] = {enabled = false},
          },
          filetype = {
            custom_colors = false,
            enabled = true,
          },
          separator = {left = '', right = '▕'},
          modified = {button = '●'},
          pinned = {buffer_index = true, filename = true, button = '', separator = { right = '▕', left = ''} },
          alternate = {filetype = {enabled = false}},
          current = {buffer_index = false},
          inactive = {button = '', separator = {left = '', right = '▕'}},
          visible = {modified = {buffer_number = false}},
        },
        sidebar_filetypes = {
          ['neo-tree'] = {event = 'BufWipeout'},
        },
        exclude_ft = {'netrw'},
        highlight_visible = false,
      })

Thanks, indeed it was bothering me 😆


LeetHub v3 not pushing code to GitHub

Description:
@raphaelheinz I've been using LeetHub v3 for about a week now, and it has been working fine. However, today (08/05/2024), after submitting my code, it passed all the test cases but did not push the code to GitHub. I tried manually pushing by pressing the push button multiple times, but it didn't work. I suspect the issue might be related to the recent UI changes made by LeetCode in the user profile summary section. Every time there's a UI change on LeetCode, it seems to cause a bug with LeetHub.
To Reproduce:

Go to LeetCode.
Submit code using LeetHub v3.
Observe that the code passes all test cases.
Manually press the push button.
Notice that the code is not pushed to GitHub.

Expected Behavior:
After passing all test cases and pressing the push button, the code should be pushed to GitHub as usual.
Screenshot:

Additional Context:
I've been using LeetHub v3 without any issues until today. The only noticeable change I've seen is the update in the LeetCode UI, particularly in the user profile summary section. It seems that every time there's a change in the UI, it affects LeetHub's functionality.

Hi @Pushpakumar02,
sorry for my late response. I tried but was not able to reproduce this issue. I tested both dynamic layouts (run/submit button on top and on bottom) Pushing code worked for me. Could you recheck please?

I have the same problem.

Hi @raphaelheinz,
Thanks for your response. The issue lasted only for some time on that day (i.e., 08/05/2024). Now the extension works perfectly fine. Thank you for maintaining this project; it is really helpful to keep track of the problems I have solved and to revise effectively.
I have an enhancement request as well. Right now, I'm adding (editing) the problem topic manually in the README.

If the problem topic could be added automatically along with the code when it is pushed to GitHub, it would save some time.
Thanks for reviewing the issue.
Happy Leetcoding!


Cannot use sample_qubo of BraketSampler with postprocessingType parameter

Describe the bug
Cannot use the example from tutorial to test the sample_qubo function of BraketSampler
To reproduce
from braket.ocean_plugin import BraketSampler
sampler = BraketSampler(s3_folder, "arn:aws:braket:::device/qpu/d-wave/Advantage_system4")
Q = {(0, 0): -1, (4, 4): -1, (0, 4): 2}
sampleset = sampler.sample_qubo(Q, postprocessingType="SAMPLING", shots=100)
Expected behavior
Run without errors
Screenshots or logs

System information
A description of your system. Please provide:

Amazon Braket Python Ocean Plugin version:1 .0.6
Amazon Braket Python SDK version: 1.9.5.post0
Amazon Braket Python Schemas version: 1.4.1
Python version: 3.7.12

Additional context
Add any other context about the problem here.

Hello,
Thank you for reaching out! For this issue and https://github.com/aws/amazon-braket-ocean-plugin-python/issues/63, a fix will be coming out shortly.
In this particular case, the device specific properties for arn:aws:braket:::device/qpu/d-wave/Advantage_system4 can be found here. The other D-Wave device, arn:aws:braket:::device/qpu/d-wave/DW_2000Q_6, has device properties defined in a schema here.
Feel free to respond with any further questions.

A fix went out in https://github.com/aws/amazon-braket-ocean-plugin-python/pull/64 for this issue.


feat: add eslint9 compatibility

description
This adds support for ESLint v9 by replacing deprecated function calls.
The context.js is just needed for compatibility with v7.
If this was my project, i would just drop v7 support and remove it, but that is your call ;)

Thank you very much! I commented on https://github.com/salesforce/eslint-plugin-lwc/pull/148 as well, but we are in the process of evaluating ESLint v9 to figure out how or if we can maintain backwards compatibility with older versions as well.


update some packages to latest version, remove deprecated dependency... closes #5

update some packages to latest version, remove deprecated dependency improve routing auth flow adding onEnter and checkAuth method. closes #5

Thanks so much, I'll check it out soon!

A few nitpicks here and there, but other than that it looks great! Could you fix those and then I'll merge.
Thanks so much!

@mxstbr it's moved.. just one thing I can't get to access the store from the checkAuth any thoughts on that? one of the reasons I kept on the same file.
I also added sourcemap/devtools to webpack to be able to debug the file easier.

Interesting, that's indeed a problem. Maybe that was a mistake, would you mind reverting that change and putting both of those functions into the app.js again? Thanks and sorry for the troubles!
What does sourcemap/devtools do?

Done @mxstbr no problem.

Thanks so much @weblancaster, great work!


Checkout after creating a new branch

I am a big fan of the new feature below. It will allow us more flexible gitops operations.
https://github.com/argoproj-labs/argocd-image-updater/pull/304
However, I found a bug after trying the feature by myself on my local environment.
It seems after creating a new branch, Argo CD doesn't checkout the newly created branch. In the end, a new branch is pushed without any changes committed.
So, I've added a checkout process after branch creation.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


How to configure tcp_proxy with CDS?

I originally posted this in Slack but wasn't able to get a reply from those who were online at the time. Putting it here for asynchronous conversation purposes.
Is it possible to get tcp_proxy working with clusters as defined via CDS? I am able to get it working with http_connection_manager just fine. Here is the error I'm encountering:
[2017-11-15 01:18:26.445][251][critical][main] source/server/server.cc:78] error \
  initializing configuration '/etc/envoy.json': tcp proxy : unknown cluster \
  'TCPSERVICE' in TCP route

However that TCPSERVICE service is available in CDS. The CDS response provides information about hundreds of different clusters. Here's a truncated result with just the applicable one:
{
  "clusters": [
    "...many HTTP services",
    {
      "connect_timeout_ms": 2000,
      "hosts": [
        {
          "url": "tcp://instance1.datacenter.opentable.com:1234"
        }
      ],
      "lb_type": "random",
      "name": "TCPSERVICE",
      "type": "strict_dns"
    }
  ]
}

And finally, here is what my generated configuration file looks like. If the egress_listener-TCPSERVICE section is removed then the file compiles just fine and I'm able to make egress HTTP connections.
{
  "listeners": [
    {
      "name": "ingress_http_listener",
      "address": "tcp://<IP_ADDRESS>:3002",
      "filters": [
        {
          "name": "http_connection_manager",
          "config": {
            "codec_type": "auto",
            "stat_prefix": "CONSUMERNAME-ingress",
            "route_config": {
              "virtual_hosts": [
                {
                  "name": "route_vhost_local_service",
                  "domains": [
                    "*"
                  ],
                  "routes": [
                    {
                      "timeout_ms": 0,
                      "prefix": "/",
                      "host_rewrite": "tcp://<IP_ADDRESS>:3000",
                      "cluster": "CONSUMERNAME-cluster-ingress"
                    }
                  ]
                }
              ]
            },
            "filters": [
              {
                "name": "router",
                "config": {}
              }
            ]
          }
        }
      ]
    },
    {
      "name": "egress_http_listener",
      "address": "tcp://<IP_ADDRESS>:80",
      "filters": [
        {
          "name": "http_connection_manager",
          "config": {
            "codec_type": "auto",
            "stat_prefix": "CONSUMERNAME-egress",
            "route_config": {
              "virtual_hosts": [
                {
                  "name": "route_vhost_remote_services",
                  "domains": [
                    "*"
                  ],
                  "routes": [
                    {
                      "prefix": "/",
                      "cluster_header": "Envoy-Discovery-Target",
                      "timeout_ms": 15000,
                      "retry_policy": {
                        "retry_on": "5xx",
                        "num_retries": 3,
                        "per_try_timeout_ms": 5000
                      }
                    }
                  ]
                }
              ]
            },
            "filters": [
              {
                "name": "router",
                "config": {}
              }
            ]
          }
        }
      ]
    },
    {
      "name": "egress_listener-TCPSERVICE",
      "address": "tcp://<IP_ADDRESS>:6379",
      "filters": [
        {
          "name": "tcp_proxy",
          "config": {
            "stat_prefix": "CONSUMERNAME-egress-TCPSERVICE",
            "route_config": {
              "routes": [
                {
                  "cluster": "TCPSERVICE"
                }
              ]
            }
          }
        }
      ]
    }
  ],
  "cluster_manager": {
    "cds": {
      "refresh_delay_ms": 10000,
      "cluster": {
        "name": "envoy-discovery.api.opentable.com",
        "type": "logical_dns",
        "connect_timeout_ms": 250,
        "lb_type": "round_robin",
        "hosts": [
          {
            "url": "tcp://envoy-discovery.api.opentable.com:80"
          }
        ]
      }
    },
    "clusters": [
      {
        "name": "CONSUMERNAME-cluster-ingress",
        "connect_timeout_ms": 250,
        "type": "logical_dns",
        "lb_type": "round_robin",
        "hosts": [
          {
            "url": "tcp://<IP_ADDRESS>:3000"
          }
        ]
      }
    ]
  }
}

My intention with this approach is to provide a catch-all for all HTTP traffic, routing based on the Envoy-Discovery-Target header. When it comes to non-HTTP traffic I'll generate a list of those tcp_proxy entries based on the name of the cluster and an internal port to listen on.

Currently, tcp_proxy clusters must be defined when the listener is created. They cannot come later via CDS. Thus, in the current implementation you will need to use LDS also. It would be possible to relax this and allow the tcp_proxy to specify clusters that are not yet defined, but that would require a code change.

Thanks for the reply, I'll checkout LDS.

It looks like I can output the following JSON from an LDS to get my desired outcome:
{
  "listeners": [
    {
      "name": "%TCP_SERVICE_NAME%-listener",
      "address": "<IP_ADDRESS>:%DESIRED_PORT%",
      "filters": [{
        "name": "%TCP_SERVICE_NAME%-filter",
        "config": {
          "name": "tcp_proxy",
          "config": {
            "stat_prefix": "%TCP_SERVICE_NAME%-egress",
            "route_config": {
              "routes": [{
                "cluster": "%TCP_SERVICE_NAME%"
              }]
            }
          }
        }
      }]
    }
  ]
}

However with this scenario the LDS needs to somehow keep a registry of relationships between services. For example if I have consumers C1, C2, C3, then LDS needs to know that C1 needs to talk to producers P4 and P5, C2 needs to talk to P6, etc. Registering these requirements ahead of time seems a little dangerous, especially when C1 version 2.0 is released and needs to talk to P6 and no longer P4. Also, what happens when a developer does one-off local testing?
I do know, at the point in time the envoy.json file is created, which servicename/ports I want to access from a given consumer. Like I know that C1 wants to access P4 and that C1 is expecting to do so over port 1234. The listeners I need won't really be dynamic; C1 will always need to talk to P4 and P5 through the same ports.
Does this still sound like LDS is the best approach? Are most users somehow registering the producers they need to communicate with ahead of time? Does my use-case even make sense or am I beginning to misuse Envoy?

Does my use-case even make sense or am I beginning to misuse Envoy?

Unfortunately there is no right answer here. Your use case makes sense, but every use case is different in terms of whether you can use centralized control or service local based configuration. I would say that in general most people are moving towards feeding intention into the central management system and serving it from there.
It's not a very difficult change to add a configuration option to allow TCP proxy config to load with a cluster that does not exist and gracefully fail at runtime if the cluster continues to not exist. If you want to turn this issue into a feature request that's fine also.

@mattklein123 thanks for the recommendation, glad to hear it wouldn't be a difficult change. I've created #2075.


[MAINT]: rename sol.tile.main

Instead of being called sol.tile.main and sol.tile.vector_util, we should call these something that more directly indicates what they're for. I'm thinking sol.tile.raster_tile and sol.tile.vector_tile (include "_tile" in the names to differentiate them from sol.raster and sol.vector)

Resolved with #125


Reconstructing Original RGB Frames from Motion Vector and Residual

Hello! I am using the compressed video reader to read the motion vectors and residuals from a video. I attempted to reconstruct the original video’s RGB frames using the motion vectors and residuals from P-frames, along with the previous P/I-frame. However, the reconstructed frames do not match the original frames (with noises).
I-frame0

P-frame0 (reconstructed by I-frame0)

P-frame1 (reconstructed by P-frame0)

Here is the process I followed for reconstruction:

Convert the reference frame to YUV space.
Use the motion vectors to calculate the offset matrix (micro_block=4).
Add the residuals. Since the residuals are centered at 128, I subtract 128 from them.
Convert the final result back to RGB space.

Below is my code:
import numpy as np
from tqdm import tqdm
import cv2

def reconstruct_video(frames, gt_frames):
    reconstructed_frames = []
    previous_frames = {"I": None, "P": None, "B": None}

    for idx, frame in tqdm(enumerate(frames)):
        if frame["pict_type"] == "I":
            # Iframe：directly using RGB Value
            reconstructed_frame = frame["rgb"]

            previous_frames["I"] = reconstructed_frame
            previous_frames["P"] = None
        elif frame["pict_type"] == "P":
            # Pframe：based on previous reconstructed Iframe/Pframe
            ref_frame = previous_frames["I"] if previous_frames["P"] is None else previous_frames["P"]
            motion_vectors = frame["motion_vector"]
            residuals = frame["residual"]
            reconstructed_frame = reconstruct_frame(ref_frame, motion_vectors, residuals)
            previous_frames["P"] = reconstructed_frame
        elif frame["pict_type"] == "B":
            # skip Bframe for now
            continue
        else:
            raise ValueError(f"Unsupported frame type: {frame['pict_type']}")

        # saving reconstructed frame
        reconstructed_frames.append((frame["pict_type"], reconstructed_frame))

    return reconstructed_frames

def reconstruct_frame(reference_frame, motion_vectors, residual, gt=None):
    """
    Reconstruct the P-frame from the reference frame, motion vectors, and residual.

    :param reference_frame: numpy array of shape (height, width, 3), the RGB reference frame
    :param motion_vectors: numpy array of shape (height/4, width/4, 4), motion vectors for each 4x4 block
                           The 4 channels are [L0_x, L0_y, L1_x, L1_y].
    :param residual: numpy array of shape (height, width, 3), the residual values to be added to the predicted frame
    :return: numpy array of shape (height, width, 3), the reconstructed P-frame
    """

    reference_frame_yuv = cv2.cvtColor(reference_frame, cv2.COLOR_RGB2YUV).astype(np.float32)

    # Dimensions of the reference frame
    height, width, _ = reference_frame.shape

    # Initialize the predicted frame in YUV color space
    predicted_frame_yuv = np.zeros_like(reference_frame_yuv).astype(np.float32)
    motion_vectors = motion_vectors.astype(np.int16)

    # Motion vector block size
    block_size = 4

    for y in range(0, height, block_size):
        for x in range(0, width, block_size):
            mv_block_y = y // block_size
            mv_block_x = x // block_size

            # Motion vector for this block
            mv_x = motion_vectors[mv_block_y, mv_block_x, 0]
            mv_y = motion_vectors[mv_block_y, mv_block_x, 1]

            # Reference block position (may include fractional values in real scenarios)
            ref_x = x + mv_x
            ref_y = y + mv_y

            # Ensure the reference position is within bounds
            ref_x = np.clip(ref_x, 0, width - block_size)
            ref_y = np.clip(ref_y, 0, height - block_size)

            # Copy the block from the reference frame to the predicted frame
            predicted_frame_yuv[y:y+block_size, x:x+block_size, :] = reference_frame_yuv[ref_y:ref_y+block_size, ref_x:ref_x+block_size, :]

    residual = residual.astype(np.float32)
    tmp_res = predicted_frame_yuv
    tmp_res += (residual - 128)
    reconstructed_frame_yuv = np.clip(tmp_res, 0, 255).astype(np.uint8)

    reconstructed_frame_rgb = cv2.cvtColor(reconstructed_frame_yuv, cv2.COLOR_YUV2RGB)

    return reconstructed_frame_rgb

import cv_reader
import decord
from decord import cpu
video_path = './test_data/h264_sample.mp4'
frames = cv_reader.read_video(video_path=video_path, with_residual=True)
rgb_frames = decord.VideoReader(video_path, num_threads=1)
gt_frames = []
for f in frames:
    if f['pict_type'] == 'I':
        batch = rgb_frames.get_batch([f['frame_idx']]).asnumpy()
        f['rgb'] = batch[0]
        gt_frames.append((f['pict_type'], f['rgb']))
    elif f['pict_type'] == 'P':
        batch = rgb_frames.get_batch([f['frame_idx']]).asnumpy()
        gt_frames.append((f['pict_type'], batch[0]))
    else:
        gt_frames.append(None)

reconstructed_video = reconstruct_video(frames[:40], gt_frames)

# save resonstruct frames
from PIL import Image
import shutil
import os
if os.path.exists('resons'):
    shutil.rmtree('resons')
os.makedirs('resons')
for idx, (type_, f) in enumerate(reconstructed_video):
    img = Image.fromarray(f)
    img.save(f'resons/resons{idx}_{type_}.png')

Could it be that I have misunderstood the meaning of the motion vector or residual extracted using the cv-reader?
P.S. I noticed that residuals can also be extracted from I-frames. What is the meaning of the residuals in this case?

Hello @joez17 , I apologize for the late reply.
Unfortunately, I am not an expert in this area, so I’m unable to help you with reconstructing video from motion vectors and residuals as you had hoped. However, I believe that going from motion vectors and residuals to actual video is not something that can be solved with simple code—it’s still far from a fully functional decoder. You might want to refer to some Python-based H.264 decoder implementations (e.g. jackliang086/py-h264-decoder), as they contain many processing units.


[Bug]: OnNewToken repeatadly called

Component/Nuget
Push - Native (Shiny.Push)
What operating system(s) are effected?

[ ] iOS (13+ supported)
[ ] Mac Catalyst
[X] Android (8+ supported)

Version(s) of Operation Systems
Android 14
Nuget version: 3.3.3
Hosting Model

[X] MAUI
[ ] Native/Classic Xamarin
[ ] Manual

Steps To Reproduce
I just started to look at implementing the OnNewToken method in the IPushDelegate. But when I call PushAccessState result = await _pushManager.RequestAccess();, OnNewToken is then repeatedly called and hangs the app.
Here is a video showing the issue -
https://github.com/user-attachments/assets/09dd003e-f34b-49ed-a9f9-695f4bf5fae5
Expected Behavior
OneNewToken to be called once
Actual Behavior
Its repeatedly called and I have to force close the app
Exception or Log output
No response
Code Sample
I will create repo if needed, hoping I'm just misunderstanding something.
Code of Conduct

[X] I have supplied a reproducible sample that is NOT FROM THE SHINY SAMPLES!
[X] I am a Sponsor OR I am using the LATEST stable/beta version from nuget (v3.0 stable - ALPHAS are not taking issues - Sponsors can still send v2 issues)
[X] I am Sponsor OR My GitHub account is 30+ days old
[X] I understand that if I am checking these boxes and I am not actually following what they are saying, I will be removed from this repository!

Might be my issue, so ignore for now (sorry)

Dont understand why it was happening but implemented a work around an its all working as expected now

Always include a full sample or the issue is closed.  Please don't file anything as "hoping it is a misunderstanding".
You shouldn't need a workaround.

@aritchie you are right, here is the repo -
I've slimmed down our app as much as I can to repo the issue -
OnNewTokenRepo.zip
Here is an updated video showing the same issue in the repo project -
https://github.com/user-attachments/assets/6245d55c-fbe5-4140-aa86-86db7aa31b07
Think the issue is in Features > PushNotifications > Handlers > HandleDeviceRegistration > RegisterOrUpdate() I'm recalling await _pushManager.RequestAccess() that's causing a loop between OnNewToken and my code.
But I did look into your code and see you have checks in place to only call OnNewToken when there is a change that you are tracking, so not sure why that's not taking effect - https://github.com/shinyorg/shiny/blob/1b4138d42835a71447cee7b4134c7b0ef25b2f21/src/Shiny.Push/Platforms/Android/PushManager.cs#L117C13-L117C72
The workaround I've done was to update the code in OnNewToken to fire the update on a background thread an ignore it (not sure why this works, but this does stop OnNewToken being recalled) -
public Task OnNewToken(string token)
{
	try
	{
		_pushNotificationFeature.HandleDeviceRegistration.RegisterOrUpdate(token).SafeFireAndForget();
	}
	catch(Exception)
	{
		// intentionally left blank
	}

	return Task.CompletedTask;
}

I need smaller samples in the future please.  I've got stuff to do too.  I'm happy to help, but I fix the library, not all the code around it.  In this case, you've identified your issue quite well.  You're calling RequestAccess downstream from the OnNewToken which is causing a loop.  This isn't something I would fix or implement a guard against.

@aritchie Thanks, no prob, will restructure the code.


should patch webhook on managed cluster

https://github.com/open-cluster-management/backlog/issues/10074
https://github.com/open-cluster-management/backlog/issues/10096
https://github.com/open-cluster-management/backlog/issues/10131
https://github.com/open-cluster-management/backlog/issues/10139
https://github.com/open-cluster-management/backlog/issues/10142

I think https://github.com/open-cluster-management/backlog/issues/10181 hit the same issue prior to the fix getting in.


Add comparator prop to Column class

Part 2/2 for Hoist Issue #1216
Hoist P/R Checklist
Review and check off the below. Items that do not apply should be checked to indicate they have been considered. If unclear if a step is relevant, please leave unchecked and note in comments.

[ ] Up to date with develop branch as of last change.
[x] Ready for review (or add wip label).
[x] Added CHANGELOG entry (or N/A)
[x] Checked for breaking changes (add breaking-change label + CHANGELOG if so, or N/A)
[x] Updated doc comments / prop-types (or N/A)
[x] Reviewed and tested on Mobile (or N/A)
[ ] Created Toolbox branch / PR (link provided here, or N/A)

Would love to go through it with you two tomorrow and understand this better.  Looks promising.

Still WIP.  Broke something last night with a variable change.


Add Strapi

Add the Strapi framework that allows you to build powerful back-end with no effort on top of Koa.

Thanks for the suggestion, but I'm going to have to pass on this. It's hard for me to judge a framework without any community. Happy to reconsider some time in the future when you've gathered some traction and community around the project ;)

Sure I understand, thank you for your feedback @sindresorhus. ;-)


init monitor [11470]

This PR must be merged after #60
Start reviewing from commit with description "Mocks for DDS entities"
Some minor corrections to other backend code were also added as they were found during this development

Build is failing due to the change in the ${PROJECT_NAME}:

Solved on dba0854

Also, running the tests locally, it seems that:
* 371 - init_monitor_tests.init_monitor_twice: timeouts occasionally. It also fails with segmentation fault from time to time.

This and the other failures in tests were caused by the monitor being a static singleton, and therefore, not being reset between one execution and the next one. Resolved on 2f713ae

The following tests start issuing a GMOCK_WARNING: Uninteresting mock function call - returning directly. in the following tests:

These seem to be solved by something corrected above. Probably it was also related to the singleton not being reset between executions

Death tests use fork(), which is unsafe particularly in a threaded context. For this test, Google Test detected 11 threads.

This happens randomly because of the EXPECT_DEATH tests. It happens since the first time these kind of tests were added in previous PRs.

I forgot to check the coverage report. I am concerned about these lines:

https://app.codecov.io/gh/eProsima/Fast-DDS-statistics-backend/compare/72/diff#D1L278: I think we should try to cover this line with a test.
https://app.codecov.io/gh/eProsima/Fast-DDS-statistics-backend/compare/72/diff#D2L51: this line should also be covered.
https://app.codecov.io/gh/eProsima/Fast-DDS-statistics-backend/compare/72/diff#D2L194: should we cover this case?


Multi Tenancy Source Code

Multi Tenancy Source Code is unavailable?
https://github.com/volkanceylan/Serenity-Tutorials/tree/master/MultiTenancy

Multi tenancy source is not available at the moment. You may follow from guide.


fid scan still not working properly

branch: master
starting the fid scan creates one fid (FID scan) then no updates appear
the FID is not properly scaled and it cannot be interacted with - no new experiment can be started until the acquisition server is restarted

Can you run, in a terminal window,
ps -ef | grep Expproc
to get the PID of the Expproc process. Then run
sudo strace -o bout -s 128  -t -p <PID_of_Expproc>
and then start the Fid scan. After it fails, send me the bout file.

Hi dan,
this is the b12out for the fid scan, currently the MPS gets a firmware
update so the other issue will have to wit
Karl
On Fri, Aug 11, 2023 at 4:01 PM Dan Iverson @.***> wrote:

Can you run, in a terminal window,
ps -ef | grep Expproc
to get the PID of the Expproc process. Then run
sudo strace -o bout -s 128 -t -p <PID_of_Expproc>
and then start the Fid scan. After it fails, send me the bout file.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: @.***>

--
Karl Rieger
@.***
Bridge 12 Technologies, Inc.
11 Michigan Dr Ste 2, Natick, MA 01760
--

Bridge12 Technologies, Inc.
11 Michigan Drive Ste 2
Natick, MA 01760, USA
Web:
http://www.bridge12.com http://www.bridge12.com/

This email and any files
transmitted with it
are company confidential, meant for the sole
use of the
intended recipient. Any use or
dissemination of this email by others is
strictly
prohibited. If you are not the intended recipient,
please contact
the sender immediately.

OpenVnmrJ_B12T has a script to update the MPS firmware.
See OpenVnmrJ_B12T/firmware/uploadFirmware


R language

@Niketkumardheeryan  @Rutikab12 @pratishthaa Completed on issue 245 please check it out and if there is some correction please let me know.
It fixes https://github.com/Niketkumardheeryan/ML-CaPsule/issues/245

@Rutikab12 please assign level to this so that I can get point on leaderboard .


the batch file isnt working

Hey, just open pysilon from builder.py with python instead of using the .bat

Hey, just use the ModdedPysilon version, it covers every bug and it make sure your discord account never get banned.
Leave me a star if you like my project ;)


Roadmap

Is there a roadmap of what's required before this library becomes production ready? Is anyone already using it in production? We prototyped a low-risk service with tower-grpc that we're about to deploy to production, but we don't feel comfortable writing core services in rust until there is a production-ready gRPC library.

People are using it in production, but the library is young and under active development.
I hope to get this to crates.io soon(ish) but there will be significant API changes before then. Hopefully that will happen by the end of 2018.

@carllerche it's great to hear that it's being used in production and that it's under active development. That will make adopting Rust for some services easier.
Thank you.


The settings are not displayed

Jenkins and plugins versions report

Environment

Paste the output here

What Operating System are you using (both controller, and any agents involved in the problem)?
OS: macos Monterey 12.7.5
Browser: Google Chrome 126.0.6478.127
Jenkins 2.452.2
Reproduction steps

install plugin 2. locate to /manage/spacecode/

Expected Results
displaying plugin settings
Actual Results
Plugin settings is empty

and 2 errors in console

Anything else?
No response
Are you interested in contributing a fix?
No response

Hi @oFFraid,
It looks like the page couldn't load either its content or the javascript from the server due to some origin issues that shouldn't be there (probably http/https, or a wrong host name). Could you please show the contents of the network tab of the browser development tools so that I can see the failed requests and their URLs?

Hi @Kiryushin-Andrey. Here is a screenshot from the network tab. All requests have a status of 200. The host address (the one that is painted over) is ip:port of my Jenkins server.


[Announcement] Daily builds and introduction

Concerning daily builds
As of now, I manually fetch the latest commits from the parent fork, merge them, and then trigger the automated build process. This is done by hand, and typically at the end of the day (around 1800 - 2000 PDT).  If there are no new commits at the time of me checking in, then commits that happen after this time will make it into the release the day after.
All builds are done from the "master" branch, and the code does differ from that of the parent fork. Namely, the built-in yt-dlp updater points at my repository instead of that of the parent fork, and some file descriptors and strings have been changed to indicate that this is not an official release of yt-dlp, and was built and compiled by me.
If you are (understandably) concerned about any other undocumented changes to the code, you can easily verify any changes by checking out both forks and using the git diff command.
Additionally, I am maintaining another branch called "master-test" which exists for my own amusement, may break or won't work at all, and is not meant to be build for general circulation.
Concerning updates and reverting to official releases
Once you download one of my builds from releases, you will be able to update yt-dlp via yt-dlp -U. This will fetch the latest build from my unofficial (observeroftime01/yt-dlp) repository.
Should you wish to return to the official yt-dlp binaries, please simply delete my binary (or folder) and download the latest official release from yt-dlp/yt-dlp/releases.
What's the point of this?
I didn't want to wait for the latest release in order to benefit from the latest commits, so I started cloning the official yt-dlp (and originally youtube-dl) repository, and building the binaries locally, every day. Perhaps other people are interested in daily builds as well, but I don't feel comfortable uploading binaries build on my own machine to github. There is zero transparency of what code the binary was compiled with. Building them with github actions adds a layer of trust and verifiability to the build and distributed binaries, and it's overall a much better solution than me uploading my binaries every day. Github actions also allows me to build binaries for operating systems I don't use, with different versions of python, that others might find useful (e.g Win_x86, MacOS, MacOS_Legacy).
What is my part in all of this?
I am not a python developer. I can not provide you with support (although I will still try). I don't contribute to the yt-dlp project. I don't claim to take a shred of credit for this amazing application. If you find bugs, have feature requests, would like to report a broken site, etc. I suggest opening an issue over on the official fork's issue page yt-dlp/yt-dlp/issues.
Although the following applies before opening an issue there:
DO NOT EXPECT SUPPORT FOR AN UNOFFICIAL BUILD  FROM THE MAINTAINERS OF THE OFFICIAL FORK.
If you run into problems with my daily releases, please revert back to an official yt-dlp binary, and verify if the issue still exists there. If it does, then you may receive support from the people working on the official repository.
If your issue gets resolved there, then the code changes will find their way into my fork once they have been committed to their fork. While pull requests are welcome, the same idea applies: You'll be better off contributing to the official repository. Pull requests merged here but not in the official repository will cause the code to diverge too much from their original fork, and this could lead to problems down the road (which I would really like to avoid).
This fork and repository exists primarily to automatically build the code found in the parent fork. As such, I would like to keep the code in the master branch near identical to that of the official repository.
Suggestions, discussions and everything else are still welcome of course. If there is a convincing argument for changes here but not in the official repository then I will evaluate its merits and feasibility on an individual basis.
How much longer will I be doing this?
I really don't know. If you'd ask me now my answer would be: I have no plans on stopping. Perhaps one day the official fork will do automated daily releases, at which point the existence of this repository becomes redundant. Perhaps one day I'll return from vacation, and decide this isn't all that important to me anymore, and move on. Perhaps at some point it becomes too time-intensive for a daily task to continue. It's hard to answer such questions, as I don't know what the future holds. For as long as it feasible for me to do so, with a reasonable amount of daily effort, I'm going to keep on fetching the latest commits, merging them, and triggering the github action to build the project. What is considered a "reasonable amount of daily effort" depends on personal life circumstances. All I know is that for today, and likely also tomorrow, I have the 5 minutes to spare it takes me to click a few buttons and resolve the occasional merge conflict.

Further ideas
For further developments and improvements to the build process, I'm currently looking for a way to automatically sign the binaries build by Github Actions, or find a more tamper-resistant method of code verification.
Although Github Actions provides more transparency of what code the binaries were built against it is still not as secure as I would like. There is currently no way, for example, to download a release's source code, compile it yourself, and then compare your version's file hash to that of the one produced by Github Actions. Even when using the same operating system, python version etc. the file hash will be different. Even the same source code compiled twice on the same system will produce different results. This is unacceptable.
The file hashes are fine for verifying file integrity after a download or during the update process, but they don't guarantee that the file matches the source code automatically released by Github Actions. I understand that they are meant for checking the integrity of the file more so than to provide any sort of code verification. Also, there is currently no way to indicate what branch a release was created from, it only points at a commit or a tag.
Furthermore, if somebody was maliciously inclined, then such a person could simply alter the release created by Github Actions. It is trivial to swap out files, upload different source code, modify existing files and so on, without any notice to the user that modifications have occurred after the release was created.
Due to the nature of python, compiling the same code yields binaries which are functionally identical, but cryptographically different. While I know that signing the windows executables is possible, I'm not sure about the Linux or macOS binaries. Ideally, the binaries would be signed (by Github Actions, either with its own certificate, if that exists, and barring that, a user-provided one) after the build process and fingerprinted with the zipped source code's file hash. I don't know if this is possible (yet), but it would satisfy many of the concerns I addressed. I will evaluate the feasibility of this, and if such a solution could be implemented, I'd feel better.


Move unzip image to config

Issue Ref: Continues #607 Fixes #578
Description:
This PR updates #607 with the latest status of master. It also includes the required secrets for both the unzip and the function-builder image.
cc/ @rakesh-garimella
TODOs:

[x] Ready to review
[X] Automated Tests
[x] Docs

LGTM


[daily_dev] shuffle=True causes silent duppliction of parameters

Due to a buggy interaction between random.shuffle and numpy arrays shuffle=True silently corrupts data
See this link for a description of the bug
https://www.reddit.com/r/Python/comments/42uqqo/a_nasty_little_bug_involving_random_and_numpy/
Changing the line
import random
in ParamGrid.py
to adding numpys random solves the problem

Pull request https://github.com/autonomio/talos/pull/227

Thanks. This is merged, so closing.


Refactor fee computation during runtime execution

Motivation
The current code is difficult to adapt for #1474 and other missing features like #1537.
Proposal

Add the missing code to price write operations
Remove RuntimeCounts and RuntimeLimits
Introduce ResourceController to keep together a (fixed) policy, a tracker, and a balance.
The balance is systematically decreased when a new operation is "tracked".
Use a similar idea in ChainStateView::execute_block. This requires generalizing the code so that we can store the resource funding balance in the system execution view (where transactions can modify it any time).

Follows #1535
Test Plan
CI

Maybe for the "Release Plan": We'll need to update linera-infra/validators/scripts/create_and_upload_genesis.sh

That is optional but ok.


Typescript is included in the bundle

Describe the bug
One of your dependencies is improperly scoping their dev dependencies, causing typescript to be included in the final bundle of your package.
Steps to Reproduce the Bug or Issue
❯ yarn why typescript
yarn why v1.22.22
[1/4] 🤔  Why do we have the module "typescript"...?
[2/4] 🚚  Initialising dependency graph...
[3/4] 🔍  Finding dependency...
[4/4] 🚡  Calculating file sizes...
=> Found<EMAIL_ADDRESS>info This module exists because "reagraph#reakeys#ctrl-keys#just-types" depends on it.
info Disk size without dependencies: "30.86MB"
info Disk size with unique dependencies: "30.86MB"
info Disk size with transitive dependencies: "30.86MB"
info Number of shared dependencies: 0

Expected behavior
Not include Typescript
Screenshots or Videos
No response
Platform
All
Your Example Website or App
No response
Additional context
No response

Good catch! We will fix asap!

I wouldn't rely on that package to update; it looks pretty dead. You might need to vendor it


Actuator health check always returns property not loaded

Describe the bug
Hi, using cloud config client version 3.0.0 and native profile for configuration I always get that configuration property sources could not be loaded and status is UNKNOWN when calling the actuator health check.
"clientConfigServer": {
  "status": "UNKNOWN",
  "details": {
    "error": "no property sources located"
  }
}

Comparing to spring boot 1.x I was receiving:
"configServer": {
  "status": "UP",
  "propertySources": [
     "file:C:\\Users\user\projects\tagging.yml",
  ]
}

Here is my configuration:
spring:
  application:
    name: my-app
  cloud:
    config:
      discovery:
        enabled: true
        serviceId: config-server
      failFast: false
      retry:
       initialInterval: 10000
       maxInterval: 60000
       maxAttempts: 12
       multiplier: 10.1

I see also the log that probably should be "CompositePropertySource" but is Bootstrap one:
2021-02-23 10:11:15.402  INFO b.c.PropertySourceBootstrapConfiguration : Located property source: [BootstrapPropertySource {name='bootstrapProperties-configClient'},  BootstrapPropertySource {name='bootstrapProperties-file:C:\Users\user\properties.yml'}]

Can you provide a complete, minimal, verifiable sample that reproduces the problem? It should be available as a GitHub (or similar) project or attached to this issue as a zip file.

Hi,
here is my demo project. Let me now if you need something more:
demo.zip

So adding
spring:
  config:
    import: configserver:http//config-server

fixes the problem?

Unfortunately not it just shows the label instead of the actual property path or something..

#1813 takes care of not having spring.config.import
Lets reword the title based on the last comment.


HARP-6886: Z-fighting improvements.

Signed-off-by: Andrés Valencia Téllez<EMAIL_ADDRESS>Improved present z-fighting by:

Fixing extrusionFeature attribute copy (broken depth pre-pass for non animated buildings).
Removing the polygonOffset applied to meshes and applying instead a VS depth offset for edge geometries.

Thank you for contributing to harp.gl!
Before requesting a pull request, please remember to check the following documents:

contribution guidelines
coding style

If you are adding new functionality we would highly appreciate if you can describe what is the capability you are adding and even better if you can add some examples. Please also remember to add tests for it.
Our bots will check whether your PR can be directly integrated into the mainline. We have some internal integration tests running on the background, our bots will inform you of the next steps and someone from our team will take a look and help if needed!
And please do not forget to sign-off your commit! You can read more about DCO here. But, in short, you just need to use git commit -s or append --signoff when you are committing to the repo.
Happy contributing!

@zbigg Polygon offset cannot be applied to all primitives, only to triangle primitives.
What we actually wanted to do in our scene is to PULL the outlines geometry towards the screen, but since we cannot apply WebGL PolygonOffset to the GL_LINES, we ended up having to PUSH all the extruded geometries away from the scene.
In an initial implementation, this was fine, but now that we always render the groundPlane depth to our scene, this translated in low buildings undesirably clipping through the ground and presenting z-fighting issue when depthBuffer precision was not sufficient...
Current implementation solves both issues and performs a similar operation to what polygonOffset previously did.


Cannot index event publisher.Event{Content:beat.

{"type":"illegal_argument_exception","reason":"mapper [predecoder.timestamp] cannot be changed from type [keyword] to [text]"}
I'm trying to load a custom json in filebeat with OpenSearch . the same JSON file perfectly running in  Filebeat + opendistro

This is a dup of https://github.com/opensearch-project/OpenSearch/issues/667, resolved with https://github.com/opensearch-project/OpenSearch/pull/847. Set compatibility.override_main_response_version to put the cluster into a configuration that returns 7.10.2 as with ES OSS in OpenSearch GA.

java.lang.IllegalArgumentException: unknown setting [compatibility.override_main_response_version] please check that any required plugins are installed,

java.lang.IllegalArgumentException: unknown setting [compatibility.override_main_response_version] please check that any required plugins are installed,
@dblock

Are you running GA OpenSearch from https://opensearch.org/downloads.html? Can you please curl <your host>:9200 and provide output?

@dblock thanks problem Soled with New Release


Website Not Responsive

Describe the bug
Website is not responsive
Expected behavior
website will become responsive
Screenshots (Mandatory)

Additional Context (Mandatory )
Are you contributing under any open-source program ?
GSSoC '24

please label the issue

Hey there! I'm Harsh Abhishek from #GSSOC 2024. I'm a MERN web developer. With experience in numerous successful MERN stack projects, I excel in HTML, CSS,JavaScript,java.
Sample Live project link: https://harshsde0.github.io/1-1personaltraining/
LinkedIn profile: https://www.linkedin.com/in/harsh-abhishek-463359222/

I can resolve this issue of making the website responsive. Please assign this task to me.

Hey there assign me the issue , i have experience in resolving this kind of issues.
I am a MERN Developer from NIT Raipur

Hello I am Gargi from IIT Kharagpur! I work with html,css,js,react.js and so on and am eager to learn more. I'd appreciate being assigned this task for GSSoC 24.

Please assign this task to me.

I am prepared to work on resolving the issue with the website not being responsive. Kindly assign this task to me for resolution. Thank you.

Hey there, I am wilson zeugang a fullstack js developer, Making this page responsive will be a matter of hours, within which the results will really be appreciated please assign me the issue

#328 is already there on this same topic. Thanks for raising the issue but Sorry to close this issue


Call of Duty: Black Ops III has GPU usage and FPS spikes on the main menu.

This problem only happens on the main menu, where you start a game, choose gamemode or custommize weapons. The same thing does not happen with the Options menu in game, nor do the lag spikes happen in game. Just the menu. Tried the game both with Glorious Eggroll's Proton version 7-22 and Proton 7.0-3, with the same results. My DXVK logs are going to be from Proton-GE, due to it being the best Proton version to play Black Ops 3. The spikes are that the GPU usage jumps from around 50% to 10% regularly, such as every 5 or so seconds.
Software information
Call of Duty: Black Ops III, tested with Fsync both enabled and disabled, tested with Feral's Gamemode both enabled and disabled, no change in result.
System information

GPU: Geforce GTX 1050ti
Driver: 515.48.07
Wine version: Wine Staging 7.0
DXVK version: v1.10.1-async

Apitrace file(s)
Couldn't create one for now, I can do it later if absolutely needed.
Log files

d3d11.log:
BlackOps3_d3d11.log

dxgi.log:
BlackOps3_dxgi.log

Couldn't create one for now, I can do it later if absolutely needed.

It is needed.

Couldn't create one for now, I can do it later if absolutely needed.

It is needed.

Alright, if I may ask, what should I do to create it on Proton?
And a quick note, WineD3D does not work with the game, so I have to do it with DXVK.

Proton & DXVK is fine.

Alright then. Again, how exactly am I going to use it with Proton?

https://github.com/doitsujin/dxvk/wiki/Making-a-Trace

Here is the link for the Apitrace: https://drive.google.com/file/d/17hcXdecAuEy00cLtIVe6Wsp2LjX-U-QJ/view?usp=sharing

Just a quick note, this issue seems to be marked as d3d9 but I think the game runs on DirectX 11. Was that intentional?

This issue is related to the a steam client update and the game constantly pinging the servers to check for DLC, if you install all DLC (this includes the gamemodes multiplayer/campaign/zombies) the stutters stop and I can confirm this is the case.
There is a huge thread about it here
https://steamcommunity.com/app/311210/discussions/0/5135803832916918329/

Well that might be it. I only have Zombies and it's DLC's installed. Going to try out now.

You are correct, @KagoraTheGrindcoreAddict. Installing all the DLCs fixed the issue. Closing, as it is not DXVK related.


rmilter: remove invalid debug option

There's no debug option available, setting it causes the daemon fail to start.
# rmilter -d
rmilter: invalid option -- 'd'
Rapid Milter Version 1.6.7
Usage: rmilter [-h] [-d] -c <config_file>
-n - do not daemonize on startup
-h - this help message
-c - path to config file

This option was added in a more recent version. See 799a3f81478b94f11ba25e3ab7666f5599cd4faf.
I think it's useful to support that option instead of removing it.


Feature/cors

Description
Added CORS support.
options := cors.Default()
options.AllowedOrigins = []string{"https://google.com", "https://images.google.com"}
router.CORS(options)

Possible drawbacks
None.
Related issue(s)

#19

Coverage increased (+0.08%) to 98.246% when pulling 29cb75b94f18d6e022835741c98246ec21732eba on feature/cors into 017f9d992d462a58bee56006a55e36a23535d28b on develop.


Fixed powershell quickstart variable and added import-module for corr…

Fixed powershell quickstart variable and added import-module for correct az.network version

@GinSiuCheng : Thanks for your contribution! The author(s) have been notified to review your proposed change.

#label:"aq-pr-triaged"

@GinSiuCheng : Thanks for your contribution! The author(s) have been notified to review your proposed change.

#sign-off


fix(amplify-provider-awscloudformation): add new error message

Issue #, if available:
Given it is pretty trivial, there is no issue # associated with it.
Description of changes:
Something short and sweet.
When I do amplify push with either zero or two or more CloudFormation Template, the error message stays the same which is confusing and misleading for me.
On my team, due to someone mistakenly removing one of the cloudformation template, our amplify push did not work and the error messages was very misleading and suggested there might be more hidden Cloudformation template somewhere getting used until I realized it was just missing the template instead.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Hi, I have two questions,
1, The config.yml from circle ci is automatically added when I commit, I am not sure if this is needed or not
2, Is this change appropriate to add test cases as well?


[Feature][Issue-2324/Issue-2418] Add FE pages for Yarn queue management feature.

What changes were proposed in this pull request
Issue Number: close #2418

Brief change log
Add FE pages for Yarn queue management feature.
Verifying this change

Manually verified the change by testing locally.

Does this pull request potentially affect one of the following parts

Dependencies (does it add or upgrade a dependency): (yes / no)

Hi, @wangsizhu0504 Could you help to review this pr when you have free time ?
Thanks in advance~


Upgrade logback.xml, more verbose response loggers by default close #2509

Added commented out DEBUG / TRACE io.gatling.http.response loggers to the default logback.xml

Let's go this way for now, but it would be nice to have a single trigger. Will try to think of something.
Thanks!

Aye t'would be cool to have a single trigger. But at least now people won't fall into the same trap that I did and spend hours trying to debug odd responses :+1:


Ability to provide a replacement XHRLoader for the loader plugin.

Hi! I am using the Cache api (https://developer.mozilla.org/en-US/docs/Web/API/Cache) to have full control over caching and management of my 500mb+ game assets. However there is no feasible way (that I'm currently aware of or able to find) to have Phaser's normal asset system, which handles MultiAtlas and many other types quite well, be able to get files from something other than the internal XHRLoader. I was expecting File would reference the Phaser.Loader so I could at least override the xhr loader there and hack in my own approach.
Given that I was thinking it might be awesome to have the Loader plugin have a more generic approach allowing us to implement our own network (or otherwise) based loader handlers. I assume this might have implications on progress reporting and such. But most of it seems generic enough already, there's just no place to override the actual loader method.
If I can find the time I'll take a stab at a PR or at least API suggestion, but I'm not confident about my overall knowledge of the entire Loader system and would be afraid to do so without a lot of time to really grasp more.

For reference, I just came up with an approach to add directly to the cache, and made a bunch of utils around that in my own code. but for things like MultiAtlas that meant re-implementing the logic it has to build out the correct data and images, which isn't terrible but still increases the work required for anyone to load assets outside of the standard XHR approach.


Jax version requirement

Hi,
I've seen in 3a3e510 that the minimum Jax version was bumped to >=0.4.24.
I suppose this is necessary to run this library (and by extension Lorax)? I am running Jax on Google Cloud TPUs with default Jax version 0.4.13 and I'd love to use your libraries there.
Thanks for any help!

The easiest thing to do would probably be install qax==0.3.0. Does that work for you?

Hi, I ended up setting up a conda env with a more recent Jax version. I was a bit cautious about changing the Jax version of the default image but it works just fine!

Great! Let me know if you have any issues. I'd love to help.


Added test-arangodb-3_10 in CircleCI workflow.

Added test-arangodb-3_10 in CircleCI workflow.

GraphApiClientTest.PostVertexAsync_ShouldThrow_WhenVertexCollectionIsNotFound() was failing tests on line 437 because in ArangoDB 3.10, the error number is 1947 (not 1203). So there was a need to check for the version number on this line.
I've added support for version numbers to all test fixture classes. I think it gives us a bit more control on version-specific processing than the Trait attribute does. What do you think @DiscoPYF?


KTLS with openssl 3.0 fail with error ENOTCONN(Transport endpoint is not connected)

Kernel Support for KTLS:
kernel version is 5.15
CONFIG_TLS=y
CONFIG_TLS_DEVICE=y
CONFIG_CRYPTO_TLS=y
Openssl:
$ ./ Configure enable-ktls linux-aarch64
$ make
Server
$ ./openssl version
OpenSSL 3.0.2-dev 14 Dec 2021 (Library: OpenSSL 3.0.0 7 sep 2021)
$ ./openssl s_server -key rsa.key -cert server.pem -accept 443
error
file: crypto/bio/bio_sock2.c
function: BIO_socket()
ktls_enable(sock); failed with ENOTCONN error
setsockopt failed, 107, Transport endpoint is not connected
server logs( added some debug logs)
root@imx8mmevk:~# ./openssl s_server -key rsa.key -cert server.pem -accept 443
sk->sk_state != TCP_ESTABLISHED (log added in kernel net/tls/tls_main.c)
sk->sk_state != TCP_ESTABLISHED
BIO_socket sock_family = 10, sock_type = 1, sock_protocol = 6, return = 3
setsockopt failed, 107, Transport endpoint is not connected
BIO_socket, ktls_enable(asock) = 0
ACCEPT
setsockopt failed, 17, File exists
BIO_new_socket, ktls_enable(s) = 0
-----BEGIN SSL SESSION PARAMETERS-----
MF8CAQECAgMDBALAMAQABDAC9MHCSSlLXrS0D8tq2hCZtW0vmB1EC6HQerBThuev
PdX7VOUnD1a2bybdw1LfEiqhBgIEYcLciaIEAgIcIKQGBAQBAAAArQMCAQGzAwIB
HQ==
-----END SSL SESSION PARAMETERS-----
Shared ciphers:ECDHE-RSA-AES256-GCM-SHA384
Signature Algorithms: ECDSA+SHA256:ECDSA+SHA384:ECDSA+SHA512:Ed25519:Ed448:RSA-PSS+SHA256:RSA-PSS+SHA384:RSA-PSS+SHA512:RSA-PSS+SHA256:RSA-PSS+SHA384:RSA-PSS+SHA512:RSA+SHA256:RSA+SHA384:RSA+SHA512:ECDSA+SHA224:RSA+SHA224:DSA+SHA224:DSA+SHA256:DSA+SHA384:DSA+SHA512
Shared Signature Algorithms: ECDSA+SHA256:ECDSA+SHA384:ECDSA+SHA512:Ed25519:Ed448:RSA-PSS+SHA256:RSA-PSS+SHA384:RSA-PSS+SHA512:RSA-PSS+SHA256:RSA-PSS+SHA384:RSA-PSS+SHA512:RSA+SHA256:RSA+SHA384:RSA+SHA512:ECDSA+SHA224:RSA+SHA224:DSA+SHA224:DSA+SHA256:DSA+SHA384:DSA+SHA512
Supported Elliptic Curve Point Formats: uncompressed:ansiX962_compressed_prime:ansiX962_compressed_char2
Supported groups: x25519:secp256r1:x448:secp521r1:secp384r1
Shared groups: x25519:secp256r1:x448:secp521r1:secp384r1
CIPHER is ECDHE-RSA-AES256-GCM-SHA384
Secure Renegotiation IS supported
Using Kernel TLS for sending fail
Using Kernel TLS for receiving fail

Its unclear what you have done to get this output. It seems to me you have added additional debug logging to the OpenSSL source? If so, please supply further details of exactly what you have changed.
From the supplied output it looks to me like a connection was successfully established - but it didn't use KTLS? I would not have expected it to since you did not supply the "-ktls" option to s_server.

I added additional logs for debugging. as I am not getting the success log (Using Kernel TLS for sending).
log added in kernel(file net/tls/tls_main.c)
kernel is returning error -ENOTCONN when (sk->sk_state != TCP_ESTABLISHED) in function static int tls_init(struct sock *sk)
you are right that connection is establishing but it is not using ktls.
As per openssl changelog(https://www.openssl.org/news/changelog.html#openssl-30), support for Kernel TLS (KTLS) was added in openssl 3.0 and I am using OpenSSL 3.0.2-dev.
"-ktls" option was introduced in OpenSSL 3.1.0.(https://www.openssl.org/docs/manmaster/man1/openssl-s_server.html)
I am not sure if ktls support was added in openssl 3.0, then why "-ktls" option is introduced in 3.1.0.
can you confirm which openssl version has the working support for ktls?

As suggested by you, i tried with -ktls option with openssl 3.1.0, but still ktls is not working
$ openssl version
OpenSSL 3.1.0-dev  (Library: OpenSSL 3.1.0-dev )
$ openssl s_server -ktls -key rsa.key -cert server.pem -accept 443
sk->sk_state != TCP_ESTABLISHED
ACCEPT
-----BEGIN SSL SESSION PARAMETERS-----
MF8CAQECAgMDBALAMAQABDADNEkWucVTZpiKPtRz48bGM1wHHnOUlta9WcSH9Q3y
4jdP8DgTAZAkrkD9SbCbs6uhBgIEYdQH96IEAgIcIKQGBAQBAAAArQMCAQGzAwIB
HQ==
-----END SSL SESSION PARAMETERS-----
Shared ciphers:ECDHE-RSA-AES256-GCM-SHA384
Signature Algorithms: ECDSA+SHA256:ECDSA+SHA384:ECDSA+SHA512:Ed25519:Ed448:RSA-PSS+SHA256:RSA-PSS+SHA384:RSA-PSS+SHA512:RSA-PSS+SHA256:RSA-PSS+SHA384:RSA-PSS+SHA512:RSA+SHA256:RSA+SHA384:RSA+SHA512:ECDSA+SHA224:RSA+SHA224:DSA+SHA224:DSA+SHA256:DSA+SHA384:DSA+SHA512
Shared Signature Algorithms: ECDSA+SHA256:ECDSA+SHA384:ECDSA+SHA512:Ed25519:Ed448:RSA-PSS+SHA256:RSA-PSS+SHA384:RSA-PSS+SHA512:RSA-PSS+SHA256:RSA-PSS+SHA384:RSA-PSS+SHA512:RSA+SHA256:RSA+SHA384:RSA+SHA512:ECDSA+SHA224:RSA+SHA224:DSA+SHA224:DSA+SHA256:DSA+SHA384:DSA+SHA512
Supported Elliptic Curve Point Formats: uncompressed:ansiX962_compressed_prime:ansiX962_compressed_char2
Supported groups: x25519:secp256r1:x448:secp521r1:secp384r1
Shared groups: x25519:secp256r1:x448:secp521r1:secp384r1
CIPHER is ECDHE-RSA-AES256-GCM-SHA384
Secure Renegotiation IS supported
$ openssl s_client -quiet -connect <IP_ADDRESS>:443 -cipher 'ECDHE-RSA-AES256-GCM-SHA384' -tls1_2 -ktls
[1119274.610941] sk->sk_state != TCP_ESTABLISHED
Connecting to <IP_ADDRESS>
Can't use SSL_get_servername
depth=0 C=IN, ST=NOIDA, L=NOIDA, O=NXP, OU=EP, CN=Gaurav<EMAIL_ADDRESS>verify error:num=18:self-signed certificate
verify return:1
depth=0 C=IN, ST=NOIDA, L=NOIDA, O=NXP, OU=EP, CN=Gaurav<EMAIL_ADDRESS>verify return:1

I debugged further the invalid argument error reported from setsockopt called in ktls_start().
Problem is with crypto_info->tls_crypto_info_len.
when I applied the below change I could run s_server, s_client on linux with KTLS support.
below patch enables the aes_gcm_128 ciphers

AES128-GCM-SHA256
ECDHE-RSA-AES128-GCM-SHA256

diff --git a/include/internal/ktls.h b/include/internal/ktls.h
index 95492fd065..30ed5072de 100644
— a/include/internal/ktls.h
+++ b/include/internal/ktls.h
@@ -285,7 +285,7 @@ static ossl_inline int ktls_start(int fd, ktls_crypto_info_t *crypto_info,
int is_tx)
{
return setsockopt(fd, SOL_TLS, is_tx ? TLS_TX : TLS_RX,
-crypto_info, crypto_info->tls_crypto_info_len) ? 0 : 1;
+crypto_info, sizeof(crypto_info->gcm128)) ? 0 : 1;
}
When trying to enable other 2 ciphers, I am getting build errors in openssl.
3. AES256-GCM-SHA384
4. ECDHE-RSA-AES256-GCM-SHA384
when trying to build openssl for gcm256, getting compilation errors:
In file included from crypto/bio/bio_sock2.c:15:
include/internal/ktls.h:251:46: error: field 'gcm256' has incomplete type
struct tls12_crypto_info_aes_gcm_256 gcm256;
^~~~~~
By default Openssl has support for  aes_gcm_128 ciphers.
When include kernel tls.h file in openssl, aes_gcm_256 ciphers can be built and run without errors.
I feel that Openssl KTLS support for Linux is broken.

https://github.com/openssl/openssl/issues/17451
answered in above ticket.


FancyZones Layout Based on Modifier

📝 Provide a description of the new feature
What is the expected behavior of the proposed feature?  What is the scenario this would be used?
The user would be able to change the FancyZones layout based on the modifier (e.g. Shift, Ctrl, Alt) they have active.
If you'd like to see this feature implemented, add a 👍 reaction to this post.

@hlavell
can you please elaborate?

Sure. At the current moment, I use the 'Shift' key to view my fancy zones (I know this doesn't matter, it could be any key). I have a 32:9 monitor so I have three windows side-by-side. My suggestion was for each modifier (Shift, Ctrl, Alt) to have a different layout so that I could position the windows differently depending on which modifier I am using.
Sometimes I like to have my middle window larger than the two outer windows. The only way to do this at the moment is either to do it manually or go into the FancyZones editor and adjust the layout. Why not be able to do all this with just key modifiers?

@hlavell
good idea.

Adding a reference to https://github.com/microsoft/PowerToys/issues/1411 since they are related.

Tracked in https://github.com/microsoft/PowerToys/issues/6611


Add missing sensors for temperature delta on VBO and HUP

As requested here, a new issue for adding these diagnostic sensors for the temperature delta on the VBO and HUP.
Below is my current template sensor configuration. There is no device_class for these sensors.
HUP is probably what you call circulation_pump_heating, although it is also used for DHW through the use of a three-way valve.
VBO is what you call pump_flow, in my case the brine pump.
    - name: "VBO delta calculated"
      unique_id: "ait_vbo_delta_calculated"
      state: "{{ states('sensor.luxtronik2_unknown_calculation_239')|float / 10 }}"
      availability: "{{ states('sensor.luxtronik2_unknown_calculation_239') != None }}"
      unit_of_measurement: K
      state_class: measurement
      icon: mdi:delta
    - name: "VBO delta"
      unique_id: "ait_vbo_delta"
      state: "{{ states('sensor.luxtronik2_unknown_calculation_240')|float / 10 }}"
      availability: "{{ states('sensor.luxtronik2_unknown_calculation_240') != None }}"
      unit_of_measurement: K
      state_class: measurement
      icon: mdi:delta
    - name: "HUP delta calculated"
      unique_id: "ait_hup_delta_calculated"
      state: "{{ states('sensor.luxtronik2_unknown_calculation_242')|float / 10 }}"
      availability: "{{ states('sensor.luxtronik2_unknown_calculation_242') != None }}"
      unit_of_measurement: K
      state_class: measurement
      icon: mdi:delta
    - name: "HUP delta"
      unique_id: "ait_hup_delta"
      state: "{{ states('sensor.luxtronik2_unknown_calculation_243')|float / 10 }}"
      availability: "{{ states('sensor.luxtronik2_unknown_calculation_243') != None }}"
      unit_of_measurement: K
      state_class: measurement
      icon: mdi:delta

In the latest version of luxtronik these sensors are no longer unknown, so the division by 10 should no longer be needed.
            239: Kelvin("VBO_Temp_Spread_Soll"),
            240: Kelvin("VBO_Temp_Spread_Ist"),
            241: Percent2("HUP_PWM"),
            242: Kelvin("HUP_Temp_Spread_Soll"),
            243: Kelvin("HUP_Temp_Spread_Ist"),

Added to main, prerelease is coming.

See 2023.10.16-Beta

Thank you!

what does entity_registry_enabled_default mean?

HA Docs: entity#advanced-properties
Indicate if the entity should be enabled or disabled when first added to the entity registry. This includes fast-changing diagnostic entities or, assumingly less commonly used entities. For example, a sensor exposing RSSI or battery voltage should typically be set to False; to prevent unneeded (recorded) state changes or UI clutter by these entities.

Also, you have set invisible_if_value to 0.0 for these sensors, but a delta-T of 0 K is a valid measurement. So at least for SensorKey.PUMP_FLOW_DELTA and SensorKey.CIRCULATION_PUMP_DELTA that is not correct.
The SensorKey.PUMP_FLOW_DELTA_TARGET and SensorKey.CIRCULATION_PUMP_DELTA_TARGET seem to have the value 0 when the heat pump hasn't done a DHW or heating run yet after it has powered up. So I'm not sure using invisible_if_value is a good idea for these either.

You are right. I remove it.

Please try the latest prerelease: 2023.10.20-Alpha

Feel free to reopen if it is not fixed.


Update k8s to v0.30.3

This PR contains the following updates:

Package
Type
Update
Change

k8s.io/api
require
patch
v0.30.2 -> v0.30.3

k8s.io/apimachinery
require
patch
v0.30.2 -> v0.30.3

k8s.io/cli-runtime
require
patch
v0.30.2 -> v0.30.3

k8s.io/client-go
require
patch
v0.30.2 -> v0.30.3

k8s.io/kubectl
require
patch
v0.30.2 -> v0.30.3

Release Notes

kubernetes/api (k8s.io/api)
v0.30.3
Compare Source

kubernetes/apimachinery (k8s.io/apimachinery)
v0.30.3
Compare Source

kubernetes/cli-runtime (k8s.io/cli-runtime)
v0.30.3
Compare Source

kubernetes/client-go (k8s.io/client-go)
v0.30.3
Compare Source

kubernetes/kubectl (k8s.io/kubectl)
v0.30.3
Compare Source

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about these updates again.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

ℹ Artifact update notice
File name: go.mod
In order to perform the update(s) described in the table above, Renovate ran the go get command, which resulted in the following additional change(s):

1 additional dependency was updated

Details:

Package
Change

k8s.io/component-base
v0.30.2 -> v0.30.3

Pull Request Test Coverage Report for Build<PHONE_NUMBER>4
Details

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 55.442%

Totals

Change from base Build<PHONE_NUMBER>5:
0.0%

Covered Lines:
433

Relevant Lines:
781

💛  - Coveralls


Client name are not properly formated and alligned in client page

Describe the task
The client are available  having space before first word of their name

Also the client name are not sorted alphabeticaly.

The space is given if client has a parent compnay associated with it which is mentioned above client name in the records. Hence it is not a bug but functionality of client management


Update subscription.md

Hi Hayden
I'm starting to make a few changes as I go through. I haven't used GitHub extensively so please let me know if there's something I'm doing wrong.
Thanks!
Dario

Many thanks for your contribution!


Use event hub name as default checkpoint storage container name

Codecov Report

Merging #78 into master will increase coverage by 0.36%.
The diff coverage is 0%.

@@             Coverage Diff             @@
##             master     #78      +/-   ##
===========================================
+ Coverage     40.43%   40.8%   +0.36%
  Complexity      140     140
===========================================
  Files            57      57
  Lines           774     767       -7
  Branches         45      45
===========================================
  Hits            313     313
+ Misses          431     424       -7
  Partials         30      30

Impacted Files
Coverage Δ
Complexity Δ

...eam/binder/config/EventHubBinderConfiguration.java
0% <ø> (ø)
0 <0> (ø)
:arrow_down:

.../properties/EventHubExtendedBindingProperties.java
20% <ø> (+4.61%)
1 <0> (ø)
:arrow_down:

...gration/eventhub/DefaultEventHubClientFactory.java
0% <0%> (ø)
0 <0> (ø)
:arrow_down:

Continue to review full report at Codecov.

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