fix: add dropbar_menu to excluded_filetypes

Add dropbar.nvim's dropbar_menu filetype to the list of excluded filetypes

Thanks for the PR. Been meaning to try out dropbar, looks cool


@supabase/supabase-js TypeScript types - on join query

Bug report

[x] I confirm this is a bug with Supabase, not with my own application.
[x] I confirm I have searched the Docs, GitHub Discussions, and Discord.

Describe the bug
Types generated for TypeScript, based on the query content are not correct:
Query
const result = await dbServerClient
      .from('table_1')
      .select(
        'processed, created_at, table_2:table_2_id (name, table_3:table_3_id (name, image))',
      )
      .eq('id', id)

Provided type
PostgrestSingleResponse<{
    processed: any;
    created_at: any;
    table_2: {
        name: any;
        table_3: {
            name: any;
            image: any;
        }[];
    }[];
}[]>

Type in reality
PostgrestSingleResponse<{
    processed: string;
    created_at: string;
    table_2: {
        name: string;
        table_3: {
            name: string;
            image: string;
        };
    };
}[]>

Additional context
In theory difference is small, but it makes big types issues, since casting is required to make it work correctly.

A fix for this would be greatly appreciated. Without this I'm still writing out types manually.

@sethtjf I suggest you to use zod for validation

Ah! I spent quite some time looking for a solution to this in the docs and elsewhere on the internet. I guess overriding the type is the only way for now.

A fix has been released in supabase-js v2.46.0. I'm closing this issue, but feel free to reopen if you encounter any further errors.


Playing with an Audit filter

Type of change
Select the type of your PR

Enhancement / new feature

Description
I've had some ideas about an auditing filter bumping around in my head for a few weeks.  I wanted to see how they look.
Please don't expend effort reviewing this work right now.
Please describe your pull request
Additional Context
Why are you making this pull request?
Checklist
Please go through this checklist and make sure all applicable tasks have been done

[ ] Write tests
[ ] Make sure all tests pass
[ ] Review performance test results. Ensure that any degradations to performance numbers are understood and justified.
[ ] Make sure all Sonar-Lint warnings are addressed or are justifiably ignored.
[ ] Update documentation
[ ] Reference relevant issue(s) and close them after merging
[ ] For user facing changes, update CHANGELOG.md (remember to include changes affecting the API of the test artefacts too).

Will come back to this later, closing.


Optional options

[CommandOption("--memory")]
public long? Memory { get; set; }

I've tried like that
[CommandOption("--[memory]")]
public long? Memory { get; set; }

and
[CommandOption("[memory]")]
public long? Memory { get; set; }

and
[CommandOption("--memory")]
[DefaultValue(null)]
public long? Memory { get; set; }

Nothing works. How can make option optional?

Could you elaborate what you're trying to achieve and what's not working. All options are optional by default.


Output archive requests json with no indent by default

Ouput the archive json with no indent by default, so it is only on 1 line. This makes it easier to handle the file afterwards, like concat into a jsonl file.

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

Project coverage is 75.00%. Comparing base (b1d2560) to head (c2860c8).

Additional details and impacted files
@@           Coverage Diff            @@
##           develop      #74   +/-   ##
========================================
  Coverage    75.00%   75.00%
========================================
  Files            1        1
  Lines            4        4
========================================
  Hits             3        3
  Misses           1        1

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


params are shown in the mermaid graph but apparently not used?

params are shown in the mermaid graph but apparently not used?

Fixed by #2


This is an issue with the Clockwork package, the necassary fixes for clockwork compatibility were made in this commit https://github.com/itsgoingd/clockwork/commit/e7bd05b9a9edd586381c81187c9aa0ef25538499 but it has not yet been pushed to a release yet. In the meantime, you can either disable clockwork, revert to 5.7, or swap out your dependency with the master branch (not recommended)

I had this on one of my upgrades.
Have you run php artisan cache:clear? - does that solve it?

I had this on one of my upgrades.
Have you run php artisan cache:clear? - does that solve it?

I've tried but no success

Fixed thanks to @ajoy39 !

If the above solutions doesn't work for anyone, I had this problem because of Telescope.

You're right, @yamenarahman, this was fixed in https://github.com/laravel/telescope/pull/583 and released for the v2

I had this problem as well. I have done a shift from Laravel 5.7 to 5.8 and suddenly had this issue. Copying and pasting themsaid words:

Everyone, please make sure to use Telescope 2.0 on Laravel 5.8, or Telescope 1.0 on Laravel 5.7.

https://github.com/laravel/telescope/issues/568

I had the same problem with Laravel 5.8 and Telescope 2.1. It was solved by updating Clockwork package: I had clockwork v.2.2 and it was upgrade to 4.0


T-SQL editor is querying sys.dm_cluster_endpoints even if doesn't need to...

Issue Type: Bug
Subject says it all. Every new T-SQL window is trying to query the BDC DMV. This is not necessary.
Azure Data Studio version: azuredatastudio-insiders 1.14.0-insider (a7f597c9431c2ee82e6175eb744c328e8c680019, 2019-10-28T07:38:19.274Z)
OS version: Windows_NT x64 10.0.19008

System Info

Item
Value

CPUs
Intel(R) Core(TM) i7-7820HQ CPU @ 2.90GHz (8 x 2904)

GPU Status
2d_canvas: enabledflash_3d: enabledflash_stage3d: enabledflash_stage3d_baseline: enabledgpu_compositing: enabledmetal: disabled_offmultiple_raster_threads: enabled_onoop_rasterization: disabled_offprotected_video_decode: enabledrasterization: enabledskia_renderer: disabled_offsurface_control: disabled_offsurface_synchronization: enabled_onvideo_decode: enabledviz_display_compositor: enabled_onviz_hit_test_surface_layer: disabled_offwebgl: enabledwebgl2: enabled

Load (avg)
undefined

Memory (System)
31.85GB (17.95GB free)

Process Argv

Screen Reader
no

VM
0%

Extensions (8)

Extension
Author (truncated)
Version

ssmskeymap
kev
1.1.0

admin-tool-ext-win
Mic
0.0.2

agent
Mic
0.43.0

azuredatastudio-postgresql
Mic
0.2.2

dacpac
Mic
0.7.0

import
Mic
0.11.0

profiler
Mic
0.10.0

sql-vnext
Mic
0.16.0

(1 theme extensions excluded)

Hi @uc-msft can you describe the customer impact?

I'm unclear how this is a notebooks issue. This appears to be related to BDC, as when I start Profiler and do a query in the query editor, we see the following:
SELECT [name], [description], [endpoint], [protocol_desc] FROM .[sys].[dm_cluster_endpoints];

@kevcunnane can you help here?

This is a SQL Tools Service thing. We're doing this when gathering the server info (which is done for pretty much every connection)
We can look into scoping this down or not fetching it unless we need it but in general this is like the server version query we/SSMS does and shouldn't have a huge customer impact. Although in this case the DMV is probably doing more than a single version lookup so there might be perf considerations if we're running this a lot.
I don't believe we've gotten any customer complaints about this though so I'm inclined to say we leave it unless we have actual reasoning as to why this would negatively impact customers.

