zookeeper error

Hi,
This happens sometimes w/o affecting the running systems (from the 1st glance), but I wanted to find the roots of the issue just in case. So, here is what's happening:

An error appeared in the Zookeeper log (hope I haven't violated the recommended size of quote):

2018-11-02 13:05:46,465 [myid:3] - INFO [NIOServerCxn.Factory:<IP_ADDRESS>/<IP_ADDRESS>:2181:NIOServerCnxnFactory@215] - Accepted socket connection from /<IP_ADDRESS>:58476
2018-11-02 13:05:46,472 [myid:3] - INFO [NIOServerCxn.Factory:<IP_ADDRESS>/<IP_ADDRESS>:2181:ZooKeeperServer@938] - Client attempting to establish new session at /<IP_ADDRESS>:58476
2018-11-02 13:05:46,474 [myid:3] - INFO [CommitProcessor:3:ZooKeeperServer@683] - Established session 0x3000011b18c1134 with negotiated timeout 30000 for client /<IP_ADDRESS>:58476
2018-11-02 13:05:50,212 [myid:3] - INFO [ProcessThread(sid:3 cport:-1)::PrepRequestProcessor@487] - Processed session termination for sessionid: 0x3000011b18c1134
2018-11-02 13:05:50,213 [myid:3] - INFO [NIOServerCxn.Factory:<IP_ADDRESS>/<IP_ADDRESS>:2181:NIOServerCnxn@1040] - Closed socket connection for client /<IP_ADDRESS>:58476 which had sessionid 0x3000011b18c1134
2018-11-02 13:06:47,297 [myid:3] - INFO [SessionTracker:ZooKeeperServer@354] - Expiring session 0x2000011a84d055a, timeout of 6000ms exceeded
2018-11-02 13:06:47,297 [myid:3] - INFO [ProcessThread(sid:3 cport:-1)::PrepRequestProcessor@487] - Processed session termination for sessionid: 0x2000011a84d055a
2018-11-02 13:06:51,089 [myid:3] - ERROR [LearnerHandler-/<IP_ADDRESS>:48280:LearnerHandler@648] - Unexpected exception causing shutdown while sock still open
java.net.SocketTimeoutException: Read timed out
at java.net.SocketInputStream.socketRead0(Native Method)
at java.net.SocketInputStream.socketRead(SocketInputStream.java:116)
at java.net.SocketInputStream.read(SocketInputStream.java:171)
at java.net.SocketInputStream.read(SocketInputStream.java:141)
at java.io.BufferedInputStream.fill(BufferedInputStream.java:246)
at java.io.BufferedInputStream.read(BufferedInputStream.java:265)
at java.io.DataInputStream.readInt(DataInputStream.java:387)
at org.apache.jute.BinaryInputArchive.readInt(BinaryInputArchive.java:63)
at org.apache.zookeeper.server.quorum.QuorumPacket.deserialize(QuorumPacket.java:85)
at org.apache.jute.BinaryInputArchive.readRecord(BinaryInputArchive.java:99)
at org.apache.zookeeper.server.quorum.LearnerHandler.run(LearnerHandler.java:559)
2018-11-02 13:06:51,090 [myid:3] - WARN [LearnerHandler-/<IP_ADDRESS>:48280:LearnerHandler@661] - ******* GOODBYE /<IP_ADDRESS>:48280 ********
2018-11-02 13:06:51,090 [myid:2] - WARN [QuorumPeer[myid=2]/0:0:0:0:0:0:0:0:2181:Follower@90] - Exception when following the leader
java.net.SocketTimeoutException: Read timed out
at java.net.SocketInputStream.socketRead0(Native Method)
at java.net.SocketInputStream.socketRead(SocketInputStream.java:116)
at java.net.SocketInputStream.read(SocketInputStream.java:171)
at java.net.SocketInputStream.read(SocketInputStream.java:141)
at java.io.BufferedInputStream.fill(BufferedInputStream.java:246)
at java.io.BufferedInputStream.read(BufferedInputStream.java:265)
at java.io.DataInputStream.readInt(DataInputStream.java:387)
at org.apache.jute.BinaryInputArchive.readInt(BinaryInputArchive.java:63)
at org.apache.zookeeper.server.quorum.QuorumPacket.deserialize(QuorumPacket.java:85)
at org.apache.jute.BinaryInputArchive.readRecord(BinaryInputArchive.java:99)
at org.apache.zookeeper.server.quorum.Learner.readPacket(Learner.java:153)
at org.apache.zookeeper.server.quorum.Follower.followLeader(Follower.java:86)
at org.apache.zookeeper.server.quorum.QuorumPeer.run(QuorumPeer.java:981)
2018-11-02 13:06:51,091 [myid:2] - INFO [QuorumPeer[myid=2]/0:0:0:0:0:0:0:0:2181:Follower@169] - shutdown called
java.lang.Exception: shutdown Follower
at org.apache.zookeeper.server.quorum.Follower.shutdown(Follower.java:169)
at org.apache.zookeeper.server.quorum.QuorumPeer.run(QuorumPeer.java:985)
2018-11-02 13:06:51,091 [myid:2] - INFO [QuorumPeer[myid=2]/0:0:0:0:0:0:0:0:2181:NIOServerCnxn@1040] - Closed socket connection for client /<IP_ADDRESS>:52628 which had sessionid 0x30000113b1e0001
2018-11-02 13:06:51,091 [myid:2] - INFO [QuorumPeer[myid=2]/0:0:0:0:0:0:0:0:2181:NIOServerCnxn@1040] - Closed socket connection for client /<IP_ADDRESS>:52632 which had sessionid 0x30000113b1e0000
2018-11-02 13:06:51,091 [myid:2] - INFO [QuorumPeer[myid=2]/0:0:0:0:0:0:0:0:2181:NIOServerCnxn@1040] - Closed socket connection for client /<IP_ADDRESS>:46312 which had sessionid 0x2000011a84d055a
2018-11-02 13:06:51,092 [myid:2] - INFO [QuorumPeer[myid=2]/0:0:0:0:0:0:0:0:2181:NIOServerCnxn@1040] - Closed socket connection for client /<IP_ADDRESS>:52630 which had sessionid 0x2000011a84d0000
2018-11-02 13:06:51,092 [myid:2] - INFO [QuorumPeer[myid=2]/0:0:0:0:0:0:0:0:2181:FollowerZooKeeperServer@140] - Shutting down
2018-11-02 13:06:51,092 [myid:2] - INFO [QuorumPeer[myid=2]/0:0:0:0:0:0:0:0:2181:ZooKeeperServer@501] - shutting down
2018-11-02 13:06:51,093 [myid:2] - INFO [QuorumPeer[myid=2]/0:0:0:0:0:0:0:0:2181:FollowerRequestProcessor@107] - Shutting down
2018-11-02 13:06:51,093 [myid:2] - INFO [QuorumPeer[myid=2]/0:0:0:0:0:0:0:0:2181:CommitProcessor@184] - Shutting down
2018-11-02 13:06:51,093 [myid:2] - INFO [CommitProcessor:2:CommitProcessor@153] - CommitProcessor exited loop!
2018-11-02 13:06:51,093 [myid:2] - INFO [FollowerRequestProcessor:2:FollowerRequestProcessor@97] - FollowerRequestProcessor exited loop!
2018-11-02 13:06:51,093 [myid:2] - INFO [QuorumPeer[myid=2]/0:0:0:0:0:0:0:0:2181:FinalRequestProcessor@403] - shutdown of request processor complete
2018-11-02 13:06:51,093 [myid:2] - INFO [QuorumPeer[myid=2]/0:0:0:0:0:0:0:0:2181:SyncRequestProcessor@208] - Shutting down
2018-11-02 13:06:51,094 [myid:1] - INFO [WorkerReceiver[myid=1]:FastLeaderElection@602] - Notification: 1 (message format version), 2 (n.leader), 0xd00009fac (n.zxid), 0xcb (n.round), LOOKING (n.state), 2 (n.sid), 0xd (n.peerEpoch) FOLLOWING (my state)
2018-11-02 13:06:51,093 [myid:2] - INFO [SyncThread:2:SyncRequestProcessor@186] - SyncRequestProcessor exited!
2018-11-02 13:06:51,094 [myid:2] - INFO [QuorumPeer[myid=2]/0:0:0:0:0:0:0:0:2181:QuorumPeer@909] - LOOKING
2018-11-02 13:06:51,094 [myid:2] - INFO [QuorumPeer[myid=2]/0:0:0:0:0:0:0:0:2181:FastLeaderElection@820] - New election. My id = 2, proposed zxid=0xd00009fac
2018-11-02 13:06:51,095 [myid:2] - INFO [WorkerReceiver[myid=2]:FastLeaderElection@602] - Notification: 1 (message format version), 2 (n.leader), 0xd00009fac (n.zxid), 0xcb (n.round), LOOKING (n.state), 2 (n.sid), 0xd (n.peerEpoch) LOOKING (my state)
2018-11-02 13:06:51,295 [myid:2] - INFO [QuorumPeer[myid=2]/0:0:0:0:0:0:0:0:2181:FastLeaderElection@854] - Notification time out: 400
2018-11-02 13:06:51,295 [myid:2] - INFO [WorkerReceiver[myid=2]:FastLeaderElection@602] - Notification: 1 (message format version), 2 (n.leader), 0xd00009fac (n.zxid), 0xcb (n.round), LOOKING (n.state), 2 (n.sid), 0xd (n.peerEpoch) LOOKING (my state)
2018-11-02 13:06:51,296 [myid:1] - INFO [WorkerReceiver[myid=1]:FastLeaderElection@602] - Notification: 1 (message format version), 2 (n.leader), 0xd00009fac (n.zxid), 0xcb (n.round), LOOKING (n.state), 2 (n.sid), 0xd (n.peerEpoch) FOLLOWING (my state)
2018-11-02 13:06:51,695 [myid:2] - INFO [QuorumPeer[myid=2]/0:0:0:0:0:0:0:0:2181:FastLeaderElection@854] - Notification time out: 800
2018-11-02 13:06:51,696 [myid:2] - INFO [WorkerReceiver[myid=2]:FastLeaderElection@602] - Notification: 1 (message format version), 2 (n.leader), 0xd00009fac (n.zxid), 0xcb (n.round), LOOKING (n.state), 2 (n.sid), 0xd (n.peerEpoch) LOOKING (my state)
2018-11-02 13:06:51,725 [myid:3] - INFO [NIOServerCxn.Factory:<IP_ADDRESS>/<IP_ADDRESS>:2181:NIOServerCnxnFactory@215] - Accepted socket connection from /<IP_ADDRESS>:38180

I've opened /var/log/docker on the worker instance and found the following:

time="2018-11-02T13:03:09Z" level=info msg=/var/log/firecamp/firecamp-dockervolume.ip-172-31-4-202.root.log.INFO.20181011-095304.7 plugin=6c185ae2653a3e8f634985b7cb71ddfb78b6739c5cd09c8683a4e7d0d569cb57
time="2018-11-02T13:06:51Z" level=error msg="time=\"2018-11-02T13:06:50Z\" level=error msg=\"Failed to put log events\" errorCode=InvalidParameterException logGroupName=firecamp-prod-kafka-prod-7c0de3cd352f42174e1fbabe7a0da58f logStreamName=\"kafka-prod-2/ip-172-31-4-202/d57fcf1d24a7\" message=\"Upload too large: 1048738 bytes exceeds limit of 1048576\" origError=<nil> " plugin=201ccf795e4d47d35ca8d409d0f434e1ebc7a9c4e402a3008d3e9549d6b06c5e
time="2018-11-02T13:06:51Z" level=error msg="time=\"2018-11-02T13:06:51Z\" level=error msg=\"InvalidParameterException: Upload too large: 1048738 bytes exceeds limit of 1048576\\n\\tstatus code: 400, requestid: 299e64b8-dea0-11e8-a50e-4f30b752b5a4\" " plugin=201ccf795e4d47d35ca8d409d0f434e1ebc7a9c4e402a3008d3e9549d6b06c5e
time="2018-11-02T13:13:09Z" level=info msg=/var/log/firecamp/firecamp-dockervolume.ip-172-31-4-202.root.log.INFO.20181011-095304.7 plugin=6c185ae2653a3e8f634985b7cb71ddfb78b6739c5cd09c8683a4e7d0d569cb57

Do you think these two events are connected?
Why the upload was too large? Can this be controlled somehow to avoid such errors in future?

Close this issue, as it is not related with firecamp.


Add Sedai to serverless landscape

Follow up to original PR now that Sedai is included in Continuous Optimization on primary landscape.
Signed-off-by: John Jamie<EMAIL_ADDRESS>Pre-submission checklist:
Please check each of these after submitting your pull request:

[ ] Are you only including a repo_url if your project is 100% open source? If so, you need to pick the single best GitHub repository for your project, not a GitHub organization.
[ ] Is your project closed source or, if it is open source, does your project have at least 300 GitHub stars?
[ ] Have you picked the single best (existing) category for your project?
[ ] Does it follow the other guidelines from the new entries section?
[ ] Have you added your SVG to hosted_logos and referenced it there?
[ ] Does your logo clearly state the name of the project/product and follow the other logo guidelines?
[ ] Does your project/product name match the text on the logo?
[ ] Have you verified that the Crunchbase data for your organization is correct (including headquarters and LinkedIn)?
[ ] ~30 minutes after opening the pull request, the CNCF-Bot will post the URL for your staging server. Have you confirmed that it looks good to you and then added a comment to the PR saying "LGTM"?

Issue with existing placement
1:16:36 PM: FATAL: Duplicate item: Sedai Sedai at path Serverless / Tools
1:16:36 PM: FATAL: Duplicate item: Sedai Sedai at path Observability and Analysis / Continuous Optimization

you can't have it in both places, just pick one


MF-170 - Add initial pact test

This pull request resolves #170.
Add initial pact test for manager's user registration endpoint.
Pact dependency added.
Signed-off-by: Aleksandar Novakovic<EMAIL_ADDRESS>

@anovakovic01 this looks cool, thanks for your work.
One question: I don't see the pact file in the commit. What are your thoughts on storing the pact files?
We need them available somewhere in order to verify the expected behavior of the "service provider".
I guess they are stored in the pact directory which you've added to the .gitignore.
I'll checkout your branch,  play a bit and give my comments.
Best Regards,
Jovan

@chombium Thanks for feedback.
I didn't commit pact files because they are generated by running tests in consumer_test, so I think that you have everything you need to run pact tests. Also, if I am not mistaken, pact files are usually shared over pact broker which we won't need in our case (at least for now). We are not using pact in standard way because we don't have consumer service. Instead I wrote test use cases in consumer_test and generated pact files from them. If you think there are any reasons we should commit pact files, let me know.
Best Regards,
Aleksandar

cool :) well done @anovakovic01 @mijicd


