path: do not recurse into hidden/dot directories

Cargo recursively looks for TOML manifest into child directories,
sometimes getting into unrelated files when exploring hidden
directories (eg. quilt .pc).
This commit lets cargo skip dot directories, to partially avoid
the issues described in #1423.
Signed-off-by: Luca Bruno<EMAIL_ADDRESS>Closes #978

Thanks for the pull request, and welcome! The Rust team is excited to review your changes, and you should hear from @wycats (or someone else) soon.
If any changes to this PR are deemed necessary, please add them as extra commits. This ensures that the reviewer can see what has changed since they last reviewed the code. The way Github handles out-of-date commits, this should also make it reasonably obvious what issues have or haven't been addressed. Large or tricky changes may require several passes of review and changes.
Please see the contribution instructions for more information.

Thanks! Could you also add a test for this?

Rebased according to your comments and added a test. As I didn't find an existing test covering that portion of code, I added a new one in a somehow arbitrary place. Let me know if I missed an existing one, or if it should be moved somewhere else.

@bors: r+ 11144645fa69cdc5cd6e28c2e8fbff62efc7974a
Thanks!

:hourglass: Testing commit 1114464 with merge e93e27b...

Digging through the archives, I just discovered that this PR also closes #978.

:sunny: Test successful - cargo-linux-32, cargo-linux-64, cargo-mac-32, cargo-mac-64, cargo-win-gnu-32, cargo-win-gnu-64, cargo-win-msvc-32, cargo-win-msvc-64


Implement proper JS layout for settings editor

From https://github.com/Microsoft/vscode/issues/65981
I've found a couple of problematic things with how the DOM is laid out in the settings editor, which I suggest to fix asap:

The settings-toc-container and settings-tree-container elements, both children of settings-body seem to take both full height and width of its parent. We should use a layout scheme there and have them side-by-side. Flex or simple block layout would be sufficient.
Because of (1), the settings editor is overriding internal tree/list CSS rules just to position and size both lists/trees as you want them to be. This is a big no no. By fixing (1), all these rules become obsolete.
The wrong width is passed along to the settings list. It should be the width of the whole container (up to 1000px) minus the width of the overview tree. Something like dimension.width < 600 ? dimension.width : Math.min(dimension.width, 1000) - 160.

I think the simplest solution would be just to keep the layout similar to the way it is now but avoid touching the list's own styles. Put the centering and extra padding styles inside each row element's content. Also would have to have styles for the scrollable element's shadows but that seems ok. Simpler than trying to put the scrollbars and shadows outside of the scrollable element's structure.

I implemented that, I think the only styles that might step on the tree are these
https://github.com/Microsoft/vscode/blob/c064781f92ddac447a24cbd4df88f0a61c9a2006/src/vs/workbench/parts/preferences/electron-browser/media/settingsEditor2.css#L263-L268
I don't think I can work around them right now, but if you think they are problematic we can try to do something about that.

So the validation messages can overflow the row:

Dammmnnn!


Review tests annotated with @ToBeFixedForInstantExecution

Signed-off-by: Rodrigo B. de Oliveira<EMAIL_ADDRESS>

@bot-gradle test QF

OK, I've already triggered QuickFeedback build for you.


zqd worker process

This adds a new API to zqd: /worker
This API allows the zqd to be invoked as worker process for a manager zqd process.
It adds a hidden flag, "chunk" to zapi, so the zqd /worker API can tested independently
of a manager zqd. The test is in ztests/suite/zqd/worker-count.yaml.
The PR does NOT add features for a manager zqd process. I will split that into a separate PR to avoid having either one get too big.

I have some questions about the code in multisource.spanWalk, and how to create a special case where it just returns scannerCloser for a single S3 object when the zqd instance is running a "/worker" request rather than a "/search" request.

I'm kind of behind the times with the distributed query work, so I hope you'll forgive a naive question: In order to handle overlaps shouldn't the worker be given spans to operate on as opposed to chunks?

I'm kind of behind the times with the distributed query work, so I hope you'll forgive a naive question: In order to handle overlaps shouldn't the worker be given spans to operate on as opposed to chunks?

The /worker API for ZQD does accept a span which can include multiple chunks. The zapi -chunk flag takes one chunk with the dash-separated format from the file name, and builds a span that includes one chunk in order to call zqd /worker.


CSP Violation with unsafe-eval in json-logic-engine

Hi,
I’m having trouble with the Content Security Policy (CSP) when using this library. My CSP doesn’t allow unsafe-eval, and even though the README says this library doesn’t use functions that cause CSP errors, the issue comes from its dependency on json-logic-engine.
After checking, I found that json-logic-engine uses evalon this line, which triggers the CSP error.
Could you let me know:

Is this something missed in the documentation, or is it intentional?
Is there a way to avoid this CSP issue while still using handlebars-jle and its dependency?

Thanks for your help! Let me know if you need more details.
Best regards,

Hey @jrpedrianes,
The JSON-Logic-Engine module, as well as this one, supports both a compiled mode and an interpreted mode.
For the purposes of this module, instead of using compile, you need to use interpreted (sorry, I need to update the docs to make this clear).
The signature is the same as compiled; interpreted(script: string, options)

Some further info: JLE's interpreter is able to use a WeakMap against the AST to cache an execution plan; which creates bindings between methods via closures so that it doesn't need to traverse the instructions each time.
This allows the JIT to optimize things that it otherwise wouldn't be able to if I was crawling the AST.
interpreted in Handlebars-JLE creates the AST and binds it to the engine.run function, making sure it can reuse that execution plan if the method is called again.
This leads to it having better performance compared to the Visitor approach used by the Kibana Fork of Handlebars.
It also seems to outperform Handlebar's compiler in most cases as well, which is a bit interesting.

Going to close the issue for now; if you have any trouble, don't hesitate to re-open or file a new one :)

Hello @TotalTechGeek,
Over the weekend, I didn’t have access to my laptop and couldn’t test your suggestion.
I’ve just had the chance to try it out, and it works like a charm 🎉.
I really appreciate your help and the time you took to provide these suggestions.
Thanks!!!


[FEATURE]: sensor state should provide clear information

