Add filtering of userlog based on settings

Description

Add filtering of userlog based on settings see. Should be merged after https://github.com/owncloud/ocis/pull/10706
Related Issue

Closes https://github.com/owncloud/ocis/issues/10769

How Has This Been Tested?

test environment: localhost
test case 1: unshare space with user that has in-app notifications for space unshared disabled

Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[x] Breaking change (fix or feature that would cause existing functionality to change)
[ ] Technical debt
[ ] Tests only (no source changes)

Checklist:

[x] Code changes
[x] Unit tests added
[ ] Acceptance tests added
[ ] Documentation ticket raised:

Thanks for the review!
Findings should be fixed @2403905 @kobergj


Release v0.3.3

[ ] on dev

[x] merge all outstanding PRs

[x] #89
[x] #91

[x] ensure the versions have been bumped

[x] run doit preflight:release

[x] ensure CHANGELOG.md is up-to-date
[x]  validate on binder

[x] not running reliably now, due to funding

[x] validate on ReadTheDocs

[x] https://readthedocs.org/projects/ipyforcegraph/builds/20832334/

[x] make a PR from dev to main

[x] https://github.com/jupyrdf/ipyforcegraph/pull/93
[x] https://github.com/jupyrdf/ipyforcegraph/pull/95

[x] wait for a successful build of main

[x] https://github.com/jupyrdf/ipyforcegraph/actions/runs/5093230111

[x] download the dist archive and unpack somewhere
[x] create a new release through the GitHub UI

[x] pick a new release name to go with the version of real (or imaginary) force

[x] Surface

[x] paste in the relevant CHANGELOG.md entries
[x] upload the artifacts

[x] upload distribution to package repositoriescd dist
twine upload *.tar.gz *.whl
npm login
npm publish jupyrdf-jupyter-forcegraph-$VERSION.tgz
npm logout

[x]<EMAIL_ADDRESS>[x] https://pypi.org/project/ipyforcegraph/0.3.3/

[ ] postmortem

[ ] handle conda-forge feedstock tasks

[x] https://github.com/conda-forge/ipyforcegraph-feedstock/pull/7
[x] https://anaconda.org/conda-forge/ipyforcegraph/files?version=0.3.3

[x] create postmortem PR from main targeting dev

[ ] https://github.com/jupyrdf/ipyforcegraph/pull/97
[x] bump to next development version
[x] bump the CACHE_EPOCH
[x] rebuild yarn.lock
[x] rebuild .github/locks

[x] run doit env:lock
[x] run rm -rf .github/locks
[x] from a clean command prompt

[x] 🐧source envs/lock/bin/activate
[ ] 🪟 call envs/lock/Scripts/activate.bat)

[x] run doit lock
[x] commit the new locks

[x] update release procedures with lessons learned in
.github/ISSUE_TEMPLATE/release.md

Remaining tasks on #97


Remove signal-forwarding/timeout thread in c-ares unit test driver

This was originally added back in https://github.com/grpc/grpc/pull/12210 to make sure that run_tests.py-generated timeouts would kill all test child processes and not leave zombies in our test workers.
Now that we use bazel RBE for all C/C++ tests (and all tests run in their own container), this cleanup mechanism shouldn't be necessary.

ios binary size diff: https://github.com/grpc/grpc/issues/25053

ios binary size diff: https://github.com/grpc/grpc/issues/25053


sometimes machines write /etc/current_version before they are ready

According to the code, you have to pass your Puppet run, and your validation checks before writing the /etc/current_version file.
I have occasionally seen that file written even when machines are in a failed validation state. In this case, the machine requires another puppet run to fix itself, but it will not run b/c the file has been written.
In other cases, a machine may be in a functional state, but still need an additional run to configure newly available data from published services.

this fix was merged as #137


Add a panel pop-up for the extension

References user story #15
Add a pop-up to build off of for future UI related features.
Definition of Done

[x] A window opens once the extension activates

Added a window that opens once the extension activates (currently when mail.gmail.com is accessed).
Added minimal formatting and title to the window.
Played around with some tests, but realized the tester needs access to a Gmail account.
I plan to bring this up at our next meeting and talk about possibly incorporating dotenv for environment variables.
Submitted pull request.
[t:180]


Changing simulation parameters and conditions

Greetings Aphros team!
I was trying out the example 205_multivof/clustering and could successfully run it in its default configuration (except for changing the number of processors and mesh resolution). I was trying to change some simulation parameters and conditions and have some queries regarding the same.

How to change the size of the box in which the bubbles are rising, without changing the mesh resolution and other parameters? For example, if I wish to increase the height of the box by 3 times how to do it?
How to change the size of the bubbles? Also, is there a way to change the number of bubble sources?
If we wish to change the boundary conditions from no slip to periodic, how to do the same?
How to change the fluid properties to Non-Newtonian fluid?
If we wish to dump the information like velocity field, volume fraction etc into the output files (.vtk) so that we can visualize using tools like Paraview,  how to do the same? (Some of these data are present in the traj.csv files, but not in the .vtk files which are generated)
Is it possible to directly calculate time-averaged RMS quantities and turbulent energy budget using aphros? If yes, how to do it?
It would be really nice if you could respond to the above queries.
Thank you.

Hi,
The file deploy/scripts/sim_base.conf contains descriptions of configuration parameters along with their default values.

the maximum domain size is set by extent, to make the box three times higher, you need to add to add.conf

set double extent 0.06

and then use make 'm=192 384 192' run
2. the size and number of spawned bubbles is control by file bspawn.dat, so to have three sources with larger bubbles, try
0.015 0.002 0.015 0.002
0.02 0.002 0.015 0.002
0.025 0.002 0.015 0.002

the boundary conditions in x and z are already periodic, as set in std.conf

