sync TcpStream, UnixStream and UdpSocket functionality

A few features have been added to one or the other. This brings them back to parity with each other.
Socket:
pub(crate) fn from_std<T: IntoRawFd>(socket: T) -> Socket

    Socket.from_std is changed from being UdpSocket specific to
    being generic over the IntoRawFd trait.

TcpStream:
pub from_std(std::net::TcpStream) -> TcpStream

UdpSocket:
pub(crate) fn from_socket(Socket) -> UdpSocket

pub fn shutdown(std::net::Shutdown) -> io::Result<()>

unsafe fn from_raw_fd(RawFd) -> UdpSocket

fn as_raw_fd() -> RawFd

UnixStream:
pub fn from_std(std::os::unix::net::UnixStream) -> UnixStream

pub(crate) from_socket(Socket) -> UnixStream

pub fn write_all<T: IoBuf>(mut buf: T) -> BufResult<(), T>

pub fn shutdown(std::net::Shutdown) -> io::Result<()>

unsafe fn from_raw_fd(RawFd) -> UdpSocket

fn as_raw_fd() -> RawFd

I hope these are considered trivial additions and trivial changes. Will fix up as you wish.

I will submit a new PR with these changes squashed into a new commit.

What's the reason for the new PR?

Wanted a single commit to contain those changes and wanted the branch to be up to date so wanted to build it off the new master and cherry-pick the old commit. I'm not used to the multiple commits in a single merge and also didn't know if they always get squashed automatically by the tool or would have required you to squash them later.


Removed all "Update" references. Pushed version to 1.11.0 and macOS t…

…o 10.14. Resized preferences and removed Updates tab. Changed Issue link from right click menu of menu bar icon and removed KM link. Furthermore fixed some deprecations.

I hope I did it the right way :)


yarn says momi is not compatible with node 8.x

https://github.com/Avaq/momi/blob/7c00ad64e49c3071b71613445429a7e75174d262/package.json#L22
or, is it just a typo?

Yeah, that's a mistake. It should have been >=.


Cannot import Classification Dataset into DIGITS from customized object classes

Hi all,
I followed the tutorial to step "Customizing the Object Classes". But in step "Importing Classification Dataset into DIGITS" I see below error.
2018-02-08 15:19:29 [20180208-151926-18de] [WARNING] Parse Folder (train/val): Not enough images for this category 2018-02-08 15:19:29 [20180208-151926-18de] [ERROR] Parse Folder (train/val): Did not find two valid categories 2018-02-08 15:19:29 [20180208-151926-18de] [ERROR] Parse Folder (train/val) task failed with error code 1
I think this error comes from the structure of the dataset because I compared with the COCO dataset structure in some next steps.
Could you guide me how to re-create the dataset to retrain the network? Thanks.

I found that DIGITS cannot train the dataset because I put the dataset on another disk (under /media/disk). When I move dataset to home direction, it can run now.


Disable comments

Disable comments
Use ints for enums

#685  👈 (View in Graphite)
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Merge activity

Dec 7, 4:58 AM EST: A user started a stack merge that includes this pull request via Graphite.


Mistral example code error: missing model data

Issue

I followed the mistral example code(quantized version) and ran it as follows.
cargo run --example mistral --release -- --prompt "Here is a sample quick sort implementation in rust " --quantized -n 400

But I received the following error:
    Finished release [optimized] target(s) in 0.16s
     Running `target/release/examples/mistral --prompt 'Here is a sample quick sort implementation in rust ' --quantized -n 400`
avx: true, neon: false, simd128: false, f16c: true
temp: 0.00 repeat-penalty: 1.10 repeat-last-n: 64
Error: request error: https://huggingface.co/mistralai/Mistral-7B-v0.1/resolve/main/model-q4k.gguf: status code 404

Caused by:
    https://huggingface.co/mistralai/Mistral-7B-v0.1/resolve/main/model-q4k.gguf: status code 404

(Expected) cause

In a recent commit 88589d88153bef3316a13741bd12bf5e7963957a, the default value of the model_id variable was changed. However, the repository does not have the file "model-q4k.gguf".

(Expected) solution

The modified source code in mistral directory can be reverted to the previous version, or the example(quantized version) of mistral can be changed as follows.
cargo run --example quantized --release -- --which 7b-mistral --prompt "Here is a sample quick sort implementation in rust "

And the following is the result of executing the modified example.
    Finished release [optimized] target(s) in 0.18s
     Running `target/release/examples/quantized --which 7b-mistral --prompt 'Here is a sample quick sort implementation in rust '`
avx: true, neon: false, simd128: false, f16c: true
temp: 0.80 repeat-penalty: 1.10 repeat-last-n: 64
loaded 291 tensors (4.14GB) in 0.06s
model built
Here is a sample quick sort implementation in rust 0.11.1 using `itertools`.

``
#![feature(test)]
extern crate itertools;
use itertools::*;

fn main() {
    let v = [(-2, -3), (-4, 1), (1, 2)]; // [-2, 1, -4, -3, 2]
    quicksort(&mut v.iter().cloned()); // sort in place
    println!("{:?}", v); // [0, 1, 2, 3, 4]
}
``
By the way: I don’t think this code will compile with the default compiler flags; it needs `--test` to allow the runtime to call the function twice without recompiling between calls. See https://github.com/rust-lang/rfcs/pull/518, which is being considered for Rust 1.0, for details.
...
  11 prompt tokens processed: 11.37 token/s
 805 tokens generated: 3.90 token/s

(The execution results are not satisfactory... I would suggest reverting the source code in mistral directory to the previous version.)

Sorry about that, I broke the quantized version when switching to using the official safetensors weights. I've just pushed a fix so hopefully it should be back to working.

@LaurentMazare  which commit i can use?   I got the error when using the quantized mistral example. thanks!
commit
bdd8107fda4cd02f6a37330ad6c395f70abbdcbc
error message
cargo run --example quantized --release -- --prompt "The best thing about coding in rust is " --model llama-2-7b.ggmlv3.q4_0.bin
Finished release [optimized] target(s) in 0.32s
Running /root/dev/candle/target/release/examples/quantized --prompt 'The best thing about coding in rust is ' --model llama-2-7b.ggmlv3.q4_0.bin
avx: true, neon: false, simd128: false, f16c: false
temp: 0.80 repeat-penalty: 1.10 repeat-last-n: 64
loaded 291 tensors (3.79GB) in 11.01s
params: HParams { n_vocab: 32000, n_embd: 4096, n_mult: 256, n_head: 32, n_layer: 32, n_rot: 128, ftype: 2 }
thread 'main' panicked at 'called Option::unwrap() on a None value', /root/.cargo/registry/src/mirrors.ustc.edu.cn-12df342d903acd47/gemm-f32-0.16.15/src/gemm.rs:3:5
note: run with RUST_BACKTRACE=1 environment variable to display a backtrace

That's odd, I cannot reproduce the issue locally either on mac or x86 (without the --model file). I just updated the gemm version where the error is coming from to the latest 0.17.0, could you give this a spin at the current github tip? Hopefully the new version will make for a more interesting error message.


Revert MPC_LAND_ALT1/2 to original defaults to prevent slowing down too late

Describe problem solved by this pull request
This reverts commit 59bd3e9f6e72db5d1751fc11fe6dccaf1c69b05e from https://github.com/PX4/Firmware/pull/14560. I checked and this change was only introduced because the vertical velocity in position mode got constrained (too much) when getting closer to the ground when testing the relatively samll pixhawk vision. Since then the horizontal slow down was more or less disabled by only limiting to 10 m/s in https://github.com/PX4/Firmware/pull/15029. Also the defaults should represent safe values for a wide variety of suppoerted vehicles and can be adjusted if not "itght" enough for certain use cases.
Since that change we had multiple incidents where also larger drones slowed down too late and hit the ground quite hard and I consider it a safety critical issue. The cases seem to have various root causes from not enough thrust to distance sensor acceptance delay issues. Most if not all of them could have been prevented by just starting slow down earlier. So this seems an easy and useful fix since the original change was probably tyring to solve the same issue as https://github.com/PX4/Firmware/pull/15029.
Test data / coverage
It's restoring the original defaults that were tested a lot.
Additional context
Testpilot @fury1895 confirmed that usually he needs to increase the values from the defaults for safe operation.

No objection here. I'd still like to consider renaming or even partially eliminating these at some point.

I'd still like to consider renaming or even partially eliminating these at some point.

I agree, there should be one that represents a safety distance from ground and has an adequate name.


Delete the '--custom_for_pub' argument from make_version.py

