Android scroller  component ,loadmore event  would not be triggered in horizontal  mode

[x] Review the documentation: https://weex.apache.org/index.html
[x] Search for existing issues: https://github.com/apache/incubator-weex/issues
[x] Use the latest Weex release: https://github.com/apache/incubator-weex/releases

Describe the bug
Please check dotwe demo below, loadmore event won't be triggered in horizontal mode on Android phones, while it acts well on iOS.
To Reproduce
http://dotwe.org/vue/343721bb5b5b5a81f7d7bfdb3bc00dcd
Environment

Device: [坚果 pro OC105 and maybe on other android phones ]
OS: [android 7.1.2]
Version [weex 0.18 +]
Build from source [no]

fixed by #3025


Fedora 29, failed to execute dnf install -y dotnet-sdk-3.0

Problem encountered on https://dotnet.microsoft.com/download/linux-package-manager/sdk-current
Operating System: Windows 10, Docker engine 19.03.5, Docker machine: 0.16.2
I am running the Docker daemon with experimental mode enabled.  This is to support experiemntal syntax in the Dockerfile, but I don't think it is relevant to this issue that I'm reporting here.
# syntax=docker/dockerfile:experimental
#     The line above stipulates that our Dockerfile is defined with an experimental syntax which requires the docker
#     daemon to be running in experimental mode.
FROM registry.fedoraproject.org/fedora:29

# Install .NET Core 3.0 runtime
RUN dnf install -y wget
RUN rpm --import https://packages.microsoft.com/keys/microsoft.asc
RUN wget -q -O /etc/yum.repos.d/microsoft-prod.repo https://packages.microsoft.com/config/fedora/29/prod.repo
RUN dnf install -y dotnet-sdk-3.0

I get an error during dnf install -y dotnet-sdk-3.0.  My console output is as follows:
$ docker build .
#1 [internal] load build definition from Dockerfile
#1 transferring dockerfile: 1.25kB done
#1 DONE 0.1s

#2 [internal] load .dockerignore
#2 transferring context: 2B done
#2 DONE 0.1s

#3 resolve image config for docker.io/docker/dockerfile:experimental
#3 DONE 0.5s

#4 docker-image://docker.io/docker/dockerfile:experimental@sha256:888f21826...
#4 CACHED

#5 [internal] load metadata for registry.fedoraproject.org/fedora:29
#5 DONE 0.0s

#6 [1/8] FROM registry.fedoraproject.org/fedora:29
#6 CACHED

#7 [2/8] RUN dnf install -y wget
#7 11.17 Fedora Modular 29 - x86_64                      195 kB/s | 1.5 MB     00:07
#7 17.62 Fedora Modular 29 - x86_64 - Updates            406 kB/s | 2.1 MB     00:05
#7 25.29 Fedora 29 - x86_64 - Updates                    4.9 MB/s |  30 MB     00:05
#7 63.69 Fedora 29 - x86_64                              7.4 MB/s |  62 MB     00:08
#7 160.1 Last metadata expiration check: 0:00:02 ago on Wed Nov 20 22:14:44 2019.
#7 175.0 Dependencies resolved.
#7 177.8 ================================================================================
#7 177.8  Package       Arch            Version                   Repository        Size
#7 177.8 ================================================================================
#7 177.8 Installing:
#7 177.8  wget          x86_64          1.20.3-1.fc29             updates          771 k
#7 177.8
#7 177.8 Transaction Summary
#7 177.8 ================================================================================
#7 177.8 Install  1 Package
#7 177.8
#7 177.8 Total download size: 771 k
#7 177.8 Installed size: 3.0 M
#7 177.8 Downloading Packages:
#7 181.6 wget-1.20.3-1.fc29.x86_64.rpm                   438 kB/s | 771 kB     00:01
#7 181.6 --------------------------------------------------------------------------------
#7 181.6 Total                                           204 kB/s | 771 kB     00:03
#7 181.6 Running transaction check
#7 181.7 Transaction check succeeded.
#7 181.7 Running transaction test
#7 181.8 Transaction test succeeded.
#7 181.8 Running transaction
#7 182.0   Preparing        :                                                        1/1
#7 182.4   Installing       : wget-1.20.3-1.fc29.x86_64                              1/1
#7 182.6   Running scriptlet: wget-1.20.3-1.fc29.x86_64                              1/1
#7 183.1   Verifying        : wget-1.20.3-1.fc29.x86_64                              1/1
#7 183.1
#7 183.1 Installed:
#7 183.1   wget-1.20.3-1.fc29.x86_64
#7 183.1
#7 183.1 Complete!
#7 DONE 183.7s

#8 [3/8] RUN rpm --import https://packages.microsoft.com/keys/microsoft.asc
#8 DONE 3.3s

#9 [4/8] RUN wget -q -O /etc/yum.repos.d/microsoft-prod.repo https://packag...
#9 DONE 2.0s

#10 [5/8] RUN dnf install -y dotnet-sdk-3.0
#10 8.370 packages-microsoft-com-prod                     1.4 MB/s | 3.9 MB     00:02
#10 31.11 Last metadata expiration check: 0:00:23 ago on Wed Nov 20 22:17:00 2019.
#10 39.10 Dependencies resolved.
#10 41.95 ================================================================================
#10 41.95  Package              Arch   Version          Repository                   Size
#10 41.95 ================================================================================
#10 41.95 Installing:
#10 41.95  dotnet-sdk-3.0       x86_64 3.0.101-1        packages-microsoft-com-prod  64 M
#10 41.95 Installing dependencies:
#10 41.95  compat-openssl10     x86_64 1:1.0.2o-7.fc29  updates                     1.1 M
#10 41.95  libicu               x86_64 62.2-1.fc29      updates                     8.8 M
#10 41.95  gc                   x86_64 7.6.4-4.fc29     fedora                      101 k
#10 41.95  guile                x86_64 5:2.0.14-12.fc29 fedora                      3.5 M
#10 41.95  libatomic_ops        x86_64 7.6.6-1.fc29     fedora                       34 k
#10 41.95  libtool-ltdl         x86_64 2.4.6-27.fc29    fedora                       34 k
#10 41.95  make                 x86_64 1:4.2.1-10.fc29  fedora                      487 k
#10 41.95  aspnetcore-runtime-3.0
#10 41.95                       x86_64 3.0.1-1          packages-microsoft-com-prod 7.5 M
#10 41.95  aspnetcore-targeting-pack-3.0
#10 41.95                       x86_64 3.0.1-1          packages-microsoft-com-prod 1.4 M
#10 41.95  dotnet-apphost-pack-3.0
#10 41.95                       x86_64 3.0.1-1          packages-microsoft-com-prod  66 k
#10 41.95  dotnet-host          x86_64 3.0.1-1          packages-microsoft-com-prod  39 k
#10 41.95  dotnet-hostfxr-3.0   x86_64 3.0.1-1          packages-microsoft-com-prod 147 k
#10 41.95  dotnet-runtime-3.0   x86_64 3.0.1-1          packages-microsoft-com-prod  29 M
#10 41.95  dotnet-runtime-deps-3.0
#10 41.95                       x86_64 3.0.1-1          packages-microsoft-com-prod 2.8 k
#10 41.95  dotnet-targeting-pack-3.0
#10 41.95                       x86_64 3.0.1-1          packages-microsoft-com-prod 3.4 M
#10 41.95  netstandard-targeting-pack-2.1
#10 41.95                       x86_64 2.1.0-1          packages-microsoft-com-prod 2.1 M
#10 41.95
#10 41.95 Transaction Summary
#10 41.95 ================================================================================
#10 41.95 Install  17 Packages
#10 41.95
#10 41.96 Total download size: 122 M
#10 41.96 Installed size: 155 M
#10 41.96 Downloading Packages:
#10 46.69 (1/17): compat-openssl10-1.0.2o-7.fc29.x86_64.r 536 kB/s | 1.1 MB     00:02
#10 47.09 (2/17): gc-7.6.4-4.fc29.x86_64.rpm               41 kB/s | 101 kB     00:02
#10 47.32 (3/17): libatomic_ops-7.6.6-1.fc29.x86_64.rpm   152 kB/s |  34 kB     00:00
#10 47.54 (4/17): libtool-ltdl-2.4.6-27.fc29.x86_64.rpm   155 kB/s |  34 kB     00:00
#10 48.82 (5/17): make-4.2.1-10.fc29.x86_64.rpm           379 kB/s | 487 kB     00:01
#10 49.04 (6/17): libicu-62.2-1.fc29.x86_64.rpm           2.0 MB/s | 8.8 MB     00:04
#10 49.44 (7/17): aspnetcore-targeting-pack-3.0.1.rpm     3.7 MB/s | 1.4 MB     00:00
#10 49.71 (8/17): dotnet-apphost-pack-3.0.1-x64.rpm       240 kB/s |  66 kB     00:00
#10 49.75 (9/17): dotnet-host-3.0.1-x64.rpm               888 kB/s |  39 kB     00:00
#10 49.96 (10/17): dotnet-hostfxr-3.0.1-x64.rpm           724 kB/s | 147 kB     00:00
#10 52.57 (11/17): aspnetcore-runtime-3.0.1-rh.rhel.7-x64 2.0 MB/s | 7.5 MB     00:03
#10 52.63 (12/17): dotnet-runtime-deps-3.0.1-fedora.27-x6  45 kB/s | 2.8 kB     00:00
#10 52.78 (13/17): guile-2.0.14-12.fc29.x86_64.rpm        589 kB/s | 3.5 MB     00:06
#10 53.37 (14/17): dotnet-targeting-pack-3.0.1-x64.rpm    5.8 MB/s | 3.4 MB     00:00
#10 53.65 [MIRROR] netstandard-targeting-pack-2.1.0-x64.rpm: Downloading successful, but checksum doesn't match. Calculated: 45e199caf1151a750d11d9c5c7669d6e23d8dbb33da54d1d90bde55745996480(sha256)  Expected: fa194a8c12913dcec85c8d24bfc91686a7b93128b4c05346df16e2c641e2ba41(sha256)
#10 53.68 [FAILED] netstandard-targeting-pack-2.1.0-x64.rpm: No more mirrors to try - All mirrors were already tried without success
#10 53.74
#10 53.74 The downloaded packages were saved in cache until the next successful transaction.
#10 53.74 You can remove cached packages by executing 'dnf clean packages'.
#10 53.79 Error: Error downloading packages:
#10 53.79   Cannot download netstandard-targeting-pack-2.1.0-x64.rpm: All mirrors were tried
#10 ERROR: executor failed running [/bin/sh -c dnf install -y dotnet-sdk-3.0]: runc did not terminate sucessfully
------
 > [5/8] RUN dnf install -y dotnet-sdk-3.0:
