Tooltip animation options has no effect on tooltip fade in animation

Expected behavior
Setting
options: {
      plugins: {
        tooltip: {
           animation: {
             duration: 0,
           },
        },
      },
}

would have effect on fade in animation
Current behavior
Setting this option has no effect on tooltip fade in animation
Reproducible sample
https://codepen.io/mottoweb/pen/mdaRrbY
Optional extra steps/info to reproduce
No response
Possible solution
No response
Context
No response
chart.js version
@latest
Browser name and version
No response
Link to your project
No response

If there is another way to affect tooltips fade in animation please let me know because i could not find any info in the docs nor on stackoverflow.

Hi @Mottoweb, I'd look at https://www.chartjs.org/docs/latest/configuration/animations.html to see how to control animations, you can technically remove the tooltip fade in animation by adding myChart.options.animation = false; after you init myChart at the end of the JS portion of your example.
Note: This will disable most animations, you might have to target something more specific to just affect the tooltip animation. Hopefully you'll be able to find the answer in that docs link I posted!


trigoformula.html

Want to add all the basics to advanced trigo formulas and identities.
and this will be under the study section of project.

@sairish2001 , please assign this to me under LGM SOC , As i want to contribute under it

Go ahead
Deadline 16 June,2021

Thanks for assigning me

@sairish2001 , I created a pr related to this issue , please check it.


Validate dataschema datasource

Re: #5780
The user was able to create a Kafka Indexing Service using a a dataSchema with a dataSource as an empty string. As the service uses the datasource as a key it can't be shut down etc.
This changes validates that a datasource isn't an empty string.

👍


How to process predictor error response ?

What would you like to be added:
If predict http request failed , return an error and cancel scheduling , like this:
https://github.com/clusternet/clusternet/blob/main/pkg/scheduler/framework/plugins/predictor/predictor.go#L128
One cluster predictor failure resulted in a subscription scheduling failure, which is inappropriate.
Why is this needed:
The task is to find a better way to solve this problem.

If predict request failed, return 0
drop cluster from available list when predict is not health

If method 1 is used, cluster which replicas is 0 will still in binding cluster, and cannot be removed, either it needs to be removed during the merge process, or there might be other ways to address this.
And if method 2,  drop the cluster from available cluster list when one feed predict failed even this subs have many feeds, It is a radical approach when there are only a few child clusters.

add post-predict extension point to process predictor unhealthy cluster

@dixudx @Garrybest

If predict request failed, return 0
If method 1 is used, cluster which replicas is 0 will still in binding cluster, and cannot be removed, either it needs to be removed during the merge process, or there might be other ways to address this.

I'd prefer using method 1 to return 0 replica, which is friendly to current scheduling framework and implementations.
By adding a new flag in struct ClusterScore to indicate such unhealthy predictor cases, all clusters with replicas 0 could be easily pruned in the function RunPredictPlugins.

add post-predict extension point to process predictor unhealthy cluster

If so, it will be better to taint the cluster.


Massive skill issue detected by Honbra

https://github.com/EnderKill98/RingMessage/blob/84a1625af2d11d0c8874c1fc0c1745aa3cc51320/src/client/java/me/enderkill98/ringmessage/Ring.java#L106
That line basically amounts to hast[3]. Bruh!
Java is keeping it a byte and not casting to int as i suspected, discarding all shifted bytes and THEN turning it into a int. Rust ftw fr!

https://ideone.com/Uyqh2c


Update objloader to accept non-triangulated faces and fix shaderpath problem

I updated the objloader.lua script to accept non-triangulated OBJ models.
And I also changed the way the path to the shader was built. Why ?
Wanting to import g3d like this local g3d = require("lib.g3d") I got this error:
Error: lib/g3d/init.lua:49: Could not open file lib.g3d/g3d.vert. Does not exist.
So I corrected it by replacing shaderpath = ... .. "/g3d.vert" by shaderpath = (...):gsub("%.", "/") .. "/g3d.vert"
I would like to specify that this modification does not prevent importing the module like this require("g3d") or like this require("lib/g3d").

Works great, thanks for the contribution!


The application is displaying an error when the room has configured only 1 “Amenities”.

Description:
When the user only configured 1 “amenities” to a room an error message is displayed.
-Env:
Device: MacBook Pro
Google Chrome Version 54.0.2840.98 (64-bit)
REPRODUCIBILITY LEVEL:
Always
STEPS:
Steps

Open the Crafter studio with the Hotel_Info site.
On the site bar, locate the pages section.
Click on the edit button of the “Rooms & Tariff“  page.
On the rooms list, select one room and click on the edit button
Delete or add new amenities to the room, so the room only contains 1 amenities.
Click on the Save and Close Button.
Go to the page preview of the room.

CURRENT RESULT:
The application displays an error message when the room page has only 1 amenities configured.
https://www.screencast.com/t/hJw3UICt
EXPECTED RESULT:
The application should not display any error message when there is only 1 amenities configured for the room.

Fixed

Bug verified and closed as fixed, build a115998.


Relax ping limits on the gRPC server

R: @aaltay
I find myself running longer jobs locally via the DirectRunner and I keep getting errors like this:
E0810 10:28:22.716036000<PHONE_NUMBER>97408 chttp2_transport.cc:1081]     Received a GOAWAY with error code ENHANCE_YOUR_CALM and debug data equal to "too_many_pings"
    target=lambda: self._read_inputs(elements_iterator),
  File "/Users/stefan/workspace/earth/.env/lib/python3.9/site-packages/apache_beam/runners/worker/data_plane.py", line 570, in _read_inputs
    for elements in elements_iterator:
  File "/Users/stefan/workspace/earth/.env/lib/python3.9/site-packages/grpc/_server.py", line 382, in __next__
    return self._next()
  File "/Users/stefan/workspace/earth/.env/lib/python3.9/site-packages/grpc/_server.py", line 374, in _next
    request = self._look_for_request()
  File "/Users/stefan/workspace/earth/.env/lib/python3.9/site-packages/grpc/_server.py", line 358, in _look_for_request
    _raise_rpc_error(self._state)
  File "/Users/stefan/workspace/earth/.env/lib/python3.9/site-packages/grpc/_server.py", line 113, in _raise_rpc_error
    raise rpc_error
grpc.RpcError
Exception in thread read_grpc_client_inputs:
Traceback (most recent call last):
  File<EMAIL_ADDRESS>line 973, in _bootstrap_inner
I0810 10:28:22.788511<PHONE_NUMBER>30400 local_job_service.py:340] Worker: severity: ERROR timestamp {   seconds:<PHONE_NUMBER>   nanos: 724023103 } message: "Failed to read inputs in the data plane.\nTraceback (most recent call last):\n  File \"/Users/stefan/workspace/earth/.env/lib/python3.9/site-packages/apache_beam/runners/worker/data_plane.py\", line 57
0, in _read_inputs\n    for elements in elements_iterator:\n  File \"/Users/stefan/workspace/earth/.env/lib/python3.9/site-packages/grpc/_channel.py\", line 416, in __next__\n    return self._next()\n  File \"/Users/stefan/workspace/earth/.env/lib/python3.9/site-packages/grpc/_channel.py\", line 803, in _next\n    raise self\ngrpc._channel._MultiThread
edRendezvous: <_MultiThreadedRendezvous of RPC that terminated with:\n\tstatus = StatusCode.UNAVAILABLE\n\tdetails = \"Too many pings\"\n\tdebug_error_string = \"{\"created\":\"@1628587702.717555000\",\"description\":\"Error received from peer ipv6:[::1]:57093\",\"file\":\"src/core/lib/surface/call.cc\",\"file_line\":1063,\"grpc_message\":\"Too many pi
ngs\",\"grpc_status\":14}\"\n>" trace: "Traceback (most recent call last):\n  File \"/Users/stefan/workspace/earth/.env/lib/python3.9/site-packages/apache_beam/runners/worker/data_plane.py\", line 570, in _read_inputs\n    for elements in elements_iterator:\n  File \"/Users/stefan/workspace/earth/.env/lib/python3.9/site-packages/grpc/_channel.py\", lin
e 416, in __next__\n    return self._next()\n  File \"/Users/stefan/workspace/earth/.env/lib/python3.9/site-packages/grpc/_channel.py\", line 803, in _next\n    raise self\ngrpc._channel._MultiThreadedRendezvous: <_MultiThreadedRendezvous of RPC that terminated with:\n\tstatus = StatusCode.UNAVAILABLE\n\tdetails = \"Too many pings\"\n\tdebug_error_stri
ng = \"{\"created\":\"@1628587702.717555000\",\"description\":\"Error received from peer ipv6:[::1]:57093\",\"file\":\"src/core/lib/surface/call.cc\",\"file_line\":1063,\"grpc_message\":\"Too many pings\",\"grpc_status\":14}\"\n>\n" log_location: "/Users/stefan/workspace/earth/.env/lib/python3.9/site-packages/apache_beam/runners/worker/data_plane.py:57
7" thread: "read_grpc_client_inputs"
    self.run()
  File<EMAIL_ADDRESS>line 910, in run
    self._target(*self._args, **self._kwargs)
  File "/Users/stefan/workspace/earth/.env/lib/python3.9/site-packages/apache_beam/runners/worker/data_plane.py", line 587, in <lambda>
    target=lambda: self._read_inputs(elements_iterator),
  File "/Users/stefan/workspace/earth/.env/lib/python3.9/site-packages/apache_beam/runners/worker/data_plane.py", line 570, in _read_inputs
    for elements in elements_iterator:
  File "/Users/stefan/workspace/earth/.env/lib/python3.9/site-packages/grpc/_channel.py", line 416, in __next__
    return self._next()
  File "/Users/stefan/workspace/earth/.env/lib/python3.9/site-packages/grpc/_channel.py", line 803, in _next
    raise self
