use of closed network connection

Copied the code on the homepage, but now I print out the error from http.Serve().
./test
2019/06/06 15:42:07 [overseer master] run
2019/06/06 15:42:07 [overseer master] starting /tmp/main/test
2019/06/06 15:42:07 [overseer slave#1] run
2019/06/06 15:42:07 [overseer slave#1] start program
2019/06/06 15:42:07 app (f81a86c0d7a5120aa306900493dacb542143ca66) listening...
2019/06/06 15:42:45 [overseer master] graceful restart triggered
2019/06/06 15:42:45 [overseer slave#1] graceful shutdown requested
2019/06/06 15:42:45 accept tcp [::]:3000: use of closed network connection
2019/06/06 15:42:45 [overseer master] signaled, sockets ready
2019/06/06 15:42:45 [overseer master] starting /tmp/main/test
2019/06/06 15:42:45 [overseer master] restart success
2019/06/06 15:42:45 [overseer slave#2] run
2019/06/06 15:42:45 [overseer slave#2] start program
2019/06/06 15:42:45 app (f81a86c0d7a5120aa306900493dacb542143ca66) listening...
The problem is that when I do a kill -s SIGUSR2 PID, I sometimes get an error along the lines of:
accept tcp [::]:3000: use of closed network connection
Ideas?

I have the same problem, also in fvbock/endless.
why?

I also am running into this. Any discoveries on this end?

same


NEW REPO! DO NOT OPEN ISSUES HERE

This is the new home of this library: https://github.com/Bungeefan/logger

Is it? Why not archive this repo?
Is this fork published on pub.dev? Is flutter_logger forked and published too?
As someone looking to start using logger, its quite confusing where to start, and what is or isn't maintained.

This is because I took over the maintenance of this repo some time ago. But I wasn't assigned admin rights (I also forgot to ask).
I want to step back from this project and have found several very capable new maintainers. But because I do not have admin rights, I cannot add new maintainers. Nor can I archive this repo. I've tried contacting the original author several times via several routes but he is unresponsive.
That is why the repo is now forked. That fork is now the canonical repo.
I did have admin rights on pub.dev, so nothing changes there. The new maintainers will push new versions there.
I never took any ownership of flutter_logger, so I can't comment there.

Hi, I am one of the new maintainers of this project, alongside with @Oliinyk-Volodymyr.
Unfortunately, as Harm mentioned, we cannot use the original repository, but we are able to upload and maintain the pub.dev package.
We've already talked about flutter_logger package and whether we should provide a fork for that as well.
At the moment there is no definite answer to this, however my opinion is that if there is enough demand for it, we can certainly try to fork it and publish it as a new package on pub.dev (since none of us has access to the original).
On the other hand, there are already some maintained forks with their respective packages on pub.dev, so you could probably use one of those without any problems.
See https://github.com/simc/logger_flutter/issues/24#issuecomment-1341278449

See also https://pub.dev/packages/logger_flutter_plus

@Bungeefan @haarts Please create/reuse a Github org for the forked package, similar to say hivedb, rather than moving it under another single user. That way changing maintainers will not involve changing repos, avoiding confusing situations like this which also lose issues / analytics / etc. Using orgs also makes it clearer who has permissions for the org for newcomers and thus who to contact when permissions are needed.
I also suggest adding at least two people with admin rights to the org, ideally 3+, to avoid one person leaving the project resulting in the need to fork. The non-primary admins need not be currently active in the project, just reasonably active on Github so they can act as a backup point of contact.
Aside: please keep using the flutter_logger package - this isn't a 'true' fork afaict, just maintenance changing hands due to an absentee admin, so no need to change the name.

@holocronweaver
Sorry for the long delay for a proper response, I would certainly welcome an organization for the logger repository, however we need a proper name for it that doesn't need to be changed it in a year or so.
We are not really affiliated with anything, nor was there a brand name (or similar) before, and we cannot name it "logger".
So if anyone has got a good unused name that we can use, I am ready to create an org and move logger under it.

@holocronweaver Your wish has come true! :tada:
I am happy to announce that the logger repository  is now under a new organization with both me and @haarts as owners!


Return Share URL after upload

Hi
Thank you for you lib.
But, Can you add some feature, after upload image, it will return "share url" to access that image.
Thank you again.

This feature exists.
This is the function: https://github.com/storj-thirdparty/uplink-php/blob/264b074f830f69e6d2a6fb9c442f35d3b1b7c10b/src/Edge/Edge.php#L84


Enable capacity support for LVM CSI

Chart updates to enable capacity tracking by default, with support being added in PR https://github.com/metal-stack/csi-driver-lvm/pull/89.

The chart version has to be bumped (we prevent overriding existing releases) in https://github.com/metal-stack/helm-charts/blob/master/charts/csi-driver-lvm/Chart.yaml#L2.


Global graph settings: autoLayout

change to layout, with setting 'default'/'horizontal'/'vertical'. Remove orientation (which doesn't do anything if autolayout is set to false?) Add an entry to DEVELOPMENT.md about where the layout is implemented and how to create a new layouting algorithm

The default value of orientation is "horizontal". Change in example 3 the orientation to vertical. This is the result:

The reason why the connections are different is because sourceHandle and targetHandle are not defined. So in a vertical layout, it makes sense to connect the nodes at the top and the bottom, if the nodes are below each other.
The algorithm can be found here: https://github.com/TiboStr/dataflow-visualization/blob/d11452d3830081d567eab88cbbcd59145642b8bb/src/custom/editors/editorUtil.js#L319-L374
The idea is very simple.

If the layout is vertical,

Check if the nodes are on top/below each other

If so, the connections are the top/bottom
If not so, the connections should be at the side.

Else if the layout is horizontal (default):

Check if the nodes are adjacent

If so, the connections are left/right
If not so the connections should be top/bottom

Ah yeah, I didn't realize that 'orientation' is also relevant when 'autoLayout' is set to false, OK!


xcaddy build failure

Repro
xcaddy build --with github.com/caddy-dns/tencentcloud
Expected
Successfully build.
Actual
2024/11/14 17:09:01 [INFO] exec (timeout=0s): /home/zhizhen/bin/go/go/bin/go get -v
2024/11/14 17:09:03 [INFO] Build environment ready
2024/11/14 17:09:03 [INFO] Building Caddy
2024/11/14 17:09:03 [INFO] exec (timeout=0s): /home/zhizhen/bin/go/go/bin/go mod tidy -e
2024/11/14 17:09:04 [INFO] exec (timeout=0s): /home/zhizhen/bin/go/go/bin/go build -o /home/zhizhen/caddy -ldflags -w -s -trimpath -tags nobadger,nomysql,nopgx
# github.com/caddyserver/caddy/v2
/home/zhizhen/go/pkg/mod/github.com/caddyserver/caddy/v2@v2.8.4/context.go:541:12: undefined: zapslog.HandlerOptions
2024/11/14 17:09:04 [INFO] Cleaning up temporary folder: /tmp/buildenv_2024-11-14-1708.1373625778
2024/11/14 17:09:04 [FATAL] exit status 1

I am experiencing the same issue and error as described. I have been using GitHub Actions to automatically build Caddy with this plugin. However, since around two weeks ago, the build process consistently fails when including this plugin.

When I revert this merge, everything's fine.
Hope @ysicing have a look.

The current tagged release is still broken it seems.
If the master branch is working, could we create a new tag against it as that is the default spot for the xcaddy builder to pull from.


fix: task dependency

Description:
Summarize the changes you're submitting in a few sentences, including Jira ticket ATL-xxxx if applicable. Link to any discussion, related issues and bug reports to give the context to help the reviewer understand the PR.
Alternatives Considered (optional):
Link to existing ADR (Architecture Decision Record), if any. If relevant, describe other approaches explored and the selected approach. Documenting why the methods were not selected will create a knowledge base for future reference, helping prevent others from revisiting less optimal ideas.
Checklist:

[ ] My PR follows the contribution guidelines of this project
[ ] My PR is free of third-party dependencies that don't comply with the Allowlist
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] I have checked the PR title to follow the conventional commit specification

The changes look good, but would be good to change the description to something that describes the work done.


feat: pass extra volume attributes to static PV (Issue #2114)

Feature
when using pre-provisioned volumes, pass these parameters in spec.csi.volumeAttributes in PV declaration:

kernelMountOptions
fuseMountOptions
subvolumeGroup

Related issues
#2114

Hi! Thanks for your PR :+1:
Please see the Developers Guide which explains how to format commit messages. In this case, the subject could be
cephfs: pass extra volume attributes to static PV

The last line of the commit message should include Signed-off-by: <name> <email> (use git commit --amend -s).
In your PR description, you can include Fixes: #2114 so that the issue automatically gets closed once this PR is merged.

https://github.com/ceph/ceph-csi/pull/2127/checks?check_run_id=2727773249

@YingshuoTao DCO is failing can you please fix it.

@Madhu-1 I've just fixed it, please take a look, thanks.

Sorry, there were differences between my local git user config and github user config, which caused DCO failure. Now it should be fixed.


Documentation

I spent about an hour evaluating hdf5.node, and didn't make much progress. There some misdirection in the README.md and the link to the api appears to be out of date. Looking at the recent commit history and test suites is helpful.
I would suggest two concurrent steps to improve the documentation:

Update the README.md to be similar in style and quality to popular node projects. The README.md on express looks like a good model. Having README sections Installation,  Features, Philosophy,  and Docs & Community would be helpful for users and contributors. It's important to say up front what hdf5.node does and does not do.

Discussion forum on Gitter or Google Groups. Searchable discussion forums outside of issues could attract new developers, help focus the scope and goals, and nucleate new ideas. I've used Slack and Google Groups on other projects, but Gitter might be the best match for this project.

If other developers think this is a good idea. I can jump in and do this. I (or someone else) should probably set up the discussion group first, since I have some questions about the existing README.md file. I also need to make sure I understand the philosophy and vision behind this project. I don't want to add any additional confusion about the scope or goals.

The readme.md is out of date with the splitting of the core from my experiments and reference viewer.
Did you follow the link to http://rycole.com/hdf5.node/?  It will need some updating or additions.
I'd've cut readme.md down quite a bit and published again but the changes to hard-coded paths in binding.gyp https://github.com/HDF-NI/hdf5.node/blob/master/binding.gyp#L3 to native hdf5 libs is problematic for users who don't install that way; In the past I had an environment variable
export HDF5_HOME=/home/roger/NodeProjects/hdf5
to set it http://rycole.com/hdf5.node/doc/install-setup.html
Trying to resolve the issue; this does't work when hdf5.node is a sub module of another project yet
https://github.com/nodejs/node-gyp/issues/893

Ah when the project was moved under the HDF-NI organization the gh-pages https://github.com/HDF-NI/hdf5.node/tree/gh-pages automatically republished!  Nice of github to do that:-)
http://hdf-ni.github.io/hdf5.node/
so the link can be changed

Nice! This is making more sense now. The rycole.com domain and the out-of-date “Getting Started” page  that refers to ./lib/application.js really threw me when I first looked at it. @vincent-tr 's #18 commit message on the libs directory got me back on track.  I can do some small updates to the master README.md, then mostly go through the gh-pages to see that all the tutorials work correctly in the current version.
Regarding building and runtime: HDF5_HOME is most convenient when it works. Because I did an npm install hdf5 directly that worked great for me. As an additional complication, it's probably more convenient to link to static libraries, since that's possible in node. Setting LD_LIBRARY_PATH has always been a pain with the Java wrappers and tools.

Oh before going too far github sent me a notice they will no longer be supporting  'redcarpet' Markdown engine but the 'kramdown' engine.  Not sure how different these two formats are.
Also this project uses node-pre-gyp and I have prebuilt versions up on amazon S3 which get pulled by npm install hdf5 or when included in another package as a module. Many users don't need native compiling at all.
Static linking would solve one problem; I was hesitant over licenses and because I didn't know if there could be an incompatibility to a user's h5 files across versions;  although hdf5 has been very stable.  Have to ask more people how this would effect them.  It definitely would make the prebuilts matrix smaller

A web socket layer and the application/hdf5 viewer/editor are moving to their separate projects under https://github.com/HDF-NI organization.  You have access to it
You and @vincent-tr now have write access to hdf5.node as well(discovered I can change settings now that @ryancole moved it to HDF-NI.
Had all my hdf5 interface efforts in one project while I was experimenting and was happy when @vincent-tr  decided to help split the core hdf5.node as a pure API so other projects don't need my extra or experimental dependencies such as binaryjs[which is being replaced] and koa etc.
I have browser tree views and editing which I'm rewriting ad putting into other projects. Had table data going to an ethercalc spreadsheets.
Now with a rewrite I'm making a  web socket endpoint api to provide access in browser pages to hdf5 data.

Also am thinking of a separate image layer for sending large images to the browser. Geo and weather and map data

npm install  --build-from-source --hdf5_home_linux=<pathtoyourhdf5install>

does work; also if a dependent project puts the --hdf5_home_linux switch on its install line it works from there too.
We cut down the readme.md for this core project, update links and I'll publish it to npm and provide the prebuilts for mac, windows and linux

I tested changing to kramdown markup in another project https://github.com/rimmartin/saxon-node/blob/gh-pages/_config.yml#L46
Change most needed was a linefeed before blockquotes

OK, I now have jekyll running locally and I'm seeing some of those formatting issues with kramdown. I'm working on that now.

Ah good.    codeblocks are different too.  I'll test more on linux and in the morning build on windows and mac to be ready to publish and upload the prebuilts.
./bin/jekyll-page
Is a little helper script for setting up new pages; .md is tagged on automatically
I had started with https://github.com/bruth/jekyll-docs-template
Let me know what else you may need

I updated the readme.md. Please leave me feedback if there are any problems with my edits. I added badges to the top, reorganized headings a little, then removed the description of the viewer.
Sorry for the multiple commits. I'm out of practice with git, then I made a mess when I tried to amend my missing edit. It was a simple edit (deleting the viewer description in the readme), but the log got botched by splitting into three commits.

Good going!  Ill look thru..
We should be able to publish to math the docs soon

For users who don't have hdf5 libraries installed at the path of https://github.com/HDF-NI/hdf5.node/blob/master/binding.gyp#L3
the hdf5_home_linux is now a switch:

and in dependent projects it also is passes thru
cd /home/user/NodeProjects/hdf5.ws
$NODE_HOME/bin/npm install  --hdf5_home_linux=/home/user/NodeProjects/hdf5

and there is a different one for mac and windows which work similarly.
Where we talk about building we can reduce questions by stating this clearer than what I just did

Published to npm


opening the enchiridion crashes your game

everytime i open the enchriridion book, it crashes my game
this is the error i get with it
The game crashed whilst unexpected error
Error: java.lang.NoClassDefFoundError:
vazkii/patchouli/common/book/BookRegistry
Exit Code: -1

Can confirm, happens every time with the same error.

I use Conjuring 1.0.23 without Patchouli

There was an oversight when porting Conjuring for trying to load Patchouli, but a 1.19 version is available as a snapshot on their Maven. You can download it there.
It seems a bit pointless to make a release disabling Patchouli, only to re-enable it in the (possibly near) future.
For now you will simply have to install Patchouli or remove the Enchiridion somehow (datapack to remove recipe or kubejs would work)

Given that there is no real problem apart from Patchouli not being declared as a dependency, I will close this issue for now and pin it to prevent future confusion. Check the above comment from Noaaan for where to download 1.19 builds of Patchouli
Cheers


crypto/tls: ambiguous comment in cipher_suites.go

https://github.com/golang/go/blob/master/src/crypto/tls/cipher_suites.go#L77
This line says "RC4 comes before AES (because of the Lucky13 attack)" when it should be clarified that AES-GCM is safe and therefore preferred over RC4.

https://go-review.googlesource.com/#/c/19845/


Adjust namespaces to be replaced using parameters

Provide the ability to custom the namespaces by creating the project like:
dotnet new cleandddapi -n "MyNewCleanTest.API" -c "MyCompanyName" -p "MyAwseomeProduct"

PR Inception ;)

usings in most files are not sorted, can you do that @jorsang1?

I guess now it should be good to merge....

Closed by mistake.... :-D


Suggestion: one repo per package

I don't know how others work on packages locally, but I use the PACKAGE_DIRS technique personally. So when I want to work on a package, I usually just clone the repo into my package directory and it just works.
Since this repo contains two packages though, I can't really do that. It's not a huge problem, but I was thinking if you want to get more contributors it might be good to make it even easier to get started cloning the packages? Curious to know what you think.

The directory structure was set up to match how MDG does some of their repos.  I understand the issue you are having but I'm not going to break it out at this time.
I don't see a lot of people making pull requests to this repo since it was designed to be customizable.  I expect most changes to just be overrides of parts a developer want to be different.  If I do see a lot of useful PR's coming in I'd be open to splitting it out.
If you're on Linux I think you can use symbolic links in your PACKAGE_DIRS directory.

Well my point was that this will prevent PRs from coming in.


Need help troubleshooting: "error finding address for actor type  with id "

In what area(s)?
Actors
/area placement
What version of Dapr?

1.0.0-rc.3

Expected Behavior
I have a service that has 3 actors on it. It works fine using dapr locally but doesn't work when deployed to Kubernetes. I've uninstalled and reinstalled dapr in kubernetes a couple times to be sure. But there isn't an issue there.
Actual Behavior
The .NET SDK exception when trying to invoke the method:
fail: Microsoft.AspNetCore.Server.Kestrel[13]
      Connection id "0HM67KBEG6M8G", Request id "0HM67KBEG6M8G:00000002": An unhandled exception was thrown by the application.
      Dapr.DaprApiException: error invoke actor method: error finding address for actor type SolarSystemMiningActor with id 9a97ec50-a6e7-4e8f-86fa-ff649d27ac22
         at Dapr.Actors.DaprHttpInteractor.SendAsyncHandleUnsuccessfulResponse(Func`1 requestFunc, String relativeUri, CancellationToken cancellationToken) in /dotnet-sdk/src/Dapr.Actors/DaprHttpInteractor.cs:line 377
         at Dapr.Actors.DaprHttpInteractor.SendAsync(Func`1 requestFunc, String relativeUri, CancellationToken cancellationToken) in /dotnet-sdk/src/Dapr.Actors/DaprHttpInteractor.cs:line 285
         at Dapr.Actors.DaprHttpInteractor.InvokeActorMethodWithRemotingAsync(ActorMessageSerializersManager serializersManager, IActorRequestMessage remotingRequestRequestMessage, CancellationToken cancellationToken) in /dotnet-sdk/src/Dapr.Actors/DaprHttpInteractor.cs:line 120
         at Dapr.Actors.Communication.Client.ActorRemotingClient.InvokeAsync(IActorRequestMessage remotingRequestMessage, CancellationToken cancellationToken) in /dotnet-sdk/src/Dapr.Actors/Communication/Client/ActorRemotingClient.cs:line 39
         at Dapr.Actors.Client.ActorProxy.InvokeMethodAsync(Int32 interfaceId, Int32 methodId, String methodName, IActorRequestMessageBody requestMsgBodyValue, CancellationToken cancellationToken) in /dotnet-sdk/src/Dapr.Actors/Client/ActorProxy.cs:line 219
         at <StartupCode$Chronos-Mining-Web>.$EventHandlerController.OnAsteroidCreated@75-2.Invoke(Unit unitVar0) in /app/Chronos.Mining/Chronos.Mining.Web/Controllers/EventHandlerController.fs:line 75
         at FSharp.Control.Tasks.TaskBuilder.StepStateMachine`1.nextAwaitable()
      --- End of stack trace from previous location ---
         at Microsoft.AspNetCore.Mvc.Infrastructure.ActionMethodExecutor.TaskOfIActionResultExecutor.Execute(IActionResultTypeMapper mapper, ObjectMethodExecutor executor, Object controller, Object[] arguments)
         at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.<InvokeActionMethodAsync>g__Awaited|12_0(ControllerActionInvoker invoker, ValueTask`1 actionResultValueTask)
         at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.<InvokeNextActionFilterAsync>g__Awaited|10_0(ControllerActionInvoker invoker, Task lastTask, State next, Scope scope, Object state, Boolean isCompleted)
         at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.Rethrow(ActionExecutedContextSealed context)
         at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.Next(State& next, Scope& scope, Object& state, Boolean& isCompleted)
         at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.<InvokeInnerFilterAsync>g__Awaited|13_0(ControllerActionInvoker invoker, Task lastTask, State next, Scope scope, Object state, Boolean isCompleted)
         at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.<InvokeNextResourceFilter>g__Awaited|24_0(ResourceInvoker invoker, Task lastTask, State next, Scope scope, Object state, Boolean isCompleted)
         at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.Rethrow(ResourceExecutedContextSealed context)
         at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.Next(State& next, Scope& scope, Object& state, Boolean& isCompleted)
         at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.<InvokeFilterPipelineAsync>g__Awaited|19_0(ResourceInvoker invoker, Task lastTask, State next, Scope scope, Object state, Boolean isCompleted)
         at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.<InvokeAsync>g__Awaited|17_0(ResourceInvoker invoker, Task task, IDisposable scope)
         at Microsoft.AspNetCore.Routing.EndpointMiddleware.<Invoke>g__AwaitRequestTask|6_0(Endpoint endpoint, Task requestTask, ILogger logger)
         at Dapr.CloudEventsMiddleware.ProcessBodyAsync(HttpContext httpContext, String charSet) in /dotnet-sdk/src/Dapr.AspNetCore/CloudEventsMiddleware.cs:line 114
         at Chronos.Utilities.RequestResponseLoggingMiddleware.Invoke(HttpContext context) in /app/Chronos.Common.AspNetCore/RequestResponseLoggingMiddleware.cs:line 29
         at Microsoft.AspNetCore.Server.Kestrel.Core.Internal.Http.HttpProtocol.ProcessRequests[TContext](IHttpApplication`1 application)

The dapr side car's logs:
time="2021-02-02T17:49:17.9175701Z" level=info msg="starting Dapr Runtime -- version 1.0.0-rc.3 -- commit dbfa3e4" app_id=mining instance=mining-664bd89997-cgrhv scope=dapr.runtime type=log ver=1.0.0-rc.3
time="2021-02-02T17:49:17.9176126Z" level=info msg="log level set to: info" app_id=mining instance=mining-664bd89997-cgrhv scope=dapr.runtime type=log ver=1.0.0-rc.3
time="2021-02-02T17:49:17.9178261Z" level=info msg="metrics server started on :9090/" app_id=mining instance=mining-664bd89997-cgrhv scope=dapr.metrics type=log ver=1.0.0-rc.3
time="2021-02-02T17:49:17.9178779Z" level=info msg="loading default configuration" app_id=mining instance=mining-664bd89997-cgrhv scope=dapr.runtime type=log ver=1.0.0-rc.3
time="2021-02-02T17:49:17.9178965Z" level=info msg="kubernetes mode configured" app_id=mining instance=mining-664bd89997-cgrhv scope=dapr.runtime type=log ver=1.0.0-rc.3
time="2021-02-02T17:49:17.9179027Z" level=info msg="app id: mining" app_id=mining instance=mining-664bd89997-cgrhv scope=dapr.runtime type=log ver=1.0.0-rc.3
time="2021-02-02T17:49:17.9180439Z" level=info msg="mTLS enabled. creating sidecar authenticator" app_id=mining instance=mining-664bd89997-cgrhv scope=dapr.runtime type=log ver=1.0.0-rc.3
time="2021-02-02T17:49:17.9181944Z" level=info msg="trust anchors and cert chain extracted successfully" app_id=mining instance=mining-664bd89997-cgrhv scope=dapr.runtime.security type=log ver=1.0.0-rc.3
time="2021-02-02T17:49:17.9182282Z" level=info msg="authenticator created" app_id=mining instance=mining-664bd89997-cgrhv scope=dapr.runtime type=log ver=1.0.0-rc.3
time="2021-02-02T17:49:17.9248038Z" level=info msg="Initialized name resolution to kubernetes" app_id=mining instance=mining-664bd89997-cgrhv scope=dapr.runtime type=log ver=1.0.0-rc.3
time="2021-02-02T17:49:17.9269488Z" level=info msg="component loaded. name: kubernetes, type: secretstores.kubernetes" app_id=mining instance=mining-664bd89997-cgrhv scope=dapr.runtime type=log ver=1.0.0-rc.3
time="2021-02-02T17:49:17.9333112Z" level=info msg="component loaded. name: redis-state, type: state.redis" app_id=mining instance=mining-664bd89997-cgrhv scope=dapr.runtime type=log ver=1.0.0-rc.3
time="2021-02-02T17:49:17.9334424Z" level=info msg="waiting for all outstanding components to be processed" app_id=mining instance=mining-664bd89997-cgrhv scope=dapr.runtime type=log ver=1.0.0-rc.3
time="2021-02-02T17:49:17.9366692Z" level=info msg="component loaded. name: messagebus, type: pubsub.redis" app_id=mining instance=mining-664bd89997-cgrhv scope=dapr.runtime type=log ver=1.0.0-rc.3
time="2021-02-02T17:49:17.9367448Z" level=info msg="all outstanding components processed" app_id=mining instance=mining-664bd89997-cgrhv scope=dapr.runtime type=log ver=1.0.0-rc.3
time="2021-02-02T17:49:17.9367927Z" level=info msg="enabled gRPC tracing middleware" app_id=mining instance=mining-664bd89997-cgrhv scope=dapr.runtime.grpc.api type=log ver=1.0.0-rc.3
time="2021-02-02T17:49:17.9368141Z" level=info msg="enabled gRPC metrics middleware" app_id=mining instance=mining-664bd89997-cgrhv scope=dapr.runtime.grpc.api type=log ver=1.0.0-rc.3
time="2021-02-02T17:49:17.9368947Z" level=info msg="API gRPC server is running on port 50001" app_id=mining instance=mining-664bd89997-cgrhv scope=dapr.runtime type=log ver=1.0.0-rc.3
time="2021-02-02T17:49:17.9372084Z" level=info msg="enabled metrics http middleware" app_id=mining instance=mining-664bd89997-cgrhv scope=dapr.runtime.http type=log ver=1.0.0-rc.3
time="2021-02-02T17:49:17.937241Z" level=info msg="enabled tracing http middleware" app_id=mining instance=mining-664bd89997-cgrhv scope=dapr.runtime.http type=log ver=1.0.0-rc.3
time="2021-02-02T17:49:17.9372982Z" level=info msg="http server is running on port 3500" app_id=mining instance=mining-664bd89997-cgrhv scope=dapr.runtime type=log ver=1.0.0-rc.3
time="2021-02-02T17:49:17.9373292Z" level=info msg="The request body size parameter is: 4" app_id=mining instance=mining-664bd89997-cgrhv scope=dapr.runtime type=log ver=1.0.0-rc.3
time="2021-02-02T17:49:17.9373551Z" level=info msg="enabled gRPC tracing middleware" app_id=mining instance=mining-664bd89997-cgrhv scope=dapr.runtime.grpc.internal type=log ver=1.0.0-rc.3
time="2021-02-02T17:49:17.9373896Z" level=info msg="enabled gRPC metrics middleware" app_id=mining instance=mining-664bd89997-cgrhv scope=dapr.runtime.grpc.internal type=log ver=1.0.0-rc.3
time="2021-02-02T17:49:17.9374123Z" level=info msg="sending workload csr request to sentry" app_id=mining instance=mining-664bd89997-cgrhv scope=dapr.runtime.grpc.internal type=log ver=1.0.0-rc.3
time="2021-02-02T17:49:17.9473722Z" level=info msg="certificate signed successfully" app_id=mining instance=mining-664bd89997-cgrhv scope=dapr.runtime.grpc.internal type=log ver=1.0.0-rc.3
time="2021-02-02T17:49:17.9476425Z" level=info msg="internal gRPC server is running on port 50002" app_id=mining instance=mining-664bd89997-cgrhv scope=dapr.runtime type=log ver=1.0.0-rc.3
time="2021-02-02T17:49:17.9476809Z" level=info msg="application protocol: http. waiting on port 80.  This will block until the app is listening on that port." app_id=mining instance=mining-664bd89997-cgrhv scope=dapr.runtime type=log ver=1.0.0-rc.3
time="2021-02-02T17:49:17.9477402Z" level=info msg="starting workload cert expiry watcher. current cert expires on: 2021-02-03 18:04:17 +0000 UTC" app_id=mining instance=mining-664bd89997-cgrhv scope=dapr.runtime.grpc.internal type=log ver=1.0.0-rc.3
time="2021-02-02T17:49:17.9481058Z" level=info msg="application discovered on port 80" app_id=mining instance=mining-664bd89997-cgrhv scope=dapr.runtime type=log ver=1.0.0-rc.3
time="2021-02-02T17:49:18.0266006Z" level=info msg="application configuration loaded" app_id=mining instance=mining-664bd89997-cgrhv scope=dapr.runtime type=log ver=1.0.0-rc.3
time="2021-02-02T17:49:18.0267307Z" level=info msg="actor runtime started. actor idle timeout: 1h0m0s. actor scan interval: 30s" app_id=mining instance=mining-664bd89997-cgrhv scope=dapr.runtime.actor type=log ver=1.0.0-rc.3
time="2021-02-02T17:49:18.0392252Z" level=info msg="placement tables updated, version: 5" app_id=mining instance=mining-664bd89997-cgrhv scope=dapr.runtime.actor.internal.placement type=log ver=1.0.0-rc.3
time="2021-02-02T17:49:18.0419316Z" level=info msg="app is subscribed to the following topics: [mining-equipment-added metal-capacity-units-set asteroid-created solar-system-created ship-created] through pubsub=messagebus" app_id=mining instance=mining-664bd89997-cgrhv scope=dapr.runtime type=log ver=1.0.0-rc.3
time="2021-02-02T17:49:18.0422876Z" level=warning msg="redis streams: BUSYGROUP Consumer Group name already exists" app_id=mining instance=mining-664bd89997-cgrhv scope=dapr.contrib type=log ver=1.0.0-rc.3
time="2021-02-02T17:49:18.0424681Z" level=warning msg="redis streams: BUSYGROUP Consumer Group name already exists" app_id=mining instance=mining-664bd89997-cgrhv scope=dapr.contrib type=log ver=1.0.0-rc.3
time="2021-02-02T17:49:18.0426284Z" level=warning msg="redis streams: BUSYGROUP Consumer Group name already exists" app_id=mining instance=mining-664bd89997-cgrhv scope=dapr.contrib type=log ver=1.0.0-rc.3
time="2021-02-02T17:49:18.0428844Z" level=warning msg="redis streams: BUSYGROUP Consumer Group name already exists" app_id=mining instance=mining-664bd89997-cgrhv scope=dapr.contrib type=log ver=1.0.0-rc.3
time="2021-02-02T17:49:18.0431132Z" level=warning msg="redis streams: BUSYGROUP Consumer Group name already exists" app_id=mining instance=mining-664bd89997-cgrhv scope=dapr.contrib type=log ver=1.0.0-rc.3
time="2021-02-02T17:49:18.043187Z" level=info msg="dapr initialized. Status: Running. Init Elapsed 125.2846ms" app_id=mining instance=mining-664bd89997-cgrhv scope=dapr.runtime type=log ver=1.0.0-rc.3
time="2021-02-02T17:49:18.4656394Z" level=warning msg="retriable error returned from app while processing pub/sub event d0dface0-e418-4399-9ae6-bba44aa4e5ab: . status code returned: 500" app_id=mining instance=mining-664bd89997-cgrhv scope=dapr.runtime type=log ver=1.0.0-rc.3
time="2021-02-02T17:49:18.4657139Z" level=warning msg="retriable error returned from app while processing pub/sub event 14d672a0-e1a9-43f6-b0b8-bb0f477d7fde: . status code returned: 500" app_id=mining instance=mining-664bd89997-cgrhv scope=dapr.runtime type=log ver=1.0.0-rc.3

(The retriable errors are because as a result of consuming a pub/sub message I'm making a call to an Actor)
The dapr placement service logs:
> klo dapr-placement-server-0 -n dapr-system
time="2021-02-02T17:35:55.5036354Z" level=info msg="starting Dapr Placement Service -- version 1.0.0-rc.3 -- commit dbfa3e4" instance=dapr-placement-server-0 scope=dapr.placement type=log ver=1.0.0-rc.3
time="2021-02-02T17:35:55.5037436Z" level=info msg="log level set to: info" instance=dapr-placement-server-0 scope=dapr.placement type=log ver=1.0.0-rc.3
time="2021-02-02T17:35:55.5039444Z" level=info msg="metrics server started on :9090/" instance=dapr-placement-server-0 scope=dapr.metrics type=log ver=1.0.0-rc.3
time="2021-02-02T17:35:55.5044764Z" level=info msg="Raft server is starting on <IP_ADDRESS>:8201..." instance=dapr-placement-server-0 scope=dapr.placement.raft type=log ver=1.0.0-rc.3
time="2021-02-02T17:35:55.5045819Z" level=info msg="mTLS enabled, getting tls certificates" instance=dapr-placement-server-0 scope=dapr.placement type=log ver=1.0.0-rc.3
time="2021-02-02T17:35:55.5046176Z" level=info msg="starting watch for certs on filesystem: /var/run/dapr/credentials" instance=dapr-placement-server-0 scope=dapr.placement type=log ver=1.0.0-rc.3
time="2021-02-02T17:35:57.0894178Z" level=info msg="certificates detected" instance=dapr-placement-server-0 scope=dapr.placement type=log ver=1.0.0-rc.3
time="2021-02-02T17:35:57.0895313Z" level=info msg="tls certificates loaded successfully" instance=dapr-placement-server-0 scope=dapr.placement type=log ver=1.0.0-rc.3
time="2021-02-02T17:35:57.0895651Z" level=info msg="placement service started on port 50005" instance=dapr-placement-server-0 scope=dapr.placement type=log ver=1.0.0-rc.3
time="2021-02-02T17:35:57.0896633Z" level=info msg="cluster leadership acquired" instance=dapr-placement-server-0 scope=dapr.placement type=log ver=1.0.0-rc.3
time="2021-02-02T17:35:57.0910679Z" level=info msg="Healthz server is listening on :8080" instance=dapr-placement-server-0 scope=dapr.placement type=log ver=1.0.0-rc.3
time="2021-02-02T17:35:57.0911645Z" level=info msg="leader is established." instance=dapr-placement-server-0 scope=dapr.placement type=log ver=1.0.0-rc.3
time="2021-02-02T17:47:14.0915367Z" level=info msg="Start desseminating tables. memberUpdateCount: 1, streams: 3, targets: 1, table generation: 1" instance=dapr-placement-server-0 scope=dapr.placement type=log ver=1.0.0-rc.3
time="2021-02-02T17:47:14.0923235Z" level=info msg="Completed dessemination. memberUpdateCount: 1, streams: 3, targets: 1, table generation: 1" instance=dapr-placement-server-0 scope=dapr.placement type=log ver=1.0.0-rc.3
time="2021-02-02T17:47:19.0916059Z" level=info msg="Start desseminating tables. memberUpdateCount: 1, streams: 10, targets: 2, table generation: 2" instance=dapr-placement-server-0 scope=dapr.placement type=log ver=1.0.0-rc.3
time="2021-02-02T17:47:19.0972405Z" level=info msg="Completed dessemination. memberUpdateCount: 1, streams: 10, targets: 2, table generation: 2" instance=dapr-placement-server-0 scope=dapr.placement type=log ver=1.0.0-rc.3
time="2021-02-02T17:48:32.091439Z" level=info msg="Start desseminating tables. memberUpdateCount: 2, streams: 0, targets: 0, table generation: 4" instance=dapr-placement-server-0 scope=dapr.placement type=log ver=1.0.0-rc.3
time="2021-02-02T17:48:32.0915036Z" level=info msg="Completed dessemination. memberUpdateCount: 2, streams: 0, targets: 0, table generation: 4" instance=dapr-placement-server-0 scope=dapr.placement type=log ver=1.0.0-rc.3
time="2021-02-02T17:49:17.5914926Z" level=info msg="Start desseminating tables. memberUpdateCount: 1, streams: 9, targets: 1, table generation: 5" instance=dapr-placement-server-0 scope=dapr.placement type=log ver=1.0.0-rc.3
time="2021-02-02T17:49:17.5922274Z" level=info msg="Completed dessemination. memberUpdateCount: 1, streams: 9, targets: 1, table generation: 5" instance=dapr-placement-server-0 scope=dapr.placement type=log ver=1.0.0-rc.3
time="2021-02-02T17:49:20.0915692Z" level=info msg="Start desseminating tables. memberUpdateCount: 1, streams: 13, targets: 2, table generation: 6" instance=dapr-placement-server-0 scope=dapr.placement type=log ver=1.0.0-rc.3
time="2021-02-02T17:49:20.0950564Z" level=info msg="Completed dessemination. memberUpdateCount: 1, streams: 13, targets: 2, table generation: 6" instance=dapr-placement-server-0 scope=dapr.placement type=log ver=1.0.0-rc.3
time="2021-02-03T15:52:10.5032936Z" level=info msg="Start desseminating tables. memberUpdateCount: 8, streams: 13, targets: 2, table generation: 14" instance=dapr-placement-server-0 scope=dapr.placement type=log ver=1.0.0-rc.3
time="2021-02-03T15:52:10.5089016Z" level=info msg="Completed dessemination. memberUpdateCount: 8, streams: 13, targets: 2, table generation: 14" instance=dapr-placement-server-0 scope=dapr.placement type=log ver=1.0.0-rc.3

The mining service manifest:
---
apiVersion: apps/v1
kind: Deployment
metadata:
  name: mining
  labels:
    app: mining
spec:
  replicas: 1
  selector:
    matchLabels:
      app: mining
  template:
    metadata:
      labels:
        app: mining
      annotations:
        dapr.io/enabled: "true"
        dapr.io/app-id: "mining"
        dapr.io/app-port: "80"
        dapr.io/max-concurrency: "1"
    spec:
      containers:
        - name: web
          image: <my image>
          ports:
            - containerPort: 80
          imagePullPolicy: Always
          env:
            - name: DAPR_HTTP_PORT
              value: "3500"

The dapr components yaml:
apiVersion: dapr.io/v1alpha1
kind: Component
metadata:
  name: redis-state
spec:
  type: state.redis
  version: v1
  metadata:
  - name: redisHost
    value: {{ .Values.redisServiceName }}
  - name: redisPassword
    value: {{ .Values.redisPassword }}
  - name: actorStateStore
    value: "true"
---
apiVersion: dapr.io/v1alpha1
kind: Component
metadata:
  name: messagebus
spec:
  type: pubsub.redis
  version: v1
  metadata:
  - name: redisHost
    value: {{ .Values.redisServiceName }}
  - name: redisPassword
    value: {{ .Values.redisPassword }}

I even see via the "/dapr/config" call that it is indeed returning the 3 actors that it should host:
$ curl localhost:6016/dapr/config
{"entities":["MinerActor","ResourcesActor","SolarSystemMiningActor"]}

If I port forward to daprd in the pod and try calling the actor i get errors as well:
$ curl localhost:3500/v1.0/actors/SolarSystemMiningActor/abc123/state/redis-state
{"errorCode":"ERR_ACTOR_INSTANCE_MISSING","message":"actor instance is missing"}

$ curl localhost:3500/v1.0/actors/SolarSystemMiningActor/9a97ec50-a6e7-4e8f-86fa-ff649d27ac22/method/tickAsync
{"errorCode":"ERR_ACTOR_INVOKE_METHOD","message":"error invoke actor method: error from actor service: "}

My kubectl get pods -n dapr-system:
NAME                                     READY   STATUS    RESTARTS   AGE
dapr-dashboard-6c4b54cc55-n58wv          1/1     Running   0          30h
dapr-operator-79df664bd-vnk5n            1/1     Running   1          30h
dapr-placement-server-0                  1/1     Running   0          30h
dapr-sentry-56df54f4d9-5vn69             1/1     Running   0          30h
dapr-sidecar-injector-56ddf9d5c4-8q2lv   1/1     Running   0          30h

Steps to Reproduce the Problem
I have basically an exact duplicate of another F# project that is working, the only difference is that I have 3 actors in this one opposed to 1 in the working one. All of the nuget packages, startup.fs, and program.fs are exactly the same too but for some reason only this one service's actors don't get registered or something where as the other service works fine.
Basically I just need a hand troubleshooting this as I am at a loss on where to go from here. I can't determine from any of the logs anywhere why this particular project's actors dont get registered.
Release Note

RELEASE NOTE:

{"errorCode":"ERR_ACTOR_INVOKE_METHOD","message":"error invoke actor method: error from actor service: "}

This error indicates that Dapr tries to call the Actor Framework on the app and received a status code != 200. So it is able to find the actor, but it may be that the actor itself is throwing an exception.
Did you upgrade to the latest version of the dotnet SDK?
Second, can you try to put more logs in your actor's tickAsync method or change the logic to simply return an Ok response and test again?

/cc @rynowak

Also, is there any reason for this? dapr.io/max-concurrency: "1". Can you try to remove this and see what happens?

Thanks @yaron2 - I think that the 'max-concurrency' flag may have been the problem. I just redeployed it and it's working now. I will do some more experimenting tomorrow and report back.
The error for "TickAsync" maybe be somewhat unrelated as it was just a troubleshooting step I was trying - it was the only actor method that doesnt require a message body. The main issue I keep getting stuck on is Dapr.DaprApiException: error invoke actor method: error finding address for actor type SolarSystemMiningActor with id 9a97ec50-a6e7-4e8f-86fa-ff649d27ac22 which I keep getting in under different circumstances but not sure how to troubleshoot it really.
And yes, I'm on the latest SDK. I'm actually building the dotnet SDK directly off of master. I setup the container to allow me to debug into it and I get that same "error finding address for actor type X with id X" error directly from Dapr.
Anyway - I will do some more experimenting tomorrow and let you know what I find. Thanks for the quick response!

Never mind - I'm still getting the same issue:
Dapr.DaprApiException: error invoke actor method: error finding address for actor type SolarSystemMiningActor with id 9e410f7a-da62-488b-b892-86f3da22a8ce

Are there any logs I can look at to help me track this down?

How many instances of your pod do you have running?

Just the single instance
On Sat, Feb 6, 2021 at 6:35 PM Yaron Schneider<EMAIL_ADDRESS>wrote:

How many instances of your pod do you have running?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/dapr/dapr/issues/2765#issuecomment-774573342, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAYMDJDGC7FRR5ZXG3KYXQLS5XU5BANCNFSM4XB45WRA
.

--
-Luke Pammant
<EMAIL_ADDRESS>720-583-5853
LinkedIn http://www.linkedin.com/pub/luke-pammant/17/636/48a

The service making the call to the actor and the actor itself are hosted in the same app in this instance. I'm subscribing to events and calling actors in the same service.
One thing that's strange is that I get the following:
fail: Microsoft.AspNetCore.Server.Kestrel[13]
    Dapr.DaprApiException: error invoke actor method: error finding address for actor type SolarSystemMiningActor with id 9e410f7a-da62-488b-b892-86f3da22a8ce

// ... But a few lines later my logging on the actor itself shows:

info: Utilities.RequestResponseLoggingMiddleware[0]
    Actor 9e410f7a-da62-488b-b892-86f3da22a8ce is starting  <--- from the OnActivateAsync method on the SolarSystemMiningActor
info: Utilities.RequestResponseLoggingMiddleware[0]
    Finished [PUT] **(200)** (0 ms) Finished processing request **http://<IP_ADDRESS>:80/actors/SolarSystemMiningActor/9e410f7a-da62-488b-b892-86f3da22a8ce/method/AddMinerAsync**

I don't get much time in the day to dig into this but I'll try investigating more tomorrow if you can point me in a direction.

Hey, it's me again. I havnt worked on the project since hitting this road block last year. I've decided to pick it back up and I'm still getting the same error. I've updated dapr runtime and SDK but still hitting the error when running in kubernetes.
Are there any tools or additional logging that has been added to actors that might help me get to the bottom of this?

I believe I figured it out. It turns out there was a rogue controller route assigned to "/{id}" which was taking all traffic and returning a 400.

Hi @LukePammant,
did you finally resolve it?
I am facing the same issue with a similar use-case as you set-up in your scenario.

Unfortunately I haven't worked on this for over a year so I can't recall if
I ended up fixing it. My last post said that it was an issue with
controller routes so that might be an avenue worth investigating.
On Mon, May 15, 2023 at 10:19 AM Marcel Bindseil @.***>
wrote:

Hi @LukePammant https://github.com/LukePammant,
did you finally resolve it?
I am facing the same issue with a similar use-case as you set-up in your
scenario.
—
Reply to this email directly, view it on GitHub
https://github.com/dapr/dapr/issues/2765#issuecomment-1548165029, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAYMDJH4BRVZAVJLR6AIYUDXGJJPTANCNFSM4XB45WRA
.
You are receiving this because you were mentioned.Message ID:
@.***>

--
-Luke Pammant
@.***
720-583-5853
LinkedIn http://www.linkedin.com/pub/luke-pammant/17/636/48a

For anyone else running into this error in the future, confirm all your actors are registered with DI. In my case, I had one registered but had forgotten to register the new, additional actors.

I had similar issue using Dapr 1.13 and workflow.
Solved by running dapr uninstall and dapr init


Algorithm settings

Based on the sharpness algorithm, it would be interesting to know how the values are taken over from a command with this param:
--sharpness, -sh  #Set image sharpness (-100 - 100)
regarding the sharpness algorithm parameters, which can also be entered/set in a specific .json  file (depending on camera model).
threshold 1.0
strength 1.0
limit 1.0
For example --sharpness 75 sets all the params to this value I guess?

Not exactly, we also factor in if we use binning modes or not.  You can see exactly what the parameter does over here.  userStrength_ is the parameter that gets set with the --sharpness command line argument.

You are right, we do need to update that document with the latest code changes.


Azure DF & SHIR: unable to connect to 3rd party MySQL DB with custom Cert

Azure documentation issue guidance
Thanks for opening an issue in the Azure technical documentation repository.
We use GitHub issues as the primary channel for customer and community feedback about the Azure documentation.
Creating an issue
We prefer that you create documentation feedback issues using the Feedback link on the published article - the feedback control on the doc page creates an issue that contains all the article details so you can focus on the feedback part.
You can also create a feedback issue here in the repo. If you do this, please make sure your issue lists:

[ ] The relevant Azure service or technology.
[ ] A link to the published documentation article that you have feedback about.
[ ] Clear, specific feedback that the author can act on.

Pull requests and article contributions
If you know the change that is needed in an article, we encourage you to submit the changes directly using a pull request. If the change is large, or if you want to contribute an entire article, follow these guidelines:

[ ] Don't surprise us with a big pull request or a pull request with a new article! Submit an issue that describes the details of the proposed large change or new article.
[ ] Include the service or technology area.

We'll route the issue to the appropriate content team for review and discussion.
Tech support and product feedback
If you would like to contact Microsoft about other things, such as product feedback or tech support, please review these guidelines:

If you need technical support using Azure, the paid and free support options are described here: https://azure.microsoft.com/support/options/.

Each article in the Azure technical documentation contains a product feedback button - it's best to submit product feedback directly from a relevant article. Otherwise, you can submit product feedback for most Azure products in the following product feedback forum: https://feedback.azure.com/d365community/forum/79b1327d-d925-ec11-b6e6-000d3a4f06a4.

Hi,
I am using a SHIR to connect to a 3rd Party MySQL DB with custom certificates.  I have installed an ODBC 32 bit driver on my VM. However, I wasn't able to get the SHIR to connect to the DNS. Is there some documentation for this approach?
Regards,
Sharon

The ODBC driver is able to successfully connect with the 3rd party source however in IR I get the following error:
Failed to connect to the database. Error message: ERROR [HY000] [MySQL][ODBC 8.0(w) Driver]SSL connection error: SSL_CTX_set_default_verify_paths failed
ERROR [HY000] [MySQL][ODBC 8.0(w) Driver]SSL connection error: SSL_CTX_set_default_verify_paths failed

We are going to close this thread as resolved but if there are any further questions regarding the documentation, please tag me in your reply and we will be happy to continue the conversation.


TheHiveApi.find_alerts cannot find alerts with specific custom field

Request Type
Bug
Work Environment

Question
Answer

OS version (server)
Ubuntu

OS version (client)
10, Ubuntu

TheHive4py 1.8.1

Problem Description
When I am using find_alerts with specific customField in query, the result is empty. I tried find_cases and API request and both works without problem.
Steps to Reproduce: in attach files

+1

+1

+1
I have updated my thehive for the v4 and I am using thehive4py 1.8.1.
Since thehive update, the query with In("customFields.client.string", CLIENT) does not retrieve anything, but I am sure there are alerts.
CLIENT is an array
The query worked before, maybe there is some change that I have to do for the new version...

+1
I have updated my thehive for the v4 and I am using thehive4py 1.8.1.
Since thehive update, the query with In("customFields.client.string", CLIENT) does not retrieve anything, but I am sure there are alerts.
CLIENT is an array
The query worked before, maybe there is some change that I have to do for the new version...

@wloody54 your query in curl is wrong.
Look at the example in code:

@CapaoAzul yours is also wrong.
Shoud look like In(customFields.client.string", [CLIENT])
Because second argument for In should be an array.

My code is equal. The datatype is "customFields.client.string" and the CLIENT is an array.
I think the problem is datatype being a customField


Creating proper documentation

I would like to work on this issue @rexdivakar .

ANy specific things to be included or kept in mind for documentation @rexdivakar ?

You can add a README.md file, requirements.txt and add in the work structure

You can add a README.md file, requirements.txt and add in the work structure

What do you mean by work structure ?

How AES works and how we are using it to encrypt the files

Join in to discuss more https://discord.gg/3VWffB

During file decryption, even after entering the key, it shows Decryption failed.
Images attached below for reference

In folder encryption, if the folder has files in it, the code runs into an error. Otherwise, it runs just fine.
Image attached below for reference

@rexdivakar please help to resolve these errors! Or if I am doing something wrong so that I can include the same in the readme .

It is unable to find the file due to escape sequence in the file path u may resolve it or raise a Issue and work on @Tawishi

During file decryption, even after entering the key, it shows Decryption failed.
Images attached below for reference

Why is this happening?

The issue has been patched u can proceed now @Tawishi
Problem (IO file creation error)

The issue has been patched u can proceed now @Tawishi
Problem (IO file creation error)

hey @Tawishi  can u please ping me https://discord.gg/e47wmTW

hey @Tawishi can u please ping me https://discord.gg/e47wmTW

Your username and tag ?

root#5998


🌟 Configure release workflow

This PR configures a release workflow for stable versions.
A release must be triggered manually from the workflows tab. There are 2 inputs:

the version to be released, i.e, 1.0.0.Alpha1. (REQUIRED)
the next development version, i.e, 1.1.0-SNAPSHOT. (OPTIONAL)

The next development version will be automatically calculated from the current version, that is, use the d.d.d value and append -SNAPSHOT. No number will be automatically incremented as the maven-release-plugin does because one could go from 1.0.0.Final into 1.1.0-SNAPSHOT (or even 2.0.0-SNAPSHOT !!) where as the maven release plugin will always increment the build number, resulting in 1.0.1-SNAPSHOT for example instead of 1.1.0-SNAPSHOT. Also, the release plugin would require using the jreleaser-maven-plugin and executing the jreleaser:full-release goal.
This workflow could be revised later.

Thanks!


Maintainer inquiry

Hi @tore-espressif,
After consulting with @C47D and @embeddedt, I'd like to ask if you have the liking to become the maintainer of this repo.
Seeing your past activity, it seems you have the same vision as us and you know ESP very well (no surprise :slightly_smiling_face: ).
If you are interested in it we could provide write access to this and the lvgl_esp32_drivers repo.

Hello @kisvegabor,
Thank you very much for the offer. I'd be very happy to join your efforts.
I'd like to come up with a suggestion of refactoring, focused on (but not only) on these issues:
https://github.com/lvgl/lvgl_esp32_drivers/issues/40
https://github.com/lvgl/lvgl_esp32_drivers/issues/44
https://github.com/lvgl/lvgl_esp32_drivers/issues/68
https://github.com/lvgl/lv_port_esp32/issues/272

Thank you very much for the offer. I'd be very happy to join your efforts.

Awesome! I've sent the invitation for both repos.
So from now you, @C47D, @embeddedt, and I have write access to these repos.

I'd like to come up with a suggestion of refactoring,

Could you open an issue to summarize your ideas?

I hope I'll have something worth sharing within two weeks

Okay, great! :slightly_smiling_face:
I think this issue can be closed. See you in the issues and PRs  :slightly_smiling_face:


Light doesnt work

lightgo.app and math-sheets.michaelfoody.com dont work

Thanks for informing me! The link was working the other day but Light is currently in BETA, so it is probably unstable. I labeled the link as broken.


Github action fails for lage PRs

Hi,
for PRs containing 50+ files github action fails due to rate-limiting error received from openAI API., can someone make some improvements in this direction?
Thanks!

OpenAI seems to return following headers:
X-Ratelimit-Limit-Requests:
200

X-Ratelimit-Limit-Tokens: 40000
X-Ratelimit-Remaining-Requests: 199
X-Ratelimit-Remaining-Tokens: 39742
X-Ratelimit-Reset-Requests: 300ms
X-Ratelimit-Reset-Tokens: 387ms

If anyone has good solutions in mind for rate limiting, I'm open for suggestions (and pull requests)! :)

@villesau you could consider using the chat model and re-prompting with chunks of files until that whole PR has been consumed by OpenAI. If i'm reading the issue correctly, the rate limit is on the single request?

@gad2103 can you elaborate a bit? Maybe a rudimentary example payload? Now it reviews chunks one by one which might cause the action to hit rate limits if the pr has many chunks. I'm very open for any ideas to improve the action<->OpenAI communication as it definitely has it's problems, such as not understanding the whole context of the pull request and so on.

Hi everybody,
I'm getting a rate limit response but in my case it's from Github API. This is because the Action is sending a lot of comments in a single request. I'm gonna try to send the comments split into different requests.


package "speter.net/go/exp/math/dec/inf" has been moved to https://gopkg.in/inf.v0

https://github.com/kubernetes/kubernetes/issues/23529

I made a hot-fix for that issue at script/vendor-hotfix.sh
In future, when upgrading new version of Kubernetes (<1.2), this issue will be automatically solved.


Palindrome Checker

I would like to add a code to check Palindrome strings in Java.
Please assign me this issue @gauriiighadge.
HACTOBERFEST2023

I wish to contribute. Kindly assign me this.

I want to contribute .please assign me this .

Please assign me this issue @gauriiighadge.
HACKTOBERFEST2023

Hey! I would like to work on this can you please assign it to me.

I would like to add a palindrome string checker code in any of the languages of: Java, cpp, C, javascript, C#, python or shell-script. Kindly assign me with the task

hello ,
I would like to contribute this code as i do coding mainly on java and will provide the simplest code for it.

Hello! I'm interested in working on this task. I would like to add code in Java , and I'm eager to contribute. Please consider assigning this to me, and I'll get started right away. Thanks! I will make a worthful contribution. @saseentharan

Hey @gauriiighadge  please assign me for creating a small code for checking  applicable number is  palindrome number or not ?


Add leader-for-life leader election

New Operator-SDK projects enable leader-for-life leader election by
default. This can help in running multiple instances of the operator
with only one pod running the controllers until the leader pod is deleted.
This model doesn't affect the admission controller webhook in the
current setup as only the leader pod will be running the webhook and
the other pods will be in a waiting state. When a leader pod is
deleted, the new leader generates new cert for the admission controller
and updates the client cert.
Reference docs:

Leader election - Operator SDK User Guide
Leader for Life Proposal for Operator SDK

Logs of a pod that becomes leader when the current leader pod is deleted:

2019-11-14T09:00:37.791Z	INFO	storageos.setup	Initializing	{"goversion": "go1.12.9", "os": "linux", "arch": "amd64", "operator-sdk": "v0.10.0"}
2019-11-14T09:00:37.792Z	INFO	leader	Trying to become the leader.
2019-11-14T09:00:37.792Z	DEBUG	k8sutil	Found namespace	{"Namespace": "storageos-operator"}
2019-11-14T09:00:37.836Z	DEBUG	k8sutil	Found podname	{"Pod.Name": "storageos-cluster-operator-697dd4797c-fwfjm"}
2019-11-14T09:00:37.845Z	DEBUG	k8sutil	Found Pod	{"Pod.Namespace": "storageos-operator", "Pod.Name": "storageos-cluster-operator-697dd4797c-fwfjm"}
2019-11-14T09:00:37.847Z	INFO	leader	Found existing lock	{"LockOwner": "storageos-cluster-operator-697dd4797c-zvbmn"}
2019-11-14T09:00:37.852Z	INFO	leader	Not the leader. Waiting.
2019-11-14T09:00:38.977Z	INFO	leader	Not the leader. Waiting.
...
<--Leader pod deleted-->
...
2019-11-14T09:04:03.443Z	INFO	leader	Not the leader. Waiting.
2019-11-14T09:04:20.952Z	INFO	leader	Became the leader.
2019-11-14T09:04:21.014Z	INFO	storageos.setup	Registering Components
...
2019-11-14T09:04:21.236Z	INFO	kubebuilder.controller	Starting workers	{"controller": "nfsserver-controller", "worker count": 1}
2019-11-14T09:04:21.453Z	INFO	kubebuilder.admission.cert.writer	cert directory doesn't exist, creating	{"directory": "k8s-webhook-server/cert"}
2019-11-14T09:04:21.455Z	DEBUG	kubebuilder.admission.cert.writer.atomic-writer	performed write of new data to ts data directory	{"task": "processing webhook", "ts directory": "k8s-webhook-server/cert/..2019_11_14_09_04_21.229763209"}
2019-11-14T09:04:21.595Z	INFO	kubebuilder.webhook	starting the webhook server.
...

This is applicable only when more than one replica of operator is deployed.

For leader election, the operator pods try to create a configmap. Looks like that may be causing a failure in OLM setup.


Z-Wave: Scene activation & Polling

This small refactor adds the following features:

The poll interval got fixed and the poll intensity gets configurable in the settings
Activated scenes now fire an event

The poll interval is needed for devices that don't push their state changes (e.g. greenwave powernode 6)
An example for a configuration is:
zwave:
  usb_path: /dev/ttyACM0
  config_path: /home/lukas/projects/smart-home/python-openzwave/openzwave/config
  polling_interval: 10000
  debug: 0
  customize:
    sensor.greenwave_powernode_6_port_energy_10:
        polling_intensity: 1

    sensor.greenwave_powernode_6_port_energy_10_2:
        polling_intensity: 1

    sensor.greenwave_powernode_6_port_energy_10_3:
        polling_intensity: 1

The scene activation event is useful for automation scripts that invole a wall switch - e.g. the Z-Wave.Me Wall Controller.
It allows automation scripts to react to button presses, e.g.:
automation:
  - alias: Turn on Desk light 1
    trigger:
      platform: event
      event_type: zwave.scene_activated
      event_data:
        entity_id: zwaveme_zme_wallcs_secure_wall_controller_8
        scene_id: 11
    action:
      service: switch.turn_on
      entity_id: switch.greenwave_powernode_6_port_switch_11_5

  - alias: Turn off Desk light 1
    trigger:
      platform: event
      event_type: zwave.scene_activated
      event_data:
        entity_id: zwaveme_zme_wallcs_secure_wall_controller_8
        scene_id: 12
    action:
      service: switch.turn_off
      entity_id: switch.greenwave_powernode_6_port_switch_11_5

  - alias: Turn on Desk light 2
    trigger:
      platform: event
      event_type: zwave.scene_activated
      event_data:
        entity_id: zwaveme_zme_wallcs_secure_wall_controller_8
        scene_id: 21
    action:
      service: switch.turn_on
      entity_id: switch.greenwave_powernode_6_port_switch_11_3

  - alias: Turn off Desk light 2
    trigger:
      platform: event
      event_type: zwave.scene_activated
      event_data:
        entity_id: zwaveme_zme_wallcs_secure_wall_controller_8
        scene_id: 22
    action:
      service: switch.turn_off
      entity_id: switch.greenwave_powernode_6_port_switch_11_3

This will also fix issue #1042

Code looks good. I've had some comments but they are more stylish improvements.
You have 1 style violation, if that is fixed I think this is good to be merged. :dolphin:


JS Client - OpenAPI Generator generates wrong version format and incomplete details

Is your feature request related to a problem? Please describe.
The JS Client will override the package.json and README with details that are incorrect. The expected changes are as follows:

The version needs to be full semantic versioning format, e.g. v1.0.0 instead of just v1
The package.json needs to have the repository in there, currently it is incomplete.
The README needs to include instructions for setting up the example, including what commands to run.

Steps to reproduce

You can generate the OpenAPI tool using the npm run generate:client:js in the root folder of the repository
Double check the outputs of packages/client/js/package.json and packages/client/js/README.md

@wilsonianb @hackgoofer Please take a look when you get a chance :+1:

The README should ideally include the instructions on setting up the minimal example and using the client to a base level. Reference the current (modified) README file for the added section on setting up the example.


test_virtual_machine_create_cpu_memory fails on Drone due to Deadlock while updating config_item status

Observed test_virtual_machine_create_cpu_memory failing on Drone couple of times with "Failed to find a placement" error caused by DeadLock during the config_item update

Never had this error when run integration tests locally; happens on Drone only

Yeah.  I've seen this deadlock error occur in drone multiple times too.  A
lot of times it seems to cause a lot of other test failures downstream.
On Fri, Apr 24, 2015 at 10:04 AM, Alena Prokharchyk <
<EMAIL_ADDRESS>wrote:

Never had this error when run integration tests locally; happens on Drone
only
—
Reply to this email directly or view it on GitHub
https://github.com/rancherio/rancher/issues/609#issuecomment-95993405.

Haven't seen this problem for a while; with all the refactoring done for config items there is a high chance it was fixed along the way. Closing for now


NodeJS FS module will cause the hydrogen deployment to fail - Hydrogen enviroment variables can't be loaded on localhost

What is the location of your example repository?
No response
Which package or tool is having this issue?
Hydrogen
What version of that package or tool are you using?
3.0.27
What version of Remix are you using?
No response
Steps to Reproduce
Let's say this is the Hydrogen deployment YAML file on Github actions
name: Storefront example
on: [push]

permissions:
  contents: read
  deployments: write

jobs:
  deploy:
    name: Deploy to Oxygen
    timeout-minutes: 30
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v3

      - name: Setup node.js
        uses: actions/setup-node@v3
        with:
          node-version: '16'
          check-latest: true

      - name: Get yarn cache directory
        id: yarn-cache-dir-path
        run: echo "dir=$(yarn cache dir)" >> $GITHUB_OUTPUT

      - uses: actions/cache@v3
        with:
          path: ${{ steps.yarn-cache-dir-path.outputs.dir }}
          key: ${{ runner.os }}-yarn-${{ hashFiles('**/yarn.lock') }}
          restore-keys: |
            ${{ runner.os }}-yarn-

      - name: Install dependencies
        id: 'install-dependencies'
        run: yarn

      - name: Build and Publish to Oxygen
        id: deploy
        uses: shopify/oxygenctl-action@v4
        with:
          oxygen_deployment_token: ${{ secrets.OXYGEN_DEPLOYMENT_TOKEN_1540294 }}
          build_command: "HYDROGEN_ASSET_BASE_URL=$OXYGEN_ASSET_BASE_URL yarn build"

      # Create GitHub Deployment
      - name: Create GitHub Deployment
        uses: shopify/github-deployment-action@v1
        if: always()
        with:
          token: ${{ github.token }}
          environment: 'preview'
          preview_url: ${{ steps.deploy.outputs.url }}
          description: ${{ github.event.head_commit.message }}

and let's say this is hydrogen.config.ts
import {defineConfig, CookieSessionStorage} from '@shopify/hydrogen/config';

export default defineConfig({
  shopify: {
    defaultCountryCode: 'GB',
    defaultLanguageCode: 'EN',
    storeDomain: Oxygen.env.PUBLIC_STORE_DOMAIN,
    storefrontToken: Oxygen.env.PUBLIC_STOREFRONT_API_TOKEN,
    privateStorefrontToken: Oxygen.env.PRIVATE_STOREFRONT_API_TOKEN,
    storefrontApiVersion: '2022-07',
    storefrontId: Oxygen.env.PUBLIC_STOREFRONT_ID,
  },
  session: CookieSessionStorage('__session', {
    path: '/',
    httpOnly: true,
    secure: import.meta.env.PROD,
    sameSite: 'Strict',
    maxAge: 60 * 60 * 24 * 30,
  }),
});

Let's say you want to test on localhost before deploying to production, you have to use the hydrogen environment variables, otherwise, the project won't so you first try to use the dotenv  library and you do something like this
privateStorefrontToken: Oxygen?.env?.ADMIN_API_TOKEN || process?.env['PRIVEATE_STOREFRONT_TOKEN']
Now you push to production, the deployment pipeline will fail and say fs module can't be found
Ok then let's ditch using dotenv library or any library and just load the environment from the file, but the .env file is in .gitignore  which means it won't be committed to git and the file can't be found on production, so we need check if the file exists in order for it to work.
Now how do you check if a file exists in nodejs?
    const fs = require('fs');
    const path = require('path');

    const envFilePath = path.resolve(__dirname, '.env');

    if (fs.existsSync(envFilePath)) {

    require('dotenv').config({ path: envFilePath });

    }

That won't work either, because you guessed it, fs library will cause the deployment pipeline to fail.
But you really want to test on my local machine, like any sane person, so ok let's add the hydrogen environment variables to the PC's environment variables, that way we can use process.env without loading files and using fs, and let's modify hydrogen.config.ts and check for every possible scenario
import { defineConfig, CookieSessionStorage } from '@shopify/hydrogen/config';

let STORE_DOMAIN = '';
let STORE_FRONT_TOKEN = '';
let PRIVATE_STORE_TOKEN = '';
let STORE_ID = '';

if (typeof Oxygen !== 'undefined') {
  STORE_DOMAIN = Oxygen.env.PUBLIC_STORE_DOMAIN ?? '';
  STORE_FRONT_TOKEN = Oxygen.env.PUBLIC_STOREFRONT_API_TOKEN ?? '';
  PRIVATE_STORE_TOKEN = Oxygen.env.PRIVATE_STOREFRONT_API_TOKEN ?? '';
  STORE_ID = Oxygen.env.PUBLIC_STOREFRONT_ID ?? '';
} else {
  STORE_DOMAIN = process.env.PUBLIC_STORE_DOMAIN ?? '';
  STORE_FRONT_TOKEN = process.env.PUBLIC_STOREFRONT_API_TOKEN ?? '';
  PRIVATE_STORE_TOKEN = process.env.PRIVATE_STOREFRONT_API_TOKEN ?? '';
  STORE_ID = process.env.PUBLIC_STOREFRONT_ID ?? '';
}
export default defineConfig({
  shopify: {
    shopify: {
      defaultCountryCode: "GB",
      defaultLanguageCode: "EN",
      storeDomain: STORE_DOMAIN,
      storefrontToken: STORE_FRONT_TOKEN,
      privateStorefrontToken: PRIVATE_STORE_TOKEN,
      storefrontApiVersion: "2022-07",
      storefrontId: STORE_ID,
    },
  },
  session: CookieSessionStorage('__session', {
    path: '/',
    httpOnly: true,
    secure: import.meta.env.PROD,
    sameSite: 'Strict',
    maxAge: 60 * 60 * 24 * 30,
  }),
});

The deployment works now, but the hydrogen environment variables won't load correctly on production and the website will go down.
So To summarize:

Fs module will cause the deployment pipeline to fail

there's no way to load the Hydrogen/Shopify environment variables on localhost and production so you can't test on localhost

the only way is just to create hydrogen.config.ts on machine which is different than the one tracked by git by using git update-index --assume-unchanged <path-name> or git update-index --skip-worktree <path-name> but this means you if you have to do changes to the file, then you'd have to track it again, make changes and then stop tracking it again. It's a hassle.

Expected Behavior
I expect everything to work
Actual Behavior
The deployment pipeline fails

Oxygen is a "worker-based runtime" (see more here) that primarily runs on Cloudflare Workers (see more here).
Unfortunately that means that NodeJS-based utilities don't necessarily work, as NodeJS is different than a Workers-based environment, even if both are running JavaScript on the server.

There's a guide on using Environment Variables in Hydrogen locally here.

ok then thank you


Enhance Docker Build Efficiency

This pull request introduces a significant enhancement to our Dockerfile and associated start.sh script by transitioning to uv, a cutting-edge Python package manager developed by Astral.sh. uv is designed to be a highly efficient drop-in replacement for traditional pip install operations, boasting remarkable speed improvements and compatibility with existing pip workflows.
Key Improvements:

Build Performance: Through local testing, I've observed that adopting uv has slashed our Docker build times by an impressive 50%. This enhancement is expected to streamline our development pipeline, reducing wait times for builds and deployments significantly.
Image Optimization: Alongside the performance boost, this change introduces the use of virtual environments, which has the added benefit of reducing our Docker image size by approximately 300MB. This optimization not only speeds up the deployment process but also minimizes resource consumption, aligning with our goals for efficiency and sustainability.

For more details on uv and its capabilities, visit Astral.sh's uv announcement.
I believe these changes will significantly improve our workflow and resource usage, and I look forward to any feedback on this change (even if it's "this might be too new").

Amazing stuff! it works flawlessly on my machine but we might need more comprehensive testing to make sure there won't be any issues, but overall it looks promising!

Amazing stuff! it works flawlessly on my machine but we might need more comprehensive testing to make sure there won't be any issues, but overall it looks promising!

Agreed, I'll make sure to keep my branch updated.

Yerp, found a bug already, the uv pip install for PyTorch fails on Linux x86_64 (but not macOS).

I think they fixed this bug but I need to wait until they push a new release to PyPI. Also found a workaround for global package installation.

Unfortunately, ya I think it may be too early days for this one. I'm hitting a lot of roadblocks trying to get this working smoothly on Linux (which is kinda important for Docker containers)... too many hacks and workarounds for my liking. I flies on my macOS local development environment, but it is definitely not ready for prod CI/CD.

Let's consider again when it's mature enough, keeping my eyes on it!


About adjacency matrix

Hi there.
According to your code,  the adjacency matrix of a graph uses 0 to indicate that two nodes are connected,  and 1 to indicate that two nodes are not connected. This seems to be different from routine which uses 1 to represent connected.  I'm curious why you chose such an implementation?

Thanks for any reply!

https://github.com/chaitjo/learning-tsp/blob/master/nets/encoders/gat_encoder.py#L55
https://github.com/chaitjo/learning-tsp/blob/master/nets/encoders/gnn_encoder.py#L117
Sorry for the late, brief response. The idea was to make it easy to enforce sparsity by indexing the mask where it had value 1/True to indicate that the edge doesn't exist. Today, I would just use PyG or DGL!


Fix #29 (consumer stops after a while)

This implements the fix described by @cubase in #29.

Hi @sanfilippopablo, could you try the most recent version 0.4.0 an verify if the issue still exist?


Add DataConflictError & return HTTP 409 when creating duplicate areas

Fixes https://github.com/fabric8-services/fabric8-wit/issues/1484
When an area creation with the same name in the same space/path is attempted, return an HTTP 409, instead of HTTP 400 which was earlier being mapped from BadParameterError. In this PR, a new Error type DataConflictError is returned and mapped into a HTTP 409 .
Note, HTTP 409 is returned for VersionConflictError as well.
Error in logs:
ERRO[2017-07-17 23:36:31] unable to create child area because an area in the same path already exists  err="pq: duplicate key value violates unique constraint \"areas_name_space_id_path_unique\"" file="/Users/shoubhikbose/dev/alm-core-sbose/src/github.com/fabric8-services/fabric8-wit/area/area.go" func="github.com/fabric8-services/fabric8-wit/area.(*GormAreaRepository).Create" identity_id=5af0439a-47fb-4832-a060-47d654567b02 line=84 name=myspace path=/de129c08-655a-44f6-8ee9-0b7d90b6f935 pid=56198 pkg=area req_id=3a959a6d-d5fd-4aef-84b1-a099b994b607 space=11412d5c-ecf3-4fd4-8b84-2b609fdb62d7

(pq: duplicate key value violates unique constraint "areas_name_space_id_path_unique")
[2017-07-17 23:36:31]
ERRO[2017-07-17 23:36:31] an error occurred in our api                  err="area already exists with name = myspace & space_id = 11412d5c-ecf3-4fd4-8b84-2b609fdb62d7 & path = /de129c08-655a-44f6-8ee9-0b7d90b6f935 " error_message="area already exists with name = myspace & space_id = 11412d5c-ecf3-4fd4-8b84-2b609fdb62d7 & path = /de129c08-655a-44f6-8ee9-0b7d90b6f935 " file="/Users/shoubhikbose/dev/alm-core-sbose/src/github.com/fabric8-services/fabric8-wit/jsonapi/jsonapi_utility.go" func="github.com/fabric8-services/fabric8-wit/jsonapi.ErrorToJSONAPIError" line=38 pid=56198 pkg=jsonapi

Response
Request URL:http://localhost:8080/api/areas/de129c08-655a-44f6-8ee9-0b7d90b6f935
Request Method:POST
Status Code:409 Conflict
Remote Address:[::1]:8080
Referrer Policy:no-referrer-when-downgrade

Response body:
{"errors":[{"code":"data_conflict","detail":"area already exists with name = myspace \u0026 space_id = 11412d5c-ecf3-4fd4-8b84-2b609fdb62d7 \u0026 path = /de129c08-655a-44f6-8ee9-0b7d90b6f935 ","status":"409","title":"Data conflict error"}]}

@sbose78 snapshot fabric8-wit image is available for testing.  docker pull docker.io/fabric8/fabric8-wit:SNAPSHOT-PR-1509-1

@sbose78 snapshot fabric8-wit image is available for testing.  docker pull docker.io/fabric8/fabric8-wit:SNAPSHOT-PR-1509-2

Codecov Report

Merging #1509 into master will increase coverage by 0.14%.
The diff coverage is 68.42%.

@@            Coverage Diff             @@
##           master    #1509      +/-   ##
==========================================
+ Coverage   58.78%   58.92%   +0.14%
==========================================
  Files         121      121
  Lines       14282    14300      +18
==========================================
+ Hits         8395     8426      +31
+ Misses       5230     5217      -13
  Partials      657      657

Impacted Files
Coverage Δ

area/area.go
76.57% <100%> (+1.33%)
:arrow_up:

jsonapi/jsonapi_utility.go
96.87% <100%> (+0.13%)
:arrow_up:

errors/errors.go
92.4% <25%> (-7.6%)
:arrow_down:

controller/workitem.go
80.53% <0%> (-0.51%)
:arrow_down:

controller/area.go
87.3% <0%> (+1.58%)
:arrow_up:

remoteworkitem/scheduler.go
63.26% <0%> (+16.32%)
:arrow_up:

remoteworkitem/github.go
100% <0%> (+21.62%)
:arrow_up:

models/transaction.go
66.66% <0%> (+24.99%)
:arrow_up:

Continue to review full report at Codecov.

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

@sbose78 snapshot fabric8-wit image is available for testing.  docker pull docker.io/fabric8/fabric8-wit:SNAPSHOT-PR-1509-3


Update stream-analytics-stream-analytics-query-patterns.md

Updated incorrect timestamps and LicensePlate table header

Hi @janety, I'm your friendly neighborhood Azure Pull Request Bot (You can call me AZPRBOT). Thanks for your contribution!

It looks like you're working at Microsoft (janety). If you're full-time, we DON'T require a contribution license agreement.

If you are a vendor, or work for Microsoft Open Technologies, DO please sign the electronic contribution license agreement. It will take 2 minutes and there's no faxing! https://cla.azure.com.

TTYL, AZPRBOT;

Per Jeff S, sign-off.


Move items between containers

At present you can re-order dashboard items within a container (sections can be reordered within the dashboard, rows within sections, cells within rows, etc...), but you can't move an item from one container to another (i.e. move a row between sections, or move a chart from one cell to another in a different row & section).
Being able to do so via drag & drop would be ideal, however that's likely to be a rather large undertaking.

This looks interesting for drag & drop support: http://threedubmedia.com/demo/drag/

Here's another possibility:  https://github.com/troolee/gridstack.js

https://github.com/bevacqua/dragula

https://github.com/briangonzalez/jquery.pep.js

https://github.com/rkusa/touch-dnd

http://interactjs.io/

https://haltu.github.io/muuri/

https://github.com/clippings/layout-grid

http://gridstackjs.com


Each Queue's DelaySeconds parameter is always set to 0 when enabling queues-storage and reloading from a persisted queues config file.

Using the serverless-offline-sqs plugin along with Elasticmq running in a Docker container, and the serverless-offline-sqs plugin configured to autoCreate the Queues.
One of the Queues defined in the resources section of serverless.yml has a DelaySeconds parameter set to 600.
When first starting everything up, all Queues get auto-created as expected (verifiable via the Elasticmq Web UI and via its auto-generated persisted queues config file), and the DelaySeconds for the one Queue is correctly set to 600.
Upon stopping and restarting the Elasticmq container (forcing it to reload from its persisted queues config file), the one Queue's DelaySeconds parameter is now set to 0.  This is verifiable via the Elasticmq Web UI and via the persisted queues config file.
This issue is occurring in both the softwaremill/elasticmq-native and softwaremill/elasticmq container images.

Hi, thanks for reporting the issue. It's fixed in v1.3.11


Workflow upgrade

Current workflow is pretty good, but also a mess. Let me explain:
Problems

There is no centralized source of truth for dependencies. I'd prefer one requirements.txt file, pip install -r requirements.txt and I'm ready for development. I also don't see any pros for creating separated venvs, as it's only taking more disk space and makes you switch between them regularly.
Scripts! As for now, project on 1/3 consists of scripts. Scripts are hard to maintain, they are platform-dependent, and you have to run them manually. IMHO, they MUST be replaced.

Suggestions
We can:

[ ]  Use poetry to manage dependencies & venvs (it seems to support building and publishing as well).
[ ]  Use tox to standardize testing. For example, see pytest-asyncio.
[ ]  Place most of the configs in setup.cfg.
[ ]  Setup multiplatform development workspace with devcontainer.json. Also, vs-code Python extension can take care of linting and formatting.

Afterword
I know it isn't so simple as "do that and everyone will be happy" so leave your thoughts in the comments.

Hey Alex, thanks for the feedback. I'm very aware that bash scripts are not a good long term solution. It was simply copy/pasted from some of my other projects where it is actually a pretty good solution for getting up and running where it is just me working on them.
Let me first explain a bit about the current design. The reason for having multiple requirements files is that it enables only installing the requirements that are actually needed for any particular task. This is especially helpful in the GItHub Action workflows. Each job can just install the needed requirements. I would push back on there not being any single source of truth. The single source of truth for any script is the generated frozen requirements file. You are correct that it takes more disk space though.
In terms of setting up venvs or switching between them, I don't think that is something users should ever  do. So that is why the scripts bootstrap the venvs for you. All a dev has to do is run ./scripts/test.sh for example and a venv with all the needed requirements will be set up, then pytest will be run in that venv.
One downside as you mention is maintainability. Another that I think is important is that the current set up doesn't allow for testing against multiple versions of dependencies (or Python versions). This script set up was copied from other projects of mine where this isn't a problem because there are no downstream users downloading or depending on the project (the code just runs on servers).
All that said, I agree that the scripts should be replaced. I have only limited knowledge of poetry and tox but I have been considering them already. (I also am interested in writing my own bootstrapper framework...). Have you used either of them before? Do you have any preferences?
Centralizing the configs is also something I have considered. Though I was under the impression that pyproject.toml is becoming a somewhat standard?
I will have to read up on devcontainer.json. Looks like it is for GitHub Codespaces which is still in beta?
Is this overhaul something that you would be interested in working on?

Each job can just install the needed requirements.

I haven't had a lot of experience with GitHub Actions (I had a lot with GitLab CI/CD, though), but I think those special dependencies can be configured within the job config file.

...current set up doesn't allow for testing against multiple versions of dependencies (or Python versions).

Tox seems to solve that exact problem.

Have you used either of them before? Do you have any preferences?

I'm only started studying both of them and already fell in love😄.

Though I was under the impression that pyproject.toml is becoming a somewhat standard?

pyproject.toml is a really cool solution too! I think the reason for it becoming a standart is PEP 518.

I will have to read up on devcontainer.json. Looks like it is for GitHub Codespaces which is still in beta?

It is GitHub Codespaces / VS Code thing. It lets you run the project on the web or using VS Code, with all needed configuration (for example: installed formatters and linters) already been applied to a Docker container. I think it's really cool, because all of us will develop in the exact same environment.

Is this overhaul something that you would be interested in working on?

Surely yes! I can create a PR for that, but I think it's better to release a new version first and maybe put something like "under refactoring" label in ReadMe, so other contributors will know that their PRs will probably need merge-conflict resolving. Btw, how about adding badges to ReadMe?

I think those special dependencies can be configured within the job config file.
Not sure what you mean by this?

I'm only started studying both of them and already fell in love.
Would you like to make the decision about which tool to use?

It is GitHub Codespaces / VS Code thing.
Ahh cool. I'm excited to try codespaces. I don't use VS Code but if it helps use it then we can add it to the repo.

maybe put something like "under refactoring" label in ReadMe
I don't think that the infra changes would impact other development of the code?

+1 to README badges

I think those special dependencies can be configured within the job config file.

Not sure what you mean by this?

For example, we now store wheel in basic_requirements.txt. However, we can move it directly to .github/workflows/something.yaml. Here is an example from pytest-asyncio GitHub Actions config.
steps:
      - uses: "actions/checkout@v2"
      - uses: "actions/setup-python@v2"
        with:
          python-version: "${{ matrix.python-version }}"
      - name: "Install dependencies"
        run: |
          set -xe
          python -VV
          python -m site
          python -m pip install --upgrade pip wheel
          python -m pip install --upgrade coverage[toml] virtualenv tox tox-gh-actions
      - name: "Run tox targets for ${{ matrix.python-version }}"
        run: "python -m tox"

I'm only started studying both of them and already fell in love.

Would you like to make the decision about which tool to use?

They are solving different problems, aren't they? We can use tox for test automation and poetry to manage dependencies and build the package. Here is an article that I've found, that describes the process of setting up both of them.

maybe put something like "under refactoring" label in ReadMe

I don't think that the infra changes would impact other development of the code?

Until they add new dependencies... Yeah, adding this label seems to be an overkill 🤔

If you had something like this in a workflow

      - name: "Install dependencies"
        run: |
          set -xe
          python -VV
          python -m site
          python -m pip install --upgrade pip wheel
          python -m pip install --upgrade coverage[toml] virtualenv tox tox-gh-actions
      - name: "Run tox targets for ${{ matrix.python-version }}"
        run: "python -m tox"

then what would you tell users to run locally? All those same steps? Wouldn't it be best to wrap that in a script in which case we are back where we started?

They are solving different problems, aren't they? We can use tox for test automation and poetry to manage dependencies and build the package. Here is an article that I've found, that describes the process of setting up both of them.

Unfortunately that article is paywalled for me?

then what would you tell users to run locally?

I don't think most of the contributors need to build the package on their machines. However, if they do, this should be quite simple if we use poetry. With poetry GitHub Actions and requirements files will look differently, so this discussion is a bit pointless. Probably it's just better to create a PR and see if it works.

Unfortunately that article is paywalled for me?

Oops... I can quickly retell it for you :)
The main statement of the article is that while poetry helps you with installing dependencies for the development, tox takes care of the dependencies while testing + adds ability to run tests against multiple python versions. They complement each other really well. And here is an example from the article.


Incorrect AWS provider version requirement

Describe the Bug
The AWS provider requirement is still listed as >=2.x, but creating an instance with this module with an AWS provider version <5.x will result in the error Can't configure a value for "domain": its value will be decided automatically based on the result of applying this configuration. due to attempting to set the "domain" value on main.tf:181
Expected Behavior
No errors about setting derived attributes that can't be set or overridden in any way without back-versioning the module to a version where this line doesn't exist
Steps to Reproduce
Attempt to create an instance using this module, with AWS provider <5.x
Screenshots
╷
│ Error: Value for unconfigurable attribute
│
│   with module.ec2_zscaler.aws_eip.additional,
│   on .terraform/modules/ec2_zscaler/eni.tf line 29, in resource "aws_eip" "additional":
│   29:   domain            = "vpc"
│
│ Can't configure a value for "domain": its value will be decided
│ automatically based on the result of applying this configuration.
╵
╷
│ Error: Value for unconfigurable attribute
│
│   with module.ec2_zscaler.aws_eip.default,
│   on .terraform/modules/ec2_zscaler/main.tf line 181, in resource "aws_eip" "default":
│  181:   domain   = "vpc"
│
│ Can't configure a value for "domain": its value will be decided
│ automatically based on the result of applying this configuration.
╵

Environment
No response
Additional Context
No response

The requirement was updated to >= 4.7.0 in https://github.com/cloudposse/terraform-aws-ec2-instance/commit/a8a32149c4c3c5e0ea6058b602209d3f450dbbd7. This issue can likely be closed.


Update return type of getMonthlySales

The api response /v1/market/private/user/earnings-and-sales-by-month.json will result in something like:
{
  "earnings-and-sales-by-month": [
    {
       //
    }
  ]
}

This turned out to be a wider issue with interface definitions, and I've fixed them all in 9aa960e08ca020388b379f6d6690ab0c8fedc74f which has been published as part of v3.0.3. The singular IMonthlySalesResponse interface now correctly represents the entire response as an array.
Thank you very much for the pull request and for bringing my attention to this! 👍


Identify the parts of the application that are consuming the most resources and taking the most time to execute.

Time: 2 days
Dependencies: None
Assignments: Istiaqul
Milestone: Sprint 1
Acceptance Criteria: List the things that take the longest time to execute in decreasing order so we can focus on the one that takes the longest time

This turned out to be everything that has to do with the evaluation dataset. We couldn't really generate a list because there were a lot of dependencies, however we created a list of all the dependencies that are actually needed to make the program run.


Unencrypted keys in user directory for single-password access (from #1399)

NOTE: Continuation of #1399
OK here it is!
Adds new encryption system that uses unencrypted keys the the encrypted user partition, to allow for easier encrypted login. edit-chroot -u or mount-chroot -u will create the keys, and they will be detected from then on.
I think edit-chroot and mount-chroot are good to go. I tested them on my C720
I am unsure if (or how) I should edit main.sh and add an option to set this up on creation of a chroot, for now you have to run edit-chroot -u or mount-chroot -u to create the keys.
I'm still new to all this (crouton, git, bash, life) so feel free to offer comments, questions, concerns, criticisms, critiques, complaints.
Thanks!

Thanks for working on this!
I don't think there needs to be a new parameter, though.  When you go to encrypt the chroot, and only if you specify the -k parameter, you should be allowed to leave the passphrase empty.  crouton should confirm that you want to leave the passphrase in the clear, and note that this should only be done if the keyfile is located in encrypted storage (such as your user profile) or on removable media.  When you go to mount the chroot, the chroot should automatically find the unwrapped key (as it already does for -k).

@dnschneid I will get on that. It shouldn't take so long now that i'm familiar with the code.
On an off topic git-related tangent, If I want to roll back my current commit, and start fresh (I think that would be easiest), should I git revert or git reset --hard and then push --force? I looked it up, but I'm unsure which is correct.
Thanks

If you want to start fresh and throw away the work, git reset --hard origin/master followed by git push origin encryption --force-with-lease will safely update github.

OK thanks for the tip.
The question I have with the -k parameter is that if .ecryptfs is a pointer for the moved keyfile, then the only location for the keys is in the user directory, which is lost if the user account is deleted. I would prefer to have the keys in 2 places, both encrypted in the folder of the chroot and decrypted in the user home (this is especially true with separate-partition).
Any suggestions for this?

That's kind of the point of moving the key around.  You can manually back up your key somewhere else (and then point to it if need-be by passing -k to enter-chroot), but for security, crouton shouldn't be silently duplicating your keys in multiple places.

Is that the sort of change you were looking for? I guess that makes more sense.
FYI the previous commit was moved to timvrakas/old-encryption
WARNING: The above not tested, I will not have access to my chrome book until later tomorrow.

But yes, this was pretty much how I was expecting it to behave (kudos for the very clean way of handling the unwrapped keys).

I still have a problem. They 63-char keys are coming back to haunt me. They are not properly handled. But It should be good otherwise.

Is hexdump still giving you a bad byte count, even with the 32/1 update?  It seemed fixed to me.

The issue with the hexdump is that old keys (made before the fix) are still too short. I will have to do line-by-line separation.

Good point.  I don't think you need to do line-by-line though.  Something like:
If first 16 characters of key is ....., it's unencrypted (don't check fnek to confirm).  Then you can easily extract the keys (which are just hex):
contents="`tail -n+1 keyfile`"
key="${keyfile#${DOTS}}"
key="${key%%.*}"
fnek="${keyfile##*.}"

OK I finished testing and worked out a few bugs. It all works for the most parts.
TODO:

Deal with the malformed (short) keys (as mentioned above)
The -ee change password should check for request password.
Link empty-password to -k flag (as mentioned above)

Well this is going to sound lame, but I just lost the completed above TODO. Somebody pressed the spacebar..... grr. I will have it done again in a few days.

Whoops!  No rush :)

Haha, well it looks like I got side-tracked for a long time....
Anyway now I have to deal with the new echo_tty functions

This is shaping up very well!

The last thing I'd like to see is additions to the 17-encryption tests to handle no passwords (both with -k and without -k specified).

Considering how critical this is to users' data, I can't merge this unless there are tests in place to prove it works.  Could you add tests to 17-encryption to stress the new code paths?

OK, I'm still figuring out the testing architecture, But I will figure it out eventually.

@Timvrakas shouldn't be too complex (you can run the encryption tests on your device by dropping the repo outside your chroot and running ./test/run.sh 17).  If you need help, swing by #crouton-devel for advice.  It'd be awesome to get this feature merged, but we have to be careful.

Much simpler to just store some long random password in the home folder, then modify mount-chroot to read it out.  Additionally I recommend moving all the scripts from /usr/local/bin to within the eCryptfs home folder (i.e. /home/chronos/user/crouton/) and making a symlink to the chroot storage (i.e. /home/chronos/user/chroot)
mount-chroot:
...
PWFILE="/home/chronos/user/crouton/pwfile"
...
            if [ -e "$PWFILE" ]; then
                passphrase="`cat $PWFILE`"
            else
                echo_tty -n "Enter encryption passphrase for $NAME: "
                [ -t 0 ] && stty -echo
                if [ -z "$passphrase" ]; then
                    read -r passphrase
                fi
                [ -t 0 ] && stty echo
                echo_tty ''
            fi
...

Much simpler to just store some long random password in the home folder, then modify mount-chroot to read it out.

The password would have to have as many bits of entropy as the key itself, assuming the wrapping function actually can use that much data.  Seems like one way or another this would weaken the chroot protection somewhat, compared to storing the key directly in encrypted storage.  Of course, it's still better (and more convenient) than the current approach.

Additionally I recommend moving all the scripts from /usr/local/bin to within the eCryptfs home folder (i.e. /home/chronos/user/crouton/) and making a symlink to the chroot storage (i.e. /home/chronos/user/chroot)

This is also very prudent.  To be clear, you have to run the scripts directly from the encrypted storage.