The option '--custom_for_pub' was added to make_version.py to enable Flutter to invoke the Dart build using this option
(see https://github.com/flutter/flutter/issues/14751 for more details on why this was done).
This option causes problems as we end up with Flutter building a Dart SDK that pretends to be a version that it is not
(please see https://github.com/flutter/flutter/issues/62146 for the kind of issues using the '--custom_for_pub' option to
create a version string causes).
This is set up in the flutter engine build as follows:
tools/gn has this line
gn_args['dart_custom_version_for_pub'] = 'flutter'
and the Dart build rules have this line
if (dart_custom_version_for_pub != "") {
args += [
"--custom_for_pub",
dart_custom_version_for_pub,
]
}
This option needs to be removed from make_version.py as we do not want the Dart SDK reporting a version that it is not.

/cc @whesse @athomas @zanderso @tvolkert

Sounds good to me, we should land it.  But then we need to roll, to get it, right?

Sounds good to me, we should land it. But then we need to roll, to get it, right?

Yes, it is not going to help the current situation but it will avoid such issues in the future.

Same problem on Windows when doing 'flutter upgrade'

@a-siva
Please re-evaluate this and do one of the following:

Add it to a milestone if it is still P1
Change priority label and add milestone if no longer P1
Close, if this issue is no longer needed

@athomas - are we clear to do this?  if so, can you reassign to @a-siva to land a fix?  if not, can you bump from Sept?

I did trigger the 3xH tryjob on asiva's CL to remove the flag and it was
green. So maybe we can just remove it? I'm not sure when this flag makes a
difference in our infrastructure, though.
In any case, this is hardly a P1 because Flutter infrastructure no longer
relies on this code path anymore. This is now only used in our 3xH infra.
On Tue, Aug 18, 2020, 17:48 vsmenon<EMAIL_ADDRESS>wrote:

@athomas https://github.com/athomas - are we clear to do this? if so,
can you reassign to @a-siva https://github.com/a-siva to land a fix? if
not, can you bump from Sept?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/dart-lang/sdk/issues/42820#issuecomment-675559316,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AEYRJB7ENUKCWHTE5I7XVJLSBKPDZANCNFSM4PGAR7YA
.

a-siva has landed the CL.


[Risk]: Processing large data volumes with CWL and Docker

Who: U-SPS
When: April 2023
What: Copying data from PCM to Docker Container might cause issues: large data volumes require a lot of storage/time for data transfer. Might cause issues with CWL.

TLDR: when executing multiple CWL steps via Docker containers, it seems like data is not copied every time from one container to the other, but rather referenced by mounting volumes into the successive containers. So when executing the CHIRP workflow we should make sure that:
a) The EKS node has enough storage to store all input and output data (a single copy only)
b) The CWL steps do NOT use the "staging" option, which would cause the input data to be copied to the current working directory. In other words, do NOT do something like this:
requirements:
InitialWorkDirRequirement:
listing:
- $(inputs.src)


Add WPF platform to the AllControls Sample

An attempt at adding WPF to the AllControls Sample as mentioned in https://github.com/fsprojects/Elmish.XamarinForms/issues/55 .

I could run the sample - I noticed a few glitches, which I assume are due to the Xamarin.Forms.WPF implementation.
The sample isn't very "pretty" and it would be great if someone went over the controls and made them look a bit better (e.g. made the editing box be a decent size, used StackLayout a bit less etc.) :)

Yeah I saw that.  There are definitely some re-sizing issues going on at a minimum.
Are you suggesting a view function just for WPF?

Will close/reopen to retest CI

I hit the same error earlier because the log file has become too long. Cherry-picking https://github.com/fsprojects/Elmish.XamarinForms/pull/69/commits/ac24b4fa5a9b7ae2deba63b2f625c401d6dde6d9 should fix it.
Once that is fixed, I think the build will still fail because we don't have WPF on the OSX build machine :)

replaced by #175


[feature-resquest] OM - Create label for Schemas

Hi OM Team!
Good day!
It's will be very interesting to have a label for schemas, with that, we can control the access from users, not just controlling by tables.

@BessonEduardo, do you mean ability to add tag labels to Schema? If that is the case, it has been added by https://github.com/open-metadata/OpenMetadata/pull/10381. Marking this as resolved. Feel free to open it with clarifying comments.


add dispatchMain to wrapping overlay

dispatch_main is meant to be made available via
the global function dispatchMain().

hah that could be useful.
@mwwa is it what we're doing too on Darwin?


added missing license headers

Note that this PR targets the branch feature/r2-xxx-js_latest, which is expected to be merged soon into feature/new-db (see https://github.com/readium/readium-desktop/pull/189 ).
If you prefer to target feature/new-db directly (and separately), then let's close this PR and delete the associated branch (feature/r2-xxx-js_latest_license-headers).
Then, simply use the following command line utility to update the license headers in any other branch:
cd readium-desktop && node ../r2-utils-js/tools/license_header.js ./src
Assuming the filesystem:
/
|___ readium-desktop
|___ r2-utils-js

PR now updated to match the latest feature/r2-xxx-js_latest (which itself is sync'ed with feature/new-db, ready to be merged).


how to config the path in zookeeper?

I want to change zhe path in zookeeper /dubbo/....
but how to config it ?

<dubbo:registry address="zookeeper://<IP_ADDRESS>:2181" group=" the path you want"/>
such as <dubbo:registry address="zookeeper://<IP_ADDRESS>:2181" group="payway"/>

@kimmking thx

thxs


Add string_less_than data-test expression

Codecov Report

Merging #97 into master will not change coverage.
The diff coverage is 100.00%.

@@            Coverage Diff            @@
##            master       #97   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files            8         8
  Lines          570       569    -1
  Branches        87        85    -2
=========================================
- Hits           570       569    -1

Impacted Files
Coverage Δ

src/awsstepfuncs/choice.py
100.00% <100.00%> (ø)

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 39a86a0...3e55189. Read the comment docs.


Handle prismic urls

What?
The app currently uses a hardcoded url in the player. This PR fetches a url from Prismic based on a videoId which is stored in app state. If no such video stream is available it defaults to the original hardcoded url.
Why?
This enables us to see the correct content for the event.
How?
To be able to fetch a url from Prismic, we need an ID for the video in question.
In the existing event data state in the app, we are able to harvest a list of video IDs, filtering out the ones that have the isBroken field set to false. The filtered list may contain several videos and several types of video - ("performance", "behind the scenes" or "trailer").
We are currently only interested in "performance" videos, so we need to identify these. That data is not available in the app state, so I needed to build a new list of data fetched from Prismic, in parallel to the event data. That list of videos can then be filtered to match the ids of the filtered video list from events mentioned in the last paragraph. I tried to make the saga that does this as consistent as possible with the code that fetches the events, such that I was able to factor out some common code there (for the time delay).
By this stage, we have one or more IDs for performance videos. NB: I chose to take the first at this stage, which I have confirmed now is the appropriate behaviour even in the production environment.
I also added a saga to fetch the url when we have a url available (ie. when there is an ID in the list we created above). The url is then placed in the state for that video in the list that I originally fetched from Prismic.

@sinewave440hz can you please update your description for this PR, ideally along the lines of https://www.pullrequest.com/blog/writing-a-great-pull-request-description/

I gave the template you suggested a try @tomdyson

Thank you @sinewave440hz! This is exactly what I needed.


Adding Protein Structure Prediction related functionality

Looks good mostly. See some small comments inline. Also, unless I missed it, shouldn't there be some code that uses all these test data files? are you planning to add tests/examples?

Thanks!
Currently most (or possibly all) of the code that uses the test data is found in the jupyter notebooks, we should definitely add more test, I agree!

tests

I think that I mostly use the test data in example jupyter notebooks, I'll check

tests

I think that I mostly use the test data in example jupyter notebooks, I'll check

If the notebook is not in fusedrug. I suggest moving it to the notebook repo.


[question] ViTSTR experiment

Hi @baudm 👋 ,
thanks a lot for this great repository 👍
I saw you have run some experiments with ViTSTR and an input of 32x128.
Could you maybe share the results ? :)
And do you run the experiment from scratch ?
I have planned to integrate both ViTSTR and ParSeq in https://github.com/mindee/doctr in the next time 👍
Best regards

Hello @felixdittrich92. Thanks for your interest and initiative for integration.
The results for ViTSTR for 128x32 images are in the paper. arXiv link in the README. :)
Yes, all models were trained from scratch using the same exact datasets and training pipeline and strategy (in contrast to the original ViTSTR which used DeiT weights for initialization).

@baudm Thanks 👍


LuaTable sorted

Hallo, I'm currently trying some basic functionality of SLua (great work!) and I wondered if it's possible to get the hashed values of a LuaTable sorted in the original way it was written? Iterating over the pairs in C# gets them in a random order, which is understandable.
(I used MoonSharp before, and there the values were in the original order.)

No, you can't.


Update single-user-sobigdata with conda-lock

Summary
Merge all the conda and pip deps into a single environment file and use conda-lock to pin the environment.

Related issue :

We are getting
ERROR:root:[Errno 28] No space left on device

which is expected since the env is so huge.
According to my tests the build requires around 20GB of disk, do you know how much do we have available for the CI?

xref: https://github.com/marketplace/actions/maximize-build-disk-space
answer: 29GB

for the record, disabling the building of the base image still runs out of disk space for this new env.
we are going to check with the user community about having a number of smaller envs to replace this single big one

Issues again after adding back the building of the base image on the same PR.


Run Blackhole on 22.04

Ticket
#14393
Problem description
Move BH pipeline to 22.04
What's changed

Plumb the correct version of Python to the wheel builder
Install the repo to be able to run the unit tests -- not really sure why it fails in 22.04 but was okay with 20.04.

Checklist

[ ] Post commit CI passes  https://github.com/tenstorrent/tt-metal/actions/runs/12300743997
[x] Blackhole Post commit (if applicable) https://github.com/tenstorrent/tt-metal/actions/runs/12289973402

Another issue we had for higher python versions, including a link in there to another issue detailing our struggles with editable install: https://github.com/tenstorrent/tt-metal/issues/10765


LoadSnapshot

Signed-off-by: Kazuyoshi Kato<EMAIL_ADDRESS>Issue #, if available:
Description of changes:
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Great to see this PR up @kzys. One thing I really liked about the current SDK is how it configures CNI during the initial setup of the VM, I started poking around with the unix socket and manual HTTP requests to try to load a snapshot, but this fails due to the missing network. What sorts of requirements are there on the networking tap/veth devices for a restore from a snapshot? The VMID is used or a random UID for the network namespace, is that required for rehydrating the snapshot?
Happy to do some early testing, what I'd look for is a simple script / main.go that shows:
Create VM with CNI bridge / host-local and tc-tap-redirect and stable VMID
Pauses, snapshots, kills process
A new process is started, loads the snapshot, and networking in the guest still works

hi @kzys, it is great to see progress on snapshot support in the SDK. I wonder if you have a different implementation in mind, compared to our implementation apart from the fact that we implemented it in the firecracker-containerd directly.

Hi @kzys, this is what I got when trying to add the following to the existing "create VM" method I have:
	if action == "load" {
		fcCfg.Snapshot = firecracker.SnapshotConfig{
			MemFilePath:         path.Join(cwd, "mem"),
			SnapshotPath:        path.Join(cwd, "disk"),
			ResumeVM:            true,
			EnableDiffSnapshots: false,
		}
	}