------
failed to solve with frontend dockerfile.v0: failed to solve with frontend gateway.v0: rpc error: code = Unknown desc = failed to build LLB: executor failed running [/bin/sh -c dnf install -y dotnet-sdk-3.0]: runc did not terminate sucessfully

Here's the critical error line:
#10 53.65 [MIRROR] netstandard-targeting-pack-2.1.0-x64.rpm: Downloading successful, but checksum doesn't match. Calculated: 45e199caf1151a750d11d9c5c7669d6e23d8dbb33da54d1d90bde55745996480(sha256)  Expected: fa194a8c12913dcec85c8d24bfc91686a7b93128b4c05346df16e2c641e2ba41(sha256)

This is a known issue with ongoing investigation, tracked by https://github.com/dotnet/core/issues/3853.
(There's a Fedora-specific duplicate that I'm leaving open as a signpost at https://github.com/dotnet/core/issues/3867. I've removed the "30" part of its title so it doesn't exclude Fedora 29.)


Try to implement portable caching using a statically compiled binary

I came across https://full-stack.blend.com/how-we-write-github-actions-in-go.html#how-we-write-actions-in-go which, in a nutshell, pretends to be a regular JavaScript action, but actually just calls a statically compiled binary.
That can obviously be done using Go, but Rust should also be able to do it.
Using that approach, one could revisit a properly portable implementation of the release caching problem.

Statically linking for Windows: https://georgik.rocks/how-to-statically-link-rust-application-for-windows/


HEI not respecting items hidden using Game Stages

Mod Version:
1.12.2-4.25.3
Description:
HEI not correctly hiding/showing items when adding or removing gamestages.
Reproducing this issue was difficult as it seemed to work correctly about half the time. Using the following modlist I was able to consistently reproduce the bug causing all items to remain visible, ignoring player gamestages.
This issue did not occur when using JEI with the same modlist.
Mods Loaded:

Astral Sorcery
Baubles
Bookshelf
CraftTweaker
Game Stages
GroovyScript
Had Enough Items
Item Stages
MixinBooter
Recipes Stages
ZenStages

Crafttweaker ZenStages Scripts:
scripts.zip
Steps to reproduce:

Install above modlist.
Ensure that B:hideRestrictionsInJEI=true is set to true in config/itemstages.cfg
Stage items using modId (Astral Sorcery was used for testing using the attached script)
Load the game and search for Astral Sorcery items. (all items are visible despite being staged)
Use the commands to add/remove the testing Gamestage (this does not change item visibility)

/gamestage add <player> testStage
/gamestage remove <player> testStage

Logs from the modlist in this issue thread:
logs.zip
Logs from the large modpack:
modpack_logs.zip


Trending graph for daily cases in a district

Is your feature request related to a problem? Please describe.
The information for number of cases in a district is shown for the present date only. It would be good to show the trend of cases in a line or bar graph for the number of cases reported in a district in the past. Monthly and 2-week graphs could be toggled just like the present functionality
Describe the solution you'd like
Line / Bar graph to show the trend of number of cases in a district.
Describe alternatives you've considered
None
Additional context
I tried to get the information from raw_data.json file. I wrote a python code to parse the data and print it in the form of "State => District => Date => No. of cases"
"Gujarat": {         "Surat": {             "21/03/2020": 2,             "23/03/2020": 1,             "24/03/2020": 1,             "25/03/2020": 2,             "26/03/2020": 1,             "29/03/2020": 1,             "31/03/2020": 1,             "01/04/2020": 2,             "04/04/2020": 1,             "05/04/2020": 3,             "06/04/2020": 3,             "07/04/2020": 3,             "08/04/2020": 1,             "09/04/2020": 1,             "10/04/2020": 3,             "11/04/2020": 1,             "13/04/2020": 5,             "14/04/2020": 9,             "15/04/2020": 9,             "16/04/2020": 37,             "17/04/2020": 52,             "18/04/2020": 13,             "19/04/2020": 89,             "20/04/2020": 27,             "21/04/2020": 78,             "22/04/2020": 68,             "23/04/2020": 41,             "24/04/2020": 6,             "25/04/2020": 34         },         "Ahmadabad": {             "20/03/2020": 2,             "21/03/2020": 2,             "22/03/2020": 3,             "23/03/2020": 6,             "28/03/2020": 3,             "29/03/2020": 4,             "30/03/2020": 1,             "31/03/2020": 1,             "01/04/2020": 8,             "03/04/2020": 7,             "04/04/2020": 7,             "05/04/2020": 8,             "06/04/2020": 11,             "07/04/2020": 19,             "09/04/2020": 59,             "10/04/2020": 55,             "11/04/2020": 46,             "12/04/2020": 39,             "13/04/2020": 38,             "14/04/2020": 53,             "15/04/2020": 77,             "16/04/2020": 95,             "17/04/2020": 78,             "18/04/2020": 239,             "19/04/2020": 239,             "20/04/2020": 147,             "21/04/2020": 125,             "22/04/2020": 128,             "23/04/2020": 151,             "24/04/2020": 169,             "25/04/2020": 182         },         "Vadodara": {             "20/03/2020": 1,             "21/03/2020": 1,             "23/03/2020": 4,             "28/03/2020": 2,             "05/04/2020": 1,             "06/04/2020": 2,             "08/04/2020": 6,             "09/04/2020": 4,             "10/04/2020": 37,             "11/04/2020": 36,             "12/04/2020": 6,             "13/04/2020": 6,             "14/04/2020": 6,             "15/04/2020": 8,             "16/04/2020": 7,             "17/04/2020": 16,             "18/04/2020": 14,             "19/04/2020": 22,             "20/04/2020": 8,             "21/04/2020": 11,             "22/04/2020": 9,             "23/04/2020": 7,             "24/04/2020": 5,             "25/04/2020": 7         },         "Gandhinagar": {             "22/03/2020": 1,             "23/03/2020": 1,             "24/03/2020": 3,             "26/03/2020": 3,             "28/03/2020": 1,             "31/03/2020": 1,             "04/04/2020": 2,             "10/04/2020": 1,             "11/04/2020": 1,             "14/04/2020": 1,             "16/04/2020": 1,             "23/04/2020": 1,             "24/04/2020": 1,             "25/04/2020": 4         },         "Kachchh": {             "05/04/2020": 1,             "10/04/2020": 2,             "20/04/2020": 2         },
This may be helpful in creating the district level graph using the above data.

Duplicates #1391


Doesnt work anymore on gleam.

No giveawayhelper buttons show up on gleam giveaways.

I'm not experiencing this on Gleam.  The buttons on Gleam appear differently than they do on other sites.  Here's an example of what it should look like; though Twitter buttons are no longer supported and so should not appear.  No buttons should appear if you're either not logged into a Gleam account, or don't have the relevant account linked to your Gleam account.


feat: add support for apache\kafka docker image

Up till now kafka test container used confluentinc/cp-kafka, recently kafka started producing two official
images apache\kafka and apache\kafka-native which may use kraft protocol, thus no zookeeper
instance is needed.
apache\kafka-native image has kafka server compiled using GraalVM which decreases container startup and memory consumption.
Default image is apache\kafka-native which provide fast starting speed.
More details:

KIP-974: Docker Image for GraalVM based Native Kafka Broker
KIP-975: Docker Image for Apache Kafka
Java testcontainer implementation

I've used this commit to fix mongo example missing feature which was failing tests

thanks @CommanderStorm, I hope your comments have been addressed


Put the index and sample values for sound decoding as fields of the relevant decoders

Possible enhancement, saves having to keep them around outside of the decoding process.  Would restrict decoding to being sequential, but it always is anyway right? 🤷♂

Done!  Forgot to tag commit 🤦♂


FEATURE bump march21-2022

Codecov Report

Merging #31 (ed0e4c5) into develop (a763052) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##           develop       #31   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files            1         1
  Lines           12        12
  Branches         1         1
=========================================
  Hits            12        12

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 a763052...ed0e4c5. Read the comment docs.


Add possibility to append a namespace to lock map key.

This PR makes it possible to specify a namespace for the switchboard instance, in order to be able to maintain multiple lock collections for a locker.
Also I had to upgrade the version of ruby, as well as versions of some dependencies, because currently used versions are quite hard to get up and running on a modern system.

👑

@ykorchomakha-fiverr

You may want to republish the gem to rubygems - https://rubygems.org/gems/switch_board
You may want to update the image on the readme, seems to be broken by now..


fix(redis_cache): Create SafeRedisClusterClient class to avoid application crashing because of redis

Thanks for submitting a PR! Please check the boxes below:

[ ] I have run pre-commit to check linting
[ ] I have added information to docs/ if required so people know about the feature!
[ ] I have filled in the "Changes" section below?
[ ] I have filled in the "How did you test this code" section below?
[ ] I have used a Conventional Commit title for this Pull Request

Changes

Create a client class that converts RedisClusterException to ConnectionInterrupted(handled/defined by django_redis)
Add explicit retry

How did you test this code?

Adds unit tests
Tested manually against local redis cluster

closing for https://github.com/Flagsmith/flagsmith/pull/3392


Improve internal-debug and use it in tf Dump commands

Support external istiod without XDS Address. If no pod are found for
the revision, we will fetch the URL from the webhook as a fallback
mechanism.
Improve the output. Currently, we always fetch from all istiods and
then emit some non-json output to distinguish the requests. This is hard
to read/parse in the case we do want all requests, and excessive
verbosity/performance when we only care about one. Instead, expose a
--all flag, off by default. When set, we will query all Istiod's, but
put the response in a structured JSON blob. When unset, we just output
the response from Istiod directly.
Switch Dumping or configz and ndsz in test framework to use the new
command. This both tests the command and makes tf dumping work for
external Istiod tests. I would also like bug-report to do it, but the PR is pretty
big.
Some smaller refactorings in the istioctl code to make this PR cleaner

[ ] Configuration Infrastructure
[ ] Docs
[ ] Installation
[ ] Networking
[ ] Performance and Scalability
[ ] Policies and Telemetry
[ ] Security
[ ] Test and Release
[ ] User Experience
[ ] Developer Infrastructure
Pull Request Attributes
Please check any characteristics that apply to this pull request.
[ ] Does not have any changes that may affect Istio users.

Hi @howardjohn, I noticed that you have changed the internal debug output format in this PR, so I want to understand:

For multiple istiod pods, which istiod pod would be output when user execute istioctl x internal-debug XXX by default?
I noticed that there are many \n displayed in output in my cluster when I execute istioctl x internal-debug edsz?proxyID=istio --all, showing as below:

{
  "istiod-67fc95944d-4vjjr": "Proxy not connected to this Pilot instance.

In fact, this output is not friendly for me, is that the same output in your cluster?

For multiple istiod pods, which istiod pod would be output when user execute istioctl x internal-debug XXX by default?

An arbitrary one

I noticed that there are many \n displayed in output in my cluster when I execute istioctl x internal-debug edsz?proxyID=istio --all, showing as below:
In fact, this output is not friendly for me, is that the same output in your cluster?

Yes. This is an internal-debug command. Its not intended to be as simple to use as possible - commands like istioctl proxy-config do that. It is machine readable. If you like the simple output you can not pass --all (its not often needed), or you can do something like jq -r 'to_entries[].value'.


Refactor healthchecker tests and update shrinkwrap files

Coverage increased (+0.004%) to 91.632% when pulling e2a4251eddf61aaad68fbc6077b83c5609b75c72 on SAP:429_2 into<PHONE_NUMBER>f8c3de5c66058fb5bf0ef5f171ea59 on cloudfoundry-incubator:master.

Coverage increased (+0.004%) to 91.632% when pulling 63464f993b7f9e6ab402bf3aafff5fe3b885d43d on SAP:429_2 into<PHONE_NUMBER>f8c3de5c66058fb5bf0ef5f171ea59 on cloudfoundry-incubator:master.

Coverage increased (+0.3%) to 91.911% when pulling bddde0ab6f4b48a974443827999d3400f9b90e62 on SAP:429_2 into<PHONE_NUMBER>f8c3de5c66058fb5bf0ef5f171ea59 on cloudfoundry-incubator:master.


Bastion can be used with Private DNS zones

The answer to the question  "https://docs.microsoft.com/en-us/azure/bastion/bastion-faq#can-i-use-azure-bastion-with-azure-private-dns-zones"  is not clear or wrong.
I have a VM and Bastion on same Vnet . This Vnet is linked to a private DNS zones and still I can access my VM via bastion. According to the document it is not possible. can you give clarity on the statement that you have written with an example ??

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

ID: 03ec4426-bfc1-b046-500d-38b2ca89c71d
Version Independent ID: cdacb6c7-1d83-c62b-9204-f04d9955722c
Content: Azure Bastion FAQ
Content Source: articles/bastion/bastion-faq.md
Service: bastion
GitHub Login: @cherylmc
Microsoft Alias: cherylmc

@rajsshah86 , thank you for your feedback. We'll investigate this and get back to you shortly!

@rajsshah86 , I did a lab setup on this scenario and below are my findings:

You can deploy Azure Bastion to a Vnet which is linked to a private DNS zone but only if the private DNS is not in service (which means the DNS zone is not integrated with any Private endpoint service).
You can also deploy Azure Bastion to a Vnet which is linked to a private DNS zone and the DNS zone is integrated to a private endpoint but you will not be able to connect to the VM resources in this Vnet via Bastion and will get the below error:

Hence, the correct sentence would be more like - "The use of Azure Bastion with Private endpoint integrated Azure Private DNS Zones is not supported at this time. Before you deploy your Azure Bastion resource, please make sure that the host virtual network is not linked to a Private endpoint integrated private DNS zone."
We have assigned this to the content owner/author for review and updating the doc accordingly.
@cherylmc , for your review & doc update.

Thanks! I've created the PR to update. You should see this published this week.

#please-close


Add support for device storage/memory

I have replaced all my rest calls with your integration and it works great. :blush:
However, I have two sensors that I hope you could consider adding.
  - platform: rest
    name: fullykiosk
    json_attributes:
      ['internalStorageFreeSpace', 'internalStorageTotalSpace',
      'ramFreeMemory', 'ramTotalMemory']
    resource: !secret fullykiosk_rest_resource
    value_template: '{{ value_json.screenOn }}'
    scan_interval: 900

  - platform: template
    sensors:
      fullykiosk_storage:
        friendly_name: Lagring
        icon_template: mdi:sd
        unit_of_measurement: '%'
        value_template: >
          {% set entity_id = 'sensor.fullykiosk' %}
          {% set FreeSpace = state_attr(entity_id, 'internalStorageFreeSpace') %}
          {% set TotalSpace = state_attr(entity_id, 'internalStorageTotalSpace') %}
          {% if not (FreeSpace == None or TotalSpace == None) %}
            {{ 100 - (FreeSpace / TotalSpace * 100) | int }}
          {% endif %}

      fullykiosk_memory:
        friendly_name: Minne
        icon_template: mdi:memory
        unit_of_measurement: '%'
        value_template: >
          {% set entity_id = 'sensor.fullykiosk' %}
          {% set FreeMemory = state_attr(entity_id, 'ramFreeMemory') %}
          {% set TotalMemory = state_attr(entity_id, 'ramTotalMemory') %}
          {% if not (FreeMemory == None or TotalMemory == None) %}
            {{ 100 - (FreeMemory / TotalMemory * 100) | int }}
          {% endif %}

Should be fairly easy to add. I've been concentrating on the zwave_js in HA core recently, but I'll try to get these added soon 🙂


Created MIT License

Notion card
Summary
Since the Miru is open-source, so we have to add an open-source Licence.
Preview

Type of change
Please delete options that are not relevant.

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to
not work as expected)
[ ] This change requires a documentation update

How Has This Been Tested?

Checklist:

[ ] I have manually tested all workflows
[ ] I have performed a self-review of my own code
[ ] I have added automated tests for my code

@akhilgkrishnan Please take pull from develop and re-run jobs again


Go modules support

In line with Go's release policy, dropping support for Go 1.10 and adding support for Go 1.13

At a very interesting point here:
This PR would never have all the test cases pass. There are two things going on here:

The build fails at the gfmrun stage where the gfmrun is not able to successfully run two of the README.md examples reference ShortOptionHandling (in master) which is not available in the latest release 1.21.0 of the cli.

Support I were to remove these references from the code and push, the gfmrun stage would pass but the build would again fail at the git diff stage as the README.md pushed with the PR would again not match the README.md at the master.

This brings me to the issue: #884

two of the README.md examples reference ShortOptionHandling (in master) which is not available in the latest release 1.21.0 of the cli

I have a PR for releasing 1.22.0 with ShortOptionHandling  here => https://github.com/urfave/cli/pull/882

This PR is based of the original flags PR.

I can remove that and separate it if you like

Right, either lets make the changes completely independent, or not file them at the same time if they are, and wait for required change to land.

Fair enough. I will clean this up

I have rebased this and cleaned up.

This build will fail until such time that 1.22.0 is merged and UseShortHandOptions is available for the tests to succeed.

All green here too :)


onDone not triggered on programatic call when no scroll is needed

There is a closed issue #27 considering probably same case (@ilkome did not specify whether he did it programatically). I am not sure if my message would be seen there since it is closed, sorry if I'm not doing it right.
Fiddle: https://jsfiddle.net/cfsv3dz8/
Tested on MacOS Sierra, Google Chrome Version 70.0.3538.110

You are passing body as the scroll to element, try passing a child element of body, as otherwise the scrollTop will always be 0 and no scrolling will occur.

Try to scroll down manually a bit and then click the button - you will see that both scroll and callback indeed can and do happen.
This GIF should illustrate the issue: callbacks not fired when no scroll occured.

It think this is still an issue when not targeting body.  If no scroll is needed, the onDone callback should fire.  Otherwise, consuming libraries have no idea if they can proceed to their next "action".
Here is an example showing the problem: https://codepen.io/brophdawg11/pen/exEwgX
The problematic code seems to be here: https://github.com/rigor789/vue-scrollto/blob/master/src/scrollTo.js#L193
In our specific use case, we're promisify-ing this library through a mixin, and in the case that an element is in the viewport, the promise will never resolve, unless we implement the same logic for checking vieport presence:
export default {
    methods: {
        $scrollToElement(element) {
            return new Promise((resolve) => {
                VueScrollTo.scrollTo(element, 500, {
                    onDone: resolve,
                    onCancel: resolve,
                    force: false,
                });
            });
        },
    },
};

I'm going to try to get a PR together to fix this now

Can the PR be integrated please? I really need this fix.

@rigor789 Sorry but this didn't fix my problem because issue also exists with force: true.

Please check whether 'onDone' is defined before calling!


Failed to load resource after build lambci/lambda:nodejs8.10

After start on sam local start-api and lambci/lambda:nodejs8.10 Docker container image
and open localhost:3000, all assets files return Failed to load resource: the server responded with a status of 403 (FORBIDDEN)
PS. Shared drives in docke turn on
OS: Win 10
sam --version
SAM CLI, version 0.18.0

docker --version
Docker version 18.09.2, build 6247962

Resolved, use git bash for start  sam local start-api -s  '.\'


[Optimizer] Infer is not null predicate from where clause

Is your feature request related to a problem or challenge? Please describe what you are trying to do.
There are some predicate include implicit is not null.
select * from t1 where c1 > 0;
->
select * from t1 where c1 > 0 and c1 is not null;

Why do this?
Expr in select expr and where expr is different.
Same expr in select don't include implicit is not null.
After this,
We can do this

eliminate self compare #2252
convert outer join to inner join #1585
eliminate Unsatisfiable Boolean Expressions #1716
.... other about predicate

Note: It isn't a optimizer rule !
It is because the following transformation can't terminate in Finite State Machine of rule.
select * from t1 where c1 > 0;
->
select * from t1 where c1 > 0 and c1 is not null;
->
select * from t1 where c1 > 0 and c1 is not null and c1 is not null;
->
.....

So, In fact, this is a rewrite in planner build (Specifically, it is in plan_selection).

I think this is a very subtle area of SQL and it depends on how the expression is being used
For example,
select * from t1 where c1 > 0;

and
select * from t1 where c1 > 0 and c1 is not null;

Are semantically equivalent (produce the same answers), but these are not:
select c1 > 0  from t1;

and
select c1 > 0 and c1 is not null from t1;

The reason is that the semantics of the WHERE clause are that only rows that evaluate to true are passed (if the row evaluates to NULL or false then they don't pass).
However, in general, you still have to handle the three way logic with NULL -- I am not at all convinced we do this entirely correctly in the expression simplification pass. We should probably have two modes: used in where and used elsewhere or something 🤔

Yes, we just handle the expr in where.
This rewrite is from spark.
Andrew Lamb @.***> 于 2022年4月19日周二 04:55写道：

I think this is a very subtle area of SQL and it depends on how the
expression is being used
For example,
select * from t1 where c1 > 0;
and
select * from t1 where c1 > 0 and c1 is not null;
Are semantically equivalent (produce the same answers), but these are not:
select c1 > 0  from t1;
and
select c1 > 0 and c1 is not null from t1;
The reason is that the semantics of the WHERE clause are that only rows
that evaluate to true are passed (if the row evaluates to NULL or false
then they don't pass).
However, in general, you still have to handle the three way logic with
NULL -- I am not at all convinced we do this entirely correctly in the
expression simplification pass. We should probably have two modes: used
in where and used elsewhere or something 🤔
—
Reply to this email directly, view it on GitHub
https://github.com/apache/arrow-datafusion/issues/2254#issuecomment-1101759932,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AHI4SLNVFUPSCQ5WR4SY5RDVFXD3RANCNFSM5TT2L62Q
.
You are receiving this because you authored the thread.Message ID:
@.***>

Great summary, this rewrite is from spark, I will read and consider carefully about this part.
I want to do this just because some expr rewrite is include this problem.

I am not at all convinced we do this entirely correctly in the expression simplification pass. We should probably have two modes: used in where and used elsewhere or something 🤔

Yes, This is where the problem lies. Other optimizer rules depend on implicit not null in where, which must handle this problem.
I think we should infer is not null, so other rule don't need to do infer not null but use directly is not null inferred by this rewrite. For example, convert outer join to left/right outer join or inner join can use is not null directly instead of match compare operator.


Nice to have: add .gitignore in the generated project

It would be great if the generated project contains a .gitignore with following content
dp_keys/
wwwroot/dist

I've added this in the latest templates.


added new screenshots

There was an error while validating job fc8fa42b-d017-497a-b3f3-77ffdd18363d Message:
Result status: Failed
There was a problem accessing Github repository 'https://github.com/Microsoft/cordova-docs.git'.
Details:Microsoft.LightweightJobEngine.Core.Language.ContextCommandBase+ContextCommandException:
Result status: Failed
There was a problem accessing Github repository 'https://github.com/Microsoft/cordova-docs.git'.
---> System.AggregateException: One or more errors occurred. ---> System.ArgumentException: Error clonning repository ---> LibGit2Sharp.NotFoundException: Branch 365 not found. Available branches: origin/master
at Microsoft.DPS.Services.LibGit2SharpSourceControlProvider.GetBranch(Repository repo, String name)
at Microsoft.DPS.Services.LibGit2SharpSourceControlProvider.<>c__DisplayClass30.<>c__DisplayClass35.b__2a(KeyValuePair2 branch)    at System.Collections.Generic.List1.ForEach(Action1 action)    at Microsoft.DPS.Services.LibGit2SharpSourceControlProvider.<>c__DisplayClass30.<CloneRepository>b__28()    at Microsoft.Practices.EnterpriseLibrary.TransientFaultHandling.RetryPolicy.<>c__DisplayClass1.<ExecuteAction>b__0()    at Microsoft.Practices.EnterpriseLibrary.TransientFaultHandling.RetryPolicy.ExecuteAction[TResult](Func1 func)
at Microsoft.Practices.EnterpriseLibrary.TransientFaultHandling.RetryPolicy.ExecuteAction(Action action)
at Microsoft.DPS.Services.LibGit2SharpSourceControlProvider.CloneRepository(String url, IDictionary2 branches)    --- End of inner exception stack trace ---    at Microsoft.DPS.Services.LibGit2SharpSourceControlProvider.CloneRepository(String url, IDictionary2 branches)
at Microsoft.DPS.Services.LibGit2SharpSourceControlProvider.CloneRepository()
at Microsoft.DPS.Services.LibGit2SharpSourceControlProvider.GetVersionAsync(String path)
at Microsoft.DPS.Commands.IdentifyDocumentsToPublish.CheckExternalServicesCommand.Do(IDictionary2 context)    --- End of inner exception stack trace ---    --- End of inner exception stack trace ---    at Microsoft.LightweightJobEngine.Core.Language.ContextCommandBase.ThrowIfErrorsLogged()    at Microsoft.DPS.Commands.IdentifyDocumentsToPublish.CheckExternalServicesCommand.Do(IDictionary2 context)
at Microsoft.LightweightJobEngine.Core.Language.JobWorkflow1.RunCommands(Guid jobId, IDictionary2 context, CancellationTokenSource cancelSignal)


Add support support for API, whose request body is just an object without specifying any details

…hout specifying any details

/azp run

/azp run


HBASE-24687 MobFileCleanerChore uses a new Connection for each table …

…each time it runs

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
1m 27s
Docker mode activated.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
4m  5s
the patch passed

+1 :green_heart:
compile
1m  6s
the patch passed

+1 :green_heart:
javac
1m  6s
the patch passed

+1 :green_heart:
shadedjars
6m 11s
patch has no errors when building our shaded downstream artifacts.

-0 :warning:
javadoc
0m 51s
hbase-server in the patch failed.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
4m  1s
the patch passed

+1 :green_heart:
compile
1m  4s
the patch passed

+1 :green_heart:
javac
1m  4s
the patch passed

+1 :green_heart:
shadedjars
5m 46s
patch has no errors when building our shaded downstream artifacts.

-0 :warning:
javadoc
0m 40s
hbase-server in the patch failed.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
5m 20s
the patch passed

+1 :green_heart:
compile
1m 24s
the patch passed

+1 :green_heart:
javac
1m 24s
the patch passed

+1 :green_heart:
shadedjars
7m 53s
patch has no errors when building our shaded downstream artifacts.

-0 :warning:
javadoc
0m 51s
hbase-server in the patch failed.

_ Other Tests _

-1 :x:
unit
147m 22s
hbase-server in the patch failed.

181m 14s

Subsystem
Report/Notes

Docker
Client=19.03.12 Server=19.03.12 base: https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-2038/2/artifact/yetus-jdk11-hadoop3-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/2038

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux 40a2e465f705 4.15.0-58-generic #64-Ubuntu SMP Tue Aug 6 11:12:41 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
master / f35c5eaadd

Default Java
2020-01-14

javadoc
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-2038/2/artifact/yetus-jdk11-hadoop3-check/output/branch-javadoc-hbase-server.txt

javadoc
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-2038/2/artifact/yetus-jdk11-hadoop3-check/output/patch-javadoc-hbase-server.txt

unit
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-2038/2/artifact/yetus-jdk11-hadoop3-check/output/patch-unit-hbase-server.txt

Test Results
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-2038/2/testReport/

Max. process+thread count
4038 (vs. ulimit of 12500)

modules
C: hbase-server U: hbase-server

Console output
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-2038/2/console

versions
git=2.17.1 maven=(cecedd343002696d0abb50b32b541b8a6ba2883f)

Powered by
Apache Yetus 0.11.1 https://yetus.apache.org

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
1m 40s
Docker mode activated.

-0 :warning:
yetus
0m  3s
Unprocessed flag(s): --brief-report-file --spotbugs-strict-precheck --whitespace-eol-ignore-list --whitespace-tabs-ignore-list --quick-hadoopcheck

_ Prechecks _

_ master Compile Tests _

+1 :green_heart:
mvninstall
4m 48s
master passed

+1 :green_heart:
compile
1m  3s
master passed

+1 :green_heart:
shadedjars
7m 23s
branch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
0m 45s
master passed

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
4m 26s
the patch passed

+1 :green_heart:
compile
1m 15s
the patch passed

+1 :green_heart:
javac
1m 15s
the patch passed

+1 :green_heart:
shadedjars
7m 18s
patch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
0m 47s
the patch passed

_ Other Tests _

-1 :x:
unit
233m 38s
hbase-server in the patch failed.

265m  5s

Subsystem
Report/Notes

Docker
Client=19.03.12 Server=19.03.12 base: https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-2038/2/artifact/yetus-jdk8-hadoop3-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/2038

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux 6dde7fcb8b7c 4.15.0-101-generic #102-Ubuntu SMP Mon May 11 10:07:26 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
master / f35c5eaadd

Default Java
1.8.0_232

unit
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-2038/2/artifact/yetus-jdk8-hadoop3-check/output/patch-unit-hbase-server.txt

Test Results
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-2038/2/testReport/

Max. process+thread count
3015 (vs. ulimit of 12500)

modules
C: hbase-server U: hbase-server

Console output
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-2038/2/console

versions
git=2.17.1 maven=(cecedd343002696d0abb50b32b541b8a6ba2883f)

Powered by
Apache Yetus 0.11.1 https://yetus.apache.org

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
0m 32s
Docker mode activated.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
4m 39s
the patch passed

+1 :green_heart:
compile
1m 12s
the patch passed

+1 :green_heart:
javac
1m 12s
the patch passed

+1 :green_heart:
shadedjars
6m 42s
patch has no errors when building our shaded downstream artifacts.

-0 :warning:
javadoc
0m 51s
hbase-server in the patch failed.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
4m 13s
the patch passed

+1 :green_heart:
compile
1m  7s
the patch passed

+1 :green_heart:
javac
1m  7s
the patch passed

+1 :green_heart:
shadedjars
6m 14s
patch has no errors when building our shaded downstream artifacts.

-0 :warning:
javadoc
0m 51s
hbase-server in the patch failed.

_ Other Tests _

+1 :green_heart:
unit
148m  1s
hbase-server in the patch passed.

175m 28s

Subsystem
Report/Notes

Docker
Client=19.03.12 Server=19.03.12 base: https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-2038/4/artifact/yetus-jdk11-hadoop3-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/2038

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux 25de20f01a4c 4.15.0-58-generic #64-Ubuntu SMP Tue Aug 6 11:12:41 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
master / 8191fbdd7d

Default Java
2020-01-14

javadoc
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-2038/4/artifact/yetus-jdk11-hadoop3-check/output/branch-javadoc-hbase-server.txt

javadoc
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-2038/4/artifact/yetus-jdk11-hadoop3-check/output/patch-javadoc-hbase-server.txt

Test Results
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-2038/4/testReport/

Max. process+thread count
4005 (vs. ulimit of 12500)

modules
C: hbase-server U: hbase-server

Console output
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-2038/4/console

versions
git=2.17.1 maven=(cecedd343002696d0abb50b32b541b8a6ba2883f)

Powered by
Apache Yetus 0.11.1 https://yetus.apache.org

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
0m 35s
Docker mode activated.

-0 :warning:
yetus
0m  2s
Unprocessed flag(s): --brief-report-file --spotbugs-strict-precheck --whitespace-eol-ignore-list --whitespace-tabs-ignore-list --quick-hadoopcheck

_ Prechecks _

_ master Compile Tests _

+1 :green_heart:
mvninstall
3m 51s
master passed

+1 :green_heart:
compile
0m 56s
master passed

+1 :green_heart:
shadedjars
5m 36s
branch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
0m 37s
master passed

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
3m 36s
the patch passed

+1 :green_heart:
compile
0m 55s
the patch passed

+1 :green_heart:
javac
0m 55s
the patch passed

+1 :green_heart:
shadedjars
5m 35s
patch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
0m 35s
the patch passed

_ Other Tests _

-1 :x:
unit
158m 22s
hbase-server in the patch failed.

182m 57s

Subsystem
Report/Notes

Docker
Client=19.03.12 Server=19.03.12 base: https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-2038/4/artifact/yetus-jdk8-hadoop3-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/2038

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux 72600739cb6b 4.15.0-58-generic #64-Ubuntu SMP Tue Aug 6 11:12:41 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
master / 8191fbdd7d

Default Java
1.8.0_232

unit
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-2038/4/artifact/yetus-jdk8-hadoop3-check/output/patch-unit-hbase-server.txt

Test Results
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-2038/4/testReport/

Max. process+thread count
3873 (vs. ulimit of 12500)

modules
C: hbase-server U: hbase-server

Console output
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-2038/4/console

versions
git=2.17.1 maven=(cecedd343002696d0abb50b32b541b8a6ba2883f)

Powered by
Apache Yetus 0.11.1 https://yetus.apache.org

This message was automatically generated.

@ArthurSXL8 any chance you can rebase and fix the merge conflicts on this? I can help get it merged, this recently became an issue for us.

This PR has become long out of date, with a bunch of merge conflicts. Closing it and we will re-implement it based on the current state of the branches.


Optimize getResponse

we have to call getResponse in almost every function to get sim800l response and its not a good practice try to deal with this like RTOS

issue is now solved in latest branch. but not with RTOS, RTOS will be implemented soon.


Make sure trace context headers are added only once

What does this PR do?

Make sure trace context headers are added only once to outgoing calls, even if the protocol supports multiple values per header (like in HTTP).
Checklist

[x] This is a bugfix

[ ] I have updated CHANGELOG.asciidoc
[x] I have added tests that would fail without this fix

:green_heart: Build Succeeded

the below badges are clickable and redirect to their specific view in the CI or DOCS

Expand to view the summary

Build stats

Start Time: 2021-07-28T09:58:33.261+0000

Duration: 55 min 45 sec

Commit: 20c5f123526e7eb5d537d1d3f2515ac1a77cb314

Test stats :test_tube:

Test
Results

Failed
0

Passed
2357

Skipped
19

Total
2376

Trends :test_tube:

:green_heart: Flaky test report
Tests succeeded.

Expand to view the summary

Test stats :test_tube:

Test
Results

Failed
0

Passed
2357

Skipped
19

Total
2376

For HTTP headers, most (if not all) header accessors allow for ready & write operations, thus maybe we could have a helper method or a variant of propagateTraceContext that ensure that header has only a single value.

Yes, that's what I wanted to do at first, but then realized that in some cases it's not efficient to read (allocates iterator for example), so using set instead of add (i.e. override) is cheaper (even though it's not equivalent).
In Spring RestTemplate I used a containsKey API on a per-header basis.
In OkHttp you even need to use a different type for reading and writing.
So I ended up doing it case by case, at least for now.


Consider libp2p mono repo

Taking into account the overhead that we experience in libp2p development when sometimes for getting a feature in we need to orchestrate several PRs just to land a change, we should consider turning libp2p into a mono repo. This would also help new contributors as they would not need to know where other modules are and that they would need to be updated (like the interop, in case its tests fail in CI).
Some of the repos that should be considered are the daemon, daemon client and libp2p-interfaces.
This issue should be used for this discussion, where we should put together benefits, drawbacks and lessons learned from js-ipfs change into a mono repo.
cc @jacobheun @achingbrain @hugomrdias

The other really nice thing we could do with this not listed is releasing preconfigured libp2p nodes more easily with every libp2p release so users don't have to configure anything if they just want something ready to go.

Some related modules have been grouped together as monorepos since this was opened:

https://github.com/libp2p/js-libp2p-daemon
https://github.com/libp2p/js-libp2p-interfaces
https://github.com/libp2p/js-libp2p-peer-id
https://github.com/libp2p/js-libp2p-webrtc-star

The primary piece of learning from js-ipfs is that choosing what to add to a monorepo is very important, and that you should not add everything unless you like very long build times.
Modules should also be homogeneous in terms of technology, scope and testing - if you have one GUI app in a monorepo and ten tiny utils, releasing changes to the utils takes as long as releasing changes to the GUI app which is a bit nuts.
Also flaky tests become that much painful.

I don't think there are other modules that need grouping together in the libp2p ecosystem so I'm going to close this issue but it's always something worth keeping an eye on.

candidates to add to monorepo: transports, multiplexers (yamux and mplex are in CS org), interfaces

The subject of migrating js-libp2p components into a monorepo was brought up by @MarcoPolo and discussed in the 2023-03-07 js-libp2p triage meeting with @achingbrain @wemeetagain @maschad and @p-shahi
The reasons for moving to a monorepo given were:

It is painful for maintainers to manage separate repos
Even though its cleaner conceptually to have separate repos, they are harder to track.

In practice there's added overhead even with CI bots to make things smoother.

The original proposed solution was to move any potential component a user pulls into a simple js-libp2p app (i.e. TCP, mplex, Yamux, Noise, WebSocket, WebTransport, Interfaces, etc.) into a monorepo.
However, we decided not to do this because:

Yamux, mplex, Noise, and GossipSub are maintained by ChainSafe and should be separate repos (to have other parties in ecosystem be responsible for libp2p components)
A simple app or user may not use all transports or components (some transports like TCP are not used by browsers)

So instead of one monorepo, our current thought is to create different groupings of smaller monorepos. These would look like:

js-libp2p: libp2p/interop, interfaces (consolidate interfaces to add and others to exclude)
js-libp2p-transports: WebRTC, WebTransport, WebSocket
js-libp2p-protocols: js-libp2p-kad-dht, identify, ping
js-libp2p-peer-discovery: js-libp2p-mdns, js-libp2p-bootstrap

@MarcoPolo also brought up the idea of using Git subtrees (where one can make changes to a repo directly and from a monorepo pull those changes in or you can make changes from monorepo and push changes out) as an option - but no consensus here.

Having spent more time that I'd like to admit pushing changes around during the IPFS Althing I am becoming more amenable to this as I'd like to spend more time shipping features and less time shipping dependency updates.
After<EMAIL_ADDRESS>I'm going to set something up like this here:

/packages/libp2p - the current repo
/packages/interface - types from @libp2p/interface-libp2p - this will be the public API and will have no dependencies on anything we consider the internal API, the goal being this should not change often so projects like Helia can depend on it and be free of internal module churn
/packages/interface-internal - a new module, @libp2p/interface-libp2p-internal that contains interfaces for internal components like ConnectionManager, TransportManager, etc.  Modules in the services hash can depend on this to define the components they require to operate.  By including this here it can be released alongside libp2p
/packages/interop - this is for interop tests

Essentially the first bullet point from the comment above.
Docs, examples stay where they are.

Another problem that we have is releasing changes to modules ahead of libp2p.
For example the next libp2p release changes the peer store to be atomic, so that means:

Update @libp2p/interface-peer-store with the breaking changes and release a major
Update @libp2p/peer-store to implement the interface changes and release a major
Update consumers of the peer store @libp2p/bootstrap, @chainsafe/libp2p-gossipsub, etc and release majors
Update libp2p and release a major

Before 4 is completed there's a window during which js users see an update to a module, upgrade to it and then wonder why stuff doesn't work.  Ts users will see a type error, though frequently they will ignore it and also wonder why stuff doesn't work.
We cannot control the release schedule of external modules (e.g. @chainsafe/libp2p-gossipsub) but being able to release 1-4 in one PR would go some way to reducing module churn and user surprise.
This adds a bit of weight to the whole-hog option of adding every supported libp2p module into the js-libp2p monorepo.

non-interface modules to monorepo added in https://github.com/libp2p/js-libp2p/pull/1828


mod_pagespeed does not handle application/xhtml+xml

From<EMAIL_ADDRESS>on November 03, 2010 18:10:48
I serve pages with the mime-type application/xhtml+xml (for xhtml 1.1). This should be optimized the same as html, but it does not work. xhtml can also be served as text/xml and application/xml but these might need to be handled differencly.
Attachment: instaweb-application-xhtml-xml.diff
Original issue: http://code.google.com/p/modpagespeed/issues/detail?id=4

From<EMAIL_ADDRESS>on November 03, 2010 16:22:36
Great, thanks chaz, we know of a few issues we will have parsing and rewriting strict XML, but we would like to get this supported fully.

From<EMAIL_ADDRESS>on November 03, 2010 19:25:30
shawn you can find the categorization logic that page speed uses here: https://code.google.com/p/page-speed/source/browse/lib/trunk/src/pagespeed/core/resource.cc#281 we should factor a lot of this code out into common libraries that can be shared.

From<EMAIL_ADDRESS>on November 05, 2010 08:01:17
Labels: -Type-Defect Type-Enhancement

From<EMAIL_ADDRESS>on November 09, 2010 14:33:15
Issue 57 has been merged into this issue.

From<EMAIL_ADDRESS>on November 09, 2010 14:34:13
Comment from rwap.services:
Line 17, Column 199: end tag for "link" omitted, but OMITTAG NO was specified
…608ee6f61356.css,_style,s+css,_color,s+js,_countdown,_jquery,ocountdown,s.css">✉
You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".
This relates to where mod_pagespeed has merged several css files together - forming the line:
17.<link rel="stylesheet" type="text/css" media="all" href="http://<IP_ADDRESS>/themes/enuukGreen/cc.f770833204dec8234e53608ee6f61356.css,_style,s+css,_color,s+js,_countdown,_jquery,ocountdown,s.css
To fit in with XHTML, this should have a proper closing tag -ie:
17.<link rel="stylesheet" type="text/css" media="all" href="http://<IP_ADDRESS>/themes/enuukGreen/cc.f770833204dec8234e53608ee6f61356.css,_style,s+css,_color,s+js,_countdown,_jquery,ocountdown,s.css"/
Other issues appear where the module inserts the image dimensions - for example:
<img src="http://<IP_ADDRESS>/uploaded/img/ce.8645aabfe710d131203e130f259e5c49.site-logo,g.gif alt="Logo" width=360 height=123 />
This should have quotes around the width and height values, ie:
<img src="http://<IP_ADDRESS>/uploaded/img/ce.8645aabfe710d131203e130f259e5c49.site-logo,g.gif alt="Logo" width="360" height="123" />
Rich
www.rwapservices.co.uk

From<EMAIL_ADDRESS>on November 24, 2010 08:08:58
Status: Started
Owner<EMAIL_ADDRESS>

From<EMAIL_ADDRESS>on December 03, 2010 14:36:51
Status: Fixed


Automated cherry pick of #4728: fix: eip duplicate name

Cherry pick of #4728 on release/2.11.
#4728: fix: eip duplicate name

Codecov Report

:exclamation: No coverage uploaded for pull request base (release/2.11@76edf6b). Click here to learn what that means.
The diff coverage is 0%.

@@              Coverage Diff               @@
##             release/2.11   #4733   +/-   ##
==============================================
  Coverage                ?   7.09%
==============================================
  Files                   ?     480
  Lines                   ?   78225
  Branches                ?       0
==============================================
  Hits                    ?    5552
  Misses                  ?   72206
  Partials                ?     467

Flag
Coverage Δ

#aFlag
7.09% <0%> (?)

Impacted Files
Coverage Δ

pkg/compute/models/elasticips.go
1.26% <0%> (ø)

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 76edf6b...f7f3a66. Read the comment docs.

/lgtm

/approve

/approve


feat: add sqs schemas

Current dependencies on/for this PR:

11-29-feat_add_sns_schemas

PR #17   👈

This comment was auto-generated by Graphite.

Graphite Merge Job
Current status: ⏳ Queued to merge
This pull request is currently queued to be merged as part of a stack.
This comment was auto-generated by Graphite.

Job Reference: j7Bu8pCEUHqFlKED3zbX


microtype Unable to apply patch `footnote' with phase-II and phase-III

MWE:
\DocumentMetadata{
 testphase=phase-II,
 pdfversion=2.0
}

\documentclass{article}

\usepackage{microtype}

\begin{document}

Simple text

\end{document}

Result:
lualatex mwe.tex | texlogfilter
LaTeX2e <2022-11-01> patch level 1
Document Class: article 2022/07/02 v1.4n Standard LaTeX document class
Package microtype Warning: Unable to apply patch `footnote' on input line 10.

Output written on microtype.pdf (1 page, 17767 bytes).

Found 1 warning(s)

yes as the footnote commands are different microtype can't patch them. microtype will have to adapt its code at some time if it wants to support also footnotes if tagging active. For now either ignore or silence with \usepackage[nopatch=footnote]{microtype}

Thank you!

opened an issue for this https://github.com/schlcht/microtype/issues/40

seems to be already fixed but not released yet
see https://github.com/schlcht/microtype/issues/40


Meta analysis of update functions in BBM real-world networks

In particular, we want to know how common are:

threshold functions
nested canalising functions

The problem is that we probably shouldn't use syntax for this, because the function expressions can be very weird depending on format. So we actually need some more sophisticated method (this should be a fast test with on the BDD representation once we figure out the right conditions, but maybe there is an easier way to test this even if it takes more time to run it).

I'm going to close this as being out-of-scope for the current manuscript.


Fix #635 - Use StaticDecode<> instead of Static<> to get type of inpu…

…t schema
This will infer the correct type with Typebox Transform Types (https://github.com/sinclairzx81/typebox?tab=readme-ov-file#transform-types) are used

@SaltyAom do you consider this for the next release? This is pretty useful. Like transforming a string to a date, converting using an enum and so on. I wonder if this is actually just a type issue or if this needs more work (actually transforming the data using typebox).

I wonder if this is actually just a type issue or if this needs more work (actually transforming the data using typebox).

I didn't hunt down where the deserialization happens, but as long as Elysia is using Decode it should automagically work, and indeed that seems to be the case in my little project.


Some changes to build.jl

wget -> download (there's no wget in OS X by default)
git clone to use https<EMAIL_ADDRESS>... is giving public key error)

I think all cp / mv commands should be replaced with julia's internal ones as they should be os independent? I also get errors with copy:
cp: illegal option -- -
usage: cp [-R [-H | -L | -P]] [-fi | -n] [-apvX] source_file target_file
       cp [-R [-H | -L | -P]] [-fi | -n] [-apvX] source_file ... target_directory

Finally, the compilation is failing using OS X, any ideas?
Cloning into 'CalculiX-cmake'...
remote: Counting objects: 658, done.
remote: Compressing objects: 100% (3/3), done.
remote: Total 658 (delta 0), reused 0 (delta 0), pack-reused 655
Receiving objects: 100% (658/658), 1.35 MiB | 575.00 KiB/s, done.
Resolving deltas: 100% (234/234), done.
Checking connectivity... done.
-- The C compiler identification is Clang 5.1.0
-- The Fortran compiler identification is GNU
-- Check for working C compiler: /usr/bin/cc
-- Check for working C compiler: /usr/bin/cc -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Check for working Fortran compiler: /opt/local/bin/gfortran
-- Check for working Fortran compiler: /opt/local/bin/gfortran  -- works
-- Detecting Fortran compiler ABI info
-- Detecting Fortran compiler ABI info - done
-- Checking whether /opt/local/bin/gfortran supports Fortran 90
-- Checking whether /opt/local/bin/gfortran supports Fortran 90 -- yes
CMake Warning (dev) at CMakeLists.txt:6 (LINK_DIRECTORIES):
  This command specifies the relative path

    ../../usr/lib

  as a link directory.

  Policy CMP0015 is not set: link_directories() treats paths relative to the
  source dir.  Run "cmake --help-policy CMP0015" for policy details.  Use the
  cmake_policy command to set the policy and suppress this warning.
This warning is for project developers.  Use -Wno-dev to suppress it.

-- Try OpenMP C flag = [ ]
-- Performing Test OpenMP_FLAG_DETECTED
-- Performing Test OpenMP_FLAG_DETECTED - Failed
-- Try OpenMP C flag = [-fopenmp]
-- Performing Test OpenMP_FLAG_DETECTED
-- Performing Test OpenMP_FLAG_DETECTED - Failed
-- Try OpenMP C flag = [/openmp]
-- Performing Test OpenMP_FLAG_DETECTED
-- Performing Test OpenMP_FLAG_DETECTED - Failed
-- Try OpenMP C flag = [-Qopenmp]
-- Performing Test OpenMP_FLAG_DETECTED
-- Performing Test OpenMP_FLAG_DETECTED - Failed
-- Try OpenMP C flag = [-openmp]
-- Performing Test OpenMP_FLAG_DETECTED
-- Performing Test OpenMP_FLAG_DETECTED - Failed
-- Try OpenMP C flag = [-xopenmp]
-- Performing Test OpenMP_FLAG_DETECTED
-- Performing Test OpenMP_FLAG_DETECTED - Failed
-- Try OpenMP C flag = [+Oopenmp]
-- Performing Test OpenMP_FLAG_DETECTED
-- Performing Test OpenMP_FLAG_DETECTED - Failed
-- Try OpenMP C flag = [-qsmp]
-- Performing Test OpenMP_FLAG_DETECTED
-- Performing Test OpenMP_FLAG_DETECTED - Failed
-- Try OpenMP C flag = [-mp]
-- Performing Test OpenMP_FLAG_DETECTED
-- Performing Test OpenMP_FLAG_DETECTED - Failed
-- Could NOT find OpenMP (missing:  OpenMP_C_FLAGS)
-- Configuring done
-- Generating done
-- Build files have been written to: /Users/jukka/dev/CalculiX.jl/deps/builds/CalculiX
Scanning dependencies of target calculix
[  0%] Building C object CMakeFiles/calculix.dir/src/expand.c.o
In file included from /Users/jukka/dev/CalculiX.jl/deps/src/CalculiX-cmake/src/expand.c:22:
/Users/jukka/dev/CalculiX.jl/deps/src/CalculiX-cmake/src/CalculiX.h:1510:21: error:
      unknown type name 'pthread_t'
int pthread_create (pthread_t *thread_id, const pthread_attr_t *attributes,
                    ^
/Users/jukka/dev/CalculiX.jl/deps/src/CalculiX-cmake/src/CalculiX.h:1513:19: error:
      unknown type name 'pthread_t'
int pthread_join (pthread_t thread, void **status_ptr);
                  ^
In file included from /Users/jukka/dev/CalculiX.jl/deps/src/CalculiX-cmake/src/expand.c:24:
/Users/jukka/dev/CalculiX.jl/deps/src/CalculiX-cmake/src/spooles.h:40:2: error:
      unknown type name 'IV'
        IV *newToOldIV, *oldToNewIV;
        ^
/Users/jukka/dev/CalculiX.jl/deps/src/CalculiX-cmake/src/spooles.h:41:2: error:
      unknown type name 'SolveMap'
        SolveMap *solvemap;
        ^
/Users/jukka/dev/CalculiX.jl/deps/src/CalculiX-cmake/src/spooles.h:42:2: error:
      unknown type name 'FrontMtx'
        FrontMtx *frontmtx;
        ^
/Users/jukka/dev/CalculiX.jl/deps/src/CalculiX-cmake/src/spooles.h:43:2: error:
      unknown type name 'SubMtxManager'
        SubMtxManager *mtxmanager;
        ^
/Users/jukka/dev/CalculiX.jl/deps/src/CalculiX-cmake/src/spooles.h:44:2: error:
      unknown type name 'ETree'
        ETree *frontETree;
        ^
7 errors generated.
make[2]: *** [CMakeFiles/calculix.dir/src/expand.c.o] Error 1
make[1]: *** [CMakeFiles/calculix.dir/all] Error 2
make: *** [all] Error 2
=============================[ ERROR: CalculiX.jl ]=============================

LoadError: failed process: Process(`make`, ProcessExited(2)) [2]
while loading /Users/jukka/.julia/v0.4/CalculiX.jl/deps/build.jl, in expression starting on line 157

================================================================================

================================[ BUILD ERRORS ]================================

WARNING: CalculiX.jl had build errors.

 - packages with build errors remain installed in /Users/jukka/.julia/v0.4
 - build the package(s) and all dependencies with `Pkg.build("CalculiX.jl")`
 - build a single package by running its `deps/build.jl` script

================================================================================

I think this is the root cause: "Could NOT find OpenMP (missing:  OpenMP_C_FLAGS)".  Maybe here is the answer: http://forums.macrumors.com/threads/configuring-using-cmake-openmp-issues.1842891/


fix: change invalid log message when InPlace update strategy is used

Currently, regardless of whether a recreate (ChildUpdateRecreate/ChildUpdateRollingRecreate) or inplace update (ChildUpdateInPlace/ChildUpdateRollingInPlace) strategy is selected for updating children, the same message (Recreate update strategy selected) is shown in the log. Instead, they should print different messages.

thanks @vmax for this  PR!

:tada: This PR is included in version 2.1.2 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


SWB access to Vyshnavi

@vyshu1094 already has an AWS account, she want to launch a windows SWB workspace to use PowerBI desktop to create PCORnet study metrics dashboard.
Since there is no SWB study/organization for PMs she can be added to "NextGenBMI-Outback-Engineering"

Got her added to the SWB researchers access group and added/activated her user entry in the UMBMIAWS SWB application.  She should be able to log in at https://aws.nextgenbmi.umsystem.edu now, but let me know of any issues.

@vasanthi014 @fergusonsha-umkc I got the access. Thanks much!


Add backward compatibility of WebHDFS

Coverage remained the same at 51.62% when pulling 3cdde173115687818cffe6f407908bed77bc4d4e on qixcheng/pylon/webhdfs-backward-compatibility into 0b4a6728c71c84bd83da2f4a26c01c1c53ca05da on master.


fixed a type error in jams_to_lab

jams_to_lab didn't actually work because Annotation objects ceased being hashable.
This PR fixes the conversion logic to use an array rather than a set.
Anyone care to CR?  It should be an easy one.  (Maybe @ejhumphrey )


[proposal] Add a new cfn/SAM based deployment backend

This is a proposal to add a new deployment backend that’s based on cloudformation and the AWS Serverless Application Model (AWS SAM).  This addresses several points of customer feedback and makes several feature requests easier to implement.
Motivation
When chalice deploys your application, it uses boto3, the AWS SDK for Python, to make the necessary coordinated API calls to IAM, Lambda, and API Gateway.  There’s several benefits with this approach.  Deployments are fast as we're making direct API calls to API gateway and Lambda.  Nothing to setup (including S3 buckets because we send the zip file contents directly to lambda).
However, there’s several customer issues that I’d like to address:

Option to not deploy to dev, but only to update the resources in IAM, lambda, and API Gateway
Separation of chalice app and chalice deploy concerns
Chalice delete
Support cloud formation templates
List of resources created

I think that most of these issues can be addressed by leveraging the serverless application model along with cloudformation stacks.  Consider if the whole deployment was broken down into into two explicit and separable components:

Generate assets that describe what to deploy
Take those locally generated assets and deploy them to AWS.

This gives users insight into what we’re about to deploy, allows them to customize what’s going to be deployed (by manipulating the manifest), allows them to see a list of resources that were created, and also makes deletion trivial.
Specification
Customers will now have the option of creating a chalice application with the new cfn deployment backend (the defaults will remain unchanged).  This choice must be made at project creation time.  It will not be possible to migrate from the current deployment backend to the cfn deployment backend.
The eventual goal would be to make this the default (and maybe only) deployment backend.
A new parameter is added to the new-project command that indicates you want to use Serverless Application Model templates: chalice new-project --use-sam-templates --s3-path.  Note you'll also have to specify an S3 location where the deployment package can be uploaded (this is needed when using SAM/cfn).
Once you’ve created a new application with SAM templates enabled, the chalice deploy command will internally use SAM templates and cloud formation to deploy your application.
There will also be a new chalice package command, which can only be used for projects created with --use-sam-templates.  This command creates local assets for your chalice app that can then be deployed at a later time (or even by other tools that can work with SAM templates).  This package command takes an output directory and writes the following files to that directory:

app.json - The generated SAM template
deployment.zip - The deployment zip file to send to lambda

In order to create a lambda function with cfn, we’ll need to upload your deployment package to S3 and update the app.json with a path to that remote path.  By default, the chalice package command does not make any remote
API calls, but you can provide the --remote-assets flag to indicate you’d like chalice to handle uploading your lambda deployment package to S3 for you.  It will also take care of updating the SAM template with a reference to that S3 location when --remote-assets is specified.
Example
Here’s an example of using this new functionality to create a deployment package that can be deployed with the AWS CLI using the newly introduced aws cloudformation package/deploy commands:
$ chalice new-project —use-sam-templates cfn-based-app --s3-path s3://bucket/

# This will generate a SAM template, and upload your deployment package to S3
$ chalice package --remote-assets /tmp/deploy

# You can now deploy the app using your preferred cfn tools
# Here we're using the AWS CLI to deploy our app:
$ aws cloudformation deploy
        --template-file /tmp/deploy/app.json \
        --stack-name cfn-based-app --capabilities CAPABILITIES_IAM

# We can grab the endpoint url from the stack outputs:
$ aws cloudformation describe-stacks \
        --stack-name cfn-based-app \
        --query "Stacks[0].Outputs[?OutputKey=='EndpointUrl'] | [0].OutputValue" \
        --output text
https://api-id.execute-api.us-west-2.amazonaws.com/dev/

Future enhancements
One other thing I'd like to add in the future is the ability for users to modify the existing SAM template, possibly with their own application specific resources.  A really simple example would be to allow them to specify additional cfn/SAM resources that can merged together with the template we generate:
# Project root directory (where app.py is located):
$ cat app.json
{
  "Resources" : {
    "myTable" : {
      "Type" : "AWS::DynamoDB::Table",
      "Properties" : {
        "AttributeDefinitions" : [...],
        "TableName": "mytable"
        ...
      }
    }
  }
}

@jamesls
I like the direction of making the chalice compatible with the other tools like the CLI that support SAM. One question that I do have is for the package command when you do not specify --remote-assets how difficult is it to modify your app.json to point to the s3 bucket that you upload it to? The only reason I ask is because I wonder if the package command should be uploading to s3 by default?
Also is the --s3-path  argument required for new-project? And if so, if you do not specify it, does the workflow change in getting your application deployed and if so, how?

how difficult is it to modify your app.json to point to the s3 bucket that you upload it to?

Are you asking how hard it is to manually update?  If so, there's only one line you change.
In general though, you would be able to leverage the aws cloudformation package command to handle that for you.  It generates a reference to the local deployment package path.
$ chalice package --local-assets /tmp/packaged
$ cd /tmp/packaged
$ ls -la
-rw-r--r--   1 jamessar  wheel     8547 Nov 29 11:12 app.json
-rw-r--r--   1 jamessar  wheel  3358734 Nov 29 11:12 deployment.zip

$ jp Resources.APIHandler < app.json
{
  "Properties": {
    "CodeUri": "./deployment.zip",
    "Events": {
      "indexget": {
        "Properties": {
          "Method": "get",
          "Path": "/",
          "RestApiId": {
            "Ref": "RestAPI"
          }
        },
        "Type": "Api"
      }
    },
    "Handler": "app.app",
    "Runtime": "python2.7"
  },
  "Type": "AWS::Serverless::Function"
}

# Then to deploy:

$ aws cloudformation package ...
$ aws cloudformation deploy ...

Also is the --s3-path argument required for new-project?

Yeah, I'll update the issue.

Ahh that makes sense did not realize you could do:
chalice package --local-assets /tmp/packaged
aws cloudformation package --template-file app.json --s3-bucket mybucket

That's nice. Seems straightforward.

Love the direction +1

This all looks very good.  What my team needs soon will be the ability to deploy via update rather than delete/add in APIG and deploying to prod rather than dev.  The latter is easy to workaround for now, at least.

any code/wip on this to review?

@jamesls I would like to help with PR, can you please let me know if you already started working or I should start from scratch?

Sorry for the delay.  I'll clean up the local branch I have of this and sent for initial review.

I wanted to ping this issue and see if this is still the plan. I'm looking for a way to use Chalice when promoting code up a CD pipeline.

Any news on this, currently using SAM and python and keen to try chalice.

Following up here, this is now available in the 0.8.0 release of chalice, via the new chalice package command: chalice package /tmp/packaged-dir.  I'll keep this open until I finish writing docs for this, but you it's available if you want to try it out.

Docs have been added, closing out issue, this is implemented in chalice now.


Memory leak when closing bottom sheet via BottomSheetParams.closeCallBack()

Which platform(s) does your issue occur on?

iOS/Android

Please, provide the following version numbers that your issue occurs with:

CLI: 8.8.0
Cross-platform modules: 8.7.3
Runtime(s): Android - 8.8.2, iOS - 8.7.2
Plugin(s): 7.2.55
Nativescript Angular: 17.1.0

Please, tell us how to recreate the issue in as much detail as possible.

Use the bottom-sheet to display a component.
Perform some action within the component and call BottomSheetParams.closeCallBack() to close the modal.
Do this several times.
Invoke Application.getRootView()._getRootModalViews();
Notice that the modals opened via the bottom sheet remain in memory and are not cleaned up. If you instead dismiss the bottom sheet by tapping elsewhere in the app (and not closing it via bottomSheetParams.closeCallback()) the modal reference is cleaned up.

Not sure if this is the proper solution, but if you invoke this - this._bottomSheetClosed(); - at the end of ViewWithBottomSheetBase.closeBottomSheet, the modal reference appears to get cleaned up when following the flow listed above.

@mono-tropa i tested and could not reproduce the issue. Here the modal stack is correctly emptied.
Can you create a simple reproducible example project?

Here's a link to a sample app.
https://stackblitz.com/edit/nativescript-stackblitz-templates-xwop8k
It appears this issue is only reproducible in iOS, not Android. Sorry about that, i'll amend my original post.
When you open up the bottom sheet and tap done, notice how the items in the console log repeatedly grow.


Spec Example not compliant to DID Core spec

Minor issue in the example:
The correct name for the Authentication-Method is just authentication and not authenticationMethod. See here

hello, nice to e-meet you! And thank you for opening the issue :)
This is indeed an error in the example. After a review, I see that the rest of the spec simply refers to the corresponding W3C names, so it seems to just be an error in that example. I will correct the text in a PR


Added StringFunctionTests + Move Implementations out of headers

This is needed for my homeboy @bilisun in #514
I didn't finish all of the StringFunctions test cases, so the coverage might go down. I can pick up on that later tomorrow after class.

Coverage decreased (-0.1%) to 65.719% when pulling 236ff1ccd33a5f2846dd1b44c56d39043a2a60ec on apavlo:master into 931d6b9040963ca72b350f173eadd8b0c7d0792b on cmu-db:master.

Coverage decreased (-0.3%) to 65.597% when pulling be92317b6e60e585f983aa6cc321001ea37b6bab on apavlo:master into 40492abe210cde5712f660bc0997dd948cbe31b2 on cmu-db:master.


chore(main): release 0.0.15

:robot: I have created a release beep boop
0.0.15 (2024-06-26)
What's Changed

add: llm megaparser by @chloedia in https://github.com/QuivrHQ/MegaParse/pull/42

Full Changelog: https://github.com/QuivrHQ/MegaParse/compare/v0.0.14...v0.0.15

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/QuivrHQ/MegaParse/releases/tag/v0.0.15 :sunflower:


Add other important element identifiers for the webpage.

Need to add other identifiers for testers.
For testers, here are some commonly used identifiers that help locate and interact with elements on a webpage, along with XPath and className:

ID (id):

A unique identifier assigned to an HTML element, typically the most reliable selector.
Example: <input id="username" />

Name (name):

Often used for form elements, like inputs or buttons, especially in testing scenarios.
Example: <input name="email" />

CSS Selectors (cssSelector):

CSS selectors provide a way to select elements based on CSS properties (e.g., classes, attributes).
Example: input[name='email']

Tag Name (tagName):

Identifies an element by its HTML tag (e.g.,
, <input>, ).
Example: document.getElementsByTagName('input')

Class Name (className):

Selects elements by their class attribute, often used when many elements share the same class.
Example:

Link Text (linkText):

Useful for testing links (anchor tags) by the exact visible text.
Example: Submit (selector: By.linkText('Submit'))

Partial Link Text (partialLinkText):

Similar to linkText, but matches a portion of the link's text.
Example: Click here (selector: By.partialLinkText('Click'))

Attributes:

Elements can also be selected by attributes like href, type, placeholder, etc.
Example: <input type="password" placeholder="Enter password" />

Relative XPath:

Provides flexibility by selecting elements based on their relationship to other elements.
Example: //button[text()='Submit']

Text Content (text):

Finds elements based on the visible text content of the element.
Example: document.querySelector('button').innerText

Each of these identifiers can be essential for targeting and interacting with elements on webpages, particularly in automated testing scenarios like UI testing or form validation.

TBD: which of these element identifiers to add that are relevant to QA