Describe the solution you'd like
At present, when tje config leads to a no-data situation, afetr a while the sensor goes to unknown, which can mean multiple things
Describe alternatives you've considered
Static start/end: currently shows first/next departure
=> unknown seems pretty accurate as it is not known when a next dpearture takes place, could change to something more descriptive as "next-departure-unknown"
Local-stop sensor: currently shows stop name
=> stop name in a state is not really a good location, possibly change to number of collected departures

Hello,
The following exampleis working fine.
I'm not using  state to find out the "Stop name", but the departures, and it works fine.
The following example search for gtfs2 entities having "phone" in the name. ( mine is something like "Bus around my phone")
This example works in "Markdown Card"... at least for me ... :-) :-;
Regards
`
{%- set keyword = "phone" %}
{%- set unique_entities = states  |  list %}
{%- set ns = namespace(integrations = []) %}
{%- set ns.result = [] %}
{%- set ns.count_unique_entities= 0 %}
{%- set ns.processed_entities= 0 %}
{%- for entity in unique_entities %}
{%- set ns.count_unique_entities = ns.count_unique_entities + 1 %}
{%- set l_indentifiers = device_attr(entity.entity_id, "identifiers") %}
{%- set ns.l_indent1 = "" %}
{%- set ns.l_indent2 = "" %}
{%- if (l_indentifiers | string) != "None" %}
{%- set ids = l_indentifiers | list | first| default %}
{%- if ids and ids | length == 2 %}
{%- set ns.l_indent1 = ids[0] %}
{%- set ns.l_indent2 = ids[1] %}
{%- endif %}
{%- endif %}
{%- if 1  == 2  %}
1 {{ entity.entity_id }}
2 {{ entity.name }}
3 {{ entity.last_updated }}
4 {{ entity.domain }}
5 {{ entity.state }}
6 {{ entity.attributes }}
7 {{ entity.object_id }}
8 {{ entity.context }}
9 {{ l_indentifiers }}

9a={{ ns.l_indent1 }}
9b={{ ns.l_indent2 }}
{%- endif %}

{%- if ( entity.domain  == "sensor"  ) and ( ns.l_indent1 == "gtfs2")  %}
{%- if ( keyword in ns.l_indent2 )  %}
{%- set ns.processed_entities = ns.processed_entities + 1 %}
{%- for entry_departure in  entity.attributes['next_departures_lines']  %}
{%- set stop_name = entry_departure['stop_name'] %}
{%- set departure = entry_departure['departure'] %}
{%- set icon      = entry_departure['icon'] %}
{%- set direction = entry_departure['direction_id'] %}
{%- set route     = entry_departure['route'] %}
{%- set route_long = entry_departure['route_long'] %}
{%- if direction == 1 %}
{%- set terminus = route_long.split(" - ")[0] %}
{%- else %}
{%- set terminus = route_long.split(" - ")[-1] %}
{%- endif %}
{% set raw_string = stop_name + " -> " + terminus %}
{% set item = { 'sort_key1': departure , 'sort_key2':'', 'icon': icon , 'route':route, 'departure':departure, 'stop_name':stop_name,'terminus': terminus } %}
{% set ns.result = ns.result + [item] %}
{%- endfor -%}
{%- endif %}
{%- endif %}
{%- endfor -%}
{%- set sorted = ns.result | sort(attribute='sort_key1')%}
{%- for item in sorted %}
{{ item['departure'] + ' : '  + item['stop_name'] + ' -> ' + item['terminus']  + ' ('+ item['icon']+','+item['route'] + ')'}}
{%- endfor %}
`

Well i have seen a strange behavior a couple of weeks (months?) ago.
I was checking if state was valid or not... and if i remember at the end HA claimed it was valid, but the content was "unknown" or "unavailable" or something like that... :-(
I sould try to reproduce it... I think i was comparing 2 timestamps to retreive "In XX minutes"

It is quite tricky to repoduce things as I often donot have the same source or the time to look at things that are not 'my data of interest'...anything you can provide may help me to understand where the code may go pearshaped :)

Hi ,
I just found this https://community.home-assistant.io/t/how-to-make-template-sensor-with-as-timestamp-update-regularly/106084/2
In short it says "It is possible to force update even if sensor value doesn't change...."... may be it cound help with your update/refresh ....
On my side the issue is related to invalid timestamp when processing:
{{as_timestamp (states('sensor.tec_place_renard')) | timestamp_custom("%H:%M") }}
Fabien

Thanks and I was indeed thinking about a state-value that changes, which is not the stop-name. ...still pondering

@FabienD74 To keep the state usable I am thinking about this

keep the stop-name in it, that facilitates the use with cards e.g. auto-entities
add number of departures which would also help in identifyng the stops with departures
add a time (HH:MM), this will keep the state active even if a stop has no departure for more than 1 day
It could (still thinking) like:  stopname - 13:23 - 5

Tried it out but the 'dash' as separator is not nice
Liege Gare des Guillemins - Quai C - 10:24 - 0

Addressed with 0.4.8


Updated placeholder text to include " / WIF"

Please do not merge this commit.  It needs to be better displayed not just adding " / WIF".  It could give the wrong message that "Passphrase / WIF" is the same - which it is not.  I will make a new PR with better indication of either passphrase or WIF


"Downloading of Russian failed!"

Hi,
Dunno if this is the right forum for reporting a Text Fairly issue. But having used Text Fairy for a long time I am now getting the above message when trying to download the Russian language pack. Am using Android Nexus 5. Please fix if possible!
Thank you,
Justin

I have same problem with Russian package on Honor 8.

the tesseract repo has changed the russian files. I fixed it on master and released a new version to the  playstore.

Thank you. But I don't see the Playstore update yet - Text Fairy version
says released on Apr 2nd 2016. Do I need to refresh anything ?
On Dec 15, 2016 21:30, "renard314"<EMAIL_ADDRESS>wrote:

Closed #140 https://github.com/renard314/textfairy/issues/140.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/renard314/textfairy/issues/140#event-895891200, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAAilM4CCem-MnB5vIWNNaFtEm9_sfcVks5rIbFpgaJpZM4LN1BR
.

I just released a staged rollout of for 10% of the users. I added some more features and refactoring to this version and would like to let it run 1 day or so before rolling out to everybody.

Understood, thank you. I will try again in a couple of days.
On Dec 15, 2016 21:41, "renard314"<EMAIL_ADDRESS>wrote:

I just released a staged rollout of for 10% of the users. I added some
more features and refactoring to this version and would like to let it run
1 day or so before rolling out to everybody.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/renard314/textfairy/issues/140#issuecomment-267452577,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAAilJPFcKh1C2_8AzeEIQx2CxfoIGSYks5rIbQfgaJpZM4LN1BR
.


Fix DCF and FourierOp edgecase bugs

This fixes two bugs noticed by @schuenke (only triggered because of another bug):
Our FourierOp did not work for image_size<nufft_numpoints -- so you could not to non-uniform sampling with fewer than 6 points (not that common)
Our DCF vornoi assumed that the k dimension requiring vorinoi did not contain singleton dimensions.

I don't understand which case caused the dcf to fail. Could you please add a test case for this?

kx = rng.float32_tensor((1, 1, 4, 4))
ky = rng.float32_tensor((1, 4, 1, 4))

--> both need voronoi. they cant be stacked without broadcasting. this PR added the broadcast.
Not sure which real 3d trajectory would trigger this besides a wrongly read-in pulseq trajectory -- but it should work nevertheless as it is in theory a completely valid trajectory.


Helm hook does not return proper failure to standard output.

When using a helm hook for a pre-install step I would expect that if the hook fails the user gets an error message from the job indicating what failed. That is not the case, if a pre-install hook fails the only error that is returned is a generic job failure message that the job never completed (Either a backoffLimit or timeout) For example:
helm install
Error: Job failed: BackoffLimitExceeded
This is not useful since the real reason the helm release failed is because whatever task the pre-install hook tried to complete was unsuccessful. The return message from the helm install command should either be the output of the logs command of that pod or a mechanism is needed in order to return an error from that pod indicating why the pod failed.

 Since a hook can be applied to anything from configmaps to stateful sets, there's no uniform way to inspect a failure beyond what the API tells us. (And keep in mind that many kinds do not have logs attached)
As a feature, this would likely require quite a bit of work. But if someone provides a fix that is maintainable, we'd probably accept it.

Is this similar to #3370 ?

It would be very helpful to see, which job is failing, currently it's really hard:
helm upgrade --install ... mychart
Release "myrelease" does not exist. Installing it now.
Error: Job failed: BackoffLimitExceeded

We have a huge helm chart, with many jobs and other k8s resources, so it's not obvious, which job is failing.

Second this. I just spend 30 mins debugging this error:
$ helm upgrade --install --tiller-namespace MYSITE --namespace MYSITE ...
Error: UPGRADE FAILED: timed out waiting for the condition

journalctl showed the actual issue:
Apr 11 13:31:15 ... kubelet[430]: E0411 13:31:15.847166     430 pod_workers.go:190] Error syncing pod 14642dea-5c4d-11e9-a665-5254000919ee ("MYSITE-test-migrate-z62c8_MYSITE(14642dea-5c4d-11e9-a665-5254000919ee)"), skipping: failed to "StartContainer" for "django-migrate" with CrashLoopBackOff: "Back-off 1m20s restarting failed container=django-migrate pod=MYSITE-test-migrate-z62c8_MYSITE(14642dea-5c4d-11e9-a665-5254000919ee)"

The kube object is:
apiVersion: batch/v1
kind: Job
metadata:
  name: {{ template "fullname" . }}-migrate
  annotations:
    "helm.sh/hook": "pre-install,pre-upgrade"
    "helm.sh/hook-delete-policy": "before-hook-creation"
...

closing as inactive.


Custom Discord Bot Template

Functionality:-A discord.py bot template for making your own bot.

I would like to work on this issue under JWOC.

@jayesh-shadi go ahead!!

@neelshah2409 I would like to work on this issue.

@neelshah2409 I would like to work on this issue under KWOC.

Go ahead 🚀


bump webassemblyjs

Fix custom section decoding.

What kind of change does this PR introduce?

Did you add tests for your changes?

Does this PR introduce a breaking change?

What needs to be documented once your changes are merged?

Fixes #8781 https://github.com/rustwasm/wasm-bindgen/issues/1246

I can confirm this fix addresses the issue in question. For search engines, this was the relevant error code:
Module parse failed: Unexpected section: 0xfe
You may need an appropriate loader to handle this file type.
Error: Unexpected section: 0xfe

Thanks


Add Fatima Monteiro as Collaborator -- timamonteiro?

Add Yusuf Bolden as Collaberator -- yusufbolden?

Mianta -- Since you are the admin, I believe you have access to add

They are added


Check Receipt State in RAV aggregate receipts

Creating issue to tie to TODO comment.
In RAV aggregate receipts the state of any RAV that is aggregated should be OK, otherwise error should be thrown. This is waiting on #28 to be completed.

@ColePBryan isn't this one fixed?

No, this refers to this line: https://github.com/semiotic-ai/timeline-aggregation-protocol/blob/009c829bd2790ea3e8bfc289d807abe6cf1f66d4/tap_core/src/receipt_aggregate_voucher.rs#L52
We just need to add a check that the state of the receipt is correct. I'm not sure if that would work as expected now. The idea was to have the aggregator use the manager and do all required checks then when we are aggregating we just check the receipt state to ensure they are all checked. I think right now we don't have the aggregator using the manager. So unless that is going to change we can just remove this and the TODO comment as well.

I looked at the code again, I still think that we're better off not using the manager in the aggregator for now. The current checks code in the Aggregator is quite straightforward, and besides tap_core does not provide these implementations anyway, and the manager does not really fit for usage outside the indexer in my opinion.


All database cargo features are enabled when migrate cargo feature is enabled

Bug Description
I am encountering unexpected behavior of the cargo features in this crate. I want to enable only the postgres and migrate features, but it seems to pull in all database features whenever migrate is enabled.
This is surprising because all of the database crates (sqlx-sqlite, etc) are optional and should only be enabled by their corresponding features. This is how the migrate feature is defined:
migrate = ["sqlx-core/migrate", "sqlx-macros?/migrate", "sqlx-mysql?/migrate", "sqlx-postgres?/migrate", "sqlx-sqlite?/migrate"]

My understanding of the ? in a cargo manifest is that it should not enable the feature before the ?, and only enable the feature following the ? if the parent crate is already enabled somewhere else. The behavior I observe is not consistent with this.
To be fair, this might be a cargo bug. I can't really tell.
Minimal Reproduction
cargo init --lib foo
cd foo
cargo add sqlx --no-default-features --features migrate
cargo check
rg "sqlite|mysql|postgres" Cargo.lock

