Discussion: How to make the projects portal customizeable

As mentioned on the the ISC Community Call InnerSource and Discoverability, one of our ideas for the portal is to make it customizeable.
What is the problem?
Currently, the way to reuse the portal is to fork it and modify it, it is not reusable in the sense of being a customizeable dependency that can be reused without modifications.
One of the cons of this approach is that it is harder to keep it up to integrate updates, as there may be conflicts between the changes on the original repo and the forks.
Here are some of the features that could be customizeable:

favicon
logo
style and colors
link to contribute (see #25)

What is this issue about
I created this issue to collect ideas on how we could make the portal customizeable.
Features we should keep
One of the great features of the portal today is that it can be easily hosted as static files. This make it easy to operate, as it can be hosted for instance on GitHub pages. When making customizeable, we should aim to keep it for simplicity.

This is an interesting angle to make it easier to reuse the project and contribute to it.
Some other ideas where customizability could be helpful:

link to "add new project" (orange ➕  sign at the bottom right) - Links to https://yourcompany.corp/innersource-instructions by default right now.
default sort order for the projects in the portal (I think right now the default is "Activity", even though the activity score is a custom
contact information for the company-internal maintainer of the portal - e.g. if somebody is browsing the portal and something doesn't look right, who should they contact?
an predefined approach to add custom pages to the portal (e.g. a menu from where one could link to other resources that a given company considers relevant in relation to their InnerSource Portal)

@spier https://github.com/SAP/project-portal-for-innersource/issues/26#issuecomment-877785826 all good considerations.

I'm thinking about how I'd like the experience to be from a developer's perspective reusing the portal.
I am picturing something like this:

I initialize an npm package for my own portal:npm init

I install the "portal reusable" as a dependencynpm install --save @sap/project-portal-for-innersource

depending on how we do it, could be --save-dev
I start it withnpm start

or build it for deployment with (it would output something deployable to the dist folder)npm run build

I configure the portal, maybe by adding a section to package.json, or creating a folder on the root of the project, like portal-config.json

A suggestion for the portability:
Rename repos.json to repos.sample.json and add repos.json to .gitignore, update the README.md with the extra step of cp repos.sample.json repos.json
That way if the sample data gets updated I don't get merge conflicts when I pull from upstream.

👋 One thing I've done to customize the portal for a few companies is to insert any "Overview metrics" right at the top just above the search bar and filters. This is done through a nightly automation to keep the stats fresh.
Example:

"424 InnerSource repositories, 10% of all repositories, 21hr average time to first response on Pull requests, Average security score: 90"

Hi @svrnm, this is an interesting suggestion. I'll discuss it with @Michadelic.
@zkoppert , that's an interesting customization, thanks for sharing!

thanks @dellagustin

Amazing list of suggestions to customize the portal. I will have a look and i am also very open for public contributions on this issue. Maybe we can jointly create a concept and work on it.
My two cents for getting it implemented:

have a config.json file as @dellagustin-sap suggested in the root directory and adjust the portal so that it reads the config file instead of hard-coded values in the portal. Then the config file can be updated at any time to adjust the beahvior and content of the portal
have a templating wizard connected to the npm init command to fill the config.json file interactively by asking with the comments defined in the config.json file. This would need a json format that supports comments or a separate file for the wizard. The wizard can also be used to update existing values at any time and readjust the portal behavior.

We could start with the config.json file and the list of suggestions in this thread and later add the wizard.
What do you thing?
PS: the overview metrics is also an interesting idea. This would probably done in the crawler at the end and update an entry in the config.json file?

Having a configuration to fill out the page details is a great idea! It also helps to find all the things that need to be changed since on the HTML page they are at very different places 👍
A few other suggestions:

a thing I just learned while trying the portal out, is that npm is currently only used for pulling in some dependencies via the postinstall and then it uses http-server, so it is possible to run the portal without npm and with my "preferred" (or available) webserver, for example I can just do php -S localhost:8080 and it works, or I can put it into a nginx container, or I can use GitHub Pages (see below)! It would be great to have those alternatives documented.

Additionally, it would be great if the HTML + assets (styles, JS, JSON files) would live in their own directory, because then when hosted not all other files of the repository are exposed via the HTTP server.

making peoples' live extra easy the name of the folder could be docs/, because this is the only other path GH allows besides /:

Here is a prototype how this could look like: https://svrnm.github.io/project-portal-for-innersource/#display=card

Finally, while looking into this option I was wondering if it wouldn't be an option to leverage jekyll or hugo instead of npm for building and configuration?


Revert "logo add."

Reverts LandiMi2/BHKi-Training-Activities#5
@karegapauline can the logo be on the side? Doesn't look okay on top.

@LandiMi2 sorry about this. I thought it would fit on the right. let me also upload the SVG instead


Let successful revision finish when in block window

@bratseth please review.
A recent change, to allow revision to complete roll-out, was flawed, because new revisions would be accepted as the new target, stopping the previous revision.
By storing new revisions as outstanding changes when we are in a revision block window and are stil rolling out a previous revision and are not failing (in which case it makes sense to immediately allow new revisions, for testing in system and staging tests), this problem is alleviated.

@kkraune FYI.


MGDSTRM-10985 accounting for the possibility of competing operators

With later josdk we'll likely enable leader election.

Can we use io.javaoperatorsdk.operator.api.config.LeaderElectionConfiguration even with the current platform?

Can we use io.javaoperatorsdk.operator.api.config.LeaderElectionConfiguration even with the current platform?

There have been a lot of fixes / improvements in the leader election logic since 5.12.4, I'm honestly not sure if a 5.x version is appropriate for general use - I was just going to wait until we were on a later version.

Ok, got it. I didn't realize it might not be ready.


Send sdk version in X-Kii-SDK header.

Added codes are Similar to KiiCloud SDKs.

Http Header output of SDK info: X-Kii-SDK (For internal access log analytics.)
ThingIFAPI#getSDKVersion() method is added. (Public method)

please fix failed tests

Fixed small test and confirmed large test result as well.

LGTM


Rz extract dedup - hardcode lonlat spacing

Hard coded lon lat pixel resolution values to 0.000833334 degrees. This was done in a single place: lines 487-488 in the extractProduct.py module, mergedproductbbox function. To the best of my understanding, the parameters coded here should propagate throughout the ariaTSsetup.py bin file, in which mergedproductbbox returns the pixels resolution, and that returned value is passed to calls to the export_products function.
This change is made as part of a larger ARIA-tools forward processing deduplication effort.

@rzinke with the on-demand capability we might actually have set variations in resolution for the products.
We will want to be able to support costom on-demand, our disaster pipeline might have different resolutions too.
I think if we can pass it through and be strategic on the where it finds this information then we keep future flexibility.


Create Christmas_tree_pattern.cpp

Great work, but I suggest you work on implementing some algorithm or data structure.👍


[CELEBORN-1366] Bump guava from 32.1.3-jre to 33.1.0-jre

What changes were proposed in this pull request?
Bump guava from 32.1.3-jre to 33.1.0-jre.
Why are the changes needed?
Guava v33.1.0 has been released, which release note refers to v33.1.0. v33.1.0 brings some bug fixes and optimizations as follows:

cache: Fixed a bug that could cause https://github.com/google/guava/pull/6851#issuecomment-1931276822.

Does this PR introduce any user-facing change?
No.
How was this patch tested?
No.

cc @FMX, @pan3793, @cfmcgrady.

cc @FMX, @pan3793, @cfmcgrady.


feat(Catalog Management): re-gen service after recent API changes

PR summary
Re-generating Go SDK after API updates
PR Checklist
Please make sure that your PR fulfills the following requirements:

[x] The commit message follows the Angular Commit Message Guidelines.
[x] Tests for the changes have been added (for bug fixes / features)
[ ] Docs have been added / updated (for bug fixes / features)

Current vs new behavior
New features associated with API updates
Does this PR introduce a breaking change?

[ ] Yes
[x] No

Other information

Examples tests:
Ran 599 of 627 Specs in 37.819 seconds
SUCCESS! -- 599 Passed | 0 Failed | 0 Pending | 28 Skipped
PASS
ok  	github.com/IBM/platform-services-go-sdk/catalogmanagementv1	38.914s

Integration tests:
Ran 610 of 666 Specs in 38.160 seconds
SUCCESS! -- 610 Passed | 0 Failed | 0 Pending | 56 Skipped
PASS
ok  	github.com/IBM/platform-services-go-sdk/catalogmanagementv1	38.933s

:tada: This PR is included in version 0.57.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Dispatch actions when extentproperty handles a change to fix bug

Description of the problem this pull request fixes
This fixes an issue introduced earlier where the ExtentProperty UI is broken.
Changes proposed in this pull request:

Use disable/enableProperty actions to toggle disabled state on rect extent properties

@arvind I could use your testing to see whether what's happening is what we expect, esp. when you bind data!

A bug, which I have recreated 3 times now, but unpredictably.

Add a rect.
mess around with the spacial properties.
Add data to each axis
mess around with the spacial properties.
Add another mark.
Delete that mark.
Try to click on the rect in the sidebar.

This is what the properties look like when I get the bug:

You'll know things are broken because the graph looks weird.
@arvind have you ever seen this in vega?

+1 code.  I did functional testing and other than a really hard to recreate bug that I don't think is a blocker, I am +1 functional.
Waiting on Arvind to +1 functional too since he knows what the behavior should look like.

This is functional close for me. Couple of bugs I'm noticing:

After adding a rect mark, if I switch any of the spatial properties (e.g., "right" --> "width") the two corresponding textboxes are empty (even though an actual value is being used to render the visualization). If I enter values into the textboxes, the visualization updates correctly.

The SpatialPreset component for width/height isn't being rendered anymore? Just as we see a checkbox for "Group width" and "Group height" when using left/right or top/bottom respectively, we should see a checkbox saying "Automatic" when width/height are selected.

Jk on (2) above. The "Automatic" only shows up when width/height is bound to a scale. However, (1) continues to be a problem. We also have a regression from the current lyra2 branch. Say we bind a field to a rect's horizontal channel. In lyra, the inspector updates correctly to show that Left and Width have been set. In this branch, however, Left shows as set but Right is still selected (if we manually switch Right to Width, we see the correct scale/field binding appear, but this should happen automatically).

Fixed with f593ab8.


Bug: Passing maximum parameters of 2100 to SqlCommand object is failing to execute

Describe the bug
I created a DELETE statement using IN keyword that accepts 2099 parameters and the exception is being thrown. Thinking that the limits are not working as it should.

If you are seeing an exception, include the full exceptions details (message and stack trace).
Exception message: Microsoft.Data.SqlClient.SqlException: 'The incoming request has too many parameters. The server supports a maximum of 2100 parameters. Reduce the number of parameters and resend the request.'
Stack trace: Microsoft.Data.SqlClient.SqlException
  HResult=0x80131904
  Message=The incoming request has too many parameters. The server supports a maximum of 2100 parameters. Reduce the number of parameters and resend the request.
  Source=Core Microsoft SqlClient Data Provider
  StackTrace:
   at Microsoft.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction)
   at Microsoft.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction)
   at Microsoft.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj, Boolean callerHasConnectionLock, Boolean asyncClose)
   at Microsoft.Data.SqlClient.TdsParser.TryRun(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj, Boolean& dataReady)
   at Microsoft.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString, Boolean isInternal, Boolean forDescribeParameterEncryption, Boolean shouldCacheForAlwaysEncrypted)
   at Microsoft.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean isAsync, Int32 timeout, Task& task, Boolean asyncWrite, Boolean inRetry, SqlDataReader ds, Boolean describeParameterEncryptionRequest)
   at Microsoft.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, TaskCompletionSource`1 completion, Int32 timeout, Task& task, Boolean& usedCache, Boolean asyncWrite, Boolean inRetry, String method)
   at Microsoft.Data.SqlClient.SqlCommand.InternalExecuteNonQuery(TaskCompletionSource`1 completion, Boolean sendToPipe, Int32 timeout, Boolean& usedCache, Boolean asyncWrite, Boolean inRetry, String methodName)
   at Microsoft.Data.SqlClient.SqlCommand.ExecuteNonQuery()
   at RepoDb.DbConnectionExtension.ExecuteNonQueryInternal(IDbConnection connection, String commandText, Object param, Nullable`1 commandType, Nullable`1 commandTimeout, IDbTransaction transaction, Boolean skipCommandArrayParametersCheck) in C:\Users\MichaelP\Source\Repos\GitHub\RepoDb\RepoDb.Core\RepoDb\Extensions\DbConnectionExtension.cs:line 727
   at RepoDb.DbConnectionExtension.DeleteInternalBase(IDbConnection connection, DeleteRequest request, Object param, Nullable`1 commandTimeout, IDbTransaction transaction, ITrace trace) in C:\Users\MichaelP\Source\Repos\GitHub\RepoDb\RepoDb.Core\RepoDb\Operations\DbConnection\Delete.cs:line 870
   at RepoDb.DbConnectionExtension.DeleteInternal[TEntity](IDbConnection connection, QueryGroup where, String hints, Nullable`1 commandTimeout, IDbTransaction transaction, ITrace trace, IStatementBuilder statementBuilder) in C:\Users\MichaelP\Source\Repos\GitHub\RepoDb\RepoDb.Core\RepoDb\Operations\DbConnection\Delete.cs:line 239
   at RepoDb.DbConnectionExtension.DeleteAll[TEntity](IDbConnection connection, IEnumerable`1 primaryKeys, String hints, Nullable`1 commandTimeout, IDbTransaction transaction, ITrace trace, IStatementBuilder statementBuilder) in C:\Users\MichaelP\Source\Repos\GitHub\RepoDb\RepoDb.Core\RepoDb\Operations\DbConnection\DeleteAll.cs:line 98
   at RepoDb.SqlServer.IntegrationTests.Operations.DeleteAllTest.TestSqlServerConnectionDeleteAllViaPrimaryKeysBeyondLimits() in C:\Users\MichaelP\Source\Repos\GitHub\RepoDb\RepoDb.SqlServer\RepoDb.SqlServer.IntegrationTests\Operations\DeleteAllTest.cs:line 72

  This exception was originally thrown at this call stack:
    [External Code]
    RepoDb.DbConnectionExtension.ExecuteNonQueryInternal(System.Data.IDbConnection, string, object, System.Data.CommandType?, int?, System.Data.IDbTransaction, bool) in DbConnectionExtension.cs
    RepoDb.DbConnectionExtension.DeleteInternalBase(System.Data.IDbConnection, RepoDb.Requests.DeleteRequest, object, int?, System.Data.IDbTransaction, RepoDb.Interfaces.ITrace) in Delete.cs
    RepoDb.DbConnectionExtension.DeleteInternal<TEntity>(System.Data.IDbConnection, RepoDb.QueryGroup, string, int?, System.Data.IDbTransaction, RepoDb.Interfaces.ITrace, RepoDb.Interfaces.IStatementBuilder) in Delete.cs
    RepoDb.DbConnectionExtension.DeleteAll<TEntity>(System.Data.IDbConnection, System.Collections.Generic.IEnumerable<object>, string, int?, System.Data.IDbTransaction, RepoDb.Interfaces.ITrace, RepoDb.Interfaces.IStatementBuilder) in DeleteAll.cs
    RepoDb.SqlServer.IntegrationTests.Operations.DeleteAllTest.TestSqlServerConnectionDeleteAllViaPrimaryKeysBeyondLimits() in DeleteAllTest.cs

