Address playwright race conditions and environment timeouts

Please don't delete this checklist! Before submitting the PR, please make sure you do the following:

[x] It's really useful if your PR references an issue where it is discussed ahead of time. In many cases, features are absent for a reason. For large changes, please create an RFC: https://github.com/sveltejs/rfcs
[x] This message body should clearly illustrate what problems it solves.
[ ] Ideally, include a test that fails without this PR but passes with it.

Tests

[x] Run the tests with pnpm test and lint the project with pnpm lint and pnpm check

Changesets

[ ] If your PR makes a change that should be noted in one or more packages' changelogs, generate a changeset by running pnpx changeset and following the prompts. All changesets should be patch until SvelteKit 1.0

Attempting to resolve #3552
First, the obligatory "it works on my machine"...
In attempting to address this issue, I encountered the following underlying difficulties:

Addressing "prefetches programmatically" test race by waiting for playwright network event
Handling environment dependent network requests issued by "prefetches programmatically" test
Addressing visibility issues by using playwright's page.isVisible method
Random test timeouts on my local machine, and apparently also in other environments according to discord. These were addressed by bumping the window.setTimeout threshold from 2s to 5s AND the test harness from 10s to 15s in utils.js, both of which were required.

Further info on changes for "prefetches programmatically" test, the following debug output
console.log(`waiting for ${baseURL}/routing/prefetched.json`);
requests.forEach((req) => {
  console.log(`req was: ${req}`);
});

Resulted in
waiting for http://localhost:3000/routing/prefetched.json
req was: http://localhost:3000/src/routes/routing/prefetched/index.svelte
req was: http://localhost:3000/@fs/C:/kit/packages/kit/src/runtime/env.js
req was: http://localhost:3000/routing/prefetched.json

waiting for http://localhost:3000/routing/prefetched.json
req was: http://localhost:3000/src/routes/routing/prefetched/index.svelte
req was: http://localhost:3000/routing/prefetched.json

waiting for http://localhost:3000/routing/prefetched.json
req was: http://localhost:3000/_app/pages/routing/prefetched/index.svelte-b0244d07.js
req was: http://localhost:3000/routing/prefetched.json

Note depending upon the vite mode, sometimes a third "fs" path would be fetched.
Possible improvements:

Unfortunately, the sets_paths and trailingSlash tests still fail on windows, seemingly reliably at least. Should I open a separate issue for this?
Should the integration timeout values just be changed to the following, in order to account for additional failures mentioned in the discord discussion:
timeout: process.env.CI ? 45000 : 15000,

All feedback welcome!
Last but not least thank you so much for your efforts on this project, SvelteKit and Svelte are wonderful!

The timeout thing is quite interesting. My first reaction was that it should never take more than 2 seconds to finish. Then I started thinking about how that could possibly be and I wonder if having more worker threads than CPUs means the worker processes slow down too much or block each other. It could explain how reducing the worker threads in https://github.com/sveltejs/kit/pull/3635 helps. I don't like that PR if it's just changing when we hit race conditions. But it might be more legitimate if we're talking about timeouts. If that's it, then raising from 2s to 5s is maybe not the cleanest solution. Maybe instead we should base the number of workers on os.cpus().length?

You're right @benmccann this PR is really awesome, and as I said in the #3635 PR that was just a little boost to get more tests to pass, it was definitely not a solution, this is a real fix.
Awesome stuff @harvey-k

Maybe instead we should base the number of workers on os.cpus().length?

That command mostly returns threads(number of) and not CPU cores, just something to keep in mind, but could work.

The timeout thing is quite interesting. My first reaction was that it should never take more than 2 seconds to finish. Then I started thinking about how that could possibly be and I wonder if having more worker threads than CPUs means the worker processes slow down too much because they're fighting for CPU time. It could explain how reducing the worker threads in #3635 helps. I don't like that PR if it's just changing when we hit race conditions. But it might be more legitimate if we're talking about timeouts. If that's it, then raising from 2s to 5s is maybe not the cleanest solution. Maybe instead we should base the number of workers on os.cpus().length?

At face value, I agree. However, in the context of #3552, let me try and articulate the questions/concerns I see being raised:

Should the integration test suite favor overall test throughput (a higher workers value) or favor lower individual test latency?

How can we enforce some sort of performance baseline, and can we do so by favoring lower individual test latency in the first question?

Does that sound about right? Unfortunately, my proposed changes fail to address either of these questions. Should they be broken out into separate issues? Anyways, below is my two cents on them.
For the first item, my interpretation of the current code is that the setting of the playwright workers config option to a higher value is that the current decision is to attempt achieve higher test throughput. E.g, please run these fast as possible, I want to get back to coding.
With regards to the second question, IMHO, the integration test timeout values should be very gentle guardrails, focusing on if the situation under test executes successfully. Enforcing a performance baseline is a separate concern, and would be better addressed by a testing framework designed with this as a primary goal. I'm not sure playwright falls under this category, although my only experience with playwright is this PR.
Finally, on my current system os.cpus().length happens to equal the currently used value of 8. Just for discussion, the default playwright parallelism level is half the number of processors.
Further confusing all this is the high variance in host test execution speed.  From a recent run, a bit over 10 minutes on windows to 4.5 minutes on linux.
Apologies in advance if all of this should've been posted to the issue instead of the PR here, I'm a bit new to this.

I'm personally still think #3635 is a good addition. More workers come with the expense of more memory used, which can likely cause longer timeouts, so we have to find the right balance point between workers and timeouts. That said this PR looks great so far (besides my comment above), thanks for digging into this!

Finally, on my current system os.cpus().length happens to equal the currently used value of 8. Just for discussion, the default playwright parallelism level is half the number of processors.

I think this is a really sensible default. It leaves a few CPUs free so that it doesn't lock up your machine. Maybe we could do something like process.env.ci ? num_cpus : num_cpus / 2;
On my machine, os.cpus().length is also 8. I changed it to use the Playwright default and it actually ran faster going from 6m to 5m, so I don't think we'll be losing much performance :laughing:

This is fantastic, thanks so much!


Local data store with temporal coverage information

I would like to have this for daily->monthly aggregation to be able to save the resulting monthly files into local data store and then be able to use the resulting data source as a 'normal' monthly data source.

#103

@kbernat Any plans moving this forward? I need this to move on with UC06.

http://cfconventions.org/Data/cf-conventions/cf-conventions-1.7/build/ch04s04.html

When defining a local data store, temporal coverage should be extracted from netcdf files.

Implemented. See also #153


Fix broken scraper: Angel List

Please do work for this task in a branch called issue-161.
Error from April 4 scrape:
C:\Users\JenniferHsu\Documents\GitHub\internaloha\scraper>npm run scrapers angellist --save statistics

><EMAIL_ADDRESS>scrapers C:\Users\JenniferHsu\Documents\GitHub\internaloha\scraper
> node scrapers/main.js "angellist" "statistics"

Starting scraper angellist at 9:11 PM
Angellist:  Our Error:  waiting for selector `#user_email` failed: timeout 30000ms exceeded
Finished scraping!

Angellist results from May 3:
$ npm run scrapers angellist dev open --save statistics

><EMAIL_ADDRESS>scrapers /Users/philipjohnson/github/internaloha/internaloha/scraper
> node scrapers/main.js "angellist" "dev" "open" "statistics"

[ 'angellist', 'dev', 'open', 'statistics' ]
Starting scraper angellist at 7:32 AM
Angellist:  Our Error:  waiting for selector `a.component_21e4d.defaultLink_7325e.information_7136e` failed: timeout 30000ms exceeded
Finished scraping!
Now parsing...
  .
  .


Style system documentation

Generate documentation using sassdocs comments

:tada: This PR is included in version 1.0.0-next.1 :tada:
The release is available on:

npm package (@next dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Allow maven components to automatically express their dependencies

Currently, if I have a maven conponent that has dependency upon another model element (be it a component, a container or a system), I have to write some code to add that dependency (typically, it will be called ContainerPopulator and will host a lot of switches).
It would be way better to use the maven ability to declare properties.
What I suggest here is, precisely

Declare maven property in the form <agile.architecture.depends.upon>...</agile.architecture.depends.upon> which would contain a list of already existing model components
Extend the maven component to read that property and link the maven module to the dependencies expressed in
Remove more java code!

In fact, it would be way smarter to extract all maven properties prefixed with agile.architecture from maven pom into model element, then process the agile.architecture.depends.on property.


Removed inadvertent it.only

Was the cause of the reduced test coverage from https://github.com/Netflix/falcor/pull/552#event-422622779

Oops! Programming and merging with kids hours well :)


My post disappeared

Describe the bug
A post I wrote yesterday is not accessible anymore. I see a notification about it, but trying to view the post shows "Post not found. The post may have been deleted". I did not delete it. I think I even got a later push notification about a reply to it, but that does not show in the in-app notifications.
To Reproduce
Steps to reproduce the behavior:

Post something to Bluesky

Expected behavior
Try to view the post and see it.
Screenshots
Post, the topmost one, shows in notifications:

If I open it, it flashes in view, I captured this to video so this is a frame from that:

Finally Bluesky says post not found:

Details

Platform: I think I used the iOS app to post originally. The post does not show with browsers either.
Platform version: iOS 16.6.1
App version: 1.56.0

Additional context
I think I even got a later push notification about a reply to it, but that does not show in the in-app notifications.

It's another case of https://github.com/bluesky-social/atproto/issues/1387

It's another case of bluesky-social/atproto#1387

Yep I realized that too, when seeing some other part of the thread and seeing the block. Was in my todo to come update the bug report here, but also did not find previous one. Thanks! Maybe it's useful to have this mentioned in this repo too, edit the title first now but don't close.

Closing as a duplicate of https://github.com/bluesky-social/social-app/issues/2243; this is being worked on


Change urdf robot name

