Improve speed of lockup queries

On our nodes, @Thunnini & @mattverse  noticed that "/osmosis.lockup.Query/AccountLockedCoins": and "/osmosis.lockup.Query/AccountLockedLongerDuration" have latency problems. They are taking an average of 0.36 and 0.2 seconds to query.
We need to look into whats taking so long. These queries should be fast as far as I understand, so theres probably some iteration that should be changed into a seek somewhere.

Seems to be the known IAVL & iterator problems upon investigation.


[X] I have pulled the latest main branch of the repository.
[X] I have searched for related issues and found none that matched my issue.

Overview
Let's say I have made a module call "sdl-codegen"- when you run setup things like your username, the npm org, any words in the kebab case package name etc
Mainly so there's less surprises when you try get it green for the first time
Additional Info

Yeah it's been annoying having to fill out assorted package names & such in each new package 😕. I want to say this is blocked on https://github.com/streetsidesoftware/cspell/issues/3215. Do you see any way around it @orta?

Add it to the cspell file in the repo, that's how I solved it locally

I use cspell paired with a custom script to populate the false position in a separate file as new dictionary.
Script - https://github.com/timelessco/node-ts-app/blob/main/package.json#L46
Custom dictionary file - https://github.com/timelessco/node-ts-app/blob/main/project-words.txt
Dictionary file added to the cspell config - https://github.com/timelessco/node-ts-app/blob/main/cspell.json#L22

OK! Coming back to this: I've learned a good bit about cspell in the meantime and thought on the issue. I think it's different depending on how you're running CTA:

"Creation" and "Initialization" modes: this issue absolutely applies. No words in your provided options -description, title, logo alt, etc.- should be reported. Anything that would be should be added to your cspell words
"Migration" mode: the exemptions for options still apply, but not for the rest of the repo. If you have existing typos then they should be reported.

OK! Coming back to this: I've learned a good bit about cspell in the meantime and thought on the issue. I think it's different depending on how you're running CTA:

"Creation" and "Initialization" modes: this issue absolutely applies. No words in your provided options -description, title, logo alt, etc.- should be reported. Anything that would be should be added to your cspell words.
"Migration" mode: the exemptions for options still apply, but not for the rest of the repo. If you have existing typos then they should be reported.

https://github.com/JoshuaKGoldberg/cspell-populate-words is my own script that adds in missing words. It's got references of using the cspell API. I'll integrate it into create.

@all-contributors please add @orta for ideas.

🤖 Beep boop! This comment was added automatically by all-contributors-auto-action.
Not all contributions can be detected from Git & GitHub alone. Please comment any missing contribution types this bot missed.
...and of course, thank you for contributing! 💙

Hmm, this is tough. The main cspell APIs are all generally asynchronous. I'm poking around in the internal checkText -> checkTextDocument -> DocumentValidator::prepare() and there's a lot of async work to read in dictionaries and such. This will need to be asynchronous.
The only way to do that in the new Blocks system is with a scripts entry. I'll have that be the implementation.


Cluster-wide setting for underpinned threshold

we should make the underpinned value an environment variable so that we can increase/decrease the redundancy easily.
Originally posted by @MSevey in https://github.com/SkynetLabs/pinner/pull/2#discussion_r856472538
Proposal
As we want this to be a cluster-wide setting, we cannot use an environment variable for it because each server will have its own value and they will need to do a complicated negotiation in order to decide on a common, cluster-wide number.
That's why we should add a configuration or settings collection in Mongo and use that to store all cluster-wide settings, similar to what we do in accounts when we need to disable registrations on a given cluster.

/linear

https://linear.app/skynetlabs/issue/SKY-279/cluster-wide-setting-for-underpinned-threshold


No arm release?

Hi @dberuben,
we have arm for linux and macos. Do you need an arm release for windows?

Hi @tuunit
I did a helm plugin install https://github.com/seacrew/helm-compose and i had an error saying that arm package doesn't exist  ... then i realize that package was present in the release section

Hi @dberuben,
can you reproduce the error and share it here? Which OS are you using? I would like to analyze the issue so helm Plugin install works as well.

Yes sure
helm plugin install https://github.com/seacrew/helm-compose
No prebuild binary for macos-arm64.
Failed to install helm-compose
\tFor support, go to https://github.com/seacrew/helm-compose/helm-compose.
Error: plugin install hook for "compose" exited with error

packages are present 🤔
(☸|lspay-trial-eu-west-1:datadog)➜  plugins ls -la
total 0
drwxr-xr-x   4 dberuben  staff  128 Aug 28 13:55 .
drwxr-xr-x   3 dberuben  staff   96 Oct 21  2022 ..
drwxr-xr-x  20 dberuben  staff  640 Aug 28 13:55 helm-compose
drwxr-xr-x  23 dberuben  staff  736 Oct 21  2022 helm-diff
(☸|lspay-trial-eu-west-1:datadog)➜  plugins pwd
/Users/dberuben/Library/helm/plugins

helm version
version.BuildInfo{Version:"v3.9.4", GitCommit:"dbc6d8e20fe1d58d50e6ed30f09a04a77e4c68db", GitTreeState:"clean", GoVersion:"go1.19"}

MacOS 13.5

Hi @dberuben,
I found the issue:
https://github.com/seacrew/helm-compose/commit/940c9229817b782c5f7493538bb9c247bb5f42b4
If you have the time please try to uninstall and install once more :)
As I currently don't have direct access to a Mac I would highly appreciate any other feedback you have and if you find a bug. Please feel free to raise a issue asap.

Fixed 🚀
(☸|lspay-trial-eu-west-1:datadog)➜  plugins helm plugin install https://github.com/seacrew/helm-compose
Downloading https://github.com/seacrew/helm-compose/releases/latest/download/helm-compose-macos-arm64.tgz
Preparing to install into /Users/dberuben/Library/helm/plugins/helm-compose
helm-compose installed into /Users/dberuben/Library/helm/plugins/helm-compose
Installed plugin: compose


Revert "Merge pull request #899 from Homebrew/formula_detect_cask"

This PR reverts PR #899 which fixed issue #897.
The cause of #897 was later identified as coming from Homebrew/brew itself, and has been fixed in

https://github.com/Homebrew/brew/pull/15150

Thus in homebrew-test-bot here #899 can be safely reverted.

Thanks for cleaning up, great work again @muzimuzhi!


logout not working

When I logout a user on facebook they are automatically logged in every time in facebook afterwards, never prompted again.
adapter.getCurrentProvider().logout(); <--doesn't work

Yes, none of the below work:

adapter.getCurrentProvider().logout();
boolean signOutResult = adapter.signOut(thisContext, SocialAuthAdapter.Provider.LINKEDIN.name());


Resolve state management bug

This fixes #54 with the following changes:

Improve form validation so user is informed if name field is incorrect
Fix logic so that state of default parent selection matches what's shown in the UI
Add toast messages for success/failure of breeding transaction (was no feedback before)
Disable persistence of redux store that was leading to stale data being used
Improve feedback in UI for kitty list loading and error states (search and My Kitties pages)

Hi @nrutledge  and @AltiMario ,
I conducted multiple tests and successfully completed breeding operations several times. Based on my findings, I can summarize the results as follows:
Summary:

Web Server: No issues detected.
Blockchain Operations: No issues detected.
DApp (JavaScript Code): Several issues identified.

Issues Identified:
1. Outdated Kitty Data in DApp: The JavaScript code retains old kitties and doesn't refresh when the application is started, even though the web server provides the updated list of kitties.

Incorrect DNA Used in Breeding: During breeding, the JavaScript code uses the DNA of an old kitty instead of the selected one. This issue was confirmed through logs from the web server, which indicated that the correct values were shown in the DApp, but incorrect values were sent during the breed operation.

Workarounds:
Issue 1: Outdated Kitty Data in DApp
Problem: The DApp displays old, deleted kitties in the "Search Kitty" and "My Kitty" pages.
Workaround:

In the linux terminal, navigate to "/tmp/tuxedo-wallet".
Run the command: "rm -rf wallet_database" to remove the old kitties from the web server's database.
Create new "Dad" and "Mom" kitties as outlined in the TuxedoDapp Testing Guide.
Click on "Search Kitty" to view the updated listing the DApp , which will now only include the newly created kitties.
Note: Creating new kitties is necessary to refresh the list in the current DApp, as it doesn't refresh the existing list.

Issue 2: Incorrect DNA Used in Breeding
Problem: The DApp caches old kitty DNA, causing errors during breeding. An alert may display "Error breeding kitty: Cannot read properties of null," indicating that the DApp is sending outdated DNA to the web server, which then rejects the operation because the DNA doesn't match any entries in the database.
Workaround:

Go to "Search Kitties." in DApp
Select the "Mom" kitty. i.e click on that which will lead to kitty detail page.
Click on the "Breed" button at the bottom
Attempt to select the "Dad" kitty from the dropdown.
Enter the name of the child kitty.
Click on the "Breed." button
If you receive the error "Error breeding kitty: Cannot read properties of null," proceed to the next step.
Return to "Search Kitty."
This time, select the "Dad" kitty.
Then select the "Mom" kitty from the dropdown.
Enter the name of the child kitty.
Press "Breed." button This time, the Talisman wallet should appear for signing the transaction.

I believe the above steps will resolve the issues related to the DApp caching old kitty details.
Here basically JS will send the correct dnas of mom and DAD kitties to web server which are selected for breeding.
Below are some of the screen shots which were taken in during this testing '
Error due to wrong DNA

Success full breeding Case 1

Success full breeding Case 2

**Make sure Talisman wallet is connected always: **

If you find issues in testing, I can be available for assistance. Please book a meeting slot with me. I can show you the demo.

@NadigerAmit thank you for investigating and providing additional details. I've made additional changes based on that and have been able to successfully breed kitties on my end.
That being said, I was not able to fully reproduce the first issue (outdated kitty data in DApp) that you mentioned. The parent DNA was indeed stale due to unnecessary persistence of what should be transient form data. However, the kitty list was being reloaded and replaced with the response from the server after each load/refresh (despite it also being persisted). The only case where this was not true, was if the server responded with an error / no results.
Anyway, none of this should be an issue anymore with the latest changes.

Hi @nrutledge
CC: @AltiMario
Thank you for resolving the issues. I tested the updated DApp code, and I'm happy to report that both previously mentioned issues have been addressed. This is a big relief and has made testing much easier.
However, I noticed one minor issue:
When attempting to breed using a Mom Kitty with the status "HadBirthRecently" and a Dad Kitty with the status "Tired," the transaction status incorrectly shows "Kitty Breed successfully." While the transaction is indeed sent, it is correctly rejected by the blockchain due to the kitties' statuses, and no new child kitty is created. This behavior is as expected, but the messaging could be clearer.
Since the blockchain sends the failed transaction status asynchronously to the web server, which then relays it to the DApp, we have a few options to improve this:
Options to Address the Issue:
Option 1: Simple Fix
Update the message from "Kitty Breed successfully" to "Kitty Breed transaction sent successfully."
This provides a more accurate description of the transaction status.
Option 2: Moderate Complexity