set int hypre_periodic_x 1
set int hypre_periodic_z 1

non-newtonian would require implementing additional force terms or non-uniform viscosity, which in principle can be done using the hook mechanism as in examples/210_step_hook
the velocity field and volume fraction field can be written to hdf+xdmf files by setting in add.conf

set string dumplist vx vy vz vf

this can also be done using hooks examples/210_step_hook

Thanks a lot for your response! It really helped a lot.

Could you please explain how set extent works?
I am running the example on my local machine before trying it on HPC. On my local machine, I was using 4 processors and  m = 48 32 48 for the original case. To increase the box size by three times I did set double extent 0.06 and make 'm=48  96 48' run.
However, I am getting strange output with 2 boxes one on top of the other and one having almost 3 times more height than the other, with bubbles originating and clustering only in the smaller box. Could you please help to resolve this issue?
Thanks!

seems that you also need to change b.dat, which initializes the volume fraction field with a free surface (as one huge bubble)
the default values are 0 0.02 0 1e5 0.005 1e5, corresponding to x,y,z,rx,ry,rz for an ellipsoid.
so this bubble is supposed to be centered on the domain top,
with extent 0.06, you would need to change b.dat to
0 0.06 0 1e5 0.005 1e5

to put center the bubble at the top

Yeah, it worked perfectly. Thanks a lot!


deployment webhook is broken

What happened:

Installed kueue using the following commands:

IMAGE_REGISTRY=<registry> make  image-local-push deploy

Ran patch command to try out the visibility api

 kubectl patch -n kueue-system deployment kueue-controller-manager --type='json' -p='[

  {
    "op": "add",
    "path": "/spec/template/spec/containers/0/args/-",
    "value": "--feature-gates=VisibilityOnDemand=true"
  }
]'

The error failed with
Error from server (InternalError): Internal error occurred: failed calling webhook "vdeployment.kb.io": failed to call webhook: the server could not find the requested resource

Tried to create busybox deployment, failed with the same error

What you expected to happen:
Create and update calls to deployment should work.
How to reproduce it (as minimally and precisely as possible):

checkout main
run IMAGE_REGISTRY=<registry> make  image-local-push deploy
create or update deployment as noted above

Anything else we need to know?:
This PR #2813 added a validating and mutating webhook for deployments, but it is not registered by default
Environment:

Kubernetes version (use kubectl version): tested in 1.30.3 and 1.31.0
Kueue version (use git describe --tags --dirty --always): main at commit  0bcde8c82e6a769bf75e3d195b65d18dbb6e2bf6
Cloud provider or hardware configuration:
OS (e.g: cat /etc/os-release):
Kernel (e.g. uname -a):
Install tools:
Others:

/assign

It seems like importing deployment https://github.com/kubernetes-sigs/kueue/blob/main/pkg/controller/jobs/jobs.go#L28 should solve the issue.
Trying it out in local environment

diff --git a/config/components/manager/controller_manager_config.yaml b/config/components/manager/controller_manager_config.yaml
index c0a9f597..9850c3fa 100644
--- a/config/components/manager/controller_manager_config.yaml
+++ b/config/components/manager/controller_manager_config.yaml
@@ -48,15 +48,16 @@ integrations:
   - "kubeflow.org/pytorchjob"
   - "kubeflow.org/tfjob"
   - "kubeflow.org/xgboostjob"
-#  - "pod"
+  - "pod"
+  - "deployment"
 #  externalFrameworks:
 #  - "Foo.v1.example.com"
-#  podOptions:
-#    namespaceSelector:
-#      matchExpressions:
-#        - key: kubernetes.io/metadata.name
-#          operator: NotIn
-#          values: [ kube-system, kueue-system ]
+  podOptions:
+    namespaceSelector:
+      matchExpressions:
+        - key: kubernetes.io/metadata.name
+          operator: NotIn
+          values: [ kube-system, kueue-system ]

enabling the above configuration made it work for me.
# kubectl patch -n kueue-system deployment kueue-controller-manager --type='json' -p='[
  {
    "op": "add",
    "path": "/spec/template/spec/containers/0/args/-",
    "value": "--feature-gates=VisibilityOnDemand=true"
  }
]'
deployment.apps/kueue-controller-manager patched

So either the pod framework should be enabled or webhook configuration should be disable, one or the other should solve this issue in main branch.

/cc @vladikkuzn

The original intention was to enforce that the pod integration is enabled. From https://github.com/kubernetes-sigs/kueue/issues/2717#issue-2435374397: "introduce a dedicated Deployment integration, and validate that it can only be enabled when pod integration is enabled".
Here was the preparatory PR: https://github.com/kubernetes-sigs/kueue/pull/2768. However, I'm not sure if the mechanism was eventually used. Do you know @vladikkuzn @trasc ?
@alaypatel07 would enforcing the dependency solve this issue for you?


Using $state.go does not work

