Cannot properly open client on c#-rewrite branch

When i open it, login and then main window opens, huge stack trace with this error appears:
System.AggregateException: One or more errors occurred. (Exception has been thrown by the target of an invocation.)
 ---> System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation.
 ---> System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation.
 ---> System.NullReferenceException: Common section does not exist for app 590830
   at OpenSteamworks.Client.Apps.SteamApp..ctor(AppId_t appid) in /home/plyshka/Documents/Code/C#/opensteamclient/OpenSteamworks.Client/Apps/SteamApp.cs:line 64
   at OpenSteamworks.Client.Apps.AppBase.CreateSteamApp(AppId_t appid) in /home/plyshka/Documents/Code/C#/opensteamclient/OpenSteamworks.Client/Apps/AppBase.cs:line 163
   at OpenSteamworks.Client.Apps.AppsManager.GetApp(AppId_t appid) in /home/plyshka/Documents/Code/C#/opensteamclient/OpenSteamworks.Client/Apps/AppsManager.cs:line 290
   at OpenSteamworks.Client.Apps.AppsManager.GetApp(CGameID gameid) in /home/plyshka/Documents/Code/C#/opensteamclient/OpenSteamworks.Client/Apps/AppsManager.cs:line 257
   at OpenSteamClient.ViewModels.Library.LibraryAppViewModel..ctor(CGameID gameid) in /home/plyshka/Documents/Code/C#/opensteamclient/OpenSteamClient/ViewModels/Library/LibraryAppViewModel.cs:line 27
   at OpenSteamClient.ViewModels.LibraryPageViewModel.OnLibraryUpdated(Object sender, EventArgs e) in /home/plyshka/Documents/Code/C#/opensteamclient/OpenSteamClient/ViewModels/LibraryPageViewModel.cs:line 84
   at OpenSteamClient.ViewModels.LibraryPageViewModel..ctor(AppsManager appsManager, LibraryManager libraryManager) in /home/plyshka/Documents/Code/C#/opensteamclient/OpenSteamClient/ViewModels/LibraryPageViewModel.cs:line 55
   at System.RuntimeMethodHandle.InvokeMethod(Object target, Void** arguments, Signature sig, Boolean isConstructor)
   at System.Reflection.MethodBaseInvoker.InvokeDirectByRefWithFewArgs(Object obj, Span`1 copyOfArgs, BindingFlags invokeAttr)
   --- End of inner exception stack trace ---
   at System.Reflection.MethodBaseInvoker.InvokeDirectByRefWithFewArgs(Object obj, Span`1 copyOfArgs, BindingFlags invokeAttr)
   at System.Reflection.MethodBaseInvoker.InvokeWithFewArgs(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)
   at OpenSteamworks.Client.Utils.DI.Container.ConstructOnly(Type type, Object[] extraArgs) in /home/plyshka/Documents/Code/C#/opensteamclient/OpenSteamworks.Client/Utils/DI/Container.cs:line 253
   at OpenSteamClient.ViewModels.PageHeaderViewModel.<>c__DisplayClass35_0.<.ctor>b__1(Object page) in /home/plyshka/Documents/Code/C#/opensteamclient/OpenSteamClient/ViewModels/PageHeaderViewModel.cs:line 74
   at OpenSteamClient.ViewModels.MainWindowViewModel.SwitchToPage(Type pageType) in /home/plyshka/Documents/Code/C#/opensteamclient/OpenSteamClient/ViewModels/MainWindowViewModel.cs:line 102
   at OpenSteamClient.ViewModels.MainWindowViewModel..ctor(MainWindow mainWindow, ISteamClient client, AppsManager appsManager, TranslationManager tm, LoginManager loginManager, Action openSettingsWindowAction) in /home/plyshka/Documents/Code/C#/opensteamclient/OpenSteamClient/ViewModels/MainWindowViewModel.cs:line 88
   at System.RuntimeMethodHandle.InvokeMethod(Object target, Void** arguments, Signature sig, Boolean isConstructor)
   at System.Reflection.MethodBaseInvoker.InvokeWithManyArgs(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)
   --- End of inner exception stack trace ---
   at System.Reflection.MethodBaseInvoker.InvokeWithManyArgs(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)
   at OpenSteamworks.Client.Utils.DI.Container.ConstructOnly[T](Object[] extraArgs) in /home/plyshka/Documents/Code/C#/opensteamclient/OpenSteamworks.Client/Utils/DI/Container.cs:line 261
   at OpenSteamClient.AvaloniaApp.ForceMainWindow() in /home/plyshka/Documents/Code/C#/opensteamclient/OpenSteamClient/AvaloniaApp.axaml.cs:line 196
   at OpenSteamClient.AvaloniaApp.<>c__DisplayClass11_0.<OnFrameworkInitializationCompleted>b__8() in /home/plyshka/Documents/Code/C#/opensteamclient/OpenSteamClient/AvaloniaApp.axaml.cs:line 98
   at Avalonia.Threading.DispatcherOperation.InvokeCore()
--- End of stack trace from previous location ---
   at Avalonia.Threading.DispatcherOperation.Wait(TimeSpan timeout)
   at Avalonia.Threading.DispatcherOperation.Wait()
   at Avalonia.Threading.Dispatcher.InvokeImpl(DispatcherOperation operation, CancellationToken cancellationToken, TimeSpan timeout)
   at Avalonia.Threading.Dispatcher.Invoke(Action callback, DispatcherPriority priority, CancellationToken cancellationToken, TimeSpan timeout)
   at Avalonia.Threading.Dispatcher.Invoke(Action callback)
   at OpenSteamClient.AvaloniaApp.InvokeOnUIThread(Action callback) in /home/plyshka/Documents/Code/C#/opensteamclient/OpenSteamClient/AvaloniaApp.axaml.cs:line 62
   at OpenSteamClient.AvaloniaApp.<>c__DisplayClass11_0.<OnFrameworkInitializationCompleted>b__1(Object sender, LoggedOnEventArgs e) in /home/plyshka/Documents/Code/C#/opensteamclient/OpenSteamClient/AvaloniaApp.axaml.cs:line 95
   at OpenSteamworks.Client.Managers.LoginManager.<>c__DisplayClass79_0.<RunLogon>b__0() in /home/plyshka/Documents/Code/C#/opensteamclient/OpenSteamworks.Client/Login/LoginManager.cs:line 583
   at System.Threading.ExecutionContext.RunFromThreadPoolDispatchLoop(Thread threadPoolThread, ExecutionContext executionContext, ContextCallback callback, Object state)
--- End of stack trace from previous location ---
   at System.Threading.ExecutionContext.RunFromThreadPoolDispatchLoop(Thread threadPoolThread, ExecutionContext executionContext, ContextCallback callback, Object state)
   at System.Threading.Tasks.Task.ExecuteWithThreadLocal(Task& currentTaskSlot, Thread threadPoolThread)
--- End of stack trace from previous location ---
   at OpenSteamworks.Client.Managers.LoginManager.RunLogon(LoggedOnEventArgs e) in /home/plyshka/Documents/Code/C#/opensteamclient/OpenSteamworks.Client/Login/LoginManager.cs:line 583
   at OpenSteamworks.Client.Managers.LoginManager.OnLoggedOn(LoggedOnEventArgs e) in /home/plyshka/Documents/Code/C#/opensteamclient/OpenSteamworks.Client/Login/LoginManager.cs:line 574
   at OpenSteamworks.Client.Managers.LoginManager.<>c__DisplayClass74_0.<<BeginLogonToUser>b__0>d.MoveNext() in /home/plyshka/Documents/Code/C#/opensteamclient/OpenSteamworks.Client/Login/LoginManager.cs:line 513
   --- End of inner exception stack trace ---

If i run it with this patch, client opens and seems to run (though proton games do not seem to start, but it might be another error, native games start)
fix-patch.txt

Correction: Some proton games did not launch (7 days to die in my case, Deep rock galactic works)

Peculiar. There's some problems with the appinfo not existing even when it should but this is usually fixed by starting OpenSteamClient a couple times. After that it shouldn't really a problem.
The patch doesn't solve the underlying problem (appinfo missing), and instead masks it by simply initializing the appinfo to null values, which will cause game launching problems, cloud sync problems, problems where the apps aren't visible in the library and possibly further exceptions, since the common section provides us the app's name, corrected gameid, icons, proton data and more.
I'd advise to unpatch and relaunch and login a bunch of times, try 5 or so times and if it isn't solved even after that you could try another account? Other than that I can't really help too much at the moment. You could also try copying over appinfo.vdf from
The appinfo has been very difficult to get working properly so issues like this pop up every now and then, but I have a rewrite in the works that should squash a lot of the bugs, instabilities and badly written code the client has at the moment.
However the launching issue likely is not to do with the appinfo issue. Factorio not working is even more peculiar, as it's a native linux game. I'll look into it, but in the meanwhile proton games should become workable if you manually enable compat for them with the Interface Debugger.

I already tried launching 5 or more times, issue doesnt seem to be fixing by itself
Don't have another account... might try to check with another blank account

You could also try copying over appinfo.vdf from ...
from where? this seems incomplete


Improve or Clarify Backpressure on OTel-Grpc-Sources

Is your feature request related to a problem? Please describe.
Ingestion of events via Opentelemetry over GRPC can fail due to a full buffer or an open CircuitBreaker.
In that case, an error response is sent. When testing with the OpenTelemetry Collector, this leads to dropped data by the collector.
Reason for this is, that apparently the OTLP/gRPC Throttling specification is not used properly. The DataPrepper gRPC response needs to contain a proper RetryInfo.
Describe the solution you'd like
DataPrepper should implement proper OTLP/gRPC throttling, when the ingress buffers are full or the circuit breaker is open.
Describe alternatives you've considered (Optional)
DataPrepper can document, that on full buffers or open circuit breakers, requests are rejected as non-retryable. This can happen for both cases or separately just for one, e.g. open circuit breaker.
Additional context
Currently on an open curcuit breaker, the error message from the CircuitBreakingBuffer is contained in the DataPrepper response.
This is managed by the GrpcRequestExceptionHandler, that generates a RESOURCE_EXHAUSTEDresponse status. This is only retryable, if a RetryInfo is present according to https://opentelemetry.io/docs/specs/otlp/#failures. This is currently not the case, hence the OpenTelemetry collector drops the events and does no retries.

@KarstenSchnitter , For both a full buffer and the circuit breaker, we can tell the client that the request can be retried.
What I'm unsure of is what time we can give back to the client. One option would be to use the request timeout. Perhaps there is something we can get from the buffer to hint at the time. But, I'm not sure.

@KarstenSchnitter , That approach sounds reasonable. And we could allow for configuration of the initial retry and the maximum.


v1.23.0

Update Dockerfiles + docs for v1.23.0

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


Showcase: New app "Discord"

Text/voice communication app for gamers developed in React Native.

Everytime someone submits a PR with a new app for the showcase it feels like Christmas, thanks @vishnevskiy this app looks amazing! Do you have a server that I can join to try it out with people?

Feel free to join this one and ping me.
https://discord.gg/0ESuwoZe4M0y8Hrr


Influxdb pod getting wrong IP address