Expected behavior
I would expect that exception must not be thrown and the 2100 parameters will be passed accordingly in the actual execution.
Further technical details
Microsoft.Data.SqlClient: v1.1.1
.NET target: NetStandard 2.0
SQL Server: Microsoft SQL Server Developer (64-bit) - Microsoft SQL Server 2014 (SP1-GDR) (KB4019091) - 12.0.4237.0 (X64)   Jul  5 2017 22:03:42   Copyright (c) Microsoft Corporation  Developer Edition (64-bit) on Windows NT 6.3  (Build 18363: ) (Hypervisor)
Operating System: Windows 10

You are actually sending 2099 + 2 parameters. So from an app point of view the max is 2098!

I notice that @ErikEJ - it is passing if I put it 2098. Apology, but I missed the 2 parameters. Can you elaborate?

SqlClient uses sp_executesql, which uses 2 parameters, afaik.

Seems to be an already discussed and known behavior. Thanks @ErikEJ . I will close this one now.


Add acceleration structure overrides

Add code-overrides for vulkan's acceleration-structure API
Extend address-tracking to cover acceleration-structures
Start with device-address replacement for binding-tables and acceleration-structure buffers
Addition to capture device-address state-tracking
Add tracking for physical-device raytracing-properties
Leave TODOs

belongs to portable raytracing initiative

CI gfxreconstruct build queued with queue ID 263907.

CI gfxreconstruct build # 4895 running.

CI gfxreconstruct build # 4895 passed.

CI gfxreconstruct build queued with queue ID 263941.

CI gfxreconstruct build # 4896 running.

CI gfxreconstruct build # 4896 passed.

CI gfxreconstruct build queued with queue ID 265244.

CI gfxreconstruct build # 4906 running.

CI gfxreconstruct build # 4906 failed.

CI gfxreconstruct build queued with queue ID 267593.

CI gfxreconstruct build # 4925 running.

CI gfxreconstruct build # 4925 passed.

CI gfxreconstruct build queued with queue ID 267636.

CI gfxreconstruct build queued with queue ID 267654.

CI gfxreconstruct build # 4929 running.

CI gfxreconstruct build # 4929 passed.

CI gfxreconstruct build queued with queue ID 268581.

CI gfxreconstruct build # 4936 running.

CI gfxreconstruct build # 4936 passed.

CI gfxreconstruct build queued with queue ID 268639.

CI gfxreconstruct build # 4937 running.

CI gfxreconstruct build # 4937 passed.


/Move Note: add a new folder

Awhile back, I added the ability to (optionally) allow the user to create a new folder in the chooseFolder dialog.
function chooseFolder(msg: string, includeArchive: boolean, includeNewFolderOption: boolean, startFolder: string): string

Will you please use this option in the /move note command?
Just set the 3rd param to true.
While you're at it, you may want to do a quick scan of other places you use chooseFolder to see if there are other places you may want to add it (maybe in Filer/newNote?).

It's now updated, and will soon be released in v0.17.


On slide click issue

When user swiping slick carousel there is trigerring click event. It means that if items in carousel will be clickable there will be a problem. I think it would be better to add onSlideClick porperty which will be triggered only if it will be successful click on slide, and if it will be swipe than click event will be ignored

Duplicate with #1952


Prepare FloatingPanel 2

Feature updates

Support top, left and right positions of the panel
Add ObjC compatibility
Improve the layout customization
Improve the behavior customization to handle it like UIScrollView
Improve the remove interaction
Fix many issues depending on API design

API updates

FloatingPanelController

Replace surfaceOriginY with surfaceLocation.
Enable to update layout and behavior directly.
Update scroll tracking API a bit to support multiple scroll view tracking in the future.

FloatingPanelControllerDelegate

Change floatingPanelDidMove behavior which is also called in the spring animation.
Update removal interaction delegate

Enable a panel to invoke the removal action at any state(position)
Add
floatingPanel(_:shouldRemoveAt:with:) to determine whether it invokes the removal interaction.

Add floatingPanelDidEndDragging(_ vc:willAttract:)

Layout

Introduce LayoutAnchor for the more flexible layout.

Add a factional panel position in the FloatingPanelController view
Replace FloatingPanelFullScreenLayout and FloatingPanelIntrinsicLayout

Behavior

Introduce the new spring effect using Numeric springing
Add properties to contorl numeric springing
Remove .topInteractionBuffer/.bottomInteractionBuffer

You can control the panel max/min position in floatingPanel(_:didMove:) delegate method

SurfaceView

UseSurfaceAppearnace to specify the rounding corners, shadow and background color.

BackdropView

Disable the dismissal action of backdrop by default

You can enable it to set fpc.backdropView.dismissalTapGestureRecognizer.isEnabled = true

FloatingPanelPanGestureRecognizer

Add delegateProxy to intercept the gesture recognizer delegate.

Improve API naming

FloatingPanelPosition -> FloatingPanelState: Now FloatingPanelPosition is used to specify the panel positioning in a screen.
FloatingPanelGrabberHandleView -> GrabberView: Swift only
FloatingPanelSurfaceView  -> SurfaceView: Swift only
FloatingPanelBackdropView -> BackdropView: Swift only
Decelerating -> Attracting: Because the spring behavior is actually magnetic.

Misc

Add UISpringTimingParameters(decelerationRate:frequencyResponse:initialVelocity:)

Environment updates

Swift 5.0 or later
iOS 11 or later(iOS 10 might be working)
Update the directory structure and file names

TODO

[ ] Write Migration Guide to v2
[x] Enhance the doc comments

Incredible. Can't wait for this!

This is awesome work! Thank you @SCENEE 🙏

Thank you so much, @zntfdr! I revised the migration guide following your reviews.

You're very welcome @SCENEE, can't wait to try this out 😃

Today I released version 2.0.0. Thank you so much, @zntfdr and everyone.

Bravo @SCENEE, @zntfdr, and everyone else! 👏


Rounded Rectangle swf asset renders incorrectly

This rounded rectangle asset started rendering incorrectly at certain scale values with the commit mentioned below (between 9.2.0 and 9.2.1)
Steps to reproduce the behavior:

Run sample program
You will see issue as shown in screen shot

Run sample app with the display.rotation = 0.001; line uncommented to see how it looks (and our current workaround)

Issue started in this commit: https://github.com/openfl/openfl/commit/bb8a97d717c819769d21d8019b4f6fe355cdbe34
html5 target.
Additional context
Demo project
RRectDemo.zip

Can you add a screenshot that shows how it's supposed to look too? Thanks!

