Adding infinite list behavior

Overview

Adding infinite scroll list behavior that @meomix created

Oh jeeze. No pressure or anything :p I think there might be a slight optimization I can make to this after I refactor to use onAttach, but cool! Exciting!! :D :+1:

I figured it's better to have it then not have it at all :) We can make optimizations over-time. Make it work then make it better. Which area are you talking about for using onAttach?

IIRC children get added to a CollectionView before the CollectionView is shown which was making the initial bout of _addChild all result in no-ops because minRenderIndex and maxRenderIndex had yet to be calculated. Then, onShow triggers, and runs through the collection again and figures it all out.
I remember talking to jmeas about this and him saying this would change at some point. That might be a v3 thing, but it might be with onAttach, too. So, gotta take a look.

So good. Merging so we can all play!

:+1:
My largest complaints with it right now are:

You need to explicitly tell it what the size is of your ItemView being rendered and they all need to be the same size.
I defer running some of the logic in OnCollectionRemove to prevent an off-by-one which sucks.
There's a bug regarding adding a model to a collection at a specific index which can be fixed by calling sort on the collection afterward (because that causes the implementing view to re-draw itself). The issue is that the index the model is being added at in the collection is not the same as the index that the ItemView is being added at in the CollectionView if minRenderIndex is > 0. You can see a comment I made regarding that here: https://github.com/MeoMix/StreamusChromeExtension/blob/master/src/js/foreground/view/behavior/sortable.js#L150

I have to wonder if it would be better to just aggressively re-render the view instead of trying to do a bunch of math to try and touch a smaller amount of elements during specific events.
Anyway, just some things to think about. Would love to have more eyes on this code and happy to answer questions, but I've put more than enough hours into this by myself at the moment. :)


Reciprocation in Identification not working

I create L Agnanum. I make Identification - certain with L Aglanum. Under Aglanum, no reciprocation back to Agnanum appears. The link should be symmetrical and editable (removable) from both sides, and the certainty is the same both ways (it is actually the same relation).
I think we have seen with Adam that also elsewhere, reciprocations, already checked OK once, ceased to work in the last couple of months also for other relations.
Top priority - this prevents us from checking the correct import of gsheets data for Hackathon 3 (checking due in mid-January).

can you please confirm if Subject/Actant1 Reciprocal should also be symmetrical?

Yes, SubjectActant1Reciprocal is symmetrical. E.g.: if "tell sb st" has the SubjectActant1Reciprocal "hear from sb st", then "hear from sb st" has the reciprocal "tell sb st".

fixed in c829d714129e9bab2f8053964420a6c734cd81e1


Merge prTesting_201903040931 branch to master branch

OPS Build status updates of commit 69e5386:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details
Dependent Files

split/updateTestRef.md
:white_check_mark:Succeeded

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


Implement Merchant Page

I created a merchant page which is a subsect of our documentation page, where we talked about the various e commerce stores from which Haggle makes comparism across


[SPARK-42084][SQL] Avoid leaking the qualified-access-only restriction

What changes were proposed in this pull request?

This is a better fix than https://github.com/apache/spark/pull/39077 and https://github.com/apache/spark/pull/38862
The special attribute metadata __qualified_access_only is very risky, as it breaks normal column resolution. The aforementioned 2 PRs remove the restriction in SubqueryAlias and Alias, but it's not good enough as we may forget to do the same thing for new logical plans/expressions in the future. It's also problematic if advanced users manipulate logical plans and expressions directly, when there is no SubqueryAlias and Alias to remove the restriction.
To be safe, we should only apply this restriction when resolving join hidden columns, which means the plan node right above Project(Join(using or natural join)). This PR simply removes the restriction when a column is resolved from a sequence of Attributes, or from star expansion, and also when adding the Project hidden columns to its output. This makes sure that the qualified-access-only restriction will not be leaked to normal column resolution, but only metadata column resolution.
Why are the changes needed?

To make the join hidden column feature more robust
Does this PR introduce any user-facing change?

No
How was this patch tested?

existing tests

cc @viirya @gengliangwang

@cloud-fan I feel the qualifiedAccessOnly attributes are still complicated. We have to check them here and there. Since it is for certain Joins only, shall we decouple it from the metadataOutput and have a new TreeNode method to infer these hidden lists? E.g. hiddenOutputFromJoin. In this way, we don't need to mark whether an attribute is qualifiedAccessOnly.

It's more tricky to do it at the plan level, as you need to define which operators are allowed after natural/using join to access the hidden columns, an you will hit the same "when to remove restriction" problem.

You will need to re-implement a propagation framework, as not only the direct parent of the join can access the hidden columns. e.g. Sort -> Project -> Join, we can sort by the join hidden column

OK, let me think more on this recently. I feel that mixing the V2 metadata columns and the hidden join columns are hard to maintain. A bit of duplicate code for the propagation can make future development easier.

thanks for the review, merging to master/3.3!


Please invite me to the community

Name
Tran Nguyen Thuong Truong - @thuongtruong1009
Discord Username (if applicable)
thuongtruong1009
Additional Context
Hi guys!
Nice to meet you!
Let's go 🚀

Welcome to the Community!


chai3 released yet

temporary npm install chai3-json-schema

+1

Even though "npm install chai-json-schema" throws an error with the peer dependencies, it does install and appears to work. Should be a simple matter fix.

Can we get this version into bower?

Anyone want to take ownership and get this sorted? See https://github.com/Bartvds/chai-json-schema/issues/23


Hours only view in TimePicker does not hide separator

Environment

Tech
Version

@material-ui/pickers
3.1.2

material-ui

React
16.8.6

Browser
chrome

Peer library
moment 2.24.0

Steps to reproduce
1.set views={["hours"]}
2. open TimePicker
Expected behavior
tool bar contains hours figures only
Actual behavior
tool bar displays separator too. e.g "08:" instead of "08"
Live example
https://codesandbox.io/embed/material-ui-pickers-usage-demo-um132

Closed by #1161


Implement your portfolio panel UI

BLOCKED BY #131
Changes

Created and added your portfolio panel in portfolio screen
Integrate your portfolio API with UI

Screen
Desktop

Mobile

Wallet Not Connected

refs oursky/likedao#141

@hochiw updated 🙇♂


Dialogic.Audio.base_music_player.volume_db = new value does not work anymore

Dialogic.Audio.base_music_player.volume_db = new value used to work in previous version of dialogic, now it doesn't do anything. And I do not know how to adjust global music or sounds.
Godot v4.2.2.stable - Ubuntu 22.04.4 LTS 22.04 - X11 - Vulkan (Forward+) - dedicated NVIDIA GeForce GTX 1060 3GB (nvidia; 535.183.01) - AMD Ryzen 9 3900X 12-Core Processor (24 Threads)
version="2.0-Alpha-15 WIP (Godot 4.2+)"

The correct way to adjust the volume it to adjust the volume of the Audio Bus that the music_player is on.
https://docs.godotengine.org/en/stable/tutorials/audio/audio_buses.html
Here is an explanation of how audio settings can be implemented: https://github.com/Jowan-Spooner/Dialogic2FantasyTemplate?tab=readme-ov-file#audio-settings

Thank you. That solved the issue


Fixes support for material-ui@5

Fixes #72 by extending #88

Working for me too. Thanks @varevarao !

@Neodern how did you do? I cannot achieve to make it works

@Jerome1337  what is the problem you're having and what did you try?
Please note, SSR may not work yet. That's still in progress.

@bherila I tried to require the master branch with npm/yarn without success so I cannot test if it's working on my project.

Please note, SSR may not work yet. That's still in progress.
Oh ok, thanks for the info!

Most likely, I won't have time to continue working on this until the weekend. If you need something sooner, please implement it and send a PR 🙏

@bherila We just need a new release from master to support material-ui v5.
Without this release we cannot use this lib with Mui@5

We need @alexplumb  to make the release, I don't have permissions on the npm module
@alexplumb  can you add me to the npm so I can at least release pre-release packages off master?
Also, I can help set up CI/CD off master branch here.

What's your npm username? I'll add you as a maintainer on that

@alexplumb  it's bherila, same as github


I wish /docs/user-guide/services/ would have better images because they seem to be cut in half

I wish /docs/user-guide/services/ would have better images because they seem to be cut in half

Fixed in https://github.com/kubernetes/kubernetes.github.io/commit/55020cc414e356a310bee6e71c009e1ab5d9e07d

Awesome, thanks!


'autolink' doesn't work

<!-- MarkdownTOC autolink="true" bracket="round" -->

