Documentation added docs and numpy docstrings

full html file with the documentation can be found in docs/_build/html/index.html

Can you please run:
git rm -r docs/_build/
And then push again to this repository?
It is currently a bit too difficult to review since GitHub doesn't handle the number of files very well...

Also, are all of the .rst files auto-generated with some command, and then you edit them?
If so, maybe the repository should not include the ones that were not edited, and we will just generate them as part of the build process. We can have a short call on this if you'd like.


[fix docs compiler warnings] Nicks pallet

This PR fixes the 7 compiler warnings emitted by running RUSTFLAGS="-W missing_docs" cargo check -p pallet-nicks by adding missing documentation throughout the crate.

bot merge


Include variant in AdjointValue.h

d971f125d966 added a usage of std::variant and std::holds_alternative to SILOptimizer/Differentiation/AdjointValue.h, but did not include variant directly. This caused issues while building on Linux.
Failing run: https://ci.swift.org/view/Swift rebranch/job/oss-swift-rebranch-RA-linux-ubuntu-18_04/3239/
/home/build-user/swift/include/swift/SILOptimizer/Differentiation/AdjointValue.h:234:8: error: no template named 'variant' in namespace 'std'
  std::variant<unsigned int, VarDecl *> inner;
  ~~~~~^
/home/build-user/swift/include/swift/SILOptimizer/Differentiation/AdjointValue.h:218:17: error: no member named 'holds_alternative' in namespace 'std'
    return std::holds_alternative<unsigned int>(inner);
           ~~~~~^
/home/build-user/swift/include/swift/SILOptimizer/Differentiation/AdjointValue.h:218:44: error: expected '(' for function-style cast or type construction
    return std::holds_alternative<unsigned int>(inner);
                                  ~~~~~~~~ ^
/home/build-user/swift/include/swift/SILOptimizer/Differentiation/AdjointValue.h:234:41: warning: private field 'inner' is not used [-Wunused-private-field]
  std::variant<unsigned int, VarDecl *> inner;
                                        ^

@swift-ci please smoke test

@etcwilde would you have any suggestions on how I could avoid these mistakes? I'm not sure why these were not caught during the swift-ci tests.

Usually I'd recommend "including what you use". If you use variant, pull in variant, vector, pull in vector, etc....
You were likely getting it transitively through something LLVM was including. I noticed it in the rebranch work, LLVM probably changed some header so that it was no longer recursively including the variant type somewhere between stable/20221013 and stable/20230725.

Thank you that makes sense!

It's pointed at a branch that cuts off of llvm, but yeah. Main currently uses the stable/20221013, but I am working on moving it to the stable/20230725. I sent it to main since it's low-risk and I am trying to minimize merge conflict potential between main and rebranch.


Fix screenshot.

[Enter feedback here]
In this url,
https://docs.microsoft.com/en-us/azure/data-factory/data-flow-conditional-split
the screenshot under “In the Service UI” should have shown the option [x] All matching conditions, which sets the ‘disjoint’ option to ‘True’.

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

ID: ba433ccf-eede-2219-e94c-1066ad116459
Version Independent ID: 0b134410-9b1a-0dbf-584c-6eb6b2fbca18
Content: Conditional split transformation in mapping data flow - Azure Data Factory & Azure Synapse
Content Source: articles/data-factory/data-flow-conditional-split.md
Service: data-factory
Sub-service: data-flows
GitHub Login: @kromerm
Microsoft Alias: makromer

Thanks for the feedback! We are taking a look into this and will get back to you soon.

Hello @Help4Access
Current Configuration (As per current ScreenShot)
There are 3 output streams generated.
Every row matching the first condition goes to output stream moviesBefore1960.
All remaining rows matching the second condition go to output stream moviesAFter1980.
Those don't match will go to the Default Stream.
If my understanding is incorrect, please free to add additional context.
You'd like to add an additional screenshot with the below information.  Can you please help me understand the ask behind this ?

The equivalent script will be
CleanData
    split(
        year < 1960,
	    year > 1980,
	    disjoint: true
    )