Hello,
Ideally the urdf package name should be go1_description and the robot name should be go1.
Also adding a default value for the xacro DEBUG argument.

@sktometometo


Wrong Serpentine

Hi, I am currently trying this V4.0, what I found is, as you can see in the picture above, that the serpentine generation, to select the led's per Item is somehow wrong. But in the "Add ESP" there is everything right.

Is this just me, or is this a bug?
Tanks.

This issue was on my side. Fixed


Loading finetuned models

Type of Change
Bug
No API changed
Description
Adding capablities to load LoRA finetuned model using Peft

@srinarayan-srikanthan Thanks for your contribution!


Gantt plugin: Class 'Kanboard\Formatter\TaskGanttFormatter' not found

After installing the Gantt plugin and selecting the Gantt View the following error is shown:
Fatal error: Class 'Kanboard\Formatter\TaskGanttFormatter' not found in /home/brodbeck/brodbeck.com.br/kanboard/plugins/Milestone/Formatter/TaskGanttLinkAwareFormatter.php on line 14
Kanboard version 1.0.43 and Gantt plugin version 1.01.
After unistalling the plugin and reinstalling it the error didn't show again.

The error seems to come from the plugin Milestone, perhaps you could contact its author.

A patch has been proposed to the plugin author: https://github.com/oliviermaridat/kanboard-milestone-plugin/pull/11

The Milestone plugin has been updated.


Fixed oneword misstype in intro.txt

Just a oneword misstype in class-based-views/intro#Decorating class-based views documentation.

merged in f5fbddf22f5e9b760e76ef35f104270026c60693, thanks!


Update/Add [tool name]

Tool information

Tool name:
Tool license:
Add or update?
Desired version:
Approximate size:
If this is an add request:

Brief description of tool:
URL for tool's homepage:
Provide a basic test case to validate the tool's functionality:

Area for Triage:

Question, Bug, or Feature?:

Virtual environments affected

[x] macOS 10.15
[x] Ubuntu 16.04 LTS
[x] Ubuntu 18.04 LTS
[x] Ubuntu 20.04 LTS
[x] Windows Server 2016 R2
[x] Windows Server 2019

Can this tool be installed during the build?

Tool installation time in runtime

Are you willing to submit a PR?

@Am1401Am please create a new issue with all the fields properly filled. I'm going to close this one.
Thank you!


feature: add container memory isolation options

Signed-off-by: Allen Sun<EMAIL_ADDRESS>Ⅰ. Describe what this PR did
This PR added four alios related container isolation options for pouch. These four options are:

ScheLatSwitch
MemoryWmarkRatio
MemoryExtra
MemoryForceEmptyCtl

These options are introduced in PR #685 .
This PR made these options supported in Pouch daemon. When supporting, we add these options in the annotation filed of spec. And we make runc to deal these options rather than pouch daemon. We make this via passing these data as specified keys, like _MEMORY_XXX, like:

_MEMORY_WATER_MARK_RATIO
_MEMORY_EXTRA
_MEMORY_FORCE_EMPTY_CTL
_SCHEDULE_LATENCY_SWITCH

Ⅱ. Does this pull request fix one issue?

This is related to issue #688
Ⅲ. Describe how you did it
None
Ⅳ. Describe how to verify it
None
Ⅴ. Special notes for reviews
None

Codecov Report

Merging #743 into master will decrease coverage by 0.05%.
The diff coverage is 0%.

@@            Coverage Diff             @@
##           master     #743      +/-   ##
==========================================
- Coverage   13.58%   13.52%   -0.06%
==========================================
  Files          97       98       +1
  Lines        5927     5950      +23
==========================================
  Hits          805      805
- Misses       5068     5091      +23
  Partials       54       54

Impacted Files
Coverage Δ

daemon/mgr/spec.go
0% <ø> (ø)
:arrow_up:

cli/container.go
47.76% <0%> (-0.97%)
:arrow_down:

cli/create.go
0% <0%> (ø)
:arrow_up:

cli/run.go
0% <0%> (ø)
:arrow_up:

daemon/mgr/spec_alios.go
0% <0%> (ø)

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 d04f8a0...91ab3bd. Read the comment docs.

LGTM

LGTM


Adding EmergencyWithdraw event

Description
All saving strategies implement a function emergencyWithdraw(address _asset, address payable _wallet) which allows the owner to transfer all tokens of an _asset to an arbitrary address _wallet. Due to the sensitivity of this operation, an event should be emitted when the emergency withdraw executes.
Integrations Checklist

[ ]  Have any function signatures changed? If yes, outline below.
[ ]  Have any features changed or been added? If yes, outline below.
[ ]  Have any events changed or been added? If yes, outline below.
[ ]  Has all documentation been updated?

Changelog

Adding EmergencyWithdraw event in IYield.sol, AaveYield.sol, CompoundYield.sol, YearnYield.sol and NoYield.sol.
Adding comments for emergencyWithdraw function in all strategy contracts.

Event Signature Changes
Function Signature Changes
Features
Events

Codecov Report

Merging #229 (313216a) into master (6aaf59a) will decrease coverage by 0.03%.
The diff coverage is 0.00%.

@@            Coverage Diff             @@
##           master     #229      +/-   ##
==========================================
- Coverage   15.95%   15.91%   -0.04%
==========================================
  Files          16       16
  Lines        1736     1740       +4
  Branches      321      321
==========================================
  Hits          277      277
- Misses       1459     1463       +4

Impacted Files
Coverage Δ

contracts/yield/AaveYield.sol
17.34% <0.00%> (-0.18%)
:arrow_down:

contracts/yield/CompoundYield.sol
17.10% <0.00%> (-0.23%)
:arrow_down:

contracts/yield/NoYield.sol
23.25% <0.00%> (-0.56%)
:arrow_down:

contracts/yield/YearnYield.sol
10.66% <0.00%> (-0.15%)
: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 6aaf59a...313216a. Read the comment docs.


Create Pipeline in a specific folder in ADF using C#

Hi Team, Is there any property in this class to set the folder name of the pipeline ?

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

ID: c23ab318-1dbc-05a7-11b8-b61153532fea
Version Independent ID: 48afd0af-5252-62bf-8ea9-86af4c752a28
Content: PipelineResource Class (Microsoft.Azure.Management.DataFactory.Models)
Content Source: xml/Microsoft.Azure.Management.DataFactory.Models/PipelineResource.xml
GitHub Login: @erickson-doug
Microsoft Alias: douge

Issue got resolved in the latest package


Screen.width effected by Device.contentScale

Input
reSize = ->
	print Screen.width
	Framer.Device.contentScale = (Math.ceil Screen.width / 240) / 10
window.onresize = () ->
  reSize()
reSize()

Output
» 1807.5
» 907.5
» 1820
» 911.25
» 1825
» 913.75
» 1830
» 916.25

I think this is the expected behavior.
contentScale can go from 0.5 to 1. If it's 0.5, then the screen width and height will double, and you'll get 4x the number of pixels to work with (retina).
What are you trying to achieve? I'm curious :)

OK! I was trying to get my animation to scale to whatever device width it was put on ^^


chore(package): update rollup to version 0.45.0

Closes #238

Codecov Report

Merging #239 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #239   +/-   ##
=======================================
  Coverage   88.42%   88.42%
=======================================
  Files           1        1
  Lines         216      216
=======================================
  Hits          191      191
  Misses         25       25

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 19dde14...abafa12. Read the comment docs.


Support for running in a highly locked-down environment

This PR does two things:

Uses http://registry.npmjs.org instead of https://registry.npmjs.org for tarball downloads.
This was already preferred when fetching package metadata as seen here. So I believe this is consistent with existing behavior.
Adds basic proxy support.
While it would be possible to rely on environment variables I felt it would be helpful to explicitly support setting a proxy for downloads.

These were the features I needed to get this tool working behind a highly controlled corporate gateway.

@ricksbrown Thanks for the PR! I'm happy to merge the changes to add the proxy, but I agree with @luisdavim that Resolver.js should be https as well.
Is it not possible to use the new --registry option to force http?

@luisdavim Why should we use https instead of http to download artefacts from the public NPM repository?
This will simply force me to fork the project and publish my own version to NPM which is just "more noise" as far an I am concerned. I would much rather work together in a spirit of open collaboration with the goal of developing more quality and less quantity.
We all work with constraints in non-ideal circumstances, though our constraints may be different. My constraint (shared by many as my searching on stack overflow attests) is a highly controlled corporate gateway that uses self-signed certificates when intercepting https traffic.

@alexbrazier The new --registry option will not help because it does not affect the tarball URLs parsed out of the metadata, for example here: http://registry.npmjs.org/clean-css You can see all the tarball URLs refer to the https npm.org location even though we fetched the metadata from the http repo.

@ricksbrown yeah I see the issue you're having. I don't think I can just change it to use http as that will make it less secure for other users.
I've had a look at the yarn package and found they have a function called cleanRegistry which replaces the registry in the tarball to use the yarn registry.
Could we do something similar where if the --registry option is set it will replace the default registry, so you would have to run pb clean-css --registry http://registry.npmjs.org.
@luisdavim would this still work for your use case of --registry?

@ricksbrown at most we could create another flag to force the use of plain http. we should use https, specially when fetshing software from a public repository to ensure we're geting it from the real registry we trust and not some fake. have you heard about DNS spoofing and man in the middle attacks?

@luisdavim I think a flag is the way to go. I originally wrote it this way but then I noticed the resolver already used http so this was not a new vector.
@alexbrazier I'll take a look at that yarn function and probably update my PR to:

switch the resolver to use secure npmjs.org by default
add a flag to switch to insecure npmjs.org for both the resolver and the downloader