- [variable \](#required\)

<!-- /MarkdownTOC -->

# variable \[required\]

should be
<!-- MarkdownTOC autolink="true" bracket="round" -->

- [variable\[#required\]](#variable-required)

<!-- /MarkdownTOC -->

# variable \[required\]

On GFM, [and] seems to be  escaped always, but this is conflicting Markdown specification maybe.

Idea

Separate GFM mode and Original Markdown mode

including autolink=true and bracket=round

Fixed in 3.0.0.


Add template for when customer-managed IngressController cannot run

Adds new template to cover instances of customer-managed ingresscontrollers lacking secrets/certs needed to run the router pods.

/lgtm
/approve


[Query Fuzz] Query doesn't return

This issue was found by fuzzing the database with a query generator tool. It may be possible to simplify the query to help identify the root cause.
Dataset
$ curl https://s3.amazonaws.com/noaa.water-database/NOAA_data.txt -o NOAA_data.txt
$ influx -import -path=NOAA_data.txt

Query
SELECT    BOTTOM("degrees", "location", 5)  AS "_",   NON_NEGATIVE_DERIVATIVE("degrees") +   STDDEV("water_level") FROM  "h2o_temperature"

Results
The query hangs. Heap remains low, no CPU activity.
Possibly related to #8061 but there is only one BOTTOM, so it's possible this is a different issue.
1488220069229540178-freeze.txt

I think this query shouldn't be possible. @jwilder thoughts? I'm of the opinion that anything involving TOP() and BOTTOM() should just be by themselves.


Rustup to rustc 1.14.0-nightly (f09420685 2016-10-20)

This includes a revert of https://github.com/rust-lang/rust/pull/37132.


Initial setup

Everything is looking pretty good so far. Only a few suggestions so far with what exists:

You should have an assets folder that holds everything that is not an HTML file (for now)
assets/css
assets/images
assets/misc

be sure to link the javascript for Bootstrap under your body tag. Generally, you will need this.

For an extra challenge try to FIRST create a branch to handle these changes with the steps discussed in slack (listed below)

create a branch from master
Change only 1 specific task
commit (however many it takes)
open a pull request pointed to the base master
send a technical lead/peer the PR number or tag them in the PR
once approved merge into master

thank you antonio!!!!!

Bootstrap JavaScript link should be placed under body and not in the head?
Get Outlook for iOShttps://aka.ms/o0ukef

From: Steph L<EMAIL_ADDRESS>Sent: Saturday, April 25, 2020 1:02:01 PM
To: pagevanhoy/pagevanhoy.github.io<EMAIL_ADDRESS>Cc: Subscribed<EMAIL_ADDRESS>Subject: Re: [pagevanhoy/pagevanhoy.github.io] Initial setup (#1)
thank you antonio!!!!!
[takingnotes]https://user-images.githubusercontent.com/58382657/80287067-e75d1200-86f4-11ea-817e-1c3bf9ab94cc.gif
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHubhttps://github.com/pagevanhoy/pagevanhoy.github.io/issues/1#issuecomment-619418257, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AM73CIBDO3EWRD3EUJ2PS5DROMQRTANCNFSM4MPPEWCQ.


Bruce's Secret ... s

Bruce's Secret Kung Fu ... AKA:
https://hkmdb.com/db/movies/view.mhtml?id=16748&complete_credits=1&display_set=eng
contains footage from:
-)Bruce's Fingers
-)Bruce and the Shaolin Bronzemen

Bruce's Fingers ... AKA:
https://hkmdb.com/db/movies/view.mhtml?id=9710&complete_credits=1&display_set=eng

Bruce and the Shaolin Bronzemen ... AKA:
https://hkmdb.com/db/movies/view.mhtml?id=10184&complete_credits=1&display_set=eng


ONNX 1.8 support timeline

Hi all. We're wondering if there is a timeline or plan for moving to ONNX 1.8.X? We've looked into this locally, and unfortunately, unlike the ONNX 1.7 move, there are some substantial changes required, even without moving to new operator versions. There is a separate issue that the version 13 operator set introduces a number of significant semantic changes, but those can be adopted later or not at all. We're happy to help with the patch, but it touches a lot of core areas. Thanks!

A related question: is there any plan for supporting multiple ONNX opsets? Any ONNXMLIR-based tool will need to eventually support ONNX models using earlier opsets, instead of just a single (current) opset. Some of the op-changes in ONNX1.8 break compatibility: e.g., the treatment of "axes" has changed for reduction ops like ReduceSum. If onnxmlir migrates to ONNX1.8, instead of throwing away the lowering-support for the earlier form of ReduceSum, it would be better to just add support for the newer form. But this requires some design decisions on how to support it. One solution would be to generate different dialects for each opset. Another would be to have a single dialect, with different ops (e.g., ReduceSum12 and ReduceSum13).

@NathanielMcVicar I will be very glad to collaborate on this. Which operations did you implemented?

@gramalingam As for the multiple versions support, here are our thoughts:

We will focus on support "the latest" version. That means we will keep upgrade onnx-mlir following onnx.
As for different dialects for different versions, it is difficult for us to maintain the optimization code. For example, we need write rule for all the dialects. If a new lowering is introduced, all the dialects need to be updated.
Our current plan is to use converter to transform lower version to the version onnx-mlir is supporting. The good thing with this approach is that compiler code is clean. The disadvantages include that converter code may not be available and it is always guaranteed  (I think in theory) we can write converter for all operations.
I think v11 ReduceSum can be converted to v13 ReduceSum by convert the attribute to constant and use it an input. Is that correct?
I noticed some code in Build that handles the optional input with default value need to be changed when we move to new version. I might keep those code in certain way so that we can import different version operation if we define operation for them.
@gramalingam @NathanielMcVicar You already have some experience for versioning.  We can discuss and collaborate more on this topic.

Agreeing with @chentong319 opinion.
On supporting multiple ONNX opsets, my hope is that we can handle most of the ops by up converting older ops to a newer version, so that we may have as few operations as possible. This is borne by the experience that the more ways that exist to do something similar, the more likely something is not going to be fully tested when some new optimization is brought online.
When an operation is too different from prior one, meaning we cannot convert an old one in a newer one, then we will have to maintain two operations, with two distinct names to maintain the past behavior and the newer behavior.
The idea of two dialects seems to introduce more redundancy to me, maybe there is a way to have it so that most ops are reused, an idea to be maybe pursued a bit further. It might be a solution if we can introduce a version specific dialect, and then use MLIR rules to automatically convert them in the latest version. But having two or more ONNX dialects that needs to be handled separately all the way to their lowering to KRNL and eventually affine/vector/standard, that does not seem attractive at all to me.

It looks like the ONNX 1.8 patch is incoming #575. It looks like we have the Expand op, and maybe some others (I need to count) ready to go. Would it make sense for us to start submitting PRs for individual ops once 575 lands? Thanks!

@NathanielMcVicar Yes, I think if you have patches ready to go it would be great to submit PRs for them.

I'm going to close this, since 1.8 specifically is no longer relevant, and future discussion of supporting multiple opsets can continue in #708.


Homebrew forumula not available?

Hey there. I just ran brew update and brew install docker-cloud per the readme, but the formula isn't found.
Any clue when it will be up or what the correct name of the formula is?
Thanks!

@masondesu
I sent a PR to homebrew:
https://github.com/Homebrew/homebrew/pull/48966
The cli will be available when it is merged.

It is now available on brew


QUESTION: POPULARITY via 噂（うわさ）causes "VIP" treatment?

NO.
1) JAPAN EXAMPLE
remembers: in JAPAN, where being seen eating lunch with female classmate from NORWAY,
--> caused: noticeable CHANGE in treatment from Japanese people,
--> via: increase in popularity via UWASA (rumors);
--> however, excess causes ERROR,
--> via thinking "VIP" treatment based on UWASA
--> shall also include increased assistive ACTION from people;
--> recommends: 独（どく） GERMANY TECHNIQUE,
--> where: self is STRONG to be assistive to neighbors;
REMINDER:
people execute incorrect actions (intentional or non-intentional);
--> cautions: against people classified to be LIARS;
--> where: LIARS = continuous LYING;
2) U.S.A. EXAMPLE
remembers: JOKE from U.S.A. to also exist,
--> where: NEW PEOPLE who moved into the NEIGHBORHOOD,
--> are welcomed via SCARY ACTION, e.g. attempted "THEFT";
--> adds: finishes QUICKLY if JOKE (NOT over 1 year)
3) Social Networking Service (SNS) EXAMPLE
notes: technique to cause another to identify self with select parts of text;
--> remembers: FB social media, et cetera;
--> recommends: as with self, opt to IGNORE to GAIN TIME for another ACTION with VALUE;
--> notes: thinking and thinking, without clarification; EXCESS USE OF TIME;
--> adds: JWONG IN JAPAN - PLAYING AT BIGONE: SFII BATTLE @BIG ONE ARCADE,
--> where: even understanding nihongo does NOT immediately cause self to identify the object of conversation;
--> adds: DIRECT clarification faster;
--> adds: IF TRIVIAL/SOLVED (e.g. NO SUPER METER, FEMALE MUSCLE), ignore by person;
Health,
SYSON, MICHAEL B.


Fix infinite join retry

This changes behavior.
What's wrong with the original code, is that if retries == 0, it goes in infinite mode. I'd suggest introducing an attempts variable set to retries + 1 and check retries == -1 || attempts-- > 0

In the original code any positive value will make it go into an infinite retry. The original check was just wrong.
The fix does not change the behaviour. Confirmed on a device:
ttn.join(appEui, appKey, 2, 10000); - Tries 2 times to join.
ttn.join(appEui, appKey, 0, 10000); - Does not try to join.
ttn.join(appEui, appKey, -1, 10000); - Infinitely tries to join.
ttn.join(appEui, appKey, -2, 10000); - Does not try to join.
ttn.join(appEui, appKey); - Infinitely tries to join.

I think I see the issue. "Try" vs "retry".
"Number of times to retry after failed or unconfirmed join. Defaults to -1 which means infinite."
So according to the documentation if the value is 0, you want it to try to join once.

Behaviour is now:
ttn.join(appEui, appKey, 2); - Tries 3 times to join.
ttn.join(appEui, appKey, 0); - Tries 1 time to join.
ttn.join(appEui, appKey, -1); - Tries infinitely to join.
ttn.join(appEui, appKey, -2); - Tries 0 times to join.
Also did a minor version number bump.


Unsupported operation 'blpop'

Will be awesome to have blpop and brpop implemented here

https://github.com/fppt/jedis-mock/pull/43

Addressed in your PR - thanks for that - and release in v0.1.13


Benchmark assets

Remove some code we don't use.
Remove benchmarks for already removed extrinsics.
Fixup remaining benchmarks.

@deepink-mas shouldn't this include the newly generated weights?

I haven't gotten to that yet. I need to check that the benchmarks still match the extrinsics and that each extrinsic has a benchmark (mostly for the other DAO crates) and then I can run them to produce new numbers.