Update the message to "Kitty Breed transaction sent successfully."
Additionally, listen for the REST API return value. If the transaction fails, display "Transaction failed." If successful, display "Kitty Breed successfully."

Option 3: Moderate Complexity

Have the DApp validate the kitties' statuses before calling the REST API. Specifically, check that the Mom Kitty's status is not "HadBirthRecently" and the Dad Kitty's status is not "Tired." If either condition fails, do not call the REST API and display an appropriate message to the user.

Note: This last option may not be ideal, as there could be many invalid transactions, and having the DApp check all conditions could be resource-intensive and prone to errors due to stale data.
PFA some of the screen shots taken when issues occoure '

When invlid transactions are sent from the Dapp , it shows  "Kitty Breed successfully"

Blockchain error due to invalid txn '

Weservioce error, since blockchain returned error :

Custom error: 0

I didn't follow the whole conversation, but I wanted to let you know that if you use a newer version of Tuxedo, you will get a more specific a descriptive error. I improved this in https://github.com/Off-Narrative-Labs/Tuxedo/pull/214

@nrutledge
cc: @AltiMario
Thank you for fixing .
All the above counter measures the problem mentioned looks ok to me and it should be ok to follow the test guide without issues.

Hi @NadigerAmit and @nrutledge I did a test following the instructions from scratch and step by step. The breading issue is fixed but I cannot edit (for the scope of trading) the kitties. Here is the video to show the problem:
Edit-kitty.webm
The only errors in the log are these

My local tools:
node 22.7
rust 1.78.0
yarn 1.22.22
Am I doing something wrong?


Bellatrix Acceptance Test

Description
We should have acceptance tests that checks teku behaviour with Bellatrix is activated, ideally going through the transition block.
We could think about adding complexity by test several scenarios (ie. optimistic sync)
An option is to have extended AT by running a fixed besu client version capable of running as EL.
Another option is to start using kurtosis.
https://docs.kurtosistech.com/
https://github.com/kurtosis-tech/eth2-merge-kurtosis-module
Pari is already running it daily to check various client compatibility:
https://github.com/parithosh/nightly-kurtosis-test/blob/main/.github/workflows/kurtosis.yml
https://github.com/parithosh/nightly-kurtosis-test/actions
additional examples:
https://notes.ethereum.org/@ExXcnR0-SJGthjz1dwkA1A/H11OzhRAK

This would actually be an acceptance test in our terminology as it would be end-to-end.

What tests could be done next:

optimistically pass merge after safe slots (blocked with re-execution issue, see #5914)
switch from optimistic sync to normal, blocked by Besu bug
https://github.com/hyperledger/besu/issues/3988

Though both blockers are merged we couldn't yet finish this until https://github.com/hyperledger/besu/issues/3988 is included in release, so we could update Besu version used in acceptance tests. When this fix reaches release, we will need to add to OptimisticSyncPostMergeAcceptanceTest and OptimisticSyncSafeSlotsAcceptanceTest logic to enable sync with disconnected execution client and wait for non-optimistic block


ISPN-14313 Set different properties and port for cross-site testdriver

https://issues.redhat.com/browse/ISPN-14313

Merged, thanks


[v0.12.x] [Unmaintained branch] Disable Flatcar auto-updates

This a patch we added in our side other may benefit from. Feel free to reject as I know well is unmaintained.

We'll accept, thanks for the contribution.


Why does CovPass (not CovPassCheck) require internet/network access?

The app itself reads the QR from the certificate and also displays this QR code. Why does it need internet/network access for this? I am not talking about CovPassCheck, which obviously DOES need internet (at least from time to time to check the validity of issuer's certificates).

I second that question and additionally would like to know why the CovPass app requires the rights to "run at startup" and "deactivate sleep mode" (on android).
It's not answered in the technical details or the FAQ and using a search engine produces too much white noise.
Word cloud: covpass android app berechtigungen why warum

CovPass and CovPassCheck both need internet access to update the local trust list which is required for the signature validation. We do not accept certificates with an invalid signature. In those cases the CovPass app will show an error and does not save the certificate on the device, and the CovPassCheck app will show an error result view.

Thx for the insight. Since the paper-based QR-code can still be used (or used in CWA, which doesn't check trust list) even if the trust for a certificate has become invalid, wouldn't it be sufficient if the trust list was only updated in the CovPassCheck-App? Instead, you could still update the list in CovPass by integrating it with regular app updates.
I do understand that CovPassCheck-App does need an internet connection for that purpose.

We use Android's WorkManager to update the trust list in the background once every day, so even if you're offline you're pretty much guaranteed to have an up-to-date trust list. The Android WorkManager docs provide more detail about the required permissions:
 WorkManager uses the following permissions:

    android.permission.WAKE_LOCK to make it can keep the device awake to complete work before API 23
    android.permission.ACCESS_NETWORK_STATE to listen to network changes before API 23 and monitor network Constraints
    android.permission.RECEIVE_BOOT_COMPLETED to listen to reboots and reschedule work properly.

thx @wkornewald, I am just saying it wouldn't be necessary to update the trust list in CovPass in-app. It would work fine without it, since evaluation is done with CovPassCheck. It would be sufficient to update the trust list through regular app updates over the app stores. No network permission would be needed for the CovPass-App.

The other question whether CovPass should even validate the scanned QR code at all is a trade-off of helping the user to avoid mistakes vs. not requiring these permissions. Countries can revoke certificates and having the feedback that the validation will indeed succeed and you won't be denied at the entrance is a UX improvement and also it makes manipulation slightly more difficult.
Now you can debate that it's more important to not use these permissions, but on the other hand you can see in the source code that these permissions are only used in good faith.

Agreed. Also, I didn't see that you finally published the source 👍.

Hi all :) Has the question been resolved?


Implement a Function to Check Even or Odd

Issue Title: Create a function to check if a number is even or odd
Description: Write a Python function that takes an integer as input and returns whether the number is even or odd.
You have to code in Python Folder

@Jadu07  can you leave this issue to me

Please assign me this issue . I would like to contribute .


refactor: control project preview with challenge property

feat: add demoType to relevant challenges
feat: control preview via demoType
tools: update project helper to create property

Checklist:

[x] I have read and followed the contribution guidelines.
[x] I have read and followed the how to open a pull request guide.
[x] My pull request targets the main branch of freeCodeCamp.
[x] I have tested these changes either locally on my machine, or GitPod.

This removes the awkward logic from the client and, instead, means the project creator can choose if they want to show the final project or not.
Also, labs will soon let learners see the demo inside the client and this PR lays some of the groundwork for that.

@freeCodeCamp/mobile I assume adding a property is fine, but could you confirm?

What if we want to show the workshop preview on demand as well - like a button on all the steps.

If we decided that all the labs and workshops should behave the same way, we can probably remove this code. There's not much logic that relies on the demoType, so it shouldn't be hard to remove.

https://github.com/freeCodeCamp/freeCodeCamp/pull/55569 has diverged a little, so it doesn't seem helpful to keep this around any more.


updated login page now its visible

before the login page was not visible and elements were going out
but now its visible and also inside the box.

I will merge this because it is a good fix, but an issue needs to be created first next time. Then, when you complete the pr, link the issue in the template.


add fraction symbols

#12
It's all fraction symbols Unicode supports, except ↉.

Why not ↉?

Why not ↉?

Is it common? Do you use it?

I never use any of these, so wouldn't know. Seems it's mostly just used for baseball scoring, so we can just leave it out.

Thanks :)


AMAZING! I cant seem to get the URL scheme to work for me

Hi and thx so much for your amazing work, been using awful hacks (using apple shortcuts..) to get something similar to your quick capture method, but this seems so much better! :)
I am pretty bad at programing though (sorry!) and cant seem to get the URL scheme option to work
this works well
obsidian://create-task

opening the modal input window
yet when I try your example for also putting in the task name
obsidian://create-task&task-description=Do%20stuff

nothing seem to happen
im sure im missing something right? would you mind giving example code for that?
thx so much!!

Thank you for the positive feedback @zeltak
Regarding your issue:
It seems that you are missing the questionmark (? )in front of your parameters.
The correct URL would be
obsidian://create-task?task-description=Do%20stuff

Notice the questionmark (?) instead of the ampersand (&).
The first parameter must be prepended with a questionmark. All following parameters must be prepended with an ampersand.

that would indeed be great :D


VueQL

I'd like to see a Vue and GraphQL combo. So, this is a request for a module, which would basically connect GraphQL and Vuex together. http://graphql.org/
Another possibility is to connect Vuex with Apollo-client. https://github.com/apollostack/apollo-client
A couple of discussions I've already started.
https://github.com/apollostack/apollo-client/issues/143
https://github.com/vuejs/vuex/issues/18
Scott

What do you think about this?
https://github.com/Akryum/vue-apollo
Discussion thread
https://github.com/Akryum/vue-apollo/issues/140

I know about it. Thanks. Found out about it after I wrote this. 😄
Scott


Remove unnecessary whitespace

There's a space after a } in styles.css of foundations/06-cascade-fix

@Filip-Tomasko I appreciate you wanting to contribute, but I don't believe that this is a significant change that needs to be merged. If the whitespace had a negative affect anywhere I would merge this, but because it doesn't I will be closing without merging.
If you are looking to contribute more, please check out our issues in this or some of our other repos :)


layout of coordinates on hex grids isn't great

It's not just "not great", it's bad. I think it's from API changes since Foundry 8 & 9. I'm going to disable coordinates on hex grids temporarily until I can fix this. This will let me release a square grid v12 version ASAP.

removed 'in progress' label because the branch from the old repo had no commits so I deleted it. Not ready to work on this yet.


Calculate distance for all flights

Is your feature request related to a problem? Please describe.
I have to go through and manually calculate the distance for individual flights
Describe the solution you'd like
A button on the maintenance page, like the one on PHPVMS5 that calculates the distance for every flight
Describe alternatives you've considered
Additional context

Thanks, I've added this to the roadmap


Idea: Design and implement a "private wallet data transfer file" format

There is a maybe surprisingly large number of things that a wallet stores for you that are bound to the wallet files themselves: Lose those files, lose the data.
I call this private wallet data in the following, as a "working title" - maybe we will find a better term if the idea gains traction.
If you restore the wallet from the blockchain using your seed, you get all the most important info back of course, like the list of transactions, enotes, and amounts, but not the following:

destination addresses of outgoing transactions
transaction secret keys
maybe subaddresses and accounts that you "allocated" in your wallet but never used