Hello Svijay,
Looks good. Please proceed.
Kind Regards,
Sasha Froyland
Director of Business Development & Partnerships
(Direct) +1<PHONE_NUMBER> | (Cell) +1<PHONE_NUMBER> | Online Calendarhttps://www.help4access.com/schedule/
help4access.com
@.***
From: Svijay-msft @.>
Sent: Wednesday, November 10, 2021 2:34 AM
To: MicrosoftDocs/azure-docs @.>
Cc: Sasha Froyland @.>; Mention @.>
Subject: Re: [MicrosoftDocs/azure-docs] Fix screenshot. (Issue #83419)
Hello @Help4Accesshttps://github.com/Help4Access
Current Configuration (As per current ScreenShot)
There are 3 output streams generated.
Every row matching the first condition goes to output stream moviesBefore1960.
All remaining rows matching the second condition go to output stream moviesAFter1980.
Those don't match will go to the Default Stream.
If my understanding is incorrect, please free to add additional context.
You'd like to add an additional screenshot with the below information. Can you please help me understand the ask behind this ?
[image]https://user-images.githubusercontent.com/66949976/141096425-7f4a10dc-44cd-4a8a-b344-7c780d157085.png
The equivalent script will be
CleanData
split(

    year < 1960,

        year > 1980,

        disjoint: true

)

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/MicrosoftDocs/azure-docs/issues/83419#issuecomment-964999681, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AFTQ3IE3D7K4VE4VSGB7MFLULJDCVANCNFSM5HMSSHVA.
Triage notifications on the go with GitHub Mobile for iOShttps://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Androidhttps://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

I have assigned the issue to the content author to review further and update the document as appropriate.


Hosts with multiple residues

Find a way to automatically build the systems when the hosts have multiple identical fragments connected.

solved


Memory Leak when running the UI in Firefox

Current Behaviour
When running the webui in Firefox you can get an out-of-memory error.
Reproduce

Open the webui in Firefox
Login so tat you get the Cesium globe
Wait

After a couple of minutes the out-of-memory-error will appear,

Does it happen with the globes in Cesium Sandbox too?
May also ask the CfS team if they observe similar things.

As Firefox is a very popular browser, I make this a blocker.
However, in Chrome, the problem does not occur.

Seems to be fixed by #61. @AliceBalfanz and @dzelge please verify on Linux. Reopen if problem persists.


Allow usage of the "adjust forecast" feature

This adds the "actual" query parameter to the estimate method, needed to use forecast.solars "adjust forecast" feature.
This as a first towards implementing this feature request.

any updates to this PR when this PR is planed to get merged/released?

When all the CI checks are passing 😉 It needs to add tests for full pytest coverage
./Klaas

@GreenOpposite could you check that? I'm not a python dev

When I run the tests locally, everything passes and I get a code coverage of 95%, but the automatic test on GitHub fail to run with the error Error: Codecov token not found. Please provide Codecov token with -t flag.

After a bit of investigation, it seems like what's happening is that the Codecov GitHub integration needs a token that my forked repository is missing. A maintainer has to approve the workflows for them to run in the context of this repository. @klaasnicolaas

Any updates on the state of this PR? Do I need to do something? @klaasnicolaas

What I'm wondering is whether we should pass the actual parameter with every request by default (if you have an API key), or only when the value is higher than 0.
The only thing I'm missing is a test that tests what happens if you specify a value higher than 0.
./klaas

A value of 0 is also used to signal invalidation/reset of the previously send correction data. So not passing an actual value to the estimate() function has the effect of deactivating the correction.
a = estimate()
b = estimate(actual=15)
c = estimate()

If you don't send 0 every time, then a and c would have different values, which I would argue is not intuitive.
What kind of testing is missing exactly?

Another thing I was wondering: suppose someone has solar panels in 2 zones and therefore also a split forecast.solar, to what extent will this have an effect if you send the full actual of both zones together (because you often have that as an entity) every time. 🤔
./Klaas

Another thing I was wondering: suppose someone has solar panels in 2 zones and therefore also a split forecast.solar, to what extent will this have an effect if you send the full actual of both zones together (because you often have that data as single entity) every time. 🤔
./Klaas

I think that might lead to wrong values being predicted, but I also don't see how that could be easily mitigated. You would need separate data for each zone and send the appropriate data with each request.

Will this be supported/used in the HA integration?


bug: svg-spinners nuke the css when used

Version
@nuxthq/ui: v2.4.0
nuxt: ex: v3.5.3
Reproduction Link

[x] ~Stackblitz isn't working currently from tablet, I'll make sure to add it once I'm home/office.~
~Here is a simple Stackblitz repro~
Here is an updated Stackblitz repro

Steps to reproduce
Try to use any of the SVG-Spinners inside the <UIcon/>.
What is Expected?
The SVG-Spinner gets loaded and rendered correctly.
What is actually happening?
Before changing the first heroicons-pencil:

After I change it with an SVG-Spinner:

Other icons (following the procedure of installing and declaring them inside the nuxt.config.ts) work correctly.

While trying to create the stackblitz repro I noticed that it gets nuked even more.

Not to mention that icons get used even if I don't specify them inside nuxt.config.ts:
export default defineNuxtConfig({
  ui: {
    icons: ['ph', 'svg-spinners']
  }
})

So maybe there are two issues here...

I'm noticing that it is regardless of where the svg-spinner icon gets placed, even just in a pre tag nukes everything:

i-svg-spinners-blocks-shuffle-3

get it too

Not just SVG spinners, but all icons with animation

Is this issue still present? Does using the dynamic prop fix it?

Is this issue still present? Does using the dynamic prop fix it?

Tested on the original stackblitz repro, updating both<EMAIL_ADDRESS>and<EMAIL_ADDRESS>the issue does seem to be solved. Even without dynamic.
Just out of curiosity: do you have any clue what was causing this?

Not really, maybe an update of https://github.com/egoist/tailwindcss-icons?

Not really, maybe an update of https://github.com/egoist/tailwindcss-icons?

possibly... found a change that was made for 1.7.2 about this topic.
Anyway, thanks again for reminding me to test this.

No worries, I'm just trying to clean issues before v3 😊


Ultraviolet Enum Returning Incorrect Values

wttr.in has UV values ranging from 1 to 12. This is supposed to get mapped to LOW, MODERATE, HIGH, VERY_HIGH, or EXTREME. However, the mapping is incorrect due to declarations using the auto keyword. e.g. If wttr returns a UV value of 5, EXTREME gets returned instead of MODERATE.
By starting the enum values at 13, it is outside the range of valid wttr values, so it will return the correct enum value.

Thank you sooooo much for this! ❤


[#730]Add soul-pulgin-global Test Case

// Describe your PR here; eg. Fixes #issueNo

Make sure that:

[x] You have read the contribution guidelines.
[x] You submit test cases (unit or integration tests) that back your changes.
[x] Your local test passed mvn clean install -Dmaven.javadoc.skip=true.

Codecov Report

Merging #732 (06d2326) into master (faf10df) will increase coverage by 0.50%.
The diff coverage is n/a.

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 faf10df...06d2326. Read the comment docs.

I hope I didn’t mess this up I’m afraid to move thank you
Debbie Slater

From: Codecov<EMAIL_ADDRESS>Sent: Monday, December 14, 2020 1:03:28 AM
To: dromara/soul<EMAIL_ADDRESS>Cc: Subscribed<EMAIL_ADDRESS>Subject: Re: [dromara/soul] [#730]Add soul-pulgin-global Test Case (#732)
Codecovhttps://codecov.io/gh/Dromara/soul/pull/732?src=pr&el=h1 Report
Merging #732https://codecov.io/gh/Dromara/soul/pull/732?src=pr&el=desc (06d2326https://github.com/dromara/soul/commit/06d23269e7e22494e2c3ad373f1dd49cc34f8eff) into masterhttps://codecov.io/gh/Dromara/soul/commit/faf10dfee279be3ebe1ba8194c15efdf5e5f769c?el=desc (faf10dfhttps://github.com/dromara/soul/commit/faf10dfee279be3ebe1ba8194c15efdf5e5f769c) will increase coverage by 0.50%.
The diff coverage is n/a.

Continue to review full report at Codecovhttps://codecov.io/gh/Dromara/soul/pull/732?src=pr&el=continue.
Legend - Click here to learn morehttps://docs.codecov.io/docs/codecov-delta
Δ = absolute  (impact), ø = not affected, ? = missing data
Powered by Codecovhttps://codecov.io/gh/Dromara/soul/pull/732?src=pr&el=footer. Last update faf10df...06d2326https://codecov.io/gh/Dromara/soul/pull/732?src=pr&el=lastupdated. Read the comment docshttps://docs.codecov.io/docs/pull-request-comments.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHubhttps://github.com/dromara/soul/pull/732#issuecomment-744255319, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AMEX3TQZGNDMOIDTFEEZIE3SUXBFBANCNFSM4U2KNQGA.

@flwrchild42  who are you?


lessThan/greaterThan for strings

For lexical order queries, we need lessThan/greaterThan queries also on strings.

@derolf Good idea I'll implement it

Fixed with stable release


image registry not consistent across resources

Description:
Envoy gateway controller uses defined registry in manifest compared to automatically deployed proxy deployments that miss registry in image specification.
image: docker.io/envoyproxy/gateway:v1.1.2

vs
image: envoyproxy/envoy:distroless-v1.31.2

This causes proxy pods end up in ImageInspectError at clusters without set default registry.
It does not seem that repository for proxy deployment is configurable through helm.
Repro steps:
Follow installation docs.
Create gateway and httproute resources.
Check image specifications of deployments.


Cloning config and patches from the master branch instead of a specific branch

Description of problem
When trying to build the kernel, I am using the branch stable-1.7 but when running build_kernel.sh, it is cloning from the master branch and not switching to stable-1.7 which results in a missing config file.
https://github.com/kata-containers/packaging/blob/fdacac9e81c0c16affa246c2fb56ca06b29dade8/kernel/build-kernel.sh#L160
ERROR: failed to find default config /root/go/src/github.com/kata-containers/packaging/kernel/configs/x86_64_kata_kvm_4.19.x

Looking at the commit history, it appears the config file was dropped in the master branch but the changes haven't made it to the stable-1.7 branch yet.
Expected result
When cloning the repo, it should switch to the branch that is being used and not use the master branch to build
Actual result
It is building the kernel off the master branch and not the branch the user is using.

/cc @jcvenegas

Guessing we need to backport https://github.com/kata-containers/packaging/pull/646 and https://github.com/kata-containers/packaging/pull/657 to the stable branches.

we recently started to branch packaging,  it is a bug if is not able to found the patches directly.
it should work if we do go get pacakging and git checkout stable-1.7 and finally build_kernel.sh .
If in that case it should not need to download anything.

packaging is downloaded in a different place,  I agree that the patches and config should checkout to the current  branch or something similar.

When I initially cloned the repo to run build_kernel.sh it is in a different location but within the logs that I see I noticed
INFO: Clone config and patches
Cloning into '/root/go/src/github.com/kata-containers/packaging'...

So it appears to be cloning the repo to another location that is in the GOPATH but fails to realise that it is in a different branch.

It sounds like kernel/build-kernel.sh needs to check to ensure that it is not being run as root. If the users runs ./build-kernel.sh install, the script itself can call sudo for just the calls to install(1).
We need to explain this behavior in the README.md too of course.

@joshku so to try to summarize the the issue.

clone packaging in a not golang path.

cd /tmp
git clone packaging
cd kernel/

2 ) run the build kernel script
./build-kernel.sh  setup
# This will try to download packaging again because, the packaging repo is not in the gopath.

Is that right ?
But works if  instead you do, something like:
go get github.com/kata-containers/packaging
git checkout stable-1.7
cd  $GOPATH/src/github.com/kata-containers/packaging/kernel
./build-kernel.sh  setup
...

So the first and second step sound correct. What I did to get it to work is just to adjust the code at line 161 of build_kernel.sh to add the -b option. So instead of just a git clone <repo_url> it is now git clone -b <branch_name> <repo_url> and then it worked.
I suspect what you are saying is correct. I am not really sure what patches_repo_dir points to. But not really a 100% confident.

I believe that regardless of what I did, within the build_kernel.sh script it still calls a git clone of the packaging repo but it doesn't know if you are executing the script from a different branch than master. Therefore, when it is grabbing the kernel config and patches, it is grabbing it from the freshly cloned directory regardless of whether or not I have already downloaded the repo or not.

Rigth, so when I did those scripts I was expecting that people do a go get, and the extra git clone is if for some reason just download the script so it could get them. But seems really confusing flow.
So we can modify the script
to
https://github.com/kata-containers/packaging/blob/master/kernel/build-kernel.sh#L33 use the script dir
-readonly patches_repo_dir="${GOPATH}/src/${patches_repo}"
+readonly patches_repo_dir="${script_dir}/src/${patches_repo}"

And instead of download again the repo, just fail.
https://github.com/kata-containers/packaging/blob/master/kernel/build-kernel.sh#L238
-[ -d "${patches_path}" ] || git clone "https://${patches_repo}.git" "${patches_repo_dir}"
+[ -d "${patches_path}" ] || die "patches path ${patches_path} not found" # or a warning only.

ahh I see. That makes a lot more sense. I like this flow because if we keep the git clone part we would have to ensure it clones and checkouts the correct branch to be used which is a bigger hassle.


ci: add typechecking for deno

Currently no typechecking is performed on the remix-deno package, because tsc cannot handle .ts file extension imports. This PR adds support for typechecking using the deno check command.
Closes: #

[ ] Docs
[ ] Tests

Testing Strategy:
Run yarn build --deno

@mcansh it also runs if process.env.CI is true, so should run every time

@mcansh it also runs if process.env.CI is true, so should run every time

ope you're right 🤦♂ 👍


Original ROS 2 Cartographer ROS port created from v1.0.0

This PR is a port of cartographer_ros to ROS 2. As you can see from the diff, it is actually quite a substantial change to cartographer_ros to make this work for ROS 2.
This code has been used in a few different robotics projects, so we know that at least the major parts of it work. There are some parts of it that could use a cleanup, as they workaround problems that may or may not still exist.
As-is, this PR doesn't apply to master. That's because this port was originally done against the 1.0.0 tag of this repository. Moving it forward would be possible, but would likely require some work.
I'm opening this PR as a starting point for the discussion on how to move this code into the upstream. As of right now, the ros2-dashing-1.0.0 branch here in https://github.com/cartographer-project/cartographer_ros is branched off of 1.0.0, so this PR applies without conflict.
Comments, questions, thoughts all welcome!

@wohe @bochen87 Since this will be an archived branch (see #1536) I want to preserve the commit history. But I can't do a simple fast-forward merge, only squash is possible. Maybe you have more rights? It would only be needed once for this archive branch.


test: Improve duration_attribute_tests

Add constructor_lazy and ensure it fails as expected.
Combine two separate tests into one.

What type of PR is this? (check all applicable)

[ ] 💾 Refactor
[ ] ✨ Feature
[ ] 🐛 Bug Fix
[ ] 🔧 Optimization
[ ] 📝 Documentation
[x] ✅ Test
[ ] 🐳 Other

Related issues

Related issue #
Closes #

Checklist

[ ] Code follows style guide (ruff)
[ ] Tests added
[ ] Documented the changes

If you have comments or can explain your changes, please do so below.

The combination of two tests is somewhat aggressive; if it's not suitable, I would like to revert them.


⚠ Bofrost.de has degraded performance

In 47e3cde, Bofrost.de (https://www.bofrost.de) experienced degraded performance:

HTTP code: 200
Response time: 1330 ms

Resolved: Bofrost.de performance has improved in bd873d0 after 6 minutes.


Unable to enable extension

Extension is greyed out in gnome-shell-extension-prefs
$ gnome-shell --version
GNOME Shell 3.21.91

Indeed, that version issnot supported yet. Can you update the manifest file
and see if that works ? If not, what problems do you face ?
On Sep 6, 2016 00:02, "Łukasz Wieczorek"<EMAIL_ADDRESS>wrote:

Extension is greyed out in gnome-shell-extension-prefs
$ gnome-shell --version
GNOME Shell 3.21.91
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/deadalnix/pixel-saver/issues/89, or mute the thread
https://github.com/notifications/unsubscribe-auth/AA0IaT3NJYsuSpOS-PQgtEE6MW5qQMJcks5qnQ_7gaJpZM4J1hcz
.

It works fine with 3.21.

Alright, let's update the manifest, then.
On Sep 8, 2016 06:11, "Léo Andrès"<EMAIL_ADDRESS>wrote:

It works fine with 3.21.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/deadalnix/pixel-saver/issues/89#issuecomment-245592225,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AA0IaSZN7DIYxlTJ5rI69RnoEAflz8vxks5qoAmNgaJpZM4J1hcz
.

luke ~/S/pixel-saver $ cat<EMAIL_ADDRESS>{
	"uuid"<EMAIL_ADDRESS>	"name": "Pixel Saver",
	"description": "Pixel Saver is designed to save pixel by fusing activity bar and title bar in a natural way",
	"url": "https://github.com/deadalnix/pixel-saver",
	"shell-version": ["3.16", "3.18", "3.20", "3.21"]
}

Still grayed out.

It does looks like 3.22 is due by the end of the month. I thin the best it to bump to 3.22 once it is released. 3.21 is unstable and therefore, I'm not sure how much effort should be put in it.

3.21 is just the dev name of 3.22 ; so it'll also work on 3.22.
Just add 3.22 to metadata.json as 3.21 is just a temporary release.

The gnome version of current Debian Testing is 3.21.59.
$ gnome-shell --version
GNOME Shell 3.21.91

The method mentioned by @wieczorek1990  is not working. I also test the latest commit 3738e86, same situation. Any  suggestion?

@qyin , you've got to add 3.21.91 and not just 3.21.

@zapashcanon It works! Thank you very much.

Alright, it is updated on extension.gnome.org as well, closing,


Issue while changing state

It shows Exception in hasSize

The screenshot does not have any useful information.
Please show me the actual stacktrace or something in "text" not in screenshot.


boost::beast::buffers_range_ref

Version of Beast BOOST_BEAST_VERSION 313 (boost_1_76_0)
g++ (Ubuntu 9.3.0-17ubuntu1~20.04) 9.3.0
Dears,
first of all I'd like to thank you, really thank all of you for the efforts providing such amazing libraries, they make our life definitely much easier.. :)
I'm using Beast as a websocket client and I'd like to move from "buffers_to_string" to "buffers_range_ref".
At the moment I'm encountering some differences between debug and release compilations using 'boost::beast::buffers_range_ref'.
I've reproduced the issue with the async-ssl websocket sample:
websocket_client_async_ssl.cpp  (boost_1_76_0/libs/beast/example/websocket/client/async-ssl)
I've just modified the 'on_read' method adding what I found here: https://www.boost.org/doc/libs/1_76_0/libs/beast/doc/html/beast/ref/boost__beast__buffers_range_ref.html
	std::cout << "bytes_transferred: " << bytes_transferred << std::endl;
	std::size_t size = 0;
	for (auto const buffer : boost::beast::buffers_range_ref(buffer_.data())) {
		std::cout << "buffer size: " << buffer.size() << std::endl;
		size += buffer.size();
	}
	std::cout << "total size: " << size << std::endl;

*I'm attaching the sample project. (Eclipse CDT)
beast_test.zip
It seems the 'single' buffer size is correct in the debug build, but get some issue in the release one:
DEBUG:
g++ -I/path_to/boost_1_76_0 -O0 -g3 -Wall -c -fmessage-length=0 -MMD -MP -MF"main.d" -MT"main.o" -o "main.o" "../main.cpp"
g++ -pthread -o "beast_test"  ./main.o   -lssl -lcrypto
OUTPUT:
./beast_test echo.websocket.org 443 "Hello, world!"
bytes_transferred: 13
buffer size: 13
total size: 13
RELEASE:
g++ -I/path_to/boost_1_76_0 -O3 -Wall -c -fmessage-length=0 -MMD -MP -MF"main.d"
g++ -pthread -o "beast_test"  ./main.o   -lssl -lcrypto
OUTPUT:
./beast_test echo.websocket.org 443 "Hello, world!"
bytes_transferred: 13
buffer size:<PHONE_NUMBER>4400
total size: 0
*Note:
Using the 'boost::beast::buffers_range' function instead, both versions work as expected.
Thank you for any suggestion for solving my problem.
Kind regards
Emiliano

You're constructing from a temporary:
boost::beast::buffers_range_ref(buffer_.data())

As the name implies, buffers_range_ref stores a reference to the target buffer, which is destroyed after the expression is evaluated - leading to undefined behavior.

Dear Vinnie Falco,
thank you! I've got the point:
"...The application is responsible for ensuring that the lifetime of the referenced buffers extends until the range object is destroyed."
	auto _buffers = buffer_.data();
	for (auto const buffer : boost::beast::buffers_range_ref(_buffers)) { ..

Works perfectly.


omni_send with null referenceamount

Hi
I try to send USDT with a null referenceamount. I created a previous raw transaction: https://www.blockchain.com/btc/tx/a10111305ebe011ecc984c1c07ef60e725f7a96f11c1d59001acebd2abd2d2a7?show_adv=false
Some BTC have been sent to 1JJGCfAPmmV79yJMbCbnXWWntZgjHBZtzn which is something I dont't want.
When I try to create a transaction without any referenceamount, I've got this error:
./omnicore-cli  "omni_send" "12eXXt156hevSx14c7pgryQcGLiPBFcPMj" "1JJGCfAPmmV79yJMbCbnXWWntZ
gjHBZtzn" 31 "1" "12eXXt156hevSx14c7pgryQcGLiPBFcPMj" "0.0"
error code: -3
error message:
Invalid amount

Is there always the dust? No way to bypass it?

@dannywillems  That is correct.
Bitcoin transactions do not allow a 0 value for an address output and since the Omni protocol is built on / uses the bitcoin blockchain it is the same constraint.
There always has to be some amount of BTC for each address in the output list

Thanks @achamely


cleanup debug log messages

there are currently some really weird messages in the console, see:

"shit to log"
"Es kam ein neuer change rein für ..."
"save zum saven übergeben wurde"
"Current error ist nun:"

in general it seems like the ACI is requested a lot of times from the compiler. is it really required to call the http compiler that often? I don't think so

Agree, formatted the log messages a little. The compiler isn't called that often though, it's just multiple event-based subscriptions firing on every call.


For Reactjs comprehension

Nice work

Give it a try and you'll not regret doing it

Thanks for supporting React! But it is not a issue in zh-hans repo, I'll close it.


Hmcgowan/selenium3

Hey Hugh:
It appears I'm still on one of the Spredfast/Lithium notification lists. No
big deal, but I suspect I should not be.
Cheers -- and thanks,
--ag
On Mon, Mar 4, 2019 at 2:00 PM Hugh McGowan<EMAIL_ADDRESS>wrote:

You can view, comment on, or merge this pull request online at:
https://github.com/lithiumtech/mineraloil-selenium/pull/78
Commit Summary

update selenium to v3.x
ramp down polling interval
simplify screenshots

File Changes

M pom.xml
https://github.com/lithiumtech/mineraloil-selenium/pull/78/files#diff-0
(12)
M
src/main/java/com/lithium/mineraloil/selenium/browsers/ChromeBrowser.java
https://github.com/lithiumtech/mineraloil-selenium/pull/78/files#diff-1
(57)
D
src/main/java/com/lithium/mineraloil/selenium/browsers/FirefoxBrowser.java
https://github.com/lithiumtech/mineraloil-selenium/pull/78/files#diff-2
(38)
M
src/main/java/com/lithium/mineraloil/selenium/browsers/RemoteBrowser.java
https://github.com/lithiumtech/mineraloil-selenium/pull/78/files#diff-3
(2)
M
src/main/java/com/lithium/mineraloil/selenium/browsers/RemoteChromeBrowser.java
https://github.com/lithiumtech/mineraloil-selenium/pull/78/files#diff-4
(18)
D
src/main/java/com/lithium/mineraloil/selenium/browsers/RemoteFirefoxBrowser.java
https://github.com/lithiumtech/mineraloil-selenium/pull/78/files#diff-5
(57)
M
src/main/java/com/lithium/mineraloil/selenium/elements/Driver.java
https://github.com/lithiumtech/mineraloil-selenium/pull/78/files#diff-6
(4)
M
src/main/java/com/lithium/mineraloil/selenium/elements/DriverConfiguration.java
https://github.com/lithiumtech/mineraloil-selenium/pull/78/files#diff-7
(4)
M
src/main/java/com/lithium/mineraloil/selenium/elements/DriverInstance.java
https://github.com/lithiumtech/mineraloil-selenium/pull/78/files#diff-8
(8)
M
src/main/java/com/lithium/mineraloil/selenium/elements/Screenshot.java
https://github.com/lithiumtech/mineraloil-selenium/pull/78/files#diff-9
(191)
M
src/main/java/com/lithium/mineraloil/selenium/elements/WebdriverActions.java
https://github.com/lithiumtech/mineraloil-selenium/pull/78/files#diff-10
(4)
A
src/main/java/com/lithium/mineraloil/selenium/exceptions/ScreenshotException.java
https://github.com/lithiumtech/mineraloil-selenium/pull/78/files#diff-11
(9)
M
src/test/java/com/lithium/mineraloil/selenium/helpers/BaseTest.java
https://github.com/lithiumtech/mineraloil-selenium/pull/78/files#diff-12
(2)
M
src/test/java/com/lithium/mineraloil/selenium/helpers/ChromeSettings.java
https://github.com/lithiumtech/mineraloil-selenium/pull/78/files#diff-13
(15)

Patch Links:

https://github.com/lithiumtech/mineraloil-selenium/pull/78.patch
https://github.com/lithiumtech/mineraloil-selenium/pull/78.diff

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/lithiumtech/mineraloil-selenium/pull/78, or mute the
thread
https://github.com/notifications/unsubscribe-auth/AA34nO6BqvGtK1BWGFQrlWFe2BN1iocJks5vTXtMgaJpZM4bdGN2
.

--
Artie Gold, Austin, Texas
http://makeitsimpler.org

Hi Artie, this code is open source so it probably didn't get caught by
whatever scripts IT was running. I'd look to see if you're following it:
https://github.com/watching
Thanks!
Hugh
On Mon, Mar 4, 2019 at 2:02 PM Artie Gold<EMAIL_ADDRESS>wrote:

Hey Hugh:
It appears I'm still on one of the Spredfast/Lithium notification lists. No
big deal, but I suspect I should not be.
Cheers -- and thanks,
--ag
On Mon, Mar 4, 2019 at 2:00 PM Hugh McGowan<EMAIL_ADDRESS>wrote:

You can view, comment on, or merge this pull request online at:
https://github.com/lithiumtech/mineraloil-selenium/pull/78
Commit Summary

update selenium to v3.x
ramp down polling interval
simplify screenshots

File Changes

M pom.xml
<https://github.com/lithiumtech/mineraloil-selenium/pull/78/files#diff-0

(12)

M
src/main/java/com/lithium/mineraloil/selenium/browsers/ChromeBrowser.java
<https://github.com/lithiumtech/mineraloil-selenium/pull/78/files#diff-1

(57)

D

src/main/java/com/lithium/mineraloil/selenium/browsers/FirefoxBrowser.java

<https://github.com/lithiumtech/mineraloil-selenium/pull/78/files#diff-2
(38)

M
src/main/java/com/lithium/mineraloil/selenium/browsers/RemoteBrowser.java
<https://github.com/lithiumtech/mineraloil-selenium/pull/78/files#diff-3

(2)

M

src/main/java/com/lithium/mineraloil/selenium/browsers/RemoteChromeBrowser.java

<https://github.com/lithiumtech/mineraloil-selenium/pull/78/files#diff-4
(18)

D

src/main/java/com/lithium/mineraloil/selenium/browsers/RemoteFirefoxBrowser.java

<https://github.com/lithiumtech/mineraloil-selenium/pull/78/files#diff-5
(57)

M
src/main/java/com/lithium/mineraloil/selenium/elements/Driver.java
<https://github.com/lithiumtech/mineraloil-selenium/pull/78/files#diff-6

(4)

M

src/main/java/com/lithium/mineraloil/selenium/elements/DriverConfiguration.java

<https://github.com/lithiumtech/mineraloil-selenium/pull/78/files#diff-7
(4)

M

src/main/java/com/lithium/mineraloil/selenium/elements/DriverInstance.java

<https://github.com/lithiumtech/mineraloil-selenium/pull/78/files#diff-8
(8)

M
src/main/java/com/lithium/mineraloil/selenium/elements/Screenshot.java
<https://github.com/lithiumtech/mineraloil-selenium/pull/78/files#diff-9

(191)

M

src/main/java/com/lithium/mineraloil/selenium/elements/WebdriverActions.java

<
https://github.com/lithiumtech/mineraloil-selenium/pull/78/files#diff-10>
(4)

A

src/main/java/com/lithium/mineraloil/selenium/exceptions/ScreenshotException.java

<
https://github.com/lithiumtech/mineraloil-selenium/pull/78/files#diff-11>
(9)

M
src/test/java/com/lithium/mineraloil/selenium/helpers/BaseTest.java
<
https://github.com/lithiumtech/mineraloil-selenium/pull/78/files#diff-12>
(2)
M
src/test/java/com/lithium/mineraloil/selenium/helpers/ChromeSettings.java
<
https://github.com/lithiumtech/mineraloil-selenium/pull/78/files#diff-13>
(15)

Patch Links:

https://github.com/lithiumtech/mineraloil-selenium/pull/78.patch
https://github.com/lithiumtech/mineraloil-selenium/pull/78.diff

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/lithiumtech/mineraloil-selenium/pull/78, or mute
the
thread
<
https://github.com/notifications/unsubscribe-auth/AA34nO6BqvGtK1BWGFQrlWFe2BN1iocJks5vTXtMgaJpZM4bdGN2
.

--
Artie Gold, Austin, Texas
http://makeitsimpler.org
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/lithiumtech/mineraloil-selenium/pull/78#issuecomment-469400935,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AACZvcrswrnAis_UIjeBrAZYEyuzstfmks5vTXvGgaJpZM4bdGN2
.


Need to check the status of RH before sshing into it

Instead of using c sockets, need to use qt libraries to check the status of resource host.
https://github.com/subutai-io/tray/issues/537

Fixed in Master.

Fixed in Prod.


Switch to auto formatted code

Hi,
Can I suggest we use VSCode to auto format the codes? There are many benefits to this, namely:

Easier for anyone to file clean PRs
Higher readability, less work

I'm happy to file a PR.

VSCode? Did you mean ESLint / Prettier / PHPStan / PHPCS?

@nelson6e65 My bad, I looked. I'm using esbenp.prettier-vscode. I guess we should just pick one and make it known so that it is easier to make small changes in PRs.
@ondras what do you think?

I am not sure this is going to solve a problem I am having. To address your arguments:

Easier for anyone to file clean PRs

In what sense? I do not recall dismissing a PR due to it being "unclean".

2. Higher readability, less work

There is no work being mandated with respect to formatting. Obviously becoming consistent with the "code style status quo" is useful.
I am okay with a PR that somewhat normalizes whitespace (as long as it does not introduce style changes incompatible with my own coding style). But I do not plan on applying that manually and/or automatically to my further code base adjustments.

@ondras
Ok, when I used the word clean, what I meant was small or much smaller
See here https://github.com/ondras/wwwsqldesigner/pull/254, this was indicated as too big, I had a quick look and also felt it was beyond what I can afford, largely due to it being hard to read.
Reading to understand by itself is work :)
And the latest commit was only removing 5 lines, but there was another extra 16 additions and deletions (probably due to some auto formating of tabs to spaces etc)
https://github.com/ondras/wwwsqldesigner/commit/4c2b6f5d537abda62a9d1cc80a08576579e5188d
It's just a suggestion, but would require core collaborators to stick to using the auto formatter, otherwise it would not bring any benefits. Thank you.

See here #254, this was indicated as too big, I had a quick look and also felt it was beyond what I can afford, largely due to it being hard to read.

Right, but the related functionality has been implemented and merged separately. Also, in https://github.com/ondras/wwwsqldesigner/pull/254#issuecomment-325629982, I mentioned that I would welcome a separate white-space normalizing commit. This still holds.

And the latest commit was only removing 5 lines, but there was another extra 16 additions and deletions (probably due to some auto formating of tabs to spaces etc)

Yep. Is this is problem?

Ok, let me file a PR using the auto formatter esbenp.prettier-vscode, we see if it is suitable. Basically, whitespace additions and deletions require additional effort to parse (read and understand) and ignore, yet it is something that can be eliminated.
Thanks!

Ok, I have done it, removes all white-spaces + auto format, the tools used are also listed.
All I basically did was open, save, close and commit all changes.

Sorry for not replying earlier. I just accepted the PR. Thanks!

No worries, thanks! Now I can based my other PRs off this :)


[full-ci] update reva to v2.6.1-...

update reva to  v2.6.1-...

:boom: Acceptance test Core-API-Tests-ocis-storage-1 failed. Further test are cancelled...

I added full-ci to the title. If you push again, drone will take notice.

https://drone.owncloud.com/owncloud/ocis/12787/38/6
Scenario: A user cannot create a folder in a Space if they do not have permission                                     # /drone/src/tests/acceptance/features/apiSpaces/uploadSpaces.feature:33
    Given user "Alice" has created a space "Project Merkur" of type "project" with quota "2000"                         # SpacesContext::userHasCreatedSpace()
    And user "Bob" creates a folder "forAlice" in space "Project Merkur" owned by the user "Alice" using the WebDav Api # SpacesContext::theUserCreatesAFolderToAnotherOwnerSpaceUsingTheGraphApi()
    Then the HTTP status code should be "404"                                                                           # FeatureContext::thenTheHTTPStatusCodeShouldBe()
      HTTP status code 403 is not the expected value 404
      Failed asserting that 403 matches expected '404'.

  Scenario: A user cannot upload a file in a Space if they do not have permission                                                                # /drone/src/tests/acceptance/features/apiSpaces/uploadSpaces.feature:52
    Given user "Alice" has created a space "Project Pluto" of type "project" with quota "2000"                                                   # SpacesContext::userHasCreatedSpace()
    When user "Bob" uploads a file inside space "Project Pluto" owned by the user "Alice" with content "Test" to "test.txt" using the WebDAV API # SpacesContext::theUserUploadsAFileToAnotherOwnerSpace()
    Then the HTTP status code should be "404"                                                                                # FeatureContext::thenTheHTTPStatusCodeShouldBe()
      HTTP status code 403 is not the expected value 404
      Failed asserting that 403 matches expected '404'.

It looks like those scenarios should now be edited to change the expectation of 404 to 403

hmmm ocis apiSpaces/uploadSpaces.feature:52
  Scenario: A user cannot upload a file in a Space if they do not have permission                                                                # /drone/src/tests/acceptance/features/apiSpaces/uploadSpaces.feature:52
    Given user "Alice" has created a space "Project Pluto" of type "project" with quota "2000"                                                   # SpacesContext::userHasCreatedSpace()
    When user "Bob" uploads a file inside space "Project Pluto" owned by the user "Alice" with content "Test" to "test.txt" using the WebDAV API # SpacesContext::theUserUploadsAFileToAnotherOwnerSpace()
    Then the HTTP status code should be "404"                                                                                # FeatureContext::thenTheHTTPStatusCodeShouldBe()
      HTTP status code 403 is not the expected value 404
      Failed asserting that 403 matches expected '404'.
    And for user "Alice" the space "Project Pluto" should not contain these entries:                                                             # SpacesContext::userTheSpaceShouldContainEntries()
      | test.txt |

seems to contradict reva apiAuthWebDav/webDavPUTAuth.feature:70
2315 | Scenario: send PUT requests to another user's webDav endpoints as normal user using the spaces WebDAV API # /drone/src/tmp/testrunner/tests/acceptance/features/apiAuthWebDav/webDavPUTAuth.feature:70 | 203s
2316 | When user "Brian" requests these endpoints with "PUT" including body "doesnotmatter" about user "Alice" # OCSContext::userSendsRequestToTheseEndpointsWithBody() | 204s
2317 | \| endpoint                                       \| | 204s
2318 | \| /remote.php/dav/spaces/%spaceid%/textfile0.txt \| | 204s
2319 | \| /remote.php/dav/spaces/%spaceid%/PARENT        \| | 204s
2320 | Then the HTTP status code of responses on all endpoints should be "403"                                 # FeatureContext::theHTTPStatusCodeOfResponsesOnAllEndpointsShouldBe() | 204s
2321 | Responses did not return expected http status code | 204s
2322 | Failed asserting that 404 is identical to 403. | 204s
2323 | When user "Brian" requests these endpoints with "PUT" including body "doesnotmatter" about user "Alice" # OCSContext::userSendsRequestToTheseEndpointsWithBody() | 204s
2324 | \| endpoint                                           \| | 204s
2325 | \| /remote.php/dav/spaces/%spaceid%/PARENT/parent.txt \| | 204s
2326 | Then the HTTP status code of responses on all endpoints should be "403"

In both cases Brian is PUTing a file into the space of another user. In the first example a project space, in the second example a personal space.
Taking a step back, we are trying to prevent leaking the existence of a space / file by returning 404 instead of 403. But to access a file you need to know the space id in advance ... hm, which for users is guessable because the userid is not secret and currently equals the personal space id.
IMO we should always return 404 if the user has no access to a space, which would make the reva apiAuthWebDav/webDavPUTAuth.feature:70 test the wrong status code.

currently points to my branch, needs merge in reva

  Scenario: A user with role viewer cannot create a folder in shared Space via the Graph API                  # /drone/src/tests/acceptance/features/apiSpaces/uploadSpaces.feature:95
    Given user "Alice" has created a space "Viewer cannot create folder" of type "project" with quota "2000"  # SpacesContext::userHasCreatedSpace()
    And user "Alice" has shared a space "Viewer cannot create folder" to user "Bob" with role "viewer"        # SpacesContext::userHasSharedSpace()
    When user "Bob" creates a folder "mainFolder" in space "Viewer cannot create folder" using the WebDav Api # SpacesContext::theUserCreatesAFolderUsingTheGraphApi()
    Then the HTTP status code should be "403"                                                                 # FeatureContext::thenTheHTTPStatusCodeShouldBe()
      HTTP status code 404 is not the expected value 403
      Failed asserting that 404 matches expected '403'.
    And for user "Bob" the space "Viewer cannot create folder" should not contain these entries:              # SpacesContext::userTheSpaceShouldContainEntries()
      | mainFolder |
    And for user "Alice" the space "Viewer cannot create folder" should not contain these entries:            # SpacesContext::userTheSpaceShouldContainEntries()
      | mainFolder |

seems to contradict reva apiAuthWebDav/webDavPUTAuth.feature:70

https://github.com/owncloud/core/pull/39718/files#diff-6f66858efef616c8d86267ddb370262dabe13b0e8a63f175b734777f5db66945
Those scenarios were added with the same "403" expectation as for the /remote.php/dav/files/%username% endpoint. In oC10 it gives 403 "forbidden". And I think that is a problem/feature in oC10 also. I get a different HTTP 4xx status if I try to access another real user, or if I try to access a non-existent user.
The requirements need to be thought about and defined - probably a consistent 404 for all these combinations of trying to access something that may or may not "really" exist, but it does not exist from the point-of-view of the authenticated user. Then make the test scenarios expect the proper requirements. Then make both oC10 and oCIS meet the requirements. Part of the problem here is that we have oC10 core tests that demonstrate current oC10 behavior, but actually the current behavior is not correct/optimal.

@phil-davis I agree. Regardless of the error, it you don't have read access to the storage all you get should be a 404.
Currently, only some error paths of the ocdav service do a stat request to determine if a user can read file.
This actually differs from oc10 where you get a 403.
The initial spaces implementation required a space lookup, when you didn't have access you would always get a 404. For performance reasons we moved the space lookup from the storage registry to the storage provider.
That ocdav does a stat after an error is technical debt. The storage providers would need to return 404 when the user has no access to the root. That could be done in the storage provider and is not necessary required to be done by the storage drivers.

In any case this pr can now point to Reva edge, as both cis are green and the Reva pr has been merged.

In any case this pr can now point to Reva edge, as both cis are green and the Reva pr has been merged.

Agree - are you going to update this PR?
And after you do, and CI goes green, IMO it can be merged.


Can not reproduce results on VOC dataset after base training.

Hi, thanks for your work.
I tried to reproduce the results on VOC2007 test dataset, but got confused.
First, I tried to finetune the model provided, which is base trained. I got similar results as reported.
Second, I tried to train from base stage to fine tune stage and I got much worse results, mAP nearly 0. I tried 3 times parallel training, none of the attempt worked well. (first split) All steps were following the README file.
Can you help explain this problem? Thanks.

@Jaraxxus-Me Can you tell me set?how you built this VOC data ？I am also very surprised that this question arises.

Hi, thanks so much for your response.
About VOC dataset, I downloaded from this mirror web since the official one seems to be down. Then just follow your instruction in the README file.
I've carefully inspected this problem today. I tried to continue train both your provided model and my self-trained model in the first stage (see attached figures). The loss of your model seems to be much lower (0.3) than mine (1.5), and my meta loss seems to remain 0.1806.
Then I re-implemented my experiment again from the beginning. Found that the loss seems to remain around 1.5 since the forth epoch. Even more wired is that, the meta loss in all 3 splits seem to remain 0.1806 after several epochs (higher than yours).
I'm still stuck on this problem.
Can you offer me some advice maybe?
Thanks.

Besides, I randomly got this situation, which continues to confuse me. I have to try several times before getting

it normal. I didn't modify your code. After building up the dataset, I simply ran the .sh files.

Hi, thanks so much for your response.
About VOC dataset, I downloaded from this mirror web since the official one seems to be down. Then just follow your instruction in the README file.
I've carefully inspected this problem today. I tried to continue train both your provided model and my self-trained model in the first stage (see attached figures). The loss of your model seems to be much lower (0.3) than mine (1.5), and my meta loss seems to remain 0.1806.
Then I re-implemented my experiment again from the beginning. Found that the loss seems to remain around 1.5 since the forth epoch. Even more wired is that, the meta loss in all 3 splits seem to remain 0.1806 after several epochs (higher than yours).
I'm still stuck on this problem.
Can you offer me some advice maybe?
Thanks.

Hi，have you solved the problem? I have the same problems as you.

Hi, thanks so much for your response.
About VOC dataset, I downloaded from this mirror web since the official one seems to be down. Then just follow your instruction in the README file.
I've carefully inspected this problem today. I tried to continue train both your provided model and my self-trained model in the first stage (see attached figures). The loss of your model seems to be much lower (0.3) than mine (1.5), and my meta loss seems to remain 0.1806.
Then I re-implemented my experiment again from the beginning. Found that the loss seems to remain around 1.5 since the forth epoch. Even more wired is that, the meta loss in all 3 splits seem to remain 0.1806 after several epochs (higher than yours).
I'm still stuck on this problem.
Can you offer me some advice maybe?
Thanks.

Hi，have you solved the problem? I have the same problems as you.

Unfortunately not, I still don't know why and have to find another code base for my project..


multi language support system added.

the system is working, @Vimall03 can you please review this .
#123 solved.
https://github.com/user-attachments/assets/af1ea0b8-149d-40f9-a32d-cd90a15ff9e2
Type of Change

[ ] Bug fix
[X] New feature
[ ] Documentation update
[ ] Refactoring
[ ] Other (please describe):

Closes: #123 solved
Testing

Checklist

[X] I have tested my changes and ensured they work as expected.
[X] I have added necessary documentation (if applicable).
[X] I have reviewed my code for style and linting issues.
[X] I have ensured that any dependent changes are merged before this PR.

Additional Notes

@Vimall03 can you assign the level aswell , thank you.

@T-Rahul-prabhu-38  I was reviewing the code, How many languages does this support ?


Deleted forced Accept header

I think we can set this header by configuration file.
In our case our web service have error when json exporter send Accept header.

We probably want to default to having this header, but a flag to not force it would be OK.

@SuperQ Hello! I added a parameter to the config file, added a test for this parameter. Check, please.

Closing as stale.


Enhancement: Dialogues

Please check for duplicates or similar issues before creating this issue.
What is your suggestion, and why should it be implemented?
--- i would really like for dialogues, along with an editor for dialogues to be implemented. this is easier than using cutscenes as dialogues.

there's already a way to do this but it's really complicated to make it work

this is being added in the 2.0 update

I GET IT!!!


Initial configuration for Jamaica

[x] Map location
[x] Intro text
[x] Drop OIA logo
[x] Drop later sections

Closed as of 565d9a6f21


Issue #328 plugin version

Fixed pom warning for https://github.com/GoogleCloudPlatform/appengine-java-vm-runtime/issues/328

LGTM.
Going forward, can you create branches for pull requests directly in this repo?

@meltsufin I don't appear to have permission to do the merge on this repo?   I do have it on openjdk-runtime and jetty-gae-compat-runtime.   So can you merge or give me permission.

@gregw Try now. I had the wrong setting on for protecting the master branch.


Tracking Issue: Store Façade

We need an interface in front of the data store and blueprint store that handles:

ergonomic read/write of common types
blueprint overrides/fallbacks for entity components values
component transforms (jpeg -> tensor)
Rework re_query to be object centered (store.query(…) instead of re_query::query(store, …))

Let's start with the first two points

HybridResults is pretty much doing this now. It also takes into account blueprint store.
We don't have an immediate need for a Facade on the store itself anymore. Closing this as outdated.


Updated the landing page with bootstrap

fixes #39
Description: Updated the societies page  with bootstrap
Checklist

[x] I've followed the Contributing guidelines provided in the repository.
[x] I've made the changes which were demanded in the linked issue.
[ ] I've tested my code on a Chromium based browser.
[x] I've tested my code on Mozilla Firefox.
[x] My code gave a clean console on debugging. (no warnings/errors)

Testimonial

Change the base branch from houseofgeeks:master to houseofgeeks:front-end to see live build preview.
If you've worked on the front-end part make PR (Pull Request) to the front-end branch

I think this pull is not required anymore in ref to #48


pm: Do not select deprecated symbol

PM_DEVICE_RUNTIME_EXCLUSIVE was deprecated and its behavior is achived with PM_DEVICE_SYSTEM_MANAGED=n.
Fixes #76037

Thanks @JordanYates and @kartben for reporting and confirm it

@ceolin could please git -C zephyr/ grep RUNTIME_EXCLUSIVE and remove? As in "lead by example" :-)
git grep RUNTIME_EXCLUSIVE
samples/boards/stm32/power_mgmt/stop3/prj.conf:CONFIG_PM_DEVICE_RUNTIME_EXCLUSIVE=n
tests/lib/cpp/cxx/prj.conf:CONFIG_PM_DEVICE_RUNTIME_EXCLUSIVE=n

@marc-hb I saw these entries but tried to limit this change because we are in rc3. Since those occurrences are  not selecting this symbol I thought they should be addressed later.


How to set the notification time

Use timeout.
Check this file: https://github.com/alihesari/notice.js/blob/master/src/js/api.js


InlayHints work only with only_current_line = false

The inlay hints are working for me only when
only_current_line = false

If this option is set to true, they do no show up when I am on a line where the inlay hint should be there.
This was working fine until recently, but I am not sure when it stopped working for me.
I am not sure how to debug this to ensure it is not something else clashing with rust-tools!
Any help would be much appreciated.

Looks like rust-analyzer recently changed the spec which might have broken only_current_line, will have a look. Thanks for the report!

I'm seeing this behavior too, worth noting that the :RustToggleInlayHints (as well as Set and Disable) have also stopped working, probably due to the same spec change.

OK, so I am rewriting the inlay hints code (and a bit more of the plugin), I would really appreciate if you could test the https://github.com/simrat39/rust-tools.nvim/tree/modularize_and_inlay_rewrite branch and see if it fixes your issue

I have just tested it and works perfectly with my setup.

I have similar issues with inlay hints. Should I switch to the branch @simrat39? I see it is missing a couple of commits and the last commits on main where related to the LSP functionality so I am not sure if I should 🤔

Thanks for testing! I'll be merging it soon once we get some more testers

I just would like to report that the InlayHints are working beautifully in this modularize_and_inlay_rewrite branch with my setup. Contrary to the OP, the only_current_line option is working as intended. On the other hand, show_variable_name is not.

InlayHints indeed are working on this branch, however I've encountered an error when using RustHoverActions:
Error executing vim.schedule lua callback: vim/shared.lua:0: after the second argument: expected table, got nil
stack traceback:
        [C]: in function 'error'
        vim/shared.lua: in function 'validate'
        vim/shared.lua: in function 'tbl_extend'
        ...r/start/rust-tools.nvim/lua/rust-tools/hover_actions.lua:90: in function 'fn'
        ...ker/start/rust-tools.nvim/lua/rust-tools/utils/utils.lua:101: in function 'handler'
        /usr/share/nvim/runtime/lua/vim/lsp.lua:1025: in function ''
        vim/_editor.lua: in function <vim/_editor.lua:0>

Can confirm that I have the same issue as @Zwo1in

Me too!!
It doesn't happen in master.

@Zwo1in @dathinaios @fdelacruz Should be fixed now!

Thanks! I did a quick test and it indeed seems to be working fine now 🙂

Hi, I sadly still have the same issue on the latest versions of rust-tools and rust-analyzer (2022-05-17 stable)
Is there something wrong with my config?
autoSetHints = true,
hover_with_actions = true,
runnables = {
    use_telescope = true
},
inlay_hints = {
    show_parameter_hints = false,
    other_hints_prefix = "<< ",
    only_current_line = true,
    only_current_line_autocmd = "CursorMoved,CursorMovedI"
}

Hi, I sadly still have the same issue on the latest versions of rust-tools and rust-analyzer (2022-05-17 stable)

Are you on the modularize_and_inlay_rewrite cause I don't think this has been merged to master yet.

Hi, any progress on merging this?

Hi,
I tried below in LunarVim "config.lua" but inlay hints still didn't work for me (I tried with or without "config" block but same results):
`  {
"simrat39/rust-tools.nvim",
branch = "modularize_and_inlay_rewrite",
config = function()
local lsp_installer_servers = require "nvim-lsp-installer.servers"
local _, requested_server = lsp_installer_servers.get_server "rust_analyzer"
require("rust-tools").setup({
tools = {
autoSetHints = true,
hover_with_actions = true,
inlay_hints = {
        -- Only show inlay hints for the current line
        only_current_line = false,

        -- Event which triggers a refersh of the inlay hints.
        -- You can make this "CursorMoved" or "CursorMoved,CursorMovedI" but
        -- not that this may cause higher CPU usage.
        -- This option is only respected when only_current_line and
        -- autoSetHints both are true.
        only_current_line_autocmd = "CursorHold",

        -- whether to show parameter hints with the inlay hints or not
        -- default: true
        show_parameter_hints = true,

        -- whether to show variable name before type hints with the inlay hints or not
        -- default: false
        show_variable_name = false,

        -- prefix for parameter hints
        -- default: "<-"
        parameter_hints_prefix = "<- ",

        -- prefix for all the other hints (type, chaining)
        -- default: "=>"
        other_hints_prefix = "=> ",

        -- whether to align to the lenght of the longest line in the file
        max_len_align = false,

        -- padding from the left if max_len_align is true
        max_len_align_padding = 1,

        -- whether to align to the extreme right or not
        right_align = false,

        -- padding from the right if right_align is true
        right_align_padding = 7,

        -- The color of the hints
        highlight = "Comment",
      },
      runnables = {
        use_telescope = true,
      },
    },
    server = {
      cmd_env = requested_server._default_options.cmd_env,
      on_attach = require("lvim.lsp").common_on_attach,
      on_init = require("lvim.lsp").common_on_init,
    },
  })
end,
ft = { "rust", "rs" },

},
`
any pointers?
Thanks


Feature/issue 115

Description
Remove check for attendance group for authman sync call.
Fixes #115

Done in version 4.0.55.


make EKS create, delete, update flow fully resilient

Q
A

Bug fix?
yes

New feature?
no

API breaks?
no

Deprecations?
no

License
Apache 2.0

What's in this PR?

move create, delete, update EKS cluster code from cluster.EKSCluster to separate creator, deleter, updater
the whole create update delete flow, including cluster setup, db persist, happens now in workflow
move k8s config download code to workflow activity
delete unused code from EKSCluster
EKSCluster can be completely removed from cluster package once we can delete UpdateNodepools API endpoint

Checklist

[x] Implementation tested (with at least one cloud provider)
[x] Error handling code meets the guideline
[x] Logging code meets the guideline (TODO)

LGTM


First-class function type

Closes #3405
This PR (as a continuation of PR #4967) implements:

[x] Major revision on how Dispatcher and FunctionType instances interact.
[x] Full support for jit-decorated functions as first-class type functions

The jit-decorated functions are considered first-class type functions when using firstclass=True option. For<EMAIL_ADDRESS>def a(x):  # `a` is first-class type function, that is,
           # it can be used as an object in other jit-decorated functions
    return x + 1

@numba.jit()
def foo(f, x):
    return f(x)

assert foo(a, 3) == 4

@stuartarchibald to reproduce the issue of constant functions:

uncomment the line in https://github.com/Quansight/numba/blob/6e190ed13987c2c33d065eebc807879e3307a9a0/numba/core/types/function.py#L116
run the test_constant_functions test, for instance:pytest -sv numba/tests/test_function_type.py -k test_constant_functions

that should print out the LLVM IR and fail with AssertionError: 246 != 579

It needs to handle njit functions that are generators, or reject gracefully:
from numba import njit

@njit(firstclass=True)
def gen(xs):
    for x in xs:
        x += 1
        yield x

@njit
def con(gen_fn, xs):
    return  [it for it in gen_fn(xs)]

con(gen, (1, 2, 3))

currently, it fails with:
numba/core/pythonapi.py in serialize_object(self, obj)
   1327         try:
-> 1328             gv = self.module.__serialized[obj]
   1329         except KeyError:

KeyError: (UniTuple(int64 x 3),) -> int64 generator(func=<function gen at 0x116defb90>, args=(UniTuple(int64 x 3),), has_finalizer=True)

In nopython mode, generators cannot be used as first-class function types because of the corresponding cfunc wrapper functions cannot hold the state of generators. So, raising UnsupportedError when njit(firstclass=True)-decorating generators.
In python mode, however, generators can be used as first-class functions.

To eliminate the need for firstclass=True, the notes in https://github.com/xnd-project/rbc/wiki/How-numba-resolves-function-calls%3F#numba-jit-decorated-functions-as-first-class-functions must be addressed.
Also, the implementation of FunctionType for jit-decorated functions needs to be made immutable: currently, the hash value depends on the last specialization of jit-decorated function.

This PR is ready for review. Here are notable changes:

Revised the interaction between FunctionType and Dispatcher instances. Introduced UndefinedFunctionType that is an imprecise Numba type during type-inference and that is transformed to be precise FunctionType during lowering.
Enabled all tests for Numba jit-decorated functions, cfunc-decorated functions, and WAP instances.
Removed the need for firstclass= jit decorator option.
Generating cfunc wrapper functions is enabled by default for all Numba jit-decorated functions except for generator functions, and functions that take Omitted arguments or return Optional values.
Simplified and cleaned up the code. Improved error handling from using first-class functions.

@sklam @stuartarchibald, please review.

1 test is failing: numba.tests.test_cfunc.TestCFunc.test_errors azure log.
The test might have aborted the process.

Fail details:

  File "/home/vsts/miniconda3/envs/travisci/lib/python3.7/runpy.py", line 193, in _run_module_as_main
    "__main__", mod_spec)
  File "/home/vsts/miniconda3/envs/travisci/lib/python3.7/runpy.py", line 85, in _run_code
    exec(code, run_globals)
  File "/home/vsts/work/1/s/numba/runtests.py", line 9, in <module>
    sys.exit(0 if _main(sys.argv) else 1)
  File "/home/vsts/work/1/s/numba/testing/_runtests.py", line 26, in _main
    **kwds).wasSuccessful()
  File "/home/vsts/work/1/s/numba/testing/__init__.py", line 73, in run_tests
    nomultiproc=nomultiproc)
  File "/home/vsts/work/1/s/numba/testing/main.py", line 160, in __init__
    super(NumbaTestProgram, self).__init__(*args, **kwargs)
  File "/home/vsts/miniconda3/envs/travisci/lib/python3.7/unittest/main.py", line 101, in __init__
    self.runTests()
  File "/home/vsts/work/1/s/numba/testing/main.py", line 321, in runTests
    run_tests_real()
  File "/home/vsts/work/1/s/numba/testing/main.py", line 306, in run_tests_real
    super(NumbaTestProgram, self).runTests()
  File "/home/vsts/miniconda3/envs/travisci/lib/python3.7/unittest/main.py", line 271, in runTests
    self.result = testRunner.run(self.test)
  File "/home/vsts/work/1/s/numba/testing/main.py", line 734, in run
    return super(ParallelTestRunner, self).run(self._run_inner)
  File "/home/vsts/miniconda3/envs/travisci/lib/python3.7/unittest/runner.py", line 176, in run
    test(result)
  File "/home/vsts/work/1/s/numba/testing/main.py", line 682, in _run_inner
    self._run_parallel_tests(result, pool, child_runner, tests)
  File "/home/vsts/work/1/s/numba/testing/main.py", line 718, in _run_parallel_tests
    raise e
  File "/home/vsts/work/1/s/numba/testing/main.py", line 709, in _run_parallel_tests
    child_result = it.__next__(self.timeout)
  File "/home/vsts/miniconda3/envs/travisci/lib/python3.7/multiprocessing/pool.py", line 743, in next
    raise TimeoutError from None