Actually reading a bit more about producing weights through benchmarks (https://docs.substrate.io/test/benchmark/, https://github.com/paritytech/substrate/tree/master/utils/frame/benchmarking-cli), it seems that the idea is that you run the benchmarks on the machine that will actually run the node. Therefore it seems pointless for me to actually run the benchmarks to produce weights. I've made sure that the benchmarks compile and run, so if someone wanted to benchmark it should work.


Read() doesn't adhere to io.Reader specifications

Hi,
I noticed that Read() does not adhere to the io.Reader specifications;.
The specification says Read reads up to len(p) bytes into p (source)
Meanwhile, the library's Read() does the following (source)
		min := len(p)
		if len(p) < r.outBuffer.Len() {
			min = r.outBuffer.Len()
		}
		copy(p, r.outBuffer.Bytes()[:min])

Consequently, the read could be larger than len(p).
I'm wondering whether this deviation is deliberate?
Thanks!

You actually found a bug there. The if statement should not use lesser-than but greater-than. I've fixed it in the latest release.


Umbrel: curl / IP verification timing out

Systeminfos:

Umbrel (native linux)
Tailscale (deactivated after TS error)

setup script ends with:
Verifying tunnel ...
> ERR: TunnelSats VPN interface not successfully activated, please check debug logs

manual execution:
$ sudo docker run -ti --rm --net=docker-tunnelsats curlimages/curl https://api.ipify.org
  curl: (28) Failed to connect to api.ipify.org port 443 after 278832 ms: Operation timed out

restarting Umbrel:
creating network "umbrel_main_network" with the default driver
ERROR: Failed to Setup IP tables: Unable to enable SKIP DNAT rule:  (iptables failed: iptables --wait -t nat -I DOCKER -i br-fcc540e07644 -j RETURN: iptables: No chain/target/match by that name.
 (exit status 1))
Failed to start containers
Skipping status update when not on Umbrel OS

wg stats:
allowed ips: <IP_ADDRESS>/0, ::/0
latest handshake: 13 minutes, 36 seconds ago
transfer: 220 B received, 308 B sent

DNS entry required


[bug] Memory leak? FATAL ERROR: MarkCompactCollector: young object promotion failed Allocation failed - JavaScript heap out of memory

Version
Checklist:

[x] I am not using HomeAssistant. Or: a developer has told me to come here.
[x] I have checked the troubleshooting section and my problem is not described there.
[x] I have read the changelog problem was not mentioned there.

Build/Run method

[x] Docker

zwavejs2mqtt version: latest docker image, can't open control panel due to this bug so I cannot check exactly
zwave-js version: latest docker image, can't open control panel due to this bug so I cannot check exactly
Describe the bug
Whenever I try to start the Docker container, I get the following fatal error:
<--- Last few GCs --->

[1:0x55a7f40]    23467 ms: Scavenge 998.1 (1035.9) -> 996.3 (1036.9) MB, 18.3 / 0.0 ms  (average mu = 0.911, current mu = 0.785) allocation failure
[1:0x55a7f40]    23509 ms: Scavenge 999.2 (1036.9) -> 998.2 (1041.6) MB, 23.4 / 0.0 ms  (average mu = 0.911, current mu = 0.785) allocation failure
[1:0x55a7f40]    23714 ms: Mark-sweep 1003.8 (1041.6) -> 1002.0 (1048.9) MB, 168.6 / 0.1 ms  (average mu = 0.857, current mu = 0.701) allocation failure scavenge might not succeed

<--- JS stacktrace --->

FATAL ERROR: MarkCompactCollector: young object promotion failed Allocation failed - JavaScript heap out of memory

free -h:
              total        used        free      shared  buff/cache   available
Mem:          7.6Gi       1.6Gi       3.8Gi       157Mi       2.3Gi       5.7Gi
Swap:         2.0Gi          0B       2.0Gi

My platform is a Raspberry Pi 4 - 8GB.
To Reproduce
Steps to reproduce the behavior:
Unclear how to reproduce this bug, it started happening after +/- 2 weeks of run time.
Expected behavior
I expect the Docker container to start successfully, not crash and restart non-stop.
Additional context
Relevant docker logs:
-- Logs begin at Wed 2021-03-31 13:15:38 CEST, end at Wed 2021-03-31 13:26:30 CEST. --
Mar 31 13:15:46 pi dockerd[939]: time="2021-03-31T13:15:46.704329902+02:00" level=warning msg="Your kernel does not support cgroup memory limit"
Mar 31 13:15:46 pi dockerd[939]: time="2021-03-31T13:15:46.704400754+02:00" level=warning msg="Your kernel does not support cgroup rt period"
Mar 31 13:15:46 pi dockerd[939]: time="2021-03-31T13:15:46.704479087+02:00" level=warning msg="Your kernel does not support cgroup rt runtime"
Mar 31 13:15:46 pi dockerd[939]: time="2021-03-31T13:15:46.704512717+02:00" level=warning msg="Your kernel does not support cgroup blkio weight"
Mar 31 13:15:46 pi dockerd[939]: time="2021-03-31T13:15:46.704543013+02:00" level=warning msg="Your kernel does not support cgroup blkio weight_device"
Mar 31 13:16:39 pi dockerd[939]: time="2021-03-31T13:16:39.605584622+02:00" level=info msg="ignoring event" module=libcontainerd namespace=moby topic=/tasks/delete type="*events.TaskDelete"
Mar 31 13:16:39 pi dockerd[939]: time="2021-03-31T13:16:39.619436882+02:00" level=warning msg="e7963ea21f4f903b8ae6aba58422378c1edc19347b772083925b810cacf9e5a8 cleanup: failed to unmount IPC: umount /var/lib/docker/containers/e7963ea21f4f903b
Mar 31 13:17:07 pi dockerd[939]: time="2021-03-31T13:17:07.664080324+02:00" level=info msg="ignoring event" module=libcontainerd namespace=moby topic=/tasks/delete type="*events.TaskDelete"
Mar 31 13:17:07 pi dockerd[939]: time="2021-03-31T13:17:07.695350782+02:00" level=warning msg="e7963ea21f4f903b8ae6aba58422378c1edc19347b772083925b810cacf9e5a8 cleanup: failed to unmount IPC: umount /var/lib/docker/containers/e7963ea21f4f903b
Mar 31 13:17:42 pi dockerd[939]: time="2021-03-31T13:17:42.900951986+02:00" level=info msg="ignoring event" module=libcontainerd namespace=moby topic=/tasks/delete type="*events.TaskDelete"
Mar 31 13:17:42 pi dockerd[939]: time="2021-03-31T13:17:42.941397827+02:00" level=warning msg="e7963ea21f4f903b8ae6aba58422378c1edc19347b772083925b810cacf9e5a8 cleanup: failed to unmount IPC: umount /var/lib/docker/containers/e7963ea21f4f903b
Mar 31 13:18:22 pi dockerd[939]: time="2021-03-31T13:18:22.756910611+02:00" level=info msg="ignoring event" module=libcontainerd namespace=moby topic=/tasks/delete type="*events.TaskDelete"
Mar 31 13:18:22 pi dockerd[939]: time="2021-03-31T13:18:22.799604271+02:00" level=warning msg="e7963ea21f4f903b8ae6aba58422378c1edc19347b772083925b810cacf9e5a8 cleanup: failed to unmount IPC: umount /var/lib/docker/containers/e7963ea21f4f903b
Mar 31 13:19:02 pi dockerd[939]: time="2021-03-31T13:19:02.836339345+02:00" level=info msg="ignoring event" module=libcontainerd namespace=moby topic=/tasks/delete type="*events.TaskDelete"
Mar 31 13:19:02 pi dockerd[939]: time="2021-03-31T13:19:02.864552733+02:00" level=warning msg="e7963ea21f4f903b8ae6aba58422378c1edc19347b772083925b810cacf9e5a8 cleanup: failed to unmount IPC: umount /var/lib/docker/containers/e7963ea21f4f903b
[is spammed continously]

After enabling the memory cgroup I can actually monitor the memory usage of the container. After ~10 seconds it is at ~1.2GiB
e7963ea21f4f        zwavejs2mqtt        93.28%              1.214GiB / 7.64GiB   15.89%              0B / 0B             0B / 0B             11

At which point it is killed.

Apologies for the spam, the issue was that in the mqtt folder, the outgoing file was 1.9GB as the system had lost connection to MQTT for some amount of time, and then it rebooted. There are a lot of nodes in the network so I guess the messages accumulated quite quickly.
I guess there a few options here:

Limit the file size of the mqtt buffer
Don't try to read the entire buffer in one go
Split up the buffer in multiple files

Also by default db doesn't have a way to limit it's size, it keeps storing messages while iit's offline. I suggest you to keep that disabled, I dunno if I will fix that as it's a problem on mqtt side

Duplicate of #220


Can't log in normally on the app

After logging into the account on the app, it will go to the web version. After logging out and returning to the app, the app is still not logged in. Or is it designed like this now? My account has many online collections, but logging in on the web version is too uncomfortable.  Can you fix this bug and go back to the past, can you keep your account logged in on the app? Please, this is really important to me

Try clear the cache and cookies


OS X 10.11 Audio Warning

When compiling a test app with sfml-audio the following warning is put in the console:
WARNING:  140: This application, or a library it uses, is using the deprecated Carbon Component Manager for hosting Audio Units. Support for this will be removed in a future release. Also, this makes the host incompatible with version 3 audio units. Please transition to the API's in AudioComponent.h.
It seems to be an issue with 10.11.x only, but I'm not sure.
I'm running OS X 10.11.6 with Xcode 7.3.1

You are more than welcome to discuss your issue on the forum first as we try to keep this issue tracker for confirmed issues only. The procedure to open a bug/feature request is explained in the contribution guidelines. Thanks.
Note: This was discussed in #1000 and fixed with its related PR. Make sure you use latest master version when testing.


Feature/#656 allow an entity to have multiple relations to the same entity

Not ready to merge yet


support for catchcn ensemble run

Correct the child name for different ensemble members of catchcn

@gmao-rreichle It is not ready yet. Some variables need to be bubbled up to the Land grid comp so the GEOSens grid comp can see them.

I successfully 0-diff tested the branch at the current commit https://github.com/GEOS-ESM/GEOSgcm_GridComp/pull/645/commits/ba5672bdb1213510b1e6ba83b0f0793dd19c2b70
@gmao-jkolassa successfully exercised the new functionality after the initial commit https://github.com/GEOS-ESM/GEOSgcm_GridComp/pull/645/commits/dca3508f36524f940640a387d47441359d587655
Since @weiyuan-jiang just reported that additional changes will be needed, testing will need to be repeated later.

This PR depends on the PR on MAPL https://github.com/GEOS-ESM/MAPL/pull/1683


Prep 1.3.0 release

I'm planning on releasing tomorrow, thus the changelog date.

IE 11 test failure looks like?

@rictic yeah, I think it's a flake. A timer didn't fire. First time I've seen that test flake though.


Fixed format of 'base64' to correct 'byte'

@handrews

I'm not sure if we have an issue tracking that, if not I'll file one today.

#1547?

@hkosova that's at least related.  I didn't manage to file an issue but I discovered a 2/3rds done PR in my local repo.  Wonder when I did that... I'll try to post that soonish.

@smhc all of this stuff is in the middle of being changed around for OAS 3.1, that's why it doesn't make any sense right now.

Let me finish updating this section with my PR that aligns it with previous work done to update OAS 3.1 to use the latest JSON Schema.  If it still doesn't make sense, let's work through it then.

This is being addressed as part of PR #2200, which drops "format": "byte" entirely in favor of "contentEncoding": "base64".  contentEncoding is more flexible, and compatible with the latest JSON Schema (which will be used in OAS 3.1).
If there will be an OAS 3.0.4, then a decision on byte vs base64 is needed, as tracked by #1547, followed by a PR against the appropriate branch.  That issue still has not resolved which of byte or base64 was intended.  Since this is not against the right branch for 3.0.4 and it's not clear which value is correct, I'm closing this.  We'll need a PR against the right branch depending on the outcome of #1547.


Add support for showing hidden files in dialog

There's no option to show the hidden files in the dialog.showOpenDialog currently. Here is an example:

BTW, is it possible to add a description in the dialog (just like the text "Choose a custom SSH key..." in the above image)? Tried the title option but it seems not showing at all (OS X).

Just curious... Does OS X's built in hotkey command, ⌘ CMD + ⇧ SHIFT + ., show the hidden files?
For reference: http://apple.stackexchange.com/questions/186376/hotkey-to-show-hidden-files-and-folders-in-file-open-dialog

BTW, is it possible to add a description in the dialog (just like the text "Choose a custom SSH key..." in the above image)? Tried the title option but it seems not showing at all (OS X).

The title should show in the titlebar if the dialog is not attached to a browserWindow.

I think the behavior of the title field is correct. Mac OS X exposes a native API for adding custom views to the bottom portion of the open/save dialogs, but I doubt Electron can support that in a generic way.
@manovotny :  command-shift-. does work to show hidden files.

How about dialog.showSaveDialog?


Update dependencies to M93

(Working on updating the readme file, stand by for that.)

Also need to update cpp_version_sdk.json

Done.


chore: split CanonicalEmbedding

#11873 seems related

Hum, indeed... I guess I am too late :)


fix(material/chips): show checkmark for selected non-selectable chips

Fixes that chips that were selected programmatically, but were set as selectable="false" weren't showing the checkmark as intended in https://github.com/angular/components/pull/25890. Also removes some of the logic now that we can assume that the checkmark will always be present.

good fix, didn't know about this edge case


Implement index subscripting and superscripting in Tensors