I have a directive as following (don't mind the JSX):
.directive('messageButton', ['Components', '$state', function (Components, $state) {
		return {
			scope: {
				user: '@',
				isContacted: '@'
			},
			replace: true,
			templateUrl: '/views/directives/Profile/message.html',
			link: function (scope) {
				scope.click = function () {
					if (scope.isContacted) {
						$state.go('messages.chat', {id: scope.isContacted});
					} else {
						Modals.create(<Components.Modal.Message user={scope.user} />);
					}
				};
			}
		};
	}])

but the transition does not happen. When I use only messages as a state, transition occurs.

Problem was in value scope.isContacted. State expects integer, so I had to cast the value to Number.


Cannot create new controller mapping profiles from the inspector

XRTK - Mixed Reality Toolkit Bug Report
Describe the bug
As you can see from the screenshot below, you can only assign mapping profiles in the controller mapping inspector. This is not inline with the capabilities on other areas where a profile can be selected, as each also has a "create" button

Controller Mappings

Input Configuration Profile

It should be standard where a profile is required that you can create one from the inspector as well as the project view.

This was by design

There's no way to specify the type of profile you'd need because the whole list is serialized as BaseControllerMapping profiles

I think I figured out a way to do this by adding a instance type drawer dropdown, selecting the type you want to create, then pressing the "Add new mapping" button which will then create it.

I want to add this to 0.1.32 as well

I thought you resolved this in another PR?

Nope, this has it's own inspector that does specific things.

I want to add hands to 0.1.32 as well, so meh :D

We technically can't bc of the breaking changes in the SDK


Enable type-safe project dependencies

Issue

close #ISSUE_NUMBER

Overview (Required)

I tried to enable the feature preview function.

Links

https://docs.gradle.org/7.0/userguide/declaring_dependencies.html#sec:type-safe-project-accessors

Screenshot

Before
After

👀


Test local file links in PR review comments

Refs: https://github.com/microsoft/vscode-pull-request-github/issues/4569

[ ] anyOS @justschen
[ ] anyOS @ntrogh

Complexity: 2
Create Issue

Install the pre-release version of GitHub Pull Requests and Issues
Open a clone of a GitHub repo in VS Code. Check out a PR.
Open a file from the repo. Select some lines and use the "Copy Permalink" command to create a permalink.
Open a file that's in the PR and leave a comment. Paste your permalink into the comment.
Verify that when you save the comment it shows a link for the file. Verify that if you click on the link it takes you to the local file. Verify that there's an option to open the file on github.com. Verify that opening the file on github.com works.

testing with https://github.com/Yoyokrazy/clean-nb-imports-ext/pull/7
path was this:

lgtm!


deb: Use custom install script instead of dh-exec

dh-exec has some limitations that we can't really get around. The immediate need is it can't copy a directory to a new name in the target location.
As such we need more flexibility in how we set things up, so this switches to bash so we can have the power that we need.
Should resolve the issue with CI in #385

Merged as part of #385


Fix DataTabDataContextTests

After refactoring PROSE to service hub, many DataTabDataContext tests are broken. I commented them out to checked in so we can bash, but they need to be fixed.

Build passing confirms that tests are fixed.


Blazor API Review: RenderTreeBuilder

Summary
RenderTreeBuilder is a low level API used by the compiler for .razor components, and used in expert scenarios for C# components.
It's critical that we get the design of the RenderTreeBuilder and its methods right, because there's no conceivable way we could change anything here. It's always possible for us to add however, and we don't generally need to optimize for simplicity or clear names.
APIs
namespace Microsoft.AspNetCore.Components.RenderTree
{
    public partial class RenderTreeBuilder : System.IDisposable
    {
        public const string ChildContent = "ChildContent";
        public RenderTreeBuilder(Microsoft.AspNetCore.Components.Rendering.Renderer renderer) { }
        public void AddAttribute(int sequence, in Microsoft.AspNetCore.Components.RenderTree.RenderTreeFrame frame) { }
        public void AddAttribute(int sequence, string name, Microsoft.AspNetCore.Components.EventCallback value) { }
        public void AddAttribute(int sequence, string name, System.Action value) { }
        public void AddAttribute(int sequence, string name, bool value) { }
        public void AddAttribute(int sequence, string name, System.Func<System.Threading.Tasks.Task> value) { }
        public void AddAttribute(int sequence, string name, System.MulticastDelegate value) { }
        public void AddAttribute(int sequence, string name, object value) { }
        public void AddAttribute(int sequence, string name, string value) { }
        public void AddAttribute<T>(int sequence, string name, Microsoft.AspNetCore.Components.EventCallback<T> value) { }
        public void AddComponentReferenceCapture(int sequence, System.Action<object> componentReferenceCaptureAction) { }
        public void AddContent(int sequence, Microsoft.AspNetCore.Components.MarkupString markupContent) { }
        public void AddContent(int sequence, Microsoft.AspNetCore.Components.RenderFragment fragment) { }
        public void AddContent(int sequence, object textContent) { }
        public void AddContent(int sequence, string textContent) { }
        public void AddContent<T>(int sequence, Microsoft.AspNetCore.Components.RenderFragment<T> fragment, T value) { }
        public void AddElementReferenceCapture(int sequence, System.Action<Microsoft.AspNetCore.Components.ElementReference> elementReferenceCaptureAction) { }
        public void AddMarkupContent(int sequence, string markupContent) { }
        public void AddMultipleAttributes(int sequence, System.Collections.Generic.IEnumerable<System.Collections.Generic.KeyValuePair<string, object>> attributes) { }
        public void Clear() { }
        public void CloseComponent() { }
        public void CloseElement() { }
        public Microsoft.AspNetCore.Components.RenderTree.ArrayRange<Microsoft.AspNetCore.Components.RenderTree.RenderTreeFrame> GetFrames() { throw null; }
        public void OpenComponent(int sequence, System.Type componentType) { }
        public void OpenComponent<TComponent>(int sequence) where TComponent : Microsoft.AspNetCore.Components.IComponent { }
        public void OpenElement(int sequence, string elementName) { }
        public void SetKey(object value) { }
        public void SetUpdatesAttributeName(string updatesAttributeName) { }
        void System.IDisposable.Dispose() { }
    }
}

The naming here follows a general pattern - we should make sure we think this is right:

There are methods for appending a single item Add...
There are methods for opening closing a scoped construct Open.../Close...
There are methods for modifying the current frame Set...

This seems like a reasonable naming structure. Outliers:

Clear and GetFrames for getting the result and resetting
Dispose used to return memory to the pool and it's optional to call

Some suggestions for improvement:

[ ] Make it sealed
[ ] Remove the constructor (it doesn't need the renderer)
[ ] Remove AddAttribute(int sequence, string name, System.Action value) and AddAttribute(int sequence, string name, System.Func<System.Threading.Tasks.Task> value) (unused)

The justification for the last one is that the compiler does something more sophisticated now. Removing this API doesn't block us from using delegates, they will go through AddAttribute(int sequence, string name, System.MulticastDelegate value).

@SteveSandersonMS

All the suggestions sound good to me.

One other topic - is RenderTree a good namespace for this to live in forever? Right now what's there is all of the actual render frame types, which we want to discourage people from using. Rendering would be a better namespace.

Namespace RenderTree->Rendering makes sense. I would totally endorse that.

Updated to .NET Core 3.0 Preview 7 & now getting following errors in my .razor pages.  Not sure if related to this issue or not:
Severity	Code	Description	Project	File	Line	Suppression State
Error	CS1061	'RenderTreeBuilder' does not contain a definition for 'SetUpdatesAttributeName' and no accessible extension method 'SetUpdatesAttributeName' accepting a first argument of type 'RenderTreeBuilder' could be found (are you missing a using directive or an assembly reference?)

Following up on the namespace part separately.


Provider children error after updating

I've updating redux, reat-redux and react on my project and now, this:
var tmp = React.createElement(myproject_view_Application.Reduxed,{ });
ReactDOM.render(React.createElement(Provider,{ store : store},tmp,"\t"),win.document.querySelector("#app"));

throws:
Warning: Failed prop type: Invalid prop `children` of type `array` supplied to `Provider`, expected a single ReactElement.
Uncaught Error: React.Children.only expected to receive a single React element child.(…)

I do not understand as I correctly give a sigle child to my Provider component... This was working with react 15.1.0 and react-redux 4.4.5.
I'm having this issue with react 15.4.1 and react-redux 4.4.6.

You're passing tmp and "\t" as children to Provider. Provider expects a single child. Get rid of the second one.


Exceptionally SapiEmitter is allowed to call emit with 2nd arguments

Exceptionally SapiEmitter is allowed to call emit with 2nd arguments - bufferLevel

EmitterInterface defines only 1st arguments

To fix non-consistentcy method arguments in Server::listen() #233

Closing in favor of #233.


set node docker container to 3.18

node:22-alpine-3.19 was released yesterday and
causes our builds to fail. Reverting to last
working version 3.18.

closed for #1121


planned support for ClusterIssuer ?

Hello .
Is there any support or planned support for ClusterIssuer  kind ?
We're looking to send requests from different namespaces without deploying the  OriginIssuer and key in each namespace and wonder if this will be supported .
Thanks .

Duplicate of #24. Planned, but not yet implemented.


Autodoc on ReadTheDocs is ignoring 3rd party modules, but locally Autodoc works fine

A local installation of CanAction allows the documentation to be built fine.
$ cd /path/to/ConAction/docs
$ make clean
$ make html

And the ReadTheDocs build says it is successful. But Autodoc is failing to see the third party packages. Details about functions are not being rendered.

I have opened a support request on the autodoc website.

Related:

https://stackoverflow.com/questions/65487163/python-sphinx-autodoc-not-rendering-on-readthedocs
https://docs.readthedocs.io/en/stable/guides/reproducible-builds.html#specifying-a-requirements-file

Try creating a .readthedocs.yaml configuration file as per the documentation above and a docs/requirements.txt with
python:
  install:
    - requirements: docs/requirements.txt

Making a suitable .readthedocs.yaml and /docs/requirements.txt did the trick.


FreeBSD Support

It would be great if we could add support for FreeBSD

@syepes Do you mean for pre-compiled binaries or a package you could install? Telegraf should compile on FreeBSD, afaik

I was thinking more that the system/net and zfs plugins be able to collect there info from fBSD.

Could you be more specific about what errors you are seeing in those plugins?

Currently, ZFS plugin does not work on fBSD

FreeBSD Build log failure:
# gmake
go get github.com/tools/godep
/opt/go/bin/godep go build -o telegraf -ldflags \
        "-X main.Version=v0.2.0-52-g68ef07b" \
        ./cmd/telegraf/telegraf.go
# github.com/cloudfoundry/gosigar
Godeps/_workspace/src/github.com/cloudfoundry/gosigar/concrete_sigar.go:20: cpuUsage.Get undefined (type Cpu has no field or method Get)
Godeps/_workspace/src/github.com/cloudfoundry/gosigar/concrete_sigar.go:30: cpuUsage.Get undefined (type Cpu has no field or method Get)
Godeps/_workspace/src/github.com/cloudfoundry/gosigar/concrete_sigar.go:49: l.Get undefined (type LoadAverage has no field or method Get)
Godeps/_workspace/src/github.com/cloudfoundry/gosigar/concrete_sigar.go:55: m.Get undefined (type Mem has no field or method Get)
Godeps/_workspace/src/github.com/cloudfoundry/gosigar/concrete_sigar.go:61: s.Get undefined (type Swap has no field or method Get)
Godeps/_workspace/src/github.com/cloudfoundry/gosigar/sigar_unix.go:23: cannot use stat.Ffree (type int64) as type uint64 in assignment
# github.com/fsouza/go-dockerclient/external/github.com/Sirupsen/logrus
Godeps/_workspace/src/github.com/fsouza/go-dockerclient/external/github.com/Sirupsen/logrus/terminal_freebsd.go:10: ioctlReadTermios redeclared in this block
        previous declaration at Godeps/_workspace/src/github.com/fsouza/go-dockerclient/external/github.com/Sirupsen/logrus/terminal_bsd.go:7
Godeps/_workspace/src/github.com/fsouza/go-dockerclient/external/github.com/Sirupsen/logrus/terminal_freebsd.go:12: Termios redeclared in this block
        previous declaration at Godeps/_workspace/src/github.com/fsouza/go-dockerclient/external/github.com/Sirupsen/logrus/terminal_bsd.go:9
godep: go exit status 2
Makefile:9: recipe for target 'build' failed
gmake: *** [build] Error 1

# go version
go version go1.5.1 freebsd/amd64

# uname -a
FreeBSD node 10.2-STABLE FreeBSD 10.2-STABLE #11 r289763: Thu Oct 22 23:30:25 CEST 2015 node:/usr/obj/usr/src/sys/GENERIC  amd64

That is due to the fact that the dependency gosigar has no FreeBSD support.
It is mainly using the proc filesystem to parse cpu stats which in FreeBSD is not available.
You probably want to extend gosigar to support FreeBSD in the first place which would mean getting a sigar_freebsd.go in there that implements the missing bits of all those types - mainly all the Get methods.
If you take sigar_linux.go as a source and reimplement the stat gathering for the FreeBSD world you would be good.

I think it would be more simple to just remove the go-sigar dependency and replace it with gopsutil. gosigar is a project that doesn't often respond to PRs, and I think you even have to send in a snail-mail CLA agreement

@sparrc since gopsutil is already a dependency for other stuff this seems to be a good way.
There still is the termios problem in the logrus code but @Sirupsen is very responsive so that problem might be easily solved.

Turns out it already is fixed in logrus just the stored version of go-dockerclient still had a broken version.
A simple bump of github.com/fsouza/go-dockerclient via godep did the trick.
PR #372 should fix compilation on FreeBSD

fixed by https://github.com/influxdb/telegraf/pull/372

@syepes @cornerot FYI: Telegraf now support ZFS on FreeBSD since #1224.


copy right footer is added

🛠 Fixes Issue #1054

👨💻 Changes proposed and Brief Description

✅ Check List (Check all the applicable boxes)

[x] My code doesn't break any part of the project
[x] This PR does not contain plagiarized content.
[x] My Addition/Changes works properly and matches the overall repo pattern.
[x] The title of my pull request is a short description of the requested changes.

📄 Note to reviewers

📷 Screenshots

@swapnilsparsh have a look.


Fix printing the help for different entrypoints

Codecov Report

Merging #366 (ebc5ef1) into main (04f16c8) will increase coverage by 0.00%.
The diff coverage is 100.00%.

:exclamation: Current head ebc5ef1 differs from pull request most recent head b7a7b9f. Consider uploading reports for the commit b7a7b9f to get more accurate results

@@           Coverage Diff           @@
##             main     #366   +/-   ##
=======================================
  Coverage   97.61%   97.61%
=======================================
  Files          44       44
  Lines        3557     3558    +1
=======================================
+ Hits         3472     3473    +1
  Misses         85       85

Impacted Files
Coverage Δ

robotidy/cli.py
98.28% <100.00%> (+<0.01%)
:arrow_up:

Continue to review full report at Codecov.

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


Create / Save button should be at the bottom of the Create / Edit Event page

https://goo.gl/mi5zFr
As I was scrolling down the page to create an event, I got to the bottom of the page and panicked a bit that there was no 'Save' button on the page. After a few moments of panic, I scrolled up to the top of the page and found the save button squished on the top edge of the page.
I would like to have these buttons at the bottom of the page so I can save when I get to the end of the page.

Looking through that page, the markup isn't quite correct. There are column specified containers without being nested in row specified containers. I've got a fix locally that I'll raise a PR for this evening.


generate a csv for the comparing results/feature importance analysis results

can be extra files of the comparing result html

completed by #16


Broken Link to examples

The link to Unreal - Rive examples files is broken. Getting 404 error.
On this page: https://github.com/rive-app/rive-unreal
This page throws the error: https://github.com/rive-app/rive-unreal-examples

Good catch! Thank you. Fixing now. Our newer demos are at https://github.com/rive-app/rive-unreal-demos


WSGI headers with accented characters are not passed to the app

Hello,
I am using nginx + granian to serve my app but I found that a headers value containing an accent is not passed to the app:
search_term: levé
Python 3.11.9
Ubuntu 22.04
Flask 2.3.2
Granian 1.4.0
My command in systemd
/api/venv/bin/granian --host <IP_ADDRESS> --port 8000 --no-ws --interface wsgi --workers 1 --threads 8 run_wsgi:app*
Then the nginx has a proxy_pass to http://<IP_ADDRESS>:8000
When using gunicorn, the headers is passed correctly
Edit: Tested with 1.4.4 and same issue occurs

@Kumzy can you please provide a MRE including the request sent to the server?

Also, AFAIK the HTTP spec only allows ASCII characters in headers, and é it is not.. 🤔

Sorry I did not have time to create a MRE yet, it just that it's working with gunicorn. Maybe it's not allowed in the value of the headers, I did not check that

So, per spec (https://www.rfc-editor.org/rfc/rfc7230#section-3.2.4):

Historically, HTTP has allowed field content with text in the
ISO-8859-1 charset [ISO-8859-1], supporting other charsets only
through use of [RFC2047] encoding.  In practice, most HTTP header
field values use only a subset of the US-ASCII charset [USASCII].
Newly defined header fields SHOULD limit their field values to
US-ASCII octets.  A recipient SHOULD treat other octets in field
content (obs-text) as opaque data.

Thus, I don't think Granian should support non-ASCII characters decoding in WSGI protocol.
I'm closing this, feel free to open up a discussion about encoding support in comparison to other servers, and we'll se where that discussion land.

Yes, thank you. I will try to implement method to encode value correctly in my headers.


Removing the redfish_1.0 group from the CIT smoke-test suite.

This will stop it from running as part of the PR gate.
The redfish scripts have been convert to the FIT format and exist in the directory /test/tests/api-cit/redfish_1.0 and are running as part of the PR gate under the 'FIT' bubble.

At what point are these CIT tests going to be removed from source?

@panpan0000 @brianparry @johren @derrickostertag @larry-dean @manfrednde


ARROW-18056: [Ruby] Add support for building Arrow::Table from {name: Arrow::Tensor}

New #to_arrow_array protocol is also introduced.

@mrkn What do you think about this approach?


Error

Getting error 500

Thank you for reporting this. I assume you meant gutendex.com rather than a self-hosted server, because there has been intermittent downtime on the gutendex.com server lately, maybe due to high traffic. I have now added an automatic restart script which I expect to reduce the durations of downtime. Please let me know if you experience another error lasting more than a couple of minutes.


feat(legacy-plugin-chart-pivot-table): add support for timestamp format

🏆 Enhancements
This adds support for formatted dates on the row or column headers on pivot-table. This is done by prefixing date values with __timestamp:, after which they can be identified and parsed into formattable date objects. In addition sorting is done based on the epoch value, meaning that the format won't affect the sorting order. Other changes:

Add date format
Move visual options to own tab (currently on Query pane)
make sorting of numeric values based on the parsed float value, not the text value.

AFTER:

BEFORE:

Thanks for your reviews @ktmud and @rusackas ! <3

Oh, one more thing @ktmud and @rusackas . Currently the sorting carets are broken (displays a black box, see the screenshots). I wasn't sure how to fix this, do you guys know how to make the icon work properly?

Thanks @kristw , I'll update accordingly 👍

Oh, one more thing @ktmud and @rusackas . Currently the sorting carets are broken (displays a black box, see the screenshots). I wasn't sure how to fix this, do you guys know how to make the icon work properly?

I used react-icons in the table chart. https://github.com/apache-superset/superset-ui/blob/d323ce86dd7000e9b65a2a7d6b861d713616701b/plugins/plugin-chart-table/src/TableChart.tsx#L91-L98
In the future we should probably move the SVG icons from superset-frontend to superset-ui so they can be reused by visualizations.

I used react-icons in the table chart.
https://github.com/apache-superset/superset-ui/blob/d323ce86dd7000e9b65a2a7d6b861d713616701b/plugins/plugin-chart-table/src/TableChart.tsx#L91-L98
In the future we should probably move the SVG icons from superset-frontend to superset-ui so they can be reused by visualizations.

@ktmud I was unsure how to apply this snippet to this code, as it doesn't seem to be natively React. Perhaps it's vest if we merge this as-is and leave this fix for later?

@ktmud I was unsure how to apply this snippet to this code, as it doesn't seem to be natively React. Perhaps it's best if we merge this as-is and leave this fix for later?

Sounds good


Is there a way to use Microsoft.UI.Xaml in a Visual Studio 2022 extension

I'm writing a Visual Studio extension that has multiple async windows. I came across the NuGet package Microsoft.UI.Xaml which provides a lot of well-made custom controls that blend well with Visual Studio.
The problem is upon installation the extension supposes that you will run it in a standalone WPF application and tells you (like in the docs:

Don't forget to set XamlControlsResources as your Application
resources in App.xaml:
<Application>
    <Application.Resources>
        <XamlControlsResources xmlns="using:Microsoft.UI.Xaml.Controls" />
    </Application.Resources>
</Application>

If you have other resources, then we recommend you add those to the
XamlControlsResources' MergedDictionaries. This works with the
platform's resource system to allow overrides of the
XamlControlsResources resources.

I used Extensibility Essentials 2022 to start a "VSIX Project w/Tool Window (Cummunity)" project and the project structure came as follows:
│   VSIXProject1.sln
│
└───VSIXProject1
    │   source.extension.cs
    │   source.extension.vsixmanifest
    │   VSCommandTable.cs
    │   VSCommandTable.vsct
    │   VSIXProject1.csproj
    │   VSIXProject1Package.cs
    │
    ├───Commands
    │       MyToolWindowCommand.cs
    │
    ├───Properties
    │       AssemblyInfo.cs
    │
    ├───Resources
    │       Icon.png
    │
    └───ToolWindows
            MyToolWindow.cs
            MyToolWindowControl.xaml
            MyToolWindowControl.xaml.cs

Can anyone point me in the right direction as to how to use the Microsoft.UI.Xaml library

As a start, I would switch to using the WinUI 3 inside WinAppSDK instead of the WinUI 2 nuget package. That said, this is not a common scenario for us or one that we are currently targeting.


Unnecessary | undefined in signature help with optional parameter

TypeScript Version: 3.0.0-dev.20180601
Code
/// <reference path='fourslash.ts' />
// @strictNullChecks: true

////function f(x?: number): void {}
////f(/**/)

verify.signatureHelp({ marker: [""], text: "f(x?: number): void" });

Expected behavior:
Test passes.
Actual behavior:
Signature help is f(x?: number | undefined): void.

This is consistent with other places int he type system.. e.g. quick info on optional properties.
the type does include undefined in it.


Expose ConversionError type using exported method

Why:
All the exported error types in models/errors.go depend on models.simpleError type which is non-exported and therefore the exported error types are not usable unless invoked from the same package or if the errors.go is copied over the other specific package.
What:
Added method to access the non-exported methods.
This is an additional sub-task which was missed when https://github.com/almighty/almighty-core/commit/bf4f6bc40233a2311220e7266d078fb9b20d7699 when merged.
Fixes #309

Current coverage is 64.53% (diff: 100%)

Merging #423 into master will increase coverage by 0.03%

@@             master       #423   diff @@
==========================================
  Files            44         44
  Lines          1907       1909     +2
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
+ Hits           1230       1232     +2
  Misses          550        550
  Partials        127        127

Powered by Codecov. Last update 99878df...4d7b5be

Hi @kwk Could you please review and approve this? This is a tiny ( missed ) change , a part of which is already in master. Would need this for consumption in #395

[test]


libkbfs: add more debugging for "cannot open secret box" error

Trying to narrow down the error path for the secret box error experienced by a user.
(The user is willing to run the Linux nightly build to get us more info on a broken TLF.)
Issue: KBFS-4181

@keybase/kbfs-hackers Any chance someone could give me a quick thumb on this debugging before 9 am? I'd like to get it into the Linux nightly to help a user.

Thanks!


Add the ability to only show merge commits

Started from #1100, created by @tabuchid :+1:

@asfalcone Yeah. I think what you're describing would be a valuable addition to the FastlaneCore::ConfigItem API. Do you think it's worth it to be more noisy about it here in the absence of a standardized way?

@mfurtak Yea I'd want it to be noisy at the point of use and we can replace whatever we decide to do here with a future, more holistic solution.

LGTM :+1: Squash before committing!

Thanks for the contribution @tabuchid! :tada:


goreleaser improvements

changelog to use github as source, pre-release suppose and discussions creation

does this mean it will use PR titles/links rather than commits?


how can i use less in nuxt?

as the title, i hope to use less in nuxt , but when i set lang to less the nuxt tell me that,
`This dependency was not found:

!!vue-style-loader!css-loader!../node_modules/._vue-loader@11.3.4@vue-loader/lib/style-compiler/index?{"id":"data-v-b155f86e","scoped":false,"hasInlineConfig":true}!less-loader!../node_modules/._vue-loader@11.3.4@vue-loader/lib/selector?type=styles&index=0!./index.vue in ./pages/index.vue

To install it, you can run: npm install --save !!vue-style-loader!css-loader!../node_modules/._vue-loader@11.3.4@vue-loader/lib/style-compiler/index?{"id":"data-v-b155f86e","scoped":false,"hasInlineConfig":true}!less-loader!../node_modules/._vue-loader@11.3.4@vue-loader/lib/selector?type=styles&index=0!./index.vue
`
but when i install vue-style-load & css-loader , it does not work either, hope to fix it as soon, thanks!

You need to install less-loader and less first
npm i less less-loader --save-dev

thanks @stbaer

Should add it to the document ?

@langgo I think some notes about sass-loader exists in docs. Would be nice if having both :)

You need to install less-loader and less first
npm i less less-loader --save-dev

thank you very much!

But ... why do use save it as dev dependencies ?
It's not a package "for developers", like a linter, it's a part of the build process, and if you run your project with NODE_ENV=production npm install it will fail without these packages


Update qdrant interface

Hello

Passing embedding_function as a callable seems to be outdated and the common interface is to pass Embeddings instance

At the moment Qdrant.add_texts is designed to be used with embeddings.embed_query, which is 1) slow 2) causes ambiguity due to 1.
It should be used with embeddings.embed_documents

This PR solves both problems and also provides some new tests

Hi, @hwchase17
Great, thanks
I’ve just fixed linter complaints, it should work now


Turbo segfaults on vGPUs that don't support Unified Memory (Managed Memory)

There is a significant limitation when running Turbo on a virtualized GPU (vGPU): The GPU has no access to Unified Memory.  This is because the NVIDIA GRID hypervisor does not support Unified Memory in many situations.

2.10 Unified Memory Support
Unified memory is a single memory address space that is accessible from
any CPU or GPU in a system. It creates a pool of managed memory that is
shared between the CPU and GPU to provide a simple way to allocate and
access data that can be used by code running on any CPU or GPU in the system.
Unified memory is supported only on a subset of vGPUs and guest OS releases...
Only time-sliced vGPUs that are allocated all of the physical GPU's
frame buffer on physical GPUs that support unified memory are supported.
Linux only. Unified memory is not supported on Windows.
When unified memory is enabled for a VM, vGPU migration is disabled
for the VM.

This issue is related to #16.
The problem is that battery's call to cudaMallocManaged does not check for cudaErrorNotSupported so it segfaults.
Major projects like PyTorch have a conditional runtime switch to run with or without UM.
I have a pull-request that ports Turbo to Windows, but I can't test it on Azure's HCI because of the UM limitation.
I have since updated my proposed PR to add a new runtime option to turn off UM (-gpu-opt no-um). It checks at runtime if the GPU supports UM (cudaDevAttrManagedMemory, cudaDevAttrConcurrentManagedAccess) to set the option implicitly. I have not yet hooked it into gpu_solving.hpp.  There is a clean division between kernel and non-kernel code in the solver, so it looks doable. I think the trick might involve inventing a new kind of shared_ptr where the .get() moves the memory to/from the GPU (.getdev() and .gethost()).
I plan on tackling it in a few days.  It should fix #16 too.
I'm stuck right now because main is broken https://github.com/lattice-land/lala-core/issues/6

Thanks for raising this issue, I wasn't aware that in some (recent) settings UM is not available.
But without UM, it's going to be quite difficult, here some of the things to take into account:

There is a producer/consumer between CPU and GPU using atomics so we print the solutions on the CPU. The reason is that, for some problems, printing directly from the GPU was too slow.
The timeout is also handled on the CPU side and communicated through the GridData::cpu_stop Boolean variable.
Even if you port the timeout to the GPU side (which seems to be possible), cpu_stop is also used for CTRL-C cancellation.

With cuda_battery, and in all lattice-land libraries, I have worked to make the code both executable from the CPU and GPU, and avoid methods like getdev or gethost. Normally you don't need that. I exclusively rely on the allocator type to know where to allocate. The issue you are going to face is to transfer all the data structures from the CPU to the GPU without UM. I guess we would need to modify the data structures in cuda-battery (vector, shared_ptr, ...) to support copying memory from a CPU standard_allocator to a GPU global_allocator, but that means using the CUDA API cudaMemcpy and the like, which are byte-copy and do not care about objects. Unless there is an easy mechanism (other than UM) to copy abritrary data structures (with array and pointers) that I'm not aware of?
I have no problem supporting Windows.
For non-UM support, it would make things less flexible, which might not be a good thing, especially since it's an early development stage. Not sure if the Azura HCI use-case is worth the pain (yet).


Implemented issues #21, #33, #35, #51, #55, and #56

I believe this was accidentially closed without merging. You should reopen the PR and then "merge and close".

Yes, thanks


Python version 3.8 and above - changes to multiprocessing

Default for multiprocessing on Mac OSX changes to spawn from version 3.8: https://docs.python.org/3/library/multiprocessing.html. Spawn also works on Unix and Windows. We should update the code to using spawn and shared_memory wherever multiprocessing is employed. Seems to be mash.py, sketchlib.py, refine.py and utils.py. The lineage_clustering.py file on the relevant branch (e.g. f9645039f303100a3987fa845ec47f2e605914fb) already uses spawn.

Replaced sharedmem with multiprocessing in refine.py in 1fef55f805348427e03b3c5c2269505dfe38dea3 in branch https://github.com/johnlees/PopPUNK/tree/py38.

Still a problem in mash.py at least unfortunately.

#76 includes my attempt at mash.py on top of your changes, will see if I can get it to pass the tests

Looks like the distMat is returned as all zeroes following the fitKmerBlock pool run.

Right, forgot to copy it back at the end

Afriad not, even distances_shared is/was returning zeros when printed - but printing within fitKmerBlock suggests the values in there are being edited. Just not being returned to the parent function.

Right, it's at least getting to that test which is failing (so they're not totally useless!). Not sure why this is – by my reading of the sharedmem docs was that writing should be fine too. Was your understanding that this would be a problem?