multiprocessing.context.TimeoutError: Tests didn't finish before timeout (or crashed):
- 'numba.tests.test_cfunc.TestCFunc.test_errors'

/AzurePipelines run

Rerunning just in case it's a Frosty Thompson or similar.

Failure is consistent.

The following is failing at lowering. It needs a more graceful error:
from numba import njit

@njit
def f1(x):
    return x

@njit
def f2(x):
    return x

@njit
def foo(disp1, disp2, sel):
    if sel == 1:
        fn = disp1
    else:
        fn = disp2

    return fn([1]), fn(1)

print(foo(f1, f2, sel=1))

Traceback (most recent call last):
  File "/Users/siu/dev/numba-git/numba/core/errors.py", line 720, in new_error_context
    yield
  File "/Users/siu/dev/numba-git/numba/core/lowering.py", line 266, in lower_block
    self.lower_inst(inst)
  File "/Users/siu/dev/numba-git/numba/core/lowering.py", line 347, in lower_inst
    val = self.lower_assign(ty, inst)
  File "/Users/siu/dev/numba-git/numba/core/lowering.py", line 521, in lower_assign
    return self.lower_expr(ty, value)
  File "/Users/siu/dev/numba-git/numba/core/lowering.py", line 1041, in lower_expr
    res = self.lower_call(resty, expr)
  File "/Users/siu/dev/numba-git/numba/core/lowering.py", line 778, in lower_call
    res = self._lower_call_FunctionType(fnty, expr, signature)
  File "/Users/siu/dev/numba-git/numba/core/lowering.py", line 944, in _lower_call_FunctionType
    assert fnty.check_signature(signature)