You also lose names and labels you set for various things like accounts, subaddresses or the wallet as a whole, your address book, your settings, and other things, where it's probably a lot less surprising that those won't restore from the blockchain but where it still can be a pain to configure it all again.
Even without losing wallet files outright you may run into problems when switching wallet apps because for some types of apps it's hard and/or complicated to copy wallet files in order to use them with full data intact. I have mostly smartphone apps in mind here.
This finally leads me to the idea: We design a new file format that makes transporting all that "private wallet data" between Monero wallet apps as easy as possible. The "core wallet" supports/implementes the file format to make it as easy as possible for wallet app writers to offer it as a feature in their UI, with the aim to achieve broad support.
I imagine a textual format in Base64 encoding because that's easy to cut and paste. Users could store the data alongside seeds e.g. in password managers.
A wallet app would basically only need a simple screen with one input field to allow users to paste the string to support this feature.
The basic approach is of course nothing new, it's already used for transporting multisig key data , key images, transactions for cold-signing, and similar.
Encrypting the data with any of the available secret keys wouldn't be hard.
If the full data turns out to be too large to handle for larger wallets, maybe offer the user a number of checkboxes when creating the file to specify exactly which data to include to keep the size under control.

This seems a very important thing to have. May I suggest though that this format be designed in a modular way so as to allow the creation of wallet files which may contain only a subset of the infos. This would allow for scenarios where you want to export the list of accounts for example but not the tx private keys, or vice-versa.
It will also be important to be able to load multiple wallet files into a wallet software, for example to consolidate tx keys for transactions which were initiated from different wallets.


Improve Thanos Querier documentation

Here are the list of question which was actually asked in our internal forum, it would be great if these gets covered in the Querier documentation.
Q1. How does Thanos Query show the user the same metric values from the two Prometheus?
Q2. How does Thanos Query detect Prometheus anomalies when one of the Prometheus does not have the correct metrics?
Q3. Is Thanos Querier letting Prometheus do the query operations and get only the result of query operations from Prometheus, or is Thanos Querier getting only the metrics data from Prometheus and doing the query operation by Thanos Querier's own self? How the query handles calculation? For example. when the query returns an average, does Thanos Querier get raw data from Prometheus and calculate the average or Thanos Querier asks Prometheus to calculate it and simply return that data?
Q5. For time width queries like avg_over_time, is the Thanos Querier query result correct even if each of the metrics data obtained from the redundant Prometheus contains outliers or missing values? Will deduplicate solve that well?
For example: Assume that OTA update is in progress. During the update, nodes and Prometheus instances need to be restarted. Prometheus could not scrape metrics during the restart so one instance does not record a value while the other will do (because just one node is restarted at a time).
Here's an explanation figure, where x is a downtime and when Prometheus didn't record a correct value:
Prometheus-0 --xxxxxx-------------
Prometheus-1 -----------xxxxxxxx--
Then, assume that someone would like to know whether the update affected the application performance so use Thanos Querier to get an average value of CPU usage during the update.
Under this scenario, both of the Prometheuses have incorrect values, but does Thanos Querier understand which data is correct at each time point and return the correct average?
cc: @bwplotka

Thanos, Prometheus and Golang version used:

Object Storage Provider:
What happened:
What you expected to happen:
How to reproduce it (as minimally and precisely as possible):
Full logs to relevant components:

Anything else we need to know:

Fixed here:https://github.com/thanos-io/thanos/pull/5305


Give simple SendCommand another go...

... once built-in delay is available.

With increased delays one can use SendCommand instead of SendKeyPress, however SendKeyPress allows for shorter delays and thus faster response.


data.zip

Hi,
Like the work!
I an wondering if the data will be released like the annotations?
Another question: in the code, each item from the dataloader has only 1 question paired with a video for the NLQ task (before batching). Does the codebase supports grounding multiple questions within a video? Thanks.

Thanks for your questions.
A1: The data has already been released on Huggingface.
A2: Grounding multiple questions is not supported.


Use raw string for docstring that contains a backslash

Python 3.12 started to complain about invalid escape sequences. https://docs.python.org/dev/whatsnew/3.12.html#other-language-changes
One supposed to use r""" when dostrings contains backslashes """ https://stackoverflow.com/a/33734332

Thanks, Chuck.
Would it be possible to cut a new patch release?

@alexbozhenko Unfortunately, I do not have the ability to cut a release. I pinged some folks at Google to try and cut a patch release.

I'll include this in the 0.10.1 release.


Fix ci

Lost in merge: upgrade test https://github.com/mesosphere/dcos-commons/pull/294

@mesosphere-ci: retest this please

@mesosphere-ci: retest this please

@nickbp: Working on the lost upgrade test in another PR.  Trying to unblock all PRs now.


How can I use the plugin with Angular 4 in my Ionic 3 project?

I already installed the plugins videojs-wavesurfer (npm install videojs-wavesurfer --save) and wavesurfer.js (npm install wavesurfer.js --save) and now I want to use them in my Ionic 3 component.
I was working only with Video.js, and all it working fine. But now, I need to add videojs-wavesurfer plugin.
I tried:
Component.html:
<audio class="video-js vjs-default-skin" controls #audio>
    <source [src]="audioSource" type="audio/mp3">
</audio>

Component.ts:
import videojs from 'video.js';
import WaveSurfer from 'wavesurfer.js';
import VideojsWavesurfer from 'videojs-wavesurfer';

let audioJS = videojs(this.audio,
    {
      fluid: true,
      plugins: {
        wavesurfer: {
          src: this.audioSource,
          msDisplayMax: 10,
          debug: true,
          waveColor: 'grey',
          progressColor: 'black',
          cursorColor: 'black',
          hideScrollbar: true
        }
      }
    }, () => {

    });

But console prints the following error:

ERROR Error: plugin "wavesurfer" does not exist

So, I changed the code to:
import videojs from 'video.js';
import WaveSurfer from 'wavesurfer.js';
import VideojsWavesurfer from 'videojs-wavesurfer';

let audioJS = videojs(this.audio,
    {
      fluid: true,
      plugins: {
        VideojsWavesurfer
      }
    }, () => {

    });

And apparently recognized the plugin, but now I get this error:

Uncaught Error: Cannot find module "WaveSurfer"

How can I fix it?

Sorry for the late reply @IgorSamer. Take a look at https://github.com/collab-project/videojs-wavesurfer/wiki/Webpack
I would change your imports to:
import videojs from 'video.js';
import WaveSurfer from 'wavesurfer.js';

/*
// this is only required when you're using the videojs-wavesurfer 'live' mode
// with the microphone plugin
import MicrophonePlugin from 'wavesurfer.js/dist/plugin/wavesurfer.microphone.js';
WaveSurfer.microphone = MicrophonePlugin;
*/

// register videojs-wavesurfer plugin with this import
import Wavesurfer from 'videojs-wavesurfer/dist/videojs.wavesurfer.js';


Is auto-release a good idea?

Currently, we auto-release at each commit to main.
We also have adjusted it from the default:
on:
  push:
    branches: ['main']

This seems a bit "too much" for me. I'd like to control when to make a new release. E.g. collect a few bug fixes, then release. The auto semantic versioning can then still determine the correct version number. This would also might allow us to sync Milestone names and releases again (depending on the correct usage of feat/fix prefixes in commit messages).
I checked a few other projects similar to superwerker and all of them also don't seem to have auto-release set on, so I think we should follow this good practice:

AWS CDK
Org-formation
ADF

Additional info:

Intro article to semantic-release (has no auto-release as well).

super-eks uses a manual GitHub Action to trigger a new release. This works fine as well:
on:
  workflow_dispatch: {}

https://github.com/superluminar-io/super-eks/blob/main/.github/workflows/release.yml

thx @sbstjn - since you initially introduced the auto-release mechanism, I'd like to know your opinion on auto-release vs manual release as well. What do you think?

I guess, it depends on the purpose of a release/version.

If you want to use a release/version as a tool for communication, we might switch to a manual trigger
if you want to use a release/version as a point-in-time identifier, we can keep the automated workflow

With the current flow, a major release requires a "BREAKING CHANGE" commit message. Basically, 0.x.y is handled automatically, 1.0.0 needs a special commit message and afterwards 1.x.y is handled automatically again. I do not know if we care about manual triggers for 0.2.3 and/or 1.0.0 🤷♀ 🙈
Shall we just flip a coin? :)

Thanks for the feedback.

I guess, it depends on the purpose of a release/version.

I want to be able to accumulate several changes / PRs into one release with one release number, as other projects do.

If you want to use a release/version as a tool for communication, we might switch to a manual trigger

Not only for communication but also for simplification for:

Announce on the mailing list / slack etc pp for every new release.
Push changes upstream to Quickstart.

if you want to use a release/version as a point-in-time identifier, we can keep the automated workflow

That's a commit-hash for me :) I am not yet ready for cattle releases :)
So I would propose to move to a manual trigger-based release workflow, e.g. with a GitHub action, and we still let the semantic-release determine the correct semantic version number.

So I would propose to move to a manual trigger-based release workflow, e.g. with a GitHub action, and we still let the semantic-release determine the correct semantic version number.

I favor this approach as well


API integration tests broken by 1.3.0

It looks like systemweb adapters 1.3.0 breaks all our integration tests, testing Controller-based API's, using XUnit (latest version) with its IClassFixture and appling WebApplicationFactory and still using .NET 6. With systemweb adapters 1.2.0 all tests were green, with 1.3.0 at most one test is green, the rest fails. Running each test separately has the test always succeed.
The tests consistently fail with the following error:
Message:
System.ObjectDisposedException : Cannot access a disposed object.
Object name: 'IServiceProvider'.

  Stack Trace:
ThrowHelper.ThrowObjectDisposedException()
ServiceProvider.GetService(Type serviceType, ServiceProviderEngineScope serviceProviderEngineScope)
ServiceProvider.GetService(Type serviceType)
ServiceProviderServiceExtensions.GetRequiredService(IServiceProvider provider, Type serviceType)
ServiceProviderServiceExtensions.GetRequiredService[T](IServiceProvider provider)
WebApplicationFactory`1.ConfigureHostBuilder(IHostBuilder hostBuilder)
WebApplicationFactory`1.EnsureServer()
WebApplicationFactory`1.CreateDefaultClient(DelegatingHandler[] handlers)
WebApplicationFactory`1.CreateDefaultClient(Uri baseAddress, DelegatingHandler[] handlers)
WebApplicationFactory`1.CreateClient(WebApplicationFactoryClientOptions options)
WebApplicationFactory`1.CreateClient()
SuperSimpleTests.TestWhatever_WithoutCondition_DoesWhatever() line 19
--- End of stack trace from previous location ---

This seems to suggest somehow the TestServer instance is being disposed at an unfortunate moment.
This even happens for a test as simple as (and seemingly totally isolated from the other tests)...
public class SuperSimpleTests : IClassFixture<WebApplicationFactory<Program>>
{
    private readonly WebApplicationFactory<Program> _factory;

