remove dead link

This heading was removed as part of https://github.com/kubernetes/website/pull/39501

@josephgardner  Thanks you for your contribution.
Could you please sign the CLA before the PR can be reviewed.
You can follow the steps documented here: CLA Steps

@josephgardner : Please sign the CLA before you begin contributing to the Kubernetes project. Since there has been no action on this PR taken from your end, we'd be closing this off.
Thanks!
/close


add ability to warn when suspense queries aren't prefetched

When using the promise-rsc-hydration thingy we aim to prefetch all queries in the RSCs and just consume the streamed promises in our components.
This can be a bit fragile since forgetting to prefetch may not be obvious to find. This PR adds a new option that, when enabled, will log at warning level when useSuspenseQuery is called on a new query that's not already observed.
as with all options, this can be set globally when constructing the QueryClient and overridden locally cause you may have queries
Questions

naming? idk, just went with the first thing that came to mind. as a matter of fact it's not even bound to being on the server as you may wanna use this with a usePrefetchQuery -> useSuspenseQuery pattern in a SPA as well
given @TkDodo's recent talk, this should probably also accept a callback that gets the query(?) and not just a static boolean flag
warning log might be too specific, would it be better for this to be a function and allow the developer to control what should happen? Perhaps they want to log more/less info about the query to help track down the query that's missing a prefetch

I had as similar idea recently, but wanted to actually create some kind of StrictMode component that would only do this in dev-mode, but there, trigger a hard failure. Please have a look at the RFC:

https://github.com/TanStack/query/discussions/8064

Yea that's a much more thought out idea compared to this PR which I put together in 5 minutes after a meeting :)

Yea that's a much more thought out idea compared to this PR which I put together in 5 minutes after a meeting :)

😂 . Would you like to give implementing the first part of it a try? Specifically, the under-prefetching part, as it overlaps with what you were trying to do here:

Whenever useSuspenseQuery would suspend the component with a new promise, it would log an error. This will alert developers that they are using a suspense query, but haven’t prefetched it. When the component renders, it should merely pick up a promise that is already in the cache. This would address the under-prefetching issue.

Bonus points if it would also work with the use(promise) experimental feature 😁


Improve fee estimation performance / fix accidentally quadratic function

Issue Number

#2032 & rel
Overview

ca9dd1ea2ded5b3539d7362f4fcb74fd2bcadf94
:round_pushpin: remove use of DerivingVia in Sqlite types: can't build with --profile with it

bc1bacc106faa4b17ad2a3cecf75eb29fb459bd6
:round_pushpin: avoid re-creating and folding on a map to compute balance of a list of resolved inputs
This is somehow causing massive slowness in the fee estimation. Changing this reduces the time in benchmarks from 18,000ms to 3,000ms!!

f82a7fed3903f46409456c41ec46b292e2fa4bc6
:round_pushpin: use standard random generator for picking random UTxO
There's really no need for strong cryptographic randomness at this level, this is needlessly slower than it could be an called pretty often during fee calculation.

94d4812d459951fef3fa999008c35d9d781b4f0c
:round_pushpin: do not re-compute the full balance after picking new inputs
Instead, compute the balance incrementally. The 'coverRemainingFee' was computing the balance of the extra inputs selected to cover for fee. In worst-case scenario where many inputs needed to be selected, for example, 1000 extra inputs, it'll recompute the balance of an ever growing list a thousand times! Not only this is accidentally quadratic, but, it is also completely unbounded and will potentially select way too many inputs. In theory, this should not select more than the max allowed inputs. Next commit will fix this.

Comments

Before:
Latency with 500 utxos scenario
    postTransactionFee  - 16756.3 ms

After:
    Latencies for 2 fixture wallets with 500 utxos scenario
        postTransactionFee  - 119.0 ms

bors r+


Fixes for django-compressor compressing foundation.

Running the latest version of django compressor/sass ruby.
scss/components/_media-object.scss
Breaks when trying to compress the file becauses of $selector.
scss/util/_mixins.scss
Compiles but corrupts css output making screen unusable.
Not sure why this is happening since it supports ruby sass 3.4+. Any ideas?

Oh missed this pr right before mine...
https://github.com/zurb/foundation-sites/pull/7346

Merging this one because it's a slightly cleaner solution.


fix: endless poll on an errored ws stream

The sink_rx split from websocket will output endless Err(_) when error happened. Causing 100% cpu usage.
Use try_fold to return when the first error occurred.

Thanks for pointing out. Will do

And I think it's hard to test this function since this function accepts a warp::ws::WebSocket. The warp::test::WsClient can not send Err to the other side.


Read concepts from text file in fathomnet_generate

Instead of reading concepts from the command line, allow users to point the CLI to a text file. Would be helpful for big groups of concepts.

Got it. I'll tentatively plan on a newline-delimited list of concepts:
example.txt:
Apolemia
Abraliopsis
Chionoecetes tanneri

with usage
fathomnet-generate --concept-file example.txt ...

Resolved by #4


Add Grok-2?

Is it possible to add the results for Grok-2 on this to the leaderboard?

https://x.ai/blog/grok-2

Best regards

We are asking them for the breakdown now. We will update once we receive that.

They now have an official API:
https://docs.x.ai/docs | https://docs.x.ai/api
It would be great to have full, validated numbers on Grok 2. Some recent first-party numbers where exaggerated.


Update transactionBuilder.js

When trying to get estimated energy via constantContract, it returnes very small (wrong) value, because call_value variable is not passed in args. This update will fix it.
Why actually call_valu, fee_limit, token_id and call_token_value are not included in current version? Whats the reason?
Example without call value (current version where call value is excluded form constantContract call)
Request:

Response (decoded error: "REVERT opcode executed"):

Example with call value (changes made in this pull request):
Request:

Response:

Great! Thanks for your pr, we will test it, if there is no question, we will update in next version.


napari for geodata

🚀 Feature

We've had some interest in using napari for geodata. In addition to physical coordinate systems, we'll need tiling and geographic transforms. It turns out there is a project implementing these things, which I heard about on gitter.im/vispy/vispy: https://github.com/codypiersall/vismap
I have nothing more to add here, only opening this to track interest and progress here.

Very cool, maybe @freeman-lab can help us out ;-)

Is this tiling purely for map data, or could you also tile images with the same mechanics?

That specific package is for map data, but yes, it certainly can and should be generalised when it comes to napari.

I'm trying to use GeoTiffs and Shapefiles in napari and I consider this feature very important to create a 3D visualization that facilitates the analysis of certain parameters over time. Can you provide more information on how to implement vismap in napari and how to add a projection (example EPSG 4326)?
This is what I've achieved so far:

Added a shapefile (it is upside down), represented by several points in napari;

3D visualization (Lon, Lat, Time) of the NDVI (vegetation parameter) values of an island, important to detect clusters.

Without a geographic coordinate system it is difficult to use this type of data, any tips? I would like to help develop this feature for napari. I think it would be interesting to achieve something similar to this (but simpler and open source):
https://www.esa.int/ESA_Multimedia/Videos/2018/07/Earth_System_Data_Lab/

This is great!
More geodata examples would be wonderful. I have started a "napari for geoscience" playlist on youtube, which currently has only Draga's talk in it, but ideally we can add more in the future: https://www.youtube.com/channel/UCbTgw84ew4pxTJ9qu3W2hqg/playlists

Super cool your excited about napari for geosciences!

For geographic transforms, we'll probably need to do a bit of an overhaul of our transform system to enable user- or plugin-defined transforms, but I'm hoping it's not too terrible. 😬

I'd be interested to know what this requires too, I'm not so familiar with geographic transforms. cc @andy-sweet who was worked on the napari transform system too

But I have been thinking about whether we want to invert that model - i.e. mostly think about the viewer/canvas requesting the data required for some field of view.

@perlman might be interest in that approach too as we think about the "level of detail" rendering - cc @nclack


Update icons.json

Icons Library
Added icon resource
Library of Animated icons, ready to use in digital products, presentations, or videos!

Fixes Issue

Changes proposed

Screenshots

Note to reviewers

thanks


Unknown error occured

I was switch from another ETA integration to this, but unfortunatly cannot get to  work like I imagined.
I am on ETA-Integration 1.1.2
HomeAssistant: 2024.2.5
The Api version is 1.2
<api xmlns="http://www.eta.co.at/rest/v1" version="1.2" uri="/user/api"/>

Hi,
This error may be caused by a general error in Home Assistant.
Please check the HA logs in Settings -> System -> Logs -> Load Full Logs (Einstellungen -> System -> Logs -> Vollständige Protokolle Laden) There may be a critical error unrelated to this integration.
If you can't find any error there you can update the integration to the latest version (1.1.3) and retry setting it up. On the first dialog box you can then enable verbose logging.
If the error still persists you can then go to Settings -> System -> Logs and click on Download Full Log. Please upload the file here or on Pastebin.

Thanks for the quick answer.
I could not really see a unrelated problem in the logs, and after more testing I found that forcing the "old API version" does work, so it would appear the problem is related to the new API stuff... I did install the latest version for the Integration and for the pellet heater software itsself, too.
I did attach the log like you asked.
home-assistant_2024-02-29T22-36-48.965Z.log

Thanks for the log.
It looks like the integration just suddenly stops querying the ETA endpoints after almost exactly 90 seconds, without throwing any kind of error.
That looks suspiciously like some kind of timeout.
I will do some tests and see if I can find the problem.

Hi,
Unfortunately I can't reproduce the issue here.
According to your logs the integration just stops doing anything after some time without throwing any kind of error.
This leads me to believe that there is some external component which terminates the integration.
Home Assistant itself does not have this kind of feature, so I think that one of your other integrations interferes with the eta one.
If you want to help me pinpoint the problem you can do the following:

enable debug logging for everything (either in your configuration.yaml, or via a service call to logger.set_default_level, see the docs), try adding this integration again, and post the log here

make sure to reset the logging level to warning again at the end to avoid filling up your storage space with huge logfiles

or disable your other integrations one by one and retry adding this integration until you find out which integration interferes with this one

If not, you can force the old API version, which you already confirmed to be working. The only difference between the two API versions is how the sensors are discovered. So if all necessary sensors are discovered, you can just stay in old API mode.

Thanks for the help and testing it.
I did some testing myself, but could not really figure out what causes it, but since the old API isnt that much different according to you, I will just use that since that works fine.


Add --version and nmstatectl version

Added --version option and nmstatectl version. Wrote integration tests.

@ffmancera This should be the final PR.