AssertionError

The CI failure should be now fixed (it was due to uncomplete error handling code that missed gil release).
The error message from @sklam example of value-dependent polymorphism is now more informative and the corresponding test case has been added to unittests.
All review comments have been addressed. Please review.

@sklam I have addressed all your comments and feedback. Please review.

@sklam some notes from our discussion.

Need to move import from numba/__init__.py to somewhere more appropriate.
Need to move any reasonable candidates to numba/experimental/.
Issue warning of experimental feature if used (i.e. unification of function types triggers warning), perhaps a NumbaExperimentalFeatureWarning or similar.
Longer term goal: compilation should derive from more in depth static analysis.

Merge conditions:

@pearu are you able to commit to providing support for fixing parts of this that may need alterations and also to respond to user bugs? Thanks.

@stuartarchibald @sklam , yes, I would be happy to continue improving the feature and fix any related bugs.

Thanks @pearu, that's great!

Fixes to the docs in 984a24b look good, thanks @pearu .

https://github.com/numba/numba/pull/5441 should be merged immediately after merging this


File list popup preventing mouse click

Does this issue occur when all extensions are disabled?: Yes

VS Code Version: 1.76.0-insider (system setup)
OS Version: Windows_NT x64 10.0.22621 (Windows 11)

Steps to Reproduce:

Open Visual Studio Code
Hover an item in file list with git initialized

It doesn't let me interact with the files.

/duplicate and fixed in the newest Insiders
Version: 1.76.0-insider (user setup)
Commit: 96a795cc0b1cd62f9ff66c347637f917c6dde3da
Date: 2023-02-17T22:22:55.538Z

Thanks for creating this issue! We figured it's covering the same as another one we already have. Thus, we closed this one as a duplicate. You can search for similar existing issues. See also our issue reporting guidelines.
Happy Coding!


Circuit currently allows measure gates with duplicated keys. Is this intentional?

It's not intentional. We are trying to get https://github.com/quantumlib/Cirq/pull/1862 in. Closing as a duplicate of https://github.com/quantumlib/Cirq/issues/2152.


bug: window titles are not showing up in macOS

Describe the bug
Titles in the webview window are not showing up in macOS when running examples in this repo.
To Reproduce
Run the examples in a macOS machine.
Expected behavior
The title "TEST" should appear in the top of this window.
Screenshots
Screenshot of window opened with the sample example:

Platform and Versions (please complete the following information):

OS: 64bit Mac OS X 10.15.6 19G73
Rustc: rustc 1.45.0 (5c1f21c3b 2020-07-13)

Hmm, it can't show the title in original repo either. Maybe we should also file a issue there.