grpc._channel._MultiThreadedRendezvous: <_MultiThreadedRendezvous of RPC that terminated with:
        status = StatusCode.UNAVAILABLE
        details = "Too many pings"
        debug_error_string = "{"created":"@1628587702.717555000","description":"Error received from peer ipv6:[::1]:57093","file":"src/core/lib/surface/call.cc","file_line":1063,"grpc_message":"Too many pings","grpc_status":14}"

I understand that the DirectRunner has its limitations and, in my case, I'm not using it for production jobs. However, it would be nice if some of the ping limits are relaxed a bit. Currently, the gRPC server has fairly strict limits:
GRPC_ARG_HTTP2_MAX_PINGS_WITHOUT_DATA = 2
GRPC_ARG_HTTP2_MAX_PING_STRIKES = 2

My PR removes these 2 limits completely wherever grpc.server() is invoked (Python SDK only). I'm not sure this is the best approach, but I'm happy to adjust it based on your feedback.
Bonus request: it would be even nicer if Beam could allow passing options to the gRPC client & server via some flags.

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[x] Choose reviewer(s) and mention them in a comment (R: @username).
[ ] Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.
[ ] Update CHANGES.md with noteworthy changes.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.

GitHub Actions Tests Status (on master branch)

See CI.md for more information about GitHub Actions CI.

hi @angoenka - could you please take a look at this change?
@stefanistrate - you'd need to fix autoformatter warnings on this change eventually, see: https://cwiki.apache.org/confluence/display/BEAM/Python+Tips#PythonTips-LintandFormattingChecks

I missed this review request earlier. Sorry for the delay and thank you for the contribution.

R: @ibzib

I've just run yapf on my code to fix formatting issues. Those tests are passing now.

07:38:58 The command '/bin/sh -c mkdir -p /usr/local/gcloud &&     cd /usr/local/gcloud &&     curl -s -O https://dl.google.com/dl/cloudsdk/release/google-cloud-sdk.tar.gz &&     tar -xf google-cloud-sdk.tar.gz &&     /usr/local/gcloud/google-cloud-sdk/install.sh &&     rm google-cloud-sdk.tar.gz' returned a non-zero code: 1
07:38:58
07:38:58 > Task :sdks:python:container:py36:docker FAILED
07:39:00

perhaps it's a flake, let's retry.

Run Portable_Python PreCommit


URL-Error with TranscribeAudio

Service
OpenAI
Describe the bug
Hi,
if I call the TranscribeAudio-Function from an AudioClient, I get the exception
HTTP 404 (invalid_request_error: )
Invalid URL (POST /v1/audio/transcriptions)
Please help.
Thanks.
Steps to reproduce

create an AudiClient-Instance
call the TranscribeAudio-Function with a mp3-file

Code snippets
No response
OS
winOS
.NET version
8.0.0
Library version
2.0.0