Coverage remained the same at ?% when pulling bb5902035d61168192a1fd57bdba30e09f19a21b on IsmayilMirzali:master into 1b00ecadd292869e12d80b34c3a048bbe0893ae9 on nmstate:master.

Coverage remained the same at ?% when pulling bb5902035d61168192a1fd57bdba30e09f19a21b on IsmayilMirzali:master into 1b00ecadd292869e12d80b34c3a048bbe0893ae9 on nmstate:master.

previous discussion is in #920

Thank you, it looks quite good. Please see my suggestions for small improvements.

Done, made all suggested changes and made all changes into a single commit.

Also you will need to rebase the branch on master.

Please rebase the branch instead of merging master. If you need help with this. please tell us.

Please rebase the branch instead of merging master. If you need help with this. please tell us.

Some help would be appreciated, how would I rebase from the command line?

Please rebase the branch instead of merging master. If you need help with this. please tell us.

Some help would be appreciated, how would I rebase from the command line?

Please take a look here: https://git-scm.com/book/en/v2/Git-Tools-Rewriting-History

Please rebase the branch instead of merging master. If you need help with this. please tell us.

Some help would be appreciated, how would I rebase from the command line?

Please take a look here: https://git-scm.com/book/en/v2/Git-Tools-Rewriting-History

Is it good now?

Is it good now?

Thank you, it looks good except for the commit message, see my older comment: https://github.com/nmstate/nmstate/pull/926#discussion_r391777151

/packit copr-build

@ffmancera All good? Shouldn't the PR be automatically closed?

Thank you, it looks good now. Unfortunately, it needs to be merged by hand.


Typeguard not working if checked against Exclude

Bug Report

🔎 Search Terms
typeguard exclude union

🕗 Version & Regression Information
v4.6.2

This is the behavior in every version I tried, and I reviewed the FAQ for entries about typeguards

⏯ Playground Link

Playground link with relevant code
💻 Code

type AAA = {
    c: 0
    b: 1
} | {
    c: Exclude<number, 0>
    x: 1
}

const a = {} as unknown as AAA

if (a.c !== 0) a.x

🙁 Actual behavior
error
Property 'x' does not exist on type 'AAA'.
  Property 'x' does not exist on type '{ c: 0; b: 1; }'.

🙂 Expected behavior
no error

The type Exclude<number, 0> is exactly the same type as number. It does not do what you think it does. There is no way to represent a type "any number, except 0" in TypeScript. This would first require #29317.

thanks, tho it's been open for 3+yrs now...

It's a fairly difficult issue to solve.


[Map] MH-collaboration-timmy11

Not a playable MH map, in fact not even a MH map at all.  There is no game type set - the map has one PlayerStart and consists of two fairly nicely designed buildings in landscape - other than that it is empty - no sounds, no pickups, no bot paths, no nothing really. An unfinished project perhaps?

URL: https://unrealarchive.org/maps/unreal-tournament/monster-hunt/C/mh-collaboration-timmy11_43473a2a.html
Hash: 43473a2a0c38e7e8173fd5058e63c7b0600831b2
Current name: MH-collaboration-timmy11

Moved to tests and demos


fix: node 16.6.0 issue

Description
This pull request should avoid Rollup to fail with Node 16.6.0. You can have details about this issue here: https://github.com/babel/babel/discussions/15015#discussioncomment-3801654
Related issue
This closes #15.

Thanks! Do you have test it with some versions after and before 16.6.0? I suspect not only just 16.6.0 not work. Let's try testing a few of them on CI

I tried a few more versions, and I didn't find any anomalies. It will be a bit complicated to test each version one by one. Could I recommend adjusting the versions according to the users' feedback?

@Olyno That's reasonable! Have you tested 16.5.0, 16.7.0, latest 17.x and latest 18.x?

I just tried the versions you asked for, and they all seem to work fine.
Should we add a security layer by adding a build worflow for these versions? By using Github actions, we could reduce the cases of incompatibility @ailisp


#react-tinymce

Category

[ ] Question
[x ] Bug
[ ] Enhancement

Expected or Desired Behavior
The webpart react-tinymce have some minimal issues at the beginning when gulp serve is executed.
Some lines are missing and of this the application need to be modified first before running gulp serve.
The application is an texteditor and this means that height and position is needed for the webpart inside the SCCS module file.
Observed Behavior
An error occures when running at the first time after executing gulp serve:
[10:18:43] Error - typescript - src\webparts\reactTinyMce\ReactTinyMceWebPart.ts(15,25): error TS2307: Cannot find module './components/ReactTinyMce.module.scss'.
[10:18:43] Error - typescript - src\webparts\reactTinyMce\components\ReactTinyMce.tsx(16,19): error TS2307: Cannot find module './ReactTinyMce.module.scss'.
This happenes of the reason for:
.reactTinyMce {
// An emplty SCSS class that affects the application to run at the first time. This is a texteditor.
}
Steps to Reproduce
The application should have some parameters inside the module:
.\react-tinymce\src\webparts\reactTinyMce\components\ReactTinyMce.module.scss
Default values that may affect the first time run by gulp serve:
.reactTinyMce {
}
Submission Guidelines
First time runnig the application will generate an error because of some error inside the component module. I found that under the ReactTinyMce.module.scss file that has empty parameters that should not have.
What I did was to put this inside the file and the application worked:
.reactTinyMce {
max-width: 100%;
margin: 0 auto;
}
This reason is of the fact that the texteditor must have some margin and height before the project runs. Otherwise there will be no reason by the workbench to create the webpart without. Text editors must have edges and margins from the start.
Keep in mind that you can still have the application running and just enter the parameters inside the scope. Just save and wait until the page is reupdated.
Thank you! Sharing is caring.

Hi @Gspot81 the file that is causing you issues is an optional file, I will submit a pull request this weekend to update the webpart.


Documentation Getting started

The readme is lacking some basic getting started info IMHO.
After listing the features it start with Connect the SmartEVSE controller to your WiFi network (using the menu of the SmartEVSE) but connecting to the network is not possible using the menu. The menu only enables the hotspot. The password for the hotspot is only to be found using an usb3 cable, putty and the knowledge to use baud rate 115200.

I'll update the readme and manual with the information to connect the SmartEVSE to WiFi.
The password for the hotspot is also visible in the top line of the SmartEVSE LCD.

top line

User error on my side.  Totally missed the top line because the device is mounted pretty low. Thanks for the quick support @mstegen !


Adding a script to run torpedo as DCOS job

adding @disrani-px to review the dcos job

Addressed the comments


Robust toolchain resolution for Code LLDB dylib

Is your feature request related to a problem? Please describe.
The Swift extension currently resolves the Swift toolchain LLDB dylib used by CodeLLDB by following the symbolic link, if any, from other toolchain binaries to the toolchain install location and relative paths from there to the standard location. However, in some environments the symlink may not point to the toolchain. It can be a shell script, or some kind of proxy instead, which would mean that the dylib cannot be located in this way.
See the swiftly proxy proposal as an example.
Describe the solution you'd like
Since the Swift extension has knowledge of swiftly already, such as the presence of the config.json file, it can use the toolchain location under swiftly to find the symbolic link.
Note that the proposal above includes a possible mechanism to invoke swiftly itself to find a toolchain location that could be another avenue for finding the physical location of a toolchain managed by swiftly. Currently, it looks something like this, but could change before it is released:
swiftly use --print-location

Describe alternatives you've considered
An alternative to this is to use the LLDB-DAP, which doesn't require the use of specific files within a toolchain for debugging.
Additional context
N/A

@matthewbastien can we somehow ask swift for the location?


fix: use correct clickhouse port

Description
This PR fixes and issue in which the ralph API cannot connect to clickhouse because the port is wrong (9000 instead of 8123)

Thanks for the pull request, @Ian2012!  Please note that it may take us up to several weeks or months to complete a review and merge your PR.
Feel free to add as much of the following information to the ticket as you can:

supporting documentation
Open edX discussion forum threads
timeline information ("this must be merged by XX date", and why that is)
partner information ("this is a course on edx.org")
any other information that can help Product understand the context for the PR

All technical communication about the code itself will be done via the GitHub pull request interface. As a reminder, our process documentation is here.
Please let us know once your PR is ready for our review and all tests are green.

@Ian2012 🎉 Your pull request was merged!  Please take a moment  to answer a two question survey so we can improve your experience in the future.


Pfe navigation light dom

Title of this pull request

Link to discovery documentation (should contain all the planning and requirements for this work):

See the DISCOVERY.md template at the root of the project

Link(s) to demo pages where this element can be viewed:

http://localhost:8000/elements/pfe-navigation/demo/

What has changed and why
Summarize files edited as part of this MR along with a brief description of what was changed/why.

pfe-navigation/demo/index.html - making this match the mockups to be shared out
pfe-navigation/src/pfe-navigation--lightdom-2.scss - making temporary file that will merge over into --lightdom.scss when pfe-navigation branch is merged in to master.

Testing instructions
Be sure to include detailed instructions on how your update can be tested by another developer.

Browser requirements
Your component should work in all of the following environments:

[ ] Latest 2 versions of Edge
[ ] Internet Explorer 11 (should be useable, not pixel perfect)
[ ] Latest 2 versions of Firefox (one on Mac OS, one of Windows OS)
[ ] Firefox 60.7.2 (or latest version for Red Hat Enterprise Linux distribution)
[ ] Latest 2 versions of Chrome (one on Mac OS, one of Windows OS)
[ ] Latest 2 versions of Safari
[ ] Galaxy S9 Firefox
[ ] iPhone X Safari
[ ] iPad Pro Safari
[ ] Pixel 3 Chrome

Your repository infrastructure updates should work for at least:

[ ] Node v8.x
[ ] NPM v7.x

Ready-for-merge Checklist

[ ] Expected files: all files in this pull request are related to one feature request or issue (no stragglers)?
[ ] Did automated tests pass?
[ ] Did browser testing pass?
[ ] Did you update or add any necessary documentation (README.md, WHY.md, etc.)?
[ ] Was this feature demo'd and the design review approved?
[ ] Did it get a LGTM after the last commit?
[ ] Did you update the CHANGELOG.md file with a summary of this update?

Be sure to share your updates with the<EMAIL_ADDRESS>mailing list!

👍 Thanks for this Lyndsey!  It looks great.  We'll resolve the testing errors in pfe-navigation branch.


WalletConnect authentication