"GraphQL Rate Limiting" pages need to be reviewed

Description:
Quoting few below which are either grammatically incorrect, have punctuation mistakes or capitalizing issues etc.
Please go through the entire sub section as there are multiple mistakes.
Overview Page

--

Query Depth Limit Page

-----

Affected Product Version:
3.2.0

This issue is in progress


Armada V1 and Armada V2 diagrams

Armada is migrating to a new set of components. To help users with that move, we need to have diagrams of both setups.
Currently we have https://github.com/armadaproject/armada/blob/master/docs/design/diagrams/relationships/armada_system.png, which is created using code from here https://github.com/armadaproject/armada/blob/master/docs/design/diagrams/relationships/generate.py. The one change that needs to happen, is it should be called "Lookout V2" instead of just "Lookout".
For the Lookout V1 Doc, it should instead look like this: https://drive.google.com/uc?id=1XtXdCP2dVXa2pXqLFGHdeSNkh8A6hBt8. Where items crossed out are part of V2, and the items in the green box are all one component.
We should have https://github.com/armadaproject/armada/blob/master/docs/design/relationships_diagram.md be changed to include both diagrams. I expect a PR for this to be a back-and-forth process.
┆Issue is synchronized with this Jira Task by Unito

@Sharpz7 would you like both diagrams in a single generate.py file or seperate python programs?

When I run generate.py file, it is not able to access images. I changed the reference to "images/armada.png" from "../files/armada.png" but still it's not accessing images. I don't know if it unique to my environment or is it something I don't understand. Please help me.
P.S: I changed "Lookout" to "Lookout V2".

After hours of exploration, I finally found solution.
In with Diagram(), I commented out filename parameter and it is working!
But the produced image will be in relationships folder and not in out folder.
Need help here.

should we add this info in our README.md ?

Please review Armada V2 diagram

Good spot with the I/o issues, feel free to edit it and document it as you see fit to get it working.


Logo not looking good on Google IO test of the Open Event Android App

Actual Behaviour
Just tested the open event android app on creating a new event over here: https://eventyay.com/events/173/
On downloading the apk  the logo doesnt look good.
Expected Behaviour
Improving the dimensions of logo in the Android App itself or setting logo dimension on eventyay when creating new event.
Steps to reproduce it

LogCat for the issue

Screenshots of the issue

Would you like to work on the issue?
Yes.
Target Milestone to solve the issue
Till which milestone will you be fixing the issue?
https://github.com/fossasia/open-event-android/milestone/24

@arp95 I think we should make the header color to be gray so that we remain neutral to the event pictures

@iamareebjamal
even grey doesn't make sense. like when i created an event they asked for a logo and the event image and for the event image they asked for a fixed size image. so we can do the same for the logo case or another alternative would be to automatically detect the logo size in the app itself and use that in to create the navigation drawer.