Expected output: empty
Actual output:
468:name = "libsqlite3-sys"
898: "sqlx-mysql",
899: "sqlx-postgres",
900: "sqlx-sqlite",
976:name = "sqlx-mysql"
1017:name = "sqlx-postgres"
1055:name = "sqlx-sqlite"
1067: "libsqlite3-sys",

Info

SQLx version: 0.7.4
SQLx features enabled: migrate
Database server and version: Postgres 14.9 (or none!)
Operating system: NixOS (Linux 6.1.69)
rustc --version: 1.76

Showing up in the Cargo.lock doesn't mean they're actually getting compiled
This is likely the same as #2964 which appears to be a result of the following Cargo bug: https://github.com/rust-lang/cargo/issues/10801#issuecomment-1874741198

@abonander

Showing up in the Cargo.lock doesn't mean they're actually getting compiled

Interesting! I guess I'm not worried about this then.

This is likely the same as https://github.com/launchbadge/sqlx/issues/2964

This was the original issue I was running into as well, except I've got rusqlite in my dep tree instead of sqlsync. Sorry I didn't manage to find it in my search. For now, I can live with a workaround where I just downgrade rusqlite so the libsqlite3-sys versions match up, even though I'm not even using sqlx for SQLite.
Feel free to close this issue as a duplicate of #2964 .


upgrade to null safety

hello, this package needs to upgrade to the latest version even not null safety. please assign me, I will upgrade this repo to null safety

Here is the null-safe version of this package :
 another_carousel_pro: ^1.0.0
pub.dev


Is logo image in README indicative of "nominal" wheel profile?

I am interested to build a railcart (small powered vehicle for riding abandoned tracks), and I am looking for "ideal" design to implement. Given this will be for recreation, it need not be the most performant or resistant to wear and tear. Since your "importance" section clarifies that the "right" conicity will tradeoff turning well (not hitting inner flange) with straight-track comfort... which from this youtube demo I understand that comfort must mean less wobbling... I would like to know if the blue wheel 2D profile is the "ideal", even if just for your [country/region's] tracks in your [country/region's] gauge, etc... or is it, on the other hand, and extreme profile meant to showcase the conditions where performance is out-of-spec?