    public SuperSimpleTests(WebApplicationFactory<Program> factory) => _factory = factory;

    [Fact]
    public async Task TestWhatever_WithoutCondition_DoesWhatever()
    {
        //  Arrange
        var client = _factory.CreateClient();

        //  Act
        var response = await client.GetAsync("/");

        //  Assert
        response.StatusCode.Should().Be(HttpStatusCode.NotFound);
    }
}

...when this is made part of the set of API tests.
All our main API tests follow the main construction for accessing a client as follows:
var client = _factory.WithWebHostBuilder(
   builder =>
   {
       builder.ConfigureTestServices(services =>
       {
            // Add or replace some services...
       });
       builder.UseConfiguration(new ConfigurationBuilder()
                                            .AddJsonFile(AppsettingsTestJson)
                                            .Build());
   }).CreateClient(new WebApplicationFactoryClientOptions { BaseAddress = _address });

whereby the error obviously pops up at the CreateClient() call.

Can you share an example repro? The stacktrace alone is not giving enough info to pinpoint anything specific.
Between 1.2 and 1.3, the lifetime of a couple of things that were per-request were moved to be per-host to better mimic ASP.NET Framework behavior. For example, HttpRuntime and HostingEnvironment APIs, so maybe something there is causing this?
For reference, this is how we recommend testing it with the TestServer tools: https://learn.microsoft.com/en-us/aspnet/core/migration/inc/unit-testing. I have not tried it with the WebApplicationFactory pattern.