@arp95 But event images are alpha png, so background color does matter

@iamareebjamal
yes you are right. but do you think that will be efficient?
i think we can take logo size and adjust the navigation accordingly programmatically.

I agree, but I was talking about images being transparent. Transparent images are generally made to work on white backgrounds. That is why I suggested a light grey navigation header

@the-dagger @mariobehling @mananwason @iamareebjamal

After cahnging the background it looks like this. is it fine? or should i dynamically check the logo size and do work with that?

There are also logos in white. I think we need a theming option for the whole app to solve this. It is difficult to solve this "isolated case" by not thinking about the design of the whole app, e.g. the blueish color does neither work with the red color of the app.

@mariobehling
we can do one thing. get the logo colour during runtime and set the background colour according to that.

Yes, I think we should have an app theme attribute defining the app primary, dark and accent color in the JSON, and generator should update the colors in styles.xml at the time of apk building

@arp95 This will be suitable for this particular case. But let's suppose that a transparent png of red logo is provided, then, the Palette API will return red color, and if we make the background red, the logo won't be visible

yeah exactly. @mariobehling sounds good?

@iamareebjamal this is why i was opposing the idea of dynamic colour loading earlier and suggested tht i take the logo size and adjust the nav header accordingly. but apart from the logo we have to see that what app bar colour have to be and the entire design prospect, which means dynamic colour loading has to be used if we look for the entire app case.

@arp95 I think the best way to solve the problem is to tart allowing the user to select the theme colors while generating the app. Doing everything will be a bottleneck and eventually with bigger datasets, the app is bound to lag. Try to think of the project as a whole, not as an event app. In the bigger picture, we want to make everything customisable if the user wants it.

@mananwason
yes you are right.
so now should i open an issue on the server repo for this so that they can allow what we want?

I think it is more of a generator specific issue

@arp95 Let's open a new issue on this repo and get working on that. We need to implement ways to give the users options to customise the app on the generator

@mananwason
creating the new issue.

CLosing this. Any further discussion can take place over here #1552


Output to FITS files

Add option to write output for each colour band to a FITS file, simulating observational output formats.

This would also enable other ways of combining colour bands to a resulting RGB image


Importing storage technologies

I fixed this last week by giving the import_from attribute for batteries in the technologies-table an electricity_output_capacity property. But EtModel doesn't export the batteries correctly. Also Generic Battery isn't working in the technologies table, with this setting.

I fixed this last week by giving the import_from attribute for batteries in the technologies-table an electricity_output_capacity property.

For storage options, both electricity_output_capacity and electricity_input_capacity need to be assigned. For now, we can set them to the same value.

Also Generic Battery isn't working in the technologies table, with this setting.

Ignore "Generic battery" for now; it was used temporarily for testing and has been replaced by households_flexibility_p2p_electricity / "Battery". I'll make a note to remove it.

households_flexibility_p2p_electricity is not picked up correctly by ETLoader yet it seems.
I have 60% batteries in my scaled scenario but none in my technology table.


@Nonnull annotation for ReactPackage

Summary
Here are some leftovers from nullable annotations for native modules, discovered while developing native module in Kotlin. This will help improve Kotlin developer experience
Changelog
[Android] [Changed] - Add @Nonnull annotations to ReactPackage
Test Plan
CI is green

can't wait to have Kotlin code in RN 👍


Example Code DPC for DE

Thank you for a great package and associated paper.
I was wondering if you had example code on how to use the DPC as part of a DE model as you did in your comparative analysis?
On a related note, how does DPC differ from proDA? https://github.com/const-ae/proDA

Hi there thank you for the question and yes we are working on finalising the DPC-based pipeline for limma.
The main idea is that our DPC models the missingness patterns as a standalone method, where the DPC can be used to guide many different other downstream analyses, not just DE.
In proDA I believe the missingness modelling is integrated into the DE testing.

@Mengbo-Li Hope you are doing well. I just wanted to see if you had an update related to when this would be implemented into LIMMA? I would love to try it out with a current proteomics dataset I have on hand.


Cgroup issue i.e. RAC container is not coming up because of RT settings

Error response from daemon: OCI runtime create failed: container_linux.go:348: starting container process caused "process_linux.go:402: container init caused "process_linux.go:367: setting cgroup config for procHooks process caused \"failed to write 95000 to cpu.rt_runtime_us: write /sys/fs/cgroup/cpu,cpuacct/system.slice/docker-7855dc62aa673ffa14ca7d9271ae571b818e628b9fb586ba4604aba55afe2c34.scope/cpu.rt_runtime_us: invalid argument\""": unknown
Error: failed to start containers: racnode1

Please try following:
echo 950000 > /sys/fs/cgroup/cpu/cpu.rt_runtime_us
echo 1000000> /sys/fs/cgroup/cpu/cpu.rt_period_us
echo 95000 > /sys/fs/cgroup/cpu,cpuacct/system.slice/cpu.rt_runtime_us
Retstart container and let me know if you face any issue.

Please can you provide more information, like the output from docker info on this host?

Hi Djelibeybi,
[root@nodec ~]# docker info
Containers: 6
Running: 4
Paused: 0
Stopped: 2
Images: 62
Server Version: 17.06.2-ee-7
Storage Driver: overlay2
Backing Filesystem: xfs
Supports d_type: true
Native Overlay Diff: false
Logging Driver: json-file
Cgroup Driver: systemd
Plugins:
Volume: local
Network: bridge host macvlan null overlay
Log: awslogs fluentd gcplogs gelf journald json-file logentries splunk syslog
Swarm: inactive
Runtimes: runc
Default Runtime: runc
Init Binary: docker-init
containerd version: 6e23458c129b551d5c9871e5174f6b1b7f6d1170
runc version: 462c82662200a17ee39e74692f536067a3576a50
init version: 949e6fa
Security Options:
seccomp
Profile: default
Kernel Version: 4.1.12-112.16.4.el7uek.x86_64
Operating System: Oracle Linux Server 7.4
OSType: linux
Architecture: x86_64
CPUs: 1
Total Memory: 19.08GiB
Name: nodec
ID: OBQJ:DYCP:BAR4:C2BF:ZXZ6:YBY2:ITPE:CZRI:U6XR:IA3L:YO4S:TJAQ
Docker Root Dir: /var/lib/docker
Debug Mode (client): false
Debug Mode (server): false
Registry: https://index.docker.io/v1/
Experimental: false
Insecure Registries:
<IP_ADDRESS>/8
Live Restore Enabled: false
Thank you very much.

Is this still an issue? Your other issues have been resolved?

This is not issue， other issues have been resolved.

Great. Closing this because it is not an issue.


Open on mouseover / hover