The node has in its config the admin address. For the front end to connect to the node and make changes, it needs to connect with the same address the node is configured with. Otherwise, the connection should not be allowed

Not sure what this issue is about? Whoever is running the node can use the same address in their wallet and the node conifg without any problems, that would already work with metamask, wallet connect etc. We also don't have any endpoints that require this authentication at the moment.


0.43.0 released

https://github.com/describo/crate-builder-component/releases/tag/v0.43.0

https://github.com/describo/crate-builder-component-react/releases/tag/0.43.0


Feature/preinstall script

Coverage remained the same at 85.887% when pulling becc5db41578af93b86001cd901ec379f0205b2f on feature/preinstall-script into 30862532d073d9337f9c81d64791218f84207f00 on master.


Full Inventory Page, Bower segment: sequences out of order

discovered on staging, http://<IP_ADDRESS>/index/?source=123906. Seems to be caused by some folios not having leading zeroes. Sequences, as far as I understand, can be ordered by s_sequence alone, rather than by folio and then by c_sequence (sequences don't have a c_sequence - only chants do)

You're looking for "natural sort" (as opposed to "ASCIIbetical" sort). Technically your database is sorting by the ASCII code of the leading digit.
There are a number of ways to solve this. The "easiest" is to post-sort your results in Python. There are some packages out there that does it, but the easiest is just to left-pad the string with zeros out to a fixed number to create a fixed-length string, and then sort on that.
000001
000045
000123
Since the zeros always sort first, this will end up in the correct order.
On the other hand the "correct" way is to implement this as a new collation in Postgres for fields that will need to be sorted this way. https://blog.testdouble.com/posts/2022-12-12-pg-natural-sorting/
NB: You will probably also find this problem when sorting by shelfmarks. For that you would need to identify numeric components of the string and left-pad those.

I think that natural sort by folio and then by s_sequence (i.e. the sequence notation Calvin Bower used) would solve this problem. But also, since s_sequence orders sequences in a manuscript rather than on a folio, the tweak made in #585 also works. Since Calvin Bower used his own idiosyncratic system for assigning "sequence numbers" to the sequences he found in the MSs he looked at, even if we implement "natural sort" in one way or another, things will end up displayed out of their intended order.
I don't know that it's worth trying to unpick all the situations where this occurs - unless someone (i.e. Debra) identifies natural sort as an important enhancement, ASCII sort is probably sufficient.


Adapting for HPX V1.5

This PR updates HPX to V1.5

Thanks @hkaiser!

Thanks for your contribution!

Thanks for your contribution!

Thanks for your work on vcpkg!


Build on CI

I don't see anything in your repository which suggests that the nuget packages are build on a CI-Server. Not doing so, is a security risk for any project which depends on this package, as you might change source files locally before building or your PC might be infected.
Are there any plans on building the NuGet package on an CI server, like for instance AppVeyor?
I can support you to do so, with creating a cake build script and an AppVeyor file, but in the end it's the maintainer who is responsible.
Keep up the good work!!
Best wishes,
Robin

@Lakritzator Thanks for the suggestion, Robin. I totally agree on the value of a CI Server. We should go for it.
Now it is just a matter of time and effort. It will be great if you can help speeding up the process by providing more information or even a PR. I will take care of the rest.

Btw, at present the integration&unit tests of DataflowEx depends on .Net Core 2 and Docker (so theoretically build+test can run on a Linux box). We may need to look for a CI provider that supports these.

Do they NEED Docker and Linux, or are you just implying that it's possible to use it?
AppVeyor can run a VM with a VS 2017 image which should support .NET Core 2.

you can use travis ci. its free for open source projects and supports docker and a csharp base image.


Fixes #5

Removes Google Analytics
Removes GH badges (blocked by ASF policy anyway)
Adds (Incubating) disclaimer to mentions of SC
Adds Incubator Logo + Footer

Thanks @rzo1

I will regenerate site content :)


Update note on available logging providers

Hello, I just noticed that the documentation for available providers is still pre-RTM:

The ASP.NET Core team is still working with third party logging providers to publish support for this logging model. Once these ship, we will include links to them here.

I have replaced this note with an alphabetized copy of the list found in: https://github.com/aspnet/Logging#providers
Cheers,
Nick

Hi @nblumhardt, I'm your friendly neighborhood .NET Foundation Pull Request Bot (You can call me DNFBOT). Thanks for your contribution!
You've already signed the contribution license agreement. Thanks!
The agreement was validated by .NET Foundation and real humans are currently evaluating your PR.
TTYL, DNFBOT;

@ardalis  please review.

:shipit:


Extension issue

Issue Type: Bug
Extension Name: python
Extension Version: 2021.9.1246542782
OS Version: Windows_NT x64 10.0.19043
VS Code version: 1.60.2

:warning: We have written the needed data into your clipboard. Please paste! :warning:

dupe of #1773


Allow creating query JSON via REST API

Is your feature request related to a problem? Please describe.
The basic features from #332 are useful but creating the query JSON is very cumbersome. The UI offers a very comfortable way to use presets and fine-tune them.
Describe the solution you'd like
Provide an API to generate query JSON based on (a) the case (b) general presets (such as dominant or de novo) and (c) category deviations from these presets (dominant strict, dominant super strict).
Describe alternatives you've considered
N/A
Additional context
N/A

Implementation Proposal
We should introduce a module variants.query_presets that contains the code driving the feature and adjust variants.views_api to expose it. The defaults should be stored in immutable data structure where it makes sense and use typing where possible to allow for static detection of problems (e.g., attrs classes or Python enums).
The top level presets (such as "de novo") should be captured by an enum as well as the presets for each category (e.g., category frequency with entries dominant strict, super strict etc). When the category values are implemented as enums, they can provide a to_settings() function that then converts them into a dict with a fragment for the query settings. In the case where the value depends on the pedigree members, these should be passed as a parameter.
Affected Components
Varfish Server
Affected Modules/Files

variants.views_api
variants.query_presets

Required Architectural Changes
N/A
Implementation Sketch
See above.

Not fixed yet, tries to get arguments from kwargs but must get from GET params.


feat: pass T in onDidDismiss to OverlayEventDetail

Feature Request
the onDidDismiss, e.g. for a Modal, returns OverlayEventDetail<any>.
The any is poor for coding, it would be better to be able to pass T.
Right now onDidDismiss is defined like so:
"onDidDismiss": () => Promise<OverlayEventDetail<any>>;
please change to
"onDidDismiss": <T = any>() => Promise<OverlayEventDetail<T>>;
so T is still optional, but if you want, you can have it typed now.
Ionic version:

[x] 4.x
Describe the Feature Request

Describe Preferred Solution

Describe Alternatives

Related Code

Additional Context

@liamdebeasi Hello, I would like to take this. May I do this issue?

Yes, thank you!
Here is our contributing guide that gives you an overview of how to make the changes, test, and create a PR: https://github.com/ionic-team/ionic/blob/master/.github/CONTRIBUTING.md#creating-a-pull-request.
Let me know if you have any questions 😊.

Nice, didn‘t know that this is possible. Next time i contribute right away :)

@aivinog1  maybe you can look out for other locations where it‘s just any and change to T=any so we have the possibility to type it.

@nickwinger Yes, I'll try to find such methods, but if there are too many such methods I think that the best solution is to split such PR to many.
In the first iteration, I can find all the possible places and describe them in the comments of this task.

I've created a #21393 and I see other places when typing could be added:

https://github.com/ionic-team/ionic/blob/53fc8e37c89cea793d0e00246d52805166730108/core/api.txt#L908
https://github.com/ionic-team/ionic/blob/53fc8e37c89cea793d0e00246d52805166730108/core/api.txt#L1046
https://github.com/ionic-team/ionic/blob/53fc8e37c89cea793d0e00246d52805166730108/core/api.txt#L1080

Thanks for the feature request. This has been added via https://github.com/ionic-team/ionic/pull/21393 and will be available in an upcoming release of Ionic Framework.


WIP: Selenide driver

Proposed changes
Add non-static variant of $. It

makes possible to open 2+ browsers in one test
(in future) allows to use different configurations in parallel tests
makes Selenide own code cleaner and tests simpler

See feature request https://github.com/codeborne/selenide/issues/354
Checklist

[x] Checkstyle and unit tests pass locally with my changes by running gradle check chrome htmlunit command
[x] I have added tests that prove my fix is effective or that my feature works
[x] I have added necessary documentation (if appropriate)

Linked with #763

Wuhuuu!
We did it. Merged to master. The biggest refactoring ever.

@asolntsev I think that we can clear backlog now.


(feat): Update notebooks for new leiden defaults

See scverse/scanpy#2815 for implementation prompting the changes.  The changes here generally reflect the reordering of labels.  It does not look like results changed in a meaningful way, so changes should be minimal in that sense.

Current issues:

pbmc3k.ipynb
- pca on highly_variable (as was the default evidently) or not in cell 22
 spatial/basic-analysis.ipynb
- Why did the data change (3rd cell)?
- Why doesn't sc.pl.spatial not work in cell 14?
- SpatialDE.run is not working for no apparent reason
 spatial/integration-scanorama.ipynb
- number of categories for plotting the 2 image clusters is 18, but this is less than the total number (warning was present before)
- Link for adata_processed not working?  Should we regenerate?
- scanroma result changed?

Overall issues are the number of warnings, which is quite high without suppression.  Is this expected, and if so, how were they repressed in the past for building the docs?

So there are a few different strains here:

We need to get this stuff running in a reproducible CI env (ISSUE NEEDED). See https://scverse-tutorials.readthedocs.io/en/latest/ for how this can be done

We need to fix the current outputs so that the code runs (currently, some notebooks outright do not run)

We need to update the outputs so they match the scanpy outputs even if it is not totally reproducible (i.e., this current PR)

and 3. will be the blockers here for 1.10.  1. can come later.  The focus for now will just be on these notebooks.

Overall issues are the number of warnings, which is quite high without suppression. Is this expected, and if so, how were they repressed in the past for building the docs?

I have no idea why they were displayed like that. Maybe some manual setting somewhere?
By the way, those are not the warnings that will make a sphinx build fail when running sphinx in CI or with -W error. The warnings thrown during notebook creation will simply be displayed unless somehow silenced

@flying-sheep I understand, I was just curious.  I would be in favor of silencing them if you'd be ok with that.

Depends:
If there’s instances of warnings coming

only out of library code, like all these plotting warnings, we should file a scanpy bug and silence them globally in a hidden code cell at the start
both in library code and user code, we can silence them on a case by case basis by adding hidden code cells before and after the offending cell.