It seems to be a problem from OpenAI  :-(

It's solved.
I have to take the AudioClient-Instance with "whisper-1", not "tts-1".
I'm sorry.  :-)


Upgrade graal version

Release notes
https://www.graalvm.org/release-notes/20_2/
Nothing obviously critical

[cft:31247]      [total]:  64,436.33 ms,  6.26 GB
native image available at build/graal/cft (37 MB)

Deprecated Gradle features were used in this build, making it incompatible with Gradle 7.0.
Use '--warning-mode all' to show the individual deprecation warnings.
See https://docs.gradle.org/6.5/userguide/command_line_interface.html#sec:command_line_warnings

BUILD SUCCESSFUL in 1m 6s
10 actionable tasks: 1 executed, 9 up-to-date
➜  certifikit-cli git:(graal_upgrade) ./build/graal/cft -V
cft 0.3.0-SNAPSHOT


python312Packages.sagemaker: relax attrs

ZHF: #352882

Things done

Built on platform(s)

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

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

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

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

[ ] Fits CONTRIBUTING.md.

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

nixpkgs-review result
Generated using nixpkgs-review.
Command: nixpkgs-review pr 353340

x86_64-linux

:white_check_mark: 4 packages built:

python311Packages.sagemaker
python311Packages.sagemaker.dist
python312Packages.sagemaker
python312Packages.sagemaker.dist

Cherry-picked into https://github.com/NixOS/nixpkgs/pull/351565


Attach jsonRequest payload to http request body

The jsonRequest is never attached to the request - every call fails with 411 Length Required.

I've tested it locally, by manually wiring it together with other guice components. Unfortunately, I don't have time to invest into this since gRPC transport is now working (I've used http transport when gRPC was not working in production for few days).
I agree that there should be at least some kind of unit tests for it but I have no capacity to work on them and since there weren't any in a first place I have not updated them with a new test case - to be fair though if there were, there would be no issue in a first place. The code in this class, as it is now, is broken - the jsonRequest is never used in the code.
I suggest we merge this fix and iterate on solid test harness for http transport or simply just remote this class since it's broken at the moment.

Please update the branch


0.1.3 breaks functionality for querying for cloudcover intervals

Describe the bug
In cdsetool 0.1.2 cloudCover (and probably other things queried for in lists) could be queried for via
"cloudCover": '[0, 70]'

This no longer functions in 0.1.3.
If the method for querying has been updated, readme should include working example.
Steps to reproduce

    from cdsetool.query import query_features

    features = query_features(
        "Sentinel2",
        {
            "startDate": "2020-10-20",
            "completionDate": "2020-12-20",
            "box": ["4","51","4.5","52"],
            "processingLevel": "S2MSI2A",
            "cloudCover": '[0, 20]'
        },
    )
    print(len(list(features)))

yields
AssertionError: search_term [0, 70] does not match pattern ^(\[|\]|[0-9])?[0-9]+$|^[0-9]+?(\[|\])$|^(\[|\])[0-9]+,[0-9]+(\[|\])$

Expected behavior
Expected to find 26 features
Environment
Windows 10
VSCode

The regex mentioned in the error message is derived from the describe.xml document provided by CDSE.
It seems the patterns provided in this document is meant for client-side validation, since the server does not respond with error to non-matching queries
The pattern for cloudCover consists of 3 separate regex, joined by OR |
regex 1 ^(\[|\]|[0-9])?[0-9]+$
regex 2 ^[0-9]+?(\[|\])$
regex 3 ^(\[|\])[0-9]+,[0-9]+(\[|\])$

first regex will match

^ start of text
(\[|\]|[0-9])? 0 or 1 characters matching either [, ] or a single digit number
[0-9]+ one or more numbers
$ end of text

matching examples [100, ]60, 20
second regex will match

^ start of text
[0-9]+? match as few as possible numbers
(\[|\]) match either [ or ]
$ end of text

third regex will match

^ start of text
(\[|\]) match either [ or ]
[0-9]+ one or more numbers
, the character comma ,
[0-9]+ one or more numbers
(\[|\]) match either [ or ]

Going by your examlpe, the third sub-regex would be the one you are trying to use.
'[0, 20]' would match, except for the   space in the middle. Remove this and it works just fine
import re

pattern = '^(\[|\]|[0-9])?[0-9]+$|^[0-9]+?(\[|\])$|^(\[|\])[0-9]+,[0-9]+(\[|\])$'

assert not re.match(pattern, '[0, 20]')
assert re.match(pattern, '[0,20]')


Graceful service shutdown and configure SO_LINGER

Prevent point loss during proxy shutdown/restart process - stop port listeners first and drain all in-memory buffers to retry queue

@panghy Updated as per code review + added ability to configure SO_LINGER on listener ports as per customer's request


[Hotfix] Issue fixes related to private top project icons

Purpose
Fixes these two issues:
#2184
#2293
Changes

The icons and methods for a parent that is not a private project were the correct ones, these were not accurately transferred to the scenario where the parent is private. These have changed to have the same behaviors
If there is no link to parent component the cursor is not a link and the tooltip says the parent is private.

Side effects
None, very tiny code change.

So if we are leaving the data toggle the only other thing is the arrow use mentioned above. Someone tell me what to do and I'll implement it right away.

I'll talk to you in person about the arrow.

I have found the bent arrows to be a bit confusing, myself.
On Tue, Mar 24, 2015 at 1:10 PM, Brian J. Geiger<EMAIL_ADDRESS>wrote:

I'll talk to you in person about the arrow.
—
Reply to this email directly or view it on GitHub
https://github.com/CenterForOpenScience/osf.io/pull/2294#issuecomment-85603373
.

Causes there to be a slash at every page, including top level projects which do not have parents and don't need this.


GEE HTML Export error

HTML Export error
I try to create a map using geemap and python3 and in the and to export that map in HTML format. Everything goes fine but the exported HTML get's me some errors.

This is what that exported HTML it says. I tried to add manually the missing libraries but I get errors again and again. This is a blocker error for me as HTTPS does not support this kind of errors and I can not put it on browser. Is there something that am I missing?

Try the folium backend. import geemap.foliumap as geemap.
Keep in mind the GEE layers usually expire in 24 hours. You won't be able to see the GEE layers after it expires. A better way would be to deveop a web app instead of export the map as an HTML file. See https://github.com/opengeos/solara-geemap

This is an ipyleaflet issue rather than geemap. Run the following code. If you get the same error, then you need to report the issue on the ipyleaflet repo.
m = ipyleaflet.Map()
m.save('map.html')

Try the folium backend. import geemap.foliumap as geemap.
Keep in mind the GEE layers usually expire in 24 hours. You won't be able to see the GEE layers after it expires. A better way would be to deveop a web app instead of export the map as an HTML file. See https://github.com/opengeos/solara-geemap

This solved my issue. Thank you!


Port for eufy_security_ws addon is hardcoded

Since port 3000 was already in use by another program where I can't easily change it, I use another port for the eufy_security_ws addon. It should be a changeable config parameter.

Done. Please check my recent commits


Any utility to convert jpg image set to .dcm

Actually i have exactly 100 images of an object with 3,60 degrees. Is there any way to convert these images to .DCM in order to use this tool???

I do not understand what the "3,60 degrees" mean. In terms of converting jpg images to dicom images:

There are the DCMTK command line tools. This might be interesting for you.
I found also another tool which is supposed to do the job. No idea if that works.

If you know C++, you could implement this feature directly into this tool, DicomToMesh. It should be straight forward, as the whole mesh creation is performed on vtkImageData. vtkImageData, on the other hand, can be generated from an image source, such as jpeg images. Here is something similar. I can give you further information, if that would be an option for you. Would be a nice feature!

this type of error is generated. when i am processing DICOM file
No mesh could be created. Wrong DICOM or wrong iso value

You might need to align the orientation of the images first.
About the sample data: I do not have anything I am allowed to share.

"You might need to align the orientation of the images first"
Whats wrong with these files :
This is .dcm files for processing.  :- https://github.com/shalinsirwani/dcmfiles

I don't what those files are and how you created them. There are known issues that compressed DICOM images, multi-series images, etc. can not be imported. You can overcome that problem by using an extended DICOM importer, as described here

After correcting number problem and building this tool with "USE_VTK_DICOM = ON". Now when i am opening "https://github.com/shalinsirwani/dcmfiles" these files in itk-snap it says vector too long, if possible please provide any clue why this is happening....

Unfortunately, I do not know this error.

Good morning, Is it fine when I am closing this issue or are you still working on it?

Hmm , I used this tool by passing .vti file directly to the marching cube. And that .vti file was generated by a tool named as Volview.
Nice tool !


Encrypt/decrypt stellar key bundle

Implement Box and Unbox for encrypting and decrypting stellar key bundles. Some changes to PUK code to factor things out for reuse.
I put this in the go/stellar/bundle package rather than just go/stellar. Because I was thinking back on teams and I don't like how big the teams package is with service handlers, gregor handlers, crypto, parsing, and storage all mushed together. So for stellar we could try having smaller sub-packages and then maybe a few things in stellar that can depend on those. If it turns out to be too annoying I bet it's easier to merge into one package later than to split it apart later.

Cool I'm going to merge this and make another PR for the split way of doing it


size mismatch between vector and indexed vector

I have inserted into qdrant server with the help of qdrant client around 0.7M records.
I see there is a mismatch between the indexed_vector_count and vectors_count.
Why is this happening? Also my indexing_threshold is set to 10000 and my vector dimension is set 768, so the indexed_vectors_count should be 0, right?
{'status': <CollectionStatus.GREEN: 'green'>, 'optimizer_status': <OptimizersStatusOneOf.OK: 'ok'>, 'vectors_count': 727462, 'indexed_vectors_count': 715228, 'points_count': 727462, 'segments_count': 8, 'config': {'params': {'vectors': {'size': 768, 'distance': <Distance.COSINE: 'Cosine'>}, 'shard_number': 1, 'replication_factor': 1, 'write_consistency_factor': 1, 'on_disk_payload': True}, 'hnsw_config': {'m': 16, 'ef_construct': 100, 'full_scan_threshold': 10000, 'max_indexing_threads': 0, 'on_disk': False, 'payload_m': None}, 'optimizer_config': {'deleted_threshold': 0.2, 'vacuum_min_vector_number': 1000, 'default_segment_number': 0, 'max_segment_size': None, 'memmap_threshold': None, 'indexing_threshold': 20000, 'flush_interval_sec': 5, 'max_optimization_threads': 1}, 'wal_config': {'wal_capacity_mb': 32, 'wal_segments_ahead': 0}}, 'payload_schema': {}}

Hi @anandhperumal! Qdrant split collection into segments and indexes only those segments which are large enough. If segment is small, it is not that efficient to build vector index, as full-scan will work faster. Please consider indexed_vectors_count simply as indication that index works and covers majority of points.
Worth mentioning, that even if point is not marked as indexed, it is still available in search and any other API.

@generall that’s what even my understanding was from the document but all my vectors is of same size 768, so ideally they indexed_vector and vector_count should match, isn’t it?

vector size doesn't affect this. Indexing is defined by the number of vectors in the segment. And apparently you have one small segment which was not indexed


Move block_writer example from main Cockroach repo

The Block Writer example program is designed to write random blocks of data to a
single table in CockroachDB.  Writes are spread randomly across the table's
primary key via a randomized ID, and are never read.
The intention of this program is to create a large amount of data in CockroachDB
quickly, in order to quickly generate split and rebalance events.

LGTM


CocoaPods support + project structure improvements

CocoaPods support has been introduced (this requires CocoaPods 0.36 which is available as pre-release, see http://blog.cocoapods.org/Pod-Authors-Guide-to-CocoaPods-Frameworks/ for more details). Also project/folder structure has been improved.
@radex if you approve this pull request - please, uncomment the line with "s.source" property that points to your repository and remove currently active one which points to mine. After this make sure you have tag "1.0.0" associated with latest commit on "master" branch.
Note: this has been tested on a test project and proved that this library works as a pod.
P.S. thank you for the article and for this helpful little extension, very nice!

Great stuff! 🎉 Thanks @maximkhatskevich!

FYI @maximkhatskevich I'm still recommending to just copy the project's file to your project over CocoaPods because: a) Swift support in CocoaPods isn't shipped yet, and b) it won't work on iOS 7 AFAIK.

@radex agree with you. And you are right, the way CocoaPods can integrate Swift-based pods is as framework, but third-party frameworks require iOS8+. The purpose was to try the technology, despite it has some limitations right now :)


Changed how Cargo.toml of baseline is being built, added all features to baseline's manifest

Fixes https://github.com/obi1kenobi/cargo-semver-check/issues/147
Tested on the repo from this issue - seems to work. (Should I write some tests besides manually checking?)
In the issue you mentioned deleting the baseline's Cargo.lock. Is it also needed here? I don't really understand why this step is necessary.

Fixes #147 Tested on the repo from this issue - seems to work. (Should I write some tests besides manually checking?)

It would be great to have a test, since this is a tricky issue that would be a pain to debug again if we had a regression.
What do you think would be the best and easiest way to test this? It's a little bit tricky since the

In the issue you mentioned deleting the baseline's Cargo.lock. Is it also needed here? I don't really understand why this step is necessary.

Since we'd be emitting a brand new Cargo.toml in the baseline directory, it's probably a good idea to ensure the baseline directory is empty and freshly created, for example by deleting it completely if it already existed.
I'm not sure why I had a problem with Cargo.lock, but the easiest way to not have the problem is to not have any files (including the lockfile) in the baseline directory when writing the new Cargo.toml.
This is another case of "it's better to not have to debug this later." :)

What do you think would be the best and easiest way to test this? It's a little bit tricky since the issue only happens when using a baseline from crates.io.

It is tempting to add a test that checks for this problem from a selected crate from crates.io, but that would require internet connection. From one side, it seems weird to require access to crates.io during testing, but from the other side, cargo-semver-checks requires it when running the tool. What is your opinion?

It is tempting to add a test that checks for this problem from a selected crate from crates.io, but that would require internet connection. From one side, it seems weird to require access to crates.io during testing, but from the other side, cargo-semver-checks requires it when running the tool. What is your opinion?