For every new connection we run some basic queries to get server state. I can see a future optimization where we already know this is cached (e.g. if there's a single connection to a server, no need for additional information) but it's likely that changing DB might mean we need to refresh this (for example to detect SQL DB vs. DW where at server level they're the same, handle DB compat).
I'd be inclined to close this as "by design" for now and see if down the line we need to optimize whether we need to query server/db info when we've already connected somewhere in the tool. For now, closing but willing to reopen if we have solid customer data of an impact here.


New Publisher Added - Bohemian Visual Recognition Alliance

Including Inception V4 model for mushroom recognition.

@googlebot I fixed it.

@googlebot I fixed it.

Hi Lukas and thanks for contributing. There seem to be some issues with the contributions that we'll need to address before continuing.

Although you have agreed to CLA, the commits have likely a different e-mail address than the one used for CLA (typically one would do git config --global user.email<EMAIL_ADDRESS>to set e-mail address for commits).

The model has to be hosted on a https location (we can't read via this drive link). Some ideas for hosting include: GitHub release, GitHub FS, or Google Cloud Bucket.

Hi Vojtěch,
thank you for fast feedback.
First, the email I’m using is the same (lukaspicek@gmail.com). I will explore it more.
Second, I will use the Google Cloud Bucket https://cloud.google.com/storage/docs/creating-buckets. Looks good.
Lastly, I’m adding the Christine as my Google / TF Hub „contact person“.
Best,
Lukas

2020 v 13:55, Vojtech Bardiovsky<EMAIL_ADDRESS>

Hi Lukas and thanks for contributing. There seem to be some issues with the contributions that we'll need to address before continuing.
Although you have agreed to CLA, the commits have likely a different e-mail address than the one used for CLA (typically one would do git config --global user.email<EMAIL_ADDRESS>to set e-mail address for commits).
The model has to be hosted on a https location (we can't read via this drive link). Some ideas for hosting include: GitHub release https://help.github.com/en/enterprise/2.13/user/articles/creating-releases, GitHub FS https://git-lfs.github.com/, or Google Cloud Bucket https://cloud.google.com/storage/docs/creating-buckets.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub https://github.com/tensorflow/hub/pull/580#issuecomment-627933257, or unsubscribe https://github.com/notifications/unsubscribe-auth/ACLEJ44F676X75NVCNFTNPDRRKDE3ANCNFSM4M7EZJBA.

@googlebot I fixed it.

Thanks for fixing the model location.
The commit e-mail now looks good to me, but I think the issue is that you have several commits and some are still from the last e-mail, so it will need some more work. I found this guide internally

After updating GitHub configuration here, you need to follow the steps below to update author info, if you have already created commits before having properly configure .gitconfig.

If only the most recent commit needs update, run: git commit --amend --reset-author
If there is more than one commit to update. Use git rebase -i.
Type e or edit on the commits you want to update.
For each commit, run: git commit --amend --reset-author and git rebase --continue
A force push to remote branch is required if you have pushed your branch before.

Or alternatively you can just simply create a new PR if that's less work.

Looks like it passed in another pull request with squeezed commits.
LP

2020 v 16:06, Vojtech Bardiovsky<EMAIL_ADDRESS>

Thanks for fixing the model location.
The commit e-mail now looks good to me, but I think the issue is that you have several commits and some are still from the last e-mail, so it will need some more work. I found this guide internally
After updating GitHub configuration here, you need to follow the steps below to update author info, if you have already created commits before having properly configure .gitconfig.
If only the most recent commit needs update, run: git commit --amend --reset-author
If there is more than one commit to update. Use git rebase -i.
Type e or edit on the commits you want to update.
For each commit, run: git commit --amend --reset-author and git rebase --continue
A force push to remote branch is required if you have pushed your branch before.
Or alternatively you can just simply create a new PR if that's less work.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub https://github.com/tensorflow/hub/pull/580#issuecomment-628012380, or unsubscribe https://github.com/notifications/unsubscribe-auth/ACLEJ42OX62AWV2UH7JLIUDRRKSNZANCNFSM4M7EZJBA.


Connect to multiple BLE Servers

Hello.
Looking to connect to multiple BLE Servers, bike HR and Power Meter.
I can succesfully connect to each device individually, but cannot figure out how to have to connections going on simultaniusly. I cannot do round robin as i need to get updates every second for each sensor.
Any one having example code connecting to multiple server?
Regards Kasper

@kasperkls02 you need to create a BLEClient instance for each connection, connect to the first with instance 1, scan, then connect to the second with instance 2 etc..

@h2zero I've tried this myself with a couple of servers (one BLEClient each), and while it seems perfectly content to connect to both of them, subsequently trying to disconnect from either one disconnects both at the same time.
Is that expected behaviour? I would've thought using BLEClient->disconnect() would only have disconnected that specific server.

@NbrTDB That is not the expected behavior. I have not seen this in my testing, I will try to reproduce that result when I get home.

@h2zero Thanks for the quick response! I don't suppose you could let me know what modifications need to be made when you have a moment? I have been poking around the library but must confess I haven't figured out what needs to change. Any suggestions would be much appreciated.

I don't have access to my files at the moment and honestly I'm not sure anymore as to the specific code I changed as it's been a couple years since I did it. I use NimBLE now and I have ported this library to use it and fully supports multiple connections.
Unless you have a specific reason to use bluedroid I'd suggest trying my NimBLE repo.
You can check it out here or here (arduino) if you're interested.
I'll have a look to see what code changes need to made to this repo anyway when I get home.

Found the modifications, there are many in this file but I think the only one needed to fix this is to change all the instances of
if(m_gattc_if != gattc_if)
    break;

to:
if(m_gattc_if != gattc_if)
    return;

in the BLEClient::gattClientEventHandler


Can't find this <React/RCTViewManager.h>

In case if I replace #import <React/RCTViewManager.h> to #import "RCTViewManager.h" everything is OK!!!
iOS developers help me! What wrong with it?

Got same issue here. Then I tried this and resolved it. https://github.com/facebook/react-native/issues/12042#issuecomment-275025960

Yes could be fixed by adding this construction to BVLinearGradientManager.h:
#if __has_include(<React/RCTViewManager.h>)
#import <React/RCTViewManager.h>
#elif __has_include("RCTViewManager.h")
#import "RCTViewManager.h"
#else
#import "React/RCTViewManager.h"   // Required when used as a Pod in a Swift project
#endif

Are you using an older version of react native?
If you're using React Native < 0.40 you'll want to use v1.x of this package (npm install --save react-native-linear-gradient@^1.6.2). v2.x is for RN >=0.40. At this point that's really the only difference between the two.

Sorry, but I am closing this issue. Please refer to https://github.com/react-native-community/react-native-linear-gradient/pull/150#issuecomment-290373936 for explanation.


Get instance from dom element

Is there any way to get instance from dom element?

...

find → https://pqina.nl/filepond/docs/patterns/api/filepond-object/#methods

Hello. Thank you for your quick response. Can you write a simple example please? It is not clear for me. Maybe like this?
document.querySelector( '.my-custom-uploader-1' ).FilePond.getFile();

FilePond.find(document.querySelector(“.my-class-name”));

OK. Thank you so much.


Secure grpc connection

Hello, I cannot make it work with secure connection.
Is Mediator proxying secure grpc requests/responses?
(I am using Dart for prototyping, maybe I should try another language?)

Plz check the readme
https://github.com/ButterCam/Mediator#https-support

Thank you, the problem was in server rules settings


Check for missing i18n strings when running tests

Depends on https://github.com/DFE-Digital/dfe-complete-conversions-transfers-and-changes/pull/700
We have had several instances of i18n strings being missing from locale files. This initializer will cause the test suite to report failures if any i18n locales are missing. It will only be run in test, and not cause any issues in dev or production modes.

I think it will massively help the content people!


Add Hubspot extenstion

Description
Hubspot extension allows you to search Hubspot contacts and deals with raycast.
Screencast

Checklist

[x] I read the extension guidelines
[x] I read the documentation about publishing
[x] I ran npm run build and tested this distribution build in Raycast
[x] I checked that files in the assets folder are used by the extension itself
[x] I checked that assets used by the README are placed outside of the metadata folder

messed up the pr . Tried to to upload the folder in the fork.


Options | Add icons to all buttons

Some buttons on the Options page (like "Refresh now", "Add new option" and "Undo recent changes") don't has any icon inside. We should add icons to make them more consistent with other buttons.

done via #48


Shell "select" method

I think it would be useful to have a Thor shell command for selecting from a list of options. This is fairly common in CLI applications, e.g.:
$ gem uninstall rspec

Select gem to uninstall:
 1. rspec-2.14.1
 2. rspec-3.0.0
 3. rspec-3.1.0
 4. All versions
>

The closest Thor currently has to this behavior is:
gems = ['rspec-2.14.1', 'rspec-3.0.0', 'rspec-3.1.0', 'All versions']
ask 'Select gem to uninstall: ', { :limited_by => gems }
# Select gem to uninstall:  [rspec-2.14.1, rspec-3.0.0, rspec-3.1.0, All versions]

I do like the autocomplete support to select by value via Thor ask, but it isn't a good solution for long lists or long names since it displays an inline list rather than the question, list, then prompt format in the original example above.
In fact, to support very long lists my ideal implementation would:

Be paginated
Allow selection by row number (like the gem example)
OR allow selection by value (with autocomplete) like ask ... :limited_by
Select directly from a list of objects (using to_s or another callback to determine display names) so the caller doesn't need to use list.find on the results.

Basically something that behaves like this, where both 4 or Auto Scale - List scaling groups are equivalent selections:
Which API would you like to test?
1.  Cloud Identity - List Users
2.  Cloud Identity - Reset user API key
3.  Cloud Identity - List Credentials
4.  Auto Scale - List scaling groups
5.  Cloud Big Data - View profile information
(Press return for more options)
>
6.   Cloud Queues - Get home document
7.   Cloud Databases - List versions
8.   Cloud DNS - Update PTR records
9.   Cloud Identity - Get version details
10.  Cloud Images - List images
(Press return for more options)
>
11.  Cloud Images - Get images schema
12.  Cloud Networks - List Routers
13.  Cloud Databases - List All Compute Hosts
14.  Cloud Networks - List Networks
15.  Cloud Networks - List Networks
(Press return for more options)
>  Auto Scale - List scaling groups

@maxlinc @ezekg Though your requirement for list menu is quite often necessary in building CLI apps, I think it maybe slightly out of scope for thor. I would prefer for thor to be 'mighty hammer' rather than 'swiss army-knife'  for CLI development. I'm not a thor maintainer, therefore I cannot express the views for the future of the library but my own. If you are still interested in this functionality, I've been recently working on library that helps building user prompts tty-prompt.

That looks pretty awesome @peter-murach, thanks for sharing.


Client cannot make API calls when running in Dev Tunnel

I'm trying to use Dev Tunnels with my Blazor .NET client application.  I also have a REST API project (.NET 7) that the client utilizes.
The API is hosted in Azure, but I cannot get the client to make successful API requests when the client is running in a Dev Tunnel.
In Fiddler, I see the client making HTTP OPTIONS /protected/Provider HTTP/1.1 requests, but no other HTTP verbs are used in any requests.
I updated the CORS settings for the API to include the client dev tunnel URL (the actual settings file does not have any x 'd-out data).
"CorsPolicySettings": {
"Origins": [
"https://localhost:7094",
"https://xxxxxxxx-7094.use2.devtunnels.ms/"
]
},
What am I missing?
I set up a dev tunnel for the API running locally on my machine, and I can connect to it with the client just fine when the client is not using a dev tunnel.  But when I switch the client to a dev tunnel, I have the same issue where no API requests are made - just the HTTP OPTIONS.
Here is an example header from an HTTP request:
Request URL:
https://xxxxxxxxxxxxxxxxxx.azurewebsites.net/protected/Provider
Request Method: OPTIONS
Status Code: 204 No Content
Remote Address: <IP_ADDRESS>:8888
Referrer Policy: same-origin

So the client (Blazor application) is running locally on localhost:7094 and also on the dev tunnel at https://xx-7094.use2.devtunnels.ms. The API project is running on Azure at https://xx.azurewebsites.net/protected/Provider.
When you visit https://xx-7094.use2.devtunnels.ms, the client is unable to make the request to https://xx.azurewebsites.net/protected/Provider but it works when using the client running on localhost:7094.
Is that correct?
If so, it may be that the updated CORS settings are not taking effect on your Azure Website.
Right now, I don't see how dev tunnels would be involved since the request is being made to https://xx.azurewebsites.net/protected/Provider.

API app using dev tunnel/WebAssembly app using dev tunnel and both running locally:
Access API from WebAssembly app: fails
Access API from Postman: succeeds
The API app includes the dev tunnel URL for the WebAssembly dev tunnel.
I have tried also only running the WebAssembly app dev tunnel locally, and having it connect to the API when it is hosted in Azure, but I have the same issue.  The CORS settings do not change when our pipeline builds and deploys the API.
The CORS policy is (x's replacing actual values):
  "CorsPolicySettings": {     "Origins": [       "https://localhost:7094",     <-------The WebAssembly when run locally without a dev tunnel (this works)       "https://xxxx-xxxx-xxxxxxx.1.azurestaticapps.net",       "https://xxxxxx.com",       "https://xxxxxxxx-7094.use2.devtunnels.ms/"   <-----The WebAssembly dev tunnel     ]   },

Thank you for looking at this.  We have resolved the issue.
I was able to add a wildcard CORS entry in my appsettings for the API and things worked (https://*devtunnels.ms/).  It looks like this:
"CorsPolicySettings": {
"Origins": [
"https://localhost:7094",
"https://*devtunnels.ms/"
]
},


Want to Create - Info Alert

Reference to Component

Will add under Alert folder
Good luck.

@myGlitches go ahead

Thanks ! @rupsha014

Done

Also, @Rajdip019  @rupsha014 is it possible to mention the Figma file and how to contribute, directly in the description for newbies like myself? Can change the doc if you want me to

Hey, @myGlitches . We are not giving users to change the Figma file.

No , I meant something else and I saw it is already mentioned ! My bad sorry ~ hehe


Update Garden clients at runtime

How to categorize this issue?

/area quality
/ area robustness
/kind enhancement
/priority normal
What would you like to be added:
Make it possible to transparently update the Garden Cluster clients at runtime.
With the introduction of the client map concept, it is possible to refresh clients when the underlying kubeconfig stored in a secret changes.
This is implemented for Seed and Shoot clusters only.
What we need is to

refresh the garden clients in the garden client map (similar to how it is implemented for the seed and shoot client map)
a solution to exchange the clients used by the SharedInformers throughout the project. Possibly replace the direct usage of SharedInformers with e.g the ControllerRuntime.

I understand that the latter is a bigger task, but I wanted to raise the issue already to collect thoughts and ideas.
Why is this needed:
The garden cluster client credentials are not guaranteed to be stable. For instance due to

Certificate rotation performed by the  Gardenlet

After certificate  rotation, the Gardenlet needs to self terminate in order to get the new credentials when the new pod comes up

Operator wants the Gardenlet to act on another Garden cluster - updates the Garden kubeconfig

The Gardenlet currently does not detect changed credentials for the Garden cluster nor updates the clients & Informers. The Gardenlet still targets the "old" cluster.

Regarding Certificate Rotation: Currently this is an event happening once a year, but I envision offering functionality like the kubelet's  -experimental-cluster-signing-duration  to control the client certificates lifetime.

@tim-ebert can explain it in detail, but what I understood from a discussion with him is that it's very complex/not even clear from the current design's perspective to achieve a dynamic refreshment of the garden client.
IIUC the certificate rotation of the gardenlet is the only real use-case (I don't understand the second point, sounds artificial to me, can you explain more about it).
Even if we lower its client certificate validity duration I don't think that restart of the gardenlet is problematic given that we omit additional code/complexity.
So, my take on this would be: If there is an easy, straight-forward way to achieve this behaviour then sure, let's do it, but if not, then let's not do/postpone it in favor of tasks with a higher priority.

@tim-ebert can explain it in detail, but what I understood from a discussion with him is that it's very complex/not even clear from the current design's perspective to achieve a dynamic refreshment of the garden client.

Indeed, I don't see any way how the configuration of client-go style ClientSets, Informers or Listers can be changed at runtime. Maybe I miss something here, if you see such possibilities, I would be very interested to look into them.
As we rather heavily rely on Informers and so on in our controllers and don't have any way of refreshing them, we need to shutdown the gardenlet in order to recreate them, when its certificate is changed.
BTW: the same also applies to the Informers obtained from a runtime cache from a ClientMap. So if you change a Seed Secret for example and you obtained some Informers from a runtime cache from the ClientMap, they will be stopped by the ClientMap, so they will receive no more watch events. That in turn means, that controllers relying on such informers will have to get a new client again and start watching with new Informers. Fortunately, we currently only rely on generated Informers, that are statically initialized, but that will change with #2516. So we will have to somehow refresh the Informers we use there in order to receive further watch events (cc @timuthy).

If there is an easy, straight-forward way to achieve this behaviour then sure, let's do it, but if not, then let's not do/postpone it in favor of tasks with a higher priority

Agree. I am not advocating to tackle the issue right now but to keep in mind that we have some technical debt here in my opinion.
I think it makes sense to leave this issue open and revisit it when we see more reasons to switch to the controller runtime clients.

Indeed, I don't see any way how the configuration of client-go style ClientSets, Informers or Listers can be changed at runtime. Maybe I miss something here, if you see such possibilities, I would be very interested to look into them.

No I do not. I see that as a reason to harmonize the client usage in the GCM, Gardenlet and extensions to all use the controller runtime clients.

That in turn means, that controllers relying on such informers will have to get a new client again and start watching with new Informers.

That would be possible at runtime, right?

Agree. I am not advocating to tackle the issue right now but to keep in mind that we have some technical debt here in my opinion.

TBO, I don't really get, why this would be a technical debt. Can you elaborate, why you think so?
We have a lot of other components that are simply restarted if their configuration changes (see the Pod checksum annotations in many of our deployments). And I guess, this is also the "cloud-native" way to do things. Rather kill your workload to see it get restarted cleanly with the correct configuration instead of reloading configuration. And I think, doing so is a well-established mechanism in the kubernetes space and I don't see any problem with it. The only place, where such mechanisms are not desired is for stateful workload, that might take some time for being restarted (e.g. prometheus) and for such workload, there are other means to reload configuration (e.g. the prometheus-config-reloader sidecar).
But as the gardenlet is not a stateful component and can start up quite fast, it doesn't hurt if it shuts down itself ~once a year for rotating its certificate. In between it might have been killed/restarted hundreds of times by the VPA or version upgrades or whatever...
I was also thinking about how other controllers for custom resources in kubernetes do such things.
I guess most of the time they a running as a Pod and using in-cluster config/ServiceAccounts to talk to the API server and start their watches. So probably none of them is doing a dynamic reload of their client configuration, or am I mistaken?
And that's probably why there are no mechanisms in the kubernetes libraries to accomplish such things.
BTW: how does the kubelet deal with rotated certificates? Does it dynamically refresh the underlying configuration of its watches? And if so, how?

I think it makes sense to leave this issue open and revisit it when we see more reasons to switch to the controller runtime clients.

What do you mean by that? I don't understand how this is related to controller-runtime clients...

Indeed, I don't see any way how the configuration of client-go style ClientSets, Informers or Listers can be changed at runtime. Maybe I miss something here, if you see such possibilities, I would be very interested to look into them.

No I do not. I see that as a reason to harmonize the client usage in the GCM, Gardenlet and extensions to all use the controller runtime clients.

Why? The controller-runtime clients also use client-go under the hood, so I'm not aware of any mechanisms to refresh the rest config of their Informers at runtime as it is just the same client-go stuff.

That in turn means, that controllers relying on such informers will have to get a new client again and start watching with new Informers.

That would be possible at runtime, right?

Of course, that would be possible at runtime. But we don't have any mechanism for that at the moment. I was thinking about such a way to do so, but I now tend more and more to not implement such things, as they will be highly gardener specific and probably won't work if we use our clientmaps for constructing controller-runtime managers unless this mechanism is highly over-engineered.

We agreed upon that it does not make sense to update the Garden and Seed clients at runtime due to increased complexity.
Gardener is build in a stateless fashion - so killing the Gardenlet pod will do not harm (does not reconcile any Shoots again etc.).
The only thing that possibly happens is that an ongoing reconciliation will be started again.
Thanks for your guys input!
Closing this.


global search - FrontEnd P1

Summary
#1172
Added global search bar in header - FRONTEND part 1
Checklist

[ ] On the frontend, I've made my strings translate-able.
[ ] If I've added shared components, I've added a storybook story.
[x] I've made pages responsive and look good on mobile.

Screenshots
Desktop view:

Responsive/mobile view:

Known issues
Full functionality requires #1175 and #1173
will fix formatting issues when in mobile view- see screenshot above - #1200

re prev commit:
uninstalled unnecessary package that I installed prev
rounded borders:

Not ready for reviews. I need to do another commit.

Not ready for reviews. I need to do another commit.

No worries! Perhaps for extra visibility we could mark this as a draft?

Desktop:

Mobile:
signed in:

signed out:
notice sign in button is red box in navBar -
stylistically preferable than original (prod website)

Not ready for reviews. I need to do another commit.

No worries! Perhaps for extra visibility we could mark this as a draft?

Sure! That sounds great!


v1.4_Update_DG

Added Email command and use cases

Codecov Report

Merging #135 (082199c) into master (24563ff) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master     #135   +/-   ##
=========================================
  Coverage     61.18%   61.18%
  Complexity      437      437
=========================================
  Files            91       91
  Lines          1649     1649
  Branches        160      160
=========================================
  Hits           1009     1009
  Misses          590      590
  Partials         50       50

:mega: Codecov can now indicate which changes are the most critical in Pull Requests. Learn more


Add Secret Input parameters

Parameter is a part of the latest StoryBook: https://developers.grafana.com/ui/latest/index.html?path=/story/forms-secretinput--basic

Not Available in Grafana 8.5.2. Waiting when it's become a part of the Grafana/ui


Added Calculator webpage

Zero To Mastery - Webblocks 2022 📦📦
👉 Please remove the below and replace with your own values, leaving the headers where they are. 👈
PR contains:

INFO ABOUT YOUR PULL REQUEST GOES HERE (Please be as descriptive as possible) 🤜

Breaking changes

IF ANYTHING YOU'RE COMMITTING WOULD BREAK SOMETHING, INCLUDE HERE WHAT WOULD BREAK
IF YOU HAVE NO BREAKING CHANGES, ENTER 'None'

Screenshots

IF YOU HAVE ANY SCREENSHOTS, INCLUDE THEM HERE.
IF YOU HAVE NO SCREENSHOTS, ENTER 'None'

Next time, please fill out the pull request template, so it is easier to understand for maintainers.


Fix typos for IoT Edge Node.js development

Fixed a few typos related to Node.js.
Expanded ACR acronym line to match C# article line.

@theangellmethod : Thanks for your contribution! The author, @shizn, has been notified to review your proposed change.

#sign-off

Thanks for your contribution!!!


 is mapped also in describe buffer

when describing an object, <C-d> is still mapped to delete but I want to use the original functionality of scrolling down so I can scroll the describe output.
Can you cancel the default keybindings in describe buffers?
Thanks.

Thanks for the heads up, changed delete to use "D" instead!


The second card is being cut and overflowing on medium and small sized mobile screens.

Description
The second card cuts and overflows in medium and small-size screens.
Screenshots

Hi, is it alright if I work on this issue?

Hi, is it alright if I work on this issue?

Sincerest apologies for not replying to this issue sooner and assigning it, but a PR has already been opened it seems


Renaming the 2 last not good named tuya quirks.

Codecov Report

Merging #1077 (1efe298) into dev (9dcdf7a) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##              dev    #1077   +/-   ##
=======================================
  Coverage   81.06%   81.06%
=======================================
  Files         197      197
  Lines        5223     5223
=======================================
  Hits         4234     4234
  Misses        989      989

Impacted Files
Coverage Δ

zhaquirks/tuya/ts0201_neo.py
100.00% <ø> (ø)

zhaquirks/tuya/ts0601_singleswitch.py
100.00% <ø> (ø)

Continue to review full report at Codecov.

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

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

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

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
4234

Relevant Lines:
5223

💛  - Coveralls

Last renaming of tuya quirks and  now the folder looks better (but not very good).
One thing is moving all ts0601 (tuya DP command devices) to one own folder and the rest "normal zigbee" devices to one other but that the maintainer must deciding how they like to have it.


Add Whatif and Confirm to the commandlets

Implement these items for the functions in the module.

The Whatif implementation is really shoddy. Going to pass on it for now. Maybe it's be improved in a later PS version.


How to close the achievement pop-up window in the upper right corner?

I have to admit that Goldberg's achievement pop-up is a bit rudimentary.
Some games have pop-ups and some don't. The overlay of Shift+Tab doesn't have an on/off option. Do I need to modify the file to turn it on or off?

You need to enable the 'Enable Overlay' option to enable the overlay.
Also experimental version goldberg emulator is required to use the overlay.


Unit of Work Redesign

IUnitOfWork, IDomain, IApplication, IGeneric
Too many interfaces and too specific.  Im thinking of implementing some kind of generic typed unit of work and a configuration step
Aggregates.Configure().WithUnitOfWork<MyUnitOfWork>();
and then ctx.Uow() would return MyUnitOfWork - somehow
Important that instances available to handlers don't have Begin and End methods, which was one of the reasons I split up unit of works to begin with.

Fixed in v0.17


Document android background platform channels

The Background Platform Channels feature requires documentation (https://github.com/flutter/flutter/issues/91635)

Did https://github.com/flutter/website/pull/6494 resolve this?


Dealing with a strictly controlled firewall

Hi,
We'd like to use Docker in a setup where the firewall is strictly controlled by ferm via puppet. The trouble we're running into is that ferm needs all rules in its own config, any changes performed by external applications (like docker) will get removed by ferm when it reloads. Which is a bit of a problem when you've bound ports to docker containers.
Aside from disabling ferm entirely (which is sadly not an option in this environment), I see only three ways around that, all of them require changes in docker:

Fixed IP addresses for docker containers, so we know in advance which port on which IP address needs to be masqueraded and we can add it to the ferm config statically.

Add an option to docker that makes it reload it's firewall config and set it up anew. This would be slightly problematic, since it would break already running connections, but at least it would allow me to get the config.

Make docker 'request' the firewall changes from some script that automagically creates the required ferm config and adds it in the ferm.d directory. Docker would invoke a script and sent its information in some format (json?) to the stdin of the script.

The first one is probably preferred, since it allows us to take the config change into account in config management (and thus, in version control). But maybe I'm overlooking already implemented solutions for this? On IRC it was recommended to simply open all the ports, but that's not an option.
I'd appreciate some input to this problem.

All the iptables rules are in a Chain called docker, you could run a iptables-save and iptables-restore to bring them back up.
Also you can used assign a fixed-cidr.
See the networking articles here: http://docs.master.dockerproject.com/articles/networking/

@timstoop you could use pre/post ferm hooks for this, and call helper scripts:
# !/bin/bash
# pre_script
iptables -S DOCKER -t nat > /etc/saved_rules/nat_DOCKER
iptables -S DOCKER > /etc/saved_rules/filter_DOCKER
iptables -S DOCKER-ISOLATION > /etc/saved_rules/filter_DOCKER-ISOLATION

# !/bin/bash
# post_script
for table in nat filter; do
  for chain in /etc/saved_rules/${table}_*; do
    iptables-restore -n ${table}_${chain}
  done
done

Not tested, might work :)


FR: move music_assistant.db out of /config (but remain on the HA instance MA is running on)

Please consider support for allowing the music_assistant.db to be saved elsewhere, to keep the /config share as clean as possible.
In Discord we briefly discussed the technique Powercalc supports doing this, by allowing a user configured folder inside the CC folder. Used so this is not wiped at updating the CC.
For my personal use it would be sufficient to make that a fixed /db folder, so /config/custom_components/mass/db
I noticed others mention a location even outside the HA instance, because the file might get large quite soon. I would no be an advocate for that, as it would make MA rely on an external source per definition, and I dont think that would be very robust.
thanks for considering!

I really would like to have this improvement in place. Now the database (200mb) is part of my nightly backups as they include the config folder. Moving the database to i.e. my media folder would solve that.

Moving the db to a location outside of HA (e.g. mounted disk) is very dangerous. I'd rather invest in mysql compatibility in that case. That said. What is 200mb nowadays ? Worst case scenario (when you have like 500.000 items in your library) the db would grow to like 500mb ....
Can we merge the 2 feature requests into one ?
Make it more generic to customize the db path ?
It truly is just a sqlalchemy string so it supports both sqlite in a folder of choice and mysql or postgres

Moving the db to a location outside of HA (e.g. mounted disk) is very dangerous

Agreed to keep it local (my media folder is not a mount, but part of my local SSD).
But the proposal for a fixed '/db' folder, like '/config/custom_components/mass/db' will keep it part of my backups. The database doesn't need to be backed up (easily regenerated). It only increases my backup times and cloud space.
Note: the Google drive backup add-on, that I use, only allows to exclude particular add-ons and folders like media and shared.
That is why I was thinking to use the media folder (local, nit part of my backup). No other reason

I currently use owntone (formerly called forked-daapd) for library streaming and there I configured the database to be in /share which isn't backed up. Would be great indeed if music assistant would also support this.

Moved to discussions: raise your votes 😀


More user friendly search

Description
The search on the documentation pages do not give any relevant search results. It is better for the user to google than to use the internal search. Can we make the search better or replace it with a better search engine?
Related to https://github.com/Altinn/altinn-studio-docs/issues/595
In scope
No response
Out of scope
No response
Additional Information
No response
Analysis
No response
Conclusion
No response

Improved by #686 and #1258


Installation failure

Ran brew install Caskroom/cask/java
which downloaded the binary and then timed out; re-ran the process and got back:
==> Downloading http://download.oracle.com/otn-pub/java/jdk/8u25-b17/jdk-8u25-macosx-x64.dmg
Already downloaded: /Library/Caches/Homebrew/java-1.8.0_25.dmg
Error: no implicit conversion of nil into String
Please report this bug:
    https://github.com/caskroom/homebrew-cask/issues
/System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib/ruby/2.0.0/digest.rb:44:in `initialize'
/System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib/ruby/2.0.0/digest.rb:44:in `open'
/System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib/ruby/2.0.0/digest.rb:44:in `file'
/System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib/ruby/2.0.0/digest.rb:29:in `file'
/usr/local/Cellar/brew-cask/0.43.0/rubylib/cask/download.rb:41:in `block in _check_sums'
/usr/local/Cellar/brew-cask/0.43.0/rubylib/cask/download.rb:39:in `each'
/usr/local/Cellar/brew-cask/0.43.0/rubylib/cask/download.rb:39:in `_check_sums'
/usr/local/Cellar/brew-cask/0.43.0/rubylib/cask/download.rb:32:in `perform'
/usr/local/Cellar/brew-cask/0.43.0/rubylib/cask/installer.rb:72:in `download'
/usr/local/Cellar/brew-cask/0.43.0/rubylib/cask/installer.rb:49:in `install'
/usr/local/Cellar/brew-cask/0.43.0/rubylib/cask/cli/install.rb:20:in `block in install_casks'
/usr/local/Cellar/brew-cask/0.43.0/rubylib/cask/cli/install.rb:17:in `each'
/usr/local/Cellar/brew-cask/0.43.0/rubylib/cask/cli/install.rb:17:in `install_casks'
/usr/local/Cellar/brew-cask/0.43.0/rubylib/cask/cli/install.rb:6:in `run'
/usr/local/Cellar/brew-cask/0.43.0/rubylib/cask/cli.rb:81:in `run_command'
/usr/local/Cellar/brew-cask/0.43.0/rubylib/cask/cli.rb:121:in `process'
/usr/local/bin/brew-cask.rb:42:in `<top (required)>'
/System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib/ruby/2.0.0/rubygems/core_ext/kernel_require.rb:55:in `require'
/System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib/ruby/2.0.0/rubygems/core_ext/kernel_require.rb:55:in `require'
/usr/local/Library/brew.rb:59:in `require?'
/usr/local/Library/brew.rb:142:in `<main>'

Hi!
This is a duplicate of #7946.
A fix has been in release since v0.50.0.  The following command should fix the issue:
$ brew update && brew upgrade brew-cask && brew cleanup && brew cask cleanup

Hi!
This is a duplicate of #7946.
A fix has been in release since v0.50.0.  The following command should fix the issue:
$ brew update && brew upgrade brew-cask && brew cleanup && brew cask cleanup


feat: add cDAI/cUSDC vault

commit 61b9d76ecca4fb48915f3231750700a9f091ba81
Author: x48<EMAIL_ADDRESS>Date:   Sun Nov 8 15:12:07 2020 -0600

    feat: add cDAI/cUSDC vault

commit 1fca2c6857fbe81aaa1f853eeb9ed832d695951e (HEAD -> develop, origin/develop)
Author: x48<EMAIL_ADDRESS>Date:   Sun Nov 8 15:13:20 2020 -0600

    refactor: update styling to account for larger token symbols


Documentation about cquery-specific messages

I'm trying to make cquery work with Sublime Text, namely, with an extension plugin to this LSP plugin.

Is there a documentaion about cquery-specific messages? For example, currently I struggle to understand $cquery/progress message - what's its structure, and how should the plugin behave based on that values it provides.
It is worth noting that LSP is new for me, so please make no assumptions about my knowladge in LSP.
Partly related quesetion: is there a way which you can recommend to me about how to examine cquery server's behaviour, when trying to diagnose whether the root of a problem is at cquery's end or the plugin's? For example, if a $textDocument/documentSymbol request is answered with $cquery/progress response, where you'd look first?

Great! 😼
There is currently no document about cquery extensions. The Language Server Protocol specification is here https://microsoft.github.io/language-server-protocol/specification
There are two types of messages sending from the client to the server:

NotificationMessage
RequestMessage. It should be responded with a lsOutMessage

Whether the id field exists differentiates the two types.
Most response messages do not contain the "method" field.
For $cquery/progress, it is a notification message pushed by the server. https://github.com/cquery-project/cquery/blob/master/src/import_pipeline.cc#L27 It has no "id" and will not be sent as a response of requests.

Added some source file links in README.md

Thank you for your fast and informative response :wink:
I'll take my time diving into this material and  see how it goes.
Considering future questions I might have on the subject, would you like me to comment on this issue? Or to open a new one? Or maybe there's a chat?

Questions can be asked in the gitter: https://gitter.im/cquery-project/Lobby


Error while readin AOD file

Jim, now I'm trying to read AOD file
/afs/cern.ch/user/v/valya/public/C84930B2-7C55-E711-B915-02163E014722.root
and it fails right away:
    for branchname in tree.arrays().keys():
        print(branchname)

gives
Traceback (most recent call last):
  File "vk_test.py", line 38, in <module>
    branchNames(eTree)
  File "vk_test.py", line 24, in branchNames
    for branchname in tree.arrays().keys():
  File "/Users/vk/Work/Languages/Python/GIT/uproot/uproot/tree.py", line 458, in arrays
    outi, res = branch.array(dtype, executor, False)
  File "/Users/vk/Work/Languages/Python/GIT/uproot/uproot/tree.py", line 1427, in array
    return TBranch.array(self, dtype, executor, block)
  File "/Users/vk/Work/Languages/Python/GIT/uproot/uproot/tree.py", line 1182, in array
    out[start:end] = self._basket(i, parallel=False)
  File "/Users/vk/Work/Languages/Python/GIT/uproot/uproot/tree.py", line 857, in _basket
    self._basketwalkers[i]._evaluate(parallel)
  File "/Users/vk/Work/Languages/Python/GIT/uproot/uproot/_walker/lazyarraywalker.py", line 54, in _evaluate
    string = self._original_function(walker.readbytes(length))
  File "/Users/vk/Work/Languages/Python/GIT/uproot/uproot/rootio.py", line 84, in <lambda>
    return lambda x: zlib_decompress(x[9:])
error: Error -3 while decompressing data: incorrect header check

Well, it's not quite immediate because you've asked uproot to interpret and convert all arrays in the tree (tree.arrays()), then only return their names (.keys()), which could be accomplished without all the heavy calculations by just tree.allbranchnames.
However, it's a real bug. I've looked at this in both versions and as it scans through branches, reading them all out, it encounters this one:
GlobalObjectMapRecord_hltGtStage2ObjectMap__HLT.obj.m_gtObjectMap.m_algoBitNumber

which somehow is failing to decompress. The branch has the same compression parameters as the file (in principle, they can be different, and I haven't handled that yet), and it's just zlib-7.
Seeking to this point in the file, it has the right kind of header (starting with "XZ"), which is supposed to be 9 bytes long, followed by zlib data. Python's zlib then complains about the format of the data.
01613360  58 5a 00 28 02 00 00 1c  00 fd 37 7a 58 5a 00 00  |XZ.(......7zXZ..|
01613400  01 69 22 de 36 02 00 21  01 00 00 00 00 37 27 97  |.i".6..!.....7'.|
01613420  d6 e0 1b ff 01 ec 5d 00  00 60 04 08 ca 06 5b f5  |......]..`....[.|
01613440  fa 66 ca fc 2c 3c 41 57  c9 09 f4 5f f9 55 48 b6  |.f..,<AW..._.UH.|
01613460  73 22 9b fe 54 36 56 93  d7 91 c5 94 58 f5 b0 d7  |s"..T6V.....X...|
01613500  c9 03 c0 fd dc f0 9e 3d  2a 61 2e 81 2f 2e 1c 2d  |.......=*a../..-|
01613520  42 88 81 7b 45 66 a2 bb  69 f2 06 b8 f7 bb bc 1d  |B..{Ef..i.......|
01613540  41 24 7a ec 6d fc c1 08  0f 48 8b 88 11 b2 0c 76  |A$z.m....H.....v|
01613560  c0 c1 87 6b bb b5 25 16  29 da 87 3d 32 e7 24 25  |...k..%.)..=2.$%|
01613600  69 7f 08 81 a4 cd a3 f3  7f c5 be 3c 2f 6a 49 13  |i..........</jI.|

It looks wrong to me, too: after the 9-byte header, there's only 3 bytes of stuff before another "XZ". That could be part of the compressed data, but it would be a weird coincidence for the compressed data to also have an "XZ". It looks like another block of compressed data. Could the compressed data really be just 3 bytes long? Maybe Python's library has a problem with that (maybe the Python library would rather the data be padded...).
According to the basket header, that compressed data is supposed to be 561 bytes compressed and 7168 uncompressed, which makes me even more suspicious. I'll have to come back to this.

This is one of those wake-you-up-in-the-middle-of-the-night things. It was staring me in the face. The file declared the compression to be zlib-7, but the two-character header of this compressed block is "XZ", which means LZMA. Apparently, when fCompress and that two-character header disagree, the two-character header has precedence.
So instead of using fCompress to determine which compression algorithm to use, we should use the first two bytes of the 9-byte compressed block header. Here's where it is in C++ ROOT:
https://github.com/root-project/root/blob/5b7d9393c1c0c242be452510ac8ddf08bd492d40/core/zip/src/RZip.cxx#L348
They check is_valid_header_zlib, is_valid_header_lzma, is_valid_header_lz4 to determine the compression algorithm on the spot, rather than the file's or branch's own fCompress. I would have thought that fCompress ought to agree, but okay.
Now we can read in all those arrays, including the LZMA ones. Check out version 1.6.2 from GitHub.
python -i -c 'import uproot; t = uproot.open("/afs/cern.ch/user/v/valya/public/C84930B2-7C55-E711-B915-02163E014722.root")["Events"]; print(t.arrays())'

Jim,
thanks for looking into this and provide me details. I better understand the
logic behind the uproot now.
Could you please commit 1.6.2 tag since I don't see it, may be you tag the code
but didn't commit.
Thanks,
Valentin.
On  0, Jim Pivarski<EMAIL_ADDRESS>wrote:

This is one of those wake-you-up-in-the-middle-of-the-night things. It was staring me in the face. The file declared the compression to be zlib-7, but the two-character header of this compressed block is "XZ", which means LZMA. Apparently, when fCompress and that two-character header disagree, the two-character header has precedence.
So instead of using fCompress to determine which compression algorithm to use, we should use the first two bytes of the 9-byte compressed block header. Here's where it is in C++ ROOT:
https://github.com/root-project/root/blob/5b7d9393c1c0c242be452510ac8ddf08bd492d40/core/zip/src/RZip.cxx#L348
They check is_valid_header_zlib, is_valid_header_lzma, is_valid_header_lz4 to determine the compression algorithm on the spot, rather than the file's or branch's own fCompress. I would have thought that fCompress ought to agree, but okay.
Now we can read in all those arrays, including the LZMA ones. Check out version 1.6.2 from GitHub.
python -i -c 'import uproot; t = uproot.open("/afs/cern.ch/user/v/valya/public/C84930B2-7C55-E711-B915-02163E014722.root")["Events"]; print(t.arrays())'

--
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub:
https://github.com/scikit-hep/uproot/issues/16#issuecomment-341887272

I had committed it, but it wasn't a release. I just uploaded it to PyPI and made a formal GitHub release. (I always do these two things together to ensure that the version numbers are in sync: it's easy to botch a version number in PyPI.)
As for explaining the problem, I was just thinking out loud. This detail (whether to trust fCompress or the compressed buffer header when the two are in conflict) is exactly the sort of reason we need multiple implementations of ROOT I/O, to spread the knowledge.


Can i display image on push notification

In Push.notify() ,we can pass three arguments title, body ,data if I send the image in data it is not displaying .
Am I sending  wrongly or  is there any other way to display notification image send from backend.

Thanks for the information @pushy-me it was very helpful.


GNOME 45 updates (2024-03-17)

Description of changes

Things done

Built on platform(s)

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

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

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

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

[ ] Fits CONTRIBUTING.md.

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

I think the only notable change here is silent disabling of the rt-scheduler experimental feature, but with the reasoning upstream provides I understand wanting to ship this ahead of 46.


How to Hide Build ID  ?

Hello, you can comment out this line:
https://github.com/vvbbnn00/onedrive-index/blob/3f53b04ce50feb43cae8b5c662e322c0b510c50c/app/src/components/Footer.tsx#L13C7-L13C50

Thanks anyway, way to fix this ?
OneDrive-index

Alist

It seems that there are some issues with the support for Markdown parsing.
We will look for a solution to fix it later.

Ok thanks


Badge links refer to proper2

Actually have those been worked at all? eg. https://circleci.com/gh/propelorm/Propel3/tree/master should show something - right ?


NgenCalibrationRequest and associated workflow logic

Add request type for calibration jobs
Alter request hierarchy to add intermediate abstraction for Nextgen-based job requests (e.g., NGENRequest) so that certain things can be reused in calibration request type with it being detached from model exec types/events
Updating scheduler library to work with calibration requests
Fixing a few bugs with __init__ syntax in certain request types
Fixing a few unit tests

Note that this PR partially replaces #240, in that it is composed of changes extracted from that PR for easier reviewing and merging.

@aaraney, FYI, when you have a moment, this will need approval once more.  I tweaked a few things you noted and fixed the failing tests.

@robertbartel 👍🏻, ill have a look right after the standup.

@aaraney, ok, had to do some rebasing and reworking of a few things.  Assuming this last check passes (I'm fairly confident), this will need one last review.


[BUG] Error when executing script

Describe the bug
Got Exception while fetching emotes: Request failed with status code 401 when executing the script

I just had to get a new client_token 🤦♂


Review WETH contract on Ethereum, Arbitrum, Optimism, Base and Polygon

Review WETH contract on Ethereum, Arbitrum, Optimism, Base and Polygon

cc @Nana-EC
Ethereum WETH9

uses solidity ^0.4.18
it's been on the mainnet for a long time doing its job in a bugless manner

Arbitrum WETH9

uses solidity >=0.6.2 <0.8.0
implements UpgradeableProxy that might reduce people's trust

Optimism WETH9

uses solidity >=0.4.22 <0.6
same as Ethereum's WETH9, with a few syntax changes due to the higher solidity version

Base WETH9

uses solidity >=0.4.22 <0.6
same as Optimism's WETH9, no changes

Polygon WETH9

uses solidity ^0.6.0
implements polygon's defined "ChildERC20"
added more code complexity while providing the same functionalities


Greenkeeper/@types/node 10.12.12

Coverage remained the same at 100.0% when pulling 8997050b11ce80118f0a0c5a9e29dbf9c5081039 on<EMAIL_ADDRESS>into 4df06ca1c219434f0e8998e6694eb45d47f53991 on master.


Not working in iOS

Hello i have install plugin using cli.
But when i use yotube url then it open player but not playing video its loading nothing Ahed
Please help me.

@mayurloved: For youtube videos, you may want to check this out: https://github.com/Glitchbone/CordovaYoutubeVideoPlayer

Please reopen if you're willing to provide more information.


it would be great to check if headers were present in response

https://github.com/2muchcoffeecom/ngx-restangular/blob/e1679e7af3ca9cac0d3dbc77decfd32b2d4dcc34/src/ngx-restangular.ts#L387

@bartes We can perform the check on headers but can you please specify the situation in which you need it?

I found myself uncomfortable with adding empty headers to mockedResponses in specs,
but if you think that this is not a good enough reason then please close this issue.

@bartes thanks for your answer. We'll consider the necessity of such check with the team if there are more similar issues. Closing this one for now.


VSIX debug visualizer doesn't show IPropertySet values

I'm trying this with a private C++/WinRT API.

Since IPropertySet implements IIterable<IKeyValuePair<winrt::hstring, IInspectable const &>>, it should be possible to show all its contents.
More generally, it would be great to add visualization support for:

IIterable of anything (at least show an item for each element; show actual values where the types are visualizable)
KeyValuePair of anything (show actual key and/or value if those types are visualizable)

Thanks David, this is a known issue with the visualizer that it cannot display information about generic types like IIterable. Feel free to contribute a fix but we don't have a developer working on the visualizer at the moment. Our hope was that the Visual Studio team would eventually consume this support and provide it directly. There are many issues with the visualizer that we unfortunately cannot fix without direct support from Visual Studio.


dictu: init at 0.19.0

Motivation for this change
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[ ] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
21.11 Release Notes (or backporting 21.05 Relase notes)

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

[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 132540 run on x86_64-linux 1

1 package built:

dictu

Result of nixpkgs-review pr 132540 at a5f39bde run on x86_64-linux 1

1 package built successfully:

dictu

2 suggestions:

warning: missing-phase-hooks
checkPhase should probably contain runHook postCheck.
Near pkgs/development/compilers/dictu/default.nix:65:3:
   |
65 |   checkPhase = ''
   |   ^

warning: missing-phase-hooks
installPhase should probably contain runHook preInstall and runHook postInstall.
Near pkgs/development/compilers/dictu/default.nix:70:3:
   |
70 |   installPhase = ''
   |   ^


[TieredStorage] Make TieredStorage's Offset compatible with AccountsDB's offset

Problem
AccountsDB currently assumes all offsets are multiple of 8, and this
applies to all AccountsFile API.  However, TieredStorage uses its
IndexOffset that does not have this assumption.
Summary of Changes
This PR adds a conversion to make TieredStorage::IndexOffset
compatible with the AccountsDB offset inside the AccountsFile layer.
Test Plan
Tested by running a validator with TieredStorage manually enabled on mnb.
More accounts-db tests will be enabled with #334

Codecov Report
Attention: Patch coverage is 48.91304% with 47 lines in your changes are missing coverage. Please review.

Project coverage is 81.8%. Comparing base (0e12172) to head (1590a84).
Report is 11 commits behind head on master.

Additional details and impacted files
@@           Coverage Diff           @@
##           master      #74   +/-   ##
=======================================
  Coverage    81.8%    81.8%
=======================================
  Files         838      838
  Lines      226564   226648   +84
=======================================
+ Hits       185520   185615   +95
+ Misses      41044    41033   -11

Hmm, we may need to make the index not divide by 8 automatically, and instead only do it for append vecs. I'm not sure how this will interact with forwards/backwards compatibility though.

Yep, I think this isn't the best way but offers an intermediate step to make tiered-storage runnable without changing the accounts-db + append-vec code path/logic.  Ideally, we want to have accounts-db + append-vec logic untouched until we make tiered-storage default / proven to be stable.

Hmm, we may need to make the index not divide by 8 automatically, and instead only do it for append vecs. I'm not sure how this will interact with forwards/backwards compatibility though.

Yep, I think this isn't the best way but offers an intermediate step to make tiered-storage runnable without changing the accounts-db + append-vec code path/logic. Ideally, we want to have accounts-db + append-vec logic untouched until we make tiered-storage default / proven to be stable.

this seems like it may be ok. I'm trying to figure out why the validators and ledger-tool were working without this change. I guess the indexes are *8 already somewhere else? I know I have hacked this in in a few places in my test branches. Maybe that's what I'm thinking of.

this pr does appear consistent with the one I was running 4fbts-test-all. I think it is good to go.

Hmm, we may need to make the index not divide by 8 automatically, and instead only do it for append vecs. I'm not sure how this will interact with forwards/backwards compatibility though.
Or maybe the StorageLocation gets a new variant? That may impact many other things too.

the index is using those extra bits for flags (like zero lamports), knowing that indexes were 8-byte aligned. This would be tricky to change. It does place an upper limit on offsets. This is not a problem at all for a 0,1,2 index. It is a limiting factor already for append vec offsets (where entries have a min size of 136 bytes or so). I thing this implementation is reasonable.


Accessing LLAMA 2 Model

Model description
Hi, I tried running the LLAMA 2 Model using this text generation inference but I am getting below error
Error:
File "/opt/conda/lib/python3.9/site-packages/text_generation_server/models/init.py", line 223, in get_model
raise NotImplementedError(FLASH_ATT_ERROR_MESSAGE.format("Sharded Llama"))
NotImplementedError: Sharded Llama requires a CUDA device with capability 7.5, > 8.0 or 9.0. No compatible CUDA device found.
Gpu details:

Model card: daryl149/llama-2-7b-chat-hf
Open source status

[ ] The model implementation is available
[X] The model weights are available

Provide useful links for the implementation
No response

If you're using unsharded model it might be able to work. Sharded requires flash for this model.


S3 Block Public Access settings for this account

Add config to block public access to s3 (global)

PCI.S3.6
AWS.S3.1

resource "aws_s3_account_public_access_block" "main" {
  block_public_acls   = true
  block_public_policy = true
  ignore_public_acls = true
  restrict_public_buckets = true
}

https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/s3_account_public_access_block

It looks like this is already set:
https://github.com/nozaq/terraform-aws-secure-baseline/blob/master/modules/secure-bucket/main.tf#L119

Awesome, must be a new option I need to enable.

While the log bucket this module creates already blocks all public accesses, enabling the account-level protection could be better.
Thanks for the suggestion!


Support Amazon S3

Do we have the support for Amazon S3 for this package?
I have been trying toe filesystem for this package and documentation is very hard to understand for the things.

I think there are actually people who used Amazon S3 in combination with this package. Really recommend you to look at the Filesystem and Laravel Docs regarding this. It's not something specific to this package that is making this hard.

We solved this simply prefixing multiple tenants into their own folders based on UUID. Do not attempt to use multi-tenant for this. Ideally you will create a wrapper class on top of Laravel's file system (which supports S3 out of the box) that handles this automatically for you.


Suggestion: Adding circuit braker

What do you say about providing circuit braker as well?
I was thinking about providing the following:
client.CircuitTreshold=10 (After 10 retries, disable the http client).
client.CircuitTimeout = 10000 (10 seconds timeout is whats considered a failure).
Thoughts?

Hi Alan. I've been on PTO; sorry for the late response. What would this do differently than client.MaxRetries and client.Timeout? As an alternative to putting something like this in pester, would you be able to embed the client and add those properties? Not sure if that would work for your use case.
From the Hystrix docs (the most popular circuit breaker of which I am aware):
Hystrix reports successes, failures, rejections, and timeouts to the circuit breaker, which maintains a rolling set of counters that calculate statistics.

It uses these stats to determine when the circuit should “trip,” at which point it short-circuits any subsequent requests until a recovery period elapses, upon which it closes the circuit again after first checking certain health checks.

My first thought is it might be a bit much to add into pester and perhaps there is a way to have two libs work together to achieve this result, keeping each a bit more thin.


Is it too hard to do multiple image selection?

iOS's UIImagePickerController does not support this, unfortunately. If you want, you could fork this repo and use something like ELCImagePickerController instead of UIImagePickerController.


cyber TimerComponent cleanup during shutdown

Describe the bug

There is a public member function Process() which seems never get called.

bool TimerComponent::Process() {
  if (is_shutdown_.load()) {
    return true;
  }
  return Proc();
}

In Initialize() function, the task is added to the timing_wheel through member variable timer_. Notice in the callback function, ptr->Proc() is called instead of ptr->Process().

bool TimerComponent::Initialize(const TimerComponentConfig& config) {
  if (!config.has_name() || !config.has_interval()) {
    AERROR << "Missing required field in config file.";
    return false;
  }
  node_.reset(new Node(config.name()));
  LoadConfigFiles(config);
  if (!Init()) {
    return false;
  }

  std::weak_ptr<TimerComponent> self =
      std::dynamic_pointer_cast<TimerComponent>(shared_from_this());
  auto func = [self]() {
    auto ptr = self.lock();
    if (ptr) {
      ptr->Proc();
    }
  };
  timer_.reset(new Timer(config.interval(), func, false));
  timer_->Start();
  return true;
}

There is no corresponding timer_->Stop() call to remove the task from the timing_wheel.

During shutdown, there is potential memory faults because Proc() from the derived class can be called in the timing wheel. Note: The timing_wheel is a singleton instance (I am not sure when its destructor gets called during shutdown).

Possible Fix:

Stop the timer inside Process(), so the task will not be added to the timing_wheel again.

bool TimerComponent::Process() {
  if (is_shutdown_.load()) {
    timer_->Stop();
    return true;
  }
  return Proc();
}

In callback function, call ptr->Process() instead of ptr->Proc()

  std::weak_ptr<TimerComponent> self =
      std::dynamic_pointer_cast<TimerComponent>(shared_from_this());
  auto func = [self]() {
    auto ptr = self.lock();
    if (ptr) {
      ptr->Process();
    }
  };

Any comments will be appreciated.

Thank you. The bug you said indeed exists. We will use ptr->Process() than ptr->Proc(). timer_->Stop() will be invoked duration timer_'s desctruction, so I think timer_->Stop() is not need to be invoked in Process

Please reopen if you have further questions.


Improve write_dataframe_async function

introduce new write_async function

@macsir
I did a few small changes to the write_dataframe_async function and added a new write_async function for dictionaries.
Can you please double-check that my changes don't break your code?

Hi, @MariusWirtz  sorry for the late reply. Yes, it looks good to me. Thanks.

Thanks for the confirmation!


Groovy metaclass stopped working as of Gradle 3.4

Methods added through Groovy metaclass option cannot be found
Steps to Reproduce
Having a simple script
apply plugin: 'maven-publish'

MavenArtifactRepository.metaClass.groovyCheck {
    println 'it works!'
}
publishing {
    publications {
        maven {
            groovyCheck()
            name 'release'
            url 'https://myreleaserepo'
        }
    }
}

With gradle v3.3 and lower the output is 'it works!', while with 3.4 and above the following error occurs:
> Exception thrown while executing model rule: PublishingPlugin.Rules#publishing(ExtensionContainer)
   > Could not find method groovyCheck() for arguments [] on object of type org.gradle.api.internal.artifacts.repositories.DefaultMavenArtifactRepository.

IMHO it's a bad idea to mess around with Groovy meta programming in a Gradle build script. What exactly are you trying to achieve in groovyCheck()? I am sure we'll find a different option that doesn't involve Groovy meta programming.

I'm adding authentication to a particular maven repository.
I have a plugin, which does pretty much the same as I had described before:
MavenArtifactRepository.metaClass.authenticate = { repoId ->
            //reads username and password from ~/.m2/settings.xml for this repoId
            Credentials cred = locateAuthenticationCredentials(repoId)
            delegate.credentials {
                    username cred.username
                    password cred.password
            }
}

And the build script looks like:
apply plugin: 'maven-authentication'
...
repositories {
        maven {
                authenticate 'dependenciesrepo'
                url 'https://mydependenciesrepo'
        }
}
...
publishing {
    publications {
        maven {
            authenticate 'publishrepo'
            url 'https://mypublishrepo'
        }
    }
}

Where 'dependenciesrepo' and  'publishrepo' are ids from ~/.m2/settings.xml

Why can't I get access to metaclass? Is there an alternative to that?

Something like the following should work:
project.afterEvaluate {
    repositories.each { repo ->
        if (repo instanceof MavenArtifactRepository) {
            repo.credentials {
                username 'admin'
                password 'password'
            }
        }
    }
}

I am going to close the issue. Feel free to reopen if you have other questions.


feat: use storage instead of runtime config

🔗 Linked issue
❓ Type of change

[ ] 📖 Documentation (updates to the documentation or readme)
[ ] 🐞 Bug fix (a non-breaking change that fixes an issue)
[ ] 👌 Enhancement (improving an existing functionality like performance)
[ ] ✨ New feature (a non-breaking change that adds functionality)
[ ] ⚠ Breaking change (fix or feature that would cause existing functionality to change)

📚 Description

📝 Checklist

[ ] I have linked an issue or discussion.
[ ] I have updated the documentation accordingly.

Thank you a lot Ahad 🙏, I finalized initial implementation!
I'm merging this so I can go forward with https://github.com/nuxtlabs/docus/pull/584


Consider moving inventory updating code for new donations to outside of controller

[This was originally a Slack discussion; I am moving it here.]
Me: Question: I see this in DonationsController:
    if @donation.save
      @donation.storage_location.increase_inventory @donation
      redirect_to donations_path

I am not familiar with Rails model/controller responsibilities, but my gut tells me that data integrity issues like this should be enforced in a model, not a controller. Am I wrong?
By “data integrity issues” I mean ensuring that the inventory is updated when a donation is saved to the DB.
(End, issue description; discussion follows.)

Aaron: Good point. I think it was promoted to the controller because it straddled 2 models, but if you have a suggestion or idea on how to do it differently that is better separated, please suggest it!

Michael Dworkin: I remember there was a good reason we did it that way.
I think our reasoning was that it wouldn't work living in the model as it would tightly couple models in a way we wouldn't want
Regarding putting it in the controller, we did take some mild liberties with what constitutes dispatching vs business logic when we added the transaction to make it everything or nothing
Ideally, it would then instead be extracted to a service object call, but @A-A-ron and I had some concerns about making the app less default rails in terms of accessibility to newer contributors
And so we made the judgement call that putting the "everything or nothing" into the controller  vs complicating the app we erred on throwing it in the controller

Aaron: That sounds about right

Michael: That said, we may be interested in extracting our inventory/line item patterns into a gem we can use for this and similar projects, so if you'd be interested in working on that wiht us @keithrbennett do let me know!

Aaron: oh that'd be cool
Overall, Itemizable seems pretty stable and we've not had to change the internals much at all

Me:  I asked the question on the DCTech Ruby Slack, and have gotten 1 suggestion so far: Move the code to the Donation model and wrap it in a transaction. (edited)
If we override Donation’s save method to call super and then do the inventory stuff, then the controller code would not look out of the ordinary at all. However, I don’t know if overriding save like that is a good idea, since we would no longer have a method to only save the Donation record; maybe we need a new method,  save_and_increase_inventory. Or…?

Here is some dialog on the DC Tech Slack about this question:
Keith:
I am not familiar with Rails model/controller responsibilities, but my gut tells me that data integrity issues like this should be enforced in a model, not a controller. Am I wrong? Is there a better way? Maybe a trigger in the DB?
 Using an ActiveRecord transaction is probably what you will want to do:  https://api.rubyonrails.org/classes/ActiveRecord/Transactions/ClassMethods.html
In the transaction block you can save the donation and increase inventory. I would have all that logic in the Donation model.
From: api.rubyonrails.orgapi.rubyonrails.org
ActiveRecord::Transactions::ClassMethods
Active Record Transactions Transactions are protective blocks where SQL statements are only permanent if they can all succeed as one atomic action.

Robb Kidd:
Please, not in an ActiveRecord callback, though, right?

Keith Bennett:
@robbkidd Can you say more about that? If it’s only needed on object creation, why would an AR callback be bad, and how else would you suggest implementing it?

Robb Kidd:
That's coming from pain testing callbacks and seeing them not interact well in prod. But I can't show any evidence. Just emotional scars.

Dave Copeland:
if you do it in a callback then everywhere you use that thing, including tests, the callback  gets triggered and that can be problematic
I know DHH would hate this, but I'd make a class called Donator with a method called donate that does the save and the increase_inventory in a transaction and returns the Donation object
(or replace donate with whatever the word for what is happening in the controller is)

Robb Kidd: Yea. I've been thinking for a minute on commentary, but it all boiled down to different words for the same moving parts as @davetron5000 suggests.

dezmathio:
I've definitely wasted countless hours/days tracking down callbacks like that that were happening in a non-obvious way. I agree with Dave on it potentially being problematic, imo it really comes down to how widely used is it going to be throughout the rest of your application. It might also help if you assume that if that code ever breaks, that you won't be the one fixing it, so how is the next person going to discover that & know that CB is triggered every time?

Dave Copeland:
the mental model that I eventually adopted is that while it's a nice thought that app/models are models in the Domain Driven Design sense, in reality they really just aren't—they are a convenient way to access the database. And taken as that, putting business logic of any kind on them doesn't feel right.  I also think not putting business logic ever on an Active Record is a wonderful tradeoff because you give up really nothing about what makes Rails special.

Chris Flipse:
I like the idea that an ActiveRecord is a gateway, and not a model
But .. the process of trying to break apart the "modeling" parts an use natural models for other things lead to a lot of really uncomfortable mapping mismatches (edited)
Rails is somewhat less dependant on being able to get the class name out of an object now; at the time I was playing with this, it was bad
this was a good part of what lead me in to playing with ROM

I agree with the transaction -- we're moving more of our things towards that. That is the best way to ensure the data changes both happen in tandem.
I disagree with putting it into the Donation model, specifically, because it also sends messages to the StorageLocation object, and I think it would be folly to tightly couple them like that. (I don't know if greg is familiar with this app or not, so maybe he doesn't know that inventory is held in a different model).
I don't know how much of the app's history you've looked through but originally we did have the increase/decrease logic being done in the individual resources (in the model itself), but that ended up with a lot of replicated code that was done differently in each resource. Michael and I realized that the concern of increase/decrease was really a responsibility of the storage location itself, so we moved it to that and wrapped it in a transaction. We have about a half-dozen resources that manipulate inventory totals, so it doesn't make as much sense to put the logic into them.
I agree with Rob on not doing it as a callback. Especially this transaction specifically. In general, we have tried to avoid using side-effects to perform important process steps. (If any still exist, we likely want to remove those)
Using a service object of some kind is the direction that Sean and Michael and I have been moving, we're discussing how to best approach that.
Data integrity is definitely important to this app, for sure. We've uncovered a few bugs over the past year in that vein and have been mashing them as they come up. It's in a far better place than it was a year ago.
The reason some of this is being invoked in the Controller is because it makes it easier to follow. Rails will 100% give you more than enough rope to hang yourself with, and I've seen far too many nascent rails devs overzealously extract and DRY their apps to the bejeezus and then you end up with a disparate codebase that requires opening up 10-15 files just to trace down a single execution line.
Having a controller action whose lifecycle, end-to-end, is essentially covered in a sequence that is easy to read and understand (and you have basic idea of where everything is and will be happening) makes it easier to maintain. If we refactor this by extracting some of the logic out to a separate class, it's because that logic is being used multiple times, in the same way, in multiple places, and having it conceptually encapsulated in a single location just makes more sense. -- Take a look at Itemizable, or at the StorageLocation#increase_inventory / #decrease_inventory methods.
If we're going to add additional cognitive load to the app (additional dependencies, additional conceptual models or objects), it's gotta be worth it.

Closing this as it is being implemented as a service object re: issue #1310


ROX-12844: Refactor signature verification with multiple image names

Description
This is the second PR in a series of PRs to allow images to have multiple image names to improve the correctness of image signature verification results.
For additional context, see the parent PRs description as well as ROX-12844.
This PR refactors the signature verification part of our code base to fill the new field verified_image_references on the signature verification result.
This is done by using the payload of the signature, which is in simple signing format.
The simple signing format specifies which location is associated with the container image. This location will be used to match any associated names of the image, and filter those.
In the end, all image names associated with the same registry and repository are added to the verified_image_references list, allowing the signature verification result to be scoped to a specific image digest in a specific registry/repository, which previously was not possible.
Caveat:
I found an inconsistency within the spec of the simple signing format and the cosign implementation for the dockerreference field which we are using.
The spec specifies that this field SHOULD include a tag (either a floating tag or digest format) of the image reference, but cosign currently does not include this. Due to this we have to match the registry / repository name instead of each "full names".
What's still missing and will be done in the follow-up PRs of this series (besides the ones mentioned in the parent PR):

Ensuring within the image enricher that we fetch signatures from all the different locations of the image.

Checklist

[ ] Investigated and inspected CI test results
[ ] Unit test and regression tests added
- [ ] Evaluated and added CHANGELOG entry if required
- [ ] Determined and documented upgrade steps
- [ ] Documented user facing changes (create PR based on openshift/openshift-docs and merge into rhacs-docs)

Testing Performed

see CI (added unit tests).

Current dependencies on/for this PR:

master

PR #3511

PR #3512   👈

This comment was auto-generated by Graphite.


Multi tenant token

closes #580
Add logic for the API-features I currently work on.

[x] get accessToken from api
[x] generate accessTokens for 3rd party clients
[x] introduce token-caching

In my opinion its ready for reviewing.

I have to say that discord-bots arent my strength, but the logic for creating a new token at the api worked for me.
I prepared a caching-logic which currently isnt used to the full extend as we arent calling the other endpoints of the API yet

Wow this looks great 👍 I left a small comment

I think its ready to review


modified vue-treeselect class only for the showColumns treeselect com…

…ponent
By creating this pull request you agree to the terms in CONTRIBUTING.md.
https://github.com/Infineon/.github/blob/master/CONTRIBUTING.md
--- DO NOT DELETE ANYTHING ABOVE THIS LINE ---
CONTRIBUTING.md also tells you what to expect in the PR process.
Description
applied vue-treeselect class styling only for the showColumnSelect TreeSelect component to prevent the overriding of the styling for other TreeSelect components

📦 Published PR as canary version: 0.4.2--canary.23.7616af9ec305511c295430621ad819c2f9ac51a7.0

:sparkles: Test out this PR locally via:
npm install<EMAIL_ADDRESS># or
yarn add<EMAIL_ADDRESS>

:rocket: PR was released in v0.5.0 :rocket:


Fix some typos

Some typos in instructions and level tutorials fixed.
Note: old branches and pull request closed. I think the problem was I based a new branch off of hexcode_colors instead of master, so all the old commits came along with this one.

Now all the Hex commits are missing 😭. Will fix this


Support Python 3.11

Describe the feature
Support Python 3.11.x.
How to implement

Update this section
Update here too
And here

How to test

In your local environment, make sure python3 --version reports 3.11
Run the tests locally using these instructions

Additional context
https://github.com/dbeatty10/dbt-mysql/issues/117 is a similar issue for Python 3.10.

I also have the same needs.


<EMAIL_ADDRESS>

Release: https://github.com/emscripten-core/emsdk/releases/tag/3.1.8
Used by:

https://github.com/proxy-wasm/proxy-wasm-cpp-sdk
https://github.com/envoyproxy/envoy

Hello @bazelbuild/bcr-maintainers, modules without existing maintainers (emsdk) have been updated in this PR. Please review the changes.

I haven't used it with bzlmod yet. I've only been using the workspace instructions (https://github.com/emscripten-core/emsdk/tree/main/bazel). Adding to WORKSPACE.bzlmod works fine for my current usage, but I'm sure they would love bzlmod support upstream. I'd recommend first trying to add support there instead of adding a patch to the BCR.


Add a Windows specific Makefile and some instructions

Description
This PR aims to make the setup process compatible with Windows machines. To this purpose:

Add a Makefile.win for Windows users to run
Add a WINDOWS_USERS.md readme file with instructions

Note: Due to some issues with the installation of sent2vec, the windows Makefile will pull the repository and install it directly from the local clone, hence the addition of sent2vec into the gitignore file.
Checklist

[ ] Added link to Github issue or Trello card
[ ] Added tests

@SamDepardieu If the main difference is the VIRTUALENV and PYTHON location why don't we check at the begging of the file the OS of the user and initialise according so that we can have one Makefile?

@nsorros You do certainly get a point. Will edit this to add a system check on the main Makefile instead :+1:

Codecov Report

Merging #302 (1ae51c0) into main (149e6dc) will decrease coverage by 3.72%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             main     #302      +/-   ##
==========================================
- Coverage   86.22%   82.49%   -3.73%
==========================================
  Files          41       41
  Lines        2316     2314       -2
==========================================
- Hits         1997     1909      -88
- Misses        319      405      +86

Impacted Files
Coverage Δ

wellcomeml/ml/bert_classifier.py
23.25% <0.00%> (-69.77%)
:arrow_down:

wellcomeml/utils.py
40.00% <0.00%> (-60.00%)
:arrow_down:

wellcomeml/ml/bert_vectorizer.py
75.92% <0.00%> (-20.38%)
:arrow_down:

wellcomeml/io/s3_policy_data.py
91.17% <0.00%> (-0.13%)
:arrow_down:

wellcomeml/ml/bilstm.py
91.42% <0.00%> (-0.07%)
:arrow_down:

Continue to review full report at Codecov.

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

@nsorros I was just editing the .win makefile to pull it on my Windows machine for testing purpose, pushed the actual changes :)

Sadly I'm fairly sure this wouldn't run great in a container... It hardly runs on a physical machine as it needs some build specific libs that Jeff couldn't even get working on Vagrant. If you just want us to test for OS specific routes though, it's mostly about testing is the OS env variable is set (it is by default on all Windows systems), so that's something fairly easy to test for

I think in the case of Travis/CodeBuild the build environment is actually a virtualized WIndows Server instance which is similar to Windows 10 in most ways, however, we may have to find ways to install the required dependencies for building on windows in an automated way before this is diable.
The issues I had with vagrant were around VirtualBox I believe, effectively the only way around that is to install tensorflow-cpu instead of tensorflow because the Vagrant/VirtualBox VM has no access to the host systems GPU, and ends up installing/compiling for the FMA instruction set which then doesn't exist in the VM. That's an issue fairly specific to VirtualBox/Vagrant though and may get resolved by the 3.0 rollout of Vagrant.
So it's possible it may well work under CodeBuild / Travis for windows builds, just we may have to look at some additional scripts / tooling to run on windows builds before the Makefile to ensure that the pre-requisites are installed like MSVC++, Cygwin, etc... as I don't think Windows Server has the Linux subsystem like on Windows 10.


Paste As Plain Text - adding UPPER/lower case options

Description of the new feature / enhancement
It would be nice to add option to paste in UPPER/lower case
Scenario when this would be used?
many times I am pasting text into notepad++ then converting to UPPER/lower case for some type of documentation, adding these two as optional options to see on right-click menu would be helpful
Supporting information
The masses will agree with me if they have to do it more than once an hour
(not sure I know what I should add here)
I know I have looked for tools and not found any
there was a key combo I heard about but I can't ever remember it

/dup #24657

/dup https://github.com/microsoft/PowerToys/issues/24657


Scaling (Sharding)

THIS IS HIGHLY REQUIRED BECAUSE THE BOT IS NOW AT 20 GUILDS!
no need for todos, just read the d.js docs to get it functional

Eris has built-in shard support and it is not currently not needed.


Add a new ElasticSearchLogStashEventSerializer

to handle kibana v12 version of model + be sure to not send all message properties as String but also as long / double if possible (impact the json format)

We don't accept pull requests. Could you please attach the patch to a jira here: https://issues.apache.org/jira/browse/FLUME ? Thanks!

@harishreedharan done there https://issues.apache.org/jira/browse/FLUME-2784


STAGING - Typo in DT reservation

"Stay tuned and subscribes to our Telegram Channel" => "Stay tuned and subscribe to our Telegram Channel"

Seems fixed but forgot to put on verification, closed


Switch use of .loc to groupby

many places in the lc_classifier code use a .loc to access a subset of rows.  Switch this to groupby.
clarifying comment from Troy in V1 of this classifier:
"Here we're iterating over one of the indexes and then doing a .loc lookup to get a subset of rows.
I've seen lately that we're doing a lot of this kind of thing, not just in this notebook, and also that it's really error prone. I think it would be much better to do a groupby and iterate over the groups -- this is exactly what it's for. This would avoid the .loc lookups entirely and actually guarantee that we'll iterate over all the groups that we intend to, no more and no less. So we won't have to even think about whether band_list (or range(nobjects), etc.) contains exactly the same bands as df_lc or if it might accidentally be missing something, and it won't throw KeyErrors."
sections to be checked (among others)
2.3 - Remove some rows based on filtering out bad data
2.5 - Uniform Length and Spacing (would allow to also remove the try except block)

done as part of PR #163


[BUG] DeepSpeed command is not installing

I installed deepspeed with pip3 install deepspeed. However none of the commands (e.g. ds_report, deepspeed script.py) work. I get the following error:
ds_report: command not found
deepspeed: command not found.
I'm running this on an EC2 instance with an A10G GPU.
I have tried installing from the repo directly as well and still encounter this error. As I understand it, the deepspeed command is critical to using this framework, and running scripts with python directly is not advised. Does anyone know why the command is not working for me?

Can't believe I didn't figure this out immediately...I just had to add the bin directory to path.

Hi, may I know which bin directory you added in your path?


upgrate admin ui to 1.7.2

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@503123e). Click here to learn what that means.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master    #6497   +/-   ##
=========================================
  Coverage          ?   82.91%
  Complexity        ?    13091
=========================================
  Files             ?     1501
  Lines             ?    48647
  Branches          ?     5880
=========================================
  Hits              ?    40335
  Misses            ?     5534
  Partials          ?     2778

Continue to review full report at Codecov.

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


Link and text color is almost equal

Link and text color is almost equal, links are invisible at initial.
by @YonatanKof

just included medium-like underline


Normalization

Probelab's GoKademlia repo
LibP2P Go Kad DHT repo v2-develop branch
Important files:

kad.go: Defines a set of interfaces that are then implemented in libp2p-go-kad-dht v2 repo. They use Go Generics; might be worth checking them out before diving into this file. We discuss interfaces that we need to modify below.
routing/simplert: A simple RT implementing the RoutingTable interface. Includes a test function as well.
key.go: Implements the Key interface through 256 and 32 bit keys. The 32 bit keys can be used for simulating small networks.
server/basicserver/basicserver.go:

Interfaces we need to modify in kad.go:

Key interface --- we want another interface that is parameterized on top of the Key interface, called KeyPrefix. Alternately, this interface includes a CommonPrefixLength method. Maybe make a similar method called CommonPrefix?
RoutingTable interface --- we will develop a normalized RT interface, which will run the normalization algorithm in its implementation of AddNode. Its implementation of the NearestNodes will take only the KeyPrefix as an argument and then just grab all nodes in the normalized bucket.
Request and Response interfaces --- we need to have a PrivateRequest and PrivateResponse interfaces. These interfaces will not be parameterized on the Key type but the KeyPrefix type. In the PrivateRequest, we should replace the Target method with a method to preprocess the PIR request, if necessary, before computing the response. In the PrivateResponse, retain the CloserNodes method and type signature, but it should probably process the PIR response.
RoutingProtocol interface --- the FindNode method's third argument target will now be of type KeyPrefix.

See issues 1 and 2 in private-go-kademlia repo.


Add FaceNet face recognition project

Is your feature request related to a problem? Please describe.
This project uses FaceNet for face recognition.
dataset used = 5 Celebrity Faces Dataset
models and weights = https://drive.google.com/drive/folders/1pwQ3H4aJ8a6yyJHZkTwtjcL4wYWQb7bn
Describe the solution you'd like
This project uses the pre-trained Keras FaceNet model provided by Hiroki Taniai. It was trained on MS-Celeb-1M dataset and expects input images to be color, to have their pixel values whitened (standardized across all three channels), and to have a square shape of 160×160 pixels.
Describe alternatives you've considered
No response
Additional context
No response
Code of Conduct

[X] I agree to follow this project's Code of Conduct

Do assign it to me

@lakshmishreea122003   - you can go ahead! We are assigning you 21 days for this project, after which it will be assigned to someone else if not completed. All the best!
Name the file as: algorithm_dataset.ipynb and link it in the readme of the labeled directory as algorithm - dataset.