Modify sample code as follows to show correct rendering:
Assets.loadLibrary ("WCCmessageUI.swf").onComplete (function (_) {
var message = Assets.getMovieClip ("WCCmessageUI.swf:WCCsysMsg");
mc = getClip(message);
mc.rotation = 0.001;
addChild(mc);

Thanks!

This appears to be fixed in commit b630fb80ae5e2ca7b2bba7f9ad6139cc82bf0264. The fix will be included in the next update.


IPv6 preferred over IPv4 in mDNS

Based on the code in the following lines :
			if hasIPv4Address {
				addr = fmt.Sprintf("%s:%d", entry.AddrIPv4[0].String(), port)
				m.addAppAddressIPv4(appID, addr)
			}
			if hasIPv6Address {
				addr = fmt.Sprintf("%s:%d", entry.AddrIPv6[0].String(), port)
				m.addAppAddressIPv6(appID, addr)
			}

			if onEach != nil {
				onEach(addr) // invoke callback.
			}

https://github.com/dapr/components-contrib/blob/master/nameresolution/mdns/mdns.go#L708-L719
It is seen that onEach() is called with the address populated.
But when both IPv6 and IPv4 addresses are available for an application, IPv6 is given preference over IPv4 ...
Is this the expected behavior or should it be changed. As a follow up should there be some way to select only one interface to use when both are available?
cc @jjcollinge

@yaron2 @jjcollinge Can you comment on whether this the expected behavior ?

I'm not sure about changing the default (happy to if we think it's better to pick IPv4 over IPv6), I think making it possible to configure a preference seems reasonable.


feat: redis implementation of cache

Update cache interface and add redis implementation.

I'm not a fan of prefixing Context as the first arg to all methods. I think its mostly just interface bloat. A better pattern is to have one method available in a package that returns an interface with the context set.
func Context(ctx context.Context) Cache {
   return &cache{
     ctx: ctx,
   }
}

I'll change back to previous Context pattern, but do you think this will increase GC pressure in high concurrent scenario?

OK, thanks for your explanation.


research: compatibility with citus

Research if we could support citus

cc @cho-thinkfree-com

+1

Stream replication
Current situation
The main problem is at building the index, when index is replayed inside PG of standby instance:
postgres=# select * from pg_indexes where tablename = 't';
 schemaname | tablename | indexname | tablespace |                                               indexdef
------------+-----------+-----------+------------+-------------------------------------------------------------------------------------------------------
 public     | t         | t_val_idx |            | CREATE INDEX t_val_idx ON public.t USING vectors (val vector_l2_ops) WITH (options='[indexing.hnsw]')
(1 row)

but the backend hook ambuild is not triggered at WAL replay of standby instance. So they are no longer in sync, which lead to this error at any vector query:
postgres=# SELECT idx_status, idx_indexing FROM pg_vector_index_stat;
ERROR:  pgvecto.rs: The index is not existing in the background worker.
ADVICE: Drop or rebuild the index.

Implement
We need to write a custom WAL manager like this PR.
These operations should be logged:

Index create
Index edit
Index drop

Limitation

Write-ahead log (WAL) is supported only on Postgres 15+ due to the fact that custom WAL managers were introduced in Postgres 15

Citus
TODO

Thanks for your research!


Accidentally hid most buttons

In an attempt to hide the shortcut indicators that appear on hover I rashly used a line of css without testing on chat.beeper.com and now I hid most buttons, including the "Apply" button for CSS theming.
.mx_AccessibleButton:last-child {display: none;}
Is there anyway to reset the CSS without uninstalling?

@imjoshin any ideas what I could do about this?
Seems that uninstalling and reinstalling didn't work either - meaning they are probably stored locally.

Managed to fix problem with ctrl+shift+i.


add author field

allow for an "author" field.

I can take this one, I don't seem to have permission to assign myself though

Hi, any progress on this issue?

Hi, yes it just took me some time to figure out where I was supposed to add these components, but I should be able to get this done soon. Sorry for the delay!

No worries, just checking in! Thanks for working on the issue!


Declare Python 3.13 support

Tests pass...

Connecting to issue #2 .

Line 26: Did you mean 3.13?

Yes, it works on 3.13


Kf/visualizer

There are three main contributions from this pull request:

A more properly implemented corpus processing step in the generic pipeline, which outputs triplets, triplet stats, entity and predicate mappings, graph data, and a static graph.
Revamp of clustering approach for entities and predicates. It is not that different from Stine's work. The main difference is in choosing a main label. The overall strategy is:

Create embedding for each entity/predicate.
Cluster those embeddings with HDBSCAN.
Combine clusters that have labels in common.
Select as the main label for the cluster the most prototypical member of the cluster. The most prototypical member is the member with the embedding closest to the centroid embeddings of the cluster (i.e. the mean of all members of the cluster).

A visualization tool. I had hoped for something much more capable where you could inspect the entities' locations in text pieces etc., but for now this will have to do.

I am focusing on something else, so I am opening this to avoid it just going stale and being forgotten. Some parts of the code probably show this.

The failing documentation seems to be something in/with Sphinx and not the changes here. Any suggestions on how to fix it @KennethEnevoldsen ?

Can you run it locally?
you might try:
set sphinx==5.3.0 in the pyproject.toml (though I don't think it should work)
The error seems to stem from:
File "/home/runner/.local/lib/python3.10/site-packages/IPython/core/guarded_eval.py", line 40, in <module>
      from typing_extensions import TypeAliasType

which does not seem to be a sphinx issue

Nope, does not work locally, not even on main.

Nope, does not work locally, not even on main.

Will take a look!

Maybe with IPython. From the error log on my machine:
# Sphinx version: 5.3.0
# Python version: 3.10.12 (CPython)
# Docutils version: 0.19
# Jinja2 version: 3.1.3
# Last messages:

# Loaded extensions:
Traceback (most recent call last):
  File "~/PycharmProjects/conspiracies/venv/lib/python3.10/site-packages/sphinx/cmd/build.py", line 276, in build_main
    app = Sphinx(args.sourcedir, args.confdir, args.outputdir,
  File "~/PycharmProjects/conspiracies/venv/lib/python3.10/site-packages/sphinx/application.py", line 223, in __init__
    self.setup_extension(extension)
  File "~/PycharmProjects/conspiracies/venv/lib/python3.10/site-packages/sphinx/application.py", line 398, in setup_extension
    self.registry.load_extension(self, extname)
  File "~/PycharmProjects/conspiracies/venv/lib/python3.10/site-packages/sphinx/registry.py", line 472, in load_extension
    metadata = setup(app)
  File "~/PycharmProjects/conspiracies/venv/lib/python3.10/site-packages/myst_nb/__init__.py", line 8, in setup
    from .sphinx_ext import sphinx_setup
  File "~/PycharmProjects/conspiracies/venv/lib/python3.10/site-packages/myst_nb/sphinx_ext.py", line 22, in <module>
    from myst_nb.ext.download import NbDownloadRole
  File "~/PycharmProjects/conspiracies/venv/lib/python3.10/site-packages/myst_nb/ext/download.py", line 8, in <module>
    from myst_nb.sphinx_ import SphinxEnvType
  File "~/PycharmProjects/conspiracies/venv/lib/python3.10/site-packages/myst_nb/sphinx_.py", line 29, in <module>
    from myst_nb.core.execute import ExecutionResult, create_client
  File "~/PycharmProjects/conspiracies/venv/lib/python3.10/site-packages/myst_nb/core/execute/__init__.py", line 6, in <module>
    from .base import ExecutionError, ExecutionResult, NotebookClientBase  # noqa: F401
  File "~/PycharmProjects/conspiracies/venv/lib/python3.10/site-packages/myst_nb/core/execute/base.py", line 13, in <module>
    from myst_nb.ext.glue import extract_glue_data
  File "~/PycharmProjects/conspiracies/venv/lib/python3.10/site-packages/myst_nb/ext/glue/__init__.py", line 8, in <module>
    import IPython
  File "~/PycharmProjects/conspiracies/venv/lib/python3.10/site-packages/IPython/__init__.py", line 55, in <module>
    from .terminal.embed import embed
  File "~/PycharmProjects/conspiracies/venv/lib/python3.10/site-packages/IPython/terminal/embed.py", line 16, in <module>
    from IPython.terminal.interactiveshell import TerminalInteractiveShell
  File "~/PycharmProjects/conspiracies/venv/lib/python3.10/site-packages/IPython/terminal/interactiveshell.py", line 48, in <module>
    from .debugger import TerminalPdb, Pdb
  File "~/PycharmProjects/conspiracies/venv/lib/python3.10/site-packages/IPython/terminal/debugger.py", line 6, in <module>
    from IPython.core.completer import IPCompleter
  File "~/PycharmProjects/conspiracies/venv/lib/python3.10/site-packages/IPython/core/completer.py", line 219, in <module>
    from IPython.core.guarded_eval import guarded_eval, EvaluationContext
  File "~/PycharmProjects/conspiracies/venv/lib/python3.10/site-packages/IPython/core/guarded_eval.py", line 40, in <module>
    from typing_extensions import TypeAliasType
ImportError: cannot import name 'TypeAliasType' from 'typing_extensions' (~/PycharmProjects/conspiracies/venv/lib/python3.10/site-packages/typing_extensions.py)

Hmm I don't get that one (will just recreate my env). I can get it to work if I do:
nb_execution_mode = "off"  # "auto", "force", "off"

In the docs/conf.py
If that works then it seem to be an issue with the notebook execution

Hmm, interesting. That was also my first thought and that the error message just obscured what was the actual reason. I'll take a closer look tomorrow. It is surprising that it does not work on main either, but maybe it has gone under the radar somehow.

Without having the complete overview, I think what happened was some issue in peer-dependencies. If I opened IPython on my own machine, I would see the same error. I cannot reproduce it now, though; but maybe the latest version IPython needed a newer version of typing_extensions than what some of the other dependencies (which are kept back on older versions) would allow for.


Update to latest versions of each component

Applicable Issues

N/A
Description of the Change

Update to all latest versions of components.
This next release will be a major release, 2.0.0 due to #91
Alternate Designs

Benefits

Possible Drawbacks

Sign-off

Developer's Certificate of Origin 1.1
By making a contribution to this project, I certify that:
(a) The contribution was created in whole or in part by me and I
have the right to submit it under the open source license
indicated in the file; or
(b) The contribution is based upon previous work that, to the best
of my knowledge, is covered under an appropriate open source
license and I have the right under that license to submit that
work with modifications, whether created in whole or in part
by me, under the same open source license (unless I am
permitted to submit under a different license), as indicated
in the file; or
(c) The contribution was provided directly to me by some other
person who certified (a), (b) or (c) and I have not modified
it.
(d) I understand and agree that this project and the contribution
are public and that a record of the contribution (including all
personal information I submit with it, including my sign-off) is
maintained indefinitely and may be redistributed consistent with
this project or the open source license(s) involved.
Signed-off-by: Tobias Persson<EMAIL_ADDRESS>

@fredjn Is on vacation so I will approve this in his stead.


bst shell should be able to stage the specified element on top of a base element

See original issue on GitLab
In GitLab by [Gitlab user @tlater] on Jun 12, 2018, 12:32
Background
I find that I avoid using type: runtime on very low-level elements most of the time, even if they are technically runtime dependencies. This is because they tend to be large and contain dependencies mostly available on systems I'll want to deploy software to. It doesn't seem useful for bst checkout to checkout something like /bin/sh, for example.
This works for anything I want to run in CI, or actually use for deployable builds, but as soon as I start developing I want to run bst shell on whatever I am working on.
bst shell currently requires the runtime of any element I want to shell into to contain a /bin/sh, and therefore consistently breaks unless I add type: runtime to my base platform dependency. As a result I end up constantly adding and removing dependencies for debugging.
There is bst shell --sysroot, but it requires a checkout of the base platform, which makes it cumbersome to use for  debugging. It also doesn't update with potential changes to the base platform, which makes it feel wrong for this use case.
Acceptance Criteria
We should have a way to avoid specifying type: runtime on base platforms with bst shell. Options include:

Adding a --platform option which specifies a dependency to stage the given element on top of
Allow specifying multiple elements

This is still very up for discussion, please do comment :)
Update from Laurence, February 2019: This was discussed at the Gathering in Jan 2019 and a summary mail sent to the list which was discussed a little.

In GitLab by [Gitlab user @cs-shadow] on Jun 12, 2018, 14:55
I would quite like something like this too.
I would much prefer a solution where bst shell <element> "just works" without the need for any other options as that would be the more intuitive behavior IMHO.
To that end, another idea that comes to mind is defining something like base-runtime-platform(s) in project.conf which will get staged automatically anytime you run bst shell on any element. This would make sense for projects where almost all the elements will have the same base platform for runtime.
The same idea could be extended to build-time dependencies too. If all of .bst files in a project are going to depend on the same base platform, then having a dependency on it in each of the file seems overly verbose. This could be solved if there was a declare a base-build-platform(s) property in project.conf

cc [Gitlab user @sstriker] as we were discussing the same issue a while back.

In GitLab by [Gitlab user @LaurenceUrhegyi] on Jun 18, 2018, 16:15
marked this issue as related to #425

In GitLab by [Gitlab user @LaurenceUrhegyi] on Jun 18, 2018, 16:16
marked this issue as related to #425

In GitLab by [Gitlab user @LaurenceUrhegyi] on Jun 18, 2018, 16:16
removed the relation with #425

In GitLab by [Gitlab user @jennis] on Sep 18, 2018, 12:40

I would much prefer a solution where bst shell <element> "just works" without the need for any other options as that would be the more intuitive behavior IMHO.

+1, especially when you build an application in BuildStream, as one of the first things you're likely to do is bst shell application.bst and try to test it within the shell.
Here is my current workaround, which as you will be able to see, is much less than ideal:
At the moment, I'm currently building vim.bst, which, within it's pipeline, contains no runtime dependencies that provide the sh command, thus I cannot bst shell into it.
If I want to shell into something where I can execute vim --version or something similar, I'm currently creating a stack element that looks something like this:
kind: stack

runtime-depends:
- vim.bst
- platform.bst

I then bst build vim-stack.bst, then bst shell vim-stack.bst
^ Not ideal...

The same idea could be extended to build-time dependencies too. If all of .bst files in a project are going to depend on the same base platform, then having a dependency on it in each of the file seems overly verbose. This could be solved if there was a declare a base-build-platform(s) property in project.conf

Again +1.

In GitLab by [Gitlab user @tristanvb] on Sep 18, 2018, 15:24
Note that something similar was discussed on the mailing list
Basically, developers want to include their own personal tooling in their shell, and might have some tooling which is compatible with a runtime they are using inside bst shell.
The idea is to allow either overlay or underlay of a user specified filesystem into the shell; so that it is staged along with the regular BuildStream staging mechanism, so that a user can provide their own input to the shell, without using a --mount.
For this issue, I think we need to ensure that the use cases being employed here are in fact the intended use of dependencies.

If an element requires another to run, it should have a runtime dependency
Dependencies are both build + run by default
More fragmented decoupling is achieved with split-rules, not the dependency model

As far as I can see, it can happen that you have a situation where you want to shell into something without a dependency on the shell, this can be tricky to implement here as it may imply cyclic dependencies (does the shell inadvertently also depend on this element I want to shell into ?)

In GitLab by [Gitlab user @richardmaw-codethink] on Sep 28, 2018, 16:14
From my reading of the discussion, it's actually covered 4 different issues:

The need to stage more dependencies for a useful shell session.
You need to have a shell to have a useful shell session,
but you can build an application that doesn't use the shell at runtime,
therefore having the shell isn't a valid runtime dependency.
This can be generalised to more than just the "platform",
e.g. staging test dependencies if the purpose of running the shell is to do testing,
though testing on its own isn't the best example
as there's been discussion of making that a first-class feature
for the purposes of passing/failing builds rather than punting the decision to running a shell.

Adding tooling that isn't defined in .bst files to the shell
This is a natural extension to wanting to stage more things,
and could be used in some circumstances to solve the same problems as (1),
but there's other cases where (1) would be more convenient.
There doesn't appear to be an issue specifically for this.

Being able to cheaply export to a Docker image.
The argument for this appears to be that it's a problem with a known solution under Docker.
Given Docker doesn't allow you to combine multiple images to create a container
I can't see this ever becoming a zero-copy operation,
so there'll be value in bst shell being able to make the container if it can do so quicker.
https://gitlab.com/BuildStream/buildstream/issues/349 already exists for this.

Being able to use Docker as a container runtime backend.
Depending how it's implemented it might make (3) easier, but otherwise is unrelated.
There doesn't appear to already be an issue for this, but [Gitlab user @cs]-shadow was looking at it earlier.

In GitLab by [Gitlab user @richardmaw-codethink] on Sep 28, 2018, 17:42
This is in bikeshedding territory,
but the presence of base-build-platform and base-runtime-platform
suggests a symmetry with build-dependencies and runtime-dependencies to me
and that it adds dependencies to every element,
despite such an idea only working with a systemd-style
NoDefaultDependencies=yes option.
It may be possible to do base-build-platform behaviour with element overrides
https://buildstream.gitlab.io/-/buildstream/-/jobs/58667641/artifacts/public/projectconf.html#element-overrides
setting replacing the dependencies for the default set,
and using the merge syntax to add extra dependencies on top of the default set.
project.conf
elements:
  ...
    depends:
    - platform.bst

platform.bst
depends: []

foo.bst
depends:
  (>):
  - barlib.bst

We might be able to solve both this, and have a default target for shell
by merging the elements from the command-line with those in project.conf,
but possibly not both at the same time.
The configuration in project.conf may look something like this:
shell:
  elements:
    (<):
    - platform.bst
    (>):
    - debugger.bst

I suspect the best way to work out a good interface will be to try it
and then see how people feel about it.
I expect to get to this after I've looked at
separating sandboxing errors from build errors.

In GitLab by [Gitlab user @richardmaw-codethink] on Oct 5, 2018, 10:41
assigned to [Gitlab user @richardmaw-codethink]

In GitLab by [Gitlab user @richardmaw-codethink] on Oct 29, 2018, 14:18
mentioned in merge request !909

In GitLab by [Gitlab user @LaurenceUrhegyi] on Jan 31, 2019, 11:22
Discussion from London Gathering, January 2019:

Not very controversial for multiple runtime shells.
For build shells, we can’t really have multiple build environments, let’s be clear that the use-case is to have exactly one element that sets the build environment but the ability to add more elements into the shell as runtime.
Angelos highlighted a central use-case where people may been working on a library AND multiple apps at the same time. Coming in and out of shells for that might be a pain?
Valentin raised the point that if you modify a new library you’ll have to rebuild it anyway, in that light, using another shell isn’t really an extra inconvenience
For many users' use-case, any testing of anything that has been built, needs to happen inside the shell.
One problem, how do we know what’s already been staged? Need to expand the API to figure our shared dependencies? Complicated addition required for this use-case…?
We didn’t feel too comfortable to commit to that (yet).
Chandan re-raised the issue that shell is too slow to invoke.
Re-staging things seems to be the biggest issue.
Click won’t let us: bst shell --build one.bst two.bst three.bst now-give-me-this-runtime.bst and-this-runtime.bst
Perhaps elements we want for runtime are the default arguments, which can be unlimited, and the build element (or elements…?) must be specified with --build this.bst --build that.bst
Can split this into two steps (where the first is much more attainable):
Be able to stage multiple runtime elements and JUST ONE build element
Editing multiple elements in the shell at the same time (i.e. allowing for multiple build elements)
There will be some complications with the --deps option, we’d have to allow this to support limited options.

In GitLab by [Gitlab user @LaurenceUrhegyi] on Feb 14, 2019, 08:23
changed the description

In GitLab by [Gitlab user @LaurenceUrhegyi] on Feb 14, 2019, 08:24
changed the description

In GitLab by [Gitlab user @jennis] on Feb 15, 2019, 15:04
Link to the most recent summary email: https://mail.gnome.org/archives/buildstream-list/2019-February/msg00001.html


Upgrade juice to 3.0.1

Thanks @houjunchen - see #227
See v2.6.0 on NPM npm install --save email-templates@latest


feat(middleware): add ability to force single build pass

This is the second (and last) hack required for the middleware bundle on cloudflare.
For us the second build pass is hanlded by wrangler. This PR adds an option to disable that pass.

FYI you can't merge multiple PR at the same time without crashing the e2e test (the cdk cannot update an app that are already in the UPDATE_IN_PROGRESS state )
You need to wait for the end of the previous e2e test. Also something that we should rework in the future.

Ah cool, I was just looking at why tests failed. Thanks!


nixos/fprintd: add TOD support

Motivation for this change
#104915 introduces TOD support. This PR is covering this functionality in the fprintd module.
Things done

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

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[ ] Fits CONTRIBUTING.md.

I see #104915 has been merged, do we need anything else done here before merging? @SuperSandro2000

@ofborg eval

fprtind -> fprintd :)

Rephrased commit message, thanks eagle eye @deviant 😉

@kamushadenes @trobert I see you both were active in the #104915 so may I ask you to test this PR as well? Appreciate in advance any feedback.

Looks pretty good, though I’m skeptical about making the goodix driver
the default.
On April 9, 2021, GitHub @.***> wrote:

@ymatsiuk https://github.com/ymatsiuk requested your review on:
#117928 https://github.com/NixOS/nixpkgs/pull/117928 nixos/fprintd:
add TOD support.

—
You are receiving this because your review was requested.
Reply to this email directly, view it on GitHub
https://github.com/NixOS/nixpkgs/pull/117928#event-4574368077, or
unsubscribe <https://github.com/notifications/unsubscribe-
auth/AAASXLEJRA4U32JEM57N66DTH34KHANCNFSM4Z7KMQGQ>.

@grahamc this is the only driver available in nixpkgs that I've found so far 🙂

works perfectly! thank you !!

@grahamc I'm curious about what do you think: leaving default driver package empty and notify the user that they have to specify the package manually makes more sense in this case?

@grahamc I'm curious about what do you think: leaving default driver package empty and notify the user that they have to specify the package manually makes more sense in this case?

Yeah, I think a good choice would be to put the goodix package as an example value. In case a new driver comes along, we won't need to break existing users: they'll already have specified the driver they intend.

@grahamc thanks for the input! Removed default values for pkgs and added example.

Thanks!


Send expression level coverage report

Work branch: https://github.com/guillaume-nargeot/codecov-haskell/tree/expression-level-coverage
Some initial changes were made in a420f6f5ddeb36fade0bb2706b97f007ae512fee and 2c8ca354127912b5b6c622d4a282e065b629e843 to propagate additional information required to compute expression level coverage.
The remaining work consist in performing the following transformations:

split coverage entries which cover multiple lines into ones that cover only a single line

in the case of TopLevelEntry, discard all but the first line in case it is hit at least once
splitted lines will have their start column adjusted to the first non-blank character of the covered code

"unnest" coverage entries (see this gist for details)

Below are examples html outputs produced by hpc, which is what codecov-haskell should try to reproduce.
These html reports were generated for the same peace of code, with differing variations of coverage.
--
No coverage at all:

Coverage when tested with takeUntil (> 1) [] ~=? []:

Coverage when tested with takeUntil (> 1) [2] ~=? [2]:

Coverage when tested with takeUntil (> 1) [1, 2] ~=? [1, 2]:

--

TODO check what multi-line if-then-else statements mix entries look like depending on their coverage


update Django to a later version.

Update to 1.6 first, then test, then test, and then update to 1.7

1.6 seems to check out just fine w/launchpad-autotest. running 1.7 now.

1.7 introduces migrations, which appear to be mandatory in a way I haven't found a simple way to route around yet.  For now, targeting 1.6. We can re-evaluate again later.
Note that the changes to persistent connections (https://docs.djangoproject.com/en/1.8/ref/databases/#persistent-database-connections) and the CONN_MAX_AGE setting might help us with the connection issues we've seen.

Note that the old from django.utils import simplejson as json shim was removed as of 1.5: https://docs.djangoproject.com/en/1.8/releases/1.5/#simplejson-deprecation
Replacing with import json and testing.

Closed by 1031.


deleting portion of code supporting Ruby < 1.9 for Bundler 2.0

I think this should be the last of the intended (valid) changes from #6803

The only failure here is for Ruby 1.8.7.

@gavrieltal Thanks! But the current master branch already fixed this pull-request.


connection problem its always red(for connection)

dear sir
whenever i got on site it does not connect live and says to refresh and connects for a second, after that the connection get lost, i think due to this i am not being able to get live streaming of charts. Kindly help with this. - posted by<EMAIL_ADDRESS>

Resolved


Install Anisble dependencies on remote nodes

Fixes #346
Install python-simplejson and libselinux-python packages from their docs

Should we be doing this? What happens when there is no internet connection on the nodes? I would guess the error message would be more confusing than the current one.

Yes I've modified the PR to not install the packages just check for libselinux-python in the inspector.
Also it looks like python-simplejson is only required for older Python versions as we dont have this package installed on our test machines and it still works.

Closing for now


(enhancement) Dark Page Color In Dark Theme

RectifyPad is a great app, but I believe it requires a dark page color option similar to the one in word and notepad. The light color is not easy on the eyes and just looks out of place when everything else is in a dark theme.

Fine, i'll work on adding it later

Thank You

Fixed in commit e48949c
Thanks for adding the feature


Fix runtime template using es5 function style

Using latest release of this plugin has thrown some error in some browser that doesn't support es6 syntax, need to change this line bro.

Indeed. Can you fix the tests? Then I'll be able to merge.

Forgot about the test, will working on it.

Am I doing it right for fix the test fixtures? specially on case paths-explicit-absolute-tools-override-outside. I just copy paste the hash value from output to expected value there.

Yeah, you are doing it right. Thank you for the PR, I'll merge as soon as I'm back to my computer.

no problem  bro.

@diondirza oh, I just realized that. You made PR against master but it had to be done against v4 branch :-(

I did the fix manually, I was a bit critical I guess. Anyway, thank you very much for creating this and pointing me to this problem. Very appreciated!
4.6.1 is out with the fix, btw

no problem, I was gonna change the pull request when I got home. Sorry for late response bro.. Anyway good job!


[docs] Explain more clearly where the ref prop actually goes

Duplicates

[X] I have searched the existing issues

Related page
https://mui.com/joy-ui/api/input/
Kind of issue
Unclear explanations
Issue description
I needed to get a ref of the <input> element, and i thought the root element in "The ref is forwarded to the root element." refers to it, but it refers to some container div. If this is intended behavior I would consider adding inputRef property like in MUI. Or show how to pass the ref to the input element
<Input
  slotProps={{ input: { ref } }}
></Input>

Context 🔦
Spent 30 minutes why my imask wasn't working, before I found out the root element refers to something other than input element

Thanks for the feedback. Do you think this section is enough? or should it be another demo that's specific to the input ref?

Well kinda, I would include ref in the HTML attributes such as min, max, and autocomplete. So it's more clear, and people searching ref on that page using Ctrl + F can find ti

Well kinda, I would include ref in the HTML attributes such as min, max, and autocomplete. So it's more clear, and people searching ref on that page using Ctrl + F can find ti

Would you like to submit a PR? That'd be really welcome.

Well kinda, I would include ref in the HTML attributes such as min, max, and autocomplete. So it's more clear, and people searching ref on that page using Ctrl + F can find ti

Would you like to submit a PR? That'd be really welcome.

Will try when I get home in like 5 hours

Fixed by #36913


Unable to see app full name

I am unable to see the app full name in the list and in info, despite it being available in Winget-cli:

Image 1 (list):

Image 2 (info):

Image 3 (Powershell):

Related:
https://github.com/martinet101/WingetUI/commit/9dfbaf35384f61fab1c1c3af102572d35ec2e79d
https://github.com/martinet101/WingetUI/issues/187

About image 1, what do you think about making the tooltip show the full name?
About image 2, I see 2 ways to solve that: reduce font size or make it possible to select text that is off screen

Well, this text cut out must be fixed

despite it being available in Winget-cli

Well, running winget search does not always show the full app names

despite it being available in Winget-cli

Well, running winget search does not always show the full app names

It puzzles me why Winget-cli sometimes doesn't show the full app name. I would open an issue in Winget-cli, but I don't know how to explain it very well. I am aware there's not much you can do to mitigate this issue in WingetUI, but thanks for still trying!

It puzzles me why Winget-cli sometimes doesn't show the full app name. I would open an issue in Winget-cli, but I don't know how to explain it very well. I am aware there's not much you can do to mitigate this issue in WingetUI, but thanks for still trying!

yeah, winget does behave weirdly sometimes (i gues we can blame microsoft for it hehe)


CentOS based Docker resources for WSO2 Stream Processor v4.3.x

Description:
It is required to create CentOS based Docker resources for WSO2 Stream Processor v4.3.x. Further, Docker-Compose resources need to be tested with these Docker resources.
Suggested Labels:
Type/NewFeature
Suggested Assignees:
chamindi-a
Affected Product Version:
WSO2 Stream Processor 4.3.x

Fixed in https://github.com/wso2/docker-sp/pull/57.


Add global helper functions, update dependencies & readme, add DatoCMS

This moves some global helper functions up from the hashicorp-www-middleman project into this project for easier reuse across different projects.

I've tested this with a modified (changes to config.rb) version of https://github.com/hashicorp/hashicorp-www-middleman and it's working well.

@jescalan Tagging you here, I can't add you as a reviewer.

Waiting on response back from Dato folks on slowdown in Dato 0.6.2 - see @schonfeld's comment

@jescalan Think this is ready to roll.


Beautify frontend

It works, but it's not pleasant to view.

[x] Fix menu behavior so that menu hides & re-appears
[x] Fix font sizes
[ ] Display data in a clean-looking grid

https://github.com/DenisKolodin/yew/blob/master/examples/fragments/src/lib.rs
And
https://purecss.io/tables/#table-with-horizontal-borders


Add xmas:feature preset

OSM Tag(s)
xmas:feature=*
How would you like this tag to see supported?
As a Preset
Label
Christmas Tree, Market....
Aliases
Xmas, Santa, Christmas
Terms
Xmas, Santa, Christmas
Link to OSM Wiki page
https://wiki.openstreetmap.org/wiki/Key:xmas:feature
Status of the Tag
In Use
Usage of the tag
2503
Replaces other Tag?
no
Regional Tag?
in some parts of the world
Further Information
Merry Christmas :),
I would like to request the inclusion of xmas:feature in iD's presets.
taginfo
https://taginfo.openstreetmap.org/keys/xmas:feature
JOSM-Preset
https://josm.openstreetmap.de/wiki/Presets/Xmas
best regards
Miche101

What I would find super interesting in this context is to unify how to tag visit dates / dates of when the existence was checked last time (check_date) of the xmas features uniformly.
Although, @miche101, I think you're working on it right now, right?
Back then, my suggestion to expand the use of check_date in iD was not rejected: https://github.com/openstreetmap/iD/issues/7414
(that was not related to the xmas:features though).

hi,
xmas:day_date and xmas:opening_hours better united in one value? Yes, that would be better, but wouldn't be easy for the mappers. You would then have something like this:
opening_hours="2019 Jul 23 05:00-24:00; 2019 Jul 24-2019 Jul 26 00:00-24:00; 2019 Jul 27 00:00-18:00"
Oh my god! ... There is also no tool that does that for the user.
Yes, I'm working on cleaning up a lot of things. The German wiki in particular differs from the English wiki in a few things. Many things were still invented in the German Wiki.
But I have to be careful because OSMand already has support for 4 XMas-feature (tree, market, shop, pyramid) not to break it.
OSMand understands: xmas:name, xmas:day_date, xmas:location, xmas:opening_hours (partial support only), xmas:url, xmas:note... from what I know.
check_date helps when you say you have a lot of dates and are looking for dates that are probably out of date. For example, you want all OSM objects that have not been processed for 15 years. You check everything, what do you do with those where there is nothing to change or add. You can add Check_date or move the object by one meter, I find adding Check_date= better. But if adding is too complicated, many will simply move.
A button to set the current one would be enough..
best regards
Miche101

I see. Thanks for your quick answer.

xmas:day_date and xmas:opening_hours better united in one value?

Maybe you don't have to go that far. I rather meant maybe not using xmas:lastcheck anymore and then check_date (or better probably xmas:check_date) instead
xmas:day_date can remain in my view.

The German wiki in particular differs from the English wiki in a few things. Many things were still invented in the German Wiki.

True.
For example, I noticed that in the German Wiki for xmas:feature=market all additional tags with namespace, for example xmas:opening_hours, are suggested,
for other features like xmas:feature=shop + xmas:feature:shop=christmas_tree the "normal" opening_hours key can be used according to the wiki.
Whether one could achieve uniformity in this regard, especially as far as the preset is concerned?
The advantage of namespace "xmas:..." is of course that the opening hours of a xmas:feature=market can be clearly assigned with xmas:opening_hours if the Christmas market takes place at an amenity=marketplace, for example, which has its own opening_hours.
If so, I would definitely be in favor of implementing all additional tags in the preset with the xmas namespace.

xmas:lastcheck and check_date. Until 2016, the German wiki also had check_date
Anything with xmas: is not a good idea. You have to look closely. A Christmas tree that is a natural tree would you have to have double keys for everything? A store that sells Chist trees would have to do all the keys twice
I'm definitely not in favor of it, because then I might as well close the issues. Because the namespace is more of a reason to refuse the recording..

I tried a preset to write, I don't know if it works..
data.zip
What's the best way to do that?  ( https://www.openstreetmap.org/node/1741924902 ) a add to preset tree.json ... natural and matchScore?
To market and event i add seasonal=christmas because you can enter everything without XMAS: , works with my site https://greymiche.lima-city.de/xmas/

or more fields for the most used xmas:* Keys xmas:name, xmas:day_date, xmas:location, xmas:opening_hours, xmas:url ..


Bug fixes in ATT Client

bugfix: disconnecting from an ATT client works now
bugfix: sending a connection_create cmd when a device is unavailable
retries now
bugfix: multiple ATT clients can now be started simultaneously
bugfix: reconnect now works
bugfix: HCI and ACL calls will now timeout rather than hang forever
bugfix: connection_complete event now uses the correct address
endianness

The commented out code is for stuff that other ATT clients do (at least android and btstack). stuff that we will want to implement in the future, but isn't strictly required for ATT to work.


Upgrade to newer kernel versions (4.9.x, etc.)

The current master branch uses a special tagged version of the 4.4.x kernel line for RaspberryPi. We should revisit possibilities to upgrade to newer kernel versions in a future version of RaspberryMatic (as soon as we have implemented HomeMatic-IP support). See here for development on linux kernels for RaspberryPi: https://github.com/raspberrypi/linux

As we are using the PREEMPT_RT real time patches now we are bound to the kernel versions compatible to the RT patches. as such we are currently bound to kernel versions 4.4.


[5.4] Date objects returned by the framework should be in the correct locale

Rationale:
When using Laravel, you may want to serve a site in multiple languages, and change that language at runtime. Eloquent and other parts of the framework return date objects that can be displayed in human relative text form, or formatted in a localized string. We have a locale that is set by default when the app boots, and it can also be called using App::setLocale('code').
Users expect objects returned from the framework to be in the locale that they set in the configuration options.
Assuming timestamp of 2016-12-28 00:00:00 and locale in config of 'de'
Before PR:
echo User::first()->created_at->diffForHumans(); // Output: "4 months ago"
App::setLocale('fr');
echo User::first()->created_at->diffForHumans(); // Output: "4 months ago"

After PR:
echo User::first()->created_at->diffForHumans(); // Output: "vor 4 Monaten"
App::setLocale('fr');
echo User::first()->created_at->diffForHumans(); // Output: "il y a 4 mois"

The Translation class is the logical place to set this, even though Carbon is used from many places in the framework, it is never 'initialized' anywhere.

I'm not sure this is the best place for this. IMO it belongs in a middleware or service provider in your application. The translator might not even be constructed on some requests. Thanks.

Thank you very much for the feedback @taylorotwell
Moving the logic into Eloquent by listening for locale change events before it returns a Carbon date object may make more sense, as this is the place the objects are made. To set this once in the config, then have to interact with another lib in a middleware or service provider feels odd to me.
{{ $user->first()->created->formatLocalized('%d %B %Y') }} => Always returning English regardless of app setting may seem strange when it's Laravel that's exposing the 'formatLocalized' method to the user.
Happy to explore other options to make this as logical as possible for the user and the framework.


feat: split dashboards for 7mode - volume

For 7mode system, vol create is based on aggr name, means aggr+vol name is unique.
tobago-2> vol help create
vol create <vol-name>
        { [-l <language-code>] [-s {none | file | volume}]
          <hosting-aggr-name> <size>[k|m|g|t] }
    |
        { [-l <language-code>] <hosting-aggr-name>
          [size[k|m|g|t]] -S <remotehost:remotevolume> }
    |
        { [-f] [-l <language-code>] [-m] [-n]
          [-L [compliance | enterprise]]
          [-r <raid-group-size>] [-t {raid4 | raid_dp}]
          <disk-list> }
 -- create a new volume, either a flexible volume from an existing
   aggregate, or a traditional volume from a disk list.  A disk
   list is either
           <ndisks>[@<disk-size>]
   or
           -d <disk-name1> <disk-name2> ... <disk-nameN>
           [-d <disk-name1> <disk-name2> ... <disk-nameN>].

link: https://library.netapp.com/ecm/ecm_download_file/ECMP1196890
Few examples from above link:

gaps:

7 mode perf counters don't have node/svm detail
bin/zapi --poller cluster-04 show data --object volume | dasel -r xml -w json
...
...
{
"name": "node_name",
"value": ""
},
{
"name": "node_uuid",
"value": ""
},
{
"name": "process_name",
"value": ""
},
{
"name": "vserver_name",
"value": ""
},
{
"name": "vserver_uuid",
"value": ""
},
{
...
...

As we are not able to get svm name detail in perf counters for 7mode, we use join query with volume labels such that it can be filterable in 7mode.
ex: volume_avg_latency{datacenter="$Datacenter",cluster="$Cluster",volume=~"$Volume"} * on  (volume, aggr) group_right() volume_labels{datacenter="$Datacenter",cluster="$Cluster",svm=~"$SVM",volume=~"$Volume"}

for lun,
lun-list-info zapi and lun counter don't have svm/vfiler detail, so svm level filter has been removed for lun dashboard in 7mode.

Unit testing:
Import dashboards
Case 1:
fresh import:
bin/grafana import --addr localhost:3000 --directory grafana/dashboards
using API token from config
connected to Grafana server (version: 8.1.2)
created Grafana folder [Harvest 2.0] - OK
created Grafana folder [7 mode] - OK
preparing to import dashboards...
OK - imported [harvest_dashboard_aggregate7.json]
OK - imported [harvest_dashboard_cluster7.json]
OK - imported [harvest_dashboard_disk7.json]
OK - imported [harvest_dashboard_lun7.json]
OK - imported [harvest_dashboard_metadata7.json]
OK - imported [harvest_dashboard_network7.json]
OK - imported [harvest_dashboard_node7.json]
OK - imported [harvest_dashboard_nvme_fc7.json]
OK - imported [harvest_dashboard_shelf7.json]
OK - imported [harvest_dashboard_volume7.json]
Imported 10 dashboards from grafana/dashboards/7mode
OK - imported [harvest_dashboard_aggregate.json]
OK - imported [harvest_dashboard_cluster.json]
OK - imported [harvest_dashboard_disk.json]
OK - imported [harvest_dashboard_lun.json]
OK - imported [harvest_dashboard_metadata.json]
OK - imported [harvest_dashboard_network.json]
OK - imported [harvest_dashboard_network_detail.json]
OK - imported [harvest_dashboard_node.json]
OK - imported [harvest_dashboard_node_details.json]
OK - imported [harvest_dashboard_nvme_fc.json]
OK - imported [harvest_dashboard_shelf.json]
OK - imported [harvest_dashboard_snapmirror.json]
OK - imported [harvest_dashboard_svm.json]
OK - imported [harvest_dashboard_svm_details.json]
OK - imported [harvest_dashboard_volume.json]
OK - imported [harvest_dashboard_volume_details.json]
Imported 16 dashboards from grafana/dashboards
Case 2:
one folder exist other not(7 mode not exist):
hardikl@hardikl-mac-0 harvest % bin/grafana import --addr localhost:3000 --directory grafana/dashboards
using API token from config
connected to Grafana server (version: 8.1.2)
folder [Harvest 2.0] exists in Grafana - OK
created Grafana folder [7 mode] - OK
preparing to import dashboards...
OK - imported [harvest_dashboard_aggregate7.json]
OK - imported [harvest_dashboard_cluster7.json]
OK - imported [harvest_dashboard_disk7.json]
OK - imported [harvest_dashboard_lun7.json]
OK - imported [harvest_dashboard_metadata7.json]
OK - imported [harvest_dashboard_network7.json]
OK - imported [harvest_dashboard_node7.json]
OK - imported [harvest_dashboard_nvme_fc7.json]
OK - imported [harvest_dashboard_shelf7.json]
OK - imported [harvest_dashboard_volume7.json]
Imported 10 dashboards from grafana/dashboards/7mode
OK - imported [harvest_dashboard_aggregate.json]
OK - imported [harvest_dashboard_cluster.json]
OK - imported [harvest_dashboard_disk.json]
OK - imported [harvest_dashboard_lun.json]
OK - imported [harvest_dashboard_metadata.json]
OK - imported [harvest_dashboard_network.json]
OK - imported [harvest_dashboard_network_detail.json]
OK - imported [harvest_dashboard_node.json]
OK - imported [harvest_dashboard_node_details.json]
OK - imported [harvest_dashboard_nvme_fc.json]
OK - imported [harvest_dashboard_shelf.json]
OK - imported [harvest_dashboard_snapmirror.json]
OK - imported [harvest_dashboard_svm.json]
OK - imported [harvest_dashboard_svm_details.json]
OK - imported [harvest_dashboard_volume.json]
OK - imported [harvest_dashboard_volume_details.json]
Imported 16 dashboards from grafana/dashboards
Case 3:
both folder exist(but removed 2-3 dashboards from grafana UI):
hardikl@hardikl-mac-0 harvest % bin/grafana import --addr localhost:3000 --directory grafana/dashboards
using API token from config
connected to Grafana server (version: 8.1.2)
folder [Harvest 2.0] exists in Grafana - OK
folder [7 mode] exists in Grafana - OK
preparing to import dashboards...
OK - imported [harvest_dashboard_aggregate7.json]
OK - imported [harvest_dashboard_cluster7.json]
OK - imported [harvest_dashboard_disk7.json]
OK - imported [harvest_dashboard_lun7.json]
OK - imported [harvest_dashboard_metadata7.json]
OK - imported [harvest_dashboard_network7.json]
OK - imported [harvest_dashboard_node7.json]
OK - imported [harvest_dashboard_nvme_fc7.json]
OK - imported [harvest_dashboard_shelf7.json]
OK - imported [harvest_dashboard_volume7.json]
Imported 10 dashboards from grafana/dashboards/7mode
OK - imported [harvest_dashboard_aggregate.json]
OK - imported [harvest_dashboard_cluster.json]
OK - imported [harvest_dashboard_disk.json]
OK - imported [harvest_dashboard_lun.json]
OK - imported [harvest_dashboard_metadata.json]
OK - imported [harvest_dashboard_network.json]
OK - imported [harvest_dashboard_network_detail.json]
OK - imported [harvest_dashboard_node.json]
OK - imported [harvest_dashboard_node_details.json]
OK - imported [harvest_dashboard_nvme_fc.json]
OK - imported [harvest_dashboard_shelf.json]
OK - imported [harvest_dashboard_snapmirror.json]
OK - imported [harvest_dashboard_svm.json]
OK - imported [harvest_dashboard_svm_details.json]
OK - imported [harvest_dashboard_volume.json]
OK - imported [harvest_dashboard_volume_details.json]
Imported 16 dashboards from grafana/dashboards
case 4:
custom names:
hardikl@hardikl-mac-0 harvest % bin/grafana import --addr localhost:3000 --directory grafana/dashboards -H cmode -f filer7
using API token from config
connected to Grafana server (version: 8.1.2)
created Grafana folder [cmode] - OK
created Grafana folder [filer7] - OK
preparing to import dashboards...
OK - imported [harvest_dashboard_aggregate7.json]
OK - imported [harvest_dashboard_cluster7.json]
OK - imported [harvest_dashboard_disk7.json]
OK - imported [harvest_dashboard_lun7.json]
OK - imported [harvest_dashboard_metadata7.json]
OK - imported [harvest_dashboard_network7.json]
OK - imported [harvest_dashboard_node7.json]
OK - imported [harvest_dashboard_nvme_fc7.json]
OK - imported [harvest_dashboard_shelf7.json]
OK - imported [harvest_dashboard_volume7.json]
Imported 10 dashboards from grafana/dashboards/7mode
OK - imported [harvest_dashboard_aggregate.json]
OK - imported [harvest_dashboard_cluster.json]
OK - imported [harvest_dashboard_disk.json]
OK - imported [harvest_dashboard_lun.json]
OK - imported [harvest_dashboard_metadata.json]
OK - imported [harvest_dashboard_network.json]
OK - imported [harvest_dashboard_network_detail.json]
OK - imported [harvest_dashboard_node.json]
OK - imported [harvest_dashboard_node_details.json]
OK - imported [harvest_dashboard_nvme_fc.json]
OK - imported [harvest_dashboard_shelf.json]
OK - imported [harvest_dashboard_snapmirror.json]
OK - imported [harvest_dashboard_svm.json]
OK - imported [harvest_dashboard_svm_details.json]
OK - imported [harvest_dashboard_volume.json]
OK - imported [harvest_dashboard_volume_details.json]
Imported 16 dashboards from grafana/dashboards
Export dashboards:
case 1:
fresh export:
hardikl@hardikl-mac-0 harvest % bin/grafana export --addr localhost:3000 --directory grafana/A
using API token from config
connected to Grafana server (version: 8.1.2)
querying for content of folder id [222]
exporting dashboards to directory [grafana/A/Harvest_2.0]
OK - exported [grafana/A/Harvest_2.0/db_netapp_detail_node.json]
OK - exported [grafana/A/Harvest_2.0/db_netapp_detail_snapmirror.json]
OK - exported [grafana/A/Harvest_2.0/db_netapp_detail_volume.json]
OK - exported [grafana/A/Harvest_2.0/db_netapp_detail_volume_details.json]
OK - exported [grafana/A/Harvest_2.0/db_netapp_detail_network_details.json]
OK - exported [grafana/A/Harvest_2.0/db_netapp_detail_node_details.json]
OK - exported [grafana/A/Harvest_2.0/db_netapp_detail_shelf.json]
OK - exported [grafana/A/Harvest_2.0/db_netapp_detail_svm.json]
OK - exported [grafana/A/Harvest_2.0/db_netapp_detail_svm_details.json]
OK - exported [grafana/A/Harvest_2.0/db_harvest_metadata.json]
OK - exported [grafana/A/Harvest_2.0/db_netapp_detail_lun.json]
OK - exported [grafana/A/Harvest_2.0/db_netapp_detail_network.json]
OK - exported [grafana/A/Harvest_2.0/db_netapp_detail_network_with_nvme_fc.json]
OK - exported [grafana/A/Harvest_2.0/db_netapp_detail_aggregate.json]
OK - exported [grafana/A/Harvest_2.0/db_netapp_detail_cluster.json]
OK - exported [grafana/A/Harvest_2.0/db_netapp_detail_disk.json]
exported 16 dashboards to [grafana/A/Harvest_2.0]
querying for content of folder id [223]
exporting dashboards to directory [grafana/A/7_mode]
OK - exported [grafana/A/7_mode/db_netapp_detail_shelf_7_mode.json]
OK - exported [grafana/A/7_mode/db_netapp_detail_aggregate_7_mode.json]
OK - exported [grafana/A/7_mode/db_netapp_detail_cluster_7_mode.json]
OK - exported [grafana/A/7_mode/db_netapp_detail_network_with_nvme_fc_7_mode.json]
OK - exported [grafana/A/7_mode/db_netapp_detail_node_7_mode.json]
OK - exported [grafana/A/7_mode/db_netapp_detail_volume_7_mode.json]
OK - exported [grafana/A/7_mode/db_harvest_metadata_7_mode.json]
OK - exported [grafana/A/7_mode/db_netapp_detail_disk_7_mode.json]
OK - exported [grafana/A/7_mode/db_netapp_detail_lun_7_mode.json]
OK - exported [grafana/A/7_mode/db_netapp_detail_network_7_mode.json]
exported 10 dashboards to [grafana/A/7_mode]
case 2:
one folder exist other not (7 mode deleted from grafana/A location):
hardikl@hardikl-mac-0 harvest % bin/grafana export --addr localhost:3000 --directory grafana/A
using API token from config
connected to Grafana server (version: 8.1.2)
querying for content of folder id [222]
exporting dashboards to directory [grafana/A/Harvest_2.0]
OK - exported [grafana/A/Harvest_2.0/db_netapp_detail_network_details.json]
OK - exported [grafana/A/Harvest_2.0/db_netapp_detail_node.json]
OK - exported [grafana/A/Harvest_2.0/db_netapp_detail_node_details.json]
OK - exported [grafana/A/Harvest_2.0/db_netapp_detail_aggregate.json]
OK - exported [grafana/A/Harvest_2.0/db_netapp_detail_lun.json]
OK - exported [grafana/A/Harvest_2.0/db_netapp_detail_snapmirror.json]
OK - exported [grafana/A/Harvest_2.0/db_netapp_detail_volume_details.json]
OK - exported [grafana/A/Harvest_2.0/db_harvest_metadata.json]
OK - exported [grafana/A/Harvest_2.0/db_netapp_detail_network.json]
OK - exported [grafana/A/Harvest_2.0/db_netapp_detail_shelf.json]
OK - exported [grafana/A/Harvest_2.0/db_netapp_detail_volume.json]
OK - exported [grafana/A/Harvest_2.0/db_netapp_detail_cluster.json]
OK - exported [grafana/A/Harvest_2.0/db_netapp_detail_network_with_nvme_fc.json]
OK - exported [grafana/A/Harvest_2.0/db_netapp_detail_svm_details.json]
OK - exported [grafana/A/Harvest_2.0/db_netapp_detail_disk.json]
OK - exported [grafana/A/Harvest_2.0/db_netapp_detail_svm.json]
exported 16 dashboards to [grafana/A/Harvest_2.0]
querying for content of folder id [223]
exporting dashboards to directory [grafana/A/7_mode]
OK - exported [grafana/A/7_mode/db_harvest_metadata_7_mode.json]
OK - exported [grafana/A/7_mode/db_netapp_detail_aggregate_7_mode.json]
OK - exported [grafana/A/7_mode/db_netapp_detail_node_7_mode.json]
OK - exported [grafana/A/7_mode/db_netapp_detail_volume_7_mode.json]
OK - exported [grafana/A/7_mode/db_netapp_detail_cluster_7_mode.json]
OK - exported [grafana/A/7_mode/db_netapp_detail_disk_7_mode.json]
OK - exported [grafana/A/7_mode/db_netapp_detail_lun_7_mode.json]
OK - exported [grafana/A/7_mode/db_netapp_detail_network_7_mode.json]
OK - exported [grafana/A/7_mode/db_netapp_detail_network_with_nvme_fc_7_mode.json]
OK - exported [grafana/A/7_mode/db_netapp_detail_shelf_7_mode.json]
exported 10 dashboards to [grafana/A/7_mode]
case 3:
both folder exist in dir(but removed 2-3 dashboards from grafana/A location):
same as above
exported files at location grafana/A:
hardikl@hardikl-mac-0 harvest % find grafana/A -name "*.json"
grafana/A/Harvest_2.0/db_netapp_detail_shelf.json
grafana/A/Harvest_2.0/db_netapp_detail_node.json
grafana/A/Harvest_2.0/db_netapp_detail_volume.json
grafana/A/Harvest_2.0/db_netapp_detail_disk.json
grafana/A/Harvest_2.0/db_netapp_detail_snapmirror.json
grafana/A/Harvest_2.0/db_netapp_detail_network.json
grafana/A/Harvest_2.0/db_netapp_detail_volume_details.json
grafana/A/Harvest_2.0/db_netapp_detail_cluster.json
grafana/A/Harvest_2.0/db_netapp_detail_lun.json
grafana/A/Harvest_2.0/db_netapp_detail_aggregate.json
grafana/A/Harvest_2.0/db_netapp_detail_svm_details.json
grafana/A/Harvest_2.0/db_netapp_detail_svm.json
grafana/A/Harvest_2.0/db_netapp_detail_network_with_nvme_fc.json
grafana/A/Harvest_2.0/db_netapp_detail_network_details.json
grafana/A/Harvest_2.0/db_netapp_detail_node_details.json
grafana/A/Harvest_2.0/db_harvest_metadata.json
grafana/A/7_mode/db_netapp_detail_shelf_7_mode.json
grafana/A/7_mode/db_harvest_metadata_7_mode.json
grafana/A/7_mode/db_netapp_detail_volume_7_mode.json
grafana/A/7_mode/db_netapp_detail_disk_7_mode.json
grafana/A/7_mode/db_netapp_detail_cluster_7_mode.json
grafana/A/7_mode/db_netapp_detail_node_7_mode.json
grafana/A/7_mode/db_netapp_detail_network_7_mode.json
grafana/A/7_mode/db_netapp_detail_aggregate_7_mode.json
grafana/A/7_mode/db_netapp_detail_network_with_nvme_fc_7_mode.json
grafana/A/7_mode/db_netapp_detail_lun_7_mode.json
hardikl@hardikl-mac-0 harvest %

Covered panels from details page of volume, node and network and validated against tobago-1 and tobago-2.
Removed panels:
Node fan status
node power status
avg throughput
read write throughput
fcp front drill (5) because fcp_lif not exist
nvme/fc front drill(5) because nvme_lif not exist
throughput by lif
top volume end-to-end qos drilldown(8) because qos_volume_xxx not exist
top volume qos resource latency drilldown(9) because qos_detail_volume_xxx not exist
per volume snapshot space used
per volume snapshot space used perc
top volume fabric pool -> it is empty title
Added panels:
Node uptime
Ethernet port utilization percent
FCP port utilization perc
Ethernet port throughput
avg read latency
avg latency
avg write latency
avg iops
read write latency
read write iops
icsci latency
icsci iops
avg latency by lif
iops by lif
ethernet throuput
per volume space used
per volume space used perc
volumes in cluster
top volume read latency
top volume write latency
top volume read throughput
top volume write throughput
top volume read iops
top volume write iops
updated:
FCP port throughput
fcp throughput
fcp read th  fcp send
fcp write th  fcp receive
No change: (both same)
volume wafl layer - backend wafl drill


Page 30

In chapter 4, in the first paragraph of page 30, at the end of line 5, you mention "in this blog post". I believe this was not intentional for the book?

Fixed. Thanks!


Link to Box resource  not working

On this page:
https://www.carbondesignsystem.com/data-visualization/color-palettes/#categorical-palettes
https://github.com/carbon-design-system/carbon-website/edit/master/src/pages/data-visualization/color-palettes/index.mdx
The link to Resources: "Data visualization color palettes (IBM internal link)" directs to this box link: https://ibm.ent.box.com/s/1rvfetsgovxoj4660suz5sa2tgqizlvy
This link is not accessible to all users.

this link is no longer on the website


Updated: losslesscut 3.17.4

${}

5decfac8-0093-4270-a644-a537c5d931aa

Newer version of losslesscut (3.17.27) is now available in master. 255ea75e80a12dbeca72dd1288bd7686f50c77be


resyncPeriod=0 should imply no resync

Tried to test SharedInformerFactory examples using the blog https://rohaan.medium.com/introduction-to-fabric8-kubernetes-java-client-informer-api-b945082d69af.
When testing with 0 resync period, it is still relisting the updates within seconds.
sharedInformerFactory.sharedIndexInformerFor(
Pod.class,      // POJO for Pod resource
PodList.class,  // POJO for Pod list resource
0 * 1000L);    // resync period
As per definition for ResyncPeriod: if non-zero, will re-list this often (you will get OnUpdate calls, even if nothing changed). Otherwise, re-list will be delayed as long as possible (until the upstream source closes the watch or times out, or you stop the controller). https://github.com/kubernetes/client-go/blob/fb61a7c88cb9f599363919a34b7c54a605455ffc/tools/cache/controller.go#L337

created it under kubernetes-client project https://github.com/fabric8io/kubernetes-client/issues/2651


huge delay with PR review and merges

I noticed that this module seems be maintained for long time (4 months) and there is 22 PRs for review which also contain some critical bug fixes.
What we can do as community to increase velocity of developing and improving this module?

We are the group of @terraform-aws-modules/triage-supporters well aware of this.
The reason is the lack of time from the reviewers' side to read the code, evaluate changes, run it, update examples, documentation, and comment back to the creators if there is anything they can do.
The best that community members can do is to help by reading and answer on issues, suggest closing some of them which are not relevant anymore, and verify that PRs are in good shape.
A couple of months ago we've had Terraform AWS modules Office Hours where we talked about some things related to this - https://www.youtube.com/playlist?list=PLvz1V_9d3uiufsJF6Romw_cyXBCqtNTGn
There was a plan to host such meetings regularly but I don't have time for that myself at the moment.

I tried this approach but without any permissions on repos this seems be useless. Generally speaking community:

cannot tag issues
cannot close issues
cannot manage PRs

From other side community raising a huge amount of great PRs, but because they are not merged in reasonable time community will start abandoning this project.
I understand lack of time, but this is maybe time to open for new supporters and increase strength of maintainers?

In order to bring new supporters on board, we need to make sure that he/she has been helping the project(s) for a while.


The experimental results  of note are inconsistent with the results in this paper

Dear authors,
I have requests on several things.
We run the code in the following environment：
"--model_adaptation_method"——— "note"
"--model_selection_method"——— "last_iterate"
"--model_selection_method"——— "cifar10"
"--model_name"——— "resnet26"
"--episodic"——— "false"
"--data_names"——— ("cifar10_c_deterministic-snow-5;"
"cifar10_c_deterministic-brightness-5;"
"cifar10_c_deterministic-fog-5;"
"cifar10_c_deterministic-frost-5;"
"cifar10_c_deterministic-contrast-5;"
"cifar10_c_deterministic-motion_blur-5;"
"cifar10_c_deterministic-glass_blur-5;"
"cifar10_c_deterministic-zoom_blur-5;"
"cifar10_c_deterministic-gaussian_noise-5;"
"cifar10_c_deterministic-shot_noise-5;"
"cifar10_c_deterministic-jpeg_compression-5;"
"cifar10_c_deterministic-impulse_noise-5;"
"cifar10_c_deterministic-pixelate-5;"
"cifar10_c_deterministic-elastic_transform-5;"
"cifar10_c_deterministic-defocus_blur-5",)
"--batch_size"—— 100
"--lr"—— 1e-4
"--n_train_steps"——— 1
"--inter_domain"———“HomogeneousNoMixture”
The error rate of note is 41%, which is quite different from the result in table 2 "NOTE-online"(24.0 ± 0.1) in this paper. Is this issue caused by the difference between our experimental environment and the setting of the original paper？Or there are other reasons？

Hello,
Thanks for your interest in reproducing our work.
To answer your questions:

Is this issue caused by the difference between our experimental environment

I don't think the small difference in python environment will make such large difference.

the setting of the original paper?

Yes. In order to compare different state-of-the-art TTA methods as fair as possible, for online results we benchmark in the paper, we run with different combinations of lr and n_train_steps, and pick the best one regarding the metrics we used out of all results. Please see more details in scripts like this one we upload in exps folder.

Or there are other reasons？

Yes, please carefully set up the value of hyper-parameters like batch_size and check with scripts we provided in exps folder.
Hope it helps!

Hi, @jiangqinting. Do you have any further feedback on this problem? If you need more help, feel free to contact us.


bug(create entity): every type should have a default "default" value

Given
type: BlueprintAttribute,
attributeType: number,
required: True

instantiating this attribute would return value 0, even if there is no "default" in BlueprintAttribute. 0 is the default default for "number"

They do


dotkernel's add allows escape of reference to stack created data

I ran into a crash while walking through the example code in Visual Studio, and was able to get some help from the VC++ team in tracking it down:
https://github.com/CBaquero/delta-enabled-crdts/blob/master/delta-crdts.cc#L416-L427
       dotkernel<T, K> add(const K& id, const T& val)
       {
              dotkernel<T, K> res;
              // get new dot
              pair<K, int> dot = c.makedot(id);
              // add under new dot
              ds.insert(pair<pair<K, int>, T>(dot, val));
              // make delta
              res.ds.insert(pair<pair<K, int>, T>(dot, val));
              res.c.insertdot(dot);
              return res;
       }

res is created on the stack, which ends up using the stack allocated res.cbase when assigning the reference to res.c in the ctor.
https://github.com/CBaquero/delta-enabled-crdts/blob/master/delta-crdts.cc#L312-L315
  dotkernel() : c(cbase) {}
  // if supplied, use a shared causal context
  dotkernel(dotcontext<K> &jointc) : c(jointc) {}
//  dotkernel(const dotkernel<T,K> &adk) : c(adk.c), ds(adk.ds) {}

Once res is copied by value on return the stack allocated value is destroyed and c is left with a dangling reference and an eventual crash. I'm not proficient enough in C++ to advise on a fix, but figured I'd pass this along.
The crash occurs in ccounter::inc when r.dk joins the result of dk.add or dk.rmv: https://github.com/CBaquero/delta-enabled-crdts/blob/master/delta-crdts.cc#L670-L687
  ccounter<V,K> inc (const V& val=1)
  {
...
    for(const auto & dot : dots)
      r.dk.join(dk.rmv(dot));
    r.dk.join(dk.add(id,base+val));
    return r;
  }

The problem occurs because of dotkernel has a reference field dotcontext and returning res in add function ends in broken (or dangling) reference.
Simple changing from reference to value fixes the problem, but i'm not 100% sure that it preserves the correct semantics of dotkernel. Hope @CBaquero will check and fix it in the right way.


Send message to all users on shutdown

When Twisted is shutting down cleanly, use addSystemEventTrigger("before", "shutdown", self.somecommand) so that we send an announcement to every logged in user.

This didn't work for some reason.

Fixed in 65713ceb31f1a13a873e28f24194b05ece22fb4e.


Update Composer dependencies (2023-09-08-00-12)

Visual regression test passed!
View the visual regression test report


Make compatible with BrainGlobe Atlas API

Currently, atlases are included in the PyNutil package (AMBA CCF and WHS). Atlases could instead be fetched from the BrainGlobe Atlas API. But there are issues regarding atlas orientation that have to be resolved (Nesys tools use atlases in different orientation to the Atlas API). To be discussed.

This is done, though we still need to have a conversation about orientation consistency between tools.


Unable to withdraw or claim Cosmos SDK

Overview
When trying to withdraw from Cosmos SDK, selecting continue gives error "Something went wrong".
Whent trying to claim rewards, it just spins continuously and doesnt progress.
References and additional details
Withdraw: https://jam.dev/c/798b488a-d709-4983-b090-1b1e18700621
Claim: https://jam.dev/c/cc48235b-e65b-4658-9ef0-458baf42cf50
Acceptance Criteria
Should be able to interact with cosmos SDK
Need By Date
No response
Screenshots/Mockups
No response
Ownership

[X] If my bounty needs engineering or needs product I have added the respective labels on the right
[X] As the sponsor of this bounty I will review the changes in a preview environment (ops/product) or review the PR (engineering)

Estimated effort
No response
Sponsor / Stakeholder
No response
Bounty Hunters

Join our discord
Include an expected timeline for you to complete work in the work plan when you apply for this bounty!
Please refer to this link for some basic info
Please do not start work on this issue until you are approved in Gitcoin.

https://github.com/cosmos/gaia/pull/3028
looks like a breaking change last update. no longer self hosting so haven't been paying as close of attention, but looks like I will need to start...

https://github.com/shapeshift/unchained/pull/1010

@MBMaria pushed the backend fix to prod if you can verify on your end when available. I tested in develop and was able to successfully withdraw/claim


Add a .gitignore

Add a .gitignore; general purpose Python from github/gitignore and add an ignorance for gedit backups.

Rebased as https://github.com/ipfs/py-ipfs/pull/10


[feature] Make preprints with deleted nodes viewable via admin [OSF-8951]

Purpose
Deleted preprints be broke on admin.

Changes
There was a bit of django html gore that needed cleaning.

Side effects
na

Ticket
https://openscience.atlassian.net/browse/OSF-8951
QA Notes

View a preprint with a deleted node and test the restore node button.
View a private preprint

Closing in favor of hotfix version (#7928)


implement libra rcnnmask rcnn

I tested it on coco val and I got 41.0 map on bbox and 36.5 map on segm.
While I got 0 on coco test-dev. Could someone tell me why?

Please follow the Error report issue template to provide more information, so that other users or maintainers can help.

@hellock Thanks for you reply. I have solved it. Because I have two versions of the code and I mixed them up.


Remove team/triage and triage milestone from external contributor pr workflow

What does this PR do?

Remove the triage team label and triage milestone from the external contributor PR workflow.
Motivation

Team labels and milestones are now automatically set by other workflows, so we don't need to add the triage ones.
Additional Notes

Possible Drawbacks / Trade-offs

Describe how to test/QA your changes

/merge


SVD Implementation in loftQ Initialization

Thanks for sharing great work! Learned a lot. I have a question regarding SVD implementation in loftQ init.
https://github.com/yxli2123/LoftQ/blob/e6bdef42d0fbc297b18c3e09ec59108aa5c723a8/utils.py#L25-L26
Upon reviewing the code, in the SVD decomposition, I noticed the use of a "reduced SVD" option. (full_matrices=False) I wondering the potential impact of choosing a reduced SVD over a full SVD option in the context of loftQ initialization, especially regarding its effect on the alternating optimization process.
Could you share some insights on whether there are specific advantages or reasons for choosing reduced SVD in this scenario?
Thanks in advance.

Thanks for your inserts of our work. Setting either full_matrices=True or full_matrices=False will not affect the results. For square matrices, they are the same. For non-square matrices, reduced SVD is also the same as full SVD but removes the zero singular vectors. In our work, we are actually using truncated SVD, which only obtain the first r singular vectors.

Thank you for your kind response. I have some additional questions regarding the LoftQ algorithm.
I am struggling to intuitively understand how repeatedly performing quantization and SVD approximation leads to progressively better initialization at adapter weight.
If we rewrite LoftQ Algorithm 1 with an added Error Term, it looks as follows: ($\epsilon$ is a error term)

As in Equation 3, when we approximate the difference between $W_{FP}$ and the $Q_t + A_tB_t$ using SVD, let's say the SVD approximation error is $\epsilon^{svd}_t$.

I have personally measured how this error term ($\epsilon^{svd}_t$) changes across layers with each iteration.
The results show that in all layers, this svd error term decreases as the number of iteration steps increases.
In summary, as the steps in the LoftQ algorithm increase, the SVD approximation becomes more accurate, effectively minimizing the main objective, as stated in eq.6 of the paper. However, I am not entirely clear on why this error minimizes through the repetition of these two steps (1)Quantization 2)SVD). Could you please explain this once more?
I conceptually understand how the initialization of quantized weight and adapter weight are jointly optimized but it is not clear to me why this process minimizes $W_{FP} - Q - AB^T$ analytically. (maybe I miss something)
I would greatly appreciate additional clarification on this, as it would help me deeply understand the core idea of this excellent paper.

Hi @MarsJacobs, the error decreasing as the step increasing is not guaranteed. This algorithm is heuristic. For some models, like some layers in DeBERTa-v3-base, the error fluctuates as steps increases.


Convert ES6 JS files to ES5

Summary
When @glebm converted these files from CoffeeScript to JavaScript, he used ES6. These files break on older browsers like IE 11.
I transpiled them to ES5 using babel.
I think sticking to ES5 is a better solution than adding babel gem dependency complexity

Why do you need to support IE11 in 2019?

IE11 end of support is in Jan 2020

@glebm IE 11 is still at around ~3% usage: https://www.stetic.com/market-share/browser/ https://www.w3counter.com/globalstats.php


⚠ Bofrost.gr has degraded performance

In c556d89, Bofrost.gr (https://www.bofrost.gr) experienced degraded performance:

HTTP code: 200
Response time: 5908 ms

Resolved: Bofrost.gr performance has improved in eb7799f after 1 day, 2 hours, 8 minutes.


Fedora 21 Kernel 4.0.4, empty files via hgfs

Writing files via hgfs results in empty files in the host system. The files and folders are created, but all of them are empty.

This is worse than it might sound - I effectively erased one of my files by editing it :-(
I assume this affects all 4.x kernels. I'm running with 3.19 for now to avoid the problem

Happened to me as well. Luckily it was in a git repo on the host. I remember having had the same issue with some 3.19 version as well, but don't know the exact version anymore.

Updated to VMware Player 7.1.2 build-2780323 (including tools 9.9.3)
Still the same issue.
Writing to a file seems to work inside the guest (Fedora), but the result does never appears in my host (Win).
echo Test > test.txt
cat test.txt # echos Test

The test.txt in Win is empty though.
After reboot the same file is empty in the guest as well.
It looks like some intermediate buffer is never flushed.

Maybe this is related to  #38 somehow.

#39 modified for 9.9.3 solves the issue.

Thanks for pointing that out, I updated to the new patch and it's working fine now.