Otherwise:

UserWarning: Received a view of an AnnData. Making a copy.

Should be avoided with adata[...].copy().

ConvergenceWarning: lbfgs failed to converge (status=1): STOP: TOTAL NO. of ITERATIONS REACHED LIMIT.

Should probably fixed?
I don‘t want to see a
warnings.filterwarnings('ignore')

Yes!

View entire conversation on ReviewNB

Huh, I am not sure what happened here.   The local diff was correct.  It's possible something didn't push.

View entire conversation on ReviewNB

Nope, this cell was not run

View entire conversation on ReviewNB


Can I use this plugin with NextFederationPlugin?

I am also wondering about this.

Looks like it doesn't work, at least not with isServer option


feat: move google-cloud-cpp-pubsub (with history) into this repo

Fixes: https://github.com/googleapis/google-cloud-cpp/issues/3549
This PR moves the code in http://github.com/googleapis/google-cloud-cpp-pubsub into this repo at  google/cloud/pubsub. All git history from the previous repo has been preserved according to this script.

This change is

FYI, I think we need to add the integration-tests-no-emulator label to all the integration tests for them to be picked up by the CI scripts. Right now they are not running because they are neither storage-integration-tests, nor bigtable-integration-tests to run under the respective emulator.
We probably need to change ci/etc/integration-tests-config-* to add any Pub/Sub specific configurations too, maybe.

FYI, I think we need to add the integration-tests-no-emulator label to all the integration tests for them to be picked up by the CI scripts. Right now they are not running because they are neither storage-integration-tests, nor bigtable-integration-tests to run under the respective emulator.
We probably need to change ci/etc/integration-tests-config-* to add any Pub/Sub specific configurations too, maybe.

Done.


not formatting on save

Hi,
formatting on save stopped working in the last few days.
using vscode Version 1.19.0
plugin 0.0.20
Terraform v0.11.1

Having the same issue.

Make sure to have the following settings:
"terraform.format.enable": true,
"editor.formatOnSave": true

This worked for me.

Oh, that was already discussed here: https://github.com/mauve/vscode-terraform/issues/45

Thanks @taganaka -- I think this can be closed now @odedpriva?

@taganaka thanks.
@chadbean, yep, that helped


Known limitation: ChangeLegacyIndicators can handle max two variables in a bracket pair

Legacy DataFlex indicators were used instead of, for example, If-statements.
Example: "[Not Found] Indicate Select as... "
The logic for the ChangeLegacyIndicators refactoring function has a limit of max two variables within a bracket pair.
So this will be handled correctly;
"[Found ~Found] Begin"
...but this will not:
"[Found Select MyIndicator} Begin"

We will  leave it at this and just mention it in the help as a limitation of the tool.


feat: add command to run repo and commit finder without analysis

This pull request adds a new command find-source that requires a PURL, and optionally accepts a repository path as input. If no repository path is provided, the command will call the Repo Finder and Commit Finder to find the repository and commit of the provided PURL. If a repository is provided as input, only the Commit Finder will be called.
Closes https://github.com/oracle/macaron/issues/781

I tried to run the find-source command against a Maven PURL that doesn't have a version:
$ macaron find-source -purl pkg:maven/apache/maven
2024-08-16 11:16:55,421 [INFO] Setting the output directory to .../output
2024-08-16 11:16:55,422 [INFO] The logs will be stored in debug.log
2024-08-16 11:16:55,424 [ERROR] Could not find repo for PURL: pkg:maven/apache/maven

I believe we don't support Maven PURL without a version now - https://github.com/oracle/macaron/blob/44dbf0acbd3dcb9f577db97b5c6876cfb8c87957/src/macaron/repo_finder/repo_finder_java.py#L53-L56
However, the debug message doesn't show up if I ran it without the verbose flag. I believe we should let the user of the find-source command know about this behavior by default.

I also think it's great to add an integration test case for the new command too.


Add error for constant connection to output port

Hi ,
can you please add error if such case happen :
module inst(a,b);
output b;
input a;
assign b = ~a;
endmodule
module top(a,b);
input a;
output b;
inst inst(
.a(a),
.b(1'b1)
);
endmodule
iverilog gives this error :
top.v:12: error: expression not valid in assign l-value: 1'd1
top.v:12: error: Output port expression must support continuous assignment.
top.v:12:      : Port b of inst is connected to 1'd1
1 error(s) during elaboration.
yosys gives no error.
Thanks

Implemented in b6bd12f. (As part of the "hierarchy" pass.)


Proper Logging

Give the option to log issues that have been imported.

Need to output:

Celery logs
Django logs
Tenma logs

Imported comics
Errors
etc.

Functionality added. Will continue to improve over time.


How crashes are handled? [explanation]

I'm using Cowboy 2.7.0, and want to keep my HTTP handler very short.
Thus only matching for success, and never handling errors.
How Cowboy will handle my code because the Req term will be lost?
What i'd like to achieve is to tell Cowboy to send back an HTTP 500 reponse in any case.
Appreciate you help

In Cowboy 2.x there's a connection process and a request process (where your handler runs). When the request process crashes, Cowboy may send a 400 or an appropriate 4xx if the crash occurred within a cowboy_req function that deals with input. Any other crash results in a 500.
If you need to convert those 400/4xx to a 500 you can do so by implementing a stream handler, but it's generally not a good idea to hide those errors like this.

In Cowboy 2.x there's a connection process and a request process (where your handler runs). When the request process crashes, Cowboy may send a 400 or an appropriate 4xx if the crash occurred within a cowboy_req function that deals with input. Any other crash results in a 500.

Hmm, not observing this in my case.
2019-11-11T06:36:38.136504-05:00 error: crasher: initial call: cowboy_stream_h:request_process/3, pid: <0.284.0>, registered_name: [], error: {{badmatch,{error,closed}},[{transfer_ui_api_handler,stream_body_parts,4,[{file,"src/transfer_ui_api_handler.erl"},{line,231}]},{transfer_ui_api_handler,parse_mp_metas,3,[{file,"src/transfer_ui_api_handler.erl"},{line,260}]},{transfer_ui_api_handler,stream_multipart,2,[{file,"src/transfer_ui_api_handler.erl"},{line,272}]},{transfer_ui_api_handler,handle_post,3,[{file,"src/transfer_ui_api_handler.erl"},{line,155}]},{cowboy_handler,execute,2,[{file,"src/cowboy_handler.erl"},{line,41}]},{cowboy_stream_h,execute,3,[{file,"src/cowboy_stream_h.erl"},{line,320}]},{cowboy_stream_h,request_process,3,[{file,"src/cowboy_stream_h.erl"},{line,302}]},{proc_lib,init_p_do_apply,3,[{file,"proc_lib.erl"},{line,249}]}]}, ancestors: [<0.283.0>,<0.122.0>,<0.121.0>,ranch_sup,<0.105.0>], message_queue_len: 1, messages: [{etag,<<>>}], links: [<0.283.0>], dictionary: [], trap_exit: false, status: running, heap_size: 1598, stack_size: 27, reductions: 27777; neighbours:
2019-11-11T06:36:38.142322-05:00 error: Ranch listener http, connection process <0.283.0>, stream 1 had its request process <0.284.0> exit with reason {badmatch,{error,closed}} and stacktrace [{transfer_ui_api_handler,stream_body_parts,4,[{file,"src/transfer_ui_api_handler.erl"},{line,231}]},{transfer_ui_api_handler,parse_mp_metas,3,[{file,"src/transfer_ui_api_handler.erl"},{line,260}]},{transfer_ui_api_handler,stream_multipart,2,[{file,"src/transfer_ui_api_handler.erl"},{line,272}]},{transfer_ui_api_handler,handle_post,3,[{file,"src/transfer_ui_api_handler.erl"},{line,155}]},{cowboy_handler,execute,2,[{file,"src/cowboy_handler.erl"},{line,41}]},{cowboy_stream_h,execute,3,[{file,"src/cowboy_stream_h.erl"},{line,320}]},{cowboy_stream_h,request_process,3,[{file,"src/cowboy_stream_h.erl"},{line,302}]},{proc_lib,init_p_do_apply,3,[{file,"proc_lib.erl"},{line,249}]}]

It's like my process gets restarted and my browser keeps sending data.

If you need to convert those 400/4xx to a 500 you can do so by implementing a stream handler, but it's generally not a good idea to hide those errors like this.

I'm fine with this. 400/4xx is also OK.

The logs will not tell you what the response status code was, you need to look at the response directly.
Dunno why the browser would keep retrying, maybe you got some JS doing that?

The logs will not tell you what the response status code was, you need to look at the response directly.

I don't see any error code 4xx/5xx in browser's inspector console.
That's why this my form keeps pushing data to cowboy handler i think.

Dunno why the browser would keep retrying, maybe you got some JS doing that?

Firefox 70.0.1 on MacOS.
I will investigate more and keep you posted. Thanks for you time.

@essen can you please point me to the part reponsible of returning the 500 reponse code?

@essen I was able to narrow down my issue to this clause cowboy_http.erl#L969-L970
The 500 reponse gets in there, and simply gets dropped from the list.
I still don't understand the logic, but i'm pretty sure you can help.
commands(State, StreamID, [{error_response, _, _, _}|Tail]) ->
	commands(State, StreamID, Tail);

Thanks

This clause drops the error_response when a response was already sent. We cannot send two responses in HTTP.


Estimation module template

This branch will be ready to merge after some clean-up.

We're going to remove the ceci dependency to have a simpler estimator superclass whose subclasses can wrap photo-z PDF codes.

Last things to do before merge:

[ ] Combine tomo.py and base.py (and credit tomo_challenge)
[ ] Fill in documentation
[ ] Move paths and output format parameters from base.py to base.yaml; make estimators read in both their own param file and base.yaml (with path names that we will change for different test conditions)

random.py should be renamed as random_pz.py for instance, as I am not convinced the namespace can be safely kept.

from estimator import Estimator as BaseEstimation : I think it should be from ..estimator etc to be ok with local imports

in estimator.py the files are loaded at initiallization, instead of when that are actually used..... I think we should be lazier.... Not sure how this works out with the parallel_io branch effort

I am opening the pull request for review as it seems that github can help automatically detect relevant templates for actions, but this is based on what is on master. CI is the last thing to deal with in this first stage overall construction of the package

I just added a basic coverage running, and it seems to work

remaining issue with class_name moved to new issue #22


tests/vntag: Basic test case for VNTAG decode

Continuation of #489
This PR adds a basic test for VNTAG decoding and supports

7.0.0 beta
-6.0.3 backport

@jlucovsky what is the status ? should this pass now that https://github.com/OISF/suricata/pull/6173 got merged ?

@jlucovsky what is the status ? should this pass now that OISF/suricata#6173 got merged ?

Yes -- this test should be succeeding with the merge of that pr.

So, could you rebase and force-push to run CI again ?

Merged. Thanks!


Add support for an optional path to Dism.exe and apply EAs from WIMs

@mebersol look ready  to merge?

I've been trying to avoid updating the MakePs1 build version, otherwise looks good


Bumped version to 0.2.2

Codecov Report

Merging #45 into master will not change coverage.
The diff coverage is 100%.

@@          Coverage Diff          @@
##           master    #45   +/-   ##
=====================================
  Coverage     100%   100%
=====================================
  Files           3      3
  Lines         191    193    +2
  Branches       20     20
=====================================
+ Hits          191    193    +2


feat: allow overriding instance profile name

When creating provisioners outside of CDK having a friendlier Instance Profile name makes it easier to pass it around, compared to the ugly CDK-generated name.
Example
Without override
new Karpenter(this, 'Karpenter', {
  cluster,
  vpc,
})

// instance profile name: instanceProfile: MyStackAFA747D8-KarpenterInstanceProfileCDDAB33E-Lh74yWBWUNIu

With override
new Karpenter(this, 'Karpenter', {
  cluster,
  vpc,
  instanceProfileName: 'my-instance-profile
})

// instance profile name: instanceProfile: my-instance-profile

@robertd sorry for the ping but I noticed my other pr (#31) is also still open. May I request your review on both? We need these features for our projects and would very much love helping maintain an existing project over forking/implementing our own

Thanks for the PR and sorry for the late response. I was out of the pocket for a while. I'll get cdk-karpenter project back on track soon.

@MatteoJoliveau Can you please pull the latest main and resubmit your PR? v2.0.0 introduced some breaking changes. Thanks!

@MatteoJoliveau Any updates on this PR?


Hyprland crashes when a window is too small

Hyprland Version
 System/Version info
Hyprland, built from branch HEAD at commit 84ab8d11e8951a6551d1e1bf87796a8589da6d47  (props: bump ver to 0.35.0).
Date: Mon Feb 5 01:59:02 2024
Tag: v0.35.0

flags: (if any)

System Information:
System name: Linux
Node name: MAXHUB-D501
Release: 6.7.6-zen1-1-zen
Version: #1 ZEN SMP PREEMPT_DYNAMIC Fri, 23 Feb 2024 16:32:48 +0000

GPU information:
00:02.0 VGA compatible controller [0300]: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller])
00:13.0 Non-VGA unclassified device [0000]: Intel Corporation Sunrise Point-LP Integrated Sensor Hub [8086:9d35] (rev 21)