Have now updated so that it doesn't do anything with registry URLs at all.
There is now a nuclear ☢option which can only be invoked by typing the full insecure flag which pretty much says it all (I find it ironic how these highly secure, locked-down environments often encourage us to be less secure).
This method has the added bonus of working for tarballs that may be fetched from other https locations which was probably a problem I would eventually encounter anyway, so I prefer this solution.


Show/hide Password feature added

Issue reference:
Earlier there was no option for toggling showing/hiding password
Proposed changes:
I added this feature using react hooks in both logging in and registration pages.

Please delete options that are not relevant.

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Other (please specify)
[ ] This change requires a documentation update

Checklist:

[ ] My code follows the style guidelines of this project
[ ] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] My changes generate no new warnings

Additional info (if any):

@Siddhesh777
Some changes need:

Why are you changing the public/index.html. For adding icons, you have to use react-icons. Don't make any change in public/index.html ❌.
Also, you need to work on the UI a bit. The icon has no margins and it is touching the borders, and also, it's not aligned properly to the center.
In the setup guide and also in the pull request template, I mentioned that you have to follow the style guide. If you are using vs code, then install the prettier extension, and from the vs code settings, enable the format on save option. It's important that you do this since it maintains a consistent style of code (If you have done this step, then ignore this point 👍)
Give a new line between any two functions (code should not look ugly 😅)
I think you didn't update your forked repo before making changes, that's why you getting merge conflicts. Fix the conflicts

NOTE:
One simple you can fix the conflicts is to download the package.json and package-lock.json files from my repository and replace them in your forked repository. This is the simplest way you can fix that 👍
If you face any issues or have any doubt, you can ask me on the discord channel 👍


Some ideas around PlaygroundView and its CompletionList

Some things id like to see. So i am asking which of these points we can/should adress and which should be left to AvaloniaEdit project.
Allow use of right click for caret movement in editor
Since right click is not used for anything at the moment, not invoking any flyout it would be nice to make it move the caret.
The CompletionList is created without any item of its listBox selected
This leads to ability of running insertion on empty space.

we could check if selectedItem == null

And throwing a toast that no completion list item was selected.

we could fix selectedItem to First() on creation of completionList

This would also make it apparent that you have to select items to be AutoCompleted first, personally i was a bit lost why it was always just closing the completionList on single leftClick on MouseOverSelected item.
Better mouse handling

Theres a problem that mouseOver the item in scrollViewer has its own selection which conflicts which the completionList selected item.

mouse focus is bound to seletec item after right click:

after left click in completion list, mouse selection is unbound from selected item:

CompletionListSelectedItem -> GlassCard
MouseOverSelectedItem -> Button

Simply using left click when no item is selected just closes the CompletionList.

This leads to question if it would not be worth it to create mouse event handler for the CompletionList and map the mouseOver selectedItem to the completionList selected item.
Not rly sure how this would be implemented getting VisualChildren and quering the listBox items?
Making custom hitTest for the listBox items under cursor?
But certainly it would be nice to automaticaly select items which are under mouse pointer.
Dont constatly rerender on each character input
I would prefer if there were 2 buttons Render and Reset
as currently for whatever char u type it tries to render and simply constatly spams exceptions bcs the Xaml is not yet valid for XamlParser to process it and pointlessly has to produce exceptions as you type.
Change the xaml in the PlaygroundView.cs to readonly raw strings
        private readonly string StartingString =
            """
            <suki:GlassCard Width="300" Height="320" Margin="15" VerticalAlignment="Top">
                <Grid>
                    <TextBlock FontSize="16" FontWeight="DemiBold" Text="Humidity" />
                    <Viewbox Width="175" Height="175" Margin="0,0,0,5" HorizontalAlignment="Center" VerticalAlignment="Center">
                        <suki:WaveProgress Value="{Binding Value, ElementName=SliderT}" />
                    </Viewbox>
                    <DockPanel VerticalAlignment="Bottom">
                        <icons:MaterialIcon Width="20" Height="20" DockPanel.Dock="Left" Foreground="#666666" Kind="TemperatureLow" />
                        <icons:MaterialIcon Width="20" Height="20" DockPanel.Dock="Right" Foreground="#666666" Kind="TemperatureHigh" />
                        <Slider Name="SliderT" Margin="8,0" Maximum="100" Minimum="0" Value="23" />
                    </DockPanel>
                </Grid>
            </suki:GlassCard>
            """;

I think that these are good ideas, but we unfortunately don't have time to improve the playground part as we're just focusing on solving issue and make it ready for a release. To me it's just a kind of "gimmick".
However, if you're willing to improve the playground experience to be closer to an IDE experience, I would be glad to accept your PR to improve it👍

Sure, i was just unsure if it shall be tackled on our side, i will work on it.
Btw expanding the scrollviewer listbox with more items, glitch appeared. Not sure if this is bug or just lack styling implementation for this.

Sure, i was just unsure if it shall be tackled on our side, i will work on it.
Btw expanding the scrollviewer listbox with more items, glitch appeared. Not sure if this is bug or just lack styling implementation for this.

Oh cool, you can contact me on discord ( 'KoalaKoala' ) if you want to discuss more of it. I'm closing this for readability.
I will take a look on scrollviewer style.


Add TLS v1.3

i.e., add TLS v1.3 to the list in issue  #1144

That would be handy!

+1

+1

plus one

+1 Please add this

+1

+1

+1

Now available at http://caniuse.com/#feat=tls1-3


auth: context.WithValue has string type keys