INFO[0000] Called startVMM(), setting up a VMM on firecracker.sock
INFO[0000] VMM logging disabled.
INFO[0000] VMM metrics disabled.
INFO[0000] Attaching drive out.img, slot 1, root true.
2022-03-14T20:44:08.903778314 [anonymous-instance:fc_api:ERROR:src/api_server/src/parsed_request.rs:174] Received Error. Status code: 400 Bad Request. Message: The requested operation is not supported after starting the microVM.
ERRO[0000] Attach drive failed: out.img: [PUT /drives/{drive_id}][400] putGuestDriveByIdBadRequest  &{FaultMessage:The requested operation is not supported after starting the microVM.}
ERRO[0000] While attaching drive out.img, got error [PUT /drives/{drive_id}][400] putGuestDriveByIdBadRequest  &{FaultMessage:The requested operation is not supported after starting the microVM.}
WARN[0000] Failed handler "fcinit.AttachDrives": [PUT /drives/{drive_id}][400] putGuestDriveByIdBadRequest  &{FaultMessage:The requested operation is not supported after starting the microVM.}

2022-03-14T20:44:08.909516283 [anonymous-instance:main:WARN:src/devices/src/virtio/net/event_handler.rs:62] Received unknown event: ERROR from source: 30
failed to start the vm: [PUT /drives/{drive_id}][400] putGuestDriveByIdBadRequest  &{FaultMessage:The requested operation is not supported after starting the microVM.}
alex@nuc7:~$ 2022-03-14T20:44:13.072828504 [anonymous-instance:main:ERROR:src/devices/src/virtio/net/device.rs:438] Failed to write to tap: Os { code: 77, kind: Other, message: "File descriptor in bad state" }

2022-03-14T20:44:25.133210665 [anonymous-instance:main:ERROR:src/devices/src/virtio/net/device.rs:438] Failed to write to tap: Os { code: 77, kind: Other, message: "File descriptor in bad state" }
2022-03-14T20:44:28.432145169 [anonymous-instance:main:ERROR:src/devices/src/virtio/net/device.rs:438] Failed to write to tap: Os { code: 77, kind: Other, message: "File descriptor in bad state" }

A CNI adapter is being added, the snapshot is just saved to the CWD, and when running commands via curl, a similar approach worked for me.

		WithBin(firecrackerBinary).
		WithSocketPath(fcCfg.SocketPath).
		WithStdin(os.Stdin).
		WithStdout(os.Stdout).
		WithStderr(os.Stderr).
		Build(ctx)

	machineOpts = append(machineOpts, firecracker.WithProcessRunner(command))

	m, err := firecracker.NewMachine(vmmCtx, fcCfg, machineOpts...)
	if err != nil {
		fmt.Printf("failed to start the vm: %+v\n", err)
		os.Exit(1)
	}

	if err := m.Start(vmmCtx); err != nil {
		fmt.Printf("failed to start the vm: %+v\n", err)
		os.Exit(1)
	}
	defer m.StopVMM()

	log.Printf("Machine ID: %s, action: %s", mmid, action)

	if err := m.Wait(vmmCtx); err != nil {
		fmt.Printf("failed to start the vm: %+v\n", err)
		os.Exit(1)
	}

	log.Print("Machine exitied.")

}

Does this look like the test case that you ran? Any suggestions for me to try?
Alex

Superseded by #414. We can have the snapshotting feature finally!!!

@alexellis @ustiugov Sorry for the very late reply.
Our intern @sondavidb has been working on the snapshotting feature. The tests are using CNI. So I believe that CNI is working with his version.

@kzys @sondavidb great news! Thank you for letting me know. I can see that you restore the NI with the exact same configuration.
If I may ask, What backend storage do you assume for VM snapshots? Is the host expected to retrieve the whole set of entire files or would retrieving on-demand guest memory pages be possible somehow?

@sondavidb thank you for the details. I am a little confused, could you clarify what the new implementation is going to be like and which implementation is going to be deprecated?

@ustiugov Sure, the differences can be found in their snapshotting documentation, via the first two API call examples under the "Loading snapshots" header. The second example uses a snapshot_path and a mem_file_path variable, which is the implementation being used in the SDK today. This is being deprecated in favor of the format used in the first example, which uses the same snapshot_path but uses mem_backend as its second variable. This allows the user to have the option to run it similar to the current implementation and allow the kernel to handle page faults, or provide a UFFD that can have page faults delegated to it.

@sondavidb thanks for the clarification! this is good news that UFFD is supported (we published the work that showcases this approach advantages last year :) ).

@kzys Are there any plans to add support for the new mem_backend field to enable using UFFD as a backend?

Sorry. I no longer work for Amazon.


Chart key/summary

Awesome lib! I'm wondering if this library can render color coordinated keys that correlate to a chart?

@crobinson42 can you give a little more detail on what keys you'd like to see correlated, or let us know if this question has been resolved by a newer version of react-charts?
I see in the docs tooltips support color matching series natively https://react-charts.tanstack.com/examples/tooltip-options

Due to a massive overhaul and rewrite of React Charts to TypeScript and a massively upgraded public API, this issue is being bulk closed for triage. The latest version can be tested via the react-charts@beta tag. Documentation is in the process of being upgraded, but thankfully, everything is fully typed now, so you can explore the API that way for now.
If, after testing or playing with the v3 beta, you believe your issue is still not addressed or relevant, feel free to open a new issue.


Sprite sheet bundle picking support

Analogues to the sprite bundle picking support - which seems to work fine now - is there any support planned for the SpriteSheetBundle as well or should this even be working already?
What's the best way to go about this otherwise? Just add a MaterialMesh2DBundle as a child to the Entity with the SpriteSheetBundle?

I just whipped up a working TextureAtlasSpriteBackend using an implementation that's identical to SpriteBackend except with the following changes in the filter_map:
        let position = sprite_transform.translation();
        let scale = sprite_transform.compute_transform().scale;
        let half_extents = sprite
            .custom_size
            .or_else(|| {
                let texture_atlas = texture_atlases.get(handle)?;
                let texture_bounds = texture_atlas.textures.get(sprite.index)?;
                Some(texture_bounds.size())
            })
            .map(|size| size / 2.0 * scale.truncate())?;

Declaration changes include:
    texture_atlases: Res<Assets<TextureAtlas>>,
    sprites: Query<(
        Entity,
        &Handle<TextureAtlas>,
        &TextureAtlasSprite,
        &GlobalTransform,
        &ComputedVisibility,
        Option<&FocusPolicy>,
    )>,

(most likely, the SpriteBackend should be taking into account scale as well).
There's no other change; the only practical difference between a Sprite and a TextureAtlasSprite here is that the latter's bounds are taken from a TextureAtlas and not an Image.

I'm happy to include this in the sprite picking backend if you PR it!

I can do that, although what I was posted is kind of ugly copypasta. Do you have a design preference out of the following?

Add a new TextureAtlasSpriteBackend that's nearly identical to SpriteBackend except for the changes above
Update the SpriteBackend to also handle TextureAtlasSprite, i.e. by making some of the query elements Option and checking them all in the half_extents calculation
Write a "2D backend" generic system using a trait to compute the bounds or do a bounds check, since that seems to be the only thing that varies?

I used the picking mod for another example I did with the nascent vector shapes addon, and it's kind of the same story; it's circular, so there's no "bounding box", but the "bounds check" is trivial and everything else is pretty much the same. Not sure how common this is beyond the two sprite types and my toy example, though, and I don't want to overcomplicate things.

Update the SpriteBackend to also handle TextureAtlasSprite, i.e. by making some of the query elements Option and checking them all in the half_extents calculation

This option seems the most straightforward while avoiding code duplication. Writing a generic system seems like more effort with unclear benefit.

This is now supported and can be tested in the sprite example.
https://github.com/aevyrie/bevy_mod_picking/blob/8f78621a6c03b73c0b896dc65af8b151d5e01bcc/examples/sprite.rs#L133
https://github.com/aevyrie/bevy_mod_picking/assets/2632925/4027227b-07fc-4708-8fda-19bf86fb633a


Right Info Panel display working dir

Is your feature request related to a problem? Please describe.
No.
Describe the solution you'd like
Right Info Panel display working dir. Just like docker inspect <container_id> command output WorkingDir filed.
Describe alternatives you've considered
None.
Additional context
None.

Duplicate of #468


Ensure that the package-name and package-type in your workflow file match exactly with the package you’re trying to delete.

I think the issue is that https://github.com/warm-metal/csi-driver-image/blob/a2e26ec4c89837d672e8e638eab5c39eb056df0f/.github/workflows/images-build-and-push.yaml this workflow needs additional permissions
permissions:
  packages: write

I think the issue is that https://github.com/warm-metal/csi-driver-image/blob/a2e26ec4c89837d672e8e638eab5c39eb056df0f/.github/workflows/images-build-and-push.yaml this workflow needs additional permissions
permissions:
  packages: write

If the issue is with the permissions lacking in the workflow, I wonder how did the cleanup run successfully on another fork.

Ensure that the package-name and package-type in your workflow file match exactly with the package you’re trying to delete.

@HarjobandeepSingh it is using the same name already.

See this comment - https://github.com/warm-metal/csi-driver-image/pull/117#issuecomment-1902686625
@mugdha-adhav Please see this action run https://github.com/warm-metal/csi-driver-image/actions/runs/7602485716/job/20703096374.
The package was created successfully and automatically made public - https://github.com/warm-metal/csi-driver-image/pkgs/container/csi-driver-image%2Fdevcontainer
In any case, I'm positive just adding that permissions should do away with the error in a fork.


fix desiutil import errors

While activating RTD for surveysim, I discovered that the doc build was throwing errors very similar to desihub/desisurvey#64.  The fix is also basically the same.