I agree we probably don't want to trigger this at cargo test time, for the reasons you laid out.
How about a test script that gets run on GitHub Actions, as a sort of integration test? For example, it could clone the specific repo and commit where we found this problem, and assert that the false-positive is gone i.e. that running cargo-semver-checks with the appropriate flags exits cleanly.

So then I would need to edit https://github.com/obi1kenobi/cargo-semver-check/blob/main/.github/workflows/ci.yml right?
I guess the test would clone the rust-libp2p repo with a given relative path and rev and then it would run cargo run on it?

So then I would need to edit https://github.com/obi1kenobi/cargo-semver-check/blob/main/.github/workflows/ci.yml right? I guess the test would clone the rust-libp2p repo with a given relative path and rev and then it would run cargo run on it?

Yeah, that was what I had imagined, but I'm not tied to that idea or approach. If you have an alternative idea on how to add a regression test for this, I'd love to know about it!

That idea seems good enough for me. I don't really see another way to test this specific problem without connecting to crates.io during cargo test. And this approach would also potentially find other bugs (connection to crates.io is needed for the tool to work and it is good to check on an example that it works)

I think I'll add an issue and try to write a new PR for the GitHub Action integration tests and leave this PR without any tests. It seems that those tests would be beneficial not only to this particular PR. What do you think?

That sounds good. We should just avoid making new releases before those tests are in, which should be okay.


easier dependencies

It will be very easy to change the db to QL or BoltDB.
It will make the code and deployment, management much simpler i feel.
QL is a SQL db.
BoltDB is a Key value store db.
Both are 100% golang based databases.
QL
https://godoc.org/github.com/cznic/ql

an ORM for QL: https://github.com/gernest/ngorm

BoltDB
https://github.com/boltdb/bolt

an ORM for BoltDB: https://github.com/asdine/storm

is this something your open to ?

Definitely! The DB layer has been already abstracted in a way so that any database, as long as it implements the "datastore.Store" interface, it should work.
The only thing is that at the moment there are no automated tests for the datastore package, something which should also be solved sometime in the near future, so at the moment it will require some manual testing.
Again, feel free to work on any implementation, contributions are more than welcome!

Great news. I will be making some PR's
On Sat, 28 Jan 2017, 17:05 Anthony N. Simon<EMAIL_ADDRESS>wrote:

Definitely! The DB layer has been already abstracted in a way so that any
database, as long as it implements the "datastore.Store" interface, it
should work.
The only thing is that at the moment there are no automated tests for the
datastore package, something which should also be solved sometime in the
near future, so at the moment it will require some manual testing.
Again, feel free to work on any implementation, contributions are more
than welcome!
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/anthonynsimon/parrot/issues/28#issuecomment-275853162,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ATuCwoCJsTkY7vNlVVoaWyqCVJbBn3HTks5rW1k0gaJpZM4LweBK
.

Cool, just open them once you've got some progress.


Dog status codes

Relevant Issues

Description
HTTP status dogs doesn't the following codes: [101, 102, 421, 511, 499, 599, 415].
I have made a group for cat and dog status codes and dog status code is just duplicate to that of the cat just it adds another check by checking the response status after requesting the url.
Screenshots

Did you:

[x] Join the Python Discord Community?
[x] Lint your code (pipenv run lint)?
[x] Set the PR to allow edits from contributors?

When you input 101 for the dog status codes, what does it output? A 404?

When you input 101 for the dog status codes, what does it output? A 404?

Sorry, what I mean is when requesting from the url for a 101, what does it return?

Sorry, what I mean is when requesting from the url for a 101, what does it return?

My bad, any code that hasn't been implemented redirects to https://httpstatusdogs.com/404-not-found which is a page with a 404 image, but a bunch of other content. This is the case for 101, but also 999 as example.

I see, thank you for this information.

@ChrisLovering Mentioned the requested changes!

Mentioned the requested changes @Xithrius !


Remove unnecessary unsafe code and dependency

Re-upping from https://github.com/rustcoreutils/posixutils-rs/pull/211. Both the unsafe code and the dependency are unnecessary.


What are dimensionalities of images in UBD and FFOB catasets?

I see that many people ask you to release datasets, but, unfortunately you cannot do that. That's fine.
I want to ask you how big the images are? Are we talking about 500x500 pixels? Or even 1024x1024? I haven't found this information in the paper.
Thank you.

I think the size of these images is 256 x 256.
According to https://github.com/samet-akcay/ganomaly/blob/master/train.py#L9

Yes, I saw this code, but then I thought that x-ray scans of the luggage should be way bigger than that. But it is ok.


Stepping down as a maintainer

Hey folks!
I'd like to announce that I'm stepping down as a maintainer of this crate. I'm off to new adventures and would like to be able to focus on this new direction going forward.
Since that means that @dbrgn is the only remaining active maintainer, this might be an opportunity to look for new maintainers. But that is not my choice to make. I'm will be removing myself from @stm32-rs/stm32l0 shortly after posting this.
cc @arkorobotics, @dbrgn (the other members of @stm32-rs/stm32l0)
cc @adamgreig (chief of stm32-rs)
(edit: sorry, I tagged the wrong Arko originally)

I'd be happy to take a more passive maintainership role for this crate. I'm not skilled enough to make architectural decisions but I can help out on the easier feature/bugfix PRs.

I'd be happy to take a more passive maintainership role for this crate. I'm not skilled enough to make architectural decisions but I can help out on the easier feature/bugfix PRs.

Honestly, I think that's all that's required to keep things going. I myself have been leaning heavily on contributors for knowledge and testing for a while now. Providing a second pair of eyes and pressing "Merge" in a timely manner is already a very valuable role.

In that case, count me in!

Oh, that's sad to hear, @hannobraun. Thanks for all the maintenance work you've done here! However, your CAD project sounds very interesting, good luck 🙂 I'll definitely check it out.

I'd be happy to take a more passive maintainership role for this crate. I'm not skilled enough to make architectural decisions but I can help out on the easier feature/bugfix PRs.

Same thing for me 😄 As noted in #106, I'm a high-level software engineer and many things in the embedded world are still black boxes to me (for example, I've never used DMA so far and some aspects of timer configuration are still mysterious to me).
I think in the long term it would be good to have someone with more embedded experience that would be able to properly review pull requests. Until then, we could adopt a more passive maintenance model, where we generally accept all pull requests that are well-documented and don't look totally wrong, making the submitters responsible for their code. This could be documented in a more explicit way (e.g. with a note in the README), also with a call for more maintainers.

Since that means that @dbrgn is the only remaining active maintainer, this might be an opportunity to look for new maintainers. But that is not my choice to make. I'm will be removing myself from @stm32-rs/stm32l0 shortly after posting this.

I'd add @jamwaffles as co-maintainer, but I don't actually have the permission to edit members of that group (nor do I have maintainer-permissions for this repository, for that matter). @hannobraun do you know whom to ping?

Thanks for the kind words, @dbrgn!

I'd add @jamwaffles as co-maintainer, but I don't actually have the permission to edit members of that group (nor do I have maintainer-permissions for this repository, for that matter). @hannobraun do you know whom to ping?

Are you sure? When I was still in the team, it looked like I could add members on the team members page, but since I didn't actually do it, I either might have been mistaken, or maybe I was a maintainer and you're a normal member? I'm not sure; not an expert on GitHub org stuff.
If you really can't do anything on that page, @adamgreig should be able to help. Besides adding @jamwaffles to the team, it might be a good idea to make one or both of you maintainers in that team, while @arkorobotics is AWOL.

(nor do I have maintainer-permissions for this repository, for that matter)

I thought any rights we have here were conferred to us through our team memberships, but it seems I was wrong. At the very least, I can still open the repository settings (although I can't seem to do a whole lot there). And I still can close random issues.
Looks like I didn't actually step down. I just removed the privileges that would have been useful to add @jamwaffles, but kept all the others :laughing:

I've made @dbrgn a maintainer of the stm32l0 team, so you should now be able to add new members. Anyone in the team has maintainer access to this repository, but it looks like you were also directly listed on the repository as a holdover from before... I've cleaned up the direct repository access so it should all be through the team now.
Thanks for all your hard work here too, @hannobraun!

Thank you, Adam!

Thanks @adamgreig!
I can now add people to the team, but only if they're already part of stm32-rs. I cannot add people to stm32-rs, so unfortunately I'm still unable to add @jamwaffles 🙂

Oh, that's annoying! I don't think I can enable that, so I've invited @jamwaffles to the org myself. Please let me know whenever anyone else needs inviting (and welcome, @jamwaffles!)

I'm in! Thanks everyone, and thank you @hannobraun for your stewardship of this crate :)

Perfect, thanks @adamgreig!

Call for maintainers added in #212.

@hannobraun I'm still alive. Looks like @adamgreig took care of things here (Hi Adam!). I thought I'd chime in to say how great it has been to watch this repo grow over the years. It wouldn't be where it is today without you! Best wishes on your new adventures with Fornjot!

Thank you, @arkorobotics!

I'd be happy to help as well, I've been using l0xx as my go-to m0 lately, if help is still needed!

A quick update from my side: I'm not actively using stm32l0 MCUs anymore, so I will only rarely be of help. Don't wait for me on any reviews 🙂 Only if there are smaller maintenance tasks or small PRs that don't require any testing with an actual MCU, I might be able to help out from time to time.


Move validation module to consensus_validation

The consensus module is currently doing two things, validation and encoding. These two things are orthogonal.
Move the consensus::validation module to consensus_validation. Remove the function re-exports from consensus.
This was originally discussed here: https://github.com/rust-bitcoin/rust-bitcoin/issues/2779

Should we have deprecated reexport?

I'm going to wildly claim that we can't, last time we tried was a year or so ago so I could easily be misremembering.

IIUC this should work:
#[deprecated = "use consensus_* instead"]
mod consensus {
    pub use crate::consensus_encoding as encoding;
    pub use crate::consensus_validation as validation;
    pub use crate::consensus_params as params;
}

I'm going to test that now, if I'm correct and I'm testing [obvious] code you just posted without testing my contrary claim then you owe me a steak next time I'm in your area :)