os-release: NAME="Arch Linux"
PRETTY_NAME="Arch Linux"
ID=arch
BUILD_ID=rolling
ANSI_COLOR="38;2;23;147;209"
HOME_URL="https://archlinux.org/"
DOCUMENTATION_URL="https://wiki.archlinux.org/"
SUPPORT_URL="https://bbs.archlinux.org/"
BUG_REPORT_URL="https://gitlab.archlinux.org/groups/archlinux/-/issues"
PRIVACY_POLICY_URL="https://terms.archlinux.org/docs/privacy-policy/"
LOGO=archlinux-logo

plugins:

Bug or Regression?
Bug
Description
Hyprland crashes when a window is too small caused by opening too many windows.
How to reproduce
simply by spamming the key you use to open your terminal.
Crash reports, logs, images, videos
hyprland.log
hyprlandCrashReport4297.txt

Updated Hyprland to release v0.36.0, the bug does not occur anymore. Note for arch users that if Hyprland is installed through pacman then the version is still on v0.35.0.


support platform report

add support for platform report 1 (total searches, clicks, and record views)

This was implemented in #87


Initial wallet loading time is long

I took ~ 1 - 2 minutes.
How about showing an loading icon or message to let users wait and make a coffee?

Added a small animation using loading dots ("Loading." -> "Loading.." -> "Loading...")


git attributes added

Summary: Line endings unified to LF
Type: Feature
Owner: Marcin Wojciechowski
Reviewers: Adam Czynszak, Stuart Pett
Coding Standard Applied: Y
Test Plan: None
Dependencies and Impacts: None
Jira: RIALTO-21

https://jenkins.code.rdkcentral.com/job/build-component/59982/ started.

https://jenkins.cmf.code.rdkcentral.com/job/github-triggered/16940/ started

https://jenkins.cmf.code.rdkcentral.com/job/build-component-platform/28645/ started.

Smoke tests for ['build-brcm-refboard'] added.
https://jenkins.cmf.code.rdkcentral.com/job/test-components-flow/130285/

Smoke tests for ['build-rpi-hybrid-refapp2'] added.
https://jenkins.cmf.code.rdkcentral.com/job/test-components-flow/130290/

Smoke tests for ['build-rpi-hybrid-wpe-dunfell'/'build-rpi-mc-wpe-dunfell'] added.
https://jenkins.cmf.code.rdkcentral.com/job/test-components-flow/130291/


[base-ui][Switch] Refine demos

[x] I have followed (at least) the PR section of the contributing guide.

Follow-up to https://github.com/mui/material-ui/pull/38820
Standardize the border and focus style on Base UI Switch demos
👉   https://deploy-preview-39822--material-ui.netlify.app/base-ui/react-switch/

@zanivan the issue was because the focus is not on the element you want to style (it is on the hidden input). I used the group selector where I check for the Mui-focusVisible class on the parent, see https://github.com/mui/material-ui/pull/39822/commits/d831bdaa3341e4a71a0a2d090efb674f6880c7ba. I hope this helps for future demos :)


Output to MongoDB interface doesn't work

Failed to execute the following code.
      context.bindings.employeeDocument = JSON.stringify({         id: context.bindings.myQueueItem.name + "-" + context.bindings.myQueueItem.employeeId,         name: context.bindings.myQueueItem.name,         employeeId: context.bindings.myQueueItem.employeeId,         address: context.bindings.myQueueItem.address       });
500 Error:
Sql api is not supported for this database account ActivityId: 18408514-8907-4665-b0e5-eae696e5cb09, Microsoft.Azure.Documents.Common/2.11.0, Windows/10.0.14393 documentdb-netcore-sdk/2.9.2
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: cad004df-f275-bc43-5de9-2a7eed9260d8
Version Independent ID: 84a11ee5-3e98-3c28-ab41-3b776598894c
Content: Azure Cosmos DB bindings for Functions 1.x
Content Source: articles/azure-functions/functions-bindings-cosmosdb.md
Service: azure-functions
GitHub Login: @craigshoemaker
Microsoft Alias: cshoe

@dery168 -  Thanks for brining this to our attention. We will investigate it further and update you shortly.

Hello @dery168,
Thank you for reaching out. Azure Functions’ CosmosDB Binding does not support MongoDB using SQL API. The alternative is to run the MongoDB client directly within the code. You can refer to this blog which shows how to integrate MongoDB with Azure Functions using C# and something similar can also be done using other supported programming languages.

@dery168, Just following up here... Hope my previous comment helps.

Hi @ChaitanyaNaykodi-MSFT : thanks for the following up! But for a super simple Function solution my client is expecting is:

Able to read and  write to dynamodb with MongoDB interface.
Browser based editing the JavaScript Function.
I am able to run the MongoDB client directly within the code on a Linux base Function but browser editing is missing.
I switch to Windows base Function but still failed because Windows missing MongoDB npm.

@dery168, Thank you for the response.
Actually editing the code from the Azure Portal is not recommended, we can edit function app using multiple local tools. Following the JavaScript developer guide for functions can also be helpful.
Please feel free to comment, I will be happy to continue with our conversation.

Totally make sense. Thanks @ChaitanyaNaykodi-MSFT !
It would be great the targeted document could indicate MongoDB interface binding wouldn't work with nodejs (maybe work for C# only?).

@dery168, Thank you for the feedback. You can also explore the Azure Cosmos DB's supported API's which supports multiple programming languages.

@dery168 We will now proceed to close this thread. If there are further questions regarding this matter, please reopen it and we will gladly continue the discussion.


Add metros to location summaries

@mikelehen I added metros to the summary files here - it looks like the email alerts query by fips code, so I don't think adding additional fips that it doesn't know about should be an issue? But wanted to verify in case it is


Storage download() and list() systematically return 404

Using supabase plugin version 1.2.0 or 1.3.0, using download() or list(), both return 404.
Reproduction:
Create a "public" bucket, named "translations" and upload a file, named "locale_en.json"
In Flutter, execute the following:

await Supabase.instance.client.storage.from("translations").download("locale_en.json")
or
await Supabase.instance.client.storage.from("translations").list()

Both return an exception:
StorageException(message: The resource was not found, statusCode: 404, error: Not found)
Logs on Supabase reveal an extra "/info/" in the URL being used.
Context:

Flutter 3.3.10
supabase: 1.2.0 or 1.3.0
supabase_flutter: 1.2.2

Thanks @boeledi for opening this issue.
Have you configured RLS policies for the translations bucket? Public buckets allows you to access the stored objects through a public URL, which you can obtain by calling supabase.storage.getPublicUrl(), but they still require proper RLS policies if you want to perform .download() or .list() operations on them.
We could probably address this is the comments docs of each method, so I will add it to my queue to add some comments about it.

Thanks @dshukertjr for your answer.
I have just tried to configure such RLS policy, but I still have the same issue with the following policy definition
((bucket_id = 'translations'::text) AND (storage.extension(name) = 'json'::text) AND (lower((storage.foldername(name))[1]) = 'public'::text) AND (role() = 'anon'::text))