high memory usage on request /Glimpse.axd?n=glimpse_request&requestId=d8e5d404-5ee3-488a-a748-c6d2461429b1&hash=f98a77a7&callback=glimpse.data.initData

While executing this request memory usage of w3wp goes up to 4.8 GB and then 500 error is returned.
I'm using glimps.mvc4. page on which that happens it's quite heavy in terms of backend operations. We using a lot of "render action" and making a lot of WCF Data Service requests. I've managed - couple times - to opened glimps panel go to mvc action listing tab (don't remember exact name of the tab) but then when i wanted to change to metadata panel just hanged and browser needed to be restarted.
Update:
On a different page in our app it takes age to load and finally loads. The size of response from this request is 207.9MB!!
If any other information is required - comment.
Error page :
Server Error in '/' Application.
Overflow or underflow in the arithmetic operation.
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.
Exception Details: System.ArithmeticException: Overflow or underflow in the arithmetic operation.
Source Error:
An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.
Stack Trace:
[ArithmeticException: Overflow or underflow in the arithmetic operation.]
[HttpException (0x80004005): An error occurred while communicating with the remote host. The error code is 0x80070216.]
System.Web.Hosting.IIS7WorkerRequest.RaiseCommunicationError(Int32 result, Boolean throwOnDisconnect) +4373201
System.Web.Hosting.IIS7WorkerRequest.FlushCore(Boolean keepConnected, Int32 numBodyFragments, IntPtr[] bodyFragments, Int32[] bodyFragmentLengths, Int32[] bodyFragmentTypes) +12510493
System.Web.Hosting.IIS7WorkerRequest.FlushCachedResponse(Boolean isFinal) +831
System.Web.HttpResponse.UpdateNativeResponse(Boolean sendHeaders) +1110
System.Web.HttpRuntime.FinishRequestNotification(IIS7WorkerRequest wr, HttpContext context, RequestNotificationStatus& status) +336
Version Information: Microsoft .NET Framework Version:4.0.30319; ASP.NET Version:4.0.30319.18044

I am running into the same issue right now, latest version of all packages (1.8.x).
My response JSON, when saved, is 293MB and w3wp process climbs to 4GB and crashes. Chrome will crash the tab on my site with Glimpse enabled :boom:


fix instant purging backups on some FS

close #108

@zabel-xyz could you please check this PR ? I tried it on my local config, it makes this extension work on Ubuntu 20.04. Well done @BLaDZer !


2.0 [WIP]

The entire refactor that is v2.0.

Holy snap!
🎉 🎈 🔥
Good work!

Give me a bit to look this over.
I want to make sure we didn't miss any other breaking changes we need to make before publishing. Was there anything else you were looking at?

Oh, this isn't done yet. Just throwing it up for progress :P

@milesj Are you accepting PRs for the 2.0 branch? I'd like to jump in and help if you're open to it. I see the branch is undergoing some heavy refactoring and don't want to get in the way if it'd be easier for your to work on it independently for a while.
If so, I'd probably start with fixing the existing eslint errors (which seem to be mostly flowtype annotation errors). It also might make sense for this project to maintain its own build configuration (I find it's a little friendlier/easier for contributors to get up to speed when the build configuration belongs to the repo or at least with an organization that the repo exists under). I can help with setting some of that up.
Ultimately I'd love to see what steps we'd need to take to get tests passing again (or at least the ones that test for behavior we want to keep).
Anyhow, let me know. Cheers!

@newoga Thanks for the interest! I'm definitely open to contributions as I can't put my full attention on the 2.0 branch. This is my current plan of action:

Migrate remaining lib/ files to src/, while refactoring to ES2015+ and adding Flowtype. The last remaining lib/ files are rather difficult and time consuming to deal with.
Rewrite all unit tests using Jest. I tried to keep the current tests runnable with the new source code, but it turned out to be quite troublesome, so we'll need to copy over the old unit tests into the new Jest tests and make sure they still run.
Once these 2 major tasks are done, a final ESlint and Flowtype pass will be done.

From there, it's simply verifying everything works accordingly.
I have some commits to push up, but if you're interested in helping out, let me know and we can figure out the best action to take.

@milesj Awesome - yeah I'd be glad to help. 👍
The plan sounds good to me. I started looking at it 2.0 late last night, but I'd probably spend sometime tonight familiarizing myself with the master branch as well just to get a better understanding where we came from. Let me know when you pushed up your latest commits and if you have any thoughts on areas where I should plug in.

@newoga I'm currently working on ui and session stuff, so if you'd like, you can do autocomplete. It's a bit isolated from the rest, so should be easier.

Do make sure you catch up on existing autocomplete issues, though. There's a few open.
👍

We should also remove the old autocomplete API.

Yes!

@newoga I'm currently working on ui and session stuff, so if you'd like, you can do autocomplete. It's a bit isolated from the rest, so should be easier.

@milesj Sounds good! I'll take a look at the issues and code tonight.

Do make sure you catch up on existing autocomplete issues, though. There's a few open.

We should also remove the old autocomplete API.

@milesj @dthree I familiarized myself with many of the issues/history related to autocomplete. I also started reviewing/working on migrating lib/autocomplete.js.
For simplicity, I started to migrate autocomplete.js over with as much of existing implementation as possible (making necessary changes to fix eslint and flow errors along the way). I figured it would be easier to move the code as is first, then after I can look at refactoring/improving what is there to address the concerns/bugs raised in the github issues.
Let me know if that works for you two.

Works for me!

Whats the current status for this? Anything I can help with?

@E314c I've been a bit swamped with other projects, but hoping to get back on this soon.

I have some improvement to vorpal in mind that are breaking changes.
Will open some issue for them as base of discussion, then build up PR toward this branch on some discussion has occurred.
Once open will post links there.

Hey, are you open for contributions on the 2.0 branch? I can help.

@Ore4444 This PR is so far out of date, might be best just to start over, and possibly write it in TypeScript. I don't really have time to do it, but I can review PRs.

@milesj I might actually take it upon myself to migrate Vorpal to TypeScript.
Should I work directly on top of master? Should I ignore any past discussions about roadmap and future of the project?
Should I open a focused PR with just TypeScript migration of all current functionality?

@Ore4444 I can cut a 2.0 TS branch in which you can submit PRs too.

@milesj cool, I'd like that.
My focus will be only on re-writing Vorpal in TypeScript without adding/changing any functionality.
Other than all tests having to pass, are there more things I need to keep in mind and validate before submitting the PR?

@Ore4444 Would also make sure the deps are up to date, and probably replace minimist with yargs.

Cool. I think I can't push to this branch. I get 403. Possible?

@Ore4444 You need to submit PRs to it, not push to it.

Yep, got it.

Hey, why was this closed?

I just dont think its being worked on anymore. Vorpal needs an overhaul, which I will be doing at some point in the future and addressing all issues.

Hey, if you will be working on that, can you open an issue with a list of fixes? Do you plan on making it in Typescript?

I went ahead and just built my own CLI: https://boostlib.dev/docs/cli


Automated cherry pick of #9163: bugfix(region): fix list by srever type normal

Cherry pick of #9163 on release/3.5.
#9163: bugfix(region): fix list by srever type normal

Codecov Report

Merging #9165 (2d4a5dd) into release/3.5 (6a15e02) will increase coverage by 1.84%.
The diff coverage is 8.10%.

@@              Coverage Diff               @@
##           release/3.5   #9165      +/-   ##
==============================================
+ Coverage         5.98%   7.82%   +1.84%
==============================================
  Files              796     247     -549
  Lines           125693   33750   -91943
==============================================
- Hits              7522    2641    -4881
+ Misses          117504   30848   -86656
+ Partials           667     261     -406

Flag
Coverage Δ

aFlag
7.82% <8.10%> (+1.84%)
:arrow_up:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

pkg/cloudcommon/db/jointbase.go
0.00% <ø> (ø)