// The provided key must be comparable and should not be of type
// string or any other built-in type to avoid collisions between
// packages using context. Users of WithValue should define their own
// types for keys. To avoid allocating when assigning to an
// interface{}, context keys often have concrete type
// struct{}. Alternatively, exported context key variables' static
// type should be a pointer or interface.
func WithValue(parent Context, key, val interface{}) Context {

https://github.com/coreos/etcd/blob/1d01aaa3958069e062805edd808b4658e1a04133/auth/store.go#L1066-L1073
From https://github.com/coreos/etcd/pull/8031.
The key should have been typed (e.g. keyABC{}), rather than string.
Otherwise, it could collide with other keys (e.g. tracing).
"index" and "simpleToken" have not been released yet, so should be safe to change.
Do we have any other string context keys in 3.2? /cc @mitake
UPDATE: might need handle 3.1 https://github.com/coreos/etcd/pull/5672 compatibility as well.

@gyuho I didn't know the keys should have its own type, thanks for letting me know. We don't have keys other than the two.
BTW we are using context instead of a custom struct for passing the parameters for reducing dependencies from etcdserver to auth (the result of offline discussion with @xiang90 ). But if we need custom types for the params, it must introduce such a dependency between the packages. So I think that stopping using context and introduce a struct for the parameter would be fine. How do you think? @xiang90

@mitake @xiang90 I meant something like this:
context.WithValue(ctx, simpleToken{}, "bar")

And we have 2 places to handle backward compatibility:
https://github.com/coreos/etcd/blob/5ed5ee51f57a635c84acde19d96c288f57d1754a/auth/simple_token.go#L189-L192
https://github.com/coreos/etcd/blob/5ed5ee51f57a635c84acde19d96c288f57d1754a/proxy/grpcproxy/util.go#L66-L67

@gyuho yes, in such a case, the definition of simpleToken{} should be in auth and used from etcdserver? Then the dependency between the packages can be increased, so I think dropping context and introducing custom structs rather than using context would be simpler.
BTW do we need to care about the backward compatibility between packages which cannot be seen from external ones?
Also, the code of etcd/proxy/grpcproxy/util.go isn't related to other context usages. I think the type of key cannot be changed because the parameter is initialized like this:
https://github.com/coreos/etcd/blob/master/clientv3/client.go#L169-L175

@mitake Oh, somehow I was thinking context passed from other servers (where we need worry about compatibilities against older versions). But in this case, the context only goes from etcdserver to auth package, and never goes to other servers. So breaking change should be fine.

so I think dropping context and introducing custom structs rather than using context would be simpler.

Agree.

key cannot be changed because the parameter is initialized like this:

I see. Then, proxy should fine, as it is now.

@gyuho I tried to eliminate context styled parameter passing from etcdserver to auth, but found that it is quite useful for LeaseRevoke(): https://github.com/coreos/etcd/blob/master/etcdserver/server.go#L772-L775 . Probably employing a newly defined struct instead of context requires lots of hard to follow changes. I'll replace the string typed keys of the existing contexts for following the correct usage of context.


Shape of 'counts' and 'counts_comp_err' sometimes disagree

Yesterday I closed issue #291 after performing some checks, but now I see that in some cases, the shape of counts is not the same as counts_comp_err, for example:
solo_L1_stix-sci-xray-cpd_20210215T130339-20210215T132124_V01_2102150012-53010.fits
> help, data.counts
<Expression>    BYTE      = Array[15, 12, 30, 102]
> help, data.counts_comp_err
<Expression>    FLOAT     = Array[15, 12, 32, 102]

It may well be that only the data acquired between Nov. 2020 and March 2021 are affected, due to a misconfiguration of the detectors.

I checked the generated files and worked as expected:
hdul = fits.open('http://pub099.cs.technik.fhnw.ch/testing/esa_release3/L1/2021/02/15/SCI/solo_L1_st
    ...: ix-sci-xray-cpd_20210215T130339-20210215T132124_V01_2102150012-53010.fits')
hdul[2].data['counts_comp_err'].shape
(102, 30, 12, 15)

hdul[2].data['counts'].shape
(102, 30, 12, 15)

I also checked a few files, and I can confirm that the issue seems to be fixed.


Did everyone use the BFGS method or did you try to find better algorithms?

I used that one and so the rest of people I assume


Add support for Hetzner Private Networks

What this PR does / why we need it:
This PR implements support for Hetzner Private Networks. A new optional field is added to the Hetzner spec called network that consumes a network ID or name. It is expected that the network already exists, i.e. that it's created by the user.
To make this work I had to vendor the latest version of the hcloud-go library which includes support for networks.
Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #599
Special notes for your reviewer:
This PR is still work in progress. There are some questions and tasks that should be resolved before merging the PR:

How can I test does it work as expected without pushing the image somewhere?

Running machine-controller binary on the local machine complains about plugins.

Should I add some E2E (or other) tests for this feature?
Should we support just a single network or multiple networks?

It seems like a Hetzner server can be attached to up to 3 networks.

It is up to be researched should I change the provisioning logic to make this work.

How machine-controller knows which network interface to use by default, i.e. use private instead of public interface? Is there some logic for that, that might need to be updated?

Add support for Hetzner Private Networks

@alvaroaleman When you get some time please take a look at questions I left in the PR description. It's nothing urgent, so no hurry. :slightly_smiling_face:

Running machine-controller binary on the local machine complains about plugins.

That is supposed to work :thinking:

Should I add some E2E (or other) tests for this feature?

Hmm, I think this is a bit tricky, because something has to create the network we use there beforehand

Should we support just a single network or multiple networks?

I guess there is no harm in supporting more? I don't really see the usecase, but if we don't, someone will complain sooner or later I imagine

How machine-controller knows which network interface to use by default,

I don't understand the question, where does the machine-controller care about the network interface?

@alvaroaleman

I don't understand the question, where does the machine-controller care about the network interface?

That's what I'm asking. :slightly_smiling_face: Does the machine-controller care about the network interfaces anywhere? As far as I get all the existing code, it's just enough to attach the machine to the network and that should be it.
Also, have I broke something? I guess this is not really a flake. :sweat_smile:

/retest

Also, have I broke something? I guess this is not really a flake. ￼

not sure what was going on with the tests yesterday, probably hetzner running out of capacity.

Does the machine-controller care about the network interfaces anywhere?

Not really, it uses the IP to match the machine to its node on platforms that do not have a cloudprovider like Hetzner but thats about it

Not really, it uses the IP to match the machine to its node on platforms that do not have a cloudprovider like Hetzner but thats about it

Okay, that makes sense. I think this PR has everything covered now and should be ready for review. :slightly_smiling_face:

/test pull-machine-controller-e2e-ubuntu-upgrade

@alvaroaleman Fixed, PTAL

/lgtm
/approve

/retest


fix connmanctl tether wifi command

disable is not a valid option. The correct command is tether wifi off.

Thanks @dlech


rabin_finger_print unit tests are added. Some schema_tests added. [API-1297]

Extra rabin_finger_print units tests and schema test for all types are added.

Windows test PASSed.

Linux test PASSed.

Windows test PASSed.

Linux test PASSed.

Linux test PASSed.

Windows test PASSed.

Linux test PASSed.

Windows test PASSed.

Linux test PASSed.

Linux test PASSed.

Windows test PASSed.

Linux test PASSed.

Windows test FAILed.

Windows test FAILed.

Linux test PASSed.

Windows test FAILed.

Linux test PASSed.

Windows test FAILed.

Linux test PASSed.

Windows test FAILed.

Linux test PASSed.

Windows test FAILed.

Linux test PASSed.

Linux test PASSed.

Windows test FAILed.

Windows test FAILed.

Windows test FAILed.

Linux test PASSed.

Linux test PASSed.

Windows test FAILed.

Linux test PASSed.

Windows test FAILed.

Linux test PASSed.

Linux test PASSed.

Windows test PASSed.

Windows test PASSed.

Linux test PASSed.

Linux test PASSed.

Linux test PASSed.

Windows test PASSed.

Linux test PASSed.

Linux test PASSed.

Windows test PASSed.

Windows test PASSed.

Linux test PASSed.

Windows test FAILed.

Windows test FAILed.

Linux test PASSed.

Linux test PASSed.

Linux test PASSed.

Windows test PASSed.


[FEAT] Reviewers statistics changes

Describe the solution you'd like
A new column: The longest PR waiting.
Standardize columns naming. To check -> Sum of code to check.

I will do this


feat(workflows): add helper and workflow to keep keystone and nautobot in sync

Adds a helper and a workflow to keep keystone and nautobot in sync.

I'm really not a fan of my approach with the tests. Maybe even the whole thing. Would be happy for some feedback on changes. @rackerlabs/understack-dev

The requests-mock might not be catching all HTTP calls because it feels slow.

The requests-mock might not be catching all HTTP calls because it feels slow.

https://vcrpy.readthedocs.io/en/latest/ ?

So need some ideas on how to better check the workflow template against the schema. Otherwise I think this will work.


[3.6.4] PostgreSQL: NumberFormatException: For input string: "5beta2"

1.) Fresh installation of dbeaver-ce-3.6.4-x86
2.) Added postgresql driver 9.4.1208.jre7 with the help of the wizard (screenshot 1)
3.) When trying to connect to postgresql server, GUI is screwed up ("Failed to create the part's controls), and error log show "Error initalizing datasource: invalid version 9.5beta2: non-numeric 5beta2" (screenshot 2)

It is a bug in PG version detection function.
Will be fixed in the next version


Date Field: 2-Digit Year Format

Describe the feature in detail (code, mocks, or screenshots encouraged)
For really compact date fields, it is often helpful to specify the year by only specifying the last 2 digits.
Is there a way to implement this with the current features, or would that need to be a new feature that could be considered?
What type of pull request would this be?
Enhancement
Provide relevant links or additional information.
No response

This isn't possible with the library currently. Given the complexity this would introduce (considering we use Intl.DateTimeFormat and there isn't a dateStyle that outputs a 2-digit year), it's unlikely to be added anytime soon, so going to close this for now.
Should things change in the future I am happy to reopen this.
Thank you!


Add conditional requests and cache-control headers on the 'spaces' endpoints (#998)

goa-generate conditionalEntity and conditionalEntities methods
on the contexts with domain models as arguments.
also introducing a new goa generator for helper function related
to app.* structures.
Fixes #998
Signed-off-by: Xavier Coulon<EMAIL_ADDRESS>

[test]

[test]


RuntimeInfo could display assemblies loaded

If RuntimeInfo displays assemblies inside packages and where they are loaded from then it would help you identify if a package has been serviced and if an assembly is loaded from a global cache instead of locally with the app.

Dup of https://github.com/aspnet/Diagnostics/issues/237


[Metrics] Allow users to specify histogram buckets in clipper_admin

Currently, we support users to specify the histogram buckets in metric_config.yaml, we should enable users to set the configuration inside clipper_admin interface so users can interact with metric inside clipper_admin through scripting or python-cli

After some thoughts:

metric_config.yaml is not visible to users and packed directly into rpc.py. This metric_config files is for Clipper's own metrics.
If users want to specify histogram buckets for Clipper's metrics (as overriding default buckets), one place can be at deployer::create_endpoint. However, this requires changes in all the possible deployers and creates unnecessary complication.
The preferred way to do it: Let the #401's metric server be not just a metric receiver but also some sort of api server that

Enable overriding default configuration at init step in ModelContainer
Enable schema definition for user_defined metrics
Able to receive metrics during the lifetime of the model container.

/api/v1/

add
POST: name, type, description, (bucket)
report
POST: name, metric data
update_default
POST: name, bucket

That makes sense. I think it's logical to place model-specific metric configuration (whether that is changing default bucket sizes, adding their own metrics, etc), in the model container code.

The other thing to keep in mind is how to support these metrics in model containers implemented in other languages. Is there a way to keep the metrics exporter code unified in Python, and export to it from a model container written in Java or R?

Closed via #440


Retrieve instance Parameters of service instances and bindings

Motivation
In many cases services require input parameters for service instances or service bindings creation. These parameters are used by the broker in the provisioning process.
This information is valuable to the instance owner and might be required in order to manage the instance.
Currently service manager does not store this information and thus it cannot be retrieved.
BLI: https://jtrack.wdf.sap.corp/browse/SAPCPCFS-17437?src=confmacro
Pull Request status
Use checklists as a means to represent the status of your Pull Request.
For example:

[x] Initial implementation
[ ] Refactoring
[x] Unit tests
[ ] Integration tests

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

Coverage decreased (-0.2%) to 83.855% when pulling 12fc24f58128afadd35dc41bddc2af38b7868078 on instance_and_binding_params into 4fd118133a4001cbcaca566e57b7a69de83c4ad5 on master.


tsEssentialPlugins.switchExcludeCoveredCases should be removed

I think this one should be removed: tsEssentialPlugins.switchExcludeCoveredCases as it is now supported by default by TS.

Yes, we are aware of it, thx for recording, but not priority


Update release.json, .gitlab-ci.yml and notify.yml with 7.61.x

What does this PR do?
Motivation
Describe how to test/QA your changes
Possible Drawbacks / Trade-offs
Additional Notes

LGTM, although shouldn't we wait for the actual release to start using the stable branches for integrations?

Switching to 7.61.x is correct for them, they already released the integrations on this branch


Clean slate with Winnow 2

Continuing the rewrite started by @tertsdiepraam  https://github.com/uutils/parse_datetime/pull/61

The functions in lib.rs keep the same signature
I kept the tests in lib.rs too all they are passing
90% of the parsing was written by @tertsdiepraam (check #61)
Added timestamp with @\d+ format
Added timezone abbreviation names
Added 8 digits dates MMDDhhmm
Using winnow

@tertsdiepraam I squashed your commits into a single commit, I hope you don't mind

Looks cool! A few initial comments to send you in the right direction. One of the reasons for this rewrite is that chrono wasn't cutting it for adding all the items together. Instead we should  add all the items together ourselves to really match GNU. It'll require a lot of experimentation, but it'll make the compatibility much better. I think most of the corner cases were around the ends of months. I believe GNU had some overflow behaviour there that chrono didn't. So I recommend first creating a custom datetime struct to manipulate and then mapping that to chrono.
Squashing the commit is absolutely fine by the way. Thanks for continuing this!

please let us know when it is ready to be reviewed :)

please let us know when it is ready to be reviewed :)