See http://surveysim.readthedocs.io/en/rtd-fixes/, for the documentation built on this branch.

Changes Unknown when pulling 450f5b9abf6e7f4922c8343247e18b0e11210e37 on rtd-fixes into ** on master**.

Changes Unknown when pulling 450f5b9abf6e7f4922c8343247e18b0e11210e37 on rtd-fixes into ** on master**.

Changes Unknown when pulling 450f5b9abf6e7f4922c8343247e18b0e11210e37 on rtd-fixes into ** on master**.

This looks good.  The datamodel pages are now obsolete, but that's a separate issue #47 so this is ready to merge.


what is the language -l  when I want to use Chinese pdf?

I used it like this
python process.py a.png -l Chinese -xml a.xml
but failed

The list of supported recognition languages is here https://ocrsdk.com/documentation/specifications/recognition-languages/

thanks


Missing tryLock with leaseTime option for IMap

Currently, client supports tryLock with timeToWait or no time restriction at all for IMap.
Per implementation, setting leaseTime is also possible and seems like it's missing in the client impl. It would be useful to include that in cpp client as well.

Many thanks for your contributions @RikeVoltz!! :)

I am glad to help and thank you for this great project and for the opportunity to participate in its development, @burakcelebi  :)

Hey @RikeVoltz, we cannot make it without the fantastic Hazelcast community members like you! 🥇🥇🥇
Also, many thanks to our lead C++ Engineer @ihsandemir for his support throughout the process. 💯


abuild: 3.7.0 -> 3.9.0

Description of changes
There is no changelog but the commit log should be enough
most importantly this fixes a serious bug in abuild checksum that causes it to create a new sha512sums= entry instead of updating the already existing one.
see this commit for an example.

Things done

updated version from 3.7.0 to 3.9.0
updated rev to use version directly instead of v${version}
added scdoc to nativeBuildInputs

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

Testing was done by using it while contributing to Alpine Linux, in the case I used my overlay that overrode the original nixpkgs with effectively the same changes.

Hm somehow it doesn't work for me, I only get exit code 127 :(

Yep you're right apk-tools is missing. Should we wrap it as a dependency with:
wrapProgram $out/bin/abuild \
  --prefix PATH : ${lib.makeBinPath [ apk-tools ]}

?

Yes but it is not only abuild is a shellscript provided.
I think this should cover all Shellscripts provided by the abuild package
for prog in abuild abuild-keygen abuild-sign newapkbuild abump apkgrel buildlab checkapk; do
    wrapProgram $out/bin/$prog \
       --prefix PATH : ${lib.makeBinPath [ apk-tools ]}
done

The apkbuild-cpan apkbuild-pypi and apkbuild-gem-resolver are perl, python and ruby scripts respectively and they have their own dependencies as noted in abuild's APKBUILD, we might want to look into those at a later date, I really want 3.9.0 to get in to fix a serious bug in the checksum subcommand

I took a less superficial look into the apkbuild-{cpan,pypi,gem-resolver} scripts and they literally use a /usr/bin/<INTERPRETER> shebang, they are completely non-functional on NixOS since they have been shipped(?)

I took a less superficial look into the apkbuild-{cpan,pypi,gem-resolver} scripts and they literally use a /usr/bin/<INTERPRETER> shebang, they are completely non-functional on NixOS since they have been shipped(?)

do we have to run patchShebangs especially for these files or is this done automatically as soon we put perl into buildInputs?

I took a less superficial look into the apkbuild-{cpan,pypi,gem-resolver} scripts and they literally use a /usr/bin/<INTERPRETER> shebang, they are completely non-functional on NixOS since they have been shipped(?)

do we have to run patchShebangs especially for these files or is this done automatically as soon we put perl into buildInputs? Or I guess we'll have to package the perl and ruby scripts using their own packaging function?

adding perl to buildInputs makes it auto-patch the shebangs, I'm looking into the proper way (NixOS documentation is "suboptimal" in this regard) of adding the perl packages to the shell equivalent of PATH

Pushed a new version that uses the following in buildInputs:
    # for $out/bin/apkbuild-cpan and $out/bin/apkbuild-pypi
    (perl.withPackages (ps: with ps; [
      LWP
      JSON
      ModuleBuildTiny
      LWPProtocolHttps
      IPCSystemSimple
    ]))

the perl that is called by the autopatch has the packages available and it should cover them all (I have merely added the ones mentioned in the dependencies of the Alpine Linux APKBUILD subpackage).

This is very messy:
Many of the scripts (shell, perl, ruby) call into binaries from apk-tools and many of them also call into eachother (many call into abuild but some also call into abuild-tar, etc)

who do we ask to get this merged ?

Thank you both for the contribution!


Export the estimated trajectories?

Is there an example, or some part in the documentation that explains how to export estimated trajectories after using localization algorithms. I know that "traj" gives the actual trajectories generated by agent mobility. I can't find out how, after performing localization, can I get the estimated trajectories based on the localization algorithms. is that even an option? I suppose it is.
Thanks,
Mahi

Dear Mahi,
I think this important feature is not yet implemented. An estimated trajectory should also be a trajectotry.
I you make some progress on that please propose a pull request.
Best regards
Bernard


Remove ext-json from required in composer.json

Extension JSON is part of PHP core since version 8, there is no need to specify it in the composer.json file any longer.

@tuqqu This looks fine, but just curious: how did you find out about this?

:) I was going through the changelog for PHP8 when noticed there was a dedicated RFC for this.

Thanks, attentive! Since this change does not have any actual substance, I won't create a tag for this.

Note: even if it is part of core (and bundled with it), it is still a dependency.

@Ocramius And therefore it should be readded as a dependency?

Maybe: no strong feelings though.
Adding maglnet/composer-require-checker would expose this and other hidden
dependencies.
On Mon, Jun 21, 2021, 12:19 Frederik Bosch @.***> wrote:

@Ocramius https://github.com/Ocramius And therefore it should be
readded as a dependency?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/moneyphp/money/pull/653#issuecomment-864916836, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AABFVEA4MC6M4YR3ORQCY23TT4G3PANCNFSM45VE2VKQ
.

Created issue #658 for this, thanks for the suggestion.


Omit init containers from limitrange default request calculations

Changes
This commit modifies how resource requirements are adjusted based on LimitRanges present
in a namespace. Prior to this commit, the container requests for a resource
were determined by dividing the default requests specified in a LimitRange by the number of
app containers plus 1 (to represent the init container), taking the maximum of this value
and the minimum request specified in the LimitRange, and applying this value to all containers.
However, Kubernetes does not sum init container resource requests to app container resource requests
when determining the pod's effective resource requests, as described here. Instead, it takes the larger of
the maximum init container resource requests and the sum of app container resource requests.
As a result, the appropriate behavior is to split the default requests only among app containers, and
to apply the default requests directly to init containers. This commit implements that behavior.
/kind bug
Submitter Checklist
As the author of this PR, please check off the items in this checklist:

n/a Docs included if any changes are user facing
[x] Tests included if any functionality added or changed
[x] Follows the commit message standard
[x] Meets the Tekton contributor standards (including
functionality, content, code)
[x] Release notes block below has been filled in
(if there are no user facing changes, use release note "NONE")

Release Notes
Omit init containers from limitrange default request calculations

/assign vdemeester

/test pull-tekton-pipeline-go-coverage
/test pull-tekton-pipeline-alpha-integration-tests

cc @abayer

/lgtm

/retest

/test pull-tekton-pipeline-alpha-integration-tests


whisper已经下载到本地了，就是找不到加载位置