I had a vague memory that it was read-only, but I am pretty sure that is wrong. Though it is strange that trying to access the buffer (shm_distMat.buf) directly after the pool.map call results in a segfault 11.

Abandoned memory manager for sharing of distMat and it now seems to be writeable in ddfd0e2eef2cadf1e925e938babcd0ccccdef976. I am not sure I trust the shared memory managers.

I did a bit of investigation. memory manager is fine, it's basically just a wrapper around a SharedMemory that doesn't let you name the object (but you can still get the name out of the object). I still like it as it does the deleting for you which feels more pythonic.
The problem was what was being passed to and from the functions in my changes. If you just pass an array it will still be copied when the function is called. This works fine for reading, though doesn't at all achieve any of the purpose of shared memory, and explains why writes don't work as it's not passed by reference. So your original method was correct, and I had misunderstood the docs (which do only show passing of a sharedmemory object, not an array).
I've slightly rewritten it to pass a tuple instead of each sharedmemory parameter, and also correct my error in refine.py

Great, thanks - my attitude to the memory managers was purely emotional at this point. Latest commit to master works for my local tests now.


License dialog text is not shown correctly

About this issue
The dialog text is cut off for me. I am utilizing the legacy UI fragment on Android.
        val fragment = LibsBuilder()
            .withVersionShown(true)
            .withLicenseShown(true)
            .withLicenseDialog(true)
            .supportFragment()

        supportFragmentManager.beginTransaction().apply {
            replace(R.id.fragment_container, fragment)
        }.commit()