oooo, so the steak goes to no-one. You are correct that we can deprecate a module but we cannot deprecate a re-export, and we can't use the module style yet because consenus is not empty with this PR's patches applied.
I'm glad you made me test :) Excuse my facetious-ness, I'm still butt sore from the hashes work recently :)

but we cannot deprecate a re-export

Right but that's really not that important if we've only moved to a different module, since users will have to name them learning the new name.

I mean we cannot add a deprecation notice in this PR.

We could also do this:
#[deprecated = "use consensus_validation"]
pub mod validation {
    pub use crate::consensus_validation::*;
}

Which also happens to be a bit friendlier to the users (but annoying to us). But it's not a big deal.

Force push is just rebase, I"m going to leave the deprecation stuff out. We can revisit before release of primitives if we want but eh

The conflicts introduced if this merges are IMO manageable, please merge if/when you get time to review @apoelstra

LGTM. Will ACK and merge after I am done with #3037. Agreed about the deprecation stuff. Let's try to remember to put it in, but if not, it's easy to add after release.


SAK-34012 fix cancel button and missing wicket id

Please also check submit behaviour as per ticket
https://jira.sakaiproject.org/browse/SAK-34012

The changes look good to me but there are conflicts with the base branch, would you mind to take a look @steveswinsburg ? Thanks in advance

Easy way to clean your master:
git branch -D master
git checkout -b master upstream/master

@ottenhoff Yeah I do that pretty often on 11.x/12.x branches when git gets funky.


[WIP] - Parse arf reports

It might need additional changes, opening as wip for visibility.

Thank you for review, I opened https://github.com/dLobatog/openscap_parser/pull/7 with the refactoring.

Should we close this as stale?

Yes, I think we can close. I will reopen when I have time to move forward with it.


LIRC

Register a service for sending infrared remote control signals using LIRC.
Listening to incoming infrared signals (and generating an event) would also be a great feature.
python-lirc is a LIRC extension for Python that is compatible with Python 3.
Although this can be easily emulated using scripts (for sending) and calling the API (for receiving commands), the proper solution would be adding LIRC as platform.

just added a ir transmitter to my raspberry where the home-assistant runs. would love to automatically power my stereo system if for example the firetv starts playing. :)
(controlling the stereo system via raw command line (irsend) works)

For this, you could use a combination of command line sensors, automations,
and the universal media player.
On Monday, February 1, 2016, Micha Stöcker<EMAIL_ADDRESS>wrote:

just added a ir transmitter to my raspberry where the home-assistant runs.
would love to automatically power my stereo system if for example the
firetv starts playing. :)
(controlling the stereo system via raw command line (irsend) works)
—
Reply to this email directly or view it on GitHub
https://github.com/balloob/home-assistant/issues/716#issuecomment-177932007
.

--
Thanks,
Ryan Kraus

Closing this issue as feature requests should be posted in the forum.

FYI I just made a PR related to this feature request here: https://github.com/home-assistant/home-assistant/pull/2139


MeanWeightedSumQuantileLoss and ND metrics produce incorrect results for all-zero data

Description
In the new evaluation module gluonts.ev, the MeanWeightedSumQuantileLoss and ND metrics are computed incorrectly if the target time series equals all zeros during the forecast horizon.
To Reproduce
import numpy as np
import pandas as pd
from gluonts.model.forecast import SampleForecast
from gluonts.model.evaluation import evaluate_forecasts
from gluonts.dataset.split import split
from gluonts.ev.metrics import MeanWeightedSumQuantileLoss, ND

T = 50
H = 20
start = pd.Period("2020-01-01", freq="D")
data = [{"target": np.zeros(T + H), "start": start}]
_, test_template = split(dataset=data, offset=-H)
test_data = test_template.generate_instances(H, windows=1)
forecasts = [SampleForecast(np.ones([1, H]), start_date=start + T)]
evaluate_forecasts(forecasts, test_data=test_data, metrics=[MeanWeightedSumQuantileLoss([0.1, 0.5, 0.9]), ND()])

Error message or code output
Code snippet above produces the following output:
      mean_weighted_sum_quantile_loss  ND[0.5]
None                              0.0      NaN

Expected output:
      mean_weighted_sum_quantile_loss  ND[0.5]
None                              Inf      Inf

The NaN value for ND is arguably okay, but the 0.0 value of WQL is definitely wrong.
Old evaluator from gluonts.evaluation used to produce Inf values in both of these cases.
Environment

Operating system: Amazon Linux 2
Python version: 3.10
GluonTS version: 0.14.0

I think NaN should be the expected value in both cases, why would Inf be ok?

Numpy and pandas return Inf when dividing a positive float by zero and NaN when dividing zero by zero. As far as I understand, that's what happens for WQL and ND metrics when the denominator equals zero.
>>> np.array(2.0) / 0.0
inf
>>> np.array(0.0) / 0.0
nan
>>> (pd.Series([2.0]) / 0.0).item()
inf
>>> (pd.Series([0.0]) / 0.0).item()
nan

Right, I missed that the prediction is ones, not zeros, OK

A more minimal working example:
import numpy as np
from gluonts.ev.metrics import MeanWeightedSumQuantileLoss, ND

H = 20

nd_aggregate_evaluator = ND()()
nd_aggregate_evaluator.update({"label": np.zeros((H)), "0.5": np.ones(H)})
print(nd_aggregate_evaluator.get())

mwql_aggregate_evaluator = MeanWeightedSumQuantileLoss([0.1, 0.5, 0.9])()
mwql_aggregate_evaluator.update({"label": np.zeros((H)), "0.5": np.ones(H), "0.1": np.ones(H), "0.9": np.ones(H)})
print(mwql_aggregate_evaluator.get())

Yields
-- # masked
0.0

Fixed in #3037


Firebase-related?

Is this module related to r-n-Firebase or not?
Can I, for instance, register to fireabase nototification topics without it ?

Separate to RNFirebase. RNFirebase Messaging already allows you to register to messaging topics. Messaging is not notifications.
This library will allow you to create local notifications without FCM, or make richer notifications from an FCM message if using alongside RNFirebase Messaging.


Revamp intro/onboarding docs.

This shifts some things around, fleshes some other bits out, and removes some bits altogether.

The quickstart page is now the landing page for docs: anyone hitting our docs site is more likely to know what React Flow is than not so let's make things smoother for them.
Links at the bottom of quickstart should make it easier for the majority of our users to find their way.

The "Overview" section has now been renamed "Concepts" and includes the introduction docs.
The introduction page has been slightly rewritten to flesh out each of the "Key Features" listed.

Awesome work @hayleigh-dot-dev 🙌 This is so much better!


remove unused dependencies

I was curious what this was originally for, and it seems to be for old docs - https://github.com/sbt/sbt/commit/600caef721991366b4939ed17f730149bc915108


router NAT configuration is lost after a reboot

I had to enable manually the IP masquerading after a reboot with this command:
/usr/sbin/iptables -t nat -A POSTROUTING -o eth1 -j MASQUERADE

This is because the masquerade is set via ssh is not write to a config file. I will check this.


[Enhancement]-[84]:Currency widget should allow , to be used as decimal seperator

Is there an existing issue for this?

[X] I have searched the existing issues

Description
Some locale (ex: de-de germany) use , as decimal and . as thousand separators. so we need to allow commas to be entered on the currency widget.
Steps To Reproduce

Try to enter , in the currency input
observe that you're not allowed to.

Public Sample App
No response
Version
cloud

Stats

Stat
Values

Reach
21

Effort (months)
0.5

Not only the currency widget also the input wigdet with type number. Please consider prioritizing this bug.

+1

Another user on discord is facing similar issue
Locale - pt-PT
Thousand separator -    (space)
Decimal separator -  , (comma)
https://discord.com/channels/725602949748752515/989129968141336606