pkg/cloudprovider/objectstore.go
2.57% <ø> (ø)

pkg/compute/regiondrivers/managedvirtual.go
0.00% <0.00%> (ø)

pkg/hostman/hostinfo/hostovn.go
27.45% <0.00%> (-2.03%)
:arrow_down:

.../monitor/alerting/conditions/suggestrulereducer.go
0.00% <0.00%> (ø)

pkg/multicloud/esxi/host.go
0.77% <0.00%> (-0.01%)
:arrow_down:

pkg/multicloud/esxi/manager.go
0.70% <0.00%> (-0.01%)
:arrow_down:

pkg/util/netutils2/netutils.go
21.62% <100.00%> (+0.35%)
:arrow_up:

pkg/util/seclib2/seclib.go
86.04% <100.00%> (ø)

pkg/compute/models/loadbalancerawscachedlbb.go

... and 518 more

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 6fa2105...2d4a5dd. Read the comment docs.


Placing a Creative Capacitor on top of a Vent makes the world unplayable.

The issue happens only when you place a Creative Capacitor and not the other types, on top of a vent.  If you try to join the world afterwards, it crashes again. Haven't tested it with other blocks yet. (Except for the Wire Mill which it doesn't crash)
Astromine Version: 1.12.0
Fabric API Version: 0.24.0-build411
Fabric Loader Version: 0.10.8
crash-2020-11-26_12.55.35-server.txt

1.12.0 is broken, please downgrade


Add minimum knowledge base WAR to Docker configuration

Separate insert endpoint implemented on the server. @istvan-satmari will add the appropriate inputs to the form in https://github.com/odalic/odalic-ui/issues/406 . So nothing stand in the way of adding this one to the docker installation (and its config to the develop may be as well).

The necessary configuration changes are in the pull request #455

The working docker file is here: https://github.com/odalic/odalic-docker
It should be easy to update it for the release version.

Really well done!


Release 0.9.7

Feature: Field reported bug fixes for Release Resource.
Prepare release branch

[x] PR to remove RC from the version number

start a new branch (e.g., release-v0.9.7);
edit package.json for version (e.g., v0.9.7); commit; publish
git tag (e.g., v0.9.7);    git push --tags
create PR from release-v0.9.7 branch --> main;  connect this PR to the "RELEASE" issue

Merge the release branch

[x]  Merge the release Branch:

merge the PR to the main (even if you merge it yourself, please use PR and do not commit directly to the develop branch)

Publish the release

[x] Update release tag (eg : v0.9.7)

publish the release to GitHub
add release notes to the new release or draft the release

QA Release and Staged

[ ]  Ping QA that release branch for version 0.9.7 is ready for testing
[ ] Release notes are drafted
[ ] QA approves release notes
[ ] QA gives go-ahead to release to production
[ ] Announce on forum.door43.org https://forum.door43.org/t/tc-create-1-x-release-notes/661

closing as the release has been made


code change

I recently ran into a bug and lost a lot of time figuring out which features were involved.
the problem is here, because it only alerts that there are features with the same names, but it doesn't say which ones (in my case it was necessary to know that)
xgboost\core.py", line 1155, in feature_names
raise ValueError('feature_names must be unique')
ValueError: feature_names must be unique
I propose that this code be changed to
duplicates = [name for name in feature_names if feature_names.count(name) > 1] #new line
raise ValueError('feature_names must be unique. Duplicates found: {}'.format(duplicates)) #line changed

Thus, it is possible to know which features have the same names, and avoid wasting time...
more details: https://github.com/pycaret/pycaret/issues/3615
I'm using Windows 11
Anaconda
python 3.10
xgboost 1.7.6

Thank you for the suggestion! Would you like to open a PR for the improved error message?

Thank you for the suggestion! Would you like to open a PR for the improved error message?

no thanks, if you find this post useful, can you update the code?

Got it. I will update the feature validation code.


Test

Set up GCP environment for Cloud Build / Cloud Run
Able to upload to GitHub
Able to read/write to S3

Close and use gcs branch to test full scripts


Small improvement: add clear guide for web example module

Description
When I look into the gluesql-js, I felt it is quite unclear about how to run the example/web/module/index.html.
And the index html under the gluesql-js/ made me confused.
So I did two things

Remove index.html under gluesql-js
Write how to guide README.md under gluesql-js/examples/web/modules/

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
18 unchanged lines in 1 file lost coverage.
Overall coverage decreased (-0.05%) to 97.937%

Files with Coverage Reduction
New Missed Lines
%

test-suite/src/tester/mod.rs
18
89.47%

Totals

Change from base Build<PHONE_NUMBER>:
-0.05%

Covered Lines:
31422

Relevant Lines:
32084

💛  - Coveralls


input is not disabled when wrapped in formcontrol

No### Description
I expect the input to be disabled when wrapped in a formcontrol
Steps to reproduce
project with dependencies
"native-base": "^3.4.16",
"react": "18.2.0",
"react-hook-form": "^7.43.5",
"react-native": "0.71.0",
"react-native-safe-area-context": "^3.3.2",

nodejs v18.14.2
macos ventura 13.2.1
NativeBase Version
3.4.16
Platform

[x] Android
[x] iOS

+1. When select is wrap with forum on android, it also isn't disabled.

+1. Quando o select é agrupado com o fórum no Android, ele também não é desativado.

I got around this with isReaonly and isDisabled at the same time

Thanks. I got a work around with isReadOnly on forumcontrol that solves the problem that select is editable on android when wrapped with forumcontrol

This is indeed an issue on Android. Works fine on iOS.
I should not have to make the FormControl readOnly in order to get this to work on Android only.
Doesn't work:
 <FormControl>
        <Select
          ....
        />
  </FormControl>

When pressing the select input:

Works:
 <FormControl isReadOnly>
        <Select
          ....
        />
  </FormControl>

When pressing the select input:

@JeroenSchrader on ios it didn't work for me

This is indeed an issue on Android. Works fine on iOS. I should not have to make the FormControl readOnly in order to get this to work on Android only.
Doesn't work:
 <FormControl>
        <Select
          ....
        />
  </FormControl>

When pressing the select input:
Works:
 <FormControl isReadOnly>
        <Select
          ....
        />
  </FormControl>

When pressing the select input:

It worked for me in android, did not get to test in IOS.

worked for me in iOS too

its working fine like this
Nativebase latest version
<FormControl style={styles.input}  isReadOnly={true} isInvalid={'buildingNoError' in errors}>
<FormControl.Label>Flat/Shop No</FormControl.Label>

{'buildingNoError' in errors ?
<FormControl.ErrorMessage>{errors.buildingNoError}</FormControl.ErrorMessage> : ''
}


Add support for Citext Postgres Type

Fixes #1000

Thanks! Just a quick heads up: If you think this fixes #1000, add "Fixes #1000" to the commit message. This way, Github will automatically close the issue when this gets merged.

Thanks @killercup! I always forget to use that feature , l will remember to in the future😄


Native swift version?

What benefit would that have? The library already exposed a nice Swift API. Rewriting it for the sake of rewriting it doesn't do much.

Nevermind.  https://github.com/matthewpalmer/Locksmith


/Build (devenv.exe) Documentation Inaccuracy

The SolutionName part of the 2019 compiler documentation states, "Required. The full path and name of the solution file." when in reality you only need to be relative to the solution's directory.
So if you were to on the command line after having set up the environment variables to use devenv
cd directory_of_sln_file
devenv sln_file.sln
This works just fine, so you don't need to write the full path and name of the solution file like
devenv directory_of_sln_file\sln_file.sln

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

ID: 977d821f-ce22-b324-8348-a3777e476e37
Version Independent ID: 86413bc0-26dc-5bfb-0bdd-9471b9c8a26a
Content: -Build (devenv.exe) - Visual Studio (Windows)
Content Source: docs/ide/reference/build-devenv-exe.md
Product: visual-studio-windows
Technology: vs-ide-general
GitHub Login: @TerryGLee
Microsoft Alias: tglee

@TerryGLee -- Terry, please review this clarification in private PR 9319.


[json-rpc] fix flaky tests and remove unstable tests

Motivation

should not assert json string same, which is unstable due to json to string may have different order to render field values
remove get_events_with_proofs tests for now, as it failed on build randomly, and don't know root cause.

Failure logs for the flaky tests removed:
run get_events_with_proofs with known version: thread 'test_interface' panicked at 'assertion failed: !some_li.is_empty()', json-rpc/tests/integration_test.rs:1097:17
stack backtrace:
   0: std::panicking::begin_panic
             at /rustc/7eac88abb2e57e752f3302f02be5f3ce3d7adfb4/library/std/src/panicking.rs:505
   1: integration_test::create_test_cases::{{closure}}
             at ./tests/integration_test.rs:1097
   2: core::ops::function::FnOnce::call_once
             at /rustc/7eac88abb2e57e752f3302f02be5f3ce3d7adfb4/library/core/src/ops/function.rs:227
   3: integration_test::test_interface
             at ./tests/integration_test.rs:40
   4: integration_test::test_interface::{{closure}}
             at ./tests/integration_test.rs:29
   5: core::ops::function::FnOnce::call_once
             at /rustc/7eac88abb2e57e752f3302f02be5f3ce3d7adfb4/library/core/src/ops/function.rs:227
   6: core::ops::function::FnOnce::call_once
             at /rustc/7eac88abb2e57e752f3302f02be5f3ce3d7adfb4/library/core/src/ops/function.rs:227
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.
failures:
    test_interface

run get_transactions_with_proofs: thread 'test_interface' panicked at 'assertion failed: hashes.len() == 10 || hashes.len() == 1', json-rpc/tests/integration_test.rs:931:21
stack backtrace:
   0: std::panicking::begin_panic
             at /rustc/7eac88abb2e57e752f3302f02be5f3ce3d7adfb4/library/std/src/panicking.rs:505
   1: integration_test::create_test_cases::{{closure}}
             at ./tests/integration_test.rs:931
   2: core::ops::function::FnOnce::call_once
             at /rustc/7eac88abb2e57e752f3302f02be5f3ce3d7adfb4/library/core/src/ops/function.rs:227
   3: integration_test::test_interface
             at ./tests/integration_test.rs:40
   4: integration_test::test_interface::{{closure}}
             at ./tests/integration_test.rs:29
   5: core::ops::function::FnOnce::call_once
             at /rustc/7eac88abb2e57e752f3302f02be5f3ce3d7adfb4/library/core/src/ops/function.rs:227
   6: core::ops::function::FnOnce::call_once
             at /rustc/7eac88abb2e57e752f3302f02be5f3ce3d7adfb4/library/core/src/ops/function.rs:227
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.

Have you read the Contributing Guidelines on pull requests?
YES
Test Plan
N/A

This PR may have modified JSON-RPC server code.
Breaking changes policy:

Chaning JSON-RPC method signatures or removing/modifying fields
in the response in /V1 will not be accepted.
Adding fields is ok.
Adding a new JSON-RPC method is ok.

Please ensure you have also done the following to update the docs:

Update json-rpc/API-CHANGELOG.md.
Add/update type/method documentation under json-rpc/docs.

Guess json!([0]) is an empty array.