'(MaxRetryError("HTTPSConnectionPool(host='huggingface.co', port=443): Max retries exceeded with url: /openai/whisper-large-v2/resolve/main/config.json (Caused by ConnectTimeoutError(<urllib3.connection.HTTPSConnection object at 0x7fd9399957b0>, 'Connection to huggingface.co timed out. (connect timeout=10)'))"), '(Request ID: 7b68228e-e6a6-4ecd-bc7e-3affc92e3ac3)')' thrown while requesting HEAD https://huggingface.co/openai/whisper-large-v2/resolve/main/config.json
Traceback (most recent call last):
File "/root/anaconda3/envs/llasm/lib/python3.10/site-packages/transformers/utils/hub.py", line 417, in cached_file
resolved_file = hf_hub_download(
File "/root/anaconda3/envs/llasm/lib/python3.10/site-packages/huggingface_hub/utils/_validators.py", line 118, in _inner_fn
return fn(*args, **kwargs)
File "/root/anaconda3/envs/llasm/lib/python3.10/site-packages/huggingface_hub/file_download.py", line 1291, in hf_hub_download
raise LocalEntryNotFoundError(
huggingface_hub.utils._errors.LocalEntryNotFoundError: Connection error, and we cannot find the requested files in the disk cache. Please try again or make sure your Internet connection is on.
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/work/liukai/LLaSM/infer.py", line 122, in
main(args)
File "/work/liukai/LLaSM/infer.py", line 46, in main
model = LlaaaLlamaForCausalLM.from_pretrained(
File "/root/anaconda3/envs/llasm/lib/python3.10/site-packages/transformers/modeling_utils.py", line 2700, in from_pretrained
model = cls(config, *model_args, **model_kwargs)
File "/work/liukai/LLaSM/llasm.py", line 160, in init
self.model = LlaaaLlamaModel(config)
File "/work/liukai/LLaSM/llasm.py", line 41, in init
self.audio_tower = [load_whisper(config.mm_audio_tower)]
File "/work/liukai/LLaSM/llasm.py", line 28, in load_whisper
model = WhisperModel.from_pretrained(audio_tower_name)
File "/root/anaconda3/envs/llasm/lib/python3.10/site-packages/transformers/modeling_utils.py", line 2325, in from_pretrained
config, model_kwargs = cls.config_class.from_pretrained(
File "/root/anaconda3/envs/llasm/lib/python3.10/site-packages/transformers/configuration_utils.py", line 590, in from_pretrained
config_dict, kwargs = cls.get_config_dict(pretrained_model_name_or_path, **kwargs)
File "/root/anaconda3/envs/llasm/lib/python3.10/site-packages/transformers/configuration_utils.py", line 617, in get_config_dict
config_dict, kwargs = cls._get_config_dict(pretrained_model_name_or_path, **kwargs)
File "/root/anaconda3/envs/llasm/lib/python3.10/site-packages/transformers/configuration_utils.py", line 672, in _get_config_dict
resolved_config_file = cached_file(
File "/root/anaconda3/envs/llasm/lib/python3.10/site-packages/transformers/utils/hub.py", line 452, in cached_file
raise EnvironmentError(
OSError: We couldn't connect to 'https://huggingface.co' to load this file, couldn't find it in the cached files and it looks like openai/whisper-large-v2 is not the path to a directory containing a file named config.json.
Checkout your internet connection or see how to run the library in offline mode at 'https://huggingface.co/docs/transformers/installation#offline-mode'.

我也遇到这问题了，请问你解决了吗

我解决了，你仔细看看报错的日志，有一个py文件中把路径写错了，你对应的改一下，改成你的路径就行了。

请问楼主部署成功这个项目了吗，我运行提示我CUDA版本过低了，我是11.7的版本，请问最低要求版本是多少啊

我的是CUDA 12.0的成功了

'(MaxRetryError("HTTPSConnectionPool(host='huggingface.co', port=443): Max retries exceeded with url: /openai/whisper-large-v2/resolve/main/config.json (Caused by ConnectTimeoutError(<urllib3.connection.HTTPSConnection object at 0x7fd9399957b0>, 'Connection to huggingface.co timed out. (connect timeout=10)'))"), '(Request ID: 7b68228e-e6a6-4ecd-bc7e-3affc92e3ac3)')' thrown while requesting HEAD https://huggingface.co/openai/whisper-large-v2/resolve/main/config.json Traceback (most recent call last): File "/root/anaconda3/envs/llasm/lib/python3.10/site-packages/transformers/utils/hub.py", line 417, in cached_file resolved_file = hf_hub_download( File "/root/anaconda3/envs/llasm/lib/python3.10/site-packages/huggingface_hub/utils/_validators.py", line 118, in _inner_fn return fn(*args, **kwargs) File "/root/anaconda3/envs/llasm/lib/python3.10/site-packages/huggingface_hub/file_download.py", line 1291, in hf_hub_download raise LocalEntryNotFoundError( huggingface_hub.utils._errors.LocalEntryNotFoundError: Connection error, and we cannot find the requested files in the disk cache. Please try again or make sure your Internet connection is on.
During handling of the above exception, another exception occurred:
Traceback (most recent call last): File "/work/liukai/LLaSM/infer.py", line 122, in main(args) File "/work/liukai/LLaSM/infer.py", line 46, in main model = LlaaaLlamaForCausalLM.from_pretrained( File "/root/anaconda3/envs/llasm/lib/python3.10/site-packages/transformers/modeling_utils.py", line 2700, in from_pretrained model = cls(config, *model_args, **model_kwargs) File "/work/liukai/LLaSM/llasm.py", line 160, in init self.model = LlaaaLlamaModel(config) File "/work/liukai/LLaSM/llasm.py", line 41, in init self.audio_tower = [load_whisper(config.mm_audio_tower)] File "/work/liukai/LLaSM/llasm.py", line 28, in load_whisper model = WhisperModel.from_pretrained(audio_tower_name) File "/root/anaconda3/envs/llasm/lib/python3.10/site-packages/transformers/modeling_utils.py", line 2325, in from_pretrained config, model_kwargs = cls.config_class.from_pretrained( File "/root/anaconda3/envs/llasm/lib/python3.10/site-packages/transformers/configuration_utils.py", line 590, in from_pretrained config_dict, kwargs = cls.get_config_dict(pretrained_model_name_or_path, **kwargs) File "/root/anaconda3/envs/llasm/lib/python3.10/site-packages/transformers/configuration_utils.py", line 617, in get_config_dict config_dict, kwargs = cls._get_config_dict(pretrained_model_name_or_path, **kwargs) File "/root/anaconda3/envs/llasm/lib/python3.10/site-packages/transformers/configuration_utils.py", line 672, in _get_config_dict resolved_config_file = cached_file( File "/root/anaconda3/envs/llasm/lib/python3.10/site-packages/transformers/utils/hub.py", line 452, in cached_file raise EnvironmentError( OSError: We couldn't connect to 'https://huggingface.co' to load this file, couldn't find it in the cached files and it looks like openai/whisper-large-v2 is not the path to a directory containing a file named config.json. Checkout your internet connection or see how to run the library in offline mode at 'https://huggingface.co/docs/transformers/installation#offline-mode'.

vpn开全局可以解决

Refe
请问，是哪行代码 的路径错了，


Using GPG on V4, the gpg importer will always take 3 minutes

Description:
When configuring and using setup-java on v4 with gpg parameters, the step that imports the gpg key will always take 3 minutes
Task version:
V4
Platform:

[ X] Ubuntu
[ ] macOS
[ ] Windows

Runner type:

[ X] Hosted
[ ] Self-hosted

Repro steps:
Create a working GPG setup using setup-java on v3. Update the version to v4. The task will now take 3 minutes.
Working
       - name: Set up Java
        uses: actions/setup-java@v3
        with:
          java-version: ${{ matrix.java-version }}
          distribution: 'oracle'
          #server-id: github_token
          #settings-path: ${{ github.workspace }}
          cache: 'maven'
          gpg-private-key: ${{ secrets.GPG_PRIVATE_KEY }}
          gpg-passphrase: GPG_PASSPHRASE

Affected
      - name: Set up Java
        uses: actions/setup-java@v4
        with:
          java-version: ${{ matrix.java-version }}
          distribution: 'oracle'
          #server-id: github_token
          #settings-path: ${{ github.workspace }}
          cache: 'maven'
          gpg-private-key: ${{ secrets.GPG_PRIVATE_KEY }}
          gpg-passphrase: secrets.GPG_PASSPHRASE

Expected behavior:
The same as in V3, when the task is complete the job must continue immediately.
Actual behavior:
The step waits for 3 minutes on any workflow for the task to complete

Hello @GedMarc
Thank you for creating this issue. We will investigate it and get back to you as soon as we have some feedback.

Hello @GedMarc  👋 ,
We've released a new version of setup-java (v4.2.0), and the v4 tag has been updated accordingly. This update includes a version bump for actions/http-client to 2.2.1. We anticipate that this change might address the delay issue with the GPG importer.
Could you please confirm if it resolves your issue?

Hey @GedMarc, Just checking in to see if your issue has been addressed with the recent setup-java update (v4.2.0). Could you please update us on this? Thank you in advance for your update!

Issue resolved with version 4.2.0 (y)
Whooop 👯


Add PMT dark count simulation

This PR tries to add PMT dark counts to fuse.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

46 of 68 (67.65%)  changed or added relevant lines in 5 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.04%) to 67.698%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

fuse/plugins/truth_information/records_truth.py
1
3
33.33%

fuse/plugins/pmt_and_daq/dark_counts.py
41
61
67.21%

Totals

Change from base Build<PHONE_NUMBER>:
-0.04%

Covered Lines:
1859

Relevant Lines:
2746

💛  - Coveralls


replace set() declarations with set literals

given that we removed 2.6 from the menu, we can now start refactoring set declarations to use more efficient set literals.
Instead of set(('item1', 'item2')) we will use {item1,item2} syntax

Looking forward to this.


ARROW-1336: [C++] Add arrow::schema factory function, simply some awkward constructors

cc @cpcloud
I'm not sure why Appveyor is upset

Have you considered naming it make_schema? That'd go well with std::make_unique, std::make_shared, std::make_pair, etc; then you can also get rid of ::arrow:: (I assume that was to avoid name clashes).

@pcmoritz I did think of that; this is more consistent with functions like arrow::field, arrow::timestamp, etc. I would rather change everything than do something inconsistent, so perhaps we can revisit if there are strong feelings about the naming style of these factory functions
I wonder what is going on with the segfault in Travis CI, we should try to figure that out (I have seen it before): opned ARROW-1338


Cython 3.1+ fixes

This fixes the errors that came up during Cython3.1a testing. I'm not a Cython expert by any means, so let me know if there is a better way to handle any of these. Do you want to add a test/workflow for upcoming Cython releases?
Test with this nightly wheel release install locally:
pip install --upgrade --pre --only-binary :all: -i https://pypi.anaconda.org/scientific-python-nightly-wheels/simple cython numpy
pip install .
python -m pytest

[x] Closes #1451

Do you want to add a test/workflow for upcoming Cython releases?

Yes, that change is welcome.

Do you want to add a test/workflow for upcoming Cython releases?

Yes, that change is welcome.

I added it to the PROJ_latest workflow to just install the latest Cython there as well. Let me know if you want it as an isolated workflow instead.

Thanks @greglucas 👍


Renaming of tracked files ignored if only case is changed

When a tracked file is renamed so that only case of some characters is changed e.g. 'file' => 'File',
git does not detect these changes.  to unstage)

	new file:   file

$ mv file File
$ git status
On branch master

Initial commit

Changes to be committed:
  (use "git rm --cached <file>..." to unstage)

	new file:   file

This issue isn't related to the website about the project.
However, you may want to look at Git: File Rename on Stack Overflow and see if that applies in your case.


appGenerator is called instead actionsGenerator

 $ yo react-reflux:actions api                                                                                [17:27:53]

     _-----_
    |       |    .--------------------------.
    |--(o)--|    | Welcome to the excellent |
   `---------´   |  React Reflux generator! |
    ( _´U`_ )    '--------------------------'
    /___A___\
     |  ~  |
   __'.___.'__
 ´   `  |° ´ Y `

Out of the box I include ReactJS, React-Router, ReFlux, jQuery.
? What is the project's name? (api)

First of all, nice work :+1:
But it seems that both yo react-reflux:actions actionName and singular version: yo react-reflux:action trigger app generator instead of actions generator.

Hi!
I just tried to run the actions generator with the latest version and it seems to work OK. Here is the output:
$ yo react-reflux:actions api
   create app/scripts/actions/ApiActions.js

Which version of the generator and yeoman are you using?

Hey,
<EMAIL_ADDRESS>1.4.6```
```node --version
v0.12.2

strange..

Hi,
It works well for me also.
The only difference I have is:

node --version
v0.10.29

Re,
I tested with node v0.12.2, and I have the same issue as you !
So I confirm the issue with latest node version. Need a fix.

Interesting, I've upgraded my node version (it was v0.12.0 before) and it still seems to work for me.
$ yo --version
1.4.6

$ node --version
v0.12.2

$ npm --version
2.7.5

$ yo react-reflux:actions api
   create app/scripts/actions/ApiActions.js

I am using OS X Yosemite 10.10.3 so maybe thats the difference. Which OS-es are you using?

Windows 7, I will try to investigate on my side. Perhaps it is a bug of Node.js for Windows...

I tried it on windows and indeed it's not working. Will try to figure out whats the problem.

I'm even using OS X 10.10.3.
Thanks for your effort

I tested again with the master branch code, and it works now.
Seems it occurs randomly! Very strange...

I re tested with latest release, and yo react-reflux:actions still doesn't work (see below).
The future release will fix the issue if we are lucky enough...   :-)
D:\Projets\workspaces\test>yo react-reflux:component dashboard
create app\scripts\components\dashboard.jsx
D:\Projets\workspaces\test>yo react-reflux:store user
create app\scripts\stores\UserStore.js
D:\Projets\workspaces\test>yo react-reflux:actions user
 _-----_
|       |    .--------------------------.
|--(o)--|    | Welcome to the excellent |

---------´   |  React Reflux generator! |     ( _´U_ )    '--------------------------'
/A
|  ~  |
'..'_
´    |° ´ Y
Out of the box I include ReactJS, React-Router, ReFlux, jQuery.
? What is the project's name? (user)

Really interesting. Same thing, on the master branch it works ok.

Closing for now. Issue seems to be resolved with the new version.

Still got this issue with the latest versions. Fixed it by manually adding the missing "actions" folder in my AppData\Roaming\npm\node_modules\generator-react-reflux folder.
Maybe related to the package.json that mentions the following :
  ...
  "files": [
    "app",
    "component",
    "store"
  ],
  ...

Shouldn't we get "actions" as well in this array ?

Yes, good catch this was the issue. I was testing locally on windows using npm link and it worked, so I assumed everything was ok. Will update immediately.


[Feat] add a google maps button

Description
google maps button with effect.
Screenshots
No response
Checklist

[X] I have checked the existing issues
[X] I have read the Contributing Guidelines
[X] I'm a GSSoC'24-Extd contributor
[X] I'm a Hacktoberfest'24 contributor
[X] I am willing to work on this issue (optional)

@beRajeevKumar can you please assign me the issues

@beRajeevKumar remainder ./

@beRajeevKumar assign me this


Create a Readme

A readme should be created to help people understand the project

I would like to work on it.

okay


[Bug]: App stopped working on Mi8

Summary
App stopped working on Mi8. It was working before
Steps to reproduce

Start app
Observe start screen
Nothing happens

Expected behaviour
App should open
Actual behaviour
Start screen is showing and nothing happens
Device name
Mi8
Android version
10
Commons app version
4.2.1
Device logs
No response
Screen-shots
No response
Would you like to work on the issue?
None

Close. I didn't understood interface

Would it help if we add a call to action on the first empty screen?
For instance "Welcome to Commons! Upload your first picture by tarpini the + sign"

Would it help if we add a call to action on the first empty screen?
For instance "Welcome to Commons! Upload your first picture by tarpini the + sign"

@nicolas-raoul Yeah I think that enhancement is long pending. Some discussion was already going on here and these designs seem to be good enough to be implemented. What are your thoughts?


Change JSON lib from Boon to Jackson

Intro
The initial motive for removing the dependency to Boon was because it relies on the Unsafe class and there is no plan to remove that. This makes it impossible to upgrade to Java 9+, if the need arise in the future.
During the development it also appeared that Boon is not the fastest JSON serialization/deserialization library anymore and it suffers from minor issues (more on that later).
To replace Boon, Jackson was chosen because it is a fast, well maintained, feature-rich and widely used JSON serialization/deserialization library.
This PR first isolates the dependency to the library to a single package, io.warp10.json, by providing a single class io.warp10.json.JsonUtils with methods to serialize/deserialize to/from JSON.
Next, the dependency has been changed to the last version (2.10.2) of jackson-databind to be able to easily update the library as the API slightly changed in 2.10.
These changes impacted the behavior and results as listed below:
Serialization
Type by type differences

Bitset: serialized to null, no change.
Boolean: no change.
byte[]: serialized to base64 instead of null.
Counter (AtomicLong): serialized like Long instead of its String representation.
Double: no change.
GTSEncoder: added missing lastActivity. Except that, no change.
GeoShape: no change.
GTS: no change.
List: no change.
Long: no change.
Macro: no change.
Map: null keys are serialized as "null" instead of null. This makes the JSON valid.
Matrix (RealMatrix): serialized to null, no change.
NamedWarpScriptFunction: no change.
null: no change.
PFont, PGraphics, PImage, PShape: serialized to null, no change.
Set: serialized as a list, was previously null.
String: Unicode escaping use capital letter (ie \u00C3 instead of \u00c3). Except that, no change.
Vector (ArrayRealVector): serialized to null, no change.
VList (Vector): no change.

->JSON
->JSON now uses the exact same function as the Egress output to generate JSON and the call to validate has been removed.
This means:

All the types handled above are also handled by ->JSON instead of only List, Map, Number and Boolean.
If there is a cycle in the structure, this is handled by Jackson with a StackOverflowError.

On top of that, as it was pretty easy to reach a OOM with ->JSON there is now a limit on the size of a generated JSON only for ->JSON. The size limit can be changed in the conf with warpscript.maxjson and warpscript.maxjson.hard and in an authenticated WarpScript stack using MAXJSON.
Custom serialization
Like SNAPSHOT, it is possible to register custom serializers for JSON with io.warp10.json.JsonUtils#addEncoder.
Deserialization
Deserialization with Boon suffer from a number of issues which has been fixed in this PR:

Boolean: object type is now Boolean instead of ValueContainer.
Double: object type is now Double instead of NumberValue. Infinity and NaN are handled by Jackson contrary to Boon.
List: no change.
Long: object type is now Double instead of NumberValue.
Map: no change.
null: object is now really null instead of a ValueContainer instance.
String: no change.
String representing a ISO8601 date in a List: was converted to a Date with Boon, now correctly deserialized as a String.

For the serialization, these choices are open for discussion, comments are welcome:

byte[] serialized as base64
Set serialized as list
ArrayRealVector and RealMatrix not serialized


nargo codegen-verifier only produces UltraVerificationKey and not UltraVerifier

Aim
After upgrading from Noir 0.8.0 to Noir 0.19.2 ,  I tried generating a solidity verifier for my circuit.
Expected Behavior
A working solidity program with a UltraVerifier contract defined.
Bug
I successfully ran nargo compile. Running nargo codegen-verifier also returns [test] Contract successfully created and located at circuits/test/contract/test/plonk_vk.sol ; but the resulting contract (attached) is missing the verifier parts.
plonk_vk.sol.txt
To Reproduce

Install nargo via the nix instructions ( or include nargo via a nix flake)
Copy the default acvm-backend-barretenberg backend into another backend folder, nargo backend use that folder (don't know if this causes the bug, but I have to do so because I am using a wrapped backend)
nargo init
nargo codegen-verifier

Installation Method
Compiled from source
Nargo Version
nargo 0.17.0 (git version hash: 7de37c6935571c2865eca7ce11da0038ff735b2f, is dirty: false)
Additional Context
I am running NixOS so I had to wrap the backend in script to provide it the libraries required to run. I can imagine this /might/ be a problem if this binary downloads more binaries that it then tries to execute, or has other hidden dependencies.
Would you like to submit a PR for this Issue?
No
Support Needs
No response

Copy the default acvm-backend-barretenberg backend into another backend folder, nargo backend use that folder (don't know if this causes the bug, but I have to do so because I am using a wrapped backend)

Hey @Cryptuude, this step is the issue. The BaseUltraVerifier and UltraVerifier contracts should really be provided by the backend but bb actually only gives us the verification key library. We've then special cased the default backend which is named acvm-backend-barretenberg so that nargo injects those contracts itself.
Backends with a different name are assumed to not be bb so we don't perform any of the special-casing in that scenario. You should be able to place your patched binary back into the acvm-backend-barretenberg directory which will get you a working contract again, the only issue is that you'll automatically download a non-patched version to replace it if we bump the expected bb version.
See here for where we have this special case.
https://github.com/noir-lang/noir/blob/a22898d68712192a6ad014986f11f1f55ca9a2c1/tooling/nargo_cli/src/cli/codegen_verifier_cmd.rs#L89-L92
Ideally bb should be updated to return the full contract file but it's competing with other priorities.


When training, how should I do with groundtruth? such as normalization

hello, I am trying to recreate your results on the NYU_depth dataset with Tensorflow, I use your published test code directly as a build network. When training, I found the value of the network output is not between 0 and 1. So I don't know deal with groundtruth to calculate loss. Can you help me to solve this problem?
Thank you.

We predict depth in meters. No normalization needed.

@chrirupp when training, I am sure the pixel value of network input(RGB) is between 0 and 255. Is the pixel value of network input(depthmap)  between 0 and 255?

input is between 0 and 255, output between 0 meters and 10 meters


Metadata keyspace collision with two different copies of a stack

If you create two copies of a stack with the service names the same, you can not traverse /service/. You end up with the last service created it appears.
To reproduce create two stacks from the same docker-compose.yml file. Then query metadata from inside one of the containers for the service name.

Tested with latest build from master:
When there are services with same name that exists across multiple stacks, http://rancher-metadata/latest/services/ will still return one of the services with the matched name. But now we have a way to uniquely fetch the service details by name using http://rancher-metadata/latest/stacks//services/.
In this case I have a service named - "test1" in 2 stacks -> "Default" and "new".
root@a654ff2e44d7:/# wget --header="Accept:application/json" http://rancher-meta
data/latest/stacks/new/services/test1

{"create_index":4,"expose":[],"external_ips":[],"fqdn":null,"hostname":null,"kin
d":"service","labels":{"io.rancher.container.pull_image":"always"},"links":{},"m
etadata":{},"name":"test1","ports":[],"scale":3,"sidekicks":[],"stack_name":"Default"}

root@a654ff2e44d7:/# wget --header="Accept:application/json" http://rancher-meta
data/latest/stacks/new/services/test1

{"create_index":1,"expose":[],"external_ips":[],"fqdn":null,"hostname":null,"kin
d":"service","labels":{"io.rancher.container.pull_image":"always"},"links":{},"m
etadata":{},"name":"test1","ports":[],"scale":1,"sidekicks":[],"stack_name":"new"}


downloadable workflow for off-line multi animal tracking

Is there a downloadable workflow available for multi-animal off-line tracking?
Thank you!

Hi there, inside of the multi-animal tracking free-swimming example folder, you will see the multi-animal-tracking.bonsai workflow, which you can download and use for offline tracking.


gdal_retile.py ERROR 1: The transformation is already "north up" or a transformation between pixel/line and georeferenced coordinates cannot be computed for TEMP.

When running command
+ gdal_retile.py -levels 1 -tileIndex 2019-Boucherville-13225474-13410695_tile.shp -tileIndexField Location -ps 128 128 -targetDir /tmp/test-jpg-2/test-jpg/2019-Boucherville-13225474-13410695_tile /tmp/test-jpg-2/test-jpg/2019-Boucherville-13225474-13410695_tile.jpg
There are error messages :

0...10...20...30...40...50...60...70...80...90...100 - done.
Warning 1: Field Location of width 256 truncated to 254.
ERROR 1: The transformation is already "north up" or a transformation between pixel/line and georeferenced coordinates cannot be computed for TEMP. There is no affine transformation and no GCPs. Specify transformation option SRC_METHOD=NO_GEOTRANSFORM to bypass this check.
Reprojection failed for /tmp/test-jpg-2/test-jpg/2019-Boucherville-13225474-13410695_tile/1/2019-Boucherville-13225474-13410695_tile_1_1.tif, error 3

They can be ignored, that does not prevent the command to successfully create the tiles and shapefile.


Add support for command line options

Makes it easy to call the ripper in an non-interactive environment (i.e. a script). Picked up python just for this, forgive me if the code isn't the best.

@scoliono Would you please review my changes

Sorry for the late response. I could have sworn I came back for code review at some point and your account had totally vanished.
Just fixed a couple small things and merged.

You didn't imagine things, indeed my account was banned for a few weeks until I appealed.


ValueError: Invalid service account certificate. Certificate must contain a "type" field set to "service_account".

[READ] Step 1: Are you in the right place?

For issues or feature requests related to the code in this repository
file a Github issue.

If this is a feature request make sure the issue title starts with "FR:".

For general technical questions, post a question on StackOverflow
with the firebase tag.
For general Firebase discussion, use the firebase-talk
google group.
For help troubleshooting your application that does not fall under one
of the above categories, reach out to the personalized
Firebase support channel.

[REQUIRED] Step 2: Describe your environment

Operating System version: Arch Linux kernel 4.13.11-1-ARCH
Firebase SDK version: 2.5.0
Library version: 2.50
Firebase Product: database

[REQUIRED] Step 3: Describe the problem
Steps to reproduce:
I downloaded the default google-services.json file from my project's Firebase console.
Then I have the following error:
ValueError: Invalid service account certificate. Certificate must contain a "type" field set to "service_account".
Relevant Code:
import firebase_admin
from firebase_admin import db
from firebase_admin import credentials

cred = credentials.Certificate('google-services.json')
firebase_admin.initialize_app(cred)

The error message states what the problem is. google-services.json is not a service account certificate. You have to download the service account certificate by going to the Settings >  Service Accounts tab, and then clicking on the Generate New Private Key button.
https://firebase.google.com/docs/admin/setup#add_firebase_to_your_app


chore: add codeql.yml

Codecov Report

Merging #41 (77509fc) into master (0d214cb) will not change coverage.
The diff coverage is n/a.

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

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
@@            Coverage Diff            @@
##            master       #41   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files            1         1
  Lines           38        38
=========================================
  Hits            38        38

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


How can change splash background?

How can change splash background?

I added this feature in this release.
You can set the background-color property to any hex colors that you want.

can set a background image?

no!

but in the future...


yarn or npm

This repository contains both yarn.lock and package-lock.json. Which file are contributors supposed to update in Pull Requests?

@jorrit yarn please. I'll sort this out when i have time


util: remove kubernetes csi prefixed parameters

remove kubernetes csi prefixed parameters from the volumeContext as we dont want to store it in the PV VolumeAttributes.
updates: #2835
Signed-off-by: Madhu Rajanna<EMAIL_ADDRESS>

@Madhu-1 I hope the below values won't be removed
// PV metadata keys
pvcNameKey      = "csi.storage.k8s.io/pvc/name"
pcNamespaceKey = "csi.storage.k8s.io/pvc/namespace"
pvNameKey       = "csi.storage.k8s.io/pv/name"

// snapshot metadata keys
volSnapNameKey        = "csi.storage.k8s.io/volumesnapshot/name"
volSnapNamespaceKey   = "csi.storage.k8s.io/volumesnapshot/namespace"
volSnapContentNameKey = "csi.storage.k8s.io/volumesnapshotcontent/name"

https://github.com/ceph/ceph-csi/pull/2898

@Madhu-1 I hope the below values won't be removed
// PV metadata keys
pvcNameKey      = "csi.storage.k8s.io/pvc/name"
pcNamespaceKey = "csi.storage.k8s.io/pvc/namespace"
pvNameKey       = "csi.storage.k8s.io/pv/name"

// snapshot metadata keys
volSnapNameKey        = "csi.storage.k8s.io/volumesnapshot/name"
volSnapNamespaceKey   = "csi.storage.k8s.io/volumesnapshot/namespace"
volSnapContentNameKey = "csi.storage.k8s.io/volumesnapshotcontent/name"

#2898

This is only for PVC not for snapshot. Yes it will be removed. All keys starting with csi.storage.k8s.io will be removed from the volumeAttributes.

This is only for PVC not for snapshot. Yes it will be removed. All keys starting with csi.storage.k8s.io will be removed from the volumeAttributes.

This will affect the PR https://github.com/ceph/ceph-csi/pull/2898
Why do we want to do this?

This is only for PVC not for snapshot. Yes it will be removed. All keys starting with csi.storage.k8s.io will be removed from the volumeAttributes.

This will affect the PR #2898 Why do we want to do this?

How it will be affected?

How it will be affected?

As you know, the mentioned PR tries to read the details of PV and snapshot from the volume attributes, If you think this won't affect, I doubt I missing something.

How it will be affected?

As you know, the mentioned PR tries to read the details of PV and snapshot from the volume attributes, If you think this won't affect, I doubt I missing something.

This will not affect the PR you are working on looks like it affect the encryption as PVC Namespace is required. will re-check on this one.

/retest ci/centos/mini-e2e/k8s-1.23

/retest ci/centos/mini-e2e/k8s-1.23

   Mar 16 09:16:31.643: failed to delete PVC and Deployment: timed out waiting for the condition
Failed due to cephfs error not related to this PR.

@nixpanic @Rakshith-R PTAL from an encryption point of view for double confirmation.

There might be a problem when tenant based encryption is being used and pvc created in namespace A is recreated in namespace B.
This change will override the namespace in omap and we may not be able to unlock the volume.

This will not override the namespace in the omap, the owner will be retrieved from the OMAP in case of normal workflow (NodeStage). in case of DR, the omap will be regenerated with the correct owner specified in the PV claimRef object.

Before the change, reading ns from pv spec ensured the namespace remained the same(in omap).

IMO This is a wrong assumption, what if the whole namespace is deleted and PV is reattached to a new PVC in a different namespace. in the case of DR restoring to a new namespace should be a supported option.

@nixpanic @Rakshith-R PTAL from an encryption point of view for double confirmation.

Encryption uses owner (maps to the Kubernetes Namespace), which is set as metadata on the RBD image.
I agree that we should not store any csi.storage.k8s.io keys, not in the journal or metadata. We should use non-Kubernetes names for attributes that we need, and explicitly add those where needed.

/test ci/centos/mini-e2e-helm/k8s-1.22

/test ci/centos/mini-e2e-helm/k8s-1.22

deployment.apps/snapshot-controller created

customresourcedefinition.apiextensions.k8s.io/volumesnapshotclasses.snapshot.storage.k8s.io created

Error from server: error when creating "https://raw.githubusercontent.com/kubernetes-csi/external-snapshotter/v5.0.1/client/config/crd/snapshot.storage.k8s.io_volumesnapshotcontents.yaml[](https://jenkins-ceph-csi.apps.ocp.ci.centos.org/blue/organizations/jenkins/mini-e2e-helm_k8s-1.22/detail/mini-e2e-helm_k8s-1.22/2312/pipeline#step-77-log-1283)": etcdserver: request timed out

script returned exit code 1

/retest ci/centos/mini-e2e/k8s-1.22

CephFS NodeUnpublishVolume never returned (logs):
Mar 17 07:30:56.406: INFO: PersistentVolume pvc-80c82e0f-f9a8-4554-8c6b-db975cb13967 found and phase=Bound (2.645108ms)
Mar 17 07:30:56.422: INFO: Waiting up to csi-cephfs-demo-pod to be in Running state
Mar 17 07:31:02.438: INFO: Waiting for pod csi-cephfs-demo-pod to be deleted
Mar 17 07:41:02.452: FAIL: failed to validate CephFS pvc and application binding: timed out waiting for the condition
...
I0317 07:33:05.369623       1 utils.go:191] ID: 52 Req-ID: 0001-0024-2fe35e4b-d251-4e22-a116-bd6496352ee9-0000000000000001-2deb9525-a5c4-11ec-afd0-4e1bf5dd6186 GRPC call: /csi.v1.Node/NodeUnpublishVolume
I0317 07:33:05.369732       1 utils.go:195] ID: 52 Req-ID: 0001-0024-2fe35e4b-d251-4e22-a116-bd6496352ee9-0000000000000001-2deb9525-a5c4-11ec-afd0-4e1bf5dd6186 GRPC request: {"target_path":"/var/lib/kubelet/pods/b205ec8b-88e3-4feb-8619-f68eafec58b3/volumes/kubernetes.io~csi/pvc-80c82e0f-f9a8-4554-8c6b-db975cb13967/mount","volume_id":"0001-0024-2fe35e4b-d251-4e22-a116-bd6496352ee9-0000000000000001-2deb9525-a5c4-11ec-afd0-4e1bf5dd6186"}
I0317 07:33:05.380060       1 mount_linux.go:218] Cannot run systemd-run, assuming non-systemd OS
I0317 07:33:05.380097       1 mount_linux.go:219] systemd-run output: System has not been booted with systemd as init system (PID 1). Can't operate.
Failed to create bus connection: Host is down
, failed with: exit status 1

@mergifyio refresh


Add support for reading and writing Zip comments

It looks like MiniZip provides unzGetGlobalComment() and zipClose(file, global_comment)

Released in v1.1.2


Unifi-Poller can't show more than 1 Unifi Controller?

I love your great dashboard, it's very useful, but i try to add more than 1 controller always failed to start service unifi-poller, it's can add more than 1 unifi controller ?

It doesn't currently support multiple controllers. You could run it more than once to poll separate controllers. I'll consider adding support for this, but for now I recommend just running two copies.

I created network with unifi devices and separate 1 site for 1 controller, it will so helpfull if the fitur add on unifi-poller.
Thanks for your prompt responses! 👍

I'm going to add this support, but just so we're clear: it's going to be a long time, and a 2.0 release when it's added. This requires changing the config file format which I've been reluctant to do in the 1.x series.


Fix sending sending an env to itself.

[!WARNING]
This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

#1524  👈 (View in Graphite)
#1521
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Merge activity

Dec 4, 3:34 PM EST: A user started a stack merge that includes this pull request via Graphite.


Add Paint cum quicknotes extension

Hello, I am a gssoc'22 contributer and would like to add a paint(drawing tools) cum quicknotes extension in your project.

sounds fun, go ahead :))

any updates @Girlwithasmile ?

Almost done shall make the pr tomorrow


Apply yapf formatter.

This PR applies yapf formatter to Optuna source code.
Although this branch contains many changes produced by yapf,  the essential ones are only the followings:

.yapfignore
setup.cfg

[FYI] yapf(style=pep8) is almost compatible with autopep8 except the following diff:
--- original/./tests/integration_tests/test_lightgbm.py
+++ fixed/./tests/integration_tests/test_lightgbm.py
@@ -109,20 +109,20 @@
             'objective': 'binary',
             'metric': ['auc', 'binary_error']
         },
-               dtrain,
-               1,
-               verbose_eval=False,
-               nfold=2,
-               callbacks=[pruning_callback])
+            dtrain,
+            1,
+            verbose_eval=False,
+            nfold=2,
+            callbacks=[pruning_callback])
     else:
         lgb.train({
             'objective': 'binary',
             'metric': ['auc', 'binary_error']
         },
-                  dtrain,
-                  1,
-                  valid_sets=[dtest],
-                  valid_names=valid_names,
-                  verbose_eval=False,
-                  callbacks=[pruning_callback])
+            dtrain,
+            1,
+            valid_sets=[dtest],
+            valid_names=valid_names,
+            verbose_eval=False,
+            callbacks=[pruning_callback])
     return 1.0