🐞 Problem
We have no way to know whether the Tensor has contravariant or covariant indices
🎯 Goal
The indices must be properly formatted in front of a symbol
💡 Possible solutions

📋  Steps to solve the problem

Comment below about what you've started working on.
Add, commit, push your changes
Submit a pull request and add this in comments - Addresses #<put issue number here>
Ask for a review in comments section of pull request
Celebrate your contribution to this project 🎉

@spacetimeengineer , this idea blatantly plagiarized from spacetimeengine, we would surely give the due credits.
Thanks!

You can not bring any code from spacetimeengine. Its BSD 3 Claused and hence,  it is not possible for us to bring the code here.

What recommendations do you have for me changing the license to accommodate your intentions? I am no expert on this subject but I really want you to take the code for whatever purpose necessary,

What recommendations do you have for me changing the license to accommodate your intentions? I am no expert on this subject but I really want you to take the code for whatever purpose necessary,

Wow, thanks ! It's really generous of you. It would be good to have MIT license, as it's the most open of all. Anyways, don't take any action regarding this now. We would intimate you after coming to a conclusion about what to do.
We welcome you to the community and you may join our chatroom https://riot.im/app/#/room/#einsteinpy:matrix.org
Again, thanks!!

What recommendations do you have for me changing the license to accommodate your intentions? I am no expert on this subject but I really want you to take the code for whatever purpose necessary,

Hi @spacetimeengineer , I won't recommend you to change the licence. Its okay. I see that spacetimeengine and EinsteinPy are doing similar things. We know that already. So, is there any possible collaboration that can benefit the whole scientific community as a whole?

I only added an MIT license just now. I kept BSD because Sympy uses it but apparently I am allowed to add a second license which SHOULD permit you to use it. I am not entirely sure how open source licensing works but I would really like to get it figured out.

@spacetimeengineer Can we discuss a few things somewhere? Some chat platform on which its wasy for you to communicate? :smiley:

Of-course, I am working now but if you send me a link, I can revisit later.

Of-course, I am working now but if you send me a link, I can revisit later.

If you are on Gitter then come say Hi here 😃
https://gitter.im/EinsteinPy-Project/EinsteinPy
Our Riot and Gitter chatrooms are integrated

Closed in #278

@OVSofia , As evident from the checklist above, indices manipulation already works with some tensors. Kindly go through PR #278 thoroughly and try to understand the working. See the example http://docs.einsteinpy.org/en/latest/examples/Playing_with_Contravariant_and Covariant_Indices_in_Tensors(Symbolic).html . I'm assigning this to you, try to check the other two tick-boxes :)

@OVSofia , ricci tensor checked! :)


clarifying mergeSTR docs

Clarifying misleading mergeSTR summary at the top of the page, which previously suggested mergeSTR should be used to merge VCFs from multiple TR genotypers. In fact, mergeSTR requires the VCFs being merged to be created by the same genotyper.

Codecov Report

Merging #92 into develop will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff            @@
##           develop      #92   +/-   ##
========================================
  Coverage    96.98%   96.98%
========================================
  Files           17       17
  Lines         2186     2186
========================================
  Hits          2120     2120
  Misses          66       66

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update e57b08b...0ebcef5. Read the comment docs.