Hi Taylor,
In relation to the above referred issue earlier reported by me: we managed to reproduce the issue in an isolated fashion. What is the best way to forward it to you?
BTW
Is there any interest from your (i.e., Microsoft) side to restart the monthly Wednesday discussion with you and John? It stopped last year well before the Season Holidays and was never started up again afterwards.
Rens Segaar
Senior Software Engineer
@.***
Molengraaffsingel 33, 2629 JD Delft
The Netherlands
T +31 (0)15 - 711 51 00
<EMAIL_ADDRESS>www.exact.comhttps://exact.com/
Follow us LinkedInhttps://www.linkedin.com/company/exact | Twitterhttps://twitter.com/exact_NL | Facebookhttps://www.facebook.com/ExactWorld/ | Youtubehttps://www.youtube.com/user/Exacttv | Instagramhttps://www.instagram.com/exact/
@.***
DISCLAIMER
The information in this e-mail message is privileged and confidential and is only intended for the addressee. If you received this e-mail in error, you are hereby notified that any disclosure, reproduction, distribution or use of this message and any attachments is strictly prohibited. Please notify the sender immediately and delete the e-mail without copying or disclosing its contents to any other person. No legal consequences can be derived from the contents of this e-mail. Neither the sender nor Exact Holding B.V. (or any of its related companies) accept liability for any damage resulting from the use and/or acceptance of the content of this e-mail message.
Please consider the environment before printing this message.
From: Taylor Southwick @.>
Sent: Tuesday, January 9, 2024 03:32
To: dotnet/systemweb-adapters @.>
Cc: Rens Segaar @.>; Author @.>
Subject: Re: [dotnet/systemweb-adapters] API integration tests broken by 1.3.0 (Issue #462)
CAUTION: This e-mail is sent from an external email address. Please do not open attachments or click links from an unknown or suspicious origin. If you have any questions or concerns, please contact the IT Services team
Can you share an example repro? The stacktrace alone is not giving enough info to pinpoint anything specific.
Between 1.2 and 1.3, the lifetime of a couple of things that were per-request were moved to be per-host to better mimic ASP.NET Framework behavior. For example, HttpRuntime and HostingEnvironment APIs, so maybe something there is causing this?
For reference, this is how we recommend testing it with the TestServer tools: https://learn.microsoft.com/en-us/aspnet/core/migration/inc/unit-testing. I have not tried it with the WebApplicationFactory pattern.

Reply to this email directly, view it on GitHubhttps://github.com/dotnet/systemweb-adapters/issues/462#issuecomment-1882224766, or unsubscribehttps://github.com/notifications/unsubscribe-auth/BB2FIZE6AHC2UNMQWBEKWHLYNST3FAVCNFSM6AAAAABBFQ7DMOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQOBSGIZDINZWGY.
You are receiving this because you authored the thread.Message ID<EMAIL_ADDRESS>


mention the documentation license

Test name
Status

big-data
passed

storage
passed

haproxy
passed

scaling
passed

recreate
passed

upgrade-haproxy
passed

init-deploy
passed

self-healing
passed

restore-to-encrypted-cluster
passed

upgrade-proxysql
passed

scaling-proxysql
passed

limits
passed

monitoring-2-0
passed

self-healing-advanced
passed

demand-backup
passed

smart-update
passed

affinity
passed

one-pod
passed

operator-self-healing
passed

auto-tuning
passed

proxysql-sidecar-res-limits
passed

pitr
passed

users
passed

demand-backup-encrypted-with-tls
passed

security-context
failed

tls-issue-self
passed

tls-issue-cert-manager
passed

scheduled-backup
failed

tls-issue-cert-manager-ref
passed

validation-hook
passed

upgrade-consistency
failed

commit: https://github.com/percona/percona-xtradb-cluster-operator/pull/806/commits/4fbf49907c438ca4a536ef0bb0afa0518c5af8b8
image: perconalab/percona-xtradb-cluster-operator:PR-806-4fbf4990


[book] is it ok that builtin criteria can't "imply" other criteria?

You can have your custom criteria imply the builtins (so you can have stronger criteria), but I don't currently see a way to have custom criteria be "implied by" the builtins (so you can have weaker criteria).
Unclear if this matters / is intentional, but it's a weird asymmetry I figured I'd mention in case you hadn't thought about it.

Good point. Would it be trivial in our current implementation to introduce a companion implied-by to support edges in the other direction? We could defer actually implementing it until someone needs it.


Expand ~ to $home on Windows with tab completion

PR Summary
https://github.com/PowerShell/PowerShell/pull/19489 added some improvements to tab-completion, but one side effect is that on Windows, a ~ is retained instead of being expanded.  Since ~ is not understood by native commands, this breaks many use cases.
This change only retains ~ on non-Windows systems.
PR Context
Fix https://github.com/PowerShell/PowerShell/issues/20750
PR Checklist

[x] PR has a meaningful title

Use the present tense and imperative mood when describing your changes

[x] Summarized changes
[x] Make sure all .h, .cpp, .cs, .ps1 and .psm1 files have the correct copyright header
[x] This PR is ready to merge and is not Work in Progress.

If the PR is work in progress, please add the prefix WIP: or [ WIP ] to the beginning of the title (the WIP bot will keep its status check at Pending while the prefix is present) and remove the prefix when the PR is ready.

Breaking changes

[x] None
OR
[ ] Experimental feature(s) needed

[ ] Experimental feature name(s):

User-facing changes

[x] Not Applicable
OR
[ ] Documentation needed

[ ] Issue filed:

Testing - New and feature

[ ] N/A or can only be tested interactively
OR
[x] Make sure you've added a new test if existing tests do not effectively test the code changed

Tooling

[x] I have considered the user experience from a tooling perspective and don't believe tooling will be impacted.
OR
[ ] I have considered the user experience from a tooling perspective and opened an issue in the relevant tool repository. This may include:

[ ] Impact on PowerShell Editor Services which is used in the PowerShell extension for VSCode
(which runs in a different PS Host).

[ ] Issue filed:

[ ] Impact on Completions (both in the console and in editors) - one of PowerShell's most powerful features.

[ ] Issue filed:

[ ] Impact on PSScriptAnalyzer (which provides linting & formatting in the editor extensions).

[ ] Issue filed:

[ ] Impact on EditorSyntax (which provides syntax highlighting with in VSCode, GitHub, and many other editors).

[ ] Issue filed:

Wait on a preview release before considering for 7.4


Add a sample test using pytest-pyvista

🚀 Pull Request
Add a sample test using pytest-pyvista.
Description

Once this sample has been discussed and approved, we will add other tests in subsequent PullRequests.
Reference: pytest-pyvista document (https://pytest.pyvista.org/)
Edit: The best way to try this test is to let the test draw a different figure and see if that results in an error.

I recommend using --fail_extra_image_cache option on the CI.

Since it seems that conda-forge can also be created by non-authors, I will consider creating it.
https://github.com/conda-forge/staged-recipes

@bjlittle Could you please tell me how to register a new package in the lock file so that it will be installed by CI when we add a new package via pull request?

Of course, if you don't want to reject this PR LOL.

@bjlittle Could you please tell me how to register a new package in the lock file so that it will be installed by CI when we add a new package via pull request?

Ahhh it's a shame that pytest-pyvista isn't on conda-forge, I can help make that happen, if you needed help. From my perspective that would be ideal.
Essentially, the GHA CI ci-locks task renders all the package dependencies each week (scheduled as a GHA cron), but under the hood it's using conda-lock to do this ... the thing I'll need to investigate is whether it honours the use of pip within the YAML, and I don't think it does ATM.
Hence, having pytest-pyvista as a conda package would be ideal ... I'll make time this weekend to confirm this or not for you @tkoyama010

Of course, if you don't want to reject this PR LOL.

Of course not ... I'm excited that you're pushing this forwards @tkoyama010 and thanks @MatthewFlamm for getting involved.

I can help make that happen, if you needed help.

@bjlittle
Thanks. I have not created it yet and will give it a try.
Is this the right place to make our submit?
https://github.com/conda-forge/staged-recipes/tree/main

I will update the conda environment after https://github.com/conda-forge/staged-recipes/pull/24058 is released.

@tkoyama010 Of course, once pytest-pyvista is available on conda-forge, then we commit to embracing image testing of the geovista examples, for to #447 both geovista and pyvista will have failing tests.
This puts pressure on resolving #447.
Do you have a feel for whether this is possible soon?
If not, then as a temporary measure I guess I'll have to introduce a pyvista<=0.42.2 pin in the dependencies.
In fact, thinking about this I'm kinda forced to do this now for safety, and push a post release for 0.4.0

@tkoyama010 Of course, once pytest-pyvista is available on conda-forge, then we commit to embracing image testing of the geovista examples, for to #447 both geovista and pyvista will have failing tests.
This puts pressure on resolving #447.
Do you have a feel for whether this is possible soon?
If not, then as a temporary measure I guess I'll have to introduce a pyvista<=0.42.2 pin in the dependencies.
In fact, thinking about this I'm kinda forced to do this now for safety, and push a post release for 0.4.0

@tkoyama010 You'll also need to add pytest-pyvista to the pypi dependencies in https://github.com/bjlittle/geovista/blob/main/requirements/pypi-optional-test.txt

@tkoyama010 I'll sort out the optional dependencies that are required for this particular example :+1:

@bjlittle I opened #460 . Could you review and merge it?

pre-commit.ci autofix

pre-commit.ci autofix

pre-commit.ci autofix

I can't resolve the core dumped error, so I'm going to discontinue the investigation once.

Are you using osmesa vtk library or using xvfb?

It would be useful to add in an environment state and/or a pv.Report()  into the CI output before the tests are run.

I can't resolve the core dumped error, so I'm going to discontinue the investigation once.

Note that, the CI is using the QT bindings to vtk. I've never attempted to render a plot on a GH runner, does it have to be the OSMESA build of vtk instead?

Are you using osmesa vtk library or using xvfb?

Neither.
Is it a case that we should have:

osmesa vtk or
Qt vtk and xvfb

It's only Qt vtk at present.

I think these are the options that PyVista has used in the recent past.  I remember xvfb was flaky in the CI.  The way pytest-pyvista works is that it hooks into the before_close_callback machinery on the Plotter, so if you run with normal vtk bindings it will try to plot an interactive session and wait for it to close.  I never wrapped my head around why xvfb works in this case.
I could envision adding functionality to pytest-pyvista to work without this requirement by only using Plotter.screenshot.  In this way it would be slightly easier to use pytest-mpl.  But then you wouldn't be able to directly test your examples with images as they all use Plotter.show.

pre-commit.ci autofix

Since this PR seems to be the preferred one to move forward, I will place here.  The other PRs have regression errors.  I strongly recommend using a pyvista theme that is set in a conftest.py to avoid differences in themes for different contributors.  pyvista's is here (although I'd prefer it to be in a fixture that is autouse=True) to make sure it is reset before every test.
https://github.com/pyvista/pyvista/blob/19e7b15b4ba8a3466926804a6acab66b35377da9/tests/plotting/conftest.py#L13
https://github.com/pyvista/pyvista/blob/19e7b15b4ba8a3466926804a6acab66b35377da9/pyvista/plotting/themes.py#L3076-L3094

Thanks. You are best.

Closed by #470.
Thanks so much for pushing this forwards @tkoyama010 🍻


fix: Don't strip spaces from "ignore folders" paths

Hi, great job on the plugin. I noticed a small bug where the "Ignore Folders" list doesn't support paths that contain spaces. I don't see a reason why the should get stripped so I switched this to just strip the newlines.
Example:

I didn't realize this! Thank you for all!


Add filter in nearby volunteers

Should filter out all volunteers who are not set as 'MISSION', and all those set to hamal=True.
or alternatively: type='MISSION', hamal=False.

@astar26 Please confirm, but this seems irrelevant - putting on hold

Part of what we discussed earlier today. Will be added as part of scoring algoritm.


Waiting for processing

For slightly longer videos (>1hour) the programme stops after uploading the video and thumbnail without entering the rest of the info (promt:'video upload complete, processing will begin shortly').
Eventually the programme times out without entering in the rest of the info and the video goes into draft
I think it's good to add a another route to enter in the info if the waiting takes too long and let youtube finish the processing later

I have uploaded videos of around 1 hour 20min length, and it worked fine, can you share your video, so that I could look

I have uploaded videos of around 1 hour 20min length, and it worked fine, can you share your video, so that I could look

Yeah nvm, I removed the line that awaits the processing and added a 5s timeout after upload. So the video will upload with the info and the processing will fi ish later

Please send a PR, I will merge it, as it solved your problem

#57


New locking

Should be 75% (read-write lock controls access to the table by writers while an index is being built)
Adds a java test to test this behavior
Still need to add more tests and cleanup the existing tests that we may have broken.

Ignore this sorry


Update Readme.md

Formatting improvements -- spelling fixes

Thank you very much @marktab for these corrections !


Suggest inline SVG as another use case

Embeded SVG also tend to have alot of code, that you just dont wanna focus on.
So with this settings below you can fold the ugly part.
Regex to Match: <svg(\s*.*?\s*)<\/svg>
Regex Flags: gs

Note: Minfing SVG maybe required for better experience.Beside we looking forward that this extension will support multiple Regex soon.

Awesome 😁
I have always wanted to see different use cases, that's why I gave it a generic name.
Thanks for the PR


Add Echelon to osmosis-1 assetlist

After meeting the requirements of more than $15,000+ USD in our OSMO/ECH LP Pool #747 with external incentives enabled on Frontier, we are requesting addition into the main asset list for swapping on app.osmosis.zone, Thanks Osmosis! @JeremyParish69 @jonator @sunnya97

Hi, to be moved off frontier, you need to be receiving OSMO incentives

@sunnya97
Other coins like TGD and KUJI, etc. do not have Superfluid Staking enabled and have been added? Your documentation states we meet all the requirements? We were originally told we only required $1,000 in liquidity, checking today we are around $26,000+ USD and have external incentives enabled. We would request that we are added into the main asset list, so that we can get our Coinmarketcap listing updated with the new market (https://coinmarketcap.com/currencies/echelon/markets/), then Superfluid Staking would be proposed and voted upon, provided we have the proper exposure within the main dapp of Osmosis for our OSMO/ECH LP. Please and thank you sunny!

Hi @echelonfoundation , thanks for the interest. Although some assets are by exception strategically advanced to the primary asset list by the Foundation's discretion, the standard criterion is not by minimum TVL or whether one of its pools has superfluid staking; rather, tokens are added when Osmosis governance has voted to include a pool containing the asset to receive Osmosis liquidity mining rewards. One that happens we'll be happy to add ECH to the main list. For now I will close this PR.

@sunnya97
Other coins like TGD and KUJI, etc. do not have Superfluid Staking enabled and have been added? Your documentation states we meet all the requirements? We were originally told we only required $1,000 in liquidity, checking today we are around $26,000+ USD and have external incentives enabled. We would request that we are added into the main asset list, so that we can get our Coinmarketcap listing updated with the new market (https://coinmarketcap.com/currencies/echelon/markets/), then Superfluid Staking would be proposed and voted upon, provided we have the proper exposure within the main dapp of Osmosis for our OSMO/ECH LP. Please and thank you sunny!

Hi @echelonfoundation , thanks for the interest. Although some assets are by exception strategically advanced to the primary asset list by the Foundation's discretion, the standard criterion is not by minimum TVL or whether one of its pools has superfluid staking; rather, tokens are added when Osmosis governance has voted to include a pool containing the asset to receive Osmosis liquidity mining rewards. One that happens we'll be happy to add ECH to the main list. For now I will close this PR.

There are many tokens in the main asset list that do not have Superfluid Staking or a governance proposal voted on. The two coins I mentioned above do not seem to be following this process? If some assets are added by exception, that does not really make it fair to developers. What is the criteria for having an exception made? This seems to be really a bottleneck for developers and blockchains to have to have Superfluid Staking enabled (Voted in) to just be in the main asset list for trading, as it prevents Coinmarketcap from adding the market (which stifles growth).
How would people know in general and or want to vote yes on a proposal made for a coin that is not available for trading in the main asset list of Osmosis (The main domain app.osmosis.zone)? It is obviously technically feasible to create a proposal without such a listing, but would mean having more things working against a proposal than for it, right off to start. Hopefully something can be worked out, Thanks @sunnya97


No LICENSE file

Hi - I'm interested in using WAKit to make a QuickLook extension for .wasm files, but I don't see a LICENSE file in the project so it's not clear whether that's allowed.
Could you please add a LICENSE file?  Preferably a non-restrictive license if you're ok with it being reused.  Thanks.

Hey @akkyie, I'm interested in contributing to this awesome project, could you provide an update on the license please? Thank you!

@fdstevex @MaxDesiatov
Hi guys, thank you pinging me and deeply apologize for the late response.
I really don't know why I missed this issue…
It's now under MIT as usual.
This was nothing more than a hobby project during my college days, which I couldn't eventually get to work completely. I hope it helps you if it can, however!
(BTW I'm also exciting about the recent progress of swift-wasm!)


Choose library/framework

I don't feel like dealing with CSS or accessibility myself, and I'm not sure static site generators/vanilla JS are enough; plus I need a reason to dive into a cool thing like:

~https://fluidproject.org/infusion.html~
~https://svelte.technology/blog/frameworks-without-the-framework~
~https://donejs.com/~

~Not so sure about PureScript, Elm, Cycle.js...~
~Fine, I'll give up first-class code efficiency and web accessibility for DoneJS's innovation, maturity, debuggability, and transparency.~

JK.

JK.

Dojo 2 is still in beta, but let's see if I can use its good docs to get around its poor API docs... From reading about version 1, it's not a walled garden and it justifies/discloses many of its decisions/limitations/further directions.
It looks like it has at least some features/focus/history around code optimization, network optimization, debuggability.

Tutorials miss entire features.

HTML GUI wanted, but this works in RequireBin:
b=require('jsbn').BigInteger
console.log(require('factoradic').ntop(
 new b(/*HEX STRING WITHOUT 0x*/,16),0,[/*ARRAY*/],
 function(n,d){
  d=n.divideAndRemainder(new b(d+''))
  return{div:d[0],mod:d[1].intValue()}}))

It's also missing a calculation function for how much entropy is needed and the chance that extra extropy must be rejected for being out of the fair range.

Alternative: non-JS/TypeScript tools (but why?).
However..., fine fine, I'll try Dojo - I'm a web dev beginner and a sucker for all-in-one even if it means early adoption. :)


Add Helmet to the project

Reason/Context
Why do we need this improvement?
One of the security best practices for node.js is we should use helmet. This way we secure at least well-known web vulnerabilities by setting HTTP headers appropriately.
Description
What changes have to be introduced?
We should change the app.ts initializeMiddlewares function, to include the Helmet middleware.

@BOLT04 I would like to work on this issue 😊

@ritik307 Sure, you can work on it. Please ping us when you will have any problems :)

@ritik307 I've assigned the issue to you 🙂. Like @magicmatatjahu  said, do let us know if you have any doubts and we are happy to help 👍


Problems using goofys with ceph rgw using keystone accounts

I have a ceph radosgw integrated with an OpenStack cloud.
So there are two types of accounts here:

rgw accounts (accounts created using "radosgw-admin user create"
"keystone" accounts (accounts created "automatically": one account per
OpenStack project. To use these accounts, you use the EC2 credentials  provided by OpenStack)

I have no problems using goofys with rgw accounts.
Instead I have problems using the "keystone" accounts. For such accounts I am able to
use the S3 endpoint using e.g. s3cmd:
[sgaravat@localhost ~]$ s3cmd -c ~/cernbox/s3-magic-atesting.cfg ls
2020-03-25 20:10  s3://DOO
2020-03-25 20:10  s3://GOO
2020-03-25 16:45  s3://efg
2020-03-25 19:20  s3://goo
[sgaravat@localhost ~]$ s3cmd -c ~/cernbox/s3-magic-atesting.cfg ls s3://goo
[sgaravat@localhost ~]$

but when I try to use goofsys it claims that the bucket does not exist [*]
I realize that this info doesn't help to understand the info.
Please let me know how I can help to debug the issue
Thanks, Massimo
[*]
[sgaravat@localhost ~]$ goofys -f --debug_s3 -debug_fuse --endpoint https://clo\
ud-areapd.pd.infn.it:5210 goo /home/sgaravat/mnt1
2020/03/31 09:52:31.600023 s3.DEBUG HEAD https://cloud-areapd.pd.infn.it:5210/g\
oo = 404 []
2020/03/31 09:52:31.600207 s3.DEBUG Content-Length = [227]
2020/03/31 09:52:31.600239 s3.DEBUG X-Amz-Request-Id = [tx000000000000000007b11\
-005e82f6bf-11b39b7e-cloudprod]
2020/03/31 09:52:31.600302 s3.DEBUG Accept-Ranges = [bytes]
2020/03/31 09:52:31.600329 s3.DEBUG Content-Type = [application/xml]
2020/03/31 09:52:31.600354 s3.DEBUG Date = [Tue, 31 Mar 2020 07:52:31 GMT]
2020/03/31 09:52:31.600391 main.ERROR bucket goo does not exist
2020/03/31 09:52:31.600422 main.FATAL Mounting file system: Mount: initializati\
on failed
[sgaravat@localhost ~]$

what does the s3cmd cfg look like in this case?

Hello
This is the content of the s3cmd conf file
[default]
host_base = cloud-areapd.pd.infn.it:5210
host_bucket = cloud-areapd.pd.infn.it:5210
use_https = true
access_key = xxx
secret_key = yyy

does using --subdomain help

Unfortunately no:

[sgaravat@localhost ~]$ ./goofys.1 -v
goofys version 0.24.0-45b8d78375af1b24604439d2e60c567654bcdf88
[sgaravat@localhost ~]$ ./goofys.1 -f --debug_s3 -debug_fuse --endpoint https://cloud-areapd.pd.infn.it:5210 --subdomain goo /home/sgaravat/mnt1
2020/04/05 08:24:11.282197 s3.DEBUG HEAD https://cloud-areapd.pd.infn.it:5210/goo = 404 []
2020/04/05 08:24:11.282355 s3.DEBUG Content-Length = [227]
2020/04/05 08:24:11.282386 s3.DEBUG X-Amz-Request-Id = [tx000000000000000000dbb-005e89798b-11aaa85d-cloudprod]
2020/04/05 08:24:11.282432 s3.DEBUG Accept-Ranges = [bytes]
2020/04/05 08:24:11.282458 s3.DEBUG Content-Type = [application/xml]
2020/04/05 08:24:11.282509 s3.DEBUG Date = [Sun, 05 Apr 2020 06:24:11 GMT]
2020/04/05 08:24:11.282556 main.ERROR Unable to access 'goo': bucket goo does not exist
2020/04/05 08:24:11.282596 main.FATAL Mounting file system: Mount: initialization failed
[sgaravat@localhost ~]$

Unfortunately having the same issue, i can access the containers through s3cmd but not with goofys.
I had to set signature_v2 = True for s3cmd to work properly.


How to get a websocket connection handshake status code?

Hi @dvmatyun ,
When connecting to a websocket, I would like to intercept the handshake status code (e.g., 101 WebSocket Protocol Handshake, 401 Unauthorized, 500 Internal Server Error) to inform the user of the reason why the connection was unsuccessful, such as invalid credentials.
Is there a way how to get these handshake details?
Thanks.

Hi @selecky . As far as I know the low-level dart webSocket implementation gives me only closeCode and closeReason, but they are not like status codes. You can see PlatformWebsocketIo implementation in my library and if you have any idea where I can get those statuses - I can add them to library. However, I think what is possible for you if you want to have some scenarios on "wrong" connection to server - you can just send this codes as first message from server and close connection from server side. And client will react to those status codes.


Provide a SourceLocationConverter when adding a source file to a diagnostics group

The creation of SourceLocationConverters is expensive, so allow (but do not require) clients to provide one when adding a source file to a diagnostics group.

@swift-ci please test


Feat/UI env

This PR is included in version 1.0.0 :tada:

This PR is included in version 1.0.0 :tada:


Add links to rules

Eslint supports linking to documentation for rules. For example, if the no-comma-dangle fails, it will return a link to the rule:
https://github.com/AtomLinter/linter-eslint/wiki/Linking-to-Rule-Documentation

Hi @amilajack!
That's not an ESLint feature, that is a feature of the Atom linter plugin.
I recently created a new repo that has that same list (https://github.com/jfmengels/eslint-rule-documentation/) and I'm working on integrating it in that plugin (https://github.com/AtomLinter/linter-eslint/pull/657), though I'll have to get back to working on that. Obviously, this plugin is already on that new list, so it just needs to be merged.
Thanks for the reporting this though :)


docs: fix FluentDialogProvider registration

🙋 Documentation Request
https://www.fluentui-blazor.net/Dialog says

Dialogs are rendered by the  component. This component needs to be added to the main layout of your application/site.

As per https://github.com/microsoft/fluentui-blazor/issues/1195, it's incorrect as FluentDialogProvider needs to be added to the component, not the layout.

What do you mean by this? The FluentDialogProvider must be added at the end of the MainLayout page... as explained here :
https://www.fluentui-blazor.net/CodeSetup

And this has already been added quite some time ago:

Oops, wrong button...

No response so apparently not _that_important. Closing this.

I spent quite some time figuring out why FluentDialogProvider doesn't work despite added in the main layout before I stumbled upon https://github.com/microsoft/fluentui-blazor/issues/1195#issuecomment-1868106676 and tried to add it to the component instead, which fixed it. Either it's a bug in the code or in the documentation.


Option to show when a YouTube video is part of a playlist.

Let me explain. Many times I want to reference a playlist from YouTube. The way I currently do it, is to copy the link to the first video of a playlist and paste the thumbnail for that video.
Take for example the following video:

We can clearly see the video is part of a playlist. However, when I paste the video as a thumbnail, there is nothing indicating me that the video is part of a playlist.
So, I think a great addition for this plugins would be the ability to indicate if the link to the video is part of a playlist. Maybe a visual indication like the ones we have when the video start as specific point in time:

Thanks for your time :)

This is a feature I was thinking about building. I wasn't sure if it would be very useful, but hearing your explanation makes me think it would be. I will try to build it sometime soon.

Great to hear that. Thanks.

Hi.
Just wondering if there are still plans to implement this feature.
Thanks for the awesome job, one of my favorite plugins :)

I'm using this plugin more and more and realizing this would be very useful. Love this work!

Thanks for your comments! I should be able to build this in the next few days.

Awesome, thanks 👍


Create lock.yml

This PR will add a workflow that automatically locks closed issues and PRs with no activity for 180 days or longer. The workflow is run at the first day of the month. In this way we encourage people with a similar issue or PR to start a new one. That in turn avoids mixing conversions about very different versions of GGIR.

Checklist before merging:

[ ] Existing tests still work (check by running the test suite, e.g. from RStudio).
[ ] Added tests (if you added functionality) or fixed existing test (if you fixed a bug).
[ ] Updated or expanded the documentation.
[ ] Updated release notes in inst/NEWS.Rd with a user-readable summary. Please, include references to relevant issues or PR discussions.
[ ] Added your name to the contributors lists in the DESCRIPTION and CITATION.cff files.

Codecov Report

Merging #960 (f813d3d) into master (db25c5c) will not change coverage.
 Consider uploading reports for the commit 5470ccc to get more accurate results

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
@@           Coverage Diff           @@
##           master     #960   +/-   ##
=======================================
  Coverage   78.15%   78.15%
=======================================
  Files          93       93
  Lines       12364    12364
=======================================
  Hits         9663     9663
  Misses       2701     2701


iOS <IP_ADDRESS> (14B55c)

let me just leave this here
    else if (strcmp(u.version, "Darwin Kernel Version 16.1.0: Fri Sep 16 03:53:23 PDT 2016; root:xnu-3789.20.46~54/RELEASE_ARM64_T7000") == 0) {         allproc_offset = 0x5B0168;         rootvnode_offset = 0x5B60B8;     }

This looks very useful @tpurtell, and you actually made this issue code-related by adding code.
I have 2 questions for this:

Who would be on iOS 10.1 beta 1 right now?
Why didn't you just add this to the "offsets.c" file in this project?

Unfortunately I heard about Yalu after the signing window had closed.  I happened to have a test phone on  the beta so I did the analysis to find the offsets.   I suppose there might be a few other lucky souls out there who happen to have an old OS install they can work with, but who knows.
The code is intended to be added there, but since the window has closed, I didn't send it as a PR as the repository seems to be silent now.  The real directions to do this for other firmware's appear to be here: https://github.com/kpwn/yalu102/issues/414


[FEATURE] add support to Processing Python Mode

First thank you for creating this tool!
It would be great if one could make it work with Processing Python Mode.
Here is a tutorial for using Processing Python Mode with VS Code manually:
https://discourse.processing.org/t/tutorial-running-python-mode-in-vscode/7716

Processing Python mode is kind of dead. https://py5coding.org is the future, and it has a CLI run_sketch which could be a good thing to integrate, so I'll close this.


sloooowwwwww

maudite was created with the intention of making fast templates, by not concatenating strings all over the place and instead sending data to the destination stream as soon as it's ready to go.
Sadly, it seems that this may not be the case. As it turns out, the overhead of sending a new chunk whenever it's available seems to be considerably high. In some simple benchmarks I put together, it turned out that sending the chunks on their own is roughly ~10x slower than simply concatenating all the data together and writing it to the stream all at once. Unless I can figure out how to write things to the stream roughly 10x quicker, this means that the original premise and purpose of this module might be invalid and incorrect.
All is not lost though. There's still a pretty neat templating system here that takes advantage of ES6's template literals rather than including its own parser. The next goal here is to implement a new backend that simply concatenates and returns a string. Possibly using String.raw.

Closing this since I've now rewritten all the logic so it's now just concatenating strings recursively. This ends up being even faster than handlebars, which is pretty sweet!


[WIP] Try refresh UI

To be merged after #57.
This is mostly a test and I don't think this is the good way to go. However, the UI functions I added will still be useful. I just think that we need to handle it through memoization like the delete.

Updated.

Ah and now the dependencies are out of date... Why are we checking that btw?

I should put that in warning instead of error; the point being to follow the updates and avoid attempting to install a removed version from the repositories.. (it's dev only so it's okay to be bleeding edge)


Fix behave tests

Refactored login test cases, renamed pah_behave folder and made initial file organization

Please, be consistent in type hints - remove all or add missing (I recommend)

@kruczyna thanks for addressing to my suggested changes but I don't see your updated code in here. Have you pushed to correct branch? Last commit in this PR is Create first Behave feature  which I'm guessing is not the one with fixes.


Support for setting PreTokenGeneration to v2_0 for access token

Is this feature request related to a new or existing Amplify category?
auth
Is this related to another service?
cognito
Describe the feature you'd like to request
Currently, the amplify cli doesn't support configuring the PreTokenGeneration trigger to v2_0 directly through its configuration
Describe the solution you'd like
amplify update auth
Do you want to enable any of the following capabilities?
Add a Override Access Token option
Describe alternatives you've considered
use amplify override auth
and in override.ts
import {
  AmplifyAuthCognitoStackTemplate,
  AmplifyProjectInfo,
} from "@aws-amplify/cli-extensibility-helper";

export function override(
  resources: AmplifyAuthCognitoStackTemplate,
  amplifyProjectInfo: AmplifyProjectInfo
) {
  resources.userPool.userPoolAddOns = {
    AdvancedSecurityMode: "ENFORCED",
  }; // This works if I just ignore the type error
  resources.userPool.lambdaConfig = {
    preTokenGenerationConfig: {
      // ...
      // This is not currently supported
      // https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-properties-cognito-userpool-lambdaconfig.html#cfn-cognito-userpool-lambdaconfig-pretokengenerationconfig
      LambdaVersion: "V2_0",
    },
  };
}

Additional context
No response
Is this something that you'd be interested in working on?

[ ] 👋 I may be able to implement this feature request

Would this feature include a breaking change?

[ ] ⚠ This feature might incur a breaking change

Hey @Zhuohui-Li, thank you for filing this, marking this as feature request.
Note: tried overriding the property but was unable to modify the the property to v2
resources.userPool.addPropertyOverride("LambdaConfig", {
    ...resources.userPool.lambdaConfig,
    PreTokenGenerationConfig: {
      LambdaVersion: "V2_0",
      LambdaArn:
        "<arn>",
    },
  });


Ruby support for the buildpack

Adds Ruby support to the Google Cloud Platform buildpack.

@mdonkers I've pushed a "clean" version of this branch.


[site feature request] add ability to reset progress while signed in

Add the ability to reset progress while signed in

This feature is already available on the neetcode.io website.

Checkout the image above: the delete icon with white underlined

Closing the issue as its done :)