--- original/./tests/integration_tests/test_xgboost.py
+++ fixed/./tests/integration_tests/test_xgboost.py
@@ -46,11 +46,11 @@
             'silent': 1,
             'objective': 'binary:logistic'
         },
-                  dtrain,
-                  1,
-                  evals=[(dtest, 'validation')],
-                  verbose_eval=False,
-                  callbacks=[pruning_callback])
+            dtrain,
+            1,
+            evals=[(dtest, 'validation')],
+            verbose_eval=False,
+            callbacks=[pruning_callback])
         return 1.0

     study = optuna.create_study(pruner=DeterministicPruner(True))

As discussed offline in the Optuna dev team, we are not going to include yapf in the checks job. This is because there still be frequent format change with the library's update. Let's revisit the library after the format get enough stable.


Changed CSS rules back to English

CSS rules are the same in Spanish no need to translate them.

[x] I have read freeCodeCamp's contribution guidelines.
[x] My pull request has a descriptive title (not a vague title like Update index.md)
[x] My pull request targets the master branch of freeCodeCamp.
[x] None of my changes are plagiarized from another source without proper attribution.
[x] My article does not contain shortened URLs or affiliate links.

If your pull request closes a GitHub issue, replace the XXXXX below with the issue number.
Closes #XXXXX