The provided screenshots show the start of the text (cannot scroll upwards) and that scrolling downwards is possible, but no text is shown.

Details

[x] Used library version - 10.10.0
[ ] Used support library version
[ ] Used gradle build tools version - 8.3.0-rc01
[x] Used tooling / Android Studio version - Android Studio Iguana | 2023.2.1 RC 1
[ ] Other used libraries, potential conflicting libraries

Checklist

[x] Searched for similar issues
[x] Checked out the sample application
[x] Read the README
[x] Checked out the CHANGELOG
[x] Read the MIGRATION GUIDE

@LethalMaus thank you for the report.
Can you reproduce this in the sample app? I just tried to see if the same happens in the FragmentActivity, and it doesn't appear to be the case.
I also notice the dialog has a different corner radius than the sample 🤔 Could it be a m2 vs m3 issue perhaps?

No worries, thanks for the great library. I haven't had the time to build a mini sample app. It could be that it's M2 as we have not yet migrated.

Appreciated @LethalMaus
You can use the sample app in this repo perhaps: https://github.com/mikepenz/AboutLibraries/tree/develop/app
Having it reproduced in this context would really help!

Alright, as soon as I get the chance I'll do so. The app is not compiling straight off the bat on my mac, will try it on my Windows PC later on this week and let you know.

I am building this project on a Mac, any details on what is not compiling for you?

A problem occurred configuring root project 'AboutLibraries'.
> Could not determine the dependencies of task ':plugin-build:plugin:compileKotlin'.
   > No matching toolchains found for requested specification: {languageVersion=11, vendor=any, implementation=vendor-specific} for MAC_OS on aarch64.
      > No locally installed toolchains match and toolchain download repositories have not been configured.

I didnt spend long looking into it. I presume its because I'm on Java 17

Ah yes. It's searching for a java 11 on your system. And can't find any

Found the issue

Thank you for reporting back! greatly appreciated 👍


hide navigation bar

is there any way to hide the bottom navigation bar on some specific page?

@ahmedmirza994 Try add "rootNavigator: true", like this:
Navigator.of(context, rootNavigator: true).push<Widget>(
   MaterialPageRoute<Widget>(builder: (BuildContext context) => Screen(),
)),

@ahmedmirza994 wait.. i thought you want something like an animation or something..
Yes it’s possible!! I put that in the docs and i guess what @Goolpe said works as well!
Happy coding 🚀