stability and fragile test fixes

Summary
if we get multiple keystones before we mine one, there is a chance that keystones get queued up twice; we copy the known keystones on each reception, then we try to mine, but we only lock during the copying step, so keystones may be copied twice in two different go routines then mined
don't mine known keystones in goroutines, it isn't helping
use less than comparison in tests, if an rpc gets called more than the expected number of times, this is ok
add consistent (longer) timeout to tests
Changes
see above

I ran this 5 times (before rebasing) and it passed each time:


When passing a Boolean to Cosmos Patch an Item Connector the Connector is converting the boolean to a string in the DB.

Describe the Bug with repro steps
Within Azure Logic Apps Cosmos Connector Patch an Item, when updating a value that is a boolean, the connector converts the value to a string when updating the CosmosDB.
{
"type": "Set",
"path": "/IsRecurring",
"value": true
},
I have tried all the differing Patch Types and all render the same result. I have manually entered the code within the patch body aswell as sent dynamic data. This is occurring in all scenarios. This does not seem to happen with integer values.
What type of Logic App Is this happening in?
Standard (Portal)
Are you using new designer or old designer
New Designer
Did you refer to the TSG before filing this issue? https://aka.ms/lauxtsg
Yes
Workflow JSON
{
    "definition": {
        "$schema": "https://schema.management.azure.com/providers/Microsoft.Logic/schemas/2016-06-01/workflowdefinition.json#",
        "actions": {
            "Patch_an_item": {
                "inputs": {
                    "parameters": {
                        "containerId": "@triggerOutputs()['queries']['AccountDatabaseName']",
                        "databaseId": "Accounts",
                        "itemId": "@triggerBody()?['DocumentId']",
                        "partitionKey": "@triggerBody()?['PartitionGroup']",
                        "patchOperations": [
                            {
                                "path": "/TicketName",
                                "type": "Add",
                                "value": "Famrmijgn1"
                            },
                            {
                                "path": "/IsScheduled",
                                "type": "Replace",
                                "value": "true"
                            },
                            {
                                "path": "/TicketNumber",
                                "type": "Set",
                                "value": "1000"
                            }
                        ]
                    },
                    "serviceProviderConfiguration": {
                        "connectionName": "AzureCosmosDB-4",
                        "operationId": "PatchItem",
                        "serviceProviderId": "/serviceProviders/AzureCosmosDB"
                    }
                },
                "runAfter": {},
                "type": "ServiceProvider"
            },
            "Response": {
                "inputs": {
                    "body": "@body('Patch_an_item')?['content']",
                    "statusCode": 200
                },
                "kind": "Http",
                "runAfter": {
                    "Patch_an_item": [
                        "SUCCEEDED"
                    ]
                },
                "type": "Response"
            }
        },
        "contentVersion": "<IP_ADDRESS>",
        "outputs": {},
        "triggers": {
            "When_a_HTTP_request_is_received": {
                "conditions": [],
                "inputs": {
                    "method": "POST",
                    "schema": {
                        "properties": {
                            "DocumentId": {
                                "type": "string"
                            },
                            "PartitionGroup": {
                                "type": "string"
                            },
                            "Update": {
                                "items": {
                                    "properties": {
                                        "path": {
                                            "type": "string"
                                        },
                                        "type": {
                                            "type": "string"
                                        },
                                        "value": {
                                            "type": [
                                                "integer",
                                                "string",
                                                "boolean"
                                            ]
                                        }
                                    },
                                    "required": [
                                        "type",
                                        "path",
                                        "value"
                                    ],
                                    "type": "object"
                                },
                                "type": "array"
                            }
                        },
                        "type": "object"
                    }
                },
                "kind": "Http",
                "type": "Request"
            }
        }
    },
    "kind": "Stateful"
}