it is ready for review (:

a test failed:

---- tests::iso_8601::test_t_sep stdout ----
error: test failed, to rerun pass `--lib`
thread 'tests::iso_8601::test_t_sep' panicked at src/lib.rs:128:13:
assertion `left == right` failed
  left: 2021-02-15T06:37:47-05:00
 right: 2021-02-15T06:37:47Z
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

a test failed:

---- tests::iso_8601::test_t_sep stdout ----
error: test failed, to rerun pass `--lib`
thread 'tests::iso_8601::test_t_sep' panicked at src/lib.rs:128:13:
assertion `left == right` failed
  left: 2021-02-15T06:37:47-05:00
 right: 2021-02-15T06:37:47Z
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

I saw this in the CI, but I couldn't reproduce it here, for some reason it is passing to me, any ideas on how to reproduce?

a test failed:

---- tests::iso_8601::test_t_sep stdout ----
error: test failed, to rerun pass `--lib`
thread 'tests::iso_8601::test_t_sep' panicked at src/lib.rs:128:13:
assertion `left == right` failed
  left: 2021-02-15T06:37:47-05:00
 right: 2021-02-15T06:37:47Z
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

I saw this in the CI, but I couldn't reproduce it here, for some reason it is passing to me, any ideas on how to reproduce?

Okay, I fixed the test. There was a .fixed_offset() call missing. Without this, it prints Z instead of the offset and the test fails

The codecov is failing, there are some cases where it is checking if the test code is covered, should I fix them all?, or is there some configuration I'm missing!? codecov is kind of new to me

Codecov can be wrong sometimes. It's nice to have good coverage, but it might be alright.

Hi! I was looking at this again and I found an issue with how you're currently using chrono. Here's my theory:

It's currently 2024-09-11 and September is a month with 30 days.
I give as input: 2024-01-31
While setting the Date item, you first change the day, then the month and then the year.
At each of those, the validity is checked.
That means that you adjust the date first to 2024-09-31, then 2024-01-31.
However, 2024-09-31 is an invalid date and chrono will therefore yield and error even though I have entered a valid date.

We need to find a way to construct the times such that this never happens. Just changing the order won't cut it because that can still lead to invalid states. chrono might be more of a hindrance than a help here, unfortunately.

Hi! I was looking at this again and I found an issue with how you're currently using chrono. Here's my theory:
1. It's currently 2024-09-11 and September is a month with 30 days.

2. I give as input: `2024-01-31`

3. While setting the `Date` item, you first change the day, then the month and then the year.

4. At each of those, the validity is checked.

5. That means that you adjust the date first to `2024-09-31`, then `2024-01-31`.

6. However, `2024-09-31` is an invalid date and `chrono` will therefore yield and error even though I have entered a valid date.

We need to find a way to construct the times such that this never happens. Just changing the order won't cut it because that can still lead to invalid states. chrono might be more of a hindrance than a help here, unfortunately.

Hi Terts,
I introduced a function to create dates from naive dates instead of using with_ method chains.
About the month behavior, if I understood correctly GNU gets the number of the days in the current month and adds it to the date, I implemented this behavior added your test and one more.

@tertsdiepraam I was looking into the fuzzy testing. I added the code so it generates fuzzy dates with some sanity and caught some problems, I will look into them next.

sorry but some tests are failing:
failures:
    items::date::tests::test_year
    items::date::tests::with_year
    items::tests::date_and_time
    tests::offsets::invalid_offset_format
    tests::test_relative::chrono_date
    tests::test_relative::gnu_compat
    tests::test_relative::test_month

and needs some rebasing

sorry but some tests are failing:
failures:
    items::date::tests::test_year
    items::date::tests::with_year
    items::tests::date_and_time
    tests::offsets::invalid_offset_format
    tests::test_relative::chrono_date
    tests::test_relative::gnu_compat
    tests::test_relative::test_month

and needs some rebasing

I will rebase it
But right now I have a problem with Chrono, I'm looking into alternatives like https://time-rs.github.io/book/how-to/create-dates.html

Hello, I updated the PR, some key notes:

I found that if we use only years in the range 0 to 9999, Chrono and GNU behavior coincide. I update the PR with such a fix, the fuzz tests for example are generating years in this range.
GNU accepts years in the range 0 to<PHONE_NUMBER>
Chrono accepts years in the range 0 to 262144
But when using years >9999 the chrono add a '+' the output format where GNU doesn't

Let me know what you think, if this is too bad, or if it is okay for now. I guess that to achieve 100%
GNU compatibility we'll need to do our own date math.
BTW I was playing with GNU date and I found this behavior
TZ=UTC date -d '0000-01-01 00:00 utc+00001' '+%Y'
-001

Here -001 is the year, it looks like it is subtracting 1 second from the date (which is 0)
and it underflows to -1, I guess this is a bug, here is again all the output
Z=UTC date -d '0000-01-01 00:00 utc+00001'
Fri Dec 31 11:59:00 PM UTC -001


feat: add multiple working dirs

Closes #81
This adds the ability to specify multiple terraform plans based on different working directories. The mixin config can now specify a list of directories for the different working dirs. Then each step can specify the working dir for the run of that step.
Example mixin config
mixins:
  - terraform:
      workingDirs:
        - infra1
        - infra2

Example install step with working directory specified for the step:
install:
  - terraform:
      description: 'infra 1'
      workingDir: 'infra1'
      vars:
        infra1_var: ${bundle.parameters.infra1_var}
      outputs:
        - name: infra1_output
  - terraform:
      description: 'infra 2'
      workingDir: 'infra2'
      vars:
        infra2_var: ${bundle.parameters.infra2_var}
      outputs:
        - name: infra2_output

Updated integration test with a multiple working dirs bundle.
Added usage docs.

Refactor to have the build step inspect all actions for "workingDir" specified and collect them at build time. Fallback to the "workingDir" set in the mixin config or default

oop, @sgettys  can you fix that test?


term request: health status inclusion criterion

label: health status inclusion criterion
definition: "An inclusion criterion that defines and states one or more clinically significant bodily components, dispositions, and/or bodily processes of an entity that are inferred from relevant clinical findings or self-reported, which, if met, makes the entity suitable for a given task or participation in a given process.”
examples of usage: ‘diagnosed with Type 2 diabetes mellitus’, ‘E11.4’, ’not finding of hypertension'
ontology term requester: MIABIS2.0

Discussed on OBI Dev call on 2/12/18 and approved.

resolved:
https://github.com/obi-ontology/obi/commit/2a84d760e1351707b248fb20465cb4031ad693d4


Detect changes

Hello,
Have been looking through the code base and couldn't spot a way to identify if the content in the editor has changed. This would be very useful in events where an autosave feature is used and you only want to trigger the autosave if the editor has been marked as changed/dirty. Am I missing something?
Thanks

Any updates on this? It would be nice to have a single changed event that was triggered whenever an action occurred that has potentially changed the output.
Given the EvenBus is shared by all ST instances, it seems like it would also be nice to have a convention with events generally where they all passed the ST instance as the first argument, and all block events passed the block as the second argument, with any custom arguments after that.
I might be able to look into doing this (if people don't mind the second one being a breaking change).

Hi @jamesthurley,
The instance manager is going to be removed from a future version of sir-trevor. At present ST is doing too much and it's a good idea to reduce the core code base where possible.
This will also mean that events will probably be per instance, rather than through a global EventBus.
This doesn't answer your question, but at least gives you an idea of the direction the project is taking.

Hi @raffij, was there any movements on this?


Using dedicated guest WiFi restricted by MAC address and no internet access

Lot of modern routers allow setting up dedicated guest WiFi with MAC filtering and mark it hidden (Unifi network or TPLink Extenders), in which case something like  NodeRed flow can process MQTT data and forward via MQTT or REST to HomeAssistant?
Would this work without needing any additional reverse engineering?
#NotReallyAnIssue

Would this work without needing any additional reverse engineering?

Nope, but only because you can't use hidden SSIDs with the test mode I uncovered.
Having a hidden network also doesn't really help with security since you can use the test mode with a password-protected WiFi network. However, creating a segregated network for the Vue 2's test mode is a good idea, if only because the test mode does not support TLS MQTT & is vulnerable to man-in-the-middle attacks.

Also, if it's something that interests you, we're working on a ESPHome component that would allow you to flash the onboard chip for maximum flexibility/configurability. It's actually in a working state right now if you want to test that out.

@flaviut That's unfortunate, I guess either way this device needs to be on isolated network to prevent work done so far getting nuked by "them".
@Maelstrom96 Does the component require soldering to flash? (I didn't see pictures of inside), I can try it assuming the process doesn't need any other equipment. (any link where I can read more about it?)

The company behind this thing is unusually open to folks modifying it, there's a thread dedicated to reverse engineering it on the official forums, where I've posted links to this project. As far as I'm aware, those links are still there.
You don't need to solder to flash, but soldering does make it easier if you'll be flashing it a bunch of times, like while developing. As far as tools go, you need two things (no affiliation with any of the folks I'm linking to):

UART/USB adapter like https://www.ebay.com/itm/313578857750
male to female jumper wire like https://www.ebay.com/itm/234232880745

You might also need a 3.3V or 5V power supply, I think I was getting brownouts while programming mine. Perhaps something like https://www.ebay.com/itm/274903424910 (fully adjust the power BEFORE connecting it to the board), but there's a decent chance you can get away without one.
I forgot to take a picture of the PCB, but if someone else has one, please do upload it!

Here's the PCB; under those jumper cables is the debug header that we've been using for testing. As flaviut was saying, it would be possible to flash without any soldering; two things you might want to do before that is a) backup the old firmware and b) get the calibration data. When the ESPHome component is released, we'll probably write some documentation to make those steps more clear

@krconv Is the white connector (beside the chip) wifi antenna that device came with? What's the bottom white plug, I assume you added it?

@rchukka
The white cable with the gold connector is the WiFi antenna connector. It goes to the female SMA connector on the enclosure.
The 2x2 white connector at the bottom of the board is the voltage sensor/power supply connector. It pokes out the bottom of the enclosure. You connect it to the mains voltage when you plug it into your panel.

@krconv Is the white connector (beside the chip) wifi antenna that device came with? What's the bottom white plug, I assume you added it?

The connector just beside the ESP32 is indeed for the Wifi antenna, but it's just an extension cable to another connector that is attached to the plastic body of the Vue 2.
The bottom white plug is standard. It's for the line voltage harness, so the device can be powered and measure the voltage from your breaker panel. The only thing that is altered in this picture is the 2.54mm dupont header on top of the ESP32.


Feature Request: Subscriptions / Live Queries

Feature request
Is your feature request related to a problem? Please describe.
real-time all the things!
Describe the solution you'd like
Describe alternatives you've considered
Additional context

Subscription support is likely a ways off since postgres has no websocket support to piggyback on, but we do plan to explore it
We have some ideas from supabase/realtime to try when the time comes

SSE would be better than websockets I think.

SSE would be better than websockets I think.

Agreed. If for subscriptions Websockets do not feel necessary. I popped an issue Re: SSE into the Realtime repo some time back. Please consider upvoting as I see an opportunity to improve Realtime with SSE and a potential SvelteKit example to accompany the existing vdom-based examples provided.

This can be kinda achieved by using custom rest server which polls stored  persistent queries as mentioned in #189 every few seconds and generates server-side-events or fetch response everytime data changes.
This is actually very efficient since single polling loop can satisfy n subscriptions.

Interactions between queries and role + row level security make subscriptions difficult to implement and cache securely
supabase/realtime uses supabase/walrus to solve those interactions efficiently but it is tightly coupled. I'm in the process of refactoring walrus to be re-usable by pg_graphql. Things are headed in the right direction but it'll still be a while before subscriptions are supported by the platform

Could you provide an update on the status of the work on walrus and adding it to pg_graphql? Some kind of time horizon when you might provide subscriptions for pg_graphql?

sure thing,
The supabase/walrus work is on the linked branch. Currently  supabase/realtime does a kind-of smart polling thing to query Postgres for new WAL records. The walrus worker branch extracts the DB polling and security stuff out of realtime and implements a background worker that listens for new WAL records on a logical replication slot (much faster & lighter). The filtering logic and column security logic was ported to rust where possible
That logic will start getting rolled out in 2-6 weeks once the realtime team finishes their transition from single to multi-tenant.
The worker was designed be reusable by pg_graphql. The output of the walrus worker is generic and we can plug different transport layers on top. We'll either write another transport layer and/or web socket sever to expose the functionality depending on how thing shake out.

A major reworking of pg_graphql is also about to drop. We ported it to use the pgx framework (rust). There's one failing test remaining and then they'll be a PR.
Psyched to get ^ out so we can get back to features!
Once that lands the feature priorities loosely are:

add a global Id of some kind (easy)
add a select 1 record by global id  interface for each table accountById(globalId: ID) (easy)
(maybe) composite support
(maybe) admin interface i.e. create tables/columns through GraphQL which are immediately reflected
(maybe) an integration or two e.g. OneGraph
an optional webserver to remove the dependency on PostgREST for exposing over HTTP
connect background worker to ^ and expose subscriptions through webserver

So basically there's a ton going on and things are starting to align but it isn't imminent. Sometime next year is my best guess but I'd struggle to narrow it down past that.

@olirice lmk if you want to chat about this. You could implement the same logic as Logflare Endpoints.
Basically, subscribe to a query with an interval and and idle timeout.  Where the interval would be the time between pushing results to clients, and the idle timeout would be when the process dies after the last request to said query.
So a client would connect, and listen to results of a query which would get updated every, say 5 seconds, and then the process would continue polling and caching these results for, say 5 minutes, so that if someone reconnected they'd get results very quickly again.

any updates? curious how it's going.

@aaronbond its still a ways out for now
we're rapidly getting to the point where request/response oriented pg_graphql core functionality is complete. That doesn't mean expanding the schema will stop, just that everything needed for performant applications is available. After that, realtime will get more attention.
A lot of thought is going into how to get subscriptions right for pg_graphql. Here's a summary of the ideas that have been floating around:
There are 2 options for "listening" for changes
WAL (write ahead log)
The postgres write ahead log is a stream of changes to the database that you can listen to. It is intended creating replica databases, for reporting etc. This is how supabase/realtime works.

Security
pg_graphql leans on postgres to apply role and row level security. Data is passed over the WAL in full, so we don't have a convenient way to detect who has access to what. You can (mostly) solve that for insert/update by querying back into the database "as the subscriber", which is what supabase/walrus does, but its a serious performance bottleneck, doesn't work for deletes, and is not transactionally consistent.

Unchanged TOAST
TOAST is a postgres internals thing where large values are not stored directly in line with the source tuple. Since values in TOAST are large and inefficient to transmit of the network, part of the WAL spec is to omit TOASTed value is their value has not changed. There is no good solution to retrieve these values without querying back into the database for each row

Triggers
Option 2 is to develop a highly generic rust trigger that can apply security in the same transaction as the insert/update/delete. That would work for TOASTed values, and could send a message to some external process.
The risks with this approach are

Security
Since RLS would be applied within the same transaction as the insert/update/delete, it needs to be hella performant or your transaction throughput will decrease as the number of subscribers increases.

Consistency
If we're operating inside a trigger, we need to release the transaction ASAP. If the external process we're communicating with is temporarily unavailable, the choices are to hold the current transaction until it becomes available again (a bad option), or drop the message and continue (another bad option)

I think a workaround to that issue might be to write messages to a table in the graphql schema and have the external process read from that table. That would always be available (no networking issues) and have ACID guarantees. I also like that option because it keeps everything contained within postgres and feels aligned with pg_graphql philosophically. The potential downside is that its a source of write amplification.

I have a good understanding of the WAL approach, but I'd like to explore the trigger option (specifically around performance) before making a decision.

next up we have
Transport
Neither Postgres or PostgREST have a solution for web sockets or server push so there's no way around having a separate process running to hold persistent connections.
That process could be truly standalone, or it could be a postgres background worker . Background workers sound great in theory but they're fiddly to deploy/debug and require the database to restart to upgrade (no more transactional upgrades).
For supabase to adopt either of those approaches the memory footprint would have to be small enough to comfortably fit on free-tier hardware with a high degree of scalability (at least hundreds of concurrent subscribers).

Lots to explore and think about. We'll get there but it going to take a while to get it right

@olirice May be following articles will give you some insight
https://neon.tech/blog/serverless-driver-for-postgres
https://neon.tech/blog/quicker-serverless-postgres

Is there a sense for if/when this might come?

@pawarren No, it's still on the backburner.

May be interesting: https://www.graphile.org/postgraphile/live-queries/


video_name in database and dumped file for interpolation mode

Hi @BrunoLansacSBD , @nmanovic ,
I have opened a pull request that fixes issue #56.

@edumotya
Hi, thank you for your PR. I have several issues here.
First of all, I see you use new field "video_name", but I don't see any django migrations here. Currently the Task model doesn't consist this field.
Secondly, answering your question, CVAT doesn't support several videos for a single task.
Furthermore, I believe the code should be placed in the function "_save_task_to_db", not "make_image_meta_cache".
Finally, in my opinion, CVAT is unified tool and we should strive to unification. More specific, it would be great to try find some common solution. Not only for a video. Maybe @nmanovic will disagree with me.

@edumotya , We don't need video_name field. Please look at Video and Image models. They contain all necessary information.

https://github.com/opencv/cvat/blob/a5a9b0a0192fc4a75279563b0ba6579f07db3498/cvat/apps/engine/models.py#L128
https://github.com/opencv/cvat/blob/a5a9b0a0192fc4a75279563b0ba6579f07db3498/cvat/apps/engine/models.py#L140

Hi @bsekachev I agree with you, CVAT needs a generic solution. Therefore,

The new field should be named "source" like in annotation mode. Do you agree?
I placed the code in "make_image_meta_cache" to be consistent with the annotation mode analogous code [1]. Anyway, both codes (original annotation mode code [1] and my PR for interpolation mode [2])  are workarounds. As @nmanovic pointed out we don't need video_name field, but we don't need neither to extract the image paths walking the uploads folder [2], they both should be extracted from either Video or Image db models. The issue is that, as far as I know, _save_task_to_db/make_image_meta_cache do not have access neither to the Video nor Image models, only to the Task model, which does not keep the information of the original video path, it only keeps the extracted frame paths. So, how can I access to the Video model object from _save_task_to_db?

[1] make_image_meta_cache for annotation mode: https://github.com/opencv/cvat/blob/bfc9f8e5d81bd1662fea4a0a95ce04e7ec366341/cvat/apps/engine/task.py#L91-L95
[2] This PR make_image_meta_cache for interpolation mode: https://github.com/opencv/cvat/blob/bfc9f8e5d81bd1662fea4a0a95ce04e7ec366341/cvat/apps/engine/task.py#L106-L110
I haven't gone very deep into the code, so I apologise if i'm missing something obvious...
What do you propose?

@edumotya , the main problem here is make_image_meta_cache(db_task) is obsolete. It should be removed. Previously we created a special file which contained information about images/video resolution. Now we have the information inside DB and should take it from DB.
For now inside dump file function you can use db_task.video to get access to Video table and db_task.image_set to get access to Image table. Thus you don't need to create video_name field. You can extract all information which you need from DB. If you can as well remove obsolete functions and use DB instead in appropriate place it will be awesome but it is optional.

@edumotya , let me know what you think. Are you going to adjust your PR request?

I will try it as you suggested @nmanovic

Hi @nmanovic,
Finally I reverted all my previous changes, pulling from develop, and I added a single line into the dump function that extracts the video path from the DB, as suggested. Actually, it was easier.
For now, I am not removing the obsolete functions, maybe later on...

@edumotya , thanks! Could you please check your patch? I still can see db_task.video_name code in your patch. Do you think we can add something similar for images?

Sorry @nmanovic , you were right... I didn't undo my initial changes. It should be fine now, please check it.
Let me see what we can do for images!

Well, docker-compose build for cvat container has failed... I think it has nothing to do with my commit. Anyway, I will check it later on.

@edumotya , Thanks for your contribution! Don't hesitate to submit new PRs to improve the tool.


Supported archive types

If you support zip files you shouldn't have any problems with at least jar and xpi files. Both formats are just zip files themselves....
Just beware: neither of them uses a 'root directory' 😉

Good to know. Thanks for the tip!


fix: clock flicker & color contrast

Hi! @atapas I have fixed three things for Clock Play:

Clock flickering by adding width and font-family
Better background and font color contrast.
Responsive design for the small screen.

Current Clock

New Design

Please review this contribution.
Thanks

@DalpatRathore  plz create an issue and associate to the PR


Add LKG support

Breaking down #45 into smaller chunks.
This PR contains the following changes:

Update the gulp build to support an LKG ("last known good") build of gulp-tsb.
* Update the gulp build to compile an "interim build" of gulp-tsb with the LKG build, and use the "interim build" to compile a "latest build" of gulp-tsb as a simple build verification step.
Use gulp-mocha to run tests in watch mode.
Update the "scripts" section of package.json to use gulp for the test, compile, and prepublish scripts.
Include the lib output directory in git to allow npm installation of an unpublished build.

Minor project structure changes:

lib/ stores the LKG build and is now checked in.
tmp/ stores an "interim build" of gulp-tsb and is excluded from git and npm.
out/ stores a "latest build" of gulp-tsb and is excluded from git and npm.

New gulp tasks:

gulp clean - Cleans the tmp/ and out/ directories.
gulp test - Builds gulp-tsb and runs mocha.
gulp lkg - Copy the "latest build" to lib/ as the new "last known good" build.

@jrieken, can you take a look?

// cc: @joaomoreno

Thanks. lgtm. merging


Nesting ListViews in ScrollView

Hi
I'm trying to nest multiple ListViews in a ScrollView and I want to trigger the onEndReached Event of each ListView. I know that the ScrollView's Scroll is taken in this particular example but is there a way to manage this?
I thought about using a View instead a ScrollView for a Container but my Content is bigger than the Screen and I don't know the height of my Content.
Is there a way to either make a View as height as the Content or to Decide witch scroll should be taken?
Something like this:

     -> Scroll To End

(I hope you understood my problem :smile: )

Not sure but maybe you can set a separate reference on each one of the listView components?

hi thank you for your response
I made another workaround. I have set the height of each ListView to the full height of the device. Then when the end is reached I load the next ListView.
I close this issue until I run in the same problem again.


Prices for needed baked players

Can you extract transfer market info through CHPP? Like current prices for certain skill sets etc?

Indications on prices of your baked players you need to purchase, your profit trainees and salaries could deliver the total package!

At least help out with searching for the baked players you need on the transfer.

Moved to vision: https://github.com/kvarak/htstatus/wiki


Make default pagination item count and maximum item count customizable from admin ui

Hello,
With this pr, the maximum number of records that API can return and the number of default records will be editable via the admin panel.

This was requested before, but for now is left aside as the default 500 limit should be enough for most cases (if you want to get all items at once, the SDKs comes with getFullList() method that will perform sequential batch requests and will return a final array with all collection records).
Eventually sometime in the future we may introduce similar configurable limits options per collection level (could be even combined eventually with https://github.com/pocketbase/pocketbase/issues/1232).
I appreciate the effort, but please don't file PRs for new features without previously discussing the implementation details in an issue or a Q&A discussion, to avoid spending too much time in something that may not get merged. I try to follow a specific plan/roadmap and such PRs come out of nowhere, skew the initial planning and always require some tedious back-and-forth.

I couldn't find anything about pagination settings in roadmap, but I wanted to open pr because of this comment.
I made such an improvement because pulling 20k or more data with the getFullList is wasted time :/
Thanks for your time.

20k or more data with the getFullList is wasted time

I'm not sure what is your use case, but please note that you could easily exhaust your server resources when fetching so many items at once and most of the time it would be better to batch or paginate the requests.

You are absolutely right, it is necessary to paginate when pulling 20k data, but I think I should have higher standards for this much data, instead of making requests that I can get 500 records all the time. Right now I can handle this in 4 or 5 requests instead of making 40 requests. I think it's possible to speed up a lot with less requests with sacrificing some resources. All I want to say is that you should leave that desicion to the user. Pocketbase is already sufficient for most scenarios. If I want to fetch 100k record in a request, its my problem, not pocketbase.


rosdep cannot locate rosdep definition for "pacmod3_msgs"

Checklist

[X] I've read the contribution guidelines.
[X] I've searched other issues and no duplicate issues were found.
[X] I'm convinced that this is not my fault but a bug.

Description
When installing the dependent ROS packages for Autoware based on the installation guide, the command rosdep install -y --from-paths src --ignore-src --rosdistro $ROS_DISTRO errors out complaining that it cannot find the package pacmod3_msgs. Here is the full log:
ERROR: the following packages/stacks could not have their rosdep keys resolved
to system dependencies:
pacmod_interface: Cannot locate rosdep definition for [pacmod3_msgs]

Expected behavior
rosdep must start downloading the ROS and system dependencies without errors.
Actual behavior
But it doesn't!
Steps to reproduce
Perform a clean and fresh installation of Autoware based on the mentioned installation guide.
Versions
OS: Ubuntu 22.04
ROS: ROS2 Humble
Possible causes
It can be an outdated autoware.repos file. Probably adding the package index for pacmod3_msgs to the repos file would fix the issue. I actually got it from the pacmod_interface build_depends.repos file.
Additional context
I've checked the term about duplicate issues, but actually, there is a duplicate issue and it's here. I wonder why the bug still exists.

If you follow the source installation guide, on the list, you should see

Install pacmod

item on the list if you don't follow the ansible route.
The steps there will help the rosdep find the message you need.

I actually took the ansible route and it went well without any errors. After that rosdep failed.

Interesting, at least in the Autoware dockerfile generation, it seems to be installing fine:

https://github.com/autowarefoundation/autoware/actions/runs/7004746973/job/19053135870#step:4:1254

Could you manually run these steps and tell if it works?


Leaderboard / benchmark ?

It would be nice to also have some kind of leaderboard associated to each of the listed datasets.
One (bad) way of doing it would be to use numbers reported in papers. It is bad for several reasons:

one cannot be sure the exact same evaluation protocol was used
one cannot be sure the exact same metric was used

A better way of doing it would be to ask authors to provide their output files and run the evaluation for them (possibly automatically on each pull request) but this does not solve the first problem. We could use pyannote.metrics for that.
An even better way would be to ask them to provide runnable pre-trained systems and run them for them but this would need a lot of work to ask from the authors and to setup.
An utopian way would to ask them to provide trainable systems.
Anyway, maybe it is too much to ask and existing challenges like DIHARD and Albayzin are probably enough...

Recently I want to get some related information about the performance of the diarization.But I can not  access the leaderboard now.

It seems the website https://www.stateoftheart.ai/ is down. There's nothing we can do about it, unfortunately.

ohh,that's terrible. Thanks for your reply.


Update docs for tree item label type config

What does this PR do?
This PR adds documents for the new workspace.views.treeViews namespace and the config key treeItemLabelType
What issues does this PR fix or reference?

Relates to: dendronhq/dendron#2858

Merge requirements satisfied

For more information, visit the Contributing Guide for Documentation

[ ] Check rendered output to ensure formatting is correct for renderings of wikilinks, note refs, tables, and images. Dendron: Show Preview can be used in your workspace to confirm the page renders as expected. Sometimes, Dendron: Reload Index needs to be ran if certain wikilinks aren't working as expected. (ignore this if contribution is made via the Edit this page on GitHub button from the published site)
[ ] If this PR includes any refactoring (renaming notes, renaming headers, etc.), make sure that these changes were done via Dendron Refactoring Commands. This will ensure that any other impacted areas of the documentation, that link to or embed modified notes (via note references), are automatically updated.

Verify GitHub Actions tests are passing, which can be seen in the Checks tab of the PR:

[ ] URL validator GitHub Action passes
[ ] Dendron site build GitHub Action passes

NOTE: If you are a new contributor, a maintainer will need to provide approval for GitHub Actions to run on your PRs.

closing this since we decided to persist UI state through metadata


Data dir permissions issue in Minikube

Hello,
I'm following this tutorial on a local minikube cluster and Consul fails with this error:
$ kubectl logs -f consul-0
==> CRITICAL: Permission denied for data folder at "/var/lib/consul/mdb"!
==> Consul will refuse to boot without access to this directory.
==> Please correct permissions and try starting again.

I was able to get around it by using /consul/data as the mountPath.  The Consul image entrypoint sets the right permissions for this path when launching Consul.
I'm not sure if this error is specific to Minikube, but I imagine volume mounts in general would be owned by root and would have the same issue.  I guess the issue here is that Consul runs as a non-root user, which is unconventional for Docker images.

Hi,
I am also running this tutorial with a local minikube cluster and even after changing the mountPath to /consul/data, it seem to be not working. Performing a kubectl get pods and getting the logs resulted in what you see below.

@naiduarvind  It looks like Consul is still trying to use /var/lib/consul.  When I made this change, I also removed the arg -data-dir=/var/lib/consul from the StatefulSet.  See if that works for you.

@pbitty 's solution works, but it doesn't change /var/lib from being the recommended unix folder for storing DB state. This is probably a bug in minikube?

I was having the same issue with the v0.9.0 Consul container. I updated the paths used in my pull request to update to v0.9.0, #15, which resolved the issue.


How to Encode Numerical Sparse features?

Question on encoding numerical sparse features:
How do we encode sparse features with non binary values? Say we have frequency/strength values in X for the sparse features (normalized between 0 and 1)? All my sparse features are already stored in separate columns. (col2 : col11133)
Currently I do this:
sparse_features = ['col' + str(i) for i in range(2, n)]
dense_features = []
testing_dataframe[sparse_features] = testing_dataframe[sparse_features].fillna(0, )
testing_dataframe[dense_features] = testing_dataframe[dense_features].fillna(0, )

sparse_feature_list = [SingleFeat(feat, 0) for feat in sparse_features]
dense_feature_list = [SingleFeat(feat, 0) for feat in dense_features]

test_model_input = [df_test[feat.name].values for feat in sparse_feature_list] + \
                   [df_test[feat.name].values for feat in dense_feature_list]

This makes my network take much longer to initialize. I am using embedding of 50, with ~11K features.
I see the examples shown are more so categorical.
Any assistance would be greatly appreciated!

python version 3.6
tensorflow version 1.12.0
deepctr version latest

hi,please treat the  numerical sparse features as  dense features~

Thanks for your quick response. So basically we cannot reduce dimensionality for sparse numerical, right?
Reason I am asking is that my data is in FFM format (field:feature:value). The closest thing to this would be to just use categorical, correct?
Thanks
Leo

So, can model support coo or csr matrix type?

@leoanghelescu  for the format of (field:feature:value),

#feature=1,#value >= 1,treat it as dense feature
#feature>1,#value = 1,treat it as sparse feature
#feature >1,#value > 1, now deepctr not support

@XunGong99  there is no need to use sparse matrix type in deepctr


[Bug] Editor form label is not displayed on UI

Description

Label 'Content' is not displayed with the following editor.json file configuration used for s3 plugin query editor:

 {
  "editor": [
    {
      "sectionName": "",
      "id": 1,
      "children": [
        {
          "label": "Action",
          "configProperty": "actionConfiguration.pluginSpecifiedTemplates[0].value",
          "controlType": "DROP_DOWN",
          "isRequired": true,
          "initialValue": "LIST",
          "options": [
            {
              "label": "List all files in bucket",
              "value": "LIST"
            },
            {
              "label": "Create a new file",
              "value": "UPLOAD_FILE_FROM_BODY"
            },
            {
              "label": "Read file",
              "value": "READ_FILE"
            },
            {
              "label": "Delete file",
              "value": "DELETE_FILE"
            }
          ]
        },
        {
          "label": "Bucket Name",
          "configProperty": "actionConfiguration.pluginSpecifiedTemplates[1].value",
          "controlType": "INPUT_TEXT",
          "isRequired": true,
          "initialValue": ""
        },
        {
          "label": "File Path",
          "configProperty": "actionConfiguration.path",
          "controlType": "INPUT_TEXT",
          "initialValue": ""
        },
        {
          "label": "Content",
          "configProperty": "actionConfiguration.body",
          "controlType": "QUERY_DYNAMIC_TEXT",
          "initialValue": ""
        }
      ]
    }
  ]
}

Steps to reproduce the behaviour:

Copy the above configuration in an editor.json file for any plugin.
Run appsmith server.
Create new query.
Check that label is missing in the query editor form.

Important Details

Version: Cloud
OS: MacOS
Browser: Chrome

Instead of 2 separate fields for QUERY_DYNAMIC_TEXT and INPUT_TEXT, can we have a single field that simply expands as it does everywhere else in the application?

@Nikhil-Nandagopal the problem is figuring out which context the code is running under.
Dynamic text needs to know which entity it is associated with. I had to do the same for #2983
I guess we can use state to populate or pass on this information, but that will be larger refactor for some day.

@ofpiyush @hetunandu sounds like a code design problem. I don't see why the component should be aware of that since it's only doing auto-complete. If it's for validation then that can be optionally passed to the component


[Synapse] Add pipeline, linked service, trigger, notebook, data flow and dataset related cmdlets

Description

Add some new commands to manage pipeline, linked service, trigger, notebook, data flow and dataset in synapse workspace.

az synapse linked-service  create/set/list/show/delete
az synapse dataset   create/set/list/show/delete
az synapse pipeline create/set/list/show/delete/create-run
az synapse pipeline-run show/cancel/query-by-workspace
az synapse activity-run query-by-pipeline-run
az synapse trigger create/set/list/show/delete/subscribe-to-event/get-event-subscription-status/unsubscribe-from-event/start/stop
az synapse trigger-run query-by-workspace/rerun
az synapse data-flow create/set/list/show/delete
az synapse notebook create/set/list/show/delete/import/export

Testing Guide

az synapse linked-service -h
az synapse dataset -h
az synapse pipeline -h
az synapse pipeline-run -h
az synapse activity-run -h
az synapse trigger -h
az synapse trigger-run -h
az synapse data-flow -h
az synapse notebook -h
History Notes

This checklist is used to make sure that common guidelines for a pull request are followed.

[ ] The PR title and description has followed the guideline in Submitting Pull Requests.

[ ] I adhere to the Command Guidelines.

Synapse

@haroldrandom could you please help merge the PR?

@wonner, I added some comments, please take a look.


Date/time random inside container

This is the output of "date" from inside the container:
bash-5.1# date
Thu May  7 03:56:00 CEST 2037
bash-5.1# date
Sun Jun 14 22:38:08 CEST 2037
bash-5.1# date
Sat May 30 06:01:52 CEST 2037
bash-5.1# date
Mon Jun 15 08:52:32 CEST 2037
bash-5.1# date
Sat Apr 18 16:12:00 CEST 2037
bash-5.1# date
Thu Apr 23 13:23:28 CEST 2037
bash-5.1# ^C
bash-5.1#

My cron settings are seemingly ignored, that is why I checked the date/times.
Files uploaded with rclone also receive the time stamp reflecting these weird date/times. Zipping (when enabled) and the subsequent zip check also fail, but I do not know if that is related.

Hey @Boergen ,please check #34 .


Project: Intranet Search Bot

Project name
Intranet Search Bot
Description
Intranet Search Bot is chat bot for searching SharePoint for files, events, list items and messages. So users do not have to leave Microsoft Teams, they can leverage SharePoint within teams by a using a Teams Chat bot that leverage MS Graph.
Potential improvement will be implemented is to summarize the search results by using Azure Open AI Service.
Project Repository URL
https://github.com/mohammadamer/HackTogether/tree/main/IntranetSearchBot
Project video
https://github.com/mohammadamer/HackTogether
Team members
@mohammadamer

Thanks for your project submission @mohammadamer, we are so excited check out the details! Meanwhile, would you be willing to fill out the hackathon survey? That'd help us learn from your experience and improve it next time: https://aka.ms/hack-together-teams/survey


feat: Estimator typeclass and implementation for Levenshtein distance

[x] depends on: #6096
[x] depends on: #6097
[x] depends on: #6115
[x] depends on: #6117
[x] depends on: #6118

bors merge


Remove color wheel

I think it would be better visually to just show the coverage (9113, 9116, or total, depending on tab) as opposed to having the color wheel showing range of acres for the segment.

Opting to leave this in, I think showing the color range is appropriate because it provides an overview of the whole range across all year comparisons.


Tag version v2.0.0-dev not referencing in packagist (reopen)

Hi, in packagist.org on this page https://packagist.org/packages/mailjet/mailjet-apiv3-php-simple
you lib v2.0.0-dev is not referenced.

Hi @flug !
We are currently working on a cleaner and much more maintainable version of the PHP wrapper in another repository, that is planned to be released soon. This v2.0.0-dev tag is not going to be maintained
Best,
Guillaume from Mailjet


Implement federation fields and types using strawberry

Add tests for federation schema
Implement federation fields and types using strawberry

Closes #3521 #3522

Thanks for adding the RELEASE.md file!

Here's a preview of the changelog:

This release refactors our Federation integration to create types using
Strawberry directly, instead of using low level types from GraphQL-core.
The only user facing change is that now the info object passed to the
resolve_reference function is the strawberry.Info object instead of the one
coming coming from GraphQL-core. This is a breaking change for users that
were using the info object directly.
If you need to access the original info object you can do so by accessing the
_raw_info attribute.
import strawberry

@strawberry.federation.type(keys=["upc"])
class Product:
    upc: str

    @classmethod
    def resolve_reference(cls, info: strawberry.Info, upc: str) -> "Product":
        # Access the original info object
        original_info = info._raw_info

        return Product(upc=upc)

Here's the tweet text:
🆕 Release (next) is out! Thanks to @patrick91 for the PR 👏

Get it here 👉 https://strawberry.rocks/release/(next)


Allow sending JsonRpcRequests through wallet api

Purpose
Expose JSON-RPC methods through wallet-api.
Changes

Add a JSON-RPC client to the wallet-api.
Updated piggybank to use wallet's JSON request.

Checklist

[x] My code follows the style of this project.
[x] The code compiles without warnings.
[x] I have performed a self-review of the changes.
[x] I have documented my code, in particular the intent of the
hard-to-understand areas.
[ ] (If necessary) I have updated the CHANGELOG.

If I don't have any account connected and I try to get the JSON-RPC client, then a connection request in the wallet is opened.

The returned errors from the client should be better. I just get that the RPC call was rejected by the wallet, but my request was in fact just bad.