Hi, my friend. You have 3 options: pure conical profile (which it's only a theoretical case), and a conformal wheel (variable conicity angle) with or without flange area. The picture you pointed out is clearly the case which lacks of flange zone (that technically speaking; it can be considered a very smoothed area in there, anyway).
That said, the right wheel profile depends on the rail profile, and the need of flange is related to curving and speed specifications.
But to keep it simple, assuming you won't build an TGV, I would use a conformal profile like the picture shows, according to your country's track dimensions.
Have a nice build journey.
Vincent.


fix(45045): class method destructuring assignment autocomplete not work

Fixes #45045

Just as a heads up, I've been investigating the issue related to that fix, and I'm trying to see if we can reuse a function from the checker to replace the piece of code that caused the bug. So it might be a few days before I have a better idea on how to proceed with a fix. If we decide we just want to fix the code as is, I'll review your PR, and I'll let you know otherwise. And as always, thanks.


elixir: support projects using Nerves extensions

Nerves provides tooling for using Elixir in embedded systems. Using
Dependabot on these projects currently fails with the following error
message:
Dependabot can't evaluate your Elixir dependency files.
As a result, Dependabot couldn't check whether any of your dependencies
are out-of-date.

The error Dependabot encountered was:
** (Mix) Archive "nerves_bootstrap" could not be found. Please make sure the archive is installed locally.

Adding the nerves_bootstrap.archive fixes this issue. This does not
affect projects that do not use the Nerves tooling since the code in the
archive is not called in those cases.

I have an updated test, but I'm still getting the original error like the mix archive.install hex nerves_bootstrap isn't happening:
   # JSON::ParserError:
     #   767: unexpected token at '** (Mix) Archive "nerves_bootstrap" could not be found. Please make sure the archive is installed

I thought that I added the line to the right place, but maybe not? Is there a way that I can verify that it took?

I guess the Docker image you updated to install nerves_bootstrap is not used during tests.
you should update hex/helpers/build
diff --git a/hex/helpers/build b/hex/helpers/build
index 2f1f8f4be..bc075ac8e 100755
--- a/hex/helpers/build
+++ b/hex/helpers/build
@@ -10,7 +10,7 @@ fi

 mkdir -p $install_dir

-mix local.hex --force
+mix local.hex --force && mix archive.install hex nerves_bootstrap --force

 helpers_dir="$(dirname "${BASH_SOURCE[0]}")"

Thanks - I just added your change. Let's see what happens...

@cblavier The tests passed! Thanks!
I rebased and squashed the intermediate work.


ActOnEveryObject can accept IReadOnlyReactiveCollection

Enhancement for #989
(this should target the proper branch now, previous PR was #999)

I think you might have missed my comment on the previous PR. IReadOnlyReactiveCollection extends IReactiveCollection, so you've actually narrowed the utility of this method by taking IReadOnlyReactiveCollection rather than just IReactiveCollection. Do you agree @flagbug ?

@kentcb is right, I thought the implementation was the other way around, so extending IReactiveCollection is the right way to go

:thumbsup: IReactiveCollection

Read, facepalmed, fixed. I guess there's no more room left to do another mistake.

Thanks @arkein!


Billing not working

I enabled billing in the config (after reinstalling on Laravel 5.5) but when I install the app, it does not take me to the billing page. It just goes straight to the app homepage. Is there anything else that needs to be done apart from setting the billing parameters in the the config file?

ok sorry for this. I got it to work. I forgot to apply the "billable" middleware


'Esc' key does not prioritize closing bank/interface

Hello it's my first time writing here/using github in general  i don't know if it is appropriate to say it here but i've set my chat toggle hotkey to ESC and whenever im in a bank or other interface it will not close because I use both togglechat and 'ESC close interface' features.

Hello it's my first time writing here/using github in general i don't know if it is appropriate to say it here but i've set my chat toggle hotkey to ESC and whenever im in a bank or other interface it will not close because I use both togglechat and 'ESC close interface' features.

Should be fixed in the latest update. Thanks for bringing it up!


Fix daily test

The daily test hasn't run correctly in the last weeks. The testing of the packages seem to be aborted because the default maximum execution time (6 hours) is exceeded. Increase the timeout to 12 hours.
The failure caused the README badge to be updated wrongly:

Change the conclusion status of the package testing step to success even if packages fail, as the action is still
running as expected (we want to count the failures, so we expect failures). This way we detect other errors early avoiding the wiki and the badge to be updated.

Thanks for the review @mr-tz! I have just triggered the daily test manually :wink:

Seems we are getting an ERROR still after the latest run:

It looks like there's an issue with git.install dependency, where git isn't installing correctly, which then leads to a bunch of other installation failures: https://github.com/mandiant/VM-Packages/actions/runs/10559091787/job/29249826630#step:3:4884


Fix StructuredGeneration examples and internal check

Description
The examples of StructuredGeneration have been updated to show how the values can be informed, they are the same as a TextGeneration that takes a structured_output argument.
Both AsyncLLM and LLM (plus InferenceEndpointsLLM) take the same input:
{"format": "json", "schema": "..."}

If the format is not informed (outlines requires that), we will try to infer it from the schema.
Closes #906

@plaguss can ytou add the index page for deepseek prover here too? it does not show up at the moment. https://distilabel.argilla.io/dev/sections/pipeline_samples/examples/#examples


[Feature request]: S220 Solo Cam Support

Describe the solution you'd like
Please, can you add support for S220 Solo Cam.
I can give access.
Thanks.

Hello, I can give access to my camera too if needed.

Hello, is this something that is being worked on?
Would like this feature as well

Currently says: Unsupported.
S220 SoloCam, Version: <IP_ADDRESS>

https://github.com/bropat/eufy-security-client/pull/353

love to see s220 working to. I have one and I want buy more. but waiting till support on homebridge.

Please add support for S220 Solo can. I have a lot of them and love to see them in HomeKit. Nice work. Keep going.


Add RBAC for prometheus

Fixes https://github.com/istio/istio/issues/3149

Hi @Stono. Thanks for your PR.
I'm waiting for a istio member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.
I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

I signed it!

/assign @frankbu

/lgtm

@Stono: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-presubmit.sh
0f9d2ab9899df6556c027b8801affef8cb540cd8
link
/test istio-presubmit

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

Hmm @andraxylia that test failure looks unrelated to this?  Do you have flakey tests?

/retest

@Stono: you can't request testing unless you are a istio member.

In response to this:

/retest

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.


 It will be in your mounted data folder

location / {# Access List

That's the entire file contents? seems to be a lot missing.
Any letsencrypt certs will not be able to renew when nginx is down altogether. If they expire and you're not using them, no big deal, they can renew later when nginx is back up.

------------------------------------------------$# Lidarr.example.net
------------------------------------------------$
server {
��set $forward_scheme https;
��set $server���������"<IP_ADDRESS>";
��set $port�����������8686;
��listen 8080;
��server_name Lidarr.example.net;
�����������������[ Read 45 lines ]
I edited out my domain with example.net

I ended up deleting the entry in the proxy host webui and every thing is back up and running.

Definitely seems weird. Re-open this if it happens again.


How to restore the options to default values?

Required Info

Camera Model
D435

Firmware Version
<IP_ADDRESS>

Operating System & Version
Linux (Ubuntu 20LTS)

Kernel Version (Linux Only)
5.11

Platform
PC

SDK Version
pyrealsense 2.50

Language
python

Segment
Others

Issue Description
How can I restore the options to default values via pyrealsense API after I change some of them such as:
color_sensor.set_option(rs.option.exposure, 1000)
color_sensor.set_option(rs.option.gain, 50)
......

Hi @ZhongQingliang  You could set the defaults for the 400 Series cameras manually for specific options that you have changed.  If you launch the RealSense Viewer program and examine the settings of the options without altering them, they are typically the default values of that camera model.
For example, the RGB defaults are 156 for exposure and 64 for gain.
Alternatively, you could try performing a reset of the camera using the hardware_reset() instruction.  A simple example Python code snippet is shown below.
ctx = rs.context()
devices = ctx.query_devices()
for dev in devices:
dev.hardware_reset()

Hi @ZhongQingliang  Do you require further assistance with this case, please?  Thanks!

Case closed due to no further comments received.


[Feature]: Credentials handling improvement suggestions

Hi, I think there are a couple issues with the current credential management system. For most of them I'd be happy to implement fixes but I think it is better to first discuss them before coding :)
1. Superfluous token refreshes
The current pattern for API calls is the following:
api_call (e.g. pycmc.artist.metadata())
    utilities.RequestData
        importlib.reload(credentials_manager)
            credentials.Update
                credentials.FetchAccessToken
    utilities.RequestGet

Authentication is reperformed before each API call. Hence all functions in the library would be twice as fast if the token was only refreshed when needed (i.e. Error 401).
2. Rate limit handling
I know #15 already references this but I still mention it here because I think it should happen at the same place than token refreshing. In other words, the automatic handling of error 401 (unauthorized) could also handle error 429 (too many requests).
3. Rigid environment variable flow
I think the current mandatory JSON environment variable is not very user-friendly. First, the only needed input from user is the refresh token; the empty dict structure could automatically be infered. Second, I'd say it would be better if users had an alternative way to connect, cause maybe they don't want to use an environment variable.
To solve this, I would imagine a lazy design that does not authenticate at import time but only on first API call, coupled with a new pycmc.authenticate(refresh_token) function. Authentication would use CMCREDENTIALS by default until the user calls authenticate at some point.
4. Impossibility to manage several Chartmetric accounts
I'd like to develop applications that have several users, each with their own API token (think of a web server doing Chartmetric requests in place of the end-user). The current global variable system does not allow this. The way I would redesign the API would be an object-oriented interface similar to for instance what they do at spotipy:
import pycmc

client = pycmc.ChartmetricClient(refresh_token)
client.artists.metadata(...)
client.search_engine.search(...)

That way the application could handle several clients at a time.

I think number 1-3 are not breaking changes and are not that hard to implement. Number 4 is a breaking change; even though the API spirit is the same, everything must refactored into this object-oriented interface. I guess you have the right to do such a change when switching to 1.0 but maybe you don't want to since you must already have a bunch of apps running on the current API...
However, if the amount of required coding frightens you, please note that:

I already have similar solutions implemented on my side that I could easily transpose to pycmc.
I'd be very happy to spend time on this project because I use the Chartmetric API a lot at my company and I'd appreciate having a stable public library for this rather than coding my custom solutions all the time.

@RomeoDespres Thank you for your thoughtful comments. There are a number of reasons for design decisions as they are and why I avoided a 1.0 release up to this point :-). Agree that we need a rewrite of credentials!
I'm buried in other dev for the next 12-24 hours, however, will have the above reviewed in detail by tomorrow morning.
Also, it seems like we have pretty similar wishes, re: public lib for CM. If you'd like, let's move this offline to chat about 1) plans for lib overall and 2) you can jump on as a maintainer here.

@RomeoDespres Terribly sorry for ghosting. Moving #15 here (and closing), as I completely agree w/combining rate limiting with this.
Let's also go for breaking changes at this point, as I'm in complete agreement with OOP approach, rather than the current pseudo-functional version we originally hacked together.
I also agree with 2 that it should be done in the same object. I'd like to create an AuthManager class that basically implements something similar to the auth_manager work in the spotipy Spotify class. I think in AuthManager it should a function to check the limit, i.e. check a set of request headers from requests and update and/or log. We can instantiate this AuthManager class in your referenced api client class, re: 4 . Let's use Client, instead of ChartmetricClient, and in the class's init we can instantiate the AuthManager.

My objective is to give the best of both worlds: each client is separately contained, along with its own auth logic and token, plus the auth manager could check for the CMCREDENTIALS environment variable. Down the road I'd like the entire lib to have a CLI interface, but that's for a later day at this point.

For reference, here are the specs from #15 :

The current credentials.py and other auth code don't consider rate limiting, which it should. We should implement a means of taking into account:

Header Name
Description

X-RateLimit-Limit
Number of requests allowed per minute on current plan

X-RateLimit-Remaining
Number of requests remaining in current time period (1 minute)

X-RateLimit-Reset
Time at which rate limit will reset

Let's consider that I'd like to nearly replicate the your client api suggestion in 4, and in particular, as the Client class that instantiates its own AuthManager and will instantiate the items in #29.

Let me know if/what you'd like to work on here. I'm going to update deps and ensure tests pass, then start chipping away at #29. I'll quote the PR here so things are clear!


Question: Is it possible to configure CORS?

Hi, y'all! First of all thanks for your great work. My first time using AWS Lambda tooling and I'm really enjoying the experience so far 😊
My question because I didn't really find anything in the docs (which makes sense as the product is rather new): is it possible to configure CORS for the local RIE docker container which holds my custom function? Once it is deployed I'd imagine you would configure this directly in AWS but until then I currently don't see a way how I'd tell it to set CORS headers.
It's not the biggest of problems, as I could just use another pass-through CORS proxy locally. I was just wondering whether this was already a supported scenario.
Thanks a lot in advance!

Still not resolved in 2023! 😭
This pull request did fix it for me: https://github.com/aws/aws-lambda-runtime-interface-emulator/pull/84/.
So I cloned the v1.13 release, make the changes from the PR, and re-made the binaries. So that I could simply add this line to my Dockerfile and it would work for my AWS lambda image.
RUN curl -Lo /usr/local/bin/aws-lambda-rie https://github.com/MecSimCalc/aws-lambda-runtime-interface-emulator/raw/msc-v1.13/bin/aws-lambda-rie && chmod +x /usr/local/bin/aws-lambda-rie

It's not ideal, but better than nothing...


[wasm, phone browser] Dimension Y value 5038 exceeds the limit of 4096

Bevy version
0.9.1
[Optional] Relevant system information

WASM build
Running in Mobile Chrome on a Samsung Galaxy S20 phone

AdapterInfo { name: "Adreno (TM) 650", vendor: 20803, device: 0, device_type: IntegratedGpu, driver: "", driver_info: "", backend: Gl }

What you did

Running my game in a desktop browser (Chrome) works fine
Running it on a mobile browser (Chrome) from the Samsung Galaxy S20 phone fails with

game-902f20548b71ecb7.js:627 panicked at 'wgpu error: Validation Error

Caused by:
    In Device::create_texture
      note: label = `view_depth_texture`
    Dimension Y value 5038 exceeds the limit of 4096

', /home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/wgpu-0.14.2/src/backend/direct.rs:2403:5

Not sure what is causing this, I'm not loading any explicit depth texture and none of my regular textures are above 4096 in size. Is this a depth texture that bevy loads somehow? Interestingly, the bevy examples from bevyengine.org do work in the same mobile browser though.

I did some digging on this back in April, here is what I found https://github.com/rust-windowing/winit/issues/2524#issuecomment-1518987014
I took another look today and was able to fix this on my Pixel device for Vanadium and Brave with Bevy 0.11 by doing a couple of things.
For my use-case I am filling the whole page with my canvas.
.add_plugins(DefaultPlugins.build().set(WindowPlugin {
            primary_window: Some(Window {
                fit_canvas_to_parent: true,
                ..default()
            }),
            ..default()
        }))

This combined with the devicePixelRatio of 2.65 was causing the wgpu texture to be too big.
To fix it I add this meta tag to the html head
    <meta name="viewport" content="width=device-width, initial-scale=1, maximum-scale=1" />

I'm not sure if the winit change was actually required because I hadn't tried the meta tag until today.
side-note: for some reason the body has a margin side by default so in my css I also add
body {
    margin: 0;
}

@jroddev I'm trying this to no success, is this still working for you using latest tagged bevy? or main branch?

@miketwenty1 I actually can no longer reproduce the problem with my example projects and my device. Tested with Bevy 10, 11, and 12.
I thought maybe it was patched on the device, but Chromium is still reporting window.devicePixelRatio  as 2.625.

I'm on bevy main branch right now. but this was still an issue for me on 10, 11, and 12. the specific device is a pixel 6 pro with a pixel ratio of 3.5.

I'm not sure, sorry. I tried again and cannot reproduce with or without my line anymore.
It could be that the resulting resolution is now supported in wgpu (snuck through in a patch version?) or by my device, but then yours is still over the limit.
Which browser are you using? and is it the stock Android OS that came with the device?
From my original testing Chromium based browsers had the issue but Firefox worked (Firefox devicePixelRatio was 1)
Just checking that the meta tag was added to the head and not the body in your index.html file?
<!DOCTYPE html>
<html lang="en">
    <head>
        <meta name="viewport" content="width=device-width, initial-scale=1, maximum-scale=1" />
    </head>
    <body>
    </body>
</html>

It's not a great solution, but if you just need to get something running you could shrink the size of the canvas on the page enough that it fits within the texture limit. I did this originally by putting a header and some extra buttons on the page until the render surface was small enough. More details on this linked comment.


Standard Volume Unit

Hello,
The instance.getVolume() method return value between 0 and 1. instance.setVolume(vol) need a value between 0 and 10. Why it is not the same volume unit ?

Good point. I'll fix this in the next major release (soon) with a few other new features as it would be a breaking change.

I'd suggest unifiying both to a range of 0 - 1 and make the volume slider accept floating point values. If a value > 1 is encountered on setVolume, you can divide by 10 for some backwards compatibilty, if needed.

I just discovered this discrepancy too. Looks like it's been in the pipe awhile. Any idea when it will land?

It's already in v3 which I should have out soon (sorry, I keep saying that)

Closing this one as I think it's fixed but feel free to re-open if not solved in v3 👍


Status of drf-json-api

Hi,
I am considering using this project, but I am concerned that the last commit to the master branch was on Feb 18, 2015. JSON API itself reached version 1.0 on the 29.05.2015. Could we get an idea of what is the development status of the project? Are there maybe other active forks?
Thanks!

Maybe not a fork but another project: https://github.com/django-json-api/django-rest-framework-json-api on the develop branch.
Full disclosure: I am an active contributor on that project

This project is dead, and it won't be coming back to life.
This project has been superseded by https://github.com/django-json-api/django-rest-framework-json-api.


npm envroment

What version is good for running ptz-server?
Almostry npm run build says...

for (let i = startIndex ?? 0; i < array.length; i++) {

ubuntu@vaio0001:~/git/ptz-server$ nvm ls
v8.17.0
v10.24.1
v12.22.12
v14.21.3
v16.20.2
->     v20.12.0
system
default -> 14 (-> v14.21.3)
iojs -> N/A (default)
unstable -> N/A (default)
node -> stable (-> v20.12.0) (default)
stable -> 20.12 (-> v20.12.0) (default)
lts/* -> lts/iron (-> v20.12.0)
lts/argon -> v4.9.1 (-> N/A)
lts/boron -> v6.17.1 (-> N/A)
lts/carbon -> v8.17.0
lts/dubnium -> v10.24.1
lts/erbium -> v12.22.12
lts/fermium -> v14.21.3
lts/gallium -> v16.20.2
lts/hydrogen -> v18.20.0 (-> N/A)
lts/iron -> v20.12.0

Any idea??

nvm install v14.21.3
nvm use v14.21.3
nvm use node v16.20.2
npm audit fix
npm install typescript -g
npm run build
and I got an error
~/git/ptz-server$ npm run build

<EMAIL_ADDRESS>build
tsc

node_modules/@utopian/visca/dist/visca-serial.d.ts:1:23 - error TS2688: Cannot find type definition file for 'serialport'.
1 ///
~~~~~~~~~~
node_modules/@utopian/visca/dist/visca-serial.d.ts:4:29 - error TS2307: Cannot find module '../../node_modules/@types/serialport' or its corresponding type declarations.
4 import SerialPort = require("../../node_modules/@types/serialport");
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Found 2 errors in the same file, starting at: node_modules/@utopian/visca/dist/visca-serial.d.ts:1

4 import SerialPort = require("../../node_modules/@types/serialport");

it seems ../../../../node_modules/@types/serialport is ok to run
Thanks a lot :)

node_modules/@utopian/visca/dist/visca-serial.d.ts:4:29 - error TS2307: Cannot find module '../../node_modules/@types/serialport' or its corresponding type declarations.
4 import SerialPort = require("../../node_modules/@types/serialport");

look ok. and next??

~/git/ptz-server$ npm run build

<EMAIL_ADDRESS>build
tsc

~/git/ptz-server$ cat  /home/mack/.npm/_logs/2024-03-29T22_45_43_712Z-debug-0.log
0 verbose cli /home/mack/.nvm/versions/node/v16.20.2/bin/node /home/mack/.nvm/versions/node/v16.20.2/bin/npm
1 info using<EMAIL_ADDRESS>2 info using<EMAIL_ADDRESS>3 timing npm:load:whichnode Completed in 0ms
4 timing config:load:defaults Completed in 1ms
5 timing config:load:file:/home/mack/.nvm/versions/node/v16.20.2/lib/node_modules/npm/npmrc Completed in 0ms
6 timing config:load:builtin Completed in 0ms
7 timing config:load:cli Completed in 4ms
8 timing config:load:env Completed in 1ms
9 timing config:load:file:/home/mack/git/ptz-server/.npmrc Completed in 0ms
10 timing config:load:project Completed in 9ms
11 timing config:load:file:/home/mack/.npmrc Completed in 0ms
12 timing config:load:user Completed in 0ms
13 timing config:load:file:/home/mack/.nvm/versions/node/v16.20.2/etc/npmrc Completed in 0ms
14 timing config:load:global Completed in 0ms
15 timing config:load:validate Completed in 0ms
16 timing config:load:credentials Completed in 1ms
17 timing config:load:setEnvs Completed in 1ms
18 timing config:load Completed in 19ms
19 timing npm:load:configload Completed in 19ms
20 timing npm:load:mkdirpcache Completed in 1ms
21 timing npm:load:mkdirplogs Completed in 1ms
22 verbose title npm run build
23 verbose argv "run" "build"
24 timing npm:load:setTitle Completed in 1ms
25 timing config:load:flatten Completed in 3ms
26 timing npm:load:display Completed in 5ms
27 verbose logfile logs-max:10 dir:/home/mack/.npm/_logs
28 verbose logfile /home/mack/.npm/_logs/2024-03-29T22_45_43_712Z-debug-0.log
29 timing npm:load:logFile Completed in 4ms
30 timing npm:load:timers Completed in 1ms
31 timing npm:load:configScope Completed in 0ms
32 timing npm:load Completed in 33ms
33 silly logfile start cleaning logs, removing 1 files
34 silly logfile done cleaning log files
35 timing command:run Completed in 3487ms
36 verbose exit 0
37 timing npm Completed in 3528ms
38 info ok

Greetings... I'm not sure I understand your question. Is everything working now?

Greetings... I'm not sure I understand your question. Is everything working now?

I cannot get any web UI with serve -s buld. because there s no build/ .

This library is not a web server. There is no serve command.

This library is not a web server. There is no serve command.

I see... How can I use ?
npm run build to be end normally...no effects...


Write a Scala program to convert days to minutes

Description
Write a Scala program to convert days to minutes
1 day = 24 hours = 1440 minutes
Input  : 5
Output : 7200

How to contribute

Save the solution in convertDaysToMinutes.scala file
Add convertDaysToMinutes.scala file in convert-days-to-minutes folder

Hey @Chirag8023,
This issue has been assigned to you for more than 15 days.
We are unassigning you from this issue.
If you are still interested in contributing to this issue, please get auto-assigned on the issue by commenting !assign again.
Thanks for your contributions :)

!assign


cert-manager: fast-forward to upstream 67e55190

Automated cherry pick of #577 (jetstack/cert-manager#578)

/lgtm


No right on red

In most places outside North America, as well as in NYC, Montreal, and Mexico City, right turns are not permitted on red except where specifically indicated. This PR adds a map config option for turn on red which is true by default and false for nyc (need to add the others).
It then ignores yield turns which don't share a stage with a (green) protected stage in make_stages. This doesn't affect the traffic signal generators which don't use make_stages. Perhaps it would be better to do even less, and just alter the literals in four_way_two_stage etc?

Nice! The results look correct in NY.

Perhaps it would be better to do even less, and just alter the literals in four_way_two_stage etc?

I like the simplicity of the implementation right now. We could add conditions to
        vec![
            vec![
                (vec![north, south], TurnType::Straight, PROTECTED),
                (vec![north, south], TurnType::Right, YIELD),
                (vec![north, south], TurnType::Left, YIELD),
                (vec![east, west], TurnType::Right, YIELD),
            ],
            vec![
                (vec![east, west], TurnType::Straight, PROTECTED),
                (vec![east, west], TurnType::Right, YIELD),
                (vec![east, west], TurnType::Left, YIELD),
                (vec![north, south], TurnType::Right, YIELD),
            ],
        ],

but I think it would hurt readability a bit. make_stages already makes other transformations like swapping left/right in the UK. So I'm in favor of the way you've written it.

This doesn't affect the traffic signal generators which don't use make_stages

We could alternatively filter out the yield turns at the end of get_possible_policies, near // Make sure all possible policies have a minimum crosswalk time enforced. That would also handle greedy_assignment and others. I don't think this is too important, since if all the generators using make_stages fail and the first working policy is one of these other ones, the results aren't realistic anyway.

This PR adds a map config option for turn on red which is true by default and false for nyc (need to add the others).

Right, in terms of merging this PR, we need to

Update all of the config files... which is getting quite annoying to do frequently. Maybe it's time to rethink this config. Most places use defaults, but they have to be manually copied around.

Regenerate all the maps, since adding to MapConfig is binary incompatible

I updated the config files. I'll try and regenerate all the maps tonight, then merge this in.
I'm also looking into ideas for cleaning up all the map config and the maintenance burden of adding fields...

I changed the non-US maps to "turn_on_red": false

Awesome! Regenerating all the maps now, then I think we can merge?

Thanks for the PR! This is a nice step towards more accurate modelling especially outside the US. I've regenerated all the maps, since the binary format changed. Merging!


fix: running with deno v0.34.0 's strict mode

includes updating get-aws-config to v0.3.5

#4 also makes strict mode tricky on the user side.

Happy to help on this if you can get deno deps.ts running on 0.34.0+ (i.e. update your dependencies to support strict mode).


3D Audio

I would like to let you know that we successfully presented a demo of our metaverse using Agora, the project is getting bigger.
We are in contact with your customer support and they told us that the SDK 4.0 was release so we can start working with the 3D Audio, which is the feature that we want to use for the next release.
I see that you have something called "Spatial Audio" but not sure how it works; if that's similar to and audio 3d or if you are gonna have something else or what we can do to have this feature.

You can see a demo called spatialaudio, you can try it, you plug in the headphones and enter the demo. Then another client enters the room. Click left or right. You can hear the sound from the left or right earphone. Thanks for your use. Please click star if possible, it's important to me.

How do I click the star?
We tried that but it was not working, I'm gonna try again.
I guess I can use maths to simulate the effect into a 3d space, but do you have any considerations or planning something to get that to work in a 3d space?

It can work in 3d space, you only need to pass the vector3 of the object to convert it into a float array to the sdk, this part may be calculated by yourself. And the star I said refers to the github star and not elsewhere

Oh now I remember the issue with the spatial audio. I could not get it to work.
I can only hear the voice if I join to a normal audio channel.
If I try to join using the spatial audio interface is not working. How is this suppose to work?

èngcháng de?
 And if both segments are spatial sound demos, won't it work? Also, I saw the picture you shared and it seems that the uid at both ends are the same. Are you sure it is normal?

èngcháng de?
 And if both segments are spatial sound demos, won't it work? Also, I saw the picture you shared and it seems that the uid at both ends are the same. Are you sure it is normal?

You can try this function with headphones

Yeah, I'm using headphones.
What I wanna say is that I can't hear anything if I try to join using the spatial audio. I can only hear the other person if he join to a normal call, because of using the same channel..
So I don't know what do I need to do to get the spatial audio working.

sorry,you can add this code to fix this bug，we will fix next version

Cool, it was working


Testing attachment in the shell?

Is there a way to test the slack attachment (custom message) in the shell?
For some reasons, all my attempts were unsuccessful, but maybe I do something wrong. Any example would be nice if this is something possible.

I don't believe there is. The slack attachment is specific to the slack adapter. When using the shell adapter the ability to emit slack attachments simply isn't there.
For some of my scripts I've added logic to test for a slack adapter before attempting to emit an attachment. This, of course, defaulting to sending an unformatted messaged if the adapter doesn't exist.

Here's an example
if robot.adapterName == 'slack'
    robot.emit 'slack-attachment',
      message: msg
      content: mySlackAttachment
else
  msg.send "An alternative message"

You can of course always use Message Builder to test out your messages.
Closing as resolved.


Implement canonicaljson serialization

See ga4gh/vr-schema#31 for details.

Actual proposal is now here:
https://github.com/ga4gh/vr-schema/issues/31#issuecomment-491962997