You need to add a blank line before the first set of 3 backticks and a blank line after the second set of 3 backticks for it to render correctly.

Hi @username. Congrats on your first pull request (PR)! 🎉
Thank you for your contribution to the page! 👍
We're happy to accept these changes, and look forward to future contributions. 📝


CircleCI token documentation

As discussed in #2373, I've added the documentation for token badges.
I think that the #1064 should be closed because the forum thread created by @Horgix regarding this issue has never been responded to.

Warnings

:warning:
This PR modified service code for circleci but not its test code. That's okay so long as it's refactoring existing code.

Messages

:book:
:sparkles: Thanks for your contribution to Shields, @haythem!

  Generated by :no_entry_sign: dangerJS


New collective page admin: pick primary color

With the new collective page admins are able to set the primary color of the collective :taco: :taco: :taco:
There no design yet for it, so here's a proposal to start the discussion:

On the Hero, show a pencil icon if user is admin

When users click on it, open a modal with

Hero background image upload form (will be part of another issue)
Color picker

For the color picker, let's not use something fancy: the native color picker (<input type="color"/>) is well supported by browsers, no need to include heavy libraries that will never match the level of accessibility that this one has. You can try it on https://developer.mozilla.org/fr/docs/Web/HTML/Element/Input/color (the results vary depending on the browser/OS).
Ideally, we should update the color in real time so that collectives can preview before saving.