Screenshots or Videos

Browser
Edge
Additional context
No response
AB#25790637

Hi, does anybody look at these issues?


New Nodes/BG Client section

Hello! Uploading a PR for a new section to include in the main BG site, about the Node/ bg Client.
It's a bit provisional cause as I understand the main goal is to redesign the whole BG site sooner than later, but just shipping this quickly to have it there in the meantime C:
It's supposed to look like this:

so it's still missing:

the lines that go all the way to the limits of the section (can't seem to get it done even with the IA)
and a small tweak to make the pink and green section stretch all the way (also can't find the issue- but I'm looking into it).
button copy is not great

Also maybe Hunter can give me a little frontend hand for these :) And open to any feedback, thank you!
PD: First PR after the long holidays so I hope it's not very messy :p

Thanks @ChangoMan ! The fixes were very helpful, just updated them. Will update on the lines as a last step 👍🏻


Updating debugger.

New debugger bits.

with NGEN/Ready2Run images.
minor fixes.

@gregg-miskelly @chuckries @wesrupert @DustinCampbell

This PR should at least improve https://github.com/OmniSharp/omnisharp-vscode/issues/971

Increment the version number to produce a new beta release?


NP-849: Add instruction for configuring OVN-K log level

Which issue(s) this PR addresses:

Closes #

/retest

/lgtm


BP_FunctionalTest_SimpleNavigation fails sometimes in both sp and mp

BP_FunctionalTest_SimpleNavigation in both sp and mp fails sometimes on GitHub so it was disabled. See if you can get it to fail locally, maybe when running the RunAutomatedGameTests.ps1 script with multiple TestLoops

It had some test pollution from another test where pm.MaxWalkingSpeedOverride was set to 1. It should no be fixed because i was unable to make it fail.


Fixed #2364 - scenarios produced by recorder play back in reverse order

You think there's a performance issue @oleg-nenashev ?

@tomakehurst not an issue given this is not the recurrent functionality


Store data in sqlite

It would be useful to store data in a sqlite database
Is it possible to integrate external saving ?