my bucket is "translations" and I have 2 folders.
Here is an extract of the logs I see on Supabase, in which we clearly see the word "info" (see highlighted)
[
  {
    "context": [
      {
        "host": "ip-........eu-central-1.compute.internal",
        "pid": 29
      }
    ],
    "err": [],
    "error": [
      {
        "__fault": null,
        "__metadata": [],
        "address": null,
        "cause": [],
        "code": null,
        "config": [],
        "detail": null,
        "errno": null,
        "expiredAt": null,
        "file": null,
        "httpStatusCode": null,
        "length": null,
        "line": null,
        "message": null,
        "metadata": [
          {
            "bucketId": "translations",
            "name": "folder1/locale_en.json",
            "names": []
          }
        ],
        "name": null,
        "originalError": [],
        "port": null,
        "postgresError": [
          {
            "code": "PGRST116",
            "details": "Results contain 0 rows, application/vnd.pgrst.object+json requires 1 row",
            "hint": null,
            "message": "JSON object requested, multiple (or no) rows returned"
          }
        ],
        "routine": null,
        "severity": null,
        "stack": null,
        "status": 406,
        "statusCode": null,
        "syscall": null,
        "validation": [],
        "validationContext": null
      }
    ],
    "job": [],
    "level": "info",                       <<<<<<<<<<<<<<<<<<<<< IS THIS NORMAL ?
    "project": "........",
    "req": [
      {
        "headers": [
          {
            "accept": null,
            ...
            "content_length": null,
            "content_range": null,
            "content_type": null,
            "date": null,
            "host": "storage-api-lb-eu-central-1-ext.storage.supabase.com",
            "referer": null,
            "transfer_encoding": null,
            "user_agent": null,
            "x_client_info": null,
            "x_client_trace_id": null,
            "x_forwarded_proto": "https"
          }
        ],
        "hostname": "storage-api-lb-eu-central-1-ext.storage.supabase.com",
        "method": "GET",
        "remoteAddress": ".......",
        "remotePort": 31810,
        "url": "/object/info/translations/folder1/locale_en.json"
      }
    ],
    "reqId": "........-BRU",
    "res": [
      {
        "statusCode": 400
      }
    ],
    "responseTime":<PHONE_NUMBER>033932,
    "results": [],
    "tenantId": ".............................."
  }
]

@boeledi Yeah, I can see the same log on my working project as well, so accessing info shouldn't be the problem.
I would try to debug the RLS policy. One thing I noticed is that you have role() = 'anon'::text if you are making the API call from a user that has been signed in, this would be false, but any chance you are doing that? I would personally remove that statement, just because it's not adding any security.

I will close this issue for now, as it seems like it's a matter of setting up the correct RLS policy but feel free to reopen it if the issue persists.


How to accept input within a handler function?

I have read through the documentation, but could not to find a solution that could accept input in a handler function. I have two agents to connect using "SYNC_PUB", and when an agent receives message another agent, it can accept input (a dialogue to ask for input) and then send this message back to the other agent.
I would like to create interfaces for the agents, could anyone tell me how to implement this? Any suggestions? Thanks a lot in advance.

I think you may be referring to this: https://github.com/opensistemas-hub/osbrain/issues/313
Feel free to reopen otherwise.


RandomTransitionGenerator gets outside of image's content sometimes, or does too much zooming sometimes

I'm trying to have a POC project that has the following features:

fading action  bar, using this library:
https://github.com/flavienlaurent/NotBoringActionBar
imageView that change their sizes in parallel (top and bottom) , as you scroll.
the imageViews are actually KenBurnsView, and they switch between multiple images that might be from the Internet.
all in fragments and action-bar-navigation is supported.

here's the project:
https://drive.google.com/file/d/0B_nrUhQ0MIgwUGZ3cjJwZVpVbkU/
the problem is that even though everything works , the RandomTransitionGenerator sometimes go outside of the content of the image being shown, so empty area is shown too. Also, sometimes, the zoom factor gets really large.
of course, I had to change some stuff on both libraries in order for this to work, but most of the code remained intact.

hello
I'm not having the problem with getting out of the image's bounds.
However, I'm having the problem with WAY too much zoom.
You guys have any idea how I can fix that?

Sorry, I didn't return to this issue. I don't use this library anymore.

Hello,
Some news about this récurrent issue, it seems to occurs when view is used with multiple image downloaded from URL (Picasso in my case) and dynamically resized
Thanks
Nomane

I haven't seen it happening after https://github.com/flavioarfaria/KenBurnsView/pull/34.
Closing for now.


SR-IOV Migration: Move attach SRIOV devices to virt-handler

What this PR does / why we need it:
Currently when SR-IOV VM is migrated we detach its SR-IOV network devices just before migration
starts and attach similar devices to VM on the target when migration is finished successfully.
Attaching the SR-IOV devices is one-shot operation and is performed one time only at post migration.
Due to the fact that it is a one-shot operation the VM might end up in incomplete state (missing SR-IOV devices)
when a SR-IOV device is disconnected manually or due to aborted migration.
Also the current implementation doesn't follow Kubernetes desire state design that is followed all over the project.
With this PR changes, virt-handler VMController is now aware of the SR-IOV network devices state and reconciles
them which means they will be attached to the VM when needed.
Since attaching SR-IOV host-device is an intrusive operation it will be rate-limited and stops after a while.
Also With this change,  when a migration is aborted (due to failure or client request) the SR-IOV devices there were detached will be attached again to the source VM, and in case SR-IOV devices are disconnected from the guest they will be attached
again.
Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Special notes for your reviewer:
Release note:

SRIOV network interfaces are now hot-plugged when disconnected manually or due to aborted migrations.

/test pull-kubevirt-e2e-kind-1.19-sriov pull-kubevirt-unit-test

/test pull-kubevirt-unit-test pull-kubevirt-e2e-kind-1.19-sriov

Rebased
/test pull-kubevirt-unit-test pull-kubevirt-e2e-kind-1.19-sriov

/test pull-kubevirt-unit-test

Change:

Rebase
Resolve https://github.com/kubevirt/kubevirt/pull/6581#discussion_r767246024 and https://github.com/kubevirt/kubevirt/pull/6581#discussion_r767251059
Fix kubevirt core v1 api import

/test pull-kubevirt-unit-test

rebased

Changes:
Merged pkg/network/sriov package (introduced by the second commit) to pkg/network/vmispec

/test pull-kubevirt-unit-test pull-kubevirt-e2e-kind-1.19-sriov

changes:

(1st commit) add make generate changes
(2nd commit) fix backoff package test suite setup

/test pull-kubevirt-generate pull-kubevirt-build pull-kubevirt-unit-test

/test pull-kubevirt-manifests

/test pull-kubevirt-e2e-kind-1.19-sriov

/test pull-kubevirt-generate pull-kubevirt-build pull-kubevirt-unit-test pull-kubevirt-manifests  pull-kubevirt-e2e-kind-1.19-sriov

rebased

Resolved code review comments

Last force-push was performed to move this change to the second commit

The first two commits look good.
Is the 3rd commit ready?
And when are you planning to change the command on the virt-launcher to be async?

/test pull-kubevirt-e2e-kind-1.19-sriov

/test pull-kubevirt-e2e-kind-1.19-sriov

/test pull-kubevirt-e2e-kind-1.19-sriov

Rebased due to file license date issue (it was updated by make generate), it also caused unit-test job to fail.

Thank you! Great work, I know it was a hard and long one.

@EdDev  Thank you very much for your input and patience, here and face-to-face, I appreciate it!
I surly learned a lot :slightly_smiling_face:

/approve

Following offline discussion about how this PR changes affect SR-IOV hotplug on old virt-launcher pods and backward comparability in general.
I did some testing on my local env that emulating different stages of Kubevirt during an upgrade in order to verify that SR-IOV hotplug is performed as expected.
There are two interesting scenarios:

When a VM is migrated to a node that runs old version of virt-handler (w/o this PR changes), and new virt-launcher migration target pod (includes this PR changes)
For example: when Kubevirt was upgraded but there is a node still running old virt-handler and there is SR-IOV VM migration to that node.
virt-handler sends FinalizeVirtualMachineMigration command as part of post migration on target flow.
But new virt-launcher doesn't attach host-devices as part of FinalizeVirtualMachineMigration any longer.
Thus SR-IOV interfaces are not plugged to the guest at the end of the migration.
Once virt-handler is upgraded it will send HotplugHostDevices as part of the reconcile loop that will trigger
virt-launcher to attach the host-devices.

This is transient state as we expect all virt-handler pods to eventually upgrade as part of Kubevirt upgrade.

When a VM is migrated to a node that runs new virt-handler and virt-launcher migration target pod is old (w/o this PR changes).
For example: when Kubevirt is upgrading and virt-handler pods just finished its upgrade.
virt-handler sends FinalizeVirtualMachineMigration command as part of post migration on target flow.
old virt-launcher attach host-devices as part of FinalizeVirtualMachineMigration, but fails due to QEMU process lack of resources:

{"component":"virt-launcher","level":"error","msg":"cannot limit locked memory of process 117 to<PHONE_NUMBER>: Operation not permitted","pos":"virProcessSetMaxMemLock:962","subcomponent":"libvirt","thread":"51","timestamp":"2022-01-18T15:46:56.085000Z"}
{"component":"virt-launcher","level":"error","msg":""msg":"failed to hot-plug host-devices","name":"testvmi-bcxxb","namespace":"kubevirt-test-default1","pos":"live-migration-target.go:42",
"reason":"failed to attach host-device \u003chostdev type=\"pci\" managed=\"no\"\u003e\u003csource\u003e\u003caddress type=\"pci\" domain=\"0x0000\" bus=\"0x04\" slot=\"0x07\" function=\"0x0\"\u003e\u003c/address\u003e\u003c/source\u003e\u003calias name=\"ua-sriov-sriov\"\u003e\u003c/alias\u003e\u003c/hostdev\u003e,
err: virError(Code=38, Domain=0, Message='cannot limit locked memory of process 117 to 65536: Operation not permitted')\n","timestamp":"2022-01-18T15:46:56.091744Z","uid":"da2b6fb3-faef-4546-adcc-f44c76e1e2ba"}

Next, when the migration is completed and virt-handler now switched to the regular "vmUpdate" flow, it will send HotplugHostDevices command as part of the reconciliation loop, but old virt-launcher does not support it and return the following error:
"failed to hot-plug SR-IOV interfaces: unknown error encountered sending command HotplugHostDevices: rpc error: code = Unimplemented desc = unknown method HotplugHostDevices for service"

To solve this and support old virt-launcher pods it is necessary that make virt-handler keep adjusting QEMU process memloc limits (which is pre-requirement for attaching SRI-IOV host-device) as part of post migration on target node.
I have pushed new changes to fix it.

I accidentally pushed wrong change along with the one that was needed [1], I have pushed new change to remove just that [2].

/hold
Placing hold until we have more eyes on it

@AlonaKaplan , this change was added (after your approve) to support the (edge) scenario where a new virt-handler handles the migration target of an old virt-launcher.
It was explained in detail here.
I think we are good to go.

/unhold
We seem to be good, lets have this in.

/cherry-pick release-0.49


Correctness of ThaumcraftApi#exists

Is the method correct? Because when I tried to use it on items, it returned false on every one. So I copied this method to my mod, and Intellij inspection showed that CommonInternals.objectTags might not contain strings in its keys. I changed CommonInternals.objectTags.get(stack.serializeNBT().toString() to CommonInternals.objectTags.get(stack.serializeNBT().toString().hashCode()) and it now works properly.

This won't be resolved ever


Issue connecting to solr and mongo running in cloud

I was able to successfully use this index data from mongodb to solr in my local installation.. however when using the same with a solr instance running on cloud (opensolr).. I am getting following error when starting the mongoconnector..
c:\python27\lib\site-packages\requests\packages\urllib3\util\ssl_.py:90: InsecurePlatformWarning: A true SSLContext object is not a
InsecurePlatformWarning
Logging to mongo-connector.log.
should I follow any additional steps to make it work  .looking for some input around this..

This isn't a bug in mongo-connector. It appears to be a warning raised from urllib3, which is packaged by the requests library. I suggest asking the requests project:
https://github.com/kennethreitz/requests

Actually, this warning, with workarounds, is documented for urllib3 here:
https://urllib3.readthedocs.org/en/latest/security.html#insecureplatformwarning


Please consider to use other than 9000 port by default.

While it is possible to change the port i would suggest NOT to use 9000 by default.
This could save some time for users who work in PHP arena.

Fixed in version 3.0.0. Now the default port is set as 18512.


Camel-Salesforce: Fix serialization for string MPLs

Serialization/deserialization failed when using Strings instead of
enumerations for multiselect pick lists. You can reproduce by running the new test cases without the changes to the Serializer/Deserializer classes.
The error you'd see is:
Class org.apache.camel.component.salesforce.api.StringMultiSelectPicklistDeserializer has no default (no arg) constructor
 at [Source: (String)"{"attributes":{"type":"MSPTest"},"MspField":"Value1;Value2;Value3"}"; line: 1, column: 1]
        at com.fasterxml.jackson.databind.JsonMappingException.from(JsonMappingException.java:306)

I added default constructors for the affected classes and it seems to fix things.

Thanks!


MSSQL: Update the cascading rules section to point to the usage of referential actions as a solution instead of manual update of the migration file

https://www.prisma.io/docs/concepts/components/preview-features/sql-server/#cascading-rules

Closing this - it's an old link that no longer exists and the current version of the connector has a section on using referential actions for cyclic references.


dispositor: fix a couple typos and remove some python 2 code

Pull Request Test Coverage Report for Build 259

4 of 4 (100.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.004%) to 94.234%

Totals

Change from base Build 257:
0.004%

Covered Lines:
1471

Relevant Lines:
1561

💛  - Coveralls


Enforce clippy via bors

Now that we have a stable Clippy CI, we can enforce Clippy lints via bors.

The CI failure seems to be a dockerhub hickup. A rerun should probably work

bors retry


Add Kubernetes node name to exported labels

Right now, when dcgm-exporter is deployed in Kubernetes (we're using gpu-operator), the Hostname label is set to the pod name, which is not particularly useful. I'd like to suggest either:

Adding a new label node or
Using different logic to populate Hostname when running in Kubernetes

It should be fairly straightforward to inject the node name into the container using the Downward API.

Would it be possible to have labels in general added as well? We have kubernetes pods that have label.app=dev for example and these are not visible in DCGM metrics

@neggert as workaround right now you can do it from the Prometheus dcgm-exporter job side. You need kube-state-metrics exporter or something like that, then you can do relabel_config. For example:
- job_name: dcgm-exporter
  scrape_interval: 30s
  scrape_timeout: 10s
  kubernetes_sd_configs:
    - role: endpoints
  relabel_configs:
    - source_labels: [__meta_kubernetes_endpoints_name]
      regex: 'dcgm-exporter'
      action: keep
    - source_labels: [__meta_kubernetes_namespace]
      action: replace
      target_label: namespace
    - source_labels: [__meta_kubernetes_pod_name]
      action: replace
      target_label: pod_name
    - source_labels: [__meta_kubernetes_pod_node_name]
      action: replace
      target_label: node

result
DCGM_FI_DEV_FB_FREE{UUID="GPU-16e319ba-0b7d-3a4b-e35f-915bf484870f", cluster="test-cluster01", device="nvidia0", gpu="0", instance="<IP_ADDRESS>:9400", job="dcgm-exporter", namespace="dcgm-exporter", node="node06", pod_name="dcgm-exporter-k22f5"}

Hey, i have solved this by adding some relabeling to my ServiceMonitor.
I also overwrote the instance label so I don't have to customize my grafana boards.
apiVersion: monitoring.coreos.com/v1
kind: ServiceMonitor
...
spec:
  endpoints:
  - relabelings:
    - action: replace
      sourceLabels:
      - __meta_kubernetes_pod_node_name
      targetLabel: nodename
    - action: replace
      sourceLabels:
      - __meta_kubernetes_pod_node_name
      targetLabel: instance
    ...

I needed node_ip and hostname to join DCGM metrics to Node Exporter metrics.
I used the following relabelings in my ServiceMonitor to add node_ip and hostname labels to all DCGM metrics:
spec:
  selector:
    matchLabels:
      app: nvidia-dcgm-exporter # target service
  namespaceSelector:
    matchNames:
      - nvidia-gpu-operator
  endpoints:
    - port: gpu-metrics
      interval: 5s # Scrape interval
      relabelings:
        - sourceLabels: ["__meta_kubernetes_pod_host_ip"]
          regex: "(.*)"
          replacement: "$1"
          targetLabel: "node_ip"
        - sourceLabels: ["__meta_kubernetes_pod_node_name"]
          regex: "(.*)"
          replacement: "$1"
          targetLabel: "hostname"

How can I get the name of the pod which is actually using the GPU ? Right now what we get is the name of DCGM-Exporter and the job name is being populated with gpu metrics job name.

@thekuffs Can you elaborate on how to do this?
I've got a GPU node which is running two pods: dcgm-exporter and a workload which uses the GPU. Id like to be able to associate that workload with the metrics exposed from dcgm-exporter.
How exactly is this done? I understand how to do the pod role with kubernetes_sd_configs, but not clear how this helps the problem. I can target my workload through this, but my workload doesnt expose a /metrics endpoint (only dcgm-exporter does). I can target the dcgm-exporter pod, but then im still not sure how to associate those with the workload.

@francescov1 I think I was just wrong when I posted that comment. I had forgotten that available GPU resources can be shared among multiple pods. If your workload is 1:1:1 (gpu:pod:node) you can use something like the cadvisor/kubelet metrics to "join" between dcgm metrics and your own workload. i.e. there are metrics in cadvisor/kubelet that have both a pod and a node label. You can select those by your workload's pod name. You can join those against themselves to find the specific instance of the dcgm exporter for that node. Which you can use to find the dcgm metrics for the node your workload is running on.  Like I said though, that requires you to be allocating the entire GPU on a node to a single pod.
So, I apologize for my comment. I made a few other comments on other similar issues without thinking thoroughly about it.

@thekuffs Thanks for the insight, this is exactly what I need. Will give it a shot!


Fix minimum order pct and abs

This might fix issues of having an order commission under precision.
Also, I don't know why "value" was calculated before, since size is already the order size expressed in base asset, and it's not used anywhere else.
@rhamnett can you doublecheck this?
LGTM anyway

To solve the issue reported on discord, you can just set min_order_abs to something like 100.0, and it will never try to make an order of 0.01usd with 0.0001usd commission, which for example triggers commission under precision

@rhamnett I managed to get rewards and so on with this implementation. Aside from the "size" nomenclature, if you find that working for you too, I suggest merging as-is (to fix the bug) and then evaluating the nomenclature change at a later time

The bug I was eperiencing is tracked down to an issue in Ray 2.0.0 dev. Merging now.


Improve mapping interpolation with k>1 when NaN values are present

Currently, we use RectBivariateSpline, so have to replace NaN pixels with some value before interpolating (currently just set to 0). Even though we later mask any projected NaN pixels (with _should_propagate_nan_to_map), this can produce edge effects near NaN pixels when using e.g. cubic splines.
It would make more sense therefore to either:

Replace NaNs with a more appropriate constant value before interpolating - e.g. the median value of the image rather than 0. This would be the easiest to implement, and have negligible performance impact.
Replace NaNs with locally derived value before interpolating - e.g. do nanmean of 3x3 footprint around each pixel. This would cost more performance, but provide better results for variable data.
Use a different interpolation method that doesn't require a regular grid - probably using bisplrep or griddata.

Could do locally derived value fixing with something along the lines of
def clean(img: np.ndarray) -> np.ndarray:
    nans = np.isnan(img)
    cleaned = img.copy()
    cleaned[nans] = np.nanmedian(img)
    to_fix = nans & ~scipy.ndimage.uniform_filter(nans, size=3)
    for i, j in np.argwhere(to_fix):
        cleaned[i, j] = np.nanmean(img[max(i - 1, 0) : i + 2, max(j - 1, 0) : j + 2])
    return cleaned

griddata clearly performs best at keeping original variation with no influence from NaNs, so think we should use that as the default method. Can keep RectBivariateSpline as an option for e.g. if smoothing is wanted.

From futher testing, griddata doesn't seem as great:

It can become prohibitively slow for larger (~1000px) datasets, as it needs to construct a triangulation.
The results can be unstable and dependent on the system (see failing tests only on GitHub's macOS workers). It seems like this is probably again due to the triangulation, which doesn't necessarily have a unique solution, and can therefore be affected by floating point errors.

I think this probably therefore rules out griddata, as e.g. we don't want unstable mapping results to be interpreted as changes in the target etc.
Scipy's RegularGridInterpolator seems to perform really nicely (and quickly) when paired with our custom _replace_nans_with_interpolated_values, so this is probably the way to go.


Add superflat world generation

A supersimple superflat world generator.
Related issue:
#129

@mastercoms  Good to go.

Thanks!


an empty NavigationView panel slides in from the right side, when used in top configuration on Hololens 2 when used with an xbox controller

Describe the bug
As it says in the title. It happens every time when use it in a 2d app on HoloLens 2 and a bluetooth connected xbox controller, I use pivot instead for now. It is strange since I have used the top layout, and still an empty opaque panel slides over my content.
Steps to reproduce the bug
Create a navigation panel on a blank xaml app, set it to use top layout instead of left side. Get a HoloLens 2, and pair an xbox controller, open the app (maybe repeatedly) and it start happening. I could not reproduce the issue on desktop or without the controller.
Please note that I have used the 2d app as a secondary view in an immersive HoloLens app, the issue started happening when I closed and reopened the view with the controller.
I expect you can check how the left panels, background could slide in when in top configuration. Please note that this also happens in left configuration as well, in that case it does slide over the actual open panel with items, and occcludes it with an empty panel.
Expected behavior
The left panel cannot be displayed in top confgiuration in any way, anywhere, with any input device.
Screenshots

I do not have the device at me anymore.
Version Info

NuGet package version:

I am using Windows SDK 18362 with c++/winrt + xaml.

Windows 10 version
Saw the problem?

Windows Holographic 2020 2B (february update)
Yes

Insider Build (xxxxx)

November 2019 Update (18363)

May 2019 Update (18362)

October 2018 Update (17763)

April 2018 Update (17134)

Fall Creators Update (16299)

Creators Update (15063)

Device form factor
Saw the problem?

Desktop

HoloLens 2
Yes

Mobile

Xbox

Surface Hub

IoT

Additional context

@axodox Are you using Microsoft.UI.Xaml.Controls.NavigationView from the WinUI nuget package or Windows.UI.Xaml.Controls.NavigationView ? Some screenshots, video would be helpful to understand the issue.

Windows.UI.Xaml.Controls.NavigationView from the windows sdk

@axodox Can you give the one from WinUI prerelease package a try ? There have been several fixes made to that control compared to the one that shipped in the Windows namespace.


Mirror directory to CashCtrl server

Adding functions mirror_directory() and list_files() to CashCtrlAPIClient, with a corresponding unit test. Those functions allow to recursively sync a local directory on the CashCtrl server, and to list remote files.

No human around for review. Asking ChatGPT:
Review methods `mirror_directory()` and `list_files()`. Then review the corresponding unit tests in test_mirror_directory.py. Provide review in markdown format for download.

Thanks ChatGPT, for your comments:
I find the following comments most pertinent:

Logging would be helpful for debugging, adding the logging module is planned at a later stage.
Pagination at the API level will most likely be necessary in the future.
Batch operations for file upload would certainly improve update performance (but potentially will lead to pacing of API requests from the server side).

I declare the current state to be good enough for a first version and go ahead with merging :)


feat: upgrade to angular v14

re #41

Codecov Report
Patch and project coverage have no change.

Comparison is base (8938fe8) 100.00% compared to head (7f17666) 100.00%.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
Additional details and impacted files
@@            Coverage Diff            @@
##              main       #58   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files            6         6
  Lines           63        63
  Branches         7         7
=========================================
  Hits            63        63

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


tfsec v0.53.1 new checks causing failures

Describe the bug
The new AWS checks (api gateway cache settings) that were introduced in tfsec v0.53.1 are causing failures in our CI builds. We don't have caching enabled so it's simply the default rules it doesn't like:
resource "aws_api_gateway_method_settings" "api_post_method_settings" {
  rest_api_id = aws_api_gateway_rest_api.private_api.id
  stage_name  = aws_api_gateway_stage.private_api_prod_stage.stage_name
  method_path = "XXX/XXX/XXX"

  settings {
    logging_level      = "INFO"
    data_trace_enabled = true
    metrics_enabled    = true
  }
}

Usually we would be able to find the AWS code and add it to our ignore list, but I can't find it in the docs. The first link provided by the error (https://tfsec.dev/docs/aws/apigateway/enable-cache-encryption#aws/apigateway) is also incorrect as it leads to a page not found.

Could you please provide guidance on what is the correct AWS code to add to our ignore list? It would be great if the docs were updated ahead of time so when we encounter the failure, we can use the docs to add the code to our ignore list.
Is there a place we can track to see upcoming changes?

Thanks!
To Reproduce
Steps to reproduce the behavior:

Install tfsec v0.53.1
Run against AWS API Gateway resource that doesn't have any caching enabled for its aws_api_gateway_method_settings
See below error

  [aws-apigateway-enable-cache-encryption][MEDIUM] Resource 'aws_api_gateway_method_settings.container_id_post_method_settings' uses default value for settings.cache_data_encrypted

...

  Impact:     Data stored in the cache that is unencrypted may be vulnerable to compromise
  Resolution: Enable cache encryption

  More Info:
  - https://tfsec.dev/docs/aws/apigateway/enable-cache-encryption#aws/apigateway
  - https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/api_gateway_method_settings#cache_data_encrypted

Expected behavior
This was a new check introduced so the failure we expect. It would be great to be provided the corresponding AWS code so we can either fix the issue or add the AWS code to our ignore list.
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):

OS: Linux (docker), MacOS

Additional context
Add any other context about the problem here.

Hey @johannesgiorgis-galvanize - the documentation build failed for this release so the new checks didn't get added.

The correct code for this is aws-apigateway-enable-cache-encryption
The imminent checks are in #763 - although a lot of these exist already. Very soon we will maintain a visible sheet of all the new to be checks

Sorry this has caused you a headache, we're looking at ways to catch the build failure sooner

v0.53.2 should be pushing the documentation and have a fix to this check.
documentation here - https://tfsec.dev/docs/aws/api-gateway/enable-cache-encryption/#aws/api-gateway

Thanks @owenrumney - appreciate the prompt response as always!


Implement spinlock on top of atomic api and remove up_testset

See the discussion here: https://github.com/apache/incubator-nuttx/pull/6283

@xiaoxiang781216
For example, cxd56xx needs to use up_testset API because the SoC has a restriction to use ldrex and strex.

Yes, in your case not only up_testset, but also atomic_xxx need rewrite for cxd56xx. The issue description is still right, it's better to use atomic api directly, but implement atomic api has different approach:

boolchain's bultin
libs/libc/machine/arc_atomic. for single core
chip special one(e.g. cxd56xx)

@hujun260 please look at this problem too.


docs: update multivariate anomaly detection - fabric doc edit

/azp run

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 1.88%. Comparing base (580f759) to head (9bca20a).

Additional details and impacted files
@@            Coverage Diff             @@
##           master   #2191       +/-   ##
==========================================
- Coverage   85.88%   1.88%   -84.01%
==========================================
  Files         329     329
  Lines       17086   17086
  Branches     1515    1515
==========================================
- Hits        14675     322    -14353
- Misses       2411   16764    +14353

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

/azp run


A non master-slave partition mode in process function

Hi Lion,
In ASDFDataSet.process(), you used the master-slave working mode. I think you introduce it mainly because of balancing the workload.
I had a discussion with @mpbl  about it and we think we should also have another job partition way(the tradition and simple way), which is partition the job prior to job running. For example, if we get 1000 stations and 10 cores, every processors would take 100 and they know which 100 they would take. The advantage of doing that is:

code is much easier, so more maintainable, less bugs.
scalable. If in the future we have 100000 stations, and we want to have 1000 cores. The master-slave may suffer from communications between cores.

The drawback:

we can't ensure workload balance. Under some extreme conditions, it will perform very poor.
However, if we shuffle the job queues, it won't be to bad.

What do you think? Worth adding such a method?

No activity in a while. Closing for now.


Set cache control to 1 month for each object

Added Cache-Control header to S3 object

@mpatek #reviewmerge?

Why 1 month? Shouldn't we do for infinity?

I think the maximum is 1 year. I can change to 1 year.
Best Regards,
Noppanit Charassinvichai aka Toy
twitter: @noppanit
On Tue, Jul 21, 2015 at 1:16 PM, Daniel Bachhuber
<EMAIL_ADDRESS>wrote:

Why 1 month? Shouldn't we do for infinity?
Reply to this email directly or view it on GitHub:
https://github.com/fusioneng/gif2html5-app/pull/48#issuecomment-123406591


Playback controls not available after selecting video from Timeline view

Checklist:

[x] I updated to the latest version available
[x] I cleared the cache of my browser

Release with the issue:
v5.2.0
Last working release (if known):
None
Browser and Operating System:
Google Chrome in Windows 11 and Home Assistant app in Android

Description of problem:

After opening the Timeline view in Home Assistant and selecting a moment in time when there is no events, the playback controls (i.e. pause, play, mute and jump to a different moment of the video) are not available
Frigate card diagnostic information

Javascript errors shown in the web inspector (if applicable):

Additional information:

After opening the Timeline view in Home Assistant and selecting a moment in time when there is no events, the playback controls (i.e. pause, play, mute and jump to a different moment of the video) are not available

You mean the native video controls in the video player itself? Can you take a screenshot / video capture to show what you mean?

Yes, the native video controls are not available so the video cannot be paused or jump. This is an screenshot of the normal video with the controls available:

After selecting a moment in time in the timeline, for example this one marked with a blue X in this screenshot:

Controls are not available anymore:

Weird! Thanks for the screenshots. Mind including your card config so I can attempt to reproduce?

Don´t you have the same issue? I thought it would happen to everyone

[Issue cleanup] If you still have issues with this, please try the latest release (https://github.com/dermotduffy/frigate-hass-card/releases/tag/v6.0.0-beta.4) first and re-open this. Thanks and good luck!
(A quick check by clicking on a random spot on the timeline does not show the issue for me, at least with the new builds)


predict owner mail when creating new server

when you setup a new server you have a little box for the owner email, what if the box would predict the mail that you are typing in via a little dropdown?
picture as example:

(its a small touch, but its nice to have :) )

Only issue is privacy. I could go in and start typing letters and get emails of users. Then use that for spam, worse case scenario. Just another reason why I want to use username aliases. >.>

@koo04 This says new server though, which means there is an admin doing it, so "privacy" at that point could be questionable.

Sure, but admins can be dicks too. I just know that things regarding other account emails has been brought up in the past. The admins should just know the emails that are needing to be invited.
Now, this could be nice for PufferPanel admins in the back end. When adding a new server, I would love to either get a full list or get a drop down like the suggestion.

Nice!
Op wo 11 feb. 2015 20:16 schreef Dane Everitt<EMAIL_ADDRESS>
https://camo.githubusercontent.com/f4483a58dab168e81a10819f9f6a265a86447640/687474703a2f2f73332e6b656c702e696e2f58374247612e706e67
—
Reply to this email directly or view it on GitHub
https://github.com/PufferPanel/PufferPanel/issues/427#issuecomment-73944620
.