This problem is certainly more than an enhancement but a bug. In all browsers that use the comma to separate decimals (e.g. Germany) neither the input nor the currency object works with decimal places! Because a dot is interpreted by my browser as a separator from the thousands place, not as a decimal place.

@liebig We have triaged this. The currency widget will accept the decimal character based on the locale. Will pick this up during the first part of the following week.

@techbhavin assigning this to you, please pick this up as part of this sprint.

@techbhavin can you please discuss with @sbalaji1192 on how you plan to fix this?

@somangshu @sbalaji1192  fyi, this didn't work out as expected. We were trying to use the browser locale to manage this, but turns out some browsers don't support this well enough.
I will work on a new prd for this which is much more comprehensive and easy for devs to implement

Discussed the default value problem with @keyurparalkar and @sbalaji1192 -
The default value will only support . as the decimal separator for now.
@keyurparalkar instead of using helper text, just show an error message if the user enters , or any other value as decimal separator saying that "Invalid number, please use ./point as the decimal separator for default values."
cc @chandannkumar

Hi, just to be sure that you focus on the other problem too, so not only the default value problem but the fact that in every country where the , is the decimal seperator the field does not accept decimal places at all. , in a currency field cannot be entered in languge de-DE and . is interpreted as a thousand delimiter.

Hello @MrWombastic yes, we already fixed it in the PR linked. Based on the locale we will accept either , or .
We are working on an expansion to also fix this in the default value field


Akka Dispatcher Metrics: Tasks

implement the metrics

Executor tasks completed
Executor tasks submitted

should be viewable in prometheus or grafana

@lgajowy
Tasks submitted can be obtained from:

executorRef.getTaskCount (if executor is thread pool)
executorRef.getQueuedSubmissionCount (if executor is fork join)

Tasks completed can be obtained from:

executorRef.getCompletedTaskCount (if executor is thread pool)
not yet known for fork join executor

We can re-use io.scalac.mesmer.agent.akka.dispatcher.DispatcherExecuteTaskAdvice to instrument the dispatcher executeTask and get a reference to the executor to poll these metrics as described in my comment below here [https://github.com/ScalaConsultants/mesmer-akka-agent/issues/324]


Keyvault metapackage is skipped from build

Keyvault meta package is omitted when building packages and causing pipeline issue when publishing to devops feed.

Successful run logs for keyvault:
https://dev.azure.com/azure-sdk/internal/_build/results?buildId=251621&view=logs&j=24b0f0c3-fa6f-56ea-ef7e-6d768498cf58&t=82783fc2-250a-5f4a-261d-8353cfb8854b


Array in argument and still check in body (abstract exception)

we know on line 155 have array at $errors argument
https://github.com/apiato/core/blob/571c6b27e9d1e756404a198c7d5c153e9f94fc9a/Abstracts/Exceptions/Exception.php#L155
but why still check (is_array) at line 157 ?
https://github.com/apiato/core/blob/571c6b27e9d1e756404a198c7d5c153e9f94fc9a/Abstracts/Exceptions/Exception.php#L157
just asking...

Better safe than sorry, I guess.. ;)


find-file doesn't seem to respect case-fold-search

The readme says:

Selectrum doesn't have any special handling of case-sensitivity, because Emacs includes a system for this by default. The command M-x toggle-case-fold-search toggles globally between case-sensitive matching and case-insensitive matching.

But in the case of find-file at least, case does not appear to be folded, despite case-fold-search being t.

Hm, I think the description needs an update as case-fold-search doesn't control the case folding for completion usually. There are completion-ignore-case, read-file-name-completion-ignore-case and read-buffer-completion-ignore-case and those should probably be dealt with by the refinement. It seems prescient doesn't make use of them currently, orderless supports it via the orderless-smart-case option which can be set to nil and will automatically pickup those in this case.

Hm, I think the description needs an update as case-fold-search doesn't control the case folding for completion usually.

I had a hunch that was not quite accurate, which is why I quoted it. :D

There are completion-ignore-case, read-file-name-completion-ignore-case and read-buffer-completion-ignore-case and those should probably be dealt with by the refinement. It seems prescient doesn't make use of them currently, orderless supports it via the orderless-smart-case option which can be set to nil and will automatically pickup those in this case.

I am still using the built-in completion-styles (though not the default value), so setting read-file-name-completion-ignore-case does the trick for now. Opening Makefile just got so much easier. But yeah, they should all respect those settings and the description should be updated. ;P

Done by fb68e5aace877f8c8791dc8dd9878af9f9ec06b8. The nice thing about oderless-smart-case option is that it will automatically disable case folding when using upper chars. Also to wet you appetite a bit more you can add custom dispatchers to determine how a search component is interpreted. For example I add "~" after an input string to use fuzzy matching for it or "=" to interpret it literally.

Thanks!
And I have just started using orderless. I'll let you know how it goes.