Hi,
We are using influxdb as a deployment on kubernetes, for some reason it is listening on different IP address. Hence pod is not being created. is there anyway I can make it listen on the node IP?
run: open server: listen: listen tcp IP:8088: bind: cannot assign requested address
This is what I get.

@farrukh90 would you share your k8s deployment?

Version 1.10.13 kubernetes
Docker Version: 18.09.2
3 Master nodes
3 Worker nodes.
`piVersion: extensions/v1beta1
kind: Deployment
metadata:
name: monitoring-influxdb
namespace: kube-system
spec:
replicas: 1
template:
metadata:
labels:
task: monitoring
k8s-app: influxdb
spec:
containers:

name: influxdb
image: k8s.gcr.io/heapster-influxdb-amd64:v1.5.2
volumeMounts:
mountPath: /data
name: influxdb-storage
volumes:
name: influxdb-storage
emptyDir: {}`

@farrukh90 seems fine although do be careful with emptyDir... you may want a persistent volume.
So, next would be to check the service.  Would you post the service definition?

apiVersion: v1
kind: Service
metadata:
labels:
task: monitoring
For use as a Cluster add-on (https://github.com/kubernetes/kubernetes/tree/master/cluster/addons)
If you are NOT using this as an addon, you should comment out this line.
kubernetes.io/cluster-service: 'true'
kubernetes.io/name: monitoring-influxdb
name: monitoring-influxdb
namespace: kube-system
spec:
ports:

port: 8086
targetPort: 8086
selector:
k8s-app: influxdb

@farrukh90 we are getting somewhere... your error specifies 8088 but the service configuration is 8086.
Would you dig into the influxdb configuration and see where 8088 is being used?

But,
The pod is not created and in error state, I cant login or exec into that pod.

and the image is not hosted on our system. It is coming from

image: k8s.gcr.io/heapster-influxdb-amd64:v1.5.2

@farrukh90 ok, I have an idea... you aren't using a configmap; that means you are using the default configuration.
I'd like you to try to set the environment variable INFLUXDB_BIND_ADDRESS to
:8088
(https://docs.influxdata.com/influxdb/v1.7/administration/config#bind-address-127-0-0-1-8088)

`[containers:

env:
name: INFLUXDB_BIND_ADDRESS
value: :8088
image: k8s.gcr.io/heapster-influxdb-amd64:v1.5.2
imagePullPolicy: IfNotPresent`

You have been very helpfull @goller  it works now

@farrukh90 Yay!!! Have fun !

It was using the wrong env variable


Add option to override command line

Follows from #22.
(Guess it's not possible to reopen a PR and reassociate it with a replacement fork, even an identical one... TIL.)

Looks mostly good to me now. I will likely merge this after I sorted out the ongoing venv issues. If I haven't merged it by Monday, I forgot. In that case please ping me.

Getting the venvs (probably) working took longer than expected. I will have to postpone this by a day or two. Don't worry about the conflicts, that I caused, I will handle them myself.

Do you object to any of the changes I made?
Could you tell me why you did add diag_mp to some of the old tests but not to all of them?

Do you object to any of the changes I made?

Thanks for asking. I guess the main thing you changed is having
apply_overrides always run, whereas before, it only ran when a nonempty
list was specified. I also see that it now runs during one of the dmypy
administrative tasks but only on the shutil conditional branch. By this
I mean the "dmypy status" subcommand -- which doesn't actually pass
"status" (unlike its run_dmypy counterpart, but I suppose this disparity
is intentional?). Anyway, I've been gathering some additional thoughts
on the dmypy situation, but I guess I'll save those for some other
discussion. BTW, with the addition of the shutil stuff, the resulting
divergent code paths aren't completely covered, but I suspect you
already knew that.

Could you tell me why you did add diag_mp to some of the old tests but not to all of them?

I only added them to those tests that call the function pylsp_lint
because that's what mutates the global last_diagnostics variable. But we
can always do something else, such as set autouse=True in the fixture
and drop the injected params in the test functions.

Thanks for asking. I guess the main thing you changed is having
apply_overrides always run, whereas before, it only ran when a nonempty
list was specified.

This was changed because otherwise there where checks at multiple locations weather it was specified. This does not come with a significant performance decrease but in my opinion makes the code a little bit more straight forward.

I also see that it now runs during one of the dmypy
administrative tasks but only on the shutil conditional branch. By this
I mean the "dmypy status" subcommand -- which doesn't actually pass
"status" (unlike its run_dmypy counterpart, but I suppose this disparity
is intentional?).

The two code paths are basically the change from #27 split into two paths. This discrepancy was introduced back then. I think using "status" on the subprocess as well should work and would be preferable to actually performing a analysis using mypy if we just want the status. However as it stands now it should run. I will investigate that after Christmas, but would like to release this PR before, therefore, that is a can of worms I don't want to open now.

Anyway, I've been gathering some additional thoughts
on the dmypy situation, but I guess I'll save those for some other
discussion.

Feel free to open a new PR or issue; Whatever fits best.

BTW, with the addition of the shutil stuff, the resulting
divergent code paths aren't completely covered, but I suspect you
already knew that.

If by covered you mean covered by tests, yes I know that (or at least am reasonable certain that this is the case but haven't checked yet) and plan to address it. If you mean something different please elaborate.

I only added them to those tests that call the function pylsp_lint
because that's what mutates the global last_diagnostics variable. But we
can always do something else, such as set autouse=True in the fixture
and drop the injected params in the test functions.

That makes sense. For now I'll keep it this way and document it. I will be writing more tests over the holidays, if i find, that nearly every tests uses it, I might switch.
So as far as I understand you are fine with the current state of the PR?
If you don't object I will merge and release today in the evening (CET)

Richard Kellnberger @.***> writes:

This was changed because otherwise there where checks at multiple
locations weather it was specified. This does not come with a
significant performance decrease but in my opinion makes the code a
little bit more straight forward.

Agree, thanks.

So as far as I understand you are fine with the current state of the PR?

Looks great!


⚠ Bofrost.at has degraded performance

In bce80c0, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 2708 ms

Resolved: Bofrost.at performance has improved in 408fae3.


Support service mapping part2

Support installing Service Mapping Operator in the Connectivity Proxy Reconciler (part 2)

add Service Mapping Configmap management

/test pre-main-reconciler-integration-k3d


Keyword argument expire_at for base.put() method not found (Python)

I am writing to a Deta base and trying to use the expire_at functionality of Deta bases.
Whenever I run the project locally everything works fine, however when I deploy my project to a micro, the following exception is raised:
put() got an unexpected keyword argument 'expire_at'
Python 3.9

same issue if I use the 'expire_in' keyword arguement

hi @HernandezCU , this is because Micros are locked with an older version of the SDK. You need to specify deta in your requirements.txt file and deploy with deta deploy to install the latest version.


Exception at "Create Compilation Database"

By trying to create the compilation database from Sourcetrail, the Sroucetrail log in Visual Studio shows the following Exception:
Info: Received request to create a compilation database.
Error: Excpetion: Due to high risk of deadlock you cannot call GetService from a background thread in an AsyncPackage derived class. You should instead call GetServiceAsync (without calling Result or Wait on the resultant Task object) or switch to the UI thread with the JoinableTaskFactory.SwitchToMainThreadAsync method before calling GetService.
Setup:
Visual Studio Version 2015
Sourcetrail Extension <IP_ADDRESS>
Sourcetrail 2019.1.11 - 64 bit

Thanks for reporting! Yesterday I fixed a similar issue that happened when navigating to a location in VS from Sourcetrail. So it should be easily fixable.
For now you can just use "Sourcetrail->Create Compilation Database"  from the VS menu bar as a workaround.

Fixed with version 2.0.2


voicevox: 0.20.0 -> 0.22.1; voicevox-engine: 0.20.0 -> 0.22.0; voicevox-core: 0.15.4 -> 0.15.5

Followup to https://github.com/NixOS/nixpkgs/pull/319403
This PR bumps all the voicevox package versions to the latest non-pre-release version.
I also changed over to using fetchurl instead of fetchzip for voicevox-core. fetchurl won't uncompress the zip file, so it takes up less space (though the difference is not too big).
This will also facilitate the creation of an update script, since we won't need to unpack to get the hash.
(I will create the script in the next bump PR)
I also appended ${version} to voicevox-engine.passthru.resources's derivation name. This way when we want to update voicevox-engine, but forget to update the hash of the resources to, it will throw a hash mismatch error.

Things done

Built on platform(s)

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

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

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

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

[ ] Fits CONTRIBUTING.md.

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

@ofborg build voicevox-core.src

@ofborg build voicevox

When temporarily setting free = true it seemed to build on all platforms (didn't wait out aarch64-darwin)

@eljamm I added you as a maintainer

I tried to run nixpkgs-review but triton-llvm is taking a lot of time and resources to build so I just gave up on that.

Do you know how triton-llvm is possibly related to the changes in this PR?

Here is the dependency graph from nom:
┏━ Dependency Graph:
┃    ┌─ ⏸ hardcode-paths.patch waiting for 2 ⏵
┃ ┌─ ⏸ voicevox-0.22.1
┃ │              ┌─ ⏵ triton-llvm-19.1.0-rc1 (configurePhase) ⏱ 10s
┃ │           ┌─ ⏸ python3.12-triton-3.1.0
┃ │        ┌─ ⏸ python3.12-torch-2.5.1
┃ │        ├─ ⏵ python3.12-jax-0.4.28 (pytestCheckPhase) ⏱ 10s
┃ │     ┌─ ⏸ python3.12-nanobind-2.4.0
┃ │  ┌─ ⏸ python3.12-soxr-0.5.0.post1
┃ ├─ ⏸ voicevox-engine-0.22.0
┃ ⏸ review-shell

When I run nix-build . -A voicevox everything builds fine, but I have to build triton-llvm with nixpkgs-review.
I assume this is happening because python3.12-soxr or its deps changed in master and is not cached, right?

I did some manual bisecting and looks like there was a staging-next merge recently and I think that caused it to start rebuilding. (maybe it doesn't build, so it didn't get cached)
I'll look into it.

Looks like some weird test failure making it not build
https://hydra.nixos.org/build/281892957/nixlog/5
Other people have already reported this issue:
https://github.com/NixOS/nixpkgs/issues/363965
https://github.com/NixOS/nixpkgs/issues/367784

Haven't rebased, since triton-llvm has only just been fixed, so it isn't cached yet.
Added a commit that makes it easier to update the voicevox-core artifact hashes in the future.

triton-llvm is now cached, so I was able to rebase on latest master.
I had to disable some tests: it was some minor floating-point imprecision issue, not sure why it only showed up now.

nixpkgs-review result
Generated using nixpkgs-review.
Command: nixpkgs-review pr 367083
x86_64-linux
✅ 4 packages built:

it is unfortunate that I just updated everything :/

@ofborg build voicevox

I had to disable some tests: it was some minor floating-point imprecision issue, not sure why it only showed up now.

This was most probably caused by the triron issue as it broke a lot of other packages as well. Everything seems to be working fine, though.

it is unfortunate that I just updated everything :/

Yeah, we posted at the same time.

Looks like on darwin torch is still broken, so it won't build there.
In any case the app built successfully on both linux platforms

Would you rather mark voicevox as broken on darwin and merge or wait until the issue is resolved?

Would you rather mark voicevox as broken on darwin and merge or wait until the issue is resolved?

As far as I know it, it will work once torch gets fixed, so we don't need to mark this package as broken.
Meaning we can merge whenever.


Gateway dispatch event types

Although the union of all event types will most likely be set to Any for performance reasons of type checkers - which is why they were never created in the first place - it can still be useful when handling individual events to be able to specify their types.
For example, as I am implementing wumpy-cache the typings of individual events is useful for each processor of an event.
If complete support was the aim, there would need to be two new types for each event, but for now it is probably easiest to only provide the d type and encourage the use of the overarching DispatchEvent type for the complete WebSocket message received over the gateway. This code should be placed in gateway.py as it is still quite small, although the size of it will increase quite a lot after this change.

This has now been implemented in the gateway-events branch, and fast forwarded into main. See 88910d2def45de014b8f3766a5a92a60ba18152f and f3ffd3be069087dce91865b78d15e6bebf6abc55 primarily.


PR's not merged #132

Added non merged PR links and assigned issue links for GSSOC verification
PR's Not Merged:

Add title on hover #477 on this link https://github.com/singodiyashubham87/Draw-it-out/pull/518 its Level 1

Made PR Merge Request Pending: Issue with Menu bar #1370 on this link https://github.com/khushi-joshi-05/Food-ordering-website/pull/1618 Level not assigned yet

Also merged my PR on this repo https://github.com/MAVRICK-1/e-commerce_website which is showing 404 error . I have merged PR of level 2 and it also been added to the leaderboard but i am not able to find the repo i have merged so my points is reduced by 25 , when I go to that repo it is showing 404 error.

@sanjay-kv Hello Sir, Kindly , merge my PR .

@sanjay-kv Thanks sir for adding labels.. Kindly merge it please.

@sanjay-kv Thank youu Sir..


ModuleNotFoundError in Output window for pytest in project.

Steps to Reproduce
1.Create python application named PythonApplication3
2.Right click in project and select New->New Folder, renamed folder as testing
3.Right click in testing folder and select Add->New item->Python Unit test
4.Make sure test1.py should be added under testing folder
5.Right click in project and select Properties ->Test, and change Test Framework to "Pytest"
Expected behavior
no any error happened and test1 could be found in Test Explorer
Actual behavior
ModuleNotFoundError happened

Solution: If I delete the default python file(PythonApplication3.py) when I created the project,  tests could be found in Test Explorer and no errors
Test environment:

Duplicate of https://github.com/microsoft/PTVS/issues/5461


Doc site improvements

add splash page
Improve some of the wording
Add details of debugging 3rd party services
Add further reading page.

Reviewer checklist

[ ] Read the contributing guide
[ ] PR should be motivated, i.e. what does it fix, why, and if relevant, how
[ ] Ensure relevant issues are linked (description should include text like "Fixes #")
[ ] Ensure any appropriate documentation has been added or amended

Coverage: 93.284%. Remained the same when pulling b02d0dec48144b963c076addaee3ecad31d70a2b on docs into 798b05553fb40cc93347a1af5a11af002abfead7 on main.


Return additional headers/response code with HandshakeException

The RFC requires that non-101 upgrades are processed as RFC 2616 responses. Therefore clients may need to use this information. E.g. 401s, 301s etc. Dropping these responses on the floor doesn't allow client behaviour to be modified when given direction from the server.


[FLINK-8497] [connectors] KafkaConsumer throws NPE if topic doesn't exist

What is the purpose of the change
To make the Kafka connector behavior clearer for the API user, by throwing a specific exception
Brief change log

PartitionDiscoverer shall not throw any exceptions, and shall return whatever it was able to find.
If nothing was found on initial discovery phase, and further discovery is disabled, an exception is thrown.

Verifying this change
This change added tests and can be verified as follows:

Added new test class Kafka09PartitionDiscovererTest.java with an appropriate unit tests
Added an extra test for the FlinkKafkaConsumerBase, and updated the other tests to take the new behavior into account

Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): no
The public API, i.e., is any changed class annotated with @Public(Evolving): no
The serializers: no
The runtime per-record code paths (performance sensitive): no
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Yarn/Mesos, ZooKeeper: no
The S3 file system connector: no

Documentation

Does this pull request introduce a new feature? no
If yes, how is the feature documented? n/a

I am not sure if failing is the right behavior here.
What is someone has a Flink job running and one of the topics for which partitions are discovered gets deleted? That would fail the job in such a way that it never recovers, even if other partitions are still valid.

@alexpf thanks for the updates.
Please bear with me just a little, I'll try to get back to reviewing this PR ASAP after I finish with some ongoing tasks.

Any update on this PR?

Any update on this PR? It might not affect K11 and up but I think K10 partition discoverer is inherent from this K9 one.

This was resolved in https://issues.apache.org/jira/browse/FLINK-11321


Install DS headers

Signed-off-by: The MathWorks, Inc<EMAIL_ADDRESS>

This will need to be merged into master as well since it stops users from integrating with Declarative Services.

I believe this closes #421 right?

Yes, this will fix #421


Add the ability to create Test::UploadedFile instances without the file system

Uploaded files behave as IO streams, so it should be reasonable to instantiate a fake one from an IO stream.  These changes don't change the existing interface to the #initialize method, but add the ability to do something like this:
io = StringIO.new('Some content')
upload = Rack::Test::UploadedFile.new(io, original_filename: 'wibble.txt')
...

A lot of tests for content uploads don't need a lot of complex content; this should allow for test suites without a bunch of tiny test files cluttering the project or spec directories.

Thanks for the contribution. I really like the idea, but I am not to sure about all details of the implementation. Especially the conditional switch on respond_to to then handle IO object and paths differently.
However I don't want to to reject anything for that reason. What do you think @perlun and @junaruga

@scepticulous I like the idea too, though I have not checked the actual source code yet.
Thanks for the contribution.

@amilligan This has now conflicts with the current master code. Are you still around, and if so, could you try to rebase this on top of the current tree?

Okay, I fixed the conflicts; nothing too concerning.
Regarding an earlier concern: I don't like using #respond_to? in almost any circumstances, but in this case the existing initializer interface expects a filename as a string, which is not easily reconciled with also accepting an abstract IO stream.  Ideally, the initializer would accept only an IO stream, but that would break the existing interface.
I can think of any number of ways to work around this, but #respond_to? seems to be the most generally accepted in the Ruby community.  I'm open to suggestions, if you have preferences.

@amilligan this now has conflicts again. 😄 If you rebase one more time, I promise we'll try to give it a look.

Resolved again; ready for a look.

Yeah, sure.

@perlun I'm slightly confused.  You're asking about the choice to implement #respond_to_missing? as opposed to #respond_to??
As of ruby 1.9 implementing the former is the invariably preferred mechanism.  The 'DO NOT USE THIS DIRECTLY' directive refers to calling the method, which I don't believe is done anywhere in the project.

@perlun I'm slightly confused. You're asking about the choice to implement #respond_to_missing? as opposed to #respond_to??
As of ruby 1.9 implementing the former is the invariably preferred mechanism. The 'DO NOT USE THIS DIRECTLY' directive refers to calling the method, which I don't believe is done anywhere in the project.

I stand corrected. 🙈 Sorry for that @amilligan! This blog post explains some more of the details.
I am fine with this now. Will approve and merge. Thanks for the effort, and sorry about the delay!

Hi,
This change is breaking an use case in specs with Paperclip + FactoryBot.
The suggested method documented here: https://github.com/thoughtbot/paperclip#testing
FactoryGirl.define do
  factory :user do
    avatar { File.new("#{Rails.root}/spec/support/fixtures/image.jpg") }
  end
end

does not work anymore:
     NoMethodError:
       undefined method `size' for nil:NilClass
     # ~/dev/rack-test/lib/rack/test/uploaded_file.rb:38:in `public_send'
     # ~/dev/rack-test/lib/rack/test/uploaded_file.rb:38:in `method_missing'
     # ~/dev/rack-test/lib/rack/test/utils.rb:136:in `build_file_part'
     # ~/dev/rack-test/lib/rack/test/utils.rb:101:in `block in get_parts'
     # ~/dev/rack-test/lib/rack/test/utils.rb:92:in `each'
     # ~/dev/rack-test/lib/rack/test/utils.rb:92:in `map'
     # ~/dev/rack-test/lib/rack/test/utils.rb:92:in `get_parts'
     # ~/dev/rack-test/lib/rack/test/utils.rb:87:in `build_parts'
     # ~/dev/rack-test/lib/rack/test/utils.rb:77:in `build_multipart'
     # ~/dev/rack-test/lib/rack/test.rb:231:in `env_for'
     # ~/dev/rack-test/lib/rack/test.rb:128:in `custom_request'
     # ~/dev/rack-test/lib/rack/test.rb:66:in `post'

Is there any suggested way of doing this with rack-test 0.7.1? Should I report this to Paperclip?
I've tried several things but I'm unable to make it work.
TIA

Hi,
I have the same problem with 0.7.1: https://github.com/rspec/rspec-rails/issues/1915

@tagliala @007lva Sorry for this; this is an unintended regression because of this change. For now, downgrade your project to 0.7.0 to work around the issue.
If either one of you could provide a PR with a failing test case to the rack-test repo, that would be 👍 👍 👍. We will then try to fix this as soon as possible, and get a fixed gem version released.
I will lock this conversation now, since it's too hard to find discussions going on in "merged pull requests"; we need it in a new issue or PR for it to be visible to the audience at large.

The issue @tagliala reported is now here: #214


PDOException: SQLSTATE[HY000]: General error: 1180 Got error 35 "Resource deadlock avoided" during COMMIT

We are receiving "Resource deadlock avoided" from the Mariadb with galera cluster.
I will do a pull request sortly.

I am getting this error on my laravel 5.2


Count coverage of cypress-ct based tests

Currently, only jest-based tests are recognized when computing the tests coverage. The component tests written in cypress-ct should also be included in these percentages.
Possible solutions:
https://github.com/bahmutov/cypress-and-jest
https://docs.cypress.io/guides/tooling/code-coverage

:tada: This issue has been resolved in version 1.0.11 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Custom Docker versions

What happened:
When running horusec on a machine that is using Microsofts fork of moby (Azure Kubernetes Service, GitHub Actions etc) it will fail because they use other versions.
It would be great if we either could make it configurable (skip version check) or that we add a specific check for the Docker version marked with the prefix "+azure".
What you expected to happen:
When running horusec on a machine with Microsoft fork, it won't start:
2020-11-01T14:44:47.9096474Z + docker --version
2020-11-01T14:44:47.9322280Z Docker version 3.0.13+azure, build dd360c7c0de8d9132a3965db6a59d3ae74f43ba7
2020-11-01T14:44:47.9330681Z + horusec start -p=./ -e=true
2020-11-01T14:44:48.0425625Z time="2020-11-01T14:44:48Z" level=error msg="{HORUSEC_CLI} Your docker version is below of: " error=19.3
2020-11-01T14:44:48.0426489Z time="2020-11-01T14:44:48Z" level=info msg="{HORUSEC_CLI} If your docker is not installed check in docs of how to install in:\n\t\thttps://docs.docker.com/get-docker\n\t"
2020-11-01T14:44:48.0427682Z time="2020-11-01T14:44:48Z" level=panic msg="{HORUSEC_CLI} Missing required DOCKER in min. version 19.03 to start" error="check the requirements for run and try again"
2020-11-01T14:44:48.0448274Z panic: (*logrus.Entry) 0xc000362310
2020-11-01T14:44:48.0448426Z
2020-11-01T14:44:48.0449000Z goroutine 1 [running]:
2020-11-01T14:44:48.0449589Z github.com/sirupsen/logrus.Entry.log(0xc00011c000, 0xc0005be240, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, ...)
2020-11-01T14:44:48.0450066Z 	/home/wilian/go/src/github.com/ZupIT/horusec/vendor/github.com/sirupsen/logrus/entry.go:255 +0x325
2020-11-01T14:44:48.0450391Z github.com/sirupsen/logrus.(*Entry).Log(0xc0003622a0, 0x0, 0xc0005a9da8, 0x1, 0x1)
2020-11-01T14:44:48.0450705Z 	/home/wilian/go/src/github.com/ZupIT/horusec/vendor/github.com/sirupsen/logrus/entry.go:283 +0xf0
2020-11-01T14:44:48.0451009Z github.com/sirupsen/logrus.(*Entry).Panic(0xc0003622a0, 0xc0005a9da8, 0x1, 0x1)
2020-11-01T14:44:48.0451299Z 	/home/wilian/go/src/github.com/ZupIT/horusec/vendor/github.com/sirupsen/logrus/entry.go:321 +0x55
2020-11-01T14:44:48.0452245Z github.com/ZupIT/horusec/development-kit/pkg/utils/logger.LogPanicWithLevel(0xc6283c, 0x44, 0xdd6680, 0xc000060390, 0x0, 0x0, 0x0, 0x0)
2020-11-01T14:44:48.0452789Z 	/home/wilian/go/src/github.com/ZupIT/horusec/development-kit/pkg/utils/logger/logger.go:99 +0x125
2020-11-01T14:44:48.0453311Z github.com/ZupIT/horusec/horusec-cli/internal/controllers/requirements.(*Requirements).ValidateDocker(0xc0005a9f68)
2020-11-01T14:44:48.0453872Z 	/home/wilian/go/src/github.com/ZupIT/horusec/horusec-cli/internal/controllers/requirements/requirements.go:43 +0x8b
2020-11-01T14:44:48.0454332Z main.main()
2020-11-01T14:44:48.0454969Z 	/home/wilian/go/src/github.com/ZupIT/horusec/horusec-cli/cmd/horusec/main.go:60 +0x49
2020-11-01T14:44:48.0483833Z
2020-11-01T14:44:48.0534364Z ##[error]Bash exited with code '2'.
2020-11-01T14:44:48.0547725Z ##[section]Finishing: Code scan

How to reproduce it (as minimally and precisely as possible):
In my case this happens on Azure Kubernetes Service, but may also be possible to reproduce on GitHub Actions.
Anything else we need to know?:
Read about it here: https://github.community/t/what-really-is-docker-3-0-6/16171/2
Environment:

Horusec version (use horusec version): 1.4.0
Operating System: Ubuntu 18.04
Network plugin / Tool and version (if this is a network-related / tool bug): N/A
Others: N/A

When looking through the code, it seems like the output is taken from here: https://github.com/ZupIT/horusec/blob/c1bd1dd8911854e90ef9a1e8fc226e9ae4c89693/horusec-cli/internal/controllers/requirements/docker/docker.go#L77
If you use the following, you will get json output which may help in extracting the data: docker version -f '{{json .}}'.
This is the output from AKS:
{
  "Client": {
    "Platform": {
      "Name": ""
    },
    "Version": "3.0.13+azure",
    "ApiVersion": "1.40",
    "DefaultAPIVersion": "1.40",
    "GitCommit": "dd360c7c0de8d9132a3965db6a59d3ae74f43ba7",
    "GoVersion": "go1.13.11",
    "Os": "linux",
    "Arch": "amd64",
    "BuildTime": "Thu May 28 20:41:25 2020",
    "Experimental": false
  },
  "Server": {
    "Platform": {
      "Name": ""
    },
    "Components": [
      {
        "Name": "Engine",
        "Version": "3.0.10+azure",
        "Details": {
          "ApiVersion": "1.40",
          "Arch": "amd64",
          "BuildTime": "Fri Jan 24 20:08:11 2020",
          "Experimental": "false",
          "GitCommit": "ea84732a77",
          "GoVersion": "go1.12.14",
          "KernelVersion": "4.15.0-1092-azure",
          "MinAPIVersion": "1.12",
          "Os": "linux"
        }
      },
      {
        "Name": "containerd",
        "Version": "v1.2.11",
        "Details": {
          "GitCommit": "f772c10a585ced6be8f86e8c58c2b998412dd963"
        }
      },
      {
        "Name": "runc",
        "Version": "1.0.0-rc10",
        "Details": {
          "GitCommit": "dc9208a3303feef5b3839f4323d9beb36df0a9dd"
        }
      },
      {
        "Name": "docker-init",
        "Version": "0.18.0",
        "Details": {
          "GitCommit": "fec3683"
        }
      }
    ],
    "Version": "3.0.10+azure",
    "ApiVersion": "1.40",
    "MinAPIVersion": "1.12",
    "GitCommit": "ea84732a77",
    "GoVersion": "go1.12.14",
    "Os": "linux",
    "Arch": "amd64",
    "KernelVersion": "4.15.0-1092-azure",
    "BuildTime": "2020-01-24T20:08:11.000000000+00:00"
  }
}

The below is from my local computer: (not +azure version)
{
  "Client": {
    "Platform": {
      "Name": "Docker Engine - Community"
    },
    "Version": "19.03.12",
    "ApiVersion": "1.40",
    "DefaultAPIVersion": "1.40",
    "GitCommit": "48a66213fe",
    "GoVersion": "go1.13.10",
    "Os": "darwin",
    "Arch": "amd64",
    "BuildTime": "Mon Jun 22 15:41:33 2020",
    "Experimental": false
  },
  "Server": {
    "Platform": {
      "Name": "Docker Engine - Community"
    },
    "Components": [
      {
        "Name": "Engine",
        "Version": "19.03.12",
        "Details": {
          "ApiVersion": "1.40",
          "Arch": "amd64",
          "BuildTime": "Mon Jun 22 15:49:27 2020",
          "Experimental": "false",
          "GitCommit": "48a66213fe",
          "GoVersion": "go1.13.10",
          "KernelVersion": "4.19.76-linuxkit",
          "MinAPIVersion": "1.12",
          "Os": "linux"
        }
      },
      {
        "Name": "containerd",
        "Version": "v1.2.13",
        "Details": {
          "GitCommit": "7ad184331fa3e55e52b890ea95e65ba581ae3429"
        }
      },
      {
        "Name": "runc",
        "Version": "1.0.0-rc10",
        "Details": {
          "GitCommit": "dc9208a3303feef5b3839f4323d9beb36df0a9dd"
        }
      },
      {
        "Name": "docker-init",
        "Version": "0.18.0",
        "Details": {
          "GitCommit": "fec3683"
        }
      }
    ],
    "Version": "19.03.12",
    "ApiVersion": "1.40",
    "MinAPIVersion": "1.12",
    "GitCommit": "48a66213fe",
    "GoVersion": "go1.13.10",
    "Os": "linux",
    "Arch": "amd64",
    "KernelVersion": "4.19.76-linuxkit",
    "BuildTime": "2020-06-22T15:49:27.000000000+00:00"
  }
}

Not sure about the 19.03 requirement, but may be easier to match the ApiVersion instead of the Version.

I agree to check the docker version on apiVersion.
The reason we limit it to version 19 is because we only tested this version and we can only guarantee that it fully works on this version.

Hello, how are you @simongottschlag ?
Thanks for the informed report!
We really have a problem with the way azure works with its pipelines. For this we have some recommendations:
We put the docker in version 19.03 as a requirement, as several tests were carried out in different S.O and pipelines as suggested in the Horusec documentation, so we can guarantee that anyone who uses them in that way would have no problems with the environment of their machine.
We have some solutions that the Horusec team found your problem:

Change the source code in order to ignore the requirements with a global flag, so no environment check will be performed on your machine, but we cannot guarantee that the analysis carried out is in accordance with our tests.
Change your pipeline to use Horusec as a docker image. For this change, just as we do on AWS, you can start a new step in your pipeline with a Horusec-CLI image so that it will be fully configured with all the necessary requirements. The image is available on the DockerHub

Hi @wiliansilvazup !
Thank you for the update!
Since we already had other problems with Docker-in-Docker and AKS, we've started moving to Virtual Machine Scale Sets instead which doesn't have these issues.
I did a test (#107) and it seems to be working as expected, but since we won't need it I'll close it. If you want to use it, feel free to take what I did and convert to checking the api version instead.
Thank you!

@simongottschlag Could you tell us what you did in your workflow? I need to import horusec cli results into manager.


bootkube panics and exits when third party resources are present

Issue
When launching bootkube with a pre-existing etcd present, if /registry/thirdparty resources are present in etcd, bootkube will panic and exit as follows.
Feb 25 02:21:37 ip-10-0-47-164 bootkube-start[5131]: [ 1158.791945] bootkube[5]: panic: runtime error: invalid memory address or nil pointer dereference
Feb 25 02:21:37 ip-10-0-47-164 bootkube-start[5131]: [ 1158.792323] bootkube[5]: [signal SIGSEGV: segmentation violation code=0x1 addr=0x60 pc=0xe552ad]
Feb 25 02:21:37 ip-10-0-47-164 bootkube-start[5131]: [ 1158.792512] bootkube[5]: goroutine 44 [running]:
Feb 25 02:21:37 ip-10-0-47-164 bootkube-start[5131]: [ 1158.792671] bootkube[5]: panic(0x28ca700, 0xc420010050)
Feb 25 02:21:37 ip-10-0-47-164 bootkube-start[5131]: [ 1158.792878] bootkube[5]:         /usr/local/go/src/runtime/panic.go:500 +0x1a1
Feb 25 02:21:37 ip-10-0-47-164 bootkube-start[5131]: [ 1158.793035] bootkube[5]: github.com/kubernetes-incubator/bootkube/vendor/k8s.io/kubernetes/pkg/apimachinery/registered.(*APIRegistrationManager).RESTMapper(0xc4200fe500, 0x0, 0x0, 0x0, 0xc422807a08, 0x53eb80)
Feb 25 02:21:37 ip-10-0-47-164 bootkube-start[5131]: [ 1158.793205] bootkube[5]:         /go/src/github.com/kubernetes-incubator/bootkube/vendor/k8s.io/kubernetes/pkg/apimachinery/registered/registered.go:313 +0x24d
Feb 25 02:21:37 ip-10-0-47-164 bootkube-start[5131]: [ 1158.793365] bootkube[5]: github.com/kubernetes-incubator/bootkube/vendor/k8s.io/kubernetes/pkg/apimachinery/registered.(*APIRegistrationManager).RESTMapper-fm(0x0, 0x0, 0x0, 0xc4227a2600, 0xc422807a40)

After some trial and error, I found the following keys were causing the above error.
# etcdctl get --prefix=true --keys-only=true /registry | grep thirdparty
/registry/thirdpartyresources/auth-code.oidc.coreos.com
/registry/thirdpartyresources/auth-request.oidc.coreos.com
/registry/thirdpartyresources/o-auth2-client.oidc.coreos.com
/registry/thirdpartyresources/password.oidc.coreos.com
/registry/thirdpartyresources/refresh-token.oidc.coreos.com
/registry/thirdpartyresources/signing-key.oidc.coreos.com

Removal of the thirdparty keys, as seen below, allows bootkube to start successfully.
etcdctl get --prefix=true --keys-only /registry | grep thirdparty | xargs -L1 etcdctl del

This issue was discovered while troubleshooting #333.
Versions
k8s [hyperkube] version: 1.5.2_coreos.2
version: v0.3.7
os:
NAME="Container Linux by CoreOS"
ID=coreos
VERSION=1235.12.0
VERSION_ID=1235.12.0
BUILD_ID=2017-02-23-0222
PRETTY_NAME="Container Linux by CoreOS 1235.12.0 (Ladybug)"

Just noting that currently bootkube is not meant to be used against an existing cluster. However, there may be situations later where we do want this behavior (e.g. maybe disaster recovery is built into bootkube at some point) - so I'll keep this open.


⚠ SpeakUpConference.com has degraded performance

In 85601c4, SpeakUpConference.com (https://www.speakupconference.com) experienced degraded performance:

HTTP code: 200
Response time: 15355 ms

Resolved: SpeakUpConference.com performance has improved in 448b18f after 12 minutes.


[BUG] Yaml Uninstall operation did not delete resources that are not under namespace "morphling-system", e.g., clusterRole

What steps did you take and what happened:
[A clear and concise description of what the bug is.]
Yaml Uninstall operation did not delete resources that are not under namespace "morphling-system", e.g., clusterRole
What did you expect to happen:
Add an undeploy script, effecting with kustomization.yaml
Anything else we need to know?:
Environment:

Morphling version:
Minikube version (minikube version):
Kubernetes version (use kubectl version):
OS (e.g: cat /etc/os-release):
Kernel (e.g. uname -a):
Install tools:
Others:

Will add an undeploy script, effecting with kustomization.yaml in the next commit


[Feature Request] Add

Please consider adding "time till payout", I'd like to be able to setup a template sensor that calculates "$/btc per hour" based on actual payouts.

Would that work as an attribute of the unpaidAmount or would you prefer a dedicated sensor?

An attribute of unpaidAmount would be fine but what ever is easiest.


Ensure that the worker is running when we are reporting

Opbeat.capture fails silently unless there's a transaction right now.

I realise now that this should maybe be in Client#enqueue instead, not sure.

Hey Jens – thank you for this. Transactions shouldn't play a role in whether .capture sends or not. Are you using opbeat-ruby with Rails? If so, the worker should automatically be started by the the railtie. If not, you should make sure to boot Opbeat somewhere through Opbeat.start!.

Maybe there's also some confusion around a renamed method from 2.0. Opbeat.capture(&block) is supposed to be used to wrap anything that needs automatic error capturing. To report a single error to Opbeat use Opbeat.report(exception)

I'm not using Rails, without this patch, the following does not send a report to opbeat.
if ENV['OPBEAT_APP_ID']
  require 'opbeat'

  config = Opbeat::Configuration.new do |config|
    config.organization_id = ENV.fetch('OPBEAT_ORGANIZATION_ID')
    config.app_id = ENV.fetch('OPBEAT_APP_ID')
    config.secret_token = ENV.fetch('OPBEAT_SECRET_TOKEN')
  end

  Opbeat.start! config

  Opbeat.capture do
    raise ArgumentError
  end
end

Story checks out. Thanks a bunch!
:heart: :blue_heart: :purple_heart: :yellow_heart: :green_heart:

You're welcome!


Cannot Add Pivot Table

I'm trying to add a pivot table based on an existing table.  The source table is located at 'A4:M345'.  I get numerous errors printed and no pivot table.
Here is the test script:
$pt = @{
SourceWorkSheet = 'OpenIncidentsByAgeAndTeam'
PivotColumn = 'Assignment Group'
PivotRows = 'Number'
SourceRange = 'A4:M345'
PivotData = @{
'Number' = 'sum'
}
}
export-excel -path "./Executive Report Test3.xlsx"     -WorksheetName 'PivotTable'
-PivotTableDefinition $pt

Please post sample data and are pro script that I can run and shows the error. Also include the version of powershell and import excel

Thanks for your patience.
I was able to work through my issue.  I used one of your examples in the
Add-PivotTable cmdlet to get what I needed.
On Fri, Feb 17, 2023 at 6:30 AM Doug Finke @.***> wrote:

Please post sample data and are pro script that I can run and shows the
error. Also include the version of powershell and import excel
—
Reply to this email directly, view it on GitHub
https://github.com/dfinke/ImportExcel/issues/1398#issuecomment-1434575117,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AVGUKGYTKE3B5POIFKDE6CDWX5VM3ANCNFSM6AAAAAAU6WT3BE
.
You are receiving this because you authored the thread.Message ID:
@.***>

--
Larry Singer
@.***


Restricting Playermodels

If you're still open to suggestions, I think it might be useful to be able to restrict playermodels through URS as well. It certainly might prove useful to be able to prevent certain ranks from using certain playermodels (Donor models, admin-only models, etc.).
Sound like something you might consider?

I will consider this soon.  I think it could be somewhat useful.


Backpack system

Let the character equip different bags and backpacks that work as his or hers inventory. A character could also drop the backpack and pick it up later on to recover all items that were inside it.

In the creature presets there will be an array with objects of the form
{probability, bag,
[{prob1, itemId1}, {prob2, itemId2}, ...]}
This allows for:
Rare and different bags.
Rare and different items inside the bags.


Uninstalling modules doesn't seem to work

I can't uninstall custom timestamps or other modules.

Wrong repo


Add multiselect example with no design [WIP]

This is just an example for adding multiselect, as the types are very tricky. Don't merge this as is, as it has no proper design yet.
Web frontend checklist

[ ] Formatted my code with yarn format
[ ] There are no warnings from yarn lint --fix
[ ] There are no console warnings when running the app
[ ] Added any new components to storybook
[ ] Added tests where relevant
[ ] All tests pass
[ ] Clicked around my changes running locally and it works
[ ] Checked Desktop, Mobile and Tablet screen sizes

Closing as was just for an example.


feat(apps): adapt OpenAPI createEvaluation

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

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

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
7614

Relevant Lines:
8794

💛  - Coveralls


Max/Min Number of Assets for the optimized Portfolio (pypfopt.efficient_frontier.EfficientCVaR)

What are you trying to do?
I am optimizing via the pypfopt.efficient_frontier.EfficientCVaR (mainly with efficient_risk() / efficient_return())
I was wondering how one could implement a min. or max. limit regarding the number of assets which the optimized portfolio should hold (as another restriction - like atleast 10 stocks or not more than 30 for example).
In my case efficient_risk() with ratio = 0.2 for example leads to very clumped portfolios for example and even for efficient_return() at ratios between 0.06 und 0.15 out of 52 assets it for example only considers 8 at best.
I am relatively new to python and could really use some help :)
If such a feature already exists i truly am sorry for bringing it up. Thanks in advance for the feedback and of course for the amazing module!
What data are you using?
I am using mainly stocks and optimizing the CVaR for a potential list of >50 assets.

Hi @fstulle,
That kind of stuff is not currently supported, as it requires an additional and complex constraint. I could give you a single line of code for this constraint, but I cannot guarantee the results, so I won’t do that here.
However, I believe this feature (min and/or max number of assets) would be useful for others, especially for practitioners. I’d like to include it in our next version. I hope this will be useful for you and others.

Any update on this? thanks.

In addition to min/max number of assets, it would be great to be able state which ones must be included in the result (which must be < nmax. For example we may want at least 3 assets in our portfolio, but we always want to have GOOGL included.


Not compatible with >= gulp 4.0

Hey there,
Empty arrays are no longer supported for gulp.src in the latest Gulp 4.0.
Could you provide a working example that gets around this limitation?

I just did gulp.src('gulpfile.js')... works for meow.


Read replica crashes during insert or extension load

Steps to reproduce
We have found sometimes simply creating a new database, creating a new table, or inserting data via primary causes a logical replica node to crash. This can be reproduced somewhat unreliably by importing data (in our testing we used a 100MB CSV) via PGAdmin into a regular table.
We can more reliably replicate the crash simply by creating an empty database and loading timescale extension with:
CREATE EXTENSION IF NOT EXISTS timescaledb;

Please see our configuration and relevant snippets of crash logs below.
Expected result
Primary writes WAL to safekeepers. Replica is informed of WAL changes. Reading from either replica or primary succeeds. Replica should not crash.
Actual result
Primary writes WAL. Replica crashes. Reading from primary succeeds. On replica restart, reading from replica succeeds.
Environment
Running neon in a test kubernetes cluster on a single node with a custom helm template. Neon containers on release-4781 tag with compute v16. Remote storage is self-hosted minio in the cluster. The stack is essentially the same as the docker-compose example, but with the addition of a compute replica. Pods:

1x pageserver (1 tenant + timeline)
1x storage-broker
1x safekeeper (also tested with 3x)
1x primary compute
1x replica compute

Configuration for pageserver and compute are attached as files below. Replica config was inferred from control_plane/src/endpoint.rs:setup_pg_conf.

pageserver.toml
primary-spec.json
replica-spec.json

We have also attempted to decrease max_replication_write_lag significantly (e.g. 500MB -> 15MB), and have tried different versions of postgres (v15) to no avail.
Logs, links
Replica fails with various errors depending on action performed on the primary, all with WAL redo context:
PG:2024-02-07 06:09:22.898 GMT [27] LOG:  redo starts at 0/149F148
PG:2024-02-07 06:09:22.902 GMT [27] LOG:  [NEON_SMGR] libpagestore: connected to 'host=neon-pageserver port=6400'
PG:2024-02-07 06:09:23.756 GMT [27] FATAL:  [NEON_SMGR] could not read block 2 in rel 1663/16384/2620.1 from page server at lsn 0/0149F638
PG:2024-02-07 06:09:23.756 GMT [27] DETAIL:  page server returned error: Read error: could not find data for key 000000067F00004000000000000000000001 (shard ShardNumber(0)) at LSN 0/149F060, for request at LSN 0/149F638
PG:2024-02-07 06:09:23.756 GMT [27] CONTEXT:  WAL redo at 0/1FC2AA8 for Heap/INSERT: off 40 flags 0x00; blkref #0: rel 1663/16384/2620, blk 0
PG:2024-02-07 06:09:23.758 GMT [22] LOG:  startup process (PID 27) exited with exit code 1
PG:2024-02-07 06:09:23.759 GMT [22] LOG:  terminating any other active server processes
PG:2024-02-07 06:09:23.760 GMT [22] LOG:  shutting down due to startup process failure
PG:2024-02-07 06:09:23.762 GMT [22] LOG:  database system is shut down
2024-02-07T06:09:23.764660Z  INFO Postgres exited with code exit status: 1, shutting down
2024-02-07T06:09:23.764690Z  INFO checking for core dumps in /var/db/postgres/compute
2024-02-07T06:09:23.764744Z  INFO shutting down tracing
2024-02-07T06:09:23.764853Z  INFO shutting down

PG:2024-02-08 04:56:51.018 GMT [27] FATAL:  [NEON_SMGR] [shard 0] could not read block 2 in rel 1663/36494/36495.1 from page server at lsn 0/1804B220
PG:2024-02-08 04:56:51.018 GMT [27] DETAIL:  page server returned error: Read error
PG:2024-02-08 04:56:51.018 GMT [27] CONTEXT:  WAL redo at 0/18B9D110 for neon/MULTI_INSERT+INIT: ntuples: 5, flags: 0x08; blkref #0: rel 1663/36494/36495, blk 0
PG:2024-02-08 04:56:51.021 GMT [22] LOG:  startup process (PID 27) exited with exit code 1

PG:2024-02-07 06:34:40.114 GMT [27] FATAL:  unexpected data beyond EOF in block 0 of relation global/2965
PG:2024-02-07 06:34:40.114 GMT [27] HINT:  This has been seen to occur with buggy kernels; consider updating your system.
PG:2024-02-07 06:34:40.114 GMT [27] CONTEXT:  WAL redo at 0/1FEA7C0 for XLOG/FPI: ; blkref #0: rel 1664/0/2965, blk 1 FPW
PG:2024-02-07 06:34:40.119 GMT [22] LOG:  startup process (PID 27) exited with exit code 1

PG:2024-02-07 06:39:35.398 GMT [27] WARNING:  page 0 of relation global/2964 does not exist
PG:2024-02-07 06:39:35.398 GMT [27] CONTEXT:  WAL redo at 0/2D146B8 for neon/HOT_UPDATE: old_xmax: 748, old_off: 2, old_infobits: [], flags: 0x20, new_xmax: 0, new_off: 3; blkref #0: rel 1664/0/2964, blk 0
PG:2024-02-07 06:39:35.398 GMT [27] PANIC:  WAL contains references to invalid pages
PG:2024-02-07 06:39:35.398 GMT [27] CONTEXT:  WAL redo at 0/2D146B8 for neon/HOT_UPDATE: old_xmax: 748, old_off: 2, old_infobits: [], flags: 0x20, new_xmax: 0, new_off: 3; blkref #0: rel 1664/0/2964, blk 0
PG:2024-02-07 06:39:35.432 GMT [22] LOG:  startup process (PID 27) was terminated by signal 6: Aborted

Pageserver log at time of error:
2024-02-08T03:56:24.629953Z  INFO page_service_conn_main{peer_addr=<IP_ADDRESS>:59092}:process_query{tenant_id=941ddc8604413b88b3d208bddf90396c timeline_id=4af489b06af8eed9e27a841775616962}:handle_pagerequests:handle_get_page_at_lsn_request{rel=1663/24576/2663 blkno=4 req_lsn=0/45411F8}: launched walredo process duration_ms=0 pid=45
2024-02-08T03:56:34.450776Z  INFO wal_connection_manager{tenant_id=941ddc8604413b88b3d208bddf90396c shard_id=0000 timeline_id=4af489b06af8eed9e27a841775616962}:connection{node_id=0}: check_checkpoint_distance 2240, layer size 2325, elapsed since last flush<PHONE_NUMBER>03s
2024-02-08T03:56:34.453864Z  INFO layer flush task{tenant_id=941ddc8604413b88b3d208bddf90396c shard_id=0000 timeline_id=4af489b06af8eed9e27a841775616962}:flush_frozen_layer{layer=inmem-0000000004541DC1-0000000004542681}: Rebuilt layer map. Did 1 insertions to process a batch of 1 updates.
2024-02-08T03:56:34.453943Z  INFO layer flush task{tenant_id=941ddc8604413b88b3d208bddf90396c shard_id=0000 timeline_id=4af489b06af8eed9e27a841775616962}:flush_frozen_layer{layer=inmem-0000000004541DC1-0000000004542681}: scheduled layer file upload<PHONE_NUMBER>00000000000000000000000000-FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF__0000000004541DC1-0000000004542681 gen=<none> shard=0000
2024-02-08T03:56:34.454017Z  INFO layer flush task{tenant_id=941ddc8604413b88b3d208bddf90396c shard_id=0000 timeline_id=4af489b06af8eed9e27a841775616962}:flush_frozen_layer{layer=inmem-0000000004541DC1-0000000004542681}: scheduling metadata upload with 8 files (1 changed)
2024-02-08T03:56:34.456086Z  INFO remote_upload{tenant_id=941ddc8604413b88b3d208bddf90396c shard_id=0000 timeline_id=4af489b06af8eed9e27a841775616962 upload_task_id=4}:lazy_load_identity: identity cache miss occurred; added new identity (took Ok(15.03µs))
2024-02-08T03:58:07.108703Z ERROR page_service_conn_main{peer_addr=<IP_ADDRESS>:50190}:process_query{tenant_id=941ddc8604413b88b3d208bddf90396c timeline_id=4af489b06af8eed9e27a841775616962}:handle_pagerequests:handle_get_rel_exists_request{rel=1663/32768/32769_fsm req_lsn=0/4542448}: error reading relation or page version: Read error: could not find data for key 000000067F00008000000000000000000001 (shard ShardNumber(0)) at LSN 0/14EE9E8, for request at LSN 0/4542448: layer traversal: result Continue, cont_lsn 0/14EE9E8, layer: /data/.neon/tenants/941ddc8604413b88b3d208bddf90396c/timelines/4af489b06af8eed9e27a841775616962/000000000000000000000000000000000000-FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF__00000000014EE9E8-00000000014EEA61: layer traversal: result Continue, cont_lsn 0/14EEA61, layer: /data/.neon/tenants/941ddc8604413b88b3d208bddf90396c/timelines/4af489b06af8eed9e27a841775616962/000000000000000000000000000000000000-FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF__00000000014EEA61-0000000002D147B9: layer traversal: result Continue, cont_lsn 0/2D147B9, layer: /data/.neon/tenants/941ddc8604413b88b3d208bddf90396c/timelines/4af489b06af8eed9e27a841775616962/000000000000000000000000000000000000-FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF__0000000002D147B9-0000000002D15A41: layer traversal: result Continue, cont_lsn 0/2D15A41, layer: /data/.neon/tenants/941ddc8604413b88b3d208bddf90396c/timelines/4af489b06af8eed9e27a841775616962/000000000000000000000000000000000000-FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF__0000000002D15A41-0000000002D16AE9: layer traversal: result Continue, cont_lsn 0/2D16AE9, layer: /data/.neon/tenants/941ddc8604413b88b3d208bddf90396c/timelines/4af489b06af8eed9e27a841775616962/000000000000000000000000000000000000-FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF__0000000002D16AE9-0000000002D1F6B9: layer traversal: result Continue, cont_lsn 0/2D1F6B9, layer: /data/.neon/tenants/941ddc8604413b88b3d208bddf90396c/timelines/4af489b06af8eed9e27a841775616962/000000000000000000000000000000000000-FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF__0000000002D1F6B9-000000000453D071: layer traversal: result Continue, cont_lsn 0/453D071, layer: /data/.neon/tenants/941ddc8604413b88b3d208bddf90396c/timelines/4af489b06af8eed9e27a841775616962/000000000000000000000000000000000000-FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF__000000000453D071-0000000004541DC1: layer traversal: result Continue, cont_lsn 0/4541DC1, layer: /data/.neon/tenants/941ddc8604413b88b3d208bddf90396c/timelines/4af489b06af8eed9e27a841775616962/000000000000000000000000000000000000-FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF__0000000004541DC1-0000000004542681
2024-02-08T03:58:08.418218Z  INFO page_service_conn_main{peer_addr=<IP_ADDRESS>:40776}:process_query{tenant_id=941ddc8604413b88b3d208bddf90396c timeline_id=4af489b06af8eed9e27a841775616962}:handle_basebackup_request{lsn=None prev_lsn=None full_backup=false}: taking basebackup lsn=0/5079910, prev_lsn=0/50798D8 (full_backup=false)
2024-02-08T03:58:08.419383Z  INFO page_service_conn_main{peer_addr=<IP_ADDRESS>:40776}:process_query{tenant_id=941ddc8604413b88b3d208bddf90396c timeline_id=4af489b06af8eed9e27a841775616962}:handle_basebackup_request{lsn=None prev_lsn=None full_backup=false}:send_tarball{backup_lsn=0/5079910}: timeline.pg_version 16
2024-02-08T03:58:08.442193Z  INFO page_service_conn_main{peer_addr=<IP_ADDRESS>:40776}:process_query{tenant_id=941ddc8604413b88b3d208bddf90396c timeline_id=4af489b06af8eed9e27a841775616962}:handle_basebackup_request{lsn=None prev_lsn=None full_backup=false}: basebackup complete lsn_await_millis=0 basebackup_millis=23

Safekeeper log at time of error:
2024-02-08T03:56:34.706423Z  INFO WAL backup{ttid=941ddc8604413b88b3d208bddf90396c/4af489b06af8eed9e27a841775616962}:lazy_load_identity: identity cache miss occurred; added new identity (took Ok(59.651µs))
2024-02-08T03:56:34.767154Z  INFO WAL backup{ttid=941ddc8604413b88b3d208bddf90396c/4af489b06af8eed9e27a841775616962}: offloaded segnos [4] up to 0/5037A50, previous backup_lsn 0/4000000
2024-02-08T03:58:07.114638Z  INFO {cid=4 ttid=941ddc8604413b88b3d208bddf90396c/4af489b06af8eed9e27a841775616962}:WAL sender: terminated: EOF on COPY stream
2024-02-08T03:58:08.478796Z  INFO {cid=5 ttid=941ddc8604413b88b3d208bddf90396c/4af489b06af8eed9e27a841775616962}: got query "IDENTIFY_SYSTEM"
2024-02-08T03:58:08.479278Z  INFO {cid=5 ttid=941ddc8604413b88b3d208bddf90396c/4af489b06af8eed9e27a841775616962}: got query "START_REPLICATION SLOT \"repl_4af489b06af8eed9e27a841775616962_\" 0/5000000 TIMELINE 1"
2024-02-08T03:58:08.479321Z  INFO {cid=5 ttid=941ddc8604413b88b3d208bddf90396c/4af489b06af8eed9e27a841775616962}:WAL sender: starting streaming from 0/5000000, available WAL ends at 0/5079910, recovery=false, appname=Some("replica")

I was able to reproduce the problem with neon_local and the following simple shell script:
neon_local init
neon_local start
neon_local tenant create  --pg-version=16 --set-default
neon_local endpoint create --pg-version=16 main
neon_local endpoint start main
echo "shared_preload_libraries='neon,timescaledb'" >> .neon/endpoints/main/postgresql.conf
neon_local endpoint stop main
neon_local endpoint start main
neon_local endpoint create --pg-version=16 --branch-name main --hot-standby true
neon_local endpoint start ep-main
psql "port=55432 user=cloud_admin dbname=postgres" -c "create database empty"
psql "port=55432 user=cloud_admin dbname=empty" -c "create extension timescaledb"
psql "port=55434 user=cloud_admin dbname=empty"

This crash is not reproduced in my PR giving LR problems:
https://github.com/neondatabase/neon/pull/6357
And I have theory explaining why...

Hi @knizhnik, I've built images from your branch (commit 32f4a563) and it does appear to solve the create extension timescaledb crash. Excellent work!
However I noticed I was still seeing the replica node crash sometimes, so I tracked down queries I ran and found I can also reproduce the crash by altering database timezone:
psql "host=localhost port=55433 user=cloud_admin dbname=postgres" -c "create database test"
psql "host=localhost port=55433 user=cloud_admin dbname=postgres" -c "alter database test set timezone to 'Australia/Sydney'"

This doesn't crash the replica immediately, but replica seems to be in a bad state, e.g. repeated [85] FATAL:  database "postgres" does not exist logs.
Then if the timezone-altered database is dropped or timescale extension is created, the replica crashes:
psql "host=localhost port=55433 user=cloud_admin dbname=postgres" -c "drop database test"
# OR
psql "host=localhost port=55433 user=cloud_admin dbname=test" -c "create extension timescaledb"

Error for drop database:
PG:2024-02-12 04:36:46.000 GMT [27] WARNING:  page 0 of relation global/2964 does not exist
PG:2024-02-12 04:36:46.000 GMT [27] CONTEXT:  WAL redo at 1/479F8200 for neon/DELETE: xmax: 11827, off: 64, infobits: [KEYS_UPDATED], flags: 0x00; blkref #0: rel 1664/0/2964, blk 0
PG:2024-02-12 04:36:46.001 GMT [27] PANIC:  WAL contains references to invalid pages
PG:2024-02-12 04:36:46.001 GMT [27] CONTEXT:  WAL redo at 1/479F8200 for neon/DELETE: xmax: 11827, off: 64, infobits: [KEYS_UPDATED], flags: 0x00; blkref #0: rel 1664/0/2964, blk 0

Error for create extension timescaledb:
PG:2024-02-12 04:45:57.159 GMT [27] FATAL:  unexpected data beyond EOF in block 0 of relation global/2964
PG:2024-02-12 04:45:57.159 GMT [27] HINT:  This has been seen to occur with buggy kernels; consider updating your system.
PG:2024-02-12 04:45:57.159 GMT [27] CONTEXT:  WAL redo at 1/4B333DF8 for neon/INSERT: off: 69, flags: 0x00; blkref #0: rel 1664/0/2964, blk 0 FPW

Please notice that although the problem in not reproduced in #6357 branch (which changes request LSNs for  pages fetched by replica), the real fix is in #6371


Finalize top-level API

[x] Finalize API for writing to deltalake
[x] Rename read_delta_table -> read_deltalake; temporarily keep an alias for the old name with DeprecationWarning
[x] Remove vacuum and history; user can use deltalake.DeltaTable for that
[x] Add documentation for to_deltalake to README

Closes https://github.com/dask-contrib/dask-deltatable/issues/42, https://github.com/dask-contrib/dask-deltatable/issues/17, https://github.com/dask-contrib/dask-deltatable/issues/16.

Codecov Report

Merging #46 (4b392d2) into main (045481b) will decrease coverage by 2.57%.
The diff coverage is 84.61%.

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
@@            Coverage Diff             @@
##             main      #46      +/-   ##
==========================================
- Coverage   76.63%   74.07%   -2.57%
==========================================
  Files           6        6
  Lines         351      324      -27
==========================================
- Hits          269      240      -29
- Misses         82       84       +2

Impacted Files
Coverage Δ

dask_deltatable/core.py
89.41% <66.66%> (-4.51%)
:arrow_down:

dask_deltatable/__init__.py
100.00% <100.00%> (ø)

dask_deltatable/write.py
65.51% <100.00%> (+1.23%)
:arrow_up:

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more

Windows tests fail uploading coverage to codecov.


Drowning bug [Feature] Bug explanation

Well i am curently in the ocean and im not loosing and of the bubbles at all im not sure if this is s bug or my game is lagging just thought you guys shoukd no about it.
Expected behavior
to drown and take damage
Screenshots
If applicable, add screenshots to help explain your problem.
Narcia_*
**Server name titan

Could not be reproduced, closing.


🌱 Bump golangci-lint, remove staticcheck

Summary
This is some housekeeping for our linters.

Originally, the idea behind running staticcheck standalone was that "golangci-lint should find deprecation, but it doesn't work" (in #1798). I checked and could not immediately see deprecated code that golangci-lint doesn't find by itself.

Additionally, #1798 doesn't even enable the necessary check in staticcheck. Instead we configured:

ST1019 - duplicate import statements
ST1005 - error strings should not be capitalized

Both of these things can be accomplished using revive. However we have to lower the minimum confidence level from 0.8 to 0.6 to surface these issues correctly. staticcheck (the standalone binary) has some additional smarts and produces fewer false positives because it recognizes code identifiers in error strings. However a few //nolint comments are to me an acceptable downside, compared to keeping a dedicated linter around.

A whole bunch of functions in our SDK implicitly do a fmt.Sprintf(), which newer golangci-lint versions are complaining about if non-constant format strings are used. I pondered multiple solutions, but ultimately chose the simplest one that doesn't cause an API break (by calling MarkFalse(reason) now as MarkFalse("%s", reason)). Other options would be possible, like introducing new functions (MarkFalse and MarkFalsef) or removing the sprintf functionality alltogether, however since it's part of the SDK package, I feared an API break.

Release Notes
Update golangci-lint to 1.26.2, remove dependency on standalone staticcheck binary

/approve
/lgtm


How can I detect changes on Twitter?

Hey, what is the CSS element for the the name dispalyed & bio and the tweet count at the top .
I've tried using inspect element and I can't figure out what it is.
When I put what I believe to be the right element in the CSS/JSON/XPATH Filter, it shows up as empty so I guess I'm puttin in the wrong element? Can someone put my in the right direction?

Any ideas? How do I monitor all these 4 elements? I'm completely lost (which is my own fault I think).

If someone could send some screenshots to explain it a bit better that'd be appreicated cause I really do want to use this piece of software a lot! And not just for Twitter, I'm aware I can use the API for this type of stuff but I want it all in one place.


feat: implement non-native field emulation

This PR adds a new standard gadget std/math/nonnative for performing non-native field operations in a circuit. It is trying to follow big.Int-like interface, but is not completely compatible.
The PR is mostly ready, but still some things to do:

[x] add tests for more complex computations
[x] implement Select and Lookup2
[x] write a nice documentation which lists all the assumptions the library does to ensure the validness of the computation

Marking this version as ready to review as is. It is functionally complete, but lacks several optimisations I will implement in a new PR. When reviewing, I suggest to start from std/math/nonnative/doc.go (or look at the package documentation with godoc) for general description and then (in parallel) look at std/math/nonnative/variable.go.

will it support Sqrt?

will it support Sqrt? @ivokub

Currently Sqrt is not implemented in the PR, but it should be easy to add. Will add the Sqrt method soon.

when will this PR be merged? @ivokub

I believe it is being reviewed right now. Cannot promise ETA but hopefully shortly.


206 fe fix layout responsiveness  logo size on mobile

https://github.com/learnhubmkd/app/assets/105276163/eff11eea-711b-47a0-8725-138837f50363
There is an overflow and it still doesn't look good on mobile.

You need to add width to the main tag;
Go through all the sections and check which have a max-width/ min-width added;
Check the image in the hero section and fix width there


drivers: clock_control: nrf driver reimplementation

Clock_control has been re-implemented to support new clock control API and calibration algorithm which optionally uses temperature sensor and skips calibration on no temperature change.

Added new API implementation
Added calibration algorithm (calibration support extracted to separate file)
Added test suite
Updated usage of clock _control API in nordic drivers, removed hacky usage of subsys parameter.

Requires #17301

@nordic-krch In https://github.com/aescolar/zephyr/tree/clock_control_calibration_fix  you have this branch with a couple of updates for simulation and rebased on top of #17301 . With it the nrf52_bsim works nicely

@pizi-nordic @cvinayak @ioannisg anyone would find some time to do the review? @anangl did quite extensive one but we need another to get that in.

@pizi-nordic @cvinayak @ioannisg anyone would find some time to do the review? @anangl did quite extensive one but we need another to get that in.

I think we should all review this; it is a major driver, affecting all systems in nRF platforms. I am going to do a pass; for now, I am a bit concerned whether this increases RAM usage... I saw, here, a ram-usage fix in one of nRF51 tests, and I started thinking about it. We should are to re-work the driver, we need to ensure this does not bring further overhead for the resource-constrained nrf51 SOC

@ioannisg

I am a bit concerned whether this increases RAM usage...

It's only couple of bytes and that brought your attention only because there was a test that was using 99,5% or RAM. There are dozens of places where ram is wasted. It's increased mainly when LF RC is used because of async data structure required (12 bytes).

Rebased.
@pabigot it's no longer blocked by #17301.
@pizi-nordic long time ago you were soo close to approve, then vacation time came. Can you take another look?

It's been out for 3 months. There are 3 approvals. @carlescufi @ioannisg can we merge this then unless someone plans to review it soon?

For the record, I have no issue with this PR. The only file changed I own is perfectly fine. But as this is a Nordic only change, I do not believe I should approve it. I presume BT and USB maintainers would have a similar feeling as the BT and USB code changes are minor and circumstantial.

It's been out for 3 months. There are 3 approvals. @carlescufi @ioannisg can we merge this then unless someone plans to review it soon?

I would appreciate if @pabigot could re-review once more (and approve if possible). I guess we can merge this afterwards ;)

I haven't looked much at the code, this switch to zephyr is all new to me, so I am still confused. So so this is more a question than a suggestion.  After this PR we will still use the Calibration timer in the NRF_CLOCK peripheral right? how easy would it be to switch to using some other source for the periodic timer to drive the calibration state machine in zephyr world? we always wanted to do that in SoftDevice, but never did. The calibration timer in in NRF_CLOCK has some big awkward weaknesses, since some register can not be written withing the same 32khz clock cycle as some things happens. Another reason to stop using the calibration timer, is that we want to remove it from the chip, to save silicon, if sw could do without it.

@martintv i don't see any obstacles. In the next step we can replace calibration timer with k_timer.

@ioannisg see @pabigot comment. What then blocks as from merging it?

@ioannisg see @pabigot comment. What then blocks as from merging it?

Your description is still blocking this PR @nordic-krch.
#17301 is not reviewed/merged. Please, advice

@ioannisg i've updated description as this is no longer true. I don't use functionality which #17301 attempted to add.

@ioannisg i've updated description as this is no longer true. I don't use functionality which #17301 attempted to add.

OK, great, now this PR is not blocked-by-definition ;)
Could you rebase and run CI (PR hasn't been rebased for ~10 days, AFAICS)

@ioannisg, done.

There is by default a lot of info lines being printed. Can we change the settings so that that doesn't happen?
[00:10:10.496,673] <inf> clock_control: CLOCK_16M: callback
[00:10:10.496,704] <inf> clock_control: CLOCK_16M: node 0x0000000

There is by default a lot of info lines being printed. Can we change the settings so that that doesn't happen?
[00:10:10.496,673] <inf> clock_control: CLOCK_16M: callback
[00:10:10.496,704] <inf> clock_control: CLOCK_16M: node 0x0000000

Tested connections using 2 nrf52840. and 500 PPM, works fine.

I saw that as well, I assumed this was my config but now that @joerchan also brings it up I think this is worth cleaning up. @nordic-krch could you please disable those by default?

@carlescufi @joerchan removed those log calls.
@carlescufi I've reduced irq locking time. Additionally, i did measurement to check longest locking time in clock driver vs other lockings (used peripheral_hr sample for that). Clock locking is up to 1.4us while there are many many more longer lockings (up to 2.5ms which seems very odd). In general locking in clock is one of the shortest.

@carlescufi @joerchan removed those log calls.
@carlescufi I've reduced irq locking time. Additionally, i did measurement to check longest locking time in clock driver vs other lockings (used peripheral_hr sample for that). Clock locking is up to 1.4us while there are many many more longer lockings (up to 2.5ms which seems very odd). In general locking in clock is one of the shortest.

Thank you @nordic-krch. I will merge this as soon as CI passes.


documentation: updated example image (fixes #111)

I can get a larger image if necessary.

I would prefer a larger image, and also one that shows off the error linkification

Increased image size as requested.
I am unsure what do you mean by the linkification. Do you want me to change the link text in the example (to show "link" or something similar instead) or to update code_linking.png?
Sadly my command line doesn't seem to be able to display links like that (I am on Windows), so I can't show it off.

@TrapinchO the new Windows Terminal supports the feature:

I meant link tooltip, as seen on the current code_linking image.
I am afraid I don't understand what you want me to do. The error already includes a url. The other image is large enough and is about a different error.

The problem is that it's displaying a URL at all. It should show the dashed underline instead.

This is the best I got to, no underline (url("(link)")). Cannot test whether it works due to windows terminal.

I would like to note that replacing docsrs with a string seems to display it whole and not just (link) and the documentation doesn't seem to show how to hide the link.

Was thinking to make the same PR, but I see this is already made. I can make an image and share here or make another PR if you want?
Seems the <img alt="..."> in the readme should change too. And I noticed lib.rs has a copy of the readme. I tried replacing it with #![doc = include_str!("../README.md")], but then tests started failing so I'm guessing that's why.

I have no problem with either. If you post it, I will update the pr, but feel free to open a fresh one.

Here you go. The underline on oops::my::bad (Files) only shows up when I mouse over it, at least on Alacritty terminal in Linux. I had to zoom way in to get the resolution higher, mouse over the link, and take the screenshot with grim, and then crop the result in gimp.

This latest one looks good to me, thanks :)


Create a Showcase page

Create a Showcase page that'll display community projects that are built with Chakra UI. Use the #🌟-showcase channel on Discord and the Awesome Chakra UI repo to gather the initial data. Categorize the data entries similarly to the Awesome Chakra UI repo.
You can use the https://nextjs.org/showcase for inspiration.

Can I work on this one?

Hi @lazarnikolov94, since there is no preview image in the Awesome Chakra UI repo. I'd like to use puppeteer to write a script to get preview images.
Is it ok to add a new package?

Hi @lazarnikolov94, since there is no preview image in the Awesome Chakra UI repo. I'd write script with puppeteer to get preview images if there is a website existed.
Is it ok to add a new package?

Uh, I misclicked un-assigned


Fixed error with non-standard base

Closes #11
The name is actually prefixed not with a slash, but with the config base. This PR takes that into account.

Nice, I was actually just about to make the same PR, would be good to get this merged :)

Hi @aral, is there anything I can do to push this forward? Thanks!


Fixed DateTime parsing

When creating or updating a page with a field of type DateTime, it produces the error Call to a member function format() on string. This pull request provides a fix for this bug by parsing the given string into the expected DateTime.

:tada: This PR is included in version 1.0.0-rc.1 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Map is empty

Hello,
We are getting an empty map in Go from "new Map([['a',1], ['b', 2]]);" in the following one liner script. We've also tried keys() to see what's going on but that also turns out to be an empty map. We would appreciate your expertise on this matter. Thanks.

Testcase go code

package main
import (
"fmt"
"github.com/dop251/goja"
)
func main() {
vm := goja.New()
r, _ := vm.RunString(    m = new Map([['a',1], ['b', 2]]);    )
v, _ := r.Export().(map[string]interface{})
fmt.Printf("Map is empty: %#v\n", v)
}

Execution result
Map is empty: map[string]interface {}{}

Here's a simpler code without type casting:
vm := goja.New()
r, _ := vm.RunString("var m = new Map([['a',1], ['b', 2]]);")
v := r.Export()
fmt.Printf("Map is still empty: %#v\n", v)

Currently Export() for Maps works as for any regular Objects, i.e. exports enumerable properties which there are none. Same way Object.keys(m) would return an empty array.
The problem here is similar to what I described in #336, however I gave it a little bit of thought and I think something like this could work:

Export() for Map and Set will return goja.Map and goja.Set which will contain regular access/manipulation methods (Get/Set/Has/Delete/Add). Similar to how it's currently done for Proxy or Promise.
ExportTo() for Map will export the Map's contents into the specified typed map.
ExportTo() for Set will export the Sets contents into either a map (where values will be set to zero) or a slice.

Note that ExportTo() will panic if the value used as a map key is not hashable (same way as reflect.Value's SetMapIndex() would panic).
What do you (or anyone else interested) think?

Hello Dmitry,
I admire your work and appreciate that you took time to offer your insightful advice.
Here's what we have found after some experiments:

Casting to *goja.Object revealed the regular access/manipulation methods such as 'has' and 'get' at which we were very excited. Then we realised that the challenge we have is that we do not know the keys in advance in order to utilise 'get' or 'has'.

We were delighted to try out ExportTo() which we had not been aware of. Then we were saddened by the result which showed an empty interface{}:

Code
value, _ := vm.RunString("var m = new Map([['a',1], ['b', 2]]);m;")
var exportTo map[string]interface{}
err := vm.ExportTo(value, &exportTo)
if err == nil {
fmt.Printf("ExportTo: %#v\n", exportTo)
}
Result
ExportTo: map[string]interface {}{}

We wish there were a way to get the keys so that we could at least utilize 'get' that you advised  in order to access the values. We would appreciate your expertise on this matter.
Best regards,
Nicholas

First of all I highly recommend you to read the README and the reference documentation. It's not the best in the world, but it's there and at least it has all public methods mentioned.
What I mentioned in the previous comment was a proposal, none of it it implemented right now, and I have doubts about what would be the best approach, especially for the Export(). The problem with the approach I mentioned is that if you override Map methods (such as get() or has()), it will be tricky to make goja.Map.Get() and goja.Map.Has() use those. It also raises a question about exception handling (your custom methods can throw, whereas default Map methods cannot). Also, as you've mentioned, you can still use Map's methods by converting the value to *Object, so this wouldn't add any new functionality.
Another possibility would be that Export() return map[interface{}]interface{}. However it's not possible for a map to have non-hashable keys (for example a slice or a struct with a slice field). What's more, there is no easy way to tell if a type is hashable and there is no 'safe' SetMapIndex() equivalent, one that would return an error instead of panicking.  But even if there was, Export() is supposed to always work, it does not return an error. And having a possibility of Export() panic on certain values doesn't sound good to me.
Another option could be returning a list of entries in the form of [[key, value], ...] as [][]interface{}. This would make it somewhat more useful than the current version.
As for your question about map keys, see https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Map/keys. I might add a method to simplify using ES iterators from Go (i.e. ForOf(iterable Value, step func(v Value) (continue bool, err error)) error).
Another advice would be to consider whether you really need to use Map for values exported to Go at all. Using a simple Object may be an easier option.

Hello Dmitry,
Thank you for recommending the README and the reference documentation which have been very helpful.
[][]interface{} is a fantastic idea. We hope it can be implemented soon. Unfortunately our requirement is to use Map instead of a simple Object.
We appreciate your help and your wonderful work.
Best regards,
Nicholas


Added some more terms, fleshed out some definitions.

Howdy,
I tried to sync up the repos before I started this effort but Github said we were in sync already. Hopefully this pull request won't cause any heartache!
As always, please let me know if there are issues with the request.
Thanks!
E.

Hi @modalpdx ! Don't you worry, we'll get this figured out.
Because you are working with a fork of this repository, you will from time to time need to pull from this (lyzadanger/JSoT) repository, which is the "upstream" repository from your fork. Simply doing a git pull from origin on your own master branch won't get the changes from this repository.
I can see that your fork doesn't yet have the commits from this weekend merged:

Here are some docs about how to sync from upstream:
https://help.github.com/articles/syncing-a-fork/
Totally happy to help walk you through this if you have any trouble!

Wow, talk about instruction failures...the first time I sync'd the repos I used the instructions listed here:
http://stackoverflow.com/questions/20984802/how-can-i-keep-my-fork-in-sync-without-adding-a-separate-remote/21131381#21131381
That appeared to work. I tried to run through them again before changing the README.md file today and nothing looked quite the same as in the instructions so I figured we were in sync. Yep, never assume.
I'm throwing away those instructions. I like yours much, much better. :)
I have run through them and sync'd everything up, fixed merge conflicts, and pushed to my fork.  Just let me know.
Thanks, and sorry 'bout this!
E.

First: Please don't feel sorry! We all go through this! It's happened to me, for sure.
Why don't you go ahead and open a new PR? Potentially less confusing.

Will do.


Consume information about failed device instantiation and expose information to REST API

Requires https://github.com/DiamondLightSource/dodal/pull/62 to be merged.
Part of #198, as allows start up when not all devices are connected (desired behaviour replacing plan setups)

superceded by #515 , petition to close @callumforrester

How does #515 cover this?

@DiamondJoseph I think we should close this since its very out of date. If we want to expose this via the API we should make another issue for that?


Upscale

How can I set "upscale" to false?

I checked the jimp documentation and I found no mention of 'upscale' as a parameter that you can set to false. Are you asking how to resize but prevent upscaling? This lib passes the config params to jimp so you might want to check there to see how to resize w/o upscaling.

Yes I want to prevent upscaling.
I want to generate thumbnails for big images and just copy small without resize.

My guess is that you would have to read the size of the image before you resized it. There is nothing in this library to do that for you. Best to read the JIMP documentation.


Java: Unable to find maven package for OpenAI services

According to these docs https://github.com/microsoft/semantic-kernel/blob/java-v1/java/PACKAGES.md, there should be a semantickernel-connectors-ai-openai package, but it does not appear to be available on Maven.

the package you are looking for is:
            <dependency>
                <groupId>com.microsoft.semantic-kernel</groupId>
                <artifactId>semantickernel-aiservices-openai</artifactId>
            </dependency>

Worked after doing mvn clean install -U