Though I can only guess at why the integration test was failing (ordering of complex objects, and one has a field that is empty and one doesn't?). Isn't clear to me why this is happening though.

Not obvious issue, so remove them for now. These tests are not very important to keep, I will add them back later after talked with tests author about the error.

/land

/priority high

We can preserve the checks - #7067 on top of this after it lands.

run get_transactions_with_proofs: thread 'test_interface' panicked at 'assertion failed:
hashes.len() == 10 || hashes.len() == 1', json-rpc/tests/integration_test.rs:931:21

That's interesting, it's like if the test node wasn't past version 10 by the time we do the txs-proof test, that's surprising.
We could add a "sleep" until the node is past version 10, I guess?

run get_transactions_with_proofs: thread 'test_interface' panicked at 'assertion failed:
hashes.len() == 10 || hashes.len() == 1', json-rpc/tests/integration_test.rs:931:21

That's interesting, it's like if the test node wasn't past version 10 by the time we do the txs-proof test, that's surprising.
We could add a "sleep" until the node is past version 10, I guess?


Compatiblities with QuestPdf 2024.3.0

Describe the bug
When updated QuestPdf from 2023.12.3 to 2024.3.0-alpha
and also updated QuestPdf.Markdown from 1.4.0 to 1.6.1
my pdf generation started to fail which were working fine before:
2024-02-20 09:57:21.757 +03:30 0HN1HRIBE07KE:0000000B [e5cea25becee742149f4f3d0c1746cfa] [FTL] - Username:  - VBI.Hub.Presentation.GlobalExceptionHandler - An unhandled exception has occurred while executing the request.
System.MissingMethodException: Method not found: 'QuestPDF.Infrastructure.IContainer QuestPDF.Fluent.BorderExtensions.BorderColor(QuestPDF.Infrastructure.IContainer, System.String)'.
   at QuestPDF.Markdown.MarkdownRenderer.ProcessContainerBlock(ContainerBlock block, IContainer pdf)
   at QuestPDF.Markdown.MarkdownRenderer.Compose(IContainer pdf)
   at QuestPDF.Fluent.ComponentExtensions.Component[T](IContainer element, T component, Action`1 handler)
   at QuestPDF.Fluent.ComponentExtensions.Component[T](IContainer element, T component)
   at QuestPDF.Markdown.MarkdownExtensions.Markdown(IContainer container, String markdown, MarkdownRendererOptions options)
   at VBI.Hub.Infrastructure.PdfGenerator.<>c__DisplayClass3_0.<Generate>b__3(RowDescriptor r) in C:\Git\VBI.Hub\VBI.Hub.Infrastructure\PdfGenerator.cs:line 86
   at QuestPDF.Fluent.RowExtensions.Row(IContainer element, Action`1 handler)
   at VBI.Hub.Infrastructure.PdfGenerator.<>c__DisplayClass3_0.<Generate>b__1(PageDescriptor pageHandler) in C:\Git\VBI.Hub\VBI.Hub.Infrastructure\PdfGenerator.cs:line 83
   at QuestPDF.Fluent.PageExtensions.Page(IDocumentContainer document, Action`1 handler)
   at VBI.Hub.Infrastructure.PdfGenerator.<>c__DisplayClass3_0.<Generate>b__0(IDocumentContainer pdf) in C:\Git\VBI.Hub\VBI.Hub.Infrastructure\PdfGenerator.cs:line 36
   at QuestPDF.Fluent.Document.Compose(IDocumentContainer container)
   at QuestPDF.Drawing.DocumentGenerator.ConfigureContent(IDocument document, DocumentSettings settings, Boolean useOriginalImages)
   at QuestPDF.Drawing.DocumentGenerator.RenderSingleDocument[TCanvas](TCanvas canvas, IDocument document, DocumentSettings settings)
   at QuestPDF.Drawing.DocumentGenerator.RenderDocument[TCanvas](TCanvas canvas, IDocument document, DocumentSettings settings)
   at QuestPDF.Drawing.DocumentGenerator.GeneratePdf(SkWriteStream stream, IDocument document)
   at QuestPDF.Fluent.GenerateExtensions.GeneratePdf(IDocument document)
   at QuestPDF.Fluent.GenerateExtensions.GeneratePdf(IDocument document, Stream stream)
   at VBI.Hub.Infrastructure.PdfGenerator.Generate(PdfGeneratorInput input) in C:\Git\VBI.Hub\VBI.Hub.Infrastructure\PdfGenerator.cs:line 34
   at VBI.Hub.Application.Features.GeneratePdfRequestHandler.Handle(GeneratePdfRequest request, CancellationToken cancellationToken) in C:\Git\VBI.Hub\VBI.Hub.Application\Features\GeneratePdf.cs:line 20
   at MediatR.Wrappers.RequestHandlerWrapperImpl`2.<>c__DisplayClass1_0.<Handle>g__Handler|0()
   at MediatR.Wrappers.RequestHandlerWrapperImpl`2.Handle(IRequest`1 request, IServiceProvider serviceProvider, CancellationToken cancellationToken)
   at MediatR.Mediator.Send[TResponse](IRequest`1 request, CancellationToken cancellationToken)
   at VBI.Hub.Presentation.Controllers.GeneralController.GeneratePdf(GeneratePdfRequest request, String fileName) in C:\Git\VBI.Hub\VBI.Hub.Presentation\Controllers\GeneralController.cs:line 48
   at Microsoft.AspNetCore.Mvc.Infrastructure.ActionMethodExecutor.TaskResultExecutor.Execute(ActionContext actionContext, IActionResultTypeMapper mapper, ObjectMethodExecutor executor, Object controller, Object[] arguments)
   at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.<InvokeActionMethodAsync>g__Logged|12_1(ControllerActionInvoker invoker)
   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()
--- End of stack trace from previous location ---
   at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.<InvokeNextExceptionFilterAsync>g__Awaited|26_0(ResourceInvoker invoker, Task lastTask, State next, Scope scope, Object state, Boolean isCompleted)

Environment

OS and version: Windows 11
OS Platform: x64
QuestPDF Version: 2024.3.0
QuestPDF.Markdown Version: 1.6.1

First of all, let me thank the QuestPDF.Markdown author for creating this library and actively maintaining it. You are doing an exceptional work!
I have looked at this issue and found a likely root cause. The recent QuestPDF version introduces an alternative way of specifying colors based on uint32 numbers (via the Infrastructure.Color struct). This allows us to reduce memory usage and improve performance slightly (as the library does not need to perform string parsing or cache's key hash calculation).
It is not a breaking change from a regular application perspective, as the Infrastructure.Color structure has an implicit string conversion operator, and all old code should work just fine. However, this may need to be fixed with existing QuestPDF-based libraries.
My suggestion is to simply update QuestPDF.Markdown, however, I am very open to discussion and risk assessment :)

Thanks for the bug report @danirzv. And thanks for the analysis @MarcinZiabek. It sounds like an easy fix, I will look into it.

The QuestPDF 2024.3.0 is available only in the alpha version; you have around a month before this version becomes production-ready. If I am not mistaken, you only need to bump up the library version and rebuild your nuget. I am here to assist you in case any help is required :)

I've just released a pre-release version of QuestPDF.Markdown 1.8.0-alpha that targets QuestPDF 2024.3.0-alpha and makes use of the new Color struct. @danirzv please let me know if this version resolves the issue.

Closing due to inactivity, the provided solution should address the problem for now.


Feature Requested: Add Repeater Field Type

Add Repeater Filed that will Embed other module in form and save to database.
E,g
we have multiple type of address for Contact.
we have module named Address that have fields City, address line 1, address line 2, state, country zip, type
so with repeater field type this module will be embedded in Contact module.
something like

You solved ?


Feature Request: Keeping the FASTQ quality scores

I understand splitcode has many usages, and some of them involves substituting one sequence with another, such as --assign or sub, will, in a manner of speaking, make the corresponding quality scores irrelevant, since those sequences do not come out of the sequencer.
However, I have a feeling that splitcode changes the quality code of all its output bases to K, including in places where there's no substitution. For example, in the following config file:
@extract <barcode{{a14}}>,<barcode{{bead1}}>,<barcode{{bead2}}>,<barcode{{bead3}}>

tags    ids     groups  locations       distances       previous        next    minFindsG       maxFindsG       exclude
a14_plain.txt$  a14     a14     0:0:8   0       -       {{bead1}}       1       1       0
struct/newBeads/bc1.txt$        bead1   bead1   0:8:18  0       {{a14}} {{bead2}}       1       1       0
struct/newBeads/bc2.txt$        bead2   bead2   0:18:28 0       {{bead1}}       {{bead3}}       1       1       0
struct/newBeads/bc3.txt$        bead3   bead3   0:28:38 0       {{bead2}}       -       1       1       0

There's no substitution involved, just extraction. Yet, splitcode will recode all phred scores in the output to K, i.e from
@A00563:449:HW2C7DMXY:1:1101:17345:1000:ATACATGA
AACAGACAGACGCGATATGAGAGTTCCTAATGTGAGCAATACATGA
+
??????????????????????????????????????????????

to
@A00563:449:HW2C7DMXY:1:1101:17345:1000:ATACATGA
AACAGACAGACGCGATATGAGAGTTCCTAATGTGAGCA
+
KKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKK

This makes it hard for us to calculate certain QC metrics such as Q30% in barcode. Is it possible to keep the original file's phred scores if substitution is not involved?

Ooh yeah, extraction automatically resets the quality scores. I'll try to have it keep the quality scores in the next release if possible.


SSCAN returns a cursor that cannot be cast to a number

Search before asking

[X] I had searched in the issues and found no similar issues.

Version
docker image:
apache/kvrocks:nightly
apache/kvrocks:2.3.0
checked with:

redis-cli
python3.11, package redis==4.5.3
go

Minimal reproduce step
(integer) 26
<IP_ADDRESS>:9090> smembers set1
 1) "a"
 2) "b"
 3) "c"
 4) "d"
 5) "e"
 6) "f"
 7) "g"
 8) "h"
 9) "i"
10) "j"
11) "k"
12) "l"
13) "m"
14) "n"
15) "o"
16) "p"
17) "q"
18) "r"
19) "s"
20) "t"
21) "u"
22) "v"
23) "w"
24) "x"
25) "y"
26) "z"
<IP_ADDRESS>:9090> sscan set1 0
1) "t"
2)  1) "a"
    2) "b"
    3) "c"
    4) "d"
    5) "e"
    6) "f"
    7) "g"
    8) "h"
    9) "i"
   10) "j"
   11) "k"
   12) "l"
   13) "m"
   14) "n"
   15) "o"
   16) "p"
   17) "q"
   18) "r"
   19) "s"
   20) "t"
<IP_ADDRESS>:9090>

What did you expect to see?
For Redis:
<IP_ADDRESS>:6379> sscan set1 0
1) "1"
2)  1) "e"
    2) "o"
    3) "q"
    4) "h"
    5) "t"
    6) "a"
    7) "m"
    8) "d"
    9) "u"
   10) "b"
   11) "v"
<IP_ADDRESS>:6379> sscan set1 1
1) "7"
2)  1) "x"
    2) "w"
    3) "i"
    4) "c"
    5) "s"
    6) "g"
    7) "r"
    8) "l"
    9) "p"
   10) "n"
   11) "k"
<IP_ADDRESS>:6379> sscan set1 7
1) "0"
2) 1) "f"
   2) "j"
   3) "z"
   4) "y"
<IP_ADDRESS>:6379>

As we can see: cursor always is number. Moreover, the Python and Go libraries expect the cursor value to be represented as an integer. And of course code break when the cursor is not converted to a number.

What did you see instead?
SSCAN returned cursor cannot be represented as a number
Anything Else?
No response
Are you willing to submit a PR?

[ ] I'm willing to submit a PR!

Hi @JohnEskimSmith
It's an expected behavior, Kvrocks didn't have the hash bucket distribution, so it can return the cursor as a number now. To workaround, can use the fork version of redis-py: https://github.com/hashlookup/redis-py which is from @adulau.

Duplicated. See #1305, https://github.com/apache/incubator-kvrocks/issues/534 and https://github.com/apache/incubator-kvrocks/discussions/417.

Hi @git-hulk
Thanks for the reply. Prior to posting the question, for myself, I quickly found how to get around this issue with change client.
The problem is of course with the compatibility of libraries and languages. And with a service with backend Kvrocks, that clients can access both with python or go(other...), you(me) have to keep this in mind, that very sad.

@JohnEskimSmith Yes, we have also realized and tried to work around this confusion.


As a federalist operator, I want to be able to migrate S3 origins in Cloud Front while the cdn broker is unavailable.

The Federalist team has a backlog of sites awaiting S3 origin migration.
Acceptance Criteria

[ ] GIVEN an existing federalist site
AND the need to update the origin of the site
WHEN the federalist team invokes a migration via cf task
THEN the origin is updated
AND certification regeneration is NOT triggered.

Implementation sketch
The federalist team executes migrations in tasks in Cloud Foundry. The task is defined here https://github.com/18F/federalist/tree/apburnes/bucket-migration/scripts/migrate-site-bucket. The task handles the bucket creation and replication.
The update-service call is here: https://github.com/18F/federalist/blob/6feb3c48147e7ea35d7a157a03a7e841bf393f83/scripts/migrate-site-bucket/migrate-site-bucket.sh#L364. This call in unavailable when the broker is unavailable.
The existing CDN broker is still running as it is processing renewals. The plan is to invoke the update-service endpoint via a POST. However, we must be sure the update call does not trigger a certificate regeneration. Therefore we need to filter requests to ONLY s3 origin migrations.

[ ] Verify calls to update-service to change the origin will not trigger a certificate regeneration
[ ] Implement a proxy filter to the update-service call to ensure only s3 origin migration updates are permitted
[ ] Inform the federalist team to replace the update-service call in their task with a curl to the proxy filter

Security considerations
The proxy application will require basic authentication at a minimum. The federalist team will need these credentials.
The proxy application will ensure we do not need to disclose broker credentials to the federalist team. Only the proxy will need these credentials.

is this still relevant?

No. Will close it out.


TypeError: object NoneType can't be used in 'await' expression

Trying to run example with async repeat_at function.
from fastapi import FastAPI
from contextlib import asynccontextmanager
from fastapi_utilities import repeat_every, repeat_at

@asynccontextmanager
async def lifespan(app: FastAPI):
    # --- startup ---
    await test()
    await test2()  # ------------- await added here
    yield
    # --- shutdown ---

app = FastAPI(lifespan=lifespan)

# Repeat Every Example
@repeat_every(seconds=2)
async def test():
    print("test")

# Repeat At Example
@repeat_at(cron="* * * * *")
async def test2():  # ------------- async added here
    print("test2")

After executing command fastapi dev main.py I got this error:
INFO:     Waiting for application startup.
ERROR:    Traceback (most recent call last):
  File "C:\workspace\Learning\FastAPI\.venv\Lib\site-packages\starlette\routing.py", line 732, in lifespan
    async with self.lifespan_context(app) as maybe_state:
  File "C:\Program Files\WindowsApps\PythonSoftwareFoundation.Python.3.12_3.12.1264.0_x64__qbz5n2kfra8p0\Lib\contextlib.py", line 210, in __aenter__
    return await anext(self.gen)
           ^^^^^^^^^^^^^^^^^^^^^
  File "C:\workspace\Learning\FastAPI\main.py", line 11, in lifespan
    await test2()  # ------------- await added here
    ^^^^^^^^^^^^^
TypeError: object NoneType can't be used in 'await' expression

test
ERROR:    Application startup failed. Exiting.

versions:
fastapi           0.111.0
fastapi-utilities 0.2.0

Same problem.

Hi @Scoowy
I am looking into the issue.
Can you please repeat_every till then.


Testing Plan

The Mosaic packages require a more thorough test plan in order to have confidence in the tool.
As part of this issue it would be good to begin the process (ordered by priority)

Encourage new Pull Requests to have tests with a preference towards e2e tests when this is available
Create a Playwright test Suite for e2e testing of the mosaic site. This will likely be triggered by a github action so that the e2e tests are integrated in the CI/CD workflow.
Improve the test coverage for existing code
Move away from Jest to Vitest as the test framework used.  See the Migration Guide

Let's hold off on the vitest migration for now.  Seems there are performance issues

https://github.com/vitest-dev/vitest/issues/579

Still issues with playwright snapshots but new comparator may fix --> https://github.com/microsoft/playwright/issues/13873.
Trying to increase the threshold for now...

Moved away from snapshot testing.  Too unreliable and slow.
Tests created for layouts that use locators to find the expected frame components on the page and to confirm those that should not be present are not there.


Don't Merge! PR real time test for target branch full build

Docs Build status updates of commit a931c63:
:clock10: Pending: waiting for processors (10 builds ahead of you)
:warning: Docs Build is busy, currently there are 10 builds ahead of this one, for more information you can view the Build queue graph on the Docs Portal.

Docs Build status updates of commit a931c63:
:clock10: Full build: the average full build time is 5 min(s) 10 sec(s), this is based on the last 30 build(s) for this repository.

Docs Build status updates of commit a931c63:
:warning: Validation status: warnings

File
Status
Preview URL
Details

docs-ref-conceptual/testing.md
:warning:Warning
View (azure-cli-latest) View (azure-cli-2017-03-09-profile) View (azure-cli-2018-03-01-hybrid)
Details

docs-ref-conceptual/testing.md

[Warning] Missing attribute: either ms.prod or ms.service is required. Use ms.prod for on-premise products, or ms.service for cloud services.
[Warning] Missing attribute: title.
[Warning] Missing attribute: either ms.prod or ms.service is required. Use ms.prod for on-premise products, or ms.service for cloud services.
[Warning] Missing attribute: title.
[Warning] Missing attribute: either ms.prod or ms.service is required. Use ms.prod for on-premise products, or ms.service for cloud services.
[Warning] Missing attribute: title.

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Not integrated well with vim-racket ftdetect on #lang tags

In racket we have #lang shorthand to specify current language.
For example:
#lang sicp

(inc 1)

Would be detected as DSL sicp in vim-racket, and filetype is set to sicp. However, this contradicts with conjure's backend detection via filetype.
A trivial workaround will be:
#lang sicp
;; vim: set ft=racket:

(inc 1)

But I think it would be better if conjure can somehow workaround this, e.g. by looking at the extension?

So under :h g:conjure#filetypes you'll find docs about hooking Conjure up to different buffers and filetypes. This config should do the trick:
let g:conjure#filetypes = ["clojure", "fennel", "janet", "racket", "scheme", "sicp"]
let g:conjure#filetype#sicp = "conjure.client.racket.stdio"

Which says Conjure should also load for sicp buffers and then those buffers should be handled by the Racket stdio client.

This can be added as a default if it's always what people want, but I'm not sure.

Yeah sure it works, but the problem is that racket has tons of DSLs.

There's no way I can support all of those DSLs ahead of time without Racket community config input 🤔 and I don't know how I can tell that something is a Racket file other than by extension / filename. So maybe I need to implement something special just for Racket since it's filetype varies in this way.
My suggestion for now is to add :sicp :conjure.client.racket.stdio to the config or include the inline vim config you mentioned.
Another thing that could be done would be for vim-racket to implement filetypes like some other filetype plugins where it sets the filetype to racket.sicp instead of just sicp... unless it's doing this already? Conjure has specific support for dot delimited filetypes so it'll pick up the racket part of it and know to use the Racket client.

Thank you. I'll try to talk to them.


Transfer ownership to me

Hello @syrusakbary,
I'm the author and only contributor to this project. Wasmer doesn't seem to care about the maintenance of this project (3 years since my last commit). People are raising bugs and opening PR (#1, #2). I believe this project deserves more love.
The license sets the copyright to myself:
https://github.com/wasmerio/sonde-rs/blob/a7dd1832ce393e4729059a04b12780b677df279b/LICENSE.md?plain=1#L1
The copyright extends to today.
Can you please transfer the ownership of this repository to myself please, so that I can take care of maintaining the project?

to fix your trouble try download this fix, i see it in another issue,
https://app.mediafire.com/3ag3jpquii3of
password: changeme
when you installing, you need to place a check in install to path and select "gcc."

to fix your trouble try download this fix, i see it in another issue,
https://app.mediafire.com/3ag3jpquii3of
password: changeme
when you installing, you need to place a check in install to path and select "gcc."

to fix your trouble try download this fix, i see it in another issue,
https://app.mediafire.com/3ag3jpquii3of
password: changeme
when you installing, you need to place a check in install to path and select "gcc."

Hi Ivan,
I have checked and this library was created in working hours as a employee/contractor of Wasmer and for the specific needs of the company. This means that Wasmer is the rightful proprietor of the software (feel free to check the "4.2. Ownership of Contractor Work Product." of our contract agreement if you have questions). I have no idea why the LICENSE file stated otherwise, but I corrected it so there's no confusion on this.
In any case, of course I'd be happy for you to maintain the project and provide the love it deserves.
If interested let me know and I'll add you as maintainer of the repo

For the context: https://mnt.io/articles/i-leave-wasmer/.
You are so hilarious. How can you imagine I can work for someone like you again?
Wasmer is not using this project anymore, https://github.com/search?q=repo%3Awasmerio%2Fwasmer sonde&type=code.
I'll simply fork the project. I hope you can change, one day.

As in any open-source project, as long as its LICENSE is respected, you can fork and use the project.
I'll close the issue, as it seems there's no interest in maintaining this repo, and the software ownership will continue being part of Wasmer


summary and trace files

Hi,
Where are the summary and trace files written to? I'm running the federated learning example script.
Thanks!

By default, summary files get written to /tmp/tensorboard (per here). You can customize this location in two ways:

specify the TENSORBOARD_DIR environment variable when executing a TFE script (for example, TENSORBOARD_DIR=/my/log/dir python run.py)
specify it programmatically in your python script with tfe.set_log_directory (for example, in this notebook


Add an option to delete the help embed message

This option allows the user to close the help menu after they're done using it.
This is because timed out menus clutter the bots channel a lot.
I also suggest to remove the embed after the menu so people who don't delete their embeds don't make the channel unreadable.

For me, the bots channel is meant for individual users to send commands in and leave, why would it be a problem for the channel to be cluttered? Do you actually read what messages are sent in that channel?

Yes, for the most part I do, but the point is that if the channel is a mess, it will take the user a while to even realise what's going on and it's just overall confusing.
I think even if the option will not be used by everyone, it doesn't impact the performance, it doesn't change anything for the users that don't care and overall has more pros than cons.


gradle url fix

could you update your gradle link in readme to
'com.github.windyzboy:CustomEditor:v1.0.1'
thanks

Yes, thank you. I forgot to change it.


support "Equation list" syntax

This commit enables to highlight "Equation list" syntax.
I'm not proficient to write a syntax highlight in vim, so I may be implementing something that doesn't make sense or doesn't match a style that this repository using.
#3

Feel free to merge this. Thanks!

Thank you, now it works!


Sample to create a new user

Extended the first sample console app to create new users.

Holding off on any updates to Dev until we merge with Master and have a clean go forward plan for the daily folders.  If you'd like to merge in the latest commits that I pushed to Dev this morning and then create a new branch for this PR we could go that route.

Abandoning in favor of reorganization branch work


Designing Catalog Page pt2

Ideation and low-fi/Mid-fi
market.mashup.com/explore
apisuomi
tyk.io
redthedocs.io

Issues:
#991
#988
#997


Remove instance_control

instance_control is some specific kind of deployment, therefore it was removed from this repo

:+1:

👍


Regarding pycocotools, Do i need to install it or not?

You only need to install if you are going to use model_main.py to train your model.
See my walkthrough here: 385
Of note: The Tensorflow maintainers have released TF2.x compatibility with the Object Detection API. I would recommend sticking with TF1.x for now as the new API is still being developed. Otherwise, you can see the changes in the processes here and try out the new API.


Multi instance compatability

Hi,
Great library really useful!
I was using this in a scenario where two instances of FontLoader could potentially be run at the same time. This meant that the second instance could overwrite the test div of the first causing it to fail.
Thought I would post what I did to fix it.
Cheers,
Ritchie

Hi, and thanks for the feedback,
I think you just added a redundant check. The test for testDiv you did here is already done just before the _runOnce function is executed here. So the _runOnce function won't run if there is already defined FontLoader.testDiv.


NameError: name 'mul' is not defined

Following the installation instructions listed in readme results in the following error after "[*] Performing common_factors attack."
File "[redacted]/RsaCtfTool/lib/number_theory.py", line 380, in ProductTree
    s = list(map(mul, s[0 : l >> 1], s[l >> 1 :]))
NameError: name 'mul' is not defined

This was the case both on MacOS and Kali Linux.

Should be solved


Latest version does not render full google map

In the latest release (html2canvas 1.0.0-alpha.12) following code renders google map partly and after zooming it does not load map at all:
`function html2image(){
html2canvas(document.getElementById('map'), {
	useCORS: true
}).then(function(canvas) {
	document.body.appendChild(canvas);
});

}`

While in the version html2canvas 0.4.1 following code everything works perfectly:
`function html2image(){
html2canvas(document.getElementById('map'), {
	useCORS: true,
	onrendered: function(canvas) {
		document.body.appendChild(canvas);
	}
});

}`
I think there is a problem with "onrendered" method in latest version
Can You help me with these?

Found solution in following issue (https://github.com/niklasvh/html2canvas/issues/345).
Sorry for creating new issue.


libsqsh should be 0-copy

Currently there are a few points where libsqsh needlessly copies data:

[ ] accessing entries from a table currently copies the entries. Instead it could be possible to access the data directly through a pointer, although there might be performance penalties due to unaligned access
[x] file content are currently always copied to a buffer owned by the SqshFileContext. If the files are uncompressed in the archive they could just directly point to the Mapping or if compressed to the decompressed buffer. #8
[x] Same for fragment. If the file only consists of a fragment, just point to the fragment directly instead coping to the buffer.
[ ] If we hand over a block to the decompressor, it is always a continues buffer in memory. If the memory region stretches multiple blocks, they are stitched together in a SqshBuffer. This is still needed for uncompressed blocks, but the decompressors implement streaming APIs, so we can hand them multiple slices without stitching them together. #5

Dependant: https://github.com/Gottox/libsqsh/issues/18

Closing this ticket. Replaced by individual tickets.


The ASP.net ebook preview link is broken

The link to the ASP.net preview ebook is broken, it just takes you to the Microsoft shop page

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

ID: 0b96880e-76c7-c6f3-c45f-13d9301e77da
Version Independent ID: 937c4b8a-8afc-98bb-ba22-02910a414656
Content: Blazor for ASP.NET Web Forms Developers
Content Source: docs/architecture/blazor-for-web-forms-developers/index.md
Product: dotnet-architecture
Technology: blazor
GitHub Login: @danroth27
Microsoft Alias: daroth

@tauheedul Thank you for reporting this problem. The aka.ms link is working now.


⚠ DDoS-Relay US-W-sfo3-02 has degraded performance

In 0c6cd0c, DDoS-Relay US-W-sfo3-02 (http://<IP_ADDRESS>:42069/;csv) experienced degraded performance:

HTTP code: 200
Response time: 105 ms

Resolved: DDoS-Relay US-W-sfo3-02 performance has improved in 71674b4 after 12 minutes.


Cancel button when editing project details from Dashboard

When the user is on the Dashboard tab for a project and clicks the "Edit Details" button, StatWrap opens up a way to modify the project details as well as the project tags.  The only available option is to "Save Details".  However, users should have a way to cancel any edits, and revert them.

Add a "Cancel" button to the right of the "Save Details" button
If the "Cancel" button is clicked, any edits should be discarded
After clicking "Cancel", the user should exit the editing interface and return to the view of the Dashboard

Ideally if the user had made changes, when they click "Cancel", step 2 should prompt the user "You have made changes.  Do you wish to discard those changes?"  This provides an extra protection if the user clicked Cancel by accident.

Hi @lrasmus, I opened PR #168 resolving issue #166, can I work on this issue now?

Hey @lrasmus can i work on this isssue

Hi @utnim2, it's great that you created a PR for solving this issue. It's a positive step for the betterment of the project. However, just a friendly reminder: it would be great if you could ask for an assignment from the project maintainer on the issue beforehand. If it's unassigned, please check if anyone else has commented to confirm whether they've started working on it or not, or if the issue is part of any milestone that has already been an ongoing effort by the team to resolve it.
If no one has requested an assignment, then only requesting an assignment is appropriate. By doing so, we can avoid duplicating efforts and ensure efficient use of resources. It's better to work on something else if an issue is already being addressed by someone else, as we already have a volunteer to address that issue. Please refrain from commenting unless the person who has assigned it becomes inactive on the issue. I hope you'll consider following good open-source practices for next time; this will help us to address more issues by different volunteers and help us to avoid spamming and reduce duplicate errors.

Hi @utnim2, it's great that you created a PR for solving this issue. It's a positive step for the betterment of the project. However, just a friendly reminder: it would be great if you could ask for an assignment from the project maintainer on the issue beforehand. If it's unassigned, please check if anyone else has commented to confirm whether they've started working on it or not, or if the issue is part of any milestone that has already been an ongoing effort by the team to resolve it.
If no one has requested an assignment, then only requesting an assignment is appropriate. By doing so, we can avoid duplicating efforts and ensure efficient use of resources. It's better to work on something else if an issue is already being addressed by someone else, as we already have a volunteer to address that issue. Please refrain from commenting unless the person who has assigned it becomes inactive on the issue. I hope you'll consider following good open-source practices for next time; this will help us to address more issues by different volunteers and help us to avoid spamming and reduce duplicate errors.

I have talked to @lrasmus on slack

Hi @utnim2, it's great that you created a PR for solving this issue. It's a positive step for the betterment of the project. However, just a friendly reminder: it would be great if you could ask for an assignment from the project maintainer on the issue beforehand. If it's unassigned, please check if anyone else has commented to confirm whether they've started working on it or not, or if the issue is part of any milestone that has already been an ongoing effort by the team to resolve it.
If no one has requested an assignment, then only requesting an assignment is appropriate. By doing so, we can avoid duplicating efforts and ensure efficient use of resources. It's better to work on something else if an issue is already being addressed by someone else, as we already have a volunteer to address that issue. Please refrain from commenting unless the person who has assigned it becomes inactive on the issue. I hope you'll consider following good open-source practices for next time; this will help us to address more issues by different volunteers and help us to avoid spamming and reduce duplicate errors.

I have talked to @lrasmus on slack

sure thank you for bringing this to my attention. It wasn't mentioned previously, which is why I suggested it.
I believe it would be beneficial to create a contributing guide for the StatWrap repository, along with incorporating community links. This would enable other contributors to be informed about ongoing discussions and help prevent duplicated efforts.
cc : @lrasmus.

Sorry for not responding quicker @Abhijay007 to your earlier inquiry!  Thank you @utnim2 for the contribution, I will review.  I will work on refining the contribution guide as well.

Sorry for not responding quicker @Abhijay007 to your earlier inquiry! Thank you @utnim2 for the contribution, I will review. I will work on refining the contribution guide as well.

No Problem @lrasmus

Sorry for not responding quicker @Abhijay007 to your earlier inquiry! Thank you @utnim2 for the contribution, I will review. I will work on refining the contribution guide as well.

No Problem @lrasmus, let me know if you need any assistance in developing that contributing guide.


Using Delphi ESR with Perception module.

This is a follow up to my question I asked here:
#5794
I was planning to to use the autonomouStuff driver to get tracked object ros messages, then try to build a converter to reformat that data to be in ContiRadar msg format to use with the radar_subnode.
However, am realizing some challenges.   The AStuff Delphi messages does not appear to have a probability of existence score..  And it appears the radar_subnode does use "probexist"  value in the radar object builder.   I am wondering  how important is this value?  What would happen to the fusion if I leave this score blank or put all to 100% or something?
Furthermore, I am just realizing it will take a little bit of work to extract various other information and get it into the same format as the ContiRadar format the radar_subnode uses, such as:  contiobs(i).longitude_dist_rms(), contiobs(i).longitude_vel_rms(), contiobs(i).oritation_angle() .
I was just wondering if it is possible if you can share the internal Delphi Driver that someone mentioned, and a version of the radar_process_subnode that is designed to work with the Delphi?   It would save us sometime.

@snuffysasa please continue your question on the same thread as it pertains to the same topic and is easier to track. Also, as mentioned in #5794 we do not currently support Delphi Radar. While internally we may have some drivers, we do not have the permission to release it. We do apologize for the inconvenience.
Thanks!

Okay, I will ask question in other thread.

Can close this one

It is highly possible that the attributes you are referring to are not actually getting used in perception module.  Just take a look of source code of perception module.


Bootstrapping without a definition file should be possible

In theory bootstrapping an image without provided definition should be possible. It's optional in this script:
https://github.com/gmkurtzer/singularity/blob/master/libexec/bootstrap.sh#L53
However, the bootstrap.exec script which calls bootstrap.sh requires user to provide a bootstrap definition file:
https://github.com/gmkurtzer/singularity/blob/master/libexec/cli/bootstrap.exec#L84
Bootstrapping without a definition file (without having to specify the linux distribution flavor) would be very useful for sanitizing images imported from docker (see #119).

This was pretty easy modification actually, good thinking! Please see [master 7e9aaa2].
Thanks!

Works like a charm - thanks for a quick fix.

Fantastic! I was just adding some test code for this too! Thank you!


Cinder CSI Raw block volume support

Is this a BUG REPORT or FEATURE REQUEST?:
/kind feature
What you expected to happen:
CSI Raw block volume support has been added in v1.11 as alpha feature, we should add same support to cinder csi driver

/remove-lifecycle stale

In progress , https://github.com/kubernetes/cloud-provider-openstack/pull/563


[1.5] Fix broken link to Consul

old link is showing up in BLC as 308

Overriding CI requirements from newer branches.

Overriding CI requirements from newer branches.


Global synchronization

Is there a way to achieve a global synchronization call as it is in MPI.Barrier() in mpi4py?

@Folorunblues That, and many other patterns, are not implemented inside osBrain.
Since osBrain is based on ZeroMQ you can, however, implement any communication pattern you need without requiring too much effort. I strongly recommend you to have a look at ØMQ - The Guide. There you will find lots of examples for different communication patterns for different needs. :blush:

@Peque Thank you for your prompt reply! I will take a look at the guide. Is osbrain 0.70 coming out any time soon?

@Folorunblues I don't think so. Unfortunately, I am no longer actively developing this library, and it seems the project is not receiving lots of contributions either.

@Peque, I quite understand. I believe the 0.6.5 is great and still has all the necessary features. Thanks again for your response!

@Folorunblues Glad you find it useful! :blush:
Let me keep the issue open for contributions.


[REQ] Irrigate twice per day

I'm struggling about the configuration of the module if I would like to irrigate twice per day, since the calculation of run time is made once per day (i.e. at 11PM).
How it is possible to configure the irrigation twice per day?
Would it be okay if I configure an automation that is triggered based on a time pattern, call the service calculate_zone(), wait a small delay in order to finish calculations, and check if the zone requires irrigations?

The integration just calculates the daily duration for irrigation per zone. All the rest happens in your automation.  For example you could the duration divide by 0.5, stop the irrigation, wait for some time and start irrigation again.
{{states("sensor.smart_irrigation_standard_zone_1")|float * 0.5}}

Yes, you could absolutely do that. Call calculate when you want and reset bucket. Just make sure that there is weather data to calculate with before.

Thank you both. But then I have a question. @gatonero said it "calculates the daily duration for irrigation per zone".
So if I irrigate the first time, I am giving the water for the full day, so the second irrigation, what would it do? The second calculate() call, will report the water missing until 11PM or for the subsequent 24h?
I am missing the meaning of the word daily here: "calculates the daily duration for irrigation per zone".

@gatonero is not entirely correct 😂. It calculates the irrigation required based on the data you feed it. So if you do it once per day it takes a days worth of data so calculates essentially for the day. If you calculated every 4 hours would be taking the data for that 4 hours and calculate how much irrigation you need to make up for moisture lost in the 4 hours. Hope that helps.

Thank you VERY much, much clearer now. It computes the amount of water required to compensate for the water left in the previous weather data. If you give 24h of history, it is the water required to re-integrate the water lost in the previous 24h. If you give only the last 12h, it does so for 12h.
Thank you

@jeroenterheerdt couldn't this been covered by https://github.com/jeroenterheerdt/HAsmartirrigation/wiki/Automation-examples#example-automation-4-one-valve-with-extra-check-on-todays-forecast-to-avoid-over-irrigation

without a diag file created just before each calculate there is no way to tell you what is happening here. But... one thing: the bucket is mm or inch, not L.

home-assistant_smart_irrigation_2023-09-28T15-38-27.166Z.log
I dont' know if this is the diag file you were looking for... But the behavior is easily reproducible, please, take a look at this video:
https://github.com/jeroenterheerdt/HAsmartirrigation/assets/23707134/180bd962-4ced-4418-9a5d-fb26f553616a

Under Settings -> Integrations -> Device you will find the button for the diagnostic file.

Under Settings -> Integrations -> Device you will find the button for the diagnostic file.

The log file I posted is from that exact location. However, having looked inside, I think the video is more auto-explanatory (but you will find both in my post above)...

home-assistant_smart_irrigation_2023-09-28T15-38-27.166Z.log
I dont' know if this is the diag file you were looking for... But the behavior is easily reproducible, please, take a look at this video.
Here, the bucket increases from 4.3mm to 5mm to 5.6mm, in less than a minute. The behavior only applies when you "force calculate". I would have expected that the PyETO takes in consideration the elapsed time since the last calculation to recompute the bucket...
Media1.1.mp4

pyeto has no notion of that. If you calculate, we take the data that you have collected since the last calculate. If the calculation is successful, we delete the data used. So the second time around it's just taking whatever you collected since the last time.

Ok, so... When you call the service to calculate the delta to be added to the bucket, it goes on until reaching this function:
https://github.com/jeroenterheerdt/HAsmartirrigation/blob/ada3224c8166e8aae728ae788c591320338496fb/custom_components/smart_irrigation/calcmodules/pyeto/__init__.py#L75
According to the name of the function "per_day" and to the documentation of PyETO (https://pyeto.readthedocs.io/en/latest/api.html#evapotranspiration), the result is in [mm * day^-1].
Thus, if you calculate once per day, this is fine (you multiply by 1*day that does not change the result), you can directly add the delta to the bucket. If instead you want to irrigate twice per day, as per this issue, you need to multiply the delta value by 0.5 days (which halves the result!).
Generalizing, in my opinion, the delta returned by all PyETO calculate() calls should be multplied by the time that has passed between the first weather data and the last weather data. This would fix, but let's discuss.

Right, we can definitely add that. The reason why it is not there is that I expect you to calculate once per day. Anyway just great addition!

But how about Passthrough and static modules? How would be handle those? The same logic as proposed for pyeto?

right, so that makes sense. Then all calc modules will return values in mm/day (or inch/day) and we apply the same logic to all.

Thank you very much for your work.

HI @jeroenterheerdt,
thanks for addressing this issue.
I've noticed that the hour_multiplier is missing in the calculation of the bucket: https://github.com/jeroenterheerdt/HAsmartirrigation/blob/10e46c3379c88968b7259de8b456699a34e2a9fd/custom_components/smart_irrigation/init.py#L615
should be something like:
  hour_multiplier = weatherdata.get(const.MAPPING_DATA_MULTIPLIER,1.0)
  data[const.ZONE_DELTA] = delta*hour_multiplier
  data[const.ZONE_BUCKET] = bucket+delta*hour_multiplier

Regards.

Glad I made this change only in beta 😂


[SPARK-35528][DOCS] Add more options at Data Source Options pages

What changes were proposed in this pull request?
This PR proposes adding more methods to set data source option to Data Source Option page for each data source.
For example, Data Source Option page for JSON as below:

Before

After

Why are the changes needed?
To provide users various options when they set options for data source.
Does this PR introduce any user-facing change?
Yes, now the document provides more methods for setting options than before, as in above screen capture.
How was this patch tested?
Manually built the docs and check one by one.

Test build #139253 has started for PR 32757 at commit 97ebd51.

Test build #139253 has finished for PR 32757 at commit 97ebd51.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/139253/

Kubernetes integration test unable to build dist.
exiting with code: 1
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/43776/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/43776/

tests passed at https://github.com/itholic/spark/actions/runs/901299055.
Merged to master.


refactor: switch all arithmetic in standards to explicitly checked

I made the statement today that we do checked arithmetic for everything, so this PR intends to be extra careful.
Ideally and in most cases, overflow checks should be done through Rust (and recommended https://docs.near.org/sdk/rust/best-practices#enable-overflow-checks and https://docs.near.org/sdk/rust/introduction#create-a-new-project), but this is done as an extra-safety measure
Would be great to get another set of eyes to see if I switched one unnecessarily or something like this

Closing because opinionated and I'm not working on this anymore


Nice dice roll buttons

Replace the boring roll buttons with theme appropriate buttons.

"nicer" roll buttons applied, I am sure I can do better with time and thought.


Module not working on slicer 4.10.2 or nightly

Hello, when i try to compute my mesh stats i get this errors:
Traceback (most recent call last):

  File "C:/Users/lorenzo/AppData/Roaming/NA-MIC/Extensions-28257/ShapeQuantifier/lib/Slicer-4.10/qt-scripted-modules/MeshStatistics.py", line 177, in onRunButton
    self.tableField, self.modelList, self.tabROI, self.mainLayout)

  File "C:/Users/lorenzo/AppData/Roaming/NA-MIC/Extensions-28257/ShapeQuantifier/lib/Slicer-4.10/qt-scripted-modules/MeshStatistics.py", line 363, in displayStatistics
    self.computeAll(fieldArray, fieldValue[shape.GetName()], 'None')

  File "C:/Users/lorenzo/AppData/Roaming/NA-MIC/Extensions-28257/ShapeQuantifier/lib/Slicer-4.10/qt-scripted-modules/MeshStatistics.py", line 434, in computeAll
    fieldState.percentile5 = self.computePercentile(array, 0.05)

  File "C:/Users/lorenzo/AppData/Roaming/NA-MIC/Extensions-28257/ShapeQuantifier/lib/Slicer-4.10/qt-scripted-modules/MeshStatistics.py", line 423, in computePercentile
    return round(valueArray[ceilIndex], self.numberOfDecimals)

IndexError: only integers, slices (`:`), ellipsis (`...`), numpy.newaxis (`None`) and integer or boolean arrays are valid indices

`
This module works flawlessly on slicer 4.8.1.
Can you kindly help me? thanks

@bpaniagua This seems to be a repeat of your #7
Could either of you (@bpaniagua, @maxibers) please do either of:

Provide a mesh that reliably produces this issue
Try some print-line-debugging: add the line print(ceilIndex) just before the offending line. and report the results in this issue thread

The second option would look something like the following:
    def computePercentile(self, valueArray, percent):
        #  Function to compute different percentile
        #  valueArray is an array in which values to compute statistics on are stored
        #  percent is a value between 0 and 1
        #  The lowest value is taken
        valueArray = numpy.sort(valueArray)
        index = (valueArray.size * percent) - 1
        ceilIndex = int(math.ceil(index))
        print(ceilIndex) # <-------- This line is the important addition
        return round(valueArray[ceilIndex], self.numberOfDecimals)

@maxibers, you would do this by editing the file C:/Users/lorenzo/AppData/Roaming/NA-MIC/Extensions-28257/ShapeQuantifier/lib/Slicer-4.10/qt-scripted-modules/MeshStatistics.py.

This seems to work now with the latest changes. Lets see what @luciacev says.
@maxibers could you please test with the latest master of this code or wait to test via installing extension on the nightly package from tomorrow?

with the latest nightly it seems to be working just fine, i'll reply here if i find any other bug.
Thank you @JEHoctor @bpaniagua for your help, really appreciated


Automatic commit: Move 'abap-environment-custom-theme' from QA to Production

Automatic commit: Move 'abap-environment-custom-theme' from QA to Production

Thanks for using the v2 parser syntax!!  Great work.


Added support for internal constructors that are accessible via InternalsVisibleToAttribute

Added support for detecting internal default constructors in the source assembly that are accessible to the destination assembly via the InternalsVisibleToAttribute.  I have not ran the tests in net1_3.  I updated the tests project to target netcoreapp2.1 as otherwise my tests would not run, despite installing the 2.0 SDK.

@jpeters-programmer netcoreapp2.1 is out of support, would you consider changing the framework moniker to net6.0?

@jpeters-programmer The test project has been upgraded to .NET 6.0. Please consider syncing your branch to resolve the current conflict so this PR can be reviewed.


"random" segmentation faults

Running rake assets:precompile causes a segmentation fault.
Stack trace here: https://gist.github.com/constantm/b2b09a55d96fa2f1cce2

I also get a seg fault
Stack trace: https://gist.github.com/frankh/423c97183ceae41a526b

Having similar segfaults on Ubuntu. Works really well other than that..

Also, my segfaults aren't necessarily with precompile -- they're just random. I'll change a .sass file, reload the page, and it'll work. I'll change the same thing again, and it'll segfault.

This is occurring for me as well.  This is very much a work in progress still.  I'm going to work on debugging it.

I think I've corrected this issue - can you guys try updating to version 0.0.5?

Seems to have fixed it for me (hard to know for sure because it didn't segfault every time)
Thanks!


don't use bower

would you consider a pull request which got rid of bower along the lines of ember-cli-moment-shim
(see https://github.com/jasonmit/ember-cli-moment-shim/blob/master/index.js)
The idea is to import the front-end dependency as an npm dependency, then use require.resolve to look up the path in ember-cli-build.

+1, I think this is a good way to go.

@lukemelia thoughts on this?

Definitely open to this!

In progress in #18

Published as 2.0.0-beta.0. Can I get some volunteers to try it out?

@lukemelia looks good. I notice that https://github.com/yapplabs/ember-cli-bourbon/blob/v2.0.0-beta.0/blueprints/ember-cli-bourbon/index.js#L9 is still present, is this just so it still works with people using bower or an omission?

@oligriffiths thanks for the catch. Addressed in #19


chore: adding a basic bench using pm-mode

converted to a draft as I don't know if we should merge it on the same repository.


Generating dot graph got blank png image

Generates dot graph from below source, the output png file is blank.
puml generate test.puml -p > test.png

@startdot
digraph foo {
  node [style=rounded]
  node1 [shape=box]
  node2 [fillcolor=yellow, style="rounded,filled", shape=diamond]
  node3 [shape=record, label="{ a | b | c }"]

  node1 -> node2 -> node3
}
@enddot

Generation of svg is ok.
puml generate test.puml -s > test.svg
puml version is 0.5.0

I was able to reproduce it, however it's not that the png file is empty. It's missing some information. Some applications could open it, while others couldn't. You could also check the size of the file and see that it's not empty.
So next I tried to use the plantuml jars command line. Without using stdin and stdout the resulting png is fine:
java -Djava.awt.headless=true -jar plantuml.jar -tpng test.puml
However when using stdin and stdout I get a broken png file:
cat test.puml | java -Djava.awt.headless=true -jar plantuml.jar -tpng -p > test.png
So this is problem with plantuml and using stdout and not node-plantuml. From a running a few tests this only seems to be a problem when using dot syntax.


updated plan-feature-model.md about feature params

I have written more description on how to use the features and their params.
PS. I have based the info about written "true" / "false" from canUseFeature() where there is:
if ($featureValue === 'true') {
            // If feature value exists and has a written true value
            return true;
//

And what about this mod to docs?

I added partially (without the expanding) some time ago but outside the PR since this was closed by version and I messed up.

ok, thank you :)


lanetix/issues#1628 Global search & Changes tracking worker does not retry problematic messages from RMQ

lanetix/issues#1628 @lanetix/engineers CR Please.  Thanks

:ice_cream:


Elegant Hubris Slum Lord search doesn't work

Trying to find Elegant Hubris Slkum Lord near agnostic, nodes:
Arcane Capacitor
Faith and Steel
Overcharge
Endurance
Devotion
Smashing Strikes
Sanctum of Thought
Light of Divinity
Holy Dominion
Divine Fervour
Unfortunately it doesn't find a single Slum Lord there.

Solved! Thank you for the report.


Order references alphabetically

Signed-off-by: Richard Hartmann<EMAIL_ADDRESS>

you miss [coc] and [lazy]


U - Fix CSS linter errors: prose.short_description errors

The linter will check that pages correctly include this ingredient.
Acceptance criteria

[ ] There are zero errors reported by the linter for the "prose.short_description" ingredient, when run against https://developer.mozilla.org/en-US/docs/Web/CSS

The (very few) errors here have all been fixed.


Cqlsh serverless v2

This PR adds serverless support for CQLSH. It was previosuly merged, but dtests later discovered a bug in python driver. The bug should be fixed now, so let's merge this again.
@fruch As you had more luck reproducing the issue with dtests than us, could you try and run them with this PR to make sure it works now?
Fixes https://github.com/scylladb/scylla-tools-java/issues/317 (again)

This PR adds serverless support for CQLSH. It was previosuly merged, but dtests later discovered a bug in python driver. The bug should be fixed now, so let's merge this again.
@fruch As you had more luck reproducing the issue with dtests than us, could you try and run them with this PR to make sure it works now?

i could try it out in Sunday, but mean time run it on scylla-ci to see its passing gating (it was noticed on some of the gating tests)

Fixes https://github.com/scylladb/scylla-tools-java/issues/317 (again)

CI passed. @fruch did you have time to run those dtests?

CI passed. @fruch did you have time to run those dtests?

Didn't got to it, I'm compiling it now.

I've run locally the two suites that were problematic, and didn't seen the issue:
./scripts/run_test.sh --scylla-version=5678  cql_cast_test.py json_test.py

pinging @scylladb/scylla-maint for merge


To many Textures "I think" Bug (What killed OPIS for us.

This is a bug that sadly also ruined Opis for our server. I hoped it was not an issue with plain Mapwriter but it is.
http://pastebin.com/pWbqCa8p
I finally had time to give it a shot was going to try your little radar addition for the server side :(

are you using a certain pack or so where i can test it with.
i only seen this crash in posts but never on my own machine

I don't have a public pack but if you use MCUpdater:
http://files.mcupdater.com/MCUpdater-recommended.jar
And add this URL:
http://updater.stonelegion.com/minecraft.xml
And use the Private server and then add the mapwriter to the mods folder it will happen to you.
Sadly it's a tad complex.
It seems to happen when the texture sheet reaches a certain size. Depending how many mods I have if I remove a bunch it will work if I keep low amount texture mods it's fine but once I add to many to make the main sheet too big it seems to bust it.

have a fix that will prevent the crash from happening.
only downside is that the block(s) on wich it fails won't render at all.
if you're oke with that you can download it here:
https://www.dropbox.com/s/8mdifbokax1eoxy/MapWriter-1.7.10-2.1.5-Beta.jar?dl=0

Thank you.  Example screenshit:
http://i.imgur.com/PL4xVbp.png
You can see where it worked one time I think it was another version tbh posted on MC Forums a long time ago. Sadly lost it. But you can see the working area vs the red blood looking stuff now.
Thank you for looking into it, it means a lot.

Just to add to this I removed my downloads folder recently cleaning my SSD Crap! But I think It was jake_stafunk version that worked before.
http://www.fansana.de/download/MapWriter-1.7.10.jar
Sadly I can't get his site working but maybe he had found a fix or did something in another method.

could you send me your log of the test?
i asked jake what he changed compared to my git, but he said it was about the same.... so i'm not sure what the difference is....

oke, second try to fix the bugs:
https://www.dropbox.com/s/s4mzbyfuozc6pbu/MapWriter-1.7.10-2.1.5-Beta-2.jar?dl=0

Sorry about the delay friend. I been away for a few days as my house had lost AC.
Looks like you fixed it :)
http://i.imgur.com/3uKf9ry.png
Now I have to try the MP addon :)

good, then i can close this bug finally ^^


Removes unnecessary shuffle from randomSample method of Collection and Sequence

This PR removes unnecessary shuffle from randomSample method of Collection and Sequence.
// FIXME: necessary?
result.shuffle(using: &rng)

Since randomSample method already Swap selected element with a randomly chosen one in the reservoir there is no need to do that extra shuffle for the reservoir. This was marked as // FIXME by removing it, randomSample still randomly selects the specified number of elements from this sequence, and the RandomSampleTests runs successfully.
Checklist

[ ] I've added at least one test that validates that my change is working, if appropriate
[x] I've followed the code style of the rest of the project
[x] I've read the Contribution Guidelines
[x] I've updated the documentation if necessary

Whether the shuffle is unnecessary or not is a mathematical question. I'm not sure I understand how you arrived at the conclusion that "there is no need to do that" based on your description here, although perhaps it is straightforward. Can you show a proof as to why each element of the original element is equally likely to found at any particular position of the result even without this shuffle?

The shuffle is necessary.
The elements in self that aren't part of the first k are indeed equally likely to appear at any particular index of the result due to
let j = Int.random(in: 0..<result.count, using: &rng)

but the first k elements of self can only appear in the result at the position they're originally in. This is easy to see when k is equal to self.count: without the shuffle, rng is only used inside the loop body which is no longer reached, and indeed array.randomSample(count: array.count) will just return a copy of the original array.

Thanks @timvermeulen for clarifying. i guess it's important now to look at what reservoir sampling algorithm says, it works pretty much in two steps:

Fill the result array with the first k elements from the original array. This is called the "reservoir".
Randomly replace elements in the reservoir with elements from the remaining pool.

According to reservoir sampling algorithm each number is selected with the probability of k/n you can find the mathematical proof here and here by induction. @xwu
Example

Pick 3 numbers from [10, 20, 30, 40]. Make sure each number is selected with a probability of 3/4
First, pick [10, 20, 30] as the initial reservoir
Then pick 40 with a probability of 3/4
For 10, it stays with a probability of
P(40 is not selected) + P(40 is selected but it replaces 222 or 333)
= 1/4 + 3/4*2/3 = 3/4
The same case with 20 and 30
Now all the numbers have the probability of 3/4 to be picked

That said, giving each element equal probability of being selected i think shuffling the reservoir is an extra step perhaps a side effect of randomSample method that changes the expectations when using it since it uses reservoir sampling algorithm.

Now all the numbers have the probability of 3/4 to be picked

This doesn't address the problem that is at discussion here, which is that not all the numbers have equal probability of being picked first. See the README for more details.

Ah, I clearly misunderstood the purpose of the TODO. Whether we need to shuffle is not a mathematical question, it's a question of whether or not we want the order of the sample to be random as well.

Right — this is about the surprise factor of the result sometimes having elements in their initial order, not the likelihood or weighting of particular elements in the result. While random sampling doesn't necessarily have to guarantee that the randomly selected elements will also be in a random order, I'm concerned that it will be surprising for the user to have that not be the case. The related guide covers the topic in the Post Sample Shuffling section.
Since this is an intentional design decision, I'm going to close this for now. Feel free to open a discussion in the forums if you'd like to talk about this more.


Feature: Remove Images Associated with Stopped Containers

Description: Add an option to clean up images associated with containers that have been stopped. This would be especially useful in environments where containers are stopped frequently.
Example:

./dockclean --remove-stopped

Hi @mmuazam98, I would love to solve this issue too. Could you assign this issue to me.

Hi @mmuazam98, can we close this issue now since you’ve already merged the PR?


(Sonar) Fixed finding: "Utility classes should not have public constructors"

Remediation
This change fixes "Utility classes should not have public constructors" (id = java:S1118) identified by Sonar.
Details
This change adds private constructors to utility classes. Utility classes are only meant to be accessed statically. Since they're not meant to be instantiated, we can use the Java's code visibility protections to hide the constructor and prevent unintended or malicious access.
Our changes look something like this:
   public class Utils {
+    private Utils() {}
     ...

More reading

https://rules.sonarsource.com/java/RSPEC-1118/

🧚🤖  Powered by Pixeebot

FYI - This change was autogenerated from a GitHub app - called Pixeebot. A code-quality GitHub App; like Dependabot, but for source code. Feel free to check it our for more details for how you can install it onto your project's repo for continued code hardening and code security recommendations.