Great! I had a complex setup for a while but arrived at the following myself (the dispatchers is a result of recommendations from @minad and @oantolin):
(setq completion-styles '(orderless))

(setq orderless-matching-styles
      '(orderless-strict-leading-initialism orderless-regexp))

(setq orderless-style-dispatchers
      (list (defun my-orderless-dispatch (pattern _index total)
              (cond
               ((string-prefix-p "!" pattern)
                `(orderless-without-literal . ,(substring pattern 1)))
               ((string-suffix-p "!" pattern)
                `(orderless-strict-full-initialism . ,(substring pattern 0 -1)))
               ((string-suffix-p "=" pattern) `(orderless-literal . ,(substring pattern 0 -1)))
               ((string-suffix-p "~" pattern) `(orderless-flex . ,(substring pattern 0 -1)))))))

(setq orderless-skip-highlighting (lambda () selectrum-is-active))
(setq selectrum-highlight-candidates-function #'orderless-highlight-matches)


Dask not running in parallel

Just getting started with Dask.  I was following along with a Dask array example from here: https://examples.dask.org/array.html and also a Matthew Rocklin video here: https://youtu.be/TQM9zIBzNBo.
I expected the example to use all 12 cores on my Windows server, but it only ever used one processor.  I tried to increase the size of the example in case it was finishing quickly, but it just ran longer on only one processor.
Is there something else that needs to be done to have Dask run in parallel and use all the cores?
I have no code to submit other than the example code from the examples.dask.org and the YouTube video.
Not clear if this is a bug, but it did not work at all like the examples.
Environment:
Dask version: 2021.10.0

Python version: 3.9.7
Operating System: Windows 2019 Server
Install method (conda, pip, source): Base install of Anaconda that included Dask

Hi @AMCTeamMIS665ZA, welcome to Dask! This is more of a usage question than a bug report or feature request. We encourage people with such questions to ask them at the Dask Discourse 😄 Also, although the code is from examples.dask.org, can you please copy it into the post on Discourse so that the post is self-contained for any future readers, and in case the examples on the site change? Thank you!

I'm confused.  I'm following an example that clearly shows parallel use with a simple example in Dask and it did not work as demonstrated.  This could be a bug unless there are some steps in the examples that were not explained or documented.  Without knowing if any steps were omitted from the example, I would conclude this is a bug.

That's a fair point @AMCTeamMIS665ZA, in that example we explicitly set n_workers and threads_per_worker in the first notebook cell:
client = Client(processes=False, threads_per_worker=4,
                n_workers=1, memory_limit='2GB')

IIUC this is so we don't crash binder resources when running examples interactively. If you remove those n_workers / threads_per_worker specifications, you should see more resources being used on your machine


CORE-5804: Be flexible about order of config change distribution for RPC Permission reader/writer

The problem is that PermissionStorageWriterProcessorImpl may a a reference to the stale PermissionStorageReader which might have been already closed after the config update.
See more details on the Jira.

Looks plausible. I'm guessing you've tried it out with a few config updates and it still seems to process permission updates afterwards?

I did some testing locally, but I would want to add an E2E test to prove that users can be created once configuration been changed.

Unfortunately, E2E which updates config creates some side effects on the running cluster. I will not be introducing E2E this time.

Looks plausible. I'm guessing you've tried it out with a few config updates and it still seems to process permission updates afterwards?

I did some testing locally, but I would want to add an E2E test to prove that users can be created once configuration been changed.

Unfortunately, E2E which updates config creates some side effects on the running cluster. I will not be introducing E2E this time. But local testing has been performed and it works as expected.

I did worry that might be the case. I have a ticket on the backlog to add a smoke test that changes config for this reason.


suggestions about preview image file type

there is something important information is lost when preview images file. etc: width&height, file size.

file tree on the sidebar doesn't support arrow key in keyboard, like up(down) arrow key to active current file easy.

@xyyjk This might be a good candidate for extension. Feel free to contribute. Thanks.


Fix incorrectly formatted version rules

Related issue number

Issue: #131

Description
Fix incorrectly formatted version rules.

Remove the .* at line18 numpy>=1.19.*

Could someone please review my PR? Thank you.

Hello maintainers,
I recently submitted a pull request and noticed that there was a build error during the review process. Upon inspecting the error message, it was related to the install_requires section in the setup.py file. Specifically, the error message was:
  × Getting requirements to build wheel did not run successfully.
  │ exit code: 1
  ╰─> [3 lines of output]
      error in torchsde setup command: 'install_requires' must be a string or list of strings containing valid project/version requirement specifiers; .* suffix can only be used with `==` or `!=` operators
          numpy>=1.19.*;python_version>='3.7'
               ~~~~~~~^
      [end of output]

  note: This error originates from a subprocess, and is likely not a problem with pip.
error: subprocess-exited-with-error

To address this, I updated the requirement string from **numpy>=1.19.*;**python_version>='3.7' to **numpy>=1.19;**python_version>='3.7' and committed the changes. However, the build test still seems to produce the same error message indicating the presence of the older code.
Could you please help me understand why this might be happening? Is there something I may have missed or another step I need to take to ensure the updates are reflected?
Thank you for your assistance!

Ah, that's because it's pulling from the GitHub main branch to do a version check. Let me poke at that.
FWIW you may note that torchsde hasn't been touched in a couple of years; I'll try to get this PR merged, but I'd recommend Diffrax for new projects.

@patrick-kidger I enabled force push for you. Can you check if you can force merge?

@patrick-kidger I enabled force push for you. Can you check if you can force merge?

Merged and thanks, @jphan32. Let me know what else I should help with.

I've confirmed that my PR has been successfully merged into the master branch. Thank you. Also, I appreciate the introduction to Diffrax.


DAG

This PR is an internal refactor to make stacker build a Directed Acyclic Graph when planning execution.
Fixes https://github.com/remind101/stacker/issues/300
Fixes https://github.com/remind101/stacker/issues/186
Fixes https://github.com/remind101/stacker/issues/279
Fixes https://github.com/remind101/stacker/issues/384
Why use a DAG?
Performance
The DAG simplifies parallel scheduling, so that we can execute mutually exclusive stacks at the same time.
In this PR, each stack is executed in it's own thread. The thread blocks until all of the stacks dependencies have been executed, and then immediately starts. This means that stacks at the same depth, won't block each other unnecessarily.
The worst case stacker build time, is now the total time it takes for the longest critical chain (the longest chain of dependencies). Previously, the worst case stacker build time was a combination of the longest critical chain, in addition to the widest point in the graph.
For a concrete example, using the benchmark.yaml config, this PR dropped NOOP execution time from ~1min+ to ~15 seconds.
In our internal infrastructure repo, it drops NOOP execution time from ~7 minutes down to ~2.5 minutes (with my shitty RTT in Thailand).
Automatic dependency resolution for --stacks
stacker build supports a --stacks flag, however, in practice, it's difficult to use, because it won't automatically resolve dependencies. The DAG makes this easy, so when you provide a --stacks flag now, any dependencies are automatically visited.

Graceful SIGINT/SIGTERM
SIGINT and SIGTERM are handled more gracefully now. When received, stacker will wait until all current stack operations complete before shutting down.
Cyclic Dependency Checks
If there are any circular dependencies, it's detected and an error is shown. Previously, stacker would just hang forever.
Duplicate Node Detection
Previously, if you accidentally added a node with the same name, you wouldn't know about it, until it overwrote your existing stack with the new template (I've done this before with an RDS stack...). With the DAG, duplicate nodes are automatically detected.
Logging Improvements
The log output is updated whenever a step changes status, which fixes a number of issues where it would previously look like stacker wasn't doing anything (e.g. a noop run would never update the statuses).
Currently, logging is pretty jiterry because of this. I'll try to fix these issues before this gets merged.
https://asciinema.org/a/ilOwudPADDXQBnmfqa57JaC4Y
What can go wrong
Thread Safety
stacker is now multi-threaded, so we need to be careful to ensure that everything is thread safe. Not sure if there are any static analysis tools in the Python world for this.
Rate limiting
Because we're executing more API calls in parallel, it's possible for stacker to hit rate limits more easily, although, I've yet to hit any rate limits in all of my tests.

Tested

[x] Interactive mode
[ ] Tailing
[x] Assuming role with MFA
[x] Diff

TODO

[ ] Add a --j/jobs flag for specifying concurrency
[x] Figure out how to show stack traces without getting overwritten by checkpointing
[ ] Fix jitter in checkpointing
[ ] Fix SIGINT catch breaking CTL-C from MFA prompt.
[ ] Better handling of retrieving stack status updates to avoid throttling on DescribeStacks.

One annoying thing about going to threading, is that if a thread throws an exception, the stack trace can get overwritten by checkpointing:
https://asciinema.org/a/EUd6jUK8ogTqjsm0CgjMgtXDB

Apologies if it is too late given the seemly advanced stage of this PR, but were any other approaches considered other than explicitly building a DAG and walking it in multiple threads?
I've recently had a similar use case, and chose to implement it using Python 3's asyncio with "implicit" dependencies defined by waiting on futures corresponding to parents ' builds instead of explicitly walking the graph (which has the secondary advantage of making data propagation to children easier). Concurrency is limited by waiting on a semaphore before the first stage of an actual build (but only after waiting for dependencies).
While asyncio is not an option with Python 2, and probably a bit too large of a change for stacker as a whole, a very similar approach can be implemented with threads and events.
The interesting part of that implementation can be seen here (apologies for the less-than-prod-quality code).

@danielkza thanks for the feedback!
I think there's probably two things here that are orthogonal.

Building a graph before execution.
Whether or not to use threads for parallelization. The current implementation here uses threads to walk the graph, using an algorithm very similar to what you described above, but could be implemented using asyncio I think (if we ditched python2 support).

There's a couple of advantages that I see of building an explicit graph vs using implicitly waiting on outputs:

When we build a graph, it makes introspection of dependencies really easy. We can output a DOT formatted graph so you can see how all the stacks relate to each other.
It makes the destroy action really simple, since we just need to take the graph and then transpose it.
We can detect cyclic dependencies.

So, with that in place, then the question comes down to whether or not to use threading to walk the graph.
I'm definitely not married to the idea of using threads for parallelization here, since it's pretty resource inefficient (we're just waiting on IO to complete). I'm not sure what other options there are for python2 that would give us the same level of performance though.

@ejholmes Yeah, I figure the explicit DAC has some clear advantages. But I still think using futures for "flow control" would be preferable to checkpointing and explicit state monitoring. They make waiting relationships much more clear, likely easier to debug an test, and can more easily work with a fixed pool of resources instead of creating an arbitrary number of threads.
I will play with the idea a bit during this week and see if it actually makes sense. At worse I'll learn why it doesn't work and maybe get some insights.

Looks like someone ported asyncio to 2.7 - though YMMV: https://pypi.python.org/pypi/trollius


attributes on request

Related to issue https://github.com/falconry/falcon/issues/835

Current coverage is 100% (diff: 100%)

Merging #917 into master will not change coverage

@@           master   #917   diff @@
====================================
  Files          31     31
  Lines        1970   1976     +6
  Methods         0      0
  Messages        0      0
  Branches      320    320
====================================
+ Hits         1970   1976     +6
  Misses          0      0
  Partials        0      0

Powered by Codecov. Last update 45b4176...ed822df


⚠ ClamAV has degraded performance

In 389f9b3, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 221 ms

Resolved: ClamAV performance has improved in 1ec99be.


Motion Tagging Code

Thanks for the wonderful work! I am trying to reproduce the dataset, and if I understand it correctly, the current released code does not include ones that produces tag (e.g., frames 0-95: truck right) given the trajectory. I am wondering if this code is available?
Thank you very much again, and I am looking forward to hearing from you.

Hi,
Thank you for your feedback. The code is available, but I forgot to mention it in the README file (I have just updated it). You can find the motion tagging script in scripts/processing/dataset_captioning.py.


would like some help setting up

I ran your compiled build but I never get an accepted job, tried both monero and aeon mining.
I suspect it has something to do with not having any memory?
Im on a rPi 3b
See screenshot

I am running it with ./xmrig
And the following config.json
{     "algo": "cryptonight-light",     "api": {         "port": 3333,         "access-token": "null",         "worker-id": "pi3brig",         "ipv6": false,         "restricted": false     },     "av": 1,     "background": false,     "colors": true,     "cpu-affinity": null,     "cpu-priority": null,     "donate-level": 5,     "huge-pages": true,     "hw-aes": null,     "log-file": null,     "max-cpu-usage": 70,     "pools": [{ 		"url": "pool.aeon.hashvault.pro:3333", 		"user": "I have put my wallet address here", 		"pass"<EMAIL_ADDRESS>		"keepalive": true, 		"nicehash": false, 		"rig-id": null, 		"variant": -1, 		"enabled": true, 		"tls": false, 		"tls-fingerprint": null 	}],     "print-time": 60,     "retries": 5,     "retry-pause": 5,     "safe": false,     "threads": [         {             "low_power_mode": 1,             "affine_to_cpu": 0         }     ],     "user-agent": null,     "syslog": false,     "watch": false }
When I do enable 4 cores (inside the config json)
I still get huge pages 0/4 0% memory 4096 KB
In the image below you see that both my macbook and rpi are connected.
However Macbook gets jobs accepted and rpi does not.

On Macbook i compiled xmrig myself, on rpi i used this repo

Pi is too slow, especially for modern XMR. Also cryptonight is super slow and outdated, this would need to be migrated to rx


[IMPORTANT] Deprecation & Transition Strategy

Now that https://github.com/neovim/neovim/pull/12655 is merged, we are deprecating diagnostic-nvim. For full information and commit message, see: https://github.com/neovim/neovim/commit/f75be5e9d510d5369c572cf98e78d9480df3b0bb
Any features that were in diagnostic-nvim have now been implemented in Neovim core! This was always the plan for diagnostic-nvim, as it was a playground and testing area for features and interfaces for the builtin LSP
You should remove any on_attach calls from diagnostic-nvim in your configuration. They are no longer required.
Common Actions

PrevDiagnosticCycle and NextDiagnosticCycle:

New methods:

vim.lsp.diagnostic.goto_prev()
vim.lsp.diagnostic.goto_next()

Example Mappings:

nnoremap <leader>dn <cmd>lua vim.lsp.diagnostic.goto_next()<CR>

PrevDiagnostic and NextDiagnostic

New methods:

vim.lsp.diagnostic.goto_prev { wrap = false }
vim.lsp.diagnostic.goto_next { wrap = false }

Example Mappings:

nnoremap <leader>dn <cmd>lua vim.lsp.diagnostic.goto_next { wrap = false }<CR>

OpenDiagnostic

New method:

vim.lsp.diagnostic.set_loclist()

Configuring LSP Diagnostic Display

Configuration of the LSP diagnostic display is now done with lsp-handlers.

You can read more about them by doing :help lsp-handler
For example, to disable virtual text, you would do this in your init.vim

lua << EOF
vim.lsp.handlers["textDocument/publishDiagnostics"] = vim.lsp.with(
  vim.lsp.diagnostic.on_publish_diagnostics, {
    -- This will disable virtual text, like doing:
    -- let g:diagnostic_enable_virtual_text = 0
    virtual_text = false,

    -- This is similar to:
    -- let g:diagnostic_show_sign = 1
    -- To configure sign display,
    --  see: ":help vim.lsp.diagnostic.set_signs()"
    signs = true,

    -- This is similar to:
    -- "let g:diagnostic_insert_delay = 1"
    update_in_insert = false,
  }
)
EOF

Also note, the highlight group names have changed to now be consistent with each other. From the commit message in neovim core:
- Changed the highlight groups for LspDiagnostic highlight as they were
  inconsistently named.
    - For more information, see |lsp-highlight-diagnostics|

For example, the highlight that was formerly LspDiagnosticsError is now LspDiagnosticsVirtualTextError. It can also be configured by changing the default highlight group, LspDiagnosticsDefaultError. For more information, read :help lsp-highlight-diagnostics.
Advanced configuration

To configure more advanced usage, first, you should read the new help for ":help vim.lsp.diagnostic.on_publish_diagnostics"
After reading, you can override diagnostic-nvim configuration values, like sign configuration and virtual text spacing using something similar to the following:

vim.lsp.handlers["textDocument/publishDiagnostics"] = vim.lsp.with(
  vim.lsp.diagnostic.on_publish_diagnostics, {
    -- Enable underline, use default values
    underline = true,
    -- Enable virtual text, override spacing to 4
    virtual_text = {
      spacing = 4,
      prefix = '~',
    },
    -- Use a function to dynamically turn signs off
    -- and on, using buffer local variables
    signs = function(bufnr, client_id)
      local ok, result = pcall(vim.api.nvim_buf_get_var, bufnr, 'show_signs')
      -- No buffer local variable set, so just enable by default
      if not ok then
        return true
      end

      return result
    end,
    -- Disable a feature
    update_in_insert = false,
  }
)

Can someone please show me to how to do this autocmd CursorHold * lua vim.lsp.util.show_line_diagnostics() now?

Can someone please show me to how to do this autocmd CursorHold * lua vim.lsp.util.show_line_diagnostics() now?

have you tried autocmd CursorHold * lua vim.lsp.diagnostic.show_line_diagnostics()

have you tried autocmd CursorHold * lua vim.lsp.diagnostic.show_line_diagnostics()

Oh, hey that worked. Thanks!

Was someone able to change the signs icons?  I tried several ways but nothing worked.

have you tried :help vim.lsp.diagnostics.set_signs() info?
    sign define LspDiagnosticsSignError text=E texthl=LspDiagnosticsSignError linehl= numhl=
    sign define LspDiagnosticsSignWarning text=W texthl=LspDiagnosticsSignWarning linehl= numhl=
    sign define LspDiagnosticsSignInformation text=I texthl=LspDiagnosticsSignInformation linehl= numhl=
    sign define LspDiagnosticsSignHint text=H texthl=LspDiagnosticsSignHint linehl= numhl=

Yep,
I tried this in the init.vim and all the possible lua versions
vim.api.nvim_call_function("sign_define", {"LspDiagnosticsErrorSign",
{text = "", texthl = "LspDiagnosticsError"}})
vim.fn.sign_define("LspDiagnosticsErrorSign",
{text = "", texthl = "LspDiagnosticsError"})
vim.cmd [[ sign define LspDiagnosticsErrorSign text= texthl=LspDiagnosticsError linehl= numhl= ]]
I tried them on_attach, in the new beforeDiagnostick callback, before and after any lsp setting, noone worked, to me.

https://github.com/neovim/neovim/blob/bfed67e00ecdf71e0c7d17b1fd802f223b42c800/test/functional/plugin/lsp/diagnostic_spec.lua#L700
Is this todo still a thing?

That todo is for a different thing (there was some error when trying to find the signs that had been displayed. it's an internal bug I think, not related or due to the code).
Have you tried it via the ex command, not using sign_define? I think there may be some bugs related to sign functions and commands (I do not know for sure though, I have not had time to investigate)

No worries, cosmetics is not as important as functionalities, and for now LSP is a great piece of software so I can definitely wait.
(truth is I don't know know what parameters to pass to :lua vim.lsp.diagnostic.set_signs, still a newb on lua :D)

Ah, I meant to just try the ex commands listed in the docs to configure the signs.

Wow, I am truly sorry.
LspDiagnosticsErrorSign => LspDiagnosticsSignError
I'm gonna hide behind a mountain.

:laughing: such is life. No worries. I changed the names in the PR because they were randomly named before and now follow a pattern, so at least you're not too crazy :)

Might wanna archive this repo, maybe.

autocmd CursorHold * lua vim.lsp.diagnostic.show_line_diagnostics{focusable=false}
focusable=false is very useful


Update console.rst

The "Creating a cross-platform Console app with DNX" section was missing a link to the installation instructions on Linux.
Addresses #703

Hi @shrayasr, I'm your friendly neighborhood .NET Foundation Pull Request Bot (You can call me DNFBOT). Thanks for your contribution!

This seems like a small (but important) contribution, so no Contribution License Agreement is required at this point. Real humans will now evaluate your PR.

TTYL, DNFBOT;

This was already fixed in a duplicate PR that hadn't been merged (https://github.com/aspnet/Docs/commit/c762e19936920bcfce16054b6dc9921ee6d83199)
Thanks for the PR but I'm closing it as a dupe.

:+1: Thank you for the info. Cheers


414 mallob error persistant on zergpool

Users have reported for several months (since Dynex was added to ZergPool) that there have been mallob issues (414) using SRBMiner and also OneZeroMiner on AMDs and NVIDIA.
The issue appears to happen most often when using multiple GPUs. When users have more than one GPU mining dynex on ZergPool they most often get 414 errors.
Users have tried many things to resolve this, including ensuring their "paid to" address is a dynex address (not auto converting) as well as adjusting difficulty by various magnitudes.

Zergpool needs to update to the latest versions which have been released today to fix that issue.


Added the answer to be logged during evals

This PR contains:

[ ] New features
[ ] Changes to dev-tools e.g. CI config / github tooling
[ ] Docs
[x] Bug fixes
[ ] Code refactor

What is the current behavior? (You can also link to an open issue here)
During an eval, the answer field of scores was not being logged. It looks like this was first introduced in the Feature / epoch reducer pr:
Should fix https://github.com/UKGovernmentBEIS/inspect_ai/issues/208
What is the new behavior?
Starts logging this again
Does this PR introduce a breaking change? (What changes might users need to make in their application due to this PR?)
Shouldn't do
Other information:

Thanks for the fix! Should there be a test to catch this kind of regression?

Thanks for the fix! Should there be a test to catch this kind of regression?

Yeah there should be (I'm just being lazy), will write one

(Fixes #208)

(The test failure appears to be related to a release of Mistral's python package which occurred this afternoon. Not related to this PR at all. I'm investigating that separately).