why would it be useful? this doesnt make any sense.
databases are meant to hold a large and complex amount of data where settings are just basic types (numbers and strings). also accessing a database is a much more expensive operation than accessing SharedPreferences (and accessing that data could happen a lot during an apps' life cycle).
can you please explain why you would want to do this?

Sure
I have an application which store config file for one company
I'd like to configure now multiple company and also to sync it with a server
Le mer. 13 févr. 2019 à 06:48, Or Dvir<EMAIL_ADDRESS>a écrit :

why would it be useful? this doesnt make any sense.
databases are meant to hold a large and complex amount of data where
settings are just basic types (numbers and strings). also accessing a
database is a much more expensive operation than accessing
SharedPreferences (and accessing that data could happen a lot during an
apps' life cycle).
can you please explain why you would want to do this?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/or-dvir/EasySettings/issues/7#issuecomment-463068475,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AFnSvLOq3D-dncft9Y71ESDqDl1DLNAQks5vM6cqgaJpZM4a3Qon
.

how big of a configuration file? if not too big, you can possibly convert it to json and then store that as a string.
it sounds like the "regular" way of storing settings/preferences does not suit your needs, and this library is meant to be as close to the "regular" way as possible.

i think it is a good idea to store in a json file.
how would do you proceed, would you store in shared pref file and then migrate it in json ? or would you directly store in json with a lib ?

i meant store the json as string (which you can save to shared preferences), not a file.
i dont know the specifics of your app requirements and how this configuration file is built, but maybe instead of in a file you can save those configurations as a json string and then save that string to shared preferences


v1 Account

Display email and password, and allow them to change them.

TODO:

Allow changing email
First pass of improving the UI by @johnkuney

I'm going to move changing their email out into a v2 #594.


Develop Resource Page: Contributions: Collaboration Style

This issue is for coordinating around developing the resource page for Contributions: Collaboration Style.
The resource page lives in the following google document for easy editing, commenting, and revision:
https://docs.google.com/document/d/1yx_EJO5lSnjeFji7__8kAaecDIRqFP95xkZm6GhOgxc/edit?usp=sharing
Once the page is in a decent shape, we will put a copy of it in the repository as a markdown file.
To work on this issue, feel free to leave a comment here and start editing the document. For questions, feedback requests, and other coordination tasks, please leave a comment here on the issue.
Please edit the google document directly and add your ideas to it. We can help with cleaning it up later.

I am closing the issue as it has been labeled as a metric idea. The idea is that we can capture all metric ideas (either new metrics or additions to existing metrics). We can then look at all Metric Ideas collectively.


can I hide devices?

hi there
i have got 2 devices that are shared with me but not in my home any help will be appreciated

hey.
i’m a little confused because the title of your issue is about hiding devices but then you say the devices aren’t there in the first place?
Can you show startup logs of the plugin?

Yes you can use the plugin settings to hide/ignore specific devices.
Choose the correct device type section, add an entry with a label and the device id, and tick the “Hide from HomeKit” option.

i cant see that option anyware

Closing this as I believe I saw on discord you found the option.


chore(ui-ux): adjust bottom sheet layout

What this PR does / why we need it:
Adjust padding/margin of bottom sheet for vault fee and slippage tolerance
Which issue(s) does this PR fixes?:

Fixes #
Additional comments?:
Developer Checklist:

[ ] Read your code changes at least once
[ ] Tested on iOS/Android device (e.g, No crashes, library supported etc.)
[ ] No console errors on web
[ ] Tested on Light mode and Dark mode*
[ ] Your UI implementation visually matched the rendered design*
[ ] Unit tests*
[ ] Added e2e tests*
[ ] Added translations*

LGTM!


Chat history items text issue

Text of history items are not visible.

Sure checking on this.

Hi, @yagizhanNY, hope you are doing great.
Have found the root cause, the initial logic is a bit messy, cleaning it up (basically data passing from chat to sidebar or from another way needs to be handled like the user could create a new chat first or just start typing), will be pushing the changes after validating.


Add Kinova Jaco Gen3 description

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Warning: This coverage report may be inaccurate.
This pull request's base commit is no longer the HEAD commit of its target branch. This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.

For more information on this, see Tracking coverage changes with pull request builds.
To avoid this issue with future PRs, see these Recommended CI Configurations.
For a quick fix, rebase this PR at GitHub. Your next report should be accurate.

Details

9 of 9 (100.0%)  changed or added relevant lines in 3 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.01%) to 98.46%

Totals

Change from base Build<PHONE_NUMBER>:
0.01%

Covered Lines:
831

Relevant Lines:
844

💛  - Coveralls


The card info is not updated

Please check Services, Known Bug / Issues and Troubleshooting over here first: https://github.com/fuatakgun/kia_uvo/blob/master/README.md
Region and Brand of carEU
Version of the integration2.31.0
Describe the bug
Even though when you click on "last Update the pop up says it was updated 3 sec ago, the card itself continues saying that it was updated 1 hour ago or whatever the last value recorded was.
Debug logs if an error occurred
Outlined here: https://github.com/fuatakgun/kia_uvo/blob/master/README.md
To Reproduce
Expected behavior
Screenshots
If applicable, add screenshots to help explain your problem.

Additional context

I have resolved       the issue creating a button on the dashboard. Whoever wants to reproduce what I did, please see below.


Add variable link to explore in Grafana Loki?

Add a variable link to explore logs in Grafana Loki (with maybe a time range of 30 minutes ?).

Useful API endpoints:
Short URL: https://grafana.com/docs/grafana/latest/developers/http_api/short_url/
Datasource: https://grafana.com/docs/grafana/latest/developers/http_api/data_source/#get-data-source-id-by-name
Organization: https://grafana.com/docs/grafana/latest/developers/http_api/org/


Allow ability to set EKSv2 versions in KDM instead of UI

Currently EKS v2 versions are controlled by UI and any update to allow new EKS versions requires UI changes.
Update the ability so that KDM can control the EKS v2 versions.
Example PR of how we have to maintain EKS versions manually: https://github.com/rancher/ui/pull/4781

@gaktive  - Is this something that you guys are going to need for v2.6.4? It currently isn't targeted for a release but the associated issue (https://github.com/rancher/rancher/issues/33825) was actually delivered in v2.6.3. Is there even any work that needs to be done from the backend in order for the frontend to execute on this?

@Jono-SUSE-Rancher if the work on the backend is done, we can remove our manual entries. We have https://github.com/rancher/dashboard/issues/4401 sitting in our backlog blocked for 2.6.4 so this ticket reads as a duplicate of that one.

@rmweir - Can you confirm that I am not crazy here? Does the backend still need to do work with this specific issue or is #33825 completion in v2.6.3 sufficient for the criteria of this one?

33825 was about removing a specific issue, this is about making process of adding/removing them dynamic.


Add text inside progress bar

Is there a way to add text inside of the progress bar?

I figured it out and for anyone else with this question here is how I did it:
<Progress.Bar progress={0.3} width={200}><Text>test</Text></Progress.Bar>

Can I ask. is there a way to make a progress bar become a button?

When i trying your solution then it's showing like this

<Progress.Bar progress={0.3} width={200}>
<Text style={{position:'absolute', flex:0}}>testes
</Progress.Bar>

I did like that
<Progress.Bar progress={0.9} color={blueColor} width={200} height={19}>
<Text style={{alignSelf:"center",color:grayColor,position:"absolute",top:0.5}}>selected week 8
</Progress.Bar>


Bug 1976326: fix configmap registry server liveness probe timeouts

Failing readiness/liveness probe fires prometheus alerts for
CatalogSources backed by configmap registry servers.
In #1378, the readiness probe initial delay and timeout were bumped
to account for node resource constraints during pod startup. This
PR bumps the liveness probe delay and timeout values too, to account
for scenarios where node resources continue to be overloaded causing
the liveness probe to fail temporarily.
Signed-off-by: Anik Bhattacharjee<EMAIL_ADDRESS>

Need to wait until the downstream port has been completed to merge this.
/hold

/retest
/bugzilla refresh
@timflannagan I think we need an exception for this since it's an urgent/urgent

/hold cancel
/lgtm


Update the release process for publishing GliaWidgets to Cocoapods

Created template podspec file for automating the release process. A new release flow will not trigger pospec repo but publish podspec file directly from this repo.

!merge


[test] Fix C++ realtime tests

Fix C++ realtime tests using new way to declare listeners

 Snippets tests reports   SDK Version Tests overview      v6        v5                           :heavy_check_mark:                            v1        v1        v1        v1

@Aschen : You mean like this?


Fix: Always forward props from components to child elements

Fixes so that props are always forwarded from components (LoginForm, RegistrationForm, Authenticated, aso) to child elements.
How to verify
Use this branch with the React example application.
Use the various components LoginForm, RegistrationForm, Authenticated and NotAuthenticated and set props such as classNames and style and verify that these are on the first underlying element.
E.g.
<Authenticated style={{backgroundColor: 'black'}}>
  I should be wrapped in an element and have a black background.
</Authenticated>

And:
<Authenticated style={{backgroundColor: 'black'}}>
  <div>
    I should not be wrapped in an element, but the wrapping `div` above should have the a black background.
  </div>
</Authenticated>

Fixes #86

I visited all the components while reviewing this, please see the commit I just added.  We had to stop passing the spToken property downward, and utils wasn't being required somewhere.  This missing utils import was causing a silent error - the component simply wouldn't load, with no errors in the browser, or during the build step.  Do yo know what that's about?
Please review my additions, otherwise this PR looks good to me.

Thank you! I don't know why that happened. Before errors like that were caught, but it seems that it might have changed in the later Babel versions. But I have tested this and works great. So going to merge it in.


Any REST calls which return the full chain should be paginated

when we have a lot of blocks e.g. 10 million blocks - we can by default return the 2 days worth from in memory - and then paginate to get more - similar to how transactions_for_address works

moved to notion


Typo fixes

Fix a few typos and broken links.

:warning: Validation status: warnings

File
Status
Preview URL
Details

articles/quantum-techniques-2-OperationsandFunctions.md
:warning:Warning

Details

articles/quantum-techniques-3-LocalVariables.md
:warning:Warning

Details

articles/quantum-techniques-6-PuttingItAllTogether.md
:warning:Warning

Details

articles/quantum-techniques-TestingAndDebugging.md
:warning:Warning

Details

articles/libraries/data-structures.md
:white_check_mark:Succeeded

articles/quantum-techniques-4-TypeModel.md
:white_check_mark:Succeeded

articles/quantum-techniques-5-WorkingWithQubits.md
:white_check_mark:Succeeded

articles/quantum-techniques-2-OperationsandFunctions.md

[Warning] 1 invalid cross reference(s) "Repeat Until Sucess (RUS)".

articles/quantum-techniques-3-LocalVariables.md

[Warning] 1 invalid cross reference(s) "array types".

articles/quantum-techniques-6-PuttingItAllTogether.md

Line 20: [Warning] Invalid file link:(~/media/teleportation.svg).

articles/quantum-techniques-TestingAndDebugging.md

Line 164: [Warning] Invalid file link:(~/media/unit-test-output.png).

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

:warning: Validation status: warnings

File
Status
Preview URL
Details

articles/quantum-techniques-2-OperationsandFunctions.md
:warning:Warning

Details

articles/quantum-techniques-3-LocalVariables.md
:warning:Warning

Details

articles/quantum-techniques-6-PuttingItAllTogether.md
:warning:Warning

Details

articles/quantum-techniques-TestingAndDebugging.md
:warning:Warning

Details

articles/libraries/data-structures.md
:white_check_mark:Succeeded

articles/quantum-techniques-4-TypeModel.md
:white_check_mark:Succeeded

articles/quantum-techniques-5-WorkingWithQubits.md
:white_check_mark:Succeeded

articles/quantum-techniques-2-OperationsandFunctions.md

[Warning] 1 invalid cross reference(s) "Repeat Until Sucess (RUS)".

articles/quantum-techniques-3-LocalVariables.md

[Warning] 1 invalid cross reference(s) "array types".

articles/quantum-techniques-6-PuttingItAllTogether.md

Line 20: [Warning] Invalid file link:(~/media/teleportation.svg).

articles/quantum-techniques-TestingAndDebugging.md

Line 164: [Warning] Invalid file link:(~/media/unit-test-output.png).

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

:warning: Validation status: warnings

File
Status
Preview URL
Details

articles/quantum-techniques-2-OperationsandFunctions.md
:warning:Warning

Details

articles/quantum-techniques-3-LocalVariables.md
:warning:Warning

Details

articles/quantum-techniques-6-PuttingItAllTogether.md
:warning:Warning

Details

articles/quantum-techniques-TestingAndDebugging.md
:warning:Warning

Details

articles/quantum-concepts-7-PauliMeasurements.md
:warning:Warning

Details

articles/libraries/data-structures.md
:white_check_mark:Succeeded

articles/quantum-techniques-4-TypeModel.md
:white_check_mark:Succeeded

articles/quantum-techniques-5-WorkingWithQubits.md
:white_check_mark:Succeeded

articles/quantum-techniques-2-OperationsandFunctions.md

[Warning] 1 invalid cross reference(s) "Repeat Until Sucess (RUS)".

articles/quantum-techniques-3-LocalVariables.md

[Warning] 1 invalid cross reference(s) "array types".

articles/quantum-techniques-6-PuttingItAllTogether.md

Line 20: [Warning] Invalid file link:(~/media/teleportation.svg).

articles/quantum-techniques-TestingAndDebugging.md

Line 164: [Warning] Invalid file link:(~/media/unit-test-output.png).

articles/quantum-concepts-7-PauliMeasurements.md

Line 96: [Warning] Invalid file link:(~/../api/canon/microsoft.quantum.canon.measurepaulis.yml).

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.