Hi
Just wondering if there is a way to open the select item when hovering instead of clicking? I can't attach a standard hover and then fire the open event as the select and the dropdown don't have a shared parent container element (meaning I'd mouseout when trying to select an item from the dropdown).
Many thanks,
Shaun

Someone know how to do this?

This appears to be a usage question, rather than a bug report or feature request.  Please see our contributing guidelines.
Usage questions should be discussed on the forums instead.


Rewrite gallery example for masks to boxes.

Not done yet, I will ping once it's ready for review.

I think I have completed it. Now the tutorial includes converting masks to boxes and

torchvision.io to read images and masks.
Plotting masks and boxes using torchvision.utils
Using FasterRCNN over converted boxes.
A simple SegmentationToDetection dataset

Feel free to review @NicolasHug @0x00b1

thanks @oke-aditya , I'll take a look tomorrow

Here is the link to rendered example :smile:
https://822905-73328905-gh.circle-artifacts.com/0/docs/auto_examples/plot_repurposing_annotations.html#

Hi @NicolasHug feel free to have a review.

Hey @NicolasHug two small things to clear, then we would be good to merge.

We should be good to merge!! @NicolasHug

Here is the link for final docs. :smiley:
https://826691-73328905-gh.circle-artifacts.com/0/docs/auto_examples/plot_repurposing_annotations.html

Thanks again @oke-aditya !!

I learn a lot by contributing. Thanks to you guys. 😀


Indicator/Warning for when EMI+JEI aren't installed server-side

I ran into an issue where I wasn't able to use fill recipe while in multiplayer for mods that require advanced integration, but could while in singleplayer.
In my case, it was sophisticated backpacks. Which threw a weird error every time I tried to use fill recipe server side.
Received invalid discriminator byte 14 on channel sophisticatedcore:channel

Anyways, I spent like 3 hours looking over this before realizing the server didn't have JEI so didn't know what the client was talking about.

If this is a JEI recipe fill handler, the onus is on JEI to detect this. EMI can generally handle being not installed on the server itself.


Update logging.mdx typo

Minor typo fixed on line 34

@HonestFreak Thanks so much for catching that!!! It's really helpful to have folks submitting small things they notice like this!! We really appreciate the PR.
The change is perfect! Once the checks finish running, I'll go ahead and merge this to main 👍🏻


Add BeAsyncEvent

Is your feature request related to a problem? Please describe.
Implement BeAsyncEvent<T> that has the same interface as BeEvent<T> but supports/respects async functions (awaits Promises).
Describe alternatives you've considered
Async code is all around, it only seems natural to have async aware BeEvent in the core and not have to implement similar types on every project.

Please provide examples of why it is useful for the event dispatcher to await each event listener's callback. i.e., if you and I both subscribe to SomeEvent, why would it be useful for my listener to have to wait to be notified of the event until after your listener completes whatever potentially long-running async work it wants to do?
To me that makes no sense. BeEvent is about notifying any number of listeners of an event's occurrence, at the moment it occurs. Each listener can respond in whatever manner it sees fit, and should not interfere with or delay notification of other listeners. The notifier does not care - it's job is complete once it has notified all listeners.
If I misunderstand your proposal, please clarify.

I think you are right @pmconne, the purpose of BeEvent should only be to notify of an event that happened (should not care how its handled). Perhaps the thing I need (awaiting the completion of all handlers) is not general enough or at least the name of BeAsyncEvent doesn't fit.
In my use case, I'll just go with an array of async handlers that are invoked and awaited.


Possible issue with port forwarding and wallet sync on latest image.

Hi all,
I've just done a fresh install of TrueNAS Scale, and deployed/install the latest Official Chia pod/container onto the system (version 1.8.1, 1.0.10).
The Full Node is syncing fine, however the Wallet does not appear to be syncing at all. Also, it looks like the Port Forwarding on the container isn't working. I've correctly got ports 8444 and 8447 forwarded to 38444 and 38447, but they don't appear as being opened. I've tested with other application ports, and port forwarding on the host is working correctly for those other apps.

Hello,
You shouldn't need ports forwarded to the wallet in order for it to sync, so I'm not sure that is the issue here. The logs are indicating that every peer the wallet is trying to connect with is not synced, which seems like a different problem (admittedly weird and unexpected that you would hit that many un-synced peers in a row).
I tested the 1.8.1 chia-docker container outside of the truenas context and was able to get the wallet synced without any issues
docker run --rm -it -e service=wallet -e log_level="INFO" chianetwork/chia-docker:1.8.1
It seems like this may be an issue specific to running this on TrueNAS, but you could possibly try removing the wallet_peers.dat file (in ~/.chia/mainnet/wallet/db or whatever your equivalent path would be) and then restarting the container to see if maybe you just have a bunch of bad peers in your peer list


Calc's grammar allows "stmtOrExpr" "stmtOrExpr" without separators

... which wasn't the intent. It should be more like: stmtOrExpr ( EOL | ';' ) stmtOrExpr (repeated of course)

Related to #343 .


S3 Lock service

What problem does this PR solve?
Issue Number: ref https://github.com/pingcap/tiflash/issues/6827
Problem Summary: We need one and only one tiflash node run S3 lock service.
What is changed and how it works?
Depends on

OwnerManager: https://github.com/pingcap/tiflash/pull/6863
diff 1e7378...b918ba5
kvproto: https://github.com/pingcap/kvproto/pull/1060
https://github.com/pingcap/tiflash/pull/6878

S3Filename
Generate the S3 object keys for local file or parsing the key from S3 object key
S3LockService
S3LockService provides two RPC interface and ensure these two operations with the same key (the S3 key of CheckpointDataFile/DTFile)  is atomic on S3

TryAddLock
TryMarkDelete

If the owner changed, this service will return NotOwner with the new owner id to client. Client should retry the request to new owner.
S3LockClient
Make rpc request to the S3 GC owner. S3LockClient will automatically retry when owner is changed
Check List
Tests

[x] Unit test
[ ] Integration test
[ ] Manual test (add detailed scripts or steps below)
[ ] No code

Side effects

[ ] Performance regression: Consumes more CPU
[ ] Performance regression: Consumes more Memory
[ ] Breaking backward compatibility

Documentation

[ ] Affects user behaviors
[ ] Contains syntax changes
[ ] Contains variable changes
[ ] Contains experimental features
[ ] Changes MySQL compatibility

Release note

None

/rebuild

/run-all-tests

/run-all-tests

/run-unit-test

/run-unit-test

/merge

/run-unit-test

/run-unit-test

/rebuild

/run-unit-test

/merge

/merge

/run-unit-test

/merge


Uncaught ValueError in base_coder.py line 156

Aider version: 0.58.0
Python version: 3.12.4
Platform: Windows-11-10.0.22631-SP0
Python implementation: CPython
Virtual environment: No
OS: Windows 11 (64bit)
Git version: git version 2.46.2.windows.1
An uncaught exception occurred:
Traceback (most recent call last):
  File "<frozen runpy>", line 198, in _run_module_as_main
  File "<frozen runpy>", line 88, in _run_code
  File "__main__.py", line 7, in <module>
    sys.exit(main())
             ^^^^^^
  File "main.py", line 727, in main
    coder.run()
  File "base_coder.py", line 730, in run
    self.run_one(user_message, preproc)
  File "base_coder.py", line 773, in run_one
    list(self.send_message(message))
  File "base_coder.py", line 1201, in send_message
    self.reply_completed()
  File "architect_coder.py", line 32, in reply_completed
    editor_coder = Coder.create(**new_kwargs)
                   ^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "base_coder.py", line 156, in create
    raise ValueError(f"Unknown edit format {edit_format}")
ValueError: Unknown edit format whole-file

Thank you for filing this issue.
This error should be handled more gracefully. The allowed valued for edit formats are whole and diff (there are more, but those are experimental,  avoid them for now).

Thanks for trying aider and filing this issue.
How did you cause this error? If you run aider with a bad edit format, it should print a nice error:
$ aider --edit-format nonono
─────────────────────────────────────────────────────────────────────────────────────────────────────────
Unknown edit format nonono

Hi,
I was in architecture mode, setting up new project repo using win
powershell with my usual yaml config but forgot I had testing instructions.
Aider was trying to test, and rightly said it couldn’t but crashed. It may
have been missing rights to edit in powershell or incorrect path. When I
get a chance I’ll try to replicate if needed and send more info.
On Sat, 2 Nov 2024 at 4:14 AM, paul-gauthier @.***>
wrote:

Thanks for trying aider and filing this issue.
How did you cause this error? If you run aider with a bad edit format, it
should print a nice error:
$ aider --edit-format nonono
─────────────────────────────────────────────────────────────────────────────────────────────────────────
Unknown edit format nonono
—
Reply to this email directly, view it on GitHub
https://github.com/Aider-AI/aider/issues/1835#issuecomment-2452046372,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BJHQMEGELVEDUI5C4X7YDZDZ6OLFNAVCNFSM6AAAAABPCQC3COVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDINJSGA2DMMZXGI
.
You are receiving this because you authored the thread.Message ID:
@.***>

I'm labeling this issue as stale because it has been open for 2 weeks with no activity. If there are no additional comments, it will be closed in 7 days.


[Bug][Worker Manage]Monitor Chart balnk display

Describe the bug
with correct response data , the monitor chart doesn't show as expected.
Expected behavior
just show the correct chart rather than blank
Screenshots

Which version of Dolphin Scheduler:
-[1.3.2-preview]

Hi～
Please try clear the site cache and try it again.Multi version ui maybe have the left cache in your browser.

{
    "code": 0,
    "msg": "成功",
    "data": [
        {
            "id": 31,
            "host": "<IP_ADDRESS>",
            "port": 5678,
            "zkDirectory": "/dboard/nodes/master/<IP_ADDRESS>:5678",
            "resInfo": "{\"cpuUsage\":0.02,\"loadAverage\":0.19,\"memoryUsage\":0.41}",
            "createTime": "2020-08-20T07:05:17.000+0000",
            "lastHeartbeatTime": "2020-08-20T07:31:53.000+0000"
        },
        {
            "id": 30,
            "host": "<IP_ADDRESS>",
            "port": 5678,
            "zkDirectory": "/dboard/nodes/master/<IP_ADDRESS>:5678",
            "resInfo": "{\"cpuUsage\":0.03,\"loadAverage\":0.01,\"memoryUsage\":0.25}",
            "createTime": "2020-08-20T06:42:30.000+0000",
            "lastHeartbeatTime": "2020-08-20T07:31:54.000+0000"
        },
        {
            "id": 30,
            "host": "<IP_ADDRESS>",
            "port": 5678,
            "zkDirectory": "/dboard/nodes/master/<IP_ADDRESS>:5678",
            "resInfo": "{\"cpuUsage\":0.0,\"loadAverage\":0.14,\"memoryUsage\":0.48}",
            "createTime": "2020-08-20T07:05:21.000+0000",
            "lastHeartbeatTime": "2020-08-20T07:31:47.000+0000"
        }
    ]
}

clear the cache, use new browser,still not show as expect.
the last one show blank ,may be the cpuUsage=0 make something wrong?

finaly I found the key, the two worker start by docker ,and have the same pid.
worker in different machine has same pid is ok, so this is a bug

finaly I found the key, the two worker start by docker ,and have the same pid.
worker in different machine has same pid is ok, so this is a bug

fixed #3563

fixed #3563


[BUG]  A segmentation fault happened when calling utils op flatten

Describe the bug
A segmentation fault happened when calling utils op flatten. The utils op is in JIT mode. I have try to delete the cache, and rerun, Nothing help. Finally, I clone the DeepSpeed repo, install it locally. The error still happen. But when I install it with utils op built, The error disappear. I donot know the difference between JIT and built with package. The issue only triggered in former
To Reproduce
Steps to reproduce the behavior:
call deepspeed init, and flatten is called int allreduce_bucket.
Expected behavior
no error
ds_report output
--------------------------------------------------
DeepSpeed C++/CUDA extension op report
--------------------------------------------------
NOTE: Ops not installed will be just-in-time (JIT) compiled at
      runtime if needed. Op compatibility means that your system
      meet the required dependencies to JIT install the op.
--------------------------------------------------
JIT compiled ops requires ninja
ninja .................. [OKAY]
--------------------------------------------------
op name ................ installed .. compatible
--------------------------------------------------
async_io ............... [NO] ....... [OKAY]
cpu_adagrad ............ [NO] ....... [OKAY]
cpu_adam ............... [NO] ....... [OKAY]
fused_adam ............. [NO] ....... [OKAY]
fused_lamb ............. [NO] ....... [OKAY]
quantizer .............. [NO] ....... [OKAY]
random_ltd ............. [NO] ....... [OKAY]
 [WARNING]  sparse_attn requires a torch version >= 1.5 and < 2.0 but detected 2.0
 [WARNING]  using untested triton version (2.0.0), only 1.0.0 is known to be compatible
sparse_attn ............ [NO] ....... [NO]
spatial_inference ...... [NO] ....... [OKAY]
transformer ............ [NO] ....... [OKAY]
stochastic_transformer . [NO] ....... [OKAY]
transformer_inference .. [NO] ....... [OKAY]
utils .................. [NO] ....... [OKAY]
--------------------------------------------------
DeepSpeed general environment info:
torch install path ............... ['/home/ps/mambaforge/envs/videomae/lib/python3.10/site-packages/torch']
torch version .................... 2.0.1
deepspeed install path ........... ['/home/ps/mambaforge/envs/videomae/lib/python3.10/site-packages/deepspeed']
deepspeed info ................... 0.9.2, unknown, unknown
torch cuda version ............... 11.8
torch hip version ................ None
nvcc version ..................... 11.8
deepspeed wheel compiled w. ...... torch 2.0, cuda 11.8

Screenshots
If applicable, add screenshots to help explain your problem.
System info (please complete the following information):

Ubuntu 22.04
x2 RTX4090
Python 3.10

Launcher context
using python function
Docker context
no docker
Additional context
Add any other context about the problem here.

Hi @vipcxj - were you using the git tag from the version you intalled from pip when building from source?  That's the only immediate difference I can think of.  If not, could you try again and see if you can repro this with the latest DeepSpeed and can get a repro case for us to try out?

Hi @vipcxj - closing this issue for now, if you're still having issues with this, please re-open.
More info on pre-installing DeepSpeed ops can be found here as well.


Replace the video header with a valid one

Checklist

[ ] I'm reporting a site feature request
[ ] I've verified that I'm running youtube-dl version 2019.06.08
[ ] I've searched the bugtracker for similar site feature requests including closed ones

Description

WRITE DESCRIPTION HERE

Here: https://vaughn.live/embed/video/lmshows_koq server gives the video with the following title:

4D 56 4E 02 05 00 00 00 09 00 00 00 00 12 00 01 -> MVN.............
It can be downloaded using youtube-dl, streamlink, curl, IDM and others. All of these tools save a video file with this title to disk. But such a file is not played by the video player.
To play such a file, you need to change the header from to
4D 56 4E 02 -> MVN.    to
46 4C 56 01 -> FLV.
However, TubeDigger immediately saves the video file to a disk with the correct title.
I ask the developers to make it so that youtube-dl can do the same.


Dockerfile fails ot produce XML output

Describe the bug
Trying to use docker to run tarpaulin and produce XML fails.
To Reproduce
docker run --security-opt seccomp=unconfined -v "${PWD}:/volume:rw" \
  xd009642/tarpaulin:develop-nightly \
  cargo build && cargo tarpaulin --out Xml

Produces the error: Error: "Failed to report coverage! Error: Failed to create run report".
No additional information is logged about why it failed. It had even produced coverage information already.
If I specify --output-dir=/volume the error changes to Error: "Failed to create or locate custom output directory: Some(\"/volume\")"
Expected behavior
The output file added to my local directory.

I believe this issue is around docker command chaining, the following seems to work for me:
docker run --security-opt seccomp=unconfined -v "${PWD}:/volume:rw" \
  xd009642/tarpaulin:develop-nightly \
  /bin/bash -c "cargo build && cargo tarpaulin --out Xml"

Whoops! Indeed it is. Thanks!


invalide date

trying https://ss.rec.la it gives ERR_CERT_DATE_INVALID error
i think certificate is expired.

Hi @TonyStark, could you post the steps to reproduce the error? The certificate is up-to-date as far as I can see.

problem solved.
actually i was using old certificate. but now i updated from site and everything works