What does "if the allele definitions are different across different files" mean? Should that be "if different alternate alleles are present in the different files"? (If so, I'll confirm this by writing a test for that).
Or is this a holdover from claiming that mergeSTR can merge files from different genotypers, and should just be deleted?

This was a holdover. I updated to your suggestion. If all looks good please approve and merge. Thanks!

Melissa, I made a few changes on top of your doc changes that are related, or just part of me trying to understand if what we say in our documentation is actually true. If you like the changes, feel free to merge.
A few changes:

MergeSTR seems in really bad shape. I have lots of complaints about the design and the testing. I've now listed those at the bottom of the mergeSTR tests file.
Make clear in two more places that mergeSTR does not merge VCFs from different genotypers
Don't list which genotypers we support here - just one more place we have to update
We don't have per-genotyper options, don't pretend to
Better links
Better --vcfs argument syntax
Actually support the eh SVTYPE INFO field
Clean up the GetSampleInfo function so I can understand it

Thanks for the changes. I have looked them over and will merge.
Thanks for adding the TODOs to the tests. We should look at and discuss those later in a separate PR. I agree with many but not all.
FYI One major reason we specify which format fields we support is that for some (in particular, genotype likelihoods, but any field that has a number of things specified by the number of alternate alleles), are not trivially mergeable. So for now we wrote out the ones we know should make sense even after merging to make sure we don't fill in FORMAT fields with garbage. It's possible we could instead merge all fields of a certain type (e.g. those with a constant number of entries) and not merge others (e.g. per-allele or per-genotype fields like GL. But that is still dangerous. GangSTR's GGL field meets neither of those because it is a special case. So we can't just blindly append.
I'm not sure where we ever promised per-genotyper options. We do mention supporting different fields per genotyper which is accurate.


chore(main): release 1.2.1

:robot: I have created a release beep boop
1.2.1 (2024-10-10)
Bug Fixes

StaticWebsite, fixed incorrect parent for new ResponseHeadersPolicy resources (f2a57f8)

This PR was generated with Release Please. See documentation.

:robot: Created releases:

v1.2.1
:sunflower:


Carplay for ios 14

Fixes various bugs I found when using this package and adds first class support for ios14. There were a fair few breaking changes from ios13 to ios14 and it was not possible to support both 14 and < 14 within the same package so in my mind it is better to move forward with a version 2.0.0 that supports ios14 and leave the existing version 1.3.1 to support legacy ios versions.

updates readme
updates the example app
sets build / deployment target to 14
improves the on connect / disconnect approach
adds support for different distance units for travel estimates
adds support for resizing / tinting manoeuvre symbol images
remove use of deprecated symbol image
fixes bug with maps where trip keeps getting recreated
adds pan events
adds back button detection to list templates
adds selected trip preview event
adds started trip event
adds leading / trailing navigation bar buttons to map templates
fixes bar buttons
fixes map buttons
fixes travel estimates
fixes show trip previews
adds update map buttons functionality
adds ability to disable bar buttons
adds trip destination / starting position names
fixes route choice functionality
fixes configs which didn't extend TemplateConfig
adds template configs to index barrel file
fixes pause-reasons enum
fixes time remaining color
types many events which were set to any

@birkir please take a look at this and contact me if you'd like to discuss. I've used this to integrate carplay into an existing turn by turn app and got it working pretty well. These are all the bugs / tweaks I made along the way to get it running more stable and with more functionality.
I think moving forward with a v2.0.0 aimed at ios14 is the best approach here.

@birkir please take a look at this and contact me if you'd like to discuss. I've used this to integrate carplay into an existing turn by turn app and got it working pretty well. These are all the bugs / tweaks I made along the way to get it running more stable and with more functionality.
I think moving forward with a v2.0.0 aimed at ios14 is the best approach here.

Hello @tomdye we have a music app similar to Spotify and are trying to integrate CarPlay for it. We are trying to use our fork, the problem is thank when we open the app in our simulator app does not seem to open in CarPlay and if we open it directly in CarPlay it crashes with this message:
Application does not implement CarPlay template application lifecycle methods in its scene delegate.
Are we missing something?
Thank you

This is awesome.
What was the problem with supporting ios13 with the of statements?
Runtime errors or just didn't build?

This is awesome.
What was the problem with supporting ios13 with the if statements?
Runtime errors or just didn't build?

The biggest issue I had was the macro level conditionals in the Objective C. Essentially the PODs / build targets for your package were set to a low iOS level so when they got installed into your react native package they were compiled for the wrong target and thus the statements never got entered.
I also found that the differing types / rules for the typescript side of the interface were problematic and caused problems.
TLDR: When using the package previously you could not build it to target both pre / post iOS14 so there was no point jumping through hoops and adding complexity to support it. Your app either has to support one of the other.

@birkir please take a look at this and contact me if you'd like to discuss. I've used this to integrate carplay into an existing turn by turn app and got it working pretty well. These are all the bugs / tweaks I made along the way to get it running more stable and with more functionality.
I think moving forward with a v2.0.0 aimed at ios14 is the best approach here.

Hello @tomdye we have a music app similar to Spotify and are trying to integrate CarPlay for it. We are trying to use our fork, the problem is thank when we open the app in our simulator app does not seem to open in CarPlay and if we open it directly in CarPlay it crashes with this message:
Application does not implement CarPlay template application lifecycle methods in its scene delegate.
Are we missing something?
Thank you

Did you follow the delegate steps in the Readme? https://github.com/birkir/react-native-carplay#installing

@birkir going forward, I think it would be worthwhile converting to swift and remove the use of the non-deprecated delegate - though I've not yet looked into the complexities surrounding this.

Comments addressed and prettier ran against the example dir.

@birkir please take a look at this and contact me if you'd like to discuss. I've used this to integrate carplay into an existing turn by turn app and got it working pretty well. These are all the bugs / tweaks I made along the way to get it running more stable and with more functionality.
I think moving forward with a v2.0.0 aimed at ios14 is the best approach here.

Hello @tomdye we have a music app similar to Spotify and are trying to integrate CarPlay for it. We are trying to use our fork, the problem is thank when we open the app in our simulator app does not seem to open in CarPlay and if we open it directly in CarPlay it crashes with this message:
Application does not implement CarPlay template application lifecycle methods in its scene delegate.
Are we missing something?
Thank you

Did you follow the delegate steps in the Readme? https://github.com/birkir/react-native-carplay#installing

Yeah I followed them but they are several called, I read somewhere that they are used by Navigation apps only, and if you have Audio app capabilities like in my case they are not called. Maybe is this the problem?

@marf I'm afraid that I have not looked into audio apps yet.

@tomdye I tried using this branch's example with the instructions in the ReadMe of this branch.  It doesn't seem to be working on my machine, think the instructions might need to be updated.
error message is 'React/RCTConvert.h' file not found

@kevinlowen1 if you already the example etc installed you may need to run rm -rf node_modules ios/Pods from the example dir before running the steps. re. POI, I'm afraid I did not look at this template yet as I was working on a navigation app for which POI is not actually a valid template. Once this PR is approved and merged I'm sure contributors like myself can look into the remaining templates currently causing issues.

I will release later today, thank you for the effort!

@birkir I'm assuming you don't have a react-native-carplay related discord, but I'm tom#1547 if you wanted to chat at all on discord about this project and future development / releases etc.

@tomdye @birkir sorry I don;t understand. From this PR I see POI template should work on IOS 14 but it crash so is it supported or not?

@vvusts I do not believe I was able to get POI to work when I was doing this, but I was writing a turn by turn navigation app when I was making this PR. The POI template is only valid for certain types of apps as per the apple developer guide so you may need to check that over and see if your app qualifies.


[BUG] Toolbox don't work with QtChart

Expected Behavior
Enabling toolbox on QtChart should work the same as when using Chart.
Current Behaviour
When running the PyQt example from the documentation (https://lightweight-charts-python.readthedocs.io/en/latest/examples/gui_examples.html) and enabling the toolbox flag on the QtChart declaration, you will get the following error when trying to draw anything:
AttributeError: 'QtChart' object has no attribute 'handlers
Since the main issue is the fact that the Bridge is declared with self and the QtChart does not declare the handlers attribute as a simple workaround, I've been doing:
chart = QtChart(widget, toolbox = True)
chart.handlers = chart.win.handlers

Reproducible Example
import pandas as pd
from PyQt5.QtWidgets import QApplication, QMainWindow, QVBoxLayout, QWidget
from lightweight_charts.widgets import QtChart

app = QApplication([])
window = QMainWindow()
layout = QVBoxLayout()
widget = QWidget()
widget.setLayout(layout)

window.resize(800, 500)
layout.setContentsMargins(0, 0, 0, 0)

chart = QtChart(widget, toolbox=True)

df = pd.read_csv('ohlcv.csv')
chart.set(df)

layout.addWidget(chart.get_webview())

window.setCentralWidget(widget)
window.show()

app.exec_()

Environment
- OS: Windows 10 19045
- Library: <IP_ADDRESS>

Hey @mcanavarros,
Thanks for pointing this out. This bug affects Qt and Wx, will fix in the next update.
Louis

Fixed in the latest version.


Send test mail to Amazon SES fails

Sending a test mail to SES failed:
root@grad:/opt/duplicacy-util# duplicacy-util -tn -sd /opt/duplicacy-util
07:05:12 Using global config: /opt/duplicacy-util/duplicacy-util.yaml
Error: gomail: could not send email 1: 554 Transaction failed: Expected '/', got ;
Error: gomail: could not send email 1: 554 Transaction failed: Expected '/', got ;
Error: gomail: could not send email 1: 554 Transaction failed: Expected '/', got ;

with config file
notifications:
  onStart: []
  onSkip: ['email']
  onSuccess: ['email']
  onFailure: ['email']

email:
  fromAddress: "Steve Frank<EMAIL_ADDRESS>  toAddress: "Steve Frank<EMAIL_ADDRESS>  serverHostname: email-smtp.us-east-1.amazonaws.com
  serverPort: 587
  authUsername: ID [these are correct in test]
  authPassword: KEY

closed by accident, reopening

I have no idea what the problem might be, so I copied your issue to the appropriate GitHub forum. We'll see what they have to say.

Thanks. I installed your package yesterday. It is a great help. Steve
Begin forwarded message:

From: Jeff Coffler<EMAIL_ADDRESS>Subject: Re: [jeffaco/duplicacy-util] Send test mail to Amazon SES fails (#36)
Date: February 8, 2019 at 6:47:38 PM GMT+1
To: jeffaco/duplicacy-util<EMAIL_ADDRESS>Cc: "Steven A. Frank"<EMAIL_ADDRESS> State change<EMAIL_ADDRESS>Reply-To: jeffaco/duplicacy-util<EMAIL_ADDRESS>I have no idea what the problem might be, so I copied your issue to the appropriate GitHub forum. We'll see what they have to say.
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub, or mute the thread.


[Question]: Multi modal rag implementation for pdf text and images

Question Validation

[X] I have searched both the documentation and discord for an answer.

Question
I have multiple pdf documents with me that contains both images and text. These documents contain lots of steps/procedures and it may have images for certain steps. The application I want to build should fetch not only the relevant text and also the relevant image. Is it possible to implement this using llamaindex, if so can anyone say a procedure for this

@dosu-bot that's great and i would be able to extract the text from image but that's not what i expect. I don't want to extract text from images rather i want to extract relevant text and from the document and if there is any relevant image for the retrieved context then the application should also include the image in the response. In my case i have multiple steps in the document and each step have some text followed by some images. I want my application to work in a way such that when a certain step is retrieved  and image under it should also be retrieved

@dosu-bot that's great and i would be able to extract the text from image but that's not what i expect. I don't want to extract text from images rather i want to extract relevant text and from the document and if there is any relevant image for the retrieved context then the application should also include the image in the response. In my case i have multiple steps in the document and each step have some text followed by some images. I want my application to work in a way such that when a certain step is retrieved and image under it should also be retrieved

Do you have a solution for this part yet?


DO NOT MERGE [es-backend/issues/227] Disable minikube by default and add NOTEST.tx…

…t for helm install
This disables, by default, the minikube-specific helm-charts mods.  (Which are essentially mods to expose our services with NodePorts.)
This is marked as DO NOT MERGE for now because this change will undoubtedly throw our current users for a loop.  We'll have to prepare them via email etc. that this is coming.

I think the all.yaml change is a bad idea - we should get the frontend guys on the same page and using helm charts as the correct approach... having this kind of thing introduces confusion and inconsistency across the teams, as there is no single source of truth for installation.

Going to make the all.yaml change here and deal with removing it altogether in https://github.com/lightbend/es-backend/issues/299.  (I did move the all.yaml stuff to the "dev" section of the Makefile.)

FYI for posterity sake, we discussed and decided to hold onto all.yaml for now.


Added Catalog Images(snapshots)

Description
This PR fixes #1494
Notes for Reviewers
Signed commits

[x] Yes, I signed my commits.

Don't edit the catalog manually. Also can you share the screenshot of the page by explicity setting image attribute in of the catalog to https://github.com/layer5labs/meshery-extensions-packages/blob/master/action-assets/design-assets/2512c0cb-385d-40de-b1f5-bc4a67131538.png (Be sure to undo your changes)

Do you want this image for every catalog? What i understand was that everyone will have a different image, that's why i what i did was i added a simple check statement in main file to just check if we have image attribute in remote url, then we are going to show that image else for all other catalog's we will have default service-mesh image, that's why i removed that image attribute from those catalogs md files, which have these default image.

Don't edit the catalog manually. Also can you share the screenshot of the page by explicity setting image attribute in of the catalog to https://github.com/layer5labs/meshery-extensions-packages/blob/master/action-assets/design-assets/2512c0cb-385d-40de-b1f5-bc4a67131538.png (Be sure to undo your changes)

Sure, will do the changes. Btw this link that you provided here should be this-https://raw.githubusercontent.com/layer5labs/meshery-extensions-packages/master/action-assets/design-assets/2512c0cb-385d-40de-b1f5-bc4a67131538.png

Don't edit the catalog manually. Also can you share the screenshot of the page by explicity setting image attribute in of the catalog to https://github.com/layer5labs/meshery-extensions-packages/blob/master/action-assets/design-assets/2512c0cb-385d-40de-b1f5-bc4a67131538.png (Be sure to undo your changes)

Sure, will do the changes. Btw this link that you provided here should be this-https://raw.githubusercontent.com/layer5labs/meshery-extensions-packages/master/action-assets/design-assets/2512c0cb-385d-40de-b1f5-bc4a67131538.png

Oh yes, I directly pasted the GitHub link and forgot to change it to the raw URL.

@MUzairS15 done the changes, also i have fixed the formatting issue in two .md  files of catalog, which were giving build errors.

Hey @coder12git  Let's discuss this on website call tomorrow at 6:30 PM IST / 7 AM Central time. Please add this as an agenda item in the meeting minutes.

@coder12git Great.
Can you also add the capability to render the default image if the src is not found? i.e. if the src attribute points to an invalid URL then render the default icon?

@coder12git Try this once <img src="......" onerror="this.onerror=null; this.src='/assets/.....png'"
To test, set an invalid URL for src.

Oh, you already did. Perfect.


EPIC: SEP-38

As an Anchor Engineering developer, I want to implement SEP-38 protocol core module such that the SEP-38 Anchor Tests: anchor-tests.stellar.org passes when run against the anchor platform service.
GanttStart: 2022-03-14
GanttDue: 2022-04-01
Tasks:

[x] #74
[x] #75
[x] #76
[x] #77
[x] #78
[x] #79
[x] #81
[x] #80
[x] #135
[x] #137
[x] #116

Finished SEP-38 🎉
Cc @reecexlm


WatchHistory, CurrentTime and Duration

@leandromoreira I'm calling extra.watchHistory, but if you prefer I can changed it to extra.watchedTime.
Since I was playing with this, I took the time to address the #9 too.

Thank you so much! :)


Start refactoring repository project

The window sample still outputs some critical errors during runtime. The rest of the samples seem to work fine.

As the errors are already present in the current develop branch I would like to merge this as it improves the file structure.
We can improve / fine tune the structure in a separate PR in a next step.

Yes I think we should merge as it is now and improve later in little steps. I think this makes like the 90% step into the right direction. The rest is really fine tuning and not very urgent and probably needs a lot of discussion.
I would even consider deferring the discussion at a later point in time as I would like to concentrate on bringing the Generator forward. I did not expect the refactoring of the Repository getting this huge. So the Generator refactoring will probably be much more work.
In case you want to improve the structure yourself I would suggest you open a new PR and we discuss the topics there. But I would recommend to not mix different topics like name of the project file with for example the file hierarchy as we could have different opinions and sorting it all out in one step could be more difficult (except the topic are dependent on each other from your point of view).
My opinions regarding your remarks:

I don't think it makes sense to swap Namespace with Repository. They aren't really the same concept, and it makes the Generator code more verbose with little benefit.

I did not do the changes from the view point of the Generator project, but from the view point of what is right in my opinion from the Repository projects view. I did the change for the same reason you bring forward: Namespace and Repository are different concepts. A Namespace does not define any dependencies. Instead a Repository defines the dependencies of all the Namespaces it is containing. As we require the dependencies on the Type level there are two possibilities to solve this:

Switch the Namespace property for the Repository property
Introduce a new a type which just holds a list of the dependencies.

I decided to not use a new Type because if we for example would need another information from the repository we would need to transfer it to the new type, too. So I'm left with the first solution.
In general I think the best solution would be to have no dependency from the Type level into higher levels (neither Namespace nor Repository).
But as this requires a lot more brain thought and concepts I went with the "simple" solution. Any idea into this direction is more than welcome. <5 minutes later> Hmmm, while thinking about it I checked the Method generation and it uses the "current namespace" which is available during generation. Perhaps we can really get rid of the reference into higher levels completely if we do it in the same way? But this would be another PR, too.

I'm not really a fan of GirLoader as the project name. It describes what the library does, but doesn't make much sense in terms of it being a representation of introspection data. Maybe Introspection could be a better name? e.g. GirLoader.Output.Model.Record vs Introspection.Model.Record.

I'm open to improvement here but for me the "introspection data" is part of the "gir" = "GObject Introspection". I think if we omit something like "Loader" it is not clear for a 3rd party developer what this is for and digging through code would be necessary to understand what is happening especially in our case as we have lots of projects in the git repository.

Having Input.Model and Output.Model is nice in terms of symmetry but it reduces readability. It's not immediately clear what type is being referred to when the namespace is not qualified.

This is why I would qualify the name if there is any risk of confusing them, and at the same time avoiding duplicated potentially missleading information. It is quite common to have conflicting names which are only separated by the namespace. Consider Frameworks like Xamarin Forms. There is the Gtk.Button, the Xamarin button, the WPF button and so on. They need to get everything handled somehow but they don't prefix / suffix their classes. It does not add any value.

Similarly, I would like to avoid having multiple Loader.cs files.

See above.

I think Loading, Transforming, and Resolving are too interconnected. My preference would be to split out Model and have Input and Output interface only by the contents of Model (i.e. no reference to Input from Output).

Yeah like one year ago I would agree without hesitation. I think it is very hard to find the line between "overengeneering" and "future proof work which is as easy as possible". For me separating this is not needed. The model classes do not have any relevant logic. They are just there to help other classes do their work. The important logic is in the "Loader" / "Resolver" things. Thus I think the focus should be on those. If the model would be needed separately by some other project this would perhaps qualify to move it into a top level folder. But in the same moment I think it should be moved into a separate project file to stand for itself. So currently it is a bit: YAGNI.
I think you are already aware that some of my opinions are not the idiomatic C# ones (like not suffixing class with the namespace they live in, interfaces which are not starting with an "I", or using a little more uncommon libs like MSTest, Serilog and so on). I don't want to go the idiomatic way but the way which makes sense from a data point of view and test things out to improve on the standard:

E.g. GObject does not prefix their interfaces with an "I".
E.g. Vala is not adding suffixes to their classes.

Ultimatively I think this is from a pure technical language independent point of view the right decision. This is why I try to test thinkgs out as I want to see if it is benefical to do so with C#. If it is not we can always change but learned a lesson for our professional live.
So let's merge? :wink:


Question: why enforcing lowercase for WDS file suffix?

I noticed that the group_by_keys function in tariterator.py would by default lowercase the WDS file suffix. I'm wondering what is the motivation behind this? Is there way to turn this off? This is slightly confusing when the tar file contains files like "TestData.pth", but the loaded dict key is "testdata.pth"? Thanks!

Windows and Mac file systems are case independent. WebDataset therefore prefers that your datasets are case independent as well, since otherwise unpacking them on those other systems would cause problems. You can disable this by setting lcase=False

Thanks for the explanation! I've buried in the Linux world for too long to
forget what the Mac and Windows side looks like. Can you point me to any
code snippet to set this flag when creating a WDS loader? Thanks!
On Thu, Jul 18, 2024, 9:42 PM Tom @.***> wrote:

Windows and Mac file systems are case independent. WebDataset therefore
prefers that your datasets are case independent as well, since otherwise
unpacking them on those other systems would cause problems. You can disable
this by setting lcase=False
—
Reply to this email directly, view it on GitHub
https://github.com/webdataset/webdataset/issues/371#issuecomment-2238148014,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABVTNOTEMIRDOJVWOS4N74DZNCKM3AVCNFSM6AAAAABKIPET3KVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEMZYGE2DQMBRGQ
.
You are receiving this because you authored the thread.Message ID:
@.***>


Navigating Back On IPLD Breadcrumbs Fails

OS: macOS
Version of IPFS Desktop [Version 0.27.2 (0.27.2)]
Electron Version: '19.1.9'
Chrome Version: '102.0.5005.167'

Describe the bug
When trying to navigate back to a parent level inside of the IPLD explorer breadcrumbs, the links cannot be found.
To Reproduce
Steps to reproduce the behavior:

Click on XKCD Archives (or any other IPLD explorer trail) on the Explore Page
Click on any path
Click on another path (to go a level deeper)
Click the breadcrumb in the top level to go back
See error of a path not being found

GIF attached:

Expected behavior
You should be able to navigate back to the parent level which you clicked.
Developer Tools Logs:

@Faolain thanks for reporting this bug!
I was able to reproduce this bug on the latest version of IPFS Desktop as well.
It doesn't seem to be occurring at explore.ipld.io so maybe something in webui/desktop is broken.
I will investigate further.

Not reproducible in webui (ran locally) either.


[ja] Translate content/en/docs/reference/glossary/cidr.md into Japanese

This is a Feature Request
What would you like to be added
Translate content/en/docs/reference/glossary/cidr.md into Japanese
Why is this needed
There is no Japanese translation for this page
Comments

File to translate:

https://github.com/kubernetes/website/blob/main/content/en/docs/reference/glossary/cidr.md

Original:

https://kubernetes.io/ja/docs/reference/glossary/?all=true#term-cidr

日本語に翻訳する際は、以下のドキュメントを参考にしてください。

Japanese Localization document: https://kubernetes.io/ja/docs/contribute/localization/

/area localization
/language ja
/good-first-issue

/triage accepted

/assign


Same task across runs

I have a question about how a task is defined in the spec, and how this applies to tasks that might span across runs (i.e. naturalistic tasks "movie-watching").
In the spec it states:

Task - a set of structured activities performed by the participant. Tasks are usually accompanied by stimuli and responses, and can greatly vary in complexity. For the purpose of this protocol we consider the so-called “resting state” a task. In the context of brain scanning, a task is always tied to one data acquisition. Therefore, even if during one acquisition the subject performed multiple conceptually different behaviours (with different sets of instructions) they will be considered one (combined) task

Note that it states that tasks are "always tied to one data acquisition", not "conceptually different behaviors".
I think this reading of the spec would suggest that a naturalistic study spanning three runs (e.g.: https://openneuro.org/datasets/ds001338), should be three tasks.
However, I think the section on Run clears this up:

Run - an uninterrupted repetition of data acquisition that has the same acquisition parameters and task (however events can change from run to run due to different subject response or randomized nature of the stimuli). Run is a synonym of a data acquisition.

I would suggest that the definition for Task is modified to avoid confusion:

a task is always tied to one or more data acquisitions

Also brought up in
https://openneuro.org/datasets/ds001338#comment-5c6314ba80ad0939ed28f806
On Tue, Feb 12, 2019 at 10:53 AM Alejandro de la Vega <
<EMAIL_ADDRESS>wrote:

I have a question about how a task is defined in the spec, and how this
applies to tasks that might span across runs (i.e. naturalistic tasks
"movie-watching").
In the spec it states:
Task - a set of structured activities performed by the participant. Tasks are usually accompanied by stimuli and responses, and can greatly vary in complexity. For the purpose of this protocol we consider the so-called “resting state” a task. In the context of brain scanning, a task is always tied to one data acquisition. Therefore, even if during one acquisition the subject performed multiple conceptually different behaviours (with different sets of instructions) they will be considered one (combined) task
Note that it states that tasks are "always tied to one data acquisition",
not "conceptually different behaviors".
I think this reading of the spec would suggest that a naturalistic study
spanning three runs (e.g.: https://openneuro.org/datasets/ds001338),
should be three tasks.
However, I think the section of runs clears this up:
Run - an uninterrupted repetition of data acquisition that has the same acquisition parameters and task (however events can change from run to run due to different subject response or randomized nature of the stimuli). Run is a synonym of a data acquisition.
I would suggest that the definition for Task is modified to avoid
confusion:
"a task is always tied to one or more data acquisitions"
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/bids-standard/bids-specification/issues/146, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAOkpz2I-ncgU6Pvw6iy3n-swtkl1VLIks5vMw2ggaJpZM4a30-5
.

In https://openneuro.org/datasets/ds001338 the stimulus (an audio story) was split into three parts creating three tasks. They are not three runs (repetitions) of the same task because each time a different part of the story was played.
I don't think that dataset needs to be corrected - as you suggested. But it might be good to provide this example as part of the specification to bring more clarity.

Wouldn't the same argument apply to a dataset such as this one: https://openneuro.org/datasets/ds001545/. The stimulus is also split up into three tasks, yet treated as a single task.
This is how I've seen most naturalistic datasets implemented in BIDS (e.g. raiders, life, forrest). I could imagine other conceptual "tasks" that differ in specific stimuli across runs (different words used in Stroop).
In your reading, are both styles legal? (and BIDS has some flexibility?).
In any case, I've published a fork of ds001338 using single task "style": https://github.com/neuroscout-datasets/ds001338_raw

Wouldn't the same argument apply to a dataset such as this one: https://openneuro.org/datasets/ds001545/. The stimulus is also split up into three tasks, yet treated as a single task.

Indeed in this case I would recommend splitting into task-movie01, task-movie02, etc.
This allows distinguishing between watching the same segment of a movie twice (task-movie01_run-01, task-movie01_run-02) vs. watching two different segments of the same movie (task-movie01, task-movie02).
In my interpretation of the definition of task splitting a movie in a consistent manner is not randomizing stimuli and thus different from Stroop example. It's just my interpretation though.

Sorry, just to confirm: Is that to suggest that the data could be represented both as task-movie_run01 and task-movie01 ? Or are you suggesting we should standardize towards task-movie01 ?
Like @adelavega I've also mostly seen the task-movie_run-01 labelling, so it'd be nice to clarify this !

My personal interpretation is that task-movie_run-01, task-movie_run-02 should be only used if the same movie was watched twice. If a movie was split into two section task-movie01, task-movie02 should be used. Both options are allowed, but they mean something else.

@chrisfilo, I think you make a good point about about watching the same segment twice, but this could also be determined using the events.tsv file as well (e.g. different stimuli files are referred to).
This allows for more complex designs. For example, https://openneuro.org/datasets/ds001246/versions/1.0.1 has three runs of the same task (e.g. "perception"), with different stimuli for each run.

@tyarkoni -- pinging you as you had some thoughts on this you wanted to shae

I agree with @adelavega here—I don't see a good reason to privilege a difference in stimuli over a difference in nominal task instructions. If the same movie is split into 3 runs, but it's passive viewing in all cases, calling the result task-movie01, task-movie02, etc. feels inconsistent to me with the way we handle standard cognitive tasks where the stimuli change. E.g., suppose you're doing a face vs. house recognition task that lasts for 2 runs, but the specific images are different in each run. We wouldn't call that task-recog1_run-1 and task-recog2_run-1 just because the stimuli are different, would we? Typically we'd say you did the same task for 2 runs, even if the stimuli are different. It feels much more natural to call it task-recog_run-1 and task-recog_run2. I don't see any difference in the movie situation.
@chrisfilo I don't really see why randomization should make a difference for purposes of determining labels. Say you have 20 clips you need to distribute over 2 runs. Why should randomization scheme change the naming convention? If they're randomized, then that makes task-movie_run-1 and task-movie_run-2 okay, but if they're not randomized, then it's task-movie1_run-1 and task-movie2_run-2? The only argument I can see for that is that order is a confound in the latter case, so maybe you shouldn't fit the same model to both runs. But that's a judgment call that I don't think we can impose on people at the spec level.
I also don't think this really helps distinguish cases where the same stimuli are repeated a second time. How would you know whether it's run-1 and run-2 because of randomization, vs. because exactly the same sequence of events is presented a second time?
In general I think we should try to stay away as much as possible from having  design considerations bleed into the labeling. Unfortunately that means we're stuck with ambiguity in cases like this. If it were up to me, I would say that runs indices should just sequentially increase within session, based on the chronological order they were acquired in, and task should be used to encode anything else the researcher wants to track. So then you could have things like task-movie1_run-1, task-movie1_run-2, task-movie1repeat_run-3, task-movie2repeat_run-4, etc. I realize this is probably incompatible with the spec at at this point, but it would at least have the benefit of being unambiguous—and would also avoid having to rely on task` to uniquely distinguish any two files.
Absent that, I don't see any way to settle on a convention that won't be ambiguous and elicit disagreement on occasion, and I think we just have to live with that.

Absent that, I don't see any way to settle on a convention that won't be ambiguous and elicit disagreement on occasion, and I think we just have to live with that.

+1
It seems to me that no action is warranted for now. Ambiguous cases such as these should be well documented (e.g., in the README)
Closing for now, feel free to reopen if new arguments or suggestions for changing the spec emerge


Add config for max number of auto-unfurls

This is super dope. I can see it becoming a problem in really long comments with a ton of links - can there be a config that says "if you've already added x links, don't add more"?

Yeah, I like that. I think we could default it to only unfurling 5-10 links. I can't imagine more than that would be useful. I'd also like to change the behavior when there are >2 links to switch to a more compact layout with 1-line for each unfurl.

I love the idea for a "compact" layout. It should be an option in attachments, and unfurl should just switch that on with >X links.

@bkeepers @JasonEtco Please review my PR.
Thanks in advance.


Added support for theming through introducing a function that checks …

Added support for theming through introducing a function that checks whether theme support has been switched on, if so, it loads the theme if not it load default views
Theme support provided by caffeinated\themes

@Rndwiga, please respond to @marktopper's review comments

Is this still applicable?

This has been closed for over 2 years now. Signficant changes have occurred since then.  You're much better off explaining your use-case and asking for help in our slack group instead


Applet programming in java

Proposed title of article
Understanding Applet programming in java
Introduction paragraph (2-3 paragraphs):
An applet is a small java program that is used in internet programming.
Applets are run mainly using applet viewer or web browsers that mainly supports java. An applet just like any other stand-alone application it performs many functions of which includes performing arithmetic operations, play sounds, accept inputs from the user and also display graphics.
Applets cannot be run independently like stand-alone applications they therefore  use HTML tags to enable them run in a web browser
Key takeaways:
By the end of this tutorial the learner should understand:

Definition of an applet and write a 'hello world' program using applet.
The lifecycle of an applet.
Difference between an applet and java stand-alone application
How to invoke an applet.
How to convert applications to applets.

References:
N/A

sounds like a good topic - approved @Paul22691


net: bt: fix 6lowpan over BLE regression

6lowpan over BLE stopped working since multicast filtering was implemented. Seems like Address Registration Option implementation is required for this to work without solicit node multicast, but as that is not currently implemented, nodes are unresponsive.

Actually after further investigation I realize that the current behavior has been set explicitly in
66244a0e67 net: if: No need to always join solicit node mcast group
the multicast stack handles solicited node address correctly when initialized to do so with join_mcast_solicit_node().
Dropping NET_L2_MULTICAST_SKIP_JOIN_SOLICIT_NODE from net_bt_flags() seems to make the ipsp example work again, so that would be an option, but that should not be needed according to https://tools.ietf.org/html/rfc7668#section-3.2.2 (mentioned in the patch above). What I don't understand now is why the Linux host is using solicited node for neighbor discovery and if there is a way of setting up the link to make this work correctly.
Marked the PR as draft while investigating further.

Actually after further investigation I realize that the current behavior has been set explicitly in
66244a0e67 net: if: No need to always join solicit node mcast group
the multicast stack handles solicited node address correctly when initialized to do so with join_mcast_solicit_node().
Dropping NET_L2_MULTICAST_SKIP_JOIN_SOLICIT_NODE from net_bt_flags() seems to make the ipsp example work again, so that would be an option, but that should not be needed according to https://tools.ietf.org/html/rfc7668#section-3.2.2 (mentioned in the patch above). What I don't understand now is why the Linux host is using solicited node for neighbor discovery and if there is a way of setting up the link to make this work correctly.
Marked the PR as draft while investigating further.

I think this is what's happening: according to rfc7668, 6lowpan over BLE does not need solicited node frames, and neighbor discovery happens with NS messages with Address Registration Option (described in rfc6775), which supposedly keeps the neighbor cache hot on the border router:

Registration:
The process during which a LoWPAN node sends a Neighbor
Solicitation message with an Address Registration Option to a
router creating a Neighbor Cache Entry (NCE) for the LoWPAN node
with a specific timeout.  Thus, for 6LoWPAN routers, the Neighbor
Cache doesn't behave like a cache.  Instead, it behaves as a
registry of all the host addresses that are attached to the
router.

Now the problem is that there's no implementation for this in the stack as far as I can tell, and it seems like ARO is not supported in Linux either (that would have to be defined here as option 33).
So since the node does not send NS ARO messages, Linux tries to do normal host initiated neighbor discovery, which fails because the node stack is discarding those frames.
rfc7668 also states that link local addresses do not have to be registered

A Bluetooth LE 6LN MUST NOT register its link-local address.

so I don't quite get the full story of how link-local address are supposed to be resolved.
Either way, this does not work with the current code base without address registration plus solicited node filtering, and I think that even if we had address registration, it would not work without explicit handling in Linux.
@jukkar: would it make sense to remove NET_L2_MULTICAST_SKIP_JOIN_SOLICIT_NODE as a workaround until rfc6775 is fully implemented? I'll update the PR with that in the meantime, just in case someone else wants to test it.

I think this is what's happening: according to rfc7668, 6lowpan over BLE does not need solicited node frames, and neighbor discovery happens with NS messages with Address Registration Option (described in rfc6775), which supposedly keeps the neighbor cache hot on the border router:

Registration:
The process during which a LoWPAN node sends a Neighbor
Solicitation message with an Address Registration Option to a
router creating a Neighbor Cache Entry (NCE) for the LoWPAN node
with a specific timeout.  Thus, for 6LoWPAN routers, the Neighbor
Cache doesn't behave like a cache.  Instead, it behaves as a
registry of all the host addresses that are attached to the
router.

Now the problem is that there's no implementation for this in the stack as far as I can tell, and it seems like ARO is not supported in Linux either (that would have to be defined here as option 33).
So since the node does not send NS ARO messages, Linux tries to do normal host initiated neighbor discovery, which fails because the node stack is discarding those frames.
rfc7668 also states that link local addresses do not have to be registered

A Bluetooth LE 6LN MUST NOT register its link-local address.

so I don't quite get the full story of how link-local address are supposed to be resolved.
Either way, this does not work with the current code base without address registration plus solicited node filtering, and I think that even if we had address registration, it would not work without explicit handling in Linux.
@jukkar: would it make sense to remove NET_L2_MULTICAST_SKIP_JOIN_SOLICIT_NODE as a workaround until rfc6775 is fully implemented? I'll update the PR with that in the meantime, just in case someone else wants to test it.

would it make sense to remove NET_L2_MULTICAST_SKIP_JOIN_SOLICIT_NODE from the 6lowpan bluetooth stack as a workaround until rfc6775 is fully implemented? I'll update the PR with that in the meantime, just in case someone else wants to test it.

Sure, that seems to be the only usable workaround for this issue atm.

would it make sense to remove NET_L2_MULTICAST_SKIP_JOIN_SOLICIT_NODE from the 6lowpan bluetooth stack as a workaround until rfc6775 is fully implemented? I'll update the PR with that in the meantime, just in case someone else wants to test it.

Sure, that seems to be the only usable workaround for this issue atm.

In your sample commit message, the example list of multicast addresses are
IPv6 multicast addresses (max 8):
        ff02::1
        ff02::1:ff01:c41e
        ff02::1:ff00:1
        ff02::1

Here ff02::1 is mentioned twice. Is this a typo or was it really like this? The address should be there once and it is a bug if mentioned multiple times.

In your sample commit message, the example list of multicast addresses are
IPv6 multicast addresses (max 8):
        ff02::1
        ff02::1:ff01:c41e
        ff02::1:ff00:1
        ff02::1

Here ff02::1 is mentioned twice. Is this a typo or was it really like this? The address should be there once and it is a bug if mentioned multiple times.

Not a typo, it does show up twice, seems like init_app() of samples/bluetooth/ipsp/src/main.c is calling net_if_ipv6_maddr_add() on that address directly, which bypasses the duplicate check (that's in net_ipv6_mld_join).
Removing it or changing it to net_ipv6_mld_join makes the duplicate go away. Don't see why that address should be registered by the application anyway, I'll add a third patch to drop if entirely from the sample you agree with that.
As for the API, should the duplicate detection be moved from net_ipv6_mld_join to net_if_ipv6_maddr_add?

Not a typo, it does show up twice, seems like init_app() of samples/bluetooth/ipsp/src/main.c is calling net_if_ipv6_maddr_add() on that address directly, which bypasses the duplicate check (that's in net_ipv6_mld_join).
Removing it or changing it to net_ipv6_mld_join makes the duplicate go away. Don't see why that address should be registered by the application anyway, I'll add a third patch to drop if entirely from the sample you agree with that.
As for the API, should the duplicate detection be moved from net_ipv6_mld_join to net_if_ipv6_maddr_add?

Removing it or changing it to net_ipv6_mld_join makes the duplicate go away. Don't see why that address should be registered by the application anyway, I'll add a third patch to drop if entirely from the sample you agree with that.

Yes, please add a 3rd patch for that.

As for the API, should the duplicate detection be moved from net_ipv6_mld_join to net_if_ipv6_maddr_add?

Sounds like an error if the same address is there multiple times. So please move the check to when the address is added.

Removing it or changing it to net_ipv6_mld_join makes the duplicate go away. Don't see why that address should be registered by the application anyway, I'll add a third patch to drop if entirely from the sample you agree with that.

Yes, please add a 3rd patch for that.

As for the API, should the duplicate detection be moved from net_ipv6_mld_join to net_if_ipv6_maddr_add?

Sounds like an error if the same address is there multiple times. So please move the check to when the address is added.

Alright, I've updated the PR to add a patch to check for duplicate addresses to net_if_ipv6_maddr_add(), removed the call from the examples and while I was on it I updated the sample documentation to mention the debug config.
Tested the whole thing again, seems to be working fine, the address list looks like this now:
IPv6 multicast addresses (max 4):
ff02::1
ff02::1:ff01:c41e
ff02::1:ff00:1

Alright, I've updated the PR to add a patch to check for duplicate addresses to net_if_ipv6_maddr_add(), removed the call from the examples and while I was on it I updated the sample documentation to mention the debug config.
Tested the whole thing again, seems to be working fine, the address list looks like this now:
IPv6 multicast addresses (max 4):
ff02::1
ff02::1:ff01:c41e
ff02::1:ff00:1

Updated with a couple of checkpatch fixes.

Updated with a couple of checkpatch fixes.


Create Adama Science and Technology University(ASTU)

URL: www.astu.edu.et

@frezewd First stage of verification passed, official domain is astu.edu.et as far as I verified. This is just an informational note. Pull request is still in the review. I appreciate your patience while waiting for the final decision.

@frezewd Thank you for your patience while waiting for a review and processing your request. Pull request merged.


[Linux] [macOS] Support pre-compiled Python 3.9 wheels

Related https://github.com/grpc/grpc/issues/24344
Thanks to previous effort of supporting Python 3.8 in https://github.com/grpc/grpc/issues/20615. It's easier to extend our support to 3.9 by simply update existing scripts. Hope our CI will be happy about this change.

Unfortunately, the behavior of Python3.9 installer on Windows changed. The installation process can't be deterministically by previous mechanism (Wait-Process). I somehow can't access Kokoro images on Pantheon to tune the script, so I will postpone Windows 3.9 support till later.

Known failures: https://github.com/grpc/grpc/issues/24375 https://github.com/grpc/grpc/issues/23919


Move towards u64 for internal size storage

This implements the changes that were suggested as part of issue #7 .

The patch looks good to me.


Segfault when running codecoverage with tarpaulin

On my machine

running codecoverage for non-doctest succeeds with both 1 thread or multiple
running codecoverage for doctest fails with or without the thread limitation (See below for details)

On GitHub any codecoverage configuration fails with a segmentation fault.

I am not sure where the problem is exactly.
Note that

doctest coverage for tarpaulin depends on rust-nightly.
ion-c might have a bug

Running tarpaulin with
cargo tarpaulin -v --debug --release --run-types Doctests --out Html --workspace

or
cargo tarpaulin -v --debug --release --run-types Doctests --out Html --workspace -- --test-threads=1

fails on
Doc-tests ion-c-sys
     Running `rustdoc --edition=2018 --crate-type lib --test /home/ANT.AMAZON.COM/therapon/Amazon/Work/GitHub/Ion/ts-ion-rust-1/ion-c-sys/src/lib.rs --crate-name ion_c_sys -L dependency=/home/ANT.AMAZON.COM/therapon/Amazon/Work/GitHub/Ion/ts-ion-rust-1/target/release/deps -L dependency=/home/ANT.AMAZON.COM/therapon/Amazon/Work/GitHub/Ion/ts-ion-rust-1/target/release/deps -L native=/home/ANT.AMAZON.COM/therapon/Amazon/Work/GitHub/Ion/ts-ion-rust-1/target/release/build/ion-c-sys-30c937fa6fac9e04/out/lib -L native=/home/ANT.AMAZON.COM/therapon/Amazon/Work/GitHub/Ion/ts-ion-rust-1/target/release/build/libloading-35f0411caee9e2f5/out --test-args --test-threads=1 --extern ion_c_sys=/home/ANT.AMAZON.COM/therapon/Amazon/Work/GitHub/Ion/ts-ion-rust-1/target/release/deps/libion_c_sys-c0e9a51780e178af.rlib --extern paste=/home/ANT.AMAZON.COM/therapon/Amazon/Work/GitHub/Ion/ts-ion-rust-1/target/release/deps/libpaste-07a2659eec7ed2cb.so --extern rstest=/home/ANT.AMAZON.COM/therapon/Amazon/Work/GitHub/Ion/ts-ion-rust-1/target/release/deps/librstest-f059a51b34ab8d79.so -C relocation-model=dynamic-no-pic -C link-dead-code -C debuginfo=2 --cfg=tarpaulin --persist-doctests /home/ANT.AMAZON.COM/therapon/Amazon/Work/GitHub/Ion/ts-ion-rust-1/target/doctests -Z unstable-options`
error: test failed, to rerun pass '--doc'
[ERROR tarpaulin] Building doctests failed
[ERROR tarpaulin] Cargo failed to run! Error: Building doctest failed
[INFO tarpaulin] Serializing tarpaulin debug log to tarpaulin-run-2020-08-10T22:01:17.635435492-07:00.json
Error: "Cargo failed to run! Error: Building doctest failed"

The tarpaulin debug log is not that informative
{"events":[{"ConfigLaunch":"<anonymous>"}]}

Resolving, we don't run/support tarpaulin, but use grcov.


refactor(app): rename the port field into address and support change the address and the port

Sorry for the late PR, I had to take some time to parse the project structure tree.
Current behavior
The Share a service window only allows the user to define the service port and the address it always defaults to <IP_ADDRESS>
Proposed changes

Replace the Port field name to Address
We should support the formats Host:Port,  IP:Port and Port (defaulting to <IP_ADDRESS>)
Adapt the app backend to parse the address correctly.

Closes: #5685

Checks

[x] All commits in this Pull Request are signed and Verified by Github.
[x] All commits in this Pull Request follow the Ockam commit message convention.
[x] I accept the Ockam Community Code of Conduct.
[x] I have accepted the Ockam Contributor License Agreement by adding my Git/Github details in a row at the end of the CONTRIBUTORS.csv file in a separate pull request to the build-trust/ockam-contributors repository. The easiest way to do this is to edit the CONTRIBUTORS.csv file in the github web UI and create a PR, this will mark the commit as verified.

I don't know why the commits are un-signed. I suppose that I've messed up my gitconfig. anyway, I will fix that and open a new PR.


Suggest to support chrome extension shortcuts

Hope to support chrome extension shortcuts.
For example, set alt+c to copy html as markdown.

Supported in v2.3.0.


Add README to /templates directory

Description
This PR adds a README to /templates explaining what Hydrogen templates are, and describing the two we currently/will soon offer. Keeping this as a draft until the Demo Store template migrates in.
Before submitting the PR, please make sure you do the following:

[x] Read the Contributing Guidelines
[x] Provide a description in this PR that addresses what the PR is solving, or reference the issue that it solves (e.g. fixes #123)
[ ] ~Update docs in this repository according to your change~
[ ] Run yarn changeset add if this PR cause a version bump based on Keep a Changelog and adheres to Semantic Versioning

@gfscott Related question: Will these commands also be available through yarn, or are they exclusively run through npx?

@mcvinci Good question! I'm reasonably certain this works with npm init, npx and yarn, just like we have in the current getting started docs.
Should we pick a winner in this context, or keep surfacing all options? Do you have any strong views?

@gfscott I'd love if we could surface all options! It would keep the information aligned with what we have on Shopify.dev, too. I'd be hesitant to assert a preference here as developers might want to use any one of these options, so I'd suggest airing on the side of comprehensiveness!


titlewttj-qa-bot

Test summary
:white_check_mark: 1 :x: 0 :fast_forward: 0

Run details

Status
Value 1

Started
Value 2

Duration
20 min

Environment
Value 2

Browser
Chrome

Artifacts: aws s3 cp s3://qa-cypress/artifacts//WACC-20220310_180553.tar

Failures

            cypress/integration/commands/net_stubbing_spec.ts

            1

1

            network stubbing > intercepting response > does not overwrite the json-related content-type header

Test summary
:white_check_mark: 1 :x: 0 :fast_forward: 0

Thanks for taking the time to open a PR!

Create a Draft Pull Request if your PR is not ready for review. Mark the PR as Ready for Review when you're ready for a Cypress team member to review the PR.
Become familiar with the Code Review Checklist for guidelines on coding standards and what needs to be done before a PR can be merged.

test


Implementation of Jupyter Widget

Implement Jupyter widget to explore saved trials.
from purple_caffeine import Widget, LocalBackend
Widget.render(LocalBackend(file_storage_path="./"))

Issues:

https://github.com/IceKhan13/purplecaffeine/issues/6
https://github.com/IceKhan13/purplecaffeine/issues/7

Project that we can look as first look reference is https://github.com/TheGupta2012/qiskit-timeline-debugger/tree/main/src/qiskit_trebugger
The feedback I have is that is it turning in a spagetti code if you operate only with ipywidgets classes + html elements.
What I was thinking is we can use Jinja templating engine to render all dynamic html and then inject it to ipywidgets 🤔

checking...

If we use https://pretty-jupyter.readthedocs.io/en/latest/quickstart.html then we can create html + javascript + bootstrap + python cells
disadvantage: we need to reload one cell to load changes made on python code

If we use jinja + ipywidgets then we can create html + bootstrap + python cells
disadvantage: apparently our javascript code is broken (need to re-check)

So after digging into the documentation(accordingly to https://ipywidgets.readthedocs.io/en/stable/examples/Widget Custom.html#models-and-views) we can do something like this:

create a custom value widget
get the values that we want to inject inside the html code inside the class
call the method template.render so jinja can inject our python variables into the html code
render our inyected code using the typescript append method

Alternatively we can do the same steps but instead of using jinja we can use OOB typescript functions to change the html template

@mentesniker let's have any of this options implemented with simple data pagination in table widget implemented with mock data. Then we will see how it looks and we will made a decision on path forward :)

yes! 🥳  closing


Can not download parameter tuning toolkit

Hello,the link of parameter tuning toolkit  is not available for me.

Hello,the link of parameter tuning toolkit is not available for me.

Hi~ Thanks for your interest. The tuning toolkit  is embedded in codes, you do not need to download again. Check siamese_tracking/tune_tps.py pls.

Thank  you!
---Original---
From: "ZP<EMAIL_ADDRESS>Date: Thu, Sep 12, 2019 09:50 AM
To<EMAIL_ADDRESS>Cc: "Author"<author<EMAIL_ADDRESS>Subject: Re: [researchmm/SiamDW] Can not download parameter tuning toolkit   (#39)
Hello,the link of parameter tuning toolkit is not available for me.
Hi~ Thanks for your interest. The tuning toolkit  is embedded in codes, you do not need to download again. Check siamese_tracking/tune_tps.py pls.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

Thank  you!
…
---Original--- From: "ZP<EMAIL_ADDRESS>Date: Thu, Sep 12, 2019 09:50 AM To<EMAIL_ADDRESS>Cc: "Author"<author<EMAIL_ADDRESS>Subject: Re: [researchmm/SiamDW] Can not download parameter tuning toolkit (#39) Hello,the link of parameter tuning toolkit is not available for me. Hi~ Thanks for your interest. The tuning toolkit is embedded in codes, you do not need to download again. Check siamese_tracking/tune_tps.py pls. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or mute the thread.

You are so welcom. And if you need other help, please email me<EMAIL_ADDRESS>


no API to customize rocksdb options and read-only mode

Currently we use the NewRocksDBWithRawDB API for two things:

tune the rocksdb options as we want
open the db in read-only mode, rocksdb support multi-process readers on a live db, we use it to run read-only tasks on live db.

Closed by https://github.com/cometbft/cometbft-db/pull/42


Docs: Add to docs that tests may fail because the server is too slow and hidden fields did not get shown fast enough

The developer would need to run the tests again.

It's not the da server that would be too slow, it would be the GitHub server running the client. Race conditions can pop up everywhere in end-to-end testing.


Multiple languages spell checker

Is it currently possible to enable multiple languages at the same time for spell checking? I don't seem to find a way to accomplish that. I can only select one language at the time.
If currently is not possible, adding this option would be extremely useful for my use case.
Thanks for your excellent work on WhatSie!

I just discovered that you can have multiple languages enabled at the same time in the spell checker simply using the standard WhatsApp web interface with Firefox

Hi thanks for opening this issue. I will try to add this feature in next version of whatsie.