Styleguidist snippet
import Modal, { ModalBody, ModalHeader, ModalFooter } from 'components/StyledModal';
import StyledButton from 'components/StyledButton';

initialState = { show: false };

<React.Fragment>
  {state.show ? (
    <Modal show onClose={() => setState({ show: false })}>
      <ModalHeader>Customize your collective appearance</ModalHeader>
      <ModalBody>

Pick the primary color for your collective

        <input type="color"/> #A85679

Upload an image

        <input type="file"/>

      </ModalBody>
      <ModalFooter>

      </ModalFooter>
    </Modal>
  ) : (

  )}
</React.Fragment>;

I love that.
Given it's a setting that will be changed only once, I'm not sure we want to use real estate from the collective page, otherwise it will always be in your face. So maybe put it in the /edit page?

By having it directly on the collective page you can preview the result in real-time before saving (rather than save, navigate to the collective page, return to the edit page if it doesn't look nice...etc). That's what Twitter does and I really like the UX of it:

I'd personally love if we were able to edit 100% of the content on this page without never leaving it.

alright, I'm sold :-)

https://github.com/opencollective/opencollective-frontend/pull/2104 adds support for theming by setting the primary color in settings.collectivePage.primaryColor. So the implemented color picker described in this issue should update the color in settings.

Resolved in https://github.com/opencollective/opencollective-frontend/pull/2421


Clear the DartdocEntry status flags on regression.

Handles the first part of the core issue in #1786.

Isn't the underlying problem here that we have duplicate information in the DartDocEntry, since isLatest and isObsolete can be computed from other places, right?

Correct. Another option is to use an extra Datastore check (+memcache) on each content that is being served, and then we can sunset the flag too. Which would you prefer?

I have no opinion at this point.. :)

I'm merging this with the doc now. We can easily remove this if we want to change the frontend serving part to not use the fields.


Center title

Hi, thanks for the great library. Is there any way to center the title ?

No for the moment. I will add that option in new release

Please update to the version 2.2.3, and you will be able to set the title Gravity


Add documents about trailing comma is disabled when wrapping is enabled

Description
From Kotlin Slack
If wrapping rule is disabled then trailing comma on call site & trailing comma on declaration site is disabled, because w/o wrapping trailing commas can produce weird formattings. (see 10cb29caf2c36bf5a8aac8d3cce38314c6671f71)
But there are no descriptions in rule documents about existence of this dependency and why exists. It may confuse users, so I added it.
Checklist

[ ] PR description added
[x] tests are added
[x] KtLint has been applied on source code itself and violations are fixed
[x] documentation is updated
[ ] CHANGELOG.md is updated

In case of adding a new rule:

[ ] Rule is added to rules documentation

Thanks for your kind reviews about PR, I've answered and fixed some changes about your comments.


Add Dracula2 color scheme to Dribbblish theme

resolves #162

Can you take another screenshot without windows control and big black ads in the middle?

I was never able to get the SpotifyNoControls.exe launcher working (the controls are never removed), but I will take one without the ads as soon as I get a chance.